Recherche d'un outils avant de créer un nouveau paquet Debian
Cher Développeurs Debian, Avant de commencer la création d'un nouveau paquet, je souhaiterais vous solliciter pour savoir si un équivalent ne serait pas déjà existant. L'objectif de cet outils est très similaire au fonctionnement des Initscripts du System-V Ce programme du style initd (appelons-le ainsi) pourrait accepter la syntaxe suivante: initd [DIRECTORY] [OPTION] ... [DIRECTORY] = répertoire contenant des scripts (pas des scripts de type démons) [OPTION] = commande à envoyer aux démons A quoi me sert-il ? Mon fournisseur a créé une application reposant sur une suite de scripts non construite sur un modèle de démon. Pour démarrer cette application, je dois par conséquent lancer chaque script dans un ordre bien défini. Pour arréter l'application, je dois tuer chaque processus dans l'ordre inverse. Avec cette idée de initd, je pourrais controler l'initialisation de toute l'application seulement avec une seule commande (très utile car elle doit fonctionner avec DRBD) Est-ce que ce programme du style initd exist déjà ? Sinon, I pense utiliser les outils run-parts et start-stop-deamon pour créer mon programme. Quel nom conviendrait le mieux à cet outils ? Initialize Directory as Daemons : initdd, initd, dinit ? Merci pour votre aide ou pour votre point de vue et vos réflexions. Bonne soirée. Salokine. ([EMAIL PROTECTED]) PS: Une copie traduite est aussi postée sur [EMAIL PROTECTED] (http://lists.debian.org/debian-mentors/2007/05/msg00210.html) pgpdSfptyEaHI.pgp Description: PGP signature
Re: Debian base system package list
hi carlos, On Mon, 2007-05-14 at 22:33 -0700, Carlos Ramirez wrote: Is a file, webpage or command that can provide a list of packages that are part of the Debian base system? I tried searching in various places without much luck. Any help in the right direct is appreciated. the easiest way: apt-get install grep-dctrl and then do something like: grep-aptavail -F Essential yes -o -F Priority required -s Package or grep-aptavail -F Essential yes -o -F Priority required -o \ -F Priority standard -s Package depending on what it is exactly that you want (the fine manpage has more info). if you want all the packages part of a basic debian installation, the second one is probably closer. alternatively, you could run the installer, not select any software, and then run dpkg -l from the cmdline :) sean signature.asc Description: This is a digitally signed message part
Re: Debian base system package list
Sean, Thanks for the info. It seems that all those would give me the info I want. I was thinking that I would be able to get that info from the actual build files of the Debian distribution itself, does there exists such a beast? I'm trying to compile a list packages that are common to 'base systems' of various Linux distributions. I initially thought that the Linux Standard Base would provide that list but it only consists of lower level utilities/libraries and not software tools per se. Thanks again. -Carlos sean finney wrote: hi carlos, On Mon, 2007-05-14 at 22:33 -0700, Carlos Ramirez wrote: Is a file, webpage or command that can provide a list of packages that are part of the Debian base system? I tried searching in various places without much luck. Any help in the right direct is appreciated. the easiest way: apt-get install grep-dctrl and then do something like: grep-aptavail -F Essential yes -o -F Priority required -s Package or grep-aptavail -F Essential yes -o -F Priority required -o \ -F Priority standard -s Package depending on what it is exactly that you want (the fine manpage has more info). if you want all the packages part of a basic debian installation, the second one is probably closer. alternatively, you could run the installer, not select any software, and then run dpkg -l from the cmdline :) sean -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian base system package list
On Tuesday 15 May 2007 07:33, Carlos Ramirez wrote: Is a file, webpage or command that can provide a list of packages that are part of the Debian base system? I tried searching in various places without much luck. Any help in the right direct is appreciated. You could use debootstrap: debootstrap --arch i386 --print-debs \ etch /tmp/etch.$$ http://ftp.nl.debian.org/debian/ Cheers, FJP pgp5kPe8xqzIL.pgp Description: PGP signature
Re: Bug#423911: ITP: citadel -- Citadel.org is an highly integrated Groupware Platform with a Web 2.0 enabled Webinterface, but also providing SMTP, IMAP, POP3 and GroupDAV access to its content.
Hello! On Tue, May 15, 2007 at 12:09:30AM +0100, Stephen Gran wrote: This one time, at band camp, Wilfried Goesgens said: * Package name: citadel ... However, I have one question that has made me leery of it so far: does it really need it's own implementation of all of those protocols? AFAIK yes, since that is Citatels benefit: It gives access to the same data by different protocols; no nightmare because of inconsistent data between all those parts. Can't it use existing, well tested, pop/imap/smtp servers? No. And that's why I didn't pick it for production, since I didn't want to replace my working Postfix + Cyrus-IMAP setup. BYtE Philipp -- Philipp Matthias Hahn [EMAIL PROTECTED] GPG/PGP: 9A540E39 @ keyrings.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Hi, Ad backports importance, I know there is backports.org -however this, and the testing, unstable, stable, volatile, experimental.. So many package versions, so much duplicate work.. Other hand, there's nothing official and recommended excepting the stable. Using anything else, You're on Your own.. I think, any new stable version of the desktop software should be automaticaly added to security updates and distributed to end user. There's no need to test the tested and stabilise the stable software. Should the new stable version be broken, let's give the user easy way to downgrade, and help upstream to fix it fast. I can agree with You in some point -Yes, compiling against the, let's call it stable base, as I suggested before, could also mean real backporting work, especially if the upstream moved to higher libraries versions in the middle of Debian's release cycle. That's why i think the backport's people are _very_important_ in the proposed scheme. Moreover, I could suggest the backporting work to be moved closer to upstream and further from Debian itself. Other distros do lot of backport work too, so working together somewhere in the upstream's playground could bless all together. PS. I know the text is long. I can work on bulleted version. Is there any interest? Peter Petter Reinholdtsen wrote / napísal(a): [Peter Tuharsky] Ask somebody, what distro would he install at desktop for novice or M$ refugee? Why many are choosing Ubuntu instead of Debian, and even worse, abandon Debian in favor of Ubuntu? Why do most people consider Debian to be user-unfriendly and server-oriented distro? Interesting analysis, with several good points on keeping the stable release working with newer hardware and keeping the software selection relevant. But my first impression after reading your long text is that you are ignoring the work going on at backports.org, and the ideas that has been floating around on making a Debian release based on the stable version for the base packages, and include upgraded packages like the kernel, X, Gnome, KDE and other hardware- and user-interacting packages from backports.org. You might want to have a look into those ideas. I've also seen ideas on making releases based on testing, now that we have security fixes for the packages in testing. It could give a snapshot of internally consistent packages (as opposed to unstable). Friendly, -- Odchádzajúca správa neobsahuje vírusy, nepou¾ívam Windows. === Mgr. Peter Tuhársky Referát informatiky Mesto Banská Bystrica ÈSA 26 975 39 Banská Bystrica Tel: +421 48 4330 118 Fax: +421 48 411 3575 === -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
The kernel, the X.org I realise, that the kernel and X.org are somewhat delicate things, because they affect both desktop and server. Changing them in the middle of release life, might not sound too well. However, at least by the means of the kernel, the server world also needs new hardware support. Putting Debian on the server could get hard in the second half of release cycle. Fortunately, upgrading the kernel dosen't break anything usually, as long as there is not some nasty bug in there. I suggest the kernel to follow the stable tree at kernel.org, with caution of course. If the kernel version upgrade was available eq 2 times inside stable release life, those willing to upgrade could use it, and those unvilling can stay with old version. The kernel upgrade could fit the volatile philosophy IMO. As of X, it's quite complex, however it's less the server and more the desktop thing, that could also get upgraded with some caution. Might also be the concern of volatile. Some server software occasionaly need an upgrade too. However the ordinary desktop packages, environments and so on could get upgraded routinely IMO, with easy downgrade option. No need to do the whole stabilisation scrutiny. If some developer wishes to test the package before putting it to the repositories, he can join the upstream's beta testing to help catch the bugs before the software is stabilised upstram. Peter Petter Reinholdtsen wrote / napísal(a): [Peter Tuharsky] Ask somebody, what distro would he install at desktop for novice or M$ refugee? Why many are choosing Ubuntu instead of Debian, and even worse, abandon Debian in favor of Ubuntu? Why do most people consider Debian to be user-unfriendly and server-oriented distro? Interesting analysis, with several good points on keeping the stable release working with newer hardware and keeping the software selection relevant. But my first impression after reading your long text is that you are ignoring the work going on at backports.org, and the ideas that has been floating around on making a Debian release based on the stable version for the base packages, and include upgraded packages like the kernel, X, Gnome, KDE and other hardware- and user-interacting packages from backports.org. You might want to have a look into those ideas. I've also seen ideas on making releases based on testing, now that we have security fixes for the packages in testing. It could give a snapshot of internally consistent packages (as opposed to unstable). Friendly, -- Odchádzajúca správa neobsahuje vírusy, nepou¾ívam Windows. === Mgr. Peter Tuhársky Referát informatiky Mesto Banská Bystrica ÈSA 26 975 39 Banská Bystrica Tel: +421 48 4330 118 Fax: +421 48 411 3575 === -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian base system package list
On Tue, 15 May 2007 08:19:50 +0200, sean finney wrote: On Mon, 2007-05-14 at 22:33 -0700, Carlos Ramirez wrote: Is a file, webpage or command that can provide a list of packages that are part of the Debian base system? I tried searching in various places without much luck. Any help in the right direct is appreciated. Some poiking about in apt's Packages list as described by sean will do the trick, although there is also a 'Priority: important' level, which I assume is installed by default along with required packages. If the user opts to activate any 'tasks' during installation then even more packages will be installed. See '/usr/share/tasksel/debian- tasks.desc' for the list of tasks, and '/usr/share/doc/tasksel/README.gz' to see how to interpret the contents of the debian-tasks.desc file. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian base system package list
On Tuesday 15 May 2007 11:36, Sam Morris wrote: Some poiking about in apt's Packages list as described by sean will do the trick, although there is also a 'Priority: important' level, which I assume is installed by default along with required packages. Priority important packages are part of the base system. For a normal install, packages with Priority standard will be installed as well as the Standard system task is selected by default. The Standard system task is somewhat different from other tasks as it is based on the priority of packages instead of a list of packages. The real base system is a fairly bare-bones system. pgpTnGTeuB24O.pgp Description: PGP signature
Re: Liability protection project - call for participants
Hi, On Tue, 15.05.2007 at 18:11:03 +1000, Anthony Towns [EMAIL PROTECTED] wrote: On Mon, May 14, 2007 at 03:51:40PM -0700, Bruce Perens wrote: Some of us have homes, and other property that we would rather not place at risk of any lawsuit connected with our Free Software activities. The way to do that is to act as a volunteer on the behalf of a non-profit corporation, with the corporation assuming your liability. [...] owns property that we do not want to expose to liability. Copyrights of software produced would be assigned to a non-profit like FSF or SPI* That said, giving up a little autonomy in exchange for potentially a lot of financial security is an entirely sensible tradeoff to consider, and it makes a lot of sense to do that before people start getting sued individually. It might be possible to do something like have SPI get copyright assignment for works in return for providing the authors with a vote (or a voice) on how they handle that copyright in future, which might ease the concerns about handing over control and could even be argued to be a work for hire arrangement making it a bit easier to deal with legally. I'm unconvinced that such copyright assignments can be done in a way that avoids creating an asset - in the form of the software - that the bad boys can go after. Eg. IFF they (hypthetically) were to successfully sue the FSF, then we'd lose a large chunk of important stuff because the copyrights held by the FSF will probably be confiscated in order to pay the damages. I'm also unsure that there are no ways to extend such a liability if the contracts come to be work for hire style or similar. Example: DDs work for company A which directs them to do something, and company B assumes all the benefits (the copyrights), specified that way in the contract between some DD and company A. I'm not sure that such a contract would prevent company B from being disowned in such a case. Best, --Toni++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Merging packages
Andreas Metzler [EMAIL PROTECTED] wrote: Luis Rodrigo Gallardo Cruz [EMAIL PROTECTED] wrote: [...] Also, some people might be relaying in the file's current location for something. Should I put a symlink in their place? Just a warning: Symlinks that are shipped in the deb and point to conffiles (not just directories) are not a good idea. bug #420578 Oh, since your statement confused me a bit, but reading the bug log clarified it: The problem is not with any symlink pointing to conffiles, in particular not with the common case of fixing non-FHS-aware applications by creating symlinks from /usr/share/ to /etc. The problem is specifically with symlinks from /etc to some other place in /etc, and is caused by the fact that debhelper does not mark symlinks in /etc as conffiles. Has this aspect been discussed with the debhelper maintainer? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Re: Liability protection project - call for participants
Does all this project involve only proper Debian Developers, or also people who are maintaining Debian packages without being full Debian Developers? Also, we're only talking about Developers who live in the USA, or that have that nationality, aren't we? Greetings, Miry
Re: Liability protection project - call for participants
Toni Mueller [EMAIL PROTECTED] wrote: [...] Eg. IFF they (hypthetically) were to successfully sue the FSF, then we'd lose a large chunk of important stuff because the copyrights held by the FSF will probably be confiscated in order to pay the damages. [...] Even if that is the case (what is the precedent?), then we would not lose much because as far as I know, FSF grants a perpetual all-permissions license back to the original author of the copyright- assigned work. We'd only lose the ability to defend copyright infringment on the stuff, but if the FSF has been successfully sued, then we've arguably lost a big chunk of that anyway. Other than maybe making some GPL code effectively BSD-like for whoever sued FSF, the winner would gain nothing except the ability to police some of our code for us. FSF has its faults, but this aspect looks pretty clever to me. Hope that explains, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Hi, Thank you for sharing your point of view. But you draw too many conclusions. You speak out of rumors and experience and you fail to understand that Debian is not a Desktop-only distribution. Get involved and learn our development process, you'll discover that you can't rely on many assumptions that you made. On Tue, 15 May 2007, Mgr. Peter Tuharsky wrote: in my experience, testing is not really good option for real work. There are _platform_ changes going in testing, that leads to broken dependencies and sometimes completely nonfunctional snapshots. Testing is usable. I used it through the whole development cycle of etch. Bugs are unavoidable, you said it yourself. It's a matter of how many problems you can accept. Therefore, I suggest _the_platform_ (libraries and so on) to remain stable, just upgrade the software that runs on top of that. Thus we can both avoid broken deps problems, and have new software available. In the Debian context, Gnome is a platform. It's not only software that runs on top of libc6. Gnome represent dozens of libraries that are used by hundreds of applications. You can't just get the latest version and hope that it won't break anything. If You mean to use the software from testing -You must first make it run on stable without need for library upgrades. That is more similar to backports job, than to testing. You can't backport everything if you don't want to upgrade libraries. It's simply not doable without rewriting the application. Testing should simply be the place where _platform_ changes are shaken out, not the input buffer for the new software. Actually sid is where the platform changes are done. And once they're OK, they get moved to testing in a coherent manner. So testing should stay usable. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Hi, Raphael Testing is usable. I used it through the whole development cycle of etch. Bugs are unavoidable, you said it yourself. It's a matter of how many problems you can accept. Yes, bugs are unavoidable. However, testing is often in situation whole system broken or nearly useless. I see difference here; occassional bug in desktop app is acceptable. Whole system unreliable is not acceptable. In the Debian context, Gnome is a platform. It's not only software that runs on top of libc6. Gnome represent dozens of libraries that are used by hundreds of applications. That's true. You can't just get the latest version and hope that it won't break anything. That should be verified in light of broad experience (I don't have any). Does it happen often that GNOME version change breaks many things? The only my try was to put GNOME 2.0 to Debian Woody (ugly GNOME 1.2), and I was succesful. If You mean to use the software from testing -You must first make it run on stable without need for library upgrades. That is more similar to backports job, than to testing. You can't backport everything if you don't want to upgrade libraries. It's simply not doable without rewriting the application. I think majority of software _should_ build w/o problem with ordinary libraries of maximum 2 years age. In my experience, apps are generally happy if libraries are not older than that. Of course, shorter release cycle could remove remaining problems in this order. Next stable release of Debian will of course upgrade the whole platform, including the versions, thus software would be happy for next 18 months. Testing should simply be the place where _platform_ changes are shaken out, not the input buffer for the new software. Actually sid is where the platform changes are done. And once they're OK, they get moved to testing in a coherent manner. So testing should stay usable. This is just a wish, not a common experience. Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
Hello, On Le Tuesday 15 May 2007, à 14:01:28, Raphael Hertzog wrote: Testing should simply be the place where _platform_ changes are shaken out, not the input buffer for the new software. Actually sid is where the platform changes are done. And once they're OK, they get moved to testing in a coherent manner. So testing should stay usable. And you can also look at [CUT][] which seems a project to fit well desktop user's needs. [CUT]: http://kitenet.net/~joey/code/debian/cut/ Constantly Usable Testing François Post Scriptum : [EMAIL PROTECTED] wrote in http://lists.debian.org/debian-user/2007/04/msg00427.html CUT was exactly what testing was supposed to be, in the beginning. Period. It hasn't become that. It has gotten to the point that sometimes testing is borkdened for long periods of time... in small areas mind you, but still broken. which I agree even in a lot of case testing is really usable -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Tuesday 15 May 2007 14:44, Mgr. Peter Tuharsky wrote: Yes, bugs are unavoidable. However, testing is often in situation whole system broken or nearly useless. I see difference here; occassional bug in desktop app is acceptable. Whole system unreliable is not acceptable. Can you substantiate that? In my experience it is not true. And even unstable is almost always usable if you know how to avoid temporary uninstability of packages and how to downgrade a package occasionally. Though I'd not advice running unstable to end users, I would happily suggest testing. Cheers, FJP pgpNJ1U7ciwY0.pgp Description: PGP signature
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Tue, 15 May 2007, Mgr. Peter Tuharsky wrote: Yes, bugs are unavoidable. However, testing is often in situation whole system broken or nearly useless. I see difference here; occassional bug in desktop app is acceptable. Whole system unreliable is not acceptable. Have you facts to assert this? I've been an happy user of testing. It happens that some packages are not upgradable during a timeframe however the installed packages are not broken and thus the system is perfectly reliable. You can't just get the latest version and hope that it won't break anything. That should be verified in light of broad experience (I don't have any). Does it happen often that GNOME version change breaks many things? The only my try was to put GNOME 2.0 to Debian Woody (ugly GNOME 1.2), and I was succesful. You can't generalize based on a single experience like that. Your restricted yourself to software published by the Gnome project. Check how many applications depend on Gnome and yet are not developed following Gnome's schedule. Those are the applications which have not been tested by upstream with the new Gnome and which are the more likely to break. You can't rely on upstream to do this testing for you. We have a purpose, we don't stabilize our distribution just because it sounds nice, it's really needed in many cases. Don't get me wrong however, I'm all in favor of having backports integrated in Debian and make it a viable alternative for many users. But you simply can't drop newer upstream version in what we call stable like you suggest. We don't really need more discussion on that topic. We need improvements to make that a realistic goal. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
We're going OT, however my experience based on last two Debian releases: testing becomes quite stable in means of usability somewhere half year before it's released as stable. The sooner before the stable, the rapidly increasing is the chance that the snapshot that You have will not be installable at all, will have dependencies severely broken, etc. That's why I suggest: focus on base platform, stabilise it, polish the dependencies. Then compile software against it and release it, compile newer version and release it, etc.. Desktop software itself shouldn't break dependencies. Peter Frans Pop wrote / napísal(a): On Tuesday 15 May 2007 14:44, Mgr. Peter Tuharsky wrote: Yes, bugs are unavoidable. However, testing is often in situation whole system broken or nearly useless. I see difference here; occassional bug in desktop app is acceptable. Whole system unreliable is not acceptable. Can you substantiate that? In my experience it is not true. And even unstable is almost always usable if you know how to avoid temporary uninstability of packages and how to downgrade a package occasionally. Though I'd not advice running unstable to end users, I would happily suggest testing. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Tue, 15 May 2007, Mgr. Peter Tuharsky wrote: We're going OT, however my experience based on last two Debian releases: testing becomes quite stable in means of usability somewhere half year before it's released as stable. The sooner before the stable, the rapidly increasing is the chance that the snapshot that You have will not be installable at all, will have dependencies severely broken, etc. The goal of testing is to be continuously installable with as few RC bugs as we can manage. In general, it approaches this goal closely enough to be usable almost constantly. That's why I suggest: focus on base platform, stabilise it, polish the dependencies. Then compile software against it and release it, compile newer version and release it, etc.. Desktop software itself shouldn't break dependencies. If only that were the case. Most of the bugs and pain in transition that we run into are not in the base system itself, but in everything else that people actually want to use on their Debian system. While I am glad that you are interested in making Debian better, you need to pitch in and become conversant with the problems that we actually have; only then will you be able to present solutions to those problems. Don Armstrong -- Any excuse will serve a tyrant. -- Aesop http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mysterious NMU (Bug #423455)
Roberto C. Sánchez [EMAIL PROTECTED] writes: On Mon, May 14, 2007 at 09:24:35AM +0200, Raphael Hertzog wrote: Maybe I misunderstand, but wouldn't something like (= 1.0.1-1) and ( 1.0.1-2) be more correct? That way the package is still binNMU safe and also safe from breaking if incompatibilities are introduced in the next source upload? Regards, -Roberto (= version) and ( next-version). The problem is knowing next-version. 1.0.1-2 is not the next version. For example a NMU of 1.0.1-1.1 is less. Also 1.0.1-1lenny1 (security update for lenny) is less than 1.0.1-2. There could also be an 1.0.1-2~rc1, again less than 1.0.1-2. And now for something really ugly: % dpkg --compare-versions 1.0.1-1lenny1 1.0.1-1+b1 echo yes yes So a security upload of the package has a smaller version than a binNMU upload. At that point you are pretty much screwed. One way around the problem is Package: foo-any Provides: foo-any-source-version Package: foo-all Depends: foo-any-source-version MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mysterious NMU (Bug #423455)
On Tue, May 15, 2007 at 03:49:07PM +0200, Goswin von Brederlow [EMAIL
PROTECTED] wrote:
Roberto C. Sánchez [EMAIL PROTECTED] writes:
On Mon, May 14, 2007 at 09:24:35AM +0200, Raphael Hertzog wrote:
Maybe I misunderstand, but wouldn't something like (= 1.0.1-1) and (
1.0.1-2) be more correct? That way the package is still binNMU safe and
also safe from breaking if incompatibilities are introduced in the next
source upload?
Regards,
-Roberto
(= version) and ( next-version).
The problem is knowing next-version. 1.0.1-2 is not the next
version. For example a NMU of 1.0.1-1.1 is less. Also 1.0.1-1lenny1
(security update for lenny) is less than 1.0.1-2. There could also be
an 1.0.1-2~rc1, again less than 1.0.1-2.
A rule that works pretty good:
= ${source:Version} and = ${source:Version}.1~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Mon, May 14, 2007 at 02:55:40PM +0200, Mgr. Peter Tuharsky [EMAIL PROTECTED] was heard to say: Debian developers often see Ubuntu the enemy and are mocking it as inferior technology. However, they fail to see, what does the Debian really offer to desktop users eventually. They fail to understand, why are they using Ubuntu happily and reference it to novices. It seems, that desktop users don't see Debian fitting their needs. What are the means? When you talk about desktop users, I think you really mean novice consumers. Is that a fair assessment? In my experience, Debian can work just fine on the desktop in some situations, just not for novice home users. (think, e.g., about desktops for office workers) b, Stability It simply depends on, well, luck on choosing the particulary good version of software. With stable upstream versions of software, there should not be major stability issues anyhow. Debian proclaims to offer excellent stability. However, if some application does have stability issues, users must wait at least 2 years for next stable version of Debian to see the fix. The stability is not automatically guaranteed by oldness of software and lack of upgrades in Debian. The word stable with regard to Debian's repositories doesn't mean works without bugs. Every piece of software has bugs, and in general, if a newer version of the software appears to have less bugs, that's a reflection of the fact that there's been less time for people to report the bugs it contains. Debian stable is stable in the sense of solid rock versus shifting sands: we ensure that the behavior of the system won't change during a stable cycle. There might be bugs in it, but they'll be the same bugs throughout stable's lifetime. Why would you want this? In a setting where you have people doing productive work using a piece of software, unnecessary changes to the software are *worse* in the short term than a fixed and unchangable set of bugs: not only are changes likely to break the software, but they may require users to retrain or disrupt the processes of your organization. This is true even if the new software is an unqualified improvement (either in terms of bug count or usability) over the old software; look at the backlash over the new Ribbon interface in Microsoft office, for instance. Having briefly overseen a small network of Debian systems for a research group, my sense is that an 18-month cycle would work well in this setting; anything shorter than a year would be too disruptive. I await correction from more experienced members of this list who can tell me I'm full of it. :) Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Ensuring complete upgrades in applications with multiple binary packages
Hi, we've run across a problem with our texlive packages, and I'd like to get some opinions, in particular regarding dpkg behavior. TeX Live is one big thing upstream (one DVD) and has been split for Debian packaging into one arch:any and four arch:all source packages with numerous binary packages each. Generally, you cannot assume a system to work properly which has a mixture of different upstream versions of these packages installed. But how should we achieve that? A. The straightforward approach is the most ugly one: The packages of course frequently declare Depends: texlive-some-other-package, and we could switch all of these depends into versioned depends, (= $upstream-version). But that would really look ugly, e.g. from texlive-latex-extra: -Depends: preview-latex-style, texlive-common (= 2007), texlive-pictures, texlive-latex-base +Depends: preview-latex-style, texlive-common (= 2007), texlive-pictures (= 2007), texlive-latex-base (= 2007) It would require a really big change to our internal packaging scripts to add such version restrictions only where a real incompatibility shows up, so it would have to be each of them. B. texlive-common could declare Conflicts: long_list_of_texlive_packages_each_with_old_upstreamversion But how would that work upon upgrade? Technically, there's no problem, first all texlive packages except texlive-common would be unpacked, then texlive-common could be unpacked and configured, after that the others can be configured. But usually dpkg tries to do unpacking and configuring in the same order; would it be confused by this situation? C. Ignore the problem and just expect from users to handle their upgrades in a sane way and not put individual packages on hold? Of course, other reasons like unrelated errors during dist-upgrade might also cause version mixes, but again the sane thing to do would be to run dist-upgrade again, and not try to use the packages or report a bug... Comments? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Re: Bug#423911: ITP: citadel -- Citadel.org is an highly integrated Groupware Platform with a Web 2.0 enabled Webinterface, but also providing SMTP, IMAP, POP3 and GroupDAV access to its content.
On 14-May-07, 19:35 (CDT), Ron Johnson [EMAIL PROTECTED] wrote: On 05/14/07 17:23, Wilfried Goesgens wrote: Description : Citadel.org is an highly integrated Groupware Platform with a Web 2.0 enabled Webinterface, but also providing SMTP, IMAP, POP3 and GroupDAV access to its content. You don't need to put Citadel.org in the short description. And the short description should be limited to 50(?) characters. Also, there's no need to capitalize Groupware Platform, Webinterface should be web interface. Citadel offers Versatile email services with verry low administration needed. It provides its own implementations of these server protocols: Imap, Pop3, SMTP, ManageSieve, Citadel Versatile = versatile verry = very Imap = IMAP Pop3 = POP3 (Yes, small nit-picky changes.) Thanks, Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: print-system virtual package?
On 14-May-07, 14:40 (CDT), Andreas Fester [EMAIL PROTECTED] wrote: I was just investigating a bug where the issue seems that no print system is installed (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420746) That raised the question: would it make sense to add a virtual package like print-system or similar, which is provided by cupsys-client, lpr et al. and which I can suggest or recommend in my package? Well, given the specific error: $ qcad libcups.so: cannot open shared object file: No such file or directory I don't think you need a virtual depends, but instead an explicit Depends: cupsys-client. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mysterious NMU (Bug #423455)
On Tue, May 15, 2007 at 03:49:07PM +0200, Goswin von Brederlow wrote: Roberto C. Sánchez [EMAIL PROTECTED] writes: On Mon, May 14, 2007 at 09:24:35AM +0200, Raphael Hertzog wrote: Maybe I misunderstand, but wouldn't something like (= 1.0.1-1) and ( 1.0.1-2) be more correct? That way the package is still binNMU safe and also safe from breaking if incompatibilities are introduced in the next source upload? Regards, -Roberto (= version) and ( next-version). The problem is knowing next-version. 1.0.1-2 is not the next version. For example a NMU of 1.0.1-1.1 is less. Also 1.0.1-1lenny1 (security update for lenny) is less than 1.0.1-2. There could also be an 1.0.1-2~rc1, again less than 1.0.1-2. Yes, but in reality what is the likelihood that either a security update or NMU would introduce an incompatible change? I would say that such a possibility is extremely low. And now for something really ugly: % dpkg --compare-versions 1.0.1-1lenny1 1.0.1-1+b1 echo yes yes So a security upload of the package has a smaller version than a binNMU upload. At that point you are pretty much screwed. Perhaps the policy should change so that security uploads are done with x.y.z-(w++)~lenny1? That is, the Debian version number gets incremented. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Bug#424067: ITP: python-sasync -- asynchronous access for SQLAlchemy
Package: wnpp Severity: wishlist Owner: Eric Evans [EMAIL PROTECTED] * Package name: python-sasync Version : 0.4 Upstream Author : Edwin A. Suominen [EMAIL PROTECTED] * URL : http://foss.eepatents.com/sAsync * License : GPL Programming Lang: Python Description : asynchronous access for SQLAlchemy An enhancement to the SQLAlchemy package that provides asynchronous deferred-result access via the Twisted framework and an access broker for conveniently managing database access, table setup, and transactions. Included are modules for implementing persistent dictionaries, three-dimensional arrays, and graph objects. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (700, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Eric Evans [EMAIL PROTECTED] signature.asc Description: Digital signature
Call for tests: webcalendar 1.1.2-1
I just released webcalendar 1.1.2 to experimental. Although this version is considered to be a development version by the upstream author (1.0.5 is the recommended production release), it is good to have the 1.1.* branch in experimental, such that upgrade problems are detected before Webcalendar 1.2 comes out. The trickiest aspect of the package is indeed related to the upgrade of the SQL database via dbconfig-common. I have tested 1.0.5 - 1.1.2 migration using Apache an MySQL and the major problems seem to be fixed. However, there should be corner cases where the upgrade would fail. Hence the present Call for Tests. If you are a WebCalendar 1.0.* user, I would like to hear about your upgrading experiences. Also, tests results regarding PostgreSQL and SQLite are welcome. If you use another HTTP server than Apache or if you have webcalendar embedded into postnuke or joomla, I would like to know about your eventual problems. Note that the upgrade from 0.9.* should also be tested, but 0.9.45-4sarge7 was released in the pre-dbconfig-common era, so I am not sure whether we should also support automatic upgrade from that version. -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITP: bandwidthcalc -- file transfer time calculator written in GTK+
Hi, John Goerzen wrote: I guess I have to just ask: how useful is this? This is really a quite trivial calculation, and many apps/websites perform it automatically these days anyway. It's right, but rsync only display upload/download time for one file, even if You transfer 20 files. And what about people sitting in a closed network without access to Internet? Greetings, Christoph signature.asc Description: OpenPGP digital signature
Re: Mysterious NMU (Bug #423455)
On Tue, May 15, 2007 at 12:20:22PM -0400, Roberto C. S?nchez wrote: Yes, but in reality what is the likelihood that either a security update or NMU would introduce an incompatible change? I would say that such a possibility is extremely low. Why couldn't a security change require making incompatible changes to something? A bin NMU would hopefully never change any such thing though. Perhaps the policy should change so that security uploads are done with x.y.z-(w++)~lenny1? That is, the Debian version number gets incremented. But isn't the idea that the version in test/unstable should _always_ be higher than the version in stable including security versions? That makes incrementing 'w' not an option. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Merging packages
Frank Küster [EMAIL PROTECTED] wrote: Andreas Metzler [EMAIL PROTECTED] wrote: [...] bug #420578 Oh, since your statement confused me a bit, but reading the bug log clarified it: The problem is not with any symlink pointing to conffiles, in particular not with the common case of fixing non-FHS-aware applications by creating symlinks from /usr/share/ to /etc. Sorry for being unclear. The problem is specifically with symlinks from /etc to some other place in /etc, and is caused by the fact that debhelper does not mark symlinks in /etc as conffiles. Has this aspect been discussed with the debhelper maintainer? Actually the problem is that dpkg does not handle the case (#421344) sanely and therefore debhelper cannot (#421346) do it. cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On 15-May-07, 04:25 (CDT), Mgr. Peter Tuharsky [EMAIL PROTECTED] wrote: Do You think, that -compiling new upstream version of software against stable platform, building a package and distributing it -needs more effort than -studying security fixes in upstream, backporting them to ancient version of software (if it's barely possible), compiling it against stable platform, building a package and distributing it? It's not a matter of effort, it's a matter of stability. A new upstream version is a *much* higher risk of breaking other packages than backporting a security fix. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On 15-May-07, 08:27 (CDT), Mgr. Peter Tuharsky [EMAIL PROTECTED] wrote: We're going OT, however my experience based on last two Debian releases: testing becomes quite stable in means of usability somewhere half year before it's released as stable. The sooner before the stable, the rapidly increasing is the chance that the snapshot that You have will not be installable at all, will have dependencies severely broken, etc. That does not match my experience with testing. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On 14-May-07, 07:55 (CDT), Mgr. Peter Tuharsky [EMAIL PROTECTED] wrote: Ask somebody, what distro would he install at desktop for novice or M$ refugee? Why many are choosing Ubuntu instead of Debian, and even worse, abandon Debian in favor of Ubuntu? Why is this worse? Why isn't there room for two similar distributions, with one aimed at being more up-to-date for a limited set of packages and hardware, while the other aims at being rock-solid on a wide variety of hardware for extended periods of time? There are certainly ways that Debian can improve, but I'm not convinced that become more like Ubuntu is one of them. Why not let Ubuntu fulfill the desires of that group of users? Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
System freezes when copying large files over pptp in Etch
Hi all, I have several machines (all T60s) at work running Debian/Etch/AMD64 suffering the same problem: when copying large files over network the system suddenly freezes and is only rebootable via power-off button. I can reproduce this bug pretty constantly when running pptp but was not able to reproduce it without pptp yet, so I'm assuming it's a problem with pptp-linux or one of the relevant kernel drivers. I've no idea what the problem is but I noticed that my syslog always gets spammed with the following lines just before the freeze: pptp[4072]: anon log[decaps_gre:pptp_gre.c:407]: buffering packet 484619 (expecting 484489, lost or reordered) pptp[4072]: anon log[decaps_gre:pptp_gre.c:407]: buffering packet 484620 (expecting 484618, lost or reordered) pptp[4072]: anon log[decaps_gre:pptp_gre.c:407]: buffering packet 484621 (expecting 484618, lost or reordered) pptp[4072]: anon log[decaps_gre:pptp_gre.c:407]: buffering packet 484622 (expecting 484618, lost or reordered) pptp[4072]: anon log[decaps_gre:pptp_gre.c:407]: buffering packet 484623 (expecting 484618, lost or reordered) pptp[4082]: anon log[logecho:pptp_ctrl.c:676]: Echo Reply received. Someone pointed me to #416404 which is an open, grave bug against pptpd in etch, which sounded very similar but it's filled against pptpd (server) which is not even installed on those systems but pptp-linux (client). Is someone aware of this problem and knows if a bugreport was already filled? If not, how can I get useful information to report a bug myself? I've tried strace but it doesn't seem to provide useful information in this case (just read, write, select, ... again and again when using wget to download big files). Cheers, Bastian -- Bastian Venthur http://venthur.de Debian Developer venthur at debian org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Liability protection project - call for participants
Bruce Perens [EMAIL PROTECTED] writes: There is a downside. If you work on behalf of such an entity, you would have to agree to act at their direction, which means acting responsbily on their behalf, by not doing stupid stuff that obviously increases the corporation's risk of being sued. There are other potential downsides and complex legal interactions, such as interactions with existing personal umbrella policies which some people already carry and interactions with liability insurance already carried by employers when one's Debian work is wholly or partially in the context of some other employment. There are also possible conflict-of-interest issues for those whose employers are fine with personal contributions to volunteer projects but may not feel the same way about affiliation with a registered non-profit in an area of work that could be argued to be competing. I think it's important that, if this comes to fruition, it comes with very good legal advice attached, and I think that legal advice may need to be tailored to the specific circumstances of individual developers. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Tue, 15 May 2007, Mgr. Peter Tuharsky wrote: We're going OT, however my experience based on last two Debian releases: testing becomes quite stable in means of usability somewhere half year before it's released as stable. The sooner before the stable, the rapidly increasing is the chance that the snapshot that You have will not be installable at all, will have dependencies severely broken, etc. In several mails you claimed testing as broken. This is completely orthognal to my experience. I'm using testing since its existence on most of my boxes. Only production servers are running stable and I keep my fingers from running unstable (except of chroots). So were is the proof for you statement. What are the numbers of the bugs you might have reported against packages in testing? Could you please a bit more verbose about your problems in testing because nobody else made it to my radar that testing is that unusable. Perhaps I missed something ... Kind regards Andreas (writing from a laptop that runs testing. ;-)) -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: print-system virtual package?
On Tue, May 15, 2007 at 10:44:05AM -0500, Steve Greenland wrote: On 14-May-07, 14:40 (CDT), Andreas Fester [EMAIL PROTECTED] wrote: I was just investigating a bug where the issue seems that no print system is installed (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=420746) That raised the question: would it make sense to add a virtual package like print-system or similar, which is provided by cupsys-client, lpr et al. and which I can suggest or recommend in my package? Well, given the specific error: $ qcad libcups.so: cannot open shared object file: No such file or directory I don't think you need a virtual depends, but instead an explicit Depends: cupsys-client. Well, no; qcad needs to be fixed to use the fully qualified library name with soname included, instead of assuming it can open any file name 'libcups.so' (even if present) and get the interface it's looking for. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ensuring complete upgrades in applications with multiple binary packages
Le mardi 15 mai 2007 à 16:28 +0200, Frank Küster a écrit :
TeX Live is one big thing upstream (one DVD) and has been split for
Debian packaging into one arch:any and four arch:all source packages
with numerous binary packages each. Generally, you cannot assume a
system to work properly which has a mixture of different upstream
versions of these packages installed. But how should we achieve that?
A. The straightforward approach is the most ugly one: The packages of
course frequently declare Depends: texlive-some-other-package, and
we could switch all of these depends into versioned depends, (=
$upstream-version). But that would really look ugly, e.g. from
texlive-latex-extra:
-Depends: preview-latex-style, texlive-common (= 2007), texlive-pictures,
texlive-latex-base
+Depends: preview-latex-style, texlive-common (= 2007), texlive-pictures (=
2007), texlive-latex-base (= 2007)
It's ugly but it's the right thing to do. Unfortunately it doesn't
prevent texlive-latex-extra 2007 from being installed with
texlive-common 2008.
B. texlive-common could declare
Conflicts: long_list_of_texlive_packages_each_with_old_upstreamversion
But how would that work upon upgrade? Technically, there's no
problem, first all texlive packages except texlive-common would be
unpacked, then texlive-common could be unpacked and configured, after
that the others can be configured.
But usually dpkg tries to do unpacking and configuring in the same
order; would it be confused by this situation?
dpkg handles this case right, but it's really painful in the long term.
C. Ignore the problem and just expect from users to handle their
upgrades in a sane way and not put individual packages on hold?
Not setting strong enough dependencies is a RC bug.
For GNOME packages, we opted for a solution similar to A, but with the
notion of a next upstream version. For example, epiphany-extensions
declares:
Depends: epiphany-browser (= ${gnome:Version}), epiphany-browser (
${gnome:NextVersion})
The two variables are expanded (e.g. to 2.18 and 2.19 for GNOME 2.18.X)
by a specific rule. We can afford to do that for almost all packages
because upstream guarantees compatibility inside a major release.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`-our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
Re: print-system virtual package?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Greenland wrote: [...] That raised the question: would it make sense to add a virtual package like print-system or similar, which is provided by cupsys-client, lpr et al. and which I can suggest or recommend in my package? Well, given the specific error: $ qcad libcups.so: cannot open shared object file: No such file or directory I don't think you need a virtual depends, but instead an explicit Depends: cupsys-client. Well, the question was more a general one ;) because I was not sure if explicitly depending on one specific printing frontend is a good idea. Nevertheless, I meanwhile think that this specific issue has a different cause: it seems that the Qt runtime dynamically loads libcups.so, which is of course only available when the corresponding -dev package is installed (I could reproduce the originally reported issue today after a reboot). Manually creating the dev link from libcups.so.2 to libcups.so then worked around the problem ... Best Regards, Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGShCaZ3bQVzeW+rsRAnj0AJ9cQJkdZD27/BxrH2bcxAjzBkXsIQCeNtz6 ayyyEbmLBU/m+eObLqoLiOA= =EZK7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ensuring complete upgrades in applications with multiple binary packages
On Tue, May 15, 2007 at 04:28:39PM +0200, Frank Küster wrote: B. texlive-common could declare Conflicts: long_list_of_texlive_packages_each_with_old_upstreamversion But how would that work upon upgrade? Very, very poorly. Versioned conflicts are advocated against in Policy 7.3, because the package manager will often find it easier to remove the old version of the package than to upgrade it to a version that's acceptable. These sorts of conflicts seem to always be a major source of pain for non-interactive dist-upgrades. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
update-initramfs -k all -u
Hi, I maintain uswsusp. It is a package that relies on a binary on the initramfs that will start the resume process. This binary (and some other stuff) get installed via an update-initramfs call in the postinst. On some updates, the new binary that suspends the system is incompatible with the old resume binary on the initramfs, hence a update-initramfs call is required. So far so good. Current pratice is to only call `update-initramfs -u', that is, to only update the most recent initramfs. This however will break older initramfses (I have had bugreports). Now I plan to switch to running with '-k all' (all initramfses), but this of course will also influence the packages that ran with '-u' only. Now what do people think is the best option? (And why?) grts Tim signature.asc Description: PGP signature
Bug#424170: ITP: python-twisted-goodies -- miscellaneous add-ons for the Twisted networking framework
Package: wnpp Severity: wishlist Owner: Eric Evans [EMAIL PROTECTED] * Package name: python-twisted-goodies Version : 0.2 Upstream Author : Edwin A. Suominen [EMAIL PROTECTED] * URL : http://foss.eepatents.com/Twisted-Goodies * License : GPL Programming Lang: Python Description : miscellaneous add-ons for the Twisted networking framework This package contains miscellaneous third-party add-ons and improvements to the Twisted asynchronous processing framework. Modules included in this package: taskqueue: Asynchronous task queuing with a TaskQueue object and support staff for running tasks through a queue with a powerful system of task prioritization and management. webfetch: HTTP fetching with a SiteGetter object that handles fetching of web pages from a given server. asyncluster: Asynchronous clustering with a cluster management server asyncluster.master and node display manager asyncluster.ndm that communicate via Twisted's Perspective Broker. The long description was (mostly) taken verbatim from the project website and will need some work (suggestions welcome). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (700, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- Eric Evans [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: update-initramfs -k all -u
Hi, I maintain uswsusp. It is a package that relies on a binary on the initramfs that will start the resume process. This binary (and some other stuff) get installed via an update-initramfs call in the postinst. On some updates, the new binary that suspends the system is incompatible with the old resume binary on the initramfs, hence a update-initramfs call is required. So far so good. Current pratice is to only call `update-initramfs -u', that is, to only update the most recent initramfs. This however will break older initramfses (I have had bugreports). Now I plan to switch to running with '-k all' (all initramfses), but this of course will also influence the packages that ran with '-u' only. Now what do people think is the best option? (And why?) This may be related: http://lists.debian.org/debian-devel/2006/12/msg00014.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sp: News
The message that you sent to me (Deen Foxx) has not yet been delivered: From: debian-devel@lists.debian.org Subject: sp: News Date: Tue, 16 May 2007 01:15:44 -0300 (MSK) I am now using Vanquish to avoid spam. This automated message is an optional feature of that service, which I have enabled. Please accept this one-time request to confirm that the above message actually came from you. Your confirmation will release the message and allow all future messages from your address. Click here to confirm: http://confirm.vanquish.com/?U=lpKUi9n4VxfNkwO7bPrNxg Vanquish respects my privacy and yours. Your confirmation gets your mail delivered to me now and in the future. It does not serve any marketing purpose. Learn how privacy is assured: www.vanquish.com/privacy
Re: Getting Debian to use less power?
On Mon, May 14, 2007 at 09:20:00AM +0200, Petter Reinholdtsen wrote: Well, my experience is that rarely do the RFP result in anyone stepping up, and as I need the package and did the work already, I saw no use in not making it available from the Debian archive. I'll maintain powertop if you're looking to get rid of it. I have a new package for 1.2 sitting on my machine right now, just waiting to get an okay before I upload. Cheers, Christine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Mon, 2007-05-14 at 14:55 +0200, Mgr. Peter Tuharsky wrote: Ask somebody, what distro would he install at desktop for novice or M$ refugee? For me the choice is clear. I use Debian for myself. I choose to support Ubuntu for people that do not want as many choices. This is what M$ refugees think they want. Ubuntu is channelized into a few platforms as you put it. It has: Ubuntu == GNOME Desktop Environment (platform) Kubuntu == KDE Desktop Environment (platform) Xubuntu == XFCE Desktop Environment (platform) Each is release accordingly to the GNOME release schedule, as that is the driving force behind Ubuntu's release schedule. This release schedule is 6 months. Why many are choosing Ubuntu instead of Debian, and even worse, abandon Debian in favor of Ubuntu? The same reason many people choose Fedora Core or Mandriva or Gentoo or insert other distro because they can. I abandon Debian for other people, only because it has a (as you put it) more friendly support system. Why do most people consider Debian to be user-unfriendly and server-oriented distro? It is a misnomer that Debian is all about elitism or that it is hard to install or that the developers/mailing lists don't speak newbie-ese or that it doesn't support new hardware really well. I have to tell you the only thing in that list that *might* be right is the hardware thing for stable. Stable... more on the stable/ testing/ unstable/ thing in a bit. Debian developers often see Ubuntu the enemy and are mocking it as inferior technology. However, they fail to see, what does the Debian really offer to desktop users eventually. Sure, there is a bit of friction. Not Ubuntu is TEH 3N3MY, 7HR0W R0XX 47 7H3M! D13! D13! D13! or Argh, there mateys, we be sailing up the port side of the Ubuntu, prepare the starboard side cannons! Nothing of the sort. Ubuntu and Debian have a tremendously different set of motivators for releases and development. Debian, is all about volunteers, free and Free software and policy to implement them without much ado. This also has to occur across 10 or so Hardware architectures at the same time. Ubuntu, is all about volunteers, free and Free software, except where is interferes with the release schedule and the quality of the user experience. And it only supports three hardware architectures. And apparently soon, only 2 as Apple dropped PowerPC as an architecture. AND it is supported by a commercial entity. They fail to understand, why are they using Ubuntu happily and reference it to novices. It seems, that desktop users don't see Debian fitting their needs. What are the means? It is more about the fact that Ubuntu is indeed a niche OS. Debian runs on a plethora of Hardware Architectures and is consistent across those architectures. The answers: 1, needs 2, release cycle philosophy 3, community 4, priorities As many see, all of them are different in server and in desktop world, and many times Debian chooses to dictate the users we know the best what You need instead of listening to them. Why then are there 28000+ packages in Debian? If Debian only dictates, why then are there *FAR* more packages available for install than in *ANY* other Distribution? How many Window Managers? How many alternative packages to do the same thing, like word processing, editors, music clients, rss feed readers, web-browsers? I could go on for days, but I hope you get my point. Come on, we know the answer, you can say it. Let's think a while about the current situation. First define, what I need from my _desktop_, being an ordinary power user: a, The system must work well with available hardware, automatically and naturally This depends on *MANY* things. Primarily the Kernel. But also side projects to deal with vendors that produce *WINDOWS ONLY* device drivers. Case in point Wireless drivers. NDIS wrapper is a very good attempt to cover this. There are other device manufactures that only develop Windows drivers only. This is a case of Why bother, Windows cover 90%+ of the field b, Stable without (too many) crashes Do you realize Debian's stable is classified as this: Stable means stable package list. No changes in API and ABI names or versions. This means no newer versions will ever make it into stable. It is in maintenance mode. This makes a very good setup for those wishing for Rock Solid machines. Doesn't crash. too many comes from the Windows World, does not typically apply to Debian's Linux. c, Applications should work generally Okay, what specifically does not work in Debian? I have a few obscure problems, but they are obscure. Currently in Sid, I have an xnest problem, but it was only just introduced, will be fixed very shortly. I don't see your should work generally, mine just *DO* work. d, Applications should work together well
Re: sp: News
On Tue, May 15, 2007 at 05:16:54PM -0400, Confirmation from Deen Foxx wrote: The message that you sent to me (Deen Foxx) has not yet been delivered: From: debian-devel@lists.debian.org Subject: sp: News Date: Tue, 16 May 2007 01:15:44 -0300 (MSK) I am now using Vanquish to avoid spam. This automated message is an optional feature of that service, which I have enabled. Please accept this one-time request to confirm that the above message actually came from you. Your confirmation will release the message and allow all future messages from your address. Click here to confirm: http://confirm.vanquish.com/?U=lpKUi9n4VxfNkwO7bPrNxg Vanquish respects my privacy and yours. Your confirmation gets your mail delivered to me now and in the future. It does not serve any marketing purpose. Learn how privacy is assured: www.vanquish.com/privacy Hmm, seems someone subscribed while using one of those totally braindead email confirmation systems that only serversto cause more spam and infinite loops in mail systems. This almost falls under the same category as 'no vacation mail' although not quite the same. Maybe a new item should be added to the mailing list 'Code of conduct'. :) -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Tue, 2007-05-15 at 21:43 +0200, Andreas Tille wrote: On Tue, 15 May 2007, Mgr. Peter Tuharsky wrote: We're going OT, however my experience based on last two Debian releases: testing becomes quite stable in means of usability somewhere half year before it's released as stable. The sooner before the stable, the rapidly increasing is the chance that the snapshot that You have will not be installable at all, will have dependencies severely broken, etc. In several mails you claimed testing as broken. This is completely orthognal to my experience. I'm using testing since its existence on most of my boxes. To that, I run Sid/unstable on 90% of everything I have. Stable on those machines that cannot have problems. Only production servers are running stable and I keep my fingers from running unstable (except of chroots). I haven't seen an unstable problem that was a problem for more than a couple of days... and mostly had workarounds in any case. So were is the proof for you statement. What are the numbers of the bugs you might have reported against packages in testing? Could you please a bit more verbose about your problems in testing because nobody else made it to my radar that testing is that unusable. Perhaps I missed something ... I've asked for specific examples. Kind regards Andreas (writing from a laptop that runs testing. ;-)) Cheers from a Sid+Experimental machine. -- greg, [EMAIL PROTECTED] PGP key: 1024D/B524687C 2003-08-05 Fingerprint: E1D3 E3D7 5850 957E FED0 2B3A ED66 6971 B524 687C Alternate Fingerprint: 09F9 1102 9D74 E35B D841 56C5 6356 88C0 signature.asc Description: This is a digitally signed message part
Re: Mysterious NMU (Bug #423455)
On Tue, May 15, 2007 at 01:14:01PM -0400, Lennart Sorensen wrote: On Tue, May 15, 2007 at 12:20:22PM -0400, Roberto C. S?nchez wrote: Yes, but in reality what is the likelihood that either a security update or NMU would introduce an incompatible change? I would say that such a possibility is extremely low. Why couldn't a security change require making incompatible changes to something? A bin NMU would hopefully never change any such thing though. I am not saying that such a thing couldn't happen, simply that a security update is much less likely to cause it. Perhaps the policy should change so that security uploads are done with x.y.z-(w++)~lenny1? That is, the Debian version number gets incremented. But isn't the idea that the version in test/unstable should _always_ be higher than the version in stable including security versions? That makes incrementing 'w' not an option. Well, the ~ character is stated to be evaluated to be less than the empty string. If a package is the target of a security upload in stable, you can be certain that the testing/unstable version will also increase when the new package is introduced to fix the problem there as well. Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: update-initramfs -k all -u
also sprach Tim Dijkstra [EMAIL PROTECTED] [2007.05.15.2201 +0200]: Now what do people think is the best option? (And why?) I use -k all in mdadm already. I could not find any reasons why that would not be a good idea. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems when everything is coming your way, you're in the wrong lane. signature.asc Description: Digital signature (GPG/PGP)
Re: RFC: initramfs-tools postinst causes system inconsistency?
i'd appreciate if you post such questions to the corresponding development mailing list which is debian-kernel for initramfs questions. thanks Current pratice is to only call `update-initramfs -u', that is, to only update the most recent initramfs. This however will break older initramfses (I have had bugreports). Now I plan to switch to running with '-k all' (all initramfses), but this of course will also influence=20 the packages that ran with '-u' only. afaik uswsusp does not support full 2.6.15 range, so better stay on the safe side. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: initramfs-tools postinst causes system inconsistency?
On Tuesday 15 May 2007 15:54, maximilian attems wrote: afaik uswsusp does not support full 2.6.15 range, so better stay on the safe side. What about 2.6.18? I am not sure Debian should be that worried about kernels before the one that shipped with the last stable. wt -- Warren Turkal, Research Associate III/Systems Administrator Colorado State University, Dept. of Atmospheric Science -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Stable too stable?
Le Tue, May 15, 2007 at 05:50:50PM -0400, Greg Folkert a écrit : f, Usability problems, wishes and bugs should get fixed too. I should be able to report a problem, participate on it's solution and see fruits of that. Have you even looked at Debian's BTS? Unless your patch or bug is a security related problem, it won't make it into Stable. Stable is in maintenance mode. Not in New features or versions or additions or design improvements mode. That would be testing. Hi all, I think that Peter really makes a point there. Since the release of Etch, I am using it at work, and I am running in usabiilty bugs. Since they do not open the possibility for somebody else to take control of my machine, will they never be fixed? Definitely, a good backporting strategy could be very helpful to users, but I think that Debian needs something else in addition. For the moment, users of stable must rely on linear webforum-style information written in english in the BTS to find workarounds, or be lucky that somebody on a user mailing list shares their experience. Since the BTS understands versions, maybe providing an easy display of the bugs which are still open in Stable could help users to have a good overview. In line with this, official message (for instance a summary) from the maintainers could be displayed (and translated ?) on top of the bug. Maybe at each point release, the release notes could be updated on the basis of these messages. Things like emacs21 does not have full unicode support, but you can display chinese characters if you install the mule-ucs package. for instance. (I wasted hours, because I thought that packages with no full unicode support would at least have an open bug on this issue since it is a past release goal...). Have a nice day, -- Charles -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
On Tue, May 15, 2007 at 09:41:17AM +0200, Mgr. Peter Tuharsky wrote: The kernel, the X.org So are you volunteering to join the kernel and XSF teams to make this happen? - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Stable too stable?
On Wednesday 16 May 2007 01:11, Charles Plessy wrote: Maybe at each point release, the release notes could be updated on the basis of these messages. Things like emacs21 does not have full unicode support, but you can display chinese characters if you install the mule-ucs package. for instance. (I wasted hours, because I thought that packages with no full unicode support would at least have an open bug on this issue since it is a past release goal...). IIRC there already is a general note about that in the RN. (At least in the installation section, not sure about the what's changed section. Feel free to file BRs against release-notes for information that could be added. Including a (short) proposed text for an issue increases the chance it will be included. Cheers, FJP pgpGwFCsunq2H.pgp Description: PGP signature
Bug#424406: ITP: python-snpp -- SNPP library for Python
Package: wnpp Severity: wishlist Owner: Bernd Zeimetz [EMAIL PROTECTED] * Package name: python-snpp Version : 1.1.1 Upstream Author : Monty Taylor [EMAIL PROTECTED] * URL : http://www.sf.net/projects/pysnpp * License : GPL2 Programming Lang: Python Description : SNPP library for Python Pure Python library implementing RFC 1861, the Simple Network Paging Protocol -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug Squashing Party -- May 17th - 20th
Martin Zobel-Helas wrote: where to find available RC bugs: http://bts.turmzimmer.net/details.php?ignore=sidignnew=onnew=5 I'm just curious - the ignore=sid part means exclude bugs that only affect sid, correct? Which means bugs which affect lenny but are already fixed in sid are still included (I think). Is it useful to have bugs already fixed in sid included in the list for BSP purposes? I would have thought bydist=both would be more appropriate. Just my 2p. Dave. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mysterious NMU (Bug #423455)
Roberto C. Sánchez wrote: Well, the ~ character is stated to be evaluated to be less than the empty string. If a package is the target of a security upload in stable, you can be certain that the testing/unstable version will also increase when the new package is introduced to fix the problem there as well. What if it's a NMU? -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug Squashing Party -- May 17th - 20th
David Claughton wrote: Martin Zobel-Helas wrote: where to find available RC bugs: http://bts.turmzimmer.net/details.php?ignore=sidignnew=onnew=5 I'm just curious - the ignore=sid part means exclude bugs that only affect sid, correct? Which means bugs which affect lenny but are already fixed in sid are still included (I think). Is it useful to have bugs already fixed in sid included in the list for BSP purposes? I would have thought bydist=both would be more appropriate. You might want to read the section Testing-only bugs at [0] on why lenny-only bugs might also be interesting to fix. Cheers Luk [0] http://people.debian.org/~vorlon/rc-bugsquashing.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted amavis-stats 0.1.12-7.4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 May 2007 22:51:18 -0700 Source: amavis-stats Binary: amavis-stats Architecture: source all Version: 0.1.12-7.4 Distribution: unstable Urgency: high Maintainer: Jean-Michel Kelbert [EMAIL PROTECTED] Changed-By: Steve Langasek [EMAIL PROTECTED] Description: amavis-stats - Virus statistics RRDtool frontend for Amavis Closes: 416646 Changes: amavis-stats (0.1.12-7.4) unstable; urgency=high . * Non-maintainer upload. * High-urgency upload for RC bugfix. * Guard the calls to debconf in the postrm so that they work even if debconf has already been removed; and drop the duplicate call to db_purge. Closes: #416646. Files: 0ed449c1dd7b3420769501d9d34b6fcc 607 admin extra amavis-stats_0.1.12-7.4.dsc 84287ad09f8a3e9cb040e924fa1d024d 35969 admin extra amavis-stats_0.1.12-7.4.diff.gz 82df97ea59579fd525049eb32a7ee88e 26416 admin extra amavis-stats_0.1.12-7.4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSU6/KN6ufymYLloRAvOEAJ43s7c8KlWSEDew3Q5QFDPQxUzimACffDI1 qChtqzSiXd+lT2ECN45p8JM= =k+2Q -END PGP SIGNATURE- Accepted: amavis-stats_0.1.12-7.4.diff.gz to pool/main/a/amavis-stats/amavis-stats_0.1.12-7.4.diff.gz amavis-stats_0.1.12-7.4.dsc to pool/main/a/amavis-stats/amavis-stats_0.1.12-7.4.dsc amavis-stats_0.1.12-7.4_all.deb to pool/main/a/amavis-stats/amavis-stats_0.1.12-7.4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted egg 4.0.6+0.20041122cvs-10 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:41:55 +0900 Source: egg Binary: egg Architecture: source i386 Version: 4.0.6+0.20041122cvs-10 Distribution: unstable Urgency: low Maintainer: ISHIKAWA Mutsumi [EMAIL PROTECTED] Changed-By: ISHIKAWA Mutsumi [EMAIL PROTECTED] Description: egg- Tamago Ver. 4 -- EGG Input Method Architecture for Emacsen Changes: egg (4.0.6+0.20041122cvs-10) unstable; urgency=low . * adapt emacs22 * fix debian/rules to clean up helper/egg-helper * cleanup debian/rules * bump Standerd-Version to 3.7.2.2 Files: 80f8d0ae1690c356642ae5f20b9a762a 594 utils extra egg_4.0.6+0.20041122cvs-10.dsc a3e7dd57eb2d4f729812578b6800fe10 16575 utils extra egg_4.0.6+0.20041122cvs-10.diff.gz 2c4923dde0617c5c933c4d02c4258d5f 162696 utils extra egg_4.0.6+0.20041122cvs-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iEYEARECAAYFAkZJUfEACgkQfi8w7uypT6hUfgCdE8eGsNNIS5EAH1M6dJSIEPt2 9hkAnRzBpBQPsJiORWCWmILuF0sqc6mu =AVbo -END PGP SIGNATURE- Accepted: egg_4.0.6+0.20041122cvs-10.diff.gz to pool/main/e/egg/egg_4.0.6+0.20041122cvs-10.diff.gz egg_4.0.6+0.20041122cvs-10.dsc to pool/main/e/egg/egg_4.0.6+0.20041122cvs-10.dsc egg_4.0.6+0.20041122cvs-10_i386.deb to pool/main/e/egg/egg_4.0.6+0.20041122cvs-10_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kcheckgmail 0.5.6-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 22 Apr 2007 20:54:46 +0200 Source: kcheckgmail Binary: kcheckgmail Architecture: source i386 Version: 0.5.6-1 Distribution: unstable Urgency: low Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Changed-By: Jose Luis Tallon [EMAIL PROTECTED] Description: kcheckgmail - KDE systray application to check GMail accounts Closes: 296420 349531 378192 378192 407509 415234 420264 420264 Changes: kcheckgmail (0.5.6-1) unstable; urgency=low . * New upstream version (Closes: #415234) - Works on amd64 (Closes: #420264, #378192) . * Several upstream fixes - More efficient (Closes: #349531) - Fixes charset issues (Closes: #296420) - Proprely opens GMail (Closes: #378192, #420264) . * Build enhancements - Completely disable debug verbose debugging code (Closes: #407509) . * Many thanks to Raphael G [EMAIL PROTECTED], for adopting KCheckGmail upstream and providing so much help and feedback. Files: 1d88e9f9aa53dffc6d181a9333ec4cc3 643 kde optional kcheckgmail_0.5.6-1.dsc eb2bbc155c7b5ee7cda52009edc659ff 658150 kde optional kcheckgmail_0.5.6.orig.tar.gz 0c530c89bc1d5c92a737edc61a387239 8920 kde optional kcheckgmail_0.5.6-1.diff.gz 2575f8c0591fb7dbf02454b97ce14cec 129140 kde optional kcheckgmail_0.5.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSVYIipBneRiAKDwRAgomAJ9SzjPWr3X0oJg98Y1G2Dlq0ychIACaA4kI xPKNI+9xUEm6imF/Bh8zbrQ= =70QC -END PGP SIGNATURE- Accepted: kcheckgmail_0.5.6-1.diff.gz to pool/main/k/kcheckgmail/kcheckgmail_0.5.6-1.diff.gz kcheckgmail_0.5.6-1.dsc to pool/main/k/kcheckgmail/kcheckgmail_0.5.6-1.dsc kcheckgmail_0.5.6-1_i386.deb to pool/main/k/kcheckgmail/kcheckgmail_0.5.6-1_i386.deb kcheckgmail_0.5.6.orig.tar.gz to pool/main/k/kcheckgmail/kcheckgmail_0.5.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libwww-opensearch-perl 0.12-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 13 May 2007 20:47:32 +0100 Source: libwww-opensearch-perl Binary: libwww-opensearch-perl Architecture: source all Version: 0.12-1 Distribution: unstable Urgency: low Maintainer: Ian Beckwith [EMAIL PROTECTED] Changed-By: Ian Beckwith [EMAIL PROTECTED] Description: libwww-opensearch-perl - search OpenSearch compatible web sites Changes: libwww-opensearch-perl (0.12-1) unstable; urgency=low . * New upstream version. * Added dependency on liburi-template-perl. * Added watch file. Files: de9121c3aabbc608a8efb8243482 871 perl optional libwww-opensearch-perl_0.12-1.dsc a7e0044c877713c9a191f7d4dc0f5f1c 26957 perl optional libwww-opensearch-perl_0.12.orig.tar.gz 9cbeb60f6155307b1af3f0e8acdcf54a 1948 perl optional libwww-opensearch-perl_0.12-1.diff.gz 75efd46e4373f5dbd455e955e7b1e1a7 29826 perl optional libwww-opensearch-perl_0.12-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSViCipBneRiAKDwRAgMnAJ9Dm0Y3K6MlEuRLWtPZfU17X7gsVACdHfDa BzbgEkGwq5pow39hQT3b+RE= =TJO6 -END PGP SIGNATURE- Accepted: libwww-opensearch-perl_0.12-1.diff.gz to pool/main/libw/libwww-opensearch-perl/libwww-opensearch-perl_0.12-1.diff.gz libwww-opensearch-perl_0.12-1.dsc to pool/main/libw/libwww-opensearch-perl/libwww-opensearch-perl_0.12-1.dsc libwww-opensearch-perl_0.12-1_all.deb to pool/main/libw/libwww-opensearch-perl/libwww-opensearch-perl_0.12-1_all.deb libwww-opensearch-perl_0.12.orig.tar.gz to pool/main/libw/libwww-opensearch-perl/libwww-opensearch-perl_0.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bzr-builddeb 0.16.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 May 2007 14:08:11 +0200 Source: bzr-builddeb Binary: bzr-builddeb Architecture: source all Version: 0.16.1 Distribution: unstable Urgency: low Maintainer: Debian Bazaar Maintainers [EMAIL PROTECTED] Changed-By: Reinhard Tartler [EMAIL PROTECTED] Description: bzr-builddeb - bzr plugin for Debian package management Closes: 423745 Changes: bzr-builddeb (0.16.1) unstable; urgency=low . * fix FTBFS by correcting build depends. Thanks to Rob Weir [EMAIL PROTECTED] for providing the patch! (Closes: #423745) Files: dcc8fe94aa688b2c95b25c9183a2bc5a 866 devel optional bzr-builddeb_0.16.1.dsc 273ff954eb3f2080185f242986da4c8d 37116 devel optional bzr-builddeb_0.16.1.tar.gz 60607865b195b3a131bf4bd739ca7962 31228 devel optional bzr-builddeb_0.16.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Debian Powered! iD8DBQFGSWCVmAg1RJRTSKQRAtwtAJwIVpoKH0A5sfHr4oqFD1dJdIUVtwCeJjIx hXNFFm29sRwUBSJkg6PO54o= =gyoV -END PGP SIGNATURE- Accepted: bzr-builddeb_0.16.1.dsc to pool/main/b/bzr-builddeb/bzr-builddeb_0.16.1.dsc bzr-builddeb_0.16.1.tar.gz to pool/main/b/bzr-builddeb/bzr-builddeb_0.16.1.tar.gz bzr-builddeb_0.16.1_all.deb to pool/main/b/bzr-builddeb/bzr-builddeb_0.16.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnunet-gtk 0.7.1c-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 10:09:10 +0200 Source: gnunet-gtk Binary: gnunet-gtk-dev gnunet-gtk Architecture: source i386 Version: 0.7.1c-2 Distribution: unstable Urgency: low Maintainer: Arnaud Kyheng [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: gnunet-gtk - GTK frontend to GNUnet gnunet-gtk-dev - GTK frontend to GNUnet Changes: gnunet-gtk (0.7.1c-2) unstable; urgency=low . * Upload to unstable. * Rebuild against gnunet 0.7.1c-2. * Added build-depends to libnotify-dev. Files: 16d085659078a346daaa5c4c1920ffbb 814 net optional gnunet-gtk_0.7.1c-2.dsc 4015212f2802cad7dcc7ccb78a3800c0 7004 net optional gnunet-gtk_0.7.1c-2.diff.gz bccaea03ca5a2b25cebf0813c8247337 221338 net optional gnunet-gtk_0.7.1c-2_i386.deb b5c35f5d5fb56e135d4206afd20d4968 7848 libdevel optional gnunet-gtk-dev_0.7.1c-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSW2W+C5cwEsrK54RAg+DAJoDwvycCmX4kFagh2V8ephISGrufACfWnFL A8hhMM63kwoqtqt6U/YP8A8= =OiWW -END PGP SIGNATURE- Accepted: gnunet-gtk-dev_0.7.1c-2_i386.deb to pool/main/g/gnunet-gtk/gnunet-gtk-dev_0.7.1c-2_i386.deb gnunet-gtk_0.7.1c-2.diff.gz to pool/main/g/gnunet-gtk/gnunet-gtk_0.7.1c-2.diff.gz gnunet-gtk_0.7.1c-2.dsc to pool/main/g/gnunet-gtk/gnunet-gtk_0.7.1c-2.dsc gnunet-gtk_0.7.1c-2_i386.deb to pool/main/g/gnunet-gtk/gnunet-gtk_0.7.1c-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libalgorithm-c3-perl 0.07-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 10:14:43 +0200 Source: libalgorithm-c3-perl Binary: libalgorithm-c3-perl Architecture: source all Version: 0.07-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.07-1) unstable; urgency=low . * New upstream release Files: 9e234cdaa7a3ac243e41000fe87eb352 818 perl optional libalgorithm-c3-perl_0.07-1.dsc 2e301c80f096182cb16a30f0db9603ee 9563 perl optional libalgorithm-c3-perl_0.07.orig.tar.gz e420ef091a771ed45dd9024c009b348f 2045 perl optional libalgorithm-c3-perl_0.07-1.diff.gz 3b49cfa352b327cf93c664caa46bf29b 11574 perl optional libalgorithm-c3-perl_0.07-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSWxWy+HP4f7iC8sRArOrAJ97e/Vo7dPlxDeJBb96/gxDf3GQiQCglbim jjQOXXrvTvZ0XDQQwJCamXg= =QGid -END PGP SIGNATURE- Accepted: libalgorithm-c3-perl_0.07-1.diff.gz to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.07-1.diff.gz libalgorithm-c3-perl_0.07-1.dsc to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.07-1.dsc libalgorithm-c3-perl_0.07-1_all.deb to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.07-1_all.deb libalgorithm-c3-perl_0.07.orig.tar.gz to pool/main/liba/libalgorithm-c3-perl/libalgorithm-c3-perl_0.07.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted telepathy-mission-control 4.22-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 09:19:24 +0200 Source: telepathy-mission-control Binary: libmissioncontrol-server-doc libmissioncontrol-server-dev libmissioncontrol-server0 libmissioncontrol0 libmissioncontrol-dev telepathy-mission-control libmissioncontrol-doc Architecture: source all i386 Version: 4.22-2 Distribution: unstable Urgency: low Maintainer: Telepathy Maintaince Team [EMAIL PROTECTED] Changed-By: Sjoerd Simons [EMAIL PROTECTED] Description: libmissioncontrol-dev - Development files for the Telepathy mission control library libmissioncontrol-doc - Documentation for the Telepathy mission control library libmissioncontrol-server-dev - Development files for the Telepathy mission control plugin librar libmissioncontrol-server-doc - Documentatation for the Telepathy mission control plugin library libmissioncontrol-server0 - Telepathy mission control plugin library libmissioncontrol0 - Library to interact with Telepathy mission control telepathy-mission-control - Central control for Telepathy connection managers Changes: telepathy-mission-control (4.22-2) unstable; urgency=low . * Let libmissioncontrol-dev depend on libtelepathy-dev Files: c77f88b42ec0c82942b6c273f0d66b40 1084 libs optional telepathy-mission-control_4.22-2.dsc c5690b3b7b05052bff44e6fa03a354e5 2973 libs optional telepathy-mission-control_4.22-2.diff.gz 3397d880857b82606ac99c4900ea090a 55390 doc optional libmissioncontrol-server-doc_4.22-2_all.deb 2e77982784b642c6c37a372074414b25 52954 doc optional libmissioncontrol-doc_4.22-2_all.deb b3c39f400de8ea27d476772d444ec911 33436 net optional telepathy-mission-control_4.22-2_i386.deb b1363083d5b95cb2c1d24ca1b8d7944e 83630 libs optional libmissioncontrol-server0_4.22-2_i386.deb c754ce7a4c0c85b11047ad4251577d17 103414 libdevel optional libmissioncontrol-server-dev_4.22-2_i386.deb 0001fddabec16d000277ac8be560f3b6 56954 libs optional libmissioncontrol0_4.22-2_i386.deb 94280fd340813f22a2948bfa98e84c67 64614 libdevel optional libmissioncontrol-dev_4.22-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSWlFgTd+SodosdIRAmpbAJ9iUH5BBLwHr3w6tNPA+GMRg93m+QCg0eLW XUQKFZh0kaHmaAEKVy41SDo= =SDWC -END PGP SIGNATURE- Accepted: libmissioncontrol-dev_4.22-2_i386.deb to pool/main/t/telepathy-mission-control/libmissioncontrol-dev_4.22-2_i386.deb libmissioncontrol-doc_4.22-2_all.deb to pool/main/t/telepathy-mission-control/libmissioncontrol-doc_4.22-2_all.deb libmissioncontrol-server-dev_4.22-2_i386.deb to pool/main/t/telepathy-mission-control/libmissioncontrol-server-dev_4.22-2_i386.deb libmissioncontrol-server-doc_4.22-2_all.deb to pool/main/t/telepathy-mission-control/libmissioncontrol-server-doc_4.22-2_all.deb libmissioncontrol-server0_4.22-2_i386.deb to pool/main/t/telepathy-mission-control/libmissioncontrol-server0_4.22-2_i386.deb libmissioncontrol0_4.22-2_i386.deb to pool/main/t/telepathy-mission-control/libmissioncontrol0_4.22-2_i386.deb telepathy-mission-control_4.22-2.diff.gz to pool/main/t/telepathy-mission-control/telepathy-mission-control_4.22-2.diff.gz telepathy-mission-control_4.22-2.dsc to pool/main/t/telepathy-mission-control/telepathy-mission-control_4.22-2.dsc telepathy-mission-control_4.22-2_i386.deb to pool/main/t/telepathy-mission-control/telepathy-mission-control_4.22-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libclass-c3-perl 0.18-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 May 2007 16:22:38 +0200 Source: libclass-c3-perl Binary: libclass-c3-perl Architecture: source all Version: 0.18-1 Distribution: unstable Urgency: low Maintainer: Debian Catalyst Maintainers [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: libclass-c3-perl - A pragma to use the C3 method resolution order algortihm Changes: libclass-c3-perl (0.18-1) unstable; urgency=low . * New upstream release Files: 02ab9b51ced30f749fd8ec4e138d9baa 887 perl optional libclass-c3-perl_0.18-1.dsc 930c53503b3b4c8adfe51af57dd599e0 33291 perl optional libclass-c3-perl_0.18.orig.tar.gz a1650d3772a33f3507c41dc587b80e85 2357 perl optional libclass-c3-perl_0.18-1.diff.gz a799db6e3cfbac2cf1fa82b373a44585 23116 perl optional libclass-c3-perl_0.18-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSHshy+HP4f7iC8sRApuEAJ9qDG6felRLR1+ladBQ07I1IxJDnQCgghnu Pn9gXeW2Qpj9DSUDrXeUo3g= =5fkq -END PGP SIGNATURE- Accepted: libclass-c3-perl_0.18-1.diff.gz to pool/main/libc/libclass-c3-perl/libclass-c3-perl_0.18-1.diff.gz libclass-c3-perl_0.18-1.dsc to pool/main/libc/libclass-c3-perl/libclass-c3-perl_0.18-1.dsc libclass-c3-perl_0.18-1_all.deb to pool/main/libc/libclass-c3-perl/libclass-c3-perl_0.18-1_all.deb libclass-c3-perl_0.18.orig.tar.gz to pool/main/libc/libclass-c3-perl/libclass-c3-perl_0.18.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted iaxmodem 0.3.0~dfsg-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 09:43:53 +0200 Source: iaxmodem Binary: iaxmodem Architecture: source amd64 Version: 0.3.0~dfsg-1 Distribution: unstable Urgency: low Maintainer: Debian VoIP Team [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: iaxmodem - software modem with IAX2 connectivity Changes: iaxmodem (0.3.0~dfsg-1) unstable; urgency=low . * New upstream release. + Now supports V.17 reception; see changelog for details. Files: 3822dec660240c9764ecc35df0dce6e4 863 comm optional iaxmodem_0.3.0~dfsg-1.dsc d907d2e4d14f900203786ea56941cca8 2206896 comm optional iaxmodem_0.3.0~dfsg.orig.tar.gz 141d4fddd8ab6df34f5bdbefc3c38ebb 6193 comm optional iaxmodem_0.3.0~dfsg-1.diff.gz f2dc045ef74ed8f706abd06c342ee72e 198594 comm optional iaxmodem_0.3.0~dfsg-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSWXhzWFP1/XWUWkRAiVoAKCt4iB0EBtVagQjnj2ET8yZsdVU+gCgv3To pTPkSIqEMOoDDZHtVZBjweA= =JUys -END PGP SIGNATURE- Accepted: iaxmodem_0.3.0~dfsg-1.diff.gz to pool/main/i/iaxmodem/iaxmodem_0.3.0~dfsg-1.diff.gz iaxmodem_0.3.0~dfsg-1.dsc to pool/main/i/iaxmodem/iaxmodem_0.3.0~dfsg-1.dsc iaxmodem_0.3.0~dfsg-1_amd64.deb to pool/main/i/iaxmodem/iaxmodem_0.3.0~dfsg-1_amd64.deb iaxmodem_0.3.0~dfsg.orig.tar.gz to pool/main/i/iaxmodem/iaxmodem_0.3.0~dfsg.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libfile-copy-recursive-perl 0.33-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 10:30:13 +0200 Source: libfile-copy-recursive-perl Binary: libfile-copy-recursive-perl Architecture: source all Version: 0.33-1 Distribution: unstable Urgency: low Maintainer: Debian Catalyst Maintainers [EMAIL PROTECTED] Changed-By: Krzysztof Krzyzaniak (eloy) [EMAIL PROTECTED] Description: libfile-copy-recursive-perl - Perl extension for recursively copying files and directories Changes: libfile-copy-recursive-perl (0.33-1) unstable; urgency=low . * New upstream release Files: b92989c3dbbe8183a9cb618bfe36c133 868 perl optional libfile-copy-recursive-perl_0.33-1.dsc 172af9928a65e91ae0bc1439daabe6b9 9945 perl optional libfile-copy-recursive-perl_0.33.orig.tar.gz 9031aded5a7e46d9d92d54104b93d8d5 2325 perl optional libfile-copy-recursive-perl_0.33-1.diff.gz 1a51b214e27ed7b87448af91fbe36e6b 18616 perl optional libfile-copy-recursive-perl_0.33-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSXDmy+HP4f7iC8sRArJZAJ9f/UpIwC2O71lSYx+lJVAvv8t6HgCdEnXm fhGNJYXzmw0SUf/39+IdW1Q= =wOf1 -END PGP SIGNATURE- Accepted: libfile-copy-recursive-perl_0.33-1.diff.gz to pool/main/libf/libfile-copy-recursive-perl/libfile-copy-recursive-perl_0.33-1.diff.gz libfile-copy-recursive-perl_0.33-1.dsc to pool/main/libf/libfile-copy-recursive-perl/libfile-copy-recursive-perl_0.33-1.dsc libfile-copy-recursive-perl_0.33-1_all.deb to pool/main/libf/libfile-copy-recursive-perl/libfile-copy-recursive-perl_0.33-1_all.deb libfile-copy-recursive-perl_0.33.orig.tar.gz to pool/main/libf/libfile-copy-recursive-perl/libfile-copy-recursive-perl_0.33.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kiwi 1.9.13-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 10:41:47 +0200 Source: kiwi Binary: python-kiwi Architecture: source all Version: 1.9.13-4 Distribution: unstable Urgency: medium Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Matej Vela [EMAIL PROTECTED] Description: python-kiwi - a graphical framework to construct simple UI Closes: 423975 Changes: kiwi (1.9.13-4) unstable; urgency=medium . * QA upload. * debian/rules: Renaming .egg-info is no longer necessary. Closes: #423975. Files: 3d577e94fec91b12019cfe7f98a3d3bc 943 python optional kiwi_1.9.13-4.dsc a46eb9b15a6c15b77b2910617e372b1c 6707 python optional kiwi_1.9.13-4.diff.gz 42c78dde32e3be43c9a991c48b1a6d99 550246 python optional python-kiwi_1.9.13-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSXJxqbYs6sQrY8oRAhqYAJ0dJ/J1RDzQgEeExmKb0TmMtSx7qQCcCwx3 fNnRVI4Z8DSBoUx0DVw4WmE= =33cK -END PGP SIGNATURE- Accepted: kiwi_1.9.13-4.diff.gz to pool/main/k/kiwi/kiwi_1.9.13-4.diff.gz kiwi_1.9.13-4.dsc to pool/main/k/kiwi/kiwi_1.9.13-4.dsc python-kiwi_1.9.13-4_all.deb to pool/main/k/kiwi/python-kiwi_1.9.13-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted aiccu 20070115-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 8 May 2007 11:51:59 +0200 Source: aiccu Binary: aiccu Architecture: source amd64 Version: 20070115-3 Distribution: unstable Urgency: low Maintainer: Philipp Kern [EMAIL PROTECTED] Changed-By: Philipp Kern [EMAIL PROTECTED] Description: aiccu - SixXS Automatic IPv6 Connectivity Client Utility Changes: aiccu (20070115-3) unstable; urgency=low . * Fixed the sed expression for configuration file creation which did fail when special sed chars are given, thanks go to Michael Biehunko for the patch Files: 49ea55eda40bd6798e4b91e712077bc9 587 net optional aiccu_20070115-3.dsc 60ae5e37d85178c92ac1ae1a5cc898ff 12594 net optional aiccu_20070115-3.diff.gz 86daeb1fa1c975a6e35e38ebbcd87c66 49096 net optional aiccu_20070115-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSXgN7Ro5M7LPzdgRAoRuAJ4+J8PfgzusQiNnBLrKNS4Pof7r0ACfUfWC lKlfRvQs7v/uMnwg6Usl4t4= =rsN8 -END PGP SIGNATURE- Accepted: aiccu_20070115-3.diff.gz to pool/main/a/aiccu/aiccu_20070115-3.diff.gz aiccu_20070115-3.dsc to pool/main/a/aiccu/aiccu_20070115-3.dsc aiccu_20070115-3_amd64.deb to pool/main/a/aiccu/aiccu_20070115-3_amd64.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hdf5 1.6.5-5 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 May 2007 23:40:30 +0200 Source: hdf5 Binary: libhdf5-lam-dev hdf5-tools libhdf5-mpich-dev libhdf5-mpich-1.6.5-0 libhdf5-serial-dev libhdf5-doc libhdf5-lam-1.6.5-0 libhdf5-serial-1.6.5-0 Architecture: source all i386 Version: 1.6.5-5 Distribution: unstable Urgency: low Maintainer: Debian GIS Project [EMAIL PROTECTED] Changed-By: Francesco Paolo Lovergine [EMAIL PROTECTED] Description: hdf5-tools - Hierarchical Data Format 5 (HDF5) - Runtime tools libhdf5-doc - Hierarchical Data Format 5 (HDF5) - Documentation libhdf5-lam-1.6.5-0 - Hierarchical Data Format 5 (HDF5) - runtime files - LAM version libhdf5-lam-dev - Hierarchical Data Format 5 (HDF5) - development files - LAM versi libhdf5-mpich-1.6.5-0 - Hierarchical Data Format 5 (HDF5) - runtime files - MPICH version libhdf5-mpich-dev - Hierarchical Data Format 5 (HDF5) - development files - MPICH ver libhdf5-serial-1.6.5-0 - Hierarchical Data Format 5 (HDF5) - runtime files - serial versio libhdf5-serial-dev - Hierarchical Data Format 5 (HDF5) - development files - serial ve Changes: hdf5 (1.6.5-5) unstable; urgency=low . * Changed maintainer and added uploards for true in control.in * Moved to debhelper compatibility level 5. Files: 210742c5cdc7c758aea7b68c8103da10 858 science optional hdf5_1.6.5-5.dsc 9895bcb5f72f329301cf15a81f6020d7 523175 science optional hdf5_1.6.5-5.diff.gz 391a51f5d3d9da68d5a369b49b43fd22 1931630 doc optional libhdf5-doc_1.6.5-5_all.deb b5851938370706b4cc4a8513796c2bdc 616136 libs optional libhdf5-serial-1.6.5-0_1.6.5-5_i386.deb a3ff0ddfb5ebd0bf3f124952123eebba 742298 libdevel optional libhdf5-serial-dev_1.6.5-5_i386.deb 4dbf1f7d9b2694f1b9dafa02742b5a83 519108 libs extra libhdf5-lam-1.6.5-0_1.6.5-5_i386.deb be8dcca39903e8add87ef22537c507c4 620400 libdevel extra libhdf5-lam-dev_1.6.5-5_i386.deb 8cb45194e1c23c59e433174097a603c4 696098 libs extra libhdf5-mpich-1.6.5-0_1.6.5-5_i386.deb a0906e7a059252a830bbb0b35103eaeb 620164 libdevel extra libhdf5-mpich-dev_1.6.5-5_i386.deb 6934a342b13b6bcf2cfad9eae07620e1 217904 science optional hdf5-tools_1.6.5-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSXfwpFNRmenyx0cRAl60AJ0UV7RvhZB5w72uoLWsWlZRPLnSbwCdFbDV 5bE3d5h4776dt7tjSBTp2Yg= =Xd76 -END PGP SIGNATURE- Accepted: hdf5-tools_1.6.5-5_i386.deb to pool/main/h/hdf5/hdf5-tools_1.6.5-5_i386.deb hdf5_1.6.5-5.diff.gz to pool/main/h/hdf5/hdf5_1.6.5-5.diff.gz hdf5_1.6.5-5.dsc to pool/main/h/hdf5/hdf5_1.6.5-5.dsc libhdf5-doc_1.6.5-5_all.deb to pool/main/h/hdf5/libhdf5-doc_1.6.5-5_all.deb libhdf5-lam-1.6.5-0_1.6.5-5_i386.deb to pool/main/h/hdf5/libhdf5-lam-1.6.5-0_1.6.5-5_i386.deb libhdf5-lam-dev_1.6.5-5_i386.deb to pool/main/h/hdf5/libhdf5-lam-dev_1.6.5-5_i386.deb libhdf5-mpich-1.6.5-0_1.6.5-5_i386.deb to pool/main/h/hdf5/libhdf5-mpich-1.6.5-0_1.6.5-5_i386.deb libhdf5-mpich-dev_1.6.5-5_i386.deb to pool/main/h/hdf5/libhdf5-mpich-dev_1.6.5-5_i386.deb libhdf5-serial-1.6.5-0_1.6.5-5_i386.deb to pool/main/h/hdf5/libhdf5-serial-1.6.5-0_1.6.5-5_i386.deb libhdf5-serial-dev_1.6.5-5_i386.deb to pool/main/h/hdf5/libhdf5-serial-dev_1.6.5-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ocurl 0.2.1-8 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 May 2007 17:30:13 +0200 Source: ocurl Binary: libcurl-ocaml libcurl-ocaml-dev Architecture: source amd64 Version: 0.2.1-8 Distribution: unstable Urgency: low Maintainer: Enrico Tassi [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: libcurl-ocaml - ocaml curl bindings libcurl-ocaml-dev - ocaml libcurl bindings Closes: 423816 Changes: ocurl (0.2.1-8) unstable; urgency=low . * moved to ocaml CBDS class * rebuilt against curl abi 4 (Closes: #423816) Files: e49d465ad0719acafe4d31a28ef8ed44 850 libdevel optional ocurl_0.2.1-8.dsc 2c36d4aa31bbfe3714d1e6007589f0b8 3533 libdevel optional ocurl_0.2.1-8.diff.gz cfb665955ed8df47ef857de1093fb9d3 72000 libdevel optional libcurl-ocaml-dev_0.2.1-8_amd64.deb fe8a3faa26c9d5d415c0359e2b114cf6 20606 libs optional libcurl-ocaml_0.2.1-8_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSXv37kkcPgEj8vIRAhIpAKCf38Nd+fIo1cBWOEOlk80DzPx95gCghsdu usV0igZgcNI04btXahK/owk= =i8uh -END PGP SIGNATURE- Accepted: libcurl-ocaml-dev_0.2.1-8_amd64.deb to pool/main/o/ocurl/libcurl-ocaml-dev_0.2.1-8_amd64.deb libcurl-ocaml_0.2.1-8_amd64.deb to pool/main/o/ocurl/libcurl-ocaml_0.2.1-8_amd64.deb ocurl_0.2.1-8.diff.gz to pool/main/o/ocurl/ocurl_0.2.1-8.diff.gz ocurl_0.2.1-8.dsc to pool/main/o/ocurl/ocurl_0.2.1-8.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted accerciser 0.1.2-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 15 May 2007 11:31:02 +0200
Source: accerciser
Binary: accerciser
Architecture: source amd64
Version: 0.1.2-4
Distribution: unstable
Urgency: low
Maintainer: Mario Lang [EMAIL PROTECTED]
Changed-By: Mario Lang [EMAIL PROTECTED]
Description:
accerciser - an interactive Python accessibility explorer for the GNOME deskto
Changes:
accerciser (0.1.2-4) unstable; urgency=low
.
* Add yet more {Build-,}Depends. Gosh, what was I thinking...
Files:
4d6ba7c0bbfe1b23fd5e4f679f41d1a7 796 gnome extra accerciser_0.1.2-4.dsc
f82899c548e09358dbdaa7b10e50ca61 2131 gnome extra accerciser_0.1.2-4.diff.gz
aecd12ff92e4066ab03358abe19cf9bc 750994 gnome extra
accerciser_0.1.2-4_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGSYCq3/wCKmsRPkQRAgAQAKCKEuyBfbRfrtTapgoHV0pjM6TK4ACfajvx
IepRx+D6ICM/EMDgZ7UpcCQ=
=nZKN
-END PGP SIGNATURE-
Accepted:
accerciser_0.1.2-4.diff.gz
to pool/main/a/accerciser/accerciser_0.1.2-4.diff.gz
accerciser_0.1.2-4.dsc
to pool/main/a/accerciser/accerciser_0.1.2-4.dsc
accerciser_0.1.2-4_amd64.deb
to pool/main/a/accerciser/accerciser_0.1.2-4_amd64.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ipw3945 1.2.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 11:45:00 +0200 Source: ipw3945 Binary: ipw3945-source Architecture: source all Version: 1.2.1-1 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: ipw3945-source - Source for the Intel PRO/Wireless 3945ABG (ipw3945) driver Changes: ipw3945 (1.2.1-1) unstable; urgency=low . * New upstream release. Files: 97c55ba5c87d14bcc3acb2bc7fcad1eb 580 contrib/net extra ipw3945_1.2.1-1.dsc 9d6b2116122beb33a0d1d923ea49065c 200925 contrib/net extra ipw3945_1.2.1.orig.tar.gz e2db34000542854e60cc6edaac1a1515 5354 contrib/net extra ipw3945_1.2.1-1.diff.gz 32a68a9358f7de22a36325b8ab28c438 167652 contrib/net extra ipw3945-source_1.2.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSYFS+C5cwEsrK54RAmwvAJ9fhLk+a18dzbYC7QFnd99RHv19bQCfbVtc rWRPAWrhGwJhX2i//5xfDWE= =V+3y -END PGP SIGNATURE- Accepted: ipw3945-source_1.2.1-1_all.deb to pool/contrib/i/ipw3945/ipw3945-source_1.2.1-1_all.deb ipw3945_1.2.1-1.diff.gz to pool/contrib/i/ipw3945/ipw3945_1.2.1-1.diff.gz ipw3945_1.2.1-1.dsc to pool/contrib/i/ipw3945/ipw3945_1.2.1-1.dsc ipw3945_1.2.1.orig.tar.gz to pool/contrib/i/ipw3945/ipw3945_1.2.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bluez-gnome 0.6-2 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 11:39:53 +0200 Source: bluez-gnome Binary: bluez-gnome Architecture: source powerpc Version: 0.6-2 Distribution: unstable Urgency: low Maintainer: Debian Bluetooth Maintainers [EMAIL PROTECTED] Changed-By: Filippo Giunchedi [EMAIL PROTECTED] Description: bluez-gnome - Bluetooth utilities for GNOME Closes: 392539 405251 420447 Changes: bluez-gnome (0.6-2) unstable; urgency=low . * add Recommends: bluez-utils (Closes: #405251) * add gnome-icon-theme (= 2.16) as a dependency for stock_bluetooth.png (Closes: #420447) * rebuild against current gtk, fixes black background (Closes: #392539) Files: 2300325251ab829ce09fb7f6de85b9be 859 gnome optional bluez-gnome_0.6-2.dsc 85812e7d44bafa9adcff53021e86ab82 3458 gnome optional bluez-gnome_0.6-2.diff.gz 9db6dc4291d0dc5b0cea37d057a85ea8 31020 gnome optional bluez-gnome_0.6-2_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSYH5ABzeamt51AERAgyPAKDOizebRRH9eukV6sYfkO8z19ua9ACdHWuL v8oiEv5vm7PTi6ZdYp7IJ/c= =UvH9 -END PGP SIGNATURE- Accepted: bluez-gnome_0.6-2.diff.gz to pool/main/b/bluez-gnome/bluez-gnome_0.6-2.diff.gz bluez-gnome_0.6-2.dsc to pool/main/b/bluez-gnome/bluez-gnome_0.6-2.dsc bluez-gnome_0.6-2_powerpc.deb to pool/main/b/bluez-gnome/bluez-gnome_0.6-2_powerpc.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted potool 0.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 11:19:23 +0100 Source: potool Binary: potool Architecture: source i386 Version: 0.8-1 Distribution: unstable Urgency: medium Maintainer: Marcin Owsiany [EMAIL PROTECTED] Changed-By: Marcin Owsiany [EMAIL PROTECTED] Description: potool - A program to aid manipulation of gettext po files Changes: potool (0.8-1) unstable; urgency=medium . * New upstream revision - fixed a segfault when filtering plural entries - fixed some memleaks Files: 23dadb62bb8b16e6dff6dc07e73da462 581 utils optional potool_0.8-1.dsc b8aa882dfa8939792a252f43a770783f 9978 utils optional potool_0.8.orig.tar.gz 087fbb3ff9d524822f5b6aa8d3f94144 4404 utils optional potool_0.8-1.diff.gz a8e7a1bf507ce67b2e95759eaf322039 19804 utils optional potool_0.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSYpNOg2KoGD0EhYRAu5XAJ9EuOmoeFXaFWnk3nP0MP/X2u5ncgCfZzjO C3+sR3plx154Cv6VEdk9pe8= =XzWv -END PGP SIGNATURE- Accepted: potool_0.8-1.diff.gz to pool/main/p/potool/potool_0.8-1.diff.gz potool_0.8-1.dsc to pool/main/p/potool/potool_0.8-1.dsc potool_0.8-1_i386.deb to pool/main/p/potool/potool_0.8-1_i386.deb potool_0.8.orig.tar.gz to pool/main/p/potool/potool_0.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xmds-doc 0~svn.1342-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 10:50:19 +0200 Source: xmds-doc Binary: xmds-doc Architecture: source all Version: 0~svn.1342-2 Distribution: unstable Urgency: low Maintainer: Debian Scientific Computing Team [EMAIL PROTECTED] Changed-By: Rafael Laboissiere [EMAIL PROTECTED] Description: xmds-doc - documentation for the eXtensible Multi-Dimensional Simulator Closes: 423968 Changes: xmds-doc (0~svn.1342-2) unstable; urgency=low . * debian/control: Build-depend on gs-gpl, needed for the epstopdf command, so that the package will not FTBFS (closes: #423968) Files: 5cce623b5ca59776f6f7ccc50eadff91 918 doc extra xmds-doc_0~svn.1342-2.dsc 92f5de3b3ee648619f455eba1cc50061 2566 doc extra xmds-doc_0~svn.1342-2.diff.gz 47a49018f495674da4e6a598daf0a43b 7162712 doc extra xmds-doc_0~svn.1342-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSYr7k3oga0pdcv4RAnhrAJ0QPmU+O+Q3GGGSib3BMllcFYaR5gCgjubP B22CL3nqKid4lhCAVUzqh5g= =wK3I -END PGP SIGNATURE- Accepted: xmds-doc_0~svn.1342-2.diff.gz to pool/main/x/xmds-doc/xmds-doc_0~svn.1342-2.diff.gz xmds-doc_0~svn.1342-2.dsc to pool/main/x/xmds-doc/xmds-doc_0~svn.1342-2.dsc xmds-doc_0~svn.1342-2_all.deb to pool/main/x/xmds-doc/xmds-doc_0~svn.1342-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gtkmm2.4 1:2.10.10-0.2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 11:05:56 +0200 Source: gtkmm2.4 Binary: libgtkmm-2.4-dev libgtkmm-2.4-doc libgtkmm-2.4-1c2a Architecture: source amd64 all Version: 1:2.10.10-0.2 Distribution: unstable Urgency: low Maintainer: Bradley Bell [EMAIL PROTECTED] Changed-By: Guus Sliepen [EMAIL PROTECTED] Description: libgtkmm-2.4-1c2a - C++ wrappers for GTK+ 2.4 (shared libraries) libgtkmm-2.4-dev - C++ wrappers for GTK+ 2.4 (development files) libgtkmm-2.4-doc - C++ wrappers for GTK+ 2.4 (documentation) Closes: 423926 Changes: gtkmm2.4 (1:2.10.10-0.2) unstable; urgency=low . * Non-maintainer upload. * Update the dependencies of libgtkmm-2.4-dev. Closes: #423926 Files: 9256fe5e24ce473d0ae4507b3ba92f78 740 libs optional gtkmm2.4_2.10.10-0.2.dsc 7a14445d6d51edab9476c536cdb6a31c 129119 libs optional gtkmm2.4_2.10.10-0.2.diff.gz 3e47273652c19bd239fd1d4f8d6ac153 995418 libdevel optional libgtkmm-2.4-dev_2.10.10-0.2_amd64.deb e92cccf45abb5bdd0c6a0a54331e0d84 1099918 libs optional libgtkmm-2.4-1c2a_2.10.10-0.2_amd64.deb 1dfddf7f1d63dfaa0b6ef4c51203235e 9132868 doc optional libgtkmm-2.4-doc_2.10.10-0.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSX4nAxLow12M2nsRAglqAKCso/X2hgbY/kdzruvr/05ZJoGh3gCeJpSW C1KNZbwqlOWBprySLQ4JpGY= =r4Py -END PGP SIGNATURE- Accepted: gtkmm2.4_2.10.10-0.2.diff.gz to pool/main/g/gtkmm2.4/gtkmm2.4_2.10.10-0.2.diff.gz gtkmm2.4_2.10.10-0.2.dsc to pool/main/g/gtkmm2.4/gtkmm2.4_2.10.10-0.2.dsc libgtkmm-2.4-1c2a_2.10.10-0.2_amd64.deb to pool/main/g/gtkmm2.4/libgtkmm-2.4-1c2a_2.10.10-0.2_amd64.deb libgtkmm-2.4-dev_2.10.10-0.2_amd64.deb to pool/main/g/gtkmm2.4/libgtkmm-2.4-dev_2.10.10-0.2_amd64.deb libgtkmm-2.4-doc_2.10.10-0.2_all.deb to pool/main/g/gtkmm2.4/libgtkmm-2.4-doc_2.10.10-0.2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zeroc-icee-java 1.2.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 13 May 2007 00:31:10 +0200 Source: zeroc-icee-java Binary: libicee-java Architecture: source all Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco.Moya [EMAIL PROTECTED] Description: libicee-java - Ice-E for Java libraries Changes: zeroc-icee-java (1.2.0-1) unstable; urgency=low . * New upstream release Files: 7a9b3b6f07c50018638b338dee93e560 758 devel optional zeroc-icee-java_1.2.0-1.dsc 1bafa29fa4e9995b97367f03a6e9bb09 2930407 devel optional zeroc-icee-java_1.2.0.orig.tar.gz 6b3d4a39adb4a2bcb47f1209e88bb0e5 2693 devel optional zeroc-icee-java_1.2.0-1.diff.gz 828611ba3d0d33581babaa0e93006e98 204734 devel optional libicee-java_1.2.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSZA1OaI3yygJ5hoRAs3NAKDwygNyGs9SSUpG5uh4RcirpQJfegCbBkBO UINp3numWs1bJ1dSGuZ2tZY= =tkFj -END PGP SIGNATURE- Accepted: libicee-java_1.2.0-1_all.deb to pool/main/z/zeroc-icee-java/libicee-java_1.2.0-1_all.deb zeroc-icee-java_1.2.0-1.diff.gz to pool/main/z/zeroc-icee-java/zeroc-icee-java_1.2.0-1.diff.gz zeroc-icee-java_1.2.0-1.dsc to pool/main/z/zeroc-icee-java/zeroc-icee-java_1.2.0-1.dsc zeroc-icee-java_1.2.0.orig.tar.gz to pool/main/z/zeroc-icee-java/zeroc-icee-java_1.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zeroc-icee-translators 1.2.0-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 12 May 2007 23:51:22 +0200 Source: zeroc-icee-translators Binary: slice2javae slice2cppe icee-translators Architecture: source all i386 Version: 1.2.0-1 Distribution: unstable Urgency: low Maintainer: Francisco Moya [EMAIL PROTECTED] Changed-By: Francisco.Moya [EMAIL PROTECTED] Description: icee-translators - Metapackage to install ZeroC IceE Slice translators slice2cppe - Slice to C++ translator for IceE slice2javae - Slice to Java translator for IceE Changes: zeroc-icee-translators (1.2.0-1) unstable; urgency=low . * New upstream release Files: 6dd1084585b8a18a83d9d169bd10facb 666 devel optional zeroc-icee-translators_1.2.0-1.dsc bc8e385c847b12c20a5c98b655358d9e 351710 devel optional zeroc-icee-translators_1.2.0.orig.tar.gz cefaad6a83b5e621ff57b9193fda6e30 5982 devel optional zeroc-icee-translators_1.2.0-1.diff.gz 4f1d32ddf2c9795e582da4751bac7b67 4270 devel optional icee-translators_1.2.0-1_all.deb 020035ad2d82a12066fc6e4139f8bad1 346376 devel optional slice2cppe_1.2.0-1_i386.deb 1b704b6d850eaa8082debb01b06d6ef0 373364 devel optional slice2javae_1.2.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSZA6OaI3yygJ5hoRAjQXAKDkwIiWXEYswPOGWwjNdgxsBIrzugCcDaJy 6FVKHFaiIvpVBgABBjYxGdA= =mzRF -END PGP SIGNATURE- Accepted: icee-translators_1.2.0-1_all.deb to pool/main/z/zeroc-icee-translators/icee-translators_1.2.0-1_all.deb slice2cppe_1.2.0-1_i386.deb to pool/main/z/zeroc-icee-translators/slice2cppe_1.2.0-1_i386.deb slice2javae_1.2.0-1_i386.deb to pool/main/z/zeroc-icee-translators/slice2javae_1.2.0-1_i386.deb zeroc-icee-translators_1.2.0-1.diff.gz to pool/main/z/zeroc-icee-translators/zeroc-icee-translators_1.2.0-1.diff.gz zeroc-icee-translators_1.2.0-1.dsc to pool/main/z/zeroc-icee-translators/zeroc-icee-translators_1.2.0-1.dsc zeroc-icee-translators_1.2.0.orig.tar.gz to pool/main/z/zeroc-icee-translators/zeroc-icee-translators_1.2.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted webcalendar 1.1.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 15 May 2007 13:06:37 +0200
Source: webcalendar
Binary: webcalendar
Architecture: source all
Version: 1.1.2-1
Distribution: experimental
Urgency: low
Maintainer: WebCalendar Debian package development [EMAIL PROTECTED]
Changed-By: Rafael Laboissiere [EMAIL PROTECTED]
Description:
webcalendar - PHP-Based multi-user calendar
Closes: 293648 407698 407700
Changes:
webcalendar (1.1.2-1) experimental; urgency=low
.
[ Rafael Laboissiere ]
* New upstream release. This is a development upstream release, hence
the upload to experimental.
* This release allow external files to be included as header/trailer
(closes: #293648)
* dpatches adapted for 1.1.2:
+ 01_config_patch
+ 02_pgsql_patch
+ 03_login_lean
+ 04_php-perl-paths
+ 07_SA23341-xss-vulnerability
* Removed dpatch:
+ 05_translations-french-utf8
* Added dpatches:
+ 08_db-load-config: Load the configuration settings if
WEBCAL_PROGRAM_VERSION is not present in the webcal_config table or
if it corresponds to an old version of WebCalendar. This will avoid
launching the Installation Wizard when visiting the web page at the
first time.
+ 09_quote-edit-template: Fix a typo that was preventing custom
header/trailer edition. This is taken from the Help/Troubleshooting
forum of the WebCalendar project at SourceForge (#1734121)
+ 10_include-header-trailer: Allow leading/trailing whitespaces in
file name specified for custom header/trailer inclusion. Also,
fixes a small typo that was making the file name appear in the web
page along with its HTML contents. This patch was proposed to the
Patch Tracker of the WebCalendar project at SourceForge (#1719102
and #1719114).
.
* debian/watch: Adjusted for the development tarballs at SourceForge
.
* debian/rules:
+ Fixed permissions of some installed files
+ Removed extra license file phpmailer/LICENSE
* debian/copyright: Added copyright statement and licensing terms for
files in /www/includes/classes/phpmailer/
.
* debian/sql/upgrade-{my,pg}sql/1.1.2-1: Added upgrade files. Some
SQL is taken from install/{index,install_functions}.php.
* debian/install:
+ Adjusted for the new upgrade SQL scripts
+ Give correct path for files tables-*.sql, which are now in
install/sql/ instead of the top source directory
+ Install images/ and themes/ directories in the web area
.
* Added support for SQLite (closes: #407698, #407700)
+ debian/control:
- Depends on the php*-sqlite* packages
- Added SQLite to the list of supported DBMS
+ debian/webcalendar.config: Added sqlite to the dbc_dbtypes list
+ debian/webcalendar.links: Added link for tables-sqlite.sql
.
* debian/preinst: Added maintainer script for removing the
configuration file /etc/webcalendar/translations/Japanese-utf8.txt
left behind by version 1.0.5. The md5sum is checked before removal.
.
[ Elizabeth Bevilacqua ]
* dpatches adapted for 1.1.2:
+ 06_send-reminder
Files:
5e5506be09af244b7b2ffc7cefce237d 909 web optional webcalendar_1.1.2-1.dsc
a4987178c3f63292c4bed1e7322fbed6 1235041 web optional
webcalendar_1.1.2.orig.tar.gz
09aa12ad67bad200ca6379a6faf4dc01 31985 web optional webcalendar_1.1.2-1.diff.gz
7540a372fc226be2e068658b880d9327 1259768 web optional
webcalendar_1.1.2-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFGSZS0k3oga0pdcv4RAm7eAJ9ybc7GEypKuslfdMCUpPcAJFYsuQCfeU6u
2Au1Gb/LsovYBSbOXlgMPYM=
=/mUy
-END PGP SIGNATURE-
Accepted:
webcalendar_1.1.2-1.diff.gz
to pool/main/w/webcalendar/webcalendar_1.1.2-1.diff.gz
webcalendar_1.1.2-1.dsc
to pool/main/w/webcalendar/webcalendar_1.1.2-1.dsc
webcalendar_1.1.2-1_all.deb
to pool/main/w/webcalendar/webcalendar_1.1.2-1_all.deb
webcalendar_1.1.2.orig.tar.gz
to pool/main/w/webcalendar/webcalendar_1.1.2.orig.tar.gz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cjk 4.7.0+git20070504-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 11 May 2007 00:35:17 +0200 Source: cjk Binary: latex-cjk-common latex-cjk-japanese latex-cjk-all cjk-latex latex-cjk-korean latex-cjk-thai latex-cjk-chinese Architecture: source all i386 Version: 4.7.0+git20070504-2 Distribution: unstable Urgency: low Maintainer: Danai SAE-HAN (ééè) [EMAIL PROTECTED] Changed-By: Danai SAE-HAN (ééè) [EMAIL PROTECTED] Description: cjk-latex - installs all LaTeX CJK packages latex-cjk-all - installs all LaTeX CJK packages latex-cjk-chinese - Chinese module of LaTeX CJK latex-cjk-common - LaTeX macro package for CJK (Chinese/Japanese/Korean) latex-cjk-japanese - Japanese module of LaTeX CJK latex-cjk-korean - Korean module of LaTeX CJK latex-cjk-thai - Thai module of LaTeX CJK Changes: cjk (4.7.0+git20070504-2) unstable; urgency=low . * [changelog,TODO] Small cleanup. Thanks to Frank Küster. * [control] Don't depend on tetex-base anymore. Thanks to Frank Küster. Files: 76a8294d208735eeb7702e8a58c59001 908 tex optional cjk_4.7.0+git20070504-2.dsc e9897d8c3c1af97c56012b725b50b43f 884950 tex optional cjk_4.7.0+git20070504-2.diff.gz 2a3c0525c6a09cca4ca7f361cfb06468 236730 tex optional latex-cjk-common_4.7.0+git20070504-2_i386.deb 0c00b1b6116eb5649dac93ad6530564e 63222 tex optional latex-cjk-chinese_4.7.0+git20070504-2_i386.deb eea97749ffa13a686767499247a56060 37454 tex optional latex-cjk-japanese_4.7.0+git20070504-2_i386.deb 4d16cd8ebd99654379c9a5dbeb9fc52c 22694 tex optional latex-cjk-korean_4.7.0+git20070504-2_all.deb fd29367ca4357a2320d12bd4fa09cbc2 708408 tex optional latex-cjk-thai_4.7.0+git20070504-2_all.deb f8f7fda9e81e4adcd40f21c430787358 902 tex optional latex-cjk-all_4.7.0+git20070504-2_all.deb 028ff1f05906d2e9674641f3b2cb984d 870 tex optional cjk-latex_4.7.0+git20070504-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSZl2+xs9YyJS+hoRAiC5AKCtpF0V9hdKOYuetdHWuIsVSDPYGgCgh6lY xBoECo+nTgXOUIyzMthIZX0= =ijyL -END PGP SIGNATURE- Accepted: cjk-latex_4.7.0+git20070504-2_all.deb to pool/main/c/cjk/cjk-latex_4.7.0+git20070504-2_all.deb cjk_4.7.0+git20070504-2.diff.gz to pool/main/c/cjk/cjk_4.7.0+git20070504-2.diff.gz cjk_4.7.0+git20070504-2.dsc to pool/main/c/cjk/cjk_4.7.0+git20070504-2.dsc latex-cjk-all_4.7.0+git20070504-2_all.deb to pool/main/c/cjk/latex-cjk-all_4.7.0+git20070504-2_all.deb latex-cjk-chinese_4.7.0+git20070504-2_i386.deb to pool/main/c/cjk/latex-cjk-chinese_4.7.0+git20070504-2_i386.deb latex-cjk-common_4.7.0+git20070504-2_i386.deb to pool/main/c/cjk/latex-cjk-common_4.7.0+git20070504-2_i386.deb latex-cjk-japanese_4.7.0+git20070504-2_i386.deb to pool/main/c/cjk/latex-cjk-japanese_4.7.0+git20070504-2_i386.deb latex-cjk-korean_4.7.0+git20070504-2_all.deb to pool/main/c/cjk/latex-cjk-korean_4.7.0+git20070504-2_all.deb latex-cjk-thai_4.7.0+git20070504-2_all.deb to pool/main/c/cjk/latex-cjk-thai_4.7.0+git20070504-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xen-tools 3.3-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 May 2007 19:09:09 +0200 Source: xen-tools Binary: xen-tools Architecture: source all Version: 3.3-1 Distribution: unstable Urgency: low Maintainer: Roland Stigge [EMAIL PROTECTED] Changed-By: Radu Spineanu [EMAIL PROTECTED] Description: xen-tools - Tools to manage debian XEN virtual servers Closes: 419561 421174 Changes: xen-tools (3.3-1) unstable; urgency=low . [ Steve Kemp ] * New upstream release v3.3 - Refuse to delete running guests. (Closes: #419561) - Updated the package Recommends (Closes: #421174) Files: 7b36980050dda6af882505434a4b4d9e 647 utils extra xen-tools_3.3-1.dsc dc18ccc26d6595e710e8c66efff8b1cc 107062 utils extra xen-tools_3.3.orig.tar.gz 743240ae2e8c0f0bf901398b862b296f 19468 utils extra xen-tools_3.3-1.diff.gz f5639580a4f5e45d33a0d16cbf47e14e 126766 utils extra xen-tools_3.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSZvBJkMZOMmr+9MRAk5XAJ4+JfeGnjcwHaNogwg/ZHhQF2Ua9gCcCBEg t0kbv3SNHJGOsr+o9zloDQw= =FZzi -END PGP SIGNATURE- Accepted: xen-tools_3.3-1.diff.gz to pool/main/x/xen-tools/xen-tools_3.3-1.diff.gz xen-tools_3.3-1.dsc to pool/main/x/xen-tools/xen-tools_3.3-1.dsc xen-tools_3.3-1_all.deb to pool/main/x/xen-tools/xen-tools_3.3-1_all.deb xen-tools_3.3.orig.tar.gz to pool/main/x/xen-tools/xen-tools_3.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xen-shell 1.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 12 May 2007 19:04:51 +0300 Source: xen-shell Binary: xen-shell Architecture: source all Version: 1.2-1 Distribution: unstable Urgency: low Maintainer: Radu Spineanu [EMAIL PROTECTED] Changed-By: Radu Spineanu [EMAIL PROTECTED] Description: xen-shell - Console based Xen administration utility Changes: xen-shell (1.2-1) unstable; urgency=low . * New Upstream release - Two new commands were added: pause unpause. Files: 14e186a890889cd9394142653eb07d85 599 utils extra xen-shell_1.2-1.dsc 3c995d747b1aecd618bc0fe4ed3f7cfc 21168 utils extra xen-shell_1.2.orig.tar.gz 81115ec9d94a8d6173687788b7bd4fd2 2114 utils extra xen-shell_1.2-1.diff.gz 52158289b29b60f7270bcd8abf842269 26118 utils extra xen-shell_1.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSZvQJkMZOMmr+9MRAsnEAJ9vGA6G6hKVVIDU7Ds1HtYAlMI+LwCeIQCR yfUBEbSRNzb4tGDNu2hW3LM= =GFCl -END PGP SIGNATURE- Accepted: xen-shell_1.2-1.diff.gz to pool/main/x/xen-shell/xen-shell_1.2-1.diff.gz xen-shell_1.2-1.dsc to pool/main/x/xen-shell/xen-shell_1.2-1.dsc xen-shell_1.2-1_all.deb to pool/main/x/xen-shell/xen-shell_1.2-1_all.deb xen-shell_1.2.orig.tar.gz to pool/main/x/xen-shell/xen-shell_1.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted latex-cjk-japanese-wadalab 0.20050817-13 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 13 May 2007 18:19:09 +0200
Source: latex-cjk-japanese-wadalab
Binary: latex-cjk-japanese-wadalab
Architecture: source all
Version: 0.20050817-13
Distribution: unstable
Urgency: high
Maintainer: Danai SAE-HAN (ééè) [EMAIL PROTECTED]
Changed-By: Danai SAE-HAN (ééè) [EMAIL PROTECTED]
Description:
latex-cjk-japanese-wadalab - type1 and tfm DNP Japanese fonts for latex-cjk
Closes: 422399
Changes:
latex-cjk-japanese-wadalab (0.20050817-13) unstable; urgency=high
.
* Urgency is set to high because of an FTBFS bug fix.
* [control]
- Build-Depend on texlive-font-utils, which provides
vptovf. This fixes FTBFS: Can't exec vptovf: No such file
or directory at makeuniwada.pl line 120 (Closes: #422399).
Thanks to Lucas Nussbaum;
- change tetex-bin to tetex-extra;
- prefer TeXlive over teTeX in the Build-Dependencies and Dependencies;
- minor cleanup, and add dependencies on ${misc:Depends}.
Thanks to Florent Rougon.
* [rules] add a few arguments after dh_testdir when cleaning, to make
sure we're deleting the correct directory. Thanks to Florent Rougon
* [watch] clean it up, and locally force the version numbers of most
packages.
Files:
abb2cca8335ff8e51f94fcce0c2f7b18 849 tex optional
latex-cjk-japanese-wadalab_0.20050817-13.dsc
9e6ff683f03abdb53ab65c37102ed644 113673 tex optional
latex-cjk-japanese-wadalab_0.20050817-13.diff.gz
983b0f0b1cb04a89f4cc03bd4e7735f5 18373048 tex optional
latex-cjk-japanese-wadalab_0.20050817-13_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGSZ3f+xs9YyJS+hoRAt+6AJ0ehvHgh2GbWvfUpUC56T/KzZnyKQCfRvC7
nfetMA5tQo+CKGQNZtGwX4U=
=y8Sp
-END PGP SIGNATURE-
Accepted:
latex-cjk-japanese-wadalab_0.20050817-13.diff.gz
to
pool/main/l/latex-cjk-japanese-wadalab/latex-cjk-japanese-wadalab_0.20050817-13.diff.gz
latex-cjk-japanese-wadalab_0.20050817-13.dsc
to
pool/main/l/latex-cjk-japanese-wadalab/latex-cjk-japanese-wadalab_0.20050817-13.dsc
latex-cjk-japanese-wadalab_0.20050817-13_all.deb
to
pool/main/l/latex-cjk-japanese-wadalab/latex-cjk-japanese-wadalab_0.20050817-13_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-networkx 0.34-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 10:59:02 +0200 Source: python-networkx Binary: python-networkx Architecture: source all Version: 0.34-2 Distribution: unstable Urgency: low Maintainer: Cyril Brulebois [EMAIL PROTECTED] Changed-By: Cyril Brulebois [EMAIL PROTECTED] Description: python-networkx - tool to manipulate and study more than complex networks Closes: 423981 Changes: python-networkx (0.34-2) unstable; urgency=low . * Added a versioned B-D on python-suppport (= 0.6.4) since #422436 is fixed in this version, and on python-all-dev (= 2.3.5-11), according to the Python Policy. * Dropped the manual egg renaming, which isn't needed anymore, and even fails with the new python-support (Closes: #423981). * Turned setup.py usage into setup_egg.py usage. 20_egg_support patch dropped accordingly. * Added a TODO file so as not to forget TODO items for next uploads. * Added a find/rm to remove some .cvsignore files, now installed after the switch to setup_egg.py. * Adjusted README.Debian and Recommends:, since python-yaml is now packaged, and added instructions to run the testsuite from a python interpreter. Files: 96487f5638c0dd80e7ca283628f5ee59 811 graphics optional python-networkx_0.34-2.dsc 231795877b1818bfb2fa5a8d29c6affc 5340 graphics optional python-networkx_0.34-2.diff.gz 7984fa7ff78d642fedf4c68d266ef8ab 387650 graphics optional python-networkx_0.34-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaOkB01zfu119ZkRAvwTAJsH70BLfNKi4TMdb8a/JaynJzmwuQCeK1v0 VsIGqgPHWtTMghCgSDpb22Y= =WwHj -END PGP SIGNATURE- Accepted: python-networkx_0.34-2.diff.gz to pool/main/p/python-networkx/python-networkx_0.34-2.diff.gz python-networkx_0.34-2.dsc to pool/main/p/python-networkx/python-networkx_0.34-2.dsc python-networkx_0.34-2_all.deb to pool/main/p/python-networkx/python-networkx_0.34-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted numactl 0.9.11-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 21:57:55 +1000 Source: numactl Binary: libnuma-dbg libnuma1 libnuma-dev numactl Architecture: source i386 Version: 0.9.11-4 Distribution: unstable Urgency: low Maintainer: Ian Wienand [EMAIL PROTECTED] Changed-By: Ian Wienand [EMAIL PROTECTED] Description: libnuma-dbg - Debug package for libnuma libnuma-dev - Development files for libnuma libnuma1 - Libraries for controlling NUMA policy numactl- NUMA scheduling and memory placement tool Closes: 423182 423771 Changes: numactl (0.9.11-4) unstable; urgency=low . * Closes: #423771 -- drop hppa and s390 due to no kernel support, add mipsel, thanks Steve Langasek * Closes: #423182 -- Install static library; add patches/static-lib.patch, update libnuma-dev.install. Thanks Samuel Thibault Files: d86ff9b7f47059b959eb5ae7efbc6a92 815 admin optional numactl_0.9.11-4.dsc 7aa621bf467ebedc17075a63644c7528 5694 admin optional numactl_0.9.11-4.diff.gz 1e5f52331e63413ca3681a9a1d996d43 27158 admin optional numactl_0.9.11-4_i386.deb a4999141f801edb62c8d8204c925fdf8 15482 libs optional libnuma1_0.9.11-4_i386.deb 9ec868aa6ed35b4ba1da0a4c6fb9088d 23482 libdevel extra libnuma-dev_0.9.11-4_i386.deb f7c84424136c1d52a597ff3de9246c0f 38288 libdevel extra libnuma-dbg_0.9.11-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaLdWDlSU/gp6ecRAiTjAJ4tDhLP7QXIJs6jdR1sfmh2hehOjwCfcvUQ EokSvow8Dng/IxDirg54DfE= =nQGh -END PGP SIGNATURE- Accepted: libnuma-dbg_0.9.11-4_i386.deb to pool/main/n/numactl/libnuma-dbg_0.9.11-4_i386.deb libnuma-dev_0.9.11-4_i386.deb to pool/main/n/numactl/libnuma-dev_0.9.11-4_i386.deb libnuma1_0.9.11-4_i386.deb to pool/main/n/numactl/libnuma1_0.9.11-4_i386.deb numactl_0.9.11-4.diff.gz to pool/main/n/numactl/numactl_0.9.11-4.diff.gz numactl_0.9.11-4.dsc to pool/main/n/numactl/numactl_0.9.11-4.dsc numactl_0.9.11-4_i386.deb to pool/main/n/numactl/numactl_0.9.11-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ilohamail 0.8.14-0rc3sid5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:49:51 +0300 Source: ilohamail Binary: ilohamail Architecture: source all Version: 0.8.14-0rc3sid5 Distribution: unstable Urgency: low Maintainer: Joerg Jaspert [EMAIL PROTECTED] Changed-By: Radu Spineanu [EMAIL PROTECTED] Description: ilohamail - Light weight yet full featured multilingual web-based IMAP/POP3 c Closes: 423841 423852 Changes: ilohamail (0.8.14-0rc3sid5) unstable; urgency=low . * Fixed initial installation error (if $2 was not set). (closes: #423841) * The Apache-ssl debconf value was in different case than the one ilohamail was using. Thanks to Matthew Exley for the patches. (closes: #423852) Files: 358c119b7fc09826c25e2ee850a311d6 669 web optional ilohamail_0.8.14-0rc3sid5.dsc 6cca8b656ed9182e7cbdbac49b6974c6 81336 web optional ilohamail_0.8.14-0rc3sid5.diff.gz 2d550e07c227e8750a26ff06ea0ae7dc 381000 web optional ilohamail_0.8.14-0rc3sid5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaQoJkMZOMmr+9MRApVGAJ921L4C21DtGk7NenZUl1YD64+dqACdHqeW 0DIEZqo349UyrVpLkWuIsGU= =2QsZ -END PGP SIGNATURE- Accepted: ilohamail_0.8.14-0rc3sid5.diff.gz to pool/main/i/ilohamail/ilohamail_0.8.14-0rc3sid5.diff.gz ilohamail_0.8.14-0rc3sid5.dsc to pool/main/i/ilohamail/ilohamail_0.8.14-0rc3sid5.dsc ilohamail_0.8.14-0rc3sid5_all.deb to pool/main/i/ilohamail/ilohamail_0.8.14-0rc3sid5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bchunk 1.2.0-6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:17:00 +0200 Source: bchunk Binary: bchunk Architecture: source i386 Version: 1.2.0-6 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: bchunk - CD image format conversion from bin/cue to iso/cdr Changes: bchunk (1.2.0-6) unstable; urgency=low . * Fixed lintian warning. Files: 60d916aa8cfd5a27bb55f243de8c0de4 561 otherosfs optional bchunk_1.2.0-6.dsc 6d37af431c8f4f37fa55d7d41c936429 3014 otherosfs optional bchunk_1.2.0-6.diff.gz 2dc8973b7ad43edd4107f154698cc62f 13502 otherosfs optional bchunk_1.2.0-6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaTl+C5cwEsrK54RAtk4AJoDdp/wqO/0HCplv+jTzlHYrjWX/QCgxDlJ OZpD/2vagSD3fJxyk9QyU28= =XO8W -END PGP SIGNATURE- Accepted: bchunk_1.2.0-6.diff.gz to pool/main/b/bchunk/bchunk_1.2.0-6.diff.gz bchunk_1.2.0-6.dsc to pool/main/b/bchunk/bchunk_1.2.0-6.dsc bchunk_1.2.0-6_i386.deb to pool/main/b/bchunk/bchunk_1.2.0-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted amule 2.1.3-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Tue, 15 May 2007 13:58:38 +0200
Source: amule
Binary: amule amule-daemon amule-common amule-utils amule-utils-gui
Architecture: source i386 all
Version: 2.1.3-2
Distribution: unstable
Urgency: low
Maintainer: Adeodato Simó [EMAIL PROTECTED]
Changed-By: Adeodato Simó [EMAIL PROTECTED]
Description:
amule - client for the eD2k and Kad networks, like eMule
amule-common - common files for the rest of aMule packages
amule-daemon - non-graphic version of aMule, a client for the eD2k and Kad
netwo
amule-utils - utilities for aMule (command-line version)
amule-utils-gui - graphic utilities for aMule
Closes: 384344 404557
Changes:
amule (2.1.3-2) unstable; urgency=low
.
* The Not only bureaucracy release.
.
* Add patch to unconditionally set the type of search to Global. Thanks
to Robert Millan for the idea/patch. (Let's say this closes: #384344.)
.
* Remove diversions in amule.preinst in addition to amule-utils.preinst,
since otherwise there'll be dangling diversions on systems where only
amule is installed. Thanks to Javier Fernandez-Sanguino Peña for the
diagnosis. (Closes: #404557)
.
* Use ${source:Version} instead of ${Source-Version}.
.
* Move myself from Uploaders to Maintainer, at Julien's request.
Files:
62adf8342c64f7baa160ba3de6926525 863 x11 optional amule_2.1.3-2.dsc
411d256dbfcacc8fb4d6d0d65917a0e9 18596 x11 optional amule_2.1.3-2.diff.gz
eb8cce5880f0bb746467d208f0d79441 1261310 x11 optional amule_2.1.3-2_i386.deb
a088820746954f81028b8427d086f65b 384540 x11 optional
amule-utils_2.1.3-2_i386.deb
c57220ebfe463b7fa8ffb8cffcd27c2b 969414 x11 optional
amule-utils-gui_2.1.3-2_i386.deb
a3eab4ae013f6bbac97732e222f630d8 936772 x11 optional
amule-daemon_2.1.3-2_i386.deb
fa79d88c5f5e09e0fd74f9e70d998322 1579512 x11 optional
amule-common_2.1.3-2_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Signed by Adeodato Simó [EMAIL PROTECTED]
iEYEARECAAYFAkZJo2MACgkQgyNlRdHEGIIDagCgkFLnCUjZPeKPiUmNubZoQT4o
ADIAnRIuCG+ns+pSruKjEcUPa2dPDrzV
=YU25
-END PGP SIGNATURE-
Accepted:
amule-common_2.1.3-2_all.deb
to pool/main/a/amule/amule-common_2.1.3-2_all.deb
amule-daemon_2.1.3-2_i386.deb
to pool/main/a/amule/amule-daemon_2.1.3-2_i386.deb
amule-utils-gui_2.1.3-2_i386.deb
to pool/main/a/amule/amule-utils-gui_2.1.3-2_i386.deb
amule-utils_2.1.3-2_i386.deb
to pool/main/a/amule/amule-utils_2.1.3-2_i386.deb
amule_2.1.3-2.diff.gz
to pool/main/a/amule/amule_2.1.3-2.diff.gz
amule_2.1.3-2.dsc
to pool/main/a/amule/amule_2.1.3-2.dsc
amule_2.1.3-2_i386.deb
to pool/main/a/amule/amule_2.1.3-2_i386.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dialog 1.1-20070514-1 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:11:00 +0200 Source: dialog Binary: dialog Architecture: source powerpc Version: 1.1-20070514-1 Distribution: unstable Urgency: low Maintainer: Santiago Vila [EMAIL PROTECTED] Changed-By: Santiago Vila [EMAIL PROTECTED] Description: dialog - Displays user-friendly dialog boxes from shell scripts Closes: 418905 423732 Changes: dialog (1.1-20070514-1) unstable; urgency=low . * New upstream release. * Fixed timeout regression (Closes: #418905). * Fixed tailbox regression (Closes: #423732). Files: 44338aa3224367f0f5d671b7b4427d84 593 misc optional dialog_1.1-20070514-1.dsc 1a5dd79088ac3ba3047b48e7efaea8d1 365832 misc optional dialog_1.1-20070514.orig.tar.gz 3952d8738a186721eb02a9aff8341080 8876 misc optional dialog_1.1-20070514-1.diff.gz 68af9d4389661324d7e73e3716b0881e 259570 misc optional dialog_1.1-20070514-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaShd9Uuvj7yPNYRAsEFAKCwWE6XndZ8chfL0E69gPmNqc+JmQCePSGa wZrTTTgF9NOkrZLWSwL5zcc= =TrFD -END PGP SIGNATURE- Accepted: dialog_1.1-20070514-1.diff.gz to pool/main/d/dialog/dialog_1.1-20070514-1.diff.gz dialog_1.1-20070514-1.dsc to pool/main/d/dialog/dialog_1.1-20070514-1.dsc dialog_1.1-20070514-1_powerpc.deb to pool/main/d/dialog/dialog_1.1-20070514-1_powerpc.deb dialog_1.1-20070514.orig.tar.gz to pool/main/d/dialog/dialog_1.1-20070514.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xarchiver 0.4.6-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:37:00 +0200 Source: xarchiver Binary: xarchiver Architecture: source i386 Version: 0.4.6-3 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: xarchiver - GTK frontend for most used compression formats Changes: xarchiver (0.4.6-3) unstable; urgency=low . * Removed superfluous files in /usr/share/doc/xarchiver. Files: e3b0c47a9a3276921870a2633d60c351 613 x11 optional xarchiver_0.4.6-3.dsc 2fd2cdf0706ae1aba5d4702327e20deb 9218 x11 optional xarchiver_0.4.6-3.diff.gz beb8cbf3c1af760a78639fbce98eccfd 373726 x11 optional xarchiver_0.4.6-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaqo+C5cwEsrK54RAoMoAJ92G02pP8sXvLwS6fWSxYoAkFvScwCdEk0b ZBXQ1QJZdGCJ2c14qyJc/Yo= =CjTD -END PGP SIGNATURE- Accepted: xarchiver_0.4.6-3.diff.gz to pool/main/x/xarchiver/xarchiver_0.4.6-3.diff.gz xarchiver_0.4.6-3.dsc to pool/main/x/xarchiver/xarchiver_0.4.6-3.dsc xarchiver_0.4.6-3_i386.deb to pool/main/x/xarchiver/xarchiver_0.4.6-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xarchive 0.2.8.6+debian-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:44:00 +0200 Source: xarchive Binary: xarchive Architecture: source i386 Version: 0.2.8.6+debian-4 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: xarchive - GTK frontend for most used compression tools Changes: xarchive (0.2.8.6+debian-4) unstable; urgency=low . * Removed depends to bash. Files: 2a8dbf67572aeb3e991cae07f99fadff 631 x11 optional xarchive_0.2.8.6+debian-4.dsc 8b92c70688db9f98f60b434700f3e789 32793 x11 optional xarchive_0.2.8.6+debian-4.diff.gz 6eb8c6020095d27267c9444829df4d2c 51942 x11 optional xarchive_0.2.8.6+debian-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSaut+C5cwEsrK54RAs8qAJ9pqdlWHSF/gbqYXCIBYs/ZRMrEnACeORq2 bbY05qIxY6sy1WO9O3T2CcM= =ndkJ -END PGP SIGNATURE- Accepted: xarchive_0.2.8.6+debian-4.diff.gz to pool/main/x/xarchive/xarchive_0.2.8.6+debian-4.diff.gz xarchive_0.2.8.6+debian-4.dsc to pool/main/x/xarchive/xarchive_0.2.8.6+debian-4.dsc xarchive_0.2.8.6+debian-4_i386.deb to pool/main/x/xarchive/xarchive_0.2.8.6+debian-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wmii 3.6~rc2+20070501-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 14:52:00 +0200 Source: wmii Binary: wmii Architecture: source i386 Version: 3.6~rc2+20070501-2 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: wmii - lightweight tabbed and tiled X11 window manager, version 3 Changes: wmii (3.6~rc2+20070501-2) unstable; urgency=low . * Added lintian override. * Do not compile wmiir statically. Files: 7a4f411558e5568e44acf123941dd7a5 646 x11 optional wmii_3.6~rc2+20070501-2.dsc aa0ac3f1374982c233a458273a4e40da 4771 x11 optional wmii_3.6~rc2+20070501-2.diff.gz c34a7a66dc5babfb891a62567edbc5de 75534 x11 optional wmii_3.6~rc2+20070501-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSa2M+C5cwEsrK54RAojSAJ9uvHhMAN+rL0DtqSI8/KnTzVS8NACgykYc 5Bz/yFDPbmE85QNHaEfapOU= =LiqN -END PGP SIGNATURE- Accepted: wmii_3.6~rc2+20070501-2.diff.gz to pool/main/w/wmii/wmii_3.6~rc2+20070501-2.diff.gz wmii_3.6~rc2+20070501-2.dsc to pool/main/w/wmii/wmii_3.6~rc2+20070501-2.dsc wmii_3.6~rc2+20070501-2_i386.deb to pool/main/w/wmii/wmii_3.6~rc2+20070501-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted osdclock 0.5-19 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 15:05:00 +0200 Source: osdclock Binary: osdclock Architecture: source i386 Version: 0.5-19 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: osdclock - Clock using the XOSD library Changes: osdclock (0.5-19) unstable; urgency=low . * Adjusted manpage section. Files: 7417af4b908798580948f6de9b7fc92b 617 utils optional osdclock_0.5-19.dsc bbc8ed62ec64df376d54ba1ed4ca8de2 5480 utils optional osdclock_0.5-19.diff.gz 73e9293f279464377f7ff90baf03ea75 7934 utils optional osdclock_0.5-19_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGSbAa+C5cwEsrK54RAllDAKCvGuA3ZvMTm5aJFmZVoZ/EwAfF8ACfcbjy B6IoWpfQmS6+G/gSofyaQjw= =cTOE -END PGP SIGNATURE- Accepted: osdclock_0.5-19.diff.gz to pool/main/o/osdclock/osdclock_0.5-19.diff.gz osdclock_0.5-19.dsc to pool/main/o/osdclock/osdclock_0.5-19.dsc osdclock_0.5-19_i386.deb to pool/main/o/osdclock/osdclock_0.5-19_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted texinfo 4.8.dfsg.1-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 15 May 2007 15:00:37 +0200 Source: texinfo Binary: texinfo info Architecture: source i386 Version: 4.8.dfsg.1-5 Distribution: unstable Urgency: low 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: 422518 Changes: texinfo (4.8.dfsg.1-5) unstable; urgency=low . * adjust suggests to include texlive-generic-recommended and remove tetex (Closes: #422518) * lintian fixes: - move dh compat setting from rules to debian/compat - save control file in UTF8 Files: 1f6ad96f3727761e054171f6f3c06672 681 doc standard texinfo_4.8.dfsg.1-5.dsc 217aed36ef8f33addc4be806b8bd462b 102001 doc standard texinfo_4.8.dfsg.1-5.diff.gz 500b21d8819e0b1ca83d799a4ff7126e 679546 text standard texinfo_4.8.dfsg.1-5_i386.deb a6d9ae58ffe03dcba3a1e4504d08f8f9 163830 doc important info_4.8.dfsg.1-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFGSbDB0r9KownFsJQRAnVXAJ9YE8XWuGue/mcGiBCn4JuOSLzaSgCYpvFK nyYFzfSNGQIS1MR6A/lbsA== =50z1 -END PGP SIGNATURE- Accepted: info_4.8.dfsg.1-5_i386.deb to pool/main/t/texinfo/info_4.8.dfsg.1-5_i386.deb texinfo_4.8.dfsg.1-5.diff.gz to pool/main/t/texinfo/texinfo_4.8.dfsg.1-5.diff.gz texinfo_4.8.dfsg.1-5.dsc to pool/main/t/texinfo/texinfo_4.8.dfsg.1-5.dsc texinfo_4.8.dfsg.1-5_i386.deb to pool/main/t/texinfo/texinfo_4.8.dfsg.1-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
