FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > CentOS > CentOS Development

 
 
LinkBack Thread Tools
 
Old 12-12-2008, 11:56 PM
Karanbir Singh
 
Default updated yum packages are now available in c5-testing

The following packages have been updated in the testing repo :
./5/testing/SRPMS/yum-utils-1.1.16-13.el5.centos.src.rpm
./5/testing/SRPMS/yum-3.2.19-18.el5.centos.src.rpm


./5/testing/x86_64/RPMS/yum-tmprepo-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-keys-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-upgrade-helper-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-changelog-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-fastestmirror-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-protectbase-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-merge-conf-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-tsflags-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-list-data-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-verify-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-kmod-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-protect-packages-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-versionlock-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-3.2.19-18.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-utils-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-NetworkManager-dispatcher-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-kernel-module-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-updateonboot-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-refresh-updatesd-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-downloadonly-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-security-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-allowdowngrade-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-aliases-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-priorities-1.1.16-13.el5.centos.noarch.rpm
./5/testing/x86_64/RPMS/yum-filter-data-1.1.16-13.el5.centos.noarch.rpm



./5/testing/i386/RPMS/yum-tmprepo-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-keys-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-upgrade-helper-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-changelog-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-fastestmirror-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-protectbase-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-merge-conf-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-tsflags-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-list-data-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-verify-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-kmod-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-protect-packages-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-versionlock-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-3.2.19-18.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-utils-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-NetworkManager-dispatcher-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-kernel-module-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-updateonboot-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-refresh-updatesd-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-downloadonly-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-security-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-allowdowngrade-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-aliases-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-priorities-1.1.16-13.el5.centos.noarch.rpm
./5/testing/i386/RPMS/yum-filter-data-1.1.16-13.el5.centos.noarch.rpm


test these on non-production machines only for now. And all feedback is
appreciated.

keepcache is now turned on, how does this impact everyone's yum setups ?

--
Karanbir Singh : http://www.karan.org/ : 2522219@icq
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 12-22-2008, 08:34 PM
Dag Wieers
 
Default updated yum packages are now available in c5-testing

On Mon, 22 Dec 2008, James Antill wrote:

> On Mon, 2008-12-22 at 12:29 -0800, Akemi Yagi wrote:
>> On Fri, Dec 12, 2008 at 4:56 PM, Karanbir Singh <mail-lists@karan.org> wrote:
>
> [...]
>> File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 470,
>> in _sql_pkgKey2po
>> pkg = self._packageByKey(repo, ob['pkgKey'])
>> File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 413,
>> in _packageByKey
>> po = self.pc(repo, cur.fetchone())
>> File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 68,
>> in __init__
>> self._read_db_obj(db_obj)
>> File "/usr/lib/python2.4/site-packages/yum/sqlitesack.py", line 94,
>> in _read_db_obj
>> setattr(self, item, _share_data(db_obj[item]))
>> TypeError: unsubscriptable object
>
> This is more understandable upstream by:
>
> http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=3120676a73219b018d 317d8adaac0d858d751a3b;hp=54bd2c6eebf6be6b2596e255 38bff6b35e34c443
>
> ...which gives a "nice" message. There is also a change to
> yum-metadata-parser, which should work around the problem in atrpms.
> The short term. fixes are:
>
> 1. Don't use atrpms.
>
> 2. Use "yum clean metadata"

Can you be a little bit more specific ? Is there a thread describing the
issue ? Is there going to be a real fix for it ?

I really don't feel good with this patch. The error does not indicate
to a user that a "yum clean metadata" resolves their problem.

If we are going to have all our users that use atrpms go through this by
default, then I think we should avoid it at all cost.

--
-- dag wieers, dag@centos.org, http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 12-22-2008, 10:04 PM
Dag Wieers
 
Default updated yum packages are now available in c5-testing

On Mon, 22 Dec 2008, James Antill wrote:

