Re: Increasing regularity of build systems
> On Fri, 17 Sep 1999 11:13:49 +0200 (CET), Santiago Vila <[EMAIL > PROTECTED]> said: Santiago> David Welton wrote: >> Xemacs21 - runs *autoconf* to generate other makefiles, which are >> then run. [...] autoconf doesn't generate makefiles. It generates a configure file. >> Do you seem what I mean? Each of these is doing something >> slightly different, and it is a bit frustrating not to see a bit >> more cohesiveness. Not that any of these things are *bad*, per >> se, just that there seem to be a lot of packages that do stuff >> like this. Santiago> Well, for this particular case (xemacs21), I think that Santiago> running autoconf in the debian/rules file is "bad per se", Santiago> and should be discouraged at least, if not forbidden by Santiago> policy (I guess it is already forbidden by the GNU Santiago> standards). You could have pointed it out to me in private rather than say bad things where I wouldn't notice (just happened to grep the mail folder because I was looking for another old message). There actually is a reason it was done (the configure.in file was modified. Know any other way to recreate the configure file?). As it is this is no longer neccessary and will go away (patch upstream fixes the problem I was having). At least I did remove the configure file so that the patch wasn't ungodly large. Dres -- @James LewisMoss <[EMAIL PROTECTED]> | Blessed Be! @http://www.ioa.com/~dres | Linux is kewl! @"Argue for your limitations and sure enough, they're yours." Bach
Re: APRIS GNU/LINUX EXPO UPDATES. (need debian Logo).
Jeff Teunissen wrote: > Speaking of the open use logo, was it intentional or an unintentional > artifact of the conversion from EPS to xfig that changed the shape of the > letters and the logo itself? Unintentional, I think. I have .ps files with the correct shapes, and have sent them to the web team, but nothings been done yet. -- see shy jo
Re: Guessing the date style from the timezone for postgresql postinst
At 20:58 -0300 1999-09-18, Nicolás Lichtmaier wrote: Well.. the libc maintainers don't want to add the locale for my country for no reason, even if it is included in the package as source. I use a target in the glibc makefiles to generate the locales, if it doesn't generate the one for your country, there's nothing I can do about it. -- Joel Klecker (aka Espy)Debian GNU/Linux Developer mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED]> http://web.espy.org/> http://www.debian.org/>
Re: Announcing debconf, configuration management for debian
I've sent this to the debian-devel list because I've tried to add some clarification to my suggestions, in case they were unclear to others (it seems they may have been). Note that none of my suggestions are in any way negative criticisms. debconf looks incredibly useful as it is, and I just had some thoughts I wanted to share. So, let me clarify my suggestions: 1) This was a suggestion relating to package management (through dpkg, only indirectly to debconf). I'm suggesting a ConfigScript parameter in the package control file, so that debconf's hacks (Joey's term) are not necessary. This suggestion was aimed at dpkg more than debconf. 2) I think I presented this suggestion backwards. According to debconf's docs, a user will be prompted for the answer to a question only if they haven't already answered that question, and only new questions will be presented. I'm suggesting there be a way for a user to over-ride this behaviour and completely reconfigure a package if they want. Am I still missing something in the docs? Is this already possible? 3) I see I missed the substitution capability during my first read of the docs. Sorry about that. But the rest of this suggestion is still valid, in that I'm looking for a way to repackage a package with whatever new defaults I want. Again, this may not be related directly to debconf, but perhaps needs to be implemented in dpkg-repack. My apologies for the lack of clarity in my original email. I hope I have made my suggestions more clear now. > > Looking for a husband? Know anyone looking for a husband? Well, I'm looking > > for a wife. See http://www.mostlylinux.ab.ca/scott/wife.shtml > > I didn't follow the URL to see if this is a joke, but if it is not, you do > not know what powers of restraint it requires to stay away from THIS fish > hook. Hey, don't knock it :) It's been working, and I've been meeting people. -- Scott Barker [EMAIL PROTECTED] Linux Consultant http://www.mostlylinux.ab.ca/scott Looking for a husband? Know anyone looking for a husband? Well, I'm looking for a wife. See http://www.mostlylinux.ab.ca/scott/wife.shtml Want a good deal on a personal computer in Calgary, Alberta, Canada? Visit http://www.mostlylinux.ab.ca/scott/computers.shtml [ Unsolicited commercial and junk e-mail will be proof-read for US$100 ] "All the world's a stage and most of us are desperately unrehearsed." - Sean O'Casey
Re: A few changes
On Sat, Sep 18, 1999 at 04:09:17PM -0700, Darren Benham wrote: > Bugs are no longer deleted!!! We don't have a way for you to access them > directly but there's an "official" location in the database where they're > being archived. We're trying to decide how to serve them up... by > requesting a bug number, obviously, but any other way? Do we need them > index by maintainer or package? Remember, these are closed -- solved -- > bugs. Definately by package. I can think of several circumstances where this is useful: when a bug is closed in unstable but someone using stable wants an explanation for a problem; when a bug is inadvertantly reintroduced; when a maintainer closes a bug caused by user error, and another user does the same thing; when a package is adopted and the new maintainer wants to get a feel for the packages history and the rationale behind various packaging decisions. It would be most useful if someone could search by package name, keyword, and status of the bug report. pgpCWbv7Mlw1Y.pgp Description: PGP signature
Re: Guessing the date style from the timezone for postgresql postinst
> > Well.. the libc maintainers don't want to add the locale for my country for > >no reason, even if it is included in the package as source. > I use a target in the glibc makefiles to generate the locales, if it > doesn't generate the one for your country, there's nothing I can do > about it. Modify the makefile; report it upstream; compile it from the debian/rules.
[Q] May I take over the mmm package?
Hi, I found the mmm package for Debian is quite obsolete and not usable anymore(it depends on several old packages like libc5). I guess that's because you could not re-build it with the newer version of Objective Caml. I contacted one of the original authors(Jun P. Furuse) and he was kind enough to release 0.80beta, which can be compiled with Objective Caml 2.02. But he said they had lost interest in this project, so further improvement should not be expected. Anyway, MMM is still one of the few open-sourced(I don't understand why the INRIA license is non-free) Web browsers which can handle Japanese characters correctly, so I hope it remains a part of Debian. Now I'd like to ask you a question; are you still interested in maintaining the mmm(and ocamltk) package? If not, would you hand it over to me? You seem not to get in touch with the upstream(if not, sorry). Thanks to Joey and other guys, Debian-QA seems to revive, so if you leave mmm alone, it might be the first one to be slaughterd ;-) Unfortunately I'm not an official maintainer at present though I've already sent my application to new-maintainers (but they does not respond at all...). So if you are willing to continue your duty, that's great. For the present, I'll send a bug report to BTS. BTW, I don't read debian-devel anymore(my mailbox has been flooded...). I would appreciate if you send me a reply directly. Regards, MH -- Masayuki Hatta The University of Tokyo [EMAIL PROTECTED] / [EMAIL PROTECTED] [EMAIL PROTECTED] / [EMAIL PROTECTED]
Re: Hosed system during package build
On 17-Sep-99, 04:35 (CDT), "J.H.M. Dassen (Ray)" <[EMAIL PROTECTED]> wrote: > On Thu, Sep 16, 1999 at 20:26:15 -0500, Steve Greenland wrote: > > I saw much talk about fakeroot not working with the new glibc, much talk > > about it being difficult to fix, and no talk about it being fixed. > > Actually, AFAIK most of this talk was about /libtricks/ which was a new > approach to doing what fakeroot does (it provided a "fakeroot" binary as > well); that approach did turn out not to be usable for glibc2.1. The current > fakeroot in potato is based on the old approach, and works fine. Aaah. Understanding is. Thanks, sg -- Steve Greenland <[EMAIL PROTECTED]> (Please do not CC me on mail sent to this list; I subscribe to and read every list I post to.)
Re: ProFTPd being lame
On Sat, Sep 18, 1999 at 04:21:34PM -0700, Robert Stone wrote: > Virtualhosting in proftpd is far easier than with wu-ftpd. As it > stands now, I don't believe any debian ftp server supports virtual > anon ftp sites as provided besides proftpd. roxen does. -- Raul
Re: A few changes
In article <[EMAIL PROTECTED]> you wrote: > Bugs are no longer deleted!!! We don't have a way for you to access them > directly but there's an "official" location in the database where they're > being archived. We're trying to decide how to serve them up... by > requesting a bug number, obviously, but any other way? Do we need them > index by maintainer or package? Remember, these are closed -- solved -- > bugs. By package would be nice. Bdale
Re: Redesign of diskless NFS-root package & ITP diskless-image
On Wed, Sep 15, 1999 at 11:46:36AM +1000, Brian May wrote: > [description removed] I have made most of the changed required for my redesign of diskless. Amazingly, it looks like no changed are required for dpkg. I haven't yet tested anything though, and implementing secure mode might be a bit awkward. Currently I am considering the following: 1 installation moves /var, /dev, and /tmp into /rw/ 2 symlinks are created: /var --> /rw/var, /dev --> /rw/dev, and /tmp --> /rw/tmp. On startup (non-secure mode) /var, /dev, and /tmp are mounted as usual, over the top of the directories under /rw/ (should I do the same thing for /etc too? I inclined not to - I think it should be read-only. Making /etc read-write might make adding extra hosts easier, as all host specific data can be copied and processed on startup) On startup (secure mode) the temp directory is mounted in a temp location (eg /copy), and files all files are copied from /rw to /copy. This means the read-write files are all contained on the one partition, that could easierly be erased/formatted on startup. At this stage, /copy is re-mounted over /rw. This would be easier if I didn't have to re-mount /copy twice, I will need to think about that. The result will be that /var, /dev, and /tmp are read-write, but completely refreshed every-time the computer boots. Anyway, as part of this redesign, I propose to package a new package, diskless-image. I am not sure if I normally have to ITP a new package when it is based on the same source package, but this one is a bit unusual... ...it is not meant to be manually installed! Rather, when you create a new diskless-image with diskless-newimage, this script automatically installs diskless-image.deb with the dpkg --root parameter, so that it only effects the NFS-root image. I think it is important to have this in the Debian archive though, to make upgrades easier. I believe that creating a separate package makes diskless for modular and easier to maintain. I suspect that it will make installing different architectures easier, as diskless-image can be installed a host other then the server, but I can't test this. As it is possible that diskless-image could break your computer if installed on the root directory by mistake, I have a check in the preinst file to ensure the directory /etc/diskless-image exists. If it doesn't installation will abort. Any comments? -- Brian May <[EMAIL PROTECTED]> pgpO95a7T0PGD.pgp Description: PGP signature
Re: Move proftpd to contrib
On Sep 18, Josip Rodin <[EMAIL PROTECTED]> wrote: >An alternative is wu-ftpd. It would be rather foolish to support wu-ftpd >100%, however, it has almost the same status as sendmail - it is a very You mean that it's like sendmail, i.e. security bugs pops out every time somebody looks at the code? -- ciao, Marco
Re: A few changes
Michael Stone <[EMAIL PROTECTED]> wrote: > > Definately by package. I can think of several circumstances where this > is useful: when a bug is closed in unstable but someone using stable On a side note, it would be nice to be able to see the bugs filed against all binary packages of a source package, perhaps under the source package's bug page. -- Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Re: ProFTPd being lame
>>>Robert Stone wrote: > Virtualhosting in proftpd is far easier than with wu-ftpd. As it > stands now, I don't believe any debian ftp server supports virtual anon ftp > sites as provided besides proftpd. Roxen does, at least if you have different IP numbers, I can't get IP-less vistual hosting to work with ftp sessions. And as a ISP the security issues of Proftpd shuold be a realy big consern. > Proftpd also has a config file syntax that less experienced admins > find easier to work with (since they've all mucked with apache configs by > the time the're dealing with ftp servers). Roxen has a nice http interface for configuring. > This software is not essential, but it's certainly not useless. The suggestion was to move it to contrib allot of the software in contrib are wery usefull. / Balp
Re: Announcing debconf, configuration management for debian
Branden Robinson wrote: > Thanks again, Joey. I look forward to migrating XFree86 to debconf (won't > happen for -1, but I'm hoping to tackle FHS-compliance and this for -2). Err, can you please wait for this until a) debconf has been accepted and b) there will be proper support for it and c) proper documentation. No, I haven't looked at it yet, but I appreciate it. Regards, Joey -- GNU does not eliminate all the world's problems, only some of them. -- The GNU Manifesto Please always Cc to me when replying to me on the lists.
RE: libwxx-gtk 2.1
On 17-Sep-99 Sean 'Shaleh' Perry wrote: > I was supposed to be taking them over. However I am stretched a wee thin at > the moment. So, if you or someone else would like to help, feel free. I can't help you, I'm not able to handle that package. I was wondering about it because I was trying to compile hugo, an engine for adventure games. --- Christian Surchi| Debian GNU/Linux User [EMAIL PROTECTED] | http://www.debian.org www.firenze.linux.it/~csurchi | Linux, the choice of a GNU generation The most important early product on the way to developing a good product is an imperfect version.
Orphaning Packages
Well, I don't like to admit it, but school's gotten too busy for me to take care of a lot of the packages I have, so I'm setting them free to find good homes with other maintainers... here's a list of the packages I intend to orphan: libxml-parser-perl libxml-dom-perl libxml-cgi-perl /* Does this exist anymore on CPAN? I haven't found * it since I originally packaged it. */ libxml-writer-perl zenirc I'll keep tik for myself, especially since it looks like it may be a while before another version comes out upstream, anyway, and I'd like to fix a bug in it, anyway, before I orphan it if I do. All the above should be bug-free, or at least I haven't added any if they weren't, I don't believe :) Basically I'm just trying to free up some time so that I can work with some of the more basic needs of Debian, such as working with the boot-floppies group and volunteering for Incoming processing... and if I'm not needed, well, I guess school will expand to swallow up my free time, anyway ;) Thanks, Stevie -- Stevie Strickland| 325912 Georgia Tech Station [EMAIL PROTECTED] | Georgia Institute of Technology http://kelewan.dhis.org/~sstrickl| Atlanta, GA 30332 Official Debian GNU/Linux Developer | Cyberlink/#Debian on IRC pgpRvi85AfHdW.pgp Description: PGP signature
Re: Move proftpd to contrib
On Sat, Sep 18, 1999 at 10:51:33PM +0200, Marco d'Itri wrote: > On Sep 18, Josip Rodin <[EMAIL PROTECTED]> wrote: > >An alternative is wu-ftpd. It would be rather foolish to support wu-ftpd > >100%, however, it has almost the same status as sendmail - it is a very > You mean that it's like sendmail, i.e. security bugs pops out every time > somebody looks at the code? Not quite. -- enJoy -*/\*- don't even try to pronounce my first name
Re: A few changes
Darren Benham <[EMAIL PROTECTED]> wrote: > In the new software, the X-Debian-CC was changed to X-Debbugs-CC (more > general) and it appears to be working. With an alias so that X-Debian-CC still works? > Some of the perl scripts have been made -w clean. and `use strict;' clean? > Bugs are no longer deleted!!! We don't have a way for you to access them > directly but there's an "official" location in the database where they're > being archived. We're trying to decide how to serve them up... by > requesting a bug number, obviously, but any other way? Do we need them > index by maintainer or package? Remember, these are closed -- solved -- > bugs. Add them to the end of the package pages in the resolved section. > All @bugs.debian.org will accept PGP/GPG clearsigned and most forms of mime > formated email. Most? Let me put it this way, I havn't found one that it > barfs on but I'm sure there's some evil MUA that will prove it's not > perfect. Does anything special happen if the a message is signed? -- I consume, therefore I am pgpa04UPHY4Lg.pgp Description: PGP signature
Re: Guessing the date style from the timezone for postgresql postinst
On Sun, Sep 19, 1999 at 12:31:27AM +0200, Josip Rodin wrote: > On Sat, Sep 18, 1999 at 06:36:47PM +0200, Robert Vollmert wrote: > > With /bin/sh -> /bin/ash, I get the following error: > > > > guess.datestyle: 25: Syntax error: word unexpected (expecting ")") > > > > It works fine with bash. It seems the opening brace on > > > > case "$x" in ( SystemV | posix | right ) > > ^ > > is causing this. > > Wasn't this fixed in potato ash? I seem to remember seeing a bug report > about this once... You're right. It was fixed in 0.3.5-4, while I was still running 0.3.5-3. It works as is, now. -- Robert Vollmert [EMAIL PROTECTED]
Re: A few changes
On Sun, Sep 19, 1999 at 02:27:20PM +0100, Edward Betts wrote: > With an alias so that X-Debian-CC still works? Not guarenteed... It's not in the "upstream" package so I'd have to remeber to put it in every time I upgrade.. > > Some of the perl scripts have been made -w clean. > > and `use strict;' clean? I figured somebody would ask :) That comes next. Lots of global variable and from what I understand, thats one of the things that'll kill the scripts. > > Bugs are no longer deleted!!! We don't have a way for you to access them > > directly but there's an "official" location in the database where they're > > being archived. We're trying to decide how to serve them up... by > > requesting a bug number, obviously, but any other way? Do we need them > > index by maintainer or package? Remember, these are closed -- solved -- > > bugs. > > Add them to the end of the package pages in the resolved section. I'd rather not. Otherwise there's no reason to have the bugs expire at all and the size of the web mirror would grow.. and grow.. and grow and never shrink. Instead, they'll be a seperate page where you can enter a bug number and...? a package name (I had about decided that, too) and the page would be served up. > > > All @bugs.debian.org will accept PGP/GPG clearsigned and most forms of mime > > formated email. Most? Let me put it this way, I havn't found one that it > > barfs on but I'm sure there's some evil MUA that will prove it's not > > perfect. > > Does anything special happen if the a message is signed? Other than it gets processed? Nope... > > -- > I consume, therefore I am pgpnj9umubrxe.pgp Description: PGP signature
Re: /opt/ again (was Re: FreeBSD-like approach for Debian? [was: ...])
"In article <[EMAIL PROTECTED]> you wrote:" > > You're also almost as good as stating that one cannot > backup /etc, toss in a spare drive, do the install off a local > NFS/FTP mount (less than 2 hours by a long shot) throw /etc > back in (no need for a tape even, whatta concept!) and then get > the rest of the data from there in under 2 hours. I'm digging through my newsspool & dejanews for an answer to this and can't find it. If the docs mention it I can't find it. Can you help? You mention a local NFS mount for installing. I'm doing some practice installs from scratch as practice for a local (Vancouver) installfest next weekend and the install procedure mentions NFS as an option for installing the base system. Is it possible to NFS mount ftp.debian.org for this? Or is the option only there for mounting local file systems? If it's possible to remotely mount, could you tell the incantation? I must have tried pretty much every one except the right one. Thanks. Rick -- [EMAIL PROTECTED] [EMAIL PROTECTED] http://vcn.bc.ca/~rick
Re: A few changes
Darren Benham <[EMAIL PROTECTED]> wrote: > > > All @bugs.debian.org will accept PGP/GPG clearsigned and most forms of > > > mime > > > formated email. Most? Let me put it this way, I havn't found one that it > > > barfs on but I'm sure there's some evil MUA that will prove it's not > > > perfect. > > > > Does anything special happen if the a message is signed? > Other than it gets processed? Nope... Oh, do you mean that it will work with [EMAIL PROTECTED] If so then I understand what you are saying, if not then I don't. -- I consume, therefore I am
Re: A few changes
On Sun, Sep 19, 1999 at 07:18:54PM +0100, Edward Betts wrote: > Darren Benham <[EMAIL PROTECTED]> wrote: > > > > All @bugs.debian.org will accept PGP/GPG clearsigned and most forms of > > > > mime > > > > formated email. Most? Let me put it this way, I havn't found one that > > > > it > > > > barfs on but I'm sure there's some evil MUA that will prove it's not > > > > perfect. > > > > > > Does anything special happen if the a message is signed? > > Other than it gets processed? Nope... > > Oh, do you mean that it will work with [EMAIL PROTECTED] If so then I > understand what you are saying, if not then I don't. Yes, it will work with [EMAIL PROTECTED] I've been signing all my mails I've been testing with yesterday :) -- Please cc all mailing list replies to me, also. = * http://benham.net/index.html<[EMAIL PROTECTED]> <>< * * * ---* * Debian Developer, Debian Project Secretary, Debian Webmaster * * <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> * * <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> * = pgpuX9mm4rgcg.pgp Description: PGP signature
Re: ProFTPd being lame
* "Raul" == Raul Miller <[EMAIL PROTECTED]> wrote: Raul> On Sat, Sep 18, 1999 at 04:21:34PM -0700, Robert Stone wrote: >> Virtualhosting in proftpd is far easier than with wu-ftpd. As it >> stands now, I don't believe any debian ftp server supports virtual >> anon ftp sites as provided besides proftpd. Raul> roxen does. I use Roxen exclusively as a httpd where I have a say on the matter, but it is mainly a httpd, and lacks configuration features (like chrooting some selected users into different roots) I use with proftpd, although I have a *very* small host, no virtual hosting etc. Go, Roxen, go as a httpd, but for ftpd, I prefer proftpd. Ciao, Martin
Re: Announcing debconf, configuration management for debian
On Sun, Sep 19, 1999 at 12:20:39PM +0200, Martin Schulze wrote: > Branden Robinson wrote: > > Thanks again, Joey. I look forward to migrating XFree86 to debconf (won't > > happen for -1, but I'm hoping to tackle FHS-compliance and this for -2). > > Err, can you please wait for this until a) debconf has been accepted and > b) there will be proper support for it and c) proper documentation. Hmm, okay. It's not like I have anything else I need to do with the X packages, anyway. You know, no bugs to fix, stuff like that. -- G. Branden Robinson |Kissing girls is a goodness. It is a Debian GNU/Linux |growing closer. It beats the hell out [EMAIL PROTECTED] |of card games. cartoon.ecn.purdue.edu/~branden/ |-- Robert Heinlein pgpbjExs6QBSi.pgp Description: PGP signature
Re: Announcing debconf, configuration management for debian
On Sun, Sep 19, 1999 at 01:16:23PM -0400, Branden Robinson wrote: > On Sun, Sep 19, 1999 at 12:20:39PM +0200, Martin Schulze wrote: > > Branden Robinson wrote: > > > Thanks again, Joey. I look forward to migrating XFree86 to debconf (won't > > > happen for -1, but I'm hoping to tackle FHS-compliance and this for -2). > > > > Err, can you please wait for this until a) debconf has been accepted and > > b) there will be proper support for it and c) proper documentation. > > Hmm, okay. It should be at least in the Debian ftp archive, I think :) > It's not like I have anything else I need to do with the X packages, > anyway. > > You know, no bugs to fix, stuff like that. Oh. If you are bored, finish the Hurd port of X. *grin* Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org Check Key server Marcus Brinkmann GNUhttp://www.gnu.orgfor public PGP Key [EMAIL PROTECTED]PGP Key ID 36E7CD09 http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/
Re: Orphaning Packages
Stevie Strickland <[EMAIL PROTECTED]> writes: > libxml-parser-perl > libxml-dom-perl > libxml-cgi-perl /* Does this exist anymore on CPAN? I haven't found > * it since I originally packaged it. >*/ > libxml-writer-perl I can take these. Mike.
apt-get dist-upgrade trouble...
> well i have an dell latitude cpi. i install slink r1 with no problem. (i stop install with selected package and i do not use dselect). i down load a apt-get update and i change source list to deb http://http.us.debian.org/debian potato main contrib non-free i use a proxy. i change apt.conf. apt-get update apt-get dist-upgrade. 49 package upgraded 7 newly installed 2 not upgraded. process and when bsdutils : dpkg (subproces) unable to execute new pre-installation script ; No such file or directory. error: were processing /var/cache/apt/archives/diff_2.7-19. "" "" "" debianutils_1.13_i386 bst regards. frederic.
Re: ProFTPd being lame
On Sun, Sep 19, 1999 at 06:49:55PM +0200, Martin Bialasinski wrote: > I use Roxen exclusively as a httpd where I have a say on the matter, > but it is mainly a httpd, and lacks configuration features (like > chrooting some selected users into different roots) I use with > proftpd, although I have a *very* small host, no virtual hosting etc. It's true that roxen's design prevents chrooting ftp if you are running a non chrooted web server on the same system. However, it's silly to be running a non-chrooted web server if you want a chrooted ftp server. And, with a little work, roxen could support running chrooted. [And it would be reasonable to lose the ability to reconfigure it at run time from the administrative web interface -- that's probably good from a security standpoint. The other option, putting the config file in the chrooted area, is also viable but would be less secure.] -- Raul
Re: Orphaning Packages
Hi, I'm willing to take-over the libxml* packages. Thanks, Ardo Stevie Strickland <[EMAIL PROTECTED]> writes: > Well, I don't like to admit it, but school's gotten too busy for me > to take care of a lot of the packages I have, so I'm setting them > free to find good homes with other maintainers... here's a list of > the packages I intend to orphan: > > libxml-parser-perl > libxml-dom-perl > libxml-cgi-perl /* Does this exist anymore on CPAN? I haven't found > * it since I originally packaged it. >*/ > libxml-writer-perl > zenirc [snip] -- Ardo van Rangelrooij home email: [EMAIL PROTECTED], [EMAIL PROTECTED] home page: http://www.tip.nl/users/ardo.van.rangelrooij PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9
Re: Too many kernels in unstable
On Fri, 17 Sep 1999, Edward Betts wrote: > My suggestion would be: > > kernel-{doc,headers,image,source}-2.0.38 > kernel-{doc,headers,image,source}-2.2.12 > > Can anybody provide arguements against just having two kernels? Maybe I don't see all the problems, but why don't we name the packages kernel-{doc,headers,image,source}-2.0 2.0.38- kernel-{doc,headers,image,source}-2.2 2.2.12- which would reduce the effort of the ftp maintainer and speed up upgrading our ftp archive from 2.2.12 to 2.2.13. The dependencies between the kernels and the kernel depending modules could be realized using versioned dependencies, couldn't they? Maybe we should add an unstable kernel to the stable versions above: kernel-{doc,headers,image,source}-2.3 2.3.18- Ciao Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ * PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF
Re: Announcing debconf, configuration management for debian
[ announce for debconf skipped ] Is i18n going to be supported by debconf? If yes, how? Thanks, -- Mike (who thinks i18n should be considered from the very beginning)
Re: boot-floppies status from an insider (was Re: Deficiencies in Debian)
Adam Di Carlo wrote: > Here's my unofficial boot-floppies TODO: > > * build for all supported arches > > * eliminate all dselect acquisition methods aside from apt and > possibly mountable (for NFS, which apt doesn't handle -- socks > also not handled by apt but I don't know if we care) > > * GUI for apt's sources.list configuration > > * GUI for tasks/profiles (see above) > > * better lilo configuration (borrow from slackware perhaps?) > > * close bugs! > > * nifty stuff like TFTP and and serial console installation should be > supported on all possible architectures > (TFTP images may require some software in Debian which is not currently > available) Do we still want to support very old hardware, especially low memory system (eg. some old sparc, and maybe old 386, 486 as well) ? In this case, we need to add a "swap on NFS" patch to the kernel. I found one patch for 2.0.35 (sparc) kernel. And for 2.2, NBD could be used along with a patch to the networking subsystem (http://atrey.karlin.mff.cuni.cz/~pavel/nbd/nbd.html). I will try to build bootdisks for sparc based on them. > * update documentation (too early to do this) -- Eric Delaunay | "La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant." Henri Jeanson (1900-1970)
Re: Announcing debconf, configuration management for debian
On 17-Sep-99, 13:23 (CDT), Joey Hess <[EMAIL PROTECTED]> wrote: > This is a bit long, so I'll summarize: > > Debconf is a tool that packages can use to ask questions when they are > installed. It allows various frontends, from dialog, to gtk to web pages > to be used, and it also allows for non-interactive package installs, and > allows packages to ask questions all at once, before any of them are even > installed. Nice job, Joey. I've read (or at least skimmed) the tutorial you posted, and it looks like the various configuration variables are associated with a package via the template "foo/variable". What about variables that are logically shared between packages, such as the default directory for the webservers, or news server name, and such. Is it acceptable for the group of affected maintainers to use the virtual package name as the variable package name? Or would some other way be better? -- Steve Greenland <[EMAIL PROTECTED]> (Please do not CC me on mail sent to this list; I subscribe to and read every list I post to.)
Re: Announcing debconf, configuration management for debian
Michael Sobolev wrote: > Is i18n going to be supported by debconf? If yes, how? Well Wichert and I have talked about this. One nice thing about debconf is it separates out nearly all translatable text from the postinst and configure script into it's template file. So it merely becomes a question of adding translations to that file. The file is formatted similarly to a package's control file, and should be extensible enough so we can embed translated text in it in a variety of ways (what works good for a control file?) -- see shy jo
Re: Announcing debconf, configuration management for debian
Steve Greenland wrote: > I've read (or at least skimmed) the tutorial you posted, and it > looks like the various configuration variables are associated with a > package via the template "foo/variable". What about variables that are > logically shared between packages, such as the default directory for > the webservers, or news server name, and such. Is it acceptable for the > group of affected maintainers to use the virtual package name as the > variable package name? Or would some other way be better? I think we'll eventually let the policy group deal with this. For now there really arn't any rules, just common sense. Yes, I think it's acceptable to use virtual package names. The two packages I have now that share a variable name and slrn and slrnpull, they use news/server, which isn't exactly mapped to a virtual package name, since slrn and slrnpull don't share a virtual package name. -- see shy jo
Re: Announcing debconf, configuration management for debian
> Well Wichert and I have talked about this. > > One nice thing about debconf is it separates out nearly all translatable > text from the postinst and configure script into it's template file. So it > merely becomes a question of adding translations to that file. The file is > formatted similarly to a package's control file, and should be extensible > enough so we can embed translated text in it in a variety of ways (what > works good for a control file?) I don't know about debconf, but it would be great if you can integrate it with gettext... You would just need to set the "textdomain" and call gettext (included in libc6) for each message.
Re: demo vs. real package: FYI (was Re: Announcing debconf, configuration management for debian)
On Fri, Sep 17, 1999 at 02:45:32PM -0400, Raul Miller wrote: > FYI, sash_3.3-5 (which has been sitting in Incoming for the last couple > weeks) no longer prompts at postinst time, as the postinst/prerm scripts > have been completely redesigned. do they automatically set up sash as root's shell? craig -- craig sanders
ITP: ndtpd
I intent to package ndtpd. From README: NDTPD is a server for accessing CD-ROM books with NDTP (Network Dictionary Transfer Protocol) on TCP. You can replace dserver with NDTPD. NDTPD can run on UNIX derived systems. It supports to access CD-ROM books of EB, EBG, EBXA, EBXA-C and EPWING formats. CD-ROM books of those formats are popular in Japan. Since CD-ROM books themseves are stands on the ISO 9660 format, you can mount the discs by the same way as other ISO 9660 discs. License: GNU GPL2 -- Susumu OSAWA
Re: Orphaning Packages
Am Son, 19. Sep, 1999 schrieb Ardo van Rangelrooij: > Hi, > > I'm willing to take-over the libxml* packages. They're yours :) Thanks, Stevie -- Stevie Strickland| 325912 Georgia Tech Station [EMAIL PROTECTED] | Georgia Institute of Technology http://kelewan.dhis.org/~sstrickl| Atlanta, GA 30332 Official Debian GNU/Linux Developer | Cyberlink/#Debian on IRC Member of the X Strike Force | PGP/GPG ID = 23A6D909/AE7637D9 PGP Key fingerprint = 84 52 C7 EA E6 DB A1 C5 6A C9 D6 B9 88 26 74 FC GPG Key fingerprint = 3062 4329 AA5C 6095 DB71 AF9A 2A5E C7DE AE76 37D9 pgpSgs3tB7BCf.pgp Description: PGP signature
sash (was Re: demo vs. real package: FYI (was ...))
On Fri, Sep 17, 1999 at 02:45:32PM -0400, Raul Miller wrote: > > FYI, sash_3.3-5 (which has been sitting in Incoming for the > > last couple weeks) no longer prompts at postinst time, as the > > postinst/prerm scripts have been completely redesigned. On Mon, Sep 20, 1999 at 07:18:09AM +1000, Craig Sanders wrote: > do they automatically set up sash as root's shell? They don't touch the root account. Instead, they clone it as sashroot and set the shell on the cloned account. This is mentioned in the package description. -- Raul
Re: sash (was Re: demo vs. real package: FYI (was ...))
On Sun, Sep 19, 1999 at 06:30:37PM -0400, Raul Miller wrote: > On Fri, Sep 17, 1999 at 02:45:32PM -0400, Raul Miller wrote: > > > FYI, sash_3.3-5 (which has been sitting in Incoming for the > > > last couple weeks) no longer prompts at postinst time, as the > > > postinst/prerm scripts have been completely redesigned. > > On Mon, Sep 20, 1999 at 07:18:09AM +1000, Craig Sanders wrote: > > do they automatically set up sash as root's shell? > > They don't touch the root account. Instead, they clone it as sashroot > and set the shell on the cloned account. cool. i was just checking that the discussion from two weeks ago on how/what to do hadn't been forgotten. > This is mentioned in the package description. even better :) craig -- craig sanders
Re: sash (was Re: demo vs. real package: FYI (was ...))
Raul Miller wrote: > They don't touch the root account. Instead, they clone > it as sashroot and set the shell on the cloned account. > > This is mentioned in the package description. I suppose you have considered the security problems, if root forgets to change that password when they change the main root one? -- see shy jo
New gnome-libs stuff up for testing...
I believe I have a gotten a good build of an updated gnome-libs. And I only cursed Joey for the problems with dh_shlibdeps a little bit. It is currently a little lacking in the changelog department---that kind of got over-looked in the overhaul---but otherwise I think it's ready to go. One thing to note is that there is a new package, gnome-faq (I don't think it fit well in gnome-libs-data), and upstream gnome-hello has been moved into its own package, so it no longer appears here. Someone should package the new upstream version. I would appreciate people examining it and using it. I would also be nice if maintainers of gnome binaries and/or non-i386 architecture porters could compile with it. It's at http://master.debian.org/~mdorman/gnome-libs-1.0.16/. I'm uploading it now, and my DSL line doesn't give me infinite bandwidth, so you might wait five or ten minutes. Please email me any issues directly at [EMAIL PROTECTED] Mike.
Re: A few changes
On Sat, 18 Sep 1999, Michael Stone wrote: > Definately by package. I can think of several circumstances where this > is useful: when a bug is closed in unstable but someone using stable > wants an explanation for a problem; when a bug is inadvertantly > reintroduced; when a maintainer closes a bug caused by user error, and > [...] Agreed. It would be nice to have a mail server command `resurrect', or similar, that would bring a dead bug back to life (if it were found not to be dead, or whatever; several reasons were listed above). This would also be some way to producing some kind of automated list of bugs fixed in each release of Debian; people could visit a list somewhere showing them precisely which bugs in which packages had been fixed between their version of Debian and unstable. -- Chris <[EMAIL PROTECTED]> ( http://www.fluff.org/chris )
Re: FreeBSD-like approach for Debian? [was: Re: Deficiencies in Debian]
On Wed, Sep 15, 1999 at 07:51:47AM +0200, Anders Arnholm wrote: > You mean having to dive into almost every perl script (not Linux > developed) and change #!/usr/local/bin/perl to #!/usr/bin/perl It is unfortunate, but the popular usage (ie, #!/usr/local/bin/perl) is wrong. /usr/bin/perl has always been the cannonical location of perl. The perl Configure script will default to creating a link from wherever you install the binary to /usr/bin. The first edition of the Camel book even recommended doing unpleasant things to the local system administrator if /usr/bin/perl didn't exist; unfortunately this is not in the second edition, for what reason I do not know. I suggest kindly pointing this out to those who start their scripts with #!/usr/local/bin/perl. Andrew
Re: Orphaning Packages
Am Son, 19. Sep, 1999 schrieb Michael Alan Dorman: > Stevie Strickland <[EMAIL PROTECTED]> writes: > > libxml-parser-perl > > libxml-dom-perl > > libxml-cgi-perl /* Does this exist anymore on CPAN? I haven't found > > * it since I originally packaged it. > > */ > > libxml-writer-perl > > I can take these. I already handed them off to Ardo... you technically asked first, but my checkmail script only checks messages from my Inbox and a few other select folders, so I didn't see yours until now... sorry :( Thanks, Stevie -- Perl's garbage collector abhors a naked circularity. -- the Perl Cookbook pgpodbUS8Jr3p.pgp Description: PGP signature