Hi James,All,
So regarding this Qs below, currently we are using yum 3.22 version, so
as per your earlier suggestion, I am able to set the repo directory, through,
repo.setAttribute('_dir_setup_pkgdir', package_mailbox)
So this works fine on yum 3.22 version.
Now the Qs is, if we upgrade to yum 3.2.24, would be still be able to set
attribute-->dir_setup_pkgdir or not.
Please let me know.
thanks,
SK
On Tue, 2009-09-22 at 18:32 -0700, Creative Innovative wrote:
> Hi James/All,
>
> I had sent an email sometime back, regarding NOT being able to repo's
> package directory in yum-3.2.22.
>
> James Antill had replied back with 2 options below.
>
> In the email below, you have mentioned
> 1) For just a local hack, you could just still override the
> '_dir_setup_pkgdir' value.
> Qs-->> How can I do this in YUM plugin.
> 2) If you want it to be writable again, it's possible but a bit of
> work, open
> an RFE ticket in BZ or trac.
> Qs--->>> Has this been already fixed in newer version of YUM. Please
> let me know, if this issue is still there.
Yes, this is listed in:
http://yum.baseurl.org/wiki/whatsnew/3.2.24
--
James Antill <ja...@fedoraproject.org>
Fedora
--- On Wed, 9/23/09, yum-devel-requ...@lists.baseurl.org
<yum-devel-requ...@lists.baseurl.org> wrote:
From: yum-devel-requ...@lists.baseurl.org <yum-devel-requ...@lists.baseurl.org>
Subject: Yum-devel Digest, Vol 66, Issue 24
To: yum-devel@lists.baseurl.org
Date: Wednesday, September 23, 2009, 5:07 PM
Send Yum-devel mailing list submissions to
yum-devel@lists.baseurl.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.baseurl.org/mailman/listinfo/yum-devel
or, via email, send a message with subject or body 'help' to
yum-devel-requ...@lists.baseurl.org
You can reach the person managing the list at
yum-devel-ow...@lists.baseurl.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yum-devel digest..."
Today's Topics:
1. Re: [PATCH] Use basic string matching/replacing instead of
regexps where appropriate. (James Antill)
2. Re: Fw: Yum-devel Digest, Vol 63, Issue 3 (James Antill)
3. [PATCH] Don't traceback on baseurl only repos. which have
network failures, BZ 525094 (James Antill)
4. Re: [PATCH] Don't traceback on baseurl only repos. which have
network failures, BZ 525094 (Seth Vidal)
5. Re: Yum-devel Digest, Vol 63, Issue 3 (Creative Innovative)
----------------------------------------------------------------------
Message: 1
Date: Wed, 23 Sep 2009 09:22:04 -0400
From: James Antill <ja...@fedoraproject.org>
Subject: Re: [Yum-devel] [PATCH] Use basic string matching/replacing
instead of regexps where appropriate.
To: yum development <yum-devel@lists.baseurl.org>
Message-ID: <1253712124.28837.0.ca...@code.and.org>
Content-Type: text/plain; charset="UTF-8"
On Wed, 2009-09-23 at 00:34 +0300, Ville Skytt? wrote:
> On Tuesday 22 September 2009, James Antill wrote:
> > On Tue, 2009-09-22 at 23:04 +0300, Ville Skytt? wrote:
> > > + return 'bin/' in filename or filename.startswith('/etc/') or \
> > > + filename == '/usr/lib/sendmail'
> >
> > Could you do these as:
> >
> > if 'bin/' in filename:
> > return True
> > if filenam.startswith('/etc/'):
> > return True
> > if filename == '/usr/lib/sendmail':
> > return True
> > return False
>
> Sure, revised patch attached.
>
> > ...also have you tested these with unicode and str?
>
> Yes, on Fedora 11 (Python 2.6).
Pushed, thanks.
--
James Antill <ja...@fedoraproject.org>
Fedora
------------------------------
Message: 2
Date: Wed, 23 Sep 2009 09:25:35 -0400
From: James Antill <ja...@fedoraproject.org>
Subject: Re: [Yum-devel] Fw: Yum-devel Digest, Vol 63, Issue 3
To: Creative Innovative <innovativ...@yahoo.com>
Cc: yum-devel@lists.baseurl.org
Message-ID: <1253712335.28837.2.ca...@code.and.org>
Content-Type: text/plain
On Tue, 2009-09-22 at 18:32 -0700, Creative Innovative wrote:
> Hi James/All,
>
> I had sent an email sometime back, regarding NOT being able to repo's
> package directory in yum-3.2.22.
>
> James Antill had replied back with 2 options below.
>
> In the email below, you have mentioned
> 1) For just a local hack, you could just still override the
> '_dir_setup_pkgdir' value.
> Qs-->> How can I do this in YUM plugin.
> 2) If you want it to be writable again, it's possible but a bit of
> work, open
> an RFE ticket in BZ or trac.
> Qs--->>> Has this been already fixed in newer version of YUM. Please
> let me know, if this issue is still there.
Yes, this is listed in:
http://yum.baseurl.org/wiki/whatsnew/3.2.24
--
James Antill <ja...@fedoraproject.org>
Fedora
------------------------------
Message: 3
Date: Wed, 23 Sep 2009 10:27:16 -0400
From: James Antill <ja...@and.org>
Subject: [Yum-devel] [PATCH] Don't traceback on baseurl only repos.
which have network failures, BZ 525094
To: yum-devel@lists.baseurl.org
Cc: James Antill <ja...@and.org>
Message-ID: <1253716036-417-1-git-send-email-ja...@and.org>
---
yum/yumRepo.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/yum/yumRepo.py b/yum/yumRepo.py
index d860ef9..daf8095 100644
--- a/yum/yumRepo.py
+++ b/yum/yumRepo.py
@@ -798,7 +798,7 @@ class YumRepository(Repository, config.RepoConf):
)
except URLGrabError, e:
errstr = "failed to retrieve %s from %s\nerror was %s" %
(relative, self.id, e)
- if self.mirrorurls:
+ if hasattr(self, 'mirrorurls'):
errstr +="\n You could try running: yum clean
expire-cache"
errstr +="\n To get a new set of mirrors."
if e.errno == 256:
--
1.6.2.5
------------------------------
Message: 4
Date: Wed, 23 Sep 2009 10:36:04 -0400 (EDT)
From: Seth Vidal <skvi...@fedoraproject.org>
Subject: Re: [Yum-devel] [PATCH] Don't traceback on baseurl only
repos. which have network failures, BZ 525094
To: yum development <yum-devel@lists.baseurl.org>
Cc: James Antill <ja...@and.org>
Message-ID:
<alpine.lfd.2.00.0909231034150.20...@localhost.localdomain>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Wed, 23 Sep 2009, James Antill wrote:
> ---
> yum/yumRepo.py | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/yum/yumRepo.py b/yum/yumRepo.py
> index d860ef9..daf8095 100644
> --- a/yum/yumRepo.py
> +++ b/yum/yumRepo.py
> @@ -798,7 +798,7 @@ class YumRepository(Repository, config.RepoConf):
> )
> except URLGrabError, e:
> errstr = "failed to retrieve %s from %s\nerror was %s" %
>(relative, self.id, e)
> - if self.mirrorurls:
> + if hasattr(self, 'mirrorurls'):
> errstr +="\n You could try running: yum clean
>expire-cache"
> errstr +="\n To get a new set of mirrors."
why not just define: self.mirrorurls = [] in __init__() of YumRepository?
Same result and we don't have to remember that mirrorurls may not be
present.
-sv
------------------------------
Message: 5
Date: Wed, 23 Sep 2009 10:06:57 -0700 (PDT)
From: Creative Innovative <innovativ...@yahoo.com>
Subject: Re: [Yum-devel] Yum-devel Digest, Vol 63, Issue 3
To: yum-devel@lists.baseurl.org
Message-ID: <137971.39220...@web65308.mail.ac2.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello Folks,
?
?I had sent an email sometime back, regarding NOT being able to repo's package
directory in yum-3.2.22.
? ? ?
? ? James Antill had replied back with 2 options below.
? ? ?
? ? In the email below, you have mentioned
? ? 1) For just a local hack, you could just still override the
'_dir_setup_pkgdir' value.
? ? Qs-->> How can I do this in YUM plugin.
? ? 2) If you want it to be writable again, it's possible but a bit of work,
open
? ? an RFE ticket in BZ or trac.
? ? Qs--->>> Has this been already fixed in newer version of YUM. Please let me
know, if this issue is still there.
? ? Thanks,
? ? ?
? ? Sudha
--- On Thu, 6/4/09, yum-devel-requ...@lists.baseurl.org
<yum-devel-requ...@lists.baseurl.org> wrote:
From: yum-devel-requ...@lists.baseurl.org <yum-devel-requ...@lists.baseurl.org>
Subject: Yum-devel Digest, Vol 63, Issue 3
To: yum-devel@lists.baseurl.org
Date: Thursday, June 4, 2009, 12:00 PM
Send Yum-devel mailing list submissions to
??? yum-devel@lists.baseurl.org
To subscribe or unsubscribe via the World Wide Web, visit
??? http://lists.baseurl.org/mailman/listinfo/yum-devel
or, via email, send a message with subject or body 'help' to
??? yum-devel-requ...@lists.baseurl.org
You can reach the person managing the list at
??? yum-devel-ow...@lists.baseurl.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Yum-devel digest..."
Today's Topics:
???1. Re: Unable to set repo attribute pkgdir, using YUM Plugin
? ? ? (James Antill)
???2. Re: group DB (Florian Festi)
----------------------------------------------------------------------
Message: 1
Date: Wed, 03 Jun 2009 09:37:55 -0400
From: James Antill <ja...@fedoraproject.org>
Subject: Re: [Yum-devel] Unable to set repo attribute pkgdir, using
??? YUM Plugin
To: yum development <yum-devel@lists.baseurl.org>
Message-ID: <1244036275.18685.73.ca...@code.and.org>
Content-Type: text/plain
On Tue, 2009-06-02 at 17:33 -0700, Creative Innovative wrote:
> Hi Folks,
>
> I am using yum-3.2.22 version.
>
> I have modified the downloadonly.py YUM plugin, that comes with
> yum-utils.
>
> def postreposetup_hook(conduit):
>? ???package_mailbox = conduit.confString('main', 'package_mailbox',
> '/var/pkg_mailbox')
>? ???print 'setting pkgdir=%s' % package_mailbox
>? ???repos = conduit.getRepos();
>? ???list = repos.listEnabled();
>
>? ???for repo in list:
>? ? ? ???repo.setAttribute('pkgdir', package_mailbox)
>
> When the above plugin runs, it quits with below error,
Yes, it was changed in commit cea34c86cc5142effa3b33fce1a62dff1d8d2bc0.
It was generally assumed to be a readonly attribute. For just a local
hack, you could just still override the '_dir_setup_pkgdir' value. If
you want it to be writable again, it's possible but a bit of work, open
an RFE ticket in BZ or trac.
--
James Antill <ja...@fedoraproject.org>
Fedora
------------------------------
Message: 2
Date: Wed, 03 Jun 2009 17:33:00 +0200
From: Florian Festi <ffe...@redhat.com>
Subject: Re: [Yum-devel] group DB
To: yum development <yum-devel@lists.baseurl.org>
Message-ID: <4a2697ac.8030...@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi everybody!
I very much appreciate the effort to improve the handling of groups in
yum. Nevertheless I think this effort is too short sighted. The
mechanisms we use to handle packages still date back to the time where
Fedora? had 1500 packages. We've see a growth (in number of packages) by
a factor ten since then and I expect another factor ten soonish. I
belief it is time to sit back and rethink the whole package selection
topic from the beginning. And while better "group" (what ever this
means) handling will be part of it it surely will not be sufficient to
solve the problems we are currently running into.
Right now we mix several things in the comps groups:
1. Grouping similar thing so users can select the ones he likes (Office
applications, Browsers, Games, ...)
2. Preselected installation patterns with one of each kind (GNOME, KDE)
3. Offer related packages that the user might also be interested.
4. Hide packages that the user is most likely not interested in (libs,
system core)
5. Add a more powerful selection layer (conditionals - mainly for
language support) (anaconda only)
Additionally to mixing thinks up comps is not scaling with the number of
packages.
Right now we only have 64 groups (when not counting the language
groups). This is simply not enough to structure 10k packages and surely
not enough for 100k. So IMHO we need to think how we can further
decentralize the grouping process and encourage people? to take care of
special application domains.
Another area of great pain is language support. There are hundreds of
packages waiting to be split up by language if there only was a way to
handle the huge amount of new sub packages (yes, we'll reach the 100k
packages much faster if this happens).
Another thing that has been silently shifting is the ration between the
distribution and the typical installation. While it used to be
(guessing) 800/1500 it is now 1500/15000. The burden of the meta data is
getting heavier and heavier compared to the actual install data. This is
probably not becoming critical soon but something we should keep an eye on.
But back to the package selection: IMHO we need to reinvent and
reimplement the package selection from scratch within the next two years
- the earlier the better. First step should be collecting all the use
cases and finding out what level of control is desirable for the
different meta data pieces.
Florian
------------------------------
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
End of Yum-devel Digest, Vol 63, Issue 3
****************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.baseurl.org/pipermail/yum-devel/attachments/20090923/1b04b82c/attachment.htm>
------------------------------
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
End of Yum-devel Digest, Vol 66, Issue 24
*****************************************
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
