rebooting while installing.
I have encountered a problem with my computer rebooting, while trying to install Debian. I have tried to install it on a hdd all the files I need are there on that drive, but little much of anything else. When I configured the hdd the first time to run by itself, not as a slave, I forgot to remove my slave drive from my cmos settings, this returned an error while booting up, but I continued. I tried to install Debian, and got to the (from what I understand) i/o controller detection stage, the part after asking me for colour or b/w screen. I selected colour, and told the computer to continue, but due to the incorrect info in my cmos settings, a timeout error was given repeatedly. I fixed the cmos problem, and then tried to install Debian again, exactly as I had done the first time. Now, it starts to load, and then I get a glimpse of unknown Pci Device not exactly sure it happens to fast to read properly, and then reboots the computer. I have no idea what is causing this, any assistance, would be most appreciated. David Coles. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: slang, newt, whiptail
On Wed, 24 Jun 1998, Michael Dietrich wrote: hi all, i am about to write an easy to use editor, using slang ... (remember this ugly emacs/vi discussion) i started with slang and noticed that there is nearly no documentation and no good screen/kbd support at all. Hm, slang is actually amazingly easy to program for, it has a nice - simple IO model. Keyboard handling is quite simple too. If you need anything on that I can certainly help. There is a mostly complete slang doc that I found in the slang sources that is good for getting started. After that just look in the headers for the functions you want. If you desperately want overlapping windows/menus etc then maybe you'd be interested in the slightly finished APT widget library that does do this. But there is even less documentation : Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2.0-beta CD Image mirror sites ?
Hi, Could those of you who have grabbed, or are intending to grab the cd images from www.uk.debian.org, and then offer them for anon access, please mail me, so I can add your sites to the list of mirrors. For more info about how to grab them from www.uk see this: http://www.uk.debian.org/debian-cd/ We could do with some sites in the USA (remember to skip the non-us-non-free.raw image though ;-) Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Tue, 23 Jun 1998, Philip Hands wrote: for all future time. People make mistakes choosing version numbers, and we have a mechanism for recovering these mistakes. People being ``inventive'' so they can maintain the aesthetic beauty of a control file that is rarely seen by anyone is a waste of all our time. it's more than just 'aesthetic beauty'. 'dpkg -l' output is hard-coded for 80 columns, and there are only a limited number of character positions available for the version number. extracting the version from the listing is not possible for long version strings. yes, this is a bug in dpkg, and should be fixed. but the problem exists now, and if dpkg's revision history is anything to go by will continue to exist for a long long time. craig -- craig sanders -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0.34 and x-bit on libraries
At 13:22 -0700 1998-06-24, Heiko Schlittermann wrote: . 2.0.34 needs the x-bit on shared libraries! Actually, no, it's just the dynamic linker that needs to be executable. This is apparently a security feature, 2.1 kernels also require an executable dynamic linker, and thus 2.2 will as well. -- Joel Espy KleckerDebian GNU/Linux Developermailto:[EMAIL PROTECTED] http://www.espy.org/ ftp://ftp.espy.org/pub/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On 24 Jun 1998, Manoj Srivastava wrote: Hi, Dale == Dale Scheetz [EMAIL PROTECTED] writes: Dale What is with this snake like facination with epochs? Firstly, this is uncalled for. Secondly, even as a popular belief, it is not snakes that are fascinated, their victims are supposed to be. Thirdly, there is no scientific evidence that snakes indeed semi-hypnotize their prey. I appologize for waving a facinating metaphor in your face. I had not realized you would be fixated by single words from my statement. I like snakes (I live in a swamp) and sometimes forget that others put mystical meaning into their use. My point was that you are suffering from something called problem set, usually defined as certain that the solution in hand is the correct one, even when it doesn't work. While I agree that application of epochs to this problem would work, I still disagree that it is the correct solution. Dale Epochs are intended to be a fix for version number overlap. Why is an upstrem prerelese with an version number that does not order well not fit this criterion? Because it is fundamentaly different in nature. Version overlap is not the same thing as periodically cruddy version numbering. As I see it, there are upstream releases. Some are more stable than others. The upstream athours sometimes create versions which do not order correctly. We use epochs to correct this. Well, this is probably the crux of our difference of oppinion. I see versions numbered 2.0.7 and 2.0.8 as release versions, because that is the way the upstream authors see them. The tarballs that appear before those releases are given numbers like 2.0.7pre1 specifically to indicate that they are NOT releases, but pre-release test versions. Thus I see myself as being free to reformat the pre-release versions to conform to reasonable numbering for dpkg, specifically so that the release version numbers can be identical to the upstream release version number. This preserves the important aspects of the upstream numbering scheme while allowing pre-release versions to integrate smoothly with our package system. Dale This, on the other hand, while it does deal with version Dale numbers, the similarity ends there. This is a temporary problem Dale that is better solved by some careful planning in the Dale future. (Yes, it is a recurring problem, but each time, it is Dale temporary.) Oh, your package, your decision, but you should realize that the solutions presented do warp upstream versions (I assume that the upstream release had a version number). So, it is a choice between warping a version number (and creating confusion about exactly which pre-release was being used) or using an epoch, which is an irreversible process. When properly used epochs do not hang around forever. Consider the situation where epochs are supposed to be used: Upstream Debian 1.0 1.0 2.0 2.0 3.0 3.0 2.01:2.0 3.01:3.0 4.0 4.0 Here, the epochs only hang around as long as they are needed to get past the overlap in version numbers. If we apply epochs to the problem of pre-release version numbering (with my proposal along side) you should be able to see why I don't like it. Upstream Your Proposal My Proposal 2.0.8pre12.0.8pre1 2.0.7.99.1 2.0.8 1:2.0.8 2.0.8 2.0.9pre1 1:2.0.9pre1 2.0.8.99.1 2.0.9 2:2.0.9 2.0.9 As you can see, for every point release, the epoch number must increase. This presents this problem as an infinitely folded list of repeating version numbers, which is not actually the case. Just a retorical question: Would you insist on epochs if the upstream author accepted my numbering scheme? Would there be any reason to use them? Then I submit that my solution is adequate, and more useful than yours. (Please note that I only put this on a personal basis for purposes of properly isolating the two different points of view. I am certain that I have been biased towards my own proposal, so I hope you will take that into account when discounting my points. I am also certain that I have not misrepresented the technical consequences of the use of epochs) Luck, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Manoj Srivastava [EMAIL PROTECTED] wrote: warping them (I can just see Ted T'so saying what the $#^%$ is 2.0.7 *r*? Debian is doing its won thing again); and using epochs, a It could be 2.0.7released -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Dale Scheetz [EMAIL PROTECTED] wrote: When properly used epochs do not hang around forever. Consider the situation where epochs are supposed to be used: Upstream Debian 1.0 1.0 2.0 2.0 3.0 3.0 2.01:2.0 3.01:3.0 4.0 4.0 Here, the epochs only hang around as long as they are needed to get past the overlap in version numbers. Er.. no. epoch 1, version 3 comes after epoch 0, version 4. Otherwise, epochs would be worthless. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Tue, 23 Jun 1998, Philip Hands wrote: for all future time. People make mistakes choosing version numbers, and we have a mechanism for recovering these mistakes. People being ``inventive'' so they can maintain the aesthetic beauty of a control file that is rarely seen by anyone is a waste of all our time. it's more than just 'aesthetic beauty'. 'dpkg -l' output is hard-coded for 80 columns, and there are only a limited number of character positions available for the version number. extracting the version from the listing is not possible for long version strings. Which is actually another reason for using epochs, that I'd not previously realised, since epochs don't show up, whereas random suffixes do: [phil] palm:~$ dpkg -l libgtk1 Desired=Unknown/Install/Remove/Purge | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=b ||/ NameVersionDescription +++-===-==-= ii libgtk1 1.0.4-1The GIMP Toolkit set of widgets for X ^^^ Nice clean version here, but wait... [phil] palm:~$ dpkg -s libgtk1 Package: libgtk1 Status: install ok installed Priority: optional Section: libs Installed-Size: 862 Maintainer: Ben Gertzfield [EMAIL PROTECTED] Source: gtk+ Version: 1:1.0.4-1 - Shock Horror!!! I've seen an epoch, I'll ... have to pluck my eyes out now ;-) Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Corrupted wtmp file under 'frozen'
Dirk I have a machine which is 'almost pure frozen' Debian, and I have a Dirk corrupted wtmp file. Anybody else seeing that as well ? Turned out that, at least on my machine, it was xterm. I did a s/xterm/rxvt in ~/.fvwm2/* a couple of days ago, and that helped Incidentally, the newest XFree package for the now-beta Debian 2.0 appear to have that fixed, according to the changelog I saw today. -- mailto:[EMAIL PROTECTED] According to the latest official figures, http://rosebud.ml.org/~edd 43% of all statistics are totally worthless. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Thu, 25 Jun 1998, Craig Sanders wrote: 'dpkg -l' output is hard-coded for 80 columns, and there are only a limited number of character positions available for the version number. extracting the version from the listing is not possible for long version strings. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Wed, 24 Jun 1998, Raul Miller wrote: Dale Scheetz [EMAIL PROTECTED] wrote: When properly used epochs do not hang around forever. Consider the situation where epochs are supposed to be used: Upstream Debian 1.0 1.0 2.0 2.0 3.0 3.0 2.01:2.0 3.01:3.0 4.0 4.0 Here, the epochs only hang around as long as they are needed to get past the overlap in version numbers. Er.. no. epoch 1, version 3 comes after epoch 0, version 4. Otherwise, epochs would be worthless. But, of course, how slow of me ;-) The whole point of the epoch is to override any seeming higher version number. This must also override actual higher versions as well, of course. Must be my bed time ;-) Thanks, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
gcc help
Hi I'm new to the list, I just installed debian 2, which went through fine, now however when I try and compile anything it says gcc is broke. when running configure scripts some of them report that gcc cannot create executables. Anyone else had this kinda problem?? Thanks for any info in advance. Bel
Re: libc6_2.0.7 release notes...
In article [EMAIL PROTECTED] you wrote: : I see versions numbered 2.0.7 and 2.0.8 as release versions, because that : is the way the upstream authors see them. The tarballs that appear before : those releases are given numbers like 2.0.7pre1 specifically to indicate : that they are NOT releases, but pre-release test versions. Which is, of course, the problem... I think this 'pre' versioning scheme is a crock... if it isn't 2.0.8 yet, then the version should be 2.0.7.something. But, we can't control what upstream maintainers choose as version sequences... so what we think isn't very important here. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: About the Hamm Freeze (!)
-BEGIN PGP SIGNED MESSAGE- Stephen Zander, in an immanent manifestation of deity, wrote: Not true Darren: dbmopen does the moral equivalent of the tie under the covers. It's one of my pet peeves that perl links in libraries to the main executable that are only required by extensions. Hmm. You're right. Any ideas on when this changed or was I just on too much sleep-dep when I last looked at this. (a while back) Darren - -- [EMAIL PROTECTED] http://www.daft.com/~torin [EMAIL PROTECTED] [EMAIL PROTECTED] Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996 @ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI programmer and tutor. @ @Make a little hot-tub in your soul. @ -BEGIN PGP SIGNATURE- Version: 2.6.3a Charset: noconv Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQCVAwUBNZHNDI4wrq++1Ls5AQGSegP/R/dhVQ32p7WQ11f4vNkNasKhF/Qn3kvz n6wwl4AJuGYgoRB77VvspgXORoMjtOda0Zr+N3bK0WGO3yIZyS2sMOilmhLuF4rF J+ztgem+35weBBME/Kd3AMHXzH/5Re/SmI9VfNj/LPoFFiFgPq+OhUPn2C1IKoag 1J0wjwk++e4= =4IkJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: gcc help
Chris Massam [EMAIL PROTECTED] writes:
I'm new to the list,=20
I just installed debian 2, which went through fine, now however when I =
try and compile anything it says gcc is broke.
when running configure scripts some of them report that gcc cannot =
create executables.
Anyone else had this kinda problem??
Thanks for any info in advance.
Bel
Post the error message from trying to compile something like:
#include stdio.h
int main( int argc, char *argv[] ){
printf(Hello, world!\n);
}
My guess is that you need to install libc6-*-dev, where the * depends on
what version of libc6 you have available. Without an error message it's
hard to debug.
Later,
Dale
+ finger for pgp public key -+
| Dale E. Martin | University of Cincinnati Savant Research Laboratory |
| [EMAIL PROTECTED]| http://www.ececs.uc.edu/~dmartin |
+--+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Gothenburg - Vancouver
Dan Jacobowitz [EMAIL PROTECTED] writes: They explicitly disallow all servers of ANY kind. No open ports, except maybe identd. A friend of mine was running one just fine under linux, with dhcp and all, but got his account terminated for having sendmail up :) This is rather off-topic, but doesn't Win98 come bundled with Microsoft's WWW server? Are they going to terminate people's accounts for having this installed, or for binding Microsoft Networking to the cable modem? (Not that the latter is a very good idea anyway, but...) -- Carey Evans http://home.clear.net.nz/pages/c.evans/ [UNIX] appears to have the inside track on being the replacement for CP/M on the largest microcomputers (e.g. those based on 68000...) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: automating the Intents to package was Re: Please follow protocol when you announce your Intents to package
In article [EMAIL PROTECTED] you write: Ok, I'm game. I have had to fend off enough people from taking my packages that this is worth my time. Besides, I enjoy writing CGI, call me sick. What do we want/need/desire/despise and let's get this going. a database with the stuff from wnpp (list of programs that should be packages, and of orphaned/giveaway packages). would be nice to also handle tasks with that (e.g. someone to check permissions of files and suid/sgid bits in all packages). the whole thing with a i will do it button, maybe also with a history function. no access control: we will correct things, if some people do crap. a daily or weekly journal to debian-devel would also be nice... andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
netselect - choosing the best FTP server automatically
Hi all, A while ago on debian-devel I proposed an algorithm that would allow APT to choose the best possible server for each user from a large list automatically. It could also be used for other tasks, eg. choosing a good SQUID neighbour or IRC server. So, I wrote a program that gathers the statistics needed for these operations. It's called netselect, and I wrote it all in one night, so please be gentle with the bug reports :) I do want to hear what you think though. Following my signature is the first part of the README. Get it from: http://www.worldvisions.ca/~apenwarr/netselect-0.1.tar.gz It's very experimental. Let me know what happens! Have fun, Avery --- netselect 0.1 = This is netselect, an ultrafast intelligent parallelizing binary-search implementation of ping. Now stop laughing and pay attention. netselect determines several facts about all of the hosts given on the command line, much faster you would if you manually tried to use ping and traceroute. For example, if I type: netselect -v ftp.fceia.unr.edu.ar ftp.kulnet.kuleuven.ac.be \ ftp.cdrom.com ftp.debian.org ftp.de.debian.org It tells me this: ftp.fceia.unr.edu.ar 422 ms 19 hops 40% ok ( 2/ 5) ftp.kulnet.kuleuven.ac.be ms 30 hops0% ok ftp.cdrom.com 215 ms 13 hops 89% ok (17/19) ftp.debian.org 194 ms 20 hops 50% ok ( 3/ 6) ftp.de.debian.org 276 ms 15 hops 66% ok ( 6/ 9) For each host, it figures out the approximate ping time (though not as accurately as ping does), the number of network hops to reach the target, and the percentage of ping requests that got through successfully. Note that for ftp.kulnet.kuleuven.ac.be in this case, nothing got through at all. That indicates that either the host doesn't exist, or it is down. For a bigger example, I've included the file debian-ftp-mirrors, which is a partially up-to-date list of Debian Linux FTP site mirrors. Try this: netselect -vv $(cat debian-ftp-mirrors) [...etc...] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: f
Processing commands for [EMAIL PROTECTED]: reassign 23867 general Bug#23867: Critical permissions bug on /lib and /tmp Bug assigned to package `general'. reassign 23851 boot-floppies Bug#23851: `install.txt' contains back spaces Bug assigned to package `boot-floppies'. reassign 23859 boot-floppies Bug#23859: # of disks in floppy installation Bug assigned to package `boot-floppies'. thanks Stopping processing here. Please contact me if you need assistance. Ian Jackson (administrator, Debian bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
DO NOT UPGRADE TO PLAN 1.6.1-4.2 ! USE -5
Sorry for this, but I made a very bad mistake in -4.2, which will just unconditionally overwrite you netplan-acl file with an empty one. Please get 1.6.1-5 instead (in Incoming for now, maybe at its mirrors), it has this problem fixed. Sorry for the inconvenience - I sincerely hope nobody suffered from this. -- Yann Dirson[EMAIL PROTECTED] | Stop making M$-Bill richer richer, isp-email: [EMAIL PROTECTED] | support Debian GNU/Linux: debian-email: [EMAIL PROTECTED] | more powerful, more stable ! http://www.mygale.org/~ydirson/ | Check http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Isn't cc the default compiler?
I compiled a lot of packages on my system and often I see that programms don't use cc as their compiler. Thus they don't use /etc/alternatives/cc. Unless somebody tells me a good reason for not using cc I will open bugs against any Packages that just uses gcc for fun. I know that some Packages need gcc explicitly, but that should be a realy small number. May the Source be with you. Mrvn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0-beta CD Image mirror sites ?
Philip Hands [EMAIL PROTECTED] writes: Hi, Could those of you who have grabbed, or are intending to grab the cd images from www.uk.debian.org, and then offer them for anon access, please mail me, so I can add your sites to the list of mirrors. For more info about how to grab them from www.uk see this: http://www.uk.debian.org/debian-cd/ We could do with some sites in the USA (remember to skip the non-us-non-free.raw image though ;-) Cheers, Phil. In what formats are those images provided? It would be nice to download the image in parts including md5sums and to have some additional error correction chunks like ras provides. I know that it would multiply the size requirements if various chunk sizes are provided, but maybe one could make a small programm to download a chunk of a given size. The programm would then split up the image and send the respective chunk, similar to what split does, but with a parameter for which chunk one wants. May the Source be with you. Mrvn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New web pages are finally up!
The latest version of the Debian web pages are complete. They are being mirrored to www.debian.org as I write this. The new pages use content negotation to decide what version should be served when there is more than one choice. This is used to automatically give a document in a users prefered language, if it is available, while giving the default version (english in our case) when there is no choice. The pages also use wml to handle some of the complexity of a large web site such as ours from the document writers. It also allows for some nice automation. For example when the main page is created from the .wml file, the titles of the most recent news items are automatically added to the page. Pretty slick. Now all that is needed is for people to send news items to webmaster. :) Finally, I'd like to thank Thomas Apel [EMAIL PROTECTED] for the layout of the new pages and Anthony Fok [EMAIL PROTECTED] for setting up the wml. Now it's time for bed. Jay Treacy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0-beta CD Image mirror sites ?
Brederlow [EMAIL PROTECTED] In what formats are those images provided? Single ISO image per CD. It would be nice to download the image in parts including md5sums and to have some additional error correction chunks like ras provides. For the final release, this is probably worth the effort, but I'm a bit busy at present --- if one of the mirrors (whoever they are) wants to have a go, feel free. Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
When properly used epochs do not hang around forever. Consider the situation where epochs are supposed to be used: Upstream Debian 1.0 1.0 2.0 2.0 3.0 3.0 2.01:2.0 3.01:3.0 4.0 4.0 Dong! You loose ;-) [as has already been pointed out] 1:3.0 4.0 If we apply epochs to the problem of pre-release version numbering (with my proposal along side) you should be able to see why I don't like it. Upstream Your Proposal My Proposal 2.0.8pre12.0.8pre1 2.0.7.99.1 2.0.8 1:2.0.8 2.0.8 2.0.9pre1 1:2.0.9pre1 2.0.8.99.1 2.0.9 2:2.0.9 2.0.9 As you can see, for every point release, the epoch number must increase. This presents this problem as an infinitely folded list of repeating version numbers, which is not actually the case. I don't think anyone was suggesting this. What was being suggested, was that where a mistake is made (i.e. the use of a ``pre'' version in the first place), the right way to recover from it (in the absence of time-travel.deb) was to use an epoch, so the sequence goes: Upstream Debian 2.0.7pre1 2.0.7pre1 (can you see the silent 0: ?) 2.0.7 1:2.0.7 2.0.8pre1 1:2.0.7.99.1 2.0.8 1:2.0.8 2.0.9pre1 1:2.0.9.99.1 2.0.9 1:2.0.9 or whatever other solution the maintainer comes up with to avoid having to use epochs again, until the next SNAFU. Just a retorical question: Would you insist on epochs if the upstream author accepted my numbering scheme? Would there be any reason to use them? To answer your retorical question: Yes there is. If the maintainer typos the changelog, and releases 2.0.9.99.1 as 2.0.99.9.1 (easy mistake to make, easy to miss on the upload), then we'd use an epoch to fix it, although I expect some genius would suggest that we use: 2.0.x9 until 2.1.0 comes out, so that we wouldn't need to use a ``dirty, evil epoch''. I am also certain that I have not misrepresented the technical consequences of the use of epochs) Apart from the fact that they never go away, even when used ``properly'' :-) Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New web pages are finally up!
From: James A.Treacy [EMAIL PROTECTED] Subject: New web pages are finally up! Date: Thu, 25 Jun 1998 05:04:59 -0400 (EDT) The new pages use content negotation to decide what version should be served when there is more than one choice. This is used to automatically give a document in a users prefered language, if it is available, while giving the default version (english in our case) when there is no choice. Very cool. How can I add the translated version? I have some Japanese translations (based on the previous version, though). I'd like to catch up the latest version and release them. Keita Maehara [EMAIL PROTECTED] PGP Key fingerprint = 82 37 2F 1E 06 ED C4 37 1E E2 C2 96 22 B8 B3 F1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0.34 and x-bit on libraries
On Wed, Jun 24, 1998 at 05:50:08PM -0700, Joel Klecker wrote: : At 13:22 -0700 1998-06-24, Heiko Schlittermann wrote: : . 2.0.34 needs the x-bit on shared libraries! : : Actually, no, it's just the dynamic linker that needs to be executable. : : This is apparently a security feature, 2.1 kernels also require an : executable dynamic linker, and thus 2.2 will as well. Ok, if this turns out to be true, it should be made publically known. Heiko --- datom * internet * support ** Heiko Schlittermann Partner GbR mailto:[EMAIL PROTECTED] http://www.datom.de/is voice:+49-351-8029981 Heiko Schlittermann HS12-RIPE finger:[EMAIL PROTECTED] --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New web pages are finally up!
The latest version of the Debian web pages are complete. They are being mirrored to www.debian.org as I write this. They look great :-) You've gone back to calling www.uk ``England'' though... I still prefer ``Britain'' to ``United Kingdom'', but either will do. Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Intent to package ktop
-BEGIN PGP SIGNED MESSAGE- Package: ktop Version: 0.9.7-1 Architecture: i386 Depends: kdelibs0g (= 2:980312), libc6, libstdc++2.8 (=2.90.26-1), qt1g (= 1.33-4), xlib6g (= 3.3-5) Installed-Size: 214 Maintainer: Lars Steinke [EMAIL PROTECTED] Description: system performance process monitoring tool A combination of top, tkps and NT system monitor WNPP does not list this package as being worked on. Any objections to uploading it via erlangen ? Regards, /(__ __|\ Lars Steinke, Research Student @ (\/ __)_www.fmf.uni-freiburg.de, Germany ) (_ / For PGP PKey and WWW-Page finger /___/[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQCVAwUBNZF4YMMnaHd2HseJAQFSRAP/cV/w13vnmUvAgnJ3SuMBr3tfLLNmqyZa kbmJ+ZtB16aK/O7CiUqawG4AC7pREpdqNvGSxGWx0rCVykgR728OSKf5csLu8RWl t6MdAiWJTqnbjt3hvj5hN3CAMGHmfZWN/mrUTZxyN3Sh26juWhsGKxsinVjwIqE8 wf+T/5qZqVg= =9Org -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: VI reasons (was Re: Base Set: Suggested additions removals.)
On 25 Jun 1998, Martin Mitchell wrote: Sorry for the delayed reply, I've been away a few days. Dale Scheetz [EMAIL PROTECTED] writes: On 17 Jun 1998, Martin Mitchell wrote: Dale Scheetz [EMAIL PROTECTED] writes: Did you use X and x as declared on the help screen? These are the vi delete keys, and the cursor is moved left (backspace?) with the h key. All of this is on the help screen. If you don't see it there, there is no guarantee that it will do what you expect. I did successfully edit using the standard vi keys, but the backspace works in any vi, and it should be supported in the 'vi-mode' of ae. This is one of the few remaining problems that are glaringly apparent when using ae in vi-mode. I can certainly add it back into the keybindings, but it will behave slightly different in an xterm. I can't make an xterm treat backspace any different from del (they both do a right delete, if I remember correctly) How about the arrow keys. I can make them work on a console and in an xterm, although not from a tty. I'm trying to provide constructive criticism, that can help improve ae. And I appreciate that. I realize you've faced some rather harsh criticism in the past, however I think this was due to the particularly annoying nature of some of the bugs that have now been fixed. (eg not being able to quit in vi-mode) Yes, it has been a bit frustrating that folks can't seem to get over the past difficulties. Reminds me of my Mom, who would keep lists (in her head) of everything my Dad had ever done wrong, and would go over the list at the least opportunity. When the necessary keys are properly configured, ae is a nice little editor that serves the needs of the installation environment. Why anyone would continue to use it, instead of one of the other, more virsatile editors provided in standard, is beyond my comprehension ;-) The part of the changelog that should have been in that release was missing through my error as well. (how do you fix bugs in a changelog?) Add them in a subsequent version, with an explanatory note as to which version they were fixed in. My choices are to junk the whole concept, and force all you with vi programmed fingers to use ae instead, or to continue with the poor functionality emulation I have, in hopes that someone will figure out how to improve it. I'm appreciative of all that has been done, and I only have 3 requests for future releases: 1) Fix backspace to act as expected when editing text. To some limits, I can do this. 2) Fix displaying default option at command prompts, eg File not saved. Quit (y/n) ? n^H after typing :q This is a known slang bug, and we have our best men working on it ;-) 3) Remove old /etc/ae2vi.rc file if it exists, to avoid confusion. Yes, this is a detail that dpkg should be able to deal with, but on an upgrade it doesn't want to remove such files, even though they do not exist, or have been moved, in the new replacement package. I can deal with this in the post install. Thanks for reminding me that this bit of fluff is still under the bed. Waiting is, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0-beta CD Image mirror sites ?
Previously Brederlow wrote: In what formats are those images provided? It would be nice to download the image in parts including md5sums and to have some additional error correction chunks like ras provides. You're just describing how rsync works. rsync retrieves the file in parts and compares checksums. And later you can update with rsync: it just compares checksums of parts and replaces only changed blocks. Wichert. -- == This combination of bytes forms a message written to you by Wichert Akkerman. E-Mail: [EMAIL PROTECTED] WWW: http://www.wi.leidenuniv.nl/~wichert/ pgpFPmSgZBU2i.pgp Description: PGP signature
apt-0.0.16 and libc6-2.0.7r2
I haven't been following the discussion on the libc6 naming (too little time, I'm afraid) so I may have missed any fixes to this. I have apt 0.0.16-1 and libc6 2.0.7r-2 installed. I installed apt before the upgrade of libc6. Now the first thing that apt wants to do when you run it is to commit suicide by removing itself. Is there a workaround? puccini:~# dpkg -s apt Package: apt Status: install ok installed Version: 0.0.16-1 Pre-Depends: libc6 (= 2.0.7pre1-0), libstdc++2.8 (= 2.90.26-1) Suggests: perl, libnet-perl, libwww-perl, libmd5-perl Conflicts: deity Conffiles: /etc/apt/sources.list ea2d8631fa15fc7abbc3aae46cb9d2e5 puccini:~# dpkg -s libc6 Package: libc6 Status: install ok installed Source: glibc Version: 2.0.7r-2 Pre-Depends: ldso (= 1.8.10-1) Conflicts: libc5 ( 5.4.33-7), libpthread0 ( 0.7-10) puccini:~# apt-get update Get file:/groucho/private/debian/debian-non-US/ unstable/binary-i386/ Packages Get file:/groucho/pub/linux/debian/ frozen/contrib Packages Get file:/groucho/pub/linux/debian/ frozen/main Packages Get file:/groucho/pub/linux/debian/ frozen/non-free Packages Updating package file cache...done Updating package status cache...done Checking system integrity...dependency error You might want to run `apt-get -f install' to correct these. Sorry, but the following packages are broken - this means they have unmet dependencies: apt: Depends:libc6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
translations of the web pages to begin
With the new web pages up, it is finally time to begin translation of the pages. What I'd like to do is to get one person to start with. This person should be familiar with CVS (putting everything under CVS is next on my list and I've never used it before). The reason for having one person to start with is to work out any kinks in the system. My goal is to give translators a recipe to follow so they don't need to know anything about content negotiation or wml. This person will hopefully catch any errors I've introduced during this latest transition. A system (to be worked out) will notify translators when documents are modified. It is ok to have a team work on translation although there should be one person in charge for each language. All translators should subscribe to debian-www (don't worry - it's low volume). Anyway, the first qualified person to contact me gets to be the guinea pig^H^H^H^H^H^H^H^H^H^Hlucky translator. Jay Treacy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Thu, 25 Jun 1998, Philip Hands wrote: until 2.1.0 comes out, so that we wouldn't need to use a ``dirty, evil epoch''. No one has said anything about dirt or evil with respect to epochs. Policy says not to use them for this purpose. It also says not to use pre-release numbering schemes. Which doesn't leave much wiggle room. I am also certain that I have not misrepresented the technical consequences of the use of epochs) Apart from the fact that they never go away, even when used ``properly'' :-) Agreed. Brandon Mitchell has come up with a better scheme than my numbering alternative. Consider the following: 2.0.8pre1 2.0.8-0pre1 2.0.8pre2 2.0.8-0pre2 2.0.8 2.0.8-1 This has several advantages over my previous scheme. It preserves the upstream version information in human readable form. It takes advantage of the fact that dpkg will create a source upload for -0 and -1 sequences. It naturally maintains the dpkg sequence ordering of the version numbers. It doesn't need to use epochs. Waiting is, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: apt-0.0.16 and libc6-2.0.7r2
On Thu, Jun 25, 1998 at 09:16:25AM -0500, Douglas Bates wrote: I haven't been following the discussion on the libc6 naming (too little time, I'm afraid) so I may have missed any fixes to this. I have apt 0.0.16-1 and libc6 2.0.7r-2 installed. I installed apt before the upgrade of libc6. Now the first thing that apt wants to do when you run it is to commit suicide by removing itself. Is there a workaround? Yes, you encountered a bug in apt 0.0.16 (an error in the sorting code. Get apt 0.0.17 from http://master.debian.org/~doogie/ -- Scott K. Ellis [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X development on va
Could someone please install the xlib6g-dev package on va.debian.org? I'm close to finishing the packaging of the TWIN windows emulator (can't do it on my own machines because they are too slow) and the X libraries and headers seem to have disappeared. -- Jaldhar H. Vyas [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xterm-debian terminfo entry
Alexander E. Apke writes: I propose xbase allowing people to choose between black or white background during postinst or maybe in some kind of xbaseconfig script. I think it's not necessary. I did not test, but the following (or a similar setting) should work well and please most people: # ln -s xterm /usr/bin/X11/xterm-black # cat /etx/X11/Xresources EOF xterm-black*background: black xterm-black*foreground: gray90 EOF Branden, maybe it should be added to the X packages ? -- Yann Dirson[EMAIL PROTECTED] | Stop making M$-Bill richer richer, isp-email: [EMAIL PROTECTED] | support Debian GNU/Linux: debian-email: [EMAIL PROTECTED] | more powerful, more stable ! http://www.mygale.org/~ydirson/ | Check http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Thu, Jun 25, 1998 at 10:29:43AM -0400, Dale Scheetz wrote: Brandon Mitchell has come up with a better scheme than my numbering alternative. Consider the following: 2.0.8pre1 2.0.8-0pre1 2.0.8pre2 2.0.8-0pre2 2.0.8 2.0.8-1 This has several advantages over my previous scheme. It preserves the upstream version information in human readable form. It takes advantage of the fact that dpkg will create a source upload for -0 and -1 sequences. It naturally maintains the dpkg sequence ordering of the version numbers. It doesn't need to use epochs. It has one disadvantage I can see. The -0pre looks like it's something it's not, but I believe people will figure it out, especially if the desc contained real version info. pgpx7E6JFcyEU.pgp Description: PGP signature
Re: Hamm Bug Stamp-Out List for June 25, 1998
On Thu, 25 Jun 1998, Wichert Akkerman wrote: Welcome to the nem Hamm Bugs Stamp-Out List. 21884 libc6-dev: relative links between top-level dirs I'm not sure what to do abou this one. The upstream maintainer (Ulrich D.) insists that the relative links are correct and that making /usr a symlink to something else is evil. Rebuilding the links is at the edge of my shell script skills, and certainly outside any time frame I have available at the moment. I feel the need for some discussion on the technical consequences of changing these links, as well as the consequences of not changing them. Waiting is, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Isn't cc the default compiler?
On Thu, Jun 25, 1998 at 10:24:02AM +0200, Brederlow wrote: I compiled a lot of packages on my system and often I see that programms don't use cc as their compiler. Thus they don't use /etc/alternatives/cc. Unless somebody tells me a good reason for not using cc I will open bugs against any Packages that just uses gcc for fun. I know that some Packages need gcc explicitly, but that should be a realy small number. Huge numbers of packages pass gcc-specific CFLAGS and LDFLAGS. These are important, because running 'cc' without these flags can often generate pure garbage for code. (WvDial and g++, for example -- I looked at the assembly output, and was not impressed!) If you want to use 'cc', just force CC=cc on the command line. If that doesn't work, that's a bug. Avery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hamm Bug Stamp-Out List for June 25, 1998
On Thu, Jun 25, 1998 at 09:45:43AM -0500, Wichert Akkerman wrote: Package: kdebase (i386 contrib) Maintainer: Stephan Kulow [EMAIL PROTECTED] 23655 kdebase includes /etc/X11/Xsession Stephen is probably busy trying to get KDE 1.0 done, so I doubt he has any plans to work on this. My suggestion is to either copy the beta4 kde packages from slink (which includes the fix for this bug) into hamm or drop kde from hamm altogether. I prefer the former. FWIW, I think the only reason, the beta4 packages weren't put in hamm in the first place is because Stephen didn't take the time to rebuild and re-upload them with the proper 'frozen tag. David -- David EngelODS Networks [EMAIL PROTECTED] 1001 E. Arapaho Road (972) 234-6400 Richardson, TX 75081 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
--On Thu, Jun 25, 1998 3:23 pm + Rev. Joseph Carter [EMAIL PROTECTED] wrote: On Thu, Jun 25, 1998 at 10:29:43AM -0400, Dale Scheetz wrote: Brandon Mitchell has come up with a better scheme than my numbering alternative. Consider the following: 2.0.8pre12.0.8-0pre1 2.0.8pre22.0.8-0pre2 2.0.8 2.0.8-1 This has several advantages over my previous scheme. It preserves the upstream version information in human readable form. It takes advantage of the fact that dpkg will create a source upload for -0 and -1 sequences. It naturally maintains the dpkg sequence ordering of the version numbers. It doesn't need to use epochs. It has one disadvantage I can see. The -0pre looks like it's something it's not, but I believe people will figure it out, especially if the desc contained real version info. Someone suggested this earlier in the discussion, and someone else pointed out that this is clearly against policy, since anything after the '-' should reflect debian-specific packaging changes, not upstream changes. Jules /+---+-\ | Jelibean aka | [EMAIL PROTECTED] | 6 Evelyn Rd| | Jules aka | | Richmond, Surrey | | Julian Bean | [EMAIL PROTECTED]| TW9 2TF *UK* | ++---+-+ | War doesn't demonstrate who's right... just who's left. | | When privacy is outlawed... only the outlaws have privacy. | \--/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hamm Bug Stamp-Out List for June 25, 1998
On Thu, Jun 25, 1998 at 11:30:45AM -0400, Dale Scheetz wrote: On Thu, 25 Jun 1998, Wichert Akkerman wrote: Welcome to the nem Hamm Bugs Stamp-Out List. 21884 libc6-dev: relative links between top-level dirs I'm not sure what to do abou this one. The upstream maintainer (Ulrich D.) insists that the relative links are correct and that making /usr a symlink to something else is evil. You should ask him why he uses an absolute path to /lib/libc.so.6 in the /usr/lib/libc.so linker script then. Rebuilding the links is at the edge of my shell script skills, and certainly outside any time frame I have available at the moment. I feel the need for some discussion on the technical consequences of changing these links, as well as the consequences of not changing them. Here is little bash snippet to be added very late in the 'debian/rules binary' stage that does the job. It is a liitle specific to the glibc 2.0.7 release, but that shouldn't be a big problem at this time. v=2.0.7 pv=0.7 cd debian/tmp/usr/lib for f in *.so ; do if [ $f != libc.so -a $f != libndbm.so ]; then rm $f if [ $f != libpthread.so ]; then ln -s /lib/$(basename $f .so)-$v.so $f else ln -s /lib/$(basename $f .so)-$pv.so $f fi fi done Dale you should note that this also makes another important change that should have been noticed by me a long time ago. It changes the symlink to point to the actual shared library file instead of the soname symlink. For example, this would make /usr/lib/libm.so point to /lib/libm-2.0.7.so instead of /lib/libm.so.6. This change makes it harder for a user to screw up his compilation environment by simply installing a newer shared library file and running ldconfig manually. David -- David EngelODS Networks [EMAIL PROTECTED] 1001 E. Arapaho Road (972) 234-6400 Richardson, TX 75081 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: automating the Intents to package was Re: Please follow protocol when you announce your Intents to package
On Thu, Jun 25, 1998 at 09:20:13AM +0200, Andreas Jellinghaus wrote: In article [EMAIL PROTECTED] you write: Ok, I'm game. I have had to fend off enough people from taking my packages that this is worth my time. Besides, I enjoy writing CGI, call me sick. What do we want/need/desire/despise and let's get this going. a database with the stuff from wnpp (list of programs that should be packages, and of orphaned/giveaway packages). would be nice to also handle tasks with that (e.g. someone to check permissions of files and suid/sgid bits in all packages). the whole thing with a i will do it button, maybe also with a history function. no access control: we will correct things, if some people do crap. a daily or weekly journal to debian-devel would also be nice... Hell, might as well implement the vacation stuff while we're at it. Shaleh's just wandered into the Twilight Zone cafeteria, where task after task is getting piled on his tray... :) -- G. Branden Robinson | Purdue University | The software said it required Windows [EMAIL PROTECTED] | 3.1 or better, so I installed Linux. http://www.ecn.purdue.edu/~branden/ | pgpWVtD2SqT2F.pgp Description: PGP signature
Re: New web pages are finally up!
Very cool. How can I add the translated version? I have some Japanese translations (based on the previous version, though). I'd like to catch up the latest version and release them. I'd like to keep the different language versions in sync as much as possible. Only translations based on the new version of the pages will be allowed. That's why I've been putting off offers of translation until now. One nice thing about using content negotation is that you can translate one document at a time. All untranslated docs will just be presented in another language available (defaulting to English). The one document that I will be asking for translators for as soon as it is ready is the install docs. I will announce it's availability on debian-www so subscribe there if you want to work on it. Jay Treacy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bad kernel 2.0.34 bug ?
Hello,
As a matter of fact it just happened with our IDE drives after upgrading
to 2.0.34, since we had read this, we downgraded to 2.0.33 and it works with
no erros now. I
don't intent to say that this is an important bug, but maybe it should be
looked at.
I had this error messages with 2.0.{29,30,32,33} (not tried 31). With
2.0.34, they disappeared. I haven't changed anything in the hardware
setup.
CPU: P100,
Chipset: i82371 PIIX (Triton) chipset
Harddisc: WDC AC21000H, 1033MB w/128kB Cache, CHS=525/64/63, DMA
Harald
--
Harald Weidner http://www.ifi.unizh.ch/~weidner/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hamm Bug Stamp-Out List for June 25, 1998
Hi, Wichert == Wichert Akkerman [EMAIL PROTECTED] writes: Wichert Package: emacs19 Wichert Maintainer: [EMAIL PROTECTED] (Mark W. Eichin) Wichert 23742 emacs19 should probably be just emacs Why is this a release critical bug? emacs19 depends on a whole slew of packages, and it quite differently set up than the old emacs package. Also, there are now a number of packages that vie for the name Emacs, is not unreasonable to have the package renamed. I can understand that the originator may ``wish'' to have the old name retained, but is this an important enough objection to hold up Hamm or throw emacs19 out? I think no. Olease downgrade this bug (I would say to a wishlist), and get it out of the release critical list. manoj -- Imagination is more important than knowledge. Albert Einstein On Knowledge Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Hi, Dale == Dale Scheetz [EMAIL PROTECTED] writes: Dale Brandon Mitchell has come up with a better scheme than my numbering Dale alternative. Consider the following: Dale 2.0.8pre12.0.8-0pre1 Dale 2.0.8pre22.0.8-0pre2 Dale 2.0.8 2.0.8-1 Dale This has several advantages over my previous scheme. It preserves the Dale upstream version information in human readable form. It takes advantage Dale of the fact that dpkg will create a source upload for -0 and -1 sequences. Dale It naturally maintains the dpkg sequence ordering of the version numbers. Dale It doesn't need to use epochs. I actually like this. I still think that the aversion people have for epochs is rather more than is warranted from the technical objections (the mandatory longevity _is_ a technical objection), but the -0 approach is elegant. I am copying this to the policy list. manoj -- Statistics: A system for expressing your political prejudices in convincing scientific guise. Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Manoj Srivastava [EMAIL PROTECTED] writes: I actually like this. I still think that the aversion people have for epochs is rather more than is warranted from the technical objections (the mandatory longevity _is_ a technical objection), but the -0 approach is elegant. I mostly agree, but the argument that anything to the right of the dash should only reflect *Debian* related revisions does hold some water. My final take on this is that I would have been happy using epochs, but I can see that, in cases where we know that we're going to have a recurring pattern in the upstream sources, it could be considered more elegant to have a mini or right-side epoch that's somehow distinguished from the major or left-side epoch. The proposal above accomplishes this, but in a slightly ugly fashion. It might be a little nicer to just define a right side epoch. Something like: 2.0.7-1:alpha 2.0.7-1:pre1 etc. So anything to the right of a : that's to the right of the - would be the mini-epoch, and any package with a :foo at the end automatically sorted as older than the same version of the package without the :X (ignoring the debian revision). (I'd rather use 2.0.7:pre1-1, but we can't because then something like 1:2-4 becomes ambiguous.) Unfortunately this might require some major dpkg hackery akin to the hassle we had introducing epochs in the first place, but it would IMO be a cleanish solution to the problem. I've probably overlooked something obvious, so flame away... -- Rob Browning [EMAIL PROTECTED] PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Thu, 25 Jun 1998, Jules Bean wrote: Someone suggested this earlier in the discussion, and someone else pointed out that this is clearly against policy, since anything after the '-' should reflect debian-specific packaging changes, not upstream changes. Then I would argue that the policy statement is self contradictory. The -0 and -1 suffixes create (and declare) those releases to be source change releases, which are, obviously, upstream changes. This is how they are being used in this case, with the additional information added. If we simplify it to 2.0.8-0.1 then it should conform to your idea of policy better, but it doesn't convey as much information as the other form and it would make them look like non-maintainer releases. If policy must insist on leaving no wiggle room here, then my only recourse is to not release pre-release versions. I don't think that is a good idea, as it wastes our testing manpower, and weakens the final product. Manoj has already cc'd the suggestion to the policy list (Thanks Manoj!) so if you guys will haggle out something useful, that would be wonderful. From some other comments I have heard it seems that the list should first figure out how to maintain the document so we can all gain from the work you are doing. A committee to maintain the package would be fine, but that suggests another policy change ;-) Waiting is, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Dale Scheetz [EMAIL PROTECTED] writes: If we simplify it to 2.0.8-0.1 then it should conform to your idea of policy better, but it doesn't convey as much information as the other form and it would make them look like non-maintainer releases. Go with the more informative option, and make a proposal to get policy relaxed, or do something like the more radical solution I proposed. Either way, we now have technical solutions that will keep the info in the version number. Let's use one of those. If policy must insist on leaving no wiggle room here, then my only recourse is to not release pre-release versions. I don't think that is a good idea, as it wastes our testing manpower, and weakens the final product. Of course. That would be ridiculous. No one sane is arguing in favor of that. -- Rob Browning [EMAIL PROTECTED] PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hamm Bug Stamp-Out List for June 25, 1998
Manoj Srivastava [EMAIL PROTECTED] writes: Why is this a release critical bug? emacs19 depends on a whole slew of packages, and it quite differently set up than the old emacs package. Also, there are now a number of packages that vie for the name Emacs, is not unreasonable to have the package renamed. Yep, Debian no longer has a one true emacs : I think this bug should be closed. -- Rob Browning [EMAIL PROTECTED] PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: automating the Intents to package was Re: Please follow protocol when you announce your Intents to package
On Thu, 25 Jun 1998, Andreas Jellinghaus wrote: In article [EMAIL PROTECTED] you write: Ok, I'm game. I have had to fend off enough people from taking my packages that this is worth my time. Besides, I enjoy writing CGI, call me sick. What do we want/need/desire/despise and let's get this going. a database with the stuff from wnpp (list of programs that should be packages, and of orphaned/giveaway packages). would be nice to also handle tasks with that (e.g. someone to check permissions of files and suid/sgid bits in all packages). the whole thing with a i will do it button, maybe also with a history function. no access control: we will correct things, if some people do crap. a daily or weekly journal to debian-devel would also be nice... I had a package of mine moved to orphaned and I never knew about it, we should notify maintainers whenever thier packages are orphaned. - Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[joey: Intent to package mswordview]
I apologize, but I used the wrong list... Regards, Joey - Forwarded message from Martin Schulze joey - --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Hi! I plan to package this. It's distributed under the GPL. MSWordView is a program that can understand the microsofts word 8 binary file format (office97), it currently converts word into html, which can then be read with a browser. MSWordView is being actively worked on, and will be pretty bleeding edge for the next few weeks. It works fine so far. http://www.csn.ul.ie/~caolan/docs/MSWordView.html Regards, Joey --=20 / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / http://home.pages.de/~joey/ / The only stupid question is the unasked one / --azLHFNyN32YCQGCU Content-Type: application/pgp-signature -BEGIN PGP SIGNATURE- Version: 2.6.3ia iQCVAwUBNZKVvRRNm5Suj3z1AQF/9QP+L4MM3NDh4Y314ZtVm8jS1nrwLFtdYwtA TMh6pZZyuI/Lc75EwhF+gK7kbqJb/mDTJNYakuitB5U713zF0yDDPX5ZbRt/pxfq +Wph83gZBg62PIBuP32MMydovhvQv5U251AER3n/WSEKPNBQQvbGh9Ea1y7cWZ18 li0l55U3FCw= =TjtY -END PGP SIGNATURE- --azLHFNyN32YCQGCU-- - End forwarded message - -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / http://home.pages.de/~joey/ / The only stupid question is the unasked one / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0-beta CD Image mirror sites ?
--0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Previously Brederlow wrote: In what formats are those images provided? It would be nice to download the image in parts including md5sums and to have some additional error correction chunks like ras provides. You're just describing how rsync works. rsync retrieves the file in parts and compares checksums. And later you can update with rsync: it just compares checksums of parts and replaces only changed blocks. The problem with rsync at the moment is that if the transfer is interrupted, it throws away the partial image --- Andrew Tridgell said he'd fix this though. In the mean time I'd either use wget (which can continue interrupted transfers), and use HTTP, or do this: rsync the file, once it starts arriving, link the incoming file to a second name: ln .binary-i386.raw.a123456 binary-i386-saved-copy if you get a partial reception, mv the saved file to the proper name: mv binary-i386-saved-copy binary-i386.raw and re-do the rsync (and the saved-copy link) You'll need more disk space this way, because rsync keeps the old file untill all the new one arrives. If you use wget, and find that the md5sum that results is wrong, you should be able to fix any trasmission errors with rsync in short order, because it will only send the difference beween your broken copy and the real one. This is mostly covered here: http://www.uk.debian.org/debian-cd/ Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
On Thu, 25 Jun 1998, Philip Hands wrote: until 2.1.0 comes out, so that we wouldn't need to use a ``dirty, evil epoch''. No one has said anything about dirt or evil with respect to epochs. Sorry, I was being facetious, and I forgot the ;-) Policy says not to use them for this purpose. It also says not to use pre-release numbering schemes. Which doesn't leave much wiggle room. Hm. So how would you deal with the 2.0.99.9.1 example, without epochs ? I think when policy says that it means ``premeditated use of epochs'' is a bad way of dealing with silly ``pre'' upstream versions. If you issue a ``pre'' version by mistake, as happened in this case, it recommends that you get yourself out of the hole with an epoch. Brandon Mitchell has come up with a better scheme than my numbering alternative. Consider the following: 2.0.8pre1 2.0.8-0pre1 2.0.8pre2 2.0.8-0pre2 2.0.8 2.0.8-1 Doesn't this mean that the upstream source will be called: packagename_2.0.8.orig.tar.gz the upstream author might have something to say about that, since it looks like a final release, and they've only published: packagename-2.0.8pre2.tgz Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug #23877: Include autoup.sh and apt in hamm/hamm
Andreas [EMAIL PROTECTED] filed this against ftp.debian.org: Subject: please include apt and autoup in hamm/hamm/upgrade-i386/ To: [EMAIL PROTECTED] -- Package: ftp.debian.org,apt,autoup Version: N/A i think this is the right location. if people want to get all files they need to install or burn a cdrom, they should have one source, and not collect the files from several servers (which might be down or unreachable or ...). this bug should be either wishlist and ignored or marked grave IMO. andreas I think this needs a thorough discussion here, too, that´s why I forward it here. Jens --- [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 2048/E451C639 Jens Ritter Key fingerprint: 5F 3D 43 1E 24 1E CC 48 1E 05 93 3A A7 10 73 37 Nothing works better as it is supposed to. (Steven Chu) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Hi, Jules == Jules Bean [EMAIL PROTECTED] writes: Jules Someone suggested this earlier in the discussion, and someone Jules else pointed out that this is clearly against policy, since Jules anything after the '-' should reflect debian-specific Jules packaging changes, not upstream changes. Technically, this is correct, unless we take the stance that pre-releases are not really upstream releases (I find that quite reasonable -- isn't that implied by the very definition?); so these versions are released as a kinda debian-revision-to-detect-bugs, and take a -0* debian version. The options are: a) Use epochs, which can then never be done away with b) Play games with suffixes on the upstream version, and rely on both dpkg and people recognizing that the pre release suffix are older than the release suffix, c) pretend pre-releases are a -0 debian revision, and are not really upstream releases (I still contend they are not real upstream releases) manoj its all a matter of interpretation ;-) -- It might help if we ran the MBA's out of Washington. Admiral Grace Hopper Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Hi, Rob == Rob Browning [EMAIL PROTECTED] writes: Rob Manoj Srivastava [EMAIL PROTECTED] writes: I actually like this. I still think that the aversion people have for epochs is rather more than is warranted from the technical objections (the mandatory longevity _is_ a technical objection), but the -0 approach is elegant. Rob I mostly agree, but the argument that anything to the right of the Rob dash should only reflect *Debian* related revisions does hold some Rob water. Well, my contention is that pre-release are *not* upstream releases. They can arguably be termed a special release (not an upstream release) that the debian maintainer has chosen to make. This is a bit of a stretch, but acceptable, in my opinion. Rob It might be a little nicer to just define a right side epoch. Rob Something like: Rob 2.0.7-1:alpha Rob 2.0.7-1:pre1 Rob etc. Rob So anything to the right of a : that's to the right of the - would be Rob the mini-epoch, and any package with a :foo at the end automatically Rob sorted as older than the same version of the package without the :X Rob (ignoring the debian revision). Rob (I'd rather use 2.0.7:pre1-1, but we can't because then something like Rob 1:2-4 becomes ambiguous.) Interesting. A higher epoch makes a package newer, this new proposal make a package version older. Nice. We could even tack it to the left using a different symbol: 1:pre~libc-2.07-1 1:libc-2.07-1 1:pre~libc-2.07-1 libc-2.07-1 Or we can, as Rob proposed, tack it on to the right. The critical part is that this new mini-epoch makes a package sort older. manoj -- The difference between fantasy and science fiction is that one hast honest politicians scrupulous lawyers, and altruistic doctors, while the other only has beings from outer space. William John Watkins Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
possible bug in xemacs20/w3-el
I was trying to install the updated w3-el package, but it wouldn't work with xemacs on my machine, it seemed not to do any of the compiliation that was done for emacs20. It also killed the w3-el that came with xemacs. Is w3-el meant to be installed with xemacs? Shaya -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: libc6_2.0.7 release notes...
Manoj Srivastava [EMAIL PROTECTED] writes: Well, my contention is that pre-release are *not* upstream releases. They can arguably be termed a special release (not an upstream release) that the debian maintainer has chosen to make. This is a bit of a stretch, but acceptable, in my opinion. I don't think it's a good idea to do anything to make developmental versions second-class citizens, especially since we've had many cases where these versions were the only reasonable versions to be using at the time. -- Rob Browning [EMAIL PROTECTED] PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: libc6_2.0.7 release notes...
I think a reasonable policy statement for this would be something like: All pre-release versions will have debian revision of -0.x Maintainer release revisions will start at -1 and increment in whole numbers Non maintainer releases will add a point version to the left of the maintainer release number they are closest to or based on. Additional non maintainer releases will increment the point version number until the maintainer officially releases another debian revision. Non maintainer releases will not cause the removal from the archive of the maintainer release they are based on. This seems to solve future problems with upstream beta software revision numbers that don't allow us to use the upstream release number. OK, I opened my big mouth and have put on my asbestos undergarments :-) Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: libc6_2.0.7 release notes...
OOPS left should be right. One of these days I'll be able to tell my left and right apart! -Original Message- From: Patrick Ouellette [mailto:[EMAIL PROTECTED] Sent: Thursday, June 25, 1998 3:13 PM To: debian-policy@lists.debian.org Cc: Debian Developers Subject: RE: libc6_2.0.7 release notes... I think a reasonable policy statement for this would be something like: All pre-release versions will have debian revision of -0.x Maintainer release revisions will start at -1 and increment in whole numbers Non maintainer releases will add a point version to the left of the RIGHT maintainer release number they are closest to or based on. Additional non maintainer releases will increment the point version number until the maintainer officially releases another debian revision. Non maintainer releases will not cause the removal from the archive of the maintainer release they are based on. This seems to solve future problems with upstream beta software revision numbers that don't allow us to use the upstream release number. OK, I opened my big mouth and have put on my asbestos undergarments :-) Pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: About the Hamm Freeze (!)
Darren == Darren/Torin/Who Ever [EMAIL PROTECTED] writes: Darren Hmm. You're right. Any ideas on when this changed or was Darren I just on too much sleep-dep when I last looked at this. Darren (a while back) Been that way for quite a while AFAIK. Till very recently, though, dbmopen was hard-coded to GDBM_File or NDBM_File (can't remember which). -- Stephen --- all coders are created equal; that they are endowed with certain unalienable rights, of these are beer, net connectivity, and the pursuit of bugfixes... - Gregory R Block -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hamm Bug Stamp-Out List for June 25, 1998
On Thu, 25 Jun 1998, Dale Scheetz wrote: The upstream maintainer (Ulrich D.) insists that the relative links are correct and that making /usr a symlink to something else is evil. I'm running out of space and wanted to move subdirs of /usr to another partition. But because of relative links pointing back up to '/', this is impossible. I hope there is a good reason for using relative links, because as it is , /usr must be on the same partition as '/' , or else consist of an entire partition. John Lapeyre [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Retract packaging mswordview
Ouch! I can't package this software. At least not for now: File: ConvertUTF.C Author: Mark E. Davis Copyright (C) 1994 Taligent, Inc. All rights reserved. This code is copyrighted. Under the copyright laws, this code may not be copied, in whole or part, without prior written consent of Taligent. Taligent grants the right to use or reprint this code as long as this ENTIRE copyright notice is reproduced in the code or reproduction. The code is provided AS-IS, AND TALIGENT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL TALIGENT BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OR INABILITY TO USE THIS CODE, EVEN IF TALIGENT HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(l)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. This code may be protected by one or more U.S. and International Patents. TRADEMARKS: Taligent and the Taligent Design Mark are registered trademarks of Taligent, Inc. I have now contacted the author and hope he'll get a replacement. Regards, Joey PS: If s/o needs this package, contact me. -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / http://home.pages.de/~joey/ / The only stupid question is the unasked one / pgpYaw8m1mr2W.pgp Description: PGP signature
Re: libc6_2.0.7 release notes...
Rob Browning [EMAIL PROTECTED] wrote: I mostly agree, but the argument that anything to the right of the dash should only reflect *Debian* related revisions does hold some water. The question is: is it being used to bail out a maintainer who didn't take other steps to deal with the version information or not? 2.0.7-1:alpha 2.0.7-1:pre1 etc. So anything to the right of a : that's to the right of the - would be the mini-epoch, and any package with a :foo at the end automatically sorted as older than the same version of the package without the :X (ignoring the debian revision). Er.. but this violates least surprise. You'd expect that the 1: to the left of alpha would have higher precedence than the :alpha. I'd prefer to see 2.0.7-alpha:1 2.0.7-pre:1 Unfortunately this might require some major dpkg hackery akin to the hassle we had introducing epochs in the first place, but it would IMO be a cleanish solution to the problem. Yep, but (assuming we don't want to violate least surprise) we could use a subset of its functionality right now, with the existing sorting rules. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug #23877: Include autoup.sh and apt in hamm/hamm
Jens == Jens Ritter [EMAIL PROTECTED] writes: Jens Andreas [EMAIL PROTECTED] filed this against Jens ftp.debian.org: Subject: please include apt and autoup in hamm/hamm/upgrade-i386/ To: [EMAIL PROTECTED] -- Package: ftp.debian.org,apt,autoup Version: N/A i think this is the right location. if people want to get all files they need to install or burn a cdrom, they should have one source, and not collect the files from several servers (which might be down or unreachable or ...). this bug should be either wishlist and ignored or marked grave IMO. andreas Jens I think this needs a thorough discussion here, too, that´s Jens why I forward it here. Well, let's just do it! I see no problem with making such a directory for final hamm. Ben -- Brought to you by the letters J and O and the number 6. We are the music makers. And we are the dreamers of dreams. -- Willy Wonka Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/ I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0-beta CD Image mirror sites ?
Philip Hands [EMAIL PROTECTED] wrote: The problem with rsync at the moment is that if the transfer is interrupted, it throws away the partial image --- Andrew Tridgell said he'd fix this though. ... If you use wget, and find that the md5sum that results is wrong, you should be able to fix any trasmission errors with rsync in short order, because it will only send the difference beween your broken copy and the real one. If this is the case, it seems like you could pad out the file using dd /dev/zero . and then use rsync to correct the changes. -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.0-beta CD Image mirror sites ?
Philip Hands [EMAIL PROTECTED] wrote: The problem with rsync at the moment is that if the transfer is interrupted, it throws away the partial image --- Andrew Tridgell said he'd fix this though. ... If you use wget, and find that the md5sum that results is wrong, you should be able to fix any trasmission errors with rsync in short order, because it will only send the difference beween your broken copy and the real one. If this is the case, it seems like you could pad out the file using dd /dev/zero . and then use rsync to correct the changes. No need to dd, rsync just handles it anyway. Cheers, Phil. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: automating the Intents to package was Re: Please follow protocol when you announce your Intents to package
Well classes just ended (I was taking a summer course). So everyone put your heads together and tell me what you want. Once a general idea is agreed on I will happily code it. If we want vacations and stuff -- that is fine also. How much security are we allowing for here? How should we control access to the page?? Maybe it would be better to write a shell script on master/va for vacations? `vacation -on -time=5 days shaleh` (as long as shaleh=uid I get set to vacationing for x). This will then be displayed on a web page and/or sent to a mailing list once a week. Basically I enjoy small, stupid coding projects like this. Lets me vent. Brandon wrote: Hell, might as well implement the vacation stuff while we're at it. Shaleh's just wandered into the Twilight Zone cafeteria, where task after task is getting piled on his tray... :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Hamm Bug Stamp-Out List for June 25, 1998
Yeah, there's been enough discussion in this context. The decision to ditch the emacs name as a package name was in fact made for good reasons, a while back; just-before-the-release is the wrong time to revisit it. As emacs and emacs19 maintainer, I'm closing it, with this message. Feel free to discuss further on debian-devel, but I'd recommend either dropping it or taking it to the technical committee. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
non-html versions
Yo- I was woondering if non-html versions of the following exist and if so, where? Debian Packaging Manual Creating a Package with Debmake The New-maintainer's Debian Packaging Howto I would like to print and read all of these documents but going to every web page of every section and printing is very tedious. Are there text or Postscript versions of any of these? Also, where would one find the criteria for the different sections (i.e main, non-free, contrib)? Thanks again, Ian __ Ian Setford [EMAIL PROTECTED] PGP = F2 92 50 E3 CD D7 A2 D9 C4 CE 08 A6 98 E0 0F 58 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
SOLVED! :non-html versions
Thanks! __ Ian Setford [EMAIL PROTECTED] PGP = F2 92 50 E3 CD D7 A2 D9 C4 CE 08 A6 98 E0 0F 58 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot-disks 98-06-23 missing nfs support
The kernel in the latest base2_0.tgz seems to have a couple of small problems. Firstly, the PCMCIA modules can't find a number of symbols on start-up (no big deal to me but important to others). Secondly, and more importantly, support for the nfs file-system has been removed. This makes using the nfs method in dselect during the initial install impossible. Just doing my small bit for testing... :) -- Stephen --- all coders are created equal; that they are endowed with certain unalienable rights, of these are beer, net connectivity, and the pursuit of bugfixes... - Gregory R Block -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: automating the Intents to package was Re: Please follow protocol when you announce your Intents to package
--On Thu, Jun 25, 1998 4:16 pm -0400 Shaleh [EMAIL PROTECTED] wrote: Well classes just ended (I was taking a summer course). So everyone put your heads together and tell me what you want. Once a general idea is agreed on I will happily code it. If we want vacations and stuff -- that is fine also. How much security are we allowing for here? How should we control access to the page?? Maybe it would be better to write a shell script on master/va for vacations? `vacation -on -time=5 days shaleh` (as long as shaleh=uid I get set to vacationing for x). This will then be displayed on a web page and/or sent to a mailing list once a week. Basically I enjoy small, stupid coding projects like this. Lets me vent. Make sure you don't miss out on any prior work done around this area. Was netgod involved? I seem to remember someone saying so, but he hasn't commented on this thread yet. So I've been rude enough to Cc: him directly Jules /+---+-\ | Jelibean aka | [EMAIL PROTECTED] | 6 Evelyn Rd| | Jules aka | [EMAIL PROTECTED] | Richmond, Surrey | | Julian Bean | [EMAIL PROTECTED]| TW9 2TF *UK* | ++---+-+ | Debian GNU/Linux - Microsoft *does* have a year 2000 problem - | | and we're it! (paraphrased from IRC) | \--/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
