apero pour NM parisiens: **30/09/2009**, 19:30, Frog @ BNF
On Mon, Sep 28, 2009 at 11:50:56PM +0200, Stefano Zacchiroli wrote:
mercredi soir, on va prendre un apero pour fêter le nouvelles DDs du
Bien sûr le sujet a été incorrect: la date est 30/09/2009 (i.e. demain).
Merci a Sylvain et Sylvestre pour le heads-up.
--
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: apero pour NM parisiens: 30/11/2009, 19:30, Frog @ BNF
On Mon, Sep 28, 2009 at 11:50:56PM +0200, Stefano Zacchiroli wrote: Salut a tous, Ciao Stefano, salut à tous, mercredi soir, on va prendre un apero pour fêter le nouvelles DDs du labo PPS (Mehdid Dogguy and Stéphane Glondu). En fait, je sais que il y a beaucoup d'autres nouvelle DDs français, mais je suis pas sur si ils sont sur Paris au pas. Je ne suis pas DD (DebMaint), mais j'aurais volontiers tapé l'incruste avec vous si je n'avais eu un autre engagement (ironie du sort : avec un DD, mon ami Lionel, qui vient manger à la maison, en banlieue lointaine, donc pas facile de changer les plans). Félicitations à tous et à une prochaine fois, Ciao ! Filippo -- Filippo Rusconi, PhD - CNRS - public key C78F687C Author of ``massXpert'' at http://www.massxpert.org U565 INSERM - UMR7196 CNRS - USM0503 MNHN 57, rue Cuvier Tél. : +33 (0)1 40 79 38 84 Case Postale 26 F-75231 Paris CEDEX 05 FRANCEFax : +33 (0)1 40 79 37 05 signature.asc Description: Digital signature
Re: apero pour NM parisiens: 30/11/2009, 19:30, Frog @ BNF
On Tue, Sep 29, 2009 at 10:21:18AM +0200, Filippo Rusconi wrote:
Je ne suis pas DD (DebMaint), mais j'aurais volontiers tapé l'incruste
Bien sûr l'apero est ouvert à tous: DD, DM, utilisateurs, ... On est pas
(trop) cabalistes :)
avec vous si je n'avais eu un autre engagement (ironie du sort : avec
un DD, mon ami Lionel, qui vient manger à la maison, en banlieue
lointaine, donc pas facile de changer les plans).
Dommage :-/
Si vous avez encore possibilité de changer des plans, dit nous, si non
dit bonjour a Lionel (qui j'imagine être Mamane) de chez moi.
--
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
renamings to remove extensions
Hi, I agree with Charles: this is unncessary, unproductive busy-work. On the other hand, Section 10.4 says only the script name should not include an extension. So you can leave the extension for compatibility with the rest of the world. It is a bug, but Section 1.1 says: Non-conformance with guidelines denoted by should (or recommended) will generally be considered a bug, but will not necessarily render a package unsuitable for distribution. -Steve signature.asc Description: Digital signature
Re: Policy §10.4 as a divergence from usptr eam (renamings to remove extensions like .pl an d .sh).
Charles Plessy wrote: I use the packages I made, and renaming upstream programs names makes my scripts incompatible with my colleagues work environments using other distributions or installations from source. So as a maintainer, I spend time creating extra work for myself as a user. That does not make sense. It is also possible to add symlinks into a private directory. Users willing to use names with extensions only have to add this directory to their PATH. For example, you can ship: /usr/bin/util /usr/share/package/bin/util.sh - /usr/bin/util Users willing to use names with extension on Debian only have to do PATH=/usr/share/package/bin:$PATH Regards, Vincent -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Patch Tagging Guidelines (aka DEP3)
On Wed, 23 Sep 2009, Kurt Roeckx wrote: For elfutils, I have 2 patches that I take from the upstream git repo. Both patches have their own branch, and upstream/redhat merges the master branch into them. So around the time of an upstream release I do git diff release...branch to get the new patch. Those branches contain several patches, so it's not a single commit. And I'm not sure how to properly put in the header where it comes from. I would suggesto to put an URL pointing to a branch instead of pointing to a specific commit. And explain in the description how the patch was generated. Cheers, -- Raphaël Hertzog -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
Steve M. Robbins st...@sumost.ca writes: I agree with Charles: this is unncessary, unproductive busy-work. The same characterisation could be given to other changes that raise the quality of software in Debian (e.g. ensuring that commands are accompanied by man pages, or that the package synopsis should not be repeated in the extended description). Improving quality may be strictly unnecessary, and may be not directly productive, but that doesn't mean there's no good reason to expect it. -- \“Choose mnemonic identifiers. If you can't remember what | `\mnemonic means, you've got a problem.” —Larry Wall | _o__) | Ben Finney pgpZfCOcoX2rn.pgp Description: PGP signature
Re: renamings to remove extensions
On Tue, Sep 29, 2009 at 07:30:44PM +1000, Ben Finney wrote: Steve M. Robbins st...@sumost.ca writes: I agree with Charles: this is unncessary, unproductive busy-work. The same characterisation could be given to other changes that raise the quality of software in Debian (e.g. ensuring that commands are accompanied by man pages, or that the package synopsis should not be repeated in the extended description). None of these have an impact on *other* software. Renaming a file does. Improving quality may be strictly unnecessary, and may be not directly productive, but that doesn't mean there's no good reason to expect it. Improving quality only for the sake of it is not necessarily a good idea. I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
On Tue, 2009-09-29 at 19:30 +1000, Ben Finney wrote: Steve M. Robbins st...@sumost.ca writes: I agree with Charles: this is unncessary, unproductive busy-work. The same characterisation could be given to other changes that raise the quality of software in Debian (e.g. ensuring that commands are accompanied by man pages, or that the package synopsis should not be repeated in the extended description). This is not a useful analogy. Software will continue to work with or without documentation or description. Renaming programs breaks interfaces. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
* Mike Hommey m...@glandium.org [090929 11:43]: Improving quality may be strictly unnecessary, and may be not directly productive, but that doesn't mean there's no good reason to expect it. Improving quality only for the sake of it is not necessarily a good idea. I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. If that is the case that only means that upstream should be educated and one has to choose between keeping bugs to be compatible and creating problems by fixing bugs. (File names is not the only case where fixing bugs can cause problems even to an extend where in same cases not fixing the bug can be the better solution). Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
Mike Hommey m...@glandium.org writes: On Tue, Sep 29, 2009 at 07:30:44PM +1000, Ben Finney wrote: Steve M. Robbins st...@sumost.ca writes: I agree with Charles: this is unncessary, unproductive busy-work. The same characterisation could be given to other changes that raise the quality of software in Debian (e.g. ensuring that commands are accompanied by man pages, or that the package synopsis should not be repeated in the extended description). None of these have an impact on *other* software. Renaming a file does. Peter Eisentraut pet...@debian.org writes: This is not a useful analogy. Software will continue to work with or without documentation or description. Renaming programs breaks interfaces. This is a different complaint from “unnecessary, unproductive busy-work”. I was answering only that complaint. So, if the change can be made *without* breaking existing interfaces (e.g. by providing a compatibility symlink to the suffix-less real program file), then the “breaks interfaces” complaint is addressed and is no longer an impediment to providing well-named program files. -- \“Holy contributing to the delinquency of minors, Batman!” —Robin | `\ | _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: renamings to remove extensions
Peter Eisentraut wrote: On Tue, 2009-09-29 at 19:30 +1000, Ben Finney wrote: Steve M. Robbins st...@sumost.ca writes: I agree with Charles: this is unncessary, unproductive busy-work. The same characterisation could be given to other changes that raise the quality of software in Debian (e.g. ensuring that commands are accompanied by man pages, or that the package synopsis should not be repeated in the extended description). This is not a useful analogy. Software will continue to work with or without documentation or description. Renaming programs breaks interfaces. I totally agree. For this reason the suffix must be removed! Program interfaces remain, but implementation language changes (see many -ng packages). ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Orphaning my packages...
Le mardi 29 septembre 2009 03:04:25, Kevin B. McCarty a écrit : Hi all, I unfortunately don't have the free time at the moment to do much for the Debian Project, so I'm orphaning my packages. If anyone wants to stake a claim to any of the following, please go ahead and say so, otherwise I'll file the orphaning bugs within a couple days. (Follow-ups set to debian-devel.) Cernlib-related (Cernlib is a huge, mostly obsolete set of physics libraries and tools) packages. These all have corresponding wnpp ITO bugs that can be changed to ITA / closed as desired. Note, Francois Niedercorn (in CC) has first dibs on these if he wants them. Francois, if you still do, please reply to debian-devel. cernlib - #508413 cfortran - #508500 I am not a debian developer but i could comaintain cfortran Bastien geant321 - #508496 mclibs - #508498 mn-fit - #508501 paw - #508495 Other packages: feynmf viewglob best regards, -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Policy §10.4 as a divergence from usptream (renamings to remove extensions like .pl and .sh).
On Tue, 2009-09-29 at 13:36 +0900, Charles Plessy wrote: I know that there has already been much of talk about this, but I am am getting more and more uncomfortable removing .pl or .sh extensions from programs when upstream does not. At least in cases where the programs/scripts could be considered part of a programming interface, this requirement is approximately equivalent to requiring the exported symbols of libraries to conform to some spelling scheme. While Debian has occasionally altered or broken the exported interfaces of libraries in cases of severe trouble, this is not routinely done, and usually not merely in the name of prettiness. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
Le mardi 29 septembre 2009 à 11:43 +0200, Mike Hommey a écrit : Improving quality only for the sake of it is not necessarily a good idea. I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. Which is why lintian warnings are left at the appreciation of the maintainer. Renaming binaries in a way that breaks interfaces or expectations is not desirable, of course. That doesn’t prevent the goal of removing useless script extensions from being a worthy one. The idea of putting extensions in scripts is stupid; it denotes a lack of understanding of the Unix way, and makes it harder to make them evolve in the future. Which is why we should remove these extensions when possible, and ask upstream to do so when it is not. Cheers, -- .''`. 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: Policy §10.4 as a divergence from usptream (renamings to remove extensions like .pl and .sh).
Le mardi 29 septembre 2009 à 13:21 +0800, Paul Wise a écrit : On Tue, Sep 29, 2009 at 1:09 PM, Reinhard Tartler siret...@debian.org wrote: Would you consider this a blocker to inclusion into Debian? Upstream may either release very slowly or may just not care about Debian, which would result in the package to never end up in Debian. I'd consider not fixing it in the .deb (irrespective of what upstream does) as a blocker. Having an uncooperative upstream would likely make me think twice about putting it in Debian in the first place. You can also try to make the world look like you want not adapt your eyes to see the world as is, no? Please note that upstream could not adapt themselves to all distribution policies which may be contradictory, but a distribution could and probably should adapt itself to upstream. In addition, many of upstream won't change their work just because we want them to do so because of our policy. In my case, I tried many times and most of my tries failed. You can not force others to adopt the same vision as you (at least in a democratic world). I consider this is a nice to have, that's all. Abou Al Montacir, signature.asc Description: Ceci est une partie de message numériquement signée
Webinar (free sign-up) on Google ranking: Top 10 SEO Tools
Good day, I came across your company in my research on potential firms and marketers (ad agencies, PR firms) that may be active in Internet Marketing, including S.E.O. or Search Engine Optimization for ranking higher on Google. I'd like to invite you to my upcoming free webinar on the Top Ten Free Tools for S.E.O. / Google Rank being held online on Oct 8th and 12th. The webinar is free, and the tools I identify are free as well - all are focused on helping you and your company improve your rank on Google searches. To register - more details on the eg3.com class I am teaching - http://seo-webinars.org/go.cgi?debian-de...@lists.debian.org Because it identifies the best free tools for SEO and ways to leverage Google's free (aka organic) listings - it usually fills up when I do offer it. I am usually too busy to offer this webinar, except a few times each year. About me - I am a researcher, journalist, and teacher living in the SF Bay Area working more on Google and S.E.O. issues. Hope to see you there. It will be time well spent! Best regards, Jason McDonald j.mcdon...@seo-webinars.org p.s. - I'd prefer that you minimize any forwarding of this announcement to colleagues as the webinars do usually fill up, and I try to limit the attendence to seriously minded marketers, ad agencies types, PR firms, etc. * To remove yourself from my contact list - http://www.seo-webinars.org/stop.html?debian-de...@lists.debian.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - How I do hate those enemies of the human race who go around enslaving God's free people with pledges- to quit drinking instead of to quit wanting to drink. -Letter to Henry W. Beecher, 9/11/1885 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548872: ITP: libjgraphx-java -- Java Swing Diagramming Library
Package: wnpp Severity: wishlist Owner: Sylvestre Ledru sylvestre.le...@inria.fr * Package name: libjgraphx-java Version : 1.0.2.4 * URL : http://www.jgraph.com/jgraphx.html * License : LGPL Programming Lang: Java Description : Java Swing Diagramming Library JGraph X is based on the mxGraph architecture, a re-designed core based on JGraph experience. . The new library API is designed to provide a much lower learning curve as well as making the feature set easier to extend and integrate. Sharing the model code base of mxGraph, the web diagramming library, enabling applications written in Java to be more easily ported to mxGraph-based web applications. . Overall, JGraph X provides more features that JGraph, with a far smaller code size and complexity. Redesigning the codebase from scratch now means implementing common feature extensions are easier and require less coding. A number of new loosely coupled application-centric features have been added, making prototyping even faster, without their usage restricting application flexibility. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: PLEASE REPLY ME ITS URGENT FOR HOME DECOR WEBSITES
Hi, I have signed up for this company And i have earned money from here You also can gain from here... Free sign up here and follow the instructions Its a online earning programme.No scams...because i have earned and still doing work for the company Free Register here: http://www.earnparttimejobs.com/index.php?id=2451106 For more knowledge you can see the Read More button Thanks Ronald
Re: Policy §10.4 as a d ivergence from usptrea m (renamings to remove extensions like .pl and .sh).
On Tue, Sep 29, 2009 at 10:40:23AM +0200, Vincent Danjean wrote:
It is also possible to add symlinks into a private directory. Users willing
to use names with extensions only have to add this directory to their PATH.
For example, you can ship:
/usr/bin/util
/usr/share/package/bin/util.sh - /usr/bin/util
But this will break the interface for users as well as long as they not
explicitely extend their path to
/usr/share/{packages_with_extensions_in_names}/bin
The only way to not break the interfaces is to invent a dir say
/usr/not_policy_compliant_named_dust-bin/
and move everything there ans set the policy compliant links to /usr/bin.
Not that I would be in favour of this suggestion but this is the only
way I would see to let things work out of the box if you globally set
your PATH to this dir.
Users willing to use names with extension on Debian only have to do
PATH=/usr/share/package/bin:$PATH
The problem is: A user has to read the docs before and adding this to
the PATH explicitely is as easy as learning about a renamed executable.
The goal is to let things work out of the box.
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: renamings to remove extensions
Quoting Josselin Mouette j...@debian.org: Le mardi 29 septembre 2009 à 11:43 +0200, Mike Hommey a écrit : Improving quality only for the sake of it is not necessarily a good idea. I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. Which is why lintian warnings are left at the appreciation of the maintainer. Renaming binaries in a way that breaks interfaces or expectations is not desirable, of course. That doesn’t prevent the goal of removing useless script extensions from being a worthy one. The idea of putting extensions in scripts is stupid; it denotes a lack of understanding of the Unix way, and makes it harder to make them evolve in the future. Which is why we should remove these extensions when possible, and ask upstream to do so when it is not. I've also read people claiming that preserving extensions could actually help evolving and migrations in the future and it is as simple as app.lang1 being rewritten as app.lang2, both stay on board as needed or for a reasonable amount of time, then at some point app.lang1 could actually be changed to just call app.lang2 when it's considered mature enough. That is absolutely fine with me as long as app.* are kept in reasonable amount of disk space, but scripts usually don't tend to become that large. (even small sizes could not be that practical for embedded when doubled, but that is another story). -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Policy §10.4 as a divergence from usptr eam (renamings to remove extensions like .pl an d .sh).
Abou Al Montacir wrote: Le mardi 29 septembre 2009 à 13:21 +0800, Paul Wise a écrit : On Tue, Sep 29, 2009 at 1:09 PM, Reinhard Tartler siret...@debian.org wrote: Would you consider this a blocker to inclusion into Debian? Upstream may either release very slowly or may just not care about Debian, which would result in the package to never end up in Debian. I'd consider not fixing it in the .deb (irrespective of what upstream does) as a blocker. Having an uncooperative upstream would likely make me think twice about putting it in Debian in the first place. You can also try to make the world look like you want not adapt your eyes to see the world as is, no? Please note that upstream could not adapt themselves to all distribution policies which may be contradictory, but a distribution could and probably should adapt itself to upstream. In addition, many of upstream won't change their work just because we want them to do so because of our policy. In my case, I tried many times and most of my tries failed. You can not force others to adopt the same vision as you (at least in a democratic world). IMHO this is not true. Look at Linux 10-15 years ago: it was completely different: every program was different: different option conventions, different commands to configure and build, different paths, different keys, different interpretation of free software, etc. Debian tried hard to standardize such things, and IMHO because of Debian (or with some Debian help) a lot of things changed. Your arguments are old, but fortunately we look forward, and now we have the open source definition, we have FHS, we have LSB, backspace/delete/C-H have a consistent behaviour, we don't need to use any special environment variable for any program, ... It is not a different vision, but a forward looking: user are interested in interfaces, not in the underlying details and languages. Thus *in general* (there are always exceptions), the suffix causes difficulties to reprogram the utility in an other language. It is not the upstream task to simplify forks and concurrent utilities (in an other language), so you cannot always agree/convince upstream to remove suffix, but we will have do deal with such enhancements. We cannot force the other to adapt to our vision, but we can have a common vision. Users (and developers) have the choice of distributions. Debian, unlike other old distribution, still exist, proving our vision is good. ciao cate PS: I see this issue the same as FHS (but one is about path prefix, and this in about suffix). Thus we experienced a lot on how to modify upstreams (a lot of upstreams still don't know about FHS). -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
What is this rule for? (was: Re: renamings to remove extensions)
On 29.09.2009 08:21, Steve M. Robbins wrote: On the other hand, Section 10.4 says only the script name should not include an extension. So you can leave the extension for What is the intention of this rule anyway? Thank you and best regards Andreas -- Andreas Tscharnerstarf...@sunrise.ch -- Intruder on level one. All Aliens please proceed to level one. -- Call in Alien: Resurrection -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Andreas Tscharner starf...@sunrise.ch writes: On 29.09.2009 08:21, Steve M. Robbins wrote: On the other hand, Section 10.4 says only the script name should not include an extension. So you can leave the extension for What is the intention of this rule anyway? To encourage command names (and hence command APIs, since the name is part of the API for the command) that do not encode implementation details, such as the programming language. This allows the program to be later re-implemented in a different language without the command name being misleading. -- \ “If we don't believe in freedom of expression for people we | `\ despise, we don't believe in it at all.” —Noam Chomsky, | _o__) 1992-11-25 | Ben Finney -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548895: ITP: pinyin-database -- PinYin database used by ibus-pinyin
Package: wnpp Severity: wishlist X-Debbugs-CC: debian-devel@lists.debian.org --- Please fill out the fields below. --- Package name: pinyin-database Version: 1.2.99 Upstream Author: Huang Peng shawn.p.hu...@gmail.com URL: http://code.google.com/p/ibus License: GPLv2 Description: PinYin database used by ibus-pinyin This package provide pinyin-database-version.tar.bz2 which is required when compile ibus-pinyin. Homepage: http://code.google.com/p/ibus -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Andreas Tscharner a écrit : On the other hand, Section 10.4 says only the script name should not include an extension. So you can leave the extension for What is the intention of this rule anyway? So I'm not the only one to wonder about this. After digging I've found the following discussion: http://lists.debian.org/debian-policy/2003/04/msg00031.html which led to the following bugreport: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=190753 which was fixed in version debian-policy/3.7.0.0. I agree with the arguments, but I am not convinced we should diverge from upstream on this topic, by the way. Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
O: mantis - web-based bug tracking system
retitle 471094 O: web-based bug tracking system noowner 471094 thanks Hi, as I do not use mantis anymore and I don't have the time nor interest to keep up with the mantis development, I'm hereby orphaning mantis. If you want to be the new maintainer, please take it -- see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Please note: There currently exists a SVN repository and a git repository. The latter is where the more recent development took place. I just let the SVN exist, because older versions referred to that repository in their control file and I didn't want to let it fail when checking them out (e.g. with debcheckout). If you need any information: I'm not out of the world or anything, so you can still reach me. CC'ing Olivier Berger, because he already made significant contributions to the mantis package. Maybe you are interested in taking it. Best Regards, Patrick -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Patch Tagging Guidelines (aka DEP3)
On Tue, Sep 29, 2009 at 11:25:17AM +0200, Raphael Hertzog wrote: On Wed, 23 Sep 2009, Kurt Roeckx wrote: For elfutils, I have 2 patches that I take from the upstream git repo. Both patches have their own branch, and upstream/redhat merges the master branch into them. So around the time of an upstream release I do git diff release...branch to get the new patch. Those branches contain several patches, so it's not a single commit. And I'm not sure how to properly put in the header where it comes from. I would suggesto to put an URL pointing to a branch instead of pointing to a specific commit. And explain in the description how the patch was generated. That assumes you can point to a URL. It might have a public VCS repo, but not some website. Kurt -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Ben Finney dijo [Tue, Sep 29, 2009 at 11:40:46PM +1000]: On the other hand, Section 10.4 says only the script name should not include an extension. So you can leave the extension for What is the intention of this rule anyway? To encourage command names (and hence command APIs, since the name is part of the API for the command) that do not encode implementation details, such as the programming language. This allows the program to be later re-implemented in a different language without the command name being misleading. And because extensions truly mean nothing. Of course, I can implement foo.py in Ruby as I am just prototyping but later decide to reimplement it (using the same name, as many scripts already depend on it) in Perl. In a Unix system, extensions are usually appended garbage which adds very, very little real value. ...Or possibly we could decide on renaming /bin/ls to /bin/ls.elf in order to show what kind of file it is, and allowing for different implementations to coexist? -- Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
Mike Hommey wrote: I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. /var/qmail/bin/qmail-send /command/supervise These are what are expected when you use qmail and daemontools the DJB way. http://cr.yp.to/unix.html We solve the first one with /var/qmail/bin being a symlink to /usr/sbin. We don't solve the latter one at all. Debian bug, or DJB bug? -- John H. Robinson, IV jaq...@debian.org http WARNING: I cannot be held responsible for the above, sbih.org ( )(:[ as apparently my cats have learned how to type. spiders.html -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Debconf and PackageKit
Hi, following pusling advice I'd like to explain the issues involved in this subject and a proposed solution. If you don't know anything about PackageKit it might be interesting to look at www.packagekit.org. I started to contribute to PackageKit willing to have it working on the system I use (Debian of course), but after I finished KPackageKit Debian support was almost at the same stage an apt backend written in python that didn't support lots of apt features like localizing, media changing, and installing packages that need removal of others... As I'm not a python fan i decided to do a new apt backend written in cpp (which does a difference in speed), apcc was created and most of the issues the py version had aptcc does not have I added media change support to Pk, descriptions of packages are now localized, and recently i added a new method called simulate that allowed me to emit packages to be removed in an install transaction. So now it works very close to what apt-get does. Installing/Removing/Updating are the last problem of this backend mostly because of debconf. PackageKit works this way (if you didn't take a look at the web site): Backend (apt | aptcc | yum | zyppy ) || || (some are completely separated process like python backends) || PackageKitD (an activated DBus service) || || (DBus interface) || GUI tools (gnome-packagekit, kpackagekit...) Some problems: 1. Looking at the above you probably already guessed that we have an already specified API, like search_name, get_details.. and adding something strickly debconf specific is not soo simple. 2. The user is able to start an update and logout his session, so where the DebConf dialog will be shown? Will it hang for ever? We thought of various solutions to these problems, and the one that might put and end to this would work like this: - The user asks to install foo - Backend creates a socket for debconf and (don't know how yet) keep an eye on it. - Backend starts installing foo... - Backend detects that a debconf dialog is needed - Backend check if the caller (the app that asked to install foo) is active, then one of the two actions must be taken: 1. If active sends a signal with the socket path and the path of an script that can set up a front end using this socket 2. If not, behave like in noninteractive mode chosing default answears OR finding a way to fail the instalation if the user is not present (dunno which is best) This solution is not implemented as I don't know debconf verry well but there is one problem that I'd like to know if there is a already a way to deal with this: when aptcc backend starts installing packages it's status are in a fd which might be localized is LANG is set, so I clean LANG and get dpkg to give strings like removing, unpacking, that can be converted to an enum. The problem is if i unset LANG debconf is not localized too so the user will see debconf dialog in english. My solution would be to have an extra env var like DEBCONF_LANG or DPKG_LANG (sorry if they already exist but i could not find it) This way dpkg can run not localized and debconf will have the right locale. Please be kind as I'm not familiar with this list :P and don't know debconf and dpkg internals... If you want download PackageKit and please try aptcc :D (BTW please send me links with intesreting info about debconf protocol, I could only find it from a package maintainer POV) Thanks, Daniel. Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Ben Finney dijo [Tue, Sep 29, 2009 at 11:40:46PM +1000]: On the other hand, Section 10.4 says only the script name should not include an extension. So you can leave the extension for What is the intention of this rule anyway? To encourage command names (and hence command APIs, since the name is part of the API for the command) that do not encode implementation details, such as the programming language. This allows the program to be later re-implemented in a different language without the command name being misleading. And because extensions truly mean nothing. Of course, I can implement foo.py in Ruby as I am just prototyping but later decide to reimplement it (using the same name, as many scripts already depend on it) in Perl. In a Unix system, extensions are usually appended garbage which adds very, very little real value. True. However, it makes no big difference whether people use (or resp. abuse) file extensions to claim the language a program is implemented in, or they do it within the base name. There are plenty of apps starring with py* and perl*, (and we have them most for years, which is not that different from *.py and *.pl) and I'd hesitate to characterize their naming style as tasteless or non- Unix way, instead I'd rather accept it as is, since this was what the author decided on and is what the rest of the world got used to. ...Or possibly we could decide on renaming /bin/ls to /bin/ls.elf in order to show what kind of file it is, and allowing for different implementations to coexist? This is of course good argument. Perhaps, some groups of apps, are not that challenging to be reimplemented in different ways, for various reasons including historical ones. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debconf and PackageKit
On Tue, Sep 29, 2009 at 10:26:01 -0700, Daniel Nicoletti wrote: This solution is not implemented as I don't know debconf verry well but there is one problem that I'd like to know if there is a already a way to deal with this: when aptcc backend starts installing packages it's status are in a fd which might be localized is LANG is set, so I clean LANG and get dpkg to give strings like removing, unpacking, that can be converted to an enum. The problem is if i unset LANG debconf is not localized too so the user will see debconf dialog in english. I don't understand this part. Why would you have to unset LANG? What exactly do you want to avoid being localized? My solution would be to have an extra env var like DEBCONF_LANG or DPKG_LANG (sorry if they already exist but i could not find it) This way dpkg can run not localized and debconf will have the right locale. Please be kind as I'm not familiar with this list :P and don't know debconf and dpkg internals... If you want download PackageKit and please try aptcc :D (BTW please send me links with intesreting info about debconf protocol, I could only find it from a package maintainer POV) /usr/share/doc/debian-policy/debconf_specification.html Cheers, Julien -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debconf and PackageKit
Le mardi 29 septembre 2009 à 10:26 -0700, Daniel Nicoletti a écrit : Installing/Removing/Updating are the last problem of this backend mostly because of debconf. PackageKit works this way (if you didn't take a look at the web site): Backend (apt | aptcc | yum | zyppy ) || || (some are completely separated process like python backends) || PackageKitD (an activated DBus service) || || (DBus interface) || GUI tools (gnome-packagekit, kpackagekit...) Some problems: 1. Looking at the above you probably already guessed that we have an already specified API, like search_name, get_details.. and adding something strickly debconf specific is not soo simple. 2. The user is able to start an update and logout his session, so where the DebConf dialog will be shown? Will it hang for ever? Currently, the question will simply be ignored, the frontend being set to noninteractive when there is no TTY nor display available. We thought of various solutions to these problems, and the one that might put and end to this would work like this: - The user asks to install foo - Backend creates a socket for debconf and (don't know how yet) keep an eye on it. - Backend starts installing foo... - Backend detects that a debconf dialog is needed - Backend check if the caller (the app that asked to install foo) is active, then one of the two actions must be taken: 1. If active sends a signal with the socket path and the path of an script that can set up a front end using this socket 2. If not, behave like in noninteractive mode chosing default answears OR finding a way to fail the instalation if the user is not present (dunno which is best) This is one of the possible solutions indeed. The thing you need is actually a new frontend for Debconf, that should probably be based on D-Bus so that you can map the authentication and permissions from what comes from PackageKit. This frontend would actually consist in a middleware that forwards requests through D-Bus. The real frontend would be called by the PackageKit frontend itself. You could probably directly re-use the existing Gnome frontend to show the actual dialogs. This solution is not implemented as I don't know debconf verry well but there is one problem that I'd like to know if there is a already a way to deal with this: when aptcc backend starts installing packages it's status are in a fd which might be localized is LANG is set, so I clean LANG and get dpkg to give strings like removing, unpacking, that can be converted to an enum. Ugh, that’s an absolutely horrible and broken solution. You should use the --status-fd dpkg option instead. The problem is if i unset LANG debconf is not localized too so the user will see debconf dialog in english. This is not a problem. The frontend is responsible for extracting the templates (the protocol only tells which questions to ask), and the locale in the frontend remains that of the user. Please be kind as I'm not familiar with this list :P and don't know debconf and dpkg internals... If you want download PackageKit and please try aptcc :D Maybe you should be aware that because of the shortcomings you describe, some Ubuntu people started to work on aptdaemon as a possible PackageKit replacement, PackageKit being absolutely unsuitable for a Debian-based system at the moment. (BTW please send me links with intesreting info about debconf protocol, I could only find it from a package maintainer POV) The protocol is described in debconf-devel(7). Cheers, -- .''`. 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: Policy §10.4 as a divergence from usptream (renamings to remove extensions like .pl and .sh).
On Tue, Sep 29 2009, Abou Al Montacir wrote: You can also try to make the world look like you want not adapt your eyes to see the world as is, no? We try to fix the world, yes. Systems integrations, and consistent policies, is what make Debian a superior OS. Please note that upstream could not adapt themselves to all distribution policies which may be contradictory, but a distribution could and probably should adapt itself to upstream. A distribution should not adapt itself to 1 different upstreams with different polices, that would be a inconsistent madness, and would serve our end users ill. Part of what we do as Debian maintainers is to make software fit better with other bits of Debian, and this we do by creating and following a technical policy. manoj -- We don't care how they do it in New York. Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
On Tue, Sep 29 2009, George Danchev wrote: I've also read people claiming that preserving extensions could actually help evolving and migrations in the future and it is as simple as app.lang1 being rewritten as app.lang2, both stay on board as needed or for a reasonable amount of time, then at some point app.lang1 could actually be changed to just call app.lang2 when it's considered mature enough. That is absolutely fine with me as long as app.* are kept in reasonable amount of disk space, but scripts usually don't tend to become that large. (even small sizes could not be that practical for embedded when doubled, but that is another story). Since it is being claimed that the script name is an interface that other software uses, then basic encapsulation 101 says that one should maintain the interface, but not rely on implementation (which, in the case of scripts, includes the language the script is implemented in). manoj -- But Officer, I stopped for the last one, and it was green! Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
On Tue, Sep 29 2009, Mike Hommey wrote: Improving quality may be strictly unnecessary, and may be not directly productive, but that doesn't mean there's no good reason to expect it. Improving quality only for the sake of it is not necessarily a good idea. !!! If we are trying to provide the best OS ever, improving quality is _always_ a good idea. It might be too hard, or too time consuming, to implement all the quality improvements, but that does not make the improvement of quality not a good idea. I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. I think I disagree. As my mother used to say, if all your friends jump into the well, that does not make it a good idea. manoj -- The one charm of marriage is that it makes a life of deception a neccessity. Oscar Wilde Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: renamings to remove extensions
On Tue, Sep 29 2009, Josselin Mouette wrote: Le mardi 29 septembre 2009 à 11:43 +0200, Mike Hommey a écrit : Improving quality only for the sake of it is not necessarily a good idea. I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. Which is why lintian warnings are left at the appreciation of the maintainer. Renaming binaries in a way that breaks interfaces or expectations is not desirable, of course. That doesn’t prevent the goal of removing useless script extensions from being a worthy one. Damn. Must be a cold day in hell, since I am on the same page here. The idea of putting extensions in scripts is stupid; it denotes a lack of understanding of the Unix way, and makes it harder to make them evolve in the future. Which is why we should remove these extensions when possible, and ask upstream to do so when it is not. Also, it breaks encapsulation; and makes it unnecessarily hard to re-implement the functionality in a different language (unless one thinks it is a good idea to have a python script have the name foo.sh). manoj -- This was the most unkindest cut of all. William Shakespeare, Julius Caesar Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Res: Debconf and PackageKit
De: Julien Cristau This solution is not implemented as I don't know debconf verry well but there is one problem that I'd like to know if there is a already a way to deal with this: when aptcc backend starts installing packages it's status are in a fd which might be localized is LANG is set, so I clean LANG and get dpkg to give strings like removing, unpacking, that can be converted to an enum. The problem is if i unset LANG debconf is not localized too so the user will see debconf dialog in english. I don't understand this part. Why would you have to unset LANG? What exactly do you want to avoid being localized? When apt-get install foo is installing things dpkg prints removing, unpacking, installing and those need to be mapped to enums that will be localized in PackageKit frontends. Thanks, Daniel. Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
On Tue, 29 Sep 2009, George Danchev wrote: True. However, it makes no big difference whether people use (or resp. abuse) file extensions to claim the language a program is implemented in, or they do it within the base name. There are plenty of apps starring with py* and perl*, (and we have them most for years, which is not that different from *.py and *.pl) and I'd hesitate to characterize their naming style as tasteless or non- Unix way, Both of these naming styles are annoying. Wasting characters in commands on non-useful information gets in the way of users doing what they want to do. If you're going to stick a command into a directory which is in PATH,[1] then it should be named as precisely and concisely as possible, while still being unique. If an executable encodes an interface which is widely used outside of Debian, then a compatibility symlink might still be in order, but otherwise, ditch the extension, submit a patch upstream,[2] and get on with life. [But whatever is done, don't spend too much time on it; if an upstream is doing this sort of thing, odds are there are other, more insidious things lurking, and it'd be a beter use (or waste!) of time trying to find them.] Don Armstrong 1: If this is some piddly executable in /usr/lib/foobar/blah.sh, then it doesn't really matter; the author could call it blah.sh.because.its.cool.nyatch because presumably no one is going to actually run the executable directly. 2: It's perfectly fine if its named blah.sh in the source, so long as it installs as blah on UNIX-y operating systems. -- Ban cryptography! Yes. Let's also ban pencils, pens and paper, since criminals can use them to draw plans of the joint they are casing or even, god forbid, create one time pads to pass uncrackable codes to each other. Ban open spaces since criminals could use them to converse with each other out of earshot of the police. Let's ban flags since they could be used to pass secret messages in semaphore. In fact let's just ban all forms of verbal and non-verbal communication -- let's see those criminals make plans now! 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: DEB_MAINTAINER_MODE=1 versus DEB_BUILD_OPTIONS=network.
On Mon, Sep 28 2009, Paul Wise wrote: On Tue, Sep 29, 2009 at 9:37 AM, Charles Plessy ple...@debian.org wrote: in my first experimentations I used DEB_BUILD_OPTIONS, but this leads to the possibility of clashing with flag names that can be reserved later with a different behaviour. On the other hand, if there are enough packages made using the same convention, then we may set the standard by our usage. Would there be other maintainers interested in using a 'network' flag for DEB_BUILD_OPTIONS? Just use something like DEB_BUILD_OPTIONS=x-check-network until there is an option for this enshrined in policy. Creating a working example, which is used in a number of packages (enough packages that most of the kinks in implementation of the handling have been worked out) would be a great first step towards getting it into policy anyway. manoj -- I am here by the will of the people and I won't leave until I get my raincoat back.- a slogan of the anarchists in Richard Kadrey's Metrophage Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548931: ITP: liburcu -- a userspace RCU (read-copy-update) library
Package: wnpp Severity: wishlist Owner: Jon Bernard jbern...@debian.org * Package name: liburcu Version : 0.1 Upstream Author : Mathieu Desnoyers mathieu.desnoy...@polymtl.ca * URL : http://ltt.polymtl.ca/?q=node/18 * License : GPL, LGPL, MIT/X Programming Lang: C Description : a userspace RCU (read-copy-update) library This data synchronization library provides read-side access which scales linearly with the number of cores. It does so by allowing multiples copies of a given data structure to live at the same time, and by monitoring the data structure accesses to detect grace periods after which memory reclamation is possible. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debconf and PackageKit
De: Josselin Mouette Currently, the question will simply be ignored, the frontend being set to noninteractive when there is no TTY nor display available. The hard work imo will be if i start in an interactive mode (in the backend) but when a question needs to popup the user loged out and i need to ignore the questions.. This is one of the possible solutions indeed. The thing you need is actually a new frontend for Debconf, that should probably be based on D-Bus so that you can map the authentication and permissions from what comes from PackageKit. This frontend would actually consist in a middleware that forwards requests through D-Bus. The real frontend would be called by the PackageKit frontend itself. You could probably directly re-use the existing Gnome frontend to show the actual dialogs. Well I think it might be easy to get accepts by Upstream if this was a separate app since no change in gnome or kde frontends would be needed to add a strictly Debian Feature, I thought of using a socket since it could be chmod to 600 for example. This solution is not implemented as I don't know debconf verry well but there is one problem that I'd like to know if there is a already a way to deal with this: when aptcc backend starts installing packages it's status are in a fd which might be localized is LANG is set, so I clean LANG and get dpkg to give strings like removing, unpacking, that can be converted to an enum. Ugh, that’s an absolutely horrible and broken solution. You should use the --status-fd dpkg option instead. hmm ok I'll investigate on how to use that in an apt-get based code.. The problem is if i unset LANG debconf is not localized too so the user will see debconf dialog in english. This is not a problem. The frontend is responsible for extracting the templates (the protocol only tells which questions to ask), and the locale in the frontend remains that of the user. hmm nice to know :D Please be kind as I'm not familiar with this list :P and don't know debconf and dpkg internals... If you want download PackageKit and please try aptcc :D Maybe you should be aware that because of the shortcomings you describe, some Ubuntu people started to work on aptdaemon as a possible PackageKit replacement, PackageKit being absolutely unsuitable for a Debian-based system at the moment. Yep I know they worked on aptdaemon but as the author told me it does not fit well in PackageKit as this could do. Thanks, Daniel. Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Debconf and PackageKit
Le mardi 29 septembre 2009 à 11:37 -0700, Daniel Nicoletti a écrit : Currently, the question will simply be ignored, the frontend being set to noninteractive when there is no TTY nor display available. The hard work imo will be if i start in an interactive mode (in the backend) but when a question needs to popup the user loged out and i need to ignore the questions.. In this case, just don’t set the questions as seen, and that’s all. They’ll be ignored or re-asked later, depending on the case. You could also switch to emulating the noninteractive frontend when that happens. This frontend would actually consist in a middleware that forwards requests through D-Bus. The real frontend would be called by the PackageKit frontend itself. You could probably directly re-use the existing Gnome frontend to show the actual dialogs. Well I think it might be easy to get accepts by Upstream if this was a separate app since no change in gnome or kde frontends would be needed to add a strictly Debian Feature, I thought of using a socket since it could be chmod to 600 for example. I was talking about the Gnome.pm frontend for Debconf. As for the socket idea, this is just a hack; if you’re working on a D-Bus-based frontend for APT, you need to use D-Bus for all communication. Ugh, that’s an absolutely horrible and broken solution. You should use the --status-fd dpkg option instead. hmm ok I'll investigate on how to use that in an apt-get based code.. Why do you use apt-get and not libapt? Especially if you’re working on a C++ frontend… Yep I know they worked on aptdaemon but as the author told me it does not fit well in PackageKit as this could do. Yes, OTOH it could fit as a backend to update-manager. Cheers, -- .''`. 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: Policy §10.4 as a divergence from usptream (renamings to remove extensions like .pl and .sh).
Peter Eisentraut pet...@debian.org writes: At least in cases where the programs/scripts could be considered part of a programming interface, this requirement is approximately equivalent to requiring the exported symbols of libraries to conform to some spelling scheme. While Debian has occasionally altered or broken the exported interfaces of libraries in cases of severe trouble, this is not routinely done, and usually not merely in the name of prettiness. The argument for the Policy change wasn't about prettiness, but rather about not encoding the implementation language into the interface name. When the shell script named foo.sh gets rewritten into Perl, having it stay foo.sh or be renamed to foo.pl are both kind of broken. That may not be a good enough argument to continue this policy, but that was the argument for why it's now in Policy. -- 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: What is this rule for?
On Tue, 29 Sep 2009, George Danchev wrote: True. However, it makes no big difference whether people use (or resp. abuse) file extensions to claim the language a program is implemented in, or they do it within the base name. There are plenty of apps starring with py* and perl*, (and we have them most for years, which is not that different from *.py and *.pl) and I'd hesitate to characterize their naming style as tasteless or non- Unix way, Both of these naming styles are annoying. Wasting characters in commands on non-useful information gets in the way of users doing what they want to do. If you're going to stick a command into a directory which is in PATH,[1] then it should be named as precisely and concisely as possible, while still being unique. If an executable encodes an interface which is widely used outside of Debian, then a compatibility symlink might still be in order, but otherwise, ditch the extension, submit a patch upstream,[2] and get on with life. [But whatever is done, don't spend too much time on it; if an upstream is doing this sort of thing, odds are there are other, more insidious things lurking, and it'd be a beter use (or waste!) of time trying to find them.] Don Armstrong 1: If this is some piddly executable in /usr/lib/foobar/blah.sh, then it doesn't really matter; the author could call it blah.sh.because.its.cool.nyatch because presumably no one is going to actually run the executable directly. 2: It's perfectly fine if its named blah.sh in the source, so long as it installs as blah on UNIX-y operating systems. Don, I hereby agree with the above (hence fully quoted signed), believe me or not. However, I'm afraid that we have some sort of asymmetry at our side, since we claim that both (py* vs. *.py) are annoying, but make sure policy discriminates only one of them. It is the asymmetry I have mostly misgivings with, hence I'd hesitate to use adjectives the authors naming styles. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu signature.asc Description: This is a digitally signed message part.
Re: Debconf and PackageKit
De: Josselin Mouette Le mardi 29 septembre 2009 à 11:37 -0700, Daniel Nicoletti a écrit : Currently, the question will simply be ignored, the frontend being set to noninteractive when there is no TTY nor display available. The hard work imo will be if i start in an interactive mode (in the backend) but when a question needs to popup the user loged out and i need to ignore the questions.. In this case, just don’t set the questions as seen, and that’s all. They’ll be ignored or re-asked later, depending on the case. You could also switch to emulating the noninteractive frontend when that happens. Good :D This frontend would actually consist in a middleware that forwards requests through D-Bus. The real frontend would be called by the PackageKit frontend itself. You could probably directly re-use the existing Gnome frontend to show the actual dialogs. Well I think it might be easy to get accepts by Upstream if this was a separate app since no change in gnome or kde frontends would be needed to add a strictly Debian Feature, I thought of using a socket since it could be chmod to 600 for example. I was talking about the Gnome.pm frontend for Debconf. As for the socket idea, this is just a hack; if you’re working on a D-Bus-based frontend for APT, you need to use D-Bus for all communication. Well the socket idea was one way to talk to debconf, I could setup an DBus interface to debconf so that debconf frontends could talk.. I just don't want to create another one. Ugh, that’s an absolutely horrible and broken solution. You should use the --status-fd dpkg option instead. hmm ok I'll investigate on how to use that in an apt-get based code.. Why do you use apt-get and not libapt? Especially if you’re working on a C++ frontend… I do use libapt, but I find it's docs too simple to write a whole aplication, in the code i do: result = DoInstall(file_descriptor); Probably dpkg has some env var to enable this --status-fd, or maybe this file descriptor is this ( i have to code this part.. :P ) Cheers, Daniel. Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
LSI MegaRAID SAS 9260-4i and Lenny
Hi all, Is there any way to make it work under Debian Lenny? I saw only RHE/SLE drivers on the LSI website... Is there an open source driver? If yes, will it be backported into lenny? Cheers, Darkbasic -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
[George Danchev] However, I'm afraid that we have some sort of asymmetry at our side, since we claim that both (py* vs. *.py) are annoying, but make sure policy discriminates only one of them. I think that is a historical accident. Before python got so popular, language-based prefixes were not common, but suffixes have always been popular, probably because people came from MS-DOS and its spiritual descendent, Windows NT. The other reason suffixes are worse is, again due to influence from MS-DOS, people don't think of them as part of the name. And, removing the suffix does not cause problems with tab completion in the shell. So it seems less harsh to strip suffixes than to strip prefixes. -- 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: LSI MegaRAID SAS 9260-4i and Lenny
On Tue, 2009-09-29 at 21:10 +0200, Niccolò Belli wrote: Hi all, Is there any way to make it work under Debian Lenny? Maybe, but you're asking on the wrong list... I saw only RHE/SLE drivers on the LSI website... Is there an open source driver? Yes. If yes, will it be backported into lenny? Maybe, if you file a wishlist bug against linux-2.6. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp signature.asc Description: This is a digitally signed message part
Re: link to link
For link ex..:- seo.kishor...@gmail.com
Re: LSI MegaRAID SAS 9260-4i and Lenny
Il 29 settembre 2009 21.47, Ben Hutchings b...@decadent.org.uk ha scritto: On Tue, 2009-09-29 at 21:10 +0200, Niccolò Belli wrote: Is there any way to make it work under Debian Lenny? Maybe, but you're asking on the wrong list... Where shall I ask? I already tried debian-italian without success... Is there an open source driver? Yes. Really? Where can I find it? If yes, will it be backported into lenny? Maybe, if you file a wishlist bug against linux-2.6. I'll do it, thank you. Cheers, Darkbasic -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Policy §10.4 as a divergence from usptream (renamings to remove extensions like .pl and .sh).
On Tuesday 29 September 2009, Russ Allbery wrote: Peter Eisentraut pet...@debian.org writes: At least in cases where the programs/scripts could be considered part of a programming interface, this requirement is approximately equivalent to requiring the exported symbols of libraries to conform to some spelling scheme. While Debian has occasionally altered or broken the exported interfaces of libraries in cases of severe trouble, this is not routinely done, and usually not merely in the name of prettiness. The argument for the Policy change wasn't about prettiness, but rather about not encoding the implementation language into the interface name. When the shell script named foo.sh gets rewritten into Perl, having it stay foo.sh or be renamed to foo.pl are both kind of broken. That may not be a good enough argument to continue this policy, but that was the argument for why it's now in Policy. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ I am a newcommer to this particular bit of policy, but it occurs to me that the answer is to add links to the original commands to conform to Debian standards while leaving the upstream commands intact. This would then also mean that any documentation or howtos or tutorials or blogs written around the upstream commands will still work. Otherwise not only does Debian have to modify the commands but also all the documentation and write its own howtos and blogs. Also somehow we would need to subvert Google so it finds our copies for Debian users. David David -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Gunnar Wolf wrote: [snip] And because extensions truly mean nothing. Of course, I can This is true for Unix/Posix systems, but unfortunately not for Windows systems. And if the maintainer of a great Perl script wants his script to work on both platforms, he'll probably will name it GreatPerlScript.pl If the extension .pl is linked with a Perl interpreter in Windows, he'll be able to run it on both systems without a prepending perl Don't get me wrong here: I see the reasons for removing the extensions, but I think this is a valid point for having one in the first place. Best regards Andreas -- Andreas Tscharner starf...@sunrise.ch -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rich Cook -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Andreas Tscharner starf...@sunrise.ch writes: This is true for Unix/Posix systems, but unfortunately not for Windows systems. And if the maintainer of a great Perl script wants his script to work on both platforms, he'll probably will name it GreatPerlScript.pl If the extension .pl is linked with a Perl interpreter in Windows, he'll be able to run it on both systems without a prepending perl If he names it GreatPerlScript on Unix and GreatPerlScript.pl on Windows, he'll be able to run it on both systems as GreatPerlScript. -- 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: What is this rule for?
Russ Allbery r...@debian.org wrote: Andreas Tscharner starf...@sunrise.ch writes: This is true for Unix/Posix systems, but unfortunately not for Windows systems. And if the maintainer of a great Perl script wants his script to work on both platforms, he'll probably will name it GreatPerlScript.pl If the extension .pl is linked with a Perl interpreter in Windows, he'll be able to run it on both systems without a prepending perl If he names it GreatPerlScript on Unix and GreatPerlScript.pl on Windows, he'll be able to run it on both systems as GreatPerlScript. Yes. And those scripts that would run on Windows and expect GreatPerlScript.pl, but do not run on Unix *only* because the pl is missing - those script probably don't exist. Regards, Frank -- Dr. Frank Küster Debian Developer (TeXLive) VCD Aschaffenburg-Miltenberg, ADFC Miltenberg B90/Grüne KV Miltenberg -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Policy §10.4 as a divergence from usptream (renamings to remove extensions like .pl and .sh).
David Goodenough david.goodeno...@btconnect.com wrote: I am a newcommer to this particular bit of policy, but it occurs to me that the answer is to add links to the original commands to conform to Debian standards while leaving the upstream commands intact. That would horribly clutter the bin directories. I think the approach with a /usr/share/$packagename/bin/ that contains the old names as links, and can be added to PATH, is the best we can do for supporting scripts that assume extensions. Regards, Frank -- Dr. Frank Küster Debian Developer (TeXLive) VCD Aschaffenburg-Miltenberg, ADFC Miltenberg B90/Grüne KV Miltenberg -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is this rule for?
Frank Küster fr...@debian.org writes: Russ Allbery r...@debian.org wrote: If he names it GreatPerlScript on Unix and GreatPerlScript.pl on Windows, he'll be able to run it on both systems as GreatPerlScript. Yes. And those scripts that would run on Windows and expect GreatPerlScript.pl, but do not run on Unix *only* because the pl is missing - those script probably don't exist. Oh, I'm sure they do. I know that renaming binaries can break compatibility; I'm not arguing that. I'm just pointing out that it's not impossible to do the right thing. Transition issues certainly still apply. -- 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: renamings to remove extensions
John H. Robinson, IV jaq...@debian.org (29/09/2009): These are what are expected when you use qmail and daemontools the DJB way. http://cr.yp.to/unix.html We solve the first one with /var/qmail/bin being a symlink to /usr/sbin. We don't solve the latter one at all. Debian bug, or DJB bug? The Debian bug is to have anything DJB-related in the first place. Mraw, KiBi. signature.asc Description: Digital signature
Re: What is this rule for?
Andreas Tscharner dijo [Tue, Sep 29, 2009 at 10:35:46PM +0200]: And because extensions truly mean nothing. Of course, I can This is true for Unix/Posix systems, but unfortunately not for Windows systems. And if the maintainer of a great Perl script wants his script to work on both platforms, he'll probably will name it GreatPerlScript.pl If the extension .pl is linked with a Perl interpreter in Windows, he'll be able to run it on both systems without a prepending perl Don't get me wrong here: I see the reasons for removing the extensions, but I think this is a valid point for having one in the first place. That's the reason we sometimes diverge away from upstream: We don't cater for the exact same audience, and we might modify their chosen binary names to make things easier and more coherent for our users. -- Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548972: ITP: gross -- fast and efficient greylist server
Package: wnpp Severity: wishlist Owner: Antonio Radici anto...@dyne.org * Package name: gross Version : 1.0.2 Upstream Author : Eino Tuominen e...@utu.fi, Antti Siira an...@utu.fi * URL : http://code.google.com/p/gross/ * License : BSD Programming Lang: C Description : fast and efficient greylist server with DNSBL support Gross is a resource efficient greylist server written in C that supports greylisting and/or blocking based on DNSRBL so it will not impact legitimate mails . It also contains a milter implementation and natively supports Postfix, Exim and Sendmail. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /var/www is depracated, which directory to use?
Tollef wrote: I realise you've had good an constructive responses for webapps, so commenting on /srv in particular: As I read it, putting stuff there is absolutely not fine. It's even more off-limits than /usr/local (where you can create directories, but not remove them). I'm still unconvinced by /srv personally - we've strived for years in Debian to make things work as much as possible straight from initial installation, yet now we're expected to deliberately leave services unconfigured. I don't think this is progress for most of our users... -- Steve McIntyre, Cambridge, UK.st...@einval.com Since phone messaging became popular, the young generation has lost the ability to read or write anything that is longer than one hundred and sixty characters. -- Ignatios Souvatzis -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /var/www is depracated, which directory to use?
Steve McIntyre st...@einval.com writes: I'm still unconvinced by /srv personally - we've strived for years in Debian to make things work as much as possible straight from initial installation, yet now we're expected to deliberately leave services unconfigured. I don't think this is progress for most of our users... I don't think /srv is the answer to any question about where do Debian packages put data in their default configuration. /srv is really intended to be a place where the local system administrator organizes their service data, which means we need to let them choose to organize it however they wish. I think the real problem here is that we have some missing integration glue. A lot of packages want to serve things out via the web by default unless the sysadmin has indicated that they want control over the URL space. Apache sort of provides a way to do that, but it isn't very good. Other web servers in Debian so far as I know don't at all. And there isn't a common interface supported by all of them. I think we need to put together a standard definition of how a Debian package can specify please serve out this data and this CGI script at these URLs unless the sysadmin has said to leave the web configuration alone, using a standard API implemented by all web servers in Debian. I suspect that will get everyone what they want. -- 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: /var/www is depracated, which directory to use?
Russ Allbery wrote: Steve McIntyre st...@einval.com writes: I'm still unconvinced by /srv personally - we've strived for years in Debian to make things work as much as possible straight from initial installation, yet now we're expected to deliberately leave services unconfigured. I don't think this is progress for most of our users... I don't think /srv is the answer to any question about where do Debian packages put data in their default configuration. /srv is really intended to be a place where the local system administrator organizes their service data, which means we need to let them choose to organize it however they wish. I think the real problem here is that we have some missing integration glue. A lot of packages want to serve things out via the web by default unless the sysadmin has indicated that they want control over the URL space. Apache sort of provides a way to do that, but it isn't very good. Other web servers in Debian so far as I know don't at all. And there isn't a common interface supported by all of them. I think we need to put together a standard definition of how a Debian package can specify please serve out this data and this CGI script at these URLs unless the sysadmin has said to leave the web configuration alone, using a standard API implemented by all web servers in Debian. I suspect that will get everyone what they want. I agree on this one. I personally prefer to keep files served by a webserver in /var/www/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: /var/www is depracated, which directory to use?
mli...@stacktrace.us mli...@stacktrace.us writes: I personally prefer to keep files served by a webserver in /var/www/ Local sysadmins can of course use that path, but Debian packages aren't allowed to according to the way most of us have read the FHS. Debian web application packages should really put their static files in /usr/share/package and their data files in /var/lib/package just like every other package does, and then use the web configuration to serve out the correct parts of the file system. That way there's never any accidental, unexpected results from dropping files into an area that a sysadmin may think they can use for some other purpose. -- 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: renamings to remove extensions
On Tue, Sep 29, 2009 at 10:05:29AM -0700, John H. Robinson, IV wrote: Mike Hommey wrote: I do agree that if everyone but Debian expects foo to be called as foo.pl, there is a bug in Debian. /var/qmail/bin/qmail-send /command/supervise These are what are expected when you use qmail and daemontools the DJB way. http://cr.yp.to/unix.html We solve the first one with /var/qmail/bin being a symlink to /usr/sbin. We don't solve the latter one at all. Debian bug, or DJB bug? DJB bug. (And a symlink doesn't make the software FHS-compliant.) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Processed: Re: Bug#548661: dpkg: Override package dependencies
Processing commands for cont...@bugs.debian.org: reassign 548661 apt Bug #548661 [general] dpkg: Override package dependencies Bug reassigned from package 'general' to 'apt'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Orphaning my packages...
Bastien ROUCARIES wrote: Le mardi 29 septembre 2009 03:04:25, Kevin B. McCarty a écrit : Hi all, I unfortunately don't have the free time at the moment to do much for the Debian Project, so I'm orphaning my packages. [...] Cernlib-related (Cernlib is a huge, mostly obsolete set of physics libraries and tools) packages. These all have corresponding wnpp ITO bugs that can be changed to ITA / closed as desired. Note, Francois Niedercorn (in CC) has first dibs on these if he wants them. Francois, if you still do, please reply to debian-devel. cernlib - #508413 cfortran - #508500 I am not a debian developer but i could comaintain cfortran If you don't hear from Francois within the next couple days, please feel free to claim it. (If you do hear from him, the two of you will have to work something out.) Note that I unfortunately will not have the time to co-maintain or sponsor any uploads. best regards, -- Kevin B. McCarty kmcca...@gmail.com WWW: http://www.starplot.org/ WWW: http://people.debian.org/~kmccarty/ GPG: public key ID 4F83C751 signature.asc Description: OpenPGP digital signature
Bug#548661: dpkg: Override package dependencies
reassign 548661 apt thanks But as seen in bug#542095, some dependencies are not really hard, yet you don't want them to be recommends because that would be too easy for users to ignore. So bug#542095 shows that there is a need for something between recommends and true dependencies that can only be ignored if the user very specifically requests to ignore this precise dependency (I already ignore all recommends). I don't agree that we need something in between. You decide what you want to install. the gnome meta-packages doesn't correspond to what you want? don't install it and install the various components by hand or create an alternative meta-package. While it's not too difficult to install some of the components by hand (aptitude show gnome makes it easy to see which components are needed), doing it leads to lots of headaches in the long run, since when new components come around, nothing will tell you about it (and even less install them for you), and when old ones become replaced or obsolete, agai nobody will tell you (and even less install the replacement for you). That's what the `gnome' package is for, and that's why it's important to be able to install that package (and other metapackages) rather than its dependencies. You come up with this request only because Josselin Mouette doesn't want to drop network-manager to a Recommends or put an alternative in place. Actually, no. It's a kind of problem that has shown up several times already in the past, for various reasons. Sometimes it's just a bug in the packaging other times the maintainer has good reasons to keep the dependencies in a particular way, even if they don't fit my needs. Clearly, the current network-manager-in-gnome issue is the one that prompted this bug-report, but only because it finally occurred to me that a good solution to this problem is a more general solution that gives more power to the end-user. The solution exists but because the maintainer doesn't want to implement it, you request a third way to respond to your need under control of the user. How is that reasonable? Because in the world of Free Software, last I heard, giving more control to the end user is generally considered a good thing, so she doesn't have to rely on the goodwill/agreement/help of the men in charge. What alternative solution do you propose if I want to both have wicd and gnome installed? Or if my system is memory constrained and I want xserver-xorg installed but not hal? Or ...? gnome is not required at all, it's only a meta-package, don't install it but install manually all the other dependencies. For the xserver, talk to the X maintainers or use a lighter distribution. So for each problem in the packaging dependencies, you advocate to use a different solution, each one of those with its own set of problems. Instead, I advocte a single solution that can solve each one of those problems in a uniform manner: tell the packaging system (I originally thought dpkg would be a good place for that, but I now realize that APT is a better place for it) about some constraints that need to be ignored. This could include not only Dpends-constraints (as suggested originally in this bug-report), but also Conflicts-constraints (e.g., so I can install grub-pc, grub-efi-amd64 and and grub-efi-ia32 on my Debian rescue USB key). Clearly, ignoring such constraints is risky business (not like ignoring recommends constraints), so you'd want to force the user to think hard before doing so, and you'd only let her ignore specific constraints, you might ask for confirmation before adding such an ignore-constraint to the list of ignored constraints, and you might even query the user every once in a while to make sure she still wants to keep those ignore-constraints. Stefan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: DEB_MAINTAINER_MODE=1 versus DEB_BUILD_OPTIONS=network.
Le Tue, Sep 29, 2009 at 01:12:14PM -0500, Manoj Srivastava a écrit : On Mon, Sep 28 2009, Paul Wise wrote: On Tue, Sep 29, 2009 at 9:37 AM, Charles Plessy ple...@debian.org wrote: in my first experimentations I used DEB_BUILD_OPTIONS, but this leads to the possibility of clashing with flag names that can be reserved later with a different behaviour. On the other hand, if there are enough packages made using the same convention, then we may set the standard by our usage. Would there be other maintainers interested in using a 'network' flag for DEB_BUILD_OPTIONS? Just use something like DEB_BUILD_OPTIONS=x-check-network until there is an option for this enshrined in policy. Creating a working example, which is used in a number of packages (enough packages that most of the kinks in implementation of the handling have been worked out) would be a great first step towards getting it into policy anyway. Hi all, since there was no ‘me too’ message in this thread from developers wanting to optionaly enable network tests, I will keep on using DEB_MAINTAINER_MODE and will not go further in proposing a new DEB_BUILD_OPTIONS flag. This said, I will be happy to update my package to use DEB_BUILD_OPTIONS in the future if some standard emerges. 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
Accepted ntop 3:3.3-12 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Sep 2009 09:20:27 +0200 Source: ntop Binary: ntop Architecture: source i386 Version: 3:3.3-12 Distribution: unstable Urgency: low Maintainer: Ola Lundqvist o...@debian.org Changed-By: Ola Lundqvist o...@debian.org Description: ntop - display network usage in web browser Closes: 501754 527757 534779 543312 Changes: ntop (3:3.3-12) unstable; urgency=low . * Correction for CVE-2009-2732. Closes: #543312. * Brazilian translation added. Closes: #501754. * Russian translation added. Closes: #534779. * Added autogen.sh -p to the clean target to make sure that the build works fine. Closes: #527757. Checksums-Sha1: 10dd6694592090dc5c80fadb57a55d1ee9d9a594 1097 ntop_3.3-12.dsc 6be06339b6b90c75e0c8e6867218fda594ef5376 227781 ntop_3.3-12.diff.gz 4f6d8291c223a438a22ada6fd5ce27e3f1450630 2640516 ntop_3.3-12_i386.deb Checksums-Sha256: f30d555cf87a545bc3679a39b51859a51294c29fac68f439d25d1a1dce9a3b3a 1097 ntop_3.3-12.dsc dc3e1fc035e788ccb242ed9e859bf90ca2b3fa89dc3f6a3226c13366a11c964a 227781 ntop_3.3-12.diff.gz ab91aa73d8fc987c4d9249ce38c7ec5d17356fe928652407c6e2e0f13df1b6b4 2640516 ntop_3.3-12_i386.deb Files: f8fc0e5b124dedeb5fbb0a7bb7e4079b 1097 net optional ntop_3.3-12.dsc d0ac9d0b5836534a515024cd335e56de 227781 net optional ntop_3.3-12.diff.gz a3ea60cbdd3e2561405ebb131c0036a6 2640516 net optional ntop_3.3-12_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrBnhoACgkQGKGxzw/lPdkD8gCfXC0uvL8g5cxZYNo6RG+lH4jI xhAAnjJEnysjaFBhTH/EhcbBXqtyy938 =r24m -END PGP SIGNATURE- Accepted: ntop_3.3-12.diff.gz to pool/main/n/ntop/ntop_3.3-12.diff.gz ntop_3.3-12.dsc to pool/main/n/ntop/ntop_3.3-12.dsc ntop_3.3-12_i386.deb to pool/main/n/ntop/ntop_3.3-12_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 xfce4-settings 4.6.3-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.8 Date: Tue, 29 Sep 2009 08:53:46 +0200 Source: xfce4-settings Binary: xfce4-settings Architecture: source amd64 Version: 4.6.3-1 Distribution: unstable Urgency: low Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Yves-Alexis Perez cor...@debian.org Description: xfce4-settings - graphical application for managing Xfce settings Changes: xfce4-settings (4.6.3-1) unstable; urgency=low . * New upstream bugfix release. * debian/control: - update standards version to 3.8.3. - drop quilt, now useless. * debian/patches/ - 01_fix-timeout-startup dropped, included upstream. - 02_fix-keyrepeat-typo as well. - 10_pc too, useless now. * debian/rules: - drop --with-quilt addon. Checksums-Sha1: 8ba5d6e9e45897ed94cabcae16062099e78b8d32 1500 xfce4-settings_4.6.3-1.dsc c31e392997cac0fb926297057b6c44899c7de040 788461 xfce4-settings_4.6.3.orig.tar.gz 34505218c430fddc1a169f49b3da8de8ecd4bb61 3808 xfce4-settings_4.6.3-1.diff.gz 7bdb7fd403f071e6995b4f2c66baeb1134ec2774 301160 xfce4-settings_4.6.3-1_amd64.deb Checksums-Sha256: 44dc0cc99b429a14b946fd9fac5c7ba2a3cd4f2831ffcd155527d3cff56d 1500 xfce4-settings_4.6.3-1.dsc 5b5f9794ad4f43914941e50f78bcf79cecc8084465fa3634e72f62004003c1ae 788461 xfce4-settings_4.6.3.orig.tar.gz 5b7d2e4696331339ee0fd4aad398e4bd920bb11cd24a5b760134e1330d7c3ecd 3808 xfce4-settings_4.6.3-1.diff.gz 55d1ffef8d5e36eedf6cbcf577e44472a156ee62533819060b241b083cadf33e 301160 xfce4-settings_4.6.3-1_amd64.deb Files: 26b94fb2721f67b43ed6dbeab486856a 1500 xfce optional xfce4-settings_4.6.3-1.dsc 334514c3ad1fb8c49dae4c5aa9705cbf 788461 xfce optional xfce4-settings_4.6.3.orig.tar.gz 59f60d17e6ed2aa8b834a5854b0aecd3 3808 xfce optional xfce4-settings_4.6.3-1.diff.gz f75f294a58f7889a6082aedca80216a9 301160 xfce optional xfce4-settings_4.6.3-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEAREDAAYFAkrBse0ACgkQTUTAIMXAW65W/ACfYbuSC/SrfZzZp7/IUP4T3iUN 9AMAoKHKbn+WlOC0CDu5HNuRl4cV9TIW =1mf/ -END PGP SIGNATURE- Accepted: xfce4-settings_4.6.3-1.diff.gz to pool/main/x/xfce4-settings/xfce4-settings_4.6.3-1.diff.gz xfce4-settings_4.6.3-1.dsc to pool/main/x/xfce4-settings/xfce4-settings_4.6.3-1.dsc xfce4-settings_4.6.3-1_amd64.deb to pool/main/x/xfce4-settings/xfce4-settings_4.6.3-1_amd64.deb xfce4-settings_4.6.3.orig.tar.gz to pool/main/x/xfce4-settings/xfce4-settings_4.6.3.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 cups 1.4.1-3 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 09:22:12 +0200 Source: cups Binary: libcups2 libcupsimage2 libcupscgi1 libcupsdriver1 libcupsmime1 libcupsppdc1 cups cups-client libcups2-dev libcupsimage2-dev libcupscgi1-dev libcupsdriver1-dev libcupsmime1-dev libcupsppdc1-dev cups-bsd cups-common cups-ppdc cups-dbg cupsys cupsys-client cupsys-common cupsys-bsd cupsys-dbg cupsddk Architecture: source all i386 Version: 1.4.1-3 Distribution: unstable Urgency: low Maintainer: Debian CUPS Maintainers pkg-cups-de...@lists.alioth.debian.org Changed-By: Martin Pitt mp...@debian.org Description: cups - Common UNIX Printing System(tm) - server cups-bsd - Common UNIX Printing System(tm) - BSD commands cups-client - Common UNIX Printing System(tm) - client programs (SysV) cups-common - Common UNIX Printing System(tm) - common files cups-dbg - Common UNIX Printing System(tm) - debugging symbols cups-ppdc - Common UNIX Printing System(tm) - PPD manipulation utilities cupsddk- Common UNIX Printing System (transitional package) cupsys - Common UNIX Printing System (transitional package) cupsys-bsd - Common UNIX Printing System (transitional package) cupsys-client - Common UNIX Printing System (transitional package) cupsys-common - Common UNIX Printing System (transitional package) cupsys-dbg - Common UNIX Printing System (transitional package) libcups2 - Common UNIX Printing System(tm) - Core library libcups2-dev - Common UNIX Printing System(tm) - Development files CUPS library libcupscgi1 - Common UNIX Printing System(tm) - CGI library libcupscgi1-dev - Common UNIX Printing System(tm) - Development files for CGI libra libcupsdriver1 - Common UNIX Printing System(tm) - Driver library libcupsdriver1-dev - Common UNIX Printing System(tm) - Development files driver librar libcupsimage2 - Common UNIX Printing System(tm) - Raster image library libcupsimage2-dev - Common UNIX Printing System(tm) - Development files CUPS image li libcupsmime1 - Common UNIX Printing System(tm) - MIME library libcupsmime1-dev - Common UNIX Printing System(tm) - Development files MIME library libcupsppdc1 - Common UNIX Printing System(tm) - PPD manipulation library libcupsppdc1-dev - Common UNIX Printing System(tm) - Development files PPD library Closes: 548246 Changes: cups (1.4.1-3) unstable; urgency=low . * Add disable-pie-mipsen.dpatch: Disable PIE on mipsen, its binutils segfaults with it. (Closes: #548246) Checksums-Sha1: 50e8c3d042ebfff7491c1d292bd2901b252560cd 2152 cups_1.4.1-3.dsc c51c911b6a210c3b1204a8cb94765bfa17265f42 403155 cups_1.4.1-3.diff.gz 90c6c1cffaf3e4cabe5d2abc0a0d6b614a1e2bc3 1439972 cups-common_1.4.1-3_all.deb db4a1e94646015d98fd9213508be8db1d493f38c 67924 cupsys_1.4.1-3_all.deb 508a0258c5fd470fb1e3e3e39720c94181ac1db0 67946 cupsys-client_1.4.1-3_all.deb 7a6d2c7fad386160bf44944e6f91e495451e28d6 67940 cupsys-common_1.4.1-3_all.deb 4274959b3d6156357f4e2ead0c6ea5b7ef522b97 67942 cupsys-bsd_1.4.1-3_all.deb 0ed076cd4ccb401e61ba028b81d8540525a89ede 67946 cupsys-dbg_1.4.1-3_all.deb 98a191353c179b8c5b9b33eabab466ecae0cf903 67898 cupsddk_1.4.1-3_all.deb ba96bdc41f432452b913fca1885cc76620a892ce 209654 libcups2_1.4.1-3_i386.deb 456cf24337d198fd805dd982cba3e7c1b7b59ddc 115042 libcupsimage2_1.4.1-3_i386.deb b2ea9eab8908b31823fb8b640ba1e6fbdb6e46aa 94070 libcupscgi1_1.4.1-3_i386.deb d036a69bb48392db260e3dea8ac9735905f25812 84932 libcupsdriver1_1.4.1-3_i386.deb d0f8f1be49a7eebfd23d51de0da7367914e364fd 78404 libcupsmime1_1.4.1-3_i386.deb 3554a0574eb5b3c62bfb029bf783d965a46fde21 124938 libcupsppdc1_1.4.1-3_i386.deb bfbad011ccec3a609d2008822a5a80252b96d50b 1873840 cups_1.4.1-3_i386.deb cb3bff48c00ce5bae41abc3bdc2fe6b21340c1ae 114268 cups-client_1.4.1-3_i386.deb d95d90b09df945604fe806b87a6a1100ba6c9a65 261550 libcups2-dev_1.4.1-3_i386.deb 71685354b05705d1745947dc890eb820b884c5a3 59738 libcupsimage2-dev_1.4.1-3_i386.deb 9fab204147eec9d49571dabcb87b133c0d11a1a8 98830 libcupscgi1-dev_1.4.1-3_i386.deb 80e41cbc09ba8a64e38525aebf73fc2e4ee4afe8 88464 libcupsdriver1-dev_1.4.1-3_i386.deb 78e05d74517ee8171617d6ba5324fc6a9e8ebfe0 79244 libcupsmime1-dev_1.4.1-3_i386.deb 2de230ca1407c1b88dc8c977cb0ced09b2f6f382 139614 libcupsppdc1-dev_1.4.1-3_i386.deb 6c9ff361164166cfbce7b02c574c9fb63a857732 35804 cups-bsd_1.4.1-3_i386.deb d43eb4375ca3b24dbef1076438a413cbed6a8b04 96284 cups-ppdc_1.4.1-3_i386.deb e70f75cdf19a8be2c474a0a7af40ed853f2b2d5c 86630 cups-dbg_1.4.1-3_i386.deb Checksums-Sha256: 6e71d93b0c2cd5ed409e2f2951da10fb1e125d25d16e80e4b2a17e98fd3bf802 2152 cups_1.4.1-3.dsc 178c81c13842458ff8cb5193c7a6b8ee56001313885d550d838a4a89d0919d81 403155 cups_1.4.1-3.diff.gz e6faab4ab4d3921bbbd5cc34d55c956c3ca87df1d8e69867670a574e475e2898 1439972 cups-common_1.4.1-3_all.deb 12ce7218025a7a88d2512f76a6f0fdff21b47f9ed3ea0632c596ce3d2dd81da1 67924 cupsys_1.4.1-3_all.deb ed46e449fc10afe20af4fb013bdaa28e371a01bac90cc28564d6af8f4785b23c
Accepted tmux 1.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 Sep 2009 09:52:15 +0200 Source: tmux Binary: tmux Architecture: source i386 Version: 1.0-1 Distribution: unstable Urgency: low Maintainer: Karl Ferdinand Ebert kfeb...@gmail.com Changed-By: Karl Ferdinand Ebert kfeb...@gmail.com Description: tmux - terminal multiplexer Closes: 531151 531497 548818 Changes: tmux (1.0-1) unstable; urgency=low . * New upstream release (Closes: #548818) + fixes add a setenv command like in Screen (Closes: #531151) + and Omit tmux-generated line-wrapping newlines from paste buffer (Closes: #531497) * Fix lintian info with 07_fix_hyphen.diff. Checksums-Sha1: 09e83aa4dcbf4f9d116ec552f50fe46b75d36b52 973 tmux_1.0-1.dsc 62bbea17e54cdacb48442e25eddf0463ab69ba61 215329 tmux_1.0.orig.tar.gz c2a42d7070658dbc1902ee764cc5c0378ffcc887 8939 tmux_1.0-1.diff.gz cce85eaf8bfbdd5f12f8bfc993a3915c53fcc76d 163280 tmux_1.0-1_i386.deb Checksums-Sha256: 75705671101c29ee182470c3f19a171edd4fea9753c5bea9d295c13c5c72be13 973 tmux_1.0-1.dsc f260fef8293b3eec795b21d3b561049b758c482dc6a04dba09fdce10ef8d3a6b 215329 tmux_1.0.orig.tar.gz ecb3d865e88d19f7de1096b4e5c98ca6dc1727d773479dd750489f8ff5cda2f2 8939 tmux_1.0-1.diff.gz feef0386a36a4cc453d6efa3303bf78b8442904114e7817829f0ec4301a14f25 163280 tmux_1.0-1_i386.deb Files: 3ee5628625c8add8a871ac41dd801749 973 admin optional tmux_1.0-1.dsc 716b12d9ea052f57d917bf2869d419df 215329 admin optional tmux_1.0.orig.tar.gz cea4a9665a532a6ad48068d88945eb30 8939 admin optional tmux_1.0-1.diff.gz a8332ea9f451ab16ec8192ca2fc69016 163280 admin optional tmux_1.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrBu5YACgkQ01u8mbx9AgpVWACeIxuJ8hyoid2jWa6jEZ3qHd+W TqUAoM7q4VQJ/NB7H8prsOwf+rRgBAD6 =YH8A -END PGP SIGNATURE- Accepted: tmux_1.0-1.diff.gz to pool/main/t/tmux/tmux_1.0-1.diff.gz tmux_1.0-1.dsc to pool/main/t/tmux/tmux_1.0-1.dsc tmux_1.0-1_i386.deb to pool/main/t/tmux/tmux_1.0-1_i386.deb tmux_1.0.orig.tar.gz to pool/main/t/tmux/tmux_1.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 krb5-auth-dialog 0.13-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 09:36:13 +0200 Source: krb5-auth-dialog Binary: krb5-auth-dialog Architecture: source i386 Version: 0.13-1 Distribution: unstable Urgency: low Maintainer: Guido Günther a...@sigxcpu.org Changed-By: Guido Günther a...@sigxcpu.org Description: krb5-auth-dialog - tray applet for reauthenticating kerberos tickets Changes: krb5-auth-dialog (0.13-1) unstable; urgency=low . * [b6cfb6e] Imported Upstream version 0.13 * [045601b] Drop 0001-remove-unused-GtkImage-with-duplicate-id.patch - fixed upstream. Checksums-Sha1: 6c01652d2b7db3f473c5a3c7c81787d893654646 1446 krb5-auth-dialog_0.13-1.dsc 62779268714cf53b4ffd0e8540608fadb1f5a4c5 755734 krb5-auth-dialog_0.13.orig.tar.gz c923e47e76ae7b973e8cd8fc548b6f0ec9fcdeb9 3883 krb5-auth-dialog_0.13-1.diff.gz 4821b24ac273a92f733115bde5df50f10df90a8f 292638 krb5-auth-dialog_0.13-1_i386.deb Checksums-Sha256: 5e114c777917494b6f5037d1357c8022b9a2f9109583b41a758964c075d73bc8 1446 krb5-auth-dialog_0.13-1.dsc a1bc235fd720795bf79d9783359b9a1f3edf102101c70c55ca1edd4f38a4d35e 755734 krb5-auth-dialog_0.13.orig.tar.gz f57fc5498c3a912e5a55650d3ff801a6a2f84a7ad0d4921c9f3a414d0c2e5dc4 3883 krb5-auth-dialog_0.13-1.diff.gz 665db3437a8f21e4a6bba3e086a8179d606268e2c2d71dc18b680d1c259ace29 292638 krb5-auth-dialog_0.13-1_i386.deb Files: 2be45e43bc1c9a21de6b01d6dee1e835 1446 gnome optional krb5-auth-dialog_0.13-1.dsc 1c34a974f80f0da7c3517f041437bd33 755734 gnome optional krb5-auth-dialog_0.13.orig.tar.gz 8538172da13daebd0f04c465fae29264 3883 gnome optional krb5-auth-dialog_0.13-1.diff.gz 524b9f0af7483da7139441b678c98eae 292638 gnome optional krb5-auth-dialog_0.13-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFKwbr7n88szT8+ZCYRAmgrAJ9BqgK9+rlNdT+d5R+YHqzIHYtPugCcDz89 tsj/kEEZ8+7JtbV8F2LUJJg= =E6lx -END PGP SIGNATURE- Accepted: krb5-auth-dialog_0.13-1.diff.gz to pool/main/k/krb5-auth-dialog/krb5-auth-dialog_0.13-1.diff.gz krb5-auth-dialog_0.13-1.dsc to pool/main/k/krb5-auth-dialog/krb5-auth-dialog_0.13-1.dsc krb5-auth-dialog_0.13-1_i386.deb to pool/main/k/krb5-auth-dialog/krb5-auth-dialog_0.13-1_i386.deb krb5-auth-dialog_0.13.orig.tar.gz to pool/main/k/krb5-auth-dialog/krb5-auth-dialog_0.13.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 x11proto-xcmisc 1.2.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 11:06:37 +0200 Source: x11proto-xcmisc Binary: x11proto-xcmisc-dev Architecture: source all Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Julien Cristau jcris...@debian.org Description: x11proto-xcmisc-dev - X11 XC-Miscellaneous extension wire protocol Changes: x11proto-xcmisc (1.2.0-1) unstable; urgency=low . * Bump debhelper compat level to 5. * Run autoreconf at build time. * Parse space-separated DEB_BUILD_OPTIONS, handle parallel=N. * Drop Pre-Depends on x11-common and Conflicts/Replaces on libxext-dev. This was only needed for upgrades from sarge. * Bump Standards-Version to 3.8.3. * New upstream release. Checksums-Sha1: 61948b5506d9ab74b1e6e3949d3c7966ffd2d7a7 1326 x11proto-xcmisc_1.2.0-1.dsc c254e590254d10b2f1e02d170314917723fe833d 56535 x11proto-xcmisc_1.2.0.orig.tar.gz 61db6af36e57785cb2446a3c449d46e5add07bc6 13358 x11proto-xcmisc_1.2.0-1.diff.gz dcaab7d9d773a1317a9a6aa713ac125c1db9de1d 3888 x11proto-xcmisc-dev_1.2.0-1_all.deb Checksums-Sha256: 82bd5171f30cf587262ff4636d1a876190ebf82e015d91da8259cf567696ace6 1326 x11proto-xcmisc_1.2.0-1.dsc 3e7ebffc1cdf93b371aa0db90775a630f66c3a77815059992c7b2789f119273e 56535 x11proto-xcmisc_1.2.0.orig.tar.gz 146be6850ed30d0f09fd96cf0e3588d4ebf71e1f86ac484465bd11ebb4269aba 13358 x11proto-xcmisc_1.2.0-1.diff.gz 5911956e64e9ff0afdd440e3aefb729b9ffd6b5bbba9782ae6da4b34fa7837b8 3888 x11proto-xcmisc-dev_1.2.0-1_all.deb Files: ae7644ba98dff721ce61cb43c9ac767a 1326 x11 optional x11proto-xcmisc_1.2.0-1.dsc bacfb0f3cb4d6e1a71770307bfdba129 56535 x11 optional x11proto-xcmisc_1.2.0.orig.tar.gz 51fb470affa81cdd0f85a0d34069a4a8 13358 x11 optional x11proto-xcmisc_1.2.0-1.diff.gz 2ac95c3b9b3ae3e06e7e2e29a6eb851c 3888 x11 optional x11proto-xcmisc-dev_1.2.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB0/0ACgkQmEvTgKxfcAwZFgCfdL042p69DowWyxKkqSJQysPz v8YAn1kF/qNGJRXQWpIXH0iz+kH7cIqe =FFLS -END PGP SIGNATURE- Accepted: x11proto-xcmisc-dev_1.2.0-1_all.deb to pool/main/x/x11proto-xcmisc/x11proto-xcmisc-dev_1.2.0-1_all.deb x11proto-xcmisc_1.2.0-1.diff.gz to pool/main/x/x11proto-xcmisc/x11proto-xcmisc_1.2.0-1.diff.gz x11proto-xcmisc_1.2.0-1.dsc to pool/main/x/x11proto-xcmisc/x11proto-xcmisc_1.2.0-1.dsc x11proto-xcmisc_1.2.0.orig.tar.gz to pool/main/x/x11proto-xcmisc/x11proto-xcmisc_1.2.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 clamtk 4.18-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 10:03:57 +0200 Source: clamtk Binary: clamtk Architecture: source all Version: 4.18-1 Distribution: unstable Urgency: low Maintainer: d.pale...@gmail.com Changed-By: David Paleino d.pale...@gmail.com Description: clamtk - graphical front-end for ClamAV Changes: clamtk (4.18-1) unstable; urgency=low . * New upstream version * debian/control: - removed dependency on Config::Tiny (libconfig-tiny-perl) - removed Build-Dependency on quilt - raised Build-Dependency on debhelper (= 7.0.50), to use dh7 override targets * debian/patches/* removed, merged upstream * debian/README.source removed * debian/rules: - removed quilt infrastructure - rewritten using dh7-tiny style * debian/docs added * debian/manpages added Checksums-Sha1: 4192be5a7cd6ea77aa6b37a5b652c68793a4140a 1170 clamtk_4.18-1.dsc a7fc43b422af89cbba83946c03cf4ddfb9a8b0b5 288542 clamtk_4.18.orig.tar.gz 363dc9e23d39784e24cb3ea2b970c8637387e51f 8730 clamtk_4.18-1.diff.gz 0a36166b1d37025090e1e1a42ca538e27943842c 165184 clamtk_4.18-1_all.deb Checksums-Sha256: 91625d782b2c28f824119a0ead6b3a2bce0629bb4e8d3af311bfc060522e8a8d 1170 clamtk_4.18-1.dsc 1f532a41244f347830af1c826f130669401c4d19aab3a98fe174692fbdfa8232 288542 clamtk_4.18.orig.tar.gz c0e30cd5fb68ff5d243ad4375f1685e748690f47a3e2907e8555f9f93543dc5d 8730 clamtk_4.18-1.diff.gz be2d92203bae406398f5f749ddfb44071c776421994ccb050ae1078a0bb65090 165184 clamtk_4.18-1_all.deb Files: 7e8151b229570d1053fe5bc3ac36c9c1 1170 utils optional clamtk_4.18-1.dsc ca12b2b87918d598e8cd49f79ad29e29 288542 utils optional clamtk_4.18.orig.tar.gz a3b814fa17256d5549f799e1c55ec900 8730 utils optional clamtk_4.18-1.diff.gz a6c3bcd07165361667d5183890e7f30e 165184 utils optional clamtk_4.18-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrBwEcACgkQ5qqQFxOSsXQiTACfcSrQhRL2gqNfdKE6Byyit+ny 6PYAoKZxSUBUrgjuk0fBDoUvYpMoBMnx =k34H -END PGP SIGNATURE- Accepted: clamtk_4.18-1.diff.gz to pool/main/c/clamtk/clamtk_4.18-1.diff.gz clamtk_4.18-1.dsc to pool/main/c/clamtk/clamtk_4.18-1.dsc clamtk_4.18-1_all.deb to pool/main/c/clamtk/clamtk_4.18-1_all.deb clamtk_4.18.orig.tar.gz to pool/main/c/clamtk/clamtk_4.18.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 x11proto-xf86vidmode 2.2.99.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 11:49:35 +0200 Source: x11proto-xf86vidmode Binary: x11proto-xf86vidmode-dev Architecture: source all Version: 2.2.99.1-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Julien Cristau jcris...@debian.org Description: x11proto-xf86vidmode-dev - X11 Video Mode extension wire protocol Changes: x11proto-xf86vidmode (2.2.99.1-1) experimental; urgency=low . * Bump debhelper compat level to 5. * Run autoreconf at build time. * Drop Pre-Depends on x11-common and Conflicts/Replaces on xlibs-static-dev and libxxf86vidmode-dev. This was only needed for upgrades from sarge. * Parse space-separated DEB_BUILD_OPTIONS, handle parallel=N. * Bump Standards-Version to 3.8.3. * New upstream release. + Xlib header moved to libXxf86vm * Break old libxxf86vm-dev Checksums-Sha1: bcee237d132183c24dc9b4c160295abe2b922467 1397 x11proto-xf86vidmode_2.2.99.1-1.dsc 14af282b85d1d74819e6efcf2ba43276b1b791dc 58811 x11proto-xf86vidmode_2.2.99.1.orig.tar.gz 91538549ae0f5dedeb91d58f0c9a483463350659 13532 x11proto-xf86vidmode_2.2.99.1-1.diff.gz 55ac02cca4c4f18008c2ca9ebc26f59d6cb2e220 5796 x11proto-xf86vidmode-dev_2.2.99.1-1_all.deb Checksums-Sha256: a34f37ee93864c08d5cbe9ce1144ecd850c500a19e112ae3a625bce7bfe32fe0 1397 x11proto-xf86vidmode_2.2.99.1-1.dsc 16685d9142a600f1b7718425dfcca35f4925fd709bcdec04901bdb00a5de 58811 x11proto-xf86vidmode_2.2.99.1.orig.tar.gz 4f7d3632ef3e9f88bd6ff13dd0fb1866dff3d56d6be5f21cefb3e146e0741b98 13532 x11proto-xf86vidmode_2.2.99.1-1.diff.gz 01ed670972a1d0a1acc8f08518a3ba23a37f7196ff53dd5d4ac27399bab79df3 5796 x11proto-xf86vidmode-dev_2.2.99.1-1_all.deb Files: 2b049444c2e7f3078ed36ff62265f0aa 1397 x11 optional x11proto-xf86vidmode_2.2.99.1-1.dsc b7fae44030525f67f09ac900e0fad7ba 58811 x11 optional x11proto-xf86vidmode_2.2.99.1.orig.tar.gz 415ad1c497bde31281d1ee06fa3315c7 13532 x11 optional x11proto-xf86vidmode_2.2.99.1-1.diff.gz aa03d17bc51df343c6f750852989a134 5796 x11 optional x11proto-xf86vidmode-dev_2.2.99.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB2IIACgkQmEvTgKxfcAx08gCfa+SjBKHoJHFQt3S9Knj6i0IC QhwAoM/ZnEbkTzQjJRuzV3tdrkKna0DE =Vd/R -END PGP SIGNATURE- Accepted: x11proto-xf86vidmode-dev_2.2.99.1-1_all.deb to pool/main/x/x11proto-xf86vidmode/x11proto-xf86vidmode-dev_2.2.99.1-1_all.deb x11proto-xf86vidmode_2.2.99.1-1.diff.gz to pool/main/x/x11proto-xf86vidmode/x11proto-xf86vidmode_2.2.99.1-1.diff.gz x11proto-xf86vidmode_2.2.99.1-1.dsc to pool/main/x/x11proto-xf86vidmode/x11proto-xf86vidmode_2.2.99.1-1.dsc x11proto-xf86vidmode_2.2.99.1.orig.tar.gz to pool/main/x/x11proto-xf86vidmode/x11proto-xf86vidmode_2.2.99.1.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 liblocale-gettext-perl 1.05-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Sep 2009 12:21:42 +0200 Source: liblocale-gettext-perl Binary: liblocale-gettext-perl Architecture: source i386 Version: 1.05-6 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Raphaël Hertzog hert...@debian.org Description: liblocale-gettext-perl - Using libc functions for internationalization in Perl Closes: 548860 Changes: liblocale-gettext-perl (1.05-6) unstable; urgency=low . * The -d option of dh_perl was lost by mistake while converting to tiny rules files. Re-add it. Closes: #548860 Checksums-Sha1: 4ba04fc6cfdb4a5a72df6fc91883d3488585464a 1721 liblocale-gettext-perl_1.05-6.dsc 5f7a7cdc4ffea6f73ab96893878adb6af4d13115 4703 liblocale-gettext-perl_1.05-6.diff.gz 0826a79c0ba96e62a667230a12e81b4eb17fd76f 21596 liblocale-gettext-perl_1.05-6_i386.deb Checksums-Sha256: 4571bb19edb5a31e964735dbb1eb0dc69bc36490c74fdcfa6dc039434015b1da 1721 liblocale-gettext-perl_1.05-6.dsc a0a5052599de91fde773058a7a961dc020dfad9e68ba81a18e9f774a5a547e5d 4703 liblocale-gettext-perl_1.05-6.diff.gz af656f704e59ba8d03609ace111d8297a1d6405b329b663ebd019505a8cd26a3 21596 liblocale-gettext-perl_1.05-6_i386.deb Files: 27fac4dc51dc8019732412eb55d0158b 1721 perl required liblocale-gettext-perl_1.05-6.dsc 50b663a079dc58422b6d93385511c3d0 4703 perl required liblocale-gettext-perl_1.05-6.diff.gz a71c3dadecdf1b64b4cb050f91e032b5 21596 perl required liblocale-gettext-perl_1.05-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Signed by Raphael Hertzog iQEcBAEBCAAGBQJKweFYAAoJEAOIHavrwpq57j0IALgbQK5ZAJADZaIAnqis73sL PaNYnf0gE0vZSaLaNrjakSQduL6RP/uGfMsgVb4udRNcNCYxqsISLonT7upXjF8B doVDTK1oCN+PI4vrMDzeAsp0X42JNT3xPjK1sUiaGGvc2Khc17NgCTRid6TmjO5x X/R/HbKk2nAsPu2DItDA1ILF9Rzn8qHaeic6crR9WoXeAuBBd8ZjkvEEDSNAdyOB UmKFv3mBY1aPZqp4or57AMBtGi+nYHtF/NcMpJUdQARmMGlfQ++e7yaqSNjErJwV 03I3lc+6t/nqKsAjIhhwoshABQRme44TCAUZn4S2Gi+6GcNEpoPNrJdc9QVGw78= =LCkn -END PGP SIGNATURE- Accepted: liblocale-gettext-perl_1.05-6.diff.gz to pool/main/libl/liblocale-gettext-perl/liblocale-gettext-perl_1.05-6.diff.gz liblocale-gettext-perl_1.05-6.dsc to pool/main/libl/liblocale-gettext-perl/liblocale-gettext-perl_1.05-6.dsc liblocale-gettext-perl_1.05-6_i386.deb to pool/main/libl/liblocale-gettext-perl/liblocale-gettext-perl_1.05-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 nodm 0.6-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Sep 2009 11:27:25 +0100 Source: nodm Binary: nodm Architecture: source amd64 Version: 0.6-2 Distribution: unstable Urgency: low Maintainer: Debian FreeSmartphone.Org Team pkg-fso-ma...@lists.alioth.debian.org Changed-By: Enrico Zini enr...@debian.org Description: nodm - automatic display manager Closes: 538365 538904 540873 544907 548104 548776 Changes: nodm (0.6-2) unstable; urgency=low . * Added kdb to initscript Should-Start:. Closes: #548104. Thanks to Michael Schutte. * Added hal and bluetooth to initscript Should-Start. Closes: #548776. * Updated German translation, thanks Thomas Mueller. Closes: #544907. * Updated French translation, thanks Christian Perrier. Closes: #540873. * Updated Portuguese translation, thanks Miguel Figueiredo. Closes: #538904. * Updated Russian translation, thanks Yuri Kozlov. Closes: #538365. Checksums-Sha1: 5d5ab71f7c747ecb8630b50f715dfbbeac55f0e5 1815 nodm_0.6-2.dsc 5c404621b7a65abe1131f0e7fcc331d1165a4501 16621 nodm_0.6-2.diff.gz 0a8a37413c0399fe89c32f6ab3c50f223524ab4e 24540 nodm_0.6-2_amd64.deb Checksums-Sha256: 11062772b7a96bca670c1228d2b28d4968b2359e5c90ab8fa9c827300b2b3eeb 1815 nodm_0.6-2.dsc 5b278595e0c3b11ae23da74746435c59fe13ac6a9fe8b183be49307594da750c 16621 nodm_0.6-2.diff.gz 7739e8b7a7f61174aa97fb1acded5da6bd817b5a96e640d56cfde08a0a597b30 24540 nodm_0.6-2_amd64.deb Files: e9bbdff27ff6a2d14a2ae6d6c4a4c9b6 1815 misc extra nodm_0.6-2.dsc 76f0454de0e45c72645519e265a3efb3 16621 misc extra nodm_0.6-2.diff.gz dd02b82a9b5cb916ac72409b3daabe27 24540 misc extra nodm_0.6-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCAAGBQJKwekpAAoJEB5qw/OH8O2sxVUP/2dOVl4B/dwXeFUsWqikoZ5H Kt1MmlWsnsUQLxjt3qUTYpK4EEqssGMrfbpZ+ZhgMT24/4fgto5QNUYjWoTN5uZH y7umqGBJIEFmCcOO7MPDwWURXwNNj9Try4PtuFPZLIjl6ivYQ5G7hs4yPkIhzgzC wvv/n0ATMASD1Ab4UqDei+JNY8GhqxbXPd/qj0Zv4xkLzF+H/GlO00XCBu+NGUDb nDrjdqxfrHHtTKRARkt3xzIVMR81sQfRqBFyHz2ZJvO1oMfEdB7tZ+CKSKFiJa5G k5TGUjxqhJlV00B9PAbZvQiNm5NkZLw+FpcFn8o/VTVWoCWZElPYPtw4Yq4iCMsN fZQfKPXU8YYYnAa3IYyqes/dOzxKm4fR2LNFuwp02quqbUSJjcOn8J0x7sUPI0aZ i3UfeDZ+jRM65uhrjjc418w1d0WuKrA9zRuSsWRUvqz8YE/LVAOtlVGPpgsYqX1o vftomZrHG12WTt/ckS6iaIrcFhzpLZeiSDBA1u8KZtEt3X3YPV5v17A5RTXm9x5S UVB1m8zO+x3OrOFQfWdkcgNQDfNUWcZv5kwiVskjHsNAndZ4oTZh1bpPNidc3AZ7 k9Lc62ljiCtm4ArnXfZOQEZEkPNp1IwKxI06gfsaKs3LqdKGR2TCgA9g71E8JswS YfKRxtY7wr8J48bmfhPE =yXuJ -END PGP SIGNATURE- Accepted: nodm_0.6-2.diff.gz to pool/main/n/nodm/nodm_0.6-2.diff.gz nodm_0.6-2.dsc to pool/main/n/nodm/nodm_0.6-2.dsc nodm_0.6-2_amd64.deb to pool/main/n/nodm/nodm_0.6-2_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 imaprowl 1.2.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 19:39:15 +0900 Source: imaprowl Binary: imaprowl Architecture: source all Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Takuo KITAME kit...@debian.org Changed-By: Takuo KITAME kit...@debian.org Description: imaprowl - IMAP new mail notification utility for iPhone using Prowl Public Changes: imaprowl (1.2.0-1) unstable; urgency=low . * New upstream release. Checksums-Sha1: d45d659766f2a9fe51ef22b373efc1b1cc587f48 1017 imaprowl_1.2.0-1.dsc 9e8fbf0862190b087c6a97471d7615af01e8f683 20017 imaprowl_1.2.0.orig.tar.gz 778fd464dadb8c724d97348f3fd77edc0c337373 20 imaprowl_1.2.0-1.diff.gz 538a3def34f4ba5cd2698591543b6d5b579b94b5 14136 imaprowl_1.2.0-1_all.deb Checksums-Sha256: cf64f7c526e559dfdb9005485be97b102979c0fd2b10b458854b4f376c162527 1017 imaprowl_1.2.0-1.dsc 876be5b50120693845ce6367d77edbd7d777f8057321039e73e03367a3114a7f 20017 imaprowl_1.2.0.orig.tar.gz d76e53fbb023c7838a245c66a7a8c7f94f530aaa1f2fc4cabd0cf3f8d3679338 20 imaprowl_1.2.0-1.diff.gz b5b4341095e0257f799d872ce445a1782a88910e364a848b52133f67aee2024f 14136 imaprowl_1.2.0-1_all.deb Files: e2108860d9fe313a595c931661572fb1 1017 mail optional imaprowl_1.2.0-1.dsc c1bc6a9191e5911371c74d776171dc83 20017 mail optional imaprowl_1.2.0.orig.tar.gz 0166e69fd3f40659c6096c6d17820e8c 20 mail optional imaprowl_1.2.0-1.diff.gz 0a0df9e8c94760022df00dab48997bd3 14136 mail optional imaprowl_1.2.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFKweboU+WZW1FVMwoRAkHRAJ9tcNXsaDBYhWmPwUDLkpiu8M0CCgCaAzr5 QyhtiqiOgcgMAZc0YK77uhg= =xeja -END PGP SIGNATURE- Accepted: imaprowl_1.2.0-1.diff.gz to pool/main/i/imaprowl/imaprowl_1.2.0-1.diff.gz imaprowl_1.2.0-1.dsc to pool/main/i/imaprowl/imaprowl_1.2.0-1.dsc imaprowl_1.2.0-1_all.deb to pool/main/i/imaprowl/imaprowl_1.2.0-1_all.deb imaprowl_1.2.0.orig.tar.gz to pool/main/i/imaprowl/imaprowl_1.2.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 libcitadel 7.66-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 12:14:04 +0200 Source: libcitadel Binary: libcitadel2 libcitadel2-dbg libcitadel-dev Architecture: source amd64 Version: 7.66-1 Distribution: unstable Urgency: low Maintainer: Debian Citadel Team pkg-citadel-de...@lists.alioth.debian.org Changed-By: Michael Meskes mes...@debian.org Description: libcitadel-dev - Development files for libcitadel2 libcitadel2 - Citadel toolbox libcitadel2-dbg - Debugging symbols for libcitadel2 Changes: libcitadel (7.66-1) unstable; urgency=low . * New upstream version. Checksums-Sha1: 99b7b21f6d108ef1cecf027d8093b85fb3a7a780 1337 libcitadel_7.66-1.dsc e0ce8d423a7f438626984b28865ef2a61d6bb7af 523634 libcitadel_7.66.orig.tar.gz dd62c2e79da3071f2086bfe572c63ee41c0b45a4 6857 libcitadel_7.66-1.diff.gz 587e85b6473a875d94eacdbc7907913335c318e3 60396 libcitadel2_7.66-1_amd64.deb 141a141013d287a8057c4f44ed0e5094083cfb4d 94162 libcitadel2-dbg_7.66-1_amd64.deb a4323ee79cd19a93ba3d001b85724981b87fd9f2 70746 libcitadel-dev_7.66-1_amd64.deb Checksums-Sha256: 0788dc7c9f9d3529b5d82e1a22548502c39604bc760adec07c4704b506e27f8b 1337 libcitadel_7.66-1.dsc 81e427be752097a961a9d63eea26e60186815d0cef8c958c09e1071ba33575cd 523634 libcitadel_7.66.orig.tar.gz 17784a417e62cf5d441ec8180e27428a480c79c7739183da61f955d42b8d7711 6857 libcitadel_7.66-1.diff.gz c4eab94fb4e891d5ab0d5045790c40c5f5130b09e8679c40f91b602d2d555e64 60396 libcitadel2_7.66-1_amd64.deb 56d825b9ad101cd9da2d1c9768788a1b8ec1699f04e4a784aa20a9e214b1a3f1 94162 libcitadel2-dbg_7.66-1_amd64.deb 5c14acb18950f868d17507571e02d961f628ecddb0df65b6cad2ca471dd38bf7 70746 libcitadel-dev_7.66-1_amd64.deb Files: 3bb003e3cb4e9ee2385753d79b440f96 1337 libs extra libcitadel_7.66-1.dsc a3873674b3fc700d887442c157853681 523634 libs extra libcitadel_7.66.orig.tar.gz e189c8f3b4795163e2edc11c6ac84d55 6857 libs extra libcitadel_7.66-1.diff.gz 24bb108b8e6cb9f38578005621e7b91a 60396 libs extra libcitadel2_7.66-1_amd64.deb 937f998e7e71918e3bcc54803b2da8e3 94162 debug extra libcitadel2-dbg_7.66-1_amd64.deb 2a85d479fea4dd4c6381be8708c5585e 70746 libdevel extra libcitadel-dev_7.66-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFKweBjVkEm8inxm9ERAn4RAJ91pUkHBSFDD1WJCRssYeFqpxVT/gCbB6Pi 6iuEGY/0vglLirQ34penyM4= =75mb -END PGP SIGNATURE- Accepted: libcitadel-dev_7.66-1_amd64.deb to pool/main/libc/libcitadel/libcitadel-dev_7.66-1_amd64.deb libcitadel2-dbg_7.66-1_amd64.deb to pool/main/libc/libcitadel/libcitadel2-dbg_7.66-1_amd64.deb libcitadel2_7.66-1_amd64.deb to pool/main/libc/libcitadel/libcitadel2_7.66-1_amd64.deb libcitadel_7.66-1.diff.gz to pool/main/libc/libcitadel/libcitadel_7.66-1.diff.gz libcitadel_7.66-1.dsc to pool/main/libc/libcitadel/libcitadel_7.66-1.dsc libcitadel_7.66.orig.tar.gz to pool/main/libc/libcitadel/libcitadel_7.66.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 minbif 1:1.0~beta+git20090929+fa518a5-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 11:41:44 +0200 Source: minbif Binary: minbif minbif-dbg Architecture: source i386 Version: 1:1.0~beta+git20090929+fa518a5-1 Distribution: unstable Urgency: low Maintainer: Sebastien Delafond s...@debian.org Changed-By: Sebastien Delafond s...@debian.org Description: minbif - Re-use code from Pidgin to provide an IRC-to-other-IM-networks ga minbif-dbg - Re-use code from Pidgin to provide an IRC-to-other-IM-networks ga Changes: minbif (1:1.0~beta+git20090929+fa518a5-1) unstable; urgency=low . * New development snapshot (default upstream config file now forces daemon mode). Checksums-Sha1: 8ed4e10e86f97ac901044df88a48abe6ec0536a0 1206 minbif_1.0~beta+git20090929+fa518a5-1.dsc 44aa04977e9c7dcd51b251eef4440156480e0efc 99546 minbif_1.0~beta+git20090929+fa518a5.orig.tar.gz 454424f97baaadaab5db7eac6c90d9216b11d493 5426 minbif_1.0~beta+git20090929+fa518a5-1.diff.gz 3b897cc7c0f2b0f16ef98fdede80b9c384ba995a 212488 minbif_1.0~beta+git20090929+fa518a5-1_i386.deb 2135f64bcfa6fb1d5aa5cc8d7e99326bead9f888 1042950 minbif-dbg_1.0~beta+git20090929+fa518a5-1_i386.deb Checksums-Sha256: 927f39c669a90d0a18ae01f288c0174d1fb8e76423fa8721ad7bde6149ec7a2b 1206 minbif_1.0~beta+git20090929+fa518a5-1.dsc c2b6db84e2cf6af4225b0ffe32df992c6e10dfd7c8985a74a65f041fcdb87978 99546 minbif_1.0~beta+git20090929+fa518a5.orig.tar.gz 581979b8ff186427ebacfc08a0c83526d05901a4e8d1eb702cf97243c4d9d004 5426 minbif_1.0~beta+git20090929+fa518a5-1.diff.gz 1b0523c0fcdce87bc6145c8a4bd616ed6216013395d350481bcd9438dad87d76 212488 minbif_1.0~beta+git20090929+fa518a5-1_i386.deb 3a03879d4035d098ebbd8b0e2e4a76c0efe296ba32458e91cde2a99ea391200b 1042950 minbif-dbg_1.0~beta+git20090929+fa518a5-1_i386.deb Files: e9ffd1df263acf33ee0a3e2759f367e2 1206 net optional minbif_1.0~beta+git20090929+fa518a5-1.dsc 4e85395a26736429cb3a6814c61074e7 99546 net optional minbif_1.0~beta+git20090929+fa518a5.orig.tar.gz bdefba80b7ad0bfb0037e4053e5f3841 5426 net optional minbif_1.0~beta+git20090929+fa518a5-1.diff.gz cce312afe7e5f44e86bed75c3d7e3f10 212488 net optional minbif_1.0~beta+git20090929+fa518a5-1_i386.deb 64026ee0ce499421054f5a1c349ec0aa 1042950 debug extra minbif-dbg_1.0~beta+git20090929+fa518a5-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB2q8ACgkQiZgNKcDdyD9ZWQCfQ1NQNjeW1Q0A8ecoAFyEFbEz cUIAn2WuBJSFwA3GzrTFH/lJ+qEhC7T0 =f1NB -END PGP SIGNATURE- Accepted: minbif-dbg_1.0~beta+git20090929+fa518a5-1_i386.deb to pool/main/m/minbif/minbif-dbg_1.0~beta+git20090929+fa518a5-1_i386.deb minbif_1.0~beta+git20090929+fa518a5-1.diff.gz to pool/main/m/minbif/minbif_1.0~beta+git20090929+fa518a5-1.diff.gz minbif_1.0~beta+git20090929+fa518a5-1.dsc to pool/main/m/minbif/minbif_1.0~beta+git20090929+fa518a5-1.dsc minbif_1.0~beta+git20090929+fa518a5-1_i386.deb to pool/main/m/minbif/minbif_1.0~beta+git20090929+fa518a5-1_i386.deb minbif_1.0~beta+git20090929+fa518a5.orig.tar.gz to pool/main/m/minbif/minbif_1.0~beta+git20090929+fa518a5.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 minbif 1:1.0~beta+git20090928+1aadbc4-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 28 Sep 2009 19:49:49 +0200 Source: minbif Binary: minbif minbif-dbg Architecture: source i386 Version: 1:1.0~beta+git20090928+1aadbc4-1 Distribution: unstable Urgency: low Maintainer: Sebastien Delafond s...@debian.org Changed-By: Sebastien Delafond s...@debian.org Description: minbif - Re-use code from Pidgin to provide an IRC-to-other-IM-networks ga minbif-dbg - Re-use code from Pidgin to provide an IRC-to-other-IM-networks ga Changes: minbif (1:1.0~beta+git20090928+1aadbc4-1) unstable; urgency=low . * New development snapshot. * Added init script for daemon-fork mode. * Fixed devscripts (care about commands, and allow debhelper paragraphs). * Added debug package. * Don't restart the daemon when upgrading, let the administrator handle this manually. * Thanks Marc Dequènes (Duck) d...@duckcorp.org for all the aforementioned contributions. * Deprecate inetd mode in favor of daemon mode. Checksums-Sha1: da50042f392d4a74f2fc930dc3b77636cccda84b 1206 minbif_1.0~beta+git20090928+1aadbc4-1.dsc f305dc6590f85b6de4eab11b205f7390eb81f2e5 99516 minbif_1.0~beta+git20090928+1aadbc4.orig.tar.gz 002cc4ff99e862d4aca5516f1a823b7eea40a643 5380 minbif_1.0~beta+git20090928+1aadbc4-1.diff.gz 8a074aa549375745b668656a5d47b073d2a64382 212396 minbif_1.0~beta+git20090928+1aadbc4-1_i386.deb bd857a2cf9fecf52054a840ea72b44199bd71795 1042906 minbif-dbg_1.0~beta+git20090928+1aadbc4-1_i386.deb Checksums-Sha256: dd72779fab0edd5b8390478a1797ce36fcbdbe625e20de8c8e461615371a9fcd 1206 minbif_1.0~beta+git20090928+1aadbc4-1.dsc 378b8a49a468731eea0e26a5daad8c2d3073a780eb4e8b2e559edc85052f56f0 99516 minbif_1.0~beta+git20090928+1aadbc4.orig.tar.gz 2003af1a83499a6a59cbe07937b4a4c52416c10c44756dec93311634191b06b6 5380 minbif_1.0~beta+git20090928+1aadbc4-1.diff.gz c95fcbaed08c9ec605bc0644ea5cdacd67fb3dc8a46079b47042e6b25b5a0ee0 212396 minbif_1.0~beta+git20090928+1aadbc4-1_i386.deb dfd214868ec4161ea8d55ced4206b4550f7cdffcb73ca4b1c571a25df5420c9e 1042906 minbif-dbg_1.0~beta+git20090928+1aadbc4-1_i386.deb Files: 51a0db51d98e8bee2cd1b0a0fe8628b5 1206 net optional minbif_1.0~beta+git20090928+1aadbc4-1.dsc 2cfdf36cf2181a513d3bdb0131c47401 99516 net optional minbif_1.0~beta+git20090928+1aadbc4.orig.tar.gz b086512586389f3cedf51bcd21c16cf8 5380 net optional minbif_1.0~beta+git20090928+1aadbc4-1.diff.gz c4974a45bd17bb54a4b61ba37febc6e6 212396 net optional minbif_1.0~beta+git20090928+1aadbc4-1_i386.deb ddcdc6ae9af73a00331e08ef83f6c813 1042906 debug extra minbif-dbg_1.0~beta+git20090928+1aadbc4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrA+NAACgkQiZgNKcDdyD//dgCbBkTLbyxgDf5TPCE/rg16QEcu F6sAoNUDoCihAkSxuU66KdRObxWxkmNU =nJ4y -END PGP SIGNATURE- Accepted: minbif-dbg_1.0~beta+git20090928+1aadbc4-1_i386.deb to pool/main/m/minbif/minbif-dbg_1.0~beta+git20090928+1aadbc4-1_i386.deb minbif_1.0~beta+git20090928+1aadbc4-1.diff.gz to pool/main/m/minbif/minbif_1.0~beta+git20090928+1aadbc4-1.diff.gz minbif_1.0~beta+git20090928+1aadbc4-1.dsc to pool/main/m/minbif/minbif_1.0~beta+git20090928+1aadbc4-1.dsc minbif_1.0~beta+git20090928+1aadbc4-1_i386.deb to pool/main/m/minbif/minbif_1.0~beta+git20090928+1aadbc4-1_i386.deb minbif_1.0~beta+git20090928+1aadbc4.orig.tar.gz to pool/main/m/minbif/minbif_1.0~beta+git20090928+1aadbc4.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 flashrom 0.9.1+r736-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 13:09:58 +0200 Source: flashrom Binary: flashrom Architecture: source i386 Version: 0.9.1+r736-1 Distribution: unstable Urgency: low Maintainer: Uwe Hermann u...@debian.org Changed-By: Uwe Hermann u...@debian.org Description: flashrom - Identify, read, write, erase, and verify BIOS/ROM/flash chips Changes: flashrom (0.9.1+r736-1) unstable; urgency=low . * New upstream release. Checksums-Sha1: ddd75f7a27552bf296c992d53ba7e70df35ca02c 1127 flashrom_0.9.1+r736-1.dsc 123d4d996b5678b373af3e453a78b7606b3e5257 194613 flashrom_0.9.1+r736.orig.tar.gz e887b49230d5a8188a9ac50530df4b645717844c 4416 flashrom_0.9.1+r736-1.diff.gz 5def504e47eb9045c15d6d1422ff752d6b998bde 149018 flashrom_0.9.1+r736-1_i386.deb Checksums-Sha256: 9fc2e6c1e3603221ba587d0dea5f8c3615be45ff54b5f4f1bbffe520ab10c444 1127 flashrom_0.9.1+r736-1.dsc 570f014a07184332c876165751e302d2f2c4d0f2cce2f36764dce90856493526 194613 flashrom_0.9.1+r736.orig.tar.gz 54d05206b90d6976ce5668f7ee28b6b310b438623f28450809bf6723e39459c0 4416 flashrom_0.9.1+r736-1.diff.gz 35609f1f75ba0e3c77fa5036d2bbbd90e5af780f672abc22e2607a1fa3c83eaf 149018 flashrom_0.9.1+r736-1_i386.deb Files: 0fd12dbd5c9687b087c673fc4ff69e0b 1127 electronics extra flashrom_0.9.1+r736-1.dsc f90e73d5300d954ab51416010711d9a8 194613 electronics extra flashrom_0.9.1+r736.orig.tar.gz 9f05f382f82df50220377c8c4b351d05 4416 electronics extra flashrom_0.9.1+r736-1.diff.gz 0587d94881279efe4461c99875d6ef92 149018 electronics extra flashrom_0.9.1+r736-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB7IMACgkQXdVoV3jWIbR0fgCffaVHPwN57vJt2JcqiSdlzJzv NCUAn3bvL/OnsmU1WxLwU0VZZSJU7L3q =F2+o -END PGP SIGNATURE- Accepted: flashrom_0.9.1+r736-1.diff.gz to pool/main/f/flashrom/flashrom_0.9.1+r736-1.diff.gz flashrom_0.9.1+r736-1.dsc to pool/main/f/flashrom/flashrom_0.9.1+r736-1.dsc flashrom_0.9.1+r736-1_i386.deb to pool/main/f/flashrom/flashrom_0.9.1+r736-1_i386.deb flashrom_0.9.1+r736.orig.tar.gz to pool/main/f/flashrom/flashrom_0.9.1+r736.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 imagemagick 7:6.5.5.3-1exp1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.8 Date: Mon, 28 Sep 2009 20:00:55 -0300 Source: imagemagick Binary: imagemagick imagemagick-dbg imagemagick-doc libmagickcore2 libmagickcore2-extra libmagickcore-dev libmagickwand2 libmagickwand-dev libmagick++2 libmagick++-dev perlmagick Architecture: source i386 all Version: 7:6.5.5.3-1exp1 Distribution: experimental Urgency: low Maintainer: ImageMagick Packaging Team pkg-gmagick-im-t...@lists.alioth.debian.org Changed-By: Nelson A. de Oliveira nao...@debian.org Description: imagemagick - image manipulation programs imagemagick-dbg - debugging symbols for ImageMagick imagemagick-doc - document files of ImageMagick libmagick++-dev - object-oriented C++ interface to ImageMagick - development files libmagick++2 - object-oriented C++ interface to ImageMagick libmagickcore-dev - low-level image manipulation library - development files libmagickcore2 - low-level image manipulation library libmagickcore2-extra - low-level image manipulation library - extra codecs libmagickwand-dev - image manipulation library - development files libmagickwand2 - image manipulation library perlmagick - Perl interface to the ImageMagick graphics routines Closes: 478538 524613 Changes: imagemagick (7:6.5.5.3-1exp1) experimental; urgency=low . * Split SVG, WMF, OpenEXR, DjVu and Graphviz coders into a new libmagickcore2-extra package: - Removed libmagickcore2 circular Depends on libmagickwand2 (Closes: #524613); - Removed dependency on gtk libs (Closes: #478538). A big thank you to Nick Wellnhofer wellnho...@aevum.de! * Sorted Build-Depends and Depends in debian/control. Checksums-Sha1: a821747eb8ea70ccd7ac582cc3da1b46b8faa610 1877 imagemagick_6.5.5.3-1exp1.dsc 0745351eae6ae971f57996516ad1e219559c48cb 36602 imagemagick_6.5.5.3-1exp1.diff.gz 8387e0516f5963a32dbe820d6e72891f8e3031cd 6 imagemagick_6.5.5.3-1exp1_i386.deb df285db9f162f64ab01bbee8522b1cae66b88761 3409830 imagemagick-dbg_6.5.5.3-1exp1_i386.deb d6d7b9ad1aa1e724e03fdc4e4f235b47163d7545 4142134 imagemagick-doc_6.5.5.3-1exp1_all.deb 968a1e107b112271fbb8d525a375953adaaeb0cb 1659036 libmagickcore2_6.5.5.3-1exp1_i386.deb 2d7f2de2ceb26caa7c5bac84a6ebeae0fc2ae97b 112358 libmagickcore2-extra_6.5.5.3-1exp1_i386.deb 7efc5095676717de30aad336124758a8f615da0d 3528240 libmagickcore-dev_6.5.5.3-1exp1_i386.deb 14d6842d6b8beaed70ea8c61d4deb0cd240b4225 353584 libmagickwand2_6.5.5.3-1exp1_i386.deb e6b9163a322a328cc036e9eaa3e0fa50012da4fe 431906 libmagickwand-dev_6.5.5.3-1exp1_i386.deb 428a43cf5bbf05331228b5788febbff88293377c 205222 libmagick++2_6.5.5.3-1exp1_i386.deb 628e8137a8b1dee20a55ec8ac9ad74cb34516c95 233584 libmagick++-dev_6.5.5.3-1exp1_i386.deb c32756dfeed2592f8d4bebbd8bfcda3ec9c2f865 208076 perlmagick_6.5.5.3-1exp1_i386.deb Checksums-Sha256: 4f57d251a083df6e307e42df6f03933e39ba8b213cb59f2384c0d0d9c725c9a4 1877 imagemagick_6.5.5.3-1exp1.dsc 380844f8ed7a3001ffe4b0721818e6c91d3abfbf99eb3f2330fad35cd03a0476 36602 imagemagick_6.5.5.3-1exp1.diff.gz a4c93dae76560fb6aa2522758503c2a3e165be19714d4f0bc5e958e46ea40a78 6 imagemagick_6.5.5.3-1exp1_i386.deb 528c5639b8ddfd0452c2f944411d4feb83623c53bea772204a661bdbfa297547 3409830 imagemagick-dbg_6.5.5.3-1exp1_i386.deb 6cda187a567614372dbe2c2443905acf844c7e70da87eee91b19dfd731878aeb 4142134 imagemagick-doc_6.5.5.3-1exp1_all.deb 7dbc2796e660ad981e8e2dcebd175927134f81860b47744a957123bc09f658c8 1659036 libmagickcore2_6.5.5.3-1exp1_i386.deb 82f6b1dac1ba4928eb74d60727d4168e25e27ffa7c928b14acc89d8e2e3f2d2f 112358 libmagickcore2-extra_6.5.5.3-1exp1_i386.deb d45b1664f1f33a8e7b4e1fab7917362c34732b46040e0539f649f6a8e1d06ab8 3528240 libmagickcore-dev_6.5.5.3-1exp1_i386.deb 73bdfd78453beba6d5c8c86ab4bd5ecff2a171da3a02d29dedef9332e09439cf 353584 libmagickwand2_6.5.5.3-1exp1_i386.deb 3963c0235c10440de29363155ff396e210643ce27557406de4b1c9c7acbb036a 431906 libmagickwand-dev_6.5.5.3-1exp1_i386.deb e852e97d6ceaf3194acb0ac7885a2e098f0d2afa18bc55074334ecba012a0a1c 205222 libmagick++2_6.5.5.3-1exp1_i386.deb 22cce72c159bf10fd3c02ba4c16eaf6b71590a9e913d6bdcd037d37b986f38be 233584 libmagick++-dev_6.5.5.3-1exp1_i386.deb b160fa2ecda6c98fa5dd25c93fa4f19c5969cab424e95325c274a66958972d86 208076 perlmagick_6.5.5.3-1exp1_i386.deb Files: a567e53f7224883b041eec543c92fcf0 1877 graphics optional imagemagick_6.5.5.3-1exp1.dsc af4e5cd106d574e9379a5c33c9d8c502 36602 graphics optional imagemagick_6.5.5.3-1exp1.diff.gz f26140dd578e0c799f3d82b444309040 6 graphics optional imagemagick_6.5.5.3-1exp1_i386.deb a0f1e6a1d61bc1f0064509bbd085763b 3409830 debug extra imagemagick-dbg_6.5.5.3-1exp1_i386.deb 1f0f32f72b5e93d61c71d9b420bee92e 4142134 doc optional imagemagick-doc_6.5.5.3-1exp1_all.deb 9c0ff1c1b68f6a6cb4ac5712a69a8edb 1659036 libs optional libmagickcore2_6.5.5.3-1exp1_i386.deb 3ccf3bd70b58cc5d2fb88bbca2b07a3b 112358 libs optional libmagickcore2-extra_6.5.5.3-1exp1_i386.deb
Accepted mesa 7.6-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 11:51:58 +0200 Source: mesa Binary: libgl1-mesa-swx11 libgl1-mesa-swx11-dbg libgl1-mesa-swx11-i686 libgl1-mesa-swx11-dev libgl1-mesa-glx libgl1-mesa-glx-dbg libgl1-mesa-dri libgl1-mesa-dri-dbg libgl1-mesa-dev mesa-common-dev libosmesa6 libosmesa6-dev libglu1-mesa libglu1-mesa-dev libglw1-mesa libglw1-mesa-dev mesa-utils Architecture: source i386 Version: 7.6-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Brice Goglin bgog...@debian.org Description: libgl1-mesa-dev - A free implementation of the OpenGL API -- GLX development files libgl1-mesa-dri - A free implementation of the OpenGL API -- DRI modules libgl1-mesa-dri-dbg - Debugging symbols for the Mesa DRI modules libgl1-mesa-glx - A free implementation of the OpenGL API -- GLX runtime libgl1-mesa-glx-dbg - Debugging symbols for the Mesa GLX runtime libgl1-mesa-swx11 - A free implementation of the OpenGL API -- runtime libgl1-mesa-swx11-dbg - A free implementation of the OpenGL API -- debugging symbols libgl1-mesa-swx11-dev - A free implementation of the OpenGL API -- development files libgl1-mesa-swx11-i686 - Mesa OpenGL runtime [i686 optimized] libglu1-mesa - The OpenGL utility library (GLU) libglu1-mesa-dev - The OpenGL utility library -- development files libglw1-mesa - A free implementation of the OpenGL API -- runtime libglw1-mesa-dev - A free implementation of the OpenGL API -- development files libosmesa6 - Mesa Off-screen rendering extension libosmesa6-dev - Mesa Off-screen rendering extension -- development files mesa-common-dev - Developer documentation for Mesa mesa-utils - Miscellaneous Mesa GL utilities Closes: 539162 545085 Changes: mesa (7.6-1) unstable; urgency=low . [ Brice Goglin ] * New upstream release. + Fix software fallback assertion on RS480, closes: #539162. + Fix segfault in _swrast_ReadPixels on i915, closes: #545085. . [ Julien Cristau ] * Don't run install from the various configs in parallel, hopefully fixing a bug in the previous debian/rules. Thanks to Bernhard R. Link for the suggestions. Checksums-Sha1: bd1db100208d598ad343c001de183c4c248c00d9 1892 mesa_7.6-1.dsc 6f4577ebf2bc7e0d22dbf75b334cb99373fff478 8691502 mesa_7.6.orig.tar.gz 0e251fab56e87bce5290977a070f65ded8f6c6d2 2243133 mesa_7.6-1.diff.gz f2e68c3162593881c049cff5292944dee7f85252 977666 libgl1-mesa-swx11_7.6-1_i386.deb 58870d8d2a532fdfd5971d6d01d075e9a56cc9ad 4340968 libgl1-mesa-swx11-dbg_7.6-1_i386.deb a157576426bd05acb5718e8e81fd9da25873a791 974016 libgl1-mesa-swx11-i686_7.6-1_i386.deb 6064c40adbc057fc625957083db9f2907e8fa3b9 1120752 libgl1-mesa-swx11-dev_7.6-1_i386.deb 93fba1e896256cabda7e42d0ee858823fb48ddea 150486 libgl1-mesa-glx_7.6-1_i386.deb 1aafeb0dda07ca37e97c708caab69a9417e4fd4a 597668 libgl1-mesa-glx-dbg_7.6-1_i386.deb 59351747bc0c188558434b9ede06536c8f4078b0 14588936 libgl1-mesa-dri_7.6-1_i386.deb 2ea9e951118e6d300abf94525c33da537c632135 72455664 libgl1-mesa-dri-dbg_7.6-1_i386.deb 28ac7ba0330817923e230d1761809c9ddfef7b47 23202 libgl1-mesa-dev_7.6-1_i386.deb 2d0497da3ad999092371d67cec0ed33bb7b90d27 2121730 mesa-common-dev_7.6-1_i386.deb 56076cef15ed3c8e378d0c32f09f0dbcf2024aa4 2599042 libosmesa6_7.6-1_i386.deb ab593f2b5fe51bc27abcecde8ad15d591d6da19c 3012526 libosmesa6-dev_7.6-1_i386.deb 90c366f928f008b6c471e73541942c3e9a5f2e4a 210266 libglu1-mesa_7.6-1_i386.deb 1126902a1f0b8859d623b35173e70ef121f4cd08 258974 libglu1-mesa-dev_7.6-1_i386.deb 19ce140496155ee1ad71dd76fcf3233f9e716b4e 30432 libglw1-mesa_7.6-1_i386.deb 4c1ee850ac412b29e5ac96580a0ae7f7a56876e0 31390 libglw1-mesa-dev_7.6-1_i386.deb 6b24afbe994b8c98dc6a8b612466e14915d54108 45682 mesa-utils_7.6-1_i386.deb Checksums-Sha256: a0b604f5d189e656056844695032bc5d627c0300505c11801de15fca7d0392f0 1892 mesa_7.6-1.dsc 9547f5b2bf61bd754ce2a003591f4660449cbfb76c90d0153df5900e52de99d0 8691502 mesa_7.6.orig.tar.gz 347682079dc02456044a5bc569c20f99adfd370c8a3213adc1ca005235cefa89 2243133 mesa_7.6-1.diff.gz 732019f61f3522e9bfff0a2cc706d48ec5d41afeb7ae76a54e390c6a7f6411ea 977666 libgl1-mesa-swx11_7.6-1_i386.deb 2bdfee532fe05e339e5537fedf82ea3f6b5534b971c67c1e3f7f7b53c02420b9 4340968 libgl1-mesa-swx11-dbg_7.6-1_i386.deb 1833139c3e72d3ea2dbf6f9a98fe42097f5922cd48f5304484a11cf52a594817 974016 libgl1-mesa-swx11-i686_7.6-1_i386.deb ffbb9da9482c71f5d4fd77f967e44b6d1f4d269d93a1539c8deac70defb1f7ef 1120752 libgl1-mesa-swx11-dev_7.6-1_i386.deb adf29a60f0f837ac61d8a4a5c89c57d03833dd984b5c56477613b90852884ce2 150486 libgl1-mesa-glx_7.6-1_i386.deb a4a87bc6e2c26aaf818b16c0071bac5b9d9149e9794b3576a22365390de12e1d 597668 libgl1-mesa-glx-dbg_7.6-1_i386.deb 1b0049c8899dfb514bdbfb32a5d6115e9c1befa189a6e614f7d27dcee1d5ac71 14588936 libgl1-mesa-dri_7.6-1_i386.deb f24ecfebff9ca12f2c12abe76c6ffd871bec5cb70ee50e3f1c4fe5d004c41c33 72455664 libgl1-mesa-dri-dbg_7.6-1_i386.deb
Accepted citadel 7.66-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 10:19:30 +0200 Source: citadel Binary: citadel-server citadel-common citadel-mta citadel-client citadel-doc citadel-dbg Architecture: source amd64 all Version: 7.66-1 Distribution: unstable Urgency: low Maintainer: Debian Citadel Team pkg-citadel-de...@lists.alioth.debian.org Changed-By: Michael Meskes mes...@debian.org Description: citadel-client - complete and feature-rich groupware server (command line client) citadel-common - complete and feature-rich groupware server citadel-dbg - complete and feature-rich groupware server - debugging symbols citadel-doc - complete and feature-rich groupware server (documentation) citadel-mta - complete and feature-rich groupware server (mail transport agent) citadel-server - complete and feature-rich groupware server Closes: 545568 545719 546006 548016 Changes: citadel (7.66-1) unstable; urgency=low . * Updated VCS information to point to new git. * Removed files deleted by clean target. * Updated Russian debconf translation. (Closes: #546006) - thanks to Yuri Kozlov yu...@komyakino.ru * Updated German debconf translation. (Closes: #545719) - thanks to Helge Kreutzmann deb...@helgefjell.de * Updated French debconf translation. (Closes: #545568) - thanks to Christian Perrier bubu...@debian.org * Updated Vietnamese debconf translation. (Closes: #548016) - thanks to Clytie Siddall cly...@riverland.net.au * New Upstream version Checksums-Sha1: 59ca1df0df28d22ccf0fa1653413873297e732c3 1568 citadel_7.66-1.dsc 6078f5537e05abcf291b1aa7f88d7eb0a210d11e 798407 citadel_7.66.orig.tar.gz b93a5af90b429fa4f59a3d9205a91adc749fa2ac 32660 citadel_7.66-1.diff.gz 58a3edc415ed2169a938f22fb6d2d227c6a394ca 389860 citadel-server_7.66-1_amd64.deb b6f687e878643687582e9cc07bc36fd9bc5dc544 10426 citadel-mta_7.66-1_amd64.deb 01866fff535fc28ddd570aeff114770306f1c3e5 128424 citadel-client_7.66-1_amd64.deb 07cff858848cd51fbd2fa55d75c6c44bad8e0c48 1076154 citadel-dbg_7.66-1_amd64.deb 9ca30767866e4153a57f79556f27f9de25b169ce 10194 citadel-common_7.66-1_all.deb 7a9f3099d096a74528ecb3752c073df689ae8f58 100070 citadel-doc_7.66-1_all.deb Checksums-Sha256: 7e9c7000580bc4d8dbdc80155868d00ffc5c644906ea67e9c5d53f253c99792c 1568 citadel_7.66-1.dsc d9e172249759d3be8ee25a7b86671fa063e1957d8cda739bbbd1197c55c260eb 798407 citadel_7.66.orig.tar.gz b67060ffe35a4f2b2158abd94270ba698fef94fa7bf9192387b2ed66fac9a7e8 32660 citadel_7.66-1.diff.gz addd1e44a2db1afa45ea9ac2c0dd27bdab67f2ba5f71e966091e53cb97bc1da7 389860 citadel-server_7.66-1_amd64.deb cc93c602b692b32a81ecb84e9a91447502a25b76ac83762fd5db68e0fe314689 10426 citadel-mta_7.66-1_amd64.deb c43d10a7a315c16030f42bdd38d6dc996c48232981f61fc57d64cb4e285b28f3 128424 citadel-client_7.66-1_amd64.deb a312ad8808296a723145607be00ffb0936a4cede30ab68b9c7c08e7040491dc2 1076154 citadel-dbg_7.66-1_amd64.deb 06968953b6b9b833b0ef82104ef9bfa94b98c584dddccd5f1516a134b9706147 10194 citadel-common_7.66-1_all.deb 6b22e9d1860c4815ecb9e4303b29a5f4fc4c78b4e6df05ed9260b474443ea492 100070 citadel-doc_7.66-1_all.deb Files: e2ffc08882edaeee5a369823c553f4a4 1568 mail extra citadel_7.66-1.dsc fb49df9b4a31559ef3591af7341787e8 798407 mail extra citadel_7.66.orig.tar.gz 644f5bb32fd053bb42fa75522929b128 32660 mail extra citadel_7.66-1.diff.gz 423aef6f74a1ee7aece52bb59a7169e7 389860 mail extra citadel-server_7.66-1_amd64.deb ee386fa4613f3e89457a2b70d0610654 10426 mail extra citadel-mta_7.66-1_amd64.deb 2d6682d29843b5836b577fea9bf66ac6 128424 mail extra citadel-client_7.66-1_amd64.deb d359217127874af69acf430da0f1c5d7 1076154 debug extra citadel-dbg_7.66-1_amd64.deb 0c1c28fd6e022b1257ec479e30a9e737 10194 mail extra citadel-common_7.66-1_all.deb 1f692b243d5108e2c1957e34b6b832e0 100070 doc extra citadel-doc_7.66-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFKweWvVkEm8inxm9ERAj+1AJ99CIgDYn/9qnyF2vYW2BhC0nq06ACaA3xi LNWB6ErTrRtIjzdR7iNU2rk= =tn3E -END PGP SIGNATURE- Accepted: citadel-client_7.66-1_amd64.deb to pool/main/c/citadel/citadel-client_7.66-1_amd64.deb citadel-common_7.66-1_all.deb to pool/main/c/citadel/citadel-common_7.66-1_all.deb citadel-dbg_7.66-1_amd64.deb to pool/main/c/citadel/citadel-dbg_7.66-1_amd64.deb citadel-doc_7.66-1_all.deb to pool/main/c/citadel/citadel-doc_7.66-1_all.deb citadel-mta_7.66-1_amd64.deb to pool/main/c/citadel/citadel-mta_7.66-1_amd64.deb citadel-server_7.66-1_amd64.deb to pool/main/c/citadel/citadel-server_7.66-1_amd64.deb citadel_7.66-1.diff.gz to pool/main/c/citadel/citadel_7.66-1.diff.gz citadel_7.66-1.dsc to pool/main/c/citadel/citadel_7.66-1.dsc citadel_7.66.orig.tar.gz to pool/main/c/citadel/citadel_7.66.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 archfs 0.5.4-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 28 Sep 2009 21:00:08 +0100 Source: archfs Binary: archfs Architecture: source i386 Version: 0.5.4-1 Distribution: unstable Urgency: low Maintainer: Jon Dowland j...@debian.org Changed-By: Jon Dowland j...@debian.org Description: archfs - rdiff-backup virtual filesystem Closes: 471536 Changes: archfs (0.5.4-1) unstable; urgency=low . * Initial release Closes: #471536. * New maintainer. Thanks to Adam Sloboda for his initial packaging work. Checksums-Sha1: f82840a557dfc9458f7cf3680eb30ebc728dc0ca 1157 archfs_0.5.4-1.dsc da7016b7c03da266c622ba30bb441cbebacdc608 145304 archfs_0.5.4.orig.tar.gz c8961aea898f8329fec8022826b46aa2bf5455f4 52101 archfs_0.5.4-1.diff.gz 211b879fc8d2e40a32370101a1e47c3fa5a6ff36 23322 archfs_0.5.4-1_i386.deb Checksums-Sha256: f259ed53e177df45e70d7d663b48171cf98ca1511f8eb346bc33f5b55faac6fe 1157 archfs_0.5.4-1.dsc 131201429531194e8fc09b8b864c44fd11699591a3bc42af7d6886f5bc475ba1 145304 archfs_0.5.4.orig.tar.gz b9c2e7ce0d2c6a8e11e192ced2b34ce8e27b88d81b99b8aeb8033a9b551a 52101 archfs_0.5.4-1.diff.gz bec07079842fed6b536ec9a56618aaf482fa025385f6be720ef9769bc821f21a 23322 archfs_0.5.4-1_i386.deb Files: 1f88e57b33fdf1528b231885018812d1 1157 utils optional archfs_0.5.4-1.dsc e29f8a023cde337814ce55d9aa144ac8 145304 utils optional archfs_0.5.4.orig.tar.gz c65e4d8c2b850218506dfb542a25b4d7 52101 utils optional archfs_0.5.4-1.diff.gz 762e871635adb96e320fd325d21cd7d9 23322 utils optional archfs_0.5.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrBNnkACgkQFotOcXAy8jhZtgCgs7CNMDaaIpup9j+ZhjYWafB+ yT4An2+VjQFFEyXD3Ph1J9pc6R28GSLc =GjxT -END PGP SIGNATURE- Accepted: archfs_0.5.4-1.diff.gz to pool/main/a/archfs/archfs_0.5.4-1.diff.gz archfs_0.5.4-1.dsc to pool/main/a/archfs/archfs_0.5.4-1.dsc archfs_0.5.4-1_i386.deb to pool/main/a/archfs/archfs_0.5.4-1_i386.deb archfs_0.5.4.orig.tar.gz to pool/main/a/archfs/archfs_0.5.4.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 libgee 0.5.0-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 09:37:27 +0200 Source: libgee Binary: libgee2 libgee-dev libgee2-dbg Architecture: source amd64 Version: 0.5.0-1 Distribution: unstable Urgency: low Maintainer: Maintainers of Vala packages pkg-vala-maintain...@lists.alioth.debian.org Changed-By: Sebastian Dröge sl...@debian.org Description: libgee-dev - GObject based collection library (development files) libgee2- GObject based collection library libgee2-dbg - GObject based collection library - library symbols Closes: 543249 Changes: libgee (0.5.0-1) unstable; urgency=low . * New upstream release: + Use correct default hash/equal/copy functions for string hashmaps and other containers (Closes: #543249). + debian/control, debian/libgee[12].install: - Update for the new so version. + debian/copyright: - Updated. * debian/rules: + Also regenerate the generated C sources for the tests. Checksums-Sha1: 2f9d0f62fd5e3b2472da5feffeb5a4d59c79defa 1347 libgee_0.5.0-1.dsc 6ff043a8ded64dcd9e54e10c7a9cfaf9d047eefa 675954 libgee_0.5.0.orig.tar.gz 776f8d6c54ff072e8cdd319018983b4eb5f50256 3354 libgee_0.5.0-1.diff.gz 49d3c54bbef23bf5a0dddc6cd6318cdac7cd4368 114036 libgee2_0.5.0-1_amd64.deb 3e916878fe9f23732577d0e2c52649ba1ea35470 27996 libgee-dev_0.5.0-1_amd64.deb 8104a04073911f9af9b35d8f27e9bb79d4ed225e 263196 libgee2-dbg_0.5.0-1_amd64.deb Checksums-Sha256: 6aaf7cf3fc8e9b34e999140194de214c520889a503942e70292f37a654fe0766 1347 libgee_0.5.0-1.dsc 5986ac76c78a5da4800916dbe477ab8196ee86f6777d638060ccded248cb38be 675954 libgee_0.5.0.orig.tar.gz 7526efaf7bdcb764835a2b066e3108e0f60d44e10f2475cbfabbfd594a5d8bfe 3354 libgee_0.5.0-1.diff.gz 6e67fe8ddc3652cc5c7a00914803be98f67cf8a6e055a2db6e037e545dfe5dca 114036 libgee2_0.5.0-1_amd64.deb a569ad1beefdc3b3a1b34de87b0b4bb141c04f55026eccaf0a888a9e0e4564ad 27996 libgee-dev_0.5.0-1_amd64.deb aa72cc88116d0d03371f9e23c20bf6f4f5ab8d17234272e9d29c3a65d901de5b 263196 libgee2-dbg_0.5.0-1_amd64.deb Files: 24d87846b71f355aaa69a75d3f6e9109 1347 libs optional libgee_0.5.0-1.dsc e344c13851e991dd24b4e9ebbc3f8fb7 675954 libs optional libgee_0.5.0.orig.tar.gz 5a21d6b444ac5525194759894b87ac87 3354 libs optional libgee_0.5.0-1.diff.gz 75f485a672699036166fb2ad5de70fbe 114036 libs optional libgee2_0.5.0-1_amd64.deb 7123137be5392d0cbb4404d348ddb229 27996 libdevel optional libgee-dev_0.5.0-1_amd64.deb d7fdbe44a32be5fb64ab2344ac1091b5 263196 debug extra libgee2-dbg_0.5.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrBvYoACgkQBsBdh1vkHyFXOQCeP9R806FFw546zEkKj0pqx25F YfYAnR23tdYF0H0yKpDBJ+FcHrAzfa4X =5bjr -END PGP SIGNATURE- Accepted: libgee-dev_0.5.0-1_amd64.deb to pool/main/libg/libgee/libgee-dev_0.5.0-1_amd64.deb libgee2-dbg_0.5.0-1_amd64.deb to pool/main/libg/libgee/libgee2-dbg_0.5.0-1_amd64.deb libgee2_0.5.0-1_amd64.deb to pool/main/libg/libgee/libgee2_0.5.0-1_amd64.deb libgee_0.5.0-1.diff.gz to pool/main/libg/libgee/libgee_0.5.0-1.diff.gz libgee_0.5.0-1.dsc to pool/main/libg/libgee/libgee_0.5.0-1.dsc libgee_0.5.0.orig.tar.gz to pool/main/libg/libgee/libgee_0.5.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 gnome-icon-theme 2.28.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 28 Sep 2009 20:45:42 +0200 Source: gnome-icon-theme Binary: gnome-icon-theme Architecture: source all Version: 2.28.0-1 Distribution: unstable Urgency: low Maintainer: Josselin Mouette j...@debian.org Changed-By: Andrea Veri andrea.ver...@gmail.com Description: gnome-icon-theme - GNOME Desktop icon theme Changes: gnome-icon-theme (2.28.0-1) unstable; urgency=low . * New upstream release. * debian/control.in: - bumped standards-version to 3.8.3. No changes needed. Checksums-Sha1: 0e5ce0582be14bab244c3abb8ac9026e8530968a 1338 gnome-icon-theme_2.28.0-1.dsc 7af1949d652ebf33247537b900111817c7acb4d1 4180180 gnome-icon-theme_2.28.0.orig.tar.gz 559ddeeae84cd8711a0288d2d4d9948b684de4e3 16713 gnome-icon-theme_2.28.0-1.diff.gz df97ac3dc19191d5a9e7392561b2c50f6fdfcede 3743932 gnome-icon-theme_2.28.0-1_all.deb Checksums-Sha256: aeabe53ae90bae204cdf90e068e11994048a38f0b538c395e2253d4b7daaa376 1338 gnome-icon-theme_2.28.0-1.dsc 5d7824423dd4625cf6f19982ab6a024d80dd3bb98356becbdcd07907bf79d948 4180180 gnome-icon-theme_2.28.0.orig.tar.gz 3fe84ef6479e8657ce6b97e3a52bd6998bbc1980b4a4a173ce4634fcde9bfaa9 16713 gnome-icon-theme_2.28.0-1.diff.gz c696ddb908f972756fcf7324ee6c0ad229c97b275e2938bccfca8bbdcc4f07b0 3743932 gnome-icon-theme_2.28.0-1_all.deb Files: 9d0b3b0d0b24e9fcf2f639a66f4d135b 1338 gnome optional gnome-icon-theme_2.28.0-1.dsc 15715341d6a9e755fbf3e73547c431a7 4180180 gnome optional gnome-icon-theme_2.28.0.orig.tar.gz 5fb1d943d0c14ba77a080460cdafe1e5 16713 gnome optional gnome-icon-theme_2.28.0-1.diff.gz ad07de1d0e7f564a73f5b015d5942823 3743932 gnome optional gnome-icon-theme_2.28.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB8McACgkQhTV17EoIsv7DEgCguYnTQ9gC+D57wBsvM7Z9cTaO ylIAnj4WQDscY4ljqqFPKzmMJ0mP23+n =VWfK -END PGP SIGNATURE- Accepted: gnome-icon-theme_2.28.0-1.diff.gz to pool/main/g/gnome-icon-theme/gnome-icon-theme_2.28.0-1.diff.gz gnome-icon-theme_2.28.0-1.dsc to pool/main/g/gnome-icon-theme/gnome-icon-theme_2.28.0-1.dsc gnome-icon-theme_2.28.0-1_all.deb to pool/main/g/gnome-icon-theme/gnome-icon-theme_2.28.0-1_all.deb gnome-icon-theme_2.28.0.orig.tar.gz to pool/main/g/gnome-icon-theme/gnome-icon-theme_2.28.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 libjgraphx-java 1.0.2.4-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 11:14:53 +0200 Source: libjgraphx-java Binary: libjgraphx-java libjgraphx-java-doc Architecture: source all Version: 1.0.2.4-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: libjgraphx-java - Java Swing Diagramming Library libjgraphx-java-doc - Java Swing Diagramming Library - API documentation and manual Closes: 548872 Changes: libjgraphx-java (1.0.2.4-1) unstable; urgency=low . * Initial Release (Closes: #548872) Checksums-Sha1: 6611aa6b3da93814a39bd40a2da7585ba8cff952 1344 libjgraphx-java_1.0.2.4-1.dsc 0a5d9caf1d995aa63e2a509c5d63ff29323feaeb 1190384 libjgraphx-java_1.0.2.4.orig.tar.gz 34afeb3ff6ba99a53d853b7f9022e827da1fcfc8 1992 libjgraphx-java_1.0.2.4-1.diff.gz c279b9cf0ccdb954beab9061d8b776ebb74dbb98 369380 libjgraphx-java_1.0.2.4-1_all.deb 30c7656c361676e10967b939dede1071be760e40 581392 libjgraphx-java-doc_1.0.2.4-1_all.deb Checksums-Sha256: cbaf907a6a85b091a62ec3a652cc66a4de471aaf827310a0c00d74f880c54a30 1344 libjgraphx-java_1.0.2.4-1.dsc b8aacc93898dffd39ae1e570eb39808d13cb79283cabf2316a36a3ca44c52536 1190384 libjgraphx-java_1.0.2.4.orig.tar.gz 6f5ffaa1a32c1162ac93dd831849e5fce1e3661a15091cb3de9085e6e91c93d7 1992 libjgraphx-java_1.0.2.4-1.diff.gz e12d3f3ae7a75f0a11f9fdbe97042b3545cba042ecb45a16ef3315c1ac1f4ad8 369380 libjgraphx-java_1.0.2.4-1_all.deb a8c7d99252d7470ab7aff8f5be4c6552834d9a7dd4613628eb0e2b418d103ca8 581392 libjgraphx-java-doc_1.0.2.4-1_all.deb Files: cdffa825c21005ea30a5c22c2dc8095a 1344 java optional libjgraphx-java_1.0.2.4-1.dsc 4721b0348748c635538b0b7e082bc756 1190384 java optional libjgraphx-java_1.0.2.4.orig.tar.gz 20f851c1ff4c72b65905dced4fc9a094 1992 java optional libjgraphx-java_1.0.2.4-1.diff.gz dae47d48c8c2db23856662792db17e72 369380 java optional libjgraphx-java_1.0.2.4-1_all.deb 54f546005bed70780407a3ca5e584e21 581392 doc optional libjgraphx-java-doc_1.0.2.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrB8D0ACgkQiOXXM92JlhDVVQCgzWk1PWA+nUN9m9u6Cj/B55Z2 BPcAnRGlnOSmTYorrrnQJloeRJeu72dM =ZIsF -END PGP SIGNATURE- Accepted: libjgraphx-java-doc_1.0.2.4-1_all.deb to pool/main/libj/libjgraphx-java/libjgraphx-java-doc_1.0.2.4-1_all.deb libjgraphx-java_1.0.2.4-1.diff.gz to pool/main/libj/libjgraphx-java/libjgraphx-java_1.0.2.4-1.diff.gz libjgraphx-java_1.0.2.4-1.dsc to pool/main/libj/libjgraphx-java/libjgraphx-java_1.0.2.4-1.dsc libjgraphx-java_1.0.2.4-1_all.deb to pool/main/libj/libjgraphx-java/libjgraphx-java_1.0.2.4-1_all.deb libjgraphx-java_1.0.2.4.orig.tar.gz to pool/main/libj/libjgraphx-java/libjgraphx-java_1.0.2.4.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 webcit 7.66-dfsg-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 12:21:33 +0200 Source: webcit Binary: citadel-webcit webcit-dbg citadel-suite Architecture: source amd64 all Version: 7.66-dfsg-1 Distribution: unstable Urgency: low Maintainer: Debian Citadel Team pkg-citadel-de...@lists.alioth.debian.org Changed-By: Michael Meskes mes...@debian.org Description: citadel-suite - complete and feature-rich groupware server; metapackage for full citadel-webcit - web-based frontend to Citadel groupware server webcit-dbg - web-based frontend to Citadel groupware server Changes: webcit (7.66-dfsg-1) unstable; urgency=low . * Added information about new git. * Remove auto-generated files. * New upstream version. Checksums-Sha1: 35ae4b3642f78e91140066bcdda077dbd3c5698b 1433 webcit_7.66-dfsg-1.dsc 0af02cd4a7446395680e54713dd35e7a548add16 1371977 webcit_7.66-dfsg.orig.tar.gz bc8b79d826970002d533254ac76c77dba355770b 20417 webcit_7.66-dfsg-1.diff.gz b5edefdbd24cc6a468836310976ce56a74b84a8d 693408 citadel-webcit_7.66-dfsg-1_amd64.deb 20a7040a9a457f6e12b5a57008192e24565383f6 315582 webcit-dbg_7.66-dfsg-1_amd64.deb 1d33f859c29d40b2130bfae40040fa2860ae0a00 7208 citadel-suite_7.66-dfsg-1_all.deb Checksums-Sha256: f5faec804bfb24d897f26d27bf962df3ec9910283a65bfb3f63695e3af308031 1433 webcit_7.66-dfsg-1.dsc 10453b75bad7a5b60aa3b146dfb2a0f7522310e926857501206806c32d1580da 1371977 webcit_7.66-dfsg.orig.tar.gz fb10075d3a992b6ca40c3b44a4ff979d76531e52d78e72dd93242f4effc03cdc 20417 webcit_7.66-dfsg-1.diff.gz 3111243dc0c9dd38b587ef2786d56be977d87535d63597f7ba12ad54d80298f1 693408 citadel-webcit_7.66-dfsg-1_amd64.deb b2caab483926d6f01f944b2251a4e474f8bf3833295f73ff694b0f2f3d6bc7f1 315582 webcit-dbg_7.66-dfsg-1_amd64.deb 47aafb50dd659bea04e75109aebd4cc05dbc7e25403ada602465722e2bf15043 7208 citadel-suite_7.66-dfsg-1_all.deb Files: 75ee9ec5ed84132e6741e62fdcc10a4f 1433 web extra webcit_7.66-dfsg-1.dsc 340b68c9cc75b5b4e48c9c86dccd068f 1371977 web extra webcit_7.66-dfsg.orig.tar.gz 767284e665658b0b3934b7f844468e07 20417 web extra webcit_7.66-dfsg-1.diff.gz 10760ad358a6bc995374c17e47ff3a7a 693408 web extra citadel-webcit_7.66-dfsg-1_amd64.deb 2d2317a2a8baedc1911319496beda240 315582 debug extra webcit-dbg_7.66-dfsg-1_amd64.deb 9e03b2638fc3724d0b51de363b40636d 7208 mail extra citadel-suite_7.66-dfsg-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFKweL7VkEm8inxm9ERAjiBAJ9QdjreB7p67XEanCvbvDRryno1HgCfdeVE YbucCqrFhMMsWvJWg/hdRVY= =cHWS -END PGP SIGNATURE- Accepted: citadel-suite_7.66-dfsg-1_all.deb to pool/main/w/webcit/citadel-suite_7.66-dfsg-1_all.deb citadel-webcit_7.66-dfsg-1_amd64.deb to pool/main/w/webcit/citadel-webcit_7.66-dfsg-1_amd64.deb webcit-dbg_7.66-dfsg-1_amd64.deb to pool/main/w/webcit/webcit-dbg_7.66-dfsg-1_amd64.deb webcit_7.66-dfsg-1.diff.gz to pool/main/w/webcit/webcit_7.66-dfsg-1.diff.gz webcit_7.66-dfsg-1.dsc to pool/main/w/webcit/webcit_7.66-dfsg-1.dsc webcit_7.66-dfsg.orig.tar.gz to pool/main/w/webcit/webcit_7.66-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 clanlib 1.0~svn3827-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 23 Sep 2009 13:37:09 -0400 Source: clanlib Binary: libclanapp-1.0 libclansdl-1.0 libclanlib-dev clanlib-doc Architecture: source all i386 Version: 1.0~svn3827-1 Distribution: experimental Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Barry deFreese bdefre...@debian.org Description: clanlib-doc - Reference documentation and tutorials for ClanLib libclanapp-1.0 - ClanLib game SDK runtime libclanlib-dev - ClanLib game SDK development files libclansdl-1.0 - SDL module for ClanLib game SDK Closes: 528942 Changes: clanlib (1.0~svn3827-1) experimental; urgency=low . [ Barry deFreese ] * New upstream release. (Taken from upstream svn). + Remove patches no longer needed. + Refresh old patches. + Use autotools on build instead of rebootstrap patch. + Rename binary packages for SONAME bump. * Add README.source file for quilt. * Bump Standards Version to 3.8.3. (No changes needed). . [ Christoph Egger ] * Fix missing includes when building with gcc 4.4 (Closes: #528942) Thanks to Martin Michlmayr for the patch Checksums-Sha1: ba014806e38f2f1c5186e28c19d78ee23fac1088 1729 clanlib_1.0~svn3827-1.dsc 7d7a445cb850a93471e96f5ff94739ee99391774 6804020 clanlib_1.0~svn3827.orig.tar.gz 437a95a7b25d36c0ff4bc97d84d66f633fa8c437 205155 clanlib_1.0~svn3827-1.diff.gz 6b43e3563b85a77e712c833e8a029d853112aa10 5090904 clanlib-doc_1.0~svn3827-1_all.deb 4fa4728858f7e7877a9e1271845b6877db369ee0 1779638 libclanapp-1.0_1.0~svn3827-1_i386.deb 93a542db7a97f46feb62e98040e5b2c6ce3ed917 70192 libclansdl-1.0_1.0~svn3827-1_i386.deb d186766c4b5e5498cbbcf493127f96babc9433fb 3413712 libclanlib-dev_1.0~svn3827-1_i386.deb Checksums-Sha256: f22f43d8a4dd58e5bd855e8da3e7dc5bb1cc30772e6cfc6ceb57ca9aab7f8041 1729 clanlib_1.0~svn3827-1.dsc bff9662de2324ac30baccb0e8f4ade989fcc21fcbeff4148510cacdc41b333c9 6804020 clanlib_1.0~svn3827.orig.tar.gz 7962fab1b9a2a46f4a9aa3155afdaf43a5c4cafbb35583511be06d96b4f3f99b 205155 clanlib_1.0~svn3827-1.diff.gz 5cf41cf17247d45a57631ee9a364d52865da232ec65044ab7d8153931e8c7cb6 5090904 clanlib-doc_1.0~svn3827-1_all.deb df0a30da9f114ac11a820aa7b31295934ac09bfde11162fb68834b513f4027f5 1779638 libclanapp-1.0_1.0~svn3827-1_i386.deb e66567ba02ca878be4a8e811d50e385342ab8e3f5600d9208ab4a0ebf188523c 70192 libclansdl-1.0_1.0~svn3827-1_i386.deb 5f873f9335dd834e975e7ec699dd3c2656f2a3749998d01c289098a1925aabf4 3413712 libclanlib-dev_1.0~svn3827-1_i386.deb Files: 0f1ba8b4004071b60f85ad7490b64ed4 1729 libs optional clanlib_1.0~svn3827-1.dsc 0ee29d0a5e993543320a6148b372 6804020 libs optional clanlib_1.0~svn3827.orig.tar.gz 74368175164555ddc98eb4c64a61b798 205155 libs optional clanlib_1.0~svn3827-1.diff.gz 24b6320e2bea5c1509e625e5a7ac 5090904 doc optional clanlib-doc_1.0~svn3827-1_all.deb 04ff6dc0781b0968849316ecb6d4bd70 1779638 libs optional libclanapp-1.0_1.0~svn3827-1_i386.deb 58f88b8f5d2547e0b692a361638c1c07 70192 libs optional libclansdl-1.0_1.0~svn3827-1_i386.deb e3e4487d745573d5e3209411663c2deb 3413712 libdevel optional libclanlib-dev_1.0~svn3827-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrBIEYACgkQ5ItltUs5T34cSwCePomo8DUfitLHSBcFAkkvSivI XuoAoIYmfWpUbF1sGMfHXmExfOu/R2z2 =FPgp -END PGP SIGNATURE- Accepted: clanlib-doc_1.0~svn3827-1_all.deb to pool/main/c/clanlib/clanlib-doc_1.0~svn3827-1_all.deb clanlib_1.0~svn3827-1.diff.gz to pool/main/c/clanlib/clanlib_1.0~svn3827-1.diff.gz clanlib_1.0~svn3827-1.dsc to pool/main/c/clanlib/clanlib_1.0~svn3827-1.dsc clanlib_1.0~svn3827.orig.tar.gz to pool/main/c/clanlib/clanlib_1.0~svn3827.orig.tar.gz libclanapp-1.0_1.0~svn3827-1_i386.deb to pool/main/c/clanlib/libclanapp-1.0_1.0~svn3827-1_i386.deb libclanlib-dev_1.0~svn3827-1_i386.deb to pool/main/c/clanlib/libclanlib-dev_1.0~svn3827-1_i386.deb libclansdl-1.0_1.0~svn3827-1_i386.deb to pool/main/c/clanlib/libclansdl-1.0_1.0~svn3827-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 window-picker-applet 0.5.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 29 Sep 2009 14:11:04 +0200
Source: window-picker-applet
Binary: window-picker-applet
Architecture: source i386
Version: 0.5.8-1
Distribution: unstable
Urgency: low
Maintainer: Guido Günther a...@sigxcpu.org
Changed-By: Guido Günther a...@sigxcpu.org
Description:
window-picker-applet - Window picker applet for GNOME
Changes:
window-picker-applet (0.5.8-1) unstable; urgency=low
.
* [65f33bd] add Vcs-{Git,Browser}
* [4b89124] fix upstream URL
* [b6704c2] Imported Upstream version 0.5.8
* [cb8b82c] bump standards version
* [22f22db] Add Homepage: field
* [217dfc2] Drop 0001-fix-version-display.patch - applied upstream
Checksums-Sha1:
8061c17139b68052f218e208cb06ed3c0c8df246 1368 window-picker-applet_0.5.8-1.dsc
d14c1f7452d455262b47c71e8ac4bd1b03dc6a0f 338910
window-picker-applet_0.5.8.orig.tar.gz
1f008ae08152a9c90fb13683d0ca8df09248e0ee 2047
window-picker-applet_0.5.8-1.diff.gz
487fd23e814ddefeeb258b6918302518cb15c717 31208
window-picker-applet_0.5.8-1_i386.deb
Checksums-Sha256:
8280e31cbe19b2b5a4a8b433e461f6790d3303b65d5000921ba72cd07626b62e 1368
window-picker-applet_0.5.8-1.dsc
a07a99275c799846b4e2a8162fd54089c880acc026f14d35a725eb4f0ccf1aa0 338910
window-picker-applet_0.5.8.orig.tar.gz
7ff084a5a32ebdc9cf739487b08aceaad3d8160c2a262e036f86f21441e25956 2047
window-picker-applet_0.5.8-1.diff.gz
7e859578cff213301719aa933856860a200d44c2d9305fc6eb6267319156bf29 31208
window-picker-applet_0.5.8-1_i386.deb
Files:
51327799fed6bb22b7e06f4328a2fecc 1368 gnome optional
window-picker-applet_0.5.8-1.dsc
18c469175e3d6ea0ef9b39ba61e6da20 338910 gnome optional
window-picker-applet_0.5.8.orig.tar.gz
875a2e272fdf81d924d74c5397fdc8df 2047 gnome optional
window-picker-applet_0.5.8-1.diff.gz
4866aa87ccc01c33ea7045793d461245 31208 gnome optional
window-picker-applet_0.5.8-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFKwfqen88szT8+ZCYRAj3SAJwNyNyr6dDT2tzLRY9i46691/5u6wCfXaTH
Al/Aihiw4AupFw0U3oj+jaE=
=gFBp
-END PGP SIGNATURE-
Accepted:
window-picker-applet_0.5.8-1.diff.gz
to pool/main/w/window-picker-applet/window-picker-applet_0.5.8-1.diff.gz
window-picker-applet_0.5.8-1.dsc
to pool/main/w/window-picker-applet/window-picker-applet_0.5.8-1.dsc
window-picker-applet_0.5.8-1_i386.deb
to pool/main/w/window-picker-applet/window-picker-applet_0.5.8-1_i386.deb
window-picker-applet_0.5.8.orig.tar.gz
to pool/main/w/window-picker-applet/window-picker-applet_0.5.8.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 mafft 6.713-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 28 Sep 2009 09:02:30 +0200 Source: mafft Binary: mafft Architecture: source i386 Version: 6.713-1 Distribution: unstable Urgency: low Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: mafft - Multiple alignment program for amino acid or nucleotide sequences Changes: mafft (6.713-1) unstable; urgency=low . [ David Paleino ] * debian/control: - removed myself from Uploaders . [ Andreas Tille ] * New upstream version * debian/control: - Standards-Version: 3.8.3 (no changes needed) - s/Debian-Med/Debian Med/ - Recommends: blast2, lynx, ruby (instead of Suggests - we have a Ruby script in /usr/bin using blast and lynx. * debhelper 7 * No need for debian/patches/Securisation-by-mktemp-usage.patch any more * debian/watch: Handle -with.*-extensions naming - we are dealing with the without-extensions tarball in Debian Checksums-Sha1: 80873af61bd52d98aec940c837f00ae90c5b2003 1289 mafft_6.713-1.dsc daaeeac6bd49612ecc51ccdc56a1a01d64b09c96 541970 mafft_6.713.orig.tar.gz ac946c68bf1d87ea3ae4413c638161736ad7a834 4421 mafft_6.713-1.diff.gz 4eee401b9e1ab930c0d0bd88094c6469ec94b07b 2283276 mafft_6.713-1_i386.deb Checksums-Sha256: 4a5eb890085c076854adf3567ea2c6d4e4031be271215db1deef74f83ad5e384 1289 mafft_6.713-1.dsc 2faf13bc0dedfffd2e7fa9a3055a5ace3a3a3465393c6ab85d622d96e483a4f4 541970 mafft_6.713.orig.tar.gz b39db7b0a9b904e8bc4fd3ed04eb4dc6c36d363fce1d788535c88da8477ebe2a 4421 mafft_6.713-1.diff.gz b8dfc2fcfb1c20c22db9d95a746764e9c3627aada7bd79a6c67a7ca54cd6c92d 2283276 mafft_6.713-1_i386.deb Files: 358edcf4c49ed1cf361a5251db1f77d1 1289 science optional mafft_6.713-1.dsc 82133fc88578fd783f807070af768553 541970 science optional mafft_6.713.orig.tar.gz 98bce32106d63839b9d535842cbba20e 4421 science optional mafft_6.713-1.diff.gz 4aa243ed504c2f0e85887b979072548c 2283276 science optional mafft_6.713-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFKwfUFYDBbMcCf01oRAqb7AKCiSAxB8RQQ1mxbojee6L0h15D5nQCdGZ4E o1DYTjsZYZFIw3QCZVWrD+Y= =jGgS -END PGP SIGNATURE- Accepted: mafft_6.713-1.diff.gz to pool/main/m/mafft/mafft_6.713-1.diff.gz mafft_6.713-1.dsc to pool/main/m/mafft/mafft_6.713-1.dsc mafft_6.713-1_i386.deb to pool/main/m/mafft/mafft_6.713-1_i386.deb mafft_6.713.orig.tar.gz to pool/main/m/mafft/mafft_6.713.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 maximus 0.4.12-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 13:55:49 +0200 Source: maximus Binary: maximus Architecture: source i386 Version: 0.4.12-1 Distribution: unstable Urgency: low Maintainer: Guido Günther a...@sigxcpu.org Changed-By: Guido Günther a...@sigxcpu.org Description: maximus- Automaximizing window management tool Changes: maximus (0.4.12-1) unstable; urgency=low . * [c84ebec] depend on a window manager it's pretty useless without one * [4cba576] typo in short description * [ab35c73] Imported Upstream version 0.4.12 * [0293740] build-dep on libunique-dev * [0a4e30b] bump standards version Checksums-Sha1: 83f5eff1cfaab0132ba9520b3df8f4af052d0c68 1265 maximus_0.4.12-1.dsc 0ebf06cc20cec059ea201ca0841b8ed1e0d6f554 308533 maximus_0.4.12.orig.tar.gz 68c4beaf38f99d0e3ca062d3dee47fda05d62c26 3000 maximus_0.4.12-1.diff.gz 9d81fc01cf0e69fc827223f5dca03fb128d626ad 21448 maximus_0.4.12-1_i386.deb Checksums-Sha256: 4b2a18deaedb812cf6a4ce414cf00e807790c297e609a70fa3a1f014f901a42e 1265 maximus_0.4.12-1.dsc 345c7dffad5e107cca2a0eca49323769aaaf7471d3729307d515ae8b4737f294 308533 maximus_0.4.12.orig.tar.gz 0baa7a29ed9441821e39aa7a5cd2b2effe61a0b14dcc700114dfa1a70e89b1e2 3000 maximus_0.4.12-1.diff.gz 2fbac7d2b40d1287b484db0122af8767d12105863e629d8c030443cb89a62ef9 21448 maximus_0.4.12-1_i386.deb Files: 78a05cd239ee9dee1138db96e1d88c11 1265 gnome optional maximus_0.4.12-1.dsc fbc8567195462983809fa0e220ca1ce7 308533 gnome optional maximus_0.4.12.orig.tar.gz 0e3f70931edf4f72db510fa926d1515e 3000 gnome optional maximus_0.4.12-1.diff.gz 14d83d19ea3497c902cbf12f2f4785e1 21448 gnome optional maximus_0.4.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFKwfepn88szT8+ZCYRAnM3AJ9TFxSlMKLn3xraSBaXLS8qa8xpJgCaAvu1 I3Ae1wSFCpr6Up0nlAu6Tj8= =f2Qu -END PGP SIGNATURE- Accepted: maximus_0.4.12-1.diff.gz to pool/main/m/maximus/maximus_0.4.12-1.diff.gz maximus_0.4.12-1.dsc to pool/main/m/maximus/maximus_0.4.12-1.dsc maximus_0.4.12-1_i386.deb to pool/main/m/maximus/maximus_0.4.12-1_i386.deb maximus_0.4.12.orig.tar.gz to pool/main/m/maximus/maximus_0.4.12.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 ant-contrib 1.0~b3+svn177-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 26 Sep 2009 08:45:47 +0200 Source: ant-contrib Binary: ant-contrib Architecture: source all Version: 1.0~b3+svn177-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Michael Koch konque...@gmx.de Description: ant-contrib - collection of tasks, types and other tools for Apache Ant Closes: 485708 Changes: ant-contrib (1.0~b3+svn177-1) unstable; urgency=low . * Initial release (closes: #485708). Checksums-Sha1: 4286d94e86f38038be0daf4ec23d072ff85a29db 1574 ant-contrib_1.0~b3+svn177-1.dsc f411ea45814e506e6248ec2f4a900182c0ca116b 189719 ant-contrib_1.0~b3+svn177.orig.tar.gz 958553c43ac0e342c88ae414140be5b23068439f 2881 ant-contrib_1.0~b3+svn177-1.diff.gz e5d85f578d175daf7644da3e17a01b89f8b255fd 265184 ant-contrib_1.0~b3+svn177-1_all.deb Checksums-Sha256: 3b9b6769f25110b6ecbbc001b0dd6eb3adb0b7af335d43794d389e58723b7e72 1574 ant-contrib_1.0~b3+svn177-1.dsc 6b6d0926af32f9db6f482521fe09fdc2294284c2d00840b06442088fa3fb896b 189719 ant-contrib_1.0~b3+svn177.orig.tar.gz 9373a110de094cd72825cde9d1ccc9c58fb0a19ab9ef02664faef0214c0e2909 2881 ant-contrib_1.0~b3+svn177-1.diff.gz fcb95f64f503ddd358c13655fb24cfbdd1e2bfe8c8471731f875d973de554aec 265184 ant-contrib_1.0~b3+svn177-1_all.deb Files: 1b38f1e54ca1e0d3501e62c68773058e 1574 java extra ant-contrib_1.0~b3+svn177-1.dsc ec171f3c2256bd0a97dc5fab69a1b867 189719 java extra ant-contrib_1.0~b3+svn177.orig.tar.gz 57a1db6e59fa1d8b2ef6c61449282557 2881 java extra ant-contrib_1.0~b3+svn177-1.diff.gz 8c76955219bacebe92042476e26a4c72 265184 java extra ant-contrib_1.0~b3+svn177-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkq9uaAACgkQWSOgCCdjSDsWnACgh8OcyBNpLRzbkWAji2Xq/+iv q/IAoJbqi30aYHr7qh3VVtDXm6UOXlnI =u/39 -END PGP SIGNATURE- Accepted: ant-contrib_1.0~b3+svn177-1.diff.gz to pool/main/a/ant-contrib/ant-contrib_1.0~b3+svn177-1.diff.gz ant-contrib_1.0~b3+svn177-1.dsc to pool/main/a/ant-contrib/ant-contrib_1.0~b3+svn177-1.dsc ant-contrib_1.0~b3+svn177-1_all.deb to pool/main/a/ant-contrib/ant-contrib_1.0~b3+svn177-1_all.deb ant-contrib_1.0~b3+svn177.orig.tar.gz to pool/main/a/ant-contrib/ant-contrib_1.0~b3+svn177.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 gtksourceview2 2.8.1-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 14:07:34 +0200 Source: gtksourceview2 Binary: libgtksourceview2.0-0 libgtksourceview2.0-common libgtksourceview2.0-dev libgtksourceview2.0-doc Architecture: source all i386 Version: 2.8.1-1 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Emilio Pozuelo Monfort po...@debian.org Description: libgtksourceview2.0-0 - shared libraries for the GTK+ syntax highlighting widget libgtksourceview2.0-common - common files for the GTK+ syntax highlighting widget libgtksourceview2.0-dev - development files for the GTK+ syntax highlighting widget libgtksourceview2.0-doc - documentation for the GTK+ syntax highlighting widget Changes: gtksourceview2 (2.8.1-1) unstable; urgency=low . * New upstream bugfix release. Checksums-Sha1: a57d15167c03e8ded971995dea1f5a7da5bf9a3c 1749 gtksourceview2_2.8.1-1.dsc 058fdf96366d5bb7803ddb7ac7018e31021ee543 1804286 gtksourceview2_2.8.1.orig.tar.gz d666e245e67e4d5f91bf92cc16deb8791e6ae36f 8609 gtksourceview2_2.8.1-1.diff.gz a56b24cdd29f4f66f522b71c6e7a44ecb92adc17 732246 libgtksourceview2.0-common_2.8.1-1_all.deb 817881a42ccb6f82ddf024f5fb5e68530d460e1b 92500 libgtksourceview2.0-doc_2.8.1-1_all.deb 4092556f8c5145f221b9d110099626fc6020dd1f 135388 libgtksourceview2.0-0_2.8.1-1_i386.deb 3016950f8cff8b451dd10b7a46b4f1e2e6fc238e 163402 libgtksourceview2.0-dev_2.8.1-1_i386.deb Checksums-Sha256: a2e00a6ecfcc998262e5840f7a6cd428fb86dcf9ea67b1a88dfe6e44dbeaed4e 1749 gtksourceview2_2.8.1-1.dsc 6f41e9435e4553c8589dc5429b5d48df249689a7635f758257e70da5dda95174 1804286 gtksourceview2_2.8.1.orig.tar.gz cdb802660d944cfea4fca151f3c659e76a9d9da5da81268205a205d75ba9a174 8609 gtksourceview2_2.8.1-1.diff.gz 80fcc61f17d1ba7b7b0e9ed5341e5c57c50a753695053451a54ebfbf722e5ba0 732246 libgtksourceview2.0-common_2.8.1-1_all.deb 7f142033d458f722b520fb4a87db6343a2bf34906d73703e79077565460f7355 92500 libgtksourceview2.0-doc_2.8.1-1_all.deb 5b7af0c19897e74ee3890721ddc5484eed36533176d340aaee5e3b13fbd4fe02 135388 libgtksourceview2.0-0_2.8.1-1_i386.deb aec1735ad9c05273fec4b35538beed3afe2742257ebd27e650be39eac7eedbec 163402 libgtksourceview2.0-dev_2.8.1-1_i386.deb Files: 23f6d87b36f45c5f1f0fc855eab2211a 1749 libs optional gtksourceview2_2.8.1-1.dsc 6c06d7a6589734e5c9afb99d9947f3eb 1804286 libs optional gtksourceview2_2.8.1.orig.tar.gz 1ea590e25f4981c11a7cccf280f91df1 8609 libs optional gtksourceview2_2.8.1-1.diff.gz ad1bd577d16b3a48dd8a2e7a0912da08 732246 misc optional libgtksourceview2.0-common_2.8.1-1_all.deb 9ae5495ff36a6fd467d2928cb55c16d6 92500 doc optional libgtksourceview2.0-doc_2.8.1-1_all.deb e9ed683620634a262af1754229b956a6 135388 libs optional libgtksourceview2.0-0_2.8.1-1_i386.deb 78f17c795fd2de41a24f91eb4610390b 163402 libdevel optional libgtksourceview2.0-dev_2.8.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB+a8ACgkQhTV17EoIsv75/ACeNbMyZCft4MaWre6gszr4KI2S 5K0Anjois/22c9xPCaEi0gZJJgVf+qZb =7qXm -END PGP SIGNATURE- Accepted: gtksourceview2_2.8.1-1.diff.gz to pool/main/g/gtksourceview2/gtksourceview2_2.8.1-1.diff.gz gtksourceview2_2.8.1-1.dsc to pool/main/g/gtksourceview2/gtksourceview2_2.8.1-1.dsc gtksourceview2_2.8.1.orig.tar.gz to pool/main/g/gtksourceview2/gtksourceview2_2.8.1.orig.tar.gz libgtksourceview2.0-0_2.8.1-1_i386.deb to pool/main/g/gtksourceview2/libgtksourceview2.0-0_2.8.1-1_i386.deb libgtksourceview2.0-common_2.8.1-1_all.deb to pool/main/g/gtksourceview2/libgtksourceview2.0-common_2.8.1-1_all.deb libgtksourceview2.0-dev_2.8.1-1_i386.deb to pool/main/g/gtksourceview2/libgtksourceview2.0-dev_2.8.1-1_i386.deb libgtksourceview2.0-doc_2.8.1-1_all.deb to pool/main/g/gtksourceview2/libgtksourceview2.0-doc_2.8.1-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 vte 1:0.22.2-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Sep 2009 14:06:41 +0200 Source: vte Binary: libvte9 libvte9-udeb libvte-dev libvte-common python-vte libvte-doc Architecture: source all i386 Version: 1:0.22.2-1 Distribution: unstable Urgency: low Maintainer: Guilherme de S. Pastore gpast...@debian.org Changed-By: Emilio Pozuelo Monfort po...@debian.org Description: libvte-common - Terminal emulator widget for GTK+ 2.0 - common files libvte-dev - Terminal emulator widget for GTK+ 2.0 - development files libvte-doc - Terminal emulator widget for GTK+ 2.0 - documentation libvte9- Terminal emulator widget for GTK+ 2.0 - runtime files libvte9-udeb - Terminal emulator widget for GTK+ 2.0 - minimal runtime (udeb) python-vte - Python bindings for the VTE widget set Changes: vte (1:0.22.2-1) unstable; urgency=low . * New upstream bugfix release. - debian/patches/01_vte_sequence_handler_cd_crash.patch: + Removed, applied upstream. - debian/patches/90_autoreconf.patch: + Refreshed. * debian/watch: Don't uupdate. Checksums-Sha1: 279ddb62f4ccbe034f74189bf8243222328b3a12 1651 vte_0.22.2-1.dsc 9641287b31542b565117d5fa36dfef5b01c26c2f 1690961 vte_0.22.2.orig.tar.gz d894789f823234f566578c170502219ed9916dfa 122098 vte_0.22.2-1.diff.gz f26e6359bdf44df0f30fcafe02d0eef546a1710b 402828 libvte-common_0.22.2-1_all.deb c7f9d5fcfd95208d33ed3e2b50c34f8a57f0fe31 370808 libvte-doc_0.22.2-1_all.deb ab05d1b18a8f4d554bb3a771d1a77eec7720a517 50 libvte9_0.22.2-1_i386.deb fb06e19936e7923a414744c32f62dd2608111aa0 311432 libvte9-udeb_0.22.2-1_i386.udeb 9dfe2781bdf51ee80b24c7cbf58362c2fb022409 690528 libvte-dev_0.22.2-1_i386.deb 3ff5fc12b52c41d5fdae251a53ae57f9d7c4a196 369514 python-vte_0.22.2-1_i386.deb Checksums-Sha256: 8858464a21c028d0430e7812455f4d3c880bce9612eae9e067b4981426466208 1651 vte_0.22.2-1.dsc c1a834898e4f1f4edc590f6243077f6024e29f4d4079298b8115bbe817d7c2cb 1690961 vte_0.22.2.orig.tar.gz 5f4346c5394f12af913114c053bf2748c4f03a03c1cd3e85c9204aafc459892b 122098 vte_0.22.2-1.diff.gz a80d46ababd88228f4bb7db90c3278def8ccec319f56d65efc4cdfb3bf242c3d 402828 libvte-common_0.22.2-1_all.deb 80f96a6f28a6bae9dac064d8f7f935d74e97e46de1791a5770d73e1cb42667a0 370808 libvte-doc_0.22.2-1_all.deb ca3b2e36081353e1b86fd3a7a9ed8ab0756564addf01c08bddbf7973b5969066 50 libvte9_0.22.2-1_i386.deb db63c780aed62ee2507a2635633167823dc7ebae37571b066e48ed57dd919296 311432 libvte9-udeb_0.22.2-1_i386.udeb 37b45c8bad55573b4fc2667fe4d8b65a97449823aefdc23344c33fe12c9bb660 690528 libvte-dev_0.22.2-1_i386.deb 7c24148f415c317e0701526998ec3fa972ca1788fdb8ee6a4f511dab043f6ef1 369514 python-vte_0.22.2-1_i386.deb Files: 8c3f610d6ec0a7f97036c6a357aaafe4 1651 libs optional vte_0.22.2-1.dsc 395d1cfb26eb88cd59cf8c4ba9cff5a3 1690961 libs optional vte_0.22.2.orig.tar.gz b89b83492467c68df4f8107c37b84b1a 122098 libs optional vte_0.22.2-1.diff.gz 1dedcee5f2fa5b1c7d9296c31d956002 402828 libs optional libvte-common_0.22.2-1_all.deb 77fbd6f1a67357eea4f06a340d58563f 370808 doc optional libvte-doc_0.22.2-1_all.deb 51b4cc73cbb7e247e55e069b61913f9d 50 libs optional libvte9_0.22.2-1_i386.deb d93d9f876985f18663a70391c4535b0f 311432 debian-installer extra libvte9-udeb_0.22.2-1_i386.udeb 639affce81f37b2fd6e5071b9b104df6 690528 libdevel optional libvte-dev_0.22.2-1_i386.deb 70e624ef1e8050032956ce3b478aef52 369514 python optional python-vte_0.22.2-1_i386.deb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrB+ksACgkQhTV17EoIsv7IpwCglnZB06vqqW1LMdybveFmaWDf itcAnA6y+dYIJabXNszhYGqud02tmMD+ =vUoB -END PGP SIGNATURE- Accepted: libvte-common_0.22.2-1_all.deb to pool/main/v/vte/libvte-common_0.22.2-1_all.deb libvte-dev_0.22.2-1_i386.deb to pool/main/v/vte/libvte-dev_0.22.2-1_i386.deb libvte-doc_0.22.2-1_all.deb to pool/main/v/vte/libvte-doc_0.22.2-1_all.deb libvte9-udeb_0.22.2-1_i386.udeb to pool/main/v/vte/libvte9-udeb_0.22.2-1_i386.udeb libvte9_0.22.2-1_i386.deb to pool/main/v/vte/libvte9_0.22.2-1_i386.deb python-vte_0.22.2-1_i386.deb to pool/main/v/vte/python-vte_0.22.2-1_i386.deb vte_0.22.2-1.diff.gz to pool/main/v/vte/vte_0.22.2-1.diff.gz vte_0.22.2-1.dsc to pool/main/v/vte/vte_0.22.2-1.dsc vte_0.22.2.orig.tar.gz to pool/main/v/vte/vte_0.22.2.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
