Ubuntu 22.04 LTS is not supported

Bug #1973205 reported by Balazs Kiss
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LiveWallpaper
New
Undecided
Unassigned

Bug Description

The package is not supported on Ubuntu 22.04.

$ sudo add-apt-repository ppa:fyrmir/livewallpaper-daily
Repository: 'deb https://ppa.launchpadcontent.net/fyrmir/livewallpaper-daily/ubuntu/ jammy main'
Description:
Daily builds of LiveWallpaper. If you are looking for stable releases, please use https://launchpad.net/~fyrmir/+archive/livewallpaper-stable
More info: https://launchpad.net/~fyrmir/+archive/ubuntu/livewallpaper-daily
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
Found existing deb entry in /etc/apt/sources.list.d/fyrmir-ubuntu-livewallpaper-daily-jammy.list
Adding deb entry to /etc/apt/sources.list.d/fyrmir-ubuntu-livewallpaper-daily-jammy.list
Found existing deb-src entry in /etc/apt/sources.list.d/fyrmir-ubuntu-livewallpaper-daily-jammy.list
Adding disabled deb-src entry to /etc/apt/sources.list.d/fyrmir-ubuntu-livewallpaper-daily-jammy.list
Adding key to /etc/apt/trusted.gpg.d/fyrmir-ubuntu-livewallpaper-daily.gpg with fingerprint B6A9F002AFE38AFC54C2CEDC358EC4CAB2D77075
Hit:1 http://hu.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://hu.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://hu.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 https://swupdate.openvpn.net/community/openvpn3/repos jammy InRelease
Hit:5 https://dl.google.com/linux/chrome/deb stable InRelease
Ign:6 https://ppa.launchpadcontent.net/fyrmir/livewallpaper-daily/ubuntu jammy InRelease
Get:7 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Err:8 https://ppa.launchpadcontent.net/fyrmir/livewallpaper-daily/ubuntu jammy Release
  404 Not Found [IP: 2001:67c:1560:8008::19 443]
Hit:9 https://deb.nodesource.com/node_18.x jammy InRelease
Reading package lists... Done
E: The repository 'https://ppa.launchpadcontent.net/fyrmir/livewallpaper-daily/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.