From: Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com>
Subject: Re: debian's gnus package older than its emacs builtin gnus?
Date: Fri, 03 Jan 2003 21:04:16 +0100 [thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-znqi6lvj.fsf@gothgoose.net> (raw)
In-Reply-To: <87hecryyc8.fsf@pelisse.ddts.net>
* hobbes@easynet.be (Rémi Letot) wrote:
> Marcus Frings <iam-est-hora-surgere@fuckmicrosoft.com> writes:
>> Or do it the Debian-way:
>> http://people.debian.org/~srivasta
> Not updated since oort is in unstable. A better way now is to add
Manoj's current version is gnus_5.9.0-0.CVS.2003.01.02.1_all.deb at his
Debian homepage.
> unstable in sources.list and pin to stable. That way you can upgrade
> just the packages you want to the unstable version, like gnus.
Sorry, I don't agree. apt-pinning is pretty worthless these days because
too many packages depend on the new libc6 in unstable which makes it
quite useless to get Sid-packages for Woody as you certainly don't want
to import libc6-2.3.1-x from Sid to Woody. Okay, the Gnus package is an
exception concerning this dependency.
I prefer to get the source from Sid and do a backporting for Woody.
Regards,
Marcus
--
Fight fight fight, just push it away, fight fight fight, just push until it
breaks, fight fight fight, don't cry at the pain, fight fight fight, or watch
yourself burn again, fight fight fight, don't howl like a dog and never stop.
next prev parent reply other threads:[~2003-01-03 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18NoUD-0001YN-00@debian>
[not found] ` <87vg1k8ez5.fsf@glaurung.green-gryphon.com>
[not found] ` <87bs3bbvcl.fsf@jidanni.org>
2002-12-26 15:39 ` Kai Großjohann
[not found] ` <87hed3y3gh.fsf@kuntu.zangpo.org>
[not found] ` <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-k7hxx47j.fsf@gothgoose.net>
2003-01-02 22:35 ` Rémi Letot
2003-01-03 20:04 ` Marcus Frings [this message]
2003-01-03 21:50 ` Rémi Letot
2003-01-03 22:20 ` Marcus Frings
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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-znqi6lvj.fsf@gothgoose.net \
--to=iam-est-hora-surgere@fuckmicrosoft.com \
--cc=protagonist@gmx.net \
/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).