Release-critical Bugreport for December 12, 2003
Bug stamp-out list for Dec 12 06:01 (CST) Total number of release-critical bugs: 689 Number that will disappear after removing packages marked [REMOVE]: 44 Number that have a patch: 106 Number that have a fix prepared and waiting to upload: 32 Number that are being ignored: 17 Number on packages not in testing: 170 Explanation for bug tags: P pending + patch H help M moreinfo R unreproducible S security U upstream I sarge-ignore Some bugs have an additional set of tags indicating they only apply to a particular release: O for oldstable (potato), S for stable (woody), T for testing (sarge) or U for unstable (sid). X indicates that the package is not in testing. -- Package: a2ps (debian/main) Maintainer: Masayuki Hatta [EMAIL PROTECTED] 215357 [ + ] a2ps: contains /usr/share/info/dir.gz Package: abiword (debian/main) Maintainer: Masayuki Hatta [EMAIL PROTECTED] 223606 [] [X] abiword: FTBFS on mips Package: abiword-gnome (debian/main) Maintainer: Masayuki Hatta [EMAIL PROTECTED] 221597 [] [X] abiword-gnome: abiword crashes on printing Package: advi (debian/main) Maintainer: Sven Luther [EMAIL PROTECTED] 219545 [] advi: FTBFS: Unsatisfiable Build-Depends Package: aime (debian/main) Maintainer: Ed Boraas [EMAIL PROTECTED] 172566 [] [X] aime: fills up /var diskspace until it is overflowing Package: alsa-base (debian/main) Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] 221038 [P ] postinst should not break on init script restart Package: amavis-ng (debian/main) Maintainer: Hilko Bengen [EMAIL PROTECTED] 219044 [ M] amavis-ng: Postfix module deletes all mail 223774 [] amavis-ng: amavis-ng breaks mail delivery Package: antlr (debian/main) Maintainer: John Leuner [EMAIL PROTECTED] 223143 [] [X] antlr doesn't build on arm Package: apache2 (debian/main) Maintainer: Debian Apache Maintainers debian-apache@lists.debian.org 222551 [] violates policy 11.5.2, access to HTML documents 222552 [] violates policy 11.5.3, Web Document Root 223417 [] cannot purge any of the various models of Apache2 Package: apt-build (debian/main) Maintainer: Julien Danjou [EMAIL PROTECTED] 222666 [] apt-build: Fails to install Package: aqsis (debian/main) Maintainer: Will Newton [EMAIL PROTECTED] 176790 [ + ] [X] aqsis_0.7.2-1(mipsel/unstable): configure generated from broken libtool.m4 Package: ari-yahoo (debian/main) Maintainer: Gopal Narayanan [EMAIL PROTECTED] 223615 [] [X] ari-yahoo can't connect. Package: arping (debian/main) Maintainer: Lenart Janos [EMAIL PROTECTED] 219108 [ HM] arping: does not work Package: aspseek (debian/main) Maintainer: Matt Sullivan [EMAIL PROTECTED] 184572 [ + ] [X] c++ transition problems? Package: atari-bootstrap (debian/main) Maintainer: Roman Hodek [EMAIL PROTECTED] 70144 [] atari-bootstrap lacks build dependencies Package: audacity (debian/main) Maintainer: Joshua Haberman [EMAIL PROTECTED] 213193 [P ] audacity: open project causes empty project to be overwritten 223248 [] audacity: segfault when trying to set preferences Package: autoconf (debian/main) Maintainer: Ben Pfaff [EMAIL PROTECTED] 156259 [] [S] db4.0: does not build from source Package: autopartkit (debian/main) Maintainer: Debian Install System Team debian-boot@lists.debian.org 217503 [] [X] Evil autopartkit should _NEVER_ _NEVER_ try to overwrite an unknown partition table Package: awstats (debian/main) Maintainer: Jonas Smedegaard [EMAIL PROTECTED] 222694 [] awstats: keeps its stats in /usr/lib/cgi-bin/ Package: babel (debian/main) Maintainer: Adam C. Powell, IV [EMAIL PROTECTED] 209283 [] babel_0.8.6-3(unstable/sparc): outdated build-depends Package: bcm4400-source (debian/main) Maintainer: martin f. krafft [EMAIL PROTECTED] 223131 [] bcm4400-source: FTBFS: Cannot patch bcm4400.4 Package: bcm5700-source (debian/main) Maintainer: martin f. krafft [EMAIL PROTECTED] 223005 [ + ] bcm5700-source: Confused with bcm4400-source and doesn't build module 223128 [] bcm5700-source: FTBFS: Cannot patch bcm5700.4 Package: bibletime-i18n (debian/main) Maintainer: Daniel Glassey [EMAIL PROTECTED] 223130 [] [X] bibletime-i18n: FTBFS: Missing Build-Depends Package: bogl-bterm (debian/main) Maintainer: Daniel Jacobowitz [EMAIL PROTECTED] 221538 [ + ] bogl-bterm-udeb: var/lib/dpkg/info/bogl-bterm-udeb.md5sums unwanted Package: bookmarks (debian/main) Maintainer: Carlos Laviola [EMAIL PROTECTED] 223129 [] bookmarks: FTBFS: Bad debian/control file Package: busybox-cvs (debian/main) Maintainer: Debian Install System Team debian-boot@lists.debian.org 216528 [ + ] busybox-cvs doesn't build on s390 Package: busybox-cvs-static (debian/main)
debian-installer status report
In case you've not heard of it, debian-installer is the next-generation Debian installation system that is targeted to be the installer for sarge. Its home page: http://www.debian.org/devel/debian-installer This is a periodic status report. The first beta release back on November 9th was rather successful: It showed that d-i does work on a fair number of systems besides the systems of those of us developing it, and indeed that users generally like it and find it easy to use. Thanks partly to better than expected press coverage (two articles about it, mention on slashdot, etc), we gathered a lot of installation reports to help guide us toward the areas that need work. Indeed there are so many installation reports that we have not managed to follow up on them all as of yet, though all have at least been read over and we've identified the biggest problems with beta 1 (of which, see below). This is one area we need more manpower to deal with, since ideally an installation report is followed up on, categorised, and bugs passed on any the appropriate packages while the reporter is still trying to install debian or their install is fresh in their mind. From personal experience, this can be very fruitful, but it can be a fair bit of work. I hope that we can add a few more volenteers to the group who actively work on this; it is a good way to learn about the internals of debian-installer. Interested? Then take a look at http://bugs.debian.org/installation-reports Based on the installation reports we've seen so far, some of the biggest unfixed problems are these: #1 isolinux CDs do not boot on some systems, more than was expected. #2 The behavior of always trying to do DHCP was bad. An updated netcfg is in the works to address this. #3 The partitioner is not quite on a par with the rest of the installer. The forthcoming partman partitioner may address this. #4 Error handling around debootstrap still sucks, problems with debootstrap failing on non-empty partitions are common. #5 More folks have SCSI CD drives than we'd have guessed, and find the need for a driver floppy with such drives annoying. #6 base-config is not very well integrated with the rest of d-i (base-config 2.0 has partially addressed this, but more work needs to be done). Of course our TODO file and bug repoorts attest to lots of smaller or less common problems. Still, we've fixed so many problems since the beta that I cannot keep track of, let alone list them all. A few of the biggest areas fixed in the daily builds include: - problems with dual ethernet cards - keyboard selection problems - floppy boot problems (kernel oops) on some Sony laptops - boots and installs direct from USB keychain now working and documented - problems with using an IDE CD drive on a system with all SCSI disks or the converse - many varied problems with unsupported hardware (such as various ethernet cards), that is now supported - lots of work on improving the language used to be easier to understand - many, many more The recent server compromise slowed us down for a while, but we're nearly past that and planning for the next beta. Besides fixing #1-#5 above, the big focus for this beta will be on ports and translations. We're doing pretty well on translations already. 4 languages are more than 90% done, 4 more are over 50% done[1]. An upcoming string freeze, scheduled for the 14th through 21st, should provide the chance for lots of languages to get 100% up-to-date against a stationary target. Any translators who are interested in helping bring an existing language up to date, or add a new one, should subscribe to the debian-boot mailing list and read doc/translations.txt in d-i cvs. We're not doing so well on ports. There has been some activity on the ia64 and hppa ports since beta 1, and I hope to see one or both included in beta 2, but both need more testing. Of course powerpc continues to be supported. The mips port more or less works if you know what you're doing, and is on track to be included in beta 2. But there has been only some activity on sparc, mipsel, alpha, m69k (amiga), and s390; and little or progress on hppa, arm, various m68k subarches, and many less common powerpc subarches; and many of these architectures are nowhere near working. I know that there can still be quite a learning curve involved in porting d-i, and I hope that we can come up with some better ways for those of us who understand all of d-i to work more closely with those of you who grok an architecture. Something I'd like to try is getting separate pairs of d-i developers and porters together in one place, and see if and see if such small teams they can make some real progress. I encourage any porter or d-i developer who is interested in this idea to post to the debian-boot mailing list. Ports or no ports, d-i will eventually release, and the release plans for beta 2 are to have it out before New Years. -- see shy
announcing public access to X Strike Force SVN repositories
[This is a re-send, as the one I mailed on 6 December never showed up.] Hi, folks. I'm pleased to announce the availability of anonymous, read-only, public access to the X Strike Force Subversion repositories. The latest revision of the README file at the top of the XFree86 repository tells the story best. % svn cat svn://necrotic.deadbeast.net/xfree86/README | head -n 56 README for Debian X Strike Force Subversion repository == Browsing the repository via the Subversion protocol --- Read-only access is available via the SVN protocol. A daemon is running on the standard svn port on necrotic.deadbeast.net. Note that multiple repositories are available. Subversion URLs of interest include: svn://necrotic.deadbeast.net/render/trunk svn://necrotic.deadbeast.net/xcursor/trunk svn://necrotic.deadbeast.net/xfree86/trunk svn://necrotic.deadbeast.net/xft/trunk svn://necrotic.deadbeast.net/xrender/trunk CHECKOUT OR EXPORTS MUST BE CONFINED TO DIRECTORIES THAT ARE IMMEDIATE PARENTS OF A debian/ DIRECTORY, OR THEMSELVES HAVE debian/ IN THEIR PATH SPECIFICATIONS. ABUSE OF READ-ONLY ACCESS THROUGH VIOLATION OF THIS RULE MAY RESULT IN TERMINATION OF THIS SERVICE. It may also result in your hard drive filling up and/or your ISP terminating your service for excessive usage of bandwith. Examples of paths that it is acceptable to checkout or export include: svn://necrotic.deadbeast.net/xfree86/branches/4.1.0/woody svn://necrotic.deadbeast.net/xfree86/branches/4.1.0/woody-proposed-updates svn://necrotic.deadbeast.net/xfree86/branches/4.3.0/sid svn://necrotic.deadbeast.net/xfree86/branches/4.3.0/woody svn://necrotic.deadbeast.net/xfree86/tags/4.1.0-16 svn://necrotic.deadbeast.net/xfree86/tags/4.1.0-16woody1 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-7 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-8 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-9 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-10 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-11 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-12 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-13 svn://necrotic.deadbeast.net/xfree86/tags/4.2.1-14 svn://necrotic.deadbeast.net/xfree86/people/branden/lintian-overrides svn://necrotic.deadbeast.net/xfree86/people/branden/xlibs-and-xbase-clients-split svn://necrotic.deadbeast.net/xfree86/trunk Use of the list or cat commands is acceptable on any path specification. Write access is restricted to people with SSH access to the host. If you don't know how to use Subversion, you may wish to read Branden's tutorial: http://necrotic.deadbeast.net/~branden/svn_pres/top.html If you have more time, a comprehensive manual, written by Subversion's developers, is also available: http://svnbook.red-bean.com/ -- G. Branden Robinson| Why do we have to hide from the Debian GNU/Linux | police, Daddy? [EMAIL PROTECTED] | Because we use vi, son. They use http://people.debian.org/~branden/ | emacs. signature.asc Description: Digital signature
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Thu, Dec 11, 2003 at 09:08:38PM +, Andrew Suffield wrote: On Wed, Dec 10, 2003 at 10:29:24PM -0800, Marc Wilson wrote: On Wed, Dec 10, 2003 at 12:31:17PM +, Andrew Suffield wrote: We don't have to map them onto anything. We just have to pass them through to the menu methods in a fashion that allows them to generate .desktop files. Other way around. You have to pass .desktop files through to the menu-methods in a fashion that allows them to generate menus digestible to applications not supporting .desktop files. You seem to have lost the context. Not at all. You want to enforce on $RANDOM_UPSTREAM the idea that they have to support .desktop files. That is *not* going to work. Debian does not have that sort of power. On the other hand, the idea that an application desiring to participate in the menu system being required to provide the necessary menu-method to get from .desktop files to their own format is much more reasonable. Upstream can create that, or the package maintainer can, or the menu package can provide it. Boy... that sure sounds a lot like the current $APPLICATION-agnostic method Debian has right now. So, why does this change need to happen again? If what you want is for only Gnome and KDE to be able to participate in the menu system, you could just come out and say so. -- Marc Wilson | All kings is mostly rapscallions. --Mark Twain [EMAIL PROTECTED] | signature.asc Description: Digital signature
How frequently is the override file getting updated?
Hi, I updated a new set of e2fsprogs debs 5 or 6 days ago, which among other things contained an RC bugfix. It's been stalled waiting for someone to update the override file. I know that people are busy finishing off the last bits of recovery from the security compromise, but when should I expect that the override file will get updated so the updated e2fsprogs can get accepted into the archive? Many thanks!! - Ted
Re: Initrd and software raid
Bernd Eckenfels [EMAIL PROTECTED] wrote: On Wed, Dec 10, 2003 at 09:48:55AM +0100, Florent Rougon wrote: autodetection to manual setting in my GRUB config files and am happy with this setup (I hate black magic). Black magic can be good for multi path io, sans and generally for a unattended reboot on hardware changes. Sure, I didn't mean to say black magic is always a bad thing. I have no problem with it when there is a known, documented way to avoid it when unneeded. -- Florent
Re: How frequently is the override file getting updated?
On Fri, Dec 12, 2003 at 03:55:53AM -0500, Theodore Ts'o wrote: Hi, I updated a new set of e2fsprogs debs 5 or 6 days ago, which among other things contained an RC bugfix. It's been stalled waiting for someone to update the override file. I know that people are busy finishing off the last bits of recovery from the security compromise, but when should I expect that the override file will get updated so the updated e2fsprogs can get accepted into the archive? One week says the email, but then i have been waiting for over a month for the new powerpc kernel packages. There is definitively something roten in the way this gets handled. On the one hand we were aiming at releasing sarge 12 days ago, on the other hand the ftpmaster, by being buy (or do you say by business ?) or for other reason stall back the work of their fellow debian developers without even giving feedback as to the reason of it. And don't tell me they have no time, since apparently they have time to discuss this with third party people behind our back, so what does it cost to share this discussion with the maintainer of said package, who probably knows more about the reason of the new binary packages than the ftp-masters do. This behavior is holding us back, and it is really sad that nothing than a week or more of public ranting will help in getting something done there, and it may not even work this time. And the intrussion is not even an excuse, since i uploaded the package at the begining of november, when the intrussion did not exist yet. Friendly, Sven Luther
debian-devel@lists.debian.org
¹ØÓÚÍø׬ ÎÒµÄÍøÕ¾£ºhttp://www.fj35.com/so/?mid=wsh888ÊÇÄã·¢¼ÒÖ¸»£¬ÃÎÃÁÒ»ÇóµÄµØ·½£¬Ö»ÒªÄóö5·ÖÖÓʱ¼ä£¬×Ðϸ¿´ÏÂÃæÍøÕ´ÄÚÈÝ http://www.fj35.com/so/?mid=wsh888Äú¿Ï¶¨´ó³¹´óÎò£¡ [EMAIL PROTECTED] 2003-12-12
debian-devel@lists.debian.org
Http://www.qgpx.com; 2003122728 1 2 3 4 5 6 7 : .HRHRHR : 1 2 3 4 1 2 3 4 5 1 2 3 4 1 2 3 1 2 3 1 2 3 1 2 3 4 1 2 3 45 5 Http://www.qgpx.com01088923748; : : 1980 : 010--8892374851875077 88923748 Http://www.qgpx.com
Bug#223772: general: no md5sums for many packages (e.g. bc)
Subject: general: no md5sums for many packages (e.g. bc) Package: general Version: N/A; reported 2003-12-12 Severity: normal Tags: security -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux donald 2.4.18-xfs-1.1 #1 Tue Apr 8 09:10:07 CEST 2003 i686 Locale: LANG=C, LC_CTYPE=C Mit freundlichen Grüßen / Best regards Dipl.-Ing. Werner THÖNI Allgemeines Rechenzentrum GmbH Technischer Bereich Leiter Systemgruppe UNIX A-6020 Innsbruck, Tschamlerstraße 2 Tel.: +43 / (0)50400-0 Fax: +43 / (0)50400-1382 e-Mail: [EMAIL PROTECTED] http://www.arz.co.at
personal invite -- Ryze business networking
Rahul has invited you to join Rahul's personal and private network on Ryze. To view the invite, click on: http://www.ryze.com/in/v99qOIWWki9e9cylrZDT Ryze is a networking service that helps people grow their careers, businesses and lives. * meet entrepreneurs, CEOs and other neat people through your existing friends and contacts * get expert advice and contacts through special networks focused on your interests and industry * get your own networking-oriented home page * keep in touch with your friends and keep track of their birthdays http://www.ryze.com/in/v99qOIWWki9e9cylrZDT
Intent to hijack pvm
Hi, I intend to hijack pvm within the next week or so -- the package has not had a maintainer upload for years (several RC-bugs closed by NMU), does not appear to work properly on 64-bit platforms and has other problems. The maintainer appears to be semi-MIA and has not responded to my OTA filed a week or so ago. Please speak up now if you have any problems with this. /* Steinar */ -- Homepage: http://www.sesse.net/
Bug#223772: general: no md5sums for many packages (e.g. bc)
[EMAIL PROTECTED] writes: Subject: general: no md5sums for many packages (e.g. bc) Package: general Version: N/A; reported 2003-12-12 Severity: normal Tags: security Every package has a md5sum in the Package file. Some packages have a useless and space wasting md5sums file inside the package. Due to its uselessness the existance is rather a bug than its omission. Please close this bug, read the threads on debian-devel about this and if you still want md5sum files help making actually usefull ones. MfG Goswin
Bug#223781: [RFA]: usemod-wiki -- Perl-based Wiki clone
Package: wnpp Severity: normal I no longer use usemod-wiki and thus have no time to maintain it. Package is in good shape, no serious bugs. Very few work is needed to maintain it as release cycle is quite long. The only one todo item is to package version 1.0, which requires some changes to the wiki database. Peter Gervai [EMAIL PROTECTED] has already made a package for this and is going to NMU usemod-wiki. But as he does not have time to adopt it, we need a new maintainer. I can provide my CVS repository for usemod-wiki upon request. Cheers, Benjamin -- .''`. ; ;' ; Debian GNU/Linux | Benjamin Drieu `. `'http://www.debian.org/ | [EMAIL PROTECTED] `- pgpMtrMqLxdQg.pgp Description: PGP signature
RE: Bug#223781: [RFA]: usemod-wiki -- Perl-based Wiki clone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Drieu wrote: I no longer use usemod-wiki and thus have no time to maintain it. Package is in good shape, no serious bugs. Very few work is needed to maintain it as release cycle is quite long. The only one todo item is to package version 1.0, which requires some changes to the wiki database. Peter Gervai [EMAIL PROTECTED] has already made a package for this and is going to NMU usemod-wiki. But as he does not have time to adopt it, we need a new maintainer. As I'm using UseMod Wiki on a slew of Debian machines, I'd be more than willing to continue maintaining usemod-wiki, but I'm no Debian Developer, so I'd need a sponsor until I decide and manage to become one. -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Get my PGP public key at http://www.mehnle.net/about. iQA/AwUBP9nDXsC+zypQWVo7EQJJZACfUMiuM8Z19w/ydpwpnpnESmyHYkoAoMtY bAopzElp8scS+9hcetlzhFfH =gbCW -END PGP SIGNATURE-
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, 2003-12-12 at 01:01, Marc Wilson wrote: Not at all. You want to enforce on $RANDOM_UPSTREAM the idea that they have to support .desktop files. That is *not* going to work. Debian does not have that sort of power. On the other hand, the idea that an application desiring to participate in the menu system being required to provide the necessary menu-method to get from .desktop files to their own format is much more reasonable. Upstream can create that, The above two paragraphs don't make sense to me, in combination. If upstream can write code to convert from .desktop to their own format, why can't they just include that directly in their software? The user would never have to know that the software wasn't reading .desktop natively (except that presumably it wouldn't support all the .desktop features). signature.asc Description: This is a digitally signed message part
RE: Bug#223781: [RFA]: usemod-wiki -- Perl-based Wiki clone
Am Fr, den 12.12.2003 schrieb Julian Mehnle um 15:32: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Drieu wrote: I no longer use usemod-wiki and thus have no time to maintain it. Package is in good shape, no serious bugs. Very few work is needed to maintain it as release cycle is quite long. The only one todo item is to package version 1.0, which requires some changes to the wiki database. Peter Gervai [EMAIL PROTECTED] has already made a package for this and is going to NMU usemod-wiki. But as he does not have time to adopt it, we need a new maintainer. As I'm using UseMod Wiki on a slew of Debian machines, I'd be more than willing to continue maintaining usemod-wiki, but I'm no Debian Developer, so I'd need a sponsor until I decide and manage to become one. I use it on some systems too, so I would be pleased to be your sponsor. Get in touch with me if you have packages ready for upload/inspection. formorer -- Alexander formorer Wirt KeyID: BC7D020A EMail: [EMAIL PROTECTED] ICQ: 28651245 WWW: http://www.formorer.de Encrypted and Signed Email preferred. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Accepted kernel-image-2.4.22-i386 2.4.22-2woody.2 (i386 source)
Hello, Tuesday, December 9, 2003 at 12:02:33 (CET), Herbert Xu wrote: Format: 1.7 Date: Sat, 29 Nov 2003 14:02:33 +1100 Source: kernel-image-2.4.22-i386 Binary: [...] kernel-image-2.4.22-2-386 [...] Architecture: source i386 Version: 2.4.22-2woody.2 Distribution: stable Urgency: high Maintainer: Herbert Xu [EMAIL PROTECTED] Changed-By: Herbert Xu [EMAIL PROTECTED] The kernel-images are available in the woody-proposed-updates. They depend on initrd-tools (= 0.1.32woody.5), but the latest available version for Woody (including the woody-proposed-updates) is 0.1.32woody.3. Should I report the bug through the BTS ? Against which package ? -- Arnaud
Re: XFS entering kernel 2.4 tree - Should the installer include support?
On Thu, Dec 11, 2003 at 10:57:25PM -0600, Gunnar Wolf wrote: I am writing to -devel and not to -boot as I think this should be visible for most developers, as it can have a huge impact in our systems. I was reading [1] today that XFS is entering the 2.4 kernel tree - Being we still reasonably far from having Sarge releasable, what would you think on adding XFS support in our debian-installer? There are not many relevant (although they might be quite complicated) bugs in either xfs-progs or kernel-patch-xfs, and they will surely get attention from upstrean with this announcement... What do you think about this? I have never used XFS for my machines, but have heard quite a lot of good comments about it, and would like to see it available from the official d-i setup. I don't think that XFS support in the mainline d-i images should either precede our kernel maintainers' adoption of the newest kernel sources as a base, or force the issue of upgrading. We use XFS extensively at work, and while it has many nice features, I think some time is needed before we can say the integration into 2.4 has been successful. I'm actually quite surprised to hear the patch no longer touched the VFS by the time it was integrated; there were still quite a few things outside of fs/xfs being changed by the kernel patch last I looked. Either they've done an excellent job of merging the rest of these other changes already, or there are as-yet-unapplied patches that some of us might miss. ;) I'm really quite close on the ITP for the xfs-enabled kernel. I was about ready to upload (just needed a little more testing) before the compromise happened; now I've been trying to decide whether to wait for a brk-patched kernel tree in unstable before uploading, or to just upload and fix it later. Either way, I hope that we'll see some form of official support for XFS in sarge, even if it's not part of the default install images. -- Steve Langasek postmodern programmer pgpofkUSRH46y.pgp Description: PGP signature
Re: mozilla 1.6b
Thomas E. Vaughan wrote: *snip* Any help appreciated. Did you see the mozilla-snapshot package? Try installing it. wt -- Warren Turkal President, GOLUM, Inc. http://www.golum.org
Re: debian pxe dhcp netinstall (debconf enterprise fai etc.)
On Thu, Dec 11, 2003 at 08:36:34PM -0500, Nathan Hawkins wrote: I used grub, though instead of PXE. (Most of the hardware was old, and very few, if any, of the the NIC's supported PXE.) grub can be built with network support, and it supported all the NIC's we had. It also loads the kernel and filesystem from the network faster than from floppy. :) Heh. grub is among the first things I install, along with screen, sudo, vim, and ssh. ;-) I had forgotten about grub's netboot capabilities. Very cool feature. -- Chad Walstrom [EMAIL PROTECTED] http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */ pgpAsVZAFi3KD.pgp Description: PGP signature
Re: Bug reports missing
On Wed, Dec 10, 2003 at 11:20:30PM +1100, Hamish Moffatt wrote: On Wed, Dec 10, 2003 at 08:30:49AM +0100, Andreas Tille wrote: mailx -s Merge [EMAIL PROTECTED] ... merge 219863 223355 close 223355 thanks and got the answer mentioned below. It's your punishment for using the close command. DON'T! There is no need and no excuse. I disagree. See situations like #214865 or #218038. close *can* be handled responsibly. -- G. Branden Robinson| The power of accurate observation Debian GNU/Linux | is frequently called cynicism by [EMAIL PROTECTED] | those who don't have it. http://people.debian.org/~branden/ | -- George Bernard Shaw signature.asc Description: Digital signature
Re: XFS entering kernel 2.4 tree - Should the installer include support?
On Fri, Dec 12, 2003 at 05:39:59PM +0100, Andreas Metzler wrote: On Fri, Dec 12, 2003 at 09:51:07AM -0600, Steve Langasek wrote: [...] We use XFS extensively at work, and while it has many nice features, I think some time is needed before we can say the integration into 2.4 has been successful. I'm actually quite surprised to hear the patch no longer touched the VFS by the time it was integrated; there were still quite a few things outside of fs/xfs being changed by the kernel patch last I looked. Either they've done an excellent job of merging the rest of these other changes already, or there are as-yet-unapplied patches that some of us might miss. ;) e.g. the ACL support in xfs has not been (and will not be) merged in mainline 2.4. Ah, so it makes the XFS patchset smaller for 2.4, but an unpatched 2.4 is still pretty much worthless for XFS. :) -- Steve Langasek postmodern programmer pgp707OSES2Pb.pgp Description: PGP signature
Re: XFS entering kernel 2.4 tree - Should the installer include support?
On Fri, Dec 12, 2003 at 09:51:07AM -0600, Steve Langasek wrote: [...] We use XFS extensively at work, and while it has many nice features, I think some time is needed before we can say the integration into 2.4 has been successful. I'm actually quite surprised to hear the patch no longer touched the VFS by the time it was integrated; there were still quite a few things outside of fs/xfs being changed by the kernel patch last I looked. Either they've done an excellent job of merging the rest of these other changes already, or there are as-yet-unapplied patches that some of us might miss. ;) e.g. the ACL support in xfs has not been (and will not be) merged in mainline 2.4. cu andreas
Processed: Re: Bug#223772: general: no md5sums for many packages (e.g. bc)
Processing commands for [EMAIL PROTECTED]: tags 223772 - security Bug#223772: general: no md5sums for many packages (e.g. bc) Tags were: security Tags removed: security thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: Changes in formal naming for NetBSD porting effort(s)
[I am not subscribed to debian-bsd.] On Thu, Dec 11, 2003 at 04:39:47PM -0700, Joel Baker wrote: On December 2nd, I was contacted by Luke Mewburn, on behalf of The NetBSD Foundation, asking about the transition to calling the NetBSD port Debian GNU/KNetBSD, and expressing their appreciation for this change, as it reflects (in their opinion) a more accurate statement about what the system is, and avoids any potential dilution of the NetBSD trademark. Uh-huh. I'll go check, but is all of this discussion archived on debian-bsd? [minutes pass] I checked, and I don't see the *specific* grounds for the request explicated anywhere. I did, however, say that I (at least) would be happy to try to find a name they found equally suitable, for the same reasons, rather than continue to use the current one. What makes a suitable name? Please be specific. If you don't know, I think you should request this information from the NetBSD Foundation. On December 3rd, Mr. Mewburn confirmed that The NetBSD Foundation would prefer to see the name changed, and I brought the issue up on the debian-bsd mailing list for discussion. [...] Okay, yeah, I'm caught up on that part. The thread seemed to be mostly concerned with technical issues, which is a completely legitimate concern, but I think the discussion to date, if comprehensively reflected on the -bsd list has almost completely neglected discussion of the central thrust of the request you received. 4) The Debian port name will become 'Debian GNU/KLNetBSD(i386)'[1]. Well, no offense, but that's ugly as hell, and is going to square the amount of confusion people experience when trying to decode our OS names. If anyone objects, or wishes to see further requirements met, please let me know, and I'll do what I can to resolve the situation. I don't understand the nature of your request. They're cool with Debian GNU/KLNetBSD but not Debian GNU/NetBSD? Why, exactly? And how does trademark enter into this, exactly? In both cases, the mark is still being used. Yet they're cool with the former and not the latter? As I understand the law[1], the mark is no more or less used or diluted in either case. Debian either needs a trademark license from the NetBSD Foundation for use of the NetBSD mark, or it does not. If we do, then our hands are tied and we might as well ask them to tell us what they want it called, and what the terms of use are. Since the Debian Project doesn't legally exist, this will probably have to go through SPI. If we don't need a trademark license, then I don't understand why they've grounded their request for a name change on a claim to be preserving the mark. It might be best to remove NetBSD from the name of the OS altogether -- that would the most sure-fire way to mitigate their fears of dilution, and help ensure that the NetBSD Foundation doesn't have to rattle its saber at us again (albeit through a lace curtain, as you say), enabling us to maintain good relations with the NetBSD Project on the technical front. Please note that all of my discussions with The NetBSD Foundation, and it's representatives, have been both cordial and productive, to date, and that I feel their request is born largely of having seen an example which they preferred, rather than any antipathy towards the Debian project as a whole, or the various BSD porting efforts under it. No, it's probably antipathy for the Free Software Foundation driving this more than anything else. Maybe they'd prefer Debian GNU/KLMNOPQRSTUVWXYZABCDEFGHIJNetBSD most of all. One can't get too far away from those pinkos in Boston! On a more serious note, you have been contacted in your capacity as a Debian Developer by a trademark holder who is either displeased, or is suggesting that they might easily become displeased. I think the responsible thing to do at this point is to get the debian-legal mailing list involved so that folks with a mind for trademark law can have a closer look at the matter. None of the abuse should be taken to denigrate the work of the NetBSD or Debian developers. My concerns here are twofold: 1) the suggestion by a trademark holder that Debian might be regarded as infringing a mark if we don't take some action; and 2) the comprehensibility of our OS names to the pubic. [1] which ain't much -- G. Branden Robinson| The greatest productive force is Debian GNU/Linux | human selfishness. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | signature.asc Description: Digital signature
[custom] Localized CD with pruned locale data
CDDs may be tailored for a particular purpose, such as to distribute to a small group where the locales of all users is known (or assumed). In order to include the maximum useful material per media it would be useful in such cases to prune any unnecessary locale data provided by the included packages. However, to do so would be to damage the packages that provide that data. Is a CDD that is tailored in this fashion still Debian? Take, for example, a package with missing locales that is used by a user who desires a different locale. Such a user might be inclined to file a bug against the modified package, but the maintainer of the buggy package would probably not immediately recognize the cause of the problem, wasting their valuable time. Do mechanisms exist within Debian for providing such tailoring? Should they exist? Locales are only one example of bloat[0] that might be desirable to trim for a CDD. In general, how do we allow CDDs to be pure Debian and still make efficient use of media space? Ben Armstrong [0] It almost goes without saying that one person's bloat is another person's valuable feature. When you produce something for users that don't need a resource-consuming feature, the feature is bloat. -- ,-. nSLUGhttp://www.nslug.ns.ca [EMAIL PROTECTED] \`' Debian http://www.debian.org[EMAIL PROTECTED] ` [ gpg 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ] [ pgp 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ]
Re: Bug reports missing
On Fri, 12 Dec 2003, Branden Robinson wrote: It's your punishment for using the close command. DON'T! There is no need and no excuse. I disagree. See situations like #214865 or #218038. close *can* be handled responsibly. Thanks for this support. I'm generally aware that close is bad, but I wanted to merge the bugs to show their relation (which is not possible as I have learned now) and the explanation was given in previous mails, so close seemd to me apropriate (under this very special conditions). Kind regards Andreas.
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
Marc Wilson dijo [Thu, Dec 11, 2003 at 10:01:39PM -0800]: Other way around. You have to pass .desktop files through to the menu-methods in a fashion that allows them to generate menus digestible to applications not supporting .desktop files. You seem to have lost the context. Not at all. You want to enforce on $RANDOM_UPSTREAM the idea that they have to support .desktop files. That is *not* going to work. Debian does not have that sort of power. Worse yet - after demanding that, we probably will rewrite their .desktop files - We will still (I hope) strive to provide menus consistent with our way of doing things. One of the main roles of the maintainers of a distribution is to handle interaction between each individual package and the rest of the collection - this involves sorting out how menus will be presented. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5630-9700 ext. 1366 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF signature.asc Description: Digital signature
Re: Changes in formal naming for NetBSD porting effort(s)
[ Adding -legal to the Cc; it may become inappropriate for -devel, at ] [ some point, in which case folks should remove the -devel Cc. The -bsd ] [ Cc should probably remain no matter what, as this could potentially ] [ affect any of the BSD ports.] On Fri, Dec 12, 2003 at 11:54:09AM -0500, Branden Robinson wrote: [I am not subscribed to debian-bsd.] On Thu, Dec 11, 2003 at 04:39:47PM -0700, Joel Baker wrote: On December 2nd, I was contacted by Luke Mewburn, on behalf of The NetBSD Foundation, asking about the transition to calling the NetBSD port Debian GNU/KNetBSD, and expressing their appreciation for this change, as it reflects (in their opinion) a more accurate statement about what the system is, and avoids any potential dilution of the NetBSD trademark. Uh-huh. I'll go check, but is all of this discussion archived on debian-bsd? [minutes pass] I checked, and I don't see the *specific* grounds for the request explicated anywhere. I guess it depends on precisely what you mean by specific grounds, in this case. If you mean 'specific accusations of dilution of trademark', then I don't believe there have been any. I did, however, say that I (at least) would be happy to try to find a name they found equally suitable, for the same reasons, rather than continue to use the current one. What makes a suitable name? Please be specific. If you don't know, I think you should request this information from the NetBSD Foundation. As far as I can tell, anything which does not use the bare word 'NetBSD' as part of it's name, but I certainly can request clarification from Mr. Mewburn and The NetBSD Foundation about that. On December 3rd, Mr. Mewburn confirmed that The NetBSD Foundation would prefer to see the name changed, and I brought the issue up on the debian-bsd mailing list for discussion. [...] Okay, yeah, I'm caught up on that part. The thread seemed to be mostly concerned with technical issues, which is a completely legitimate concern, but I think the discussion to date, if comprehensively reflected on the -bsd list has almost completely neglected discussion of the central thrust of the request you received. I think that is largely a reflection of nobody had any disagreement on the principle, or a better suggestion for the formal port name, combined with the fact that it triggered reviewing some of the haphazard naming conventions with a critical eye, and making sure that they were reasonable and rational. The thread is, indeed, split into two interleaved parts, and the non-technical part is almost empty. 4) The Debian port name will become 'Debian GNU/KLNetBSD(i386)'[1]. Well, no offense, but that's ugly as hell, and is going to square the amount of confusion people experience when trying to decode our OS names. Agreed, unfortunately - it is, and I suspect it may well. Suggestions for better naming welcome, of course (or even a direction to go in). If anyone objects, or wishes to see further requirements met, please let me know, and I'll do what I can to resolve the situation. I don't understand the nature of your request. They're cool with Debian GNU/KLNetBSD but not Debian GNU/NetBSD? Why, exactly? I believe (note: personal view) that the core is a perceived difference between the bare word 'NetBSD', which has, prior to this port, implied a kernel, libc, *and* userland of a specific form, and a variant of that name which is recognizeable, but distinctive enough to not cause confusion between their product and what we intend to produce. And how does trademark enter into this, exactly? In both cases, the mark is still being used. Yet they're cool with the former and not the latter? As I understand the law[1], the mark is no more or less used or diluted in either case. I do not have anything remotely like the background to discuss this meaningfully - frankly, I wasn't particularly aware that there might be any substantive issue with the assertion. See below for more. Debian either needs a trademark license from the NetBSD Foundation for use of the NetBSD mark, or it does not. If we do, then our hands are tied and we might as well ask them to tell us what they want it called, and what the terms of use are. Since the Debian Project doesn't legally exist, this will probably have to go through SPI. If we don't need a trademark license, then I don't understand why they've grounded their request for a name change on a claim to be preserving the mark. This might well be a reasonable path to take, given that TNF (those making the actual request) are, in many ways, related to The NetBSD Project in the same fashion that SPI and Debian are related; one is a legal entity, the other is a bunch of folks producing an operating system. Certainly, it would make things more explicit and less prone to future problems. It might be best to remove NetBSD from the name of the OS
Nice multilingual environment with Debian menu
Hi, We all know how to set up localized environment through shell environment variables. There is even helper packages language-env. (Or KDE etc can be started with locale set by kdm.) But I never liked them since I get locked into a single locale. So how can we elegantly set multilingual environment in X window environment with direct access to the different language environments. My wishlists are: * UTF-8 console with English locale * UTF-8 console with Japanese locale * en_US.ISO-8859-1 console * fr_FR.ISO-8859-1 console * de_DE.ISO-8859-1 console * mozilla at the top of initial menu selection It may have been known for many but I just found that the customized Debian menu is the most elegant way to do this :-) (I used to have shell start-up script asking locale.) Long answer is here: http://qref.sourceforge.net/Debian/reference/ch-tune.en.html#s-x-cjk Key tricks used are: 1. creating customized menu entry by adding files in /etc/menu, 2. command are executed under sh -c to enable new environment, 3. menu entry such as / ... to get to the nicer location. Osamu PS: per user based ~/.menu entry never worked for me.
Re: mozilla 1.6b
* Warren Turkal wrote: Thomas E. Vaughan wrote: *snip* Any help appreciated. Did you see the mozilla-snapshot package? Try installing it. Last update of this package was in the beginning of october. I don't think that's a mozilla 1.6b. Norbert
Re: Changes in formal naming for NetBSD porting effort(s)
I removed a lot of CC's, since this comment isn't relevant to the rest of the discussion, really... On Thu, Dec 11, 2003 at 04:39:47PM -0700, Joel Baker wrote: [snip] I explained that Debian GNU/KNetBSD was actually a separate effort, primarily by Robert Millan, to port Debian to a system consisting of NetBSD's kernel (thus, 'KNetBSD') and a ported GNU libc, while the other effort was aimed at a NetBSD kernel and native NetBSD libc. I did, however, say that I (at least) would be happy to try to find a name they found equally suitable, for the same reasons, rather than continue to use the current one. Are you saying that we're going to have both a Debian GNU/KNetBSD distribution, which, since it uses glibc presumably would be able to use the same binaries as the GNU/Linux architecture for _most_ packages (please correct me if I'm wrong) _and_ a distribution based on NetBSD's libc, which would required close to every damn binary to have separate packages. Thus, given NetBSD's multiplatform support, almost doubling the size of the Debian archives?! Madness lies that way. Yes, choice is good, but sometimes, just sometimes too much choice will make you choke... /David -- /) David Weinehall [EMAIL PROTECTED] /) Northern lights wander (\ // Maintainer of the v2.0 kernel // Dance across the winter sky // \) http://www.acc.umu.se/~tao/(/ Full colour fire (/
Re: Release-critical Bugreport for December 12, 2003
BugScan reporter [EMAIL PROTECTED] writes: Package: chrony (debian/main) Maintainer: John Hasler [EMAIL PROTECTED] [REMOVE] 223134 [] chrony: FTBFS: Errors in kernel headers Why is chrony getting removed? Package: defrag (debian/main) Maintainer: Timshel Knoll [EMAIL PROTECTED] [REMOVE] 223145 [] defrag: FTBFS: Errors in kernel headers Again why is this remove? (If the maintainer is unresponsive or something I would adopt either package.) MfG Goswin
Re: Changes in formal naming for NetBSD porting effort(s)
On Fri, Dec 12, 2003 at 07:24:29PM +0100, David Weinehall wrote: I removed a lot of CC's, since this comment isn't relevant to the rest of the discussion, really... On Thu, Dec 11, 2003 at 04:39:47PM -0700, Joel Baker wrote: [snip] I explained that Debian GNU/KNetBSD was actually a separate effort, primarily by Robert Millan, to port Debian to a system consisting of NetBSD's kernel (thus, 'KNetBSD') and a ported GNU libc, while the other effort was aimed at a NetBSD kernel and native NetBSD libc. I did, however, say that I (at least) would be happy to try to find a name they found equally suitable, for the same reasons, rather than continue to use the current one. Are you saying that we're going to have both a Debian GNU/KNetBSD distribution, which, since it uses glibc presumably would be able to use the same binaries as the GNU/Linux architecture for _most_ packages (please correct me if I'm wrong) _and_ a distribution based on NetBSD's libc, which would required close to every damn binary to have separate packages. Thus, given NetBSD's multiplatform support, almost doubling the size of the Debian archives?! Madness lies that way. Yes, choice is good, but sometimes, just sometimes too much choice will make you choke... Mostly, I'm saying that the debian-bsd ports list is much like the classical herd of cats, and the debate over which kernel, core libraries, and userland to use has gone on for... well, pretty much as long as the list has existed, as far as I can tell from the archives. The specific efforts talked about are those with code on the ground, that is, those which actually have a package archive of some fashion, visible progress in getting things to a useable state, and enduring effort applied to them. The expectation, as far as I can tell, is that we'll be expected to resolve this in some sane and rational fashion before the ftpmasters let us anywhere near the archive. Right now, both NetBSD ports use the 'netbsd-i386' name, which works solely because nobody attempting to use this tries to pull from more than one of the APT archives. It also doesn't bar the possibility of ending up with a port which, for example, has a 'core' libc from NetBSD, but has a copy of GNU libc which some applications link against for specific things. Porting the GNU libc is a topic better addressed elsewhere (and has been, fairly recently). In other words: yes, it's a bit mad. We're trying fairly hard not to inflict that madness on anyone we don't have to, and expect that it will settle out at some point. :) -- Joel Baker [EMAIL PROTECTED],''`. Debian GNU/KLNetBSD(i386) porter : :' : `. `' `- pgpea8IHtzg1U.pgp Description: PGP signature
Re: Changes in formal naming for NetBSD porting effort(s)
On Fri, Dec 12, 2003 at 07:24:29PM +0100, David Weinehall wrote: On Thu, Dec 11, 2003 at 04:39:47PM -0700, Joel Baker wrote: [snip] I explained that Debian GNU/KNetBSD was actually a separate effort, primarily by Robert Millan, to port Debian to a system consisting of NetBSD's kernel (thus, 'KNetBSD') and a ported GNU libc, while the other effort was aimed at a NetBSD kernel and native NetBSD libc. I did, however, say that I (at least) would be happy to try to find a name they found equally suitable, for the same reasons, rather than continue to use the current one. Are you saying that we're going to have both a Debian GNU/KNetBSD distribution, which, since it uses glibc presumably would be able to use the same binaries as the GNU/Linux architecture for _most_ packages (please correct me if I'm wrong) _and_ a distribution based on NetBSD's libc, which would required close to every damn binary to have separate packages. Thus, given NetBSD's multiplatform support, almost doubling the size of the Debian archives?! Probably not exactly. It is the case at the moment, but hopefully it won't stay that way. You are incorrect about glibc allowing the use of the same binaries. It doesn't work that way, because kernel struct's and constants differ. (Among other things. Actually, the BSD's can run regular Debian binaries in Linux emulation mode, so that's really not necessary. The problem is that dpkg doesn't understand that, so you have to use a chroot.) The use of glibc gains some source compatiblity at the expense of an unstable libc that will require a lot more work to fully support the BSD kernels. I don't believe that this work will ever really get done, giving the native libc port an advantage. Also, I would be really surprised if the glibc port gets past i386, since there's a lot more effort involved in doing that. Madness lies that way. Yes, choice is good, but sometimes, just sometimes too much choice will make you choke... True. ---Nathan
Bug#223807: ITP: seq24 -- Real time MIDI sequencer
Package: wnpp Version: unavailable; reported 2003-12-12 Severity: wishlist * Package name: seq24 Version : 0.4.3 Upstream Author : Rob C. Buse * URL : http://www.filter24.org/seq24/ * License : GPL Description : Real time MIDI sequencer Seq24 was created to provide a very simple interface for editing and playing midi 'loops'. It is a very minimal sequencer that excludes the bloated features of the large software sequencers and includes a small subset that proved to be useful for live performances. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux xdv 2.4.22-1-686 #1 Fri Sep 5 23:04:29 EST 2003 i686 Locale: LANG=C, LC_CTYPE=C
Re: Nice multilingual environment with Debian menu
On Fri, 2003-12-12 at 12:43, Osamu Aoki wrote: * UTF-8 console with English locale * UTF-8 console with Japanese locale Why are these different? It isn't really laid out in the document linked; does this mean different input methods? -- Joe Drew [EMAIL PROTECTED] [EMAIL PROTECTED] Just admit to yourself that you're a thief: http://me.woot.net/stealing.html
Re: XFS entering kernel 2.4 tree - Should the installer include support?
Gunnar Wolf wrote: I am writing to -devel and not to -boot as I think this should be visible for most developers, as it can have a huge impact in our systems. I was reading [1] today that XFS is entering the 2.4 kernel tree - Being we still reasonably far from having Sarge releasable, what would you think on adding XFS support in our debian-installer? There are not many relevant (although they might be quite complicated) bugs in either xfs-progs or kernel-patch-xfs, and they will surely get attention from upstrean with this announcement... What do you think about this? I have never used XFS for my machines, but have heard quite a lot of good comments about it, and would like to see it available from the official d-i setup. Once the stock debian kernel has XFS in it, support can trivially be added to the installer, by providing a udeb in the archive that contains a mkfs.xfs program that does the usual thing. -- see shy jo signature.asc Description: Digital signature
Re: [Openhbci-general] Re: Ktoblzcheck 0.6 auf debian / stable
Christian Stimming wrote: ich hab leider keine Ahnung, was da los ist (hab kein Debian). Ktoblzcheck benötigt eigentlich keinerlei ungewöhnliche libraries. Irgendjemand sonst Erfahrungen mit Debian woody hier? Ja. Wie sieht es mit dpkg -l build-essentials aus? crt1.o ist in libc6-dev... Gruß T. pgpGa3fANCAUc.pgp Description: PGP signature
Re: XFS entering kernel 2.4 tree - Should the installer include support?
Joey Hess wrote: Gunnar Wolf wrote: I am writing to -devel and not to -boot as I think this should be visible for most developers, as it can have a huge impact in our systems. I was reading [1] today that XFS is entering the 2.4 kernel tree - Being we still reasonably far from having Sarge releasable, what would you think on adding XFS support in our debian-installer? There are not many relevant (although they might be quite complicated) bugs in either xfs-progs or kernel-patch-xfs, and they will surely get attention from upstrean with this announcement... What do you think about this? I have never used XFS for my machines, but have heard quite a lot of good comments about it, and would like to see it available from the official d-i setup. Once the stock debian kernel has XFS in it, support can trivially be added to the installer, by providing a udeb in the archive that contains a mkfs.xfs program that does the usual thing. FWIW, I would like to see XFS support in the installer. I always use XFS on my servers, so whenever I install Debian it is through a Knoppix chroot. I would gladly assist any effort to add/test XFS in the Debian installer. -Roberto pgpjqOi5pWZ7T.pgp Description: PGP signature
Re: Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, Dec 12, 2003 at 04:05:50AM +0100, Moritz Moeller-Herrmann wrote: Because nobody but KDE and Gnome use those features and they already support .desktop files. How would e.g. the lyx debian package get an i18nized menu entry into the menu of either KDE or Gnome. YOU HAVE TO PROVIDE A DESKTOP FILE IF YOU WANT A DECENT MENU. FUD. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: APT-Fu 0.2.3
On Fri, Dec 12, 2003 at 09:55:07AM +0900, Miles Bader wrote: Herbert Xu [EMAIL PROTECTED] writes: I guess that makes sense, if you interpret it as meaning something like `Hard work is the partner of success' -- which sort of works with `apt' too (partner of apt?). I don't think that derivation is correct. The `fu' really has no meaning in the original meaning of the word `kung-fu', which is simply time spent doing things. Well I certainly have no idea of the historical background of the word, but my `guessed derivation' does actually sort of make sense in that context... Do you have a dictionary that gives the historical derivation? The historical derivation isn't very important. The usage here is a modern fan invention (generally used when you aren't being very serious). I don't think it's a very good idea to use in this context. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Thu, Dec 11, 2003 at 10:01:39PM -0800, Marc Wilson wrote: On Thu, Dec 11, 2003 at 09:08:38PM +, Andrew Suffield wrote: On Wed, Dec 10, 2003 at 10:29:24PM -0800, Marc Wilson wrote: On Wed, Dec 10, 2003 at 12:31:17PM +, Andrew Suffield wrote: We don't have to map them onto anything. We just have to pass them through to the menu methods in a fashion that allows them to generate .desktop files. Other way around. You have to pass .desktop files through to the menu-methods in a fashion that allows them to generate menus digestible to applications not supporting .desktop files. You seem to have lost the context. Not at all. You want to enforce on $RANDOM_UPSTREAM the idea that they have to support .desktop files. That is *not* going to work. Debian does not have that sort of power. Eh? That's the opposite of what I've been saying all along. I think you have lost the context. -- .''`. ** Debian GNU/Linux ** | Andrew Suffield : :' : http://www.debian.org/ | `. `' | `- -- | signature.asc Description: Digital signature
Re: Bits from the RM
On Thu, 2003-12-11 at 12:41, Julian Gilbey wrote:
On Mon, Dec 01, 2003 at 02:45:09PM +1000, Anthony Towns wrote:
We've often downplayed asking for help in favour of encouraging people
to *offer* to help, but since we're having problems, it's important to
try everything we can to overcome them. One of the more effective way
of getting useful help (as opposed to someone who says they'll help,
then does absolutely nothing), is to find some specific areas (or tasks)
that could use help, and then be specific in your request. There are
plenty of ways to do this, but at the moment, I think the best way is to
file a RFA (which we're redefining as Request For Assistance instead
of just Request For Adoption) report against wnpp, with some decent
information as to what assistance do you want (someone to take over the
package entirely? a co-maintainer? someone to work on some particular
area? someone to fix some particular bugs? what skills are required?).
I wonder whether it would be better to have two different labels: RFA
(Request For Adoption) and RFH (Request For Help)?
I can see a few eager-beavers seeing an RFA and uploading a replacement
package without even bothering to notice the Maintainer's just asking
for someone to fix a particularly fiendish bug on some architecture they
haven't got.
I guess what we're really going for intentwise is similar to the recent
GNOME Bounties thing.
I'm quite tempted to RF{A,H} a couple of the tricky wishlist bugs open
on libtool for example.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
Any Progress?
I was wondering if there is any progress in getting the servers back to normal. I noticed that http://qa.debian.org/developer.php still isn't updating. Also how long until the buildd's are back online? I only see 3 archs that have online buildds right now. It also appears master's email is broken. Bugs I tried closing in one email yesterday (via multiple [EMAIL PROTECTED]) have yet to be closed and an email I sent to debian-qt-kde still hasn't appeared after 2 hours. Also bugs I tried to close individually about 1 hour ago have yet to be closed as well. Its been 3 weeks now since Debian was compromised, hopefully it won't take too much longer for Debian to return to normal... Thanks, Chris Cheney signature.asc Description: Digital signature
Re: Release-critical Bugreport for December 12, 2003
Scripsit Goswin von Brederlow [EMAIL PROTECTED] BugScan reporter [EMAIL PROTECTED] writes: Package: chrony (debian/main) Maintainer: John Hasler [EMAIL PROTECTED] [REMOVE] 223134 [] chrony: FTBFS: Errors in kernel headers Why is chrony getting removed? AFAIU, the [REMOVE] tag means that the release manager thinks that *if* we do not succeed in fixing this bug, *then* it is reasonable to remove the package from sarge rather than letting it delay the release. It does not imply that the bug is less likely to get fixed than bugs without the tag. (And if it does get fixed, of course it will not cause the package to be removed). The first step in getting concrete information is always to look at the bug in the BTS. Here you'll find that the maintainer of crony is working on the bug and has filed three comments within the last week. 223145 [] defrag: FTBFS: Errors in kernel headers (If the maintainer is unresponsive or something I would adopt either package.) This bug is less than a week old, so it's a little early to declare that the maintainer is unresponsive. -- Henning MakholmWhat the hedgehog sang is not evidence.
Re: Any Progress?
On Fri, Dec 12, 2003 at 03:35:53PM -0600, Chris Cheney wrote: I noticed that http://qa.debian.org/developer.php still isn't updating. See debian-qa. It looks as if this can be re-enabled soon, but the primary author of developer.php currently doesn't have a key in the keyring. -- Colin Watson [EMAIL PROTECTED]
Re: Any Progress?
On Fri, Dec 12, 2003 at 03:35:53PM -0600, Chris Cheney wrote: It also appears master's email is broken. Bugs I tried closing in one email yesterday (via multiple [EMAIL PROTECTED]) have yet to be closed and an email I sent to debian-qt-kde still hasn't appeared after 2 hours. Also bugs I tried to close individually about 1 hour ago have yet to be closed as well. Please cc [EMAIL PROTECTED] about bugs.debian.org problems in future. Can you supply some message-ids or subject lines or something so that we can investigate? master's e-mail doesn't appear to be generally broken. I wonder, though, if all five (!) MXs are doing the right thing. -- Colin Watson [EMAIL PROTECTED]
Re: Release-critical Bugreport for December 12, 2003
On Fri, Dec 12, 2003 at 09:34:12PM +, Henning Makholm wrote: Scripsit Goswin von Brederlow [EMAIL PROTECTED] BugScan reporter [EMAIL PROTECTED] writes: Package: chrony (debian/main) Maintainer: John Hasler [EMAIL PROTECTED] [REMOVE] 223134 [] chrony: FTBFS: Errors in kernel headers Why is chrony getting removed? AFAIU, the [REMOVE] tag means that the release manager thinks that *if* we do not succeed in fixing this bug, *then* it is reasonable to remove the package from sarge rather than letting it delay the release. It does not imply that the bug is less likely to get fixed than bugs without the tag. (And if it does get fixed, of course it will not cause the package to be removed). I'm not sure of the exact process by which the [REMOVE] tag appears in the report. At least in the testing scripts, manual intervention is still required to remove a package from the removal list, so fixing the bug doesn't automatically mean the package won't still be removed from testing. However, since fixing the bug in unstable doesn't immediately lead to the bug's fixing in testing, this doesn't seem inappropriate to me. There's certainly time to communicate with the Release Manager that the package should no longer be considered a removal candidate. -- Steve Langasek postmodern programmer pgpylwdDnXQnC.pgp Description: PGP signature
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, Dec 12, 2003 at 11:42:25AM -0600, Gunnar Wolf wrote: Worse yet - after demanding that, we probably will rewrite their .desktop files - We will still (I hope) strive to provide menus consistent with our way of doing things. One of the main roles of the maintainers of a distribution is to handle interaction between each individual package and the rest of the collection - this involves sorting out how menus will be presented. All that would do is make it consitently different from all other distributions. Assuming that they listed the proper Categories in their Categories: section all that would be needed, if we wanted to be different from other dists, is tweaking of how to break out the menu hierarchy. It would not involve any modification of the .desktop files themselves. See section A. http://www.freedesktop.org/standards/menu-spec/menu-spec-0.8.html Chris Cheney signature.asc Description: Digital signature
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Wed, Dec 10, 2003 at 01:28:51PM -0700, Bruce Sass wrote: On Tue, 9 Dec 2003, Henning Makholm wrote: Scripsit Bruce Sass [EMAIL PROTECTED] On Tue, 9 Dec 2003, Moritz Moeller-Herrmann wrote: In which format shall application packages store their menu information. It doesn't matter, If you don't think the problem being discussed matters, why are you participating in the discussion? The problem is real, the format used to convey the data is immaterial. the question should be, what requires more work: adding features to the existing menu system, or changing the entire menu system. Is there a difference? The changes being contemplated consist in adding features, and any addition of features constitute a change. Yes. relatively small change vs. rewriting almost from scratch NIH. Users and developers propose following the freedesktop standard and using this. Users and developers are also resisting the proposal. With few or no actual arguments about what would go bad. The pain is not worth the gain... why should all the menu consumers need to redo their menu handling so two of them can have a slightly easier time of it. Or just let the Gnome and KDE people who want this do the rewrite for the others. How is this logical? How does the freedesktop standard not gain us features? Because nobody but KDE and Gnome use those features and they already support .desktop files. Yes, but that does not buy KDE and Gnome users anything unless the .desktop files are in the .debs for the applications they use. We're discussions how to allow the .debs to contain them without duplication of information and needless redundancy. Ok. How about doing it so the vast majority of menu consumers are not stuck with a needless rewrite. See above... freedesktop entry features debian menu file features True, but everyone except KDE and Gnome will toss out the freedesktop features. Processing bloated .desktop files just to toss the results is a waste of resources. The fraction of Debian users who use KDE and Gnome is probably less than 90%, but I don't believe that it is small enough that it makes sense to oppose on principle their getting the information they want. All users should be able to get what they want, including those who don't want KDE or Gnome... saddling them with bloated .desktop files does not achieve that. .desktop files are not bloated... period. They include i18n which for you is bloat since you obviously can communicate in English. As I mentioned further down in this message Konqueror only uses 159 bytes when all i18n is stripped from it. I see many debian menu files that are larger than this and they don't contain i18n either. Nobody benefits from the transition... not even KDE or Gnome, since they already support the features the freedesktop standard brings to the table. Having a .desktop infrastructure is worth nothing if you dont have the data it works with. KDE and Gnome users would certainly benefit from having .desktop files in the .debs of the packages they use. Yes, but they would benefit in the same way if the KDE and Gnome specific bits were an addendum to the main menu data entries. Only KDE and Gnome users stand to benefit, so they should be the ones with the added burden. If several KDE and Gnome developers got together and rewrote the menu-methods for the various WM's would that satisfy you? I regularily use KDE, UWM, pdmenu, and Fluxbox, I also have twm, xfce and mwm installed... processing the menues takes too much time and resources as it is, and you want to use up more, for what gain? Just how much more time and resources would it take to convert .desktop files to Debian menu definitions? How often does it have to be done? 1 or 2 hundred bytes vs. a couple to few thousand bytes _per_entry_; what percentage of resources that takes depends on the system... it may be a drop in the bucket for KDE and Gnome users, who are likely to have very capable machines, but what about those who don't have the resources to run KDE or Gnome---why should they be stuck with processing useless stuff they likely can't afford and obviously don't want? The entire menu hierarchy is regenerated everytime a package containing a menu entry is installed or removed. I call bullshit on this one. desktop files with no i18n are not several thousand bytes _pre_entry_. And the fact that those other WM's don't support should be considered a bug not a feature... For example the Konqueror .desktop file is 159 bytes with no i18n or 2234 with it. If as we suggested earlier the Debian menu format gain i18n support then it would be just as big as .desktop (probably actually since Debian has very limited i18n support). I would like to see: /usr/lib/menu/desktop /usr/lib/menu/desktop/gnome /usr/lib/menu/desktop/kde etc. desktop/ can contain the
Bug#223819: RFA: murasaki -- another HotPlug Agent
Package: wnpp Version: N/A; reported 2003-12-12 Severity: normal In last august I adopted murasaki. Despite many emails I've sent to the upstream author I never received any news from him. Last week a RC bug was filled on this package (#223197). A good solution to close this bug is probably to upload a newer version, but the lastest developpment version dosen't meet requirements to be include in Debian[1]. Since I have neither interest nor ressource to handle this package, I request for an adopter. I don't believe that this package is much use. People are generaly using the hotplug package. So if nobody is willing to adopt this package after a week, I will ask for its removal from Debian. [1] : http://packages.qa.debian.org/m/murasaki/news/2.html Cheers, -- Pierre Machard [EMAIL PROTECTED] http://debian.org GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87 signature.asc Description: Digital signature
Re: Any Progress?
On Fri, Dec 12, 2003 at 10:36:30PM +, Colin Watson wrote: On Fri, Dec 12, 2003 at 03:35:53PM -0600, Chris Cheney wrote: It also appears master's email is broken. Bugs I tried closing in one email yesterday (via multiple [EMAIL PROTECTED]) have yet to be closed and an email I sent to debian-qt-kde still hasn't appeared after 2 hours. Also bugs I tried to close individually about 1 hour ago have yet to be closed as well. Please cc [EMAIL PROTECTED] about bugs.debian.org problems in future. Can you supply some message-ids or subject lines or something so that we can investigate? master's e-mail doesn't appear to be generally broken. I wonder, though, if all five (!) MXs are doing the right thing. Message-ID: [EMAIL PROTECTED] The other bug reports from earlier today seem to have been processed but took an hour to do so. Actually from looking at the timestamp they were processed 1min after I sent my previous email, heh. The message to debian-qt-kde that was clogged up by murphy for ~ 2hrs was: Message-ID: [EMAIL PROTECTED] Thanks, Chris signature.asc Description: Digital signature
[no subject]
I WOULD LIKE TO TAKE MY WIFE ON THIS VACATION IF WE WIN IS BECAUSE SHE IS THE MOST WOUNDERFUL WIFE IN THE WORLD WE BEEN TOGETHER FOR OVER 4 YEARS NOW AND MARRIED FOR 1 YEAR AND I'M STILL IN LOVE WITH HER LIKE THE FIRST DAY WE MET SHE IS ALWAYS DOING THING FOR OTHER PEOPLE EVEN IF SHE DON'T HAVE TO DO SHE DO IT ANYWAY AND SHE WORKS SO HARD SHE WORKS 12 HOURS A DAY AND COME HOME AND COOKS AND I JUST WANTED TO TRY AND GIVE HER A ROMANTIC DREAM VACATION TO TELL HER THAT I LOVE HERE AND IF WE LIVE TO BE 150 YEARS OLD I KNOW IN MY HEART THAT SHE WILL STILL BE MY WIFE MY LOVE AND MY BEST FRIEND IN THE WORLD AND MY LIFE EVEN THOUGH I NOT THE RICHES MAN IN THE WORLD I KNOW SHE LOVES MEENRIQUE LOPEZ
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, Dec 12, 2003 at 12:28:29PM +0800, Cameron Patrick wrote: On Fri, Dec 12, 2003 at 04:12:58AM +0100, Moritz Moeller-Herrmann wrote: | Cameron Patrick wrote: | | On Tue, Dec 09, 2003 at 01:57:29PM +, Henning Makholm wrote: | | | Because you gain *nothing* | | | | Are you claiming that everyone who says that .desktop has technical | | advantages is a liar? These features actually do not exist in the | | desktop format? (It may be so; I have no firsthand information, but it | | does sound far out). | | Most of the advantages of .desktop that I am aware of are currently | vapourware - i.e. they're in the specs on the freedesktop.org site, but | not yet implemented in KDE and Gnome. | | This is not true. Almost all features are being used in current KDE and to | some degree by current GNOME. Could you please give examples? The Categories= field (to place .desktop files into menu hierarchies) is AFAIK not used at all by KDE, although I think Gnome may support it. The freedesktop 'menu' standard (where sub-menus can be generated from the categories in the .desktop files, and which also claims to allow legacy menus to be merged with the new standard) doesn't seem to have been adopted yet by anyone. The worst part, though, is that currently both KDE and Gnome store their .desktop files in different places, so that a .desktop that is available to KDE (and placed in /usr/lib/applnk) won't automatically appear in the Gnome menu, which looks in /usr/lib/applications. I presume that these things are being worked on in later releases of KDE and Gnome, but I don't know where to look for the current status of their adoption of the freedesktop.org standards. The above statements are probably true of KDE 3.1 since it doesn't use the proper /usr/share/applications layout. KDE 3.2 which is due to be released in about a month does use it. The location Gnome uses is correct. I have also noticed what might be considered as 'abuse' of these standards, presumably due to poor implementation of some fields. For example, /usr/share/applications/epiphany.desktop lists its Name as Web Browser; it should more correctly list its name as Epiphany and have a GenericName field containing Web Browser. I've already reported that, several months ago, to some Gnome people in #debian-devel, hopefully it will be fixed soon. Chris signature.asc Description: Digital signature
RE: Bug#223781: [RFA]: usemod-wiki -- Perl-based Wiki clone
Hi Peter, Alexander Wirt wrote: Am Fr, den 12.12.2003 schrieb Julian Mehnle um 15:32: Benjamin Drieu wrote: I no longer use usemod-wiki and thus have no time to maintain it. Package is in good shape, no serious bugs. Very few work is needed to maintain it as release cycle is quite long. The only one todo item is to package version 1.0, which requires some changes to the wiki database. Peter Gervai [EMAIL PROTECTED] has already made a package for this and is going to NMU usemod-wiki. But as he does not have time to adopt it, we need a new maintainer. As I'm using UseMod Wiki on a slew of Debian machines, I'd be more than willing to continue maintaining usemod-wiki, but I'm no Debian Developer, so I'd need a sponsor until I decide and manage to become one. I use it on some systems too, so I would be pleased to be your sponsor. Get in touch with me if you have packages ready for upload/inspection. Are you going to do an NMU wrt usemod-wiki 1.0? If yes, are you going to include an automatic upgrade mechanism for old singlebyte Wikis? If yes, I'll wait for that NMU before starting my own packaging work. Otherwise, would you mind sending me whatever you have packaged up for 1.0, so I can add an automatic upgrade mechanism (which I'd really like to include with the initial release of the 1.0 Debian package)?
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
Daniel Burrows ([EMAIL PROTECTED]): On Fri, Dec 12, 2003 at 04:11:08PM -0600, Chris Cheney [EMAIL PROTECTED] was heard to say: All that would do is make it consitently different from all other distributions. Assuming that they listed the proper Categories in their Categories: section all that would be needed, if we wanted to be ^ Isn't that a rather large assumption? The .desktop format is nice in that there are tools to manipulate the files [1] so changing this in the packaging is pretty clean. -Billy [1] http://www.freedesktop.org/Software/desktop-file-utils
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, Dec 12, 2003 at 04:11:08PM -0600, Chris Cheney [EMAIL PROTECTED] was heard to say: All that would do is make it consitently different from all other distributions. Assuming that they listed the proper Categories in their Categories: section all that would be needed, if we wanted to be ^ Isn't that a rather large assumption? Daniel -- / Daniel Burrows [EMAIL PROTECTED] ---\ | Almost Winter, Winter, Still Winter, and Construction.| \- The Turtle Moves! -- http://www.lspace.org /
Re: APT-Fu 0.2.3
Miles Bader [EMAIL PROTECTED] wrote:
Well I certainly have no idea of the historical background of the word,
but my `guessed derivation' does actually sort of make sense in that
context...
The reason I think it's incorrect is that although `fu' means husband,
it is not used to mean partner in any other context. In fact, all of
the a) entries (apart from a4) are always used to refer to people
which isn't appropriate here.
Actually, I did miss one interpretation which means manual labourer.
That may well be appropriate here.
Do you have a dictionary that gives the historical derivation?
I used
?
(that's UTF-8) as the reference.
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Accepted kernel-image-2.4.22-i386 2.4.22-2woody.2 (i386 source)
Arnaud Giersch [EMAIL PROTECTED] wrote:
The kernel-images are available in the woody-proposed-updates. They
depend on initrd-tools (= 0.1.32woody.5), but the latest available
version for Woody (including the woody-proposed-updates) is
0.1.32woody.3.
Should I report the bug through the BTS ? Against which package ?
I have uploaded 0.1.32woody.5 previously but it was rejected by the
Stable Release Manager.
You can get it from
http://master.debian.org/~herbert/woody/
--
Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, 12 Dec 2003, Chris Cheney wrote: On Wed, Dec 10, 2003 at 01:28:51PM -0700, Bruce Sass wrote: ... .desktop files are not bloated... period. They include i18n which for you is bloat since you obviously can communicate in English. not bloated... period, yet you admit the translations are bloat for someone who doesn't need them. Can you also accept the X-KDE-* stuff is bloat for every menu data consumer except KDE (ditto for Gnome specials), and that in general freedesktop features are bloat for everyone who doesn't support the freedesktop standard. As I mentioned further down in this message Konqueror only uses 159 bytes when all i18n is stripped from it. I see many debian menu files that are larger than this and they don't contain i18n either. I suspect those files contain more than one menu entry; KDE has a file per entry, menu uses a file per package which contain multiple menu entries. ... If several KDE and Gnome developers got together and rewrote the menu-methods for the various WM's would that satisfy you? No, because it doesn't address the primary concern of (say) a Fluxbox user needing to process the KDE, Gnome, and freedesktop stuff which they don't have a use for. ... 1 or 2 hundred bytes vs. a couple to few thousand bytes _per_entry_; what percentage of resources that takes depends on the system... it may be a drop in the bucket for KDE and Gnome users, who are likely to have very capable machines, but what about those who don't have the resources to run KDE or Gnome---why should they be stuck with processing useless stuff they likely can't afford and obviously don't want? The entire menu hierarchy is regenerated everytime a package containing a menu entry is installed or removed. I call bullshit on this one. desktop files with no i18n are not several thousand bytes _pre_entry_. And the fact that those other WM's don't support should be considered a bug not a feature... For example the Konqueror .desktop file is 159 bytes with no i18n or 2234 with it. If as we suggested earlier the Debian menu format gain i18n support then it would be just as big as .desktop (probably actually since Debian has very limited i18n support). Ok, the .desktop file sizes are typically between 1 and 2K---but you don't have to look too hard to find 3 or 4K .desktop files, and some of the (admitedly KDE specific) files are over 10K. Yup, that last bit is FUD: I fear it is the future of .desktop files, I'm uncertain they are atypical, and I doubt that 1-2K will be the norm... especially since the example (/usr/share/applnk/konqueror.desktop) you are holding up is 3748 bytes and incomplete (only 7 Name and over 3 dozen Comment items) on my box (unstable, updated daily). ... desktop/ can contain the generic .desktop data (translations and features common to all .desktop aware menu consumers), the gnome and kde dirs would contain the bits specific to them (X-KDE-*, etc.) Hahaha, you do realize how much extra effort that would entail? It would be much simpler for the Gnome and KDE maintainers to just rewrite all the converters and the menu package itself than to keep that up to date. Maybe I don't (although nobody has torn apart my most recent post regarding the scheme)... please enlighten me. - Bruce
Re: APT-Fu 0.2.3
On Sat, Dec 13, 2003 at 10:31:11AM +1100, Herbert Xu wrote: Miles Bader [EMAIL PROTECTED] wrote: Well I certainly have no idea of the historical background of the word, but my `guessed derivation' does actually sort of make sense in that context... [snip] I read the archives to make sure nobody already posted this. -fu has a entry in the jargon file: http://info.astrian.net/jargon/terms/f/-fu.html -fu [common; generalized from `kung-fu'] Combining form denoting expert practice of a skill. That's going to take some serious code-fu. First sighted in connection with the GIMP's remote-scripting facility, script-fu, in 1998.
Re: Building a distribution from source?
On Thu, Dec 11, 2003 at 12:10:06PM +1100, Russell Coker wrote: Let me know when you have an apt repository that's in a usable state and I'll recommend it on my SE Linux web pages. I expect that anyone who is interested in SE Linux will be interested in your work as well. This work has hit a snag with dependencies which I've currently hacked around. I want to use a patched compiler, so that's the thing that I started with. I was a little optomistic originally as I was working on unstable. On stable there are two main approaches: * Patch gcc-2.95 with the SSP code. * Backport gcc-3.3 with the SSP code already included. So far I've been going down the second course, getting the latest Debian unstable package and hacking it to build on stable (strange issues with internal compiler errors when building the pascal code, and issues with building the -doc package). Once those problems were resolved getting gcc-3.3 built on Debian stable was fairly trivial, just time consuming. (8 hours from start of compile to finish was my fastest recorded time!) After that there are dependencies to be followed before it can be installed, I'm unsure if I can ignore them so far: gcc-3.3: Depends: binutils (= 2.13.90.0.10) but 2.12.90.0.1-4 is installed libstdc++5-3.3-dev: Depends: libc6-dev (= 2.3.1) but 2.2.5-11.5 is installed binutils is a simple one to build, only relying upon Debian stable, and a more recent modutils. modutils was simple to build, just requiring the new package dpatch. After that the last dependencei is the libc6-dev package - getting v2.3.1 built on Debian stable appears to be involved. I have currently patched my UML image such that although libc6, libc6-dev and locales all are 2.5.5-11.5 they appear as 2.3.1, this satisfies the dependencies and allows things to proceed - but it's clearly the wrong solution. So .. progress is happening and I have a couple more routes to explore: 1. Telling libstdc++ that it can get by on an older libc 2. Abandoning this approach and getting the SSP code running on gcc-2.95 I have the packages I've built, but until I solve the libc problem they are not fit to be distributed. I'll keep updating the new pages: http://www.shellcode.org/Cat/ Steve --
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, Dec 12, 2003 at 06:33:52PM -0500, Daniel Burrows wrote: On Fri, Dec 12, 2003 at 04:11:08PM -0600, Chris Cheney [EMAIL PROTECTED] was heard to say: All that would do is make it consitently different from all other distributions. Assuming that they listed the proper Categories in their Categories: section all that would be needed, if we wanted to be ^ Isn't that a rather large assumption? If they aren't in the proper categories as listed by the standard it should be treated as any other bug and be corrected. That won't be the common case, and we can just write the convertor to look for the standardized categories. Chris signature.asc Description: Digital signature
Re: APT-Fu 0.2.3
On Sat, Dec 13, 2003 at 10:31:11AM +1100, Herbert Xu wrote: Miles Bader [EMAIL PROTECTED] wrote: Do you have a dictionary that gives the historical derivation? I used ? (that's UTF-8) as the reference. That seems to have got mangled into the nine question marks above, perhaps because your post didn't have a Content-Type: header to specify the character set. I checked in the raw list archives on master and it was indeed nine times ASCII 0x3f. -- Colin Watson [EMAIL PROTECTED]
Re: APT-Fu 0.2.3
On Fri, 2003-12-12 at 18:31, Herbert Xu wrote: ? (that's UTF-8) as the reference. But your message didn't include a Content-Type header specifying that, so it's likely to come through as garbage for most MUAs... signature.asc Description: This is a digitally signed message part
chrony_1.20-2 Released
I've uploaded chrony_1.20-2. It may have problems in the rtc stuff, especially on 440BX/GX boards. Please test it. Running the chronyc rtcdata command will suffice. To do so you will need 'Enhanced RTC' support in your kernel and will need to uncomment the rtcfile line in /etc/chrony/chrony.conf/ -- John Hasler [EMAIL PROTECTED] Dancing Horse Hill Elmwood, Wisconsin
Re: Debian packages and freedesktop.org (Gnome, KDE, etc) menu entries
On Fri, Dec 12, 2003 at 09:37:51AM -0500, Colin Walters wrote: On Fri, 2003-12-12 at 01:01, Marc Wilson wrote: Not at all. You want to enforce on $RANDOM_UPSTREAM the idea that they have to support .desktop files. That is *not* going to work. Debian does not have that sort of power. On the other hand, the idea that an application desiring to participate in the menu system being required to provide the necessary menu-method to get from .desktop files to their own format is much more reasonable. Upstream can create that, The above two paragraphs don't make sense to me, in combination. The rest of the second paragraph, which you clipped, make it plain that what I was doing was listing sources for the .desktop file-converting-menu-method. It could be provided by upstream, it could be created by the Debian package maintainer, it could be part of the menu package. In short, it could be created by just about anyone. If upstream can write code to convert from .desktop to their own format, why can't they just include that directly in their software? Perhaps THEY don't want to, but do want to allow their software to participate in the Debian menu system. It would be their choice, one way, or the other. -- Marc Wilson | Debian Hint #7: You can use the cron-apt package [EMAIL PROTECTED] | to do automatic nightly downloads of updates for | packages installed on your system. signature.asc Description: Digital signature
Re: Changes in formal naming for NetBSD porting effort(s)
On Fri, Dec 12, 2003 at 11:54:09AM -0500, Branden Robinson [EMAIL PROTECTED] wrote a message of 126 lines which said: Debian either needs a trademark license from the NetBSD Foundation for use of the NetBSD mark, or it does not. Legally speaking, you're right. Now, on more practical grounds, I do not think that the NetBSD Foundation threatened to sue us. I believe that they feared confusion and asked politely, as an humble request from fellow free software developers, to consider a change in the name. I do not think debian-legal is concerned: it is not an issue of being right with trademark law, it's an issue of not pissing off NetBSD people for no good reason.
Accepted pyvorbis 1.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 00:15:00 -0600 Source: pyvorbis Binary: python-pyvorbis Architecture: source i386 Version: 1.3-1 Distribution: unstable Urgency: low Maintainer: Christopher L Cheney [EMAIL PROTECTED] Changed-By: Christopher L Cheney [EMAIL PROTECTED] Description: python-pyvorbis - A Python interface to the Ogg Vorbis library Changes: pyvorbis (1.3-1) unstable; urgency=low . * Maintainer upload. Files: 5f3ec2669d53198820072245ba18cb55 646 interpreters optional pyvorbis_1.3-1.dsc c7e31c4b1711b5eec7c45fbc9b87438e 37768 interpreters optional pyvorbis_1.3.orig.tar.gz a90c7db1237b33ee82ff46dbb6d52302 2817 interpreters optional pyvorbis_1.3-1.diff.gz 28686160e471f47bab8fdd8f9676e1b4 32158 interpreters optional python-pyvorbis_1.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2V+B0QZas444SvIRAnrnAKCVNBPeI4V1oiptR38dhlCh7n7+rgCfbX5r TVyk0knTORAD5z+PNQebZXU= =nu2C -END PGP SIGNATURE- Accepted: python-pyvorbis_1.3-1_i386.deb to pool/main/p/pyvorbis/python-pyvorbis_1.3-1_i386.deb pyvorbis_1.3-1.diff.gz to pool/main/p/pyvorbis/pyvorbis_1.3-1.diff.gz pyvorbis_1.3-1.dsc to pool/main/p/pyvorbis/pyvorbis_1.3-1.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hddtemp 0.3-beta9-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 09:21:16 +0100 Source: hddtemp Binary: hddtemp Architecture: source i386 Version: 0.3-beta9-1 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: hddtemp- Utility to monitor the temperature of your hard drive Changes: hddtemp (0.3-beta9-1) unstable; urgency=low . * New upstream version. * Updated the database to version 03B. Files: c0d4d2f96dc7f66510cce0f4bc56a214 619 utils extra hddtemp_0.3-beta9-1.dsc f5bfc7ba8b76a29e5a3f2b159c098fbf 246342 utils extra hddtemp_0.3-beta9.orig.tar.gz 7cf25931c02b0611dc65e0d733c53012 15775 utils extra hddtemp_0.3-beta9-1.diff.gz 35f4f3723cf80003cd06691c437d6af4 35348 utils extra hddtemp_0.3-beta9-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2XrEw3ao2vG823MRAp98AJ9yBEAy+bdJ4Hvw99boPFYzYd9b+QCfeFGK bllAPl0FsHTvTJSYl8R6um4= =CPvn -END PGP SIGNATURE- Accepted: hddtemp_0.3-beta9-1.diff.gz to pool/main/h/hddtemp/hddtemp_0.3-beta9-1.diff.gz hddtemp_0.3-beta9-1.dsc to pool/main/h/hddtemp/hddtemp_0.3-beta9-1.dsc hddtemp_0.3-beta9-1_i386.deb to pool/main/h/hddtemp/hddtemp_0.3-beta9-1_i386.deb hddtemp_0.3-beta9.orig.tar.gz to pool/main/h/hddtemp/hddtemp_0.3-beta9.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hddtemp 0.3-beta9-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 09:31:19 +0100 Source: hddtemp Binary: hddtemp Architecture: source i386 Version: 0.3-beta9-2 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno [EMAIL PROTECTED] Changed-By: Aurelien Jarno [EMAIL PROTECTED] Description: hddtemp- Utility to monitor the temperature of your hard drive Changes: hddtemp (0.3-beta9-2) unstable; urgency=low . * Moved ja.po in the right directory. Files: f4af95254dc0585ae51a63a7817c7975 619 utils extra hddtemp_0.3-beta9-2.dsc ffca0e3ff7941146979c7d395a1526b9 15302 utils extra hddtemp_0.3-beta9-2.diff.gz 680a6624ed90913591663bb3398db851 36154 utils extra hddtemp_0.3-beta9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2X1Pw3ao2vG823MRAiDyAJ0X213NgLlVxJl+xmzo2519YfybcACeMIrk dPkW5JF9TAamDdTn7cPL9lw= =F4tF -END PGP SIGNATURE- Accepted: hddtemp_0.3-beta9-2.diff.gz to pool/main/h/hddtemp/hddtemp_0.3-beta9-2.diff.gz hddtemp_0.3-beta9-2.dsc to pool/main/h/hddtemp/hddtemp_0.3-beta9-2.dsc hddtemp_0.3-beta9-2_i386.deb to pool/main/h/hddtemp/hddtemp_0.3-beta9-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lvm10 1:1.0.8-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 7 Dec 2003 13:49:08 + Source: lvm10 Binary: lvm10 lvm10-udeb Architecture: source i386 Version: 1:1.0.8-2 Distribution: unstable Urgency: low Maintainer: Patrick Caulfield [EMAIL PROTECTED] Changed-By: Patrick Caulfield [EMAIL PROTECTED] Description: lvm10 - The Logical Volume Manager for Linux lvm10-udeb - The Logical Volume Manager for Linux (udeb) Closes: 221663 223112 Changes: lvm10 (1:1.0.8-2) unstable; urgency=low . * Include enough kernel headers so it will actually compile on buildd machines. LVM requires 2.4 kernel headers (yuk). Also fix lvm.h ioctl definitions so it doesn't need ioctl.h for all architectures in the above directory. Closes: #221663 * Fix typo in lvscan error message. * Add German translation: Closes: #223112 Files: 53bfcef3858076769ee53d73e5b59270 597 admin optional lvm10_1.0.8-2.dsc 3d2965a83aa1252b65b32a6ec153c0eb 22995 admin optional lvm10_1.0.8-2.diff.gz 472d9f38f21d09b204aa17687d667476 2568226 admin optional lvm10_1.0.8-2_i386.deb 6318095220f93cfda7aa2da8d37f17f8 141620 debian-installer extra lvm10-udeb_1.0.8-2_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/0zA4hej7/PCycRMRAhTlAJ4sa9Ra5gXe/pFNCp+a+Obk/NaM9ACgjnBi LIhO070SKWwDBkBF9elrWgQ= =CW2x -END PGP SIGNATURE- Accepted: lvm10-udeb_1.0.8-2_i386.udeb to pool/main/l/lvm10/lvm10-udeb_1.0.8-2_i386.udeb lvm10_1.0.8-2.diff.gz to pool/main/l/lvm10/lvm10_1.0.8-2.diff.gz lvm10_1.0.8-2.dsc to pool/main/l/lvm10/lvm10_1.0.8-2.dsc lvm10_1.0.8-2_i386.deb to pool/main/l/lvm10/lvm10_1.0.8-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted manpages 1.62-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 09:47:01 +0100 Source: manpages Binary: manpages manpages-dev Architecture: source all Version: 1.62-1 Distribution: unstable Urgency: low Maintainer: Martin Schulze [EMAIL PROTECTED] Changed-By: Martin Schulze [EMAIL PROTECTED] Description: manpages - Manual pages about using a GNU/Linux system manpages-dev - Manual pages about using GNU/Linux for development Changes: manpages (1.62-1) unstable; urgency=low . * New upstream version Files: bbb67333c9444c327d90d9831f3e479e 583 doc - manpages_1.62-1.dsc 84e70c57183a753678925c0e30545aca 913113 doc - manpages_1.62.orig.tar.gz cdcc1cfc970c703bdb61cac3ad615ade 46934 doc - manpages_1.62-1.diff.gz 73fb37835f4d45134361dda62baa7fd7 367970 doc important manpages_1.62-1_all.deb dc2c29c751feb50e014d77a3d8fe8be2 1022164 doc standard manpages-dev_1.62-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2YILW5ql+IAeqTIRAqcaAJwKUi/1iGF+OZ0WbtCYJzBySlB4egCfQ+dv jJjY/re1XiyifGwKe+9BdXU= =zlLA -END PGP SIGNATURE- Accepted: manpages-dev_1.62-1_all.deb to pool/main/m/manpages/manpages-dev_1.62-1_all.deb manpages_1.62-1.diff.gz to pool/main/m/manpages/manpages_1.62-1.diff.gz manpages_1.62-1.dsc to pool/main/m/manpages/manpages_1.62-1.dsc manpages_1.62-1_all.deb to pool/main/m/manpages/manpages_1.62-1_all.deb manpages_1.62.orig.tar.gz to pool/main/m/manpages/manpages_1.62.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted cupsys 1.1.20final-3 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 18:32:58 +0900 Source: cupsys Binary: cupsys-bsd libcupsys2-dev libcupsys2 cupsys libcupsimage2-dev libcupsimage2 cupsys-client Architecture: source i386 Version: 1.1.20final-3 Distribution: unstable Urgency: low Maintainer: Kenshi Muto [EMAIL PROTECTED] Changed-By: Kenshi Muto [EMAIL PROTECTED] Description: cupsys - Common UNIX Printing System(tm) - server cupsys-bsd - Common UNIX Printing System(tm) - BSD commands cupsys-client - Common UNIX Printing System(tm) - client programs (SysV) libcupsimage2 - Common UNIX Printing System(tm) - image libs libcupsimage2-dev - Common UNIX Printing System(tm) - image development files libcupsys2 - Common UNIX Printing System(tm) - libs libcupsys2-dev - Common UNIX Printing System(tm) - development files Closes: 223432 223748 Changes: cupsys (1.1.20final-3) unstable; urgency=low . * Apply patch into lpd.c for true compatible with RFC1179 (closes: Bug#223432). Thanks Lionel. * Hmm, PJL patch causes a problem. Since I don't have any PJL printers, I simply unapply PJL patch and reopen Bug#220611 (closes: Bug#223748) Files: 9d1fbda41cf95fc76af6163a87af1bb4 810 net optional cupsys_1.1.20final-3.dsc 2871aeee7cd3a91c311c2f38c5230269 1261888 net optional cupsys_1.1.20final-3.diff.gz d9c3428d7cab71cf908e7fe9a1913ed3 3583880 net optional cupsys_1.1.20final-3_i386.deb 3f51a928cd3fe647a1904abb2114e3aa 100874 net optional cupsys-client_1.1.20final-3_i386.deb 89abd835dc60cfae38af9174c7ea8efb 68810 libs optional libcupsys2_1.1.20final-3_i386.deb 099a68db84d52d84616eac1c24d8873f 95594 libdevel optional libcupsys2-dev_1.1.20final-3_i386.deb 2089f9e1840f4f87ba7c1d3450cf8624 49064 libs optional libcupsimage2_1.1.20final-3_i386.deb 0641d66d6640258fe2b98ad4e54eafef 58528 libdevel optional libcupsimage2-dev_1.1.20final-3_i386.deb cf8a1966dd88c3c83e57499c4669e593 53052 net extra cupsys-bsd_1.1.20final-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iEYEARECAAYFAj/ZjbkACgkQQKW+7XLQPLFZGgCggK52c49oQ1wkIwzAGG3pLPce P3cAn3JMRuyYQBSaoC0WOdwNu3eDxeou =27FA -END PGP SIGNATURE- Accepted: cupsys-bsd_1.1.20final-3_i386.deb to pool/main/c/cupsys/cupsys-bsd_1.1.20final-3_i386.deb cupsys-client_1.1.20final-3_i386.deb to pool/main/c/cupsys/cupsys-client_1.1.20final-3_i386.deb cupsys_1.1.20final-3.diff.gz to pool/main/c/cupsys/cupsys_1.1.20final-3.diff.gz cupsys_1.1.20final-3.dsc to pool/main/c/cupsys/cupsys_1.1.20final-3.dsc cupsys_1.1.20final-3_i386.deb to pool/main/c/cupsys/cupsys_1.1.20final-3_i386.deb libcupsimage2-dev_1.1.20final-3_i386.deb to pool/main/c/cupsys/libcupsimage2-dev_1.1.20final-3_i386.deb libcupsimage2_1.1.20final-3_i386.deb to pool/main/c/cupsys/libcupsimage2_1.1.20final-3_i386.deb libcupsys2-dev_1.1.20final-3_i386.deb to pool/main/c/cupsys/libcupsys2-dev_1.1.20final-3_i386.deb libcupsys2_1.1.20final-3_i386.deb to pool/main/c/cupsys/libcupsys2_1.1.20final-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tinysnmp 0.6.1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 11 Dec 2003 23:39:12 +0200 Source: tinysnmp Binary: tinysnmp-tools tinysnmp-dev tinysnmp-module-resources tinysnmp-module-mib2 tinysnmp-agent-dev tinysnmp-manager-dev tinysnmp-agent Architecture: source i386 all Version: 0.6.1 Distribution: unstable Urgency: low Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: tinysnmp-agent - A lightweight SNMPv1 implementation tinysnmp-agent-dev - Libraries and header files for developing TinySNMP plugins tinysnmp-dev - Files needed for developing TinySNMP programs and plugins tinysnmp-manager-dev - Libraries and header files for developing TinySNMP programs tinysnmp-module-mib2 - MIB-2 (RFC 1450) plugin for TinySNMP tinysnmp-module-resources - Frogfoot Networks Resources MIB plugin for TinySNMP tinysnmp-tools - TinySNMP Utilities Closes: 218352 221414 221857 223221 Changes: tinysnmp (0.6.1) unstable; urgency=low . * Complete rewrite of agent. The agent now uses libevent and should be much faster. * New Cisco-like configuration file format and all the modules share the same configuration file as the agent. * New plugin library API. * Removed traffic modules and daemons. MIB has to be redesigned and reimplemented. * Lots of compatibility fixes/updates (Closes: #218352, #221414, #223221) * Better documentation. * Pipe stderr to /dev/null in logrotate script (Closes: #221857) Files: 9d93cc442426d0ff98755dbd656d0d6d 708 net optional tinysnmp_0.6.1.dsc f40bf0daa20eebc31065fd3a51129ba2 56973 net optional tinysnmp_0.6.1.tar.gz 5b102e8110d90b76c3bb81b5ec6ebf9e 8836 devel optional tinysnmp-agent-dev_0.6.1_all.deb 39bfeb4e908b3e0ea0a15a2ab3945f7b 10018 devel optional tinysnmp-dev_0.6.1_i386.deb 6b4cddc093756b01c4ba66df8cc2e22b 12870 devel optional tinysnmp-manager-dev_0.6.1_i386.deb 603149238437f61035214263f1de10c1 24252 net optional tinysnmp-tools_0.6.1_i386.deb 837cfef05f23f3513989fe4b58fb4831 26696 net optional tinysnmp-agent_0.6.1_i386.deb dd4b7545cbc12220de18c5270d00927c 10390 net optional tinysnmp-module-mib2_0.6.1_i386.deb afd6e5e1894a05b8b08fbbf4e55ca595 9108 net optional tinysnmp-module-resources_0.6.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2ZhDzvVjZitVWu4RAhYNAJ9OO15d2Dbh17LY0fvVlqSdHanchwCfRhAc ZX4AIhLZes8PnJ52J9yndeA= =d2jk -END PGP SIGNATURE- Accepted: tinysnmp-agent-dev_0.6.1_all.deb to pool/main/t/tinysnmp/tinysnmp-agent-dev_0.6.1_all.deb tinysnmp-agent_0.6.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-agent_0.6.1_i386.deb tinysnmp-dev_0.6.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-dev_0.6.1_i386.deb tinysnmp-manager-dev_0.6.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-manager-dev_0.6.1_i386.deb tinysnmp-module-mib2_0.6.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-module-mib2_0.6.1_i386.deb tinysnmp-module-resources_0.6.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-module-resources_0.6.1_i386.deb tinysnmp-tools_0.6.1_i386.deb to pool/main/t/tinysnmp/tinysnmp-tools_0.6.1_i386.deb tinysnmp_0.6.1.dsc to pool/main/t/tinysnmp/tinysnmp_0.6.1.dsc tinysnmp_0.6.1.tar.gz to pool/main/t/tinysnmp/tinysnmp_0.6.1.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libber 0.3.2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 9 Dec 2003 17:27:02 +0200 Source: libber Binary: libber0-dev libber0 Architecture: source i386 Version: 0.3.2 Distribution: unstable Urgency: low Maintainer: Abraham vd Merwe [EMAIL PROTECTED] Changed-By: Abraham vd Merwe [EMAIL PROTECTED] Description: libber0- A Basic Encoding Rules (ITU X.690) implementation libber0-dev - Development files for the BER library Changes: libber (0.3.2) unstable; urgency=low . * Fixed buffer overflow in makeoid(). * Renamed make_oid() to makeoid(). * Minor bugfixes in regression test programs. Files: 4b3a653dab47c59d6d159e889bc1fc9a 551 devel optional libber_0.3.2.dsc 7707385610a9800d52cee65405e50c08 18265 devel optional libber_0.3.2.tar.gz 63238bd0ce0f74057fb0d97752edb596 8786 libs optional libber0_0.3.2_i386.deb 1700a84b12e932df191250d1a31da6a1 22440 libdevel optional libber0-dev_0.3.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/1e5JzvVjZitVWu4RAnLJAJ0fF6Z22P6PGfP+uRTs4Y5VxR6a8gCgnFak rN1tDcbnJ+oY3zkdOPQNQjg= =CzX4 -END PGP SIGNATURE- Accepted: libber0-dev_0.3.2_i386.deb to pool/main/libb/libber/libber0-dev_0.3.2_i386.deb libber0_0.3.2_i386.deb to pool/main/libb/libber/libber0_0.3.2_i386.deb libber_0.3.2.dsc to pool/main/libb/libber/libber_0.3.2.dsc libber_0.3.2.tar.gz to pool/main/libb/libber/libber_0.3.2.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted intlfonts 1.2.1-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 12:15:24 +0100 Source: intlfonts Binary: emacs-intl-fonts xfonts-intl-chinese-big xfonts-intl-japanese-big xfonts-intl-asian xfonts-intl-arabic xfonts-intl-european xfonts-intl-chinese xfonts-intl-japanese xfonts-intl-phonetic Architecture: source all Version: 1.2.1-2 Distribution: unstable Urgency: low Maintainer: Milan Zamazal [EMAIL PROTECTED] Changed-By: Milan Zamazal [EMAIL PROTECTED] Description: emacs-intl-fonts - Fonts to allow multi-lingual PostScript printing from Emacs xfonts-intl-arabic - International fonts for X -- Arabic xfonts-intl-asian - International fonts for X -- Asian xfonts-intl-chinese - International fonts for X -- Chinese xfonts-intl-chinese-big - International fonts for X -- Chinese big xfonts-intl-european - International fonts for X -- European xfonts-intl-japanese - International fonts for X -- Japanese xfonts-intl-japanese-big - International fonts for X -- Japanese big xfonts-intl-phonetic - International fonts for X -- Phonetic Alphabet Closes: 210053 210178 Changes: intlfonts (1.2.1-2) unstable; urgency=low . * Package descriptions improved, thanks to Marek Habersack [EMAIL PROTECTED]; closes: #210053, #210178. Files: 0ad0f232f7bc9bb60a5b4abdebbe6376 766 x11 optional intlfonts_1.2.1-2.dsc 910c23dfa54cd25abaaf2fc4f86a6a2c 6877 x11 optional intlfonts_1.2.1-2.diff.gz 2732066fa1cff3b79c3917f10ee57cd1 17232 x11 optional xfonts-intl-arabic_1.2.1-2_all.deb b10155bc0f379fb353d03df600305e85 104356 x11 optional xfonts-intl-asian_1.2.1-2_all.deb cc058ca5a0ccdc0ef7b1bf800543e75b 5784840 x11 optional xfonts-intl-chinese_1.2.1-2_all.deb 1ff20d42ca4e3510458f1b60742655d4 1814752 x11 optional xfonts-intl-chinese-big_1.2.1-2_all.deb dd86c808afc7e9ffb97fb68a6e3eaca2 156492 x11 optional xfonts-intl-european_1.2.1-2_all.deb ec5f72a66e80d0697e315dfc5c8b8701 932952 x11 optional xfonts-intl-japanese_1.2.1-2_all.deb a03eec5b0a3150ca11fc37e14668eabd 657892 x11 optional xfonts-intl-japanese-big_1.2.1-2_all.deb f88fdabe9dcf3aa61372a0dc78e085d0 11848 x11 optional xfonts-intl-phonetic_1.2.1-2_all.deb 5c4ec11092e667460589d6e1f80af3eb 2523962 x11 optional emacs-intl-fonts_1.2.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2aO8kSkk/j3Cm0ERAn3bAJ96r6ZGPMoF0GqGwDb/G5xyz4CJCwCeNayA qvDWywP5wM+2ZUWAulH3vGw= =xguG -END PGP SIGNATURE- Accepted: emacs-intl-fonts_1.2.1-2_all.deb to pool/main/i/intlfonts/emacs-intl-fonts_1.2.1-2_all.deb intlfonts_1.2.1-2.diff.gz to pool/main/i/intlfonts/intlfonts_1.2.1-2.diff.gz intlfonts_1.2.1-2.dsc to pool/main/i/intlfonts/intlfonts_1.2.1-2.dsc xfonts-intl-arabic_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-arabic_1.2.1-2_all.deb xfonts-intl-asian_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-asian_1.2.1-2_all.deb xfonts-intl-chinese-big_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-chinese-big_1.2.1-2_all.deb xfonts-intl-chinese_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-chinese_1.2.1-2_all.deb xfonts-intl-european_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-european_1.2.1-2_all.deb xfonts-intl-japanese-big_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-japanese-big_1.2.1-2_all.deb xfonts-intl-japanese_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-japanese_1.2.1-2_all.deb xfonts-intl-phonetic_1.2.1-2_all.deb to pool/main/i/intlfonts/xfonts-intl-phonetic_1.2.1-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gnatsweb 3.beta99.2+cvs20011113-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 12:38:56 +0100 Source: gnatsweb Binary: gnatsweb Architecture: source all Version: 3.beta99.2+cvs2003-2 Distribution: unstable Urgency: low Maintainer: Debian QA Group [EMAIL PROTECTED] Changed-By: Milan Zamazal [EMAIL PROTECTED] Description: gnatsweb - Web interface to GNU GNATS Changes: gnatsweb (3.beta99.2+cvs2003-2) unstable; urgency=low . * Officially orphaned. Files: ef842876ec99a227c7ca6199fd068336 617 devel extra gnatsweb_3.beta99.2+cvs2003-2.dsc 333232771d41eac7a276906bb68b740f 2050 devel extra gnatsweb_3.beta99.2+cvs2003-2.diff.gz 810ad5416e3a90673b3580efd78fb58c 54076 devel extra gnatsweb_3.beta99.2+cvs2003-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2ajzkSkk/j3Cm0ERAguJAJ97DuojXvP/GAQN+PCFjlPc9yGCbgCfUGgu QmtCTCeoo/anb3cCRPOR7i8= =njQT -END PGP SIGNATURE- Accepted: gnatsweb_3.beta99.2+cvs2003-2.diff.gz to pool/main/g/gnatsweb/gnatsweb_3.beta99.2+cvs2003-2.diff.gz gnatsweb_3.beta99.2+cvs2003-2.dsc to pool/main/g/gnatsweb/gnatsweb_3.beta99.2+cvs2003-2.dsc gnatsweb_3.beta99.2+cvs2003-2_all.deb to pool/main/g/gnatsweb/gnatsweb_3.beta99.2+cvs2003-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted alsa-driver 0.9.8-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 23:35:01 +1100 Source: alsa-driver Binary: alsaconf alsa-source alsa-headers alsa-base Architecture: source all Version: 0.9.8-2 Distribution: unstable Urgency: low Maintainer: Debian-Alsa Psychos [EMAIL PROTECTED] Changed-By: Steve Kowalik [EMAIL PROTECTED] Description: alsa-base - ALSA sound driver common files alsa-headers - ALSA sound driver header files alsa-source - ALSA sound driver source alsaconf - ALSA configuration generator Closes: 216253 221038 221292 221295 221809 05 222349 222350 223103 Changes: alsa-driver (0.9.8-2) unstable; urgency=low . * Steve Kowalik: - Stop the init script bombing out if it can't load any driver modules. (Closes: #221038) - Drop debconf question about loading OSS compatibility modules. We now perform auto-detection during boot-up. (Closes: #222350) - Bump the Depends on lsof to (= 4.64-1). (Closes: #221295, #221809) - Apply patch to the init script so that it will work with both modules configured, or ALSA compiled statically. (Closes: #221292) - Drop Depends on kernel-image to Recommends. (Closes: #216253) - Add six new cards to the debconf list. (Closes: #05) + au8810 (PCI: Aureal Advantage) + au8820 (PCI: Aureal Vortex) + au8830 (PCI: Aureal Vortex 2) + mixart (PCI: Digigram miXart) + pdaudiocf (PCMCIA: Sound Core PDAudioCF) + usb-us428 (USB: Tascam USB US-428) - Remove all the instances of the word 'driver' from the debconf list. - Mention alsaconf in alsa-base's README.Debian. (Closes: #222349) - Use the user's /etc/default/alsa to run sed over, rather than the default example. - Don't Build-Depend on kernel-headers. - Bump alsa-source's pseudo-source package's Standards-Version to 3.6.1. * Jordi Mallach: - debian/control: make alsa-base conflict with old lsof-2.2, just in case. - debian/po/de.po: German translation update (thanks, Patrick Willam, Tomas and Friedemann; closes: #223103). Files: 4cd96a5237dde581238ddba731b2986e 806 sound optional alsa-driver_0.9.8-2.dsc 8949a1d1cf368c650a819aeae2a39602 118824 sound optional alsa-driver_0.9.8-2.diff.gz 9db538dc6a6b8190f2dc80cce41a04f8 49696 sound optional alsa-base_0.9.8-2_all.deb 8fcd21c4afa30426be35411f4410da22 1707736 sound optional alsa-source_0.9.8-2_all.deb 959416f15b8c9cc3b94de0b0340af5d5 53426 sound optional alsa-headers_0.9.8-2_all.deb 8077ef2f6464689755d2eea37142b1fe 40044 sound extra alsaconf_0.9.8-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2bm0JYSUupF6Il4RAsvBAJ9lTeDpPUJLJzviMgzF7Kn/HqpSFgCgwfOV AALEMk7tK3fofYoL/3XOHmY= =zz+l -END PGP SIGNATURE- Accepted: alsa-base_0.9.8-2_all.deb to pool/main/a/alsa-driver/alsa-base_0.9.8-2_all.deb alsa-driver_0.9.8-2.diff.gz to pool/main/a/alsa-driver/alsa-driver_0.9.8-2.diff.gz alsa-driver_0.9.8-2.dsc to pool/main/a/alsa-driver/alsa-driver_0.9.8-2.dsc alsa-headers_0.9.8-2_all.deb to pool/main/a/alsa-driver/alsa-headers_0.9.8-2_all.deb alsa-source_0.9.8-2_all.deb to pool/main/a/alsa-driver/alsa-source_0.9.8-2_all.deb alsaconf_0.9.8-2_all.deb to pool/main/a/alsa-driver/alsaconf_0.9.8-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted hypermail 2.1.8-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 20:41:05 +0800 Source: hypermail Binary: hypermail Architecture: source i386 Version: 2.1.8-1 Distribution: unstable Urgency: low Maintainer: Yu Guanghui [EMAIL PROTECTED] Changed-By: Yu Guanghui [EMAIL PROTECTED] Description: hypermail - Create HTML archives of mailing lists Changes: hypermail (2.1.8-1) unstable; urgency=low . * New upstream release Files: f0f8b01904581cf5147ba91956539bf3 601 web optional hypermail_2.1.8-1.dsc bacd95589f2f3ca426631461fd9237dd 1238173 web optional hypermail_2.1.8.orig.tar.gz 8bff2a980d6bfd73167c1ac763851dc1 29205 web optional hypermail_2.1.8-1.diff.gz 56f24a1368dbf69140fcc0deaa787f46 256068 web optional hypermail_2.1.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2boEKNPoKRflcycRAq0CAJ0Y+2UqKz/hNix/P0BkmYIA/aXXVACfYHko kZqFzPPiY/qD8tKwXQWBcAE= =Psap -END PGP SIGNATURE- Accepted: hypermail_2.1.8-1.diff.gz to pool/main/h/hypermail/hypermail_2.1.8-1.diff.gz hypermail_2.1.8-1.dsc to pool/main/h/hypermail/hypermail_2.1.8-1.dsc hypermail_2.1.8-1_i386.deb to pool/main/h/hypermail/hypermail_2.1.8-1_i386.deb hypermail_2.1.8.orig.tar.gz to pool/main/h/hypermail/hypermail_2.1.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted zh-autoconvert 0.3.14-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 21:15:42 +0800 Source: zh-autoconvert Binary: libhz-dev libhz0 zh-autoconvert Architecture: source i386 Version: 0.3.14-1 Distribution: unstable Urgency: low Maintainer: Yu Guanghui [EMAIL PROTECTED] Changed-By: Yu Guanghui [EMAIL PROTECTED] Description: libhz-dev - Headers and static libraries for zh-autoconvert libhz0 - Chinese encoding autoconvert library zh-autoconvert - Chinese HZ/GB/BIG5/UNI/UTF7/UTF8 encodings auto-converter Changes: zh-autoconvert (0.3.14-1) unstable; urgency=low . * New upstream release Files: 7f76952148da66900dae6ce35cadce3d 622 - optional zh-autoconvert_0.3.14-1.dsc 3023068ab9cc7aaa25b8b294698c4b39 464192 - optional zh-autoconvert_0.3.14.orig.tar.gz 67ff9c7837b0064bfdd1f11a308a823e 4996 - optional zh-autoconvert_0.3.14-1.diff.gz 8d757857b137d813127bade7c25f4f80 221966 text optional zh-autoconvert_0.3.14-1_i386.deb f2e7e76c050017e48b7754ecd4f386e0 155178 devel optional libhz-dev_0.3.14-1_i386.deb f7668f3631698f72085f1f5d1f5dd938 155838 libs optional libhz0_0.3.14-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2cBOKNPoKRflcycRArqmAKD3+ckcnxuu46UgXvYueWWcgJJj7wCfa+E5 K/OqCsmo8IEoyF6ZHXfhQEU= =+8y/ -END PGP SIGNATURE- Accepted: libhz-dev_0.3.14-1_i386.deb to pool/main/z/zh-autoconvert/libhz-dev_0.3.14-1_i386.deb libhz0_0.3.14-1_i386.deb to pool/main/z/zh-autoconvert/libhz0_0.3.14-1_i386.deb zh-autoconvert_0.3.14-1.diff.gz to pool/main/z/zh-autoconvert/zh-autoconvert_0.3.14-1.diff.gz zh-autoconvert_0.3.14-1.dsc to pool/main/z/zh-autoconvert/zh-autoconvert_0.3.14-1.dsc zh-autoconvert_0.3.14-1_i386.deb to pool/main/z/zh-autoconvert/zh-autoconvert_0.3.14-1_i386.deb zh-autoconvert_0.3.14.orig.tar.gz to pool/main/z/zh-autoconvert/zh-autoconvert_0.3.14.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted openbox 3.0-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 14:59:21 +0100 Source: openbox Binary: openbox Architecture: source i386 Version: 3.0-2 Distribution: unstable Urgency: low Maintainer: Tore Anderson [EMAIL PROTECTED] Changed-By: Tore Anderson [EMAIL PROTECTED] Description: openbox- Standards compliant, fast, light-weight, extensible window manage Closes: 221868 222900 Changes: openbox (3.0-2) unstable; urgency=low . * debian/openbox.menu-method: - Ascertain that the five XML reserved characters are translated into their respective entities, closes: #221868. - Set output encoding to UTF-8. - Remove unused openbox supported type. . * debian/openbox.menu: - Add an entry for the restart action, closes: #222900. Files: 6ebbd08b18b60ce6205f8f56844b4301 679 x11 optional openbox_3.0-2.dsc c9011d4df2807d47b2f7ffbad66325e3 7190 x11 optional openbox_3.0-2.diff.gz 79a6d5bcd62803698ac0919a4be97c3e 194100 x11 optional openbox_3.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2dPr/8x4SxA9OY8RAtkMAKCZYXK/T83Ta+b8fn5g4jPiFBYfaQCeII5c J2tR7SxoVZJjkA4kQ7LqOeE= =M6tI -END PGP SIGNATURE- Accepted: openbox_3.0-2.diff.gz to pool/main/o/openbox/openbox_3.0-2.diff.gz openbox_3.0-2.dsc to pool/main/o/openbox/openbox_3.0-2.dsc openbox_3.0-2_i386.deb to pool/main/o/openbox/openbox_3.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted eximdoc4 4.30-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 4 Dec 2003 14:38:08 +0100 Source: eximdoc4 Binary: exim4-doc-html eximdoc4-html exim4-doc-info eximdoc4-info Architecture: source all Version: 4.30-1 Distribution: unstable Urgency: low Maintainer: Andreas Metzler [EMAIL PROTECTED] Changed-By: Andreas Metzler [EMAIL PROTECTED] Description: exim4-doc-html - Documentation for Exim v4 in html format exim4-doc-info - Documentation for Exim v4 in info format eximdoc4-html - Dummy package for upgrade purposes only eximdoc4-info - Dummy package for upgrade purposes only Closes: 202501 Changes: eximdoc4 (4.30-1) unstable; urgency=low . * New upstream version 4.30. - fixes stray formatting (font color) on info-pages. (Closes: #202501) * Correct doc-base entries. Files: 72982ed2993341a544f265a5ba288819 688 doc optional eximdoc4_4.30-1.dsc 828cd37b75c11289c3539938fe37f802 818286 doc optional eximdoc4_4.30.orig.tar.gz aa38d1d8705dccff108c45ccef00bf73 2827 doc optional eximdoc4_4.30-1.diff.gz e1779afd66292f2f585a9be6816e3a32 444170 doc optional exim4-doc-info_4.30-1_all.deb 0ec131b62ff95e251696150f9dd0fc65 767746 doc optional exim4-doc-html_4.30-1_all.deb 9134c39f51faac62a35f6be522ef1172 2330 doc optional eximdoc4-info_4.30-1_all.deb a8346a87bd8ba2336085bbf4a85d5380 2332 doc optional eximdoc4-html_4.30-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/2eHOHTOcZYuNdmMRAoPaAJ4shL/nn1EcKJIhjANcbG8BmnOVmQCfTDG6 AbcHpKS5vUQIEM/3UDAaCI0= =yXb6 -END PGP SIGNATURE- Accepted: exim4-doc-html_4.30-1_all.deb to pool/main/e/eximdoc4/exim4-doc-html_4.30-1_all.deb exim4-doc-info_4.30-1_all.deb to pool/main/e/eximdoc4/exim4-doc-info_4.30-1_all.deb eximdoc4-html_4.30-1_all.deb to pool/main/e/eximdoc4/eximdoc4-html_4.30-1_all.deb eximdoc4-info_4.30-1_all.deb to pool/main/e/eximdoc4/eximdoc4-info_4.30-1_all.deb eximdoc4_4.30-1.diff.gz to pool/main/e/eximdoc4/eximdoc4_4.30-1.diff.gz eximdoc4_4.30-1.dsc to pool/main/e/eximdoc4/eximdoc4_4.30-1.dsc eximdoc4_4.30.orig.tar.gz to pool/main/e/eximdoc4/eximdoc4_4.30.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted kwiki 0.18-2 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 11 Dec 2003 21:23:59 + Source: kwiki Binary: kwiki Architecture: source all Version: 0.18-2 Distribution: unstable Urgency: low Maintainer: Michael D. Ivey [EMAIL PROTECTED] Changed-By: Michael D. Ivey [EMAIL PROTECTED] Description: kwiki - A Quickie Wiki that's not too Tricky Closes: 222512 Changes: kwiki (0.18-2) unstable; urgency=low . * Added dependency on undeclared dep liblocale-maketext-perl (not liblocale-gettext-perl as the bug states...) (Closes: #222512) Files: b957d88098fc7cade07ec3db0c1a7fd7 568 web optional kwiki_0.18-2.dsc 31215694c2e160838566fca93b009f1b 2286 web optional kwiki_0.18-2.diff.gz 0945724b1e08cc0739b7e7bda91c02c5 110824 web optional kwiki_0.18-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/2eMjxshy4ONJOMcRAkXRAJkBDYCcZlTtCuVh5VADOecJxfy/XACgjSkQ 4C5mBjTLtppvUsKZujc4ApQ= =vAkA -END PGP SIGNATURE- Accepted: kwiki_0.18-2.diff.gz to pool/main/k/kwiki/kwiki_0.18-2.diff.gz kwiki_0.18-2.dsc to pool/main/k/kwiki/kwiki_0.18-2.dsc kwiki_0.18-2_all.deb to pool/main/k/kwiki/kwiki_0.18-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted exim4 4.30-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 8 Dec 2003 16:52:32 +0100 Source: exim4 Binary: eximon4 exim4-daemon-custom exim4-daemon-heavy exim4-base exim4 exim4-daemon-light exim4-config Architecture: source i386 all Version: 4.30-1 Distribution: unstable Urgency: low Maintainer: Andreas Metzler [EMAIL PROTECTED] Changed-By: Andreas Metzler [EMAIL PROTECTED] Description: exim4 - An MTA (Mail Transport Agent) exim4-base - EXperimental Internal Mailer -- a Mail Transport Agent exim4-config - Debian configuration for exim4 exim4-daemon-heavy - Exim (v4) with extended features, including exiscan-acl exim4-daemon-light - Lightweight version of the Exim (v4) MTA eximon4- X monitor for the Exim (v4) mail transport agent Closes: 202136 214853 219781 220694 221458 221468 221838 222521 222773 Changes: exim4 (4.30-1) unstable; urgency=low . * Exim now runs under its own uid (Debian-exim) instead of using mail:mail. (am) . WARNING: You cannot downgrade this version to an older one without manual chown|chgrp all files owned by Debian-exim to mail. . - control: dependency on adduser and virtual package exim4-config-2 to force review of external -config packages. - use a statoverride for passwd.client. - different postinst scripts: * adduser. * chown|chgrp files/directories owned by mail (group|user) to Debian-exim. * update-exim4.conf does not exit immidiately if /etc/exim4/exim4.conf exists AND -o is specified. (Bill Moseley) * Brazilian Portuguese debconf template translation by André Luís Lopes (Closes: #219781) * Dutch debconf template translation by Bart Cornelis (cobaco) (Closes: #220694) * Pull Dansk debconf template translation from ddtp. * Use a macro to make it possible to overide the value of spool_directory with -DSPOOLDIR=. Needed for mailscanner, (Closes: #221468), suggested by Matthias Klose. * enable support for Cyrus saslauthd (package sasl2-bin, /var/run/saslauthd/mux) for SMTP AUTH against /etc/shadow. (am) * Christian Perrier has reviewed the debconf-templates and changed them to follow the Debconf Templates Style Guide. (Closes: #221838) Thanks to the (ru|nl|fr|pt_BR) translators for updating their translations. * New upstream version 4.30 with exiscan 4.30-14 (am) - option table for -d in exim(8) readable (but not perfect). (Closes: #214853) - Messages for configuration errors now include the name of the main configuration files (Closes: #202136) - does not reject IPv6 address literals in EHLO/HELO anymore (Closes: #222521) * exim4-config.config: support going back to previous *package* when invoked by base-config 2.0. (Closes: #222773). Suggested by Joey Hess. (am) * exim4-config now conflicts with non-exim4 packages providing MTA, to keep dselect from automatically installing it (and -base) on dist-upgrades on systems that use a different MTA. (mh) * exim4-base depends on netbase again because exim requires /etc/services.(mh) * reindent init-script with two spaces instead of tabs to fit it in 80 chars/line. (Closes: #221458) Files: 4958827c39e154b5a2aa6e190ddc1f4e 915 mail important exim4_4.30-1.dsc ba8fe22a527172bc3cf6481ba26712cb 1670421 mail important exim4_4.30.orig.tar.gz 7f010110a854336f4b036c434d8217e5 261136 mail important exim4_4.30-1.diff.gz 53d855c492be6d9731cb67cbf240a09c 723950 mail important exim4-base_4.30-1_i386.deb 91f3eedcd316ff2b723af3b5217f2832 335172 mail important exim4-daemon-light_4.30-1_i386.deb 25c60c45c8d079aea63565226252f0b4 61868 mail optional eximon4_4.30-1_i386.deb eb17880cc6ba89270d1392624bbce76e 398212 mail optional exim4-daemon-heavy_4.30-1_i386.deb 487c1e136fb491e50934745e87458d68 75732 mail important exim4-config_4.30-1_all.deb e8ebe12a2bc9ccd58036c7db942da071 852 mail important exim4_4.30-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/2enHHTOcZYuNdmMRAkYjAJ40DgXoCVAlFdvIg7Cjd3BA0hJdJgCgmefG 1nTMpgNOX91F+y1FJ9GTL+Y= =XFla -END PGP SIGNATURE- Accepted: exim4-base_4.30-1_i386.deb to pool/main/e/exim4/exim4-base_4.30-1_i386.deb exim4-config_4.30-1_all.deb to pool/main/e/exim4/exim4-config_4.30-1_all.deb exim4-daemon-heavy_4.30-1_i386.deb to pool/main/e/exim4/exim4-daemon-heavy_4.30-1_i386.deb exim4-daemon-light_4.30-1_i386.deb to pool/main/e/exim4/exim4-daemon-light_4.30-1_i386.deb exim4_4.30-1.diff.gz to pool/main/e/exim4/exim4_4.30-1.diff.gz exim4_4.30-1.dsc to pool/main/e/exim4/exim4_4.30-1.dsc exim4_4.30-1_all.deb to pool/main/e/exim4/exim4_4.30-1_all.deb exim4_4.30.orig.tar.gz to pool/main/e/exim4/exim4_4.30.orig.tar.gz eximon4_4.30-1_i386.deb to pool/main/e/exim4/eximon4_4.30-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ctxextensions 3.1.2003112501-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 14:18:37 +0900 Source: ctxextensions Binary: mozilla-ctxextensions Architecture: source all Version: 3.1.2003112501-1 Distribution: unstable Urgency: low Maintainer: Mike Hommey [EMAIL PROTECTED] Changed-By: Mike Hommey [EMAIL PROTECTED] Description: mozilla-ctxextensions - Context Menu Extensions for Mozilla Changes: ctxextensions (3.1.2003112501-1) unstable; urgency=low . * New upstream release Files: 86e7cab58880c238ee949b333b442523 641 web optional ctxextensions_3.1.2003112501-1.dsc 692b76b81b097506926241e87b172c47 223435 web optional ctxextensions_3.1.2003112501.orig.tar.gz a56a1b66b42c8f79748a2ccd12f00c6c 8186 web optional ctxextensions_3.1.2003112501-1.diff.gz 1940a5fb89a9c327c36f800cb9f9e76b 308204 web optional mozilla-ctxextensions_3.1.2003112501-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2g26rSla4ddfhTMRAl32AKDulLIf1gybIiNK7glWuxkm+C6GYACfcw+j DOiiKhQduwCeGMi4xVKkr5g= =tKij -END PGP SIGNATURE- Accepted: ctxextensions_3.1.2003112501-1.diff.gz to pool/main/c/ctxextensions/ctxextensions_3.1.2003112501-1.diff.gz ctxextensions_3.1.2003112501-1.dsc to pool/main/c/ctxextensions/ctxextensions_3.1.2003112501-1.dsc ctxextensions_3.1.2003112501.orig.tar.gz to pool/main/c/ctxextensions/ctxextensions_3.1.2003112501.orig.tar.gz mozilla-ctxextensions_3.1.2003112501-1_all.deb to pool/main/c/ctxextensions/mozilla-ctxextensions_3.1.2003112501-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tabextensions 1.10.2003120902-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 14:10:15 +0900 Source: tabextensions Binary: mozilla-tabextensions Architecture: source all Version: 1.10.2003120902-1 Distribution: unstable Urgency: low Maintainer: Mike Hommey [EMAIL PROTECTED] Changed-By: Mike Hommey [EMAIL PROTECTED] Description: mozilla-tabextensions - Tabbed browsing extensions for Mozilla Changes: tabextensions (1.10.2003120902-1) unstable; urgency=low . * New upstream release Files: b4b55970481935a18b1872632ea21bbc 645 web optional tabextensions_1.10.2003120902-1.dsc 57297de25eda855ce936b4435ed3517f 251068 web optional tabextensions_1.10.2003120902.orig.tar.gz 777b859d839fdb442bd20c57d936d4b2 15586 web optional tabextensions_1.10.2003120902-1.diff.gz 6c4129a94b82b15a22d0fdf897921f7f 293634 web optional mozilla-tabextensions_1.10.2003120902-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2g58rSla4ddfhTMRAtF7AKDLt0+hsSQp44rnqRUZgxBxvqGEKgCfXUVz BNgjamrrLSy7i/ENqpwgHTk= =SmSt -END PGP SIGNATURE- Accepted: mozilla-tabextensions_1.10.2003120902-1_all.deb to pool/main/t/tabextensions/mozilla-tabextensions_1.10.2003120902-1_all.deb tabextensions_1.10.2003120902-1.diff.gz to pool/main/t/tabextensions/tabextensions_1.10.2003120902-1.diff.gz tabextensions_1.10.2003120902-1.dsc to pool/main/t/tabextensions/tabextensions_1.10.2003120902-1.dsc tabextensions_1.10.2003120902.orig.tar.gz to pool/main/t/tabextensions/tabextensions_1.10.2003120902.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted tcsh 6.12.00-10 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 19:22:35 +0100 Source: tcsh Binary: tcsh-kanji tcsh Architecture: source i386 Version: 6.12.00-10 Distribution: unstable Urgency: low Maintainer: Martin A. Godisch [EMAIL PROTECTED] Changed-By: Martin A. Godisch [EMAIL PROTECTED] Description: tcsh - TENEX C Shell, an enhanced version of Berkeley csh tcsh-kanji - TENEX C Shell, an enhanced version of Berkeley csh Closes: 223800 Changes: tcsh (6.12.00-10) unstable; urgency=low . * Updated completions, closes: #223800. Files: dc4aa92b0bc607a28d0dab605faa1d69 632 shells standard tcsh_6.12.00-10.dsc d6b8f8451cec2da26c6ce313a6612b20 28171 shells standard tcsh_6.12.00-10.diff.gz 99c5ecec90f72671b239a3cda9496fb4 457450 shells standard tcsh_6.12.00-10_i386.deb 25d342ea01aa1ccf7a2b3a78934465db 462980 shells extra tcsh-kanji_6.12.00-10_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2gkimpGCHWjc1gYRAsidAJ9y36xOeMZ2FAVXR5vf67P3Ue/v9ACgxtxV +v0XdE/rhrZb9S0/Z9rgSqg= =Fn6m -END PGP SIGNATURE- Accepted: tcsh-kanji_6.12.00-10_i386.deb to pool/main/t/tcsh/tcsh-kanji_6.12.00-10_i386.deb tcsh_6.12.00-10.diff.gz to pool/main/t/tcsh/tcsh_6.12.00-10.diff.gz tcsh_6.12.00-10.dsc to pool/main/t/tcsh/tcsh_6.12.00-10.dsc tcsh_6.12.00-10_i386.deb to pool/main/t/tcsh/tcsh_6.12.00-10_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted showimg 0.8.1-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 18:16:22 +0100 Source: showimg Binary: showimg Architecture: source i386 Version: 0.8.1-1 Distribution: unstable Urgency: low Maintainer: Jean-Michel Kelbert [EMAIL PROTECTED] Changed-By: Jean-Michel Kelbert [EMAIL PROTECTED] Description: showimg- A feature-rich image viewer Changes: showimg (0.8.1-1) unstable; urgency=low . * New upstream release * Remove --enable-final from configure to fix a compilation problem. Files: 890f798e983d96c68fc6551ad5c85b17 630 graphics optional showimg_0.8.1-1.dsc ffbe725b0104b5b063398c652c82ce86 1577047 graphics optional showimg_0.8.1.orig.tar.gz e99121541dc2c86113fc6d27d401ca0c 24928 graphics optional showimg_0.8.1-1.diff.gz 9696845e8f28953f77bfc1db9fcfb48e 1061880 graphics optional showimg_0.8.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2fm6ZA5kLi8vDN4RAgnsAJ9A46mWRowL/+P4nKBVz9V3vaqDcQCfdkwS 0bs7rZq0YNlVhMPpI10H3BU= =Qr+P -END PGP SIGNATURE- Accepted: showimg_0.8.1-1.diff.gz to pool/main/s/showimg/showimg_0.8.1-1.diff.gz showimg_0.8.1-1.dsc to pool/main/s/showimg/showimg_0.8.1-1.dsc showimg_0.8.1-1_i386.deb to pool/main/s/showimg/showimg_0.8.1-1_i386.deb showimg_0.8.1.orig.tar.gz to pool/main/s/showimg/showimg_0.8.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libxml2 2.6.3-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 14:45:24 +0900 Source: libxml2 Binary: libxml2-python2.3 libxml2-utils libxml2-dev libxml2 Architecture: source i386 Version: 2.6.3-1 Distribution: unstable Urgency: low Maintainer: Mike Hommey [EMAIL PROTECTED] Changed-By: Mike Hommey [EMAIL PROTECTED] Description: libxml2- GNOME XML library libxml2-dev - Development files for the GNOME XML library libxml2-python2.3 - Python 2.3 bindings for libxml2 libxml2-utils - XML utilities Changes: libxml2 (2.6.3-1) unstable; urgency=low . * New upstream release * debian/rules: - Use dh_makeshlibs -V 'libxml2 (= 2.6.3)', since versions 2.6.3 introduced some new functions. - Put more examples in /usr/share/doc/libxml2-dev/examples. Files: 57ae02917626f277babcbfa40dbc0e41 646 libs optional libxml2_2.6.3-1.dsc f7b83b8d65e8d4e41b0e5e6431a85f49 6377236 libs optional libxml2_2.6.3.orig.tar.gz ecdaad19d3a74e4dd1ab8e717a7ac943 11264 libs optional libxml2_2.6.3-1.diff.gz 321478824233cbcf6d35901abd5934ce 618114 libs optional libxml2_2.6.3-1_i386.deb 1c262aefcdfc4a95fe470c215710334e 234608 text optional libxml2-utils_2.6.3-1_i386.deb d0714efa0665a9b3a3710862da26435b 1501736 libdevel optional libxml2-dev_2.6.3-1_i386.deb 6cdfed64f5a5677e41ef9240f3c5ac5b 425460 python optional libxml2-python2.3_2.6.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2hvg0RXQZ6pf16wRAm6QAKDi0vnaxbfAacF/R0fMJHLlbKvhvQCfcqHt TBLMRLcHfi5LZvogFUYJUq4= =AcWV -END PGP SIGNATURE- Accepted: libxml2-dev_2.6.3-1_i386.deb to pool/main/libx/libxml2/libxml2-dev_2.6.3-1_i386.deb libxml2-python2.3_2.6.3-1_i386.deb to pool/main/libx/libxml2/libxml2-python2.3_2.6.3-1_i386.deb libxml2-utils_2.6.3-1_i386.deb to pool/main/libx/libxml2/libxml2-utils_2.6.3-1_i386.deb libxml2_2.6.3-1.diff.gz to pool/main/libx/libxml2/libxml2_2.6.3-1.diff.gz libxml2_2.6.3-1.dsc to pool/main/libx/libxml2/libxml2_2.6.3-1.dsc libxml2_2.6.3-1_i386.deb to pool/main/libx/libxml2/libxml2_2.6.3-1_i386.deb libxml2_2.6.3.orig.tar.gz to pool/main/libx/libxml2/libxml2_2.6.3.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lvmcfg 0.10 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 10 Dec 2003 21:59:11 + Source: lvmcfg Binary: lvmcfg Architecture: source all Version: 0.10 Distribution: unstable Urgency: low Maintainer: Debian Install System Team [EMAIL PROTECTED] Changed-By: Alastair McKinstry [EMAIL PROTECTED] Description: lvmcfg - Configure the Logical Volume Manager (udeb) Closes: 219471 Changes: lvmcfg (0.10) unstable; urgency=low . * Verok Istvan - Initial Hungarian translation * Template polishing from Christian Perrier plus fixes by Chris Tillman. Closes: #219471 Files: 91ec25edcd2670856bf70abd13c2f4a9 587 debian-installer optional lvmcfg_0.10.dsc 37e0b0693ba1574ba8b48d4096c22b40 38943 debian-installer optional lvmcfg_0.10.tar.gz e51222ed0682eed53c03872af79fe5bd 5626 debian-installer optional lvmcfg_0.10_all.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2hQZ2tp5zXiKP0wRAnEWAJwMfgiGYnE/TTg9mSG1KOumQCOoSACeKKGG wGEkHEccWKFmMh1twqhcDbU= =kqHo -END PGP SIGNATURE- Accepted: lvmcfg_0.10.dsc to pool/main/l/lvmcfg/lvmcfg_0.10.dsc lvmcfg_0.10.tar.gz to pool/main/l/lvmcfg/lvmcfg_0.10.tar.gz lvmcfg_0.10_all.udeb to pool/main/l/lvmcfg/lvmcfg_0.10_all.udeb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted vserver 0.29-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 20:59:40 +0100 Source: vserver Binary: vserver Architecture: source i386 Version: 0.29-1 Distribution: unstable Urgency: low Maintainer: Ola Lundqvist [EMAIL PROTECTED] Changed-By: Ola Lundqvist [EMAIL PROTECTED] Description: vserver- Virtual private servers and context switching Changes: vserver (0.29-1) unstable; urgency=low . * New upstream version. Files: 8267dc529dc9d94eb2e52c5059af33a5 608 base optional vserver_0.29-1.dsc a6107cf98f829c7bd208ab6334fde033 101758 base optional vserver_0.29.orig.tar.gz 58d83c66c74e4289c44650c0db9985a0 41968 base optional vserver_0.29-1.diff.gz f95ba08723cf474f48c18b6363696f65 380318 base optional vserver_0.29-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2iZMGKGxzw/lPdkRAgejAJ9Kp7feXK6iZRGTdhzHk79PADtYJwCfRWEH 9utLjIo0kVvrrBpa49NPf6M= =XK3H -END PGP SIGNATURE- Accepted: vserver_0.29-1.diff.gz to pool/main/v/vserver/vserver_0.29-1.diff.gz vserver_0.29-1.dsc to pool/main/v/vserver/vserver_0.29-1.dsc vserver_0.29-1_i386.deb to pool/main/v/vserver/vserver_0.29-1_i386.deb vserver_0.29.orig.tar.gz to pool/main/v/vserver/vserver_0.29.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rhythmbox 0.6.1-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 20:50:18 +0100 Source: rhythmbox Binary: rhythmbox Architecture: source i386 Version: 0.6.1-2 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers [EMAIL PROTECTED] Changed-By: Josselin Mouette [EMAIL PROTECTED] Description: rhythmbox - music player and organizer for GNOME Closes: 223538 223802 Changes: rhythmbox (0.6.1-2) unstable; urgency=low . * 00docs-fix.patch: patch from Jordi Mallach to make the XML correct (closes: #223538, #223802). * 01docs-fix-autogen.patch: patch Makefile.in as well. * rules: + use simple-patchsys.mk to apply the patches. + clean help/C/authors.xml to force its rebuild. Files: 06ae149cd4967ef97dd2bcd92f5af13e 1582 gnome optional rhythmbox_0.6.1-2.dsc 9563e056c41ea25757e012664b8f977f 6679 gnome optional rhythmbox_0.6.1-2.diff.gz a5502a2e63f72d6925f44e6961a3483d 1115484 gnome optional rhythmbox_0.6.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2iH/rSla4ddfhTMRAjWUAKCZjRscMGIy/j75EPG2j8BPSObtNgCcCQMW HVuN07yHp+MRG0LHHX2KPlM= =om1n -END PGP SIGNATURE- Accepted: rhythmbox_0.6.1-2.diff.gz to pool/main/r/rhythmbox/rhythmbox_0.6.1-2.diff.gz rhythmbox_0.6.1-2.dsc to pool/main/r/rhythmbox/rhythmbox_0.6.1-2.dsc rhythmbox_0.6.1-2_i386.deb to pool/main/r/rhythmbox/rhythmbox_0.6.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted epic4-script-hienoa 0.52-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 22:37:32 +0200 Source: epic4-script-hienoa Binary: epic4-script-hienoa Architecture: source all Version: 0.52-1 Distribution: unstable Urgency: low Maintainer: Upi Tamminen [EMAIL PROTECTED] Changed-By: Jaakko Niemi [EMAIL PROTECTED] Description: epic4-script-hienoa - A script for ircII-EPIC4 Closes: 126836 161789 180693 Changes: epic4-script-hienoa (0.52-1) unstable; urgency=low . * Sponsored upload * New release! * New standards version * Implemented a topic edit command (tedit) (Closes: #126836) * Fixed call to undefined alias h.log_quit (Closes: #180693) * For full list of changes, see changelog.gz (Closes: #161789) Files: c2d4275afd38e2da74485fa43069d923 617 net optional epic4-script-hienoa_0.52-1.dsc 8020f089cfea7bed336ec23f21868515 66933 net optional epic4-script-hienoa_0.52.orig.tar.gz 8d6aa5b70c87af1f321fc978c88cc7cd 2731 net optional epic4-script-hienoa_0.52-1.diff.gz d51ee8b4ee5e019ec94c971529b21e8b 81034 net optional epic4-script-hienoa_0.52-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2icfJMXP5PVSFUERAvpDAJ9lOwPYGjzy4iwPvln73fKHAEYp3gCgmJdk Ri4tQHK4bEn1u96l2n+WZ2E= =5v/1 -END PGP SIGNATURE- Accepted: epic4-script-hienoa_0.52-1.diff.gz to pool/main/e/epic4-script-hienoa/epic4-script-hienoa_0.52-1.diff.gz epic4-script-hienoa_0.52-1.dsc to pool/main/e/epic4-script-hienoa/epic4-script-hienoa_0.52-1.dsc epic4-script-hienoa_0.52-1_all.deb to pool/main/e/epic4-script-hienoa/epic4-script-hienoa_0.52-1_all.deb epic4-script-hienoa_0.52.orig.tar.gz to pool/main/e/epic4-script-hienoa/epic4-script-hienoa_0.52.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wflogs 0.9.6-2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 21:20:39 +0100 Source: wflogs Binary: wflogs Architecture: source i386 Version: 0.9.6-2 Distribution: unstable Urgency: low Maintainer: Jean-Michel Kelbert [EMAIL PROTECTED] Changed-By: Jean-Michel Kelbert [EMAIL PROTECTED] Description: wflogs - The modular firewall log analyzer of the WallFire project Closes: 221123 Changes: wflogs (0.9.6-2) unstable; urgency=low . * Add the possibility to override the default REPORT_DIRECTORY according to the Apache configuration. (Adapt a patch provided by Nicolas Rueff : Thanks to him.) (closes: #221123) * Solve a bug in months handling in wflogs_report. Files: 0864e4fb913f9c77c606f0ae03c92392 642 net optional wflogs_0.9.6-2.dsc 252856e0fc206769f733dc2c265b405d 23024 net optional wflogs_0.9.6-2.diff.gz 5e83a3c7262c6121cbc18efc136dbcfe 173928 net optional wflogs_0.9.6-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2iYUZA5kLi8vDN4RAp0kAJ4uOZ0GQ3eal1XKypE65pAg9A12lQCfU565 3QxBMXcQFZAHq9s1b8BHBiA= =yugU -END PGP SIGNATURE- Accepted: wflogs_0.9.6-2.diff.gz to pool/main/w/wflogs/wflogs_0.9.6-2.diff.gz wflogs_0.9.6-2.dsc to pool/main/w/wflogs/wflogs_0.9.6-2.dsc wflogs_0.9.6-2_i386.deb to pool/main/w/wflogs/wflogs_0.9.6-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lrrd 0.9.9r5-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 28 Nov 2003 23:30:27 +0100 Source: lrrd Binary: lrrd-server lrrd-client Architecture: source all Version: 0.9.9r5-1 Distribution: unstable Urgency: low Maintainer: Tore Anderson [EMAIL PROTECTED] Changed-By: Tore Anderson [EMAIL PROTECTED] Description: lrrd-client - Linpro's network-wide graphing framework (client) lrrd-server - Linpro's network-wide graphing framework (server) Closes: 202190 214114 214186 214210 214277 215739 216176 216401 221691 222674 222821 222838 222841 Changes: lrrd (0.9.9r5-1) unstable; urgency=low . * New upstream release: - Allows for customizing which port to connect to when the server is talking to its clients, closes: #214114. - Makes it possible to change the plugins' environment arbitrarily, sort-of closes: #214277. - Relaxes the paranoia regarding the plugins' ownership and permission modes somewhat, closes: #214186, #216401. - Further impovements to the error-handling logic in lrrd-server, which hopefully closes: #215739, #222674, #222821. - Removed the spurious use of Config::General in lrrd-client, closes: #216176. - Includes Andras Korn's psu_ wildcard plugin, which counts the number of processes owned by specific users, closes: #214210. Thanks, Andras! - The number of context switches per second is now graphed by the interrupts plugin, closes: #222838. Thanks, Mike Fedyk! - Corrected field names in the vmstat plugin, closes: #222841. Thanks again, Mike Fedyk! . * debian/control: - Drop dependency on libconfig-general-perl for lrrd-server, as this configuration file format is now deprecated. - Change priority to extra, due to the dependency on librrds-perl. . * debian/rules: - Polished slightly. . * debian/lrrd-client.dirs: - Removed unecessary entry /var/run/lrrd, which is installed from the Makefile. . * debian/lrrd-client.init: - Rewritten, now sports improved error handling and intrinsic distrust of start-stop-daemon's return values, closes: #202190. . * debian/lrrd-server.cron.d: - Check if the binaries we're about to run exist and are executable before running them, closes: #221691. . * debian/lrrd-client.postinst, debian/lrrd-server.postinst: - If we're updating from the packages which didn't create the lrrd system group, try to make the GID the same as the already existing lrrd users' UID, if it's available. . * debian/lrrd-client.postinst: - Rewritten as a shell script. - Initial plugin setup now relies on lrrd-client-configure instead of an internal function to to initialize plugins. This also ensures that automatic plugins later added to the package will be enabled on upgrades. - The plugins' state files was inappropriately placed in /var/run, move them to /var/lib if any exist in the former location. . * debian/lrrd-server.postinst: - Actually check how we're called, don't blindly assume we're configuring. . * debian/lrrd-server.postrm, debian/lrrd-client.postrm: - Better handling of empty dirs after purge. (This is workaround for dpkg bug #198522). . * debian/lrrd-server.postrm: - Remove some ucf stuff I had forgotten about. . * debian/plugins.conf: - Updated to the new syntax for passing options to the plugins. . * debian/Makefile.config: - Now only contains overrides to the upstream defaults, instead of being a full replacement for upstream's Makefile.config. - PLUGSTATE changed from /var/run/lrrd to /var/lib/lrrd/plugin-state, as these files should persist after reboots. Files: b28a2f08c8c604a4057eccde406d6563 607 net extra lrrd_0.9.9r5-1.dsc e2d3fcc084507113caeab48ad2e592e2 108609 net extra lrrd_0.9.9r5.orig.tar.gz 48d664beae5dbb6a5d1bc4ad00bcd8ed 8644 net extra lrrd_0.9.9r5-1.diff.gz 5cd56f527b0acac58e97a595bcef948a 91146 net extra lrrd-client_0.9.9r5-1_all.deb cd82c9f5964d8dfcdf1e378da924bd3d 87940 net extra lrrd-server_0.9.9r5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2jLw/8x4SxA9OY8RAqghAJ0enuonHOWFrjBWnD1lK39FMGtmdwCcD/yr 9G5LJFEHtP0lLcm2IZ1TEx4= =CHoI -END PGP SIGNATURE- Accepted: lrrd-client_0.9.9r5-1_all.deb to pool/main/l/lrrd/lrrd-client_0.9.9r5-1_all.deb lrrd-server_0.9.9r5-1_all.deb to pool/main/l/lrrd/lrrd-server_0.9.9r5-1_all.deb lrrd_0.9.9r5-1.diff.gz to pool/main/l/lrrd/lrrd_0.9.9r5-1.diff.gz lrrd_0.9.9r5-1.dsc to pool/main/l/lrrd/lrrd_0.9.9r5-1.dsc lrrd_0.9.9r5.orig.tar.gz to pool/main/l/lrrd/lrrd_0.9.9r5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wesnoth 0.6-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 12 Dec 2003 14:24:51 +0100 Source: wesnoth Binary: wesnoth-data wesnoth wesnoth-server Architecture: source i386 all Version: 0.6-1 Distribution: unstable Urgency: low Maintainer: Cyril Bouthors [EMAIL PROTECTED] Changed-By: Cyril Bouthors [EMAIL PROTECTED] Description: wesnoth- Battle for Wesnoth is a fantasy turn-based strategy game wesnoth-data - Data files for Wesnoth wesnoth-server - Wesnoth multiplayer network server Changes: wesnoth (0.6-1) unstable; urgency=low . * New upstream release * Run wesnothd as nobody Files: ad6aa9220272e10e9e25825a09841268 686 games extra wesnoth_0.6-1.dsc 4998f90d4625305a136da4e6901218f8 11590575 games extra wesnoth_0.6.orig.tar.gz af6b515d516d4c47c10cd4d069f344ef 24028 games extra wesnoth_0.6-1.diff.gz 4e3894e66434f0a38ef3bcfca801c609 701446 games extra wesnoth_0.6-1_i386.deb e7b2c1cd11bc9e27acf769d85b45528b 11324306 games extra wesnoth-data_0.6-1_all.deb a6cf0fe744b4532ea8e643e6925c1aab 81582 games extra wesnoth-server_0.6-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2jwDZ1SJHeqsYt8RAkcfAJ91g1LcLjjfBhcsdmAlt8fhTSFaQgCeLOxJ 5U1ipi5VAbz0ws/YFIWZ7H8= =MjG8 -END PGP SIGNATURE- Accepted: wesnoth-data_0.6-1_all.deb to pool/main/w/wesnoth/wesnoth-data_0.6-1_all.deb wesnoth-server_0.6-1_i386.deb to pool/main/w/wesnoth/wesnoth-server_0.6-1_i386.deb wesnoth_0.6-1.diff.gz to pool/main/w/wesnoth/wesnoth_0.6-1.diff.gz wesnoth_0.6-1.dsc to pool/main/w/wesnoth/wesnoth_0.6-1.dsc wesnoth_0.6-1_i386.deb to pool/main/w/wesnoth/wesnoth_0.6-1_i386.deb wesnoth_0.6.orig.tar.gz to pool/main/w/wesnoth/wesnoth_0.6.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted wesnoth 0.6-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 13 Dec 2003 00:02:10 +0100 Source: wesnoth Binary: wesnoth-data wesnoth wesnoth-server Architecture: source i386 all Version: 0.6-2 Distribution: unstable Urgency: low Maintainer: Cyril Bouthors [EMAIL PROTECTED] Changed-By: Cyril Bouthors [EMAIL PROTECTED] Description: wesnoth- Battle for Wesnoth is a fantasy turn-based strategy game wesnoth-data - Data files for Wesnoth wesnoth-server - Wesnoth multiplayer network server Changes: wesnoth (0.6-2) unstable; urgency=low . * The red wine release. Files: 7fbf52273707f103de4e7e06f9369222 686 games extra wesnoth_0.6-2.dsc cb1f6d2004b8cd60e8c8902dc4326244 24056 games extra wesnoth_0.6-2.diff.gz 0b1477f22d1bcade84e7576f65f9434c 634100 games extra wesnoth_0.6-2_i386.deb 59f9bdc2adee578d8a543efdd00b1e35 11324256 games extra wesnoth-data_0.6-2_all.deb f6156854108c89d6ead646beba83fea3 81602 games extra wesnoth-server_0.6-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/2ku8Z1SJHeqsYt8RAuLiAJoDGjkZ97fyu+IVvZi9t7gYhhm5LgCgjE9C ctu61J2xm31G9ldK1c2bwK8= =9X1C -END PGP SIGNATURE- Accepted: wesnoth-data_0.6-2_all.deb to pool/main/w/wesnoth/wesnoth-data_0.6-2_all.deb wesnoth-server_0.6-2_i386.deb to pool/main/w/wesnoth/wesnoth-server_0.6-2_i386.deb wesnoth_0.6-2.diff.gz to pool/main/w/wesnoth/wesnoth_0.6-2.diff.gz wesnoth_0.6-2.dsc to pool/main/w/wesnoth/wesnoth_0.6-2.dsc wesnoth_0.6-2_i386.deb to pool/main/w/wesnoth/wesnoth_0.6-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
