>I am for now not accepting the virtualbox-ext-pack for artful as I first would like to get confirmation about something: looking at the debian/control and debian/rules version variables, those seem to be using the 5.1.32 version string while the package itself is versioned as 5.1.34. Is that a mistake? Or is that intentional?
it is an useless variable. we use DEB_VERSION_UPSTREAM and not that variable to compute runtime dependencies.
that variable is used only to create a new fake tarball, just to import-orig --pristine-tar it
VERSION=5.1.32
tarball:
mkdir virtualbox-ext-pack_$(VERSION)
tar cJvf virtualbox-ext-pack_$(VERSION).orig.tar.xz virtualbox-ext-pack_$(VERSION)
rm -rf virtualbox-ext-pack_$(VERSION)
mv virtualbox-ext-pack_$(VERSION).orig.tar.xz ..
so, I can bump it, or you can accept the current one, the resulting deb will be just the same!
let me know if you want to reject and I'll quickly reupload
@sil2100 thanks!
>I am for now not accepting the virtualbox-ext-pack for artful as I first would like to get confirmation about something: looking at the debian/control and debian/rules version variables, those seem to be using the 5.1.32 version string while the package itself is versioned as 5.1.34. Is that a mistake? Or is that intentional?
it is an useless variable. we use DEB_VERSION_ UPSTREAM and not that variable to compute runtime dependencies.
that variable is used only to create a new fake tarball, just to import-orig --pristine-tar it ext-pack_ $(VERSION) ext-pack_ $(VERSION) .orig.tar. xz virtualbox- ext-pack_ $(VERSION) ext-pack_ $(VERSION) ext-pack_ $(VERSION) .orig.tar. xz ..
VERSION=5.1.32
tarball:
mkdir virtualbox-
tar cJvf virtualbox-
rm -rf virtualbox-
mv virtualbox-
so, I can bump it, or you can accept the current one, the resulting deb will be just the same!
let me know if you want to reject and I'll quickly reupload