Hızlı yanıt: kod örneği
The Ubuntu Help site has the answer: package that was released for has a serious packaging bug, where it expected a directory structure use in Apache 2.2, whereas had Apache 2.4. It couldn't even be installed. The fix was released in .For most users, enabling all four shouldn't be a problem most of the time. For a very stable environment, keep only enabled. Keep enabled if some package you're using has a packaging issue. Updates packages have to conform to policies regarding stable updates, so they shouldn't cause breakage and keeping them enabled all the time is recommended. Keep enabled if you don't mind testing out new things. This might cause things to break on occasion, so if you're not a fan of the " latest and greatest" philosophy, keep it disabled unless you have a problem and devs ask you to enable it. Keep enabled if you wish to have software that is typically only available for a newer release of Ubuntu.
- "Important Security Updates (raring-security)". Patches for security vulnerabilities in Ubuntu packages. They are managed by the Ubuntu Security Team and are designed to change the behavior of the package as little as possible -- in fact, the minimum required to resolve the security problem. As a result, they tend to be very low-risk to apply and all users are urged to apply security updates.
- "Recommended Updates (raring-updates)". Updates for serious bugs in Ubuntu packaging that do not affect the security of the system.
- "Pre-released Updates (raring-proposed)". The testing area for updates. This repository is recommended only to those interested in helping to test updates and provide feedback.
- "Unsupported Updates (raring-backports)". As the name states, these are unsupported new versions of packages which have been backported to an older release. Packages may contain new features, may introduce new interfaces, and bugs.
phpldapadmintrustytrustytrusty-updatessecurityupdatesproposedbackports