Bug#1109891: hyperv-daemons no longer available for bullseye/arm64
Control: tag -1 pending On Mon, 2025-07-28 at 10:24 -0400, Noah Meyerhans wrote: [...] > Looking through the changelogs and the content of the rest of our cloud > images, I think the hyperv-daemons from 5.10 should be OK. We're > installing that version on all our amd64 cloud images (including the > -backports image), so the only potential issues I can see are: > > * There's some arch-specific issue impacing hyperv-daemons for arm64, > * There's the possibility for confusion among the current users of our > arm64 bullseye-backports images, as they've previously contaned the > 6.1 version of that package. > > I think I'm OK with the risk associated with those issues, and am in > favor of doing the most basic work to enable the 5.10 hyperv-daemons > binary package. I've cherry-picked the necessary changes, so hyperv-daemons/arm64 will be included in the next upload of src:linux. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#1109891: hyperv-daemons no longer available for bullseye/arm64
Control: tags -1 - moreinfo On Sun, Jul 27, 2025 at 04:42:42PM +0200, Ben Hutchings wrote: > > With the retirement of bullseye-backports, hyperv-daemons for arm64 is > no > > longer available in any bullseye repository. This breaks the cloud > team's > > arm64 image builds for Hyper-V environments. > > > > Please enable the hyperv-daemons binary package in the linux-6.1 > builds for > > bullseye-security. > > hyperv-daemons is already built (for x86) by src:linux and I don't think > 2 source packages can build the same binary package for different > architectures. > > There have been no functional changes in hyperv-daemons between 5.10 and > 6.1, so I can build it for arm64 from src:linux with no loss of > functionality. However the version number would be lower than before. > > Would that meet the requirements for cloud images? Or do I need to > fudge the binary version number? Looking through the changelogs and the content of the rest of our cloud images, I think the hyperv-daemons from 5.10 should be OK. We're installing that version on all our amd64 cloud images (including the -backports image), so the only potential issues I can see are: * There's some arch-specific issue impacing hyperv-daemons for arm64, * There's the possibility for confusion among the current users of our arm64 bullseye-backports images, as they've previously contaned the 6.1 version of that package. I think I'm OK with the risk associated with those issues, and am in favor of doing the most basic work to enable the 5.10 hyperv-daemons binary package. Thanks noah
Bug#1109891: hyperv-daemons no longer available for bullseye/arm64
Control: tag -1 moreinfo On Fri, 25 Jul 2025 11:40:14 -0400 Noah Meyerhans wrote: > Source: hyperv-daemons > Severity: important > X-Debbugs-Cc: [email protected], [email protected] > User: [email protected] > Usertags: arm64 > > With the retirement of bullseye-backports, hyperv-daemons for arm64 is no > longer available in any bullseye repository. This breaks the cloud team's > arm64 image builds for Hyper-V environments. > > Please enable the hyperv-daemons binary package in the linux-6.1 builds for > bullseye-security. hyperv-daemons is already built (for x86) by src:linux and I don't think 2 source packages can build the same binary package for different architectures. There have been no functional changes in hyperv-daemons between 5.10 and 6.1, so I can build it for arm64 from src:linux with no loss of functionality. However the version number would be lower than before. Would that meet the requirements for cloud images? Or do I need to fudge the binary version number? Ben. -- Ben Hutchings The Peter principle: In a hierarchy, every employee tends to rise to their level of incompetence. signature.asc Description: This is a digitally signed message part
Bug#1109891: hyperv-daemons no longer available for bullseye/arm64
Control: reassign -1 src:linux Reassigning to src:linux, as the BTS sent the original mail to [email protected]. On Fri, Jul 25, 2025 at 11:40:14AM -0400, Noah Meyerhans wrote: > Source: hyperv-daemons > Severity: important > X-Debbugs-Cc: [email protected], [email protected] > User: [email protected] > Usertags: arm64 > > With the retirement of bullseye-backports, hyperv-daemons for arm64 is no > longer available in any bullseye repository. This breaks the cloud team's > arm64 image builds for Hyper-V environments. > > Please enable the hyperv-daemons binary package in the linux-6.1 builds for > bullseye-security. > > noah
Bug#1109891: hyperv-daemons no longer available for bullseye/arm64
Source: hyperv-daemons Severity: important X-Debbugs-Cc: [email protected], [email protected] User: [email protected] Usertags: arm64 With the retirement of bullseye-backports, hyperv-daemons for arm64 is no longer available in any bullseye repository. This breaks the cloud team's arm64 image builds for Hyper-V environments. Please enable the hyperv-daemons binary package in the linux-6.1 builds for bullseye-security. noah
