Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions projects/github.com/vmware/tdnf/package.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ distributable:
display-name: tdnf

versions:
github: vmware/tdnf
github: vmware/tdnf/releases

platforms: [linux] # rpm doesn't support darwin, and patching is a nightmare.

Expand Down Expand Up @@ -46,4 +46,17 @@ build:
provides:
- bin/tdnf

test: 'test "$(tdnf --version)" = "tdnf: {{version}}"'
test:
env:
RELEASE: '10'
ROOTFS: rocky-${RELEASE}-rootfs
script:
- run: 'test "$(tdnf --version)" = "tdnf: {{version}}"'
- run: |
sudo pkgx tdnf install \
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we definitely shouldn't be modifying the underlying OS using sudo in a test. if we can do it local to the testdir or the synthetic homedir, that would be fine.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tdnf seems to need sudo to work into the --installroot

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • /home/admin/.pkgx/pkgx.sh/v2.7.0/bin/pkgx tdnf install --installroot=/home/admin/Documents/pantry-tdnf+libgomp/testbeds/github.com__vmware__tdnf-3.6.3/rocky-10-rootfs --releasever=10 --forcearch=aarch64 -y bash coreutils passwd iproute iputils procps-ng util-linux openssh-server openssh-clients less vim-minimal tar gzip which dnf yum
    Error(1601) : Operation not permitted. You have to be root.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interesting; i wonder if it's using a loopback mount or something in a chroot. that seems like a problem, but probably not one we can fix. alright.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i guess maybe those oversights aren't surprising, since vmware did things like hardcoding /etc into cmake. they're clearly targeting their own systems.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you have an idea for the "undefined symbol: luaL_openlibs" error?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

interesting, since both rpm's test and the old tdnf test don't detect the missing symbol. possibly we need to pin rpm to lua~5.4 instead of using ^5.2? it's probably abi changes.

--installroot="$PWD/${ROOTFS}" \
--releasever=${RELEASE} \
--forcearch={{ hw.arch }} \
-y bash coreutils passwd iproute iputils procps-ng util-linux \
openssh-server openssh-clients less vim-minimal tar gzip \
which dnf yum
Loading