1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.MENTOR

  • Re: Debian watch file and GitLab for Autotools projects?

    From Ansgar@21:1/5 to Eivind Naess on Wed Apr 6 19:10:02 2022
    Hi,

    On Wed, 2022-04-06 at 16:26 +0000, Eivind Naess wrote:
    Using watch with git tags yields the same thing (snapshot of the
    source code, not the release tarball). I could use the GitLab API and
    fetch a JSON file, but I can't figure out to make that work with the
    watch file.

    I once suggested to use

    opts="searchmode=plain,downloadurlmangle=s{/uploads}{/upower/upower/uploads}" \ https://gitlab.freedesktop.org/api/v4/projects/upower%2fupower/releases /uploads/[0-9a-z]+/upower-([0-9.]+)\.tar\.xz

    on IRC for a Gitlab project. I think that or something similar might
    be what you are looking for.

    Ansgar

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eivind Naess@21:1/5 to All on Wed Apr 6 18:50:01 2022
    Hello,

    I have a package hosted on GitLab and am trying to modify my Debian package's watch file to follow the releases as I tag/upload them there. I've read through the GitLab related details for the watch file here: https://wiki.debian.org/debian/watch, but am
    still having problems.

    The project is using ./autogen.sh to generate the configure scripts, et al for the project. When I got to tag and create a release, I have to upload the resulting tarball with the resulting configure scripts embedded. Now, I can do this so I have a
    permanent link to the archive by using the GitLab API and using curl to upload the archive. The resulting URL would be something similar to:
        releases/@ANY_VERSION@/downloads/dist-gzip/<project-name>-\d\S*@ARCHIVE_EXT@

    However, because how GitLab pages are composed; the original https://gitlab.com/<user>/<project>/tags?sort=updated_desc doesn't include my permanent URL on that page, and using a different base URL for getting the releases page isn't containing any links
    as it uses javascript to fetch a Json file.

    Using watch with git tags yields the same thing (snapshot of the source code, not the release tarball). I could use the GitLab API and fetch a JSON file, but I can't figure out to make that work with the watch file.

    Does anyone have any suggestion to use the watch file with GitLab and custom release tarballs?

    Regards,
    - Eivind

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul Wise@21:1/5 to Eivind Naess on Thu Apr 7 04:10:01 2022
    On Wed, 2022-04-06 at 16:26 +0000, Eivind Naess wrote:

    The project is using ./autogen.sh to generate the configure scripts,
    et al for the project. When I got to tag and create a release, I have
    to upload the resulting tarball with the resulting configure scripts embedded.

    Personally I would suggest not using the tarballs containing autotools
    files for the Debian orig.tar and instead using tarballs that are
    identical to the upstream git repository. This ensures that on Debian
    you are always building the ./configure and other autotools files from
    source at `debian/rules build` time.

    Also review the upstream git repository to ensure it doesn't contain
    embedded copies of files maintained elsewhere (those should be packaged
    in Debian and added to build-deps instead), or other generated files
    (those should be removed and instead created at build time.

    The only potential exception to this are the copies of the licenses.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmJORhkACgkQMRa6Xp/6 aaNKrg/+LdOR2HochkRlui34V4zFndsuW8pTE9muAsmi7hoVcu7/MivMIzVNYcx6 yNSfuDHYU/4U1PwIerv9mA7qMhA2NzHyS/wzYo+J9w+1Dhxtbe3MRy7QaHyDQZI3 YOv+5WI10364nzp311t3+XFQIWhXDcrsNl079qs7ypB50cv4NAYTe6xr92WkVgQ8 FzGVWsNEIip73+Lh/EM1tIzX7F7ogFtxCbkkdaeiAFWjY5Nn61FGXip8TKUyvHsC QWrQoVsKXcuyaY5bpCMeQOtdE2F7nW0HUSLbDUlczgWrrnwmdHmNAT9+SHDHtypl LhgNSzlrO5/vdokanqyI9divpFa/F1pKaGPk2GbyG1D53XwrV8Ysb8WqdVl+D2ex XU59qVyCc6JftJv+L8iqbkY9dSqDPqTO2MPnII5AzmvlL28NsmVEd3x7UBxUTSBC KtXjm4pYREEnvdIuFgpOESNSAe9dJb5Rvf7Z7QgSEFBttZliMcOpjSnkIxoF9Onf FA3nYs2UgNrZUO6vKJSYWHTsrvldXHX/pq91gdtPKx8MXF4iOVMwpT6MJ4GN+4Ti aNw7rVK7cyGAnlJq8pEHHEj+jOEqOCrjuF+jLqp2WzFOymmES5CDWTT3qF1WJaOy 1dJw9gZGWQ9UOy2yd7z6BffdvjnEZtl0hv2nhzoJz/NQHhZKsWU=
    =TAaQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)