Rich Rudnick <[EMAIL PROTECTED]> writes:
> Me, I keep a minimal woody on another partition :)
Yeah, it's always good to have a backup woody in case your primary one
breaks. After all, you always want to minimize your woody's downtime.
--
People said I was dumb, but I proved them!
msg13145/p
On Thu, 2002-11-14 at 10:22, Craig Dickson wrote:
> Colin Watson wrote:
>
> > You explain to the common man not to use unstable. :)
> >
> > It *certainly* shouldn't have broken in the first place, but accidents
> > happen. If one doesn't have enough system administration experience to
> > cope wi
On Thu, Nov 14, 2002 at 01:45:19PM -0600, Mark A. Bialik wrote:
> Osamu Aoki wrote:
>
> > > The alternative would be to run a different distribution or compile from
> > > source, and we wouldn't want that, would we? :)
> >
> > No that is not correct if you understand basics of Debian.
>
> Sarca
On Thu, Nov 14, 2002 at 04:17:33PM -0500, Robert L. Harris wrote:
>
>
> Very nice writeup.
>
> Question, what if you want foo from unstable and it requires a version
> of bar in unstable but your existing bar is from testing? What if bar
> isn't installed at all and the requirement is going to
han E Norman ([EMAIL PROTECTED]):
> Date: Thu, 14 Nov 2002 15:13:58 -0600
> From: Nathan E Norman <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: argh! aptitude/dselect/apt-get dieing
> X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/245342
>
> On
On Thu, Nov 14, 2002 at 11:54:51AM -0600, Mark A. Bialik wrote:
> Colin Watson wrote:
>
> > This may sound callous, but those "some people" - or at least those
> > people who *can* fix it, perhaps not trivially easily - are the only
> > people who should be using unstable.
>
> ... and there are s
On Thu, Nov 14, 2002 at 11:22:30AM -0800, Osamu Aoki wrote:
> I know Brian who complained this in -devel list was rightfully pissed at
> the care taken by the uploader and he can deal with this situation
> without problem. Most interesting part of Colin's comment is
> > This may sound callous, bu
Osamu Aoki wrote:
> > The alternative would be to run a different distribution or compile from
> > source, and we wouldn't want that, would we? :)
>
> No that is not correct if you understand basics of Debian.
Sarcasm, my man, Sarcasm. :)
Mark
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Craig Dickson wrote:
> What's wrong with compiling from source? If you download the Debian
> source package, it should have everything you need to build a proper
> deb package, so what's the problem? Even if you don't build a deb, you
> just install to /usr/local, and as long as you don't break an
Hi,
On Thu, Nov 14, 2002 at 11:54:51AM -0600, Mark A. Bialik wrote:
> Colin Watson wrote:
>
> > This may sound callous, but those "some people" - or at least those
> > people who *can* fix it, perhaps not trivially easily - are the only
> > people who should be using unstable.
>
> ... and there a
Mark A. Bialik wrote:
> ... and there are some people who run unstable because certain packages
> and/or versions of packages they need are only in unstable.
>
> The alternative would be to run a different distribution or compile from
> source, and we wouldn't want that, would we? :)
What's wro
Colin Watson said:
> This may sound callous, but those "some people" - or at least those people
> who *can* fix it, perhaps not trivially easily - are the only people who
> should be using unstable.
speak for yourself :) I suggested a fix to someone who had this
problem and they said it worked f
On Thu, Nov 14, 2002 at 11:26:10AM +, Colin Watson wrote:
> This may sound callous, but those "some people" - or at least those
> people who *can* fix it, perhaps not trivially easily - are the only
> people who should be using unstable.
Exatly :-) Where is chroot.
I think it is lack of sim
Colin Watson wrote:
> You explain to the common man not to use unstable. :)
>
> It *certainly* shouldn't have broken in the first place, but accidents
> happen. If one doesn't have enough system administration experience to
> cope with this kind of thing (after all, it was "just" everything
> wri
Colin Watson wrote:
> This may sound callous, but those "some people" - or at least those
> people who *can* fix it, perhaps not trivially easily - are the only
> people who should be using unstable.
... and there are some people who run unstable because certain packages
and/or versions of pack
On Thu, Nov 14, 2002 at 02:22:25AM -0600, Mark A. Bialik wrote:
> Brian Nelson wrote:
> > The problem is simply that the library file was misnamed to
> > libstdc++libc6.2-2.so.3.
>
> This may be easy enough for some people to fix, but how exactly do
> explain to the common man how to fix it when t
Brian Nelson wrote:
> The problem is simply that the library file was misnamed to
> libstdc++libc6.2-2.so.3.
This may be easy enough for some people to fix, but how exactly do
explain to the common man how to fix it when the basic tools (dselect
and apt-get) no longer work?
At least on my system
iain d broadfoot <[EMAIL PROTECTED]> writes:
> apt-get: error while loading shared libraries: libstdc++-libc6.2-2.so.3:
> cannot open shared object file: No such file or directory
>
> same thing for dselect and aptitude.
And for every other C++ program you have...
> any thoughts??
Beat maintain
nate wrote:
iain d broadfoot said:
apt-get: error while loading shared libraries: libstdc++-libc6.2-2.so.3:
cannot open shared object file: No such file or directory
same thing for dselect and aptitude.
/
any thoughts??
find the package that has that fil
iain d broadfoot said:
> apt-get: error while loading shared libraries: libstdc++-libc6.2-2.so.3:
> cannot open shared object file: No such file or directory
>
> same thing for dselect and aptitude.
>
> /
>
> any thoughts??
find the package that has that file(us
apt-get: error while loading shared libraries: libstdc++-libc6.2-2.so.3:
cannot open shared object file: No such file or directory
same thing for dselect and aptitude.
/
any thoughts??
i'm scared to reboot in case it doesn't come back at all.
(shivers horri
21 matches
Mail list logo
