Login | Register
My pages Projects Community openCollabNet

Discussions > users > Re: up2date --get fails

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

current
Discussion topic

2020-03-13: This site is going to be decommissioned and shut down very soon. Please copy and archive any data you wish to keep ASAP

Back to topic list

Re: up2date --get fails

Reply

Author theslack
Full name Jack Neely
Date 2005-04-09 14:25:12 PDT
Message Trevor,

Thanks for the report.

You have successfully discovered a new API call. This will probably
show up with the 1.7.x devel series now that I know about it.

BTW, if you nodeps/force installs of packages that conflict or have
other dependancy errors you will most likely get your RPM database in
an inconsistant state to the point that up2date/yum will not be able
to update your system at all.

Jack

On Apr 8, 2005 11:23 AM, Trevor Astrope <astrope at tabbweb dot com> wrote:
> Is it possible to use the --get option with up2date and current? These
> are the versions of up2date and current I'm using:
>
> up2date-4.2.57-2
> current-1.6.0-1
>
> I get the error below when I try and use --get to retrieve a package
> without solving dependencies...
>
> bash-2.05b# up2date --get maildrop
>
> Fetching all package list for channel: rhel-i386-es-3...
> Traceback (most recent call last):
> File "/usr/sbin/up2date", line 1174, in ?
> sys.exit(main() or 0)
> File "/usr/sbin/up2date", line 683, in main
> return getPackages(pkgNames)
> File "/usr/sbin/up2date", line 944, in getPackages
> progressCallback = wrapperUtils.percent)
> File "rhnPackageInfo.py", line 276, in getAllAvailableAllAr​chPackageList
> File "rhnPackageInfo.py", line 215, in allAvailablePackageList
> File "rpcServer.py", line 379, in doCall
> up2date_client.up2da​teErrors.Communicati​onError: Error communicating with
> server. The message was:
> Not Found
>
> I have some packages with conflicts that I need to install manually with
> rpm --nodeps.
>
> The strange thing above is it is looking for the package in the
> rhel-i386-es-3 channel, but the package is in my custom-i386-es-3 channel.
> However, the --get option fails even if I try and get a package in the
> rhel-i386-es-3 channel.
>
> Here is what is in the current logs...
>
> Apr 08 11:12:05 Current v1.6.0 starting up
> Apr 08 11:12:05 Inside Current accesshandler
> Apr 08 11:12:05 /XMLRPC/$RHN/rhel-i​386-es-3/listAllPack​ages/20050406154814
> Apr 08 11:12:05 /usr/share/current/a​uth.py:isValid({})
>
> Besides the --get, up2date is working fine and I can list download and
> update packages.
>
> Any help is appreciated.
>
> Thanks,
>
> Trevor
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
> For additional commands, e-mail: users-help at current dot tigris dot org
>
>

--------------------​--------------------​--------------------​---------
To unsubscribe, e-mail: users-unsubscribe@cu​rrent.tigris.org
For additional commands, e-mail: users-help at current dot tigris dot org

« Previous message in topic | 2 of 4 | Next message in topic »

Messages

Show all messages in topic

up2date --get fails Trevor Astrope <astrope at tabbweb dot com> Trevor Astrope <astrope at tabbweb dot com> 2005-04-08 08:23:59 PDT
     Re: up2date --get fails theslack Jack Neely 2005-04-09 14:25:12 PDT
         Re: up2date --get fails Trevor Astrope <astrope at tabbweb dot com> Trevor Astrope <astrope at tabbweb dot com> 2005-04-09 16:11:18 PDT
             Re: up2date --get fails =?ISO-8859-1?Q?S=E9bastien_BLAISOT?= <sebastien at blaisot dot org> =?ISO-8859-1?Q?S=E9bastien_BLAISOT?= <sebastien at blaisot dot org> 2005-04-10 02:17:26 PDT
Messages per page: