Wheezy and Jessie were recently removed from the mirror network, so if you want to continue fetching Jessie backports, you need to use archive.debian.org instead:
deb [check-valid-until=no] http://archive.debian.org/debian jessie-backports main
(Validity checks need to be disabled since the repository is no longer being updated. Jessie’s apt doesn’t ...
Debian Jessie and later (2014-)
As pointed out by @voltagex in the comments, it can now be found in the software-properties-common package:
sudo apt-get install software-properties-common
Debian Wheezy and earlier:
The program add-apt-repository is available in Debian. It's in the python-software-properties package:
sudo apt-get install python-software-...
You can set options in your sources.list:
deb [trusted=yes] http://localmachine/debian wheezy main
The trusted option is what turns off the GPG check. See man 5 sources.list for details.
Note: this was added in apt 0.8.16~exp3. So it's in wheezy (and of course jessie), but not squeeze.
After trying solutions suggested by @inostia and @Stephen Kitt I was still getting the following error:
W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found
E: Some index files failed to download. They have been ignored, or old ones used instead.
I figured out that it can be solved by removing the ...
You need to take a look at https://wiki.debian.org/Packaging — the packaging tutorial there will help you a lot, as well as parts of the new maintainer's guide.
As to your questions, in order:
The repository contains "list" files. E.g.., http://http.us.debian.org/debian/dists/stretch/main/binary-amd64/Packages.xz. apt-get update downloads these list files, ...
I would assume most distros accept individual private donations (they may also accept free hosting). However, that is probably not the bulk of their financing in most cases.
Note that some of the major distros may have some paid staff, and possibly also office space, the cost of which likely exceeds that of hosting the repos1. This should not be taken to ...
You can use repotrack instead like this:
repotrack -a x86_64 -p /repos/Packages [packages]
Unfortunately there is a bug with the -a flag (arch). It will download i686 and x86_64.
Here's how to fix it:
#archlist = 
archlist = opts.arch.split(',') # Change to this
On Ubuntu amd64 installations, i386 is enabled as an additional architecture by default. apt & co. expect repositories to provide all configured architectures, which causes the error you're seeing.
Since your mirror only has amd64 packages, you should mark it as such:
deb [ arch=amd64 ] file:///var/spool/apt-mirror-trusty/mirror/archive.ubuntu.com/...
This happened to me provisioning a Vagrant box that was using Debian "Jessie".
Following Stephen Kitt's answer, switching to archive.debian.org worked for me, but I had to add it to /etc/apt/sources.list.d/jessie-backports.list, rather than to /etc/apt/sources.list.
I added the following line to provision.sh:
echo "deb http://archive.debian.org/debian ...
Usually each Linux distro has a few central servers were they put directly all the packages. But there exists mirrors arround the world that have copies of these packages. These mirrors comunicate directly with the central servers looking for updates periodically. Normally there is a delay in the release of an update between this central servers and the ...
non-free packages are packages not complying to the Debian Free Software Guidelines definition. E.g.:
nvidia-driver which provides a proprietary driver.
contrib packages are packages that do comply with the DFSG, but depend on non-free packages, or which depend on some non-free software downloaded (by the package or having to be downloaded manually) to ...
You need --update option with createrepo
createrepo --update: Sometimes you have a lot of packages in your repsitory and regenerating the meta data for each package when only a few packages have been added or changed is just too time consuming. This is where --update comes in handy. You run createrepo just like you did before but you pass the --update ...
In order to remove the actual yum repository rather than just to disable it, you have to find the package and remove it.
rpm -qa | grep epel
yum remove epel-release-5-4
yum clean all
For everyone's information, yumdownloader does not do the job. For anyone with some experience in package management with `yum, it is natural to expect that the following command-line would recursively download a package RPM and all its dependencies:
yumdownloader --resolve <package>
But it does not. May be it prints first-level dependencies or those ...
Get gcc-doc package
In order to be able to fetch this packages with the apt-get install command we need to edit our sources.list file to include both contrib and non-free repositories.
For example, here's my /etc/apt/sources.list file:
deb http://httpredir.debian.org/debian/ jessie main contrib non-free
deb-src http://httpredir.debian.org/debian/ jessie ...
Assuming you're running a non-ancient version of Debian (Etch or later), you can just drop a file in /etc/apt/sources.list.d/ The file name must end with .list; Debian Stretch (not yet released) will likely add .sources with a different format.
The format is the same as the main sources.list file.
The advantage is, especially if this is for some software ...
Just in case anybody ends up here, like me, looking for the equivalent answer for dnf on Fedora I fathomed out the following python one-liner:
python3 -c 'import dnf, pprint; db = dnf.dnf.Base(); pprint.pprint(db.conf.substitutions,width=1)'
On Fedora 24 it looks like this:
On AskUbuntu there is this question which may of help
The repositories for EOL Ubuntu releases are archived, so http://archive.ubuntu.com/ubuntu/dists/ was moved to http://old-releases.ubuntu.com/ubuntu/dists/ (raring-updates is here) - basically all you should need to do is replace archive.ubuntu.com & security.ubuntu.com in the software sources (/etc/...
If you trust the repo, you can simply edit the file /etc/yum.repos.d/mysql-community.repo and disable the gpgcheck
name=MySQL 5.7 Community Server
I found the answer from https://www.reddit.com/r/bashonubuntuonwindows/comments/8fcbs5/update_of_opensuse_on_wsl_error/ : you need to change the repository URIs from HTTP to HTTPS. I just did that and was able to see new packages. I only had the oss and oss_update repositories, so the process I followed was:
sudo zypper rr oss
sudo zypper rr oss_update
Delete this centos.repo (or change enabled=0 for all) and Create a new repository centos1.repo in /etc/yum.repos.d/ with the content:
Now check if you can install ...
you can remove the repo with yum-config-manager but not with yum:
yum-config-manager --disable repository
yum-config-manager --add-repo http://www.example.com/example.repo
EDIT: you need some way of running this as root (ie. sudo)
Clean the cache
For starters I would clean up my cache area.
$ sudo yum clean all
Testing each repo
If that doesn't resolve the issue then I would go through and attempt to disable each repository 1 at a time and then re-run the yum list command to see if that resolves your issue.
You can do this via the command line temporarily, but first you need to ...
This error happens because you have some YUM repository configuration in /etc/yum.repos.d/ that lists a GPG key like this:
This configuration is telling YUM that the GPG key for the repository exists on disk. The error you get from YUM is YUM letting you know that it couldn't find the GPG key at the path /...
I was just looking for the very same thing. If you use eix, you are in luck.
From the wiki:
Adding overlays to the cache
To search not only in the portage tree but all the overlays, add overlays to the cache
root # eix-remote update
and then sync it all:
root # eix-sync
(example from my system)
$ eix nuvola
Available versions: ...