I seem to have the same Problem with:
name -a
Linux Ben-PC 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 
16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux


apt-get install fails for linux-generic and linux-image with "no installation 
candidate" errors.


Tried installing mainline kernel via Mainline (6.11.0) but ran into dependency 
issues (libc6, libelf1t64, libssl3t64).
Currently stuck on kernel 6.2.0-26

Repositories seem okay:
ben@Ben-PC:~$ grep ^[^#] /etc/apt/sources.list /etc/apt/sources.list.d/*

/etc/apt/sources.list:deb http://de.archive.ubuntu.com/ubuntu/ jammy
main universe restricted multiverse

/etc/apt/sources.list.d/amdgpu-proprietary.list:deb
https://repo.radeon.com/amdgpu/6.2/ubuntu jammy proprietary

/etc/apt/sources.list.d/amdgpu-proprietary.list.save:deb
https://repo.radeon.com/amdgpu/6.2/ubuntu jammy proprietary

/etc/apt/sources.list.d/amdgpu.list:deb
https://repo.radeon.com/amdgpu/6.2/ubuntu jammy main

/etc/apt/sources.list.d/amdgpu.list.dpkg-old:deb
https://repo.radeon.com/amdgpu/6.2/ubuntu jammy main #Orginal
https://repo.radeon.com/amdgpu/6.1.1/ubuntu

/etc/apt/sources.list.d/amdgpu.list.save:deb
https://repo.radeon.com/amdgpu/6.2/ubuntu jammy main

/etc/apt/sources.list.d/brostrend.list:deb https://linux.brostrend.com
stable main previous

/etc/apt/sources.list.d/brostrend.list.save:deb
https://linux.brostrend.com stable main previous

/etc/apt/sources.list.d/cappelikan-ubuntu-ppa-jammy.list:deb
https://ppa.launchpadcontent.net/cappelikan/ppa/ubuntu/ jammy main

/etc/apt/sources.list.d/damentz-ubuntu-liquorix-jammy.list:deb
https://ppa.launchpadcontent.net/damentz/liquorix/ubuntu/ jammy main

/etc/apt/sources.list.d/damentz-ubuntu-liquorix-jammy.list.save:deb
https://ppa.launchpadcontent.net/damentz/liquorix/ubuntu/ jammy main

/etc/apt/sources.list.d/danielrichter2007-ubuntu-grub-customizer-
jammy.list:deb

https://ppa.launchpadcontent.net/danielrichter2007/grub-
customizer/ubuntu/ jammy main

/etc/apt/sources.list.d/danielrichter2007-ubuntu-grub-customizer-
jammy.list.save:deb
https://ppa.launchpadcontent.net/danielrichter2007/grub-
customizer/ubuntu/

jammy main

/etc/apt/sources.list.d/ernstp-ubuntu-mesarc-jammy.list:deb
https://ppa.launchpadcontent.net/ernstp/mesarc/ubuntu/ jammy main

/etc/apt/sources.list.d/ernstp-ubuntu-mesarc-jammy.list.save:deb
https://ppa.launchpadcontent.net/ernstp/mesarc/ubuntu/ jammy main

/etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list:deb
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy main

/etc/apt/sources.list.d/mozillateam-ubuntu-ppa-jammy.list.save:deb
https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/ jammy main

/etc/apt/sources.list.d/rocm.list:deb [arch=amd64]
https://repo.radeon.com/rocm/apt/6.2 jammy main

/etc/apt/sources.list.d/rocm.list.dpkg-old:deb
https://repo.radeon.com/rocm/apt/6.2 jammy main #Original
https://repo.radeon.com/rocm/apt/6.1.1

/etc/apt/sources.list.d/rocm.list.save:deb [arch=amd64]
https://repo.radeon.com/rocm/apt/6.2 jammy main

/etc/apt/sources.list.d/teamviewer.list:deb [signed-
by=/usr/share/keyrings/teamviewer-keyring.gpg]
https://linux.teamviewer.com/deb stable main

/etc/apt/sources.list.d/teamviewer.list:deb [signed-
by=/usr/share/keyrings/teamviewer-keyring.gpg]
https://linux.teamviewer.com/deb preview main

/etc/apt/sources.list.d/teamviewer.list.dpkg-old:deb
http://linux.teamviewer.com/deb stable main

/etc/apt/sources.list.d/teamviewer.list.save:deb [signed-
by=/usr/share/keyrings/teamviewer-keyring.gpg]
https://linux.teamviewer.com/deb stable main

/etc/apt/sources.list.d/teamviewer.list.save:deb [signed-
by=/usr/share/keyrings/teamviewer-keyring.gpg]
https://linux.teamviewer.com/deb preview main

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2025192

Title:
  broken installation while mirror syncing new kernel packages

Status in linux-meta package in Ubuntu:
  Confirmed

Bug description:
  
  A new kernel package for jammy was released 3 hours ago. It is probably being 
synced to mirrors right now.

  It can be seen at https://launchpad.net/ubuntu/+source/linux-meta:

  5.15.0.76.74     updates (main)     3 hours ago

  A little before that, I was deploying 10 Jammy machines in maas,
  without any problem. After that, I started having all 10 machines fail
  deployment. The reason is that curtin will fail package updates
  (complete log attached). This is the important part:

  
==========================================8<---------------------------------------------------
  Running command ['unshare', '--fork', '--pid', '--', 'chroot', 
'/tmp/tmp_24ek5y0/target', 'eatmydata', 'apt-get', '--quiet', '--assume-yes', 
'--option=Dpkg::options::=--force-unsafe-io', 
'--option=Dpkg::Options::=--force-confold', 'install', 'linux-generic'] with 
allowed return codes [0] (capture=False)
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   linux-headers-generic : Depends: linux-headers-5.15.0-76-generic but it is 
not installable
   linux-image-generic : Depends: linux-image-5.15.0-76-generic but it is not 
going to be installed
                         Depends: linux-modules-extra-5.15.0-76-generic but it 
is not installable
                         Recommends: thermald but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.
  
==========================================8<---------------------------------------------------

  The repository being used is "http://archive.ubuntu.com/ubuntu
  jammy/main"

  It may be the case that there is still a partial mirror there, but it
  should not break and instead just use the latest available version
  while the new one is not completely avalable.

  I'm not sure this is only valid for linux kernel packages (maybe this
  is a general problem with any package) but I'm opening to linux-meta
  since it happened with linux in this case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2025192/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to