• Bug#1085489: gkrellm-tz FTCBFS multiple issues

    From Andreas Tille@1:229/2 to All on Sun Jul 6 12:30:01 2025
    From: [email protected]

    Hi Adrian,

    your package gkrellm-tz came up as a candidate for the Bug of the Day.
    I would like to work on this package to demonstrate how to fix bugs of
    Debian packages which is done most easily by Salsa commits. Since I
    know you are perfectly active in Debian I'm hesitating to migrate your
    package to Salsa without your confirmation. Thus I'm kindly asking
    hereby what you might think about moving gkrellm-tz either to Salvage
    or Debian team space.

    Kind regards
    Andreas.

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Adrian Bunk@21:1/5 to Andreas Tille on Thu Jul 10 22:40:01 2025
    On Sun, Jul 06, 2025 at 12:25:37PM +0200, Andreas Tille wrote:
    Hi Adrian,

    Hi Andreas,

    your package gkrellm-tz came up as a candidate for the Bug of the Day.

    does "Bug of the Day" even make sense during a freeze?

    I would like to work on this package to demonstrate how to fix bugs of
    Debian packages which is done most easily by Salsa commits. Since I
    know you are perfectly active in Debian I'm hesitating to migrate your package to Salsa without your confirmation. Thus I'm kindly asking
    hereby what you might think about moving gkrellm-tz either to Salvage
    or Debian team space.

    I want to look at moving my packages to Salsa after the freeze.

    My red line is that I do not want to do tarball+quilt maintainance in
    git where I have to "git format-patch" in one git repository and then
    copy patches to debian/patches in another git repository.

    If tag2upload enables a fully git based workflow without .orig.tar
    (and without pristine-tar!) then that's something I will do.

    Kind regards
    Andreas.

    cu
    Adrian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to any of your packages and I'm happy on Thu Jul 10 23:40:01 2025
    Hi Adrian,

    Am Thu, Jul 10, 2025 at 11:31:31PM +0300 schrieb Adrian Bunk:
    your package gkrellm-tz came up as a candidate for the Bug of the Day.

    does "Bug of the Day" even make sense during a freeze?

    Well, we do not upload packages in testing but there are some packages
    that are not in testing and it happened that we fixed RC bugs and we
    can do also do removals. Moreover it gives more time to maintainers who
    might potentially respond since for sure we follow freeze policy.

    Besides all this the original idea was to demonstrate newcomers how to
    fix bugs and this can be done in any case. Unfortunately regarding this
    idea the project is a failure since newcomers are (at least not visibly) joining.

    I would like to work on this package to demonstrate how to fix bugs of Debian packages which is done most easily by Salsa commits. Since I
    know you are perfectly active in Debian I'm hesitating to migrate your package to Salsa without your confirmation. Thus I'm kindly asking
    hereby what you might think about moving gkrellm-tz either to Salvage
    or Debian team space.

    I want to look at moving my packages to Salsa after the freeze.

    Cool. Thanks a lot for confirming this.

    My red line is that I do not want to do tarball+quilt maintainance in
    git where I have to "git format-patch" in one git repository and then
    copy patches to debian/patches in another git repository.

    I understand (and for sure accept) your preference which aligns with
    lots of other developers who prefer the `gbp pq` workflow. I'm not
    (yet) comfortable with this workflow but rather use quilt manually
    adding the quilt patches later to Git. Since I'm used to it I have no
    problem to work with it but I perfectly understand your point that this
    is counter-intuitive. Thus I think its not a good idea if I might touch
    any of your packages and I'm happy to have asked in advance.

    If tag2upload enables a fully git based workflow without .orig.tar
    (and without pristine-tar!) then that's something I will do.

    This is perfectly at the horizont and I'm happy that finally some
    tooling is sufficiently convincing due to visible advantages to make
    developers considering to move to a git based workflow.

    Since I'm not the best person to help here I will stop bothering you
    from the Bug of the Day perspective. However, I will most probably take
    the freedom to quote you (anonymized) if I'm talking about tag2upload /
    git workflows since I consider your view as pretty interesting and a
    good example for others.

    Thanks a lot for your helpful response and greetings from Brest
    Andreas.

    --
    https://fam-tille.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andreas Tille@21:1/5 to All on Fri Jul 25 12:30:01 2025
    Hi again,

    I just realised that I once created a repository for your package
    black-box.

    Am Thu, Jul 10, 2025 at 11:28:38PM +0200 schrieb Andreas Tille:
    I want to look at moving my packages to Salsa after the freeze.

    Cool. Thanks a lot for confirming this.

    So maybe this repository[1] is helpful for you. I'll invite you as
    owner and if this is not sufficient I can help with moving it to your
    own preference.

    My red line is that I do not want to do tarball+quilt maintainance in
    git where I have to "git format-patch" in one git repository and then
    copy patches to debian/patches in another git repository.

    I understand (and for sure accept) your preference which aligns with
    lots of other developers who prefer the `gbp pq` workflow. I'm not
    (yet) comfortable with this workflow but rather use quilt manually
    adding the quilt patches later to Git. Since I'm used to it I have no problem to work with it but I perfectly understand your point that this
    is counter-intuitive. Thus I think its not a good idea if I might touch
    any of your packages and I'm happy to have asked in advance.

    I just removed the pristine-tar branch. Unfortunately I have no idea
    about the patches-applied workflow. IMHO, this can be done with `gbp
    pq` but I never tried this. So I'll leave the repository in the state
    as is and hope it is sufficientl helpful for you to be converted to
    your own prefered workflow.

    If tag2upload enables a fully git based workflow without .orig.tar
    (and without pristine-tar!) then that's something I will do.

    This is perfectly at the horizont and I'm happy that finally some
    tooling is sufficiently convincing due to visible advantages to make developers considering to move to a git based workflow.

    As far as I understood tag2upload can deal perfectly fine with the
    current repository.

    As I said in my gkrellm-tz related mail I do not intend to touch the
    package without your consent.

    Hope this helps
    Andreas.

    [1] https://salsa.debian.org/games-team/black-box

    --
    https://fam-tille.de

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