Bug#721219: RFS: light-locker [ITP] -- simple session locker

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package light-locker * Package name: light-locker Version : 1.0.0-1 Upstream Author : Simon Steinbeiß si...@xfce.org * URL :

Sponsorship request

Can someone please sponsor https://mentors.debian.net/package/python-meld3 and https://mentors.debian.net/package/clipit ? meld3 is lintian clean and clipit is very close to. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#721208: Missed items in template

Good day, I noticed I missed the informational link in the RFS template. Please find out more about mugshot at the following link. http://www.smdavis.us/2013/07/27/mugshot-quick-and-easy-user-config/ Thank you, Sean Davis

Bug#721208: 0.1-6 uploaded

Hello mentors, I have uploaded 0.1-6 which makes the package lintian-clean. Please review my package for upload. Regards, Sean Davis

RFS: spotweb (uploaded new version to mentors)

Hi all, I've uploaded a new version of the spotweb package to mentors. This new version properly handles package upgrades by updating the database and includes a working watch file. The URL for spotweb at the mentors site is: http://mentors.debian.net/package/spotweb Alternatively, you can

Bug#683120: ITP missing for package yadifa with RFS 683120 with ITP in title

Hi, I would still like to see yadifa packaged, but I don't have any spare time at the moment. Could you rename the bug for me? thanks, Martijn On Wed, Aug 28, 2013 at 4:52 PM, Mònica Ramírez mon...@debian.org wrote: Hi, Are you still interested in packaging yadifa? If you are not, please

Bug#721208: 0.1-6 uploaded

Hi Sean, Several suggestions for you: debian/control: - change debhelper (=9.0.0) to debhelper (=9). - why you are using priority extra? Your package conflicts with other?[1] I suggest to use optional. - your VCS control is disabled... Please, enable it and use a VCS (can be

development needed for run-time

I'm working on packaging stan, which has an unusual structure. stanc, a binary, is the stan compiler. It converts stan code to C++, which it then hands to the C++ compiler. The user writes the stan code and then runs the resultant binary. As a result of this, files like headers and (probably)

Re: Upstream database update not in a single step

On 28-08-13 22:32, Jan-Pascal van Best wrote: I've extracted the update script from the indicated revision and all php files actually needed to run it. My current version of the package installs them into /usr/share/spotweb/db-update/version. postinst then checks whether the intermediate step

Re: Upstream database update not in a single step

I remember you said your package uses dbconfig-common. I assume you have this checking and versions performed by dbconfig-common. If not, why not? No, because dbconfig-common runs after the regular postinst script. The db-update script from the current installing version of the package is

Re: Upstream database update not in a single step

On 29-08-13 21:09, Jan-Pascal van Best wrote: I remember you said your package uses dbconfig-common. I assume you have this checking and versions performed by dbconfig-common. If not, why not? No, because dbconfig-common runs after the regular postinst script. But isn't that your choice?