• On frama-c's debian/watch

    From julien.puydt@gmail.com@21:1/5 to All on Fri Jul 22 20:20:02 2022
    Hi,

    upstream had modified their site, so I complained:

    https://git.frama-c.com/pub/frama-c/-/issues/2622

    and upstream pretty quickly provided a new page ; except that I don't
    get how from upstream 25.0-Manganese we got a Debian version 20220511- manganese-1.3 !

    With d/watch being:

    version=4
    https://frama-c.com/html/direct-source-distributions.html .*/frama-c- ([0-9]{2}\.[0-9]-[a-zA-Z]+)\.tar\.gz

    then uscan -v lists the upstream versions in a reasonable order.

    What can we do to improve things?

    Cheers,

    J.Puydt

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?St=c3=a9phane_Glondu?=@21:1/5 to All on Thu Jul 28 09:30:01 2022
    Le 22/07/2022 à 20:19, julien.puydt@gmail.com a écrit :
    upstream had modified their site, so I complained:

    https://git.frama-c.com/pub/frama-c/-/issues/2622

    and upstream pretty quickly provided a new page ; except that I don't
    get how from upstream 25.0-Manganese we got a Debian version 20220511- manganese-1.3 !

    With d/watch being:

    version=4
    https://frama-c.com/html/direct-source-distributions.html .*/frama-c- ([0-9]{2}\.[0-9]-[a-zA-Z]+)\.tar\.gz

    then uscan -v lists the upstream versions in a reasonable order.

    What can we do to improve things?

    I was also suprised when I looked at frama-c'v versioning.

    I don't know why date-based versions were chosen.

    If I were in charge, I would add an epoch et start using upstream
    version numbers.


    Cheers,

    --
    Stéphane

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mehdi Dogguy@21:1/5 to All on Thu Jul 28 10:50:01 2022
    ------8A8Z5T8Z3X9D24HX7Y4D0W37C2PRP3
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    Hi,

    Early versions of FramaC were snapshots with dates and codenames. There were no version numbers back then (the date was the only reliable number we've got). At some, they dropped the dates and assigned version numbers to codenames and kept going with
    them.

    One needs to check with them that this schema is stable and not subject to changes in the foreseable future to avoid epoch'ing twice though.

    Regards,

    Le 28 juillet 2022 09:21:15 GMT+02:00, "Stéphane Glondu" <steph@glondu.net> a écrit :
    Le 22/07/2022 à 20:19, julien.puydt@gmail.com a écrit :
    upstream had modified their site, so I complained:

    https://git.frama-c.com/pub/frama-c/-/issues/2622

    and upstream pretty quickly provided a new page ; except that I don't
    get how from upstream 25.0-Manganese we got a Debian version 20220511-
    manganese-1.3 !

    With d/watch being:

    version=4
    https://frama-c.com/html/direct-source-distributions.html .*/frama-c-
    ([0-9]{2}\.[0-9]-[a-zA-Z]+)\.tar\.gz

    then uscan -v lists the upstream versions in a reasonable order.

    What can we do to improve things?

    I was also suprised when I looked at frama-c'v versioning.

    I don't know why date-based versions were chosen.

    If I were in charge, I would add an epoch et start using upstream
    version numbers.


    Cheers,

    --
    Stéphane

    --
    Sent from my Android device with K-9 Mail. Please excuse my brevity. ------8A8Z5T8Z3X9D24HX7Y4D0W37C2PRP3
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body>Hi,<br><br>Early versions of FramaC were snapshots with dates and codenames. There were no version numbers back then (the date was the only reliable number we've got). At some, they dropped the dates and assigned version numbers
    to codenames and kept going with them.<br><br>One needs to check with them that this schema is stable and not subject to changes in the foreseable future to avoid epoch'ing twice though.<br><br>Regards,<br><br><div class="gmail_quote">Le 28 juillet 2022
    09:21:15 GMT+02:00, "Stéphane Glondu" &lt;steph@glondu.net&gt; a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
    <pre dir="auto" class="k9mail">Le 22/07/2022 à 20:19, julien.puydt@gmail.com a écrit&nbsp;:<br><blockq