Problem with tcpdump in 1.2.17
Before the coffin is nailed shut on rex, maybe the version of tcpdump that was placed in 1.2.17 should be replaced or backed out, as it depends on libpcap0, which is in bo, but not rex. I say this because I think Dale Scheetz (among other people) was going to burn a CD of the final version of rex for people, and this would be sort of an embarrassing bug to send out the door. Please correct me if I'm wrong about this. -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://cartoon.ecn.purdue.edu/~branden/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with tcpdump in 1.2.17
On 7 Jun 1997, Guy Maor wrote: > I made a 1.2.18 to fix this. The info in the new Packages file lists libpcap0 as being in net and libpcap-dev as being in devel, which is fine, but a dpkg --info on the libpcap0 file itself reports its section as "libs", which doesn't exist in rex. Is this a problem? It probably isn't for people who use dpkg by hand to install, but I don't know enough about dselect to guess whether it would be a problem for people who use it. Also, the inclusion of libpcap-dev isn't mentioned in the ChangeLog, so I didn't fetch it. It was only after I looked in Packages.gz that I knew it was there. -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://cartoon.ecn.purdue.edu/~branden/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problem with tcpdump in 1.2.17
On 8 Jun 1997, Guy Maor wrote: > <[EMAIL PROTECTED]> writes: > > > The info in the new Packages file lists libpcap0 as being in net and > > libpcap-dev as being in devel ... > > It's not a problem. Well, no, that wouldn't be -- the -dev versions of packages are often in a different place. The point of my remark was that the Packages file said libpcap0 was in one place, and libpcap0's own control file said it was someplace else (net vs. libs). If this isn't a problem big enough to sweat about, I don't care...I just wanted to point it out. If I thought it was the end of the world I'd file a bug report. :) > The ChangeLog is actually listing _source_ package names, so there is > only one entry for "libpcap0". I will improve the format for bo when > it will be edited automatically. Oh ah (he said as comprehension dawned). -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://cartoon.ecn.purdue.edu/~branden/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: leap second
On Sat, 21 Jun 1997, Mark Baker wrote: > As it is, we use POSIX time, which means that the system time follows GMT. > When there is a leap second the time itself is changed; the timezone > information does not need to. > > > This is completely unacceptable. OS time must be predictable. > > Which is why real time would be much better than POSIX time. > > Unfortunately we have to use POSIX time, so we're compatible with other > computers on the network :( Can someone explain to me exactly what POSIX time is? I was under the impression that many computers on the net (at least ones belonging to big sites) grabbed their time from a radio signal broadcast by the U.S. Naval Observatory or some similar organization, and propagated the correct time from there. xntp is supposed to figure in network latency from a host with an authoritative notion of the time, right? I do know that they do that very thing here at Purdue. -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://www.ecn.purdue.edu/~branden/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: fixhrefgz - tool for converting anchors to gzipped files
On Fri, 27 Jun 1997, Martin Schulze wrote: > On Jun 27, Christian Schwarz wrote > > > I wrote exactly the same thing in Perl (on your request!) some time ago. I > > have attached it to this mail. > > > > I don't know which version is better. It looks like Lars' implementation > > has hard coded a lot of HTML tags for processing. Mine is based on Perl's > > HTML::Parser class and is thus independent of any specific HTML tags. > > "better"? I'm not sure if this is important. If the tool should > be used on every system, we should use the perl tool. We cannot > recommend another high-level interpreter (python) - perl should be enough. > > > # Currently, we have a problem with compressed HTML: we can access > > # compressed HTML fine, but links don't work very well. The problem > > # is that the link says "foo.html", and the actual file is > > # "foo.html.gz", > > # and the browsers and servers aren't intelligent enough to handle > > # this invisibly. This means that we can't install compressed HTML, if > > # it contains links. > > Wouldn't it be a cool project if we would improve all Debian used > browsers to handle this and give back the code to the upstream > release? I like the idea. Yes, but... On Thu, 26 Jun 1997, Federico Di Gregorio wrote: > > From: Federico Di Gregorio <[EMAIL PROTECTED]> > To: Debian Development > > [...] > > > Right, but typing xxx.html.gz will work! We can write a litte sed script > > > to change the links from xxx.html to xxx.html.gz inside the documents. > > > > What do the popular http daemons do about this? I think a good solution > > would be: > > > > For every .html request that comes in (or perhaps for any request in > > general), look for a file fitting the traditional spec. > > > > If that fails, look for a .gz version of that file in the same directory. > > > > If that fails, return the usual 404 error. > > > > Does anything already implement this? If not, why not? > > boa support this. it even decompress on the .gz file on the fly. > I just tryed to access http://localhost/doc/HOWTO/INFO-SHEET and > it works! > > boa is also very small and really fast. i think should be the default > httpd of choice for a small debian system. I haven't tested this myself, but it looks like the ideal solution, because: 1) You can compress documentation, like we want to, without having to hack or modify it, and 2) It permits document maintainers to gunzip the html file for modifications, and uses the uncompressed one in case they forget (or don't want to) re-compress it. -- G. Branden Robinson | Kissing girls is a goodness. It is a Purdue University | growing closer. It beats the hell out [EMAIL PROTECTED] | of card games. http://www.ecn.purdue.edu/~branden/ |-- Robert Heinlein -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Documentation Policy
On 25 Jun 1997, Manoj Srivastava wrote: > >>"Philip" == Philip Hands <[EMAIL PROTECTED]> writes: > > Philip> I was thinking about the possibility of offereing _all_ Debian > Philip> documentation on a web site --- which lpr(1) man page would > Philip> you want to show? lpr's or lprng's? > > Philip> Perhaps man pages should really go in > Philip> /usr/doc/package-name/man/, with symbolic links for /usr/man > Philip> if needed --- then there wouldn't be as much of a problem > > That is a good idea for the web site (which is what I hope you > meant, rather than massively changing man just for Debian systems). Right. I would think /etc/alternatives handles things just fine for end-user systems. -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://www.ecn.purdue.edu/~branden/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Re^6: Status of Debian Policy
On 25 Jun 1997, Marco Budde wrote: > Am 23.06.97 schrieb pdm # informatics.muni.cz ... > > MZ> - Limited possibilities of handling gzip files (typing xxx.html > MZ> doesn't find xxx.html.gz) => problems with links (may be solvable by > > Right, but typing xxx.html.gz will work! We can write a litte sed script > to change the links from xxx.html to xxx.html.gz inside the documents. What do the popular http daemons do about this? I think a good solution would be: For every .html request that comes in (or perhaps for any request in general), look for a file fitting the traditional spec. If that fails, look for a .gz version of that file in the same directory. If that fails, return the usual 404 error. Does anything already implement this? If not, why not? -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://www.ecn.purdue.edu/~branden/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
PGP -kc forgets a key, has corrupt output?
-BEGIN PGP SIGNED MESSAGE- I am reposting this from comp.security.pgp.tech, where my plea was met only with stony silence. Can someone here help? (Lars, do you know anything about this?) I have read the pgp manpage and pgpdoc[12].txt files in their entirety, and cannot figure out what the problem is. Newsgroups: comp.security.pgp.tech Subject: PGP -kc forgets a key, has corrupt output? Date: 24 Jun 1997 13:05:01 GMT Organization: Purdue University Lines: 96 Sender: Branden Robinson <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> NNTP-Posting-Host: cartoon.ecn.purdue.edu X-Newsreader: TIN [UNIX 1.3 unoff BETA 970622; sun4u SunOS 5.5] Could someone enlighten me please? I just recently signed the key of someone whose key is on my public ring. pgp -kv on my public ring shows correct output, but pgp -kc makes it appear that I have signed my own key twice, and leaves out the other inidividual's information -- except for the fact that it recognizes his signatures on my and other keys and expands it to his name. I'm using pgp 2.6.3a from the pgp-us Debian package assembled by Lars Wirzenius (moderator of comp.os.linux.announce, among other things). Here is some sample output, edited for brevity. [0] 205 apocalypse ~ > pgp -kvv | more Pretty Good Privacy(tm) 2.6.3a - Public-key encryption for the masses. (c) 1990-96 Philip Zimmermann, Phil's Pretty Good Software. 1996-03-04 Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc. Distributed by the Massachusetts Institute of Technology. Export of this software may be restricted by the U.S. government. Current time: 1997/06/24 12:53 GMT Key ring: '/home/branden/.pgp/pubring.pgp' Type Bits/KeyIDDate User ID pub 1024/F6599E8D 1996/07/20 Bruce Perens <[EMAIL PROTECTED]> [...] pub 1024/D23450F9 1997/06/21 Branden Robinson <[EMAIL PROTECTED]> sig D190E74D Terran Lane <[EMAIL PROTECTED]> sig D23450F9 Branden Robinson <[EMAIL PROTECTED]> pub 1024/D190E74D 1996/09/25 Terran Lane <[EMAIL PROTECTED]> sig D23450F9 Branden Robinson <[EMAIL PROTECTED]> sig C38884A5 (Unknown signator, can't be checked) sig 20D3D431 (Unknown signator, can't be checked) sig 914C58A9 (Unknown signator, can't be checked) sig 47D738C1 (Unknown signator, can't be checked) sig B29DE5FD (Unknown signator, can't be checked) sig D7BD2F75 Timothy M. Stough <[EMAIL PROTECTED]> sig 9C2A5CDD (Unknown signator, can't be checked) sig FC0C02D5 Eugene H. Spafford <[EMAIL PROTECTED]> sig D190E74D Terran Lane <[EMAIL PROTECTED]> 6 matching keys found. As you see, my own key is next to last in this output, followed by Terran Lane's, which I signed. Now for the strange part. [0] 206 apocalypse ~ > pgp -kc | more Pretty Good Privacy(tm) 2.6.3a - Public-key encryption for the masses. (c) 1990-96 Philip Zimmermann, Phil's Pretty Good Software. 1996-03-04 Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc. Distributed by the Massachusetts Institute of Technology. Export of this software may be restricted by the U.S. government. Current time: 1997/06/24 12:56 GMT Key ring: '/home/branden/.pgp/pubring.pgp' Type Bits/KeyIDDate User ID pub 1024/F6599E8D 1996/07/20 Bruce Perens <[EMAIL PROTECTED]> [...] pub 1024/D23450F9 1997/06/21 Branden Robinson <[EMAIL PROTECTED]> sig! D190E74D 1997/06/24 Terran Lane <[EMAIL PROTECTED]> sig! D23450F9 1997/06/21 Branden Robinson <[EMAIL PROTECTED]> sig! D23450F9 1997/06/24 Branden Robinson <[EMAIL PROTECTED]> And Terran Lane's key, which I signed, is completely absent from this output. Is this a bug in 2.6.3a, am I misinterpreting this output, or has my public ring become corrupted? Please help. Apologies for not signing this message "correctly", my newsreader does not integrate well with pgp. Of course, pgp-signed or -encrypted mail is welcome. - -- G. Branden Robinson Purdue University [EMAIL PROTECTED] http://www.ecn.purdue.edu/~branden/ -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM7H7qKiRn0nSNFD5AQEtggP/ZkjHBv9Ko4dANFr/orXmtXYHtwlGbHFY YNDx8kH6zUUpfvMPyhFIuTjUX/s4roAm7lCOaX6G8BzC1DonYmK7pVIdgslev0DC lfDkOrXPUNtSOmdVOnttIwv+wdtiS3zI6YICIg4GmOx3KyejwigDcTjvw3cxpZ4X 8XOETWqtBsM= =vvnE -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: fixhrefgz - tool for converting anchors to gzipped files
-BEGIN PGP SIGNED MESSAGE- On Fri, 27 Jun 1997, Christoph Lameter wrote: I can sort of see both sides of this argument. I agree that rewriting html documents to say ".html.gz" in their hrefs is bad. [Lars Wirzenius wrote:] > : Being able to read documentation directly without running > : a web server is very important. > > So far I cannot discern why. I can, and it's a good point. In case the machine is in single-user mode, for instance. You seldom need the docs more than when the box is at init level 1. I have two suggestions, and they're both going to take some work. If someone wants to organize this, I can contribute what feeble coding skills I have to it, because I think it's important. 1) We need to make sure boa (since it looks like that's what we'll be using) is as close to bulletproof as it can get. It needs to stay small and fast, and it also needs to be clean, efficient, and secure. It needs to be as ready to do its job as telnetd. (Is boa hooked into inetd or does it run on its own? If it's a non-forking daemon, why can't it be grafted into inetd? Answer these questions gently, folks -- I haven't looked into the guts of inetd.) This way we don't have to screw with rewriting HTML files. 2) We need to hack some .gz sophistication into the file: handling code of lynx. (I.e., you feed it a filename, it looks -- can't find it? look for filename.gz and run gzip as a filter -- still can't find it? smack the user around) This is probably slower and less preferred, but necessary for single user mode. Lynx already is smart enough to gunzip files that have a .gz extension. This doesn't sound very hard, so if people think it's a good idea, I'll have a go at modifying the source to do this myself. Perhaps it should look for a certain flag in its config file before behaving this way, which we can call "debian_gz_flamewar" or something. Anyway, I know what happens when you step in between quarrelling giants, so I think I'll don both a hardhat and an asbestos suit. - -- G. Branden Robinson | It was a typical net.exercise -- a Purdue University | screaming mob pounding on a greasy spot [EMAIL PROTECTED] | on the pavement, where used to lie the http://www.ecn.purdue.edu/~branden/ | carcass of a dead horse. -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv iQCVAwUBM7UUVaiRn0nSNFD5AQH5wwQAtKT5wobK8PYMe9siVh4ujRG0cU3dxFNb VGRniXE+2Dzd+MEeP8/loaXLFIWF24aUHb/2MkmF2mfnJW7Vj2e6e6Ernbt27R96 dB6cz985yze7LApqNmBpkwZAP91jAAWZsvbQLHcVYPDe2j9fuSBfBvJuVsKt8g3p y0ssPLz/Ocs= =4Vrn -END PGP SIGNATURE- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
having trouble with xdm/xfs 4.3.0.dfsg.1-9?
[Followups set to debian-x.] Hi folks, I just wanted to bring the following information to the attention of those who may be frustrated by problems with the latest xdm and xfs packages. [...] [14 December] XFree86 4.3.0.dfsg.1-9 sneaked out with a couple of small but annoying bugs in it. Specifically, the xdm and xfs packages suffer from some bad shell syntax in conffiles. Fabio and I plan to release what it is currently on the SVN trunk as 4.3.0.dfsg.1-10 in a couple of days. In the meantime, you can grab fixes (in unified diff format) for the [14]xdm bug and the [15]xfs bug from the archives of the debian-x mailing list. 14. http://lists.debian.org/debian-x/2004/12/msg00411.html 15. http://lists.debian.org/debian-x/2004/12/msg00410.html [...] The above is from the X Strike Force news page. If you use Debian X Strike Force-maintained packages from testing or unstable, please bookmark the following site: http://necrotic.deadbeast.net/xsf/XFree86/NEWS.xhtml -- G. Branden Robinson| The greatest productive force is Debian GNU/Linux | human selfishness. [EMAIL PROTECTED] | -- Robert Heinlein http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Bug 295175 followup
On Sun, Feb 20, 2005 at 01:16:58PM -0800, Thomas Bushnell BSG wrote: > Bug 295175, the grave xfree86-common bug that was blocking many > autobuilds has now had its fix uploaded to the archive. > > Unfortunately, the xfree86 build with the fix is failing, and looking > at the build logs, I think it's because the buildd chroots are still > corrupted with the damage that the buggy package did. Well, the damage is in part the package's fault, and in part (apparently) dpkg's -- if you do a --purge of an installed package, the package does not pass through the "removed ok conffiles-only" stage. Instead, despite the package payload being removed, the package is marked as still being installed, which is where all this grief comes from. > We need the buildd maintainers to all clean the chroots by hand Yes, but... > (perhaps it would be best to just rebuild them from scratch), I don't think that's necessary. Just apply the attached patch[1] in /var/lib/dpkg/info. > and then reschedule builds of xfree86. That part's necessary too. :) > Regardless of exactly what the correct procedure is, is there someone > who is taking the lead of making sure all this happens? More than a > few packages have gotten stalled by the corrupted chroots on the > buildd's causing spurious build failures and it needs by-hand work to > correct each one. Steve Langasek has been working with me and some of the buildd admins on this via IRC, but it is good to give this cleanup procedure broader exposure. [1] also available at http://redwald.deadbeast.net/tmp/xfree86-common_postrm_buildd_fix.diff > -- G. Branden Robinson| The software said it required Debian GNU/Linux | Windows 3.1 or better, so I [EMAIL PROTECTED] | installed Linux. http://people.debian.org/~branden/ | --- xfree86-common.postrm~ 2004-02-17 18:20:44.0 -0500 +++ xfree86-common.postrm 2005-02-19 14:07:19.323055852 -0500 @@ -599,7 +599,7 @@ if [ "$1" = "purge" ]; then - update-rc.d "$THIS_PACKAGE" remove + update-rc.d "$THIS_PACKAGE" >/dev/null remove for DIR in /etc/X11/Xresources /etc/X11/Xsession.d /etc/X11; do rmdir "$DIR" 2> /dev/null || true done signature.asc Description: Digital signature
Anyone want to make a Debian XDM login screen?
Wanted: Someone to follow the lead set at http://tr.ml.org/~tom/software/xdm/ and create a Debian XDM login screen featuring Mr. Blue-Eye or something. This would be great to have for 2.0, but that's probably not realistic, so it would probably go in 2.1. -- G. Branden Robinson | Reality is what refuses to go away when Purdue University | I stop believing in it. [EMAIL PROTECTED] | -- Philip K. Dick http://www.ecn.purdue.edu/~branden/ | pgprdZj5r1NQP.pgp Description: PGP signature
Re: Anyone want to make a Debian XDM login screen?
On Mon, Apr 13, 1998 at 02:09:43AM -0400, Steve Dunham wrote: > Some choices here are: > > 1) A modified version of xdm-external+gtkgreet (from the web site > mentioned earlier in this thread. [...] > They both would be easy, but with the first option I would be > concerned by the rapidly changing state of the gtk libraries. (Red > Hat is basing some gui apps on gtk, so users are unable to install > newer versions of the gtk libraries without breaking these apps.) One presumes that will stop very soon now. Both GTK+ and the GIMP are very, very close to a 1.0 release. For the GTK+, one can assume that the library interface will be stable for a while. Like I said, this is probably a 2.1 thing. 2.1 should be one hell of a release. I should (knock wood) have a lot of X issues ironed out by then; we'll have APT; we'll be moved to FHS; Mozilla, GTK+, GIMP, and GNOME will have been hacked on enough to make outsiders drool just by looking at them; etc. Who knows, kernel 2.2 may even be out by then. Quite a bit of change for a "minor" version increment. -- G. Branden Robinson | Kissing girls is a goodness. It is a Purdue University | growing closer. It beats the hell out [EMAIL PROTECTED] | of card games. http://www.ecn.purdue.edu/~branden/ | -- Robert Heinlein pgpZKl6vehwU2.pgp Description: PGP signature
Re: Anyone want to make a Debian XDM login screen?
On Mon, Apr 13, 1998 at 01:40:57PM +0200, Wichert Akkerman wrote: > Previously Branden Robinson wrote: > > Someone to follow the lead set at http://tr.ml.org/~tom/software/xdm/ > > and create a Debian XDM login screen featuring Mr. Blue-Eye or something. > > Perhaps we could use XDM-External for this? It allows you to use another > program instead of the default login widget. See the homepage for more info: > http://tr.ml.org/~tom/software/xdm/ Isn't that what I just suggested? -- G. Branden Robinson | Convictions are more dangerous enemies Purdue University | of truth than lies. [EMAIL PROTECTED] | -- Friedrich Nietzsche http://www.ecn.purdue.edu/~branden/ | pgpGpHugJXVFg.pgp Description: PGP signature
HELP WANTED with XFree86
A very skeletal, preliminary X Strike Force homepage is up. Later, the page will become prettier and I will flesh out my ideas for the XSF, but for now, with around 300 outstanding bugs, there are higher priorities. I have plenty on my own plate, but seven tasks I don't feel completely competent to do yet are listed. (The main reason being I simply haven't learned about certain things yet, like diddling with update-rc.d.) For now, I want to focus my efforts on things I *do* know how to fix, like manpages, breaking some stuff into a xserver-common package, and tackling the abominable keyboard issue with Christian Schwarz. Please, if anyone would like to see X get better any faster, take a look at this page and see if there's anything you can do. Failing that, if anyone would identify the X server package they use (especially s3 or s3v), bring up the bug list for that package, and see if any of the ancient bugs against that server have in fact been closed, or are no longer reproducible, please send me a report about that and I will close the bug. The URL for the X Strike Force is: http://master.debian.org/~branden/xsf.html -- G. Branden Robinson | There's nothing an agnostic can't do Purdue University | if he doesn't know whether he believes [EMAIL PROTECTED] | in it or not. http://www.ecn.purdue.edu/~branden/ | -- Graham Chapman pgp9123Kh0yM9.pgp Description: PGP signature
X Strike Force homepage up
It's still pretty skeletal as far as style of presentation goes, but that's subordinate to the content, which has been significantly updated. My ideas about what the X Strike Force is and what it should do are there. If anyone would like to help improve X, I urge you to take a look and see if there's a role you can fill. Some of the jobs will not be terribly difficult (like the X servers, which will mainly consist of reproducing old bugs); others will be more demanding. Anders Hammarquist and James Troup: I expect you in particular will each be interested in a couple of the roles available, but I don't want to volunteer you without your consent. Please check it out. http://master.debian.org/~branden/xsf.html -- G. Branden Robinson | The first thing the communists do when Purdue University | they take over a country is to outlaw [EMAIL PROTECTED] | cockfighting. http://www.ecn.purdue.edu/~branden/ | -- Oklahoma State Senator John Monks pgpmyD83YIPUE.pgp Description: PGP signature
xbase: xbase: fails to fail when told not to stop xfs/xdm
I think this is a bug in dpkg. When you answer "n" to that question about stopping xfs and xdm, the xbase preinst exits with a status of 1. There's really not much more the shell script can do. It's up to dpkg to interpret that as a failure and not go ahead with the package install (which it obviously did, as the message about methods of starting X is in xbase's postinst script). I am reassigning this bug to dpkg. -- G. Branden Robinson | We either learn from history or, Purdue University | uh, well, something bad will happen. [EMAIL PROTECTED] | -- Bob Church http://www.ecn.purdue.edu/~branden/ | pgpMoTneOzJ3S.pgp Description: PGP signature
Re: bzip2 for source packages?
On Sat, Apr 18, 1998 at 02:14:08PM -0400, Michael Alan Dorman wrote: > James Troup <[EMAIL PROTECTED]> writes: > > Having said that, I'm a lot less opposed to this idea than I am to the > > idea of using bzip2 for debs. > > Well, perhaps it would be nice to have it as an option for things > where either we can't use pristine source anyway, or those rare, but > often meaningful, occasions where it's supported upstream (linux > kernel, maybe xfree one day...). > > Besides, considering the glacial pace of dpkg development, you won't > have to take a decided stance any time soon. :-) It just so happens that with XFree86 we "can't use pristine source anyway". XFree86 source ships like the X source itself does -- in three chunks. It would probably make a lot of people very happy (including me) to bzip2 the Xfree86 source and/or binaries. -- G. Branden Robinson |One man's "magic" is another man's Purdue University |engineering. "Supernatural" is a [EMAIL PROTECTED] |null word. http://www.ecn.purdue.edu/~branden/ |-- Robert Heinlein pgp2IOdcDBPOi.pgp Description: PGP signature
Re: x 3.3.2-4
On Fri, Apr 24, 1998 at 12:25:56PM +0200, Michael Meskes wrote: > What happened? Were the files simply removed? I was just downloading them to > test the new version. Oops. Sorry, yes, they were, hence my "WITHDRAWN" message on debian-devel-changes. xbase-configure was stupidly broken. More ominously, xterm segfaults after it reads XKeysymDB. A gentleman on #debian moved in the 3.3.2-3 xterm and it worked, so one of the two patches that was applied to xterm broke things. Later today I will be investigating. Apart from those, the new package seemed to work all right, but I'm not letting anything with bugs that bad sit around with *my* name on it. :) The truly masochistic (with accounts on master) can get the stuff from /debian2/tmp/branden/ . The fixed xbase-configure script is in my home directory. Any one interested in helping with the postmortem on xterm is invited to dig through there. I will be making a few more changes and will rebuild and re-release -4 probably by Monday. Hopefully sooner. -- G. Branden Robinson | The first thing the communists do when Purdue University | they take over a country is to outlaw [EMAIL PROTECTED] | cockfighting. http://www.ecn.purdue.edu/~branden/ | -- Oklahoma State Senator John Monks pgptXbWk9602O.pgp Description: PGP signature
fakeroot and dpkg
Can someone explain the following message to me? dpkg-shlibdeps: warning: unable to find dependency information for shared library /usr/lib/libfakeroot/libfakeroot (soname 0, path /usr/lib/libfakeroot/libfakeroot.so.0, dependency field Depends) This is with fakeroot 0.0-10 and dpkg 1.4.0.22. -- G. Branden Robinson | Human beings rarely imagine a god that Purdue University | behaves any better than a spoiled child. [EMAIL PROTECTED] | -- Robert Heinlein http://www.ecn.purdue.edu/~branden/ | pgp4EKFhZtpYR.pgp Description: PGP signature
another question
I also got this warning, which makes me nervous. Anyone care to explain to me what is happening? dpkg-shlibdeps: warning: unknown output from ldd on `debian/tmp-xlib6/usr/lib/libc5-compat/libX11.so.6.1': ` ./debian/tmp-xlib6/usr/lib/libc5-compat/libX11.so.6.1 => ./debian/tmp-xlib6/usr/lib/libc5-compat/libX11.so.6.1 (0x4000b000)' -- G. Branden Robinson | Purdue University | Never attribute to malice that which can [EMAIL PROTECTED] | be adequately explained by stupidity. http://www.ecn.purdue.edu/~branden/ | pgpx80smTohU8.pgp Description: PGP signature
Re: X and Window Mangers
On Mon, Apr 27, 1998 at 11:11:12PM -0600, Jason Gunthorpe wrote: > I was just setting up a new install and ran into the problem of wmaker > configuring itself before /etc/X11/window-managers existed, it's postinst > bombed. > > I presume some X package creates this file since dpkg can't find it, this > also means that every window manager has a dependency on that package or > has a bug.. (APT likes to configure the window manager before x* without > a dependency to change that.) /etc/X11/window-managers is created in xbase's postinst iff the file does not already exist. Elimination of behavior like this is on my List. The long-term plan is: 1) ship an empty /etc/X11/window-managers with xbase 2) mark it as a conffile 3) separate twm into its own package 4) write /usr/sbin/register-window-manager register-window-manager [pathname] with no arguments, enters interactive mode with one pathname argument, invokes interactive mode with "add" action and pathname already done, thus prompting for priority (see below) register-window-manager --add pathname adds window-manager at pathname to bottom of list register-window-manager --remove pathname removes window-manager at pathname from list The interactive mode would display the non-comment contents of /etc/X11/window-managers prepended with numbers from 1 to n and prompt for an action (help, quit, add, remove, priority). The add command would prompt for a pathname and a priority (with a default of last), the remove command would prompt for a name (basename accepted if no collisions), the priority command would prompt for a name (basename accepted if no collisions) and a priority (with a default of current priority). I have no idea when I'll get around to actually writing this. I imagine it would have applicability beyond just this one configuration file. The non-interactive invocations are, of course, for use by window managers' maintainer scripts. I envision something like the following: window-manager-postinst: if [ $interactive = 1 ]; then # I assume we'll have this someday register-window-manager /usr/bin/X11/window-manager else register-window-manager --add /usr/bin/X11/window-manager fi window-manager-postrm: register-window-manager --remove /usr/bin/X11/window-manager Of course, all window managers will have to depend on xbase for this to work. Is there any reasonable scenario in which a user would have a window manager installed but not xbase? Comments very much welcome. -- G. Branden Robinson | I am sorry, but what you have mistaken Purdue University | for malicious intent is nothing more [EMAIL PROTECTED] | than sheer incompetence! http://www.ecn.purdue.edu/~branden/ | -- J. L. Rizzo II pgpgeIFTCukOf.pgp Description: PGP signature
Re: X and Window Mangers
On Tue, Apr 28, 1998 at 09:52:07AM -0400, Ben Pfaff wrote: >register-window-manager [pathname] > with no arguments, enters interactive mode > with one pathname argument, invokes interactive mode with "add" action > and pathname already done, thus prompting for priority (see below) > > Could we instead have a default priority assigned to each window > manager? So postinst scripts would run it like this: > >register-window-manager pathname priority > > and the script would add in the new window manager and report which > one currently has the highest priority. The sysadmin could still > start it in interactive mode to rearrange the priorities. Well, as said, everything will default to the bottom of the list (lowest priority). I don't think it will buy us very much for me to hard-code priorities for various window managers into register-window-manager, only to see the majority of users change them (as they should). "Externalizing" the standard priorities and having them passed to register-window-manager by the various WM's postinsts is A) too difficult to coordinate and B) wouldn't get us very much, I don't think. Remember, /etc/X11/window-managers is *only* used if the person using startx or logging in with XDM has no ~/.xsession file, which I image most experienced X users have. This file is just a way of letting the system administrator set defaults he or she considers sane. I don't think this is being needlessly interactive. If invoked as in my example (register-window-manager /usr/bin/X11/fvwm2, for instace), all the user has to do is press enter once. And until we get our magic "interactive" flag, we can of course default to the non-interactive behavior. -- G. Branden Robinson |One man's "magic" is another man's Purdue University | engineering. "Supernatural" is a [EMAIL PROTECTED] |null word. http://www.ecn.purdue.edu/~branden/ |-- Robert Heinlein pgpuD05H7D0hc.pgp Description: PGP signature
Re: X and Window Mangers
On Tue, Apr 28, 1998 at 11:19:36AM -0400, Ben Pfaff wrote: > Branden Robinson writes: > > The long-term plan is: > > > > 1) ship an empty /etc/X11/window-managers with xbase > > 2) mark it as a conffile > > 3) separate twm into its own package > > 4) write /usr/sbin/register-window-manager > >I don't think shipping an empty file, and marking it as a conffile, >would be interesting. If this file is going to be modified only by >the registering interface, then this should not be necessary. > > You also don't want to do this because dpkg will offer to replace your > populated /etc/X11/window-managers with an empty one, which would be a > Bad Thing (tm). Well, I only wanted to make it conffile so dpkg wouldn't overwrite it without prompting at all. The only alternative is not to ship a /etc/X11/window-managers file, but to conditionally create it in xbase's postinst. That means no package no package will claim knowledge of it, which I hate. Sounds like a job for "extrafiles". -- G. Branden Robinson | Purdue University | If God had intended for man to go about [EMAIL PROTECTED] | naked, we would have been born that way. http://www.ecn.purdue.edu/~branden/ | pgpdn6Tc1JORb.pgp Description: PGP signature
Re: X and Window Mangers
On Tue, Apr 28, 1998 at 04:23:34PM +0100, Mark Baker wrote: > > 1) ship an empty /etc/X11/window-managers with xbase > > 2) mark it as a conffile > > So you don't think other packages---such as the window managers---should > modify it? It's considered Bad Practice for a package to go about mucking with files belonging to another package. Providing a front end, as this suggestion does, is the preferred solution. -- G. Branden Robinson | A celibate clergy is an especially good Purdue University | idea, because it tends to suppress any [EMAIL PROTECTED] | hereditary propensity toward fanaticism. http://www.ecn.purdue.edu/~branden/ | -- Carl Sagan pgpnMaQND0N9w.pgp Description: PGP signature
Re: CERT* VB-98.04: Vulnerabilities in xterm and Xaw
On Tue, Apr 28, 1998 at 05:12:22PM +0100, Mark Baker wrote: > On Tue, Apr 28, 1998 at 05:57:55PM +0200, A Mennucc wrote: > > > > Vulnerabilities exist in the terminal emulator xterm(1), and the Xaw > > > library distributed in various MIT X Consortium; X Consortium, Inc.; > > > and The Open Group X Project Team releases. These vulnerabilities may > > > be exploited by an intruder to gain root access. > > > > the only solutions seems to > > > > chmod 0755 `which xterm` > > Or to apply a patch that TOG sent to their members, but didn't think to do > anything useful like include it in the alert itself. It's probably not free > anyway :( > > Since a program as complicated as xterm is always likely to contain security > problems, we probably should leave it un-suid anyway, even once we have > patched it to fix the bugs mentioned. Well, the reason xterm is setuid is because it needs privileged access to the utmp file. However, this is presently a problem under some circumstances (see bug #20685). XFree86 3.3.2-4 is shipping with an /etc/X11/XResources that sets XTerm*utmpInhibit to true. Is it the consensus of the project that xterm should have its setuid removed until this bug (#20685) is fixed? Let me know quickly (especially if any of you know any additional reason xterm is setuid). If I turn it off then I will want to do so for -5, which I'd like to release within the next 24 hours. -- G. Branden Robinson | Human beings rarely imagine a god that Purdue University | behaves any better than a spoiled child. [EMAIL PROTECTED] | -- Robert Heinlein http://www.ecn.purdue.edu/~branden/ | pgpqzrCw3bMya.pgp Description: PGP signature
Re: How Debian Linux could be made more secure
On Tue, Apr 28, 1998 at 04:50:45PM +0200, Thomas Roessler wrote: > First, the Debian Policy should be enhanced by a paragraph > on suid binaries. The policy should emphasize the least > privilege principle. It should require the use of > suidmanager when installing scripts suid root. > > Further, the policy should require maintainers to tag bug > reports about programs running suid root "critical". (You > may also consider to add an option to the bug program > which tags a bug report as a security problem, and thus > "critical". This is also interesting for network programs > which have security breaches and/or denial of service > vulnerabilities.) I thought we already addressed this somewhere, though if true it probably needs to me documented in a more conspicuous place. IIRC: root privilege exploits are severity "critical" user privilege exploits are severity "grave" denial-of-service attacks are severity "important" -- G. Branden Robinson | Measure with micrometer, Purdue University | mark with chalk, [EMAIL PROTECTED] | cut with axe, http://www.ecn.purdue.edu/~branden/ | hope like hell. pgpK7B1Ch8KG5.pgp Description: PGP signature
Re: How Debian Linux could be made more secure
On Tue, Apr 28, 1998 at 07:59:49PM +0200, Martin Schulze wrote: > I thought lintian already detects setuid binaries and needs > confirmation by the author that it needs to be setuser or > not. Yes, it does. -- G. Branden Robinson | The first thing the communists do when Purdue University | they take over a country is to outlaw [EMAIL PROTECTED] | cockfighting. http://www.ecn.purdue.edu/~branden/ | -- Oklahoma State Senator John Monks pgpsBVTq84KOr.pgp Description: PGP signature
Re: FWD: CERT Vendor-Initiated Bulletin VB-98.04 - xterm.Xaw
I have put some hopefully helpful information regarding this bug up on the X Strike Force page. http://master.debian.org/~branden/xsf.html -- G. Branden Robinson | The key to being a Southern Baptist: Purdue University | It ain't a sin if you don't get caught. [EMAIL PROTECTED] | -- Anthony Davidson http://www.ecn.purdue.edu/~branden/ | pgpGY1QODyEiw.pgp Description: PGP signature
The latest XFree86 (3.3.2-4)
Hi, folks, your friendly neighborhood X maintainer here. XFree86 3.3.2-4 just got installed into the archive today (I uploaded it Sunday). Unless you have bandwidth to spare, please don't download it without good reason. With impeccable timing, a CERT bulletin warning of possible security problems with xlib and xterm was released just after I finished -4, so -5 will be coming out very, very soon. Anybody interested in accelerating this process should see the X Strike Force page <http://master.debian.org/~branden/xsf.html>. -- G. Branden Robinson | Purdue University | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://www.ecn.purdue.edu/~branden/ | pgpYrIIkcUbsJ.pgp Description: PGP signature
Re: X and Window Mangers
On Tue, Apr 28, 1998 at 08:54:18PM -0400, Ben Pfaff wrote: >> Could we instead have a default priority assigned to each window >> manager? So postinst scripts would run it like this: >> >>register-window-manager pathname priority > >You know, this looks like a job for update-alternatives. Maybe we should >have a /usr/X11R6/bin/sensible-window-manager, or some such thing? > > Actually I like that a lot better myself. Could we do it that way > instead, Branden? Uh, I've never played with alternatives before. Would someone care to flesh out this proposal? Remember, twm will be a separate package in slink, and xbase will probably recommend the virtual package "window-manager", which all window managers will provide. -- G. Branden Robinson | If you wish to strive for peace of soul, Purdue University | then believe; if you wish to be a [EMAIL PROTECTED] | devotee of truth, then inquire. http://www.ecn.purdue.edu/~branden/ | -- Friedrich Nietzsche pgpNepldxlSv6.pgp Description: PGP signature
Re: X and Window Mangers
So I go to all the trouble of drafting a proposal for register-window-manager, and even start coding it, and you guys don't want to use it? *sigh* All right, if we can weather the inevitable religious flame war about which what the default priority for each window manager should be, I'll implement this solution. Less work for me, anyway. All I have to do is have /etc/X11/Xsession do this: if [ -x $startup ] && grep -q ^allow-user-xsession /etc/X11/config; then exec $startup else xterm -ls & if [ -x /usr/bin/X11/window-manager ]; then exec /usr/bin/X11/window-manager ] elif [ -x /usr/bin/X11/window-manager ]; then exec /usr/bin/X11/sensible-window-manager else xmessage -nearmouse -button "Quit X Windows" "No window manager installed!" fi fi -- G. Branden Robinson | A committee is a life form with six or Purdue University | more legs and no brain. [EMAIL PROTECTED] | -- Robert Heinlein http://www.ecn.purdue.edu/~branden/ | pgpbM6MejqVYb.pgp Description: PGP signature
Re: X and Window Mangers
On Wed, Apr 29, 1998 at 10:53:36AM +0100, Enrique Zanardi wrote: > (add a "xterm -sl 500 -sb -ls -fn 10x20 -j &" line before the exec if you Wow, that's a mighty Byzantine xterm line. But to each his own. :) -- G. Branden Robinson |If you make people think they're Purdue University |thinking, they'll love you; [EMAIL PROTECTED] |but if you really make them think, http://www.ecn.purdue.edu/~branden/ |they'll hate you. pgpQ9pVZIADen.pgp Description: PGP signature
Re: x 3.3.2-4
On Wed, Apr 29, 1998 at 02:06:55PM +0200, Remco Blaakmeer wrote: > Can you make that -5 so that those who did get the broken version will get > the right version? Releasing two different versions of a package with the > same release number is bad, IMHO, even if the first one was only available > for a very short time. Well, it's too late now, but -4 has been rendered undesirable anyway because of the CERT advisory (for which I still don't have fixes -- well, xterm should be okay thanks to Richard Braakman, but xlib6g still needs patching). Not to mention some small, annoying, idiotic bugs. I urge those who'd like to see -5 come out quickly to visit http://master.debian.org/~branden/xsf.html and see what you can do to help. -- G. Branden Robinson | Purdue University |Music is the brandy of the damned. [EMAIL PROTECTED] |-- George Bernard Shaw http://www.ecn.purdue.edu/~branden/ | pgpmhb6cwlDJl.pgp Description: PGP signature
Re: installation report of hamm 26.4.
On Wed, Apr 29, 1998 at 09:22:20PM +0200, Andreas Jellinghaus wrote:
> f) xserver offered my to "configure now". this failed, because not everything
> was installed, so it could not work.
Can you be more specific?
There is nothing in the xserver postinst that demands the presence of
xbase. I assume makedev and libc6 were installed and configured. Were
they? They're both essential, so I assume they must have been.
> h) xbase: some files were already there, but empty (Xserver). maybe this has
> todo with f). many people had problems with bo, when /etc/init.d/xdm
> did exist, but was empty, and they did not press "I" to replace it.
> now the same thing again ?
What version of xbase was this? Sounds like it must be 3.3.2-3 or earlier.
If /et/X11/Xserver was empty, how did your machine know to look for the
Mach64 server when starting X (below)?
> h) xserver installation. the user needs your help !
> i didn't know, what xserver i need, so i installed only vga16,
> so XF86Setup will tell me more. result : fatal.
> the first time it failed because mach64 server was not installed.
XF86Setup depends only on the VGA16 server. XFree86 3.3.2-4 always backs
up the /etc/X11/XF86ConfConfig file.
> this will confuse users !
> i suggest to do an appropiate "echo xserver-|dpkg
> --set-selection" call, save the default config, and ask the user
> to run dpkg again and continue later.
This is a very poor solution. I think 3.3.2-4 solves this.
> ok, so i had to care about this myself, and started xf86setup later again,
> doing the whole configuration again... this time i got :
>
> missing close-brace
> ("if" then script line 1)
> while compiling
> "if {![getline]} { ..."
> (file "/ ... /phase5.tcl" line 26)
> invoked within "source /.../phase5.tcl"
This is harmless (as you can see, the XF86Config file is created anyway),
but fixed in 3.3.2-4.
> XF86Config was written, but Xserver was not modified.
Xserver is not modified by XF86Setup, it is modified by the xserver package
postinst.
> xdm-start-server was not listed in /etc/X11/config.
> calling xbase-configure did not help. this script should assist the user in
> such stuff, because the debian way to do these things is only known to some
> hackers.
In XFree86 3.3.2-4, you may invoke /usr/sbin/xbase-configure with the
"force" argument.
XFree86 3.3.2-4 ships with xdm configured to start a local server, if the
user configures XDM to run at all.
> ok, at least xbase-configure changed the xdm/Xserver file, after i added
> the "xdm-start-server" line.
> btw: this seems to be redundant information to me.
All this is changed in XFree86 3.3.2-4. The xdm-start-server option has
been placed in limbo, and nothing edits /etc/X11/xdm/Xserver anymore; it
must be edited by hand. Detailed instructions are now inside that file to
facilitate the process.
--
G. Branden Robinson | If you wish to strive for peace of soul,
Purdue University | then believe; if you wish to be a
[EMAIL PROTECTED] | devotee of truth, then inquire.
http://www.ecn.purdue.edu/~branden/ | -- Friedrich Nietzsche
pgptdelocAqYq.pgp
Description: PGP signature
Re: xfsft deb package
On Thu, Apr 30, 1998 at 12:22:58AM +, Rev. Joseph Carter wrote: > On Thu, Apr 30, 1998 at 01:49:06AM +0200, Remco Blaakmeer wrote: > > If it is a patch to xfs that uses the freetype libs, I'd think it could be > > incorporated into the xfs that is in the xbase package, but I wouldn't > > care if it was implemented as a separate font server. Could you contact > > Branden Robinson <[EMAIL PROTECTED]> (the XFree86 maintainer) about this? > > Why is xfs in xbase at all? It's not required to use X. I would suggest > just pulling it out to its own package. I eventually plan to do this. See the X Strike Force page. http://master.debian.org/~branden/xsf.html -- G. Branden Robinson | When I die I want to go peacefully in Purdue University | my sleep like my ol' Grand Dad...not [EMAIL PROTECTED] | screaming in terror like his passengers. http://www.ecn.purdue.edu/~branden/ | pgpeFBO5F3yRh.pgp Description: PGP signature
Ease of use and configurability
Am I the only one who feels that, to a large extent, ease of use *is* a
technical problem?
This is a somewhat major proposal and would be a big piece of architecture
if implemented. However it's something I've been kicking around in my head
for months and I haven't yet come up with a good counter-argument.
I'll also be pretty surprised if something similar hasn't been proposed
*somewhere* before.
I note that on April 20th, the "Gnome System Control Panel Project" was
announced (see http://www.gnome.org). I think this is our opportunity to
work with its originator, Andy Doran, on making a consistent, easy, and
powerful interface for configuring programs.
My idea is this:
Every program that fetches user-modifiable files to control its behavior
(on a Debian system and according to the FHS, these should all be in /etc
or as dotfiles/dirs in $HOME) should have a kind an associated interface
file. Call it /usr/lib//gconfig or something.
Now bear with me as I'm probably about to abuse some terms from both compiler
and object theory.
Most configration files are reducible to key/value pairs (sometimes a key
word may take multiple values simultaneously, as in a list of pathnames),
or a list of grouped key/value pairs (/etc/passwd).
To handle this we need to define some primitive object types, like
boolean
file
directory (subtype of file)
device (subtype of file)
plainfile
... (you get the idea)
URI (Universal Resource Indicator, superset of URL's)
URL (thus, URL is a subtype of URI)
integer
string
Maybe URI should be a subtype of string...that's a technical decision. I'm
painting in broad strokes right now.
We must also allow the "interface" file to define its own object types.
For instance, /etc/password might do this; it is an aggregation of some of
the primitive data types mentioned above.
Some common methods should be written into the primitive objects (testing
for file not found in the file object, range checking in integer, illegal
character detection in string, etc.
We must also allow the "interface" file to override methods, and define new
ones of its own for existing objects and objects defined within that
interface file.
The bottom line:
For instance, an "interface" file for /etc/X11/xdm/config would work
something like this. Be aware that I am no parsing guru and am in no way
wedded to the syntactical appearance of this; I'm just trying to
communicate the concept.
# interface file for /etc/X11/xdm/config
defineproperty(boolean(scaled,label("Scaled"),style("yes","no))
definemethod(readscaling,subtype(read)) {
# read in line beginning with "catalogue"
# for each of the comma-delimited filenames
if (right(filename,9) = ":unscaled")
fontpath.scaled = false
else
fontpath.scaled = true
}
definemethod(writescaling,subtype(write)) {
if ! (fontpath.scaled) {
fontpath.value = fontpath.value + ":unscaled"
}
}
definetype(fontpath,subtype(directory),addproperty(scaled), \
addmethod(readscaling),addmethod(writescaling))
boolean(clone-self,label("Clone self"),style("on","off"))
boolean(use-syslog,label("Use syslog"),style("on","off"))
setof(fontpath(catalogue,label("Catalogue"))
plainfile(error-file,label("Error file"))
integer(default-point-size,label("Default point size"))
setof(integer(default-resolutions,label("Default resolutions"))
Okay, hopefully some of you will be able to get the gist of what I mean by
all of the above.
The great thing about this approach is that you can build a data structure
understood by gconfig internally, then hand this off to a desired
front-end (dumb,ncurses/slang/newt,gtk).
Would this be hard as hell to implement? Hell yeah, probably. But think
of the potential rewards. Once implemented, initially, package maintainers
would have to do the work of developing a thorough understanding of their
packages' config files. But once this thing catches on, upstream
maintainers may begin to show an interest.
Pipe dream, or can we make it real? Or does this suffer from some horrible
conceptual flaw that I haven't thought of?
I must also say that I am sure I do not have the coding expertise to
implement much of this at all. If I did, I'd be on it.
--
G. Branden Robinson | Never underestimate the power of human
Purdue University | stupidity.
[EMAIL PROTECTED] | -- Robert Heinlein
http://www.ecn.purdue.edu/~branden/ |
pgpB9vw3vWfBE.pgp
Description: PGP signature
Re: The latest XFree86 (3.3.2-4)
On Thu, Apr 30, 1998 at 10:17:27PM +0200, Alexander Shumakovitch wrote: > I'm not sure whether I want to spare my bandwidth, but I've installed 3.3.2-4 > version (just because dselect wanted to do this and I was too lazy to > contradict). And now all my xterms have a totally black background. Is it to > warn about the security problem or just that security problem itself? :-) > Anyway, I was unable to find out how to return my standard (light gray?) > background back. /usr/X11R6/lib/X11/app-defaults/XTerm is identical to the > previous one. If it's a bug, just consider this message as a bug-report, but > if it's a feature, I would appreciate very much knowing how to get rid of it. Well, firstly, you should not mess with /usr/X11R6/lib/X11/app-defaults/XTerm. /usr/doc/X11/README.Debian says as much. What is just as effective is editing /etc/X11/Xresources. There you will see that I changed the default foreground and background colors so that programs using ANSI color will look like they do at the virtual console. You may change the defaults herre. The changelog documents this, though I'll understand if your eyes sort of glazed over when reading the it. :) > I also had the following problems with installation: > 1) xserver-svga post-install script produced some strange error (sorry, I > didn't pay attention to this at that time and ignored it), and I've lost my > /etc/X11/Xserver file. It was easy to reconstruct it from Xserver.dpkg-new, > though. Yeah, this was a dumb bug in xserver-postinst, and a fix is in place for -5. > 2) xauth produced an error on startup the following error: > > xauth: (argv):1: bad display name "blackshark." in "add" command > (blackshark is a host name). But this one was easy to fix also (just to change > the corresponding line in startx script). Ditto. This time the dumb bug was in programs/xinit/startx.cpp. -- G. Branden Robinson | It was a typical net.exercise -- a Purdue University | screaming mob pounding on a greasy spot [EMAIL PROTECTED] | on the pavement, where used to lie the http://www.ecn.purdue.edu/~branden/ | carcass of a dead horse. pgp64OjF4rMAv.pgp Description: PGP signature
Re: Ease of use and configurability
On Fri, May 01, 1998 at 12:57:24AM +0200, Marcus Brinkmann wrote: > Great, I did it wrong... should go to bed. Anyway, here is the errata: > > > 1) There was a very long discussion on debian-admin (I can send it to you, > > Obviously, this should be debian-admintool. Okay. I was unaware of that list. We have a lot of them. > > 2) The KDE (and Gnome) approach of several little config programs will not > > work, > > Obviously, this was not what Branden suggested. Well, perhaps someone should become a liaison between the Gnome Control Panel person and COAS. As long as COAS has the power and flexibility I want, then I'm cool with it. My idea was very abstract, I hadn't written any code yet. :) -- G. Branden Robinson | To stay young requires unceasing Purdue University | cultivation of the ability to unlearn [EMAIL PROTECTED] | old falsehoods. http://www.ecn.purdue.edu/~branden/ | -- Robert Heinlein pgpC7LH0SYBs3.pgp Description: PGP signature
Re: Intent to package: debian-keyring
On Mon, Apr 20, 1998 at 03:57:27PM -0400, Dale Scheetz wrote: > On 20 Apr 1998, Manoj Srivastava wrote: > > By the way, I do not think I am alone in regarding the Policy > > as a standards document; a quick (informal) poll on IRC showed a > > wider accord (for what it counts for). > > > Folks with time on their hands tend to support measures that control the > group for the betterment of all without reguard to the desirablility of > such controls by those who have it imposed upon them. (sorry for the > tangled sentance) Dale, there are plenty of hard-working Debian folks who spend time in the IRC channel. Richard Braakman, Manoj, Joey Schulze, Joey Hess, Jason Gunthorpe, Ray "JHM" Dassen, Igor Grobmann... I know I'm forgetting several -- no denigration of their hard work is intended. I think you are mischaracterizing the developers who utilize the IRC channel, and it does not strengthen your argument. To what extent the policy manual should be a "guideline", and to what extent it should be a "standard", is an issue to which IRC has no relevance. -- G. Branden Robinson | We either learn from history or, Purdue University | uh, well, something bad will happen. [EMAIL PROTECTED] | -- Bob Church http://www.ecn.purdue.edu/~branden/ | pgpGIm5bD0nAL.pgp Description: PGP signature
Re: dists/{bo,stable} temporarily unavailable
On Mon, Apr 20, 1998 at 02:38:59PM -0600, Jason Gunthorpe wrote: > If anyone is using apt to access the archive then you will have to remove > the line with stable. If you have a special reason for access to stable > (right now the feature is not used) then you can put something like > > deb http://.../Debian stable/binary-i386/ > deb http://.../Debian non-free/binary-i386/ > > etc. (note the trailing slash) > > This is documented in sources.list(5) Whee! My manpage is actually good for something! -- G. Branden Robinson | If you wish to strive for peace of soul, Purdue University | then believe; if you wish to be a [EMAIL PROTECTED] | devotee of truth, then inquire. http://www.ecn.purdue.edu/~branden/ | -- Friedrich Nietzsche pgpaOyGYxlaT1.pgp Description: PGP signature
Re: interest in xfstt package
On Mon, Apr 20, 1998 at 10:16:29PM -0400, Stephen Carpenter wrote: > About 10 mins ago I posted a message to the debian-user list in a > discussion of this package xfstt. The reason being that the package > needs some work and I also have noticed it on the list of "Packages > needing a new maintainer" That is why I am writting you now (and > cc:ing debian-devel because I would like to get some more opinions > on this) I fount xfstt a while back anbd love it...I think what it > does is great (even if it is limited by the moronic copyrights on > most fonts :( ) I am interested in volunteering some of my time and > giving back to the Linux (and more specifically now debian) community, > and am wondering if possibly you might think xfstt would make a good > package to start with since I have never workerd on a package before. > Yes I have read all of the documentation, the policy manual and all > of that on the web page...and looked over a few times the packageing > manual (need to play with it some more :) ) I am a little afraid of > this...im unsure of my abilities I have fooled around with C for > about 4 or 5 years and done some C++...playe dwith shell scripts and > perl I admit I am unsure of what this will involve and the amount of > work it requires... but one of the main reasons I use linu xin the > first place is I want to learn...so I supose thats not entirely bad > so im wondering what you (and others on debian-devel) think does this > package seem like a bit much for a first package? if not...what do I > do next (yes I read all of the info on how to get started but...that > confused me just a bit... course thats probbaly just me :) ) Well, I'd like to invite you to join, or at least be in contact with, the X Strike Force <http://master.debian.org/~branden/xsf.html> and me in particular. I'd like to learn more about xfstt and what I can do to make sure it integrates smoothly with X. After hamm is released I'm going to be re-engineering XFree86 a bit. An xserver-common package will be created, and xbase will be further segregated. I know it's a terrible thing to break X into even more binary packages, but I think things like xfs and xdm need to be split off, especially as they are targets for replacement on some systems. -- G. Branden Robinson | Somebody once asked me if I thought sex Purdue University | was dirty. I said, "It is if you're [EMAIL PROTECTED] | doing it right." http://www.ecn.purdue.edu/~branden/ | -- Woody Allen pgpcd6Qfo13K7.pgp Description: PGP signature
Re: Bug#302138: incorrect Description line wrapping with bullet lists
On Wed, Mar 30, 2005 at 03:54:36AM -0600, Peter Samuelson wrote: > [Peter Samuelson] > > I'd like to file a mass bug for these, but it's on the order of 583 > > binary packages in 430 source packages, so I obviously want to get > > some feedback first. > > Jeroen van Wolffelaar pointed out to me that 430 source packages is a > bit much for a mass bug, especially if lintian/linda could flag this > stuff automatically, which is probably the case. > > Lars Wirzenius also suggested that I name names so people will know if > they're affected. So here are source packages grouped by maintainer. > Data is from /var/lib/apt/lists/*_Packages on an i386 sid box. [...] > Branden Robinson <[EMAIL PROTECTED]>: > twofish Go ahead and file a bug for this one, please -- twofish sees so little activity that I'm likely to forget to fix this, and having an open bug report against it will remind me to start maintaining the package from a Subversion repository. Thanks for helping to make our package descriptions something we can be proud of! -- G. Branden Robinson| Debian GNU/Linux |Yeah, that's what Jesus would do. [EMAIL PROTECTED] |Jesus would bomb Afghanistan. Yeah. http://people.debian.org/~branden/ | signature.asc Description: Digital signature
Re: Debian Project Leader report for 2005-04-24
On Mon, Apr 25, 2005 at 01:45:52PM +0200, Josselin Mouette wrote: > Le lundi 25 avril 2005 à 01:03 -0500, Branden Robinson / Debian Project > Leader a écrit : > > Woody Security Update Challenges and Progress > > - > > The ARM problems we've had have also affected the timeliness with which > > we've been able to get security updates out. A security fix to > > ``xfree86``, for example, has been stalled for weeks because no ARM > > build daemon has been operational to compile it. (See `Debian bug > > #298939`_ for details.) > > Why, in this case, isn't the package released for the other > architectures? There's nothing wrong with sending an update later for > architectures that were missing in the first run. I don't have an answer for this. My guess is that the Security Team decided delaying the update was the lesser of two evils. Security folks, would you care to comment? In any event, we have recovered from the ARM situation (and xfree86 for stable/arm is built for it), and you can expect some happy details in my next DPL report. -- G. Branden Robinson| The power of accurate observation Debian GNU/Linux | is frequently called cynicism by [EMAIL PROTECTED] | those who don't have it. http://people.debian.org/~branden/ | -- George Bernard Shaw signature.asc Description: Digital signature
Re: Ongoing Firefox (and Thunderbird) Trademark problems
On Tue, Jun 14, 2005 at 01:38:53PM +0100, Matthew Garrett wrote: > Julien BLACHE <[EMAIL PROTECTED]> wrote: > > > Their trademark policy is something that should not exist in a free > > software context. They don't care about free software. They don't care > > about distributors/vendors. > > What is DFSG 4 if not a grudging acceptance of this sort of behaviour as > free? Integrity of The Author's Source Code The license may restrict source-code from being distributed in modified form _only_ if the license allows the distribution of "patch files" with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software. (This is a compromise. The Debian group encourages all authors not to restrict any files, source or binary, from being modified.) The point of DFSG 4, as I understand it, is to permit the licensor to take certain explicit steps to prevent people from drawing the inference that the licensor endorses modified versions in any way. I think if DFSG 4 had intended to grant licensors broad latitude to invent novel ways of prevent such an inference from being drawn, it would have been worded differently -- or, at least, the last two sentences would have been. In my opinion, DFSG 4 somewhat clumsily lumps together two related but distinguishable issues -- one is a presentation format for distribution, the other is a means for the work to identify itself. -- G. Branden Robinson| Religious bondage shackles and Debian GNU/Linux | debilitates the mind and unfits it [EMAIL PROTECTED] | for every noble enterprise. http://people.debian.org/~branden/ | -- James Madison signature.asc Description: Digital signature
Re: Editing history... (about debian/changelog in experimental)
On Wed, Jan 12, 2005 at 07:13:57PM +0100, Jeroen van Wolffelaar wrote: > Branden Robinson told me that he does changelog editing of past > revisions continuously for X, for reasons of being able to correctly > lookup when a certain bug was fixed. Especially typo's in bugnumber for > example can make a changelog quite useless if I want to determine when a > certain bug was fixed, and a correct changelog makes it very easy to > close bugs that were fixed some time ago by quoting the relevant > changelog entry. That's correct. The purpose of the changelog is to document history[1], not be an indelible document. We'd all prefer to document history accurately the first time around, and we should take care to do so, but we do make mistakes from time to time. I did maybe feel a bit more strongly about indelible changelog entries a couple of years back (and longer) before I even kept the XFree86 packages in revision control, though I don't think I was ever quite the hard-liner that some people are. Again, the fundamental question is: does the changelog entry in question document history as accurately as it can? If so, leave it alone. If not, and the inaccuracy is likely to mislead people, fix it. Similarly, it is not the job of a changelog entry to document things that aren't changes (as evidence that people will behave more absurdly than you can at first believe, I offer [2]). IMO, the Policy Manual should countenance retroactive modification of changelog entries under such circumstances. [1] ...with a secondary function of automatically closing bugs. [2] Message-id: <[EMAIL PROTECTED]> http://lists.debian.org/debian-devel/2004/03/msg01377.html -- G. Branden Robinson| There's nothing an agnostic can't Debian GNU/Linux | do if he doesn't know whether he [EMAIL PROTECTED] | believes in it or not. http://people.debian.org/~branden/ | -- Graham Chapman signature.asc Description: Digital signature
Re: static user IDs
On Tue, Sep 21, 1999 at 10:15:10AM +0200, Tomasz Wegrzanowski wrote: > Who will agree with me that > qmail[dsrqlp] should be forbidden > Their existance in /etc/passsd rape me thru my eyes > 6 statics for pacage is a bad idea but > if this package isnt even free they should be > thown out without mercy I nominate this guy for Debian's Most Promising Newcomer Award. :) -- G. Branden Robinson | "Why do we have to hide from the police, Debian GNU/Linux | Daddy?" [EMAIL PROTECTED] | "Because we use vi, son. They use cartoon.ecn.purdue.edu/~branden/ | emacs." pgpSrL53lQXks.pgp Description: PGP signature
Re: Add your location to the developer db so it can be added to the map
On Wed, Sep 22, 1999 at 01:26:19PM -0400, James A. Treacy wrote: > Check out the new map showing developer locations: > http://www.debian.org/devel/developers.map.jpg Nifty! However I must decry the foul and evil file extension JPG and request that JPEG be used instead. This ain't DOS. > The marker file used to generate this can also be viewed: > http://www.debian.org/devel/developers.coords Hmm. I get a 404 on this. Great work, thanks to everyone responsible for this, it is cool. We probably should whack the old xearth stuff from the site now. -- G. Branden Robinson | Human beings rarely imagine a god that Debian GNU/Linux | behaves any better than a spoiled child. [EMAIL PROTECTED] | -- Robert Heinlein cartoon.ecn.purdue.edu/~branden/ | pgptwHD2P8EA5.pgp Description: PGP signature
possible problem with new perl, libc6 on Sep 23rd
e providing pl2pm (/usr/bin/pl2pm) removed, deleting it. Checking available versions of splain, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link splain.1p.gz (/usr/man/man1/splain.1p.gz). Last package providing splain (/usr/bin/splain) removed, deleting it. Checking available versions of perlcc, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Last package providing perlcc (/usr/bin/perlcc) removed, deleting it. Checking available versions of s2p, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link s2p.1p.gz (/usr/man/man1/s2p.1p.gz). Last package providing s2p (/usr/bin/s2p) removed, deleting it. Checking available versions of find2perl, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Last package providing find2perl (/usr/bin/find2perl) removed, deleting it. Checking available versions of pod2man, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link pod2man.1p.gz (/usr/man/man1/pod2man.1p.gz). Last package providing pod2man (/usr/bin/pod2man) removed, deleting it. Checking available versions of pod2html, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link pod2html.1p.gz (/usr/man/man1/pod2html.1p.gz). Last package providing pod2html (/usr/bin/pod2html) removed, deleting it. Checking available versions of pod2latex, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Last package providing pod2latex (/usr/bin/pod2latex) removed, deleting it. Checking available versions of pod2text, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link pod2text.1p.gz (/usr/man/man1/pod2text.1p.gz). Discarding obsolete slave link Pod::Text.3pm.gz (/usr/man/man1/../man3/Pod::Text.3pm.gz). Last package providing pod2text (/usr/bin/pod2text) removed, deleting it. Checking available versions of pstruct, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link pstruct.1p.gz (/usr/man/man1/pstruct.1p.gz). Last package providing pstruct (/usr/bin/pstruct) removed, deleting it. Checking available versions of rename, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Discarding obsolete slave link rename.1p.gz (/usr/man/man1/rename.1p.gz). Last package providing rename (/usr/bin/rename) removed, deleting it. Checking available versions of cperl-mode.el, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Last package providing cperl-mode.el (/usr/share/emacs/site-lisp/cperl-mode.el) removed, deleting it. Unpacking replacement perl-5.005 ... Replacing files in old package perl-5.005-base ... Preparing to replace perl-5.005-base 5.005.03-3 (using /var/cache/apt/archives/perl-5.005-base_5.005.03-4_i386.deb) ... Checking available versions of perl, updating links in /etc/alternatives ... (You may modify the symlinks there yourself if desired - see `man ln'.) Last package providing perl (/usr/bin/perl) removed, deleting it. Unpacking replacement perl-5.005-base ... Preparing to replace libc6-dev 2.1.2-2 (using .../libc6-dev_2.1.2-3_i386.deb) ... Unpacking replacement libc6-dev ... Preparing to replace gconv-modules 2.1.2-2 (using .../gconv-modules_2.1.2-3_i386.deb) ... Unpacking replacement gconv-modules ... Preparing to replace libc6 2.1.2-2 (using .../libc6_2.1.2-3_i386.deb) ... Unpacking replacement libc6 ... Setting up libc6 (2.1.2-3) ... Current default timezone: 'US/Eastern'. Local time is now: Thu Sep 23 22:03:13 EDT 1999. Universal Time is now: Fri Sep 24 02:03:13 UTC 1999. Run `tzconfig' if you wish to change it. /var/lib/dpkg/info/libc6.postinst: /usr/sbin/update-rc.d: Permission denied dpkg: error processing libc6 (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: libc6 E: Sub-process returned an error code (1) [...later...] [1] 1013 apocalypse ~ > ls -dl /usr/bin/perl lrwxrwxrwx 1 root root 10 Sep 23 22:02 /usr/bin/perl -> perl-5.005 [0] 1014 apocalypse ~ > ls -dl /usr/bin/perl-5.005 -rw--- 1 root root 534844 Aug 19 04:29 /usr/bin/perl-5.005 -- G. Branden Robinson | "I came, I saw, she conquered." The Debian GNU/Linux | original Latin se
Re: Conference! - around the world with Debian
On Fri, Sep 24, 1999 at 04:26:27PM +0200, Sven LUTHER wrote: > Also use of computer in planes is discouraged and prohibited during landfall > and takeoff, as it interfer with the onboard radio equipement ... This is a fiction perpetrated by flight attendants because many of them are too dumb to tell the difference between electronic devices that may generate significant EMF at 108MHz or a little above and ones that don't. Hint: if it's got an FCC sticker on it, it's okay. The FCC is so ubelievably anal about radio transmissions, nothing they license could come close to interfering with a receiver even 10 feet away. But the airlines don't expect flight attendants to comprehend such things and don't have to, since their passengers don't raise enough fuss to get the policy changed. As portable computing devices become ever more ubiquitous, this may change. -- G. Branden Robinson | The only way to get rid of a temptation Debian GNU/Linux | is to yield to it. [EMAIL PROTECTED] | -- Oscar Wilde cartoon.ecn.purdue.edu/~branden/ | pgpAybQyVRk3J.pgp Description: PGP signature
Re: Conference! - around the world with Debian
On Sat, Sep 25, 1999 at 11:08:37AM -0400, James A. Treacy wrote: > > Well, this is completely off-topic, but I wouldn't be so sure. > > I have plenty of electronic equipment here which generates an awful > > lot of interference to my sensitive radio receivers. Switch-mode > > power supplies in particular (although passengers won't be using > > those on the plane). > > > This is common. The problem is that while FCC requirements are quite > high, manufacturing standards are not, causing an awful lot of > equipment out there to create interference. But the FCC are particularly crazy paranoid about interference in the radio band. Mind you, I'm not cheering for the FCC here -- in fact that I think their restrictions on output power for private radio transmitters are hideously excessive -- but they do seem to keep a pretty tight lid on RFI generated by portable devices. Household appliances, on the other hand... -- G. Branden Robinson | Debian GNU/Linux |Please do not look directly into laser [EMAIL PROTECTED] |with remaining eye. cartoon.ecn.purdue.edu/~branden/ | pgpiv2fqJar7l.pgp Description: PGP signature
Hysterical Onanistic ITP's (was: ITP: Country Codes)
On Sun, Sep 26, 1999 at 03:01:22AM +0900, Keita Maehara wrote: > Country Codes is an ISO 3166 country code finder. I'll upload it as > "countrycodes". Here is some example output: > > % iso3166 -d ftp.chiark.greenend.org.uk > > Domain name : ftp.chiark.greenend.org.uk You don't need to echo back the input argument, the user knows it already. > Top domain : uk (Great Bretain (iso 3166 code is gb)) This seems to be the only useful part of the output. The output format is all wrong, however. Anyone familiar with the Internet host namespace knows that .uk is the top-level domain because it is the last component of the hostname. Again, you're telling the user something they already know. You misspelled "Britain". Is it misspelled that way in the ISO 3166 text file that ships with libc6? Did you know an ISO 3166 table ships with libc6? The nested parentheses are also a bad idea for automated parsing reasons. > Sub domain #1: org (Organizations) > Sub domain #2: greenend (Unknown) > Sub domain #3: chiark (Unknown) > Sub domain #4: ftp (File Transfer Protocol) There is no way you can know the meanings of the names of all possible subdomains. It looks like you're destined to hardcode a massive table which will be staggeringly daunting to update and which will be necessarily doomed to fall out of date. > % iso3166 jp > > Country 2 letter 3 letter Number > - > Japanjp jpn 392 This output is needlessly dressy. It looks like a DOS program. Remember one of the core design principles of Unix is for the output of one program to be easily manipulated by another. Finally, I must question the utility of this program altogether. Fundamentally, it tells us nothing useful that grep UK /usr/share/zoneinfo/iso3166.tab does not. At the risk of starting another flamewar or being called some kind of cultural chauvinist, this isn't the first program I've seen from .jp that has big flaws like this. Many Japanese programmers seem to be utterly unaware of many of the Unix idioms, reinventing the wheel over and over again, and usually with ugly output formats (to spread blame a little more evenly, dpkg -l is just as awful in this regard and I really hope our Japanese brethren aren't using it as an example). To be fair, there is plenty of that among "Western" programmers as well; freshmeat is rife with programs that have been done before, better, and just as freely licensed. But I do not see the debian-devel list bombarded with ITP's of these marginal toys. I really wish we could get this psychotic ITP obsessiveness under control. Before posting an ITP, usually with a comment like "I'll upload this tomorrow", why not ask the development community of such a tool is truly needed? Why not take a look around the existing distribution, which is very large, and see if something that can do the job is already present? -- G. Branden Robinson | Debian GNU/Linux | It tastes good. [EMAIL PROTECTED] | -- Bill Clinton cartoon.ecn.purdue.edu/~branden/ | pgprrIapNJF5t.pgp Description: PGP signature
Re: Hysterical Onanistic ITP's (was: ITP: Country Codes)
On Sun, Sep 26, 1999 at 02:21:52PM +0900, Keita Maehara wrote:
> Country Codes is not a program developed by a Japanese programmer. I
> used "jp" just as an example. I hope someone won't call you "some
> kind of cultural chauvinist" :).
Okay, then feel free to heap all my scorn and derision on whoever deserves
it. I'm an equal-opportunity jerk, and I pay no heed to anyone's
nationality, race, creed, color or religion. :)
In my own defense, I do remember some package straight from the Debian-JP
project with a textual output format that made me recoil in horror. I
didn't speak up about it at the time and of course I can't remember what it
was now.
> > I really wish we could get this psychotic ITP obsessiveness under control.
>
> Perhaps it should be under some kind of control, but I don't know
> that's a good idea or not. Currently we have only a rough, or natural
> consensus.
Well, we do see lots of ITP's with only a day or two's notice before upload
to the archives. The Debian-JP team are hardly the only ones guilty of
that, though. (On the other end of the spectrum are the people who post
ITP's before they've even *started* work on a package, and it is literally
months before it ever shows up.)
Perhaps we should start an informal mechanism of "seconding" ITP's?
Give a package a week or so to garner three "seconds". A heck of a lot of
people read -devel and it shouldn't be hard for truly useful packages to
muster that relatively small amount of support.
> There might be a strong objection from others too, so I'll withdraw
> this ITP for now, not because it's useless but I have much more work
> (not so much as you though) to do for Debian other than flamewar.
>
> Finally, from upstream README:
>
> | I am lazy to hold all the ISO 3166 in my mind, or to grep it from a file,
> | it's too much work :)
It is so darn easy to grep /usr/share/zoneinfo/iso3166.tab that I must take
exception to that reasoning.
I can understand someone not wanting to type all that, but it would really
be cake to write a shell alias or function that can accomplish the same
thing.
iso3166 () {
grep -i ^$1 /usr/share/zoneinfo/iso3166.tab;
}
--
G. Branden Robinson | "Why do we have to hide from the police,
Debian GNU/Linux | Daddy?"
[EMAIL PROTECTED] | "Because we use vi, son. They use
cartoon.ecn.purdue.edu/~branden/ | emacs."
pgpIDajD1E5WA.pgp
Description: PGP signature
Re: Conference! - around the world with Debian
On Sun, Sep 26, 1999 at 09:04:46PM +1000, Hamish Moffatt wrote: > On Sat, Sep 25, 1999 at 10:57:31PM -0400, Branden Robinson wrote: > > Mind you, I'm not cheering for the FCC here -- in fact that I think their > > restrictions on output power for private radio transmitters are hideously > > excessive -- [snip] > > Really? I don't consider the 1.5kW limit for US amateurs > excessively limiting :-) Down here in Australia we are only allowed 400W. I said private, not licensed or otherwise fooled with. The limit for completely laissez faire use appears to be about 10mW. That is six orders of magnitude less than the figure you quote. -- G. Branden Robinson | Debian GNU/Linux | Mob rule isn't any prettier just because [EMAIL PROTECTED] | you call your mob a government. cartoon.ecn.purdue.edu/~branden/ | pgp1CzVfzj8ah.pgp Description: PGP signature
Re: [RHSA-1999:035-02] Updated XFree86 3.3.5 packages available
My apologies if you replied to the mail quoted below; I never received one. As far as I can tell, Red Hat's webpages have not been updated with the corrected information. Are there any plans to do so? On Mon, Sep 20, 1999 at 12:30:04AM -0400, branden wrote: > Hi Preston, > > In Red Hat's recent announcement, there is the following text: > > > Thanks go to Branden Robinson <[EMAIL PROTECTED]> for discovering a > > possible symlink attack in the xkb extension initialization at server > > startup time. > > I appreciate the mention, but I cannot claim credit for having discovered > this vulnerability. Credit for that, as far as I know, goes to Olaf Kirch > <[EMAIL PROTECTED]>, who announced it to the vendor-sec list. > > I did, however, author the fix, which was accepted into the XFree86 source > tree upstream and which I mailed to you. -- G. Branden Robinson | Debian GNU/Linux | Music is the brandy of the damned. [EMAIL PROTECTED] | -- George Bernard Shaw cartoon.ecn.purdue.edu/~branden/ | pgpH6G0QmzqUj.pgp Description: PGP signature
Re: ITP: actx
On Fri, Oct 01, 1999 at 07:16:37PM +0900, Kenshi Muto wrote: > Package: actx > Version: 0.98pre8-2 You do realize that dpkg treats "0.98" as less than "0.98pre8", don't you? > Section: x11 This should probably go in "games" or maybe "graphics" depending on what a "window sitter" is. > Description: A Window Sitter Program on X > ActX is a window sitter program to make your life with X rich and > fruitful. It supports a helpful pop-up menu to modify configuration of > animation and more. Originally inspired with XAyanami, another window > sitter. The second, third, and fourth lines of the extended description should be indented one space. Also, the description doesn't actually tell me much. What is a "window sitter"? A baby sitter for windows? I do not understand. "to make your life with X rich and fruitful" either sounds like a joke or very bad advertising. If it is the latter it has no place in the package description, which needs to be informative. Instead of that second sentence, I would say "Animation and other configuration is done with a pop-up menu." "Originally inspired with" should probably be "Originally inspired by". But the most important thing is to tell the user what a "window sitter" is. I think I'm up on my jargon, but I don't know what you're talking about here. -- G. Branden Robinson | If you wish to strive for peace of soul, Debian GNU/Linux | then believe; if you wish to be a [EMAIL PROTECTED] | devotee of truth, then inquire. cartoon.ecn.purdue.edu/~branden/ | -- Friedrich Nietzsche pgpi0eaMfd9G0.pgp Description: PGP signature
Re: recompile needed for xlib6g (>= 3.3.5-1) instead of (>= 3.3.2.3a-2) ?
On Tue, Oct 05, 1999 at 11:43:14AM +0200, Santiago Vila wrote: > On Fri, 1 Oct 1999, Peter S Galbraith wrote: > > Should I rebuild the i386 binaries with the new xlib6g-dev > > and upload them with .0.1 version number suffix? Or perhaps it > > doesn't matter? > > As far as xlib6g is concerned, I don't think it does matter. But it might. There *have* been changes to the libraries between 3.3.2.3 and 3.3.5. No, I don't think any interfaces have changed. But just to err on the side of caution, would anyone doing what Santiago is doing PLEASE recompile their packages against the latest versions of the potato libraries shortly before the potato freeze? Mixed slink/potato systems are temporary things. Potato will be around for a long time. So let us please make it internally consistent. -- G. Branden Robinson | One man's theology is another man's Debian GNU/Linux | belly laugh. [EMAIL PROTECTED] | -- Robert Heinlein cartoon.ecn.purdue.edu/~branden/ | pgpZYewiWNMsA.pgp Description: PGP signature
Re: Consistant Keyboard Configuration (was Re: Another packages wishlist)
On Tue, Mar 07, 2000 at 04:40:12PM +, Jules Bean wrote: > The problem in fact turned out to be that the stuff in > /etc/X11/Xsession which groks the /etc/X11/Xresources directory is > relatively new, ^^ Time to break out the flashlights and the moving trains. This transition occurred over a year ago. > and my /etc/X11/Xsession had been diverted by some > copy of kdebase which I installed a while ago, and had long since > purged (but it naughtily didn't clean up the diversion in the removal > scripts). Another reason why kdm should be split from kdebase, and another reason people should be assiduous about filing bugs against the KDE packages. -- G. Branden Robinson| We either learn from history or, Debian GNU/Linux | uh, well, something bad will happen. [EMAIL PROTECTED] | -- Bob Church roger.ecn.purdue.edu/~branden/ | pgpirzTpnEL5i.pgp Description: PGP signature
Re: Packages to remove from frozen
On Tue, Mar 07, 2000 at 11:26:12PM -0500, Michael Stone wrote: > How is it right to spit out an error message on every connection that > adds nothing to most people's use of the product? Especially when there > exists a verbose mode for people who want lots of gory details about the > efficacy of their connection? SSH doesn't tell me the key length of > connections *except* in this one case--which is not consistent, and > which is not unambiguously "*right*" behavior. I disagree with your analysis, but nevertheless... Use the Source, Luke. Quit whining and start coding. -- G. Branden Robinson|A celibate clergy is an especially good Debian GNU/Linux |idea, because it tends to suppress any [EMAIL PROTECTED] |hereditary propensity toward fanaticism. roger.ecn.purdue.edu/~branden/ |-- Carl Sagan pgpZfjGUNDsxY.pgp Description: PGP signature
Re: Ghostscript 6.0
On Wed, Mar 08, 2000 at 05:25:42PM +0100, Torsten Landschoff wrote: > On Tue, Mar 07, 2000 at 08:19:47AM -0500, Branden Robinson wrote: > > > As I understand it, pdftotext is a new tool available in 5.5 but not 5.0. > > AFAIK pdftotext is included in xpdf - it's not part of gs 5.5. The differences > between 5.10 and 5.50 are not that big and I do not want to risk a stable > package just for being up to date. Eh? There would be no real code changes at all. As I understand it, the license on 5.5 is all that has changed. So why not move it from non-free to main for potato? -- G. Branden Robinson| The first thing the communists do when Debian GNU/Linux | they take over a country is to outlaw [EMAIL PROTECTED] | cockfighting. roger.ecn.purdue.edu/~branden/ | -- Oklahoma State Senator John Monks pgp4wU2hX8LUi.pgp Description: PGP signature
Re: Ghostscript 6.0
On Thu, Mar 09, 2000 at 06:59:01AM +0100, Adrian Bunk wrote: > On Wed, 8 Mar 2000, Branden Robinson wrote: > > Eh? There would be no real code changes at all. As I understand it, the > > license on 5.5 is all that has changed. So why not move it from non-free > > to main for potato? > > The Release Notes of GNU ghostscript 5.50 say: > > The content of GNU Ghostscript 5.50 is Aladdin Ghostscript 5.50 with two > enhancements: > > - Approximately a dozen bug fixes that were posted on the Web site > after the release. Well, it would be good to have these! > - The expanded URW++ fonts with the full Adobe PostScript 3 > character set (the additions are mostly Eastern European > characters). Given the fact that we have quite a few Eastern European users, this might not be a bad idea either. If dark would approve this, I think we should do it. I'd volunteer but I need to be occupying myself with XFree86 4.0. (They're on their second release candidate -- it is very close.) -- G. Branden Robinson| I am sorry, but what you have mistaken Debian GNU/Linux | for malicious intent is nothing more [EMAIL PROTECTED] | than sheer incompetence! roger.ecn.purdue.edu/~branden/ | -- J. L. Rizzo II pgpN9bOjURQlw.pgp Description: PGP signature
So, what's up with the XFree86 4.0 .debs?
I have been getting a fair amount of mail about this so I thought I would mail two of the most widely-read lists Debian has. Hopefully folks will agree with me that XFree86 4.0 support has ramifications for both users and developers. I don't subscribe to -user, so I will not see replies posted to that list. *) What? In case anyone missed the fanfare, a major new upstream version of XFree86 -- the version of the X Window System Debian uses -- was made last week. In addition to being based upon the latest official code base of the X Window System itself, X11R6.4, XFree86 4 features many architectural changes and enhancements -- far too many to list here. Interested readers can start with the following two URL's: http://www.xfree86.org/4.0/README.html http://www.xfree86.org/4.0/RELNOTES.html *) Who? As Debian package maintainer for XFree86, it's my responsibility to come up with Debian packages. They're not available yet, so I am sending this message to apprise Debian users my fellow developers of the situation. That brings us to the question that everybody has been asking... *) When? I don't know. I had hoped to get some preliminary packaging done on the 3.9.x (4.0 pre-release) series, but time constraints prevented that from happening. Furthermore, the 4.0 release doesn't even build out of the box on Debian[1]. This is a recent breakage; 3.9.18, released just a couple of weeks previous, compiled fine. But, I'm not resigning my position as XFree86 package maintainer. Getting 3.3.6 fit for potato is actually priority number one, but since that is just in a scrutiny cycle for release-critical bugs, the lion's share of my Debian time is actually going to XFree86 4.0. I don't have a timeframe on when they'll be ready yet -- the reasons are discussed below. *) Where? Phase 1) My initial intention is to make even my earliest progress available to interested Debian users. These packages will be highly, HIGHLY experimental, and I will make any effort to support smooth upgrades between them. This means that I will be maintaining package relationships only with respect to officially released Debian packages (3.3.6-x and previous). The practical consequence of this is that it may be necessary to purge the packages of one of these experimental releases before a new experimental set can be installed. This is inconvenient, but it is better than clogging up the Depends/Replaces/Provides/Conflicts/etc. lines with cruft from an experimental series of packages. These initial experimental versions will only be available from the official Debian homepage of XFree86 development, the X Strike Force <http://www.debian.org/~branden/>. Initially, I probably won't provide a proper APT repository since upgrading will likely be broken anyway. I will only expect the kind of people who would build XFree86 4.0 from source themselves to use these packages. These will not be appropriate for consumption by ordinary users who want things to "just work". Since these won't be official releases, bug reports filed with the Debian Bug Tracking System against these packages will be closed immediately and without comment. Phase 2) This phase will occur once I've settled upon a package arrangement and have worked out what I think the most critical issues are going to be, I'll expand my testing model a little bit. I won't release to unstable, but I'll make my test packages APT-able. My target audience for this phase is people who aren't going to panic if things break or work funny. Again, since these won't be official releases, bug reports filed with the Debian Bug Tracking System against these packages will be closed immediately and without comment. Phase 3) This will happen once I have a fair amount of confidence in the packages. I will release them to unstable and they will be treated like any other Debian package in unstable. (At least, as much so as the XFree86 packages ever are.) *) Why? Why all this complication? Why a three-phase approach to packaging XFree86 4.0? There are a number of reasons: 1) I'm going to repackage XFree86 basically from scratch. If debhelper is up to the task -- and I think it is -- I'm going to use it. It really does nicely automate a lot of the otherwise tedious stuff in packaging, and I need to focus my energies on the bigger issues. I will continue to use some form of "Doogie's Build System", which I think is invaluable for a package of this size. 2) Package relationships are going to be shaken up quite a bit. The biggest change is the server model, discussed in the Release Notes URL above. There will be one server binary, "XFree86", which dynamically loads various server modules for diverse purposes. This will probably demand a fairly involved virtual package setup, since there will be
Re: So, what's up with the XFree86 4.0 .debs?
Today's news flash: omitted words can really change the meaning of a sentence. On Sun, Mar 12, 2000 at 01:16:55PM -0500, Branden Robinson wrote: > They're not available yet, so I am sending this message to apprise Debian > users my fellow developers of the situation. ...users AND my fellow developers... > These packages will be highly, HIGHLY experimental, and I will make any > effort to support smooth upgrades between them. ...and I will NOT make any effort... Also, in case it was unclear in my previous mail, I have no plans to support full versions of XFree86 3.3.x and 4.x in the same Debian release. By the time official 4.0 .debs are ready, it is my hope that the legacy chipsets currently only supported in 3.3.x will be supported in 4.x as well. 3.3.x libc5-compatibility libraries will be provided for i386 and m68k per my previous mail until and unless consensus is reached that this support should be dropped. -- G. Branden Robinson|The errors of great men are venerable Debian GNU/Linux |because they are more fruitful than the [EMAIL PROTECTED] |truths of little men. roger.ecn.purdue.edu/~branden/ |-- Friedrich Nietzsche pgpRhRvYKLFsg.pgp Description: PGP signature
Re: So, what's up with the XFree86 4.0 .debs?
On Sun, Mar 12, 2000 at 07:06:19PM -0800, Alex Romosan wrote:
> the problem is with curses.h in libncurses5-dev. it redefines ERR and
> as such it conflicts with the definition from the glibc headers. this
> was the same problem noticed in dpkg 1.6.10. i just commented out the
> redefinition of ERR in /usr/include/curses.h and then the X package
> compiled just fine. i am sure the proper solution is the one used in
> dpkg-1.6.11 though.
Hmm. I am using the following patch, which I got from slashdot of all
places:
--- xc/config/makedepend/cppsetup.c.origSun Mar 12 15:47:41 2000
+++ xc/config/makedepend/cppsetup.c Sun Mar 12 15:48:21 2000
@@ -188,7 +188,7 @@
return 0;
do {
var = (*s)->s_value;
- if (!isvarfirstletter(*var))
+ if (!isvarfirstletter(*var) || !strcmp((*s)->s_name, var))
break;
s = lookup_variable (ip, var, strlen(var));
} while (s);
It did seem to fix the problem. If someone who understands cppsetup.c
could comment and it turns out that this patch doesn't in fact disable some
feature of cppsetup, I will submit this patch to XFree86.
Anyway, XFree86 4.0 built without errors on a potato system and I am
basically deep in the guts of it right now, figuring out how I need to
break it up for packaging.
--
G. Branden Robinson| I am sorry, but what you have mistaken
Debian GNU/Linux | for malicious intent is nothing more
[EMAIL PROTECTED] | than sheer incompetence!
roger.ecn.purdue.edu/~branden/ | -- J. L. Rizzo II
pgpbKpq6enEWg.pgp
Description: PGP signature
Danger, Branden Robinson! Danger!
On Sun, Mar 12, 2000 at 06:18:25PM -0800, Joey Hess wrote: [...] > - X 4.0 drivers (but probably just X servers, to minimize changes; Branden > has huge reorganizations in mind for X) Ha ha ha ha. "Just X servers"? You haven't been reading the news. :) There is only one server binary in XFree86 4.0. The "huge reorganizations" are almost all going to revolve around that X server binary, too. 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. I've considered checking myself into a mental hospital, rendered a cackling lunatic by the weight this thing is going to put on our packaging infrastructure (well, not so much that as the weight it will put on user comprehension). If we're going to come up with something better than task packages, I need it. Now. Supporting the 3.3.x server with 4.0 libraries and clients would in fact be easier than the other way around. > Please speak up if you like this idea. I like it fine as long as I don't have to commit to any particular strategy regarding 4.0. I only really got my hands dirty with it today, and it is far too soon for me to speculate sensibly on details of what the final packages will look like. -- G. Branden Robinson|The only way to get rid of a temptation Debian GNU/Linux |is to yield to it. [EMAIL PROTECTED] |-- Oscar Wilde roger.ecn.purdue.edu/~branden/ | pgpzN0zGoQNCy.pgp Description: PGP signature
Re: So, what's up with the XFree86 4.0 .debs?
On Mon, Mar 13, 2000 at 02:22:10AM +, Edward Betts wrote: > I thought the plan was to drop support for ISA VGA cards in 4.x, so people > who want to keep using old hardware HAVE to stick with 3.3.x If so, that's news to me and I've been following the XFree86 developers' list for months. Support for the ISA bus is not being dropped. Whether the legacy hardware is supported depends on if anybody ports the old 3.3.x drivers to the new server model or not. > I am not actually suggesting that you try and maintain both. It would make the > upgrade path easier if everything had a 4 in it, so that people stay with > 3.3.x and do not move until they decide they want the new version. I mean how > do you plan to handle the fact that the config file format has changed? Does > anybody have a converter? I don't know yet, and I don't think so. > On the other hand, I suppose it is probably useful to force people to upgrade > to the new version. The old version will probably not be maintained upstream. Last I heard, the 3.3.x tree was going to be maintained concurrently with 4.x for approximately a year. Most of the developer enthusiasm seems to be with 4.x, though, and this will probably only strengthen with its release. XFree86 is a volunteer project, too, and has the same problems with herding cats. > You are going to keep /usr/X11R6 for this release right? I guess that the > XFree86 people might get a bit irritated if you tried to drop it. Actually, I've evilly been toying with the idea of #defining ProjectRoot to /usr for 4.0. Upstream has already moved almost entirely to the way Debian currently does things as far as filesystem layout goes. > (No, I am not using an ISA VGA card. No, I do not know anybody who is using > one. But, I did use X 3.3.x on a EGA card for a while, I see that xega is not > even in the archive now.) I still have an old DOS game called EGATREK lying around someplace. I sure would like to play it again sometime. I wonder if dosemu can give you ega graphics in an X window? :) -- G. Branden Robinson|Human beings rarely imagine a god that Debian GNU/Linux |behaves any better than a spoiled child. [EMAIL PROTECTED] |-- Robert Heinlein roger.ecn.purdue.edu/~branden/ | pgpHtoQeibLSV.pgp Description: PGP signature
Re: So, what's up with the XFree86 4.0 .debs?
On Mon, Mar 13, 2000 at 09:59:20AM -0500, Alex Yukhimets wrote: > Commercical packages I use assume > existence of /usr/X11R6/lib/X11/app-defaults (not to mention > /usr/X11R6/include and /usr/X11R6/lib). Sorry, dude, upstream already kicked over the table on that one. It is now /etc/X11/app-defaults. > I remember that me being against something actually serves to you as an > endorsements to do it, Heh heh heh heh heh heh... -- G. Branden Robinson|Any man who does not realize that he is Debian GNU/Linux |half an animal is only half a man. [EMAIL PROTECTED] |-- Thornton Wilder roger.ecn.purdue.edu/~branden/ | pgpp5tG1VEOoR.pgp Description: PGP signature
Re: realplayer installer and frozen
On Mon, Mar 13, 2000 at 05:47:41PM -0800, Joey Hess wrote: > The realplayer installer package in potato is broken and useless because > Real has, in their infinite wisdom, removed version 6.x of the program from > their download sites now that they have a beta of 7.0. (Bug #60323.) > > So the installer can't install anything. The package either needs to be > pulled from potato, or the new package in woody that can handle realplayer > 7.0 needs to be substituted in its place. The changes to the actual debian > package were minor; the changes between real 6.x and 7.0 are anyone's > guess and who knows what has broken. > > So, Dark, what should I do? Let's boycott the fuckers! Drop the package and swear to never support Real until they discard their patents and free their software! G! P! L! G! P! L! CHAGE! -- G. Branden Robinson|I just wanted to see what it looked like Debian GNU/Linux |in a spotlight. [EMAIL PROTECTED] | -- Jim Morrison roger.ecn.purdue.edu/~branden/ | pgpdyGC19dC46.pgp Description: PGP signature
Re: priority of x-window-manager
On Wed, Mar 15, 2000 at 09:04:47PM +0900, Changwoo Ryu wrote: > You misunderstood "i18n" as just the translation support (and "l10n" > as the translations). Translation is just a category of i18n. > Atsuhito means i18n for the correct character displaying. > > Korean (and maybe Japanese) X users often see the Netscape titlebar > incorrectly displays Korean web page title. Many of the window > managers still don't care about this and just draw the raw string with > XDrawString(). The correct behavior is decoding the received compound > strings and drawing the decoded ones with XmbDrawString(). Thanks for the clarification. I'm willing to support such a priority increase now; but first, please come up with a list of specific things that a window manager needs to do. We can't just say "add 10 points if the window manager is internationalized" without telling the possible thick-headed American package maintainer how to determine whether it is or not. :) One item would obviously be: + The window manager should use XmbDrawString() instead of XDrawString() for non-error/non-diagnostic text output. Please come up with more, if there are any, and I'd be happy to make a new policy proposal incorporating your suggestions. -- G. Branden Robinson| I've made up my mind. Don't try to Debian GNU/Linux | confuse me with the facts. [EMAIL PROTECTED] | -- Indiana Senator Earl Landgrebe roger.ecn.purdue.edu/~branden/ | pgpv5mHi93o7V.pgp Description: PGP signature
Re: priority of x-window-manager
On Thu, Mar 16, 2000 at 02:16:42PM +0900, Taketoshi Sano wrote: > > We can't just say "add 10 points if the window manager is > > internationalized" without telling the possible thick-headed American > > package maintainer how to determine whether it is or not. :) > > I have thought that users can judge if the specific software > is correctly internationalized or not, and they will file their > report on BTS if they find the wrong priorities. But your concern > may be reasonable. Well, what I want to do is have very clear guidelines so that we don't have any "bug terrorism". Violating policy is often interpreting as being a release-critical bug -- so if we put this into policy, I want to try to be very clear about what kinds of i18n problems are going to hold up a release, or cause a package to be removed from consideration for a release, and what kinds won't. > > One item would obviously be: > > + The window manager should use XmbDrawString() instead of XDrawString() > > for non-error/non-diagnostic text output. > > > > Please come up with more, if there are any, and I'd be happy to make a new > > policy proposal incorporating your suggestions. > > In fact, the true internationalization may require more than just replacing > XDrawString() with XmbDrawString(), but this is a good indicator as a start > point, I think. Yes, that's what I'm trying to get at. Obviously there's more to i18n than just replacing function calls, or everything would have been i18n'ed already. :) But since I have only a shallow understanding of i18n issues generally, and in implementing them in X window managers specifically, I wanted to request input on this issue. > # Anyway, users will file their report on that package if it can not be used. > > Just one thing: Error text output could be localized one (libc does have > localized error messages for such as "No such file or directory" or > "File exists". So excluding error output is not good in this case, I think. Yeah, but here's where we run into the specter of l10n again -- which I very strongly feel shouldn't be mandated by policy. Here's what I'm getting at -- if an X client has been internationalized, and it provides locale specific information to the window manager, the window manager needs to be able to deal with that. The XDrawString() vs. XmbDrawString() issue is a perfect example; I've *seen* the title of my Netscape window become total gibberish (in any language), because the window manager didn't use a multi-byte character aware function to render it -- if it did, I'd see proper Japanese glyphs (which I don't understand, either -- but I recognize them as human language rather than a machine-readable encoding method like Shift_JIS or EUC-JP). Error messages are another story. If the error messages come from outside the window manager, and are already localized, then the window manager shouldn't mangle them. I don't, however, think that the window manager should be compelled by Debian policy to have an internal message catalog for various languages. To sum up, what I'm saying is this: I think a Debian window manager policy should say that window managers should be given higher priority if they DON'T mangle localized information that they are intended to pass along to the user. And that is what I understand internationalization of computer software to mean -- it makes localization transparent and possible. -- G. Branden Robinson|Men use thought only to justify their Debian GNU/Linux |wrong doings, and speech only to conceal [EMAIL PROTECTED] |their thoughts. roger.ecn.purdue.edu/~branden/ |-- Voltaire pgpzcMtghfvPb.pgp Description: PGP signature
Re: xfs question
On Thu, Mar 16, 2000 at 04:19:47PM +0100, Michael Meskes wrote: > Now that xfs per default does not listen on a tcp port anymore, could > anyone please tell me how to configure x (i.e. XF86Config) to use unix > domain sockets instead? I think the answer is in the FAQ: zgrep -i unix /usr/share/doc/xfree86-common/FAQ.gz Like Unix shell login sessions, which are customized by a file like Like the Unix filesystem, windows in X are laid out like a tree with a FontPath "unix/:7100" Yup. I sometimes wonder why I bother maintaining that FAQ. -- G. Branden Robinson| Debian GNU/Linux | If ignorance is bliss, [EMAIL PROTECTED] | is omniscience hell? roger.ecn.purdue.edu/~branden/ | pgpyR0AsI6ybC.pgp Description: PGP signature
Bug#60573: general: wrong perms on /dev/null and /tmp in potato upgrade
reassign 60573 SantiagoVila thanks On Thu, Mar 16, 2000 at 04:57:37PM -0700, der.hans wrote: > Subject: general: > Package: general > Version: 2315 > Severity: grave > > [EMAIL PROTECTED]:~$ ls -l /dev/null > crw-r--r--1 root root 1, 3 Feb 22 1999 /dev/null > > [EMAIL PROTECTED]:~$ ls -ld /tmp > drwxr-xr-t3 root root 1024 Mar 14 18:40 /tmp > > /dev/null was 644 not 666, which is what it is everywhere but my two > problem machines. > > /tmp was 1755, not 1777 as it needs to be. > > This machine was installed off a Cheap*Bytes 2.1 cd without these probs. > Today I > used apt-get -u dist-upgrade to move to potato, then noticed the problems. > > The other machine with the /dev/null problem was also slink updated to potato. > > -- System Information > Debian Release: 2.2 > Kernel Version: Linux shasta 2.0.36 #2 Sun Feb 21 15:55:27 EST 1999 i586 > unknown > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- G. Branden Robinson| If you make people think they're Debian GNU/Linux | thinking, they'll love you; [EMAIL PROTECTED] | but if you really make them think, roger.ecn.purdue.edu/~branden/ | they'll hate you. pgpqTnP6VUNi2.pgp Description: PGP signature
Re: [dickey@clark.net: Re: http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=59191]
On Sat, Mar 18, 2000 at 12:42:12AM +0100, Josip Rodin wrote: > 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'. Tom Dickey is also the upstream xterm maintainer. He and I have exchanged mails several times over the past couple of years. -- G. Branden Robinson| We either learn from history or, Debian GNU/Linux | uh, well, something bad will happen. [EMAIL PROTECTED] | -- Bob Church roger.ecn.purdue.edu/~branden/ | pgpasB6DlY6ul.pgp Description: PGP signature
Re: Single architecture on -announce lists
On Fri, Mar 17, 2000 at 04:49:54PM -0500, Bob Hilliard wrote: > During the slink freeze there was some discussion of the wasted > bandwidth due to -devel-announce and -announce listing all packages > installed/uploaded to all architectures. Funny, I don't notice any such messages going to -devel-announce or -announce. -- G. Branden Robinson|Murphy's Guide to Science: Debian GNU/Linux |If it's green or squirms, it's biology. [EMAIL PROTECTED] |If it stinks, it's chemistry. roger.ecn.purdue.edu/~branden/ |If it doesn't work, it's physics. pgpiozaCIFw9O.pgp Description: PGP signature
Re: cannot login in xdm anymore (upgrade potato -> potato)
On Tue, Mar 21, 2000 at 10:45:37AM -0600, Carlo Segre wrote: > > Xlib: connection to ":0.0" refused by server > > Xlib: Client is not authorized to connect to Server > > xrdb: Can't open display ':0' [...] > I have seen a similar symptom on 1 out of three computers that I have > running potato. In my case, I am not running xdm but gdm and I am able > to log in and run any X applications from the GUI but if I try to run one > from a command line in a a terminal, I get the same message. Well, terminal sessions that aren't children of the X session don't inherit $DISPLAY. If $DISPLAY is not set, these programs don't even know where to look for a server to connect to. Some might default to :0.0. > This happens only when I am using a Gnome session. With a Debian session > it works fine. Furthermore, as root there are no problems. Since I am > seeing this on one of three machines which are presumabley set up in the > same way, I am presuming that it is some incorrect configuration file > somewhere. If anyone has an insight, I would appreciate it. My next > move is to purge all X packages and reinstall... Please see the section in the Debian X FAQ[1] about the XAUTHORITY environment variable. [1] /usr/share/doc/xfree86-common/FAQ.gz -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy spot [EMAIL PROTECTED] |on the pavement, where used to lie the roger.ecn.purdue.edu/~branden/ |carcass of a dead horse. pgpmxMIzIi7oU.pgp Description: PGP signature
Re: Bash, Keys, Potato
On Thu, Mar 23, 2000 at 06:17:21PM -0300, Rodrigo Castro wrote: > I started with no .inputrc, no /etc/profile, no /etc/inputrc > and even so I had problems with letter E (upcase only). Any idea? Even > with no setup, no config files, I get no success. I upgraded my > libreadline4 today and it didn't work either. Hmm, since you are from brazil you might not be used a key layout 100% identical to a North American keyboard. You may have fallen victim to Yann Dirson's 100%-bug-free console-data package. Install the "kbd" package, and from the console (not X), use the "showkey" command to determine what scan code is being generated by the E key. If none, you either have a hardware problem or a kernel problem. Otherwise, your console keymap is messed up and you should file a bug against the console-data package. Don't feel bad; Yann Dirson has the default keymap set to some French thing -- this affects every Debian user in the world, and most of the world isn't France. I guess some people take the figurative expression "lingua franca" too literally. :) -- G. Branden Robinson|Software engineering: that part of Debian GNU/Linux |computer science which is too difficult [EMAIL PROTECTED] |for the computer scientist. roger.ecn.purdue.edu/~branden/ | pgpmq7W4p7ADs.pgp Description: PGP signature
Re: New version of xserver-svga gives poorer display on laptop
On Sun, Mar 26, 2000 at 06:05:43PM +0400, Konstantin Kivi wrote: > I also had to add > Set_LCDClk 40 > to the Device section. Be aware that parse-xf86config > used in /etc/init.d/xdm doesn't unserstand it Be aware that because of problems like this, parse-xf86config has been eliminated from recent XFree86 packages. Potato will ship without it. -- G. Branden Robinson|Any man who does not realize that he is Debian GNU/Linux |half an animal is only half a man. [EMAIL PROTECTED] |-- Thornton Wilder roger.ecn.purdue.edu/~branden/ | pgpDApaBdf5cd.pgp Description: PGP signature
Re: blue on black is unreadable
On Sun, Mar 26, 2000 at 12:54:39AM +0100, Wouter Hanegraaff wrote: > > Oh crap, you're right. I wasn't thinking on that one. Oh well, I guess > > somebody will have to find good colour combinations for every colour > > package. > > I can do that. Black on white. Proven to work > perfectly for centuries. Or do you only read books with white letters on > a black background, or all sorts of colors for differently styled > text??? You betray profound ignorance. The pages of books (most of them, anyway) do not emit their own light. They are reflective only. CRT's generate light. If black-on-white xterms work fine for you, that's great. It's YOUR system and your choice. But your rationale betrays little understanding of the phsyiological/ergonomic issues involved. > Is there a reason why xterm defaults to color xterm? In slink it > does, on potato it's changed all of a sudden. The recent potato xterm packages change precious little from upstream behavior. You have a beef with it, take it up upstream. > Why does debian have to be different than the rest of the world in > everything? Why do I get colors when I set TERM=xterm? there was already > xterm-color and xterm-debian which could do colors. You get colors when TERM=xterm because upstream says so. Any Linux distribution with a brain in its head uses XFree86 xterm for its version of xterm. nxterm is a piece of shit. If you want an X11R5-compatible xterm, use TERM=xterm-r5. Read /usr/share/doc/xterm/README.Debian and /usr/share/doc/xterm/xterm.faq.html for more information. > Right now, I have to set my TERM to xterm-mono on potato to avoid > fruitsalads in a handful of programs I use very often (Mutt, dselect, > vim). That is very annoying, because it results in broken terminal > settings when I login to *any* other system. Maybe I'm the only one who > hates colors in xterms, but still. It should be possible to use xterms > without colors in a normal way, and right now it isn't. It is, you just haven't bothered to read any documentation on the subject. > Please leave *personal* configuration to the *user*, and leave the system > configuration to some reasonable, _very_ conservative defaults. I agree with this statement but not the baggage you attach to it. As far as I'm concerned, "conservative" means "upstream behavior." If upstream changes, I'll track those changes unless there is a very good reason not to (for instance, Debian policy). You desire to keep compatibility with a version of xterm that is ten years old is not a very good reason to accomodate you in the Debian defaults. Read that FAQ. Features have been added to xterm by Thomas Dickey, but the only changes that break compatibility have been bugfixes. I'm sorry if you've grown attached to some of X11R5's bugs. Please keep replies out of my personal mailbox. I read the lists. -- G. Branden Robinson| Convictions are more dangerous enemies Debian GNU/Linux | of truth than lies. [EMAIL PROTECTED] | -- Friedrich Nietzsche roger.ecn.purdue.edu/~branden/ | pgpjlhOWhE2Kx.pgp Description: PGP signature
Re: blue on black is unreadable
On Sun, Mar 26, 2000 at 04:07:11PM +0200, Wouter Hanegraaff wrote: > > So why don't you just change your local settings to make xterm be mono? > > Ummm. `XTerm*ColorMode: no' seems like it'd do what you want. > > That seems to work just fine. I wish I was aware of that resource a bit > earlier... Perhaps if you read the manpage before whining and bitching to this mailing list, you'd spend less time being unhappy. colorMode (class ColorMode) Specifies whether or not recognition of ANSI (ISO 6429) color change escape sequences should be enabled. The default is ``true.'' -- G. Branden Robinson| Communism is just one step on the long Debian GNU/Linux | road from capitalism to capitalism. [EMAIL PROTECTED] | -- Russian saying roger.ecn.purdue.edu/~branden/ | pgpqJWcVx3zVE.pgp Description: PGP signature
Re: Bug#32888: marked as done (base: Removing "Obsolete" package base kills a system)
On Sun, Mar 26, 2000 at 02:53:30PM +0200, Raphael Hertzog wrote: > Yes, because Santiago Vila doesn't want it and because it looks like > a crude hack. There is no correlation there. Or if there is, it is a negative one. -- G. Branden Robinson| If a man ate a pound of pasta and a Debian GNU/Linux | pound of antipasto, would they cancel [EMAIL PROTECTED] | out, leaving him still hungry? roger.ecn.purdue.edu/~branden/ | -- Scott Adams pgpXMBuPkHWRe.pgp Description: PGP signature
Re: Signing Packages.gz
On Tue, Mar 28, 2000 at 12:43:32AM +1000, Anthony Towns wrote: > Actually, now I think about it, the Packages file itself is valuable > information. Consider a Packages file that doesn't actually changes the > .deb's, but changes the netbase entry, say to read: > > Package: netbase > Depends: vim > Conflicts: nvi, emacsen > > and leaves everything else the same. You can only achieve fairly petty > vadalism with this, but it would still be nice to avoid it, IMO. What a deliciously evil idea. -- G. Branden Robinson|Reality is what refuses to go away when Debian GNU/Linux |I stop believing in it. [EMAIL PROTECTED] |-- Philip K. Dick roger.ecn.purdue.edu/~branden/ | pgpoJuI7bSUeY.pgp Description: PGP signature
Re: Potato - update-alternatives (Ian Jackson) and window managers - doubt (and Slink to Potato Success)
On Mon, Mar 27, 2000 at 09:16:10PM +0200, Wichert Akkerman wrote: > Previously Robert Bihlmeyer wrote: > > FWIW, gnome-session is not a window manager. > > But it starts one for you, so it would be a good candidate for an > x-window-manager alias imho. I'm antsy about that. gnome-session itself does NOT provide window management services. The package also doesn't depend on a real window manager. I think having it masquerade as a window manager could lead to people not having a window manager installed at all. Users generally need to modify their .xsession files just as they do their .profile. If the system administrator wants to modify the default, system-wide X session file to call gnome-session, he can. /etc/X11/Xsession is a conffile. The onus should be on him to make sure there is at least one window manager installed that gnome-session can invoke. Debian has a very configurable X environment; I don't cram much more than I have to down anyone's throat. Many things are conffiles so that they can be tailored by the local admin. Let's please not pretend this isn't the case, and pollute the meaning of the x-window-manager virtual package and alternative. Session managers and window managers are different things. See the Debian X FAQ. -- G. Branden Robinson|You don't just decide to break Kubrick's Debian GNU/Linux |code of silence and then get drawn away [EMAIL PROTECTED] |from it to a discussion about cough roger.ecn.purdue.edu/~branden/ |medicine. pgpCaRUEuhkto.pgp Description: PGP signature
Re: ITP: tinydns and dnscache
On Mon, Mar 27, 2000 at 02:52:59PM -0500, Adam McKenna wrote: > I just subscribed, and I'd like to let the list know I'm (hopefully) going to > be working on a couple of new packages, namely tinydns/dnscache by djb, which > is a replacement for BIND, and djb's "daemontools", (which is required for > running tinydns). Since the letters "djb" appear here, I guess it goes without saying that these will have to go in non-free, but please mention the license when posting ITP's. -- G. Branden Robinson|If you wish to strive for peace of soul, Debian GNU/Linux |then believe; if you wish to be a [EMAIL PROTECTED] |devotee of truth, then inquire. roger.ecn.purdue.edu/~branden/ |-- Friedrich Nietzsche pgpH03QOQaALh.pgp Description: PGP signature
Re: woody mutt users, please read
On Mon, Mar 27, 2000 at 10:38:22PM +0200, Marco d'Itri wrote: > You have to change all "lists" commands in your ~/.muttrc in > "subscribe". I have both. Do you mean I can get rid of "lists" altogether? Last time I read the docs, they appeared to do slightly different things. -- G. Branden Robinson| Debian GNU/Linux |Exercise your freedom of religion. Set [EMAIL PROTECTED] |fire to a church of your choice. roger.ecn.purdue.edu/~branden/ | pgpj6kS3Xh08u.pgp Description: PGP signature
Re: keyring-maint@debian.org
On Mon, Mar 27, 2000 at 04:00:30PM -0600, Mike Mattice wrote: > How long does it take to get your gpg key updated via > this e-mail address? The more you ask, the longer it takes. :) Seriously, AFAIK keyring maintenance is handled by one (very busy) person. Please be patient. -- G. Branden Robinson|It's not a matter of alienating authors. Debian GNU/Linux |They have every right to license their [EMAIL PROTECTED] |software however we like. roger.ecn.purdue.edu/~branden/ |-- Craig Sanders, in debian-devel pgplftmyZQTZm.pgp Description: PGP signature
Re: first draft "aptitude howto"
> it for removal.
Packages that are not presently installed (in the "New Packages" or "Not
Installed Packages" categories) may be selected for installation with the
"+" ("add package") key.
> Packages which are upgradeable can be put on hold with the '-' key, so their
> desired state is downgraded from "upgrade" to "hold". If you press the '-'
> key once more, they are even deleted. To purge a package instead of deleting
> it (purging will remove all data, especially the config files, too) you use
> the '_' key.
Packages that are installed (in the "Installed Packages" or "Upgradeable
Packages" categories) may be placed on hold, removed, or purged. Placing a
package on hold means that it is kept at the currently installed version
even if a newer version is available. Removing a package deletes it from
the system -- but system-specific configuration information about the
package is kept for reference in case the package is re-installed later.
Purging a package removes every trace of it from the system, including its
configuration information.
Pressing the '-' ("remove package") key places upgradeable packages on
hold, and marks installed packages for removeable. Pressing '-' again on a
held package marks it for removal. Pressing the '_' ("purge package") key
marks a package for purge.
(Remark: I think I would find the overloading of the '-' key confusing.
Please consider using a different key for hold operations. 'h' seems
intuitive but might be pressed by novices as an attempt to get help. '!'
seems like another possible candidate for hold, a la "Stop!" "Wait!"
"Achtung!" :) )
> If you made your selections (which action should be taken on which package
> with "+", "-", "_") you press the 'g'o key. Another screen will list you all
> desred options (which packages will be updated, which installed and which
> deleted. You can make changes there, too. While pressing 'q' will get you
> back to the main tree, pressing 'g' a second time will actiate the
> installation/download/deleting of packages.
Once you have marked packages of interest with the desired actions, use the
'g' ("go") key to put the package manager to work. A confirmation screen
will be displayed that summarizes the actions to be taken. You can use the
same operation keys here that you did on the main screen, in the event you
made a mistake or change your mind. From this confirmation screen,
pressing 'q' ("quit") returns you to the main screen, and 'g' ("go") a
second time invokes the apt program and sets about putting your system's
packages in the desired state.
> Additional Keys in aptitude include '/' for searching, 'home', 'end',
> 'up', and 'down' for navigation.
(As a die hard vi user, I suggest making 'j' and 'k' also perform
navigation operations as well. :) )
> NOTE: with aptitude 0.0.4a (included in potato) you will find it confusing if
> you dont have support for colors in your term, since:
What kind of Luddite would use a terminal type that didn't support color?
:)
> (todo: find the right names for those colors :)
> white = normal
> red= broken
> green = install
> turkis = remove
Do these reflect current status, or the desired action to be taken?
I don't know what "turkis" means; I guess I'll have to try aptitude out to
learn. :)
> bl n wh= hold
What?
> cyan = update (same as green but alrady installed).
>
> Also in the 0.0.4a version a split screen view with package details and a
> key help menu is missing.
It would really suck to ship without a help screen. Dark might be
persuaded to let in such a documentation-only revision.
--
G. Branden Robinson|
Debian GNU/Linux | kernel panic -- causal failure
[EMAIL PROTECTED] | universe will now reboot
roger.ecn.purdue.edu/~branden/ |
pgpkB3H8M7ODP.pgp
Description: PGP signature
Re: Is someone working on Jazz++ ?
On Fri, Mar 24, 2000 at 08:56:15AM -0300, Eduardo Marcel Macan wrote: > Hello, I noticed Jazz++ (www.jazzware.com) is now released under > the GPL, is there anyone working on it? Unfortunately I don't have the time > to do it, but I'd like to see it packaged. It is the best linux midi sequencer > nowadays. I tried, but it would not build and failed in several places. It is written mostly in C++, and I don't know C++. Not to mention the fact that I do have one or two other packages on my plate. Someone who does, please adopt this package. As added incentive, if you get it working, you'll a get a "avoid-Overfiend-bitch-out-for-free" card. This offer is valid for a limited time only! Not for pets or small children. -- G. Branden Robinson| Communism is just one step on the long Debian GNU/Linux | road from capitalism to capitalism. [EMAIL PROTECTED] | -- Russian saying roger.ecn.purdue.edu/~branden/ | pgp9aDvRHtXfI.pgp Description: PGP signature
Re: WNPP
On Tue, Mar 28, 2000 at 08:58:38AM +0200, Radovan Garabik wrote: > On Mon, Mar 27, 2000 at 08:27:29PM -0500, Brian Almeida wrote: > > ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), > > so > > I probably can't package it due to wonderful US laws. Drat. > > Strange... I read everywhere that US export restrictions are now gone. > (e.g. just a minute ago the announcement of redhat 6.2) New regulations were adopted in January that lift some of the restrictions on cryptographic software, but it's still treated specially by U.S. law. What's more, those changes were deliberately temporary, and are up for review next month and may be revoked or replaced. It is too soon to tell whether the U.S. is going to join the free world when it comes to crypto or not. Louis Freeh (Director of the FBI) testified before Congress this week, and muttered ominously about increases in "cyber-crime". You can rest assured that he trotted out his usual apocalyptic horsemen of child pornography, illegal drug trafficking, and terrorism on U.S. soil to try and scare Congress into permitting universal warrantless wiretaps, key escrow, and other acts of urination on the Fourth Amendment. -- G. Branden Robinson|The errors of great men are venerable Debian GNU/Linux |because they are more fruitful than the [EMAIL PROTECTED] |truths of little men. roger.ecn.purdue.edu/~branden/ |-- Friedrich Nietzsche pgpFFu2lBWToW.pgp Description: PGP signature
Re: Encryption Builds
On Tue, Mar 28, 2000 at 02:28:49PM -0800, Brent Fulgham wrote: > Can anyone refresh my memory as to the legality of encryption-enabled builds > of software inside the U.S. Did we (like Kernel.org) decide it was okay to > host this in U.S.-based servers, or are we still recommending > that members of the free world do such builds? > > If the answer is to not build inside the U.S., I need a non-US developer > to help me build a SSL module for AOLserver. A flamewar on -private between myself, Manoj, and Ben Collins led to the conclusion that it's not yet safe to distribute crypto in the U.S. I posted another message to -devel a few minutes ago with more information. -- G. Branden Robinson|Suffer before God and ye shall be Debian GNU/Linux |redeemed. God loves us, so He makes us [EMAIL PROTECTED] |suffer Christianity. roger.ecn.purdue.edu/~branden/ |-- Aaron Dunsmore pgpIrw6tWgb9M.pgp Description: PGP signature
Re: Paradise
On Tue, Mar 28, 2000 at 03:53:22PM -0600, Jeffrey Watts wrote: > Hello, I'm a member of the Paradise Netrek development team. Paradise > Netrek is a X based game that started as Xtrek back in 1986. It is a > multiplayer, real-time, Internet game. > > Paradise has undergone a revival recently, and active development has > resumed. > > The Paradise Netrek developers would like to work with Debian to get > Paradise included in Debian GNU/Linux. > > Please let me know what I need to do or who I need to contact. I should > be on debian-devel but feel free to CC me. Sounds great, but the first thing we need to know is: What's the license on Paradise Netrek? If it is DFSG-free (and it is if it uses the GPL, LGPL, MIT, or BSD without advertising clause licenses), then you're bound to generate enthusiasm. :) -- G. Branden Robinson| Never underestimate the power of human Debian GNU/Linux | stupidity. [EMAIL PROTECTED] | -- Robert Heinlein roger.ecn.purdue.edu/~branden/ | pgp5s3ga38OpK.pgp Description: PGP signature
Re: MiniVend Debian package
On Wed, Mar 29, 2000 at 10:11:57AM +0200, Stefan Hornburg wrote: > OK, now as MV 4.03 is out, there is a Debian package available now > for testing. Excellent. I've long been awaiting an upgrade to the mv command. -- G. Branden Robinson| A committee is a life form with six or Debian GNU/Linux | more legs and no brain. [EMAIL PROTECTED] | -- Robert Heinlein roger.ecn.purdue.edu/~branden/ | pgp6q02Oj3vjm.pgp Description: PGP signature
Re: MiniVend Debian package
On Wed, Mar 29, 2000 at 12:53:12PM +0200, Stefan Hornburg wrote: > Branden Robinson <[EMAIL PROTECTED]> writes: > > > On Wed, Mar 29, 2000 at 10:11:57AM +0200, Stefan Hornburg wrote: > > > OK, now as MV 4.03 is out, there is a Debian package available now > > > for testing. > > > > Excellent. I've long been awaiting an upgrade to the mv command. > > Oh, don't you know that Linux is case-sensitive ? You obviously overlooked the headers in my message... :) -- G. Branden Robinson|Murphy's Guide to Science: Debian GNU/Linux |If it's green or squirms, it's biology. [EMAIL PROTECTED] |If it stinks, it's chemistry. roger.ecn.purdue.edu/~branden/ |If it doesn't work, it's physics. pgpr71p1lMHiP.pgp Description: PGP signature
Ian Jackson, please get me the hell off your blacklist.
Mar 29 15:20:15 apocalypse sendmail[7886]: e2T8qEi03048: [EMAIL PROTECTED], ctladdr=branden (1000/1000), delay=11:28:01, xdelay=00:00:21, mailer=esmtp, pri=6332789, relay=chiark.greenend.org.uk. [195.224.76.132], dsn=4.2.0, stat=Deferred: 450 Site not yet trusted, try later [Irritated] Maybe you'd care to explain to me what's not trusted about my site? Irritated? *YOU'RE* irritated? If you don't correct this at once I will be forced to re-evaluate my place within a project that is nominally devoted to free and open communication among its members and the rest of the world. Since I cannot communicate with bug report filers from chiark.greenend.org.uk, all bug reports submitted, past, present, or future, by people from that host will be summarily closed. -- G. Branden Robinson| Communism is just one step on the long Debian GNU/Linux | road from capitalism to capitalism. [EMAIL PROTECTED] | -- Russian saying roger.ecn.purdue.edu/~branden/ | pgpzTjTxGJ1bK.pgp Description: PGP signature
Re: RBL report..
On Wed, Mar 29, 2000 at 12:42:14PM -0600, Steve Greenland wrote: > A. swbell has frequent problems with their mail-servers, both inbound > (POP) and outbound (SMTP). I don't know (or care) what OS they run. > > B. When I got my DSL line, swbell was the *only* ISP possibile in > houston. That's part of what is (very) darkly humorous about the blacklisting bigots -- they don't have much of a grasp of realities in the telecom marketplace at the consumer level. For instance, when regulations preventing phone companies from providing both local and long distance service in the same LATA were lifted, part of the agreement said that those same phone companies had to permit competition on the local loops if they wanted to peddle long distance to their local customers. Needless to say, a great many phone companies can now sell you both local and long distance service, but local phone service competition is still almost unheard of. (Just one example: BellSouth here in Louisville has been successfully stonewalling competing DSL providers on their wires for at least a year, and are lobbying the state legislature for exemption from a bill that would compel public utility companies in general to permit competition.) The cable companies are similarly trying to maintain monopolies over their wires. The result of this is that there is actually very little competition among ISP's in any given geographic locality in the United States *except* in the dialup market. So when the bigots tell you to exercise your "rights" as a consumer and change ISP's, they're either ignorant of this reality, or winking at each other from behind their nailed-up IP's, knowing you'll either be paying a lot for shitty service, and the privilege of getting off the DUL blacklist (but you'd better pray they haven't blacklisted your ISP!). They're like little kids who torture small animals -- as long as they're not getting hurt themselves, it's just good clean fun to fuck with the pathetic little creatures. > C. Even though it's now possible to get other ISPs, it would roughly > double my current ISP bill. The blacklisters consider price no object, when it's someone else's money. > D. DUL is discrimination, pure and simple. If Debian chooses to add a > warning header based on it (so that those who choose to can filter), > that's fine. If Debian starts to reject list mail based on DUL, I'd > strongly consider leaving the project. Agreed. > Joseph's arguments, while occasionally strident, are not foolish. I > find it interesting that his opponents devolve into name calling and > obscenity. Well, he could comport himself in such a way as to make his critics look worse -- and he does have a history of being on the wrong side of some issues :) -- but he's not in the wrong this time. I have noticed that after screeching for statistics that would "prove" that usage of DUL on murphy would all but eliminate spam on the Debian mailing lists, none of those screechers has bothered to actually reply to the following fact that Jason offered: > DUL would seem to effect at most maybe 10 people, but it hasn't actually > been shown to stop any spam - so this needs more investigation. No blacklister has offered suggestions for followup on this issue -- they simply continue to reiterate their faith in the righteousness and universal applicability of the DUL blacklist (and wander off on tangents about ORBS). They remind me of Creationists, who will marshal "facts" in defense of their position, but when those "facts" are discredited, will simply fallback on repeated blunt assertions of their conclusion, not caring that their premises have been obliterated. -- G. Branden Robinson|When I die I want to go peacefully in Debian GNU/Linux |my sleep like my ol' Grand Dad...not [EMAIL PROTECTED] |screaming in terror like his passengers. roger.ecn.purdue.edu/~branden/ | pgpdBWJx5F14l.pgp Description: PGP signature
Re: RBL report..
On Wed, Mar 29, 2000 at 11:06:19PM +0200, Nils Jeppe wrote: > Hey, please leave me out of that ;-) But would you please provide me with > a link for DUL so I can finally check out what it's all about? Leave you out of what? I mailed the list, not you personally. > But the points about ORBS are still valid, no matter what DUL is. I wasn't talking about ORBS, I was talking about DUL. I haven't visited the DUL site in quite some time, but IIRC it is <http://maps.vix.com/dul/>. -- G. Branden Robinson|The errors of great men are venerable Debian GNU/Linux |because they are more fruitful than the [EMAIL PROTECTED] |truths of little men. roger.ecn.purdue.edu/~branden/ |-- Friedrich Nietzsche pgpr0GBrqeTJb.pgp Description: PGP signature
Re: RBL report..
On Wed, Mar 29, 2000 at 01:15:27PM -0800, Larry Gilbert wrote: > Rather than contribute to the flame war, I would like to ask a question. > Apologies if this is a total rookie question. > > Why is murphy.debian.org not adding a "Received:" header to show where > messages are originating? This information is useful when trying to > track down actual spammers. Is this being deliberately omitted or does > qmail just normally not include this info? Some MTA's -- and I don't know which ones -- apparently choke if there is more than n bytes' worth of Received: headers. So, as I understand it, these are stripped out by murphy to help make sure the list mails get to all the recipients. A person who runs an SMTP listener on their own box could, of course, be sure to run a non-broken MTA, but some people don't do that because they've been intimidated into using a smarthost, which might run just such a broken MTA. The anti-spam bigots enjoy seeing catch-22's like this. DoS attacks in the name spam prevention is their favorite sport. After all, no REAL people (read: people with single-user machines and nailed-up IP's) get hurt by such tactics. -- G. Branden Robinson|I must despise the world which does not Debian GNU/Linux |know that music is a higher revelation [EMAIL PROTECTED] |than all wisdom and philosophy. roger.ecn.purdue.edu/~branden/ |-- Ludwig van Beethoven pgp81cnkM57uV.pgp Description: PGP signature
Re: RBL report..
On Thu, Mar 30, 2000 at 07:58:22AM +1000, Craig Sanders wrote: [snip] Why did you CC me? I read the list. Please control yourself. -- G. Branden Robinson| The basic test of freedom is perhaps Debian GNU/Linux | less in what we are free to do than in [EMAIL PROTECTED] | what we are free not to do. roger.ecn.purdue.edu/~branden/ | -- Eric Hoffer pgp3q3PMqdtXn.pgp Description: PGP signature
Re: RBL report..
On Thu, Mar 30, 2000 at 01:25:03AM +0200, Nils Jeppe wrote: > > Branden: You might consider getting a static. > > The only way to live, imho. ;-) You guys can stop CC'ing me any day now; I read the lists. And BTW, I've stated several times that I *do* have a static IP. I suppose you guys are too busy disregarding my messages and spamming my inbox to have noticed that. -- G. Branden Robinson|Experience should teach us to be most on Debian GNU/Linux |our guard to protect liberty when the [EMAIL PROTECTED] |government's purposes are beneficent. roger.ecn.purdue.edu/~branden/ |-- Louis Brandeis pgplZmFwlWEoi.pgp Description: PGP signature
Re: RBL report..
On Thu, Mar 30, 2000 at 10:34:05AM +1000, Craig Sanders wrote: > On Thu, Mar 30, 2000 at 02:17:55AM +0200, Nils Jeppe wrote: NILS JEPPE, CRAIG SANDERS: PLEASE STOP CC'ING ME ON LIST MAILS. -- G. Branden Robinson| The greatest productive force is human Debian GNU/Linux | selfishness. [EMAIL PROTECTED] | -- Robert Heinlein roger.ecn.purdue.edu/~branden/ | pgpkywWHZ3wJG.pgp Description: PGP signature
Re: RBL report..
On Thu, Mar 30, 2000 at 01:44:24PM +0200, David N. Welton wrote: > Is there any kind of database to filter out time-wasting, vitriolic > arguments full of personal attacks, about things that have nothing to > do with Debian? Sure: :0: * ^X-Mailing-List: <[EMAIL PROTECTED]>.* /dev/null -- G. Branden Robinson| Debian GNU/Linux | Please do not look directly into laser [EMAIL PROTECTED] | with remaining eye. roger.ecn.purdue.edu/~branden/ | pgpoZgurLvGPn.pgp Description: PGP signature
