Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Cc: Mike Kupfer <mike.kupfer@sun.com>
Subject: Date of XEmacs' Gnus (5.10.7) package (was: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers)
Date: Fri, 17 Feb 2006 23:13:05 +0100	[thread overview]
Message-ID: <v9accpzlam.fsf_-_@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87d5ia1pnv.fsf@tleepslib.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Mon, 30 Jan 2006 10:16:04 +0900")

On Mon, Jan 30 2006, Stephen J. Turnbull wrote:

>>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>     Reiner> On Sun, Jan 29 2006, Steve Youngs wrote:
>
>> (package-get-info 'gnus 'date)
>>  => 2005-11-15
>>
>> That would come pretty close. :-)
>
>     Reiner> Could you suggest a way to check the date of the package
>     Reiner> without XEmacs?  Maybe an URL to the package ChangeLog or
>     Reiner> similar?
>
> In general, using XEmacs is the right way, because that will tell you
> what the bug reporter has installed.  If you want to check what's
> current, all of that information is in the package-index,
>
> ftp://ftp.xemacs.org/pub/xemacs/packages/package-index.LATEST.gpg

(progn (url-insert-file-contents
	"ftp://ftp.xemacs.org/pub/xemacs/packages/package-index.LATEST.gpg")
       (re-search-forward "^(gnus"))

... fine:

,----
| (package-get-update-base-entry (quote
| (gnus
|   (standards-version 1.1
|    version "1.89"
|    author-version "5.10.7"
|    date "2006-01-04"
|    build-date "2006-01-04"
`----

On Tue, Jan 31 2006, Mike Kupfer wrote:

(Mike, your article has a bogus References header:

,----
| Message-ID: <200601302324.k0UNOLos019384@athyra.sfbay.sun.com>
| References: <reinersteib+gmane@imap.cc>
| [...]
| In-Reply-To: Message from Reiner Steib <reinersteib+gmane@imap.cc>    of "Sun, 29 Jan 2006 23:40:15 +0100." <v9y80yu08g.fsf@marauder.physik.uni-ulm.de> 
| X-Mailer: MH-E 7.4.2; nmh 1.0.4; XEmacs 21.4 (patch 18)
`----

MH-E bug?)

> If you've got the mail generated by report-xemacs-bug, it has the
> version information for all the installed packages.  In this case, it's
>
> (gnus ver: 1.87 upstream: 5.10.7)
>
> You could then track this back with the package ChangeLog.

(url-insert-file-contents "http://cvs.xemacs.org/viewcvs.cgi/*checkout*/XEmacs/packages/xemacs-packages/gnus/ChangeLog?rev=HEAD&content-type=text/plain")

Good.

> 2005-11-15  Norbert Koch  <viteno@xemacs.org>
>
> 	* Makefile (VERSION): XEmacs package 1.87 released.
>
> 2005-11-15  Steve Youngs  <steve@sxemacs.org>
>
> 	* Sync with upstream stable branch.
> 	Please see the ChangeLog.upstream files for details.
[...]
> Does that help?

Yes, I hope so.  Thanks guys.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2006-02-17 22:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200601280127.k0S1RqD7007468@athyra.sfbay.sun.com>
     [not found] ` <87irs44xm9.fsf@tleepslib.sk.tsukuba.ac.jp>
2006-01-29 20:05   ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Reiner Steib
2006-01-29 22:24     ` Steve Youngs
2006-01-29 22:40       ` Reiner Steib
2006-01-30  1:16         ` Stephen J. Turnbull
2006-02-17 22:13           ` Reiner Steib [this message]
2006-01-30 23:24         ` Mike Kupfer
2006-01-30 23:39       ` where does package-get-info get its info from? (was: gnus 5.10.7 not rendering Latin-1 headers) Mike Kupfer
2006-01-31  1:11         ` where does package-get-info get its info from? Steve Youngs
2006-02-18  0:34     ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-02-18 14:55       ` Stephen J. Turnbull
2006-02-19 12:48         ` Reiner Steib
2006-02-19 22:11           ` Mike Kupfer
2006-02-19 23:22             ` Reiner Steib
2006-02-20  7:41               ` Katsumi Yamaoka
2006-02-20  9:40                 ` Katsumi Yamaoka
2006-02-20 11:30                   ` Katsumi Yamaoka
2006-02-20 19:20                     ` Mike Kupfer
2006-02-21 18:29                     ` Mike Kupfer
2006-02-20  8:46               ` Stephen J. Turnbull
2006-02-20  9:41                 ` Reiner Steib
2006-02-20 15:52                   ` Stephen J. Turnbull
2006-02-20 21:26                     ` Miles Bader
2006-04-09  8:14                   ` Aidan Kehoe
2006-04-11 18:35                     ` Reiner Steib
2006-04-13 22:34                       ` Mike Kupfer
2006-04-14  8:14                         ` Stephen J. Turnbull
     [not found] <17990.13620.262943.353149@parhasard.net>
2007-05-13  9:20 ` Gnus: Autoloads for parse-time.el variables (was: [PATCH] package building problems.) Reiner Steib
2007-05-13 12:45   ` Aidan Kehoe
2007-05-14 17:21   ` Mike Kupfer
     [not found] <m33awph096.fsf@Overgaard.mail.dk>
     [not found] ` <878x6g6yz7.fsf@uwakimon.sk.tsukuba.ac.jp>
2007-10-06 16:09   ` [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages Reiner Steib
2007-10-07 13:47     ` Thomas Overgaard
2007-10-09 21:13     ` gnus 5.10.8 for XEmacs (was [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages) Mike Kupfer

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=v9accpzlam.fsf_-_@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=mike.kupfer@sun.com \
    /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).