Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 811162] New: texlive-scheme-medium won't install due to many uninstallable texlive components
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 23 Mar 2013 01:35:36 +0000
  • Message-id: <>

Summary: texlive-scheme-medium won't install due to many
uninstallable texlive components
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: i686
OS/Version: openSUSE 12.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: jimc@xxxxxxxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: Customer
Blocker: ---

(This is actually for OS = openSUSE 12.3)
I do: zypper install texlive-scheme-medium . It complains that
texlive-scheme-medium-2012.61.svn18615-4.2.1 requires uninstallable provider
texlive-collection-context-2012.61.svn23785-4.2.1.noarch .
Following the chain of A requires uninstallable B requires uninstallable C... I
requires texlive-extratools >= 2012
Uninstallable provider: texlive-extratools-2012.61-4.2.1.noarch
And texlive-extratools is installable by itself.
If I do: zypper install texlive-extratools texlive-tools
it says texlive-extratools-2012.61-4.2.1.noarch obsoletes texlive-tools
provided by texlive-tools-2012.60.svn26263-4.2.1.noarch
Note that %{texlive_noarch} is 61 on extratools and 60 on tools.
The source RPM for all these packages is
In the texlive-extratools section it says:
Obsoletes: texlive-tools < %{texlive_version} (value is 2012).
I think Zypper is overinterpreting the Obsoletes relation. I commented out the
Obsoletes statement, and this pair of packages became installable, but there
were several other similar dependency chains that I followed, stomping
Obsoletes statements one at a time, but I did not finish that project.

Workaround: I edited texlive-filesystem.spec removing every Obsoletes
statement, incremented the build number on all packages (78 of them I think) to
4.2.2 (from 4.2.1) so the recompiled package will be preferred, and did:
rpmbuild -bb /usr/src/packages/SPECS/texlive-filesystem.spec
I made the built packages, from /usr/src/packages/RPMS/noarch, available on my
enterprise mirror. Now texlive-scheme-medium, which is my desired keystone
package, can be installed.

What I would like the developers to do: I'm not completely sure.
A. Is libzypp or satsolver comparing the complete versions of potentially
obsolete packages (wrong)? It should do just the comparison listed in the
Obsoletes statement, which would have let these packages on.
B. Is texlive-filesystem.spec overzealous with the Obsoletes relations?
What's in the spec file seems reasonable, if it would just be obeyed.
C. All these packages originate from the Official Release on (no Pbone, no "unstable packages"). Although I believe
all the packages out of texlive-filesystem have %{texlive_noarch}=61, there are
a number of other packages back at minor(?) version 60, such as
texlive-tools-2012.60.svn26263-4.2.1.noarch and
texlive-xdvi-2012. . Is this version skew
actually causing the problem, and would upgrading all packages to minor version
61 put a band-aid on it?

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >