Preparation of the next stable Debian GNU/Linux update (III)
Preparation of the next stable Debian GNU/Linux update == An up-to-date version is at http://people.debian.org/~joey/3.0r6/. I am preparing the (most probably) last revision ever of the current stable Debian distribution (woody) and will frequently send reports so people can actually comment on it and intervene whenever this is required. It is scheduled for any time now. If you disagree with one bit or another, please reply to this mail and explain why these things should be handled differently. There is still time to reconsider. The plan is to release a new revision roughly two months after the last update. It is required, however, that this happens before the release of sarge since the Debian archive infrastructure is unable to update the then called oldstable distribution. Hence, this update is planned for the end of May, right before the proposed release of sarge. An ftpmaster still has to give the final approval for each package since ftpmasters are responsible for the archive. However, I'm trying to make their work as easy as possible in the hope to get the next revision out properly and without too much hassle. The regulations for updates to the stable Debian release are quite conservative. The requirements for packages to get updated in stable are: 1. The package fixes a security problem. An advisory by our own Security Team is required. Updates need to be approved by the Security Team. 2. The package fixes a critical bug which can lead into data loss, data corruption, or an overly broken system, or the package is broken or not usable (anymore). 3. The stable version of the package is not installable at all due to broken or unmet dependencies or broken installation scripts. 4. All released architectures have to be in sync. 5. The package gets all released architectures back in sync. It is (or (and (or 1 2 3) 4) 5) Regular bugs and upgrade problems don't get fixed in new revisions for the stable distribution. They should instead be documented in the Release Notes which are maintained by Rob Bradford mailto:[EMAIL PROTECTED] and are found at http://www.debian.org/releases/woody/releasenotes. Packages, which will most probably be rejected: . Packages that fix non-critical bugs. . Misplaced uploads, i.e. packages that were uploaded to 'stable unstable' or `frozen unstable' or similar. . Packages for which its binary packages are out of sync with regard to all supported architectures in the stable distribution. . Binary packages for which the source got lost somehow. . Packages that fix an unusable minor part of a package. If you would like to get a package updated in the stable release, you are advised to talk to the stable release manager first (see http://www.debian.org/intro/organization). Changelog - 2005/05/20 06:07 MET * Accepted doc-base * Accepted phpsysinfo * Accepted ppxp * Rejected ssmtp Accepted Packages - These packages will be installed into the stable Debian distribution and will be part of the next revision. cvs stable1.11.1p1debian-9woody7 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source cvs updates 1.11.1p1debian-10 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source DSA 715 cvs - several vulnerabilities doc-basestable0.7.11 all source doc-baseupdates 0.7.11-0.woody1 all source Important backport to support the woody - sarge upgrade ethereal-common stable0.9.4-1woody11 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc ethereal-common updates 0.9.4-1woody12 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc ethereal-dev stable0.9.4-1woody11 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc ethereal-dev updates 0.9.4-1woody12 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc ethereal stable0.9.4-1woody11 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source ethereal updates 0.9.4-1woody12 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source tetherealstable0.9.4-1woody11 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc tetherealupdates 0.9.4-1woody12 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc DSA 718 ethereal - buffer overflow f2c stable20010821-3.1 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source f2c updates 20010821-3.2 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc source Fix bug in DSA-661 gaim-common stable1:0.58-2.4 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc gaim-common updates 1:0.58-2.5 alpha arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc gaim-gnome stable1:0.58-2.4 alpha arm hppa i386 ia64 m68k mips mipsel
spam envoyé par sober.q
On Thu, May 19, 2005 at 02:05:01PM +0200, Martin Quinson wrote: Il y a fort à parier que vous n'y etes pas. Le message auquel vous répondez est un spam d'un groupe néo-nazi allemand qui s'amuse depuis une semaine ou deux à usurper l'adresse de cette liste pour envoyer les pires horreurs comme les camps ont été libérés il y a 60 ans, mais qui cela interresse-t-il?. Aargh. Je ne vois pas bien comment faire arreter ce flot d'ignominie, mais si quelqu'un voit, je suis pour : j'en reçois plusieurs centaines par jour... On trouve la liste des sujets de ces mails sur le net assez facilement[1], et chez moi, procmail fait le reste. Reste à traiter le problème des MTA qui me renvoient les mails qui ont mon adresse dans le champ From: mais pour le moment spambayes fait du bon boulot. [1] par exemple sur http://www.sophos.com/virusinfo/analyses/trojsoberq.html dans l'onglet description. -- Alexandre Fayolle LOGILAB, Paris (France). http://www.logilab.com http://www.logilab.fr http://www.logilab.org signature.asc Description: Digital signature
Re: Paranoider Deutschenmoerder kommt in Psychiatrie
From: Martin Quinson [EMAIL PROTECTED] To: debian-devel-french@lists.debian.org,Sophie Luc Briand [EMAIL PROTECTED] Subject: Re: Paranoider Deutschenmoerder kommt in Psychiatrie Date: Thu, 19 May 2005 14:05:01 +0200 Il y a fort à parier que vous n'y etes pas. Le message auquel vous répondez est un spam d'un groupe néo-nazi allemand qui s'amuse depuis une semaine ou deux à usurper l'adresse de cette liste pour envoyer les pires horreurs comme les camps ont été libérés il y a 60 ans, mais qui cela interresse-t-il?. Aargh. Je ne vois pas bien comment faire arreter ce flot d'ignominie, mais si quelqu'un voit, je suis pour : j'en reçois plusieurs centaines par jour... Personnellement, je n'ai jamais reçu les mails que tu décris. Je n'ai pas de soucis avec CET mailing list. Pour ne pas recevoir les mails, à part un filtre anti-spam je ne vois pas. Pour empecher l'usurpation de l'adresse debian-devel-french, c'est impossible. En revenche le groupe qui usurpe cette adresse s'est probablement compromis. http://europa.eu.int/ISPO/legal/fr/internet/wpfr.html (paragraphe 4.4), Ceux qui reçoivent ces mails peuvent/doivent le signaler à leur FAI ( ou admin système si c'est à votre travail ). mcoolive. _ MSN Messenger : personnalisez votre messagerie instantanée ! http://g.msn.fr/FR1001/866 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
Yes, I'm aware that if it's possible to revoke the GPL, it fails the Tentacles of Evil test, and GPL software would be completely unsuitable for any serious deployment. [Roberto C. Sanchez] But it can't be done, period. Reference: http://www.gnu.org/philosophy/free-sw.html That I am not legally trained does not make me completely unschooled in these things. Believe it or not, I actually did already know the FSF's position on the revocability of the GPL. That is why I opened my message with a sentence you helpfully did not quote: It seems to me that this is another of those things everyone takes for a postulate just because the FSF said so. I'm much more interested in arguments that do not start with well, the FSF says... or this is ridiculous, everyone knows that... or even for 12 years we've all assumed It seems to me that the FSF position on the irrevocability of free software depends on the interesting dual notions that the license is not a contract, but nonetheless the copyright holder is bound by it. Michael Edwards disputes the former notion; this seems to be a productive line of reasoning. signature.asc Description: Digital signature
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
Peter Samuelson wrote: Yes, I'm aware that if it's possible to revoke the GPL, it fails the Tentacles of Evil test, and GPL software would be completely unsuitable for any serious deployment. [Roberto C. Sanchez] But it can't be done, period. Reference: http://www.gnu.org/philosophy/free-sw.html That I am not legally trained does not make me completely unschooled in these things. Believe it or not, I actually did already know the FSF's position on the revocability of the GPL. That is why I opened my message with a sentence you helpfully did not quote: It seems to me that this is another of those things everyone takes for a postulate just because the FSF said so. I'm much more interested in arguments that do not start with well, the FSF says... or this is ridiculous, everyone knows that... or even for 12 years we've all assumed It seems to me that the FSF position on the irrevocability of free software depends on the interesting dual notions that the license is not a contract, but nonetheless the copyright holder is bound by it. Michael Edwards disputes the former notion; this seems to be a productive line of reasoning. Point taken. However, the GPL clearly states the conditions in section 6: 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. To me, that says Once the cat is out, it's out for good. So, if you as the author of GPL software, try to restrict someone that has already received your software under the terms of the GPL, then you violate the license. Since you are the author, it doesn't affect you so much, since you are also the copyright holder. The only other alternative is that the GPL is not enforceable. That would probably call into question the validity of all software licenses. However, I am not lawyer (I'm sure you guessed that by now), so I will refrain from speaking further on this subject. Incidentally, if there was so much controversy about this and the origins and rights to the code have been in question, why has SourceForge let the project continue for 2 years? I imagine that it is not their responsibility that to comb through every piece of code housed on their servers. However, I would imagine that it would be part of their due diligence to verify whether a project like this can even exist on their servers in the first place. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr signature.asc Description: OpenPGP digital signature
Hey man, stop throwing away your money
Hey man, stop throwing away your money http://www.prumie.net/ss/ Wanna be more man? Check this dude -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Inconsistent handling of sourceless packages in main
Hi, there are a number of packages in main that contain the actual source code for their binaries in the package itself. Instead those packages rely on other packages to supply source or prebuild binaries. The handling of those packages is inconsisten across the various packages and, every now and then, even violates the GPL (sources are missing). One package (debian-installer) gets away without source while another (ia32-libs) has to carry a huge bloat around for GPL compliance. The handling of them is incosistent and unsatisfactory. Namely I know about the following cases: (probably incomplete) package | handling -+-- kernel-image*| Build-Depends kernel-source* linux-kernel-di* | downloads kernel-image debs kernel-modules | Build-Depends on kernel-headers ia32-libs| include prebuild debs and source debian-installer | downloads udebs and uses installed binaries And all have problems: package | danger -+-- kernel-image*| kernel-source* update replaces source | rebuild differs | but old version is retrievable through included patches | linux-kernel-di* | kernel-source* update replaces source (see above), | kernel-image updates make rebuilds differ | kernel-modules | kernel-image* updates replaces source (arch patches) | rebuild differs | GPL VIOLATION | ia32-libs| huge bloat of the source. 215MB source, 12MB deb | debian-installer | source updates replace source, rebuilds differ | GPL VIOLATIONS IMHO debian-installer in unacceptable as it causes GPL violations. Interlocking the debian-installer builds with the exact source versions used during build is impractical at best and would stop many base debs from entering testing. The ia32-libs way is not practical as it causes way too much waste. Debian installer would have to grow beyond 500Mb (guess) and an OOo for ia64 beyond 300Mb for their source packages. The kernel-image* packages are the most practical ones since kernel-sources* takes care of preserving past sources. But the same can't be sanely used for ia32-libs or debian-installer. But what can be done about it? I thought about making wraper packages (for ia32-libs) that download (copy from cd) the respective i386 debs and mangle them on the fly. But that feels too hackish. Any ideas? Comments? Solutions? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC on mysql 4.1 in sarge
On Wednesday 18 of May 2005 17:23, sean finney wrote: - people often symlink the mysql datadir (/var/lib/mysql) and logdir (/var/log/mysql) to somewhere else, such as /usr/local - because these two directories are in the files.list of woody's mysql server, upgrading to packages in sarge leads to the symlinks being removed and replaced with empty directories. I think the most cleanest solution would be to use dpkg diversion for the directory. It is possible but the /var/lib/dpkg/diversions file have to be modified by hand. I've beed reported with similar problem about /var/www - /home/www symlink and the diversion was helpful. -- .''`.Piotr Roszatycki, Netia SA : :' :mailto:[EMAIL PROTECTED] `. `' mailto:[EMAIL PROTECTED] `- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Release Notes] Use Woody's or Sarge's aptitude for upgrades?
* Bernd Eckenfels ([EMAIL PROTECTED]) [050517 03:35]: In article [EMAIL PROTECTED] you wrote: 2. change the /etc/apt/sources.list to point to stable I wish all documentation is using the distribution names not the symbolic names. If you put stable in a file this will cause major trouble a few years later. Beside it is unclear to the reader when you have written the text and which stable you mean. (I think you mean sarge?) Fully agreed. Cheers, Andi -- http://home.arcor.de/andreas-barth/ PGP 1024/89FB5CE5 DC F1 85 6D A6 45 9C 0F 3B BE F1 D0 C5 D1 D9 0C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
On 20050519T153811+1000, Anthony Towns wrote: Adeodato Simó wrote: As you probably know, entries in the Packages file only have a Source field if the name of the source package is different from the name of the binary package being described. This is an inconsistency that makes it a bit harder to massage this data, e.g. with grep-dctrl. Why not add a patch to grep-dctrl instead? What patch would that be? Grep-dctrl is able to handle that, it just becomes a little messy (search in Source, and if there is no Source, search in Package). The most one could do for grep-dctrl would be to add a shorthand option for that; is it worth the trouble? Hmm, actually, it might make sense to add support for predicate abstractions. Hmm. -- Antti-Juhani Kaijanaho, Debian developer http://kaijanaho.info/antti-juhani/blog/en/debian signature.asc Description: Digital signature
Re: /usr/lib vs /usr/libexec
Josselin Mouette [EMAIL PROTECTED] writes: Le jeudi 12 mai 2005 à 18:32 -0700, Thomas Bushnell BSG a écrit : You said it: there is a cache. After the first access, the directory will be in the cache. Making all of this a purely imaginary problem. The whole directory is in the cache? I don't think so. Remember, that in between each lookup, a library gets searched, which probably flushes the entire cache. Currently, on my 256 MB machine, the kernel is using 60 MB for the cache. I think this is enough to include a few directory blocks, especially some as frequently used as /usr/lib. If it doesn't while loading an application then something is seriously wrong or you will be swapping. But the problem remains that you have to look at each dire entry in unhashed ext2/3, fat or minix. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC on mysql 4.1 in sarge
Hi Sean, On Wed, May 18, 2005 at 11:23:35AM -0400, sean finney wrote: the following upgrade paths work: mysql-server/woody - mysql-server/sarge mysql-server/woody - mysql-server/sarge - mysql-server-4.1/sarge but this does not: mysql-server/woody - mysql-server-4.1/sarge so at this point, we're not sure what to do to cover this last problem, as we have no guarantee the preinst of mysql-server-4.1 will even run before mysql-server/woody is removed. the only fix we can think of is to remove the two directories from the files.list of the woody package. so we've come up with three options, none of which are great: 1 the most recenty woody security update caused problems for some people, and there's a package already waiting to go in to fix this problem. we could put a fix into the woody mysql-server package into this package before the security team handles it. 2 if there's going to be a final woody point release, we could put a fixed version in there 3 give up on trying to fix it, assume that symlinks might get lost, and put something in a README file telling users what they have to do in order to fix up their database after restoring the symlinks. i don't see 1 happening, i don't know if the prerequisite (woody release update) for 2 is going to happen, and 3 doesn't make me all too happy as a solution. so, questions, comments, suggestions all welcome, I see the same three options. Joey has said he is working on a final woody point release for the last weekend in May; you'll probably need to coordinate with him and get something uploaded soon if you want to try for this option. 3 does not sound so bad to me; it's arguably user error anyway to replace a package-provided directory with a symlink in this manner, so having a corner case of partially upgraded woody system and installing mysql-server-4.1 and messed with a package directory is not the end of the world... Cheers, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Questions about waste licence and code.
Wesley J. Landaker [EMAIL PROTECTED] writes: On Friday 13 May 2005 06:30, Steinar H. Gunderson wrote: On Fri, May 13, 2005 at 02:20:02PM +0200, Romain Beauxis wrote: http://cvs.sourceforge.net/viewcvs.py/waste/waste/license.cpp?rev=1.1v iew=auto Has it ever occured to you that this might be the license text itself, in some compressed form? In fact, that is what it is supposed to be, but even if not, the data is never used during compilation or runtime. Deleting the file and removing references to it yields bit-for-bit binaries vs. an original compile. Still, the question for upstream is: why is this here? It's not actually used by the program. If it where used I would suggest replacing it with #include /usr/share/common-licenses/GPL (or a file inside the source) and patch to make it use plain text instead of crypted data. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: alioth mailing list moderation broken for extended period of time
Marc Haber [EMAIL PROTECTED] writes: On Sat, 14 May 2005 22:06:42 +0200, Martin Mewes [EMAIL PROTECTED] wrote: Marc Haber [EMAIL PROTECTED] wrote : So I need to ask here whether it would be a better idea to move mailing lists away from obviously broken, unmaintained and unsupported infrastructure like alioth currently is. If there is any $LIST-admin-position somewhat orphaned I would happily volunteer to take over the service if this helps. This problem is not one of a MIA list moderator. It is a technical issue. One of the $LIST values I know as clearly affected is pkg-exim4-users, and I currently serve as one of the targets for pkg-exim4-users-admin. At least, that's what the mailman frontend of alioth says, but [EMAIL PROTECTED] bounces nevertheless: pipe to |/var/lib/mailman/mail/wrapper admin pkg-exim4-users generated by [EMAIL PROTECTED], Illegal command: admin I firmly believe that this is a technical problem with the mailing list setup on alioth, and the corresponding alioth site admin tracker item 301440. This problem affects all alioth mailing lists that I am admin for, which includes the lists for pkg-exim4, pkg-torrus and adduser. Greetings Marc Did the move change anything? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
Anthony Towns aj@azure.humbug.org.au writes: Adeodato Simó wrote: As you probably know, entries in the Packages file only have a Source field if the name of the source package is different from the name of the binary package being described. This is an inconsistency that makes it a bit harder to massage this data, e.g. with grep-dctrl. Why not add a patch to grep-dctrl instead? Cheers, aj And have it insert Source: ... entries into debian/control files? grep-dctrl does not want to have special knowledge about the data content of what it greps but is ment to work on anything resembling RFC822 headers. So while it would be possible to teach grep-dctrl about Packages files and add Source: ... lines it is not desireable. There is also another reason for more Source: ... entries in the Packages file mentioned in an unrelated thread earlier and also a reason why grep-dctrl can't rebuild that entry: The detection of binary NMUs is currently, among others, using the debian version of a package and guessing from its form. What is a binary NMU and what not is not aparent from the Packages file. It has been suggested to insert Source: entries pointing to the original source of an binary NMU instead. Examples: Packages: Package: fftw-dev Architecture: m68k Source: fftw Version: 2.1.3-16.0.1 Package: libcnumx0 Architecture: m68k Source: numerix Version: 0.19-5.1.1 Sources: Package: fftw Binary: fftw2, fftw-dev, fftw-docs, sfftw-dev, sfftw2 Version: 2.1.3-16 Package: numerix Binary: libnumerix-ocaml-dev, libcnumx0-dev, numerix-doc, libnumerix-ocaml, libcnumx0 Version: 0.19-5.1.1 What should grep-dctrl do there? Guessing that -x.y.z is an binary NMU or not? Either way one of them will be wrong. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Questions about waste licence and code.
If it where used I would suggest replacing it with #include /usr/share/common-licenses/GPL (or a file inside the source) and patch to make it use plain text instead of crypted data. Yep in fact it was used as it said, by using the -L switch for both wastesrv and the admin command wastesrv_admin. I thought about doing so, but it seemed better to simply remove the -L switch for the following means: -- The licence is already shipped within the package, and simply for _debian package users_ it is obvious to check it. -- This way it is harmless with regards to the original code source: my patch is only putting parts of the code in comment. BTW the different patches are at debian/patches so you can have a look on it and tell me what you think of it.. Then, still it is unclear if the licence is really GPL or not.. I've not heard from the original author, nor managed to find a main copyright holder or an emai.. only I got the user ml.. Romain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
Antti-Juhani Kaijanaho wrote:
As you probably know, entries in the Packages file only have a Source
field if the name of the source package is different from the name of
the binary package being described.
Why not add a patch to grep-dctrl instead?
What patch would that be?
Something equivalent to:
cat /var/lib/dpkg/available |
awk '/^Package:/ {P=$2;V=}
/^Version:/ {if (V==) { V=$2; } }
/^Source: .* (.*)/ {V=substr($3,2,length($3)-2)}
/^Source:/ {P=$2}
/^$/ { print Source-Package:, P; print Source-Version:, V }
{print}'
I would've thought. (That adds Source-Package: and Source-Version:
fields to every stanza)
The idea being that grep-available --source-info [...] would work the
same as piping the above into | grep-ctrl [...].
Cheers,
aj
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
Goswin von Brederlow wrote: The detection of binary NMUs is currently, among others, using the debian version of a package and guessing from its form. What is a binary NMU and what not is not aparent from the Packages file. It has been suggested to insert Source: entries pointing to the original source of an binary NMU instead. Yes, by me. It's not related to this issue; the problem there is that dpkg thinks the source is 2.1.3-16.0.1. It will happily include a Source: line to that effect when it can't be inferred from the Version: field. Cheers, aj -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
On 20050519T205101+1000, Anthony Towns wrote:
Something equivalent to:
cat /var/lib/dpkg/available |
awk '/^Package:/ {P=$2;V=}
/^Version:/ {if (V==) { V=$2; } }
/^Source: .* (.*)/ {V=substr($3,2,length($3)-2)}
/^Source:/ {P=$2}
/^$/ { print Source-Package:, P; print Source-Version:, V }
{print}'
I would've thought. (That adds Source-Package: and Source-Version:
fields to every stanza)
The idea being that grep-available --source-info [...] would work the
same as piping the above into | grep-ctrl [...].
Any user can already put that in their ~/.grep-dctrlrc (well, a not
*literally* that, but instructions to that effect).
If someone wants it as a standard feature, feel free to wishlist-bug
grep-dctrl.
--
Antti-Juhani Kaijanaho, Debian developer
http://kaijanaho.info/antti-juhani/blog/en/debian
signature.asc
Description: Digital signature
Re: Entries in Packages files that lack a Source field
Anthony Towns aj@azure.humbug.org.au writes: Goswin von Brederlow wrote: The detection of binary NMUs is currently, among others, using the debian version of a package and guessing from its form. What is a binary NMU and what not is not aparent from the Packages file. It has been suggested to insert Source: entries pointing to the original source of an binary NMU instead. Yes, by me. It's not related to this issue; the problem there is that dpkg thinks the source is 2.1.3-16.0.1. It will happily include a Source: line to that effect when it can't be inferred from the Version: field. Cheers, aj Yes. But that misconception of dpkg makes it impossible to guess the Source: entry or alraedy gives a wrong Source entry. If it weren't for this then patching grep-dctrl or post-processing the output (like your awk script) would work. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /usr/lib vs /usr/libexec
On Thu, May 19, 2005 at 11:47:31AM +0200, Goswin von Brederlow wrote: [snip] But the problem remains that you have to look at each dire entry in unhashed ext2/3, fat or minix. Ehrm, I don't think having /usr/lib on a fat FS is an option anyway, considering its lacking file ownership/permission support and its filename munging... And I somehow doubt that minix is a problem either, these days. Regards: David Weinehall -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC on mysql 4.1 in sarge
Hello On 2005-05-19 Steve Langasek wrote: ... so we've come up with three options, none of which are great: 1 the most recenty woody security update caused problems for some people, and there's a package already waiting to go in to fix this problem. we could put a fix into the woody mysql-server package into this package before the security team handles it. 2 if there's going to be a final woody point release, we could put a fixed version in there 3 give up on trying to fix it, assume that symlinks might get lost, and put something in a README file telling users what they have to do in order to fix up their database after restoring the symlinks. ... I see the same three options. Joey has said he is working on a final woody point release for the last weekend in May; you'll probably need to coordinate with him and get something uploaded soon if you want to try for this option. 3 does not sound so bad to me; it's arguably user error anyway to replace a package-provided directory with a symlink in this manner, so having a corner case of partially upgraded woody system and installing mysql-server-4.1 and messed with a package directory is not the end of the world... I guess you missed my response to this thread so I here the relevant parts: As a direct upgrade from mysql-server (3.23) to mysql-server-4.1 without a prior upgrade to mysql-server (4.0) is quite unlikely, I would like to see our last upload, which in addition has some notes in README.Debian and the Debconf installation notes regarding this, to be accepted for Sarge. Relevant versions are 4.1.11a-2 and 4.0.24-10. [new: 2nd issue - statically linked db3] The new bug #308966 complains that mysql-server and libnss-db produce segfault crashes as mysql-server until now still had the obsolete BDB (aka BerkeleyDB) engine enabled which uses a statically linked local db3 version. Thus BDB support could now complete been removed as luckily support for BDB was not present on most architectures, disabled by default and being warned at startup for a while now and will most likely be removed in 5.0 upstream anyway. Or we could try a patch that Piotr Roszatycki is currently evaluating which would add versioned symbols to the bdb functions in MySQL. He already suspected though, that the patch would not be a oneliner.. So do you want 1. just stay with 4.1.11a-2 and the bug 2. an upload without BDB support as 4.1.11a-3 3. wait to decide upon the forthcoming versioned symbols patch later bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some packages up for adoption
* Martin Michlmayr [EMAIL PROTECTED] [2005-05-04 22:29]: Brent Fulgham has decided to give some packages away (mostly Erlang and Dylan related packages but also some others); the following mail is forwarded with permission from debian-private: anyone interested? 2. Erlang -- Concurrent programming language 3. erlang-doc-html -- HTML documentation for Erlang. 4. erlang-manpages -- Manpages for Erlang. 5. wings3d -- Awesome 3-D modelling software (written in Erlang) 6. libsdl-erlang -- SDL binding for Erlang. 7. gwydion-dylan -- Dynamic Language 8. gwydion-dylan-sgml -- SGML documentation package for Dylang. 9. libopengl-dylan -- OpenGL binding for Dylan. 10. libpng-dylan -- PNG binding for Dylan. In addition, the following GNUstep packages should be handled by the GNUstep packaing team: I sent a message to [EMAIL PROTECTED] about these. gnustep-antlr gnustep-dl2 gnustep-gd gnustep-netclasses pdfkit.framework renaissance steptalk -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upcoming removals
* Igor Stroh [EMAIL PROTECTED] [2005-05-06 22:10]: From what I can tell, cantus3 doesn't actually provide all of the functionality originally present in cantus. And it won't either -- the upstream is unresponsive and seems to have no interest neither in incorporating bug fixes nor in adding features which the package formerly claimed to be offering[0]. I'd suggest to remove cantus3 from the archive if it wouldn't have so many users (according to popcon.d.o) - there are better Has there been any agreement about what to do with cantus and cantus3? Since you're the maintainer of cantus3 and you suggest it's removal, can you go ahead and file a bug report on ftp.d.o? Should cantus be removed too? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upcoming removals
* Martin Michlmayr [EMAIL PROTECTED] [2005-05-03 14:54]: I intend to ask for removal of the following packages in the next few days unless someone is willing to step up as maintainer. All of these packages have been orphaned for over 60 days and have never been part of a stable release; none of them have any reverse (build-)dependencies. ... I will now ask for removal of these packages, with the exception of: - cantus/cantus3: situation unclear; waiting for maintainer of cantus3 to decide - bbconf: will be adopted - langband/langband-data: will be adopted - audio-cd: someone has indicated interest in this -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /usr/lib vs /usr/libexec
[David Weinehall] Ehrm, I don't think having /usr/lib on a fat FS is an option anyway, considering its lacking file ownership/permission support and its filename munging... I should think the lack of symlink support is the real problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Some packages up for adoption
On Thursday 19 May 2005 13:24, Martin Michlmayr wrote: anyone interested? 2. Erlang -- Concurrent programming language 3. erlang-doc-html -- HTML documentation for Erlang. 4. erlang-manpages -- Manpages for Erlang. These are taken by François-Denis Gonthier. 5. wings3d -- Awesome 3-D modelling software (written in Erlang) 6. libsdl-erlang -- SDL binding for Erlang. I will take these if no-one else is interested.
Re: Bug#309241: ITP: dguitar -- Guitar Pro 3/4 tabs viewer and player
Hello Tue, 17 May 2005 13:11:51 -0700 David Schleef [EMAIL PROTECTED] wrote: It does not appear to be available under a DFSG-compatible license. ;) Even though the Song That Shall Not Be Named seems ancient, it's really only about 50 years old and still under copyright. Tabs are not included in debian package. I will send mail to upstream autor to exclude tabs from official release. Regards, Verdan -- [ ,''`. [EMAIL PROTECTED] // [EMAIL PROTECTED] ] [ : :' : GG: 830398 // JID: verdan(at)chrome.pl ] [ `. `' [EMAIL PROTECTED] //GPG: 0xDF32F531 ] [ `- 1A6F A0A1 01D1 3033 332A 60FE 4C7B 8037 DF32 F531 ] pgp802nL1S2fg.pgp Description: PGP signature
Hi cutey. Its me jjIt's J GirlIts JJbaste
Hi there sweety. This is Hottie July, from the online personlals place. I have been checking out all about you and I just wanted to say hi! I want you to look at my pics and read about me at my website. I can't wait to talk to you baby. Cya soon, J-girl www.zgeqij.ucanttouchfist.com/ju29/ __ Jimmie collinear aida oblige adolph. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309782: ITP: keurocalc -- universal currency converter and calculator
Package: wnpp Severity: wishlist Owner: Moratti Claudio [EMAIL PROTECTED] * Package name: keurocalc Version : 0.9.1 Upstream Author : Éric Bischoff [EMAIL PROTECTED] Melchior Franz [EMAIL PROTECTED] Bas Willems [EMAIL PROTECTED] * URL : http://opensource.bureau-cornavin.com/keurocalc/ * License : GPL Description : universal currency converter and calculator KEurocalc is a universal currency converter and calculator. It downloads latest exchange rates directly from the European Central Bank and the Federal Reserve Bank of New York. I have made packages that works, whithout any error (from lintian check) I'm looking for a sponsor to check them. Package and Sources are available here: http://spirit.knio.it/~maxer/deb/ Best regards Claudio -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-maxer Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC on mysql 4.1 in sarge
On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote: 3 does not sound so bad to me; it's arguably user error anyway to replace a package-provided directory with a symlink in this manner If you consider this an user error, then what is the officially blessed way of relocating a package-prodived directory to a different (already mounted) file system? Gabor -- - MTA SZTAKI Computer and Automation Research Institute Hungarian Academy of Sciences - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC on mysql 4.1 in sarge
On Thu, May 19, 2005 at 05:08:28PM +0200, GOMBAS Gabor wrote: On Thu, May 19, 2005 at 02:49:13AM -0700, Steve Langasek wrote: 3 does not sound so bad to me; it's arguably user error anyway to replace a package-provided directory with a symlink in this manner If you consider this an user error, then what is the officially blessed way of relocating a package-prodived directory to a different (already mounted) file system? currently, that would be bind mounts. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Entries in Packages files that lack a Source field
* Anthony Towns [Thu, 19 May 2005 15:38:11 +1000]: Adeodato Simó wrote: As you probably know, entries in the Packages file only have a Source field if the name of the source package is different from the name of the binary package being described. This is an inconsistency that makes it a bit harder to massage this data, e.g. with grep-dctrl. Why not add a patch to grep-dctrl instead? grep-dctrl was only meant an example: every script or whatever parsing Packages files will have to deal with that inconsistency (in the case of a Perl or similar script, it's less cumbersome that with grep-dctrl, that's true). Fixing apt-ftparchive solves the issue for everybody, hence what I was looking to know is if there is a reason for which the current behavior of apt-ftparchive should not be changed. Cheers, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Don't be irreplaceable, if you can't be replaced, you can't be promoted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes to the weekly WNPP posting
Re: Martin Michlmayr in [EMAIL PROTECTED] I have therefore decided to stop the weekly WNPP summaries to d-d-a and instead do the following: - send the weekly posting to debian-wnpp instead of d-d-a - only include new entries I always read the announcements to look for O or RFAs of packages I use, hence I appreciate the only new entries change. However, from browsing the debian-wnpp archives, there's a lot more stuff there than I'm willing to read, so not posting the announcements on a different list is a regression for me. (Ok, I could procmail it away, but that's a hack.) How about posting the announcements to -devel (instead of -d-a)? If only new entries are included, it wouldn't hurt much for those who are not interested. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Changes to the weekly WNPP posting
* Christoph Berg [EMAIL PROTECTED] [2005-05-19 18:40]: How about posting the announcements to -devel (instead of -d-a)? If only new entries are included, it wouldn't hurt much for those who are not interested. I agree that this might be a good idea. debian-wnpp is quite cluttered with all the control messages from the BTS. What do other people think of this? Do you want a shorter WNPP posting with only new entries on -devel? -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes to the weekly WNPP posting
On Thu, 2005-05-19 at 18:40 +0200, Christoph Berg wrote: I always read the announcements to look for O or RFAs of packages I use, hence I appreciate the only new entries change. Same here. However, from browsing the debian-wnpp archives, there's a lot more stuff there than I'm willing to read, so not posting the announcements on a different list is a regression for me. (Ok, I could procmail it away, but that's a hack.) I'd consider it a regression as well, for the same reason. How about posting the announcements to -devel (instead of -d-a)? If only new entries are included, it wouldn't hurt much for those who are not interested. I'd like to see them continue on -d-a. There are times when I just can't handle -devel and unsub completely. They really don't add up to much traffic, and the new entries only change should help bring back some people to doing regular reviews that they had developed a resistance to doing due to having to wade through too many old entries to see the new ones. Ben signature.asc Description: This is a digitally signed message part
Re: Entries in Packages files that lack a Source field
On Thu, May 19, 2005 at 12:18:55PM +0200, Goswin von Brederlow wrote: The detection of binary NMUs is currently, among others, using the debian version of a package and guessing from its form. What is a binary NMU and what not is not aparent from the Packages file. It has been suggested to insert Source: entries pointing to the original source of an binary NMU instead. That should probably happen regardless, and is because dpkg doesn't have the proper support for it. It's independent of whether to add Source: lines when unneeded in any other case. If you bin-NMU, you *are* building from a source called -N.0.1, because you changed the changelog. dpkg-dev could have some means to build with different version number from the same source package, or any other (probably a bit hacky) way to achieve this. That there's special code in dak to cope with this issue somewhat heuristically is a sign of that the bin-NMU issue is deeper. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
unsubscribe
Ignasi. __ Do you Yahoo!? Make Yahoo! your home page http://www.yahoo.com/r/hs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Release Notes] Use Woody's or Sarge's aptitude for upgrades?
On Wednesday 18 May 2005 02:47, Steve Langasek wrote: Is there a difference in packages removed if you run aptitude install aptitude instead of aptitude install aptitude dpkg? I don't see any reason why dpkg needs to be upgraded first, unlike aptitude. No, makes no real difference. I still need perl to keep my system at least somewhat alive. If perl needs to be added to the list, I say to just add it. People who have Prio: standard packages missing from their systems probably won't want to follow our advise to use aptitude, either. perl was not missing on my system. It just needed to be upgraded along with aptitude because of dependencies (no idea which). That upgrade had to be forced by adding it in the install command. Otherwise perl would be removed, taking half my system with it. I think we will be getting two kinds of upgrade: - servers or light desktops that can get by with just upgrading aptitude - desktops with kde, gnome (from unofficial backports or not) that will have to look at the results of 'aptitude install aptitude' and decide if anything else is needed; perl probably is a prime candidate I going to try to rewrite/reorganize chapter 4 of the release notes somewhat on Saturday to see if I can make the upgrade instructions a bit more organic. pgpLCBeArcofP.pgp Description: PGP signature
Re: RFC on mysql 4.1 in sarge
Hello [1st RC issue - dpkg removes symlinks when upgrading from 3.23] As discussed before in some corner cases we can do nothing except for showing the user an explanation what happened which has been done in 4.1.11a-2 and 4.0.24-10. [2nd RC issue - statically linked db3] The new bug #308966 complains that mysql-server and libnss-db produce segfault crashes as mysql-server-4.1 until now still had the obsolete BDB (aka BerkeleyDB) engine enabled which uses a statically linked local db3 version. This affects only mysql-server-4.1, not the 4.0 branch. Option 3 changed: 1. just stay with 4.1.11a-2 and the bug 2. an upload without BDB support as 4.1.11a-3 3. an upload with Piotr Roszatyckis 8 line patch that mainly only adds --with-uniquename=_mysql to the configure options and runs sed over one header file (the actual diff is ~50 lines because the patch is been saved as dpatch file like all other patches, too) I verified that the patched package - runs in those cases where the old segfaultet - contains the unique-fied symbols only in /usr/sbin/mysqld and not in the libraries which would be problematic - succeeds the mysql benchmark and some basic tests I did The patch itself can be reviewed at http://www.lathspell.de/linux/debian/mysql/mysql-dfsg-4.1-4.1.11a.debian.diff So I'm in favour of 3. but could live with the other choices, too. Steve? bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes to the weekly WNPP posting
Hi, On Thursday 19 May 2005 18:43, Martin Michlmayr wrote: What do other people think of this? Do you want a shorter WNPP posting with only new entries on -devel? less frequent, maybe every four weeks ? i've got wnpp-alert in my cron for weekly mails - if people reaaally care, they can put into daily cron, otherwise every four weeks is IMO not really annonying - on d-d-a. maybe even every six to eight weeks... with a pointer to wnpp-alert it should be sufficient. regards, Holger pgpq2w2iZxsk1.pgp Description: PGP signature
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/18/05, Roberto C. Sanchez [EMAIL PROTECTED] wrote: Point taken. However, the GPL clearly states the conditions in section 6: 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. To me, that says Once the cat is out, it's out for good. So, if you as the author of GPL software, try to restrict someone that has already received your software under the terms of the GPL, then you violate the license. Since you are the author, it doesn't affect you so much, since you are also the copyright holder. And what, exactly, is the licensee's recourse if the licensor violates the license in this way? Are you mistaking the GPL for a statute? The law about whether a license without an explicit term can be revoked at will varies from one contract law jurisdiction to another. See Walthal v. Corey Rusk at http://caselaw.lp.findlaw.com/data2/circs/7th/981659.html -- and observe that appeals courts sometimes screw up too (note the scathing commentary regarding the Ninth Circuit's opinion in Rano v. Sipa Press). Even in the Ninth, you probably wouldn't want to be using Rano as a central part of the argument in a case today. The only other alternative is that the GPL is not enforceable. That would probably call into question the validity of all software licenses. However, I am not lawyer (I'm sure you guessed that by now), so I will refrain from speaking further on this subject. IANAL either, but this sweeping statement is obviously nonsense. The typical EULA is a dog's breakfast of enforceable and unenforceable constraints, but there's getting to be quite a bit of statute and case law about how to construe a EULA under any given jurisdiction's contract law. A court of fact's analysis of the GPL terms would in any case have no value as precedent in a later court of fact where some EULA (or for that matter the GPL) is under discussion. The GPL is anomalous in that the drafter has published a widely believed, but patently false, set of claims about its legal basis in the FSF FAQ. Yet in many ways the actual GPL text, properly construed, is sounder than the typical EULA. I don't believe that it bans all of the things that the FSF says it does (notably dynamic linking GPL and non-GPL code). But the only thing I can see that might jeopardize its validity with respect to real derivative works is the difficulty of construing a legitimate implementation of that automatically receives language in Section 6, which a court would have to construe in terms of conventional rules of agency to sub-license. Incidentally, if there was so much controversy about this and the origins and rights to the code have been in question, why has SourceForge let the project continue for 2 years? I imagine that it is not their responsibility that to comb through every piece of code housed on their servers. However, I would imagine that it would be part of their due diligence to verify whether a project like this can even exist on their servers in the first place. SourceForge is not the tightest run ship on the planet. They are probably not protected by any kind of common carrier exemption, but they also probably figure they can wait until they get a cease and desist letter. In the real world, most violations of the law go unpunished unless they involve major bodily harm, justify a claim for large monetary damages, run afoul of the ascendant political agenda, or really piss someone off. Cheers, - Michael
Re: Changes to the weekly WNPP posting
On Thu, 2005-05-19 at 17:43 +0100, Martin Michlmayr wrote: * Christoph Berg [EMAIL PROTECTED] [2005-05-19 18:40]: How about posting the announcements to -devel (instead of -d-a)? If only new entries are included, it wouldn't hurt much for those who are not interested. I agree that this might be a good idea. debian-wnpp is quite cluttered with all the control messages from the BTS. What do other people think of this? Do you want a shorter WNPP posting with only new entries on -devel? I think shorter WNPP postings with only new entries posted to -devel (or even -d-a) would be much better. I fall into the doesn't read WNPP summaries because they're too friggin' long category, but I'd certainly glance through them, would they be shorter and posted to a list I'm subscribed to most of the time. -- Gergely Nagy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/19/05, Raul Miller [EMAIL PROTECTED] wrote: On 5/19/05, Michael K. Edwards [EMAIL PROTECTED] wrote: The GPL is anomalous in that the drafter has published a widely believed, but patently false, set of claims about its legal basis in the FSF FAQ. For the record, I disagree that this faq is patently false. It is, in places, a bit simplistic, but I wouldn't advise anyone delve into those fine points of law unless they've retained the services of a lawyer (at which point the FAQ is merely an interesting commentary -- it has less weight than professional advice). The FAQ is not merely an interesting commentary -- it is the published stance of the FSF, to which its General Counsel refers all inquiries. Although I am not legally qualified to judge, I believe that he can have no reasonable basis under the law in his jurisdiction for many of the assertions that it contains, particularly the assertion that the GPL is a creature of copyright law and not an ordinary offer of contract. That may yet become a problem for him personally as well as for the FSF. This is not a fine point of law, it is first-year law student stuff that anyone with a modicum of familiarity with legalese can easily verify for himself or herself by the use of two law references (Nimmer on Copyright and Corbin on Contracts) found in every law library in the US. These law references are probably also available from most law libraries in any English-speaking country and the bigger ones anywhere in the world, as are their equivalents for other national implementations. The fact that all licenses are (terms in) contracts is also blatantly obvious from a few hours' perusal of the primary literature -- statute and appellate case law -- which is available for free through www.findlaw.com. Don't believe me; look it up for yourself. Furthermore, that FAQ is far and away better than anything you've proposed. If that is a challenge to produce an adequate summary of my writings to date on the topic, I think I'll take it up, in my own sweet time. It won't be legal advice (IANAL), but it will be firmly grounded in the applicable law to the best of my ability, which is a hell of a lot more than you can say for the FSF FAQ. Cheers, - Michael
Re: Changes to the weekly WNPP posting
On Thu, May 19, 2005 at 05:28:50PM +0100, Martin Michlmayr wrote: WNPP (Work-Needing and Prospective Packages) is an important part of our infrastructure used to discuss packages to be added to the archive and, in particular, to look for new or additional maintainers for existing packages. In the last few years, WNPP summaries have been posted weekly to this mailing list to show packages which are currently orphaned or up for adoption. I think that these weekly postings are no longer effective. I suspect that most people delete them without reading and they only clutter up this list - the only list which Debian developers are required to subscribe to. Furthermore, Debian Weekly News (DWN) has had a WNPP section for a while, further reducing the usefulness of these weekly postings. I have therefore decided to stop the weekly WNPP summaries to d-d-a and instead do the following: - send the weekly posting to debian-wnpp instead of d-d-a - only include new entries What about sending only new entries to d-d-a ? it would sure be more interesting to read if there where only new entries, or even the new entries first, and then all the other ones. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
Adeodato Simó [EMAIL PROTECTED] writes: * Anthony Towns [Thu, 19 May 2005 15:38:11 +1000]: Adeodato Simó wrote: As you probably know, entries in the Packages file only have a Source field if the name of the source package is different from the name of the binary package being described. This is an inconsistency that makes it a bit harder to massage this data, e.g. with grep-dctrl. Why not add a patch to grep-dctrl instead? grep-dctrl was only meant an example: every script or whatever parsing Packages files will have to deal with that inconsistency (in the case of a Perl or similar script, it's less cumbersome that with grep-dctrl, that's true). Fixing apt-ftparchive solves the issue for everybody, hence what I was looking to know is if there is a reason for which the current behavior of apt-ftparchive should not be changed. Cheers, apt-ftparchive can't reliably fix this as it breaks for binary NMUs. The right place is to tackle this on the dpkg level and always include the Sources entry in the control and changes files. Should be a trivial patch to dpkg-gencontrol to always add the field and a simple patch to add binary NMU support. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changes to the weekly WNPP posting
* Ben Armstrong | How about posting the announcements to -devel (instead of -d-a)? If | only new entries are included, it wouldn't hurt much for those who are | not interested. | | I'd like to see them continue on -d-a. There are times when I just | can't handle -devel and unsub completely. They really don't add up to | much traffic, and the new entries only change should help bring back | some people to doing regular reviews that they had developed a | resistance to doing due to having to wade through too many old entries | to see the new ones. FWIW, me too. I'd hate to see the listing go away completely, but trimming it to only show new entries might be a good idea. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `-
Thanks for your email
Thank you for your comments! Brian Hewitt The Golf Channel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/19/05, Michael K. Edwards [EMAIL PROTECTED] wrote: The GPL is anomalous in that the drafter has published a widely believed, but patently false, set of claims about its legal basis in the FSF FAQ. For the record, I disagree that this faq is patently false. It is, in places, a bit simplistic, but I wouldn't advise anyone delve into those fine points of law unless they've retained the services of a lawyer (at which point the FAQ is merely an interesting commentary -- it has less weight than professional advice). Furthermore, that FAQ is far and away better than anything you've proposed. -- Raul
Re: alioth mailing list moderation broken for extended period of time
On Thu, 19 May 2005 11:58:47 +0200, Goswin von Brederlow [EMAIL PROTECTED] wrote: Did the move change anything? No: |From: Mail Delivery System [EMAIL PROTECTED] |Subject: Mail delivery failed: returning message to sender |To: [EMAIL PROTECTED] |Date: Thu, 19 May 2005 22:09:04 + | |This message was created automatically by mail delivery software. | |A message that you sent could not be delivered to one or more of its |recipients. This is a permanent error. The following address(es) failed: | | pipe to |/var/lib/mailman/mail/wrapper admin pkg-exim4-users |generated by [EMAIL PROTECTED] |local delivery failed | |The following text was generated during the delivery attempt: | |-- pipe to |/var/lib/mailman/mail/wrapper admin pkg-exim4-users | generated by [EMAIL PROTECTED] -- | |Illegal command: admin Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/19/05, Raul Miller [EMAIL PROTECTED] wrote: For the record, I disagree that this faq is patently false. It is, in places, a bit simplistic, but I wouldn't advise anyone delve into those fine points of law unless they've retained the services of a lawyer (at which point the FAQ is merely an interesting commentary -- it has less weight than professional advice). On 5/19/05, Michael K. Edwards [EMAIL PROTECTED] wrote: The FAQ is not merely an interesting commentary -- it is the published stance of the FSF, to which its General Counsel refers all inquiries. And if you have retained counsel of your own, I'd let your lawyer deal with that. If you haven't, then my interesting commentary comment is irrelevant. Perhaps that is indeed what you would do. I don't consider lawyers to be the only persons capable of reading the law for themselves. They are the only ones authorized to offer certain forms of legal advice and legal representation, but that's a whole 'nother animal. Although I am not legally qualified to judge, I believe that he can have no reasonable basis under the law in his jurisdiction for many of the assertions that it contains, particularly the assertion that the GPL is a creature of copyright law and not an ordinary offer of contract. That may yet become a problem for him personally as well as for the FSF. I don't find in the GPL FAQ any assertion that the GPL is not to be considered an agreement under contract law. Very, very interesting. The grossly erroneous conclusions are there (including various statements about run-time use that are false in the US in light of 17 USC 117, and false for other reasons in many other jurisdictions), but the GPL is a creature of copyright law bit is not. Does anyone happen to have a six-month-old copy of the FSF FAQ? Happily, the public record is not limited to websites under the FSF's control. Google Eben Moglen for the text of various interviews, and read his statements (especially paragraph 18) in http://www.gnu.org/press/mysql-affidavit.html -- or Google's cached copy, if that URL mysteriously stops working. I can only guess that you're objecting to the implication that copyright law is somehow important to understanding the GPL. Presumably this bit of grandstanding is meant for the benefit of any reader who doesn't know that you and I have been spamming debian-legal (and on and off debian-devel) with this debate for months, and hence you can guess a great deal more than that. I'm stopping here because I'm assuming that the rest of what you wrote is somehow logically related to these assertions which do not appear in the FAQ. Yeah, right. Like you haven't been arguing strenuously for months that the GPL is not an offer of contract. I am starting to question your sincerity again. - Michael
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
Michael K. Edwards wrote: not. Does anyone happen to have a six-month-old copy of the FSF FAQ? From 11-2004: http://web.archive.org/web/20041130014304/http://www.gnu.org/philosophy/free-sw.html http://web.archive.org/web/20041105024302/http://www.gnu.org/licenses/gpl-faq.html -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr signature.asc Description: OpenPGP digital signature
Orphaning cantus3 [was: Re: Upcoming removals]
Martin Michlmayr wrote: * Igor Stroh [EMAIL PROTECTED] [2005-05-06 22:10]: From what I can tell, cantus3 doesn't actually provide all of the functionality originally present in cantus. And it won't either -- the upstream is unresponsive and seems to have no interest neither in incorporating bug fixes nor in adding features which the package formerly claimed to be offering[0]. I'd suggest to remove cantus3 from the archive if it wouldn't have so many users (according to popcon.d.o) - there are better Has there been any agreement about what to do with cantus and cantus3? Since you're the maintainer of cantus3 and you suggest it's removal, can you go ahead and file a bug report on ftp.d.o? I don't like the idea of removing cantus3 right away, maybe there's someone who's actually using it and is willing to take over its' maintenance. Anyone up to adopt it? If nobody speaks up, I'll request a removal. Should cantus be removed too? Yes, imho it's outdated. I'll file a bug report against ftp.d.o. Cheers, Igor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Orphaning cantus3 [was: Re: Upcoming removals]
* Igor Stroh [EMAIL PROTECTED] [2005-05-20 01:18]: Has there been any agreement about what to do with cantus and cantus3? Since you're the maintainer of cantus3 and you suggest it's removal, can you go ahead and file a bug report on ftp.d.o? I don't like the idea of removing cantus3 right away, maybe there's someone who's actually using it and is willing to take over its' maintenance. Maybe it should be removed from sarge but stay in unstable for now? Should cantus be removed too? Yes, imho it's outdated. I'll file a bug report against ftp.d.o. No, reassign the existing WNPP bug to ftp.d.o. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
For the record, I disagree that this faq is patently false. It is, in places, a bit simplistic, but I wouldn't advise anyone delve into those fine points of law unless they've retained the services of a lawyer (at which point the FAQ is merely an interesting commentary -- it has less weight than professional advice). On 5/19/05, Michael K. Edwards [EMAIL PROTECTED] wrote: The FAQ is not merely an interesting commentary -- it is the published stance of the FSF, to which its General Counsel refers all inquiries. And if you have retained counsel of your own, I'd let your lawyer deal with that. If you haven't, then my interesting commentary comment is irrelevant. Although I am not legally qualified to judge, I believe that he can have no reasonable basis under the law in his jurisdiction for many of the assertions that it contains, particularly the assertion that the GPL is a creature of copyright law and not an ordinary offer of contract. That may yet become a problem for him personally as well as for the FSF. I don't find in the GPL FAQ any assertion that the GPL is not to be considered an agreement under contract law. I can only guess that you're objecting to the implication that copyright law is somehow important to understanding the GPL. I'm stopping here because I'm assuming that the rest of what you wrote is somehow logically related to these assertions which do not appear in the FAQ. -- Raul
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/19/05, Roberto C. Sanchez [EMAIL PROTECTED] wrote: http://web.archive.org/web/20041130014304/http://www.gnu.org/philosophy/free-sw.html http://web.archive.org/web/20041105024302/http://www.gnu.org/licenses/gpl-faq.html Thanks, Roberto. The (moderately) explicit bit I had in mind is in fact still in the current FAQ, I just missed it: ( http://www.fsf.org/licensing/licenses/gpl-faq.html#TOCIfInterpreterIsGPL ) ... The interpreted program, to the interpreter, is just data; a free software license like the GPL, based on copyright law, cannot limit what data you use the interpreter on. But you are quite right to provide the philosophy link, since that's the one that (IMHO, IANAL) goes way over the top: quote Most free software licenses are based on copyright, and there are limits on what kinds of requirements can be imposed through copyright. If a copyright-based license respects freedom in the ways described above, it is unlikely to have some other sort of problem that we never anticipated (though this does happen occasionally). However, some free software licenses are based on contracts, and contracts can impose a much larger range of possible restrictions. That means there are many possible ways such a license could be unacceptably restrictive and non-free. We can't possibly list all the possible contract restrictions that would be unacceptable. If a contract-based license restricts the user in an unusual way that copyright-based licenses cannot, and which isn't mentioned here as legitimate, we will have to think about it, and we will probably decide it is non-free. /quote This text is still present in http://www.fsf.org/licensing/essays/free-sw.html . Cheers, - Michael
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/19/05, Raul Miller [EMAIL PROTECTED] wrote: [snip Raul's honest and polite response] I've been objecting to the nature of the generalizations you've been making. In other words, I see you asserting that things which are sometimes true must always be true. In the case of the contract issue -- I've been arguing that it's not always the case that the law will rely solely on contract law. I've not been arguing that contract law would never apply. I believe it to be the case that contract law is the only basis on which the text of the GPL has any significance whatsoever in any jurisdiction I have heard spoken of, except that some jurisdictions may also apply doctrines of estoppel, reliance, etc. against the FSF and other GPL licensors in tort proceedings. An action for copyright infringement, or any similar proceeding under droit d'auteur for instance, will look at the GPL (like any other license agreement) only through the lens of contract law. IANAL, TINLA. I don't believe you have succeeded in providing any evidence to the contrary. In my opinion, an assertion that contract law would never apply would involve the same kind of over generalization as an assertion that contract law must always apply. Contract law (or its equivalent in a civil law system) always applies to offers of contract; that's kind of tautological. And the GPL has no legal significance as anything other than an offer of contract, except perhaps as a public statement by the FSF and hence conceivably as grounds for estoppel. I have been convinced, over the last week, that within the U.S., contract law will almost always apply. I think there is a basis even in U.S. law for other kinds of legal action, but I think that you're much more likely to find examples in international law than in U.S. law. People with actual legal qualifications in continental Europe and in Brazil, as well as other laymen who read and cite law, have weighed in on this one. While they are less prolix than I, they seem to be no less certain as to the offer-of-contract nature of the GPL. Have you any more evidence to adduce in opposition? Cheers, - Michael
Re: Changes to the weekly WNPP posting
Hi Martin, On Thursday 19 May 2005 10:28, Martin Michlmayr wrote: WNPP (Work-Needing and Prospective Packages) is an important part of our infrastructure used to discuss packages to be added to the archive and, in particular, to look for new or additional maintainers for existing packages. [ . . . ] I have therefore decided to stop the weekly WNPP summaries to d-d-a and instead do the following: - send the weekly posting to debian-wnpp instead of d-d-a - only include new entries Finally, please note that I will go through the list of orphaned packages after sarge is out and will request removal of packages which have not been maintained for a long time. Now is your chance to check whether you are using any of them. Please visit http://www.debian.org/devel/wnpp/ for more information. One suggestion might be to include both new entries, and entries that are about to be requested for removal. That seems like it might be useful. What do you think? -- Wesley J. Landaker [EMAIL PROTECTED] OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 pgpmPCNVwGoFh.pgp Description: PGP signature
Request for key signing help
I am looking for someone to sign my gpg key. I have contacted the three people listed as offering to sign keys in Ohio [0], but I have received no response after a few days. Anibal suggested I ask on d-d. So, if anyone is able to sign my gpg key so I can get recognized by the front desk, I would appreciate it. Please reply off-list and we can make arrangements to meet. -Roberto [0] http://nm.debian.org/gpg_offer.php -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr signature.asc Description: OpenPGP digital signature
Re: Entries in Packages files that lack a Source field
On Thu, May 19, 2005 at 07:34:46PM +0200, Jeroen van Wolffelaar wrote: On Thu, May 19, 2005 at 12:18:55PM +0200, Goswin von Brederlow wrote: The detection of binary NMUs is currently, among others, using the debian version of a package and guessing from its form. What is a binary NMU and what not is not aparent from the Packages file. It has been suggested to insert Source: entries pointing to the original source of an binary NMU instead. That should probably happen regardless, and is because dpkg doesn't have the proper support for it. It's independent of whether to add Source: lines when unneeded in any other case. If you bin-NMU, you *are* building from a source called -N.0.1, because you changed the changelog. dpkg-dev could have some means to build with different version number from the same source package, or any other (probably a bit hacky) way to achieve this. I am not sure it is relevant, but dpkg-dev already support binary packages having a different version than the source packages, by adding a Version field to debian/control. There is at least one package that use this facility: olvwm: Package: olvwm Architecture: i386 Source: xview (3.2p1.4-19) Version: 4.4.3.2p1.4-19 So we could have for binNMU: Source: foo (1-1) Version: 1-1.0.1 It is possible to do that with current dpkg-dev by 1) not adding a new version field to the changelog, add any comment to the last one (the maintainer one). 2) add a Version field to debian/control with the .0.1 version. Cheers, -- Bill. [EMAIL PROTECTED] Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [WASTE-dev-public] Do not package WASTE! UNAUTHORIZED SOFTWARE [Was: Re: Questions about waste licence and code.]
On 5/19/05, Michael K. Edwards [EMAIL PROTECTED] wrote: Perhaps that is indeed what you would do. I don't consider lawyers to be the only persons capable of reading the law for themselves. They are the only ones authorized to offer certain forms of legal advice and legal representation, but that's a whole 'nother animal. In a sense, it's that ability to offer legal advice which I was talking about. In any event, I'd consider going to a lawyer as better than listening to someone else reading the law for themselves. Happily, the public record is not limited to websites under the FSF's control. Google Eben Moglen for the text of various interviews, and read his statements (especially paragraph 18) in http://www.gnu.org/press/mysql-affidavit.html -- or Google's cached copy, if that URL mysteriously stops working. Are you talking about point18? It's pretty clear that 18 refers to people who are not engaged in copying or distributing. There are no terms in the GPL which impose any contractual obligations in those cases. (Though it is the case that if someone is distributing a work illegally, that a person could receive work which supposedly has been released under the GPL but where parts of it aren't legal for further distribution.) I can only guess that you're objecting to the implication that copyright law is somehow important to understanding the GPL. Presumably this bit of grandstanding is meant for the benefit of any reader who doesn't know that you and I have been spamming debian-legal (and on and off debian-devel) with this debate for months, and hence you can guess a great deal more than that. Well... if I thought I understood what your points were, I'd probably be in better shape here. For the most parts, I'm hung up on what appear to me to be gross leaps of illogic, and I'm reduced to guessing about what your points are. I'm stopping here because I'm assuming that the rest of what you wrote is somehow logically related to these assertions which do not appear in the FAQ. Yeah, right. Like you haven't been arguing strenuously for months that the GPL is not an offer of contract. I am starting to question your sincerity again. I've been objecting to the nature of the generalizations you've been making. In other words, I see you asserting that things which are sometimes true must always be true. In the case of the contract issue -- I've been arguing that it's not always the case that the law will rely solely on contract law. I've not been arguing that contract law would never apply. In my opinion, an assertion that contract law would never apply would involve the same kind of over generalization as an assertion that contract law must always apply. I have been convinced, over the last week, that within the U.S., contract law will almost always apply. I think there is a basis even in U.S. law for other kinds of legal action, but I think that you're much more likely to find examples in international law than in U.S. law. -- Raul
Re: RES: /usr/lib vs /usr/libexec
Thomas == Thomas Bushnell BSG [EMAIL PROTECTED] writes: Thomas sbin is for things that should be in root's path. The Thomas executables in question are ones that shouldn't be in Thomas anyone's path. (The standard example is programs started Thomas only by inetd.) Why not put them under /usr/lib/$packagename/*? I have only seen one argument against this proposal, and that was of (unverified) performance issues. If a given file system does have performance problems with /usr/lib, isn't the correct solution to fix the file system? Disclaimer: I don't care too much either way. It is perhaps worth noting that a package I maintain does use /usr/lib/$packagename/* for inetd servers, and this reduces file conflicts with other packages. -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITP: skim -- Smart Common Input Method platform for KDE/QT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: wnpp Severity: wishlist Owner: William J Beksi [EMAIL PROTECTED] * Package name: skim ~ Version : 1.2.2 ~ Upstream Author : liuspider [EMAIL PROTECTED] * URL : http://www.scim-im.org/ * License : GPL ~ Description : Smart Common Input Method platform for KDE/QT skim is an input method platform based upon scim-lib under *NIX systems (including GNU/Linux and FreeBSD) optimized for KDE. It provides a GUI panel (named scim-panel-kde), a KConfig config module and setup dialogs for itself and libscim. It also has its own plugin system which supports on-demand loadable actions. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCjVBcyy8yU+fh2zsRAmslAJsGXWuDSEGf1fFa/oS02f8Ftr3D3wCfYNRd RudL3q7nHbMn9YV0NXdcO6E= =l2Mw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RES: /usr/lib vs /usr/libexec
Brian May [EMAIL PROTECTED] writes: /bin/mount foo:whatever /bin I was considering commenting on this, I think if you want to start going down this track it would be simpler to write/adapt a script that automatically creates an initramfs. Yes, this is surely true. When I had the need for this, it was long long before the existence of such things. But that is probably without doubt the best solution now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re:
Michael K. Edwards [EMAIL PROTECTED] writes: The FAQ is not merely an interesting commentary -- it is the published stance of the FSF, to which its General Counsel refers all inquiries. Although I am not legally qualified to judge, I believe that he can have no reasonable basis under the law in his jurisdiction for many of the assertions that it contains, particularly the assertion that the GPL is a creature of copyright law and not an ordinary offer of contract. That may yet become a problem for him personally as well as for the FSF. If it is merely an offer of contract, then because no written or verbal acceptance has been given, nobody has permission to copy anything GPLd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re:
Michael K. Edwards [EMAIL PROTECTED] writes: An action for copyright infringement, or any similar proceeding under droit d'auteur for instance, will look at the GPL (like any other license agreement) only through the lens of contract law. IANAL, TINLA. I don't believe you have succeeded in providing any evidence to the contrary. Um, it is true that the rules for interpreting the meaning of licenses are more or less the same as the rules for interpreting contracts. It does not follow that licenses are therefore contracts. Contract law (or its equivalent in a civil law system) always applies to offers of contract; that's kind of tautological. And the GPL has no legal significance as anything other than an offer of contract, except perhaps as a public statement by the FSF and hence conceivably as grounds for estoppel. Huh? What about the license as just what it purports to be: a license? There is a thing you are not considering: it is a unilateral grant of conditional permission. This is a perfectly well-traveled area of law. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309861: ITP: xfce4-quicklauncher-plugin -- rapid launcher plugin for the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Debian Xfce Maintainers [EMAIL PROTECTED] * Package name: xfce4-quicklauncher-plugin Version : 0.8 Upstream Author : Masse Nicolas [EMAIL PROTECTED] * URL : http://www.example.org/ * License : GPL Description : rapid launcher plugin for the Xfce4 panel Application launcher plugin for the Xfce panel. . Main differences from the original Xfce panel: . - Multiline support - Easy and fast configuration - Zoom effect . Homepage: http://xfce-goodies.berlios.de/ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-powerpc Locale: LANG=es_PE.UTF-8, LC_CTYPE=es_PE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309860: ITP: xfce4-genmon-plugin -- Generic Monitor for the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Debian Xfce Maintainers [EMAIL PROTECTED] * Package name: xfce4-genmon-plugin Version : 1.1 Upstream Author : Roger Seguin [EMAIL PROTECTED] * URL : http://xfce-goodies.berlios.de * License : LGPL Description : Generic Monitor for the Xfce4 panel This plugin cyclically spawn the indicated script/program, displaying its output as a string into the panel. It could be useful for periodic monitoring of program's status. . Homepage: http://xfce-goodies.berlios.de/ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-powerpc Locale: LANG=es_PE.UTF-8, LC_CTYPE=es_PE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Entries in Packages files that lack a Source field
Bill Allombert [EMAIL PROTECTED] writes: On Thu, May 19, 2005 at 07:34:46PM +0200, Jeroen van Wolffelaar wrote: On Thu, May 19, 2005 at 12:18:55PM +0200, Goswin von Brederlow wrote: The detection of binary NMUs is currently, among others, using the debian version of a package and guessing from its form. What is a binary NMU and what not is not aparent from the Packages file. It has been suggested to insert Source: entries pointing to the original source of an binary NMU instead. That should probably happen regardless, and is because dpkg doesn't have the proper support for it. It's independent of whether to add Source: lines when unneeded in any other case. If you bin-NMU, you *are* building from a source called -N.0.1, because you changed the changelog. dpkg-dev could have some means to build with different version number from the same source package, or any other (probably a bit hacky) way to achieve this. I am not sure it is relevant, but dpkg-dev already support binary packages having a different version than the source packages, by adding a Version field to debian/control. There is at least one package that use this facility: olvwm: Package: olvwm Architecture: i386 Source: xview (3.2p1.4-19) Version: 4.4.3.2p1.4-19 So we could have for binNMU: Source: foo (1-1) Version: 1-1.0.1 It is possible to do that with current dpkg-dev by 1) not adding a new version field to the changelog, add any comment to the last one (the maintainer one). 2) add a Version field to debian/control with the .0.1 version. Cheers, -- Bill. [EMAIL PROTECTED] That is sort of the idea but in a cleaner way. The idea was, iirc, to add an option to dpkg-buildpackage for binary-NMU that getts passed down to dpkg-gencontrol and adds Source: foo (1-1) for Version: 1-1.0.1, automatically cuting away the bin-NMU revision. The DAK can then accept them the normal way (as the right source version already exists in archive) and reject any bin-NMUs without this (as their source will be seen as missing). apt-ftparchive, dpkg-scanpackage, whatever tool will automatically do the right thing too. A further idea was to have e.g. dpkg-buildpackage --binary-nmu 'reason for doing this' that will automatically add the changelog entry for the binary-nmu with the given reason and build with the right flags. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309862: ITP: xfce4-cpugraph-plugin -- cpu load grap plugin for the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Debian Xfce Maintainers [EMAIL PROTECTED] * Package name: xfce4-cpugraph-plugin Version : 0.2.2 Upstream Author : Alexander Nordfelth [EMAIL PROTECTED] * URL : http://xfce-goodies.berlios.de/ * License : BSD Description : cpu load grap plugin for the Xfce4 panel The cpugraph plugin displays a graph from your latest systemload. . Homepage: http://xfce-goodies.berlios.de/ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-powerpc Locale: LANG=es_PE.UTF-8, LC_CTYPE=es_PE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#309863: ITP: xfce4-fsguard-plugin -- filesystem monitor plugin for the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Debian Xfce Maintainers [EMAIL PROTECTED] * Package name: xfce4-fsguard-plugin Version : 0.2.0 Upstream Author : Andre Lerche [EMAIL PROTECTED] * URL : http://xfce-goodies.berlios.de/ * License : BSD Description : filesystem monitor plugin for the Xfce4 panel The fsguard plugin checks free space on a chosen mountpoint frequently and displays an alarm if free space is less than given alarm limit. . Homepage: http://xfce-goodies.berlios.de/ -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-powerpc Locale: LANG=es_PE.UTF-8, LC_CTYPE=es_PE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Please try out dpatch 2.0.12 from experimental
Hi, on the weekend, dpatch 2.0.12 has been uploaded to experimental. It introduces some great new features and some fixes that are inappropriate for unstable at this stage of the release[1]. Please try out the package from experimental to find bugs before it is uploaded to unstable. Greetings Marc [1] if the release team says ok, I can upload to unstable on the weekend or in the middle of next week, but I won't do before sarge release so without the explicit Ok. -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re:
On 5/19/05, Thomas Bushnell BSG [EMAIL PROTECTED] wrote: Michael K. Edwards [EMAIL PROTECTED] writes: An action for copyright infringement, or any similar proceeding under droit d'auteur for instance, will look at the GPL (like any other license agreement) only through the lens of contract law. IANAL, TINLA. I don't believe you have succeeded in providing any evidence to the contrary. Um, it is true that the rules for interpreting the meaning of licenses are more or less the same as the rules for interpreting contracts. It does not follow that licenses are therefore contracts. The words license and contract are indeed not synonymous under law. But the law applicable to offers of contract containing grants of license is contract law (or the equivalent codes in civil law systems). Contract law (or its equivalent in a civil law system) always applies to offers of contract; that's kind of tautological. And the GPL has no legal significance as anything other than an offer of contract, except perhaps as a public statement by the FSF and hence conceivably as grounds for estoppel. Huh? What about the license as just what it purports to be: a license? You're a little bit late to the party. Check the debian-legal archives for debate and case law out the yin-yang. There's no such thing as a copyright-based license. There is a thing you are not considering: it is a unilateral grant of conditional permission. This is a perfectly well-traveled area of law. Also part of contract law; and not applicable to the GPL, which does not lack for acceptance or consideration. Thread at http://lists.debian.org/debian-legal/2004/12/msg00209.html . Cheers, - Michael (IANAL, TINLA, etc.)
Accepted flyspray 0.9.7-3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 09:08:54 +0200 Source: flyspray Binary: flyspray Architecture: source all Version: 0.9.7-3 Distribution: unstable Urgency: low Maintainer: Pierre Habouzit [EMAIL PROTECTED] Changed-By: Pierre Habouzit [EMAIL PROTECTED] Description: flyspray - lightweight Bug Tracking System (BTS) in PHP Closes: 306928 309171 Changes: flyspray (0.9.7-3) unstable; urgency=low . * Debconf templates : add czech translation (closes: #309171). * Fix problem with db type set to Manual at upgrade time (closes: #306928). . * Use my brand new debian account. Files: 97ed69789a5eb8c6fccc16b9dcbbbf7e 595 web optional flyspray_0.9.7-3.dsc 880e3fe81d045508fa3bb4db695635fe 19863 web optional flyspray_0.9.7-3.diff.gz a0c27b9e21e0fecde3c2ffd2717f5cf4 344988 web optional flyspray_0.9.7-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjDx6vGr7W6HudhwRAn08AJ4rbwmfKlsqh6lzDAXmAdWGUcGoQQCfewMz 20WYPdq+SiKTdjTmig8N18Q= =zXvA -END PGP SIGNATURE- Accepted: flyspray_0.9.7-3.diff.gz to pool/main/f/flyspray/flyspray_0.9.7-3.diff.gz flyspray_0.9.7-3.dsc to pool/main/f/flyspray/flyspray_0.9.7-3.dsc flyspray_0.9.7-3_all.deb to pool/main/f/flyspray/flyspray_0.9.7-3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted nvidia-cg-toolkit 1.3.0501.0700-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 10:08:09 +0200 Source: nvidia-cg-toolkit Binary: nvidia-cg-toolkit Architecture: source i386 Version: 1.3.0501.0700-2 Distribution: unstable Urgency: low Maintainer: Federico Di Gregorio [EMAIL PROTECTED] Changed-By: Federico Di Gregorio [EMAIL PROTECTED] Description: nvidia-cg-toolkit - NVIDIA Cg Toolkit installer Changes: nvidia-cg-toolkit (1.3.0501.0700-2) unstable; urgency=low . * Applied patch from Drew Hess to fix a path bug. Files: 9fd7b0e8771199212206b451bb877164 568 contrib/libs optional nvidia-cg-toolkit_1.3.0501.0700-2.dsc c0fbe21cf05af77cf8d3a2ac5ea61f93 9446 contrib/libs optional nvidia-cg-toolkit_1.3.0501.0700-2.tar.gz dc6c39c4e5d2491cb565bac71a4d2c87 9980 contrib/libs optional nvidia-cg-toolkit_1.3.0501.0700-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjEmFvcCgrgZGjesRAhBtAKCb6wWxpStsCZlUzLJn90KPySWr4QCgj/Ef 6zB2sI7rvfeo6KRWHGLT3GA= =aw+8 -END PGP SIGNATURE- Accepted: nvidia-cg-toolkit_1.3.0501.0700-2.dsc to pool/contrib/n/nvidia-cg-toolkit/nvidia-cg-toolkit_1.3.0501.0700-2.dsc nvidia-cg-toolkit_1.3.0501.0700-2.tar.gz to pool/contrib/n/nvidia-cg-toolkit/nvidia-cg-toolkit_1.3.0501.0700-2.tar.gz nvidia-cg-toolkit_1.3.0501.0700-2_i386.deb to pool/contrib/n/nvidia-cg-toolkit/nvidia-cg-toolkit_1.3.0501.0700-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted mountfloppy 0.2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 09:36:22 +0100 Source: mountfloppy Binary: mountfloppy Architecture: source all Version: 0.2 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Colin Watson [EMAIL PROTECTED] Description: mountfloppy - Mounts a floppy (udeb) Changes: mountfloppy (0.2) unstable; urgency=low . * Colin Watson - Set debconf template output encoding to UTF-8. * Updated translations: - Bulgarian (bg.po) by Ognyan Kulev - Czech (cs.po) by Miroslav Kure - Danish (da.po) by Claus Hindsgaul - Greek, Modern (1453-) (el.po) by Kostas Papadimas - Spanish (es.po) by Enrique Matias Sanchez - Basque (eu.po) by Piarres Beobide - French (fr.po) by Christian Perrier - Italian (it.po) by Stefano Canepa - Japanese (ja.po) by Kenshi Muto - Portuguese (pt.po) by Miguel Figueiredo - Portuguese (Brazil) (pt_BR.po) by André Luís Lopes - Ukrainian (uk.po) by Eugeniy Meshcheryakov - Simplified Chinese (zh_CN.po) by Carlos Z.F. Liu Files: f20bf75f23a8fc4f465c57c084fc4e6b 585 debian-installer optional mountfloppy_0.2.dsc 3ebd8aefcf863321c95759c6329823f5 16573 debian-installer optional mountfloppy_0.2.tar.gz 78560639e3d241699361f97877619cb1 3982 debian-installer optional mountfloppy_0.2_all.udeb package-type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjFBr9t0zAhD6TNERAuYGAJwIy1+1ECtbDFlF9UpKAzHabQj41QCeO490 +lrcAfmdGqk11XX65H2nDGY= =TGQr -END PGP SIGNATURE- Accepted: mountfloppy_0.2.dsc to pool/main/m/mountfloppy/mountfloppy_0.2.dsc mountfloppy_0.2.tar.gz to pool/main/m/mountfloppy/mountfloppy_0.2.tar.gz mountfloppy_0.2_all.udeb to pool/main/m/mountfloppy/mountfloppy_0.2_all.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted synaptic 0.55+cvs20050503-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 10:32:50 +0200 Source: synaptic Binary: synaptic Architecture: source i386 Version: 0.55+cvs20050503-3 Distribution: unstable Urgency: high Maintainer: Michael Vogt [EMAIL PROTECTED] Changed-By: Michael Vogt [EMAIL PROTECTED] Description: synaptic - Graphical package manager Changes: synaptic (0.55+cvs20050503-3) unstable; urgency=high . * Remove NotShowIn=KDE from the synaptic.desktop file. This was used when there was a seperate synaptic-kde.desktop file. Urgency set to high so that this change can make it into Sarge. No other changes. Files: 2e1d2ed1c457369f2c5e5b3db9c1eb67 780 admin optional synaptic_0.55+cvs20050503-3.dsc e38f9abc091156ccd2e47442e232d782 45607 admin optional synaptic_0.55+cvs20050503-3.diff.gz 13c5920a9d1f61a0d73c89da5eb13567 1682472 admin optional synaptic_0.55+cvs20050503-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjFLrliSD4VZixzQRAosjAJ4viEk6rs5DivH+RyP1MvGMIOv8nwCfRGn4 WfdciTYUzn6UIF85p44bPWE= =lPfr -END PGP SIGNATURE- Accepted: synaptic_0.55+cvs20050503-3.diff.gz to pool/main/s/synaptic/synaptic_0.55+cvs20050503-3.diff.gz synaptic_0.55+cvs20050503-3.dsc to pool/main/s/synaptic/synaptic_0.55+cvs20050503-3.dsc synaptic_0.55+cvs20050503-3_i386.deb to pool/main/s/synaptic/synaptic_0.55+cvs20050503-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sig2dot 0.34-4 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 May 2005 23:48:47 +0200 Source: sig2dot Binary: sig2dot Architecture: source all Version: 0.34-4 Distribution: unstable Urgency: high Maintainer: Christoph Berg [EMAIL PROTECTED] Changed-By: Christoph Berg [EMAIL PROTECTED] Description: sig2dot- converts a list of GPG signatures to a .dot file Closes: 308271 Changes: sig2dot (0.34-4) unstable; urgency=high . * Fix breakage with gnupg 1.4 (keys with trust signatures) noted by Matthew Wilcox (Closes: #308271). Files: 7313c4dd4f30f4e42aa2ccbe862090d8 567 graphics extra sig2dot_0.34-4.dsc 2fc25f5f7a682ed40eebcc0107e68c04 4423 graphics extra sig2dot_0.34-4.diff.gz 6dca45edb822f524ac8397dd2ea3fb0c 8740 graphics extra sig2dot_0.34-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iEYEARECAAYFAkKMX3cACgkQELuA/Ba9d8YmHgCg5BS6jKcCTvZ/oqxXGJzlSyqb XV0AnRYwVSge7DUXuUdLGAGRmLTYDlbN =pAYa -END PGP SIGNATURE- Accepted: sig2dot_0.34-4.diff.gz to pool/main/s/sig2dot/sig2dot_0.34-4.diff.gz sig2dot_0.34-4.dsc to pool/main/s/sig2dot/sig2dot_0.34-4.dsc sig2dot_0.34-4_all.deb to pool/main/s/sig2dot/sig2dot_0.34-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted muse 0.6.3-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 May 2005 13:36:54 +0200 Source: muse Binary: muse Architecture: source i386 Version: 0.6.3-3 Distribution: unstable Urgency: medium Maintainer: Daniel Kobras [EMAIL PROTECTED] Changed-By: Daniel Kobras [EMAIL PROTECTED] Description: muse - Qt-based midi/audio sequencer Closes: 308024 Changes: muse (0.6.3-3) unstable; urgency=medium . * debian/po/cs.po: Added Czech translation of debconf template. Closes: #308024 Files: 564a13e0a6920957dc4d946da07b2bd3 709 sound optional muse_0.6.3-3.dsc cf357490ad985ce079e135d03bad18df 19311 sound optional muse_0.6.3-3.diff.gz 4e33d09dbb82f7b045b4dc46358bfc17 2452418 sound optional muse_0.6.3-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjGKzpOKIA4m/fisRApnuAJ99j53+rtuJDIgMryBbDCTEz7JMMACfUnac 8myBMDhytIekGmdeXSMbrBo= =D9Y3 -END PGP SIGNATURE- Accepted: muse_0.6.3-3.diff.gz to pool/main/m/muse/muse_0.6.3-3.diff.gz muse_0.6.3-3.dsc to pool/main/m/muse/muse_0.6.3-3.dsc muse_0.6.3-3_i386.deb to pool/main/m/muse/muse_0.6.3-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted noflushd 2.7.5-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 May 2005 13:06:42 +0200 Source: noflushd Binary: noflushd Architecture: source i386 Version: 2.7.5-2 Distribution: unstable Urgency: medium Maintainer: Daniel Kobras [EMAIL PROTECTED] Changed-By: Daniel Kobras [EMAIL PROTECTED] Description: noflushd - allow idle hard disks to spin down Closes: 309080 Changes: noflushd (2.7.5-2) unstable; urgency=medium . * debian/po/cs.po: Added Czech debconf translation. Closes: #309080 Files: a04c4b475d55f10ed6f9e9499da59ff7 578 utils optional noflushd_2.7.5-2.dsc a55b1a860b1ac837e04601028f89c1ed 2308 utils optional noflushd_2.7.5-2.diff.gz 475644b9608984b42a29dce201afd67e 59444 utils optional noflushd_2.7.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjGLDpOKIA4m/fisRAsCVAJsHFxUFQQ6+0lrDGwA2fky1sYUdfwCgpgVw qQE78pPAeXyT6Mx1n+FOEy0= =KHrb -END PGP SIGNATURE- Accepted: noflushd_2.7.5-2.diff.gz to pool/main/n/noflushd/noflushd_2.7.5-2.diff.gz noflushd_2.7.5-2.dsc to pool/main/n/noflushd/noflushd_2.7.5-2.dsc noflushd_2.7.5-2_i386.deb to pool/main/n/noflushd/noflushd_2.7.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kernel-source-2.4.27 2.4.27-10 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 May 2005 14:48:47 +0900 Source: kernel-source-2.4.27 Binary: kernel-tree-2.4.27 kernel-source-2.4.27 kernel-patch-debian-2.4.27 kernel-doc-2.4.27 Architecture: source all Version: 2.4.27-10 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Simon Horman [EMAIL PROTECTED] Description: kernel-doc-2.4.27 - Linux kernel specific documentation for version 2.4.27 kernel-patch-debian-2.4.27 - Debian patches to Linux 2.4.27 kernel-source-2.4.27 - Linux kernel source for version 2.4.27 with Debian patches kernel-tree-2.4.27 - Linux kernel source tree for building Debian kernel images Closes: 302704 302705 302864 305655 308757 Changes: kernel-source-2.4.27 (2.4.27-10) unstable; urgency=low . * 155_net-bluetooth-signdness-fix.diff: [Security] Fix signedness problem at socket creation in bluetooth which can lead to local root exploit. See CAN-2005-0750 (Simon Horman) (closes: Bug#302704) . * 156_fs-ext2-info-leak.diff: [Security] Fix information leak in ext2 which leads to a local information leak. See CAN-2005-0400 (Simon Horman) . * 157_fs-isofs-range-check-1.diff, 157_fs-isofs-range-check-2.diff, 157_fs-isofs-range-check-3.diff: [Security] Fix range checking in isofs which leads to a local crash and arbitary code execution. See CAN-2005-0815 (Simon Horman) (closes: #302864) . * 158_fs-binfmt_elf-dos.diff: Potential DOS in load_elf_library. See CAN-2005-0749 (Simon Horman) (closes: #302705) . * 159_fs-cramfs-stat.diff Fix to stat output for cramfs (Simon Horman) . * 160_drivers-net-sis900-oops.diff sis900 kernel oops fix (Simon Horman) . * 161_drivers-net-amd8111e-irq.diff AMD8111e driver was releasing an irq in some error situations (Simon Horman) . * 162_drivers-net-via-rhine-irq.diff VIA Rhine driver was releasing an irq in some error situations (Simon Horman) . * 165_VM_IO.diff added, 140_VM_IO.diff removed: [CAN-2004-1057] Updated fix for DoS from accessing freed kernel pages. The previous fix seems to have cuased some problems and this is the one that is upstream. (Simon Horman, Dann Frazier) . * 164_net-ipv4-icmp-quench.diff: [CAN-2004-0790] Just silently ignore ICMP Source Quench messages. (Simon Horman) (closes: #305655) . * 165_arch-ia64-kernel-missing-sysctl.diff: [CAN-2005-0137] Add missing sysctl slot for ia64 resolving local DoS. (Simon Horman) . * fs-binfmt_elf-dump-privelage.diff: Linux kernel ELF core dump privilege elevation See CAN-2005-1263. (closes: #308757). (Simon Horman) Files: 59d9aeb90e71e4b6369a6b4986da690b 888 devel optional kernel-source-2.4.27_2.4.27-10.dsc 0ccc5c9df0130e5da099cd1a7c8a7f64 688010 devel optional kernel-source-2.4.27_2.4.27-10.diff.gz 157b883cbfb91812912c16728eb61fa0 633228 devel optional kernel-patch-debian-2.4.27_2.4.27-10_all.deb 9478d7f77b06c30454ef7864d9487fd4 3576196 doc optional kernel-doc-2.4.27_2.4.27-10_all.deb 3ae3d29a6b8a3de23a860627f3b440c3 31022934 devel optional kernel-source-2.4.27_2.4.27-10_all.deb 15394d1f0d96b07955178f05296929e0 23348 devel optional kernel-tree-2.4.27_2.4.27-10_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjGuZdu+M6Iexz7URAnSkAJ9SWaRWL1fYfJzpqtV+TXQ3LhkidgCgynIE FHrCSlUvvU/NhZxzmELwM+0= =kbKC -END PGP SIGNATURE- Accepted: kernel-doc-2.4.27_2.4.27-10_all.deb to pool/main/k/kernel-source-2.4.27/kernel-doc-2.4.27_2.4.27-10_all.deb kernel-patch-debian-2.4.27_2.4.27-10_all.deb to pool/main/k/kernel-source-2.4.27/kernel-patch-debian-2.4.27_2.4.27-10_all.deb kernel-source-2.4.27_2.4.27-10.diff.gz to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-10.diff.gz kernel-source-2.4.27_2.4.27-10.dsc to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-10.dsc kernel-source-2.4.27_2.4.27-10_all.deb to pool/main/k/kernel-source-2.4.27/kernel-source-2.4.27_2.4.27-10_all.deb kernel-tree-2.4.27_2.4.27-10_all.deb to pool/main/k/kernel-source-2.4.27/kernel-tree-2.4.27_2.4.27-10_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kernel-image-2.4.27-i386 2.4.27-10 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 May 2005 14:48:26 +0900 Source: kernel-image-2.4.27-i386 Binary: kernel-headers-2.4.27-2-k6 kernel-pcmcia-modules-2.4.27-2-k7 kernel-pcmcia-modules-2.4.27-2-686 kernel-headers-2.4.27-2-686-smp kernel-pcmcia-modules-2.4.27-2-386 kernel-headers-2.4.27-2-k7-smp kernel-image-2.4.27-2-k7 kernel-headers-2.4.27-2-686 kernel-pcmcia-modules-2.4.27-2-k6 kernel-pcmcia-modules-2.4.27-2-686-smp kernel-image-2.4.27-2-686-smp kernel-headers-2.4.27-2 kernel-image-2.4.27-2-586tsc kernel-pcmcia-modules-2.4.27-2-586tsc kernel-headers-2.4.27-2-k7 kernel-image-2.4.27-2-686 kernel-headers-2.4.27-2-586tsc kernel-image-2.4.27-2-386 kernel-headers-2.4.27-2-386 kernel-build-2.4.27-2 kernel-image-2.4.27-2-k6 kernel-pcmcia-modules-2.4.27-2-k7-smp kernel-image-2.4.27-2-k7-smp Architecture: source i386 Version: 2.4.27-10 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Simon Horman [EMAIL PROTECTED] Description: kernel-build-2.4.27-2 - Headers for building modules for Linux 2.4.27 kernel-headers-2.4.27-2 - Header files related to Linux kernel version 2.4.27 kernel-headers-2.4.27-2-386 - Linux 2.4.27 kernel headers for 386 kernel-headers-2.4.27-2-586tsc - Linux 2.4.27 kernel headers for Pentium-Classic kernel-headers-2.4.27-2-686 - Linux 2.4.27 kernel headers for PPro/Celeron/PII/PIII/P4 kernel-headers-2.4.27-2-686-smp - Linux 2.4.27 kernel headers for PPro/Celeron/PII/PIII/P4 SMP kernel-headers-2.4.27-2-k6 - Linux 2.4.27 kernel headers for AMD K6/K6-II/K6-III kernel-headers-2.4.27-2-k7 - Linux 2.4.27 kernel headers for AMD K7 kernel-headers-2.4.27-2-k7-smp - Linux 2.4.27 kernel headers for AMD K7 SMP kernel-image-2.4.27-2-386 - Linux kernel image for version 2.4.27 on 386 kernel-image-2.4.27-2-586tsc - Linux kernel image for version 2.4.27 on Pentium-Classic kernel-image-2.4.27-2-686 - Linux kernel image for version 2.4.27 on PPro/Celeron/PII/PIII/P4 kernel-image-2.4.27-2-686-smp - Linux kernel image for version 2.4.27 on PPro/Celeron/PII/PIII/P4 kernel-image-2.4.27-2-k6 - Linux kernel image for version 2.4.27 on AMD K6/K6-II/K6-III kernel-image-2.4.27-2-k7 - Linux kernel image for version 2.4.27 on AMD K7 kernel-image-2.4.27-2-k7-smp - Linux kernel image for version 2.4.27 on AMD K7 SMP kernel-pcmcia-modules-2.4.27-2-386 - Mainstream PCMCIA modules 2.4.27 on 386 kernel-pcmcia-modules-2.4.27-2-586tsc - Mainstream PCMCIA modules 2.4.27 on Pentium-Classic kernel-pcmcia-modules-2.4.27-2-686 - Mainstream PCMCIA modules 2.4.27 on PPro/Celeron/PII/PIII/P4 kernel-pcmcia-modules-2.4.27-2-686-smp - Mainstream PCMCIA modules 2.4.27 on PPro/Celeron/PII/PIII/P4 SMP kernel-pcmcia-modules-2.4.27-2-k6 - Mainstream PCMCIA modules 2.4.27 on AMD K6/K6-II/K6-III kernel-pcmcia-modules-2.4.27-2-k7 - Mainstream PCMCIA modules 2.4.27 on AMD K7 kernel-pcmcia-modules-2.4.27-2-k7-smp - Mainstream PCMCIA modules 2.4.27 on AMD K7 SMP Changes: kernel-image-2.4.27-i386 (2.4.27-10) unstable urgency=low . * Build against kernel-tree-2.4.27-10. (Simon Horman) Files: cd96f16ed1fe14800c6a0764ded908fd 1563 devel optional kernel-image-2.4.27-i386_2.4.27-10.dsc cbcf00a55b4c86e380d884e424fd7ad0 97254 devel optional kernel-image-2.4.27-i386_2.4.27-10.tar.gz 4537c2b63f04b64d90f8b9ec5259effd 1823142 devel optional kernel-headers-2.4.27-2_2.4.27-10_i386.deb 8fcf336a5538ca03638d9ad8ecb144ce 292446 base optional kernel-pcmcia-modules-2.4.27-2-586tsc_2.4.27-10_i386.deb 4959c0b8299d82dc204cf1161dbc2d77 297840 devel optional kernel-headers-2.4.27-2-586tsc_2.4.27-10_i386.deb defe6178a7c0454bb257117a66c4fef9 12024598 base optional kernel-image-2.4.27-2-586tsc_2.4.27-10_i386.deb b5996a449499c6b779027c3de31c10d0 267550 base optional kernel-pcmcia-modules-2.4.27-2-386_2.4.27-10_i386.deb 9fb7b5bda639c921769971e3f5b82b7a 297002 devel optional kernel-headers-2.4.27-2-386_2.4.27-10_i386.deb 877b54a0fe8d17818b93ad283da85a22 11044716 base optional kernel-image-2.4.27-2-386_2.4.27-10_i386.deb 1f7ea3287d751e5ceffde5da79b69c87 303814 base optional kernel-pcmcia-modules-2.4.27-2-686-smp_2.4.27-10_i386.deb f44389653f979d56c08a8c29a6778fae 299860 devel optional kernel-headers-2.4.27-2-686-smp_2.4.27-10_i386.deb 2460587838835a31fe9777b5a0836236 12678402 base optional kernel-image-2.4.27-2-686-smp_2.4.27-10_i386.deb 58fcc619f1796c29e60f51343a5be55d 298226 base optional kernel-pcmcia-modules-2.4.27-2-686_2.4.27-10_i386.deb 36ab0e79044cc5767e0fb10885bf85f5 298008 devel optional kernel-headers-2.4.27-2-686_2.4.27-10_i386.deb 7cfb4ddcf49433e55a53fae4d9a3c636 12335804 base optional kernel-image-2.4.27-2-686_2.4.27-10_i386.deb 045dd64b1f73a09434601c79c416738f 286214 base optional kernel-pcmcia-modules-2.4.27-2-k6_2.4.27-10_i386.deb fc2648e920e0ae58a0fa79355640ef3b 297054 devel optional kernel-headers-2.4.27-2-k6_2.4.27-10_i386.deb da11488dace21a288798633f4586cebb 11707764 base optional
Accepted kernel-patch-powerpc-2.4.27 2.4.27-10 (powerpc source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 10 May 2005 19:30:02 +0900 Source: kernel-patch-powerpc-2.4.27 Binary: kernel-patch-2.4.27-powerpc kernel-build-2.4.27-nubus kernel-image-2.4.27-nubus kernel-headers-2.4.27-powerpc kernel-image-2.4.27-powerpc kernel-patch-2.4.27-apus kernel-build-2.4.27-apus kernel-headers-2.4.27-nubus kernel-image-2.4.27-powerpc-small kernel-build-2.4.27-powerpc-smp kernel-image-2.4.27-powerpc-smp kernel-image-2.4.27-apus kernel-patch-2.4.27-nubus kernel-headers-2.4.27-apus kernel-build-2.4.27-powerpc kernel-build-2.4.27-powerpc-small Architecture: source powerpc Version: 2.4.27-10 Distribution: unstable Urgency: low Maintainer: Debian Kernel Team debian-kernel@lists.debian.org Changed-By: Simon Horman [EMAIL PROTECTED] Description: kernel-build-2.4.27-apus - build infrastructure for kernel version 2.4.27-apus kernel-build-2.4.27-nubus - build infrastructure for kernel version 2.4.27-nubus kernel-build-2.4.27-powerpc - build infrastructure for kernel version 2.4.27-powerpc kernel-build-2.4.27-powerpc-small - build infrastructure for kernel version 2.4.27-powerpc-small kernel-build-2.4.27-powerpc-smp - build infrastructure for kernel version 2.4.27-powerpc-smp kernel-headers-2.4.27-apus - Linux/APUS kernel headers. kernel-headers-2.4.27-nubus - Linux/nubus kernel headers. kernel-headers-2.4.27-powerpc - Linux/nubus kernel headers. kernel-image-2.4.27-apus - Linux/APUS kernel binary image. kernel-image-2.4.27-nubus - Linux/nubus kernel binary image. kernel-image-2.4.27-powerpc - Linux/PowerPC kernel binary image for the powerpc flavour kernel-image-2.4.27-powerpc-small - Linux/PowerPC kernel binary image for the powerpc-small flavour kernel-image-2.4.27-powerpc-smp - Linux/PowerPC kernel binary image for the powerpc-smp flavour kernel-patch-2.4.27-apus - Diffs to the kernel source for APUS kernel-patch-2.4.27-nubus - Diffs to the kernel source for nubus kernel-patch-2.4.27-powerpc - Diffs to the kernel source for nubus Changes: kernel-patch-powerpc-2.4.27 (2.4.27-10) unstable; urgency=low . * Build against kernel-source 2.4.27-10 (Simon Horman) * Changed the uploader to myself. (Simon Horman) Files: e3a35df4d3484186555a9acb6d440c1f devel optional kernel-patch-powerpc-2.4.27_2.4.27-10.dsc 5adc45b3409e26af4fc8777f6eee071b 1462324 devel optional kernel-patch-powerpc-2.4.27_2.4.27-10.tar.gz 709249532e2040874c6fd4133742c02c 65312 devel optional kernel-patch-2.4.27-apus_2.4.27-10_powerpc.deb f033509703190c3213c74ac02438bce2 4681674 devel optional kernel-headers-2.4.27-apus_2.4.27-10_powerpc.deb 99967fead5bae26ffda484f83779542c 2493976 base optional kernel-image-2.4.27-apus_2.4.27-10_powerpc.deb edd2a1eea5d8ee6c86217bb5fd752b8a 136870 devel optional kernel-build-2.4.27-apus_2.4.27-10_powerpc.deb c5a68081bdaa1e0513c70399e83e5242 8656 devel optional kernel-patch-2.4.27-nubus_2.4.27-10_powerpc.deb 082458dd7782b7e62cf565e773c1aff4 4691818 devel optional kernel-headers-2.4.27-nubus_2.4.27-10_powerpc.deb 351c1fa839a1856d2e43b35c36081bc6 1812510 base optional kernel-image-2.4.27-nubus_2.4.27-10_powerpc.deb d90c707cfadb6925eb6355cbd9152723 136694 devel optional kernel-build-2.4.27-nubus_2.4.27-10_powerpc.deb 69e74703f60c168028f6ed8ed7fd1b02 8580 devel optional kernel-patch-2.4.27-powerpc_2.4.27-10_powerpc.deb f9d1b2aa8d2c153386dc8c20efb42e3b 4799462 devel optional kernel-headers-2.4.27-powerpc_2.4.27-10_powerpc.deb db1a6696d2150e3995a03d031a94d756 13472248 base optional kernel-image-2.4.27-powerpc_2.4.27-10_powerpc.deb 5b0dfefcc2396a55e5c6f607cca1c742 150712 devel optional kernel-build-2.4.27-powerpc_2.4.27-10_powerpc.deb 1689909b9f0bb2d256b7c6e69b4e13c0 13778400 base optional kernel-image-2.4.27-powerpc-smp_2.4.27-10_powerpc.deb d676d5d180980795e1192b637244d5bc 150770 devel optional kernel-build-2.4.27-powerpc-smp_2.4.27-10_powerpc.deb 35ca3d5fd6b440a30b0eda94344dbdf2 12747300 base optional kernel-image-2.4.27-powerpc-small_2.4.27-10_powerpc.deb ebaec167795b3112e08315d566e340f9 151056 devel optional kernel-build-2.4.27-powerpc-small_2.4.27-10_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjGcwdu+M6Iexz7URAgnRAJ9EGArN8fHcW0nCx4t127IbXNJaQgCfU3a6 zGMaGk4PxXm/QqrywLN6wqg= =ufY7 -END PGP SIGNATURE- Accepted: kernel-build-2.4.27-apus_2.4.27-10_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-apus_2.4.27-10_powerpc.deb kernel-build-2.4.27-nubus_2.4.27-10_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-nubus_2.4.27-10_powerpc.deb kernel-build-2.4.27-powerpc-small_2.4.27-10_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc-small_2.4.27-10_powerpc.deb kernel-build-2.4.27-powerpc-smp_2.4.27-10_powerpc.deb to pool/main/k/kernel-patch-powerpc-2.4.27/kernel-build-2.4.27-powerpc-smp_2.4.27-10_powerpc.deb kernel-build-2.4.27-powerpc_2.4.27-10_powerpc.deb to
Accepted dictionaries-common 0.25.12 (all source)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 19 May 2005 12:19:25 +0200
Source: dictionaries-common
Binary: dictionaries-common-dev dictionaries-common
Architecture: source all
Version: 0.25.12
Distribution: unstable
Urgency: high
Maintainer: Agustin Martin Domingo [EMAIL PROTECTED]
Changed-By: Agustin Martin Domingo [EMAIL PROTECTED]
Description:
dictionaries-common - Common utilities for spelling dictionary tools
dictionaries-common-dev - Developer tools and Policy for spelling dictionary
tools
Changes:
dictionaries-common (0.25.12) unstable; urgency=high
.
* debian/po/{fi,it,pl}.po
- Fixed some incorrect variable substitutions. Thanks to
Evguenyi Mescheriakov for his check_var.pl script and
to Christian Perrier, who pointed me to it.
* Urgency set to high, so the pass to sarge is faster if approved.
Files:
596ee7a0d72e74e78be59d9dfa2cee41 735 text standard
dictionaries-common_0.25.12.dsc
38cd1543f128534c304d9867b9bd4317 219413 text standard
dictionaries-common_0.25.12.tar.gz
314542eac18b7dc3025a5d2f548104ef 198930 text standard
dictionaries-common_0.25.12_all.deb
e9ffbbb58fa512c867751a7bed9c6bef 93582 text optional
dictionaries-common-dev_0.25.12_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCjGjZWMZwCEWXpZMRAtU/AJ9dHjYvlmdda687EG+wekq1HabkZwCdHheW
Kx/PHy3H4ux1swPYS6RQgmg=
=/jAc
-END PGP SIGNATURE-
Accepted:
dictionaries-common-dev_0.25.12_all.deb
to pool/main/d/dictionaries-common/dictionaries-common-dev_0.25.12_all.deb
dictionaries-common_0.25.12.dsc
to pool/main/d/dictionaries-common/dictionaries-common_0.25.12.dsc
dictionaries-common_0.25.12.tar.gz
to pool/main/d/dictionaries-common/dictionaries-common_0.25.12.tar.gz
dictionaries-common_0.25.12_all.deb
to pool/main/d/dictionaries-common/dictionaries-common_0.25.12_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kernel-source-2.6.8 2.6.8-16 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 16:51:34 +0900 Source: kernel-source-2.6.8 Binary: kernel-source-2.6.8 kernel-doc-2.6.8 kernel-tree-2.6.8 kernel-patch-debian-2.6.8 Architecture: source all Version: 2.6.8-16 Distribution: unstable Urgency: low Maintainer: Debian kernel team debian-kernel@lists.debian.org Changed-By: Simon Horman [EMAIL PROTECTED] Description: kernel-doc-2.6.8 - Linux kernel specific documentation for version 2.6.8 kernel-patch-debian-2.6.8 - Debian patches to Linux 2.6.8 kernel-source-2.6.8 - Linux kernel source for version 2.6.8 with Debian patches kernel-tree-2.6.8 - Linux kernel source tree for building Debian kernel images Closes: 272683 295725 300163 301372 301488 301528 301799 301799 301799 301799 302352 303140 303498 304548 307552 308034 308634 308724 308855 309429 Changes: kernel-source-2.6.8 (2.6.8-16) unstable; urgency=low . * smbfs-overrun.dpatch: Reinstated smbfs-overrun.dpatch to complete fix for CAN-2004-1191 (Simon Horman) (closes: #300163) . * radeon-race-2.dpatch: Symbol fix for radeon race fix in 2.6.8-15. (Simon Horman) (closes: #301488, #301528, #308034) . * drivers-input-serio-nmouse.dpatch: [Security] fix N_MOUSE TTY privelage problem. See CAN-2005-0839 (Simon Horman) (closes: #301372) . * net-bluetooth-signdness-fix.dpatch: [Security] Fix signedness problem at socket creation in bluetooth which can lead to local root exploit. See CAN-2005-0750 (Simon Horman) (closes: #301799) . * fs-ext2-info-leak.dpatch: [Security] Fix information leak in ext2 which leads to a local information leak. See CAN-2005-0400 (Simon Horman) (closes: #301799) . * fs-isofs-range-check-1.dpatch, fs-isofs-range-check-2.dpatch, fs-isofs-range-check-3.dpatch: [Security] Fix range checking in isofs which leads to a local crash and arbitary code execution. See CAN-2005-0815 (Simon Horman) (closes: #301799) . * mm-shmem-truncate.dpatch [Security] tmpfs caused truncate bug which leads to a local dos. CVE yet to be assigned. (Simon Horman) . * fs-binfmt_elf-dos.dpatch: Potential DOS in load_elf_library. See CAN-2005-0749 (Simon Horman) (closes: #301799, #303498) . * arch-ppc64-hugepage-aio-panic.dpatch: fix AIO panic on PPC64 caused by is_hugepage_only_range(). See CAN-2005-0916. (Simon Horman) (closes: #302352) . * kernel-futex-deadlock.dpatch: Fix possible deadlog in fitex mmap_sem. See CAN-2005-0937 (closes: #303140) (Simon Horman) . * net-ipv4-bic-binary-search.patch: Fix BIC congestion avoidance algorithm error (Simon Horman) . * net-ipv4-ipsec-icmp-deadlock.patch: Fix IPSEC ICMP deadlock (Simon Horman) . * drivers-media-video-saa7110-oops.patch: Fix saa7110 driver to handle I2C_FUNC_I2C support correctly, prefiously it would oops. (Simon Horman) . * fs-cramfs-stat.dpatch: Fix bogus blocks field for devices in cramfs. (Simon Horman) . * drivers-media-video-i2c-msg.dpatch: Fix i2c message flags in video drivers (Simon Horman) . * drivers-net-sis900-oops.dpatch: Fix oops in sis900 driver caused by it being preemted before it has finished setting sis_priv-mii (Simon Horman) . * drivers-net-via-rhine-wol-oops.dpatch: Fix oops in VIA Rhine driver caused by assuming all cards have WOL support. (Simon Horman) . * net-netrom-double-lock.dpatch: Fix dealock in netrom caused by double locking. (Simon Horman) . * drivers-net-amd811e-irq.dpatch: Fix bug in AMD8111e driver where it neglects to release an irq on some error conditions. (Simon Horman) . * net-xfrm-find_acq_byseq.dpatch: Fix __xfrm_find_acq_byseq() so it only returns objects in the XFRM_STATE_ACQ state. (Simon Horman) . * drivers-net-via-rhine-irq.dpatch: VIA Rhine driver was releasing an irq in some error situations (Simon Horman) . * sound-core-timer-oops.dpatch: Fix ALSA timer notification. o Ooops in read() o wake-up polls and signals with new events (Simon Horman) . * fs-jdb-race.dpatch: Fix race in JDB (Simon Horman) . * arch-ia64-syscall-audit.dpatch: Fix ia64 syscall auditing (Simon Horman) . * drivers-i2c-chips-eprom.dpatch: Fix oops in eprom driver that occrs when data is read from sysfs (Simon Horman) . * lib-rwsem-spinlock.dpatch: Fix dealock that occurs dio_complete() does up_read() from IRQ context by using interupd disabling spin locks. (Simon Horman) . * fs-jdb-slow-leak.dpatch: Fix longstanding jdb commit leak - since 2.6.6. (Maximilian Attems) . * sparc64-sigpoll-2.6.8.dpatch: Separate __SI_FAULT and __SI_POLL branches in copy_siginfo_to_user32() to resolve fcntl() bug. (Jurij Smakov, Simon Horman) (closes: #272683) . *
Accepted autossh 1.2g-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 14:41:12 +0200 Source: autossh Binary: autossh Architecture: source i386 Version: 1.2g-2 Distribution: unstable Urgency: low Maintainer: Filippo Giunchedi [EMAIL PROTECTED] Changed-By: Filippo Giunchedi [EMAIL PROTECTED] Description: autossh- Automatically restart SSH sessions and tunnels Closes: 309744 Changes: autossh (1.2g-2) unstable; urgency=low . * fixes important bug when AUTOSSH_PORT=0 (Closes: #309744) * do not strip f from arguments passed to ssh (backported from autossh 1.3) Files: cf6b302f6c986010ab1bef368130b462 607 net optional autossh_1.2g-2.dsc f89429a0abbf065248b5ec6a82f1e45c 4893 net optional autossh_1.2g-2.diff.gz 27d60b1947dce96c971fdab4c2583fa0 20954 net optional autossh_1.2g-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCjInLABzeamt51AERAsFFAJ0ZWezmA4E1Ei/59lctyTloFnX46gCg0acG iPH3D84TprAB5aBCP/QJsw4= =R3WI -END PGP SIGNATURE- Accepted: autossh_1.2g-2.diff.gz to pool/main/a/autossh/autossh_1.2g-2.diff.gz autossh_1.2g-2.dsc to pool/main/a/autossh/autossh_1.2g-2.dsc autossh_1.2g-2_i386.deb to pool/main/a/autossh/autossh_1.2g-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ifrench 1.4-20 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 May 2005 23:14:03 +0200 Source: ifrench Binary: ifrench myspell-fr Architecture: source i386 all Version: 1.4-20 Distribution: unstable Urgency: low Maintainer: Nicolas Sabouret [EMAIL PROTECTED] Changed-By: Nicolas Sabouret [EMAIL PROTECTED] Description: ifrench- The French dictionary for ispell (Hydro-Quebec version) myspell-fr - The French dictionary for myspell (Hydro-Quebec version) Closes: 308772 Changes: ifrench (1.4-20) unstable; urgency=low . * Changed priority to optional * Fix affix files (closes: #308772) * Rebuild francais.dico Files: a61fe63187ce8320626a8a0fce66d69d 630 text - ifrench_1.4-20.dsc 5c34f4f6f00f336aafd68e682ca2e17b 282427 text - ifrench_1.4-20.diff.gz d0bb196aa2327a65631ab8979221a4ff 424694 text extra ifrench_1.4-20_i386.deb 3453f6537a67a7600f39a15684f85e3f 160650 text extra myspell-fr_1.4-20_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCjJNA3WMCWcJOg8IRAnaoAKDU0gH40MQ2q8CPKDpzxZxbEjzf5gCfWv2e HtVBTrDCeE1yiFYXcSRgiOo= =6QJ0 -END PGP SIGNATURE- Accepted: ifrench_1.4-20.diff.gz to pool/main/i/ifrench/ifrench_1.4-20.diff.gz ifrench_1.4-20.dsc to pool/main/i/ifrench/ifrench_1.4-20.dsc ifrench_1.4-20_i386.deb to pool/main/i/ifrench/ifrench_1.4-20_i386.deb myspell-fr_1.4-20_all.deb to pool/main/i/ifrench/myspell-fr_1.4-20_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ifrench-gut 1:1.0-18 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 14 May 2005 22:51:48 +0200 Source: ifrench-gut Binary: ifrench-gut myspell-fr-gut Architecture: source i386 all Version: 1:1.0-18 Distribution: unstable Urgency: low Maintainer: Nicolas Sabouret [EMAIL PROTECTED] Changed-By: Nicolas Sabouret [EMAIL PROTECTED] Description: ifrench-gut - The French dictionary for ispell (GUTenberg version) myspell-fr-gut - The French dictionary for myspell (GUTenberg version) Closes: 283672 308858 Changes: ifrench-gut (1:1.0-18) unstable; urgency=low . * Changed priority to optional * Fix affix files (closes: #283672, #308858) Thanks to Guillaume Pernot for his patch Files: 3968f2ba66bd234a6c72a39c3c0df14b 653 text optional ifrench-gut_1.0-18.dsc 6e8b4818ae4baf6c208fcf6e15280954 12729 text optional ifrench-gut_1.0-18.diff.gz b34e343578695a9dc804ba33f259b042 1978522 text optional ifrench-gut_1.0-18_i386.deb a89c041e0737abdba7d9469016208435 310540 text optional myspell-fr-gut_1.0-18_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCjJYs3WMCWcJOg8IRAvMuAJ96F7Lw6aC+F9/+CluwVrM3pehGAgCguwaR ugf5B289h/X9wXnKQoysXCw= =W2WY -END PGP SIGNATURE- Accepted: ifrench-gut_1.0-18.diff.gz to pool/main/i/ifrench-gut/ifrench-gut_1.0-18.diff.gz ifrench-gut_1.0-18.dsc to pool/main/i/ifrench-gut/ifrench-gut_1.0-18.dsc ifrench-gut_1.0-18_i386.deb to pool/main/i/ifrench-gut/ifrench-gut_1.0-18_i386.deb myspell-fr-gut_1.0-18_all.deb to pool/main/i/ifrench-gut/myspell-fr-gut_1.0-18_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fai 2.8.3 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 15:54:18 +0200 Source: fai Binary: fai Architecture: source all Version: 2.8.3 Distribution: unstable Urgency: high Maintainer: Thomas Lange [EMAIL PROTECTED] Changed-By: Thomas Lange [EMAIL PROTECTED] Description: fai- Fully Automatic Installation Closes: 309134 309138 309142 309209 309556 309707 Changes: fai (2.8.3) unstable; urgency=high . * fix a serious bug, remove debconf support (closes: #309209), debconf support may be included again after sarge * fix important bug, do not delete files in /etc/fai (closes: #309707) * control: remove dependency on debconf * postinst, postrm: remove debconf code * rules: do not call dh_installdebconf * remove debian/config, debian/template * remove files in debian/po: POTFILES.in de.po fr.po templates.pot * fai.conf: set placeholder for installserver, since debconf will not set it any more * conf/make-fai-nfsroot.conf, conf/sources.list: use ftp.debian.org instead of debconf's default values * man/fai-chboot.8: minor document patch (closes: #309138, 309142) * fai-guide.sgml: minor document patch, move section For the impatient user to the front (closes: #309134, #309556) * README.build-sources: add memo to use -ICVS in the future Files: 04aa38254eee7445938499c797f3165f 524 admin extra fai_2.8.3.dsc 02f514edf5f22ee60e39ef5bc6d83163 194309 admin extra fai_2.8.3.tar.gz 0da192c9f5cfd2284d2b3bc923c50969 596594 admin extra fai_2.8.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCjJum3BPlTqubZv0RApRGAJ9Fky50CSj/r/v9zB78AgrdO2fA0ACfR8oK t6U3PfgFLWytYqnK9XiYM0g= =vy7J -END PGP SIGNATURE- Accepted: fai_2.8.3.dsc to pool/main/f/fai/fai_2.8.3.dsc fai_2.8.3.tar.gz to pool/main/f/fai/fai_2.8.3.tar.gz fai_2.8.3_all.deb to pool/main/f/fai/fai_2.8.3_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tiff 3.7.2-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 05:41:28 -0400 Source: tiff Binary: libtiff-opengl libtiffxx0 libtiff4 libtiff-tools libtiff4-dev Architecture: source i386 Version: 3.7.2-3 Distribution: unstable Urgency: high Maintainer: Jay Berkenbilt [EMAIL PROTECTED] Changed-By: Jay Berkenbilt [EMAIL PROTECTED] Description: libtiff-opengl - TIFF manipulation and conversion tools libtiff-tools - TIFF manipulation and conversion tools libtiff4 - Tag Image File Format (TIFF) library libtiff4-dev - Tag Image File Format library (TIFF), development files libtiffxx0 - Tag Image File Format (TIFF) library -- C++ interface Closes: 309739 Changes: tiff (3.7.2-3) unstable; urgency=high . * Fix for exploitable segmentation fault on files with bad BitsPerSample values. (Closes: #309739) [libtiff/tif_dirread.c, CAN-2005-1544] Thanks to Martin Pitt for the report. Files: 14ed5f799c0d34b3f4d258abb76b448a 735 libs optional tiff_3.7.2-3.dsc 1fc94f29d3a15165419a247d700ccbdd 9149 libs optional tiff_3.7.2-3.diff.gz 1e41dddfdcc5e433282e3594dd7487da 451754 libs optional libtiff4_3.7.2-3_i386.deb eba84b0e5ed28fe006e21966d1617cc5 40262 libs optional libtiffxx0_3.7.2-3_i386.deb 13272b256ec7ab7c7d3db0cbc388cfcf 250716 libdevel optional libtiff4-dev_3.7.2-3_i386.deb 3d369fa5c93aa1e456c1832e7f94eb25 205830 graphics optional libtiff-tools_3.7.2-3_i386.deb 936dddcc6265d3468c14bfbcb4a9b9b6 44828 graphics optional libtiff-opengl_3.7.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjK2REBVk6taI4KcRAuGHAKC9rmUracGLJutKXObvOGWy1cE3oQCgnQi6 uS13arrWpS1oW5y1TjRBTd0= =SR9K -END PGP SIGNATURE- Accepted: libtiff-opengl_3.7.2-3_i386.deb to pool/main/t/tiff/libtiff-opengl_3.7.2-3_i386.deb libtiff-tools_3.7.2-3_i386.deb to pool/main/t/tiff/libtiff-tools_3.7.2-3_i386.deb libtiff4-dev_3.7.2-3_i386.deb to pool/main/t/tiff/libtiff4-dev_3.7.2-3_i386.deb libtiff4_3.7.2-3_i386.deb to pool/main/t/tiff/libtiff4_3.7.2-3_i386.deb libtiffxx0_3.7.2-3_i386.deb to pool/main/t/tiff/libtiffxx0_3.7.2-3_i386.deb tiff_3.7.2-3.diff.gz to pool/main/t/tiff/tiff_3.7.2-3.diff.gz tiff_3.7.2-3.dsc to pool/main/t/tiff/tiff_3.7.2-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kino 0.76-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 16:54:18 +0200 Source: kino Binary: kino Architecture: source i386 Version: 0.76-1 Distribution: experimental Urgency: low Maintainer: Daniel Kobras [EMAIL PROTECTED] Changed-By: Daniel Kobras [EMAIL PROTECTED] Description: kino - Non-linear editor for Digital Video data Closes: 226549 308669 Changes: kino (0.76-1) experimental; urgency=low . * New upstream version (aka 0.7.6). + Properly tags exported divx files. Closes: #308669 + Fixes remaining oddities in directory handling of the file chooser. Closes: #226549 * Updated patches: + [10_desktop_fix] Rediffed. * Removed patches: + [10_fix_dvcapture_device] + [10_gtype_fix] + [10_jogshuttle_memhog_workaround] + [20_64bit_cast_fix] + [20_endian_types] + [30_wav_endian_fixes] + [40_gcc40_fixes] + [40_yuvdisplay_endian_fixes] Merged upstream. Files: 4a004079a953f420706389ad21aa3b4b 845 graphics extra kino_0.76-1.dsc c1fa929096f5a754455f5a3dd33dd203 1089097 graphics extra kino_0.76.orig.tar.gz 3b037d1c0d44a5122fb607afd82c9453 12294 graphics extra kino_0.76-1.diff.gz 54f839fc91c6bc5f47dd8af9014321ef 1579700 graphics extra kino_0.76-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjLaspOKIA4m/fisRAmXWAKC55KunQ5nMPlSNigi4T8kiiUWLgACgg+/7 ugoyOB+ME6Mlvtq1JDZbb94= =RMP7 -END PGP SIGNATURE- Accepted: kino_0.76-1.diff.gz to pool/main/k/kino/kino_0.76-1.diff.gz kino_0.76-1.dsc to pool/main/k/kino/kino_0.76-1.dsc kino_0.76-1_i386.deb to pool/main/k/kino/kino_0.76-1_i386.deb kino_0.76.orig.tar.gz to pool/main/k/kino/kino_0.76.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libapache-configfile-perl 1.18-4 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 10:56:04 -0500 Source: libapache-configfile-perl Binary: libapache-configfile-perl Architecture: source all Version: 1.18-4 Distribution: unstable Urgency: low Maintainer: Debian Perl Group [EMAIL PROTECTED] Changed-By: Gunnar Wolf [EMAIL PROTECTED] Description: libapache-configfile-perl - Parse an Apache style httpd.conf configuration file Closes: 309721 Changes: libapache-configfile-perl (1.18-4) unstable; urgency=low . * Fixed: Handles lines broken by backslashes correctly. (Closes: #309721) Files: 11ea3a8914ffa7da50872eedef69d14e 728 perl optional libapache-configfile-perl_1.18-4.dsc 8d06b97ec0240de686eef701c713b92f 3285 perl optional libapache-configfile-perl_1.18-4.diff.gz 36f311ab0c574e0be9699d7146656a8d 33320 perl optional libapache-configfile-perl_1.18-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjLi62A7zWou1J68RApokAJ9Qe3oslV/h7cMM1pS/lmPJdUrrPwCfc8w7 1Ok7+4eOBuk0qclhG2kx9Co= =yO/J -END PGP SIGNATURE- Accepted: libapache-configfile-perl_1.18-4.diff.gz to pool/main/liba/libapache-configfile-perl/libapache-configfile-perl_1.18-4.diff.gz libapache-configfile-perl_1.18-4.dsc to pool/main/liba/libapache-configfile-perl/libapache-configfile-perl_1.18-4.dsc libapache-configfile-perl_1.18-4_all.deb to pool/main/liba/libapache-configfile-perl/libapache-configfile-perl_1.18-4_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted synaptic 0.55+cvs20050503-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 16:48:43 +0200 Source: synaptic Binary: synaptic Architecture: source i386 Version: 0.55+cvs20050503-4 Distribution: unstable Urgency: high Maintainer: Michael Vogt [EMAIL PROTECTED] Changed-By: Michael Vogt [EMAIL PROTECTED] Description: synaptic - Graphical package manager Closes: 309716 Changes: synaptic (0.55+cvs20050503-4) unstable; urgency=high . * updated the brasilian (pt_BR) translation (closes: #309716) * Urgency set to high so that this change can make it into Sarge. No other changes. Files: 4a78976cd22744f338b3b3cdf9c5ea13 780 admin optional synaptic_0.55+cvs20050503-4.dsc ae6dd2a79721a522159cca44291e1273 55628 admin optional synaptic_0.55+cvs20050503-4.diff.gz abc73c2be253eaf4f32a94d0ac2d1ffe 1689666 admin optional synaptic_0.55+cvs20050503-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCjK3xliSD4VZixzQRAqEYAJ0ZbbIJ/tOES1L6RoUa9Z0iH5xeVgCfbMrs T50Bwq1ylv04oEUFobZEYVM= =Wyh/ -END PGP SIGNATURE- Accepted: synaptic_0.55+cvs20050503-4.diff.gz to pool/main/s/synaptic/synaptic_0.55+cvs20050503-4.diff.gz synaptic_0.55+cvs20050503-4.dsc to pool/main/s/synaptic/synaptic_0.55+cvs20050503-4.dsc synaptic_0.55+cvs20050503-4_i386.deb to pool/main/s/synaptic/synaptic_0.55+cvs20050503-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ocaml-tools 2005.29.04-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 18:45:13 +0200 Source: ocaml-tools Binary: ocaml-tools Architecture: source all Version: 2005.29.04-2 Distribution: unstable Urgency: low Maintainer: Debian OCaml Maintainers debian-ocaml-maint@lists.debian.org Changed-By: Samuel Mimram [EMAIL PROTECTED] Description: ocaml-tools - various tools for ocaml programmers Closes: 309743 Changes: ocaml-tools (2005.29.04-2) unstable; urgency=low . * Added a french translation of the debconf messages (thanks Steve), closes: #309743. Files: cea0fb9dc58badf7379a24fcac09bb46 839 devel optional ocaml-tools_2005.29.04-2.dsc bc49a2e2d93aa85af976b1b0334054f3 6698 devel optional ocaml-tools_2005.29.04-2.diff.gz dad8c90a166dbd8ef381cec8405bbfe9 74302 devel optional ocaml-tools_2005.29.04-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjMUKIae1O4AJae8RAneKAJ9OWG8tYeAtjnvlqMnhh04weMsbcgCdHw7o qEFaTTu+5wRd60S8d/jf3Io= =hBk1 -END PGP SIGNATURE- Accepted: ocaml-tools_2005.29.04-2.diff.gz to pool/main/o/ocaml-tools/ocaml-tools_2005.29.04-2.diff.gz ocaml-tools_2005.29.04-2.dsc to pool/main/o/ocaml-tools/ocaml-tools_2005.29.04-2.dsc ocaml-tools_2005.29.04-2_all.deb to pool/main/o/ocaml-tools/ocaml-tools_2005.29.04-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apt-proxy 1.9.30 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 17:28:33 +0100 Source: apt-proxy Binary: apt-proxy Architecture: source all Version: 1.9.30 Distribution: unstable Urgency: high Maintainer: Otavio Salvador [EMAIL PROTECTED] Changed-By: Chris Halls [EMAIL PROTECTED] Description: apt-proxy - Debian archive proxy and partial mirror builder development Closes: 277916 285792 305015 Changes: apt-proxy (1.9.30) unstable; urgency=high . * Back out all changes in 1.9.29 except for the fix for #304182, the RC bug that caused apt-proxy to be removed from Sarge * Re-enable gunzip postprocessing for Packages, needed for packages database to work properly. This code was commented out in 1.9.23 because I thought it was related to another problem. Closes: #277916: /usr/sbin/apt-proxy-import: apt-proxy-import doesn't work- no suitable backend found Closes: #285792: apt-proxy-import does not work Closes: #305015: max_versions not respected - keeps many versions more than defined there Files: 2c4d7261223824052565bf397c7b8092 638 admin extra apt-proxy_1.9.30.dsc 52b6a1ffd6d8501ceb22c5a42bbb85ff 65087 admin extra apt-proxy_1.9.30.tar.gz 966ac906f26f0def18df8d40b4deedd2 60596 admin extra apt-proxy_1.9.30_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCjMTPexmdExmX588RAqxRAJ9zDlIqf3Gzb1vBmZfrSzzMli3i0gCgghTc veRNOmKC4mo6BCrTp6QviPg= =I55C -END PGP SIGNATURE- Accepted: apt-proxy_1.9.30.dsc to pool/main/a/apt-proxy/apt-proxy_1.9.30.dsc apt-proxy_1.9.30.tar.gz to pool/main/a/apt-proxy/apt-proxy_1.9.30.tar.gz apt-proxy_1.9.30_all.deb to pool/main/a/apt-proxy/apt-proxy_1.9.30_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted watchdog 5.2.4-4 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 19:03:38 +0200 Source: watchdog Binary: watchdog Architecture: source i386 Version: 5.2.4-4 Distribution: unstable Urgency: medium Maintainer: Michael Meskes [EMAIL PROTECTED] Changed-By: Michael Meskes [EMAIL PROTECTED] Description: watchdog - software watchdog Changes: watchdog (5.2.4-4) unstable; urgency=medium . * Check for local changes to startup links before changing them Files: 54942f0c1067052a7ca211cdaf9d9cb7 567 admin extra watchdog_5.2.4-4.dsc 3bf945de408903ce7c33c678fac040e5 14234 admin extra watchdog_5.2.4-4.diff.gz 04e3a8392643640a296f25d8464a0425 57796 admin extra watchdog_5.2.4-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjM3/VkEm8inxm9ERArxXAJ0UDzog21/hjA4UnS9zdEOgPl1CeACgiReu k4if5397SNUaPQsy9dikpzk= =xE2p -END PGP SIGNATURE- Accepted: watchdog_5.2.4-4.diff.gz to pool/main/w/watchdog/watchdog_5.2.4-4.diff.gz watchdog_5.2.4-4.dsc to pool/main/w/watchdog/watchdog_5.2.4-4.dsc watchdog_5.2.4-4_i386.deb to pool/main/w/watchdog/watchdog_5.2.4-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libsdl-erlang 0.94.1025-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 17:18:25 +0100 Source: libsdl-erlang Binary: libsdl-erlang Architecture: source i386 Version: 0.94.1025-1 Distribution: unstable Urgency: low Maintainer: Will Newton [EMAIL PROTECTED] Changed-By: Will Newton [EMAIL PROTECTED] Description: libsdl-erlang - Erlang bindings to the Simple Direct Media Library Changes: libsdl-erlang (0.94.1025-1) unstable; urgency=low . * New maintainer. * New upstream version. * Package removed from sarge. (Closes #305995) * Moved from interpreters to libs section. * Updated standards version. * Removed non-functional postinst and redundant README.Debian. Files: e32ff16080e57278e10f1b1d57538bce 658 libs optional libsdl-erlang_0.94.1025-1.dsc f83e3f4a04c1908d0d62ccd3071fee28 447383 libs optional libsdl-erlang_0.94.1025.orig.tar.gz c3fcf36b43580a0511467996e909fe58 3331 libs optional libsdl-erlang_0.94.1025-1.diff.gz f8d5a3468e48776cdfc0a55ef393794b 964062 libs optional libsdl-erlang_0.94.1025-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjMBLlv9v5CRKz7cRAmCrAJ9RJuG00GB6CDTf0zJpMcpFDPWYKwCfUQmJ bgzQ9klSITbkvh6pCB7k++o= =ZDAE -END PGP SIGNATURE- Accepted: libsdl-erlang_0.94.1025-1.diff.gz to pool/main/libs/libsdl-erlang/libsdl-erlang_0.94.1025-1.diff.gz libsdl-erlang_0.94.1025-1.dsc to pool/main/libs/libsdl-erlang/libsdl-erlang_0.94.1025-1.dsc libsdl-erlang_0.94.1025-1_i386.deb to pool/main/libs/libsdl-erlang/libsdl-erlang_0.94.1025-1_i386.deb libsdl-erlang_0.94.1025.orig.tar.gz to pool/main/libs/libsdl-erlang/libsdl-erlang_0.94.1025.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted dnstop 20050405-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 11 May 2005 14:28:11 +0200 Source: dnstop Binary: dnstop Architecture: source i386 Version: 20050405-1 Distribution: unstable Urgency: low Maintainer: Adriaan Peeters [EMAIL PROTECTED] Changed-By: Adriaan Peeters [EMAIL PROTECTED] Description: dnstop - console tool to analyze DNS traffic Changes: dnstop (20050405-1) unstable; urgency=low . * New upstream release * Updated debian/control to make clear the list of features is just a selection Files: 683667b4364ec524e806474075fa714e 645 net optional dnstop_20050405-1.dsc 408514bc835e8c69fe8e791ab79d3699 11227 net optional dnstop_20050405.orig.tar.gz ac05ad6625c2cb2e4d42bd967f6750a8 2623 net optional dnstop_20050405-1.diff.gz a56350ac880e59a7ee0c81d59e0ee928 14720 net optional dnstop_20050405-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQFCjNVkTrAWvKplQe4RAvXOAJsF3EFXJiT+FwC9p9Erdt/q4pdGUgCfXdpg pmCoxbGoZ6MAx1I74L+B7D8= =ANbg -END PGP SIGNATURE- Accepted: dnstop_20050405-1.diff.gz to pool/main/d/dnstop/dnstop_20050405-1.diff.gz dnstop_20050405-1.dsc to pool/main/d/dnstop/dnstop_20050405-1.dsc dnstop_20050405-1_i386.deb to pool/main/d/dnstop/dnstop_20050405-1_i386.deb dnstop_20050405.orig.tar.gz to pool/main/d/dnstop/dnstop_20050405.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wings3d 0.98.29b-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 17:52:29 +0100 Source: wings3d Binary: wings3d Architecture: source i386 Version: 0.98.29b-1 Distribution: unstable Urgency: low Maintainer: Will Newton [EMAIL PROTECTED] Changed-By: Will Newton [EMAIL PROTECTED] Description: wings3d- Nendo-inspired 3D polygon mesh modeller Closes: 291255 Changes: wings3d (0.98.29b-1) unstable; urgency=low . * New maintainer. * New upstream version. * Remove redundant README.Debian, postinst and preinst. * wings3d and erlang have been removed from sarge. (Closes: #291255) Files: bd7e0184fe4a76be8ac9bb129d1559ee 659 graphics optional wings3d_0.98.29b-1.dsc 0de2ed2ca7aef432d70425b9630a6177 931961 graphics optional wings3d_0.98.29b.orig.tar.gz f1badfa219ebcd13caddad2b0847f980 8164 graphics optional wings3d_0.98.29b-1.diff.gz 5a3b25420b6b838a3db428875d231474 3016984 graphics optional wings3d_0.98.29b-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjM73lv9v5CRKz7cRAtokAJ41xqniPLGnd0JvmAa8G2dVwcAJsQCeKdWa wmQml1iXYeNk2WU70PBijy0= =0Ik6 -END PGP SIGNATURE- Accepted: wings3d_0.98.29b-1.diff.gz to pool/main/w/wings3d/wings3d_0.98.29b-1.diff.gz wings3d_0.98.29b-1.dsc to pool/main/w/wings3d/wings3d_0.98.29b-1.dsc wings3d_0.98.29b-1_i386.deb to pool/main/w/wings3d/wings3d_0.98.29b-1_i386.deb wings3d_0.98.29b.orig.tar.gz to pool/main/w/wings3d/wings3d_0.98.29b.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bridge-utils 1.0.6-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 19 May 2005 18:44:06 +0200 Source: bridge-utils Binary: bridge-utils Architecture: source i386 Version: 1.0.6-1 Distribution: unstable Urgency: low Maintainer: Santiago García Mantiñán [EMAIL PROTECTED] Changed-By: Santiago García Mantiñán [EMAIL PROTECTED] Description: bridge-utils - Utilities for configuring the Linux ethernet bridge Closes: 296881 302521 Changes: bridge-utils (1.0.6-1) unstable; urgency=low . * The Sorry it took so long release (AKA I've missed sarge). Yes, that's the real me (in UTF). * New upstream version. * Call vlan on post-down so that vlan interfaces get removed. * Take down bridge interfaces before deleting bridge, also reorder the instructions in post-down (thanks to Loïc Minier). Closes: #302521. * Fix little doc bug. Closes: #296881. Files: a96770f592092e85feecf1122b0228a0 606 net optional bridge-utils_1.0.6-1.dsc e02b1df90bc60d0729bc6d1788b61c33 81567 net optional bridge-utils_1.0.6.orig.tar.gz 0f7641560696f5e826373ce2892cd101 8964 net optional bridge-utils_1.0.6-1.diff.gz 855d4ea216302cf7b67945380cf687e2 27318 net optional bridge-utils_1.0.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFCjN32cv3CBfajKo4RAoMsAJ0XoAUqAPJSYvrbnRPCXepPa1zjlgCePObK e4dCPh1zXl5TJI7dLKFxHT8= =hrBn -END PGP SIGNATURE- Accepted: bridge-utils_1.0.6-1.diff.gz to pool/main/b/bridge-utils/bridge-utils_1.0.6-1.diff.gz bridge-utils_1.0.6-1.dsc to pool/main/b/bridge-utils/bridge-utils_1.0.6-1.dsc bridge-utils_1.0.6-1_i386.deb to pool/main/b/bridge-utils/bridge-utils_1.0.6-1_i386.deb bridge-utils_1.0.6.orig.tar.gz to pool/main/b/bridge-utils/bridge-utils_1.0.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
