![]() StableUpdates: official Debian repository for changes that cannot wait for the next point release, packages are also added to StableProposedUpdates for inclusion in the next point releaseĭebianSecurity: official Debian repository for frequent security updatesĭebianBackports: more recent versions of some packages, compatible with DebianStable.ĭebianTesting: current development state of the next stable Debian distributionĭebianUnstable: rolling development version containing the latest packagesĭebianExperimental: development version containing the experimental/alpha/beta/untested packagesīeing able to change the repositories used by your package management system is a powerful feature but this power comes with some responsibility. StableProposedUpdates: official Debian repository for upcoming point releases (security and important bug fixes every ~2 months) What versions of packages are availableĭebianStable: official Debian repository for the current release.What software packages are available for download.The specific repositories (package sources) configured on your machine affect: Local directories or CD/DVD are also accepted. I updated and upgraded the system and did a dist-upgrade.Apt downloads packages from one or more software repositories (sources) and installs them onto your computer.Ī repository is generally a network server, such as the official DebianStable repository. I reactivated the additional sources of the PPAs in /etc/apt// (by removing the comment character). Unfortunately, the packages installed from that PPA misbehaved now. php-7.2), that haven’t been available in trusty, but are in xenial and bionic. I thought, that this is no problem, since I added the repository for packages (e.g. The funny thing was, that php-7.2 has already been installed! Long Story Short: The Issueĭuring upgrade, the system deactivates your additional repositories (PPAs) and does not reactivate them afterwards. It said, that it has to install php-7.2, but it won’t. The following packages have unmet dependencies:Į: Unable to correct problems, you have held broken packages. ![]() The following information may help to resolve the situation: Requested an impossible situation or if you are using the unstableĭistribution that some required packages have not yet been created After that I checked, whether the upgrade seemed good so far: The solution in the page mentioned above did work. Of course, I had a backup, but my feelings said, that this issue will follow me again and again, if I just retry the upgrade. That is, I had to fix a distro upgrade that failed in between… challenge accepted □. You do not want your system showing you such a message during do-release-update. Then after everything worked again, I did another upgrade, which failed because of this issue. The first upgrade was “successful” with a lot of need for adaption in the configurations afterwards. ![]() Hence, I did two dist-upgrades after another from trusty to xenial and from xenial to the current LTS version bionic (every 2 years a new LTS version is coming out). So, support for Owncloud run out last year and I thought that the days between years are a good time to switch to a new version. But not every open source software has given you this promise, just the Ubuntanians. That means 5 years of support… I was running trusty from 2014, so there should be support until 2019. My blog runs on a VM at Hetzner with an Ubuntu LTS system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |