Bug#838939: RFS: devtodo/0.1.20-6.1 [NMU]
Hi, >One thing I noticed here was the bash-completion file which is not being >packaged for some reason. >Is that expected? I don't know, if it works... you can add it! Just open a new bug, propose a patch and then ask for a new NMU if you want :) >I will look into that and reupload. somebody already uploaded the package, so I guess I have nothing left to sponsor ;) (sorry for not answering before!) G.
Bug#838939: RFS: devtodo/0.1.20-6.1 [NMU]
Hi Gianfranco! On 09/28/2016 11:42 AM, Gianfranco Costamagna wrote: > I would expect some changes more if you want > > > (note: they are usually out of an NMU scope, but with a maintainer mostly > MIA, and a package > RC buggy since 3 years, I think some work might be nice). I think I will stick with nmu this time around, because I'm afraid I am a little busy lately :/ > other stuff is good > (I suggest you to run meld on build log files and debdiff on built deb files > to see if changes are good or not > other than by testing the package :p ) One thing I noticed here was the bash-completion file which is not being packaged for some reason. Is that expected? > > Of course if you don't want, or you are out of time, I can sponsor it as-is, > maybe with a revert of the > std-version bump (or a mention in changelog, even if policy forbids changes > of it for NMUs) I will look into that and reupload. Thank you! -- Fernando Seiti Furusato IBM Linux Technology Center signature.asc Description: OpenPGP digital signature
Bug#838939: RFS: devtodo/0.1.20-6.1 [NMU]
control: owner -1 ! control: tags -1 moreinfo Hi Fernando >I am looking for a sponsor for my package "devtodo" I would expect some changes more if you want (note: they are usually out of an NMU scope, but with a maintainer mostly MIA, and a package RC buggy since 3 years, I think some work might be nice). e.g. 1) you bumped std-version, please mention in changelog. 2) you might want to convert VCS fields in https mode and push changes on collab-maint Vcs-Git: https://git.debian.org/git/collab-maint/devtodo.git Vcs-Browser: https://git.debian.org/cgit/collab-maint/devtodo.git 3) you might consider a Team upload (collab-maint). It is not written in policy, but some people thinks collab-maint is a team, and then you can team upload if you are part of it. (really border-line thinking) 4) debhelper >=9 or 10 and compat 9 or 10 5) modernize rules file (a.k.a. drop mostly everything):q 6) d/clean should be useless now 7) check if d/dirs and so on are still useful other stuff is good (I suggest you to run meld on build log files and debdiff on built deb files to see if changes are good or not other than by testing the package :p ) Of course if you don't want, or you are out of time, I can sponsor it as-is, maybe with a revert of the std-version bump (or a mention in changelog, even if policy forbids changes of it for NMUs) G.
Bug#838939: RFS: devtodo/0.1.20-6.1 [NMU]
Package: sponsorship-requests Severity: important X-Debbugs-Cc: bren...@br.ibm.com Dear mentors, I am looking for a sponsor for my package "devtodo" * Package name: devtodo Version : 0.1.20-6.1 Upstream Author : Alec Thomas* URL : http://swapoff.org/DevTodo * License : GPLv2 Section : utils It builds those binary packages: devtodo- hierarchical, prioritised todo list manager To access further information about this package, please visit the following URL: https://mentors.debian.net/package/devtodo Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/devtodo/devtodo_0.1.20-6.1.dsc Changes since the last upload: * Non-maintainer upload. * debian/control: added dh-autoreconf as build-dep, removed its dependencies and added libtool-bin to fix ftbfs. (Closes: #779551, #723964) * debian/rules - added usage of dh-autoreconf - expanded dh clean to include dh_autoreconf_clean before dh_clean Regards, Fernando Seiti Furusato signature.asc Description: OpenPGP digital signature