Uploaded kdebindings 2.2.1-1 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 25 Aug 2001 14:34:00 -0700 Source: kdebindings Binary: dcopperl libkdexparts-dev libkdexparts1 libdcopc1 libdcopc-dev dcoppython Architecture: m68k Version: 2.2.1-1 Distribution: unstable Urgency: low Maintainer: Debian/m68k Build Daemon [EMAIL PROTECTED] Changed-By: Ivan E. Moore II [EMAIL PROTECTED] Description: dcopperl - Perl bindings for DCOP dcoppython - Python bindings for DCOP libdcopc-dev - C bindings for DCOP (Development files) libdcopc1 - C bindings for DCOP libkdexparts-dev - Python bindings for DCOP libkdexparts1 - Python bindings for DCOP Closes: 111028 Changes: kdebindings (2.2.1-1) unstable; urgency=low . * New upstream version * Lintian cleanup * Fix includes problem for building with gcc3 (Closes: #111028) Files: fd44dbd79afa8d7a5604936230981028 42986 libs optional dcoppython_2.2.1-1_m68k.deb 4eb4b5c7990d8baa8fddc2e15009d54e 52684 libs optional dcopperl_2.2.1-1_m68k.deb f5030bee9837a8b4e96cfc7665a64f72 17600 libs optional libdcopc1_2.2.1-1_m68k.deb 0b6595af127bbd55bc17d3bd077a950e 4818 devel optional libdcopc-dev_2.2.1-1_m68k.deb 9518eb92fd68f27c5b59734dbb22973d 58098 libs optional libkdexparts1_2.2.1-1_m68k.deb 38135a3968c58fdbc0cfb2fbd83343fe 4648 devel optional libkdexparts-dev_2.2.1-1_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard http://www.gnupg.org/ iEYEARECAAYFAjuxn4QACgkQcS3JWD3FdvdisQCfdHEzs1sHTiOc88/D/FNZgnT2 gukAni+R6RY/I5F2v9JnYr9kObFjc0bl =GvPk -END PGP SIGNATURE-
Uploaded gtkhtml 0.12.0-2 (m68k all) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Sep 2001 18:30:46 +0200 Source: gtkhtml Binary: libgtkhtml-dev gtkhtml libgtkhtml-data libgtkhtml15 Architecture: m68k all Version: 0.12.0-2 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Christian Marillat [EMAIL PROTECTED] Description: gtkhtml- HTML rendering/editing library - bonobo component binary. libgtkhtml-data - HTML rendering/editing library - data files. libgtkhtml-dev - HTML rendering/editing library - development files. libgtkhtml15 - HTML rendering/editing library - runtime files. Closes: 112103 Changes: gtkhtml (0.12.0-2) unstable; urgency=low . * debian/rules Fix bashism (Closes: #112103) * debian/control Replace cygnus-stylesheets by docbook-utils Files: eb66d9e7921fdf72268a1324e1a90d02 210470 libs optional libgtkhtml15_0.12.0-2_m68k.deb dbdc95485b5cbe78f76db022892cafec 264818 devel optional libgtkhtml-dev_0.12.0-2_m68k.deb c9a26dcd81a32800cf52f9fc80adf213 147922 misc optional gtkhtml_0.12.0-2_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7sSFCWgZ1HEtaPf0RAmgFAJ90nKu87cTwJU2tJjCwYBqCrZ23/ACdGeJJ UVxnbtkuWky78j/qhsFMoAc= =AkPY -END PGP SIGNATURE-
Uploaded libcurl-easy-perl 1.1.7-1 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 20 Sep 2001 01:52:13 +0200 Source: libcurl-easy-perl Binary: libcurl-easy-perl Architecture: m68k Version: 1.1.7-1 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Domenico Andreoli [EMAIL PROTECTED] Description: libcurl-easy-perl - perl interface to libcurl Closes: 94367 Changes: libcurl-easy-perl (1.1.7-1) unstable; urgency=low . * Initial release (Closes: #94367). Files: 3636194efad1fb1f53a78e3a21568332 23998 interpreters optional libcurl-easy-perl_1.1.7-1_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7sbhmWgZ1HEtaPf0RAo8DAJ4+5MJdI6LJ4YQK3Kn+hIcGME4wxQCdHK8J 77QbhxEaWXtxnPbhwj2uO1c= =V5uS -END PGP SIGNATURE-
Uploaded modemp3d 0.1-2 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Sep 2001 10:38:07 -0600 Source: modemp3d Binary: modemp3d Architecture: m68k Version: 0.1-2 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Bdale Garbee [EMAIL PROTECTED] Description: modemp3d - AO-40 (Phase3D) Soundcard Telemetry Decoder Closes: 113355 Changes: modemp3d (0.1-2) unstable; urgency=low . * change build depends to use libgtk1.2-dev instead of libgtk-dev. Sigh. * force mandir during install phase in rules file, closes: #113355 Files: 2199921c02f5b85ed9eefd4e31dc2e11 73686 hamradio extra modemp3d_0.1-2_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7saq4WgZ1HEtaPf0RAlRRAKCYsSlXKJDHESA+B9J8yRYRvqBSSACfRDsd s/KjGTPVVMEHHREWnzjYgpQ= =tpfF -END PGP SIGNATURE-
Uploaded kcd 0.1.3-5 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 23 Sep 2001 23:07:01 -0500 Source: kcd Binary: kcd Architecture: m68k Version: 0.1.3-5 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Ben Burton [EMAIL PROTECTED] Description: kcd- a CD player applet for KDE Kicker Changes: kcd (0.1.3-5) unstable; urgency=low . * Updated parameters for alpha build. Files: a27b0b2d10c378f734bd00e55f63bf4b 26388 sound optional kcd_0.1.3-5_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7saQAWgZ1HEtaPf0RAq98AJsFTTtqs/fPgxs8033f4YJ5ANJleACgnIFx CyVJDgcL775yQnVLaGz2+rI= =HooO -END PGP SIGNATURE-
Uploaded fv 3.0-1 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 20 Sep 2001 13:24:02 +0200 Source: fv Binary: fv Architecture: m68k Version: 3.0-1 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Jens Schmalzing [EMAIL PROTECTED] Description: fv - a tool for viewing and editing FITS format files Closes: 112746 Changes: fv (3.0-1) unstable; urgency=low . * Initial Release (closes: Bug#112746). Files: 93be03e62b00fee038b5340c797c9b22 1339340 science optional fv_3.0-1_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7scpmWgZ1HEtaPf0RAle1AJ9TI9K+rDpzUqQkAG9P2b3GwkhSoQCfb92q IiGSxxAxjCKJoeu2UQGdbVk= =97OI -END PGP SIGNATURE-
Uploaded mmorph 2.3.4-6 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 23 Sep 2001 01:00:52 -0600 Source: mmorph Binary: mmorph Architecture: m68k Version: 2.3.4-6 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: David Kimdon [EMAIL PROTECTED] Description: mmorph - A two-level morphology tool for natural language processing Closes: 105158 Changes: mmorph (2.3.4-6) unstable; urgency=low . * fix build failure on ia64 (closes: #105158) Files: 10458f25a7b22629a18405826dec166e 163128 misc extra mmorph_2.3.4-6_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7saW7WgZ1HEtaPf0RArM4AJ0SIIA++kyBgwuHj9JwzLVhjjSi7QCfS/eO 7J2nC6hYIokF9eN4hpFPKbw= =29vR -END PGP SIGNATURE-
Uploaded raccess4vbox3 0.2.3 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 24 Sep 2001 16:57:18 +0200 Source: raccess4vbox3 Binary: raccess4vbox3 Architecture: m68k Version: 0.2.3 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Gerrit Pape [EMAIL PROTECTED] Description: raccess4vbox3 - DTMF support and utilities for vbox3 Changes: raccess4vbox3 (0.2.3) unstable; urgency=low . * changed maintainer email address to [EMAIL PROTECTED]. Files: fcecccdee7917d4de180af06687b0fe5 750996 utils extra raccess4vbox3_0.2.3_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7saU2WgZ1HEtaPf0RAhhoAJ0QzuwZbBf0+Gri3VN5bLMOrwFSCwCfZgPG 8DzGvga4/f9kX+wkskHMshI= =vOzP -END PGP SIGNATURE-
Uploaded libdvdread 0.9.1-1 (m68k) to erlangen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 23 Sep 2001 15:21:24 -1000 Source: libdvdread Binary: libdvdread1 libdvdread-dev Architecture: m68k Version: 0.9.1-1 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Brian Russo [EMAIL PROTECTED] Description: libdvdread-dev - Simple foundation for reading DVDs. libdvdread1 - Simple foundation for reading DVDs. Closes: 110589 112248 112291 112979 113157 Changes: libdvdread (0.9.1-1) unstable; urgency=low . * New upstream version * Added URI (Closes: #113157, #112291) * Fixed sparc re configure.in (Closes: #110589) * Fix binary-arch target in rules (Closes: #112248, #112979) Files: 09d184028bd03f236dfd4b206a37f769 34560 graphics optional libdvdread1_0.9.1-1_m68k.deb 4b6ee94e3c0fa3c561d63fbc320b3438 49112 devel optional libdvdread-dev_0.9.1-1_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE7siFiWgZ1HEtaPf0RApmPAJ43c0jphpA2dXa4Hp2xSd9sgYtg9wCdFQGo 9J0FV5a7nI74D9md46uziH8= =1PFR -END PGP SIGNATURE-
Re: PROPOSED: slight change to wnpp procedures
On Wed, Sep 26, 2001 at 01:59:14PM +1000, Anthony Towns wrote: On Tue, Sep 25, 2001 at 10:35:32PM -0500, Branden Robinson wrote: You are not going to harass us into special casing you. I wouldn't dream of it, hence the proposal in this thread. Uh, and you figure making people mail the BTS specially for each new package uploaded What proposal were you reading? It sure doesn't sound like the one I wrote: When a package that has been ITP'ed is finally packaged, I'd like to suggest that it be reassigned to ftp.debian.org. If you have a problem with people filing bugs with the BTS to declare their intent to package each new package they intend to upload, I suggest you talk to the WNPP team ASAP. (instead of adding a Closes line to the changelog), The package changelog can and should still use Closes: #ITP bugnumber, so that the bug is closed automatically and filing, what, a dozen new bugs against ftp.debian.org every week is something other than harassment [0]? I'm sorry, I don't understand where you're getting the new bugs from. ITP bugs already exist in the BTS. Why, btw, are you uploading a NEW package with the maintainer set to -qa, especially when -qa has already asked for the package to be removed from the distro? That's usually considered somewhat irresponsible. Did you read the changelog of the uploaded package? It appears in the bug logs of #113360. [0] A few weeks ago, the term would've been bug terrorism, but maybe not now. Thankfully(?), you've kept the meme alive with this message. -- G. Branden Robinson| Communism is just one step on the Debian GNU/Linux | long road from capitalism to [EMAIL PROTECTED] | capitalism. http://people.debian.org/~branden/ | -- Russian saying pgpO0sQGOGmtk.pgp Description: PGP signature
Why I can not go ahead with IMP?
I've install PHP4, horde, IMP. When I access the mailbox by 127.0.0.1/horde, I get the login interface, I can log in, but when I click the subject ,or date, or compose, or any other href, I can not go ahead, I only get the login infterface again. Why?
Re: Why I can not go ahead with IMP?
It's the immediate logout issue, I believe. I've been having the same problem for half a year now, to no avail. There's other people struggling too if you search on Google. blah... ilia. - Original Message - From: Shuangquan Li [EMAIL PROTECTED] To: debian-devel@lists.debian.org Sent: Wednesday, September 26, 2001 12:59 AM Subject: Why I can not go ahead with IMP? I've install PHP4, horde, IMP. When I access the mailbox by 127.0.0.1/horde, I get the login interface, I can log in, but when I click the subject ,or date, or compose, or any other href, I can not go ahead, I only get the login infterface again. Why? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFS Kernel image packaging
At this time being, there's no official XFS kernel images nor patches in Debian, however there is xfsprogs as far as I know in Woody Sid. I am willing to work on an XFS kernel floppy boot disk, but it would be pointless cine a kernel image with XFS is bloated by about 300K if I'm not mistaken, at least the ones on some of the machines I put XFS into. There are Reiserfs images avaiable however. I certainly would like to get a hold of some XFS based install disks if anyone ever has done any with success. David On Tue, Sep 25, 2001 at 01:12:52PM -0600, Russel Ingram wrote: Pardon me if I sound like a newbie here. I am fairly new to the Debian way, but I am a Linux veteran. I have noticed that there are patches available in the debian package tree for the XFS filesystem but there are no available kernel-image packages with XFS already built in. Is there a specific reason for this or is it just because no one has stepped forward to offer such a package? If the latter is true I would be willing to be a maintainer for a kernel-*-xfs package set if no one else is working on it. I haven't been able to find any references specific to making kernel packages in the packaging manual or the policies so I'm also curious about whether or not official debian kernel packages are created with the make-kpkg command or if it has to be done with dpkg-deb tool. I've used the make-kpkg command to create kernel packages, but they always come out with a custom-1.00 label on them and I haven't figured out how to get around that. Thanx, Russ -- Russel H. Ingram Unix Systems Administrator Institute for Scientific Computation University of Wyoming/Math Dept. Phone: (307)766-6546 E-Mail: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFS Kernel image packaging
On Tue, 25 Sep 2001, David wrote: At this time being, there's no official XFS kernel images nor patches in Debian, however there is xfsprogs as far as I know in Woody Sid. I am willing to work on an XFS kernel floppy boot disk, but it would be pointless cine a kernel image with XFS is bloated by about 300K if I'm not mistaken, at least the ones on some of the machines I put XFS into. There are Reiserfs images avaiable however. I certainly would like to get a hold of some XFS based install disks if anyone ever has done any with success. David There is a set of disks for installing on XFS available at http://www.digitaltux.com. The only complaint I have with those disks is that the kernel is not up to date (nor is the version of XFS) and making the filesystems XFS during the install requires that you jump through some extra hoops. I hope to remedy that in the near future as well. Russ -- Russel H. Ingram Unix Systems Administrator Institute for Scientific Computation University of Wyoming/Math Dept. Phone: (307)766-6546 E-Mail: [EMAIL PROTECTED]
Re: Why I can not go ahead with IMP?
I got sick of how nasty IMP was getting and moved to squirrelmail recently. I dont think theres a package out there yet, nor do I know of a tool to move IMP database-driven address books to squirrelmail's format (yet). * Ilia Lobsanov [EMAIL PROTECTED] [010926 00:14]: It's the immediate logout issue, I believe. I've been having the same problem for half a year now, to no avail. There's other people struggling too if you search on Google. blah... ilia. - Original Message - From: Shuangquan Li [EMAIL PROTECTED] To: debian-devel@lists.debian.org Sent: Wednesday, September 26, 2001 12:59 AM Subject: Why I can not go ahead with IMP? I've install PHP4, horde, IMP. When I access the mailbox by 127.0.0.1/horde, I get the login interface, I can log in, but when I click the subject ,or date, or compose, or any other href, I can not go ahead, I only get the login infterface again. Why? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ [EMAIL PROTECTED] History teaches that grave threats to liberty often come in times of urgency, when constitutional rights seem too extravagant to endure. - Justice Thurgood Marshall (1989)
squirrelmail (Re: Why I can not go ahead with IMP?)
On Wed, Sep 26, 2001 at 01:13:26AM -0500, Scott Dier wrote: I got sick of how nasty IMP was getting and moved to squirrelmail recently. I dont think theres a package out there yet, nor do I know of a tool to move IMP database-driven address books to squirrelmail's format (yet). http://bugs.debian.org/86125 The last person working on it was apparently sam johnston [EMAIL PROTECTED], but the original submitter has a mostly-completed package already. It sounds like someone needs to step forward and take the final steps, preferably someone interested in PHP (not me). -- - mdz
MUAs and Locking Was: Re: PROPOSED: slight change to wnpp procedures
* Anthony Towns aj@azure.humbug.org.au [010925 22:59]: Why, btw, are you uploading a NEW package with the maintainer set to -qa, especially when -qa has already asked for the package to be removed from It's absouletly horrid code to look at and has a locking scheme I wish not to overhaul to get into the fnctl, then dotlock policy. Right now it seems to dotlock only, never fnctl. It might not be a bad idea for MUA maintainers to check on how their packages handle the munging of mailboxes. This can be a pretty 'critical' thing because users using NFS mounted mailspools can quickly lose whole spools with bad locking practices. Thanks, -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ [EMAIL PROTECTED] History teaches that grave threats to liberty often come in times of urgency, when constitutional rights seem too extravagant to endure. - Justice Thurgood Marshall (1989)
Re: PROPOSED: slight change to wnpp procedures
* Aaron Lehmann [EMAIL PROTECTED] [010925 22:43]: Thats not really fair now is it! Branden is trying to make the procedure better if his suggestions are wrong how about making constructive criticism. Tell that to James Troup. Perhaps next time let him make the comment instead. -- Scott Dier [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.ringworld.org/ [EMAIL PROTECTED] History teaches that grave threats to liberty often come in times of urgency, when constitutional rights seem too extravagant to endure. - Justice Thurgood Marshall (1989)
Re: PROPOSED: slight change to wnpp procedures
Branden Robinson [EMAIL PROTECTED] immo vero scripsit When a package that has been ITP'ed is finally packaged, I'd like to suggest that it be reassigned to ftp.debian.org. The package changelog can and should still use Closes: #ITP bugnumber, so that the bug is closed automatically, but this way it is clear that the matter is out of the (prospective) package maintainer's hands, or those of the WNPP group, and in that of the FTP maintainers. Rather than making it to be reassigned to something else, it might be better to retitle it to make it look ITP-uploaded: package - description or Uploaded: package - description and still assigned to wnpp. It will make clearer which packages are still in preparation and which are not (which is not obvious in the current state), and not make ftp.debian.org overloaded with bugs. But it's one more step to the procedure, and I guess it will add to the confusion / manual mistakes. thanks, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Re: Disappearing task-* packages!
On Tue, Sep 25, 2001 at 01:04:12PM -0500, Taral wrote: All the task-* packages seem to be missing from the main Packages file! Where did they go? the dumpster. P.S. If this was announced, perhaps the announcement should have gone to the debian-devel-announce list? its been discussed in various places. task- packages are a ugly kludge that have been replaced by a proper implementation: the Task: feild of the control file, the new tasksel uses this now instead of task- packages. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpKbCLNHL3z4.pgp Description: PGP signature
Re: XFS Kernel image packaging
On Tue, Sep 25, 2001 at 10:23:34PM -0700, David wrote: At this time being, there's no official XFS kernel images nor patches in Debian, however there is xfsprogs as far as I know in Woody Sid. I am willing to work on an XFS kernel floppy boot disk, but it would be pointless cine a kernel image with XFS is bloated by about 300K if I'm not mistaken, at least the ones on some of the machines I put XFS into. There are Reiserfs images avaiable however. I certainly would like to get a hold of some XFS based install disks if anyone ever has done any with success. fwiw current cvs boot-floppies (and 3.0.14) support XFS (as well as ext2, ext3, and reiserfs). if you boot with a kernel capable of any of these filesystems and have the corresponding mkfs utility on the root disk the filesystem will be offered as an option. if you were insane enough to get a kernel supporting all of ext2, ext3, xfs, and reiserfs and had all the mkfs utils you would be offered a choice between all 4. -- Ethan Benson http://www.alaska.net/~erbenson/ pgpirMoQI66kv.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
* Christian Kurz | On 01-09-25 Steve Greenland wrote: | | I am so tired of hearing things like this. Nobody is forcing anyone to | do anything. We already force them to use 2.2 instead of still using | 2.0. You want the functionality, you use the right tools. You want to | | Were exactly do we force them? Which debian packages do not work well | with a 2.0.x kernel? modutils, iirc. -- Tollef Fog Heen You Can't Win
Re: bind9-chroot (was: questions on ITP)
* Steve Greenland | I am so tired of hearing things like this. Nobody is forcing anyone to | do anything. We already force them to use 2.2 instead of still using | 2.0. You want the functionality, you use the right tools. You want to | stick with 2.2, then *you* deal with the issues. The maintainers have | suggested a reasonable solution. If you don't like that solution, then | it's *your* problem, not theirs. You forget something -- 2.2 is the default kernel on many architectures. The right way is, imho, the way postfix deals with it. It took quite some time before I discovered it chrooted itself. -- Tollef Fog Heen You Can't Win
Re: Questions regarding the Security Secretary Position
On Mon, Sep 24, 2001 at 09:53:26AM +0200, Martin Schulze wrote: However, the more people are involved, the more coordination has to be done. And considering we're all antisocial disobliging SoBs, this is a fatal flaw ; -- 2. That which causes joy or happiness.
Re: section descriptions
On Sun, Sep 23, 2001 at 11:21:07PM +0200, NORMAND Jacques wrote: where can I find the descriptions of the official debian subsection which can be specified in the Section field of the control file? I need something similar to the /usr/share/tasksel/debian-tasks.desc file which describes the debian tasks. this might be a first step to the answer: http://www.debian.org/doc/debian-policy/ch-archive.html Also, http://packages.debian.org/stable/ might be of some use. -- 2. That which causes joy or happiness.
Re: [Fwd: debian more international]
On Tue, Sep 25, 2001 at 02:01:05AM +, Sulaiman Alhasawi wrote: Also, I recommend you to maintain Arab web pages, documents, and other translations for Debian. Please refer http://www.debian.org/international/ for detail. Sure . Thats what im interested in and thats why im here . Im already translating LDP project with the help of my collegues becuase its so big . Great .. i have read those pages you refered to . I want to know what the first thing i should do . Should i register my self into http://nm.debian.org or what ?? I really appreciate some advice . You should post to debian-www@lists.debian.org saying you'd like to translate Debian web pages to Arabic. After you read http://www.debian.org/devel/website/ to see how it is done, we'll give you access to the translation and you can update it, you don't have to register at nm.d.o for that. -- 2. That which causes joy or happiness.
Re: strange(?) /etc/syslog.conf
On Tue, Sep 25, 2001 at 04:11:10PM +0900, Atsuhito Kohda wrote: mail.*/var/log/mail.log mail.info -/var/log/mail.info mail.warn -/var/log/mail.warn mail.err /var/log/mail.err AFAICT the first one is a catch all log file, while the others are more fine grained. In any event, these are the default values and aren't actually used by Exim -- it has its three log files in /var/log/exim which don't require editing /etc/syslog.conf. You can comment out those lines if you don't have any other mail-related programs on the machine -- but don't do it if you also have a POP3 server such as qpopper. -- 2. That which causes joy or happiness.
Re: PROPOSED: slight change to wnpp procedures
Branden Robinson [EMAIL PROTECTED] writes: The bug was quickly closed by one of the FTP admins: Be happy, you got a reply... -- Marcelo | - There have been...accidents. - What kind of [EMAIL PROTECTED] | accidents? - The kind of accidents you prefer to | call...accidents. | -- (Terry Pratchett, Maskerade)
Re: bind9-chroot (was: questions on ITP)
On 01-09-25 Henrique de Moraes Holschuh wrote: On Tue, 25 Sep 2001, Christian Kurz wrote: On 01-09-24 Henrique de Moraes Holschuh wrote: On Mon, 24 Sep 2001, Christian Kurz wrote: Hm, that doesn't make much sense too me. I think the best thing would be to have /etc/bind inside $CHROOT and having no symlink. And scratch the second-most important feature of Debian (the first one being the DFSG)? Do Not Move Config Files Out Of /etc. Ever. If you need it elsewhere, at least leave a symbolic link in place. But having a link from either the config-files in /etc/bind to $CHROOT or in the other direction, could be in my opinion a security risk. In my Oh, how so? I think you know how the method of how to break out of a chroot. Having some symlink inside the chroot would in my opinion make this task easier then it normally is. But feel free to prove me wrong. and would instead suggestion to modify the documents stating that all config files should be in /etc to make a exception for $CHROOT. wears QA hat NEVER. This is not some low-grade distribution where you can go around scattering configuration files all over the filesystem. I will fight tooth and nail against such an atrocity. /wears QA hat Well, then we have to find some other way like cp, rsync, or something else to keep one copy of the files in /etc and one in $CHROOT/etc. Using mount --bind is like I stated before, no option. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgp65GidExMe7.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
On 01-09-25 Roberto Suarez Soto wrote: On Sep/25/2001, Christian Kurz wrote: Were exactly do we force them? Which debian packages do not work well with a 2.0.x kernel? I think that maybe he refers to the fact that, for example, you may have formatted your ext2 partitions so they are incompatible with 2.0.x Well, I once heared about this, but never read an explanation what exactly causes the differences in the ext2 partitions created while running a 2.0.x kernel and why they have been introduced. kernels. Or to the lot of programs (iptables and related, for example) that only work with 2.4.x. Well, iptables is only available for kernel 2.4.x, but with kernel 2.2.x you can still build a firewall with ipchains or ipfwadm if you still use a 2.0.x kernel. So if you want to build a firewall you are not forced to kernel 2.4.x. The decision which kernel and software to use is still left to the administrator. That's a nice attitude, which will lead to the situation that people, especially administrators, will move away from debian to either other distributions, a bsd flavour or other free operating systems. Have you tried any *BSD? I would prefer any Debian to them if I had to Yes, I worked quite some time with FreeBSD and also took a short look at NetBSD. (I hadn't time to install OpenBSD for testing purposes.) seriously take charge of one :-) (but again, that's only my opinion; and I'm Well, I wouldn't agree with you, but that's an other discussion which doesn't belong on this list. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgpBfNW5Anj13.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
On Wed, 26 Sep 2001, Christian Kurz wrote: and would instead suggestion to modify the documents stating that all config files should be in /etc to make a exception for $CHROOT. wears QA hat NEVER. This is not some low-grade distribution where you can go around scattering configuration files all over the filesystem. I will fight tooth and nail against such an atrocity. /wears QA hat Well, then we have to find some other way like cp, rsync, or something else to keep one copy of the files in /etc and one in $CHROOT/etc. Using mount --bind is like I stated before, no option. I did not follow the discussion closely, so please forgive me when I'm posting already discussed facts here. The postfix MTA also uses a chroot and in its init.d file and all files needed by the chrooted processes are copied to the chroot upon start of postfix. I do the same with my chrooted bind8. Are there any problems I missed with cimply copying the files? Mount -bind is no option, hardlinks aren't either. Symlinks from inside the chroot to /etc are not possible, the other direction is imho even more evil than cp. yours, peter -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred.| : :' :By professionals, | `. `' for professionals http://www.palfrader.org/ | `-http://www.debian.org/
Re: Why I can not go ahead with IMP?
It's the immediate logout issue, I believe. I've been having the same problem for half a year now, to no avail. There's other people struggling too if you search on Google. did you check that the database for horde was properly created ? see if /var/lib/mysql/horde (don't know where to look if you're using postgres) contains various files. if the directory is empty, you have to run something like mysql -uhordemgr -ppassforhorde horde /usr/share/doc/imp/examples/mysql_create.sql We are all so much together and yet we are all dying of loneliness. -- A. Schweitzer
..
Title:
Re: bind9-chroot (was: questions on ITP)
On Sep/26/2001, Christian Kurz wrote: I think that maybe he refers to the fact that, for example, you may have formatted your ext2 partitions so they are incompatible with 2.0.x Well, I once heared about this, but never read an explanation what exactly causes the differences in the ext2 partitions created while running a 2.0.x kernel and why they have been introduced. The features are documented in mke2fs(8), under -O (or it seems, for what I've seen). They don't seem to be too useful (unless I'm missing something), but anyway they are there. Well, iptables is only available for kernel 2.4.x, but with kernel 2.2.x you can still build a firewall with ipchains or ipfwadm if you still use Yes, but it's not the same building a firewall with 2.4.x and building a firewall with 2.2.x or 2.0.x. There are a few things that you can do only with 2.4, not with lower versions. Stateful firewalling, for example. [BSD] seriously take charge of one :-) (but again, that's only my opinion; and I'm Well, I wouldn't agree with you, but that's an other discussion which doesn't belong on this list. Yes. Anyway, I don't think that this was a wrong attitude. As I said, if something is easier upgrading to 2.4.x, I think it's not bad to depend on it. Maybe there should be a easy 2.4.x-dependant bind9-chroot package, and another one, 2.2-2.0 compatible. There are two smbfs packages in a similar state, so why couldn't be two bind9-chroot packages too? -- Roberto Suarez Soto
Re: bind9-chroot (was: questions on ITP)
On Tue, Sep 25, 2001 at 04:34:31PM +0200, Christian Kurz wrote: On 01-09-25 Steve Greenland wrote: I am so tired of hearing things like this. Nobody is forcing anyone to do anything. We already force them to use 2.2 instead of still using 2.0. You want the functionality, you use the right tools. You want to Were exactly do we force them? Which debian packages do not work well with a 2.0.x kernel? apt-cache search usb for example. stick with 2.2, then *you* deal with the issues. The maintainers have That's a nice attitude, which will lead to the situation that people, especially administrators, will move away from debian to either other distributions, a bsd flavour or other free operating systems. Forcing new users to deal with historic burden is not an answer. Use a old kernel - loose features. I really can't understand your problem with limiting chroot bind9 feature to kernels with --bind mounts support. They still can run bind9 perfectly, although less securely. If 2.2 kernel users want chrooted bind, they a) have already done it - no extra work b) upgrade to 2.4 - sheez, that was hard... c) do it manually - no more work than it is now who the hell has to do more work, if we add *support* for *automaticly* running bind9 in chroot jail if the kernel supports --bind mounts? -- Riku Voipio|[EMAIL PROTECTED] | kirkkonummentie 33 |+358 40 8476974 --+-- 02140 Espoo| | Facts do not cease to exist because they are ignored. |
Re: bind9-chroot (was: questions on ITP)
On Wed, 26 Sep 2001, Roberto Suarez Soto wrote: On Sep/26/2001, Christian Kurz wrote: I think that maybe he refers to the fact that, for example, you may have formatted your ext2 partitions so they are incompatible with 2.0.x Well, I once heared about this, but never read an explanation what exactly causes the differences in the ext2 partitions created while running a 2.0.x kernel and why they have been introduced. The features are documented in mke2fs(8), under -O (or it seems, for what I've seen). They don't seem to be too useful (unless I'm missing something), but anyway they are there. IIRC ext2 filesystems created with sparse_super mount a lot faster than filesystems created without that option. Ext2 mounts of 20+ Gig filesystems took ages. yours, peter -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred.| : :' :By professionals, | `. `' for professionals http://www.palfrader.org/ | `-http://www.debian.org/
Re: bind9-chroot (was: questions on ITP)
Riku Voipio [EMAIL PROTECTED] immo vero scripsit who the hell has to do more work, if we add *support* for *automaticly* running bind9 in chroot jail if the kernel supports --bind mounts? By the way, are we talking about running bind as non-root inside a chroot, or are we talking about running bind as root inside a chroot? regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Openssl - progression into testing
There are a lot of packages waiting on openssl to move into testing. The latest excuses says: openssl 0.9.6b-2 (currently 0.9.6a-3) (standard) (non-US) (high) Maintainer: Christoph Martin [EMAIL PROTECTED] openssl uploaded 7 days ago, out of date by 5 days! libssl-dev/alpha: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-2) libssl-dev/arm: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-1) out of date on arm: libssl-dev, libssl0.9.6, openssl (from 0.9.6b-1) there are up to date bins in arm also libssl-dev/hppa: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-1) libssl0.9.6/hppa: Unsatisfiable Depends: libssl0.9.6 ssleay/hppa: Unsatisfiable Depends: openssl out of date on hppa: libssl-dev, libssl0.9.6, openssl (from 0.9.6b-1) there are up to date bins in hppa also libssl-dev/i386: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-2) libssl-dev/ia64: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-1) libssl0.9.6/ia64: Unsatisfiable Depends: libssl0.9.6 ssleay/ia64: Unsatisfiable Depends: openssl out of date on ia64: libssl-dev, libssl0.9.6, openssl (from 0.9.6b-1) there are up to date bins in ia64 also libssl-dev/m68k: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-2) libssl-dev/powerpc: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-2) libssl-dev/sparc: Unsatisfiable Depends: libssl0.9.6 (= 0.9.6b-2) not considered All these dependencies seem to be internal, so what is preventing its being installed into testing? And what does this mean? out of date on ia64: libssl-dev, libssl0.9.6, openssl (from 0.9.6b-1) there are up to date bins in ia64 also -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://www.lfix.co.uk/oliver PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47 6B 7E 39 CC 56 E4 C1 47 GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C For I am convinced that neither death, nor life, nor angels, nor principalities, nor things present, nor things to come, nor powers, nor height, nor depth, nor any other created thing, shall be able to separate us from the love of God, which is in Christ Jesus our Lord. Romans 8:38,39
wajig: Simplified command line admin for Debian
Wajig is a simplified command line interface to many of the typical Debian administration tasks, including package management and configuration, and daemon control. It is essentially a collection of tricks of the Debian trade packaged up into one python program. Underneath it uses apt-get, dpkg, apt-cache, wget, and much more. On the surface it is based around a collection of commands that hopefully make some sense. Wajig can be installed by adding the following to /etc/apt/sources.list (not yet an official Debian package): deb http://edm.act.cmis.csiro.au/debian ./ and then apt-get update and apt-get install wajig. Wajig is designed to run as a normal user, using sudo as required, but can also run as root without any extra setup. Using sudo requires a little setting up as described with the doc command wajig doc. Try wajig help for a list of common commands and wajig -v help for a complete list of available commands. Examples include: wajig update (= apt-get update) wajig install less (= apt-get install less) wajig new (list new packages since last update) wajig newupgrades (list packages upgraded since last update) wajig updatealts editor(update the default editor) wajig restart apache (restart the apache daemon) wajig listfiles less (list the files supplied by the less pkg) wajig whichpkg stdio.h (what package supplies this header file) wajig whatis rats (one line description of the pakacge rats) wajig orphans (list libraries not required by other pkgs) and many more (see below for current complete list). Wajig has evolved over many years and there's a small band of users. It has some of the same aims as the feta package and I thought to wrap the extra wajig features into feta, but a number of users suggested that wajig should stay. So it was rewritten recently from being a shell script to a python program. It is available under the GPL. $ wajig -v help All wajig commands: autoclean Remove all superseded downloaded deb files bugCheck for reported bugs in package using the Debian Bug Tacker build Retrieve/unpack sources and build .deb for the named packages dist-upgrade Upgrade to a new distribution (installed and new rqd packages) clean Remove all downloaded deb files describe Provide a description of package (-v and -vv for more detail) docEquivalent to help with -verbose=2 editsourcesEdit the sources.list file which locates Debian archives findfile Search for a file within installed pacakges force Install package even if it overwrites files from other pkgs help Print documentation (detail depends on --verbose) hold Place listed packages on hold so they are not upgraded init Initialise or reset the wajig archive files installInstall (or upgrade) one or more packages or a .deb file integrity Check the integrity of installed packages (through checksums) lastupdate Identify when an update was last performed list List the status of every known package listalts List the objects that can have alternatives configured listfiles List the files that are supplied by the named package listnames List all known packages or those containing supplied string newList packages that became available since last update newupgradesList packages newly available for upgrading orphansList libraries not required by any installed package purge Remove one or more packages and configuration files reconfigureReconfigure the named installed packages reinstall Reinstall each of the named packages remove Remove one or more packages (see also purge) repackage Generate a .deb file for an installed package reset Initialise or reset the wajig archive files search Search for packages containing listed words source Retrieve and unpack sources for the named packages status Show the version and available version of packages toupgrade List packages with newer versions available for upgrading update Update the list of downloadable packages updatealts Update the default alternative for things like x-window-manager upgradeUpgrade all of the installed packages whatis For each package named obtain a one line description whichpkg Find the package that supplies the given command or file Command line options: -h|--help Print usage message. -q|--quiet Do system commands everything quietly. -t|--teaching Trace the sequence of commands performed. -v|--verbose=n Increase (or set) the level of verbosity (to n). Run `wajig -vv help' for documentation. Regards, Graham Williams
Re: Openssl - progression into testing
Oliver Elphick olly@lfix.co.uk immo vero scripsit And what does this mean? out of date on ia64: libssl-dev, libssl0.9.6, openssl (from 0.9.6b-1) there are up to date bins in ia64 also There is a version of the package built on ia64, which has not yet been uploaded. Which could mean anything from lack of human intervention to people holding back an upload due to some serious errors, like toolchain problems. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Re: Openssl - progression into testing
On Wed, Sep 26, 2001 at 09:48:42PM +0900, Junichi Uekawa wrote: Oliver Elphick olly@lfix.co.uk immo vero scripsit And what does this mean? out of date on ia64: libssl-dev, libssl0.9.6, openssl (from 0.9.6b-1) there are up to date bins in ia64 also There is a version of the package built on ia64, which has not yet been uploaded. No, it means that the source package has some up-to-date binary packages (i.e. Architecture: all packages), but the architecture-dependent packages have not yet been built/uploaded. -- Colin Watson [EMAIL PROTECTED]
Re: bind9-chroot (was: questions on ITP)
On 25-Sep-01, 09:34 (CDT), Christian Kurz [EMAIL PROTECTED] wrote: On 01-09-25 Steve Greenland wrote: I am so tired of hearing things like this. Nobody is forcing anyone to do anything. We already force them to use 2.2 instead of still using 2.0. You want the functionality, you use the right tools. You want to Were exactly do we force them? Which debian packages do not work well with a 2.0.x kernel? The standard Debian distribution kernel is 2.2. stick with 2.2, then *you* deal with the issues. The maintainers have That's a nice attitude, which will lead to the situation that people, especially administrators, will move away from debian to either other distributions, a bsd flavour or other free operating systems. Why? Because we don't change every aspect of our default system to cater to their individual preferences? One of the reasons that there are so many Linux distributions is that every body has a different idea of the right way, and no single distribution can make everyone happy. That's fine. Steve -- Steve Greenland [EMAIL PROTECTED]
Re: XFS Kernel image packaging
At this time being, there's no official XFS kernel images nor patches in Debian, however there is xfsprogs as far as I know in Woody Sid. I am willing to work on an XFS kernel floppy boot disk, but it would be pointless cine a kernel image with XFS is bloated by about 300K if I'm not mistaken, at least the ones on some of the machines I put XFS into. There are Reiserfs images avaiable however. I certainly would like to get a hold of some XFS based install disks if anyone ever has done any with success. kernel-patch-xfs is most certainly in woody and sid. -Ed
Re: Questions regarding the Security Secretary Position
On Wed, Sep 26, 2001 at 10:54:43AM +0200, Josip Rodin wrote: On Mon, Sep 24, 2001 at 09:53:26AM +0200, Martin Schulze wrote: However, the more people are involved, the more coordination has to be done. And considering we're all antisocial disobliging SoBs, this is a fatal flaw ; Joey's just worried that too many people can get a hold of his token. :) -- G. Branden Robinson| Debian GNU/Linux | // // // / / [EMAIL PROTECTED] | EI 'AANIIGOO 'AHOOT'E http://people.debian.org/~branden/ | pgpECM17efIY5.pgp Description: PGP signature
Re: MUAs and Locking Was: Re: PROPOSED: slight change to wnpp procedures
On Wed, Sep 26, 2001 at 02:33:04AM -0500, Scott Dier wrote: * Anthony Towns aj@azure.humbug.org.au [010925 22:59]: Why, btw, are you uploading a NEW package with the maintainer set to -qa, especially when -qa has already asked for the package to be removed from It's absouletly horrid code to look at and has a locking scheme I wish not to overhaul to get into the fnctl, then dotlock policy. Right now it seems to dotlock only, never fnctl. It might not be a bad idea for MUA maintainers to check on how their packages handle the munging of mailboxes. This can be a pretty 'critical' thing because users using NFS mounted mailspools can quickly lose whole spools with bad locking practices. This is well and good, but offtopic. This thread isn't (supposed to be) about xmailtool, it's about ITP bug reports being in a state that more accurately represents what's going on with the corresponding packages. I posted no ITP for xmailtool, for two reasons: 1) It wasn't really new, since madison knew about it, and it exists in the current release of Debian; and 2) I wasn't sure I wanted to maintain it. If xmailtool implements brain-dead mail locking, I'm pretty sure I don't want to dirty my hands with it. -- G. Branden Robinson| If you have the slightest bit of Debian GNU/Linux | intellectual integrity you cannot [EMAIL PROTECTED] | support the government. http://people.debian.org/~branden/ | -- anonymous pgpuEZLSVeKMT.pgp Description: PGP signature
Re: PROPOSED: slight change to wnpp procedures
On Wed, Sep 26, 2001 at 04:54:29PM +0900, Junichi Uekawa wrote: Rather than making it to be reassigned to something else, it might be better to retitle it to make it look ITP-uploaded: package - description or Uploaded: package - description and still assigned to wnpp. It will make clearer which packages are still in preparation and which are not (which is not obvious in the current state), and not make ftp.debian.org overloaded with bugs. I don't really see how retitling is any better than reassigning. As with account creation for New Maintainers, inclusion of an uploaded package with an ITP bug against it is the final stage in the realization of the new package. We don't have fully fledged new developers until their accounts are created; we don't have fully fledged new packages until dinstall/katie can pull them into the archive. Also, I don't think ftp.debian.org will be overloaded with open bugs; getting new packages that have been ITP'ed into the archive is just as important a function as removing packages that have been orphaned, and we file bugs for that. Furthermore, as I said, this gives a place for people to post reasons why a package may not be acceptable for inclusion into the archive. Finally, should the ftp.debian.org buglist start to back up, it might serve as a useful barometer telling us that we need to add members to the team. (As they are delegates of the Project Leader, though, it's up to the DPL to make this call, as I understand it.) But it's one more step to the procedure, and I guess it will add to the confusion / manual mistakes. That could be a risk. Does it outweigh the benefits? -- G. Branden Robinson|The first thing the communists do Debian GNU/Linux |when they take over a country is to [EMAIL PROTECTED] |outlaw cockfighting. http://people.debian.org/~branden/ |-- Oklahoma State Senator John Monks pgpG81xPuCuYp.pgp Description: PGP signature
Re: xmodmap???
#include hallo.h Michael Meskes wrote on Tue Sep 25, 2001 um 08:16:35PM: Sorry you misunderstood me. I was able to get the Euro symbol but I have to run xmodmap every time I start X by hand. It should be run automatically and in fact it is, but the result is somehow overwritten again. BTW this is version 4.1.0-5. I know this problem, and I filed a bug on it, but it was not reproducible, when the environment _before_ running startx has [EMAIL PROTECTED] So I assumed that the Xserver behaves correctly and closed the bug. Feel free to reopen if you definitely have set the environment before starting X and the problem appears though. Gruss/Regards, Eduard. -- !netgod:*! time flies when youre using linux !doogie:*! yeah, infinite loops in 5 seconds. !Teknix:*! has anyone re-tested that with 2.2.x ? !netgod:*! yeah, 4 seconds now
Re: lintian releases
On 25-Sep-01, 17:56 (CDT), Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: a) you declare a relation on a package more than once i.e. Depends: foo, foo ( 2.0). Note this check assumes that '|' relations are sane, so Depends: foo | bar | baz, foo is ok. How is that sane? I'm parsing that as (foo OR bar OR baz) AND foo, which is the same as (bar OR baz) AND foo, right? If so, it should be flagged as an error. (Yes, the dependendcy resolver should reduce it correctly, but it should reduce foo, foo ( 2.0) to simply foo ( 2.0) as well.) Steve -- Steve Greenland [EMAIL PROTECTED]
Re: bind9-chroot (was: questions on ITP)
On 01-09-26 Riku Voipio wrote: On Tue, Sep 25, 2001 at 04:34:31PM +0200, Christian Kurz wrote: On 01-09-25 Steve Greenland wrote: I am so tired of hearing things like this. Nobody is forcing anyone to do anything. We already force them to use 2.2 instead of still using 2.0. You want the functionality, you use the right tools. You want to Were exactly do we force them? Which debian packages do not work well with a 2.0.x kernel? apt-cache search usb for example. Which package exactly do you mean? I don't see any package in that list which would force you to use a kernel 2.4.x. Also do you really want to compare hardware for the usb port with a daemon that you run on a server? stick with 2.2, then *you* deal with the issues. The maintainers have That's a nice attitude, which will lead to the situation that people, especially administrators, will move away from debian to either other distributions, a bsd flavour or other free operating systems. Forcing new users to deal with historic burden is not an answer. Pardon? New users are absolutely not forced to deal with historic burden. I'm just proposing that any script or debian package which offers to create a bind chroot should not depend on new kernel specific stuff like mount -bind. I really can't understand your problem with limiting chroot bind9 feature to kernels with --bind mounts support. They still can run bind9 perfectly, although less securely. So, you want to either force every admin running bind9 to either upgrade to kernel 2.4.x or have a less secure system? That's like I stated before a good approach if you want to have people move to some other distribution or free operating system, but not to have people use debian anymore. If 2.2 kernel users want chrooted bind, they a) have already done it - no extra work So let's forget those users and ignore that they maybe also happy about having a debian package set up a chroot for them? b) upgrade to 2.4 - sheez, that was hard... Which is not always an option. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgpRrzThslsXy.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
On 01-09-26 Roberto Suarez Soto wrote: On Sep/26/2001, Christian Kurz wrote: I think that maybe he refers to the fact that, for example, you may have formatted your ext2 partitions so they are incompatible with 2.0.x Well, I once heared about this, but never read an explanation what exactly causes the differences in the ext2 partitions created while running a 2.0.x kernel and why they have been introduced. The features are documented in mke2fs(8), under -O (or it seems, for what I've seen). They don't seem to be too useful (unless I'm missing something), but anyway they are there. Thanks for the pointer, which explains the features and partly reasons for them. If someone has a pointer to an even more detailed or longer explanation, please mail me. Well, iptables is only available for kernel 2.4.x, but with kernel 2.2.x you can still build a firewall with ipchains or ipfwadm if you still use Yes, but it's not the same building a firewall with 2.4.x and building a firewall with 2.2.x or 2.0.x. There are a few things that you can do only with 2.4, not with lower versions. Stateful firewalling, for example. Well, you may have not the full features available but you can build with all version a firewall and have at least filtering per ip or port available. So compared to the situation with bind, by using cp,rsync or some other tool for keeping the config files in sync, this would still be possible. If mount -bind is used for creating the chroot this would not be possible and it would be like needing kernel 2.4.x for building a firewall. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgpf6TNPq43Ox.pgp Description: PGP signature
Re: PROPOSED: slight change to wnpp procedures
Branden Robinson wrote: On Wed, Sep 26, 2001 at 04:54:29PM +0900, Junichi Uekawa wrote: Rather than making it to be reassigned to something else, it might be better to retitle it to make it look ITP-uploaded: package - description and still assigned to wnpp. But it's one more step to the procedure, and I guess it will add to the confusion / manual mistakes. That could be a risk. Does it outweigh the benefits? It doesn't need to be done manually. katie sends me an email telling me I uploaded a NEW package which requires human intervention. It could also email the bug if it sees the changelog closes in ITP bug (would we need to format them in a special way perhaps?). I don't see a problem with reassigning the bug to ftp.debian.org, and I think it's a _good_ idea. Peter
Re: xmodmap???
On Wed, Sep 26, 2001 at 06:35:16PM +0200, Eduard Bloch wrote: I know this problem, and I filed a bug on it, but it was not reproducible, when the environment _before_ running startx has [EMAIL PROTECTED] So I assumed that the Xserver behaves correctly and Hmm, I use gdm to log in. Will try with startx later. closed the bug. Feel free to reopen if you definitely have set the environment before starting X and the problem appears though. I didn't find that one. Hmm, maybe is misspelled the package name. Michael -- Michael Meskes Michael@Fam-Meskes.De Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Re: lintian releases
Steve Greenland wrote: On 25-Sep-01, 17:56 (CDT), Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: a) you declare a relation on a package more than once i.e. Depends: foo, foo ( 2.0). Note this check assumes that '|' relations are sane, so Depends: foo | bar | baz, foo is ok. How is that sane? I'm parsing that as (foo OR bar OR baz) AND foo, which is the same as (bar OR baz) AND foo, right? Perhaps he meant to write: foo | bar, foo | baz same as (foo) OR (bar AND baz) Peter
Re: lintian releases
On 26-Sep-2001 Steve Greenland wrote: On 25-Sep-01, 17:56 (CDT), Sean 'Shaleh' Perry [EMAIL PROTECTED] wrote: a) you declare a relation on a package more than once i.e. Depends: foo, foo ( 2.0). Note this check assumes that '|' relations are sane, so Depends: foo | bar | baz, foo is ok. How is that sane? I'm parsing that as (foo OR bar OR baz) AND foo, which is the same as (bar OR baz) AND foo, right? If so, it should be flagged as an error. (Yes, the dependendcy resolver should reduce it correctly, but it should reduce foo, foo ( 2.0) to simply foo ( 2.0) as well.) Consider you have a package which wants a utility to parse html and a utility to download webpages. lynx happens to handle both. So you have: Depends: lynx | web-retriever, lynx | web-parser | perl-web-parser. If you left lynx out of either depends you would be forced to install a useless package. So I assume that OR statements are sane and do not parse them.
Re: PROPOSED: slight change to wnpp procedures
On 25-Sep-01, 22:59 (CDT), Anthony Towns aj@azure.humbug.org.au wrote: and filing, what, a dozen new bugs against ftp.debian.org every week is something other than harassment [0]? How is it harrasment? It's a todo list. And won't the bug be closed automatically when the package is installed? So it's hardly any extra effort for the ftp maintainers, and it provides a public and consistent place to track the status of packages with problems. Steve -- Steve Greenland [EMAIL PROTECTED]
Re: PROPOSED: slight change to wnpp procedures
Branden Robinson [EMAIL PROTECTED] writes: As with account creation for New Maintainers, inclusion of an uploaded package with an ITP bug against it is the final stage in the realization of the new package. We don't have fully fledged new developers until their accounts are created; we don't have fully fledged new packages until dinstall/katie can pull them into the archive. Also, I don't think ftp.debian.org will be overloaded with open bugs; getting new packages that have been ITP'ed into the archive is just as important a function as removing packages that have been orphaned, and we file bugs for that. I can understand your argument for reassigning the bugs and in principle I agree with it. My only objection is that people would have to check http://bugs.debian.org/ftp.debian.org instaed of http://bugs.debian.org/wnpp or http://www.debian.org/devel/wnpp to find out about uploaded packages. Making www.d.o/devel/wnpp fetch the relevent ftp.d.o bugs would be trivial. Furthermore, as I said, this gives a place for people to post reasons why a package may not be acceptable for inclusion into the archive. That's something that I'd like to see. There's a WNPP page listing software that can't be packaged, but some stuff there lacks a reason. Links to archived debian-legal or -devel mails would be enough, but, should the need exist, archived bugs closed by ftp-master would be a nice thing to have, too. -- Marcelo | Give anyone a lever long enough and they can change [EMAIL PROTECTED] | the world. It's unreliable levers that are the problem. | -- (Terry Pratchett, Small Gods)
Re: PROPOSED: slight change to wnpp procedures
On Wed, Sep 26, 2001 at 08:42:18PM +0200, Marcelo E. Magallon wrote: I can understand your argument for reassigning the bugs and in principle I agree with it. My only objection is that people would have to check http://bugs.debian.org/ftp.debian.org instaed of http://bugs.debian.org/wnpp or http://www.debian.org/devel/wnpp to find out about uploaded packages. Making www.d.o/devel/wnpp fetch the relevent ftp.d.o bugs would be trivial. Well, the bug could be reassigned to wnpp,ftp.debian.org. That should work with the current BTS without changing anything. In general it's a bad idea to assign a bug to more than one package, but this might be one of those cases where it makes sense. -- G. Branden Robinson| Debian GNU/Linux | If ignorance is bliss, [EMAIL PROTECTED] | is omniscience hell? http://people.debian.org/~branden/ | pgpclcRXhed44.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
On Sep 26, Peter Palfrader [EMAIL PROTECTED] wrote: Are there any problems I missed with cimply copying the files? Yes: people do not want to restart bind at every configuration changes. Mount -bind is no option, hardlinks aren't either. Symlinks from mount --bind is the right solution for people using 2.4 kernels. -- ciao, Marco
letters in upstream version numbers
Lintian gives errors when looking at a package with letters at the beginning of the upstream version number. Ch. 4 of policy indicates that the upstream version can't begin with a letter. However, it doesn't really indicate what should be done in case an upstream version does begin with letters. In the case of the latest iputils package, it is ss010824. Should I just drop the letters from the version number, or is there some other preferred way of making it comply with policy. It might be worth it to add some text to policy clarifying this issue. Thanks. noah -- ___ | Web: http://web.morgul.net/~frodo/ | PGP Public Key: http://web.morgul.net/~frodo/mail.html pgpQpFoEXi1bN.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
On Wed, 26 Sep 2001, Marco d'Itri wrote: On Sep 26, Peter Palfrader [EMAIL PROTECTED] wrote: Are there any problems I missed with cimply copying the files? Yes: people do not want to restart bind at every configuration changes. good point. Mount -bind is no option, hardlinks aren't either. Symlinks from mount --bind is the right solution for people using 2.4 kernels. AFAIK mount -o ro --bind /etc/ foo/etc does not mount readonly. So there would be write access to the root partition in the chroot. I usually put chroots in a partition (or lv) of their own. yours, peter -- PGP signed and encrypted | .''`. ** Debian GNU/Linux ** messages preferred.| : :' :By professionals, | `. `' for professionals http://www.palfrader.org/ | `-http://www.debian.org/
Re: letters in upstream version numbers
Previously Noah L. Meyerhans wrote: However, it doesn't really indicate what should be done in case an upstream version does begin with letters. It shouldn't. Try prefixing it with a 0 or so. Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
RE: letters in upstream version numbers
On 26-Sep-2001 Noah L. Meyerhans wrote: Lintian gives errors when looking at a package with letters at the beginning of the upstream version number. Ch. 4 of policy indicates that the upstream version can't begin with a letter. However, it doesn't really indicate what should be done in case an upstream version does begin with letters. In the case of the latest iputils package, it is ss010824. Should I just drop the letters from the version number, or is there some other preferred way of making it comply with policy. It might be worth it to add some text to policy clarifying this issue. A problem here is knowing what is the next version. Is it st010824? maybe ss010825? I think a common solution is to put '0.' or '1.' in front of the upstream.
Re: letters in upstream version numbers
Noah L. Meyerhans writes: In the case of the latest iputils package, it is ss010824. I assume 'ss' means 'snapshot'. You should use a version of the form 20010824, and ask upstream to change. If a 'normal' version number is anticipated soon, and you want to be able to switch without using an epoch, you can use something like 0.0.20010824 (this seems to be existing practice, anyway). P.S. your Mail-Followup-To: appears to be broken. Mutt came up with a message addressed to 'frodo' (in addition to -devel). -- things change. [EMAIL PROTECTED]
Re: new packages: divx4linux and transcode
Andreas Metzler wrote: Yes, if you want mp3-Encoding. I see that it links against libvorbis, so perhaps sometime it'll be possible to use vorbis for soundcompression. cu andreas Yep - as soon as we will have more programmers in avifile team :) [EMAIL PROTECTED]
Re: bind9-chroot (was: questions on ITP)
Peter Palfrader [EMAIL PROTECTED] writes: AFAIK mount -o ro --bind /etc/ foo/etc does not mount readonly. So there would be write access to the root partition in the chroot. If they are not writable by the user of the chroot process, that isn't a problem. If the attacker gets root, the user can break the chroot. -- Alan Shutko [EMAIL PROTECTED] - In a variety of flavors! Anyone stupid enough to be caught by the police is probably guilty.
Re: lintian releases
On Wed, Sep 26, 2001 at 12:36:29PM -0500, Steve Greenland wrote: How is that sane? I'm parsing that as (foo OR bar OR baz) AND foo, which is the same as (bar OR baz) AND foo, right? Err, (foo OR bar OR baz) AND foo != (bar or baz) AND foo, because it can also be foo AND foo (= foo). Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: lintian releases
On Thu, Sep 27, 2001 at 08:30:48AM +1000, Hamish Moffatt wrote: On Wed, Sep 26, 2001 at 12:36:29PM -0500, Steve Greenland wrote: How is that sane? I'm parsing that as (foo OR bar OR baz) AND foo, which is the same as (bar OR baz) AND foo, right? Err, (foo OR bar OR baz) AND foo != (bar or baz) AND foo, because it can also be foo AND foo (= foo). So essentially it is the same as foo, bar and baz are irrelevant. Duncan Findlay
Mounts with fs type 'none'
I've a request to have checksecurity skip searching filesystems with type 'none' (not device 'none'). A brief check leads me to believe that these are result of mount --bind, which means that the mount in question is either searched or skipped in its real location, and need not be searched in its bind location. Is this correct? Are there other types of mounts that lead to type=none in the output of 'mount'? Thanks, Steve -- Steve Greenland [EMAIL PROTECTED]
Re: Mounts with fs type 'none'
On Wed, Sep 26, 2001 at 06:15:34PM -0500, Steve Greenland wrote: I've a request to have checksecurity skip searching filesystems with type 'none' (not device 'none'). A brief check leads me to believe that these are result of mount --bind, which means that the mount in question correct, mount --bind is just a shortcut for: mount -t none -o bind /somewhere /some/where/else -- Ethan Benson http://www.alaska.net/~erbenson/ pgpJ94Db6avqu.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
also sprach Tollef Fog Heen (on Wed, 26 Sep 2001 10:25:15AM +0200): The right way is, imho, the way postfix deals with it. It took quite some time before I discovered it chrooted itself. i disagree stronlgy mainly because of things like tripwire, which i think should be scanning *everything* but a small list of exceptions - not a list of things to scan and to ignore all rest. /var/spool/postfix contains some very important files that (a) affect the way postfix is working and how secure it is, and (b) are static files in that they don't change between boots. therefore, you tripwire them -- which is useless if every restart of postfix causes tripwire to bitch. martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] -- pgpQPCcVTxwDs.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
also sprach Junichi Uekawa (on Wed, 26 Sep 2001 09:23:32PM +0900): By the way, are we talking about running bind as non-root inside a chroot, or are we talking about running bind as root inside a chroot? is that a serious question? just *why* would you ever run bind9 as root? martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] -- pgpE0Ow4QTeTX.pgp Description: PGP signature
Re: bind9-chroot (was: questions on ITP)
also sprach Christian Kurz (on Tue, 25 Sep 2001 10:11:07AM +0200): But having a link from either the config-files in /etc/bind to $CHROOT or in the other direction, could be in my opinion a security risk. In my opinion there should be absolutely no link from $CHROOT to any file outside the chroot. So instead of creating a $CHROOT that contains everything without any link to the outside you want to decrease the security by having links from outside to inside? I don't agree with that and would instead suggestion to modify the documents stating that all config files should be in /etc to make a exception for $CHROOT. please explain how a symlink /etc/bind - /var/chroot/bind/etc would be a security problem? martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] -- no problem is so formidable that you can't just walk away from it. -- c. schulz pgpLiQjKjYQwP.pgp Description: PGP signature
Re: Mounts with fs type 'none'
On 26-Sep-01, 18:31 (CDT), Ethan Benson [EMAIL PROTECTED] wrote: On Wed, Sep 26, 2001 at 06:15:34PM -0500, Steve Greenland wrote: I've a request to have checksecurity skip searching filesystems with type 'none' (not device 'none'). A brief check leads me to believe that these are result of mount --bind, which means that the mount in question correct, mount --bind is just a shortcut for: mount -t none -o bind /somewhere /some/where/else Thanks. Does anything else use '-t none'? (And why does mount(8) document '--bind' but not '-t none' or '-o bind'?) Steve -- Steve Greenland [EMAIL PROTECTED]
Re: Mounts with fs type 'none'
On Wed, Sep 26, 2001 at 06:53:54PM -0500, Steve Greenland wrote: Thanks. Does anything else use '-t none'? i don't know, not that i know of, but i wouldn't rule it out in the future given `none' is pretty generic. (And why does mount(8) document '--bind' but not '-t none' or '-o bind'?) i don't know that either.. i prefer the latter since its standard usage of mount, it also makes it more clear that something like this in /etc/fstab will (and does) work as expected: /tmp/var/tmpnonebind0 0 -- Ethan Benson http://www.alaska.net/~erbenson/ pgpUDvD8DPNqK.pgp Description: PGP signature
Re: XFS Kernel image packaging
On Tue, Sep 25, 2001 at 01:12:52PM -0600, Russel Ingram wrote: Pardon me if I sound like a newbie here. I am fairly new to the Debian way, but I am a Linux veteran. I have noticed that there are patches available in the debian package tree for the XFS filesystem but there are no available kernel-image packages with XFS already built in. Is there a specific reason for this or is it just because no one has stepped forward to offer such a package? because it's not necessary. we already have way too many kernel-images with trivial feature variations - that have no business being in debian supplied kernels, but should be compiled by those who need them when they need them. debian should provide only the bare minimum number of kernel images that are required to install debian...anything else should be a custom kernel compile by the end user. if and when XFS support gets into the mainstream kernel, then support for it should be compiled in. until then, it's only one of many optional patches available. in the meantime, if you want to compile a kernel with xfs support: 1. apt-get install kernel-source-2.4.9 kernel-package (you'll also need gcc and bin86 and so on, of course...and libdb3-dev if you want to compile aic7xxx support) 2. download the appropriate patch version from ftp://oss.sgi.com/projects/xfs/download/ 3. patch the kernel 4. there will be one reject, in .../linux/init/main.c - it's easy enough to patch this by hand with vi. 5. run make config and make-kpkg - whatever your usual kernel compile procedure is. i've done this dozens of times now. it works. I've used the make-kpkg command to create kernel packages, but they always come out with a custom-1.00 label on them and I haven't figured out how to get around that. RTFM. see the --revision option. craig -- craig sanders [EMAIL PROTECTED] Fabricati Diem, PVNC. -- motto of the Ankh-Morpork City Watch
A language by any other name
I think English should be an alias for en_US. Having the English think that British English is the lingua franca of the computing world is the same as the French thinking that French is the lingua franca of the world. It's only wishful thinking. British English is beautiful where it appears in poems, plays, and novels by Shakespeare and Wilde and other brilliant English authors. It certainly does NOT belong in the ls man page. Note that SAP is one of many computing companies who have standardized on American English. They have folks from *Great Britain* translating the German into American English. Similarly, I wish that Debian required that documentation and output appear in American English as well. Inconsistent styles reduces the professional feel of the product. Therefore, without emotion and with a pragmatic hand to guide me, I feel that English should be an alias for en_US. -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and mh-e. Vote Libertarian! If you're passed on the right, you're in the wrong lane.
Re: Why I can not go ahead with IMP?
Hi, I have a long standing open ITP for squirrelmail. For various reasons I am unable to finish the package to my satisfaction and have been looking for someone to take it on. I have a mostly finished package with a couple of small bugs in it if anyone is interested in taking it over. See the ITP for further explanation. Bart Scott Dier writes: I got sick of how nasty IMP was getting and moved to squirrelmail recently. I dont think theres a package out there yet, nor do I know of a tool to move IMP database-driven address books to squirrelmail's format (yet).
Bug#113653: ITP: links-lua-ssl -- a fork of links supporting lua language, resulting a programmable browser with hooks
Package: wnpp Version: 0.96; reported 2001-09-27 Severity: wishlist * Package name: links-lua-ssl Version : 0.96p11 Upstream Author : links-lua team * URL : http://sourceforge.net/projects/links/ * License : GPL Description : a fork of links supporting lua language, resulting a programmable browser with hooks the package will contain patches the upstream author did not want to include, including, but not limited to IPv6, the dummy javascript patch, and other smaller ones like http_proxy env support. i do not intend to package non-ssl version, either because there's already enough links exist in debian, or because everyone uses ssl version anyway. the package is available for texting at: ftp://yikes.tolna.net/pub/linux/release/debian/links-lua-ssl_0.96-0.0_i386.deb advices are welcome, please cc to personal email. -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux Yikes 2.2.19 #1 Fri Apr 6 03:40:59 CEST 2001 i686 Locale: LANG=C, LC_CTYPE=hu_HU
Re: A language by any other name
On Wed, Sep 26, 2001 at 05:32:08PM -0700, Bill Wohler wrote: I think English should be an alias for en_US. Having the English think that British English is the lingua franca of the computing world is the same as the French thinking that French is the lingua franca of the world. It's only wishful thinking. British English is beautiful where it appears in poems, plays, and novels by Shakespeare and Wilde and other brilliant English authors. It certainly does NOT belong in the ls man page. Note that SAP is one of many computing companies who have standardized on American English. They have folks from *Great Britain* translating the German into American English. Similarly, I wish that Debian required that documentation and output appear in American English as well. Inconsistent styles reduces the professional feel of the product. Therefore, without emotion and with a pragmatic hand to guide me, I feel that English should be an alias for en_US. As a Canadian, I find it quite frustrating how Americans find that all English on the internet should be American. Further, I don't understand why Americans insist on removing the u in words like colours. But, putting my own radical beliefs aside, I think that English should definitely be an alias for en_GB, seeing how American really isn't English per se. I also think it's ridiculous that everybody be forced to write Debian documentation in American English. Debian is an international project, and only in the US is American English the standard. There are dozens of countries that use a dialect closer to British than American. BTW, you might think that Canadians use American English, after all, we are neighbours, but that's totally incorrect. I apologise, I have not been following this thread until now, so if I just said exactly what someone else said, that please feel free to ignore me. Duncan Findlay
Re: A language by any other name
British English is beautiful where it appears in poems, plays, and novels by Shakespeare and Wilde and other brilliant English authors. It certainly does NOT belong in the ls man page. Why such emphasis? The idea is to spell words like colour instead of color, not to write the ls man page in iambic pentameter. I am reminded of an email I saw some years ago with error messages in Haiku. Ben. :)
Re: Why I can not go ahead with IMP?
also sprach bart bunting (on Thu, 27 Sep 2001 10:32:52AM +1000): I have a long standing open ITP for squirrelmail. For various reasons I am unable to finish the package to my satisfaction and have been looking for someone to take it on. I have a mostly finished package with a couple of small bugs in it if anyone is interested in taking it over. See the ITP for further explanation. i'll take it, but i won't be able to get to it before mid-october... martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] -- all i ask of life is a constant and exaggerated sense of my own importance. pgpRYz1GRCQAY.pgp Description: PGP signature
Re: A language by any other name
On Wed, 2001-09-26 at 20:50, Ben Burton wrote: British English is beautiful where it appears in poems, plays, and novels by Shakespeare and Wilde and other brilliant English authors. It certainly does NOT belong in the ls man page. Why such emphasis? The idea is to spell words like colour instead of color, not to write the ls man page in iambic pentameter. I am reminded of an email I saw some years ago with error messages in Haiku. I think I'd RTFM a lot more if the man pages *were* in Iambic Pentameter... ~,^ Ben. :) Sean Etc.
Re: A language by any other name
also sprach Duncan Findlay (on Wed, 26 Sep 2001 08:54:40PM -0400): But, putting my own radical beliefs aside, I think that English should definitely be an alias for en_GB, seeing how American really isn't English per se. agreed! martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] -- riesco a leggerti i pensieri. dovresti vergognarti. pgpeGH7GU2vSY.pgp Description: PGP signature
Re: new port: and the winner is....
On Mon, Sep 24, 2001 at 08:42:31AM -0300, Henrique de Moraes Holschuh wrote: The point being? We do not have to waste time with that now, at least not with the kernel. We still need not to get too trigger happy with hardware and firmware, but otherwise... I won't help a Microsoft windows port. I expect a lot of others not to. It does not mean I'll lose my time trying to block such a port, but I *will* take time to stop such a port from tainting the Debian name (if someone pushes for it to become an officially supported port in the archive) UNTIL there is a DFSG-compliant kernel for it to run on top of. Hmmm..., anybody considering a port to one of the FreeDOS arch's? (there may only be one, but I can't remember anymore) There are debian packages out there for commercial X servers after all...
Re: A language by any other name
On Wed, 26 Sep 2001, Bill Wohler wrote: I think English should be an alias for en_US. Of course you do; you're /from/ the US. Having the English think that British English is the lingua franca of the computing world is the same as the French thinking that French is the lingua franca of the world. It's only wishful thinking. And believing that not just English, but /American/ English is somehow universal is the sort of arrogance typical of the provincial mindset for which Americans are notorious. Note that SAP is one of many computing companies who have standardized on American English. They have folks from *Great Britain* translating the German into American English. And as a corporation, they're free to slight as many people as they want if it leads to higher profits.[1] But Debian is built on consensus, not on profit margins. We already have a consensus that there can never be a consensus on pointing 'English' to any particular regional variant of the language, because there is no single right answer to the question of which one is English. Similarly, I wish that Debian required that documentation and output appear in American English as well. Inconsistent styles reduces the professional feel of the product. I observe here, wryly, that a larger percentage of work done on Debian, including documentation work, is done by non-native speakers of English than is done by native speakers of British English. Steve Langasek postmodern programmer [1] And British translators translating German text to American English is a testament only to the intellectual prowess of the British translators, not to the natural superiority of the American tongue.
Re: A language by any other name
On Wed, Sep 26, 2001 at 09:07:27PM -0400, Sean Middleditch wrote: On Wed, 2001-09-26 at 20:50, Ben Burton wrote: British English is beautiful where it appears in poems, plays, and novels by Shakespeare and Wilde and other brilliant English authors. It certainly does NOT belong in the ls man page. Why such emphasis? The idea is to spell words like colour instead of color, not to write the ls man page in iambic pentameter. I am reminded of an email I saw some years ago with error messages in Haiku. I think I'd RTFM a lot more if the man pages *were* in Iambic Pentameter... ~,^ I wouldn't -- I'd get kinda confused :-) Duncan
