Tag Info

Hot answers tagged

10

deb lines are relative to binary packages, that you can install with apt. deb-src lines are relative to source packages (as downloaded by apt-get source $package) and next compiled. Source packages are needed only if you want to compile some package yourself, or inspect the source code for a bug. Ordinary users don't need to include such repositories.


6

RPM file is not repository. It is type of package that is used in CentOS (and Red Hat and some other distributions). Repository is place that packages are kept and can be downloaded and installed by package manager in your distribution. Another package format is DEB. It is used by Debian, Ubuntu and their derivatives. There are also other formats, but that ...


5

This isn't a direct answer to your question, but there are several things you can do to mitigate against this risk. The simplest one is to check your downloaded packages against the checksums from a different mirror than you downloaded from. When my package manager (poldek) downloads a package, I have it set to keep a copy of the downloaded rpm in a cache ...


5

Use a meta package (e.g. linux-image-2.6-686), depending on which you want to use. This is so that if the real package name changes (which is very often), you won't lag behind. To determine which meta package to use, have a look at the name of the kernel package you are running. Also, do read the package descriptions of the meta packages that seem like the ...


5

I don't know how to list all packages and their repositories, but for a single one you can just execute apt-cache policy <package>. The line with the *** is the currently installed version with the corresponding repositories. Setting the priority of a particular source is called apt pinning and can be done via /etc/apt/preferences (newer Ubuntu ...


4

It's not about older stable versions, but still: stable means, that this version is not to be changed anymore. Debian includes new versions into experimental/unstable and maybe into testing. Some really important programs (like iceweasle ;) are also "backported" into the already stable versions (if you like back to the old testing). So that people who feel ...


4

That's simply not true. I'm posting this from FF 8.0.1, installed directly from the repos (Arch), and at work I have 8.0 (Ubuntu 11.10). Ubuntu (and maybe others) sets in stone the major versions of the software in each release's repo at its release, so that no incompatibility arises if one package doesn't support another's new major version and it doesn't ...


4

Apparently Debian does not have something like Launchpad PPA, since latest packages can damage system's stability. Instead it has a separated approach (assuming one is running the stable release and in the order of decreasing stability): Backports. Here one can find somewhat newer but not the latest version of some packages without compromising the ...


4

Your question made me think of this letter by Debian's founder Ian Murdock :) In theory Debian will use the exact same package management system that Ubuntu does. If the words apt-get or Synaptic sound familiar, then you already know how to use Debian's packages. As a matter of fact, most of the packaging is done by Debian's developers, and Ubuntu will ...


4

You seem to have the freshrpms repository installed and enabled, but as http://freshrpms.net/ says, since Fedora 10 almost everything has moved to rpmfusion so you probably don't need it anymore and should switch to rpmfusion. The specific cause of your error is simply that the freshrpms repository doesn't have any content for Fedora 15. You can probably ...


4

You can use the addremove command to mark missing files (those prefaced with a !) as removed. See the excellent Mercurial: the Definitive Guide chapter on tracking files. For future reference, there is a command to move files, hg mv.


4

Fedora packages are signed and checksummed. Even 3rd party repositories such as rpmfusion sign their packages. Yum (the package manager) requires a special flag (--nogpgcheck) to install packages which haven't been signed.


4

Most of the repositories specify a mirrorlist in their configuration file. When present, yum will select one or more of the mirrors provided by the list. Repos that don't have mirrors will have baseurl instead of mirrorlist. When downloading multiple packages, yum can download from multiple sites in parallel, though this isn't always obvious in the terminal ...


3

I don't think it's a good idea to import a Fedora repository - regardless of version - into RHEL6 or another Linux distribution derived from it. Those packages are not tested for working together and different compilation options and patches might introduce subtle incompatibilities even between packages with the same name and version. What you can do is ...


3

From the Website for Bodhi Linux, their distribution, which was just released a few days ago, is based upon Ubuntu LTS. It would be technically challenging to add more recent Ubuntu packages and maintain coherence; that is why backports are limited. Given that this distribution just had its initial release less than a week ago, it would probably be best to ...


3

