Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #17018

Re: Reviving archived package "PlatformIO"

Show key headers only | View raw

Tianyu, Carsten and Team,

Thanks so much for the guidance here! I have now submitted 3 MRs
(upstream, pristine-tar, and `debian/master`).
https://salsa.debian.org/python-team/packages/platformio/-/merge_requests/2
https://salsa.debian.org/python-team/packages/platformio/-/merge_requests/3
https://salsa.debian.org/python-team/packages/platformio/-/merge_requests/4

I welcome review and suggestions for these 3 changes. To be clear, I
am not expecting access to the DPT Team as a brand-new contributor. I
am happy to work within the MR process as long as the team is willing
to review.

As for the repository name: I agree it can be a bit confusing but I
personally prefer the name as it is currently.
`platformio` is the name used in Python PIP (pip install platformio),
and in other distros like Fedora (dnf install platformio).

Thanks again,
Austin (vidplace7)

On Fri, Aug 22, 2025 at 8:28 AM Carsten Schoenert
<c.schoenert@t-online.de> wrote:
>
> Hello Austin,
>
> Am 21.08.25 um 23:00 schrieb Austin Lane:
> > Emmanuel,
> >
> > Per my understanding, first a Debian maintainer (someone with write
> > access) must update the upstream / pristine-tar branches with "gbp
> > import-orig --uscan". Then I can submit an MR using the new upstream
> > branch. If this understanding is incorrect please let me know.
>
> you can do this perfectly in your own namespace and open one (in total 3
> MRs) once you feel happy with your packaging work.
> Running the import of a new upstream source sin't that complicated and
> you need to know how this is done anyway if you want to work on a
> serious packaging.
>
> Clone the repository and then work on the import and packaging within
> your namespace.
> You don't need to have full access to the DPT Salsa group for doing
> this. And I'm mostly against giving new contributors that I do not know
> enough directly full access, as there is no need.
>
> Probably nobody from the DPT can do what you expect as I believe nobody
> within the team knows specifics of this package to do it mostly
> correctly and without a need to re-adjust $stuff then multile times.
> Within your namespace you can do force pushing as often you like or need
> to do. Within the team namespace it should only be done in rare cases of
> not at all.
>
> And from what I've seen the repository name isn't fitting well as
> platformio is more of a platform and what you are talking about is a
> subproject called platformio-core. What we can do is to rename the
> project within the DPT namespace to that name.
>
> --
> Regards
> Carsten
>


-- 
Austin Lane

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Reviving archived package "PlatformIO" Austin Lane <vidplace7@gmail.com> - 2025-08-20 23:30 +0200
  Re: Reviving archived package "PlatformIO" Emmanuel Arias <eamanu@debian.org> - 2025-08-21 22:20 +0200
    Re: Reviving archived package "PlatformIO" Austin Lane <vidplace7@gmail.com> - 2025-08-21 23:10 +0200
      Re: Reviving archived package "PlatformIO" Tianyu Chen <billchenchina2001@gmail.com> - 2025-08-22 04:20 +0200
      Re: Reviving archived package "PlatformIO" Carsten Schoenert <c.schoenert@t-online.de> - 2025-08-22 14:30 +0200
        Re: Reviving archived package "PlatformIO" Austin Lane <vidplace7@gmail.com> - 2025-08-23 16:20 +0200
          Re: Reviving archived package "PlatformIO" Nicholas D Steeves <sten@debian.org> - 2025-08-29 22:10 +0200

csiph-web