Re: 2.9.4 fails on ximian-connector-2.1.2

[guenther <guenther rudersport de>]

> >> No big deal for me since I don't connect to an exchange server.... but
> >> what is the problem?
> >
> > It's the wrong version, known issue and already fixed in arch.
> >
> > You need to (manually) update the Makefile and checksums files like this
> > (one line per file):
> >
> > $ cat checksums
> > accdfe088d0f9e1f7858608e6a627438  download/ximian-connector-2.1.3.tar.bz2
> > $ grep ^GARVERSION Makefile
> > GARVERSION = 2.1.3
> >
> > After that, run 'make clean; make install' in desktop/ximian-connector.
> 
> Actually, guenther you don't need to update the checksum file manually.
> It's probably easier to just run 'make makesum' in
> desktop/ximian-connector. :)

Sure, I do know this. :)


But whenever I'm telling folks to upgrade, I want to mention the correct
md5sum as well...

I mean, GARNOME comes with the md5sums for a reason, no? The reason
cannot be "check if the download is correct", simply 'cause you will see
this immediately after this when trying to extract the archive. The only
reason can be security -- or at least a little bit of it. "Is the
downloaded file the correct one? The officially released one, not
spoofed?"

IMHO security is the reason for the md5sums being there at all. And I
want to keep up that security, if possible -- even more, when I'm going
to post updates officially.

Yes, this does not mean I do this always, when building locally.
Personally I do use 'make makesum' often, and I'm aware of potential
issues. I may be paranoid, but I'm lazy as well. :)

...guenther


-- 
char *t="\10pse\0r\0dtu\0  ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}