[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

FW: Problem: libc6 package in frozen damaged? (KMM43472C0KM)



what the hell is this ? 

can someone unsubscribe this e mail address ... pleeeezzzeeee 
i dont need to see the word m--------t in my debian list ... 



-----Original Message-----
From: piracy@microsoft.com [mailto:piracy@microsoft.com]
Sent: Monday, February 28, 2000 9:21 PM
To: Andrej Todosic
Subject: RE: Problem: libc6 package in frozen damaged? (KMM43472C0KM)


Hello Andrej,

Thank you for contacting the Microsoft Anti-Piracy Team.

The situation that you describe is not a piracy issue.  We suggest that 
you contact our Sales Dept at 1-800-426-9400.


You may also visit our Internet site on http://www.microsoft.com/piracy 
to review additional information on recognizing genuine Microsoft 
product and Microsoft's licensing policies.

Again, thank you for your interest in our anti-piracy campaign.

Microsoft Corporation
Worldwide Sales & Support Group



Original message follows: 
-------------------------



> ----------
> From: 	Andrej Todosic[SMTP:ATODOSIC@UBISOFT.QC.CA]
> Sent: 	Saturday, February 26, 2000 10:48:32 PM
> To: 	'Peter Cordes'; debian-testing@lists.debian.org
> Subject: 	RE: Problem: libc6 package in frozen damaged?
> Auto forwarded by a Rule
> 
there are 2 packages for libc6  -2 and -4 ....

do manually -2
and then go on witgh apt-get and all will work ...


-----Original Message-----
From: Peter Cordes [mailto:peter@llama.nslug.ns.ca]
Sent: Saturday, February 26, 2000 10:24 PM
To: debian-testing@lists.debian.org
Subject: Re: Problem: libc6 package in frozen damaged?


On Thu, Feb 24, 2000 at 09:09:22AM -0600, Nathan E Norman wrote:

> I was able to get around this, but I DO NOT recommend that anyone use
> my method!!  If you do, don't tell me about how screwed up your system
> got.

 It worked fine for me, on a fresh install of slink (2.1r4 CDs) 
upgrading to
woody.  Thank you very much for a solution to this problem! :)

> I created a file "/usr/bin/readlink" with the following contents:
>
>   #! /bin/sh
>   true
>
>   dpkg --force-depends -i libc6_2.1.3-4_i386.deb
>   apt-get -f install
>
> Luckily, everything still worked, and I was able to proceed to
> `apt-get upgrade', etc.

 apt-get dist-upgrade had been dieing on me with the pre-depend error
message.  BTW, timezones and stuff didn't even break when I did this.  
I'm
very impressed by the robustness of the package system at recovering 
from my
attempts to coerce it to proceed ;-)

 One reason this might have worked so well for me was that the slink 
system
had very few packages installed at the time, so there wasn't a lot to 
break.
(except apt, which survived :)

 I suppose the solution to this problem is to find a way to not use
readlink, so libc6 doesn't need to depend on a version of debianutils 
not
available in slink, or else the slink debian utils needs to have 
readlink
added so the libc6 pre-inst can use it.  (I really don't know debian 
very
well yet, so this might not make sense... sorry.)  I don't know if
feature-add upgrades to slink are kosher, but it seems to me that it 
would
be a good idea to make it so that one can upgrade from slink by apt-get
upgrade'ing slink to the latest version of all slink things, then 
apt-get
dist-upgrade after changing sources.list.  The current situation is not
good, because I imagine a lot of people have a slink CD, and use it to
install systems that will be upgraded to potato or woody.  hmm.

--
#define X(x,y) x##y
DUPS Secretary ; http://is2.dal.ca/~dups/
Peter Cordes ;  e-mail: X(peter@cordes.phys. , dal.ca)

"The gods confound the man who first found out how to distinguish the 
hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BCE


--
To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org


--  
To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact 
listmaster@lists.debian.org


--  
To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: