Re: [smartmontools-support] smartmontools 5.42 released

[Christian Franke <Christian.Franke@t-...>]

Alex Samorukov wrote:
> On 10/21/2011 06:25 PM, Christian Franke wrote:
>> Christian Franke wrote:
>>> Dear smartmontools users,
>>>
>>> release 5.42 of smartmontools is now available [1].
>>>
>> I uploaded a new tarball with autoconf/automake files (aclocal.m4,
>> configure, Makefile.in) regenerated.
>>
>> MD5 old: ce5690a1ba58efbe6db1bb784e4e20c3
>> MD5 new:4460bf9a79a1252ff5c00ba52cf76b2a
>>
>> Unfortunately the old tarball was built on a system without pkg-config
>> installed. The PKG_PROG_PKG_CONFIG macro was not expanded in configure.
>>
>> As a consequence, the detection of systemd presence for 'make install'
>> target was broken, sorry. The build of the executables were not 
>> affected.
> Hi Christian,
>
> May i ask in the feature not to do this way? I updated FreeBSD port 
> after release and then i was on the road when checksum  was changed. 
> So i got a lot of reports about broken port. Also it making a big 
> problem for 3-rd party dist. files mirrors, often they will never 
> recheck the file when it already mirrored. Currently port checksum was 
> fixed but in the feature its better to release 5.42.1 or 5.43 in case 
> of such problems.
>
>

Sorry!

For the future, a release with a new number will be generated even if 
the bug is only in the files not in SVN.

Cheers,
Christian

Re: [smartmontools-support] [Smartmontools-announce] smartmontools 5.42 released

[Alex Samorukov <ml@os...>]

On 10/21/2011 06:25 PM, Christian Franke wrote:
> Christian Franke wrote:
>> Dear smartmontools users,
>>
>> release 5.42 of smartmontools is now available [1].
>>
> I uploaded a new tarball with autoconf/automake files (aclocal.m4,
> configure, Makefile.in) regenerated.
>
> MD5 old: ce5690a1ba58efbe6db1bb784e4e20c3
> MD5 new:4460bf9a79a1252ff5c00ba52cf76b2a
>
> Unfortunately the old tarball was built on a system without pkg-config
> installed. The PKG_PROG_PKG_CONFIG macro was not expanded in configure.
>
> As a consequence, the detection of systemd presence for 'make install'
> target was broken, sorry. The build of the executables were not affected.
Hi Christian,

May i ask in the feature not to do this way? I updated FreeBSD port 
after release and then i was on the road when checksum  was changed. So 
i got a lot of reports about broken port. Also it making a big problem 
for 3-rd party dist. files mirrors, often they will never recheck the 
file when it already mirrored. Currently port checksum was fixed but in 
the feature its better to release 5.42.1 or 5.43 in case of such problems.