Date: Fri, 12 Oct 2007 06:41:36 +0200 From: "Dan A." <infernal211283.freebsd@gmail.com> To: freebsd-gnome@freebsd.org Subject: Problem with pidgin installation Message-ID: <22d026f00710112141h1f2d14d9r405d544af98bcf41@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
A week or so, I posted in the -ports lists in hope to get an answer to that question but except being asked to check whether or not it's a portmaster issue, the folks couldn't help me. I'm also not sure if this should be posted here but from what I understood, pidgin is part of gnome so here it is. I fixed the problem and will post the solution at the end. I guess the maintainers would know what to do with this information ; ) The original message as it was posted to the -ports list on 3.10.2007 : --------------- Hi. While trying to install net-im/pidgin using portmaster, I get this error: ===> Installing for docbook-sk-4.1.2_4 ===> docbook-sk-4.1.2_4 depends on file: /usr/local/bin/xmlcatmgr - found ===> Generating temporary packing list for file in `/usr/bin/find /usr/ports/textproc/docbook-sk/work -type f | /usr/bin/sed -e 's|^/usr/ports/textproc/docbook-sk/work/||' | /usr/bin/grep -v '^\.' | /usr/bin/sort`; do install -o root -g wheel -m 444 /usr/ports/textproc/docbook-sk/work/$file /usr/local/share/xml/docbook/4.1.2/$file; done xmlcatmgr: entry already exists for `-//OASIS//ELEMENTS DocBook XML Information Pool V4.1.2//EN' of type `public' *** Error code 1 Stop in /usr/ports/textproc/docbook-sk. I checked in the /usr/local/share/xml/docbook, tried to search for "xmlcatmgr" string in all the files, in hope to do something that will fix this but I couldn't find it. I tried to uninstall docbook\* and reinstall textproc/docbook-sk but it fails with that same error. Tried to uninstall xmlcatmgr and install pidgin but pidgin requires docbook-sk for which xmlcatmgr is a dependency, and the problem repeats. Is there something that I can do about this? Thank you. --------------- The solution as it was posted in the bsdforums.org on 11.10.2007: --------------- Ok there was no answer from the folks on the mailing lists so I gave it another try. I found a solution which works after some, sort of hackish, steps and a bit of luck. As I already said, I got stuck on that textproc/docbook-sk port, I knew it has to be something with the files in /usr/local/share/xml/ so I tried to reinstall docbook-sk again and after it failed I ran *find /usr/local/share/xml/ -cmin -1 -depth 1* which showed me that a file named *catalog.ports* was touched, so I knew that's the S.O.B. that was messing around with my installation. I renamed the file from catalog.ports to _catalog.ports just in case I'll need it later. Now I could happily install docbook-sk but I got stuck on *sdockbook-xml* saying something similar about some existing entry... I thought that maybe reinstalling xmlcatmgr would help but it didn't, however I noticed that it creates a fresh file called catalog.ports with some lines in it but nothing about sdocbook-xml (the previously renamed catalog.ports didn't have that either). I scratched my head and decided to read a bit about xmlcatmgr, there I saw that I can "destroy" the catalog file which defaults to /usr/local/share/xml/catalog.ports, I went for it and the file then was gone. While being in complete doubt that "destorying" the catalog.ports file was any more useful than renaming it (after all, it did get stuck after the file was renamed to _catalog.ports), I tried to install sdocbook-xml... for some reason now it worked. So now that all the sdocbook\* docbook\* and xmlcatmgr\* ports were installed, I tried to install pidgin, guess what, this time it got stuck on *scrollkeeper* telling that the file catalog.ports is missing some entry. Luckily, I still had that _catalog.ports file so I renamed the freshly created by xmlcatmgr, catalog.ports file and then renamed _catalog.ports to be the catalog.ports instead of the fresh one... That made scrollkeeper install successfully. Only after all that could I install net-im/pidgin. I'm not sure if someone actually will need this guide because it seems like I had something very unusual going on, but who knows. ---------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22d026f00710112141h1f2d14d9r405d544af98bcf41>