Re: Correct path for upgrading to libc6-dev?
On Jun 21, Mark Baker wrote For libg++, I'd wait until there's a libg++272 package, and install the development stuff from that; for ncurses there are libc6 versions of the library itself, I'm not sure about the development stuff but a force-depends seems to work (the header files aren't changed). I don't know about slang. I uploaded S-lang last week: libc5 compatibility: ii slang0.99.340.99.38-2.4backward compatibility shared library for li ii slang0.99.34-de 0.99.38-2.4S-Lang libc5 backward compatibility developm libc6 versions: ii slang0.99.380.99.38-2.4The S-Lang programming library, shared libra ii slang0.99.38-de 0.99.38-2.4The S-Lang programming library, development Ray -- LEADERSHIP A form of self-preservation exhibited by people with auto- destructive imaginations in order to ensure that when it comes to the crunch it'll be someone else's bones which go crack and not their own. - 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: Correct path for upgrading to libc6-dev?
You should certainly remove libdb-dev, since libc6-dev replaces it (as libc6 includes libdb.) I haven't done a libdb-altdev, and unless someone asks probably won't bother (the libgdbm* packages are already uploaded though.) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Correct path for upgrading to libc6-dev?
Mark Eichin [EMAIL PROTECTED] writes: You should certainly remove libdb-dev, since libc6-dev replaces it (as libc6 includes libdb.) I haven't done a libdb-altdev, and unless someone asks probably won't bother (the libgdbm* packages are already uploaded though.) Oh, okay. Do you know anything about the others? -- Brought to you by the letters K and I and the number 0. More testicles means more iron. -- Lunchlady Doris, The Simpsons Ben Gertzfield http://www.imsa.edu/~wilwonka/ Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Correct path for upgrading to libc6-dev?
In article [EMAIL PROTECTED], Ben Gertzfield [EMAIL PROTECTED] writes: You should certainly remove libdb-dev, since libc6-dev replaces it (as libc6 includes libdb.) I haven't done a libdb-altdev, and unless someone asks probably won't bother (the libgdbm* packages are already uploaded though.) Oh, okay. Do you know anything about the others? For libg++, I'd wait until there's a libg++272 package, and install the development stuff from that; for ncurses there are libc6 versions of the library itself, I'm not sure about the development stuff but a force-depends seems to work (the header files aren't changed). I don't know about slang.
Re: Correct path for upgrading to libc6-dev?
In article [EMAIL PROTECTED],
Ben Gertzfield [EMAIL PROTECTED] writes:
You should certainly remove libdb-dev, since libc6-dev replaces it (as
libc6 includes libdb.) I haven't done a libdb-altdev, and unless
someone asks probably won't bother (the libgdbm* packages are already
uploaded though.)
Oh, okay. Do you know anything about the others?
For libg++, I'd wait until there's a libg++272 package, and install the
development stuff from that;
It's sortof difficult to wait till May 18, as that's when
libg++272 was released, along with libg++272-dev.
for ncurses there are libc6 versions of the
Hell, ncurses was only uploaded one week ago or something, libg++272
is _much_ older!
(And, why do you call it libg++272, why not libg++27g, that's what
the standard tells us to use. I only chose libg++272 because
HJ Lu did that, and it doesn't seem to cause problems).
--
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Correct path for upgrading to libc6-dev?
*wavewave* I'm finally ready to move my Debian box up to libc6-dev, but it seems there are all sorts of dependancies that aren't solved by moving to the newest version of everything (ncurses-dev, slang-dev, libg++-dev, and libdb-dev still depend on libc5-dev..) I took a peek at libc5-altdev, but it depends on an older version of libc5 than I have (5.4.23-4, while I have 5.4.23-6..) Should I downgrade my libc5? Should I just remove ncurses-dev, slang-dev, libg++-dev, and libdb-dev? Help! :) -- Brought to you by the letters A and P and the number 11. Porco ga daisuki! -- Fio, Porco Rosso Ben Gertzfield http://www.imsa.edu/~wilwonka/ Finger me for my public PGP key. I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
