[NCLUG] downgrading libc6

[John Gilmore]

no, you fail to understand. It worked last week, then I upgraded. Now
it don't work no more :( I probably should have paid more attention to
something in /etc/apt, but I couldn't tell you what exactly. I'm
running testing (or trying to) and I have no idea which version this
poorly-updated libc6 came from.

I have a backup, but I hesitate to trust it. I also hesitate to issue
the commands to restore - It's a live backup, and I hadn't intended to
use it to back out a major upgrade. Though it's looking more and more
like that's what I need to do. Let's see...

cp -a /home /media/backup
rm -rf /
cp -a /media/backup/0.weekly/* /
cp -a /media/backup/home .

something wrong there.... :)

Probably better to use rsync -

  #this step is (strictly speaking) not needed - I already have recent
backups...
cp -a /home /media/backup
  #Use rsync to force the destination directory to look like the source(s)
rsync --delete-after  -ax  /media/backup/0.weekly/* /
  #Restore "newest" home directory image
rm -rf /home
cp -a /media/backup/home /home

What thinkest thou? I think this stuff is scary. I may have backups,
but that doesn't mean that I don't fear borking my system. I really
don't want to spend hours reinstalling crap.

On Jan 7, 2008 8:59 PM, Matt Taggart <matt at lackof.org> wrote:
> > herb:/var/cache/apt# dpkg-scanpackages -m archives /dev/null | gzip >
> > archives/Packages.gz
> >
> > Is there any problems I should be aware of with using the above
> > command? It strikes me as inherently evil, but I couldn't tell you
> > why.
>
> Probably fine although I use the dannf prescribed method(tm)
>
>   apt-ftparchive packages . > Packages
>
> (from http://dannf.org/docs/backporting-debs.txt )
> >
> > I've got an error in a java application I'll attach the "log" file it
> > gives.
>
> You forgot the log.
>
> > I suspect that it was caused by upgrading from
> > libc6_2.6.1-1+b1_i386.deb
> > to
> > libc6_2.7-5_i386.deb
> > Though I couldn't prove it except by downgrading. I have a backup that
> > works, I could try that chrooted, that may prove it... Nope, can't
> > connect to the X server. (duh)
>
> libc is the most critical userspace package, generally an upgrade of that
> large a magnitude (2.6.1-1+b1 to 2.7-5) would only occur when going from
> one release to another (or a really old unstable to a newer unstable), and
> then you'd probably be upgrading the rest of the system at the same time.
> While you can drop a newer libc on your system, you'd probably be doing it
> for a reason like the newer applications you want require it. I suspect
> that's what's happening in your case (the java thing).
>
> So the java application you want to run requires a newer release than what
> you have, so other than the piecemeal upgrade you already tried, additional
> options are to upgrade your system to what that application requires, or to
> see if you can get/build a version of the application for your current
> release (this is sometimes referred to as a "backport", compiling newer
> software on an older release of system libraries).
>
> Java is one of those things that's still changing pretty fast in the Linux
> world, I'm not surprised the application requires something newer. This is
> a cost of using Java :P
>
> --
> Matt Taggart
> matt at lackof.org
>
>
> _______________________________________________
> NCLUG mailing list       NCLUG at nclug.org
>
> To unsubscribe, subscribe, or modify
> your settings, go to:
> http://www.nclug.org/mailman/listinfo/nclug
>