libcurl4-openssl no longer exists

Bug #124008 reported by Bogdan Butnaru on 2007-07-04
8
Affects Status Importance Assigned to Milestone
curl (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: curl

Somewhere between https://launchpad.net/ubuntu/+source/curl/7.16.2-4ubuntu1 and https://launchpad.net/ubuntu/+source/curl/7.16.2-6ubuntu4 the libcurl4-openssl package disappeared.

I don't know if that's intentional (libcurl4-openssl-dev still exists, apparently), but it's wreaking havoc with the package dependencies:

$ sudo aptitude dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done
The following packages are BROKEN:
  libcurl3-gnutls libcurl4-gnutls
The following packages are unused and will be REMOVED:
  libcurl4-openssl
The following packages will be upgraded:
  apport apport-gtk base-files compiz-fusion-plugins-main curl gnome-applets gnome-applets-data human-icon-theme initramfs-tools
  iptables kdelibs-data kdelibs4c2a libboost-date-time1.34.0 libboost-filesystem1.34.0 libboost-regex1.34.0
  libboost-serialization1.34.0 libboost-thread1.34.0 libcurl3 libcurl4-openssl-dev libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx
  libglibmm-2.4-1c2a libglu1-mesa libglu1-mesa-dev libgtkmm-2.4-1c2a libmms0 libtotem-plparser7 libvlc0 libvolume-id0 mesa-common-dev
  mesa-utils mozilla-plugin-vlc python-apport python-celementtree python-launchpad-bugs python-problem-report sqlite3
  tangerine-icon-theme totem totem-gstreamer totem-mozilla ubuntu-docs udev vim vim-common vim-runtime vim-tiny vlc vlc-nox volumeid
53 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 60.9MB of archives. After unpacking 26.9MB will be freed.
The following packages have unmet dependencies:
  libcurl3-gnutls: Conflicts: libcurl4-gnutls but 7.16.2-6ubuntu3 is to be installed.
  libcurl4-gnutls: Depends: libcurl3-gnutls (= 7.16.2-6ubuntu3) but 7.16.2-6ubuntu4 is to be installed.
Resolving dependencies...
The following actions will resolve these dependencies:

Remove the following packages:
amarok
amarok-engines
amarok-xine
language-support-fr
libcurl4-gnutls
libtunepimp5
libtunepimp5-mp3
openoffice.org
openoffice.org-base
openoffice.org-calc
openoffice.org-common
openoffice.org-core
openoffice.org-draw
openoffice.org-evolution
openoffice.org-filter-binfilter
openoffice.org-filter-mobiledev
openoffice.org-gnome
openoffice.org-gtk
openoffice.org-help-en-us
openoffice.org-help-fr
openoffice.org-impress
openoffice.org-java-common
openoffice.org-l10n-en-us
openoffice.org-l10n-fr
openoffice.org-math
openoffice.org-style-andromeda
openoffice.org-style-crystal
openoffice.org-style-human
openoffice.org-style-industrial
openoffice.org-thesaurus-en-us
openoffice.org-writer
python-pycurl
python-uno
thunderbird-locale-fr
ubuntu-desktop
xine-ui

Leave the following dependencies unresolved:
bzr recommends python-pycurl
language-pack-fr-base recommends language-support-fr
Score is -10824

Steve Kowalik (stevenk) wrote :

This is intentional and known about. There are roughly forty packages that are affected by the libcurl migration, and we are working on that. Just due to the sheer number of packages it is going to take a few days to sort out.

Changed in curl:
status: New → Invalid
Bogdan Butnaru (bogdanb) wrote :

OK. I'll check it out in a few days. I didn't see any comments on that around the net.

Is there any way of installing something in the meantime without breaking the installed packages? (Ignoring the mess with openssl?)

Bogdan Butnaru (bogdanb) wrote :

I've been thinking: Shouldn't this bug be left "open" (or "in progress") until the migration is deemed complete? (It's still a bug even though it's "intentional" because it's not wanted behavior, it's a temporary side-effect of a change, like a (known) regression... right?)

Since there are so many packages, there should be a way to know when things "should" be complete. That way I can tell if I get update errors because it's still being worked on or if I actually have something broken.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers