Hi all,
I'm not sure which new package might have broken this; I think I succeeded after upgrading yum, but I can't be sure.
Here's the spewage.
Pungi:ERROR: Got an error from /usr/bin/repoview Pungi:ERROR: Traceback (most recent call last): File "/usr/bin/repoview", line 926, in <module> main() File "/usr/bin/repoview", line 923, in main Repoview(opts) File "/usr/bin/repoview", line 191, in __init__ packages = self.do_packages(repo_data, group_data, pkgnames) File "/usr/bin/repoview", line 554, in do_packages if self.has_changed(pkg_filename, checksum): File "/usr/bin/repoview", line 607, in has_changed scursor.execute(query) sqlite3.IntegrityError: column filename is not unique
Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Sqlite DBs complete Traceback (most recent call last): File "/usr/bin/pungi", line 195, in <module> main() File "/usr/bin/pungi", line 99, in main mypungi.doCreaterepo() File "/usr/lib/python2.5/site-packages/pypungi/__init__.py", line 636, in doCreaterepo self._makeMetadata(self.topdir, cachedir, compsfile, repoview=True, repoviewtitle=repoviewtitle) File "/usr/lib/python2.5/site-packages/pypungi/__init__.py", line 612, in _makeMetadata pypungi.util._doRunCommand(repoview, self.logger) File "/usr/lib/python2.5/site-packages/pypungi/util.py", line 36, in _doRunCommand raise OSError, "Got an error from %s: %s" % (command[0], err) OSError: Got an error from /usr/bin/repoview: Traceback (most recent call last): File "/usr/bin/repoview", line 926, in <module> main() File "/usr/bin/repoview", line 923, in main Repoview(opts) File "/usr/bin/repoview", line 191, in __init__ packages = self.do_packages(repo_data, group_data, pkgnames) File "/usr/bin/repoview", line 554, in do_packages if self.has_changed(pkg_filename, checksum): File "/usr/bin/repoview", line 607, in has_changed scursor.execute(query) sqlite3.IntegrityError: column filename is not unique
Any ideas?
TIA.
On Wed, 2009-02-18 at 09:10 -0700, William F. Acker WB2FLW +1 303 722 7209 wrote:
Hi all,
I'm not sure which new package might have broken this; I think Isucceeded after upgrading yum, but I can't be sure.
Here's the spewage.Pungi:ERROR: Got an error from /usr/bin/repoview Pungi:ERROR: Traceback (most recent call last): File "/usr/bin/repoview", line 926, in <module> main() File "/usr/bin/repoview", line 923, in main Repoview(opts) File "/usr/bin/repoview", line 191, in __init__ packages = self.do_packages(repo_data, group_data, pkgnames) File "/usr/bin/repoview", line 554, in do_packages if self.has_changed(pkg_filename, checksum): File "/usr/bin/repoview", line 607, in has_changed scursor.execute(query) sqlite3.IntegrityError: column filename is not unique
pretty sure it is b/c of the update to sqlite. The columns will probably need a rename in repoview. I'll check the changelogs on sqlite.
-sv
On Wed, 18 Feb 2009, seth vidal wrote:
On Wed, 2009-02-18 at 09:10 -0700, William F. Acker WB2FLW +1 303 722 7209 wrote:
Hi all,
I'm not sure which new package might have broken this; I think Isucceeded after upgrading yum, but I can't be sure.
Here's the spewage.Pungi:ERROR: Got an error from /usr/bin/repoview Pungi:ERROR: Traceback (most recent call last): File "/usr/bin/repoview", line 926, in <module> main() File "/usr/bin/repoview", line 923, in main Repoview(opts) File "/usr/bin/repoview", line 191, in __init__ packages = self.do_packages(repo_data, group_data, pkgnames) File "/usr/bin/repoview", line 554, in do_packages if self.has_changed(pkg_filename, checksum): File "/usr/bin/repoview", line 607, in has_changed scursor.execute(query) sqlite3.IntegrityError: column filename is not unique
pretty sure it is b/c of the update to sqlite. The columns will probably need a rename in repoview. I'll check the changelogs on sqlite.
I back leveled sqlite on the build machine which didn't help. I know that's not conclusive since some packages such as Anaconda are downloaded from the repo and never cached. So, before putting the old sqlite into the repo, I checked to see the when I was last successful VS when I installed sqlite. It turns out that both yum and sqlite were installed on 2/5, and my last successful spin was on 2/8. I don't see any packages installed since them that are obviously connected to this problem.
BTW, Seth, how is one supposed to use the allowdowngrade plugin for yum. I tried yum --allow-downgrade localinstall sqlite*, with the result the same as if I didn't use the option. localupdate was no better. I had to fall back on "rpm -Uv --oldpackage sqlite*".
Thanks.
On Wed, 2009-02-18 at 14:35 -0700, William F. Acker WB2FLW +1 303 722 7209 wrote:
I back leveled sqlite on the build machine which didn't help. I knowthat's not conclusive since some packages such as Anaconda are downloaded from the repo and never cached. So, before putting the old sqlite into the repo, I checked to see the when I was last successful VS when I installed sqlite. It turns out that both yum and sqlite were installed on 2/5, and my last successful spin was on 2/8. I don't see any packages installed since them that are obviously connected to this problem.
I'm not sure if this is sqlite anymore - I've been mucking with it today. Oddly on rawhide here I can't make it happen.
BTW, Seth, how is one supposed to use the allowdowngrade plugin foryum. I tried yum --allow-downgrade localinstall sqlite*, with the result the same as if I didn't use the option. localupdate was no better. I had to fall back on "rpm -Uv --oldpackage sqlite*".
In most cases, you're not. allowdowngrade sometimes is just not working. It's a long story as to why but it is something that is being worked on - it's just not trivial.
-sv
On Wed, 2009-02-18 at 16:43 -0500, seth vidal wrote:
On Wed, 2009-02-18 at 14:35 -0700, William F. Acker WB2FLW +1 303 722 7209 wrote:
I back leveled sqlite on the build machine which didn't help. I knowthat's not conclusive since some packages such as Anaconda are downloaded from the repo and never cached. So, before putting the old sqlite into the repo, I checked to see the when I was last successful VS when I installed sqlite. It turns out that both yum and sqlite were installed on 2/5, and my last successful spin was on 2/8. I don't see any packages installed since them that are obviously connected to this problem.
I'm not sure if this is sqlite anymore - I've been mucking with it today. Oddly on rawhide here I can't make it happen.
ah ha! My sample size was too small. I found out what was causing the problem
somehow we had two packages VLGothic-fonts and vlgothic-fonts - repoview case normalizes for the .html files it makes - hence this problem. Fedora was not supposed to have those two pkgs - it was an oversight and that has been fixed. I'll also change repoview to not case normalize the filenames.
-sv
On Wed, 18 Feb 2009, seth vidal wrote:
On Wed, 2009-02-18 at 16:43 -0500, seth vidal wrote:
On Wed, 2009-02-18 at 14:35 -0700, William F. Acker WB2FLW +1 303 722 7209 wrote:
I back leveled sqlite on the build machine which didn't help. I knowthat's not conclusive since some packages such as Anaconda are downloaded from the repo and never cached. So, before putting the old sqlite into the repo, I checked to see the when I was last successful VS when I installed sqlite. It turns out that both yum and sqlite were installed on 2/5, and my last successful spin was on 2/8. I don't see any packages installed since them that are obviously connected to this problem.
I'm not sure if this is sqlite anymore - I've been mucking with it today. Oddly on rawhide here I can't make it happen.
ah ha! My sample size was too small. I found out what was causing the problem
somehow we had two packages VLGothic-fonts and vlgothic-fonts - repoview case normalizes for the .html files it makes - hence this problem. Fedora was not supposed to have those two pkgs - it was an oversight and that has been fixed. I'll also change repoview to not case normalize the filenames.
Hi again,
I haven't seen new fonts or a new version of repoview. Openoffice-langpack-jp requires either the old or new fonts, so I don't see how I could exclude them. How should I proceed?
TIA
On Wed, 18 Feb 2009, seth vidal wrote:
On Wed, 2009-02-18 at 16:43 -0500, seth vidal wrote:
On Wed, 2009-02-18 at 14:35 -0700, William F. Acker WB2FLW +1 303 722 7209 wrote:
I back leveled sqlite on the build machine which didn't help. I knowthat's not conclusive since some packages such as Anaconda are downloaded from the repo and never cached. So, before putting the old sqlite into the repo, I checked to see the when I was last successful VS when I installed sqlite. It turns out that both yum and sqlite were installed on 2/5, and my last successful spin was on 2/8. I don't see any packages installed since them that are obviously connected to this problem.
I'm not sure if this is sqlite anymore - I've been mucking with it today. Oddly on rawhide here I can't make it happen.
ah ha! My sample size was too small. I found out what was causing the problem
somehow we had two packages VLGothic-fonts and vlgothic-fonts - repoview case normalizes for the .html files it makes - hence this problem. Fedora was not supposed to have those two pkgs - it was an oversight and that has been fixed. I'll also change repoview to not case normalize the filenames.
The new repoview did the trick. On F9 and F10, the install media built quite nicely. I haven't installed from them yet, but I don't see any reason why there'd be a problem with that.
Thanks a gig!
buildsys@lists.fedoraproject.org
-
Seth Vidal -
William F. Acker WB2FLW +1 303 722 7209