Dmitry,
I pulled my hair out trying to chase down why the local repository on
my 10.3
server exploded after recent updates. Looks like the latest updates to
X11:/Enlightenment/openSUSE_11.0/ do not play well with createrepo.
Specifically, after recent updates (~ 300 packages), when I went to
update my
local rpm repository, createrepo went nuts:
[22:59 nirvana:/home/backup/rpms] # createrepo --update -d openSUSE_11.0
(process:28795): GLib-WARNING **: GError set over the top of a previous GError
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before
it's set.
The overwriting error message was: Parsing other.xml error: PCDATA invalid Char
value 27
(process:10597): GLib-WARNING **: GError set over the top of a previous GError
or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before
it's set.
The overwriting error message was: Parsing other.xml error: Entity 'lt' not
defined
(process:10597): GLib-WARNING **: GError set over the top of a previous GError
or uninitialized memory. This indicates a bug in
someone's code. You must ensure an error is NULL before it's set.
The overwriting error message was: Parsing other.xml
error: Entity 'gt' not defined
<snip>
Saving Primary metadata
Saving file lists metadata
Saving other metadata
Traceback (most recent call last):
File "/usr/share/createrepo/genpkgmetadata.py", line 724, in <module>
main(sys.argv[1:])
File "/usr/share/createrepo/genpkgmetadata.py", line 648, in main
mdgen.doRepoMetadata()
File "/usr/share/createrepo/genpkgmetadata.py", line 321, in doRepoMetadata
dumpMetadata.repoXML(reporoot, self.cmds)
File "/usr/share/createrepo/dumpMetadata.py", line 854, in repoXML
rp.getOtherdata(complete_path, csum)
File "/usr/lib64/python2.5/site-packages/sqlitecachec.py", line 57, in
getOtherdata
self.repoid))
TypeError: Parsing other.xml error: PCDATA invalid Char value 27
After exhausting all possibilities of what could have gone wrong with
python
updates, yum-metaparser-data, etc... I began checking the repository packages
and found that one or more x86_64 packages were causing the problem. Removing
the last hundred or so packages and running create repo against the individual
packages, the following was the first problem package I found:
exchange-20100103_r44860-4.1.x86_64.rpm
... and guess who that led me to??
I'm sorry I don't know what is actually causing the packages to blow up
in
createrepo, but I can confirm they do. As a test, just put the above package in
a directory and run createrepo --update -d 'dirname' against it and watch the
fireworks.
( That may also explain some of the weirdness I am seeing with the
latest E17 I
have installed as well ;-)
If you can, please take a look at the packages in the
X11:/Enlightenment/openSUSE_11.0/ repo and see if you can figure out what is
going on. Let me know if you need any help testing the results and I'm happy to
give it a go. Also, if you need more info, just let me know what you want and
I'll get if for you. The server hosting the local repository where the explosion
occurred is just a plain-jane openSUSE 10.3 x86_64 box that handles the local
repositories I have for 11.0, 11.1 and 11.2.
I know something is fishy. I've hosted the local repos for years and
this is
the first explosion I've experienced..... Good luck :p
p.s. I didn't know whether or not this should go across the list, but I also
didn't know if others on the list help Dmitry maintain the Enlightenment
repositories for openSuSE. So for completeness I have posted it here as well. If
it shouldn't be here, I apologize, just hit the Del key. Just wanted to make
sure that all who may be able to help resolve the issue were in the loop.
Thanks.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
