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

  • Re: Question about source tarballs for packaging

    From Andrey Rahmatullin@21:1/5 to Joshua Peisach on Mon Oct 11 09:00:01 2021
    On Sun, Oct 10, 2021 at 09:40:54PM +0000, Joshua Peisach wrote:
    This doesn't really matter; the above means that we will have to build
    on weekly tags rather than the current '0.2.4' tag. Here is the issue.
    uscan and gbp aren't happy with the tag because by all means, it isn't a number.
    Not being a number isn't a problem though?

    It is now that I turned to how other people package, such as how the
    kernel team packages linux, and how the MATE team packages things, and
    other ways of getting the source compared to the way I am pretty much accustomed to with Python, Go, and Cinnamon team with the pristine-tar..
    is this all really neccessary?
    Not sure what do you mean here but no, nothing is really necessary as long
    as you have an orig.tar.

    What is the proper way to get the source?
    There is no single "proper" way.

    What ways are allowed and what aren't? What can I do and what can't I do?
    This is very vague but you can do anything that gives you an orig.tar.
    "How to do that automatically", "how to integrate this with my packaging
    git repo" and "how to integrate this with gbp" are separate unrelated questions.

    I'm in a tight situation where I'll be building weekly tags (not to
    mention finding a sponsor who will even be okay with the crazy crap I'm
    going to be pulling off for this to actually work), what are the
    standards? What is policy about?
    The policy doesn't talk about your packaging git repo. You can even not
    have one, or not publish it. Additionally, even if you have one there is
    no single accepted structure for it. gbp is not the only way to use a repo
    and there is no single way to use gbp. etc.

    So even in your case there are multiple valid options how to do the
    packaging, how to make a packaging repo and how to integrate it with the upstream source, from not doing it, to making tarball and importing them
    into the repo, to packaging tags directly.

    --
    WBR, wRAR

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

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmFj34ktFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh WpEP/A64ZRwLyvW1S6hduTJgoYaoqk4VFAIHqkVr7ey+qCg84St8vPi4fTwX6+iJ QHkfkSG9ksEfx9Zuu6YGxU33+3MnX5v1uNkuHg7O5Ek40nb6/FYYPZjo/vfSKKwK ROcy7FkXA+cvI1Psq9IHoMBMHh/peiY3FUkpznMVk1wN7KCyg7lufQoDjNabHYoG Uk9su/nmCG73HxTl+4cfvskmnTZGrGOKxHr581l2HT0GSYZDZMDF/3BzlWKYGdMm E1Evzf1tDP/ylbJ6A2yJD3+eY4yn9wbbMKyj12uvZzi2xgvzFcwWmJmVLs7HhTnF YKgaNBRuCjhlcfX4ckoQ9IfcpS16quYnQd8m5qPePspBdFo6eWaJ7oHOQVLwMd4a s1rP2oZ33mBF96RNNj/VM9WxTbH/7Hsv2UthYpMiAc5AOFxhMEKJ7ddAM/cWlmIs WoNBMQgmve6osbPtXDw8CXiaploAze8mc9a0y2Ufe9mOCwgyhf1feDqtHx15gpDA D8DY5iclAL/1Oc8aTERgWO9Y48fSC36F57ypduB0h9TroVJJFHXwNRLaRUAqF9lr L0GnIt/pCFo01cSvzRMs3ueFlQ6tOjRTUjD1uBer+8cFmkIfoSIZTBBVVRvxMJVJ adVtLIAzqcSwEj002kEvYZXbWc7kRBwsuEciVoL6Bea0DjJZ
    =7GDp
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jonas Smedegaard@21:1/5 to All on Mon Oct 11 10:10:02 2021
    Hi Joshua,

    Quoting Joshua Peisach (2021-10-10 23:40:54)
    we will have to build on weekly tags rather than the current '0.2.4'
    tag. Here is the issue. uscan and gbp aren't happy with the tag
    because by all means, it isn't a number.

    One option is to track git commits organized by date, using a watch file
    like this:


    debian/watch >>>
    # version=4
    # check: uscan --report
    # update: gbp import-orig --upstream-vcs-tag=vX.Y.Z --uscan

    opts=\
    mode=git,pgpmode=none,pretty=0.2.4+%cd \
    https://github.com/sctplab/usrsctp HEAD
    <<< debian/watch <<<


    - Jonas

    --
    * Jonas Smedegaard - idealist & Internet-arkitekt
    * Tlf.: +45 40843136 Website: http://dr.jones.dk/

    [x] quote me freely [ ] ask before reusing [ ] keep private --==============x19035139896711615=MIME-Version: 1.0
    Content-Transfer-Encoding: 7bit
    Content-Description: signature
    Content-Type: application/pgp-signature; name="signature.asc"; charset="us-ascii"

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

    iQIzBAABCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFj7YAACgkQLHwxRsGg ASHJEQ//aejXMW+k+DZ2kDsDRVK87mxKB9FhfqcgBwgUKobvV06lGXX4m5+1a06B EFjPTo8j7OQaAaZwGEM1z16CKSexcFHWPLWv59KW27RrMqh5zlqbGLf/2t7/dDWl wOjyFedXBhLRm1qaNiVKIAfLT6dnALvcfMMZGQI9hRezxJpx1d8sHtzE5q0km1gA V85wMZOOcxiCDNM1jFCSl7I40ZLs2q9RHis1W4nuXcFxzraB6BeS2pIxmCtxUo5r xcNmt0ymHuAXUrAjMxeNX4NL5CzQ0/LzTBHHfxZJaR7B0Wk0baLlnoWqbsTODH4h mqBxxjt34Tc7zKVxXxWALMO2iAlWF+VwVMYyVXgQGcslvuckVLqNMbv48uSNN/lN s3s0n6Mdc/PotW1youzynvDP31kOdZGKjc8L+V9Nce4kw79zsY3aSbLt5dxssMkl JgNib5l41BAB2mNzTCN/xnUfCu7p+h2tZVpFSDNzIaxF/58XJ2e6qAesmfhcAuED va2ebh3GBNYnPpGiw
  • From Paul Wise@21:1/5 to Joshua Peisach on Tue Oct 19 06:00:02 2021
    On Sun, 2021-10-10 at 21:40 +0000, Joshua Peisach wrote:

    I'm packaging the V programming language for Debian. However, V is  bit weird at the moment. It's not really ready for stable production/use.
    so for a while it will live in experimental. Currently the way building
    it works is that there is a repo that is the compiler translated to C automatically that you have to clone and compile to build V, and then
    all the actual libraries and everything to make V work. The cloning is
    done through git via Makefile.

    That is not a proper bootstrap process ala Bootstrappable Builds.

    https://bootstrappable.org/

    Is the code that generates the C code possible to run without V built
    yet? If so I suggest that you run that code from the Debian package
    build. If not, personally I would not add V to Debian yet.

    What is the proper way to get the source?

    Jonas' suggestion of using uscan to get tarballs of the git branch
    seems reasonable.

    --
    bye,
    pabs

    https://wiki.debian.org/PaulWise

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

    iQIzBAABCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmFuQl8ACgkQMRa6Xp/6 aaNPMQ//ZiX4cis3lvIzyzTZ28o1NEp47yaUS8BrkNCMp9bDgqPGlldEkNu4AyK1 BvE78pB+HTCxNQWakL+wvrz3YxcLUjxw2Ahj5F71sVnriYJB8olQUFJTjY/yRB6Y qOeJKNoZpd9ddbRIHoIRJdzJOGib7Mop2HwHLJgZt/BuobUFSPHuHK4Y4nnwC5t7 9vwr5laPtEUqdzR8BIy2paC2IgY5kEjW8dhbu2NwqN3JM0NG0bJeXO6nc0OhecsX oyLLvsRKVv4Z7esZPQDTigKyFOq3g4bXlabnTD9y9cw5sGO/aStRby11xp5FiPRG VFlQZKFmOIbnM4eLUY1kVt59HHws8Z7nWohNzrqbAWqjtV88x5QWrZso35Ooto4W AO+J7P67g4knjZjm/mKqEEFGbJZLgPJXT6nAdH1bwXemHUcgoUwUa8ZylWED0Hhl qHhu9uAVQMGRHIyFOpB6GWEfpiGqwcGNGko8aHZK9oozCNaH5KvVkm5KNiJdx4FE HGZzl3jo4g3mRic4kLKWHIdKJQGiNTXelO9SJmdmjlb8aWJst2DjCwBT2BVHvvzn 4ZvcInjqpfidjpQ0o9m6bD+4gfLPNFknpXs0dLVIxHjm8D4+jf7JpLPnTL0a3XYv fJckCOmh79CCbHCjO2Xm70UR8K6R92CAIZOW0UDmgPPZOSKbIcc=
    =bAY+
    -----END PGP SIGNATURE-----

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