5 ms·

Yeah, figuring out the Debian process can be a pain. More often than not, Debian is just a 'middle man' for the code. So for modemmanager see https://packages

by blihp 6y ago

Yeah, figuring out the Debian process can be a pain. More often than not, Debian is just a 'middle man' for the code. So for modemmanager see https://packages.debian.org/bullseye/modemmanager https://packages.debian.org/bullseye/modemmanager and note the maintainer(s) listed on the right side of the page. Sometimes the package maintainer is also a developer of the upstream code. However, often the maintainer will just be repackaging the upstream code (also listed on the right side of the page) so for new features you would need to get the upstream to incorporate it which would result in the package maintainer automatically incorporating it when they rebase/merge the latest changes. I'm not familiar with modemmanager so the main 'trick' is figuring out who does what for that package. (i.e. is the maintainer an active developer or just more passively repackaging it?) The issue right now is that Debian maintainers are all pretty busy trying to nail down Bullseye as they're currently in their hard freeze[1] period... lots of bugs and dependency problems to deal with to get to release. My suggestion would be to wait until Bullseye is released and then contact the maintainer and see if you need to be dealing with them or upstream to get your changes in. If you're impatient, you might have more luck contacting upstream directly right now. Either way, the odds of getting new features in for Bullseye are likely slim to none right now. [1] https://release.debian.org/bullseye/freeze_policy.html https://release.debian.org/bullseye/freeze_policy.html

kop316 6y ago
Gotcha. So I may be in a weird spot then. I am trying to get mmsd (not modem manager) into Debian proper. Mmsd itself is not in Debian at all. Per my original comment, I have tried to contact the ofono (mmsd) maintainers via IRC and their mailing list no less than four times to get my patches upstreamed (every time I have been ignored), and at this point I have given up trying to contact them. One of the ofono maintainers has mentioned that mmsd hasn't been worked on in over 8 years, so I think its abandoned. The Debian on Mobile (i.e. the Mobian and Purism devs) maintainers think the best course of action is to package upstream mmsd, then update with my changes.
- pabs3 6y ago
  So there are two entangled issues here that I would suggest disentangling: How do you get your changes to mmsd into the upstream mmsd repository on kernel.org? There have been commits to mmsd upstream in 2019. My suggestion would be to CC more folks on your next patch submission, at minimum: the Linux netdev mailing list, the oFono list, everyone in the mmsd AUTHORS file and all the folks who are listed as a committer in any of the mmsd git commits. https://git.kernel.org/pub/scm/network/ofono/mmsd.git https://git.kernel.org/pub/scm/network/ofono/mmsd.git How do you get mmsd into Debian? The usual procedure is to upload the package to the mentors site and file a request for sponsor bug report, XCCed to relevant people/lists, which in your case is probably the debian-mobile list, Debian oFono maintainers and any other Debian mobile related addresses (I guess Purism PureOS, Mobian etc). Of course, that doesn't guarantee that a Debian uploader will sponsor the package, but it is a good start. https://mentors.debian.net/intro-maintainers https://mentors.debian.net/intro-maintainers https://mentors.debian.net/sponsors/rfs-howto https://mentors.debian.net/sponsors/rfs-howto https://www.debian.org/Bugs/Reporting#xcc https://www.debian.org/Bugs/Reporting#xcc https://lists.debian.org/debian-mobile/ https://lists.debian.org/debian-mobile/ Do both at the same time, if upstreaming the patches doesn't work out, you can add them to Debian while still figuring out a way to push them upstream.
  - kop316 6y ago
    I will look at your suggestion for upstreaming, thank you. So you can see the ITP packaging request here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982250 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982250 The debian-on-mobile team is aware of it, but even they have been commenting that getting upstream mmsd will take time. One has suggested to change the bug for a request for sponsor. It sounds like I need to do that.
    - pabs3 6y ago
      So the ITP (Intent to Package) and RFS (Request for Sponsor) are two separate things. The ITP comes before you have started the packaging, it is a notice of intent rather than a request and functions as a way to prevent other folks from spending time on something someone else is spending time on, a place to discuss and document any issues that come up during packaging and a way to advertise the potential new package such that others can get involved and co-maintain the package if they want to. Since you didn't XCC the ITP to debian-devel as is customary (and what reportbug wnpp does), that part of the purpose of ITPs was reduced. The RFS comes after you consider the packaging complete and ready to be in the Debian archive. It is only for people who aren't yet able to upload themselves. It should be sent once each time you want to upload. It should be directed at debian-mentors (done automatically when using reportbug) and XCCed to the relevant team mailing lists and any other potential sponsors.
