On Mon, Jun 26, 2023 at 12:07:35PM +0100, Daniel P. Berrangé wrote:
> On Wed, Jun 21, 2023 at 10:58:28PM +0100, Richard W.M. Jones wrote:
> > It's possible to create this situation:
> >
> > fuse3-libs-3.13.1-1.fc38.x86_64
> > fuse3-devel-3.13.1-1.fc38.x86_64
> > fuse3-3.14.1-1.fc39.x86_64
> >
>
On Wed, Jun 21, 2023 at 10:58:28PM +0100, Richard W.M. Jones wrote:
> It's possible to create this situation:
>
> fuse3-libs-3.13.1-1.fc38.x86_64
> fuse3-devel-3.13.1-1.fc38.x86_64
> fuse3-3.14.1-1.fc39.x86_64
>
> fuse3-devel correctly requires the exact version of fuse3-libs.
> However there
On Wed, Jun 21, 2023 at 10:58:28PM +0100, Richard W.M. Jones wrote:
> It's possible to create this situation:
>
> fuse3-libs-3.13.1-1.fc38.x86_64
> fuse3-devel-3.13.1-1.fc38.x86_64
> fuse3-3.14.1-1.fc39.x86_64
>
> fuse3-devel correctly requires the exact version of fuse3-libs.
> However there
It's possible to create this situation:
fuse3-libs-3.13.1-1.fc38.x86_64
fuse3-devel-3.13.1-1.fc38.x86_64
fuse3-3.14.1-1.fc39.x86_64
fuse3-devel correctly requires the exact version of fuse3-libs.
However there doesn't seem to be any similar requirement connecting
fuse3 & fuse3-libs.
Is this a
