New answers tagged

1

While make(1) and many buildsystems, such as autotools, do support incremental compilation, Gentoo with stock Portage does not take advantage of it. After a package is compiled and installed, the working directory is discarded. The actual difficulty with using incremental compilation would be getting packages to build reliably in this fashion. It is much ...


0

There is an official package now for this task called app-portage/portpeek. It can find obsolete USE flags and obsolete KEYWORDS and clean the files, if -f (fix) is added as parameter.


1

Portage compiles full sources of the new package as delivered by upstream (sometimes gentoo team patches the source themselves, but that is another story). The binaries of the old package are usually removed, although some old libraries may stay if deleting them would harm other packages. To remove old sources you need to run eclean -d distfiles yourself.


1

CLTM might be required if your corporate proxy uses NTLM from Microsoft. After you have cntlm proxy server configured for upstream proxy (which is your corporate proxy), just configure npm to use it: npm config set proxy http://127.0.0.1:3128 npm config set https-proxy http://127.0.0.1:3128 You must have both http and https. Most package managers work ...


3

Generally speaking, new versions of libraries which introduce backwards incompatibilities should change their soname, and this will then result in a new package name for the runtime library (e.g. for GTK+, libgtk2.0-0 and libgtk2.1-0 or whatever is appropriate). It's usually considered a serious bug to introduce a breaking version upgrade without following ...


2

According to the npm config help, it will only derive its proxy settings from the environment If the HTTPS_PROXY or https_proxy or HTTP_PROXY or http_proxy environment variables are set (from the https_proxy section, the proxy section only mentions HTTP_PROXY and http_proxy). The help also doesn't list all_proxy as a configuration key anywhere, just ...


6

A solution can be made with a simple script: Open file $ vim yaourt-helper.sh Create script #!/bin/bash _update="yaourt -Syua --noconfirm" if ! which $1 2>/dev/null 1>&2; then echo 'Package not installed, installing' $_update $1 exit $?; fi echo 'Already installed, checking for upgrade' $_update Set permissions and execute $ chmod +...


1

dpkg is not lying, you do not have enough space to install unity-editor-5.3.5f1+20160525_amd64.deb. Your root filesystem only has 404.25 MB of space available, and you are trying to install a package that is 1.2 GB. Filesystem 1K-blocks Used Available Use% Mounted on /cow 4062904 3439240 413952 90% / 413952 KB available. 413952 KB =...


2

Edit sources.list sudo nano /etc/apt/sources.list Comment out a line that starts with this: deb cdrom


3

If you go to the package AUR page and View Changes, you can see that in the most recent commit one of the version numbers was increased, but that file's corresponding md5sum didn't change. # Module Versions _about_arch_url="fusion809/about" -_about_arch_ver=1.5.17 +_about_arch_ver=1.5.18 _dark_bint_syntax_ver=0.8.6 _fusion_ui_ver=0.10.5 ...


4

gdebi is the appropriate tool for this: sudo gdebi foo_1.0.0.deb will install foo from the given package file, and any necessary dependencies.


0

The best way is to use PackageKit. It will work on both Ubuntu and Fedora. Here is example how to use that: https://www.freedesktop.org/software/PackageKit/pk-faq.html#session-methods


0

I would like to thank jasonwryan for pushing me in the right direction. At this stage, I'm sure I'd be able to install Arch blindfolded and drunk, but without his help I would not have progressed far. How I solved my problem: I've used EaseUS Partition Master under Windows to create a partition for Arch. I've tried using parted and gdisk on the live ...


2

nixpkgs reorganized things since the accepted answer was posted and there is a new function for disabling tests. You now wrap any Haskell package with the nixpkgs.pkgs.haskell.lib.dontCheck function to disable tests. Here is an example Nix expression from one of my Haskell projects where I had to disable tests for the shared-memory dependency when building ...


4

Package managers need to run as root because what they do affects all users. IMO package managers should require sudo only when writing files to a dir owned by root. like /bin or /etc. They also require root access to manage the database of installed packages. A package manager that installs software under a user's home directory doesn't need to run ...


0

Package manager is a powerful tool to repair&destroy system. It's easier to ask root privilege once when check all actions for permission.


1

for system packages on nixos it is probably best to keep then in configuration.nix file (environment.systemPackages)


0

if you want to just update your servers automatically, which is remarkably safe under CentOS 4/5/6/7 unless you've done really bad things. Just do this: yum install -y yum-cron sysconfig yum-cron on service yum-cron start You're done. If you want to just check what's available, and not install anything, do yum upgrade and hit N when you have the ...


0

If you have glibc 2.12 installed, you do NOT have CentOS7; you're on CentOS6. While there's been a lot of grief about the locking of major/minor versions after distro release - it's for stability, testing and certification; you'll learn the value later - the version you're looking at should not exist under an up-to-date centos7. Update your CentOS7, do a ...


0

Be careful if you're thinking a simple conversion will do it: converting a deb to an RPM and vice versa, due to vast differences in filesystem layout, is like dressing up an American in French clothing and expecting him to fit in. Differences in filesystem layout, kernel, libraries and tunings are like cultural differences; and you can't expect a smooth ...


2

I came up with two options using diff that should work for you. Using diff -u and sed: diff -u old new | sed -n 's/^-\(.*\.so\..*\)/\1/p' /usr/lib/libfoo.so.1 /usr/lib/libfooabc.so.1 That command outputs the full diff between the two files, and we use sed to filter out only the changes from the 'old' file (indicated by a leading -), and further filter ...


1

This appears to be related to bug #665487. To remove dovecot-managesieved, try renaming /etc/init.d/dovecot temporarily: sudo mv /etc/init.d/dovecot{,.disabled} sudo apt-get purge dovecot-managesieved sudo mv /etc/init.d/dovecot{.disabled,} This should avoid the attempt to restart dovecot during the package's removal.



Top 50 recent answers are included