RE: libc5 to libc6: purge or install *-dev?

1997-11-17 Thread Remco Blaakmeer
On Sun, 16 Nov 1997, George Bonser wrote:

> Didn't save me.  I followd the instructions on an old test system here and
> STILL managed to blow it up. I was tired and cranky ... got to the part where 
> I
> manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i
> libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends
> libc5 thinking that my next command would be to install libc6 ... there was no
> next command on that system.

Well, this seems to be a great example of the "Golden Rule For Moving From
Libc5 To Libc6":

Do NOT use --force on dpkg, the conflicts are there for a good reason!


> Seems kind of a chicken and egg problem to me right now but I will get it
> sorted out, cant install libc6 'cause it conficts with libc5, can't remove
> libc5, I am considering the Kavorkian method of point-and-click system admin 
> at
> this point.

As with many libraries that exist in a libc5-version and a libc6-version: 
First upgrade the libc5-version to the one in unstable and then install
the libc6-version. If you'd just point dselect to unstable, you'd have no
problem with this. If you do it with dpkg only, you'll have to figure out
all dependencies and conflicts by yourself.

I am sure this is in the libc5-libc6-Mini-HOWTO. Or else it should be.

Remco


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: libc5 to libc6: purge or install *-dev?

1997-11-16 Thread George Bonser

Maybe I have an old version ... at the very end it finally mentiones the
conflict.  the last item in the howto.  I think it should be moved up to
where the lists of packages you need are mentioned.


On 16-Nov-97 joost witteveen wrote:
> 
> I'm sure that is mentioned in the libc5-libc6-mini-howto.
>> 
> 
> 
> -- 
> joost witteveen, [EMAIL PROTECTED]
> 
> Potentially offensive files, part 5: /dev/random.
> `head -c 4 /dev/random` may print 4-letter words (once every approx 4e8
> tries).
> 
> 
> --
> 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: libc5 to libc6: purge or install *-dev?

1997-11-16 Thread oehansen

Þann 16-Nov-97 skrifar Jameson Burt:
> 
> Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their 
> operating systems.  A few changes could save a few more people.  When a
> person 
> ruins zher operating system by badly adding packages from hamm, zhe consumes 
> weeks of time.  You might save tens of people a hundred wasted hours each.
> 
  That's a really good point, one that was needed...

  But *notice*, that it is also possible to break your system by
upgrading in unstable (hamm)...

  Here are two issues, from hamm Locales, when a program that is using
glibc does setlocale, it does not get it's locale information from the
localedata that comes with glibc (namely /usr/share/i18n/locales), but
rather takes it from the older libc5 localeinfo /usr/share/locales (not
that *that* really matters, but it raises a question as to wether *other*
functions in glibc have an _overrride_ value).

  Many Unix programs are really careless about memory allocations, now
many programs will get 'SIGSEGV' and break, and the error occurs inside
free(), as free is called with a stray pointer either from a library or
from the program... this is because glibc has runtime options that allows
well constructed programs to use malloc and have it fast, but also to set
it secure for other programs.  And a lot of libraries and programs aren't
well constructed... and the default is for malloc to be _fast_ :(

...and two issues concerning GNU C++,

  The C++ package in hamm is not compiled with setlocale functioning.  So,
if you do setlocale in your program, and then 'printf("%.2f", value)' your
value will not print "100,00" even if your decimal point is set to ','...
as it should do.

  And using 'malloc' inside a C++ program, will corrupt it and _may_ cause
it to SIGSEGV at some point...


Orn Einar Hansen [EMAIL PROTECTED]
  [EMAIL PROTECTED]
voice+fax; +46 035 217194


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: libc5 to libc6: purge or install *-dev?

1997-11-16 Thread joost witteveen
> > 
> > Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their 
> > operating systems.  A few changes could save a few more people.  When a
> > person 
> > ruins zher operating system by badly adding packages from hamm, zhe 
> > consumes 
> > weeks of time.  You might save tens of people a hundred wasted hours each.
> 
> Didn't save me.  I followd the instructions on an old test system here and
> STILL managed to blow it up. I was tired and cranky ... got to the part where 
> I
> manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i
> libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends
> libc5 thinking that my next command would be to install libc6 ... there was no
> next command on that system.

the libc5 from hamm doesn't conflict with libc6. So, you should have
installed the libc5 from hamm, before installing libc6.

I'm sure that is mentioned in the libc5-libc6-mini-howto.
> 


-- 
joost witteveen, [EMAIL PROTECTED]

Potentially offensive files, part 5: /dev/random.
`head -c 4 /dev/random` may print 4-letter words (once every approx 4e8 tries).


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


RE: libc5 to libc6: purge or install *-dev?

1997-11-16 Thread George Bonser
> 
> Your libc5-libc6-Mini-HOWTO.txt saves many people from ruinning their 
> operating systems.  A few changes could save a few more people.  When a
> person 
> ruins zher operating system by badly adding packages from hamm, zhe consumes 
> weeks of time.  You might save tens of people a hundred wasted hours each.

Didn't save me.  I followd the instructions on an old test system here and
STILL managed to blow it up. I was tired and cranky ... got to the part where I
manuall did a dpkg on libc6 ... but it conflicts with libc5 ... (dpkg -i
libc6_2.0.4-1.i386.deb) so without thinking I did a dpkg -r --force depends
libc5 thinking that my next command would be to install libc6 ... there was no
next command on that system.

Believe me, I am spitting nails right now. Since I can not seem to find any way
of installing the new distribution from scratch, only upgrading from stable, I
am more than a little frustrated.  I am reloading the stable base on that
system and am going to upgrade the default installed packages to the versions
on the ftp site and move my dpkg status file from yesterday back to the current
one and hope for the best.  In other words, I am installing base OVER my
current install, will upgrade the base packages back to where they were, move
the status file and hope I am back to where I was before I screwed up.

Seems kind of a chicken and egg problem to me right now but I will get it
sorted out, cant install libc6 'cause it conficts with libc5, can't remove
libc5, I am considering the Kavorkian method of point-and-click system admin at
this point.



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .