Package Details: vma-git 9.2.0-1

Git Clone URL: https://aur.archlinux.org/vma-git.git (read-only, click to copy)
Package Base: vma-git
Description: Virtual Machine Archive format (VMA)
Upstream URL: https://pve.proxmox.com/wiki/VMA
Licenses: AGPL
Provides: vma
Submitter: bobi
Maintainer: bobi
Last Packager: bobi
Votes: 1
Popularity: 0.000011
First Submitted: 2022-05-25 09:33 (UTC)
Last Updated: 2025-02-04 13:50 (UTC)

Latest Comments

1 2 Next › Last »

micwoj92 commented on 2025-01-23 21:17 (UTC)

Changes to this file can be tracked using nvchecker, https://nvchecker.readthedocs.io/en/latest/usage.html#check-github

micwoj92 commented on 2025-01-23 21:16 (UTC)

I got you the first time, but having to periodically check for changes in the project sources is precisely what I do not want to bother with.

I think this is the "spirit" of -git packages. I can understand this being easier, but it makes it harder for users to for example modify build options.
Checking this file it did have some activity in the past, but now the last change was 1,5 years ago. https://github.com/proxmox/pve-qemu/commits/master/debian/rules

Sadly the upstream makefile is also very debian centric. Maybe something to communicate with them? Unless it was, I don't know history of the project.

bobi commented on 2025-01-23 19:38 (UTC) (edited on 2025-01-23 20:05 (UTC) by bobi)

I got you the first time, but having to periodically check for changes in the project sources is precisely what I do not want to bother with.

Besides, sticking to upstream build tools only makes the build somewhat resilient to upstream changes (spare the diff file), which is arguably expected from *-git package. On the subject, the package is a *-git package because I needed to have, thus aimed to provide, the very last vma binary no matter what, should any change in the format occur on Proxmox side. If an unburdened, more controlled and/or more stable build also seems necessary, I guess one can provide a vma or vma-bin alternative.

As for the submodules, I will gladly dig into it and implement that here, thanks for the insight!

micwoj92 commented on 2025-01-23 18:36 (UTC)

I think the simplest way is to just observe changes in this debian file and then copy/paste into pkgbuild.

Submodules should be put in sources array: https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules

bobi commented on 2025-01-23 10:32 (UTC)

@micwoj92, mostly because I don’t have any convenient ways to track upstream changes and I want to keep this build as vanilla as possible (keeping changes only to a rather short diff). Thus I ended up using the debian/rules file, for lack of distro-agnostic upstream build files (at least to my knowledge and at the time of original submission of this package).

That said, I updated the diff so that patching won’t fail anymore; GitHub seems to be quite annoying with the amount of submodules involved, requiring login at some point. Should one not desire to login, it can be circumvented with manually re-calling meson subprojects download from ./src/pve-qemu/qemu after a first call to makepkg, but that is far from convenient. To be frank I am unsure of how that can be addressed.

micwoj92 commented on 2025-01-22 20:28 (UTC)

Why are you using debian tools to create this package? Commands from debian/rules file should just be in this pkgbuild

bobi commented on 2023-12-11 14:56 (UTC)

@maaarghk, thanks for the update, should be good now (with some additional fixes).

maaarghk commented on 2023-12-08 13:18 (UTC)

dpkg.diff does not apply, here's an updated one (worth testing incase the text input mangles tabs / spaces)

diff --git a/Makefile b/Makefile
index 8be4721..ac34e08 100644
--- a/Makefile
+++ b/Makefile
@@ -18,6 +18,6 @@ all: $(DEBS)
 .PHONY: submodule
 submodule:
 ifeq ($(shell test -f "$(SRCDIR)/configure" && echo 1 || echo 0), 0)
-   git submodule update --init --recursive
+   git -c protocol.file.allow=always submodule update --init --recursive
    cd $(SRCDIR); meson subprojects download
 endif
@@ -56,8 +56,8 @@ $(BUILDDIR): keycodemapdb | submodule
 deb kvm: $(DEBS)
 $(DEB_DBG): $(DEB)
 $(DEB): $(BUILDDIR)
-   cd $(BUILDDIR); dpkg-buildpackage -b -us -uc -j
-   lintian $(DEBS)
+   cd $(BUILDDIR); dpkg-buildpackage -b -us -uc -j -d
+#  lintian $(DEBS)

 sbuild: $(DSC)
    sbuild $(DSC)

diff --git a/debian/rules b/debian/rules
index 6d5f882..5bb108d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -69,7 +69,7 @@ ${BUILDDIR}/config.status: configure
        --enable-linux-io-uring \
        --enable-numa \
        --enable-opengl \
-       --enable-rbd \
+       --disable-rbd \
        --enable-seccomp \
        --enable-slirp \
        --enable-spice \
@@ -156,7 +156,7 @@ binary-arch: build install
    dh_installdeb
    # Debian >= Buster has libglusterfs0 and lots of libgfFOO, upstream has the libs in glusterfs-common
    # pass -x to dpkg-shlibdeps and specify dependencies in d/control instead
-   dh_shlibdeps -- -xlibglusterfs0 -xlibgfxdr0 -xlibgfrpc0 -xlibgfdb0 -xlibgfchangelog0 -xlibgfapi0
+#  dh_shlibdeps -- -xlibglusterfs0 -xlibgfxdr0 -xlibgfrpc0 -xlibgfdb0 -xlibgfchangelog0 -xlibgfapi0
    dh_gencontrol
    dh_md5sums
    dh_builddeb

bobi commented on 2023-02-10 13:24 (UTC)

@xeruf, both issues should be fixed.

1 2 Next › Last »