From: "David N. Welton" <davidw@linuxcare.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Cutting edge moved or shifting to .deb?
Date: Sun, 16 Jan 2000 11:03:20 -0800 [thread overview]
Message-ID: <20000116110320.A27127@linuxcare.com> (raw)
In-Reply-To: <200001161644.RAA14656@appel.flower>; from janneke@gnu.org on Sun, Jan 16, 2000 at 05:44:08PM +0100
<debian developer hat>
On Sun, Jan 16, 2000 at 05:44:08PM +0100, Jan Nieuwenhuizen wrote:
> On the other hand, ftp.<cc>.debian.org has stuff such as XFree
> 3.3.6, emacs-20.5 (which is good, I was having a lot of trouble with
> my 20.3 emacs), a recent mozilla-M12, that can be alienised, but the
> glibc seems to be 'stuck' at libc6_2.1.2-5.deb.
Yes, and being an open organization, anyone can participate,
contribute bug fixes, and discuss the state of things on the mailing
lists. What's more, you get the same environment across all
architectures, which currently include ARM, Alpha, m68k, i386, the
early stages of a mips port, ppc, and sparc. Most of the non i386
architectures are supported by autobuilder systems which let them keep
up with i386, where most of the development occurs. And there are a
*lot* of .deb's available.
> On a related, totally off-topic note: I can't seem to find how to
> verify package integrity with dpkg, eg, the equivalent for rpm
> --verify.
Dpkg doesn't work that way, although the capability might be added in
the future. Ask on the debian lists for details.
> I've setup a partition this summer with a minimal debian
> installation, just to test it out. But at that time, I had only
> low-bandwidth and deer internet access. The debian distribution was
> having quite some problems then, and updating by burning a cdrom a
> week didn't really work for me. Now I'm using that partition to run
> compiles on: I removed all docs and other stuff, so that a lot of
> packages should be reinstalled. However, `chroot /mnt/debian/root
> dpkg --audit', and `dpkg --status <some-doc-truncated-package>' say
> all is ok? How to fix and upgrade this?
Well, if your packages are out of date, you can just grab all the
latest ones, which should reinstall all the necessary files that have
been wiped. That's a good place to start, at least.
You really want to get 'apt' up and running - it's fantastic! It
allows you to run commands like "apt-get install emacs20" and it will
go fetch emacs off the net for you and install it. If you currently
have apt on there, you can run "apt-get update", and "apt-get
dist-upgrade", and that should get you the latest versions of
everything.
</debian developer hat>
Good luck,
--
David N. Welton, Developer, Linuxcare, Inc.
415.354.4878 x241 tel, 415.701.7457 fax
davidw@linuxcare.com, http://www.linuxcare.com/
Linuxcare. At the center of Linux.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-01-16 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 16:44 Cutting edge moved or shifting to .deb? Jan Nieuwenhuizen
2000-01-16 17:39 ` Dan Burcaw
2000-01-16 18:15 ` Martin Costabel
2000-01-16 18:43 ` Jan Nieuwenhuizen
2000-01-16 19:03 ` David N. Welton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000116110320.A27127@linuxcare.com \
--to=davidw@linuxcare.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).