> On Mon, 2008-12-22 at 23:57 +0200, Axel Thimm wrote:
>> On Mon, Dec 22, 2008 at 10:34:55PM +0100, Dag Wieers wrote:
>> > Can you be a little bit more specific ? Is there a thread describing the
>> > issue ? Is there going to be a real fix for it ?
>
> The BZ I can easily find is RH 465898:
>
> [https://bugzilla.redhat.com/show_bug.cgi?id=465898
> TypeError: 'NoneType' object is unsubscriptable error in
> sqlitesack.py:94:_read_db_obj (pkgId can't be found)]
>
> ...although I'm sure we discussed something with You or Axel at one
> point about multiple pkgId's in one repo.

It wasn't me. How can multiple pkgId's be in one repo ?


>From the bugzilla entries, I found this excerpt:

Ok, everytime I've seen this bug now it's someone using an atrpms repo.
It's possible they are doing something weird with multiple packages
with the same pkgId, combined with their desire to ship only .xml
metadata might produce these kinds of errors.

I can add that I would be happy to use the latest and greatest createrepo
if those newer versions would work with older distributions (namely, older
python versions) and if they can produce metadata that works with older
yum/apt releases as well. (Also on RHEL2.1 and RH7.3 systems)

In the past that was not always the case and we are not all using the
latest Fedora for creating and hosting repo metadata.


>> I also don't understand the patch mentioned above. What at ATrpms
>> upsets the new yum that way?
>
> The yum patch is to stop the backtraces, and give a warning to the user
> that the repo. is currently broken.

Well, I wonder why you think that the warning is better than the
backtrace if the user does not understand what the warning means or who
they should talk to and yum would still fail to work as they expect.

--
-- dag wieers, dag@centos.org, http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 
Old 12-22-2008, 11:02 PM
Dag Wieers
 
Default updated yum packages are now available in c5-testing

On Mon, 22 Dec 2008, James Antill wrote:


On Tue, 2008-12-23 at 00:04 +0100, Dag Wieers wrote:

I can add that I would be happy to use the latest and greatest createrepo
if those newer versions would work with older distributions (namely, older
python versions) and if they can produce metadata that works with older
yum/apt releases as well. (Also on RHEL2.1 and RH7.3 systems)


AFAIK noone has any plans to backport any version of createrepo to work
with RHEL-2.1 or older.


There was (and still is on RHEL5) a createrepo with the -n option of which
the _only_ purpose is to support those distributions. Now Seth already
made clear that the support was broken in later releases (but the option
still worked) and he had no interest to revive it. So I have not tried out
any new versions (and so no sqlite metadata...).


But it was unfortunate that when repomd was designed, it was not designed
for supporting a distribution that was still more than 4 years from being
unsupported by Red Hat. And that despite our needs, the repomd XML
format was nog slightly changed (making Epoch tag optional). And that to
me is worrysome.


(repoview still has a bug, and my patch to support it was never applied)

Imagine creating a createrepo release *now* that would no longer support
the RPM quirks that ship with RHEL4. The lack of such backward
compatibility is what I have seen many times for basic infrastructure
(like eg. yum) on and on because development is only targetted to Fedora.




There is a nebulous plan to create a simple script² which can be used
on "older" releases, which will take the normal createrepo (without -d)
and just add the .sqlite files in.
How far back it'll go isn't clear yet (having not been written), but
I'd guess that without help from you RHEL-2.1 is probably not going to
be tested.


Well, I have send in bugreports and patches in the past with the only
result of having seen the bugreports been deleted (yes, not just closed)
and either no or little response that was helpful.


So if I sound a bit harsh on things, it's because there's some history
(and lost time/effort) attached


--
-- dag wieers, dag@centos.org, http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]_______________________________________________
CentOS-devel mailing list
CentOS-devel@centos.org
http://lists.centos.org/mailman/listinfo/centos-devel
 

Thread Tools




All times are GMT. The time now is 06:59 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org