> On Oct 21, 2015, at 1:53 PM, John Ross <jwross.apa...@gmail.com> wrote: > > Sorry, I'm still not sure I understand. Are you saying our current > verification script is no longer applicable when using "the latest > releases of the various maven plugins"? Or is it still useful but we > should simply ignore the MD5 and SHA1 failures? What, if anything, > replaces the original point of the MD5 and SHA1 checks?
No… there should be checks of MD5 and SHA1 files for everything except ASC files. Those are no longer applicable. .jar and .pom files should have associated MD5 and SHA1 files (and .asc files), but .asc files will no longer have md5 or sha1 files. Thus, the verification script would need to be updated to not have it check the MD5/SHA1 of .asc files, but maintain the check for everything else. Dan > > On Wed, Oct 21, 2015 at 12:46 PM, Daniel Kulp <dk...@apache.org> wrote: >> >>> On Oct 21, 2015, at 1:36 PM, John Ross <jwross.apa...@gmail.com> wrote: >>> >>> What would be the appropriate way to verify the integrity of the files >>> without them? >> >> The asc files are there to verify the integrity of the jar files and pom >> file. They also have built in integrity things as part of the gpg >> signature. There isn’t a point in having md5’s for them. That would be >> like saying we need an MD5 for the sha1 files. >> >> Dan >> >> >> >>> >>> On Wed, Oct 21, 2015 at 11:24 AM, Daniel Kulp <dk...@apache.org> wrote: >>>> >>>>> On Oct 21, 2015, at 12:17 PM, John Ross <jwross.apa...@gmail.com> wrote: >>>>> >>>>> I'm receiving the following RAT failures when running the verify >>>>> script against 1045. The last simply means that Namespaces.java needs >>>>> a license header. I'm more concerned about the bad MD5s and SHA1s. Am >>>>> I doing something wrong on my end? I have the latest KEYS file >>>>> imported. >>>> >>>> With the latest releases of the various maven plugins, the “asc” files >>>> aren’t deployed with MD5 and SHA1 files. Your script is checking for >>>> them but not finding them. >>>> >>>> Dan >>>> >>>> >>>> >>>>> >>>>> *FAILURE - BAD MD5 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2.pom.asc >>>>> ***** (compared add4b1422a75fb0f9a9b7a5d2d519742 and ) >>>>> *FAILURE - BAD MD5 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2-javadoc.jar.asc >>>>> ***** (compared abd8d09533f9ba7697cd34d76466f3b7 and ) >>>>> *FAILURE - BAD MD5 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2.jar.asc >>>>> ***** (compared c70c2dd47a3db618772075d012b9b28f and ) >>>>> *FAILURE - BAD MD5 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2-sources.jar.asc >>>>> ***** (compared 0bfe742b7dfa7deb8e94df1695d7c70b and ) >>>>> *FAILURE - BAD MD5 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2-source-release.zip.asc >>>>> ***** (compared ae62356bdeca0da94e6a617de88d8ac3 and >>>>> ) >>>>> *FAILURE - BAD SHA1 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2.pom.asc >>>>> ***** (compared 3e4ea60c489c0e1ca49df6ef9fc2970e4a3eef17 and ) >>>>> *FAILURE - BAD SHA1 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2-javadoc.jar.asc >>>>> ***** (compared 9c714c7e028045b267b2911611827b3bf0ddc782 an >>>>> d ) >>>>> *FAILURE - BAD SHA1 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2.jar.asc >>>>> ***** (compared ca3a343aabe2d823f87d4af74864db26364cf9fc and ) >>>>> *FAILURE - BAD SHA1 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2-sources.jar.asc >>>>> ***** (compared e52950a2088bd2b101d316eeea702bb50b154fd9 an >>>>> d ) >>>>> *FAILURE - BAD SHA1 for >>>>> mytempdirectory/1045/org/apache/aries/blueprint/blueprint-parser/1.3.2/blueprint-parser-1.3.2-source-release.zip.asc >>>>> ***** (compared ae37301b71706f19b00ec4bdc5f1a86749ad >>>>> a3ec and ) >>>>> RAT FAILURE:????? src/main/java/org/apache/aries/blueprint/Namespaces.java >>>>> >>>>> On Wed, Oct 21, 2015 at 9:21 AM, Christian Schneider >>>>> <ch...@die-schneider.net> wrote: >>>>>> This release vote is mainly because of the issue ARIES-1430 which will >>>>>> always shutdown JPA bundles >>>>>> after 5 minutes. I also needed to release parser 1.3.2 as it was used by >>>>>> blueprint core. >>>>>> >>>>>> Release Notes - Aries - Version blueprint-parser-1.3.2 >>>>>> >>>>>> ** Improvement >>>>>> * [ARIES-1322] - Introduce Namespaces annotation >>>>>> >>>>>> https://issues.apache.org/jira/browse/ARIES/fixforversion/12332956 >>>>>> >>>>>> Staging repo: >>>>>> https://repository.apache.org/content/repositories/orgapachearies-1045 >>>>>> >>>>>> >>>>>> >>>>>> Release Notes - Aries - Version blueprint-core-1.4.5 >>>>>> >>>>>> ** Bug >>>>>> * [ARIES-1353] - NullpointerException when trying to log an exception >>>>>> * [ARIES-1430] - Blueprint bundle shut down after timeout even if all >>>>>> dependencies are present at that time >>>>>> >>>>>> https://issues.apache.org/jira/browse/ARIES/fixforversion/12333050 >>>>>> >>>>>> Staging repo: >>>>>> https://repository.apache.org/content/repositories/orgapachearies-1046/ >>>>>> >>>>>> Please review and vote: >>>>>> [ ] +1 Release the above artifacts >>>>>> [ ] -1 Do not >>>>>> >>>>>> Here is my +1 >>>>>> >>>>>> Cheers, >>>>>> Christian >>>>>> >>>>>> -- >>>>>> Christian Schneider >>>>>> http://www.liquid-reality.de >>>>>> >>>>>> Open Source Architect >>>>>> http://www.talend.com >>>>>> >>>> >>>> -- >>>> Daniel Kulp >>>> dk...@apache.org - http://dankulp.com/blog >>>> Talend Community Coder - http://coders.talend.com >>>> >> >> -- >> Daniel Kulp >> dk...@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
