Hello mentors,As far as I can see this is not configurable, all locally-repacked
I want to import a new svn snapshot to update a Debian package,
the salsa git repo is already configured for gbp, so I did
$ gbp import-orig -u1.5+svn38408 ../upstreamsvn/mplayer
upstream/mplayer is a directory with the unpacked svn checkout.
Gbp creates a ../upstreamsvn/mplayer_1.5+svn38408.orig.tar.gz
archieve (not a tar.xz); it also uses tar.gz in the pristine-tar branch.
One problem with the tar.gz is that debian/gbp.conf hasSo this configuration is wrong ad you need to change it.
compression = xz
so when I push to salsa the salsa-ci fails because it searches for a(I'm still surprised that people apparently don't build locally, only on salsa-ci)
tar.xz archieve
Hello Lorenzo,It would be much more useful if you provided the actual option for this.
please use a special gbp.conf.
More information you can get in the manpage of gbp.conf(that manpage doesn't even list actual options)
On Fri, Jan 27, 2023 at 06:02:34PM +0100, Lorenzo wrote:
Hello mentors,
I want to import a new svn snapshot to update a Debian package,
the salsa git repo is already configured for gbp, so I did
$ gbp import-orig -u1.5+svn38408 ../upstreamsvn/mplayer
upstream/mplayer is a directory with the unpacked svn checkout.As far as I can see this is not configurable, all locally-repacked
Gbp creates a ../upstreamsvn/mplayer_1.5+svn38408.orig.tar.gz
archieve (not a tar.xz); it also uses tar.gz in the pristine-tar
branch.
tarballs are repacked as .tar.gz.
I didn't write in my previous message, but the watch file of thisOne problem with the tar.gz is that debian/gbp.conf hasSo this configuration is wrong ad you need to change it.
compression = xz
(I build locally with sbuild and use salsa-ci for piuparts and otherso when I push to salsa the salsa-ci fails because it searches for a(I'm still surprised that people apparently don't build locally, only
tar.xz archieve
on salsa-ci)
Are you mixing released tarballs and contents of some SVN repo in the same package repo then? Or what is your workflow?I didn't write in my previous message, but the watch file of thisOne problem with the tar.gz is that debian/gbp.conf hasSo this configuration is wrong ad you need to change it.
compression = xz
project looks for a tar.xz when downloading a new upstream release.
On Sun, Jan 29, 2023 at 03:45:26PM +0100, Lorenzo wrote:
Are you mixing released tarballs and contents of some SVN repo in theI didn't write in my previous message, but the watch file of thisOne problem with the tar.gz is that debian/gbp.conf hasSo this configuration is wrong ad you need to change it.
compression = xz
project looks for a tar.xz when downloading a new upstream release.
same package repo then? Or what is your workflow?
Is this a one-time thing? If so, I would just create a tarball manually.Are you mixing released tarballs and contents of some SVN repo in theI didn't write in my previous message, but the watch file of thisOne problem with the tar.gz is that debian/gbp.conf hasSo this configuration is wrong ad you need to change it.
compression = xz
project looks for a tar.xz when downloading a new upstream release.
same package repo then? Or what is your workflow?
Yes, the latest upstream release (mplayer 1.5) has CVEs and fails to
build, so I jumped from 1.4 to 1.5+svn
I suspect this package may need to alternate unreleased version andYes, the latest upstream release (mplayer 1.5) has CVEs and fails toIs this a one-time thing? If so, I would just create a tarball
build, so I jumped from 1.4 to 1.5+svn
manually.
But overall you need to make sure the SVN repo contains theright, I should have excluded the .svn directory from the source..
same files as the published tarball, otherwise the compression
difference is not the largest problem you could have.
Also, the best way is probably submitting a patch for gbp to make the repacked tarball compression configurable.I doubt that I'll have the extra time for that, but it's now in my TODO
You normally don't need to do anything special when doing that as opposedBut overall you need to make sure the SVN repo contains theright, I should have excluded the .svn directory from the source..
same files as the published tarball, otherwise the compression
difference is not the largest problem you could have.
apart from that I don't think there are other relevant difference.
Is there a document that describes the right steps to follow when
importing a git or svn snapshot in Debian? I couldn't find one.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 714 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 141:12:02 |
| Calls: | 12,087 |
| Files: | 14,998 |
| Messages: | 6,517,442 |