Opened 10 years ago

Closed 10 years ago

#115 closed defect (fixed)

Package intended for a noarch architecture?

Reported by: ggamba Owned by:
Priority: major Milestone:
Component: rpm Version:
Severity: Keywords:
Cc:

Description

Running "yum update":

--> Esecuzione del controllo di transazione
---> Package python-pycurl.pentium4 0:7.19.5.1-1.oc00 will be installato
--> Risoluzione delle dipendenze completata

Dipendenze risolte

================================================================================

 Pacchetto          Arch          Versione               Repository        Dim.
================================================================================

Aggiornamento:
 urlgrabber         noarch        3.10.1-8.oc00          netlabs-rel      115 k
Installazioni per dipendenze:
 python-pycurl      pentium4      7.19.5.1-1.oc00        netlabs-rel      139 k

I confirm the update and:

Download dei pacchetti:
Running Transaction Check
Test di transazione in corso


Errore nel controllo transazione:
  package urlgrabber-3.10.1-8.oc00.noarch is intended for a noarch architecture

As you can imagine, I have "platform" file present in rpm configuration.

Change History (9)

comment:1 by Silvan Scherrer, 10 years ago

If I read the things right, you also need to have noarch in the platform file.

comment:2 by ggamba, 10 years ago

No problem trying, but I would wait for Lewis's comment, as I think he is the one who added:

http://trac.netlabs.org/rpm/wiki/RpmHowToEndUsers#Platformselectionforbinaries

comment:3 by Yuri Dario, 10 years ago

I have 'pentium4-OS/2-OS/2' in my platform file and it works.

comment:4 by ggamba, 10 years ago

I guess there is still something wrong here. "yum install python-pycurl" gives:

Attenzione: RPMDB modificato al di fuori di yum.
  Installazione     : python-pycurl-7.19.5.1-1.oc00.pentium4                1/1

Rpmdb checksum is invalid: dCDPT(pkg checksums)

And running it again:

C:\SCRIVANIA>yum install python-pycurl
Plugin abilitati:fastestmirror
Loading mirror speeds from cached hostfile
Impostazione processo di installazione
Il pacchetto python-pycurl-7.19.5.1-1.oc00.pentium4 è già installato e aggiornat
o all'ultima versione
Niente da fare

Maybe I should run rpm --rebuilddb?

comment:5 by Lewis Rosenthal, 10 years ago

Apparently, Trac does not allow for manually adding a cc to a ticket. I didn't realize this one was here, and you had mentioned my name, Gabriele. Sorry about that.

Silvan, I don't think noarch is necessary (at least I can't find a mention of it being required for other platforms).

Gabriele, as for the Rpmdb checksum is invalid: dCDPT(pkg checksums) error, please have a look at ticket #117. In my one VM, I unzipped rpm-4.8.1-20 over 4.8.1-22, and this seemed to avoid the message (which I do not think is a legitimate error). That said, repm --rebuilddb surely wouldn't hurt.

comment:6 by ggamba, 10 years ago

rpm --rebuilddb did not help, and I can't find rpm-4.8.1-20, only rpm-4.8.1-18. I'm afraid there is something wrong around, also considering http://trac.netlabs.org/rpm/ticket/116...

comment:7 by Silvan Scherrer, 10 years ago

@Gabriele: which issue is still open here? havin 2 different issues in one ticket is a bad idea, as loosing track is easy.

comment:8 by ggamba, 10 years ago

I reordered LIBPATH, that now looks

LIBPATH=.;C:\USR\LIB;C:\ECS\DLL;C:\EMX\DLL;C:\OS2\DLL;...

and this seems having fixed all the problems.

Honestly, I suspected that "C:\USR\LIB" had to be before "C:\ECS\DLL", but, as rpm-yum-bootstrap-1_3.wpi, that I repeatedly run trying to reinstall the rpm environment from scratch, did nothing to place "C:\USR\LIB" at the beginning of LIBPATH, I assumed that having it after "C:\ECS\DLL" was fine.

Note that all my experiments were on eCS 2.2 beta 2 machines, that had rpm environment in place since system installation, so it is possible that the wrong position of "C:\USR\LIB" in LIBPATH was inherited by the eCS installer.

Nevertheless, I expected that rpm-yum-bootstrap-1_3.wpi could detect and fix this problem. As it didn't, I assumed it was not a problem.

comment:9 by Silvan Scherrer, 10 years ago

Resolution: fixed
Status: newclosed

ok thx for letting us know. closing it

Note: See TracTickets for help on using tickets.