On Thu, 5 Jul 2007, Panu Matilainen wrote:
In practise it means a custom sys.excepthook couldn't be
called while rpmdb/iterators are active. Not a problem for yum where the
output is text-based anyway (the traceback can be printed), but for things
like pirut which probably have their own handler
seth vidal wrote:
On Thu, 2007-07-05 at 03:04 +0530, Debarshi 'Rishi' Ray wrote:
Please find attached a patch to incorporate the persistent
enable/disable of repositories by editing the .repo files.
Repositories mentioned in yum.conf are still not supported.
This is done using the following
Sorry I did notice this before, but these problems in ConfigParser
seem to be well discussed at
http://wiki.python.org/moin/ConfigParserShootout
I will try to cook something together there there fits into the current yum
config code, so it can save stuff in the right place and order without
In any case I will re-write this using some other parsing module. Let me try.
Done, using cfgparse
(http://pages.cs.wisc.edu/~param/software/cfgparse/) which preserves
the ordering of the options and the comments.
Good thing is that cfgparse provides an additional interface backward
compatible
On Thu, Jul 05, 2007 at 03:54:04AM -0500, Michael E Brown wrote:
James and I were talking on jabber about where things should go. He
suggested putting things in a single keyring for all of yum
in /var/cache/yum somewhere. This sounds reasonable to me. Any other
/var/cache doesnt seem like
As a result of the depsolving bugs we've been seeing I added in a
temporary
ts.check() debug option. If you're running yum from the cli and you set
rpm_check_debug=True in your yum.conf then it will run an rpm ts.check()
before it runs the transaction test. If it finds any problems it will
bail
Debarshi 'Rishi' Ray wrote:
Sorry I did notice this before, but these problems in ConfigParser
seem to be well discussed at
http://wiki.python.org/moin/ConfigParserShootout
I will try to cook something together there there fits into the
current yum
config code, so it can save stuff in the
On Thu, Jul 05, 2007 at 07:47:01AM -0400, James Bowes wrote:
On Thu, Jul 05, 2007 at 03:54:04AM -0500, Michael E Brown wrote:
James and I were talking on jabber about where things should go. He
suggested putting things in a single keyring for all of yum
in /var/cache/yum somewhere. This
On Thu, Jul 05, 2007 at 09:26:51AM -0400, seth vidal wrote:
On Thu, 2007-07-05 at 03:54 -0500, Michael E Brown wrote:
/var/cache doesnt seem like a good place to be putting keyrings. I
thought that the intent behind /var/cache/ was that you could delete it
and things would still work?
On Thu, 2007-07-05 at 17:36 +0200, Terje Røsten wrote:
seth vidal
As a result of the depsolving bugs we've been seeing I added in a
temporary
ts.check() debug option. If you're running yum from the cli and you set
rpm_check_debug=True in your yum.conf then it will run an rpm ts.check()
seth vidal
As a result of the depsolving bugs we've been seeing I added in a
temporary
ts.check() debug option. If you're running yum from the cli and you set
rpm_check_debug=True in your yum.conf then it will run an rpm ts.check()
before it runs the transaction test. If it finds any problems
On Thu, Jul 05, 2007 at 09:33:56AM -0400, James Bowes wrote:
On Thu, Jul 05, 2007 at 09:26:51AM -0400, seth vidal wrote:
Next question: are you implementing this in a way that is compatible
with the way that SUSE signs repos? I just implemented signed repos on
my repos and would hate to
Tim Lauridsen wrote:
Debarshi 'Rishi' Ray wrote:
In any case I will re-write this using some other parsing module.
Let me try.
Done, using cfgparse
(http://pages.cs.wisc.edu/~param/software/cfgparse/) which preserves
the ordering of the options and the comments.
Good thing is that cfgparse
It's a little concerning that there's only one release (0.1) and that
was in 2004 and apparently nothing since. I wonder if it's worth sort
of taking and building on within yum proper rather than adding the
dependency.
http://cfgparse.sourceforge.net/
Mea culpa.
I posted an older link. The
On Thu, 2007-07-05 at 15:10 +0530, Debarshi 'Rishi' Ray wrote:
In any case I will re-write this using some other parsing module. Let me
try.
Done, using cfgparse
(http://pages.cs.wisc.edu/~param/software/cfgparse/) which preserves
the ordering of the options and the comments.
It's a
On Wed, 2007-07-04 at 17:45 -0400, seth vidal wrote:
On Thu, 2007-07-05 at 03:04 +0530, Debarshi 'Rishi' Ray wrote:
Please find attached a patch to incorporate the persistent
enable/disable of repositories by editing the .repo files.
Repositories mentioned in yum.conf are still not
On Thu, Jul 05, 2007 at 11:03:20AM -0500, Michael E Brown wrote:
Anyways, the latest betas for zypper (opensuse pkg manager) have the
things I've asked for (I still need to test it... :)
Mailing list and project page here:
http://en.opensuse.org/Libzypp
That explains why I didn't see it in
Pardon me if I did not understand what you said.
Look fine, the only issue to solve is to keep track of of witch section
(repos) is stored in witch .repo file, so if on repo is
enabled/disabled, all other section was to written to the same file.
in system-config-repo is use some dictionaries to
It's a little concerning that there's only one release (0.1) and that
was in 2004 and apparently nothing since. I wonder if it's worth sort
of taking and building on within yum proper rather than adding the
dependency.
I posted an older link. The latest one is above, and the latest
19 matches
Mail list logo