- blihp 6y ago
  I'd definitely proceed as pabs3 suggests. As a short term solution, you might want to contact a-wai and see if your work could live in the Mobian repo in the meantime as I think MMS is still a highly sought after feature.
  - kop316 6y ago
    a-wai knows about my work, he actually has helped me solve a couple of issues I had in my mmsd plug in. I'll take a look at what pabs3 said, it looks like I have a couple of things to do today for this.

by blihp 6y ago

kop316 6y ago

Gotcha. So I may be in a weird spot then. I am trying to get mmsd (not modem manager) into Debian proper. Mmsd itself is not in Debian at all. Per my original comment, I have tried to contact the ofono (mmsd) maintainers via IRC and their mailing list no less than four times to get my patches upstreamed (every time I have been ignored), and at this point I have given up trying to contact them. One of the ofono maintainers has mentioned that mmsd hasn't been worked on in over 8 years, so I think its abandoned. The Debian on Mobile (i.e. the Mobian and Purism devs) maintainers think the best course of action is to package upstream mmsd, then update with my changes.

pabs3 6y ago
So there are two entangled issues here that I would suggest disentangling: How do you get your changes to mmsd into the upstream mmsd repository on kernel.org? There have been commits to mmsd upstream in 2019. My suggestion would be to CC more folks on your next patch submission, at minimum: the Linux netdev mailing list, the oFono list, everyone in the mmsd AUTHORS file and all the folks who are listed as a committer in any of the mmsd git commits. https://git.kernel.org/pub/scm/network/ofono/mmsd.git https://git.kernel.org/pub/scm/network/ofono/mmsd.git How do you get mmsd into Debian? The usual procedure is to upload the package to the mentors site and file a request for sponsor bug report, XCCed to relevant people/lists, which in your case is probably the debian-mobile list, Debian oFono maintainers and any other Debian mobile related addresses (I guess Purism PureOS, Mobian etc). Of course, that doesn't guarantee that a Debian uploader will sponsor the package, but it is a good start. https://mentors.debian.net/intro-maintainers https://mentors.debian.net/intro-maintainers https://mentors.debian.net/sponsors/rfs-howto https://mentors.debian.net/sponsors/rfs-howto https://www.debian.org/Bugs/Reporting#xcc https://www.debian.org/Bugs/Reporting#xcc https://lists.debian.org/debian-mobile/ https://lists.debian.org/debian-mobile/ Do both at the same time, if upstreaming the patches doesn't work out, you can add them to Debian while still figuring out a way to push them upstream.
- kop316 6y ago
  I will look at your suggestion for upstreaming, thank you. So you can see the ITP packaging request here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982250 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982250 The debian-on-mobile team is aware of it, but even they have been commenting that getting upstream mmsd will take time. One has suggested to change the bug for a request for sponsor. It sounds like I need to do that.
  - pabs3 6y ago
    So the ITP (Intent to Package) and RFS (Request for Sponsor) are two separate things. The ITP comes before you have started the packaging, it is a notice of intent rather than a request and functions as a way to prevent other folks from spending time on something someone else is spending time on, a place to discuss and document any issues that come up during packaging and a way to advertise the potential new package such that others can get involved and co-maintain the package if they want to. Since you didn't XCC the ITP to debian-devel as is customary (and what reportbug wnpp does), that part of the purpose of ITPs was reduced. The RFS comes after you consider the packaging complete and ready to be in the Debian archive. It is only for people who aren't yet able to upload themselves. It should be sent once each time you want to upload. It should be directed at debian-mentors (done automatically when using reportbug) and XCCed to the relevant team mailing lists and any other potential sponsors.
blihp 6y ago
I'd definitely proceed as pabs3 suggests. As a short term solution, you might want to contact a-wai and see if your work could live in the Mobian repo in the meantime as I think MMS is still a highly sought after feature.
- kop316 6y ago
  a-wai knows about my work, he actually has helped me solve a couple of issues I had in my mmsd plug in. I'll take a look at what pabs3 said, it looks like I have a couple of things to do today for this.