Bug 15344 - "dnf upgrade" failure
Summary: "dnf upgrade" failure
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 4.3.1
Hardware: x86 Multiple
: Undecided normal
Target Milestone: 0.0.0
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2024-01-13 06:54 UTC by Michael Opdenacker
Modified: 2024-01-13 07:07 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Opdenacker 2024-01-13 06:54:05 UTC
I'm making binary package update tests on Nanbield.
No problem with an ipk package feed. If I remember correctly:

> opkg update
> opkg upgrade

I'm running this from a Nanbield 4.3.1 image, using feeds generated on another machine with the tip of the "nanbield" branch.

If I switch to
PACKAGE_CLASSES = "package_rpm"

If can't seem to be able to do the same thing:

> dnf upgrade

OE Remote Repo:8000                            0.0  B/s |   0  B     00:00                                                                                                                              
Error: Failed to download metadata for repo 'oe-remote-repo8000': Cannot download repomd.xml: Empty mirrorlist and no basepath specified!
Ignoring repositories: oe-remote-repo8000
Dependencies resolved.
Nothing to do.
Complete!

My http server doesn't even receive any request!

Here are the contents of /etc/yum.repos.d/oe-remote-repo8000.repo:

[oe-remote-repo8000]
name=OE Remote Repo:8000
baseurl=192.168.1.34:8000
gpgcheck=0

However the following command works:

> wget http://192.168.1.34:8000/repodata/repomd.xml

On Fedora 39, I can just run "dnf upgrade" and everything works. I'm starting to suspect that something is missing in the rpm related files we generate.

You may assign this bug to me.

Cheers
Michael
Comment 1 Michael Opdenacker 2024-01-13 07:07:53 UTC
My bad, it turns out I was missing "http://" in PACKAGE_FEED_URIS
Closing the bug.