Re: glibc, bug 438179 et avenir de/dans etch
On Wed, Sep 26, 2007 at 17:18:35 +0200, Pierre Habouzit wrote: On Wed, Sep 26, 2007 at 03:55:56PM +, [EMAIL PROTECTED] wrote: La migration de Sarge à Etch casse donc ce fonctionnement, ce qui Non etch n'a pas ça. Seul lenny est concernée. Le monsieur a raison, getaddrinfo() dans etch fait le tri. Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: glibc, bug 438179 et avenir de/dans etch
On Thu, Sep 27, 2007 at 09:28:04AM +, Julien Cristau wrote: On Wed, Sep 26, 2007 at 17:18:35 +0200, Pierre Habouzit wrote: On Wed, Sep 26, 2007 at 03:55:56PM +, [EMAIL PROTECTED] wrote: La migration de Sarge à Etch casse donc ce fonctionnement, ce qui Non etch n'a pas ça. Seul lenny est concernée. Le monsieur a raison, getaddrinfo() dans etch fait le tri. Euh je suis surpris parce que Uli prétend le contraire Oo... En tout cas son test est foireux, parce que il ne teste la rule 9 que ssi il testait sur le host qui finit en 165. Pour faire le test correctement il faudrait le faire sur des préfixes qui varient bien plus tot. De plus il faudrait etre sur de le faire sans nscd ni aucun cache (qui parfois te choisissent un ordre). Donc en ayant bien vérifié avant que dig renvoie des paquets DNS où il y a de la variabilité aussi... -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpozZPnGar1J.pgp Description: PGP signature
Re: glibc, bug 438179 et avenir de/dans etch
Bonjour,
Le 26.09.2007 19:16, Pierre Habouzit a écrit :
Je ne sais pas quelles sont les conditions d'utilisation du programme,
donc il est difficile de valider quoi que ce soit. Il y a mille raisons
pour lesquelles ça a l'air d'être trié (nscd notamment). Mais:
(1) la rule 9 est à propos des plus longs préfixes, or vu que la
différence entre 165 et 166 est uniquement sur les deux derniers
bits, le test est tout simplement idiot.
Mon test est probablement idiot, mais il met en évidence un comportement que
j'ai sur plusieurs dizaines de serveurs et que j'essaye tant bien que mal de
comprendre depuis plusieurs jours. Avant de venir passer pour un âne sur une
liste debian-devel archivée sur internet (ce qui n'était pas franchement mon
rêve je dois bien te l'avouer ;-) ), j'ai parlé du problème à un ami qui a pu le
reproduire sur ses propres serveurs en Debian etch.
Le rapprochement entre mon problème et le bug 438179 est peut-être malheureux.
Néanmoins, j'ai un problème, qui touche la glibc de Etch, qui n'est apparemment
pas si isolé que cela puisque nous sommes au minimum deux à l'avoir.
Peut-être est-il lié à l'environnement (matériel, logiciel, ou réseau) mais je
dois bien avouer que je suis à cours de piste. Par ailleurs, en patchant la
glibc 2.3.6 au niveau de la règle 9 (voir plus bas), je n'ai plus le problème.
Si je refais le test sur la glibc de Etch avec le petit programme du mail
précédent et en arrêtant le plus de démons possibles (voir fichier ps-ed.txt
joint) :
$ cat /etc/debian_version
4.0
$ dpkg -l libc6* |grep ^i
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
Avec getaddrinfo :
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
Avec gethostbyname :
$ ./reso-dns ldaprs.mon.domaine gethostbyname
gethostbyname : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine gethostbyname
gethostbyname : ldaprs.mon.domaine 10.xxx.yyy.166 10.xxx.yyy.165
$ ./reso-dns ldaprs.mon.domaine gethostbyname
gethostbyname : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine gethostbyname
gethostbyname : ldaprs.mon.domaine 10.xxx.yyy.166 10.xxx.yyy.165
Non seulement, il y a un tri, mais en plus sur des adresses proches...
De plus si j'applique ce patch à la glibc 2.3.6 [1], je n'ai plus le problème :
--- glibc-backup/sysdeps/posix/getaddrinfo.c2005-10-16 12:15:30.0
+0200
+++ glibc-2.3.6/sysdeps/posix/getaddrinfo.c 2007-09-25 11:29:46.0
+0200
@@ -1392,7 +1392,7 @@
int bit1 = 0;
int bit2 = 0;
- if (a1-dest_addr-ai_family == PF_INET)
+ if (a1-dest_addr-ai_family == PF_INET 0)
{
assert (a1-source_addr.ss_family == PF_INET);
assert (a2-source_addr.ss_family == PF_INET);
Or ce patch s'applique pile ici dans la fonction getaddrinfo de la glibc 2.3.6 :
/* Rule 9: Use longest matching prefix. */
if (a1-got_source_addr
a1-dest_addr-ai_family == a2-dest_addr-ai_family)
{
int bit1 = 0;
int bit2 = 0;
if (a1-dest_addr-ai_family == PF_INET)
{
assert (a1-source_addr.ss_family == PF_INET);
assert (a2-source_addr.ss_family == PF_INET);
[1] méthode utilisée pour appliquer le patch :
- dans l'archive debian de la glibc-2.3.6, création d'un fichier
debian/patches/any/patch-sortv4.diff avec ce patch.
- ajout de any/patch-sortv4.diff -p 1 à la suite des any/ dans le fichier
debian/patches/series
Voici les tests des getaddrinfo avec la glibc patchée :
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.166 10.xxx.yyy.165
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.165 10.xxx.yyy.166
$ ./reso-dns ldaprs.mon.domaine getaddrinfo
getaddrinfo : ldaprs.mon.domaine 10.xxx.yyy.166 10.xxx.yyy.165
Je suis prêt à faire d'autre test si cela peut aider.
Cordialement,
Julien$ ps -ef
UIDPID PPID C STIME TTY TIME CMD
root 1 0 0 Sep04 ?00:00:01 init [2]
root 2 1 0 Sep04 ?00:00:00 [migration/0]
root 3 1 0 Sep04 ?00:00:00 [ksoftirqd/0]
root 4 1 0 Sep04 ?00:00:00 [migration/1]
root 5 1 0 Sep04 ?00:00:00 [ksoftirqd/1]
root 6 1 0 Sep04 ?00:00:00 [events/0]
root 7 1 0 Sep04 ?00:00:00 [events/1]
root 8 1 0 Sep04 ?
Re: glibc, bug 438179 et avenir de/dans etch
On Thu, Sep 27, 2007 at 11:39:03AM +, [EMAIL PROTECTED] wrote:
Bonjour,
Le 26.09.2007 19:16, Pierre Habouzit a écrit :
Je ne sais pas quelles sont les conditions d'utilisation du programme,
donc il est difficile de valider quoi que ce soit. Il y a mille raisons
pour lesquelles ça a l'air d'être trié (nscd notamment). Mais:
(1) la rule 9 est à propos des plus longs préfixes, or vu que la
différence entre 165 et 166 est uniquement sur les deux derniers
bits, le test est tout simplement idiot.
Mon test est probablement idiot, mais il met en évidence un comportement que
j'ai sur plusieurs dizaines de serveurs et que j'essaye tant bien que mal de
comprendre depuis plusieurs jours. Avant de venir passer pour un âne sur une
liste debian-devel archivée sur internet (ce qui n'était pas franchement mon
rêve je dois bien te l'avouer ;-) ), j'ai parlé du problème à un ami qui a pu
le
reproduire sur ses propres serveurs en Debian etch.
Disons que la règle 9 met en tete les adresses qui partagent le plus
long préfixe possible avec l'ip de la machine locale. Donc un test où la
variation du préfixe n'est sensible que sur les deux derniers bits
n'aura du sens que si le test est fait sur l'une des deux machines
concernées. Voilà pourquoi le test est mauvais.
De plus si j'applique ce patch à la glibc 2.3.6 [1], je n'ai plus le problème
:
--- glibc-backup/sysdeps/posix/getaddrinfo.c 2005-10-16 12:15:30.0
+0200
+++ glibc-2.3.6/sysdeps/posix/getaddrinfo.c 2007-09-25 11:29:46.0
+0200
@@ -1392,7 +1392,7 @@
int bit1 = 0;
int bit2 = 0;
- if (a1-dest_addr-ai_family == PF_INET)
+ if (a1-dest_addr-ai_family == PF_INET 0)
{
assert (a1-source_addr.ss_family == PF_INET);
assert (a2-source_addr.ss_family == PF_INET);
Or ce patch s'applique pile ici dans la fonction getaddrinfo de la glibc
2.3.6 :
/* Rule 9: Use longest matching prefix. */
if (a1-got_source_addr
a1-dest_addr-ai_family == a2-dest_addr-ai_family)
{
int bit1 = 0;
int bit2 = 0;
if (a1-dest_addr-ai_family == PF_INET)
{
assert (a1-source_addr.ss_family == PF_INET);
assert (a2-source_addr.ss_family == PF_INET);
Okay bah en effet, le code de tri de la rule 9 est présent depuis bien
plus de temps que ce que Uli dit p/r à la rfc 3484. Aurélien a fait un
patch qui au lien de mettre 0 à cet endroit, utilise un réglage de
gai.conf pour ce faire, le patch est attaché, et devrait du coup sans
doute s'appliquer directement en glibc 2.3.X (en tout cas sans trop de
grosses difficultés).
Avec le patch il suffit de mettre dans /etc/gai.conf: sortv4 no
Désolé d'avoir été vite agacé donc, mais j'en ai un peu marre de me
faire taper dessus pour un changement de comportement de la glibc alors
que je suis qu'un des packagers, et pas l'upstream, donc j'ai tendance à
partir au 1/4 de tour sur ce problème.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
2007-08-16 Aurelien Jarno [EMAIL PROTECTED]
* sysdeps/posix/getaddrinfo.c (gaiconf_reload_flag): Move
to the top of the file.
(gaiconf_mtime): Likewise.
(sortv4): New configuration variable.
(gaiconf_init): Parse the sortv4 option in the configuration
file.
(rfc3484_sort): Ignore rule 9 for IPv4 adresses if sortv4
is false.
* posix/gai.conf: Add the new sortv4 option.
--- posix/gai.conf 2007-08-16 22:59:03.0 +0200
+++ posix/gai.conf 2007-08-16 22:58:48.0 +0200
@@ -15,6 +15,11 @@
#changed and if necessary reload. This option should not really be
#used. There are possible runtime problems. The default is no.
#
+# sortv4 yes|no
+#If set to no, getaddrinfo(3) will ignore IPv4 adresses in rule 9. See
+#section 6 in RFC 3484. The default is yes. Setting this option to
+#no breaks conformance to RFC 3484.
+#
# label mask value
#Add another rule to the RFC 3484 label table. See section 2.1 in
#RFC 3484. The default is:
--- sysdeps/posix/getaddrinfo.c 2007-08-16 23:02:34.0 +0200
+++ sysdeps/posix/getaddrinfo.c 2007-08-16 22:31:53.0 +0200
@@ -79,6 +79,16 @@
# define UNIX_PATH_MAX 108
#endif
+/* Nozero if we are supposed to reload the config file automatically
+ whenever it changed. */
+static int gaiconf_reload_flag;
+
+/* Zero if we are supposed to ignore rule 9 for IPv4 addresses */
+static int gaiconf_sortv4_flag = 1;
+
+/* Last modification time. */
+static struct timespec gaiconf_mtime;
+
struct gaih_service
{
const char *name;
@@ -1344,7 +1354,7 @@
int bit1 = 0;
int bit2 = 0;
- if (a1-dest_addr-ai_family == PF_INET)
+ if (a1-dest_addr-ai_family == PF_INET gaiconf_sortv4_flag)
{
assert
Re: glibc, bug 438179 et avenir de/dans etch
Le 27.09.2007 13:49, Pierre Habouzit a écrit : Okay bah en effet, le code de tri de la rule 9 est présent depuis bien plus de temps que ce que Uli dit p/r à la rfc 3484. Aurélien a fait un patch qui au lien de mettre 0 à cet endroit, utilise un réglage de gai.conf pour ce faire, le patch est attaché, et devrait du coup sans doute s'appliquer directement en glibc 2.3.X (en tout cas sans trop de grosses difficultés). Bon, ca ne va pas être tout à fait trivial (mais pas forcement très compliquer) : la patch commence par s'occuper d'un fichier posix/gai.conf qui n'existe pas dans la glibc 2.3.6 et les numero de lignes ne correspondent pas ensuite. Je regarde (probablement demain, une sombre histoire d'acl ldap à régler avant ;) ) si j'arrive à l'adapter pour cette version de la glibc. Je te tiens au courant. Désolé d'avoir été vite agacé donc, mais j'en ai un peu marre de me faire taper dessus pour un changement de comportement de la glibc alors que je suis qu'un des packagers, et pas l'upstream, donc j'ai tendance à partir au 1/4 de tour sur ce problème. Pas grave ;) Qu'on soit bien d'accord, je ne cherche pas de coupable, j'essaye juste d'une part de bien comprendre un problème qui touche mes serveurs et comment tout cela va ou peut évoluer et d'autre part de le régler la meilleur façon possible. Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Welcome to A Single Blade Of Grass
The subscription of the email address: debian-devel-french@lists.debian.org To the mailing list: A Single Blade Of Grass is all set. Thanks for subscribing! Date of this subscription: Thu Sep 27 15:40:18 2007 Please save this email message for future reference. --- You may automatically unsubscribe from this list at any time by visiting the following URL: http://infinitepossibility.ralf.netmindz.net/cgi-local/dada/mail.cgi?f=ul=single[EMAIL PROTECTED]p=14264063 If the above URL is inoperable, make sure that you have copied the entire address. Some mail readers will wrap a long URL and thus break this automatic unsubscribe mechanism. You may also change your subscription by visiting this list's main screen: http://infinitepossibility.ralf.netmindz.net/cgi-local/dada/mail.cgi?f=listl=single If you're still having trouble, please contact the list owner at: mailto:[EMAIL PROTECTED] The following physical address is associated with this mailing list: - mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: glibc, bug 438179 et avenir de/dans etch
On Thu, Sep 27, 2007 at 12:02:45 +0200, Pierre Habouzit wrote: Euh je suis surpris parce que Uli prétend le contraire Oo... En tout cas son test est foireux, parce que il ne teste la rule 9 que ssi il testait sur le host qui finit en 165. Pour faire le test correctement il faudrait le faire sur des préfixes qui varient bien plus tot. De plus il faudrait etre sur de le faire sans nscd ni aucun cache (qui parfois te choisissent un ordre). Donc en ayant bien vérifié avant que dig renvoie des paquets DNS où il y a de la variabilité aussi... Je me suis contenté de comparer getent hosts security.debian.org et getent ahosts security.debian.org. Dans le premier cas ca tourne, dans le 2eme cas 212.211.132.32 et 212.211.132.250 sont toujours avant 128.31.0.36 (et l'ordre entre les deux premiers change). Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
A Single Blade Of Grass Unsubscription
The removal of the email address: debian-devel-french@lists.debian.org From the mailing list: A Single Blade Of Grass is all set. Date of this removal: Thu Sep 27 16:10:14 2007 Please save this email message for future reference. --- You may automatically subscribe from this list at any time by visiting the following URL: http://infinitepossibility.ralf.netmindz.net/cgi-local/dada/mail.cgi?f=nl=singlee=debian-devel-french%40lists.debian.orgp=14264063 If the above URL is inoperable, make sure that you have copied the entire address. Some mail readers will wrap a long URL and thus break this automatic unsubscribe mechanism. You may also change your subscription by visiting this list's main screen: http://infinitepossibility.ralf.netmindz.net/cgi-local/dada/mail.cgi?f=listl=single If you're still having trouble, please contact the list owner at: mailto:[EMAIL PROTECTED] The following physical address is associated with this mailing list: - mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
to, 2007-09-27 kello 10:21 +1000, Ben Finney kirjoitti: Jon Dowland [EMAIL PROTECTED] writes: However if an upstream author of a package wishes to conceal their address, I think we should honour that. This is at odds with always have correct contact information for the copyright holder at the time of packaging, which I think Debian should strive to achieve for the sake of its users. I'm afraid I have to disagree with that. Obfuscation which can easily be reversed by a human, but not so easily by a computer, does not render contact information incorrect. If I write my e-mail address as follows, it's still correct: My full name is Lars Ivar Wirzenius, and you can send me e-mail by taking my initials and putting them in front of the at sign and iki.fi after it. Mind you, I don't like obfuscation, and I think it's a nuisance myself, but we shouldn't violate people's wish to try to avoid spam by publishing their addresses in un-obfuscated form. That only makes people angry at us for little or no benefit, since there are no situations when we want to automatically send e-mails to upstream developers anyway. The only way to honour conceal their address at the same time as the above is to not distribute the package at all. I don't think that's a good solution. I don't think there is any requirement to have any upstream contact information whatsoever in order to be able to distribute a package. -- Close your mind to stress and pain, hack till you're no longer sane. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[VAC] a few days (I hope). Bretagne, France.
Hi, Today, I'll travel to France to pursuit my Master studies in human-computer interaction at the ENST-Bretagne and Université de Bretagne Sud. grep has a RC bug right now [1], any help to solve it will be appreciated. Just contact anibal. [1] http://bugs.debian.org/181378 I hope I'll be able to continue my work on debian as soon as a I get some order and an INET connection there. Best regards, -- Santiago Ruano RincGrupo GNU/Linux Universidad del Cauca I know but one freedom, and that is the freedom of the mind. --Antoine de Saint-Exupery
Re: modified email address in debian/copyright file
Lars Wirzenius [EMAIL PROTECTED] writes: I don't think there is any requirement to have any upstream contact information whatsoever in order to be able to distribute a package. This seems to be the point of disagreement. I think this should be required, in order that Debian users can have more confidence [0] in the copyright status of works in Debian. [0] not absolute confidence, of course, which is impossible; but greater confidence than would be the case in the absence of valid copyright holder contact details. -- \Program testing can be a very effective way to show the | `\presence of bugs, but is hopelessly inadequate for showing | _o__) their absence. -- Edsger Dijkstra | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Building packages with exact binary matches
On Wed, 26 Sep 2007 12:31:51 +0200, Martin Uecker [EMAIL PROTECTED] said: On Wed, Sep 26, 2007 at 12:25:02AM -0500, Manoj Srivastava wrote: Just because you have _heard_ anyone diss special relativity being the sole reason to believe in it is in the same ball park as blissful, you know, ignorance. It is not about hearsay. It is about finding an error in a predictation. And I do not care *who* finds the error. Of course the predications have actually be checked. So you are right with your argument, if nobody actually does this, it would be ignorant to believe in a scientifc theory for the sole reason that nobody complains. Similar, if nobody recompiles the packages and checks for mismatches, then silence would in fact not imply that things are ok. But I question your premise: I have no doubt that some people would actually recompile packages and compare the hash. Even if it is not done normally, somebody would do this if doubts come up for some reason (e.g. some debian hosts are compromised again.). This alone would actually be worth a lot. But recompiling from what? If you do not get the exact same source, you have no hope of getting the same result. And the way things work, the chances are that if the binary is tainted, the source would be tainted -- and you have got nowhere. The difference is evidence. If there is some merit to the notion that a buildd is compromised, the solution is not bunches of people building from potentially tainted sources and comparing checksums. If know that the source code wich has hash 4457575757575 compiled in the build environment with hash 4837373737 gives a package with hash 366336363, then it is actually *evidence* that something is seriously wrong if you end up with a package with a different hash. So, someone replaces the binary compiled on the buildd with a fake one, in between the binary being built and it being signed? All the work to get bit-for-bit reproducibility for such a low priority attack vector? manoj -- VMS is a text-only adventure game. If you win you can use Unix. Bill Davidsen ([EMAIL PROTECTED]) Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: semi-virtual packages?
On Wed, 26 Sep 2007 04:04:33 -0600, Bruce Sass [EMAIL PROTECTED] said: On Tue September 25 2007 09:22:02 am Manoj Srivastava wrote: On Tue, 25 Sep 2007 02:36:24 -0600, Bruce Sass [EMAIL PROTECTED] said: On Sun September 23 2007 03:08:59 pm Manoj Srivastava wrote: On Sun, 23 Sep 2007 14:26:29 -0600, Bruce Sass [EMAIL PROTECTED] said: [I've cut a lot of duplication. If I cut something which doesn't get addressed below, feel free to bring it back.] The scheme I described was under the written assumption there are no such situations which would not already have a virtual package. Ah. That assumption turns out to be incorrect. Haha. There is nothing wrong with the assumption. That is kinda like saying pylint is incorrect for spitting out errors when given a correct perl program. You ignored a sign which would have taken you down a different path, and now appear to be complaining because the path you ended up on took you to the wrong place---neither the sign or paths are incorrect, you just didn't pay attention and got lost. Hmm? You assumed, and I quote there are no such situations which would not already have a virtual package. Since there are situations where there is no virtual package, it certainly seems to me that the assumption you made is invalid. If your assumption is correct, then I have missed something somewhere. Why would you think any of that scheme was applicable to the case you were thinking of if it is a case in which there is no virtual package? I am not sure how to answer that. I assumed that the scheme under discussion was going to be universal (or else it does not seem to be much good, really -- it would still leave files around that are not associated with anything). I don't see why it would need to be universal, one size stuff often doesn't fit anyone very well and it is not like being universal is pervasive and this would stand out as a wart. If we are not talking about a policy to be made, and you are only talking about an opt in scheme for some orphan files, then indeed, I have nothing to add to the conversation. manoj -- algorithm, n.: Trendy dance for hip programmers. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444249: ITP: pyexiv2 -- Python binding to Exiv2
Package: wnpp Severity: wishlist Owner: Michal Čihař [EMAIL PROTECTED] * Package name: pyexiv2 Version : 0.1 Upstream Author : Olivier Tilloy [EMAIL PROTECTED] * URL : http://tilloy.net/dev/pyexiv2/ * License : GPL Programming Lang: C++/Python Description : Python binding to Exiv2 pyexiv2 is a python binding to exiv2, the C++ library for manipulation of EXIF and IPTC image metadata. It is a python module that allows your python scripts to read and write metadata (EXIF, IPTC, thumbnail) embedded in image files (JPEG, TIFF, ...). It is designed as a high level interface to the functionalities offered by exiv2 (and is built on top of it). Using python's built-in data types and standard modules, it provides easy manipulation of image metadata. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Re: modified email address in debian/copyright file
Hi, On Thursday 27 September 2007 08:39, Ben Finney wrote: Lars Wirzenius [EMAIL PROTECTED] writes: I don't think there is any requirement to have any upstream contact information whatsoever in order to be able to distribute a package. This seems to be the point of disagreement. I think this should be required... Whether or not it its an requirement to be able to contact the author, doesnt have anything to do with obfuscating the email address or not. (Assuming its not obfuscated beyond recognitition.) (*) Unless you talk about the requirement to be able to contact the author without human intervention. But I haven't read anybody requiring that. And as Lars wrote in the email you replied to: Mind you, I don't like obfuscation, and I think it's a nuisance myself, but we shouldn't violate people's wish to try to avoid spam by publishing their addresses in un-obfuscated form. That only makes people angry at us for little or no benefit, since there are no situations when we want to automatically send e-mails to upstream developers anyway. I completly agree with those five lines. regards, Holger (*) BTW, I dont have an example at hand, but I'm pretty sure I have seen code in Debian written by anonymous and friends. You can't contact them either. pgp1ZwP7gNX1Y.pgp Description: PGP signature
Re: Changing name of source package
On Wed, Sep 26, 2007 at 07:26:51PM -0700, Steve Langasek wrote: The only other thing you need to worry about is filing a bug report against ftp.debian.org to get the old php4-ps source package removed, since this won't happen automatically. If it is not still required in stable/oldstable isn't it? -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Building packages with exact binary matches
Ben Finney [EMAIL PROTECTED] wrote: Martin Uecker [EMAIL PROTECTED] writes: On Tue, Sep 25, 2007 at 06:33:40PM -0500, Manoj Srivastava wrote: Ah, security through blissful ignorance :) You do not actually trust the archive, or the developers, you trust the silence. I trust special relativity, because nobody has disproven it yet. Really? I trust the theory of special relativity because there is enormous evidence supporting it, and little evidence against it. There is enormous evidence for the Aristotle' believe that more massive objects fall faster and little evidence against it. Only a carefully crafted experiment shows that it is false. In the case of there are no messages, therefore I trust the security of the system, that's faith â belief in spite of an utter lack of evidence. The predictions must be testable by everbody and - of course - some must actually try to falsify them. Exact binary matches would allow everbody to check the integrity of the binary packages and I am quite sure that some people would do it. In this case no messages stating that something is wrong is not the same as lack of evidence, it is actually evidence for the assumption that everything is ok. Do you think this is blissfull ignorance, too? Worse, it's foolish. It is foolish to base his trust purely on the authority of some person. People's belief that massive objects fall faster was based on the authority of Aristotle. Debian user's trust in the integrity of some binary package is based on the authority of the person putting a gpg signature on it. In the lack of *any* evidence either way on a question, it's foolish to hold any position but unknown; That is a common misbelief. Some things are inherently more probable than other. and, if the question is important for a matter of trust, it's imperative to *get* some evidence before extending any trust. That is certainly true. Martin
Re: Changing name of source package
* Francesco P. Lovergine [Thu, 27 Sep 2007 11:01:34 +0200]: On Wed, Sep 26, 2007 at 07:26:51PM -0700, Steve Langasek wrote: The only other thing you need to worry about is filing a bug report against ftp.debian.org to get the old php4-ps source package removed, since this won't happen automatically. If it is not still required in stable/oldstable isn't it? Removals by ftpmaster (whether of binaries, source, or both) normally happen against unstable only. The removal then propagates to testing, which means that the *next* stable release won't have them. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Joan Manuel Serrat - Algo personal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Building packages with exact binary matches
On Thu, Sep 27, 2007 at 02:26:49AM -0500, Manoj Srivastava wrote: On Wed, 26 Sep 2007 12:31:51 +0200, Martin Uecker [EMAIL PROTECTED] said: On Wed, Sep 26, 2007 at 12:25:02AM -0500, Manoj Srivastava wrote: Just because you have _heard_ anyone diss special relativity being the sole reason to believe in it is in the same ball park as blissful, you know, ignorance. It is not about hearsay. It is about finding an error in a predictation. And I do not care *who* finds the error. Of course the predications have actually be checked. So you are right with your argument, if nobody actually does this, it would be ignorant to believe in a scientifc theory for the sole reason that nobody complains. Similar, if nobody recompiles the packages and checks for mismatches, then silence would in fact not imply that things are ok. But I question your premise: I have no doubt that some people would actually recompile packages and compare the hash. Even if it is not done normally, somebody would do this if doubts come up for some reason (e.g. some debian hosts are compromised again.). This alone would actually be worth a lot. But recompiling from what? If you do not get the exact same source, you have no hope of getting the same result. I had the impression that Debian distributes the source code from which the binaries are actually compiled and not some random variation. And the way things work, the chances are that if the binary is tainted, the source would be tainted -- and you have got nowhere. If I wanted to hide a trojan somewhere I would to it in the binary and not in the source code. People actually look into source code on a regular basis but they seldom disassemble a binary. The difference is evidence. If there is some merit to the notion that a buildd is compromised, the solution is not bunches of people building from potentially tainted sources and comparing checksums. If know that the source code wich has hash 4457575757575 compiled in the build environment with hash 4837373737 gives a package with hash 366336363, then it is actually *evidence* that something is seriously wrong if you end up with a package with a different hash. So, someone replaces the binary compiled on the buildd with a fake one, in between the binary being built and it being signed? All the work to get bit-for-bit reproducibility for such a low priority attack vector? I do not think it is a low priority attack vector. If I would be a cracker and had a rootkit installed on a debian build host it would certainly insert a backdoor in ssh everytime it is compiled: Access to all debian running computers world wide! BTW I did some tests and for 'dpkg' the only files which change between builds are the manpages and that's just because gzip stores the date of the orginal in the compressed file. Martin
Releasing packages with 'pending' RC bugs
Hi, out of curiousity.. imagine a package where: * the Debian maintainer is also upstream maintainer * the package has practically no users (popcon 10) * the package has RC bugs * the RC bugs are fixed upstream * the RC bugs are tagged pending in the BTS * the fixed package doesn't get uploaded (e.g. due to ENOSPONSOR) If I am not wrong (otherwise please do correct me) such a package would enter testing on the normal way, and hence, would be part of the upcoming stable release. I don't know if many of these cases extists, but, are they actually dealt with somehow by someone, or are they currently slipping through? Regards, Daniel -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Releasing packages with 'pending' RC bugs
Daniel Baumann wrote, Thursday, September 27, 2007 11:43 AM out of curiousity.. imagine a package where: * the Debian maintainer is also upstream maintainer * the package has practically no users (popcon 10) * the package has RC bugs * the RC bugs are fixed upstream * the RC bugs are tagged pending in the BTS * the fixed package doesn't get uploaded (e.g. due to ENOSPONSOR) If I am not wrong (otherwise please do correct me) such a package would enter testing on the normal way, and hence, would be part of the upcoming stable release. You're wrong. Assuming that the RC bugs are not present in testing already, the testing scripts will not allow the package to migrate. Tagging bugs as pending does not stop them being RC and makes no difference to their impact on testing migration. If the package in testing is RC buggy it will get removed by the release team before release anyway. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging a library that requires cross-compiled code
On 9/27/07, Bernd Zeimetz [EMAIL PROTECTED] wrote: 4) Give up and stay away from the Debian main repositories, just put the package up on a private package repository. Please don't choose this way to solve the problem. Lego Mindstorms are used a lot for education, including universities, as it is just very easy to build objects with Lego bricks, so you have more time to think about the code then about how to handle metal or other raw material. I agree. As I said, I want to do things right if I can. Unfortunately I still have no clue about cross-compiling, but please let me know if you need any help with the python parts. Feel free to join #debian-python on OFTC, all questions regarding python apps/modules are welcome there Thanks, I'll be there, since I actually do have a few questions on that part as well. Imho one very fast way to solve the problem would be to package all the python tools, including fwflash - but without the actual firmware blob. Instead you ask the people to download the file or let the tool handle this automatically - at least this would make sure people are able to use your tools with mindstorms while you have enough time to figure out how to ship the precompiled firmware in a debian package. For example you could build the firmware package on arm only and let your tools download and extract the package. If you look at the previous version of my library, which is in C and builds with SCons ( http://code.google.com/p/libnxt/ ), in C I embedded the binary image directly into the source code before compiling, using a small python script. And that python script does detect the absence of the compiled firmware image, and asks the user whether the binary should be downloaded from code.google.com. The alternative is to abort the build, make the binary image locally, and rerun. While this is a workable solution, I find it annoying because it places part of the burden of packaging on the user, for an implementation detail. I have seen this kind of thing done before, but for licensing reasons (non-free firmware that cannot be bundled in the package), whereas this seems to be a purely technical issue. Could the same kind of thing be done at package creation time, ie. prompt the packager to either build or download a working version of the binary image when the package is built (or just download it automatically if non-interactive is required) ? The end result is the same, except that end users don't have to care any more, which is always nice. If you couldn't tell btw: I think that the first solution I mentionned would work well. The flash driver is tiny, and so trivial that it is highly unlikely that it will change in the future, so I consider bundling it a debian-specific fix to the upstream build system more than anything else (so that the packaging process doesn't need to download something from the web, which is what the python setup.py is likely going to do to get around the cross-compiler issue). - Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
I demand that Lars Wirzenius may or may not have written... [snip] Obfuscation which can easily be reversed by a human, but not so easily by a computer, does not render contact information incorrect. If I write my e-mail address as follows, it's still correct: My full name is Lars Ivar Wirzenius, and you can send me e-mail by taking my initials and putting them in front of the at sign and iki.fi after it. But is that LIW or liw or Liw or...? :-) [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Travel less. Share transport more. PRODUCE LESS CARBON DIOXIDE. A clean and tidy desk is a sign of a *very* sick mind. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
This one time, at band camp, Darren Salt said: I demand that Lars Wirzenius may or may not have written... [snip] Obfuscation which can easily be reversed by a human, but not so easily by a computer, does not render contact information incorrect. If I write my e-mail address as follows, it's still correct: My full name is Lars Ivar Wirzenius, and you can send me e-mail by taking my initials and putting them in front of the at sign and iki.fi after it. But is that LIW or liw or Liw or...? :-) I know it was a joke, but since email is (usually) case-insensitive, it won't matter in practice. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: Maintainer of package joystick may be missing
Dear Aníbal, I uploaded the button and axis remapping patch against joystick/20051019-1.1. This most recent patch also includes updates for the jscal manpage, documenting the new command line arguments. Thank you for your help. Best regards, Laszlo Kajan Aníbal Monsalve Salazar wrote: On Tue, Sep 25, 2007 at 05:24:14PM +0200, laszlo kajan wrote: Please show me the way I can have my patch included in jscal.c of the joystick package. I believe it is useful and I immediately wanted to share it with others. Please file a bug report (including the patch) against the joystick package. Aníbal Monsalve Salazar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
On Thu, Sep 27, 2007 at 12:59:18PM +0100, Stephen Gran wrote: This one time, at band camp, Darren Salt said: I demand that Lars Wirzenius may or may not have written... [snip] Obfuscation which can easily be reversed by a human, but not so easily by a computer, does not render contact information incorrect. If I write my e-mail address as follows, it's still correct: My full name is Lars Ivar Wirzenius, and you can send me e-mail by taking my initials and putting them in front of the at sign and iki.fi after it. But is that LIW or liw or Liw or...? :-) I know it was a joke, but since email is (usually) case-insensitive, it won't matter in practice. not at all. rfc2821 2.4 The local-part of a mailbox MUST BE treated as case sensitive. So, senders should use LIW@ but the MTA at the other end is free to accept liw@ and Liw@ etc ... ;-) Regards, Paddy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging a library that requires cross-compiled code
On Wed, Sep 26, 2007 at 06:38:02PM -0700, Steve Langasek wrote: (Otherwise, you'd be building the arch: all package from the binary-arch rule on arm only; this would work, but cause brain-twistiness wrt the separation between arch: all and arch: any.) sbuild does not allow this. Bastian -- If a man had a child who'd gone anti-social, killed perhaps, he'd still tend to protect that child. -- McCoy, The Ultimate Computer, stardate 4731.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Releasing packages with 'pending' RC bugs
Adam D. Barratt wrote: You're wrong. that... If the package in testing is RC buggy it will get removed by the release team before release anyway. and that is good to know, thanks for the correction/explenation ;) -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Proposed menu changes
On Fri, Sep 21, 2007 at 03:23:04AM -0500, Manoj Srivastava wrote: Hi, While in the process of working on a new fvwm package, I noticed that the Menu policy has changed some of the old titles to new I was hoping I had sufficiently advertised the proposal and the changes so that it would have reached you sooner. ones. For example, WindowManagers = Window Managers, Modules = FVWM Module (which is incorrect; the correct way to address the wm is Fvwm). In that case, please report a bug to debian-policy requesting the change. This is a trivial matter to fix. But this means that people who use Debian menus in fvwm have now got to change their .fvwm/.fvwmrc files; and use the new names. For example, + WindowManagers Popup /Debian/WindowManagers + FVWM Modules Popup /Debian/Modules nust become. + FVWM Modules Popup /Debian/FVWM_Modules + Window Managers Popup /Debian/Window_Managers So, with the new menu policy, Fvwm users have to edit their configuration files. Are there any plans for preserving backwards compatibility, or at least a transition plan? I would say it is a job for the menu-method, not for menu itself. Does FVWM allow to define aliases to menu section, or something similar? You could define WindowManagers as an alias for Window Managers, etc. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging a library that requires cross-compiled code
On Thu, Sep 27, 2007 at 02:59:16AM +0200, David Anderson wrote: 1) Ship a built copy of the code in the package's .diff.gz, and DTRT at package creation time to move the .bin from debian/ to the right place in the staging tree. The source code for the .bin is in .orig.tar.gz, under a free license. Anyone is free to modify or rebuild the .bin, provided they obtain an arm7 cross-compiler by non-debian means (instructions provided). People who just want to rebuild the package can do so, without caring that there is cross-compiled code involved. I think this is the way to go unless you get some concrete objections. There is certainly precedent - see for instance the ia32-libs / amd64-libs packages (which are frowned upon for whole different reasons). -- Daniel Jacobowitz CodeSourcery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
This one time, at band camp, [EMAIL PROTECTED] said: On Thu, Sep 27, 2007 at 12:59:18PM +0100, Stephen Gran wrote: This one time, at band camp, Darren Salt said: I demand that Lars Wirzenius may or may not have written... [snip] Obfuscation which can easily be reversed by a human, but not so easily by a computer, does not render contact information incorrect. If I write my e-mail address as follows, it's still correct: My full name is Lars Ivar Wirzenius, and you can send me e-mail by taking my initials and putting them in front of the at sign and iki.fi after it. But is that LIW or liw or Liw or...? :-) I know it was a joke, but since email is (usually) case-insensitive, it won't matter in practice. not at all. rfc2821 2.4 The local-part of a mailbox MUST BE treated as case sensitive. So, senders should use LIW@ but the MTA at the other end is free to accept liw@ and Liw@ etc ... However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged. Hence the '(usually) case-insensitive'. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: semi-virtual packages?
On Thu September 27 2007 01:33:21 am Manoj Srivastava wrote: On Wed, 26 Sep 2007 04:04:33 -0600, Bruce Sass [EMAIL PROTECTED] said: Hmm? You assumed, and I quote there are no such situations which would not already have a virtual package. Since there are situations where there is no virtual package, it certainly seems to me that the assumption you made is invalid. That is not correct, what I assumed was: a, no, to the above [question] What you quoted is not a primary assumption (as you've been treating it as), it is based on a condition having been met. If your assumption is correct, then I have missed something somewhere. The bit you're still missing is the first part of the question you didn't answer: Is there any situation where ownership has collided IOW: if the file shared by many packages isn't having ownership problems there is no need to consider it (no point trying to fix something that is not broken, eh). I don't see why it would need to be universal, one size stuff often doesn't fit anyone very well and it is not like being universal is pervasive and this would stand out as a wart. If we are not talking about a policy to be made, and you are only talking about an opt in scheme for some orphan files, then indeed, I have nothing to add to the conversation. s/some/all but a few/I suspect - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
On Thu, Sep 27, 2007 at 02:54:08PM +0100, Stephen Gran wrote: This one time, at band camp, [EMAIL PROTECTED] said: On Thu, Sep 27, 2007 at 12:59:18PM +0100, Stephen Gran wrote: This one time, at band camp, Darren Salt said: I demand that Lars Wirzenius may or may not have written... [snip] Obfuscation which can easily be reversed by a human, but not so easily by a computer, does not render contact information incorrect. If I write my e-mail address as follows, it's still correct: My full name is Lars Ivar Wirzenius, and you can send me e-mail by taking my initials and putting them in front of the at sign and iki.fi after it. But is that LIW or liw or Liw or...? :-) I know it was a joke, but since email is (usually) case-insensitive, it won't matter in practice. not at all. rfc2821 2.4 The local-part of a mailbox MUST BE treated as case sensitive. So, senders should use LIW@ but the MTA at the other end is free to accept liw@ and Liw@ etc ... However, exploiting the case sensitivity of mailbox local-parts impedes interoperability and is discouraged. Hence the '(usually) case-insensitive'. yes, I caught that '(usually)'. figured that was what you meant :-) I don't think that drawing the conclusion I did counts as exploiting the case sensititivity of mailbox local-parts, it being explictly covered in the passage I quoted, although I would agree that perhaps Lars should be discouraged from depending on this interpretation ... ;-) On the other hand, relying on the case-insensitivity of the local-part is explicitly broken, even if it works in practice :-) I'm so glad we have standards to make these things clear ;-) Regards, Paddy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: modified email address in debian/copyright file
Holger Levsen [EMAIL PROTECTED] writes: Whether or not it its an requirement to be able to contact the author, doesnt have anything to do with obfuscating the email address or not. (Assuming its not obfuscated beyond recognitition.) That just pushes the question to a different location, without answering it: what do we accept as a valid email address, and what do we categorise as so far obfuscated that it's no longer useful. It also puts one in the untenable position of having to make *individual* decisions on every case of obfuscation: is this one too far munged? Is that one? On what do I base my judgement of too far? I argue that the only fair place to draw the line is valid RFC 2821 email address. The alternative is to leave it to ongoing subjective judgement of unspecified Debian parties as to which addresses make sense or not — or to avoid the question of valid contact information altogether, as seems to be current practice. (*) BTW, I dont have an example at hand, but I'm pretty sure I have seen code in Debian written by anonymous and friends. You can't contact them either. I don't doubt that's true. It's a regrettable situation, because the copyright statement for that person's work is unverifiable even at the time the code is accepted into Debian, let alone later in the future. -- \ Eccles: I just saw the Earth through the clouds! Lew: Did | `\ it look round? Eccles: Yes, but I don't think it saw me. | _o__) -- The Goon Show, _Wings Over Dagenham_ | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging a library that requires cross-compiled code
David Anderson wrote: Therefore, question: how should I get from this situation to having a working .deb (including the cross-compiled driver), while at the same time playing nicely with Debian packaging policies? In the general case, the problem is much wider. Let me give you an example. We currently package Xen and other free virtualization solutions. Some of them can even run proprietary OSes, such as Windows. Now, suppose that one would like to improve the way Windows runs under Xen by writing, say, a custom mouse driver for Windows that para-virtualizes the mouse on Windows. Such things are quite common in todays' world. The problem is that this driver is a kernel level driver for Windows. If it were user space we could still claim it could be compiled with cross-mingw, but this is not the case here. Setting up an environment for compiling Windows kernel drivers merely so we can build this tiny blob seems out of proportion. I think we need a change in policy for handling cases where free software requires free software in order to compile which is, non the less, non buildable on the same platform. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging a library that requires cross-compiled code
Shachar Shemesh [EMAIL PROTECTED] wrote: I think we need a change in policy for handling cases where free software requires free software in order to compile which is, non the less, non buildable on the same platform. It exists already, it's called the contrib section of the archive. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: User-Agent strings, privacy and Debian browsers
Sorry for the late reply but currently I am porting a new architecture and have not very much time... Am 2007-09-21 18:03:05, schrieb Peter Eckersley: Consider for a moment a typical User-Agent string sent by a Debian web browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070802 Iceape/1.1.4 (Debian-1.1.4-1) Unfortunately, the fact that this information identifies a specific package and version of that package means that Debian users (already a select group) have their browsing identities further distinguished by their User-Agent strings. Which quiet helpful IF YOU NEED complex websites which MUST work with ANY browsers This means, in practice, that many sites will be able to track Debian users by their User-Agent, even if (say) the user is blocking cookies or limiting them to a single session and is changing IP address regularly. Tracking $USER is not possibel if you check the popularity-contest. Mean: there 100th of thousands Debian-User using the same Program. What do people think of picking a single User-Agent string for all versions of all of Debian's Gecko-based browsers? Which leed to errors while trying to resolv bugs. Would there be any serious harm in terms of browser debugging? Are there many sites which usefully treat different Gecko browsers differently? Yes, at least my Website an some Intranet-Sites of the french military... As a far more hypothetical question, what would people think of picking a single User-Agent for Gecko-based browsers for a larger set of GNU/Linux distributions? Obviously, there is much more politics there, because any distributions that joined would be losing the ability to measure their desktop market share by looking at web statistics. Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: User-Agent strings, privacy and Debian browsers
Am 2007-09-22 11:16:55, schrieb Peter Eckersley: But maybe you use open wifi networks, and other Debian users also use those networks. Maybe there are other Debian users behind your NAT. Maybe your friends come over sometimes and they also use Debian. In those cases, standardising the User-Agent string increases the size of your anonymity sets for various activities. ...and if you have a faulty browser in your network? (e.g. forgotten to make a security-update or an interrupted one) Thanks, Greetings and nice Day Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ # Debian GNU/Linux Consultant # Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/6192519367100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: Changing name of source package
On torsdagen den 27 september 2007, Francesco P. Lovergine wrote: On Wed, Sep 26, 2007 at 07:26:51PM -0700, Steve Langasek wrote: The only other thing you need to worry about is filing a bug report against ftp.debian.org to get the old php4-ps source package removed, since this won't happen automatically. If it is not still required in stable/oldstable isn't it? ftpmaster doesn't delete the source package, he just tells the system that the package is no longer wanted. When no suite references the package any longer, it is deleted, and _that_ part happens automatically. -- Magnus Holmgren[EMAIL PROTECTED] (No Cc of list mail needed, thanks) signature.asc Description: This is a digitally signed message part.
Bug#444334: ITP: libmowgli -- a high performance development framework for C
Package: wnpp Severity: wishlist Owner: Patrick Schoenfeld [EMAIL PROTECTED] * Package name: libmowgli Version : 0.4.0 Upstream Author : Atheme Project * URL : http://www.atheme-project.org/projects/mowgli.shtml * License : BSD Programming Lang: C Description : a high performance development framework for C mowgli is a development framework for C (like GLib), which provides high performance and highly flexible algorithms. It can be used as a suppliment to GLib (to add additional functions (dictionaries, hashes), or replace some of the slow GLib list manipulation functions), or stand alone. It also provides a powerful hook system and convenient logging for your code, as well as a high performance block allocator. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-k7 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Call for tests: new ThinkFinger package in experimental (PAM-0.99.7.1)
Hello! A new ThinkFinger [1] package has been uploaded to experimental [2]: this package was built with PAM in unstable and since a while it's working with no major problems on my sid. I wrote major because there're indeed some problems (links available at [2])... 1) not all the application that perform authentication supports ThinkFinger, the worst being screensavers and gksudo [3] 2) a really annoying problem is the SSH segfault [4]: this is still unsolved and could deserve an RC bug (but I'd go anyway to lenny for wider testing (comments welcome) So, this is call for people who have an UPEK/STMicroelectronics fingerprint reader (0483:2016), usually found either as a standalone USB device, built into USB keyboards or built into laptops (usually From Dell, IBM/Lenovo and Toshiba). Please test the package in experimental and report any (unknown) problem in the BTS. Otherwise, I'll upload the experimental package to unstable after 10 days from this mail (and after lenny to bakcports, too). Thx, bye, Gismo / Luca Footnotes: [1] http://thinkfinger.sourceforge.net [2] http://lists.alioth.debian.org/pipermail/fingerforce-devel/2007-September/07.html [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444059 [4] http://news.gmane.org/group/gmane.linux.drivers.thinkfinger/thread=434/force_load=t pgpaHyFt1flOb.pgp Description: PGP signature
Re: Building packages with exact binary matches
On Thu, 27 Sep 2007 11:28:47 +0200, Martin Uecker [EMAIL PROTECTED] said: On Thu, Sep 27, 2007 at 02:26:49AM -0500, Manoj Srivastava wrote: On Wed, 26 Sep 2007 12:31:51 +0200, Martin Uecker [EMAIL PROTECTED] said: On Wed, Sep 26, 2007 at 12:25:02AM -0500, Manoj Srivastava wrote: Just because you have _heard_ anyone diss special relativity being the sole reason to believe in it is in the same ball park as blissful, you know, ignorance. It is not about hearsay. It is about finding an error in a predictation. And I do not care *who* finds the error. Of course the predications have actually be checked. So you are right with your argument, if nobody actually does this, it would be ignorant to believe in a scientifc theory for the sole reason that nobody complains. Similar, if nobody recompiles the packages and checks for mismatches, then silence would in fact not imply that things are ok. But I question your premise: I have no doubt that some people would actually recompile packages and compare the hash. Even if it is not done normally, somebody would do this if doubts come up for some reason (e.g. some debian hosts are compromised again.). This alone would actually be worth a lot. But recompiling from what? If you do not get the exact same source, you have no hope of getting the same result. I had the impression that Debian distributes the source code from which the binaries are actually compiled and not some random variation. Yup, complete with all the trojans in the binary and all. And the way things work, the chances are that if the binary is tainted, the source would be tainted -- and you have got nowhere. If I wanted to hide a trojan somewhere I would to it in the binary and not in the source code. People actually look into source code on a regular basis but they seldom disassemble a binary. The window of opportunity is small. You have to replace the binary .deb in between the time it was built, and it was signed. The difference is evidence. If there is some merit to the notion that a buildd is compromised, the solution is not bunches of people building from potentially tainted sources and comparing checksums. If know that the source code wich has hash 4457575757575 compiled in the build environment with hash 4837373737 gives a package with hash 366336363, then it is actually *evidence* that something is seriously wrong if you end up with a package with a different hash. So, someone replaces the binary compiled on the buildd with a fake one, in between the binary being built and it being signed? All the work to get bit-for-bit reproducibility for such a low priority attack vector? I do not think it is a low priority attack vector. If I would be a cracker and had a rootkit installed on a debian build host it would certainly insert a backdoor in ssh everytime it is compiled: Access to all debian running computers world wide! Compromise gcc? I see. So, fro all you know, every copy of gcc in the world now has the compile trojan into ssh built in, and again, no way for people peering at bits to see if there is a trojan buried in there to find out. BTW I did some tests and for 'dpkg' the only files which change between builds are the manpages and that's just because gzip stores the date of the orginal in the compressed file. This is one of the things, yes. ANy package with a tar archive would suffer similarly. manoj -- The bug starts here. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: semi-virtual packages?
On Thu, 27 Sep 2007 08:08:49 -0600, Bruce Sass [EMAIL PROTECTED] said: The bit you're still missing is the first part of the question you didn't answer: Is there any situation where ownership has collided IOW: if the file shared by many packages isn't having ownership problems there is no need to consider it (no point trying to fix something that is not broken, eh). The start of this thread was a rant about not loose files floating around in /etc; not necessarily about whether these files in themselves had ownership problems (whtever that means). Here is the original context. Note how you say the problem (actually, design flaw) is about current tools do not catch files created by Maintainer scripts? Nice to see the design flaw has become stuff that is not broken and does not have to be fixed. That is all I cared about, really. manoj On Fri, 21 Sep 2007 03:25:23 + (UTC), Oleg Verych (Gmane) [EMAIL PROTECTED] said: 19-09-2007, Bruce Sass: [] I like this too. Finding what a package has just installed is one of the biggest holes in Debian right now, IMO. I have to use dpkg -L to figure this out, and that's just too crude to be a real solution. Too crude? That's a simple command, easily found in a relevant manpage. In true Unix fashion, its output can be easily piped to other commands. What's crude about it? It doesn't catch files created by Maintainer scripts? This is the design flaw in those scripts (even in whole package management). -- You know how to win a victory, Hannibal, but not how to use it. Maharbal Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: semi-virtual packages?
On Thu September 27 2007 05:38:53 pm Manoj Srivastava wrote: On Thu, 27 Sep 2007 08:08:49 -0600, Bruce Sass [EMAIL PROTECTED] said: The bit you're still missing is the first part of the question you didn't answer: Is there any situation where ownership has collided IOW: if the file shared by many packages isn't having ownership problems there is no need to consider it (no point trying to fix something that is not broken, eh). The start of this thread was a rant about not loose files floating around in /etc; not necessarily about whether these files in themselves had ownership problems (whtever that means). Here is the original context. Note how you say the problem (actually, design flaw) is about current tools do not catch files created by Maintainer scripts? Nice to see the design flaw has become stuff that is not broken and does not have to be fixed. That is all I cared about, really. Oleg considers it a design flaw, I have stated no such opinion and didn't even include his statement to that effect in my reply. Why would you bring it up... grasping at straws, perhaps. The original context I was responding to, and which you jumped in on, is this: - On Sat, 22 Sep 2007 03:46:26 -0600, Bruce Sass [EMAIL PROTECTED] said: On Sat September 22 2007 12:16:18 am Oleg Verych (Gmane) wrote: 21-09-2007, Bruce Sass: On Thu September 20 2007 09:25:23 pm Oleg Verych (Gmane) wrote: 19-09-2007, Bruce Sass: I'm hoping the dpkg triggers functionality Ian Jackson has been working on will help solve that wart though. How exactly? Exactly? I don't know. I haven't followed what is happening close enough. Basically, it allows a package to toss up a flag saying, `I'm here and something needs to be done.' It may require some convention and a little more infrastructure, but that is close to letting a package say, `add these paths to the list of paths which I control.' Sure. But i thought, we are talking about finding/listing of generated files. It is not feasible (imo) to automatically find files created by maintainer scripts. Having packages append package.list themselves would (afaict) require they know too much about dpkg's internal operation, and all packages generating files would need to implement the algorithm. However, maintainer scripts can easily pass a list of generated paths on to a shared piece of code which dpkg controls. triggers looks like it could be the mechanism by which a package flags that it has generated files, and by which dpkg exerts control. But this does not address the case of a file shared by many packages but really owned by none. manoj - You then proceeded to demonstrate that you: have trouble reading, following arguments, keeping track of what your own use case actually is, and using logic. You are now finishing up with misquotes and misrepresentation of anothers position. Do you wonder why you get in so many fights and pointless arguments. :-/ Bye-bye, and I wish you luck in whatever little fantasy world you've constructed for yourself. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Intent to remove libxaw6 from Debian [security issues]
Dear Debian Developers,
the X Strike Force intends to remove libxaw6 from the archive.
The reason is explained in bug #172890. In short, libxaw6 has a
security flaw where it displays passwords in plain text.
The flaw is fixed in libxaw7. All packages in Debian now use libxaw7
rather than libxaw6. We therefore consider it prudent to remove libxaw6
from the archive to avert any possible future misuses.
This has the potential to impact on any third party packages which use
libxaw6. We don't believe this should annul the package's removal
however, because
a) these packages should be rebuilt against libxaw7 anyway, and
b) libxaw6 can still be taken from etch if really needed.
The LSB does not specify any requirements for libxaw (v7 or otherwise).
Please let us know (by replying to bug #172890) if you have any
objections or can otherwise present an argument in favour of keeping
libxaw6.
Otherwise, we will remove it in a week or so.
Drew Parsons
\hat{XSF}
signature.asc
Description: This is a digitally signed message part
Bug#444368: ITP: dvd95 -- DVD9 to DVD5 converter
Package: wnpp Severity: wishlist Owner: Carlos Laviola [EMAIL PROTECTED] * Package name: dvd95 Version : 1.2p1 Upstream Author : J. F. Coulon [EMAIL PROTECTED] * URL : http://dvd95.sourceforge.net/ * License : GPL Programming Lang: C Description : DVD9 to DVD5 converter dvd95 is a GNOME application to convert DVD9 to DVD5 (4.7GB). * Needs no additional packages - embedded versions of vamps and dvdauthor are used, to be as fast as possible. * Interface is pretty simple to use. * Shrinking factor may be computed for best results, or an adaptive compression ratio method may be used. * DVDs can be converted to file trees or ISOs. * The end result can be viewed and burned with regular third party players and DVD recording software. * DVD95 supports two copy modes: - Without menus, one video title set, multiple audio tracks and subtitles. - With menus, one video title set, multiple audio tracks and subtitles. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (999, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#444368: ITP: dvd95 -- DVD9 to DVD5 converter
On Thu, 2007-09-27 at 23:26 -0300, Carlos Laviola wrote: * Needs no additional packages - embedded versions of vamps and dvdauthor are used, to be as fast as possible. Please notify the Debian security team so they can add dvd95, vamps, dvdauthor to their list of packages with duplicated code. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Re: User-Agent strings, privacy and Debian browsers
Peter Eckersley wrote: Consider for a moment a typical User-Agent string sent by a Debian web browser: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070802 Iceape/1.1.4 (Debian-1.1.4-1) Unfortunately, the fact that this information identifies a specific package and version of that package means that Debian users (already a select group) have their browsing identities further distinguished by their User-Agent strings. ... What do people think of picking a single User-Agent string for all versions of all of Debian's Gecko-based browsers? From the other responses, it seems clear that we do not want to do this for technical reasons. Your concern addresses a potential social problem, not a technical problem. Perhaps you will have more success getting us to appreciate what you're trying to say if you can explain it more thoroughly in social terms? That is, what problem are you trying to solve exactly? Can you provide actual examples where identification by User-Agent has led to tangible harm, or may be reasonably expected to lead to harm in the near future, rather than than simply being some hypothetical tool open to abuse by some future tyrannical government or corporation? If we can be convinced the actual danger is real, then the technical solution is of course trivial. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bluez-libs 3.19-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 08:47:11 +0200 Source: bluez-libs Binary: libbluetooth2 libbluetooth-dev Architecture: source i386 Version: 3.19-1 Distribution: unstable Urgency: low Maintainer: Debian Bluetooth Maintainers [EMAIL PROTECTED] Changed-By: Mario Iseli [EMAIL PROTECTED] Description: libbluetooth-dev - Development files for using the BlueZ Linux Bluetooth library libbluetooth2 - Library to use the BlueZ Linux Bluetooth stack Changes: bluez-libs (3.19-1) unstable; urgency=low . * New upstream release. * Added XS-Vcs-* fields in debian/control. * Added a debian/watch file. Files: 7637bbf64b41450f7802720344777b8b 910 admin optional bluez-libs_3.19-1.dsc 40106bf5263e75c47d5033ae5085b6e2 309088 admin optional bluez-libs_3.19.orig.tar.gz 8aaff394591910a9d90a9d8e1f3d99d3 4570 admin optional bluez-libs_3.19-1.diff.gz 88edcd6cc088146dddcf46e8f4361159 66370 libdevel extra libbluetooth-dev_3.19-1_i386.deb a1897dd76f0a9e24b3ea3dadd1844e17 42926 libs optional libbluetooth2_3.19-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+14lJ9EDSN0bDvcRAofqAJ4oB5mc2qQ0UkLcLB2pObB3WxVWwgCePu5r oYLMOScK/D0h4DcJtH+59mA= =h5UA -END PGP SIGNATURE- Accepted: bluez-libs_3.19-1.diff.gz to pool/main/b/bluez-libs/bluez-libs_3.19-1.diff.gz bluez-libs_3.19-1.dsc to pool/main/b/bluez-libs/bluez-libs_3.19-1.dsc bluez-libs_3.19.orig.tar.gz to pool/main/b/bluez-libs/bluez-libs_3.19.orig.tar.gz libbluetooth-dev_3.19-1_i386.deb to pool/main/b/bluez-libs/libbluetooth-dev_3.19-1_i386.deb libbluetooth2_3.19-1_i386.deb to pool/main/b/bluez-libs/libbluetooth2_3.19-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted koffice 1:1.6.3-3 (source all amd64)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 26 Sep 2007 23:29:24 +0200
Source: koffice
Binary: koffice-data kivio koffice kugar kchart karbon kpresenter koffice-dbg
kformula koffice-libs koshell kivio-data kspread kword koffice-doc krita
krita-data kexi koffice-dev kword-data kthesaurus koffice-doc-html kplato
kpresenter-data
Architecture: source amd64 all
Version: 1:1.6.3-3
Distribution: unstable
Urgency: high
Maintainer: Debian Qt/KDE Maintainers [EMAIL PROTECTED]
Changed-By: Ana Beatriz Guerrero Lopez [EMAIL PROTECTED]
Description:
karbon - a vector graphics application for the KDE Office Suite
kchart - a chart drawing program for the KDE Office Suite
kexi - integrated database environment for the KDE Office Suite
kformula - a formula editor for the KDE Office Suite
kivio - a flowcharting program for the KDE Office Suite
kivio-data - data files for Kivio flowcharting program
koffice- KDE Office Suite
koffice-data - common shared data for the KDE Office Suite
koffice-dbg - debugging symbols for koffice
koffice-dev - common libraries for KOffice (development files)
koffice-doc - developer documentation for the KDE Office Suite
koffice-doc-html - KDE Office Suite documentation in HTML format
koffice-libs - common libraries and binaries for the KDE Office Suite
koshell- the KDE Office Suite workspace
kplato - an integrated project management and planning tool
kpresenter - a presentation program for the KDE Office Suite
kpresenter-data - data files for KPresenter presentation program
krita - a pixel-based image manipulation program for the KDE Office Suite
krita-data - data files for Krita painting program
kspread- a spreadsheet for the KDE Office Suite
kthesaurus - thesaurus for the KDE Office Suite
kugar - a business report maker for the KDE Office Suite
kword - a word processor for the KDE Office Suite
kword-data - data files for KWord word processor
Closes: 443673 444014
Changes:
koffice (1:1.6.3-3) unstable; urgency=high
.
* Patch for stack-based buffer overflow in the StreamPredictor::getNextLine
function in xpd that might allow remote attackers to execute arbitrary code
via a crafted PDF file. CVE-2007-504. (Closes: #444014)
* Update section in Debian menu files.
* Install kexi example /usr/share/apps/kexi/examples/Simple_Database.kexi
* Install libkrita*.{la,so} files to allow build external plugins.
(Closes: #443673)
* Add not-installed.list file to keep track of not installed files.
* Add a missing dependency on kcontrol to kformula, in order to provide the
fonts kioslave. Thanks to Eike Hein for reporting.
Files:
0ef5567567fef064d038714344c06493 1448 kde optional koffice_1.6.3-3.dsc
76e8cd407454ea3c64b56ebddce32d8d 1230471 kde optional koffice_1.6.3-3.diff.gz
eef90f444ecd64f353b6f3113f10d123 17174 kde optional koffice_1.6.3-3_all.deb
193dfc9181c35b7b58e2c3a06c6d08b6 100913348 doc optional
koffice-doc_1.6.3-3_all.deb
027eca2df4ed1e8d167588f23bb1a9a6 537050 doc optional
koffice-doc-html_1.6.3-3_all.deb
23ca002df06e7b72734b0bda30c6f837 689492 graphics optional
kivio-data_1.6.3-3_all.deb
62407d2c1aa52bd999b4879341abf081 1912310 kde optional
kpresenter-data_1.6.3-3_all.deb
c80e46ca19b6f9fdc8c29ebe7e32398f 28325580 kde optional
krita-data_1.6.3-3_all.deb
8cb26cfdc85840280dc759294d192137 1818474 kde optional
kword-data_1.6.3-3_all.deb
d91ea5fa77295c7bd6cc653d8dcfa763 745000 libs optional
koffice-data_1.6.3-3_all.deb
732788d8e0f2ca50a220aa4cae6d3bad 1072692 graphics optional
karbon_1.6.3-3_amd64.deb
e751b65b6e3d45cafdc35fe3a299c999 1375734 kde optional kchart_1.6.3-3_amd64.deb
1c2c850ef364841d1a44fc9eef9a4958 3737244 kde optional kexi_1.6.3-3_amd64.deb
1b315ca83d0440f007a3fc21867f5282 1035596 kde optional
kformula_1.6.3-3_amd64.deb
6337545e9601ec46df9d22b59b84dc4f 619712 graphics optional
kivio_1.6.3-3_amd64.deb
ffc5e6edb58c37b52251e988846e8ed9 189858 kde optional koshell_1.6.3-3_amd64.deb
c258df4c208fc1ab918de9cdf2b2c167 957600 kde optional kplato_1.6.3-3_amd64.deb
5e526024bff749b354a6285e2f01736d 1353140 kde optional
kpresenter_1.6.3-3_amd64.deb
119ccb061b91ca0e19f8ace81eb96ef4 3435812 kde optional krita_1.6.3-3_amd64.deb
243ad082a6c5566b45161b465af297ac 2743054 kde optional kspread_1.6.3-3_amd64.deb
c104c148a3b3d789c623eb7598f93ddb 460458 kde optional kugar_1.6.3-3_amd64.deb
6008cb241bff5929de964cda4a142534 2890142 kde optional kword_1.6.3-3_amd64.deb
84eff79f369cf9c2163cf013e2ae21e9 322322 kde optional
kthesaurus_1.6.3-3_amd64.deb
53c1b14c20eec6c9ed98639652469399 2740498 libs optional
koffice-libs_1.6.3-3_amd64.deb
03879598c3a81f69980c9cad1a03f07b 432810 libdevel optional
koffice-dev_1.6.3-3_amd64.deb
8bb9e1786b8f86c9252ddaa4a378dea5 109371948 libdevel extra
koffice-dbg_1.6.3-3_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Signed by Ana Guerrero
Accepted qt-x11-free 3:3.3.7-9 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Sep 2007 21:42:24 +0200 Source: qt-x11-free Binary: libqt3-i18n qt3-apps-dev libqt3-mt-sqlite qt-x11-free-dbg qt3-assistant qt3-examples qt3-doc libqt3-headers libqt3-mt-mysql libqt3-mt libqt3-mt-odbc libqt3-compat-headers qt3-dev-tools-embedded qt3-dev-tools libqt3-mt-ibase qt3-designer qt3-linguist qt3-qtconfig qt3-dev-tools-compat libqt3-mt-dev libqt3-mt-psql Architecture: source amd64 all Version: 3:3.3.7-9 Distribution: unstable Urgency: low Maintainer: Debian Qt/KDE Maintainers [EMAIL PROTECTED] Changed-By: Sune Vuorela [EMAIL PROTECTED] Description: libqt3-compat-headers - Qt 1.x and 2.x compatibility includes libqt3-headers - Qt3 header files libqt3-i18n - i18n files for Qt3 library libqt3-mt - Qt GUI Library (Threaded runtime version), Version 3 libqt3-mt-dev - Qt development files (Threaded) libqt3-mt-ibase - InterBase/FireBird database driver for Qt3 (Threaded) libqt3-mt-mysql - MySQL database driver for Qt3 (Threaded) libqt3-mt-odbc - ODBC database driver for Qt3 (Threaded) libqt3-mt-psql - PostgreSQL database driver for Qt3 (Threaded) libqt3-mt-sqlite - SQLite database driver for Qt3 (Threaded) qt-x11-free-dbg - debugging symbols for qt-x11-free binaries qt3-apps-dev - Qt3 Developer applications development files qt3-assistant - The Qt3 assistant application qt3-designer - Qt3 Designer qt3-dev-tools - Qt3 development tools qt3-dev-tools-compat - Conversion utilities for Qt3 development qt3-dev-tools-embedded - Tools to develop embedded Qt applications qt3-doc- Qt3 API documentation qt3-examples - Examples for Qt3 qt3-linguist - The Qt3 Linguist qt3-qtconfig - The Qt3 Configuration Application Changes: qt-x11-free (3:3.3.7-9) unstable; urgency=low . * Trust dpkg-architecture better than uname -m for the build key. Make mappings to not break current binary compability. Add patch 72 for that. Thanks to Bastian Blank for often changing uname -m on his buildds to discover this bug. Files: 40f788aff93b6e2be297030d509da070 1780 libs optional qt-x11-free_3.3.7-9.dsc 64acdbe49ed5f352ba50d8b813ff11b6 238085 libs optional qt-x11-free_3.3.7-9.diff.gz 18c53318124009684fca850f20412f3b 130810 libs optional libqt3-i18n_3.3.7-9_all.deb 7db53edc2c5a694a3d2870f265835d28 5612618 doc extra qt3-doc_3.3.7-9_all.deb ed3eb9b894165ce0d90939b95f7ea024 1587674 doc extra qt3-examples_3.3.7-9_all.deb fd1b76fe278667b4b92d31077ec660ea 3648894 libs optional libqt3-mt_3.3.7-9_amd64.deb 4bacb8f2e813cbae6b3347c2bf8bdb88 52562 libs optional libqt3-mt-mysql_3.3.7-9_amd64.deb 5e47c4e66ef68d07efe26869dbdcbce7 76626 libs optional libqt3-mt-odbc_3.3.7-9_amd64.deb 7794e31c789fd0f3233cfbf4b2fd0bdc 58298 libs optional libqt3-mt-psql_3.3.7-9_amd64.deb 81213f122c773fc6a2dd3fdc7bbc53fe 59420 libs optional libqt3-mt-ibase_3.3.7-9_amd64.deb cd49eb7d941a8da49e5978fc63a4bce2 220984 libs optional libqt3-mt-sqlite_3.3.7-9_amd64.deb fc25ceaa7a0a425399f415ffacbefdc1 47678 libdevel optional libqt3-mt-dev_3.3.7-9_amd64.deb 8657deffe3b710330c22db48b1548832 364626 devel optional libqt3-headers_3.3.7-9_amd64.deb e6685333ecbdb9493e05ce25439058ab 77308 devel optional libqt3-compat-headers_3.3.7-9_amd64.deb 9483d6698759267ff88092a1a88a75ac 1312530 devel optional qt3-dev-tools_3.3.7-9_amd64.deb d04aa506103519491dd146feb241863f 4237152 devel optional qt3-designer_3.3.7-9_amd64.deb 8c7acfa41e320e3df6c034fb609e1528 2725196 devel optional qt3-apps-dev_3.3.7-9_amd64.deb aa2340bd5270172944840ab33a693812 365660 devel optional qt3-linguist_3.3.7-9_amd64.deb 1a26d2f2f81807ada4c9247df75f9065 261084 x11 optional qt3-assistant_3.3.7-9_amd64.deb a6fe9bd639abd50ec3f0b3c6dcd5fb62 106694 x11 optional qt3-qtconfig_3.3.7-9_amd64.deb 30ae5bc121071e002fb497c5035009e7 298962 devel optional qt3-dev-tools-embedded_3.3.7-9_amd64.deb 9a3468309839084a10bbe1687f48c563 75448 devel optional qt3-dev-tools-compat_3.3.7-9_amd64.deb b16e7974efc0756b4ba41b0e09b4bd6a 64862546 libdevel extra qt-x11-free-dbg_3.3.7-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Signed by Ana Guerrero iD8DBQFG+3Fxn3j4POjENGERAhP8AJ9NP9pwlncVk+gZbS6CJkzMhK+7HgCdFlry cnhZmIMp3/UEIA8a5eLcO2g= =y/L6 -END PGP SIGNATURE- Accepted: libqt3-compat-headers_3.3.7-9_amd64.deb to pool/main/q/qt-x11-free/libqt3-compat-headers_3.3.7-9_amd64.deb libqt3-headers_3.3.7-9_amd64.deb to pool/main/q/qt-x11-free/libqt3-headers_3.3.7-9_amd64.deb libqt3-i18n_3.3.7-9_all.deb to pool/main/q/qt-x11-free/libqt3-i18n_3.3.7-9_all.deb libqt3-mt-dev_3.3.7-9_amd64.deb to pool/main/q/qt-x11-free/libqt3-mt-dev_3.3.7-9_amd64.deb libqt3-mt-ibase_3.3.7-9_amd64.deb to pool/main/q/qt-x11-free/libqt3-mt-ibase_3.3.7-9_amd64.deb libqt3-mt-mysql_3.3.7-9_amd64.deb to pool/main/q/qt-x11-free/libqt3-mt-mysql_3.3.7-9_amd64.deb libqt3-mt-odbc_3.3.7-9_amd64.deb to pool/main/q/qt-x11-free/libqt3-mt-odbc_3.3.7-9_amd64.deb
Accepted libpreludedb 0.9.13-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 10:49:16 +0200 Source: libpreludedb Binary: libpreludedb-perl libpreludedb-dev libpreludedb0 python-preludedb Architecture: source amd64 Version: 0.9.13-2 Distribution: unstable Urgency: low Maintainer: Mickael Profeta [EMAIL PROTECTED] Changed-By: Pierre Chifflier [EMAIL PROTECTED] Description: libpreludedb-dev - Hybrid Intrusion Detection System [ Development files ] libpreludedb-perl - Hybrid Intrusion Detection System [ Base library ] libpreludedb0 - Hybrid Intrusion Detection System [ Base library ] python-preludedb - Hybrid Intrusion Detection System [ Base library ] Changes: libpreludedb (0.9.13-2) unstable; urgency=low . * Backport patch r9907 from upstream: revent MySQL session from timing out after 8 hours of inactivity. Files: 97948fc1b204b4596a7ff1997806c04b 863 libs extra libpreludedb_0.9.13-2.dsc 87c25348aea0ae7d34668915c30d523d 3681 libs extra libpreludedb_0.9.13-2.diff.gz a22f0d8a6573cc2fcd627085ae018c63 23538 libdevel extra libpreludedb-dev_0.9.13-2_amd64.deb 4e21f3a178e8099089b7d71c1c47c873 145730 libs extra libpreludedb0_0.9.13-2_amd64.deb c969d1dc546bb124cb5ec591d20b5cc5 68368 perl extra libpreludedb-perl_0.9.13-2_amd64.deb 09129821e471e4329d0de4f0217213b3 83692 python extra python-preludedb_0.9.13-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+32RtwVrWo1fQMsRAvyoAJ46kox50tBOq+rCXJp8GLsaPT+WCgCeIG4T Xr+wpvyYIs9+acR5/k5xyVg= =z2JD -END PGP SIGNATURE- Accepted: libpreludedb-dev_0.9.13-2_amd64.deb to pool/main/libp/libpreludedb/libpreludedb-dev_0.9.13-2_amd64.deb libpreludedb-perl_0.9.13-2_amd64.deb to pool/main/libp/libpreludedb/libpreludedb-perl_0.9.13-2_amd64.deb libpreludedb0_0.9.13-2_amd64.deb to pool/main/libp/libpreludedb/libpreludedb0_0.9.13-2_amd64.deb libpreludedb_0.9.13-2.diff.gz to pool/main/libp/libpreludedb/libpreludedb_0.9.13-2.diff.gz libpreludedb_0.9.13-2.dsc to pool/main/libp/libpreludedb/libpreludedb_0.9.13-2.dsc python-preludedb_0.9.13-2_amd64.deb to pool/main/libp/libpreludedb/python-preludedb_0.9.13-2_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted poppler 0.5.4-6.2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Sep 2007 18:40:41 +0200 Source: poppler Binary: libpoppler-glib-dev poppler-utils libpoppler-qt4-dev libpoppler-qt1 libpoppler1 libpoppler-glib1 libpoppler-qt4-1 libpoppler-dev libpoppler-qt-dev Architecture: source i386 Version: 0.5.4-6.2 Distribution: unstable Urgency: high Maintainer: OndÅej Surý [EMAIL PROTECTED] Changed-By: Nico Golde [EMAIL PROTECTED] Description: libpoppler-dev - PDF rendering library -- development files libpoppler-glib-dev - PDF rendering library -- development files (GLib interface) libpoppler-glib1 - PDF rendering library (GLib-based shared library) libpoppler-qt-dev - PDF rendering library -- development files (Qt 3 interface) libpoppler-qt1 - PDF rendering library (Qt 3 based shared library) libpoppler-qt4-1 - PDF rendering library (Qt 4 based shared library) libpoppler-qt4-dev - PDF rendering library -- development files (Qt 4 interface) libpoppler1 - PDF rendering library poppler-utils - PDF utilitites (based on libpoppler) Closes: 443903 Changes: poppler (0.5.4-6.2) unstable; urgency=high . * Non-maintainer upload by testing security team. * Renamed CVE-2007-3387.patch to CVE-2007-3387_2007-5049.patch and fix a buffer overflow in StreamPredictor::getNextLine as well (CVE-2007-5049) (Closes: #443903). Files: ade318cd6a21327d721ae30ea58b7a30 1087 devel optional poppler_0.5.4-6.2.dsc 301d37d5d5a30968cbd51de327ff5588 10163 devel optional poppler_0.5.4-6.2.diff.gz 9ac76631df863e0e511f1eb439e46721 576632 libs optional libpoppler1_0.5.4-6.2_i386.deb b29b33f4a2f5b6b3f7f027a67f1e568f 763730 libdevel optional libpoppler-dev_0.5.4-6.2_i386.deb 5114f43c63cd3977ad2e55d5d6817dc8 72074 libs optional libpoppler-glib1_0.5.4-6.2_i386.deb ab693e35b20ce8a273ddeb546da11f15 100232 libdevel optional libpoppler-glib-dev_0.5.4-6.2_i386.deb a530ee70b5be94ec8c8752d2565abd29 60358 libs optional libpoppler-qt1_0.5.4-6.2_i386.deb 3d527a1a50373fc0908f23fb8d5b914c 64492 libdevel optional libpoppler-qt-dev_0.5.4-6.2_i386.deb fac1ef7a51b5bf1c7f2d37025c1c3bd9 152994 libs optional libpoppler-qt4-1_0.5.4-6.2_i386.deb 2d26149c0eaa62249bc7fa316a4f0ea3 174450 libdevel optional libpoppler-qt4-dev_0.5.4-6.2_i386.deb a238ded2b3b452a47b30d72455741567 101184 utils optional poppler-utils_0.5.4-6.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+37PHYflSXNkfP8RAtpLAJ9ziln/xaUd6SoTMKgWBlasn4dy6gCgoOqR az3uuaJpW4qVvEq7Pp9aJqU= =H4eA -END PGP SIGNATURE- Accepted: libpoppler-dev_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-dev_0.5.4-6.2_i386.deb libpoppler-glib-dev_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-glib-dev_0.5.4-6.2_i386.deb libpoppler-glib1_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-glib1_0.5.4-6.2_i386.deb libpoppler-qt-dev_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-qt-dev_0.5.4-6.2_i386.deb libpoppler-qt1_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-qt1_0.5.4-6.2_i386.deb libpoppler-qt4-1_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-qt4-1_0.5.4-6.2_i386.deb libpoppler-qt4-dev_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler-qt4-dev_0.5.4-6.2_i386.deb libpoppler1_0.5.4-6.2_i386.deb to pool/main/p/poppler/libpoppler1_0.5.4-6.2_i386.deb poppler-utils_0.5.4-6.2_i386.deb to pool/main/p/poppler/poppler-utils_0.5.4-6.2_i386.deb poppler_0.5.4-6.2.diff.gz to pool/main/p/poppler/poppler_0.5.4-6.2.diff.gz poppler_0.5.4-6.2.dsc to pool/main/p/poppler/poppler_0.5.4-6.2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xpdf 3.02-1.2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 12:05:46 +0200 Source: xpdf Binary: xpdf-utils xpdf xpdf-reader xpdf-common Architecture: source i386 all Version: 3.02-1.2 Distribution: unstable Urgency: high Maintainer: Hamish Moffatt [EMAIL PROTECTED] Changed-By: Nico Golde [EMAIL PROTECTED] Description: xpdf - Portable Document Format (PDF) suite xpdf-common - Portable Document Format (PDF) suite -- common files xpdf-reader - Portable Document Format (PDF) suite -- viewer for X11 xpdf-utils - Portable Document Format (PDF) suite -- utilities Closes: 443906 Changes: xpdf (3.02-1.2) unstable; urgency=high . * Non-maintainer upload by testing security team. * Removed post-3.5.7-kdegraphics-CVE-2007-3387.diff.dpatch and created fix-CVE-2007-3387_CVE-2007-5049.dpatch to have a fix for CVE-2007-3387 and a buffer overflow in GetNextLine() (CVE-2007-5049) since they are related (Closes: #443906). Files: 50c13160501a01e8555609e16d001858 872 text optional xpdf_3.02-1.2.dsc 45b886c40fd8ab8ea3be692623eab692 33071 text optional xpdf_3.02-1.2.diff.gz 89a860e937c9a9da201310ddb2443d47 1264 text optional xpdf_3.02-1.2_all.deb 51f888e60024b3cd39017abb1d806858 65176 text optional xpdf-common_3.02-1.2_all.deb 0a34f94517da8ceb7a8c43972339d413 862770 text optional xpdf-reader_3.02-1.2_i386.deb fd10215b671d194f813fd0aced787dcf 1584826 text optional xpdf-utils_3.02-1.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+4ivHYflSXNkfP8RAhGZAJ9FbAn791zEIomWADbeJBenkD+WzQCeN4ir 3CuL2Etdm9AnAjHIeFfJq3w= =VTfb -END PGP SIGNATURE- Accepted: xpdf-common_3.02-1.2_all.deb to pool/main/x/xpdf/xpdf-common_3.02-1.2_all.deb xpdf-reader_3.02-1.2_i386.deb to pool/main/x/xpdf/xpdf-reader_3.02-1.2_i386.deb xpdf-utils_3.02-1.2_i386.deb to pool/main/x/xpdf/xpdf-utils_3.02-1.2_i386.deb xpdf_3.02-1.2.diff.gz to pool/main/x/xpdf/xpdf_3.02-1.2.diff.gz xpdf_3.02-1.2.dsc to pool/main/x/xpdf/xpdf_3.02-1.2.dsc xpdf_3.02-1.2_all.deb to pool/main/x/xpdf/xpdf_3.02-1.2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bzr 0.91-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 12:25:43 +0200 Source: bzr Binary: bzr Architecture: source i386 Version: 0.91-2 Distribution: unstable Urgency: low Maintainer: Debian Bazaar Maintainers [EMAIL PROTECTED] Changed-By: Reinhard Tartler [EMAIL PROTECTED] Description: bzr- Bazaar, the next-generation distributed version control system Changes: bzr (0.91-2) unstable; urgency=low . * remove python-celementree and python-paramiko from build-depends. rationale: - python-celementree is purely an optimisation for python2.4, and is already included in python2.5 - python-paramiko is not used during build at all. However, the testsuite currently fails when paramiko is not installed (see also #59150 in launchpad.net for details). Since we currently don't run the testsuite by default on the buildds, it is safe to remove that dependency, at least for now. Files: d939df464ba092e0265791e11b4f5481 985 devel optional bzr_0.91-2.dsc 0e04f06c5d44a42d96e748150d061e73 9368 devel optional bzr_0.91-2.diff.gz d610acfb6783c7feb72c738564f262d0 2164496 devel optional bzr_0.91-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Debian Powered! iD8DBQFG+4qsmAg1RJRTSKQRAmsqAJ9ADP7pT5fHbaaAjzftHMB+eTqgQQCfQyYj czlEj5zKcvtzameBLGBWul8= =EEZS -END PGP SIGNATURE- Accepted: bzr_0.91-2.diff.gz to pool/main/b/bzr/bzr_0.91-2.diff.gz bzr_0.91-2.dsc to pool/main/b/bzr/bzr_0.91-2.dsc bzr_0.91-2_i386.deb to pool/main/b/bzr/bzr_0.91-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sqlalchemy 0.4.0~beta6-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 12:58:33 +0200 Source: sqlalchemy Binary: python-sqlalchemy python-sqlalchemy-doc Architecture: source all Version: 0.4.0~beta6-1 Distribution: experimental Urgency: low Maintainer: Tommi Virtanen [EMAIL PROTECTED] Changed-By: Piotr Ożarowski [EMAIL PROTECTED] Description: python-sqlalchemy - SQL toolkit and Object Relational Mapper for Python python-sqlalchemy-doc - Documentation for the SQLAlchemy Python library Changes: sqlalchemy (0.4.0~beta6-1) experimental; urgency=low . * New upstream release * Homepage field added Files: c2f061e3a71f4d04c239b98731934113 862 python optional sqlalchemy_0.4.0~beta6-1.dsc a5b1d1345d9b3ddd50fa997d202efac4 1080946 python optional sqlalchemy_0.4.0~beta6.orig.tar.gz 3f3a8f9c44de8e275ee5fa0fea0da880 6344 python optional sqlalchemy_0.4.0~beta6-1.diff.gz 2983b75cbb9079472f75235e20c82d7b 336188 python optional python-sqlalchemy_0.4.0~beta6-1_all.deb 73af4ad1bf45184824ab2f5fe0a4114e 449536 doc optional python-sqlalchemy-doc_0.4.0~beta6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+5NiB01zfu119ZkRAlbVAKCpjpIbQYr3RjOuuSJ7TMc0igN19gCePGNk n++xv+0jtaFFpvzYtXyAd00= =+gLU -END PGP SIGNATURE- Accepted: python-sqlalchemy-doc_0.4.0~beta6-1_all.deb to pool/main/s/sqlalchemy/python-sqlalchemy-doc_0.4.0~beta6-1_all.deb python-sqlalchemy_0.4.0~beta6-1_all.deb to pool/main/s/sqlalchemy/python-sqlalchemy_0.4.0~beta6-1_all.deb sqlalchemy_0.4.0~beta6-1.diff.gz to pool/main/s/sqlalchemy/sqlalchemy_0.4.0~beta6-1.diff.gz sqlalchemy_0.4.0~beta6-1.dsc to pool/main/s/sqlalchemy/sqlalchemy_0.4.0~beta6-1.dsc sqlalchemy_0.4.0~beta6.orig.tar.gz to pool/main/s/sqlalchemy/sqlalchemy_0.4.0~beta6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted misdn-user 1.1.5-2 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 14:02:18 +0200 Source: misdn-user Binary: libisdnnet-dev libmisdn-dev misdn-utils Architecture: source powerpc Version: 1.1.5-2 Distribution: experimental Urgency: low Maintainer: Simon Richter [EMAIL PROTECTED] Changed-By: Simon Richter [EMAIL PROTECTED] Description: libisdnnet-dev - ISDN networking library libmisdn-dev - mISDN interface library misdn-utils - mISDN userspace utilities Changes: misdn-user (1.1.5-2) experimental; urgency=low . * Added missing dependency misdn-dev - linux-headers-misdn Files: 5906fa7f287394bbc8d13959a8afcf5e 666 comm extra misdn-user_1.1.5-2.dsc 468dcf7a3f5c67d3c234d2105fa586bc 3578 comm extra misdn-user_1.1.5-2.diff.gz 64b668266f8bce5f4285ef1cb9853f7f 10586 comm extra misdn-utils_1.1.5-2_powerpc.deb f972e4d3e9413bfdf9b5ab85603dcffc 18206 libdevel extra libmisdn-dev_1.1.5-2_powerpc.deb c86ed15f51a81e9743449dfd0352b546 64484 libdevel extra libisdnnet-dev_1.1.5-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+52tGKDMjVcGpLQRAi0zAJ950/ub3tEx0wS9QjZ9Ym3IBVPvJwCg2JwG 6YyyA80+KJh9SJk4sO6u7Jw= =T9/D -END PGP SIGNATURE- Accepted: libisdnnet-dev_1.1.5-2_powerpc.deb to pool/main/m/misdn-user/libisdnnet-dev_1.1.5-2_powerpc.deb libmisdn-dev_1.1.5-2_powerpc.deb to pool/main/m/misdn-user/libmisdn-dev_1.1.5-2_powerpc.deb misdn-user_1.1.5-2.diff.gz to pool/main/m/misdn-user/misdn-user_1.1.5-2.diff.gz misdn-user_1.1.5-2.dsc to pool/main/m/misdn-user/misdn-user_1.1.5-2.dsc misdn-utils_1.1.5-2_powerpc.deb to pool/main/m/misdn-user/misdn-utils_1.1.5-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dibbler 0.6.1-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 26 Sep 2007 22:45:33 +0200 Source: dibbler Binary: dibbler-doc dibbler-relay dibbler-server dibbler-client Architecture: source all i386 Version: 0.6.1-1 Distribution: unstable Urgency: low Maintainer: Tomasz Mrugalski [EMAIL PROTECTED] Changed-By: Tomasz Mrugalski [EMAIL PROTECTED] Description: dibbler-client - portable DHCPv6 client dibbler-doc - documentation for Dibbler dibbler-relay - portable DHCPv6 relay dibbler-server - portable DHCPv6 server Closes: 417156 444002 Changes: dibbler (0.6.1-1) unstable; urgency=low . * New upstream release * security fix:CVE-2007-5028, CVE-2007-5029,CVE-2007-5028 (closes: #444002) * gcc 4.3 compatibility (closes: #417156) Files: 3be34b39dd9cc0573c65b213d7190975 684 admin optional dibbler_0.6.1-1.dsc 220e68795ab0375cb3bc1f40c47e0bb2 3526327 admin optional dibbler_0.6.1.orig.tar.gz dbf75fcb48bcb55f33200105a9ec9b35 17134 admin optional dibbler_0.6.1-1.diff.gz e6db4587b5c8c8d0826b45ff3ccf1704 364288 admin optional dibbler-server_0.6.1-1_i386.deb 89c4860543079b4a13503309201d6e28 346724 admin optional dibbler-client_0.6.1-1_i386.deb aab792aaf154c122910a9be0e766026b 110112 admin optional dibbler-relay_0.6.1-1_i386.deb 5c669bdd3bae6debfae4c9bdb35c680a 1168076 doc optional dibbler-doc_0.6.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+6S162zWxYk/rQcRAlUlAJ99qox879ALoCG25V6dAg/cKfkLUgCfe1JV OHm1kUNsb/M2pewcIllxdyI= =T029 -END PGP SIGNATURE- Accepted: dibbler-client_0.6.1-1_i386.deb to pool/main/d/dibbler/dibbler-client_0.6.1-1_i386.deb dibbler-doc_0.6.1-1_all.deb to pool/main/d/dibbler/dibbler-doc_0.6.1-1_all.deb dibbler-relay_0.6.1-1_i386.deb to pool/main/d/dibbler/dibbler-relay_0.6.1-1_i386.deb dibbler-server_0.6.1-1_i386.deb to pool/main/d/dibbler/dibbler-server_0.6.1-1_i386.deb dibbler_0.6.1-1.diff.gz to pool/main/d/dibbler/dibbler_0.6.1-1.diff.gz dibbler_0.6.1-1.dsc to pool/main/d/dibbler/dibbler_0.6.1-1.dsc dibbler_0.6.1.orig.tar.gz to pool/main/d/dibbler/dibbler_0.6.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libpam-mount 0.28-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 25 Sep 2007 14:24:49 +0200 Source: libpam-mount Binary: libpam-mount Architecture: source i386 Version: 0.28-1 Distribution: unstable Urgency: low Maintainer: Bastian Kleineidam [EMAIL PROTECTED] Changed-By: Bastian Kleineidam [EMAIL PROTECTED] Description: libpam-mount - PAM module that can mount volumes for a user session Changes: libpam-mount (0.28-1) unstable; urgency=low . * New upstream release. * Dropped patches: + 07_mount_option_space uneeded, mount and nfsmount support -o without a space + 09_password_prompt unneeded, the password prompt is configurable through the config + 14_convert_luserconf applied upstream + 15_pmvarrun_abspath unneeded, the bug is fixed via setting PATH manually + 16_close_session_no_volumes applied upstream * Add patch 04_spawn_pipes from upstream SVN: Fix file descriptor initialization and out-of-bounds array access. * Remove uneeded glib from Build-Depends. * Cleanup and updates for README.Debian: + put package requirements into separate paragraph + updated the examples for the new XML configuration format * Add psmisc and fuser packages to the Suggests since the umount.crypt uses them. Files: f3330b57cd5f3d0aa1ba3c8a5a22579d 711 admin extra libpam-mount_0.28-1.dsc fcd3adf3e8c768df00f477ff6aa54397 407529 admin extra libpam-mount_0.28.orig.tar.gz b7091671eb493fc2739a4ccce924f1e1 18390 admin extra libpam-mount_0.28-1.diff.gz 3e1d2def2042c137a85f50f835c86c4f 82538 admin extra libpam-mount_0.28-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+8TleBwlBDLsbz4RApI/AJ9xyUxeG3lb71ipOJTZD8FLQnBRIQCgk0hH jC4mGVbmgopD19xNe7ffUQY= =Uar9 -END PGP SIGNATURE- Accepted: libpam-mount_0.28-1.diff.gz to pool/main/libp/libpam-mount/libpam-mount_0.28-1.diff.gz libpam-mount_0.28-1.dsc to pool/main/libp/libpam-mount/libpam-mount_0.28-1.dsc libpam-mount_0.28-1_i386.deb to pool/main/libp/libpam-mount/libpam-mount_0.28-1_i386.deb libpam-mount_0.28.orig.tar.gz to pool/main/libp/libpam-mount/libpam-mount_0.28.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apt-setup 1:0.29 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 18:18:15 +0200 Source: apt-setup Binary: apt-mirror-setup apt-cdrom-setup apt-setup-udeb Architecture: source all Version: 1:0.29 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Jérémy Bobbio [EMAIL PROTECTED] Description: apt-cdrom-setup - set up a CD in sources.list (udeb) apt-mirror-setup - set up a mirror in sources.list (udeb) apt-setup-udeb - Configure apt (udeb) Closes: 402645 Changes: apt-setup (1:0.29) unstable; urgency=low . [ Frans Pop ] * Add back detection if user selected to not configure the network. That check is unrelated to the loop discussed in #442891. Closes: #402645. * Allow to continue without selecting a mirror when choose-mirror exits non-zero. This allows a user to back out of mirror selection in the case of a netinst install without a network being available while still avoiding the use a mirror question for all netinst based installs. . [ Updated translations ] * Bulgarian (bg.po) by Damyan Ivanov * Swedish (sv.po) by Daniel Nylander * Thai (th.po) by Theppitak Karoonboonyanan * Simplified Chinese (zh_CN.po) by Ming Hua Files: ce478f9f643e40d45a36aa323d02d332 677 debian-installer extra apt-setup_0.29.dsc 8b11683e95d5a2a68839c34d099098aa 142957 debian-installer extra apt-setup_0.29.tar.gz 3d19aa9ce40b80d8c74851cfc60ea9ca 22768 debian-installer standard apt-setup-udeb_0.29_all.udeb 72882055d7bf59b40c002b23671c537f 59072 debian-installer extra apt-mirror-setup_0.29_all.udeb 1b9c6e23b5edc8f9cd0fb77fce914683 8004 debian-installer extra apt-cdrom-setup_0.29_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+9js2PUjs9fQ72URAlWHAKCR7Gr6Nl8smpt9+fxErsvT65B3yQCgyMTv 8KRDqGnKMPEsra9lhO9iQx8= =Q3XH -END PGP SIGNATURE- Accepted: apt-cdrom-setup_0.29_all.udeb to pool/main/a/apt-setup/apt-cdrom-setup_0.29_all.udeb apt-mirror-setup_0.29_all.udeb to pool/main/a/apt-setup/apt-mirror-setup_0.29_all.udeb apt-setup-udeb_0.29_all.udeb to pool/main/a/apt-setup/apt-setup-udeb_0.29_all.udeb apt-setup_0.29.dsc to pool/main/a/apt-setup/apt-setup_0.29.dsc apt-setup_0.29.tar.gz to pool/main/a/apt-setup/apt-setup_0.29.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mountfloppy 0.13 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 18:28:58 +0200 Source: mountfloppy Binary: mountfloppy Architecture: source all Version: 0.13 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Jérémy Bobbio [EMAIL PROTECTED] Description: mountfloppy - Mounts a floppy (udeb) Changes: mountfloppy (0.13) unstable; urgency=low . [ Jérémy Bobbio ] * Cleanup devfs-style device names. . [ Updated translations ] * Bengali (bn.po) by Jamil Ahmed * Danish (da.po) by Claus Hindsgaul * Spanish (es.po) by Javier Fernández-Sanguino Peña * Italian (it.po) by Stefano Canepa * Panjabi (pa.po) by A S Alam * Portuguese (pt.po) by Miguel Figueiredo * Romanian (ro.po) by Eddy PetriÈor * Vietnamese (vi.po) by Clytie Siddall Files: bdd486a961c1217de91ecfd61cc8334e 662 debian-installer optional mountfloppy_0.13.dsc c40a95b1cf0addc35699614e6ce33e18 28149 debian-installer optional mountfloppy_0.13.tar.gz 87a5e37f29ca83e2add88edbeea692df 11452 debian-installer optional mountfloppy_0.13_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+9qs2PUjs9fQ72URAtvXAJ96uzFAr3XlrKGw63xPge6OK98enwCdGAGo XIFOSnyLqgCK65z/XIC3GIg= =GZnQ -END PGP SIGNATURE- Accepted: mountfloppy_0.13.dsc to pool/main/m/mountfloppy/mountfloppy_0.13.dsc mountfloppy_0.13.tar.gz to pool/main/m/mountfloppy/mountfloppy_0.13.tar.gz mountfloppy_0.13_all.udeb to pool/main/m/mountfloppy/mountfloppy_0.13_all.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lowmem 1.27 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 18:37:50 +0200 Source: lowmem Binary: lowmemcheck lowmem Architecture: source amd64 all Version: 1.27 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Jérémy Bobbio [EMAIL PROTECTED] Description: lowmem - free memory for lowmem install (udeb) lowmemcheck - detect low-memory systems and enter lowmem mode (udeb) Changes: lowmem (1.27) unstable; urgency=low . [ Frans Pop ] * Allow user to override the lowmem level by specifying a parameter lowmem at the boot prompt. Only a level higher than the default is observed. . [ Joey Hess ] * Change i386 lowmem to below 48 mb. Needs new cdebconf with template trimming code. (The cutoff point for lowmem level 2 does not change.) Files: ec97acdd6cdb0596444f074e51057871 679 debian-installer optional lowmem_1.27.dsc 24079f8ee337014e6ba669d7dedc7a9d 10101 debian-installer optional lowmem_1.27.tar.gz 1ba9ca2e32f6c4916ae7385ba4c86810 1356 debian-installer optional lowmem_1.27_all.udeb 12564d2008c29c288d5882892dce9154 5138 debian-installer optional lowmemcheck_1.27_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+91h2PUjs9fQ72URAhhsAKC1XPF6MCUHUkFKCKEknD3QyOGpcgCdGm6F 1fwxh10FP9tyaVTxJJcLXi4= =kOSS -END PGP SIGNATURE- Accepted: lowmem_1.27.dsc to pool/main/l/lowmem/lowmem_1.27.dsc lowmem_1.27.tar.gz to pool/main/l/lowmem/lowmem_1.27.tar.gz lowmem_1.27_all.udeb to pool/main/l/lowmem/lowmem_1.27_all.udeb lowmemcheck_1.27_amd64.udeb to pool/main/l/lowmem/lowmemcheck_1.27_amd64.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted floppy-retriever 1.16 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 18:31:36 +0200 Source: floppy-retriever Binary: floppy-retriever load-floppy Architecture: source all Version: 1.16 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Jérémy Bobbio [EMAIL PROTECTED] Description: floppy-retriever - Fetches modules from a floppy (udeb) load-floppy - Load installer components from a floppy (udeb) Changes: floppy-retriever (1.16) unstable; urgency=low . [ Jérémy Bobbio ] * Clean up devfs-style device names in load-floppy.postinst. . [ Updated translations ] * Bengali (bn.po) by Jamil Ahmed * Catalan (ca.po) by Jordi Mallach * Danish (da.po) by Claus Hindsgaul * Italian (it.po) by Stefano Canepa * Romanian (ro.po) by Eddy PetriÈor * Vietnamese (vi.po) by Clytie Siddall Files: 831120c4cceeaf210b9a964b522678c2 760 debian-installer optional floppy-retriever_1.16.dsc 89107942a948c871f51bdf362b315a9b 56729 debian-installer optional floppy-retriever_1.16.tar.gz 4395f5464f3ee1925462de3b07c5c634 11852 debian-installer optional floppy-retriever_1.16_all.udeb 83ba69b2e4285e7001e08087968df3ac 29984 debian-installer extra load-floppy_1.16_all.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+9sw2PUjs9fQ72URAmukAJ97qKIv8fYFU7U2bB46nmJk0aSj4wCgsfOJ T8fc/d8DRc8sEJPtU06BMT0= =Lc0S -END PGP SIGNATURE- Accepted: floppy-retriever_1.16.dsc to pool/main/f/floppy-retriever/floppy-retriever_1.16.dsc floppy-retriever_1.16.tar.gz to pool/main/f/floppy-retriever/floppy-retriever_1.16.tar.gz floppy-retriever_1.16_all.udeb to pool/main/f/floppy-retriever/floppy-retriever_1.16_all.udeb load-floppy_1.16_all.udeb to pool/main/f/floppy-retriever/load-floppy_1.16_all.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted os-prober 1.22 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 18:43:50 +0200 Source: os-prober Binary: os-prober os-prober-udeb Architecture: source amd64 Version: 1.22 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Jérémy Bobbio [EMAIL PROTECTED] Description: os-prober - utility to detect other OSes on a set of drives os-prober-udeb - utility to detect other OSes on a set of drives (udeb) Changes: os-prober (1.22) unstable; urgency=low . [ Joey Hess ] * Call dh_md5sums. . [ Jérémy Bobbio ] * Remove references to devfs-style device names in documentation and comments. . [ Colin Watson ] * Accept fuseblk as well as fuse in the Microsoft probe. * Make sure to select only the first mountpoint for a given device (in case of bind mounts). * Treat the lpia architecture (used in the Ubuntu mobile project) as x86, since it is. Files: c5de9109249eb5e70b85c818f2af2d81 697 debian-installer optional os-prober_1.22.dsc 53b8a5434f783fcf8740c7db7fe9b77d 17166 debian-installer optional os-prober_1.22.tar.gz 887130fed0a94ebd50692e2808872269 8808 debian-installer optional os-prober-udeb_1.22_amd64.udeb 51d962e1d318f4376937acc99186b621 15878 utils extra os-prober_1.22_amd64.deb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+95S2PUjs9fQ72URApaWAKCVbZ7S9dFJ3m7x2AGj5VMm0yhJ5ACfStQn 7Q7ZkOsR58Ana3eUgWQeB9U= =U061 -END PGP SIGNATURE- Accepted: os-prober-udeb_1.22_amd64.udeb to pool/main/o/os-prober/os-prober-udeb_1.22_amd64.udeb os-prober_1.22.dsc to pool/main/o/os-prober/os-prober_1.22.dsc os-prober_1.22.tar.gz to pool/main/o/os-prober/os-prober_1.22.tar.gz os-prober_1.22_amd64.deb to pool/main/o/os-prober/os-prober_1.22_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xserver-xorg-video-avivo 0.0.999+git20070927-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 20:37:23 +0200 Source: xserver-xorg-video-avivo Binary: xserver-xorg-video-avivo Architecture: source i386 Version: 0.0.999+git20070927-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force [EMAIL PROTECTED] Changed-By: Brice Goglin [EMAIL PROTECTED] Description: xserver-xorg-video-avivo - X.Org X server -- Avivo display driver Closes: 444263 Changes: xserver-xorg-video-avivo (0.0.999+git20070927-1) experimental; urgency=low . * New upstream snapshot. * Build against Xserver 1.4, closes: #444263. Files: e1f182ed88a8e7493248b56cfca04626 971 x11 extra xserver-xorg-video-avivo_0.0.999+git20070927-1.dsc 1a9e1d2c795d3e34390925a6cde6a726 88334 x11 extra xserver-xorg-video-avivo_0.0.999+git20070927.orig.tar.gz 85f4d3c2594106f834dbc5d7ed774428 325758 x11 extra xserver-xorg-video-avivo_0.0.999+git20070927-1.diff.gz 7fb206d761e999cf271ece6c371dbe3a 48820 x11 extra xserver-xorg-video-avivo_0.0.999+git20070927-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG+/rfRh88F8PcWfoRAo02AJ9i6i7zwJ5v9cVgnewUGrD3Dz/3ZwCgxadL eXMNjfv2VLfLF+mjzzoDWbo= =aJhA -END PGP SIGNATURE- Accepted: xserver-xorg-video-avivo_0.0.999+git20070927-1.diff.gz to pool/main/x/xserver-xorg-video-avivo/xserver-xorg-video-avivo_0.0.999+git20070927-1.diff.gz xserver-xorg-video-avivo_0.0.999+git20070927-1.dsc to pool/main/x/xserver-xorg-video-avivo/xserver-xorg-video-avivo_0.0.999+git20070927-1.dsc xserver-xorg-video-avivo_0.0.999+git20070927-1_i386.deb to pool/main/x/xserver-xorg-video-avivo/xserver-xorg-video-avivo_0.0.999+git20070927-1_i386.deb xserver-xorg-video-avivo_0.0.999+git20070927.orig.tar.gz to pool/main/x/xserver-xorg-video-avivo/xserver-xorg-video-avivo_0.0.999+git20070927.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted quotatool 1.4.10-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 21:01:51 +0200 Source: quotatool Binary: quotatool Architecture: source amd64 Version: 1.4.10-1 Distribution: unstable Urgency: low Maintainer: Bas Zoetekouw [EMAIL PROTECTED] Changed-By: Bas Zoetekouw [EMAIL PROTECTED] Description: quotatool - tool to edit disk quotas from the command line Closes: 402900 Changes: quotatool (1.4.10-1) unstable; urgency=low . * New upstream release - Fix for building on 64-bit systems - Bugfix off-by-one-error in parsing loop devices (thanks Bas Zoetekouw) [obsoletes 10_loop_fix.patch] - Bugfix commandline parsing with option -t (closes: #402900) - Updated manpage and usage info * Edited the long description a little bit. Files: 469223d028a541f0aed59f96fde1575a 580 admin extra quotatool_1.4.10-1.dsc d0eb99718a0dbc02189993d8667ef9b1 113822 admin extra quotatool_1.4.10.orig.tar.gz 7f0d3ca881d50e9bc531e7fa18135c76 3671 admin extra quotatool_1.4.10-1.diff.gz 5c148d2e920e905684fe616d4a8c20a7 18446 admin extra quotatool_1.4.10-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/AC+K67kHwZE+rcRAhIiAKCJbGv8SlVqPvow/zLL4ZmjiBtpywCg5Heh vTyr2o0Em0cPx92DRqC4f9s= =N+J+ -END PGP SIGNATURE- Accepted: quotatool_1.4.10-1.diff.gz to pool/main/q/quotatool/quotatool_1.4.10-1.diff.gz quotatool_1.4.10-1.dsc to pool/main/q/quotatool/quotatool_1.4.10-1.dsc quotatool_1.4.10-1_amd64.deb to pool/main/q/quotatool/quotatool_1.4.10-1_amd64.deb quotatool_1.4.10.orig.tar.gz to pool/main/q/quotatool/quotatool_1.4.10.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted evolution-python 0.0.3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Sep 2007 20:59:34 +0200 Source: evolution-python Binary: python-evolution Architecture: source i386 Version: 0.0.3-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team [EMAIL PROTECTED] Changed-By: Thomas Viehmann [EMAIL PROTECTED] Description: python-evolution - python bindings for libebook and libecal Closes: 434267 Changes: evolution-python (0.0.3-1) unstable; urgency=low . * New upstream release * Upload to unstable for the benefit of conduit. (Closes: #434267) Files: e5cc23f4975d68cb83c62241dd07b953 1070 python optional evolution-python_0.0.3-1.dsc 0ef1afcc79ae9f190ed2260eb1b1fcdd 349850 python optional evolution-python_0.0.3.orig.tar.gz e0233e25495f25f19198da29313ea4b3 3293 python optional evolution-python_0.0.3-1.diff.gz 2ae8680bf5c5fed48f55dd48ce813468 36452 python optional python-evolution_0.0.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: GnuPG key at http://thomas.viehmann.net/ iD8DBQFG+/7driZpaaIa1PkRAtwBAJ96KC74n3KZSyCWxP0TYDlDpcF1igCguooA uMev7zKGuzQO6TnXsNVPX8M= =4Oh+ -END PGP SIGNATURE- Accepted: evolution-python_0.0.3-1.diff.gz to pool/main/e/evolution-python/evolution-python_0.0.3-1.diff.gz evolution-python_0.0.3-1.dsc to pool/main/e/evolution-python/evolution-python_0.0.3-1.dsc evolution-python_0.0.3.orig.tar.gz to pool/main/e/evolution-python/evolution-python_0.0.3.orig.tar.gz python-evolution_0.0.3-1_i386.deb to pool/main/e/evolution-python/python-evolution_0.0.3-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted thinkfinger 0.3-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Sep 2007 14:44:23 +0200 Source: thinkfinger Binary: libthinkfinger0 libthinkfinger-doc thinkfinger-tools libpam-thinkfinger libthinkfinger-dev Architecture: source amd64 all Version: 0.3-2 Distribution: experimental Urgency: low Maintainer: FingerForce Team [EMAIL PROTECTED] Changed-By: Luca Capello [EMAIL PROTECTED] Description: libpam-thinkfinger - PAM module for the STMicroelectronics fingerprint reader libthinkfinger-dev - development files for libthinkfinger libthinkfinger-doc - documentation for libthinkfinger libthinkfinger0 - library for the STMicroelectronics fingerprint reader thinkfinger-tools - utilities for the STMicroelectronics fingerprint reader Changes: thinkfinger (0.3-2) experimental; urgency=low . * New release built with PAM-0.99.7.1. Files: c423d40e4a96788c57b120dcd5f2218a 865 libs optional thinkfinger_0.3-2.dsc c53ae28dfad843f0435b314e10aeaa26 3771 libs optional thinkfinger_0.3-2.diff.gz 00a13dbdafa76a748f4be8665e6a6420 15612 libs optional libthinkfinger0_0.3-2_amd64.deb 7f43d92041edbbc6c58383877244a2f1 17592 devel optional libthinkfinger-dev_0.3-2_amd64.deb e5ca257313b5e6997b6882a9b3836937 16184 admin extra libpam-thinkfinger_0.3-2_amd64.deb ad65d277b99da3012296cc2341331336 15948 admin extra thinkfinger-tools_0.3-2_amd64.deb f4c3f0594fbd3213982b1d4c59c15a92 75060 doc extra libthinkfinger-doc_0.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/AJQNTNQylgICMQRAsVAAKCAVSTwOdB7C5tHmw90xBcb0+YwyQCeJ9cK DZLfB5HucZBFQ4hlAVO7mx4= =Gk0k -END PGP SIGNATURE- Accepted: libpam-thinkfinger_0.3-2_amd64.deb to pool/main/t/thinkfinger/libpam-thinkfinger_0.3-2_amd64.deb libthinkfinger-dev_0.3-2_amd64.deb to pool/main/t/thinkfinger/libthinkfinger-dev_0.3-2_amd64.deb libthinkfinger-doc_0.3-2_all.deb to pool/main/t/thinkfinger/libthinkfinger-doc_0.3-2_all.deb libthinkfinger0_0.3-2_amd64.deb to pool/main/t/thinkfinger/libthinkfinger0_0.3-2_amd64.deb thinkfinger-tools_0.3-2_amd64.deb to pool/main/t/thinkfinger/thinkfinger-tools_0.3-2_amd64.deb thinkfinger_0.3-2.diff.gz to pool/main/t/thinkfinger/thinkfinger_0.3-2.diff.gz thinkfinger_0.3-2.dsc to pool/main/t/thinkfinger/thinkfinger_0.3-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gp2c 0.0.5pl5-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 21:07:38 +0200 Source: gp2c Binary: pari-gp2c Architecture: source amd64 Version: 0.0.5pl5-1 Distribution: unstable Urgency: low Maintainer: Bill Allombert [EMAIL PROTECTED] Changed-By: Bill Allombert [EMAIL PROTECTED] Description: pari-gp2c - PARI/GP GP to C compiler Changes: gp2c (0.0.5pl5-1) unstable; urgency=low . * New upstream release Files: 5ed9e56ec83b524e1f6422caf80fceea 612 math optional gp2c_0.0.5pl5-1.dsc 1130b75a791745498e86c965c34ec1d9 293520 math optional gp2c_0.0.5pl5.orig.tar.gz a6a91c843751feffc4252d3611e7c1f3 2762 math optional gp2c_0.0.5pl5-1.diff.gz 71fe90ee4b537a70fae2c35c764b9ec7 145866 math optional pari-gp2c_0.0.5pl5-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/Aw4eDPs8bVESBURAuTiAJ4/jiDixcN8N6m05cTPiSAQgvMzaQCdGB8d EINOAhmkFQhA/p/QlB/smWU= =x4Pd -END PGP SIGNATURE- Accepted: gp2c_0.0.5pl5-1.diff.gz to pool/main/g/gp2c/gp2c_0.0.5pl5-1.diff.gz gp2c_0.0.5pl5-1.dsc to pool/main/g/gp2c/gp2c_0.0.5pl5-1.dsc gp2c_0.0.5pl5.orig.tar.gz to pool/main/g/gp2c/gp2c_0.0.5pl5.orig.tar.gz pari-gp2c_0.0.5pl5-1_amd64.deb to pool/main/g/gp2c/pari-gp2c_0.0.5pl5-1_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted camlp5 5.00-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 22:13:32 +0200 Source: camlp5 Binary: camlp5 Architecture: source i386 Version: 5.00-1 Distribution: experimental Urgency: low Maintainer: Debian OCaml Maintainers [EMAIL PROTECTED] Changed-By: Stefano Zacchiroli [EMAIL PROTECTED] Description: camlp5 - Pre Processor Pretty Printer for OCaml - classical version Changes: camlp5 (5.00-1) experimental; urgency=low . * new upstream release * add Homepage field to debian/control * remove patch install_destdir (no longer needed since now upstream Makefile support vanilla DESTDIR passing) Files: 3ed47b57041740be7f8aa47d58c09e71 871 devel extra camlp5_5.00-1.dsc 70986d6a7b54f4d35e7cc6b16731b8fd 586867 devel extra camlp5_5.00.orig.tar.gz 0a39b469831c2e385cf4154d86292951 4941 devel extra camlp5_5.00-1.diff.gz 08e64e68afdc59b2125a28adc14a3d27 1904844 devel extra camlp5_5.00-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/A+B1cqbBPLEI7wRAnLUAJ4nIIanQKcqoCV64L6ZTxHkau5lSACgoevd qUgnF/ZbAipzq3vTspoP4M4= =u7KW -END PGP SIGNATURE- Accepted: camlp5_5.00-1.diff.gz to pool/main/c/camlp5/camlp5_5.00-1.diff.gz camlp5_5.00-1.dsc to pool/main/c/camlp5/camlp5_5.00-1.dsc camlp5_5.00-1_i386.deb to pool/main/c/camlp5/camlp5_5.00-1_i386.deb camlp5_5.00.orig.tar.gz to pool/main/c/camlp5/camlp5_5.00.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aufs 0+20070924-1.1 (ia64 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 13:39:49 -0600 Source: aufs Binary: linux-patch-aufs aufs-source aufs-tools Architecture: source ia64 all Version: 0+20070924-1.1 Distribution: unstable Urgency: low Maintainer: Julian Andres Klode [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: aufs-source - Source for the aufs driver aufs-tools - Tools to manage aufs filesystems linux-patch-aufs - Kernel patches for aufs Changes: aufs (0+20070924-1.1) unstable; urgency=low . * Non-maintainer upload. * Fix namespace collision that resulted in a FTBFS on ia64 Files: 0fe4293eda8efac113e41627fc32292f 648 misc optional aufs_0+20070924-1.1.dsc c8815a906b3a2dcf0be17d2ebe6ad907 6931 misc optional aufs_0+20070924-1.1.diff.gz 416505782c13bb842f55481acd71f522 107512 misc optional aufs-source_0+20070924-1.1_all.deb e5223643f297d2b87607912677492f89 24826 misc optional linux-patch-aufs_0+20070924-1.1_all.deb 53d6dc82f5addae6298df711f202421d 88564 misc optional aufs-tools_0+20070924-1.1_ia64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/AonhuANDBmkLRkRAuYXAJ4lC6Mu3kao/gfolaxt9sOfczf3dwCgjWU6 1fJgb5hOY+AsvCljOPzOPns= =H1IB -END PGP SIGNATURE- Accepted: aufs-source_0+20070924-1.1_all.deb to pool/main/a/aufs/aufs-source_0+20070924-1.1_all.deb aufs-tools_0+20070924-1.1_ia64.deb to pool/main/a/aufs/aufs-tools_0+20070924-1.1_ia64.deb aufs_0+20070924-1.1.diff.gz to pool/main/a/aufs/aufs_0+20070924-1.1.diff.gz aufs_0+20070924-1.1.dsc to pool/main/a/aufs/aufs_0+20070924-1.1.dsc linux-patch-aufs_0+20070924-1.1_all.deb to pool/main/a/aufs/linux-patch-aufs_0+20070924-1.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tcpdump 3.9.8-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 22:41:53 +0200 Source: tcpdump Binary: tcpdump Architecture: source amd64 Version: 3.9.8-1 Distribution: unstable Urgency: low Maintainer: Romain Francoise [EMAIL PROTECTED] Changed-By: Romain Francoise [EMAIL PROTECTED] Description: tcpdump- A powerful tool for network monitoring and data acquisition Changes: tcpdump (3.9.8-1) unstable; urgency=low . * New upstream release. Files: 670f1a78283b0549aa44ebc3d31c0e8b 672 net optional tcpdump_3.9.8-1.dsc c491a78c52fe73f1f7271aa5d8c6ab2e 938054 net optional tcpdump_3.9.8.orig.tar.gz f39401f38abd3577357a97a6e0907343 10639 net optional tcpdump_3.9.8-1.diff.gz 798ad4dc3328c642ae35f0cdbf24dcd8 320628 net optional tcpdump_3.9.8-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/BdnogN2vsA8Vt8RAhcgAKCxaPBSM6EHNhKbiODILcxiBOI6twCfcFCc /Qu8mJDOXuy5nlHDOhsdmxE= =Kqhk -END PGP SIGNATURE- Accepted: tcpdump_3.9.8-1.diff.gz to pool/main/t/tcpdump/tcpdump_3.9.8-1.diff.gz tcpdump_3.9.8-1.dsc to pool/main/t/tcpdump/tcpdump_3.9.8-1.dsc tcpdump_3.9.8-1_amd64.deb to pool/main/t/tcpdump/tcpdump_3.9.8-1_amd64.deb tcpdump_3.9.8.orig.tar.gz to pool/main/t/tcpdump/tcpdump_3.9.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted slgsl 0.7.0-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 23:45:23 +0200 Source: slgsl Binary: slang-gsl Architecture: source i386 Version: 0.7.0-2 Distribution: unstable Urgency: low Maintainer: Debian JED Group [EMAIL PROTECTED] Changed-By: Rafael Laboissiere [EMAIL PROTECTED] Description: slang-gsl - GNU Scientific Library binding for S-Lang Closes: 444316 Changes: slgsl (0.7.0-2) unstable; urgency=low . * debian/patches/use-fPIC.patch: Added patch for compiling files with -fPIC (closes: #444316) Files: 5719098a91a11542f7487b50c2a5ca1c 855 interpreters optional slgsl_0.7.0-2.dsc cc3152fea18dad4a51593d8c3bc7756c 2947 interpreters optional slgsl_0.7.0-2.diff.gz bc58444069b2dc22179051841a6674a0 56502 interpreters optional slang-gsl_0.7.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/CTCk3oga0pdcv4RAvPMAJ9PJW77GCJbmUlib7PRuONL9dqqYgCeNgSE 9KeJcU6jls9TiW5tIFawIOg= =ZZBv -END PGP SIGNATURE- Accepted: slang-gsl_0.7.0-2_i386.deb to pool/main/s/slgsl/slang-gsl_0.7.0-2_i386.deb slgsl_0.7.0-2.diff.gz to pool/main/s/slgsl/slgsl_0.7.0-2.diff.gz slgsl_0.7.0-2.dsc to pool/main/s/slgsl/slgsl_0.7.0-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bouml 2.31.3-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 22:06:53 +0200 Source: bouml Binary: bouml bouml-plugouts-src Architecture: source amd64 all Version: 2.31.3-2 Distribution: unstable Urgency: low Maintainer: Thomas Girard [EMAIL PROTECTED] Changed-By: Thomas Girard [EMAIL PROTECTED] Description: bouml - UML2 tool box to specify and generate code bouml-plugouts-src - UML2 tool box to specify and generate code (plugouts sources) Closes: 444302 Changes: bouml (2.31.3-2) unstable; urgency=low . * Link against libgcc1 from sid, not experimental. Closes: #444302. Files: 456baa95911e7b424f9712869dccb964 655 devel optional bouml_2.31.3-2.dsc d82b44f849a27aa11d0d234340d77acc 5833 devel optional bouml_2.31.3-2.diff.gz 9fa0b9f8eca4b6e1abde69e9fb113217 1876158 devel optional bouml-plugouts-src_2.31.3-2_all.deb b8ba86e09a6d08010f8e9c13592c166f 4019064 devel optional bouml_2.31.3-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/CZkz2LXlDjmjg4RAmVPAJ929tolpPfEuG45YMnjPzrOLyrIKwCfaiMS EJDuS7l/HEvyi9jQ9vVUzE8= =KT1y -END PGP SIGNATURE- Accepted: bouml-plugouts-src_2.31.3-2_all.deb to pool/main/b/bouml/bouml-plugouts-src_2.31.3-2_all.deb bouml_2.31.3-2.diff.gz to pool/main/b/bouml/bouml_2.31.3-2.diff.gz bouml_2.31.3-2.dsc to pool/main/b/bouml/bouml_2.31.3-2.dsc bouml_2.31.3-2_amd64.deb to pool/main/b/bouml/bouml_2.31.3-2_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libmail-dkim-perl 0.28-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 22:21:31 +0200 Source: libmail-dkim-perl Binary: libmail-dkim-perl Architecture: source all Version: 0.28-2 Distribution: unstable Urgency: low Maintainer: Magnus Holmgren [EMAIL PROTECTED] Changed-By: Magnus Holmgren [EMAIL PROTECTED] Description: libmail-dkim-perl - cryptographically identify the sender of email - perl library Changes: libmail-dkim-perl (0.28-2) unstable; urgency=low . * Skip 'make realclean' if Makefile does not exist, and do not ignore errors. * Modernise debian/control: wrap dependency fields, add XS-Vcs-* fields, and make Homepage a real field. Files: be7d1b3a6bc70c354a37ae63787d2d7e 918 perl optional libmail-dkim-perl_0.28-2.dsc bbaf0511f556a9cacc6ffa28dd8eb5ae 3085 perl optional libmail-dkim-perl_0.28-2.diff.gz 1bb3cf8da338c97818558aebe8e0a6ac 84576 perl optional libmail-dkim-perl_0.28-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/C8+30WoBV0H6VwRAqoAAKCvVhnoj3jR5gbr+8rmFHUt7EOXbACguFXP KSMbiN6KXhuJp1GOOIbn9jY= =/Hen -END PGP SIGNATURE- Accepted: libmail-dkim-perl_0.28-2.diff.gz to pool/main/libm/libmail-dkim-perl/libmail-dkim-perl_0.28-2.diff.gz libmail-dkim-perl_0.28-2.dsc to pool/main/libm/libmail-dkim-perl/libmail-dkim-perl_0.28-2.dsc libmail-dkim-perl_0.28-2_all.deb to pool/main/libm/libmail-dkim-perl/libmail-dkim-perl_0.28-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sun-java5 1.5.0-13-1 (ia64 source all amd64 i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 23:16:10 +0200 Source: sun-java5 Binary: sun-java5-demo sun-java5-fonts sun-java5-bin sun-java5-source sun-java5-jdk sun-java5-doc sun-java5-jre ia32-sun-java5-plugin ia32-sun-java5-bin sun-java5-plugin Architecture: all amd64 i386 ia64 source Version: 1.5.0-13-1 Distribution: unstable Urgency: low Maintainer: Matthias Klose [EMAIL PROTECTED] Changed-By: Matthias Klose [EMAIL PROTECTED] Description: ia32-sun-java5-bin - Sun Java(TM) Runtime Environment (JRE) 5.0 (32-bit) sun-java5-bin - Sun Java(TM) Runtime Environment (JRE) 5.0 (architecture dependen sun-java5-demo - Sun Java(TM) Development Kit (JDK) 5.0 demos and examples sun-java5-jdk - Sun Java(TM) Development Kit (JDK) 5.0 Changes: sun-java5 (1.5.0-13-1) unstable; urgency=low . * Upload to unstable. Files: 1e2144f0bde3adda13ef90630bd6aa58 5237594 non-free/devel optional sun-java5-demo_1.5.0-13-1_amd64.deb 26cacbfc1827be8c4c97579949d26cb9 40334 non-free/doc optional sun-java5-doc_1.5.0-13-1_all.deb 329ed04b5a25ff2abac385e2d3184916 16460578 non-free/devel optional sun-java5-source_1.5.0-13-1_all.deb 4de25e9d3079cc786558a9afdd3a9ce3 9872504 non-free/devel optional sun-java5-demo_1.5.0-13-1_i386.deb 5294a943152432dab97408f55e363174 81116 non-free/devel optional sun-java5_1.5.0-13-1.diff.gz 65f76dd622ebc5eb9a78655b1c87db06 1600 non-free/web optional sun-java5-plugin_1.5.0-13-1_i386.deb 7a93f8ddecbc1a51151b4da87304a60c 92128617 non-free/devel optional sun-java5_1.5.0-13.orig.tar.gz 9b3150213bb8b440a7b8307f2f689509 22398646 non-free/libs optional ia32-sun-java5-bin_1.5.0-13-1_ia64.deb ac8ac88a8fc4f8ba06a629803123255a 1822 non-free/x11 optional sun-java5-fonts_1.5.0-13-1_all.deb b791300bb5fad9225642e5dd1139cfa4 22398684 non-free/libs optional ia32-sun-java5-bin_1.5.0-13-1_amd64.deb bb5d6a44502bebf5563760d3d0fd1a42 19868324 non-free/libs optional sun-java5-bin_1.5.0-13-1_amd64.deb c20edcac49d20ffdfad241ade37cab2b 4883248 non-free/devel optional sun-java5-jdk_1.5.0-13-1_amd64.deb cfc1e13e62be72990617f533cd3c7a75 5049996 non-free/devel optional sun-java5-jdk_1.5.0-13-1_i386.deb e90194e3337ed6b710e14bcebea7b2b6 22397794 non-free/libs optional sun-java5-bin_1.5.0-13-1_i386.deb b3c2f65956ad60988d84e47060e39361 1219 non-free/devel optional sun-java5_1.5.0-13-1.dsc f69cd57da3490257534c31aa61b2c9d0 7463816 non-free/libs optional sun-java5-jre_1.5.0-13-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/Dt/StlRaw+TLJwRAlpgAJwMQW3QtBbT28NXFDqzPNIej92lSgCgkFuT OgAPGIWuCMa2GgkXO6R0bdw= =bkls -END PGP SIGNATURE- Accepted: ia32-sun-java5-bin_1.5.0-13-1_amd64.deb to pool/non-free/s/sun-java5/ia32-sun-java5-bin_1.5.0-13-1_amd64.deb ia32-sun-java5-bin_1.5.0-13-1_ia64.deb to pool/non-free/s/sun-java5/ia32-sun-java5-bin_1.5.0-13-1_ia64.deb sun-java5-bin_1.5.0-13-1_amd64.deb to pool/non-free/s/sun-java5/sun-java5-bin_1.5.0-13-1_amd64.deb sun-java5-bin_1.5.0-13-1_i386.deb to pool/non-free/s/sun-java5/sun-java5-bin_1.5.0-13-1_i386.deb sun-java5-demo_1.5.0-13-1_amd64.deb to pool/non-free/s/sun-java5/sun-java5-demo_1.5.0-13-1_amd64.deb sun-java5-demo_1.5.0-13-1_i386.deb to pool/non-free/s/sun-java5/sun-java5-demo_1.5.0-13-1_i386.deb sun-java5-doc_1.5.0-13-1_all.deb to pool/non-free/s/sun-java5/sun-java5-doc_1.5.0-13-1_all.deb sun-java5-fonts_1.5.0-13-1_all.deb to pool/non-free/s/sun-java5/sun-java5-fonts_1.5.0-13-1_all.deb sun-java5-jdk_1.5.0-13-1_amd64.deb to pool/non-free/s/sun-java5/sun-java5-jdk_1.5.0-13-1_amd64.deb sun-java5-jdk_1.5.0-13-1_i386.deb to pool/non-free/s/sun-java5/sun-java5-jdk_1.5.0-13-1_i386.deb sun-java5-jre_1.5.0-13-1_all.deb to pool/non-free/s/sun-java5/sun-java5-jre_1.5.0-13-1_all.deb sun-java5-plugin_1.5.0-13-1_i386.deb to pool/non-free/s/sun-java5/sun-java5-plugin_1.5.0-13-1_i386.deb sun-java5-source_1.5.0-13-1_all.deb to pool/non-free/s/sun-java5/sun-java5-source_1.5.0-13-1_all.deb sun-java5_1.5.0-13-1.diff.gz to pool/non-free/s/sun-java5/sun-java5_1.5.0-13-1.diff.gz sun-java5_1.5.0-13-1.dsc to pool/non-free/s/sun-java5/sun-java5_1.5.0-13-1.dsc sun-java5_1.5.0-13.orig.tar.gz to pool/non-free/s/sun-java5/sun-java5_1.5.0-13.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ion3 20070927-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 23:58:23 +0100 Source: ion3 Binary: ion3-doc ion3-dev ion3 Architecture: source all i386 Version: 20070927-1 Distribution: unstable Urgency: low Maintainer: Ben Hutchings [EMAIL PROTECTED] Changed-By: Ben Hutchings [EMAIL PROTECTED] Description: ion3 - keyboard-friendly window manager with tiled windows ion3-dev - ion3 development files ion3-doc - ion3 documentation Changes: ion3 (20070927-1) unstable; urgency=low . * New upstream release * Reenabled dh_strip since debugging information is disabled by default * Changed menu section to conform to new menu policy Files: e0d600a3c7ae1bea832648ede352f14c 701 non-free/x11 extra ion3_20070927-1.dsc 9901954cc34938bcb045b867633ad14a 1317593 non-free/x11 extra ion3_20070927.orig.tar.gz efde99e1818be4547d8108209a270834 35406 non-free/x11 extra ion3_20070927-1.diff.gz f7e0ca3e3278acec4b7e3155cb4c1da8 90764 non-free/devel extra ion3-dev_20070927-1_all.deb 8fa17a5cf8ea27ba6daf607b4432a9a2 126514 non-free/doc extra ion3-doc_20070927-1_all.deb 97fdfb3c50c1b2dcce4c74782bec9710 666408 non-free/x11 extra ion3_20070927-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/Dqn79ZNCRIGYgcRArvgAKCpKcSWNvLh8/kvj3hK+iKfYbshRgCgtTnR 8yjVnhs41f+qY+kTmP9hg/s= =F05W -END PGP SIGNATURE- Accepted: ion3-dev_20070927-1_all.deb to pool/non-free/i/ion3/ion3-dev_20070927-1_all.deb ion3-doc_20070927-1_all.deb to pool/non-free/i/ion3/ion3-doc_20070927-1_all.deb ion3_20070927-1.diff.gz to pool/non-free/i/ion3/ion3_20070927-1.diff.gz ion3_20070927-1.dsc to pool/non-free/i/ion3/ion3_20070927-1.dsc ion3_20070927-1_i386.deb to pool/non-free/i/ion3/ion3_20070927-1_i386.deb ion3_20070927.orig.tar.gz to pool/non-free/i/ion3/ion3_20070927.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted texmacs 1:1.0.6.11-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 15:24:19 +0900 Source: texmacs Binary: texmacs-common texmacs Architecture: source i386 all Version: 1:1.0.6.11-1 Distribution: unstable Urgency: low Maintainer: Atsuhito KOHDA [EMAIL PROTECTED] Changed-By: Atsuhito KOHDA [EMAIL PROTECTED] Description: texmacs- WYSIWYG mathematical text editor using TeX fonts texmacs-common - WYSIWYG mathematical text editor using TeX fonts Changes: texmacs (1:1.0.6.11-1) unstable; urgency=low . * Whole work was done by Kamaraju Kusumanchi [EMAIL PROTECTED] or [raju]. * New upstream release * texmacs does not build on ia64 since guile-1.8 FTBFS on ia64 (bug #401400). So reduced the build dependency to guile-1.6-dev on ia64. All other architectures still depend upon guile-1.8-dev. Files: f2e4f612b2b01d72811521a0a3c8869d 917 editors optional texmacs_1.0.6.11-1.dsc 61cba82f2b3e64914f2a33e479e45c96 4294912 editors optional texmacs_1.0.6.11.orig.tar.gz 1d24fa39f20b50f88ad5f039de9fbf62 27076 editors optional texmacs_1.0.6.11-1.diff.gz f41a8399315d5c989c2536970277dfcc 3588300 editors optional texmacs-common_1.0.6.11-1_all.deb 1f81d3d9c267970f416d8bc55af110eb 1760246 editors optional texmacs_1.0.6.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/FPi1IXdL1v6kOwRAjKBAJ9qAmR+ucdi3ARIwKo6rBFvZGWCGgCdEorn kfxTuIYV0QAQoPG79eQau3I= =3tFt -END PGP SIGNATURE- Accepted: texmacs-common_1.0.6.11-1_all.deb to pool/main/t/texmacs/texmacs-common_1.0.6.11-1_all.deb texmacs_1.0.6.11-1.diff.gz to pool/main/t/texmacs/texmacs_1.0.6.11-1.diff.gz texmacs_1.0.6.11-1.dsc to pool/main/t/texmacs/texmacs_1.0.6.11-1.dsc texmacs_1.0.6.11-1_i386.deb to pool/main/t/texmacs/texmacs_1.0.6.11-1_i386.deb texmacs_1.0.6.11.orig.tar.gz to pool/main/t/texmacs/texmacs_1.0.6.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bplay 0.991-10 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 20:51:21 -0300 Source: bplay Binary: bplay Architecture: source amd64 Version: 0.991-10 Distribution: unstable Urgency: low Maintainer: Carlos Laviola [EMAIL PROTECTED] Changed-By: Carlos Laviola [EMAIL PROTECTED] Description: bplay - Buffered audio file player/recorder Closes: 307033 327759 Changes: bplay (0.991-10) unstable; urgency=low . * Install the manpages. (Closes: #327759) * debian/copyright: download location is gone, so just removing it for now. * bplay.1: fixed minor typo. (Closes: #307033) * debian/control: Standards-Version bumped to 3.7.2.2. * debian/compat: created, compatible with debhelper V5. * debian/control: Build-Depends on debhelper 5.0.0 now. * debian/rules: no longer ignore the result of 'make clean', removes binary-indep target, and uses dh_install now. Files: d0a2657a54de0dc40c5b1671c4854267 560 sound optional bplay_0.991-10.dsc 0411acc2a5265bae2044cf70b269566d 14639 sound optional bplay_0.991-10.diff.gz bed4008b6d1b3c99064240d6c0238e1d 18616 sound optional bplay_0.991-10_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/FUUZAYCJzUW03IRAkOtAJ9xROiIkkCoYsiQ6MX0E2Lnuuq0pwCeOEKe a9yLpValelIguj1AHQcT0pU= =Wt2J -END PGP SIGNATURE- Accepted: bplay_0.991-10.diff.gz to pool/main/b/bplay/bplay_0.991-10.diff.gz bplay_0.991-10.dsc to pool/main/b/bplay/bplay_0.991-10.dsc bplay_0.991-10_amd64.deb to pool/main/b/bplay/bplay_0.991-10_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted uisp 20050207-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 22:27:27 -0300 Source: uisp Binary: uisp Architecture: source i386 Version: 20050207-4 Distribution: unstable Urgency: low Maintainer: Margarita Manterola [EMAIL PROTECTED] Changed-By: Margarita Manterola [EMAIL PROTECTED] Description: uisp - Micro In-System Programmer for Atmel's AVR MCUs Closes: 417677 Changes: uisp (20050207-4) unstable; urgency=low . * Changed debian/rules to apply dpatches at configure-time. * Fixed the manpage patch accordingly. * Added 30_fix_g++_4.3.dpatch fixing the use of parenthesis with the shift operator. (Closes: #417677) * Cleaned up old 10_const_char.dpatch to new dpatch simpler format. * Switched to debhelper compat level 5. * Cleaned and updated debian/rules * Upgraded to Standards-Version 3.7.2 - No changes needed. * Moved Homepage from pseudo-field to real field in debian/control. Files: abe53513cd5d415c54ed2aadc15d6472 605 electronics extra uisp_20050207-4.dsc 9018092424f990abf06822fdcdfe6a50 4801 electronics extra uisp_20050207-4.diff.gz 6faff1293b0510e2ba6ad01c4269ed7a 57362 electronics extra uisp_20050207-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/FzBlAuUx1tI/64RAquWAJ9M2c+qISgtYoAUo92sa9bF/40vpwCfcdiY HYwNmBG87XY2xqi+4Tb9p+0= =wvzf -END PGP SIGNATURE- Accepted: uisp_20050207-4.diff.gz to pool/main/u/uisp/uisp_20050207-4.diff.gz uisp_20050207-4.dsc to pool/main/u/uisp/uisp_20050207-4.dsc uisp_20050207-4_i386.deb to pool/main/u/uisp/uisp_20050207-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnome-python-desktop 2.20.0-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 20:40:57 -0300 Source: gnome-python-desktop Binary: python-gnome2-desktop-doc python-gnome2-desktop python-gnome2-desktop-dev Architecture: source all i386 Version: 2.20.0-1 Distribution: unstable Urgency: low Maintainer: Loic Minier [EMAIL PROTECTED] Changed-By: Gustavo Noronha Silva [EMAIL PROTECTED] Description: python-gnome2-desktop - Python bindings for the GNOME desktop environment python-gnome2-desktop-dev - Python bindings for the GNOME desktop environment python-gnome2-desktop-doc - Python bindings for the GNOME desktop environment - documentation Closes: 444268 Changes: gnome-python-desktop (2.20.0-1) unstable; urgency=low . * New upstream release - updated version requirements for various libs, including wnck (Closes: #444268) Files: 57a7e7bc124d809f6cc2fe5d8cfb41bb 1603 python optional gnome-python-desktop_2.20.0-1.dsc 857c53a8b7ec6bc12c2a983b853d87d5 644035 python optional gnome-python-desktop_2.20.0.orig.tar.gz a57eae344e01a37be0bd6c744b993b22 4924 python optional gnome-python-desktop_2.20.0-1.diff.gz 7d2b6a24b351be5278883c09df054c93 291052 python optional python-gnome2-desktop_2.20.0-1_i386.deb 3962ac08426141fc44eb4de47c4733e3 70956 doc optional python-gnome2-desktop-doc_2.20.0-1_all.deb f7ced322854ce1db1cf416599cbf53d3 43274 python optional python-gnome2-desktop-dev_2.20.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/EcRt1anjIgqbEsRAu+VAKCbb82s7quNkMEANLuMzCi6R5KHxgCgzUzX j6A1o6crvDl71WtBMXVQLXg= =L1vG -END PGP SIGNATURE- Accepted: gnome-python-desktop_2.20.0-1.diff.gz to pool/main/g/gnome-python-desktop/gnome-python-desktop_2.20.0-1.diff.gz gnome-python-desktop_2.20.0-1.dsc to pool/main/g/gnome-python-desktop/gnome-python-desktop_2.20.0-1.dsc gnome-python-desktop_2.20.0.orig.tar.gz to pool/main/g/gnome-python-desktop/gnome-python-desktop_2.20.0.orig.tar.gz python-gnome2-desktop-dev_2.20.0-1_all.deb to pool/main/g/gnome-python-desktop/python-gnome2-desktop-dev_2.20.0-1_all.deb python-gnome2-desktop-doc_2.20.0-1_all.deb to pool/main/g/gnome-python-desktop/python-gnome2-desktop-doc_2.20.0-1_all.deb python-gnome2-desktop_2.20.0-1_i386.deb to pool/main/g/gnome-python-desktop/python-gnome2-desktop_2.20.0-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted asterisk 1:1.4.11~dfsg-3 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Sep 2007 05:58:29 +0300 Source: asterisk Binary: asterisk-sounds-main asterisk-h323 asterisk asterisk-config asterisk-dbg asterisk-dev asterisk-doc Architecture: source all i386 Version: 1:1.4.11~dfsg-3 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team [EMAIL PROTECTED] Changed-By: Faidon Liambotis [EMAIL PROTECTED] Description: asterisk - Open Source Private Branch Exchange (PBX) asterisk-config - Configuration files for Asterisk asterisk-dbg - Debugging symbols for Asterisk asterisk-dev - Development files for Asterisk asterisk-doc - Source code documentation for Asterisk asterisk-h323 - H.323 protocol support for Asterisk asterisk-sounds-main - Core Sound files for Asterisk (English) Closes: 444322 Changes: asterisk (1:1.4.11~dfsg-3) unstable; urgency=low . * Depend on libsnmp-dev instead of libsnmp10-dev. Fixes FTBFS (Closes: #444322) Files: 871204ea7eeacdcd544527aa3690e4b6 1634 comm optional asterisk_1.4.11~dfsg-3.dsc 53018dbb6401c8a650c06d2acf516f71 161226 comm optional asterisk_1.4.11~dfsg-3.diff.gz 1daafeb57234426529f476c158ca 31338244 doc extra asterisk-doc_1.4.11~dfsg-3_all.deb f266d2165960b8ac53cc22a815936b9d 308042 devel extra asterisk-dev_1.4.11~dfsg-3_all.deb 34d4112c73031aa4ab6140ad991c0514 1647330 comm optional asterisk-sounds-main_1.4.11~dfsg-3_all.deb 7f4b3fe1079c4f078a9382a31ba00b70 369494 comm optional asterisk-config_1.4.11~dfsg-3_all.deb e1c4d0368794aae1f5e5e5cc916411b4 2063000 comm optional asterisk_1.4.11~dfsg-3_i386.deb 3c2ed450e8bf77d510f2e88ba4bab2f3 276236 comm optional asterisk-h323_1.4.11~dfsg-3_i386.deb 0b1e4eb4795492c9f77dcb99bb7402e8 12120538 devel extra asterisk-dbg_1.4.11~dfsg-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/HA+Vty5d8XpUzMRAgP3AJ44iJgAYYVO0H2PMmLdmhcEdC2ajwCfcru/ Mv9+GaYvDmCtmtdCr6HR70s= =Xvv5 -END PGP SIGNATURE- Accepted: asterisk-config_1.4.11~dfsg-3_all.deb to pool/main/a/asterisk/asterisk-config_1.4.11~dfsg-3_all.deb asterisk-dbg_1.4.11~dfsg-3_i386.deb to pool/main/a/asterisk/asterisk-dbg_1.4.11~dfsg-3_i386.deb asterisk-dev_1.4.11~dfsg-3_all.deb to pool/main/a/asterisk/asterisk-dev_1.4.11~dfsg-3_all.deb asterisk-doc_1.4.11~dfsg-3_all.deb to pool/main/a/asterisk/asterisk-doc_1.4.11~dfsg-3_all.deb asterisk-h323_1.4.11~dfsg-3_i386.deb to pool/main/a/asterisk/asterisk-h323_1.4.11~dfsg-3_i386.deb asterisk-sounds-main_1.4.11~dfsg-3_all.deb to pool/main/a/asterisk/asterisk-sounds-main_1.4.11~dfsg-3_all.deb asterisk_1.4.11~dfsg-3.diff.gz to pool/main/a/asterisk/asterisk_1.4.11~dfsg-3.diff.gz asterisk_1.4.11~dfsg-3.dsc to pool/main/a/asterisk/asterisk_1.4.11~dfsg-3.dsc asterisk_1.4.11~dfsg-3_i386.deb to pool/main/a/asterisk/asterisk_1.4.11~dfsg-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted iceweasel 2.0.0.7-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 Sep 2007 22:26:44 -0400 Source: iceweasel Binary: iceweasel-dbg iceweasel-gnome-support iceweasel-dom-inspector iceweasel Architecture: source amd64 all Version: 2.0.0.7-2 Distribution: unstable Urgency: low Maintainer: Eric Dorland [EMAIL PROTECTED] Changed-By: Eric Dorland [EMAIL PROTECTED] Description: iceweasel - lightweight web browser based on Mozilla iceweasel-dbg - debugging symbols for iceweasel iceweasel-dom-inspector - tool for inspecting the DOM of pages in Iceweasel iceweasel-gnome-support - Support for Gnome in Iceweasel Closes: 444149 Changes: iceweasel (2.0.0.7-2) unstable; urgency=low . * gfx/src/gtk/gtk2drawing.c: Add patch from bz#389801 for gtk problems with gtk 2.12. (Closes: #444149) Files: 8a3cbab68be9f4bb9e43dc5d1db9e059 1197 web optional iceweasel_2.0.0.7-2.dsc 2d3b1174b500ce0ad1a9058e54465b43 186113 web optional iceweasel_2.0.0.7-2.diff.gz d7a6d74989dc7879a4010d16e825a666 239656 web optional iceweasel-dom-inspector_2.0.0.7-2_all.deb 6d92c651c57eea7940aaa841285a497c 9229148 web optional iceweasel_2.0.0.7-2_amd64.deb 029bc978c5cdaf6555d97ba0d3155f0b 87572 gnome optional iceweasel-gnome-support_2.0.0.7-2_amd64.deb 75db2a0d21bb47f5ccc12fb19b9b89a1 74524888 devel extra iceweasel-dbg_2.0.0.7-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG/HasYemOzxbZcMYRAq0UAKDMWhba+GzAfM4nWC2NfE1flpkj4gCdH4N/ 7NPYPkSl70osue/vK7h+CBU= =z+T3 -END PGP SIGNATURE- Accepted: iceweasel-dbg_2.0.0.7-2_amd64.deb to pool/main/i/iceweasel/iceweasel-dbg_2.0.0.7-2_amd64.deb iceweasel-dom-inspector_2.0.0.7-2_all.deb to pool/main/i/iceweasel/iceweasel-dom-inspector_2.0.0.7-2_all.deb iceweasel-gnome-support_2.0.0.7-2_amd64.deb to pool/main/i/iceweasel/iceweasel-gnome-support_2.0.0.7-2_amd64.deb iceweasel_2.0.0.7-2.diff.gz to pool/main/i/iceweasel/iceweasel_2.0.0.7-2.diff.gz iceweasel_2.0.0.7-2.dsc to pool/main/i/iceweasel/iceweasel_2.0.0.7-2.dsc iceweasel_2.0.0.7-2_amd64.deb to pool/main/i/iceweasel/iceweasel_2.0.0.7-2_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
