On Wed, Apr 22, 2020 at 3:26 AM Susi Lehtola
wrote:
>
> This raises the question: shouldn't there be some sort of automatic tool
> for
> making soname bump announcements? It seems to me that this is a thing where
> computers easily beat humans: query for dependent packages, and shoot their
> main
On Wed, Apr 22, 2020 at 6:45 AM Susi Lehtola
wrote:
>
> On 4/22/20 11:54 AM, Miro Hrončok wrote:
> > On 22. 04. 20 10:25, Susi Lehtola wrote:
> >> first, I'm sorry for a partial screw-up of the libxc soname bump
> >> announcement.
> >> It appears I am not alone: there are a few soname bumps each
On 4/22/20 11:54 AM, Miro Hrončok wrote:
> On 22. 04. 20 10:25, Susi Lehtola wrote:
>> first, I'm sorry for a partial screw-up of the libxc soname bump
>> announcement.
>> It appears I am not alone: there are a few soname bumps each month, many of
>> them
>> still unannounced.
>
> I'd guess the
On Wed, Apr 22, 2020 at 10:55 AM Miro Hrončok wrote:
>
> On 22. 04. 20 10:25, Susi Lehtola wrote:
> > Hello,
> >
> >
> > first, I'm sorry for a partial screw-up of the libxc soname bump
> > announcement.
> > It appears I am not alone: there are a few soname bumps each month, many of
> > them
> >
On 22. 04. 20 10:25, Susi Lehtola wrote:
Hello,
first, I'm sorry for a partial screw-up of the libxc soname bump announcement.
It appears I am not alone: there are a few soname bumps each month, many of them
still unannounced.
I'd guess the biggest problem is that a lot of packages have sonam
