Bug#881032: RFS: icecc/1.1-2~bpo9+1 NMU
Wishlist bug open against the icecc package: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890526
Bug#881032: RFS: icecc/1.1-2~bpo9+1 NMU
On 03/02/18 14:50, Tobias Frost wrote: > > On Fri, Feb 02, 2018 at 09:40:41AM +0100, Pablo Saavedra wrote: >> Hello Tobias, thanks for put me in the right direction on this stuff. >> >> After reading again the established process in [1], I understand that >> the recommended process is a bit different than for standard sponsorship >> requests. Probably I should send the e-mail request with >> debian-backpo...@lists.debian.org in the CC and ask for review and upload. >> >> My intention in this case is not become a maintainer but submit my icecc >> package backported to Jessie with the idea of to be reviewed and >> accepted by the current maintainers. Is this right? > [1] is quite explicit: "Please note, that you are responsible for this > backport > from the time on when it was accepted on debian-backports. This means, you > have > to keep track of the changes in unstable, update your backport when a new > version enters testing and provide security updates when needed. If you are > not > willing or capable of doing this, you better ask someone else (e.g. on the > mentioned mailing list) to create and maintain the backport. > > So if you do not want to maintain the backport, you should not approach > the backport people for review Pretty clear. > > Did you really mean Jessie above? (The RFS said it should be for Stretch...) > Note that Jessie is old-stable. The rules are that you can only backport > versions that are in the next release. Stretch does not have 1.1, so 1.1 > cannot > be backported to Jessie. So you will need to backport it to "jessie-sloppy" > My bad, I was talking about Stretch really. >> In other case, I think I can follow your suggestion and create a >> wishlist bug against icecc too but I'd prefer follow up the more >> standard process. > > Yes, file a bug against the pacakge and ask for an backport (serverity > wishlist). Attach the diff as patch to the BTS and wait if the maintainer > picks > it up. OK. Thanks for your help.
Bug#881032: RFS: icecc/1.1-2~bpo9+1 NMU
On Fri, Feb 02, 2018 at 09:40:41AM +0100, Pablo Saavedra wrote: > Hello Tobias, thanks for put me in the right direction on this stuff. > > After reading again the established process in [1], I understand that > the recommended process is a bit different than for standard sponsorship > requests. Probably I should send the e-mail request with > debian-backpo...@lists.debian.org in the CC and ask for review and upload. > > My intention in this case is not become a maintainer but submit my icecc > package backported to Jessie with the idea of to be reviewed and > accepted by the current maintainers. Is this right? [1] is quite explicit: "Please note, that you are responsible for this backport from the time on when it was accepted on debian-backports. This means, you have to keep track of the changes in unstable, update your backport when a new version enters testing and provide security updates when needed. If you are not willing or capable of doing this, you better ask someone else (e.g. on the mentioned mailing list) to create and maintain the backport. So if you do not want to maintain the backport, you should not approach the backport people for review Did you really mean Jessie above? (The RFS said it should be for Stretch...) Note that Jessie is old-stable. The rules are that you can only backport versions that are in the next release. Stretch does not have 1.1, so 1.1 cannot be backported to Jessie. So you will need to backport it to "jessie-sloppy" > In other case, I think I can follow your suggestion and create a > wishlist bug against icecc too but I'd prefer follow up the more > standard process. Yes, file a bug against the pacakge and ask for an backport (serverity wishlist). Attach the diff as patch to the BTS and wait if the maintainer picks it up. > Thanks in advance. > [1] https://backports.debian.org/Contribute/ > > On Thu, 04 Jan 2018 12:34:36 +0100 Tobias Frost wrote: > > Control: tags -1 wontfix > > > > Hi Pablo, > > > > mmm, a backports upload is quite special.. > > > > looking for your name in the usual Debian locations, (DDPO, > > minechangelogs, contributors.d.o) I cannot find previous contributions > > with your name on it, so I cannot recommend that you do a backports > > upload as your very first contributions to Debian. (It could be that > > I've missed something, just let me know in this case) > > > > After all, when uploading to backports you commit yourself to maintain > > that package for a quite long time. See [1] for details. > > > > Many thanks for providing a backports pacakge. You maybe want to file > > a wishlist bug against icecc to ask for an backport of it and attach > > your diff as patch to it. > > > > Otherwise, be very welcome to contribute on other areas of Debian [2]! > > Backports is just advanced stuff, but there are many other > > opportunities to get you hands wet which would be more suitable. > > Pointers are all those orphaned packages[3] , bugs that are tagged > > newcomer [4] ... > > > > I'm tagging this bug "wontfix" for now. If you disagree with me on the > > above, feel free to remove the tag again but please expand a bit on > > my concerns and how you will adress them. > > > > As said, contributions are very welcome, but for backports you should > > have already some Debian experience... > > > > -- > > tobi > > > > > > [1] https://backports.debian.org/Contribute/ > > [2] https://wiki.debian.org/how-can-i-help > > [3] https://wnpp.debian.net/ > > [4] https://wiki.debian.org/BTS/NewcomerTag > > > > > > -- > Pablo Saavedra Rodiño > psaave...@igalia.com | Mail > www.igalia.com | Web >
Bug#881032: RFS: icecc/1.1-2~bpo9+1 NMU
Hello Tobias, thanks for put me in the right direction on this stuff. After reading again the established process in [1], I understand that the recommended process is a bit different than for standard sponsorship requests. Probably I should send the e-mail request with debian-backpo...@lists.debian.org in the CC and ask for review and upload. My intention in this case is not become a maintainer but submit my icecc package backported to Jessie with the idea of to be reviewed and accepted by the current maintainers. Is this right? In other case, I think I can follow your suggestion and create a wishlist bug against icecc too but I'd prefer follow up the more standard process. Thanks in advance. [1] https://backports.debian.org/Contribute/ On Thu, 04 Jan 2018 12:34:36 +0100 Tobias Frost wrote: > Control: tags -1 wontfix > > Hi Pablo, > > mmm, a backports upload is quite special.. > > looking for your name in the usual Debian locations, (DDPO, > minechangelogs, contributors.d.o) I cannot find previous contributions > with your name on it, so I cannot recommend that you do a backports > upload as your very first contributions to Debian. (It could be that > I've missed something, just let me know in this case) > > After all, when uploading to backports you commit yourself to maintain > that package for a quite long time. See [1] for details. > > Many thanks for providing a backports pacakge. You maybe want to file > a wishlist bug against icecc to ask for an backport of it and attach > your diff as patch to it. > > Otherwise, be very welcome to contribute on other areas of Debian [2]! > Backports is just advanced stuff, but there are many other > opportunities to get you hands wet which would be more suitable. > Pointers are all those orphaned packages[3] , bugs that are tagged > newcomer [4] ... > > I'm tagging this bug "wontfix" for now. If you disagree with me on the > above, feel free to remove the tag again but please expand a bit on > my concerns and how you will adress them. > > As said, contributions are very welcome, but for backports you should > have already some Debian experience... > > -- > tobi > > > [1] https://backports.debian.org/Contribute/ > [2] https://wiki.debian.org/how-can-i-help > [3] https://wnpp.debian.net/ > [4] https://wiki.debian.org/BTS/NewcomerTag > > -- Pablo Saavedra Rodiño psaave...@igalia.com | Mail www.igalia.com | Web
Bug#881032: RFS: icecc/1.1-2~bpo9+1 NMU
Control: tags -1 wontfix Hi Pablo, mmm, a backports upload is quite special.. looking for your name in the usual Debian locations, (DDPO, minechangelogs, contributors.d.o) I cannot find previous contributions with your name on it, so I cannot recommend that you do a backports upload as your very first contributions to Debian. (It could be that I've missed something, just let me know in this case) After all, when uploading to backports you commit yourself to maintain that package for a quite long time. See [1] for details. Many thanks for providing a backports pacakge. You maybe want to file a wishlist bug against icecc to ask for an backport of it and attach your diff as patch to it. Otherwise, be very welcome to contribute on other areas of Debian [2]! Backports is just advanced stuff, but there are many other opportunities to get you hands wet which would be more suitable. Pointers are all those orphaned packages[3] , bugs that are tagged newcomer [4] ... I'm tagging this bug "wontfix" for now. If you disagree with me on the above, feel free to remove the tag again but please expand a bit on my concerns and how you will adress them. As said, contributions are very welcome, but for backports you should have already some Debian experience... -- tobi [1] https://backports.debian.org/Contribute/ [2] https://wiki.debian.org/how-can-i-help [3] https://wnpp.debian.net/ [4] https://wiki.debian.org/BTS/NewcomerTag
Bug#881032: RFS: icecc/1.1-2~bpo9+1 NMU
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "icecc" * Package name : icecc Version : 1.1-2~bpo9+1 Upstream Author : schumac...@kde.org * URL : https://github.com/icecc/icecream * License : GNU General Public License v2.0 Section : devel I request for sponsorship for a backport of icecc (version 1.1-2) for stretch-backports. I'm not the maintainer, nor I'm involved with the development of this package on Debian. I'm CC'ing current maintainers. I have updated the changelog accordingly and rebuilt the package in a pristine environment (stretch cowbuilder). No more changes than updating the changelog were needed. After that I tested the package on a stretch machine and all works as expected. It builds those binary packages: icecc - distributed compiler (client and server) libicecc-dev - development files for icecc (distributed compiler) To access further information about this package, please visit the following URL: https://mentors.debian.net/package/icecc Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/i/icecc/icecc_1.1-2~bpo9+1.dsc Changes since the last upload: icecc (1.1-2~bpo9+1) stretch-backports; urgency=medium * Rebuild for stretch-backports. -- Pablo SaavedraMon, 06 Nov 2017 11:14:34 + Therefore, I request for sponsorship for this backport. Regards, Pablo Saavedra Rodiño signature.asc Description: OpenPGP digital signature