Revert "d/control: Add breaks on compressed 5.16 kernels"

This would otherwise force 5.16 older than 5.16.0-1pureos2 off the system as it can't be upraded due to it being removed from the archive when 5.17 enters.

@martin.kepplinger this is the revert I mentioned. If we do

diff --git a/debian/control.in b/debian/control.in
index 582f917f2d2a..3d5abd43e6d2 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -24,7 +24,7 @@ Vcs-Browser: https://source.puri.sm/Librem5/linux
 Package: linux-image-%KREL%
 Architecture: arm64
 Depends:
- flash-kernel,
+ flash-kernel (>= 3.102.0pureos6),
  initramfs-tools,
  kmod,
  linux-base,

in the kernel package we should be on the save side (we'd upload flash-kernel past 5.17 to give them a chance to migrate together).

This reverts commit 57c06f68.

thanks! So that Depends flash-kernel (>= 3.102.0pureos6) for the kernel should be in the first 5.17 kernel we release as linux-librem5? you can create a MR against next/byzantium then, or I'll create one later.

mentioned in commit martin.kepplinger/linux-next@27375135

mentioned in merge request linux!586 (merged)

mentioned in commit martin.kepplinger/linux-next@7cf5f726

@guido.gunther if you can Ack linux!586 (merged) I'll tag the first 5.17 kernel as linux-librem5.

@guido.gunther is away for a bit longer but I think I can merge and tag the kernel release and this one myself, as he prepared the release in this MR.

mentioned in commit b2bd6721

merged

5.17 kernel is tagged: https://source.puri.sm/Librem5/linux/-/tags/pureos%2F5.17.3pureos1

@martin.kepplinger anything left for me to do here?

no. it's tagged and migrated already.

mentioned in commit sebastian.krzyszkowiak/linux-next@8bb6a2f3