[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Depends: libapt-pkg-libc ... which is a virtual package



It seems for us experimental archive users, most of the year we see e.g.,

The following packages have unmet dependencies:
  aptitude: Depends: libapt-pkg-libc6.9-6-4.8 which is a virtual package.
  python-apt: Depends: libapt-inst-libc6.9-6-1.1 which is a virtual package.
              Depends: libapt-pkg-libc6.9-6-4.8 which is a virtual package.
  libapt-pkg-perl: Depends: libapt-pkg-libc6.9-6-4.8 which is a virtual package.
  libept0: Depends: libapt-pkg-libc6.9-6-4.8 which is a virtual package.

then about every two months the problems go away for two weeks.

It would be nicer if every two months, the problem persisted for only
two weeks. Can't somehow things be more coordinated?


Reply to: