> I really don't understand this argument. What's stopping you from simply
> incrementing the minor? After all, if ZFS only supports up to 6.19, and you
> specify <6.20, then it doesn't matter if 6.20 exists, it's still less than
> 7.0. You're literally already using it in `Recommends` ("linux-libc-dev (<<
> 6.20~)"), I don't understand why you couldn't also use it in `Depends`.


#900656 ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900656 ),
open since 2018, suggests:


> The package currently has a "Recommends" set on linux-libc-dev (of 
> appropriate version).
> 
> We could make zfs-dkms "Conflict" with linux-image of incompatible versions.

and:

> We can add dependency on linux-libc-dev (which always has the same version as 
> kernel).
> This prevents:
>  
> 1. kernel upgrade to versions that zfs does not **explicitly** say it 
> supports in META,
>   even it **might** actually build and work.
> 2. any user-compiled kernels. Users can create a fake package if needed.



If neither of these approaches is workable, please update #900656
with the reasons.

If one of them (or the approach above) *is* workable, please implement.



-jonathan

Reply via email to