Re: Bug#60753: mutt: /etc/Muttrc should not use colors
The /etc/Muttrc in the mutt package makes a fruit salad of mutt. Most people like it. BTW, the default key bindings in mutt are horribly broken. No key does what someone would expect. that depends on what you're used to. if you've been using elm for years then mutt's key binding are perfectly 'natural' i used pine for years before switching to mutt. took me several days to re-train my fingers for the right keys, but the effort was worth it. i tried using the pine emulation bindings but they were more trouble for me than just learning the mutt keys. i've been using mutt for long enough now that pine's key bindings seem clumsy and awkward. No way, there's no room for discussion. Up and down arrow keys doesn't scroll a message ap down? Pg-down advancing to next message? The key binding are so insame that prevent people (newbies) fom using mutt, they first must to learn how to change those defaults to something acceptable.
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Sun, Mar 19, 2000 at 09:04:24PM -0300, Nicolás Lichtmaier wrote: The /etc/Muttrc in the mutt package makes a fruit salad of mutt. Most people like it. BTW, the default key bindings in mutt are horribly broken. No key does what someone would expect. that depends on what you're used to. if you've been using elm for years then mutt's key binding are perfectly 'natural' i used pine for years before switching to mutt. took me several days to re-train my fingers for the right keys, but the effort was worth it. i tried using the pine emulation bindings but they were more trouble for me than just learning the mutt keys. i've been using mutt for long enough now that pine's key bindings seem clumsy and awkward. No way, there's no room for discussion. there's lots of room for discussion. you are inflating minor annoyances into end-of-the-earth disasters. Up and down arrow keys doesn't scroll a message ap down? yeah, that's annoying at first. you get used to it, though. to scroll up and down by a single line, use Enter (down) and Del (up). this is a reasonably common keybinding - i've seen other programs (including more) use the same. personally, i'd like to use the vi-keys 'j' and 'k' for next and prev messages as they do now, but the arrow keys for scrolling up and down within a message. i don't care enough about it though to write a patch...or even to submit a wishlist bug report. any change like that might make some new users happier but is bound to piss off long-time users when the program they have been using for years suddently starts behaving very differently after an upgrade. arrow keys suck, anyway. they are unreliable as any extra delays (e.g. lagged network link) can change the timing between the characters sent when an arrow key is pressed. if the timing changes too much, then you don't get an arrow key, you get ESC followed by garbage. the vi-like keystrokes are safer. they work no matter how lagged your net link is. Pg-down advancing to next message? PgDn scrolls down the message, as expected. PgUp scrolls back up. the only annoying thing is that if you are already at the end of a message, then PgDn takes you to the next message. this should be optional behaviour. maybe it already is...it has never annoyed me enough to find out. The key binding are so insame that prevent people (newbies) fom using mutt, they first must to learn how to change those defaults to something acceptable. it's not that bad. if newbies can pick up emacs' horribly contorted key bindings then mutt's a doddle. craig -- craig sanders
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
-BEGIN PGP SIGNED MESSAGE- I agree. Mutt should by default be much more like pine. I like all my multiple folders, each containing the mail from one mailing list, and I like being able to easily navigate between them like pine allows. - --sig-- Real Programmers consider what you see is what you get to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a you asked for it, you got it text editor -- complicated, cryptic, powerful, unforgiving, dangerous. On Sun, 19 Mar 2000, [iso-8859-1] Nicolás Lichtmaier wrote: The /etc/Muttrc in the mutt package makes a fruit salad of mutt. Most people like it. BTW, the default key bindings in mutt are horribly broken. No key does what someone would expect. -- a href=http://master.debian.org/~krooger;debian/a To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBONV9NMK9HT/YfGeBAQHWLwQAlrwhELmKOrpkNnWrsIixfoD3DmHv0MA1 6RgIhlcguNimAJ1IeZjv1x4vAGUnP1ilp94Nyv/llj7g40iz1um3HTTJ4uUiSYFZ H6hMVt3PMCc7oHhwECLEf9C09x83i50TxZvAi51u1DXt2jtolQCEyytUmfJta49J ueDn3AQlu/o= =I1qL -END PGP SIGNATURE-
ITP: javawrapper
Hi, I intend to package javawrapper. Package: javawrapper Version: 1.0-1 Section: utils Priority: optional Description: A wrapper for kernel execution of Java programs javawrapper uses the binfmt_misc feature of newer Linux kernels to execute a Java class file directly simply by supplying its filename on the command line like a normal executable. It also correctly handles classes contained in packages. I'm also the upstream maintainer for this package, and the source is already being distributed in the kernel documentation tree. I'm not yet a developer, so I'm looking for a sponsor - please mail me if you want to help! Thanks, -- Colin Watson [EMAIL PROTECTED]
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Sun, Mar 19, 2000 at 05:21:55PM -0800, Jonathan Walther wrote: I agree. Mutt should by default be much more like pine. I like all my multiple folders, each containing the mail from one mailing list, and I like being able to easily navigate between them like pine allows. huh? mutt's folder navigation/selection ability is much better than pine's. when selecting a folder to go to (or to save messages to), you've got a prompt with command-line history/recall/edit. you can also press TAB and get a selectable list of all mail folders in mutt's CWD. press TAB again and you get a list of all defined incoming mailboxes. mutt also lets you access mail folders anywhere on your disk, and not just in ~/mail. e.g. run mutt -f /var/spool/mail/www-data as root (to check the bounces from poorly written cgi formmail scripts)...you can't do that in pine without copying the file to /root/mail or making a symlink. craig ps: if you prefer pine, then just use it. there's no need to make every mail client as bad as pine...some of us like mutt the way it is and don't want to see it mangled into an awkward pine clone. -- craig sanders
[transcript] source package formats
[ This is a transcript of a conversation on the Debian developer irc channel. Note that Diziet is Ian Jackson. This transcript has been edited for clarity and to remove other simulantaneous conversations. ] Overfiend since both you dpkg guys are here. Overfiend Can I ask for something? How about a flag in the .dsc that tells dpkg-source not to untar the .orig? wichert rmt: you do NOT mail unsuspecing people 4Mb of stuff Overfiend That would help with pristine source packages and dbs-type stuff wichert Overfiend: how about a new source format? Overfiend wichert: as long as it lets me do what I want seeS Is this correct? wichert Overfiend: okay. now give me 48-hour days and lots of money and I'll make it happen Overfiend wichert: bah. Overfiend I asked for what I did because I'd like to see it in woody Overfiend a new source format, I won't see in woody :) rcw Overfiend: wichert and guy have had a new dsc format cooking for at least a year Diziet Surely the problem is that dpkg-source trusts the .tar.gz less than the untarred original source ? wichert rcw: oh? we do? rcw wichert: I certainly remember reading something about it about 6 months ago Diziet If when you did dpkg-source --build it should include the original .tar.gz. Overfiend Diziet: eh? I just want to delay the untarring of the upstream tarball until the rules file is run Diziet Or does it not do that already ? rcw wichert: maybe it wasn't you wichert rcw: that might be klee's stuff Overfiend rcw: besides, Guy hasn't been SEEN for at least a year :-/ wichert he already did that Overfiend he and Brian White cancelled each other out about the time of glider's fuckup of the slink archive Diziet overfiend: I don't understand. The .orig.tar.gz nees to be untarred and patched before the debian/rules exists. Are you talking about at unpack time ? rcw Overfiend: details Overfiend Diziet: no, it doesn't, and in fact we have several packages that don't do it that way Overfiend Diziet: sendmail, glibc, xfree86, ... Diziet overfiend: What ?? I'm very confused now. Diziet overfiend: The debian/rules is in the .diff.gz, right ? Overfiend Diziet: the orig.tar.gz just contains another tarball in a subdirectory Joey Diziet, these pkg's use redhat type style Joey Diziet: orig.tgz contains an orig, and diffs that a applied during debian/rules wichert what I'ld like is a .dsc that lists one or more .orig.tar.gz's, and a tar of debian/ which can include patches Overfiend The .diff.gz's for these packages are basically just tar'ed up debian/ dirs masquerading as diffs Diziet Wergh, I've just unpacked the sendmail dsc and it's well weird. Overfiend wichert: aye rcw diziet: grab the gnome-napster source package and let doogie's dbs system soak into your head. it's a trip wichert and debian/rules or something else can apply those patches at buildtime, no need to clutter the rest with that Overfiend rcw: no, don't tell him that Culus_ rcw: Better than, say, acid? :P Overfiend diziet will corner doogie and demoralize him out of the project :-P rcw Culus: much better, and cheaper Overfiend like he tried to do with Culus for writing in C++ :) rcw Culus: plus every time you look at it you get a bigger trip, it's addicting Diziet overfiend: This package is totally fucked. I can't edit the source and then dpkg-source --build it ! wichert I've also decided that conditional patches are probably the wrong approach * Overfiend notes that the number of compiler warnings in X has not appreciably decreased from 3.3.6 to 4.0 Overfiend diziet: what package? Diziet sendmail Overfiend ah Diziet I can't even _read_ the source without executing debian/rules. Overfiend diziet: well, no, you can't, because people abuse the shit out of that system and cause monolithic patches Overfiend diziet: like when I inherited XFree86 Diziet overfiend: Err, wot ? Overfiend diziet: 500k of patches, not separated by function or anything else Diziet What do you mean by monolithic patches ? Overfiend a nightmare to deal with Overfiend diziet: duh. .diff.gz Overfiend it has debian/ + all patches to upstream rolled into one Diziet That's what a version control system is for, right ? Overfiend diziet: you can lead developers to cvs but you can't make them commit Diziet Why do the X packages have such a large .diff.gz ? netgod Overfiend: heh Overfiend diziet: you get a snowball effect of acculumating, unrelated patches Overfiend diziet: because we patch the shit out of it Diziet Well, if they don't like having a single .diff.gz like that then they should use CVS. Making packages that people can't edit is not helpful ! nick Overfiend: do you edit diff files? Diziet overfiend: 500K?! That takes some coding ! Overfiend diziet: oh well, I'll let you and wichert duke this out, what he proposed will make me happy Diziet wichert: What are you proposing ? Overfiend diziet: we didn't originate most of them, we just assimilated them Culus_ wichert: What now? Overfiend diziet: a lot of
Re: Release-critical Bugreport for March 18, 2000
MoiN On Sat, Mar 18, 2000 at 09:46:25AM -0600, BugScan reporter wrote: Package: gnofin (debian/main) Maintainer: Torsten Landschoff [EMAIL PROTECTED] 60614 LANG=de_DE gnofin does weird things [...] Package: gnucash (debian/main) Maintainer: Tyson Dowd [EMAIL PROTECTED] [...] 60615 gnucash: LANG=de_DE does weird things The bug seems to be fixed in woody. Perhaps that version should go into frozen, too? Changelog says it includes a lot of bugfixes. If these bugs can't be solved for potato I suggest the following wrapper (taken from /usr/bin/X11/netscape): --8-- cut here --8-- #!/bin/sh # # Fix locale problems. # # If the locale uses a decimal separator other than a point printf # will complain and it will not return 1.0 # pnt=$(printf %1.1f 1 2/dev/null) if [ $pnt != 1.0 ]; then # echo 1.0 - $pnt # Perhaps we have a dangerous value for LANG or LC_NUMERIC. Let's # try a safe value for LC_NUMERIC. LC_NUMERIC=C export LC_NUMERIC pnt=$(printf %1.1f 1 2 /dev/null) fi if [ $pnt != 1.0 ]; then # No, it is LC_ALL which is bad. Set LC_*=$LC_ALL for every category # (as expected) except LC_NUMERIC, and then unset LC_ALL. LC_COLLATE=$LC_ALL LC_CTYPE=$LC_ALL LC_MESSAGES=$LC_ALL LC_MONETARY=$LC_ALL LC_TIME=$LC_ALL unset LC_ALL export LC_ALL LC_COLLATE LC_CTYPE LC_MESSAGES LC_MONETARY LC_CTIME fi exec /usr/bin/gnofin --8-- cut here --8-- Ingo -- Windows, me?
ITP: eog
Hello, I will be packaging eog (Eye of Gnome). Package: eog Priority: optional Section: graphics Version: 0.2-1 Description: The Eye of Gnome graphics viewer and cataloging program Gnome is the GNU Network Object Model Enviroment . The Eye of Gnome, an image viewer program. It is meant to be a fast and functional image viewer as well as an image cataloging program. -dan -- Dan Nguyen | It is with true love as it is with ghosts; [EMAIL PROTECTED] | everyone talks of it, but few have seen it. [EMAIL PROTECTED]| -Maxime De La Rochefoucauld 25 2F 99 19 6C C9 19 D6 1B 9F F1 E0 E9 10 4C 16 pgpLqJqxm83RY.pgp Description: PGP signature
Re: ITP: eog
On Mon, 20 Mar 2000, Dan Nguyen wrote: Hello, I will be packaging eog (Eye of Gnome). Package: eog Priority: optional Section: graphics Version: 0.2-1 Description: The Eye of Gnome graphics viewer and cataloging program Gnome is the GNU Network Object Model Enviroment . The Eye of Gnome, an image viewer program. It is meant to be a fast and functional image viewer as well as an image cataloging program. Bzzt. Not a description. BEGIN GEEK CODE BLOCK Version: 3.12 GCS d- s: a-- c+++ UL P+ L !E W+ M o+ K- W--- !O M- !V PS-- PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z? -END GEEK CODE BLOCK- BEGIN PGP INFO Adam Heath [EMAIL PROTECTED]Finger Print | KeyID 67 01 42 93 CA 37 FB 1E63 C9 80 1D 08 CF 84 0A | DE656B05 PGP AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG -END PGP INFO-
Re: ITP: eog
On Mon, Mar 20, 2000 at 12:12:45AM -0600, Adam Heath wrote: On Mon, 20 Mar 2000, Dan Nguyen wrote: Hello, I will be packaging eog (Eye of Gnome). Package: eog Priority: optional Section: graphics Version: 0.2-1 Description: The Eye of Gnome graphics viewer and cataloging program Gnome is the GNU Network Object Model Enviroment . The Eye of Gnome, an image viewer program. It is meant to be a fast and functional image viewer as well as an image cataloging program. Bzzt. Not a description. Yes... sorry. That's what I get for working late... Here's try 2. Description: Eye of Gnome graphics viewer program eog or the Eye of Gnome is a graphics viewer for GNOME which uses the gdk-pixbuf library. It can deal with large images, and zoom and scroll with constant memory usage. The goal is a standard graphics viewer for future releases of Gnome. -- Dan Nguyen | It is with true love as it is with ghosts; [EMAIL PROTECTED] | everyone talks of it, but few have seen it. [EMAIL PROTECTED]| -Maxime De La Rochefoucauld 25 2F 99 19 6C C9 19 D6 1B 9F F1 E0 E9 10 4C 16
Re: [transcript] source package formats
On Sun, 19 Mar 2000, Joey Hess wrote: [ This is a transcript of a conversation on the Debian developer irc channel. Note that Diziet is Ian Jackson. This transcript has been edited for clarity and to remove other simulantaneous conversations. ] Thanks Joey for posting that. Ok, now for some fun stuff. In the transcript, it is mentioned that I wrote dbs. It is a multi-tarball, multi-patch system, that is currently in use by several pkgs. However, it has its drawbacks, the 2 most glaring that it hides the source in subtrees, all packed up, and that it doesn't extract into pkg-ver directly. So, I decided to do something about that finally. Below is an example dsc format that I have come up with. === Source: xawtv Format: 2.0 Version: 3.07-2 Binary: xawtv, fbtv, radio, streamer, webcam, xawtv-tools Maintainer: Adam Heath [EMAIL PROTECTED] Architecture: any Standards-Version: 3.1.1 Build-Depends: debhelper, autoconf, xlib6g-dev, xaw3dg-dev, libjpeg62-dev, xbase-clients Files: 93c152103ca081bd993bb216952a61be 293809 xawtv_3.07.orig.tar.gz c2b6e4c24fac3bb6c4318d3281929dba 16046 xawtv_3.07-2.tarballs.tar.gz 05a79461096e2a1eefaad9ef8d28c421 2452 xawtv_3.07-2.patches.tar.gz Patches: 4177fc4c79df8d83eec24e5444064df5 455 000_fbtv_fhs.diff eb611f579f3e169c9f0007d76e10acf9 1185 001_i2c_header_fix.diff 6f4317ba2194792a8b989542095164b2 1048 002_Makefile.in.sanity.diff e32cec754188fd133da14740ba91352b 4467 003_autoconf_parallel_compile.diff Tarballs: 49d09b3edefb8279dc0ae1df3a42d15b 15908 debian.tar.gz === You'll note the addition of 3 fields(Format, Patches, and Tarballs), and the different files specified for the files field. The existance of a Format field can be used to see that this is a new format source package. Currently, my script doesn't use that. It looks for a .diff.gz, and if found, assumes an old format. The current format has 3 files that are distributed with a source package. The .orig.tar.gz, a .diff.gz, and a .dsc. With this new format, it increases that count by 1. I couldn't see a way around this however, while still keeping with my intended outcome. The entries listed in the Patches field are contained in the .patches.tar.gz file. Those listed in the Tarballs field are listed in the .tarballs.tar.gz file. The files listed are extracted in the sort order produced by ls, so naming is important. There is also no distinction between upstream and debian only patches. I currently have a script that can parse this new format, and extract both old and new format archives. It doesn't yet support building a .dsc from a directory. Also, I currently only support tar and gz, with plans for ar, zip, jar, Z, bz, bz2, and whatever else exists that we can use in Debian. A transcript of the scripts output follows: === $ ./unpack xawtv_3.07-2.dsc Extracting xawtv in xawtv-3.07. Extracting tarball debian.tar.gz. Applying patch 000_fbtv_fhs.diff. Applying patch 001_i2c_header_fix.diff. Applying patch 002_Makefile.in.sanity.diff. Applying patch 003_autoconf_parallel_compile.diff. === BEGIN GEEK CODE BLOCK Version: 3.12 GCS d- s: a-- c+++ UL P+ L !E W+ M o+ K- W--- !O M- !V PS-- PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z? -END GEEK CODE BLOCK- BEGIN PGP INFO Adam Heath [EMAIL PROTECTED]Finger Print | KeyID 67 01 42 93 CA 37 FB 1E63 C9 80 1D 08 CF 84 0A | DE656B05 PGP AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG -END PGP INFO-
Re: ITP: eog
On Mon, 20 Mar 2000, Dan Nguyen wrote: On Mon, Mar 20, 2000 at 12:12:45AM -0600, Adam Heath wrote: On Mon, 20 Mar 2000, Dan Nguyen wrote: Description: The Eye of Gnome graphics viewer and cataloging program Gnome is the GNU Network Object Model Enviroment . The Eye of Gnome, an image viewer program. It is meant to be a fast and functional image viewer as well as an image cataloging program. Bzzt. Not a description. Yes... sorry. That's what I get for working late... Here's try 2. Description: Eye of Gnome graphics viewer program eog or the Eye of Gnome is a graphics viewer for GNOME which uses the gdk-pixbuf library. It can deal with large images, and zoom and scroll with constant memory usage. The goal is a standard graphics viewer for future releases of Gnome. applaud I hate all those gnome pkgs that are 2 lines long. BEGIN GEEK CODE BLOCK Version: 3.12 GCS d- s: a-- c+++ UL P+ L !E W+ M o+ K- W--- !O M- !V PS-- PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z? -END GEEK CODE BLOCK- BEGIN PGP INFO Adam Heath [EMAIL PROTECTED]Finger Print | KeyID 67 01 42 93 CA 37 FB 1E63 C9 80 1D 08 CF 84 0A | DE656B05 PGP AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG -END PGP INFO-
Re: [transcript] source package formats
On Mon, 20 Mar 2000, Adam Heath wrote: You'll note the addition of 3 fields(Format, Patches, and Tarballs), and the different files specified for the files field. The existance of a Format Having a .tarballs.tar.gz seems rather pointless, just have all the tars seperate - as does including the md5s for patches in the .dsc, have a manifest file in patch tar. Though the point of that does rather elude me. Jason
Re: Anyone intents to package Guppi
On Fri, 17 Mar 2000, Bas Zoetekouw wrote: Accoring to http://www.gnome.org/guppi/#get, Cesar Talon [EMAIL PROTECTED] has already packaged it. The deb is at ftp://ftp.gnome.org/pub/guppi/Debian Any reason why this is not included in woody? Kind regards Andreas.
Re: Apt-Problem
On Fri, 17 Mar 2000, Jason Gunthorpe wrote: On 18 Mar 2000, Brian May wrote: I believe the original poster used dpkg -i to install the same copy that apt had downloaded - ie only one copy ever downloaded. Then dpkg should have failed to install it since it is a truncated file. No all the files which dselect wasn't able to install (via apt) were installable via dpkg -i Not sure about libtool, but have a look at bugs 60339 and 60399 for a similar problem with man-db. This was posted as another thread on debian-devel. This looks like something entirely different I used libtool and man-db as examples to show that the problem was caused by apt-get und to post short errormessages (instead of the output after failing to install 42 packages). I repeat: All packages were installable with dpkg -i after apt-get was unable to install them. Using another mirror solved this problem. Two different mirrors in Germany were affected by this. Kind regards Andreas.
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Sun, Mar 19, 2000 at 05:21:55PM -0800, Jonathan Walther wrote: I agree. Mutt should by default be much more like pine. I like This sounds like a lot of recent threads on debian-devel -- the defaults should suite MY PREFERENCES! That's why they're defaults -- you can change them. Personally I can't stand Mutt's default colours (green on blue? ugh!) but the default keybinds are fine. I have a .muttrc which I copy around between all my accounts. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Apt-Problem
On Mon, 20 Mar 2000, Andreas Tille wrote: output after failing to install 42 packages). I repeat: All packages were installable with dpkg -i after apt-get was unable to install That doesn't mean anything, if the file was only 1 byte short chances are it would still be entirely valid, dpkg -i would take it, apt would not due to a size and md5 mismatch. Jason
Re: Apt-Problem
Jason == Jason Gunthorpe [EMAIL PROTECTED] writes: Jason On Mon, 20 Mar 2000, Andreas Tille wrote: output after failing to install 42 packages). I repeat: All packages were installable with dpkg -i after apt-get was unable to install Jason That doesn't mean anything, if the file was only 1 byte Jason short chances are it would still be entirely valid, dpkg -i Jason would take it, apt would not due to a size and md5 Jason mismatch. I have to agree with Jason here, I was confused. In this case the error is generating by apt-get, in my case the error was generated by dpkg. I will take Jason's word for it that a deb file with bytes missing can still be valid... -- Brian May [EMAIL PROTECTED]
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
I agree. Mutt should by default be much more like pine. I like This sounds like a lot of recent threads on debian-devel -- the defaults should suite MY PREFERENCES! That's why they're defaults -- you can change them. Personally I can't stand Mutt's default colours (green on blue? ugh!) but the default keybinds are fine. I have a .muttrc which I copy around between all my accounts. It's a tough issue, but there's certainly a line somewhere. And mutt does not have reasonable defaults. In the keyboard, each key has a function, there are lots of functions that are not directly in the keyboard, that's why each program has to invent a keybinding. But there are functions that *are* in the keyboard and so: PgUp - must scroll up a page, just that. PgDown - must scroll down a page Up Arrow - must scroll up a line Up Arrow - must scroll down a line Home - must go to the start of something End - must go to the end of something Using the Space and the Backspace keys for up and down movement is absurd, it's even stupid. Backspace is back-space. Those keybindings where thought for keyboards without arrows, and those keyboards no longer exists... Besides, configuration should always target the norma-naive user. The tough user can always edit a configfile.
Re: [transcript] source package formats
On Sun, 19 Mar 2000, Jason Gunthorpe wrote: On Mon, 20 Mar 2000, Adam Heath wrote: You'll note the addition of 3 fields(Format, Patches, and Tarballs), and the different files specified for the files field. The existance of a Format Having a .tarballs.tar.gz seems rather pointless, just have all the tars seperate - as does including the md5s for patches in the .dsc, have a manifest file in patch tar. Though the point of that does rather elude me. I had a tarballs.tar.gz to lessen the number of files to download. Altho, upon reflection, I could see that would increase bandwidth usage. A separate manifest file sounds good. Ok, well, I went and did all that. :) === $ ./unpack xawtv_3.07-2.dsc Extracting xawtv in xawtv-3.07. Extracting xawtv_3.07-2.debian.tar.gz in xawtv-3.07. Applying patch 000_fbtv_fhs.diff in xawtv-3.07. Applying patch 001_i2c_header_fix.diff in xawtv-3.07. Applying patch 002_Makefile.in.sanity.diff in xawtv-3.07. Applying patch 003_autoconf_parallel_compile.diff in xawtv-3.07. === === Files: 93c152103ca081bd993bb216952a61be 293809 xawtv_3.07.orig.tar.gz 49d09b3edefb8279dc0ae1df3a42d15b 15908 xawtv_3.07-2.debian.tar.gz fbb0a2fdc26934037ad11553f8f19814 2624 xawtv_3.07-2.diffs.tar.gz === The script looks for all files matching the pattern *.diffs.tar.gz(yes, it allows multiple patch archives. This could be used to share between sources), then everything else that matches *.tar.gz is placed into a tarballs variable. The first listed tarball is assumed to be orig.tar.gz, and special care is taken to ensure that it unpacks into a properly named directory. All other tarballs and patches are extracted/applied by cd'ing into the target directory first. Each .diffs.tar.gz contains a file named 'dsc' which holds the Patches field from the first version. Comments? Suggestions? ps: Yes, this script does have a good amount of error/sanity checking. It doesn't, however, clean up after itself(I hope to rectify this). BEGIN GEEK CODE BLOCK Version: 3.12 GCS d- s: a-- c+++ UL P+ L !E W+ M o+ K- W--- !O M- !V PS-- PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z? -END GEEK CODE BLOCK- BEGIN PGP INFO Adam Heath [EMAIL PROTECTED]Finger Print | KeyID 67 01 42 93 CA 37 FB 1E63 C9 80 1D 08 CF 84 0A | DE656B05 PGP AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG -END PGP INFO-
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Sun, Mar 19, 2000 at 09:04:24PM -0300, Nicolás Lichtmaier wrote: Up and down arrow keys doesn't scroll a message ap down? Nope. But that's the way it is in slrn, too: backspace and enter scroll the message text, and uparrow and downarrow scroll the message list. It's good once you get used to it, and that takes about five minutes. :) Pg-down advancing to next message? No, pgdn goes page down in the message text, and if it reaches the end, it goes on to the next message. Once again, similar to slrn, where space scrolls one page down in the message text, and if it reaches the end, asks you to proceed to the next message with another space. The key binding are so insame that prevent people (newbies) fom using mutt, they first must to learn how to change those defaults to something acceptable. IME it's completely the other way round: they like the mutt keybindings better. -- enJoy -*/\*- don't even try to pronounce my first name
Re: blue on black is unreadable (was Re: Bug#60753: mutt: /etc/Muttrc should not use colors)
On Mon, Mar 20, 2000 at 10:31:40AM +1100, Craig Sanders wrote: lynx has the same problem. hyper links are blue on black, which makes it very difficult to see where you are going. fixed with: COLOR:1:cyan:black COLOR:5:brightcyan:black I wonder who made up the default lynx colours... it is totally nauseating! the first think I do when installing new debian, I always reconfigure lynx to have saner colours (e.g. highlighted links are inverse) COLOR:0:lightgray:black COLOR:1:yellow:black COLOR:2:brightred:blue COLOR:3:green:black COLOR:4:magenta:black COLOR:5:blue:black COLOR:6:black:lightgray COLOR:7:magenta:cyan -- --- | Radovan Garabik http://melkor.dnp.fmph.uniba.sk/~garabik/ | | __..--^^^--..__garabik @ melkor.dnp.fmph.uniba.sk | --- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread!
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Mon, Mar 20, 2000 at 02:30:55AM -0600, Zed Pobre wrote: From my experiments with the above, only two things behave in a way that I would expect an unfamiliar user to find strange: asymmetry in PgUp/PgDown behaviour, and maybe UpArrow and DownArrow moving between messages instead of up and down single lines in a viewed message. That can be fixed with three lines: set pager_stop bind pager up previous-line bind pager down next-line These lines are great for a new mutt user. They really should be in the /etc/Muttrc file... at least commented out and documented. postinst could even mention that such sane bindings exist. LeftArrow goes to previous message when in paged view... so why does UpArrow? It's very intuitive to use UpArrow to scroll up the current screen. ditto for RightArrow/DownArrow. On the other hand, maybe the project really would find those three lines more convenient to have as defaults. How about it, folks, anyone in favor of adding the three lines above to the default /etc/Muttrc? Yes! -- Luca Filipozzi pgpbKfDHff2M7.pgp Description: PGP signature
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Mon, Mar 20, 2000 at 02:30:55AM -0600, Zed Pobre wrote: Besides, configuration should always target the norma-naive user. The tough user can always edit a configfile. From my experiments with the above, only two things behave in a way that I would expect an unfamiliar user to find strange: asymmetry in PgUp/PgDown behaviour, and maybe UpArrow and DownArrow moving between messages instead of up and down single lines in a viewed message. That can be fixed with three lines: set pager_stop bind pager up previous-line bind pager down next-line [...] On the other hand, maybe the project really would find those three lines more convenient to have as defaults. How about it, folks, anyone in favor of adding the three lines above to the default /etc/Muttrc? nope, not me. i am in favour of adding them as comments in /etc/Muttrc, along with an explanation of what they do and why someone might choose to uncomment them - a summary of your comments in this thread would be perfect. craig -- craig sanders
Re: Apt-Problem
On Mon, 20 Mar 2000, Jason Gunthorpe wrote: That doesn't mean anything, if the file was only 1 byte short chances are it would still be entirely valid, dpkg -i would take it, apt would not due to a size and md5 mismatch. Do you expect a file of size 1 byte to install and work without problems? I repeat: The files I've got worked and are working up to this very moment. I havn't any problems with them except that apt-get refused to install them. Kind regards Andreas.
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
In article [EMAIL PROTECTED], Marco d'Itri [EMAIL PROTECTED] wrote: On Mar 19, [EMAIL PROTECTED] wrote: For an example why I think this is really a bug with severity normal, and not a wish or feature request, see http://duckman.blub.net/~wouter/muttdefaults.png Seen. My xterms are *very* different, even with a white background. Looks like wh needs to upgrade his ncurses-base and ncurses-term packages. Perhaps xterm as well. Mike. -- How do you eat soup in the matrix...?
Re: Apt-Problem
On 20 Mar 2000, Brian May wrote: I have to agree with Jason here, I was confused. In this case the error is generating by apt-get, in my case the error was generated by dpkg. I will take Jason's word for it that a deb file with bytes missing can still be valid... OK, I take the word as you, but what should I do if I detect such kind of problem. Who should I inform and which information should I ship. By the way. Shouldn't dpkg at least warn that md5 sums are wrong? Kind regards Andreas.
bug postgresql-client
I am having trouble installing postgresql in woody. I try to install the postgresql package and it asks for postgresql-client. Postgresql-client gives the following error:- Sorry, but the following packages have unmet dependencies: postgresql-client: Depends: libreadlineg2 (= 2.1-13.5) but 2.1-12 is to be installed If I try to install libreadlineg2 it tells me that it is already the latest package. Please don't make me use mysql.. :/ Neil -- Neil Hunt HuntCorp Enterprises [EMAIL PROTECTED] 0414 306 238
Re: bug postgresql-client
Sorry, submitted where it should've gone.. Neil On Mon, Mar 20, 2000 at 05:57:13PM +0800, [EMAIL PROTECTED] wrote: I am having trouble installing postgresql in woody. I try to install the postgresql package and it asks for postgresql-client. Postgresql-client gives the following error:- Sorry, but the following packages have unmet dependencies: postgresql-client: Depends: libreadlineg2 (= 2.1-13.5) but 2.1-12 is to be installed If I try to install libreadlineg2 it tells me that it is already the latest package. Please don't make me use mysql.. :/ Neil -- Neil Hunt HuntCorp Enterprises [EMAIL PROTECTED] 0414 306 238 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Neil Hunt HuntCorp Enterprises [EMAIL PROTECTED] 0414 306 238
Re: Apt-Problem
On Mon, Mar 20, 2000 at 10:29:35AM +0100 , Andreas Tille wrote:
By the way. Shouldn't dpkg at least warn that md5 sums are wrong?
It can't. dpkg doesn't know the md5sum of the .deb.
Petr Cech
--
Debian GNU/Linux maintainer - www.debian.{org,cz}
[EMAIL PROTECTED]
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
[EMAIL PROTECTED] (Craig Sanders) wrote: On Sun, Mar 19, 2000 at 09:04:24PM -0300, Nicolás Lichtmaier wrote: Pg-down advancing to next message? PgDn scrolls down the message, as expected. PgUp scrolls back up. the only annoying thing is that if you are already at the end of a message, then PgDn takes you to the next message. this should be optional behaviour. maybe it already is...it has never annoyed me enough to find out. 'set pager_stop=yes'? The key binding are so insame that prevent people (newbies) fom using mutt, they first must to learn how to change those defaults to something acceptable. it's not that bad. if newbies can pick up emacs' horribly contorted key bindings then mutt's a doddle. FWIW, I picked up mutt's keybindings from pine inside two days. I don't find them a problem. -- Colin Watson [EMAIL PROTECTED]
ITP: javawrapper
Dear Colin, I intend to package javawrapper. Package: javawrapper Version: 1.0-1 Section: utils Priority: optional Description: A wrapper for kernel execution of Java programs javawrapper uses the binfmt_misc feature of newer Linux kernels to execute a Java class file directly simply by supplying its filename on the command line like a normal executable. It also correctly handles classes contained in packages. I'm also the upstream maintainer for this package, and the source is already being distributed in the kernel documentation tree. I'm not yet a developer, so I'm looking for a sponsor - please mail me if you want to help! I will be happy to sponsor javawrapper that I have used and installed locally. The challenge, as I see it, is to write an /etc/init.d/javawrapper script that ensures that binfmt_misc is installed and registers/unregisters javawrapper with the kernel. Sincerely, Kristoffer -- Kristoffer Høgsbro Rose, phd, prof.associé http://www.ens-lyon.fr/~krisrose addr. LIP, Ecole Normale Supérieure de Lyon, 46 Allée d'Italie, F-69364 Lyon 7 phone +33(0)4 7272 8642, fax +33(0)4 7272 8080 [EMAIL PROTECTED] pgp f-p: A4D3 5BD7 3EC5 7CA2 924E D21D 126B B8E0 [EMAIL PROTECTED],tug}.org
SuSe proxy suite
What happened to the ITP for it? I didn't see a package yet. Michael -- Michael Meskes | Go SF 49ers! Th.-Heuss-Str. 61, D-41812 Erkelenz| Go Rhein Fire! Tel.: (+49) 2431/72651 | Use Debian GNU/Linux! Email: Michael@Fam-Meskes.De | Use PostgreSQL!
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Mon, Mar 20, 2000 at 02:30:55AM -0600, Zed Pobre wrote: On Mon, Mar 20, 2000 at 04:46:04AM -0300, Nicol?s Lichtmaier wrote: It's a tough issue, but there's certainly a line somewhere. And mutt does not have reasonable defaults. In the keyboard, each key has a function, I (along with others) dispute that the defaults are not reasonable. Out of curiosity, I moved my .muttrc out of the way so I could examine the native keybindings. I concur. My .muttrc does not contain any new keybindings, and I work with mutt all day. It only contains colour changes and status line changes etc. Things where I don't expect others to like my preferences. Cheers Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [transcript] source package formats
On Mon, Mar 20, 2000 at 01:51:08AM -0600, Adam Heath wrote: Comments? Suggestions? You still owe me documentation for this :-) bug#52351 on xawtv. Cheers Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: [transcript] source package formats
Previously Adam Heath wrote: However, it has its drawbacks, the 2 most glaring that it hides the source in subtrees, all packed up, and that it doesn't extract into pkg-ver directly. You conveniently ignored Ian's biggest con: it does not gave you a way to get to the source as it is compiles without running a script. This is bad, since it means you have to run an untrusted script in order to get to the source. Imagine the unpack-rules doing something like sudo rm -rf /. Oops... Wichert. -- / Generally uninteresting signature - ignore at your convenience \ | [EMAIL PROTECTED]http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: [dickey@clark.net: Re: http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=59191]
On Fri, 17 Mar 2000, Darren O. Benham wrote: Anyway... there is a second problem you mentioned that deserves to be addressed. Bugs should either be dealt with by the maintainer (if they're involved with mods they made or the packaging) or the bugs are supposed to be forwarded upstream (with a patch if one is available). That is part of the Debian philosophy. Perhaps we should open the Bug System to upstream maintainers by adding a flag to every package. If this flag is on, reports are automatically forwarded to a given upstream email address. I'm sure many upstream authors would ask this flag to be enabled for their packages, even if this means a small percentage of received bugs happen to be packaging bugs which would not have to be forwarded in normal circumstances. Thanks. -- 1eecd7e6dc4c525a66434ff1e829bb20 (a truly random sig)
Re: Single architecture on -announce lists
[EMAIL PROTECTED] (Joey Hess) wrote: Ben Collins wrote: The lists already exist, they are just not used at all. Maybe it would be easier to keep just the one debian-devel-changes list to send to and write some extra procmail stuff into sending it to the write outlist. Well, we could just sign everyone who is currently subscribed to debian-devel-changes up to debian-devel-*-changes, and obsolete debian-devel-changes. Then post an announcement that people can easily selectively filter mail by unsubscribing from architectures they're not interested in. Although I guess that might mess with some people's mail filters, to change list names behind their backs.. A little, yes ... Couldn't we keep debian-devel-changes as is and simply copy the mail to debian-devel-*-changes, for backward compatibility? -- Colin Watson [EMAIL PROTECTED]
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Mon, Mar 20, 2000 at 02:30:55AM -0600, Zed Pobre wrote: On Mon, Mar 20, 2000 at 04:46:04AM -0300, Nicol?s Lichtmaier wrote: Using the Space and the Backspace keys for up and down movement is absurd, it's even stupid. Backspace is back-space. Those keybindings where thought for keyboards without arrows, and those keyboards no longer exists... Or for terminals without valid cursor-key translations, and those terminals and connections DO exist. Or for people who don't want to have their hands leave the home position, and those people DO exist. It also gets used in things like newsreaders (well, Gnus at least) where the cursor keys move something other than the text of the message being viewed. I almost exclusively use the spacebar to page down, and I sometimes use backspace to page backwards. Different != stupid, and I'd point out that your attitude is probably offending people by now. Indeed. Besides, putting too many changes into the default configuration is only going to irritate people - a package should probably behave much as a user familiar with the program from elsewhere would expect. Old users get confused, and new users get confusing help from old users. -- Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/ pgpd2BtnVEEIR.pgp Description: PGP signature
Re: [transcript] source package formats
On Sun, Mar 19, 2000 at 11:55:27PM -0700, Jason Gunthorpe wrote: On Mon, 20 Mar 2000, Adam Heath wrote: You'll note the addition of 3 fields(Format, Patches, and Tarballs), and the different files specified for the files field. The existance of a Format Having a .tarballs.tar.gz seems rather pointless, just have all the tars seperate - as does including the md5s for patches in the .dsc, have a manifest file in patch tar. Though the point of that does rather elude me. Yeah, tk would be a lot easier to build this way. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Libc6 functions such as wprintf() (widechar/multibyte/UNICODE support)
Ive been looking around the manual pages of wprintf and include files of the latest potato. Widechar/Multibyte support exist (wchar.h) but almost all the usefull function is not in the libc distribution of potato. Functions like wprintf that a vital is no where to be found and still they have manual pages for the function. Has the widechar/multibyte printing support been removed for som resone or just missed? Im hopeing for a quick response on this matter because its very VITAL for my project! -- Name:Work:Work phone:Mobile: Jerry Lundström DaCapo Infix AB +46 (0)31 - 710 72 00 +46 (0)739 87 60 53 Occupation:Knowledge: System Developer/Consult C/C++, COM/DCOM, ASP, SQL, PHP, MySQL, Linux/UNIX
motors for Washing Machine, Electrical Fan, Refrigerator, Fume Hood, Food Blender, etc
Yuanfeng Motor Company is a professional motor manufacturer and are dedicated to developing and researching high efficient products. Various types of motor with different specification are for Washing Machine, Electrical Fan, Refrigerator, Fume Hood, Food Blender, etc. All motors we manufacture are with high quality, high efficiency, high torque, low defect rate and low-noise stable quality. If interested, please contact us for full information. OEM orders are welcome. contact:[EMAIL PROTECTED] __ Above supply information is provided by Gold Line Business Information Service Company. Our service mainly includes: to help all the manufacturers in mainland of China with sales promotion and overseas marketing. And meanwhile we offer Chinese market and products information consulting service for foreign buyers or importers. If you are now looking for any product in good quality and at favorable price, it is the great opportunity to be of your service with manufactures and products as well as other related information. Any inquiry, please feel free to contact us know. Gold Line Business Information Service Company Limited Address: 7/F, Science Technology Center, No. 3, Nanxing San Road, Guicheng District, Nanhai City 528200, Guangdong Province, China Tel: +86-757-6336 141 / 6239 656 Fax: +86-757-6336 141 E-mail: [EMAIL PROTECTED] Contact Person: Mr Wang Dong --´ËÓʼþÓÉÍòÏó»Ã¾³³öÆ·µÄÓʼþÅú·¢Õ¾·¢ËÍ--- ÍòÏó»Ã¾³Óлú·¿¾ÖÓòÍø¹ÜÀíÈí¼þÕÂÓãÖúÀí¡¢ÓʼþÅú·¢Õ¾¡¢ ¶ÔÑÛÉñ¹¦¡¢Ð£Ô°³©ÏëÇúµÈÈí¼þ£¬»¶Ó¹âÁÙÏÂÔØ£º http://cookey.126.com »¶ÓʹÓà http://2888.com Ãâ·Ñµç×ÓÐÅÏä¼°·ÖÀàÐÂÎÅ¡¢¸öÐÔ»¯±¨¿¯¡¢ ¾«ÃÀºØ¿¨¡¢×Ô¶¯ÃØÊé¡¢ËæÉíÐÅÏä¡¢ËæÉí±Ê¼Ç¡¢¹©Çó¡¢ÕÐƸÇóÖ°ÐÅÏ¢µÈ¡£ -
Re: ITP: solfege
Tom, I'm looking forward to it very much. This is on Debian Jr.'s list of programs suitable for children that we'd like to see packaged. (My children are not yet old enough to make use of it, I think, but it won't be long.) I'm a programmer and musician. I could've used something like this back in high school when I studied music theory. Ben On Sun, 19 Mar 2000, Tom Cato Amundsen wrote: Solfege is an eartraining program for GNOME written in python. (http://solfege.sourceforge.net) I'm the author of the program and Olav Stetzer will be sponsoring me. The package will be called solfege Tom Cato Amundsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] Debian http://www.debian.org [EMAIL PROTECTED] [ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] [ gpg key fingerprint = 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]
Re: Debian and GNOME, partnership with Helixcode?
Hello guys, I just got forwarded a few messages from a discussion that is going on at the Debian lists, let me reply: First of all, this fragment --which started the whole debate-- is completely wrong: I assisted today to a conference by Miguel de Icaza here in Madrid, it seems he is running a new business namde Helixcode (http://www.helixcode.com) which will be working for GNOME. In the conference he said that the GNOME developers do not want to make debian packages because they are too difficult. But he also did not understand why distributions carry out old version of GNOME. What I said was that Helix could not make GNOME packages for Debian for the Helix GNOME Preview Release 1, not that the GNOME developers did not want to make them. I am going to repeat because it seems Javier did not understand even when I spoke in spanish: Helix Code could not produce Debian packages for Helix GNOME Preview 1 because it was too hard to get them on time. The GNOME project is a completely different entity. GNOME is the project to bring new technologies to Unix Helix Code is the company that is writing GNOME-based productivity applications for GNOME, and happens to have a binary distribution of GNOME for various GNU/Linux distributions. Helix Code is the one that could not produce the Debian packages on time. The GNOME project does not produce binaries. Not for Debian, not for Red Hat, not for anything else. From time to time we get .spec files and debian/ directories, but we do not maintain them, nor do we keep track of them. More: There seems to be a lack of communication. Either the Debian packagers are not contributing their work upstream or the Gnome hackers are refusing to take it. I'm sure neither group really wants that. See my comment previously. I really think that if a developer can't follow closely a distribution, she should let the distribution maintainers do the work. Miguel said they didn't make .debs because it was too hard. What is so hard that intelligent people can't follow? We have lots of documentation. development tools like dh_make and debhelper, QA tools like Lintian, lot's and lots of prior art. I have to point out a few things: 1. Debian directories exist for all packages that the Debian maintainers have requested to maintain in the GNOME CVS. 2. I do not have anything to do with those packages. 3. My comment on Debian packages that I made in the Spain conference was that Helix did not release in the Helix GNOME Preview 1 GNOME packages for Debian because it was too hard for us to make them. We did not have the resources to attack the problem, although that was one of the original plans. If you want to help the Helix hackers to get Helix GNOME packages for Debian, then subscribe to the spidermonkey mailing list at Helix Code, and offer your help to our developers. Our developers (the Helix developers) were working around the clock (Jacob even spent one day 56 hours awake) to get Helix GNOME out. And yes, supporting Debian for preview 1 would have just delayed Preview 1 a few weeks for no good reason. In the future, there will be time to handle Debian. I do not know why you guys did not contact me directly if you had any doubts. Miguel.
Re: [dickey@clark.net: Re: http://cgi.debian.org/cgi-bin/bugreport.cgi?bug=59191]
Le Mon, Mar 20, 2000 at 03:38:34PM +0100, Santiago Vila écrivait: Perhaps we should open the Bug System to upstream maintainers by adding a flag to every package. If this flag is on, reports are automatically forwarded to a given upstream email address. I'm sure many upstream authors would ask this flag to be enabled for their packages, even if this means a small percentage of received bugs happen to be packaging bugs which would not have to be forwarded in normal circumstances. I can't believe it, usually I don't agree with you but here I do ! That's a pretty good idea. I'm sure that for most of the packages, there aren't that much Debian specific bugs and since the author can choose I don't see a reason not to implement it. Even better anybody should be able to register himself in the BTS so that he'll get all the bugreports for a specific package (or source package, but that's something more difficult to implement I guess) ... this would allow several maintainer to maintain the same package without using an alias or a list. Adding to this the possibility to have architecture specific bugs, and distribution specific bugs, and we'll have the best BTS around the world. Ok, who does it ? ;-) Cheers, -- Raphaël Hertzog 0C4CABF1 http://tux.u-strasbg.fr/~raphael/ pub CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd Formations Linux et logiciels libres : http://www.logidee.com /pub
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
Hamish Moffatt ([EMAIL PROTECTED]) wrote:
Personally I can't stand Mutt's default colours (green on blue? ugh!)
but the default keybinds are fine. I have a .muttrc which I copy
around between all my accounts.
i bet most people do. probably a .bash{rc,_profile} and .joerc too. that's
why everything stores globals and per-user settings seperatly. i can't
believe anyone even suggested that the system wide defaults be changed to
suit one user's preferences. i'd have to say that the system Muttrc is
pretty damn ugly tho. my .muttrc changes only a few settings besides color.
--
(jacob kuntz)[EMAIL PROTECTED],underworld}.net [EMAIL
PROTECTED]
(megabite systems) think free speech, not free beer. (gnu foundataion)
Re: [transcript] source package formats
On Mon, 20 Mar 2000, Wichert Akkerman wrote: Previously Adam Heath wrote: However, it has its drawbacks, the 2 most glaring that it hides the source in subtrees, all packed up, and that it doesn't extract into pkg-ver directly. You conveniently ignored Ian's biggest con: it does not gave you a way to get to the source as it is compiles without running a script. This is bad, since it means you have to run an untrusted script in order to get to the source. Imagine the unpack-rules doing something like sudo rm -rf /. Oops... Are you being purposefully obtuse, or just not following along? I mention what the current state of dbs is. That was a summary for those who couldn't see that in the transcript. That was NOT a summary of what this new script does. You complain about problems in the old dbs, without commenting at all about anything in this new thing I have come up with. Ian's complaint was that he would have to check each src pkg that comes with dbs, to make sure it was secure. This new way puts dbs-like functionality into dpkg-source itself, so he would only have to check it once. I say again. This is a .dsc unpacker, in the same way dpkg-source is. BEGIN GEEK CODE BLOCK Version: 3.12 GCS d- s: a-- c+++ UL P+ L !E W+ M o+ K- W--- !O M- !V PS-- PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z? -END GEEK CODE BLOCK- BEGIN PGP INFO Adam Heath [EMAIL PROTECTED]Finger Print | KeyID 67 01 42 93 CA 37 FB 1E63 C9 80 1D 08 CF 84 0A | DE656B05 PGP AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG -END PGP INFO-
Re: Release-critical Bugreport for March 18, 2000
BugScan reporter [EMAIL PROTECTED] writes: Bug stamp-out list for Mar 18 09:21 (CST) Total number of release-critical bugs: 192 Number that will disappear after removing packages marked [REMOVE]: 9 Package: clisp (debian/main) Maintainer: Kevin Dalley [EMAIL PROTECTED] 46059 package fails to build on sparc [WAITING] Maintainer was contacted on Dec 12, awaiting reply. This bug only affects the sparc distribution, where clisp doesn't appear, because it won't build. In fact, it has never built under sparc. The bug *may* be fixed in the near future. -- Kevin Dalley [EMAIL PROTECTED]
Re: Release-critical Bugreport for March 18, 2000
On Mon, Mar 20, 2000 at 02:41:45AM -0800, Kevin Dalley wrote: [sth] Is it just me or did something make this message go out like 12 times? Each time it had more and more of these: MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:55 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:50 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:45 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:41 2000 X-Envelope-Sender: [EMAIL PROTECTED] MBOX-Line: From [EMAIL PROTECTED] Mon Mar 20 13:55:36 2000 X-Envelope-Sender: [EMAIL PROTECTED] WTF? :) -- enJoy -*/\*- don't even try to pronounce my first name
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On 20-Mar-00, 01:46 (CST), Nicolás Lichtmaier [EMAIL PROTECTED] wrote: Using the Space and the Backspace keys for up and down movement is absurd, it's even stupid. Backspace is back-space. Those keybindings where thought for keyboards without arrows, and those keyboards no longer exists... While I agree with most of what you wrote, you're wrong on this one. There's a *lot* of history of using the space bar to do the next thing in Unix console programs (more/less, most news readers and existing mail readers). And there's no reason *not* to use them -- what else would you bind to the space key? You're right: the defaults should cater to the new user, but there's no reason to deliberatly aggravate the experienced user. Steve -- Steve Greenland [EMAIL PROTECTED] (Please do not CC me on mail sent to this list; I subscribe to and read every list I post to.)
Re: Release-critical Bugreport for March 18, 2000
On Mon, Mar 20, 2000 at 09:10:08PM +0100, Josip Rodin wrote: On Mon, Mar 20, 2000 at 02:41:45AM -0800, Kevin Dalley wrote: [sth] Is it just me or did something make this message go out like 12 times? Just you. At least, I didn't get more than one copy of it, so I would guess it's something on your side. -- David Starner - [EMAIL PROTECTED] Only a nerd would worry about wrong parentheses with square brackets. But that's what mathematicians are. -- Dr. Burchard, math professor at OSU
Re: ITP: Kannel, open source WAP and SMS gateway
Lars Wirzenius [EMAIL PROTECTED] writes: Kannel is an open source WAP and SMS gateway. It's what I do for a living. I intend to make Debian package for it. See http://www.kannel.org for more. This is fine. WAP programming is on my schedule for April. As a Debian user it would be nice to package kannel. If you need help for this, you can mail me off the list. Ciao Racke -- LinuXia Systems, eCommerce and more = http://www.linuxia.de/ or 0511-3941290. Unsere Partner: Cobolt NetServices (http://www.cobolt.net), CAPCON Systemhouse (http://www.capcon-systemhouse.com), ecoservice gmbh (http://www.ecoservice.de) Unser Fokus liegt auf Open-Source-Software (MiniVend, Debian GNU/Linux, etc.)
Re: Bug#60753: mutt: /etc/Muttrc should not use colors
On Mar 19, Nicolás Lichtmaier [EMAIL PROTECTED] wrote: BTW, the default key bindings in mutt are horribly broken. No key does what someone would expect. mutt does what I expect, and I think what every former elm user expects. PINE sucks. If newbies don't have the correct expectations to use mutt, they can read the help line in each screen and get used to the default. I'm not going to change the default keybindings, no matter how much some people will scream. I will add (to the woody package, I will not upload anything new for potato) the commented settings somebody posted. -- ciao, Marco
