Re: Chao ban ve may bay
Toi can mua ve may bay di BomBay An Do xin vui long bao gia dum. Ve khu hoi.
Re: dpkg-sig support wanted?
On Thu, Nov 24, 2005 at 07:17:06PM +0100, Goswin von Brederlow wrote: That's easy: you trust the Packages file to be correct when using apt, and it's not verified at all by per-package signatures. In what way trust and how does that change anything? At best you can prevent a newer version of a package to appear in the Packages file by compromising it. You can't subvert a package itself. But you can already ship yesterdays Release.gpg, Release and Packages file to a user and thereby prevent any updates. On the other hand, without package signatures ftp-master adds a vulnerability. You can hack into it, replace debs, recreate the Packages, Release and Release.gpg file and thereby infect users. With signed debs that could still be detected by every user in apt-get. Only if every user is in a position to verify signatures from each Debian developer individually, which is completely unrealistic. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Bug#283231: I have a patch to allow sudo-ldap
Quoting Paul LeoNerd Evans [EMAIL PROTECTED]: I'm not too familiar with creating a source package that can create multiple binary packages, but I have a local modification of the sudo source package which creates a sudo-ldap binary package. This is built using LDAP support. If you want I can provide this package, which I have tested on three of my ix86-based machines. It only does very minor changes - replacing some occurances of sudo with sudo-ldap, and changing the ./configure line in the build options. Perhaps someone with more experience could integrate this into the main source package..? Could you send the patch, and I'll see if I can make a REAL patch the sudo maintainer can use... -- Khaddafi Iran president critical South Africa kibo Ft. Meade bomb attack domestic disruption NSA Peking Saddam Hussein counter-intelligence Cuba [See http://www.aclu.org/echelonwatch/index.html for more about this] [Or http://www.europarl.eu.int/tempcom/echelon/pdf/rapport_echelon_en.pdf] If neither of these works, try http://www.aclu.org and search for echelon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#340428: octave2.9 - lists mailing list as uploader in changelog
* Bastian Blank [EMAIL PROTECTED] [2005-11-24 23:45]: On Thu, Nov 24, 2005 at 10:48:39PM +0100, Rafael Laboissiere wrote: Yes, I have been doing things wrongly in the past, but this is not the case anymore. The Changed-By fields are correct now. See, for instance, my last upload: http://lists.debian.org/debian-devel-changes/2005/11/msg01728.html [upload of octave2.9_2.9.4-7] | Maintainer: Debian/IA64 Build Daemon [EMAIL PROTECTED] | Changed-By: Debian Octave Group [EMAIL PROTECTED] Could you please explain to me why having Changed-By as a mailing list in this case (a binary NMU done by an autobuilder) is problematic? You may have good reasons for thinking Change-By should list a real person , but I fail to understand it. Notice that I am not religious about this ML versus person issue in the debian/changelog entry. If the majority of developers think we should do one way or the other, I will comply with the decision and do the necessary changes at the DOG (the Debian Octave Group, in case you did not yet get the acronym). I would like just to understand the rationale, though. -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Wed, Nov 23, 2005 at 05:34:41PM +0100, Jeroen van Wolffelaar wrote: In the archive, 525 out of 283283 .deb's are dpkg-sig'd (0.19%). There are 8 distinct keys used for those 525 .deb's, seven of which correspond to DD's[1]. Slightly off the topic, but does this mean the archive contains .debs not build by Debian developers? Shouldn't sponsors be recompiling packages from non-DDs before upload? Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
* Hamish Moffatt [Fri, 25 Nov 2005 20:34:02 +1100]: On Wed, Nov 23, 2005 at 05:34:41PM +0100, Jeroen van Wolffelaar wrote: In the archive, 525 out of 283283 .deb's are dpkg-sig'd (0.19%). There are 8 distinct keys used for those 525 .deb's, seven of which correspond to DD's[1]. Slightly off the topic, but does this mean the archive contains .debs not build by Debian developers? Shouldn't sponsors be recompiling packages from non-DDs before upload? I was suspicious too, but it was later checked on irc that all keys actually belonged to a DD. (One of them was not in public keyservers, AIUI, and Jeroen assumed it was not a DD, or something similar.) Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org A lie can go round the world before the truth has got its boots on. -- Terry Pratchett -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#340428: octave2.9 - lists mailing list as uploader in changelog
On Thu, Nov 24, 2005 at 10:36:41PM +0100, Thiemo Seufer wrote: I can see arguments against it, but none that make it an RC bug. Policy violations are RC by definition. Actually, no; policy violations are RC by *default*, but the definition of what's release-critical for a release is set by the release team with input from the developer community. I'm fairly certain that we're shipping packages in sarge that have maintainer fields pointing at people who have orphaned the packages in question; if it wasn't true at the time of the sarge release, it will certainly be true of sarge by the time etch releases. If we can survive this, I don't think that putting a mailing list address in a changelog (wrong though I think it is) would be grounds for delaying the release or removing the package from the release (the definition of RC). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Ropa Intima de Alta Calidad en CR
Si deseas desinscribirte de esta lista, envia un correo a [EMAIL PROTECTED] solicitandolo. Gracias
Re: dpkg-sig support wanted?
Hi, Anthony Towns wrote: The problem is that using gzip and ar is complicated, which adds possibilities for errors. You might find yourself not putting the deb together again and getting false signature mismatches, or worse, you might find yourself only verifying part of the .deb, and having dpkg actually use parts of the .deb that haven't been authenticated under the false conviction that you're actually safe. With md5sum foo.deb you know you've authenticated everything. Which is also a disadvantage in some cases. I could see a case for extending .deb files (say, with additional translations for the description and templates, thus removing the need for the maintainer to reupload new packages when new translations are ready). I think that it should be fairly easy to implement something that can verify parts of .deb files and check whether the authenticated parts together form a complete and consistent package on their own. This thread, however, is not about a technical problem, so I would propose a sauna meeting. IF this means we can switch the effort to a detached signature that is more powerful than a .changes file (or we are allowed to have multiple signatures in a .changes file), That is already possible with gnupg, just not well-documented; I'm not entirely sure what interesting breakage would occur if one were to upload a changes file with multiple signatures. and also that the .changes file will be stored in the archives along with the .debs, As it turns out, that's probably not feasible per se -- it likely implies too much inode usage, and slack space. And is probably pointless. If you don't trust the Debian infrastructure, you are free to get the source (which is signed by the maintainer) and build the package yourself. where dpkg would simply refuse per user-set policy any non-signed deb or any deb without a specific signature... I'm sorry, but you're back to the snakeoil use for deb sigs. Expecting a signature by a random Debian developer to mean something is not reasonable. That's why there can be multiple signatures. There would be one from the maintainer/buildd, a few from the Debian archive (for example, you could add one sig for officially in Debian unstable, one for migrated to testing and one for in a stable release) and if the idea of adding description/template translations later on catches on, also some from the translators/translation system. Simon signature.asc Description: OpenPGP digital signature
Re: How to deal with dependencies/conflics on third party packages
Hello Steve, Steve Langasek [EMAIL PROTECTED] wrote: On Sun, Nov 20, 2005 at 11:50:55PM +, Joerg Sommer wrote: Steve Langasek [EMAIL PROTECTED] wrote: Does not work with j2re1.3 means you should be depending on what it *does* work with, not trying to conflict with (unrelated) packages that don't satisfy the dependency. All packages in Debian they provide java-virtual-machine work with bootchart-view. That includes jamvm and gij-3.3? Yes, jamvm and gij-4.0. But all alternative JVMs do only work with svg output and only Sun's JVM support png. This is the reason, why I don't want restrict the dependencies upon the JVMs in Debian. I don't understand this explanation at all. The bug report is about a failure due to class version mismatches; what does this have to do with svg vs. png? I don't want block JVMs they are not in Debian, because the Debian ones are not fully functional. So I don't want to write kaffe | sablevm | jamvm | gij in the Dependens line, but than I get the problem of allowing old JVMs or JVMs I don't know. The problem here is that bootchart-view depends on '| java-virtual-machine', which does not satisfy its runtime needs. Depend on something more appropriate; possibly even j2re1.4. I can not find this package The implication was that j2re1.4 would be a virtual package, provided by those packages which implement the 1.4 spec. But of course, there's also a *real* j2re1.4 package, not available in Debian but buildable using java-package. The main point is not that j2re1.4 is the correct name to include in this list (it may be, but I don't know that for sure); the point is that java-virtual-machine is *incorrect*, because j-v-m only ensures you a lowest common denominator feature set, and that's obviously not sufficient in this case. What would be a better way? I think you get the same problem, if you force to use a C99 compiler. gcc may provide this, but other c compilers not. What would you write in the Dependens line if you need a c99. And the problem for me with java is, all JVMs in Java do not work fully with my package. Only the JVM from SUN gives you the whole functionality. Bye, Jörg. -- Alles, wovor wir Angst haben müssen, ist die Angst selbst. (Fraklin D. Roosevelt) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to deal with dependencies/conflics on third party packages
Hello sean, sean finney [EMAIL PROTECTED] wrote: hi joerg, On Sun, Nov 20, 2005 at 10:23:58AM +, Joerg Sommer wrote: I've got a bug report (#336527) my package bootchart-view do not work with j2re1.3. But j2re1.3 is not in Debian. Can I set a conflict upon a packages that is not in Debian? But if it do not work with j2re1.3 it should more than ever not work with older version. But I would assume older version have different packages names. So I must add a list of packages names (j2re1.3 j2re1.2 j2re1.1), because I can not use the version clause (j2re1.3 ( 1.3)). So what should I do? i'd consider simply adding a note to README.Debian/NEWS.Debian about said problem, and being done with it altogether. maybe leave the bug open at wishlist+wontfix for reference too, i guess. I would chose this way. I think that is the best one. Should I really decrease the level to wishlist? Is normal also alright for an wontfix bug? Bye, Jörg. -- Alles Gute wächst im Dunklen, bis es stark genug ist, ans Tageslicht zu kommen. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
Wouter Verhelst [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 06:51:24PM +0100, Goswin von Brederlow wrote: Wouter Verhelst [EMAIL PROTECTED] writes: I personally see the packages in unstable as something good for end-users who want to use it, or understand how the system works; but for Debian's purposes, it's not optimal. So non cabal members should look at a different sbuild and then magically figure out where and how the secret one differs? What is the point in looking at sbuild if it isn't THE sbuild? It's in Debian, and it's easy to use and understand. If it doesn't diverge too far from the sbuild actually on svn.cyberhqz.com, it's also good enough to give you a working setup for non-debian systems. IOW, it should be close enough to the actual thing to be useful for the general public, but cannot be close enough to the actual thing to be useful for official build daemons. Except it isn't working. Since a long time it wasn't able to build zsh, zsh-beta, bash3 for some unknown reason. It just deadlocks. Now its worse since the debian sbuild won't interact nicely with the wanna-build/buildd anymore due to interface changes and the binNMU feature. So now the sid sbuild only works standalone. That is a turn for the worse. Last year the aim was to get the buildd sbuild and debian sbuild back in sync and it pains me to see Ryan silently diferting it further and further instead of aiding that goal. That's one way to look at it. The other way would be to say that Ryan has recently been actively working on improving the code in the wanna-build SVN, and that the people maintaining the sbuild package in Debian (Roger?) haven't been paying too much attention to their upstream, likely because they didn't see the link on buildd.debian.org--a link which I, admittedly, had missed out on at first too, because it used to point to cvs.linux-m68k.org. There is indeed still a wanna-build CVS repository over there, but it's been effectively unmaintained for as long as I can remember. It should also be noted that Ryan, as appropriate for an Open Source developer, is happy to review and (provided he doesn't have any objections) apply any patches to sbuild or other things, too, as I've been able to witness first-hand myself in the past. I wasn't looking at it as upstream and debian maintainer but more like a native package with co-maintainers. But yours is a valid point. It just pains me that Debian does not include all the software to build Debian. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
Michael Banck [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 06:44:42PM +0100, Goswin von Brederlow wrote: Michael Banck [EMAIL PROTECTED] writes: On Wed, Nov 23, 2005 at 03:50:11PM +0100, Goswin von Brederlow wrote: If you NEED to do a manual binNMU it is probably best to use sbuild (the cvs, not deb) Patches for the Debian package are welcome, of course. Michael Do you know about http://svn.cyberhqz.com/svn/wanna-build/ Was that a question? I stated in the mail you replied to that wanna-build is now maintained in svn. Sorry, my bad. Still, I don't have time to look at it myself right now, so if somebody wants to send a patch, fine, otherwise, we will get to it eventually. Unless the release team and/or ftp-masters think this kind of new binNMU style should be restricted to the buildds (does the old style still work?). No. Michael MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
Michael Banck [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 06:51:24PM +0100, Goswin von Brederlow wrote: Wouter Verhelst [EMAIL PROTECTED] writes: They were, originally. Ryan's been very active on it since, and it's diverged a bit from the code you're maintaining. Then he should send patches and bug reports to the debian package. When the sbuild package got orphaned two years ago or so, I asked Ryan whether he would like to maintain it, and he said he was not interested. Which is totally fine for me and about everybody else. This split between the user/developer visible sbuild and the secret actual buildd is just not in the spirit of Debian. 1. Please drop the `secret' immediately. Unless you really want to call http://www.debian.org/devel/buildd `secret'. That your mail got resent with the this subject to debian-devel-announce is already stressing it *a lot*, IMHO. The subject and initial mail is not about sbuild being secret but about the overall change for Debian. I think that one is justified. Nothing to do with this subthread. As for http://www.debian.org/devel/buildd: $ grep sbuild http://www.debian.org/devel/buildd emwanna-build/em and calls emsbuild/em to build the packages. dta href=http://packages.debian.org/sbuild;sbuild/a/dt This nice public page only points to the nice public sbuild debian package. There is no link to the actual sbuild used on buildds. Further the links for wanna-build and buildd (which probably indirectly included sbuild) are broken: http://m68k.debian.org/buildd/getting.html -- connection refused Did you by chance mean the wanna-build svn link on http://buildd.debian.org/? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
Adeodato =?utf-8?B?U2ltw7M=?= [EMAIL PROTECTED] writes: * Goswin von Brederlow [Thu, 24 Nov 2005 18:51:24 +0100]: Hi, Wouter Verhelst [EMAIL PROTECTED] writes: They were, originally. Ryan's been very active on it since, and it's diverged a bit from the code you're maintaining. Then he should send patches and bug reports to the debian package. This split between the user/developer visible sbuild and the secret actual buildd is just not in the spirit of Debian. I believe this is wrong. In words of one of the sbuild package co-maintainers, the Debian package is the fork, while the sbuild in wanna-build is upstream [1]. And upstreams are not required forward patches to their respective Debian maintainers, are they?; they just make new versions publicly available, as already happens here. [1] http://lists.debian.org/debian-devel/2005/11/msg01463.html Cheers, I'm sorry for that. I didn't see sbuild as an upstream + maintainer package but as a debian package. Developed by Debian people for Debian. Aparently that was a misconception on my part. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Anthony Towns aj@azure.humbug.org.au writes: On Thu, Nov 24, 2005 at 06:28:04PM +0100, Florian Weimer wrote: If you just want to check hashes, you should just use changes files. If you _actually_ want to check hashes, and this isn't just a thought experiment, working out a usable way to deliver .changes for whatever purpose you've got in mind would be a good idea. (Again though, I don't see a point to them, beyond reverification of the archive in the event of an exploit. Of course, maybe that's what you want to do...) We have a perfectly useable and trivial way to deliver the hashes, which is the intresting part of the changes file for security. It is the signature in the deb. For comparison: Why do we have a signature in dsc files? From your arguments that signature is completly useless since changes files already provide all that is needed. We still sign dsc files because it is just that much easier to apt-get source foo and verify it. And that is a good thing. Why are you so set in stone against allowing the same for debs? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Steve Langasek [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 07:17:06PM +0100, Goswin von Brederlow wrote: That's easy: you trust the Packages file to be correct when using apt, and it's not verified at all by per-package signatures. In what way trust and how does that change anything? At best you can prevent a newer version of a package to appear in the Packages file by compromising it. You can't subvert a package itself. But you can already ship yesterdays Release.gpg, Release and Packages file to a user and thereby prevent any updates. On the other hand, without package signatures ftp-master adds a vulnerability. You can hack into it, replace debs, recreate the Packages, Release and Release.gpg file and thereby infect users. With signed debs that could still be detected by every user in apt-get. Only if every user is in a position to verify signatures from each Debian developer individually, which is completely unrealistic. Up to a point you can trust the keyring. As much as you can trust any DD signature. You try to argue that signatures are not absolutely trustworthy but that is nothing new. Nothing you can do will change that. What you fail to see (or say) is that all the security Debian already has is weak in exactly the same way. The difference to signed debs is the transparency and triviality to check. Even if that check has to use a 5 hop trust path to some DD you never met. Also for !i386 !ppc basicaly all packages are autobuild and will be signed by a handfull of people. You can go and meet them easily enough. Further, with signed debs, you could only allow installation of debs from people you trust and recompile all the rest after a source audit. If you are that paranoid. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
On Fri, Nov 25, 2005 at 02:38:32PM +0100, Goswin von Brederlow wrote: Michael Banck [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 06:51:24PM +0100, Goswin von Brederlow wrote: Wouter Verhelst [EMAIL PROTECTED] writes: They were, originally. Ryan's been very active on it since, and it's diverged a bit from the code you're maintaining. Then he should send patches and bug reports to the debian package. When the sbuild package got orphaned two years ago or so, I asked Ryan whether he would like to maintain it, and he said he was not interested. Which is totally fine for me and about everybody else. This split between the user/developer visible sbuild and the secret actual buildd is just not in the spirit of Debian. 1. Please drop the `secret' immediately. Unless you really want to call http://www.debian.org/devel/buildd `secret'. That your mail got resent with the this subject to debian-devel-announce is already stressing it *a lot*, IMHO. The subject and initial mail is not about sbuild being secret but about the overall change for Debian. I think that one is justified. Nothing to do with this subthread. Right, these are two different things. However, the binNMU change is mostly/only useful for the release managers and buildd admins, so I fail to see why not having documented/announced it less than a week after its implementation should imply it was done in `secret', as those people are busy with the next library transition. To make this clear, I totally welcome your post documenting the new binNMU features while the authors have been too busy to do so for now. And the existance of the wanna-build/buildd/sbuild packages is not a secret, either. As for http://www.debian.org/devel/buildd: $ grep sbuild http://www.debian.org/devel/buildd emwanna-build/em and calls emsbuild/em to build the packages. dta href=http://packages.debian.org/sbuild;sbuild/a/dt This nice public page only points to the nice public sbuild debian package. There is no link to the actual sbuild used on buildds. Further the links for wanna-build and buildd (which probably indirectly included sbuild) are broken: http://m68k.debian.org/buildd/getting.html -- connection refused The documentation should get fixed, then. Did you by chance mean the wanna-build svn link on http://buildd.debian.org/? So it is documented there as well, good. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Anthony Towns aj@azure.humbug.org.au writes: On Thu, Nov 24, 2005 at 07:47:58PM +0100, Goswin von Brederlow wrote: Anthony Towns aj@azure.humbug.org.au writes: On Wed, Nov 23, 2005 at 09:18:40PM +0100, Goswin von Brederlow wrote: Use 1: I have this deb in my apt-move mirror and I want to know if it was compromised on yesterdays breakin Boot a clean system with debian keyring and check all deb signatures. Find some don't pass because they were signed with keys that have been removed from the keyring. Those I remove and refetch from a clean source again. False negatives are no big deal. 99% of the debs will verify leaving only a managable amount of wokr behind. The clean source that's signed by the same key that you can't verify? If I can't find any verifiable source then the package can't be trusted and can be removed till that is changed. Still much better than having 100% untrustworthy packages. Ah, I see the light. Signatures are useless because packages have no signatures. That's a transitional problem, yes. In this case it's a severe one; since there are up to 150GBs worth of .debs. It's a problem that could be solved if it were worthwhile, but it's not worthwhile since .changes already do everything deb sigs could do without any transition issues, and it's not something that can be simply ignored. Cheers, aj By the way, this is trivial to work around: 1) archive the Release.gpg, Release and Packages file from today 2) only allow signed debs from now on From then on all debs can be verified. I say the transition can be simply ignored (for now). The problem will fix itself in due time when signed debs become more popular and debsign automatically adds them. At some point in the future the majority of debs will be signed and then a transition can be force by scheduling a binNMU for any remaining deb. But first there must be an official debs may be signed before anyone can think about a debs MUST be signed. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Henrique de Moraes Holschuh [EMAIL PROTECTED] writes: On Thu, 24 Nov 2005, Anthony Towns wrote: On Thu, Nov 24, 2005 at 07:39:57AM +0100, Marc Haber wrote: Uh, packages not uploaded to the official Debian archive can do whatever they want. It would, however, be convenient to be able to upload a package to Debian and to be able to use the same package for different things. As far as dpkg-sign's concerned, can't you already do that by building the package, uploading it to debian, then running dpkg-sign? At worst you'd have to run dpkg-genchanges again before uploading to your other suite, afaics. You're correct. And he is also wrong. That would result in debs with the same name and version but different md5sums. Something that easily confuses apt-get and people. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
On Fri, Nov 25, 2005 at 02:03:12PM +0100, Goswin von Brederlow wrote: Wouter Verhelst [EMAIL PROTECTED] writes: It's in Debian, and it's easy to use and understand. If it doesn't diverge too far from the sbuild actually on svn.cyberhqz.com, it's also good enough to give you a working setup for non-debian systems. IOW, it should be close enough to the actual thing to be useful for the general public, but cannot be close enough to the actual thing to be useful for official build daemons. Except it isn't working. Since a long time it wasn't able to build zsh, zsh-beta, bash3 for some unknown reason. It just deadlocks. I think there's a fix for that in svn, not sure though. Now its worse since the debian sbuild won't interact nicely with the wanna-build/buildd anymore due to interface changes and the binNMU feature. So now the sid sbuild only works standalone. That is a turn for the worse. That's only true at this very moment. Resync with svn, done. [...] It just pains me that Debian does not include all the software to build Debian. Sure it does. It just doesn't include the software that Debian uses to automatically build packages, but that's not the same thing. After all, you can build packages in an automated fashion using, e.g., pbuilder; and people do actually do this all the time (where else would I have gotten those FTBFS bugs on doc-linux-nl from? That's an arch:all package). -- .../ -/ ---/ .--./ / .--/ .-/ .../ -/ ../ -./ --./ / -.--/ ---/ ..-/ .-./ / -/ ../ --/ ./ / .--/ ../ -/ / / -../ ./ -.-./ ---/ -../ ../ -./ --./ / --/ -.--/ / .../ ../ --./ -./ .-/ -/ ..-/ .-./ ./ .-.-.-/ / --/ ---/ .-./ .../ ./ / ../ .../ / ---/ ..-/ -/ -../ .-/ -/ ./ -../ / -/ ./ -.-./ / -./ ---/ .-../ ---/ --./ -.--/ / .-/ -./ -.--/ .--/ .-/ -.--/ .-.-.-/ / ...-.-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Simon Richter [EMAIL PROTECTED] writes: IF this means we can switch the effort to a detached signature that is more powerful than a .changes file (or we are allowed to have multiple signatures in a .changes file), That is already possible with gnupg, just not well-documented; I'm not entirely sure what interesting breakage would occur if one were to upload a changes file with multiple signatures. It gives a parse error and the DAK rejects the file. where dpkg would simply refuse per user-set policy any non-signed deb or any deb without a specific signature... I'm sorry, but you're back to the snakeoil use for deb sigs. Expecting a signature by a random Debian developer to mean something is not reasonable. A signature in the deb by a random developer is as trustworthy as the changes file and you already trust that. So we are going from snakeoil to snakoil. No harm done. That's why there can be multiple signatures. There would be one from the maintainer/buildd, a few from the Debian archive (for example, you could add one sig for officially in Debian unstable, one for migrated to testing and one for in a stable release) and if the idea of adding description/template translations later on catches on, also some from the translators/translation system. Although that would alter the packages md5sum and even alter a package while still being in a distribution (the unstable deb would suddenly gain a signature). It would be a big change to allow this. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: There must be bug. But where?
Daniel Leidert [EMAIL PROTECTED] writes: Am Donnerstag, den 24.11.2005, 19:53 +0100 schrieb Goswin von Brederlow: An incoming queue for reprepo is a ~100 lines shell script to check the changes file signature and include the files in reprepro. Probably less if you rewrite it in perl. Yes. But that is something, which needs to be written. debarchiver exists and works. Or better: it normally works. Regards, Daniel Which reminds me that I wanted to send that shell script as whishlist bugreport to reprepro. Thanks. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
Wouter Verhelst [EMAIL PROTECTED] writes: On Fri, Nov 25, 2005 at 02:03:12PM +0100, Goswin von Brederlow wrote: It just pains me that Debian does not include all the software to build Debian. Sure it does. It just doesn't include the software that Debian uses to automatically build packages, but that's not the same thing. Which means not all of it. After all, you can build packages in an automated fashion using, e.g., pbuilder; and people do actually do this all the time (where else would I have gotten those FTBFS bugs on doc-linux-nl from? That's an arch:all package). From someone with sbuild setup to build arch:all packages? :))) MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#340606: ITP: libsub-name-perl -- Assigns a new name to referenced sub
Scripsit Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] This module has only one function, which is also exported by default: subname NAME, CODEREF Assigns a new name to referenced sub. The name is only used for informative routines (caller, Carp, etc). Is this really useful enough to be worth the Packages.gz file space? -- Henning Makholm*Vi vil ha wienerbrød!* -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Remove
Scripsit Chris Boyle [EMAIL PROTECTED] On Thu, Nov 24, 2005 at 06:54:12PM +, paddy wrote: I though a robots.txt thingy on the list web archive is coming to the rescue ? Huh? Isn't having the lists searchable generally a good thing? Yes, a very good thing in general. But excluding specifically the posts about c*llw*ve and d**l*ng b*nj*s might be worth a try. Of course, that is if somebody can be bothered to keep such exclusion lists up-to-date. On the other hand, l.d.o. is not the only place debian-devel is publicly archived, so it might not be worth the trouble to try to fix things locally. -- Henning Makholm What has it got in its pocketses? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 03:22:37PM +0100, Goswin von Brederlow wrote: A signature in the deb by a random developer is as trustworthy as the changes file and you already trust that. So we are going from snakeoil to snakoil. No harm done. It's not the same, actually. A signature in a .deb needs to be made by a key which is still trustworthy at the time of verification, which could be quite some time in the future. The key which makes a .changes signature, in contrast, only *needs* to be valid at the time the upload is made -- if it is later compromised, it's not important, because by that time the archive signing key hsa taken over the role of integrity verification. Of course, using the signature on the .changes to verify the .debs independent from the archive at some later date is a nice side-benefit, but one which suffers from the same key-lifetime issues as in-deb signatures, and since the .changes from autobuilt uploads aren't publically available (apparently d-d-$arch-changes isn't archived, from info previously posted in this thread) that method of package authentication isn't going to be 100% reliable anyway. - Matt signature.asc Description: Digital signature
Re: dpkg-sig support wanted?
On 11/25/05, Matthew Palmer [EMAIL PROTECTED] wrote: Of course, using the signature on the .changes to verify the .debs independent from the archive at some later date is a nice side-benefit, but one which suffers from the same key-lifetime issues as in-deb signatures, What exactly is this key lifetime issue? Is it a cryptographic issue? and since the .changes from autobuilt uploads aren't publically available (apparently d-d-$arch-changes isn't archived, from info previously posted in this thread) that method of package authentication isn't going to be 100% reliable anyway.
Re: Secret changes for binNMUs
Michael Banck [EMAIL PROTECTED] writes: On Fri, Nov 25, 2005 at 02:38:32PM +0100, Goswin von Brederlow wrote: Michael Banck [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 06:51:24PM +0100, Goswin von Brederlow wrote: Wouter Verhelst [EMAIL PROTECTED] writes: They were, originally. Ryan's been very active on it since, and it's diverged a bit from the code you're maintaining. Then he should send patches and bug reports to the debian package. When the sbuild package got orphaned two years ago or so, I asked Ryan whether he would like to maintain it, and he said he was not interested. Which is totally fine for me and about everybody else. This split between the user/developer visible sbuild and the secret actual buildd is just not in the spirit of Debian. 1. Please drop the `secret' immediately. Unless you really want to call http://www.debian.org/devel/buildd `secret'. That your mail got resent with the this subject to debian-devel-announce is already stressing it *a lot*, IMHO. The subject and initial mail is not about sbuild being secret but about the overall change for Debian. I think that one is justified. Nothing to do with this subthread. Right, these are two different things. However, the binNMU change is mostly/only useful for the release managers and buildd admins, so I fail to see why not having documented/announced it less than a week after its implementation should imply it was done in `secret', as those people are busy with the next library transition. To make this clear, I totally welcome your post documenting the new binNMU features while the authors have been too busy to do so for now. The point is that the way binNMUs are done (and accepted by DAK) was _changed_ without discussion or announcement. What should have been announced was disabling the old manual binNMU feature. The problem is that people did a binNMU and DAK refused it out of the blue. The initial mail is just to prevent that in the future. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Matthew Palmer [EMAIL PROTECTED] writes: On Fri, Nov 25, 2005 at 03:22:37PM +0100, Goswin von Brederlow wrote: A signature in the deb by a random developer is as trustworthy as the changes file and you already trust that. So we are going from snakeoil to snakoil. No harm done. It's not the same, actually. A signature in a .deb needs to be made by a key which is still trustworthy at the time of verification, which could be quite some time in the future. The key which makes a .changes signature, in contrast, only *needs* to be valid at the time the upload is made -- if it is later compromised, it's not important, because by that time the archive signing key hsa taken over the role of integrity verification. And there you have the big misconception. The archive signing key gives absolutely no integrity ensurance on the deb package. The only thing it insures is that the file was not altered _after_ leaving ftp.de.debian.org for the mirrors and/or user. In no way does it prevent altering the deb on ftp-master. The chain of trust from the DD to the enduser is broken at that point when the chnages file disapears into a non public place and the Release.gpg takes over. Even worse the Release.gpg is signed with an automatic key which I trust way less than a DDs key. Of course, using the signature on the .changes to verify the .debs independent from the archive at some later date is a nice side-benefit, but one which suffers from the same key-lifetime issues as in-deb signatures, and since the .changes from autobuilt uploads aren't publically available (apparently d-d-$arch-changes isn't archived, from info previously posted in this thread) that method of package authentication isn't going to be 100% reliable anyway. - Matt The key-lifetime issue, as you say, is already there for the changes files. It also already there for the dsc files. The deb signatures don't change a thing there. What they change is the availability of the signature. And that they change to 100% for every signed deb (and we hope all debs gets igned at some point). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Olaf van der Spek [EMAIL PROTECTED] writes: On 11/25/05, Matthew Palmer [EMAIL PROTECTED] wrote: Of course, using the signature on the .changes to verify the .debs independent from the archive at some later date is a nice side-benefit, but one which suffers from the same key-lifetime issues as in-deb signatures, What exactly is this key lifetime issue? Is it a cryptographic issue? A key can expire, get stolen / lost or get compromised and revoced. Once that happens you can't trust any signature made by that key. Although one can probably argue that an expired key still has enough trust to verify old debs. Many people don't set an expiry date anyway. While this sounds like a big problem lets have some numbers: Shortly before the sarge release we imported all source packages into the debian-amd64 DAK and actualy did have the problem with dsc file signatures. But that was a problem of maybe 20 packages (out of over 8000). Overall a miniscule problem. If I can verify all but 20 packages that realy is a great bonus. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Fri, 25 Nov 2005, Anthony Towns wrote: (I'm amazed the security crisis we're having is about deb sigs *again*, when we're still relying on md5sum which has a public exploit available now...) Do you really want a thread about how we should switch everything to SHA-512 or something like that? Huh? Why do you want multiple signatures of a .changes file? If I am to do with a .changes file everything I can do with the in-deb signatures, it needs to support at least nested signatures. and also that the .changes file will be stored in the archives along with the .debs, As it turns out, that's probably not feasible per se -- it likely implies too much inode usage, and slack space. That speaks for in-deb signatures in the usability department. and that .debs with wrong/incomplete/missing Source: fields will be rejected (such as all automated bin-NMUed .debs made until about a week ago, or any made by a maintainer right now), Huh? I don't think #62529 is fixed yet. If you think you'll have better luck at doing so, be my guest. That's not a prerequisite for verifying packages from changes files though. Well, the email about the new bin-NMU structure implied that it was fixed for *NMUs done through that structure*. I very much doubt we can produce bin NMUs in our systems with the proper Source header without taking very special steps. My objection is that it's *useless* for *Debian*. Debian has too many sources for packages for key management to be plausible, and keeps This applies to .changes files too, with the aggravating addition that those are a bitch to find right now. Uh, no, .changes files are not remotely useless for Debian right now. Where would you get that idea? I was refering to Debian has too many sources for packages for key management to be plausible. Duh, obviously .change files are useful for Debian, DAK needs them. The tools are the least concern; what's a few dozen lines of code here and there matter? If you insist every package only be uploaded once, and do the maximum packages per day, and stop all other development just to get deb sigs done, it's roughly half a year before that's finished. New packages, bug fixes, new upstream versions will make it take longer. Who said anything about adding in-deb sigs to the entire archive? where dpkg would simply refuse per user-set policy any non-signed deb or any deb without a specific signature... I'm sorry, but you're back to the snakeoil use for deb sigs. Expecting I see I have to spell it out completely all the time, for you will always assume you are talking to clueless people who either doesn't know anything about the issue at hand, or who will be impressed by your over-use of snake-oil. If I want dpkg to always check a signature, it is because it is a signature I know must be there. Like an hypothetical signature added by DAK/dinstall/whatever, or a signature I add to all debs in a specific repository under my control (and in this case, with a timestamp under my own control too, which means I can use it). Doing so with signed release files is possible, but not always in the same way and under the same conditions, and it requires a lot of fragile infrastructure which would be less fragile using in-deb signatures. a signature by a random Debian developer to mean something is not reasonable. YOU are the one who is bringing in signatures from j.random developer. Which, I should add, is all we have in .changes files. Release files are something else, though. I'm tempted to do something like that anyway to see if the md5sum exploit can be used to create fire and ice .debs. Without signed debs, Make that an exploit that says kaboom, you're it but still runs dpkg, and I will help you with it. you'll have no reason to trust it, which is exactly right; with signed debs, you'll have reason to know I built it, but you won't have reason to know I was never going to upload it to Debian because I was just experimenting with some possible security vectors. The question is, will you make the unwarranted assumption that because it's been built by me, that it's usable my you? I won't, that's for sure. I might trust such a deb because it was in a archive where you place debs for general use or something else like that, but not because you signed it. The explanation you need is ...which is useful because _. Again, I can't see any need for multiple signatures for Debian; for non-Debian, if deb sigs are convenient, use them. deb sigs get a lot less convenient if Debian doesn't allow them in debs uploaded to the archive. I don't really care if Debian will ever use the in-deb signatures somehow or not, but I'd like to see them allowed into the archive. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To
Re: dpkg-sig support wanted?
* Anthony Towns: (I'm amazed the security crisis we're having is about deb sigs *again*, when we're still relying on md5sum which has a public exploit available now...) These exploits are irrelevant as far as the Debian archive is concerned. (And that's not because hardly any sarge user verifies the MD5 hashes, by the way. 8-) Moving away from MD5 is certainly not a bad idea, but it's not clear whether the alternatives are any better. Sure, everyone recommends SHA-256 at this stage, but nobody can give a rationale. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Remove
Henning Makholm wrote: Scripsit Chris Boyle [EMAIL PROTECTED] On Thu, Nov 24, 2005 at 06:54:12PM +, paddy wrote: I though a robots.txt thingy on the list web archive is coming to the rescue ? Huh? Isn't having the lists searchable generally a good thing? Yes, a very good thing in general. But excluding specifically the posts about c*llw*ve and d**l*ng b*nj*s might be worth a try. Of course, that is if somebody can be bothered to keep such exclusion lists up-to-date. On the other hand, l.d.o. is not the only place debian-devel is publicly archived, so it might not be worth the trouble to try to fix things locally. It's not. When querying for Call Wave remove, the top hits are on a message from opensubscriber.com. When googling for callwave remove we get a page on lists.debian.org: http://lists.debian.org/debian-devel/2005/01/msg01444.html --Ken Bloom -- I usually have a GPG digital signature included as an attachment. See http://www.gnupg.org/ for info about these digital signatures. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
Blrgh!
OK. So I was working on the problem of fixing dpkg-dev so that
foo Depends: foo-data {SourceVersion}, foo-libs {BinaryVersion}
or something similar actually works. By parsing the version numbers.
Now it's apparently been changed under our noses, in such a way that my
proposed
scheme won't work -- and furthermore anyone who implemented their own
version
of such code, in their own package, will find it magically broken.
Thanks to Goswin and Henrique for *notifying* people of this, since
apparently whoever changed it didn't think about the impacts on other
developers.
Instead binNMU versions are now made by adding +b1 (+b2, +b3) to the
version and containing a Source: foo (non-NMU version) line. The
later makes it possible to reliable associate binNMUs with their
source.
So how do we write a package Depends: line now? Apparently the buildd uses
the original source,
and adds a changelog entry -- *but what happens to the {SourceVersion}
substitution?* Does the buildd
alter the substvars file before compiling? Does the {SourceVersion}
substitution end up being the original 1.2-3 source version, or the 1.2-3+b4
version? Whichever it ends up being, *how do we get the other one* if we
need it?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Anthony Towns aj@azure.humbug.org.au writes: .deb signatures are aimed at giving users some sort of assurance the package is valid; but when you actually look into it -- at least in Debian's circumstances -- those signatures can't actually give any meaningful assurance for any specific validity. Don't they give the user the assurance that a Debian developer was responsible for building and providing the package? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Goswin von Brederlow [EMAIL PROTECTED] writes: The archive signing key gives absolutely no integrity ensurance on the deb package. The only thing it insures is that the file was not altered _after_ leaving ftp.de.debian.org for the mirrors and/or user. In no way does it prevent altering the deb on ftp-master. Isn't that a useful assurance? Perhaps I trust the maintenance of ftp-master, but not the maintenance of Joe Random Mirror. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#340778: ITP: me-jasspa -- A lightweight but fully featured editor
Package: wnpp Severity: wishlist Owner: Patrick Das Gupta [EMAIL PROTECTED] * Package name: me-jasspa Version : 20050505 Upstream Author : Jon Green * URL : http://www.jasspa.com/ * License : GPL Description : A lightweight but fully featured editor Jasspa's MicroEmacs is an emacs-like editor with various features: * Window manager support for the X Window System. * Integrated spell checker. * Undo facility to back-step changes. * Extensive macro language allowing new commands to be created. * Auto C indentation support, with user definable indentation schemes for other languages. * Auto saving and automatic multiple backups. * Multi-buffer support. * Multi-task pipe support for executing shell commands within the context of the editor. * Color language hi-lighting, can be used for any type of file. * Comprehensive on-line help. * Abbreviation and command completion. * Binary file editing support. * Integral file browser with FTP support. * Session history. * Extensible, menu and dialogue features. Homepage: http://www.jasspa.com/ -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.14.2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 03:13:58PM +0100, Goswin von Brederlow wrote: You're correct. And he is also wrong. That would result in debs with the same name and version but different md5sums. Something that easily confuses apt-get and people. And yet, somehow people manage partial cross-grades between Debian and Ubuntu... Regards, aj signature.asc Description: Digital signature
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 12:49:11PM -0800, Thomas Bushnell BSG wrote: Anthony Towns aj@azure.humbug.org.au writes: .deb signatures are aimed at giving users some sort of assurance the package is valid; but when you actually look into it -- at least in Debian's circumstances -- those signatures can't actually give any meaningful assurance for any specific validity. Don't they give the user the assurance that a Debian developer was responsible for building and providing the package? Not really, they give the assurance that it was built by someone who at some point possessed a key that at some point was considered sufficient to identify a Debian developer or a buildd. What assurance would you take from a package signed by Chip's old key? (And why do you think it's actually helpful? Debian developers build *lots* of crap, especially if you can't differentiate stuff uploaded to Debian and not) Cheers, aj signature.asc Description: Digital signature
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 02:27:23PM -0200, Henrique de Moraes Holschuh wrote: Well, the email about the new bin-NMU structure implied that it was fixed for *NMUs done through that structure*. Then the email was wrong. *shrug* My objection is that it's *useless* for *Debian*. Debian has too many sources for packages for key management to be plausible, and keeps This applies to .changes files too, with the aggravating addition that those are a bitch to find right now. Uh, no, .changes files are not remotely useless for Debian right now. Where would you get that idea? I was refering to Debian has too many sources for packages for key management to be plausible. Duh, obviously .change files are useful for Debian, DAK needs them. Then my comment doesn't appl[y] to .changes files too. The tools are the least concern; what's a few dozen lines of code here and there matter? If you insist every package only be uploaded once, and do the maximum packages per day, and stop all other development just to get deb sigs done, it's roughly half a year before that's finished. New packages, bug fixes, new upstream versions will make it take longer. Who said anything about adding in-deb sigs to the entire archive? If they provide a useful service, then of course they should be everywhere. If they don't provide a useful service, why should they be anywhere? The dak check, for reference, is the one that authenticates an ar's in the correct form, it's not an explicit we had dpkg-sig check. If I want dpkg to always check a signature, it is because it is a signature I know must be there. Like an hypothetical signature added by DAK/dinstall/whatever, or a signature I add to all debs in a specific repository under my control (and in this case, with a timestamp under my own control too, which means I can use it). Again, what you do in your own repositories is _fine_. .deb signatures are a completely useful thing to do in some circumstances; which I'm inclined to classify as private development / public release. Debian just happens not to be in that problem space. a signature by a random Debian developer to mean something is not reasonable. YOU are the one who is bringing in signatures from j.random developer. Uh, no, it's what this thread's about. You know, random developers uploading signed packages to the archive...? I'm tempted to do something like that anyway to see if the md5sum exploit can be used to create fire and ice .debs. Without signed debs, Make that an exploit that says kaboom, you're it but still runs dpkg, and I will help you with it. ATM I've got better things to do. But xmas is coming up, with the corresponding need for a pointless xmas project... The explanation you need is ...which is useful because _. Again, I can't see any need for multiple signatures for Debian; for non-Debian, if deb sigs are convenient, use them. deb sigs get a lot less convenient if Debian doesn't allow them in debs uploaded to the archive. How so? Seriously -- add the signature after uploading to Debian. At worst, if you have a deb that's in both Debian and some other source, you might end up installing the unsigned .deb from Debian instead of the signed version -- but you've still verified it just like every other Debian package, so... big deal? If you set up apt's pinning correctly, that won't even happen. Cheers, aj signature.asc Description: Digital signature
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 07:59:40PM +0100, Florian Weimer wrote: * Anthony Towns: (I'm amazed the security crisis we're having is about deb sigs *again*, when we're still relying on md5sum which has a public exploit available now...) These exploits are irrelevant as far as the Debian archive is concerned. (And that's not because hardly any sarge user verifies the MD5 hashes, by the way. 8-) Uh. You're seriously putting your reputation on that claim? And md5 hashes have been verified since either slink or potato depending on when you started using apt; possibly earlier if dselect methods used them like they should have. debootstrap certainly verified them for woody. And heck, they've been used in .changes since day 0. Moving away from MD5 is certainly not a bad idea, but it's not clear whether the alternatives are any better. Sure, everyone recommends SHA-256 at this stage, but nobody can give a rationale. MD5 is broken; SHA-1 is where MD5 was a couple of years ago, SHA256 (or higher) are significantly harder to break in practice, and there's nothing better yet. Cheers, aj signature.asc Description: Digital signature
Re: Remove
Ken Bloom wrote: Henning Makholm wrote: Scripsit Chris Boyle [EMAIL PROTECTED] On Thu, Nov 24, 2005 at 06:54:12PM +, paddy wrote: I though a robots.txt thingy on the list web archive is coming to the rescue ? Huh? Isn't having the lists searchable generally a good thing? Yes, a very good thing in general. But excluding specifically the posts about c*llw*ve and d**l*ng b*nj*s might be worth a try. Of course, that is if somebody can be bothered to keep such exclusion lists up-to-date. On the other hand, l.d.o. is not the only place debian-devel is publicly archived, so it might not be worth the trouble to try to fix things locally. It's not. When querying for Call Wave remove, the top hits are on a message from opensubscriber.com. When googling for callwave remove we get a page on lists.debian.org: REMOVED --Ken Bloom And now you're perpetuating the trend, since you have that link next to the keyword. Suggestion: Why don't all the readers of debian-devel put something like this on their blogs: Google has a tendency for improperly indexed items to stay that way. In order to fix this, it is neccessary to create a google bomb by having several sites all create a link to the correct page with the keyword. In order to fix an incorrect entry that causes spam to the debian-devel mailinglist, I want everyone to know that you should go here to _remove callwave_ [0]. Cheers, Benjamin [0] http://www.callwave.com/members/help/help.asp?item=SEARCH_cancel signature.asc Description: OpenPGP digital signature
Re: Bug#340428: octave2.9 - lists mailing list as uploader in changelog
On Fri, Nov 25, 2005 at 09:01:24AM +0100, Rafael Laboissiere wrote: * Bastian Blank [EMAIL PROTECTED] [2005-11-24 23:45]: | Maintainer: Debian/IA64 Build Daemon [EMAIL PROTECTED] | Changed-By: Debian Octave Group [EMAIL PROTECTED] Could you please explain to me why having Changed-By as a mailing list in this case (a binary NMU done by an autobuilder) is problematic? You may have good reasons for thinking Change-By should list a real person , but I fail to understand it. Please explain we the meaning of person. Bastian -- I object to intellect without discipline; I object to power without constructive purpose. -- Spock, The Squire of Gothos, stardate 2124.5
Re: dpkg-sig support wanted?
On Sat, Nov 26, 2005 at 08:48:45AM +1000, Anthony Towns wrote: On Fri, Nov 25, 2005 at 03:13:58PM +0100, Goswin von Brederlow wrote: You're correct. And he is also wrong. That would result in debs with the same name and version but different md5sums. Something that easily confuses apt-get and people. And yet, somehow people manage partial cross-grades between Debian and Ubuntu... People manage to do it, but it really isn't a good idea at all to mix repositories which contain different builds of the same source packages. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Sat, Nov 26, 2005 at 09:13:02AM +1000, Anthony Towns wrote: Moving away from MD5 is certainly not a bad idea, but it's not clear whether the alternatives are any better. Sure, everyone recommends SHA-256 at this stage, but nobody can give a rationale. MD5 is broken; SHA-1 is where MD5 was a couple of years ago, SHA256 (or higher) are significantly harder to break in practice, and there's nothing better yet. Just a comment here for those who are not used to hash functions: Broken here means that you can generate collisions faster than using the birthday attack (2^64 for MD5, 2^80 for SHA-1). It does not have to mean that you can do _really_ evil stuff, like generate a second file with the same MD5 hash as a given file (so-called second preimage, IIRC) and to the best of my knowledge, nobody has done so yet). However, there's a long way from you can't generate a valid .deb with a given md5sum easily to SHA-256 is no better than MD5. You can generate an MD5 collision in four hours on a standard desktop computer today; you're nowhere near that for SHA-1, and SHA-256 is still AFAIK not broken (although it relies on the same basic structure as MD5 and SHA-1). All three might eventually be truly broken, but you can bet that MD5 will be the first to go. If you use SHA-256 today instead of MD5, you probably buy yourself a few extra years, which you can use to smooth out the transition to the next hash function when the world advances. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Thiemo == Thiemo Seufer [EMAIL PROTECTED] writes: Well, even if I know naught about it, it looks to me that having something signed is better than having the same something not signed. Thiemo Sorry, but that's a snake oil rationale. A: Why do you lock your car up[1]? B: Because it looks like having it locked is better then not having it locked. A: Sorry, but that's a snake oil rationale. Anybody can pick the lock and break in. Anybody can smash a window and break in. etc. However, we still lock our cars regardless. We still lock our houses. We still use signatures and ID cards (all of which can be forged) as protection to keep our money safe. The reason why? Because we have just made it more difficult (or so we hope!) for somebody to break in. We still consider this a worth while compared with the added inconvenience of having to maintain the additional security (e.g. keep the key safe and not lost). Despite the fact we all know it is not absolute security. It is also feasible. Yes, you could hire a security guard to watch your car 24 hours a day, but that is likely to cost more then the car is worth. Most people don't consider their cars to be this important. I think the same thing applies here - sure somebody could interfere with the system and either steal the private key or get a package signed that shouldn't be signed, but if you really want to argue along these lines, I think we remove all signatures everywhere, because the possibility exists any one of these could be forged (especially as Debian cannot guarantee that every maintainer keeps their private key secure, and that their build systems are secure, etc). So just saying its snake oil isn't really saying anything IMHO, because taken to an extreme all security we have in this world *is* snake oil. Sometimes it works. Sometimes it doesn't work. That doesn't mean we shouldn't try to improve it as much as possible. The only exception I would make is when improvements mean extra security for political/red tape reasons which do nothing to stop the weaknesses they are meant to stop, but instead serve to make our politicians looks good as well as giving them more income. However, I think the ability to trace a Debian binary package to its source, even if the original .changes file is no longer available, is a definite advantage, and is not any less reliable or secure then using the original .changes file for the same purpose. In fact, you could argue it is more secure then the Received headers everyone relies on to trace SPAM (which have no cryptographic signature). I also believe that the threat of somebody being tricked into installing a Trojan package is a very real possibility, and we should do everything we can do to aid our users prevent this from happening. Notes: [1] Assuming you have a car, if not replace the words car and lock with something more appropriate. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Sat, Nov 26, 2005 at 10:47:57AM +1100, Brian May wrote: Well, even if I know naught about it, it looks to me that having something signed is better than having the same something not signed. Sorry, but that's a snake oil rationale. A: Why do you lock your car up[1]? Because it makes it harder to steal the car. I think the point was that signing a .deb did not automatically make it harder to do whatever the scenario asked for. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Secret changes for binNMUs
On Fri, 25 Nov 2005, Nathanael Nerode wrote:
OK. So I was working on the problem of fixing dpkg-dev so that
foo Depends: foo-data {SourceVersion}, foo-libs {BinaryVersion}
or something similar actually works. By parsing the version numbers.
I'd very much like debhelper or dpkg-* to give us another variable that
points to the parent version [changelog-wise] when bin NMUs are done, and to
the current version [changelog-wise] otherwise.
Meanwhile, I am using this: unversioned depends and two conflicts: (
{Upstream-Version}), (= {Upstream-Version}.1).
BinNMUs won't break compatibility between arch any and arch all in any of my
packages, and debian revisions breaking them are rare enough that I will
track that by hand, so the above is enough (although far from ideal).
So how do we write a package Depends: line now? Apparently the buildd uses
the original source,
See above. We had that problem already, but now we will have to deploy a
real solution instead of hacks. Ain't that nice? :-)
Does anyone have any idea on how to detect if a currently running buind is a
bin NMU or not?
and adds a changelog entry -- *but what happens to the {SourceVersion}
substitution?* Does the buildd
alter the substvars file before compiling? Does the {SourceVersion}
I bet it works in the simplest way possible, i.e. it is set to the latest
changelog entry: the binNMU version.
substitution end up being the original 1.2-3 source version, or the
1.2-3+b4 version? Whichever it ends up being, *how do we get the other
one* if we need it?
We really need another substvar with different semantics.
--
One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie. -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Heimdal autotools dramas
My biggest concern with the Heimdal in experimental, is glob() in libroken. To the best of my knowledge, it isn't required because libc6 glob() does everything required. I am concerned, because of the potential of the symbols conflicting with the function in libc6. The Heimdal configure script correctly detects that glob() is present in libc6, but appears to build glob.c anyway, and it also installs glob.h. A similar situation appears to exist with fnmatch, but I haven't investigated in detail. Unfortunately, solving this is pushing my automake knowledge to its limits. lib/roken/Makefile.am has: if have_glob_h glob_h = else glob_h = glob.h endif Some how that is being set in lib/roken/Makefile, despite the fact have_glob_h is also set (this is confusing me!!!) I simply cannot see where lib/roken/Makefile.am references glob.c. However, lib/roken/Makefile references glob$U.lo and glob$U.o. I asked upstream Heimdal and got no response. Any help would be much appreciated. Thanks. PS. Source code is Heimdal in Debian experimental. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 02:57:36PM +0100, Goswin von Brederlow wrote: Steve Langasek [EMAIL PROTECTED] writes: On Thu, Nov 24, 2005 at 07:17:06PM +0100, Goswin von Brederlow wrote: That's easy: you trust the Packages file to be correct when using apt, and it's not verified at all by per-package signatures. In what way trust and how does that change anything? At best you can prevent a newer version of a package to appear in the Packages file by compromising it. You can't subvert a package itself. But you can already ship yesterdays Release.gpg, Release and Packages file to a user and thereby prevent any updates. On the other hand, without package signatures ftp-master adds a vulnerability. You can hack into it, replace debs, recreate the Packages, Release and Release.gpg file and thereby infect users. With signed debs that could still be detected by every user in apt-get. Only if every user is in a position to verify signatures from each Debian developer individually, which is completely unrealistic. Up to a point you can trust the keyring. As much as you can trust any DD signature. You try to argue that signatures are not absolutely trustworthy but that is nothing new. I'm arguing that a 5-hop-long signature chain to establish the validity of a Debian package is as good as useless, and worse if the user doesn't understand this. And a 5-hop-long signature chain does *not* mean that anyone in that chain trusts the person holding the key on the end to upload packages to Debian. The only thing we have that establishes *that* is the presence of the user's key in the Debian keyring, so then you have the logistical problem of how arbitrary users are supposed to verify whether a given key is in the keyring. The debian-keyring package doesn't get updated every time there's a key added or removed, and the web interface to keyring.debian.org doesn't provide any cryptographic assurances. Oh, and BTW, check the IPs of ftp-master.debian.org and keyring.debian.org... -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
up-to-date debian keyring with rsync (Re: dpkg-sig support wanted?)
* Steve Langasek [Fri, 25 Nov 2005 17:19:01 -0800]: how arbitrary users are supposed to verify whether a given key is in the keyring. The debian-keyring package doesn't get updated every time there's a key added or removed, and the web interface to keyring.debian.org doesn't provide any cryptographic assurances. Just as a side note other developers may be interested in knowing, the debian keyring can be synced via rsync. I personally like having a mostly-up-to-date copy of it in my computer. % cat /etc/cron.weekly/LOCAL-update-keyring #! /bin/sh -e cd /var/local/keyring rsync -rlptDq rsync://keyring.debian.org/keyrings/ . -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Elton John - Too many tears -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
Brian May wrote: Thiemo == Thiemo Seufer [EMAIL PROTECTED] writes: Well, even if I know naught about it, it looks to me that having something signed is better than having the same something not signed. Thiemo Sorry, but that's a snake oil rationale. A: Why do you lock your car up[1]? B: Because it looks like having it locked is better then not having it locked. A: Sorry, but that's a snake oil rationale. Anybody can pick the lock and break in. Anybody can smash a window and break in. etc. Wrong, it makes break-ins harder. OTOH we don't put stickers with this car is locked on our cars. The quote above suggested a signed package is somehow better than an unsigned one, even when no improvements can be shown. But the only thing it reliably achieves in that case is to increase the exposure of the signing key. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Primer sitio web de Ropa Intima en Costa Rica
Si deseas desinscribirte de esta lista, envia un correo a [EMAIL PROTECTED] solicitandolo. Gracias
Bug#340805: ITP: gearhead -- roguelike mecha role playing game
Package: wnpp Severity: wishlist Owner: Kari Pahula [EMAIL PROTECTED] * Package name: gearhead Version : 1.000 Upstream Author : Joseph Hewitt [EMAIL PROTECTED] * URL : http://www.geocities.com/pyrrho12/programming/gearhead/ * License : LGPL Description : roguelike mecha role playing game A century and a half ago the Earth was nearly destroyed by nuclear war. Now, a federation of free city-states has begun to restore civilization. However, there are forces operating in the darkness which will unleash the horrors of the past age in a bid to determine the future of the human race. Features of the game include random storyline generation, richly detailed character generation, complex NPC interaction, and of course over 150 different mechanical designs ranging from jet fighters to giant robots to city-smashing tanks. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
On Fri, Nov 25, 2005 at 05:19:01PM -0800, Steve Langasek wrote: Oh, and BTW, check the IPs of ftp-master.debian.org and keyring.debian.org... Well, at this moment those are distinct, because ftp-master is temporarily hosted on spohr.debian.org, and not on raff.debian.org, where keyring.d.o still is. But yes, they used to be the same and will again become the same. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg-sig support wanted?
[Steinar H. Gunderson] All three might eventually be truly broken, but you can bet that MD5 will be the first to go. If you use SHA-256 today instead of MD5, you probably buy yourself a few extra years, which you can use to smooth out the transition to the next hash function when the world advances. You may laugh if you wish, but I think it's annoying to have to move to a hash function whose hexadecimal representation takes 64 bytes, which doesn't leave much room on an 80-column line to describe what the hash is hashing. Maybe by the time coreutils ships a sha256sum program, the world will have settled upon BASE64, which requires only 43 bytes. signature.asc Description: Digital signature
Accepted devmapper 2:1.02.00-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Nov 2005 20:07:41 +0100 Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source i386 Version: 2:1.02.00-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 338947 Changes: devmapper (2:1.02.00-1) unstable; urgency=low . * New upstream version. (closes: #338947) Files: 0544d6af4bd728deb313a0a1ff1345e3 759 admin optional devmapper_1.02.00-1.dsc 0c24f817a384be70296549af3e51424a 902440 admin optional devmapper_1.02.00.orig.tar.gz 202487cc6c68a9daad517d470a8cbc10 54906 admin optional devmapper_1.02.00-1.diff.gz 66976c9597d0179ac8277a08eb15c687 40924 libdevel optional libdevmapper-dev_1.02.00-1_i386.deb 1675fb92fd015f477d3e7b30d6c95bc7 31946 libs optional libdevmapper1.02_1.02.00-1_i386.deb b7465cb1f374b9c055aad5f627fbd25b 21506 debian-installer optional libdevmapper1.02-udeb_1.02.00-1_i386.udeb 3640573deb5e56ae53806ae6de9200e5 23662 admin optional dmsetup_1.02.00-1_i386.deb f8dfb03cd15c04c84c3f514aaa61fe8a 10864 debian-installer optional dmsetup-udeb_1.02.00-1_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iEYEARECAAYFAkOGEPAACgkQLkAIIn9ODhGregCgyeZP/eRahRD2WYvc8D7/MoXg siAAnA5zxMMRT/8OVB+k2rCo3EmnwBI+ =Uu02 -END PGP SIGNATURE- Accepted: devmapper_1.02.00-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.00-1.diff.gz devmapper_1.02.00-1.dsc to pool/main/d/devmapper/devmapper_1.02.00-1.dsc devmapper_1.02.00.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.00.orig.tar.gz dmsetup-udeb_1.02.00-1_i386.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.00-1_i386.udeb dmsetup_1.02.00-1_i386.deb to pool/main/d/devmapper/dmsetup_1.02.00-1_i386.deb libdevmapper-dev_1.02.00-1_i386.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.00-1_i386.deb libdevmapper1.02-udeb_1.02.00-1_i386.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.00-1_i386.udeb libdevmapper1.02_1.02.00-1_i386.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.00-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gcc-snapshot 20051124-1 (source i386 powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Nov 2005 23:05:46 + Source: gcc-snapshot Binary: gcc-snapshot Architecture: i386 powerpc source Version: 20051124-1 Distribution: unstable Urgency: low Maintainer: Debian GCC Maintainers debian-gcc@lists.debian.org Changed-By: Matthias Klose [EMAIL PROTECTED] Description: gcc-snapshot - A SNAPSHOT of the GNU Compiler Collection Changes: gcc-snapshot (20051124-1) unstable; urgency=low . * Reenable Ada on powerpc, alpha, mips, mipsel, s390. * Fix build failures on hppa and sparc. * Reenable java on mips, mipsel. Files: 250c0ddda1ddffb32b8e0def7b12e361 2647 devel standard gcc-snapshot_20051124-1.dsc 3b0e8de6604818d29d6299d5b1aec401 35117644 devel standard gcc-snapshot_20051124.orig.tar.gz 540e69d9e6f8c1d8aac54234bbf90e1f 67249374 devel extra gcc-snapshot_20051124-1_powerpc.deb c284a2eb15caf04934847a4409f85835 62148502 devel extra gcc-snapshot_20051124-1_i386.deb f1d8864989fb9a7dd196dfec3d7ea8ff 160356 devel standard gcc-snapshot_20051124-1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDhsx2StlRaw+TLJwRAlGdAKCw1CkiCToiErlMfDEUuqz+wcOidACeJ623 xsqQjPCPi5uSQTVFocCjtsM= =M3OQ -END PGP SIGNATURE- Accepted: gcc-snapshot_20051124-1.diff.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20051124-1.diff.gz gcc-snapshot_20051124-1.dsc to pool/main/g/gcc-snapshot/gcc-snapshot_20051124-1.dsc gcc-snapshot_20051124-1_i386.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20051124-1_i386.deb gcc-snapshot_20051124-1_powerpc.deb to pool/main/g/gcc-snapshot/gcc-snapshot_20051124-1_powerpc.deb gcc-snapshot_20051124.orig.tar.gz to pool/main/g/gcc-snapshot/gcc-snapshot_20051124.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gdm 2.8.0.6-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Nov 2005 09:52:06 -0800 Source: gdm Binary: gdm Architecture: source i386 Version: 2.8.0.6-2 Distribution: unstable Urgency: low Maintainer: Ryan Murray [EMAIL PROTECTED] Changed-By: Ryan Murray [EMAIL PROTECTED] Description: gdm- GNOME Display Manager Closes: 339790 Changes: gdm (2.8.0.6-2) unstable; urgency=low . * Apply patch from CVS to fix new auto VT allocation method (closes: #339790) Files: 1592e238751b00789399e48268d70e4b 701 gnome optional gdm_2.8.0.6-2.dsc 006cf3faf884319bc12049c988613f4d 71117 gnome optional gdm_2.8.0.6-2.diff.gz c9ec6c3b91a1ed6a9028024e44828dfe 3568330 gnome optional gdm_2.8.0.6-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhtPBN2Dbz/1mRasRAvQXAKDqJpiaYTFrTHCo+vPNXvt9oaduswCghAEQ T0VYIJo4eWGHM9Zn9+eykKw= =YOaH -END PGP SIGNATURE- Accepted: gdm_2.8.0.6-2.diff.gz to pool/main/g/gdm/gdm_2.8.0.6-2.diff.gz gdm_2.8.0.6-2.dsc to pool/main/g/gdm/gdm_2.8.0.6-2.dsc gdm_2.8.0.6-2_i386.deb to pool/main/g/gdm/gdm_2.8.0.6-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted slgtk 0.5.15.r4-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 11:01:43 +0100 Source: slgtk Binary: slang-gtk Architecture: source i386 Version: 0.5.15.r4-6 Distribution: unstable Urgency: low Maintainer: Debian JED Group [EMAIL PROTECTED] Changed-By: Rafael Laboissiere [EMAIL PROTECTED] Description: slang-gtk - binds the GIMP Toolkit (GTK) to the S-Lang scripting language Changes: slgtk (0.5.15.r4-6) unstable; urgency=low . +++ Changes by Rafael Laboissiere . * debian/rules: Build the package using make dynamic instead of amke all. This prevents the static target from being built, which may fix the autobuild problems on 64-bit architectures. Files: 8b28448eefbaf5054dbce723b4a33976 748 interpreters optional slgtk_0.5.15.r4-6.dsc a616176b10e647f488ca66d6878e3d70 5249 interpreters optional slgtk_0.5.15.r4-6.diff.gz 74bfe655154debae74e52b8f260111cd 506358 interpreters optional slang-gtk_0.5.15.r4-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDhuYXk3oga0pdcv4RAoWIAJwJNRMeXoRBj2jFrbOVGrBLySAp4ACdHKNS 8dzIaW5wEi+P0uNrxiNwHvA= =fmVD -END PGP SIGNATURE- Accepted: slang-gtk_0.5.15.r4-6_i386.deb to pool/main/s/slgtk/slang-gtk_0.5.15.r4-6_i386.deb slgtk_0.5.15.r4-6.diff.gz to pool/main/s/slgtk/slgtk_0.5.15.r4-6.diff.gz slgtk_0.5.15.r4-6.dsc to pool/main/s/slgtk/slgtk_0.5.15.r4-6.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tmsnc 0.3.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Nov 2005 13:08:41 +0100 Source: tmsnc Binary: tmsnc Architecture: source i386 Version: 0.3.1-1 Distribution: unstable Urgency: low Maintainer: Miriam Ruiz [EMAIL PROTECTED] Changed-By: Miriam Ruiz [EMAIL PROTECTED] Description: tmsnc - textbased (console) MSN client Changes: tmsnc (0.3.1-1) unstable; urgency=low . * New Upstream Release. * Compiling with -O0 to avoid a problem when using GCC4 (see #340561). Files: 562fc44fe77088c99415b86af67ad056 598 net optional tmsnc_0.3.1-1.dsc 3b30e5dab0b1b679d2b945c3a5713636 163015 net optional tmsnc_0.3.1.orig.tar.gz c99ffe779b4ecfb9e3232b33f69de6ec 2970 net optional tmsnc_0.3.1-1.diff.gz 2663d59cc99531753aefebf58876bd13 44338 net optional tmsnc_0.3.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhub3xRSvjkukAcMRAtjzAKDWAS6beJCKV4v3kDGg1RzmA31OjQCghkJj qeLWu236TIPMYdh3zqH7rYE= =YmdI -END PGP SIGNATURE- Accepted: tmsnc_0.3.1-1.diff.gz to pool/main/t/tmsnc/tmsnc_0.3.1-1.diff.gz tmsnc_0.3.1-1.dsc to pool/main/t/tmsnc/tmsnc_0.3.1-1.dsc tmsnc_0.3.1-1_i386.deb to pool/main/t/tmsnc/tmsnc_0.3.1-1_i386.deb tmsnc_0.3.1.orig.tar.gz to pool/main/t/tmsnc/tmsnc_0.3.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wzdftpd 0.5.5-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 11:58:16 +0100 Source: wzdftpd Binary: wzdftpd-mod-perl wzdftpd-back-mysql wzdftpd-dev wzdftpd-back-pgsql wzdftpd wzdftpd-mod-tcl Architecture: source i386 Version: 0.5.5-5 Distribution: unstable Urgency: low Maintainer: Pierre Chifflier [EMAIL PROTECTED] Changed-By: Pierre Chifflier [EMAIL PROTECTED] Description: wzdftpd- A portable, modular, not user-friendly ftp server wzdftpd-back-mysql - MySQL backend for wzdftpd wzdftpd-back-pgsql - PostgreSQL backend for wzdftpd wzdftpd-dev - Development files for wzdftpd wzdftpd-mod-perl - Perl module for wzdftpd wzdftpd-mod-tcl - TCL module for wzdftpd Closes: 340711 Changes: wzdftpd (0.5.5-5) unstable; urgency=low . * Fixed patch 04_list_firefox (Closes: #340711) * Fixed errors in shell script in prerm scripts Files: 4366159e0243eac0cd5f68bbf9c3ceb4 792 net optional wzdftpd_0.5.5-5.dsc 7444bf2ade9d5935663474eeb45c1539 9093 net optional wzdftpd_0.5.5-5.diff.gz f0b267ae8a2e3eb36870920060b5cc02 275968 net optional wzdftpd_0.5.5-5_i386.deb 394080ce4537dc39538c8fb42b466a3e 33298 net optional wzdftpd-back-mysql_0.5.5-5_i386.deb 7d9ca750fb749b75ef1a7d189207df88 33974 net optional wzdftpd-back-pgsql_0.5.5-5_i386.deb fc82dbea6508a356d7db655f2fab1f32 30766 net optional wzdftpd-mod-tcl_0.5.5-5_i386.deb 9df2e64b6eaa371a854e7524edcf33d6 49588 net optional wzdftpd-mod-perl_0.5.5-5_i386.deb f7adc77349fb5ba209d369d5e52a3f89 206588 libdevel optional wzdftpd-dev_0.5.5-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhvWOw3ao2vG823MRAksPAJkBOpcA/WLWm0NfoWV6y5Xz7zMUXQCfS6Pj XyYn6jUY7s9vzT9OTQZEy84= =jCri -END PGP SIGNATURE- Accepted: wzdftpd-back-mysql_0.5.5-5_i386.deb to pool/main/w/wzdftpd/wzdftpd-back-mysql_0.5.5-5_i386.deb wzdftpd-back-pgsql_0.5.5-5_i386.deb to pool/main/w/wzdftpd/wzdftpd-back-pgsql_0.5.5-5_i386.deb wzdftpd-dev_0.5.5-5_i386.deb to pool/main/w/wzdftpd/wzdftpd-dev_0.5.5-5_i386.deb wzdftpd-mod-perl_0.5.5-5_i386.deb to pool/main/w/wzdftpd/wzdftpd-mod-perl_0.5.5-5_i386.deb wzdftpd-mod-tcl_0.5.5-5_i386.deb to pool/main/w/wzdftpd/wzdftpd-mod-tcl_0.5.5-5_i386.deb wzdftpd_0.5.5-5.diff.gz to pool/main/w/wzdftpd/wzdftpd_0.5.5-5.diff.gz wzdftpd_0.5.5-5.dsc to pool/main/w/wzdftpd/wzdftpd_0.5.5-5.dsc wzdftpd_0.5.5-5_i386.deb to pool/main/w/wzdftpd/wzdftpd_0.5.5-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted discover1 1.7.16 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 09:14:13 -0200 Source: discover1 Binary: libdiscover1 discover1 libdiscover1-pic discover1-udeb libdiscover1-dev Architecture: source powerpc Version: 1.7.16 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Otavio Salvador [EMAIL PROTECTED] Description: discover1 - hardware identification system discover1-udeb - hardware identification library (udeb) (udeb) libdiscover1 - hardware identification library libdiscover1-dev - hardware identification library development files libdiscover1-pic - hardware identification library - static PIC version Closes: 335323 338359 339565 Changes: discover1 (1.7.16) unstable; urgency=low . * Bump libdiscover1 dependencie since on 1.7.10 was added new symbols. Thanks to Daniel Stone [EMAIL PROTECTED] by notice it. (closes: #338359) * Add LSB formated dependency information info in init.d script. Thanks to Petter Reinholdtsen [EMAIL PROTECTED] by the need information. (closes: #335323) * Applied patch from Jurij Smakov [EMAIL PROTECTED] to fix SBUS detection. (closes: #339565) Files: 7861b2d38ab8178225927091e0ec2aea 798 admin optional discover1_1.7.16.dsc 4b15b0e139693c7e5e4959fba5e93047 270018 admin optional discover1_1.7.16.tar.gz d7e548eed2badb5e7a78a7d5fb94d283 69966 admin optional discover1_1.7.16_powerpc.deb 3c8f130ad05a7b4f55c8ce3075f20edf 100640 libs optional libdiscover1_1.7.16_powerpc.deb cf9c2ec48b4d83a544ff049f34312d26 25162 libdevel optional libdiscover1-dev_1.7.16_powerpc.deb 2b38ffbae20e58943e7dee86fea87efe 57440 libs extra libdiscover1-pic_1.7.16_powerpc.deb 92bccfae321166e2085c8fd61d2fde38 39668 debian-installer extra discover1-udeb_1.7.16_powerpc.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhvUlLqiZQEml+FURAuf5AJ9DcUTUWq1sZ5vPYFEsq9FVc8ZHOgCcCBR1 pXrZaIWPg2pVhcrz3ZY32lw= =fYl8 -END PGP SIGNATURE- Accepted: discover1-udeb_1.7.16_powerpc.udeb to pool/main/d/discover1/discover1-udeb_1.7.16_powerpc.udeb discover1_1.7.16.dsc to pool/main/d/discover1/discover1_1.7.16.dsc discover1_1.7.16.tar.gz to pool/main/d/discover1/discover1_1.7.16.tar.gz discover1_1.7.16_powerpc.deb to pool/main/d/discover1/discover1_1.7.16_powerpc.deb libdiscover1-dev_1.7.16_powerpc.deb to pool/main/d/discover1/libdiscover1-dev_1.7.16_powerpc.deb libdiscover1-pic_1.7.16_powerpc.deb to pool/main/d/discover1/libdiscover1-pic_1.7.16_powerpc.deb libdiscover1_1.7.16_powerpc.deb to pool/main/d/discover1/libdiscover1_1.7.16_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted discover1-data 1.2005.11.25 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 09:40:57 -0200 Source: discover1-data Binary: discover1-data discover1-data-udeb Architecture: source all Version: 1.2005.11.25 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Otavio Salvador [EMAIL PROTECTED] Description: discover1-data - hardware lists for libdiscover1 discover1-data-udeb - hardware lists for libdiscover1 (short list) (udeb) Closes: 331107 334472 334754 Changes: discover1-data (1.2005.11.25) unstable; urgency=low . [ Otavio Salvador ] * change the following PCI IDs: 1106:3119 a ethernet adapter using via-velocity module (closes: #331107); . [ David Nusinow ] * Radeon IGP 330M/340M/350M can all use the ati module with Xorg . [ Christian Perrier ] * change the following PCI IDs: 8086:27dc a ethernet adapter using e100 module (closes: #334754); 105a:3d75 Promise SATA controller using the sata_promise module (closes: #334472); Files: 5c94f6917b7463c6406f65bddef0bda1 774 libs optional discover1-data_1.2005.11.25.dsc 9a4739b656371e07c465dc02d45821a9 124873 libs optional discover1-data_1.2005.11.25.tar.gz 63764a2c8a3d03b05fa2eed5882e55b4 107168 libs optional discover1-data_1.2005.11.25_all.deb d2fd400e6b11786aa3157446ee99c642 17898 debian-installer extra discover1-data-udeb_1.2005.11.25_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhvjTLqiZQEml+FURAvgFAJ9TojsR2cP+qlCseNFmUBeaSGruUQCfSsKv uwleQNEfdKVT/siYYSoZvJE= =wLuP -END PGP SIGNATURE- Accepted: discover1-data-udeb_1.2005.11.25_all.udeb to pool/main/d/discover1-data/discover1-data-udeb_1.2005.11.25_all.udeb discover1-data_1.2005.11.25.dsc to pool/main/d/discover1-data/discover1-data_1.2005.11.25.dsc discover1-data_1.2005.11.25.tar.gz to pool/main/d/discover1-data/discover1-data_1.2005.11.25.tar.gz discover1-data_1.2005.11.25_all.deb to pool/main/d/discover1-data/discover1-data_1.2005.11.25_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted curl 7.15.0-5 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 10:30:25 +0100 Source: curl Binary: libcurl3-dbg libcurl3 libcurl3-dev libcurl3-gnutls-dev libcurl3-openssl-dev libcurl3-gnutls curl Architecture: source i386 all Version: 7.15.0-5 Distribution: unstable Urgency: low Maintainer: Domenico Andreoli [EMAIL PROTECTED] Changed-By: Domenico Andreoli [EMAIL PROTECTED] Description: curl - Get a file from an HTTP, HTTPS, FTP or GOPHER server libcurl3 - Multi-protocol file transfer library libcurl3-dbg - libcurl compiled with debug symbols libcurl3-dev - Transitional package to libcurl3-openssl-dev libcurl3-gnutls - Multi-protocol file transfer library libcurl3-gnutls-dev - Development files and documentation for libcurl libcurl3-openssl-dev - Development files and documentation for libcurl Closes: 334888 338680 338681 Changes: curl (7.15.0-5) unstable; urgency=low . * libcurl3-gnutls-dev and libcurl3-openssl-dev now only recommend libkrb5-dev (closes: #334888). * Applied upstream patch to fix error message in case FTP-path does not exist (closes: #338680). * Applied upstream patch to fix parsing of --limit-rate command line option (closes: #338681). Files: 5e9da2c67d4e38c2f78ac62aa928b303 943 web optional curl_7.15.0-5.dsc 92cc00724dfeeebd17e272baa22e0ac4 182190 web optional curl_7.15.0-5.diff.gz 529eef340ebc972f66a6a69b955b8c44 162338 web optional curl_7.15.0-5_i386.deb 3787f0c917553692889b7b3459f4fb0c 160332 libs optional libcurl3_7.15.0-5_i386.deb 607eb0520ed06e8d7cd2134a5500fe49 154672 libs optional libcurl3-gnutls_7.15.0-5_i386.deb 62fae6e0740fadf633ee0f2d0cf114f0 702790 libdevel optional libcurl3-openssl-dev_7.15.0-5_i386.deb d32b21807f8f436d80c3450cecf0943f 696598 libdevel optional libcurl3-gnutls-dev_7.15.0-5_i386.deb cc6483a87caad607b489512d4c61592e 26870 libdevel optional libcurl3-dev_7.15.0-5_all.deb fb245dcdb511ea57639471c3d3d638a3 503854 libdevel extra libcurl3-dbg_7.15.0-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhvmxBneQM6IOvFARAlthAKCL8fYpjHmqiNgswFMtuuLSQBk6pwCaAjCS TYBMj7Xf29MsOOtXwqIrh2o= =2uao -END PGP SIGNATURE- Accepted: curl_7.15.0-5.diff.gz to pool/main/c/curl/curl_7.15.0-5.diff.gz curl_7.15.0-5.dsc to pool/main/c/curl/curl_7.15.0-5.dsc curl_7.15.0-5_i386.deb to pool/main/c/curl/curl_7.15.0-5_i386.deb libcurl3-dbg_7.15.0-5_i386.deb to pool/main/c/curl/libcurl3-dbg_7.15.0-5_i386.deb libcurl3-dev_7.15.0-5_all.deb to pool/main/c/curl/libcurl3-dev_7.15.0-5_all.deb libcurl3-gnutls-dev_7.15.0-5_i386.deb to pool/main/c/curl/libcurl3-gnutls-dev_7.15.0-5_i386.deb libcurl3-gnutls_7.15.0-5_i386.deb to pool/main/c/curl/libcurl3-gnutls_7.15.0-5_i386.deb libcurl3-openssl-dev_7.15.0-5_i386.deb to pool/main/c/curl/libcurl3-openssl-dev_7.15.0-5_i386.deb libcurl3_7.15.0-5_i386.deb to pool/main/c/curl/libcurl3_7.15.0-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted 915resolution 0.4.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 21 Nov 2005 11:18:05 +0100 Source: 915resolution Binary: 915resolution Architecture: source i386 Version: 0.4.8-1 Distribution: unstable Urgency: low Maintainer: Steffen Joeris [EMAIL PROTECTED] Changed-By: Steffen Joeris [EMAIL PROTECTED] Description: 915resolution - resolution modify tool for Intel graphic chipset Changes: 915resolution (0.4.8-1) unstable; urgency=low . * new upstream release Files: 8803ab465bb4d0d9ebe24cea0d736a5c 622 x11 extra 915resolution_0.4.8-1.dsc 95835ee14f411afef6ace68decfa66e1 6943 x11 extra 915resolution_0.4.8.orig.tar.gz c5f87dc4271b7429a9d00c56d52cd802 3039 x11 extra 915resolution_0.4.8-1.diff.gz e5b5769ad1de2b9d8d0c842c7f1ac3b1 11818 x11 extra 915resolution_0.4.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDhwCW9/DnDzB9Vu0RArQXAJ904xq5R7mSYYx6a5t9CLGDBNSx1gCeJLBP rN6XI51QfHIDLITHsSn/l4c= =5RQP -END PGP SIGNATURE- Accepted: 915resolution_0.4.8-1.diff.gz to pool/main/9/915resolution/915resolution_0.4.8-1.diff.gz 915resolution_0.4.8-1.dsc to pool/main/9/915resolution/915resolution_0.4.8-1.dsc 915resolution_0.4.8-1_i386.deb to pool/main/9/915resolution/915resolution_0.4.8-1_i386.deb 915resolution_0.4.8.orig.tar.gz to pool/main/9/915resolution/915resolution_0.4.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sylpheed-claws-gtk2 1.9.100-1.1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 01:41:28 -0800 Source: sylpheed-claws-gtk2 Binary: sylpheed-claws-gtk2-spamassassin sylpheed-claws-gtk2-plugins sylpheed-claws-gtk2 sylpheed-claws-gtk2-i18n sylpheed-claws-gtk2-pgpinline libsylpheed-claws-gtk2-dev sylpheed-claws-gtk2-pgpmime sylpheed-claws-gtk2-dillo-viewer sylpheed-claws-gtk2-clamav sylpheed-claws-gtk2-trayicon Architecture: source i386 all Version: 1.9.100-1.1 Distribution: unstable Urgency: low Maintainer: Ricardo Mones [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: libsylpheed-claws-gtk2-dev - Development files for Sylpheed Claws GTK2 plugins sylpheed-claws-gtk2 - Extended GTK2 version of the Sylpheed mail client sylpheed-claws-gtk2-clamav - Clam AntiVirus plugin for the Sylpheed Claws GTK2 mail client sylpheed-claws-gtk2-dillo-viewer - HTML viewer plugin for Sylpheed Claws GTK2 using Dillo sylpheed-claws-gtk2-i18n - Locale data for Sylpheed Claws (i18n support) sylpheed-claws-gtk2-pgpinline - PGP/inline plugin for Sylpheed Claws GTK2 sylpheed-claws-gtk2-pgpmime - PGP/MIME plugin for Sylpheed Claws GTK2 sylpheed-claws-gtk2-plugins - Installs plugins for the Sylpheed Claws GTK2 mail client sylpheed-claws-gtk2-spamassassin - SpamAssassin plugin for Sylpheed Claws GTK2 sylpheed-claws-gtk2-trayicon - Notification area plugin for Sylpheed Claws GTK2 Closes: 340729 Changes: sylpheed-claws-gtk2 (1.9.100-1.1) unstable; urgency=low . * Non-maintainer upload with permission of the maintainer. * Use -Wl,--as-needed when linking, to prevent sylpheed-claws from picking up dependencies on a large number of dependencies it doesn't use; this appears to be the only reasonable way to drop these dependencies when using libtool convenience libraries. Closes: #340729. Files: bfce62a245359b0df907f343c500f39f 1388 mail optional sylpheed-claws-gtk2_1.9.100-1.1.dsc a785795b00fd95a6824916683fee0830 30722 mail optional sylpheed-claws-gtk2_1.9.100-1.1.diff.gz e153d3da3969d9805ce910ba5b40eeae 1043580 mail optional sylpheed-claws-gtk2_1.9.100-1.1_i386.deb 8ad9f49410d2b837a55444565047993d 155112 devel optional libsylpheed-claws-gtk2-dev_1.9.100-1.1_i386.deb aeaeb9ad48f6c8fca851ad41aa2bfc56 59236 mail optional sylpheed-claws-gtk2-plugins_1.9.100-1.1_all.deb fe5241b48447ffc05247dfadad9011d9 67946 mail optional sylpheed-claws-gtk2-clamav_1.9.100-1.1_i386.deb d1dc850b85e19fc8ef9810cfffe04407 64708 mail optional sylpheed-claws-gtk2-dillo-viewer_1.9.100-1.1_i386.deb 552beb5ba7c299c7f989c01de895e19f 76106 mail optional sylpheed-claws-gtk2-spamassassin_1.9.100-1.1_i386.deb 853932beb9cba4b97b7e023ccd8f285b 69200 mail optional sylpheed-claws-gtk2-trayicon_1.9.100-1.1_i386.deb aa44fae4c156391b741c9cd34838e24d 82828 mail optional sylpheed-claws-gtk2-pgpmime_1.9.100-1.1_i386.deb fbdc6f9ac9f8910c970735efe63e136b 66760 mail optional sylpheed-claws-gtk2-pgpinline_1.9.100-1.1_i386.deb f39419be26031fd762af4e103cd0e058 1224800 mail optional sylpheed-claws-gtk2-i18n_1.9.100-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhw2bKN6ufymYLloRAuEAAJ9LgwZz3Xt/MC76R8xbC8MzWhrdQQCgv6V8 mwtQ0Mz0sYjcoMEccni8T+0= =RjPl -END PGP SIGNATURE- Accepted: libsylpheed-claws-gtk2-dev_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/libsylpheed-claws-gtk2-dev_1.9.100-1.1_i386.deb sylpheed-claws-gtk2-clamav_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-clamav_1.9.100-1.1_i386.deb sylpheed-claws-gtk2-dillo-viewer_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-dillo-viewer_1.9.100-1.1_i386.deb sylpheed-claws-gtk2-i18n_1.9.100-1.1_all.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-i18n_1.9.100-1.1_all.deb sylpheed-claws-gtk2-pgpinline_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-pgpinline_1.9.100-1.1_i386.deb sylpheed-claws-gtk2-pgpmime_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-pgpmime_1.9.100-1.1_i386.deb sylpheed-claws-gtk2-plugins_1.9.100-1.1_all.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-plugins_1.9.100-1.1_all.deb sylpheed-claws-gtk2-spamassassin_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-spamassassin_1.9.100-1.1_i386.deb sylpheed-claws-gtk2-trayicon_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2-trayicon_1.9.100-1.1_i386.deb sylpheed-claws-gtk2_1.9.100-1.1.diff.gz to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2_1.9.100-1.1.diff.gz sylpheed-claws-gtk2_1.9.100-1.1.dsc to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2_1.9.100-1.1.dsc sylpheed-claws-gtk2_1.9.100-1.1_i386.deb to pool/main/s/sylpheed-claws-gtk2/sylpheed-claws-gtk2_1.9.100-1.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted glunarclock 1:0.32.4-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Nov 2005 13:24:25 + Source: glunarclock Binary: glunarclock Architecture: source i386 Version: 1:0.32.4-4 Distribution: unstable Urgency: low Maintainer: Yoshito Komatsu [EMAIL PROTECTED] Changed-By: Yoshito Komatsu [EMAIL PROTECTED] Description: glunarclock - GNOME Lunar Clock Applet Closes: 340520 Changes: glunarclock (1:0.32.4-4) unstable; urgency=low . * Use dh_gconf, closes: #340520 * Update DH_COMPAT to 5. Files: ca0404e3a362bb683a6d20873d4bcea1 695 gnome optional glunarclock_0.32.4-4.dsc d6e4558781937ed660c6b832e31dd0fb 28815 gnome optional glunarclock_0.32.4-4.diff.gz fbffb4e2ab9f2bf8c0e9879be7908ac4 149050 gnome optional glunarclock_0.32.4-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh1WOIVYdRNEsSJ0RAsgkAJ9Y5TiG6UKPCKIxWMwIVsdOKgAdCwCeOab/ 2+WOiKWa2zf9YEjSRWPGd34= =jaUv -END PGP SIGNATURE- Accepted: glunarclock_0.32.4-4.diff.gz to pool/main/g/glunarclock/glunarclock_0.32.4-4.diff.gz glunarclock_0.32.4-4.dsc to pool/main/g/glunarclock/glunarclock_0.32.4-4.dsc glunarclock_0.32.4-4_i386.deb to pool/main/g/glunarclock/glunarclock_0.32.4-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dh-make-php 0.0.12-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 11:04:57 +0100 Source: dh-make-php Binary: dh-make-php Architecture: source all Version: 0.0.12-1 Distribution: unstable Urgency: low Maintainer: Uwe Steinmann [EMAIL PROTECTED] Changed-By: Uwe Steinmann [EMAIL PROTECTED] Description: dh-make-php - Creating debian source packages for pear and pecl extensions Closes: 330718 Changes: dh-make-php (0.0.12-1) unstable; urgency=low . * New upstream release * replaced backticks by $(shell ) in template rules files (Closes: #330718) Files: ecb8a750bb8a914f0b1d2edc4d0d502d 620 web optional dh-make-php_0.0.12-1.dsc e437552ed5dbab6a7c47a9043c612ca6 17694 web optional dh-make-php_0.0.12.orig.tar.gz 489fa76a3afe960017290b6c78fe1e14 2218 web optional dh-make-php_0.0.12-1.diff.gz 6f6fdd98d6fa043784e97e9f740d5b0d 19246 web optional dh-make-php_0.0.12-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhuNIih2Zvw18pwERAiZIAKCWL5+lCRUg43i0VKrH3TA8b9BJKwCfTzOD wqAFgezeKG82hWukMx338C0= =3xT0 -END PGP SIGNATURE- Accepted: dh-make-php_0.0.12-1.diff.gz to pool/main/d/dh-make-php/dh-make-php_0.0.12-1.diff.gz dh-make-php_0.0.12-1.dsc to pool/main/d/dh-make-php/dh-make-php_0.0.12-1.dsc dh-make-php_0.0.12-1_all.deb to pool/main/d/dh-make-php/dh-make-php_0.0.12-1_all.deb dh-make-php_0.0.12.orig.tar.gz to pool/main/d/dh-make-php/dh-make-php_0.0.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pilot-link 0.11.8-0.12.0-pre4-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 15:55:05 +0100 Source: pilot-link Binary: libpisock9 libpda-pilot-perl pilot-link libpisync0 python-pisock libpisock-dev Architecture: source i386 Version: 0.11.8-0.12.0-pre4-3 Distribution: experimental Urgency: low Maintainer: Ludovic Rousseau [EMAIL PROTECTED] Changed-By: Ludovic Rousseau [EMAIL PROTECTED] Description: libpda-pilot-perl - Perl module to communicate with a PalmOS PDA libpisock-dev - development files for communicating with a PalmOS PDA libpisock9 - library for communicating with a PalmOS PDA libpisync0 - synchronization library for PalmOS devices pilot-link - tools to communicate with a PalmOS PDA python-pisock - Python module to communicate with PalmOS PDA Closes: 340594 Changes: pilot-link (0.11.8-0.12.0-pre4-3) experimental; urgency=low . * debian/rules: Closes: #340594 python-pisock: missing python bindings . add --with-python to ./configure to build the Python bindings. . call python setup.py install * debian/compat: 3 - 4 Files: ff8eb102108c34ef898437694c5848de 785 otherosfs optional pilot-link_0.11.8-0.12.0-pre4-3.dsc 5fd610b010e8c7829fbc9360d34b8c6c 11496 otherosfs optional pilot-link_0.11.8-0.12.0-pre4-3.diff.gz 66e8ce2c7609b823958899e4a8acc739 90998 libs optional libpisock9_0.11.8-0.12.0-pre4-3_i386.deb df2a907a730895a20199b54cbb2d9692 149124 libdevel extra libpisock-dev_0.11.8-0.12.0-pre4-3_i386.deb 18efdb661fadfcd68529afabb7c991d3 109706 perl extra libpda-pilot-perl_0.11.8-0.12.0-pre4-3_i386.deb 38f73ce8b3adfe9cf415895c4fbe98c7 605360 otherosfs optional pilot-link_0.11.8-0.12.0-pre4-3_i386.deb af51faba073a7ba7efb3202a28b215ce 14896 libs optional libpisync0_0.11.8-0.12.0-pre4-3_i386.deb ef60d9ae8f4869396c7adf0b4a600b31 83428 python extra python-pisock_0.11.8-0.12.0-pre4-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhyhCP0qKj+B/HPkRAk1xAKCOXOyQ3WZm+IByByLvx2JA+ZM8uACfecB1 XWIBGXQcF9w4+CBDfkt4MNY= =rR9x -END PGP SIGNATURE- Accepted: libpda-pilot-perl_0.11.8-0.12.0-pre4-3_i386.deb to pool/main/p/pilot-link/libpda-pilot-perl_0.11.8-0.12.0-pre4-3_i386.deb libpisock-dev_0.11.8-0.12.0-pre4-3_i386.deb to pool/main/p/pilot-link/libpisock-dev_0.11.8-0.12.0-pre4-3_i386.deb libpisock9_0.11.8-0.12.0-pre4-3_i386.deb to pool/main/p/pilot-link/libpisock9_0.11.8-0.12.0-pre4-3_i386.deb libpisync0_0.11.8-0.12.0-pre4-3_i386.deb to pool/main/p/pilot-link/libpisync0_0.11.8-0.12.0-pre4-3_i386.deb pilot-link_0.11.8-0.12.0-pre4-3.diff.gz to pool/main/p/pilot-link/pilot-link_0.11.8-0.12.0-pre4-3.diff.gz pilot-link_0.11.8-0.12.0-pre4-3.dsc to pool/main/p/pilot-link/pilot-link_0.11.8-0.12.0-pre4-3.dsc pilot-link_0.11.8-0.12.0-pre4-3_i386.deb to pool/main/p/pilot-link/pilot-link_0.11.8-0.12.0-pre4-3_i386.deb python-pisock_0.11.8-0.12.0-pre4-3_i386.deb to pool/main/p/pilot-link/python-pisock_0.11.8-0.12.0-pre4-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mail-expire 0.6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Nov 2005 19:22:09 +0100 Source: mail-expire Binary: mail-expire Architecture: source all Version: 0.6 Distribution: unstable Urgency: low Maintainer: Eduard Bloch [EMAIL PROTECTED] Changed-By: Eduard Bloch [EMAIL PROTECTED] Description: mail-expire - Utility to extract outdated messages from mbox files Changes: mail-expire (0.6) unstable; urgency=low . * making code more robust: using Getopt for arguments, Mail::Mbox::MessageParser for input reading, and strict * diff size calculation removed, was incorrect anyways * various updates, Standards-Version, debhelper level Files: 29ee35ba2f1fddb2064b0d89eee00824 503 utils optional mail-expire_0.6.dsc 999cdf560cdc557abf3b6768e72902f6 7149 utils optional mail-expire_0.6.tar.gz 0ed2f1583026bbbe290c9995c3e64e8d 6546 utils optional mail-expire_0.6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhzPl4QZIHu3wCMURAoleAJ0cRx/b+csuQY1YZ/2bIn4oZ+3H7QCeOQLF rAyiUuAszkOho8PJGNFyGew= =xOOl -END PGP SIGNATURE- Accepted: mail-expire_0.6.dsc to pool/main/m/mail-expire/mail-expire_0.6.dsc mail-expire_0.6.tar.gz to pool/main/m/mail-expire/mail-expire_0.6.tar.gz mail-expire_0.6_all.deb to pool/main/m/mail-expire/mail-expire_0.6_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcommandline-ruby 0.7.10-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 23 Nov 2005 11:49:26 + Source: libcommandline-ruby Binary: libcommandline-ruby libcommandline-ruby1.8 Architecture: source all Version: 0.7.10-2 Distribution: unstable Urgency: low Maintainer: Esteban Manchado Velázquez [EMAIL PROTECTED] Changed-By: Esteban Manchado Velázquez [EMAIL PROTECTED] Description: libcommandline-ruby - Ruby library to write command-line applications libcommandline-ruby1.8 - Ruby library to write command-line applications Closes: 340376 Changes: libcommandline-ruby (0.7.10-2) unstable; urgency=low . * The how could you? release. * Added mandatory field Files in the doc-base files (Closes: #340376). Files: 5fa97ad15f3d71913655b21cb7143b45 684 devel optional libcommandline-ruby_0.7.10-2.dsc 2bb2a643434a2a99900426926becbff4 10189 devel optional libcommandline-ruby_0.7.10-2.diff.gz c1efc003ef601263c6b84fb4abe5b5bb 5904 devel optional libcommandline-ruby_0.7.10-2_all.deb b27714aa37c734abb58ee34dc868fadc 36838 devel optional libcommandline-ruby1.8_0.7.10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDhz5+hYgK5b1UDsERAotMAJ9GwcabIadtAG0PHZfCpX8t9fNQWwCfZENu NR5x9S11o1tHdIjnrI99BSw= =5jOE -END PGP SIGNATURE- Accepted: libcommandline-ruby1.8_0.7.10-2_all.deb to pool/main/libc/libcommandline-ruby/libcommandline-ruby1.8_0.7.10-2_all.deb libcommandline-ruby_0.7.10-2.diff.gz to pool/main/libc/libcommandline-ruby/libcommandline-ruby_0.7.10-2.diff.gz libcommandline-ruby_0.7.10-2.dsc to pool/main/libc/libcommandline-ruby/libcommandline-ruby_0.7.10-2.dsc libcommandline-ruby_0.7.10-2_all.deb to pool/main/libc/libcommandline-ruby/libcommandline-ruby_0.7.10-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted revelation 0.4.5-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 13 Sep 2005 12:29:27 +0200 Source: revelation Binary: revelation Architecture: source i386 Version: 0.4.5-2 Distribution: unstable Urgency: low Maintainer: Stefan Voelkel [EMAIL PROTECTED] Description: revelation - GNOME2 Password manager Changes: revelation (0.4.5-2) unstable; urgency=low . * Fix gnome.applet dependency Files: f7d134d8c7bc79cb09190a454e561ea7 884 gnome optional revelation_0.4.5-2.dsc 49f58630d234c4980ecbd8d40c6fd3ff 514714 gnome optional revelation_0.4.5.orig.tar.gz 8885eb3d95935b958e9d5678ae587fb6 4746 gnome optional revelation_0.4.5-2.diff.gz 52f9d425db7c556b4718b92cbad9a08e 343276 gnome optional revelation_0.4.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh0QCntB470s6E1wRAl74AJ9h6wCNpbL88Np0Y/5AozrFpffSgQCdE7/h AhwutU2u8UnETwmjn5FxuAo= =Qaaw -END PGP SIGNATURE- Accepted: revelation_0.4.5-2.diff.gz to pool/main/r/revelation/revelation_0.4.5-2.diff.gz revelation_0.4.5-2.dsc to pool/main/r/revelation/revelation_0.4.5-2.dsc revelation_0.4.5-2_i386.deb to pool/main/r/revelation/revelation_0.4.5-2_i386.deb revelation_0.4.5.orig.tar.gz to pool/main/r/revelation/revelation_0.4.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted postgrey 1.23-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 18:20:49 +0100 Source: postgrey Binary: postgrey Architecture: source all Version: 1.23-1 Distribution: unstable Urgency: low Maintainer: Adrian von Bidder [EMAIL PROTECTED] Changed-By: Adrian von Bidder [EMAIL PROTECTED] Description: postgrey - greylisting implementation for Postfix Closes: 340140 Changes: postgrey (1.23-1) unstable; urgency=low . * New upstream version - include arcor in whitelist (closes: #340140) Files: 0a34480041f0506615b789de838568e0 679 mail optional postgrey_1.23-1.dsc d5214a0dbca6872c5be426d0ffde534d 26622 mail optional postgrey_1.23.orig.tar.gz 9cacb33db920e369630d211812c6f522 15586 mail optional postgrey_1.23-1.diff.gz 6505575a20c47ab01ef664128e91955f 44534 mail optional postgrey_1.23-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: get my key from http://fortytwo.ch/gpg/92082481 iEYEARECAAYFAkOHS3sACgkQi6Qxi+Wn99bGWQCfdQYvWEOvWptTWeswRn7Xx3gP 3eAAoKHe+9QB6bZIALdmhiUdtp/aStXV =Z19m -END PGP SIGNATURE- Accepted: postgrey_1.23-1.diff.gz to pool/main/p/postgrey/postgrey_1.23-1.diff.gz postgrey_1.23-1.dsc to pool/main/p/postgrey/postgrey_1.23-1.dsc postgrey_1.23-1_all.deb to pool/main/p/postgrey/postgrey_1.23-1_all.deb postgrey_1.23.orig.tar.gz to pool/main/p/postgrey/postgrey_1.23.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cl-sql 3.4.7-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 10:41:34 -0700 Source: cl-sql Binary: cl-sql-sqlite3 cl-sql-oracle cl-sql-aodbc cl-sql-postgresql-socket cl-sql-postgresql cl-sql-odbc cl-sql cl-sql-uffi cl-sql-tests cl-sql-sqlite cl-sql-mysql Architecture: source all i386 Version: 3.4.7-1 Distribution: unstable Urgency: low Maintainer: Kevin M. Rosenberg [EMAIL PROTECTED] Changed-By: Kevin M. Rosenberg [EMAIL PROTECTED] Description: cl-sql - SQL Interface for Common Lisp cl-sql-aodbc - CLSQL database backend, AODBC cl-sql-mysql - CLSQL database backend, MySQL cl-sql-odbc - CLSQL database backend, ODBC cl-sql-oracle - CLSQL database backend, Oracle cl-sql-postgresql - CLSQL database backend, PostgreSQL cl-sql-postgresql-socket - CLSQL database backend, PostgreSQL cl-sql-sqlite - CLSQL database backend, SQLite cl-sql-sqlite3 - CLSQL database backend, SQLite3 cl-sql-tests - Testing suite for CLSQL cl-sql-uffi - Common UFFI functions for CLSQL database backends Changes: cl-sql (3.4.7-1) unstable; urgency=low . * New upstream Files: ec349ec78ad995b03bbc7db712f076f9 819 devel extra cl-sql_3.4.7-1.dsc f8704032148523c646a8b7879d46823c 702968 devel extra cl-sql_3.4.7.orig.tar.gz 1d23aa9366dca777dd6ee80a1f201d1f 11067 devel extra cl-sql_3.4.7-1.diff.gz 2be6c6a795446613d5df44c09e76d7f4 489926 devel extra cl-sql_3.4.7-1_all.deb 38dfd553ca293e9653183281c35d2980 35780 devel extra cl-sql-aodbc_3.4.7-1_all.deb de4c9c20730f6bdcff3a70afa86be0c4 61754 devel extra cl-sql-odbc_3.4.7-1_all.deb 1e44be04aec3e1dff368adf8d462e6d0 40546 devel extra cl-sql-postgresql_3.4.7-1_all.deb 74d27f9b4ec85e8957bfb5f0bd859fd0 44688 devel extra cl-sql-postgresql-socket_3.4.7-1_all.deb f7c5f1e9dfca7a8f21932440933ea9fc 40414 devel extra cl-sql-sqlite_3.4.7-1_all.deb dae643e1ab4656c75ec9f564e0680384 41180 devel extra cl-sql-sqlite3_3.4.7-1_all.deb 997d904e64a3d19ad91e93a58d80e7fd 56854 contrib/devel extra cl-sql-oracle_3.4.7-1_all.deb 14002d4f069717023044592ec984bab8 59008 devel extra cl-sql-tests_3.4.7-1_all.deb ef578b9bf7aac485a3793a5c2a9f39ee 39178 devel extra cl-sql-uffi_3.4.7-1_i386.deb b8bf7e75b798b9fc8637b5e56165bdd5 49590 devel extra cl-sql-mysql_3.4.7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh00wES7N8sSjgj4RAli+AJ9iKIaAT0DXsO5I26dUywdnSaFioQCePQaw Mf+RcvEg9oU4AqzjwjPpC5s= =4LIx -END PGP SIGNATURE- Accepted: cl-sql-aodbc_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-aodbc_3.4.7-1_all.deb cl-sql-mysql_3.4.7-1_i386.deb to pool/main/c/cl-sql/cl-sql-mysql_3.4.7-1_i386.deb cl-sql-odbc_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-odbc_3.4.7-1_all.deb cl-sql-oracle_3.4.7-1_all.deb to pool/contrib/c/cl-sql/cl-sql-oracle_3.4.7-1_all.deb cl-sql-postgresql-socket_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql-socket_3.4.7-1_all.deb cl-sql-postgresql_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-postgresql_3.4.7-1_all.deb cl-sql-sqlite3_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite3_3.4.7-1_all.deb cl-sql-sqlite_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-sqlite_3.4.7-1_all.deb cl-sql-tests_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql-tests_3.4.7-1_all.deb cl-sql-uffi_3.4.7-1_i386.deb to pool/main/c/cl-sql/cl-sql-uffi_3.4.7-1_i386.deb cl-sql_3.4.7-1.diff.gz to pool/main/c/cl-sql/cl-sql_3.4.7-1.diff.gz cl-sql_3.4.7-1.dsc to pool/main/c/cl-sql/cl-sql_3.4.7-1.dsc cl-sql_3.4.7-1_all.deb to pool/main/c/cl-sql/cl-sql_3.4.7-1_all.deb cl-sql_3.4.7.orig.tar.gz to pool/main/c/cl-sql/cl-sql_3.4.7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted udev 0.076-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Nov 2005 20:54:23 +0100 Source: udev Binary: udev udev-udeb Architecture: source i386 Version: 0.076-1 Distribution: unstable Urgency: medium Maintainer: Marco d'Itri [EMAIL PROTECTED] Changed-By: Marco d'Itri [EMAIL PROTECTED] Description: udev - /dev/ and hotplug management daemon udev-udeb - /dev/ and hotplug management daemon (udeb) Closes: 339569 339982 340100 340202 Changes: udev (0.076-1) unstable; urgency=medium . * New upstream release. * Conflicts with initramfs-tools 0.39. (Closes: #339569) * ide.agent: fixed support for devices beyond hdf. (Closes: #339982) * Rearranged the package scripts to kill/restart udevd only in postinst. * Unconditionally oad the input *dev modules for kernels = 2.6.15 too, to work around missing $MODALIAS support in the kernel and lack of a working input.agent script. (Closes: #340202) * Install hotplug.functions in the udeb. (Closes: #340100) * Added an input.agent script, not yet enabled. Files: f9c6216b71d0fd9deba0ec6ed7d63d3e 593 admin optional udev_0.076-1.dsc 0d2a2e0f5db9f5f91685866a4d4f2fc4 222191 admin optional udev_0.076.orig.tar.gz 5e8c4fb838bcce7bfaa4f1f4b02a9cc4 45431 admin optional udev_0.076-1.diff.gz 27f0a71e45f67af0db2c0bda2e1bef28 279720 admin optional udev_0.076-1_i386.deb fa09918fb6d7f723648651a064eacb82 51332 debian-installer optional udev-udeb_0.076-1_i386.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh1CQFGfw2OHuP7ERAk8XAJ4pwZCf33psO80Fj6YIPKfWmrD22ACgpbgn 8q/P0BTjaN9CUQ6aV/BNIo4= =2kLz -END PGP SIGNATURE- Accepted: udev-udeb_0.076-1_i386.udeb to pool/main/u/udev/udev-udeb_0.076-1_i386.udeb udev_0.076-1.diff.gz to pool/main/u/udev/udev_0.076-1.diff.gz udev_0.076-1.dsc to pool/main/u/udev/udev_0.076-1.dsc udev_0.076-1_i386.deb to pool/main/u/udev/udev_0.076-1_i386.deb udev_0.076.orig.tar.gz to pool/main/u/udev/udev_0.076.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted speex 1.1.11-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 11:29:35 -0500 Source: speex Binary: speex-doc libspeex-dev speex libspeex1 Architecture: source all i386 Version: 1.1.11-1 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team [EMAIL PROTECTED] Changed-By: A. Maitland Bottoms [EMAIL PROTECTED] Description: libspeex-dev - The Speex Speech Codec libspeex1 - The Speex Speech Codec speex - The Speex Speech Codec speex-doc - Documentation for speex Changes: speex (1.1.11-1) unstable; urgency=low . * New upstream release Files: eafb43ab38ddc49eb4075baa9f0793e6 867 sound optional speex_1.1.11-1.dsc 3e0a9e020d2f496940cc2283ed6fa349 720481 sound optional speex_1.1.11.orig.tar.gz af0e0732c88d2b1b5159a8c27abffb6d 15720 sound optional speex_1.1.11-1.diff.gz d23fb3d4297a0858393122759462ba54 1109016 doc optional speex-doc_1.1.11-1_all.deb c6bc1a6099ed46d0757212908c1bf351 24388 sound optional speex_1.1.11-1_i386.deb ae3c1d7dd6a581a0927a8c47e9b3a325 68960 libs optional libspeex1_1.1.11-1_i386.deb a2c71581e105955c41f0500c39c2324a 86790 libdevel optional libspeex-dev_1.1.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh0bikwbJvNrxBUwRAtifAJ9t9N3i7bDIqjTnP3254eRDq+papACffK4J 507LtJpkG9FUnb9WzP6KRFU= =Jiqo -END PGP SIGNATURE- Accepted: libspeex-dev_1.1.11-1_i386.deb to pool/main/s/speex/libspeex-dev_1.1.11-1_i386.deb libspeex1_1.1.11-1_i386.deb to pool/main/s/speex/libspeex1_1.1.11-1_i386.deb speex-doc_1.1.11-1_all.deb to pool/main/s/speex/speex-doc_1.1.11-1_all.deb speex_1.1.11-1.diff.gz to pool/main/s/speex/speex_1.1.11-1.diff.gz speex_1.1.11-1.dsc to pool/main/s/speex/speex_1.1.11-1.dsc speex_1.1.11-1_i386.deb to pool/main/s/speex/speex_1.1.11-1_i386.deb speex_1.1.11.orig.tar.gz to pool/main/s/speex/speex_1.1.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted azureus 2.3.0.6-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 11:06:17 -0700 Source: azureus Binary: azureus Architecture: source all Version: 2.3.0.6-1 Distribution: unstable Urgency: low Maintainer: Shaun Jackman [EMAIL PROTECTED] Changed-By: Shaun Jackman [EMAIL PROTECTED] Description: azureus- BitTorrent client Changes: azureus (2.3.0.6-1) unstable; urgency=low . * New upstream release. Files: c1742790defda157e6329c58f68332f4 699 contrib/net optional azureus_2.3.0.6-1.dsc 34c865b58f9c8458420ab86a82b2337a 3079043 contrib/net optional azureus_2.3.0.6.orig.tar.gz 14cb586d6420a38083382dd88f282669 6058 contrib/net optional azureus_2.3.0.6-1.diff.gz 4ed83eaa6e8ebff2c8bee5559662439d 5039646 contrib/net optional azureus_2.3.0.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDh1k3vFdYF1IwUUoRAhxJAKDl8G6r0cMrgAAnGz46mHhF/GCAjQCfTNCL K2B6ZnMqPqpsCvwH+LdeSVo= =qszn -END PGP SIGNATURE- Accepted: azureus_2.3.0.6-1.diff.gz to pool/contrib/a/azureus/azureus_2.3.0.6-1.diff.gz azureus_2.3.0.6-1.dsc to pool/contrib/a/azureus/azureus_2.3.0.6-1.dsc azureus_2.3.0.6-1_all.deb to pool/contrib/a/azureus/azureus_2.3.0.6-1_all.deb azureus_2.3.0.6.orig.tar.gz to pool/contrib/a/azureus/azureus_2.3.0.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xmms-crossfade 0.3.8-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 19:37:56 +0100 Source: xmms-crossfade Binary: xmms-crossfade Architecture: source i386 Version: 0.3.8-2 Distribution: unstable Urgency: low Maintainer: Florian Ernst [EMAIL PROTECTED] Changed-By: Florian Ernst [EMAIL PROTECTED] Description: xmms-crossfade - XMMS Plugin for Crossfading / Continuous Output Changes: xmms-crossfade (0.3.8-2) unstable; urgency=low . * Prune unneeded Depends via specific make flags * Upgrade debhelper compatibility level * debian/watch: updated Files: 858dc2f0fe18f6b1d917c7013f710d71 631 sound optional xmms-crossfade_0.3.8-2.dsc ddaa92fec8ec476afcc558c70a820ed6 4382 sound optional xmms-crossfade_0.3.8-2.diff.gz 4badbaa54a702d010e6a634398a29b62 91674 sound optional xmms-crossfade_0.3.8-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh1tXs3U+TVFLPnwRArHyAJ95Q6b96g8nt6O4DrtsginGEWa6PwCggR2h mizfzEkBRpgkIA2Y1qtUDNw= =toB2 -END PGP SIGNATURE- Accepted: xmms-crossfade_0.3.8-2.diff.gz to pool/main/x/xmms-crossfade/xmms-crossfade_0.3.8-2.diff.gz xmms-crossfade_0.3.8-2.dsc to pool/main/x/xmms-crossfade/xmms-crossfade_0.3.8-2.dsc xmms-crossfade_0.3.8-2_i386.deb to pool/main/x/xmms-crossfade/xmms-crossfade_0.3.8-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cdrdao 1:1.2.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 19:26:09 + Source: cdrdao Binary: cdrdao Architecture: source i386 Version: 1:1.2.1-2 Distribution: unstable Urgency: low Maintainer: Andrew Suffield [EMAIL PROTECTED] Changed-By: Andrew Suffield [EMAIL PROTECTED] Description: cdrdao - Disk-At-Once (DAO) recording of audio and data CD-Rs/CD-RWs Closes: 340691 Changes: cdrdao (1:1.2.1-2) unstable; urgency=low . * Fix stupid bug that makes the package impossible to build. So the question is, why did it build for me? (closes: #340691) Files: 5e9e6be59a68e1b610e8f298771aac53 588 otherosfs optional cdrdao_1.2.1-2.dsc 92a911e665291e9a3d78aaa07e25c6b4 26432 otherosfs optional cdrdao_1.2.1-2.diff.gz dd01d5849c615609a5653fffc694c99d 416954 otherosfs optional cdrdao_1.2.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh2Z1lpK98RSteX8RApvbAJ9bzqqQN6jjnGWqPnkUo4LcLqalTwCeMj8p tIKNDAvmaH9u+ioRnUofluI= =bLNq -END PGP SIGNATURE- Accepted: cdrdao_1.2.1-2.diff.gz to pool/main/c/cdrdao/cdrdao_1.2.1-2.diff.gz cdrdao_1.2.1-2.dsc to pool/main/c/cdrdao/cdrdao_1.2.1-2.dsc cdrdao_1.2.1-2_i386.deb to pool/main/c/cdrdao/cdrdao_1.2.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted beagle 0.1.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 20:28:45 +0100 Source: beagle Binary: beagle Architecture: source i386 Version: 0.1.2-2 Distribution: unstable Urgency: low Maintainer: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Changed-By: Jose Carlos Garcia Sogo [EMAIL PROTECTED] Description: beagle - indexing and search tool for your personal data Closes: 331085 340550 340663 Changes: beagle (0.1.2-2) unstable; urgency=low . * Compiled with unstable dependencies (Closes: #340550, #340663, #331085) Files: 2168c0060e6dbefc9e0e48d0610f1a30 892 gnome optional beagle_0.1.2-2.dsc b0272461d16080654754564abd36191e 5502 gnome optional beagle_0.1.2-2.diff.gz b03d7cc2dc617d393dce0d0aebb7fc6a 789642 gnome optional beagle_0.1.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh4WJS+BYJZB4jhERAvCYAJ4lOM84EBaJrwUrJyKUIUNr3LY8pwCgoDRT JTt2B2JR2Y95R1MbuOKR+5c= =moWE -END PGP SIGNATURE- Accepted: beagle_0.1.2-2.diff.gz to pool/main/b/beagle/beagle_0.1.2-2.diff.gz beagle_0.1.2-2.dsc to pool/main/b/beagle/beagle_0.1.2-2.dsc beagle_0.1.2-2_i386.deb to pool/main/b/beagle/beagle_0.1.2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zsh 4.2.5-24 (source sparc all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 10:30:49 -0500 Source: zsh Binary: zsh zsh-static zsh-doc Architecture: source sparc all Version: 4.2.5-24 Distribution: unstable Urgency: low Maintainer: Clint Adams [EMAIL PROTECTED] Changed-By: Clint Adams [EMAIL PROTECTED] Description: zsh- A shell with lots of features zsh-doc- zsh documentation - info/HTML format zsh-static - A shell with lots of features (static link) Changes: zsh (4.2.5-24) unstable; urgency=low . * Add completion for dchroot. * Fixes/improvements for baz, bzr, date, ssh, subversion, gv. Files: fdd45de30768bb4fcebf41e5cb08bbc5 692 shells optional zsh_4.2.5-24.dsc c4cd3323d59b75f34fa9632a1223f96f 349047 shells optional zsh_4.2.5-24.diff.gz 166922a2e165d90d8185b8c0407be918 673644 shells optional zsh-doc_4.2.5-24_all.deb bdc5152861ff2d39f2531cac9d1a21c5 2087580 shells optional zsh_4.2.5-24_sparc.deb 83fb52640a9aa1c10906ba01222a3bf4 795194 shells optional zsh-static_4.2.5-24_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Debian! iD8DBQFDh2+H5m0u66uWM3ARAiDLAJ91ew4j8lYQwxw2r1ldJy2iXrgblwCfVw0r Ejbt1lZR+MXVa1KAgx+qNs8= =BIV+ -END PGP SIGNATURE- Accepted: zsh-doc_4.2.5-24_all.deb to pool/main/z/zsh/zsh-doc_4.2.5-24_all.deb zsh-static_4.2.5-24_sparc.deb to pool/main/z/zsh/zsh-static_4.2.5-24_sparc.deb zsh_4.2.5-24.diff.gz to pool/main/z/zsh/zsh_4.2.5-24.diff.gz zsh_4.2.5-24.dsc to pool/main/z/zsh/zsh_4.2.5-24.dsc zsh_4.2.5-24_sparc.deb to pool/main/z/zsh/zsh_4.2.5-24_sparc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted newt 0.52.1-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 20:50:49 + Source: newt Binary: libnewt0.52 libnewt-dev libnewt-pic newt-tcl whiptail python-newt Architecture: source i386 Version: 0.52.1-3 Distribution: experimental Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: libnewt-dev - Developer's toolkit for newt windowing library libnewt-pic - Not Erik's Windowing Toolkit, shared library subset kit libnewt0.52 - Not Erik's Windowing Toolkit - text mode windowing with slang newt-tcl - A newt module for Tcl python-newt - A NEWT module for Python whiptail - Displays user-friendly dialog boxes from shell scripts Closes: 340366 340650 Changes: newt (0.52.1-3) experimental; urgency=low . * New Bengali translation by Progga. Closes: #340650. * snack.py: function EntryWindow now works with preset values for entries. Closes: #340366. Files: 4d711640ecac104ab750133ead7917b2 736 devel optional newt_0.52.1-3.dsc 463d1c8382f9e6b6b44a69fc5a28d7b3 60643 devel optional newt_0.52.1-3.diff.gz 5464fe3fbd0bbe27ca43458541628d90 59968 base required libnewt0.52_0.52.1-3_i386.deb 5f7c19d4b8ec7556f1a41c0b3d3f734f 81186 libdevel optional libnewt-dev_0.52.1-3_i386.deb 82d0509e5135e452c7c30b696d01e9ec 53748 libdevel extra libnewt-pic_0.52.1-3_i386.deb 7efae6f75c3ebc710f8ab23b05ed5eb4 26970 interpreters extra newt-tcl_0.52.1-3_i386.deb 574ffcc5932147051fe2647975938862 35628 python standard python-newt_0.52.1-3_i386.deb 905603aa4e1707928be17bee750e584b 32500 base important whiptail_0.52.1-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh3rbQTK/kCo4XFcRAliuAKCLeg4A9Q7EcQHh0pW0MQem9GKpPACgvAIl pt7mLXgMVTZP07PqFGM18+I= =sd7r -END PGP SIGNATURE- Accepted: libnewt-dev_0.52.1-3_i386.deb to pool/main/n/newt/libnewt-dev_0.52.1-3_i386.deb libnewt-pic_0.52.1-3_i386.deb to pool/main/n/newt/libnewt-pic_0.52.1-3_i386.deb libnewt0.52_0.52.1-3_i386.deb to pool/main/n/newt/libnewt0.52_0.52.1-3_i386.deb newt-tcl_0.52.1-3_i386.deb to pool/main/n/newt/newt-tcl_0.52.1-3_i386.deb newt_0.52.1-3.diff.gz to pool/main/n/newt/newt_0.52.1-3.diff.gz newt_0.52.1-3.dsc to pool/main/n/newt/newt_0.52.1-3.dsc python-newt_0.52.1-3_i386.deb to pool/main/n/newt/python-newt_0.52.1-3_i386.deb whiptail_0.52.1-3_i386.deb to pool/main/n/newt/whiptail_0.52.1-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted console-common 0.7.55 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 20:27:21 + Source: console-common Binary: dh-consoledata console-common Architecture: source all Version: 0.7.55 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: console-common - Basic infrastructure for text console configuration dh-consoledata - Debhelper-based script to help packaging console data file Closes: 340689 Changes: console-common (0.7.55) unstable; urgency=low . * Remove exits from /etc/init.d/keymap.sh so it can be sourced, as per policy. Closes: #340689. Files: 9b6ac0a2bcfd050a46a99716cae80003 621 utils important console-common_0.7.55.dsc bc74587c3f5748b65803232e2e7e574d 128586 utils important console-common_0.7.55.tar.gz d0ee9e5d3744a1cc1925925a88b16b40 119936 utils important console-common_0.7.55_all.deb 8ecf44900c04e9bd4e4c1ce8d1546fbc 89814 devel extra dh-consoledata_0.7.55_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh3WSQTK/kCo4XFcRAm0PAJ9EKJyDk18yhM/vSWlbeOcl5Ue9BgCfZ89O OlPZ5U1ED4IADxUSqoQTXnw= =M2vd -END PGP SIGNATURE- Accepted: console-common_0.7.55.dsc to pool/main/c/console-common/console-common_0.7.55.dsc console-common_0.7.55.tar.gz to pool/main/c/console-common/console-common_0.7.55.tar.gz console-common_0.7.55_all.deb to pool/main/c/console-common/console-common_0.7.55_all.deb dh-consoledata_0.7.55_all.deb to pool/main/c/console-common/dh-consoledata_0.7.55_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted evolution-sharp 0.10.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 23 Nov 2005 23:28:53 +0100
Source: evolution-sharp
Binary: libevolution-cil
Architecture: source i386
Version: 0.10.2-2
Distribution: unstable
Urgency: low
Maintainer: Jose Carlos Garcia Sogo [EMAIL PROTECTED]
Changed-By: Jose Carlos Garcia Sogo [EMAIL PROTECTED]
Description:
libevolution-cil - CLI bindings for Evolution
Changes:
evolution-sharp (0.10.2-2) unstable; urgency=low
.
* debian/control: added missing ${shlibs:Depends} and ${misc:Depends}
variables.
Files:
9c6763a93bfcb09dbe49ee62f4854191 824 libs optional evolution-sharp_0.10.2-2.dsc
81d96a4fa4683732143d84e6336f6b12 2085 libs optional
evolution-sharp_0.10.2-2.diff.gz
31c299243c33f6aade26ccffd4c11e3d 83404 libs optional
libevolution-cil_0.10.2-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDh4JES+BYJZB4jhERAvYsAKCpZqxh4bhsgRba+nT6/VANMJMW2gCfeDk+
QxZGE79afvQKNHPUI2KKM1Y=
=FZcu
-END PGP SIGNATURE-
Accepted:
evolution-sharp_0.10.2-2.diff.gz
to pool/main/e/evolution-sharp/evolution-sharp_0.10.2-2.diff.gz
evolution-sharp_0.10.2-2.dsc
to pool/main/e/evolution-sharp/evolution-sharp_0.10.2-2.dsc
libevolution-cil_0.10.2-2_i386.deb
to pool/main/e/evolution-sharp/libevolution-cil_0.10.2-2_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted k3b-i18n 0.12.8-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 12:11:56 -0500 Source: k3b-i18n Binary: k3b-i18n Architecture: source all Version: 0.12.8-1 Distribution: unstable Urgency: low Maintainer: Jean-Michel Kelbert [EMAIL PROTECTED] Changed-By: Francois Marier [EMAIL PROTECTED] Description: k3b-i18n - Internationalized (i18n) files for k3b Changes: k3b-i18n (0.12.8-1) unstable; urgency=low . * New upstream release Files: e62f0bffd77fc8e793d77df3649c669f 688 otherosfs optional k3b-i18n_0.12.8-1.dsc 8fb1c5afedf1ce0193d20e695225b911 5854461 otherosfs optional k3b-i18n_0.12.8.orig.tar.gz d30b8be359541f277f787cd0dc84fde4 25161 otherosfs optional k3b-i18n_0.12.8-1.diff.gz f640203e232bd694363ff85f93a93e51 4304804 otherosfs optional k3b-i18n_0.12.8-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh2kHScUZKBnQNIYRAnVIAJ9z8pW9umpyTJjdASrcIJFX55jCFACfZlz+ n3bAgUMk21MLd3AaFOo714s= =8FEq -END PGP SIGNATURE- Accepted: k3b-i18n_0.12.8-1.diff.gz to pool/main/k/k3b-i18n/k3b-i18n_0.12.8-1.diff.gz k3b-i18n_0.12.8-1.dsc to pool/main/k/k3b-i18n/k3b-i18n_0.12.8-1.dsc k3b-i18n_0.12.8-1_all.deb to pool/main/k/k3b-i18n/k3b-i18n_0.12.8-1_all.deb k3b-i18n_0.12.8.orig.tar.gz to pool/main/k/k3b-i18n/k3b-i18n_0.12.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted k3b 0.12.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 12:02:49 -0500 Source: k3b Binary: k3blibs k3blibs-dev k3b Architecture: source i386 Version: 0.12.8-1 Distribution: unstable Urgency: low Maintainer: Jean-Michel Kelbert [EMAIL PROTECTED] Changed-By: Francois Marier [EMAIL PROTECTED] Description: k3b- A sophisticated KDE CD burning application k3blibs- The KDE cd burning application library - runtime files k3blibs-dev - The KDE cd burning application library - development files Changes: k3b (0.12.8-1) unstable; urgency=low . * New upstream release (minor bug fixes): - Load index0 value in audio project. - Ignore case in cue files. - Fixed eject media setting. - Fixed a bug in the mp3 decoder which caused it to miss some perfectly valid mp3 files. * Updated README.Debian with a section about running k3b as root (thanks to Ross Boylan for the suggestion) Files: b98fb3679c011e330801882d3958e17d 876 otherosfs optional k3b_0.12.8-1.dsc e1d13df1914fdf4b02470f9e62997eb4 5230170 otherosfs optional k3b_0.12.8.orig.tar.gz f48d7380e3cc149320e7f61053745a37 11512 otherosfs optional k3b_0.12.8-1.diff.gz 55cf1c785c991ea7605ac63b2e19ea7e 3760418 otherosfs optional k3b_0.12.8-1_i386.deb dab6b2a7487471c375272fe323cb998d 118154 libdevel optional k3blibs-dev_0.12.8-1_i386.deb be5c2c0cd0e6267c90e9505d98b889fc 902014 libs optional k3blibs_0.12.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh2kNScUZKBnQNIYRAhaPAJkBuuKSvjPmx+nhBQUauBlXDL3SGACfYE9y 39JFDVCAmNtUR5mOQ1Q0ZVU= =cQCr -END PGP SIGNATURE- Accepted: k3b_0.12.8-1.diff.gz to pool/main/k/k3b/k3b_0.12.8-1.diff.gz k3b_0.12.8-1.dsc to pool/main/k/k3b/k3b_0.12.8-1.dsc k3b_0.12.8-1_i386.deb to pool/main/k/k3b/k3b_0.12.8-1_i386.deb k3b_0.12.8.orig.tar.gz to pool/main/k/k3b/k3b_0.12.8.orig.tar.gz k3blibs-dev_0.12.8-1_i386.deb to pool/main/k/k3b/k3blibs-dev_0.12.8-1_i386.deb k3blibs_0.12.8-1_i386.deb to pool/main/k/k3b/k3blibs_0.12.8-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted commons-httpclient 2.0.2-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 13:12:23 -0500 Source: commons-httpclient Binary: libcommons-httpclient-java-doc libcommons-httpclient-java Architecture: source all Version: 2.0.2-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Barry Hawkins [EMAIL PROTECTED] Description: libcommons-httpclient-java - A Java(TM) library for creating HTTP clients libcommons-httpclient-java-doc - Documentation for libcommons-httpclient-java Closes: 340308 Changes: commons-httpclient (2.0.2-2) unstable; urgency=low . * Provide non-version-specific symlink commons-httpclient.jar to commons-httpclient-2.0.2.jar per Debian Java Policy Section 2.4 (Closes: 340308) * Added additional doc-base entry to point to main section of Jakarta Commons HttpClient documentation in addition to the API Javadoc * Maintainer email address updated for Barry Hawkins * Upload sponsored by Petter Reinholdtsen Files: fb1bdaa251c252b69dc56f24a3220df9 841 libs optional commons-httpclient_2.0.2-2.dsc 31e6f1b5c8c5966b52fd2a65c7d9cef5 7526 libs optional commons-httpclient_2.0.2-2.diff.gz 6b3fdf7b8a9d8213d48c03f0e576a693 213100 libs optional libcommons-httpclient-java_2.0.2-2_all.deb 8163412de3e80683c32aa78f9c83231b 1491104 libs optional libcommons-httpclient-java-doc_2.0.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh4Mx20zMSyow1ykRAqk8AJwOSsBY0hotRbV6PIPs8+tbc5J4OQCg5VqZ U99eejdLjbU0qop42njzbRQ= =/rEs -END PGP SIGNATURE- Accepted: commons-httpclient_2.0.2-2.diff.gz to pool/main/c/commons-httpclient/commons-httpclient_2.0.2-2.diff.gz commons-httpclient_2.0.2-2.dsc to pool/main/c/commons-httpclient/commons-httpclient_2.0.2-2.dsc libcommons-httpclient-java-doc_2.0.2-2_all.deb to pool/main/c/commons-httpclient/libcommons-httpclient-java-doc_2.0.2-2_all.deb libcommons-httpclient-java_2.0.2-2_all.deb to pool/main/c/commons-httpclient/libcommons-httpclient-java_2.0.2-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted php-clamavlib 0.12a-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 20 Nov 2005 13:05:52 +0200 Source: php-clamavlib Binary: php4-clamavlib php5-clamavlib Architecture: source i386 Version: 0.12a-1 Distribution: unstable Urgency: low Maintainer: Jonas Genannt [EMAIL PROTECTED] Changed-By: Jonas Genannt [EMAIL PROTECTED] Description: php4-clamavlib - PHP ClamAV Lib - ClamAV Interface for PHP4 Scripts php5-clamavlib - PHP ClamAV Lib - ClamAV Interface for PHP5 Scripts Closes: 333984 334056 335520 335521 335532 338650 Changes: php-clamavlib (0.12a-1) unstable; urgency=low . * New upstream release. * Fix up dependency handling in debian/control and debian/rules to use shlibdeps instead of hardcoded library deps, phpapi-* instead of php4/php5 and misc:Depends instead of a hardcoded debconf dep. * Lower dependency on freshclam to a suggests, since it doesn't appear that we actually NEED it to work, it's just nice to have on the system. * Remove the bogus conflict/replace with php-clamav, since we don't actually have any file overlaps between our packages. * All changes by Adam Conrad [EMAIL PROTECTED] (QA Check) * Fix typo in templates. (Closes: #334056) (Christian Perrier) * Added: Czech translation (Closes: #333984) (Miroslav Kure) * Added: French translation (Aurelien Ricard) (Closes: #335532, #335521, #335520) * Added Swedish translation (Daniel Nylander) (Closes: #338650) Files: 225aef23bca0ed6268a41df703906908 656 web optional php-clamavlib_0.12a-1.dsc 80a8e32992c6bbda35cf2f1e3b25d2fc 7140 web optional php-clamavlib_0.12a.orig.tar.gz d5854dacd8d9ac841e0c82a528e2763b 4994 web optional php-clamavlib_0.12a-1.diff.gz 75d2187f37df2f1b38ae335596e4dc66 10720 web optional php4-clamavlib_0.12a-1_i386.deb 8a295589ab9d3fcb715d19c1fe20c904 10740 web optional php5-clamavlib_0.12a-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh2sRST77jl1k+HARAir2AKCxNXIO83IZVscTtBj6MrHE4NpqIwCfZNJ5 WnfYPMB7L4jsDRFGrQ40t74= =1NBK -END PGP SIGNATURE- Accepted: php-clamavlib_0.12a-1.diff.gz to pool/main/p/php-clamavlib/php-clamavlib_0.12a-1.diff.gz php-clamavlib_0.12a-1.dsc to pool/main/p/php-clamavlib/php-clamavlib_0.12a-1.dsc php-clamavlib_0.12a.orig.tar.gz to pool/main/p/php-clamavlib/php-clamavlib_0.12a.orig.tar.gz php4-clamavlib_0.12a-1_i386.deb to pool/main/p/php-clamavlib/php4-clamavlib_0.12a-1_i386.deb php5-clamavlib_0.12a-1_i386.deb to pool/main/p/php-clamavlib/php5-clamavlib_0.12a-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pinentry 0.7.2-3 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 21:12:12 +0100 Source: pinentry Binary: pinentry-doc pinentry-gtk pinentry-qt pinentry-gtk2 pinentry-curses Architecture: source i386 all Version: 0.7.2-3 Distribution: unstable Urgency: low Maintainer: Peter Eisentraut [EMAIL PROTECTED] Changed-By: Peter Eisentraut [EMAIL PROTECTED] Description: pinentry-curses - curses-based PIN or pass-phrase entry dialog for GnuPG pinentry-doc - documentation for pinentry packages pinentry-gtk - GTK+-based PIN or pass-phrase entry dialog for GnuPG pinentry-gtk2 - GTK+-2-based PIN or pass-phrase entry dialog for GnuPG pinentry-qt - Qt-based PIN or pass-phrase entry dialog for GnuPG Changes: pinentry (0.7.2-3) unstable; urgency=low . * Added linker option --as-needed Files: bef92d653d6d1164ebaafac07f83a387 727 utils optional pinentry_0.7.2-3.dsc 6c3a537eb1b613f59eff4dd0bf33ab26 5575 utils optional pinentry_0.7.2-3.diff.gz 99001f492484bfc67dd0c6ab67846777 30552 utils optional pinentry-doc_0.7.2-3_all.deb 17bba24be5f16d6e932cbf7fa6b6cb4b 39728 utils optional pinentry-curses_0.7.2-3_i386.deb 26862011bae0fddd1ad852e78cb23ca9 78834 utils optional pinentry-qt_0.7.2-3_i386.deb 415b52f6b8f431f6f2cb94ac62cf3518 56802 utils optional pinentry-gtk_0.7.2-3_i386.deb 9306f343a274b50b645f8bd203f4897c 59290 utils optional pinentry-gtk2_0.7.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh3PSTTx8oVVPtMYRAmNMAJwJDyS9DdlHUyFyeEifLVKTZGh4xACfQ8jA +7JO+BQ3vwZ+njtObOpOp4E= =aS+J -END PGP SIGNATURE- Accepted: pinentry-curses_0.7.2-3_i386.deb to pool/main/p/pinentry/pinentry-curses_0.7.2-3_i386.deb pinentry-doc_0.7.2-3_all.deb to pool/main/p/pinentry/pinentry-doc_0.7.2-3_all.deb pinentry-gtk2_0.7.2-3_i386.deb to pool/main/p/pinentry/pinentry-gtk2_0.7.2-3_i386.deb pinentry-gtk_0.7.2-3_i386.deb to pool/main/p/pinentry/pinentry-gtk_0.7.2-3_i386.deb pinentry-qt_0.7.2-3_i386.deb to pool/main/p/pinentry/pinentry-qt_0.7.2-3_i386.deb pinentry_0.7.2-3.diff.gz to pool/main/p/pinentry/pinentry_0.7.2-3.diff.gz pinentry_0.7.2-3.dsc to pool/main/p/pinentry/pinentry_0.7.2-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted autotrace 0.31.1-11 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 22:07:08 +0100 Source: autotrace Binary: libautotrace-dev libautotrace3 autotrace Architecture: source i386 Version: 0.31.1-11 Distribution: unstable Urgency: low Maintainer: Henning Makholm [EMAIL PROTECTED] Changed-By: Henning Makholm [EMAIL PROTECTED] Description: autotrace - bitmap to vector graphics converter libautotrace-dev - bitmap to vector graphics converter, development files libautotrace3 - bitmap to vector graphics converter, shared library files Changes: autotrace (0.31.1-11) unstable; urgency=low . * Rebuild for new libpstoedit0c2a package. * Zlib is not actually used by autotrace; remove build-dependency and comment out configure check. . * Override the ad-hoc build system to avoid transitive shlibs dependencies. * Further overrides to produce a sane /usr/lib/pkgconfig/autotrace.pc * The autotrace-config script is broken by design; don't ship it. All of these per Steve Langasek in http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html Files: e1466aa039079d8eed48bc1d6dd12951 697 graphics optional autotrace_0.31.1-11.dsc afaa43a0a961f069b3ad600362f2c39f 302782 graphics optional autotrace_0.31.1-11.diff.gz 24e38a0a1859e2a473a85a2fa2b2b273 39978 graphics optional autotrace_0.31.1-11_i386.deb 228276d5e66baa0745fd73b1c6dc17fc 108984 libs optional libautotrace3_0.31.1-11_i386.deb 4f90aea20f064c41fad546145b00e498 130166 libdevel optional libautotrace-dev_0.31.1-11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh4E/etBVnb7Tf9IRAg6CAJ9s0RwGc7Jwj0y8mmECnembre0JNACfbgxW zJ17eGdCW3CKgNz1o/vcvXg= =9dT5 -END PGP SIGNATURE- Accepted: autotrace_0.31.1-11.diff.gz to pool/main/a/autotrace/autotrace_0.31.1-11.diff.gz autotrace_0.31.1-11.dsc to pool/main/a/autotrace/autotrace_0.31.1-11.dsc autotrace_0.31.1-11_i386.deb to pool/main/a/autotrace/autotrace_0.31.1-11_i386.deb libautotrace-dev_0.31.1-11_i386.deb to pool/main/a/autotrace/libautotrace-dev_0.31.1-11_i386.deb libautotrace3_0.31.1-11_i386.deb to pool/main/a/autotrace/libautotrace3_0.31.1-11_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-he 0.9+0-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 19:55:56 +0200 Source: aspell-he Binary: aspell-he Architecture: source all Version: 0.9+0-4 Distribution: unstable Urgency: low Maintainer: Debian Hebrew Packaging Team [EMAIL PROTECTED] Changed-By: Lior Kaplan [EMAIL PROTECTED] Description: aspell-he - Hebrew dictionary for aspell Closes: 340754 Changes: aspell-he (0.9+0-4) unstable; urgency=low . * Incorrect contents file was created by debian/rules (Closes: #340754) Files: 419b4fd2a8ba188a7d1cac8acc757d04 752 text optional aspell-he_0.9+0-4.dsc f528c7f17eaf16b8c9102c39dce61070 2181 text optional aspell-he_0.9+0-4.diff.gz 93ca0d58a13ed5d4995266a659528291 209752 text optional aspell-he_0.9+0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh4RfHCar6qtHRZgRAsVDAKC9cRHKSoSOylCKjOiRI1hL4YdsEgCg1Eyx h1+wUMrlJ4a/9eD9v3v7cMk= =CR9g -END PGP SIGNATURE- Accepted: aspell-he_0.9+0-4.diff.gz to pool/main/a/aspell-he/aspell-he_0.9+0-4.diff.gz aspell-he_0.9+0-4.dsc to pool/main/a/aspell-he/aspell-he_0.9+0-4.dsc aspell-he_0.9+0-4_all.deb to pool/main/a/aspell-he/aspell-he_0.9+0-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gimp-gap 2.2.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.7 Date: Mon, 31 Oct 2005 23:29:24 -0800 Source: gimp-gap Binary: gimp-gap Architecture: source i386 Version: 2.2.0-1 Distribution: unstable Urgency: low Maintainer: Emil Soleyman-Zomalan [EMAIL PROTECTED] Changed-By: Emil Soleyman-Zomalan [EMAIL PROTECTED] Description: gimp-gap - The GIMP Animation Package Closes: 336626 336916 Changes: gimp-gap (2.2.0-1) unstable; urgency=low . * New upstream release (Closes: #336626) * debian/rules: - Removed dynamic generation of debian/control - Added the following build options: --disable-audio-support --disable-libxvidcore --with-preinstalled-libmpeg3 --with-preinstalled-libmpeg3=/usr/lib/libmpeg3.a * debian/control: - Added build dependency on libmpeg3-dev * debian/patches: - FTBFS on GNU/kFreeBSD patch by Aurelien Jarno [EMAIL PROTECTED] (Closes: #336916) Files: 3a92840047b223427a8781267366e938 920 graphics optional gimp-gap_2.2.0-1.dsc 2f0f829ff9d5cb563cc27bfd6c2607c7 5178547 graphics optional gimp-gap_2.2.0.orig.tar.gz 168850b087e7c43c170d0b52a69c7a3b 1932 graphics optional gimp-gap_2.2.0-1.diff.gz e1e2f8d3b438f30e7bf06ed790a8efa3 10858912 graphics optional gimp-gap_2.2.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh2ruwO+u47cOQDsRA8SAAKCSVxTRugvTpb2aeyA+G5lJ0oc10ACfVlmc X1O5Of0tdfFtS720eZDEoLM= =KSU4 -END PGP SIGNATURE- Accepted: gimp-gap_2.2.0-1.diff.gz to pool/main/g/gimp-gap/gimp-gap_2.2.0-1.diff.gz gimp-gap_2.2.0-1.dsc to pool/main/g/gimp-gap/gimp-gap_2.2.0-1.dsc gimp-gap_2.2.0-1_i386.deb to pool/main/g/gimp-gap/gimp-gap_2.2.0-1_i386.deb gimp-gap_2.2.0.orig.tar.gz to pool/main/g/gimp-gap/gimp-gap_2.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apt-rpm 0.5.15cnc6-7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 21:13:23 +0100 Source: apt-rpm Binary: apt-rpm-repository libapt-rpm-pkg-libc6.3-6-0 libapt-rpm-pkg-dev Architecture: source i386 Version: 0.5.15cnc6-7 Distribution: unstable Urgency: low Maintainer: Peter Eisentraut [EMAIL PROTECTED] Changed-By: Peter Eisentraut [EMAIL PROTECTED] Description: apt-rpm-repository - tools to create an APT RPM repository libapt-rpm-pkg-dev - development files for APT for RPM library libapt-rpm-pkg-libc6.3-6-0 - APT for RPM library Changes: apt-rpm (0.5.15cnc6-7) unstable; urgency=low . * Added lintian overrides * Added linker option --as-needed Files: e141fac0333dc17803c6b9a22cac3c21 748 admin extra apt-rpm_0.5.15cnc6-7.dsc 6fe3358a07ba594dbab082bef33f084d 9675 admin extra apt-rpm_0.5.15cnc6-7.diff.gz 9909c83fb6aba1577d55c584d1bc6a03 505512 libdevel extra libapt-rpm-pkg-dev_0.5.15cnc6-7_i386.deb e13a62966f3e0dc78f8a9476bc5ba2eb 361694 libs extra libapt-rpm-pkg-libc6.3-6-0_0.5.15cnc6-7_i386.deb 071f07ac4c3f4f979626857a5bff29a4 35772 admin extra apt-rpm-repository_0.5.15cnc6-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh3I3TTx8oVVPtMYRAknsAKCgiwW3uba+KjuGLA3Wqiz8WKEpTQCgmEPw qhyxyJuSN23exM4GnVRJzcg= =1tlL -END PGP SIGNATURE- Accepted: apt-rpm-repository_0.5.15cnc6-7_i386.deb to pool/main/a/apt-rpm/apt-rpm-repository_0.5.15cnc6-7_i386.deb apt-rpm_0.5.15cnc6-7.diff.gz to pool/main/a/apt-rpm/apt-rpm_0.5.15cnc6-7.diff.gz apt-rpm_0.5.15cnc6-7.dsc to pool/main/a/apt-rpm/apt-rpm_0.5.15cnc6-7.dsc libapt-rpm-pkg-dev_0.5.15cnc6-7_i386.deb to pool/main/a/apt-rpm/libapt-rpm-pkg-dev_0.5.15cnc6-7_i386.deb libapt-rpm-pkg-libc6.3-6-0_0.5.15cnc6-7_i386.deb to pool/main/a/apt-rpm/libapt-rpm-pkg-libc6.3-6-0_0.5.15cnc6-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted taskjuggler 2.2+beta2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 18:03:21 + Source: taskjuggler Binary: taskjuggler Architecture: source i386 Version: 2.2+beta2-2 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team [EMAIL PROTECTED] Changed-By: Mark Purcell [EMAIL PROTECTED] Description: taskjuggler - Project management application Closes: 340692 Changes: taskjuggler (2.2+beta2-2) unstable; urgency=low . * Add Build-Depends: cdbs - taskjuggler - FTBFS: missing build dependency (Closes: #340692) Files: 2b0db8dfed386623d8769071e907811c 775 kde optional taskjuggler_2.2+beta2-2.dsc e150300c87f56c6e855a9256280cef9b 3676 kde optional taskjuggler_2.2+beta2-2.diff.gz c128a39598e6c1a5ed971c5057002920 1231644 kde optional taskjuggler_2.2+beta2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh3X2oCzanz0IthIRAlHzAJ9FCvwH8lajNhnoFytNXTyM0OiT1gCfVTm6 1+AtFE7/H5laAgLos+1+vH8= =jVoK -END PGP SIGNATURE- Accepted: taskjuggler_2.2+beta2-2.diff.gz to pool/main/t/taskjuggler/taskjuggler_2.2+beta2-2.diff.gz taskjuggler_2.2+beta2-2.dsc to pool/main/t/taskjuggler/taskjuggler_2.2+beta2-2.dsc taskjuggler_2.2+beta2-2_i386.deb to pool/main/t/taskjuggler/taskjuggler_2.2+beta2-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted laptop-mode-tools 1.11-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 29 Oct 2005 16:40:00 +0200 Source: laptop-mode-tools Binary: laptop-mode-tools Architecture: source all Version: 1.11-1 Distribution: unstable Urgency: low Maintainer: Bart Samwel [EMAIL PROTECTED] Changed-By: Bart Samwel [EMAIL PROTECTED] Description: laptop-mode-tools - Userland scripts to control laptop mode Closes: 323623 324137 324457 325186 326433 327028 328028 328118 328432 335492 336294 Changes: laptop-mode-tools (1.11-1) unstable; urgency=low . * New upstream version 1.11. * (Closes: #328118) Unset VERBOSE before starting. * (Closes: #328432) Check if block device is block device before treating it as such. * (Closes: #335492, #326433) Check if /var/run/laptop-mode-nolm-mount-opts exists before using it. * (Closes: #325186) Change default for CONTROL_HD_POWERMGMT to 0, because it causes system crashes on some hardware. * (Closes: #328028) Check if hdparm is installed before using it. * (Closes: #324457) Fit config file in 80-character screen. * (Closes: #327028) Check whether requested state matches old state, and do nothing if so. * (Closes: #336294) Send error output of hdparm to /dev/null. * (Closes: #323623) CPU frequency governor and minimum frequency control. * (Closes: #324137) Add lm-profiler, accompanying config file lm-profiler.conf, and several subdirectories to /etc/laptop-mode for controlling daemons. Files: c14ede2e436d19d2ecfccedfbfbc596a 594 utils optional laptop-mode-tools_1.11-1.dsc f5c882e2ba1953b80abd1d7cd38c3a51 51501 utils optional laptop-mode-tools_1.11.orig.tar.gz 388990af6d05ec40b481538d7a2db71f 4676 utils optional laptop-mode-tools_1.11-1.diff.gz cc8f22bdd5df5310eb859121b1477841 52690 utils optional laptop-mode-tools_1.11-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh4XjKb5dImj9VJ8RAjoBAJ0bkAQmPZVHJeDnz7NDxzgD5ESZigCghK4t +FyN4pgjHLbL5EaKbpfIo2g= =+PIc -END PGP SIGNATURE- Accepted: laptop-mode-tools_1.11-1.diff.gz to pool/main/l/laptop-mode-tools/laptop-mode-tools_1.11-1.diff.gz laptop-mode-tools_1.11-1.dsc to pool/main/l/laptop-mode-tools/laptop-mode-tools_1.11-1.dsc laptop-mode-tools_1.11-1_all.deb to pool/main/l/laptop-mode-tools/laptop-mode-tools_1.11-1_all.deb laptop-mode-tools_1.11.orig.tar.gz to pool/main/l/laptop-mode-tools/laptop-mode-tools_1.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libofx 1:0.8.0-8 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 13:20:38 -0800 Source: libofx Binary: libofx2c2a ofx libofx-dev Architecture: source powerpc Version: 1:0.8.0-8 Distribution: unstable Urgency: low Maintainer: Thomas Bushnell, BSG [EMAIL PROTECTED] Changed-By: Thomas Bushnell, BSG [EMAIL PROTECTED] Description: libofx-dev - development package for libofx2c2a libofx2c2a - library to support Open Financial Exchange ofx- Open Financial Exchange programs Closes: 340772 Changes: libofx (1:0.8.0-8) unstable; urgency=low . * debian/control (libofx-dev): Conflict with libofx2, which in its released versions, contained the .a archives which are now in libofx-dev. (Don't actually declare a replacement here, because that's not really correct; however, libofx-dev does depend on libofx2c2a, which in turn does Replace libofx2.) (Closes: #340772) Files: 00ec59db0d4673a7c513fab10df84669 664 libs optional libofx_0.8.0-8.dsc 2c1da8ccbaddc711573069c8af99907a 90841 libs optional libofx_0.8.0-8.diff.gz 282b62c406772c8f05d07cf3c126c4db 82602 libs optional libofx2c2a_0.8.0-8_powerpc.deb 08e854537396461c6edf6d578b5869f8 390930 libdevel optional libofx-dev_0.8.0-8_powerpc.deb e0dd8bc85ff166466af6c0e526761ef6 96244 libs optional ofx_0.8.0-8_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh4coqMsB9b6fcOoRAmXNAJwOFEPdFfs+i9h6FgMwFsixyPplTACfQLUD aiPOSzfV6MycIhrq8Q8/+3g= =riDo -END PGP SIGNATURE- Accepted: libofx-dev_0.8.0-8_powerpc.deb to pool/main/libo/libofx/libofx-dev_0.8.0-8_powerpc.deb libofx2c2a_0.8.0-8_powerpc.deb to pool/main/libo/libofx/libofx2c2a_0.8.0-8_powerpc.deb libofx_0.8.0-8.diff.gz to pool/main/libo/libofx/libofx_0.8.0-8.diff.gz libofx_0.8.0-8.dsc to pool/main/libo/libofx/libofx_0.8.0-8.dsc ofx_0.8.0-8_powerpc.deb to pool/main/libo/libofx/ofx_0.8.0-8_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pmccabe 2.3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Nov 2003 12:06:55 -0700 Source: pmccabe Binary: pmccabe Architecture: source i386 Version: 2.3-1 Distribution: unstable Urgency: low Maintainer: [EMAIL PROTECTED] Changed-By: Paul Bame [EMAIL PROTECTED] Description: pmccabe- McCabe-style function complexity and line counting for C and C++ Closes: 340368 Changes: pmccabe (2.3-1) unstable; urgency=low . * you can use class as an identifier in C code now. Thanks to xianjie zhang for an excellent bug report. * closes: 340368 Files: 7ba105552c7accc3572781850fb44cf9 484 devel optional pmccabe_2.3-1.dsc 706110760043de68c781c8c021e73184 55102 devel optional pmccabe_2.3-1.tar.gz 4513520ff3839e0518df6f6eddb09a23 21784 devel optional pmccabe_2.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDh4vWjdQE/37YfVcRAskOAJ4wGO/Ytaua4u9I5iteiiqsn2GT6wCglqa4 xscRhUf7Ct1p2q4j/l+OPh8= =b0As -END PGP SIGNATURE- Accepted: pmccabe_2.3-1.dsc to pool/main/p/pmccabe/pmccabe_2.3-1.dsc pmccabe_2.3-1.tar.gz to pool/main/p/pmccabe/pmccabe_2.3-1.tar.gz pmccabe_2.3-1_i386.deb to pool/main/p/pmccabe/pmccabe_2.3-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vips 7.10.16-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 25 Nov 2005 19:15:54 -0500 Source: vips Binary: libvips-tools libvips10c2a libvips-doc libvips10-dev Architecture: source all i386 Version: 7.10.16-2 Distribution: unstable Urgency: low Maintainer: Jay Berkenbilt [EMAIL PROTECTED] Changed-By: Jay Berkenbilt [EMAIL PROTECTED] Description: libvips-doc - image processing system good for very large images (doc) libvips-tools - image processing system good for very large images (tools) libvips10-dev - image processing system good for very large images (dev) libvips10c2a - image processing system good for very large images Closes: 340788 Changes: vips (7.10.16-2) unstable; urgency=low . * Fix libtool versioning problem resulting in wrong soname. (Closes: #340788) Files: ba1917bc8e90febfacf2cffcaf2c2167 847 libs optional vips_7.10.16-2.dsc 5d9c2095877a821af66e2063212bba19 5384 libs optional vips_7.10.16-2.diff.gz 5e2315de8903b4593993230f9d80bba4 1496828 doc optional libvips-doc_7.10.16-2_all.deb 71f65ef1e4d9370ff5846464de759113 373940 libs optional libvips10c2a_7.10.16-2_i386.deb 5c921a07767dfc4263cc920c0caaac70 659986 libdevel optional libvips10-dev_7.10.16-2_i386.deb fe938c9280eeb45880853a07fa847a45 79582 graphics optional libvips-tools_7.10.16-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDh7HlEBVk6taI4KcRAlJdAJ4y7dqkVcbUwmUj1HfiJ0em3FAGYgCgh3ur dWLEq95ZMPAbNVjhpXRcriw= =XOm+ -END PGP SIGNATURE- Accepted: libvips-doc_7.10.16-2_all.deb to pool/main/v/vips/libvips-doc_7.10.16-2_all.deb libvips-tools_7.10.16-2_i386.deb to pool/main/v/vips/libvips-tools_7.10.16-2_i386.deb libvips10-dev_7.10.16-2_i386.deb to pool/main/v/vips/libvips10-dev_7.10.16-2_i386.deb libvips10c2a_7.10.16-2_i386.deb to pool/main/v/vips/libvips10c2a_7.10.16-2_i386.deb vips_7.10.16-2.diff.gz to pool/main/v/vips/vips_7.10.16-2.diff.gz vips_7.10.16-2.dsc to pool/main/v/vips/vips_7.10.16-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
