All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Nieuwenhuizen <janneke@gnu.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Cutting edge moved or shifting to .deb?
Date: Sun, 16 Jan 2000 17:44:08 +0100	[thread overview]
Message-ID: <200001161644.RAA14656@appel.flower> (raw)


Hi List,

Can someone provide us with a list of repositories for cutting edge
.rpm packages?  dev.linuxppc.org should be devel.linuxppc.org, but
apart from Franz Sirl's regular glibc/binutils/gcc/rpm updates (grand!),
not much seems to happen anymore since last September.  There's an 
almost-M12 mozilla, that crashes when I type in an url.  Then, there's
some odd stuff in contrib and updates at ftp.linuxppc.org.

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. 

Kernel development seems to have moved from vger to openprojects to
Paul's at linuxcare: rsync -auvz linuxcare.com.au::linux-pmac-devel.
I was able to compile and boot the 2.3.39 kernel, with only minor
troubles.  Initially, X (fbdev) comes up with a distorted screen,
but after a circle of zooming (C-M-+), it's fine.  Also, my eth0 (Bmac)
and eth1 (pci) get swapped, which makes for silly network-setup
problems.

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.

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?

Greetings,

Jan.

-- 
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-01-16 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-16 16:44 Jan Nieuwenhuizen [this message]
2000-01-16 17:39 ` Cutting edge moved or shifting to .deb? Dan Burcaw
2000-01-16 18:15 ` Martin Costabel
2000-01-16 18:43   ` Jan Nieuwenhuizen
2000-01-16 19:03 ` David N. Welton

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=200001161644.RAA14656@appel.flower \
    --to=janneke@gnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.