Re:
Re:
Re: For those who care about their packages in Ubuntu
Hello Joey, On Sun, 15 Jan 2006, Joey Hess wrote: Leaving ubuntu out of this, what puzzles me about your message, Raphael, is this: Raphael Hertzog wrote: If you have some uploads pending, and would like to see those packages included [...] If for whatever reason you don't want to upload the new package to Debian directly [...] This seems to assume that a) There might be a lot of Debian developers who have some upload ready to go but are sitting on them for some reason. Not really... it happens quite often that I plan on working on a new upstream version (or whatever) but for various reasons, I do not prioritze it much because I know I will do it in time for etch... however I may be interested to have that better version in Ubuntu as well instead of the actual version (which may be too buggy in my opinion). If I don't know about the Ubuntu freeze, I may miss the opportunity to work on it in time... b) There might be a lot of Debian developers who are more interested in contributing to other distributions rather than Debian, or who don't know how to upload to experimental or something. I can only imagine that it may be interesting in some particular cases, for example when Ubuntu has already done a transition that Debian hasn't and where we know that the packages in Ubuntu and in Debian can't be the same. What I don't understand is why you'd think that either group is large enough to warrant a post to d-d-a. Do Debian developers habitually delay uploading packages that are ready to go? Is there some reason why Debian developers who are no longer interested in contributing to Debian shouldn't be shown the door? I hope I have better explained why I thought it was relevant. BTW, I'll take the opportunity of your mail (which is the only public response which is actually constructive) to give some facts and conclusion about this announce : - I received 2 private emails saying that this should have gone to -devel - I received 3 private emails thanking me for the announce and the effort I do to favor the cooperation between Ubuntu and Debian - of course, there have been lots of discussion on IRC and on the list - there's the stupid mail to d-d-a from Andrew Suffield (which should be tought how to reply by private email to simply tell me that this should have gone to -devel (like others have done)) I won't reuse d-d-a for this purpose and I'll ask Lucas Nussbaum (who asked me to forward this announce) to publish those himself directly on -devel in the future (he has been subscribed for a long time). Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
On 1/16/06, Thomas Bushnell BSG [EMAIL PROTECTED] wrote: While I don't disagree with this sentiment, keep in mind that Debian itself is sometimes guilty of adding changes to packages when the upstream may or may not approve. Of course, we'll justify by saying that users want it, or that it is in the best interests of the users, but isn't that exactly the same excuse used by Ubuntu? That's right. The objection is not to changes in Ubuntu. The objection is to a refusal to submit patches back. What makes you think that there is general 'refusal to submit patches back'? Espc. these days, where there are wiki pages like this: https://wiki.ubuntu.com/ContributingToDebian -- regards, Reinhard
Re: Does it sometimes happen that people send mails before NMU ?
On Sun, Jan 15, 2006 at 11:31:10PM -0800, Steve Langasek [EMAIL PROTECTED] wrote: Hi Mike, On Mon, Jan 16, 2006 at 07:47:52AM +0100, Mike Hommey wrote: There have been 2 NMUs on libxml2 in a week and I never got a message beforehand. Now I wonder if that practice has disappeared somehow. I admit I've not spent enough time for libxml2 recently, but still, I wouldn't have been bothered by some poking beforehand. Moreover, I'm not exactly sure the second NMU has indeed removed all problematic content but the bug is closed, so the NMUer may be happy. Ah, by the way, the bug was not even a problem for package propagation to testing, so that doesn't make the propagation an argument for a quick upload. The first bug shows a message from the NMUer apologizing for not sending his patch beforehand. The second bug shows a patch sent by the NMUer prior to the NMU. Did you not receive these mails? The patch was 8 minutes prior to the NMU. Moreover, I'm not exactly sure the second NMU has indeed removed all problematic content but the bug is closed, so the NMUer may be happy. Ah, by the way, the bug was not even a problem for package propagation to testing, so that doesn't make the propagation an argument for a quick upload. Well, no, but the fact that it's a longstanding release-critical bug, with no maintainer response, means that it does warrant NMUer attention. If some non-free files have been missed in the process, that would be bad, but that doesn't seem to be a reason to not try? Of course, it's your prerogative as maintainer to review the contents of the NMU for correctness before acknowledging the bug closure. Yes, it's my fault i didn't tag the bug or sent any feedback, but I'm actually trying to find a better solution than removing the files, with upstream cooperation, considering that upstream adds new testcases quite often, and that any addition is likely to have the same problem. Fixing RC bugs just for the sake of making the RC bug count down is not the best thing to do IMHO. Some might even only be important bugs tagged as grave or serious for some wrong reasons. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
Theodore Ts'o [EMAIL PROTECTED] writes: On Sun, Jan 15, 2006 at 03:12:33PM -0800, Thomas Bushnell BSG wrote: Actually, upstream maintainers have no voice before the technical committee, which exists to resolve disputes between Debian developers, not between Debian developers and outsiders. Indeed. And likewise, we have absolutely no control over what Ubuntu chooses to distribute, either. Not absolutely none. They must comply with the licenses. :) The objection from me, at least, and many others, has been that Ubuntu is *claiming* to cooperate with us, while really not doing so very well at all, and rebuffing attempts to encourage a more useful form of cooperation. The question here is *NOT* whether Ubuntu has good patches, but whether they contribute back, via the BTS, patches which are relevant to the Debian upstream. Actually, Manoj raised the issue of not wanting his name on packages being modified by a committee since bugs may harm his reputation. Sorry, I muddled the two separate issues badly. One issue is the reluctance of Ubuntu to adopt the policy of submitting all relevant patches to the Debian BTS. The second issue is the Ubuntu practice of labelling packages with the Debian maintainers, and not labelling them with a suitable Ubuntu-specific address. The second issue, in the form Manoj raised it, is solved by saying this package came from the one Manoj maintains, and we have changed it in thus-and-such ways. This preserves the attribution of credit, while avoiding the tarnishing of reputation. I have in the past had my reputation harmed by people who screwed up e2fsprogs at various distributions. I think this is not quite true. In any case, my recollection was that the bad cooperation was a two-way street, with you being extremely reluctant to acknowledge the concerns and needs of distributions, and on the other side, distributions disregarding your requests about how the package should be modified or installed. So if that's our formal distribution of power between our upstreams and our Debian Developers, why are we complaining about how Ubuntu treats us? I would be happy to agree that Debian did not cooperate well with you with respect to the past history of e2fsprogs. Ubuntu claims to cooperate well with Debian. That's the problem. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348309: ITP: dhcdbd -- dbus interface for dhclient
Package: wnpp Severity: wishlist Owner: Riccardo Setti [EMAIL PROTECTED] * Package name: dhcdbd Version : 0.1.10 Upstream Author : Jason Vas Dias [EMAIL PROTECTED] * URL : http://people.redhat.com/jvdias/dhcdbd/ * License : GPL Description : dbus interface for dhclient dhcdbd provides a dbus interface to dhclient, so application such as NetworkManager can query and control dhclient. This allows an application neutral interface for such operations -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does it sometimes happen that people send mails before NMU ?
On Mon, 2006-01-16 at 09:41 +0100, Mike Hommey wrote: Yes, it's my fault i didn't tag the bug or sent any feedback, but I'm actually trying to find a better solution than removing the files, with upstream cooperation, considering that upstream adds new testcases quite often, and that any addition is likely to have the same problem. Well, the problem is that the BTS is the only way to know about the status of a bug. If there's no maintainer response to a RC bug, there's no way to know whether the maintainer is working on it, is planning to work on it very soon, or doesn't have the opportunity of working on it anytime soon. Especially if the bug is lacking maintainer response for many months, the chances of it being the latter are of course increasing. You can't expect from NMU'ers to be able to guess what's going on. They're making an effort to address as many of the most serious problems we have, and there are a lot of those problems. Just attaching a small note to the respective bug can clear up a lot of confusion. Whenever I receive a RC-bug on a package of mine (or mostly, any bug), I file a response as soon as possible with a quick first assessment. It's then clear to both reporter and other interested developers what's going on. Thijs signature.asc Description: This is a digitally signed message part
Bug#348317: ITP: mozilla-bookmarksync -- Mozilla Firefox extension to synchronize bookmarks
Package: wnpp Severity: wishlist * Package name: mozilla-bookmarksync Version : 1.0.2 Upstream Author : [EMAIL PROTECTED] * URL or Web page : * License : MPL 1.1/GPL 2.0/LGPL 2.1 Description : Mozilla Firefox extension to synchronize bookmarks Bookmarks Synchronizer is a Mozilla Firefox extension that let you connect to an FTP/WebDAV server and synchronize your bookmarks that are stored in an XML file. Setup is easy; just write in your FTP/WebDAV server address, username, password and a name for the XML file (by default called xbel.xml). To start, press Upload to create the file on the server and set (if you want) to automatically download the file on startup or upload it when you close your browser --Yarik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Emphasize teams, not packages
(M-F-T set.) [Frans Jessop] When somebody wants to become a DD he is told ?Go find a package to maintain, one that you can be the maintainer for.? I see serious problems with this approach as Debian increases in DD's. I will how this is in a second. What I think should be emphasized is ?Go find a package team and join it and contribute and show your stuff.? The point of maintaining a package is to prove that you *can* maintain a package. Being on a team proves nothing. Being on a team and doing most of the work proves something, if this can be measured, but that's difficult. As it happens, I'm on at least one team where I do a majority of the work, and at least one team in name only (haven't yet done *any* work). I don't particularly expect to be judged favorably for the one or unfavorably for the other, because it's just too hard to get the data. I think Debian needs to emphasize teams packaging, not just individuals for many reasons. We've had this conversation already. So I'll skip it. Besides, there are lots of things we need to emphasise in Debian. We've had those conversations, too. Future A: There are now 10,000 DD's and over 100,000 packages, most nobody uses, they are just there because they were needed by people who wanted to become DD's. Obvious solution: Change the requirement from maintain a package to maintain a package that a significant number of people care about. Since AMs / DAMs are people rather than machines, we don't need an accurate automated metric for this - something as vague as popcon should be quite sufficient to reveal the difference between useful packages and pet packages only ever installed by people who said to themselves hmmm I wonder what this does and then never bothered to uninstall them. signature.asc Description: Digital signature
Re: making more packages binary NMU safe
[Ken Bloom]
$substvar{'Source-Version'}= $fi{L Version};
+#Indep-Version is for supporting binary NMUs when a strict
+#version dependancy is required against an arch independant package
+$substvar{'Indep-Version'}= $fi{L Version};
+#strip out the +bN format binary NMU version suffix
+$substvar{'Indep-Version'} =~ s/\+b[0-9]+$//;
Uh, why does Source-Version not refer to, you know, the source
version?
I think you meant this the other way around - a new Binary-Version or
Build-Version or something, to indicate the thing that Source-Version
misleadingly means now.
signature.asc
Description: Digital signature
Re: Need for launchpad
Theodore Ts'o wrote: I can give a couple of examples; one is way back when, before I took over the maintenance of the e2fsprogs package, and was merely the upstream author. The then maintainer of e2fsprogs attempted to add support for filesystems 2GB, but botched the job, and the result was people with filesystems 2GB would in some circumstances, get their filesystems trashed. Of course, those people complained directly to me, and the reputation of e2fsprogs took a hit as a result. I was pissed, but I was informed there was nothing I could do; the maintainer of the package can do whatever they want, upstream wishes be d*mned, unless you try to go through a rather painful appeal process via a then-relatively inactive technical committeee. If it lured you into becoming a DD we should mess up more upstream code :-) Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does it sometimes happen that people send mails before NMU ?
On Mon, Jan 16, 2006 at 09:41:12AM +0100, Mike Hommey wrote: Well, no, but the fact that it's a longstanding release-critical bug, with no maintainer response, means that it does warrant NMUer attention. If some non-free files have been missed in the process, that would be bad, but that doesn't seem to be a reason to not try? Of course, it's your prerogative as maintainer to review the contents of the NMU for correctness before acknowledging the bug closure. Yes, it's my fault i didn't tag the bug or sent any feedback, but I'm actually trying to find a better solution than removing the files, with upstream cooperation, considering that upstream adds new testcases quite often, and that any addition is likely to have the same problem. Then you should reopen the bug (or remove the fixed tag), retitle it to Previous non-free content should be reincluded under a free list and set the severity to wishlist. Having an NMU that removes the files doesn't stop you from readding them later when you and upstream have come to a conclusion. Fixing RC bugs just for the sake of making the RC bug count down is not the best thing to do IMHO. Putting a temporary fix in place while a permanent one continues to be worked out is /exactly/ the right thing to do. Cheers, aj signature.asc Description: Digital signature
Bug#338694: ITP: denyhosts -- simple script to prevent ssh/telnet brute force login
Package: wnpp Followup-For: Bug #338694 Owner: Marco Bertorello [EMAIL PROTECTED] * Package name: denyhosts Version : 1.1.4 Upstream Author : Phil Schwartz [EMAIL PROTECTED] * URL : http://denyhosts.sourceforge.net * License : GPL Description : simple script to prevent ssh/telnet brute force login DenyHosts is a python program that automatically blocks ssh brute-force attacks by adding entries to /etc/hosts.deny. It will also inform Linux administrators about offending hosts, attacked users and suspicious logins. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (1002, 'unstable'), (1001, 'stable'), (101, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-686-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re:
Re:
Re: Does it sometimes happen that people send mails before NMU ?
On Mon, Jan 16, 2006 at 08:34:07PM +1000, Anthony Towns aj@azure.humbug.org.au wrote: On Mon, Jan 16, 2006 at 09:41:12AM +0100, Mike Hommey wrote: Well, no, but the fact that it's a longstanding release-critical bug, with no maintainer response, means that it does warrant NMUer attention. If some non-free files have been missed in the process, that would be bad, but that doesn't seem to be a reason to not try? Of course, it's your prerogative as maintainer to review the contents of the NMU for correctness before acknowledging the bug closure. Yes, it's my fault i didn't tag the bug or sent any feedback, but I'm actually trying to find a better solution than removing the files, with upstream cooperation, considering that upstream adds new testcases quite often, and that any addition is likely to have the same problem. Then you should reopen the bug (or remove the fixed tag), retitle it to Previous non-free content should be reincluded under a free list and set the severity to wishlist. Having an NMU that removes the files doesn't stop you from readding them later when you and upstream have come to a conclusion. Fixing RC bugs just for the sake of making the RC bug count down is not the best thing to do IMHO. Putting a temporary fix in place while a permanent one continues to be worked out is /exactly/ the right thing to do. Putting a fix that solves partially the problem so that we can say the RC bug is closed is not exactly the right thing to do. There are much more than the removed files whose content is doubtful license-wise. On the other hand, some of the removed files (the slashdot rss feeds, for instance), are not exactly the kind of document that ought to have licensing issues, but IANAL. The right temporary fix, then, would have been to remove *all* the test files. But the files listed in the RC bug have been removed, the RC bug is fixed, the RC bug count going down, so everything is fine. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Trivial bug on apt-file (Was : Re: Development standards for unstable)
On Sun, Jan 15, 2006 at 01:07:58PM +1000, Anthony Towns wrote: On Sat, Jan 14, 2006 at 06:00:41PM +0100, Jesus Climent wrote: On Fri, Jan 13, 2006 at 07:31:17PM +0100, Luk Claes wrote: and this answers IMHO what the maintainer wants a patch for: a system that would work with all download managers. Which is something it is not going to work. Huh? What's so hard about that? I meant to say that following the same reasoning, we can also claim that all downloaders for X should be supported, since the end user might have a preference to use them... Anyway, my believe is that supporting those two as a baseline and then adding support for more is not a problem, but should not stop us from having a sane working option upon installation. -- Jesus Climent info:www.pumuki.org Unix SysAdm|Linux User #66350|Debian Developer|2.6.14|Helsinki Finland GPG: 1024D/86946D69 BB64 2339 1CAA 7064 E429 7E18 66FC 1D7F 8694 6D69 It is not the size, mate. It's how you use it. --N. Powers (Austin Powers in Goldmember) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does it sometimes happen that people send mails before NMU ?
On Monday 16 January 2006 10:41, Mike Hommey wrote: On Sun, Jan 15, 2006 at 11:31:10PM -0800, Steve Langasek [EMAIL PROTECTED] Well, no, but the fact that it's a longstanding release-critical bug, with no maintainer response, means that it does warrant NMUer attention. Yes, it's my fault i didn't tag the bug or sent any feedback, but I'm actually trying to find a better solution than removing the files, with upstream cooperation, considering that upstream adds new testcases quite often, and that any addition is likely to have the same problem. The correct action in this case would have been CC: this cooperation with upstream to [EMAIL PROTECTED] If you are not mailing BTS to tell what you are doing/planning to do with the bug, you can hardly blame the NMUer for it either, right? The problem with requiring mailing days before upload is the lack of instant gratification that motivates the NMUer. A delayed upload queue would seem to fix that, but in practice people seem to get active on fixing RC bugs only when the 0-day upload period is declared. Someone with more insight on human mind than I have might have an explanation for that too. Cheers, Riku -- hi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
On Mon, Jan 16, 2006 at 12:44:01AM -0800, Thomas Bushnell BSG wrote: I think this is not quite true. In any case, my recollection was that the bad cooperation was a two-way street, with you being extremely reluctant to acknowledge the concerns and needs of distributions, and on the other side, distributions disregarding your requests about how the package should be modified or installed. If that means I wasn't ready to accept a patch which *wasn't* *ready* *yet*, and people went ahead and installed a patch which I rejected is evidence of my relectant to acknowledge the concerns and needs of distributions, maybe. When Debian users started having their filesystems getting corrupted, it was proved that I was right, didn't it? So if that's our formal distribution of power between our upstreams and our Debian Developers, why are we complaining about how Ubuntu treats us? I would be happy to agree that Debian did not cooperate well with you with respect to the past history of e2fsprogs. Ubuntu claims to cooperate well with Debian. That's the problem. Free speech is a b*tch, isn't it? Debian at the time claimed that everything was being done in the interests of the users. It wasn't true, but hey, the the only way we can counter free speech is with more speech. So if we believe that Ubuntu is not cooperating well with Debian, then Debian should issue a formal statement listing how Ubuntu is failing to cooperate well with Debian. Of course, how the press release is worded will be critical in determining how people outside of Debian will perceive us as a result. - Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: making more packages binary NMU safe
Peter Samuelson wrote:
[Ken Bloom]
$substvar{'Source-Version'}= $fi{L Version};
+#Indep-Version is for supporting binary NMUs when a strict
+#version dependancy is required against an arch independant package
+$substvar{'Indep-Version'}= $fi{L Version};
+#strip out the +bN format binary NMU version suffix
+$substvar{'Indep-Version'} =~ s/\+b[0-9]+$//;
Uh, why does Source-Version not refer to, you know, the source
version?
I think you meant this the other way around - a new Binary-Version or
Build-Version or something, to indicate the thing that Source-Version
misleadingly means now.
Backward compatibility. According to
http://lists.debian.org/debian-dpkg/2005/11/msg0.html, it's quite
common for -dev packages to use Source-Version to depend on their
libraries, so changing the behavior of Source-Version would require a
large transition.
Perhaps the variables Source-Version should be left unchanged (and
deprecated) but 2 variables ArchDep-Version and ArchIndep-Version should
be introduced.
--Ken Bloom
--
I usually have a GPG digital signature included as an attachment.
See http://www.gnupg.org/ for info about these digital signatures.
signature.asc
Description: OpenPGP digital signature
Re: Need for launchpad
On Mon, Jan 16, 2006 at 12:06:29PM +0100, Moritz Muehlenhoff wrote: Theodore Ts'o wrote: I can give a couple of examples; one is way back when, before I took over the maintenance of the e2fsprogs package, and was merely the upstream author. The then maintainer of e2fsprogs attempted to add support for filesystems 2GB, but botched the job, and the result was people with filesystems 2GB would in some circumstances, get their filesystems trashed. Of course, those people complained directly to me, and the reputation of e2fsprogs took a hit as a result. I was pissed, but I was informed there was nothing I could do; the maintainer of the package can do whatever they want, upstream wishes be d*mned, unless you try to go through a rather painful appeal process via a then-relatively inactive technical committeee. If it lured you into becoming a DD we should mess up more upstream code :-) So obviously by that logic Ubuntu is doing the right thing by luring all Debian developers to become Ubuntu in order to protect their reputation? :-) - Ted -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
gerris FTBFS bug has not been fixed for 300 days
Hi all Please let me know if there is other appropriate mailing list to report this problem. I am looking at the package gerris. This package has a FTBFS bug reported (along with a patch) against it 300 days ago. The bug report can be found at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=300446 . There was no response from the maintainer since all these days. What can be done to improve this situation? thanks raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does it sometimes happen that people send mails before NMU ?
On Mon, Jan 16, 2006 at 01:36:18PM +0100, Mike Hommey wrote: Fixing RC bugs just for the sake of making the RC bug count down is not the best thing to do IMHO. Putting a temporary fix in place while a permanent one continues to be worked out is /exactly/ the right thing to do. Putting a fix that solves partially the problem so that we can say the RC bug is closed is not exactly the right thing to do. If the problem's only partially solved, reopen the bug. If the partial solution is enough to make it not-RC, downgrade it as well as reopen it. If the partial solution is worse than doing nothing, make a new upload reverting the change. The right temporary fix, then, would have been to remove *all* the test files. But the files listed in the RC bug have been removed, the RC bug is fixed, the RC bug count going down, so everything is fine. If you've got more information than is in the bug report, that's fine; add it to the bug report, and do whatever else is appropriate to fix the problem. Closing reports without fixing real bugs isn't fine, but there's no point I can see to moping about it on -devel -- especially when the bug report didn't have all the information. Cheers, aj signature.asc Description: Digital signature
Re: Does it sometimes happen that people send mails before NMU ?
On Mon, Jan 16, 2006 at 11:35:17PM +1000, Anthony Towns aj@azure.humbug.org.au wrote: If you've got more information than is in the bug report, that's fine; add it to the bug report, and do whatever else is appropriate to fix the problem. Closing reports without fixing real bugs isn't fine, but there's no point I can see to moping about it on -devel -- especially when the bug report didn't have all the information. The point is: fixing RC bugs without going a bit further than what is written in the bug report (which actually stated At least the following files, implying further investigation necessary) is the result of the let's fix RC bugs so that the RC bugs count goes down attitude. I just got pissed by the does-not-fix-anything second-in-a-row-without-notice NMU. I will, indeed, reopen the bug and document it. End of thread. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348364: ITP: libyaml-syck-perl -- Fast, lightweight YAML loader and dumper
Package: wnpp Severity: wishlist Owner: Stephen Quinney [EMAIL PROTECTED] * Package name: libyaml-syck-perl Version : 0.28 Upstream Author : Audrey Tang [EMAIL PROTECTED] * URL : http://www.cpan.org/authors/id/A/AU/AUTRIJUS/YAML-Syck-0.28.tar.gz * License : BSD + GPL (= 1) or Perl Artistic Description : Fast, lightweight YAML loader and dumper This module provides a Perl interface to the libsyck data serialization library. It exports the Dump and Load functions for converting Perl data structures to YAML strings, and the other way around. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (90, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Development standards for unstable
Russ Allbery wrote: Thomas Viehmann [EMAIL PROTECTED] writes: Russ Allbery wrote: The thing is... most of the orphaned packages are in fairly good shape. How do you know? Well, because at one point I went through the PTS for each one of them, checked for filed bugs, checked lintian reports, etc. I haven't specifically *used* each of them, but I think the choices are no one is using them (popcon seems to say no), no one is reporting problems (possible, but statistically I'd expect someone to notice), or they're in fairly good shape. Well, given that several people with more QA experience than myself objecting to this, I guess I'll yield to experience. Maybe I'll just discuss a manual selection of packages first. Thanks for your input. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
new mplayer 1.0pre7try2 package
hi everybody a new version of mplayer 1.0pre7try2 is available ; add either for the etch version, the line deb http://tonelli.sns.it/pub/mplayer/etch ./ or for the sarge version, the line deb http://tonelli.sns.it/pub/mplayer/sarge ./ to /etc/apt/source.list . a. signature.asc Description: Digital signature
Bug#348382: ITP: collatinus -- lemmatisation of latin text
Package: wnpp Severity: wishlist Owner: Christian Perrier [EMAIL PROTECTED] * Package name: collatinus Version : 7.13 Upstream Author : Yves Ouvrard [EMAIL PROTECTED] * URL : http://www.collatinus.org * License : GPL Description : lemmatisation of latin text Collatinus can be used to lemmatise latin texts, i.e. extract words and make a lexicon which indicates for each word its canonic form, and how the form actually found in the text was derived from it, for instance by declining it. Example : rosam gives : rosa-rosae -- acc. sing. Collatinus provides a nice graphic front-end to each operation. This software has a long life in the French Educational software community. The Debian packaging has been done and maintained by Georges Khaznadar who will be the maintainer of the package in long term. This ITP is a first attempt to add one of the numerous interesting developments made in the educational community in France to integrate the official Debian archive and thus be more easily available to Debian and Debian derivates (debian-edu/Skolelinux, Edubuntu) users. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
Theodore Ts'o [EMAIL PROTECTED] writes: On Mon, Jan 16, 2006 at 12:44:01AM -0800, Thomas Bushnell BSG wrote: I think this is not quite true. In any case, my recollection was that the bad cooperation was a two-way street, with you being extremely reluctant to acknowledge the concerns and needs of distributions, and on the other side, distributions disregarding your requests about how the package should be modified or installed. If that means I wasn't ready to accept a patch which *wasn't* *ready* *yet*, and people went ahead and installed a patch which I rejected is evidence of my relectant to acknowledge the concerns and needs of distributions, maybe. When Debian users started having their filesystems getting corrupted, it was proved that I was right, didn't it? I think the feeling was that there was an awful lot of foot-dragging. I certainly don't think you should install a patch which is incorrect! But I think people's perception was that you thought it was perfectly fine for e2fs to not support large filesystems, for an arbitrarily long stretch of time. At least, my recollection was that there was only this patch isn't well thought out and no here is an approach I'd like or this is a patch that does the job correctly. Free speech is a b*tch, isn't it? Debian at the time claimed that everything was being done in the interests of the users. It wasn't true, but hey, the the only way we can counter free speech is with more speech. So if we believe that Ubuntu is not cooperating well with Debian, then Debian should issue a formal statement listing how Ubuntu is failing to cooperate well with Debian. Of course, how the press release is worded will be critical in determining how people outside of Debian will perceive us as a result. We don't need that, do we? We aren't *that* bothered by Ubuntu's actions, so we don't need to start a war. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gerris FTBFS bug has not been fixed for 300 days
On Mon, Jan 16, 2006 at 10:25:58AM -0500, kamaraju kusumanchi wrote: Hi all Please let me know if there is other appropriate mailing list to report this problem. I am looking at the package gerris. This package has a FTBFS bug reported (along with a patch) against it 300 days ago. The bug report can be found at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=300446 . There was no response from the maintainer since all these days. What can be done to improve this situation? The maintainer for this package is MIA lately. I'm preparing an NMU for one of his other packages, and I can NMU gerris sometime over the next few days with your patch in his report. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gerris FTBFS bug has not been fixed for 300 days
On Mon, Jan 16, 2006 at 03:42:54PM -0500, David Nusinow wrote: On Mon, Jan 16, 2006 at 10:25:58AM -0500, kamaraju kusumanchi wrote: Hi all Please let me know if there is other appropriate mailing list to report this problem. I am looking at the package gerris. This package has a FTBFS bug reported (along with a patch) against it 300 days ago. The bug report can be found at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=300446 . There was no response from the maintainer since all these days. What can be done to improve this situation? The maintainer for this package is MIA lately. I'm preparing an NMU for one of his other packages, and I can NMU gerris sometime over the next few days with your patch in his report. ^^^ I meant the bug report, if that was unclear :-) - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Does it sometimes happen that people send mails before NMU ?
Hi, Mike Hommey: The patch was 8 minutes prior to the NMU. I'm sorry about that, I had misinterpreted the 0-day NMU policy. By the way, does anybody have a recommendation on how long the delay between an NMU patch and upload should be? (Please CC me on replies.) -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who care about their packages in Ubuntu
On Mon, Jan 16, 2006 at 08:51:12AM +0100, Raphael Hertzog wrote: Hello Joey, On Sun, 15 Jan 2006, Joey Hess wrote: Leaving ubuntu out of this, what puzzles me about your message, Raphael, is this: Raphael Hertzog wrote: If you have some uploads pending, and would like to see those packages included [...] If for whatever reason you don't want to upload the new package to Debian directly [...] This seems to assume that a) There might be a lot of Debian developers who have some upload ready to go but are sitting on them for some reason. Not really... it happens quite often that I plan on working on a new upstream version (or whatever) but for various reasons, I do not prioritze it much because I know I will do it in time for etch... however I may be interested to have that better version in Ubuntu as well instead of the actual version (which may be too buggy in my opinion). If I don't know about the Ubuntu freeze, I may miss the opportunity to work on it in time... Personally, I think that Debian maintainers need to be a bit more proactive about filing faux-serious keep this out of testing bugs (and requesting removals from testing in the meantime), and Ubuntu needs to track this activity to work out what stuff the Debian maintainer thinks is going to suck if it ends up in the next Ubuntu release. Until this utopia occurs, however, I've taken the liberty of requesting removal of non-release-worthy packages for the next Ubuntu release. E-mail ubuntu-motu@lists.ubuntu.com (it's probably subscriber-only, though, which makes it a bad choice for communications with the MOTUs by outsiders, unfortunately) and make the request. To be fair to the MOTUs, it's probably best to do this fairly quickly once you realise that the current version is bong and you can't fix it quickly, as (according to a senior Ubuntu person) MOTUs are supposed to be fixing major bugs in Debian packages anyway, so if they know up-front that something is broken, and they're doing their job, they can fix it or remove it, at their choice. Asking for removal now doesn't give the MOTUs much time to fix. It's a hell of a lot better than having useless crap with your name on it in a stable release of something as high profile as Ubuntu, though. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348423: ITP: python-pynids -- a python wrapper for libnids
Package: wnpp Severity: wishlist Owner: Lorenzo Martignoni [EMAIL PROTECTED] * Package name: python-pynids Version : 0.5 Upstream Author : Michael J. Pomraning [EMAIL PROTECTED] * URL : http://pilcrow.madison.wi.us/pynids/ * License : GPL Description : a python wrapper for libnids pynids is a python wrapper for libnids, a Network Intrusion Detection System library offering sniffing, IP defragmentation, TCP stream reassembly and TCP port scan detection. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.14 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
On Sun, Jan 15, 2006 at 01:08:41AM +1100, Hamish Moffatt wrote: On Fri, Jan 13, 2006 at 12:34:51PM -0800, Matt Zimmerman wrote: can easily spot the holes in it. Likewise, a proposal that Ubuntu developers should put their changes into Debian instead sounds simple, but to an Ubuntu developer is obviously impractical. Could you elaborate on this? It's not obvious to me at all why more changes couldn't be pushed through Debian and automatically into Ubuntu. Only Debian developers can push changes into Debian, and indeed only particular Debian developers can push particular changes into Debian. Routing patches through this mesh involves a lot of overhead, especially in the form of latency. It's commonplace in Debian to wait weeks for a response from a maintainer, for example, and there's no one covering for them during that time. Just as some aspects of Ubuntu's operation are not visible to the Debian community, Ubuntu MOTUs for example cannot be reasonably expected to know who is responsive, who is MIA, whether a particular maintainer doesn't want to receive email with the word Ubuntu in it, etc. This is another instance of the long-standing Debian has no face issue. Organizations external to Debian need genuine, responsive, personal, persistent contacts to interface with. I think that a more practical approach is to have someone (or a team) working within Debian as a liaison, who will manage the queue and ensure that the right people are contacted and that the changes eventually get uploaded to Debian. This is more or less what I hope the utnubu project will do. On a related note, it seems to me that the existence of the MOTU team, as non-core Ubuntu developers who are also not Debian developers, encourages more packages to be forked. Those developers can't make direct Debian uploads even if they want to; at worst they have no interest in contributing to Debian at all. There are also Ubuntu core developers who are not also Debian developers, and their number will continue to grow. Joining Debian cannot be a prerequisite for working on Ubuntu; that would be entirely impractical. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new mplayer 1.0pre7try2 package
* A Mennucc ([EMAIL PROTECTED]) wrote: hi everybody a new version of mplayer 1.0pre7try2 is available ; add either for the etch version, the line deb http://tonelli.sns.it/pub/mplayer/etch ./ or for the sarge version, the line deb http://tonelli.sns.it/pub/mplayer/sarge ./ to /etc/apt/source.list . This has probably been covered ad nauseum, but where do we stand in respect to getting mplayer in Debian? -- Eric Dorland [EMAIL PROTECTED] ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ --END GEEK CODE BLOCK-- signature.asc Description: Digital signature
Re: For those who care about their packages in Ubuntu
Raphael Hertzog wrote: Not really... it happens quite often that I plan on working on a new upstream version (or whatever) but for various reasons, I do not prioritze it much because I know I will do it in time for etch... I think that nearly anyone on the release team will tell you that this is a false time optimisation. The general result is the delay of stable releases. It also doesn't take into account things like d-i beta releases, which include a snapshot of all of Debian testing by way of the CD/DVD images. (And which have never been pre-announced on d-d-a, FWIW). -- see shy jo signature.asc Description: Digital signature
Re: For those who care about their packages in Ubuntu
Matthew Palmer wrote: It's a hell of a lot better than having useless crap with your name on it in a stable release of something as high profile as Ubuntu, though. FYI, I refuse to allow the fact that my code happens to be present in a currently perceived as high profile distribution to hold my time hostage. I've never done it before with other high profile distributions (Corel's mangling of alien comes to mind), and I won't start now. The correct action in these circumstances is a sufficiently evolved killfile. Please consider ALL code written/maintained by me that is present in Ubuntu and is not bit-identical to code/binaries in Debian to be not suitable for release with my name on it. -- see shy jo signature.asc Description: Digital signature
Re: new mplayer 1.0pre7try2 package
On Mon, Jan 16, 2006 at 06:27:40PM +0100, A Mennucc wrote: hi everybody a new version of mplayer 1.0pre7try2 is available ; add either for the etch version, the line deb http://tonelli.sns.it/pub/mplayer/etch ./ or for the sarge version, the line deb http://tonelli.sns.it/pub/mplayer/sarge ./ to /etc/apt/source.list . Interesting... For a proposed-to-go-into-Debian-archive-build, there's no sid version? -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpM32BJIqp8H.pgp Description: PGP signature
Re: For those who care about their packages in Ubuntu
Raphael Hertzog wrote: Not really... it happens quite often that I plan on working on a new upstream version (or whatever) but for various reasons, I do not prioritze it much because I know I will do it in time for etch... however I may be interested to have that better version in Ubuntu as well instead of the actual version (which may be too buggy in my opinion). On second read, this is also quite disrespectful of fellow DDs and users who run Debian unstable (or testing) and who would be stuck with said buggy software. -- see shy jo signature.asc Description: Digital signature
Re: Need for launchpad
Matt Zimmerman wrote: Only Debian developers can push changes into Debian, and indeed only particular Debian developers can push particular changes into Debian. Routing patches through this mesh involves a lot of overhead, especially in the form of latency. It's commonplace in Debian to wait weeks for a response from a maintainer, for example, and there's no one covering for them during that time. Just as some aspects of Ubuntu's operation are not visible to the Debian community, Ubuntu MOTUs for example cannot be reasonably expected to know who is responsive, who is MIA, whether a particular maintainer doesn't want to receive email with the word Ubuntu in it, etc. It's amazing how the Debian project manages to communicate fixes to an even more diverse set of upstream authors, isn't it. -- see shy jo signature.asc Description: Digital signature
Re: [ad-hominem construct deleted]
On Sun, Jan 15, 2006 at 02:59:58AM +0100, Gerfried Fuchs wrote: It's not about succeeding. It's about false statements all the time, like Every Debian developer is also an Ubuntu developer. If I were I would know. And they are recompiling all my packages, so you can't even say that they are using my packages directly. Is the meaning of this statement truly unclear to you, or is this purely a rhetorical point? Under the assumption that you read it differently than I do, I'll attempt to explain. Ubuntu is a Debian derivative. The work that Debian developers do is merged into Ubuntu as well. Most of the source packages in Ubuntu are identical to the ones in Debian. The statement that you quoted is an expression of gratitude and camaraderie. I believe it was Mark who originally said it, but I agree with it. I would also say that Debian's upstreams are, in the same sense, Debian developers. This is part of what makes free software so special, that one's contributions travel far and wide to benefit others, even if one has no direct involvement with them. It's also about false statements like We sync our packages to Debian regularly, because that simply doesn't happen for quite a lot of us, otherwise all these heated discussions wouldn't happen. Given that you saw this on a wiki page, a disclaimer about wiki contents should be implicit. However, regardless of whether it's an accurate quote, it's quite clear to me from context that your interpretation doesn't match the text. The full quote is We sync our packages to Debian regularly, because that introduces the latest work, the latest upstream code, and the newest packaging efforts from a huge and competent open source community. Without Debian, Ubuntu would not be possible. It should be obvious from the remainder of the sentence that it is talking about propagation of changes *from* Debian *to* Ubuntu. I can only speak for myself (like everyone anyway, but it seems to be mentioned), I haven't noticed anyone reaching me, so I hadn't had any chance to burn anyone. The only contact with respect to Ubuntu was a user disappointed that one of my packages in Debian had a fix that the one in Ubuntu hadn't... for several weeks. All I could do is thank him for appreciating my work but that it's out of my hands to fix it for Ubuntu because I never was notified about that it's included there, and wouldn't know at all who to contact therefore. It was inappropriate for this user to raise this issue with you, rather than with Ubuntu, but that's been discussed elsewhere in this thread already. What I find interesting about your statement is that you seem to imply that the situation would have been better if you had been notified that your package was a part of Ubuntu. This would be technically simple to implement, but I'm not convinced that it's possible to do it in a socially acceptable way. Emailing every Debian maintainer to notify them that their package is present in Ubuntu sounds like spam to me, and posting Ubuntu-related announcements to Debian mailing lists has been deemed inappropriate by many in Debian as well. The creation of Ubuntu was *very* widely publicized, as was the fact that it was based on Debian, and this fact has been mentioned countless times since, both in the press and on Debian mailing lists. Clearly you were informed, one way or another. What was problematic about the way it happened, and how could it have been improved? They are really investing time on the co-operation, If they were, why would there be so much fuss about it? Well, yes, I think so. It's a complicated issue, and the fact that there are discussions about it doesn't imply that either party isn't making an effort. Again, speaking for myself, I haven't noticed such a thing for myself I find this type of disclaimer very frustrating. I see a number of opinions expressed about the Ubuntu community by persons with no first-hand experience with it. Most Debian maintainers have probably never interacted with Ubuntu, and there's no reason that most of them should expect to. Setting aside the debate about patch submission for a moment, in the case of most packages, there are no patches in Ubuntu relative to Debian. In fact, I just looked, and I found only one package with maintainer [EMAIL PROTECTED] which has a delta in Ubuntu: libmetakit2.4.9.3. I read the patch just now; here's what's in it: - Transition to python2.4 as the default Python version in Ubuntu. You don't want this patch for Debian yet. - Packaging transition for the gcc4 C++ ABI. Debian developers were notified about the availability of these patches in Ubuntu when the transition began in Debian, though it looks like you chose not to use it, and rebuilt the package instead. - autoconf has been re-run. In other words, I don't see what it is that you're dissatisfied about, in your role as maintainer of these packages. Are you speaking for yourself or on behalf of
Re: Need for launchpad
Matt Zimmerman wrote: On Sun, Jan 15, 2006 at 05:09:44PM -0500, Joey Hess wrote: Hmm, it seems to me that Ubuntu has recently changed its practices regarding what degree of divergence from Debian is appropriate, notably in the introduction of the MOTU group. The MOTU team was formed about a week after the first release of Ubuntu, in October 2004. At what point did Ubuntu begin to add lots of people who weren't already seasoned Debian developers to the MOTU team, and set them loose making large numbers of changes to packages? Perhaps that's the inflection point that I'm looking for. -- see shy jo signature.asc Description: Digital signature
Cool down?!
Hi Could we stop the flaming period? Like - forever? And come back to normal development, making the best distribution on this small planet. Please remember that we have a Code of Conduct for our lists, which includes nice things like # Do not use foul language; # Try not to flame; it is not polite. Back when I joined the Net someone told me two nice little sentences (which are still true and also used, im sure you can find references everywhere), which were something like be nice to anyone else out there, you want them to be nice to you and don't reply to a thread just for the sake of it. It would be great if that could work here too. No, you dont need to write the same information the 7th time, just to keep the thread alive. And if you are angry you should not write mail, postpone it, sleep a night and then look at the mail again. Most probably the world is much better then... -- bye Joerg Unstable means subject to rapid change rather than full of bugs, though sometimes it is both :-). pgpxl63KQC1wD.pgp Description: PGP signature
Re: Need for launchpad
On Mon, Jan 16, 2006 at 06:44:42PM -0500, Joey Hess wrote: It's amazing how the Debian project manages to communicate fixes to an even more diverse set of upstream authors, isn't it. I would be interested to know how you've measured this, because it sounds hard. It's only because Ubuntu publishes an archive of its patches that it's possible to estimate how much of it propagates back into Debian, and even so it isn't easy to get an accurate estimate. The ratio of Debian developers to upstream developers is *much* closer to 1:1 than the ratio of Ubuntu developers to Debian developers, but even so, my guess (based on at least some empirical observation of packages I'm familiar with) is that many of the same issues exist. In some cases, there is a healthy and responsive relationship, and in others, there isn't. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [ad-hominem construct deleted]
Matt Zimmerman wrote: On Sun, Jan 15, 2006 at 02:59:58AM +0100, Gerfried Fuchs wrote: It's not about succeeding. It's about false statements all the time, like Every Debian developer is also an Ubuntu developer. If I were I would know. And they are recompiling all my packages, so you can't even say that they are using my packages directly. Is the meaning of this statement truly unclear to you, or is this purely a rhetorical point? Under the assumption that you read it differently than I do, I'll attempt to explain. FWIW, Mark's statement is one that I flat out disagree with. I have no obligation or committment to Ubuntu, therefore I am not an Ubuntu developer. I appreciate his statement in the spirit I think he made it, but I don't appreciate people who take it and shove it down my throat to try to pretend that I have some committment to Ubuntu. but I agree with it. I would also say that Debian's upstreams are, in the same sense, Debian developers. I think that we probably have hundreds of upstreams who would react with everything from disbelief to anger if Debian claimed that as a blanket statement. Now, analog and procmeter's upstreams have on occasion read/subscribed to the Debian BTS, sent patches to it, etc, and I certianly would be happy to tell them I consider them to be in a sense Debian developers because of that. But as a blanket statement it just makes the term Ubuntu|Debian developer a no-op. Most Debian maintainers have probably never interacted with Ubuntu, and there's no reason that most of them should expect to. And yet we're all Ubuntu developers, hmm? -- see shy jo signature.asc Description: Digital signature
Re: gerris FTBFS bug has not been fixed for 300 days
David Nusinow wrote: On Mon, Jan 16, 2006 at 10:25:58AM -0500, kamaraju kusumanchi wrote: Hi all Please let me know if there is other appropriate mailing list to report this problem. I am looking at the package gerris. This package has a FTBFS bug reported (along with a patch) against it 300 days ago. The bug report can be found at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=300446 . There was no response from the maintainer since all these days. What can be done to improve this situation? The maintainer for this package is MIA lately. I'm preparing an NMU for one of his other packages, and I can NMU gerris sometime over the next few days with your patch in his report. - David Nusinow Just wanted to say that, the person who submitted the patch is not me. I am just interested in the package. Thanks for the NMU. raju -- Kamaraju S Kusumanchi http://www.people.cornell.edu/pages/kk288/ http://malayamaarutham.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
On Mon, Jan 16, 2006 at 06:58:47PM -0500, Joey Hess wrote: Matt Zimmerman wrote: On Sun, Jan 15, 2006 at 05:09:44PM -0500, Joey Hess wrote: Hmm, it seems to me that Ubuntu has recently changed its practices regarding what degree of divergence from Debian is appropriate, notably in the introduction of the MOTU group. The MOTU team was formed about a week after the first release of Ubuntu, in October 2004. At what point did Ubuntu begin to add lots of people who weren't already seasoned Debian developers to the MOTU team, and set them loose making large numbers of changes to packages? Perhaps that's the inflection point that I'm looking for. The MOTU team has never had a significant number of seasoned Debian developers on it. If such a developer is interested in contributing directly to Ubuntu, they are more likely to join the core development team, and the fact that we're already trusting them implicitly in certain ways is taken into account when considering their application. It has also always been a relatively small group of people tackling maintenance of a large set of packages, especially when considering transitions (e.g., new C++ ABI, Python minor revisions) which involve changing a very large number of packages. I think that you're looking for justification for your position after the fact, rather than making judgements based on observations. I'm not entirely sure where your negativity over Ubuntu originated (though I could hazard a guess or two), but it wasn't because the MOTU team suddenly started behaving differently. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [ad-hominem construct deleted]
On Mon, 2006-01-16 at 19:21 -0500, Joey Hess wrote: but I agree with it. I would also say that Debian's upstreams are, in the same sense, Debian developers. I think that we probably have hundreds of upstreams who would react with everything from disbelief to anger if Debian claimed that as a blanket statement. And yet most upstreams can get pretty much arbitrary code into Debian, just by committing it?. How many DD's read the -entire- diff on major version upgrades from upstream. And not just read, audit. Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
Re: Need for launchpad
Matt Zimmerman [EMAIL PROTECTED] writes: The ratio of Debian developers to upstream developers is *much* closer to 1:1 than the ratio of Ubuntu developers to Debian developers, but even so, my guess (based on at least some empirical observation of packages I'm familiar with) is that many of the same issues exist. In some cases, there is a healthy and responsive relationship, and in others, there isn't. Certainly, but the question here is not about individuals but about the organizations. Debian's policies tell all maintainers to submit patches upstream (and that does not mean tell them where they can get Debian and find the patches themselves). Debian's policies tell all maintainers to carefully distinguish the Debian maintainer from the upstream maintainer, and to give proper credit to both. What I've been looking for is Ubuntu to do similar. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [ad-hominem construct deleted]
Matt Zimmerman writes: Is the meaning of this statement truly unclear to you... Every Debian developer is also an Ubuntu developer implies to me that I can make uploads to Ubuntu. I can't (not that I'm asking for that privilege). I don't doubt that it was meant as an expression of gratitude and camaraderie, but it does not come across that way. Perhaps Every Debian developer is, in a sense, also an Ubuntu developer might get the point across more clearly. Emailing every Debian maintainer to notify them that their package is present in Ubuntu sounds like spam to me... It doesn't to me. I am pleased when downstream distributions notify me that they are using my packages. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Getting rid of circular dependencies, stage 3
Joey Hess wrote: Bill Allombert wrote: Although sarge's aptitude did.. I don't know, there were no ways to upgrade to sarge's aptitude. The bug log contains a log of astronut doing the upgrade with sarge's aptitude.. I think the bigger problem is not whether it's possible to do this (which it somewhat was) but that it's not intuitive and that it would require research for someone to figure out how to do. Perhaps there should be some kind of upgrade pseudo-package created to ease the transition, that depends on the tools needed? Ie, aptitude install etch-upgrade would install the later version of aptitude, etc. needed for the upgrade. Benjamin (astronut) signature.asc Description: OpenPGP digital signature
Re: new mplayer 1.0pre7try2 package
A Mennucc wrote: hi everybody a new version of mplayer 1.0pre7try2 is available ; add either for the etch version, the line deb http://tonelli.sns.it/pub/mplayer/etch ./ Hi! Now we have mplayer in this repositories: http://tonelli.sns.it/pub/mplayer/etch ftp://ftp.nerim.net/debian-marillat/ http://apt.cerkinfo.be ...and probably in more. This could confuse users and lead to dependency problems. Solution is to have only one repository for every piece of software that can't be packaged in debian (i.e. non DFSG-free software and software with patent problems). There is already such a repository, with lots of packages: http://debian-unofficial.org/ Could you, or someone else, put mplayer (and xvidcap, rte,...) there, and notify people that run other repositories with mplayer to remove it or help you to maintain it? Regards, Vedran Furač
Re: Does it sometimes happen that people send mails before NMU ?
* Per Olofsson [Mon, 16 Jan 2006 22:11:05 +0100]: Hi, Mike Hommey: The patch was 8 minutes prior to the NMU. I'm sorry about that, I had misinterpreted the 0-day NMU policy. My reading of the NMU policy as set by the release team is that it's okay to upload right after sending the patch, if you feel comfortable with it. I know this works well for a number of people (myself included), while some others prefer to always do a delayed upload. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Ara que ets la meva dona, te la fotré fins a la melsa, bacona! -- Borja Álvaro a Miranda Boronat en «Chulas y famosas» -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
Matt Zimmerman wrote: I think that you're looking for justification for your position after the fact, rather than making judgements based on observations. I've written at length in my blog before about the mess that Ubuntu made of packages that I maintain in Debian. This mess seemed to become much worse after the point that everyone began talking about MOTU. -- see shy jo signature.asc Description: Digital signature
Re: Need for launchpad
I have replied to the implied ad-hominem in Matt's mail privately, but I would like the state here that I didn't appreciate it. -- see shy jo signature.asc Description: Digital signature
when and why did python(-minimal) become essential?
I saw today that the python-minimal package in unstable is tagged as Essential (and currently pulls in python2.3). According to policy, this is supposed to happen only after discussion on debian-devel and consensus is reached, but I couldn't find that discussion in the list archives. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need for launchpad
On Mon, Jan 16, 2006 at 06:58:47PM -0500, Joey Hess wrote: Matt Zimmerman wrote: On Sun, Jan 15, 2006 at 05:09:44PM -0500, Joey Hess wrote: Hmm, it seems to me that Ubuntu has recently changed its practices regarding what degree of divergence from Debian is appropriate, notably in the introduction of the MOTU group. The MOTU team was formed about a week after the first release of Ubuntu, in October 2004. At what point did Ubuntu begin to add lots of people who weren't already seasoned Debian developers to the MOTU team, and set them loose making large numbers of changes to packages? Perhaps that's the inflection point that I'm looking for. Well, if you want to know what's going on, you can always google. MOTU Report #1, from 1st Mar 2005 (http://lwn.net/Articles/125666/) lists nine MOTU, while the MOTU launchpad page (https://launchpad.net/people/motu/) currently lists 35 MOTU, and the wiki lists some 22 MOTU teams (https://wiki.ubuntu.com/MOTUTeams). These days there's also a fair number of MOTU wannabes, I believe. Cheers, aj -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: making more packages binary NMU safe
Ken Bloom wrote: I noticed that glabels is broken on i386 because it's not binary NMU safe, and someone did a binary NMU. After poking around a bit, I found http://lists.debian.org/debian-dpkg/2005/11/msg0.html, which discussed a possible solution to this problem. Since then, we have changed the version number format for binary NMUs, so I wanted to submit a patch (based on the one mentioned previously) to allow the creation more binNMU safe packages. Instead of doing blind substitutions like it is done currently, it is possible to separate Arch:all from Arch:any|other|whatever in the substitution script such that, Source-Version = bin NMU version for binaries that are build Source-Version = 'original' version for Arch:all binaries This way nothing needs to be changed. No transition. Just some code. Not as trivial as introducing new variables, but a lot simpler in the sort term and the long term. - Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: making more packages binary NMU safe
Ken Bloom wrote:
Peter Samuelson wrote:
[Ken Bloom]
$substvar{'Source-Version'}= $fi{L Version};
+#Indep-Version is for supporting binary NMUs when a strict
+#version dependancy is required against an arch independant package
+$substvar{'Indep-Version'}= $fi{L Version};
+#strip out the +bN format binary NMU version suffix
+$substvar{'Indep-Version'} =~ s/\+b[0-9]+$//;
Uh, why does Source-Version not refer to, you know, the source
version?
I think you meant this the other way around - a new Binary-Version or
Build-Version or something, to indicate the thing that Source-Version
misleadingly means now.
Backward compatibility. According to
http://lists.debian.org/debian-dpkg/2005/11/msg0.html, it's quite
common for -dev packages to use Source-Version to depend on their
libraries, so changing the behavior of Source-Version would require a
large transition.
Perhaps the variables Source-Version should be left unchanged (and
deprecated) but 2 variables ArchDep-Version and ArchIndep-Version should
be introduced.
Here is the corresponding patch for that possibility. I hope the dpkg
maintainers will pick up one of these patches quickly.
--- controllib.pl.old 2006-01-15 22:50:55.0 -0600
+++ controllib.pl 2006-01-16 23:04:24.0 -0600
@@ -241,6 +241,9 @@
parsecdata('L',0,parsed version of changelog);
close(CDATA); $? subprocerr(parse changelog);
$substvar{'Source-Version'}= $fi{L Version};
+$substvar{'ArchDep-Version'}= $fi{L Version};
+$substvar{'ArchIndep-Version'}= $fi{L Version};
+$substvar{'ArchIndep-Version'} =~ s/\+b[0-9]+$//
}
--Ken Bloom
--
I usually have a GPG digital signature included as an attachment.
See http://www.gnupg.org/ for info about these digital signatures.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: making more packages binary NMU safe
[Adam M.] Instead of doing blind substitutions like it is done currently, it is possible to separate Arch:all from Arch:any|other|whatever in the substitution script such that, Source-Version = bin NMU version for binaries that are build Source-Version = 'original' version for Arch:all binaries I suspect you haven't tried implementing that. It would require a major conceptual layering violation. Worse than the disease. signature.asc Description: Digital signature
Re: when and why did python(-minimal) become essential?
On Mon, Jan 16, 2006 at 09:45:29PM -0500, Eric Cooper wrote: I saw today that the python-minimal package in unstable is tagged as Essential (and currently pulls in python2.3). According to policy, this is supposed to happen only after discussion on debian-devel and consensus is reached, but I couldn't find that discussion in the list archives. Joerg approved it at 09:50:15 2006/01/15, after Doko uploaded a new python-defaults package (-4). I've no idea why he accepted it as Priority:required and Essential:yes, and given that python-minimal isn't any different to regular python (though presumably will be if we ever switch to python2.4), I can't see why it was uploaded at this point. The -5 upload removed the Essential:yes tag, and lowered the priority to standard (apparently due to apt automatically installing Essential:yes packages and thus screwing up people who've pinned stable or testing, see #348354, and #348319), but since the override was already set at required, that's what the Priority: field still shows. Obviously, python2.4-minimal is what Ubuntu includes in its essential set; so presumably the idea is to move Debian to a similar arrangement. Maybe Doko's been paying attention to all the folks saying Ubuntu should contribute back more? I've changed the override to Priority: standard; I can't say I'm remotely impressed by how this has been handled. Cheers, aj signature.asc Description: Digital signature
Re: making more packages binary NMU safe
On Mon, Jan 16, 2006 at 10:53:04PM -0600, Adam M. wrote:
Ken Bloom wrote:
I noticed that glabels is broken on i386 because it's not binary NMU
safe, and someone did a binary NMU.
After poking around a bit, I found
http://lists.debian.org/debian-dpkg/2005/11/msg0.html, which
discussed a possible solution to this problem. Since then, we have
changed the version number format for binary NMUs, so I wanted to submit
a patch (based on the one mentioned previously) to allow the creation
more binNMU safe packages.
Instead of doing blind substitutions like it is done currently, it is
possible to separate Arch:all from Arch:any|other|whatever in the
substitution script such that,
Source-Version = bin NMU version for binaries that are build
Source-Version = 'original' version for Arch:all binaries
Which would mean the value of the ${Source-Version} substitution would have
to change based on which *package name* preceded it in the control file --
horrible, horrible kludge! No, the correct solution is to introduce two new
variables and deprecate the old one, instead of further re-defining
Source-Version in ways that have even less to do with the source version.
And why is this on -devel instead of on -dpkg, anyway?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
Re: [ad-hominem construct deleted]
also sprach Matt Zimmerman [EMAIL PROTECTED] [2006.01.17.0039 +0100]: Ubuntu is a Debian derivative. The work that Debian developers do is merged into Ubuntu as well. Most of the source packages in Ubuntu are identical to the ones in Debian. The statement that you quoted is an expression of gratitude and camaraderie. I believe it was Mark who originally said it, but I agree with it. I would also say that Debian's upstreams are, in the s/Debian/Ubuntu same sense, Debian developers. This is part of what makes free software so And yes, all of this makes sense. I guess the issue some DDs have with this model is that they aren't treated as Upstream because there's a lack of information exchange. Moreover, Ubuntu has moved ahead in a few areas, and Debian followed, which makes it difficult to think in simple upstream-downstream terms. Note that I don't hold the opinion, and I appreciate what Ubuntu is doing -- I am just trying to echo the picture as I see it. I concur that Scott's patches are not very useful since they have been clearly automatically generated and often include autogenerated files (see libhid for instance), but all in all, Ubuntu is a worthy addition to the distro field, and Debian has profitted *a lot* already: gcc4, python2.4, zope, xorg, you name it. maintainer to notify them that their package is present in Ubuntu sounds like spam to me, and posting Ubuntu-related announcements to Debian mailing ... not anymore than the migrated-to-testing-mails we get all the time. But anyway, we are not in need for more automated solutions. What should happen is that DDs should be able to find out who's responsible for their packages in Ubuntu, and the UD should treat the DD as upstream, discussing with her/him and planning out a strategy for changes. If a change is Ubuntu-specific, so be it. If it isn't, work with the DD to have it integrated into Debian. The creation of Ubuntu was *very* widely publicized, as was the fact that it ... it's still not called Debian for Humans :) -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP (sub)keys? Use subkeys.pgp.net as keyserver! education is an admirable thing, but it is well to remember from time to time that nothing that is worth knowing can be taught. -- oscar wilde signature.asc Description: Digital signature (GPG/PGP)
Accepted aspell-mr 0.10-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jan 2006 15:34:00 +0530 Source: aspell-mr Binary: aspell-mr Architecture: source all Version: 0.10-2 Distribution: unstable Urgency: low Maintainer: Debian-IN Team [EMAIL PROTECTED] Changed-By: Jaldhar H. Vyas [EMAIL PROTECTED] Description: aspell-mr - Marathi Wordlist for Aspell Closes: 344558 Changes: aspell-mr (0.10-2) unstable; urgency=low . * Removed u-deva.cset and u-deva.cmap as these files have been included in aspell package (Closes: #344558) * Change in maintainer address Files: 35954be5867563220b6fb73e39caa5c9 691 text optional aspell-mr_0.10-2.dsc 08007c8f9f353aa76fe152617c24a3d0 1300 text optional aspell-mr_0.10-2.diff.gz 37899fc7d62da9ada3258788ad14e6aa 187664 text optional aspell-mr_0.10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy1Ch2kYOR+5txmoRAvFGAJwPIVZgi22Ihp4ySE1jarvk9xfHzACfTgAP XYtPRILMI3sWrJptzlz8HXc= =mHG9 -END PGP SIGNATURE- Accepted: aspell-mr_0.10-2.diff.gz to pool/main/a/aspell-mr/aspell-mr_0.10-2.diff.gz aspell-mr_0.10-2.dsc to pool/main/a/aspell-mr/aspell-mr_0.10-2.dsc aspell-mr_0.10-2_all.deb to pool/main/a/aspell-mr/aspell-mr_0.10-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gmsh 1.62.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 08:16:13 +0100 Source: gmsh Binary: gmsh Architecture: source i386 Version: 1.62.0-1 Distribution: unstable Urgency: low Maintainer: Christophe Prud'homme [EMAIL PROTECTED] Changed-By: Christophe Prud'homme [EMAIL PROTECTED] Description: gmsh - three-dimensional finite element mesh generator Changes: gmsh (1.62.0-1) unstable; urgency=low . * New upstream release - new option to draw color gradients in the background. - enhanced perspective projection mode. - new lasso selection mode (same as lasso zoom, but in selection mode). - new invert selection button in the visibility browser. - new snapping grid when adding points in the GUI. - nicer normal smoothing. - new extrude syntax (old syntax still available, but deprecated). - various small bug fixes and enhancements. Files: 7a0460063672156084f91177970cb195 707 math optional gmsh_1.62.0-1.dsc f3a9cba7d91618d6ad56da0b1949bccb 2141676 math optional gmsh_1.62.0.orig.tar.gz f3df750c5f271eb086217a73751958f6 29993 math optional gmsh_1.62.0-1.diff.gz 33ce67d6daaec3ba6a63792d823db2ca 2526608 math optional gmsh_1.62.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy02PoY+0C9S+FFARAmSdAJ9Y6kZJ0LoV11PW4bC93jJBiMStlgCeIeUo jvjWVRa/nlXYpeFjLqMsonc= =jvQ2 -END PGP SIGNATURE- Accepted: gmsh_1.62.0-1.diff.gz to pool/main/g/gmsh/gmsh_1.62.0-1.diff.gz gmsh_1.62.0-1.dsc to pool/main/g/gmsh/gmsh_1.62.0-1.dsc gmsh_1.62.0-1_i386.deb to pool/main/g/gmsh/gmsh_1.62.0-1_i386.deb gmsh_1.62.0.orig.tar.gz to pool/main/g/gmsh/gmsh_1.62.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libdbd-sqlite2-perl 2:0.33-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jan 2006 22:29:25 +0200 Source: libdbd-sqlite2-perl Binary: libdbd-sqlite2-perl Architecture: source i386 Version: 2:0.33-6 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Niko Tyni [EMAIL PROTECTED] Description: libdbd-sqlite2-perl - Perl DBI driver with a self-contained RDBMS (SQLite2 version) Closes: 317453 Changes: libdbd-sqlite2-perl (2:0.33-6) unstable; urgency=low . * Use dpatch for managing patches. * Add myself to Uploaders. * debian/patches/10fetchrow: + Fix segmentation fault when fetchrow() is called again after it has returned an empty list once. (Closes: #317453) * Add debian/watch. Files: 9ee671c4696088b88c42d78536d51bc8 820 perl optional libdbd-sqlite2-perl_0.33-6.dsc aacf63fd5dad2b216c8e74cf2d2d74ee 4181 perl optional libdbd-sqlite2-perl_0.33-6.diff.gz f01eae0347954d0705e61f02a4a3d5c1 187154 perl optional libdbd-sqlite2-perl_0.33-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy2bq+NMfSd6w7DERAgPuAJ9CeiDmSzwTbhniOrjR9mGhVNJIdgCgjcOl Ws+BtCV+uB9fMqkRsn4ITPY= =giyZ -END PGP SIGNATURE- Accepted: libdbd-sqlite2-perl_0.33-6.diff.gz to pool/main/libd/libdbd-sqlite2-perl/libdbd-sqlite2-perl_0.33-6.diff.gz libdbd-sqlite2-perl_0.33-6.dsc to pool/main/libd/libdbd-sqlite2-perl/libdbd-sqlite2-perl_0.33-6.dsc libdbd-sqlite2-perl_0.33-6_i386.deb to pool/main/libd/libdbd-sqlite2-perl/libdbd-sqlite2-perl_0.33-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted quick-lounge-applet 2.12.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 10:09:49 +0100 Source: quick-lounge-applet Binary: quick-lounge-applet Architecture: source i386 Version: 2.12.1-1 Distribution: unstable Urgency: low Maintainer: Andreas Rottmann [EMAIL PROTECTED] Changed-By: Andreas Rottmann [EMAIL PROTECTED] Description: quick-lounge-applet - GNOME 2 Panel Applet to organize your preferred applications Closes: 340525 348118 Changes: quick-lounge-applet (2.12.1-1) unstable; urgency=low . * New upstream release. * Rebuilt against newer libgnome-menu-dev (closes: #348118). * Use dh_gconf (closes: #340525). * Remove the rows patch; I don't have the resources to port this at every new upstream release. Files: 3c721ccb8ceb43370a6eb97ff2dbcd37 798 gnome optional quick-lounge-applet_2.12.1-1.dsc d6c1c4e6b7974ff758b696a5ddb58fd6 602646 gnome optional quick-lounge-applet_2.12.1.orig.tar.gz 89b9487814c264f35034c7b5bf2c53cc 2709 gnome optional quick-lounge-applet_2.12.1-1.diff.gz ab313db4532ed1414c8120b07d071223 103790 gnome optional quick-lounge-applet_2.12.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy2kU+S/PxQH9W2IRAnK7AJ9Tk663FLxcBmH+N6vKV7gETF1IdQCeIS35 oS7M4ISCTp7VhUfPUqZEDUw= =Zhgy -END PGP SIGNATURE- Accepted: quick-lounge-applet_2.12.1-1.diff.gz to pool/main/q/quick-lounge-applet/quick-lounge-applet_2.12.1-1.diff.gz quick-lounge-applet_2.12.1-1.dsc to pool/main/q/quick-lounge-applet/quick-lounge-applet_2.12.1-1.dsc quick-lounge-applet_2.12.1-1_i386.deb to pool/main/q/quick-lounge-applet/quick-lounge-applet_2.12.1-1_i386.deb quick-lounge-applet_2.12.1.orig.tar.gz to pool/main/q/quick-lounge-applet/quick-lounge-applet_2.12.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libunicode-map-perl 0.112-9 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jan 2006 22:46:48 +0200 Source: libunicode-map-perl Binary: libunicode-map-perl Architecture: source i386 Version: 0.112-9 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Niko Tyni [EMAIL PROTECTED] Description: libunicode-map-perl - Perl module for mapping charsets from and to UTF16 Unicode Closes: 320406 Changes: libunicode-map-perl (0.112-9) unstable; urgency=low . * Add debian/watch. * Fix the BIG5 map at build-time to include US-ASCII compatible characters 0-127. (Closes: #320406) * Test the fixed BIG5 map in t/map.t. Files: 19cf7b3ed80e3c1ad652a32792ec0615 726 perl optional libunicode-map-perl_0.112-9.dsc f66d7c30801d24d6af38cf2485916271 3780 perl optional libunicode-map-perl_0.112-9.diff.gz 604c4fe41d8073ab1ba885304d544f14 502320 perl optional libunicode-map-perl_0.112-9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy2g0+NMfSd6w7DERAh3IAKDGu32/UFiToHXp5pwspJJ67cpSqwCgtcts Fnyh6jumGP61VE0sPGrJxto= =B/bk -END PGP SIGNATURE- Accepted: libunicode-map-perl_0.112-9.diff.gz to pool/main/libu/libunicode-map-perl/libunicode-map-perl_0.112-9.diff.gz libunicode-map-perl_0.112-9.dsc to pool/main/libu/libunicode-map-perl/libunicode-map-perl_0.112-9.dsc libunicode-map-perl_0.112-9_i386.deb to pool/main/libu/libunicode-map-perl/libunicode-map-perl_0.112-9_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fail2ban 0.6.0-3 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 12 Jan 2006 18:32:14 -0500
Source: fail2ban
Binary: fail2ban
Architecture: source all
Version: 0.6.0-3
Distribution: unstable
Urgency: low
Maintainer: [EMAIL PROTECTED]
Changed-By: Yaroslav Halchenko [EMAIL PROTECTED]
Description:
fail2ban - bans IPs that cause multiple authentication errors
Closes: 347766
Changes:
fail2ban (0.6.0-3) unstable; urgency=low
.
* ignoreip is now empty by default (closes: #347766)
* increased verbosity in verbose=2 mode: now prints options accepted
from the config file
* to make fail2ban.conf more compact, thus to improve its readability,
fail2ban.conf was converted to use interpolations provided by
ConfigParser class. fw{start,end,{,un}ban} options were moved into
DEFAULT section and required options (port, protocol) were added
Files:
bc1ed707857cdfe36076b6a5cbc30469 611 net optional fail2ban_0.6.0-3.dsc
82542bbcc77ad84cbcd827e22dfd3599 14302 net optional fail2ban_0.6.0-3.diff.gz
b09d9fb6d15d0d95a0a32bad6ae7e56b 34418 net optional fail2ban_0.6.0-3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDy2wILz4Gnv7CP7IRAn0QAKCh+dyq/3IZQ2kkWcf2KOrIy9ma8QCgyP8f
/q0DF7zUVhVy/bHUgb/m3us=
=NQgE
-END PGP SIGNATURE-
Accepted:
fail2ban_0.6.0-3.diff.gz
to pool/main/f/fail2ban/fail2ban_0.6.0-3.diff.gz
fail2ban_0.6.0-3.dsc
to pool/main/f/fail2ban/fail2ban_0.6.0-3.dsc
fail2ban_0.6.0-3_all.deb
to pool/main/f/fail2ban/fail2ban_0.6.0-3_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fetchmail 6.3.1-4 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 10:27:04 +0100 Source: fetchmail Binary: fetchmailconf fetchmail Architecture: source i386 all Version: 6.3.1-4 Distribution: unstable Urgency: low Maintainer: Fetchmail Maintainers [EMAIL PROTECTED] Changed-By: Hector Garcia [EMAIL PROTECTED] Description: fetchmail - SSL enabled POP3, APOP, IMAP mail gatherer/forwarder fetchmailconf - fetchmail configurator Closes: 348037 348134 Changes: fetchmail (6.3.1-4) unstable; urgency=low . [ Nico Golde ] * Fixed broken symlink (Closes: #348134). * removed gzip of fetchmailconf.1 cause we should ignore it, it points to a wrong fetchmail manpage so we set a symlink manually. . [ Hector Garcia ] * Reverted pidfile location (Closes: #348037). * Removed #!/usr/bin/env python from fetchmailconf.py since it is used as a lib not as a script. New dpatch file. Files: 7353c8cefcc621e124f023e8a980b61f 747 mail optional fetchmail_6.3.1-4.dsc 67c321fdfdc9919cbb66b05432288316 44047 mail optional fetchmail_6.3.1-4.diff.gz bde018faf5f9dd0d3149ec6f8f36d35a 112932 mail optional fetchmailconf_6.3.1-4_all.deb 455b8fa6a3a3c36a807525490c5c3182 559268 mail optional fetchmail_6.3.1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy2pWMwsDi2xjdG0RAjmpAJ9KQbc8hNyW9cnIInZwq3/I8c9angCfdm4a d+zCXU3O6J8jh1HGRl5GNyw= =Ysft -END PGP SIGNATURE- Accepted: fetchmail_6.3.1-4.diff.gz to pool/main/f/fetchmail/fetchmail_6.3.1-4.diff.gz fetchmail_6.3.1-4.dsc to pool/main/f/fetchmail/fetchmail_6.3.1-4.dsc fetchmail_6.3.1-4_i386.deb to pool/main/f/fetchmail/fetchmail_6.3.1-4_i386.deb fetchmailconf_6.3.1-4_all.deb to pool/main/f/fetchmail/fetchmailconf_6.3.1-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted imagezoom 0.2.2-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 02:19:47 -0500 Source: imagezoom Binary: mozilla-imagezoom Architecture: source all Version: 0.2.2-2 Distribution: unstable Urgency: low Maintainer: [EMAIL PROTECTED] Changed-By: Yaroslav Halchenko [EMAIL PROTECTED] Description: mozilla-imagezoom - Mozilla context menu option to zoom current image Closes: 348283 Changes: imagezoom (0.2.2-2) unstable; urgency=low . * Updated depends to include firefox (closes: 348283) * Fixed debian/links to create link under /usr/lib/firefox * Removed links for obsolete mozilla-snapshot * Default config file now is installed under /etc/mozilla-extensions * Installing crome.manifest as well Files: c8ef5c34cc393c2791ee83caff86317e 610 web optional imagezoom_0.2.2-2.dsc 2a93ae79279ffdffc7a4f06672ccd00c 2760 web optional imagezoom_0.2.2-2.diff.gz 493e4f4cea16a78b245c7db27ce630ba 55086 web optional mozilla-imagezoom_0.2.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy2quLz4Gnv7CP7IRAqq1AJ4nKClvHD0VBgrN3T5V0GNtKGECZwCdEKzT 1Vq9YEoLzD6r1GMFAPZ0/bA= =dXwp -END PGP SIGNATURE- Accepted: imagezoom_0.2.2-2.diff.gz to pool/main/i/imagezoom/imagezoom_0.2.2-2.diff.gz imagezoom_0.2.2-2.dsc to pool/main/i/imagezoom/imagezoom_0.2.2-2.dsc mozilla-imagezoom_0.2.2-2_all.deb to pool/main/i/imagezoom/mozilla-imagezoom_0.2.2-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-configfile-perl 1.18-5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jan 2006 22:21:56 +0200 Source: libapache-configfile-perl Binary: libapache-configfile-perl Architecture: source all Version: 1.18-5 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Niko Tyni [EMAIL PROTECTED] Description: libapache-configfile-perl - Parse an Apache style httpd.conf configuration file Closes: 329154 Changes: libapache-configfile-perl (1.18-5) unstable; urgency=low . * Migrate to dpatch. * Upgrade to debhelper compatibility level 5. * Move debhelper from Build-Depends-Indep to Build-Depends, as per policy. * Add myself to Uploaders. * Remove leftover extra Maintainer line. * Upgrade to Standards-Version 3.6.2. No changes needed. * Don't ignore the return value of 'make distclean'. * debian/patches/30novalue.dpatch: + handle lines like 'ClearModuleList', where there's no value for the variable. Thanks to Jason Thomas [EMAIL PROTECTED] for the patch. (Closes: #329154) * Don't install an empty /usr/lib/perl5 directory. Files: b2853cc41108c7ec1de9f3af96c741ac 783 perl optional libapache-configfile-perl_1.18-5.dsc 44ed42f2466c1fc610a404e562733f33 4138 perl optional libapache-configfile-perl_1.18-5.diff.gz 462b4c82039ba37b180d82ad4e0d1823 33624 perl optional libapache-configfile-perl_1.18-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy2vN+NMfSd6w7DERAoeIAKCDrSvQqW+ClN6l3UdibwyQzrpZOgCfZplX knvwpsEZt9DatD6lPdKDKYs= =QQwt -END PGP SIGNATURE- Accepted: libapache-configfile-perl_1.18-5.diff.gz to pool/main/liba/libapache-configfile-perl/libapache-configfile-perl_1.18-5.diff.gz libapache-configfile-perl_1.18-5.dsc to pool/main/liba/libapache-configfile-perl/libapache-configfile-perl_1.18-5.dsc libapache-configfile-perl_1.18-5_all.deb to pool/main/liba/libapache-configfile-perl/libapache-configfile-perl_1.18-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache2-mod-auth-pgsql 2.0.3-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 10:57:34 +0100 Source: libapache2-mod-auth-pgsql Binary: libapache2-mod-auth-pgsql Architecture: source i386 Version: 2.0.3-2 Distribution: unstable Urgency: low Maintainer: Marco Nenciarini [EMAIL PROTECTED] Changed-By: Marco Nenciarini [EMAIL PROTECTED] Description: libapache2-mod-auth-pgsql - Module for Apache2 which provides pgsql authentication Changes: libapache2-mod-auth-pgsql (2.0.3-2) unstable; urgency=low . * debian/prerm: Fixed bashism (test with -[ao]). Files: 2ad5831f7f18c1c5c9d6191d7d2fe348 686 web extra libapache2-mod-auth-pgsql_2.0.3-2.dsc a4b949d40fd09e539011c23f8556a10b 4748 web extra libapache2-mod-auth-pgsql_2.0.3-2.diff.gz d898d557cdf07b435b2079ed0b5170be 19122 web extra libapache2-mod-auth-pgsql_2.0.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy3B+aGRzDfCV5eQRAsA8AJ98dcG5vNq6uAGt5W3UlhQgslRJ7wCeNGX4 Y7CP7CSSTNguwHHqG2Y64Es= =LLty -END PGP SIGNATURE- Accepted: libapache2-mod-auth-pgsql_2.0.3-2.diff.gz to pool/main/liba/libapache2-mod-auth-pgsql/libapache2-mod-auth-pgsql_2.0.3-2.diff.gz libapache2-mod-auth-pgsql_2.0.3-2.dsc to pool/main/liba/libapache2-mod-auth-pgsql/libapache2-mod-auth-pgsql_2.0.3-2.dsc libapache2-mod-auth-pgsql_2.0.3-2_i386.deb to pool/main/liba/libapache2-mod-auth-pgsql/libapache2-mod-auth-pgsql_2.0.3-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gkremldk 0.9.7-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 31 Dec 2005 00:34:49 +0100 Source: gkremldk Binary: gkrellm-mldonkey Architecture: source i386 Version: 0.9.7-1 Distribution: unstable Urgency: low Maintainer: Niv Altivanik (Debian Packages) [EMAIL PROTECTED] Changed-By: Niv Altivanik (Debian Packages) [EMAIL PROTECTED] Description: gkrellm-mldonkey - mldonkey plugin for gkrellm2 Closes: 342827 Changes: gkremldk (0.9.7-1) unstable; urgency=low . * New upstream release Upstream Bug fix: gkrellm-mldonkey always forgest split view parameter., thanks to Serge Matveev (Closes: #342827). Files: e904862a95f98fa8c49a6d215c5ada80 651 x11 optional gkremldk_0.9.7-1.dsc 72799e7613528e07fd99f32c4ce29ec5 40806 x11 optional gkremldk_0.9.7.orig.tar.gz 4ae0f13f03c23854b0bf49a727440269 1843 x11 optional gkremldk_0.9.7-1.diff.gz fbf7fd87403c2f6a8e18893fe0d11027 16500 x11 optional gkrellm-mldonkey_0.9.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy28FwM/Gs81MDZ0RAvWqAJ4vyI05b9kcMfI5JWawQfU3vMb2kQCfYWKU gLW/F6ANTj59I3IpHejtnK4= =EUYx -END PGP SIGNATURE- Accepted: gkrellm-mldonkey_0.9.7-1_i386.deb to pool/main/g/gkremldk/gkrellm-mldonkey_0.9.7-1_i386.deb gkremldk_0.9.7-1.diff.gz to pool/main/g/gkremldk/gkremldk_0.9.7-1.diff.gz gkremldk_0.9.7-1.dsc to pool/main/g/gkremldk/gkremldk_0.9.7-1.dsc gkremldk_0.9.7.orig.tar.gz to pool/main/g/gkremldk/gkremldk_0.9.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debian-builder 1.3-6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 January 2006 10:04:21 + Source: debian-builder Binary: debian-builder Architecture: source all Version: 1.3-6 Distribution: unstable Urgency: low Maintainer: Steve Kemp [EMAIL PROTECTED] Changed-By: Steve Kemp [EMAIL PROTECTED] Description: debian-builder - Rebuild Debian packages from source code Closes: 348089 Changes: debian-builder (1.3-6) unstable; urgency=low . * Corrected the spelling of 'athilon-bulder' in the package description. (Closes: #348089) * Updated standards version to 3.6.2 * Updated debhelper compatability to level 4. Files: 3236ecb5197d5c4ccb06181675952a24 564 admin optional debian-builder_1.3-6.dsc 065f88da554d18f98ab2eb4962ec3d82 3707 admin optional debian-builder_1.3-6.diff.gz 6b4039f8dbadc9e691666242783e6af1 11568 admin optional debian-builder_1.3-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy3ABwM/Gs81MDZ0RAsKJAKDTRFysSMrEJD2znNKCbr75EjBp+ACffF7y 5HLIYSmcwX4k5Qc7hlkG9LQ= =nLl0 -END PGP SIGNATURE- Accepted: debian-builder_1.3-6.diff.gz to pool/main/d/debian-builder/debian-builder_1.3-6.diff.gz debian-builder_1.3-6.dsc to pool/main/d/debian-builder/debian-builder_1.3-6.dsc debian-builder_1.3-6_all.deb to pool/main/d/debian-builder/debian-builder_1.3-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debian-builder 1.3-7 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 January 2006 10:07:12 + Source: debian-builder Binary: debian-builder Architecture: source all Version: 1.3-7 Distribution: unstable Urgency: low Maintainer: Steve Kemp [EMAIL PROTECTED] Changed-By: Steve Kemp [EMAIL PROTECTED] Description: debian-builder - Rebuild Debian packages from source code Changes: debian-builder (1.3-7) unstable; urgency=low . * Really fix the spelling. D'oh. Files: ba62896cc89a808a72d2a40f97cede1c 564 admin optional debian-builder_1.3-7.dsc ca3807858daa9e0af8ce4c21a94f5130 3735 admin optional debian-builder_1.3-7.diff.gz 94431dca7712a7485a09e7860b3de63e 11592 admin optional debian-builder_1.3-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy3COwM/Gs81MDZ0RAjqkAKCDqTYwKhgppiruvLibjXeBVwnsMQCgz/Vs 3TWLjRG1rqsGvrYd6pglPZ0= =VM5X -END PGP SIGNATURE- Accepted: debian-builder_1.3-7.diff.gz to pool/main/d/debian-builder/debian-builder_1.3-7.diff.gz debian-builder_1.3-7.dsc to pool/main/d/debian-builder/debian-builder_1.3-7.dsc debian-builder_1.3-7_all.deb to pool/main/d/debian-builder/debian-builder_1.3-7_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xwpe 1.5.29a-4 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 16 Jan 2006 10:56:58 +0100
Source: xwpe
Binary: xwpe
Architecture: source i386
Version: 1.5.29a-4
Distribution: unstable
Urgency: low
Maintainer: Francesco Paolo Lovergine [EMAIL PROTECTED]
Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED]
Description:
xwpe - Programming environment and editor for console and X11
Closes: 346860
Changes:
xwpe (1.5.29a-4) unstable; urgency=low
.
* Policy changed to 3.6.2 (no changes)
* Compatibility level set to 4 for debhelper. Added ${misc:Depends}.
* Removed xlibs-dev dependency and changed in xorg deps.
(closes: #346860)
Files:
8174e55c9f418a8cd0da43d0e1f48db6 655 editors optional xwpe_1.5.29a-4.dsc
153c66ce052f6492fec34cb0fbcd0f80 4415 editors optional xwpe_1.5.29a-4.diff.gz
551cffc650933ac69125f1d8630879a4 10848 editors optional xwpe_1.5.29a-4_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDy3P2pFNRmenyx0cRAjIdAJ96n211CHQtp9uYWYFCyCFAWahM7gCcCHf5
NUZJJcGeTDw2PSA7NbKoBMk=
=mJ2S
-END PGP SIGNATURE-
Accepted:
xwpe_1.5.29a-4.diff.gz
to pool/main/x/xwpe/xwpe_1.5.29a-4.diff.gz
xwpe_1.5.29a-4.dsc
to pool/main/x/xwpe/xwpe_1.5.29a-4.dsc
xwpe_1.5.29a-4_i386.deb
to pool/main/x/xwpe/xwpe_1.5.29a-4_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xml-crimson 1:1.1.3-7 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 11:32:22 +0100 Source: xml-crimson Binary: libcrimson-java libcrimson-java-doc Architecture: source all Version: 1:1.1.3-7 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Arnaud Vandyck [EMAIL PROTECTED] Description: libcrimson-java - XML parser which support the Java API for XML Processing (JAXP) libcrimson-java-doc - XML parser which support the Java API for XML Processing (JAXP) Closes: 348094 Changes: xml-crimson (1:1.1.3-7) unstable; urgency=low . * debian/rules: change the VERSION miniscript to skip the epoch number (closes: #348094) * debian/rules: removed the compiler reference to jikes * removed Takashi Okamoto [EMAIL PROTECTED] from the uploaders Files: aeeb782d6b8f42aa9d2cb38324d3d507 755 libs optional xml-crimson_1.1.3-7.dsc e051810e2826d9c7c8e6615925928046 3175 libs optional xml-crimson_1.1.3-7.diff.gz 455269b06a414adf10fa65766387be1f 193330 libs optional libcrimson-java_1.1.3-7_all.deb b25218e686766389ffc4a0268c674129 195002 doc optional libcrimson-java-doc_1.1.3-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy3e74vzFZu62tMIRAmB7AJwN/VmKrJkHxQXnp8304StR2ldWZACeNrJ1 fTX589vn6EiawUXp67Y2j/4= =Rlmv -END PGP SIGNATURE- Accepted: libcrimson-java-doc_1.1.3-7_all.deb to pool/main/x/xml-crimson/libcrimson-java-doc_1.1.3-7_all.deb libcrimson-java_1.1.3-7_all.deb to pool/main/x/xml-crimson/libcrimson-java_1.1.3-7_all.deb xml-crimson_1.1.3-7.diff.gz to pool/main/x/xml-crimson/xml-crimson_1.1.3-7.diff.gz xml-crimson_1.1.3-7.dsc to pool/main/x/xml-crimson/xml-crimson_1.1.3-7.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xlassie 1.8-10 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 9 Jan 2006 11:12:44 + Source: xlassie Binary: xlassie Architecture: source i386 Version: 1.8-10 Distribution: unstable Urgency: low Maintainer: Barak A. Pearlmutter [EMAIL PROTECTED] Changed-By: Barak A. Pearlmutter [EMAIL PROTECTED] Description: xlassie- Dockable mail notifier w/ message count POP3/APOP/IMAP support Closes: 347005 Changes: xlassie (1.8-10) unstable; urgency=low . * account for broken (apart) xlibs (closes: #347005) Files: 304cf95ba0f27ae6fcf5db36dbd205c7 674 x11 optional xlassie_1.8-10.dsc ea0e61ef2258653156efcac96c9fefa7 18849 x11 optional xlassie_1.8-10.diff.gz 7f4bbdb0c42e577937050a01cfa80f35 19214 x11 optional xlassie_1.8-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDwkwyLz4Gnv7CP7IRAvAoAKCveT6Ut0OJL+m8gZzo04dI7Cx/4gCgjItC fAUx0I6ZsuQ/pLnNfXLe9O8= =3/+5 -END PGP SIGNATURE- Accepted: xlassie_1.8-10.diff.gz to pool/main/x/xlassie/xlassie_1.8-10.diff.gz xlassie_1.8-10.dsc to pool/main/x/xlassie/xlassie_1.8-10.dsc xlassie_1.8-10_i386.deb to pool/main/x/xlassie/xlassie_1.8-10_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted speech-dispatcher 0.5-4 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 12:07:23 +0100 Source: speech-dispatcher Binary: speech-dispatcher-doc-cs libspeechd1 speech-dispatcher cl-speech-dispatcher libspeechd-dev speech-dispatcher-festival Architecture: source all i386 Version: 0.5-4 Distribution: unstable Urgency: low Maintainer: Milan Zamazal [EMAIL PROTECTED] Changed-By: Milan Zamazal [EMAIL PROTECTED] Description: cl-speech-dispatcher - Common Lisp interface to Speech Dispatcher libspeechd-dev - Speech Dispatcher: Development libraries and header files libspeechd1 - Speech Dispatcher: Shared libraries speech-dispatcher - Common interface to speech synthesizers speech-dispatcher-doc-cs - Speech Dispatcher documentation in Czech speech-dispatcher-festival - Festival support for Speech Dispatcher Closes: 326992 348241 Changes: speech-dispatcher (0.5-4) unstable; urgency=low . * Typo in Festival use instructions fixed; closes: #326992. * Remove speech-dispatcher user on `remove' instead of `purge'. Remove its home directory with `rm -r' instead of `deluser --remove-home'. Change owner of the home directory in postinst. Change owner of the log directory recursively. Closes: #348241. Files: 391be705ebbc0ee1e290ff626a4effb2 804 sound extra speech-dispatcher_0.5-4.dsc 87c0c82bc2dd2cf64efb07408576516e 12339 sound extra speech-dispatcher_0.5-4.diff.gz c62564d5bb45b4c1b9f82f8736122996 12114 devel extra cl-speech-dispatcher_0.5-4_all.deb 6ecebdbf8b15f299587d475d6d50507d 4326 sound extra speech-dispatcher-festival_0.5-4_all.deb 2f535a068340752d886f7cb9ba7f717f 30186 doc extra speech-dispatcher-doc-cs_0.5-4_all.deb 431e35a0f4a62dcb844f291a5745fa15 221274 sound extra speech-dispatcher_0.5-4_i386.deb 93e77a6095e7f6410f8e247bf05c7c65 38290 libs extra libspeechd1_0.5-4_i386.deb b52a4ba656987b39cc92a77e3d23b12d 39390 libdevel extra libspeechd-dev_0.5-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy4KikSkk/j3Cm0ERAg4/AJ0fQoC8CiPHFr8QisFLPfyDur5gdACcD8jr ltCYDO+Fl/a7tGCl4ZyBw/4= =16Nh -END PGP SIGNATURE- Accepted: cl-speech-dispatcher_0.5-4_all.deb to pool/main/s/speech-dispatcher/cl-speech-dispatcher_0.5-4_all.deb libspeechd-dev_0.5-4_i386.deb to pool/main/s/speech-dispatcher/libspeechd-dev_0.5-4_i386.deb libspeechd1_0.5-4_i386.deb to pool/main/s/speech-dispatcher/libspeechd1_0.5-4_i386.deb speech-dispatcher-doc-cs_0.5-4_all.deb to pool/main/s/speech-dispatcher/speech-dispatcher-doc-cs_0.5-4_all.deb speech-dispatcher-festival_0.5-4_all.deb to pool/main/s/speech-dispatcher/speech-dispatcher-festival_0.5-4_all.deb speech-dispatcher_0.5-4.diff.gz to pool/main/s/speech-dispatcher/speech-dispatcher_0.5-4.diff.gz speech-dispatcher_0.5-4.dsc to pool/main/s/speech-dispatcher/speech-dispatcher_0.5-4.dsc speech-dispatcher_0.5-4_i386.deb to pool/main/s/speech-dispatcher/speech-dispatcher_0.5-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kpowersave 0.5.2-1 (source i386 alpha)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 02:02:45 +0100 Source: kpowersave Binary: kpowersave Architecture: source i386 alpha Version: 0.5.2-1 Distribution: unstable Urgency: low Maintainer: Michael Biebl [EMAIL PROTECTED] Changed-By: Michael Biebl [EMAIL PROTECTED] Description: kpowersave - frontend to powersave for setting user specific policies Changes: kpowersave (0.5.2-1) unstable; urgency=low . * New upstream release. * Removed patches absolute_build_path_fix.diff and sound_files_path.diff, fixed upstream. * Tightened dependencies on powersave, version 0.11.2 or newer is required. * Use Debian libtool and regenerate the autotools files. + Added build dependencies to automake1.9, autoconf and libtool. * hal and dbus are now mandatory. Added the corresponding build dependencies. * Removed the build dependency on libqt3-compat-headers. Package has been fixed upstream to compile cleanly without it. Files: a31e60a79f961394b8223d027be26e2d 741 kde optional kpowersave_0.5.2-1.dsc 6ca07fa0f480cb0041677600c1769307 2395101 kde optional kpowersave_0.5.2.orig.tar.gz 9a4afc732945fb1bd4266f07e28b47ff 9199 kde optional kpowersave_0.5.2-1.diff.gz 8df0ec645b449fce69bb8376dafa132b 2204316 kde optional kpowersave_0.5.2-1_i386.deb fa07edfe7d005f720964bf4c7f709293 2218090 kde optional kpowersave_0.5.2-1_alpha.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy4v6ipBneRiAKDwRAjxeAJ4hD6v4hdDosjNJxbTxWRncOPiysACZASIl g8piu3NGEWoknC6RykCu38I= =ZC1J -END PGP SIGNATURE- Accepted: kpowersave_0.5.2-1.diff.gz to pool/main/k/kpowersave/kpowersave_0.5.2-1.diff.gz kpowersave_0.5.2-1.dsc to pool/main/k/kpowersave/kpowersave_0.5.2-1.dsc kpowersave_0.5.2-1_alpha.deb to pool/main/k/kpowersave/kpowersave_0.5.2-1_alpha.deb kpowersave_0.5.2-1_i386.deb to pool/main/k/kpowersave/kpowersave_0.5.2-1_i386.deb kpowersave_0.5.2.orig.tar.gz to pool/main/k/kpowersave/kpowersave_0.5.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apache2 2.0.55-4 (source all i386 powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 26 Nov 2005 19:06:32 +1100 Source: apache2 Binary: apache2-utils apache2 apache2-prefork-dev apache2-mpm-prefork apache2-doc libapr0-dev apache2-mpm-worker libapr0 apache2-threaded-dev apache2-common apache2-mpm-perchild Architecture: all i386 powerpc source Version: 2.0.55-4 Distribution: unstable Urgency: low Maintainer: Debian Apache Maintainers debian-apache@lists.debian.org Changed-By: Adam Conrad [EMAIL PROTECTED] Description: apache2- next generation, scalable, extendable web server apache2-common - next generation, scalable, extendable web server apache2-doc - documentation for apache2 apache2-mpm-perchild - experimental high speed perchild threaded model for Apache2 apache2-mpm-prefork - traditional model for Apache2 apache2-mpm-worker - high speed threaded model for Apache2 apache2-prefork-dev - development headers for apache2 apache2-threaded-dev - development headers for apache2 apache2-utils - utility programs for webservers libapr0- the Apache Portable Runtime libapr0-dev - development headers for libapr Closes: 307921 330275 339323 340761 345922 Changes: apache2 (2.0.55-4) unstable; urgency=low . * Add 050_mod_imap_CVE-2005-3352 to escape untrusted referer headers in mod_imap before outputting HTML to avoid XSS attacks; see CVE-2005-3352 * Add 051_mod_ssl_CVE-2005-3357 to avoid a remote denial of service in threaded MPMs when making a non-SSL connection to an SSL-enabled port on a server with a custom 400 error document defined; see CVE-2005-3357 * Clean up our use of trailing slashes on directories in debian/rules, so the newer, pickier, obviously very improved coreutils doesn't bite us. * Remove some cruft from apache2-common's postinst, dealing with upgrade scenarios from versions older than those released in Sarge or Warty. * Use SHELL := sh -e in debian/rules, so the build will stop on shell errors, instead of blundering on to later make targets (closes: #340761) * Recreate /var/run/apache2 and /var/lock/apache2 in our init script, in case the user has /var/run and /var/lock on tmpfs, which is fasionable. * Make our init script a /bin/bash script instead of a /bin/sh script, so we can abuse it with regex globbing (#348189, #347962, #340955, #342008) * Take patch from Adrian Bridgett to output errors from our config test in the init script, but only do so when we're VERBOSE (closes: #339323) * In the spirit of the LSB, make our init script exit 2 when called with incorrect arguments, and exit 4 when asked for status (closes: #330275) * Fix the default site to not mix configuration syntax (closes: #345922) * Mention apxs2 in the apache2-*-dev long descriptions (closes: #307921) Files: 01501a6dd4111291920c974b0af4e5ae 806372 net optional apache2-common_2.0.55-4_i386.deb 0656e2babab9ecbdc78d59bffe237710 214972 net optional apache2-mpm-prefork_2.0.55-4_powerpc.deb 0d6643b5d7e227651c42df1d99964f99 170580 devel optional apache2-prefork-dev_2.0.55-4_powerpc.deb 22e717e15276919bd68fb5bcb9bf8c41 212462 net optional apache2-mpm-worker_2.0.55-4_i386.deb 265b56a335e9dc2234b16e577303f082 92672 net optional apache2-utils_2.0.55-4_i386.deb 273312b083b1cb6fc903792c668b9f0c 103038 net optional apache2-utils_2.0.55-4_powerpc.deb 2909d8aa6b57ffa0abb1846e309cc0ca 170570 devel optional apache2-prefork-dev_2.0.55-4_i386.deb 30953595c4b56c44db9309e5093c59b3 280456 libdevel optional libapr0-dev_2.0.55-4_powerpc.deb 317cd63f07cb37bd40fed7c6486246bc 266942 libdevel optional libapr0-dev_2.0.55-4_i386.deb 38850ccae940e633852be1ab08efc5b4 171354 devel optional apache2-threaded-dev_2.0.55-4_i386.deb 3a5aad7409067cca0d167b5b37d2b90a 218804 net optional apache2-mpm-worker_2.0.55-4_powerpc.deb 3fdac5a0dd810227a6d0c6845a5faf05 219276 net optional apache2-mpm-perchild_2.0.55-4_powerpc.deb 6e74b5b7438a011a284a35e614336afe 35392 web optional apache2_2.0.55-4_i386.deb 88e3e55be774600ab46cbd0344f65f2a 137470 net optional libapr0_2.0.55-4_i386.deb 897e5da766c1ee27c080b3cd43fb69eb 209030 net optional apache2-mpm-prefork_2.0.55-4_i386.deb 8b190e18e94ceb14a02dbbfa2b90486e 2123842 doc optional apache2-doc_2.0.55-4_all.deb a41ec991f06a260b7d19127f06ff7d98 858630 net optional apache2-common_2.0.55-4_powerpc.deb a77979e4012d85d6e4058a267c7b6ab8 115301 net optional apache2_2.0.55-4.diff.gz c1eef4372d3e58201a55a3fe41d65c01 212866 net optional apache2-mpm-perchild_2.0.55-4_i386.deb aca2321dd3b7bfd5ca33fc3cbc65 1130 net optional apache2_2.0.55-4.dsc e52e1e75827892140511c1462177119f 171356 devel optional apache2-threaded-dev_2.0.55-4_powerpc.deb f0b0c2e2892763dbbf0c7a44311b88d4 140534 net optional libapr0_2.0.55-4_powerpc.deb f535aeec0eda0ec60716a88f6e5e11de 35398 web optional apache2_2.0.55-4_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux)
Accepted hp2xx 3.4.4-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Jan 2006 20:39:03 +0100 Source: hp2xx Binary: hp2xx Architecture: source i386 Version: 3.4.4-3 Distribution: unstable Urgency: low Maintainer: Christian T. Steigies [EMAIL PROTECTED] Changed-By: Christian T. Steigies [EMAIL PROTECTED] Description: hp2xx - A HPGL converter into some vector- and raster formats Closes: 346702 Changes: hp2xx (3.4.4-3) unstable; urgency=low . * build-depend on libx11-dev instead of removed xlibs-dev (closes: #346702) * update to use debhelper 5 * fix bug in manpage * updated Standards-Version to 3.6.2 (no changes) Files: d7f8228ff33316231fb70fe92063a167 635 graphics optional hp2xx_3.4.4-3.dsc eb90fe2773ad15706acf35f310a2bf89 3529 graphics optional hp2xx_3.4.4-3.diff.gz b85d79262ed733196ff47162a0a878be 350498 graphics optional hp2xx_3.4.4-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy5DyhWcuXd2lEoARAkR5AJ9g1cjYo43+r4LaBPQmht6anHO5egCePdr+ sR4TH6MXMb7teP9bjYdi9LU= =nvZz -END PGP SIGNATURE- Accepted: hp2xx_3.4.4-3.diff.gz to pool/main/h/hp2xx/hp2xx_3.4.4-3.diff.gz hp2xx_3.4.4-3.dsc to pool/main/h/hp2xx/hp2xx_3.4.4-3.dsc hp2xx_3.4.4-3_i386.deb to pool/main/h/hp2xx/hp2xx_3.4.4-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnokii 0.6.8-0.3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Jan 2006 14:45:13 +0100 Source: gnokii Binary: gnokii-smsd-mysql gnokii-smsd libgnokii2 gnokii libgnokii2-dev gnokii-smsd-pgsql Architecture: source i386 Version: 0.6.8-0.3 Distribution: unstable Urgency: low Maintainer: Bradley Marshall [EMAIL PROTECTED] Changed-By: Thijs Kinkhorst [EMAIL PROTECTED] Description: gnokii - Datasuite for the mobile phones (console X) gnokii-smsd - SMS Daemon for Nokia mobile phones gnokii-smsd-mysql - SMSD plugin for the MySQL RDBMS gnokii-smsd-pgsql - SMSD plugin for the PostgreSQL RDBMS libgnokii2 - Gnokii library libgnokii2-dev - Gnokii library Closes: 334070 343813 346710 348057 Changes: gnokii (0.6.8-0.3) unstable; urgency=low . * NMU with adopter's consent to fix up dependencies. . * Change build-depends from xlibs-dev to libxpm-dev, libxt-dev (Closes: #346710). * Upgrade dependency on libmysqlcient12-dev to libmysqlclient15-dev (Closes: #343813). * Drop outdated dependency on passwd, add required pre-depends on adduser (Closes: #334070). * Remove po/stamp-po on clean, so that locale files are generated. (Closes: #348057). Files: badb7c30a1317ad14c0701a771e4fd35 848 comm optional gnokii_0.6.8-0.3.dsc f7cba5a63f5595b7e59670e44ca0ee68 69612 comm optional gnokii_0.6.8-0.3.diff.gz 202f7b8c73c410e08ba5e24c1416aed5 1189344 comm optional gnokii_0.6.8-0.3_i386.deb 99ee625c19accc0d5990735e24f16bb7 26340 comm optional gnokii-smsd_0.6.8-0.3_i386.deb fa44b1a267780adc2dd115cf5e6ad135 9810 comm optional gnokii-smsd-mysql_0.6.8-0.3_i386.deb 68837358d7da77e9878770e5ebf766cf 9558 comm optional gnokii-smsd-pgsql_0.6.8-0.3_i386.deb 629c83eb9fa815b2674149c1b9a6f0b5 188662 comm optional libgnokii2_0.6.8-0.3_i386.deb 0493e7a39829b97d0e79cf4c9dba40b2 263624 comm optional libgnokii2-dev_0.6.8-0.3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy5y8xa93SlhRC1oRAjoeAKCIXXhEHF6KHUGGhcVBYnmep0XsBACg6LbC JrK+/GflQwW1iMWsW97b8kw= =69BJ -END PGP SIGNATURE- Accepted: gnokii-smsd-mysql_0.6.8-0.3_i386.deb to pool/main/g/gnokii/gnokii-smsd-mysql_0.6.8-0.3_i386.deb gnokii-smsd-pgsql_0.6.8-0.3_i386.deb to pool/main/g/gnokii/gnokii-smsd-pgsql_0.6.8-0.3_i386.deb gnokii-smsd_0.6.8-0.3_i386.deb to pool/main/g/gnokii/gnokii-smsd_0.6.8-0.3_i386.deb gnokii_0.6.8-0.3.diff.gz to pool/main/g/gnokii/gnokii_0.6.8-0.3.diff.gz gnokii_0.6.8-0.3.dsc to pool/main/g/gnokii/gnokii_0.6.8-0.3.dsc gnokii_0.6.8-0.3_i386.deb to pool/main/g/gnokii/gnokii_0.6.8-0.3_i386.deb libgnokii2-dev_0.6.8-0.3_i386.deb to pool/main/g/gnokii/libgnokii2-dev_0.6.8-0.3_i386.deb libgnokii2_0.6.8-0.3_i386.deb to pool/main/g/gnokii/libgnokii2_0.6.8-0.3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kaffe 2:1.1.6.91-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 15 Jan 2006 14:23:52 +0100 Source: kaffe Binary: kaffe-dev kaffe-common kaffe-pthreads kaffe-doc kaffe jikes-kaffe kaffe-jthreads Architecture: source all i386 Version: 2:1.1.6.91-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: jikes-kaffe - Wrapper for jikes using Kaffe classes kaffe - A JVM to run Java bytecode kaffe-common - Files shared between all Kaffe VM versions kaffe-dev - Header files and other resources for building against Kaffe kaffe-doc - Documentation for the Kaffe VM kaffe-jthreads - A green threads enabled version of the Kaffe VM kaffe-pthreads - A POSIX threads enabled version of the Kaffe VM Closes: 335227 335649 337560 338599 338628 346714 Changes: kaffe (2:1.1.6.91-1) unstable; urgency=low . * New upstream release candidate 1 (1.1.7-rc1) + Dropped patches which are applied upstream 01_Tomcat4SecurityManager.patch, 02_JarCacheUse_Fix.patch + Updated patch 03_RegisterIconvCharsetProvider.patch + Fixes gui apps assertion failure (closes: #337560, #335649) + Fixes empty file handling causing a failure of rmic (closes: #335227) + Fixes xml handling leading to NPE in eclipse ant code (closes: #338599) * Adjusted configure options and paths for upstream changes + Use --with-glibj-zip instead of --with-rt-jar configure option + Update glibj.zip location for pthreads configure option + debian/FileActions, debian/wrappers/jikes-kaffe adjust for change of rt.jar into glibj.zip (added lintian override) + debian/kaffe.links, removed link Klasses.jar + Configure with --disable-fastjar - use system fastjar instead * xorg build-deps transition (closes: #346714) Removed xlibs-dev, added libxtst-dev, libx11-dev, libxext-dev libxtst-dev and x-dev to Build-Dependencies * Switch compiler to ecj by default + debian/control: build-depend on ecj-bootstrap-gcj | ecj-bootstrap, kaffe-pthreads, kaffe-jthreads depend on ecj-bootstrap instead of jikes + Remove rules.arm, rules.mips - ecj is now default compiler + debian/rules: use /usr/bin/ecj alternative, adjust glibj.zip path and make ecj default compiler + Removed hardcoded 'build.compiler=jikes' property in VMsystemProperties.java to allow ecj usage (01_RemoveJikesBuildCompilerSetting.patch). + Applied patches (02_IncludeEcjCompilerInToolsJar*.patch) shamelessly stolen from java-gcj-compat upstream to supply a com/sun/ entrypoint to ecj for usage by ant + Adjusted jikes-kaffe wrapper script, reworked dependencies * Bumped debhelper version to 4 * Rewritten and enhanced manpages - javah, javap, native2ascii, rmic, rmiregistry, serialver (closes: #338628) Files: eec68bc155720948bfa49f0a0817f9ed 1190 interpreters optional kaffe_1.1.6.91-1.dsc 0e104f6e029f00e84a7467135f56e975 14328900 interpreters optional kaffe_1.1.6.91.orig.tar.gz 6fc1b6a9717378c299877b73039faba3 34620 interpreters optional kaffe_1.1.6.91-1.diff.gz c7cd14b306be6144ce342304c01044fc 74028 interpreters optional kaffe_1.1.6.91-1_all.deb d524d6c4e8f529a995fd4f43dd2a1819 7809248 interpreters optional kaffe-common_1.1.6.91-1_all.deb da1f6e083797ca090071883ba9426abe 89510 interpreters optional kaffe-dev_1.1.6.91-1_all.deb 217b68a69c7d00c1e37b288a4c4997c5 72390 interpreters optional jikes-kaffe_1.1.6.91-1_all.deb 625974b9119e5845c7944f3fde9c3eb5 159340 interpreters optional kaffe-doc_1.1.6.91-1_all.deb dbd82f2e3cd7b97e860a0f8664058459 598358 interpreters optional kaffe-jthreads_1.1.6.91-1_i386.deb dcb54445c3cac71140e3aab9b88710cf 654710 interpreters optional kaffe-pthreads_1.1.6.91-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy6mtWSOgCCdjSDsRAsavAJ95JHcpuQ6LVoR3FL9Tu+mo7Z9n3wCfQFmz DH0BeHyhnCrnI/4zqIHGvBw= =OYHG -END PGP SIGNATURE- Accepted: jikes-kaffe_1.1.6.91-1_all.deb to pool/main/k/kaffe/jikes-kaffe_1.1.6.91-1_all.deb kaffe-common_1.1.6.91-1_all.deb to pool/main/k/kaffe/kaffe-common_1.1.6.91-1_all.deb kaffe-dev_1.1.6.91-1_all.deb to pool/main/k/kaffe/kaffe-dev_1.1.6.91-1_all.deb kaffe-doc_1.1.6.91-1_all.deb to pool/main/k/kaffe/kaffe-doc_1.1.6.91-1_all.deb kaffe-jthreads_1.1.6.91-1_i386.deb to pool/main/k/kaffe/kaffe-jthreads_1.1.6.91-1_i386.deb kaffe-pthreads_1.1.6.91-1_i386.deb to pool/main/k/kaffe/kaffe-pthreads_1.1.6.91-1_i386.deb kaffe_1.1.6.91-1.diff.gz to pool/main/k/kaffe/kaffe_1.1.6.91-1.diff.gz kaffe_1.1.6.91-1.dsc to pool/main/k/kaffe/kaffe_1.1.6.91-1.dsc kaffe_1.1.6.91-1_all.deb to pool/main/k/kaffe/kaffe_1.1.6.91-1_all.deb kaffe_1.1.6.91.orig.tar.gz to pool/main/k/kaffe/kaffe_1.1.6.91.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ekg2 20060116+1232-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 13:39:54 +0100 Source: ekg2 Binary: ekg2 Architecture: source i386 Version: 20060116+1232-1 Distribution: experimental Urgency: low Maintainer: Marcin Owsiany [EMAIL PROTECTED] Changed-By: Marcin Owsiany [EMAIL PROTECTED] Description: ekg2 - instant messenger and IRC client for UNIX systems Closes: 346232 Changes: ekg2 (20060116+1232-1) experimental; urgency=low . * New snapshot from upstream * Fixed the symlinks to .txt files in doc dir Closes: #346232 Files: 16315f78fcf29a3052e27bd73df7e3b3 892 net optional ekg2_20060116+1232-1.dsc 89eb9b684f97656a8f439cc5268bba5c 530220 net optional ekg2_20060116+1232.orig.tar.gz e6dd88e3ddc3995fcc06908a008d852a 28383 net optional ekg2_20060116+1232-1.diff.gz 4663f9b6397afc3719d6b590e62a5115 1196250 net optional ekg2_20060116+1232-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy6QKOg2KoGD0EhYRAtkrAJ0UO9uCIgFxN0NiMjkLRA7gLX8zcwCbB4gJ O0dpFLsUfrHLhLaxAj51Fj0= =QC5K -END PGP SIGNATURE- Accepted: ekg2_20060116+1232-1.diff.gz to pool/main/e/ekg2/ekg2_20060116+1232-1.diff.gz ekg2_20060116+1232-1.dsc to pool/main/e/ekg2/ekg2_20060116+1232-1.dsc ekg2_20060116+1232-1_i386.deb to pool/main/e/ekg2/ekg2_20060116+1232-1_i386.deb ekg2_20060116+1232.orig.tar.gz to pool/main/e/ekg2/ekg2_20060116+1232.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommons-jxpath-java 1.2-7 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 5 Jan 2006 10:24:15 +0100 Source: libcommons-jxpath-java Binary: libcommons-jxpath-java-doc libcommons-jxpath-java Architecture: source all Version: 1.2-7 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: libcommons-jxpath-java - manipulate javabean using XPath syntax libcommons-jxpath-java-doc - Javadoc API for libcommons-jxpath-java Changes: libcommons-jxpath-java (1.2-7) unstable; urgency=low . * Removed libgnujaxp-java dependency - not needed anymore * debian/rules: Removed jikes build compiler property * Removed Takashi, Ola and Stefan from Uploaders/Co-Maintainers as they never uploaded a revision of this package. Files: 57c0e7ae55704d58d0fbad961ea8c327 914 libs optional libcommons-jxpath-java_1.2-7.dsc 40c42da0460444a584e1f720e255e87b 3896 libs optional libcommons-jxpath-java_1.2-7.diff.gz b2853c9733c92bc0b65c228698542730 261240 libs optional libcommons-jxpath-java_1.2-7_all.deb 9e13849fb5a97cabccc6e9f13223162c 308946 libs optional libcommons-jxpath-java-doc_1.2-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy7XhWSOgCCdjSDsRAuILAJ91Db4EHSAdVtdeOrv7Nc04am0iDACdGzr+ 5GPoF0lM29x9y9g9vjUA91s= =fZV/ -END PGP SIGNATURE- Accepted: libcommons-jxpath-java-doc_1.2-7_all.deb to pool/main/libc/libcommons-jxpath-java/libcommons-jxpath-java-doc_1.2-7_all.deb libcommons-jxpath-java_1.2-7.diff.gz to pool/main/libc/libcommons-jxpath-java/libcommons-jxpath-java_1.2-7.diff.gz libcommons-jxpath-java_1.2-7.dsc to pool/main/libc/libcommons-jxpath-java/libcommons-jxpath-java_1.2-7.dsc libcommons-jxpath-java_1.2-7_all.deb to pool/main/libc/libcommons-jxpath-java/libcommons-jxpath-java_1.2-7_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted flow-tools 1:0.68-9 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 15:54:15 +0200 Source: flow-tools Binary: libcflow-perl flow-tools flow-tools-dev Architecture: source i386 Version: 1:0.68-9 Distribution: unstable Urgency: low Maintainer: Radu Spineanu [EMAIL PROTECTED] Changed-By: Radu Spineanu [EMAIL PROTECTED] Description: flow-tools - collects and processes NetFlow data flow-tools-dev - development files for flow-tools libcflow-perl - perl module for analyzing raw IP flow files written by cflowd Closes: 343780 Changes: flow-tools (1:0.68-9) unstable; urgency=low . * Updated libmysqlclient depedency (closes: #343780) Files: c1006d0c82d854b996efce466150d1e0 806 net optional flow-tools_0.68-9.dsc fa5497649cb8b57bae475b29fbee60a7 15844 net optional flow-tools_0.68-9.diff.gz 8f880583e622d453002ddafc5e3c6463 1160130 net optional flow-tools_0.68-9_i386.deb 1927fad0967386d5bbd842063b3f702d 203430 libdevel optional flow-tools-dev_0.68-9_i386.deb 38e9bef21c1d3ab7f17effe293d6e18c 80056 perl optional libcflow-perl_0.68-9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy6Y4JkMZOMmr+9MRAtIrAKCtsIFfJCu93OKPaJH81+6y3LUiNACeM3nX hRC7chmUm8JPd1/GK70ZHTY= =lvlo -END PGP SIGNATURE- Accepted: flow-tools-dev_0.68-9_i386.deb to pool/main/f/flow-tools/flow-tools-dev_0.68-9_i386.deb flow-tools_0.68-9.diff.gz to pool/main/f/flow-tools/flow-tools_0.68-9.diff.gz flow-tools_0.68-9.dsc to pool/main/f/flow-tools/flow-tools_0.68-9.dsc flow-tools_0.68-9_i386.deb to pool/main/f/flow-tools/flow-tools_0.68-9_i386.deb libcflow-perl_0.68-9_i386.deb to pool/main/f/flow-tools/libcflow-perl_0.68-9_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pose 3.5-9 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 09:42:32 -0300 Source: pose Binary: pose-doc pose-profile pose Architecture: source i386 all Version: 3.5-9 Distribution: unstable Urgency: low Maintainer: Lucas Wall [EMAIL PROTECTED] Changed-By: Lucas Wall [EMAIL PROTECTED] Description: pose - emulates the hardware for most Palm Computing Platform devices pose-doc - emulates the hardware for most Palm Computing Platform devices pose-profile - emulates the hardware for most Palm Computing Platform devices Closes: 346850 Changes: pose (3.5-9) unstable; urgency=low . * Removed dependancy on xlibs-dev. (closes: #346850) Files: c9085c09962a7df9e4b907a7c695f36f 653 contrib/otherosfs optional pose_3.5-9.dsc 20a50f6b84508c894ad24da8ca04ccbb 186834 contrib/otherosfs optional pose_3.5-9.diff.gz 5dc0829d223fea5b3bc2daf41782d823 1232224 contrib/otherosfs optional pose-doc_3.5-9_all.deb db4e6d71daf956b99d24c09db5727cb7 1078910 contrib/otherosfs optional pose_3.5-9_i386.deb 577a1ddfc5945dfb70d567e6a9204ab1 1090130 contrib/otherosfs optional pose-profile_3.5-9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy6T4vJtHM4T7RtYRAtOtAKDHRzbO38CMYbFm9ESpGrAs+ziKowCeOvph nYboWEcggIvU9+c66oLdnNI= =/YEL -END PGP SIGNATURE- Accepted: pose-doc_3.5-9_all.deb to pool/contrib/p/pose/pose-doc_3.5-9_all.deb pose-profile_3.5-9_i386.deb to pool/contrib/p/pose/pose-profile_3.5-9_i386.deb pose_3.5-9.diff.gz to pool/contrib/p/pose/pose_3.5-9.diff.gz pose_3.5-9.dsc to pool/contrib/p/pose/pose_3.5-9.dsc pose_3.5-9_i386.deb to pool/contrib/p/pose/pose_3.5-9_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libjaxen-java 1.0FCS-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 5 Jan 2006 10:34:13 +0100 Source: libjaxen-java Binary: libjaxen-java Architecture: source all Version: 1.0FCS-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: libjaxen-java - Java XPath engine for use on a variety of XML object models Changes: libjaxen-java (1.0FCS-3) unstable; urgency=low . * Removed libgnujaxp-java dependency - not needed anymore * Removed unused build dependency / dependency on old package libdom1-java * debian/rules: Removed jikes build compiler property * Bumped debhelper version dependency to fix linda error * Added myself to uploaders Files: 0eeaddb6eee173a3b5db57f095f7c3c6 788 libs optional libjaxen-java_1.0FCS-3.dsc c80baab9c41364ed843885a825e2fcd9 3034 libs optional libjaxen-java_1.0FCS-3.diff.gz 9d329d297bd2b00a0760c0f37198a8e6 146086 libs optional libjaxen-java_1.0FCS-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy7dpWSOgCCdjSDsRAtNaAJ0SaolNHCvQ3IMB96J5WpZcMMAjkgCeItpV jzTPWhHYBsO5B5e0pgZiAIg= =U3Zk -END PGP SIGNATURE- Accepted: libjaxen-java_1.0FCS-3.diff.gz to pool/main/libj/libjaxen-java/libjaxen-java_1.0FCS-3.diff.gz libjaxen-java_1.0FCS-3.dsc to pool/main/libj/libjaxen-java/libjaxen-java_1.0FCS-3.dsc libjaxen-java_1.0FCS-3_all.deb to pool/main/libj/libjaxen-java/libjaxen-java_1.0FCS-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libjdom0-java 0.9b-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 5 Jan 2006 10:04:38 +0100 Source: libjdom0-java Binary: libjdom0-java Architecture: source all Version: 0.9b-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: libjdom0-java - lightweight and fast library using XML Changes: libjdom0-java (0.9b-2) unstable; urgency=low . * Removed libgnujaxp-java dependency - not needed anymore + Updated debian/rules accordingly + Removed dependencies from build-depends and depends * Simplified depends line to kaffe | java1-runtime | java2-runtime * Removed explicit usage of jikes compiler for upcoming kaffe transition + debian/rules: use javac instead of jikes-kaffe + debian/control: remove build-dep on jikes-kaffe * Added compat file (level 4), adjusted debian/rules * Standards-Version 3.6.2 (no changes) * Removed Takashi from Uploaders, added myself Files: 14b9632ab922d80a0cfb30304da096d1 731 libs optional libjdom0-java_0.9b-2.dsc 73d88ba7dc386933665b7dfb4bd5c7e0 4028 libs optional libjdom0-java_0.9b-2.diff.gz 59b2ac675db90ebbce61e3e728cbbf2e 399592 libs optional libjdom0-java_0.9b-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy7k+WSOgCCdjSDsRAufoAJ9v6iLpxjfuppP166HeqvaLw06ZLgCfYOLy KxvmLgohQ5BCOznxkSt1sMQ= =IcT4 -END PGP SIGNATURE- Accepted: libjdom0-java_0.9b-2.diff.gz to pool/main/libj/libjdom0-java/libjdom0-java_0.9b-2.diff.gz libjdom0-java_0.9b-2.dsc to pool/main/libj/libjdom0-java/libjdom0-java_0.9b-2.dsc libjdom0-java_0.9b-2_all.deb to pool/main/libj/libjdom0-java/libjdom0-java_0.9b-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted imview 1.1.8-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 2 Dec 2005 00:36:21 +0200 Source: imview Binary: imview Architecture: source i386 Version: 1.1.8-4 Distribution: unstable Urgency: low Maintainer: Teemu Ikonen [EMAIL PROTECTED] Changed-By: Teemu Ikonen [EMAIL PROTECTED] Description: imview - Image viewing and analysis application Closes: 347398 Changes: imview (1.1.8-4) unstable; urgency=low . * Change configure.in to use pkg-config instead of Magick-config to drop spurious shared library dependencies (closes: #347398) * Fix lintian warning about old FSF address in debian/copyright Files: 402ce32d2f59f34820422f19de3b3cf1 702 science optional imview_1.1.8-4.dsc 7edd929a99ae7e32ab537b9b4983c58f 13246 science optional imview_1.1.8-4.diff.gz 757568582130459ad7a7f6ca78143df4 573328 science optional imview_1.1.8-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy6dIYDBbMcCf01oRAisFAJ9RctrlTLuLbA4jNvJ3FXfNofQy3wCfSAdY iRolpVSRL0cixUY9jPGy9dU= =Y2mp -END PGP SIGNATURE- Accepted: imview_1.1.8-4.diff.gz to pool/main/i/imview/imview_1.1.8-4.diff.gz imview_1.1.8-4.dsc to pool/main/i/imview/imview_1.1.8-4.dsc imview_1.1.8-4_i386.deb to pool/main/i/imview/imview_1.1.8-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libsaxpath-java 1.0.0FCS-6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 5 Jan 2006 10:29:59 +0100 Source: libsaxpath-java Binary: libsaxpath-java Architecture: source all Version: 1.0.0FCS-6 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: libsaxpath-java - Java XPath engine for use on a variety of XML object models Changes: libsaxpath-java (1.0.0FCS-6) unstable; urgency=low . * Removed libgnujaxp-java dependency - not needed anymore * Simplified depends line to kaffe | java1-runtime | java2-runtime * debian/rules: Removed jikes build compiler property * Bumped debhelper version to fix linda error * Added myself to uploaders Files: ec26d6ef2f253f66b6a520dfd3256489 767 libs optional libsaxpath-java_1.0.0FCS-6.dsc 048fe749c31728c75c53663e5d6c0a3c 3177 libs optional libsaxpath-java_1.0.0FCS-6.diff.gz 2dd25b50b5c2aa22f6d7e240e910c6b5 24460 libs optional libsaxpath-java_1.0.0FCS-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy7xPWSOgCCdjSDsRAgcIAJ0YBODFSddGtezPcFBLdMzZTmSs4gCghrj4 v65eTxzEVRUqTYOdJMHqkME= =dBF3 -END PGP SIGNATURE- Accepted: libsaxpath-java_1.0.0FCS-6.diff.gz to pool/main/libs/libsaxpath-java/libsaxpath-java_1.0.0FCS-6.diff.gz libsaxpath-java_1.0.0FCS-6.dsc to pool/main/libs/libsaxpath-java/libsaxpath-java_1.0.0FCS-6.dsc libsaxpath-java_1.0.0FCS-6_all.deb to pool/main/libs/libsaxpath-java/libsaxpath-java_1.0.0FCS-6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libjdom1-java 1.0-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 5 Jan 2006 10:18:57 +0100 Source: libjdom1-java Binary: libjdom1-java Architecture: source all Version: 1.0-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Wolfgang Baer [EMAIL PROTECTED] Description: libjdom1-java - lightweight and fast library using XML Changes: libjdom1-java (1.0-3) unstable; urgency=low . * Removed libgnujaxp-java dependency - not needed anymore + Updated debian/rules accordingly + Removed dependencies from build-depends and depends * Simplified depends line to kaffe | java1-runtime | java2-runtime * debian/rules: Removed jikes build compiler property * Removed Takashi from Uploaders Files: c4c5032a7095bfa988982d75936a9315 733 libs optional libjdom1-java_1.0-3.dsc 5731b7f6cbf6940bae36a89ccbee74af 3770 libs optional libjdom1-java_1.0-3.diff.gz f48607fb36a4a22898ba88b21b95401a 341328 libs optional libjdom1-java_1.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDy7utWSOgCCdjSDsRAkEKAJwMdb3zXGGw34nMNFoUnJG7by856QCfUneD Pb+/LX0rz9KPDnf8ibtcw00= =KtA0 -END PGP SIGNATURE- Accepted: libjdom1-java_1.0-3.diff.gz to pool/main/libj/libjdom1-java/libjdom1-java_1.0-3.diff.gz libjdom1-java_1.0-3.dsc to pool/main/libj/libjdom1-java/libjdom1-java_1.0-3.dsc libjdom1-java_1.0-3_all.deb to pool/main/libj/libjdom1-java/libjdom1-java_1.0-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ltris 1.0.11-1 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 10 Jan 2006 23:38:39 +0100
Source: ltris
Binary: ltris
Architecture: source i386
Version: 1.0.11-1
Distribution: unstable
Urgency: medium
Maintainer: Joan Queralt Molina [EMAIL PROTECTED]
Changed-By: Joan Queralt Molina [EMAIL PROTECTED]
Description:
ltris - very polished Tetris clone with CPU opponents
Closes: 347125
Changes:
ltris (1.0.11-1) unstable; urgency=medium
.
* New upstream release
* Removed build dependency on xlibs-dev. Closes: #347125
* debian/control:
+ Updated debhelper build-dependency to ( 5.0.0)
+ Use ${misc:Depends} on Depends.
* debian/compat:
+ New debhelper file.
+ Follow V5 compatibility level of devhelper.
* debian/rules:
+ Don't export DH_COMPAT because we use debian/compat now.
Files:
34e4543f053d3b48c2c9cbc6154d5cd0 598 games optional ltris_1.0.11-1.dsc
412ecd9b7577a5bbcb76e19b5397391c 808214 games optional ltris_1.0.11.orig.tar.gz
ad6ca2ec9e3cf561d8a32bc1d929f0ec 3455 games optional ltris_1.0.11-1.diff.gz
0832041c2adb7dc092a789a358c72323 498012 games optional ltris_1.0.11-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDy61T3+27IiW81b8RAlrCAKCYz7egu4b8Tm3yP+8ory/TpLnFZgCg3ql1
na+o12KHGsxg8RfE2uZ6x4E=
=UXFy
-END PGP SIGNATURE-
Accepted:
ltris_1.0.11-1.diff.gz
to pool/main/l/ltris/ltris_1.0.11-1.diff.gz
ltris_1.0.11-1.dsc
to pool/main/l/ltris/ltris_1.0.11-1.dsc
ltris_1.0.11-1_i386.deb
to pool/main/l/ltris/ltris_1.0.11-1_i386.deb
ltris_1.0.11.orig.tar.gz
to pool/main/l/ltris/ltris_1.0.11.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gifsicle 1.44-1.1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 12 Jan 2006 07:53:25 +0100 Source: gifsicle Binary: gifsicle Architecture: source i386 Version: 1.44-1.1 Distribution: unstable Urgency: low Maintainer: Gürkan Sengün [EMAIL PROTECTED] Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED] Description: gifsicle - Tool for manipulating GIF images Closes: 345503 346590 Changes: gifsicle (1.44-1.1) unstable; urgency=low . * Non-maintainer upload. * Fixed small typo in description (Closes: #345503). * Now build-depends on libx11-dev and x-dev, instead of xlibs-dev (Closes: #346590). * Also run autoconf, in order to really get it right. Files: 406dff378af2429cc5e3954a57e6d9e9 607 graphics optional gifsicle_1.44-1.1.dsc f769fb8ecd8d9bda438c5e4bf5493569 28031 graphics optional gifsicle_1.44-1.1.diff.gz 026ae2144a5079a7f016504e285e2f6a 132062 graphics optional gifsicle_1.44-1.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy7X0NFDtUT/MKpARAr3GAKD3ESr3zawHZ2CAYhBIvMJGqjWoiACgmzkR MvNuqpvIM8dK0x5nQvsPrTY= =qzi2 -END PGP SIGNATURE- Accepted: gifsicle_1.44-1.1.diff.gz to pool/main/g/gifsicle/gifsicle_1.44-1.1.diff.gz gifsicle_1.44-1.1.dsc to pool/main/g/gifsicle/gifsicle_1.44-1.1.dsc gifsicle_1.44-1.1_i386.deb to pool/main/g/gifsicle/gifsicle_1.44-1.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fbi 2.01-1.4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Jan 2006 23:55:00 +0100 Source: fbi Binary: fbi exiftran Architecture: source i386 Version: 2.01-1.4 Distribution: unstable Urgency: low Maintainer: Gerd Knorr [EMAIL PROTECTED] Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED] Description: exiftran - transform digital camera jpeg images fbi- Linux frame buffer image viewer Closes: 346726 Changes: fbi (2.01-1.4) unstable; urgency=low . * Non-maintainer upload. . [ Victor Seva ] * xlibs-dev transition. Closes: #346726 . [ Amaya Rodrigo Sastre ] * Bumped Standards-Version to 3.6.2. No changes needed. * Updated the Free Software Foundation old postal address in debian/copyright. * Switch from deprecated dh_installmanpages to dh_installman. Files: ffd540c3a82b4bbdebd3375ef77560dc 767 graphics optional fbi_2.01-1.4.dsc 1c9fda9488dfdbdfd4191380899901f3 4724 graphics optional fbi_2.01-1.4.diff.gz c4a577c92c072ec3b74bb0423efbab2b 53380 graphics optional fbi_2.01-1.4_i386.deb 956e127019fbcc9b84fd098139dba5fd 24002 graphics optional exiftran_2.01-1.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy7XwNFDtUT/MKpARApncAJ49u4axGa0xPqYB0BHHsg1I9tHjawCaAq6x PWcjVCj1g4kojXLYY3tx25s= =FUhV -END PGP SIGNATURE- Accepted: exiftran_2.01-1.4_i386.deb to pool/main/f/fbi/exiftran_2.01-1.4_i386.deb fbi_2.01-1.4.diff.gz to pool/main/f/fbi/fbi_2.01-1.4.diff.gz fbi_2.01-1.4.dsc to pool/main/f/fbi/fbi_2.01-1.4.dsc fbi_2.01-1.4_i386.deb to pool/main/f/fbi/fbi_2.01-1.4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libdockapp 1:0.5.0-1.2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 Jan 2006 22:39:35 +0100 Source: libdockapp Binary: libdockapp2 libdockapp-dev Architecture: source i386 Version: 1:0.5.0-1.2 Distribution: unstable Urgency: low Maintainer: Jeff Teunissen [EMAIL PROTECTED] Changed-By: Amaya Rodrigo Sastre [EMAIL PROTECTED] Description: libdockapp-dev - Window Maker Dock App support (development files) libdockapp2 - Window Maker Dock App support (shared library) Closes: 286642 347158 Changes: libdockapp (1:0.5.0-1.2) unstable; urgency=low . * Non-maintainer upload. . [ Victor Seva ] * xlibs-dev transition. Closes: #347158 . [ Amaya Rodrigo Sastre ] * Bumped Standards-Version to 3.6.2. No changes needed. * Updated DH_COMPAT from 1 to 4 in debian/rules * Fix typo in debian/rules (Closes: #286642). Files: c0c86ddc1d1999794ff3c4220140afd9 646 libs optional libdockapp_0.5.0-1.2.dsc 77f4a0ff1ef71a848a62f83b0cec88f9 291407 libs optional libdockapp_0.5.0-1.2.diff.gz cc67a40cd7110a8038ae8f7d99d1e172 16206 libs optional libdockapp2_0.5.0-1.2_i386.deb a5dae6edcbabe7ced77fc4b04d6287d1 29384 devel optional libdockapp-dev_0.5.0-1.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDy7X1NFDtUT/MKpARAuL2AKDz/og5G0AzYavQn+xk1ClABVfKIgCgqhZF E1Z5094wn4s9GXx3lJty9jk= =jPz9 -END PGP SIGNATURE- Accepted: libdockapp-dev_0.5.0-1.2_i386.deb to pool/main/libd/libdockapp/libdockapp-dev_0.5.0-1.2_i386.deb libdockapp2_0.5.0-1.2_i386.deb to pool/main/libd/libdockapp/libdockapp2_0.5.0-1.2_i386.deb libdockapp_0.5.0-1.2.diff.gz to pool/main/libd/libdockapp/libdockapp_0.5.0-1.2.diff.gz libdockapp_0.5.0-1.2.dsc to pool/main/libd/libdockapp/libdockapp_0.5.0-1.2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
