Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • You said "I left the Debian texlive-packages where they are". I don't understand. You have installed the TeX Live packages from CTAN, and you also have the Debian TeX Live packages installed? Why? The error you are seeing is generally when one is using a versioned Provides, which is a no-no according to Debian policy. But I don't see that in the Control file you have provided. BTW, it is better if you just include the full paste in your question, and not point to some external paste site. It is Ok if the paste is a little long. Commented Feb 12, 2014 at 9:38
  • why do you need to create the virtual package? do you need to satisfy any dependencies? if so, are there any versioned dependencies you need to satisfy? Commented Feb 12, 2014 at 10:00
  • 1
    @umläute The virtual package is so that dpkg thinks that those packages are installed, though the poster actually has a local install of TeX Live. The poster is probably using tug.org/texlive/debian.html as a reference. See the section "Integrating vanilla TeX Live with Debian" Commented Feb 12, 2014 at 10:03
  • @FaheemMitha i know what virtual packages are typically used for: to satisfy dependencies of (or state dependencies on) other packages. so the question is: why does the OP need this? the package manager need not be aware of software installed into /usr/local for instance... Commented Feb 12, 2014 at 10:12
  • @umläute so that he can install Debian binary packages which require TeX Live packages as dependencies. Commented Feb 12, 2014 at 10:13