Re: RFS: nbc
Hi Sebastian, Dear mentors, I am looking for a sponsor for my package nbc. * Package name: nbc Version : 1.0.1.b35-1 Upstream Author : John Hansen bric...@comcast.net * URL : http://bricxcc.sourceforge.net/nbc/ * License : MPL Section : devel It builds these binary packages: nbc- Compiler for LEGO Mindstorms NXT The package appears to be lintian clean. The upload would fix these bugs: 518230 [...] Would you mind explaining why lazarus-ide is required to build this package? I'd strongly dislike installing all kinds of X libraries to build a package that is completely unrelated to X/GTK. Thanks, Michael pgpxpK1PXrMJ3.pgp Description: PGP signature
Re: RFS: nbc
On Thu, Mar 05, 2009 at 11:51:56AM +0100, Michael Tautschnig wrote: Hi Sebastian, Would you mind explaining why lazarus-ide is required to build this package? I'd strongly dislike installing all kinds of X libraries to build a package that is completely unrelated to X/GTK. Thanks, Michael Hi Michael, I also strongly dislike to install all kinds of X libraries for building the package and tried to avoid it, but nbc is using Graphics package from lazarus and the needed file[1] for this is unfortunately in the lazarus-ide package. -- Sebastian [1] lazarus-ide: /usr/lib/lazarus/lcl/units/$ARCH-linux/graphics.o signature.asc Description: Digital signature
Re: [RFS] python-lockfile 0.7-2
Ben Finney wrote: Howdy mentors, I am seeking a sponsor for my new package, ‘python-lockfile’ version 0.7-2. First of all, because you are not compiling anything, you don't have to build-depend on python-all-dev. In fact, you can simply build-depend on python [it's just copying the file to a directory]. And since you are using dh7, you can simplify your debian/rules even more. And using python-support instead of python-central would also reduce the complexity. And you should also install RELEASE-NOTES as changelog.gz, as specified in Policy 12.7: If an upstream changelog is available, it should be accessible as /usr/share/doc/package/changelog.gz in plain text. [...] If the upstream changelog files do not already conform to this naming convention, then this may be achieved either by renaming the files, or by adding a symbolic link, at the maintainer's discretion. BTW, have you considered to use the original license for your packaging as well? Because the time you add a patch to your package, the combination of both is GPL licensed as well. Using the same license as the upstream helps people to detect the correct license of the resulting work in an easier manner (and upstream maybe likes you more if you use the same license). Last but not least, I prefer to sponsor packages using a single revision for every upload made to Debian. And before I forget to ask, why do you want this package to get into Debian? Summary and other small issues --- debian/rules: - There is a char in line 23, which should not be there - The file could be much smaller by using dh's full power - RELEASE-NOTES should be installed as changelog debian/control: - Build-Depend on python instead of python-all-dev debian/copyright: - Update to the latest revision of the specification - Indent with one space, not with 4 spaces -- Julian Andres Klode - Free Software Developer Debian Developer - Contributing Member of SPI Ubuntu Member - Fellow of FSFE Website: http://jak-linux.org/ XMPP: juli...@jabber.org Debian: http://www.debian.org/ SPI: http://www.spi-inc.org/ Ubuntu: http://www.ubuntu.com/ FSFE: http://www.fsfe.org/ signature.asc Description: Digital signature
Re: RFS: gremind -- Simple reminder program for GNOME
Darren Salt li...@youmustbejoking.demon.co.uk wrote: I demand that Sebastian Krause may or may not have written... Being a Tk application tkremind is naturally ugly. When I tried out tkremind I didn't really like it. If this is because of aliased fonts, then installing tk8.5 and, if you can't get rid of 8.4, setting the 'wish' alternative appropriately will help: # update-alternatives --config wish I know, I use that for gitk. Still Tk is really ugly and even without Tk, tkremind wouldn't be my program of choice. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: greyfix
Dear mentors, I am looking for a sponsor for my package greyfix. * Package name: greyfix Version : 0.3.9-1 Upstream Author : Kim Minh Kaplan kaplan+grey...@kim-minh.comkaplan%2bgrey...@kim-minh.com * URL : http://www.kim-minh.com/pub/greyfix/ * License : IBM public license Section : mail It builds these binary packages: greyfix- Greylisting policy daemon for Postfix. The package appears to be lintian clean. The upload would fix these bugs: 515149 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/greyfix - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/greyfix/greyfix_0.3.9-1.dsc I would be glad if someone uploaded this package for me. Kind regards Ali MEZGANI
[UPLOADED] python-lockfile 0.7-2
Ben Finney ben+deb...@benfinney.id.au writes: I am seeking a sponsor for my new package, ‘python-lockfile’ version 0.7-2. Thanks to Kartik Mistry for giving feedback which led to a new release, 0.7-3; and for subsequently uploading that release to Debian. -- \ “Two hands working can do more than a thousand clasped in | `\ prayer.” —Anonymous | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [UPLOADED] python-lockfile 0.7-2
On Thu, Mar 5, 2009 at 22:32, Ben Finney ben+deb...@benfinney.id.au wrote: Ben Finney ben+deb...@benfinney.id.au writes: I am seeking a sponsor for my new package, ‘python-lockfile’ version 0.7-2. Thanks to Kartik Mistry for giving feedback which led to a new release, 0.7-3; and for subsequently uploading that release to Debian. Completely ignoring jak's suggestions? Consider them as soon as possible, because they are all correct (to my eyes). Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [RFS] python-lockfile 0.7-2
The package has now been uploaded, but Julian gives useful feedback which I'll respond to here. Julian Andres Klode j...@debian.org writes: First of all, because you are not compiling anything, you don't have to build-depend on python-all-dev. In fact, you can simply build-depend on python [it's just copying the file to a directory]. Don't I need to depend on ‘python-all’? Since the package is to be installed to *all* Python versions in Debian, not just the latest one. Also, should the build dependency on Python be ‘Build-Depends’ or ‘Build-Depends-Indep’? And since you are using dh7, you can simplify your debian/rules even more. And using python-support instead of python-central would also reduce the complexity. Thanks. I plan to migrate my packages to ‘python-support’, once the improved 0.90 series enters ‘testing’. And you should also install RELEASE-NOTES as changelog.gz, as specified in Policy 12.7: I considered that, but the file is quite out of date (at least four subsequent releases without any entry in the file). If the upstream changelog files do not already conform to this naming convention, then this may be achieved either by renaming the files, or by adding a symbolic link, at the maintainer's discretion. I agree that for this package, the content of ‘RELEASE-NOTES’ is pretty much that of a changelog. In general, though, what's the guideline for how non-changelog the file contents can be before it's not really appropriate to use it as the upstream changelog? Many upstream packages contain a “notes to the user about recent releases” file, which would be more appropriate as ‘NEWS’ in a Debian package. BTW, have you considered to use the original license for your packaging as well? For the packaging work which isn't modifying the upstream work, I intend to continue using GNU GPLv2+. Because the time you add a patch to your package, the combination of both is GPL licensed as well. Using the same license as the upstream helps people to detect the correct license of the resulting work in an easier manner (and upstream maybe likes you more if you use the same license). This is the first package where I've used ‘debian/patches/’; I hadn't thought about this issue. Thank you, you've convinced me that ‘debian/patches/*’ will be under the same license terms as the upstream work in any future release. Last but not least, I prefer to sponsor packages using a single revision for every upload made to Debian. Even if the ‘foo-x.y.z-3_source.changes’ contains all changes beginning with ‘foo-x.y.z-1’, as I've done with this package? I must agree with others in this forum that it's easier to track the differences between different releases if they actually have different release numbers. And before I forget to ask, why do you want this package to get into Debian? The upstream author is making an effort to provide a standard interface for Python lockfile semantics, which are currently rather fragmented in the standard library; I think this implementation and interface is good, and want to see this succeed. Also, I intend to make use of this package as a dependency for another one of my packages in future. debian/rules: - There is a char in line 23, which should not be there Normal white space: ASCII FF, a page break. I use them because they are useful for navigating a text file “by page” in the editor. debian/copyright: - Update to the latest revision of the specification I have been following the progress of the specification, and haven't seen any format changes that would affect any copyright file I work on. Can you point out the changes that affect this copyright file? - Indent with one space, not with 4 spaces What's the reasoning for that? Any indentation is sufficient for conforming with the format specification (since it's sufficient for conforming with the RFC2822 field format). Given the choice, I prefer to indent with 4 columns. Thanks very much for your feedback on my work. -- \ “I disapprove of what you say, but I will defend to the death | `\ your right to say it.” —Evelyn Beatrice Hall, _The Friends of | _o__) Voltaire_, 1906 | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [UPLOADED] python-lockfile 0.7-2
Sandro Tosi mo...@debian.org writes: On Thu, Mar 5, 2009 at 22:32, Ben Finney ben+deb...@benfinney.id.au wrote: Thanks to Kartik Mistry for giving feedback which led to a new release, 0.7-3; and for subsequently uploading that release to Debian. Completely ignoring jak's suggestions? Whoa there. I have no idea whether Kartik had seen Julian's feedback before uploading; that all happened during my down time. I'm merely reporting the result. Consider them as soon as possible, because they are all correct (to my eyes). Done, as soon as I saw it. Please consider that email messages take varying amounts of time to propagate, and that people live in varying time zones. -- \ “I lost a button-hole.” —Steven Wright | `\ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: fpm2 (updated package) - password manager
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for the new version 0.75-1 of my package fpm2. The upload would fix those bugs: #516196 Blowfish selftest failed: At startup password prompt. Please try again. Severity: important #493317 DEFAULTS is no longer the default on start-up Severity: wishlist It builds the binary package: fpm2 Description: a password manager with GTK+ 2.x GUI Figaro's Password Manager 2 (FPM2) is a program that allows you to securely store the passwords. Passwords are encrypted with the blowfish algorithm. . If the password is for a web site, FPM2 can keep track of the URLs of your login screens and can automatically launch your browser. In this capacity, FPM2 acts as a kind of bookmark manager. You can teach FPM2 to launch other applications, and optionally pass hostnames, usernames or passwords to the command line. . FPM2 also has a password generator that can choose passwords for you. It allows you to determine how long the password should be, and what types of characters (lower case, upper case, numbers and symbols) should be used. You can even have it avoid ambiguous characters such as a capital O or the number zero. The package is lintian clean. The package can be found on mentors.debian.net: - - dget http://mentors.debian.net/debian/pool/main/f/fpm2/fpm2_0.75-1.dsc I would be glad if someone uploaded this package for me. :-) Kind regards Wen-Yen Chuang - -- My GPG key is signed by Debian Developer Masayuki Hatta. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmwfeQACgkQdEpXpumNYVlYnQCfX+vKbw5BX5VR5iqbPNU5vwHz iJsAoJC4Jm3nAwYg+W+EEHV9z2aPLzMj =n5S3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: evilvte (updated package) - VTE terminal emulator
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for the new version 0.4.4-1 of my package evilvte. It builds the binary package: evilvte Description: an VTE based super lightweight terminal emulator evilvte is a terminal emulator. It supports almost everything VTE provides. It also supports tabs, tabbar autohide, and switch encoding at runtime. Configuration is via editing source code and recompilation. . This build provides all runtime changeable options in the right-click menu. The package is lintian clean. The package can be found on mentors.debian.net: - - dget http://mentors.debian.net/debian/pool/main/e/evilvte/evilvte_0.4.4-1.dsc I would be glad if someone uploaded this package for me. :-) Kind regards Wen-Yen Chuang - -- My GPG key is signed by Debian Developer Masayuki Hatta. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmwiqgACgkQdEpXpumNYVn0SgCfXVlpZNrlq59AuPApL34wWkxJ DdkAmgKhdg2djige5dlOnBEBg7sFPlRm =Sm4I -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: greyfix
On Fri, Mar 6, 2009 at 6:31 AM, mezgani ali hand...@gmail.com wrote: greyfix - Greylisting policy daemon for Postfix. We have several similar packages in Debian, could you explain why this one should be added? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [UPLOADED] python-lockfile 0.7-2
On Fri, Mar 6, 2009 at 01:38, Ben Finney ben+deb...@benfinney.id.au wrote: Sandro Tosi mo...@debian.org writes: On Thu, Mar 5, 2009 at 22:32, Ben Finney ben+deb...@benfinney.id.au wrote: Thanks to Kartik Mistry for giving feedback which led to a new release, 0.7-3; and for subsequently uploading that release to Debian. Completely ignoring jak's suggestions? Whoa there. I have no idea whether Kartik had seen Julian's feedback before uploading; that all happened during my down time. I'm merely reporting the result. So have another revision of that package uploaded in NEW to address them: you know that more than one version can live in NEW, ain't you? mailing ftpmas...@debian.org after that, to explain the situation, can be smart. -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [UPLOADED] python-lockfile 0.7-2
On Fri, Mar 6, 2009 at 12:44 PM, Sandro Tosi mo...@debian.org wrote: So have another revision of that package uploaded in NEW to address them: you know that more than one version can live in NEW, ain't you? mailing ftpmas...@debian.org after that, to explain the situation, can be smart. It will be nice! -- Cheers, Kartik Mistry | 0xD1028C8D | IRC: kart_ Debian GNU/Linux Developer Blog.en: ftbfs.wordpress.com Blog.gu: kartikm.wordpress.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [UPLOADED] python-lockfile 0.7-2
Sandro Tosi mo...@debian.org writes: On Fri, Mar 6, 2009 at 01:38, Ben Finney ben+deb...@benfinney.id.au wrote: Whoa there. I have no idea whether Kartik had seen Julian's feedback before uploading; that all happened during my down time. I'm merely reporting the result. So have another revision of that package uploaded in NEW to address them: Alternatively, instead of firing off new releases immediately, I can discuss feedback to better understand it and see what actually needs to be changed. Which is what I'm doing. -- \ “Yesterday I parked my car in a tow-away zone. When I came back | `\ the entire area was missing.” —Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
