Re: bug à reproduire : mauvaise trans mission de la map clavier X entre amd64 e t i386
Sebastien Chaumat a écrit : Bonjour à tous, Est-ce que quelqu'un peu me confirmer ce bug, je n'arrive pas à convaincre l'équipe de xorg qu'il existe : - sur amd64 yeap - installer un chroot sid i386 - installer xbase-clients dans ce chroot J'ai juste copié dans /tmp depuis une machine x86 : - /usr/bin/xev - /usr/lib/libX11.so.6* - /usr/lib/libXau.so.6* - /usr/lib/libXdmcp.so.6* HORS du chroot lancer /chroot/sid-ia32/usr/bin/xev J'ai lancé : [EMAIL PROTECTED]:/tmp$ LD_LIBRARY_PATH=/tmp ldd ./xev la touche é renvoie : KeyRelease event, serial 26, synthetic NO, window 0x141, root 0x137, subw 0x142, time 3805396627, (39,33), root:(106,531), state 0x0, keycode 11 (keysym 0xe9, eacute), same_screen YES, XLookupString gives 0 bytes: Pareil : KeyPress event, serial 22, synthetic NO, window 0x481, root 0x4c, subw 0x0, time 4172326429, (1075,593), root:(1080,642), state 0x0, keycode 11 (keysym 0xe9, eacute), same_screen YES, XLookupString gives 0 bytes: Au lieu de KeyPress event, serial 30, synthetic NO, window 0x181, root 0x137, subw 0x182, time 3805599600, (46,38), root:(630,707), state 0x0, keycode 11 (keysym 0xe9, eacute), same_screen YES, XLookupString gives 2 bytes: (c3 a9) é XmbLookupString gives 2 bytes: (c3 a9) é XFilterEvent returns: False Le xev natif renvoie lui : KeyPress event, serial 26, synthetic NO, window 0x481, root 0x4c, subw 0x0, time 4172528547, (1182,656), root:(1192,729), state 0x0, keycode 11 (keysym 0xe9, eacute), same_screen YES, XLookupString gives 2 bytes: (c3 a9) é XmbLookupString gives 2 bytes: (c3 a9) é XFilterEvent returns: False Cela signifie qu'une application X 32 bits exécutée dans un environement 64 bits est incapable d'afficher les accents. Sincèrement merci par avance à qui voudra bien essayer de reproduire ce bug. J'espère que ça t'aidera La machine amd64 et la machine i386 (depuis laquelle j'ai copié le binaire et les libs) sont toutes les deux en Debian sid mise à jour ce matin. A+ Vince Sébastien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Updated: Russian and Ukrainian translation/localization services
Dear friends, Olivia Translations provides excellent Russian and Ukrainian translation/localization services with the best rates. If you are interested, welcome to http://www.olivia-translations.org for more information. --- We discovered your address while looking through the open sources and directories. To ensure that you do not receive such messages accidentally in the future please reply just with Unsubscribe in subject line.
Re: Silly Packaging Problem
also sprach Michael S. Peek [EMAIL PROTECTED] [2006.08.09.1322 +0100]: It seems that Debian doesn't care about keeping up with files created dynamically via install scripts. For instance, I can type 'dpkg -S /etc/papersize', and I get back 'dpkg: /etc/papersize not found.' Yes, /etc/papersize is not installed by dpkg. Is this correct, or is there a way to assign package ownership of dynamically-created files? No, at least not for /etc. You could install the file, the overwrite it, but files installed to /etc by dpkg are conffiles and those must not be touched programmatically, according to policy. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system it is ok to let your mind go blank, but please turn off the sound. signature.asc Description: Digital signature (GPG/PGP)
Re: piuparts unprocessed failed logs page
ke, 2006-08-09 kello 11:45 -0700, Kevin B. McCarty kirjoitti: I was looking through these, and at least the following errors appear to be false positives for the given packages, caused only by some combination of x11-common, xcursor-themes, xutils (which leaves behind junk in /etc/X11/rstart), xlibs-data (which leaves things in /usr/X11R6/lib/X11/icons, looks like #362109 was already filed about this) and/or ttf-bitstream-vera. Yeah, that happens a lot. piuparts can't know (or at least doesn't try; anyone wanting to send an AI patch is welcome) which package it is that actually fails, so if there's a package that lots of others depend on (like xutils or the others), and that fails (and sometimes they fail only when tested with packages that depend on them), there's a lot of false positives. That's why logs are processed manually before bugs are reported. Hope this is helpful. Sure, thanks. -- Programming should be fun, otherwise you're doing something wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New source packages sometimes bypassing NEW?
* Kevin B. McCarty [Wed, 09 Aug 2006 15:42:10 -0700]: Hi all, Hi Kevin, In splitting up the cernlib source package, I just uploaded three sets of .debs for new source packages paw, mclibs and geant321. All of these new source packages produce binary .debs that previously were created from the cernlib source package. That is, there are no new .debs, only source packages. Both paw and geant321 .debs/sources were ACCEPTED immediately (the message for paw, for instance, is forwarded below), while mclibs went into the NEW queue. I had thought that new source packages are always pushed into NEW these days. What accounts for this discrepancy, and is it something that should be looked into? (I'm certainly not complaining about paw and geant321 bypassing NEW, mind you, but the discrepancy might indicate something going wrong in the infrastructure.) No, this is normal behavior of the software. If you look closer at your uploads, you'll see that the two sources that did not hit NEW (paw and geant321) had already binary packages in the archive with that name (provided by cernlib), while there was no mclibs binary package. Source overrides are looked up first in the binary override list, which explains the behavior you observed. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org When it is not necessary to make a decision, it is necessary not to make a decision. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Wouter Verhelst [EMAIL PROTECTED] wrote: On Wed, Aug 09, 2006 at 03:44:57PM +0200, Joerg Schilling wrote: Indeed, you are not free to add whatever piece of crap to the Debian archive regardless of the license. Call it a non-free project if you want, but this would only look like a calumniation campaign against us. If you continue to spread this kind of personal insults, Err, ENOPARSE. How is the above paragraph a personal insult? We are talking about my software and you are talking about a piece of crap, I am sorry but this is insulting. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Josselin Mouette [EMAIL PROTECTED] wrote: Le mercredi 09 août 2006 à 15:44 +0200, Joerg Schilling a écrit : You are again trying to intentionally tell us untrue things about my software! The Debian project accepted the clauses in cdrecord ~ 4 years ago. That doesn't mean the project still considers them acceptable *NOW*. So you like to tell me that Debian is not trustworthy? And note: the CDDL is one of 9 preferred licenses: http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:11636:200607:nknhhdligldemhkfbhpd One of the preferred licenses *by the OSI*. Debian has nothing to do with the OSI and doesn't not rely on the OSI to be told what is free or not. Can't you even understand something that simple? I understand things but if Debian people have problems to understand that the OSI is the only independend institution that deals with OSS Licenses, you are obviously a bit out of order. Note that the CDDL has been chosen because it is a first class license as it allows to combine CDDL code with other code and that the GPL only is in this list because the GPL is widely used but not because of the quality of the license. BTW: The GPL is definitely non-free if someone makes use of GPL § 8. It has no problem with any of the DFSG requirements. Many people have expressed complaints about the choice-of-venue clause and think it is not acceptable for Debian. I am not one of them and I believe the CDDL to be free, but I would surely not claim there is consensus around that in the project. I repeat: currently no CDDL project has been accepted yet. Well then help to explain these other people that only a malicious distributor or licensee needs to be in fear of this clause and that the clause protects the Author for malicious licensees. If the Authors will not be protected, we will end up with no OSS in the future... If you claim different things, you are obviously speading FUD and not a serious discussion partner - sorry. Why is anyone disagreeing with you necessarily spreading FUD, lying, trying to hurt your reputation, or anything like this? Bear with it: most people disagree with you. I do not know a SINGLE Debian developer who believes your license combination to be distributable. Does that make only hundreds of trolls who are just trying to spread FUD against you? Well this is strange. I did not invent this idea by myself and I did ask many people about their opinion. What I see is that only a few people from Debian have a different opinion and they are even unable to prove their claims by correctly quoting the parts pf the GPL that they believe prevents what I am doing. Stop the paranoia. People disagree with you, and you have to accept that. They are not disagreeing with you just to hurt you *personally*. This is why you should listen to these criticisms instead of throwing them away by calling them FUD. No one is going to listen to you if you are still unable to listen to anyone. Sorrry, the people from Debian need to stop _their_ paranoia as they are a minority with a strange opinion. I listen to people but if I see that they spread FUD instead of offering useful and traceable information I believe at some point that is does not make sense to continue a discussion. The Debian people should just read their DFSG rules and try to understand them DFSG §9 claims that a license is only free if it does not conaminate other software on the same medium. The medium in case of cdrtools is the tarball. The cdrtools distribution is based on two cases to allow a combination of different licenses: 1) Mere aggregation. This applies for The Schily Makefilesystem and other software as well as with e.g. cdda2wav and cdrecord. 2) GPLd software uses CDDLd libraries. This is done in a way that does not make the CDDLd software a derived work of the GPL software. This is done for mkisofs an libschily/libscg. If Debian sees a problem with 1) bedause of their interpretation of the GPL, then they need to clearly call the GPL a non-free license. BTW: any GPL software that makes use of GPL §8 clearly violates the DFSG, so I would not call the GPL a generaily free license. If Debian has a problem with 2) they would need to call things like Cygwin a violation of the GPL and would be in contradiction to usual GPL interpretations. If you are so braindead not to understand that this license combination is perfectly OK, I cannot help you. It seems that I did waste already too much time with you. A discussion only makes sense in case that the other side is able/willing to understand simple explanataions... Your simple explanations are wrong. I'm not going to re-explain what Wouter explained better than I would. If you cannot understand that the CDDL is incompatible with the GPL, you should stop talking about licenses and only keep coding, a task for which you seem to have more talent. You still did not read
Re: cdrtools
Goswin von Brederlow [EMAIL PROTECTED] wrote: Joerg Schilling [EMAIL PROTECTED] writes: Josselin Mouette [EMAIL PROTECTED] wrote: GR stated that invariant sections aren't acceptable for the specific GFDL case, and there is no reason why they would be acceptable for If Linux Distributions would not distribute bastardized versions of cdrecord, there was no need to add the statements you might be talking about. Sorry, but you say your software is free. That means Debian (or anyone else) is free to bastardize cdrecord as much as they want. That is called freedom. You can require proper notice or even a name change of the software when such bastardization is done but when you start forbiding such changes then your software is no longer free. I am sorry but it seems that you miss to read the Urheberrecht AND e.g. the GPL. Both forbid to damage the reputation of the original author. As I _did_ already receive coplaints against cdrecord that have been e.g. based on the fact that Linux distributoions change the name for the file /etc/default/cdrercord and the fact that the basterdized behavior is incompatible with the (officially) documented behavior, these Linux distributions cause harm Free software gives you the right to change software but free software definitely does _not_ give you the right to use the originam _name_ of the software in case you apply incompatible changes or in case that you introduce bugs. The license is related to urheberrecht, using the original name of the software is related to trade mark right If people at Denbian are missing this kind of basic knowledge, how would it be possible to discuss license issues in a serious way? Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Joerg Schilling wrote: The Debian project accepted the clauses in cdrecord ~ 4 years ago. That doesn't mean the project still considers them acceptable *NOW*. So you like to tell me that Debian is not trustworthy? The requirements of the project changed. That is called progress. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Goswin von Brederlow [EMAIL PROTECTED] wrote: If you don't know that you just need to use a clearly _different_ _name_ for such a fork, I can't help you. Read the preamble from the GPL to understand your fault. So all we need to do to apeace you is to call is debianrecord? If that is all that is needed for you not to complain that we include unsupported dvd support and the like then that can easily be aranged. This is really funny.. The oficial cdrecord _does_ support DVD writing. Why do you like to first hide this feature from your users and then later add broken DVD support? But then please just say so. The GPL alone does not require such a rename, only that the modified files to carry prominent notices stating that you changed the files and the date of any change. The GPL does not allow you to use the original name.. This is related to different things (trade mark right). You should just add a requirement for renaming the software instead of your invariant section and extra printing code requirement. Note that the name dvdrecord is illegal too as this name is too close to the name cdrecord and many people use the name dvdrecord for the newer versions of cdrecord that include DVD writing although I did never mentioned this name for my software. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Hi Joerg, Le 09.08.2006 15:33, Joerg Schilling a écrit : If you don't know that you just need to use a clearly _different_ _name_ for such a fork, I can't help you. Read the preamble from the GPL to understand your fault. Beside the licensing issues, why do you care so much patched version of your software to be distributed with big WARNINGS, a different name and tutti quanti ? AFAIK, each Linux distribution have a huge bag of patches it applies on the Linux kernel and the reputation of the kernel devels is not compromised. And it's quite the same about gcc and many pieces of free softwares. Aren't you afraid that your reputation is _far_ more about the issues to ditribute your software than about the quality of your software ? Regards, Jean Parpaillon -- _ / La science a fait de nous des dieux \ | avant même que nous méritions d'être | | des hommes. -+- Jean Rostand| \ (1894-1977) -+- / - \ ^__^ \ (**)\___ (__)\ )\/\ U ||w | || || -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITP: dc-qt -- GUI frontend for the dc protocol
Package: wnpp Owner: Steffen Joeris [EMAIL PROTECTED] Severity: wishlist * Package name: dc-qt Version : 0.2.0-alpha Upstream Author : Arsenij Vodjanov [EMAIL PROTECTED] * URL : http://dc-qt.sourceforge.net/wiki/index.php/Main_Page * License : GPL Programming Lang: C++ Description : GUI frontend for the dc protocol dc-qt is a qt front-end for the dctc program. dctc handles all communication with dc hubs and clients, while dc-qt presents an interface that has many of the features of the original directconnect client, plus some really useful improvements. . It is intended for peer-based file-sharing. In practise it works better than gnutella and other similar systems as it allows dc hubs (servers) administators to require clients to share specified amount of data. The amount is usually based on type of client's connection and it is used not to hurt or exclude anybody but to make file sharing fair play. . dc-qt is still alpha, so some care has to be taken - try it out! I am really interested in that package as I use it on a daily basis at university. pgp7OSrUoKRme.pgp Description: PGP signature
MIME type of OCaml source files
Hi, Inclusion of the OCaml syntax highlighting file in GtkTextView is blocked until FreeDesktop includes the MIME type in its shared-mime-info database, but I don't know the MIME type of OCaml source files. Would someone happen to know what the MIME type of OCaml files is? I couldn't find it in Google, and the tools I tried reported text/plain. And BTWn are there multiple possible extensions for source files? (I mailed [EMAIL PROTECTED], but didn't receive any reply.) Thanks, -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
And note: the CDDL is one of 9 preferred licenses: http://www.crynwr.com/cgi-bin/ezmlm-cgi?3:mss:11636:200607:nknhhdligldemhkfbhpd One of the preferred licenses *by the OSI*. Debian has nothing to do with the OSI and doesn't not rely on the OSI to be told what is free or not. Can't you even understand something that simple? I understand things but if Debian people have problems to understand that the OSI is the only independend institution that deals with OSS Licenses, you are obviously a bit out of order. Debian has no problem understanding that they will independently determine what licenses are suitable to Debian. If you want your software in Debian, use a currently Debian approved license. On 10/08/06, Joerg Schilling [EMAIL PROTECTED] wrote: Goswin von Brederlow [EMAIL PROTECTED] wrote: Note that the name dvdrecord is illegal too as this name is too close to the name cdrecord and many people use the name dvdrecord for the newer versions of cdrecord that include DVD writing although I did never mentioned this name for my software. Surely you jest... then again, perhaps you don't. It is highly unlikely (that any jurisdiction would recognise) that there could be any restriction on use of the name dvdrecord resulting from the existence of another highly generic name cdrecord: cdrecord and dvdrecord are generic names, describing what the software does... granted you may have a claim to cdrecord having named your software thus, but even this might be challenged by close similarly generic cdrecordtype variants... it is questionable whether cdrecorder or recordcd for example would be protected... you cannot by virtue of using the generic type name cdrecord control variants of the genric term let alone (yet) another name that is as generic (and different): dvdrecord. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: MIME type of OCaml source files
On Thursday 10 August 2006 17:30, Loïc Minier wrote: Hi, Inclusion of the OCaml syntax highlighting file in GtkTextView is blocked until FreeDesktop includes the MIME type in its shared-mime-info database, but I don't know the MIME type of OCaml source files. Would someone happen to know what the MIME type of OCaml files is? I couldn't find it in Google, and the tools I tried reported text/plain. There is no official MIME type assigned to OCaml AFAIK. http://lists.debian.org/debian-ocaml-maint/2006/07/msg00201.html And BTWn are there multiple possible extensions for source files? http://lists.debian.org/debian-ocaml-maint/2006/07/msg00199.html (I mailed [EMAIL PROTECTED], but didn't receive any reply.) both from d-o-m ;-) -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Joerg Schilling [EMAIL PROTECTED] writes: Goswin von Brederlow [EMAIL PROTECTED] wrote: If you don't know that you just need to use a clearly _different_ _name_ for such a fork, I can't help you. Read the preamble from the GPL to understand your fault. So all we need to do to apeace you is to call is debianrecord? If that is all that is needed for you not to complain that we include unsupported dvd support and the like then that can easily be aranged. This is really funny.. The oficial cdrecord _does_ support DVD writing. Why do you like to first hide this feature from your users and then later add broken DVD support? ftp://ftp.berlios.de/pub/cdrecord/ProDVD/README NOTE: the DVD-recording drivers have been added to the OpenSource part on May 15th 2006 with cdrtools-2.01.01a09. It is nice that you finaly made this free but it is a rather recent change given: ** NEW: On March 9th, we are celebrating 6 years of cdrecord-ProDVD Sorry that I'm not totally up to date. But then please just say so. The GPL alone does not require such a rename, only that the modified files to carry prominent notices stating that you changed the files and the date of any change. The GPL does not allow you to use the original name.. This is related to different things (trade mark right). So you agree with me that it is not a GPL issue. If you have a trade mark on cdrecord and want to enforce it that is your decision. But it is not GPL related as you seem to claim in the source file. You should just add a requirement for renaming the software instead of your invariant section and extra printing code requirement. Note that the name dvdrecord is illegal too as this name is too close to the name cdrecord and many people use the name dvdrecord for the newer versions of cdrecord that include DVD writing although I did never mentioned this name for my software. So is using IBM or Coca-Cola. What has that got to do with it? Jörg MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
On Thu, Aug 10, 2006 at 11:01:30AM +0100, martin f krafft wrote: No, at least not for /etc. You could install the file, the overwrite it, but files installed to /etc by dpkg are conffiles and those must not be touched programmatically, according to policy. i think a better solution (and one that has been proposed in the past) would be to have a way of providing dpkg with information about such dynamically created files. this would also be helpful for stuff like logfiles. a fairly straightforward (says he who has not looked at dpkg's source) would be to provide a new file in the control section of the deb which contained a series of globs which could be used to match such files. then, if a query through dpkg -S fails to find an owner of a file it could go through the potentially longer process of searching through these files, reporting all matches. sean signature.asc Description: Digital signature
Re: Silly Packaging Problem
sean finney [EMAIL PROTECTED] writes: On Thu, Aug 10, 2006 at 11:01:30AM +0100, martin f krafft wrote: No, at least not for /etc. You could install the file, the overwrite it, but files installed to /etc by dpkg are conffiles and those must not be touched programmatically, according to policy. i think a better solution (and one that has been proposed in the past) would be to have a way of providing dpkg with information about such dynamically created files. this would also be helpful for stuff like logfiles. a fairly straightforward (says he who has not looked at dpkg's source) would be to provide a new file in the control section of the deb which contained a series of globs which could be used to match such files. then, if a query through dpkg -S fails to find an owner of a file it could go through the potentially longer process of searching through these files, reporting all matches. sean How about allowing conffiles to list files that are generated at install time and are not included in the deb? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Joerg Schilling dijo [Thu, Aug 10, 2006 at 02:49:36PM +0200]: As I _did_ already receive coplaints against cdrecord that have been e.g. based on the fact that Linux distributoions change the name for the file /etc/default/cdrercord and the fact that the basterdized behavior is incompatible with the (officially) documented behavior, these Linux distributions cause harm Free software gives you the right to change software but free software definitely does _not_ give you the right to use the originam _name_ of the software in case you apply incompatible changes or in case that you introduce bugs. The license is related to urheberrecht, using the original name of the software is related to trade mark right If people at Denbian are missing this kind of basic knowledge, how would it be possible to discuss license issues in a serious way? I am currently maintainer (co-maintainer for most of them) for 70 packages, most of them quite easy and low-maintenance. However, some of them have patches, maybe adding a specific functionality the author didn't want to include in his official version, maybe fixing some idiosyncratic differencies (i.e. PDF::API2 comes to mind - It defines sections in its documentation which don't cleanly map to what's used in regular manpages, so I did the changes, but I must keep patching the author's official module). You say that I don't have the right to distribute this under the name PDF::API2 in Debian, do I understand correctly? Please tell me: This module is a Perl library. If I modify it to become PDF::API2::Debian, how will our users' code be portable? How can other pieces of code link against this one and not be Debian-specific? A compromise we have reached in some cases is to change the _version_ number (i.e. in Mail::IMAPClient, where I had to remove some non-free files from the distributed tarball) appending '+deb' to it (so for us it's now 2.2.9+deb-4). It clearly shows it's not the original author's code, but that the code _is_ contained. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
also sprach Goswin von Brederlow [EMAIL PROTECTED] [2006.08.10.1647 +0100]: How about allowing conffiles to list files that are generated at install time and are not included in the deb? You can, but then you run up against policy. You are not allowed to touch a conffile with a script. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system it may look like i'm just sitting here doing nothing. but i'm really actively waiting for all my problems to go away. signature.asc Description: Digital signature (GPG/PGP)
Re: MIME type of OCaml source files
On Thu, Aug 10, 2006, George Danchev wrote: (I mailed [EMAIL PROTECTED], but didn't receive any reply.) both from d-o-m ;-) I should have requested to be Cc:ed, but forgot to do so, thanks! -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: libdevice-serialport-perl 1.002-1, or picking up where 0.22 left off
Hi all! =) I'm requesting for a sponsor for my `libdevice-serialport-perl' package for the Perl module Device::SerialPort version 1.002 . This package is supposed to be under the care of Michael D. Mattice (mattice on db, LoRez on IRC,) but it hasn't been touched by him in exactly 2 years (the last upload from him was on 2004-08-10.) Since then this package has underwent 3 NMUs, the first of which severely broke the package because it somehow patched back the old release code to the new release. I have tried pinging mattice via email and IRC, but to no avail. Sometime ago I asked for the advice of debian-qa, and I was told that taking his package seems ok now, short of a real QA upload. As such, I have taken steps to create a package with the _real_ new upstream release, closing bugs, and acknowledging the three NMUs along the way. The new package is available at Debian Mentors,[0] and it is lintian clean. [0] http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=libdevice-serialport-perl Furthermore, let me emphasize that I did this package not just because it needed updating, but because I needed this package to be updated for the `sendpage' package to work correctly (speaking of which, the two packages are software that I'm involved with on the Google Summer of Code project for Sendpage/OSDL.[1]) Thus the urgency of my request. [1] http://code.google.com/soc/osdl/appinfo.html?csaid=F69CC123BDA4788A I would be glad if someone uploaded this package for me. Thanks in advance! Cheers, Zakame -- Zak B. Elep || http://zakame.spunge.org [EMAIL PROTECTED] || [EMAIL PROTECTED] 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
On Thu August 10 2006 10:16, martin f krafft wrote: also sprach Goswin von Brederlow [EMAIL PROTECTED] [2006.08.10.1647 +0100]: How about allowing conffiles to list files that are generated at install time and are not included in the deb? You can, but then you run up against policy. You are not allowed to touch a conffile with a script. Is there anything prohibiting an update-package.list command? Would updating /var/lib/dpkg/info/*.list files without touching the appropriate Installed-Size: field be OK? Is there any way to get a handle on how much more CPU time and HDD space would be used if all packages updated their meta-info at install time? - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.1925 +0100]: Would updating /var/lib/dpkg/info/*.list files without touching the appropriate Installed-Size: field be OK? Definitely not. /var/lib/dpkg is the domain of dpkg. Do not go there. You must not even assume that /var/lib/dpkg/info/*.list is the list of installed filed. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system education is an admirable thing, but it is well to remember from time to time that nothing that is worth knowing can be taught. -- oscar wilde signature.asc Description: Digital signature (GPG/PGP)
Re: Silly Packaging Problem
On Thu August 10 2006 12:40, martin f krafft wrote: also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.1925 +0100]: Would updating /var/lib/dpkg/info/*.list files without touching the appropriate Installed-Size: field be OK? Definitely not. /var/lib/dpkg is the domain of dpkg. Do not go there. You must not even assume that /var/lib/dpkg/info/*.list is the list of installed filed. Such a utility would need to be shipped with dpkg, a 3rd party or random DD implementing it would be silly for anything but local consumption. Is that the only problem? - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.1959 +0100]: Such a utility would need to be shipped with dpkg, a 3rd party or random DD implementing it would be silly for anything but local consumption. Is that the only problem? If dpkg knew how to track files it did not directly install, of course it would be of benefit. The question is how to let it know which files are meant by this. I suppose DEBIAN/conffiles-(files installed to /etc by the package) would work, but I'd be careful about touching the conffile concept. Maybe DEBIAN/dynfiles -- since after all it (sh|w)ould be used for things like logfiles as well. And it should be able to just take a directory, like /var/lib/dpkg, assuming that everything underneath that directory would be created by one package, dpkg in this case. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system one morning i shot an elephant in my pyjamas. how he got into my pyjamas i'll never know. -- groucho marx signature.asc Description: Digital signature (GPG/PGP)
Re: cdrtools
On 10742 March 1977, Joerg Schilling wrote: Both forbid to damage the reputation of the original author. Free software gives you the right to change software but free software definitely does _not_ give you the right to use the originam _name_ of the software in case you apply incompatible changes or in case that you introduce bugs. The license is related to urheberrecht, using the original name of the software is related to trade mark right Oh god, Im so sick of all this cdrecord flaming. So, how about the following (and please read it completly before you answer, it contains multiple options): - We go and take cdrecord and modify it with whatever we believe we may need *and* * remove your name completly from any output the programs give, and also mention that anyone who has problems has to contact us, not you. Your name stays in the source, of course. * or alternatively leave your name in the output, in a form similar to this is based on *** originally written by and then also mention to contact us for problems. Now, the name for this. One could imagine a lot of things. There is a possibility of naming it debian-burn, debianrecord or just burntools. The names of the other included parts shouldnt change, ie it should stay mkisofs and cdda2wav. For the short term the package would mention in its description that its based on cdrtools (and have a Provides: cdrtools in its technical part), so we do not make too much problems for the next release, as thats scheduled to be soon, after that release (schedule for december this year) we could/would also drop that. Future development should merge changes from you wherever possible and also give back patches, if we have something you might be interested in. What do you say, what name would not be ok in your opinion and which of the two options should we take? (Note that one of the first steps would be to remove the CDDL parts, as - if you like it or not - the license is not compatible with GPL. Having it approved by OSI is worth nothing, as not OSI is the standard we take for inclusion into Debian, Debian itself (and basically the DFSG together with a bit of common-sense) is.) For all those interested in the Debian part of it when this starts (Joerg, you can skip this): I will open an alioth project for it, import the full source and start with it. Anyone who wants to help is free to join. -- bye Joerg Wie gesagt, mein /proc/kcore ist 536MB gross und ich würde meinen Rechner gern davon befreien. Ein rm -f schlägt fehl! Ein Reboot hat auch nix geholfen. -- [EMAIL PROTECTED] pgpxTLWqKrs9N.pgp Description: PGP signature
Re: Silly Packaging Problem
On Thu August 10 2006 13:13, martin f krafft wrote: also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.1959 +0100]: Such a utility would need to be shipped with dpkg, a 3rd party or random DD implementing it would be silly for anything but local consumption. Is that the only problem? If dpkg knew how to track files it did not directly install, of course it would be of benefit. The question is how to let it know which files are meant by this. I suppose DEBIAN/conffiles-(files installed to /etc by the package) would work, but I'd be careful about touching the conffile concept. Maybe DEBIAN/dynfiles -- since after all it (sh|w)ould be used for things like logfiles as well. And it should be able to just take a directory, like /var/lib/dpkg, assuming that everything underneath that directory would be created by one package, dpkg in this case. I would expect usefulness with most generated files (all, if one thinks that every file resulting from a pkg install should be dpkg -S-able). It may also be useful to create local virtual packages for stuff like papersize if there is no good package to append them to. An update-package command, run at install time by the maintainer's scripts right after file generation succeeds, would head off potential problems with synchronization that are outside of the Maintainer's control (e.g., DEBIAN/dynfiles containing incorrectly generated paths) and would be simpler to implement, specifically, dynfiles vs. update-package: an infrastructure which operates at package build and install time, requiring packages and all helpers to be re-engineered[1] to make use of the feature vs. a command which knows how to append a file to a package and can be added to any package's scripts with a line or two of minor code, only depends on dpkg's external stability to continue to work, and whose behaviour could be controlled from a single point[2] Adding a directory appears to be something which could be useful (even if only as a shorthand notation[3]), but I don't think it could be done without touching dpkg internals and a big chunk of the tools (recognizing that a directories contents are owned by a pkg is new). - Bruce [1] re-engineered... maybe a bit dramatic and overstated, but unless there is a way to pick the generated paths out of the existing maintainer scripts the conversion would require re-thinking and re-doing existing work, afaict [2] `single point control'... seems to be an important characteristic given the Python transition's recent problems with the various tools being out of sync wrt an evolving policy [3] if only as... if the typical package.list file is less than the size of a typical disk block then there could be an additional processing overhead for no gain in the typical case, that would suck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.2124 +0100]: An update-package command, run at install time by the maintainer's scripts right after file generation succeeds, would head off potential problems with synchronization that are outside of the Maintainer's control (e.g., DEBIAN/dynfiles containing incorrectly generated paths) That's a bug then. I'd much rather prefer maintainer control than some script magic. How would the script determine which files were added anyway? -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system anyone who says sunshine brings happiness has never danced in the rain. signature.asc Description: Digital signature (GPG/PGP)
Re: Buildds still not picking up new architectures, why?
Hi Kevin,
On Wed, Aug 09, 2006 at 04:38:20PM -0400, Kevin Mark wrote:
Hi Aurélien G, (sorry for the bad conversion by mutt)
No problem, I am still not an UTF-8 guy, so my local ISO-8859-15
encoding is the culprit for you. ;)
So there is ONE w-b for {i386,ppc,...) and there is one buildd for each
arch that connects to that ONE w-b?
Exactly, but several buildds for each architecture which take the
packages with the status 'Needs-Build' from wanna-build.
Cheers,
--
.''`. Aurélien GÉRÔME
: :' :
`. `'` Free Software Developer
`- Unix Sys Net Admin
signature.asc
Description: Digital signature
Re: Silly Packaging Problem
On Thu August 10 2006 15:10, martin f krafft wrote: also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.2124 +0100]: An update-package command, run at install time by the maintainer's scripts right after file generation succeeds, would head off potential problems with synchronization that are outside of the Maintainer's control (e.g., DEBIAN/dynfiles containing incorrectly generated paths) That's a bug then. I'd much rather prefer maintainer control than some script magic. How would the script determine which files were added anyway? No point setting oneself up for bugs if it is not necessary. The script wouldn't determine anything, it would simply append paths to the package's list of paths. The Maintainer would need to call the script right after file generation succeeds, or perhaps with a list of files just generated, or as part of an install if packageless files are known to exist. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
Joerg Jaspert [EMAIL PROTECTED] wrote: So, how about the following (and please read it completly before you answer, it contains multiple options): I am sorry, but I cannot believe that you like to make serious proposal with the text you wrote. Let me make a proposal that makes sense for now and the future: 1) Throw out Eduard Bloch. He has been the biggest problem for Debian in the past years. Find a new maintainer with the following properties: - Some basic knowledge in C - Some basic knowledge in software engineering and interfaces between kernel and userland - Some basic knowledge in CD/DVD writing - Some basic knowledge in SCSI - Some basic knowledge in software quality assurance - Able and willing to cooperate 2) Update to a recent cdrtools source, do not hide interesting new features from Debian users and (this may be even more important to Linux users) workarounds for recent Linux kernel self-incompatibilities. 3) Remove the unneeded Debian changes as the unmodified original source does not need any changes in order to work correctly. 4) If someone at Debian likes to work on enhancements, make sure that these changes are done in a way that does not contradict the current planned behavior and make sure that the quality of the code is sufficient to allow integreation. Read the file: ftp://ftp.berlios.de/pub/cdrecord/CONTRIBUTING and follow the instructions in that file. 5) Find someone to read the original GPL text in depth who did not yet read the wrong FSF GPL FAQ. Let this person be prepared and willing to have a serious fact based discussion in case that there are still any issues to discuss. 6) Find someone to read the original CDDL text in depth and in addition read the DFSG text. Let this person be prepared and willing to have a serious fact based discussion in case that there are still problems to understand why the CDDL meets all requirements of the DFSG. Do not try to raise conditions that are not written down in the DFSG. Be prepared to have a serious discussion with people from Sun who are waiting for such a discussion and are willing to explain how the CDDL has to be understood. Try to accept that the CDDL is a first class OS license and treat it in the same open way as you treat the GPL and the BSDl. 7) Finally: learn that I am spending a lot time on cdrtools and on my other OSS activities. Understand that I am neither willing to waste my time with useless discussions with Debian people nor being forced to give up useful ways of defending me against malicious users or distributors of my code. Believe me that it does not sound serious when reading again and again silly things like we need to fork cdrecord I am now working for 10 years on cdrecord, I am now working for exactly 20 years on libscg and I am working for 24 years on star. Many people did claim to start a fork on my tools, nobody did yet even come to a serious first step in this direction not speaking about serious work on extensions... 8) Understand that all my software is highly portable and that it is not acceptable to chage it in a way that make them behave different on different platforms. 9) Help me with defending against silly artificial limitations in the Linux kernel that makes life on Linux hard. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Status of inetd for etch
This post is about some issues with the various inetd packages in etch (and unstable). This is a case where I think some coordination between all the packages or some inetd package policy would make them all generally more usable. The currently available inetd packages, and a summary of their state: +-+- Package | IPv6 support| Source quality / comments +-+- inetutils-inetd | tcp = tcp4 and tcp6 | OK, but upstream quiet | | micro-inetd | Partial | Not a proper inetd replacement | | netkit-inetd| No, and it will be | Terrible. It won't even build | difficult to add| from the .orig.tar.gz, and the | | tarball is a mess. IMO, should be | | removed from Debian. | | 102 outstanding bugs. | | openbsd-inetd | tcp=TCP4, tcp4, | OK. Bug in reload (#382404). | tcp6, tcp46 | Bug in restart (#376716). | | | | rlinetd | Yes | Not a drop-in replacement. | | superd | No | Unmaintained. Candidate for | | removal? | | xinetd | tcp4, tcp6 | Good, but not currently a drop-in | | inetd replacement (but could be | | configured to do so). +-+- Outstanding issues -- * There is no inetd virtual package, so multiple daemons may be installed, all using the same configuration file. Is this a use case we really want to support? Are there really setups running multiple inetds for a good reason? Having a virtual internet-super-server package or similar with appropriate dependencies would make them rather more interchangeable, as for e.g. mail-transport-agent. * There is no common init script name. Same problems as above. * netbase only depends on two inetd packages (openbsd-inetd and netkit-inetd; a virtual depends plus a default would be nicer. * netkit-inetd - No upstream. - Last maintainer upload was 22 months ago. The last three uploads were NMUs. - It doesn't build from the original source. - The original source is a horrible mess, with code duplication (the source tree has a duplicate copy embedded within itself), and i386 ELF object code and binaries code in the tree. - The C source itself is not very nice. - Is this really fit to keep in Debian? It might be better to remove it entirely given its terrible state. * openbsd-inetd is the only drop-in replacement at this time - The other packages have different init script names or need some work on the package dependencies (e.g. inetutils-inetd). xinetd is in the same situation, but also needs some work on update-inetd before it will be suitable as a replacement. * IPv6 transition - Should individual packages be made to listen on both tcp4 and tcp6 sockets, or should this be done by the inetd itself, or even update-inetd? - Some inetds automatically listen on v6, whereas others need it explicitly enabling. What should tcp vs tcp4 vs tcp6 (and the same for udp) imply? - Some general policy would be useful here to make the behaviour consistent and to make IPv6 support as painless as possible for users. * Upgrade from sarge and earlier The inetd daemon installed by default: etch: openbsd-inetd | netkit-inetd sarge: netkit-inetd woody: netkit-inetd (netkit-base, split from netbase) potato: (in netbase) slink: (in netbase) Users upgrading from woody or sarge to etch will not be switched to openbsd-inetd, whereas new installs will use it by default. Removing netkit-inetd from the netbase depends should permit this, but a complete removal would perhaps be the best option. While it's probably too late to fix up update-inetd and all the inetd integration issues for etch, fixing the netbase dependency and eliminating netkit-inetd is doable. Any thoughts or comments? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. pgpz6IH7fTgCn.pgp Description: PGP signature
Re: cdrtools
Hi fellow Debian people, On Thu, Aug 10, 2006 at 11:25:11PM +0200, Joerg Schilling wrote: Let me make a proposal that makes sense for now and the future: Whoever answers to this proposal will be mocked publically. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.2237 +0100]: No point setting oneself up for bugs if it is not necessary. The script wouldn't determine anything, it would simply append paths to the package's list of paths. The Maintainer would need to call the script right after file generation succeeds, or perhaps with a list of files just generated, or as part of an install if packageless files are known to exist. Ah, now I understand. Yeah, sounds like a good idea. After all, a file may or may not be created, something not known during build time... So when can we expect patches from you? ;) -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system do micro$oft's total cost of operation calculations include total cost of downtime? signature.asc Description: Digital signature (GPG/PGP)
Use of generic init script names [WAS Re: Status of inetd for etch]
On Thu, Aug 10, 2006 at 10:56:01PM +0100, Roger Leigh wrote: Outstanding issues -- * There is no inetd virtual package, so multiple daemons may be installed, all using the same configuration file. Is this a use case we really want to support? Are there really setups running multiple inetds for a good reason? Having a virtual internet-super-server package or similar with appropriate dependencies would make them rather more interchangeable, as for e.g. mail-transport-agent. * There is no common init script name. Same problems as above. So, this got me thinking about other packages which provide a common service but don't use common script names. Take imap, for instance. Looking at cyrus21-imapd (init script provided by cyrus21-common), courier-imap and dovecot-imapd (init script provided by dovecot-common) it appears that they all provide imap-server and conflict with imap server. This makes sense. However, the cyrus init script is called /etc/init.d/cyrus21, the courier init script is /etc/init.d/courier-imap and the dovecot init script is /etc/init.d/dovecot. It would seem to me that if these packages are going to claim to provide some sort of common server (imap-server in this case), that the ability and method to start and stop the service should be part of the commonality. All of those packages should really provide an init script by the same name (as they all conflict with each other anyways). The same should probably go for pop3d, httpd, inetd and so on. Regards, -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: Digital signature
Re: Status of inetd for etch
On Aug 10, Roger Leigh [EMAIL PROTECTED] wrote: * There is no inetd virtual package, so multiple daemons may be There is no virtual package because aj (who is still the netbase maintainer, even if he did not touch it in almost five years) mandated that it should be introduced after the mitical rewriting of update-inetd. IIRC three people (myself being the first of them) started rewriting update-inetd, but nobody ever managed to finish. A few more volunteered and then disappeared. installed, all using the same configuration file. Is this a use case we really want to support? Are there really setups running multiple inetds for a good reason? Having a virtual A good reason usually is using features not available in a single package (especially inetd vs. inetd). It's not hard to manage anyway, my scheme allowed this. * netkit-inetd I agree that it should be removed from the distribution, or at least replaced by openbsd-inetd as the default inetd. * openbsd-inetd is the only drop-in replacement at this time This is why I packaged it. :-) BTW, openbsd-inetd also has the feature of not being started if inetd.conf is empty. - The other packages have different init script names or need some work on the package dependencies (e.g. inetutils-inetd). xinetd is in the same situation, but also needs some work on update-inetd before it will be suitable as a replacement. ITYM lots of work. * IPv6 transition - Should individual packages be made to listen on both tcp4 and tcp6 sockets, or should this be done by the inetd itself, or even update-inetd? Only individual packages know if they support IPv6. - Some inetds automatically listen on v6, whereas others need it I call them broken. I believe that administrators do not expect that services are exposed to IPv6 connections unless they are configured this way in inetd.conf. Users upgrading from woody or sarge to etch will not be switched to openbsd-inetd, whereas new installs will use it by default. Did you actually test this? -- ciao, Marco signature.asc Description: Digital signature
Re: Silly Packaging Problem
sean finney wrote: On Thu, Aug 10, 2006 at 11:01:30AM +0100, martin f krafft wrote: No, at least not for /etc. You could install the file, the overwrite it, but files installed to /etc by dpkg are conffiles and those must not be touched programmatically, according to policy. i think a better solution (and one that has been proposed in the past) would be to have a way of providing dpkg with information about such dynamically created files. this would also be helpful for stuff like logfiles. a fairly straightforward (says he who has not looked at dpkg's source) would be to provide a new file in the control section of the deb which contained a series of globs which could be used to match such files. then, if a query through dpkg -S fails to find an owner of a file it could go through the potentially longer process of searching through these files, reporting all matches. sean The idea of a glob makes me nervous. There's been plenty of times I've accidentaly gotten extra files listed in a glob to ls or find that I didn't intend to. Michael Peek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
Bruce Sass wrote: An update-package command, run at install time by the maintainer's scripts right after file generation succeeds, would head off potential problems with synchronization that are outside of the Maintainer's control (e.g., DEBIAN/dynfiles containing incorrectly generated paths) and would be simpler to implement, specifically, dynfiles vs. update-package: Having recently come from a Solaris background (migraiting to Debian), if I understand what you're saying here, then this is the way Sun handled the problem. In their version of debian/postinst you would call a command and pass it the path of the file you just created, along with any extra necessary information needed to add an entry to the packaging database. As an example: echo Creating /etc/foo.cfg... cat /etc/foo.cfg EOF ...stuff... EOF dpkg-install-file package-name /etc/foo.cfg After that, when doing the Sun version of a purge, you had a choice: A) Remove the file yourself, and call a second command that would remove it's database entry, or B) Ignore it and let the package manager remove both the file and it's database entry for you, since it now knows of the file's existence and it's affiliation with your package. Having this background writing Solaris packages, and a desire to 'do it right' as I learn Debian, is what prompted me to ask in the first place. It just seems a little cleaner: you could query dpkg for what package *every* file came from -- no files left out; and you don't necessarily have to rely on the package maintainer to remember to clean up after themselves during a purge, so long as they registered their dynamically-created files right after creation. Anyway, that answered my question -- Debian doesn't worry about dynamically-created files. L8r, Michael Peek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Status of inetd for etch
On Thu, Aug 10, 2006 at 10:56:01PM +0100, Roger Leigh wrote: The inetd daemon installed by default: etch: openbsd-inetd | netkit-inetd sarge: netkit-inetd woody: netkit-inetd (netkit-base, split from netbase) potato: (in netbase) slink: (in netbase) Users upgrading from woody or sarge to etch will not be switched to openbsd-inetd, whereas new installs will use it by default. Why, for the love of Cthulhu, does netbase depend on inetd in the first place? Let's see: netbase: critical network configuration. It has some ancient cruft like /etc/services (which does more ill than good), but /etc/init.d/networking is not something one wants to skip. inetd: a way to set up ad-hoc network servers. Now, let's see what depends on *-inetd: Depends: lukemftpd wipl-client-java pawserv netbase bitlbee micro-httpd wipl-client-inetd ltsp-server noffle Recommends: atftpd Suggests: micro-proxy education-main-server Throw in a few packages which can optionally use inetd but don't specify the dependency. It would be good to get rid of inetd from the basic install at all. Those who need it can simply, well, install it -- and packages can use Depends: on flavour-inetd just like the rest of facilities in Debian. As an added bonus, you don't have to bother with drop-in replacements as whatever depends on an inetd can list the flavours it can use as alternatives in its Depends: line. As it stands today, I currently use equivs on all of my boxes. This can potentially break dependencies if I install something that happens to actually need inetd. Cheers and schtuff, -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Silly Packaging Problem
On Thu, Aug 10, 2006 at 06:35:03PM -0400, peek wrote: place. It just seems a little cleaner: you could query dpkg for what package *every* file came from -- no files left out; and you don't what about rotated log files? pid files? lock files? misc stuff in /var/cache? that's not to bash the suggestion of a dpkg-install-file. in fact i think it would be a great addition. better than what i suggested for the specific problem of dynamically created config files, anyway. On Thu, Aug 10, 2006 at 06:34:35PM -0400, peek wrote: The idea of a glob makes me nervous. There's been plenty of times I've accidentaly gotten extra files listed in a glob to ls or find that I didn't intend to. the proposal as i framed it would do nothing dangerous with the globs. certainly there would be no passing of said globs to an rm -rf; they were only to serve as informational to an admin asking where the heck did this file come from? sean signature.asc Description: Digital signature
Re: Status of inetd for etch
On Fri, Aug 11, 2006 at 12:29:48AM +0200, Marco d'Itri wrote: On Aug 10, Roger Leigh [EMAIL PROTECTED] wrote: - Some inetds automatically listen on v6, whereas others need it I call them broken. I believe that administrators do not expect that services are exposed to IPv6 connections unless they are configured this way in inetd.conf. A service can listen: +on a specific address In this case, it won't be exposed to IPv6 anyway. +on all addresses Here, it SHOULD accept IPv6 without any explicit configuration. Otherwise, you'll force the admin to look up the way to enable it, something that invariably will be done differently for every single service. And I can assure you that 99.9% folks won't bother. As a result, we won't have IPv6. Not good. All addresses means all addresses, be they IPv4 or IPv6 in my book. At least, the usual services like apache, apache2, sshd or exim4 work this way. Bind9 doesn't, and I'm filing a wishlist on it. Cheers and schtuff, -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
Florian Weimer wrote:
* martin f. krafft:
Thanks to the work of our DPL Anthony aj Towns (and all the other
people who have worked on this without my knowledge), I am happy to
announce that dak, our archive management software, finally supports
the use of the tilde ('~') in version numbers.
Should we really start using this feature even though it violates
section 5.6.12 of the Policy?
It's great to see '~' support finally coming to dak, if only the
announcement happened a few months earlier I would have used it in one
of my packages initially. It was a 0.1 prerelease (being pretty stable
though), so I called it 0.09+0.1.svn.
Reading this announcement I thought, great and wanted to start using
'~', only to discover that dpkg believes that 0.09+0.1.svn 0.1~svn.
I have to admit that when choosing 0.09+0.1 as version number I didn't
check with dpkg --compare-versions because then I would have discovered
that dpkg --compare-versions '0.09' '=' '0.9' yields true, which I
think is rather odd, because it means that now all version numbers up to
0.9 will be considered 0.09+0.1.
So, what should I do now:
1.) Wait for a 0.10 release. I think my users wouldn't be happy ;-)
2.) Use an epoch.
3.) File a bug report against dpkg.
If it's not a bug in dpkg, could someone please elaborate on the
reasoning of this behaviour. I'd be grateful for any comments and replies.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
* Michael Biebl [Fri, 11 Aug 2006 01:12:59 +0200]: that dpkg --compare-versions '0.09' '=' '0.9' yields true, which I think is rather odd, because it means that now all version numbers up to 0.9 will be considered 0.09+0.1. 0.09 = 0.9 means: 0 == 0 and . == . and 09 == 9 Which is pretty standard math. ;-) If it's not a bug in dpkg, could someone please elaborate on the reasoning of this behaviour. I'd be grateful for any comments and replies. Well, don't know about the reasoning, but it's definitely not a dpkg bug, since it follows the comparison algorithm as described in Policy 5.6.12. The bottom line is: whenver dealing with version, never ever say X is obviously greater than Y, and always run dpkg --compare-versions in advance. 2.) Use an epoch. 1:0.1 is obviously (heh) 0.09. On other news, 1E0.1 is _also_ 0.9, but 1.0. (Yes, this is called abuse.) Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org One of my most productive days was throwing away 1000 lines of code. -- Ken Thompson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Status of inetd for etch
On Aug 11, Adam Borowski [EMAIL PROTECTED] wrote: I call them broken. I believe that administrators do not expect that services are exposed to IPv6 connections unless they are configured this way in inetd.conf. A service can listen: Does not matter. The behaviour of inetd has always required to explicitly enable tcp, and changing it would be bad. Why, for the love of Cthulhu, does netbase depend on inetd in the first place? Let's see: Historical reasons. netbase: critical network configuration. It has some ancient cruft like /etc/services (which does more ill than good), but /etc/init.d/networking is not something one wants to skip. Actually /etc/init.d/networking should be moved to the ifupdown package. Now, let's see what depends on *-inetd: Under the current rules these packages are buggy, unless they have a *specific* reason to depend on a specific inetd. It would be good to get rid of inetd from the basic install at all. Those No, it would not. UNIX systems are supposed to have an inetd installed. -- ciao, Marco signature.asc Description: Digital signature
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Fri, 11 Aug 2006 01:12:59 +0200, Michael Biebl [EMAIL PROTECTED] said: [...] If it's not a bug in dpkg, could someone please elaborate on the reasoning of this behaviour. I'd be grateful for any comments and replies. It's documented in Policy 5.6.12 [1]. Substrings composed of digits are compared numerically, and so 09 == 9. (This is done to ensure that 10 9, for example.) [1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version So I guess your only real option is to use an epoch. -- Hubert Chan - email Jabber: [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA (Key available at wwwkeys.pgp.net) Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Fri, Aug 11, 2006 at 01:29:40AM +0200, Adeodato Simó wrote: * Michael Biebl [Fri, 11 Aug 2006 01:12:59 +0200]: that dpkg --compare-versions '0.09' '=' '0.9' yields true, which I think is rather odd, because it means that now all version numbers up to 0.9 will be considered 0.09+0.1. 0.09 = 0.9 means: 0 == 0 and . == . and 09 == 9 Which is pretty standard math. ;-) Except that the final comparison ignores that the number was to the right of the decimal, making the zero significant. I think you will be hard pressed to find a mathematician who supports dropping significant zeros for no good reason. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: Digital signature
Re: Status of inetd for etch
On Fri, Aug 11, 2006 at 01:34:39AM +0200, Marco d'Itri wrote: On Aug 11, Adam Borowski [EMAIL PROTECTED] wrote: Why, for the love of Cthulhu, does netbase depend on inetd in the first place? Let's see: Historical reasons. Now, let's see what depends on *-inetd: Under the current rules these packages are buggy, unless they have a *specific* reason to depend on a specific inetd. Right, that's why a generic inetd virtual package would be a good idea. It would be good to get rid of inetd from the basic install at all. Those No, it would not. UNIX systems are supposed to have an inetd installed. Just like they used to be supposed to have telnetd or csh. But even if it is left as priority:standard, it obviously shouldn't be depended on by netbase. I don't have portmap installed anywhere either -- but it at least can be easily ripped away, even though nfs deserves to be on an Unix system a lot more than inetd does. -- 1KB // Microsoft corollary to Hanlon's razor: // Never attribute to stupidity what can be // adequately explained by malice. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Fri, Aug 11, 2006 at 01:12:59AM +0200, Michael Biebl wrote: I have to admit that when choosing 0.09+0.1 as version number I didn't check with dpkg --compare-versions because then I would have discovered that dpkg --compare-versions '0.09' '=' '0.9' yields true, which I think is rather odd, because it means that now all version numbers up to 0.9 will be considered 0.09+0.1. So, what should I do now: 1.) Wait for a 0.10 release. I think my users wouldn't be happy ;-) 2.) Use an epoch. 3.) File a bug report against dpkg. If it's not a bug in dpkg, could someone please elaborate on the reasoning of this behaviour. I'd be grateful for any comments and replies. Oooh, oooh! I know the answer to this! fx: waves hand in the air, squirms in seat Having recently written a program to do quite detailed things with package version numbers, I've gotten intimately familiar with Policy s5.6.12. Specifically, 09 == 9 because The numerical values of these two parts are compared (3rd last paragraph), so leading zeroes are effectively stripped before comparison. I don't think it's a bug in dpkg or policy, realistically speaking -- the old practice of 0.01 versioning is pretty weird in general (periods are cheap, just make it 0.0.1 instead), and numeric sorting is much better in the general case (would you want 9 gt 10 == true?) but it just happens to have bitten you here. I think you're up for an epoch. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
On Wed, 09 Aug 2006 15:44:57 +0200 Joerg Schilling [EMAIL PROTECTED] wrote: Stuff deleted for brevity All of this, without even taking into account your brain-dead licensing mix between CDDL and GPL - which are intentionally incompatible licenses, according to Sun guys. If you are so braindead not to understand that this license combination is perfectly OK, I cannot help you. It seems that I did waste already too much time with you. A discussion only makes sense in case that the other side is able/willing to understand simple explanataions... I have just spent the last half hour reading this thread and nowhere have I seen you give ANY explanations, simple or complex. You have simply stood on your hind legs and declared that you are right and everyone in the Debian group is wrong and evil in their intent or just plain stupid. So, can you actuall construct an explanation that does not include all the inflamitory statements you have assigned to your opponents here at Debian? I have been with the Debian group since very early in the project (when I joined there were about 75 of us) and while I have not agreed with every decission this group has made over the years. I DO agree that the decissions have been made in a thoughtful and deliberate manner that supports the DFSG and our goals for Software Freedom. Other proponents of Software Freedom don't always agree with us, or us with them. For me that is part and parcel of the concept of Freedom in a diverse society. If you are going to debate, it is more useful for you to provide clear points of view about the concepts being discussed. All I have seen is juvenile name calling and useless bile. Please grow up! Luck, Dwarf Sometimes known as the voice of reason ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
* Roberto C. Sanchez [Thu, 10 Aug 2006 19:47:36 -0400]: Except that the final comparison ignores that the number was to the right of the decimal, making the zero significant. Er, read Policy 5.6.12. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Old men are fond of giving good advice to console themselves for their inability to set a bad example. -- La Rochefoucauld, Maxims -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cdrtools
This one time, at band camp, Michael Banck said: Hi fellow Debian people, On Thu, Aug 10, 2006 at 11:25:11PM +0200, Joerg Schilling wrote: Let me make a proposal that makes sense for now and the future: Whoever answers to this proposal will be mocked publically. Even if we mock the proposal? You're no fun at all. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
Re: dpkg doing wrong math (0.09 = 0.9) ?-
Michael Biebl [EMAIL PROTECTED] writes: I have to admit that when choosing 0.09+0.1 as version number I didn't check with dpkg --compare-versions because then I would have discovered that dpkg --compare-versions '0.09' '=' '0.9' yields true, which I think is rather odd, because it means that now all version numbers up to 0.9 will be considered 0.09+0.1. Which is correct. Version strings can consist of (among other things) any number of '.'-separated integers in sequence. Leading zeros on the individual integers are not significant. The full description of how values of the Version field are compared is in Policy: 5.6.12 Version [...] The strings are compared from left to right. First the initial part of each string consisting entirely of non-digit characters is determined. These two parts (one of which may be empty) are compared lexically. If a difference is found it is returned. The lexical comparison is a comparison of ASCII values modified so that all the letters sort earlier than all the non-letters. Then the initial part of the remainder of each string which consists entirely of digit characters is determined. The numerical values of these two parts are compared, and any difference found is returned as the result of the comparison. For these purposes an empty string (which can only occur at the end of one or both version strings being compared) counts as zero. These two steps (comparing and removing initial non-digit strings and initial digit strings) are repeated until a difference is found or both strings are exhausted. URL:http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version -- \ I love to go down to the schoolyard and watch all the little | `\ children jump up and down and run around yelling and screaming. | _o__) They don't know I'm only using blanks. -- Emo Philips | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Fri, Aug 11, 2006 at 02:21:04AM +0200, Adeodato Simó wrote: * Roberto C. Sanchez [Thu, 10 Aug 2006 19:47:36 -0400]: Except that the final comparison ignores that the number was to the right of the decimal, making the zero significant. Er, read Policy 5.6.12. I have read it. I was simply speaking from a mathematical perspective. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: Digital signature
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Thu, Aug 10, 2006 at 07:47:36PM -0400, Roberto C. Sanchez wrote: On Fri, Aug 11, 2006 at 01:29:40AM +0200, Adeodato Simó wrote: * Michael Biebl [Fri, 11 Aug 2006 01:12:59 +0200]: that dpkg --compare-versions '0.09' '=' '0.9' yields true, which I think is rather odd, because it means that now all version numbers up to 0.9 will be considered 0.09+0.1. 0.09 = 0.9 means: 0 == 0 and . == . and 09 == 9 Which is pretty standard math. ;-) Except that the final comparison ignores that the number was to the right of the decimal, making the zero significant. I think you will be hard pressed to find a mathematician who supports dropping significant zeros for no good reason. I'd imagine you'd be hard pressed to find a mathematician who knows what to do with a number that reads 0.0.9, either. That's why we're software developers, not mathematicians. Or, to put it another way: your numbers are not our numbers. grin - Matt
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Thu, Aug 10, 2006 at 08:37:47PM -0400, Roberto C. Sanchez wrote: On Fri, Aug 11, 2006 at 02:21:04AM +0200, Adeodato Simó wrote: * Roberto C. Sanchez [Thu, 10 Aug 2006 19:47:36 -0400]: Except that the final comparison ignores that the number was to the right of the decimal, making the zero significant. Er, read Policy 5.6.12. I have read it. I was simply speaking from a mathematical perspective. But a mathematical perspective is wrong, because it does not tell how to interpret 1.1.1 Version numbers are not floats. -- Rodrigo Gallardo GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28 signature.asc Description: Digital signature
Re: Silly Packaging Problem
On Thu August 10 2006 16:20, martin f krafft wrote: also sprach Bruce Sass [EMAIL PROTECTED] [2006.08.10.2237 +0100]: No point setting oneself up for bugs if it is not necessary. The script wouldn't determine anything, it would simply append paths to the package's list of paths. The Maintainer would need to call the script right after file generation succeeds, or perhaps with a list of files just generated, or as part of an install if packageless files are known to exist. Ah, now I understand. Yeah, sounds like a good idea. After all, a file may or may not be created, something not known during build time... So when can we expect patches from you? ;) punt Seems like the kind of thing which should be done by a DD or [EMAIL PROTECTED] (especially since it relies on dpkg's behaviour and mucks with their DB). /punt I will be so bold as to suggest... Synopsis: update-package [options] command package update-package [options] --add-files=paths package update-package [options] --remove-files=paths package update-package [options] --size=absolute | [+|-]increment package update-package [options] --field=label::new-value package Commands: --*-files modifies the indicated package's list of files --size changes or modifies a package's Installed-Size: field --field changes the value of an arbitrary field in a package's DB entry files and size accommodate the desire to include generated or packageless files and their size (if knowable) in the dpkg DB. field can be used by an admin to override a package's meta-information so it better reflects local changes in those cases where building a new package is overkill. e.g.: a local Maintainer: for a pkg with config changes only, new Depends: and/or no need for an equivs package to hack around a temporary problem or situation. Potentially a very nasty command. [what can I say, it is not that unusual for me to editor /var/lib/dpkg/status to work around a packaging problem, or dpkg/info/package.list then dpkg-repack and install somewhere else... but maybe I'm evil or enshrining the ability in a utility would send the wrong message... perhaps another reason for a DD or [EMAIL PROTECTED] to provide the functionality shrug] Options: - the usual useful stuff (help, version, verbosity, logging) - maybe an admin controlled off switch, just in case having a local DB which differs from the packaged one is a problem (implies a config file somewhere) - automatic Installed-Size: updating, not always useful or accurate, maybe best left as a invocation only option because only the Maintainer knows for sure Files: /sbin/update-package /usr/share/man/man8/update-package /etc/update-package and/or $HOME/.update-package ..., write some more if necessary to clarify something, and be an early adopter/test-dummy though. :-) - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Fri, Aug 11, 2006 at 10:42:53AM +1000, Matthew Palmer wrote: I'd imagine you'd be hard pressed to find a mathematician who knows what to do with a number that reads 0.0.9, either. That's why we're software developers, not mathematicians. Or, to put it another way: your numbers are not our numbers. grin I never said I was a mathematician :-) The original comparison, though, was 0.09 and 0.9. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto signature.asc Description: Digital signature
Desktop themes for Debian ?
Hi people, I'm a devel on Art Team in Debian-BR-CDD [1] project in Brazil and maintainer of some icon packages in Debian. The Debian-BR-CDD is a cdd focused in desktop applications for brazilians users in Portuguese, with some themes customized for GNOME, GDM, Splashy, Grub, Icons, website. Any screenshots are here[2]. I think that the etch version must have standardized themes in the KDE and GNOME. I want to know about this work in the Debian. How the graphic art is organized? Are teams? How can I help this team? Thanks a lot! Links: [1] - http://cdd.debian-br.org [2] - http://cdd.debian-br.org/project/wiki/Screenshots -- Andre Luiz Rodrigues Ferreira (si0ux) [EMAIL PROTECTED] *** Orlandia - SP - Brazil Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dpkg doing wrong math (0.09 = 0.9) ?- [was: dak now supports ~ in version numbers]
On Thu, Aug 10, 2006 at 08:47:14PM -0400, Roberto C. Sanchez wrote: On Fri, Aug 11, 2006 at 10:42:53AM +1000, Matthew Palmer wrote: I'd imagine you'd be hard pressed to find a mathematician who knows what to do with a number that reads 0.0.9, either. That's why we're software developers, not mathematicians. Or, to put it another way: your numbers are not our numbers. grin I never said I was a mathematician :-) The royal 'your', though. The original comparison, though, was 0.09 and 0.9. We're out to break *all* the rules. If we need to make up a new evaluation algorithm to be able to handle 0.0.1, we may as well include handling zero-padding differently as well. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dak now supports ~ in version numbers
Adeodato == Adeodato Simó [EMAIL PROTECTED] writes: Adeodato Package: foo-plugin Depends: foo (= 0.8), foo ( Adeodato 0.9) Adeodato Will probably want to move to: Adeodato Depends: foo (= 0.8), foo ( 0.9~) Can I assume that the first one will accept version 0.9~rc1, but the second one wont? Or I have that wrong? -- Brian May [EMAIL PROTECTED]
Re: piuparts unprocessed failed logs page
Lars == Lars Wirzenius [EMAIL PROTECTED] writes: Lars While I wait to have time to do something better and more Lars easily usable, the following page lists the logs of failed Lars piuparts files that have not yet been processed: Lars http://piuparts.cs.helsinki.fi/fail/ http://piuparts.cs.helsinki.fi/fail/heimdal-kdc_0.7.2.dfsg.1-3.log: ... Setting up krb5-config (1.10) ... dnsdomainname: Unknown host ... Setting up heimdal-kdc (0.7.2.dfsg.1-3) ... hostname: Unknown host kstash: writing key to `/var/lib/heimdal-kdc/m-key' kstash: writing master key file: unable to find realm of host piatti dpkg: error processing heimdal-kdc (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: heimdal-kdc E: Sub-process /usr/bin/dpkg returned an error code (1) ... Can the argument be made that these aren't packaging bugs but rather the fact the hostname hasn't been configured correctly? Or... Is it expected Debian packages should be able to cope regardless? In the case of heimdal-kdc, it makes no sense to install heimdal-kdc without the realm, and if the realm cannot be guessed by looking up the hostname domain, and if it cannot be found by debconf question, it makes no sense to continue. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: udev vs ldap at startup
Steve == Steve Langasek [EMAIL PROTECTED] writes: Steve libnss-ldap has a new, retarded upstream default where it Steve polls the server several times in the case of a connection Steve refused error instead of just returning a notfound to the Steve caller. Ar So that probably would explain why I can no longer log in as root when the NSS LDAP server is down, even with LDAP PAM support disabled and files is listed before ldap in /etc/nsswitch.conf. ethereal shows the following queries when it is working: Lightweight Directory Access Protocol LDAP Message, Search Request Message Id: 5 Message Type: Search Request (0x03) Message Length: 96 Base DN: dc=microcomaustralia,dc=com,dc=au Scope: Subtree (0x02) Dereference: Never (0x00) Size Limit: 1 Time Limit: 0 Attributes Only: False Filter: ((objectClass=posixAccount)(uid=root)) LDAP Message, Search Result Message Id: 5 Message Type: Search Result (0x05) Message Length: 7 Response To: 1 Time: 0.000346000 seconds Result Code: success (0x00) Matched DN: (null) Error Message: (null) LDAP Message, Search Request Message Id: 6 Message Type: Search Request (0x03) Message Length: 111 Base DN: dc=microcomaustralia,dc=com,dc=au Scope: Subtree (0x02) Dereference: Never (0x00) Size Limit: 0 Time Limit: 0 Attributes Only: False Filter: ((objectClass=posixGroup)(memberUid=root)) Attribute: gidNumber LDAP Controls LDAP Control Control OID: 1.2.840.113556.1.4.319 Control Value: 3006020203E80400 LDAP Message, Search Result Message Id: 6 Message Type: Search Result (0x05) Message Length: 7 Response To: 4 Time: 0.000415000 seconds Result Code: success (0x00) Matched DN: (null) Error Message: (null) LDAP Controls LDAP Control Control OID: 1.2.840.113556.1.4.319 Control Value: 30050201000400 The second query is trying to find out all the groups root is in (is it possible to skip this???). I don't understand the first one. root is defined in /etc/passwd. getent passwd with the LDAP server down lists all local users (including root) before hanging. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#382451: ITP: varnish -- High-performance HTTP accelerator
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen [EMAIL PROTECTED] * Package name: varnish Version : 0.9 Upstream Author : Varnish Project [EMAIL PROTECTED] * URL : http://varnish.projects.linpro.no/ * License : Two-clause BSD license Description : High-performance HTTP accelerator Varnish is a HTTP accelerator, also called reverse proxy, that stores (caches) documents that have been requested over the HTTP protocol. Vanish is targeted primarily at the FreeBSD 6 and Linux 2.6 platforms, and will take full advantage of the advanced I/O features offered by these operating systems. -- System Information: Debian Release: 3.1 Architecture: i386 (x86_64) Kernel: Linux 2.6.12-11-amd64-k8 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted snort 2.3.3-8 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 00:44:36 +0200 Source: snort Binary: snort-mysql snort-doc snort-rules-default snort-common snort-pgsql snort Architecture: source i386 all Version: 2.3.3-8 Distribution: unstable Urgency: medium Maintainer: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Changed-By: Javier Fernandez-Sanguino Pen~a [EMAIL PROTECTED] Description: snort - Flexible Network Intrusion Detection System snort-common - Flexible Network Intrusion Detection System [common files] snort-doc - Documentation for the Snort IDS [documentation] snort-mysql - Flexible Network Intrusion Detection System [MySQL] snort-pgsql - Flexible Network Intrusion Detection System [PostgreSQL] snort-rules-default - Flexible Network Intrusion Detection System ruleset Closes: 381726 Changes: snort (2.3.3-8) unstable; urgency=medium . * Fix security issue CVE-2006-2769, potential evasion in URI content buffers. This evasion only applies to Apache protected servers since that server supports some characters. The patch used is from 2.4.5 and is *not* the one provided by Demarc (which is not fully comprehensive and is much more intrusive). Since this is an evasion issue and not a real security issue thus the 'medium' urgency even though it fixes security bug (Closes: #381726) . From upstream (snort.org webpage, News item Possible Evasion in http_inspect): . «The Apache web server supports special characters in HTTP requests that do not affect the processing of the particular request. The current target-based profiles for Apache in the http_inspect preprocessor do not properly handle these requests, resulting in the possibility that an attacker can bypass detection of rules that use the uricontent keyword by embedding special characters in a HTTP request.» . «It is important to note that this is an evasion and not a vulnerability. This means that while it is possible for an attacker to bypass detection, Snort sensors and the networks they protect are not at a heightened risk of other attacks.» . * Backport fix of another (different) potential evasion in Stream4 (also in the Snort 2.4.5 release, no CVE name) * Relocate Czech translation, it was not under debian/po * Add a warning in /etc/default/snort that the SNORT_USER will be modified (with usermod) every time you reinstall the package (don't change it to 'root'!) Files: 5815a2ce3d8dc39fec057394fce1081e 961 net optional snort_2.3.3-8.dsc 6cfe673ee3abbdf96d5003fec30527a4 350526 net optional snort_2.3.3-8.diff.gz 24ee623d75c35c83514efe797997c759 94450 net optional snort-common_2.3.3-8_all.deb 27f0b6579372d7aefc8889ee69f12fac 1800212 doc optional snort-doc_2.3.3-8_all.deb 932993d0f895485512c1f976ff6ae402 233212 net optional snort-rules-default_2.3.3-8_all.deb db30e71458afba97b1c363675b4a98c0 358890 net optional snort_2.3.3-8_i386.deb 705fd479250a20cc875f60ca83be25c5 365824 net extra snort-mysql_2.3.3-8_i386.deb e14329f507a72b07708c4144368f0609 365098 net optional snort-pgsql_2.3.3-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iQCVAwUBRNp1jPtEPvakNq0lAQJ6ygQAqohT7fCplPjPJBRZG2TYDTEuHaALknvC bPikj1gUa+1Wy8QQeApJLpUqIMDIriTM9CA0+5OXc7npl59EymjhfwtKl2PpP0aP W93GRhw7bQc9GkEXMD/9AWTBO57qNE3lvKJhOUCby9SE2x9MYTgZtJGWReFT8MfF 8QpKZA8jQH8= =rpyL -END PGP SIGNATURE- Accepted: snort-common_2.3.3-8_all.deb to pool/main/s/snort/snort-common_2.3.3-8_all.deb snort-doc_2.3.3-8_all.deb to pool/main/s/snort/snort-doc_2.3.3-8_all.deb snort-mysql_2.3.3-8_i386.deb to pool/main/s/snort/snort-mysql_2.3.3-8_i386.deb snort-pgsql_2.3.3-8_i386.deb to pool/main/s/snort/snort-pgsql_2.3.3-8_i386.deb snort-rules-default_2.3.3-8_all.deb to pool/main/s/snort/snort-rules-default_2.3.3-8_all.deb snort_2.3.3-8.diff.gz to pool/main/s/snort/snort_2.3.3-8.diff.gz snort_2.3.3-8.dsc to pool/main/s/snort/snort_2.3.3-8.dsc snort_2.3.3-8_i386.deb to pool/main/s/snort/snort_2.3.3-8_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted klic 3.003-gm1-4 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 09:18:23 +0900 Source: klic Binary: klic klic-doc Architecture: source i386 all Version: 3.003-gm1-4 Distribution: unstable Urgency: low Maintainer: GOTO Masanori [EMAIL PROTECTED] Changed-By: GOTO Masanori [EMAIL PROTECTED] Description: klic - KL1 to C compiler system klic-doc - Documentation and sample KL1 files for the KLIC Closes: 382094 Changes: klic (3.003-gm1-4) unstable; urgency=low . * patch4.configure-sh-space: Fix the last extra space before $c, that prevented from compiling with either dash or bash. (Closes: #382094) * debian/configure.expect: Revert the last change. Files: 274e2011c009190beba74a47f1d3f61b 608 devel optional klic_3.003-gm1-4.dsc 4196a51d96b1e5e0cb74b8f9d43443ac 8965 devel optional klic_3.003-gm1-4.diff.gz 2c0c5f1ab5722475f3a5f20a6dea6bda 136834 doc optional klic-doc_3.003-gm1-4_all.deb 007756f3412909ef63762fe46234eb0b 674290 devel optional klic_3.003-gm1-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFE2roUqIqasIZIJsMRAhpkAJ97BkXYUVzb8EqBnw7r5AIC7G1iUACgnD5R T7aBWg/owZjmuktx/Cb6uVc= =af1a -END PGP SIGNATURE- Accepted: klic-doc_3.003-gm1-4_all.deb to pool/main/k/klic/klic-doc_3.003-gm1-4_all.deb klic_3.003-gm1-4.diff.gz to pool/main/k/klic/klic_3.003-gm1-4.diff.gz klic_3.003-gm1-4.dsc to pool/main/k/klic/klic_3.003-gm1-4.dsc klic_3.003-gm1-4_i386.deb to pool/main/k/klic/klic_3.003-gm1-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pike7.6 7.6.87-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 9 Aug 2006 01:28:37 +0200 Source: pike7.6 Binary: pike7.6-sane pike7.6-meta pike7.6-gl pike7.6-gdbm pike7.6-core pike7.6-bzip2 pike7.6-doc pike7.6-pg pike7.6-sdl pike7.6-mysql pike7.6-odbc pike7.6-image pike7.6-gtk pike7.6-svg pike7.6 pike7.6-pcre pike7.6-manual pike7.6-dev pike7.6-perl pike7.6-reference Architecture: source i386 all Version: 7.6.87-2 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: pike7.6- Recommended meta package for Pike 7.6 pike7.6-bzip2 - Bzip2 module for Pike pike7.6-core - Powerful interpreted programming language pike7.6-dev - Development files for Pike 7.6 pike7.6-doc - Pike 7.6 documentation meta package pike7.6-gdbm - Gdbm module for Pike pike7.6-gl - Mesa module for Pike pike7.6-gtk - GTK module for Pike pike7.6-image - Image module for Pike pike7.6-manual - Pike 7.6 manual pike7.6-meta - Meta package for Pike 7.6 pike7.6-mysql - Mysql module for Pike pike7.6-odbc - Odbc module for Pike pike7.6-pcre - PCRE module for Pike pike7.6-perl - Perl module for Pike pike7.6-pg - Postgres module for Pike pike7.6-reference - Pike 7.6 reference pike7.6-sane - SANE module for Pike pike7.6-sdl - SDL module for Pike pike7.6-svg - SVG format support for Pike Changes: pike7.6 (7.6.87-2) unstable; urgency=low . * Shortened the long descriptions of several binary packages * Added short description of pike, plus an url, to the description of the pike modules binary packages Files: f466b3d00c80a67209eb10aae0904964 1429 interpreters optional pike7.6_7.6.87-2.dsc f5c164b77ef442fe7420be3e5035a8a7 27517 interpreters optional pike7.6_7.6.87-2.diff.gz 98855bfd90dff04e70b31bec9ec2ba5f 19250 interpreters optional pike7.6_7.6.87-2_all.deb 4c468916f3194c27c7f928d6ca31179f 253450 interpreters optional pike7.6-dev_7.6.87-2_all.deb 5b4c16ed0893d8bd0b2dfecf130cf6ab 3991946 doc optional pike7.6-manual_7.6.87-2_all.deb 97d65baac5c6aa249f690f63afd3add1 5504858 doc optional pike7.6-reference_7.6.87-2_all.deb 3eaee8696c4a42382aa6e4574ae71998 19084 doc optional pike7.6-doc_7.6.87-2_all.deb 28a3ea990f06050c611ee656e1718dfe 19190 interpreters optional pike7.6-meta_7.6.87-2_all.deb e887410480b4f8d8ec03f14f30436b15 2529580 interpreters optional pike7.6-core_7.6.87-2_i386.deb e4c5f1adb2cf450e8bef17a19cbdd07a 21454 interpreters optional pike7.6-mysql_7.6.87-2_i386.deb 25b95285843b38cc49139377ef979269 16560 interpreters optional pike7.6-pg_7.6.87-2_i386.deb 30da2fcd22a567c19b769456068884b3 11046 interpreters optional pike7.6-odbc_7.6.87-2_i386.deb 4d343a3e3e39c7a2161977cdcb884f4e 23238 interpreters optional pike7.6-svg_7.6.87-2_i386.deb dc4786f8c35e28e0b939c56ccbad9ca7 391156 interpreters optional pike7.6-image_7.6.87-2_i386.deb c04c4200a874d5a250e41b6283e40975 36638 interpreters optional pike7.6-sdl_7.6.87-2_i386.deb 14e62ac5475a2abe325e639133c8d1a0 6904 interpreters optional pike7.6-gdbm_7.6.87-2_i386.deb 017cea95642c112413d9b1b5432596d6 165154 interpreters optional pike7.6-gtk_7.6.87-2_i386.deb 30138fb8465df1946c0a180583a2100a 44096 interpreters optional pike7.6-gl_7.6.87-2_i386.deb f5217a76770418ccf2d0a5ff06d8154f 9480 interpreters optional pike7.6-sane_7.6.87-2_i386.deb c5f790d0ea2a390ae6bb75d39d896412 13148 interpreters optional pike7.6-perl_7.6.87-2_i386.deb 3e91fd50b4baf302fb3815000d5b35e4 28458 interpreters optional pike7.6-pcre_7.6.87-2_i386.deb 41f0903a0309ffaab0e696592c07267d 28228 interpreters optional pike7.6-bzip2_7.6.87-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2tmPq3909GIf5uoRAjqbAJ9E9DUAl3xyQBcrmLGmaSD3+aSWVACeJabx stPnHMGN4g6D9/Q9s9m8xTQ= =HT0i -END PGP SIGNATURE- Accepted: pike7.6-bzip2_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-bzip2_7.6.87-2_i386.deb pike7.6-core_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-core_7.6.87-2_i386.deb pike7.6-dev_7.6.87-2_all.deb to pool/main/p/pike7.6/pike7.6-dev_7.6.87-2_all.deb pike7.6-doc_7.6.87-2_all.deb to pool/main/p/pike7.6/pike7.6-doc_7.6.87-2_all.deb pike7.6-gdbm_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-gdbm_7.6.87-2_i386.deb pike7.6-gl_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-gl_7.6.87-2_i386.deb pike7.6-gtk_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-gtk_7.6.87-2_i386.deb pike7.6-image_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-image_7.6.87-2_i386.deb pike7.6-manual_7.6.87-2_all.deb to pool/main/p/pike7.6/pike7.6-manual_7.6.87-2_all.deb pike7.6-meta_7.6.87-2_all.deb to pool/main/p/pike7.6/pike7.6-meta_7.6.87-2_all.deb pike7.6-mysql_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-mysql_7.6.87-2_i386.deb pike7.6-odbc_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-odbc_7.6.87-2_i386.deb pike7.6-pcre_7.6.87-2_i386.deb to pool/main/p/pike7.6/pike7.6-pcre_7.6.87-2_i386.deb pike7.6-perl_7.6.87-2_i386.deb
Accepted newt 0.52.2-7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 10:18:08 +0100 Source: newt Binary: libnewt0.52 libnewt-dev libnewt-pic newt-tcl whiptail python-newt Architecture: source i386 Version: 0.52.2-7 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: libnewt-dev - Developer's toolkit for newt windowing library libnewt-pic - Not Erik's Windowing Toolkit, shared library subset kit libnewt0.52 - Not Erik's Windowing Toolkit - text mode windowing with slang newt-tcl - A newt module for Tcl python-newt - A NEWT module for Python whiptail - Displays user-friendly dialog boxes from shell scripts Changes: newt (0.52.2-7) unstable; urgency=low . * debian/patches/222_fix_gauge_crash.patch - prevent a negative number input to the gauge dialog from crashing whiptail by smashing the stack. Thanks to Ryan Lortie. Files: 644c4e038df611590d6892213b27c2b5 847 devel optional newt_0.52.2-7.dsc ba78b7a8778714c46020d2cbb119ccc3 100037 devel optional newt_0.52.2-7.diff.gz 6af88b7886564aa693900ab131f6d027 63358 base standard libnewt0.52_0.52.2-7_i386.deb dca9e63bb3d0895ac12106790c127161 84946 libdevel optional libnewt-dev_0.52.2-7_i386.deb 268f6993a5f777b4f4081040da8d57d4 57278 libdevel extra libnewt-pic_0.52.2-7_i386.deb 752e71dc81d0d5b8a763d7501f5d9201 28754 interpreters extra newt-tcl_0.52.2-7_i386.deb de5e0752daff55f5c371613d76b1c49e 37812 python standard python-newt_0.52.2-7_i386.deb 7ec4730d57248ecf42b4932c44897628 34318 utils important whiptail_0.52.2-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2vwqQTK/kCo4XFcRAgiyAJ9rCPGfnNep5qAm9WYW59oC8KSJNQCeLMk8 9Ty488VHG9X7K+gzl97+AuE= =Izvf -END PGP SIGNATURE- Accepted: libnewt-dev_0.52.2-7_i386.deb to pool/main/n/newt/libnewt-dev_0.52.2-7_i386.deb libnewt-pic_0.52.2-7_i386.deb to pool/main/n/newt/libnewt-pic_0.52.2-7_i386.deb libnewt0.52_0.52.2-7_i386.deb to pool/main/n/newt/libnewt0.52_0.52.2-7_i386.deb newt-tcl_0.52.2-7_i386.deb to pool/main/n/newt/newt-tcl_0.52.2-7_i386.deb newt_0.52.2-7.diff.gz to pool/main/n/newt/newt_0.52.2-7.diff.gz newt_0.52.2-7.dsc to pool/main/n/newt/newt_0.52.2-7.dsc python-newt_0.52.2-7_i386.deb to pool/main/n/newt/python-newt_0.52.2-7_i386.deb whiptail_0.52.2-7_i386.deb to pool/main/n/newt/whiptail_0.52.2-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lua50 5.0.3-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 10:45:57 +0200 Source: lua50 Binary: liblualib50-dev liblua50-dev lua50-doc liblua50 lua50 liblualib50 Architecture: source amd64 all Version: 5.0.3-1 Distribution: unstable Urgency: low Maintainer: Enrico Tassi [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: liblua50 - Main interpreter library for the Lua 5.0 programming language liblua50-dev - Main interpreter library for Lua 5.0: static library and headers liblualib50 - Extension library for the Lua 5.0 programming language liblualib50-dev - Extension library for Lua 5.0: static and headers lua50 - Small embeddable language with simple procedural syntax lua50-doc - Documentation for the Lua 5.0 programming language Closes: 339009 359132 370633 378764 Changes: lua50 (5.0.3-1) unstable; urgency=low . * New upstream release (Closes: #378764) * Applied patch to fix -l (Closes: #370633) * The current interpreter returns 1 in case of fatal error (Closes: #359132) * Enrico Tassi [EMAIL PROTECTED] adopted lua50 (Closes: #339009) * Updated standards to 3.7.2 Files: 5450de1febe64557c171e027380bc5d0 666 interpreters optional lua50_5.0.3-1.dsc feee27132056de2949ce499b0ef4c480 191384 interpreters optional lua50_5.0.3.orig.tar.gz df20cb78fe521b15e9f97c8d08b6386f 10869 interpreters optional lua50_5.0.3-1.diff.gz d849d2a9bfd3d61c501a701193536ad8 62974 doc optional lua50-doc_5.0.3-1_all.deb 4394916c7bdb7a2e835023b14102453d 25854 interpreters optional lua50_5.0.3-1_amd64.deb afe518f7138a2b7b907059259d8ca9d5 52258 libs optional liblua50_5.0.3-1_amd64.deb 7116e10e82ff26425578a563651d0725 63898 libdevel optional liblua50-dev_5.0.3-1_amd64.deb 9760214ff4c1cf5bedfc5dc474dbfa5b 34052 libs optional liblualib50_5.0.3-1_amd64.deb 6c7a89a803ca592c8501edcbb03817fd 40338 libdevel optional liblualib50-dev_5.0.3-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD4DBQFE2vXD7kkcPgEj8vIRAk8NAJMFT9AhoDaVooe5ny0H4r21/2i/AJwOIZAT dwsZF8S9EDWwLJcPHpW3bw== =ecL5 -END PGP SIGNATURE- Accepted: liblua50-dev_5.0.3-1_amd64.deb to pool/main/l/lua50/liblua50-dev_5.0.3-1_amd64.deb liblua50_5.0.3-1_amd64.deb to pool/main/l/lua50/liblua50_5.0.3-1_amd64.deb liblualib50-dev_5.0.3-1_amd64.deb to pool/main/l/lua50/liblualib50-dev_5.0.3-1_amd64.deb liblualib50_5.0.3-1_amd64.deb to pool/main/l/lua50/liblualib50_5.0.3-1_amd64.deb lua50-doc_5.0.3-1_all.deb to pool/main/l/lua50/lua50-doc_5.0.3-1_all.deb lua50_5.0.3-1.diff.gz to pool/main/l/lua50/lua50_5.0.3-1.diff.gz lua50_5.0.3-1.dsc to pool/main/l/lua50/lua50_5.0.3-1.dsc lua50_5.0.3-1_amd64.deb to pool/main/l/lua50/lua50_5.0.3-1_amd64.deb lua50_5.0.3.orig.tar.gz to pool/main/l/lua50/lua50_5.0.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnome-doc-utils 0.6.1-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 11:17:33 +0200 Source: gnome-doc-utils Binary: gnome-doc-utils Architecture: source all Version: 0.6.1-3 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers [EMAIL PROTECTED] Changed-By: Loic Minier [EMAIL PROTECTED] Description: gnome-doc-utils - a collection of documentation utilities for the Gnome project Closes: 353503 Changes: gnome-doc-utils (0.6.1-3) unstable; urgency=low . * New patch, 10_drop-ac-output-in-gdu-m4, backported fix for GNOME #331735. (Closes: #353503) Files: 3919591682b2eb1354364365188de0b5 1518 gnome optional gnome-doc-utils_0.6.1-3.dsc cd73d9612127c2c8c71835dd8349626f 3981 gnome optional gnome-doc-utils_0.6.1-3.diff.gz ff789ee89e4f50af2f03b5a178c14cba 172098 gnome optional gnome-doc-utils_0.6.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2vqN4VUX8isJIMARAthQAKCNH7fV10Rw5u/lLic4qamXzj6+IACgqwR5 PAk8xSHb4tHJlrfE35MqvBY= =S6Ah -END PGP SIGNATURE- Accepted: gnome-doc-utils_0.6.1-3.diff.gz to pool/main/g/gnome-doc-utils/gnome-doc-utils_0.6.1-3.diff.gz gnome-doc-utils_0.6.1-3.dsc to pool/main/g/gnome-doc-utils/gnome-doc-utils_0.6.1-3.dsc gnome-doc-utils_0.6.1-3_all.deb to pool/main/g/gnome-doc-utils/gnome-doc-utils_0.6.1-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lzma 4.43-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 8 Aug 2006 23:26:37 +0200 Source: lzma Binary: lzma Architecture: source i386 Version: 4.43-2 Distribution: unstable Urgency: low Maintainer: Mohammed Adnène Trojette [EMAIL PROTECTED] Changed-By: Mohammed Adnène Trojette [EMAIL PROTECTED] Description: lzma - Default and general compression method of 7z format in 7-Zip prog Closes: 378218 379398 Changes: lzma (4.43-2) unstable; urgency=low . * Change debian/copyright to utf-8. * Build-Depends on quilt. * Correct typo on description spotted by Andrey Kiselev. (Closes: #378218) * Add a NEWS.Debian. * Add some patches with the help of Alexander Sack and Lasse Collin to integrate Tukaani's lzma-utils: + 01_large_files.diff: make large files work. + 02_lzmp.diff: use a wrapper to lzma to have a gzip-like interface. (Closes: #379398) + 03_lzma_manpage.diff: manual page for the new lzma. * Changes introduced by the Tukaani patch: + the old /usr/bin/lzma becomes /usr/bin/lzma_alone. + it is superseded with a gzip-like command line tool. + manpages are updated accordingly. Files: a5f48c6c6133e6c13b39f04bcbaf6a7e 1203 utils optional lzma_4.43-2.dsc 183767ab74aff41c641b478cf0d02e54 12797 utils optional lzma_4.43-2.diff.gz 45f0120156dee2a26093d7de84bbd193 124780 utils optional lzma_4.43-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iQIVAwUBRNr7EsjxMGWNdiHmAQJ35g//RD69sfSxxPYSCsmnsSo1nCdMhf+46j4o 8RvPLoFoRsOK2wSUDJQ6lhZ6JbRbq78AASrkgFE+HZp9leEK+zIbnN3yIYR7XWFQ ugT5yNgILlvO6aecd+fjzfAkzcmD3gX7y3nrMCISeKP4rhR7LHWnFZWgpycHSmnY rgjv0L3uVnEB0nGmcovti/9yRmEqaUFa2RxKgM/jE1XU4LNjjTKaer5Do3M7a/pI mbcWXiyL+0Bm0I/9vfMtuO7o/qmoqFWnYCuEdQXSIWxv5PRJkkoIuVNWg4SJ0Syt hqXF6Jx9CIp7en1BFlmgRsD2WgtB/gz+fTetJz8iXf7KV1Pj/PVyx5TNCLER/8XJ 9R2W891SFNP8VWAa3+HsTrXG7mrgWV0FL2dT39CNAPZ1aF2dnG5QhKFBDOTe0+qs Vyhgl3iras9rhv2rFDPih0iQK6JwUXB0JUd1v3AETvUte6cWBtLeR59MjWzRbRuo foqiJOoZVhUnA0tNQDOzG+TnbEG7TTNUt2LBw8nEtbP7kSdvy5Q4UBYIeJ6UPt3Z LciWj4Z0f184Nj7KBNZ9MHKJ14o0DTf95tmGzPvHFfHE+mJq9SlwM9tOCIEPt0E3 ImrXXBPUCdyyoHuSbYM2ckSdxQ/lMHZidRh8BoZaSDPqC9RPxe14xRaNgfk03MHp aAqf5+y3dFY= =azt/ -END PGP SIGNATURE- Accepted: lzma_4.43-2.diff.gz to pool/main/l/lzma/lzma_4.43-2.diff.gz lzma_4.43-2.dsc to pool/main/l/lzma/lzma_4.43-2.dsc lzma_4.43-2_i386.deb to pool/main/l/lzma/lzma_4.43-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kernel-patch-debianlogo 1.5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 10:09:52 +0200 Source: kernel-patch-debianlogo Binary: kernel-patch-debianlogo Architecture: source all Version: 1.5 Distribution: unstable Urgency: low Maintainer: Stefano Melchior [EMAIL PROTECTED] Changed-By: Emanuele Rocca [EMAIL PROTECTED] Description: kernel-patch-debianlogo - Display a Debian logo on a framebuffer device at boottime Changes: kernel-patch-debianlogo (1.5) unstable; urgency=low . * Added support for Linux 2.6.17 * Standards-Version updated * Build-Depends-Indep changed to Build-Depends: debhelper Files: 3294810a530eb5c6195153d30763723f 651 devel extra kernel-patch-debianlogo_1.5.dsc 13a5d8b3cad11193d49a7df1730d59f5 55393 devel extra kernel-patch-debianlogo_1.5.tar.gz f314ad7655f5bb2347ae4d27219077d3 57520 devel extra kernel-patch-debianlogo_1.5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2uqbC6DuA+rxm2ARAp/NAJ0VwP7mkSIK0H74CgrqZM7c+lzMTwCbBAH6 swsXroBSnhsagsGqzH+BrEI= =+tiQ -END PGP SIGNATURE- Accepted: kernel-patch-debianlogo_1.5.dsc to pool/main/k/kernel-patch-debianlogo/kernel-patch-debianlogo_1.5.dsc kernel-patch-debianlogo_1.5.tar.gz to pool/main/k/kernel-patch-debianlogo/kernel-patch-debianlogo_1.5.tar.gz kernel-patch-debianlogo_1.5_all.deb to pool/main/k/kernel-patch-debianlogo/kernel-patch-debianlogo_1.5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libglade2 1:2.6.0-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 11:36:20 +0200 Source: libglade2 Binary: libglade2-0 libglade2-dev Architecture: source i386 Version: 1:2.6.0-2 Distribution: unstable Urgency: low Maintainer: Andreas Rottmann [EMAIL PROTECTED] Changed-By: Loic Minier [EMAIL PROTECTED] Description: libglade2-0 - library to load .glade files at runtime libglade2-dev - development files for libglade Closes: 314789 Changes: libglade2 (1:2.6.0-2) unstable; urgency=low . * Remove the /usr/share/doc/libglade2-dev/html symlink in libglade2-dev's prerm, thanks Lior Kaplan and hungerburg. (Closes: #314789) Files: 4b151fb91e5836fda82e490581ccbe81 1511 devel optional libglade2_2.6.0-2.dsc beac1eb330f8a8a2aee30fdf7b4ce35f 4863 devel optional libglade2_2.6.0-2.diff.gz 5dfec1f45f1785e2236ad0482c785aa9 86006 libs optional libglade2-0_2.6.0-2_i386.deb 0f83981a6a0099b16356db1ab500c4ba 130428 libdevel optional libglade2-dev_2.6.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2v6x4VUX8isJIMARAmn5AJ4yRg51d8oRPklurIXo7uKROJhiRACdGu3X jOzEYMBvDPRxGOWaPX5y5Xc= =5lsF -END PGP SIGNATURE- Accepted: libglade2-0_2.6.0-2_i386.deb to pool/main/libg/libglade2/libglade2-0_2.6.0-2_i386.deb libglade2-dev_2.6.0-2_i386.deb to pool/main/libg/libglade2/libglade2-dev_2.6.0-2_i386.deb libglade2_2.6.0-2.diff.gz to pool/main/libg/libglade2/libglade2_2.6.0-2.diff.gz libglade2_2.6.0-2.dsc to pool/main/libg/libglade2/libglade2_2.6.0-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted caudium 2:1.4.7-15 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 11:48:06 +0200 Source: caudium Binary: caudium-ultralog caudium-pixsl caudium-perl caudium caudium-dev caudium-modules Architecture: source i386 Version: 2:1.4.7-15 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: caudium- An extensible WWW server written in Pike caudium-dev - Development files for Caudium caudium-modules - C modules for Caudium caudium-perl - Perl script support for Caudium caudium-pixsl - Pike XSLT module for Caudium caudium-ultralog - Log Parser module for Caudium Closes: 358261 374024 378255 381819 Changes: caudium (2:1.4.7-15) unstable; urgency=low . * New Pike version dependency * Uninstallable due to unmet dep on pike7.6-core (= 7.6.75-99) and pike7.6-image (= 7.6.75-99) (Closes: #381819) * FTBFS with GCC 4.1: Not using -fPIC to make shared lib. (Closes: #358261) * diff for 2:1.4.7-14.1 NMU (Closes: #378255) * [INTL:pt_BR] Please use the attached debconf template translation (Closes: #374024) Files: b5456621b9554bf4d6cef077268a3521 821 web optional caudium_1.4.7-15.dsc 099ac2d3ad113616f1672267c4df97f1 94821 web optional caudium_1.4.7-15.diff.gz 60e0f08b3d0e162617475ee1a51139b6 4528818 web optional caudium_1.4.7-15_i386.deb a0b5530c039b587a1731911c0611b3dd 58910 web optional caudium-modules_1.4.7-15_i386.deb 783bacba7609d8b3b7470ac7f2332ba6 39764 web optional caudium-pixsl_1.4.7-15_i386.deb 03d005be844c91f3a38a9ae50f8c356e 74166 web optional caudium-ultralog_1.4.7-15_i386.deb db714a1aa0ae86369a416a40b5f8da76 24130 devel optional caudium-dev_1.4.7-15_i386.deb 0c89c0c6baecd3014039f2949c86e167 32366 web optional caudium-perl_1.4.7-15_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2wR2q3909GIf5uoRAluFAJ9V+W8EhiC7Gu1OYQM1ZG6lK+lVtgCeMdF4 2QuxEM4iyOyF7L8B5Mo+mog= =sJTW -END PGP SIGNATURE- Accepted: caudium-dev_1.4.7-15_i386.deb to pool/main/c/caudium/caudium-dev_1.4.7-15_i386.deb caudium-modules_1.4.7-15_i386.deb to pool/main/c/caudium/caudium-modules_1.4.7-15_i386.deb caudium-perl_1.4.7-15_i386.deb to pool/main/c/caudium/caudium-perl_1.4.7-15_i386.deb caudium-pixsl_1.4.7-15_i386.deb to pool/main/c/caudium/caudium-pixsl_1.4.7-15_i386.deb caudium-ultralog_1.4.7-15_i386.deb to pool/main/c/caudium/caudium-ultralog_1.4.7-15_i386.deb caudium_1.4.7-15.diff.gz to pool/main/c/caudium/caudium_1.4.7-15.diff.gz caudium_1.4.7-15.dsc to pool/main/c/caudium/caudium_1.4.7-15.dsc caudium_1.4.7-15_i386.deb to pool/main/c/caudium/caudium_1.4.7-15_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted syslinux 3.11+3.20pre11-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 11:31:00 +0200 Source: syslinux Binary: syslinux Architecture: source i386 Version: 3.11+3.20pre11-1 Distribution: experimental Urgency: low Maintainer: Juan Cespedes [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: syslinux - Bootloader for Linux/i386 using MS-DOS floppies Changes: syslinux (3.11+3.20pre11-1) experimental; urgency=low . * New upstream pre-release. Files: 2ae810c4c5b1d24b5107304ef69be88a 732 utils optional syslinux_3.11+3.20pre11-1.dsc 0a2c09d26367e2cb41802ec37ffcd2d6 1551872 utils optional syslinux_3.11+3.20pre11.orig.tar.gz 7af0008fb506836dd6ffa15b7b58a061 14448 utils optional syslinux_3.11+3.20pre11-1.diff.gz 898eacf64ec7cc002d02153c44d3e93c 203364 utils optional syslinux_3.11+3.20pre11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2v7B+C5cwEsrK54RAvBZAKCmO7Bfr0uDX/ItFfSQZr0upOGaxACgi7MD A4uNpzcRZoYrbssxdjwqkBg= =KKDw -END PGP SIGNATURE- Accepted: syslinux_3.11+3.20pre11-1.diff.gz to pool/main/s/syslinux/syslinux_3.11+3.20pre11-1.diff.gz syslinux_3.11+3.20pre11-1.dsc to pool/main/s/syslinux/syslinux_3.11+3.20pre11-1.dsc syslinux_3.11+3.20pre11-1_i386.deb to pool/main/s/syslinux/syslinux_3.11+3.20pre11-1_i386.deb syslinux_3.11+3.20pre11.orig.tar.gz to pool/main/s/syslinux/syslinux_3.11+3.20pre11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pike-public.parser.xml2 1.38-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 12:20:04 +0200 Source: pike-public.parser.xml2 Binary: pike-public.parser.xml2 pike7.6-public.parser.xml2 Architecture: source i386 Version: 1.38-2 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: pike-public.parser.xml2 - libxml2-based XML parser module for Pike (default version) pike7.6-public.parser.xml2 - libxml2-based XML parser module for Pike Closes: 359248 381818 Changes: pike-public.parser.xml2 (1.38-2) unstable; urgency=low . * New Pike dependency * Uninstallable due to unmet dep on pike7.6-core (= 7.6.75-99) (Closes: #381818) * XML2.so has rpath to /usr/local/devel (Closes: #359248) Files: 3b5d28f6ec2825b0af1397c3bf2acf43 735 interpreters optional pike-public.parser.xml2_1.38-2.dsc fb0a2e0a1bb196e27a3b92d94fa3b182 11236 interpreters optional pike-public.parser.xml2_1.38-2.diff.gz a7f2159a7d3432ba1dc4d8b67fba2b52 13136 interpreters optional pike-public.parser.xml2_1.38-2_i386.deb 52874f73dba20067f7a5596e57bd4d65 65982 interpreters optional pike7.6-public.parser.xml2_1.38-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2wjAq3909GIf5uoRApT/AJ9v9h56jfpg/KXi/ku63M9zWt70ZwCeIwuL eZI5R9KIFDzd63kVvPuBaks= =oydU -END PGP SIGNATURE- Accepted: pike-public.parser.xml2_1.38-2.diff.gz to pool/main/p/pike-public.parser.xml2/pike-public.parser.xml2_1.38-2.diff.gz pike-public.parser.xml2_1.38-2.dsc to pool/main/p/pike-public.parser.xml2/pike-public.parser.xml2_1.38-2.dsc pike-public.parser.xml2_1.38-2_i386.deb to pool/main/p/pike-public.parser.xml2/pike-public.parser.xml2_1.38-2_i386.deb pike7.6-public.parser.xml2_1.38-2_i386.deb to pool/main/p/pike-public.parser.xml2/pike7.6-public.parser.xml2_1.38-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pike-public.network.pcap 1.2-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 12:18:06 +0200 Source: pike-public.network.pcap Binary: pike-public.network.pcap pike7.6-public.network.pcap Architecture: source i386 Version: 1.2-4 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: pike-public.network.pcap - Pike interface module for the pcap library (default) pike7.6-public.network.pcap - Pike interface module for the pcap library Closes: 359247 369628 Changes: pike-public.network.pcap (1.2-4) unstable; urgency=low . * New Pike dependency * uninstallable in unstable (pike7.6 too new) (Closes: #369628) * Pcap.so include rpath to /usr/local/devel/ (Closes: #359247) Files: 6157f9f3e24246cbe76b14ac40cdba45 713 interpreters optional pike-public.network.pcap_1.2-4.dsc e0bb41a9ca87ebffbad171167a7cd81b 17215 interpreters optional pike-public.network.pcap_1.2-4.diff.gz b88db87aa19af0979220cfa206776315 11074 interpreters optional pike-public.network.pcap_1.2-4_i386.deb 3d326d5c926c716aeaa767111d9a754f 17998 interpreters optional pike7.6-public.network.pcap_1.2-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2wg0q3909GIf5uoRAg19AJ9Fjp1zkpGqk8erAwN3+7+fcEy1dQCdFo9X 3lKO97bserr4zorR38Znsos= =lkg2 -END PGP SIGNATURE- Accepted: pike-public.network.pcap_1.2-4.diff.gz to pool/main/p/pike-public.network.pcap/pike-public.network.pcap_1.2-4.diff.gz pike-public.network.pcap_1.2-4.dsc to pool/main/p/pike-public.network.pcap/pike-public.network.pcap_1.2-4.dsc pike-public.network.pcap_1.2-4_i386.deb to pool/main/p/pike-public.network.pcap/pike-public.network.pcap_1.2-4_i386.deb pike7.6-public.network.pcap_1.2-4_i386.deb to pool/main/p/pike-public.network.pcap/pike7.6-public.network.pcap_1.2-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pike-public.tools.configfiles 1.0-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 12:24:47 +0200 Source: pike-public.tools.configfiles Binary: pike7.6-public.tools.configfiles pike-public.tools.configfiles Architecture: source all Version: 1.0-4 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: pike-public.tools.configfiles - Pike module for accessing ini-style configurations (default) pike7.6-public.tools.configfiles - Pike module for accessing ini-style configurations Closes: 369611 Changes: pike-public.tools.configfiles (1.0-4) unstable; urgency=low . * New Pike dependency * uninstallable in unstable (pike7.6 too new) (Closes: #369611) Files: 5ccacf610d4b82bf1a0fb1e10230adb1 721 interpreters optional pike-public.tools.configfiles_1.0-4.dsc ea1bf67b428b5f22455ce54eecb6c743 2794 interpreters optional pike-public.tools.configfiles_1.0-4.diff.gz 6540aa3b9a05c42f2452fbdd1960cfa3 2394 interpreters optional pike-public.tools.configfiles_1.0-4_all.deb 67a3c63b6e043710237c5481337b17f2 4042 interpreters optional pike7.6-public.tools.configfiles_1.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2wm4q3909GIf5uoRAp2JAJ9fIZpRubKAr9ZeJuEnnyj/Rj/cVwCcDHkU WxPHKHiyyQnMO9vaXkAKhKA= =o0hV -END PGP SIGNATURE- Accepted: pike-public.tools.configfiles_1.0-4.diff.gz to pool/main/p/pike-public.tools.configfiles/pike-public.tools.configfiles_1.0-4.diff.gz pike-public.tools.configfiles_1.0-4.dsc to pool/main/p/pike-public.tools.configfiles/pike-public.tools.configfiles_1.0-4.dsc pike-public.tools.configfiles_1.0-4_all.deb to pool/main/p/pike-public.tools.configfiles/pike-public.tools.configfiles_1.0-4_all.deb pike7.6-public.tools.configfiles_1.0-4_all.deb to pool/main/p/pike-public.tools.configfiles/pike7.6-public.tools.configfiles_1.0-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pike-public.protocols.syslog 1.1-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 12:22:33 +0200 Source: pike-public.protocols.syslog Binary: pike-public.protocols.syslog pike7.6-public.protocols.syslog Architecture: source all Version: 1.1-4 Distribution: unstable Urgency: low Maintainer: Marek Habersack [EMAIL PROTECTED] Changed-By: Marek Habersack [EMAIL PROTECTED] Description: pike-public.protocols.syslog - Pike module implementing the Syslog protocol (default) pike7.6-public.protocols.syslog - Pike module implementing the Syslog protocol Closes: 369629 Changes: pike-public.protocols.syslog (1.1-4) unstable; urgency=low . * New Pike dependency * uninstallable in unstable (pike7.6 too new) (Closes: #369629) Files: ddf1876d1b92d39205e480fc9ecb7228 631 interpreters optional pike-public.protocols.syslog_1.1-4.dsc 68c74fda565715daa7040efc46f9d5d1 43456 interpreters optional pike-public.protocols.syslog_1.1-4.tar.gz 774fe4d9ca989fd05a33a8595af4f62c 10866 interpreters optional pike-public.protocols.syslog_1.1-4_all.deb 5a0841a6ce69f46aa8371dffe9dd5b72 13086 interpreters optional pike7.6-public.protocols.syslog_1.1-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE2wlPq3909GIf5uoRAqMPAJ0YMkfL5SuNHWMB4T5a4NFhmJfoWwCgiLr6 VfsBxt8Mz/G03HwLyIA5Kak= =QFH1 -END PGP SIGNATURE- Accepted: pike-public.protocols.syslog_1.1-4.dsc to pool/main/p/pike-public.protocols.syslog/pike-public.protocols.syslog_1.1-4.dsc pike-public.protocols.syslog_1.1-4.tar.gz to pool/main/p/pike-public.protocols.syslog/pike-public.protocols.syslog_1.1-4.tar.gz pike-public.protocols.syslog_1.1-4_all.deb to pool/main/p/pike-public.protocols.syslog/pike-public.protocols.syslog_1.1-4_all.deb pike7.6-public.protocols.syslog_1.1-4_all.deb to pool/main/p/pike-public.protocols.syslog/pike7.6-public.protocols.syslog_1.1-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mlterm 2.9.3-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 19:17:04 +0900 Source: mlterm Binary: mlterm-im-m17nlib mlterm-im-scim mlterm-tiny mlterm-im-iiimf mlterm-tools mlterm-common mlterm mlterm-im-uim Architecture: source i386 Version: 2.9.3-2 Distribution: unstable Urgency: low Maintainer: Tomohiro KUBOTA [EMAIL PROTECTED] Changed-By: Kenshi Muto [EMAIL PROTECTED] Description: mlterm - MultiLingual TERMinal mlterm-common - MultiLingual TERMinal, common files mlterm-im-iiimf - MultiLingual TERMinal, iiimf input method plugin mlterm-im-m17nlib - MultiLingual TERMinal, m17nlib input method plugin mlterm-im-scim - MultiLingual TERMinal, scim input method plugin mlterm-im-uim - MultiLingual TERMinal, uim input method plugin mlterm-tiny - MultiLingual TERMinal, tiny version mlterm-tools - MultiLingual TERMinal, additional tools Changes: mlterm (2.9.3-2) unstable; urgency=low . * follow uim library transition. Now mlterm-im-uim depends libuim1 instead of libuim0. Files: 53524220ed74efc8ac527732a2fd372f 904 x11 optional mlterm_2.9.3-2.dsc 108a083e9f659a5cd838948d2c1a0312 18421 x11 optional mlterm_2.9.3-2.diff.gz 6ed3c2a5d6c9e5914159e0d2b6cf11b6 182860 x11 optional mlterm_2.9.3-2_i386.deb 1ab00de627f6512a9ff6d2212867d770 159288 x11 optional mlterm-tiny_2.9.3-2_i386.deb e02b95eed063393e1a9450043c53c9e4 613524 x11 optional mlterm-common_2.9.3-2_i386.deb 6474e0e64d3494ebb821272eb1dffdc9 65202 x11 optional mlterm-tools_2.9.3-2_i386.deb 699ba0a444c73477828ad29fb0539804 20978 x11 optional mlterm-im-uim_2.9.3-2_i386.deb 7d770edd76d51aae73bcdbc2835fec27 28432 x11 optional mlterm-im-iiimf_2.9.3-2_i386.deb c9f7376230fa309b9d58e554db91630d 40868 x11 optional mlterm-im-scim_2.9.3-2_i386.deb f477842ea97377b376020a77ac1c419c 18192 x11 optional mlterm-im-m17nlib_2.9.3-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkTbCy4ACgkQQKW+7XLQPLGy4ACgrN7n9P3y8xY+gay5UU+sSNvW ncMAnRmlkDuQGwHpO+7MvzYJV9Xdk9XL =US1B -END PGP SIGNATURE- Accepted: mlterm-common_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-common_2.9.3-2_i386.deb mlterm-im-iiimf_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-im-iiimf_2.9.3-2_i386.deb mlterm-im-m17nlib_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-im-m17nlib_2.9.3-2_i386.deb mlterm-im-scim_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-im-scim_2.9.3-2_i386.deb mlterm-im-uim_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-im-uim_2.9.3-2_i386.deb mlterm-tiny_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-tiny_2.9.3-2_i386.deb mlterm-tools_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm-tools_2.9.3-2_i386.deb mlterm_2.9.3-2.diff.gz to pool/main/m/mlterm/mlterm_2.9.3-2.diff.gz mlterm_2.9.3-2.dsc to pool/main/m/mlterm/mlterm_2.9.3-2.dsc mlterm_2.9.3-2_i386.deb to pool/main/m/mlterm/mlterm_2.9.3-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted last-exit 2.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 09:47:42 +0100 Source: last-exit Binary: last-exit Architecture: source i386 Version: 2.0-1 Distribution: unstable Urgency: low Maintainer: Ross Burton [EMAIL PROTECTED] Changed-By: Ross Burton [EMAIL PROTECTED] Description: last-exit - Last.fm audio player Changes: last-exit (2.0-1) unstable; urgency=low . * New upstream release * debian/control: + Add libdbus-1-dev, libdbus-glib-1-dev to Build-Depends * debian/patches/shell.diff: + Dropped, merged upstream . (thanks to Sebastian Dröge [EMAIL PROTECTED] for the work) Files: 80caae4aee4d32f167da7c6c7babcb87 816 gnome optional last-exit_2.0-1.dsc 7156a536554cca0e39807675188cfc8a 439735 gnome optional last-exit_2.0.orig.tar.gz f43d0ac651f0d24d062bbf08c2f7c804 1577 gnome optional last-exit_2.0-1.diff.gz 6a3fcca5bd8172aeff7b1e9dd517ec03 78802 gnome optional last-exit_2.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFE2w7iLQnkR9C0M98RAo3SAJ4+NrhqYeCsXIRR60fMq/do4PiCZQCcDiF7 PxVi4R/V3lo07VxYLw0Zodo= =JMpX -END PGP SIGNATURE- Accepted: last-exit_2.0-1.diff.gz to pool/main/l/last-exit/last-exit_2.0-1.diff.gz last-exit_2.0-1.dsc to pool/main/l/last-exit/last-exit_2.0-1.dsc last-exit_2.0-1_i386.deb to pool/main/l/last-exit/last-exit_2.0-1_i386.deb last-exit_2.0.orig.tar.gz to pool/main/l/last-exit/last-exit_2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-support 0.4.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 14:03:48 +0200 Source: python-support Binary: python-support Architecture: source all Version: 0.4.1 Distribution: unstable Urgency: low Maintainer: Josselin Mouette [EMAIL PROTECTED] Changed-By: Josselin Mouette [EMAIL PROTECTED] Description: python-support - automated rebuilding support for python modules Changes: python-support (0.4.1) unstable; urgency=low . * dh_pysupport: + Implement the -X option to exclude files from being searched to generate the dependencies. + Detect private extensions as .so files calling Py_InitModule*. In this case, a strict dependency on python (= X.Y), python ( X.Y+1) is generated. Files: 05e553b76744a914fd95a022a047f759 557 python optional python-support_0.4.1.dsc 1ccdc76de736bb2b18941f6c59709576 25621 python optional python-support_0.4.1.tar.gz 9dd86a6d671579a91c8c86c16302afee 22456 python optional python-support_0.4.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2yFxrSla4ddfhTMRAt2qAKCXQoAmwXbW8OX5p2mfHRBFOp2GJQCg3xQ+ DanYVzx51aTn7O8O87bkUVM= =CM6a -END PGP SIGNATURE- Accepted: python-support_0.4.1.dsc to pool/main/p/python-support/python-support_0.4.1.dsc python-support_0.4.1.tar.gz to pool/main/p/python-support/python-support_0.4.1.tar.gz python-support_0.4.1_all.deb to pool/main/p/python-support/python-support_0.4.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted koffice-l10n 1.5.2-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Aug 2006 20:07:20 +0200 Source: koffice-l10n Binary: koffice-i18n-srlatin koffice-i18n-uk koffice-i18n-eu koffice-i18n-fi koffice-i18n-tr koffice-i18n-tg koffice-i18n-sv koffice-i18n-cs koffice-i18n-ptbr koffice-i18n-uz koffice-i18n-engb koffice-i18n-zhtw koffice-i18n-ro koffice-i18n-da koffice-i18n-hi koffice-i18n-pt koffice-i18n-sr koffice-i18n-mk koffice-i18n-ga koffice-i18n-ca koffice-i18n-sk koffice-i18n-ja koffice-i18n-nn koffice-i18n-ta koffice-i18n-de koffice-i18n-cy koffice-i18n-br koffice-i18n-bg koffice-i18n-se koffice-i18n-hu koffice-i18n-nl koffice-i18n-is koffice-i18n-ru koffice-i18n-fr koffice-i18n-et koffice-i18n-pl koffice-i18n-it koffice-i18n-he koffice-i18n-sl koffice-i18n-es koffice-i18n-af koffice-i18n-zhcn koffice-i18n-ar koffice-i18n-eo koffice-i18n-bs koffice-i18n-lt koffice-i18n-ms koffice-i18n-el koffice-i18n-nb Architecture: source all Version: 1.5.2-2 Distribution: unstable Urgency: low Maintainer: Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org Changed-By: Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org Description: koffice-i18n-af - Afrikaans (af) translations for KOffice koffice-i18n-ar - Arabic (ar) translations for KOffice koffice-i18n-bg - Bulgarian (bg) translations for KOffice koffice-i18n-br - Breton (br) translations for KOffice koffice-i18n-bs - Bosnian (bs) translations for KOffice koffice-i18n-ca - Catalan (ca) translations for KOffice koffice-i18n-cs - Czech (cs) translations for KOffice koffice-i18n-cy - Welsh (cy) translations for KOffice koffice-i18n-da - Danish (da) translations for KOffice koffice-i18n-de - German (de) translations for KOffice koffice-i18n-el - Greek (el) translations for KOffice koffice-i18n-engb - British English (en_GB) translations for KOffice koffice-i18n-eo - Esperanto (eo) translations for KOffice koffice-i18n-es - Spanish (es) translations for KOffice koffice-i18n-et - Estonian (et) translations for KOffice koffice-i18n-eu - Basque (eu) translations for KOffice koffice-i18n-fi - Finnish (fi) translations for KOffice koffice-i18n-fr - French (fr) translations for KOffice koffice-i18n-ga - Irish Gaelic (ga) translations for KOffice koffice-i18n-he - Hebrew (he) translations for KOffice koffice-i18n-hi - Hindi (hi) translations for KOffice koffice-i18n-hu - Hungarian (hu) translations for KOffice koffice-i18n-is - Icelandic (is) translations for KOffice koffice-i18n-it - Italian (it) translations for KOffice koffice-i18n-ja - Japanese (ja) translations for KOffice koffice-i18n-lt - Lithuanian (lt) translations for KOffice koffice-i18n-mk - Macedonian (mk) translations for KOffice koffice-i18n-ms - Malay (ms) translations for KOffice koffice-i18n-nb - Norwegian Bookmal (nb) translations for KOffice koffice-i18n-nl - Dutch (nl) translations for KOffice koffice-i18n-nn - Norwegian Nynorsk (nn) translations for KOffice koffice-i18n-pl - Polish (pl) translations for KOffice koffice-i18n-pt - Portuguese (pt) translations for KOffice koffice-i18n-ptbr - Brazilian Portuguese (pt_BR) translations for KOffice koffice-i18n-ro - Romanian (ro) translations for KOffice koffice-i18n-ru - Russian (ru) translations for KOffice koffice-i18n-se - Northern Sami (se) translations for KOffice koffice-i18n-sk - Slovak (sk) translations for KOffice koffice-i18n-sl - Slovenian (sl) translations for KOffice koffice-i18n-sr - Serbian (sr) translations for KOffice koffice-i18n-srlatin - Latin Serbian ([EMAIL PROTECTED]) translations for KOffice koffice-i18n-sv - Swedish (sv) translations for KOffice koffice-i18n-ta - Tamil (ta) translations for KOffice koffice-i18n-tg - Tajik (tg) translations for KOffice koffice-i18n-tr - Turkish (tr) translations for KOffice koffice-i18n-uk - Ukrainian (uk) translations for KOffice koffice-i18n-uz - Uzbek (uz) translations for KOffice koffice-i18n-zhcn - Chinese Simplified (zh_CN) translations for KOffice koffice-i18n-zhtw - Chinese Traditional (zh_TW) translations for KOffice Closes: 382031 Changes: koffice-l10n (1.5.2-2) unstable; urgency=low . +++ Changes by Ana Beatriz Guerrero Lopez: * Deleting file already packaged in kde-i18n. (Closes: #382031) Files: bba3f4ed40d9ea0893caf5d8d1b2f7c0 1636 kde optional koffice-l10n_1.5.2-2.dsc 605300b7dd43acba4d440c353bb34f56 12004 kde optional koffice-l10n_1.5.2-2.diff.gz e23be984871a75d469e137a4d39de945 110206 kde optional koffice-i18n-af_1.5.2-2_all.deb 7ae23f63f31a13b7d9cd8bad8ce8e44d 81272 kde optional koffice-i18n-ar_1.5.2-2_all.deb 89cedc1affbef6333fe8247e0b54cd58 246024 kde optional koffice-i18n-bg_1.5.2-2_all.deb ddb6eaf326816b63d52a2cdde051c879 154556 kde optional koffice-i18n-br_1.5.2-2_all.deb 1cd08d1ec04472d8a1a22b2cf64e1929 79430 kde optional koffice-i18n-bs_1.5.2-2_all.deb aabcac467f51a2f8a3b1b1d0c1b97070 519536 kde optional koffice-i18n-ca_1.5.2-2_all.deb 4c6f39985012457c5eddd1602df06c29 230250 kde
Accepted gtksourceview 1.7.2-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 10 Aug 2006 15:11:43 +0200
Source: gtksourceview
Binary: libgtksourceview-dev libgtksourceview-common libgtksourceview1.0-0
libgtksourceview-doc
Architecture: source all i386
Version: 1.7.2-1
Distribution: experimental
Urgency: low
Maintainer: Andrew Lau [EMAIL PROTECTED]
Changed-By: Loic Minier [EMAIL PROTECTED]
Description:
libgtksourceview-common - common files for the GTK+ syntax highlighting widget
libgtksourceview-dev - development files for the GTK+ syntax highlighting
widget
libgtksourceview-doc - documentation for the GTK+ syntax highlighting widget
libgtksourceview1.0-0 - shared libraries for the GTK+ syntax highlighting
widget
Changes:
gtksourceview (1.7.2-1) experimental; urgency=low
.
* New upstream development releases, with API additions.
- Target at experimental.
- Bump shlibs to = 1.7.2.
- Stop shipping boo.lang, integrated upstream.
* Sync with overrides and set libgtksourceview-common's Section to misc.
* Install gtk-doc documentation in the standard upstream directory.
- Drop --with-html-dir from configure args.
- Drop now useless libgtksourceview-doc.dirs.
- Update libgtksourceview-doc.install, libgtksourceview-doc.doc-base, and
libgtksourceview-doc.links.
- Drop /usr/share/doc/gtksourceview hierarchy.
- Add a preinst to manually drop symlinks on upgrades since dpkg can't
handle switching a pathname from symlink to directory.
- Add a prerm to manually drop the doc dir on downgrades since dpkg can't
handle switching a pathname from directory to symlink either.
* Add ${misc:Depends}.
* Update watch file to track all stable releases.
Files:
0630819fcfd5da7a179b084f41321699 1591 libs optional gtksourceview_1.7.2-1.dsc
2d2a002129fe290cec11d4afe705ad8d 1270864 libs optional
gtksourceview_1.7.2.orig.tar.gz
2257176100ab7c3902defc0430933ea7 6545 libs optional
gtksourceview_1.7.2-1.diff.gz
5e5adde4593cec0bd07d94183132345c 399938 misc optional
libgtksourceview-common_1.7.2-1_all.deb
dd344a8a1f921966ae8a46885983e63c 76506 doc optional
libgtksourceview-doc_1.7.2-1_all.deb
aeefcea0e44af500aa22a7dc9d5d45dd 109162 libs optional
libgtksourceview1.0-0_1.7.2-1_i386.deb
dfaec72056c90fa83566c49b2b115e55 127730 libdevel optional
libgtksourceview-dev_1.7.2-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE2zDo4VUX8isJIMARAnarAJ9Qmsd0hwo7pX/Te1be4Ijdr/AoIgCdEBBg
7wEGjZ1plkjMctZMqhKJOmI=
=bgMh
-END PGP SIGNATURE-
Accepted:
gtksourceview_1.7.2-1.diff.gz
to pool/main/g/gtksourceview/gtksourceview_1.7.2-1.diff.gz
gtksourceview_1.7.2-1.dsc
to pool/main/g/gtksourceview/gtksourceview_1.7.2-1.dsc
gtksourceview_1.7.2.orig.tar.gz
to pool/main/g/gtksourceview/gtksourceview_1.7.2.orig.tar.gz
libgtksourceview-common_1.7.2-1_all.deb
to pool/main/g/gtksourceview/libgtksourceview-common_1.7.2-1_all.deb
libgtksourceview-dev_1.7.2-1_i386.deb
to pool/main/g/gtksourceview/libgtksourceview-dev_1.7.2-1_i386.deb
libgtksourceview-doc_1.7.2-1_all.deb
to pool/main/g/gtksourceview/libgtksourceview-doc_1.7.2-1_all.deb
libgtksourceview1.0-0_1.7.2-1_i386.deb
to pool/main/g/gtksourceview/libgtksourceview1.0-0_1.7.2-1_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted texinfo 4.8.dfsg.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 11:16:29 +0200 Source: texinfo Binary: texinfo info Architecture: source i386 Version: 4.8.dfsg.1-2 Distribution: unstable Urgency: medium Maintainer: Norbert Preining [EMAIL PROTECTED] Changed-By: Norbert Preining [EMAIL PROTECTED] Description: info - Standalone GNU Info documentation browser texinfo- Documentation system for on-line information and printed output Closes: 367243 380128 Changes: texinfo (4.8.dfsg.1-2) unstable; urgency=medium . * standards version 3.7.2, no changes necessary * fix a missing translation/locale fix (thanks Sven Joachim) (Closes: #367243) * extend wording of the copyright file to clear the differences between info --version (and man page) and the actual copyright. Add a note that the file COPYING mentioned contains GPLv2. (Closes: #380128) (urgency set to medium as this is an RC bug present in testing) Files: f0c8396c562b7bca6276de89239bd136 635 doc standard texinfo_4.8.dfsg.1-2.dsc 67429e6e341009e0cb47c19f66584896 100485 doc standard texinfo_4.8.dfsg.1-2.diff.gz f6c23b476d06ddcc137acc837f96 680682 text standard texinfo_4.8.dfsg.1-2_i386.deb a6e6c0dac1ce25b6e417a89870019063 164662 doc important info_4.8.dfsg.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2z9r1IXdL1v6kOwRArkeAJ45tFzAFB0pIv4a9b/cD8L/AMth0wCfYydd UjE8B1bgFuWlDuvTNVECeS8= =k1qz -END PGP SIGNATURE- Accepted: info_4.8.dfsg.1-2_i386.deb to pool/main/t/texinfo/info_4.8.dfsg.1-2_i386.deb texinfo_4.8.dfsg.1-2.diff.gz to pool/main/t/texinfo/texinfo_4.8.dfsg.1-2.diff.gz texinfo_4.8.dfsg.1-2.dsc to pool/main/t/texinfo/texinfo_4.8.dfsg.1-2.dsc texinfo_4.8.dfsg.1-2_i386.deb to pool/main/t/texinfo/texinfo_4.8.dfsg.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mpt-status 1.1.6-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 8 Aug 2006 23:03:31 +1000 Source: mpt-status Binary: mpt-status Architecture: source i386 Version: 1.1.6-6 Distribution: unstable Urgency: low Maintainer: Steffen Joeris [EMAIL PROTECTED] Changed-By: Steffen Joeris [EMAIL PROTECTED] Description: mpt-status - get RAID status out of mpt (and other) HW RAID controllers Closes: 381926 Changes: mpt-status (1.1.6-6) unstable; urgency=low . * Change check for mptctl modul to also honour it when it is compiled into the kernel (Closes: #381926) * Upload sponsored by Petter Reinholdtsen Files: aedf81cf1d94493a8ed0202051bc29c9 659 admin extra mpt-status_1.1.6-6.dsc 00aec9b1601b4cc54f5c95be8f684f64 43464 admin extra mpt-status_1.1.6-6.diff.gz a2c159c770f2d7c3904cf3d4e9783a32 19626 admin extra mpt-status_1.1.6-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE20cm20zMSyow1ykRAruSAJ90fbkB8sZFJuKx8JEXJ4OG8BvCrACgjOlp z8s73EdkOgCebvgC+7oqlfQ= =4pYu -END PGP SIGNATURE- Accepted: mpt-status_1.1.6-6.diff.gz to pool/main/m/mpt-status/mpt-status_1.1.6-6.diff.gz mpt-status_1.1.6-6.dsc to pool/main/m/mpt-status/mpt-status_1.1.6-6.dsc mpt-status_1.1.6-6_i386.deb to pool/main/m/mpt-status/mpt-status_1.1.6-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xen-tools 2.2-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 15:43:21 + Source: xen-tools Binary: xen-tools Architecture: source all Version: 2.2-4 Distribution: unstable Urgency: medium Maintainer: Radu Spineanu [EMAIL PROTECTED] Changed-By: Steve Kemp [EMAIL PROTECTED] Description: xen-tools - Tools to manage debian XEN virtual servers Closes: 381290 Changes: xen-tools (2.2-4) unstable; urgency=medium . * Avoid hang when installing new systems behind a HTTP proxy. (Closes: #381290) Files: f949644be8bba6eb0f76e97d77712969 640 utils extra xen-tools_2.2-4.dsc 4497d26f96137ee079a8286aa2f7a37b 7076 utils extra xen-tools_2.2-4.diff.gz b438c89c1944fb92ca9e706dc35edfb8 88236 utils extra xen-tools_2.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE20a1wM/Gs81MDZ0RAlj9AJ4k1oTFtZYUNETOLMRPvzw2706dQgCgtxp/ cHDiQoORfOeKegN/GdkLdr4= =nDDK -END PGP SIGNATURE- Accepted: xen-tools_2.2-4.diff.gz to pool/main/x/xen-tools/xen-tools_2.2-4.diff.gz xen-tools_2.2-4.dsc to pool/main/x/xen-tools/xen-tools_2.2-4.dsc xen-tools_2.2-4_all.deb to pool/main/x/xen-tools/xen-tools_2.2-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aap 1.072-1.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 17:36:21 +0200 Source: aap Binary: aap aap-doc Architecture: source all Version: 1.072-1.1 Distribution: unstable Urgency: low Maintainer: Cory Dodt [EMAIL PROTECTED] Changed-By: Pierre Habouzit [EMAIL PROTECTED] Description: aap- make-like expert system for building software aap-doc- make-like expert system for building software (documentation) Closes: 380755 Changes: aap (1.072-1.1) unstable; urgency=low . * Non-maintainer upload. * Bump Standards-Version to 3.7.2. * Update package to the last python policy (Closes: #380755): + use dh_pysupport. + remove old ways to bytecompile. * debhelper changes: + Bump DH_COMPAT to 5. + Move debhelper into B-D instead of B-D-I. Files: 1f05cbadacdf730b17524e5ce2d4205f 619 devel optional aap_1.072-1.1.dsc 0c94544855c8911586e25a77ee35e1f7 4327 devel optional aap_1.072-1.1.diff.gz c4b5b859d3f4c120ca731a1c870c3439 214016 devel optional aap_1.072-1.1_all.deb 20506b367c82499f874dbad73c87b727 676966 doc optional aap-doc_1.072-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE21NmvGr7W6HudhwRApQxAJ9+mMxYT2seQUxQOVnUCHaQ/P+UXACeMRtJ 3RINLyQkq3m1GFMnN+Q3tQ8= =hFu7 -END PGP SIGNATURE- Accepted: aap-doc_1.072-1.1_all.deb to pool/main/a/aap/aap-doc_1.072-1.1_all.deb aap_1.072-1.1.diff.gz to pool/main/a/aap/aap_1.072-1.1.diff.gz aap_1.072-1.1.dsc to pool/main/a/aap/aap_1.072-1.1.dsc aap_1.072-1.1_all.deb to pool/main/a/aap/aap_1.072-1.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dwm 0.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 17:30:00 +0200 Source: dwm Binary: dwm Architecture: source i386 Version: 0.8-1 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: dwm- dynamic window manager Changes: dwm (0.8-1) unstable; urgency=low . * New upstream release. Files: f6009eded35ac50eea04412a8a1e9c2c 566 x11 optional dwm_0.8-1.dsc 63e6076a0e3999b10efc1d1729deda31 14284 x11 optional dwm_0.8.orig.tar.gz 06d598cba3d6e8846b153b6e15bd6032 3170 x11 optional dwm_0.8-1.diff.gz d96fd820a6c602bbcf1baefa1ce5d513 16474 x11 optional dwm_0.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE21Fw+C5cwEsrK54RArRYAJ0eJshWDwWP6OoBCmxzt69bbk6lggCguJEh VF8XcOERQAZ/OlFqJpwQWeo= =vE8s -END PGP SIGNATURE- Accepted: dwm_0.8-1.diff.gz to pool/main/d/dwm/dwm_0.8-1.diff.gz dwm_0.8-1.dsc to pool/main/d/dwm/dwm_0.8-1.dsc dwm_0.8-1_i386.deb to pool/main/d/dwm/dwm_0.8-1_i386.deb dwm_0.8.orig.tar.gz to pool/main/d/dwm/dwm_0.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dmenu 0.3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 17:33:00 +0200 Source: dmenu Binary: dmenu Architecture: source i386 Version: 0.3-1 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: dmenu - dynamic menu Changes: dmenu (0.3-1) unstable; urgency=low . * New upstream release. Files: cf4a5dc03cca79bb244f810f916a3afe 554 x11 optional dmenu_0.3-1.dsc bce526e3fab2d4bd3c513b5b378ca425 6959 x11 optional dmenu_0.3.orig.tar.gz 24dc78616d6ac933f085e533fac05e25 1769 x11 optional dmenu_0.3-1.diff.gz 49d8437788f6b3655b36a9eb7f9cf0c4 8446 x11 optional dmenu_0.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE21Hd+C5cwEsrK54RAnsBAKCk04yN8jzIHY4Wv8l6mL5t6laldgCeLFHj hXKfWPfXiIRuO7YOQrCLfos= =jzw+ -END PGP SIGNATURE- Accepted: dmenu_0.3-1.diff.gz to pool/main/d/dmenu/dmenu_0.3-1.diff.gz dmenu_0.3-1.dsc to pool/main/d/dmenu/dmenu_0.3-1.dsc dmenu_0.3-1_i386.deb to pool/main/d/dmenu/dmenu_0.3-1_i386.deb dmenu_0.3.orig.tar.gz to pool/main/d/dmenu/dmenu_0.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libalgorithm-c3-perl 0.04-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 17:14:26 +0200 Source: libalgorithm-c3-perl Binary: libalgorithm-c3-perl Architecture: source all Version: 0.04-1 Distribution: unstable Urgency: low Maintainer: Debian Catalyst Maintainers [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: libalgorithm-c3-perl - A module for merging hierarchies using the C3 algorithm Changes: libalgorithm-c3-perl (0.04-1) unstable; urgency=low . * New upstream release Files: 52c5d45a8f1f365d831d1d0bfbdf7f62 818 perl optional libalgorithm-c3-perl_0.04-1.dsc 182375a87399eb5472c1be2a9fbfbc24 6916 perl optional libalgorithm-c3-perl_0.04.orig.tar.gz e966263d99b83fc15ec6aabb02bd8f3a 1981 perl optional libalgorithm-c3-perl_0.04-1.diff.gz e611fe78af2fd3b696c01806387b6d75 10158 perl optional libalgorithm-c3-perl_0.04-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD4DBQFE203e+NMfSd6w7DERAnJUAKCCWekCL2mHBiAcHdPwQjCJjjLOLwCYi1mQ IWvkDIS/JQcp2NGNHvJGZw== =RXk8 -END PGP SIGNATURE- Accepted: libalgorithm-c3-perl_0.04-1.diff.gz to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.04-1.diff.gz libalgorithm-c3-perl_0.04-1.dsc to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.04-1.dsc libalgorithm-c3-perl_0.04-1_all.deb to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.04-1_all.deb libalgorithm-c3-perl_0.04.orig.tar.gz to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.04.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted konserve 0.10.3-3 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 03 Aug 2006 20:49:28 +0200
Source: konserve
Binary: konserve
Architecture: source i386
Version: 0.10.3-3
Distribution: unstable
Urgency: medium
Maintainer: Alejandro Exojo Piqueras [EMAIL PROTECTED]
Changed-By: Alejandro Exojo Piqueras [EMAIL PROTECTED]
Description:
konserve - KDE system tray application that performs periodic backups
Closes: 344682 379818
Changes:
konserve (0.10.3-3) unstable; urgency=medium
.
* Fix the installation directory of the user documentation: force it to be
${datadir}/doc/kde/HTML by exporting kde_htmldir with that value assigned
(Closes: #344682).
* Update 01_admin_update.diff to a diff against branches/KDE/3.5 (up to
revision 569289), to include support for autoconf 2.60 (Closes: #379818).
Make executable the new file included in the diff, because it's a script.
* Raise urgency to medium, because fixes a RC bug.
* Raised Standards-Version to 3.7.2 (no changes required).
* Raise debhelper compatibility level to 5 (no changes required).
* Clarify copyright/license in debian/copyright.
* Copy config.* to admin/, instead of the root directory, and build-depend
on autotools-dev.
* Force C collation in sort invocations of debian/rules.
* Change to lowercase the name of the application in the manpage.
Files:
5cb52128b2a178f57cc04fc4828f91bd 631 kde optional konserve_0.10.3-3.dsc
138e9cd04aee1a45c1102a673103ba4c 105830 kde optional konserve_0.10.3-3.diff.gz
9bbc3c6b50b86cbbb8c9e2b275d6d1d1 501460 kde optional konserve_0.10.3-3_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFE21bolAuUx1tI/64RAsu5AJ4kLKeCt6zkcr3GcJIdQMaVxvyY9ACffoXT
HHEFvCvXuYQr2dT3N56WkY4=
=PpjR
-END PGP SIGNATURE-
Accepted:
konserve_0.10.3-3.diff.gz
to pool/main/k/konserve/konserve_0.10.3-3.diff.gz
konserve_0.10.3-3.dsc
to pool/main/k/konserve/konserve_0.10.3-3.dsc
konserve_0.10.3-3_i386.deb
to pool/main/k/konserve/konserve_0.10.3-3_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apt-listchanges 2.60 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 18:25:39 +0200 Source: apt-listchanges Binary: apt-listchanges Architecture: source all Version: 2.60 Distribution: unstable Urgency: low Maintainer: Pierre Habouzit [EMAIL PROTECTED] Changed-By: Pierre Habouzit [EMAIL PROTECTED] Description: apt-listchanges - Display change history from .deb archives Closes: 133306 251084 259171 260295 260534 262603 280323 283357 285440 292739 293594 293594 294948 297242 302548 308744 315174 318496 318498 318499 327508 330195 332443 341845 375300 375748 375953 375956 380759 Changes: apt-listchanges (2.60) unstable; urgency=low . * Change of maintainer (and upstream): + put myself as maintainer. + put Matt into Uploaders (thanks for all your work on this package !). + ack NMUs (Closes: #251084, 259171, 260295, 260534, 262603, 280323, 283357, 285440, 292739, 293594, 293594, 294948, 375300, 375953, 375956, 380759) + update debian/copyright accordingly. * Python policy last touch: + do not use dh_python anymore. + .pyc are handled correctly (Closes: #133306). * Bump DH_COMPAT to 5. * Ensure ucf is here before purging in postrm (Closes: #315174). * apt-listchanges new translations: + Traditional Chinese thanks to Kanru Chen (Closes: #297242). + Czech thanks to Miroslav Kure (Closes: #327508). * apt-listchanges templates po: + Portuguese templates thanks to Miguel Figueiredo (Closes: #330195). + Swedish update thanks to Daniel Nylander (Closes: #332443, 375748). + Japanese update thanks to Junichi Uekawa (Closes: #318499). + Vietnamese thanks to Clytie Siddall (Closes: #308744). * BTS Patches: + Make more strings translateable thanks to Junichi too (Closes: #318496). + Fix pot file generation (Closes: #318498, 302548). + Fix frontend=none behaviour thanks to Colin Watson (Closes: #341845). Files: a01cf877d67a76934fb179c32073087d 651 utils optional apt-listchanges_2.60.dsc 2dde74cf7be4e8836aa76a5930e641f0 80523 utils optional apt-listchanges_2.60.tar.gz 52eabd8d056d655762b47ac2f3c2c945 54290 utils optional apt-listchanges_2.60_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE21/PvGr7W6HudhwRAmCBAKCfFoqehxyzzcaQS8dsxrcldYOtBwCgmJv/ X5aGLaVehbRFKkaxtdCl4lM= =mWpB -END PGP SIGNATURE- Accepted: apt-listchanges_2.60.dsc to pool/main/a/apt-listchanges/apt-listchanges_2.60.dsc apt-listchanges_2.60.tar.gz to pool/main/a/apt-listchanges/apt-listchanges_2.60.tar.gz apt-listchanges_2.60_all.deb to pool/main/a/apt-listchanges/apt-listchanges_2.60_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rails 1.1.5-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 10:50:13 -0500 Source: rails Binary: rails Architecture: source all Version: 1.1.5-1 Distribution: unstable Urgency: emergency Maintainer: Adam Majer [EMAIL PROTECTED] Changed-By: Adam Majer [EMAIL PROTECTED] Description: rails - MVC ruby based framework geared for web application development Closes: 382255 Changes: rails (1.1.5-1) unstable; urgency=emergency . * New upstream release + Fixes a remote security hole [Bugtraq 19454] (closes: #382255) Files: 8d794d7e7983d8da4b5bda9f645f05da 607 web optional rails_1.1.5-1.dsc 45b86018f6e9580a1cecc48d3ff70e3f 1217259 web optional rails_1.1.5.orig.tar.gz 8b766e9266466bbe1d625d5c9e33cae4 12204 web optional rails_1.1.5-1.diff.gz 3b9b1d4342412d05693c507e8cda9a16 1775080 web optional rails_1.1.5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE21gO73/bNdaAYUURAhpXAKDYWrf2kvm3ZWHKPLt07VOUGx31YgCeMYVJ IgHPL64O1qq3NCnqJ6l7w+g= =8sED -END PGP SIGNATURE- Accepted: rails_1.1.5-1.diff.gz to pool/main/r/rails/rails_1.1.5-1.diff.gz rails_1.1.5-1.dsc to pool/main/r/rails/rails_1.1.5-1.dsc rails_1.1.5-1_all.deb to pool/main/r/rails/rails_1.1.5-1_all.deb rails_1.1.5.orig.tar.gz to pool/main/r/rails/rails_1.1.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted elfutils 0.122-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Aug 2006 19:21:05 + Source: elfutils Binary: libasm-dev libdw-dev elfutils libelf1 libasm1 libelf-dev libebl-dev Architecture: source amd64 Version: 0.122-3 Distribution: unstable Urgency: low Maintainer: Kurt Roeckx [EMAIL PROTECTED] Changed-By: Kurt Roeckx [EMAIL PROTECTED] Description: elfutils - collection of utilities to handle ELF objects libasm-dev - libasm development libraries and header files libasm1- library with a programmable assembler interface libdw-dev - library that provides access to the DWARF debug information libebl-dev - static library providing higher-level ELF access functionality libelf-dev - libelf1 development libraries and header files libelf1- library to read and write ELF files Changes: elfutils (0.122-3) unstable; urgency=low . [ Kurt Roeckx ] * Add build dependency on bzip2, so that all the regression tests can run. * elflint: Add EM_ALPHA to valid_e_machine. . [ Christian Aichinger] * Add retval to the sparc backend. * Ignore testsuite failures that elflint reports. * readelf should check destshdr instead of shdr. * Fix alignment problems in libdw_alloc seen on sparc. Files: f54263736a663118544d3704d09a3f5b 741 libs optional elfutils_0.122-3.dsc de1f64a0f3758d32737c7867aadc215a 124069 libs optional elfutils_0.122-3.diff.gz 4985427b3ce9a01a27082190237e1c0f 437406 utils optional elfutils_0.122-3_amd64.deb 5db258d12ff52cf66a5d810e24fb5373 38816 libs optional libelf1_0.122-3_amd64.deb 8a3f3c37d4e4aea56270d19f0e58cded 56128 libdevel optional libelf-dev_0.122-3_amd64.deb bf7c8d99bf31142bb1dcb672605d1437 48358 libdevel optional libebl-dev_0.122-3_amd64.deb bec1100ae43208d5e5bd7f1ffc105963 82448 libdevel optional libdw-dev_0.122-3_amd64.deb 60d5d705244abd8e97824ff10e8f4753 17970 libs optional libasm1_0.122-3_amd64.deb 82365b0a2e34c8e11e12ade9b26079d9 20726 libdevel optional libasm-dev_0.122-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE223qQdwckHJElwsRAvGoAJ9zHeK6tIxsAhBk8dw9s1c/kJg0WwCgwyZS to9y4+W9ymW6jqxfCgE7+hw= =pX2B -END PGP SIGNATURE- Accepted: elfutils_0.122-3.diff.gz to pool/main/e/elfutils/elfutils_0.122-3.diff.gz elfutils_0.122-3.dsc to pool/main/e/elfutils/elfutils_0.122-3.dsc elfutils_0.122-3_amd64.deb to pool/main/e/elfutils/elfutils_0.122-3_amd64.deb libasm-dev_0.122-3_amd64.deb to pool/main/e/elfutils/libasm-dev_0.122-3_amd64.deb libasm1_0.122-3_amd64.deb to pool/main/e/elfutils/libasm1_0.122-3_amd64.deb libdw-dev_0.122-3_amd64.deb to pool/main/e/elfutils/libdw-dev_0.122-3_amd64.deb libebl-dev_0.122-3_amd64.deb to pool/main/e/elfutils/libebl-dev_0.122-3_amd64.deb libelf-dev_0.122-3_amd64.deb to pool/main/e/elfutils/libelf-dev_0.122-3_amd64.deb libelf1_0.122-3_amd64.deb to pool/main/e/elfutils/libelf1_0.122-3_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted resolvconf 1.36 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 9 Aug 2006 16:50:50 +0200 Source: resolvconf Binary: resolvconf Architecture: source all Version: 1.36 Distribution: unstable Urgency: low Maintainer: resolvconf maintainers [EMAIL PROTECTED] Changed-By: Marco Nenciarini [EMAIL PROTECTED] Description: resolvconf - nameserver information handler Closes: 380119 Changes: resolvconf (1.36) unstable; urgency=low . [ D.K. Gillmor / TH ] * Update dnscache update script to handle runit too. (Closes: #380119) . [ Marco Nenciarini / TH ] * Modified postinst and prerm scripts to use invoke-rc.d if available * Bumped standards version to 3.7.2.1 Files: 848e31de70cdc943660e655195a6869b 736 net optional resolvconf_1.36.dsc c40da12cb104238a0fddf9f6396ebcf7 67552 net optional resolvconf_1.36.tar.gz 250fbb3c00a3ea95fcb22406d664ab74 59964 net optional resolvconf_1.36_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE22cqaGRzDfCV5eQRAptxAJ4pz4LXn1iXHs+9qh0xUYA60LbdqQCcCsFr k9clzUqcPGxxnRHP1gF5j9E= =Bk0H -END PGP SIGNATURE- Accepted: resolvconf_1.36.dsc to pool/main/r/resolvconf/resolvconf_1.36.dsc resolvconf_1.36.tar.gz to pool/main/r/resolvconf/resolvconf_1.36.tar.gz resolvconf_1.36_all.deb to pool/main/r/resolvconf/resolvconf_1.36_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted meld 1.1.3-1.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 19:02:41 +0200 Source: meld Binary: meld Architecture: source all Version: 1.1.3-1.1 Distribution: unstable Urgency: low Maintainer: Ross Burton [EMAIL PROTECTED] Changed-By: Pierre Habouzit [EMAIL PROTECTED] Description: meld - graphical tool to diff and merge files Closes: 380868 Changes: meld (1.1.3-1.1) unstable; urgency=low . * Non-maintainer upload. * Update package to the new python policy (Closes: #380868): + use dh_pysupport instead of dh_python. + remove custom postinst. * Bump Standards-Version to 3.7.2. * Fix B-D versus B-D-I for cdbs, and debhelper. Files: b78b92e9e2238202e9232de80f206b43 639 gnome optional meld_1.1.3-1.1.dsc afc632f1cc1501bf6813419ea47e466c 4366 gnome optional meld_1.1.3-1.1.diff.gz 03e9f839473e2d84e719b6112fa6b539 627426 gnome optional meld_1.1.3-1.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE22h/vGr7W6HudhwRAuPWAKCduVOafvideSKkVL4QEumya2v7mwCghJvW kyQNcRoGVZOlK4TTOgo5wfQ= =dUPr -END PGP SIGNATURE- Accepted: meld_1.1.3-1.1.diff.gz to pool/main/m/meld/meld_1.1.3-1.1.diff.gz meld_1.1.3-1.1.dsc to pool/main/m/meld/meld_1.1.3-1.1.dsc meld_1.1.3-1.1_all.deb to pool/main/m/meld/meld_1.1.3-1.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dspam 3.6.8-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 6 Aug 2006 10:50:44 -0400 Source: dspam Binary: libdspam7-dev libdspam7-drv-pgsql dspam libdspam7-drv-mysql dspam-webfrontend dspam-doc libdspam7-drv-db4 libdspam7 libdspam7-drv-sqlite3 Architecture: source i386 all Version: 3.6.8-2 Distribution: unstable Urgency: low Maintainer: Debian DSPAM Maintainers [EMAIL PROTECTED] Changed-By: Debian DSPAM Maintainers [EMAIL PROTECTED] Description: dspam - is a scalable, fast and statistical anti-spam filter dspam-doc - Documentation for dspam dspam-webfrontend - DSPAM is a scalable and statistical anti-spam filter libdspam7 - DSPAM is a scalable and statistical anti-spam filter libdspam7-dev - DSPAM is a scalable and statistical anti-spam filter libdspam7-drv-db4 - DSPAM is a scalable and statistical anti-spam filter libdspam7-drv-mysql - DSPAM is a scalable and statistical anti-spam filter libdspam7-drv-pgsql - DSPAM is a scalable and statistical anti-spam filter libdspam7-drv-sqlite3 - DSPAM is a scalable and statistical anti-spam filter Closes: 380138 381253 381395 Changes: dspam (3.6.8-2) unstable; urgency=low . [ Debian DSPAM Maintainers ] * Polish the manpages a bit. * Updated fsf address. * Updated lintian override for postgresql driver. . [ Daniel Kahn Gillmor ] * added doc/relay.txt to dspam-doc. Thanks to Micah Anderson (Closes: #381253) * added patches/fix-tag-class.dpatch (Closes: #381395) * added manpage for cssconvert. . [ Matthijs Mohlmann ] * added auto-config.h and pref.h to libdspam7-dev. (Closes: #380138) Files: ce7efb862fe27f024daa41188a0221cd 1123 mail optional dspam_3.6.8-2.dsc b81d221d939bfb5d09bc3cb93ab11bcc 52347 mail optional dspam_3.6.8-2.diff.gz 1811a48d5e87722927066c515565c08c 325028 mail optional dspam_3.6.8-2_i386.deb 4081030b5de8219f95206d6c4ab60942 109346 libs optional libdspam7_3.6.8-2_i386.deb cb068d30babd3fab42f28fc9adebca09 125418 mail optional libdspam7-dev_3.6.8-2_i386.deb dcd5cb36a790665083642a8edf709e71 103326 mail optional libdspam7-drv-pgsql_3.6.8-2_i386.deb 064768273183cd587a30e48d29ec9787 95104 mail optional libdspam7-drv-mysql_3.6.8-2_i386.deb 542233afe5f1768f55d629d232d6800d 70444 mail optional libdspam7-drv-db4_3.6.8-2_i386.deb 1426cc1f7497cd5cb686133ec70f6bb1 83992 mail optional libdspam7-drv-sqlite3_3.6.8-2_i386.deb ded68054d13bc5f4f401ed3f22b74210 109542 mail optional dspam-webfrontend_3.6.8-2_all.deb 4368467a2c63accecf136c0421ce1c6f 93290 doc optional dspam-doc_3.6.8-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE23qOZvwdf4aUbWkRApGuAKDY6YtgrVevZlnwsa6lTbBhCK7hpQCfZJ5R NPFqT8GxeUWnXovpD2Nezkk= =mctA -END PGP SIGNATURE- Accepted: dspam-doc_3.6.8-2_all.deb to pool/main/d/dspam/dspam-doc_3.6.8-2_all.deb dspam-webfrontend_3.6.8-2_all.deb to pool/main/d/dspam/dspam-webfrontend_3.6.8-2_all.deb dspam_3.6.8-2.diff.gz to pool/main/d/dspam/dspam_3.6.8-2.diff.gz dspam_3.6.8-2.dsc to pool/main/d/dspam/dspam_3.6.8-2.dsc dspam_3.6.8-2_i386.deb to pool/main/d/dspam/dspam_3.6.8-2_i386.deb libdspam7-dev_3.6.8-2_i386.deb to pool/main/d/dspam/libdspam7-dev_3.6.8-2_i386.deb libdspam7-drv-db4_3.6.8-2_i386.deb to pool/main/d/dspam/libdspam7-drv-db4_3.6.8-2_i386.deb libdspam7-drv-mysql_3.6.8-2_i386.deb to pool/main/d/dspam/libdspam7-drv-mysql_3.6.8-2_i386.deb libdspam7-drv-pgsql_3.6.8-2_i386.deb to pool/main/d/dspam/libdspam7-drv-pgsql_3.6.8-2_i386.deb libdspam7-drv-sqlite3_3.6.8-2_i386.deb to pool/main/d/dspam/libdspam7-drv-sqlite3_3.6.8-2_i386.deb libdspam7_3.6.8-2_i386.deb to pool/main/d/dspam/libdspam7_3.6.8-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gettext 0.15-0 (source all powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 20:39:56 +0200 Source: gettext Binary: gettext-doc gettext gettext-base gettext-el Architecture: source all powerpc Version: 0.15-0 Distribution: experimental Urgency: low Maintainer: Santiago Vila [EMAIL PROTECTED] Changed-By: Santiago Vila [EMAIL PROTECTED] Description: gettext- GNU Internationalization utilities gettext-base - GNU Internationalization utilities for the base system gettext-doc - Documentation for GNU gettext gettext-el - Emacs po-mode for editing .po files Changes: gettext (0.15-0) experimental; urgency=low . * Test release for experimental. Files: 08f26e3e71c0e90d949e2960f6e457fc 685 devel optional gettext_0.15-0.dsc 16bc6e4d37ac3d07495f737a2349a22b 8081941 devel optional gettext_0.15.orig.tar.gz 939700a93277fe8227c9761b54938512 20754 devel optional gettext_0.15-0.diff.gz 2d35c792c30aa4924c6ace18189e3561 56970 devel optional gettext-el_0.15-0_all.deb b2955a59f482c6ded42a5adce60dfb6a 801554 doc optional gettext-doc_0.15-0_all.deb 91f5389c73653325ad61b6f8fc024694 124002 utils standard gettext-base_0.15-0_powerpc.deb 9577ada1ad674b5d53b634c1861447d2 2007398 devel optional gettext_0.15-0_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE23+Gd9Uuvj7yPNYRApQhAKDO1vtm6uUAxtas4sFrijBbvCxBzQCeL8vu 1qApQNy3hnfYL/yV35Ty2/k= =FLEh -END PGP SIGNATURE- Accepted: gettext-base_0.15-0_powerpc.deb to pool/main/g/gettext/gettext-base_0.15-0_powerpc.deb gettext-doc_0.15-0_all.deb to pool/main/g/gettext/gettext-doc_0.15-0_all.deb gettext-el_0.15-0_all.deb to pool/main/g/gettext/gettext-el_0.15-0_all.deb gettext_0.15-0.diff.gz to pool/main/g/gettext/gettext_0.15-0.diff.gz gettext_0.15-0.dsc to pool/main/g/gettext/gettext_0.15-0.dsc gettext_0.15-0_powerpc.deb to pool/main/g/gettext/gettext_0.15-0_powerpc.deb gettext_0.15.orig.tar.gz to pool/main/g/gettext/gettext_0.15.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aspell-de-alt 2.1-1-5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 10 Aug 2006 21:08:00 +0200 Source: aspell-de-alt Binary: aspell-de-alt Architecture: source all Version: 2.1-1-5 Distribution: unstable Urgency: low Maintainer: Christoph Berg [EMAIL PROTECTED] Changed-By: Christoph Berg [EMAIL PROTECTED] Description: aspell-de-alt - German dictionary for aspell (old spelling) Changes: aspell-de-alt (2.1-1-5) unstable; urgency=low . * Unset LANG in preinst for update-alternatives output (see #382335). Files: f44dda15097b6789aec202cbbd118102 662 text optional aspell-de-alt_2.1-1-5.dsc 9945155ba0ce8df2ab97f15bc2e186da 3404 text optional aspell-de-alt_2.1-1-5.diff.gz b1ba07bae5be2c0dd6192b2f1e070dd5 295398 text optional aspell-de-alt_2.1-1-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE24Zfxa93SlhRC1oRAlaTAJ0ezhIRFl++V+aYQcixY6huBOnJcACg0VMo oVUVnzb5tPd8iLArvJVR/+I= =tR0f -END PGP SIGNATURE- Accepted: aspell-de-alt_2.1-1-5.diff.gz to pool/main/a/aspell-de-alt/aspell-de-alt_2.1-1-5.diff.gz aspell-de-alt_2.1-1-5.dsc to pool/main/a/aspell-de-alt/aspell-de-alt_2.1-1-5.dsc aspell-de-alt_2.1-1-5_all.deb to pool/main/a/aspell-de-alt/aspell-de-alt_2.1-1-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
