Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
* Christian Marillat: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. Accoridng to Policy section 4.4, it's okay to list other changes (for example, upstream changes) in the Debian changelog. Do you want to say that Policy is wrong? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Florian Weimer [EMAIL PROTECTED] writes: * Christian Marillat: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. Accoridng to Policy section 4.4, it's okay to list other changes (for example, upstream changes) in the Debian changelog. Where are you reading that ? Here is the relevant policy : , | Changes in the Debian version of the package should be briefly | explained in the Debian changelog file `debian/changelog'.[1] This | includes modifications made in the Debian package compared to the | upstream one as well as other changes and updates to the package. [2] | | [...] | | [2] Although there is nothing stopping an author who is also the Debian | maintainer from using this changelog for all their changes, it will | have to be renamed if the Debian and upstream maintainers become | different people. In such a case, however, it might be better to | maintain the package as a non-native package. ` Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
* Christian Marillat: Florian Weimer [EMAIL PROTECTED] writes: * Christian Marillat: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. Accoridng to Policy section 4.4, it's okay to list other changes (for example, upstream changes) in the Debian changelog. Where are you reading that ? An upstream change is a change to the Debian package, too, and listing them is expressly allowed under the other changes option. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Christian Marillat [EMAIL PROTECTED] writes: Package: libgtk2.0-0 Version: 2.8.17-1 Severity: serious Justification: Policy 4.4 Hi, Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. While in this particular case I think the level of detail is possibly overkill, the Debian changelog file is in a standard format (unlike upstream) and therefore can be parsed and shown by automated tools from apt-listchanges to the QA pages and the upload notifications. Accordingly, I think it is the appropriate place to record any *important* changes to the package, whether they were made upstream or by the Debian package maintainer. This particularly includes changes that someone trying to analyze the history of supported major features or critical bugs is likely to need to know about. Accordingly, for my packages, I mention (as sub-bullets to the * New upstream release bullet) any upstream change that: * Closes a Debian bug (and include the bug closer). * Is a major feature enhancement or a major bug fix likely to be of interest to a substantial percentage of the users of the package. * Is of special interest to Debian users. (Requiring configuration changes or changes in the way the package is used in Debian that aren't quite worthy of a NEWS.Debian entry, for instance.) I'm happy to take criticism on what I mention and don't mention, but I personally find Debian changelogs that never mention *any* details of why a new upstream version was packaged to be unhelpful and really inferior. If one is packaging a new version that really has no Debian-related changes or which is just fixing minor bugs or adding minor new features, none of which of interest to the average user, a bare New upstream release makes sense. But I prefer to provide at least a line or two of detail, and as long as one doesn't overdo it, there isn't much drawback. A pure no upstream changes should be in the Debian changelog file policy would break down in a number of places. Some upstream changes I think everyone agrees should be listed there (such as CAN numbers for fixed security bugs). Note: I use apt-listchanges and read the changelog deltas for every package I upgrade on four different machines, so I am one of the people who has to page through lengthy changelogs. -- 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: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
* Russ Allbery: Accordingly, for my packages, I mention (as sub-bullets to the * New upstream release bullet) any upstream change that: * Closes a Debian bug (and include the bug closer). * Is a major feature enhancement or a major bug fix likely to be of interest to a substantial percentage of the users of the package. * Is of special interest to Debian users. (Requiring configuration changes or changes in the way the package is used in Debian that aren't quite worthy of a NEWS.Debian entry, for instance.) Listing security bug with a SECURITY: tag would be a nice, too. 8-) I'm happy to take criticism on what I mention and don't mention, but I personally find Debian changelogs that never mention *any* details of why a new upstream version was packaged to be unhelpful and really inferior. I agree completely. Listing important upstream changes and fixed Debian bugs is a service to our users. It also helps with software archaeology, in particular if upstream does not provide a concise or well-ordered changelog. A pure no upstream changes should be in the Debian changelog file policy would break down in a number of places. Some upstream changes I think everyone agrees should be listed there (such as CAN numbers for fixed security bugs). It's CVE names nowadays. 8-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possible conflict with XFree 4.5
On Sat, Apr 15, 2006 at 04:17:28PM +0300, gustavo halperin wrote: I think that we have a problem when the common library between XFree and /usr/lib are update in /usr/lib. I currently have XFree 4.5, when the library libfontconfig1 was update to version 2.3.2-1 was also updated the file libfontconfig.so to the version 1.0.4 but in the XFree (/usr/X11R6/lib/) this library still be the version 1. The problem came we we use programs like Gimp that must at least version 1.0.2 of this library. I solve this problem by link the libfontconfig in /usr/X11R6/lib to the newest library in /usr/lib. That is the solution or that is a Bug in Debian System ?? I assume that you're installing XFree86 4.5 by yourself, since it wasn't packaged for Debian. In that case, local installation conflicts are your problem to sort out. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Florian Weimer [EMAIL PROTECTED] writes: * Christian Marillat: Florian Weimer [EMAIL PROTECTED] writes: [...] Where are you reading that ? An upstream change is a change to the Debian package, too, and listing them is expressly allowed under the other changes option. I'm sorry but no. Read again. The Debian changelog is for Debian changes not upstream. For that we have a changelog file and a NEW file. Changes in the Debian version of the package should be briefly explained in the Debian changelog file `debian/changelog'.[1] This includes modifications made in the Debian package compared to the upstream one as well as other changes and updates to the package. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Lintian package-has-a-duplicate-relation
Hi folks,
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
However,
Depends: ${shlibs:Depends}, libmypackage1 (= ${Source-Version})
Will make lintian scream.
I could abandon the use of ${shlibs:Depends}, and list each dependencies
manually, but this is a bit annoying.
Any clever suggestions ?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
On Sun, Apr 16, 2006 at 12:02:42PM +0200, Christian Marillat wrote: Florian Weimer [EMAIL PROTECTED] writes: * Christian Marillat: Florian Weimer [EMAIL PROTECTED] writes: [...] Where are you reading that ? An upstream change is a change to the Debian package, too, and listing them is expressly allowed under the other changes option. I'm sorry but no. Read again. The Debian changelog is for Debian changes not upstream. For that we have a changelog file and a NEW file. Changes in the Debian version of the package should be briefly explained in the Debian changelog file `debian/changelog'.[1] This includes modifications made in the Debian package compared to the upstream one as well as other changes and updates to the package. Does it say that everything else is specifically excluded? Do you really have nothing better to do with your life than argue semantics about an ambiguous sentence[0]. Please get off this list and do something more productive with your time. [0]: One could well read it as, the Debian-specific changes, and also the upstream changes and anything else done to the package as a whole. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Light Desktop - meta package
#include hallo.h * Don Armstrong [Fri, Apr 14 2006, 02:02:17PM]: On Fri, 14 Apr 2006, Torsten Marek wrote: - eog As said, Gnome bloat. Use gqview or pornview. Well, don't take pornview or you'll soon have a bug report about politically incorrect package names;-) Try feh. Much, much more powerful, and much, much nicer. Much, much, much? Where? Some eye-catchers (collage, HTTP client builtin) but not much for daily use for a desktop system: - no picture browser GUI - no picture management function - image quality not sufficiently adaptable to system's performance Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
On Sun, Apr 16, 2006 at 12:18:58PM +0200, [EMAIL PROTECTED] wrote:
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
However,
Depends: ${shlibs:Depends}, libmypackage1 (= ${Source-Version})
Will make lintian scream.
I could abandon the use of ${shlibs:Depends}, and list each dependencies
manually, but this is a bit annoying.
Any clever suggestions ?
Why? If your library's ABI is changing with every revision, you should
be bumping the soversion.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
[EMAIL PROTECTED] wrote:
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
Why would you want to do that?
cu andreas
--
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.(c) Jasper Ffforde
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
* [EMAIL PROTECTED] [Sun, 16 Apr 2006 12:18:58 +0200]:
I could abandon the use of ${shlibs:Depends}, and list each dependencies
manually, but this is a bit annoying.
No, it is not annoying. It is an utterly incorrect thing to do, so
better forget that the idea ever crossed your mind. ;-)
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
You've come to the right place. At debian-devel we are always willing
to argue over the meanings of words.
-- seen on [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Daniel Stone [EMAIL PROTECTED] writes: R On Sun, Apr 16, 2006 at 12:02:42PM +0200, Christian Marillat wrote: Florian Weimer [EMAIL PROTECTED] writes: * Christian Marillat: Florian Weimer [EMAIL PROTECTED] writes: [...] Where are you reading that ? An upstream change is a change to the Debian package, too, and listing them is expressly allowed under the other changes option. I'm sorry but no. Read again. The Debian changelog is for Debian changes not upstream. For that we have a changelog file and a NEW file. Changes in the Debian version of the package should be briefly explained in the Debian changelog file `debian/changelog'.[1] This includes modifications made in the Debian package compared to the upstream one as well as other changes and updates to the package. Does it say that everything else is specifically excluded? Do you really have nothing better to do with your life than argue semantics about an ambiguous sentence[0]. Please get off this list and do something more productive with your time. PLONK Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
* Daniel Stone: Why? If your library's ABI is changing with every revision, you should be bumping the soversion. Or you shouldn't provide a DSO at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#354674: What on earth?
Le Ven 14 Avril 2006 01:58, David Nusinow a écrit : On Thu, Apr 13, 2006 at 07:09:55PM -0400, Adam C Powell IV wrote: *Think* for a moment about the consequences. This is not a simple rebuild, this is a serious problem. I agree and I take full responsibility for the issue. I'm sorry for the trouble. I'm fully willing to put back the .la files on request from the release team, who I should definitely have coordinated with beforehand. Note that I would have done so if I'd realized the magnitude of the problem, and not doing so was entirely my error. - David Nusinow I welcome the fact that you bear your responsabilities, that's a quality fewer of us have. Though, the .la problem is not the sole one the modular Xorg raised. - /usr/X11R6/bin/X disapearing broke login managers (gdm, kdm) - fonts transition was unanounced and users have either : * only non transitionned fonts if their xorg.conf was modified * only xorg ones if they use dexconf that's a mess. - a lot of build depends were missing, something that the first build on autobuilders revealed, which makes me wonder if the XSF knows about pbuilder and friends ? Well, knowing to apology is good, but knowing how to prepare a transition is also needed. I just can quote steve on this : » So far I'm very unimpressed with the resultant bug count from the » Xorg 7 transition. I can predict that the Xorg 7.0 will be the messiest debian will have to face in years, because everything is done in a hurry, and that each new uploads adds as many bugs (if not twice as many) as it solves. So maybe it's now time to calm down the upload rate (yeah unstable is broken, but it's too late for that anyway, and after all it's not called unstable for nothing), let's have some communication to have it fixed, instead of pile of clumsy patches. Could please the XSF communicate, and announce what that damn transition implies for *everybody*, instead of letting anybody finds out that their package is broken. I suggest [1] as a very good template for what communicating about a transition means. best regards, [1] http://lists.debian.org/debian-devel-announce/2005/07/msg1.html -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpRFolkhox8u.pgp Description: PGP signature
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 04:31:10PM +0200, Pierre Habouzit wrote: I welcome the fact that you bear your responsabilities, that's a quality fewer of us have. Though, the .la problem is not the sole one the modular Xorg raised. - /usr/X11R6/bin/X disapearing broke login managers (gdm, kdm) This is being rectified, as a perfunctory glance at -x will tell you. - fonts transition was unanounced and users have either : * only non transitionned fonts if their xorg.conf was modified * only xorg ones if they use dexconf that's a mess. This is being rectified. - a lot of build depends were missing, something that the first build on autobuilders revealed, which makes me wonder if the XSF knows about pbuilder and friends ? This is being rectified, obviously, but I'm sure the people doing the packaging appreciate your slight at their skills. Well, knowing to apology is good, but knowing how to prepare a transition is also needed. I just can quote steve on this : » So far I'm very unimpressed with the resultant bug count from the » Xorg 7 transition. I can predict that the Xorg 7.0 will be the messiest debian will have to face in years, because everything is done in a hurry, and that each new uploads adds as many bugs (if not twice as many) as it solves. So maybe it's now time to calm down the upload rate (yeah unstable is broken, but it's too late for that anyway, and after all it's not called unstable for nothing), let's have some communication to have it fixed, instead of pile of clumsy patches. So, let me get this straight: on one hand you're complaining about bugs, and on the other hand, you're complaining about bugs being fixed? The workload of the XSF members getting things fixed is very admirable. Could please the XSF communicate, and announce what that damn transition implies for *everybody*, instead of letting anybody finds out that their package is broken. I suggest [1] as a very good template for what communicating about a transition means. Thanks a lot for your help. David has posted a couple of messages on debian-devel-announce discussing the transition (including xlibs-dev), and what it means for everyone. Most of the transition was co-ordinated in excruciating detail, including a long time in experimental where testing failed to uncover these sorts of problems. The rest are purely transitive. You don't need a plan to tell you that fonts are being migrated, that Build-Depends are being added as they're being caught, or that the /usr/X11R6/bin situation is nearly totally fixed. This is unstable. Sometimes the name rings true. With regards the .la files: mea culpa. I was partially unaware of the full extent of the damage, and partially unaware that the release team considered it such a problem. If you really don't like it, wait a few days until the transition blows over and the coast is clear. It's one of the biggest transitions Debian has had, and sometimes the problems aren't always clear. (Hence the delay in experimental, waiting for testers.) Daniel signature.asc Description: Digital signature
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 04:31:10PM +0200, Pierre Habouzit wrote: - /usr/X11R6/bin/X disapearing broke login managers (gdm, kdm) - fonts transition was unanounced and users have either : * only non transitionned fonts if their xorg.conf was modified * only xorg ones if they use dexconf that's a mess. - a lot of build depends were missing, something that the first build on autobuilders revealed, which makes me wonder if the XSF knows about pbuilder and friends ? You're right about the xfonts issue. I thought we had compatibility symlinks in place to deal with this. I was wrong. I'm sorry. As for the build-depends, pbuilder is, as far as I've been able to understand it, completely incapable of handling such a massive beast as this. You can't point it easily at a custom repository in order to have it pull from there. If this has changed recently, I'd love to hear it, but when I was investigating this during the development of the packages I was unable to do it. Furthermore, the packages I pulled were autobuilding just fine on Ubuntu, so I had little reason to believe that they didn't have proper build-depends for Debian. Indeed, very few of the packages ftbfs'ed, and most of these were fixed within hours of being reported. Well, knowing to apology is good, but knowing how to prepare a transition is also needed. I just can quote steve on this : ? So far I'm very unimpressed with the resultant bug count from the ? Xorg 7 transition. I can predict that the Xorg 7.0 will be the messiest debian will have to face in years, because everything is done in a hurry, and that each new uploads adds as many bugs (if not twice as many) as it solves. I'd like for you to back this claim up. So far I've fixed dozens of bugs over the course of the past week at great personal and professional cost of my time, energy, and health. And I plan to keep whittling away at the bugs until the transition is as clean as I can possibly make it. But to say that I'm introducing more bugs than I'm fixing is insulting. So maybe it's now time to calm down the upload rate (yeah unstable is broken, but it's too late for that anyway, and after all it's not called unstable for nothing), let's have some communication to have it fixed, instead of pile of clumsy patches. I'm fixing bugs as fast as I can because that's what's needed right now. I'm willing to accidentally slip in a clumsy upload if it'll lead to a proper fix over the course of another day, especially if it allows me to fix 4 other bugs in the time frame I spent exhaustively testing every possibility. Could please the XSF communicate, and announce what that damn transition implies for *everybody*, instead of letting anybody finds out that their package is broken. I suggest [1] as a very good template for what communicating about a transition means. I communicated, to the best of my knowledge, what the transition meant in the past [0]. I wasn't aware that I would be breaking a large amount of packages until after I uploaded to unstable. These packages have largely been in use in Ubuntu for several months already. They have been in experimental for several months as well, during which time I fixed every bug that came in about them. I communicated with the release team what my plans were at all stages, and while I didn't realize the scope of the disruption, I did my absolute best to keep everyone involved informed. Every single change I've done to these packages has been documented on debian-x via the svn commits, so everyone could see what I've been doing if they cared to look. I have yet to file bugs against other packages that I've affected because I haven't had time. This is a serious problem, but I have hundreds of packages to actively look after during this transition and I'd appreciate any sort of help that can be offered. Anyway, I'm going to continue to work hard on this. If you want to help dig us out of it, I'll welcome any patches you care to submit that are up to your standards of quality. Until then though, feel free to kiss my ass. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 10:52:21AM -0400, David Nusinow wrote: As for the build-depends, pbuilder is, as far as I've been able to understand it, completely incapable of handling such a massive beast as this. You can't point it easily at a custom repository in order to have it pull from there. If this has changed recently, I'd love to hear it, but when I was investigating this during the development of the packages I was unable to do it. Furthermore, the packages I pulled were autobuilding just fine on Ubuntu, so I had little reason to believe that they didn't have proper build-depends for Debian. Indeed, very few of the packages ftbfs'ed, and most of these were fixed within hours of being reported. I should point out that the FTBFSing packages were ones that were repackaged from the ground up to be more sensible, not pure imports from Ubuntu. That being said, I agree with the thrust of David's mail. And, on my behalf, apologise to the release team for any disruption incurred to Etch. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#362505: via-rhine: probe of 0000:00:0f.0 failed with error -993193440
Processing commands for [EMAIL PROTECTED]: reassign 362505 kernel-image-2.6.8-3-686 Bug#362505: via-rhine: probe of :00:0f.0 failed with error -993193440 Bug reassigned from package `general' to `kernel-image-2.6.8-3-686'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362505: via-rhine: probe of 0000:00:0f.0 failed with error -993193440
reassign 362505 kernel-image-2.6.8-3-686 thanks Hi! Thanks for your bug report! This sounds like a kernel bug. Reassigning ti to the correct package. Regards, Bas. -- ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Christian, On Sun, Apr 16, 2006, Christian Marillat wrote: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. You're not in the perfect place to criticize the contents of Debian changelogs, see #244288. Be tolerant to your fellows, -- Loïc Minier [EMAIL PROTECTED] You can gtk_main_run, but you can't gtk_widget_hide. --danw, 19-jul-04 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Loïc Minier [EMAIL PROTECTED] writes: Christian, On Sun, Apr 16, 2006, Christian Marillat wrote: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. You're not in the perfect place to criticize the contents of Debian changelogs, see #244288. And ? Most of these entries have been removed, which is unfair. Christian
Re: Bug#354674: What on earth?
In-Reply-To: [EMAIL PROTECTED] On Sun, Apr 16, 2006 at 10:52:21AM -0400, David Nusinow wrote: As for the build-depends, pbuilder is, as far as I've been able to understand it, completely incapable of handling such a massive beast as this. You can't point it easily at a custom repository in order to have it pull from there. If this has changed recently, I'd love to hear it, but when I was investigating this during the development of the packages I was unable to do it. Furthermore, the packages I pulled were autobuilding just fine on Ubuntu, so I had little reason to believe that they didn't have proper build-depends for Debian. Indeed, very few of the packages ftbfs'ed, and most of these were fixed within hours of being reported. AFAICT, it's easy to achieve. See [1]. bindmount your /var/cache/pbuilder/results (or the place where you put your built packages) e.g. in /mnt/results/. Also add a hookscript starting with D that looks like: #!/bin/sh dpkg-scanpackages /mnt/results /dev/null /mnt/results/Packages echo file:///mnt/results ./ /etc/apt/sources.list apt-get update and I think you are done. I reckon this was not in pbuilder(8) but in the online user doc. I can predict that the Xorg 7.0 will be the messiest debian will have to face in years, because everything is done in a hurry, and that each new uploads adds as many bugs (if not twice as many) as it solves. I'd like for you to back this claim up. So far I've fixed dozens of bugs over the course of the past week at great personal and professional cost of my time, energy, and health. And I plan to keep whittling away at the bugs until the transition is as clean as I can possibly make it. well, like said, it's a bit late for that. And about your bug load, let me say it loud clear: the current load you are experiencing was created by your way to package X.org 7.0, not anticipating any of the problems. I won't say your current rate of bug fixing isn't remarkable outside from the current contexte. But please, when someone run into a wall, nobody will think that his survival is a remarkable thing. Could please the XSF communicate, and announce what that damn transition implies for *everybody*, instead of letting anybody finds out that their package is broken. I suggest [1] as a very good template for what communicating about a transition means. I communicated, to the best of my knowledge, what the transition meant in the past [0]. I wasn't aware that I would be breaking a large amount of packages until after I uploaded to unstable. These packages have largely been in use in Ubuntu for several months already. They have been in experimental for several months as well, during which time I fixed every bug that came in about them. I communicated with the release team what my plans were at all stages, and while I didn't realize the scope of the disruption, I did my absolute best to keep everyone involved informed. Every single change I've done to these packages has been documented on debian-x via the svn commits, so everyone could see what I've been doing if they cared to look. I'm shocked that you didn't anticipate *any* of the problems you ran into. after all, you've broken : *dm, fonts, made FTBFS a lot of programs linking against xlibs, ... That looks to me like beeing an reasonnably complete coverage of the things X.org is supposed to achieve. The affirmation This worked fine in ubuntu looks like a very loose quality quality test for a first upload of a totally new layout of an X server. I have yet to file bugs against other packages that I've affected because I haven't had time. [...] that should have been done *before* any of your moves. And that's exactly the RM's point, and mine also. Anyway, I'm going to continue to work hard on this. If you want to help dig us out of it, I'll welcome any patches you care to submit that are up to your standards of quality. I'm already fixing a huge load of RC bugs doing NMU to clean packages that are in a loosy shape since a lot of time, and that does not seem to have an active enough maintainer. I hope X.org does not qualify yet to those criteriums. Until then though, feel free to kiss my ass. You're welcome. [1] http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html#id267034 In-Reply-To: [EMAIL PROTECTED] - /usr/X11R6/bin/X disapearing broke login managers (gdm, kdm) This is being rectified, as a perfunctory glance at -x will tell you. Are you serious ? Do you read debian-glibc@ each time you upload a package ? please, if something has te be known related to a migration, it has to come from the team that launched that migration. It's not to the others developpers to go read -x, it's up to you to inform them. So I really expect that in a really near future I'll hear from you (as a team member of the QT-KDE team that packages kdm), that gdm maintainer will hear from you as well, and that
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Le dimanche 16 avril 2006 à 19:12 +0200, Christian Marillat a écrit : Loïc Minier [EMAIL PROTECTED] writes: Christian, On Sun, Apr 16, 2006, Christian Marillat wrote: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. You're not in the perfect place to criticize the contents of Debian changelogs, see #244288. And ? Most of these entries have been removed, which is unfair. Unfair? After having deliberately ignored all procedures for orphaning packages and filled changelogs with random crap, you are calling that cleaning unfair? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message numériquement signée
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Josselin Mouette [EMAIL PROTECTED] writes: Le dimanche 16 avril 2006 à 19:12 +0200, Christian Marillat a écrit : Loïc Minier [EMAIL PROTECTED] writes: Christian, On Sun, Apr 16, 2006, Christian Marillat wrote: Apparently you don't understand (or don't care), because this is the second time I file the same bug report (#344125), but as this package isn't a native package the upstream changelog should not be here. You're not in the perfect place to criticize the contents of Debian changelogs, see #244288. And ? Most of these entries have been removed, which is unfair. Unfair? After having deliberately ignored all procedures for orphaning packages and filled changelogs with random crap, you are calling that cleaning unfair? You are wrong. I've orphaned all my GNOME packages with the right entry in the Debian changelog. read again. Christian
Bug#362878: Info received (was Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Sebastien Bacher [EMAIL PROTECTED] If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362956: ITP: libcrypt-openssl-rsa-perl -- Perl module providing basic RSA functionality.
Package: wnpp Severity: wishlist Owner: Luk Claes [EMAIL PROTECTED] * Package name: libcrypt-openssl-rsa-perl Version : 0.23 Upstream Author : Ian Robertson [EMAIL PROTECTED] * URL : http://cpan.org/ * License : like Perl Programming Lang: Perl Description : Perl module providing basic RSA functionality. Provides a glue to the RSA functions in the OpenSSL library. In particular, it provides the following functionalities: create a key from a string, make a new key, save key to a string, save public portion of key to a string using format compatible with OpenSSL's command-line rsa tool, encrypt, decrypt, sign, verify, return the size in bytes of a key, check the validity of a key. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362953: ITP: libcrypt-openssl-dsa-perl -- Perl module which implements the DSA signature verification system.
Package: wnpp Severity: wishlist Owner: Luk Claes [EMAIL PROTECTED] * Package name: libcrypt-openssl-dsa-perl Version : 0.13 Upstream Author : T.J. Mather, E [EMAIL PROTECTED] * URL : http://cpan.org/ * License : like Perl Programming Lang: Perl Description : Perl module which implements the DSA signature verification system. A wrapper to the DSA (Digital Signature Algorithm) functions contained in the OpenSSL crypto library. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Le dimanche 16 avril 2006 à 19:24 +0200, Christian Marillat a écrit : You are wrong. I've orphaned all my GNOME packages with the right entry in the Debian changelog. read again. http://lists.debian.org/debian-devel-changes/2004/03/msg01789.html -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message numériquement signée
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 07:19:40PM +0200, Pierre HABOUZIT wrote: In-Reply-To: [EMAIL PROTECTED] On Sun, Apr 16, 2006 at 10:52:21AM -0400, David Nusinow wrote: I'd like for you to back this claim up. So far I've fixed dozens of bugs over the course of the past week at great personal and professional cost of my time, energy, and health. And I plan to keep whittling away at the bugs until the transition is as clean as I can possibly make it. well, like said, it's a bit late for that. And about your bug load, let me say it loud clear: the current load you are experiencing was created by your way to package X.org 7.0, not anticipating any of the problems. I won't say your current rate of bug fixing isn't remarkable outside from the current contexte. But please, when someone run into a wall, nobody will think that his survival is a remarkable thing. It's a bit late to back your claims up? Come on man, lay off the guy. David made a couple of mistakes in handling X in Debian. So did I. I made a ton more handling X outside of Debian. So what? He's apologised *repeatedly* for what he feels he needs to apologise for. Just move the hell on and stop being such a dick. I communicated, to the best of my knowledge, what the transition meant in the past [0]. I wasn't aware that I would be breaking a large amount of packages until after I uploaded to unstable. These packages have largely been in use in Ubuntu for several months already. They have been in experimental for several months as well, during which time I fixed every bug that came in about them. I communicated with the release team what my plans were at all stages, and while I didn't realize the scope of the disruption, I did my absolute best to keep everyone involved informed. Every single change I've done to these packages has been documented on debian-x via the svn commits, so everyone could see what I've been doing if they cared to look. I'm shocked that you didn't anticipate *any* of the problems you ran into. after all, you've broken : *dm, fonts, made FTBFS a lot of programs linking against xlibs, ... That looks to me like beeing an reasonnably complete coverage of the things X.org is supposed to achieve. The affirmation This worked fine in ubuntu looks like a very loose quality quality test for a first upload of a totally new layout of an X server. It worked fine in Ubuntu, across a couple of releases. It worked fine in experimental -- where I notice you haven't been testing. If you're concerned about xlibs-dev, maybe you should try subscribing to this list called debian-devel-announce? There were *two* posts to d-d-a about xlibs-dev, including a co-ordinated mass bug (and patch!) filing. I thought your complaint was both annoying and petty in the first place, but now you're provably wrong, to boot. Anyway, I'm going to continue to work hard on this. If you want to help dig us out of it, I'll welcome any patches you care to submit that are up to your standards of quality. I'm already fixing a huge load of RC bugs doing NMU to clean packages that are in a loosy shape since a lot of time, and that does not seem to have an active enough maintainer. I hope X.org does not qualify yet to those criteriums. Are you seriously suggesting that you would be a better X maintainer than David, assisted by his team? Are you suggesting that, under the circumstances, you could've done a better job with X11R7? Or (and I suspect this is more likely) are you just saying this because you like flaming people into the ground on mailing lists, for no apparent reason? If you want to do something productive[0], how about you go and fix some of these issues, instead of whining on debian-devel? In-Reply-To: [EMAIL PROTECTED] - /usr/X11R6/bin/X disapearing broke login managers (gdm, kdm) This is being rectified, as a perfunctory glance at -x will tell you. Are you serious ? Do you read debian-glibc@ each time you upload a package ? please, if something has te be known related to a migration, it has to come from the team that launched that migration. It's not to the others developpers to go read -x, it's up to you to inform them. It's not as much a migration issue as a bug. /usr/X11R6/bin should be a symlink to /usr/bin. Right now, in *some* cases, that doesn't happen. In most cases, it does. I don't expect to get personalised updates from seb128 every time Metacity introduces some bug which results in focus behaving very weirdly. I just expect that, in due course, the bug will get fixed and that the fix will work its way into unstable. If this is a little too much for you, may I suggest the testing branch? It's much less ... well ... unstable. So I really expect that in a really near future I'll hear from you (as a team member of the QT-KDE team that packages kdm), that gdm maintainer will hear from you as well, and that font packagers will see bugs go through the
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Josselin Mouette [EMAIL PROTECTED] writes: Le dimanche 16 avril 2006 à 19:24 +0200, Christian Marillat a écrit : You are wrong. I've orphaned all my GNOME packages with the right entry in the Debian changelog. read again. http://lists.debian.org/debian-devel-changes/2004/03/msg01789.html gnome-session (2.4.2-2) unstable; urgency=low * Orphaned package. -- Christian Marillat [EMAIL PROTECTED] Fri, 19 Mar 2004 15:50:59 +0100 Christian
Bug#362957: ITP: libcrypt-openssl-random-perl -- Perl module for RSA encoding and decoding, using the OpenSSL libraries.
Package: wnpp Severity: wishlist Owner: Luk Claes [EMAIL PROTECTED] * Package name: libcrypt-openssl-random-perl Version : 0.03 Upstream Author : Ian Roberts [EMAIL PROTECTED] * URL : http://cpan.org/ * License : like Perl Programming Lang: Perl Description : Perl module for accessing the OpenSSL pseudo-random number generator. Provides the ability to seed and query the OpenSSL library's pseudo-random number generator. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362958: RFA: texmacs -- WYSIWYG emacs-ish mathematical text editor
Package: wnpp Severity: normal Hi, I would like to give the texmacs package into caring hands. TeXmacs is a mathematical text editor, combining a wysiwyg interface with the typesetting quality of TeX. In fact, the program contains a complete re-implementation of Knuth's TeX typesetting algorithm, minus some of its limitations. The intended audience is mathematical writers, for this reason it has interfaces to many computer algebra systems. Some people abuse texmacs as a wysiwyg fromtend to write LaTeX (since it has an output converter to LaTeX), but in fact it is much more. I have been maintaining this packaeg for more than four years, in recent times with the help of Magnus Ekdahl. Unfortunately, I do not have the time to continue maintaining this package, and for the same reason Magnus cannot take over maintainership. In all the time the package has grown to my heart :-), and I would feel bad leaving the users of the package out in the cold. Hence I really would like this package to be taken over by some caring developper(s). Knowledge of C++ would be very helpful. There is an upstream bug tracer at savannah and a small upstream developer community. Coordination with upstream is easy. The main outstanding issues of the package are a better integration of fonts, and compilation with gcc-4.1. For the moment I can continue to do the maintenance, but if there is no taker in some weeks I will orphan the package. -Ralf. signature.asc Description: Digital signature
Re: Lintian package-has-a-duplicate-relation
Andreas Metzler [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
Why would you want to do that?
Usually because the binaries shipped with the package use internal,
undocumented interfaces that are not available to the rest of the world
and hence are not considered part of the SONAME (i.e., upstream doesn't
bump the SONAME when they change).
--
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: Lintian package-has-a-duplicate-relation
[EMAIL PROTECTED] writes:
Hi folks,
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
However,
Depends: ${shlibs:Depends}, libmypackage1 (= ${Source-Version})
Will make lintian scream.
I could abandon the use of ${shlibs:Depends}, and list each dependencies
manually, but this is a bit annoying.
Any clever suggestions ?
If linking against your libmypackage1 requires a certain version then
specify that relationship in your shlibs file. Then the shlibs:Depends
will be what you need and lintian won#t scream. problem solved.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 07:19:40PM +0200, Pierre HABOUZIT wrote: I'm complaining because *you* created the huge load of bugs you have to cope with, and a lot of other you don't warn other packagers about (what pissed me, and made me write my previous mail is yet-another-RC bug because of X we received on kdm recently...). And also in your answer to me, you ask to be sanctified because you are currently in a hurry to fix them ? In the interests of science, I dived into the debian-qt-kde archives[0]. I count: * 'Still happening?' pings from Adam Porter: 19. + Responses to same: 14. + Total: 33. * Testing migration mails: 9. * Spam: 7. * X-related bugs you were warned about via d-d-a: 2. * X-related bugs you weren't warned about via d-d-a: 2. * Other BTS: I stopped counting. I have better things to do. Again, if you're going to make outlandish claims in the name of chastising others, for god's sake, at least have the decency to be *right*. 'Oh my god, I'm drowning in bugs', indeed, Daniel [0]: http://lists.debian.org/debian-qt-kde/2006/04/threads.html signature.asc Description: Digital signature
Re: Bug#362878: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Le dimanche 16 avril 2006 à 19:48 +0200, Christian Marillat a écrit : http://lists.debian.org/debian-devel-changes/2004/03/msg01789.html gnome-session (2.4.2-2) unstable; urgency=low * Orphaned package. -- Christian Marillat [EMAIL PROTECTED] Fri, 19 Mar 2004 15:50:59 +0100 So, don't you think the second one (which is the one fixed later by the GNOME team) is better? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message numériquement signée
Re: Lintian package-has-a-duplicate-relation
Russ Allbery [EMAIL PROTECTED] writes:
Andreas Metzler [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
Why would you want to do that?
Usually because the binaries shipped with the package use internal,
undocumented interfaces that are not available to the rest of the world
and hence are not considered part of the SONAME (i.e., upstream doesn't
bump the SONAME when they change).
Sorry, that's not quite enough. shlibs of course handles changes less
than the SONAME. But I've run into this problem with krb5, which
historically adds a tight dependency between the binaries and the
libraries because the binaries sometimes use internal interfaces
(particularly in libkadm55), and the concept made some intuitive sense to
me. Maybe not, though... even changing internal interfaces used only by
binaries built out of the same package might be worth a bump in shlibs.
--
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: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
On Sun, Apr 16, 2006 at 12:22:14PM +0300, Daniel Stone [EMAIL PROTECTED] wrote: On Sun, Apr 16, 2006 at 12:02:42PM +0200, Christian Marillat wrote: Florian Weimer [EMAIL PROTECTED] writes: * Christian Marillat: Florian Weimer [EMAIL PROTECTED] writes: [...] Where are you reading that ? An upstream change is a change to the Debian package, too, and listing them is expressly allowed under the other changes option. I'm sorry but no. Read again. The Debian changelog is for Debian changes not upstream. For that we have a changelog file and a NEW file. Changes in the Debian version of the package should be briefly explained in the Debian changelog file `debian/changelog'.[1] This includes modifications made in the Debian package compared to the upstream one as well as other changes and updates to the package. Does it say that everything else is specifically excluded? Do you really have nothing better to do with your life than argue semantics about an ambiguous sentence[0]. Please get off this list and do something more productive with your time. ... like dealing with his own bugs in a proper way. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362793: ITP: sks -- Cryptographic tool based on ECC
On Sat, 15 Apr 2006, Nacho Barrientos Arias wrote: Package: wnpp Severity: wishlist Owner: Nacho Barrientos Arias [EMAIL PROTECTED] * Package name: sks Version : 0.92-1 Upstream Author : Nacho Barrientos Arias [EMAIL PROTECTED] * URL : http://pagina.de/sks * License : GPL Programming Lang: C Description : Cryptographic tool based on ECC SKS is a public-key, command-line application for encryption/authentication, based on Elliptic Curve Cryptography (ECC). . This package can work with a public key and symmetric cryto systems and generate signs. 'signatures' probably. . Homepage: http://pagina.de/sks This package name conflicts with the not yet uploaded SKS (Syncronising Key Server) software. Maybe you could pick something else? -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred.| : :' : The universal | `. `' Operating System http://www.palfrader.org/ | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Testing transitions before uploading to unstable
You're Devon Deppler, the maintainer for the Xyzzy set of packages, a total of a dozen packages. They're important and influential: about a quarter of the entire archive depends on the packages in one way or another. You have lots of users. Now upstream comes up with a new version, and changes some things in fairly fundamental ways. They're good changes, and they need to be made. The old way of things has been causing some problems already. The problem is, the changes aren't backwards compatible and they will break other packages. Some packages won't be building anymore, and others won't install or operate properly until they're updated. Your mission, should you accept it, is to make things happen so that when you upload the new packages, as little breaks for as short a time as possible. Should you, or any of your co-maintainers, fail to be perfect, the bug tracking system will be flooded with bugs and people will be calling you names. Sound familiar? Transitions are going to happen in Debian, but we don't seem to have good tools to deal with them. It strikes me that it would be cool to have something like this: * You upload your new packages to a staging system. * A fully automated tool upgrades an existing system (a chroot, a Xen instance, or whatever) to your new packages, and reports if all went OK. It also runs automated tests to see that everything works, before and after the upgrade. * If that worked, it re-builds your packages and everything that build-depends on your packages and reports results. * If there were any problems, you can fix packages and try again. As many times as you need to. You can also include fixed versions of other packages to test them, too. In my vision, this system would have enough computing power to be able to iterate even a large transition at least once per day, maybe more often. All the components for this already exist. We have autobuilders, we have upgrade testing, we have a tool for automated testing of package functionality. There is, in theory, nothing to stop anyone from doing this on their own system (and I assume some have done so), but it would be so much easier to not have to master every component tool yourself. Also, since this requires a lot of computing power to be efficient, it is not something people who work only on an old laptop can do very well. I think that if we created a centralized system for this (or possibly a distributed centralized system), it would be possible to make it fast enough to be quite usable. I think this would be possible to do. I don't have time for it myself, at least until Debconf, and I don't know some of the components (especially the buildds), but I suspect that for someone who does, this would be relatively straight-forward to assemble together. Anyone interested? -- Programming should be fun, otherwise you're doing something wrong. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362967: ITP: libapp-info-perl -- Provide metadata about software packages installed
Package: wnpp Severity: wishlist Owner: Nacho Barrientos Arias [EMAIL PROTECTED] * Package name: libapp-info-perl Version : 0.49-1 Upstream Author : David Wheeler [EMAIL PROTECTED] * URL : http://search.cpan.org/~dwheeler/App-Info-0.49/ * License : Perl Programming Lang: Perl Description : Provide metadata about software packages installed App::Info provides a generalized interface for providing metadata about software packages installed on a system. The idea is that App::Info subclasses can be used in Perl application installers in order to determine whether software dependencies have been fulfilled, and to get necessary metadata about those software packages. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-rc3 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: regarding gerris package
On Saturday 15 April 2006 12:56, Marcelo E. Magallon wrote: Hi Kamaraju, On Sat, Mar 04, 2006 at 01:33:09AM -0500, kamaraju kusumanchi wrote: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354032 asking for the latest version (0.8.0) of gerris which has been available since Oct 17, 2005. I have not received any reply to this bug report even after 10 days. I know that 10 days is not a very long period of time, but I just want to make sure that this package is not abandoned by you. Due to reasons that I prefer not to discuss on a public mailing list, I haven't worked on my packages for the last few months. I understand it completely. I appreciate the time and effort that goes into packaging. There are real life issues that are usually more important than volunteering work like Deian. The last time I was working on an updated gerris package I had several problems, mostly related to compiler changes in unstable. I just took a look at it, and it's still not compiling. I had no idea this was the case. I will try to compile gerris and see if I can have any success with it. Thanks for the response. If you have managed to compile a package for the newer versions, I will really appreciate a patch, if there's one. I have not tried it. I did not want to duplicate the same work. But I wil try it now and see if a patch can be submitted. If you want to abandon this package, please let us know by filing a bug against wnpp package saying that you are orphaning this package. This allows other interested persons (like me) to at least work on this package. If you are willing to take over the package I'll be happy with that. Please drop me a note off-list letting me know that. I just did not want gerris to be abandoned. I wanted to take over it only if you were MIA. Now that you are back into action, I do not want to take over. However, I would like to help in whatever way I can. We can definitely use your experience in packaging this software. thanks raju -- http://kamaraju.googlepages.com/cornell-bazaar http://groups.google.com/group/cornell-bazaar/about -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
On Sun, Apr 16, 2006 at 12:18:58PM +0200, [EMAIL PROTECTED] wrote:
Hi folks,
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
However,
Depends: ${shlibs:Depends}, libmypackage1 (= ${Source-Version})
Will make lintian scream.
I could abandon the use of ${shlibs:Depends}, and list each dependencies
manually, but this is a bit annoying.
Any clever suggestions ?
Well, I think people have adequately addressed the reasons why this is a bad
idea. :)
Now, the clean solution for those cases when there's a compelling reason to
implement this bad idea: see what dpkg-shlibdeps(1) has to say about
shlibs.local.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
Re: Lintian package-has-a-duplicate-relation
Steve Langasek [EMAIL PROTECTED] writes: Now, the clean solution for those cases when there's a compelling reason to implement this bad idea: see what dpkg-shlibdeps(1) has to say about shlibs.local. I've tried to do this before and encountered: See dpkg-shlibdeps(1) for details of the format of shared library dependency files. which of course is recursive and that man page contains no such details. I don't actually know what the format of that file is (although I expect I could make guesses at it from poking around, or get a much better idea by reading over the source code). But if there is a standard format that someone knows, it would be great to have that as a patch to Bug#316485. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 07:19:40PM +0200, Pierre HABOUZIT wrote: Give me a break. For one single package, it's already quite penible to use experimental (to avoid to pull every single experimental package, you have to edit your /etc/apt/preferences, and stuff like that), it's not imagineable that users will use experimental for that reason, Yes, they do. It might be too complicated for you, oh Mighty Debian Developer, but us mere mortals just follow the examples in apt_preferences(5) and that works for us. I installed X.org 7.0 from experimental on i386 about a week or two before it was uploaded to unstable, and expect some minor adjustment it worked just fine. I installed it on AMD64 after it was uploaded to unstable, and apart from a missing package it worked just fine. In fact, considering the dozens of packages affected, I expected _MUCH_ more breakage than I actually encountered. because with the myriad of libraries that X comes with, either you pull all experimental (who is insane enough to only think of doing that ?) Oh, so the Mighty Debian Developers consider Debian users who are willing to test such big changes as the X transition insane? This is just the attitude users LOVE about Debian Developers... or edit a 645-line long /etc/apt/preferences, which nobody will want to do either. This was the line when I tought I can not resist replying to your mail. If you show so much incompetence about the product you are supposed to be developing in such a short sentence, then I'd seriously consider giving up being a DD if I were you. I honnestly think things have been rushed[3] too much, as many of the problems that have been raised, could have been found, warned, or worked around in early packaging stages (meaning before an upload). So, apart from the incompetence you showed, what are _YOUR_ excuses for not testing the transition when it was still in experimental? And if you did not do that, what are you complaining about? Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - signature.asc Description: Digital signature
Re: Lintian package-has-a-duplicate-relation
On Sun, Apr 16, 2006 at 01:19:36PM -0700, Russ Allbery wrote: Steve Langasek [EMAIL PROTECTED] writes: Now, the clean solution for those cases when there's a compelling reason to implement this bad idea: see what dpkg-shlibdeps(1) has to say about shlibs.local. I've tried to do this before and encountered: See dpkg-shlibdeps(1) for details of the format of shared library dependency files. which of course is recursive and that man page contains no such details. I don't actually know what the format of that file is (although I expect I could make guesses at it from poking around, or get a much better idea by reading over the source code). But if there is a standard format that someone knows, it would be great to have that as a patch to Bug#316485. See policy section 8.6. It's the same as normal shlibs files. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
Kurt Roeckx [EMAIL PROTECTED] writes: On Sun, Apr 16, 2006 at 01:19:36PM -0700, Russ Allbery wrote: I've tried to do this before and encountered: See dpkg-shlibdeps(1) for details of the format of shared library dependency files. which of course is recursive and that man page contains no such details. I don't actually know what the format of that file is (although I expect I could make guesses at it from poking around, or get a much better idea by reading over the source code). But if there is a standard format that someone knows, it would be great to have that as a patch to Bug#316485. See policy section 8.6. It's the same as normal shlibs files. Wow, I somehow managed to completely miss that this was in Policy, despite having read Policy all the way through a couple of times. In penance, *I'll* go submit a patch to Bug#316485. Thank you! -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
On Sunday 16 April 2006 22:13, Steve Langasek wrote: Now, the clean solution for those cases when there's a compelling reason to implement this bad idea: see what dpkg-shlibdeps(1) has to say about shlibs.local. One minor gripe about dpkg-shlibdeps(1)... If I look at that page, I get redirected to dpkg-source(1). This is fine, but the page also contains: See dpkg-shlibdeps(1) for details of the format of shared library dependency files. AFAICT there's no separate manpage for dpkg-shlibdeps(1) and I cannot find details if the format of shlibs files in dpkg-shlibdeps(1). Is this a bug that should be reported or am I missing something? pgpfAvc682oqn.pgp Description: PGP signature
Re: Bug#354674: What on earth?
su, 2006-04-16 kello 22:25 +0200, Gabor Gombas kirjoitti: So, [- - -] what are _YOUR_ excuses for not testing the transition when it was still in experimental? And if you did not do that, what are you complaining about? I like this attitude: you either help, or you shut up. Attacking people because they made a mistake and are busy fixing it is not productive. We're together in this chaotic beauty called the Debian Project, and when there is a problem, it's *our* problem. Not the X maintainers' problem, not the release managers' problem, but all our problem. We all either work to help fix it, or at least we stand silently aside so as not to make things worse. Talk is cheap. Whines are practically free. -- One does not see anything until one sees its beauty. -- O.W. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
Russ Allbery [EMAIL PROTECTED] writes:
Andreas Metzler [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
Is there a way to force a specific library version known in
${shlibs:Depends} ?
Using Depends: ${shlibs:Depends} is not really fine, if I want to
force the library to be upgraded when the primary binary package is
updated.
Why would you want to do that?
Usually because the binaries shipped with the package use internal,
undocumented interfaces that are not available to the rest of the world
and hence are not considered part of the SONAME (i.e., upstream doesn't
bump the SONAME when they change).
And you can't use a shlibs.local file to override the lesser
restrictions when building?
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Testing transitions before uploading to unstable
Lars Wirzenius [EMAIL PROTECTED] writes: You're Devon Deppler, the maintainer for the Xyzzy set of packages, a total of a dozen packages. They're important and influential: about a quarter of the entire archive depends on the packages in one way or another. You have lots of users. Now upstream comes up with a new version, and changes some things in fairly fundamental ways. They're good changes, and they need to be made. The old way of things has been causing some problems already. The problem is, the changes aren't backwards compatible and they will break other packages. Some packages won't be building anymore, and others won't install or operate properly until they're updated. Your mission, should you accept it, is to make things happen so that when you upload the new packages, as little breaks for as short a time as possible. Should you, or any of your co-maintainers, fail to be perfect, the bug tracking system will be flooded with bugs and people will be calling you names. Sound familiar? Transitions are going to happen in Debian, but we don't seem to have good tools to deal with them. It strikes me that it would be cool to have something like this: * You upload your new packages to a staging system. That is called experimental or unstable. * A fully automated tool upgrades an existing system (a chroot, a Xen instance, or whatever) to your new packages, and reports if all went OK. It also runs automated tests to see that everything works, before and after the upgrade. puiparts * If that worked, it re-builds your packages and everything that build-depends on your packages and reports results. I have that planed for when I have some spare time. I actualy want to do a few such test: - build all reverse Build-Depends of a package - build the package against the lowest possible versions (minimum stable) as specified by Build-Depends. - same but with a minimum of testing * If there were any problems, you can fix packages and try again. As many times as you need to. You can also include fixed versions of other packages to test them, too. I think this is best left to unstable/experimental. Adding yet another layer of distributions would just increase the workload managing them. In my vision, this system would have enough computing power to be able to iterate even a large transition at least once per day, maybe more often. Only for the main archs but that is better than none. All the components for this already exist. We have autobuilders, we have upgrade testing, we have a tool for automated testing of package functionality. There is, in theory, nothing to stop anyone from doing this on their own system (and I assume some have done so), but it would be so much easier to not have to master every component tool yourself. Also, since this requires a lot of computing power to be efficient, it is not something people who work only on an old laptop can do very well. I think that if we created a centralized system for this (or possibly a distributed centralized system), it would be possible to make it fast enough to be quite usable. I think this would be possible to do. I don't have time for it myself, at least until Debconf, and I don't know some of the components (especially the buildds), but I suspect that for someone who does, this would be relatively straight-forward to assemble together. Anyone interested? All you need is to setup a central wanna-build and some script to reschedule reverse Build-Depends and get people to setup buildds. If you know what you are doing this is a matter of hours. More if you try it the first time. Nobody is stopping you. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Lintian package-has-a-duplicate-relation
Goswin von Brederlow [EMAIL PROTECTED] writes: Russ Allbery [EMAIL PROTECTED] writes: Usually because the binaries shipped with the package use internal, undocumented interfaces that are not available to the rest of the world and hence are not considered part of the SONAME (i.e., upstream doesn't bump the SONAME when they change). And you can't use a shlibs.local file to override the lesser restrictions when building? That's what I've been meaning to try. The only thing that I've been a bit worried about is that the package also builds multiple library packages, and they shouldn't have the same tight dependency on each other, plus I've heard (but not verified) that shlibs.local can lead to a library package depending on itself if there are multiple shared libraries in it with internal dependencies. The best solution would really be to decide to bump the shlibs file each time anything changes that may affect even the internal programs in the package. I need to talk to upstream about that. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362793: ITP: sks -- Cryptographic tool based on ECC
On Sun, 16 Apr 2006, Nacho Barrientos Arias wrote: Date: Sun, 16 Apr 2006 21:03:43 +0200 Peter Palfrader [EMAIL PROTECTED] wrote: This package name conflicts with the not yet uploaded SKS (Syncronising Key Server) software. Maybe you could pick something else? sks-crypto? Maybe that's better, yes. (Tho still not perfect. A PGP Keyserver is about crypto too.) What does this sks stand for anyway? Peter -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred.| : :' : The universal | `. `' Operating System http://www.palfrader.org/ | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Testing transitions before uploading to unstable
su, 2006-04-16 kello 23:49 +0200, Goswin von Brederlow kirjoitti: That is called experimental or unstable. Er, no. The point is to get things tested and hopefully fixed before uploading to unstable. Experimental might work, but then packages there need to be tested with the existing unstable in ways they are not, as far as I know, currently being tested. * A fully automated tool upgrades an existing system (a chroot, a Xen instance, or whatever) to your new packages, and reports if all went OK. It also runs automated tests to see that everything works, before and after the upgrade. puiparts Piuparts tests individual packages and packages that they depend on. It does not test that, for example, reverse dependencies continue to work. * If there were any problems, you can fix packages and try again. As many times as you need to. You can also include fixed versions of other packages to test them, too. I think this is best left to unstable/experimental. Adding yet another layer of distributions would just increase the workload managing them. I didn't suggest it as a layer in the stable/testing/unstable/experimental spectrum. Rather, it is meant to be orthogonal to them, a completely new system. For example, there's no need to restrict uploads to DDs. All you need is to setup a central wanna-build and some script to reschedule reverse Build-Depends and get people to setup buildds. If you know what you are doing this is a matter of hours. More if you try it the first time. Nobody is stopping you. Why do you think anybody would be stopping me? The reason I am not going to be working on this myself is because my available time is allocated elsewhere already. -- The road is wide and the sky is tall, before I die I will see it all.--H.A. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Work-needing packages report for Apr 14, 2006
Christoph Berg wrote: Yes, definitely. If you are aware of any solved RFH bugs, could you ping the maintainers? Done. Pinged: aboot, athcool, cvs, dpkg, grub, gtkpod, openssl, parted, pbbuttonsd, phpgroupware, sourcenav, stlport4.6, thinkpad, tpctl I didn't ping the others because either there were no help responses or the responses were somewhat new. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
On 16 Apr 2006, Christian Marillat uttered the following: Here is the relevant policy : , | Changes in the Debian version of the package should be briefly explained in the Debian changelog file `debian/changelog'.[1] This includes modifications made in the Debian package compared to the upstream one as well as other changes and updates to the package. [2] So changes made in packaging are relevant, as well as other changes -- which caninclude significant changes upstream. The bottom line is not one of NIH -- the changelog should contain enough information for the target audience to decide whether or not to install the upgrade. Changes made in new versions certainly affect my decisions on whether or not I wan the new packages, based on materiel provided by apt-listchanges. manoj -- If we don't survive, we don't do anything else. John Sinclair Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possible conflict with XFree 4.5
Daniel Stone wrote: On Sat, Apr 15, 2006 at 04:17:28PM +0300, gustavo halperin wrote: I think that we have a problem when the common library between XFree and /usr/lib are update in /usr/lib. I currently have XFree 4.5, when the library libfontconfig1 was update to version 2.3.2-1 was also updated the file libfontconfig.so to the version 1.0.4 but in the XFree (/usr/X11R6/lib/) this library still be the version 1. The problem came we we use programs like Gimp that must at least version 1.0.2 of this library. I solve this problem by link the libfontconfig in /usr/X11R6/lib to the newest library in /usr/lib. That is the solution or that is a Bug in Debian System ?? I assume that you're installing XFree86 4.5 by yourself, since it wasn't packaged for Debian. In that case, local installation conflicts are your problem to sort out. I see, you are absolutely right. Thank you for you explanation. Gustavo Halperin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#354674: What on earth?
On Sun, Apr 16, 2006 at 10:52:21AM -0400, David Nusinow wrote: I have yet to file bugs against other packages that I've affected because I haven't had time. This is a serious problem, but I have hundreds of packages to actively look after during this transition and I'd appreciate any sort of help that can be offered. Anyway, I'm going to continue to work hard on this. If you want to help dig us out of it, I'll welcome any patches you care to submit that are up to your standards of quality. Until then though, feel free to kiss my ass. Let's make this a little more concrete: http://ftp-master.debian.org/~vorlon/x11-common-conflicts-unstable.txt That page is the list of all the packages in unstable that x11-common had to add conflicts for as a result of the /usr/X11R6/bin transition. Most of these packages will need patches created, and bugs filed, for being fixed to use /usr/bin and other corresponding directories outside of /usr/X11R6. If people want to chip in and help with this, that would be keen. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
sources.list
Dear all, When i wanna a local directory from my HDD, parallel of it,I use apt-get from that directory,How i dpo it? Yours,Mohsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#361418: [Proposal] new Debian menu structure
Manoj Srivastava wrote: snip To the practitioners, it is HAM radio. Not Amatuer radio -- and the only reason we are considering not calling it ham since ignorant users should not be confused. Sounds like dumbing down to me. manoj Eh? I use amateur radio all the time, any time I speak of it formally, in essays, etc. My license also says AMATEUR RADIO LICENSE on it, not ham. I use amateur for formal situations or people who aren't aware of the hobby, ham for informal use. Just my $0.02 Benjamin, KI4CXN signature.asc Description: OpenPGP digital signature
Re: libgtk2.0-0: changelog.Debian.gz is not an upstream changelog
Manoj Srivastava [EMAIL PROTECTED] writes: On 16 Apr 2006, Christian Marillat uttered the following: Here is the relevant policy : , | Changes in the Debian version of the package should be briefly explained in the Debian changelog file `debian/changelog'.[1] This includes modifications made in the Debian package compared to the upstream one as well as other changes and updates to the package. [2] So changes made in packaging are relevant, as well as other changes -- which caninclude significant changes upstream. The bottom line is not one of NIH -- the changelog should contain enough information for the target audience to decide whether or not to install the upgrade. A copy and paste from the NEW file is certainly useless. The Debian changelog : , | * New upstream version: | Bugs fixed: | - Expander disclosure button is too small | - gtk_image_clear doesn't cause redraw | - typo in configure.in yields suspicious warning | - gtk_icon_view_set_cursor causes Segmentation fault | - garbage output of --help in non UTF-8 locale | - GtkNotebook does not destroy its children on destroy() | - TreeView DnD between-row highlight colo | - Gtk-Criticals occur when scrolling a text_view that is not realized | - Hidden menubar still activates submenus with kbd | - GtkTreeItem broken | - Clean up button press handling (use one-grab-op-at-a-time pattern) | - broken scrolling when selecting | - GTK+ File-chooser dialog crashes | - Nautilus crashes when dragging icons to another screen | - mixed line separators confuse gtk_text_iter_ends_line | - Textview child is covered by window border | - gdk_pixbuf_loader_new_with_type(): What image types are allowed? | - Missing progress bar label | - Fix a problem which caused grab-notify signal to be missed in some cases ` And here the NEW entries for this release : , | 325699 Expander disclosure button is too small [Brad Taylor] | 334657 gtk_image_clear doesn't cause redraw | 334774 typo in configure.in yields suspicious | warning [Peter Breitenlohner] | 335001 gtk_icon_view_set_cursor causes | Segmentation fault [Emmanuel Rodriguez] | 335129 garbage output of --help in non UTF-8 locale [Christian Persch] | 319032 GtkNotebook does not destroy its children | on destroy() [Yevgen Muntyan] | 334906 TreeView DnD between-row highlight color [Ian McDonald] | 335717 Gtk-Criticals occur when scrolling a text_view | that is not realized [Nicolas Setton] | 336200 Hidden menubar still activates submenus with kbd |[Bastian Nocera] | 336254 GtkTreeItem broken [Sven Herzberg] | 74620 Clean up button press handling (use | one-grab-op-at-a-time pattern)[Li Yuan] | 323862 broken scrolling when selecting [Benjamin Berg] | 330617 GTK+ File-chooser dialog crashes | 325751 Nautilus crashes when dragging icons to | another screen [Hylke van der Schaaf] | 337022 mixed line separators confuse | gtk_text_iter_ends_line [Paolo Borelli] | 336796 Textview child is covered by window border [Yevgen Muntyan] | 335536 gdk_pixbuf_loader_new_with_type(): | What image types are allowed? [Murray Cumming] | 336645 Missing progress bar label [Stanislav Brabec] | Fix a problem which caused grab-notify | signal to be missed in some cases [Matthias Clasen] ` Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcgi-ajax-perl 0.694-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 14 Apr 2006 15:12:06 -0400 Source: libcgi-ajax-perl Binary: libcgi-ajax-perl Architecture: source all Version: 0.694-1 Distribution: unstable Urgency: low Maintainer: Ernesto Hernández-Novich [EMAIL PROTECTED] Changed-By: Ernesto Hernández-Novich [EMAIL PROTECTED] Description: libcgi-ajax-perl - A Perl-specific system for writing Asynchronous web applications Changes: libcgi-ajax-perl (0.694-1) unstable; urgency=low . * New upstream version. Files: e720c835122532c04fd4d0f4bbc74f82 675 perl optional libcgi-ajax-perl_0.694-1.dsc 122cd4f528a6061d87107978a991e048 33497 perl optional libcgi-ajax-perl_0.694.orig.tar.gz 88836d28d10ee001fd514011f32a96ae 2678 perl optional libcgi-ajax-perl_0.694-1.diff.gz 968673ae8f1f4600e05f8504a335b3fa 40892 perl optional libcgi-ajax-perl_0.694-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQan+mBxf18ZxJX0RArXiAJ90kJVCf3j55hFlt+URhvgTjOIPrgCfYIMC N/4BGp7hQHlfNxpTZx065Wo= =lHWN -END PGP SIGNATURE- Accepted: libcgi-ajax-perl_0.694-1.diff.gz to pool/main/libc/libcgi-ajax-perl/libcgi-ajax-perl_0.694-1.diff.gz libcgi-ajax-perl_0.694-1.dsc to pool/main/libc/libcgi-ajax-perl/libcgi-ajax-perl_0.694-1.dsc libcgi-ajax-perl_0.694-1_all.deb to pool/main/libc/libcgi-ajax-perl/libcgi-ajax-perl_0.694-1_all.deb libcgi-ajax-perl_0.694.orig.tar.gz to pool/main/libc/libcgi-ajax-perl/libcgi-ajax-perl_0.694.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gimp 2.2.11-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.7 Date: Thu, 13 Apr 2006 17:27:44 -0400 Source: gimp Binary: gimp-python libgimp2.0-doc gimp-data gimp gimp-helpbrowser libgimp2.0 gimp-svg libgimp2.0-dev gimp-dbg Architecture: source i386 all Version: 2.2.11-1 Distribution: unstable Urgency: low Maintainer: Ari Pollak [EMAIL PROTECTED] Changed-By: Ari Pollak [EMAIL PROTECTED] Description: gimp - The GNU Image Manipulation Program gimp-data - Data files for The GIMP gimp-dbg - Debugging symbols for The GIMP gimp-helpbrowser - Built-in Help Browser plugin for The GIMP gimp-python - Python support and plugins for The GIMP gimp-svg - SVG (Scalable Vector Graphics) plugin for The GIMP libgimp2.0 - Libraries necessary to Run the GIMP libgimp2.0-dev - Headers and other files for compiling plugins for The GIMP libgimp2.0-doc - Developers' Documentation for the GIMP library Closes: 361459 Changes: gimp (2.2.11-1) unstable; urgency=low . * New upstream release * Stop building with gcc-3.4 on arm * Fix build-depends to exclude kfreebsd-amd64 from using libasound2-dev (Closes: #361459) Files: 439cd5f24053e978bd809ba9a6f50197 1251 graphics optional gimp_2.2.11-1.dsc c4312189e3a7f869a26874854dc6a1d7 18549092 graphics optional gimp_2.2.11.orig.tar.gz 3d9432d0ae3446a4e2097f318e4f64e4 28949 graphics optional gimp_2.2.11-1.diff.gz 8e2b40fe57468af5699bdbec8d225f88 6688676 graphics optional gimp-data_2.2.11-1_all.deb f8323e68ee70f9d32f9f2c5e2664dd02 527174 doc optional libgimp2.0-doc_2.2.11-1_all.deb a5da4550ae3e83b46076411a256d6bd3 534208 libs optional libgimp2.0_2.2.11-1_i386.deb 3b0251124156b1ba5a1d828ab8b18fea 52054 graphics optional gimp-helpbrowser_2.2.11-1_i386.deb 7b5c0435c3c0fde17d51fb3447365c22 126798 graphics optional gimp-python_2.2.11-1_i386.deb ef2afd0f44e1587f057cd1cc5e224aa7 52720 graphics optional gimp-svg_2.2.11-1_i386.deb 916d4e083c5e39cd55c3102b3501f096 3003670 graphics optional gimp_2.2.11-1_i386.deb 5254541013348065b64d87a42035b251 108398 libdevel optional libgimp2.0-dev_2.2.11-1_i386.deb ce45fa5308b7218d93889f4fa9e84a1f 7367860 graphics extra gimp-dbg_2.2.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQbCkwO+u47cOQDsRA7/dAJ9t9SdpNhaOPMyIEFQxf7U+TlNjGACfc2QD Z7w1dqG+IJj0NRz9DE3buao= =RgpF -END PGP SIGNATURE- Accepted: gimp-data_2.2.11-1_all.deb to pool/main/g/gimp/gimp-data_2.2.11-1_all.deb gimp-dbg_2.2.11-1_i386.deb to pool/main/g/gimp/gimp-dbg_2.2.11-1_i386.deb gimp-helpbrowser_2.2.11-1_i386.deb to pool/main/g/gimp/gimp-helpbrowser_2.2.11-1_i386.deb gimp-python_2.2.11-1_i386.deb to pool/main/g/gimp/gimp-python_2.2.11-1_i386.deb gimp-svg_2.2.11-1_i386.deb to pool/main/g/gimp/gimp-svg_2.2.11-1_i386.deb gimp_2.2.11-1.diff.gz to pool/main/g/gimp/gimp_2.2.11-1.diff.gz gimp_2.2.11-1.dsc to pool/main/g/gimp/gimp_2.2.11-1.dsc gimp_2.2.11-1_i386.deb to pool/main/g/gimp/gimp_2.2.11-1_i386.deb gimp_2.2.11.orig.tar.gz to pool/main/g/gimp/gimp_2.2.11.orig.tar.gz libgimp2.0-dev_2.2.11-1_i386.deb to pool/main/g/gimp/libgimp2.0-dev_2.2.11-1_i386.deb libgimp2.0-doc_2.2.11-1_all.deb to pool/main/g/gimp/libgimp2.0-doc_2.2.11-1_all.deb libgimp2.0_2.2.11-1_i386.deb to pool/main/g/gimp/libgimp2.0_2.2.11-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted util-vserver 0.30.210-7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 7 Apr 2006 16:57:06 -0400 Source: util-vserver Binary: util-vserver Architecture: source i386 Version: 0.30.210-7 Distribution: unstable Urgency: low Maintainer: Ola Lundqvist [EMAIL PROTECTED] Changed-By: Micah Anderson [EMAIL PROTECTED] Description: util-vserver - tools for Virtual private servers and context switching Closes: 361374 Changes: util-vserver (0.30.210-7) unstable; urgency=low . * Fixed extra file installed in /etc/default (Closes: #361374) * Updated vcontext --uid patch fixing segfaults when called with incorrect usernames, and missing hunks for chkconfig in scripts/vserver * Updated chroot barrier setting in initscript * Added build-time tests to debian/rules * Added apis patch to fix a typo and allowing for specifying oldproc and olduts in --enable-apis in configure * Added condrestart patch to fix conditional restarts in 'vserver' * Added cpuset support patch * Added patch to fix nice function * Added prefix configure patch fix * Added patch to warn that gentoo initstyle is not an option * Added patch to fix start-vservers --all -stop not actually stopping all vservers, just marked ones * Added patch to fix vserver usage message to be more clear * Added a patch that lets you install Fedora Core 5 guests * Thanks go to Daniel Hokka Zakrisson! Files: ed2c9c5ee4f43fe3d4bce685054ba0ed 839 net optional util-vserver_0.30.210-7.dsc c083b310af15a89cc59f7c148e0728a8 46234 net optional util-vserver_0.30.210-7.diff.gz 4cdc8cbb8731399b65464998464097fe 393762 net optional util-vserver_0.30.210-7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQcn49n4qXRzy1ioRAqm0AJ9GSI72rGWJ3ixxVw8JJ+/JUpDGAgCfZVYU BMckca7psVxG79lXfZ/Lgck= =K7g0 -END PGP SIGNATURE- Accepted: util-vserver_0.30.210-7.diff.gz to pool/main/u/util-vserver/util-vserver_0.30.210-7.diff.gz util-vserver_0.30.210-7.dsc to pool/main/u/util-vserver/util-vserver_0.30.210-7.dsc util-vserver_0.30.210-7_i386.deb to pool/main/u/util-vserver/util-vserver_0.30.210-7_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted preload 0.2-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 14 Apr 2006 15:04:21 +0300 Source: preload Binary: preload Architecture: source i386 Version: 0.2-5 Distribution: unstable Urgency: low Maintainer: Kari Pahula [EMAIL PROTECTED] Changed-By: Kari Pahula [EMAIL PROTECTED] Description: preload- an adaptive readahead daemon Closes: 345776 362582 Changes: preload (0.2-5) unstable; urgency=low . * Quote $2 in postinst (Closes: #345776) * Add more information to debian/copyright file (Closes: #362582) * rm depends: sysv-rc | file-rc (silly me). * Upload sponsored by Petter Reinholdtsen. Files: 801a0f671c85948caa153d2667e0c547 565 misc optional preload_0.2-5.dsc 5f0ee68219b6b8cc9c8b04390f1a68cc 4664 misc optional preload_0.2-5.diff.gz d253dab4d7773a8e6cf842881657eb94 33120 misc optional preload_0.2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQgKJ20zMSyow1ykRAkJ8AKDZb4soIXHcuP3vw1oSvZZGb7M6ngCfRneT kWD0wwrtPjO0MyjjpiQH3Y8= =THhJ -END PGP SIGNATURE- Accepted: preload_0.2-5.diff.gz to pool/main/p/preload/preload_0.2-5.diff.gz preload_0.2-5.dsc to pool/main/p/preload/preload_0.2-5.dsc preload_0.2-5_i386.deb to pool/main/p/preload/preload_0.2-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mplayerplug-in 3.25-4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.7 Date: Sun, 16 Apr 2006 00:57:46 -0400 Source: mplayerplug-in Binary: mozilla-mplayer Architecture: source i386 Version: 3.25-4 Distribution: unstable Urgency: low Maintainer: Ari Pollak [EMAIL PROTECTED] Changed-By: Ari Pollak [EMAIL PROTECTED] Description: mozilla-mplayer - MPlayer-Plugin for Mozilla Closes: 362520 Changes: mplayerplug-in (3.25-4) unstable; urgency=low . * Add /usr/lib/firefox to the rpath as well (Closes: #362520) Files: d0bd349c0981ccadb13e60698e854df2 679 contrib/misc optional mplayerplug-in_3.25-4.dsc 82e5973d89bb543145ab3d127514ca02 4384 contrib/misc optional mplayerplug-in_3.25-4.diff.gz 27c7e86956e5df1c2e31cb26debf96a8 467088 contrib/misc optional mozilla-mplayer_3.25-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQc9WwO+u47cOQDsRA/ElAKCMeB/WHhtygpVDuChk2dGj8jc/IACcC36H TtEYzQXevP02cEi/4W/JX+k= =jrI7 -END PGP SIGNATURE- Accepted: mozilla-mplayer_3.25-4_i386.deb to pool/contrib/m/mplayerplug-in/mozilla-mplayer_3.25-4_i386.deb mplayerplug-in_3.25-4.diff.gz to pool/contrib/m/mplayerplug-in/mplayerplug-in_3.25-4.diff.gz mplayerplug-in_3.25-4.dsc to pool/contrib/m/mplayerplug-in/mplayerplug-in_3.25-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cgoban 1.9.14-10 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 07:31:25 +0200 Source: cgoban Binary: cgoban Architecture: source i386 Version: 1.9.14-10 Distribution: unstable Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: cgoban - complete Go board Changes: cgoban (1.9.14-10) unstable; urgency=low . * Added debug switch to make in order to investigate timestamp problem when auto-building on ia64 and sparc, which is not reproducible with a manual build. Files: e436aac20ed6bcbadcf6b3f4639c5c5d 581 games optional cgoban_1.9.14-10.dsc 69d8b2b97d8b847b7e72dd761b32bbd0 59569 games optional cgoban_1.9.14-10.diff.gz 963ecc3f4b20047b570786b50276962b 238320 games optional cgoban_1.9.14-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQdlUhOZKoAn8AVwRAuz0AKCpjD9RPpozdGcY04vC/DDvzKFwhQCfSdC3 nxWGx8cjIJrULBEz66YF5dE= =lw4+ -END PGP SIGNATURE- Accepted: cgoban_1.9.14-10.diff.gz to pool/main/c/cgoban/cgoban_1.9.14-10.diff.gz cgoban_1.9.14-10.dsc to pool/main/c/cgoban/cgoban_1.9.14-10.dsc cgoban_1.9.14-10_i386.deb to pool/main/c/cgoban/cgoban_1.9.14-10_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted noffle 1.1.5-9 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 08:20:40 +0200 Source: noffle Binary: noffle Architecture: source i386 Version: 1.1.5-9 Distribution: unstable Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: noffle - offline news server Closes: 343740 Changes: noffle (1.1.5-9) unstable; urgency=low . * Added Swedish debconf translation, closes: #343740. Thanks to Daniel Nylander. * Updated copyright file. Files: a9651e658db43098d9dbca746031963b 589 news optional noffle_1.1.5-9.dsc ab5792faff8644b10d9eced469f6ffda 24832 news optional noffle_1.1.5-9.diff.gz f09d8fc55caf2f6e255fca364126c684 122094 news optional noffle_1.1.5-9_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQeLbhOZKoAn8AVwRAi62AJ9q/Vrf6zvMOehKINYpPYgwNIA4FACgjt2u TzbTXNu10nwgIqggUaa6c+s= =NJyF -END PGP SIGNATURE- Accepted: noffle_1.1.5-9.diff.gz to pool/main/n/noffle/noffle_1.1.5-9.diff.gz noffle_1.1.5-9.dsc to pool/main/n/noffle/noffle_1.1.5-9.dsc noffle_1.1.5-9_i386.deb to pool/main/n/noffle/noffle_1.1.5-9_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sl-modem 2.9.9d+e-pre2-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 08:23:47 +0200 Source: sl-modem Binary: sl-modem-daemon sl-modem-source Architecture: source i386 Version: 2.9.9d+e-pre2-5 Distribution: unstable Urgency: low Maintainer: Eduard Bloch [EMAIL PROTECTED] Changed-By: Eduard Bloch [EMAIL PROTECTED] Description: sl-modem-daemon - SmartLink software modem daemon sl-modem-source - SmartLink software modem driver - module building source Closes: 358267 Changes: sl-modem (2.9.9d+e-pre2-5) unstable; urgency=low . * Fix for module compilation with 2.6.16, condition around line drivers/st7554.c:1160 (closes: #358267) Files: b2a474ff35fd4e77213e87091a055dbd 644 non-free/misc optional sl-modem_2.9.9d+e-pre2-5.dsc 352f87fe3c8ee7863ec57701a5e6211f 22790 non-free/misc optional sl-modem_2.9.9d+e-pre2-5.diff.gz fe91f59a8778467f6887bad389bfcb73 217430 non-free/misc optional sl-modem-source_2.9.9d+e-pre2-5_i386.deb 4f857d56eb949df94b1b693ba48ce0b9 508584 non-free/misc optional sl-modem-daemon_2.9.9d+e-pre2-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQeYw4QZIHu3wCMURAqPkAJ9iXxOY8oBxVSASk8NE5atctu30+ACcDTyX lVf3y5n6LHLmkjBwaNLBBPY= =lrVj -END PGP SIGNATURE- Accepted: sl-modem-daemon_2.9.9d+e-pre2-5_i386.deb to pool/non-free/s/sl-modem/sl-modem-daemon_2.9.9d+e-pre2-5_i386.deb sl-modem-source_2.9.9d+e-pre2-5_i386.deb to pool/non-free/s/sl-modem/sl-modem-source_2.9.9d+e-pre2-5_i386.deb sl-modem_2.9.9d+e-pre2-5.diff.gz to pool/non-free/s/sl-modem/sl-modem_2.9.9d+e-pre2-5.diff.gz sl-modem_2.9.9d+e-pre2-5.dsc to pool/non-free/s/sl-modem/sl-modem_2.9.9d+e-pre2-5.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sane-backends 1.0.17-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 13 Apr 2006 21:40:58 +0200 Source: sane-backends Binary: libsane-dev sane-utils libsane Architecture: source i386 Version: 1.0.17-2 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: libsane- API library for scanners libsane-dev - API development library for scanners [development files] sane-utils - API library for scanners -- utilities Closes: 344541 350436 357568 359797 359800 Changes: sane-backends (1.0.17-2) unstable; urgency=low . [ Aurélien JARNO ] * debian/control: + Build-depends: libcam-dev on kfreebsd-i386 and kfreebsd-amd64. + Build-depends: !libieee1284-dev on kfreebsd-amd64. + libsane-dev depends: libcam-dev on GNU/kFreeBSD. * debian/patches/25_glibc_sys_io_h.dpatch: + New; check for GNU libc instead of Linux kernel. . [ Julien BLACHE ] * debian/patches/02_udev_rules.dpatch: + Removed; coldplugging now works OK, the hotplug script aren't needed anymore (closes: #359800). * debian/patches/03_usb_perms_664.dpatch: + Updated. * debian/patches/04_udev_rules_fix.dpatch: + Added; fix udev rules file so that the rules only run for ACTION=add on the usb subsystem (closes: #359797). * debian/patches/01_usbids.dpatch: + Added; add Epson Stylus CX7800 USB IDs (closes: #350436). * debian/patches/26_manpages_spelling_fixes.dpatch: + Added; various spelling fixes to the manpages (closes: #357568). * debian/control: + Removed Conflicts: on very old SANE versions. + Recommends: module-init-tools (= 3.2.2-1) (closes: #344541). + Recommends: udev (= 0.88-1) for a version of udev with working coldplugging support. Let me know if the version can be lowered, thanks. * debian/rules: + Add variable substitution for module-init-tools on Linux. + Add version to the udev variable substitution. Files: bc9db395a529d9a6e77257c7487f05a4 898 graphics optional sane-backends_1.0.17-2.dsc e58b4a7f48195ea65a7d1fd1062b14dd 44121 graphics optional sane-backends_1.0.17-2.diff.gz ca3b7f0cba0836cede1573adedc7dfee 119690 graphics optional sane-utils_1.0.17-2_i386.deb 91b6d358a7d83be7d9548942b9aa2e06 2875934 libs optional libsane_1.0.17-2_i386.deb 3cea99ec875bb640d4e5d1fc4d00c751 2383206 libdevel optional libsane-dev_1.0.17-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQhL4zWFP1/XWUWkRAophAKC1skJwKOA/K8cXcMIJxsc4+9k5/ACg4xVq omGFl7VEv4UXIjwjksA5m0A= =/VAh -END PGP SIGNATURE- Accepted: libsane-dev_1.0.17-2_i386.deb to pool/main/s/sane-backends/libsane-dev_1.0.17-2_i386.deb libsane_1.0.17-2_i386.deb to pool/main/s/sane-backends/libsane_1.0.17-2_i386.deb sane-backends_1.0.17-2.diff.gz to pool/main/s/sane-backends/sane-backends_1.0.17-2.diff.gz sane-backends_1.0.17-2.dsc to pool/main/s/sane-backends/sane-backends_1.0.17-2.dsc sane-utils_1.0.17-2_i386.deb to pool/main/s/sane-backends/sane-utils_1.0.17-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sane-backends-extras 1.0.17.2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 11:58:44 +0200 Source: sane-backends-extras Binary: libsane-extras libsane-extras-dev Architecture: source i386 Version: 1.0.17.2 Distribution: unstable Urgency: low Maintainer: Julien BLACHE [EMAIL PROTECTED] Changed-By: Julien BLACHE [EMAIL PROTECTED] Description: libsane-extras - API library for scanners -- extra backends libsane-extras-dev - API development library for scanners [development files] Changes: sane-backends-extras (1.0.17.2) unstable; urgency=low . * debian/udev/libsane-extras.rules: + Fixed test, removed RUN rules. Files: e464629b035e9322e0178c1725e4718f 724 graphics optional sane-backends-extras_1.0.17.2.dsc c8f34c12ff0fca3471c39c34927fd843 655022 graphics optional sane-backends-extras_1.0.17.2.tar.gz adcc37a8e13761b5f5d602f1678d1759 135092 libs optional libsane-extras_1.0.17.2_i386.deb 48315ff10ea95d42ff047f324a013c68 124150 libdevel optional libsane-extras-dev_1.0.17.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQhXWzWFP1/XWUWkRAo5eAJ9qiAxi02j9deWOKyI28fQ9DAsCdwCfciO7 /0oLN/as1zlsUKjJkD42Bzg= =YWGX -END PGP SIGNATURE- Accepted: libsane-extras-dev_1.0.17.2_i386.deb to pool/main/s/sane-backends-extras/libsane-extras-dev_1.0.17.2_i386.deb libsane-extras_1.0.17.2_i386.deb to pool/main/s/sane-backends-extras/libsane-extras_1.0.17.2_i386.deb sane-backends-extras_1.0.17.2.dsc to pool/main/s/sane-backends-extras/sane-backends-extras_1.0.17.2.dsc sane-backends-extras_1.0.17.2.tar.gz to pool/main/s/sane-backends-extras/sane-backends-extras_1.0.17.2.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cgoban 1.9.14-11 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 08:54:05 +0200 Source: cgoban Binary: cgoban Architecture: source i386 Version: 1.9.14-11 Distribution: unstable Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: cgoban - complete Go board Changes: cgoban (1.9.14-11) unstable; urgency=low . * Applied workaround for autotools timestamp issue, see bug #362880. Files: 770b5f62b92672a537bccf5e77c2d3af 581 games optional cgoban_1.9.14-11.dsc 9d063b9882c2cc9e7ac209c894d9e7d7 59630 games optional cgoban_1.9.14-11.diff.gz 1b7d86a2c72ff5b066f14fca82e14e18 238432 games optional cgoban_1.9.14-11_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQeqshOZKoAn8AVwRAmU5AKCAAXbaqp+xaDWcoy9tIPndGkYXiwCcDtFg ai5xW0bft95TH1BubrVop7A= =xmGQ -END PGP SIGNATURE- Accepted: cgoban_1.9.14-11.diff.gz to pool/main/c/cgoban/cgoban_1.9.14-11.diff.gz cgoban_1.9.14-11.dsc to pool/main/c/cgoban/cgoban_1.9.14-11.dsc cgoban_1.9.14-11_i386.deb to pool/main/c/cgoban/cgoban_1.9.14-11_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libcache-perl 2.04-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 21 Mar 2006 14:26:37 + Source: libcache-perl Binary: libcache-perl Architecture: source all Version: 2.04-1 Distribution: unstable Urgency: low Maintainer: Stephen Quinney [EMAIL PROTECTED] Changed-By: Dominic Hargreaves [EMAIL PROTECTED] Description: libcache-perl - the Cache interface Changes: libcache-perl (2.04-1) unstable; urgency=low . * New upstream release Files: f95df4aecd25c72a6be5fd72979487aa 763 perl optional libcache-perl_2.04-1.dsc c64b8dd8f04e101bd20cde0c7c2e3d17 34501 perl optional libcache-perl_2.04.orig.tar.gz 5f6d621c4a0f90ed847a76767818e545 2091 perl optional libcache-perl_2.04-1.diff.gz 339d0391130b2c54ea86b9c4a4bbcf4a 72510 perl optional libcache-perl_2.04-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQfH4ITGblEwaW+URAuV3AKDH8E147vedQyfQfelrFtnD0u64xwCePBw8 IZIjyjJ3J7IXrcbl+tothqk= =8pdo -END PGP SIGNATURE- Accepted: libcache-perl_2.04-1.diff.gz to pool/main/libc/libcache-perl/libcache-perl_2.04-1.diff.gz libcache-perl_2.04-1.dsc to pool/main/libc/libcache-perl/libcache-perl_2.04-1.dsc libcache-perl_2.04-1_all.deb to pool/main/libc/libcache-perl/libcache-perl_2.04-1_all.deb libcache-perl_2.04.orig.tar.gz to pool/main/libc/libcache-perl/libcache-perl_2.04.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted liburi-fetch-perl 0.05-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 21 Mar 2006 19:24:42 + Source: liburi-fetch-perl Binary: liburi-fetch-perl Architecture: source all Version: 0.05-1 Distribution: unstable Urgency: low Maintainer: Stephen Quinney [EMAIL PROTECTED] Changed-By: Dominic Hargreaves [EMAIL PROTECTED] Description: liburi-fetch-perl - Smart URI fetching/caching Changes: liburi-fetch-perl (0.05-1) unstable; urgency=low . * New upstream release Files: 6d588b83b3859fc1013ff11139b4fe88 712 perl optional liburi-fetch-perl_0.05-1.dsc e7b186c7a2f6aa5d5aed09c344a086b0 20201 perl optional liburi-fetch-perl_0.05.orig.tar.gz a6f98c92aefc505dcb8a9e5e44513d98 2090 perl optional liburi-fetch-perl_0.05-1.diff.gz ca19e7579fa78b93fa9eeaa784f8f466 15582 perl optional liburi-fetch-perl_0.05-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQfTlITGblEwaW+URAnfXAJ9lNVh8RoGsyXSOMI4wo1QltuFCXACeOjff asinurDvXP60+VyZGKkHLYI= =LP6d -END PGP SIGNATURE- Accepted: liburi-fetch-perl_0.05-1.diff.gz to pool/main/libu/liburi-fetch-perl/liburi-fetch-perl_0.05-1.diff.gz liburi-fetch-perl_0.05-1.dsc to pool/main/libu/liburi-fetch-perl/liburi-fetch-perl_0.05-1.dsc liburi-fetch-perl_0.05-1_all.deb to pool/main/libu/liburi-fetch-perl/liburi-fetch-perl_0.05-1_all.deb liburi-fetch-perl_0.05.orig.tar.gz to pool/main/libu/liburi-fetch-perl/liburi-fetch-perl_0.05.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libvcs-lite-perl 0.08-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 21 Mar 2006 19:47:41 + Source: libvcs-lite-perl Binary: libvcs-lite-perl Architecture: source all Version: 0.08-1 Distribution: unstable Urgency: low Maintainer: Stephen Quinney [EMAIL PROTECTED] Changed-By: Dominic Hargreaves [EMAIL PROTECTED] Description: libvcs-lite-perl - Minimal version control system Changes: libvcs-lite-perl (0.08-1) unstable; urgency=low . * New upstream release Files: 3c3650a531e5447c65630453c5e2ad1a 666 perl optional libvcs-lite-perl_0.08-1.dsc 4f81c6bfbceec6abe4cd33afcbefa93a 16575 perl optional libvcs-lite-perl_0.08.orig.tar.gz 60847a4c8915e79ce35d3c89dec8bb0a 3451 perl optional libvcs-lite-perl_0.08-1.diff.gz 1f6fcb3c6e49fdbf437744176d1e4883 25206 perl optional libvcs-lite-perl_0.08-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQfWWITGblEwaW+URAkFxAJ9AxQ57WN3ZViMGkTqmawPPjBrBnACfdE1w dzer8wBy4VcIfFKUuzSWA4w= =HP33 -END PGP SIGNATURE- Accepted: libvcs-lite-perl_0.08-1.diff.gz to pool/main/libv/libvcs-lite-perl/libvcs-lite-perl_0.08-1.diff.gz libvcs-lite-perl_0.08-1.dsc to pool/main/libv/libvcs-lite-perl/libvcs-lite-perl_0.08-1.dsc libvcs-lite-perl_0.08-1_all.deb to pool/main/libv/libvcs-lite-perl/libvcs-lite-perl_0.08-1_all.deb libvcs-lite-perl_0.08.orig.tar.gz to pool/main/libv/libvcs-lite-perl/libvcs-lite-perl_0.08.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wmpuzzle 0.5.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 10:28:40 +0200 Source: wmpuzzle Binary: wmpuzzle Architecture: source i386 Version: 0.5.0-1 Distribution: unstable Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: wmpuzzle - WindowMaker dock app 4x4 puzzle Closes: 346961 Changes: wmpuzzle (0.5.0-1) unstable; urgency=low . * New upstream release. * Acknowledging NMU, thanks to Marc Brockschmidt, closes: #346961. * Added source xpm files to Debian package. * Added watch file. * Fixed menu file. * Fixed POSIX compliance of debian/rules. * Updated standards version. * Updated FSF addresse. Files: 61f5f50383cebd3c9792f819076381c7 584 games optional wmpuzzle_0.5.0-1.dsc 14b0a7dad8c932964b115c9cc9d177f7 81900 games optional wmpuzzle_0.5.0.orig.tar.gz cb2c8233e6298a18da7a5f9dbd8ce758 2611 games optional wmpuzzle_0.5.0-1.diff.gz 73c3d6cf1645b014182ea583e008366f 24394 games optional wmpuzzle_0.5.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQgB/hOZKoAn8AVwRAtEQAKC0ANhLo+OdhPe4lLQwRFYLGROrkwCgywYS zCe5Ur8Etl6yrwTE8hGhfXk= =lSqI -END PGP SIGNATURE- Accepted: wmpuzzle_0.5.0-1.diff.gz to pool/main/w/wmpuzzle/wmpuzzle_0.5.0-1.diff.gz wmpuzzle_0.5.0-1.dsc to pool/main/w/wmpuzzle/wmpuzzle_0.5.0-1.dsc wmpuzzle_0.5.0-1_i386.deb to pool/main/w/wmpuzzle/wmpuzzle_0.5.0-1_i386.deb wmpuzzle_0.5.0.orig.tar.gz to pool/main/w/wmpuzzle/wmpuzzle_0.5.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mindi 1.07-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 9 Apr 2006 12:50:36 +1000 Source: mindi Binary: mindi Architecture: source i386 Version: 1.07-1 Distribution: unstable Urgency: low Maintainer: Andree Leidenfrost [EMAIL PROTECTED] Changed-By: Andree Leidenfrost [EMAIL PROTECTED] Description: mindi - creates boot/root disks based on your system Closes: 357785 Changes: mindi (1.07-1) unstable; urgency=low . * New upstream release: - source is release 1.0.7-r460; - use old version format, i.e. 1.07 rather than new upstream format 1.0.7 to avoid epoch - re-sync will happen for 1.2.0; - removed binary files from upstream source to be compliant with Debian policy: - rootfs/bin/busybox-i386, - rootfs/bin/busybox-i386.net, - rootfs/bin/busybox-ia64; - all Debian changes integrated upstream apart from: - DebFindFailsafe, - IncludeCustomDependencies, - TryToBeCleverAboutInitrd; - analyze-my-lvm moved to /usr/lib/mindi - put new download location ftp://ftp.mondorescue.org/src/ in copyright file; - README is now in upstream - removed from debian directory and adjusted docs file accordingly; - revert change where no bigger bootdisks would get created if 1722 one succees because the 1722 doesn't contain modules to mount optical drive. * Make message unambiguous in case mounting of floppy images fails in mindi. (Closes: #357785.)) * Changed maintainer email address to [EMAIL PROTECTED] Files: 3fd42f9d65db9c16e73b3a3d6123dcf8 655 utils optional mindi_1.07-1.dsc aa3301680f8acdf5ad900228021c0a7a 263533 utils optional mindi_1.07.orig.tar.gz 279232c68c306c61e9d954be86127461 18074 utils optional mindi_1.07-1.diff.gz 0bf7712df426d5a540e74abb1402dfed 152018 utils optional mindi_1.07-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEPzzkiLvX3b2IzawRAnB3AJ4ucEjmgH1F2ylhJkzjSliczHQ8FACeJy4p n+Gw5sDt3/3q2X7QQmTIqLo= =VIUj -END PGP SIGNATURE- Accepted: mindi_1.07-1.diff.gz to pool/main/m/mindi/mindi_1.07-1.diff.gz mindi_1.07-1.dsc to pool/main/m/mindi/mindi_1.07-1.dsc mindi_1.07-1_i386.deb to pool/main/m/mindi/mindi_1.07-1_i386.deb mindi_1.07.orig.tar.gz to pool/main/m/mindi/mindi_1.07.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cupsys 1.1.99.rc2-0exp1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Sun, 16 Apr 2006 17:49:57 +0900
Source: cupsys
Binary: cupsys-bsd libcupsys2-dev libcupsys2 cupsys libcupsys2-gnutls10
libcupsimage2-dev libcupsimage2 cupsys-client
Architecture: source i386 all
Version: 1.1.99.rc2-0exp1
Distribution: experimental
Urgency: low
Maintainer: Debian CUPS Maintainers [EMAIL PROTECTED]
Changed-By: Kenshi Muto [EMAIL PROTECTED]
Description:
cupsys - Common UNIX Printing System(tm) - server
cupsys-bsd - Common UNIX Printing System(tm) - BSD commands
cupsys-client - Common UNIX Printing System(tm) - client programs (SysV)
libcupsimage2 - Common UNIX Printing System(tm) - image libs
libcupsimage2-dev - Common UNIX Printing System(tm) - image development files
libcupsys2 - Common UNIX Printing System(tm) - libs
libcupsys2-dev - Common UNIX Printing System(tm) - development files
libcupsys2-gnutls10 - Common UNIX Printing System(tm) - dummy libs for
transition
Closes: 280718 335199 347641 347829 356911 357969 361258 362070
Changes:
cupsys (1.1.99.rc2-0exp1) experimental; urgency=low
.
[ Kenshi Muto ]
* New upstream release 1.2RC2.
- Because -fpie config becomes optional, compiler works on amd64 and
other architectures. (closes: #335199)
* Enable LDAP support.
* Remove duplicated update-rc.d (closes: #356911)
* Stopped asking admin password because it works only if user chooses
digest authentication. The default configuration of Debian uses
PAM and basic authentication.
* Enable dbus support.
* 03_clean.dpatch: Remove produced and remained files during build.
* Now CUPS uses 'lp' user/group privilege to call backend or any other
programs.
CUPS SystemGroup is 'lpadmin'. You need to add users who are allowed
to add/modify/remove printers/jobs/classes.
* Remove image.h.patch from source. It is no longer needed.
* 02_configure.dpath: Remove -rpath from configure.
* Fix typo in cupsys-bsd description. (closes: #362070)
* Add Galician debconf translation. (closes: #361258)
* Update Danish debconf translation. (closes: #357969)
* Use 'reload' during logrotate instead of 'restart'. It looks safe
on CUPS 1.2. (though job-restart problem still remains)
* set TZ in init script only if TZ isn't defined yet.
* Use if-fi structure style for postrotate of logrotate script.
It solves error when cupsys is not running. (closes: #347641)
* Unset TMPDIR environment variable before running daemon. (closes: #347829)
* Removed /etc/cups/pdftops.conf because it was for pdftops of upstream
version. Debian CUPS uses xpdf-utils wrapper and doesn't need
pdftops.conf.
* Notice: /etc/cups/client.conf has been removed upstream.
* Notice: {dis,en}able have been renamed to cups{dis,en}able.
.
[ Martin Pitt ]
* debian/patches/48_stdlib.dpatch: Adapted to new upstream version.
* debian/cupsys.init.d:
- Fix arguments of start-stop-daemon and remove the hideous kill
algorithm.
- Ensure that /var/run/cupsd exists; this makes the init script work with
/var/run mounted on a tmpfs.
* debian/libcupsys2-dev.files, debian/libcupsimage2-dev.files: Remove static
library; upstream does not build them any more, and they are useless
anyway.
* Add debian/patches/06_disable_backend_setuid.dpatch: Remove the uid
changing in scheduler/cups-deviced.c which was introduced recently in
upstream. It totally breaks device node access (e. g. /dev/lp0 is root:lp
0660, which is inaccessible for a process which runs as lp:root).
* debian/rules: Remove --with-cups-user, upstream does not support
it any more.
* debian/patches/09_runasuser_fixes.dpatch: RunAsUser was removed upstream;
rename the patch to 09_runasuser.dpatch and rewrite it:
- Enclose all changes in an #if CUPS_DROP_PRIVILEGES, so that it is easy to
enable this feature.
- scheduler/main.c: Drop privileges after initialization.
- scheduler/conf.c: If we build with CUPS_DROP_PRIVILEGES, set RunUser to
User instead of getuid(), since at that point we will always run as root
(privileges cannot yet be dropped at that point).
- config-scripts/cups-defaults.m4: Add --enable-privilege-dropping option.
- config.h.in: Add CUPS_DROP_PRIVILEGES option template.
* Add debian/patches/09_runasuser_autoconf.dpatch: autoconf changes for
09_runasuser_fixes.dpatch changes.
* debian/pdftops: Fix reading from stdin (https://launchpad.net/bugs/17124)
* debian/cupsys.preinst: Remove dangling /etc/cups/pdftops.conf symlink on
upgrades to unbreak printing with poppler-utils.
* debian/control: Add poppler-utils alternative for xpdf-utils dependency.
* Add debian/patches/12_quiesce_ipp_logging.dpatch:
- Drop successful IPP messages to log level 'debug' and unsuccessful ones
to 'info'.
- Do not flood access_log with successful CUPS-Get-Printers and
Accepted mondo 2.07-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 10:44:07 +1000 Source: mondo Binary: mondo-doc mondo Architecture: source i386 all Version: 2.07-1 Distribution: unstable Urgency: low Maintainer: Andree Leidenfrost [EMAIL PROTECTED] Changed-By: Andree Leidenfrost [EMAIL PROTECTED] Description: mondo - powerful disaster recovery suite mondo-doc - manual for Mondo, a powerful disaster recovery suite Closes: 331060 Changes: mondo (2.07-1) unstable; urgency=low . * New upstream release: - source is release 2.0.7-r460; - use old version format, i.e. 2.07 rather than new upstream format 2.0.7 to avoid epoch - re-sync will happen for 2.2.0; - all Debian changes integrated upstream apart from fix for #320152 (see 2.04-6); - implements length check for '-E' argument (Closes: #331060.); - upstream doesn't build libraries anymore - adjusted rules and mondo.dirs files and removed lintian override file accordingly; - mondo's scripts are now under /usr/share/mondo - adjusted mondo.dirs and rules file accordingly and depend on mindi = 1.07 as older versions are not aware of this; - put new download location ftp://ftp.mondorescue.org/src/ in copyright file; - README is now in upstream - removed from debian directory and adjusted mondo.docs accordingly; - documentation is no longer installed by upstream Makefile, documentation is now available in various formats in addition to html - adjusted rules and mondo-doc.docs files accordingly. * Fix bug where paths in parameters for '-E' and '-I' would not get properly separated from each other by integration upstream SVN r468. * Added -D_GNU_SOURCE to CFLAGS in rules file to avoid compiler warning about undefined asprintf introduced by previous change. * Changed maintainer email address to [EMAIL PROTECTED] * Fixed verify for NFS by swapping nfs_remote_dir and isodir when assembling name for image file to verify. (Committed upstream.) * Changed declaration of setenv_mondo_lib() to setenv_mondo_share() to fix compiler warning. (Committed upstream.) Files: 3bc656c82e6b761e8d7d52fe9a847bb1 685 utils optional mondo_2.07-1.dsc 515682b623108e3c0153b9d869718382 2610864 utils optional mondo_2.07.orig.tar.gz 4482bb68f26f506352679e6182d67d4b 34245 utils optional mondo_2.07-1.diff.gz 6738f05fb5116534c6f17111c56e006b 425214 utils optional mondo_2.07-1_i386.deb 93a0291cf17a00fd7106e345bbc4b762 1541740 doc optional mondo-doc_2.07-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQZPGiLvX3b2IzawRAjUiAJ9cmat/ebtKHCBalrjdEwgVoaODGgCghas4 WDDn2dzIncA6YtrcqbtGXMs= =5foV -END PGP SIGNATURE- Accepted: mondo-doc_2.07-1_all.deb to pool/main/m/mondo/mondo-doc_2.07-1_all.deb mondo_2.07-1.diff.gz to pool/main/m/mondo/mondo_2.07-1.diff.gz mondo_2.07-1.dsc to pool/main/m/mondo/mondo_2.07-1.dsc mondo_2.07-1_i386.deb to pool/main/m/mondo/mondo_2.07-1_i386.deb mondo_2.07.orig.tar.gz to pool/main/m/mondo/mondo_2.07.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted httrack 3.40.4-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 11:10:08 +0200 Source: httrack Binary: proxytrack libhttrack1 httrack httrack-doc libhttrack-dev webhttrack Architecture: source i386 all Version: 3.40.4-1 Distribution: unstable Urgency: medium Maintainer: Xavier Roche [EMAIL PROTECTED] Changed-By: Xavier Roche [EMAIL PROTECTED] Description: httrack- Copy websites to your computer (Offline browser) httrack-doc - Httrack website copier additional documentation libhttrack-dev - Httrack website copier includes and development files libhttrack1 - Httrack website copier library proxytrack - Build HTTP Caches using archived websites copied by HTTrack webhttrack - Copy websites to your computer, httrack with a Web interface Closes: 362836 Changes: httrack (3.40.4-1) unstable; urgency=medium . * Fixed SSL version, fixed Packages must not require the existance of any files in /usr/share/doc in order to function (closes:#362836) Files: 758a76c467ed803a58a1fdb05d22f8e7 642 web optional httrack_3.40.4-1.dsc 9e4de064afc1dfcb6f50b773f8081f1c 1626176 web optional httrack_3.40.4.orig.tar.gz 5b0477ebb5d41d57026e3c742420bf23 6647 web optional httrack_3.40.4-1.diff.gz 41f59f0411ee8666493a5824d67a0168 15446 doc optional httrack-doc_3.40.4-1_all.deb 431a1c4f55e56c6d6d7c0ac156273512 33098 web optional httrack_3.40.4-1_i386.deb db8fe7eadbb6eb1f247e5d151f59c85b 969184 web optional webhttrack_3.40.4-1_i386.deb 0ebbbce91002c26d109da5d769bf1c20 422714 libs optional libhttrack1_3.40.4-1_i386.deb 4c792e7addecde7a1f8ecbf9be9bdbe0 574412 libdevel optional libhttrack-dev_3.40.4-1_i386.deb dcf81166b7367dd5c1a220fff359756a 62826 web optional proxytrack_3.40.4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEQhVE3PjWWwPzWYgRAnFKAJ4vw1Nfn5199/TMKCR9W7f9ODX6egCguuJh uALx3bUfUEjeVFptUrFPhhg= =Wd3w -END PGP SIGNATURE- Accepted: httrack-doc_3.40.4-1_all.deb to pool/main/h/httrack/httrack-doc_3.40.4-1_all.deb httrack_3.40.4-1.diff.gz to pool/main/h/httrack/httrack_3.40.4-1.diff.gz httrack_3.40.4-1.dsc to pool/main/h/httrack/httrack_3.40.4-1.dsc httrack_3.40.4-1_i386.deb to pool/main/h/httrack/httrack_3.40.4-1_i386.deb httrack_3.40.4.orig.tar.gz to pool/main/h/httrack/httrack_3.40.4.orig.tar.gz libhttrack-dev_3.40.4-1_i386.deb to pool/main/h/httrack/libhttrack-dev_3.40.4-1_i386.deb libhttrack1_3.40.4-1_i386.deb to pool/main/h/httrack/libhttrack1_3.40.4-1_i386.deb proxytrack_3.40.4-1_i386.deb to pool/main/h/httrack/proxytrack_3.40.4-1_i386.deb webhttrack_3.40.4-1_i386.deb to pool/main/h/httrack/webhttrack_3.40.4-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted elementtree 1.2.6-5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 12:26:23 +0200 Source: elementtree Binary: python-elementtree python2.4-elementtree python-elementtree-doc python2.3-elementtree Architecture: source all Version: 1.2.6-5 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team [EMAIL PROTECTED] Changed-By: Torsten Marek [EMAIL PROTECTED] Description: python-elementtree - Light-weight toolkit for XML processing python-elementtree-doc - Documentation for ElementTree python2.3-elementtree - Light-weight toolkit for XML processing python2.4-elementtree - Light-weight toolkit for XML processing Changes: elementtree (1.2.6-5) unstable; urgency=low . * Raise debhelper compatibility level to 5 * Switch to cdbs * Set maintainer to Debian Python modules team and added myself to uploaders with new address * Removed outdated entries in Replaces field * Put python-elementtree-doc into doc section Files: 45d08bb27bca7b29d9efd829ad8cb0a3 800 python optional elementtree_1.2.6-5.dsc dff0693efd35859832e67c3d1f73e299 2491 python optional elementtree_1.2.6-5.diff.gz f65b418c4b2d093b2d6b14dc580c8075 7900 python optional python-elementtree_1.2.6-5_all.deb 9510a9e49c766ebff0644d74fc1e2c6a 28900 python optional python2.3-elementtree_1.2.6-5_all.deb 587321a5b2e28c817a976ffbb7fb9748 28904 python optional python2.4-elementtree_1.2.6-5_all.deb 508f1ae1d27ff898fd9bc0454ed97a8a 20760 doc optional python-elementtree-doc_1.2.6-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQhyFfMVFHqJEyFgRAnB8AJ4kTfz+duS3I4SwkVeZBrcqSckDtQCdFOJh kjLOJtlkYVsBjHkWFvKOy14= =ctmg -END PGP SIGNATURE- Accepted: elementtree_1.2.6-5.diff.gz to pool/main/e/elementtree/elementtree_1.2.6-5.diff.gz elementtree_1.2.6-5.dsc to pool/main/e/elementtree/elementtree_1.2.6-5.dsc python-elementtree-doc_1.2.6-5_all.deb to pool/main/e/elementtree/python-elementtree-doc_1.2.6-5_all.deb python-elementtree_1.2.6-5_all.deb to pool/main/e/elementtree/python-elementtree_1.2.6-5_all.deb python2.3-elementtree_1.2.6-5_all.deb to pool/main/e/elementtree/python2.3-elementtree_1.2.6-5_all.deb python2.4-elementtree_1.2.6-5_all.deb to pool/main/e/elementtree/python2.4-elementtree_1.2.6-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted celementtree 1.0.5-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 12:33:31 +0200 Source: celementtree Binary: python2.4-celementtree python2.3-celementtree python-celementtree Architecture: source all i386 Version: 1.0.5-2 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team [EMAIL PROTECTED] Changed-By: Torsten Marek [EMAIL PROTECTED] Description: python-celementtree - Light-weight toolkit for XML processing python2.3-celementtree - Light-weight toolkit for XML processing python2.4-celementtree - Light-weight toolkit for XML processing Changes: celementtree (1.0.5-2) unstable; urgency=low . * Raise debhelper compatibility level to 5 * Switch to cdbs * Set maintainer to Debian Python modules team and added myself to uploaders with new address * Create cdbs patch for setup.py Files: 6aa1fb23c17194938bc600f0d3f98d46 814 python optional celementtree_1.0.5-2.dsc 9422731b2d5f129071d2074a295574cc 2918 python optional celementtree_1.0.5-2.diff.gz f6ae58241d24d7444d44abddac2b25f0 7618 python optional python-celementtree_1.0.5-2_all.deb 7ab7734566d3c65ae37906be230e0297 22742 python optional python2.3-celementtree_1.0.5-2_i386.deb 28ca0e7138e17cceffb56378de23f827 23108 python optional python2.4-celementtree_1.0.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQh5WfMVFHqJEyFgRAhpBAJ4sM6dDSn8ZNfLkEMLgRAdt7qJ0HACgkesq BaUKB03wkOxnMKzF2hX7L2I= =ta9m -END PGP SIGNATURE- Accepted: celementtree_1.0.5-2.diff.gz to pool/main/c/celementtree/celementtree_1.0.5-2.diff.gz celementtree_1.0.5-2.dsc to pool/main/c/celementtree/celementtree_1.0.5-2.dsc python-celementtree_1.0.5-2_all.deb to pool/main/c/celementtree/python-celementtree_1.0.5-2_all.deb python2.3-celementtree_1.0.5-2_i386.deb to pool/main/c/celementtree/python2.3-celementtree_1.0.5-2_i386.deb python2.4-celementtree_1.0.5-2_i386.deb to pool/main/c/celementtree/python2.4-celementtree_1.0.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted simpletal 4.1-5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 12:19:54 +0200 Source: simpletal Binary: python2.4-simpletal python-simpletal python2.3-simpletal Architecture: source all Version: 4.1-5 Distribution: unstable Urgency: low Maintainer: Igor Stroh [EMAIL PROTECTED] Changed-By: Igor Stroh [EMAIL PROTECTED] Description: python-simpletal - Simple TAL, TALES and METAL implementation python2.3-simpletal - Simple TAL, TALES and METAL implementation, python 2.3 version python2.4-simpletal - Simple TAL, TALES and METAL implementation, python 2.4 version Changes: simpletal (4.1-5) unstable; urgency=low . * Imported simpletal package into debian python-modules svn repository * debian/control: added Debian Python Modules Team to Uploaders Files: b72fb02014773575fbcf9b8b310f9499 758 python optional simpletal_4.1-5.dsc 88416aaff7b245be54d7fb93824b1972 2702 python optional simpletal_4.1-5.diff.gz 89064466f1538c94545e3a600f71fa90 23496 python optional python-simpletal_4.1-5_all.deb 677409810ab2e02937f528e8e25a4e0b 32628 python optional python2.3-simpletal_4.1-5_all.deb 03036f58ed04f590358a2e6ff6bbedfb 32626 python optional python2.4-simpletal_4.1-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQiVm9A/NYF0eULoRAvanAJ9ZrNDUcoU3LrLZsLHmnSLwS8+aFwCgn92R I2MqslB0UJ0m+YaP9DbzRns= =hxnL -END PGP SIGNATURE- Accepted: python-simpletal_4.1-5_all.deb to pool/main/s/simpletal/python-simpletal_4.1-5_all.deb python2.3-simpletal_4.1-5_all.deb to pool/main/s/simpletal/python2.3-simpletal_4.1-5_all.deb python2.4-simpletal_4.1-5_all.deb to pool/main/s/simpletal/python2.4-simpletal_4.1-5_all.deb simpletal_4.1-5.diff.gz to pool/main/s/simpletal/simpletal_4.1-5.diff.gz simpletal_4.1-5.dsc to pool/main/s/simpletal/simpletal_4.1-5.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted xlockmore 1:5.21-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Apr 2006 22:21:07 -0400 Source: xlockmore Binary: xlockmore xlockmore-gl Architecture: source i386 Version: 1:5.21-3 Distribution: unstable Urgency: low Maintainer: Michael Stone [EMAIL PROTECTED] Changed-By: Michael Stone [EMAIL PROTECTED] Description: xlockmore - Lock X11 display until password is entered. xlockmore-gl - Lock X11 display until password is entered -- GL version Changes: xlockmore (1:5.21-3) unstable; urgency=low . * Actually fix that...try to upload the right one this time... Files: c6e59d49f2fee08b671f45c4b38b9727 874 x11 optional xlockmore_5.21-3.dsc 57642ddf5b9c840be87e525d74814fd7 58385 x11 optional xlockmore_5.21-3.diff.gz b08e445b273022fc4eb3ed4576c9d90e 1099232 x11 optional xlockmore-gl_5.21-3_i386.deb 399b47986930ef34704cf48383b8b69a 632776 x11 extra xlockmore_5.21-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iQCVAwUBREImjg0hVr09l8FJAQKyhAQAo5lJZMx70RQb2BMASwaSe5h/93c8ZTrs ejBPRxQ+tzSVTfgOqdnGj7O84z3pDD3BZfMShyHNl3JrZ/ZCK9f4air3GVR1My+m VbxVg5Ia6tm5g+rg7O3Bdy+M7+2HN6tVb1A/E4b1E87Ql0S1weH7izBLEHcGeXHY I2DmAZk8ffc= =+IQu -END PGP SIGNATURE- Accepted: xlockmore-gl_5.21-3_i386.deb to pool/main/x/xlockmore/xlockmore-gl_5.21-3_i386.deb xlockmore_5.21-3.diff.gz to pool/main/x/xlockmore/xlockmore_5.21-3.diff.gz xlockmore_5.21-3.dsc to pool/main/x/xlockmore/xlockmore_5.21-3.dsc xlockmore_5.21-3_i386.deb to pool/main/x/xlockmore/xlockmore_5.21-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted python-reportlab 1.20debian-5 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 13:19:23 +0200 Source: python-reportlab Binary: python2.4-reportlab python-reportlab python2.3-reportlab python-reportlab-doc Architecture: source all Version: 1.20debian-5 Distribution: unstable Urgency: low Maintainer: Igor Stroh [EMAIL PROTECTED] Changed-By: Igor Stroh [EMAIL PROTECTED] Description: python-reportlab - ReportLab library to create PDF documents using Python python-reportlab-doc - Documentation for the ReportLab Python library (PDF format) python2.3-reportlab - ReportLab library to create PDF documents using Python (2.3) python2.4-reportlab - ReportLab library to create PDF documents using Python (2.4) Changes: python-reportlab (1.20debian-5) unstable; urgency=low . * Imported python-reportlab package into debian python-modules svn repository * debian/control: added Debian Python Modules Team to Uploaders Files: da0ea6538edec02c7135dc823e4beb43 842 python optional python-reportlab_1.20debian-5.dsc f175e31b27136fb6aee44623cce6ea40 18601 python optional python-reportlab_1.20debian-5.diff.gz 36ae75fd7fdec7a16f24998a863cd342 70780 python optional python-reportlab_1.20debian-5_all.deb 25cbc9780c27a66a75af20345f906be9 1491594 doc optional python-reportlab-doc_1.20debian-5_all.deb c39557b3af548e9bd36fc79eb36bd860 667614 python optional python2.3-reportlab_1.20debian-5_all.deb 9e70003bb0ef1cd1c2a0fb6df2055575 667618 python optional python2.4-reportlab_1.20debian-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQine9A/NYF0eULoRAtw+AJ9FIqDs39CesHG4s99bCHYhczI0fwCguqf0 2Cx4dCRjMcHVm2afxjgBo80= =n1q5 -END PGP SIGNATURE- Accepted: python-reportlab-doc_1.20debian-5_all.deb to pool/main/p/python-reportlab/python-reportlab-doc_1.20debian-5_all.deb python-reportlab_1.20debian-5.diff.gz to pool/main/p/python-reportlab/python-reportlab_1.20debian-5.diff.gz python-reportlab_1.20debian-5.dsc to pool/main/p/python-reportlab/python-reportlab_1.20debian-5.dsc python-reportlab_1.20debian-5_all.deb to pool/main/p/python-reportlab/python-reportlab_1.20debian-5_all.deb python2.3-reportlab_1.20debian-5_all.deb to pool/main/p/python-reportlab/python2.3-reportlab_1.20debian-5_all.deb python2.4-reportlab_1.20debian-5_all.deb to pool/main/p/python-reportlab/python2.4-reportlab_1.20debian-5_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted quota 3.13-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 13:57:07 +0200 Source: quota Binary: quota Architecture: source i386 Version: 3.13-5 Distribution: unstable Urgency: medium Maintainer: Michael Meskes [EMAIL PROTECTED] Changed-By: Michael Meskes [EMAIL PROTECTED] Description: quota - implementation of the disk quota system Closes: 362729 Changes: quota (3.13-5) unstable; urgency=medium . * Added Italian translation, closes: #362729 Files: e9cd97ce375c53bb0130d6c977bfde9e 613 admin optional quota_3.13-5.dsc 49ea6ddff041257031797d1b8d4fe7fd 33524 admin optional quota_3.13-5.diff.gz 2e6195e5d8682c7f44f40014a1350f31 456248 admin optional quota_3.13-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQjGoVkEm8inxm9ERAqAQAJ9n6wJwHrt2huc3PxkaAv40MZ3FcgCeMBQA bE0px8tPG4ioEebWwb+LjSo= =aubV -END PGP SIGNATURE- Accepted: quota_3.13-5.diff.gz to pool/main/q/quota/quota_3.13-5.diff.gz quota_3.13-5.dsc to pool/main/q/quota/quota_3.13-5.dsc quota_3.13-5_i386.deb to pool/main/q/quota/quota_3.13-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted samizdat 0.5.5.20060416-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 15:05:10 +0300 Source: samizdat Binary: libsamizdat-ruby1.8 samizdat libsamizdat-ruby Architecture: source all Version: 0.5.5.20060416-1 Distribution: experimental Urgency: low Maintainer: Dmitry Borodaenko [EMAIL PROTECTED] Changed-By: Dmitry Borodaenko [EMAIL PROTECTED] Description: libsamizdat-ruby - Samizdat module for Ruby libsamizdat-ruby1.8 - Samizdat module for Ruby 1.8 samizdat - Collaboration and open publishing engine Changes: samizdat (0.5.5.20060416-1) experimental; urgency=low . * New upstream snapshot 2005-04-16: - fixed RSS/DRbUnknown bug - synchronized Cache - more security improvements. Files: d4d2d823ad62d38c94f20cc7ab381573 665 web optional samizdat_0.5.5.20060416-1.dsc b2cca2b8eb6761d8adf0d0fe8bc580a1 156154 web optional samizdat_0.5.5.20060416.orig.tar.gz b078b7d98ced2e543254d6cf02b99f8a 3556 web optional samizdat_0.5.5.20060416-1.diff.gz 193abf5364194aafebe430752967326c 118918 web optional samizdat_0.5.5.20060416-1_all.deb 7a4c1c4baf78ddec8b1f6c31df681a41 15092 interpreters optional libsamizdat-ruby_0.5.5.20060416-1_all.deb d6d9527b8654abb29cf0b1f51bba4d0a 24194 interpreters optional libsamizdat-ruby1.8_0.5.5.20060416-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkRCM7kACgkQxhqJXoXuPg4uoACgnGC5KEgMwAKsDmeiiOhdma5w yO4AmQGswRCzotYzAkTrw8knwNGDfsF3 =ywvv -END PGP SIGNATURE- Accepted: libsamizdat-ruby1.8_0.5.5.20060416-1_all.deb to pool/main/s/samizdat/libsamizdat-ruby1.8_0.5.5.20060416-1_all.deb libsamizdat-ruby_0.5.5.20060416-1_all.deb to pool/main/s/samizdat/libsamizdat-ruby_0.5.5.20060416-1_all.deb samizdat_0.5.5.20060416-1.diff.gz to pool/main/s/samizdat/samizdat_0.5.5.20060416-1.diff.gz samizdat_0.5.5.20060416-1.dsc to pool/main/s/samizdat/samizdat_0.5.5.20060416-1.dsc samizdat_0.5.5.20060416-1_all.deb to pool/main/s/samizdat/samizdat_0.5.5.20060416-1_all.deb samizdat_0.5.5.20060416.orig.tar.gz to pool/main/s/samizdat/samizdat_0.5.5.20060416.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted linux-wlan-ng 0.2.4+svn20060414-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 13:05:01 +0200 Source: linux-wlan-ng Binary: linux-wlan-ng-firmware linux-wlan-ng-doc linux-wlan-ng-source linux-wlan-ng Architecture: source all i386 Version: 0.2.4+svn20060414-1 Distribution: unstable Urgency: low Maintainer: Victor Seva [EMAIL PROTECTED] Changed-By: Enrico Tassi [EMAIL PROTECTED] Description: linux-wlan-ng - utilities for wireless prism2 cards linux-wlan-ng-doc - documentation for wlan-ng linux-wlan-ng-firmware - firmware files used by the linux-wlan-ng driver linux-wlan-ng-source - linux-wlan-ng driver Closes: 356595 360363 Changes: linux-wlan-ng (0.2.4+svn20060414-1) unstable; urgency=low . [ Victor Seva ] * updated to last SVN * rules.modules: clean rule depends on prepare_all (Closes: #360363 ) * linux-wlan-ng.postinst error solved with an ungly hack (Closes: #356595 ) Files: cd04eb354aa409fae61c1e33932aede8 779 admin extra linux-wlan-ng_0.2.4+svn20060414-1.dsc 55756245c774e284a97162e564dc7978 361242 admin extra linux-wlan-ng_0.2.4+svn20060414.orig.tar.gz 47c744933135fc67aa13229a 39742 admin extra linux-wlan-ng_0.2.4+svn20060414-1.diff.gz 65c48e05f8d28b05f5986feb8ce3b9c3 456192 admin extra linux-wlan-ng-source_0.2.4+svn20060414-1_all.deb 1cc099d2871d36d569cc6e9c5d027568 83542 admin extra linux-wlan-ng-doc_0.2.4+svn20060414-1_all.deb 96425b066962b569948c4b198f15805c 55352 admin extra linux-wlan-ng-firmware_0.2.4+svn20060414-1_all.deb 17ca11830dfa3a2a503ca22982b0deff 115862 admin extra linux-wlan-ng_0.2.4+svn20060414-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQjvV7kkcPgEj8vIRAu+vAJ0TI96ypoTyZNTsxlx2pP8yoMN1AwCbBF6z ckvsK5gm7ZeVnSQ01ocRPLQ= =rc4y -END PGP SIGNATURE- Accepted: linux-wlan-ng-doc_0.2.4+svn20060414-1_all.deb to pool/main/l/linux-wlan-ng/linux-wlan-ng-doc_0.2.4+svn20060414-1_all.deb linux-wlan-ng-firmware_0.2.4+svn20060414-1_all.deb to pool/main/l/linux-wlan-ng/linux-wlan-ng-firmware_0.2.4+svn20060414-1_all.deb linux-wlan-ng-source_0.2.4+svn20060414-1_all.deb to pool/main/l/linux-wlan-ng/linux-wlan-ng-source_0.2.4+svn20060414-1_all.deb linux-wlan-ng_0.2.4+svn20060414-1.diff.gz to pool/main/l/linux-wlan-ng/linux-wlan-ng_0.2.4+svn20060414-1.diff.gz linux-wlan-ng_0.2.4+svn20060414-1.dsc to pool/main/l/linux-wlan-ng/linux-wlan-ng_0.2.4+svn20060414-1.dsc linux-wlan-ng_0.2.4+svn20060414-1_i386.deb to pool/main/l/linux-wlan-ng/linux-wlan-ng_0.2.4+svn20060414-1_i386.deb linux-wlan-ng_0.2.4+svn20060414.orig.tar.gz to pool/main/l/linux-wlan-ng/linux-wlan-ng_0.2.4+svn20060414.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pan 0.93-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 12:28:21 + Source: pan Binary: pan Architecture: source i386 Version: 0.93-1 Distribution: experimental Urgency: low Maintainer: Søren Boll Overgaard [EMAIL PROTECTED] Changed-By: Søren Boll Overgaard [EMAIL PROTECTED] Description: pan- A Newsreader based on GTK2, which looks like Forte Agent Changes: pan (0.93-1) experimental; urgency=low . * New upstream release * No longer requires XML::Parser during configure, so removed from build-deps. Files: eb96dcb6ba5a30913241ea7ad57999ed 642 news optional pan_0.93-1.dsc 90a51820ab0edd1ff088db48390055ce 1746908 news optional pan_0.93.orig.tar.gz ce024ede6c1007010045f6d27ca819a7 135872 news optional pan_0.93-1.diff.gz 90a997af11e15ac4ad01b3e4dadc6561 509612 news optional pan_0.93-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQkA3PHuHUx6y3mYRArzwAJ96NB29bvtc6xp428Sq/KfUMl0s8ACfdp+6 fH66XF4fvrE+vd2SBqfuqF4= =J+cA -END PGP SIGNATURE- Accepted: pan_0.93-1.diff.gz to pool/main/p/pan/pan_0.93-1.diff.gz pan_0.93-1.dsc to pool/main/p/pan/pan_0.93-1.dsc pan_0.93-1_i386.deb to pool/main/p/pan/pan_0.93-1_i386.deb pan_0.93.orig.tar.gz to pool/main/p/pan/pan_0.93.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zsh-beta 4.3.2-dev-1+20060414-1 (source sparc all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 09:51:17 -0400 Source: zsh-beta Binary: zsh-beta-static zsh-beta-doc zsh-beta Architecture: source sparc all Version: 4.3.2-dev-1+20060414-1 Distribution: unstable Urgency: low Maintainer: Clint Adams [EMAIL PROTECTED] Changed-By: Clint Adams [EMAIL PROTECTED] Description: zsh-beta - A shell with lots of features (dev tree) zsh-beta-doc - zsh beta documentation - info/HTML format Closes: 361808 Changes: zsh-beta (4.3.2-dev-1+20060414-1) unstable; urgency=low . * Update to HEAD. * Do better 'env' completion. closes: #361808. Files: fe7564daadb95c07b0ba98c78951ce98 747 shells optional zsh-beta_4.3.2-dev-1+20060414-1.dsc 48645a804c36378395bc8442e371abe8 2300824 shells optional zsh-beta_4.3.2-dev-1+20060414.orig.tar.gz b53d7fcdf0607f579bb3a409d680e48f 690491 shells optional zsh-beta_4.3.2-dev-1+20060414-1.diff.gz 6d3966211f1132b60f63ed7af6f31b7d 693238 doc optional zsh-beta-doc_4.3.2-dev-1+20060414-1_all.deb 37f264555a91c40bc1cd34fbd3162936 2182454 shells optional zsh-beta_4.3.2-dev-1+20060414-1_sparc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Debian! iD8DBQFEQmC75m0u66uWM3ARAhGLAJ909VqYlCQTCmkhF7cDT6yIFL+WWwCg37ks WBjWtAZGmtxp+wHTi/zUP2c= =FXbW -END PGP SIGNATURE- Accepted: zsh-beta-doc_4.3.2-dev-1+20060414-1_all.deb to pool/main/z/zsh-beta/zsh-beta-doc_4.3.2-dev-1+20060414-1_all.deb zsh-beta_4.3.2-dev-1+20060414-1.diff.gz to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060414-1.diff.gz zsh-beta_4.3.2-dev-1+20060414-1.dsc to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060414-1.dsc zsh-beta_4.3.2-dev-1+20060414-1_sparc.deb to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060414-1_sparc.deb zsh-beta_4.3.2-dev-1+20060414.orig.tar.gz to pool/main/z/zsh-beta/zsh-beta_4.3.2-dev-1+20060414.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pgaccess 1:0.98.8.20030520-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Apr 2006 09:13:13 + Source: pgaccess Binary: pgaccess Architecture: source all Version: 1:0.98.8.20030520-4 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Raphael Hertzog [EMAIL PROTECTED] Description: pgaccess - Tk/Tcl interface to PostgreSQL Changes: pgaccess (1:0.98.8.20030520-4) unstable; urgency=low . * QA upload. * Integrate some more changes from Ubuntu made by Martin Pitt. Files: de5e7cd3088f23de55d2cf8bef536bc4 622 misc optional pgaccess_0.98.8.20030520-4.dsc 4428912b209284aa7f13b3105dcdc7a1 8864 misc optional pgaccess_0.98.8.20030520-4.diff.gz a9234a618a1c6b7ac6af9ea107bff859 968928 misc optional pgaccess_0.98.8.20030520-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQLlrvPbGD26BadIRApypAJ9F7Ii/c064VsQ8rZPtiIWUzMcQVQCePLNp geLBfoa44ijuKFbQWiTPoeY= =YQcJ -END PGP SIGNATURE- Accepted: pgaccess_0.98.8.20030520-4.diff.gz to pool/main/p/pgaccess/pgaccess_0.98.8.20030520-4.diff.gz pgaccess_0.98.8.20030520-4.dsc to pool/main/p/pgaccess/pgaccess_0.98.8.20030520-4.dsc pgaccess_0.98.8.20030520-4_all.deb to pool/main/p/pgaccess/pgaccess_0.98.8.20030520-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted pyroman 0.2-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 15:42:20 +0200 Source: pyroman Binary: pyroman Architecture: source all Version: 0.2-4 Distribution: unstable Urgency: low Maintainer: Erich Schubert [EMAIL PROTECTED] Changed-By: Erich Schubert [EMAIL PROTECTED] Description: pyroman- Firewall configuration tool for complex networks Closes: 358402 Changes: pyroman (0.2-4) unstable; urgency=low . * Add build-dependency on python (Closes: #358402) Files: 81b7fd3e29039591b4bae1435a1074bb 560 admin optional pyroman_0.2-4.dsc fa709b9a5f5891f82ab212e8f90dd6d1 4536 admin optional pyroman_0.2-4.diff.gz 3d42f7d39ce092a2ee5ac3c3400420ae 23756 admin optional pyroman_0.2-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQkoYntB470s6E1wRArHDAJoD9nxY1eSZIC9FiVkmC4ERFs+oKgCeIwoy UU57L56HIE3592mIZ3Z9Ox8= =xHcu -END PGP SIGNATURE- Accepted: pyroman_0.2-4.diff.gz to pool/main/p/pyroman/pyroman_0.2-4.diff.gz pyroman_0.2-4.dsc to pool/main/p/pyroman/pyroman_0.2-4.dsc pyroman_0.2-4_all.deb to pool/main/p/pyroman/pyroman_0.2-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted runit 1.5.0-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 12:40:11 + Source: runit Binary: runit Architecture: source i386 Version: 1.5.0-1 Distribution: unstable Urgency: low Maintainer: Gerrit Pape [EMAIL PROTECTED] Changed-By: Gerrit Pape [EMAIL PROTECTED] Description: runit - a UNIX init scheme with service supervision Closes: 356339 Changes: runit (1.5.0-1) unstable; urgency=low . * new upstream version. * adds configuration option p (prefix) to svlogd (closes: #356339). * debian/implicit: update to revision 1.11. * debian/control: Recommends: fgetty; Suggests: socklog-run. Files: 160c4172da70c960da5e2ebadbdb1515 626 admin optional runit_1.5.0-1.dsc 3b71109513839aac8702c27906f35a11 103483 admin optional runit_1.5.0.orig.tar.gz 9d76ac2a6c07eabc611db6e8f758095f 8483 admin optional runit_1.5.0-1.diff.gz 782ea855e36ef55b20f3b7ef548bd0cf 100946 admin optional runit_1.5.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQktCGJoyQbxwpv8RAjknAJ4sf4OeQ7MyqGqhn6seMH+N669mYwCgorgB hfV3yxSjziJmt+pYrldhFBI= =J+Kh -END PGP SIGNATURE- Accepted: runit_1.5.0-1.diff.gz to pool/main/r/runit/runit_1.5.0-1.diff.gz runit_1.5.0-1.dsc to pool/main/r/runit/runit_1.5.0-1.dsc runit_1.5.0-1_i386.deb to pool/main/r/runit/runit_1.5.0-1_i386.deb runit_1.5.0.orig.tar.gz to pool/main/r/runit/runit_1.5.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dash 0.5.3-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 13:09:08 + Source: dash Binary: dash-udeb ash dash Architecture: all source Version: 0.5.3-3 Distribution: unstable Urgency: low Maintainer: Gerrit Pape [EMAIL PROTECTED] Changed-By: Gerrit Pape [EMAIL PROTECTED] Description: ash- Compatibility package for the Debian Almquist Shell dash - The Debian Almquist Shell dash-udeb - The Debian Almquist Shell for boot floppies (udeb) Closes: 349855 355011 355124 355132 Changes: dash (0.5.3-3) unstable; urgency=low . * debian/rules: target configure, configure-udeb: add --host option to configure (adds the ability to cross-compile, patch from Pjotr Kourzanov; closes: #355132, #355124). * debian/po/it.po: new: initial Italian debconf translation (thx Andrea Bolognani; closes: #355011). * debian/diff/dash-signed-char-syntax.diff: new: patch from upstream: don't remove special chars on expansion (closes: 349855). * debian/implicit: update to revision 1.11. Files: 6feeb8bd980a9757b3fb93a909791cfa 639 shells optional dash_0.5.3-3.dsc d90f816432ab5055f37abf0441018bf6 26636 shells optional dash_0.5.3-3.diff.gz b8158d5b94d9bfb51745f43d778b9b8a 16754 shells optional ash_0.5.3-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQkuEGJoyQbxwpv8RApJsAJ4+HkLGVkEKr2bz1+zTEiMEPYqVTACeJQR5 uiWM8xdj735GWcMBPO0dkrc= =iPpl -END PGP SIGNATURE- Accepted: ash_0.5.3-3_all.deb to pool/main/d/dash/ash_0.5.3-3_all.deb dash_0.5.3-3.diff.gz to pool/main/d/dash/dash_0.5.3-3.diff.gz dash_0.5.3-3.dsc to pool/main/d/dash/dash_0.5.3-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mailfront 0.98-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 13:31:57 + Source: mailfront Binary: mailfront Architecture: source i386 Version: 0.98-2 Distribution: unstable Urgency: low Maintainer: Gerrit Pape [EMAIL PROTECTED] Changed-By: Gerrit Pape [EMAIL PROTECTED] Description: mailfront - mail server network protocol front-ends Closes: 361557 Changes: mailfront (0.98-2) unstable; urgency=low . * debian/diff/tests-find-sort.diff: new: sort output from find (closes: #361557). Files: 13a75b3ae41984b1025bd0b4418858e9 614 mail extra mailfront_0.98-2.dsc d0ed132a12b3f6b677d2d02ff7cab638 7813 mail extra mailfront_0.98-2.diff.gz 5840018e0059f53683ac40c1ada1e67b 186426 mail extra mailfront_0.98-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQksOGJoyQbxwpv8RAoabAJ9SVGCMiA553tcsVaCQ55w+BlaWHACaAypN I7hqRv1hrdCDYz5N89fuX1I= =xyxQ -END PGP SIGNATURE- Accepted: mailfront_0.98-2.diff.gz to pool/main/m/mailfront/mailfront_0.98-2.diff.gz mailfront_0.98-2.dsc to pool/main/m/mailfront/mailfront_0.98-2.dsc mailfront_0.98-2_i386.deb to pool/main/m/mailfront/mailfront_0.98-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ipython 0.7.1.fix1-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 15:53:43 +0200 Source: ipython Binary: python2.3-ipython ipython-common ipython python2.4-ipython Architecture: source all Version: 0.7.1.fix1-2 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team [EMAIL PROTECTED] Changed-By: Norbert Tretkowski [EMAIL PROTECTED] Description: ipython- enhanced interactive Python shell [dummy package] ipython-common - enhanced interactive Python shell [common files] python2.3-ipython - enhanced interactive Python shell [built for python 2.3] python2.4-ipython - enhanced interactive Python shell [built for python 2.4] Changes: ipython (0.7.1.fix1-2) unstable; urgency=low . * Set maintainer to Debian Python modules team and added myself to uploaders. Files: 648df73b1bbd157ce385db83783aea6e 783 python optional ipython_0.7.1.fix1-2.dsc efa3f54a38a0fb000e785c76292dfdc9 8480 python optional ipython_0.7.1.fix1-2.diff.gz 1ae5091139f4483c1f423d1e1ac9193c 1098 python optional ipython_0.7.1.fix1-2_all.deb 68a21ca166a91d54bf01dd110cdbbc07 716200 python optional ipython-common_0.7.1.fix1-2_all.deb 7237b2ac9dead5ccc9a122f9acfa3a06 232444 python optional python2.3-ipython_0.7.1.fix1-2_all.deb 713b05541ba6e2da71631f50e1225fe0 232430 python optional python2.4-ipython_0.7.1.fix1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQlIyr/RnCw96jQERAt4cAKCo0HIs5stFajUdu2YLshKiVhSoUgCfapWV +56RJDM2UoBpPx33Ool1YHc= =LrP7 -END PGP SIGNATURE- Accepted: ipython-common_0.7.1.fix1-2_all.deb to pool/main/i/ipython/ipython-common_0.7.1.fix1-2_all.deb ipython_0.7.1.fix1-2.diff.gz to pool/main/i/ipython/ipython_0.7.1.fix1-2.diff.gz ipython_0.7.1.fix1-2.dsc to pool/main/i/ipython/ipython_0.7.1.fix1-2.dsc ipython_0.7.1.fix1-2_all.deb to pool/main/i/ipython/ipython_0.7.1.fix1-2_all.deb python2.3-ipython_0.7.1.fix1-2_all.deb to pool/main/i/ipython/python2.3-ipython_0.7.1.fix1-2_all.deb python2.4-ipython_0.7.1.fix1-2_all.deb to pool/main/i/ipython/python2.4-ipython_0.7.1.fix1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tcsh 6.14.00-4 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 16:26:00 +0200 Source: tcsh Binary: tcsh-kanji tcsh Architecture: source i386 all Version: 6.14.00-4 Distribution: experimental Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: tcsh - TENEX C Shell, an enhanced version of Berkeley csh tcsh-kanji - TENEX C Shell, transitional package Changes: tcsh (6.14.00-4) experimental; urgency=low . * Obsoleted tcsh-kanji package. tcsh-kanji users will upgrade to tcsh automatically. The tcsh package now includes kanji support. Files: 0bc0089570bf9addcc063cc21000b98d 630 shells standard tcsh_6.14.00-4.dsc 33f68041dd85333918a71ac994743a80 21708 shells standard tcsh_6.14.00-4.diff.gz 625a9d9dbb85d16d3e8658eb08b34d92 486228 shells standard tcsh_6.14.00-4_i386.deb 3a10fc0f7ac98b7f8170bc307b56783e 676 shells extra tcsh-kanji_6.14.00-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQlWehOZKoAn8AVwRAtswAKCQZ9qaQZyrYpB6IqOBmVI27K/pCQCfffIb dxZzY/a4v4kg2m7Mk2Fc7ig= =JvCp -END PGP SIGNATURE- Accepted: tcsh-kanji_6.14.00-4_all.deb to pool/main/t/tcsh/tcsh-kanji_6.14.00-4_all.deb tcsh_6.14.00-4.diff.gz to pool/main/t/tcsh/tcsh_6.14.00-4.diff.gz tcsh_6.14.00-4.dsc to pool/main/t/tcsh/tcsh_6.14.00-4.dsc tcsh_6.14.00-4_i386.deb to pool/main/t/tcsh/tcsh_6.14.00-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted manpages-ja 0.5.0.0.20060415-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 16 Apr 2006 12:50:47 +0900 Source: manpages-ja Binary: manpages-ja manpages-ja-dev Architecture: source all Version: 0.5.0.0.20060415-1 Distribution: unstable Urgency: low Maintainer: Keita Maehara [EMAIL PROTECTED] Changed-By: Keita Maehara [EMAIL PROTECTED] Description: manpages-ja - Japanese version of the manual pages (for users) manpages-ja-dev - Japanese version of the manual pages (for developers) Changes: manpages-ja (0.5.0.0.20060415-1) unstable; urgency=low . * New upstream release. Files: ef2f18df810deabab2d8fa0642793c94 636 doc optional manpages-ja_0.5.0.0.20060415-1.dsc 075683602893d553b290573bf21356f4 3303162 doc optional manpages-ja_0.5.0.0.20060415.orig.tar.gz 3c4833730f7274042fbde0fbf809d573 79084 doc optional manpages-ja_0.5.0.0.20060415-1.diff.gz 89289a3d7e5ac172fcb4a5512057052e 2969070 doc optional manpages-ja_0.5.0.0.20060415-1_all.deb 4975a4991b71d675239d6b9f2a4f1895 1495252 doc optional manpages-ja-dev_0.5.0.0.20060415-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEQl5GJxItQqZ0o1kRAmd8AKCWh9e2jCgErhgywdVhb9uOtJMTHwCdHv6I T0/QL4lzlG27e91gyGHwrpk= =A8Ei -END PGP SIGNATURE- Accepted: manpages-ja-dev_0.5.0.0.20060415-1_all.deb to pool/main/m/manpages-ja/manpages-ja-dev_0.5.0.0.20060415-1_all.deb manpages-ja_0.5.0.0.20060415-1.diff.gz to pool/main/m/manpages-ja/manpages-ja_0.5.0.0.20060415-1.diff.gz manpages-ja_0.5.0.0.20060415-1.dsc to pool/main/m/manpages-ja/manpages-ja_0.5.0.0.20060415-1.dsc manpages-ja_0.5.0.0.20060415-1_all.deb to pool/main/m/manpages-ja/manpages-ja_0.5.0.0.20060415-1_all.deb manpages-ja_0.5.0.0.20060415.orig.tar.gz to pool/main/m/manpages-ja/manpages-ja_0.5.0.0.20060415.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
