• Re: Request for salsa access

    From Carsten Schoenert@21:1/5 to All on Mon Nov 21 20:10:01 2022
    Hello Matthias,

    Am 21.11.22 um 16:39 schrieb matthias.geiger1024@tutanota.de:
    Dear Maintainers,

    I'd like to join the team and get access to maintain python3-fints.
    fints is a new package I filed an ITP for (#1024494). In my opinion it
    would be best if it
    would be maintained under the python packaging team. I'd only need
    access for this library.

    I acknowledge that I read the packaging policy. My salsa username is werdahias.
    I'm not a DD yet, so I'd need sponsorship for this package.

    I'd suggest to first work on your ITP and get more familiar with
    packaging of Debian packages in general. There is no need to first have
    a working access to the DPT group on Salsa. You will have to learn a lot
    things and to me it seems easier to work first within your own namespace
    on Salsa were you can act as you like. It's no problem to move packaging
    trees all over within the GitLab instance on Salsa later.

    I did a quick look into the git tree you referenced within your ITP.

    The branches for the upstream source and also pristine-tar are missing.
    It's of course somehow possible to get your current work build into a
    deb package, but the typical workflow is a bit different. :-)

    You might want have a look at existing packages on Salsa within the DPT
    to get some inspiration how your tree layout should look like.

    The DPT uses git-buildpackage for preparing packages, this tool can help
    a lot with the typical steps that are needed to produce the required
    files for a new package upload. But also in your case if you need to
    start a new package from scratch.

    https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id3

    I suggest to have again a look into the DPT policy and also into
    existing packages and their git history to see and learn how things work together.
    This mailing list is probably not the best place to get help on basic
    packaging question, there a better channels available (IRC, mailing list debian-mentors), but it *is* the place to ask specific questions about
    Python in Debian or Python packaging in detail.

    Feel free to contact me directly for specific questions.

    --
    Regards
    Carsten

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From matthias.geiger1024@tutanota.de@21:1/5 to All on Thu Nov 24 17:50:01 2022
    Hi Carsten,

    thanks for the reponse. I imported fints in a DEP-14 repo: https://salsa.debian.org/werdahias/python-fints
    I didn't include a d/gbp.conf and my upstream branch is named upstream/lastest, but I hope this isn't an issue.
    I'd appreciate it if you or another DD could review and upload it if you got the time.

    Cheers

    Matthias
    21. Nov. 2022, 20:04 von c.schoenert@t-online.de:

    Hello Matthias,

    Am 21.11.22 um 16:39 schrieb matthias.geiger1024@tutanota.de:

    Dear Maintainers,

    I'd like to join the team and get access to maintain python3-fints.
    fints is a new package I filed an ITP for (#1024494). In my opinion it would be best if it
    would be maintained under the python packaging team. I'd only need access for this library.

    I acknowledge that I read the packaging policy. My salsa username is werdahias.
    I'm not a DD yet, so I'd need sponsorship for this package.


    I'd suggest to first work on your ITP and get more familiar with packaging of Debian packages in general. There is no need to first have a working access to the DPT group on Salsa. You will have to learn a lot things and to me it seems easier to work
    first within your own namespace on Salsa were you can act as you like. It's no problem to move packaging trees all over within the GitLab instance on Salsa later.

    I did a quick look into the git tree you referenced within your ITP.

    The branches for the upstream source and also pristine-tar are missing. It's of course somehow possible to get your current work build into a deb package, but the typical workflow is a bit different. :-)

    You might want have a look at existing packages on Salsa within the DPT to get some inspiration how your tree layout should look like.

    The DPT uses git-buildpackage for preparing packages, this tool can help a lot with the typical steps that are needed to produce the required files for a new package upload. But also in your case if you need to start a new package from scratch.

    https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id3

    I suggest to have again a look into the DPT policy and also into existing packages and their git history to see and learn how things work together.
    This mailing list is probably not the best place to get help on basic packaging question, there a better channels available (IRC, mailing list debian-mentors), but it *is* the place to ask specific questions about Python in Debian or Python packaging
    in detail.

    Feel free to contact me directly for specific questions.

    --
    Regards
    Carsten



    <html>
    <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body>
    <div>Hi Carsten,<br></div><div dir="auto"><br></div><div dir="auto">thanks for the reponse. I imported fints in a DEP-14 repo:<br></div><div dir="auto"><a href="https://salsa.debian.org/werdahias/python-fints">https://salsa.debian.org/werdahias/python-
    fints</a><br></div><div dir="auto">I didn't include a <span class="font" style="font-family: monospace, sans-serif;">d/gbp.conf</span> and my upstream branch is named <span class="font" style="font-family: monospace, sans-serif;">upstream/lastest</span>,
    but I hope this isn't an issue.<br></div><div dir="auto">I'd appreciate it if you or another DD could review and upload it if you got the time.<br></div><div dir="auto"><br></div><div dir="auto">Cheers<br></div><div dir="auto"><br></div><div dir="auto">
    Matthias</div><div><br></div><div>21. Nov. 2022, 20:04 von c.schoenert@t-online.de:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>Hello Matthias,<br></div><div><br></div><
    Am 21.11.22 um 16:39 schrieb matthias.geiger1024@tutanota.de:<br></div><blockquote><div>Dear Maintainers,<br></div><div><br></div><div>I'd like to join the team and get access to maintain python3-fints.<br></div><div>fints is a new package I filed an
    ITP for (#1024494). In my opinion it would be best if it<br></div><div>would be maintained under the python packaging team. I'd only need access for this library.<br></div><div><br></div><div>I acknowledge that I read the packaging policy. My salsa
    username is werdahias.<br></div><div>I'm not a DD yet, so I'd need sponsorship for this package.<br></div></blockquote><div><br></div><div>I'd suggest to first work on your ITP and get more familiar with packaging of Debian packages in general. There is
    no need to first have a working access to the DPT group on Salsa. You will have to learn a lot things and to me it seems easier to work first within your own namespace on Salsa were you can act as you like. It's no problem to move packaging trees all
    over within the GitLab instance on Salsa later.<br></div><div><br></div><div>I did a quick look into the git tree you referenced within your ITP.<br></div><div><br></div><div>The branches for the upstream source and also pristine-tar are missing. It's of
    course somehow possible to get your current work build into a deb package, but the typical workflow is a bit different. :-)<br></div><div><br></div><div>You might want have a look at existing packages on Salsa within the DPT to get some inspiration how
    your tree layout should look like.<br></div><div><br></div><div>The DPT uses git-buildpackage for preparing packages, this tool can help a lot with the typical steps that are needed to produce the required files for a new package upload. But also in your
    case if you need to start a new package from scratch.<br></div><div><br></div><div>https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#id3<br></div><div><br></div><div>I suggest to have again a look into the DPT policy and
    also into existing packages and their git history to see and learn how things work together.<br></div><div>This mailing list is probably not the best place to get help on basic packaging question, there a better channels available (IRC, mailing list
    debian-mentors), but it *is* the place to ask specific questions about Python in Debian or Python packaging in detail.<br></div><div><br></div><div>Feel free to contact me directly for specific questions.<br></div><div><br></div><div>-- <br></div><div>
    Regards<br></div><div>Carsten<br></div></blockquote><div dir="auto"><br></div> </body>
    </html>

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