Description of problem: I'm now trying to compile & build a new version of wine from the wine-git & the Mageia Cauldron spec-file tells me that docbook-dtd31-sgml is required. How is it possible that wine needs a deprecated package? Here's the error when I tell urpmi to install that package: installing docbook-dtd31-sgml-1.0-19.mga2.noarch.rpm lib64gphoto-devel-2.4.14-0.1.mga2.x86_64.rpm from /var/cache/urpmi/rpms Installation failed: docbook-dtd31-sgml < 1.0-57.mga1 is obsoleted by (installed) docbook-dtds-1.0-57.mga1.noarch Version-Release number of selected component (if applicable): 1.0.19 How reproducible: Everytime I try to install it. Steps to Reproduce: 1. Open console or rpmdrake. 2. Install docbook-dtd31-sgml using urpmi in console or rpmdrake. 3. Installation fails because it seems to be deprecated.
pterjan any reason to have importing this package ? and kristoffer your summary does'nt the real bug.
Assignee: bugsquad => pterjan
CC: (none) => kristoffer.grundstrom1983Hardware: i586 => x86_64
Whiteboard: (none) => wine
BuildRequires: docbook-utils docbook-dtd-sgml I don't understand your bug report and why you want to install the wrong package. I tried to build wine on 2 and cauldron: no bug on my side.
CC: (none) => mageia
Well, did you use the git-code or Mageia source-RPM?
I don't care about git-code as I'm a packager of stable releases. As I told you, "I tried to build wine on 2 and cauldron: no bug on my side". So... with srpm of Mageia.
(In reply to comment #4) > I don't care about git-code as I'm a packager of stable releases. > As I told you, "I tried to build wine on 2 and cauldron: no bug on my side". > So... with srpm of Mageia. With all do respect, there are people that want to build custom packages sometimes. I'm one of thoose & how could I successfully make such package if this error is showing?
I just submitted wine 1.5.10 to cauldron without any issue. So I don't understand your bug report.
Why do you want that package? The files which used to be in it are now in docbook-dtds so docbook-dtds is enough to do enything you may have wanted to do with docbook-dtd31-sgml.
Status: NEW => RESOLVEDResolution: (none) => INVALID
Yes, but then the spec-file have to be edited to remove that as a dep then.
(In reply to comment #8) > Yes, but then the spec-file have to be edited to remove that as a dep then. docbook-dtd31-sgml has never been a dep of wine... Only docbook-dtd (as said in comment #2)
Check rows 67 & 68 in the spec & you'll see that you're wrong.
docbook-dtds provides docbook-dtd31-sgml so any package requiring docbook-dtd31-sgml will be happy with docbook-dtds.