As you can find on the Debian Multimedia home page The first package to install is debian-multimedia-keyring. Since Squeeze you can install this package with apt-get but you need to press Y when the package ask what to do and do not press return. So, summing up, don't care about apt-get update warning, install the named package and answer Y when ...


3

Package sources are listed in /etc/apt/sources.list and /etc/apt/sources.list.d/*.list. Usually you would list official sources in the main file /etc/apt/sources.list and add third-party repositories in /etc/apt/sources.list.d/indicative_name.list. If you installed from CD-ROM, there'll be a line with deb cdrom:[some name]/ stable main Remove it or ...


3

I made an RPM for this a little while ago. You can find the source RPM here ftp://ftp.pycopia.org/pub/python/RHEL51/python2.7-2.7.1-1TH.src.rpm Just do the usual rpmbuild --rebuild ... to create the binary rpms. It does not interfere with the installed 2.4 version, it coexists with it. but you do have to put the specific version in your scripts: ...


3

Regarding Debian suites, that README file is not complete. For one, it's missing Experimental. Browse its parent folder for more. As for the other suites that don't live on the main mirrors, the three you listed is all there is. There's of course a whole bunch on non-official repositories.


3

That package isn't int the Ubuntu repositories for armel or armhf (at least according to packages.ubuntu.com -- you can probably compile the source package (qwtplot3d). It looks like that package is in universe, so you'll need that enabled. You should be able to run apt-get build-dep qwtplot3d apt-get source qwtplot3d cd qwtplot3d-*/ dpkg-buildpackage ...


3

Unlike other systems, where the "developer makes available, people use" deployment strategy is used (Windows, I'm looking at you), with UNIX-like distros, there's usually a package manager and some team managing its packages. The main point is so that everything works well together. At least when I used Windows, the usual thing was that a program would ...


3

After simple checks I've asked you in answer comment: [root@Backup yum.repos.d]# yum -bash: yum: command not found [root@Backup yum.repos.d]# which yum /usr/bin/which: no yum in (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin) [root@Backup yum.repos.d]# echo $PATH ...


2

In Fedora the packagers are given most of the decision control. It's up to the person that packages the software to decide which Fedora releases to push it into. For certain major "mission critical" type software that is used by lots and lots of people, and Firefox is a good example, they tend to wait until new versions of the OS before releasing an ...


2

All Arch Linux packages use an md5 or sha1 sum to check that all the bits are in place. It's up to the package maintainer to choose the hashing algorithm. Packages installed from AUR (often just a small PKGBUILD text file) are supposed to be checked by the installee before being installed. The repositories containing the official binary packages are ...


2

Have you checked any of these repos: Dag Wieers Dries rpmforge livna Is it ok if you have the rpm instead of a repo (i.e. can you take care of dependencies if it arises?). If so, try phone or rpmfind. If none of the above helps, consider building from source tar balls. By far that will be the easiest.


2

It helps to understand what the action of porting software means. From Wikipedia, porting is the process of adapting software so that an executable program can be created for a computing environment that is different from the one for which it was originally designed (My emphasis added on the word different). The back in backporting denotes the ...


2

Package compatibility isn't determined by the choice repository, each package contains dependency declarations. As long as the packages are of reasonable quality, i.e. they declare the dependencies they're supposed to, you can continue to use that repository. If there's an incompatibility, you'll be told, because there'll be an unfulfilled dependency. Using ...


2

If you visit the PPA's page it'll show you what lines to manually insert into the source.list Click on Technical Details which reveals the following Choose your Ubuntu version and copy/paste the lines into the bottom of your source.list file.


2

Your answer is on this page : http://adminotes.blogspot.fr/2011/12/centos-6-rpm-sign-problem-v4-signatures.html In summary, v4 signature are used by default in Centos 6, but Centos 5 only supports v3. Adding --force-v3-sigs flag in your %__gpg_sign_cmd will makes it work.


2

From the reposync help: -r REPOID, --repoid=REPOID specify repo ids to query, can be specified multiple times (default is all enabled) That means you will need to pass the -r option to reposync and the name of the repo to sync. So, your command should look like the following: ./reposync -n -c vmware-tools.cfg -p ...



Only top voted, non community-wiki answers of a minimum length are eligible