2012/3/19 Jürgen Schmidt <jogischm...@googlemail.com>: >> FWIW, there seemed to be extraneous .txt extensions attached to aoo.KEYS >> and some of the checksum files, > > I am not sure if I understand you here, can you explain it?
Apologies, I have tracked down the root of the problem and it was an error on my part when downloading some files via Safari. I have now doublechecked and all of the files within this directory have the correct names: http://people.apache.org/~jsc/developer-snapshots/src_releases/ >> and the format of the checksum files will not work with "md5sum --check" >> and "shasum --check" -- but that's all nitpicking. > > I used gpg on my Mac to generate md5 and sha checksums as found in the docu > (). I have to check it but is there an incompatibility already known? > > Using "md5" on my Mac gave me the same checksum ... and so long as the sums are the same, that addresses all important concerns. :) FWIW, some people like to use the "md5sum" and "shasum" command line apps (which seem to be distributed with certain Linux distros) when validating checksums. Output from GPG isn't compatible with those apps, so those users must fall back to eyeball comparision. It's a nice convenience to those users to put sums in a format that their automatic validation can chew -- but speaking from experience it's also a bit of a PITA to do it on a Mac[1]. >> The README starts with a UTF-8-encoded BOM. Just FYI. >> > do you see a problem with that? It was visible in my editor (MacVim), and it's unusual. Prior to reporting it to you, I checked out Wikipedia: http://en.wikipedia.org/wiki/UTF-8#Byte_order_mark The Unicode standard recommends against the BOM for UTF-8. However, that passage in Wikipedia turns out to be incorrect. :) Here's the actual text in the Unicode standard (version 6.0 section 2.6), which does not seem to have changed substantially going back to at least Unicode 4.0: http://www.unicode.org/versions/Unicode6.0.0/ch02.pdf Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature. So, since the AOO README is not a source code file, I can only say it was unusual. I still favor stripping it because doing so won't hurt anything, and its presence may confuse machine readers that are not prepared for it -- but it's not a big deal, I'm just trying to help out with some light QC. >> I don't see the Incubation disclaimer in either a dedicated DISCLAIMER file >> or the README. Also, the word "incubating" is not in the archive filename. > > I will add it to the README. > > Ok we have to add "incubating" to the archive file names. Sounds good. Those have traditionally been blocking concerns. Cheers, Marvin Humphrey [1] Compatible checksum files can be hand-rolled using Perl and the Digest module: <http://s.apache.org/UCV>. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
