Re: Where to find cdda_inteface.h and cdda_paranoia.h in ?
On Mon, Jan 01, 2001 at 11:59:19PM +0100, Josip Rodin wrote: MM Of course a quick search in there revealed nothing poping up for cdda. Very strange. I've find that in unstable : usr/include/cdda_interface.hsound/libcdparanoia0-dev usr/include/cdda_paranoia.h sound/libcdparanoia0-dev Ah. The mirror (the Contents-* files in it) on the machine where that CGI runs is outdated. Known issue. Actually, wait, wrong. Investigating... Well, I've checked and re-checked and everything seems fine. Entered both of those files in the search form and the script returned those results. Too much alcohol, Michael? :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: DEBIAN IS LOOSING PACKAGES AND NOBODY CARES!!!
On Sun, Dec 31, 2000 at 01:06:18PM +0100, [EMAIL PROTECTED] wrote: I am very sorry for the loud subject of my mail (I know it is bad netiquette), but since I got no satisfying answer on my first mail concerning disappeared packages and because the issue is important I decided to try it again with shouting ;-). One deserves a plonk for doing that :p Fancylogin is reported to be in unstable and there also is a package page, but the package is not found from the download page and is also not present in any of the mirrors. This is an often-seen problem with packages.d.o web pages: even when packages are removed from the archive, their HTMLs stay, until manual deletion. We oughta cook up a script to handle that, but nobody has bothered yet... However, we have a different problem right now: mirror on master.d.o is not getting updated regularly due to lack of disk space on that particular partition, and the packages.d.o web pages scripts generate the HTMLs according to that mirror. So some links are outdated and will get more and more outdated if this is not fixed. Admins have been informed already, but this is hardly a season when everyone's alert and ready to fix stuff instantly. :/ And then there's the Cabal issue, of course. ;) TINC. :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: DEBIAN IS LOOSING PACKAGES AND NOBODY CARES!!!
On Sun, Dec 31, 2000 at 03:40:41PM +0100, Peter Palfrader wrote: Again there is a pointer from packages.debian.org, but the deb is not in the directory pointed to. Seems like packages.debian.org is broken then. If it's not reportet yet, maybe someone should do. It is! Several times! -- Digital Electronic Being Intended for Assassination and Nullification
Re: xfs segfaults with truetype fonts
On Fri, Dec 29, 2000 at 07:14:24AM +0100, Martin Maciaszek wrote: I want to use xfs from X4 with truetype fonts. I created a fonts.dir file with ttmkfdir and added the path with the fonts to /etc/X11/fs/config. I restarted xfs and X. Everytime I try to use one of the ttfs xfs dumps core. What can I do? xfstt+X3 works for me :o) SCNR. -- Digital Electronic Being Intended for Assassination and Nullification
Re: ITA gtk-doc-tools
On Fri, Dec 29, 2000 at 02:10:23PM +0100, Christian Marillat wrote: I intent to adopt this package. This package isn't orphaned, but Steve Haslam is MIA since more one year. I'll upload a new release before the new millennium. He actually isn't all that dead, he managed to orphan a couple of his packages recently. (I took maildrop.) Although, he doesn't seem to reply to mails... :/ -- Digital Electronic Being Intended for Assassination and Nullification
Re: test -d /usr/man mail submit@bugs
On Fri, Dec 29, 2000 at 10:46:10AM +0100, Adrian Bunk wrote: for package in dpkg apt libc gpg bplay etc ; do sed [...] bug.template | mail ; done You'd better use [EMAIL PROTECTED], else you need a very good asbestos suit ... Too late. }:) ... Grrr... He filed them: - without subject He fixed that. - with severity serious These are at most normal bugs in packages with a Standards-Version 3.0.0 Actually, that can be discussed -- do we want such packages in a stable release? :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: ITA gtk-doc-tools
On Fri, Dec 29, 2000 at 03:25:04PM +0100, Christian Marillat wrote: I intent to adopt this package. This package isn't orphaned, but Steve Haslam is MIA since more one year. I'll upload a new release before the new millennium. JR He actually isn't all that dead, he managed to orphan a couple of his JR packages recently. (I took maildrop.) Although, he doesn't seem to reply JR to mails... :/ The last time I've sent an e-amil to him, this was in September 1999 for Gnome packages without reply. We need to wait ? If yes how-many time ? Hmmm. That's not an easy question. Send him another mail, and upload a fixed package. Then wait for response :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: test -d /usr/man mail submit@bugs
On Sat, Dec 30, 2000 at 02:00:29AM +1100, Hamish Moffatt wrote: I thought of sendmail(1) where you feed the headers with the mail. and thats why I didn't send explicit to maintonly. Every mass bag submit should be maintonly no matter how you do it technically. What's the difference? I read the web page about submitting bugs and it seems that maintonly just doesn't send them to debian-bugs-dist. Exactly. How many emails are we talking about? Isn't debian-bugs-dist already full of hundreds of emails not relevant to most people? There's a slight difference between various bug report discussions and loads of spam :P -- Digital Electronic Being Intended for Assassination and Nullification
Re: test -d /usr/man mail submit@bugs
On Thu, Dec 28, 2000 at 09:56:37PM +0100, Arthur Korn wrote: for package in dpkg apt libc gpg bplay etc ; do sed [...] bug.template | mail ; done You'd better use [EMAIL PROTECTED], else you need a very good asbestos suit ... Too late. }:) BTW your Mail-Followup-To is broken. -- Digital Electronic Being Intended for Assassination and Nullification
Re: Boost Windows Reliability!!!!!
On Tue, Dec 26, 2000 at 12:05:00PM +0200, Kai Henningsen wrote: Did you ever wonder (assuming you even noticed) why so much spam gets sent to completely invalid addresss (for example, to message ids)? Because spamware sellers don't care if the finely targetted addresses they sell actually work (let alone are targetted in any way). On related note, it's fun to watch all the spams sent to oldclosedbug@bugs.debian.org or even oldclosedbug[EMAIL PROTECTED] addresses. OTOH it's not fun to discover that someone spammed existingbug[EMAIL PROTECTED] (those escape me since I'm not watching the appropriate mailing list). For the record, right now I'm the primary reason why the spam in the BTS `magically' disappears, once it's reported to [EMAIL PROTECTED] :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: perl 5.00{5,4} dependancies
On Tue, Dec 26, 2000 at 12:24:34AM -0800, Joey Hess wrote:
I'm planning a mass automated -quiet bug reporting spree against almost
all packages that depend on perl 5.00{5,4}[-base]. All such packages
should be updated to depend on perl-5.6 (possibly with 5.005 as an
alternate).
ITYM -maintonly.
--
Digital Electronic Being Intended for Assassination and Nullification
Re: List of packages that could be dropped
On Tue, Dec 26, 2000 at 03:22:21PM +0100, Christian Kurz wrote: |ppd-gs (1 year and 357 days old) Do we really need this package still for users of alladin ghostscript or is it not needed anymore? Last time I asked for this to be removed, a few people said this was useful. FWIW. |silo (195 days old) Has this package been removed from unstable and if yes, why? It's currently still listed in the wnpp but I could find it which apt-cache search silo. That's because it's SPARC-specific LILO variant, IIRC. |libmikmod (214 days old) Is any architecture still using libmikmod1 or could we drop this part of the libmikmod package? I think we should keep the newer sources for libmikmod, it's useful for one of XMMS plugins :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: BTS spam( Re: Boost Windows Reliability!!!!!)
On Wed, Dec 27, 2000 at 03:30:47AM +0900, Junichi Uekawa wrote: For the record, right now I'm the primary reason why the spam in the BTS `magically' disappears, once it's reported to [EMAIL PROTECTED] :) I've seen one in lyx-cjk bugs. It's cosmetically annoying. I really would love to remove it but there would be quite a lot of trouble (and fear that legitimate info could be lost). Tell me the bug number and I'll clean it out. -- Digital Electronic Being Intended for Assassination and Nullification
Re: Close list
On Sun, Dec 24, 2000 at 10:18:55AM +0900, Miles Bader wrote: flame war Now maybe if we were using the RBL, DUL, and RSS lists... :-) /flame war GNU mailing lists (supposedly) use RBL, but in a mode where `spam' isn't deleted, but rather just gets a header added saying `this message is considered suspicious'. That allows individual recipients to do as they see fit. That seems like it would be useful, and I fail to see how anyone could object to it... It has been said in a related thread on a mailing list that shall not be named :) that making a DNS lookup for hosts carrying the blacklists on each delivery would slow it down. It has also been said that this isn't hard to work around, though. FWIW I like the X-RBL-Warning headers. -- Digital Electronic Being Intended for Assassination and Nullification
Re: Close list
On Sun, Dec 24, 2000 at 09:13:36PM +, Mark Brown wrote: Spam to the Debian mailing lists tends to be especially annoying since the spammers always seem to hit each and every mailing list (or at least, a large number of them), which makes each spam much more noticable. Oh yeah. If only there was some way of automatic killing of such spams, sent to more than X (say, 5) mailing lists... something that would remember the last X-1 mails from the same domain name (or whatever) and kill off the remaining attempts. -- Digital Electronic Being Intended for Assassination and Nullification
Re: wnpp bug reports
On Fri, Dec 22, 2000 at 12:58:54PM -0500, Bob Hilliard wrote: Is there any way to submit an ITP bug on WNPP, so that the bug number appears in the copy to -devel? Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields. -- Digital Electronic Being Intended for Assassination and Nullification
request for archives of this list for September 2000
Hi people, Sorry for the most obnoxious crosspost. If anyone has a complete archive (mbox format) of any of the following Debian mailing lists for September 2000, please contact me immediately: debian-68k debian-admintool debian-alpha debian-arm debian-beowulf debian-boot debian-cd debian-changes debian-chinese-big5 debian-chinese-gb debian-curiosa debian-devel debian-devel-announce debian-devel-changes debian-doc debian-dpkg debian-emacsen debian-events-eu debian-firewall debian-french debian-glibc debian-hams debian-hppa debian-hurd Problem is that main archives aren't functioning[1] and web archives for these september of these lists are incomplete. [1] master:~debian/.forward-list-archive needs lists/procmailrc, but there's no such file. -- Digital Electronic Being Intended for Assassination and Nullification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE2 - nice demolition job ...
On Wed, Sep 13, 2000 at 12:23:12AM -0500, David Starner wrote: I just can't keep my mouth shut about this any longer and the unnecassary divisions (read demolitions) of KDE packages are the last straw BTW, what would it take for someone to be forced to break up a package or make some other major change? The only thing I can think of that could do it is a amendment to policy or something more drastic. Even that would be a postponed forcing, as a not-broken-up package could still exist, declaring an older Standards-Version. :) -- Digital Electronic Being Intended for Assassination and Nullification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE2 - nice demolition job ...
On Mon, Sep 11, 2000 at 04:39:33PM -0700, erik wrote: I realize I stirred up a hornets nest; I did it intentionally because otherwise nobody seems to notice and I think that at least some of what I originally wrote (goading aside) is important. Personally, I would like a normal post better. I read 4-5 lines of your initial post, after which I instantly decided it's a flamebait and moved on to the next message. a. Assign more people to process applications - kind of self-explanatory. This is Debian, so s/Assign more people/Get more volunteers/. b. Establish at least two teirs of contribution - people who are interested in helping with less technical aspects need not be subjected to the same screening process as package maintainers. So if, for example somebody says hey, could I help with paperwork or the website or something ? they can be easily accepted to work on something. Voluteering should not be a full time job. We have quite a few translators who aren't developers but do have CVS access to the web site repository, actually. All it takes is to mail the appropriate person (debian-www or the translation coordinator). Don't know about debian-doc, it's probably more or less the same (mail the list or the doc coordinator). c. (optimally) Rewrite the pages that explain how to apply and give a clearer and more complete description of tasks available and what level of expertise each requires. You'd have to talk to Taketoshi Sano about his English :o) d. (optimally) simplify the protocols for applying. It seems to me that it shouldn't get more simple that what it is now, otherwise we'd have too many people who became developers far too quickly and easily to be able to contribute quality stuff fast enough. Just IMHO. BTW you should put your real name in From:. -- Digital Electronic Being Intended for Assassination and Nullification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Mozilla PSM (https support)
On Wed, Sep 13, 2000 at 01:15:17PM -0500, Joseph Carter wrote: - Can the PSM go in Main? - If Not in main, how do I build this so that mozilla(noncrypto parts) goes in main, while mozilla-psm goes to non-us/main with minimum amount of manual work? (when answering this, keep the autobuilders in mind) Note that Netscape 4.75 is in main. No, it's in non-free/contrib. :) -- slashdot my US geograpy is lousy...lol knghtbrd so's mine and I live here This is lame. : -- Digital Electronic Being Intended for Assassination and Nullification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: BTS not showing my bugs
On Thu, Aug 31, 2000 at 01:44:29PM +0100, Mark Brown wrote: All statically updated BTS pages are broken, please see DWN for details. Might it be an idea to put a notice about this on the web page? It'd avoid a lot of confusion. Done. (at last :) -- Digital Electronic Being Intended for Assassination and Nullification -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug reports by maintainer
On Tue, Aug 29, 2000 at 07:58:14PM -0300, Nicolás Lichtmaier wrote: I believe the goal is to remove the static pages completely. Only a few more scripts need to be written. And how would that be a good goal? People can mirror static pages, caches can cache them... We don't have a good, fast system that is able to regenerate the static pages in a timely manner. -- Digital Electronic Being Intended for Assassination and Nullification
Re: Installed console-apt 0.7.7.2potato1 (source i386)
On Wed, Aug 30, 2000 at 09:34:54PM +0200, Christian Surchi wrote: Installed: console-apt_0.7.7.2potato1_i386.deb to dists/proposed-updates/console-apt_0.7.7.2potato1_i386.deb What does it mean? console-apt is not in potato and is it put again in stable? It means that it may enter 2.2r1... a wish come true :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: qmail
On Mon, Aug 21, 2000 at 01:28:40PM -0500, Chris Lawrence wrote: Debian officially recommends something? That's news to me. I believe we ship exim as the standard MTA (we changed from smail in hamm or slink); I don't know if that makes it recommended or not. It makes it recommended for new users, that's all, IIRC. -- Digital Electronic Being Intended for Assassination and Nullification
Re: [PROPOSED 2000/08/16] Free pkgs depending on non-US should go into non-US/{main,contrib}
On Wed, Aug 16, 2000 at 08:04:00PM +1000, Anthony Towns wrote: A dependency on non-us will also land a package in contrib. I think there was a proposal to change that, so that packages which depend on packages in non-US/main remain in non-US/main. Actually, there doesn't seem to be such a proposal; there just seems to be your (accepted) proposal to make both main and non-US/main part of the Debian distribution. So, let's fix that. The principle: packages that are DFSG-free, depend on packages in non-US/main, but are otherwise candidates for main should go into non-US/main also. That way they're still a part of the official distribution, but they don't come up as uninstallables for the poor deprived US folks. Here's a sample wording change. It incorporates the accepted change from #62946. It's not entirely clear where contrib packages that don't include crypto, but Depend: on software that does (from non-US/*) would go in the following, probably. Seconded! -- Digital Electronic Being Intended for Assassination and Nullification
Re: NMU's completely removed from kaffe in woody
On Fri, Aug 18, 2000 at 03:06:55PM -0500, Ean R . Schuessler wrote: The second reason I chose to cut a lot of NMU changelogs was that you took it upon yourself to load them with vindictive, personal and unprofessional statements. Editing changelogs is `modifying history' - do not do that. -- Digital Electronic Being Intended for Assassination and Nullification
slink - archive?
Hi, When will slink move to archive.debian.org site? -- Digital Electronic Being Intended for Assassination and Nullification
Re: xpdf-i obseleted by xpdf
On Sun, Aug 20, 2000 at 08:59:57AM -0300, Henrique M Holschuh wrote: xpdf already conflicts and replaces xpdf-i. Am I correct in saying that there's no way I can cause an automatic upgrade from xpdf-i to xpdf? Hmm... I'll take the oportunity to ask an old doubt of mine: Will it work if xpdf-i is made an empty package which depends on xpdf, and its description is changed so as to explain the user that she should purge xpdf-i ? (xpdf still conflicts with xpdf-i). It will, just make new xpdf conflict with ( version_before_merge) of xpdf-i. (But it'll still be ugly) -- Digital Electronic Being Intended for Assassination and Nullification
Re: WNPP now on the BTS
On Sat, Aug 19, 2000 at 09:10:50PM +0200, Marcelo E. Magallon wrote: Attached is the intended documentation for the WNPP system. I've formatted this text with html/wml and put it in the web pages. It should appear shortly as http://www.debian.org/devel/wnpp . I'll make a few other changes to it, to indicate the status of [EMAIL PROTECTED] address etc... suggestions welcome. The FTP copy of the old wnpp page will be removed, and the WWW copy will be updated to point at the new place. -- Digital Electronic Being Intended for Assassination and Nullification
Re: Intent To Split: netbase
On Wed, Aug 16, 2000 at 02:05:58PM -0500, Bryan Andersen wrote: When a user or administrator is using it it is because of unusual conditions. Why so? I use it in perfectly usual and common conditions. -- Digital Electronic Being Intended for Assassination and Nullification
Re: [Election Results] Official and Final
On Fri, Mar 31, 2000 at 02:43:19PM -0800, Seth R Arnold wrote: The ballots came from: 216 people, if I counted right (wc(1) :). So much for the `300 active developers' vaporware, even if you include dissidents et al... Wouldn't this be more properly FUD? :) What? -- Digital Electronic Being Intended for Assassination and Nullification
Re: New Mailing-Lists
On Sat, Apr 01, 2000 at 12:17:26AM +0200, Martin Schulze wrote: [new lists created] On related note, why not have new-maintainer lists on our listserver, too? -- Digital Electronic Being Intended for Assassination and Nullification
Re: New Mailing-Lists
On Sat, Apr 01, 2000 at 02:19:24PM +0200, Peter Palfrader wrote: [new lists created] On related note, why not have new-maintainer lists on our listserver, too? Isn't this what debian-mentors is for? No, I mean the nm-admin and nm-discuss lists, about the new-maintainer group, those who accept new maintainers... -- Digital Electronic Being Intended for Assassination and Nullification
Re: Obsolete packages
On Fri, Mar 31, 2000 at 09:41:29AM +0200, Michael Meskes wrote: intlfonts-european # apt-get install intlfonts-european Reading Package Lists... Done Building Dependency Tree... Done Package intlfonts-european has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list However the following packages replace it: xfonts-intl-european E: Package intlfonts-european has no installation candidate # There you go :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: wnpp@debian.org still alive ?
On Fri, Mar 31, 2000 at 10:08:57AM +0200, Gregor Hoffleit wrote: Is [EMAIL PROTECTED] still alive and maintained ? During the last few months, I sent several ITP's and a request to remove a package from the list to this address, but AFAICS all of them were ignored. E.g. I requested to remove dgs from the list of packages needing a new maintainer, and I sent an ITP for WorldPilot. We at WNPP (Johnie Ingram and me) don't quite maintain the PP part of WNPP anymore. We decided that it was pointless because the database used is hard to maintain, slow to generate pages, and also a bit buggy. It is planned to integrate the current WNPP list into the list on the QA site (http://qa.debian.org/wnpp.html), but we'd need Raphael or someone else to do large modifications to the pgsql database and the perl scripts for the mail bot... unfortunately it hasn't yet been done. Having said that, I must admit I don't know why wasn't the dgs package entry updated. I'll remove it right away, sorry. -- Digital Electronic Being Intended for Assassination and Nullification
Re: [Election Results] Official and Final
On Fri, Mar 31, 2000 at 07:08:07PM -, Darren Benham wrote: The ballots came from: 216 people, if I counted right (wc(1) :). So much for the `300 active developers' vaporware, even if you include dissidents et al... N: Marco D N: Rapha N: Stig Mathis These names are incorrect (perhaps others, maybe I haven't noticed), it seems your program doesn't like `'' or 8-bit characters, please fix it for the next vote. -- Digital Electronic Being Intended for Assassination and Nullification
Re: [Election Results] Official and Final
On Fri, Mar 31, 2000 at 02:06:19PM -0700, Jason Gunthorpe wrote: 216 people, if I counted right (wc(1) :). So much for the `300 active developers' vaporware, even if you include dissidents et al... It think it just clearly shows typical lack of election interest. FYI, Echelon has confirmed a total of 346 developers by PGP verification. Okay, 62.43% isn't so bad, but it doesn't really take that much effort to vote in Debian, IMHO. -- Digital Electronic Being Intended for Assassination and Nullification
Re: RBL report..
On Wed, Mar 29, 2000 at 06:56:47PM +1000, Hamish Moffatt wrote: Hell, Joseph, have you ever stopped to read one of your own posts to see what you really sound like? I agree, knghtbrd, you sound too fanatical(sp?). Calm down, and perhaps people will pay more attention to what you're saying. -- Digital Electronic Being Intended for Assassination and Nullification
Re: how about a real unstable?
On Wed, Mar 29, 2000 at 08:19:18AM +0200, Petr Cech wrote: This is what experimental is for, no? Unstable is for unstable Debian, not necessarily unstable software. The experimental distribution is much more appropriate for unstable upstream software. agreed with the addition that experimental must also be apt'able. it is. grep experimental /etc/apt/sources.list, please? -- Digital Electronic Being Intended for Assassination and Nullification
Re: how about a real unstable?
On Wed, Mar 29, 2000 at 12:08:31PM +0200, Petr Cech wrote: grep experimental /etc/apt/sources.list, please? deb http://samosa.debian.org/debian/project/experimental/ / Here's a prettier one, as discussed on IRC :) deb http://ftp.debian.org/debian/ project/experimental/ -- Digital Electronic Being Intended for Assassination and Nullification
Re: Entering in the Official Debian's distribution
On Wed, Mar 29, 2000 at 01:59:19PM +0100, [EMAIL PROTECTED] wrote: How can a programmer have the right of putting his own program on the Official Debian's Distribution ? I have heard something about the PGP key, but I haven't a clear idea. Please read the information in Debian Developer's Reference, chapter `Applying to become a maintainer', at: http://www.debian.org/doc/packaging-manuals/developers-reference/ch-new-maintainer.html -- Digital Electronic Being Intended for Assassination and Nullification
Re: Insufficient documentation for configuring a ethernet device /etc/network/interfaces
On Tue, Mar 28, 2000 at 07:41:12PM +0530, C Hanish Menon wrote: Heres the 1st draft of the man page for /etc/network/interfaces But it has already been written! Update your netbase package. -- Digital Electronic Being Intended for Assassination and Nullification
Re: Potato - update-alternatives (Ian Jackson) and window managers - doubt (and Slink to Potato Success)
On Mon, Mar 27, 2000 at 12:33:39PM +0200, Robert Bihlmeyer wrote: update-alternatives --install /usr/bin/x-window-manager \ x-window-manager /usr/local/bin/gnome-session 90 \ --slave /usr/share/man/man1/x-window-manager.1.gz \ x-window-manager.1.gz path-to-gnome-session-manpage (if there is no manpage, leave out the last two lines) ...and the backslash at the end of the second line, for those uninitiated ones who might have wondered. /nitpick :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: ITP John the ripper
On Sun, Mar 26, 2000 at 11:15:20AM -0500, Matt Zimmerman wrote: as jsut discussed on debian-devel, I would like to package John the Ripper. If someone already has done or is working on it, please mail me, then I will stop packing it. Otherwise I will try to upload this package till friday next week to woody. I briefly looked into packaging this a while ago, and I couldn't find a license in the distribution. Are you aware of a license for this program, or have you contacted the upstream author? A friend of mine asked Solar Designer, and he said it's GPL or something... -- Digital Electronic Being Intended for Assassination and Nullification
Re: Idea: Debian Developer Information Center
On Sat, Mar 25, 2000 at 09:51:50PM +0100, Raphael Hertzog wrote: Hi dear co-developers, Hey people ! I posted this mail in order to have some input ... it would be great if some of you gave their opinion about this proposition I posted a while ago : I guess the silent majority overwhelmingly agrees to your proposal ;) - information about the NMU policy that the maintainer has adopted (timeframe before a NMU is allowed, do i need an authorization to do a nmu ?, ...) This should also be implemented through a database. With this system, each developer can add his own page on one of his bookmark and from time to time he can check what he's responsible for and what he should do in one look. [snip] It would be my first bookmark... please do it :) -- Digital Electronic Being Intended for Assassination and Nullification
Re: blue on black is unreadable
On Fri, Mar 24, 2000 at 03:29:07PM +0100, Robert Bihlmeyer wrote: With the advent of powerful workstation monitors delivering 70 Hz or more, the most glaring problem of black/white became less and less important. Even on 85Hz or even higher vertical frequencies, I find black-on-white XTerms quite hard to read. When you combine that with the fact that most people aren't using 640*480 resolution anymore, but (much) higher modes, but the font size in XTerm doesn't enlarge automagically with the screen resolution (why should it, one might ask), you get something barely usable. I may be an exception since I usually wear photo-sensible glasses to prevent eye-strain (and headaches), but I can't say I've seen many other `normal' people satisfied by the default XTerm appearance. BTW, FWIW, when in X, I use 1024*768*32*85, gray-on-black XTerm, font size 20. Although I still prefer the console :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: ITP: bnc
On Wed, Mar 22, 2000 at 08:31:16PM +0100, Marco d'Itri wrote: I'm packaging the bnc IRC bouncer. IIRC that's already packaged and uploaded to Incoming. BTW your Mail-Followup-To: md, debian-devel@lists.debian.org is wrong... -- enJoy -*/\*- don't even try to pronounce my first name
Re: of bash and ...sbin/
On Wed, Mar 22, 2000 at 11:52:37AM -0500, Jacob Kuntz wrote: As policy states, things that pertain to system administration (and traceroute is for troubleshooting networks) is to be in /sbin or /usr/sbin. The difference between /sbin and /usr/sbin is that things that could be needed to rescue a broken system should be in /sbin (things like fsck). at the risk of reigniting a flame war, how is traceroute in a different catagory that ping? I don't think it is, but historically it has been in /usr/sbin and Herbert Xu won't move it to a /bin-type directory because it might break existing setups. Personally, I'm not certain it's a valid reason, since we move much larger chunks of stuff to comply with the filesystem standards, and I don't see anyone complaining about that... on the contrary, in fact, people file bugs if stuff isn't in a FSSTND/FHS compliant location. Then again, a little conservativisim over moving stuff won't hurt us :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Mon, Mar 20, 2000 at 02:38:12PM -0600, Steve Greenland wrote: There's a *lot* of history of using the space bar to do the next thing in Unix console programs (more/less, most news readers and existing mail readers). And there's no reason *not* to use them -- what else would you bind to the space key? You're right: the defaults should cater to the new user, but there's no reason to deliberatly aggravate the experienced user. BTW dselect keybinding for exiting the help screen shouldn't be space. Hopefully Wichert will include my patch for that (and the rest of the help stuff) in woody (he said he would). -- enJoy -*/\*- don't even try to pronounce my first name [no, there was no purpose to this post other than to say that exiting help system with space sucks ;]
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Sun, Mar 19, 2000 at 09:04:24PM -0300, Nicolás Lichtmaier wrote: Up and down arrow keys doesn't scroll a message ap down? Nope. But that's the way it is in slrn, too: backspace and enter scroll the message text, and uparrow and downarrow scroll the message list. It's good once you get used to it, and that takes about five minutes. :) Pg-down advancing to next message? No, pgdn goes page down in the message text, and if it reaches the end, it goes on to the next message. Once again, similar to slrn, where space scrolls one page down in the message text, and if it reaches the end, asks you to proceed to the next message with another space. The key binding are so insame that prevent people (newbies) fom using mutt, they first must to learn how to change those defaults to something acceptable. IME it's completely the other way round: they like the mutt keybindings better. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Release-critical Bugreport for March 18, 2000
On Mon, Mar 20, 2000 at 02:41:45AM -0800, Kevin Dalley wrote: [sth] Is it just me or did something make this message go out like 12 times? Each time it had more and more of these: MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:55 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:50 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:45 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:41 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:36 2000 X-Envelope-Sender: [EMAIL PROTECTED] WTF? :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: [dickey@clark.net: Re: http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=59191]
On Fri, Mar 17, 2000 at 02:48:30PM -0800, Darren O. Benham wrote: Anyway... there is a second problem you mentioned that deserves to be addressed. Bugs should either be dealt with by the maintainer (if they're involved with mods they made or the packaging) or the bugs are supposed to be forwarded upstream (with a patch if one is available). That is part of the Debian philosophy. I estimate that I get notified of less than 5% of the bugs. IIRC, Thomas Dickey is ncurses upstream maintainer... frankly, it has been practically orphaned for a long time, due to Galen Hazelwood's apparent AWOLness. And recently Espy offered it for adoption, again... that package really seems to be a `wild beast'. Anyway, wading through old bugs is a boring, difficult and overall completely uninteresting task. But it has to be done. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Two maintainer entrys in bug reports by maintainer
On Fri, Mar 17, 2000 at 08:25:47AM +0100, Andreas Tille wrote: I think if you reupload your packages with the correct Maintainer field, then the bug system will fix itself. Hmmm, that might fix the situation of two entries in the bug report for woody but not for slink or potato bugs. Moreover I consider it to be nonsense to upload a new package only to replace one valid e-mail address by another valid e-mail address without fixing any bugs (because there aren't any) or new upstream versions. The BTS takes the addresses from the `Maintainers' file, which you can find under indices/ directory on each FTP mirror. I'm not sure, but it would seem logical that the newest available package entry gets in the file. Alternatively, ask [EMAIL PROTECTED] to change it manually. -- enJoy -*/\*- don't even try to pronounce my first name
Re: [joey@infodrom.north.de (Martin Schulze)] Re: Re: kernel building
On Thu, Mar 16, 2000 at 09:47:41PM +1100, Mikolaj J. Habryn wrote: root isn't even mentioned in the headers. This is the only occurrence: Received: from mussel.ucc.gu.uwa.edu.au ([EMAIL PROTECTED] [130.95.13.18]) Why is this feature even in place? Isn't it obvious? :) You should not send mail from your »root« account. The »root« is a You should *not* use the »root« account for daily use or as your What are these character around root? They don't seem like quotes to me... If you haven't sent from a root account there is a chance that our list server has inserted a line like Sender: [EMAIL PROTECTED] which confuses the lists software. In that case please wait few hours and resend. Maybe this is the problem? Why would this happen, anyway? -- enJoy -*/\*- don't even try to pronounce my first name
Re: Two maintainer entrys in bug reports by maintainer
On Thu, Mar 16, 2000 at 01:12:21PM +0100, Andreas Tille wrote: * Andreas Tille [EMAIL PROTECTED] (1 outstanding Bug) * Andreas Tille [EMAIL PROTECTED] (1 outstanding Bug) The e-mail addresses are both valid, but it's the same maintainer (at least I get the mail from both :-) ). It is my task to use always the same address or is it a bug in the bug system? Neither. Do as you wish :) Personally I prefer using a unique Maintainer: field in all of my packages. -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Wed, Mar 15, 2000 at 12:10:54PM +1100, Craig Sanders wrote: Uh, which were the packages in question? Did you report it at the time? no need, the holes were already well known - and fixed in unstable. Security fixes have to be (and are) fixed in stable, too! most are. IMNSHO *all* of them must be. It would be wrong to leave the users of stable `in the cold'. Those bugs that aren't fixed in stable are the worst release-critical bugs. -- enJoy -*/\*- don't even try to pronounce my first name
Re: I don't get copies of bug reports to my packages
On Wed, Mar 15, 2000 at 11:25:47AM +0100, Gregor Hoffleit wrote: For some reason, since a while I don't get copies of bug reports against my packages mailed to me. I'm tracking debian-bugs-dist now and checking the web page once in a while, but this is less than satisfying. I noticed that [EMAIL PROTECTED] bot processes the messages you send to id silently, then processes it again, but this time mailing the report to you. It is also known that the locking in the BTS isn't implemented properly so any messages that you send while the web pages are being regenerated will get stuck in the incoming mail queue (or something like that, I don't quite recall the details correctly). Darren Benham and Adam Heath (they are behind [EMAIL PROTECTED]) spoke about this on IRC on several occasions. Word has it that Johnie Ingram has some patches for that Perl code, but I don't think these patches were applied... It actually seems that subscribing to -bugs-dist mailing list is useful right now... although it is so damn painful when you don't have lots of time to sift through it. :( -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Mon, Mar 13, 2000 at 08:17:00PM -0800, Joey Hess wrote: But slink is practically completely adjusted for 2.2 already. Sure, if you ignore the 12 packages that break (http://www.debian.org/releases/stable/running-kernel-2.2) I believe 12 out of ~2250 counts as practically completely. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Danger Will Robinson! Danger!
On Tue, Mar 14, 2000 at 01:44:09AM -0600, Manoj Srivastava wrote: Not having released for nearly 18 months [...] Which eighteen months do you refer to here? -- enJoy -*/\*- don't even try to pronounce my first name
Re: pgp-gpg keys, uploaded package not dinstalled?
On Tue, Mar 14, 2000 at 10:55:31AM +0200, joost witteveen wrote: That was all march 10, nearly 4 days ago, and fakeroot still isn't dinstalled. Was it rejected, or is it just stuck? If it was rejected, you have to reupload, if it is stuck, then ssh to master, go into incoming directory, and run ~maor/dinstall/dinstall -n fakeroot_whatever.changes That should provide an explanation. Is there anything else I need to do? (Sign for the time being with my pgp key, wait longer, or send bribes to keyring-maint?) (I haven't had a responce from my message to keyring-maint). You could try pestering James to include it sooner... but that might have a counter-effect ;) -- enJoy -*/\*- don't even try to pronounce my first name
Re: Becoming a developer
On Tue, Mar 14, 2000 at 01:23:58PM -0500, Ben Collins wrote: There is a ham radio program that I would like to see as a debian package. As I am not currently a developer, pehaps someone else might like to look into packaging this. Otherwise, I will do it, if I can run your ganlet and join your ranks. As most people will note, you don't have to become a developer to package things. You can attempt to find a sponsor that will validate and upload your packages for you. I suggest emailing debian-mentor to see if any ~~ The address is [EMAIL PROTECTED] just to make sure nobody sends mails to void :) other HAM people would be willing to take you under their wing. -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Wed, Mar 15, 2000 at 08:42:07AM +1100, Craig Sanders wrote: this same empirical evidence has also proved that 'stable' is LESS stable and reliable and secure than 'unstable'. the few debian boxes which i know of that have been compromised were cracked BECAUSE they were still running stable and had older versions of various programs which had known security holes. Uh, which were the packages in question? Did you report it at the time? -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Wed, Mar 15, 2000 at 09:18:00AM +1100, Craig Sanders wrote: this same empirical evidence has also proved that 'stable' is LESS stable and reliable and secure than 'unstable'. the few debian boxes which i know of that have been compromised were cracked BECAUSE they were still running stable and had older versions of various programs which had known security holes. Uh, which were the packages in question? Did you report it at the time? no need, the holes were already well known - and fixed in unstable. Security fixes have to be (and are) fixed in stable, too! -- enJoy -*/\*- don't even try to pronounce my first name
Re: Danger Will Robinson! Danger!
On Mon, Mar 13, 2000 at 09:39:52AM +1100, Drake Diedrich wrote: New hardware support seems to be a reasonable justification for allowing new versions into stable/frozen if there is also an older version there for the rest of us to fall back on in case it's a lemon. This would be valid, however, sometimes new drives aren't tested well, or are even marked as EXPERIMENTAL in the kernel configuration; so it's really hard to determine whether we want a possibly buggy driver (buggy ranging from spelling errors in printks :) to hardware fsckups) in the distribution, compared to no driver at all... But anyway: providing kernel *source* in the stable distribution for the bleeding-edge kernel versions would do fine. kernel-source-2.2.1 is in slink, and I haven't noticed anyone complaining. OTOH if there was a binary kernel-image-2.2.1 there, several RC bugs would have to be filed. Someone should upload kernel-source-2.3.whatever, too... shouldn't be much work. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Danger, Branden Robinson! Danger!
On Sun, Mar 12, 2000 at 10:40:36PM -0500, Branden Robinson wrote: There are exactly ONE HUNDRED server modules built by the stock 4.0 source tree. No, I don't know yet what exactly I'm going to do about that. If I got Driver Status document right, perhaps you could divide them per manufacturer... that way there would be about twenty or thirty packages. -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Mon, Mar 13, 2000 at 11:50:47AM +, Paul M Sargent wrote: Woody should be running 2.3 or pre-2.4. That should have been among the first things to change. There's a misunderstanding here: the distribution has no default kernel, the boot floppies do. Since nobody is working on woody boot floppies (why should they?), there is no default kernel for woody, it's all inherited from potato. But anyway, as I said before, a newer kernel source should be available as package. Coordinating the development cycles of an infinite number of packages is impossible. [...] The key point is a continually evolving release. Something like this will be possible when the package pools are implemented... -- enJoy -*/\*- don't even try to pronounce my first name
Re: (Re)build a Debian package
This is a message for debian-mentors mailing list, please use that one. On Mon, Mar 13, 2000 at 12:07:07PM +0100, SOETE Joël wrote: In this last directory I try to launch dpkg --build ... which failled because it did not find DEBIAN/control file (which stand in debian/control) You can't build the packages just like that, the control file has to exist, you need dpkg-gencontrol or equivalent... better run: fakeroot debian/rules binary I download and study all packaging documentation (also Debian policy) and try to find a FAQ but nothing to clarify my mind as a case study procedure for instance. Can you help me? Try reading the Packaging Manual, and the New Maintainers' Guide, found at http://www.debian.org/doc/packaging-manuals/packaging.html/ and http://www.debian.org/doc/maint-guide/, respectively. -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Mon, Mar 13, 2000 at 01:43:46PM +, Paul M Sargent wrote: Woody should be running 2.3 or pre-2.4. That should have been among the first things to change. There's a misunderstanding here: the distribution has no default kernel, the boot floppies do. Since nobody is working on woody boot floppies (why should they?), there is no default kernel for woody, it's all inherited from potato. ...but a distribution is designed for a particular kernel. e.g. slink is designed for 2.0.x with some packages for 2.2.x support. Supporting a kernel is not as much about the kernel package itself, but about the tools which surround it. But slink is practically completely adjusted for 2.2 already. IIRC, Sparc people needed a new glibc and a new kernel for slink, and that pulled in overall support for 2.2 in packages like mount or similar. If the kernel isn't even in the archive then potential problems aren't going to be found. I wouldn't put that much `weight' in the fact that kernel is in the archive: kernel packages don't get upgraded to new upstream versions, so if you want a new kernel, you have to make the decision to install it, on your own. Having the kernel in the archive is convenient for those with limited network access, using stable, or a snapshot of unstable. P.S. I missed the discussion on package pools. What's the theory? Implement a database for managing the FTP archive that would make lots of nifty things available... search the Debian Weekly News or debian-devel archives for details. -- enJoy -*/\*- don't even try to pronounce my first name
Re: The nature of unstable (was: Danger Will Robinson! Danger!)
On Mon, Mar 13, 2000 at 03:04:26PM +, Paul M Sargent wrote: If the kernel isn't even in the archive then potential problems aren't going to be found. I wouldn't put that much `weight' in the fact that kernel is in the archive: kernel packages don't get upgraded to new upstream versions, so if you want a new kernel, you have to make the decision to install it, on your own. But don't you think it's good to have the base system in place as soon as possible for a new development cycle. It's putting a stake in the ground. If somebody sees kernel-image-2.3.58 in the archive then it suggests they should be giving it a go. Hm, yes, I agree, it has a psycological effect. OTOH, maybe we don't want to put that stake into the ground until potato has been released, for obvious reasons. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Danger Will Robinson! Danger!
On Sat, Mar 11, 2000 at 11:41:10PM -0600, Manoj Srivastava wrote: Josip Why do we have to be a part of an industry? Debian would be Josip commercial if we truely cared about the industry... It is a quality of imlementation issue. If we are seriously outmoded, we can't honestly say we are trying to be the best distribution out there. Best means we at least try not to be several years behind other people. I'm not against trying to be the best, but against the reasoning *why* do we have to be the best. We shouldn't be influenced by the industry too much. because slink is so far behind that it isn't usefull anymore. Josip It's useful enough for a lot of people. So is miscrosoft. Microsoft products are for different people than ours are, IMHO. Debian has a stated goal of trying to achieve technical excellence. Obsolescence is a factor. Slink is called `stable' for a reason. It's not obsolete for people who just want a stable distribution. Of course, it is obsolete for people who want a nice GNOME (or especially KDE) environment, or those who own Athlons or other hardware the kernel provides, etc, etc. It seems that the number of those to whom slink is useful outweighs the number of those to whom it isn't. Josip A lot of people (including me) run kernel 2.2 on slink Josip machines just fine. And the point is? You can upgrade your kernel to 2.2 with little or no problems on slink machines. Really, that kernel just isn't the default, but it is otherwise fine. Once again, let's get back to fixing potato, and leave the chatter for appropriate lists or IRC... -- enJoy -*/\*- don't even try to pronounce my first name
Re: Release-critical Bugreport for March 10, 2000
On Sat, Mar 11, 2000 at 07:18:35PM -0800, Chip Salzenberg wrote: They can't both be standard if they conflict with each other, see Policy. Well, then, don't remove one, just change its priority! Who said I want to remove one? :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: Release-critical Bugreport for March 10, 2000
On Sat, Mar 11, 2000 at 12:07:11PM +0100, Christian Hammers wrote: Package: nfs-kernel-server (debian/main) Maintainer: Chip Salzenberg [EMAIL PROTECTED] 59641 nfs-kernel-server: conflicts with Standard package nfs-server Package: nfs-server (debian/main) Maintainer: Herbert Xu [EMAIL PROTECTED] 59642 nfs-server: conflicts with Standard package nfs-kernel-server Huh? Isn't this what it is expected to? They can't both be standard if they conflict with each other, see Policy. -- enJoy -*/\*- don't even try to pronounce my first name
Re: emacs19 removal? [was: rms@gnu.org: Bug#57636: Security problem with emacs19]
On Fri, Mar 10, 2000 at 08:19:29PM -0900, Ethan Benson wrote: BTW I was told removing all non-current Netscape Navigator versions will be done RSN (if it wasn't already done, haven't checked today). that could be a problem on the powerpc branch as the only available netscape is an outdated version. it still needs the 4.7 binaries. We could then make netscape4.7 source package build binary packages only for powerpc. Adam (CC:ed), what do you think? Someone should also bitch at Netscape Inc. for not providing 4.72 for powerpc. -- enJoy -*/\*- don't even try to pronounce my first name
Re: emacs19 removal?
On Sat, Mar 11, 2000 at 09:12:52PM +0100, Igor Mozetic wrote: Can we remove emacs19 from unstable now? It's de facto orphaned both upstream and in Debian, and a new version exists, supported in both upstream and Debian. What happens to vm then? I depends on emacs19 (and not emacs20) ... Obviously, the same, otherwise it would have a broken dependency. Same goes for the other packages that explicitely depend on emacs19: custom emacs-czech emacs19-el vm w3-el-e19 Do all of these have replacements that work with other emacsen? -- enJoy -*/\*- don't even try to pronounce my first name
Re: Danger Will Robinson! Danger!
On Sat, Mar 11, 2000 at 04:06:01PM -0500, Jacob Kuntz wrote: being a year behind is suicide in any industry. being a year behind in an industry that moves as fast as open source software, is idiocy. Why do we have to be a part of an industry? Debian would be commercial if we truely cared about the industry... because slink is so far behind that it isn't usefull anymore. It's useful enough for a lot of people. IMHO, leaving out 2.4 is a bad idea. there were problems with 2.0 - 2.2. there was an incompatible build of lsof, as well as some networking problems. How horrible, disastrous! : A lot of people (including me) run kernel 2.2 on slink machines just fine. FWIW all these arguments how we shall all die in disgrace if we don't get 2^32 releases out in the next ten years and similar, are a huge pile of junk (no offense, nothing personal). To release faster would be great, but no market pressure or yet another non-technical flamewar on debian-devel will help. Let's just get back to work... I have a ppp NMU to do :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: GRUB
On Fri, Mar 10, 2000 at 04:20:07PM +0100, Michael Meskes wrote: Is there any easy to understand HOWTO available? I'd like to play a little bit with grub but after reading the texinfo files it seems to be too complicated to do just that. And I don't like to spend hours to understand something just to see it does not help me much. The info's from CVS are better IMHO (then again, I'm biased, I helped write it :), they contain a tutorial about setting up grub. I wonder if the package from `unstable' has them... maybe these are even worth backporting to potato. I wonder if grub is able to cope with cylinders1023. It is. -- enJoy -*/\*- don't even try to pronounce my first name
emacs19 removal? [was: rms@gnu.org: Bug#57636: Security problem with emacs19]
- Forwarded message from Richard Stallman [EMAIL PROTECTED] - X-Envelope-Sender: [EMAIL PROTECTED] Subject: Bug#57636: Security problem with emacs19 Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED] X-Debian-PR-Message: report 57636 X-Debian-PR-Package: emacs19 X-Debian-PR-Keywords: Date: Fri, 10 Mar 2000 02:15:29 -0700 (MST) X-Authentication-Warning: aztec.santafe.edu: rms set sender to [EMAIL PROTECTED] using -f From: Richard Stallman [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED], [EMAIL PROTECTED] We are not maintaining Emacs 19 any more. I think the current version of Emacs uses a different method of allocating temp files. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] - End forwarded message - Can we remove emacs19 from unstable now? It's de facto orphaned both upstream and in Debian, and a new version exists, supported in both upstream and Debian. I was told once that we only kept version 19 in the archive for the sake of the people who haven't yet managed to convert their configuration files to version 20. It would seem logical to declare that conversion time period over, after three years. Note that removing a package from the FTP archive doesn't mean the package will automagically be removed from all users' machines, not by a long shot. BTW I was told removing all non-current Netscape Navigator versions will be done RSN (if it wasn't already done, haven't checked today). -- enJoy -*/\*- don't even try to pronounce my first name
Re: magnetic synchronous motor water pumps
On Wed, Mar 08, 2000 at 02:43:37PM +0100, Nils Jeppe wrote: One possible technique we could employ is to require that the list address appear visibly in the headers (to: or cc:). This would prevent Bcc'ing the lists which is a shame (and care would need to be taken with -private, which is also security), but it might be worth it. This is hardly a real solution. Spammers still could post stuff to the list. Still, large portion of them do use Bcc:, IME - I have been filtering my mail on the same rule for ages, and I notice all mails that escape it, and those that are really personal/wanted mail, but don't escape it - the ratio is satisfactory. -- enJoy -*/\*- don't even try to pronounce my first name
Re: slink - potato
On Fri, Oct 01, 1999 at 11:43:17AM -0700, John Lapeyre wrote: Something I have noticed several times. If you are doing a remote upgrade (probably a crazy idea), the telnet daemon (maybe inetd or something) becomes unavailble for quite some time. Maybe it is between the time that netbase is unpacked and when it is configured. There are usually problems with a broken package or two so that apt-get upgrade does not work on the first try. If I lose my telnet connection, I can't telnet again to fix things. The Release Notes for slink explicitely said you should install telnetd package if doing a hamm-slink upgrade over telnet link (no, I don't think it is a crazy idea, it is in fact marvelous feature :)... maybe you have experienced the same problem? I'd appreciate someone would investigate this, because the potato Release Notes[1] must include such anti-showstopper information. [1] ... which I'll be co-authoring, FWIW... -- enJoy -*/\*- don't even try to pronounce my first name
Re: dhcpcd procedure
On Fri, Oct 01, 1999 at 12:28:36PM -0400, Dpk wrote: I recently adopted dhcpcd... previous versions of dhcpcd would restart during upgrades, which obviously is bad for those doing it remotely. Since my recent upload does not restart dhcpcd, I need to start it for those upgrading from previous versions that did stop the daemon. What would be the best way to check for this? A simple 'ps |grep dhcpcd' ? Would doing so make my package dependent on procps? Maybe you could use the pidof utility, which comes with sysvinit (which is Essential: yes package)? is there a convenient way to check the installed version of dhcpcd someway? From the packaging manual: 3. 1. If the package is being upgraded, call: new-preinst upgrade old-version When we configure a package (this happens with `dpkg --install', or with `--configure'), we first update the conffiles and then call: postinst configure most-recently-configured-version So, you could put something like this in the preinst: if [ $1 = upgrade -a $2 ]; then whatever you need to do fi Or this in postinst: if [ $1 = configure -a $2 ]; then whatever you need to do fi And yes, this question would be more appropriate for debian-mentors list. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Debian recommended software (moving off-topic)
On Sat, Oct 02, 1999 at 04:59:35PM +0200, Martin Bialasinski wrote: Whatever, I won't restart this thread again. I wouldn't touch wuftp with a 10ft pole. I switched to proftpd, when there was a hole in many ftpds (creating a very deep directory hierarchy), the fix for proftpd was available after 1-2 days, but for wuftp, it took 2 weeks. Is there an upstream maintainer for wuftpd? Half a year ago, a new development group for wu-ftpd has been formed. They are releasing new versions and making quite a lot of changes/fixes really fast these days. -- enJoy -*/\*- don't even try to pronounce my first name
Re: shlib-with-non-pic-code _libglademodule.so
On Fri, Oct 01, 1999 at 11:23:00AM +0200, Torsten Landschoff wrote: I am the maintainer of python-gnome and the associated modules. The current python-glade has support for the libglade library in _libglademodule.so. Problem: Lintian complains that _libglademodule.so contains position dependent code. But it is compiled with gcc -g -O2 -fPIC -c libglademodule.c gcc -shared -lc -o _libglademodule.so libglademodule.o -lglade -lxml -lz \ -lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXi -lXext -lX11 -lm (I removed some of the uninteresting options as -Lfoo and -Ibar) Could you tell me what I am doing wrong? I don't see anything wrong in that gcc commands. Perhaps lintian is wrong? I think so, too. I have experienced this error several times, and could not find any error in the .so files it said were wrong. The bug report is already filed, #46186. BTW does this perhaps happen on just this one library in the package? -- enJoy -*/\*- don't even try to pronounce my first name
Re: Packages should not Conflict on the basis of duplicate functionality
On Thu, Sep 30, 1999 at 09:47:24PM -0500, Eric Weigel wrote: I wanted to look at each of ipopd, gnu-pop3d and cucipop. I could only look at one at a time. It was ok in my case, because the machine I was using has very little pop3 traffic. But it was awkward. If I wanted to download source and recompile it, I would not be using Debian. I like the package manager. I also like the thought that goes into problems like this. [snip] I'd like to propose something else: until the packages provide proper debconf (or whatever) support which would configure the port and other settings for the daemon, let's keep the Provides:+Conflicts: scheme we have been using so far. Let's admit it - the newbies[1] are the majority of Debian users. Most of these newbie users will (usually by accident) try to install another POP3 daemon, it will stomp over an existing one, and the user will get problems they will not know how to fix, at least not instantly. I'm all for detailed configuration and enhanced settings and all that nice stuff for sysadmins, but first, let's get it properly implemented in the packaging system, the back bone. Until then, keep the default way safe for the general use. [1] note the difference between newbie and lamer. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Bug#46184: mtools
On Wed, Sep 29, 1999 at 12:45:18AM -0400, Mark W. Eichin wrote: It looks like floppyd is the only thing that needs X. I'm not sure it *is* better to fork things off; that's a fair amount of hair for one isolated program. Maybe not - it wouldn't be the first nor the last 50kb large Debian package. I can help (provide patches or do NMU) with separating it into another package, shouldn't be such big problem. Given the extent to which new package insertion from incoming has been backlogged, I'm afraid it might also be a while before it got uploaded, Someone will take care of that in reasonable amount of time, surely. and I'd have to consider instead dropping floppyd from the install, though that seems a poor choice... Yes, I wasn't arguing against packaging that program, but against its placement in mtools package. Sure, if it's useful, let people use it :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: mtools
On Wed, Sep 29, 1999 at 03:35:41PM +, Dale Scheetz wrote: mtools, it's only one single file; a daemon (floppyd, if I'm not all wrong) that needs xlib6g. It'd be simple to extract this daemon from mtools and create an extra package with just this file, and make this file recommended by mtools, and make mtools required by the extra-package. So now you have two packages one without an xlib6 dependency, that requires an extra-package with _does_ depend on xlib6. Pushing the dependency away by one package, doesn't make it disappear. But who said mtools need to depend on floppyd package? -- enJoy -*/\*- don't even try to pronounce my first name
Re: mtools
On Tue, Sep 28, 1999 at 07:13:58AM -0700, Joseph Carter wrote: How comes mtools depend on xlib6g? I don't use X, and thus I consider it very stupid to have both xlib6g xfree86-common installed, but I have to if I want mtools installed... If something supports X it should be compiled with X. This means exactly two packages (xlib6g and xfree86-common) are also required, but they're reasonably smallish and anything which supports X is going to require them anyway, not just mtools. Better to fork off another package, which would include X support, and leave the original package X-free. -- enJoy -*/\*- don't even try to pronounce my first name
Re: uscan and those debian/watch files?
On Tue, Sep 28, 1999 at 11:22:34AM -0400, Peter S Galbraith wrote: ftp.phys.ocean.dal.ca users/kelley/gri/ gri-*.tgz debian uupdate Am I doing something obviously wrong? IIRC you can use this: ftp.phys.ocean.dal.ca /users/kelley/gri gri-(.*)\.tgz debian uupdate See the manpage, too. -- enJoy -*/\*- don't even try to pronounce my first name
Re: mtools
Subject: mtools: please put X related stuff in another package Package: mtools Severity: normal On Tue, Sep 28, 1999 at 10:16:20AM -0500, Brian Servis wrote: How comes mtools depend on xlib6g? I don't use X, and thus I consider it very stupid to have both xlib6g xfree86-common installed, but I have to if I want mtools installed... If something supports X it should be compiled with X. This means exactly two packages (xlib6g and xfree86-common) are also required, but they're reasonably smallish and anything which supports X is going to require them anyway, not just mtools. Better to fork off another package, which would include X support, and leave the original package X-free. What about the [x]emacs packages. I would hate to see forks of all those things on the mirrors. Maybe a Suggests or Recommends would be better than a Depends. Correction: mtools in slink does *not* depend on anything but libc6, so there is still time to do it, cleanly. Maintainer, please do it. -- enJoy -*/\*- don't even try to pronounce my first name
Re: mtools
severity 46184 wishlist thanks On Tue, Sep 28, 1999 at 12:28:08PM -0500, David Starner wrote: Correction: mtools in slink does *not* depend on anything but libc6, so there is still time to do it, cleanly. Maintainer, please do it. The bug tracking system has a weird X-Debian-CC system set up so you don't That was changed to X-Debbugs-CC: , IIRC. create several bugs through people replying to messages like this, and messages like this get added to the bug. There was no such bug filed, AFAIK, so I didn't do anything wrong (except forgetting to set Reply-To: which would exclude [EMAIL PROTECTED]). First, I believe this is against policy. Do not create two versions (one with X support and one without) of your package. This does not mean you can't split off the *different* binaries in two packages. Anyway, what is there X related in mtools? If this request does indeed conflict with the Policy, I'll close it, of course. Anyway, why is this in the policy (section 5.8), can someone enlighten me? We split off various versions of our packages, like all those programs that have GTK+, GNOME, KDE, OpenGL, SSL, ALSA, insert-whatever support... seems perfectly legal to do the same for X packages. Second, shouldn't this be wishlist anyway? It's not like it's an error in the program, it's just something you don't like. Yeah. -- enJoy -*/\*- don't even try to pronounce my first name
data section! [was: Re: Censoring :) (was: Re: anarchism_7.7-1.deb)]
On Mon, Sep 27, 1999 at 02:23:03PM +0200, Federico Di Gregorio wrote: Scavenging the mail folder uncovered Siggy Brentrup's letter: There should be one for the main distribution. Assume I want to go into the CD business providing support for packages in the main dist. The way it is, I can't say Support for all of Debian's main dist. I don't know the answer but having non-doc (in the sense of non-application-that-is-in-main-doc) stuff is bad. What if I package the 3 CD set of US maps that is publicy available? That is about 1.8Gb of sources plus 1.8Gb of .debs for about 3.6Gb of ftp space... and nobody can tell me don't do that! What about having Debian be an OS+apps and have SPI found a *new* association for the distribution of free *data*? We are already doing that - the proposal on the policy list regarding a new, data section of the FTP server has passed. Hopefully, it will be implemented in practice soon. -- enJoy -*/\*- don't even try to pronounce my first name
Re: BTS feature comments
On Thu, Sep 23, 1999 at 08:35:06AM -0700, Darren Benham wrote: | And do what... there are going to be keys that aren't in the debian keyring.. Non-developpers should not be allowed to *manipulate* bugs IMO. What do you think? Make me PGP/GPG/whatever sign all messages I send to [EMAIL PROTECTED], and I shall become your mortal enemy : :) Next step would be signing everything sent to the BTS, then everything sent to debian-* mailing lists... please, don't. If anyone puts trash in the BTS because there is no authentication, we'll handle it. I'll even volunteer to clean it up. -- enJoy -*/\*- don't even try to pronounce my first name
Re: problems with the perl5 packages
On Fri, Sep 24, 1999 at 01:32:29PM +, Dale Scheetz wrote: So, why are there packages with depends lines that include both perl5 and a particular version, like perl-5.005? When a package depends on a virtual package which is provided by multiple real packages, but none of these are already installed (hint: new installation of the whole system), APT and dselect will be confused and not know what to do, because they can't just make a guess and install a package when several equal (to them) options are present. [1] Anyway, that's just one possible explanation, it might not be valid in this particular case. [1] What a large sentence... :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: apt-get source fails for some packages
On Thu, Sep 23, 1999 at 10:43:01AM +0900, Atsuhito Kohda wrote: dpkg-source: error: Expected ^@@ in line 4569 of diff \ No newline at end of file This bug is already known, reported, and is promised to be fixed in the next dpkg(-source) upload. -- enJoy -*/\*- don't even try to pronounce my first name
Re: vrweb, newbie maintainer/developer
On Wed, Sep 22, 1999 at 03:13:03PM +0800, Paul Harris wrote: i have agreed to take VRweb off Fabien Ninoles' hands, and have been successful in making it work under my Potato system! woo hoo! however, i have no idea what the next steps are: - What is the technique to rediff a package for the debian diff? What do you mean? - Why is dpkg-source complaining about: $ dpkg-source -x vrweb_1.5-2.dsc dpkg-source: error: Expected ^@@ in line 679 of diff is this some sort of bug? seemed to work earlier... i just untared and patched it myself How did you make the diff? You should have did this: fakeroot debian/rules clean; cd .. ; dpkg-source -b vrweb-version/ - Where are the FMs on the debian/rules stuff? I'd just like to make sure it works after i get that diff thing going. The Packaging Manual. Basically, you need these rules: clean, binary, binary-arch, binary-indep. - How do I accept vrweb as mine? Do I need to get a sponser or something? Set the Maintainer: field in the control file. If you aren't a registered developer, yes, you need a sponsor. - How do I wack it on the debian mirror and all that? If you're developer, use dupload(1), if not, sponsor will do that for you. look at fixing bug #29078: package vrweb depends on library libg++272. is this really a bad thing? Yes, that's an obsolete library. * libg++.so.2.7.2 = /usr/lib/libg++.so.2.7.2 (0x400d6000) * libstdc++.so.2.7.2 = /usr/lib/libstdc++.so.2.7.2 (0x4010e000) and mine (the working! one): * libstdc++-libc6.1-2.so.3 = /usr/lib/libstdc++-libc6.1-2.so.3 (0x400d6000) Your one is okay. Or even better, libstdc++2.10. the *s indicate difference between the two. now, why doesn't the old one work? the libraries they were compiled for may be different, but won't it work with the old libc stuff installed? should i even bother thinking about this since the new compile works? i only ask as other people seem to have problems with their old libc5 stuff... maybe the same problem is suffered here... would this help anyone to debug it? As long as it works with newest non-obsolete libraries, you shouldn't care much :) BTW, these questions ought to be asked on debian-mentors list, debian-devel is inappropriate. -- enJoy -*/\*- don't even try to pronounce my first name
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: Move proftpd to contrib
On Fri, Sep 17, 1999 at 11:22:59PM +0200, Martin Bialasinski wrote: Anyway, which ftpd in unstable do you see as the package to promote as the ftpd of choice in Debian? Just to see what our alternatives are. 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 well tested and greatly improved software, for years now. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Guessing the date style from the timezone for postgresql postinst
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... -- enJoy -*/\*- don't even try to pronounce my first name
Re: Move proftpd to contrib
On Thu, Sep 16, 1999 at 10:42:36PM -0500, John Goerzen wrote: This package has been a major source of serious security bugs and indicatiosn are that it will remain as such. Our Policy states that packages that are not sufficiently free of bugs to meet our standards should not be in main and should be moved to contrib. The contrib section should not be a dumpyard for buggy packages. project/experimenal seems to be the right place for those. The Policy should be changed. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Debian 2.1r3
On Fri, Sep 17, 1999 at 03:44:36PM +0100, Chris Rutter wrote: The current `sub-release' (whatever) of Debian 2.1 is r3, right? I was just wondering, as all references on the web site are to r2, but I thought I received a message from the security team about r3 last week somtime. Just wanted to check before I filed a boring bug report, or something. /pedant Nope, r2 is still official, apparently there have been some problems with syncing packages on some architectures. -- enJoy -*/\*- don't even try to pronounce my first name
Re: Move proftpd to contrib
PLEASE reply below the old text, cut unneeded quote, and wrap your lines at 76 characters! On Fri, Sep 17, 1999 at 07:52:24AM -0700, David Bristel wrote: This package has been a major source of serious security bugs and indicatiosn are that it will remain as such. Our Policy states that packages that are not sufficiently free of bugs to meet our standards should not be in main and should be moved to contrib. The contrib section should not be a dumpyard for buggy packages. project/experimenal seems to be the right place for those. The Policy should be changed. BTW there is already a proposal for this, see bug #45318. Or a new section for packages removed from main due to bugs, but possibly still desired by some people? It's safer to have a clear message that Debian considers these packages to contain too many bugs for inclusion in the main distribution, but we are aware that there are some who want to use these packages anyway. Something like this would eliminate any blame if people use those buggy packages, and then have their systems crash or go unstable, or get hacked. Any opinions? project/experimental is exactly what you described. -- enJoy -*/\*- don't even try to pronounce my first name
