Lars Magne Ingebrigtsen wrote: > If the admin adds gcwccd-curlpp-devel <at> m.gmane.org to list subscription > list, that should fix things. This email address _is_ subscribed to the list. That doesn't fix things, although. -- -- Piotr Dobrogost *** curlpp.org - c++ wrapper for libcurl ***
Piotr Dobrogost <pd <at> 2009.gmane.dobrogost.pl> writes: >> If the admin adds gcwccd-curlpp-devel <at> m.gmane.org to list subscription >> list, that should fix things. > > This email address _is_ subscribed to the list. > That doesn't fix things, although. Gmane isn't receiving any email for that address (today at least), so the problem must be on the Google side. -- -- (domestic pets only, the antidote for overdose, milk.) larsi <at> gnus.org * Lars Magne Ingebrigtsen
Try this simple test, $ lynx -dump -listonly -nonumbers \ http://news.gmane.org/group/gmane.comp.lang.perl.perl5.porters/last=/force_load=t |\ perl -nwle 'if(m <at> /\d+$ <at> ){push <at> j, $_}END{print for sort <at> j}' Notice all this gaps? Have a look at the missing articles. Some of them are crossposts, some of them not. The problem is Gmane is not broken enough to make users become aware that they are not getting all the news. It looks fine on the surface, but in reality that vital social function announcement that you were waiting for made it Gmane, is stored on disk, but alas, not indexed. And no, it was not marked as spam either (crossposted to gmane.spam.detected). And then some messages, like http://www.nntp.perl.org/group/perl.perl5.porters/2009/06/msg146990.html never make it to Gmane in the first place. What file might the bug be in?
jidanni <at> jidanni.org writes: > Some of them are crossposts, some of them not. Crossposts mess stuff up. Haven't had time to chase down why. -- -- (domestic pets only, the antidote for overdose, milk.) larsi <at> gnus.org * Lars Magne Ingebrigtsen
Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes: >> Some of them are crossposts, some of them not. > Crossposts mess stuff up. Haven't had time to chase down why. I think even the slightest CC messes things up. Maybe 25% of articles don't get indexed... or even into NNTP. What's the URL of the source file to blame so we can see what can be fixed? Thanks.
On 2009-06-07, jidanni <at> jidanni.org <jidanni <at> jidanni.org> wrote:
> Lars Magne Ingebrigtsen <larsi <at> gnus.org> writes:
>>> Some of them are crossposts, some of them not.
>> Crossposts mess stuff up. Haven't had time to chase down why.
> I think even the slightest CC messes things up. Maybe 25% of articles
> don't get indexed... or even into NNTP. What's the URL of the source
> file to blame so we can see what can be fixed? Thanks.
I think that if we knew which source file was to blame, this issue would have
been resolved long ago.
Cheers,
Olly
On 2009-06-09 20:48 +0200, jidanni <at> jidanni.org wrote: > Don't encrypt gmane.emacs.gnus.user addresses please. It's a mirror of > Usenet group gnu.emacs.gnus, so there's no point. The addresses on gmane.emacs.gnus.user are not encrypted, unless a) a message is sent to multiple lists, and at least one of them has encryption turned on; or b) the sender requests encryption with an "X-Archive: encrypt" header. See http://gmane.org/tmda.php. Sven
Google is indexing your index pages instead of your articles. > http://www.google.com/search?q=emacs23+"Enabling+Flyspell+mode+gave+an+error"&ie=utf-8&oe=utf-8 > > 2. Gmane -- Gmane Loom: gmane.emacs.help$ > > Enabling Flyspell mode gave an error. 5 Nov 18:29, jeep. Enabling Flyspell mode gave an error .... What is the best > way to get emacs23? ... > news.gmane.org/group/gmane.emacs.help/last=0/force_load=very/?page=20 &action=--Action-- - Similar pages By the time the user clicks, the item is already gone from the index. So you need to use NOINDEX HTML meta tags or something. That way the articles would get higher pagerank.
On 2009-05-31, Lars Magne Ingebrigtsen <larsi <at> gnus.org> wrote:
> Szabolcs Szakacsits <szaka <at> ntfs-3g.org> writes:
>
>> Apparently Gmane search doesn't index emails over the last month.
>
> Yeah; we're moving the search engine over to a newer and spiffier
> machine, so it's not updating currently.
I've been having problems with libgmime segfaulting while trying to get the
new machine set up, and not had much luck tracking them down yet.
But it's been far too long to be without search index updates, so I've
cleared some more free space on the old machine by juggling files between
partitions, and set it to update. There should be an update with messages
up to June 3rd live within 12 hours, and hopefully it'll be fully caught
up in a day or so (unless it runs out of diskspace again...)
Cheers,
Olly
RSS Feed28 | |
|---|---|
61 | |
38 | |
21 | |
29 | |
51 | |
50 | |
103 | |
52 | |
107 | |
112 | |
72 | |
28 | |
68 | |
60 | |
17 | |
99 | |
85 | |
73 | |
22 | |
57 | |
11 | |
49 | |
33 | |
48 | |
46 | |
50 | |
67 | |
57 | |
52 | |
117 | |
138 | |
97 | |
284 | |
49 | |
72 | |
19 | |
34 | |
77 | |
45 | |
233 | |
80 | |
46 | |
16 | |
49 | |
130 | |
57 | |
34 | |
33 | |
28 | |
35 | |
39 | |
36 | |
59 | |
57 | |
26 | |
62 | |
19 | |
47 | |
64 | |
52 | |
68 | |
44 | |
62 | |
78 | |
43 | |
55 | |
76 | |
82 | |
33 | |
94 | |
64 | |
58 | |
54 | |
110 | |
75 | |
133 | |
211 | |
158 | |
111 | |
83 | |
97 | |
154 | |
58 | |
77 | |
75 | |
126 | |
109 | |
97 | |
210 | |
69 | |
116 | |
214 | |
162 | |
56 | |
112 | |
131 | |
183 | |
169 | |
187 | |
211 | |
248 | |
304 | |
193 | |
193 | |
118 | |
91 | |
63 | |
142 | |
106 | |
183 | |
303 | |
209 | |
294 | |
519 | |
278 | |
198 | |
246 | |
81 | |
146 | |
104 | |
225 | |
245 | |
127 | |
133 | |
202 | |
230 | |
218 | |
307 | |
55 | |
266 | |
222 | |
205 | |
338 | |
191 | |
42 |
