Re: NEW processing
On Wed, Dec 03, 2008 at 08:48:20PM -0600, Raphael Geissert wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Tautschnig wrote: [...] Still, I don't think we need to bring in that unknown $user, I think this thread is more about some impatient DDs sitting and waiting for their package to enter the archive. What about encouraging those impatient folks (please don't be just exclusive to DDs) to track down (at times from mentors.d.n) the source package and review it themselves. Any finding should be notified to the maintainer and CCed to ftpmasters so that they can REJECT the package if deserved, helping out instead of just pestering. How do you track that down? http://wnpp.debian.net/?type[]=ITPproject=description=owner[]=yesowner[]=nocol[]=dustcol[]=typecol[]=descriptioncol[]=installscol[]=ownercol[]=reportersort=project No quick way to get that information from here. Picking three random ITPs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351594 (ITP: chocolate-doom) Bug reports points to http://debian.halfcoded.net/ . Packages are still there. Last modified: Dec 2007. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455759 (ITP: crystal) Points to debian-mentors, but only at the end of the report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457230 (ITP: glest-indians) No information about a package. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Hi, On Wednesday 03 December 2008 23:46, Steve Langasek wrote: Some archs have already problems keeping up [citation needed] :-) http://buildd.debian.org/stats/graph-quarter-big.png regards, Holger pgpLRSr6TXE24.pgp Description: PGP signature
Re: NEW processing
On 2008-12-03, Russ Allbery [EMAIL PROTECTED] wrote: Sune Vuorela [EMAIL PROTECTED] writes: And from my maintainer point of view, lintian becomes more and more irrelevant, as it warns about more and more stupidities, so the real issues is being hidden in the amount of crap outputted. If you think Lintian is warning about something that it shouldn't warn about, please report a bug. In some cases, it may be that we think that you are not maintaining your package the way that we think you should based on our understanding of the general Debian consensus, but a lot of the time we just didn't realize. So you should at least make us *say* that if that's really the case. You might be surprised by us agreeing with you. :) Latest, the warning about quilt patches without any description. Sure it is nice to have a description, but I don't need lintian to tell it. and in other words, the latest package I uploaded: $ lintian kdebase_3.5.9.dfsg.1-6_i386.changes | wc --lines lintian kdebase_3.5.9.dfsg.1-6_i386.changes | tail -1 142 N: 58 tags overridden (32 errors, 26 warnings) You are most welcome to join in and help fixing issues and especially writing manpages. and then, there is the ~1500 open bug reports. Please stop making the lives for the developers harder. Especially the idea about automatically rejecting based on lintian. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Wed, Dec 03, 2008 at 10:15:50PM +0100, Joerg Jaspert wrote: Packages that only add new binary components are already sorted above packages that have completly new source, to decrease their time in the queue, as their checks are much faster done than a complete source review. But even those have a little review from us, enough people manage to even get those done wrong. Love empty packages? soname changes like to do that to people, for example. And checks for critical bugs, such as empty packages, are a good thing to have in place. I'm glad this is done as part of binary NEW processing. The problem is when packages are rejected for things that aren't critical bugs - even, in some cases, for bugs that don't follow from Policy or the DFSG. The ftp team should not presume in such cases that it's their place to block these packages from the archive. Note that we currently are working on integrating lintian into dak in a way that lets us autoreject on selected lintian tags. That will help NEW a little too, even if NEW is the smallest driving force for this change. Applying the same quality standards to NEW and non-NEW uploads is good. By what process will the selection of lintian tags be submitted to the project for review and approval prior to implementation as a hard reject? What is the plan for tracking bugfixes to the lintian checks themselves on an ongoing basis? -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Amaya [EMAIL PROTECTED] writes: Wrong! The overrriden ones should be a lot of fun to look at. Well, the override file is there for a purpose - it's entirely possible that lintian gives a false positive or the package in question has a valid exception for the error. In any case the lintian override file will get very close scrutiny by the ftpmaster doing the NEW check. -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Thu, Dec 04, 2008 at 09:25:43AM +0100, Holger Levsen wrote: On Wednesday 03 December 2008 23:46, Steve Langasek wrote: Some archs have already problems keeping up [citation needed] :-) http://buildd.debian.org/stats/graph-quarter-big.png First, that graph isn't a measure of how the buildds are keeping up. It measures what percentage of packages are built on each architecture, which basically means it's a measure of how well-ported Debian is to those archs (and/or how well the P-a-s entries are being maintained for those archs). Second, there isn't actually anything on that graph (or on the graph that /does/ give a better measure how well the buildds are keeping up, http://buildd.debian.org/stats/graph2-quarter-big.png) to indicate the archs are having problems. There are actually warning lines configured for those graphs, as you can see from http://buildd.debian.org/stats/graph2-big.png; and all archs have been far enough above the thresholds for the past quarter that the lines themselves are cut off below the bottom of the graph. So I don't think we have archs that are struggling to keep up right now, except during exceptional periods when they have zero buildds on-line. -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Thu, Dec 04, 2008 at 02:01:49AM +0100, Amaya wrote: could be very much automatic, just as Zach pointed out. An automatic /me loves the Spanish pronunciation of my (nick)name :-) Nah, blame me, for letting búbúlle pamper me with allowing me to pronounce his nickname as I wish ;) I assure you Spain has nothing to do with this :) I then propose to put all the blame on büḃúllè, ... deal? :-) (beside that, it was just a pun) -- Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],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: NEW processing
On Wed, Dec 03, 2008 at 05:03:49PM -0800, Russ Allbery wrote: Steve Langasek [EMAIL PROTECTED] writes: I submit that lintian warnings are entirely out of scope for the task the project has entrusted to the ftp team, and that mentioning this at all as a factor in making the NEW queue painless indicates there's a problem with the process as implemented. - lintian *warnings* are those points that even the lintian maintainers are not confident are always indicative of bugs. There's really no reason for the ftp team to look at these as a condition for NEW acceptance. Minor correction: lintian warnings are those points that the Lintian maintainers are either not confident are indicative of bugs or indicate bugs that are not severity important or higher. Right - sorry for the imprecision. - Even with lintian errors, there are many that are definitely bugs but which should not be grounds for a reject from the archive because they're *minor* bugs, and the ftp team should not be in the business of enforcing lintian cleanness as a condition of acceptance into the archive because this is (and always will be) a false measure of package quality.[1] There should be no minor-severity bugs that result in lintian errors. If there are, that's a bug in Lintian. Please report it. The lowest threshold that produces an E tag is severity: important, likelihood: possible. I know this is the current lintian policy on E vs. W, but that this wasn't the case historically. Is this the case for lintian 1.24? I believe that's the version in use on ftp-master currently. (It also appears to be the version that will be shipping with lenny?) And even under the new classification, possibly important bugs are still a far cry from things that should be treated as reasons for rejects, IMHO. -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Thu, Dec 04 2008, Steve Langasek wrote: Which is why the ftp team should not be taking it upon themselves to overrule other developers' assessments of which bugs are critical to fix unless those overrulings are grounded in a clear consensus. If you have doubts about the quality of your own packages, feel free to get more experienced developers to review them for you before you upload. But don't put up obstacles to other developers getting work done by giving some other set of developers veto power based on external criteria that the project has never agreed to. Why are these paragraphs only relevant to the ftp team and the archive, and not the release team and the, umm, release? manoj -- But what can you do with it? -- ubiquitous cry from Linux-user partner. (Submitted by Andy Pearce, [EMAIL PROTECTED]) Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Wed, 3 Dec 2008 16:51:34 -0800
Steve Langasek [EMAIL PROTECTED] wrote:
I completely disagree. It's a welcome benefit if packages of
inferior quality are prevented from entering the archive in the
first place imo. If you want to test packages not yet ready for
debian
The fallacy here is to assume that lintian cleanliness is strongly
correlated with high package quality. It isn't. There are certain
lintian *errors* that are almost certain indicators of *poor* package
quality, but this is not proof of the converse.
Absolutely true - though lintian does an excellent job, it does not
claim to be the final arbiter of quality, merely a tool to assist in
raising the quality of packages. For a start, lintian always tests the
source package in isolation.
One problem in reviewing packages on debian-mentors is that
lintian-clean almost becomes the be all and end all of the quality
assessment - maintainers don't expect to have to fix anything that
lintian does not pick up.
Package quality has to be about a whole lot more than just
lintian-clean.
Simplest example - lintian cannot test if the program actually does
anything. A patch that inadvertently causes the program to crash or
just skip large parts of the codebase will not be picked up. Other
examples include pbuilder tests or any test that has to test the new
package against existing packages.
lintian would need a whole new class of checks where a consensus has
been reached that these errors (and these alone) are rigorously
indicative of poor package quality and that any incidence of these
warrants an automatic REJECT. To implement this, it would probably be
better if tools that actually run lintian as part of the build (debuild,
pdebuild some of the VCS-buildpackage tools) would check the lintian
result for these errors and actually fail the build if they occur
(Emdebian does this already). Lintian would also need to disallow
overrides for such errors.
I'm not at all sure how many checks would gain this level of certainty.
Some that might qualify (only a cursory glance, a full review would
probably pick others):
arch-dependent-file-in-usr-share{2 packages}
binary-in-etc
file-in-etc-not-marked-as-conffile {7 packages}
package-contains-ancient-file
file-directly-in-usr-share
file-in-usr-local {1 package}
dir-in-usr-local
executable-is-not-world-readable{2 packages}
special-file{1 package}
symlink-has-double-slash
file-directly-in-usr-share-doc
http://lintian.debian.org/tags/
Hmmm, maybe not.
Before we implement such a REJECT policy, it's probably a good idea to:
a) RELEASE LENNY
b) get a consensus on which lintian errors are always unacceptable in
all packages
c) fix packages that already contain such errors (with NMU's if
necessary)
d) fix as many other lintian errors as possible throughout the archive.
(Quite a lot of lintian errors - some that I would consider quite
serious - affect several hundred packages.)
If we are going to make lintian quality such a banner for NEW,
shouldn't we imrpove the packages we already have in the archive first?
(after releasing Lenny, of course).
--
Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpz4C8qVs9Vv.pgp
Description: PGP signature
Re: NEW processing
On Wed, Dec 03, 2008 at 04:22:05PM -0800, Steve Langasek wrote: I submit that lintian warnings are entirely out of scope for the task the project has entrusted to the ftp team, and that mentioning And indeed, the proposal [1] (or at least my proposal) is to let dak automatically reject on lintian basis, with no need for ftp-masters to fiddle with that. [1] http://lists.debian.org/debian-devel/2008/12/msg00184.html That to me would look like not as an additional job that the project asked ftp-masters to do, but rather as a (sane) extra QA step. It it were detectable, I'd love to reject also automatically packages which were not built with cowbuilder/pbuilder/..., which were not installed by the uploader before uploading, and so on and so forth. That has nothing to do with power (or with personal battles against ftp-masters, FWIW), just plain QA. And if you argue that lintian can be sometimes dumb in checking, I for sure concur, it is just a program after all. To fight that, we give uploaders the power of overrides and to someone the power of tuning lintian parameters. To me, the most natural choice of someone looks like ftp-masters, just because they do maintainer dak. If people are uneasy about that other choices can be: - the lintian maintainers - the QA team - the policy editors - the CTTE - ... add yours ... Cheers. -- Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7 [EMAIL PROTECTED],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: NEW processing
On Thu, 4 Dec 2008 00:44:03 +0100 Amaya [EMAIL PROTECTED] wrote: Maybe providing some sort of updated unstable to test our packages on, in case we don't trust that our system has not become too tainted due to intensive testing, would help. I know some of us do not have the resources to easily build cleaner testing targets. $ sudo pbuilder create $ sudo pbuilder login ? Is this a disc-space issue, or something I'm missing about chroots as testing targets? -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgp6AWEfS7BLT.pgp Description: PGP signature
Re: volunteers wanted for driving/finalizing a DEP on debian/copyright format
On Wed, Dec 03, 2008 at 01:04:14PM +, Noah Slater wrote: On Wed, Dec 03, 2008 at 01:50:22PM +0100, Stefano Zacchiroli wrote: On Wed, Dec 03, 2008 at 12:26:03PM +, Noah Slater wrote: How should we go about collecting to the contributers? Should I post a note to the wiki (alerting the subscribers) about this, and if so, where to direct people for collaboration? It is up to you. From a management point of view, I don't think you should look for many people as the drivers. We already have two people in this thread which volunteered for that (you are one of the two). I suggest you start together to shape the first draft and see how to make the work fit in the DEP process (remember that Sam proposed the copyright stuff before we had DEPs). Okay, sure. Well, it has already been requested that this be delayed until after Lenny and I think that sounds like a good idea. Once we have that out of the way I will being to push this forward as a DEP. Hrm, who requested this (and where)? This seems like a perfectly reasonable thing to work on in parallel to the release, IMHO. -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: volunteers wanted for driving/finalizing a DEP on debian/copyright format
On Wed, Dec 03 2008, Noah Slater wrote: On Wed, Dec 03, 2008 at 10:52:39AM -0800, Steve Langasek wrote: Why do you need a separate mailing list for a single proposal? Please discuss this on debian-devel or debian-project, which are already perfectly adequate lists for this. We have struggled enough with the proposal as it is. My fear is that discussing it on debian-devel will open it up to fire-and-forget criticism that lacks context of previous discussions, is poorly thought out, results in spiralling threads and contributes little to the effort. If there was some dedicated forum for discussing this, even if this was simply a DEP mailing list, I think it would encourage thoughtful and committed contributions from all involved. Then you'll just have to go through another round of discussion and debate before this proposal could be implemented, I think. Something as intrusive as this proposal can't be just discussed in special purpose mailing lists. manoj -- Let's just be friends and make no special effort to ever see each other again. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Possibly excessive lintian warnings (was: NEW processing)
Sune Vuorela [EMAIL PROTECTED] writes: Latest, the warning about quilt patches without any description. Sure it is nice to have a description, but I don't need lintian to tell it. This is severity: minor, certainty: certain, which currently *barely* makes the W threshold. I think a very good argument could be made that this is actually severity: wishlist, which would downgrade it to an I. I'm copying debian-lint-maint to see what the other Lintian maintainers think. I do think the warning is correct for a lint program, and it sounds like you do agree that this is something that should be improved about the package. The prioritization just may be off. and in other words, the latest package I uploaded: $ lintian kdebase_3.5.9.dfsg.1-6_i386.changes | wc --lines lintian kdebase_3.5.9.dfsg.1-6_i386.changes | tail -1 142 N: 58 tags overridden (32 errors, 26 warnings) http://lintian.debian.org/full/[EMAIL PROTECTED] Much of this is just more of the desktop file fiasco, since KDE doesn't follow what's supposedly a shared standard. I've complained about that at some length before and don't know what people are supposed to do with desktop files. If anyone from the KDE team is willing to propose patches or even concrete actionable changes to how Lintian checks desktop files so that KDE's desktop files don't produce tons of noise, I'd love to hear them. You don't have man pages for many of your programs, as you've noted, which is pile of warnings. You install libraries into /usr/lib in a bunch of packages without shlibs entries and don't call ldconfig in postinst. Hm, and you override that in a few places. In general, just looking at the Lintian report, I don't understand what you're doing with shared libraries and why it's correct. Lintian thinks it's wrong, and I understand why Lintian thinks it's wrong, but I must be missing something (which Lintian is also missing). You're apparently not using detached symbols for your debugging libraries, which is another small pile of warnings. By and large, apart from the desktop mess and whatever is going on with shared libraries that I don't understand, the Lintian report looks like a lot of work that should ideally be done on the packages. I'm not really seeing stuff that's obviously wrong, although I only looked at it cursorily. You are most welcome to join in and help fixing issues and especially writing manpages. and then, there is the ~1500 open bug reports. You have a huge and difficult-to-package piece of software and inadequate resources to do all the work on it that should ideally be done. I get that, and I'm not criticizing what you're doing. But I don't think that Lintian should stay silent about issues just because there isn't enough time to correct them. It shouldn't complain about things that aren't actually issues, but it should complain about the things that need to be fixed, even if they can't be fixed right away. That's what it's for. Not having a man page for a binary is a Policy violation. If Lintian doesn't complain about Policy violations, it's hard to understand what the point of it would be. There's a reason why that's a warning and not an error, though. :) Please stop making the lives for the developers harder. Especially the idea about automatically rejecting based on lintian. The only thing that's been seriously discussed with an eye to implementation, so far as I know, is to automatically reject on the basis of a hand-selected and very limited subset of Lintian tags, which would probably not affect anything that you're doing and which would certainly not automatically block packages with proper overrides. I don't think this is going to hurt you as much as you think it would. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On 04/12/08 at 09:25 +0100, Holger Levsen wrote: Hi, On Wednesday 03 December 2008 23:46, Steve Langasek wrote: Some archs have already problems keeping up [citation needed] :-) http://buildd.debian.org/stats/graph-quarter-big.png That proves that buildds have problems building all packages that they should build, not that they have a problem keeping up with the load they receive. If you add 10 times more buildds, this graph is unlikely to change much. I've been graphing the number of NeedsBuild packages per arch. Results are here: http://blop.info/pub/needsbuild-day.png http://blop.info/pub/needsbuild-week.png http://blop.info/pub/needsbuild-month.png http://blop.info/pub/needsbuild-year.png As you can see, there are short times where the buildds for one arch have problem keeping up with the load, but that's often caused by : - one of the buildds being temporarily unavailable - one of the buildds building a very big package What we lack is more redundancy, but that's not new. -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Steve Langasek [EMAIL PROTECTED] writes: By what process will the selection of lintian tags be submitted to the project for review and approval prior to implementation as a hard reject? I think that's a pretty good question. I don't think we need a very formal process, but as a Lintian maintainer, I'd kind of like people to sanity check them before we start doing that just so that we don't get flooded with complaints if we missed something obvious. Thankfully, it's pretty easy to check in advance whether enabling hard rejects would affect much of the archive. There are a bunch of E tags Lintian produces which occur nowhere in the archive because they're so serious that they'd be immedate RC bugs if they made it in and we've cleaned them out. That would be the place to start. Lintian can do things like catch empty packages or packages missing copyright files without having to write new custom code to do so. What is the plan for tracking bugfixes to the lintian checks themselves on an ongoing basis? Joerg usually backports Lintian shortly after each new release. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457318: qmail and related packages in NEW
On Tue, Dec 02, 2008 at 11:29:13AM +0100, Bjørn Mork wrote: Gerrit Pape [EMAIL PROTECTED] writes: Hi, I'm quite surprised how the inclusion of qmail and related packages into sid is handled, or rather not handled, by the ftpmasters. I downloaded the netqmail source from http://dbn.smarden.org/sid/ and looked briefly at it, to see if most of the well-known (some of the for 10+ years!) bugs have been fixed. Unfortunately, it doesn't seem so. The Debian packaging included surprisingly few patches, and the fixes I tested still applies to the Debian package. e.g: [EMAIL PROTECTED]:/usr/local/mydebs/tmp/netqmail-1.06$ patch -p0 --dry-run ../patch-qmail-1.03-rfc2821.diff patching file qmail-remote.c [EMAIL PROTECTED]:/usr/local/mydebs/tmp/netqmail-1.06$ patch -p0 --dry-run ../patch-qmail-1.03-rfc1652.diff patching file ./qmail-smtpd.c Hunk #1 succeeded at 229 with fuzz 1. To avoid having packages starting their Debian life with a long list of serious and grave bugs, may I suggest that you take a look at http://www.dt.e-technik.uni-dortmund.de/~ma/qmail-bugs.html [1] and either include the patches or use the suggested workarounds? Sure, the two patches you mention might be considered for Debian. However, I wonder how two issues can be called a 'long list', and how these can be judged as severity grave or serious. Right now, upstream doesn't completely agree with Andree's list of bugs. Do you know how many people add accept_8bitmime to the default exim configuration, and for what reason? Do you know why any highest priority MX with the closest distance to the mail store should issue temporary errors on incoming connections permanently, and whether this is okay with the standards? I've yet to be pointed to a grave or serious bug in the packages pending in NEW, otherwise I see no reason why they shouldn't be processed and pass NEW. I completely agree with this well written post http://lists.debian.org/debian-devel/2008/12/msg00207.html Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
On Thu, 04 Dec 2008 01:00:17 -0800, Russ Allbery wrote: Sune Vuorela [EMAIL PROTECTED] writes: Latest, the warning about quilt patches without any description. Sure it is nice to have a description, but I don't need lintian to tell it. This is severity: minor, certainty: certain, which currently *barely* makes the W threshold. I think a very good argument could be made that this is actually severity: wishlist, which would downgrade it to an I. I'm copying debian-lint-maint to see what the other Lintian maintainers think. As I mentioned to Sune on IRC last night, the quilt tag's severity was copied from the equivalent dpatch tag (which was originally implemented as a warning and then moved to minor/certain during the transition). I've no problem with downgrading the severity, although we should make a corresponding change to the dpatch tag at the same time, unless there's some reason it's particularly worse for a dpatch to be missing a description. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Thu, Dec 04, 2008 at 01:03:19AM -0800, Russ Allbery wrote: Thankfully, it's pretty easy to check in advance whether enabling hard rejects would affect much of the archive. There are a bunch of E tags Lintian produces which occur nowhere in the archive because they're so serious that they'd be immedate RC bugs if they made it in and we've cleaned them out. That would be the place to start. I agree that's a good place to start. There should still be some sort of public review, though - just because nothing in the archive currently suffers from the bug shouldn't automatically make it a hard requirement. -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Wed, 03 Dec 2008 20:28:59 -0600, Raphael Geissert wrote: From the lintian hacker desk: $ lintian -I --exp-output format=letterqualifier [...] Other *experimental* output formats are 'xml' and 'colons' (currently b0rken). It's fixed in HEAD (well, it now works for me). Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
On 2008-12-04, Russ Allbery [EMAIL PROTECTED] wrote: Sune Vuorela [EMAIL PROTECTED] writes: Latest, the warning about quilt patches without any description. Sure it is nice to have a description, but I don't need lintian to tell it. I do think the warning is correct for a lint program, and it sounds like you do agree that this is something that should be improved about the package. The prioritization just may be off. Yes. downgrading to I is a good solution. And other warnings that could be changed: dbg-package-missing-depends - if there 1 dbg package and multiple arch depending packages beside that. Much of this is just more of the desktop file fiasco, since KDE doesn't follow what's supposedly a shared standard. I've complained about that at some length before and don't know what people are supposed to do with desktop files. If anyone from the KDE team is willing to propose patches or even concrete actionable changes to how Lintian checks desktop files so that KDE's desktop files don't produce tons of noise, I'd love to hear them. A good solution is to get lenny out of the door so that we can ditch kde3 and go on with kde4. KDE4 do follow the specs. Kde3 originates from before it was a shared standard (one of the few fdo standards that is actually a *shared* standard and not a rubber stamp on gnome standards, but that's a entirely different issue) You're apparently not using detached symbols for your debugging libraries, which is another small pile of warnings. we are, but apparantly dh_strip has issues under some conditions with some of the files. You have a huge and difficult-to-package piece of software and inadequate resources to do all the work on it that should ideally be done. I get This is why I need automatic tools that *helps* me and not tools that gets in the way. Not having a man page for a binary is a Policy violation. If Lintian doesn't complain about Policy violations, it's hard to understand what the point of it would be. There's a reason why that's a warning and not an error, though. :) It is also one of the reasons why we aren't overriding that. Please stop making the lives for the developers harder. Especially the idea about automatically rejecting based on lintian. The only thing that's been seriously discussed with an eye to implementation, so far as I know, is to automatically reject on the basis of a hand-selected and very limited subset of Lintian tags, which would probably not affect anything that you're doing and which would certainly not automatically block packages with proper overrides. I don't think this is going to hurt you as much as you think it would. Some people in this thread are suggesting automatic rejecting based on any E: tag. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457318: qmail and related packages in NEW
Gerrit Pape [EMAIL PROTECTED] writes: I've yet to be pointed to a grave or serious bug in the packages pending in NEW, otherwise I see no reason why they shouldn't be processed and pass NEW. I completely agree with this well written post Does the package in NEW fix the well known backscatter spam issue? I tried searching for the fix in the package but unfortunately failed. If it doesn't, then IMO, at this day and age, a MTA sending backscatter spam doesn't belong to Debian. -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Invitation to connect on LinkedIn
LinkedIn chennai pc requested to add you as a connection on LinkedIn: -- Paul, Hi, I am manager of www.chennaipc.com - Computer Laptop Directory in Chennai.Also we own www.manyforyou.com - All information Linking portal.I Would like to add in my business network. Thanks Balaji www.sjbsindia.com www.chennaipc.com www.manyforyou.com www.sjbsjobs.com View invitation from chennai pc http://www.linkedin.com/e/uwTRS9NuUj0vo8kjIcGBPqZTCi3vo8VBXfNSMrhwsPJn/blk/877691833_2/cBYPcPwNejoTdPwLqnpPbOYWrSlI/svi/ -- DID YOU KNOW that LinkedIn can find the answers to your most difficult questions? Post those vexing questions on LinkedIn Answers to tap into the knowledge of the world's foremost business experts: http://www.linkedin.com/e/ask/inv-23/ -- (c) 2008, LinkedIn Corporation
Re: For those who care about pam-ssh: RFC
On Wed, Dec 03, 2008 at 11:19:52PM +0100, Jens Peter Secher wrote: * The 'keyfiles' option is now obsolete. Instead the authentication module will automatically locate all files matching the pattern 'id_*' (the idea for this came from a patch from Javier Serrano Polo). That doesn't sound like a good idea to me. What if a user has extra ssh keys lying around that multiple people have the passphrase to, which prior to this change would have been perfectly safe? Also, why is the pattern id_*? ssh also recognizes 'identity' by default. Shouldn't this really use the same pattern as ssh itself, i.e., (identity|id_dsa|id_rsa)? -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#457318: qmail and related packages in NEW
* Gerrit Pape: Right now, upstream doesn't completely agree with Andree's list of bugs. Out of curiosity, does netqmail fix at least the delayed bounce problem? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Le Wed, Dec 03, 2008 at 08:40:12PM -0600, Raphael Geissert a écrit : I of course do not want to say that reviewing packages in -mentors is always useless, but here again we need to deal with yet another social problem which is the lack of willingness by some people to work on their package to get it in shape. Hi Raphael, I think that the workflow on -mentors does not discourage enough maintainers from working alone. Co-maintainance, work in a packaging team and use of VCS should be more often proposed after ITPs are filed (and of course, ITPs should be filed earlier). Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Packaging IKVM: inclusion of 3rd-party sources
Hello, as part of the Debian Mono Team, I'm trying to get ikvm [1] into an usable state. I've contacted the upstream author, since the build process is *nasty*, at least: it *requires* GNU Classpath's and OpenJDK's sources (upstream specified that a *full* *build* of OpenJDK is required, because of some generated files), and including them inside debian/ is not a great idea to me because: 1) *enormous* diff.gz; 2) security headaches -- code duplication is never nice; 3) hard maintainability. Upstream noted that he does provide pre-generated .zips with all the needed files to build IKVM. I suppose that this makes ikvm non-free (pre-built binaries), but the binaries are effectively coming from software in main (GNU Classpath and OpenJDK). How should I behave here? 1) Should I include the sources in debian/ and do all the needed steps to get a full compile? (notice that if we follow this, each IKVM build will include an OpenJDK build...) 2) Or should I make two separate (source) packages, ikvm and ikvm-build-deps, with the former Build-Depends on the latter? Also, would this be acceptable? (probably ikvm-build-deps would go into non-free, and ikvm into contrib?) Any suggestion is very welcome. Regards, David Paleino [1] that is, the JVM ported on Mono -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Re: NEW processing
Le Wednesday 03 December 2008 22:15:50 Joerg Jaspert, vous avez écrit : Packages that only add new binary components are already sorted above packages that have completly new source, to decrease their time in the queue, as their checks are much faster done than a complete source review. But even those have a little review from us, enough people manage to even get those done wrong. Love empty packages? soname changes like to do that to people, for example. Thanks for this answer. I would like to see these particular uploads be accepted faster. Could it be possible to make them more automatic when lintian checks are implemented in dak ? I guess that archive consistency and empty package, if they are the main issues, could be catched more automatically... Romain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging IKVM: inclusion of 3rd-party sources
David Paleino [EMAIL PROTECTED] (04/12/2008): How should I behave here? 1) Should I include the sources in debian/ and do all the needed steps to get a full compile? (notice that if we follow this, each IKVM build will include an OpenJDK build...) 2) Or should I make two separate (source) packages, ikvm and ikvm-build-deps, with the former Build-Depends on the latter? Also, would this be acceptable? (probably ikvm-build-deps would go into non-free, and ikvm into contrib?) Any suggestion is very welcome. 3) Run away. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bits from the buildd.debian.org world
Hi, On Mon, Nov 24, 2008 at 07:26:06PM +0100, Adeodato Simó wrote: Recent work from Steve McIntyre (current DPL) in coordination with Ryan Murray (wanna-build maintainer and buildd admin for several architectures) has led to the injection of new blood in the buildd.debian.org world. We Will the experimental autobuilders get integrated into buildd.debian.org, where they (IMO) belong, especially with the current situation where experimental has replaced unstable to some extent? cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging IKVM: inclusion of 3rd-party sources
On Thu, Dec 4, 2008 at 8:01 PM, Cyril Brulebois [EMAIL PROTECTED] wrote: David Paleino [EMAIL PROTECTED] (04/12/2008): Any suggestion is very welcome. 3) Run away. 4) Prepare asbestos suit. Then build-depend on openjdk-6-source and notify the release team about the need to binNMU every time openjdk gets updated. Notify the security team of this requirement so that they can fix ikvm when/if OpenJDK requires a DSA/DTSA. 5) Some kinda mono - Java runtime bridge instead of converting the code at build time? 6 ) see #3 -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who care about pam-ssh: RFC
On Thu, Dec 04, 2008 at 02:03:52AM -0800, Steve Langasek wrote: || On Wed, Dec 03, 2008 at 11:19:52PM +0100, Jens Peter Secher wrote: || || * The 'keyfiles' option is now obsolete. Instead the authentication || module will automatically locate all files matching the pattern 'id_*' || (the idea for this came from a patch from Javier Serrano Polo). || || That doesn't sound like a good idea to me. What if a user has extra ssh || keys lying around that multiple people have the passphrase to, which prior || to this change would have been perfectly safe? || || Also, why is the pattern id_*? ssh also recognizes 'identity' by default. || Shouldn't this really use the same pattern as ssh itself, i.e., || (identity|id_dsa|id_rsa)? In addition I, and probably some others, have the habit of disabling files by adding a .OFF extension to it. This practice is based on the (in my view) reasonable assumption that programs should not be scanning directories for files to use unless those directories are specially intended for that purpose. It probably would be fine if there were a (documented) ~/.ssh/id.d/ directory containing keys to be used (and nothing else). Ciao.Vincent. -- Vincent Zweije [EMAIL PROTECTED]| If you're flamed in a group you http://www.xs4all.nl/~zweije/ | don't read, does anybody get burnt? [Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r. signature.asc Description: Digital signature
Re: NEW processing
* Lucas Nussbaum [EMAIL PROTECTED] [081203 18:19]: I completely disagree. It's a welcome benefit if packages of inferior quality are prevented from entering the archive in the first place imo. We currently have a long reviewing process before packages get into the archive. But once they are in, maintainers are free to do whatever they want with their packages, without any review happening. I'm not advocating that we just stop doing reviews. But IMHO, NEW processing should be about the legal problems, not about the random lintian warning/errors, and the various other packaging malpractices. What we should do instead is encourage reviews (either on mentors, or inside teams), because that's also a much more scalable solution. I think package general reviews are a good idea. But checking packages upon entering is still the best point. Removing packages that users already user is not something most people take lightly. Rejecting packages not having some minimal quality to begin with is easy, though. Of course, if ftpmasters come across random problems in the package while reviewing legal stuff and mention that to the maintainer, it's great. But having other things checked by ftpmasters just reduces their bandwidth and causes longer queues. I think splitting that in two teams and having packages only leave NEW when both ftp-masters have agreed on the legal aspects and an other group of people have checked for other problems will not improve the time packages are in NEW in my eyes. And suggesting that things are not checked first time will only make things having less quality. In my eyes there are rather too few checks. Having things like packages with unneedingly repackaged upstream sources and things like that entering which are not possible to undo even by some later maintainer before the next upstream version and things like that do not benefit the project at all... Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who care about pam-ssh: RFC
2008/12/4 Vincent Zweije [EMAIL PROTECTED]: On Thu, Dec 04, 2008 at 02:03:52AM -0800, Steve Langasek wrote: || On Wed, Dec 03, 2008 at 11:19:52PM +0100, Jens Peter Secher wrote: || || * The 'keyfiles' option is now obsolete. Instead the authentication || module will automatically locate all files matching the pattern 'id_*' || (the idea for this came from a patch from Javier Serrano Polo). || || That doesn't sound like a good idea to me. What if a user has extra ssh || keys lying around that multiple people have the passphrase to, which prior || to this change would have been perfectly safe? || || Also, why is the pattern id_*? ssh also recognizes 'identity' by default. || Shouldn't this really use the same pattern as ssh itself, i.e., || (identity|id_dsa|id_rsa)? In addition I, and probably some others, have the habit of disabling files by adding a .OFF extension to it. This practice is based on the (in my view) reasonable assumption that programs should not be scanning directories for files to use unless those directories are specially intended for that purpose. It probably would be fine if there were a (documented) ~/.ssh/id.d/ directory containing keys to be used (and nothing else). That is a very good idea. But the id.d directory should probably contain soft links to the actual keys to not interfere with the standard location. Are the other packages which does something similar? If there are no objections, I will implement such a behaviour. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upcoming events in Japan
Hi, This is a short note to tell you all about what kind of events are happening in Japan. Upcoming events before the end of this year: 1. Kansai Debian Meeting 14 Dec 2008 in Osaka http://wiki.debian.org/KansaiDebianMeeting 2. Tokyo Area Debian Meeting 20 Dec 2008 in Ogikubo http://tokyodebian.alioth.debian.org/2008-12.html I hope I haven't missed anything. regards, junichi -- [EMAIL PROTECTED],debian.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who care about pam-ssh: RFC
2008/12/4 Luca Niccoli [EMAIL PROTECTED]: 2008/12/3 Jens Peter Secher [EMAIL PROTECTED]: Because of the security implications of changing a PAM module, I would welcome some peer reviewing of the changes I have made. The new package has been uploaded to experimental, and the NEWS.Debian is as follows. Also, I would like comments in general about the whether there are better ways to solve the problems. As a user, I see a regression: I have @include (pam)-ssh-auth before @include common-auth in my confguration, and I use two different passwords for my local account and my ssh key; this way if I know I'll be networking I take the bother to type the long-and-very-secure password to unlock my key and get acces to the computer, otherwise I just hit enter and I'm asked for the simpler local password To do that you will need to change /etc/pam.d/ssh-auth to auth sufficient pam_ssh.so such that the SSH passphrase is always asked, and, if it unlocks any of the SSH keys, it will be sufficient to login. (I don't think there's really a point in a strong password if someone has physical access to the computer). Hmm, if noone else has access to the computer (including remote access) then the passphrase on the SSH keys do not need to be more secure than the login password. On the other hand, if there is remote access to the computer, then a weak password will enable an evil hacker to get into you account, copy your SSH key and brute-force attack the key elsewhere. So I do not really see your point. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Wed, Dec 03, 2008 at 10:09:37AM -0800, Don Armstrong wrote: It shouldn't need to be more than this, because packages shouldn't be uploaded with problems that can be trivially identified at NEW processing time. Agreed. However, considering some of the rejects which have recently been discussed here, that appears not to be the case. That seems irrelevant. This is the minimum required check, I think; if ftpmasters want to check more things and/or find more issues as they're doing this check, more power to them. No, not more power to them. Conflating unnecessary tasks with privileged roles is a bad idea. If the project needed to moderate all BTS mails to ensure that nothing insulting was said about the King, it wouldn't be rational to let the BTS moderation team task themselves with ensuring that the message tone was polite enough, that any submissions with spelling errors were hard-rejected, and so on. This would clearly improve the quality of the information in the BTS. Having the stewards of the archive do QA work in a bottleneck is even more ludicrous because, unlike a bug report, which is practically eternal, bugs in packages can actually be fixed by subsequent uploads. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dropping multisync-0.8x for lenny
Hi, recently a user made me aware that multisync_0.82-8.1 is still shipping in lenny currently. The 0.8x series of multisync has been abandoned upstream for several years now, and I think the opensync-0.22 packages together with kitchensync should give at least the same user experience for lenny. However, looking at popcon, it looks like multisync-0.8x is still quite popular AFAICT, and it might work better for some users on older devices, so I am a bit hesitant to get it removed. Personally, I do not want to maintain (well, reply to bug reports mostly I guess) multisync-0.8x for lenny, so I think removing it from testing/unstable is a sensible approach even though we cannot provide a migration path to kitchensync/opensync. Users will still be able to use it when upgrading to lenny, but new users should rather turn to kitchensync (even though the opensync-0.22 packages are not perfect either, e.g. Windows Mobile syncing will not work very well with lenny on kitchensync due to #484130). If somebody is really fond of multisync-0.8x and wants to retain/maintain it for lenny, please let me know; otherwise, I'll ask for its removal from testing/unstable soonish. cheers, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who care about pam-ssh: RFC
2008/12/4 Jens Peter Secher [EMAIL PROTECTED]: To do that you will need to change /etc/pam.d/ssh-auth to auth sufficient pam_ssh.so I know, that's why I'm not complaining =) May writing it in the README.Debian could be a good idea. Hmm, if noone else has access to the computer (including remote access) then the passphrase on the SSH keys do not need to be more secure than the login password. On the other hand, if there is remote access to the computer, then a weak password will enable an evil hacker to get into you account, copy your SSH key and brute-force attack the key elsewhere. So I do not really see your point. If someone has physical access to my computer, the only security is encryption. No sense for a strong login password, he could boot with an other OS or take out the HD and directly read the key (both options will take far less time then brute-forcing an even weak password by typing tries by hand). Brute forcing a strong encryption password would take a lot of time instead (I guess), which at least keeps safe computers not accessible to anyone else (I'm thinking about a laptop and a home server, if I get stolen of the laptop I can delete the public key on the server). Please correct me if I'm completely mistaken... Cheers, Luca -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who care about pam-ssh: RFC
2008/12/4 Luca Niccoli [EMAIL PROTECTED]: 2008/12/4 Jens Peter Secher [EMAIL PROTECTED]: To do that you will need to change /etc/pam.d/ssh-auth to auth sufficient pam_ssh.so I know, that's why I'm not complaining =) May writing it in the README.Debian could be a good idea. OK, will do. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings
The only thing that's been seriously discussed with an eye to implementation, so far as I know, is to automatically reject on the basis of a hand-selected and very limited subset of Lintian tags, which would probably not affect anything that you're doing and which would certainly not automatically block packages with proper overrides. I don't think this is going to hurt you as much as you think it would. Some people in this thread are suggesting automatic rejecting based on any E: tag. Those people won't be the ones who implement it. Those who will implement it will, of course, make sure to crawl through lintian.debian.org making sure to only reject on tags that hit the most packages possible as they don't have any better things to do than pointlessly rejecting packages just for fun. One of the sentences is a joke. -- bye, Joerg Some NM: 3. How do you manage new upstream releases? yes i manage them. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
By what process will the selection of lintian tags be submitted to the project for review and approval prior to implementation as a hard reject? I think that's a pretty good question. I don't think we need a very formal process, but as a Lintian maintainer, I'd kind of like people to sanity check them before we start doing that just so that we don't get flooded with complaints if we missed something obvious. I have a list of tags. In Extremadura I had other ftpteam members and a lintian maintainer look at it. Whenever this gets implemented this list will be made public and then have a place on ftp-master.d.o webpage somewhere. And everyone can comment on it. -- bye, Joerg Ich will ein anderes Telefon, das hier klingelt immer! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
2008/12/4 Joerg Jaspert [EMAIL PROTECTED]: I have a list of tags. In Extremadura I had other ftpteam members and a lintian maintainer look at it. Whenever this gets implemented this list will be made public and then have a place on ftp-master.d.o webpage somewhere. And everyone can comment on it. So it was already decided that it was going to be implemented in Extremadura meeting? Greetings, Miry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
On Thu, Dec 04, 2008 at 09:50:04AM +0100, Lucas Nussbaum wrote: As you can see, there are short times where the buildds for one arch have problem keeping up with the load, but that's often caused by : - one of the buildds being temporarily unavailable - one of the buildds building a very big package - one of the buildd maintainers temporarily unavailable Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
I have a list of tags. In Extremadura I had other ftpteam members and a lintian maintainer look at it. Whenever this gets implemented this list will be made public and then have a place on ftp-master.d.o webpage somewhere. And everyone can comment on it. So it was already decided that it was going to be implemented in Extremadura meeting? We already talked about it in Mar del Plata, and there lintian already got a feature we want for it. -- bye, Joerg What would you do if you wanted to retire from the project? This is far easier than to get in! ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
Sune Vuorela wrote:
[...]
And other warnings that could be changed:
dbg-package-missing-depends - if there 1 dbg package and multiple
arch depending packages beside that.
Will try to work on a dh-like command (or maybe a patch against dh_strip,
depends on what Joey prefers) that will basically scan
debian/*/foo-dbg/usr/lib/debug/(*) and try to find a file under debian/*/
matching the subgrouped expression, to automagically generate the Depends field
(say ${dbg:Depends}).
Once that's done it would be just a matter of adjusting a couple of lines in
debian/control and you are done with dealing with -dbg packages.
Cheers,
Raphael Geissert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings
Adam D. Barratt [EMAIL PROTECTED] writes: As I mentioned to Sune on IRC last night, the quilt tag's severity was copied from the equivalent dpatch tag (which was originally implemented as a warning and then moved to minor/certain during the transition). I've no problem with downgrading the severity, although we should make a corresponding change to the dpatch tag at the same time, unless there's some reason it's particularly worse for a dpatch to be missing a description. I think they're equivalent cases. Personally, I vote for downgrading them both. Unless there are any objections, I'll do that in a bit. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
On 2008-12-04, Raphael Geissert [EMAIL PROTECTED] wrote:
Will try to work on a dh-like command (or maybe a patch against dh_strip,
depends on what Joey prefers) that will basically scan
debian/*/foo-dbg/usr/lib/debug/(*) and try to find a file under debian/*/
matching the subgrouped expression, to automagically generate the Depends
field
(say ${dbg:Depends}).
Once that's done it would be just a matter of adjusting a couple of lines in
debian/control and you are done with dealing with -dbg packages.
No. it actually wouldn't work.
In kde, for example kdepim, contains applications like
- korganizer
- kaddressbook
- kmail
- kpilot
With a -dbg package depending on all apps, the user will have to install
all apps just for getting a backtrace for one application.
That is not desired.
Bloating the archive with seperated -dbg packages is ttbomk not desired
as well.
The current approach is currently the least bad, and lintian should not
complain.
/Sune
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings
On Thu, 2008-12-04 at 12:51 -0800, Russ Allbery wrote: Adam D. Barratt [EMAIL PROTECTED] writes: As I mentioned to Sune on IRC last night, the quilt tag's severity was copied from the equivalent dpatch tag (which was originally implemented as a warning and then moved to minor/certain during the transition). I've no problem with downgrading the severity, although we should make a corresponding change to the dpatch tag at the same time, unless there's some reason it's particularly worse for a dpatch to be missing a description. I think they're equivalent cases. Personally, I vote for downgrading them both. I agree... Unless there are any objections, I'll do that in a bit. ... and did that an hour ago. Apologies for not waiting a little longer for objections / consensus. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Neil Williams wrote: d) fix as many other lintian errors as possible throughout the archive. (Quite a lot of lintian errors - some that I would consider quite serious - affect several hundred packages.) Actually, that's on my list of proposed QA RGs for squeeze, and am willing to work on it (together with the no bashisms one [not just whatever dash doesn't support], and others). But lets talk about that when the cal for proposals is made. Cheers, Raphael Geissert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings
Adam D. Barratt [EMAIL PROTECTED] writes: ... and did that an hour ago. Apologies for not waiting a little longer for objections / consensus. Oh, no, it's no problem. I was being too conservative. Thank you! -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings
Sune Vuorela [EMAIL PROTECTED] writes: No. it actually wouldn't work. In kde, for example kdepim, contains applications like - korganizer - kaddressbook - kmail - kpilot With a -dbg package depending on all apps, the user will have to install all apps just for getting a backtrace for one application. That's why the recommendation (which Lintian currently doesn't talk about; will fix that) is that the debug package depend on the all of the corresponding packages as alternatives. (korganizer | kaddressbook | kmail ...) That way, you still get the checking that the version of the debug package matches the version of the package for which it has debug symbols, without the problem you cite. This is what I've done for other packages and it seems to work reasonably well. (Lintian may still be confused due to the lack of similarity between the package name and the debug package name, but we may be able to fix that.) -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Hi Charles, Charles Plessy wrote: Le Wed, Dec 03, 2008 at 08:40:12PM -0600, Raphael Geissert a écrit : I of course do not want to say that reviewing packages in -mentors is always useless, but here again we need to deal with yet another social problem which is the lack of willingness by some people to work on their package to get it in shape. Hi Raphael, I think that the workflow on -mentors does not discourage enough maintainers from working alone. Co-maintainance, work in a packaging team and use of VCS should be more often proposed after ITPs are filed (and of course, ITPs should be filed earlier). Yes, I've seen some of those as well; those make me happy, actually. It is always nice to work with someone who is willing to keep working to get it the best way as possible. I love that. That reminds me that another problem (probably the original source of these issues) is that the documentation is not explicit enough or doesn't say all it needs to/should say. And before anyone tells me to stop complaining instead of working on it: I will, I just have too many items on my todo list that should be done before. Have a nice day, Cheers, Raphael Geissert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Steve Langasek [EMAIL PROTECTED] writes: On Wed, Dec 03, 2008 at 05:03:49PM -0800, Russ Allbery wrote: There should be no minor-severity bugs that result in lintian errors. If there are, that's a bug in Lintian. Please report it. The lowest threshold that produces an E tag is severity: important, likelihood: possible. I know this is the current lintian policy on E vs. W, but that this wasn't the case historically. Is this the case for lintian 1.24? I believe that's the version in use on ftp-master currently. (It also appears to be the version that will be shipping with lenny?) It's been the rough goal for a while, although we've become much clearer about it recently. I think 1.24 should generally be okay, although of course bugs have been fixed since then. And even under the new classification, possibly important bugs are still a far cry from things that should be treated as reasons for rejects, IMHO. Sure, which is why ftp-master is only going to use a specific list of tags. Joerg came to us and asked for the facility for exactly that reason -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
Sune Vuorela wrote:
On 2008-12-04, Raphael Geissert [EMAIL PROTECTED] wrote:
Will try to work on a dh-like command (or maybe a patch against dh_strip,
depends on what Joey prefers) that will basically scan
debian/*/foo-dbg/usr/lib/debug/(*) and try to find a file under debian/*/
matching the subgrouped expression, to automagically generate the Depends
field (say ${dbg:Depends}).
Using ORed depends, I forgot to say.
Once that's done it would be just a matter of adjusting a couple of lines in
debian/control and you are done with dealing with -dbg packages.
No. it actually wouldn't work.
In kde, for example kdepim, contains applications like
- korganizer
- kaddressbook
- kmail
- kpilot
With a -dbg package depending on all apps, the user will have to install
all apps just for getting a backtrace for one application.
That is not desired.
Bloating the archive with seperated -dbg packages is ttbomk not desired
as well.
Of course.
The current approach is currently the least bad, and lintian should not
complain.
I don't agree, -dbg packages all by themselves are completely useless, they MUST
depend on something that will actually make them meaningful. Otherwise they
should not be built/shipped.
/Sune
Cheers,
Raphael Geissert
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Promoting free PDF readers (was Re: Popular packages in Ubuntu that is missing in Debian/main)
Hi there! On Mon, 01 Dec 2008 11:12:55 +0100, Johannes Wiedersich wrote: Gunnar Wolf wrote: But anyway, and knowing this is not an Ubuntu list... Does anybody know why on Earth is Acroread popular? Why isn't a PDF regularly handled in a saner way with Evince (or kde-based lookalike) in some distributions? Zillions of websites promote acroread via links and thumbnails. I've yet failed to find a site with a pdf and that 'download envince|kpdf|okular for free' button. Don't forget that many people use an inferior OS just out of convenience/marketing/whatever. FYI, the FSFE has started such initiative: http://wiki.fsfe.org/Free-PDF-Readers-Campaign The discussion started in July 2008 on the FSFE discussion mailing list, but unfortunately the archive is available to subscribers only: https://lists.fsfe.org/mailman/listinfo/discussion Recently, a dedicated mailing list was setup: http://lists.fsfe.org/mailman/listinfo/pdfreaders Thx, bye, Gismo / Luca pgpSn8Shm1pk9.pgp Description: PGP signature
Re: NEW processing
Thomas Viehmann wrote: The particular pass through NEW that has been used to demonstrate the deficiency of NEW processing was necessitated by the rename iceweasel-l10n-hi to iceweasel-l10n-hi-in introduced in the previous upload (and processed in 3-4 days or so). This rename took place after uninstallability of iceweasel-l10n-all had been pointed out to the maintainer after he asked for an unblock on release. In essence, this whole trip through NEW would not have happened if the maintainer would actually routinely install his packages before uploading. I am all in favor of fast-tracking urgent stuff, but the deal should involve the maintainer making extra-sure to get things right, too. Because we all know that uninstabillity problems can only occur when you change the package name... Or undistributable/illegal stuff. Or lintian errors. In that sense, you should perform quality checks and moderate _every_ upload as well. I'm all for doing legal checks and semi-automated quality/sanity checks on the *first* upload. But what's the point on doing it on binary package renames? Crap can be introduced into the archive just as easily without it /ever/ processing NEW. If the source package existed in the archive before it shouldn't pass through NEW! Quality assurance of existing packages is a job for the QA team. The two teams should definitely cooperate, share common patterns and possibly scripts. In that way, all packages can be automatically or semi-automatically checked, even those that don't ever change their package names. Am I the only one that finds all of the above obvious? Regards, Faidon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
On 2008-12-04, Raphael Geissert [EMAIL PROTECTED] wrote:
Using ORed depends, I forgot to say.
How would OR'ed depends work?
let us look at a example:
package: kdepim-dbg
depends: korganizer (= ${binary:Version})|kaddressbook (=${binary:version})
version: 4.1.3-1
now, I install korganizer 4.1.3-1 and kdepim-dbg.
later, 4.1.3-2 gets uploadde and I install kaddressbook.
korganizer still fulfills the kdepim-dbg version.
thus, the user is not anywhere better satisfied than before.
The only thing that would work would be if dpkg and apt supported
Conflicts: korganizer (!= $binary:Version), but that is as far as I can
read in policy not valid, so I also don't expect the tools to support
it.
/Sune
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings
Sune Vuorela [EMAIL PROTECTED] writes:
How would OR'ed depends work?
let us look at a example:
package: kdepim-dbg
depends: korganizer (= ${binary:Version})|kaddressbook (=${binary:version})
version: 4.1.3-1
now, I install korganizer 4.1.3-1 and kdepim-dbg.
later, 4.1.3-2 gets uploadde and I install kaddressbook.
korganizer still fulfills the kdepim-dbg version.
thus, the user is not anywhere better satisfied than before.
The only thing that would work would be if dpkg and apt supported
Conflicts: korganizer (!= $binary:Version), but that is as far as I can
read in policy not valid, so I also don't expect the tools to support
it.
Your case is somewhat unusual in that you're providing debugging symbols
for a bunch of packages that are otherwise fairly unrelated and can be
installed with a mix of version numbers. Most of the time, this is not
the case. In your case, this is only marginally useful; it does ensure
that the user has at least one relevant package installed, but no more
than that.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Faidon Liambotis wrote: Quality assurance of existing packages is a job for the QA team. And since everybody makes part of the QA team what you are really saying is: Quality assurance of existing packages is a job for me. ftp-masters are doing a great, often thankless, job. Instead of just saying what they should or should not do why don't you volunteer and actually do something about it? (e.g. the QA check part). Cheers, Raphael Geisser -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NEW processing
Tzafrir Cohen wrote: On Wed, Dec 03, 2008 at 08:48:20PM -0600, Raphael Geissert wrote: [...] What about encouraging those impatient folks (please don't be just exclusive to DDs) to track down (at times from mentors.d.n) the source package and review it themselves. Any finding should be notified to the maintainer and CCed to ftpmasters so that they can REJECT the package if deserved, helping out instead of just pestering. How do you track that down? [...] Check the ITP? mentors.d.n? contact the maintainer? contact ftp-master? That's exactly why I said track down. Cheers, Raphael Geissert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
The best solution would just be to drop most -dbg packages, drop maintainer-uploaded binary packages (using the buildd built packages instead), install the dh_strip from debug.d.n on all the buildds and get people to use -dbgsym packages from debug.d.n. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly excessive lintian warnings (was: NEW processing)
Paul Wise wrote: The best solution would just be to drop most -dbg packages, drop maintainer-uploaded binary packages (using the buildd built packages instead), install the dh_strip from debug.d.n on all the buildds and get people to use -dbgsym packages from debug.d.n. a) That doesn't solve the dependencies problem. b) There are lots of packages missing at debug.d.n, and they only keep one package version. It isn't a drop-in replacement. c) What's the point on using a separate server when we have mirrors? d) We don't need debug symbols for every package out there. Cheers, Raphael Geissert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Work-needing packages report for Dec 5, 2008
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 482 (new: 3) Total number of packages offered up for adoption: 114 (new: 0) Total number of packages requested help for: 46 (new: 0) Please refer to http://www.debian.org/devel/wnpp/ for more information. The following packages have been orphaned: libaudio-flac-decoder-perl (#507386), orphaned 4 days ago Description: Perl module providing an object-oriented FLAC decoder Installations reported by Popcon: 85 libdata-compare-perl (#507388), orphaned 4 days ago Description: perl module to compare perl data structures recursively Reverse Depends: libtest-simpleunit-perl Installations reported by Popcon: 139 libscalar-properties-perl (#507389), orphaned 4 days ago Description: perl module to add run-time properties on scalar variables Installations reported by Popcon: 48 479 older packages have been omitted from this listing, see http://www.debian.org/devel/wnpp/orphaned for a complete list. No new packages have been given up for adoption, but a total of 114 packages are awaiting adoption. See http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list. For the following packages help is requested: apache2 (#470795), requested 266 days ago Description: Co-maintainer wanted Reverse Depends: achims-guestbook ampache apache2 apache2-dbg apache2-mpm-event apache2-mpm-itk apache2-mpm-prefork apache2-mpm-worker apache2-prefork-dev apache2-suexec (151 more omitted) Installations reported by Popcon: 40520 ara (#450876), requested 389 days ago Description: utility for searching the Debian package database Installations reported by Popcon: 124 athcool (#278442), requested 1500 days ago Description: Enable powersaving mode for Athlon/Duron processors Installations reported by Popcon: 231 bash-completion (#472468), requested 255 days ago Description: programmable completion for the bash shell Installations reported by Popcon: 19259 cvs (#354176), requested 1015 days ago Description: Concurrent Versions System Reverse Depends: crossvc cvs-autoreleasedeb cvs-buildpackage cvs2cl cvs2html cvschangelogbuilder cvsconnect cvsd cvsdelta cvsps (12 more omitted) Installations reported by Popcon: 4 dctrl-tools (#448284), requested 404 days ago Description: Command-line tools to process Debian package information Reverse Depends: aptfs debian-goodies dlocate feta haskell-devscripts hg-buildpackage ia32-archive ia32-libs-tools mlmmj sbuild (1 more omitted) Installations reported by Popcon: 9400 dpkg (#282283), requested 1475 days ago Description: dselect: a user tool to manage Debian packages Reverse Depends: alien alsa-source apt-build apt-cross apt-src backuppc build-essential bzr-builddeb cacao-oj6-dbg cacao-oj6-jdk (118 more omitted) Installations reported by Popcon: 79592 drscheme (#402589), requested 724 days ago Description: PLT scheme programming environment Reverse Depends: drscheme minlog proofgeneral-minlog Installations reported by Popcon: 345 elvis (#432298), requested 514 days ago Description: powerful clone of the vi/ex text editor (with X11 support) Reverse Depends: elvis elvis-console elvis-tools Installations reported by Popcon: 374 fglrx-driver (#454993), requested 362 days ago (non-free) Description: non-free AMD/ATI r5xx, r6xx display driver Reverse Depends: fglrx-amdcccle fglrx-atieventsd fglrx-control fglrx-driver fglrx-glx fglrx-glx-ia32 fglrx-kernel-src Installations reported by Popcon: 2163 flightgear (#487388), requested 166 days ago Description: Flight Gear Flight Simulator Installations reported by Popcon: 967 gentoo (#422498), requested 578 days ago Description: a fully GUI-configurable, two-pane X file manager Installations reported by Popcon: 256 gnat-4.3 (#475374), requested 238 days ago Description: help needed to execute test cases Reverse Depends: adabrowse adacontrol asis-programs ghdl gnade-bin gnat gnat-4.3 gnat-gps libadasockets-dev libahven13 (45 more omitted) Installations reported by Popcon: 605 gnat-gps (#496905), requested 98 days ago Description: co-maintainer needed Installations reported by Popcon: 123 grub (#248397), requested 1669 days ago Description: GRand Unified Bootloader Reverse Depends: brdesktop-artwork-grub dfsbuild grub-choose-default grub-doc replicator
Accepted debsums 2.0.40 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 21:55:34 +1300 Source: debsums Binary: debsums Architecture: source all Version: 2.0.40 Distribution: unstable Urgency: low Maintainer: Francois Marier [EMAIL PROTECTED] Changed-By: Francois Marier [EMAIL PROTECTED] Description: debsums- verification of installed package files against MD5 checksums Closes: 503400 505742 507756 Changes: debsums (2.0.40) unstable; urgency=low . * Updated Dutch debconf template (closes: #503400) * Updated Swedish debconf template (closes: #505742) * Updated Spanish debconf template (closes: #507756) Checksums-Sha1: c34cf52ab37a6b711b7edd4705142dbcc76b952d 895 debsums_2.0.40.dsc 6dee112c8d48fcca4714b8913a6fa2ee9d690ff3 46311 debsums_2.0.40.tar.gz da089edadffcb6e00e08411231d35a9d76195747 42872 debsums_2.0.40_all.deb Checksums-Sha256: 4e82c19a293f3685c5325597c48dfce3039e2f7b567c6493e79d4071205f6395 895 debsums_2.0.40.dsc 76d5709d270fde83b97e5c67518a877575defd10376f4afeb783c72103e030e5 46311 debsums_2.0.40.tar.gz 2849f2c12a96e71a9a710bc0e8852397c3f33ee0617083d442d3ce7ba930496c 42872 debsums_2.0.40_all.deb Files: a71a69500ef1cfc2e8f5399d01d07f4a 895 admin optional debsums_2.0.40.dsc 4154a9fb6d1a8d71953b7c22e0ca2720 46311 admin optional debsums_2.0.40.tar.gz 8300a37bbeecd8b85de0531411056da2 42872 admin optional debsums_2.0.40_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk3m10ACgkQScUZKBnQNIZJSwCePyTQK+8JPI1XblNPBF/wPDCU QesAoJv3nwzTtohe9g/VkwIISSiz+k/a =MuSC -END PGP SIGNATURE- Accepted: debsums_2.0.40.dsc to pool/main/d/debsums/debsums_2.0.40.dsc debsums_2.0.40.tar.gz to pool/main/d/debsums/debsums_2.0.40.tar.gz debsums_2.0.40_all.deb to pool/main/d/debsums/debsums_2.0.40_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted freemat 3.6+dfsg-5 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 00:22:03 +0100 Source: freemat Binary: freemat freemat-data freemat-help Architecture: source all i386 Version: 3.6+dfsg-5 Distribution: unstable Urgency: low Maintainer: Giuseppe Iuculano [EMAIL PROTECTED] Changed-By: Giuseppe Iuculano [EMAIL PROTECTED] Description: freemat- mathematics framework (mostly matlab compatible) freemat-data - freemat data files freemat-help - freemat help files Changes: freemat (3.6+dfsg-5) unstable; urgency=low . * debian/control: Added Vcs-Git and Vcs-Browser control field * debian/control: libarpack2-dev is back, added again in Build-depends * debian/README.source: document dpatch usage, as required by Debian Policy since 3.8.0 Checksums-Sha1: ac8f5bda4fe0af1997b4e7790740b8b1ffccc304 1480 freemat_3.6+dfsg-5.dsc 0a8975c11e0c8b8500fb7246643064812388b24a 15685 freemat_3.6+dfsg-5.diff.gz e05995336968a811889df92642a81c794c32da7d 204526 freemat-data_3.6+dfsg-5_all.deb b14c7e4ef0fc23feb18912516349e630408e9803 3102552 freemat-help_3.6+dfsg-5_all.deb 2eaf90c6f7eedbcc1ec236250c344e1b548b1a24 1343950 freemat_3.6+dfsg-5_i386.deb Checksums-Sha256: a0974b8bddad4c515fa00d1b7e1c3e55bd19c7905c8e66e3365c179baebe6e46 1480 freemat_3.6+dfsg-5.dsc f6205a3041121c9544bed98f3d74f4f5c4a8eb9555c135b66bab60170ebf9e06 15685 freemat_3.6+dfsg-5.diff.gz f915cb05b6a5e039f305bf3feb231e5ae1c4c559172b2f6dfde67a57f3d07100 204526 freemat-data_3.6+dfsg-5_all.deb bc99c98fb17347d1a2462c9c462692fe559e2d437d0025f5474cc944a4cce37a 3102552 freemat-help_3.6+dfsg-5_all.deb 5f16830e23a0bf8ffd98b866e4e9585efe8e37adf046ce9ce47325a36af38357 1343950 freemat_3.6+dfsg-5_i386.deb Files: 526ede46a53e218c162f872b04016239 1480 math optional freemat_3.6+dfsg-5.dsc bcb8240792fe715ccfa98df530bba4a9 15685 math optional freemat_3.6+dfsg-5.diff.gz bcacf9e3b01fbbd2ac60c5cefb90b96e 204526 math optional freemat-data_3.6+dfsg-5_all.deb 38aa61ab1eca7359228253f3d34e5e2c 3102552 math optional freemat-help_3.6+dfsg-5_all.deb 0f7bd2bfa43c8510faa32d882b6adc81 1343950 math optional freemat_3.6+dfsg-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk3k2MACgkQNxpp46476aroUwCfU71OsHuAYZRAZNVJf71vKfO/ u0IAn3p/UCC/6+TktNQish7+bRcsnc+a =gmJB -END PGP SIGNATURE- Accepted: freemat-data_3.6+dfsg-5_all.deb to pool/main/f/freemat/freemat-data_3.6+dfsg-5_all.deb freemat-help_3.6+dfsg-5_all.deb to pool/main/f/freemat/freemat-help_3.6+dfsg-5_all.deb freemat_3.6+dfsg-5.diff.gz to pool/main/f/freemat/freemat_3.6+dfsg-5.diff.gz freemat_3.6+dfsg-5.dsc to pool/main/f/freemat/freemat_3.6+dfsg-5.dsc freemat_3.6+dfsg-5_i386.deb to pool/main/f/freemat/freemat_3.6+dfsg-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libwww-mechanize-perl 1.52-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 00:29:22 -0800 Source: libwww-mechanize-perl Binary: libwww-mechanize-perl Architecture: source all Version: 1.52-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Kees Cook [EMAIL PROTECTED] Description: libwww-mechanize-perl - Automate interaction with websites Closes: 507729 Changes: libwww-mechanize-perl (1.52-1) unstable; urgency=low . [ Rene Mayorga ] * New upstream release (Closes: #507729) * debian/control + set debhelper and compat version to 7 + set standards-version to 3.8.0 + add libtest-taint-perl to B-D-I * debian/rules + refresh using dh-make-perl template + re-add NOINTERNET var before test + www-mechanize logo no longer installed in usr/share * debian/patches - refresh patches * debian/copyright - convert to the (new)format . [ gregor herrmann ] * debian/control: Changed: Switched Vcs-Browser field to ViewSVN (source stanza). * New upstream release. * Add (build) dependency on libhttp-response-encoding-perl and libhttp-server-simple-perl. * Bump versioned dependencies on libwww-perl, liburi-perl and libtest-warn-perl. * Add debian/README.source to document quilt usage, as required by Debian Policy since 3.8.0. . [ Damyan Ivanov ] * update years of copyright * bump perl dependency to 5.8.0 . [ Kees Cook ] * debian/patches/*: add short headers to describe changes. * debian/control: - add libtest-pod-coverage-perl to B-D-I for more tests. - add myself to Uploaders. Checksums-Sha1: 43949bce08f46ad3fcf0571d2c4d74896670c328 1789 libwww-mechanize-perl_1.52-1.dsc e5a358e6c5db6936a40651b8ed82f3fb16b7de1c 118351 libwww-mechanize-perl_1.52.orig.tar.gz 1d7c9da2992defa5e31ab7e22f85967be5e0aefa 4245 libwww-mechanize-perl_1.52-1.diff.gz 9ea61e4f18d2292cc475fdb6af0b17e2c168bb42 101584 libwww-mechanize-perl_1.52-1_all.deb Checksums-Sha256: 5078be48f105503300a2b7c63c2b8f42d1a4947ea6b89870286d0cef7a29d192 1789 libwww-mechanize-perl_1.52-1.dsc e9e610d2785266fbfdc617be0fecb8c8cc4bcdd3b21428be70762592a530a831 118351 libwww-mechanize-perl_1.52.orig.tar.gz 4c5f7dfbed42801207fc69d8ccaeae8f926322ecd36f290abb03371881fd4579 4245 libwww-mechanize-perl_1.52-1.diff.gz 8baaf5bd70e41005f182f863a208f66fc979955dbe7192f92f1f2ea306695004 101584 libwww-mechanize-perl_1.52-1_all.deb Files: 036bb60ec723eb21a2827ea19047d220 1789 perl optional libwww-mechanize-perl_1.52-1.dsc 8ece5ea7690eb6a632a46887f0d2e98e 118351 perl optional libwww-mechanize-perl_1.52.orig.tar.gz 9b33e39024d29d0810300a09d523559e 4245 perl optional libwww-mechanize-perl_1.52-1.diff.gz bb20a3b72296f10791c19638b38ee148 101584 perl optional libwww-mechanize-perl_1.52-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Kees Cook [EMAIL PROTECTED] iEYEARECAAYFAkk3m2sACgkQH/9LqRcGPm1mzACeIV+CcVa/O3eHNwcbtqYGJqxt ZaAAn0WIGLYFdKO+g7mBmnbOEmdKk3ar =7lID -END PGP SIGNATURE- Accepted: libwww-mechanize-perl_1.52-1.diff.gz to pool/main/libw/libwww-mechanize-perl/libwww-mechanize-perl_1.52-1.diff.gz libwww-mechanize-perl_1.52-1.dsc to pool/main/libw/libwww-mechanize-perl/libwww-mechanize-perl_1.52-1.dsc libwww-mechanize-perl_1.52-1_all.deb to pool/main/libw/libwww-mechanize-perl/libwww-mechanize-perl_1.52-1_all.deb libwww-mechanize-perl_1.52.orig.tar.gz to pool/main/libw/libwww-mechanize-perl/libwww-mechanize-perl_1.52.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted liburi-perl 1.37+dfsg-1 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 03 Dec 2008 22:51:28 -0800
Source: liburi-perl
Binary: liburi-perl
Architecture: source all
Version: 1.37+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group [EMAIL PROTECTED]
Changed-By: Kees Cook [EMAIL PROTECTED]
Description:
liburi-perl - Manipulates and accesses URI strings
Closes: 386007 429540 433968 507286
Changes:
liburi-perl (1.37+dfsg-1) unstable; urgency=low
.
[ Kees Cook ]
* New upstream release (Closes: #507286)
+ Closes: #386007 -- Undefined subroutine uri_escape_utf8
+ Closes: #429540 -- URI::_query does not handle ; in URI correctly
* debian/control:
- Take over for the Debian Perl Group, with permission from Stefan
Hornburg.
- Clean up long description (Closes: #433968).
- Bump standards version to 3.8.0 (added Homepage, README.source).
* debian/{control,rules}:
- Add quilt for patch management.
* debian/{watch,repack.sh,rules}: handle repacking to remove rfc2396.txt
(non-redistributable):
- http://rt.cpan.org/Ticket/Display.html?id=41418
* debian/rules:
- Enable tests.
- Correctly handle missing Makefile in clean rule.
* debian/copyright: updated and clarified to match URI.pm and README.
* debian/control: Added: ${misc:Depends} to Depends: field.
.
[ Damyan Ivanov ]
* do not ship README containing information about installing the module
* rules: converted to debhelper 7; adjusted compat and control
* add libbusiness-isbn-perl to B-D-I, enabling additional test
Checksums-Sha1:
a9e343ee687d2933af6be87b9753e4286a86fc7b 1432 liburi-perl_1.37+dfsg-1.dsc
d3af7d32208816541ff233a7eba0705b6e9836dc 73356
liburi-perl_1.37+dfsg.orig.tar.gz
8c38da1cf25e4604ae9276c855802ea83fba2a46 4292 liburi-perl_1.37+dfsg-1.diff.gz
5816fb3962a876bec0023da69173df2af48a97da 88310 liburi-perl_1.37+dfsg-1_all.deb
Checksums-Sha256:
13a7924826ae3e075315fb1d67167030d001975a69503434ba7409b48ed0d86d 1432
liburi-perl_1.37+dfsg-1.dsc
3427e9ef98125e1c9e5ef57aed7ee860185a8d10cb26e292fd7fc9186fdba8e0 73356
liburi-perl_1.37+dfsg.orig.tar.gz
248ca51a7787aaca12a67d7bdf1fe43724b074a552dde2add03cf0b0889cb64d 4292
liburi-perl_1.37+dfsg-1.diff.gz
396a4a19f8982cce6349714ab30fe75527c80e1ec0ecd573f09abd9fe9107468 88310
liburi-perl_1.37+dfsg-1_all.deb
Files:
d7aff4a21b53a2a2a08411a7c18ea6cc 1432 perl optional liburi-perl_1.37+dfsg-1.dsc
8f8c8c83b364a899265dd9ef4a952d41 73356 perl optional
liburi-perl_1.37+dfsg.orig.tar.gz
826c0ef63babffc5333c240b6c81abdc 4292 perl optional
liburi-perl_1.37+dfsg-1.diff.gz
fd00fa6d1b255efb7530cb062e37c5be 88310 perl optional
liburi-perl_1.37+dfsg-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Kees Cook [EMAIL PROTECTED]
iEYEARECAAYFAkk3kgcACgkQH/9LqRcGPm1OkACcDL5XuATeXIc5V50ykct+8qse
9wAAn3l36WKIi8diArFap1DWyeiVkd4i
=p0/b
-END PGP SIGNATURE-
Accepted:
liburi-perl_1.37+dfsg-1.diff.gz
to pool/main/libu/liburi-perl/liburi-perl_1.37+dfsg-1.diff.gz
liburi-perl_1.37+dfsg-1.dsc
to pool/main/libu/liburi-perl/liburi-perl_1.37+dfsg-1.dsc
liburi-perl_1.37+dfsg-1_all.deb
to pool/main/libu/liburi-perl/liburi-perl_1.37+dfsg-1_all.deb
liburi-perl_1.37+dfsg.orig.tar.gz
to pool/main/libu/liburi-perl/liburi-perl_1.37+dfsg.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted base-files 5 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 10:04:04 +0100 Source: base-files Binary: base-files Architecture: source powerpc Version: 5 Distribution: unstable Urgency: low Maintainer: Santiago Vila [EMAIL PROTECTED] Changed-By: Santiago Vila [EMAIL PROTECTED] Description: base-files - Debian base system miscellaneous files Changes: base-files (5) unstable; urgency=low . * Changed issue, issue.net and debian_version to read 5.0. * Changed FAQ so that users of lenny as stable will know what happens when they upgrade to the new testing. Checksums-Sha1: 1b1f368402b41ce00f6d6e7101c1f3f6d8b3b30b 652 base-files_5.dsc 429a2e3dfa15e3c420d2c3c8f82f32b1395cba45 58823 base-files_5.tar.gz 34ce367fc188440012c823a6f8b5d0ae759b3e39 60240 base-files_5_powerpc.deb Checksums-Sha256: f907e1c817eb44149d1927a9926c31ae437ebdeb2dc74305a99cabe427d7 652 base-files_5.dsc 87970f967e082972f43482ea56c9301bf08ec48942f65c50a636e2918add1c33 58823 base-files_5.tar.gz 50e5a38306d38265e8848dedf3f196b5ccc59e77c43742800fc30875f362f8bc 60240 base-files_5_powerpc.deb Files: 20033d7def4de3a8c5ea93a476ae933c 652 admin required base-files_5.dsc 7c76c761a760614bd6699177a79d77f4 58823 admin required base-files_5.tar.gz 2cbd509012311020492a64e9781ace90 60240 admin required base-files_5_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJN57rd9Uuvj7yPNYRAlqxAKDN8w+N02y4co7dYx9gIecPrD22ugCgz7wh I0TgadaGYeEz/FEVhubAVuc= =9u8M -END PGP SIGNATURE- Accepted: base-files_5.dsc to pool/main/b/base-files/base-files_5.dsc base-files_5.tar.gz to pool/main/b/base-files/base-files_5.tar.gz base-files_5_powerpc.deb to pool/main/b/base-files/base-files_5_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rpm2html 1.9.7-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 11:16:33 +0100 Source: rpm2html Binary: rpm2html Architecture: source amd64 Version: 1.9.7-1 Distribution: unstable Urgency: low Maintainer: Michal Čihař [EMAIL PROTECTED] Changed-By: Michal Čihař [EMAIL PROTECTED] Description: rpm2html - generate HTML index from directories of RPMs Changes: rpm2html (1.9.7-1) unstable; urgency=low . * New upstream version. * Switch Vcs-Browser to viewsvn. Checksums-Sha1: 99b2061c4eab2cd3f52316f3b21a04d99d75ca8d 1213 rpm2html_1.9.7-1.dsc 68696875c33c9531c06f052f577054d222f42176 198137 rpm2html_1.9.7.orig.tar.gz 3fb29787265b87bbc543ff73cbb12edfee6a650f 4353 rpm2html_1.9.7-1.diff.gz 31a6238d0ea6985ad646922b1d1d568d19737341 75392 rpm2html_1.9.7-1_amd64.deb Checksums-Sha256: 74685843dd48c66c9949fb28dfa1493635d888784119f313d8d8d1855fd2201d 1213 rpm2html_1.9.7-1.dsc c894d53ee288bc1593d619d9942d0063f5600b22b56257ad7d151d5914fed359 198137 rpm2html_1.9.7.orig.tar.gz a6405be10f51e165394dd699dbc9d93eebec273ffef323105e80c117db2d3fa9 4353 rpm2html_1.9.7-1.diff.gz d5358927d9f825202b67b46d85798e8803f1510a7284ad033adad2ba255c5e62 75392 rpm2html_1.9.7-1_amd64.deb Files: bc20d2ae25d1c71b833cb5ac07d12ca8 1213 web extra rpm2html_1.9.7-1.dsc 769e42ab7e6d4e71c155e099d5a60fdf 198137 web extra rpm2html_1.9.7.orig.tar.gz 1c50ac70fbe8db6983eb2e2c4a629f19 4353 web extra rpm2html_1.9.7-1.diff.gz 0dfc69c3351d7d5f8a8d7374bdc8b80f 75392 web extra rpm2html_1.9.7-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk3rvsACgkQ3DVS6DbnVgS8jACfetUN2rUlpbgaKFrJodGjZuz9 o1wAn3D4LFJjdIQA1+aWOo7toIatQuQQ =w8vJ -END PGP SIGNATURE- Accepted: rpm2html_1.9.7-1.diff.gz to pool/main/r/rpm2html/rpm2html_1.9.7-1.diff.gz rpm2html_1.9.7-1.dsc to pool/main/r/rpm2html/rpm2html_1.9.7-1.dsc rpm2html_1.9.7-1_amd64.deb to pool/main/r/rpm2html/rpm2html_1.9.7-1_amd64.deb rpm2html_1.9.7.orig.tar.gz to pool/main/r/rpm2html/rpm2html_1.9.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libdbd-odbc-ruby 0.2.4-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Dec 2008 21:50:21 +0200 Source: libdbd-odbc-ruby Binary: libdbd-odbc-ruby libdbd-odbc-ruby1.8 Architecture: source all Version: 0.2.4-1 Distribution: experimental Urgency: low Maintainer: Dmitry Borodaenko [EMAIL PROTECTED] Changed-By: Dmitry Borodaenko [EMAIL PROTECTED] Description: libdbd-odbc-ruby - Ruby/DBI ODBC driver libdbd-odbc-ruby1.8 - Ruby/DBI ODBC driver for Ruby 1.8 Changes: libdbd-odbc-ruby (0.2.4-1) experimental; urgency=low . * First release of libdbd-mysql-ruby as a separate package (prior to Ruby/DBI 0.4.0, all DBDs were included in the libdbi-ruby package). * Prepare to build versions for Ruby 1.8 and 1.9 (depends on #507695). Checksums-Sha1: 73cbbd63e7930b3b75e0fe88e6de246ec52b84b3 1095 libdbd-odbc-ruby_0.2.4-1.dsc 21d7b394958c7e633a72cc95e2d1e85897168a8c 51149 libdbd-odbc-ruby_0.2.4.orig.tar.gz 5f3a2e8ff207a0ca867e042b4ea027127264e3e7 2251 libdbd-odbc-ruby_0.2.4-1.diff.gz 0861a3710b20a21e17d1ed6f210b0e519ba377b7 28750 libdbd-odbc-ruby_0.2.4-1_all.deb 1ed9cc4e6412c863f8f2bf8641364ed165e59543 33076 libdbd-odbc-ruby1.8_0.2.4-1_all.deb Checksums-Sha256: f115807fe74d1c7b043b7864b411f95ed28480d28b0905fa385195f91ee2bc70 1095 libdbd-odbc-ruby_0.2.4-1.dsc 544f6645a96cddcb2d1ce540db0785b7ea7cf70dd9c2a38cfb0db811b198d6a1 51149 libdbd-odbc-ruby_0.2.4.orig.tar.gz 3f698098c63966a916091f22070a874a15fef68f51c1e484283a6f72e30f71f9 2251 libdbd-odbc-ruby_0.2.4-1.diff.gz aee6a0f85eb7d9a37137f46523ab009772da269163d1461a4b54ecbd7ee76a9b 28750 libdbd-odbc-ruby_0.2.4-1_all.deb 04595fc9e39b1833ce19208cd4bde441d0e37b21574cc53d11c85b48a4903063 33076 libdbd-odbc-ruby1.8_0.2.4-1_all.deb Files: 8090e5b81183b6281517c81e019b1b80 1095 interpreters optional libdbd-odbc-ruby_0.2.4-1.dsc 37ac5fa4aa4dc0e5155291aaa64c2f67 51149 interpreters optional libdbd-odbc-ruby_0.2.4.orig.tar.gz ed867db38dd805efcab5b01ff19df986 2251 interpreters optional libdbd-odbc-ruby_0.2.4-1.diff.gz 46a425f12f16e3a1000b6c3e7bf37fca 28750 interpreters optional libdbd-odbc-ruby_0.2.4-1_all.deb b6cb13c96b8cca0e9ae3952bdcc62f58 33076 interpreters optional libdbd-odbc-ruby1.8_0.2.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk25FkACgkQxhqJXoXuPg6heQCeOVxiSLA/BI0V2isbHXp9mWor NbIAn0WMErmiTlulfg+f2rAHEl8E4dsq =7Cfy -END PGP SIGNATURE- Accepted: libdbd-odbc-ruby1.8_0.2.4-1_all.deb to pool/main/libd/libdbd-odbc-ruby/libdbd-odbc-ruby1.8_0.2.4-1_all.deb libdbd-odbc-ruby_0.2.4-1.diff.gz to pool/main/libd/libdbd-odbc-ruby/libdbd-odbc-ruby_0.2.4-1.diff.gz libdbd-odbc-ruby_0.2.4-1.dsc to pool/main/libd/libdbd-odbc-ruby/libdbd-odbc-ruby_0.2.4-1.dsc libdbd-odbc-ruby_0.2.4-1_all.deb to pool/main/libd/libdbd-odbc-ruby/libdbd-odbc-ruby_0.2.4-1_all.deb libdbd-odbc-ruby_0.2.4.orig.tar.gz to pool/main/libd/libdbd-odbc-ruby/libdbd-odbc-ruby_0.2.4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gcx 0.9.11-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Dec 2008 23:40:42 +0100 Source: gcx Binary: gcx Architecture: source amd64 Version: 0.9.11-4 Distribution: unstable Urgency: high Maintainer: Riccardo Stagni [EMAIL PROTECTED] Changed-By: Riccardo Stagni [EMAIL PROTECTED] Description: gcx- astronomical image processing and photometry gtk+ application Closes: 507667 Changes: gcx (0.9.11-4) unstable; urgency=high . * RC bugfix picked from upstream cvs (segfaults on 64-bit systems) (Closes: #507667) Checksums-Sha1: e0169da82e9a300efacfe2b2d75a426088b96725 1099 gcx_0.9.11-4.dsc 80f8285c44d29f71bba2ae833ccbc8ee0f5c5f51 4831 gcx_0.9.11-4.diff.gz f2ceeea6bec8997dadff37000d1a8682fefe95bd 348108 gcx_0.9.11-4_amd64.deb Checksums-Sha256: 61068fcfa14d17efd443e11e3a56e1ebdae58a91efbceaccc23cdd7861a337bc 1099 gcx_0.9.11-4.dsc bfcb9d5788273cddab09ac4540cb9c5b2993867810f0c05cffb6b6461e668e18 4831 gcx_0.9.11-4.diff.gz 511bbc99aa81da9511413f676ef19b3d1548e495906983949c813b17ee28749b 348108 gcx_0.9.11-4_amd64.deb Files: 35c472896ac6b91b3099ff7e22a455b4 1099 science extra gcx_0.9.11-4.dsc 23aa6cd82b02cca7883964c8cf96977b 4831 science extra gcx_0.9.11-4.diff.gz 17f8022eb091a63e568f95df467dd435 348108 science extra gcx_0.9.11-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJN7rS9LSwzHl+v6sRAujRAJ4/6k0DGfAl5moB70+CE+00XxjSywCgjcpY wbNGpbJyI28DDtlffcw85uM= =CxwF -END PGP SIGNATURE- Accepted: gcx_0.9.11-4.diff.gz to pool/main/g/gcx/gcx_0.9.11-4.diff.gz gcx_0.9.11-4.dsc to pool/main/g/gcx/gcx_0.9.11-4.dsc gcx_0.9.11-4_amd64.deb to pool/main/g/gcx/gcx_0.9.11-4_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pitivi 0.11.2.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 12:47:07 +0100 Source: pitivi Binary: pitivi Architecture: source all Version: 0.11.2.2-1 Distribution: experimental Urgency: low Maintainer: Loic Minier [EMAIL PROTECTED] Changed-By: Sebastian Dröge [EMAIL PROTECTED] Description: pitivi - non-linear audio/video editor using GStreamer Changes: pitivi (0.11.2.2-1) experimental; urgency=low . * New upstream pre-release: + debian/control: - Update build dependencies. - Update gnonlin dependency version to 0.10.10. - Depend on python-dbus. - Recommend hal for the webcam support. Checksums-Sha1: 54129ebad7ff5dd6b393aa8eb7e3daed43b00d1a 1153 pitivi_0.11.2.2-1.dsc 5fb2583725588b8779fe710ff05c055b90ff234f 534749 pitivi_0.11.2.2.orig.tar.gz cebb1729a6b09e459d3aed0f31787d563d2674bd 3763 pitivi_0.11.2.2-1.diff.gz 259b7c0e660dc4174cad28b6761569311f95f841 275004 pitivi_0.11.2.2-1_all.deb Checksums-Sha256: ec4acaec19604e8a2af55f509c9e837a50f1bece31a655108a1211f3a5f22f17 1153 pitivi_0.11.2.2-1.dsc 09bd1f052579dc775e2f839ded083b86904c30bb990393047eb68ddc20699e1f 534749 pitivi_0.11.2.2.orig.tar.gz 401ee58e215d40b779b1f286ab926e2319f4f83166edb59652587f90cafe4d5d 3763 pitivi_0.11.2.2-1.diff.gz 14c81909986606db11892cd8cc163985de3cef2f54bb1055c72e2dec8135 275004 pitivi_0.11.2.2-1_all.deb Files: b2535177c88491fcf1b3587ae7c472fb 1153 gnome optional pitivi_0.11.2.2-1.dsc 5eb1a16386cea3d82fd00f7f4105e5ba 534749 gnome optional pitivi_0.11.2.2.orig.tar.gz 9db25a231fd01cb43c6b81f5f49a1b4e 3763 gnome optional pitivi_0.11.2.2-1.diff.gz 400e8a62ff5870359e78ed4965316639 275004 gnome optional pitivi_0.11.2.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk3xVQACgkQBsBdh1vkHyGWWACgp3ckCkJV3ZebQmKe2T326tRP arQAnRSt/MwrRviyfD7IGyBr4paYNxBv =5bkd -END PGP SIGNATURE- Accepted: pitivi_0.11.2.2-1.diff.gz to pool/main/p/pitivi/pitivi_0.11.2.2-1.diff.gz pitivi_0.11.2.2-1.dsc to pool/main/p/pitivi/pitivi_0.11.2.2-1.dsc pitivi_0.11.2.2-1_all.deb to pool/main/p/pitivi/pitivi_0.11.2.2-1_all.deb pitivi_0.11.2.2.orig.tar.gz to pool/main/p/pitivi/pitivi_0.11.2.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted isight-firmware-tools 1.2-7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 20:25:16 +0900 Source: isight-firmware-tools Binary: isight-firmware-tools Architecture: source i386 Version: 1.2-7 Distribution: unstable Urgency: low Maintainer: Nobuhiro Iwamatsu [EMAIL PROTECTED] Changed-By: Nobuhiro Iwamatsu [EMAIL PROTECTED] Description: isight-firmware-tools - tools for dealing with Apple iSight firmware Changes: isight-firmware-tools (1.2-7) unstable; urgency=low . * Updated French debconf templates. Checksums-Sha1: e48f50ffb65ae8774002abb656a85b53803cf23f 1189 isight-firmware-tools_1.2-7.dsc 46b16daf34b159e146da6bec8993fe317f4915f1 15372 isight-firmware-tools_1.2-7.diff.gz 96d6db272d6e7e9c54817ba5bbb7874ab0eb8b50 32018 isight-firmware-tools_1.2-7_i386.deb Checksums-Sha256: 36d2a43c213ec2e699e16c7c715e33b6aea9b7741730627f424bec6a54e53df2 1189 isight-firmware-tools_1.2-7.dsc bdb3b2b793a8751eaaeb5c8222764ce3be96a1832d4540b3d860aba64a94ecfa 15372 isight-firmware-tools_1.2-7.diff.gz 2571a879c9f6da92424081ba50fa66d63528b4a863fee7f979d833eacdd72088 32018 isight-firmware-tools_1.2-7_i386.deb Files: edcbf1f9cb10d034b182ed6684c227e1 1189 contrib/graphics extra isight-firmware-tools_1.2-7.dsc a87bf116aded1779763b792a02689310 15372 contrib/graphics extra isight-firmware-tools_1.2-7.diff.gz fee35249e6c06ee95dbf34c54b859ca9 32018 contrib/graphics extra isight-firmware-tools_1.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk3wbkACgkQQSHHQzFw6+l7OACgh2U3eFUSdb5e4gaxh7nMj0Ef CsIAoIxvdBoDagSb5dQZuvrN/GU1q8yr =Gy4p -END PGP SIGNATURE- Accepted: isight-firmware-tools_1.2-7.diff.gz to pool/contrib/i/isight-firmware-tools/isight-firmware-tools_1.2-7.diff.gz isight-firmware-tools_1.2-7.dsc to pool/contrib/i/isight-firmware-tools/isight-firmware-tools_1.2-7.dsc isight-firmware-tools_1.2-7_i386.deb to pool/contrib/i/isight-firmware-tools/isight-firmware-tools_1.2-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ttf-vlgothic 20081203-2 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 04 Dec 2008 21:13:46 +0900
Source: ttf-vlgothic
Binary: ttf-vlgothic
Architecture: source all
Version: 20081203-2
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force [EMAIL PROTECTED]
Changed-By: Hideki Yamane (Debian-JP) [EMAIL PROTECTED]
Description:
ttf-vlgothic - Japanese TrueType font from Vine Linux
Closes: 507745
Changes:
ttf-vlgothic (20081203-2) unstable; urgency=low
.
* debian/ttf-vlgothic.{postinst,prerm}
- Fix install failure for xset: unable to open display
revert changes introduced in 20081124-2. It does not useful and
buggy. (Closes: #507745)
Checksums-Sha1:
b2d891988a1b1976f6ec16a880400efccf0d592a 1328 ttf-vlgothic_20081203-2.dsc
ba3c63853530e881a20a123e6232f56ffc1bb19f 8433 ttf-vlgothic_20081203-2.diff.gz
a848f9d85b2d610f35b08504fa6475831672d2c5 4909550
ttf-vlgothic_20081203-2_all.deb
Checksums-Sha256:
b06bc943b9699b9ca4e9e9fae0658c13528a1fa076790a2bfa6471e72d88f2a4 1328
ttf-vlgothic_20081203-2.dsc
2a8b5f3b1612ab11f4baa1f9ccc028c0de4828d507727d97d0533dda40853bdf 8433
ttf-vlgothic_20081203-2.diff.gz
3e0d51c17befdbcfeaa217662854bcb25bd7ca63bdc767cdc3f5eb1c3b0d317f 4909550
ttf-vlgothic_20081203-2_all.deb
Files:
bc7043342e608f63dd2b35e383e71dab 1328 x11 optional ttf-vlgothic_20081203-2.dsc
2191dc40ae1610f1efb0262a44890df1 8433 x11 optional
ttf-vlgothic_20081203-2.diff.gz
fa33b538e38ca7932471af7db9298c93 4909550 x11 optional
ttf-vlgothic_20081203-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkk3yZkACgkQIu0hy8THJksfOwCePBwdTLu4VXcyHRzxUFgshy31
HVwAn3eiRahV69ZP4t6dRw1/LWo907mM
=x3P1
-END PGP SIGNATURE-
Accepted:
ttf-vlgothic_20081203-2.diff.gz
to pool/main/t/ttf-vlgothic/ttf-vlgothic_20081203-2.diff.gz
ttf-vlgothic_20081203-2.dsc
to pool/main/t/ttf-vlgothic/ttf-vlgothic_20081203-2.dsc
ttf-vlgothic_20081203-2_all.deb
to pool/main/t/ttf-vlgothic/ttf-vlgothic_20081203-2_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted virt-viewer 0.0.3-6 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 12:41:50 +0100 Source: virt-viewer Binary: virt-viewer mozilla-virt-viewer Architecture: source powerpc Version: 0.0.3-6 Distribution: experimental Urgency: low Maintainer: Debian Libvirt Maintainers [EMAIL PROTECTED] Changed-By: Guido Günther [EMAIL PROTECTED] Description: mozilla-virt-viewer - A virt-viewer widget for GTK+ (mozilla plugin) virt-viewer - Displaying the graphical console of a virtual machine Closes: 507549 Changes: virt-viewer (0.0.3-6) experimental; urgency=low . * [1f49897] install missing binary (Closes: #507549) Checksums-Sha1: f4c65de61e9bb5aedcd8d1e07e99ff89b0736d98 1432 virt-viewer_0.0.3-6.dsc 2ff0fd74b2d337a32a5d214b4980a35cdcc89617 2797 virt-viewer_0.0.3-6.diff.gz a2e654b5549071ba7a19e513eac6e7ff331efed8 23790 virt-viewer_0.0.3-6_powerpc.deb 25e1237098f4cfc900579acab351f4cb4fcf594c 24132 mozilla-virt-viewer_0.0.3-6_powerpc.deb Checksums-Sha256: 4dde565de63abea426c2441274a607a07d819aeb110709be6f181963929209e9 1432 virt-viewer_0.0.3-6.dsc 6675acea6f8b3efc50713875fe93044fd4260d3eda53945f2b2c0013384f5646 2797 virt-viewer_0.0.3-6.diff.gz b8c0ef1e3af7407848271fd5f52497762d7c713dece9c1c96fde1f195a425239 23790 virt-viewer_0.0.3-6_powerpc.deb a75c9b860794fa563c049f003e31485f70b72ee8dc61f07438f8638e06743aa9 24132 mozilla-virt-viewer_0.0.3-6_powerpc.deb Files: ca735ab666385448cb8f5538eef02cf4 1432 admin extra virt-viewer_0.0.3-6.dsc a5dc64fc9ba5340b8a2783b663805ec2 2797 admin extra virt-viewer_0.0.3-6.diff.gz 467b74781096ec3fc92d69b06f98c0bb 23790 admin extra virt-viewer_0.0.3-6_powerpc.deb 50fbc29c0508920face51ffde115 24132 web extra mozilla-virt-viewer_0.0.3-6_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJN8pgn88szT8+ZCYRAiWEAJkBXFsl6kjlg3wdmaychBJwsuJdXwCeOPBJ /unBXvTZ6fRM65SvSjRE0SY= =t96h -END PGP SIGNATURE- Accepted: mozilla-virt-viewer_0.0.3-6_powerpc.deb to pool/main/v/virt-viewer/mozilla-virt-viewer_0.0.3-6_powerpc.deb virt-viewer_0.0.3-6.diff.gz to pool/main/v/virt-viewer/virt-viewer_0.0.3-6.diff.gz virt-viewer_0.0.3-6.dsc to pool/main/v/virt-viewer/virt-viewer_0.0.3-6.dsc virt-viewer_0.0.3-6_powerpc.deb to pool/main/v/virt-viewer/virt-viewer_0.0.3-6_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted milter-greylist 4.1.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 12:34:10 + Source: milter-greylist Binary: milter-greylist Architecture: source i386 Version: 4.1.8-1 Distribution: unstable Urgency: low Maintainer: Paul Martin [EMAIL PROTECTED] Changed-By: Paul Martin [EMAIL PROTECTED] Description: milter-greylist - Greylist milter for sendmail Changes: milter-greylist (4.1.8-1) unstable; urgency=low . * New upstream release * Correct some lintian warnings: + debhelper-but-no-misc-depends milter-greylist + quilt-patch-missing-description * Upload to unstable. Checksums-Sha1: c300773ba8d394c9645e7ea2daea9af5c4b62138 1072 milter-greylist_4.1.8-1.dsc 6a8e61f13bc1e2d2215bee492abc2313559cc228 204255 milter-greylist_4.1.8.orig.tar.gz e80bb2d9df82868e5bbd3cefa85ed40b77ac3a17 7855 milter-greylist_4.1.8-1.diff.gz cc270d789bf761ea558418626260e54dc33eaadf 124726 milter-greylist_4.1.8-1_i386.deb Checksums-Sha256: 69c54256e24f272fcf6f41006f2ca376ef4316495e1b5100a216f6dee22f04aa 1072 milter-greylist_4.1.8-1.dsc d66d78d5a60f0b37fe34666de47ed9d441856088fcf0a1445975fa47ebe78255 204255 milter-greylist_4.1.8.orig.tar.gz c4748f9db3b688f2aa2e8c6062daac99a4727db6f7bf628d56287d443d18a21b 7855 milter-greylist_4.1.8-1.diff.gz 8cb5774c52c2d4827000cc7c32c6c54920255f0e983c443fe97319b4bdc1e9fd 124726 milter-greylist_4.1.8-1_i386.deb Files: cde0570eebbd7429c3280fc992a83667 1072 mail extra milter-greylist_4.1.8-1.dsc 89f2f6644b42978a4e48957e4cae9356 204255 mail extra milter-greylist_4.1.8.orig.tar.gz fac179540357a84d5789aa3c54d643ef 7855 mail extra milter-greylist_4.1.8-1.diff.gz 9f527ff9bcd30b3443f42136d867aabb 124726 mail extra milter-greylist_4.1.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJN88z+gi+rt7UWRIRAvygAJ92ebJtALdbDT3ao2Qr0d1d/m/RdQCcDaa7 bdno1x/WMFx/ehRGK3uRYfQ= =vcEO -END PGP SIGNATURE- Accepted: milter-greylist_4.1.8-1.diff.gz to pool/main/m/milter-greylist/milter-greylist_4.1.8-1.diff.gz milter-greylist_4.1.8-1.dsc to pool/main/m/milter-greylist/milter-greylist_4.1.8-1.dsc milter-greylist_4.1.8-1_i386.deb to pool/main/m/milter-greylist/milter-greylist_4.1.8-1_i386.deb milter-greylist_4.1.8.orig.tar.gz to pool/main/m/milter-greylist/milter-greylist_4.1.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pyroom 0.3.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 17:22:47 +0530 Source: pyroom Binary: pyroom Architecture: source all Version: 0.3.2-1 Distribution: unstable Urgency: low Maintainer: Kartik Mistry [EMAIL PROTECTED] Changed-By: Kartik Mistry [EMAIL PROTECTED] Description: pyroom - distractionless fullscreen text editor Closes: 507680 Changes: pyroom (0.3.2-1) unstable; urgency=low . * New upstream release: * debian/control: + Fixed too broad dependencies, Thanks to Anthony L. Awtrey [EMAIL PROTECTED] (Closes: #507680) + Dropped build-depends on python-setuptools, Upstream is using distutils, Thanks to Florian Heinle for pointing this * debian/patches/01_manpage_typo_fix.dpatch: + Dropped patch, Merged with upstream Checksums-Sha1: ef1ae8e88424024540653b5a380abbd7d51de314 1052 pyroom_0.3.2-1.dsc 2dcc745d4f47b75796b006150077fe146c38a938 36952 pyroom_0.3.2.orig.tar.gz 938748ba277a343323ffb61ae91149f4e6df89a3 2466 pyroom_0.3.2-1.diff.gz 1b3b558a4b3d936e23dd6b576d9b3c392baa1993 29496 pyroom_0.3.2-1_all.deb Checksums-Sha256: 6df692281d2ced1848f78a0dff7c83483a9420f1d6469b3d4e93a01271549c08 1052 pyroom_0.3.2-1.dsc 0530cef80c8b3f7598d903deebb96cf2fc4c71352439e30b081e1f526cfdc50c 36952 pyroom_0.3.2.orig.tar.gz 202a3228961bd4988599eafef02c76d3aa3680d8dac4b4a5e1f60ec284d808d0 2466 pyroom_0.3.2-1.diff.gz 109969d5d9268cf7b8a016d2f6fe81da7d112afd66809f585a1cdb3b1a9dac51 29496 pyroom_0.3.2-1_all.deb Files: 48d1c75c1804d08e9cb4588a99b39567 1052 editors optional pyroom_0.3.2-1.dsc 288d7d5a9853fe38201eec1dec12866d 36952 editors optional pyroom_0.3.2.orig.tar.gz 54c35a327ed5038535005d6c70d8c5ce 2466 editors optional pyroom_0.3.2-1.diff.gz f5758d0089e1db44341a47f38b56c86f 29496 editors optional pyroom_0.3.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk31TkACgkQoRg/jtECjI0HXgCeJPsbs6wY3h8e3U1x4nl+wMqc F8sAoIr0l0s8YB2QArTIJrNjhI2GZeSj =p4ZZ -END PGP SIGNATURE- Accepted: pyroom_0.3.2-1.diff.gz to pool/main/p/pyroom/pyroom_0.3.2-1.diff.gz pyroom_0.3.2-1.dsc to pool/main/p/pyroom/pyroom_0.3.2-1.dsc pyroom_0.3.2-1_all.deb to pool/main/p/pyroom/pyroom_0.3.2-1_all.deb pyroom_0.3.2.orig.tar.gz to pool/main/p/pyroom/pyroom_0.3.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wbxml2 0.9.2-7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 13:42:44 +0100 Source: wbxml2 Binary: libwbxml2-dev libwbxml2-0-dbg libwbxml2-0 libwbxml2-utils Architecture: source i386 Version: 0.9.2-7 Distribution: unstable Urgency: high Maintainer: Michael Banck [EMAIL PROTECTED] Changed-By: Michael Banck [EMAIL PROTECTED] Description: libwbxml2-0 - WBXML parsing and encoding library libwbxml2-0-dbg - WBXML library development file libwbxml2-dev - WBXML library development file libwbxml2-utils - Binary XML utilities Closes: 506740 507689 Changes: wbxml2 (0.9.2-7) unstable; urgency=high . * Urgency `high' due to RC bug fix. * debian/patches/09-devinf-doctype.patch: New patch, no longer hardcodes the Syncml version in the device information document, by Michael Bell; closes: #506740. * debian/patches/10-fix-wbxml-public-ids.patch: New patch, swaps the WBXML_PUBLIC_ID_SYNCML_METINF12 and WBXML_PUBLIC_ID_SYNCML_DEVINF12 values to be in line with the OMNA standard; closes: #507689. Checksums-Sha1: 70245952529813fb6946f47c26de5ea4d0b21da8 1120 wbxml2_0.9.2-7.dsc 3b6bb8e117cda04c99dd120f2e3484c77aca0ee8 11559 wbxml2_0.9.2-7.diff.gz d52a2fc4710816d2c59bc4e124e1d7914765e242 91266 libwbxml2-dev_0.9.2-7_i386.deb 1c550ae2ca593e5ba053a9b2f9ec2c07fb1c232a 88564 libwbxml2-0-dbg_0.9.2-7_i386.deb 3a067fd07a6391d54db18e653cca1c4d7615a3a7 67478 libwbxml2-0_0.9.2-7_i386.deb 0559099f5f4267549aeff470d2fc2ebd63e39126 21478 libwbxml2-utils_0.9.2-7_i386.deb Checksums-Sha256: e08e850c290bb89ed82b32c751c03ddd0b200925bf6b1311f02f74d2dc19db6e 1120 wbxml2_0.9.2-7.dsc 246750b0f273ce7487247d8256e00e170a4726f247377b3e2a57448fb8aa9da1 11559 wbxml2_0.9.2-7.diff.gz 3aa7fa8595086f6be8a30c9a8693f6ccd287b5dba0b20ea35d011c23111df7db 91266 libwbxml2-dev_0.9.2-7_i386.deb 741f09efdf9fb88c9072f42dec86041a2ac364b2976cadcb8d89e3e6c92f1a2b 88564 libwbxml2-0-dbg_0.9.2-7_i386.deb 16283c51f246e6cb8c83bc054de279d08a6b99bc114960d8f1c765f1d3b9a911 67478 libwbxml2-0_0.9.2-7_i386.deb 713a71777bee9e9f4e38fe4bdf3ca92a07f99dd22f23dafcbcee3f17494597fe 21478 libwbxml2-utils_0.9.2-7_i386.deb Files: 5f1aeb2c52f9275921b3800a02dff9e1 1120 libs optional wbxml2_0.9.2-7.dsc 3c0852b347db1eeada9d732d71ef8194 11559 libs optional wbxml2_0.9.2-7.diff.gz d25da5b29519051abbf29528b557b7c8 91266 libdevel optional libwbxml2-dev_0.9.2-7_i386.deb 823e20301fc0fe03d23c7d8cfa524fda 88564 libdevel extra libwbxml2-0-dbg_0.9.2-7_i386.deb d3df66216fdad101e734180e89f91ec5 67478 libs optional libwbxml2-0_0.9.2-7_i386.deb 986ef686790a41a68bce3a698ab46088 21478 text optional libwbxml2-utils_0.9.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFJN9FTmHaJYZ7RAb8RAlmiAKCAN0jGafxN8KOycmyqrTOjr873TQCgipK1 27RvRIX7oBQzxiO+Kqxw4mE= =ZyNV -END PGP SIGNATURE- Accepted: libwbxml2-0-dbg_0.9.2-7_i386.deb to pool/main/w/wbxml2/libwbxml2-0-dbg_0.9.2-7_i386.deb libwbxml2-0_0.9.2-7_i386.deb to pool/main/w/wbxml2/libwbxml2-0_0.9.2-7_i386.deb libwbxml2-dev_0.9.2-7_i386.deb to pool/main/w/wbxml2/libwbxml2-dev_0.9.2-7_i386.deb libwbxml2-utils_0.9.2-7_i386.deb to pool/main/w/wbxml2/libwbxml2-utils_0.9.2-7_i386.deb wbxml2_0.9.2-7.diff.gz to pool/main/w/wbxml2/wbxml2_0.9.2-7.diff.gz wbxml2_0.9.2-7.dsc to pool/main/w/wbxml2/wbxml2_0.9.2-7.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libgdata-java 1.26.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 14:35:11 +0100 Source: libgdata-java Binary: libgdata-java Architecture: source all Version: 1.26.0-1 Distribution: experimental Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Torsten Werner [EMAIL PROTECTED] Description: libgdata-java - simple standard protocol for reading and writing data on the web Changes: libgdata-java (1.26.0-1) experimental; urgency=low . * New upstream release Checksums-Sha1: b8ffdfbe26f56fd0371ede4a1f71cbc0d25f0892 1401 libgdata-java_1.26.0-1.dsc 29fbfe11e3efca15e49776d99617ead2e0e6d32b 506127 libgdata-java_1.26.0.orig.tar.gz 48669053198142fa37fbd3254f242789d79ec5f3 2346 libgdata-java_1.26.0-1.diff.gz f36412b035ee2cc9210f22aa81190c0b0dfce11a 1074598 libgdata-java_1.26.0-1_all.deb Checksums-Sha256: 57b0a12c59bb610f155fc1c349d46ac12a80cf48ca744251240c1c4a645e00ad 1401 libgdata-java_1.26.0-1.dsc d0ad826e7272ffa4f3a98ec76b93c5a7a92169e9e013d839ce0eeb7e01eb96a0 506127 libgdata-java_1.26.0.orig.tar.gz 27c6dde5409adaa5188258feeaacf5fa26c7ed19607ac447560a0f8a96bdbeb7 2346 libgdata-java_1.26.0-1.diff.gz 3971256da0028c530a099a6abbf26c20b7a231f101a64a6b220cae1547ace9ae 1074598 libgdata-java_1.26.0-1_all.deb Files: 273c0519786765f3204f6141c09b14d7 1401 libs optional libgdata-java_1.26.0-1.dsc 5fa248006af650f4f561be4b755d97d3 506127 libs optional libgdata-java_1.26.0.orig.tar.gz ff3dcc83bd03bd9ed5fc6ff08a1a8e1c 2346 libs optional libgdata-java_1.26.0-1.diff.gz eb58a5f1225ad7b5e15360beb06e0b76 1074598 libs optional libgdata-java_1.26.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk33e8ACgkQfY3dicTPjsN/ugCgk2ZJ1tkWC6pBjxLRoym8sFbu Ez4An36Jbj2QWoquZTjtg6UPeJQA2Bt8 =XtDL -END PGP SIGNATURE- Accepted: libgdata-java_1.26.0-1.diff.gz to pool/main/libg/libgdata-java/libgdata-java_1.26.0-1.diff.gz libgdata-java_1.26.0-1.dsc to pool/main/libg/libgdata-java/libgdata-java_1.26.0-1.dsc libgdata-java_1.26.0-1_all.deb to pool/main/libg/libgdata-java/libgdata-java_1.26.0-1_all.deb libgdata-java_1.26.0.orig.tar.gz to pool/main/libg/libgdata-java/libgdata-java_1.26.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcap2 2.15-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 14:15:48 +0100 Source: libcap2 Binary: libcap2-dev libcap2-bin libcap2 Architecture: source i386 Version: 2.15-3 Distribution: experimental Urgency: low Maintainer: Torsten Werner [EMAIL PROTECTED] Changed-By: Torsten Werner [EMAIL PROTECTED] Description: libcap2- support for getting/setting POSIX.1e capabilities libcap2-bin - basic utility programs for using capabilities libcap2-dev - development libraries and header files for libcap2 Closes: 507781 Changes: libcap2 (2.15-3) experimental; urgency=low . * Set Priority: standard for binary package libcap2. (Closes: #507781) Checksums-Sha1: c652153ce65bc1a8ef87fcd7d1272a7c3a4f0531 1168 libcap2_2.15-3.dsc 61d3fd8cf33cee948564aa8063fdbcde096ed6c3 4776 libcap2_2.15-3.diff.gz 63c2ec76d2c29f4058e031c674cdfe5520c43563 17376 libcap2-dev_2.15-3_i386.deb bd2a3b719491467d48d7ca4131cd91513d29a14c 18204 libcap2-bin_2.15-3_i386.deb 5db420b776a786362795db88112a13ce010b958d 11006 libcap2_2.15-3_i386.deb Checksums-Sha256: 471afaf4f5a1586ff025ce48b358949522087a06e3a24c0bcb11c9ac4a4ade25 1168 libcap2_2.15-3.dsc 25eb5b6fc6fbec4e6103d1ec4814e34d5d03a43ba55db74d50ebfd33cdd39f6c 4776 libcap2_2.15-3.diff.gz 48a1bc9b4aca2a28b2cb9b8454971f743e39f9ad07e5f0042dc87059813667e2 17376 libcap2-dev_2.15-3_i386.deb ea290abb49c8dde9d133f64fedf3f014e4417b4abf398e76fa22918b48db36b2 18204 libcap2-bin_2.15-3_i386.deb db36f644b9f222b7e81a9319636da98efcce34a1d2a4c1d8d320ddc7a1cf2a82 11006 libcap2_2.15-3_i386.deb Files: 021fff3193f86b7310b23ed794d46b2c 1168 libs optional libcap2_2.15-3.dsc 00182710453750219035603c22bb3ec4 4776 libs optional libcap2_2.15-3.diff.gz 3761836a9e0292cf30f7f1c30787f5d0 17376 libdevel optional libcap2-dev_2.15-3_i386.deb 984aa3b9e1899f23901eafe7ac038229 18204 utils optional libcap2-bin_2.15-3_i386.deb c3da1b2574c2e46f9b58ad524b403d9b 11006 libs standard libcap2_2.15-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk32jMACgkQfY3dicTPjsOS/ACgkg+7mJvxuWcUP8G2FszhIhuO PVEAmgMR0ysKuwYBl6e81nXLk71MrErE =YXfg -END PGP SIGNATURE- Accepted: libcap2-bin_2.15-3_i386.deb to pool/main/libc/libcap2/libcap2-bin_2.15-3_i386.deb libcap2-dev_2.15-3_i386.deb to pool/main/libc/libcap2/libcap2-dev_2.15-3_i386.deb libcap2_2.15-3.diff.gz to pool/main/libc/libcap2/libcap2_2.15-3.diff.gz libcap2_2.15-3.dsc to pool/main/libc/libcap2/libcap2_2.15-3.dsc libcap2_2.15-3_i386.deb to pool/main/libc/libcap2/libcap2_2.15-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted turbogears 1.0.4.4-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 11:27:52 -0200 Source: turbogears Binary: python-turbogears Architecture: source all Version: 1.0.4.4-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Gustavo Noronha Silva [EMAIL PROTECTED] Description: python-turbogears - Python-based web framework Changes: turbogears (1.0.4.4-2) unstable; urgency=low . [ Sandro Tosi ] * debian/control - switch Vcs-Browser field to viewsvn . [ Gustavo Noronha Silva ] * Orphaning. Checksums-Sha1: 509b9812c51df48ed764cbb9ac3798d3e6cb0bd2 2175 turbogears_1.0.4.4-2.dsc 26e3c412ce460d38abf0e98c48c385212868b7c1 8967 turbogears_1.0.4.4-2.diff.gz cf49e36a77e830635379acc30ec0733514d1a2e3 1071022 python-turbogears_1.0.4.4-2_all.deb Checksums-Sha256: f3ef4fe5ec8d56ee47a447452fd3635b21c6959bfa6523262790ff7a97a27f95 2175 turbogears_1.0.4.4-2.dsc f9f9ffd4944e2430299e859b8e3a7af9e19d22f07e309e8491cc5da433951d13 8967 turbogears_1.0.4.4-2.diff.gz 7b59bfa6a1b2738f2690f58c65654c145cb4a29d6a3a4a27bc469bfabbcb7c94 1071022 python-turbogears_1.0.4.4-2_all.deb Files: aba7de3ab641966fcc709969041b41b4 2175 python optional turbogears_1.0.4.4-2.dsc 9e340a20e558608748e50610fbed06ff 8967 python optional turbogears_1.0.4.4-2.diff.gz 356320079e3a56c56e0e58ebc88306aa 1071022 python optional python-turbogears_1.0.4.4-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJJN9w1AAoJENIA6zCg+12m0oQIAKolKELEBmIZ4mJcx8YAkFT3 apIVv3qTuG1n/KYceDF4AcG/o6GXxIh1EQBqzA84VImk9B9DdLsbbEU9tzatdWqT gbJ+jOY9J+MK+BuXM1iORrhXneaOXlKu+yDz/j4WMryxzS0yY9/gGOpFaEz7m5UC ZUsrRPcKdgtSUzIQH3cNn+xrTHqURCYfz8Om4RXpwZ7wTY5s+ZKYDz8scTtWwUp3 32Cn+vQQ6Qj5jQyFQLzO0u+u4RP8HPrcEKk4QFmHa2g29/6N8QeQbkJsbwN0R9FI 7BSVt2p+QPMxXgy+30sjrvM7Ljm0f4L/dynosbkq40aD/WmKGhiJ5Uzz0I2hclo= =S3os -END PGP SIGNATURE- Accepted: python-turbogears_1.0.4.4-2_all.deb to pool/main/t/turbogears/python-turbogears_1.0.4.4-2_all.deb turbogears_1.0.4.4-2.diff.gz to pool/main/t/turbogears/turbogears_1.0.4.4-2.diff.gz turbogears_1.0.4.4-2.dsc to pool/main/t/turbogears/turbogears_1.0.4.4-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted turbojson 1.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 11:45:48 -0200 Source: turbojson Binary: python-turbojson Architecture: source all Version: 1.2-1 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Gustavo Noronha Silva [EMAIL PROTECTED] Description: python-turbojson - TurboGears template plugin that supports Json templates Changes: turbojson (1.2-1) unstable; urgency=low . [ Gustavo Noronha Silva ] * New upstream release * Orphaning the package * debian/control: - updated standards version, no changes . [ Sandro Tosi ] * debian/control - switch Vcs-Browser field to viewsvn Checksums-Sha1: 2de13f76cded1791061f01473afc821a5b92a4b2 1639 turbojson_1.2-1.dsc 2e3dd8894afee6b5ecbd4adda725b3e7d9f4eded 5810 turbojson_1.2.orig.tar.gz 585946d8b983b37aa297dcbce6a4544be63e7d05 2589 turbojson_1.2-1.diff.gz 19cc9a8908f0b729065fdf2e55f3902f46dd57dd 8256 python-turbojson_1.2-1_all.deb Checksums-Sha256: 55a2195081e63426dadae85bd7427234acc41e239ea9af2c3c660f75fb7c1f86 1639 turbojson_1.2-1.dsc 9fac312b2dd38a7f37d0ebc44fd42af91f694b82561e0ef43c8263e11451a9f0 5810 turbojson_1.2.orig.tar.gz 27da98b39424907a9ae55f84367fe222991686785d13abd82fc903b2986d158b 2589 turbojson_1.2-1.diff.gz a99f2051b503239f54db0b9a7e10d5354fe6c51af1d9b5f4e62e4e31206c34dc 8256 python-turbojson_1.2-1_all.deb Files: 3937be29ce87dc8ab5856ddabe35f394 1639 python optional turbojson_1.2-1.dsc 19ed791bf9871d16123292ab331ef5f2 5810 python optional turbojson_1.2.orig.tar.gz a852529f4d62a426c3c3e51ee1bbf822 2589 python optional turbojson_1.2-1.diff.gz 980b3eb673893c9e8b5810d6b4ba0f5e 8256 python optional python-turbojson_1.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJJN995AAoJENIA6zCg+12mxxsH/1DvJSdj/XI6Hc8o5Ydp9KTR ao6/4zFXo89uZh9cTDOA9yQfw12BIfo97gQm5RqleSJjkj3p9KcVEh8JPeGK8tHI Mz1s68fqFnw69wGGNct2Co5NjVDM0bsKO4B6qVuMEdQm7zFPWFOH8e61e8P+i8d8 6s+tp+zf6rexVmVix6o/a9LuJbUgwJdp1nTE3CbsKhR1xQB9vW67mj8ZMvEtPeKz HirL18oSPDa3wXBM3S5ZoX3FbEQX5KJJRV+dkZpSRQvyc/KtCxpGRnemj1oa/53R KFbJXTDaMnwT0V2fHNkLxJGbrYypUEJX7bYhBOEgSmuFbn+SSl6awr0JR0lCegc= =/Fkg -END PGP SIGNATURE- Accepted: python-turbojson_1.2-1_all.deb to pool/main/t/turbojson/python-turbojson_1.2-1_all.deb turbojson_1.2-1.diff.gz to pool/main/t/turbojson/turbojson_1.2-1.diff.gz turbojson_1.2-1.dsc to pool/main/t/turbojson/turbojson_1.2-1.dsc turbojson_1.2.orig.tar.gz to pool/main/t/turbojson/turbojson_1.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted turbokid 1.0.4-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 11:41:37 -0200 Source: turbokid Binary: python-turbokid Architecture: source all Version: 1.0.4-3 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Gustavo Noronha Silva [EMAIL PROTECTED] Description: python-turbokid - TurboGears template plugin that supports Kid templates Changes: turbokid (1.0.4-3) unstable; urgency=low . [ Sandro Tosi ] * debian/control - switch Vcs-Browser field to viewsvn . [ Gustavo Noronha Silva ] * Orphaning the package. Checksums-Sha1: c427a968b7e72431169a39db308df032c8e4a34d 1643 turbokid_1.0.4-3.dsc 44ad3b2d89b427e731474a399932240d796f1a4c 2893 turbokid_1.0.4-3.diff.gz 18a591b113295eabe4224a83554447db7f6c618e 7096 python-turbokid_1.0.4-3_all.deb Checksums-Sha256: e8af516cd97b8e232909392fcf9f7c1de3723a841c9621c06713dbdd01fa06ac 1643 turbokid_1.0.4-3.dsc 9d1c8147859bcab366aa175667d13c0165df7c85bf2bfa673c6b60f519c2d6d2 2893 turbokid_1.0.4-3.diff.gz 51eab3472b4dfba9118a16f721d9270587953ca001d4d4fbeabd9d6a77e02618 7096 python-turbokid_1.0.4-3_all.deb Files: 0541388e3daa58f56b55ca0373391fbd 1643 python optional turbokid_1.0.4-3.dsc 0b8e814c9bb2d03e9ba0c5e08617de06 2893 python optional turbokid_1.0.4-3.diff.gz 83955ea40dde747b7a98cc970965ca6d 7096 python optional python-turbokid_1.0.4-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJJN96KAAoJENIA6zCg+12mLqoH/0qIj8xbuFqPcNjN4opuNHVW CSlfvXSq64W3h6xfpCvr+glw1VdDcun9HSObSYUcpC7QDptZIN9yUfCFZEXcGJQ+ XYtaYRAgiFk+6XBuwoATVE0CRSBy3lSErGALQhOGvCtVsBgJcvlzfLw5Wo9IAe8D EiS5QJIzRSeAqz/bdBasDJSkD+PMOxPC2MfLpSDa0D+ZVRx1QqeZMFJlHrWtRkjL pviQi8c8of2Plnurdh7yRRDuWOQDl+WKE9HrtbgxzdcVLR5yyK9Q1WY/TqK9jDC8 rGb27Hd6KEN3z+CpkmeyAcfLiXBpQ2PX/7vdzTATK9+OCu+JUe00V3EecCg6E1g= =rdeM -END PGP SIGNATURE- Accepted: python-turbokid_1.0.4-3_all.deb to pool/main/t/turbokid/python-turbokid_1.0.4-3_all.deb turbokid_1.0.4-3.diff.gz to pool/main/t/turbokid/turbokid_1.0.4-3.diff.gz turbokid_1.0.4-3.dsc to pool/main/t/turbokid/turbokid_1.0.4-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libjgoodies-binding-java 2.0.6-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 14:44:38 +0100 Source: libjgoodies-binding-java Binary: libjgoodies-binding-java Architecture: source all Version: 2.0.6-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Torsten Werner [EMAIL PROTECTED] Description: libjgoodies-binding-java - Swing Data Binding Framework Changes: libjgoodies-binding-java (2.0.6-1) unstable; urgency=low . * New upstream release Checksums-Sha1: f1e0a42b813ca1a88a051e9ee2be6f9a9bfd8ec6 1442 libjgoodies-binding-java_2.0.6-1.dsc 555db09a2efd4a203690d1c14fd82c26e6166dad 272240 libjgoodies-binding-java_2.0.6.orig.tar.gz 87674de53a5792b331bc6343f671598bd93d5b73 2785 libjgoodies-binding-java_2.0.6-1.diff.gz 3edf63b39e859b4f414ff90032b4045bac8425ab 394560 libjgoodies-binding-java_2.0.6-1_all.deb Checksums-Sha256: 4320a07886495db99a7fa539b3a4b22904ff8b242f08ed1539fb895ddfa70300 1442 libjgoodies-binding-java_2.0.6-1.dsc 6f19ad9dd937679c3f446d660eff0efef753fcb73204a3a7607654d8f47df3b6 272240 libjgoodies-binding-java_2.0.6.orig.tar.gz 9dc45a584aec7a47740049a1546bfb2e46781529468db19c10b328d5b5521113 2785 libjgoodies-binding-java_2.0.6-1.diff.gz 1716c10a3d14495e079f7a33f0c2fab134a1727ea95a314a93ea3bec33dce99b 394560 libjgoodies-binding-java_2.0.6-1_all.deb Files: ccce5d9f279f883ebe62b943d4796706 1442 libs optional libjgoodies-binding-java_2.0.6-1.dsc b31688827f396264ad0a49ed1e464489 272240 libs optional libjgoodies-binding-java_2.0.6.orig.tar.gz 2032375a1d36e46a0fd4c47a8e9f39de 2785 libs optional libjgoodies-binding-java_2.0.6-1.diff.gz c69079055347e9d8fcecf9dbab5c3104 394560 libs optional libjgoodies-binding-java_2.0.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk34hEACgkQfY3dicTPjsOfvQCeNO93Cu0uJzzuw3UMPbfbpXST 5xQAnAuW6hn9lOOY/ZRtFFtdgWVQRS1Q =RqWo -END PGP SIGNATURE- Accepted: libjgoodies-binding-java_2.0.6-1.diff.gz to pool/main/libj/libjgoodies-binding-java/libjgoodies-binding-java_2.0.6-1.diff.gz libjgoodies-binding-java_2.0.6-1.dsc to pool/main/libj/libjgoodies-binding-java/libjgoodies-binding-java_2.0.6-1.dsc libjgoodies-binding-java_2.0.6-1_all.deb to pool/main/libj/libjgoodies-binding-java/libjgoodies-binding-java_2.0.6-1_all.deb libjgoodies-binding-java_2.0.6.orig.tar.gz to pool/main/libj/libjgoodies-binding-java/libjgoodies-binding-java_2.0.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libjoda-time-java 1.6-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 15:17:53 +0100 Source: libjoda-time-java Binary: libjoda-time-java Architecture: source all Version: 1.6-1 Distribution: experimental Urgency: low Maintainer: Debian Java Maintainers [EMAIL PROTECTED] Changed-By: Torsten Werner [EMAIL PROTECTED] Description: libjoda-time-java - Java date and time API Changes: libjoda-time-java (1.6-1) experimental; urgency=low . * New upstream release * Prepare package for extra timezone updates. * Bump up Standards-Version: 3.8.0 (no changes). * Do no longer quote the full text of the Apache license. Checksums-Sha1: ef9925a41a9fbdbef84ed931ba75c49b93f8d6bd 1368 libjoda-time-java_1.6-1.dsc 48c61e8db240b9de6de337d22c657d6b499e6b8b 820719 libjoda-time-java_1.6.orig.tar.gz 6ae6b5e58c88fd5ff3a213b2c76522cb640a7d9f 2018 libjoda-time-java_1.6-1.diff.gz ae099a9fe768995d0970ded8259327e270b9017d 459832 libjoda-time-java_1.6-1_all.deb Checksums-Sha256: df8d9b2c6ed6ec633cd985b98fc8be12fbbd4a686a951b1ee0ae958d932fb545 1368 libjoda-time-java_1.6-1.dsc 72a3ff360a3241deb35d1d9792f515cc65b815eac77ff43042cba1821b221399 820719 libjoda-time-java_1.6.orig.tar.gz c3b1f32864a0dc3336f20a5acd356ca981277d3b444812aa93eeead2b38150cb 2018 libjoda-time-java_1.6-1.diff.gz aac3e225d838df98d577b6844077e79a320c4e54d5c9e4ad48d18db57795e368 459832 libjoda-time-java_1.6-1_all.deb Files: e620db35dabf666c8c0d56261e2b3a9c 1368 libs optional libjoda-time-java_1.6-1.dsc ac56fb71e42937958c912c2f3cf268f7 820719 libs optional libjoda-time-java_1.6.orig.tar.gz fe1b12fa10f2331dfdab5f4ca484143b 2018 libs optional libjoda-time-java_1.6-1.diff.gz 4fb8d963011c4c3be671208364faf43d 459832 libs optional libjoda-time-java_1.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk35/gACgkQfY3dicTPjsOPUgCdHBpOwliWWnI8Rgrg2OvyD5Ic +x0AoIV2wWVskhTCGJAkFfcg6Kf96sIF =LeDg -END PGP SIGNATURE- Accepted: libjoda-time-java_1.6-1.diff.gz to pool/main/libj/libjoda-time-java/libjoda-time-java_1.6-1.diff.gz libjoda-time-java_1.6-1.dsc to pool/main/libj/libjoda-time-java/libjoda-time-java_1.6-1.dsc libjoda-time-java_1.6-1_all.deb to pool/main/libj/libjoda-time-java/libjoda-time-java_1.6-1_all.deb libjoda-time-java_1.6.orig.tar.gz to pool/main/libj/libjoda-time-java/libjoda-time-java_1.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bzr-svn 0.4.16-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 16:08:19 +0100 Source: bzr-svn Binary: bzr-svn Architecture: source i386 Version: 0.4.16-1 Distribution: experimental Urgency: low Maintainer: Debian Bazaar Maintainers [EMAIL PROTECTED] Changed-By: Jelmer Vernooij [EMAIL PROTECTED] Description: bzr-svn- Bazaar plugin providing Subversion integration Changes: bzr-svn (0.4.16-1) experimental; urgency=low . * New upstream release. Checksums-Sha1: fb0859cfff45c1c18d61082d75833257d03e5d96 1514 bzr-svn_0.4.16-1.dsc bceca241f38923b992fed962eb4b0f6a44a73905 223390 bzr-svn_0.4.16.orig.tar.gz 276bc4a70b021b9bf7f22916dbd514d107fe8b43 3592 bzr-svn_0.4.16-1.diff.gz 36505094262b48656b5a917d30894b1ca359d069 307710 bzr-svn_0.4.16-1_i386.deb Checksums-Sha256: 846f52d5806d1a06da21f61e8057742281dc57313e509476b9d5f55c40758179 1514 bzr-svn_0.4.16-1.dsc 8bb002ec0fb8fc19411ec9588d06e6e6275f3983f4ff7c7d2f0ceec5978f37c0 223390 bzr-svn_0.4.16.orig.tar.gz 34a10d2dfd60867de56eda2fda51777c0f02a29c13415a390d39e643cb5c27f2 3592 bzr-svn_0.4.16-1.diff.gz 9684e4f48b21a809c90b542da646a58aa50e7a2d29b8fe1261f322cd2a5e9768 307710 bzr-svn_0.4.16-1_i386.deb Files: eaed63a2363a02d0944b5f1c3a1787d2 1514 devel optional bzr-svn_0.4.16-1.dsc 1bea665d3320924e64babff93ca6a75d 223390 devel optional bzr-svn_0.4.16.orig.tar.gz 24be14845b546ab2c7e8727a43a36ae4 3592 devel optional bzr-svn_0.4.16-1.diff.gz 62ec65f8f1c1b048f8da46457cff4baf 307710 devel optional bzr-svn_0.4.16-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iJwEAQECAAYFAkk383cACgkQDLQl4QYPZuUQiQQAistu5vnRtx0o4cI7eKSAeLZ6 sDD5ru564zc6ibq5zOK5pPaIab8AtRvryhf1SiKC3xbK+uZo8+L0KnVuZD2NNv32 UyiDizA0D1Ng3B/T/GcU+YPYa+EhkVcO2IUrvEb5FuSvY7ggPdUcTVbiXuIQnK1b x6TeSXhgi6Yl7OMO4/0= =DRtg -END PGP SIGNATURE- Accepted: bzr-svn_0.4.16-1.diff.gz to pool/main/b/bzr-svn/bzr-svn_0.4.16-1.diff.gz bzr-svn_0.4.16-1.dsc to pool/main/b/bzr-svn/bzr-svn_0.4.16-1.dsc bzr-svn_0.4.16-1_i386.deb to pool/main/b/bzr-svn/bzr-svn_0.4.16-1_i386.deb bzr-svn_0.4.16.orig.tar.gz to pool/main/b/bzr-svn/bzr-svn_0.4.16.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted transmission 1.40-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 13:54:19 +0100 Source: transmission Binary: transmission transmission-common transmission-cli transmission-gtk transmission-daemon Architecture: source all amd64 Version: 1.40-2 Distribution: unstable Urgency: low Maintainer: Leo costela Antunes [EMAIL PROTECTED] Changed-By: Leo Costela [EMAIL PROTECTED] Description: transmission - lightweight BitTorrent client transmission-cli - lightweight BitTorrent client (command line interface) transmission-common - lightweight BitTorrent client (common files) transmission-daemon - lightweight BitTorrent client (daemon) transmission-gtk - lightweight BitTorrent client (graphical interface) Closes: 507766 Changes: transmission (1.40-2) unstable; urgency=low . * debian/transmission-daemon.postinst: add --group to adduser call and add workaround for the lack of the flag in 1.40-1 (closes: #507766) * debian/control: make transmission-cli recommend transmission-daemon, instead of depending * debian/transmission-daemon.init: add --retry to stop action to avoid race condition during install Checksums-Sha1: 61eaf83cc9ea07ca244321fb2f8ec92303e8fb40 1456 transmission_1.40-2.dsc c3386e25e3c8eaa7bb1675d9d198a0a8fda72a37 11872 transmission_1.40-2.diff.gz 04bdeb4ef2a82ecd349491ab6225516b78d145ff 846 transmission_1.40-2_all.deb 04fc9107607517acd605a7dbc1b36e0a518ae629 143974 transmission-common_1.40-2_all.deb af1ef24eb247788c7466cee16699fdc0acd639d6 209450 transmission-cli_1.40-2_amd64.deb b29c1aa1e7c8484a828cd93c31b11ed18ddb688c 596050 transmission-gtk_1.40-2_amd64.deb c6db98f243bd65efd83caeb699ea8cf867b10a96 417574 transmission-daemon_1.40-2_amd64.deb Checksums-Sha256: 2999bf9bee01f8e707f452722fe40e9569060d4ee43071a2b42d2fdab849f15d 1456 transmission_1.40-2.dsc d77b809d47c8f8cb540a40c741b00f7ac14d8848e79afc68d3d86d73147e7694 11872 transmission_1.40-2.diff.gz e6793fd853c529d4fafcdbfc21265913ba83ce2873ea52d2321252d6152c4b10 846 transmission_1.40-2_all.deb 7713253e15c08f42ba84e75fc937890bbfd9f2da9dcc1ef618903e52a8769b1d 143974 transmission-common_1.40-2_all.deb f9ba8d77c5177ff50b74ecdf2aac5ceb994f8a1c9a25c0fd1d5f518e68465c54 209450 transmission-cli_1.40-2_amd64.deb 93361d6ca129f41eace94baf1d2c4aa1335b9f1c1ab2c5ea505ad0562c44011e 596050 transmission-gtk_1.40-2_amd64.deb 441c4d92bcfbeaa09e4c611dbb9b6242e8f723ecb8f23f049ea130ea14fa6c85 417574 transmission-daemon_1.40-2_amd64.deb Files: 0c46931ca79f1b8f5e2f21da8239cd18 1456 net optional transmission_1.40-2.dsc ecbe260cf630af18d01a664cb1fb81fc 11872 net optional transmission_1.40-2.diff.gz e70b41a0c76c968006439889b80ab976 846 net optional transmission_1.40-2_all.deb 9dec635fc3eb444837370241235bd206 143974 net optional transmission-common_1.40-2_all.deb 04baf6bcfa3fd29086fb61c615645491 209450 net optional transmission-cli_1.40-2_amd64.deb 78b2a5f4b368332679b49fe6d8a0fa0d 596050 net optional transmission-gtk_1.40-2_amd64.deb b8608a2cd547142ae4358cf97518ce48 417574 net optional transmission-daemon_1.40-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk38rcACgkQImLTb3rflGb86gCeJLSbN0RrHbPgX5LkEbVPD1Ig NHoAn2K5IwDKHwnVetQuuFWIZxavQUTf =DQLT -END PGP SIGNATURE- Accepted: transmission-cli_1.40-2_amd64.deb to pool/main/t/transmission/transmission-cli_1.40-2_amd64.deb transmission-common_1.40-2_all.deb to pool/main/t/transmission/transmission-common_1.40-2_all.deb transmission-daemon_1.40-2_amd64.deb to pool/main/t/transmission/transmission-daemon_1.40-2_amd64.deb transmission-gtk_1.40-2_amd64.deb to pool/main/t/transmission/transmission-gtk_1.40-2_amd64.deb transmission_1.40-2.diff.gz to pool/main/t/transmission/transmission_1.40-2.diff.gz transmission_1.40-2.dsc to pool/main/t/transmission/transmission_1.40-2.dsc transmission_1.40-2_all.deb to pool/main/t/transmission/transmission_1.40-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mpd 0.14~beta2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 09:36:43 -0500 Source: mpd Binary: mpd Architecture: source amd64 Version: 0.14~beta2-1 Distribution: unstable Urgency: low Maintainer: Decklin Foster [EMAIL PROTECTED] Changed-By: Decklin Foster [EMAIL PROTECTED] Description: mpd- Music Player Daemon Changes: mpd (0.14~beta2-1) unstable; urgency=low . * New upstream release * Bump policy version to 3.8.0 * Update Homepage: field Checksums-Sha1: d8e7a5314f040376740c0cca4ff827652b45f97c 1458 mpd_0.14~beta2-1.dsc 5672757f076a4fc93dec84c181d1d7bbac2646e3 364870 mpd_0.14~beta2.orig.tar.gz 75b7324eb893132fbc1584244c58939f4b94bdd1 13289 mpd_0.14~beta2-1.diff.gz 4485c4c6e2daab874aac5ee8ae92cd5fd3465a0a 188232 mpd_0.14~beta2-1_amd64.deb Checksums-Sha256: 42affbaace3cbd6ee7b061bd8c578ed117d06e12b6efcee9679ff0cff22fe606 1458 mpd_0.14~beta2-1.dsc abeb69b3e56cce75f1fda9e0bc97c63f789fc5e6f3a1e6b58aa097a07b0d7249 364870 mpd_0.14~beta2.orig.tar.gz d4bb9e80a5d4bd26760699d5f587a7eae6693fbc873da0f0e1640f77b024eb22 13289 mpd_0.14~beta2-1.diff.gz 88a00e9ca020cba28506c8810365200cf9a89f6df53e097e55da4ab7faf27003 188232 mpd_0.14~beta2-1_amd64.deb Files: 60bd72c8548de143982a73fbe328dcca 1458 sound optional mpd_0.14~beta2-1.dsc 96695f62b14af0e63eee6e54e7e49e28 364870 sound optional mpd_0.14~beta2.orig.tar.gz ddf03ea38ddff094bd4b151c4f7d724a 13289 sound optional mpd_0.14~beta2-1.diff.gz a854cb848a4f18b2807b25291c149af7 188232 sound optional mpd_0.14~beta2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk37nkACgkQDwp/AdfC2mPRxACgm4mbu0z/beo8I0yzmSHBRpHn cfcAoI47auGjXxWBMBKJ7rdIej2ZI4TL =6akW -END PGP SIGNATURE- Accepted: mpd_0.14~beta2-1.diff.gz to pool/main/m/mpd/mpd_0.14~beta2-1.diff.gz mpd_0.14~beta2-1.dsc to pool/main/m/mpd/mpd_0.14~beta2-1.dsc mpd_0.14~beta2-1_amd64.deb to pool/main/m/mpd/mpd_0.14~beta2-1_amd64.deb mpd_0.14~beta2.orig.tar.gz to pool/main/m/mpd/mpd_0.14~beta2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted software-properties 0.70.debian-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 12:37:23 -0200 Source: software-properties Binary: python-software-properties software-properties-gtk software-properties-kde Architecture: source all Version: 0.70.debian-1 Distribution: experimental Urgency: low Maintainer: Gustavo Noronha Silva [EMAIL PROTECTED] Changed-By: Gustavo Noronha Silva [EMAIL PROTECTED] Description: python-software-properties - manage the repositories that you install software from software-properties-gtk - manage the repositories that you install software from software-properties-kde - manage the repositories that you install software from Changes: software-properties (0.70.debian-1) experimental; urgency=low . * New upstream release * debian/control.in: - added python-kde4 as a dependency for software-properties-kde, now that it is ported - upgraded to Standards-Version 3.8.0, with no changes - added Vcs headers * debian/copyright: - make it machine readable, using the standards defined in the Debian wiki * debian/software-properties-gtk.install: - no longer install help, since upstream no longer generates it, since it is outdated Checksums-Sha1: b27636e7127365a18372cf5d2f157a4022583985 1967 software-properties_0.70.debian-1.dsc ac8a32b2f9b6847e91ac9e7ca2f1b7e591cf41ba 1368600 software-properties_0.70.debian.orig.tar.gz b8a2f428679cdf5a4703d2e9fb331880f1b1e631 23323 software-properties_0.70.debian-1.diff.gz e2b6011fa26ccf014d4ac5dfaf101df0a264558e 31968 python-software-properties_0.70.debian-1_all.deb 09a037e319bb9e023fe272255c10ebda92df82f3 50786 software-properties-gtk_0.70.debian-1_all.deb d0b47c95175314fe0a8ad831f178c5e612a90c90 29990 software-properties-kde_0.70.debian-1_all.deb Checksums-Sha256: ea90c1999b80e6931832ef581e0d3468febcf5f3da57add8ca659f46858e1706 1967 software-properties_0.70.debian-1.dsc 19064fc2ccb99d5dd8ebc8f758136f6be8d768fd4d9b4343c4f4b8054a3c78c9 1368600 software-properties_0.70.debian.orig.tar.gz 410520c58676bc3861092ee589ee2c4cb132f4788a6e24aa1c6dd5afa50e536f 23323 software-properties_0.70.debian-1.diff.gz 452032465ac125048ed97681361ef11c134df2b0c2c11af492a3bcde8269f977 31968 python-software-properties_0.70.debian-1_all.deb e0bf48967fc3c20ed71042f9dcf57105e022c8b7982d8b1935b9dce02a939bdb 50786 software-properties-gtk_0.70.debian-1_all.deb d1f88580785a5ee8d0d89d7889959d97f90f489fc7cabddf55becf657a510609 29990 software-properties-kde_0.70.debian-1_all.deb Files: 5a60eff729e01097a7693a86d0055d84 1967 admin optional software-properties_0.70.debian-1.dsc 4a18262526721585ed41b31ea7022a83 1368600 admin optional software-properties_0.70.debian.orig.tar.gz 48d6faf426d6cf2e3f500a01d531c3ba 23323 admin optional software-properties_0.70.debian-1.diff.gz 21504aefd49cf57b34f97fb38ce81572 31968 admin optional python-software-properties_0.70.debian-1_all.deb a4bfff9a1236376e9ad3be70c926e9b2 50786 admin optional software-properties-gtk_0.70.debian-1_all.deb fbaa4be6bbbdf6d14ffefde686ff954d 29990 admin optional software-properties-kde_0.70.debian-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJJN+tTAAoJENIA6zCg+12mrLIIAJnhPoqV9ILdMCt9txi61CAx TEx8SDqj3v9nJ6dSPQRuxb25k9GTGbUexbDMM3gc5w4vWezozpof8Whvwk7zbKZy 74l2rk97GK5vmbQIXJRgz3bJGgtcaCjqu53jMfmAjVIyJkfQkLg5WEvajLQ8iQFT mZIqME84pAq1aZiLj82OlbPFKPESuDqvImcfn4hAl4HZeVhMRRHRgoI5UHek7K3m NKxiRmdThH4U7mH7ZjwS9owsDZUwEviLKvwgn9SvODraihKAzlqsAfHjfSn//A/1 9DHBINw9IDZLq0BN06Aj4wrD26ZYzO9Eo3e/yN2BHc9BF+qB7PzAbDz6/syirjs= =j4YZ -END PGP SIGNATURE- Accepted: python-software-properties_0.70.debian-1_all.deb to pool/main/s/software-properties/python-software-properties_0.70.debian-1_all.deb software-properties-gtk_0.70.debian-1_all.deb to pool/main/s/software-properties/software-properties-gtk_0.70.debian-1_all.deb software-properties-kde_0.70.debian-1_all.deb to pool/main/s/software-properties/software-properties-kde_0.70.debian-1_all.deb software-properties_0.70.debian-1.diff.gz to pool/main/s/software-properties/software-properties_0.70.debian-1.diff.gz software-properties_0.70.debian-1.dsc to pool/main/s/software-properties/software-properties_0.70.debian-1.dsc software-properties_0.70.debian.orig.tar.gz to pool/main/s/software-properties/software-properties_0.70.debian.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ess 5.3.10-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 09:25:16 -0600 Source: ess Binary: ess Architecture: source all Version: 5.3.10-2 Distribution: unstable Urgency: low Maintainer: ESS Debian Maintainers [EMAIL PROTECTED] Changed-By: Dirk Eddelbuettel [EMAIL PROTECTED] Description: ess- Emacs mode for statistical programming and data analysis Closes: 507510 Changes: ess (5.3.10-2) unstable; urgency=low . * Updated to SVN revision 4001 which addresses the bug report 'ess: fails setting up' when no R version is present (Closes: #507510) Checksums-Sha1: 8344227b251e7ba0e3d949b03eee246f5ca116ac 1156 ess_5.3.10-2.dsc f6d24264a4a89fcb589d08f236090edb3e6b17ee 52889 ess_5.3.10-2.diff.gz 18c96e2a154d028b7a5ca8e16637047c8f01a809 1460740 ess_5.3.10-2_all.deb Checksums-Sha256: 00fbcda633379c611d085a449e6d5981ee9b580d95b7d2d129522cc7240c2285 1156 ess_5.3.10-2.dsc e76e88ec91c2811710f8014fde6f3e697c16b811ff7c51c9dd65bd35604ccac9 52889 ess_5.3.10-2.diff.gz e785ecb90686e72c2ca1b5431da3cfd58f4bf7cd791d674678a49ef1a083ddc5 1460740 ess_5.3.10-2_all.deb Files: 289d6bb96777f5e76c319b28c9896967 1156 math optional ess_5.3.10-2.dsc 7c6866ae041857164c8db236e12cc4bd 52889 math optional ess_5.3.10-2.diff.gz 72b009e17038fb75e33e12d83645a527 1460740 math optional ess_5.3.10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJN/kaCZSR95Gw07cRAt/8AJ0W2BsRLzc9acOayvU496/mS2B2UgCfWjzZ q9cV+Ar3RNi4Us8VyTEyrg4= =0W+A -END PGP SIGNATURE- Accepted: ess_5.3.10-2.diff.gz to pool/main/e/ess/ess_5.3.10-2.diff.gz ess_5.3.10-2.dsc to pool/main/e/ess/ess_5.3.10-2.dsc ess_5.3.10-2_all.deb to pool/main/e/ess/ess_5.3.10-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted djvulibre 3.5.21-2 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 14 Nov 2008 10:34:44 +
Source: djvulibre
Binary: libdjvulibre-dev libdjvulibre21 libdjvulibre-text djvulibre-dbg
djvulibre-desktop djview3 djview djvuserve djvulibre-plugin djvulibre-bin
Architecture: source i386
Version: 3.5.21-2
Distribution: unstable
Urgency: low
Maintainer: Barak A. Pearlmutter [EMAIL PROTECTED]
Changed-By: Barak A. Pearlmutter [EMAIL PROTECTED]
Description:
djview - Transition package for djview to djview3
djview3- Viewer for the DjVu image format
djvulibre-bin - Utilities for the DjVu image format
djvulibre-dbg - Debug symbols for the DjVu image format
djvulibre-desktop - Desktop support for the DjVu image format
djvulibre-plugin - Browser plugin for the DjVu image format
djvuserve - CGI program for unbundling DjVu files on the fly
libdjvulibre-dev - Development files for the DjVu image format
libdjvulibre-text - Linguistic support files for libdjvulibre
libdjvulibre21 - Runtime support for the DjVu image format
Closes: 498456 505643 505644
Changes:
djvulibre (3.5.21-2) unstable; urgency=low
.
* Remove bashism ...{.,*}... from debian/rules (closes: #505644)
* Put djvulibre-dbg in section libdevel (closes: #498456)
* Formatting patch for c44.1 from Ubuntu (closes: #505643)
* Don't integrate 3.5.20-8+lenny0 (do no reopen #495979, #507503)
Checksums-Sha1:
25a20d1c148e40398962e19974ffa1e4a2b711a3 1413 djvulibre_3.5.21-2.dsc
4909c38ac47339ea6871e00827c5dcafb0f9c790 43729 djvulibre_3.5.21-2.diff.gz
af5782fa35e3d803f452a4aa166805ece039e9c8 1636674
libdjvulibre-dev_3.5.21-2_i386.deb
1d8618fa2cf9dd1a58f929387b8678ae342a1321 681772
libdjvulibre21_3.5.21-2_i386.deb
8edd360c3a1d2accffedb0f5a979411e5c8552a5 74558
libdjvulibre-text_3.5.21-2_i386.deb
698976acf0cfda67267d111d4ef34959d645d924 5831516
djvulibre-dbg_3.5.21-2_i386.deb
f8e3a48ee7e4c8ea22c453e5a9e8d64ada943b24 31940
djvulibre-desktop_3.5.21-2_i386.deb
50114a7a0bc76758df67d81311c53a93f8482814 516418 djview3_3.5.21-2_i386.deb
69a9aaa2d0a5c28c99093aa05aa73cc26ee55ceb 10376 djview_3.5.21-2_i386.deb
8ffdb5c3d900a4c018f100df8652529e89236b6f 33018 djvuserve_3.5.21-2_i386.deb
6be388356deb536fca812bac959e718b26cb0b85 35138
djvulibre-plugin_3.5.21-2_i386.deb
ef66b35e8aaeddf60a2dc8bfa0881208e9d75689 382694 djvulibre-bin_3.5.21-2_i386.deb
Checksums-Sha256:
51533a994d5b69692cf4b20d09ddcd208b87d61349b5d95caf957bf3b80d3283 1413
djvulibre_3.5.21-2.dsc
85221a145b95f3dc9f05b40607e6b6cb0046b70f4d84ea68f2158b8c8a4bee34 43729
djvulibre_3.5.21-2.diff.gz
aa531d33162d8956e1d71b3fc4fd9092cee646fc7e206593c66f1d660d3522dc 1636674
libdjvulibre-dev_3.5.21-2_i386.deb
2c9d53289d05cbf6b7ec812167948058ff09e97c1d9f293bad9aa446cce323f7 681772
libdjvulibre21_3.5.21-2_i386.deb
0af425ad8be31ad7200f101d9f9529376abfeecee68a9504007d1e40240b8da1 74558
libdjvulibre-text_3.5.21-2_i386.deb
19ca3ca6dd94556c93ea3dbb955e953c64e06f77c63e2b8a30425924e84fc411 5831516
djvulibre-dbg_3.5.21-2_i386.deb
513c3703b700b48668a8d3793ce38bf2c5293c5994fef14809a2a2b8ff4780a9 31940
djvulibre-desktop_3.5.21-2_i386.deb
6074f89771f5b05c8b63a78557489f9b3a5b07a791d47a67a503cb47b6bbd4ea 516418
djview3_3.5.21-2_i386.deb
d5b43089ff8451d42bc4327e1bf6d13eb217aba6ad260cfbb4ef0d17948b9451 10376
djview_3.5.21-2_i386.deb
5f3e037822f3fb6a9feb603a0e108b6ed0ce7f0c6e9d16c58a11cd23a15c981b 33018
djvuserve_3.5.21-2_i386.deb
dce50b293421b3e4f8f93f9cd363c2bd56fe668bc2fcbca2cd33c9e97cf62f09 35138
djvulibre-plugin_3.5.21-2_i386.deb
f9ed367313b5c0116e65ae2550afe8cf295d9c4b44bb0efd32c68b95c04ca94d 382694
djvulibre-bin_3.5.21-2_i386.deb
Files:
4061fdc8d22a9f829ba9f537b844cff2 1413 web optional djvulibre_3.5.21-2.dsc
bb6637ac8e292062016a806cb41923cb 43729 web optional djvulibre_3.5.21-2.diff.gz
edf639e1b0f9268fbb3e52f26bacbb9b 1636674 libdevel optional
libdjvulibre-dev_3.5.21-2_i386.deb
b4ac7c54752f3c707312ced433d0c0db 681772 libs optional
libdjvulibre21_3.5.21-2_i386.deb
99c74bff3837efe78d1837120a3d5226 74558 libs optional
libdjvulibre-text_3.5.21-2_i386.deb
9a7e3c5ded9121b6dd25dbc8100f3d9f 5831516 libdevel extra
djvulibre-dbg_3.5.21-2_i386.deb
31ca70d3b721ef7635f5bdf7a56ec04d 31940 libs optional
djvulibre-desktop_3.5.21-2_i386.deb
5ed642bdcd768d878e8f5bb99223f77e 516418 graphics optional
djview3_3.5.21-2_i386.deb
35150d7fc42cf9ef7fc113cdd9276947 10376 graphics optional
djview_3.5.21-2_i386.deb
1e6e1fb1abe9413b2d382c16cfce8b88 33018 web optional djvuserve_3.5.21-2_i386.deb
4b8fcbff8a4737ec1b9d1d7b38982803 35138 web optional
djvulibre-plugin_3.5.21-2_i386.deb
b5afd9f0fcae81f0f469df90b6369294 382694 graphics optional
djvulibre-bin_3.5.21-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJNPm8Lz4Gnv7CP7IRAkobAJ0dyGUlxj7OW58zzzRlTXyo9Q7HSgCfbMBx
ryAGNcy5GVucIx7ln8IUwV0=
=a3TB
-END PGP SIGNATURE-
Accepted:
djview3_3.5.21-2_i386.deb
to pool/main/d/djvulibre/djview3_3.5.21-2_i386.deb
djview_3.5.21-2_i386.deb
to
Accepted libkrb5-ruby 0.7-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 Oct 2008 15:26:13 -0700 Source: libkrb5-ruby Binary: libkrb5-ruby libkrb5-ruby1.8 libkrb5-ruby1.9 libkrb5-ruby-doc Architecture: source all i386 Version: 0.7-1 Distribution: unstable Urgency: low Maintainer: Ryan Niebur [EMAIL PROTECTED] Changed-By: Ryan Niebur [EMAIL PROTECTED] Description: libkrb5-ruby - Basic Kerberos ruby binding libkrb5-ruby-doc - Documentation for libkrb5-ruby libkrb5-ruby1.8 - Basic Kerberos ruby binding (Ruby 1.8) libkrb5-ruby1.9 - Basic Kerberos ruby binding (Ruby 1.9) Closes: 502029 Changes: libkrb5-ruby (0.7-1) unstable; urgency=low . * Initial release (Closes: #502029) Checksums-Sha1: e31a5a0fb2879a1529689cb0c8c22bf353bb8e93 1235 libkrb5-ruby_0.7-1.dsc 21dabba3e0c5c9eb343cb6ba1aa2159b9c93ac90 15477 libkrb5-ruby_0.7.orig.tar.gz 9d63c25a80bf32e1ebf5ad4b058db16530e52cc5 1550 libkrb5-ruby_0.7-1.diff.gz 0b53c1a42a05fa7d010aec3e2e96f962c4eb6985 2358 libkrb5-ruby_0.7-1_all.deb e267669fb2416e720a07480f95f99ce0ff4308b8 2318 libkrb5-ruby-doc_0.7-1_all.deb d7da3b40db785aafc2f916a8af63260db86875d1 8520 libkrb5-ruby1.8_0.7-1_i386.deb ae606bc7cf7901a1a87ea1badb7a31bb18b1e7ce 8544 libkrb5-ruby1.9_0.7-1_i386.deb Checksums-Sha256: 67f5d691cebd2691f1e603d9dfda6ba36b34022a8b184861d6d290e50f85a88c 1235 libkrb5-ruby_0.7-1.dsc 72d36a32bc198534890ccaec47227dec6faa35f8742ed3d154af402fb5ea8abd 15477 libkrb5-ruby_0.7.orig.tar.gz d17eaf24a3d5e52982b61aa098657acb31da01e320bbcc7092146de9f07f0a5a 1550 libkrb5-ruby_0.7-1.diff.gz 39bb36b5c4cdb2bd9608ba54e916cb6ab60af81efa432da43ed80adcaab9e1f2 2358 libkrb5-ruby_0.7-1_all.deb 50ad3fb8cdbb0d995b3d13b0dc7d4d9f20de46ee8e076cb3264c8d0a9e09c489 2318 libkrb5-ruby-doc_0.7-1_all.deb 3e89e968a214cb6dfeb25bf67fae9d4c3296ae1ca078d185493925796b40863e 8520 libkrb5-ruby1.8_0.7-1_i386.deb 223c4685d58e752bec88da7b2768efff9005ffca990c8709184468c7c5da2b4a 8544 libkrb5-ruby1.9_0.7-1_i386.deb Files: 198a5036bb33802aead63a7fd406736e 1235 libs extra libkrb5-ruby_0.7-1.dsc ca5541ddeefc00c234205b0012a9653c 15477 libs extra libkrb5-ruby_0.7.orig.tar.gz 8fedb488fc2905a2f1c2b44e2f455960 1550 libs extra libkrb5-ruby_0.7-1.diff.gz dc77358e56cc112d7df5862e5267e697 2358 libs extra libkrb5-ruby_0.7-1_all.deb 13ca675c92e395cbdbddb902ec8fddc5 2318 doc extra libkrb5-ruby-doc_0.7-1_all.deb c6aa4e3fca1522eccb367ec157e87b3a 8520 libs extra libkrb5-ruby1.8_0.7-1_i386.deb 97af78ec0a1489fe55c9e5782713094e 8544 libs extra libkrb5-ruby1.9_0.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJCAm22hliNwI7P08RAq9oAJ4r9BpkmK88bEIp97k1INm+KyjzwACdEDvq iu5MAv161HU+sLIXUZWKJnU= =Mam3 -END PGP SIGNATURE- Accepted: libkrb5-ruby-doc_0.7-1_all.deb to pool/main/libk/libkrb5-ruby/libkrb5-ruby-doc_0.7-1_all.deb libkrb5-ruby1.8_0.7-1_i386.deb to pool/main/libk/libkrb5-ruby/libkrb5-ruby1.8_0.7-1_i386.deb libkrb5-ruby1.9_0.7-1_i386.deb to pool/main/libk/libkrb5-ruby/libkrb5-ruby1.9_0.7-1_i386.deb libkrb5-ruby_0.7-1.diff.gz to pool/main/libk/libkrb5-ruby/libkrb5-ruby_0.7-1.diff.gz libkrb5-ruby_0.7-1.dsc to pool/main/libk/libkrb5-ruby/libkrb5-ruby_0.7-1.dsc libkrb5-ruby_0.7-1_all.deb to pool/main/libk/libkrb5-ruby/libkrb5-ruby_0.7-1_all.deb libkrb5-ruby_0.7.orig.tar.gz to pool/main/libk/libkrb5-ruby/libkrb5-ruby_0.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted amtterm 1.0-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 28 Oct 2008 09:55:26 +0100 Source: amtterm Binary: amtterm gamt Architecture: source i386 Version: 1.0-2 Distribution: unstable Urgency: low Maintainer: Reinhard Tartler [EMAIL PROTECTED] Changed-By: Reinhard Tartler [EMAIL PROTECTED] Description: amtterm- Serial-over-lan (sol) client for Intel AMT, console version gamt - Serial-over-lan (sol) client for Intel AMT, gtk version Closes: 448208 Changes: amtterm (1.0-2) unstable; urgency=low . [ Franklin Piat ] * Fix debian/patch copyright * Drop patch 10_destdir.dpatch. * Improve configuration options. * Drop Homepage field (ftp folder). * Cleanup sample files . [ Reinhard Tartler ] * Further cleanups in debian/rules * move git branch to collab-maint repository * Taking over package on Franklin's wish. He agrees to stay as Co-Maintainer! * convert dpatches to quilt * added patch by Michael Gernoth to fix the enter key in some BIOS implementations * split package in amtterm (with little dependencies) and gamt (which is more heavyweight and depends on various GTK libraries) * weaken package dependency on libsoap-lite-perl to recommends. . [ Michael Gernoth ] * add patch for BIOS over SOL . amtterm (1.0-1) unstable; urgency=low . * Initial release (Closes: #448208). * Adjusted the Variables.mk to fix $DESTDIR problems. * adapt example in amt-howto to Debian. * Fix lib64 detection bug Checksums-Sha1: e93b8a1e1cc06ab692e9cd74986c5f10c9e8d218 1320 amtterm_1.0-2.dsc 8d7deffc139711b1c73da3040ab663ccc85493fd 35768 amtterm_1.0.orig.tar.gz 1406802c62999e9d72c5afa90d7c13bb64c2ac30 5150 amtterm_1.0-2.diff.gz a9e53edc7009af84d3950141d5ae869d280d6080 17868 amtterm_1.0-2_i386.deb 2691daa5dab6e66a70c64aa9c75f627fbe4afab7 19994 gamt_1.0-2_i386.deb Checksums-Sha256: d399e6250dd3dbb001dfb44149b0a18a5e9f050bee2c30420531e9f79d9e71e2 1320 amtterm_1.0-2.dsc 53fea4636c9e9e6cf589644b6dd090f949a6fc281ed03a8032bdfb01a5025443 35768 amtterm_1.0.orig.tar.gz a8d336d38a87f0534c3b0d1f0d0bf6e1dc30d80eaf7cf918300825082c0024d4 5150 amtterm_1.0-2.diff.gz ca3d95d3c157f82b13cb089180cafc0f7d23c0dff2f44f454b3a62cc3513f765 17868 amtterm_1.0-2_i386.deb 850f18d9d468e66c63cb231a453f75a0ef7436ab404ee46a4156102506a7d81d 19994 gamt_1.0-2_i386.deb Files: 3b19252ce1f16e8fed94dc32ee5edefd 1320 net extra amtterm_1.0-2.dsc d39d02baae01d22084ffd47837e90d3b 35768 net extra amtterm_1.0.orig.tar.gz 36385e253e3d5e79628c979e10c0ce3c 5150 net extra amtterm_1.0-2.diff.gz 5ad9fda9cee0b8a55cc87adce951a211 17868 net extra amtterm_1.0-2_i386.deb 8ae7f0f4d232f47740b5ca39df528ea6 19994 net extra gamt_1.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Debian Powered! iJwEAQECAAYFAkkH/icACgkQ78RAoABp8o9HmgQAhgclJSij4t0+OT4OMn9N6rZT 7bOndMIzRhBEKz//buyPH8u7g7gx+HyPuK+4HSGsKzG/Bu6enPOiKzkd/MzLRjB8 rX4ilQ4ogu5Nu3HhglSNiFs3mM/bJ7jUJBequD+xyIcuO9pMzWEntJlB72t5/lML kl1HPd+5Ubjx5AHFX2k= =Ml7q -END PGP SIGNATURE- Accepted: amtterm_1.0-2.diff.gz to pool/main/a/amtterm/amtterm_1.0-2.diff.gz amtterm_1.0-2.dsc to pool/main/a/amtterm/amtterm_1.0-2.dsc amtterm_1.0-2_i386.deb to pool/main/a/amtterm/amtterm_1.0-2_i386.deb amtterm_1.0.orig.tar.gz to pool/main/a/amtterm/amtterm_1.0.orig.tar.gz gamt_1.0-2_i386.deb to pool/main/a/amtterm/gamt_1.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libvirt 0.4.6-7 (source all powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 17:50:45 +0100 Source: libvirt Binary: libvirt-bin libvirt0 libvirt0-dbg libvirt-doc libvirt-dev python-libvirt Architecture: source all powerpc Version: 0.4.6-7 Distribution: unstable Urgency: low Maintainer: Debian Libvirt Maintainers [EMAIL PROTECTED] Changed-By: Guido Günther [EMAIL PROTECTED] Description: libvirt-bin - the programs for the libvirt library libvirt-dev - development files for the libvirt library libvirt-doc - documentation for the libvirt library libvirt0 - library for interfacing with different virtualization systems libvirt0-dbg - library for interfacing with different virtualization systems python-libvirt - libvirt Python bindings Closes: 499720 507547 507553 507578 507677 Changes: libvirt (0.4.6-7) unstable; urgency=low . * [ea12bd9] create /var/run/libvirt fixes /var/run on tmpfs (Closes: #507578) * [97e5706] also look for /usr/bin/kvm (Closes: #507547) * [311b4c1] increase initial qemu monitor read timeout (Closes: #499720) * [fbe4e00] open qemu monitor log O_APPEND instead of O_TRUNC * [f8ce017] raise error on invalid volume format * [40edcf8] rotate qemu monitor logs (Closes: #507553) - thanks to Harald Staub * [46ea43a] fix segfault on missing volume format (Closes: #507677) - thanks to Daniel Veillard * [ee377f3] bump shlibs version to 0.4.6 * [504d55d] depend on logrotate Checksums-Sha1: 6f64bb9fc084354411266107288f9d3c3ff28d12 1593 libvirt_0.4.6-7.dsc 9ed7ca5bd65dc2a40ebe29a8c4d88a69a63bd39a 16312 libvirt_0.4.6-7.diff.gz 015d6b36a8b2c3dec4c71c901fca138932eca632 548026 libvirt-doc_0.4.6-7_all.deb 6225648a7a921c7d64bb35d29e3aa4796c3c27ba 236904 libvirt-bin_0.4.6-7_powerpc.deb 689be7ca652f401067edf322f750c3fa85604ee7 307666 libvirt0_0.4.6-7_powerpc.deb b6f48fc9052b429eabd8ef158c46447c23b2dd45 554338 libvirt0-dbg_0.4.6-7_powerpc.deb 906830bf987b0b3944807a42b345db5b353e62ea 385978 libvirt-dev_0.4.6-7_powerpc.deb 09b54ae0231f101d23858f90eb6bd507e6ad879f 151500 python-libvirt_0.4.6-7_powerpc.deb Checksums-Sha256: b334383d761fcda1296e9d28b0559abdce58bcf133df2e3a364c6dbfca33e7a4 1593 libvirt_0.4.6-7.dsc e5a1cf470ac51b2caab0a50714d80bfada285ac8a1e7f184286400f3f77a93b6 16312 libvirt_0.4.6-7.diff.gz 8e084949b8d6a1f9768e638f02f67f95b7b954d539949180e700e9846a4d8eae 548026 libvirt-doc_0.4.6-7_all.deb 6701263d7ce08012b18416e27745aa18edcca6bfea3474d5905d198b44f7d235 236904 libvirt-bin_0.4.6-7_powerpc.deb b9cff65e3f798fc282757a48b88430e9bd66dd2ea4a42a960d224bfcb4f2ae78 307666 libvirt0_0.4.6-7_powerpc.deb b7063218da44d10ca9bcbec10bc204b8f9fed20cbb27765c4b93814dbe1f459b 554338 libvirt0-dbg_0.4.6-7_powerpc.deb 97410e6bab137cb20399fe3f2b750f3ff9e84ab3015d246b121e6f8ea184934f 385978 libvirt-dev_0.4.6-7_powerpc.deb e105fa3b819e35876deaec0d0451520413dfbb9538574c837a799cd4f9063022 151500 python-libvirt_0.4.6-7_powerpc.deb Files: 12fc013705ca4f40c5a9df3418c8168c 1593 libs optional libvirt_0.4.6-7.dsc e3fa7c0376a14d542a2b61701f46f7a5 16312 libs optional libvirt_0.4.6-7.diff.gz f087fc94c99bd1d4ecca4e9df3fdc8d7 548026 doc optional libvirt-doc_0.4.6-7_all.deb ad899e5a96f4f92645822b803a3aed38 236904 admin optional libvirt-bin_0.4.6-7_powerpc.deb 8a8576cd128eff7c6fe349d331a2f57d 307666 libs optional libvirt0_0.4.6-7_powerpc.deb 8f655be9698bd02145854c38d719dec5 554338 libs extra libvirt0-dbg_0.4.6-7_powerpc.deb c46654f5ada27f652e4fa133ee3c0b0e 385978 libdevel optional libvirt-dev_0.4.6-7_powerpc.deb 712f876b9b3064c35bb505c37944dc68 151500 python optional python-libvirt_0.4.6-7_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJOA80n88szT8+ZCYRAsHZAJ9JoJtyy/QBRH0gjl4BDAL3XTrntQCfanns fp9snvj82lC9CV+PkfaiK9U= =FALw -END PGP SIGNATURE- Accepted: libvirt-bin_0.4.6-7_powerpc.deb to pool/main/libv/libvirt/libvirt-bin_0.4.6-7_powerpc.deb libvirt-dev_0.4.6-7_powerpc.deb to pool/main/libv/libvirt/libvirt-dev_0.4.6-7_powerpc.deb libvirt-doc_0.4.6-7_all.deb to pool/main/libv/libvirt/libvirt-doc_0.4.6-7_all.deb libvirt0-dbg_0.4.6-7_powerpc.deb to pool/main/libv/libvirt/libvirt0-dbg_0.4.6-7_powerpc.deb libvirt0_0.4.6-7_powerpc.deb to pool/main/libv/libvirt/libvirt0_0.4.6-7_powerpc.deb libvirt_0.4.6-7.diff.gz to pool/main/libv/libvirt/libvirt_0.4.6-7.diff.gz libvirt_0.4.6-7.dsc to pool/main/libv/libvirt/libvirt_0.4.6-7.dsc python-libvirt_0.4.6-7_powerpc.deb to pool/main/libv/libvirt/python-libvirt_0.4.6-7_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cairo 1.6.4-7 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 18:20:31 +0100 Source: cairo Binary: libcairo2-dev libcairo2 libcairo2-dbg libcairo2-doc libcairo-directfb2-udeb libcairo-directfb2 libcairo-directfb2-dev Architecture: source all amd64 Version: 1.6.4-7 Distribution: unstable Urgency: low Maintainer: Dave Beckett [EMAIL PROTECTED] Changed-By: Sebastian Dröge [EMAIL PROTECTED] Description: libcairo-directfb2 - The Cairo 2D vector graphics library DirectFB build (dummy packag libcairo-directfb2-dev - Development files for Cairo graphics library DirectFB build (dumm libcairo-directfb2-udeb - The Cairo 2D vector graphics library DirectFB build (udeb) libcairo2 - The Cairo 2D vector graphics library libcairo2-dbg - The Cairo 2D vector graphics library (debugging symbols) libcairo2-dev - Development files for the Cairo 2D graphics library libcairo2-doc - Documentation for the Cairo Multi-platform 2D graphics library Closes: 495620 Changes: cairo (1.6.4-7) unstable; urgency=low . * ACK NMU, thanks Joss. * debian/patches/03_buggy-repeat.dpatch: + Patch from the Mozilla team to work around a bug in some buggy X video drivers that cause incorrect image rendering (Closes: #495620 and many duplicates). Checksums-Sha1: d82fa36903586e5340c46c0123556a9fce8b8a4a 1481 cairo_1.6.4-7.dsc 5bbc7ba66c544234f12ab2884c24d72879e4fb63 23967 cairo_1.6.4-7.diff.gz 8746718339cf67688349e30770922a46ca875384 470880 libcairo2-doc_1.6.4-7_all.deb d9e0b57d9bdfa3ae1e8b97ecf8ed8d5def499423 649114 libcairo2-dev_1.6.4-7_amd64.deb 8e46a5811e4526be70b0860429d99ddc0f23cd86 558514 libcairo2_1.6.4-7_amd64.deb baf67433eef849ad1692d3ce035b1d351286ea21 880304 libcairo2-dbg_1.6.4-7_amd64.deb 2504c34e9b0211485761abb6b98808315b6ae4ae 160426 libcairo-directfb2-udeb_1.6.4-7_amd64.udeb 1b784f1e0fc2b289073e3ac62b6ac2087f8231f6 334618 libcairo-directfb2_1.6.4-7_amd64.deb 4fa9a46f115a41a528203b6cc684a44f682c0187 334844 libcairo-directfb2-dev_1.6.4-7_amd64.deb Checksums-Sha256: 807ab8189244e39780324dceb2798adc3ef5c7b3404cd39a94ce139aa3d8791e 1481 cairo_1.6.4-7.dsc f4659ce893c84c21e6ebfcd9c6167cb23f25647e0f8c373419fb72c738ef336c 23967 cairo_1.6.4-7.diff.gz 6c3c97ce0b1348dd7441ec49c7bcdc9bd2d86014e9cc8b99fb2d30f997c2a15d 470880 libcairo2-doc_1.6.4-7_all.deb 96e5710a4b2aca315c277d535a546f6028b00f9e78172b89b1e46feec072c2e1 649114 libcairo2-dev_1.6.4-7_amd64.deb 830fe126c7c8f44ab2d2745430cb4cb35d0ff09b0f90f4e73962a93335d6029b 558514 libcairo2_1.6.4-7_amd64.deb eaff9dffa32852a57bf122b181f54f8f096e4d5a8fb25a6f4c481d1629118390 880304 libcairo2-dbg_1.6.4-7_amd64.deb c89b950aaa0ed05281d0775afd9090d61f8f9dca042a1269ed5deb3bc99b48c6 160426 libcairo-directfb2-udeb_1.6.4-7_amd64.udeb c3c3c3312d4c23e39a4d0649ea291c8aa6222e81fc2c2d48a63b5852dd40ff7f 334618 libcairo-directfb2_1.6.4-7_amd64.deb f4d9a097290500d494234019221c71e6e78ccab31131ff18deb7ababb86999ba 334844 libcairo-directfb2-dev_1.6.4-7_amd64.deb Files: d92f696c0ef22aa5b9892226c224249d 1481 libs optional cairo_1.6.4-7.dsc 9f7e6b1b0b0cad9e4adabf9b5ac01af4 23967 libs optional cairo_1.6.4-7.diff.gz a8bf8b3dace5f27e4b0a825ce70c3225 470880 doc optional libcairo2-doc_1.6.4-7_all.deb 9a7693977370d958d2e59580a0e76c02 649114 libdevel optional libcairo2-dev_1.6.4-7_amd64.deb 89d335f860608369a1f9e97821de8d23 558514 libs optional libcairo2_1.6.4-7_amd64.deb b13f5ca0e2b2e13d25a0b7c68bd967e2 880304 libdevel extra libcairo2-dbg_1.6.4-7_amd64.deb 596b88d210c2b6ad72eaf44b1925c49d 160426 debian-installer optional libcairo-directfb2-udeb_1.6.4-7_amd64.udeb 0df63f10a4d1b4030cae3fb54c6d623c 334618 libs optional libcairo-directfb2_1.6.4-7_amd64.deb 05d3bfe5c4322f718c8004b1529bb405 334844 libdevel optional libcairo-directfb2-dev_1.6.4-7_amd64.deb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk4E6IACgkQBsBdh1vkHyFjPwCeKLOVBV4c9sc8x/dD8g2ohdL1 5/YAn1SsR/p/M74vY6mYbh5aNLS68wNY =OXLj -END PGP SIGNATURE- Accepted: cairo_1.6.4-7.diff.gz to pool/main/c/cairo/cairo_1.6.4-7.diff.gz cairo_1.6.4-7.dsc to pool/main/c/cairo/cairo_1.6.4-7.dsc libcairo-directfb2-dev_1.6.4-7_amd64.deb to pool/main/c/cairo/libcairo-directfb2-dev_1.6.4-7_amd64.deb libcairo-directfb2-udeb_1.6.4-7_amd64.udeb to pool/main/c/cairo/libcairo-directfb2-udeb_1.6.4-7_amd64.udeb libcairo-directfb2_1.6.4-7_amd64.deb to pool/main/c/cairo/libcairo-directfb2_1.6.4-7_amd64.deb libcairo2-dbg_1.6.4-7_amd64.deb to pool/main/c/cairo/libcairo2-dbg_1.6.4-7_amd64.deb libcairo2-dev_1.6.4-7_amd64.deb to pool/main/c/cairo/libcairo2-dev_1.6.4-7_amd64.deb libcairo2-doc_1.6.4-7_all.deb to pool/main/c/cairo/libcairo2-doc_1.6.4-7_all.deb libcairo2_1.6.4-7_amd64.deb to pool/main/c/cairo/libcairo2_1.6.4-7_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-django-dmigrations 0.3.1+svn22-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 20 Nov 2008 22:54:00 + Source: python-django-dmigrations Binary: python-django-dmigrations Architecture: source all Version: 0.3.1+svn22-1 Distribution: unstable Urgency: low Maintainer: Chris Lamb [EMAIL PROTECTED] Changed-By: Chris Lamb [EMAIL PROTECTED] Description: python-django-dmigrations - Database migration tool for Django projects Closes: 506310 Changes: python-django-dmigrations (0.3.1+svn22-1) unstable; urgency=low . * Initial release. (Closes: #506310) Checksums-Sha1: a8b957f8852fd30ac9aa1173c47437b7cc3f4971 1352 python-django-dmigrations_0.3.1+svn22-1.dsc 1a7a86939ac6b0b354f7178d209ed7160ffc9930 20484 python-django-dmigrations_0.3.1+svn22.orig.tar.gz 69c35d0cfac20af99b64f76774cc86b9256ba5fa 2447 python-django-dmigrations_0.3.1+svn22-1.diff.gz aac5ea1e5ffa58a27b1dd59895e3047f1d9e08e3 22858 python-django-dmigrations_0.3.1+svn22-1_all.deb Checksums-Sha256: 4f0bf5a7c5225767669e50c09a42736905543f8f5f598dadaebd3773f3a45348 1352 python-django-dmigrations_0.3.1+svn22-1.dsc 06dd1ff1027161c72c18b87f166355320e8cb28be9c03a5031906449d03edf51 20484 python-django-dmigrations_0.3.1+svn22.orig.tar.gz 4312136fb87e3b79c57294ec77aa6d52596f9eae4f52eac4f74fa55a925e 2447 python-django-dmigrations_0.3.1+svn22-1.diff.gz 581305ebef35ae620543f8a9c9a3830d5c9b36750a4423194ad74a1376f79b8d 22858 python-django-dmigrations_0.3.1+svn22-1_all.deb Files: 4c42f7ff59d65b3b5a474d349536334c 1352 python optional python-django-dmigrations_0.3.1+svn22-1.dsc f79d074510d2489b1de4b3ee61744732 20484 python optional python-django-dmigrations_0.3.1+svn22.orig.tar.gz 3a1681748c7c8b9f0635108a92eddced 2447 python optional python-django-dmigrations_0.3.1+svn22-1.diff.gz 0904c60204f971e9ec427d0f0d82b00a 22858 python optional python-django-dmigrations_0.3.1+svn22-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkl/QkACgkQ5/8uW2NPmiDqZgCeOWlh04myq6xJGHv8y/WBBnNv brcAn12aNlTveTj/BauTayOtqHUV+rAB =Ui8Y -END PGP SIGNATURE- Accepted: python-django-dmigrations_0.3.1+svn22-1.diff.gz to pool/main/p/python-django-dmigrations/python-django-dmigrations_0.3.1+svn22-1.diff.gz python-django-dmigrations_0.3.1+svn22-1.dsc to pool/main/p/python-django-dmigrations/python-django-dmigrations_0.3.1+svn22-1.dsc python-django-dmigrations_0.3.1+svn22-1_all.deb to pool/main/p/python-django-dmigrations/python-django-dmigrations_0.3.1+svn22-1_all.deb python-django-dmigrations_0.3.1+svn22.orig.tar.gz to pool/main/p/python-django-dmigrations/python-django-dmigrations_0.3.1+svn22.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted agsync 0.2-pre-10 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Thu, 04 Dec 2008 12:02:43 -0500
Source: agsync
Binary: agsync-dev agsync
Architecture: source i386
Version: 0.2-pre-10
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group [EMAIL PROTECTED]
Changed-By: Barry deFreese [EMAIL PROTECTED]
Description:
agsync - Synchronization mediator for AvantGo and Pocket PC
agsync-dev - Development files for AvantGo and Pocket PC synchronization
Closes: 465639
Changes:
agsync (0.2-pre-10) unstable; urgency=low
.
* QA upload.
+ Set maintainer to Debian QA Group [EMAIL PROTECTED].
* Remove dependency on libglib2.0-dev. (Closes: #465639)
* Make clean not ignore errors.
* Add ${misc:Depends}.
* ${Source-Version} - ${binary:Version} on agsync-dev.
* Add copyright holders.
* Bump Standards Version to 3.8.0.
Checksums-Sha1:
ade2de4fe0586a110d7c5c7b45b8cc8c9b26fbeb 1069 agsync_0.2-pre-10.dsc
fdbae37f89d6d27bed95c7c88fc7d74e0d0ba66b 308829 agsync_0.2-pre-10.diff.gz
0676220e3456ad109db269bd7ac3499bc1bcf456 76618 agsync-dev_0.2-pre-10_i386.deb
e1fce3e84893a076fc3985290ae3ec94ff5474bb 69050 agsync_0.2-pre-10_i386.deb
Checksums-Sha256:
23e8126df7b9788f6697b815a245b693ecd158ec9871c380102ca995b2d494e5 1069
agsync_0.2-pre-10.dsc
7cad3dd691c88c35ae7adc13725186ab0b58f5bc33a51f8b4dfcc38f9500bd45 308829
agsync_0.2-pre-10.diff.gz
fa369850e19f13f5b9283c858a107b337b637b98bc5e95c30721dc1c29817b54 76618
agsync-dev_0.2-pre-10_i386.deb
683e4e5ac9cefaf3e7f78ff1cbbd254497268d742fa78c07b0a1dfac44b75ee0 69050
agsync_0.2-pre-10_i386.deb
Files:
5c225e36216e0463a69d17113a3c33c7 1069 libs optional agsync_0.2-pre-10.dsc
791462dafae5df6edf95cc531734eeeb 308829 libs optional agsync_0.2-pre-10.diff.gz
a7442285ee0c636e02da26e26544ed3a 76618 libdevel optional
agsync-dev_0.2-pre-10_i386.deb
3264da7c11819b9424a8dc0d107e3c69 69050 libs optional agsync_0.2-pre-10_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkk4FCoACgkQ5ItltUs5T35D9QCghcwEsXbs6W0NLEv1hXZ+WUgz
H/gAniAsmnko7V0rEEUbjPxzOHC8aqoN
=rD3U
-END PGP SIGNATURE-
Accepted:
agsync-dev_0.2-pre-10_i386.deb
to pool/main/a/agsync/agsync-dev_0.2-pre-10_i386.deb
agsync_0.2-pre-10.diff.gz
to pool/main/a/agsync/agsync_0.2-pre-10.diff.gz
agsync_0.2-pre-10.dsc
to pool/main/a/agsync/agsync_0.2-pre-10.dsc
agsync_0.2-pre-10_i386.deb
to pool/main/a/agsync/agsync_0.2-pre-10_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sugar-hulahop 0.4.8~dfsg-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Dec 2008 17:56:13 +0100 Source: sugar-hulahop Binary: python-hulahop Architecture: source amd64 Version: 0.4.8~dfsg-2 Distribution: unstable Urgency: low Maintainer: Debian OLPC [EMAIL PROTECTED] Changed-By: Jonas Smedegaard [EMAIL PROTECTED] Description: python-hulahop - Sugar graphical shell - gecko-based web engine Closes: 505459 Changes: sugar-hulahop (0.4.8~dfsg-2) unstable; urgency=low . * Add patch 0001 to fix pointer conversion. This closes: bug#505459, thanks to dann frazier. Checksums-Sha1: 25a6a33185fb3b5ca16646b4572ba3ca1076f609 1534 sugar-hulahop_0.4.8~dfsg-2.dsc 2b15c6e72af96ff5337271fe7b71b1dc2909c0d0 15004 sugar-hulahop_0.4.8~dfsg-2.diff.gz 262e9bf410fe172f98bf0e6a9493e8abd37a2075 221318 python-hulahop_0.4.8~dfsg-2_amd64.deb Checksums-Sha256: d12ed6dc8f3fa760f0ef52af4bea2e68ae22e1d8c273ac33148fdc6cb8b1c05a 1534 sugar-hulahop_0.4.8~dfsg-2.dsc 3c59af8108d35eca682208841a25d66cd6c64fd000daecf6d7864a689510e453 15004 sugar-hulahop_0.4.8~dfsg-2.diff.gz 3d9820ae2961042fbd9ef8a48454ae03d67ac3e7deea33e69e28c5857388cd50 221318 python-hulahop_0.4.8~dfsg-2_amd64.deb Files: 42d74b0676416ea674e68bde6eb165e4 1534 python optional sugar-hulahop_0.4.8~dfsg-2.dsc 01f78e61ca40e85a99615993ab2930f4 15004 python optional sugar-hulahop_0.4.8~dfsg-2.diff.gz fcd1b295f6350081eeff01be32d2b251 221318 python optional python-hulahop_0.4.8~dfsg-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkk4Eu0ACgkQn7DbMsAkQLh+xACfZAinqSE06DSNEHi2P3d7VybO /MkAnRqxwM9MvEzEPXoF7y8n91oUqBU6 =DVzR -END PGP SIGNATURE- Accepted: python-hulahop_0.4.8~dfsg-2_amd64.deb to pool/main/s/sugar-hulahop/python-hulahop_0.4.8~dfsg-2_amd64.deb sugar-hulahop_0.4.8~dfsg-2.diff.gz to pool/main/s/sugar-hulahop/sugar-hulahop_0.4.8~dfsg-2.diff.gz sugar-hulahop_0.4.8~dfsg-2.dsc to pool/main/s/sugar-hulahop/sugar-hulahop_0.4.8~dfsg-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
