Modula-3 for Debian [Was: Bug#16663: lyx: depends on xforms0]
Hello Stuart! :-) On Wed, 7 Jan 1998, Stuart Lamble wrote: * Modula-3 (compiles into packages just fine with libc5; there are issues to deal with under libc6.) Which Modula-3 did you make? Was it SRC or Cambridge or some other implementation? :-) Anyway, about glibc2 support, I just spotted the following message in comp.lang.modula3: = Tue, 06 Jan 1998 07:47:59 comp.lang.modula3 Thread4 of 10 Lines 25Preliminary glibc2 support for Cambridge Modula-3 Richard Watts [EMAIL PROTECTED] at epona (really rrw1000.sel.cam.ac.uk), Preliminary glibc2 support is now available for Cambridge Modula-3. It can be obtained from: ftp://epona.ucam.org/pub/users/rrw/software/cam3-glibc2-patches/ These patches haven't been widely tested as yet, so be careful. Many thanks to Rajat Datta [EMAIL PROTECTED] and Michel Dagenais [EMAIL PROTECTED]. This is a fairly straightforward port, so other distributions should find it reasonably easy to apply (it's mainly template hacking). Anyone with a previous version of these patches is encouraged to upgrade - older versions had a bad declaration of struct_tm which caused tetris (among other things) to segfault. This version should be fixed - I've been over all the files in m3core/src/unix/linux-libc6. Please report the inevitable errors to [EMAIL PROTECTED] Richard. - - (SUBST O 1 0.3 1.0 1.0 (2 3)) (Type O 2 TextID1.0 1.0) (ABS O 3 foo 1.0 1.0 (6)) (SubstID O 4 2.2 1.0 1.0) (NullID L 6 foo 1.0 1.0 (4)) (TextID L 5 x 1.0 1.0) = If you are still busy, and if you don't mind, could you send me the Debian diff files? I would like to give it a shot to build the Cambridge Modula-3 and see how it works. :-) Thanks! (And thanks for packaging up Modula-3 for Debian! It must have been a lot of work! :-) Cheers, Anthony -- Anthony Fok Tung-Ling[EMAIL PROTECTED] Civil Engineeringhttp://www.ualberta.ca/~foka/ University of Alberta, CanadaKeep smiling! *^_^* -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re[2]: Linux Kernel list???
| On Saturday, 10 January 98, at 5:33:08 AM | Martin wrote about Linux Kernel list??? On Fri, Jan 09, 1998 at 03:41:31PM -0500, Adam Heath wrote: I was subscribed to linux kernel. I haven't received anything since Dec. 29. I have tried resubscribing several times. I even resent the original subscrition that got me started. I keep getting emails back saying user [EMAIL PROTECTED] doesn't exist. Can anyone help me on this? I thought I saw someone write in some email that they would post something on that list, maybe they could help. vger runs a majordomo. Send a mail to [EMAIL PROTECTED] with the following line in the body: subscribe linux-kernel Doh! I totally forgot about 'the other list manager.' Comes from not getting enough sleep. I love you. You love me. Together we can kill Barney. Adam Heath of Borg-Linux [EMAIL PROTECTED] Join the H.323 effort. Email http://www.debian.org - Get Your Own Linux! [EMAIL PROTECTED] with http://wwp.mirabilis.com/3375265 - Page Me the word subscribe in the body. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: libc5 to libc6 auto-upgrade script
This version should be close to good enough. The major change since the last one that was posted is the ability to upgrade from files in the current dir instead of a local mirror requirement. This script still needs testing. # upgrade a libc5 (bo) machine to libc6 (hamm). [...] # Revision History: [...] #v0.5: 1998-01-10 (Igor Grobman) #-added a note about upgrading libraries I ran this script on a Debian-1.3.1.r6 machine at work, using the method of placing all the necessary .deb files in the current directory. It worked great, with only a few warning messages [1] when it upgraded libg++ and removed wg15-locale. [1] From looking at strings dpkg, it was this warning message: warning: while removing %.250s, directory `%.250s' not empty so not removed One of the directories it complained about was /usr/lib/g++. That was the only one I was able to write down; they scrolled off the screen too fast. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Integrating main, non-us ftp site
If I attempt to do a dselect install via ftp from a local mirror which has both the main debian distribution as well as the non-US stuff, it doesn't work. Not without jumping through some serious hoops, at any rate. The problem is that the Packages file on the non-US site do not follow the same conventions as the packages file on the main ftp site. For bo, the main Packages file contains entries like Filename: stable/binary-i386/x11/9fonts_1-4.deb ^^ Filename: bo/binary-i386/bzip_0.21-3.deb ^^ For hamm, the main Packages file contains entries like Filename: dists/unstable/main/binary-i386/text/2utf_1.01.deb, ^^^ but the non-US site's Packages file contains entries like Filename: hamm/binary-i386/apache-ssl_1.2.4+1.11-2.deb I understand (I think) why this is the way it is, but it makes it impossible to use a symlink to get at the non-US stuff via ftp (using dselect). I don't have any great ideas for the bo links, but if the non-US site kept its files in dists/unstable/non-us life would be a lot easier. Any chance there will be a solution forthcoming, or do I need to shut up and hack the Packages files on my mirror? (Easy to do but mirror will be pissed). If no one else has any interest in doing anything like this then it's not worth implementing, I suppose. -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 phone: (605) 334-4454 fax: (605) 335-1173 mailto://[EMAIL PROTECTED] http://www.midco.net PGP Key ID: 0xA33B86E9 - Public key available at keyservers PGP Key fingerprint: CE03 10AF 3281 1858 9D32 C2AB 936D C472 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Snapshots of python 1.5 packages
I've put a snapshot of my python 1.5 non-maintainer packages at http://www.mathi.uni-heidelberg.de/~flight/debian-private/python/. Hi again, Gregor. I tried to download these today, but both lynx and netscape want to display the files as text and when you save it into a file it gets corrupted (text mode mangling?). That site does not accept anonymous ftp connections, so I can't ftp it. Do you have a real ftp site available? On the other hand, I'm leaving town Monday till the end of the month, so I won't have much time to test it anyway. (I'm going to Germany (!!) -- Duesseldorf/Ratingen.) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re:libc5 to libc6 auto-upgrade script
here's another update to igor's latest version. this one: - avoids duplicated code - tells the user what it's doing - has more error checking - guesses at the location of the mirror enjoy! ---cut here--- #! /bin/sh DPKG=`which dpkg` LDCONFIG=`which ldconfig` # uncomment for debugging #set -x #DPKG=echo dpkg #LDCONFIG=echo LDCONFIG # upgrade a libc5 (bo) machine to libc6 (hamm). # based on Scott Ellis' excellent Debian libc5 to libc6 Mini-HOWTO # document at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html # Author: Craig Sanders [EMAIL PROTECTED] # # Copyright Status: This script is hereby placed in the public domain # # Revision History: # v0.0: 1998-01-08 (morning) # - a rough transcript of scott's doc and my own experiences # v0.1: 1998-01-08 (night) # - a few bugfixes # - i got unlazy and put in the right subdirectories for each package. # should run a lot faster. # - now checks for failure at critical points and exits with a different # exit code for each failure. # - now uses 'binary-$(dpkg --print-installation-architecture)' instead # of 'binary-i386'. # v0.2: 1998-01-09 # - fixed the perl-base/perl install (thanks Lindsay!) # - improved the DEVPACKAGES=$(dpkg --get-selections...) and added -dbg # packages. # v0.3: 1998-01-09 (p.m.) # - fixed some directories # - changed -iB to -iBE so that if the script fails and is run again # it will not disturb things already in place. # - added a final dpkg --configure --pending. # - sanity check that we are in the right place added # v0.4: 1998-01-10 (Igor Grobman) # - made it possible to place all packages in current dir. # - added -pic packages to removal list. # - make sure dpkg-dev does not get selected for removal. # - moved dpkg-ftp and dpkg-mounted to the end. #v0.5: 1998-01-10 (Igor Grobman) # - added a note about upgrading libraries #v0.6: 1998-01-11 (Craig Sanders) # - restructured code to avoid code duplication. # - cleaned up a few things # - prints advisory notes telling user what's happening. # - added some more instructions on what to do about development packages. # - added code to guess some obvious locations for the mirror, otherwise # ask user. # # TODO: (probably by somebody else. this script is mostly good enough imo) # - this script _still_ needs more error checking :-) PKGS_LIBC6=base/ldso_*.deb base/libc5_*.deb base/libc6_*.deb \ base/timezones_*.deb admin/locales_*.deb PKGS_NCURSES=libs/ncurses3.0_*.deb base/ncurses3.4_*.deb PKGS_LIBRL=oldlibs/libreadline2_*.deb PKGS_LIBRLG=base/libreadlineg2_*.deb PKGS_BASH=base/bash_*.deb PKGS_LIBGPP=devel/libg++272_*.deb PKGS_DPKG=base/dpkg_*.deb utils/dpkg-dev_*.deb PKGS_LIBGDBM=base/libgdbm1_*.deb devel/libgdbmg1_*.deb PKGS_PERLBASE=base/perl-base_*.deb PKGS_PERL=interpreters/perl_*.deb PKGS_MOREDPKG=base/dpkg-ftp_*.deb admin/dpkg-mountable_*.deb cat __EOF__ This script will install the packages necessary to ensure a safe upgrade to hamm. You need to either have a local or remote mirror mounted, or have the latest versions of the following packages from hamm available in the current directory: ldso, libc5, libc6, timezones, locales, ncurses3.0, ncurses3.4, libreadline2, libreadlineg2, bash, libg++272, dpkg, dpkg-dev, dpkg-ftp, dpkg-mountable, libgdbm1, libgdbmg1, perl-base, and perl. If you are using a mirror, press 'm'. __EOF__ echo -n if you have the files in the current dir, press 'c': (m/c) read answer case $answer in m|M) # local mirror available # ask where the mirror is (this could do with some error checking) echo echo enter the full path to your local mirror of debian: echo e.g. /debian/dists/unstable/main/binary-i386/ echo TRY=/debian/dists/unstable/main/binary-i386 ~ftp/debian/dists/unstable/main/binary-i386 for i in $TRY ; do if [ -d $i ] ; then DEFAULT=$i fi done [ -n $DEFAULT ] echo or just hit enter to use $i. read DM [ -z $DM ] DM=$DEFAULT SEDSCRIPT=s:\([^ /]*/\):$DM/\1:g ;; c|C) # current directory SEDSCRIPT='s:[^ /]*/::g' ;; esac echo building list of package filenames to install... # convert PKGS_ variables to correct directory location PKGS_LIBC6=$( echo $PKGS_LIBC6 | sed -e $SEDSCRIPT ) PKGS_NCURSES=$( echo $PKGS_NCURSES | sed -e $SEDSCRIPT ) PKGS_LIBRL=$( echo $PKGS_LIBRL | sed -e $SEDSCRIPT ) PKGS_LIBRLG=$( echo $PKGS_LIBRLG | sed -e $SEDSCRIPT ) PKGS_BASH=$( echo $PKGS_BASH | sed -e $SEDSCRIPT ) PKGS_LIBGPP=$( echo $PKGS_GPP | sed -e $SEDSCRIPT ) PKGS_DPKG=$( echo $PKGS_DPKG | sed -e $SEDSCRIPT ) PKGS_LIBGDBM=$( echo $PKGS_LIBGDBM | sed -e $SEDSCRIPT ) PKGS_PERLBASE=$( echo $PKGS_PERLBASE | sed -e $SEDSCRIPT ) PKGS_PERL=$( echo $PKGS_PERL | sed -e $SEDSCRIPT ) PKGS_MOREDPKG=$( echo $PKGS_MOREDPKG | sed -e $SEDSCRIPT
Re: AucTeX
Your right about AucTeX, heck I've used it many times now. We did just switch LaTeX distributions though didn't we? Btw, if you have ever managed to make dvi files with ps images print right through magicfilter, I would love to hear how you did it. Is there really a ps2dvi program? Or do you mean the other way round ? dvips is invoked by magic filter, but the new LaTeX includes standard packages for including ps graphics. The .dvi docs for the graphics package say some additional commands (besides including the graphics package) may be needed to tell LaTeX what driver you are using (dvips in this case) since colors and graphics are really implemented there. Magicfilter has a feature called fpipe which the magicfilter docs state as being useful for 'programs which require seekable input, such as dvips, or which need to do multiple passes over an input file, such as grog'. I have once read something in the Linux Journal about using multiple passes to get embedded ps images to print right. I'll have to dig that up again, because for me the the images get left out, while all the text (including captions) appears. The pictures appear when previewing with xdvi though. What goes on exactly I do not know. Marcus -- Rhubarb is no Egyptian god.Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 Britton -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re:libc5 to libc6 auto-upgrade script
oops. i hard-coded 'binary-i386'. mea culpa. ---cut here--- #! /bin/sh DPKG=`which dpkg` LDCONFIG=`which ldconfig` # uncomment for debugging #set -x #DPKG=echo dpkg #DCONFIG=echo LDCONFIG # upgrade a libc5 (bo) machine to libc6 (hamm). # based on Scott Ellis' excellent Debian libc5 to libc6 Mini-HOWTO # document at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html # Author: Craig Sanders [EMAIL PROTECTED] # # Copyright Status: This script is hereby placed in the public domain # # Revision History: # v0.0: 1998-01-08 (morning) # - a rough transcript of scott's doc and my own experiences # v0.1: 1998-01-08 (night) # - a few bugfixes # - i got unlazy and put in the right subdirectories for each package. # should run a lot faster. # - now checks for failure at critical points and exits with a different # exit code for each failure. # - now uses 'binary-$(dpkg --print-installation-architecture)' instead # of 'binary-i386'. # v0.2: 1998-01-09 # - fixed the perl-base/perl install (thanks Lindsay!) # - improved the DEVPACKAGES=$(dpkg --get-selections...) and added -dbg # packages. # v0.3: 1998-01-09 (p.m.) # - fixed some directories # - changed -iB to -iBE so that if the script fails and is run again # it will not disturb things already in place. # - added a final dpkg --configure --pending. # - sanity check that we are in the right place added # v0.4: 1998-01-10 (Igor Grobman) # - made it possible to place all packages in current dir. # - added -pic packages to removal list. # - make sure dpkg-dev does not get selected for removal. # - moved dpkg-ftp and dpkg-mounted to the end. #v0.5: 1998-01-10 (Igor Grobman) # - added a note about upgrading libraries #v0.6: 1998-01-11 (Craig Sanders) # - restructured code to avoid code duplication. # - cleaned up a few things # - prints advisory notes telling user what's happening. # - added some more instructions on what to do about development packages. # - added code to guess some obvious locations for the mirror, otherwise # ask user. #v0.7: 1998-01-11 (CS) # - uh oh. i hard-coded in binary-i386. quick...better release another # version before James notices. # # TODO: (probably by somebody else. this script is mostly good enough imo) # - this script _still_ needs more error checking :-) ARCH=binary-$(dpkg --print-installation-architecture) PKGS_LIBC6=base/ldso_*.deb base/libc5_*.deb base/libc6_*.deb \ base/timezones_*.deb admin/locales_*.deb PKGS_NCURSES=libs/ncurses3.0_*.deb base/ncurses3.4_*.deb PKGS_LIBRL=oldlibs/libreadline2_*.deb PKGS_LIBRLG=base/libreadlineg2_*.deb PKGS_BASH=base/bash_*.deb PKGS_LIBGPP=devel/libg++272_*.deb PKGS_DPKG=base/dpkg_*.deb utils/dpkg-dev_*.deb PKGS_LIBGDBM=base/libgdbm1_*.deb devel/libgdbmg1_*.deb PKGS_PERLBASE=base/perl-base_*.deb PKGS_PERL=interpreters/perl_*.deb PKGS_MOREDPKG=base/dpkg-ftp_*.deb admin/dpkg-mountable_*.deb cat __EOF__ This script will install the packages necessary to ensure a safe upgrade to hamm. You need to either have a local or remote mirror mounted, or have the latest versions of the following packages from hamm available in the current directory: ldso, libc5, libc6, timezones, locales, ncurses3.0, ncurses3.4, libreadline2, libreadlineg2, bash, libg++272, dpkg, dpkg-dev, dpkg-ftp, dpkg-mountable, libgdbm1, libgdbmg1, perl-base, and perl. If you are using a mirror, press 'm'. __EOF__ echo -n if you have the files in the current dir, press 'c': (m/c) read answer case $answer in m|M) # local mirror available # ask where the mirror is (this could do with some error checking) echo echo enter the full path to your local mirror of debian: echo e.g. /debian/dists/unstable/main/$ARCH/ echo TRY=/debian/dists/unstable/main/$ARCH ~ftp/debian/dists/unstable/main/$ARCH for i in $TRY ; do if [ -d $i ] ; then DEFAULT=$i fi done [ -n $DEFAULT ] echo or just hit enter to use $i. read DM [ -z $DM ] DM=$DEFAULT SEDSCRIPT=s:\([^ /]*/\):$DM/\1:g ;; c|C) # current directory SEDSCRIPT='s:[^ /]*/::g' ;; esac echo building list of package filenames to install... # convert PKGS_ variables to correct directory location PKGS_LIBC6=$( echo $PKGS_LIBC6 | sed -e $SEDSCRIPT ) PKGS_NCURSES=$( echo $PKGS_NCURSES | sed -e $SEDSCRIPT ) PKGS_LIBRL=$( echo $PKGS_LIBRL | sed -e $SEDSCRIPT ) PKGS_LIBRLG=$( echo $PKGS_LIBRLG | sed -e $SEDSCRIPT ) PKGS_BASH=$( echo $PKGS_BASH | sed -e $SEDSCRIPT ) PKGS_LIBGPP=$( echo $PKGS_GPP | sed -e $SEDSCRIPT ) PKGS_DPKG=$( echo $PKGS_DPKG | sed -e $SEDSCRIPT ) PKGS_LIBGDBM=$( echo $PKGS_LIBGDBM | sed -e $SEDSCRIPT ) PKGS_PERLBASE=$( echo $PKGS_PERLBASE | sed -e $SEDSCRIPT ) PKGS_PERL=$( echo $PKGS_PERL | sed -e $SEDSCRIPT ) PKGS_MOREDPKG=$( echo $PKGS_MOREDPKG | sed -e $SEDSCRIPT )
Re: 2 versions of netcat
Robert Woodcock [EMAIL PROTECTED] writes: Also I've been hearing that there's a namespace conflict between nc (netcat) and nc (nedit-client). Any ideas on this one? I think it'd be easier to rename the latter because it's not a backend tool and thus not likely to be used in scripts. (And of course because it wouldn't affect me. :) I think the concensus last time this was discussed was that nedit-client should be modified. netcat's much more likely to be used in scripts and other places where changes will cause problems. -- Rob Browning [EMAIL PROTECTED] PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian logo license still not resolved
Ian Jackson [EMAIL PROTECTED]: How about: * We require that people acknowledge the use of our trademark, quoting `Debian penguin logo automatic licence version 1' and the date. * The licence gives permission only for the year following the date quoted. Then if we want to change the licence we publish version 2 instead, leaving version 1 available but stating that it is no longer available. Users of the logo have to go and check each year that the licence hasn't changed, and update the date on their acknowledgement. As stated by Will Lowe, I think a registration process could handle this (i.e. re-register annually under the current license terms). Draft text below. There are a number of unresolved questions: * Do we want a separate logo and licence for `powered by Debian'? I think the licese should be the same in the least. * What about hardware manufacturers who preinstall Debian ? Do we just let them mail us ? Again, see Will's registration suggestion. Ian. Now I'll play lawyer, but we should really have a real one handle the language of this. DEBIAN PENGUIN LOGO AUTOMATIC LICENSE The Debian Penguin Logo is a Trademark of Software in the Public Interest, Inc (`SPI'). 1. Grant You are hereby granted a license to use the trademark on a software or informational product or a service, and in advertising and promotion of such products and services, provided that: This shouldn't be a numbered cluase since every other clause listed is soley relevant to Grant (at least as currently worded). The rest of the numbering should of course be adjusted to reflect this. 2. Term 2.1. You must acknowledge the trademark, stating that it is used under licence and giving today's date (the date of issue of the licence), alongside the trademark itself. 2.2. Your licence expires one year from the date of issue. 3. Composition of your product or service 3.1. In the case of a software product, at least half of the product must be derived from the Debian GNU/Linux Distribution (`the Distribution'). 3.2. In the case of an informational product, such as a book or a set of web pages, at least half of the content matter must be related to the Distribution. 3.3. In the case of a service, at least one half of the practice of the service must be related to the use of the Distribution. I think this is bogus. People can't put the Debian logo on a web page unless half of the page is dedicated to debian? How about changing this to the content must be substantially derived from, or directly referential to 'the Distribution', and in accordance with this license. 4. Defamation You must not intend to defame Software in the Public Interest or the Distribution. This should read must not instead of must not intend, and should be tied into the indemnity clause. There might also be a mention of remedies available in the event of breach, but a professional would know better. I think that there should also be a statement limiting this cluase to the use of the logo, since that's what we're licensing. Someone may defame SPI in an article in a pubication, and use the logo in an advertisement in the same publication. As long the defemation doesn't occur or isn't directly associated with the use of the logo. Its a bit too fascist as stated above. 5. Termination A general point here, as with cluase 4, it may be prudent to state some method of remedying a breach up front (to save SPI legal costs later). One such remedy could be described and referred to by both clauses that allowed a breach condition to be remedied within 30 days by some agreeable means lest other remedies apply. The friendlier we are here, the better in my view. We are talking about freedom after all. There might also be a default dispute resolution procedure that makes it easy for offendors to state there case and clear the breach. 5.1. This automatic licence must not have been withdrawn (on or before the day of issue) for new licencing by a notice published alongside it by SPI. I'm not sure what this means, and that probably means some other people won't know either. This should be restated so its more clear. 5.2. Your licence may be terminated by SPI at any time, for any reason, by giving you notice via email or other convenient means. In this case, you will immediately cease to use the trademark, except that you may continue until no longer than one year from the date of issue to distribute any pre-existing inventory of a physical medium (such as a book or CD, or advertising that has already been printed) containing the logo. This sounds a bit harsh. How about a longer lead time than immeadiately and changing the notification to include or as announced on our public mailing list, or publish on our web site and getting rid of convenient since that has
version 0.8 of libc5 to libc6 auto-upgrade script
I just ran this script on an old system (somewhere between rex and bo) with lots of -dev packages installed. found and fixed two bugs. - libc6 conflicts with libpthread0 - i made a typo... PKGS_GPP instead of PKGS_LIBGPP. - some old version of perl's postrm didn't delete a .packlist file from /usr/lib/perl5/i486-linux/5.003/auto/Mail/.packlist. check for it and delete if found before installing perl. apart from those problems, it ran through cleanly. i think it's nearly finished (but i said that around version 0.2 didn't I :-) ---cut here--- #! /bin/sh DPKG=`which dpkg` LDCONFIG=`which ldconfig` # uncomment for debugging #set -x #DPKG=echo dpkg #LDCONFIG=echo LDCONFIG # upgrade a libc5 (bo) machine to libc6 (hamm). # based on Scott Ellis' excellent Debian libc5 to libc6 Mini-HOWTO # document at http://www.gate.net/~storm/FAQ/libc5-libc6-Mini-HOWTO.html # Author: Craig Sanders [EMAIL PROTECTED] # # Copyright Status: This script is hereby placed in the public domain # # Revision History: # v0.0: 1998-01-08 (morning) # - a rough transcript of scott's doc and my own experiences # v0.1: 1998-01-08 (night) # - a few bugfixes # - i got unlazy and put in the right subdirectories for each package. # should run a lot faster. # - now checks for failure at critical points and exits with a different # exit code for each failure. # - now uses 'binary-$(dpkg --print-installation-architecture)' instead # of 'binary-i386'. # v0.2: 1998-01-09 # - fixed the perl-base/perl install (thanks Lindsay!) # - improved the DEVPACKAGES=$(dpkg --get-selections...) and added -dbg # packages. # v0.3: 1998-01-09 (p.m.) # - fixed some directories # - changed -iB to -iBE so that if the script fails and is run again # it will not disturb things already in place. # - added a final dpkg --configure --pending. # - sanity check that we are in the right place added # v0.4: 1998-01-10 (Igor Grobman) # - made it possible to place all packages in current dir. # - added -pic packages to removal list. # - make sure dpkg-dev does not get selected for removal. # - moved dpkg-ftp and dpkg-mounted to the end. #v0.5: 1998-01-10 (Igor Grobman) # - added a note about upgrading libraries #v0.6: 1998-01-11 (Craig Sanders) # - restructured code to avoid code duplication. # - cleaned up a few things # - prints advisory notes telling user what's happening. # - added some more instructions on what to do about development packages. # - added code to guess some obvious locations for the mirror, otherwise # ask user. #v0.7: 1998-01-11 (Craig Sanders) # - uh oh. i hard-coded in binary-i386. quick...better release another # version before James notices. #v0.8: 1998-01-11 (Craig Sanders) # - added libpthread0 to the remove list. # - fixed PKGS_LIBGPP (i mistyped it as PKGS_GPP) # - some old version of perl's postrm didn't delete a .packlist file # from /usr/lib/perl5/i486-linux/5.003/auto/Mail/.packlist. check for # it and delete if found before installing perl. # # TODO: (probably by somebody else. this script is mostly good enough imo) # - this script _still_ needs more error checking :-) ARCH=binary-$(dpkg --print-installation-architecture) PKGS_LIBC6=base/ldso_*.deb base/libc5_*.deb base/libc6_*.deb \ base/timezones_*.deb admin/locales_*.deb PKGS_NCURSES=libs/ncurses3.0_*.deb base/ncurses3.4_*.deb PKGS_LIBRL=oldlibs/libreadline2_*.deb PKGS_LIBRLG=base/libreadlineg2_*.deb PKGS_BASH=base/bash_*.deb PKGS_LIBGPP=devel/libg++272_*.deb PKGS_DPKG=base/dpkg_*.deb utils/dpkg-dev_*.deb PKGS_LIBGDBM=base/libgdbm1_*.deb devel/libgdbmg1_*.deb PKGS_PERLBASE=base/perl-base_*.deb PKGS_PERL=interpreters/perl_*.deb PKGS_MOREDPKG=base/dpkg-ftp_*.deb admin/dpkg-mountable_*.deb cat __EOF__ This script will install the packages necessary to ensure a safe upgrade to hamm. You need to either have a local or remote mirror mounted, or have the latest versions of the following packages from hamm available in the current directory: ldso, libc5, libc6, timezones, locales, ncurses3.0, ncurses3.4, libreadline2, libreadlineg2, bash, libg++272, dpkg, dpkg-dev, dpkg-ftp, dpkg-mountable, libgdbm1, libgdbmg1, perl-base, and perl. If you are using a mirror, press 'm'. __EOF__ echo -n if you have the files in the current dir, press 'c': (m/c) read answer case $answer in m|M) # local mirror available # ask where the mirror is (this could do with some error checking) echo echo enter the full path to your local mirror of debian: echo e.g. /debian/dists/unstable/main/$ARCH/ echo TRY=/debian/dists/unstable/main/$ARCH ~ftp/debian/dists/unstable/main/$ARCH for i in $TRY ; do if [ -d $i ] ; then DEFAULT=$i fi done [ -n $DEFAULT ] echo or just hit enter to use $i. read DM [ -z $DM ]
Broken smail config
Subject says it all: newest version of smail is refusing to parse the config file so is failing to work. I may be able to send this: I may not receive it back. Andy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
non-maintainer releases and bug fixes
After having a look through the policy and dpkg documents, I can't seem to find anything about non-maintainer releases. It was only because someone emailed me and reopened bugs that I had closed on a non-maintainer release that I now know that you shouldn't do this (in case the regular maintainer misses the fix). In bug #11771, Hamish Moffatt said some things that seem to make sense, I thought I'd mention them here and then add one of my own :-) When a non-maintainer release fixes some bugs then: - if the bug was fixed upstream, the bug should be closed - if the bug was fixed by the non-maintainer, the fix should be sent to the bug tracking system and the bug should be marked as fixed. This would not close the bug report, but at least people would know. - if many bugs were fixed in one go, it might be more appropriate to close all those bugs and then file a new bug detailing the original bugs and the fixes. Adrian email: [EMAIL PROTECTED] | Debian Linux - www.debian.org http://www.poboxes.com/adrian.bridgett | Because bloated, unstable PGP key available on public key servers | operating systems are from MS -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re:libc5 to libc6 auto-upgrade script
You should make sure that you record which -dev packages are installed. You also might be able to set up a script that can take a list of -dev packages from bo, and tell dpkg to install the comparable packages from Hamm. Shaya -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: AucTeX
The .ps Files are included by dvips during his run as part of the lpd magicfilter. This process runs in a other directory (the spool directory). Xdvi runs in your working directory. The use of magicfilter makes no sense if you want to reference other files from your print file (like .ps files from .dvi). If you like to include the .ps files from magicfilter, then you must refence them by absolute names, like /home/somebody/work/latex/doc1/picture1.ps in your LaTeX-source. This has the disadvantage of not beeing portable, this work onlyn on systems, where magicfilter has access to home directory. The prefered way ist to run dvips in your working directory (e.g. done by AuCTeX) and feed the PostScript output to lpd. The command to do this is 'dvips -f file.dvi | lpr'. Regards, Hubert On Sat, 10 Jan 1998, Britton wrote: dvips is invoked by magic filter, but the new LaTeX includes standard packages for including ps graphics. The .dvi docs for the graphics package say some additional commands (besides including the graphics package) may be needed to tell LaTeX what driver you are using (dvips in this case) since colors and graphics are really implemented there. Magicfilter has a feature called fpipe which the magicfilter docs state as being useful for 'programs which require seekable input, such as dvips, or which need to do multiple passes over an input file, such as grog'. I have once read something in the Linux Journal about using multiple passes to get embedded ps images to print right. I'll have to dig that up again, because for me the the images get left out, while all the text (including captions) appears. The pictures appear when previewing with xdvi though. What goes on exactly I do not know. Britton -- Hubert Weikert DB1MQ Member of DARC (www.darc.de) and FITUG (www.fitug.de) Email: [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.cube.net/~weikert/ Book: Kryptographie mit dem Computer (PGP Praxis) ISBN 3-7905-1503-5 DM 19,80 PGP Key fingerprint = 99 38 A5 83 C8 76 F4 E1 A7 9C B9 70 9A A7 70 10 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re:libc5 to libc6 auto-upgrade script
On Sun, 11 Jan 1998, Shaya Potter wrote: You should make sure that you record which -dev packages are installed. You also might be able to set up a script that can take a list of -dev packages from bo, and tell dpkg to install the comparable packages from Hamm. somebody's already suggested that. i don't think it's worth the effort - partly because there is no one-to-one mapping between bo and hamm -dev packages, and partly because it would be a long and tedious job...made more difficult by the fact that you need both a bo system and a hamm system to compare package lists on. i'm not against it. i think it would be a good thing. if somebody feels like modifying the script to do that then they're perfectly welcome to do so. my autoupgrade script was written to do the dangerous part of the upgrade and leave the rest for the user to do in dselect. it does that quite well. imo, except for bugfixes and maybe polishing the user input bits it's basically finished. i ran it earlier tonight on an old rex (or rex++, not quite bo anyway) system, and it even worked on that. craig -- craig sanders -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Snapshots of python 1.5 packages
Mike Orr wrote: I've put a snapshot of my python 1.5 non-maintainer packages at http://www.mathi.uni-heidelberg.de/~flight/debian-private/python/. Hi again, Gregor. I tried to download these today, but both lynx and netscape want to display the files as text and when you save it into a file it gets corrupted (text mode mangling?). That site does not accept anonymous ftp connections, so I can't ftp it. Do you have a real ftp site available? Thanks for the hint. I've set the MIME type for .deb files to application/octet-stream, hope this works better. I have also updated the python 1.5 package snapshots on the page above. I think I'm gone release this stuff as non-maintainer packages in the next few days. Then, I've grabbed all the python-dependent packages from hamm (that's python-wpy, python-pmw, dpkg-python, dpkg-ftp-x, dpkglint and glint) and started to rework the for python 1.5. The maintainers of those packages may want to have a look at them. I think I'll release 1.5-0.1 first, file bugs against those packages and then wait for a while to give the maintainers a fair chance to update their packages. The current standings are on http://www.mathi.uni-heidelberg.de/~flight/debian-private/ I'm providing a default postinst and prerm for byte-compiling python add-on packages, which IMHO provides a better solution than 1.4. Gregor PS: If you're really interested in these packages, please have a look at the postinst/prerm/compileall.py part and tell me what you think. Ugly, but IMHO the only way to cleanly remove python 1.4 while upgrading. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
intent to package junkbuster
junkbuster is a www privacy-enhancer. Acting a a filtering proxy, it prevents private information (browser type, operating system..) from beeing revealed to the outside and blocks unwanted advertisements and cookies. original source: http://www.junkbusters.com license: GPL Markus -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: intent to package junkbuster
On Sun, Jan 11, 1998 at 01:56:41PM +, Markus Schauler wrote: junkbuster is a www privacy-enhancer. Acting a a filtering proxy, it prevents private information (browser type, operating system..) from beeing revealed to the outside and blocks unwanted advertisements and cookies. Already done. Package: junkbuster Priority: optional Section: web Installed-Size: 157 Maintainer: Paul Haggart [EMAIL PROTECTED] Architecture: i386 Version: 1.4b1-5 Depends: libc6 Recommends: www-browser Filename: dists/unstable/main/binary-i386/web/junkbuster_1.4b1-5.deb Size: 51210 MD5sum: 65d47addb12a45ff548e2454c7f088c0 Description: The Internet Junkbuster! Junkbuster is an instrumentable proxy that filters the HTTP stream between web servers and browsers. It can prevent ads and other unwanted junk from appearing in your web browser. It would be interesting to see if it is useful and possible to combine junkbuster and squid (with anonymisation turned on). Ray -- J.H.M. Dassen | RUMOUR Believe all you hear. Your world may [EMAIL PROTECTED] | not be a better one than the one the blocks | live in but it'll be a sight more vivid. | - The Hipcrime Vocab by Chad C. Mulligan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: intent to package junkbuster
Am Sun, Jan 11, 1998 at 02:57:56PM +0100, meinte [EMAIL PROTECTED]: On Sun, Jan 11, 1998 at 01:56:41PM +, Markus Schauler wrote: junkbuster is a www privacy-enhancer. Acting a a filtering proxy, it prevents private information (browser type, operating system..) from beeing revealed to the outside and blocks unwanted advertisements and cookies. Already done. Package: junkbuster Priority: optional I'd like to see junkbuster-blank packaged. This patched version of junkbuster inserts a 1x1 blank gif in the place of the filtered gifs. That provides a very smooth filtering without destroying the look of a website. By Töns -- _o) /\\ pgp fingerprint: 9B AC A5 CB C8 CC FC DC 25 B5 26 9A 5D 28 C0 3D _\_V -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: AucTeX
Some time ago I stumbled upon a package which provides a solution for this problem. It's called flpr and is a magic filter running in the user space so it can e.g. get to the .ps files. Further, it has some nice features as being able to print a .ps file in 2 or even 4 pages per physical side. It's available as a .deb package, but installs under /usr/local. It can be found under ftp://ftp.ci.tuwien.ac.at/pub/export/flpr I've been using it for almost all my printing. However, for plain ascii files I'm atp since flpr apparently calls a2ps with some new options which the current version of a2ps doesn't understand. Maybe someone can take this up and turn it into an official package which works full featured. Thanks, Ardo Hubert Weikert [EMAIL PROTECTED] writes: The .ps Files are included by dvips during his run as part of the lpd magicfilter. This process runs in a other directory (the spool directory). Xdvi runs in your working directory. The use of magicfilter makes no sense if you want to reference other files from your print file (like .ps files from .dvi). If you like to include the .ps files from magicfilter, then you must refence them by absolute names, like /home/somebody/work/latex/doc1/picture1.ps in your LaTeX-source. This has the disadvantage of not beeing portable, this work onlyn on systems, where magicfilter has access to home directory. The prefered way ist to run dvips in your working directory (e.g. done by AuCTeX) and feed the PostScript output to lpd. The command to do this is 'dvips -f file.dvi | lpr'. Regards, Hubert On Sat, 10 Jan 1998, Britton wrote: dvips is invoked by magic filter, but the new LaTeX includes standard packages for including ps graphics. The .dvi docs for the graphics package say some additional commands (besides including the graphics package) may be needed to tell LaTeX what driver you are using (dvips in this case) since colors and graphics are really implemented there. Magicfilter has a feature called fpipe which the magicfilter docs state as being useful for 'programs which require seekable input, such as dvips, or which need to do multiple passes over an input file, such as grog'. I have once read something in the Linux Journal about using multiple passes to get embedded ps images to print right. I'll have to dig that up again, because for me the the images get left out, while all the text (including captions) appears. The pictures appear when previewing with xdvi though. What goes on exactly I do not know. Britton -- Ardo van Rangelrooij home email: [EMAIL PROTECTED], [EMAIL PROTECTED] home page: http://www.tip.nl/users/ardo.van.rangelrooij PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
xload not part of xproc any more.
G'day All, I am the Debian developer of the xproc package. The upstream people have moved xload out of xproc because the one in standard X packages does the job now. However xcontrib does not include xload. I now have a bug ( #16939 ) saying that there is no xload, should I move this bug into the xcontrib package? - Craig -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Motif problems
Hello !! I'm a french user of the last Debian Gnu Linux 1.3.1. I'm student in programmation in an I.U.T.(french) and i've learned to program in Motif. I have Motif on my Linux and i've download Motifnls.deb to use applications make in Motif. The compilation of my sources are well done but when I try to execute the result there are a lot of errors outputs like : xprog : some .(things that i don't remember) : _Xt.. ... ... ... I hope you will help me as soon as it's possible. Thanks you very much for all answers. Guillaume BIBAUT ( [EMAIL PROTECTED] ) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Motif problems
On Mon, 12 Jan 1998, Guillaume BIBAUT wrote: I'm a french user of the last Debian Gnu Linux 1.3.1. I'm student in programmation in an I.U.T.(french) and i've learned to program in Motif. I have Motif on my Linux and i've download Motifnls.deb to use applications make in Motif. The compilation of my sources are well done but when I try to execute the result there are a lot of errors outputs Tu as aussi installe les paquets lesstif et lesstif-dev? like : xprog : some .(things that i don't remember) : _Xt.. ... ... ... I hope you will help me as soon as it's possible. It would be very helpful if you could send the real error messages... things that I don't remember is not very explicit... ;) -- - Vincent RENARDIAS [EMAIL PROTECTED],pipo.com,debian.org} - - Debian/GNU Linux: Pipo:WAW: - - http://www.fr.debian.orghttp://www.pipo.com http://www.waw.com - --- - La fonctionnalite Son Visuel vous delivre des avertissements visuels. - - [Message durant l'installation de Windows95] :wq -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .