AMule
Solved
Hello,
Configuration: Linux / Firefox 88.0
I can't install aMule. A few months ago, a simple sudo apt-get install aMule was enough, if I remember correctly.
I've tried through Synaptic, via command line, and as many more or less unconventional methods as I can count, nothing works.
The packages are either not found, or unsigned, or the procedure just doesn't work at all.
Hence my question: is aMule software still maintained???
If not, is there a valid eD2k compatible equivalent?
(I really don't like software like bitTorrent)
I don't even dare to ask for a valid procedure for aMule, it feels like a mission impossible (or maybe I should stop using Linux and go back to Windows, I was actually getting along better)
Thanks in advance.
Configuration: Linux / Firefox 88.0
I can't install aMule. A few months ago, a simple sudo apt-get install aMule was enough, if I remember correctly.
I've tried through Synaptic, via command line, and as many more or less unconventional methods as I can count, nothing works.
The packages are either not found, or unsigned, or the procedure just doesn't work at all.
Hence my question: is aMule software still maintained???
If not, is there a valid eD2k compatible equivalent?
(I really don't like software like bitTorrent)
I don't even dare to ask for a valid procedure for aMule, it feels like a mission impossible (or maybe I should stop using Linux and go back to Windows, I was actually getting along better)
Thanks in advance.
8 réponses
Unlucky: it is not in the repositories of Ubuntu 20.04, it was removed between 18.04 and 20.10.
There may be a way to install the package from 20.10, but it requires tinkering.
source: https://packages.ubuntu.com/search?searchon=names&keywords=amule
;-) Flachy Joe ;-)
"Those who never fail have no chance of pushing forward!" Anonymous Graf
There may be a way to install the package from 20.10, but it requires tinkering.
source: https://packages.ubuntu.com/search?searchon=names&keywords=amule
;-) Flachy Joe ;-)
"Those who never fail have no chance of pushing forward!" Anonymous Graf
Hello,
Package
I agree with Flachy Joe, as shown on this page,
Three possible solutions (increasing difficulty):
1) You use another software than
2) You migrate to a more recent version of Ubuntu that offers the
3) You stay on
Let us know which solution works best for you.
Signed Packages
Regarding signed packages: Debian packages (files
To make these warnings disappear, you are supposed to register the repository key (normally indicated by the maintainer of that repository) using the
Archives
Sometimes certain software is redistributed through archives and/or packages.
A package is an "enhanced" archive, which provides desirable functionalities:
Advice 1: when you have the choice, prefer a
Advice 2: make sure to install packages that conform to your Ubuntu release (for now,
Good luck
Package
amule
I agree with Flachy Joe, as shown on this page,
amuledoes not exist for the
focalversion.
Three possible solutions (increasing difficulty):
1) You use another software than
amule, available in your version of Ubuntu, see this page. Most of the mentioned software should be directly available via
apt. (Note that
synapticand
discoverare two graphical interfaces that layer on top of
aptand do not provide access to more or fewer packages).
2) You migrate to a more recent version of Ubuntu that offers the
amulepackage (e.g.
groovyor
hirsute) based on this tutorial. I recommend before starting a migration to back up any important documents on an external drive or USB key, in case you need to reinstall Ubuntu. Note that sooner or later you will need to migrate to a more recent version of Ubuntu when yours is no longer maintained (see the table reported on this page for more details).
3) You stay on
focal, but you also add repositories from a more recent version that provides
amule, and you specify using
/etc/apt/preferencesthat the packages should preferably be taken from
focaland otherwise from
hirsute. This allows you to migrate a minimum of packages.
Let us know which solution works best for you.
Signed Packages
Regarding signed packages: Debian packages (files
.deb) handled by
aptare always signed.
aptmaintains a GnuPG keyring (see command
apt-key) that allows distinguishing trusted signatures from others. When
aptinstalls a package signed by a trusted key, no warning is indicated. Otherwise, you have the warning messages that you report.
To make these warnings disappear, you are supposed to register the repository key (normally indicated by the maintainer of that repository) using the
apt-keycommand. Here it's the codelite repository that is complaining, and a little google search leads us directly to the page indicating how to add these keys.
Archives
.tgz
Sometimes certain software is redistributed through archives and/or packages.
- The main archive formats are:
tar
,.tar.gz
aka.tgz
,.tar.bz2
aka.tbz2
, etc). - The main package formats are
.deb
for Debian-based distributions (Ubuntu, Mint...) and.rpm
for Red Hat-based distributions (Fedora, Mandriva...). So in your case, only.deb
are relevant. There are ways to install.rpm
on Debian-based distributions but this is often unnecessary and therefore a bad approach.
A package is an "enhanced" archive, which provides desirable functionalities:
- Signature: a package is signed, which means that you do not risk installing malicious software (or more precisely, if you try to do so, your package manager will inform you that this package is not signed by a trusted source, according to the keys registered by
apt-key
in your case). - Dependencies: a package indicates what it depends on, which avoids installing multiple copies of the same library (thus saving space). As dependencies specify valid version numbers, this ensures that the libraries used by the software allow it to function correctly.
- Installation scripts: certain commands are triggered upon installation/uninstallation of the package to ensure that everything that needs to be done is done (and in the correct order). This greatly simplifies life.
- Maintenance: since a package is installed by your package manager (
apt
in your case), it can update this software along with the rest of the system (because updating a system simply means updating the installed packages).
Advice 1: when you have the choice, prefer a
.debto an archive (e.g.
.tgz). Finally, make sure to install
.debpackages conforming to your Linux distribution. Typically, installing Ubuntu packages on Debian is a bad idea.
Advice 2: make sure to install packages that conform to your Ubuntu release (for now,
focal) and that do not come from other releases (for example,
hirsute). Indeed, there is a high chance that the dependencies of the
hirsutepackage cannot be satisfied with the packages offered by the
focalrepositories. To bypass such issues, you would either need to fully switch to
hirsute(method 2 in the previous section) or hybridize
focaland
hirsute(method 3 in the previous section).
Good luck
Hello,
First of all, I remind you that peer-to-peer downloading should only involve works that are free of rights. So I will assume that's the case :-)
1) Make sure your package manager is up to date:
... as well as your system
Ensure that the update is done without errors; if not, report the error messages to us.
2) Next, check that
3)a) If you find it, there's nothing left to do but install it:
(report any errors you may encounter).
3)b) Otherwise, it is probably because the repositories configured in
Good luck
First of all, I remind you that peer-to-peer downloading should only involve works that are free of rights. So I will assume that's the case :-)
1) Make sure your package manager is up to date:
sudo apt update
... as well as your system
sudo apt upgrade
Ensure that the update is done without errors; if not, report the error messages to us.
2) Next, check that
aptfinds the package
amule
apt search amule
3)a) If you find it, there's nothing left to do but install it:
sudo apt install amule
(report any errors you may encounter).
3)b) Otherwise, it is probably because the repositories configured in
/etc/apt/sources.listare incomplete. In this case, please report their content to us. You can also check for the existence of that package by searching on your Linux distribution's website. For Ubuntu, you can see on this page the list of distributions for which the package
amuleis available. If the package does not exist for your version of Ubuntu, you may also consider using another client (see this page and this page).
Good luck
As soon as I run
I cannot find any signed packages anywhere. I have tried options to bypass it, without success.
I have downloaded
Six months ago, a simple
My goal is to download shows/documentaries that were aired on TV but that I missed; I hope to stay within the law. And if not, then the problem will be resolved, I have no intention of going against Hadopi.
I also cannot find
sudo apt update, I get:
$ sudo apt update
[sudo] Password for titruffe:
Hit:1 http://fr.archive.ubuntu.com/ubuntu/ focal InRelease
Reading:2 http://fr.archive.ubuntu.com/ubuntu/ focal-updates InRelease [114 kB]
Hit:3 http://ppa.launchpad.net/thierry-f/fork-michael-gruz/ubuntu/ focal InRelease
Reading:4 http://fr.archive.ubuntu.com/ubuntu/ focal-backports InRelease [101 kB]
Hit:5 https://repo.steampowered.com/steam/ stable InRelease
Hit:8 https://repo.skype.com/deb/ stable InRelease
Reading:9 http://security.ubuntu.com/ubuntu/ focal-security InRelease [114 kB]
Reading:6 https://repos.codelite.org/wx3.0.5/ubuntu/ focal InRelease [2,111 B]
Reading:7 https://repos.codelite.org/wx3.0.5/debian/ buster InRelease [2,036 B]
Reading:10 http://security.ubuntu.com/ubuntu/ focal-security/main amd64 DEP-11 Metadata [24.4 kB]
Reading:11 http://security.ubuntu.com/ubuntu/ focal-security/universe amd64 DEP-11 Metadata [58.3 kB]
Reading:12 http://security.ubuntu.com/ubuntu/ focal-security/multiverse amd64 DEP-11 Metadata [2,464 B]
Error:6 https://repos.codelite.org/wx3.0.5/ubuntu/ focal InRelease
The following signatures could not be verified because the public key is not available: NO_PUBKEY 6856E1DB1AC82609
Error:7 https://repos.codelite.org/wx3.0.5/debian/ buster InRelease
The following signatures could not be verified because the public key is not available: NO_PUBKEY 6856E1DB1AC82609
Reading package lists... Done
W: GPG error: https://repos.codelite.org/wx3.0.5/ubuntu/ focal InRelease: The following signatures could not be verified because the public key is not available: NO_PUBKEY 6856E1DB1AC82609
E: The repository https://repos.codelite.org/wx3.0.5/ubuntu/ focal InRelease is not signed.
N: Updates from such a repository cannot be performed securely and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for creating repositories and user configuration details.
W: GPG error: https://repos.codelite.org/wx3.0.5/debian/ buster InRelease: The following signatures could not be verified because the public key is not available: NO_PUBKEY 6856E1DB1AC82609
E: The repository https://repos.codelite.org/wx3.0.5/debian/ buster InRelease is not signed.
N: Updates from such a repository cannot be performed securely and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for creating repositories and user configuration details.
I cannot find any signed packages anywhere. I have tried options to bypass it, without success.
I have downloaded
.deb,
tar.gzfrom different sources, nothing works. This brings me to question why
amulestill exists.
Six months ago, a simple
sudo apt install amulewas enough. I couldn't use it back then because I couldn't find a suitable firewall for that use (problem solved since)
My goal is to download shows/documentaries that were aired on TV but that I missed; I hope to stay within the law. And if not, then the problem will be resolved, I have no intention of going against Hadopi.
I also cannot find
amule(except extensions) in
discoveror
synaptic.
Hello,
I think I have installed the universe repository and now aMule appears in the list.
But when I try to install it:
aMule:
The package
Possible explanations are that the package is listed in the dependencies without ever having been released, it has become obsolete, or it is not available in the repositories defined in the
Here is my
No idea what to do with this file that I won't modify without a valid reason, being incapable of knowing the consequences.
I think I have installed the universe repository and now aMule appears in the list.
But when I try to install it:
aMule:
The package
amuleis not available although it is listed in the database.
Possible explanations are that the package is listed in the dependencies without ever having been released, it has become obsolete, or it is not available in the repositories defined in the
/etc/apt/sources.listfile.
Here is my
/etc/apt/sources.listfile:
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://fr.archive.ubuntu.com/ubuntu/ focal main restricted # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal main restricted ## Major bug fix updates produced after the final release of the ## distribution. deb http://fr.archive.ubuntu.com/ubuntu/ focal-updates main restricted # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal-updates main restricted ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team. Also, please note that software in universe WILL NOT receive any ## review or updates from the Ubuntu security team. deb http://fr.archive.ubuntu.com/ubuntu/ focal universe # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal universe deb http://fr.archive.ubuntu.com/ubuntu/ focal-updates universe # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal-updates universe ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu ## team, and may not be under a free licence. Please satisfy yourself as to ## your rights to use the software. Also, please note that software in ## multiverse WILL NOT receive any review or updates from the Ubuntu ## security team. deb http://fr.archive.ubuntu.com/ubuntu/ focal multiverse # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal multiverse deb http://fr.archive.ubuntu.com/ubuntu/ focal-updates multiverse # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal-updates multiverse ## N.B. software from this repository may not have been tested as ## extensively as that contained in the main release, although it includes ## newer versions of some applications which may provide useful features. ## Also, please note that software in backports WILL NOT receive any review ## or updates from the Ubuntu security team. deb http://fr.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse # deb-src http://fr.archive.ubuntu.com/ubuntu/ focal-backports main restricted universe multiverse ## Uncomment the following two lines to add software from Canonical's ## 'partner' repository. ## This software is not part of Ubuntu, but is offered by Canonical and the ## respective vendors as a service to Ubuntu users. # deb http://archive.canonical.com/ubuntu focal partner # deb-src http://archive.canonical.com/ubuntu focal partner deb http://security.ubuntu.com/ubuntu focal-security main restricted # deb-src http://security.ubuntu.com/ubuntu focal-security main restricted deb http://security.ubuntu.com/ubuntu focal-security universe # deb-src http://security.ubuntu.com/ubuntu focal-security universe deb http://security.ubuntu.com/ubuntu focal-security multiverse # deb-src http://security.ubuntu.com/ubuntu focal-security multiverse # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. # deb https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases) # deb-src https://deb.opera.com/opera-stable/ stable non-free #Opera Browser (final releases) deb http://repos.codelite.org/wx3.0.5/ubuntu/ focal universe deb http://repos.codelite.org/wx3.0.5/debian/ buster libs deb https://repos.codelite.org/wx3.0.5/ubuntu focal InRelease deb http://repos.codelite.org/wx3.0.5/debian buster InRelease # deb-src http://repos.codelite.org/wx3.0.5/ubuntu/ focal universe
No idea what to do with this file that I won't modify without a valid reason, being incapable of knowing the consequences.
I still can't manage this: https://www.numetopia.fr/sauvegarder-votre-systeme-linux-avec-timeshift/
As always, I only get error messages. I don't understand them at all, just as I don't comprehend the 36,000 ways to do it
I get lost in the versions, I can't find any source files, and I've been struggling for almost days, with NO results at all.
I also don't get anything from https://packages.ubuntu.com/groovy/amd64/amule/filelist
I think I've tried at least 12 tutorials, including your advice.
As always, I only get error messages. I don't understand them at all, just as I don't comprehend the 36,000 ways to do it
I get lost in the versions, I can't find any source files, and I've been struggling for almost days, with NO results at all.
I also don't get anything from https://packages.ubuntu.com/groovy/amd64/amule/filelist
I think I've tried at least 12 tutorials, including your advice.
Hello,
I'm referring you to my message #6:
Good luck
I'm referring you to my message #6:
- For the moment, you are using
focal
repositories that do not provideamule
. So it is normal that you cannot installamule
; to resolve the issue, you would need to migrate (at least partially) to another version of Ubuntu that provides this package (e.g.hirsute
) - The error messages you are seeing (GPG key error) can be resolved as indicated in this message.
- You say you have followed several tutorials and our recommendations. Compared to my message #6, which solution among the 3 did you choose? (your
/etc/apt/sources.list
suggests: none of the last two). - Have you considered alternatives to
amule
?
Good luck
I don't really understand this story about repositories.
I tried to install Hirsute and Groovy.
I understand the messages about the keys, but I'm surprised by their frequency.
Does that mean that depending on the repositories, we can't choose our packages?
Indeed, I don't master the sources.list, so I'd rather avoid it.
So there remains an alternative to aMule. Since I want eD2k and KAD, the options are limited. I haven't managed to install iMule or even qBittorrent. When I click on one of those links, I get another list of applications...
I have Kubuntu because I want the KDE environment. I also haven't managed to install version 20.10 or any system upgrades (Synaptic, Discover, Timeshift, Muon).
I tried to install Hirsute and Groovy.
I understand the messages about the keys, but I'm surprised by their frequency.
Does that mean that depending on the repositories, we can't choose our packages?
Indeed, I don't master the sources.list, so I'd rather avoid it.
So there remains an alternative to aMule. Since I want eD2k and KAD, the options are limited. I haven't managed to install iMule or even qBittorrent. When I click on one of those links, I get another list of applications...
I have Kubuntu because I want the KDE environment. I also haven't managed to install version 20.10 or any system upgrades (Synaptic, Discover, Timeshift, Muon).
Hello,
I tried to install hirsute and groovy.
Can you clarify? Normally you can only install one or the other, and it only depends on the release indicated in
I understand the messages about keys but I'm surprised by their frequency. Does that mean we can't choose our packages depending on the repositories?
No, you're mistaken. The notion of key/signature helps to identify who produced a package. It's the same principle as with software: when you install software, it warns you if it wasn't produced by a trusted third party. On Linux, this mechanism is implemented using those famous signatures (more precisely, using the GPG keys that developers used to sign the packages they provide).
For reference, packages are the standard means of installing software on Linux. Since a package not signed by a trusted third party is potentially fraudulent, your package manager warns you. Additionally, installing a package on Linux requires root rights. This means that, in theory, any operation can be triggered during the installation of a package. Trusting a third party is not something to be taken lightly.
The signature system allows
In any case, if your package manager encounters a package signed by a third party that is not trusted, it will display a warning. To make this warning disappear, you need to add this signature to the trusted third parties. That's the role of the '
In your case, the third party in question is codelite (and this only concerns the packages provided by this repository). If you trust codelite, add their signature by typing (as explained in the documentation):
Indeed, I don't master the sources.list so I prefer to avoid it.
Yet, it is the one that will need to be corrected if you adopt solutions (2) or (3) from my message #6. Moreover, you will sooner or later have to do it when your version of Ubuntu becomes obsolete. In short, it's inevitable, it's just a matter of time.
The only other solutions are to switch to another software (solution (1)) or to manually recompile amule, which is much more complicated than solutions (2) and (3).
I have Kubuntu because I want the KDE environment. I also was not able to install version 20.10 or any system upgrade (synaptic, discover, timeshift, muon)
KDE is very good (as long as the PC is reasonably recent), it's what I use too. Here you mention version 20.10, so groovy (see this table). This amounts to adopting solution (2), migrating to a more recent version of Ubuntu (since you would be moving from
I don't know exactly how you proceed and Ubuntu offers helpers to make a migration.
Concretely, carrying out a migration consists of:
1) Replacing occurrences of the current release (
2) Retrieving the list of updates with the command
3) Updating all installed packages with the command
Note that it's at step 3 that you might encounter problems. Generally, a migration entails significant changes, and you may have packages that conflict. Often the simplest approach is to remove them, while resolving the conflict, and then once the migration is done, reinstall them.
Since migration can sometimes be a bit cumbersome, some adopt a much more radical approach by reinstalling (k)ubuntu in a newer version over the old one (while ensuring to reuse the existing partitions, but without formatting
Whichever method you choose, I recommend backing up important documents on an external drive or a USB stick, as you are never safe from a misstep.
Good luck
EDIT:
I tried to install hirsute and groovy.
Can you clarify? Normally you can only install one or the other, and it only depends on the release indicated in
/etc/apt/sources.list. However, in what you reported, you are on
focal.
I understand the messages about keys but I'm surprised by their frequency. Does that mean we can't choose our packages depending on the repositories?
No, you're mistaken. The notion of key/signature helps to identify who produced a package. It's the same principle as with software: when you install software, it warns you if it wasn't produced by a trusted third party. On Linux, this mechanism is implemented using those famous signatures (more precisely, using the GPG keys that developers used to sign the packages they provide).
For reference, packages are the standard means of installing software on Linux. Since a package not signed by a trusted third party is potentially fraudulent, your package manager warns you. Additionally, installing a package on Linux requires root rights. This means that, in theory, any operation can be triggered during the installation of a package. Trusting a third party is not something to be taken lightly.
The signature system allows
aptto distinguish trusted third parties from others. By default, the only trusted third parties are the maintainers of your Linux distribution. Other keys can be added, either manually using
apt-key, or by installing certain packages (the names of which conventionally end in
-keyring). This remains an exceptional operation.
In any case, if your package manager encounters a package signed by a third party that is not trusted, it will display a warning. To make this warning disappear, you need to add this signature to the trusted third parties. That's the role of the '
apt-key' command.
In your case, the third party in question is codelite (and this only concerns the packages provided by this repository). If you trust codelite, add their signature by typing (as explained in the documentation):
sudo apt-key adv --fetch-keys https://repos.codelite.org/CodeLite.asc
Indeed, I don't master the sources.list so I prefer to avoid it.
Yet, it is the one that will need to be corrected if you adopt solutions (2) or (3) from my message #6. Moreover, you will sooner or later have to do it when your version of Ubuntu becomes obsolete. In short, it's inevitable, it's just a matter of time.
The only other solutions are to switch to another software (solution (1)) or to manually recompile amule, which is much more complicated than solutions (2) and (3).
I have Kubuntu because I want the KDE environment. I also was not able to install version 20.10 or any system upgrade (synaptic, discover, timeshift, muon)
KDE is very good (as long as the PC is reasonably recent), it's what I use too. Here you mention version 20.10, so groovy (see this table). This amounts to adopting solution (2), migrating to a more recent version of Ubuntu (since you would be moving from
focalto
groovy).
I don't know exactly how you proceed and Ubuntu offers helpers to make a migration.
Concretely, carrying out a migration consists of:
1) Replacing occurrences of the current release (
focalin your case) with the new one (e.g.,
groovy) by correcting
/etc/apt/sources.list(e.g., via the command
sudo nano /etc/apt/sources.list, ctrl x to exit) and any files contained in
/etc/apt/sources.list.d;
2) Retrieving the list of updates with the command
sudo apt updateor via your software center;
3) Updating all installed packages with the command
sudo apt upgradeor via your software center.
Note that it's at step 3 that you might encounter problems. Generally, a migration entails significant changes, and you may have packages that conflict. Often the simplest approach is to remove them, while resolving the conflict, and then once the migration is done, reinstall them.
Since migration can sometimes be a bit cumbersome, some adopt a much more radical approach by reinstalling (k)ubuntu in a newer version over the old one (while ensuring to reuse the existing partitions, but without formatting
/home).
Whichever method you choose, I recommend backing up important documents on an external drive or a USB stick, as you are never safe from a misstep.
Good luck
EDIT:
gorilla->
groovy
I just replaced the
focalwith
gorillaand I get this:
Ign :1 http://fr.archive.ubuntu.com/ubuntu/ gorilla InRelease
Ign :2 http://fr.archive.ubuntu.com/ubuntu/ gorilla-updates InRelease
Ign :3 http://fr.archive.ubuntu.com/ubuntu/ gorilla-backports InRelease
Err :4 http://fr.archive.ubuntu.com/ubuntu/ gorilla Release
404 Not Found [IP : 2001:860:f70a::2 80]
Err :5 http://fr.archive.ubuntu.com/ubuntu/ gorilla-updates Release
404 Not Found [IP : 2001:860:f70a::2 80]
Ign :6 http://ppa.launchpad.net/teejee2008/ppa/ubuntu/ gorilla InRelease
Err :7 http://fr.archive.ubuntu.com/ubuntu/ gorilla-backports Release
404 Not Found [IP : 2001:860:f70a::2 80]
Ign :8 http://ppa.launchpad.net/thierry-f/fork-michael-gruz/ubuntu/ gorilla InRelease
Atteint :10 https://repo.skype.com/deb/ stable InRelease
Err :11 http://ppa.launchpad.net/teejee2008/ppa/ubuntu/ gorilla Release
404 Not Found [IP : 2001:67c:1560:8008::19 80]
Atteint :13 https://repo.steampowered.com/steam/ stable InRelease
Err :14 http://ppa.launchpad.net/thierry-f/fork-michael-gruz/ubuntu/ gorilla Release
404 Not Found [IP : 2001:67c:1560:8008::19 80]
Ign :15 http://security.ubuntu.com/ubuntu/ gorilla-security InRelease
Atteint :16 https://repos.codelite.org/ubuntu/ groovy InRelease
Ign :9 https://repos.codelite.org/wx3.0.5/ubuntu/ gorilla InRelease
Err :17 http://security.ubuntu.com/ubuntu/ gorilla-security Release
404 Not Found [IP : 2001:67c:1562::18 80]
Atteint :12 https://repos.codelite.org/wx3.0.5/debian/ buster InRelease
Err :18 https://repos.codelite.org/wx3.0.5/ubuntu/ gorilla Release
404 Not Found [IP : 79.143.189.67 443]
Reading package lists... Done
E: The repository http://fr.archive.ubuntu.com/ubuntu/ gorilla Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
E: The repository http://fr.archive.ubuntu.com/ubuntu/ gorilla-updates Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
E: The repository http://fr.archive.ubuntu.com/ubuntu/ gorilla-backports Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
E: The repository http://ppa.launchpad.net/teejee2008/ppa/ubuntu/ gorilla Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
E: The repository http://ppa.launchpad.net/thierry-f/fork-michael-gruz/ubuntu/ gorilla Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
E: The repository http://security.ubuntu.com/ubuntu/ gorilla-security Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
E: The repository https://repos.codelite.org/wx3.0.5/ubuntu/ gorilla Release does not have a Release file.
N: Updates from such a repository cannot be performed securely, and are therefore disabled by default.
N: See the manual pages of apt-secure(8) for the creation of repositories and details on user configuration.
N: The configured file « universe/binary-i386/Packages » will not be considered because the repository « https://repos.codelite.org/ubuntu/ groovy InRelease » does not support architecture « i386 »
N: The configured file « libs/binary-i386/Packages » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not support architecture « i386 »
W: The configured file « InRelease/binary-amd64/Packages » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/binary-i386/Packages » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/i18n/Translation-en » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/i18n/Translation-fr_FR » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/i18n/Translation-fr » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/dep11/Components-amd64.yml » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/dep11/icons-48x48.tar » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/dep11/icons-64x64.tar » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/dep11/***@*** » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/dep11/icons-128x128.tar » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
W: The configured file « InRelease/cnf/Commands-amd64 » will not be considered because the repository « https://repos.codelite.org/wx3.0.5/debian/ buster InRelease » does not contain the source « InRelease » (typo in sources.list?)
Hello,
I made a mistake, apparently the magic word is
Method 1 (debian method)
To begin, restore your file to how it was before, test it, and save it elsewhere.
Then, replace its content with:
Then run:
Next, complete the upgrade, either via your software center or using the command line:
Since support for
We will properly set up the other repositories later if you still need them. For codelite, just refer to the link I already gave you. For ppas, I generally advise against using them unless you are sure.
Method 2 (with
As explained here, you can replace this entire procedure with the command
(add
Good luck!
I made a mistake, apparently the magic word is
groovy, not
gorilla.
Method 1 (debian method)
To begin, restore your file to how it was before, test it, and save it elsewhere.
Then, replace its content with:
deb http://fr.archive.ubuntu.com/ubuntu/ groovy main restricted universe multiverse deb http://security.ubuntu.com/ubuntu/ groovy-security main restricted universe multiverse deb http://fr.archive.ubuntu.com/ubuntu/ groovy-updates main restricted universe multiverse
Then run:
sudo apt update
Next, complete the upgrade, either via your software center or using the command line:
sudo apt upgrade
Since support for
groovyends in July (see this link), you can also migrate to
hirsuteon the same principle.
We will properly set up the other repositories later if you still need them. For codelite, just refer to the link I already gave you. For ppas, I generally advise against using them unless you are sure.
Method 2 (with
do-release-upgrade)
As explained here, you can replace this entire procedure with the command
do-release-upgrade(specific to ubuntu and that I didn’t know about)
do-release-upgrade --check-dist-upgrade-only --devel-release do-release-upgrade --devel-release
(add
sudobefore these two commands if needed).
Good luck!
I'm sorry, I hadn't seen the last line of your message.
With Groovy it works perfectly, I was able to install aMule without any problems; thank you very much for your patience with me!
I love learning, but I feel like I get discouraged too quickly at the moment. Learning Linux is much more exciting than Windows, it just takes a lot of time. If you know of a site (like a wiki for example, even in English) to help me relearn the basics that would be cool.
I also regret that some tutorials are either outdated (some are from 2005!) while others are not up to date. I still believe that Linux evolves a bit too quickly for me; I mainly need to adapt to it.
That said, when I talk about impatience, I'm hard on myself especially since I spend a lot of time solving problems.
But fortunately, sometimes there are kind people who give their time on this kind of forum.
So all my gratitude to you!
With Groovy it works perfectly, I was able to install aMule without any problems; thank you very much for your patience with me!
I love learning, but I feel like I get discouraged too quickly at the moment. Learning Linux is much more exciting than Windows, it just takes a lot of time. If you know of a site (like a wiki for example, even in English) to help me relearn the basics that would be cool.
I also regret that some tutorials are either outdated (some are from 2005!) while others are not up to date. I still believe that Linux evolves a bit too quickly for me; I mainly need to adapt to it.
That said, when I talk about impatience, I'm hard on myself especially since I spend a lot of time solving problems.
But fortunately, sometimes there are kind people who give their time on this kind of forum.
So all my gratitude to you!
Sorry, I didn't see the last line of your message.
It's possible that you checked it while I was modifying it, so don't worry about it :-)
With Groovy it's working great, I was able to install aMule without any problems; thank you very much for your patience with me!
I love learning, but I feel like I get discouraged too quickly right now. Learning Linux is much more exciting than Windows, it just takes a lot of time. If you know of a site (a wiki, for example, even in English) to help me relearn the basics that would be cool.
I think two things are important in this story. First, you solved your problem, that was the goal. Second, and more importantly, you must have learned a lot: you probably now understand better the causes of the problems you faced, why I proposed those solutions, and why they addressed the issue.
In this discussion, what I think is important to remember is:
Most of these elements are documented (more or less well, but it's always better than nothing) in the Ubuntu documentation. After that, you have to know how to search a bit on the internet; you'll see that the same sites often come up. The reason I get involved in this forum is that many resources are in English, which can sometimes be a hindrance for those who don't master the language.
I also regret that tutorials are either not dated (some date back to 2005!) while others are not up to date. I still believe that Linux evolves a bit too fast for me; I mainly need to adapt to it.
Many things remain true. After that, it’s a collective effort to keep them up-to-date. Each person, depending on their knowledge, beliefs, and time, can get involved more or less in maintaining wikis, answering on forums, developing free software, or getting involved in associations. For now, you say you're discovering, but if this universe interests you, you won't have any trouble finding ways to get involved in turn.
That said, when I talk about impatience I am hard on myself, as I spend a lot of time solving problems.
Yes, I think so too :-) I even believe that this episode should give you confidence in yourself and show you that courage pays off.
But fortunately, sometimes there are kind people who give their time on this kind of forum.
Yes, beyond our beliefs, it's precisely this kind of warm feedback that makes us want to continue to get involved ;-)
Good luck!
It's possible that you checked it while I was modifying it, so don't worry about it :-)
With Groovy it's working great, I was able to install aMule without any problems; thank you very much for your patience with me!
I love learning, but I feel like I get discouraged too quickly right now. Learning Linux is much more exciting than Windows, it just takes a lot of time. If you know of a site (a wiki, for example, even in English) to help me relearn the basics that would be cool.
I think two things are important in this story. First, you solved your problem, that was the goal. Second, and more importantly, you must have learned a lot: you probably now understand better the causes of the problems you faced, why I proposed those solutions, and why they addressed the issue.
In this discussion, what I think is important to remember is:
- installing / updating / removing software is about managing packages (via
apt
on Ubuntu); - the site https://packages.ubuntu.com/ allows you to see which packages are available for which version of Ubuntu
- the available packages directly result from the repositories configured in
/etc/apt/sources.list
, which includes:- the addresses of the mirrors
- the enabled repositories (notably
universe
andmultiverse
) - the version (release) of Ubuntu you are using (in your case,
groovy
for a short time)
- packages must be signed by trusted third parties to avoid triggering warnings;
- you can add repositories (like Skype, Teams), but I strongly discourage adding PPA unless you are sure of what you're doing.
- you can add a trusted third party with
apt-key
;
Most of these elements are documented (more or less well, but it's always better than nothing) in the Ubuntu documentation. After that, you have to know how to search a bit on the internet; you'll see that the same sites often come up. The reason I get involved in this forum is that many resources are in English, which can sometimes be a hindrance for those who don't master the language.
I also regret that tutorials are either not dated (some date back to 2005!) while others are not up to date. I still believe that Linux evolves a bit too fast for me; I mainly need to adapt to it.
Many things remain true. After that, it’s a collective effort to keep them up-to-date. Each person, depending on their knowledge, beliefs, and time, can get involved more or less in maintaining wikis, answering on forums, developing free software, or getting involved in associations. For now, you say you're discovering, but if this universe interests you, you won't have any trouble finding ways to get involved in turn.
That said, when I talk about impatience I am hard on myself, as I spend a lot of time solving problems.
Yes, I think so too :-) I even believe that this episode should give you confidence in yourself and show you that courage pays off.
But fortunately, sometimes there are kind people who give their time on this kind of forum.
Yes, beyond our beliefs, it's precisely this kind of warm feedback that makes us want to continue to get involved ;-)
Good luck!
See https://dane.ac-lyon.fr/spip/IMG/scenari/ubuntu/co/app_miseAjour_sur_linux.html