Re: Re:Re: trying to use

There is a new snapshot on the ftp server. I didn't update the web page
or send a freshmeat for this one - I'm going to try and work really hard
this weekend, and send out a 2.7 compatible snapshot on monday.

There are a number of minor (but crucial) bug fixes in this release:
1) naming error in sendClientResult() that would prevent sending any
files - the patch is to rename "tmp" to "tmpfile"

2) naming error in solvedeps() that would bomb any solvedeps call.
- patch is to rename chan_label to channels

3) There is a basic working Makefile now. make snapshot has always
worked - its how all the snapshots to date have been made. make archive
also - its how I did the 0.8.0 release.

Now there is a make install, which seems to do the right thing. It
includes provision for an install_root or BUILDROOT option for spec file
writing.

4) More updates for the 2.7 client handling - this code still doesn't
work yet, but should give an idea where we are going.



On Fri, 2001-12-07 at 12:07, [email protected] wrote:
> >The documentation may not be explicitly clear,
> but only 2.5 versions of 
> >up2date are supported at all. (2.5.4 was the
> last 2.5 released, and is
> >recommended)
> >
> The docs are clear, my message not.
> I have manually updated up2date to version 2.5.4
> because it does not work 2.7 and I got this
> dependency errors using 2.5.4 trying to update
> the machine.
> 
> >So 2.3 (which is what I think you are playing
> with) has a number of
> >differences from the 2.4 protocol, which is
> different still from the 2.5
> >protocol (2.5.4 is the fourth bug fix/minor
> feature update of the 2.5
> >client)
> 
> No I have manualy updated to 2.5.4 
> 
> >At present, I have no plans at all to support
> clients earlier than 2.5.
> >Since Red Hat release 2.7 clients backported to
> 6.2/7.0/7.1 releases of 
> >Red Hat, the question is whether to continue
> supporting 2.5 clients once
> >I have 2.7 support completed. I hope to
> complete that this weekend.
> >
> >Comments from users/ people planning on using
> current?
> 
> I think  there is no problem to support only new
> versions, but the question is when using the
> 2.5.4 (the supported version it can't resolve
> the dependencies to update the machine which I
> never updated before, the only rpms updated are
> the rhn_register and up2date-* python-* to make
> possible to use current)
> It get the list of packages, but get the error
> when trying to solve dependencies
> >
> >
> >On Fri, 2001-12-07 at 09:32, [email protected]
> wrote:
> >> I tring to use it now.
> >> I got an machine without any pdates (RH 7.0)
> >> 
> >> I have manually updated rhn_register (version
> >> that comes does not have the config file and
> use
> >> default RH server)
> >> 
> >> changed configs, rhn_register works.
> >> 
> >> I have mannualy updated up2date because the
> >> version that comes with 7.0 try to use a
> listall
> >> command that current does not support.
> >> 
> >> The it connected fine, get the list of
> packages,
> >> but it can sove dependencies :
> >> 
> >>
> ------------------------------------------------
> >> function = solvedep
> >> Dispatching: up2date.solvedep
> >> ./up2date.py:solvedep({'unknowns':
> >> ['liblber.so.1', 'libldap.so.1',
> 'liblber.so.1',
> >> 'libldap.so.1', 'l
> >> iblber.so.1', 'libldap.so.1', 'liblber.so.1',
> >> 'libldap.so.1', 'liblber.so.1',
> 'libldap.so.1',
> >> 'libcryp
> >> to.so.1', 'libssl.so.1', 'libcrypto.so.1',
> >> 'libssl.so.1', 'libcrypto.so.1',
> 'libssl.so.1',
> >> 'liblber.so
> >> .1', 'libldap.so.1', 'liblber.so.1',
> >> 'libldap.so.1', 'liblber.so.1',
> 'libldap.so.1',
> >> 'liblber.so.1', '
> >> libldap.so.1']})
> >>
> ./packagedb.py:getCompatibleChannels({'client_arch':
> >> 'i686', 'client_release': '7.0'})
> >> ./packagedb.py:_getCannonArch({'arch':
> 'i686'})
> >> ERROR: Recognized function up2date.solvedep
> blew
> >> up with undefined error
> >>   exception said: chan_label
> >>   params were: ('<?xml
> >>
> version="1.0"?>\012<params>\012<param>\012<value><struct>\012<member>\012<name>
> >>
> type</name>\012<value><string>REAL</string></value>\012</member>\012<member>\012<name>architecture</na
> >>
> me>\012<value><string>i686</string></value>\012</member>\012<member>\012<name>checksum</name>\012<valu
> >>
> e><string>91b2f4199d9fd3e9ba0fd4d4b6348003f4d48a07</string></value>\012</member>\012<member>\012<name>
> >>
> os_release</name>\012<value><string>7.0</string></value>\012</member>\012<member>\012<name>description
> >> </name>\012<value><string>7.0 running on
> >>
> i686</string></value>\012</member>\012<member>\012<name>syste
> >>
> m_id</name>\012<value><string>Current-ANONYMOUS</string></value>\012</member>\012<member>\012<name>ope
> >> rating_system</name>\012<value><string>Red
> Hat
> >>
> Linux</string></value>\012</member>\012<member>\012<nam
> >>
> e>profile_name</name>\012<value><string>wando.intranet.saisp.br</string></value>\012</member>\012<memb
> >>
> er>\012<name>fields</name>\012<value><array><data>\012<value><string>type</string></value>\012<value><
> >>
> string>operating_system</string></value>\012<value><string>checksum</string></value>\012<value><string
> >>
> >description</string></value>\012<value><string>os_release</string></value>\012<value><string>architec
> >>
> ture</string></value>\012<value><string>system_id</string></value>\012<value><string>profile_name</str
> >>
> ing></value>\012<value><string>username</string></value>\012</data></array></value>\012</member>\012<m
> >>
> ember>\012<name>username</name>\012<value><string>amorim</string></value>\012</member>\012</struct></v
> >> alue>\012</param>\012</params>\012',
> >>  ['liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'libcrypto.so.1',
> >>   'libssl.so.1',
> >>   'libcrypto.so.1',
> >>   'libssl.so.1',
> >>   'libcrypto.so.1',
> >>   'libssl.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1',
> >>   'liblber.so.1',
> >>   'libldap.so.1'])
> >> END OF POST
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> --------------------------------------
> >> Mensagem Enviada pelo WebMail Ecodigit
> >> http://www.ecodigit.com.br
> >-- 
> >Hunter Matthews                          Unix /
> Network Administrator
> >Office: BioScience 145/244               Duke
> Univ. Biology Department
> >Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779
> A5DB 8B09 F0F8 8438
> >Never take candy from strangers. Especially on
> the internet.
> >
> >
> >_______________________________________________
> >Current-server mailing list
> >[email protected]
> >http://lists.dulug.duke.edu/mailman/listinfo/current-server
> 
> 
> 
> 
> --------------------------------------
> Mensagem Enviada pelo WebMail Ecodigit
> http://www.ecodigit.com.br
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.