O: php-elisp -- Emacs support for php files
Package: wnpp Severity: normal Hi I hereby orphan the php-elisp package. I have not had enough time to maintain it well and think other people may be interested in it. A new upstream version fix a few things so that is likely the first thing to do for a new prosper developer. Best regards, // Ola -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Ideas for user-visible changes in Squeeze?
I created a page to collect ideas on new user-visible changes that could be rolled into Lenny. Infrastructure-related changes are fine, but the ideas collected on that page are about new things which Debian could bring to Squeeze which aren't coming from upstream. Examples from the past: - apt recommends/suggests - apt triggers - debconf - new installer What ideas do people have to make Squeeze kick ass? Please put your thoughts on the wiki: http://wiki.debian.org/UserVisibleChangesInSqueeze Who knows, some of these could even become release goals... Cheers, Francois -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thoughts on keeping a 3.0 (quilt) package in RCS
Hello Goswin, Goswin von Brederlow a écrit : I recently converted a few quilt using local packages to the new 3.0 (quilt) format. Additionaly those packages are kept in an RCS (mercurial here). Now the problem is: How to version control them? [...] You might be interested by [1]... [1] http://www.vcs-pkg.org/ Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s
On Tue,28.Apr.09, 03:09:52, Noah Slater wrote: Many of the more popular MUAs on your list have this command Can you name any others apart from mutt that come with this by default? Reply in Claws-Mail (and Sylpheed) does the right thing by default (Reply-to-List if it detects a list, Reply otherwise). Evolution and Gnus have already been mentioned and Kmail also has Reply-to-List AFAIR. For Icedove you have to install an extension. That just about covers the most popular clients in Debian. If you are interested in more details just search the archives of debian-user, this comes up every few months ;) Regards, Andrei P.S. I think your muttrc is seriously screwed up. Why do you set Mail-Followup-to to the *previous* poster? I almost CCd Ben Finney! -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Ideas for user-visible changes in Squeeze?
On Tue, 2009-04-28 at 18:08 +1200, Francois Marier wrote: I created a page to collect ideas on new user-visible changes that could be rolled into Squeeze. Please put your thoughts on the wiki: http://wiki.debian.org/UserVisibleChangesInSqueeze Who knows, some of these could even become release goals... Is there any reason not to put those entry into the page http://wiki.debian.org/SqueezeReleaseGoals ? Regards, Franklin -- Stop Software Patents - http://ffii.org/ Sign the petition at http://stopsoftwarepatents.eu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Should we still purge GConf schemas from the old directory?
On Mon, 2009-04-27 at 22:47 -0700, Steve Langasek wrote: It would be nice if packages that provided these files at one time would take responsibility for cleaning them up now, late that it is. I'm not sure this could sensibly be done as a debconf snippet though. Its not clear that all these packages still exist though :) -Rob signature.asc Description: This is a digitally signed message part
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tuesday 28 April 2009 05:11:26 Russ Allbery wrote: Noah Slater nsla...@tumbolia.org writes: As far as I see it: * Debian has dropped the Reply-To header because it is harmful in some way. * Debian has mandated that all replies must behave as if Reply-To existed. If this were the case, this would be an easy solution. However, it's not. Debian has mandated that all *public* replies must behave as if Reply-To existed, but all *private* replies behave as if it did not, and repliers must distinguish between the two. One very practical problem I personally have with all of this is that on certain/some/many other mailing lists it is expected that you reply to the poster *and* the mailing list, to be sure that the poster gets your reply in case he is not subscribed (and also, because some people can then find replies to their personal problems more easily among the load of other messages). And with the multitudes of communities I deal with, I do not have the time or concentration or infallibility to scan the emails for please cc me or please don't cc me notes or even reverse-engineer the mailing list's posting or subscription policy to make sure the message gets to who needs to read it. Considering that most mailing list software has an elimnatecc feature, this is never really a problem for people who don't want that sort of behavior. Another problem on the flip side is that many people don't observe the please cc me requests on Debian mailing lists, and that way communication gets annoying. So in practical terms, it is safer to add more recipients to the message to make sure it is received and noticed, and let computer software do the filtering if necessary. That is just my practical experience in trying to communicate with people. The policy is what it is, but I don't like it, because it *hinders* rather than *helps* me communicate effectively. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debconf templates: Choices displayed different to values
Quoting Lucas Brasilino (lucas.brasil...@gmail.com): Thanks a lot for you answer. By the way, can you please point me out some updated documentation about templates, debconf protocol, commands, etc? If you introduce debconf templates, you may want to get them reviewed by the debian-l10n-engl...@lists.debian.org mailing list *before* introducing them. If you really need the templates and can't wait for a review, then introduce them as non translatable first (not prepending with _, the Choices:, Description:, etc, fields)and turn them to translatable once they're reviewed. My primary reference is [1] which is surely helpful... but quite old man debconf-devel man po-debconf These may bring useful information to you.and so does old documentation as the debconf protocol didn't change that much over years. signature.asc Description: Digital signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
OoO En cette fin de nuit blanche du mardi 28 avril 2009, vers 05:27, Brian May b...@snoopy.debian.net disait : I tried hard, for many years, to love the Mail-Followup-To field, but I must agree that it doesn't serve the purpose well enough to recommend. (Briefly: it breaks when a discussion crosses between different mailing lists, and other common use cases.) I don't think that is a problem with the field, but the MUA programs. Mutt, for example, AFAIK will list all mailing lists in the autogenerated Mail-Folloup-To, without allowing the user to change this (unless the user overrides the entire field) or pick only one mailing list. How Mutt is able to detect all mailing lists? The fields in the headers only allow to detect the current mailing list. -- BOFH excuse #419: Repeated reboots of the system failed to solve problem pgpZ6i9Utic39.pgp Description: PGP signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
William Pitcock neno...@sacredspiral.co.uk writes: On Mon, 2009-04-27 at 14:05 +0200, Holger Levsen wrote: As it sadly happens many times every day. And as long as there are no means to enforce it (either pure social or aided by technology), it will continue to happen. Reply-To: debian-devel@lists.debian.org ? Weird. It's almost like you haven't read any of the reasons why that's a terrible idea, as already given in this thread (and countless times in the past). -- \ “Of all classes the rich are the most noticed and the least | `\ studied.” —John Kenneth Galbraith, _The Age of Uncertainty_, | _o__) 1977 | Ben Finney pgp1138Sblf4m.pgp Description: PGP signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
+ Mike Hommey (Tue, 28 Apr 2009 07:46:35 +0200): On Tue, Apr 28, 2009 at 11:53:12AM +1000, Ben Finney wrote: Noah Slater nsla...@tumbolia.org writes: Yes, I know the L command, but thanks for pointing it out! My argument is that I have to remember to use when I am replying to the Debian lists, which as you can see, doesn't happen very often. No, the point of a ‘reply to list’ command is you *don't* have to remember when to use it. Just use it every time you reply to any list, and it will DTRT because it uses the standard fields which are in just about every mailing list anywhere. The times when it doesn't will be the rare ones. There are notorious counter examples, such as the git mailing list, that *do* require people to Cc the people they reply to, while the mailing list software doesn't add Reply-To. Oh, and actually they get very annoyed if you send your mail with a Mail-Followup-To header that prevents their group-reply function from adding you to the recipient list. -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: About symbol versioning, soname bumps and symbols files.
+ Steve Langasek (Mon, 27 Apr 2009 22:13:57 -0700): On Sun, Apr 26, 2009 at 06:43:00PM +0200, Adeodato Simó wrote: I’m unsure why assigning VERS_1 to all symbols works for preserving compatibility, whereas old binaries use symbols not associated with any version node (i.e., @Base). Maybe the first defined version node gets to “answer” to all requests that come without a version node attached. :-) It’d be nice if somebody could explain. But, if that’s true, I don’t know why there have to exist both a @Base and @VERS_1 versions of sctp_connectx. I’ll also note that the @VERS_1 has a different prototype than the aliased function! Because the earlier library used unversioned symbols, any programs depending on this lib will have references to an unversioned sctp_connectx symbol, which will be resolved to an arbitrary symbol whose name matches. The explicit Base symbol, as provided by: __asm__(.symver __sctp_connectx, sctp_connectx@); ... is needed so that objects linked against the pre-versioned lib resolve deterministically. Yes, I understand that, and was what I thought initially. But then, I didn't understand why all other symbols were migrated to have one only version... in VERS_1. But my question quoted above what will make apps refering to unversioned symbols pick up the symbols from VERS_1 automatically still stands, though. :-) Oh, or maybe you answered already: an unversioned reference resolves to an arbitrary version, unless there's a version binded to @Base? Does this mean that, if another symbol was to be updated (into VERS_2, eg., or VERS_3), the same `.symver foo, f...@` would have to be used? What's the point of having every symbol on VERS_1, then, and why weren't they kept on @Base directly, adding only sctp_connectx to VERS_1? However, if the prototype for __sctp_connectx() doesn't match the prototype for sctp_connectx_orig(), then... I'm pretty sure that's a bug in the lib. Okay, we can send mail to the patch author later. 3.) Should I just update the symbols file as shown above and not worry? Well, at least this entry: sctp_conne...@base 1.0.10+dfsg is wrong, because that symbol was already present before, so (barring ABI bugs as mentioned above) the minimum version req for it shouldn't be bumped. But if every other symbol suddenly has a VERS_1 symbol version, then anything linking against those will be unhappy when run against the pre-versioned lib anyway (throwing warnings but not errors), so that's a minor point. Right. When reading the symbols file propsed by Michael, I thought something in the lines of ok, every symbol bumped because the new library is backwards but not forwards compatible, so it's kind of a shlibs bump. The sctp_conne...@base version just got lost in the noise of having every other symbol bumped, and it's (while incorrect) very minor indeed. (On other news, libsctp1 has exactly one reverse dependency, which comes from the same source package.) Thanks, Steve! -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Should we still purge GConf schemas from the old directory?
Le mardi 28 avril 2009 à 01:25 +0300, Marius Vollmer a écrit : If all files in /etc/gconf/schemas are totally useless (i.e., nobody reads them), why not put a big cleanup hack in, say, gconf itself that just removes that directory entirely. (In addition to removing the snipped from dh_gconf.) Because it would potentially remove files that were installed by hand. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Re: Consistent formating long descriptions as input data
On Mon, Apr 27, 2009 at 04:53:11PM -0400, James Vega wrote:
Please have a look at garlic-doc. It does not look right.
It's using `o' as the bullet character which is not supported by
Markdown/rST. This has already been identified as a case that will need
to be fixed by the individual packages (or pre-processed into some other
character).
Full ACK.
FWIW, note that with the fix induced by the first of Bill reports, I
consider garlic-doc looking right. As it is not a Markdown list, it is
rendered as ordinary verbatim text.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: Should we still purge GConf schemas from the old directory?
Le lundi 27 avril 2009 à 22:47 -0700, Steve Langasek a écrit : Removing that snippet would be fair; but I don't think this transition has actually been managed very well, since on a system that's been upgraded continuously since woody I now see that /etc/gconf/schemas/ is full of orphaned .schemas. These should have been handled in the preinst of the relevant packages when the conffiles were first dropped, to automatically remove any unmodified conffiles. This would have meant introducing ~200 preinsts by hand, since it was not possible to generate them automatically. It would be nice if packages that provided these files at one time would take responsibility for cleaning them up now, late that it is. I'm not sure this could sensibly be done as a debconf snippet though. I don’t think this could be done reliably either. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Re: ignoring the CoC in regards to cc:s
Le mardi 28 avril 2009 à 02:56 +0100, Noah Slater a écrit : It's all very well having a feature like this, but if that feature is easy to forget because Debian's lists are the only ones that want me use it, it's hardly of any real value. Add a Reply-To and this problem goes away. Reply-to-list works with most of the major mailing list software. I’m not subscribed to any list which set the Reply-To header. Could you at least show some examples of such lists in the free software world? -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Re: ignoring the CoC in regards to cc:s
Le mardi 28 avril 2009 à 10:11 +1000, Brian May a écrit : On Mon, Apr 27, 2009 at 04:16:08PM +0200, Josselin Mouette wrote: C. Only supported by a handful of clients A number of clients won't automatically generate the header, but may still support it for group replies. I think this might include Evolution and Thunderbid (although it was a while since I tested this so I might be wrong) when doing a group reply. Evolution safely ignores any Mail-Followup-To junk, and AFAIK only cares about mailing-list headers defined in RFC 2369 and 2919. -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling signature.asc Description: Ceci est une partie de message numériquement signée
Re: ignoring the CoC in regards to cc:s
On Tue, 28 Apr 2009, Noah Slater wrote: If this is such a concern, I would like to see the Code of Conduct updates to recommend that people concerned with follow up emails set the appropriate headers in their own clients. This was detailed earlier in this thread. If people want followups, they can explicitely ask for them, whether by setting MFT, or by just asking. This is precisely what the CoC says: * When replying to messages on the mailing list, do not send a carbon copy (CC) to the original poster unless they explicitly request to be copied. Regardless, the start of this sub-thread was in violation of the CoC itself. If you need to complain to someone about Cc:'ing you, complain directly to them, not to the list. * If you want to complain to someone who sent you a carbon copy when you did not ask for it, do it privately. Finally, if anyone has issues with how the lists are administrated or the CoC, mail listmas...@lists.debian.org; it doesn't really need to be discussed on -devel. [I won't comment further on -devel; mail listmaster@ if you actually have suggestions or problems.] Don Armstrong -- We were at a chinese restaurant. He was yelling at the waitress because there was a typo in his fortune cookie. -- hugh http://www.gapingvoid.com/Moveable_Type/archives/000321.html http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff? (was: Re: phyml_20081203-1_powerpc.changes REJECTED)
On 27 Apr 18:55, Noah Slater wrote: On Mon, Apr 27, 2009 at 07:48:50PM +0200, Adeodato Simó wrote: I fully agree with this. I think having to remember which key one must use in each context for reply is lame. This is why I do in my ~/.muttrc: [...] Where l/debian is the folder which contains Debian lists, and it allows to always use 'r' to reply to mail. Hmm, interesting! Unfortunately, I don't use folders so I don't think this will work for me. *boggle* - you claim to be on multiple lists and yet you don't use server side filtering and folders?! OK - now that's just plain odd. -- Brett Parker -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On 28 Apr 03:58, Jean-Christophe Dubacq wrote: Ben Finney a écrit : Noah Slater nsla...@tumbolia.org writes: Yes, I know the L command, but thanks for pointing it out! My argument is that I have to remember to use when I am replying to the Debian lists, which as you can see, doesn't happen very often. No, the point of a ‘reply to list’ command is you *don't* have to remember when to use it. Just use it every time you reply to any list, and it will DTRT because it uses the standard fields which are in just about every mailing list anywhere. The times when it doesn't will be the rare ones. Why do these functions not do a normal Reply when not applied to a mail contained within a list? What do they do then? If they also do the right thing for a non-list mail, why are not they bound by default to be the main Reply button? That is a real question, btw, no irony implied. Because you don't always want to reply to the list. I rather like that Reply means reply to the person that wrote the e-mail rather than reply to the list, the list wants to know, really. -- Brett Parker -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff? (was: Re: phyml_20081203-1_powerpc.changes REJECTED)
On Tue, Apr 28, 2009 at 10:46:01AM +0100, Brett Parker wrote: *boggle* - you claim to be on multiple lists and yet you don't use server side filtering and folders?! OK - now that's just plain odd. Neither do I, does that make me odd too? By all means comment on how I or anyone elses uses lists, but you have no right to tell me how I should organise my own mailbox. -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Brett Parker idu...@sommitrealweird.co.uk writes: On 27 Apr 18:55, Noah Slater wrote: Unfortunately, I don't use folders so I don't think this will work for me. *boggle* - you claim to be on multiple lists and yet you don't use server side filtering and folders?! OK - now that's just plain odd. Folders aren't the only way to manage lots of messages sanely; ask any Google Mail user. Since I wouldn't dream of recommending anyone use a proprietary data silo like Google Mail, I invite you instead to look at the ‘sup’ package for a folder-less approach to organising email messages that many say is superior. -- \ “What I have to do is see, at any rate, that I do not lend | `\ myself to the wrong which I condemn.” —Henry Thoreau, _Civil | _o__)Disobedience_ | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s
2009/4/28 Josselin Mouette j...@debian.org:
I’m not subscribed to any list which set the Reply-To header. Could you
at least show some examples of such lists in the free software world?
Just a few (all of them form Argentina):
miembros-at-usla.org.ar; anillo-lst-at-linux.org.ar,
lug-org-at-lugmen.org.ar, *-at-{linux,usla,lugmen}.org.ar?
There are plenty of others in the Libre Software Comunity of
Argentina. They may be very popular in other coutries as well, but
that's what I can assert.
Cheers,
L
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On 27 Apr 18:49, Noah Slater wrote: So, user error, not software error... This illustrates my point perfectly! It's not user error, because I'm just doing what I've learnt to do. Erm - how's that not user error? What you've learnt is obviously wrong. Relearn how to use your MUA efficiently. When software use becomes habitual, usability is increased. This is how usability is defined, instead of some abstract sense. Software that behaves according to a user's mental model is easy to use. Forcing people to adjust their behaviour is a poor substitute for a technical solution. Software should adapt to human behaviour, not the other way around. So, change your software configuration. The list software is doing the correct thing, the user agent is obviously your failing point here - so, either use a different MUA or configure your current MUA to do what you expect it to. BTW, MUAs are software too! *sigh*. -- Brett Parker -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s
On 090428 10:18, Josselin Mouette wrote: Reply-to-list works with most of the major mailing list software. I’m not subscribed to any list which set the Reply-To header. Could you at least show some examples of such lists in the free software world? Skåne Sjælland Linux User Group (SSLUG) and Ubuntu, of which I am subscribed sets the reply-to. -- Olof Johansson PGP: 0x7FC0FBBA http://www.ethup.se signature.asc Description: Digital signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 09:56:59AM +0300, Peter Eisentraut wrote: Another problem on the flip side is that many people don't observe the please cc me requests on Debian mailing lists, and that way communication gets annoying. So in practical terms, it is safer to add more recipients to the message to make sure it is received and noticed, and let computer software do the filtering if necessary. That is just my practical experience in trying to communicate with people. The policy is what it is, but I don't like it, because it *hinders* rather than *helps* me communicate effectively. +1 On Tue, Apr 28, 2009 at 02:00:05AM -0700, Don Armstrong wrote: Regardless, the start of this sub-thread was in violation of the CoC itself. If you need to complain to someone about Cc:'ing you, complain directly to them, not to the list. * If you want to complain to someone who sent you a carbon copy when you did not ask for it, do it privately. Yes, and this happens to me about once a month. Every time, I feel like an idiot for having forgot to observe the Code of Conduct. Like Peter Eisentraut points out, the current technical configuration and policy hinder my ability to communicate with others. Finally, if anyone has issues with how the lists are administrated or the CoC, mail listmas...@lists.debian.org; it doesn't really need to be discussed on -devel. [I won't comment further on -devel; mail listmaster@ if you actually have suggestions or problems.] I actually think some value has come out of this thread. Where I previously thought I was in the minority for being annoyed by the current technical configuration and policy, I have found there seems to be an even split of opinions both ways. Consensus building is valuable. On Tue, Apr 28, 2009 at 11:04:50AM +0200, Giacomo A. Catenazzi wrote: Anyway, the first rule of internet: be conservative in what you do, be liberal in what you accept from others, so people should accept wrong CC:s without crying, and people should follow the CoC when sending mails. I agree, but I wouldn't word it like this. If Debian wants to omit the Reply-To header then I think it must accept that people are going to, purposefully or otherwise, use the Reply To All feature of their MUAs. I don't actually have a preference about using the Reply-To header, because it doesn't affect how I interact with my MUA. What I object to is removing the Reply-To header and then complaining about the consequences of that action. On Tue, Apr 28, 2009 at 10:56:02AM +0100, Brett Parker wrote: On 27 Apr 18:49, Noah Slater wrote: It's not user error, because I'm just doing what I've learnt to do. Erm - how's that not user error? What you've learnt is obviously wrong. Relearn how to use your MUA efficiently. [...] So, change your software configuration. The list software is doing the correct thing, the user agent is obviously your failing point here - so, either use a different MUA or configure your current MUA to do what you expect it to. I think you're missing my entire point. Even if I do manage to figure out how to configure mutt to Reply To List for mailing list posts automatically, that's just one subscriber. The problem hasn't been solved. You still have to upgrade every single other subscriber's MUA in a similar fashion. It's a totally unrealistic goal, and so encoding it into the Code of Conduct seems wrong. On Tue, Apr 28, 2009 at 10:46:01AM +0100, Brett Parker wrote: *boggle* - you claim to be on multiple lists and yet you don't use server side filtering and folders?! OK - now that's just plain odd. Like Ben Finney hinted at, I used to be a Google Mail user. I brought across a lot of things I learnt from using that interface. In case you're curious, I have a procmail system that filters all mailing list traffic into a temporary mailbox. I have a mutt macro that redelivers from that mailbox in batch when I am ready to process my mailing list traffic. It works well for me. On Tue, Apr 28, 2009 at 10:18:35AM +0200, Josselin Mouette wrote: Reply-to-list works with most of the major mailing list software. It still requires me to THINK about which key to press, which has already proven quite difficult. Even if I do train my fingers to hit the right key, which may take some time, there will always be others who have not. This will continue being a problem for the Debian lists until something changes. On Tue, Apr 28, 2009 at 09:31:38AM +0300, Andrei Popescu wrote: That just about covers the most popular clients in Debian. If you are interested in more details just search the archives of debian-user, this comes up every few months ;) That this comes up so frequently should indicate something is wrong. I’m not subscribed to any list which set the Reply-To header. Could you at least show some examples of such lists in the free software world? I don't keep more than one weeks email on my server, but here is what I found: Reply-To: ascii...@googlegroups.com
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 11:04:50AM +0200, Giacomo A. Catenazzi wrote: Anyway, the first rule of internet: be conservative in what you do, be liberal in what you accept from others, so people should accept wrong CC:s without crying, and people should follow the CoC when sending mails. The main problem for people like me who subscribe to a lot of lists is that different groups have different requirements. Debian doesn't like CCs, others require them, others are indifferent. It's not easy to always do the correct thing--I don't want to remember all the list-specific requirements, just send a reply. We should really be using usenet rather than mailing lists... It solves all of the problems and is vastly superior. It's totally geared to group discussion, handles crossposting to related groups, and also allows mailing replies rather than public posting. Some groups (e.g. CUPS) handle this by having a public news server with an (optional) mail gateway for backward people who prefer mail. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s
Josselin Mouette j...@debian.org writes: I’m not subscribed to any list which set the Reply-To header. Could you at least show some examples of such lists in the free software world? What's the free software world? Is that a separate networking domain, or is it connected to the Internet? Anyway, here are a few examples of mailing lists which set the Reply-To header: FreeRADIUS Users' List: http://freeradius.org/list/users.html Linux-Thinkpad List: http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad Load Balancing List: http://vegan.net/mailman/listinfo/lb-l Bjørn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, 28 Apr 2009, Charles Plessy wrote: Also, can you tell us where to write comments related to NEW uploads in plain English, so that it can be documented in the Developers Reference? That's actually a really good question which I would like to formulate even more clear: How to address the fact that a rejection issue is solved now? I'd love to see a short paragraph about this in Developers Reference. I think that debian/copyright it not the best place for this, and apparently README.source is not. How about README.NEW? Or can we just drop an email to ftpmas...@d.o at the time of the upload? I have decided to use a Reply to the rejection mail after a new upload but I wonder whether this is the best way which makes the less work for ftpmaster. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s
Le mardi 28 avril 2009 à 14:12 +0200, Bjørn Mork a écrit : What's the free software world? Is that a separate networking domain, or is it connected to the Internet? CALL THE METAPHOR POLICE! -- .''`. Josselin Mouette : :' : `. `' “I recommend you to learn English in hope that you in `- future understand things” -- Jörg Schilling -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Steve Langasek wrote: On Mon, Apr 27, 2009 at 04:16:08PM +0200, Josselin Mouette wrote: Le lundi 27 avril 2009 à 14:44 +0200, Michael Tautschnig a écrit : If you're annoyed by cc:s (well, Holger, I know you are, you told me about that more than once :-) ), configure your mailclient to set Mail-Followup-To and hope for the next poster's mailclient to support that header. Which actually means that, to a certain degree, those annoyed by cc:s could themselves do something about it. Mail-Followup-To is: A. Useless junk without clear semantics B. Violating standards C. Only supported by a handful of clients D. Obi-wan Kenobi says: “All of the above” http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt Perfectly well defined. It wasa draft and the fourth line: Expires: May 1998 November 1997 I don't think it is perfectly defined. Anyway, the first rule of internet: be conservative in what you do, be liberal in what you accept from others, so people should accept wrong CC:s without crying, and people should follow the CoC when sending mails. ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 08:56:57PM +0900, Charles Plessy wrote:
Also, can you tell us where to write comments related to NEW uploads
in plain English, so that it can be documented in the Developers
Reference? I think that debian/copyright it not the best place for
this, and apparently README.source is not. How about README.NEW? Or
can we just drop an email to ftpmas...@d.o at the time of the
upload?
Given that, in response to your upload, you will get an email
precisely mentioning the NEW status of your package, the most
natural place to provide such comments is by replying to that email.
IIRC, that email also explicitly invites you to reply for further info
(but I might be confusing it with REJECTs: if this is the case,
experience tells us that patches to dak that improve those mail
templates are usually welcome).
I don't see any need to pollute a source package with another
README.something that will become garbage just after NEW processing is
over.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: Can we ship sources of a PDF file in the Debian diff?
Le Mon, Apr 27, 2009 at 08:32:28PM +0200, Joerg Jaspert a écrit : If you ask me things are quite clear: From a Debian point of view the source includes *.orig.tar.gz, *.dsc and *.diff. The files are connected via md5sum in *.dsc. So shipping the source of a PDF in the diff should be acceptable from a Debian point of view (even if it would be nice to have it i nthe upstream source). It makes sense to document this in README.Source (as you did) AND debian/copyright (I don't know whether you did). It is ok, its just 3 million times easier for the ftpmaster at work to miss this in the .diff. Which is what happened. Hi Joerg, In my profession we often say “The person who does not make mistakes usually does not do any work at all.”, so it is fine with me. Can I re-upload a version for main that you would fast-track to resolve the issue? Also, can you tell us where to write comments related to NEW uploads in plain English, so that it can be documented in the Developers Reference? I think that debian/copyright it not the best place for this, and apparently README.source is not. How about README.NEW? Or can we just drop an email to ftpmas...@d.o at the time of the upload? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can we ship sources of a PDF file in the Debian diff? (was: Re: phyml_20081203-1_powerpc.changes REJECTED)
Le Mon, Apr 27, 2009 at 07:36:27PM -0700, Steve Langasek a écrit : On Sun, Apr 26, 2009 at 08:41:14PM +0900, Charles Plessy wrote: Le Sat, Apr 25, 2009 at 01:42:04PM +, Joerg Jaspert a écrit : Hi Maintainer, rejected, i think we are missing the source for the pdf in doc/. Almost two monthes of waiting to read this… What was the license on the PDF in question, and was the license documented in debian/copyright? Hi Steve (and Cyril), the package was rejected because of missing source, not for license issues. Nevertheless, if you are curious about what debian/copyright contained, here is the relevant extract: Files: doc/phyml_manual.pdf, debian/phyml_manual.tar.gz.uu Copyright: © Copyright 1999 - 2008 by PhyML Development Team License: formerly free for academic only, but relicenced on the upstream website. The software PhyML is provided “as is” without warranty of any kind. In no event shall the authors or his employer be held responsible for any damage resulting from the use of this software, including but not limited to the frustration that you may experience in using the package. The program package and this documentation, are distributed free of charge for academic use only. Permission is granted to copy and use programs in the package provided no fee is charged for it and provided that this copyright notice is not removed. X-Comment: After discussion with the upstream maintainer, the documentation was relicenced and an updated version was published on the upstream web site with the following the new disclaimer: . The software PhyML is provided “as is” without warranty of any kind. In no event shall the authors or his employer be held responsible for any damage resulting from the use of this software, including but not limited to the frustration that you may experience in using the package. . This relicencing also affects the version shipped in this package, and the documentation will be updated with the next upstream release of PhyML. Since there is no licence but only a disclaimer, I conclude that the PDF file is licenced under the same terms of the rest of phyml, namely the GNU GPL. If, in a package that has a general license statement, there are files for which an explicit reminder of the statement is strictly required to prove their freedom, then I would like to see it documented somewhere. Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Roger Leigh wrote: On Tue, Apr 28, 2009 at 11:04:50AM +0200, Giacomo A. Catenazzi wrote: Anyway, the first rule of internet: be conservative in what you do, be liberal in what you accept from others, so people should accept wrong CC:s without crying, and people should follow the CoC when sending mails. The main problem for people like me who subscribe to a lot of lists is that different groups have different requirements. Debian doesn't like CCs, others require them, others are indifferent. It's not easy to always do the correct thing--I don't want to remember all the list-specific requirements, just send a reply. Yes, this is the liberal in what you accept from others part, so allowing errors without boring people with scaring message. Unfortunately I don't think we can change the CoC, so we MUST better handle errors. I also prefer adding cc:s, and I really annoyed to some scary (and sometime wrong) messagges I get when do wrong replies. I don't understand why people lose time trying to point error to others, instead of just ignoring errors (someone as a script to point errors, instead of a simple user side discard of email). A lot of time we lose discussion; e.g. in debian-legal: a lot of DDs are not subscribed, so they see only half of discussion, especially when there are new post after some week of pause (e.g. after a private discussion to upstream). But I don't think it is feasible to change the CoC. We should really be using usenet rather than mailing lists... It solves all of the problems and is vastly superior. It's totally geared to group discussion, handles crossposting to related groups, and also allows mailing replies rather than public posting. Some groups (e.g. CUPS) handle this by having a public news server with an (optional) mail gateway for backward people who prefer mail. personally I've more difficulty on handling usenet post on different computer: synchronize read post at home, office and offline laptop. ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525986: RFP: FoFiX -- game of musical skill and fast fingers
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org Package name: fofix Version: 3.100 Upstream Author: Pascal Giard evily...@gmail.com URL: http://code.google.com/p/fofix/ License: GPL2 Description: game of musical skill and fast fingers Frets on Fire X is a game of musical skill and fast fingers. The aim of the game is to play guitar with the keyboard as accurately as possible. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
I demand that Ben Finney may or may not have written... [snip; M-F-T] RFC2822 (which define the semantics of ‘From’ and ‘Reply-To’) and RFC2369 (which defines the semantics of ‘List-Post’) are IETF-recommended standards; the other never achieved that. Given that it's seen some use and been found to provide some worthwhile benefit, that draft would seem to need to be revisited. Oh, and RFC5322 obsoletes RFC2822. :-) -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING. Schedules are optimistic. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525999: ITP: php-html-treemenu -- Provides a PHP API to create an HTML tree
Package: wnpp Owner: Mark A. Hershberger m...@everybody.org Severity: wishlist * Package name: php-html-treemenu Version : 1.2.1 Upstream Author : Chuck Burgess, Ken Guest, Richard Heyes * URL or Web page : http://pear.php.net/package/HTML_TreeMenu/ * License : BSD Description : Provides a PHP API to create an HTML tree -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Comparing MarkDown and reST (Was: Consistent formating long descriptions as input data)
On Thu, 23 Apr 2009, Daniel Burrows wrote: I'm happy to support whatever markup language people want to use. Same for me. To feed some facts to be able to compare the options I rendered the debug blends pages with reST using the very same code for the preprocessing which does 1. s/^ // 2. s/^\.$// 3. s/^(\s*)[.o]\s+/\1* / This enables rendering lists using 'o' and '.' as bullets 4. s/*([fh]t?tp:\/\/[-./\w?=~;]+)*/[\1](\1)/ This is to mark URLs in Markdown - Syntax which definitely confuses reST - I should drop this for a fair comparison - so please ignore this 5. s/^#/\\#/ A '#' in the first column has some specific meaning in Markdown and has to be escaped (which seems to work fin in reST[1]) 6. Include empty line before lists and verbatim lines 7. Insert '\t' in the beginning of verbatim lines - this seems to confuse reST definitely (I have not yet looked into the reST docs because I'm just lacking time) which can basically be seen in the remarks which are intended to be verbatim but the reST pages just render lists etc as well I used for markdown from markdown import markdown markdown(preprocessed_string) and for reST from docutils.core import publish_parts publish_parts(preprocessed_string, writer_name='html')['body'] Conclusion: Markdown renders a lot of descriptions correctly but has several missinterpretations of multilevel lists which are partly invented by Markdown and partly not detected and turned to single level lists. I have not yet dived into the docs of the Python library but at first sight there are no obvious warnings / errors about potential problems. reST also renders sevral lists quite fine. The comparison is partly unfair because the preprocessing was keeping Markdown in mind but reST probably need other tunings. I have no time to verify this - hints are welcome. What I really like in reST is the fact that you get allways messages like ... string:10: (WARNING/2) Block quote ends without a blank line; unexpected unindent. string:11: (WARNING/2) Enumerated list ends without a blank line; unexpected unindent. string:15: (WARNING/2) Block quote ends without a blank line; unexpected unindent. string:12: (ERROR/3) Unexpected indentation. string:13: (WARNING/2) Block quote ends without a blank line; unexpected unindent. string:17: (WARNING/2) Bullet list ends without a blank line; unexpected unindent. string:18: (WARNING/2) Block quote ends without a blank line; unexpected unindent. string:13: (WARNING/2) Bullet list ends without a blank line; unexpected unindent. string:5: (SEVERE/4) Unexpected section title or transition. ... and so you have an easy interface to check descriptions with lintian or by other means. Here you can view the results: Markdown: http://blends.debian.net/debug/tasks/ reST: http://blends.debian.net/rest-test/tasks/ Hope this helps to compare the two options which were discussed here Andreas. [1] http://blends.debian.net/rest-test/tasks/works#geordi -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#525986: RFP: FoFiX -- game of musical skill and fast fingers
On Tue, Apr 28, 2009 at 02:24:48PM +0200, Resul Cetin wrote: Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org Package name: fofix Version: 3.100 Upstream Author: Pascal Giard evily...@gmail.com URL: http://code.google.com/p/fofix/ License: GPL2 Description: game of musical skill and fast fingers Frets on Fire X is a game of musical skill and fast fingers. The aim of the game is to play guitar with the keyboard as accurately as possible. What's the difference to Frets on Fire? Michael -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Peter Eisentraut pet...@debian.org writes: Considering that most mailing list software has an elimnatecc feature, this is never really a problem for people who don't want that sort of behavior. This feature is hideously broken for people (like myself) who split list mail into separate folders, since it suppresses exactly the copy that can be reasonably filed and leaves only the one that goes into one's personal inbox. I personally don't mind cc's or not cc's, but that suppress cc feature is just horrible. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 08:25:29AM -0700, Russ Allbery r...@debian.org wrote: Peter Eisentraut pet...@debian.org writes: Considering that most mailing list software has an elimnatecc feature, this is never really a problem for people who don't want that sort of behavior. This feature is hideously broken for people (like myself) who split list mail into separate folders, since it suppresses exactly the copy that can be reasonably filed and leaves only the one that goes into one's personal inbox. I personally don't mind cc's or not cc's, but that suppress cc feature is just horrible. OTOH, people annoyed with Cc's can setup filters on message-ids. Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#525999: ITP: php-html-treemenu -- Provides a PHP API to create an HTML tree
On Tue, Apr 28, 2009 at 10:06:28AM -0400, Mark A. Hershberger wrote: Description : Provides a PHP API to create an HTML tree Should be in 'is-a(n)' form, and is there no long description? -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On 2009-04-28, Mike Hommey m...@glandium.org wrote: On Tue, Apr 28, 2009 at 08:25:29AM -0700, Russ Allbery r...@debian.org wrote: Peter Eisentraut pet...@debian.org writes: Considering that most mailing list software has an elimnatecc feature, this is never really a problem for people who don't want that sort of behavior. This feature is hideously broken for people (like myself) who split list mail into separate folders, since it suppresses exactly the copy that can be reasonably filed and leaves only the one that goes into one's personal inbox. I personally don't mind cc's or not cc's, but that suppress cc feature is just horrible. OTOH, people annoyed with Cc's can setup filters on message-ids. And then you mostly need to prefer the mail that comes last because it has the proper list headers. I have yet to see such a solution. (I.e. those filters work just fine but eliminate later mails and direct Cc:s are usually faster, unless greylisting is employed.) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Comparing MarkDown and reST (Was: Consistent formating long descriptions as input data)
On Tue, Apr 28, 2009 at 04:51:56PM +0200, Andreas Tille wrote: On Thu, 23 Apr 2009, Daniel Burrows wrote: I'm happy to support whatever markup language people want to use. ... I used for markdown ... and for reST FYI: As I checked popularity of similar plain text formatters via popcon, http://people.debian.org/~osamu/pub/getwiki/html/ch12.en.html#listoftoolstohigghtplaintextdata asciidoc 0.8% installed markdown 0.4% installed rest2web 0.1% installed The packaged version of asciidoc is not yet support multilevel buletting beyond 2 levels. But upstream one does it now. As long as these converter are trimmed in the customized configuration, I think any one of them are fine (at least for English). Osamu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Thoughts on keeping a 3.0 (quilt) package in RCS
Goswin von Brederlow dijo [Tue, Apr 28, 2009 at 12:48:58AM +0200]:
Hi,
I recently converted a few quilt using local packages to the new 3.0
(quilt) format. Additionaly those packages are kept in an RCS
(mercurial here). Now the problem is: How to version control them?
The new format allows one to just edit the source and build it. No
creation of patches neccessary as dpkg-source creates them for you.
Obviously it is a good idea to give patches a descriptive name instead
of debian-changes-version but that is easy enough to do after a test
build. The ease of creating new patches is just so much fun.
But how/what do I add and commit to the RCS?
1) everything
(...)
2) only unpatched sources + debian
(...)
Currently I think the second option is more sane. What are your
thoughts?
I believe having each patch as a separate, trackable and
self-described entity is better. I maintain several packages, both on
my own and as part of a team work. Whenever there are modifications to
be made to the upstream sources, I prefer storing them as quilt
patches - Not as changesets (or feature branches or anything like
that) on my VCS. I value having them as understandable units in my
source package, in case I go missing or somebody wants to understand
it by only checking there. Yes, I know I could describe the package
should be cloned from a given repository in my README.source, but I do
feel it is much clearer if the source package has the complete
information, and the VCS-based packaging has only the packaging
evolution over time.
${vcs}-buildpackage scripts keep your base directory clean, so I don't
see it as a huge administrative penalty to keep my patches in
debian/patches. Yes, I have to apply them in order to work on one of
them, but debian/rules clean takes care of leaving everything ready
for a clean build.
--
Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Misc developer news (#15)
Raphael Hertzog schrieb: RFH: Removing spam from the listarchive --- As you all know, Lists and the Listarchive aren't 100% Spam-free. So we provide a 'Report as Spam' on every page in the archive. Now we set up a system to review those nominations, as it turned out that also inappropriate or controversial postings have been reported. If you want to help us to get rid of the Spam from the archive, go to [9] and follow the instructions. You need a @debian.org-Mailadress to participate. If you don't have one, you can help us by reviewing the Listarchive[10] itself and press the 'Report as Spam'-Button. We also maintain a Wiki-Page[11] for Details and coordination. This is a nice way to kill some free time. Is there something similar planned for the BTS or are the mark as spam messages in the BTS already dealed with? Cheers, Bastian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Comparing MarkDown and reST (Was: Consistent formating long descriptions as input data)
Andreas Tille dijo [Tue, Apr 28, 2009 at 04:51:56PM +0200]: 3. s/^(\s*)[.o]\s+/\1* / This enables rendering lists using 'o' and '.' as bullets I know 'o' is a character visually similar to a bullet... But I would really prefer to discourage its use as such, specially if now lists will be proplerly rendered. Yes, having a single 'o' is not usual in English - But it can be easily mis-detected i.e. for users relying on DDTP and using Spanish, 'or' is translated to 'o'. Which, if rendered as the first word in a line, will cause said line to be incorrectly rendered and unreadable. Adding the requirement of having an empty line above (or being the first line in the long description) could work, at least for this particular case. But I'd prefer dropping 'o' as a bullet marker. -- Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can we ship sources of a PDF file in the Debian diff?
On Tue,28.Apr.09, 20:56:57, Charles Plessy wrote: Also, can you tell us where to write comments related to NEW uploads in plain English, so that it can be documented in the Developers Reference? I think that debian/copyright it not the best place for this, and apparently README.source is not. How about README.NEW? Or can we just drop an email to ftpmas...@d.o at the time of the upload? I seem to recall that replying to the REJECT mail would be best and that the template for that mail would be adjusted accordingly. Don't recall where and when though. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 08:12:22PM +1000, Ben Finney wrote: Brett Parker idu...@sommitrealweird.co.uk writes: On 27 Apr 18:55, Noah Slater wrote: Unfortunately, I don't use folders so I don't think this will work for me. *boggle* - you claim to be on multiple lists and yet you don't use server side filtering and folders?! OK - now that's just plain odd. Folders aren't the only way to manage lots of messages sanely; ask any Google Mail user. Since I wouldn't dream of recommending anyone use a proprietary data silo like Google Mail, I invite you instead to look at the ‘sup’ package for a folder-less approach to organising email messages that many say is superior. Description: Software Upgrade Protocol implementation ? Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
+ Mike Hommey (Tue, 28 Apr 2009 20:52:36 +0200): Since I wouldn't dream of recommending anyone use a proprietary data silo like Google Mail, I invite you instead to look at the ‘sup’ package for a folder-less approach to organising email messages that many say is superior. Description: Software Upgrade Protocol implementation ? sup-mail is the chosen package name in Debian, given that sup was already taken. Cheers, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 08:52:36PM +0200, Mike Hommey wrote: On Tue, Apr 28, 2009 at 08:12:22PM +1000, Ben Finney wrote: Folders aren't the only way to manage lots of messages sanely; ask any Google Mail user. Since I wouldn't dream of recommending anyone use a proprietary data silo like Google Mail, I invite you instead to look at the ‘sup’ package for a folder-less approach to organising email messages that many say is superior. Description: Software Upgrade Protocol implementation Package: sup-mail Description: thread-centric mailer with tagging and fast search Sup is a console-based email client for people with a lot of email. It supports tagging, very fast full-text search, automatic contact-list management, custom code insertion via a hook system, and more. If you're the type of person who treats email as an extension of your long-term memory, Sup is for you. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@debian.org signature.asc Description: Digital signature
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Mike Hommey a écrit : On Tue, Apr 28, 2009 at 08:12:22PM +1000, Ben Finney wrote: Brett Parker idu...@sommitrealweird.co.uk writes: On 27 Apr 18:55, Noah Slater wrote: Unfortunately, I don't use folders so I don't think this will work for me. *boggle* - you claim to be on multiple lists and yet you don't use server side filtering and folders?! OK - now that's just plain odd. Folders aren't the only way to manage lots of messages sanely; ask any Google Mail user. Since I wouldn't dream of recommending anyone use a proprietary data silo like Google Mail, I invite you instead to look at the ‘sup’ package for a folder-less approach to organising email messages that many say is superior. Description: Software Upgrade Protocol implementation ? sup-mail - thread-centric mailer with tagging and fast search -- Mehdi Dogguy مهدي الدقي http://www.pps.jussieu.fr/~dogguy Tel.: (+33).1.44.27.28.38 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Misc developer news (#15)
On Tue, 28 Apr 2009, Bastian Venthur wrote: This is a nice way to kill some free time. Is there something similar planned for the BTS or are the mark as spam messages in the BTS already dealed with? They're currently handled manually, almost exclusively by Blars Blarson. I assume more help would be welcome, but there's currently no infrastructure in place to allow for individuals who aren't in the debbugs group to hide those messages. [That said, I do have a long-term plan to adjust the way we deal with spam so those messages are just hidden, not deleted as currently... but that's a bit of a ways off.] Don Armstrong -- If you wish to strive for peace of soul, then believe; if you wish to be a devotee of truth, then inquire. -- Friedrich Nietzsche http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 03:13:41PM -0400, James Vega wrote: On Tue, Apr 28, 2009 at 08:52:36PM +0200, Mike Hommey wrote: On Tue, Apr 28, 2009 at 08:12:22PM +1000, Ben Finney wrote: Folders aren't the only way to manage lots of messages sanely; ask any Google Mail user. Since I wouldn't dream of recommending anyone use a proprietary data silo like Google Mail, I invite you instead to look at the ‘sup’ package for a folder-less approach to organising email messages that many say is superior. Description: Software Upgrade Protocol implementation Package: sup-mail Description: thread-centric mailer with tagging and fast search Sup is a console-based email client for people with a lot of email. It supports tagging, very fast full-text search, automatic contact-list management, custom code insertion via a hook system, and more. If you're the type of person who treats email as an extension of your long-term memory, Sup is for you. Hmm, this looks very interesting! Thanks for tip Ben. Maybe sup will make it easier for me to reply to mailing lists properly! ;) -- Noah Slater, http://tumbolia.org/nslater -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Webkit build issues
On Tue, Apr 28, 2009 at 09:45:41PM +0200, Adeodato Simó wrote:
Anyway, the exact list of Bin-NMUs is rather uninteresting. More
interesting can be, I think, the current list of known transitions
against which the Release Team works, which you were pointed at on
IRC later:
https://buildd.debian.org/transitions/summary.html
Is that page linked from anywhere? I've looked into the most obvious
(to me) places (e.g., {buildd,release}.d.o), but I failed to find it.
As a bonus, Google found this for me:
http://wiki.debian.org/OngoingTransitions which looks a bit
outdated.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: Can we ship sources of a PDF file in the Debian diff?
On 11734 March 1977, Charles Plessy wrote: In my profession we often say “The person who does not make mistakes usually does not do any work at all.”, so it is fine with me. Can I re-upload a version for main that you would fast-track to resolve the issue? Also, can you tell us where to write comments related to NEW uploads in plain English, so that it can be documented in the Developers Reference? I think that debian/copyright it not the best place for this, and apparently README.source is not. How about README.NEW? Or can we just drop an email to ftpmas...@d.o at the time of the upload? The best is usual the latest changelog entry (well, one of the changelog entries the highest-versioned .changes will include) as that is shown in NEW processing. Though i should probably also extract README.source, but i dislike the idea of another control file. And yes, email is also supposed to work. -- bye, Joerg Some AM after a mistake: Sigh. One shouldn't AM in the early AM, as it were. grin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can we ship sources of a PDF file in the Debian diff?
On 11734 March 1977, Andreas Tille wrote: How to address the fact that a rejection issue is solved now? Reply to the rejection mail *or* have a changelog entry fixed lalala as mentioned by ftpmaster. -- bye, Joerg Free beer is something that I am never going to drink and free speech is something that people are never going to be allowed to. ;) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Hello, On Tue, 2009-04-28 at 12:07 +1000, Ben Finney wrote: Bjørn Mork bj...@mork.no writes: I don't know, but there are plenty of reasons to choose from. See e.g. http://www.unicom.com/pw/reply-to-harmful.html A stronger, and simpler, case is made by URL:http://woozle.org/~neale/papers/reply-to-still-harmful/ which notes that the newer IETF standards make it much clearer that the Reply-To field is specifically for the message sender to create. No matter how you implement that technically, Here's what I am considering to be a sensible behavior. [Blindly ignoring any CoC, RFC and any other current practice. BTW I am not a mailing-list guru/expert/addict, just observing what people do, on Debian m-l] If the sender of the previous email is subscribed to the list: If I select Reply: To=mailing-list CC= If I select Reply to all: To=mailing-list CC=Previous email's recipient. If the sender of the previous mail was NOT subscribed to the list. If I select Reply: To=sender,mailing-list CC= If I select Reply to all: To=sender,mailing-list CC=Previous email's recipient. = Do you agree with this? Can we forward it to list-masters? There are a few more things I am pretty sure: * Joe User should not be expected to know about mailing list, especially when he posts on debian-...@lists.debian.org and other user support mailing list (i.e asking to be CC'ed, not CC'ing people...). * Joe User should not be expected to know about Reply to list option. (Joe User only has 2 buttons: reply and reply to all) * Expecting any user to _configure_ it's MUA to have the expected behavior is the wrong way to achieve the goal. * Expecting the user to edit headers (Reply-To or Follow-up-to...) isn't reasonable, because most end-user MUA (Thunderbird, Evolution, Outlook, Lotus Notes) don't allow doing it easily. note: If you use debian-www (and probably a few other lists like debian-boot) then you are in big trouble when you need to reply to an @debian.org user... knowing if that user is subscribed is pure guess|luck. Less is more, or to put it another way: flame-sandbox Yes, I am a big fan of Gnome: i.e. Let's have less buttons that actually do what people expect./flame-sandbox Regards, Franklin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Misc developer news (#15)
On Tue, 28 Apr 2009, Raphael Hertzog wrote: RFH: Removing spam from the listarchive --- As you all know, Lists and the Listarchive aren't 100% Spam-free. So we provide a 'Report as Spam' on every page in the archive. Now we set up a system to review those nominations, as it turned out that also inappropriate or controversial postings have been reported. If you want to help us to get rid of the Spam from the archive, go to [9] and follow the instructions. You need a @debian.org-Mailadress to participate. I never got any information whether the liststat effort turned out to be useful in this topic after I wrote to listmaster: On Sat, 31 Jan 2009, Andreas Tille wrote: On Wed, 28 Jan 2009, Cord Beermann wrote: I'd like to take your input into our spamremoval-effort, at least for nominating for review and maybe as one 'spam'-vote in the review process. I tweaked my script for the mailing list stats and now it just prints an URL per line. Currently I have 4290 URLs in http://sd-13492.dedibox.fr/~tille/spamurls.txt Feel free to use them as you feel apropriate Andreas. The fact that this URL is not avialbale any more (I just noticed this just now) but nobody asked me about this lets me guess that the data was actually not used. The file is now available at http://blends.debian.net/liststats/spamurls.txt and I'm keen on hearing which additional information you might need to count the mails mentioned in this file as SPAM vote. Kind regards and thanks for caring for listmaster Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
Frank Lin PIAT fp...@klabs.be writes: If the sender of the previous email is subscribed to the list: If I select Reply: To=mailing-list CC= If I select Reply to all: To=mailing-list CC=Previous email's recipient. If the sender of the previous mail was NOT subscribed to the list. If I select Reply: To=sender,mailing-list CC= If I select Reply to all: To=sender,mailing-list CC=Previous email's recipient. = Do you agree with this? Can we forward it to list-masters? I either don't agree with this or think that you're leaving out a function that's important. Gnus has two reply functions, which it calls reply and follow-up using the old Usenet definitions. Its default behavior without any configuration is: Reply: To: sender Cc: Follow-Up: To: sender Cc: mailing-list Note the capacity for private reply. Any system that doesn't allow for a private reply to the sender is unacceptably broken in my opinion. If you configure Gnus with knowledge of the mailing list address, as I've done for all the Debian mailing lists, it will instead do: Follow-Up: To: mailing-list Cc: and there is a separate really wide reply function that will copy the sender anyway. It also honors Mail-Followup-To, for whatever that's worth. I don't really care what the default action is, but one of the standard reply options in any mail client should send a private reply to a public mailing list message. There are a few more things I am pretty sure: * Joe User should not be expected to know about Reply to list option. (Joe User only has 2 buttons: reply and reply to all) If this is the case, then your proposal above is unacceptable since it leaves Joe User without a way to reply privately. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Comparing MarkDown and reST (Was: Consistent formating long descriptions as input data)
On Tue, 28 Apr 2009, Gunnar Wolf wrote: But I'd prefer dropping 'o' as a bullet marker. Yes, me too. But somewhere in this longish discussion it was suggested to find a solution for currently existing descriptions and ditch these cases later. I do not want to spend my time to seek for the URL of this mail in the archive. It sounds somehow reasonable to me for a transitional period (and same for '.'). Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 10:54:07PM +0200, Frank Lin PIAT wrote: If the sender of the previous email is subscribed to the list: If I select Reply: To=mailing-list CC= What if you are replying to a response to somebody who is not subscribed to the list? The emailer you are responding to may not want to be CCed, but the initial person may want to get the CCs. In case this is not clear, A: initial message from somebody not subscribed B: response to A somebody who is subscribed. You want to respond to B, so sender(A) needs a CC but sender(B) doesn't. I don't think this is uncommon. By your logic no one would get the CC. -- Brian May b...@snoopy.debian.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 02:34:11PM +0200, Giacomo A. Catenazzi wrote: personally I've more difficulty on handling usenet post on different computer: synchronize read post at home, office and offline laptop. Unfortunately, this has also put me off NNTP. I think this is a limitation in the client. I don't think there has been much work on improving NNTP clients, probably because everyone is addicted to mailing lists. I want a distributed way of synchronising the read post list. I can think of several approaches you could take, however it needs somebody who is willing to implement it (and ideally create a standard). (another problem with usenet is that last I looked there didn't seem to be any real servers in my country - Australia - everything has to be fetched from overseas servers - although it sometimes isn't always immediately obvious). -- Brian May b...@snoopy.debian.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Comparing MarkDown and reST
Osamu Aoki os...@debian.org writes: As I checked popularity of similar plain text formatters via popcon, http://people.debian.org/~osamu/pub/getwiki/html/ch12.en.html#listoftoolstohigghtplaintextdata asciidoc 0.8% installed markdown 0.4% installed rest2web 0.1% installed The correct package to check for reStructuredText support is not ‘rest2web’ (a rather specialised tool to build a whole website, irrelevant for the purpose of this discussion), but ‘python-docutils’ (the library support and generic tools for reST rendering). How did you generate your statistics, and can you do so with the ‘python-docutils’ package for comparison? -- \ “I see little commercial potential for the Internet for at | `\ least ten years.” —Bill Gates, 1994 | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Folder-less email management with ‘sup-mail’ (was: ignoring the CoC in regards to cc:s)
Noah Slater nsla...@tumbolia.org writes: Hmm, [‘sup-mail’] looks very interesting! Thanks for tip Ben. You're welcome. Caveat: I tried it and dropped it because its support for Unicode is currently broken (Bug#520374), and Ruby isn't a language I'm able to hack. -- \ “He who allows oppression, shares the crime.” —Erasmus Darwin, | `\ grandfather of Charles Darwin | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Tue, Apr 28, 2009 at 09:19:04AM +0200, Vincent Bernat wrote: How Mutt is able to detect all mailing lists? The fields in the headers only allow to detect the current mailing list. You can define what are mailing lists using the lists and subcribe config options. -- Brian May b...@snoopy.debian.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s
[Noah Slater] Mandating something which relies on the wholesale upgrade of hundreds of MUAs to get right by default doesn't sound like a good solution to me. I don't care how many RFCs you wave in my face. :) Let's see ... another series of MUA-related standards documents, RFC 2045 and following (Multipurpose Internet Mail Extensions), was published in November 1996, close to 2 years before the one we're talking about. Maybe it's just me, but it seems like 2 years ago, a MUA that didn't support MIME would have been laughed out of town. Does that mean it's finally time to expect support for RFC 2369? -- Peter Samuelson | org-tld!p12n!peter | http://p12n.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
+ Frank Lin PIAT (Tue, 28 Apr 2009 22:54:07 +0200): If the sender of the previous email is subscribed to the list: [...] If the sender of the previous mail was NOT subscribed to the list. [...] And how does one (or their MUA) know which of these is the case? -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ignoring the CoC in regards to cc:s (Re: Can we ship sources of a PDF file in the Debian diff?
On Wed, 2009-04-29 at 07:46 +0200, Adeodato Simó wrote: + Frank Lin PIAT (Tue, 28 Apr 2009 22:54:07 +0200): If the sender of the previous email is subscribed to the list: [...] If the sender of the previous mail was NOT subscribed to the list. [...] And how does one (or their MUA) know which of these is the case? That's a technical problem. Reading the thread, I am pretty sure we have lots of m-l experts around. My quick assumption is that the mailing list should mangle some headers (because we shouldn't assume that the mail sender didn't configured it's MUA to customize some headers). Regards, Franklin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libmail-box-perl 2.089-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 08:26:07 +0300 Source: libmail-box-perl Binary: libmail-box-perl Architecture: source all Version: 2.089-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: libmail-box-perl - message-folder management module Changes: libmail-box-perl (2.089-1) unstable; urgency=low . * New upstream release * control: change Homepage to the official upstream site Checksums-Sha1: 1addd33cfa69e524d325a515cebeae73364c0166 1872 libmail-box-perl_2.089-1.dsc b50c4462ad93bb7a3f532b9670d0eedcefbfa282 606803 libmail-box-perl_2.089.orig.tar.gz 3978c11ce0d8f4073496c4335dd8918ac82fb18f 6432 libmail-box-perl_2.089-1.diff.gz 3986ef641605583f5eb05019b729dbc852832ebe 1074024 libmail-box-perl_2.089-1_all.deb Checksums-Sha256: ab8d4a931f86fa936229a017547b4676e711da321d0e42981dfa460c71a62575 1872 libmail-box-perl_2.089-1.dsc afb84e9b4a17730bc27d9767d63ec39f66c9a2d27170ac86f47b2efc91ff6c8b 606803 libmail-box-perl_2.089.orig.tar.gz 949f6a2411cb486b202fb213980325e9ed69546c594a2166046d60fdc8c59d28 6432 libmail-box-perl_2.089-1.diff.gz 48a7ff942082a131c7981ba8f1d121eb3bf25f9ce706fb1a6883f6d612c05aa5 1074024 libmail-box-perl_2.089-1_all.deb Files: 8e81f6c81353e3c6d032ea0d4093573b 1872 perl optional libmail-box-perl_2.089-1.dsc 070a87fa1e0cb498c35e1a3dcee84fe0 606803 perl optional libmail-box-perl_2.089.orig.tar.gz a86feef267ae88f93c336cbba1450915 6432 perl optional libmail-box-perl_2.089-1.diff.gz 85c44e3c3f15acc98b51bcf2c4bec140 1074024 perl optional libmail-box-perl_2.089-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn2lEwACgkQHqjlqpcl9jsBlACfetLHhsngBdVZqCU6NTiymbXD e5MAn1cD5rE9SAQKqnKKwunjhg1la6bH =+gdp -END PGP SIGNATURE- Accepted: libmail-box-perl_2.089-1.diff.gz to pool/main/libm/libmail-box-perl/libmail-box-perl_2.089-1.diff.gz libmail-box-perl_2.089-1.dsc to pool/main/libm/libmail-box-perl/libmail-box-perl_2.089-1.dsc libmail-box-perl_2.089-1_all.deb to pool/main/libm/libmail-box-perl/libmail-box-perl_2.089-1_all.deb libmail-box-perl_2.089.orig.tar.gz to pool/main/libm/libmail-box-perl/libmail-box-perl_2.089.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted xulrunner 1.9.0.10-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 07:26:33 +0200 Source: xulrunner Binary: xulrunner-1.9 xulrunner-1.9-gnome-support libmozjs1d libmozjs-dev libmozjs1d-dbg spidermonkey-bin xulrunner-dev xulrunner-1.9-dbg libmozillainterfaces-java python-xpcom Architecture: source all amd64 Version: 1.9.0.10-1 Distribution: unstable Urgency: high Maintainer: Mike Hommey gland...@debian.org Changed-By: Mike Hommey gland...@debian.org Description: libmozillainterfaces-java - XPCOM bindings for Java libmozjs-dev - Development files for the Mozilla SpiderMonkey JavaScript library libmozjs1d - The Mozilla SpiderMonkey JavaScript library libmozjs1d-dbg - Development files for the Mozilla SpiderMonkey JavaScript library python-xpcom - XPCOM bindings for Python spidermonkey-bin - standalone JavaScript/ECMAScript (ECMA-262) interpreter xulrunner-1.9 - XUL + XPCOM application runner xulrunner-1.9-dbg - Development files for the Gecko engine library xulrunner-1.9-gnome-support - Support for GNOME in xulrunner applications xulrunner-dev - Development files for the Gecko engine library Closes: 525740 Changes: xulrunner (1.9.0.10-1) unstable; urgency=high . * New upstream release. * Fixes mfsa-2009-23 also known as CVE-2009-1313 (Regression crash). Closes: #525740. Checksums-Sha1: df3b27dcc99f0da3ac6c5e101fb400b91a2a1bdd 1760 xulrunner_1.9.0.10-1.dsc 18138597aa69a4c28a50f3651fdeea76a2d13fad 43736377 xulrunner_1.9.0.10.orig.tar.gz 239b7223bf88735662ea48534262ddf2668abedc 115483 xulrunner_1.9.0.10-1.diff.gz a47d62103981f3db277cec88b0eecd8d48ed652c 1480396 libmozillainterfaces-java_1.9.0.10-1_all.deb 4d3cda5b2529e11d3107cfc3294b8455b0cb311c 7726112 xulrunner-1.9_1.9.0.10-1_amd64.deb c18ce8fa3c6596b6e579de9b4c80f1eae5f9fcbb 100782 xulrunner-1.9-gnome-support_1.9.0.10-1_amd64.deb c520eeda88e90687a648e9b8c2d75660dc80e343 373084 libmozjs1d_1.9.0.10-1_amd64.deb 30ed1ac4584f1a5c94c64db9c61ab804f4bbf947 223044 libmozjs-dev_1.9.0.10-1_amd64.deb 85ba3c01b445b793f5f2347348414b40b2a68c0b 884826 libmozjs1d-dbg_1.9.0.10-1_amd64.deb 86ca19e29ed98afddd4b7452f2748308fc07a23e 69308 spidermonkey-bin_1.9.0.10-1_amd64.deb 243356c43d0fcac65a6151ca970c84f4bf87f4dc 3586914 xulrunner-dev_1.9.0.10-1_amd64.deb 9b07b4b52118478800bdd488b12ee4c381bd2f1e 50423032 xulrunner-1.9-dbg_1.9.0.10-1_amd64.deb faa549dc2595c5526c9da58ccdb4dd50abb79a49 150766 python-xpcom_1.9.0.10-1_amd64.deb Checksums-Sha256: 14af7658e129bfdd57e904ce58470b920affab92da184372b5deb228ee7b6f00 1760 xulrunner_1.9.0.10-1.dsc 1bff6f53f5db3d0b1bc77ffe6371fbdefe175adda278e0afaab4a4c00bf657d8 43736377 xulrunner_1.9.0.10.orig.tar.gz cb56e292d6fdd918863aa7f35107bf3c900ecfd0164e2ad9f073df66b526d5cd 115483 xulrunner_1.9.0.10-1.diff.gz a0154ffc8fb03bcbd7993ad4350327ceb20bbe13be865054319875d00caaefbc 1480396 libmozillainterfaces-java_1.9.0.10-1_all.deb fd8a3eb3b1f8b48e74db22bb2ecd9fabf008ddea5cf91c627a82ec6e1dd3a681 7726112 xulrunner-1.9_1.9.0.10-1_amd64.deb 3a69d6aeb76e08b1da307366c789f11e3435b5c94962c7f654b121c0d454864e 100782 xulrunner-1.9-gnome-support_1.9.0.10-1_amd64.deb 394d4ea45f4eec028bbe4931d033ed7232225476b200692d90796a35b688d1e7 373084 libmozjs1d_1.9.0.10-1_amd64.deb f9b62697c67245619d3c13beedbba5fe0884ef5a5098a61d0775b4c1dbf2e204 223044 libmozjs-dev_1.9.0.10-1_amd64.deb 5efd685821358c444d77189adc5fb7cc5423bf5fb435dfaea3f841cd79c06cbe 884826 libmozjs1d-dbg_1.9.0.10-1_amd64.deb c66edf1c3d5d165f6cada959cf129fc0cf6c34f0356afb987cf6b292aa9570e9 69308 spidermonkey-bin_1.9.0.10-1_amd64.deb 983e270377b5b7116d79c5cc17e7add39d3352abc37056a5d2c7346d2d1df331 3586914 xulrunner-dev_1.9.0.10-1_amd64.deb 668828df541cca74fbb90a00583d68d4b17b9363cead7eba374ccced0c93 50423032 xulrunner-1.9-dbg_1.9.0.10-1_amd64.deb f620eb163b254a5e3d697c13a9cb72db81fc15da69dd09ecc331f0331f68e316 150766 python-xpcom_1.9.0.10-1_amd64.deb Files: 85ad06c9a3095c84fc4fd9530b9ab89f 1760 devel optional xulrunner_1.9.0.10-1.dsc 15e8a98254829bf869afe7c7e99c9b02 43736377 devel optional xulrunner_1.9.0.10.orig.tar.gz 9f457667dcf0fc1d6662bdaf0b0965ac 115483 devel optional xulrunner_1.9.0.10-1.diff.gz 556a4fb56cb3cce6b96cb5aa85a5de3f 1480396 libdevel extra libmozillainterfaces-java_1.9.0.10-1_all.deb d46defb13329447430d1f400e0dfc2c4 7726112 devel optional xulrunner-1.9_1.9.0.10-1_amd64.deb f5a80a4cdf73b8c7b0616d1efc1065e1 100782 devel optional xulrunner-1.9-gnome-support_1.9.0.10-1_amd64.deb cbaf63c9f8b1a58dffec17eefb19a485 373084 libs optional libmozjs1d_1.9.0.10-1_amd64.deb 6fdb80bd2173fc6c4baab046ca3cc27e 223044 libdevel optional libmozjs-dev_1.9.0.10-1_amd64.deb 4bf98893e6577a0652a71b5c02f148a8 884826 libdevel extra libmozjs1d-dbg_1.9.0.10-1_amd64.deb af4390916c0406124725531ca17578fb 69308 interpreters optional spidermonkey-bin_1.9.0.10-1_amd64.deb 4f485beefbd8b17d70d46d41e7c7848c 3586914 libdevel optional xulrunner-dev_1.9.0.10-1_amd64.deb 78bd33e84805403409abeba8216e1e56 50423032 libdevel
Accepted labplot 1.6.0.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 17 Apr 2009 10:37:44 +0200 Source: labplot Binary: labplot Architecture: source i386 Version: 1.6.0.2-2 Distribution: unstable Urgency: low Maintainer: Helen Faulkner he...@debian.org Changed-By: Frank S. Thomas f...@debian.org Description: labplot- data plotting and function analysis tool for KDE Closes: 523598 Changes: labplot (1.6.0.2-2) unstable; urgency=low . * debian/rules: Adjusted file paths of libtool.m4 and ltmain.sh for the new libtool (Closes: #523598). * debian/control: Bumped Standards-Version from 3.8.0 to 3.8.1, no changes required. Checksums-Sha1: b3f4d9996c550d93e2e4594c5749233fbb30cb61 1569 labplot_1.6.0.2-2.dsc df971e5f8f4da78c4513a3baa1486a0802b80706 14390 labplot_1.6.0.2-2.diff.gz 88247356a6347578060b2d48a2081e1b04542d9a 6844264 labplot_1.6.0.2-2_i386.deb Checksums-Sha256: 5b28bbd7f25e77db5a248b010e5a5f6e71ec96267a6084e6ced88dd03696ac10 1569 labplot_1.6.0.2-2.dsc 73d44bc89ff91798415f244db4c838be3d29b1a9b782c67577b0ef994c53969e 14390 labplot_1.6.0.2-2.diff.gz 1b2cb11b14a8cc13b4b0d8072465afab4ee4d64dd68068a0466c5ee736d2f72b 6844264 labplot_1.6.0.2-2_i386.deb Files: f7282e6e622cde82c7daad2d816573cd 1569 kde optional labplot_1.6.0.2-2.dsc d64c40a982ec9d2ada3fbf2ab6a1c3de 14390 kde optional labplot_1.6.0.2-2.diff.gz 373fce7b0982f921cb226ac3341b3f85 6844264 kde optional labplot_1.6.0.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn2spcACgkQft6HNdxCZCmCbQCfeawoe3vLzvSkRch/9ToExNrS gwIAn1EqKfx9QIia/c7vD5vJY9hPR+Sy =+VAz -END PGP SIGNATURE- Accepted: labplot_1.6.0.2-2.diff.gz to pool/main/l/labplot/labplot_1.6.0.2-2.diff.gz labplot_1.6.0.2-2.dsc to pool/main/l/labplot/labplot_1.6.0.2-2.dsc labplot_1.6.0.2-2_i386.deb to pool/main/l/labplot/labplot_1.6.0.2-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted librack-ruby 1.0.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 02:14:00 -0700 Source: librack-ruby Binary: librack-ruby1.8 librack-ruby Architecture: source all Version: 1.0.0-1 Distribution: unstable Urgency: low Maintainer: Sebastien Delafond s...@debian.org Changed-By: Sebastien Delafond s...@debian.org Description: librack-ruby - A modular Ruby webserver interface librack-ruby1.8 - A modular Ruby webserver interface (Ruby 1.8) Changes: librack-ruby (1.0.0-1) unstable; urgency=low . * New upstream release. * Added debian/watch file. * Bumped up Standards version to 3.8.1. * BUmped up debhelper compat level to 6. * Moved to section ruby. * Added proper versioned dependency on debhelper (for dh_lintian). * Updated short description for librack-ruby1.8. Checksums-Sha1: 38d3afee6e778c8e4bb04ddd196413789b71a4e1 1005 librack-ruby_1.0.0-1.dsc 53609db88608fb846a0a62df803ae2bb33372cfe 321280 librack-ruby_1.0.0.orig.tar.gz b653c3607da9d433dfa2a49244b3afd00d9e66bc 2563 librack-ruby_1.0.0-1.diff.gz 39b15679cf3df4d89fdce72d6b09a4b919324f1a 52392 librack-ruby1.8_1.0.0-1_all.deb 4a495f9c0e00daedda8837f1a3c8789063867529 207844 librack-ruby_1.0.0-1_all.deb Checksums-Sha256: 7c7a55cc1e982e6297a6e6911178a14bfaa3cf1e141aba9654cbbd98bedb86d3 1005 librack-ruby_1.0.0-1.dsc 769f4bab5382e033ba81e9948c6182d3ed36c6d3c9e1f3bfe3d95de7f2da01c3 321280 librack-ruby_1.0.0.orig.tar.gz 15659ecf1125de9d7a4e3a6fae6ba371aff35c370e2e616421ca5f310e32f2c3 2563 librack-ruby_1.0.0-1.diff.gz f69d39ce3de45234d7bca56999d1d716f8f726b3a7cac07d5bea2d99d714dad7 52392 librack-ruby1.8_1.0.0-1_all.deb 6b32ad576b3a4a111f7c0a540f3d8f9a43892d0b0f1c6efc68e7232f968849b6 207844 librack-ruby_1.0.0-1_all.deb Files: 65c61a2bc24497671566cf724db9813c 1005 ruby optional librack-ruby_1.0.0-1.dsc 99c0efa9feae2780238440b3c8dd8dbd 321280 ruby optional librack-ruby_1.0.0.orig.tar.gz ad2652db3e7f919ae8aeb270eae31eb3 2563 ruby optional librack-ruby_1.0.0-1.diff.gz 68a8f4ca61d70c46885008dee3242296 52392 ruby optional librack-ruby1.8_1.0.0-1_all.deb 4f46d1c5c14707fb9209c88f7612ca0f 207844 ruby optional librack-ruby_1.0.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn2yOwACgkQiZgNKcDdyD+32ACggz/MrShxb1Si2ewE8yCFqU3M ia8AniwOI/51sWdSv+2yWemoM3B35QO6 =N9AF -END PGP SIGNATURE- Accepted: librack-ruby1.8_1.0.0-1_all.deb to pool/main/libr/librack-ruby/librack-ruby1.8_1.0.0-1_all.deb librack-ruby_1.0.0-1.diff.gz to pool/main/libr/librack-ruby/librack-ruby_1.0.0-1.diff.gz librack-ruby_1.0.0-1.dsc to pool/main/libr/librack-ruby/librack-ruby_1.0.0-1.dsc librack-ruby_1.0.0-1_all.deb to pool/main/libr/librack-ruby/librack-ruby_1.0.0-1_all.deb librack-ruby_1.0.0.orig.tar.gz to pool/main/libr/librack-ruby/librack-ruby_1.0.0.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted firebird2.1 2.1.2.18118-0.ds1-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 09:22:40 +0300 Source: firebird2.1 Binary: firebird2.1-super firebird2.1-classic libfbclient2 libfbembed2.1 firebird2.1-common firebird2.1-server-common firebird2.1-dev firebird2.1-examples firebird2.1-doc firebird2.1-common-doc Architecture: source all amd64 Version: 2.1.2.18118-0.ds1-1 Distribution: unstable Urgency: low Maintainer: Debian Firebird Group pkg-firebird-gene...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: firebird2.1-classic - Firebird Classic Server - an RDBMS based on InterBase 6.0 code firebird2.1-common - common files for firebird 2.1 servers and clients firebird2.1-common-doc - copyright, licnesing anc changelogs of firebird2.1 firebird2.1-dev - Development files for Firebird - an RDBMS based on InterBase 6.0 firebird2.1-doc - Documentation files for firebird database version 2.1 firebird2.1-examples - Examples for Firebird - an RDBMS based on InterBase 6.0 code firebird2.1-server-common - common files for firebird 2.1 servers firebird2.1-super - Firebird Super Server - an RDBMS based on InterBase 6.0 code libfbclient2 - Firebird client library libfbembed2.1 - Firebird embedded client/server library Changes: firebird2.1 (2.1.2.18118-0.ds1-1) unstable; urgency=low . * New Upstream Version + update debian/copyright + refresh patches - remove cvs-execute-statement-crash.patch: released upstream * stop shipping /var/run/firebird/2.1 in -server-common it is created by the init scripts if not already present * now conforms to Policy 3.8.1 * *.config: fix detection of super/classic flavour Checksums-Sha1: 5c76aea13447b605b4c95617a49e9d7f9d2963f1 1755 firebird2.1_2.1.2.18118-0.ds1-1.dsc 6dd82cf892757b603013e8acbd94fa9f8fdceceb 7542237 firebird2.1_2.1.2.18118-0.ds1.orig.tar.gz 349325c8a692dc3adbe84ce11b51f7b9531fef56 111799 firebird2.1_2.1.2.18118-0.ds1-1.diff.gz 86147164d1d0c85dea2b2b9c85dfb0a03b2dac9d 57486 firebird2.1-dev_2.1.2.18118-0.ds1-1_all.deb d677d1d6e06196a3c37d6b24db54558d7af08692 163012 firebird2.1-examples_2.1.2.18118-0.ds1-1_all.deb 6b03e9582e0e6addc0f96231ebfaf8f7e499cb30 1104548 firebird2.1-doc_2.1.2.18118-0.ds1-1_all.deb 62e2cf9c7d6386e39b56b206c06d530f6fbccf6c 470466 firebird2.1-common-doc_2.1.2.18118-0.ds1-1_all.deb 8e40e7badfabd714175f8a7cd5a36250c2db73f1 2926656 firebird2.1-super_2.1.2.18118-0.ds1-1_amd64.deb 3dea951ed08761551aca2501aea16d1c9f09b73f 1565182 firebird2.1-classic_2.1.2.18118-0.ds1-1_amd64.deb 2b7e174d612a4399935c35a2d2627819bdc644c4 265714 libfbclient2_2.1.2.18118-0.ds1-1_amd64.deb 88ef30276bb79430ace2890f0880bca722c7537d 1343856 libfbembed2.1_2.1.2.18118-0.ds1-1_amd64.deb 1df23f1c46980e9287992cf9993a68fccbbacb9d 468520 firebird2.1-common_2.1.2.18118-0.ds1-1_amd64.deb c6879af5f423c54afae86f1c36e5c173572c2548 135438 firebird2.1-server-common_2.1.2.18118-0.ds1-1_amd64.deb Checksums-Sha256: b51d5368dc972c0d4364cbda76aefb354da1cab95736e11bab9cc9a36e463218 1755 firebird2.1_2.1.2.18118-0.ds1-1.dsc bc76e9c668867085ad0853b87c49e1428f42a37590606d356377d1bab3273dea 7542237 firebird2.1_2.1.2.18118-0.ds1.orig.tar.gz 64a73a4f7dd91391715b27e91f3ec86b8c25544c97d928ee58ca7ee3ddb64586 111799 firebird2.1_2.1.2.18118-0.ds1-1.diff.gz 367b9551e3b80d5076c15d87999203d04d0f3985eec84f01f6c766331ed6bce3 57486 firebird2.1-dev_2.1.2.18118-0.ds1-1_all.deb 38fdd189adf392dffdb8c121069fd58b5d61ddc0962ae603bb7eee3614a77e09 163012 firebird2.1-examples_2.1.2.18118-0.ds1-1_all.deb a5f1f0a349879cef3da5b57bab778ca087b986aea2258a78223693e4da4152b0 1104548 firebird2.1-doc_2.1.2.18118-0.ds1-1_all.deb 6a8f9a90b48e659e2276376fe9a86ab6a8124ecf58dc00a7b4bfbe95a55ef51a 470466 firebird2.1-common-doc_2.1.2.18118-0.ds1-1_all.deb 6dc311d832b0047e568b4c9300651368c2bd300d6ddd4723f33826ff9175dda7 2926656 firebird2.1-super_2.1.2.18118-0.ds1-1_amd64.deb 66eee33ac02987f9b75a6055ce09c6cf9896b96b6815b978d75660532c08c140 1565182 firebird2.1-classic_2.1.2.18118-0.ds1-1_amd64.deb 8966a343e423f844c821ab9d2a81168ffceefc9c5165d17327112ef577ec8f8a 265714 libfbclient2_2.1.2.18118-0.ds1-1_amd64.deb 2e383f1d215b42d8c60106e196a5e9c4ece50b238331dc19da7b9a0c38d08578 1343856 libfbembed2.1_2.1.2.18118-0.ds1-1_amd64.deb dcfe97a68a56f76f72651d779d391e23fe792cc3bcd870fd245316c1e62452e9 468520 firebird2.1-common_2.1.2.18118-0.ds1-1_amd64.deb 79e0aa5f4610c12316ebc4c2b63f2d2ee5d5a73b4b78533c1cb5fa27643d 135438 firebird2.1-server-common_2.1.2.18118-0.ds1-1_amd64.deb Files: 48a82ff7a55c676112092f2411f82d7c 1755 misc optional firebird2.1_2.1.2.18118-0.ds1-1.dsc cb2265ba5d32c861c6e2e8d98819e006 7542237 misc optional firebird2.1_2.1.2.18118-0.ds1.orig.tar.gz 585d5994aa28d2d4c0cd293beaa420e8 111799 misc optional firebird2.1_2.1.2.18118-0.ds1-1.diff.gz 8b067aa8514713aa9a38f2eefddf9e5e 57486 libdevel optional firebird2.1-dev_2.1.2.18118-0.ds1-1_all.deb 9ba7e53591d714c04cc73ac664548c08 163012 doc optional
Accepted argyll 1.0.3+dfsg1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 11:47:38 +0200 Source: argyll Binary: argyll Architecture: source i386 Version: 1.0.3+dfsg1-1 Distribution: unstable Urgency: low Maintainer: Roland Mas lola...@debian.org Changed-By: Roland Mas lola...@debian.org Description: argyll - Color Management System, calibrator and profiler Closes: 524972 Changes: argyll (1.0.3+dfsg1-1) unstable; urgency=low . * argyll-firmware-spyder2 is now generated as section non-free/graphics rather than just graphics. * Removed non-free RFC from source package (closes: #524972). Checksums-Sha1: 23158634ad6c345cb649ee1c49424ed0765a4794 1333 argyll_1.0.3+dfsg1-1.dsc 67fcd4586840bc795995c026922fad9d19393732 4821619 argyll_1.0.3+dfsg1.orig.tar.gz f24ab6c9cf9ca34919aa44b9509b5341c9f15cce 24162 argyll_1.0.3+dfsg1-1.diff.gz 18592a968b8fcfae8428ddb993c655038790613f 9759826 argyll_1.0.3+dfsg1-1_i386.deb Checksums-Sha256: b4a59be448d0cd85cebf807d4861a2725fb7a111c88589346aee8f7b90054fee 1333 argyll_1.0.3+dfsg1-1.dsc 76f5da269a5f22c2541b0aebbff7a0cd63625ba95a09f651bcde82e802d188b5 4821619 argyll_1.0.3+dfsg1.orig.tar.gz a8f7cc48f196a888eeff11c09d7200364c99d159949b96eb06a517b14c02fd08 24162 argyll_1.0.3+dfsg1-1.diff.gz 8cfc5109ddf80e456dde2c873224c0b48c61c50dcdfc0fe5742d4608b9a33004 9759826 argyll_1.0.3+dfsg1-1_i386.deb Files: 8bc87492ad115e9cd162e0b6151b8996 1333 graphics optional argyll_1.0.3+dfsg1-1.dsc d3006d2658b32a666e21918c08f8ad70 4821619 graphics optional argyll_1.0.3+dfsg1.orig.tar.gz dac13f7dbf0a4679be3c876f56c18ca4 24162 graphics optional argyll_1.0.3+dfsg1-1.diff.gz 794605e1ca6505001ec0ae60a7d09a37 9759826 graphics optional argyll_1.0.3+dfsg1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9tQCDqdWtRRIQ/URAkvIAJ9QC6sy+dkWu3aGOphAVMKfpeI/4QCdFQbT 3NnmDGC/9PBNYb8G2MbTyKo= =MMn/ -END PGP SIGNATURE- Accepted: argyll_1.0.3+dfsg1-1.diff.gz to pool/main/a/argyll/argyll_1.0.3+dfsg1-1.diff.gz argyll_1.0.3+dfsg1-1.dsc to pool/main/a/argyll/argyll_1.0.3+dfsg1-1.dsc argyll_1.0.3+dfsg1-1_i386.deb to pool/main/a/argyll/argyll_1.0.3+dfsg1-1_i386.deb argyll_1.0.3+dfsg1.orig.tar.gz to pool/main/a/argyll/argyll_1.0.3+dfsg1.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted rootskel 1.76 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 11:52:17 +0100 Source: rootskel Binary: rootskel rootskel-bootfloppy Architecture: source i386 Version: 1.76 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Colin Watson cjwat...@debian.org Description: rootskel - Skeleton root filesystem used by debian-installer (udeb) rootskel-bootfloppy - Skeleton root filesystem used by debian-installer boot floppy (udeb) Changes: rootskel (1.76) unstable; urgency=low . [ Frans Pop ] * Drop support for the ppc64 architecture. Checksums-Sha1: 31e09c9e16f35aa9c4287774574b43edf887f8ee 1002 rootskel_1.76.dsc 8a6fd69e93433290dd2fb7b455dea843a29294d6 32154 rootskel_1.76.tar.gz 60c027e9ce01e8cd91bcbb226ef16b67012ff77b 8516 rootskel_1.76_i386.udeb 0e1ce14098e5c023a35a936cb439b98bb9fa3ebf 2690 rootskel-bootfloppy_1.76_i386.udeb Checksums-Sha256: c0410a0f5dc08e7f534a8f9ae689c11430de30ba796a1b83e10f377e3d6088ba 1002 rootskel_1.76.dsc eb32e8f3a670588144f2e857bca90b1de4820582da72c888aff4748ffb04963c 32154 rootskel_1.76.tar.gz 30ba86c4c4f46a968ee671004185f4705dd9227178fbbf7d7a069b27745f7d37 8516 rootskel_1.76_i386.udeb 259004413dac1ce01d1911d6b714fdf388721b325a88a260f914a1f9f6a534c4 2690 rootskel-bootfloppy_1.76_i386.udeb Files: 1d232d1d57767bb18055926a1c2f804e 1002 debian-installer standard rootskel_1.76.dsc f0cfc4a96a07556cbf9fb2506d2a2791 32154 debian-installer standard rootskel_1.76.tar.gz 5915d65621895194b8fb62e9d978 8516 debian-installer standard rootskel_1.76_i386.udeb 21cb0c91a97df4d0a627edb096090d44 2690 debian-installer extra rootskel-bootfloppy_1.76_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Colin Watson cjwat...@debian.org -- Debian developer iD8DBQFJ9uBT9t0zAhD6TNERAjGvAKCB9D6cupoxJctGTZY/3ujzgNGF7QCeKrFv 146Bk4Iv7iYuOQW626i6pps= =vRRX -END PGP SIGNATURE- Accepted: rootskel-bootfloppy_1.76_i386.udeb to pool/main/r/rootskel/rootskel-bootfloppy_1.76_i386.udeb rootskel_1.76.dsc to pool/main/r/rootskel/rootskel_1.76.dsc rootskel_1.76.tar.gz to pool/main/r/rootskel/rootskel_1.76.tar.gz rootskel_1.76_i386.udeb to pool/main/r/rootskel/rootskel_1.76_i386.udeb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted ledger 2.6.1-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 19:52:52 +1000 Source: ledger Binary: ledger Architecture: source amd64 Version: 2.6.1-3 Distribution: unstable Urgency: low Maintainer: Matt Palmer mpal...@debian.org Changed-By: Matt Palmer mpal...@debian.org Description: ledger - command-line double-entry accounting program Closes: 524976 Changes: ledger (2.6.1-3) unstable; urgency=low . * Put sample.dat and the scripts directory in examples. Closes: #524976. * Build and install the HTML docs as well. Just Because. Checksums-Sha1: dc1861f36ca58c13d0fb672ab876b904ab8d7a39 1065 ledger_2.6.1-3.dsc a03fa16934a4af623e39c3506c0ea9a9768ddc61 3062 ledger_2.6.1-3.diff.gz d1adf6e9e4772c0ba78bc2d1aea2c66767c62d20 601224 ledger_2.6.1-3_amd64.deb Checksums-Sha256: d97fe7620dfb8d1d1e9056e8c3d21af800f14483bbbe330119ce12aef0258e00 1065 ledger_2.6.1-3.dsc 42618307378540b675fd78e87e7247a3354392809cc5c4056d9b27bf274199eb 3062 ledger_2.6.1-3.diff.gz 1aee2a6fbde4e3c47ef5fcdeaf5e846e63ec01acaf7505fb77bf2c8ae1d4abfa 601224 ledger_2.6.1-3_amd64.deb Files: fc96c325cbe031a63435ac06e08913cd 1065 utils optional ledger_2.6.1-3.dsc 3f13b83aa6ce6948d53c161e6253d801 3062 utils optional ledger_2.6.1-3.diff.gz 0dff28529bfcdc6b1c184eefc02b 601224 utils optional ledger_2.6.1-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9tpQBEnrTWk1E4cRAjmwAJ93rt5LUvfEDmdYJMgVkujMp5pWuQCfSto2 KzK9tJOPmBApYwvjIeJCrHw= =t8gW -END PGP SIGNATURE- Accepted: ledger_2.6.1-3.diff.gz to pool/main/l/ledger/ledger_2.6.1-3.diff.gz ledger_2.6.1-3.dsc to pool/main/l/ledger/ledger_2.6.1-3.dsc ledger_2.6.1-3_amd64.deb to pool/main/l/ledger/ledger_2.6.1-3_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted gnome-python 2.26.1-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 25 Apr 2009 10:32:06 +0200 Source: gnome-python Binary: python-gnome2 python-gconf python-gnome2-dev python-gnome2-doc Architecture: source amd64 all Version: 2.26.1-1 Distribution: unstable Urgency: low Maintainer: Sebastien Bacher seb...@debian.org Changed-By: Luca Bruno lethalma...@gmail.com Description: python-gconf - Python bindings for the GConf configuration database system python-gnome2 - Python bindings for the GNOME desktop environment python-gnome2-dev - Python bindings for the GNOME desktop environment - development f python-gnome2-doc - Python bindings for the GNOME desktop environment Changes: gnome-python (2.26.1-1) unstable; urgency=low . * New upstream release. * debian/control.in: - Bump Standards-Version to 3.8.1 (no changes needed). * debian/patches/70_relibtoolize.patch: - Remove, lintian doesn't complain about rpath on amd64. Checksums-Sha1: 5578b3b663b52d6779b2eae3c8ad7d063dfe0850 1903 gnome-python_2.26.1-1.dsc 8c6afd649daad3160b08f52736716b79daf783cb 657971 gnome-python_2.26.1.orig.tar.gz 722c39f492e43d030fdbff630f2a55e29df7c102 8641 gnome-python_2.26.1-1.diff.gz 982abe4df8310de172f7dc93b448c98f68506fb6 211796 python-gnome2_2.26.1-1_amd64.deb 1cddf1260a25bc6c7bc592703d2550e5d4f5eb09 33752 python-gconf_2.26.1-1_amd64.deb b1a5ff3fa62104ba103ac69bb8cf28208a303627 46654 python-gnome2-dev_2.26.1-1_all.deb 3573021fc13c2981c41793b2bbba62b182c6ec80 44374 python-gnome2-doc_2.26.1-1_all.deb Checksums-Sha256: d1847ab33eb335310a2281317d8397fc9e796284872944890808186852e17667 1903 gnome-python_2.26.1-1.dsc 32391879a2b916ab66de751b4c1e11f8b341910fca3b813cf670d1d8b04f 657971 gnome-python_2.26.1.orig.tar.gz dc4f76e46f9f773db88dab0ff2d5836cc5987db31b6f334c9d48960f77ce8534 8641 gnome-python_2.26.1-1.diff.gz 51187512ee9f2c8b980bf0477e7948233d4b02b9951ea95d4a0ad4c42fbf092d 211796 python-gnome2_2.26.1-1_amd64.deb 6692a9aca7696e9493c8b92616a656d9b41ac8bd2a6dfb1cabcf6b1c17a8f0a9 33752 python-gconf_2.26.1-1_amd64.deb aa48d1ee4bf8f73bcd0758b8f81b2e685703031e08203a66784b6ecc10f027ad 46654 python-gnome2-dev_2.26.1-1_all.deb a07066123966684744f5aae06dc7e79078f5233e5b3928922d83bb06d841eaaa 44374 python-gnome2-doc_2.26.1-1_all.deb Files: ebf18600d3f7193fb1f0188dd06859dd 1903 python optional gnome-python_2.26.1-1.dsc e6d03350fa0d1bf4d57eaaa7c379721c 657971 python optional gnome-python_2.26.1.orig.tar.gz aa1fcb54e2f2a132e13cb33fd7ea58c2 8641 python optional gnome-python_2.26.1-1.diff.gz 682031f856fb87da60551790930bb616 211796 python optional python-gnome2_2.26.1-1_amd64.deb 2e82dbcf78b4a078b7b8d8d74574cd62 33752 python optional python-gconf_2.26.1-1_amd64.deb d4b2fbcc174597c7f9a549a9b6f8168a 46654 python optional python-gnome2-dev_2.26.1-1_all.deb 6dd107ae11a385254059337c2f280a6e 44374 doc optional python-gnome2-doc_2.26.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9t+QrSla4ddfhTMRAtWoAJ9gZULwFwZkchKgwfOHeu/iK00hHACcD4G9 Vppegu/dNr9g7yhogtOLOWE= =z2A+ -END PGP SIGNATURE- Accepted: gnome-python_2.26.1-1.diff.gz to pool/main/g/gnome-python/gnome-python_2.26.1-1.diff.gz gnome-python_2.26.1-1.dsc to pool/main/g/gnome-python/gnome-python_2.26.1-1.dsc gnome-python_2.26.1.orig.tar.gz to pool/main/g/gnome-python/gnome-python_2.26.1.orig.tar.gz python-gconf_2.26.1-1_amd64.deb to pool/main/g/gnome-python/python-gconf_2.26.1-1_amd64.deb python-gnome2-dev_2.26.1-1_all.deb to pool/main/g/gnome-python/python-gnome2-dev_2.26.1-1_all.deb python-gnome2-doc_2.26.1-1_all.deb to pool/main/g/gnome-python/python-gnome2-doc_2.26.1-1_all.deb python-gnome2_2.26.1-1_amd64.deb to pool/main/g/gnome-python/python-gnome2_2.26.1-1_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted arora 0.6-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 09:53:33 +0200 Source: arora Binary: arora Architecture: source amd64 Version: 0.6-1 Distribution: unstable Urgency: low Maintainer: Sune Vuorela deb...@pusling.com Changed-By: Sune Vuorela deb...@pusling.com Description: arora - simple cross platform web browser Closes: 513794 520279 520419 525862 Changes: arora (0.6-1) unstable; urgency=low . * New upstream. (Closes: #525862) - Crtl-Q works. (Closes: #520279) - Letters with accents are supposed to work: (Closes: #520419) * Keep strong dependencies for now to ensure feature parity across architectures. * Add menu file, thanks Pawel Sadkowski. (Closes: 513794) Checksums-Sha1: 8d784038e5d6d33626a53ba3b00cacf8076e7a1c 932 arora_0.6-1.dsc 8fa7821092dcb090b2ff84437dcf6774277b44d2 819356 arora_0.6.orig.tar.gz c0491a51722665e8442200affc2fd81b53b2c02a 2737 arora_0.6-1.diff.gz 983f01a06c28aa4ceed0a1d25556f71c7f5ed934 998230 arora_0.6-1_amd64.deb Checksums-Sha256: 3a63691191033a7e11feae83656c6f3da64936a7543d4ad59d0ad4c6a1dcdd1b 932 arora_0.6-1.dsc 8ece9bcef89179618ab230492d09ee81a24a60d0f8ac5221e5463b435a3c3d74 819356 arora_0.6.orig.tar.gz b168e8b42c80c4b72299a603abcb56584c6574c8b66088e0aa0cb23fd45e823a 2737 arora_0.6-1.diff.gz 6356aa235cbc30db43b173475981e887dfedad654d120af8bdabfc09b07c58fc 998230 arora_0.6-1_amd64.deb Files: de851eeeb33a6b5bab42821ca4571429 932 web extra arora_0.6-1.dsc 8af32512bbbea4a2f2514b30cbf3d50a 819356 web extra arora_0.6.orig.tar.gz 44ba78ab967d2858d37466a0e650391e 2737 web extra arora_0.6-1.diff.gz a0da09d7306d58b095048bce939c6afd 998230 web extra arora_0.6-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn2uPEACgkQnMvaFgH6i0o97gCfT5ztLuqRQlw6c0ip2OE+eaKz W20AnjiwHQP/xtxtlErYbUl3VoLMQpfz =Yp8T -END PGP SIGNATURE- Accepted: arora_0.6-1.diff.gz to pool/main/a/arora/arora_0.6-1.diff.gz arora_0.6-1.dsc to pool/main/a/arora/arora_0.6-1.dsc arora_0.6-1_amd64.deb to pool/main/a/arora/arora_0.6-1_amd64.deb arora_0.6.orig.tar.gz to pool/main/a/arora/arora_0.6.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libgnome 2.26.0-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 12:57:02 +0200 Source: libgnome Binary: libgnome2-0 libgnome2-dev libgnome2-common libgnome2-doc libgnome2-dbg Architecture: source all amd64 Version: 2.26.0-1 Distribution: unstable Urgency: low Maintainer: Ondřej Surý ond...@debian.org Changed-By: Josselin Mouette j...@debian.org Description: libgnome2-0 - The GNOME library - runtime files libgnome2-common - The GNOME library - common files libgnome2-dbg - The GNOME library - debugging symbols libgnome2-dev - The GNOME library - development files libgnome2-doc - The GNOME library - documentation files Closes: 519263 Changes: libgnome (2.26.0-1) unstable; urgency=low . [ Josselin Mouette ] * Add libglib2.0-doc to b-d-i to ensure proper xrefs. * Move gvfs from recommends to depends. Closes: #519263. * Stop mentioning GNOME 2. . [ Luca Bruno ] * New upstream release. * debian/control.in: - Bump intltool Build-Depend to 0.40.0. - Update to Standards-Version 3.8.1, no additional changes needed. - Fix debug package section. Checksums-Sha1: eb679c2b19776307877ca893be6b83d5571762f2 1556 libgnome_2.26.0-1.dsc f6529b460e7fae25cef3d07ef4b2fb07a7b87ee7 2012789 libgnome_2.26.0.orig.tar.gz bf99529d8fd64457572872c6ef1321f40f08445c 11265 libgnome_2.26.0-1.diff.gz 64c3bb0bd40e9f8f4c4c5e26fabcbade5800d4ec 1153810 libgnome2-common_2.26.0-1_all.deb 71843139611270a5cfed2753345091772dd21dca 129650 libgnome2-doc_2.26.0-1_all.deb 6edeca8638e3b276c62c13530795ec11b3a34939 125448 libgnome2-0_2.26.0-1_amd64.deb eb4b01b91a5ca1cc0506b8168550482afe362cc7 125336 libgnome2-dev_2.26.0-1_amd64.deb b2df59c7ba1d3f344af0b137bdac063681770e2b 162350 libgnome2-dbg_2.26.0-1_amd64.deb Checksums-Sha256: 6acbf0d81709b20330c3112ce6bd1ee784f065cf3ac3b99b6779bd38b7795468 1556 libgnome_2.26.0-1.dsc fbc4706693573feadf074b3421e796c1d5c8c5d079372485f0a561315481af83 2012789 libgnome_2.26.0.orig.tar.gz 28ccc1fe22ca9daff3a66fb2a3659aea2c57b11c34e87b982779962e7f05be4e 11265 libgnome_2.26.0-1.diff.gz 686cff04fbbd5fa2fff72166728c75f87864225a6ebf5a9150557bbd2c73d33f 1153810 libgnome2-common_2.26.0-1_all.deb d3f274e082f7919e345f7d4ed6a006132a98c11e21c9bfffa3f25a34383708b8 129650 libgnome2-doc_2.26.0-1_all.deb 599aff1abcb3abac8c01c1cdc9b169d1a55324885f627c37333d00e33bc6 125448 libgnome2-0_2.26.0-1_amd64.deb 6ea6bd383273e74b66033d4e0e66dd68997b31d5ede629c71ffa8c9902313fcb 125336 libgnome2-dev_2.26.0-1_amd64.deb 78c9fbf9226289d247a88c724b70d828ca62376d7e262251dde2d19f7aec02de 162350 libgnome2-dbg_2.26.0-1_amd64.deb Files: 52d62c47b1ffeed5a197dc7b51cd69f7 1556 devel optional libgnome_2.26.0-1.dsc 57d2d9003d4b1f37357c848af46bc263 2012789 devel optional libgnome_2.26.0.orig.tar.gz f47e7820c2c4eab18652978df4b5fefa 11265 devel optional libgnome_2.26.0-1.diff.gz 17d6a311b4b1ad2c9f1651c66a356f21 1153810 libs optional libgnome2-common_2.26.0-1_all.deb 08b482c86e5d11814b77176c2597fb56 129650 doc optional libgnome2-doc_2.26.0-1_all.deb 97520ff8a9848b0305515cdb9c1a2b08 125448 libs optional libgnome2-0_2.26.0-1_amd64.deb 4115d18db97812ea66d633393e4ecf0c 125336 libdevel optional libgnome2-dev_2.26.0-1_amd64.deb d884ca45365580508a750a421202 162350 debug extra libgnome2-dbg_2.26.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9uItrSla4ddfhTMRAjH6AKDB9u6t2sqb7S1zhrhLUIl8s6tInQCgu7fC RC/0Ul42qSSbs+ivqkUyy4U= =iwVU -END PGP SIGNATURE- Accepted: libgnome2-0_2.26.0-1_amd64.deb to pool/main/libg/libgnome/libgnome2-0_2.26.0-1_amd64.deb libgnome2-common_2.26.0-1_all.deb to pool/main/libg/libgnome/libgnome2-common_2.26.0-1_all.deb libgnome2-dbg_2.26.0-1_amd64.deb to pool/main/libg/libgnome/libgnome2-dbg_2.26.0-1_amd64.deb libgnome2-dev_2.26.0-1_amd64.deb to pool/main/libg/libgnome/libgnome2-dev_2.26.0-1_amd64.deb libgnome2-doc_2.26.0-1_all.deb to pool/main/libg/libgnome/libgnome2-doc_2.26.0-1_all.deb libgnome_2.26.0-1.diff.gz to pool/main/libg/libgnome/libgnome_2.26.0-1.diff.gz libgnome_2.26.0-1.dsc to pool/main/libg/libgnome/libgnome_2.26.0-1.dsc libgnome_2.26.0.orig.tar.gz to pool/main/libg/libgnome/libgnome_2.26.0.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted ecj 3.4.2-3 (source all hppa)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 07:56:20 +0200 Source: ecj Binary: ecj libecj-java libecj-java-gcj ecj1 ecj-gcj Architecture: source all hppa Version: 3.4.2-3 Distribution: experimental Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Matthias Klose d...@debian.org Description: ecj- standalone version of the Eclipse Java compiler ecj-gcj- standalone version of the Eclipse Java compiler (native version) ecj1 - java byte code compiler used by gcj libecj-java - Eclipse Java compiler (library) libecj-java-gcj - Eclipse Java compiler (native library) Changes: ecj (3.4.2-3) experimental; urgency=low . * Fix ecj dependencies for gcj-4.4. Checksums-Sha1: fc199bc44aa1f610fd829c25e60a5921a8fcb5b9 1306 ecj_3.4.2-3.dsc 7ce5398302c918a716cd85f7f7325773ac4a37ae 26018 ecj_3.4.2-3.diff.gz 83dad0833bc80a12ea9039e8e3b78851edb5a7ad 1215734 libecj-java_3.4.2-3_all.deb 77471ba746542e9661ec20f6f7fbf6e985b1910a 13868 ecj_3.4.2-3_hppa.deb 726de6d8ccab6e1aa54156b2df0c7fba5b26b4eb 2109958 libecj-java-gcj_3.4.2-3_hppa.deb 0c4bcc6b14a5cba47625a81abc9d70c5a568b6fd 1722044 ecj-gcj_3.4.2-3_hppa.deb Checksums-Sha256: eda72a004d6a44badd0eb7755143214e155857784b3c38aca3119e6925fac7a0 1306 ecj_3.4.2-3.dsc 30232907cd0bb6493eea5841799f562e37a335e2d7af799769dce9d883c4f036 26018 ecj_3.4.2-3.diff.gz 14237340716bccac004a91c3224f45f2e1d3316fa50a0e40a605fbf20da844d1 1215734 libecj-java_3.4.2-3_all.deb 4eba78666b0c7c450a4d5b85ee6f9faad4b5dc873625b2ce723be78e2a7a2e07 13868 ecj_3.4.2-3_hppa.deb 87be6f7201300a5a76d92655de8758679ca1da7fbece5764ec67dff4e211b0ec 2109958 libecj-java-gcj_3.4.2-3_hppa.deb ab27d22cff05ce54178ff304a571c1f47d3f362227b86e9e1c6234349fa63b02 1722044 ecj-gcj_3.4.2-3_hppa.deb Files: 9165567faf3dd5d3a769c992d766f484 1306 devel optional ecj_3.4.2-3.dsc d0965e754c09882c050f30e6176498be 26018 devel optional ecj_3.4.2-3.diff.gz 260fce5a54198da06fc8a7a2209f90d2 1215734 libs optional libecj-java_3.4.2-3_all.deb ae30919b66634161f9b31e56716bc57c 13868 devel optional ecj_3.4.2-3_hppa.deb f238a4b3ebb992fe679d507872a0ea3d 2109958 libs optional libecj-java-gcj_3.4.2-3_hppa.deb de99e5235528a12f40fe60ad28836b8d 1722044 devel optional ecj-gcj_3.4.2-3_hppa.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn252gACgkQStlRaw+TLJxwjACgxG31gIdNoSU/Tqq4lsxrT37I BlMAoLfXGsUesaCkLdKpIlftl9SE5cfC =iQQR -END PGP SIGNATURE- Accepted: ecj-gcj_3.4.2-3_hppa.deb to pool/main/e/ecj/ecj-gcj_3.4.2-3_hppa.deb ecj_3.4.2-3.diff.gz to pool/main/e/ecj/ecj_3.4.2-3.diff.gz ecj_3.4.2-3.dsc to pool/main/e/ecj/ecj_3.4.2-3.dsc ecj_3.4.2-3_hppa.deb to pool/main/e/ecj/ecj_3.4.2-3_hppa.deb libecj-java-gcj_3.4.2-3_hppa.deb to pool/main/e/ecj/libecj-java-gcj_3.4.2-3_hppa.deb libecj-java_3.4.2-3_all.deb to pool/main/e/ecj/libecj-java_3.4.2-3_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted xymon 4.3.0~beta2.dfsg-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 12:49:05 +0200 Source: xymon Binary: xymon xymon-client hobbit hobbit-client Architecture: source all amd64 Version: 4.3.0~beta2.dfsg-1 Distribution: unstable Urgency: low Maintainer: Christoph Berg m...@debian.org Changed-By: Christoph Berg m...@debian.org Description: hobbit - dummy package for transitioning from Hobbit to Xymon hobbit-client - dummy package for transitioning from Hobbit to Xymon xymon - monitoring system for systems, networks and applications xymon-client - client for the Xymon network monitor Closes: 497819 511560 521045 525347 Changes: xymon (4.3.0~beta2.dfsg-1) unstable; urgency=low . * New upstream release candidate. (Closes: #497819, #511560) * Rebuilding fixes librrd dependency. (Closes: #521045) * Forbid parallel building. * init scripts create /var/run/hobbit if missing. By Axel Beckert. * init scripts properly support 'status'. By Peter Eisentraut. (Closes: #525347) * Uploading to unstable, and adding transitional packages replacing hobbit and hobbit-client. Checksums-Sha1: bf8ebdea562fd1eedefbc8e7b54d4dd522457662 1309 xymon_4.3.0~beta2.dfsg-1.dsc da7e5fab86b4620f0040975f1fb9050198084557 2400680 xymon_4.3.0~beta2.dfsg.orig.tar.gz 9398ceed4b4b316450d086e8598d6506da48874b 31890 xymon_4.3.0~beta2.dfsg-1.diff.gz 9794e28ab250c7b668a1965fe24c8fe98709 7712 hobbit_4.3.0~beta2.dfsg-1_all.deb 7c4d0eb52e6705d036a1d9eb519dd31b6416f722 7728 hobbit-client_4.3.0~beta2.dfsg-1_all.deb 6cabec77b4f9a7ed0b578016c3b5247e68204af3 4050302 xymon_4.3.0~beta2.dfsg-1_amd64.deb ba7f1be6dbd88b30651133bf42bcade10b0475ba 414934 xymon-client_4.3.0~beta2.dfsg-1_amd64.deb Checksums-Sha256: 33847f837b61e3bad3208980de73f95c3796864c05478f830468fe659f67d611 1309 xymon_4.3.0~beta2.dfsg-1.dsc a17b854df547cd2bba420f11b64ef3f040e5aed190d19918d5bd97ae573b30bf 2400680 xymon_4.3.0~beta2.dfsg.orig.tar.gz 4c465559a00b375263003a8be9171fa334bf7760dcd4b02541177a367bff924b 31890 xymon_4.3.0~beta2.dfsg-1.diff.gz a698b5b4e45f0b59600e881275e28a57f39d3c9ac9a873b25234b1af8a0aa10a 7712 hobbit_4.3.0~beta2.dfsg-1_all.deb ac51e16acea5be7a71f506d42314de233f10392bcd66c9ab75e71a9ed8646145 7728 hobbit-client_4.3.0~beta2.dfsg-1_all.deb 30557879dc528c534578e99aba2d9162ecca04bded0af7d6a952223e8a649cab 4050302 xymon_4.3.0~beta2.dfsg-1_amd64.deb 0bbc9841eab93332b65e54d59aadd9869195ecfc493f2afe2c759d92cdc700b3 414934 xymon-client_4.3.0~beta2.dfsg-1_amd64.deb Files: 71507ca053e4b8fbd3ec325ad9136a3f 1309 net extra xymon_4.3.0~beta2.dfsg-1.dsc 8347c3d56f4997d2cba6513ec7579779 2400680 net extra xymon_4.3.0~beta2.dfsg.orig.tar.gz 6e7d75a2c02c1b7edd3027abeada870a 31890 net extra xymon_4.3.0~beta2.dfsg-1.diff.gz f1e2b5c87e7c356a581ca6c2fa255ad8 7712 net extra hobbit_4.3.0~beta2.dfsg-1_all.deb e5400711de309f3b232b799d3ba6f4bf 7728 net extra hobbit-client_4.3.0~beta2.dfsg-1_all.deb 779c80fa543019623f16f47a62310868 4050302 net extra xymon_4.3.0~beta2.dfsg-1_amd64.deb 09e7783050d11d29a9d2593c55ab3def 414934 net extra xymon-client_4.3.0~beta2.dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn2568ACgkQxa93SlhRC1pbsQCgxkK1hRIjg3Zhoff0mzyTJymp 3wAAnilMCvzAjQNnKSFU8xWQddkSpjm8 =5a6L -END PGP SIGNATURE- Accepted: hobbit-client_4.3.0~beta2.dfsg-1_all.deb to pool/main/x/xymon/hobbit-client_4.3.0~beta2.dfsg-1_all.deb hobbit_4.3.0~beta2.dfsg-1_all.deb to pool/main/x/xymon/hobbit_4.3.0~beta2.dfsg-1_all.deb xymon-client_4.3.0~beta2.dfsg-1_amd64.deb to pool/main/x/xymon/xymon-client_4.3.0~beta2.dfsg-1_amd64.deb xymon_4.3.0~beta2.dfsg-1.diff.gz to pool/main/x/xymon/xymon_4.3.0~beta2.dfsg-1.diff.gz xymon_4.3.0~beta2.dfsg-1.dsc to pool/main/x/xymon/xymon_4.3.0~beta2.dfsg-1.dsc xymon_4.3.0~beta2.dfsg-1_amd64.deb to pool/main/x/xymon/xymon_4.3.0~beta2.dfsg-1_amd64.deb xymon_4.3.0~beta2.dfsg.orig.tar.gz to pool/main/x/xymon/xymon_4.3.0~beta2.dfsg.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted argyll 1.0.3-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 11:20:41 +0200 Source: argyll Binary: argyll Architecture: source i386 Version: 1.0.3-6 Distribution: unstable Urgency: low Maintainer: Roland Mas lola...@debian.org Changed-By: Roland Mas lola...@debian.org Description: argyll - Color Management System, calibrator and profiler Closes: 524972 Changes: argyll (1.0.3-6) unstable; urgency=low . * argyll-firmware-spyder2 is now generated as section non-free/graphics rather than just graphics. * Removed non-free RFC from source package (closes: #524972). Checksums-Sha1: 89ed1d1d4ff863339e2f2d71fd75fd204de40e46 1291 argyll_1.0.3-6.dsc c7cce43d4696649f1e4974a1801e9b409ef21ace 24129 argyll_1.0.3-6.diff.gz be851272f924b6fe04732bf75e14b0bed4b306da 9759598 argyll_1.0.3-6_i386.deb Checksums-Sha256: f6bb60e7aea9628820c366ae5b49b44dd600f34217ed97d48e9ea798dd203a0e 1291 argyll_1.0.3-6.dsc bf12c673321011c4499545c8c993d24608c5b3355721aef1c8c419a43d82d331 24129 argyll_1.0.3-6.diff.gz 7d668feb2f89681ce7838deaa554ffc24651566145a08e224f5c410b1f84e3df 9759598 argyll_1.0.3-6_i386.deb Files: 6419be2393a1d4d5d8de1f9c0994f88f 1291 graphics optional argyll_1.0.3-6.dsc 56ae9702707a952119444c12397a1d51 24129 graphics optional argyll_1.0.3-6.diff.gz 8bcad2b9722f45810ce73381d3b2e6c0 9759598 graphics optional argyll_1.0.3-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9s78DqdWtRRIQ/URAim8AJ9XYXH4GW8H9WVVzQxndNVqBeeXXwCfUYNQ BumIuNkZrkTHfbscYEnypSI= =40dp -END PGP SIGNATURE- Accepted: argyll_1.0.3-6.diff.gz to pool/main/a/argyll/argyll_1.0.3-6.diff.gz argyll_1.0.3-6.dsc to pool/main/a/argyll/argyll_1.0.3-6.dsc argyll_1.0.3-6_i386.deb to pool/main/a/argyll/argyll_1.0.3-6_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libgems-ruby 1.3.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 28 Apr 2009 21:18:02 +0900
Source: libgems-ruby
Binary: rubygems1.8 rubygems1.9 rubygems rubygems-doc
Architecture: source all
Version: 1.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Daigo Moriwaki da...@debian.org
Changed-By: Daigo Moriwaki da...@debian.org
Description:
rubygems - package management framework for Ruby libraries/applications
rubygems-doc - package management framework for Ruby libraries/applications
rubygems1.8 - package management framework for Ruby libraries/applications
rubygems1.9 - package management framework for Ruby libraries/applications
Changes:
libgems-ruby (1.3.2-1) unstable; urgency=low
.
[ Daigo Moriwaki ]
* New upstream release.
* debian/control:
- Bumped up the Standards-Version to 3.8.1.
- Depend ${misc:Depends} as well.
* debian/rules:
- Removed a deprecated dependency to a 'TODO' file.
* Bumped up the compat level to 7.
- debian/compat
- debian/control.
.
[ Gunnar Wolf ]
* Changed section to Ruby as per ftp-masters' request
Checksums-Sha1:
6bcab651db03f3a8d086fdce4f076d3d29349675 1394 libgems-ruby_1.3.2-1.dsc
9514b271e8d0e940b76a1931df18c16a68f7214c 288798 libgems-ruby_1.3.2.orig.tar.gz
cf0f1175eea83bda1e263c353e94dca9f20b2b67 11153 libgems-ruby_1.3.2-1.diff.gz
d64ec258b9768e871923acd2a8d2085da5458b87 187022 rubygems1.8_1.3.2-1_all.deb
f00348c11c43e630402263059a4bc6935804eb72 186176 rubygems1.9_1.3.2-1_all.deb
1033bfe3b1956a80d32e5df6fc8111ccf359788a 61952 rubygems_1.3.2-1_all.deb
a068008bdf204baac32be0ad50f026b582dbee7c 308230 rubygems-doc_1.3.2-1_all.deb
Checksums-Sha256:
83887e3d7270d5b5ac69b9c1157d032da1f61b68dbeda0e4e965fb70c758137d 1394
libgems-ruby_1.3.2-1.dsc
ab0ceaf85a6463f5408c46fa637a5eff0971427403be9f725e1751d2019f925e 288798
libgems-ruby_1.3.2.orig.tar.gz
29ad575ac67c179df597a0c78a61b6037dd02c2fd41e158bd5ba4057144e52bc 11153
libgems-ruby_1.3.2-1.diff.gz
f9aca16783eb55c4459fe74552422623e5ada31db23d35a3cf6811eb5dd6c574 187022
rubygems1.8_1.3.2-1_all.deb
36d7704e804070c63518a3cf1d75ab4bc488fab1e89833e08c438d43721aae07 186176
rubygems1.9_1.3.2-1_all.deb
652ab9da721afbe3beeeb670fbdb1e1c96ba72927341d89ff127592b674c13a2 61952
rubygems_1.3.2-1_all.deb
3fc64aa35e7c408b984ec99138f542b86182633632b132304335da0e76eb38c2 308230
rubygems-doc_1.3.2-1_all.deb
Files:
f55938d7b20dfce988de780ae2a3019c 1394 ruby optional libgems-ruby_1.3.2-1.dsc
6204d0a4c526a1d8fdbce746647b179a 288798 ruby optional
libgems-ruby_1.3.2.orig.tar.gz
2b2f6dcf2c419531f64266f178c69414 11153 ruby optional
libgems-ruby_1.3.2-1.diff.gz
fa1ee25e62997fa086db9b0508f91974 187022 ruby optional
rubygems1.8_1.3.2-1_all.deb
46bc4d03cc6d7396f362694f5222942a 186176 ruby optional
rubygems1.9_1.3.2-1_all.deb
94f0feaf9bd1bb839fd6543e26302103 61952 ruby optional rubygems_1.3.2-1_all.deb
d5632512289bda2a0f5a635a47380343 308230 doc optional
rubygems-doc_1.3.2-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkn29osACgkQNcPj+ukc0lCFnQCgtgcLUqGZC8/OzoA/kPF3nsYr
R+gAoLlLeguhw5w6MdKk3FjSjYSM9Ewd
=Fur1
-END PGP SIGNATURE-
Accepted:
libgems-ruby_1.3.2-1.diff.gz
to pool/main/libg/libgems-ruby/libgems-ruby_1.3.2-1.diff.gz
libgems-ruby_1.3.2-1.dsc
to pool/main/libg/libgems-ruby/libgems-ruby_1.3.2-1.dsc
libgems-ruby_1.3.2.orig.tar.gz
to pool/main/libg/libgems-ruby/libgems-ruby_1.3.2.orig.tar.gz
rubygems-doc_1.3.2-1_all.deb
to pool/main/libg/libgems-ruby/rubygems-doc_1.3.2-1_all.deb
rubygems1.8_1.3.2-1_all.deb
to pool/main/libg/libgems-ruby/rubygems1.8_1.3.2-1_all.deb
rubygems1.9_1.3.2-1_all.deb
to pool/main/libg/libgems-ruby/rubygems1.9_1.3.2-1_all.deb
rubygems_1.3.2-1_all.deb
to pool/main/libg/libgems-ruby/rubygems_1.3.2-1_all.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted bird 1.0.14-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 14:48:36 +0200 Source: bird Binary: bird Architecture: source amd64 Version: 1.0.14-1 Distribution: unstable Urgency: low Maintainer: Ondřej Surý ond...@debian.org Changed-By: Ondřej Surý ond...@debian.org Description: bird - Internet Routing Daemon Changes: bird (1.0.14-1) unstable; urgency=low . * New Upstream Version Checksums-Sha1: 865c18be7c9f0770956337c73587ccc8fc5c76fd 989 bird_1.0.14-1.dsc 4cffcab9725ae8bf1257809a2b799464a0706b9a 614240 bird_1.0.14.orig.tar.gz 981332565754407fba35b6cde4cafaf6ccc0fee8 5233 bird_1.0.14-1.diff.gz 119040f8ac5c3b8922c23fa160ab832d07ab5116 291922 bird_1.0.14-1_amd64.deb Checksums-Sha256: 78b6ebde78e62a364e2110bf70904a2b3b18c254510ffdd4f583ba4fb39a8ddc 989 bird_1.0.14-1.dsc db60c097697d9343af244641b23a53b6cd7ef071e462b69a111d02f0db021989 614240 bird_1.0.14.orig.tar.gz 206a6031d82f649c518cd1f57a62979f19f2610d26ffdc3882beb40a537828c6 5233 bird_1.0.14-1.diff.gz f776513b23f2930d1a92d60f1e1873ccec35b0dd19cdb7e1ea7977da07e6ee14 291922 bird_1.0.14-1_amd64.deb Files: 999f3c688e0f40c7cc21de9a5cb80aca 989 net extra bird_1.0.14-1.dsc e2e390017c9641c1e56bb11946109b2d 614240 net extra bird_1.0.14.orig.tar.gz 70e2b6e273c1ce15126fef209397b82f 5233 net extra bird_1.0.14-1.diff.gz 8615e989a9b0002e29897d76fe99a2d9 291922 net extra bird_1.0.14-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3AjwACgkQ9OZqfMIN8nNUagCgnm81sc/wL3F6Gt+RPB8EoCdF u4gAnA+f7G/6krt1AczXMKXTXPdmTXIw =YtTO -END PGP SIGNATURE- Accepted: bird_1.0.14-1.diff.gz to pool/main/b/bird/bird_1.0.14-1.diff.gz bird_1.0.14-1.dsc to pool/main/b/bird/bird_1.0.14-1.dsc bird_1.0.14-1_amd64.deb to pool/main/b/bird/bird_1.0.14-1_amd64.deb bird_1.0.14.orig.tar.gz to pool/main/b/bird/bird_1.0.14.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted padre 0.34-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 16:21:53 +0300 Source: padre Binary: padre libwx-perl-dialog-perl Architecture: source all Version: 0.34-1 Distribution: unstable Urgency: low Maintainer: Damyan Ivanov d...@debian.org Changed-By: Damyan Ivanov d...@debian.org Description: libwx-perl-dialog-perl - abstract dialog class for simple dialog creation padre - Perl Application Development and Refactoring Environment Changes: padre (0.34-1) unstable; urgency=low . * New upstream release . * bump liborlite-perl (build-)dependency to 1.20 * bump liborlite-migrate-perl (build-)dependency to 0.03 * refresh patches Checksums-Sha1: 5c5ccf6acf5f864e986281540494fcbd7b2d09c0 2404 padre_0.34-1.dsc be9eaefceefb75167b93f09dac23a4bbeff59adb 517778 padre_0.34.orig.tar.gz 865c357c15094d5c2c543e9b1400ad2eb3f89261 6432 padre_0.34-1.diff.gz f9b4967c151faeac712275e812f1cf32baad45a1 504682 padre_0.34-1_all.deb 76213c7db6beb40ae7ad6ebf079dc701ca652cf0 31970 libwx-perl-dialog-perl_0.34-1_all.deb Checksums-Sha256: bf98ea24abc63366a1e295c35e44cec03fb781e4cbad4947e60ac64f77a5d5ec 2404 padre_0.34-1.dsc 4451760f14a6b7a32c236d2c5b3ae47458507970c69bd391c3b55ce91c3d3df3 517778 padre_0.34.orig.tar.gz 4cb8dd30c898e9e9d1e4ddda247dd3346ad87fa23bf46039011dcdb97923e76a 6432 padre_0.34-1.diff.gz 84862f66fb82a1590edcf3b64970f8f8b859a85c6ddcd551772467eb42cbf126 504682 padre_0.34-1_all.deb c759df782d8400f513049f3109eea4a751f312eb02331d3ef89da69966637924 31970 libwx-perl-dialog-perl_0.34-1_all.deb Files: 6e40378974faa2c7c53d5e5a3c7b442f 2404 perl optional padre_0.34-1.dsc 041a253f61e7454564c3d8b1afae2b23 517778 perl optional padre_0.34.orig.tar.gz 427da275fc523b43d919b59a7db679bf 6432 perl optional padre_0.34-1.diff.gz b7cb68ad1b8d9983fcacee1a0f5989f6 504682 perl optional padre_0.34-1_all.deb 8652cfce35078c1d6b07a6b99b6e57c8 31970 perl optional libwx-perl-dialog-perl_0.34-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3BCkACgkQHqjlqpcl9jvyOACeMNXf4iA9AYp6WOL+A09V4+ge 28wAn0JILQX0KQwCpmALto1QR79jwycR =NCtW -END PGP SIGNATURE- Accepted: libwx-perl-dialog-perl_0.34-1_all.deb to pool/main/p/padre/libwx-perl-dialog-perl_0.34-1_all.deb padre_0.34-1.diff.gz to pool/main/p/padre/padre_0.34-1.diff.gz padre_0.34-1.dsc to pool/main/p/padre/padre_0.34-1.dsc padre_0.34-1_all.deb to pool/main/p/padre/padre_0.34-1_all.deb padre_0.34.orig.tar.gz to pool/main/p/padre/padre_0.34.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted scilab 5.1.1-3 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 27 Apr 2009 14:51:57 +0200 Source: scilab Binary: scilab scilab-data scilab-include scilab-bin libscilab-java scilab-doc scilab-doc-fr scilab-test Architecture: source all i386 Version: 5.1.1-3 Distribution: unstable Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylvestre.le...@inria.fr Description: libscilab-java - Scientific software package for numerical computations (Java API) scilab - Scientific software package for numerical computations scilab-bin - Scientific software package for numerical computations (binary fi scilab-data - Scientific software package for numerical computations (data file scilab-doc - Scientific software package for numerical computations (documenta scilab-doc-fr - Scientific software package for numerical computations (french do scilab-include - Scientific software package for numerical computations (include f scilab-test - Scientific software package for numerical computations (test file Closes: 525935 Changes: scilab (5.1.1-3) unstable; urgency=low . * Fix warnings in the manpages (modelicac.1 scilab.1) * Fix a few typo in the code (typo.diff) * Remove some exit() in some libs of Scilab (exitincode.diff) * Encoding removed from scilab.desktop (it is now the default encoding) * call_scilab documentation was not correctly loaded (missingaddchapter.diff) * change of the order of the dependencies of the numerical deps (didn't work buildd) (Closes: #525935) * Build-dep atlas3-base-dev renamed to libatlas-base-dev Checksums-Sha1: f43db71b7bf674cc227bb74216909b1f7abb32d7 1952 scilab_5.1.1-3.dsc 02e4d9524faa9da958661b3871e948cd27a3637c 62184 scilab_5.1.1-3.diff.gz a0e8603403ea36c23ac3709d4abbf8b66a191992 214882 scilab_5.1.1-3_all.deb 143c3c2ddf28fe49cf8d61d1acdb9dab3c72937f 11033896 scilab-data_5.1.1-3_all.deb 7b85c5e37e6483c5411f40337db8f3c18c2a0de4 209550 scilab-include_5.1.1-3_all.deb f23005593f23e7e9305b9a8a060645a77be3cb67 7050424 scilab-doc_5.1.1-3_all.deb 02c8e5bf5967d4331c251485ca38d33292c2c6bb 6522382 scilab-doc-fr_5.1.1-3_all.deb f868dde827412b72f344e440ae3740872f458f19 18603910 scilab-test_5.1.1-3_all.deb 7154f0d259a4ab9fb1a0ca0675a5138c53b6403f 4192018 scilab-bin_5.1.1-3_i386.deb 88d7ff9e5da792e3ab9e5d62dcb2440bd0701040 37022 libscilab-java_5.1.1-3_i386.deb Checksums-Sha256: e1231db958f7c58bf8ae066df08542dfa35476ce87b2258116a44cdc1be01d6a 1952 scilab_5.1.1-3.dsc 0ce81d6af2c20b90f2e24bf893edd1dd7fd42c918f8bb9f433b998c32d82e048 62184 scilab_5.1.1-3.diff.gz 4e2a950789ca5ee416d591548d91cb99a0d1b8f9f677935ada855f8c7e8f705f 214882 scilab_5.1.1-3_all.deb c36190ded8579529a44a27f1e567ee792ca1aa1f63e423e1ccfed0cbdab65387 11033896 scilab-data_5.1.1-3_all.deb 32b88d2d5388183f954712c9e2b426d1cdd9851221e71d59aca1e5181d79050e 209550 scilab-include_5.1.1-3_all.deb beaf8717fb3f04c83b0d569026fa33359c3ff4b7e62ca498175aafb6f0c04364 7050424 scilab-doc_5.1.1-3_all.deb 023de9122f75908a1c2e36a1a4dfadca59891dd59937042145e9d0d28c9738bb 6522382 scilab-doc-fr_5.1.1-3_all.deb ad63aaf13b5a50b09f39367441d9122ee77a49dbc150392e80be64bf4c2e6684 18603910 scilab-test_5.1.1-3_all.deb ee26241ac1e255e3f46d05697720c5fd6c167f7be98ec8e09b2fb32c88a339a4 4192018 scilab-bin_5.1.1-3_i386.deb 6cf22d1f6824babf7efc189769bd74c0a6cd8bdebeb094c8032ba89fd3902c5c 37022 libscilab-java_5.1.1-3_i386.deb Files: 10fb27a8ee03a9d4b219084db0515d3b 1952 math optional scilab_5.1.1-3.dsc 7f11dcb7e1b3a72bc3d01af547018cc1 62184 math optional scilab_5.1.1-3.diff.gz e1acc533d4b984037b8ea5a05c2f2766 214882 math optional scilab_5.1.1-3_all.deb cc4f7750c49411798dec4246cc526990 11033896 math optional scilab-data_5.1.1-3_all.deb 67373567274a06e24aac2f0d8abffada 209550 math optional scilab-include_5.1.1-3_all.deb 1eb2f0f49d1e3fbc90493c30ec357041 7050424 doc optional scilab-doc_5.1.1-3_all.deb 6aea79f0ce42c40a717e572793b7d9c4 6522382 doc optional scilab-doc-fr_5.1.1-3_all.deb e0c91eaa67f351d1f90a177643ebaf77 18603910 math optional scilab-test_5.1.1-3_all.deb 90b8c42871096a2afa8f7f65c7ee0aeb 4192018 math optional scilab-bin_5.1.1-3_i386.deb a647bec0ccc7b8318489883e9906957b 37022 java optional libscilab-java_5.1.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEUEARECAAYFAkn2/cQACgkQiOXXM92JlhCRiwCgnIr5+FHpUSwj4Sbt+QJ4ynGj u7wAljB6oV+JEYAOsS2TsCcJT6z0j24= =+Fd6 -END PGP SIGNATURE- Accepted: libscilab-java_5.1.1-3_i386.deb to pool/main/s/scilab/libscilab-java_5.1.1-3_i386.deb scilab-bin_5.1.1-3_i386.deb to pool/main/s/scilab/scilab-bin_5.1.1-3_i386.deb scilab-data_5.1.1-3_all.deb to pool/main/s/scilab/scilab-data_5.1.1-3_all.deb scilab-doc-fr_5.1.1-3_all.deb to pool/main/s/scilab/scilab-doc-fr_5.1.1-3_all.deb scilab-doc_5.1.1-3_all.deb to pool/main/s/scilab/scilab-doc_5.1.1-3_all.deb scilab-include_5.1.1-3_all.deb to
Accepted rcmdr 1.4-10-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 08:13:40 -0500 Source: rcmdr Binary: r-cran-rcmdr Architecture: source all Version: 1.4-10-2 Distribution: unstable Urgency: low Maintainer: Dirk Eddelbuettel e...@debian.org Changed-By: Dirk Eddelbuettel e...@debian.org Description: r-cran-rcmdr - GNU R platform-independent basic-statistics GUI Closes: 525971 Changes: rcmdr (1.4-10-2) unstable; urgency=low . * debian/rules: Set mode of Rcmdr/etc/linux/Rcmdr.sh to 0755 (Closes: #525971) Checksums-Sha1: 79006bd08240171eddc0fb7ce2519ee922819f52 974 rcmdr_1.4-10-2.dsc aeb752adfe1866ce7ed3599e3bd233ec6e4579f0 4568 rcmdr_1.4-10-2.diff.gz 28eb0a71f3038b33a400d08e25f9f9bc6309fac3 2285000 r-cran-rcmdr_1.4-10-2_all.deb Checksums-Sha256: 202eea8a00d691cff074b560cbe740e6eea4d0f7ccd8da38f4d030170050d05e 974 rcmdr_1.4-10-2.dsc a4d7d06552692bd8779c81d3b8b16431b6de5df67db2b6c300b4f3c75c4379d6 4568 rcmdr_1.4-10-2.diff.gz 92c1e156e4320cdc770ae4755cd2284f9200607ab2b01349af14afb19ff867c9 2285000 r-cran-rcmdr_1.4-10-2_all.deb Files: 3a056ba4bc6cba3a3be03e181102dfb1 974 gnu-r optional rcmdr_1.4-10-2.dsc 794f2ac10c0398821162b46d07067a05 4568 gnu-r optional rcmdr_1.4-10-2.diff.gz f2656d69654de4e84be3a8632d5f9288 2285000 gnu-r optional r-cran-rcmdr_1.4-10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9wWHCZSR95Gw07cRAqK4AKCWEXXOi4mWUkmSzemjfmDRoKIN0ACgk+L3 NUXCX0X5TABw7+Ab5ERVAnM= =FzZy -END PGP SIGNATURE- Accepted: r-cran-rcmdr_1.4-10-2_all.deb to pool/main/r/rcmdr/r-cran-rcmdr_1.4-10-2_all.deb rcmdr_1.4-10-2.diff.gz to pool/main/r/rcmdr/rcmdr_1.4-10-2.diff.gz rcmdr_1.4-10-2.dsc to pool/main/r/rcmdr/rcmdr_1.4-10-2.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted gforge 4.8~rc1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 15:33:18 +0200 Source: gforge Binary: gforge gforge-common gforge-web-apache2 gforge-web-apache gforge-db-postgresql gforge-mta-exim4 gforge-mta-postfix gforge-mta-courier gforge-shell-postgresql gforge-ftp-proftpd gforge-dns-bind9 gforge-lists-mailman gforge-plugin-scmcvs gforge-plugin-scmsvn gforge-plugin-mediawiki Architecture: source all Version: 4.8~rc1-1 Distribution: experimental Urgency: low Maintainer: Roland Mas lola...@debian.org Changed-By: Roland Mas lola...@debian.org Description: gforge - collaborative development tool - metapackage gforge-common - collaborative development tool - shared files gforge-db-postgresql - collaborative development tool - database (using PostgreSQL) gforge-dns-bind9 - collaborative development tool - DNS management (using Bind9) gforge-ftp-proftpd - collaborative development tool - FTP management (using ProFTPd) gforge-lists-mailman - collaborative development tool - mailing-lists (using Mailman) gforge-mta-courier - collaborative development tool - mail tools (using Courier) gforge-mta-exim4 - collaborative development tool - mail tools (using Exim 4) gforge-mta-postfix - collaborative development tool - mail tools (using Postfix) gforge-plugin-mediawiki - Mediawiki plugin for FusionForge gforge-plugin-scmcvs - collaborative development tool - CVS plugin gforge-plugin-scmsvn - collaborative development tool - Subversion plugin gforge-shell-postgresql - collaborative development tool - shell accounts (using PostgreSQL gforge-web-apache - transition package to gforge-web-apache2 gforge-web-apache2 - collaborative development tool - web part (using Apache) Changes: gforge (4.8~rc1-1) experimental; urgency=low . [ Christian Bayle ] * Removed all files from /usr/lib/gforge and put them in /usr/share/gforge * cron scripts ar now in /usr/share/gforge/cronjobs * Now generate *.cron.d *.dirs *.install from cron.d/dirs/install dirs * Use dh_install instead of copy in rules . [ Roland Mas ] * Fixed a bunch of lintian warnings. * Added logrotate configuration file for vhosts access logs. * New upstream release candidate. Checksums-Sha1: 57a09b0c03be70115683bcfe723abce1a6b3aaac 1463 gforge_4.8~rc1-1.dsc c5911f9618bd5140b2d764bf255f409747ba4e56 10910948 gforge_4.8~rc1.orig.tar.gz 2f715947f5329a86bd0be5ac40490d1e7bba3f29 3021 gforge_4.8~rc1-1.diff.gz e1a8bff729f06bf25475fe2ed53a96b7d8af6855 94484 gforge_4.8~rc1-1_all.deb a8fded4c6455c8595dbc318a3d2ed22bb6738e05 109 gforge-common_4.8~rc1-1_all.deb d7056ac95d379921a8b8788d8ad3f48ce68f3fe5 1325394 gforge-web-apache2_4.8~rc1-1_all.deb 89b12d1ccf0eb63338d4bbc84992040e46581047 90142 gforge-web-apache_4.8~rc1-1_all.deb 0f5075068c3cd31a8064113931cb6016b4e432cf 234158 gforge-db-postgresql_4.8~rc1-1_all.deb 76f2d63f70b0ee3dff112cb8c55741b52b0116f4 102430 gforge-mta-exim4_4.8~rc1-1_all.deb 5f6e00e0727f93348fc3c4d18389dd4551877b33 103334 gforge-mta-postfix_4.8~rc1-1_all.deb b94fd09eda5a06557cac668073284f1af26d7de1 90412 gforge-mta-courier_4.8~rc1-1_all.deb aeb46feb2339aa678b1ee3d4a4b30a9daa2e3268 96502 gforge-shell-postgresql_4.8~rc1-1_all.deb e9ad027f784742f0d1e132a1686f3b5fefb2ebcb 97282 gforge-ftp-proftpd_4.8~rc1-1_all.deb a13c207f7cde06edb8961ef2d14ed19d1f00099e 108788 gforge-dns-bind9_4.8~rc1-1_all.deb 365ece08339a93b397cb0554a98071058afa2b8a 96258 gforge-lists-mailman_4.8~rc1-1_all.deb 469939091ebaa80cce4d9bfb945905062298063b 122064 gforge-plugin-scmcvs_4.8~rc1-1_all.deb 03ac0ab12ce9cad7fa541d846bf25443aaa6bd08 119638 gforge-plugin-scmsvn_4.8~rc1-1_all.deb a54a8dd341c87fc07c5e5588ef4a42b312785dbd 215352 gforge-plugin-mediawiki_4.8~rc1-1_all.deb Checksums-Sha256: c40474e488f1829aad3541b941b0cdc968d7c92777bd06b659cb02cc5d9f3102 1463 gforge_4.8~rc1-1.dsc c5c576e0a88f443907d8c61706dfb53ce843e12d50135766488dfa3ecb5c0e44 10910948 gforge_4.8~rc1.orig.tar.gz 2141104d431a7bd3d1ec897733093fef437015ae96fa2529a0b80012025171bb 3021 gforge_4.8~rc1-1.diff.gz a48d8acda6c6489c59caab20f4bdc72c2ea464390a6e2c3d187ab3df0bfe75b6 94484 gforge_4.8~rc1-1_all.deb d53b4c32575a418079f698f9555cc653563df155ad3d009da8f91790bc4c803d 109 gforge-common_4.8~rc1-1_all.deb 5803f84dc8245fd3d611e3da4ab5e8f6b4ca085af987d18703cfb53308b05a3e 1325394 gforge-web-apache2_4.8~rc1-1_all.deb c52aca635dff0686fbf6c957f71cba98b0a36a31d8bb9ed5e3b5b2106fcbf3c6 90142 gforge-web-apache_4.8~rc1-1_all.deb bff3f9050289744d3e24b5fbcc0d4cf9c590073069ca5481c853299c896b9039 234158 gforge-db-postgresql_4.8~rc1-1_all.deb 39c0d9c56ff513e26227c37fe2de418d2d892fc816aa1ec2f0212e1e9a28e007 102430 gforge-mta-exim4_4.8~rc1-1_all.deb 82988af39d4e74ee8b02d4665230c4c3cea049f4612a4fd066215da9d8e9a1b9 103334 gforge-mta-postfix_4.8~rc1-1_all.deb 77d8ed6edba7e7f8a4bab74ff750fd87191db1f91ec5ab345c1d920dad4f8dbc 90412 gforge-mta-courier_4.8~rc1-1_all.deb
Accepted ccstools 1.6.7-20090401-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 29 Apr 2009 00:10:39 +0900 Source: ccstools Binary: tomoyo-ccstools Architecture: source i386 Version: 1.6.7-20090401-2 Distribution: unstable Urgency: low Maintainer: Hideki Yamane (Debian-JP) henr...@debian.or.jp Changed-By: Hideki Yamane (Debian-JP) henr...@debian.or.jp Description: tomoyo-ccstools - Lightweight and easy-use Mandatory Access Control for Linux Changes: ccstools (1.6.7-20090401-2) unstable; urgency=low . * debian/control: - Build-Depends: dpatch - Architecture: any * debian/rules: - add include /usr/share/dpatch/dpatch.make * debian/patches/typo.dpatch - fix spelling-error-in-binary, thanks to lintian. Checksums-Sha1: 9fc8999e75512b1ab8d66184ff3be6d05c243072 1140 ccstools_1.6.7-20090401-2.dsc f7b3fa313b06b7e8cc6286d89872007a9baea312 6819 ccstools_1.6.7-20090401-2.diff.gz b552852813cacca55151604c97388e2aa3d7cd33 119728 tomoyo-ccstools_1.6.7-20090401-2_i386.deb Checksums-Sha256: d8eae03de58ce267acb1b7aa897b772a961ec2c763c5a13640da21a0e30f42f9 1140 ccstools_1.6.7-20090401-2.dsc bf35648442eeb280f9ee98682ca0873c2bc19717e0c7fe6afd8e28310408f921 6819 ccstools_1.6.7-20090401-2.diff.gz 493b8ac3ad7f0f3c4f29c118a2032c16317c1248fc69e55af80f40d10534b2bc 119728 tomoyo-ccstools_1.6.7-20090401-2_i386.deb Files: 747107fbafbaf7170d4aca1edfe0d023 1140 admin extra ccstools_1.6.7-20090401-2.dsc a6521d4d041eb62d80437f8ad1217572 6819 admin extra ccstools_1.6.7-20090401-2.diff.gz 1730e9bea6401b638587feeaae6b6b30 119728 admin extra tomoyo-ccstools_1.6.7-20090401-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3HqQACgkQIu0hy8THJkvBgACgsvaZ4IAt3EfFf/Q5hOFN1EKi sdgAoLOoWdrAxqocBFTe0s10GeL7V8lv =+1tX -END PGP SIGNATURE- Accepted: ccstools_1.6.7-20090401-2.diff.gz to pool/main/c/ccstools/ccstools_1.6.7-20090401-2.diff.gz ccstools_1.6.7-20090401-2.dsc to pool/main/c/ccstools/ccstools_1.6.7-20090401-2.dsc tomoyo-ccstools_1.6.7-20090401-2_i386.deb to pool/main/c/ccstools/tomoyo-ccstools_1.6.7-20090401-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted doxygen 1.5.8-1.1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 13:01:30 + Source: doxygen Binary: doxygen doxygen-gui doxygen-doc Architecture: source i386 all Version: 1.5.8-1.1 Distribution: unstable Urgency: low Maintainer: Matthias Klose d...@debian.org Changed-By: Margarita Manterola ma...@debian.org Description: doxygen- Documentation system for C, C++, Java, Python and other languages doxygen-doc - Documentation for doxygen doxygen-gui - GUI configuration tool for doxygen Closes: 518031 Changes: doxygen (1.5.8-1.1) unstable; urgency=low . * Non-maintainer upload to fix Segmentation Fault. * Applied patch from Gentoo to fix a Segmentation Fault as debian/patches/path-prefix.dpatch. Thanks to Martin von Gagern for the patch and Leandro Lucarella for the pointer. Closes: #518031 Checksums-Sha1: b9204746e40f511a3ea03b9124b73ed90b08adfb 1216 doxygen_1.5.8-1.1.dsc abfd5bfcb48738fa49b1dfb0029a4dd7ef183f6e 17525 doxygen_1.5.8-1.1.diff.gz d6734d9a2ded3e1487bbe9adbd2cf09c8b777fe4 1595650 doxygen_1.5.8-1.1_i386.deb bcecf4910a3ce472cd28d472b990a1d9381dbada 132494 doxygen-gui_1.5.8-1.1_i386.deb d6375b49dcd18625a957192b47d3f2b0bec4a010 1370834 doxygen-doc_1.5.8-1.1_all.deb Checksums-Sha256: 2ee14999f7c662c57d62acc33aa694803d27eed00b4e465a1b29e0ce2d574970 1216 doxygen_1.5.8-1.1.dsc e8fd1a008da38ddbb904fcc3b5805184e0539219bb556c63780c0b74dead3246 17525 doxygen_1.5.8-1.1.diff.gz 1e308d740daa03e9ef56fff4d29c548abed94ed94b1f2f7492ae61fd2f8c74e4 1595650 doxygen_1.5.8-1.1_i386.deb aef7a022fe2027a0fca77bc475519b19e614abba470454da350e56d48bb9f177 132494 doxygen-gui_1.5.8-1.1_i386.deb 78214d61485e62eea2ebe0077e76d5f0bd6e32df49ac520f0aba73c78a66414a 1370834 doxygen-doc_1.5.8-1.1_all.deb Files: 86d179f9c16f10420d2dafcad69b7261 1216 devel optional doxygen_1.5.8-1.1.dsc a8b36e46cfce71b265d53349e612d320 17525 devel optional doxygen_1.5.8-1.1.diff.gz 0c0927a5c2c7210681e9dc78f641cb5c 1595650 devel optional doxygen_1.5.8-1.1_i386.deb fb7e5e9a13f4b35b5101beb75c9c86b9 132494 devel optional doxygen-gui_1.5.8-1.1_i386.deb 161582e133ff6ce5d0cc403a9e331e32 1370834 doc optional doxygen-doc_1.5.8-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3HGwACgkQlAuUx1tI/65YjgCgqR4VOADCYjf5lHaaijlZ+9OQ wtAAn3/2p0PyBKjwOZhgbOoS/Xes7s/3 =Cuby -END PGP SIGNATURE- Accepted: doxygen-doc_1.5.8-1.1_all.deb to pool/main/d/doxygen/doxygen-doc_1.5.8-1.1_all.deb doxygen-gui_1.5.8-1.1_i386.deb to pool/main/d/doxygen/doxygen-gui_1.5.8-1.1_i386.deb doxygen_1.5.8-1.1.diff.gz to pool/main/d/doxygen/doxygen_1.5.8-1.1.diff.gz doxygen_1.5.8-1.1.dsc to pool/main/d/doxygen/doxygen_1.5.8-1.1.dsc doxygen_1.5.8-1.1_i386.deb to pool/main/d/doxygen/doxygen_1.5.8-1.1_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted bootcd 3.15 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Apr 2009 10:01:40 +0200 Source: bootcd Binary: bootcd bootcd-i386 bootcd-hppa bootcd-ia64 bootcd-mkinitramfs bootcd-backup Architecture: source all Version: 3.15 Distribution: unstable Urgency: low Maintainer: Bernd Schumacher bernd.schumac...@hp.com Changed-By: Bernd Schumacher bernd.schumac...@hp.com Description: bootcd - run your system from cd without need for disks bootcd-backup - tools to backup a Debian or alien Linux installation bootcd-hppa - bootcd extension to create images that can boot on parisc/hppa bootcd-i386 - bootcd extension to create images that can boot on i386 bootcd-ia64 - bootcd extension to create images that can boot on ia64 bootcd-mkinitramfs - initramfs extension for bootcd Changes: bootcd (3.15) unstable; urgency=low . * Fix return value of udev_fixnet in bootcd2disk. * Changed /usr/bin/mkisofs - genisoimage * Output of functions after_copy() and before_copy() defined in bootcd2disk.conf are not controlled with run anymore. * in bootcd2disk, the dd command now uses conf=notrunc to really wipe out the partition table * in bootcd2disk, if we get BLKRRPART: Device or resource busy the user is asked to reboot * in bootcd2disk.lib if we can not find a block device we will guess its name Checksums-Sha1: 6093dc6d0e625055187a0af37bf589c94f561842 761 bootcd_3.15.dsc 227b96eb8d8aff544df44c1daa000d70af0e649e 102448 bootcd_3.15.tar.gz eec21ac829dddeb75fc77845d033ea457983561b 77152 bootcd_3.15_all.deb bc53774c7bf216ca673b57695f6edcbcda1bab01 12984 bootcd-i386_3.15_all.deb 4d220e9cfa121a58594e1d96e6e58088e90408c5 12876 bootcd-hppa_3.15_all.deb ef7396e7e37ae1ca0b3a45091fbaf95101df5c65 13676 bootcd-ia64_3.15_all.deb 5b8de9c2a46a8c414d9807259b86876964158a4b 16902 bootcd-mkinitramfs_3.15_all.deb e92e8624bd37565e33bdfcf0231fd1b03891ba6e 42438 bootcd-backup_3.15_all.deb Checksums-Sha256: 5e0725f1bc2d4b7f3d40b0d95b9094ad9b6b86a24f7533374651a0c2d86fe933 761 bootcd_3.15.dsc 1e2954686b2e0e3bf0c4bbb1779676ca151b26ce1b67dbbbcff0f0911d834384 102448 bootcd_3.15.tar.gz e2a52bb00916fd04a22aabaf3e5f9ee16fc5bf13e271cde6d03ace7201ee0273 77152 bootcd_3.15_all.deb f9d5739636884350ea6c7103426e84afd7d3ade7606f18caeea1f46a9c9ca1d3 12984 bootcd-i386_3.15_all.deb 9ed046cf8610df8c2d94a96c18c94c55b05f2210dbfc655e303f77848dec60d3 12876 bootcd-hppa_3.15_all.deb 04d89213ab1868d47c68dd4ceb711905dd65fbb7276bbbec3289aac46baad7bd 13676 bootcd-ia64_3.15_all.deb f314c66d6c813474d70f5b35bb07e869143bdd818186da5992101156bb91f964 16902 bootcd-mkinitramfs_3.15_all.deb d05a2cc03c638f8dd9c14b8674a97c6196f1c99c20045c3a0c222042d43e86af 42438 bootcd-backup_3.15_all.deb Files: 751555eca0d563d60296facc84df0b89 761 utils extra bootcd_3.15.dsc ee14134b9f849878a8ea021c233973bb 102448 utils extra bootcd_3.15.tar.gz 51f92d64dda72e7019acc2073f1e912c 77152 utils extra bootcd_3.15_all.deb afd45a39545b820d9b938e46f0dca107 12984 utils extra bootcd-i386_3.15_all.deb 1c479b538d11fd9f98cf20314742101e 12876 utils extra bootcd-hppa_3.15_all.deb 928c2adce26262ed18675b83db90de60 13676 utils extra bootcd-ia64_3.15_all.deb 951c3f0b814f144a67dc9d6ec41505bb 16902 utils extra bootcd-mkinitramfs_3.15_all.deb 27a9a8ef38167600cc16b26fd8c24d6e 42438 utils extra bootcd-backup_3.15_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ9xnOINZoglnvXbwRAuJ5AJ9nHY2eggeP+p8z6etsmqiW2IT2yACfaOEp TYjOrHXdXtCpKu1ToUb8qCs= =Ti5c -END PGP SIGNATURE- Accepted: bootcd-backup_3.15_all.deb to pool/main/b/bootcd/bootcd-backup_3.15_all.deb bootcd-hppa_3.15_all.deb to pool/main/b/bootcd/bootcd-hppa_3.15_all.deb bootcd-i386_3.15_all.deb to pool/main/b/bootcd/bootcd-i386_3.15_all.deb bootcd-ia64_3.15_all.deb to pool/main/b/bootcd/bootcd-ia64_3.15_all.deb bootcd-mkinitramfs_3.15_all.deb to pool/main/b/bootcd/bootcd-mkinitramfs_3.15_all.deb bootcd_3.15.dsc to pool/main/b/bootcd/bootcd_3.15.dsc bootcd_3.15.tar.gz to pool/main/b/bootcd/bootcd_3.15.tar.gz bootcd_3.15_all.deb to pool/main/b/bootcd/bootcd_3.15_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libpar-packer-perl 0.991-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 27 Apr 2009 20:50:40 -0700 Source: libpar-packer-perl Binary: libpar-packer-perl Architecture: source i386 Version: 0.991-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Ryan Niebur ryanrya...@gmail.com Description: libpar-packer-perl - utility for creating PAR archives and stand-alone executables Changes: libpar-packer-perl (0.991-1) unstable; urgency=low . * New upstream release * update copyright * refresh patches * debhelper 7 * machine readable copyright format * add some more copyright information Checksums-Sha1: 9cb4a610a482faa3db914cc7b876bc19caa7201b 1535 libpar-packer-perl_0.991-1.dsc 2df43a4a76fc50b8d07bc3fea7b8f8465d4b444f 181717 libpar-packer-perl_0.991.orig.tar.gz 178534ba86924367bb24fa5164cd773a8e9fed39 5434 libpar-packer-perl_0.991-1.diff.gz c7578eb8e96916e7475a9813892c62da6fa2a4ce 1703390 libpar-packer-perl_0.991-1_i386.deb Checksums-Sha256: 08cf3e0611c07fd8717174919615525958c00fc7685a65e9e7848e19fa52fb74 1535 libpar-packer-perl_0.991-1.dsc b001cfe5238e5060d38a6fd35fe3a6afe2e79e4f2a6cdd5d44772dc2eaed6d89 181717 libpar-packer-perl_0.991.orig.tar.gz fba13a260685f4dffd4e3ddb284c1e6945a87ad3d91a551fc3771ee1cdd0dad9 5434 libpar-packer-perl_0.991-1.diff.gz a4f77a51f461c43c3430abdd083ecb91731861a439761484cefc49700a7e449e 1703390 libpar-packer-perl_0.991-1_i386.deb Files: 7f2d1d78c475f30816540b92e8080197 1535 perl optional libpar-packer-perl_0.991-1.dsc dcc41e19cedf917ffcb8acb3a97d1d1d 181717 perl optional libpar-packer-perl_0.991.orig.tar.gz 12ebf359567c7a58b28574c9c01f3d3e 5434 perl optional libpar-packer-perl_0.991-1.diff.gz 77a9bcb88092baba7f5e163b88930bd6 1703390 perl optional libpar-packer-perl_0.991-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3Gw0ACgkQOzKYnQDzz+TwbgCfTJYyUi6wbkFU9sSJcDbMrvmn qaAAn3Fps5KDFyHMd+CuXvnsX2bRwVIO =uaZc -END PGP SIGNATURE- Accepted: libpar-packer-perl_0.991-1.diff.gz to pool/main/libp/libpar-packer-perl/libpar-packer-perl_0.991-1.diff.gz libpar-packer-perl_0.991-1.dsc to pool/main/libp/libpar-packer-perl/libpar-packer-perl_0.991-1.dsc libpar-packer-perl_0.991-1_i386.deb to pool/main/libp/libpar-packer-perl/libpar-packer-perl_0.991-1_i386.deb libpar-packer-perl_0.991.orig.tar.gz to pool/main/libp/libpar-packer-perl/libpar-packer-perl_0.991.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted octave3.0 1:3.0.5-3 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 15:17:35 +0200 Source: octave3.0 Binary: octave3.0 octave3.0-doc octave3.0-htmldoc octave3.0-headers octave3.0-emacsen octave3.0-info octave2.9 octave2.9-doc octave2.9-htmldoc octave2.9-headers octave2.9-emacsen octave2.9-info octave3.0-dbg octave3.0-common Architecture: source amd64 all Version: 1:3.0.5-3 Distribution: unstable Urgency: low Maintainer: Debian Octave Group pkg-octave-de...@lists.alioth.debian.org Changed-By: Rafael Laboissiere raf...@debian.org Description: octave2.9 - GNU Octave language for numerical computations (dummy package) octave2.9-doc - PDF documentation on the GNU Octave language (dummy package) octave2.9-emacsen - Emacs support for the GNU Octave language (dummy package) octave2.9-headers - header files for the GNU Octave language (dummy package) octave2.9-htmldoc - HTML documentation on the GNU Octave language (dummy package) octave2.9-info - GNU Info documentation on the GNU Octave language (dummy package) octave3.0 - GNU Octave language for numerical computations (3.0 branch) octave3.0-common - architecture-independent files for octave3.0 octave3.0-dbg - Debug symbols for octave3.0 octave3.0-doc - PDF documentation on the GNU Octave language (3.0 branch) octave3.0-emacsen - Emacs support for the GNU Octave language (3.0 branch) octave3.0-headers - header files for the GNU Octave language (3.0 branch) octave3.0-htmldoc - HTML documentation on the GNU Octave language (3.0 branch) octave3.0-info - GNU Info documentation on the GNU Octave language (3.0 branch) Changes: octave3.0 (1:3.0.5-3) unstable; urgency=low . * debian/in/PACKAGE.postinst: Add -verbose option when calling 'pkg rebuild' in octave and redirect stdin from /dev/null. This is just to help debugging the hang up on the mipsel buildd when installing octave3.0 for building other packages (Bug#524745). Checksums-Sha1: 547f203558eb47b62ada52067b94504328b4fc1d 1982 octave3.0_3.0.5-3.dsc 2a9a4d85405a612348fa187480c8f8a17ecd0428 59069 octave3.0_3.0.5-3.diff.gz 5b1eb62711acd140b1a3a60a55337950484e6bb6 7474058 octave3.0_3.0.5-3_amd64.deb 700890eb1780494a72e961b07cdc8f65c15a6e98 454006 octave3.0-headers_3.0.5-3_amd64.deb bcec6d2e344b4a99e6cd50d7a8365e991cb0392c 40504188 octave3.0-dbg_3.0.5-3_amd64.deb e119aab107bc2c631e17a43b9656dbdf9dc706c0 2609388 octave3.0-doc_3.0.5-3_all.deb 92051a911cea09c473aca567d3a13e4fbf0010c1 978222 octave3.0-htmldoc_3.0.5-3_all.deb c9f4830ebbc2409296e5ec8bacb2ea4da530f472 102300 octave3.0-emacsen_3.0.5-3_all.deb a22a74f669826fabebddead88529cb47ed9a50df 505084 octave3.0-info_3.0.5-3_all.deb 5f961ed6fcf3cab3d2e35c03dae14f6b45c57eb3 77390 octave2.9_3.0.5-3_all.deb 2d083f775a871d738bf7c54c2c116002c09136ac 77392 octave2.9-doc_3.0.5-3_all.deb df8d98ca4d19d34261cf6b97d8e0b830c0586a91 77408 octave2.9-htmldoc_3.0.5-3_all.deb 2bb2e8d79b0fe47fa4dcdaf41ad63b7959970978 77402 octave2.9-headers_3.0.5-3_all.deb eaa603f4304b06ba4eb74694e18a4a9e6fa10f7f 77408 octave2.9-emacsen_3.0.5-3_all.deb 6d529a11da05c835768891c5cb95560433a979a8 77400 octave2.9-info_3.0.5-3_all.deb 4322ba795c65086ee462921c27b981e17a96e399 676844 octave3.0-common_3.0.5-3_all.deb Checksums-Sha256: 103676ef3db08b3d39ffdd4969605296929c82d87cbb8c7ab714a22ba039fbdf 1982 octave3.0_3.0.5-3.dsc 1b4b0625525163aa25af48ee3c49d5574689823902031ddb6baf5b1a342167d7 59069 octave3.0_3.0.5-3.diff.gz cacbf14a8420ffe871151947170185f1f42a2295381d384157af46aab0c56577 7474058 octave3.0_3.0.5-3_amd64.deb 55fff3b4e9a6e317d89ba9c5f4d16171ac65fffa22ab04624c374ab05ba26dd7 454006 octave3.0-headers_3.0.5-3_amd64.deb cb32b50da908069663a00f051fe019bbc9d6aceb81cc53ab76c3d758f1506b8d 40504188 octave3.0-dbg_3.0.5-3_amd64.deb dd5e0397d9cb84af571765e7d44eefdf487db187981ba266d6d2c7f92b90c668 2609388 octave3.0-doc_3.0.5-3_all.deb 11f3ffa7775687116f09b3bf99790d9be84e00845e62a66e650a8cce3088e562 978222 octave3.0-htmldoc_3.0.5-3_all.deb 5c594c2c3f772f2fb81ed1da2daf30877f65191ed31c861b486e79593cd0aea6 102300 octave3.0-emacsen_3.0.5-3_all.deb 08fff9e1fb347b97bd91ed61ea3fe02f990df09054ae6ad57611fa672a6808f9 505084 octave3.0-info_3.0.5-3_all.deb 21e5c50002fdb28e3a988f0f1718903f969576901b3b527d6dc91ccb8608c79b 77390 octave2.9_3.0.5-3_all.deb 173533aed0316a3a68872f8154c85f9060739be8bd79a059049d084bd4cd34c9 77392 octave2.9-doc_3.0.5-3_all.deb 62f17a0c597fbf55d45dc01247619b163fbb4d9de240428cd8aed9b4f84a4183 77408 octave2.9-htmldoc_3.0.5-3_all.deb 6b9530b5288e9b3ca00933581b23674cd82a8b9af78f687f9c64b09733e2c300 77402 octave2.9-headers_3.0.5-3_all.deb 4f915861413e7cb1c69573f1570d2f4bdf1f12743003c90c5f83e3c3ec5df126 77408 octave2.9-emacsen_3.0.5-3_all.deb 531819ea226c924d74bcc1db15a04d1ef97975d9e82c52c5f35ffacd96d4ad5e 77400 octave2.9-info_3.0.5-3_all.deb 3aee7c6e90254252d1a7d3674a6af1654f35aa8933a9c6261e7769ae1d76f1dc 676844 octave3.0-common_3.0.5-3_all.deb Files: 428640680275ddeac88f0ecd7512b57c 1982 math
Accepted libsvn-hooks-perl 0.17.54-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 17:58:03 +0200 Source: libsvn-hooks-perl Binary: libsvn-hooks-perl Architecture: source all Version: 0.17.54-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: gregor herrmann gre...@debian.org Description: libsvn-hooks-perl - framework for implementing subversion hooks Changes: libsvn-hooks-perl (0.17.54-1) unstable; urgency=low . * New upstream release. * debian/copyright: update years of upstream copyright, add /me to copyright for debian/*. * Add /me to Uploaders. * debian/rules: add the new --noonline-tests option to dh_auto_configure to make sure we don't run tests that require network access; bump debhelper dependency in debian/control. Checksums-Sha1: 9b0ad69afa5e4f9f54e32581d778b82dff883880 1602 libsvn-hooks-perl_0.17.54-1.dsc dc8cc7aceb4e49d1a2e0edde58b9678bdf1c3e0e 32936 libsvn-hooks-perl_0.17.54.orig.tar.gz f2c67300d5407446920c98d14d1d705165d80ae2 1865 libsvn-hooks-perl_0.17.54-1.diff.gz a7be0de6b244b3c350c2d43c0426f6b3d2f23d2f 75318 libsvn-hooks-perl_0.17.54-1_all.deb Checksums-Sha256: 35ecf8069763e86e9cc01f8a3bb350b1bab9a07543407b6214b372480d0747ea 1602 libsvn-hooks-perl_0.17.54-1.dsc 5f5f08dfc5766397b86e63abb59e30dbb2ef19ddde3fade22bb2a9b1214e3f90 32936 libsvn-hooks-perl_0.17.54.orig.tar.gz 9627a0f86a098bbf4f4350d28f60c6ea65cc9f57ac1d4df4d1838be4ed82c3f3 1865 libsvn-hooks-perl_0.17.54-1.diff.gz f718fa91a4dc253612e83456859642b79723ffad82d221670b0cebb86a11f86c 75318 libsvn-hooks-perl_0.17.54-1_all.deb Files: d661afc7c4d63b8cded15e1ad6f554e7 1602 perl optional libsvn-hooks-perl_0.17.54-1.dsc 003f8c971918fa4bca1e903f84b8d2e6 32936 perl optional libsvn-hooks-perl_0.17.54.orig.tar.gz 51519852dbb45c0775b69fda73a0cb05 1865 perl optional libsvn-hooks-perl_0.17.54-1.diff.gz 19e111b2e27bcee1bfcd3ecbc0445042 75318 perl optional libsvn-hooks-perl_0.17.54-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3KFYACgkQOzKYnQDzz+T/MQCgsiWFebVihnuyVy2qz3d2g8XF iMcAoJVM1RN3YytW0jukQM8nocD9w7u6 =PfE2 -END PGP SIGNATURE- Accepted: libsvn-hooks-perl_0.17.54-1.diff.gz to pool/main/libs/libsvn-hooks-perl/libsvn-hooks-perl_0.17.54-1.diff.gz libsvn-hooks-perl_0.17.54-1.dsc to pool/main/libs/libsvn-hooks-perl/libsvn-hooks-perl_0.17.54-1.dsc libsvn-hooks-perl_0.17.54-1_all.deb to pool/main/libs/libsvn-hooks-perl/libsvn-hooks-perl_0.17.54-1_all.deb libsvn-hooks-perl_0.17.54.orig.tar.gz to pool/main/libs/libsvn-hooks-perl/libsvn-hooks-perl_0.17.54.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted bibtool 2.48alpha.2-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 12:07:38 -0400 Source: bibtool Binary: bibtool Architecture: source i386 Version: 2.48alpha.2-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Barry deFreese bdefre...@debian.org Description: bibtool- tool for BibTeX database manipulation Closes: 363178 449718 Changes: bibtool (2.48alpha.2-4) unstable; urgency=low . * QA upload. + Set maintainer to Debian QA Group packa...@qa.debian.org. * Acknowledge NMUs. * Move URL from package description to Homepage. * Update watch file. (Closes: #449718). * Fix spelling error in package description. (Closes: #363178). * Make clean not ignore errors. * Syntax cleanup in debian/copyright. * Bump debhelper build-dep to = 5. * Move DH_COMPAT from rules to debian/compat and set to 5. * Bump Standards Version to 3.8.1. Checksums-Sha1: 3034f24f58deda478cb4b36d32327aaf40dca8e4 1092 bibtool_2.48alpha.2-4.dsc b687602e3bcea06ba41af7a930cd75bd9b0497a2 53149 bibtool_2.48alpha.2-4.diff.gz 49d8fd8128081c64e1faf712718ff894247eded3 144782 bibtool_2.48alpha.2-4_i386.deb Checksums-Sha256: ec3f34e048f9849cf22b686921fb70f45cbefa01c503fc82e1d4e15ad68a9b80 1092 bibtool_2.48alpha.2-4.dsc e9b679eb44b7f13b85ca68fe0377b4e50dbb56de4b24ee4e81bc8c7015cf6822 53149 bibtool_2.48alpha.2-4.diff.gz 4fb318b14341a4de148b81aacc26362bab2db1aa6e86c11e6c5fcff7ffd9aefe 144782 bibtool_2.48alpha.2-4_i386.deb Files: 27214cd488f16ab12657d37e23603d57 1092 tex optional bibtool_2.48alpha.2-4.dsc bb68b1f47483bc8379f4780d66758820 53149 tex optional bibtool_2.48alpha.2-4.diff.gz bc0476082150f9cb873b60f287749f75 144782 tex optional bibtool_2.48alpha.2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3NC4ACgkQ5ItltUs5T353xgCfXxA5GaxJ4NKG29ARwAkjIoqV KWEAoI9FLqkAVOa3TYq5SzTU//M4KF+P =btC7 -END PGP SIGNATURE- Accepted: bibtool_2.48alpha.2-4.diff.gz to pool/main/b/bibtool/bibtool_2.48alpha.2-4.diff.gz bibtool_2.48alpha.2-4.dsc to pool/main/b/bibtool/bibtool_2.48alpha.2-4.dsc bibtool_2.48alpha.2-4_i386.deb to pool/main/b/bibtool/bibtool_2.48alpha.2-4_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted git-cola 1.3.7.21-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 18:10:38 +0100 Source: git-cola Binary: git-cola Architecture: source all Version: 1.3.7.21-1 Distribution: unstable Urgency: low Maintainer: Iulian Udrea iul...@ubuntu.com Changed-By: Iulian Udrea iul...@ubuntu.com Description: git-cola - highly caffeinated git gui Changes: git-cola (1.3.7.21-1) unstable; urgency=low . * New upstream version. * Fix symlink (/usr/bin/git-difftool--helper). Checksums-Sha1: 83337cb7d79413339f6969ce28b27131ee494735 1295 git-cola_1.3.7.21-1.dsc 10f6b5328fc1fb177f2b3b90c3d0183134e79430 358779 git-cola_1.3.7.21.orig.tar.gz 9c9080a383036ec521b2b02717d9e2d029d4b4ab 5451 git-cola_1.3.7.21-1.diff.gz aced44815e95ff86d38d8eb71a690e126db066d4 352628 git-cola_1.3.7.21-1_all.deb Checksums-Sha256: 196de878d22390a0a91c454623aa516eb9f82d74523633f77bd64223e00a5885 1295 git-cola_1.3.7.21-1.dsc 5ebdf1c1812ae13d1b84e92262964356ba2cbd628c2f2c2ef7ca71de42b9b1eb 358779 git-cola_1.3.7.21.orig.tar.gz 7c457247c5a19900390b9ae0335d413208c379a5f250da9f5d2610a58f014589 5451 git-cola_1.3.7.21-1.diff.gz bdbe29bd63a453993889ac31fb63bd1631858a0e6b1aa7d0ea9f14f3f45f732c 352628 git-cola_1.3.7.21-1_all.deb Files: 1788ebd6ead3991fe0d7ed82bb5c9a54 1295 vcs optional git-cola_1.3.7.21-1.dsc 519f7ef879866cf22caae89cdfa874b8 358779 vcs optional git-cola_1.3.7.21.orig.tar.gz 7ab6fe966536c3458a58e5413e8d206c 5451 vcs optional git-cola_1.3.7.21-1.diff.gz 7f35cfaa036dbab08e975baf12092b49 352628 vcs optional git-cola_1.3.7.21-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3QdAACgkQ5ItltUs5T34XSgCfSkpb+2NMZepPPRzQ/b5Scjdo Kp4An17ZFkaGNXEAPVRRS3qXp+DwsPlT =8Cu8 -END PGP SIGNATURE- Accepted: git-cola_1.3.7.21-1.diff.gz to pool/main/g/git-cola/git-cola_1.3.7.21-1.diff.gz git-cola_1.3.7.21-1.dsc to pool/main/g/git-cola/git-cola_1.3.7.21-1.dsc git-cola_1.3.7.21-1_all.deb to pool/main/g/git-cola/git-cola_1.3.7.21-1_all.deb git-cola_1.3.7.21.orig.tar.gz to pool/main/g/git-cola/git-cola_1.3.7.21.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted xcftools 1.0.4-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 13:19:55 -0400 Source: xcftools Binary: xcftools Architecture: source i386 Version: 1.0.4-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Barry deFreese bdefre...@debian.org Description: xcftools - command-line tools for extracting data for XCF files Closes: 438290 Changes: xcftools (1.0.4-2) unstable; urgency=low . * QA upload. + Set maintainer to Debian QA Group packa...@qa.debian.org. * Remove strip from Makefile.in. (Closes: #438290). * Update syntax in debian/copyright. * Make clean not ignore errors. * Bump debhelper build-dep version to = 5.0.0. * Move DH_COMPAT from rules to debian/compat and set to 5. * Bump Standards Version to 3.8.1. Checksums-Sha1: 0eb580d34c13821fd1e5ca0eec273ba4c39adc2f 1006 xcftools_1.0.4-2.dsc 9ac170b55cb63b41e42f2818296cbe32029cdacb 8584 xcftools_1.0.4-2.diff.gz c29e44656af35bad18bc1877c336d3f60a620d60 88794 xcftools_1.0.4-2_i386.deb Checksums-Sha256: 8a54106ea51f2723daf2bc01b02d2c4136de57ee465ec3ccca92eb39ed9fb69a 1006 xcftools_1.0.4-2.dsc 5025d77b6851edf055a70e01352d8197e70d71ce6cf0214f5f4dbfae4de2abbf 8584 xcftools_1.0.4-2.diff.gz 92c79f2df281d71ac73f49ad322c6c164394ab494688250e7bcb59ea92c2e9c6 88794 xcftools_1.0.4-2_i386.deb Files: a7a44854e13b73b1f44275ef194eb71f 1006 graphics optional xcftools_1.0.4-2.dsc 53d1daf327495c7634a9e59af0411505 8584 graphics optional xcftools_1.0.4-2.diff.gz fc276f040201a5fe7d9e9f8bdd458586 88794 graphics optional xcftools_1.0.4-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3PyIACgkQ5ItltUs5T36LWACbBu4iIper999LVCU+Bw/xYSTJ kzsAoL/grrqbF4mgNkKG4gJfRa8p3mBk =Vcri -END PGP SIGNATURE- Accepted: xcftools_1.0.4-2.diff.gz to pool/main/x/xcftools/xcftools_1.0.4-2.diff.gz xcftools_1.0.4-2.dsc to pool/main/x/xcftools/xcftools_1.0.4-2.dsc xcftools_1.0.4-2_i386.deb to pool/main/x/xcftools/xcftools_1.0.4-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted babiloo 2.0.7-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Apr 2009 12:30:40 + Source: babiloo Binary: babiloo Architecture: source all Version: 2.0.7-1 Distribution: unstable Urgency: low Maintainer: Python Applications Packaging Team python-apps-t...@lists.alioth.debian.org Changed-By: Marco Rodrigues goth...@sapo.pt Description: babiloo- dictionary viewer with multi-languages support Changes: babiloo (2.0.7-1) unstable; urgency=low . * New upstream version. * XPM icon provided by upstream. Removed. * debian/babiloo.install: + Use upstream xpm icon. * debian/control: + Bump Standards-Version to 3.8.1 (no changes). * debian/rules: + Rebuild QT ui files. * debian/copyright: + Add myself to upstream authors :) Checksums-Sha1: a91ec7ec2713c278932964357772cac8a79ad075 1321 babiloo_2.0.7-1.dsc 01516443a4e9d85b02c767fe509b9603287cae61 758102 babiloo_2.0.7.orig.tar.gz d74337ebebb752263e06de30d515aeb908ed9d15 2644 babiloo_2.0.7-1.diff.gz 98c1a2577b31c9bb2bc407b148adbf559dea90af 727496 babiloo_2.0.7-1_all.deb Checksums-Sha256: e6b8ebb50b27bc275032c6cc5b3af7375669bc0140cc96cec388a0b8f8640cb1 1321 babiloo_2.0.7-1.dsc f62fddabab4ea5d8b249c96a4b90f18990f8b5fd4731f5e5a3ea68f474172704 758102 babiloo_2.0.7.orig.tar.gz b4e4bb6e018bae47379e257c8dbd2c852b5a3e0940d2054d889a277166f0387f 2644 babiloo_2.0.7-1.diff.gz 25670d3ea6f47085a8bf6dccdcd166a4c372f5bbd9f2abab197aea93093e3ffb 727496 babiloo_2.0.7-1_all.deb Files: 48449ab33033c7eb18d2910b19f8de88 1321 utils optional babiloo_2.0.7-1.dsc 7a2f33d40213d60323a5054551b4c73b 758102 utils optional babiloo_2.0.7.orig.tar.gz fcd745d62c486576f770fe3944624cf4 2644 utils optional babiloo_2.0.7-1.diff.gz bfdcf04e25b83acbe5eef5fd5dd9a61f 727496 utils optional babiloo_2.0.7-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkn3PKYACgkQB01zfu119ZlD+ACggmiVkfeVyangixNy588vwx/I 3WcAn0SZTtNgRB+Qi+EDBFeu7KK5bcnL =D/vx -END PGP SIGNATURE- Accepted: babiloo_2.0.7-1.diff.gz to pool/main/b/babiloo/babiloo_2.0.7-1.diff.gz babiloo_2.0.7-1.dsc to pool/main/b/babiloo/babiloo_2.0.7-1.dsc babiloo_2.0.7-1_all.deb to pool/main/b/babiloo/babiloo_2.0.7-1_all.deb babiloo_2.0.7.orig.tar.gz to pool/main/b/babiloo/babiloo_2.0.7.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
