4 ms·

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=98

by 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.
- kop316 6y ago
  Gotcha, thank you for the clarification on this! Somehow when I read through the documentation on how it works, I must have misunderstood it. I did make am RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985893 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985893 and I want to say I did the XCC to the relevant sponsors? I know I included th Debian on Mobile mailing list (they are the ones to suggest how to submit debian packages).
  - pabs3 6y ago
    Looks like they did get a copy, but FTR, XCC != CC. XCC is my abbreviation for X-Debbugs-CC, which means that the Debian bug tracker forwards your bug to additional folks. If you use XCC then they get the bug number but if you use CC then they don't, at least for the initial bug submission, obviously for post-submission bug mail you are CCing the bug number. https://www.debian.org/Bugs/Reporting#xcc https://www.debian.org/Bugs/Reporting#xcc
    - kop316 6y ago
      Gotcha. Unfortunately, I thought I manually added that, but either Evolution didn't understand it or my mailing service didn't like it (which is what I was afraid of and why I CC'ed as well).
      - pabs3 6y ago
        Usually X-Debbugs-CC is a psuedo-header rather than a real email header, that makes it easier to add to submit messages.

by kop316 6y ago

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.

kop316 6y ago
Gotcha, thank you for the clarification on this! Somehow when I read through the documentation on how it works, I must have misunderstood it. I did make am RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985893 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985893 and I want to say I did the XCC to the relevant sponsors? I know I included th Debian on Mobile mailing list (they are the ones to suggest how to submit debian packages).
- pabs3 6y ago
  Looks like they did get a copy, but FTR, XCC != CC. XCC is my abbreviation for X-Debbugs-CC, which means that the Debian bug tracker forwards your bug to additional folks. If you use XCC then they get the bug number but if you use CC then they don't, at least for the initial bug submission, obviously for post-submission bug mail you are CCing the bug number. https://www.debian.org/Bugs/Reporting#xcc https://www.debian.org/Bugs/Reporting#xcc
  - kop316 6y ago
    Gotcha. Unfortunately, I thought I manually added that, but either Evolution didn't understand it or my mailing service didn't like it (which is what I was afraid of and why I CC'ed as well).
    - pabs3 6y ago
      Usually X-Debbugs-CC is a psuedo-header rather than a real email header, that makes it easier to add to submit messages.