On Tue, 2023-11-07 at 15:20 +0100, Miro Hrončok wrote:
> On 07. 11. 23 12:17, Sandro Mani wrote:
> > Hi
> >
> > Due to an unfortunate oversight of an incorrect branch merge a couple of
> > months
> > ago, a recently backported security fix caused an unwanted gdal soname bump
> > in
> > F37,
On Tue, 2023-11-07 at 15:20 +0100, Miro Hrončok wrote:
> On 07. 11. 23 12:17, Sandro Mani wrote:
> > Hi
> >
> > Due to an unfortunate oversight of an incorrect branch merge a couple of
> > months
> > ago, a recently backported security fix caused an unwanted gdal soname bump
> > in
> > F37,
On Tue, Nov 07, 2023 at 04:20:52PM +0100, Kevin Kofler via devel wrote:
> Miro Hrončok wrote:
> > this is not the first time I saw a bodhi update that breaks dozens of
> > dependencies, goes unnoticed for a week and is automatically pushed
> > stable, only to discover many packages fail to
Miro Hrončok wrote:
> this is not the first time I saw a bodhi update that breaks dozens of
> dependencies, goes unnoticed for a week and is automatically pushed
> stable, only to discover many packages fail to install.
The most important measure would be to abolish automatic pushes. This update
On 07. 11. 23 12:17, Sandro Mani wrote:
Hi
Due to an unfortunate oversight of an incorrect branch merge a couple of months
ago, a recently backported security fix caused an unwanted gdal soname bump in
F37, due to an update from the 3.5.x series to the 3.6.x series.
I'm preparing a
On 07. 11. 23 12:17, Sandro Mani wrote:
Hi
Due to an unfortunate oversight of an incorrect branch merge a couple of months
ago, a recently backported security fix caused an unwanted gdal soname bump in
F37, due to an update from the 3.5.x series to the 3.6.x series.
I'm preparing a
