Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Steve, The problem is that your history doesn't match the experience of any one else participating in this thread. You keep making assertions about testing being broken, sometimes with hundreds of broken dependencies. Since one of the key criterion of packages entering testing is dependencies are correct and fulfillable, this strikes most of us as unlikely. Yes, and security upgrades never change behaviour of software and never break things. That's the way it OUGHT to be. The reality has its own turbulences. I won't claim testing has never had a broken depends, but it's very rare, and never hundreds of packages. Well, I might have been out of luck. Maybe it hasn't been hudreds, just a full screen of (didn't count them and wouldn't remember anyway). That changes nothing on assertion, that using the testing routinely is not official, nor advisable way for ordinary users. It's a basic point of science that the person making the unusual claims needs to provide the data to back it up. My original intention was not, and still is not, to discuss capabilities of testing. I want to discuss possibilities, how could the stable be more attractive for ordinary user, how to make it usable on hardware newer-than-3-years-old, how could the user be blessed with fresh software rather than 2-years old, how to allow him to easily and effectively participate on bug reporting, and how to avoid the work of backporting security fixes to ancient software. If You and several people claim they haven't met such problems with testing, I can live with that. I also heard people whose experience was different, and my personal one is closer to them. That's all. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Steve, And as others have pointed out, the purpose of stable is to minimize disruptions. For many users, living with known bugs with known workarounds is a *lot* better than identifying new bugs. Yeas. Let the choice to the user. Don't dictate him. Whoever wants to use the old software w/o change, let be it. Whoever wants the new one, noticed about the risks, let's give him an official and supported way to do it. For one thing, it's not just Iceweasel, it's all the plugins and extensions that might be in use, *and* any external software or libraries that those extensions use. AFAIK, all Mozilla's programs take care about plugins their own way and offer upgrades automatically. I don't have enough technical background to opose You at the Debian packages level however, You're knowledge could be better than mine. Not to mention all the other software that uses iceweasel libraries. Is there any? Additionally, any internal webapps have to be validated against the new iceweasel. Internal macros need to be validated against the new OO.org.It's a lot of work. Yes, for the admins that are willing to deploy the software. Repeat, I just want the _official_and_supported_way_ to do it. Let the users choose, whether they want to upgrade. Repeat, let there be easy downgrade option for the case things don't work as expected. Now, that may be of little relevance to the home user. But I know some such users who also *don't* like upgrades, because they're happy with what they have and don't need to change. For example, my father-in-law just this year went from Mac OS9 to OSX, mostly because his hardware was dying. So he hadn't upgraded in 6 *years*, and didn't feel he was missing anything. There's quite a few of those people out there. Not to upgrade, that's perfectely legitimate choice. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, May 17, 2007 at 08:20:50AM +0200, Mgr. Peter Tuharsky wrote: Steve, And as others have pointed out, the purpose of stable is to minimize disruptions. For many users, living with known bugs with known workarounds is a *lot* better than identifying new bugs. Yeas. Let the choice to the user. Don't dictate him. Well, I really cannot see your point. If you do not like how stable is done at the moment in Debian, but do like how it is done in whatever other distro - use that distro. Nobody forces anything on you. This is all about choice. Whoever wants to use the old software w/o change, let be it. Whoever wants the new one, noticed about the risks, let's give him an official and supported way to do it. Fist of all, there is such a way: use testing, most of the time it is fairly safe to use. Learn how to put packages on hold and how to get back if something goes wrong. [ skipped ] Let the users choose, whether they want to upgrade. =) OMG, I do not think that somebody really forces me when to run apt-get upgrade and what packages to install and from what repository. Repeat, let there be easy downgrade option for the case things don't work as expected. man sources.list man apt_preferences http://snapshot.debian.net/ If you maintain more than one machine - setup a local repository and fill it with the versions of the packages you like. Including backported ones, learn how to backport. -- Stanislav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Steve, I see main problem with testing that broad platform changes are going there. That's why things break sometimes there. That's why I think, that the Stable platform with new desktop software might be the choice -the new software versions with no platform dependecies breakage risk. This is closest to backports and volatile idea. I wouldn't call it backports however, because that reminds porting some very new software to some very old platform, and this is not the case. The stable's basic platform should stay LSB-compliant and moderately-aged (supported by all main software vendors) for the whole length of release cycle. Thus the new versions of desktop software wouldn't be backported; just compiled against ordinary, stable platform. I don't know how real the vision is, however it shouldn't be completely impossible I hope ;-) Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Stanislav, I see Your point, however this is far from user-friendliness. First solution -use other distro. Wow, what a great idea. Looking at statistics and Linux users in neighborhood, You can be _sure_ they discovered that way already :-) Be also sure, that unwilling to do more for desktop users, Debian will not be less, but increasingly more server-oriented distro (I like Debian on server!). I like Debian either. Friendly, Peter Stanislav Maslovski wrote / napísal(a): On Thu, May 17, 2007 at 08:20:50AM +0200, Mgr. Peter Tuharsky wrote: Steve, And as others have pointed out, the purpose of stable is to minimize disruptions. For many users, living with known bugs with known workarounds is a *lot* better than identifying new bugs. Yeas. Let the choice to the user. Don't dictate him. Well, I really cannot see your point. If you do not like how stable is done at the moment in Debian, but do like how it is done in whatever other distro - use that distro. Nobody forces anything on you. This is all about choice. Whoever wants to use the old software w/o change, let be it. Whoever wants the new one, noticed about the risks, let's give him an official and supported way to do it. Fist of all, there is such a way: use testing, most of the time it is fairly safe to use. Learn how to put packages on hold and how to get back if something goes wrong. [ skipped ] Let the users choose, whether they want to upgrade. =) OMG, I do not think that somebody really forces me when to run apt-get upgrade and what packages to install and from what repository. Repeat, let there be easy downgrade option for the case things don't work as expected. man sources.list man apt_preferences http://snapshot.debian.net/ If you maintain more than one machine - setup a local repository and fill it with the versions of the packages you like. Including backported ones, learn how to backport. -- Odchádzajúca správa neobsahuje vírusy, nepou¾ívam Windows. === Mgr. Peter Tuhársky Referát informatiky Mesto Banská Bystrica ÈSA 26 975 39 Banská Bystrica Tel: +421 48 4330 118 Fax: +421 48 411 3575 === -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, 17 May 2007, Mgr. Peter Tuharsky wrote: This is closest to backports and volatile idea. I wouldn't call it backports however, because that reminds porting some very new software to some very old platform, and this is not the case. The stable's basic platform should stay LSB-compliant and moderately-aged (supported by all main software vendors) for the whole length of release cycle. Thus the new versions of desktop software wouldn't be backported; just compiled against ordinary, stable platform. That's precisely what a backport is. New versions of a Debian package compiled against stable with whatever changes are required to get them to compile. If the root of the concern is because the term backport is scary or otherwise unpalatable, then suggest an alternative term. Don Armstrong -- The attackers hadn't simply robbed the bank. They had carried off everything portable, including the security cameras, the carpets, the chairs, and the light and plumbing fixtures. The conspirators had deliberately punished the bank, for reasons best known to themselves, or to their unknown controllers. They had superglued doors and shattered windows, severed power and communications cables, poured stinking toxins into the wallspaces, and concreted all of the sinks and drains. In eight minutes, sixty people had ruined the building so thouroughly that it had to be condemed and later demolished. -- Bruce Sterling, _Distraction_ p4 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Mgr. Peter Tuharsky [EMAIL PROTECTED] writes: Yeas. Let the choice to the user. Don't dictate him. Whoever wants to use the old software w/o change, let be it. Whoever wants the new one, noticed about the risks, let's give him an official and supported way to do it. The user has that choice, to the extent that can be reasonably expected. Consider: The Debian project is run by volunteers: all the work done is done because someone sees value to themselves in doing it. Therefore, any official support can only be provided when a sufficient body of volunteers decide to provide it on a continuing basis. We have the Debian security team providing official support for released stable versions of Debian, according to a policy they voluntarily adhere to. Any other official support can only come about by a similar means: a sufficient body of people voluntarily organise themselves and put in the ongoing work to commit to and enact a support policy. You are welcome to help bring this about by any means you see fit, but harping on in this forum about lack of support is unlikely to have that result. This does not leave our users without other options. Anyone who wants support for Debian, beyond what official support is provided by volunteer efforts, need only speak with the many consultants who have listed themselves as providing support services for Debian. They can then negotiate an unofficial, customised support arrangement. I just don't see what more you're expecting to happen by posting to this thread. -- \ I'm a great lover, I'll bet. -- Emo Philips | `\ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, May 17, 2007 at 09:12:18AM +0200, Mgr. Peter Tuharsky wrote: Steve, I see main problem with testing that broad platform changes are going there. That's why things break sometimes there. That's why I think, that the Stable platform with new desktop software might be the choice -the new software versions with no platform dependecies breakage risk. This is closest to backports and volatile idea. I wouldn't call it backports however, because that reminds porting some very new software to some very old platform, and this is not the case. The stable's basic platform should stay LSB-compliant and moderately-aged (supported by all main software vendors) for the whole length of release cycle. Thus the new versions of desktop software wouldn't be backported; just compiled against ordinary, stable platform. This sounds more rational. Yes, the megafreeze model that Debian uses at the moment has certain drawbacks. However, my experience shows that currently it is the best one can get out of the free distros at the moment (with regard to stability), IMO. And I choose for stability. A base system (required utils + services + libs, 0 RC bugs) + script based automatic building/backporting system, similar to that used in testing, could be an option. This was discussed, i believe, many times in the past. -- Stanislav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, May 17, 2007 at 09:20:48AM +0200, Mgr. Peter Tuharsky wrote: Stanislav, I see Your point, however this is far from user-friendliness. First solution -use other distro. Wow, what a great idea. Looking at statistics and Linux users in neighborhood, You can be _sure_ they discovered that way already :-) Well, I think this is for the best. Be also sure, that unwilling to do more for desktop users, Debian will not be less, but increasingly more server-oriented distro (I like Debian on server!). I like Debian either. Debian will remain Debian ;) I really hope for it. Please, do not go for the stupid race over the so-called average (read not willing to learn) user. -- Stanislav -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: svn-buildpackage etc., mergeWithUpstream, and dpatch/quilt/cdbs again
tjena magnus, just a quick anecdotal experience to throw into the thread... for all its strengths and weaknesses, i'm pretty happy with svn-buildpackage, mergeWithUpstream, and a debian/patches dir. for a long time my biggest issue with this was having to maintain these patches across upstream changes, or introduce new patches. i (and i'm sure others) expressed this to the svn-buildpackage peeps, who responded with the svn-do command (dig around in /usr/share to find it), which i now use on a regular basis. svn-do + quilt has more or less[1] removed the annoyances of debian-only + debian/patches in svn. sean [1] there's still the issue of clutter left behind in build-area, but nothing a cronjob can't fix up. signature.asc Description: This is a digitally signed message part
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Hi, Don recent? current? upstream? fresh? :-) Why the need for volatile then? I admire I'm confused a bit. Whatever, there should be one supported, official, and acknowledged repository for the purpose, I think. Not necessarry ALL desktop software should be upgraded this way, however at least the most demanded mainstream.. The stable cycle should reflect the mainstream course, so that not much additional work should be necessarry to do that. Maybe the cycle should copy the LSB's one somehow. Peter Don Armstrong wrote / napísal(a): On Thu, 17 May 2007, Mgr. Peter Tuharsky wrote: This is closest to backports and volatile idea. I wouldn't call it backports however, because that reminds porting some very new software to some very old platform, and this is not the case. The stable's basic platform should stay LSB-compliant and moderately-aged (supported by all main software vendors) for the whole length of release cycle. Thus the new versions of desktop software wouldn't be backported; just compiled against ordinary, stable platform. That's precisely what a backport is. New versions of a Debian package compiled against stable with whatever changes are required to get them to compile. If the root of the concern is because the term backport is scary or otherwise unpalatable, then suggest an alternative term. Don Armstrong -- Odchádzajúca správa neobsahuje vírusy, nepou¾ívam Windows. === Mgr. Peter Tuhársky Referát informatiky Mesto Banská Bystrica ÈSA 26 975 39 Banská Bystrica Tel: +421 48 4330 118 Fax: +421 48 411 3575 === -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Ben, this is the most constructive advice on the topic I think :-) Thank You. Peter The user has that choice, to the extent that can be reasonably expected. Consider: The Debian project is run by volunteers: all the work done is done because someone sees value to themselves in doing it. Therefore, any official support can only be provided when a sufficient body of volunteers decide to provide it on a continuing basis. We have the Debian security team providing official support for released stable versions of Debian, according to a policy they voluntarily adhere to. Any other official support can only come about by a similar means: a sufficient body of people voluntarily organise themselves and put in the ongoing work to commit to and enact a support policy. You are welcome to help bring this about by any means you see fit, but harping on in this forum about lack of support is unlikely to have that result. This does not leave our users without other options. Anyone who wants support for Debian, beyond what official support is provided by volunteer efforts, need only speak with the many consultants who have listed themselves as providing support services for Debian. They can then negotiate an unofficial, customised support arrangement. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Am Mittwoch 16 Mai 2007 17:17 schrieb Steve Greenland: On 16-May-07, 06:24 (CDT), Mgr. Peter Tuharsky [EMAIL PROTECTED] wrote: It's been in context, meant as many of those problems -a relative part of problems, not absolute number of them. No, it's not worth the time. It's a history. The problem is that your history doesn't match the experience of any one else participating in this thread. You keep making assertions about testing being broken, sometimes with hundreds of broken dependencies. Since one of the key criterion of packages entering testing is dependencies are correct and fulfillable, this strikes most of us as unlikely. I won't claim testing has never had a broken depends, but it's very rare, and never hundreds of packages. Well, last time testing broke for me was the tetex-texlive transition with one texlive package failing in post-inst because of missing files in another. Solution was to take one package from unstable that fixed the issue. It is not very rare the case that such things happen. Another example are incomplete KDE transitions so that some stuff stops working. However, all of those cases are solvable by pinning to testing and sometimes using few packages from unstable. HS pgpE01GH74QFx.pgp Description: PGP signature
Reasons for recommends and suggests
Hi, what I am really missing in the current dependency scheme is WHY some packages define Recommends and Suggests on specific other packages. My problem with the current situation that you either do the policy of always installing such stuff or you don't. There is no way to decide case by case because there is definitely information missing in the description of packages. OK, some of those are obvious but some Recommends and Suggests are completely mysterious to me. And even after installation, I still don't know how those additional packages do extend/improve/whatever the originally wanted package. It would be nice if maintainers of packages with Recommends and Suggests that are non-obvious could state in the package description a reason for each of them. If I file bugs about them, which severity can this be given? HS pgpJARJsbLYxd.pgp Description: PGP signature
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Don, Volatile is for software which is known to be time critical, like virus and spam catching rules. Almost all Debian initiatives start as unofficial measures to demonstrate their efficacy. Eventually if they work and there is sufficient demand for them, they become official. Okay. It currently takes us a somewhere on the order of 100 person-years to release every single version of Debian. Woww. Just waving your hands and saing that not much additional work should be necessary isn't good enough. Right. Are there any real movements to synchronise Debian's cycle with LSB's one slightly? Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thursday 17 May 2007 11:29, Hendrik Sattler wrote: If I file bugs about them, which severity can this be given? I'd say wishlist. pgpQSnFwAHNE1.pgp Description: PGP signature
Re: Reasons for recommends and suggests
On Thu, May 17, 2007 at 11:29:16AM +0200, Hendrik Sattler wrote: Hi, what I am really missing in the current dependency scheme is WHY some packages define Recommends and Suggests on specific other packages. My problem with the current situation that you either do the policy of always installing such stuff or you don't. There is no way to decide case by case because there is definitely information missing in the description of packages. OK, some of those are obvious but some Recommends and Suggests are completely mysterious to me. And even after installation, I still don't know how those additional packages do extend/improve/whatever the originally wanted package. It would be nice if maintainers of packages with Recommends and Suggests that are non-obvious could state in the package description a reason for each of them. If I file bugs about them, which severity can this be given? What I thought about a while ago was this: --- Package: mutt Suggests: ispell [adds spell cheking while composing emails] Suggests: urlview [extracts urls from email and can lanuch a web browser] Suggests: mixmaster [allows you to compose anonymized email] - I'd see the maintainer create (or a user contribute) a 'short description' to accompany each suggest and recommends that is displayed $SOMEWHERE. So that the user can not just see a list of suggestions but a real reason as to why you'd want to install them. -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal |mysite.verizon.net/kevin.mark/| | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keyserver: subkeys.pgp.net | my NPO: cfsg.org | |join the new debian-community.org to help Debian! | |___ Unless I ask to be CCd, assume I am subscribed ___| signature.asc Description: Digital signature
Bug#424842: ITP: docbook2odf -- XSLT based conversions from docbook to Oasis Open Document (openoffice.org)
Package: wnpp Severity: wishlist Owner: Alexander Wirt [EMAIL PROTECTED] * Package name: docbook2odf Version : 0.211 Upstream Author : Roman Fordinal * URL : http://open.comsultia.com/docbook2odf/ * License : GPL Programming Lang: Perl Description : XSLT based conversions from docbook to Oasis Open Document (openoffice.org) toolkit that automaticaly converts DocBook to OASIS OpenDocument (ODF, the ISO standardized format used for texts, spreadsheets and presentations). Conversion is based on a XSLT which makes it easy to convert DocBook-ODF, ODT, ODS and ODP as all these documents are XML based. Alex -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (200, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.21.1 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mgr. Peter Tuharsky escribió: Stanislav, I see Your point, however this is far from user-friendliness. First solution -use other distro. Wow, what a great idea. Looking at statistics and Linux users in neighborhood, You can be _sure_ they discovered that way already :-) Be also sure, that unwilling to do more for desktop users, Debian will not be less, but increasingly more server-oriented distro (I like Debian on server!). I like Debian either. What about maintainer/developer-friendly thing? I mean, you want that us change all our infrastructure, but then he gives you as solution to change one line and exec one command and you think that's not user-friendly? There's no magical ways to do this, if you want newer packages then use lenny and if you want even more newer use sid. I use sid because of that and my system is pretty stable. Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDSzOKCtW8rKsRgRAv1yAJ9kd5ARNDxEsPct0rIdyyMosRrj2ACfQTRC 7yBRzG5rtH3LptRcnRJ8T7s= =9zdg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: svn-buildpackage etc., mergeWithUpstream, and dpatch/quilt/cdbs again
On Wednesday 16 May 2007 14:52, Marcus Better wrote: Magnus Holmgren wrote: Now, how do you combine these? Several people have thought: The VCS can handle the changesets. Putting patches under VCS is silly! I fully agree. Unfortunately Subversion doesn't make it easy for you. You can keep your patches in different feature branches, but it gets messy since Subversion doens't keep track of merges. Is there any fundamental misdesign in Subversion that prevents that from being implemented somewhere in the future? -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgp0xd84EkbeK.pgp Description: PGP signature
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Hi, Jose What about maintainer/developer-friendly thing? That'd be great. I think, the more recent is the supported software, and the more LSB-compliant is the base, the less extraordinary work for developers and less concern for end users. This dosen't conflict with either philosophy here. I mean, you want that us change all our infrastructure I think the LSB-compliance and reasonably short (or reasonably long) release cycle are inevitable goals. The sooner achieved (naturally), the better. We discussed here, that backports is the best thing to start with in order to deliver recent desktop software to the end user, so it just needs an official approval and support. Those are the direct infrastructure changes that it is being spoken about. This is not anything that would ruin Debian into chaos ;-) Next thing, quite utopistic one but inevitable in long terms, should be the common infrastructure for bug reporting, so that users would report bugs easily, and the developers would not need to interchange the bug data between users and upstream, but upstream would get them directly instead. This is just an idea, however some beginning of that is being worked on there in Canonical, AFAIK. , but then he gives you as solution to change one line and exec one command and you think that's not user-friendly? There's no magical ways to do this If the option was only obvious, advertised and easily found and done by ordinary end user, without risk of breaking deps.. Friendly, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424844: ITP: ircservices -- Nick/channel/other services for IRC networks
Package: wnpp Severity: wishlist Owner: Tim Retout [EMAIL PROTECTED] * Package name: ircservices Version : 5.1pre1 Upstream Author : Andrew Church [EMAIL PROTECTED] * URL : http://www.ircservices.za.net/ * License : GPLv2 Programming Lang: C Description : Nick/channel/other services for IRC networks IRC Services is a system of services to be used with Internet Relay Chat networks. It provides for definitive nickname and channel ownership, as well as the ability to send messages (memos) to offline users, and gives IRC operators considerably more control over the network. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thu, May 17, 2007, Kevin Mark wrote: What I thought about a while ago was this: --- Package: mutt Suggests: ispell [adds spell cheking while composing emails] Suggests: urlview [extracts urls from email and can lanuch a web browser] Suggests: mixmaster [allows you to compose anonymized email] - I'd see the maintainer create (or a user contribute) a 'short description' to accompany each suggest and recommends that is displayed $SOMEWHERE. So that the user can not just see a list of suggestions but a real reason as to why you'd want to install them. I find your proposed extension of the format of control headers very inspiring; perhaps it makes sense to spec an extension to this format to permit various transversal information to be stored. Other header based formats/protocols such as HTTP or RFC 2822 permit things like: Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=zYM0uCDKw75PZbzx or: Content-Type: text/html; charset=iso-8859-1 but I don't see any similar way of attaching meta-information to lists in a single header; your solution would be one (which is already used for architecture information unfortunately), another one could be: Suggests: mixmaster?description=allows%20anonymizing%20emails, urlview?description=extracts%20urls%20from%20emailpriority=10 -- Loïc Minier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424844: ITP: ircservices -- Nick/channel/other services for IRC networks
On Thu, 2007-05-17 at 13:41 +0200, Kurt Roeckx wrote: On Thu, May 17, 2007 at 11:59:41AM +0100, Tim Retout wrote: IRC Services is a system of services to be used with Internet Relay Chat networks. It provides for definitive nickname and channel ownership, as well as the ability to send messages (memos) to offline users, and gives IRC operators considerably more control over the network. We have a few irc server packages in Debian. It's unlikely that it works with all of them. Do you know with which it does work? Several, according to the table at: http://www.ircservices.za.net/download/testing/docs/2.html#1 I've tested with ircd-hybrid, but it should also do ircd-ircu and ircd-irc2. It might work with oftc-hybrid, if it's a close enough fork of ircd-hybrid, but I'm not sure. That leaves dancer-ircd, ngircd and rageircd, with which I assume it doesn't work. -- Tim Retout [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Bug#424844: ITP: ircservices -- Nick/channel/other services for IRC networks
On Thu, May 17, 2007 at 01:04:21PM +0100, Tim Retout wrote: On Thu, 2007-05-17 at 13:41 +0200, Kurt Roeckx wrote: Several, according to the table at: http://www.ircservices.za.net/download/testing/docs/2.html#1 I've tested with ircd-hybrid, but it should also do ircd-ircu and ircd-irc2. It might work with oftc-hybrid, if it's a close enough fork of ircd-hybrid, but I'm not sure. That leaves dancer-ircd, ngircd and rageircd, with which I assume it doesn't work. ircd-irc2 is not on that list. It does mention the 2.8 version, but 2.9, 2.10 and specially 2.11 have different server-server protocols. The current 2.11 now refuses to talk to anything that doesn't claim it supports 2.11, and we removed most of the backward compatibility code. It's unlikely that it'll work with it if it's not mentioned. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: svn-buildpackage etc., mergeWithUpstream, and dpatch/quilt/cdbs again
Le jeudi 17 mai 2007 à 13:12 +0200, Magnus Holmgren a écrit : On Wednesday 16 May 2007 14:52, Marcus Better wrote: Magnus Holmgren wrote: Now, how do you combine these? Several people have thought: The VCS can handle the changesets. Putting patches under VCS is silly! I fully agree. Unfortunately Subversion doesn't make it easy for you. You can keep your patches in different feature branches, but it gets messy since Subversion doens't keep track of merges. Is there any fundamental misdesign in Subversion that prevents that from being implemented somewhere in the future? You can use one of the svnmerge scripts instead of svn merge to do things the git way. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Re: Bug#424844: ITP: ircservices -- Nick/channel/other services for IRC networks
Tim Retout writes: On Thu, 2007-05-17 at 13:41 +0200, Kurt Roeckx wrote: On Thu, May 17, 2007 at 11:59:41AM +0100, Tim Retout wrote: IRC Services is a system of services to be used with Internet Relay Chat networks. It provides for definitive nickname and channel ownership, as well as the ability to send messages (memos) to offline users, and gives IRC operators considerably more control over the network. We have a few irc server packages in Debian. It's unlikely that it works with all of them. Do you know with which it does work? Several, according to the table at: http://www.ircservices.za.net/download/testing/docs/2.html#1 I've tested with ircd-hybrid, but it should also do ircd-ircu and ircd-irc2. It might work with oftc-hybrid, if it's a close enough fork of ircd-hybrid, but I'm not sure. That page shows compatibility with ircd-ircu 2.9.x using the p9 protocol. That is at least eight years old (ircu's current CVS archive does not go back far enough to show any 2.9 release), and the p9 protocol is not supported by the version of ircu that is currently in Debian. A quick glance at both the 5.0.61 and 5.1-pre1 source code for ircservices shows that it still uses p9 rather than p10. Michael Poole -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424844: ITP: ircservices -- Nick/channel/other services for IRC networks
On Thu, 2007-05-17 at 14:25 +0200, Kurt Roeckx wrote: On Thu, May 17, 2007 at 01:04:21PM +0100, Tim Retout wrote: On Thu, 2007-05-17 at 13:41 +0200, Kurt Roeckx wrote: Several, according to the table at: http://www.ircservices.za.net/download/testing/docs/2.html#1 I've tested with ircd-hybrid, but it should also do ircd-ircu and ircd-irc2. It might work with oftc-hybrid, if it's a close enough fork of ircd-hybrid, but I'm not sure. That leaves dancer-ircd, ngircd and rageircd, with which I assume it doesn't work. ircd-irc2 is not on that list. It does mention the 2.8 version, but 2.9, 2.10 and specially 2.11 have different server-server protocols. The current 2.11 now refuses to talk to anything that doesn't claim it supports 2.11, and we removed most of the backward compatibility code. Whoops, my mistake. I'm sure it's possible to add support. -- Tim Retout [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, May 17, 2007 at 07:56:57AM +0200, Mgr. Peter Tuharsky wrote: Yes, I have written it there too. Kernel is, IMO, the best thing to upgrade few times during release cycle, with quite little risk. Upgrading the kernel is quite high risk. Features come and go and change with each new kernel. Drivers break in some releases, although usually only for less common hardware that no one tested during the development of that release, or new features are added that require updated user space tools, etc. For example 2.6.16 and higher tag all netkey ipsec packets with a policy tag of 'ipsec'. Before 2.6.16 they didn't. So going to 2.6.16 or higher broke shorewall in sarge since it didn't know about the new policy, and it required a newer version of iptables since it too had to support this new behaviour. Do you think people with ipsec tunnels would be happy if it stopped working just because of a kernel upgrade added to support all the people who just have to have support for their latest machine in debian's stable release that was made before the hardware in their new machine even existed? Yes, Debian was the last distro using Xfree86 I know. Of course the transition was complex! Sure seems much better with x.org than xfree86 though. That should be changed anyway, since security upgrades occasionally break things too. Downgrades are in general imposible to do, unless you put in a lot of useless code that will never be used except when downgrading, which of course will be used so rarely that it will be full of bugs due to not ever being tested by anyone. Remember upgrades sometimes have to convert files to a new format. A new package can do this because at the time it was made, the maintainer knew about the older versions already made. If you try to install an older package, there is no way at the time that older package was made to know how to convert from a newer file format back to the old one. So to solve this you would now have to add some kind of downgrade feature to the scripts of the new package that could be called before going to an older package. Sometimes data is no longer used and dropped from a file format, or new stuff is added. If stuff was dropped how are you going to restore it on the downgrade? If stuff was added I guess you can just throw it away on a downgrade. But overall supporting downgrades requires a time machine and lots of generally untested support code. I wouldn't want to try to support that. Of course often there is no change to the data or config files, and you can simply install the old package again using whatever package tool you like to use by telling it what version to install. So unofficially downgrading is possible most of the time, but when it isn't, supporting it isn't worth trying. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, 2007-05-17 at 07:56 +0200, Mgr. Peter Tuharsky wrote: Michelle Konzack said: You forger that DOWNGRADING is officialy NOT SUPPORTED by Debian. That should be changed anyway, since security upgrades occasionally break things too. You keep saying this, I haven't seen this in Sarge at all. Sarge has had HOW MANY security updates that broke things? Etch's security updates including the Kernel upgrade had no noticeable problems... but of course the two *OBSCURE* issues reported affect you, right? You keep trying to HIT these things home, but the more you do this, the more you look foolish. These problems are mainly Woody and before, except for the LONG release time for Sarge. The Woody security updates for Mozilla was REALLY HARD. I am beginning to understand that you want Debian with completely new userland programs. That would be Testing or CUT as Joey Hess has promoted. You could also use Sidux, which is a distro that uses sid as the base and does minor stabilization. http://sidux.com/ -- greg, [EMAIL PROTECTED] PGP key: 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0 signature.asc Description: This is a digitally signed message part
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Thu, May 17, 2007 at 08:10:21AM +0200, Mgr. Peter Tuharsky wrote: Yes, and security upgrades never change behaviour of software and never break things. That's the way it OUGHT to be. The reality has its own turbulences. I don't remember security upgrades ever breaking anything in testing. I am sure it must have happened at some point, but the security team appears to take their work very very seriously. Well, I might have been out of luck. Maybe it hasn't been hudreds, just a full screen of (didn't count them and wouldn't remember anyway). That changes nothing on assertion, that using the testing routinely is not official, nor advisable way for ordinary users. See below. My original intention was not, and still is not, to discuss capabilities of testing. I want to discuss possibilities, how could the stable be more attractive for ordinary user, how to make it usable on hardware newer-than-3-years-old, how could the user be blessed with fresh software rather than 2-years old, how to allow him to easily and effectively participate on bug reporting, and how to avoid the work of backporting security fixes to ancient software. The answer to all of those is 'testing'. That is all stuff stable is definitely not meant to do. If You and several people claim they haven't met such problems with testing, I can live with that. I also heard people whose experience was different, and my personal one is closer to them. That's all. All it takes is one package that has a dependancy problem to prevent hundreds of other packages from upgrading or installing fully. It looks like everything is broken, when all it really is is just one missing or broken package. When you know how to read what the upgrade system tells you you can usually deal with it or put the right things on hold for a few days while the missing package makes it in to testing. In unstable there are occationally bad packages uploaded that break things enough that you just have to wonder if the maintainer even tried to install it themselves. :) Usually there will be an answer to how to go back or fix it on the debian irc channel already. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424875: ITP: libical0 -- libical offers parsing of ical text data.
Package: wnpp Severity: wishlist Owner: Wilfried Goesgens [EMAIL PROTECTED] * Package name: libical0 Version : 0.27.1 Upstream Author : Art Cancro [EMAIL PROTECTED] * URL : http://freeasociation.sf.net * License : (LGPL/MPL Dual license) Programming Lang: (C) Description : libical offers parsing of ical text data. The ICal library was originaly maintained by Eric Busboom and Andrea Campi. Its new Maintainer is Art Cancro. Its used by the Citadel Project, Kontact and Evolution (in forked versions). This release contains the patches from the forks. The Citadel ITP #423911 depends on this. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.20 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424875: ITP: libical0 -- libical offers parsing of ical text data.
Hi I wanted to find out more about this library, but... On Thu, 17 May 2007 16:27:31 +0200 Wilfried Goesgens [EMAIL PROTECTED] wrote: Package: wnpp Severity: wishlist Owner: Wilfried Goesgens [EMAIL PROTECTED] * Package name: libical0 Version : 0.27.1 Upstream Author : Art Cancro [EMAIL PROTECTED] * URL : http://freeasociation.sf.net An error has been encountered in accessing this page. 1. Server: freeasociation.sourceforge.net 2. URL path: / 3. Error notes: File does not exist: /home/groups/f/fr/freeasociation/htdocs/ 4. Error type: 404 5. Request method: GET 6. Request query string: 7. Time: 2007-05-17 08:02:07 PDT (1179414127) -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: Bug#424875: ITP: libical0 -- libical offers parsing of ical text data.
* URL : http://freeasociation.sf.net just a typo, there's a s missing: http://freeassociation.sf.net -- Bernd Zeimetz [EMAIL PROTECTED] http://bzed.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424875: ITP: libical0 -- libical offers parsing of ical text data.
typo: http://freeassociation.sourceforge.net/ two s's in association. Qui, 2007-05-17 às 17:03 +0200, Michal Čihař escreveu: Hi I wanted to find out more about this library, but... On Thu, 17 May 2007 16:27:31 +0200 Wilfried Goesgens [EMAIL PROTECTED] wrote: Package: wnpp Severity: wishlist Owner: Wilfried Goesgens [EMAIL PROTECTED] * Package name: libical0 Version : 0.27.1 Upstream Author : Art Cancro [EMAIL PROTECTED] * URL : http://freeasociation.sf.net An error has been encountered in accessing this page. 1. Server: freeasociation.sourceforge.net 2. URL path: / 3. Error notes: File does not exist: /home/groups/f/fr/freeasociation/htdocs/ 4. Error type: 404 5. Request method: GET 6. Request query string: 7. Time: 2007-05-17 08:02:07 PDT (1179414127) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424880: ITP: libl2fprod-common-java -- additional Java components for modern user interfaces
Package: wnpp Severity: wishlist Owner: Torsten Werner [EMAIL PROTECTED] * Package name: libl2fprod-common-java Version : 7.3+20070317 Upstream Author : L2FProd.com [EMAIL PROTECTED] * URL : http://common.l2fprod.com/ * License : Apache Programming Lang: Java Description : additional Java components for modern user interfaces Swing has lot of components built-in but still some are missing. This project provides the developer community with these missing components, components inspired from modern user interfaces: - PropertySheet - JTaskPane and JTaskPaneGroup - JButtonBar - JOutlookBar - JFontChooser and JDirectoryChooser - JTipOfTheDay - ... and others . Homepage: http://common.l2fprod.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424890: RFA: gkrellm -- The GNU Krell Monitors
Package: wnpp Hi, I am looking for someone who use it regularly to adopt this package. I have not used it for a long time. The package is in a good shape, and the upstream is pretty active. Cai Qian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thu, 17 May 2007 11:29:16 +0200 Hendrik Sattler [EMAIL PROTECTED] wrote: Hi, what I am really missing in the current dependency scheme is WHY some packages define Recommends and Suggests on specific other packages. I use Recommends or Suggests when the package includes a variety of scripts with broadly related purposes. The main Depends: line is determined by a core set of scripts (which may be described in detail in the long description) but if there are a couple of optional scripts that some people may like to use but which aren't strictly essential to the use of the package, then those dependencies get put into Recommends or Suggests. The meaning, to me, is: Recommends: needed or useful in conjunction with optional or limited usage scenarios where alternative methods may exist. Suggests: Not a strict dependency of any script in the package, just useful for helping the user find their way around the package. e.g. dwww for docs. My problem with the current situation that you either do the policy of always installing such stuff or you don't. There is no way to decide case by case because there is definitely information missing in the description of packages. You install a Recommends or Suggests when you want to use some part of the package that uses it. The obvious place to document such requirements is the manpage for the optional script. In most cases, users simply don't need to use those options. e.g. emdebian-tools Recommends subversion because although the core emdebian-tools scripts can be used without subversion, there is an optional script which requires subversion. Not everyone using emdebian-tools needs to use the optional script (emsource) because emsource is a cross-build-aware wrapper for 'apt-get source' that also manages the Emdebian SVN. If you aren't using the Emdebian SVN, emsource is of little use to you. Making subversion a dependency of emdebian-tools would be pointless. Having said that, emsource is becoming more like a core script and a later release may deprecate using apt-get source directly and migrate emsource into the core. OK, some of those are obvious but some Recommends and Suggests are completely mysterious to me. Until you use the package and come up against the one area where the Recommended package is actually useful, this is to be expected. Until you need to use that one option, there is no need for you to be concerned. At the point where you need that option, the manpage for that script or program should explain the role of the recommended package. And even after installation, I still don't know how those additional packages do extend/improve/whatever the originally wanted package. That isn't a problem - when you want to use a particular feature, the manpage should provide the info you need. It would be nice if maintainers of packages with Recommends and Suggests that are non-obvious could state in the package description a reason for each of them. Package descriptions can be long enough as it is - IMHO the best place for this information is the manpage. Things like Recommends often needs context - the reason for using the recommended package needs to be explained in relation to the rest of the scripts and the overall purpose of the package. There is no room to do that in the description. If I file bugs about them, which severity can this be given? wontfix. ;-) The location of this information should be the manpage, IMHO. Moreover, it should be the manpage of the specific program/script that uses or is related to the recommended package. The only bug suitable for this scenario is a wishlist bug for a more verbose manpage. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpyK5EmvWQUQ.pgp Description: PGP signature
Bug#424893: ITP: cmigrep -- search in ocaml compiled interface files
Package: wnpp Severity: wishlist Owner: Ralf Treinen [EMAIL PROTECTED] * Package name: cmigrep Version : 1.3 Upstream Author : Eric Stokes * URL : http://homepage.mac.com/letaris/ * License : GPL Programming Lang: OCaml Description : search in ocaml compiled interface files This program allows you to search for items (like for instance types, constructors, or exceptions) in compiled interface files generated by the Objective Caml compiler. Note: this software is currently contained in the catch-all package ocaml-tools. I intend to split off cmigrep from ocaml-tools. -Ralf, -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-486 Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US.ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thu, May 17, 2007 11:58, Kevin Mark wrote:
Package: mutt
Suggests: ispell [adds spell cheking while composing emails]
Suggests: urlview [extracts urls from email and can lanuch a web browser]
Suggests: mixmaster [allows you to compose anonymized email]
This seems like a useful idea to me. As a technical detail, I'd use '('
and ')' because those are used for optional comments in the RFC822 format
already.
On Thu, May 17, 2007 19:22, Neil Williams wrote:
The only bug suitable for this scenario is a wishlist bug for a more
verbose manpage.
It seems cumbersome to me to be presented with a list of recommends and
suggests at install time, ignore that and finish install, read the manpage
and then go back to the package manager to install extra packages. I'd
rather just make that decision when I'm at the root prompt anyway.
Thijs
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#424875: ITP: libical0 -- libical offers parsing of ical text data.
On Thu, 2007-05-17 at 16:27 +0200, Wilfried Goesgens wrote: * Package name: libical0 Although I'm might not be up-to-date on the library naming scheme[0], I'm pretty sure a zero should go on the end of the binary package's name, only the source package, which is what is being asked for above. The ICal library was originaly maintained by Eric Busboom and Andrea Campi. Its new Maintainer is Art Cancro. libical is currently not in Debian, but there is an ITP for libical[1] already. Now, looking at this other libical[2], it is clear that it is a modified version of the original libical project, where the original libical project is what this ITP is for. So are these two ical libraries both needed in Debian? What is the difference between them? Its used by the Citadel Project, Kontact and Evolution (in forked versions). This release contains the patches from the forks. The Citadel ITP #423911 depends on this. Interestingly, when I asked about the other libical's status in the bug report[1] for another reason, the owner of the bug reported that they were working on libical for Citadel too -- this is the main thing that makes me think that there is no need for two these two versions in Debian, if they both being packaged with Citadel in mind (ie. I assume they both work with Citadel). I hope I'm understanding everything here -- I'm no expert on anything ical-related, otherwise please correct me here! Regards, [0] http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html [1] http://bugs.debian.org/404862 [2] http://www.aurore.net/projects/libical/ -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402 signature.asc Description: This is a digitally signed message part
Re: Bug#364438: broken afer upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey, this is a very old bug about an upgrade a year ago, no one confirms it, should I close it? Refer to http://bugs.debian.org/364438 for more info. Regards, Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTKDfOKCtW8rKsRgRAqXaAJ9MWbIgyaKPJeDzMkV/iBfbBb05vACfbDBT tCtrhQI8hNz/AGJRr2zD8G4= =Z03x -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thu, 17 May 2007 19:53:07 +0200 (CEST)
Thijs Kinkhorst [EMAIL PROTECTED] wrote:
On Thu, May 17, 2007 11:58, Kevin Mark wrote:
Package: mutt
Suggests: ispell [adds spell cheking while composing emails]
Suggests: urlview [extracts urls from email and can lanuch a web browser]
Suggests: mixmaster [allows you to compose anonymized email]
This seems like a useful idea to me. As a technical detail, I'd use '('
and ')' because those are used for optional comments in the RFC822 format
already.
() are used for dependencies in other control fields - I would see '('
as a recipe for confusion.
On Thu, May 17, 2007 19:22, Neil Williams wrote:
The only bug suitable for this scenario is a wishlist bug for a more
verbose manpage.
It seems cumbersome to me to be presented with a list of recommends and
suggests at install time, ignore that and finish install, read the manpage
and then go back to the package manager to install extra packages. I'd
rather just make that decision when I'm at the root prompt anyway.
? sudo ?
Most users don't need to use the packages given as Recommends or
Suggests so the purpose, as I see it, is to help those who have unusual
or extended needs for the functions provided by the package. Are you
likely to know whether this is appropriate until you've had a chance to
use the package?
BTW: read which manpage? My example is from a package that is a
toolset. Out of the collection, only one script needs subversion right
now. There are multiple manpages in the package - only one describes
the role of subversion. Understanding whether you need that
functionality requires context - you cannot necessarily decide upon a
crude one-liner.
Take another package of mine: pilot-qof.
Recommends: libqof-backend-sqlite0, datafreedom-qsfxsl, datafreedom-perl
Suggests: datafreedom-doc
To me, the purpose of these two lines is simple: highlight that these
packages are related to pilot-qof in some way. If the user wants to
find out more, man pilot-qof is the only sensible option because the
purpose of each recommendation or suggestion needs to be explained
within the context of what the package itself can actually achieve.
Over-simplification doesn't do anyone any favours - it can promote
something that the package cannot do or it can omit something that the
package can do. Some things just need to be explained in detail,
within the overall context of the relevant packages. That is one of the
purposes of a manpage, IMHO. To let the user find out How do I use X?
In turn: datafreedom-qsfxsl:
Recommends: pilot-qof, gpe-expenses, zenity, datafreedom-doc
Suggests: calcurse, dlume, dates, contacts, gpe-contacts, gpe-calendar
These are some of the applications that can import or convert data
converted by the XSL within the package or are used by scripts based on
the XSL in some way.
Full details of what fits where and when one package is recommended
over another from the same list cannot be contained within an
over-simplified one-liner. These details are in the manpage(s) and
further documented in the suggested -doc package.
It's my way of saying that if you use any of the suggested packages,
some of the recommended packages can be used to share data with the
applications that you actually use. None are essential, I doubt that
anyone, except me, has all of the recommended and suggested packages
installed. You cannot sensibly make the choice until you've tried out
the package and decided which other package and which scripts best fit
your needs.
This problem is common to all kinds of toolset, conversion,
inter-operability and data synchronisation packages.
--
Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgp1PLHqXPiDI.pgp
Description: PGP signature
Re: Reasons for recommends and suggests
On Thu, May 17, 2007 at 07:43:09PM +0100, Neil Williams wrote: Most users don't need to use the packages given as Recommends or Suggests so the purpose, as I see it, is to help those who have unusual or extended needs for the functions provided by the package. You are at odds with Policy with regard to most users and Recommends here, as I read it. Section 7.2: `Recommends' This declares a strong, but not absolute, dependency. The `Recommends' field should list packages that would be found together with this one in all but unusual installations. In other words, most users _will_ need to use the packages given as Recommends (which is why aptitude installs them by default). Suggests is a completely different game, though. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: svn-buildpackage etc., mergeWithUpstream, and dpatch/quilt/cdbs again
On Thursday 17 May 2007 05:12:52 Magnus Holmgren wrote: On Wednesday 16 May 2007 14:52, Marcus Better wrote: Magnus Holmgren wrote: Now, how do you combine these? Several people have thought: The VCS can handle the changesets. Putting patches under VCS is silly! I fully agree. Unfortunately Subversion doesn't make it easy for you. You can keep your patches in different feature branches, but it gets messy since Subversion doens't keep track of merges. Is there any fundamental misdesign in Subversion that prevents that from being implemented somewhere in the future? No, merge tracking has been in the Subversion roadmap for a long time, but has been lower priority than other things. However, merge tracking is now one of the highest priorities. Basic merge tracking is scheduled to be in the next release; more enhancements will follow. -- Wesley J. Landaker [EMAIL PROTECTED] xmpp:[EMAIL PROTECTED] OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 pgpe1ImNx2h76.pgp Description: PGP signature
Bug#424909: ITP: lbrc -- Linux Bluetooth Remote Control Server
Package: wnpp Severity: wishlist Owner: Patrick Winnertz [EMAIL PROTECTED] * Package name: lbrc Version : 0.4 Upstream Author : Matthias Blaesing [EMAIL PROTECTED] * URL : http://lbrc.berlios.de/ * License : GPL Programming Lang: (C, C++, C#, Perl, Python, etc.) Description : Linux Bluetooth Remote Control Server Allows a J2ME device to control the Linux PC. This application allows: * injection of mouse/keyboard events into the kernel * execution of custom commands * DBUS interaction * a module offering a mplayer to be controlled by the phone -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21.1 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424925: ITP: libjcalendar-java -- Java date chooser bean for graphically picking a date
Package: wnpp Severity: wishlist Owner: Torsten Werner [EMAIL PROTECTED] * Package name: libjcalendar-java Version : 1.3.2 Upstream Author : Kai Toedter * URL : http://www.toedter.com/en/jcalendar/ * License : LGPL Programming Lang: Java Description : Java date chooser bean for graphically picking a date JCalendar is composed of several other Java beans, a JDayChooser, a JMonthChooser and a JYearChooser. All these beans have a locale property, provide several icons (Color 16x16, Color 32x32, Mono 16x16 and Mono 32x32) and their own locale property editor. So they can easily be used in GUI builders. Also part of the package is a JDateChooser, a bean composed of an IDateEditor (for direct date editing) and a button for opening a JCalendar for selecting the date. . Homepage: http://www.toedter.com/en/jcalendar/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug Squashing Party -- May 17th - 20th
Luk Claes wrote: David Claughton wrote: Is it useful to have bugs already fixed in sid included in the list for BSP purposes? I would have thought bydist=both would be more appropriate. You might want to read the section Testing-only bugs at [0] on why lenny-only bugs might also be interesting to fix. Cheers Luk [0] http://people.debian.org/~vorlon/rc-bugsquashing.html I think I see - the bugs themselves don't need fixing, it's just a case of keeping an eye on the situation to ensure the updated package isn't being held up entering testing. Thanks for the clarification. Dave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thu, May 17, 2007 at 07:53:07PM +0200, Thijs Kinkhorst wrote:
On Thu, May 17, 2007 11:58, Kevin Mark wrote:
Package: mutt
Suggests: ispell [adds spell cheking while composing emails]
Suggests: urlview [extracts urls from email and can lanuch a web browser]
Suggests: mixmaster [allows you to compose anonymized email]
This seems like a useful idea to me. As a technical detail, I'd use '('
and ')' because those are used for optional comments in the RFC822 format
already.
On Thu, May 17, 2007 19:22, Neil Williams wrote:
The only bug suitable for this scenario is a wishlist bug for a more
verbose manpage.
It seems cumbersome to me to be presented with a list of recommends and
suggests at install time, ignore that and finish install, read the manpage
and then go back to the package manager to install extra packages. I'd
rather just make that decision when I'm at the root prompt anyway.
I agree. There are different users, not all are 'programmers', some are
gui-desktop-users ( and as such should not be ignored and expect only
'programmers' to be using your programs) and all they want to know is
how will this 'suggest'ed program enhance my program. If you are using
synaptic or aptitude and just about to select evolution to install it
and want to connect to exchange then you should not have to first know
how to install and configure an exchange server, read all its manuals,
then read all of evolutions documentation and man pages just to know
that you need to add 'evolution-exchange' to your selection on the
synaptic or aptitude screen before you install them. Also, not every
package should be required to add these descriptions as the
'programmer'-users will either already know what to install or will in
fact read all the man pages and thus find out what to install.
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System| go to counter.li.org and |
| `-http://www.debian.org/ |be counted! #238656 |
| my keyserver: subkeys.pgp.net | my NPO: cfsg.org |
|join the new debian-community.org to help Debian! |
|___ Unless I ask to be CCd, assume I am subscribed ___|
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On 17-May-07, 06:23 (CDT), Mgr. Peter Tuharsky [EMAIL PROTECTED] wrote: I think the LSB-compliance and reasonably short (or reasonably long) release cycle are inevitable goals. The sooner achieved (naturally), the better. You know, Debian has been discussing how to speed up releases while supporting many architectures and still maintaining our strong reputation for a technically solid and stable system for oh, about 10 years now. Lots and lots of people have worked on this. We've gotten better. Not perfect, by any means, but not bad. In particular, we've tried to balance the needs of a variety of users, which means that many users are not going to be perfectly satisfied. Some people have seen one of our weaknesses (up-to-date desktop software), and built a buisness out of it. I say good for them. Debian *can't* be all things to all people. Let some other people work on particular problems. We'll learn from them, and they'll learn from us. Isn't that one of the points of free software, that we don't have to duplicate everything? Next thing, quite utopistic one but inevitable in long terms, should be the common infrastructure for bug reporting, so that users would report bugs easily, and the developers would not need to interchange the bug data between users and upstream, but upstream would get them directly instead. That doesn't work. A lot of upstream authors don't want to hear about Debian specific bugs. The user doesn't want to (and often can't) distinguish between Debian and upstream bugs. We make it easy to report bugs to us, and it's our job to work from there. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: update-initramfs -k all -u
On Wed, May 16, 2007 at 12:23:55AM +0200, martin f krafft wrote: also sprach Tim Dijkstra [EMAIL PROTECTED] [2007.05.15.2201 +0200]: Now what do people think is the best option? (And why?) I use -k all in mdadm already. I could not find any reasons why that would not be a good idea. The reason I didn't use it in cryptsetup's initramfs script was that many people who have 1 kernel use the second one as a fallback. In case the updated version of the package which calls update-initramfs in its postinst contains some grave bug which renders the initramfs image useless, the old one will still be there... -- David Härdeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
Neil == Neil Williams [EMAIL PROTECTED] writes: Neil The only bug suitable for this scenario is a wishlist bug Neil for a more verbose manpage. I want to know if I should install the package recommendations or not when I install the package. Unfortunately you cannot see the man pages until after the package is installed. Also aptitude will by default install all recommendations. Sometimes recommendations include packages that appear to be excessive. Do I really need to install the kernel source to get this package working? Maybe not (sorry can't remember the package that did this now). Other times the recommendations will conflict with other things I have installed. I want to know at the time of installing a new kernel, in aptitude, for example, if and why I should allow aptitude to continue its favoured approach to install the recommended libc6-i686 and remove the conflicting libc6-xen package. Anybody who knows xen would also know that I should keep libc6-xen, but there are lots of cases when I am just trying out a new package for the first time and I don't yet know what features I will need or not need. This in turn can result in errors when experimenting with new packages where it is not immediately obvious it is due to a package that is not installed that perhaps should be. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
Neil Williams wrote: You install a Recommends or Suggests when you want to use some part of the package that uses it. The obvious place to document such requirements is the manpage for the optional script. In most cases, users simply don't need to use those options. Recommends/Suggests aren't only for stuff required for specific scripts inside a package, and it's not always that obvious that a script or program may require extra libs. For example, I still wonder why the hell openoffice.org-core recommends nfs-common. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Fri, 18 May 2007, Brian May wrote: Neil == Neil Williams [EMAIL PROTECTED] writes: Neil The only bug suitable for this scenario is a wishlist bug Neil for a more verbose manpage. I want to know if I should install the package recommendations or not when I install the package. The recommends should be a set such that you'd want to install them, unless you know specifically why you don't. [In the majority of cases that I've personally run into, this means unusual setups like a separate database server, stripped installs, etc.] Moreover, the information necessary to explain what packages that are Recommends: or Suggests: actually do and the additional features they require is not something that can be easily jammed into the Description without making the description uselessly long. The Description should give you enough information to figure out whether or not you want to install a package, not telling you how to use the package or the descriptions of other packages that the package Recommends: or Suggests:. That kind of documentation really belongs in README.Debian or other documentation included with the package. Don Armstrong -- All bad precedents began as justifiable measures. -- Gaius Julius Caesar in The Conspiracy of Catiline by Sallust http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apparently-corrupted-elf-binary lintian problems on recent sid and amd64
Hi, So I entered the pbuilder amd64 sid chroot and there objdump -T works correct. I installed lintian in the chroot and it doesn't return any error. So amd64 etch objdump doesn't seem to be compatible with amd64 sid compiled binaries. I didn't bother to search for the real reason, but upgrading gcc-4.1 (and what it brings as Deps) to sid fixed those problems for me. Cheers, Bernd -- Bernd Zeimetz [EMAIL PROTECTED] http://bzed.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reasons for recommends and suggests
On Thu, May 17, 2007 at 06:22:11PM +0100, Neil Williams [EMAIL PROTECTED] was heard to say: On Thu, 17 May 2007 11:29:16 +0200 Hendrik Sattler [EMAIL PROTECTED] wrote: My problem with the current situation that you either do the policy of always installing such stuff or you don't. There is no way to decide case by case because there is definitely information missing in the description of packages. You install a Recommends or Suggests when you want to use some part of the package that uses it. The obvious place to document such requirements is the manpage for the optional script. In most cases, users simply don't need to use those options. When aptitude displays its list of here's what I'll do, there's a section for packages being automatically installed, and one for recommended/suggested packages that are not being installed. Right now it says things like: foo recommends bar (= 1.2.3) I would really like to have it say: foo recommends bar (= 1.2.3) to frobnicate the whazzit. My thought on this topic has been to do something like: Recommends-Reason: bar (= 1.2.3); to frobnicate the whazzit. These fields would be purely decorative, so they could be ignored by the core algorithms (no need to rewrite dpkg's Depends parsing). They also don't clutter up the Depends line, which is IMO likely to be important if you're just trying to read through the dependencies. My general feeling is that these would be unlikely to have enough uptake to justify implementing them...but if a patch were to drop from heaven (or I suddenly found that I had a week of free time, hah) I would be happy to give it a shot. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITP: libasterisk-agi-perl -- Asterisk::AGI Module.
Package: wnpp Owner: Rene Mayorga [EMAIL PROTECTED] Severity: wishlist * Package name: libasterisk-agi-perl * Version : 0.09 * Upstream Author : James Golovich [EMAIL PROTECTED] * URL : http://search.cpan.org/~jamesgol/asterisk-perl-0.09/ * License : Artistic License * Description : Collections of Perl modules to be used with Asterisk PBX AGI Asterisk::AGI is a Perl extension that provides a simple and easy writing way for Asterisk Gateway Interface(Asterisk). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.18.3-ch2.0 (PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash signature.asc Description: This is a digitally signed message part
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Look Greg, in the original post, I referred the security patch introduced breakage jut to point out the existence of such risk, in order to make weighting the risks more realistic. Just like this: There is some degree of risk of breaking functionality connected to upgrading to recent upstream version. There is also some degree of risk connected to backpatching the old version, that is increasing with the age of software. Both are real, both can cause severe damage. The probability of each one, _that_ is the matter of question. That should be changed anyway, since security upgrades occasionally break things too. You keep saying this, That's just because people keep asking for proof and questioning the bare existence of the risk of security patch introduced breakage. I haven't seen this in Sarge at all. Sarge has had HOW MANY security updates that broke things? Etch's security updates including the Kernel upgrade had no noticeable problems... but of course the two *OBSCURE* issues reported affect you, right? Should there be more appropriate word that ocassionally, please suggest one. My english is not perfect. Of course I listed only those issues that affected me. If You want more, go, ask someone else. You keep trying to HIT these things home, but the more you do this, the more you look foolish. These problems are mainly Woody and before, except for the LONG release time for Sarge. The Woody security updates for Mozilla was REALLY HARD. I stated before, bugs are inevitable, either in tested stable software, or upstream stable, or in security upgrades. There is no intention to harm anybody. Just name the facts. I'd say that Mozilla's backpatching was insanity from the start, the software was developing rapidly during the Woody's life. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-defaults 2.4.4-6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 08:17:16 +0200 Source: python-defaults Binary: python-dev python-doc python-dbg python-all-dbg python-minimal python-examples python-all-dev idle python python-all Architecture: source all Version: 2.4.4-6 Distribution: unstable Urgency: low Maintainer: Matthias Klose [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: idle - An IDE for Python using Tkinter (default version) python - An interactive high-level object-oriented language (default versi python-all - Package depending on all supported Python runtime versions python-all-dbg - Package depending on all supported Python debugging packages python-all-dev - Package depending on all supported Python development packages python-dbg - Debug Build of the Python Interpreter (version 2.4) python-dev - Header files and a static library for Python (default) python-examples - Examples for the Python language (default version) python-minimal - A minimal subset of the Python language (default version) Closes: 424703 424704 Changes: python-defaults (2.4.4-6) unstable; urgency=low . * python.postinst: Fix cleanup of temporary files. Closes: #424703, #424704. Files: 3c8618ae00399c366c7b53e72870b8a8 701 python optional python-defaults_2.4.4-6.dsc 30ad3ed99c4366d7b31bf0760d379270 215147 python optional python-defaults_2.4.4-6.tar.gz 60dcf252dde86fcd33e77687f86e68b2 140408 python standard python_2.4.4-6_all.deb 8e8bcae36da283f2c4c19f07e1c8e08f 12896 python standard python-minimal_2.4.4-6_all.deb 0d44f7ea5703b92081910877f50d064b 830 python optional python-examples_2.4.4-6_all.deb 73e998ad358d4d3b2a7f98fab30d8d91 934 python optional python-dev_2.4.4-6_all.deb a1dd9250714c741bb747ae1ee2edd894 3022 python optional idle_2.4.4-6_all.deb bf03b95e5c9ab50066c6df28ec709abe 998 python extra python-dbg_2.4.4-6_all.deb 57dacfe90cc6002ac5fe5884d922972d 852 python optional python-all_2.4.4-6_all.deb cab71cb3086eb14c5d103a5c925cb908 866 python optional python-all-dev_2.4.4-6_all.deb 79703c786817915b4b8f47e69d43d910 874 python optional python-all-dbg_2.4.4-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGS/P5StlRaw+TLJwRAse2AKC4vrOOCMXADQ16+4+6GsclfT51vwCffJ2F Yh81lOHNNSY8k4Utgv70bNQ= =+dOL -END PGP SIGNATURE- Accepted: idle_2.4.4-6_all.deb to pool/main/p/python-defaults/idle_2.4.4-6_all.deb python-all-dbg_2.4.4-6_all.deb to pool/main/p/python-defaults/python-all-dbg_2.4.4-6_all.deb python-all-dev_2.4.4-6_all.deb to pool/main/p/python-defaults/python-all-dev_2.4.4-6_all.deb python-all_2.4.4-6_all.deb to pool/main/p/python-defaults/python-all_2.4.4-6_all.deb python-dbg_2.4.4-6_all.deb to pool/main/p/python-defaults/python-dbg_2.4.4-6_all.deb python-defaults_2.4.4-6.dsc to pool/main/p/python-defaults/python-defaults_2.4.4-6.dsc python-defaults_2.4.4-6.tar.gz to pool/main/p/python-defaults/python-defaults_2.4.4-6.tar.gz python-dev_2.4.4-6_all.deb to pool/main/p/python-defaults/python-dev_2.4.4-6_all.deb python-examples_2.4.4-6_all.deb to pool/main/p/python-defaults/python-examples_2.4.4-6_all.deb python-minimal_2.4.4-6_all.deb to pool/main/p/python-defaults/python-minimal_2.4.4-6_all.deb python_2.4.4-6_all.deb to pool/main/p/python-defaults/python_2.4.4-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted heartbeat 2.0.8-5 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 15:43:55 +0900 Source: heartbeat Binary: libstonith0 heartbeat libpils0 stonith heartbeat-2 heartbeat-dev libstonith-dev ldirectord libpils-dev ldirectord-2 heartbeat-2-dev heartbeat-gui heartbeat-2-gui Architecture: source all i386 Version: 2.0.8-5 Distribution: unstable Urgency: low Maintainer: Simon Horman [EMAIL PROTECTED] Changed-By: Simon Horman [EMAIL PROTECTED] Description: heartbeat - Subsystem for High-Availability Linux heartbeat-2 - Subsystem for High-Availability Linux heartbeat-2-dev - Subsystem for High-Availability Linux - development files heartbeat-2-gui - Provides a gui interface to manage heartbeat clusters heartbeat-dev - Subsystem for High-Availability Linux - development files heartbeat-gui - Provides a gui interface to manage heartbeat clusters ldirectord - Monitors virtual services provided by LVS ldirectord-2 - Monitors virtual services provided by LVS libpils-dev - Plugin and Interface Loading System - development files libpils0 - Plugin and Interface Loading System libstonith-dev - Interface for remotely powering down a node in the cluster libstonith0 - Interface for remotely powering down a node in the cluster stonith- Interface for remotely powering down a node in the cluster Changes: heartbeat (2.0.8-5) unstable; urgency=low . * The heartbeat-2-dev.dirs and friends change in 2.0.8-4 closes #424192, not #424053 (which is also fixed by a different change in 2.0.8-4) * Add missing dummy package for stonith Files: 42936d62fbe119b5c1f5b9441f28d9ac 1186 admin optional heartbeat_2.0.8-5.dsc d929a1fae25c7d3d129112d70d27ef79 176610 admin optional heartbeat_2.0.8-5.diff.gz 4e856951325ed184a5c04853f1b46a88 59094 admin extra ldirectord_2.0.8-5_all.deb e24857b251f47d2d03e91792c1ddc830 15500 admin optional ldirectord-2_2.0.8-5_all.deb 80fb06aa2f499bb681352c593b95431b 15488 admin optional heartbeat-2_2.0.8-5_all.deb 805f48d1ad2039447093196876dfb4fd 15516 admin optional heartbeat-2-dev_2.0.8-5_all.deb 64d804f34dcf4ad201302eb1ff34f950 15518 admin optional libstonith-dev_2.0.8-5_all.deb 761d7870651e8ec23eefe3ba847004a3 15510 admin optional libpils-dev_2.0.8-5_all.deb f33ffe5aea856f2ca84f33029cba6841 1394316 admin optional heartbeat_2.0.8-5_i386.deb 288b83a52b502d4aeb856687b67998c5 488410 devel optional heartbeat-dev_2.0.8-5_i386.deb b3a0e5bbdb9176736fe55fa4d1c36c5c 97628 admin optional heartbeat-gui_2.0.8-5_i386.deb 98b4e40e293801de79060f7339bb5fc8 38980 admin optional heartbeat-2-gui_2.0.8-5_i386.deb 62118bc4c2ce85fd9d2c4a5eff440af5 38976 libs optional stonith_2.0.8-5_i386.deb cd77e17ccb682b9a6c177036baf4 38982 libs optional libstonith0_2.0.8-5_i386.deb 9fb046e575a5cea049e7d68ec3ed1a95 38964 libs optional libpils0_2.0.8-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGS/vXA8ACPgVBDpcRAof5AKDRSHr7FNZrkIXaclngWElsnk2DbQCfTo9X xJyLMTFY5G/UE1RQrTXirJE= =iRya -END PGP SIGNATURE- Accepted: heartbeat-2-dev_2.0.8-5_all.deb to pool/main/h/heartbeat/heartbeat-2-dev_2.0.8-5_all.deb heartbeat-2-gui_2.0.8-5_i386.deb to pool/main/h/heartbeat/heartbeat-2-gui_2.0.8-5_i386.deb heartbeat-2_2.0.8-5_all.deb to pool/main/h/heartbeat/heartbeat-2_2.0.8-5_all.deb heartbeat-dev_2.0.8-5_i386.deb to pool/main/h/heartbeat/heartbeat-dev_2.0.8-5_i386.deb heartbeat-gui_2.0.8-5_i386.deb to pool/main/h/heartbeat/heartbeat-gui_2.0.8-5_i386.deb heartbeat_2.0.8-5.diff.gz to pool/main/h/heartbeat/heartbeat_2.0.8-5.diff.gz heartbeat_2.0.8-5.dsc to pool/main/h/heartbeat/heartbeat_2.0.8-5.dsc heartbeat_2.0.8-5_i386.deb to pool/main/h/heartbeat/heartbeat_2.0.8-5_i386.deb ldirectord-2_2.0.8-5_all.deb to pool/main/h/heartbeat/ldirectord-2_2.0.8-5_all.deb ldirectord_2.0.8-5_all.deb to pool/main/h/heartbeat/ldirectord_2.0.8-5_all.deb libpils-dev_2.0.8-5_all.deb to pool/main/h/heartbeat/libpils-dev_2.0.8-5_all.deb libpils0_2.0.8-5_i386.deb to pool/main/h/heartbeat/libpils0_2.0.8-5_i386.deb libstonith-dev_2.0.8-5_all.deb to pool/main/h/heartbeat/libstonith-dev_2.0.8-5_all.deb libstonith0_2.0.8-5_i386.deb to pool/main/h/heartbeat/libstonith0_2.0.8-5_i386.deb stonith_2.0.8-5_i386.deb to pool/main/h/heartbeat/stonith_2.0.8-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted javacc 4.0+cvs20070207-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 09:48:03 +0100 Source: javacc Binary: javacc-doc javacc Architecture: source all Version: 4.0+cvs20070207-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Paul Cager [EMAIL PROTECTED] Description: javacc - A parser generator for use with Java javacc-doc - Documentation for the JavaCC Parser Generator Closes: 424481 Changes: javacc (4.0+cvs20070207-3) unstable; urgency=low . * Missing build-depends on junit. (Closes: #424481) Files: b58bc7b94e7e1ccc92f7ceba3bad005c 838 devel optional javacc_4.0+cvs20070207-3.dsc aeb268a049527f2fa836e8e662351975 5294 devel optional javacc_4.0+cvs20070207-3.diff.gz f157cfad8f952902f08c4b71c0d781a7 266740 devel optional javacc_4.0+cvs20070207-3_all.deb 096ce22f45bbfcc174d1f154749af031 227706 doc optional javacc-doc_4.0+cvs20070207-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGS2ltWSOgCCdjSDsRAod8AJ9SqUvQ8Z7rF096HXVPgD3K+B3gswCfVg4V A4wYCDp0G7nhPdUz+e2SIFU= =fQ6U -END PGP SIGNATURE- Accepted: javacc-doc_4.0+cvs20070207-3_all.deb to pool/main/j/javacc/javacc-doc_4.0+cvs20070207-3_all.deb javacc_4.0+cvs20070207-3.diff.gz to pool/main/j/javacc/javacc_4.0+cvs20070207-3.diff.gz javacc_4.0+cvs20070207-3.dsc to pool/main/j/javacc/javacc_4.0+cvs20070207-3.dsc javacc_4.0+cvs20070207-3_all.deb to pool/main/j/javacc/javacc_4.0+cvs20070207-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gob 1.0.12-4 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 09:24:20 +0100 Source: gob Binary: gob Architecture: source powerpc Version: 1.0.12-4 Distribution: unstable Urgency: low Maintainer: Mark Brown [EMAIL PROTECTED] Changed-By: Mark Brown [EMAIL PROTECTED] Description: gob- GTK+ Object Builder Closes: 424744 Changes: gob (1.0.12-4) unstable; urgency=low . * Fix build for people trying to run with sudo (closes: #424744). Files: 11bf9932d8a04b2fb2155d1527b9c1c7 572 devel extra gob_1.0.12-4.dsc b2749203abc6f5f662a9bc6ecd8fbb72 2124 devel extra gob_1.0.12-4.diff.gz b38a5500030dcafaee0eec49ccd85a6c 85988 devel extra gob_1.0.12-4_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBHkJ2Vo11xhU60RAqdsAJ43r3M58tW9N7Ehq/4AAszvUVkNcACg5War iYyZYtlz4se+fuYBM8ehRgM= =wdaB -END PGP SIGNATURE- Accepted: gob_1.0.12-4.diff.gz to pool/main/g/gob/gob_1.0.12-4.diff.gz gob_1.0.12-4.dsc to pool/main/g/gob/gob_1.0.12-4.dsc gob_1.0.12-4_powerpc.deb to pool/main/g/gob/gob_1.0.12-4_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hunchentoot 0.10.0.dfsg-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 10:20:02 +0200 Source: hunchentoot Binary: cl-hunchentoot Architecture: source all Version: 0.10.0.dfsg-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-hunchentoot - The Common Lisp web server formerly known as TBNL Changes: hunchentoot (0.10.0.dfsg-1) unstable; urgency=low . * New upstream version. Major changes: + Made MAYBE-INVOKE-DEBUGGER a generic function and exported it (suggested by Vladimir Sedach) + Fixed CREATE-FOLDER-DISPATCHER-AND-HANDLER in the presence of URL-encoded URLs (bug caught by Nicolas Lamirault) Files: 1daf9f04ff63fb05af6abb2c826efeb7 808 libs optional hunchentoot_0.10.0.dfsg-1.dsc 2b2f680e6eb780a594f84b9a04b08d24 124351 libs optional hunchentoot_0.10.0.dfsg.orig.tar.gz 757d0a82b2514e2236eb9f9d8eb5e788 3993 libs optional hunchentoot_0.10.0.dfsg-1.diff.gz 2feba52e418bf488b78bbde41a3e9885 126800 libs optional cl-hunchentoot_0.10.0.dfsg-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBJa11ldN0tyliURAouXAJwMGtxMw8ds9+qf5k6rXMXYMKcl/wCfVmD7 tMutYTIHCak4ekhona3zaWA= =f/ro -END PGP SIGNATURE- Accepted: cl-hunchentoot_0.10.0.dfsg-1_all.deb to pool/main/h/hunchentoot/cl-hunchentoot_0.10.0.dfsg-1_all.deb hunchentoot_0.10.0.dfsg-1.diff.gz to pool/main/h/hunchentoot/hunchentoot_0.10.0.dfsg-1.diff.gz hunchentoot_0.10.0.dfsg-1.dsc to pool/main/h/hunchentoot/hunchentoot_0.10.0.dfsg-1.dsc hunchentoot_0.10.0.dfsg.orig.tar.gz to pool/main/h/hunchentoot/hunchentoot_0.10.0.dfsg.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted baycomusb 0.10-8 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 10:40:01 +0200 Source: baycomusb Binary: baycomusb Architecture: source i386 Version: 0.10-8 Distribution: unstable Urgency: low Maintainer: Debian Hamradio Maintainers [EMAIL PROTECTED] Changed-By: Joop Stakenborg [EMAIL PROTECTED] Description: baycomusb - Drivers for the HB9JNX packet radio usb modem Closes: 424140 Changes: baycomusb (0.10-8) unstable; urgency=low . * Make sure we clean up flexdrv/libtrxapi.a and flexdrv/libusb.a, file modified: flexdrv/Makefile.am using CLEANFILES. Closes: #424140. * Running automake triggered a bunch of errors, things like AC_COMPILE_IFELSE was called before AC_GNU_SOURCE and for example AM_INTL_SUBDIR is expanded from Added AC_GNU_SOURCE to configure.in to get rid of these errors. * Running autoconf triggered errors in flexdrv/Makefile.am. Used AM_CFLAGS and AM_LDFLAGS to fix them. * Add the required depcomp to the distribution. * Add automake and autoconf build dependencies. * Update 'missing' to the latest version. * Use LIBMULTITHREAD instead of LIBTHREAD in trxctrl/Makefile.am to fix a compilaton error. Files: 0edc22759e93e3a93765f70765f53842 826 hamradio optional baycomusb_0.10-8.dsc 090a8de84b4034f11b00982865715be9 258356 hamradio optional baycomusb_0.10-8.diff.gz ddfebe432c84c5bb90b77616b6d9f00e 219042 hamradio optional baycomusb_0.10-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBYV/CqtjGLxpX8RArotAJ9PSnzjTRMIW8okWj3wxNqHB1+GqACgoQef wrYVMOoY6YOzdilUP/OzF5M= =91VZ -END PGP SIGNATURE- Accepted: baycomusb_0.10-8.diff.gz to pool/main/b/baycomusb/baycomusb_0.10-8.diff.gz baycomusb_0.10-8.dsc to pool/main/b/baycomusb/baycomusb_0.10-8.dsc baycomusb_0.10-8_i386.deb to pool/main/b/baycomusb/baycomusb_0.10-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted jack-audio-connection-kit 0.103.0-5 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 02:03:28 +0200 Source: jack-audio-connection-kit Binary: libjack0 libjack0.100.0-dev libjack-dev libjack0.100.0-0 jackd Architecture: source amd64 all Version: 0.103.0-5 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Team [EMAIL PROTECTED] Changed-By: Free Ekanayaka [EMAIL PROTECTED] Description: jackd - JACK Audio Connection Kit (server and example clients) libjack-dev - JACK Audio Connection Kit (development files) libjack0 - JACK Audio Connection Kit (libraries) libjack0.100.0-0 - JACK Audio Connection Kit (libraries) libjack0.100.0-dev - JACK Audio Connection Kit (libraries) Closes: 423895 Changes: jack-audio-connection-kit (0.103.0-5) unstable; urgency=low . * debian/control: - build-depend on libfreebob0-dev only on Linux systems, to solve FTBFS on GNU/kFreeBSD (closes: #423895) * debian/patches: - added 09_kbsd.patch, thanks to Petr Salinger * debian/rules: - removed enable-capabilities, as it was causing excessive CPU load when using audacity 1.3.0 with jack via portaudio Files: e3d1c7acc1f44b7016da47e4bf6026b9 1527 sound optional jack-audio-connection-kit_0.103.0-5.dsc a2d4513f7b5618816884b97dfcf23057 28786 sound optional jack-audio-connection-kit_0.103.0-5.diff.gz 670419925c250790ffd98fefa47e37af 12452 libs optional libjack0.100.0-0_0.103.0-5_all.deb ad3a1ff2b6db514a4fbe448d2e35422c 12452 libs optional libjack0.100.0-dev_0.103.0-5_all.deb 126a49b876027ed698fa61714f1c420a 99914 sound optional jackd_0.103.0-5_amd64.deb e234c798872fcbf9b669a1139fafed17 93146 libs optional libjack0_0.103.0-5_amd64.deb 10165b423e3b993e7ac75e613bd7ecef 135904 libdevel optional libjack-dev_0.103.0-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBWycanJGlcVnlkRAkiAAJ4/cF8ElhNrLgc5JLGkBEwvvEXUPgCg0Suy UzdoI/P7tv3FgGIm9lXT2JE= =bA+O -END PGP SIGNATURE- Accepted: jack-audio-connection-kit_0.103.0-5.diff.gz to pool/main/j/jack-audio-connection-kit/jack-audio-connection-kit_0.103.0-5.diff.gz jack-audio-connection-kit_0.103.0-5.dsc to pool/main/j/jack-audio-connection-kit/jack-audio-connection-kit_0.103.0-5.dsc jackd_0.103.0-5_amd64.deb to pool/main/j/jack-audio-connection-kit/jackd_0.103.0-5_amd64.deb libjack-dev_0.103.0-5_amd64.deb to pool/main/j/jack-audio-connection-kit/libjack-dev_0.103.0-5_amd64.deb libjack0.100.0-0_0.103.0-5_all.deb to pool/main/j/jack-audio-connection-kit/libjack0.100.0-0_0.103.0-5_all.deb libjack0.100.0-dev_0.103.0-5_all.deb to pool/main/j/jack-audio-connection-kit/libjack0.100.0-dev_0.103.0-5_all.deb libjack0_0.103.0-5_amd64.deb to pool/main/j/jack-audio-connection-kit/libjack0_0.103.0-5_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted suitesparse 2.3.1-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 09:06:20 +0200 Source: suitesparse Binary: libsuitesparse-dbg libsuitesparse libsuitesparse-dev libsuitesparse-doc Architecture: source all i386 Version: 2.3.1-2 Distribution: unstable Urgency: low Maintainer: Debian Scientific Computing Team [EMAIL PROTECTED] Changed-By: Christophe Prud'homme [EMAIL PROTECTED] Description: libsuitesparse - collection of libraries for computations for sparse matrices libsuitesparse-dbg - collection of libraries for computations for sparse matrices libsuitesparse-dev - collection of libraries for computations for sparse matrices libsuitesparse-doc - collection of libraries for computations for sparse matrices Closes: 422642 422644 Changes: suitesparse (2.3.1-2) unstable; urgency=low . [ Rafael Laboissiere ] * debian/control: Added XS-Vcs-Svn and XS-Vcs-Browser fields to the Source section . [ Christophe Prud'homme ] * Bug fix: colamd.h included non-existing UFconfig.h, thanks to Rene Engelhard (Closes: #422642). * Bug fix: missing Conflicts:, thanks to Rene Engelhard (Closes: #422644). Files: fdd37e42f21418baaac0e082f778b310 921 math optional suitesparse_2.3.1-2.dsc a5aaddb10782490f1cefeb5d2cd593fa 5119 math optional suitesparse_2.3.1-2.diff.gz 12eee84ae4c8b548e433109317b5a0a4 1022690 doc optional libsuitesparse-doc_2.3.1-2_all.deb 5cf61726b4877db0f7dfb09052d1876a 853410 libs optional libsuitesparse_2.3.1-2_i386.deb 501af96ca79dce70276910156e2e4aa7 1187408 libdevel optional libsuitesparse-dev_2.3.1-2_i386.deb d09625ff01cef460c553af4489b3f09c 29708 libdevel extra libsuitesparse-dbg_2.3.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTAfjoY+0C9S+FFARAqseAJ9f7l7HQPxQyOuTeVppTgxxg81E8ACdHTf2 7MWvkl/3brD8xUATL9Em0ig= =zBPg -END PGP SIGNATURE- Accepted: libsuitesparse-dbg_2.3.1-2_i386.deb to pool/main/s/suitesparse/libsuitesparse-dbg_2.3.1-2_i386.deb libsuitesparse-dev_2.3.1-2_i386.deb to pool/main/s/suitesparse/libsuitesparse-dev_2.3.1-2_i386.deb libsuitesparse-doc_2.3.1-2_all.deb to pool/main/s/suitesparse/libsuitesparse-doc_2.3.1-2_all.deb libsuitesparse_2.3.1-2_i386.deb to pool/main/s/suitesparse/libsuitesparse_2.3.1-2_i386.deb suitesparse_2.3.1-2.diff.gz to pool/main/s/suitesparse/suitesparse_2.3.1-2.diff.gz suitesparse_2.3.1-2.dsc to pool/main/s/suitesparse/suitesparse_2.3.1-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libsvn-notify-mirror-perl 0.03603-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 21:25:05 +0300 Source: libsvn-notify-mirror-perl Binary: libsvn-notify-mirror-perl Architecture: source all Version: 0.03603-1 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Niko Tyni [EMAIL PROTECTED] Description: libsvn-notify-mirror-perl - Keep a mirrored working copy of a repository path Closes: 424679 Changes: libsvn-notify-mirror-perl (0.03603-1) unstable; urgency=medium . * New upstream release. + Build.PL modification for optional rsync tests is now included upstream. * Make sure there's no prompting when running Build.PL from debian/rules. * Fake SENDMAIL=/dev/null when running the tests to keep SVN::Notify happy without mail-transport-agent. (Closes: #424679) * Update debian/copyright. Files: 236c9dc228ea33d1047c6ac347b85f41 982 perl optional libsvn-notify-mirror-perl_0.03603-1.dsc ae26574e2118c1b5f287d167092d4d04 24466 perl optional libsvn-notify-mirror-perl_0.03603.orig.tar.gz 59b4f10959792c5efce67add6b44dc56 2448 perl optional libsvn-notify-mirror-perl_0.03603-1.diff.gz c43b4ecb774c01bdb14ef4ef5ecc1fa8 31020 perl optional libsvn-notify-mirror-perl_0.03603-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTAxXHqjlqpcl9jsRAlAbAKDFDWsSmpRPBhjTNOThEX7Le9I5SACgv+hv BYglSFgaSNWP50XQlJaJt2M= =9Iu0 -END PGP SIGNATURE- Accepted: libsvn-notify-mirror-perl_0.03603-1.diff.gz to pool/main/libs/libsvn-notify-mirror-perl/libsvn-notify-mirror-perl_0.03603-1.diff.gz libsvn-notify-mirror-perl_0.03603-1.dsc to pool/main/libs/libsvn-notify-mirror-perl/libsvn-notify-mirror-perl_0.03603-1.dsc libsvn-notify-mirror-perl_0.03603-1_all.deb to pool/main/libs/libsvn-notify-mirror-perl/libsvn-notify-mirror-perl_0.03603-1_all.deb libsvn-notify-mirror-perl_0.03603.orig.tar.gz to pool/main/libs/libsvn-notify-mirror-perl/libsvn-notify-mirror-perl_0.03603.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-who 0.9.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 10:25:42 +0200 Source: cl-who Binary: cl-who Architecture: source all Version: 0.9.0-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-who - Common Lisp HTML generator Changes: cl-who (0.9.0-1) unstable; urgency=low . * New upstream version. Major changes: + Changed behaviour of STR and ESC when argument is NIL (patch by Mac Chan) + Removed antiquated installation instructions and files (thanks to a hint by Mac Chan) + Added *HTML-EMPTY-TAG-AWARE-P* (patch by Mac Chan) + A bit of refactoring Files: fdfe8f37603b2e92319772237c87390a 665 devel optional cl-who_0.9.0-1.dsc ad1a199ba513b03bb57be9f259801e76 18963 devel optional cl-who_0.9.0.orig.tar.gz f9ef4418c9e3d253352bbec403f8eb89 2512 devel optional cl-who_0.9.0-1.diff.gz ff2f67eb46c959b35919ecd3a5b415fb 22530 devel optional cl-who_0.9.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBJX11ldN0tyliURAq2MAJ9UJRpUOQxDOx1Ga2kBLWcjzXBm/ACgiZgK ae9NgNjSIYaUMg16o1lwFDQ= =1evy -END PGP SIGNATURE- Accepted: cl-who_0.9.0-1.diff.gz to pool/main/c/cl-who/cl-who_0.9.0-1.diff.gz cl-who_0.9.0-1.dsc to pool/main/c/cl-who/cl-who_0.9.0-1.dsc cl-who_0.9.0-1_all.deb to pool/main/c/cl-who/cl-who_0.9.0-1_all.deb cl-who_0.9.0.orig.tar.gz to pool/main/c/cl-who/cl-who_0.9.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wordpress 2.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 09:54:36 +0100 Source: wordpress Binary: wordpress Architecture: source all Version: 2.2-1 Distribution: unstable Urgency: low Maintainer: Kai Hendry [EMAIL PROTECTED] Changed-By: Kai Hendry [EMAIL PROTECTED] Description: wordpress - an award winning weblog manager Changes: wordpress (2.2-1) unstable; urgency=low . * New upstream release * http://wordpress.org/development/2007/05/wordpress-22/ Files: b597f29c163b92fb97ac0f80adf62b46 552 web optional wordpress_2.2-1.dsc af983f2e4de2b44d59dd817f80611463 817087 web optional wordpress_2.2.orig.tar.gz 06a8cc8de9b03ac96cdb932ab14546ed 9541 web optional wordpress_2.2-1.diff.gz 066207c83a1900b11e19cf9700b5748e 814918 web optional wordpress_2.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBvEK/juK3+WFWQRAka8AJ4wBXLb82Y4cCeizPzoiuzqve57YgCeMp/x JgjlUSaaoRf5wKl8zavTXsk= =M0av -END PGP SIGNATURE- Accepted: wordpress_2.2-1.diff.gz to pool/main/w/wordpress/wordpress_2.2-1.diff.gz wordpress_2.2-1.dsc to pool/main/w/wordpress/wordpress_2.2-1.dsc wordpress_2.2-1_all.deb to pool/main/w/wordpress/wordpress_2.2-1_all.deb wordpress_2.2.orig.tar.gz to pool/main/w/wordpress/wordpress_2.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lua-expat 1.0.2-5 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 16:20:50 +0200 Source: lua-expat Binary: liblua5.1-expat-dev liblua5.1-expat0 Architecture: source amd64 Version: 1.0.2-5 Distribution: unstable Urgency: low Maintainer: Enrico Tassi [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: liblua5.1-expat-dev - libexpat development files for the lua language version 5.1 liblua5.1-expat0 - libexpat bindings for the lua language version 5.1 Closes: 424551 Changes: lua-expat (1.0.2-5) unstable; urgency=low . * Updated to policy 10 that fixes clean target (Closes: #424551) Files: 63f764bfeabb29c96187617901361908 730 interpreters optional lua-expat_1.0.2-5.dsc b2300ad61eb9cd79122e61aee47e54cb 3294 interpreters optional lua-expat_1.0.2-5.diff.gz 1d769b1600451aae7718c0ef372a38e4 10830 interpreters optional liblua5.1-expat0_1.0.2-5_amd64.deb f959f0148c14cc288ae6beff8697a2ec 26762 interpreters optional liblua5.1-expat-dev_1.0.2-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBzw7kkcPgEj8vIRAoaCAKCCdTCL6BlNH6hpzjR/kWfup/1cRwCfZmHF 5j3Qq+YMBgY0x3H+a/RtV2w= =VnXn -END PGP SIGNATURE- Accepted: liblua5.1-expat-dev_1.0.2-5_amd64.deb to pool/main/l/lua-expat/liblua5.1-expat-dev_1.0.2-5_amd64.deb liblua5.1-expat0_1.0.2-5_amd64.deb to pool/main/l/lua-expat/liblua5.1-expat0_1.0.2-5_amd64.deb lua-expat_1.0.2-5.diff.gz to pool/main/l/lua-expat/lua-expat_1.0.2-5.diff.gz lua-expat_1.0.2-5.dsc to pool/main/l/lua-expat/lua-expat_1.0.2-5.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tucnak1 1.32-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 10:54:52 +0200 Source: tucnak1 Binary: tucnak1 Architecture: source i386 Version: 1.32-2 Distribution: unstable Urgency: low Maintainer: Joop Stakenborg [EMAIL PROTECTED] Changed-By: Joop Stakenborg [EMAIL PROTECTED] Description: tucnak1- VHF/UHF/SHF Hamradio contest log Changes: tucnak1 (1.32-2) unstable; urgency=low . * Added postinst and prerm from the original tucnak1 package which uses updates-alternatives, so we can later add the tucnak2 package. * Recommends: cwdaemon (= 0.9), ssbd (= 0.6). * Remove /usr/sbin from the package. * All of these changes suggested by Ladislav Vaiz, the upstream author. Files: 1b38a9045cf2e496503164532261db26 647 hamradio extra tucnak1_1.32-2.dsc 37bc8ad0849163d3e3aae3fc6ce2113e 2891 hamradio extra tucnak1_1.32-2.diff.gz ce402d60dfeb1cd70be8279c9dd7a240 635118 hamradio extra tucnak1_1.32-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTBtf/CqtjGLxpX8RAq6FAJ0TGcrYd0UzRlJHuyePZfqJSX3AAACgwivM tyEauM9sYYrXRLKteLiGmjo= =KHCy -END PGP SIGNATURE- Accepted: tucnak1_1.32-2.diff.gz to pool/main/t/tucnak1/tucnak1_1.32-2.diff.gz tucnak1_1.32-2.dsc to pool/main/t/tucnak1/tucnak1_1.32-2.dsc tucnak1_1.32-2_i386.deb to pool/main/t/tucnak1/tucnak1_1.32-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnome-sharp2 2.16.0-6 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 11:05:36 +0200 Source: gnome-sharp2 Binary: gnome-sharp2-examples gnome-sharp2 libgnome2.0-cil libart2.0-cil librsvg2.0-cil libgconf2.0-cil libgnome-vfs2.0-cil libvte2.0-cil libgtkhtml2.0-cil Architecture: source i386 all Version: 2.16.0-6 Distribution: unstable Urgency: low Maintainer: Debian Mono Group [EMAIL PROTECTED] Changed-By: Sebastian Dröge [EMAIL PROTECTED] Description: gnome-sharp2 - Gnome# 2.16 suite, CLI bindings for Gnome gnome-sharp2-examples - sample applications for Gnome# 2.16 libart2.0-cil - CLI binding for libart 2.3 libgconf2.0-cil - CLI binding for GConf 2.16 libgnome-vfs2.0-cil - CLI binding for GnomeVFS 2.16 libgnome2.0-cil - CLI binding for Gnome 2.16 libgtkhtml2.0-cil - CLI binding for GtkHTML 3.8 librsvg2.0-cil - CLI binding for RSVG 2.0 libvte2.0-cil - CLI binding for VTE 0.16 Changes: gnome-sharp2 (2.16.0-6) unstable; urgency=low . * Sebastian 'slomo' Dröge: + debian/libgconf2.0-cil.install, debian/libgnome2.0-cil.install, debian/control: - Move the gconf-sharp-peditors libraries from libgnome2.0-cil to libgconf2.0-cil as the pkg-config file of gconf-sharp references them. + debian/control: - Let the metapackage depend on all library packages. Files: 5863cecb3a7af7f72d60b55186443b2f 1471 libs optional gnome-sharp2_2.16.0-6.dsc 5a7ef7f1cc882cabcf1674dfd44a0e5a 9491 libs optional gnome-sharp2_2.16.0-6.diff.gz 2b5e7cd433bee4025c1ab44990e27afa 117318 libs optional gnome-sharp2_2.16.0-6_all.deb b4f4c89e6c542ffad32bc670a320722c 146256 libs optional gnome-sharp2-examples_2.16.0-6_all.deb 980781086c838b05cb2b2029faa84075 134586 libs optional libgconf2.0-cil_2.16.0-6_all.deb 4897e4d85a6ba7fa1eac17237f804eb4 137138 libs optional libart2.0-cil_2.16.0-6_i386.deb e26176b62db451d13d374f06c9095469 258206 libs optional libgnome2.0-cil_2.16.0-6_i386.deb 175773928153df6d1db6c3fd95194c06 179892 libs optional libgnome-vfs2.0-cil_2.16.0-6_i386.deb c3ae5932dc3aace563ba8181bd50fe87 149928 libs optional libgtkhtml2.0-cil_2.16.0-6_i386.deb 0e9efa2b3559e5b929b9721460f6b720 134484 libs optional librsvg2.0-cil_2.16.0-6_i386.deb 34971bf93e5d664813c3693d3e9d450b 147782 libs optional libvte2.0-cil_2.16.0-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTB7uBsBdh1vkHyERAu4SAJ42LP8O7zKttdcsfC5oU/IoeWoXcgCdGUyC RoNjsdAEsB9IoJ5sNY8Phog= =fWCD -END PGP SIGNATURE- Accepted: gnome-sharp2-examples_2.16.0-6_all.deb to pool/main/g/gnome-sharp2/gnome-sharp2-examples_2.16.0-6_all.deb gnome-sharp2_2.16.0-6.diff.gz to pool/main/g/gnome-sharp2/gnome-sharp2_2.16.0-6.diff.gz gnome-sharp2_2.16.0-6.dsc to pool/main/g/gnome-sharp2/gnome-sharp2_2.16.0-6.dsc gnome-sharp2_2.16.0-6_all.deb to pool/main/g/gnome-sharp2/gnome-sharp2_2.16.0-6_all.deb libart2.0-cil_2.16.0-6_i386.deb to pool/main/g/gnome-sharp2/libart2.0-cil_2.16.0-6_i386.deb libgconf2.0-cil_2.16.0-6_all.deb to pool/main/g/gnome-sharp2/libgconf2.0-cil_2.16.0-6_all.deb libgnome-vfs2.0-cil_2.16.0-6_i386.deb to pool/main/g/gnome-sharp2/libgnome-vfs2.0-cil_2.16.0-6_i386.deb libgnome2.0-cil_2.16.0-6_i386.deb to pool/main/g/gnome-sharp2/libgnome2.0-cil_2.16.0-6_i386.deb libgtkhtml2.0-cil_2.16.0-6_i386.deb to pool/main/g/gnome-sharp2/libgtkhtml2.0-cil_2.16.0-6_i386.deb librsvg2.0-cil_2.16.0-6_i386.deb to pool/main/g/gnome-sharp2/librsvg2.0-cil_2.16.0-6_i386.deb libvte2.0-cil_2.16.0-6_i386.deb to pool/main/g/gnome-sharp2/libvte2.0-cil_2.16.0-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted freepops 0.2.3+cleanup-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 09:19:45 +0200 Source: freepops Binary: freepops-doc freepops-updater-fltk freepops Architecture: source amd64 all Version: 0.2.3+cleanup-1 Distribution: unstable Urgency: low Maintainer: Enrico Tassi [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: freepops - POP3 interface to several webmail software freepops-doc - FreePOPs user/developer manual freepops-updater-fltk - Graphical interface for the freepops updater engine Closes: 423840 Changes: freepops (0.2.3+cleanup-1) unstable; urgency=low . * Removed spurious .o files from orig.tar.gz (Closes: #423840) Files: 2ee0cf7cc9bb9e2e9e67edcca889fb39 883 mail optional freepops_0.2.3+cleanup-1.dsc 8e874b1c637d2f9003f0146f18ae55ed 1885171 mail optional freepops_0.2.3+cleanup.orig.tar.gz a5e6bc1056a9d5632f9f70a2c9256f2c 19279 mail optional freepops_0.2.3+cleanup-1.diff.gz dc95ac1bca18c62ffe887533ebd3bda6 735644 doc optional freepops-doc_0.2.3+cleanup-1_all.deb be1c601ec9f494940fcb4c2cb1ad24c8 271396 mail optional freepops_0.2.3+cleanup-1_amd64.deb e6e0620996d3c6756225aa909b373339 44184 mail optional freepops-updater-fltk_0.2.3+cleanup-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTB/37kkcPgEj8vIRAgTGAJwLwDYMawGE8Y4endR7dVrCrt1pmACdFDMC sFyfedoQCs0RHlJ5mGiWRbM= =AKvc -END PGP SIGNATURE- Accepted: freepops-doc_0.2.3+cleanup-1_all.deb to pool/main/f/freepops/freepops-doc_0.2.3+cleanup-1_all.deb freepops-updater-fltk_0.2.3+cleanup-1_amd64.deb to pool/main/f/freepops/freepops-updater-fltk_0.2.3+cleanup-1_amd64.deb freepops_0.2.3+cleanup-1.diff.gz to pool/main/f/freepops/freepops_0.2.3+cleanup-1.diff.gz freepops_0.2.3+cleanup-1.dsc to pool/main/f/freepops/freepops_0.2.3+cleanup-1.dsc freepops_0.2.3+cleanup-1_amd64.deb to pool/main/f/freepops/freepops_0.2.3+cleanup-1_amd64.deb freepops_0.2.3+cleanup.orig.tar.gz to pool/main/f/freepops/freepops_0.2.3+cleanup.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kbfx 0.4.9.3.1-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 09:03:51 +0200 Source: kbfx Binary: kbfx Architecture: source amd64 Version: 0.4.9.3.1-1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team [EMAIL PROTECTED] Changed-By: Fathi Boudra [EMAIL PROTECTED] Description: kbfx - an alternative to K-Menu for KDE Closes: 414217 421761 Changes: kbfx (0.4.9.3.1-1) unstable; urgency=low . * New upstream release. (Closes: #414217, #421761) . [Fathi Boudra] * Remove xdg appsdir patch. Merged upstream. . [Mark Purcell] * Update debian/watch. * Robust get-orig-source target. Files: 49cb2296e76b80ebe9604db30e74d1a3 688 kde optional kbfx_0.4.9.3.1-1.dsc 1091809e12260f83e3bedbb3d0f634bf 1580324 kde optional kbfx_0.4.9.3.1.orig.tar.gz 41f7e123f9ffb12939a6190decc21958 5673 kde optional kbfx_0.4.9.3.1-1.diff.gz 4b7d262e763f6ad3672a105291ef16ab 1788456 kde optional kbfx_0.4.9.3.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTCcLvGr7W6HudhwRAkbmAKCktwGnYtDMoFy5mg8Xl48RU5Pf/wCeK1s8 kKWY5r2hyenYBts6XDn3C4s= =11u6 -END PGP SIGNATURE- Accepted: kbfx_0.4.9.3.1-1.diff.gz to pool/main/k/kbfx/kbfx_0.4.9.3.1-1.diff.gz kbfx_0.4.9.3.1-1.dsc to pool/main/k/kbfx/kbfx_0.4.9.3.1-1.dsc kbfx_0.4.9.3.1-1_amd64.deb to pool/main/k/kbfx/kbfx_0.4.9.3.1-1_amd64.deb kbfx_0.4.9.3.1.orig.tar.gz to pool/main/k/kbfx/kbfx_0.4.9.3.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted praat 4.6.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 10:28:36 +0200 Source: praat Binary: praat Architecture: source i386 Version: 4.6.1-1 Distribution: unstable Urgency: low Maintainer: Rafael Laboissiere [EMAIL PROTECTED] Changed-By: Rafael Laboissiere [EMAIL PROTECTED] Description: praat - program for speech analysis and synthesis Changes: praat (4.6.1-1) unstable; urgency=low . * New upstream release Files: 653c9445a711373022f7d738f7c1debd 807 science optional praat_4.6.1-1.dsc 206c87ddd942abe94a24b97d14ad398a 3110448 science optional praat_4.6.1.orig.tar.gz 8c68c741b7836fe6fcdfcd0f3072dd6c 22856 science optional praat_4.6.1-1.diff.gz 9bd9e3cc4a52fe8af889be9b4755c6b4 1634912 science optional praat_4.6.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTCrnk3oga0pdcv4RAnsMAJ9QjX/UKH/Qikxc4EAR1svplzhrhwCffu0o MHC6QRe2KYjYqZMz3US4Ucg= =bUeD -END PGP SIGNATURE- Accepted: praat_4.6.1-1.diff.gz to pool/main/p/praat/praat_4.6.1-1.diff.gz praat_4.6.1-1.dsc to pool/main/p/praat/praat_4.6.1-1.dsc praat_4.6.1-1_i386.deb to pool/main/p/praat/praat_4.6.1-1_i386.deb praat_4.6.1.orig.tar.gz to pool/main/p/praat/praat_4.6.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted audacity 1.3.2-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 02:36:41 +0200 Source: audacity Binary: audacity Architecture: source amd64 Version: 1.3.2-4 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Team [EMAIL PROTECTED] Changed-By: Free Ekanayaka [EMAIL PROTECTED] Description: audacity - A fast, cross-platform audio editor Changes: audacity (1.3.2-4) unstable; urgency=low . * debian/patches: - desktop_file.patch: fixed broken Category entry * debian/audacity.mime: - added entry for application/x-audacity-project Files: 992da758ac4731ac980e38ff27e74dd9 966 sound optional audacity_1.3.2-4.dsc 197c2aa90780cf8397bb34847eae1d98 39694 sound optional audacity_1.3.2-4.diff.gz eee4ab3490b78f55ce978da8374c047b 2482594 sound optional audacity_1.3.2-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTCKkcanJGlcVnlkRAkvrAKDuPhS5tEvpb9GrbTOjscLpHUhaJgCg5wRu 6slvz/GHxt3MVxu/zZuUQe0= =R3xD -END PGP SIGNATURE- Accepted: audacity_1.3.2-4.diff.gz to pool/main/a/audacity/audacity_1.3.2-4.diff.gz audacity_1.3.2-4.dsc to pool/main/a/audacity/audacity_1.3.2-4.dsc audacity_1.3.2-4_amd64.deb to pool/main/a/audacity/audacity_1.3.2-4_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zeroc-icee-translators 1.2.0-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 11:11:21 +0200 Source: zeroc-icee-translators Binary: slice2javae slice2cppe icee-translators Architecture: source all i386 Version: 1.2.0-2 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco Moya [EMAIL PROTECTED] Description: icee-translators - Metapackage to install ZeroC IceE Slice translators slice2cppe - Slice to C++ translator for IceE slice2javae - Slice to Java translator for IceE Closes: 424082 424473 Changes: zeroc-icee-translators (1.2.0-2) unstable; urgency=low . * A patch was missing causing FTBS bug (Closes: #424473) * Fixed FTBS if built twice in a row (Closes: #424082) Files: 37b02e41c3534e17349eacca0b49a954 666 devel optional zeroc-icee-translators_1.2.0-2.dsc 42cc0f3ed7ca7a3a2ed7e23617e4b842 6342 devel optional zeroc-icee-translators_1.2.0-2.diff.gz 92fffa84689ee395199350133fac1d85 4368 devel optional icee-translators_1.2.0-2_all.deb 19554023c63dd58ad85a86c85c480379 346464 devel optional slice2cppe_1.2.0-2_i386.deb 73e5fa4ebe337987bd7460a0783649c6 373472 devel optional slice2javae_1.2.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDDjOaI3yygJ5hoRAup2AJ9StOvj8FiiP9V9OsEjbZ417GhSRwCg8Plo tKdDzIy7YEwgrXv6uvmPDto= =ZOY+ -END PGP SIGNATURE- Accepted: icee-translators_1.2.0-2_all.deb to pool/main/z/zeroc-icee-translators/icee-translators_1.2.0-2_all.deb slice2cppe_1.2.0-2_i386.deb to pool/main/z/zeroc-icee-translators/slice2cppe_1.2.0-2_i386.deb slice2javae_1.2.0-2_i386.deb to pool/main/z/zeroc-icee-translators/slice2javae_1.2.0-2_i386.deb zeroc-icee-translators_1.2.0-2.diff.gz to pool/main/z/zeroc-icee-translators/zeroc-icee-translators_1.2.0-2.diff.gz zeroc-icee-translators_1.2.0-2.dsc to pool/main/z/zeroc-icee-translators/zeroc-icee-translators_1.2.0-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zeroc-ice-ruby 3.2.0-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 11:27:21 +0200 Source: zeroc-ice-ruby Binary: libzeroc-ice-ruby1.8 Architecture: source i386 Version: 3.2.0-3 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco Moya [EMAIL PROTECTED] Description: libzeroc-ice-ruby1.8 - Ice for Ruby modules Changes: zeroc-ice-ruby (3.2.0-3) unstable; urgency=low . * Fixed FTBS if built twice in a row Files: 7ac20f71377c7862e26032997584bcff 715 interpreters optional zeroc-ice-ruby_3.2.0-3.dsc 183ced407332f1dcf490863b7343fb79 2633 interpreters optional zeroc-ice-ruby_3.2.0-3.diff.gz c33ef0e389a416a02bef1f76d93610bc 254476 interpreters optional libzeroc-ice-ruby1.8_3.2.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDD+OaI3yygJ5hoRAiXfAKDpno2gaSAK4oBYX0jom0kIDUhZiwCgxjGA 5k1RNat/qh/y1Ibxt2/000w= =FLVr -END PGP SIGNATURE- Accepted: libzeroc-ice-ruby1.8_3.2.0-3_i386.deb to pool/main/z/zeroc-ice-ruby/libzeroc-ice-ruby1.8_3.2.0-3_i386.deb zeroc-ice-ruby_3.2.0-3.diff.gz to pool/main/z/zeroc-ice-ruby/zeroc-ice-ruby_3.2.0-3.diff.gz zeroc-ice-ruby_3.2.0-3.dsc to pool/main/z/zeroc-ice-ruby/zeroc-ice-ruby_3.2.0-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zeroc-ice-python 3.2.0-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 11:28:39 +0200 Source: zeroc-ice-python Binary: python-zeroc-ice Architecture: source i386 Version: 3.2.0-3 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco Moya [EMAIL PROTECTED] Description: python-zeroc-ice - Ice for Python libraries Closes: 424085 Changes: zeroc-ice-python (3.2.0-3) unstable; urgency=low . * Fixed FTBFS if built twice in a row (Closes: #424085) Files: bafe4f8246d8645daf80f91f830fc0f8 751 python optional zeroc-ice-python_3.2.0-3.dsc 5266bb9008b6c6ab36a7b8f39469c5f0 3205 python optional zeroc-ice-python_3.2.0-3.diff.gz ab0f85438679181dae874bacaa308f82 307374 python optional python-zeroc-ice_3.2.0-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDD0OaI3yygJ5hoRApJXAKDdrWPWxsrEq7vPquXyxLnI8csDZACfTXSC 6LW6xatCm6rE9lT0wVZ/Y2o= =hfF6 -END PGP SIGNATURE- Accepted: python-zeroc-ice_3.2.0-3_i386.deb to pool/main/z/zeroc-ice-python/python-zeroc-ice_3.2.0-3_i386.deb zeroc-ice-python_3.2.0-3.diff.gz to pool/main/z/zeroc-ice-python/zeroc-ice-python_3.2.0-3.diff.gz zeroc-ice-python_3.2.0-3.dsc to pool/main/z/zeroc-ice-python/zeroc-ice-python_3.2.0-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted chunga 0.2.4-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 8 Mar 2007 10:53:53 +0100 Source: chunga Binary: cl-chunga Architecture: source all Version: 0.2.4-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-chunga - Portable chunked streams for Common Lisp Changes: chunga (0.2.4-2) unstable; urgency=low . * upload to unstable Files: 93388b0d5ca64e2822e3ea35dbf2eabc 668 libs optional chunga_0.2.4-2.dsc 348ea2659294cf9f701ad2f9223183b1 2294 libs optional chunga_0.2.4-2.diff.gz 63973e1f2e8a2e66401f997d777545ad 18036 libs optional cl-chunga_0.2.4-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGXo/11ldN0tyliURAhevAJ98w/uTxzqzOJ2h9SPW1yAPFJ2HcACgvFIV hbR0A9bUUF2tNxEk+/zhcE4= =FzxH -END PGP SIGNATURE- Accepted: chunga_0.2.4-2.diff.gz to pool/main/c/chunga/chunga_0.2.4-2.diff.gz chunga_0.2.4-2.dsc to pool/main/c/chunga/chunga_0.2.4-2.dsc cl-chunga_0.2.4-2_all.deb to pool/main/c/chunga/cl-chunga_0.2.4-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-html-template 0.9.0-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 09 Apr 2007 00:48:19 +0200 Source: cl-html-template Binary: cl-html-template Architecture: source all Version: 0.9.0-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-html-template - Common Lisp HTML Template processor Changes: cl-html-template (0.9.0-2) unstable; urgency=low . * Upload to unstable. Files: ae472b067ce96a0ee63e8cf95bff297a 686 devel optional cl-html-template_0.9.0-2.dsc 382f57aada4c04c188660b8eba6f430b 3068 devel optional cl-html-template_0.9.0-2.diff.gz b7978bf4857d170449de501f6f01014e 34956 devel optional cl-html-template_0.9.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGXFM11ldN0tyliURApOBAJ96DB9l2e/YtzLc4EgIsMr6TCOuXACgxb7G ZnvovfjH9VNF34WSbtjvKEc= =xrEX -END PGP SIGNATURE- Accepted: cl-html-template_0.9.0-2.diff.gz to pool/main/c/cl-html-template/cl-html-template_0.9.0-2.diff.gz cl-html-template_0.9.0-2.dsc to pool/main/c/cl-html-template/cl-html-template_0.9.0-2.dsc cl-html-template_0.9.0-2_all.deb to pool/main/c/cl-html-template/cl-html-template_0.9.0-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-asdf 1.107-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 08 Apr 2007 23:05:18 +0200 Source: cl-asdf Binary: cl-cclan cl-asdf Architecture: source all Version: 1.107-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-asdf- Another System Definition Facility cl-cclan - Comprehensive Common Lisp Archive Network Changes: cl-asdf (1.107-1) unstable; urgency=low . * New upstream release, adding the system-relative-pathname function. Files: 64f5be5e1c6bfef0519b59c93b126823 700 devel optional cl-asdf_1.107-1.dsc 61acdb2053dfe79b621ff7c972cf505a 51339 devel optional cl-asdf_1.107.orig.tar.gz 0ec2b54dee68d66300899b27631a9ccd 13762 devel optional cl-asdf_1.107-1.diff.gz bd20c3370dce42525aae7deb2bb77969 243200 devel optional cl-asdf_1.107-1_all.deb a48e48b15d9b161b4dc33d37fe000581 20480 devel optional cl-cclan_1.107-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGVlN11ldN0tyliURAt8/AKCATQh9LZe/SyW/kSuVAWOYLDCfHgCfbzT+ nnE0ujY5bd8FSieQudkUWA4= =zBxM -END PGP SIGNATURE- Accepted: cl-asdf_1.107-1.diff.gz to pool/main/c/cl-asdf/cl-asdf_1.107-1.diff.gz cl-asdf_1.107-1.dsc to pool/main/c/cl-asdf/cl-asdf_1.107-1.dsc cl-asdf_1.107-1_all.deb to pool/main/c/cl-asdf/cl-asdf_1.107-1_all.deb cl-asdf_1.107.orig.tar.gz to pool/main/c/cl-asdf/cl-asdf_1.107.orig.tar.gz cl-cclan_1.107-1_all.deb to pool/main/c/cl-asdf/cl-cclan_1.107-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-ansi-tests 20070327-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 08 Apr 2007 22:54:45 +0200 Source: cl-ansi-tests Binary: cl-ansi-tests Architecture: source all Version: 20070327-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-ansi-tests - Conformance tests for ANSI Common Lisp Changes: cl-ansi-tests (20070327-1) unstable; urgency=low . * New upstrema version. Files: 9b688c74e46213dc612ad0fc292e348c 682 devel optional cl-ansi-tests_20070327-1.dsc 1262e3dc874193476481d96ff2ce4ec9 968241 devel optional cl-ansi-tests_20070327.orig.tar.gz 6f837fd5e4a1b101c56c1b58068f1942 79194 devel optional cl-ansi-tests_20070327-1.diff.gz 76d4cdc661ea1146322659b6848e5a97 857896 devel optional cl-ansi-tests_20070327-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGVe111ldN0tyliURAn2CAKCeXjc5jFy9uCQGFpJcO4CVayuC6wCgkVQE aC0tXRbN0rZh9f7vpI2ddw0= =KHG+ -END PGP SIGNATURE- Accepted: cl-ansi-tests_20070327-1.diff.gz to pool/main/c/cl-ansi-tests/cl-ansi-tests_20070327-1.diff.gz cl-ansi-tests_20070327-1.dsc to pool/main/c/cl-ansi-tests/cl-ansi-tests_20070327-1.dsc cl-ansi-tests_20070327-1_all.deb to pool/main/c/cl-ansi-tests/cl-ansi-tests_20070327-1_all.deb cl-ansi-tests_20070327.orig.tar.gz to pool/main/c/cl-ansi-tests/cl-ansi-tests_20070327.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bootp 2.4.3-16.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 12:10:15 +0200 Source: bootp Binary: bootp Architecture: source i386 Version: 2.4.3-16.1 Distribution: unstable Urgency: low Maintainer: Anibal Monsalve Salazar [EMAIL PROTECTED] Changed-By: Martin Zobel-Helas [EMAIL PROTECTED] Description: bootp - server for the bootp protocol with DHCP support Closes: 416670 Changes: bootp (2.4.3-16.1) unstable; urgency=low . * Non-maintainer upload durin BSP. * Depend on update-inetd for postrm. * conditional call of update-inetd in postrm. (Closes: #416670) Files: ffcfd26d735a5d716a11aaf0eb26f75e 565 net extra bootp_2.4.3-16.1.dsc bab310c031fef22860bae67fbb7a6000 23297 net extra bootp_2.4.3-16.1.diff.gz 9d086e4429567302c4e23a7d76949be6 75180 net extra bootp_2.4.3-16.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDQ7ST77jl1k+HARAi8PAKClGEuiw24AysvvWkFCxsEoSmh+cACfTKph Mhz0HO+fmH2lbpsil4k+bkI= =x+bi -END PGP SIGNATURE- Accepted: bootp_2.4.3-16.1.diff.gz to pool/main/b/bootp/bootp_2.4.3-16.1.diff.gz bootp_2.4.3-16.1.dsc to pool/main/b/bootp/bootp_2.4.3-16.1.dsc bootp_2.4.3-16.1_i386.deb to pool/main/b/bootp/bootp_2.4.3-16.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-f2cl 20061221-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 08 Apr 2007 23:35:49 +0200 Source: cl-f2cl Binary: cl-f2cl Architecture: source all Version: 20061221-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-f2cl- Common Lisp package to convert Fortran 77 source code to Common L Changes: cl-f2cl (20061221-2) unstable; urgency=low . * Upload to unstable. Files: fbab633e2e44ef50cd2ac33c4581534d 681 devel optional cl-f2cl_20061221-2.dsc 07c599902e0029cc06f7edaccdc43da1 1865 devel optional cl-f2cl_20061221-2.diff.gz 0b17a2beb9167826a3c04448fb5621ad 198584 devel optional cl-f2cl_20061221-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGWBV11ldN0tyliURAq0yAJ0W4sNbtnd3R4vB4RftWkuTjK/nPwCeOCyj PLkIPnBjsp6NcmhMgp3lkwQ= =4+2F -END PGP SIGNATURE- Accepted: cl-f2cl_20061221-2.diff.gz to pool/main/c/cl-f2cl/cl-f2cl_20061221-2.diff.gz cl-f2cl_20061221-2.dsc to pool/main/c/cl-f2cl/cl-f2cl_20061221-2.dsc cl-f2cl_20061221-2_all.deb to pool/main/c/cl-f2cl/cl-f2cl_20061221-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted asciidoc 8.2.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 11:08:48 +0200 Source: asciidoc Binary: asciidoc Architecture: source all Version: 8.2.1-1 Distribution: experimental Urgency: low Maintainer: Fredrik Steen [EMAIL PROTECTED] Changed-By: Alexander Wirt [EMAIL PROTECTED] Description: asciidoc - Highly configurable text format for writing documentation Changes: asciidoc (8.2.1-1) experimental; urgency=low . * New upstream release * Move vim files to a better place Files: e187e0f287f5b9044e38cbe7c09df158 702 text optional asciidoc_8.2.1-1.dsc ed1be3e703867c295f33424792581bb6 785116 text optional asciidoc_8.2.1.orig.tar.gz d9b1b2582e78acbdbe865156cc8637dc 3897 text optional asciidoc_8.2.1-1.diff.gz b5663be2ddb876d2f9edefbdb5385511 758558 text optional asciidoc_8.2.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDKb01u8mbx9AgoRAi3DAKC+9i3kOEfaYzTt/CL3DQoDODpNZwCdGZe1 S5QRVesc8Z/ZaGjpMfujkMM= =Kf/e -END PGP SIGNATURE- Accepted: asciidoc_8.2.1-1.diff.gz to pool/main/a/asciidoc/asciidoc_8.2.1-1.diff.gz asciidoc_8.2.1-1.dsc to pool/main/a/asciidoc/asciidoc_8.2.1-1.dsc asciidoc_8.2.1-1_all.deb to pool/main/a/asciidoc/asciidoc_8.2.1-1_all.deb asciidoc_8.2.1.orig.tar.gz to pool/main/a/asciidoc/asciidoc_8.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted happydigger 3.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 11:31:20 +0200 Source: happydigger Binary: happydigger Architecture: source i386 Version: 3.1-1 Distribution: unstable Urgency: low Maintainer: Joop Stakenborg [EMAIL PROTECTED] Changed-By: Joop Stakenborg [EMAIL PROTECTED] Description: happydigger - Program for cataloging for archaeological finds Changes: happydigger (3.1-1) unstable; urgency=low . * New upstream release Files: 63f8a3156b1d47e071f2022ae325c926 619 utils optional happydigger_3.1-1.dsc f3d54636c72b8f39ae89f7fb655a193e 230446 utils optional happydigger_3.1.orig.tar.gz 14404afb802dd68996f8cdcc1d9ae16b 4874 utils optional happydigger_3.1-1.diff.gz 03feb06ee8d00063a3f9a9137a679697 59852 utils optional happydigger_3.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTCGC/CqtjGLxpX8RAnlfAJ4sNnSS0Bmqn50HgzuzA14gqPB4vwCfRywa ZRa9gBscNk2lHdTmkqJ3dos= =b8LZ -END PGP SIGNATURE- Accepted: happydigger_3.1-1.diff.gz to pool/main/h/happydigger/happydigger_3.1-1.diff.gz happydigger_3.1-1.dsc to pool/main/h/happydigger/happydigger_3.1-1.dsc happydigger_3.1-1_i386.deb to pool/main/h/happydigger/happydigger_3.1-1_i386.deb happydigger_3.1.orig.tar.gz to pool/main/h/happydigger/happydigger_3.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-contextl 0.40-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 22 Apr 2007 22:51:58 +0200 Source: cl-contextl Binary: cl-contextl Architecture: source all Version: 0.40-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-contextl - context orientation for Common Lisp Changes: cl-contextl (0.40-1) unstable; urgency=low . * New upstream with major changes: . + Version 0.40 aims to be feature-complete with regard to the feature set of the upcoming 1.0 release. The goal is to have it tested extensively and to write a documentation of the current features and the API of ContextL before version 1.0 is eventually released. + Several features have been added in 0.4, and some parts of the API have changed. The major changes are listed below. + The functions activate-layer and activate-layer-using-class have been renamed to adjoin-layer and adjoin-layer-using-class, and deactivate-layer and deactivate-layer-using-class have been renamed to remove-layer and remove-layer-using-class. The new names reflect better what these functions actually do. + The functions funcall-with-layers and apply-with-layers have been replaced with the (different) funcall-with-layer-context and apply-with-layer-context. + The deflayer macro doesn't take a :layer-class option anymore, but instead a :metaclass option. This reflects that layers are in fact represented as CLOS classes. + Added the function current-layer-context. This captures the set of currently active layers, which can later be reinstalled with funcall-with-layer-context and apply-with-layer-context. + Added several readers for ContextL's metaclasses: layered-function-definer, layered-function-argument-precedence-order, layered-function-lambda-list, layered-method-lambda-list, layered-method-specializers, layered-method-layer, slot-definition-layered-readers, slot-definition-layered-writers. Files: 5cd9f22c9a77f5ff28d725cb3965e558 606 libs optional cl-contextl_0.40-1.dsc d833dd42465ee3eb0350cab7f74dfd28 16485 libs optional cl-contextl_0.40.orig.tar.gz 2e766e3a95abc7cb9166075500bf9bbc 3490 libs optional cl-contextl_0.40-1.diff.gz 780c3ef8eee076163e888e0ecb0d3f17 15870 libs optional cl-contextl_0.40-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGK8vX11ldN0tyliURAjbXAJsHUJqu17rPaLxJn3Omx1AXpWc1iQCfV2vx SYmG2hAMqY1ZfRAuuyZtAa0= =WwbF -END PGP SIGNATURE- Accepted: cl-contextl_0.40-1.diff.gz to pool/main/c/cl-contextl/cl-contextl_0.40-1.diff.gz cl-contextl_0.40-1.dsc to pool/main/c/cl-contextl/cl-contextl_0.40-1.dsc cl-contextl_0.40-1_all.deb to pool/main/c/cl-contextl/cl-contextl_0.40-1_all.deb cl-contextl_0.40.orig.tar.gz to pool/main/c/cl-contextl/cl-contextl_0.40.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ggz-kde-client 0.0.14-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 17 May 2007 12:43:54 +0200 Source: ggz-kde-client Binary: ggz-kde-client Architecture: source i386 Version: 0.0.14-1 Distribution: unstable Urgency: low Maintainer: Debian GGZ Maintainers [EMAIL PROTECTED] Changed-By: Josef Spillner [EMAIL PROTECTED] Description: ggz-kde-client - GGZ Gaming Zone: advanced core client for KDE Closes: 423767 Changes: ggz-kde-client (0.0.14-1) unstable; urgency=low . * New upstream version. - Fixes FTBFS (closes: #423767) Files: 973bf3ce7ab857be344e3961d5f3646c 821 games optional ggz-kde-client_0.0.14-1.dsc de2da96a92cd3a1467760fa2dcdde079 1757688 games optional ggz-kde-client_0.0.14.orig.tar.gz c3900f3aeb046d77f523c32df2aed96c 2795 games optional ggz-kde-client_0.0.14-1.diff.gz 05b2e69f7a37a05df3233b2b5c743ec5 1375612 games optional ggz-kde-client_0.0.14-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDN0TTx8oVVPtMYRAmLmAKCY6rDCW6qsf/MBBAhYcICA2me6AwCeLL7n x2HSYKA8V2DuP9Kxw9n2J8o= =1vlN -END PGP SIGNATURE- Accepted: ggz-kde-client_0.0.14-1.diff.gz to pool/main/g/ggz-kde-client/ggz-kde-client_0.0.14-1.diff.gz ggz-kde-client_0.0.14-1.dsc to pool/main/g/ggz-kde-client/ggz-kde-client_0.0.14-1.dsc ggz-kde-client_0.0.14-1_i386.deb to pool/main/g/ggz-kde-client/ggz-kde-client_0.0.14-1_i386.deb ggz-kde-client_0.0.14.orig.tar.gz to pool/main/g/ggz-kde-client/ggz-kde-client_0.0.14.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lua-posix 1.0-7 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 07 May 2007 14:25:57 +0200 Source: lua-posix Binary: liblua5.1-posix-dev liblua5.1-posix0 Architecture: source amd64 Version: 1.0-7 Distribution: unstable Urgency: low Maintainer: Enrico Tassi [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: liblua5.1-posix-dev - posix development files for the lua language version 5.1 liblua5.1-posix0 - posix library for the lua language version 5.1 Closes: 424554 Changes: lua-posix (1.0-7) unstable; urgency=low . * made control file binNMU safe * moved to policy 10 and fixed clean target (Closes: #424554) Files: 3532a17c0de96081e7ef51f812264f91 722 interpreters optional lua-posix_1.0-7.dsc 66819be25ed5c15099062edc962a8a16 3600 interpreters optional lua-posix_1.0-7.diff.gz b1b627c55e1660c1decd91721fc9485d 14282 interpreters optional liblua5.1-posix0_1.0-7_amd64.deb 6789018e6c5e46ab2ec625f5ac20b697 13968 interpreters optional liblua5.1-posix-dev_1.0-7_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDSe7kkcPgEj8vIRAqcSAJ4yHqPsA4QUpShdlQc7CYIUHb8nvQCfX37c WvKrYL1DOYPwjEPNIT6BxXw= =q8AD -END PGP SIGNATURE- Accepted: liblua5.1-posix-dev_1.0-7_amd64.deb to pool/main/l/lua-posix/liblua5.1-posix-dev_1.0-7_amd64.deb liblua5.1-posix0_1.0-7_amd64.deb to pool/main/l/lua-posix/liblua5.1-posix0_1.0-7_amd64.deb lua-posix_1.0-7.diff.gz to pool/main/l/lua-posix/lua-posix_1.0-7.diff.gz lua-posix_1.0-7.dsc to pool/main/l/lua-posix/lua-posix_1.0-7.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-closer-mop 1:0.41-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 08 Apr 2007 23:16:33 +0200 Source: cl-closer-mop Binary: cl-closer-mop Architecture: source all Version: 1:0.41-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-closer-mop - Cross Implementation AMOP library Changes: cl-closer-mop (1:0.41-2) unstable; urgency=low . * Small upstream fix for: - Fixed a bug in the creation of congruent lambda lists for generic functions in c2mop for LispWorks. Files: a2eed95f71708ef868b73cd354cc70cd 697 libs optional cl-closer-mop_0.41-2.dsc 4935cb88d991b66a01b14d1a5776cf97 3985 libs optional cl-closer-mop_0.41-2.diff.gz f28267ea7714424268852512f5c811c5 20050 libs optional cl-closer-mop_0.41-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGV6I11ldN0tyliURAtXLAKDLLu6u7sgq7g9t4SJLLgqKjpg4GACfY+Lj MzrO7ywGo91npLfA9AmW55s= =a0xg -END PGP SIGNATURE- Accepted: cl-closer-mop_0.41-2.diff.gz to pool/main/c/cl-closer-mop/cl-closer-mop_0.41-2.diff.gz cl-closer-mop_0.41-2.dsc to pool/main/c/cl-closer-mop/cl-closer-mop_0.41-2.dsc cl-closer-mop_0.41-2_all.deb to pool/main/c/cl-closer-mop/cl-closer-mop_0.41-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zeroc-ice 3.2.0-6 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 11:32:44 +0200 Source: zeroc-ice Binary: libicebox32 slice2rb icepatch2 icegrid icestorm slice2html slice2vb libicessl32 libzeroc-ice-dev ice-slice slice2freezej freeze libicegrid32 libzeroc-ice32 zeroc-ice libicepatch2-32 glacier2 libiceutil32 slice2docbook libglacier2-32 libicestorm32 icecpp icebox libslice32 slice2py slice2java libicexml32 zeroc-ice-services ice-translators libfreeze32 slice2cs slice2cpp slice2freeze Architecture: source i386 all Version: 3.2.0-6 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco Moya [EMAIL PROTECTED] Description: freeze - Freeze service utilities glacier2 - Glacier2 service utilities ice-slice - Slice definitions for Ice services ice-translators - Slice translators to several languages icebox - IceBox service utilities icecpp - Slice preprocessor icegrid- IceGrid service utilities icepatch2 - ZeroC IcePatch2 service utilities icestorm - IceStorm service administration libfreeze32 - Freeze service libraries libglacier2-32 - Glacier2 service libraries libicebox32 - IceBox service libraries libicegrid32 - IceGrid service libraries libicepatch2-32 - IcePatch2 service libraries libicessl32 - Ice for C++ SSL plug-in libicestorm32 - IceStorm service libraries libiceutil32 - Ice for C++ misc utility library libicexml32 - ZeroC Ice for C++ XML parser library libslice32 - Ice for C++ Slice parser library libzeroc-ice-dev - Ice for C++ development libraries libzeroc-ice32 - Ice for C++ runtime library slice2cpp - Slice to C++ translator slice2cs - Slice to C# translator slice2docbook - Slice to Docbook translator slice2freeze - Slice to Freeze translator slice2freezej - Slice to Freeze for Java translator slice2html - Slice to HTML translator slice2java - Slice to Java translator slice2py - Slice to Python translator slice2rb - Slice to Ruby translator slice2vb - Slice to VisualBasic translator zeroc-ice - Internet Communications Engine zeroc-ice-services - Services bundled into Ice Closes: 424086 424704 Changes: zeroc-ice (3.2.0-6) unstable; urgency=low . * Added Benoit patch #1 to IceGrid Registry * Fixed FTBFS if built twice in a row (Closes: #424086) * Recompilation will also fix FTBFS on AMD64 (Closes: #424704) Files: f3e96b3982cb67a25c7f45279a1c69ce 1154 devel optional zeroc-ice_3.2.0-6.dsc 2bc06edecb7761416496f999fec3b349 31794 devel optional zeroc-ice_3.2.0-6.diff.gz 392d382d24db8d08e3eff4b594cf86ad 40322 devel optional zeroc-ice_3.2.0-6_all.deb b42be8bc34088031098ccb9b022ddd2e 40368 devel optional ice-translators_3.2.0-6_all.deb 5b89f6588276e2278c62126637a77532 79312 devel optional zeroc-ice-services_3.2.0-6_all.deb a82ca369cfcded78b18734b57d49f0e4 83778 devel optional ice-slice_3.2.0-6_all.deb 60515e47bdbc6956082be864402f5433 301312 libs optional libicestorm32_3.2.0-6_i386.deb ae3294c7704852a1ec100d684d747246 83260 devel optional icestorm_3.2.0-6_i386.deb c9c9332779661ad45cb2a47d490c46ef 558614 libs optional libicegrid32_3.2.0-6_i386.deb 5345b36e0111dd16662ef4b6486d5842 2491432 devel optional icegrid_3.2.0-6_i386.deb 1c1dc975b5cc00330de703b44a43d000 75548 libs optional libicebox32_3.2.0-6_i386.deb f20c8ac8d33c1254e386d521fa7eda8c 87606 devel optional icebox_3.2.0-6_i386.deb 6247d1cef309396a2bfe9d2c58830264 156026 libs optional libicepatch2-32_3.2.0-6_i386.deb d5beccc585e9e08b2a261a8896bc7b7f 98992 devel optional icepatch2_3.2.0-6_i386.deb d6acbf10c918530b3e02c9e875c2d6f2 163120 libs optional libglacier2-32_3.2.0-6_i386.deb f9dd6936c485981a0cbcf5f0a692 191490 devel optional glacier2_3.2.0-6_i386.deb 2ae8b17cc47c2ba4d6c8881cebb4c7e4 223710 libs optional libfreeze32_3.2.0-6_i386.deb 07c73e10b771c8b9e43fd4095ce8b753 595708 devel optional freeze_3.2.0-6_i386.deb 3b964e5b648a27a3f7941921a764c847 87210 devel optional icecpp_3.2.0-6_i386.deb 3444e3c310f9cf10e096ec2dff06466d 227662 devel optional slice2cpp_3.2.0-6_i386.deb ecd1a6320caa9bea89b793d14046feb2 62474 devel optional slice2py_3.2.0-6_i386.deb 19b6cc41f962349749658bbb451e0075 200556 devel optional slice2cs_3.2.0-6_i386.deb bbe6326ab97aa6ec8c1b3ec3fea6a01e 204938 devel optional slice2java_3.2.0-6_i386.deb 299648689fdf9713bdbf0be2ce0f87a9 214358 devel optional slice2vb_3.2.0-6_i386.deb 51994753bf3e3535bc2eed543dcce1e7 54150 devel optional slice2rb_3.2.0-6_i386.deb b7533f75d6b56fe18f4f2dd69e1b21cf 110804 devel optional slice2freeze_3.2.0-6_i386.deb 97ff6c974919d24dd63f01991ee3 95158 devel optional slice2freezej_3.2.0-6_i386.deb 56a278e67b11805d3d590f2e53037b91 118212 devel optional slice2docbook_3.2.0-6_i386.deb 115a43c1f71c105d3658ce7b34365239 159652 devel optional slice2html_3.2.0-6_i386.deb 54695c586ef1cca8208985ce8c85e012 781230 libs optional libzeroc-ice32_3.2.0-6_i386.deb 5a92388fbd036f69391f28bebc771bab 146678 libs optional
Accepted zeroc-ice-php 3.2.0-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 11:29:09 +0200 Source: zeroc-ice-php Binary: php-zeroc-ice Architecture: source i386 Version: 3.2.0-4 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco Moya [EMAIL PROTECTED] Description: php-zeroc-ice - Ice for PHP extension Closes: 424086 Changes: zeroc-ice-php (3.2.0-4) unstable; urgency=low . * Fixed FTBS if built twice in a row (Closes: #424086) Files: 6c3107bdac320156a20af770a95518c1 649 devel optional zeroc-ice-php_3.2.0-4.dsc 1a0be8d1a14274893b36ffccff49adb5 3994 devel optional zeroc-ice-php_3.2.0-4.diff.gz 14af6ec11b4028c0ba46b8b63514ec85 139832 devel optional php-zeroc-ice_3.2.0-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDDrOaI3yygJ5hoRArfqAJ4l/0+PEoyrea9gPq7mK68pWnPbJQCfT0mp VJeYh2U8WloA0FDbXMjnI3E= =8x0y -END PGP SIGNATURE- Accepted: php-zeroc-ice_3.2.0-4_i386.deb to pool/main/z/zeroc-ice-php/php-zeroc-ice_3.2.0-4_i386.deb zeroc-ice-php_3.2.0-4.diff.gz to pool/main/z/zeroc-ice-php/zeroc-ice-php_3.2.0-4.diff.gz zeroc-ice-php_3.2.0-4.dsc to pool/main/z/zeroc-ice-php/zeroc-ice-php_3.2.0-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-gd 0.5.5-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 25 Apr 2007 05:49:49 +0200 Source: cl-gd Binary: cl-gd Architecture: source i386 Version: 0.5.5-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-gd - GD Interface Library for Common Lisp Changes: cl-gd (0.5.5-1) unstable; urgency=low . * New upstream with a working fix for the last bug. Files: a1bfeb5ba33850b9781a4369b4f4ad07 657 devel optional cl-gd_0.5.5-1.dsc 01534d6c0914b5a4e755163d8c2126f7 198495 devel optional cl-gd_0.5.5.orig.tar.gz e10dc6cbc75dfa837ed091245172cc0c 3150 devel optional cl-gd_0.5.5-1.diff.gz 4e8dbfad2ccfd50f5a3868694f2f1ee7 206346 devel optional cl-gd_0.5.5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGLtBv11ldN0tyliURAmUOAKCZ5thkIieQGkikRwBczcMU1qaFoACeO8RG lPtziUlZ2W40nfJr5jmocNo= =d2Ad -END PGP SIGNATURE- Accepted: cl-gd_0.5.5-1.diff.gz to pool/main/c/cl-gd/cl-gd_0.5.5-1.diff.gz cl-gd_0.5.5-1.dsc to pool/main/c/cl-gd/cl-gd_0.5.5-1.dsc cl-gd_0.5.5-1_i386.deb to pool/main/c/cl-gd/cl-gd_0.5.5-1_i386.deb cl-gd_0.5.5.orig.tar.gz to pool/main/c/cl-gd/cl-gd_0.5.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted luasocket 2.0.1-3 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 16:32:46 +0200 Source: luasocket Binary: luasocket-dev liblua5.1-socket2 liblua50-socket-dev luasocket liblua50-socket2 luasocket-doc liblua5.1-socket-dev Architecture: source all amd64 Version: 2.0.1-3 Distribution: unstable Urgency: low Maintainer: Enrico Tassi [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: liblua5.1-socket-dev - TCP/UDP socket library for Lua 5.1 liblua5.1-socket2 - TCP/UDP socket library for Lua 5.1 liblua50-socket-dev - TCP/UDP socket library for Lua 5.0 liblua50-socket2 - TCP/UDP socket library for Lua 5.0 luasocket - TCP/UDP socket library for Lua 5.0 luasocket-dev - TCP/UDP socket library for Lua 5.0 luasocket-doc - TCP/UDP socket library for Lua documentation Closes: 424556 Changes: luasocket (2.0.1-3) unstable; urgency=low . * made control file binNMU safe * Fixed clean target (Closes: #424556) Files: e0da36c3cdfae9bac22d1ff7f4085e5a 886 interpreters optional luasocket_2.0.1-3.dsc 9f465dd5e368c3c2f48f715bc9c10289 4269 interpreters optional luasocket_2.0.1-3.diff.gz aa372f0d079afdd57fddffcea08b005f 2888 interpreters optional luasocket_2.0.1-3_all.deb 71a51bf0aeb4a4ca67be8743f8e3fbe8 2904 interpreters optional luasocket-dev_2.0.1-3_all.deb a92bc36f83ee4003fda285a463fa710c 55382 interpreters optional luasocket-doc_2.0.1-3_all.deb 57c56e9848be3ecb0390c39a84ef9afb 52598 interpreters optional liblua5.1-socket2_2.0.1-3_amd64.deb 0fe17b41d2f1761553b8c34fc233a9f5 41142 interpreters optional liblua5.1-socket-dev_2.0.1-3_amd64.deb 4d57c9e5fc962449487326e840b4cb22 52728 interpreters optional liblua50-socket2_2.0.1-3_amd64.deb 8922d96a5129f1512f3f5fdab43c 40840 interpreters optional liblua50-socket-dev_2.0.1-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDWN7kkcPgEj8vIRAm6MAKChKiRWItS63NXbDE1N3p7pJAXreACdEG/1 6HR8pLzQUEIZTmsZAZEVxVw= =ggBm -END PGP SIGNATURE- Accepted: liblua5.1-socket-dev_2.0.1-3_amd64.deb to pool/main/l/luasocket/liblua5.1-socket-dev_2.0.1-3_amd64.deb liblua5.1-socket2_2.0.1-3_amd64.deb to pool/main/l/luasocket/liblua5.1-socket2_2.0.1-3_amd64.deb liblua50-socket-dev_2.0.1-3_amd64.deb to pool/main/l/luasocket/liblua50-socket-dev_2.0.1-3_amd64.deb liblua50-socket2_2.0.1-3_amd64.deb to pool/main/l/luasocket/liblua50-socket2_2.0.1-3_amd64.deb luasocket-dev_2.0.1-3_all.deb to pool/main/l/luasocket/luasocket-dev_2.0.1-3_all.deb luasocket-doc_2.0.1-3_all.deb to pool/main/l/luasocket/luasocket-doc_2.0.1-3_all.deb luasocket_2.0.1-3.diff.gz to pool/main/l/luasocket/luasocket_2.0.1-3.diff.gz luasocket_2.0.1-3.dsc to pool/main/l/luasocket/luasocket_2.0.1-3.dsc luasocket_2.0.1-3_all.deb to pool/main/l/luasocket/luasocket_2.0.1-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-pg 1:20061216-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 09 Apr 2007 01:04:52 +0200 Source: cl-pg Binary: cl-pg Architecture: source all Version: 1:20061216-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-pg - Common Lisp library that provides a socket level postgresql inter Changes: cl-pg (1:20061216-2) unstable; urgency=low . * Upload to unstable. Files: f863f8b9c74eb2b07bcfbd8e842624cc 671 devel optional cl-pg_20061216-2.dsc 07668a65631003897b9d5660c9622a2b 6957 devel optional cl-pg_20061216-2.diff.gz e8d0c2a859a1325fe1527f6838b9f58f 46502 devel optional cl-pg_20061216-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGXUq11ldN0tyliURAtE2AJ9S9+14PtmXWHG3EibKlgBBWkFQRQCgoHhY STl2dVebJIgQyUYDpucQOF4= =sngn -END PGP SIGNATURE- Accepted: cl-pg_20061216-2.diff.gz to pool/main/c/cl-pg/cl-pg_20061216-2.diff.gz cl-pg_20061216-2.dsc to pool/main/c/cl-pg/cl-pg_20061216-2.dsc cl-pg_20061216-2_all.deb to pool/main/c/cl-pg/cl-pg_20061216-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-portable-aserve 1.2.42+cvs.2007.02.25-dfsg-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 09 Apr 2007 01:05:57 +0200 Source: cl-portable-aserve Binary: cl-acl-compat cl-webactions cl-htmlgen cl-aserve Architecture: source all Version: 1.2.42+cvs.2007.02.25-dfsg-2 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-acl-compat - Compatibility layer for Allegro Common Lisp cl-aserve - Portable Aserve cl-htmlgen - HTML generation library for Common Lisp programs cl-webactions - HTTP dispatch library for cl-aserve Changes: cl-portable-aserve (1.2.42+cvs.2007.02.25-dfsg-2) unstable; urgency=low . * Upload to unstable. Files: 36a9ca450561ce54e20567eebda2c2d9 824 web optional cl-portable-aserve_1.2.42+cvs.2007.02.25-dfsg-2.dsc 1c001a21b8ca0d10dec3c5c273685a03 6357 web optional cl-portable-aserve_1.2.42+cvs.2007.02.25-dfsg-2.diff.gz 8f72e635ea6465d55c9fd3927d4bce82 393982 web optional cl-aserve_1.2.42+cvs.2007.02.25-dfsg-2_all.deb f56ba2617ea575910184b95f188ca8c4 68620 web optional cl-acl-compat_1.2.42+cvs.2007.02.25-dfsg-2_all.deb 1f1e6c76cd22aad9aea0360ee42d7e0b 32722 web optional cl-htmlgen_1.2.42+cvs.2007.02.25-dfsg-2_all.deb 652b5166860c615fd81de19fe2ed972b 36252 web optional cl-webactions_1.2.42+cvs.2007.02.25-dfsg-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGXVz11ldN0tyliURAhDYAJ978pbOuN74IjGs7OejMNSW/97OFwCeNaxE D332hLVwb0rjJjFOD7iHlhQ= =mjbv -END PGP SIGNATURE- Accepted: cl-acl-compat_1.2.42+cvs.2007.02.25-dfsg-2_all.deb to pool/main/c/cl-portable-aserve/cl-acl-compat_1.2.42+cvs.2007.02.25-dfsg-2_all.deb cl-aserve_1.2.42+cvs.2007.02.25-dfsg-2_all.deb to pool/main/c/cl-portable-aserve/cl-aserve_1.2.42+cvs.2007.02.25-dfsg-2_all.deb cl-htmlgen_1.2.42+cvs.2007.02.25-dfsg-2_all.deb to pool/main/c/cl-portable-aserve/cl-htmlgen_1.2.42+cvs.2007.02.25-dfsg-2_all.deb cl-portable-aserve_1.2.42+cvs.2007.02.25-dfsg-2.diff.gz to pool/main/c/cl-portable-aserve/cl-portable-aserve_1.2.42+cvs.2007.02.25-dfsg-2.diff.gz cl-portable-aserve_1.2.42+cvs.2007.02.25-dfsg-2.dsc to pool/main/c/cl-portable-aserve/cl-portable-aserve_1.2.42+cvs.2007.02.25-dfsg-2.dsc cl-webactions_1.2.42+cvs.2007.02.25-dfsg-2_all.deb to pool/main/c/cl-portable-aserve/cl-webactions_1.2.42+cvs.2007.02.25-dfsg-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-pdf 139-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 30 Apr 2007 23:10:01 +0200 Source: cl-pdf Binary: cl-pdf Architecture: source all Version: 139-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-pdf - Common Lisp package to create PDF files Changes: cl-pdf (139-1) unstable; urgency=low . * New upstream with BSD license. Thanks Marc! Files: 2604e10ce289801a5575f80e5d167f96 586 devel optional cl-pdf_139-1.dsc c2bf16ffb773176c61e5774e2c95179c 710740 devel optional cl-pdf_139.orig.tar.gz 57d237fc2662de042c9d43f0c9b341f5 3983 devel optional cl-pdf_139-1.diff.gz be37f4dad5d0c8ea78d6799b7bca6da8 465076 devel optional cl-pdf_139-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGNlwh11ldN0tyliURAn54AJ9uuD113DyhxKnhGHHnzpmtjuCLJwCdEg81 E8g+NXrmVLLrqmiO1SGJth4= =I26p -END PGP SIGNATURE- Accepted: cl-pdf_139-1.diff.gz to pool/main/c/cl-pdf/cl-pdf_139-1.diff.gz cl-pdf_139-1.dsc to pool/main/c/cl-pdf/cl-pdf_139-1.dsc cl-pdf_139-1_all.deb to pool/main/c/cl-pdf/cl-pdf_139-1_all.deb cl-pdf_139.orig.tar.gz to pool/main/c/cl-pdf/cl-pdf_139.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-typesetting 139-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 30 Apr 2007 23:12:28 +0200 Source: cl-typesetting Binary: cl-typesetting Architecture: source all Version: 139-1 Distribution: unstable Urgency: low Maintainer: Peter Van Eynde [EMAIL PROTECTED] Changed-By: Peter Van Eynde [EMAIL PROTECTED] Description: cl-typesetting - a Common Lisp typesetting library Changes: cl-typesetting (139-1) unstable; urgency=low . * New upstream version with BSD license. Thanks Marc! Files: c21d7818d6db219e6fd3636fc8fc2b02 698 non-free/devel optional cl-typesetting_139-1.dsc 8a3e096ffa60714ef2dfafe6d4e7784f 338208 non-free/devel optional cl-typesetting_139.orig.tar.gz be9d5d183bf77625001cf9ee191f97ff 3298 non-free/devel optional cl-typesetting_139-1.diff.gz 1d0057381808648b41c5928b757e22fd 164488 non-free/devel optional cl-typesetting_139-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGNlwd11ldN0tyliURAg2bAJ4h+d575PWAG4V8K2Tnh38SHHmixwCglbFa A3LNPdfuL4DZO49A7O1HNc4= =Ysbx -END PGP SIGNATURE- Accepted: cl-typesetting_139-1.diff.gz to pool/non-free/c/cl-typesetting/cl-typesetting_139-1.diff.gz cl-typesetting_139-1.dsc to pool/non-free/c/cl-typesetting/cl-typesetting_139-1.dsc cl-typesetting_139-1_all.deb to pool/non-free/c/cl-typesetting/cl-typesetting_139-1_all.deb cl-typesetting_139.orig.tar.gz to pool/non-free/c/cl-typesetting/cl-typesetting_139.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted freeloader 0.3-7 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 16 May 2007 21:50:14 +0200 Source: freeloader Binary: freeloader Architecture: source all Version: 0.3-7 Distribution: unstable Urgency: low Maintainer: Julien Valroff [EMAIL PROTECTED] Changed-By: Julien Valroff [EMAIL PROTECTED] Description: freeloader - A nice GNOME download manager supporting torrents Closes: 424280 Changes: freeloader (0.3-7) unstable; urgency=low . * Fixed FTBFS when package build twice in a row (Closes: #424280) Files: 45fd8807688d77a4292dc39a574db1ee 781 net optional freeloader_0.3-7.dsc 065c766e7b42026c090c1c438cba64bd 6467 net optional freeloader_0.3-7.diff.gz 4fc75bae38424ad29f5b3c06f14ec68e 39006 net optional freeloader_0.3-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDhArSbtgqbIBbkRAj3YAJwOAir1Jw9Tl8YUjeA+LBxah3qozACfVfNC Vz20Kc8BvUWh1EhYLAnM8zM= =3qQ5 -END PGP SIGNATURE- Accepted: freeloader_0.3-7.diff.gz to pool/main/f/freeloader/freeloader_0.3-7.diff.gz freeloader_0.3-7.dsc to pool/main/f/freeloader/freeloader_0.3-7.dsc freeloader_0.3-7_all.deb to pool/main/f/freeloader/freeloader_0.3-7_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
