Re: RFS: teseq
On Tue, Aug 12, 2008 at 09:50:47AM +0200, Evgeni Golov wrote: On Tue, 12 Aug 2008 04:00:05 + Joe Nahmias wrote: along with a proposed set of debtags[0] and I'll sponsor you. debtags do not belong into debian/control: http://debtags.alioth.debian.org/faq.html#integration-in-debian Never said they did. I just want the list so we can enter them in the debtags database. Regards Evgeni --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: joystick (updated package)
On Thu, Jul 24, 2008 at 12:11:48AM +0200, Stephen Kitt wrote: On Wed, 23 Jul 2008 07:45:56 +0200, Stephen Kitt [EMAIL PROTECTED] wrote: On Wed, 23 Jul 2008 02:04:41 +, Joe Nahmias [EMAIL PROTECTED] wrote: [snip] 2 - It doesn't look like it'd take too much to accomodate #475049 -- just a quick change and the writing of a short manpage. See if you can do this. I thought about handling this one as well, but evtest is also shipped in lineakd (with a manpage), so adding it would require some coordination. I suppose I could just add a Conflicts: and see if anyone complains, but it seems a bit late in the game to get this particular change done correctly and still have an updated package in Lenny, doesn't it? Actually lineakd diverts evtest and its manpage, so I can ship them in joystick without conflicting. Thanks! I'll upload a new version with 0 and 1 fixed as well as Ben's updated short description. In the end I've uploaded version -4 with 0, 1 and 2 fixed as well as Ben's updated short description. However, you don't mention evtest in the long description... Also, the manpage for inputattach seems very out of date, or just plain deficient. Finally, there are a bunch of lintian warnings that you should address. I fixed the first and uploaded. I'll leave the rest to you ;-) --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: freemat
On Mon, Jun 30, 2008 at 10:55:45AM +0200, Giuseppe Iuculano wrote: [snip] FreeMat is a free environment for rapid engineering and scientific prototyping and data processing. It is similar to commercial systems such as MATLAB from Mathworks, and IDL from Research Systems, but is Open Source. Can you explain how this package is better / different than octave? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ITR: libitpp (updated package)
On Mon, Jul 02, 2007 at 03:59:42PM +0530, Kumar Appaiah wrote: On 02/07/07, Neil Williams wrote: [snip] It only seems to increase the risk of mysterious bugs if you are using two different fortran libraries that are built against *VERY* different compilers : gcc-3.4 and gcc-4.2. Having one package depend on both libgfortran2 and libg2c0 could be a source of weird bugs. As maintainer of libitpp, it will be your job to fix them! (in conjunction with libitpp upstream). GnuCash has had similar problems - even now it still depends on libglib1 because of a dependency on an old library that has not been updated. (The bug report is over a year old now.) These things tend to bite eventually because the old library has to be removed from Debian at some point. Would you advise me to retain the lapack dependency and stay with refblas, or add the gsl dependency? Also, I am not clear how to avoid the lapack dependency, which forces me to depend on an old compiler. lapack would appear to be less of a potential headache than atlas and the way that the libraries are arranged means that atlas is still a usable alternative when installing the binaries. It is just worth being aware that lapack may complicate things when trying to fix bugs in libitpp. Well, since I have to depend lapack for features, I am unable to figure out a way to avoid the old gcc depends (through libg2c0). You might be interested to learn of the proposed release goal for lenny of removing g77/gcc-3.4 in favor of gfortran. Read all about it at: http://lists.debian.org/debian-toolchain/2007/07/msg0.html --Joe PS - I know nothing about fortran, just happened to read this thread and then read the about the transition on -release :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: open-invaders
On Thu, Jul 05, 2007 at 10:18:29PM +0200, Siegfried-Angel wrote: Dear mentors, I am looking for a sponsor for my package open-invaders. * Package name: open-invaders Version : 0.2-1 Upstream Author : Darryl LeCount * URL : http://www.jamyskis.net/invaders.php * License : GPLv2 Section : games It builds these binary packages: open-invaders - Space Invaders clone [snip] A few questions just from the RFS notice: Is this a new package? If so, there should be an ITP which is closed in the changelog. If there isn't one, please create one and ensure the bug is closed in the changelog. --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: ntfs-config
On Wed, Jun 27, 2007 at 12:56:12AM +0200, Francesco Namuri wrote: Dear mentors, I am looking for a sponsor for my package ntfs-config. * Package name: ntfs-config Version : 1.0-RC5-1 Upstream Author : Florent Mertens [EMAIL PROTECTED] * URL : http://givre.cabspace.com/ntfs-config/ * License : GPL Section : admin It builds these binary packages: ntfs-config - Enable/disable write support for any NTFS devices Can you please give more information about what ntfs-config actually does. Also, the URL above does not respond... Thanks, --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Extended RFS: rxvt, autofs, autofs5
On Fri, Jun 29, 2007 at 12:39:51AM +0200, Jan Christoph Nordholz wrote: Hi, Hello Jan, [snip] II. (already my package) Package Name: autofs Version:4.1.4+debian-2 [snip] III. (NEW package) Package Name: autofs5 Version:5.0.2-1 [snip] As an autofs user myself, I'd (selfishly) be willing to sponsor you. ;-) I'll take a look at the new versions you've prepared and contact you privately. Regards, Jan --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: package stuck in building state due to uninstallable build-deps
On Thu, Jun 07, 2007 at 04:49:59PM -0400, Bryan Donlan wrote: ping: does anyone have any advice? On 6/2/07, Bryan Donlan [EMAIL PROTECTED] wrote: Dear mentors, I'm the sponsored maintainer of the gimp-resynthesizer package. About a month ago, I had an upload sponsored for some minor cleanups. Currently, it's still in the 'building' state on sparc and mips[1]. I've taken a look at the buildd logs[2][3], and it seems that last month, it failed to build on those arches due to uninstallable build-deps. Will the buildds automatically requeue my package once the build-deps become installable? If not, is there a convenient way to know whether they're installable on those arches now? [snip] Normally, when this happens the buildd admin puts the package into a dep-wait state which means pretty much what it says. See http://www.debian.org/devel/buildd/wanna-build-states for more info. That doesn't seem to have happened in this case though... Try mailing the appropriate buildd admins at [EMAIL PROTECTED] --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: olive
Hello Arthur, On Mon, May 28, 2007 at 07:19:28PM +0200, Arthur Loiret wrote: Dear mentors, I am looking for a sponsor for my package olive. * Package name: olive Version : 1.3-1 Upstream Author : Shawn Boyette [EMAIL PROTECTED] * URL : http://mdxi.collapsar.net/hacks/olive/ * License : This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. Section : net It builds these binary packages: olive - console RSS reader [snip] We already have two text-based RSS readers in Debian: newsbeuter - text mode rss feed reader with podcast support snownews - Text mode RSS newsreader Can you elaborate how olive is different and what it would add to the archive above these two? [Full Disclosure: I co-maintain snownews] --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317155: RFP: ldtp -- GNU/Linux Desktop Testing Project
Package: wnpp Severity: wishlist * Package name: ldtp Version : 0.1.6 * URL : http://gnomebangalore.org/ldtp/ * License : GPL2 Description : GNU/Linux Desktop Testing framework GNU/Linux Desktop Testing Project (GNU/LDTP) is aimed at producing high quality test automation framework and cutting-edge tools that can be used to test GNU/Linux Desktop and improve it. It uses the Accessibility libraries to poke through the application's user interface. The framework has tools to generate AppMap by reading through the user interface components of an application. The framework also has tools to record test-cases based on user-selection on the application. GNU/LDTP core framework uses AppMap and the recorded test-cases to test an application and gives the status of each test-case as output. I would be willing to sponsor an NM if they want to package / maintain this. Otherwise, I'll probably do this myself sooner or later. --Joe [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Replacing a source package with two?
Hello Kari, On Fri, Jun 03, 2005 at 09:21:43AM +0300, Kari Pahula wrote: The package crossfire-maps-1.4.0-1 is currently based on a single source package. Upstream has split the maps in later versions to two map sets, -big and -small. I was thinking of handling this situation by making crossfire-maps-big and crossfire-maps-small and by putting to both of them: Conflicts: crossfire-maps Provides: crossfire-maps Replaces: crossfire-maps I would suggest to Provide crossfire-map (singular). Also, I would copy crossfire-maps' changelog to both -big and -small. Sure, can't hurt. crossfire-server and crossfire-maps have in them: Depends: crossfire-maps, ... I thought the crossfire-maps pkg is going away?! In any case, you should always include at least one real package. For example: Depends: crossfire-maps-small | crossfire-map Hope this helps, --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: maint-guide update (pbuilder, linda, orig.tar.gz etc.)
Hi Osamu, I found a number of corrections to make. I have attached my version and here is a wdiff from yours: =8=== 9.3 The orig.tar.gz file If you simply copy {+the+} contents of {+the+} debian/ directory from {+the+} old package into {+the+} new upstream version of {+the+} source tree and try to build package, you may end up with {+the+} unintended result of creating a native source [-package-] {+package,+} which comes without {+a+} diff.gz file. This type of packaging is {+only+} allowed for [-the packages-] {+software+} made [-only-] {+strictly+} for {+use in+} Debian. [2] [-Here,-] {+Otherwise,+} you must have the upstream [-tar ball-] {+tarball+} as {+an+} orig.tar.gz file in the parent directory. Usually, this [-tar ball-] {+tarball+} should untar to a source tree rooting from a directory with [-a-] {+the+} name packagename-upstream_version/. In this [-cases,-] {+case, the+} orig.tar.gz source file can be obtained by simply [-rename-] {+renaming the+} upstream [-tar ball-] {+tarball+} to [-the original file name-] packagename_upstream_version.orig.tar.gz . Please note that [-the-] 2 changes exist between {+the+} source tree directory name and the tar [-file name:-] {+filename:+} * Change {+the+} hyphen - {+between the package name and the version+} to {+an+} underscore _ * [-Add orig. before tar.gz.-] {+Append .orig.tar.gz+} The dh_make command usually takes care {+of the+} creation of {+the+} orig.tar.gz file. -- [2] Some people argue that, even for [-the-] Debian specific [-package,-] {+packages,+} it is [-a-] {+still+} better practice to package the contents of {+the+} debian/ directory [-residing not-] in [-the orig.tar.gz-] {+a diff.gz+} file [-but-] {+rather than+} in the [-diff.gz-] {+orig.tar.gz+} file. =8=== Feel free to ask any questions you have about my changes. Hope this helps, --Joe 9.3 The orig.tar.gz file If you simply copy the contents of the debian/ directory from the old package into the new upstream version of the source tree and try to build package, you may end up with the unintended result of creating a native source package, which comes without a diff.gz file. This type of packaging is only allowed for software made strictly for use in Debian. [2] Otherwise, you must have the upstream tarball as an orig.tar.gz file in the parent directory. Usually, this tarball should untar to a source tree rooting from a directory with the name packagename-upstream_version/. In this case, the orig.tar.gz source file can be obtained by simply renaming the upstream tarball to packagename_upstream_version.orig.tar.gz . Please note that 2 changes exist between the source tree directory name and the tar filename: * Change the hyphen - between the package name and the version to an underscore _ * Append .orig.tar.gz The dh_make command usually takes care of the creation of the orig.tar.gz file. -- [2] Some people argue that, even for Debian specific packages, it is still better practice to package the contents of the debian/ directory in a diff.gz file rather than in the orig.tar.gz file.
Re: RFS: ttf-dejavu -- bistream vera derivate with additional characters
Hello, On Wed, Nov 17, 2004 at 09:23:47PM +0100, Peter ernk wrote: Hello, I'm looking for someone willing to sponsor the dejavu fonts package. Package: ttf-dejavu Source Package : http://mentors.debian.net/debian/pool/main/t/ttf-dejavu/ Hmm, the source package only includes the pre-built .TTF files. AIUI, the TTF files are build from the SFD source; therefore, the source package should be based on dejavu-sfd-1.4.tar.gz, and then build-dep on fontforge to build the TTF files in debian/rules for the binary packages. Also, I do not see that you have filed an RFP for this package. Please do so and then close the bug in your debian/changelog. --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: ttf-dejavu -- bistream vera derivate with additional characters
Hello, On Wed, Nov 17, 2004 at 09:23:47PM +0100, Peter Černák wrote: Hello, I'm looking for someone willing to sponsor the dejavu fonts package. Package: ttf-dejavu Source Package : http://mentors.debian.net/debian/pool/main/t/ttf-dejavu/ Hmm, the source package only includes the pre-built .TTF files. AIUI, the TTF files are build from the SFD source; therefore, the source package should be based on dejavu-sfd-1.4.tar.gz, and then build-dep on fontforge to build the TTF files in debian/rules for the binary packages. Also, I do not see that you have filed an RFP for this package. Please do so and then close the bug in your debian/changelog. --Joe
Re: RFS: rdiff-backup (adopted)
Hello Alec, On Sun, Oct 24, 2004 at 09:52:19PM -0400, Alec Berryman wrote: Hi mentors, I adopted rdiff-backup and have a new revision ready that fixes ten outstanding bugs, leaving only one of non-wishlist priority. When I adopted rdiff-backup I received two sponsorship offers, but the individuals appear to be too busy at the moment. The package is lintian and linda clean, and has been working well for me the past month. I'm available again. So, if you still have not found a sponsor drop me a line privately. [1] http://www.thened.net/~alec/stuff/debian/rdiff-backup/13.4-4/ In the meantime, I'll take a look here. BTW, why do you not use the service at mentors.debian.net ? --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: rdiff-backup (adopted)
Hello Alec, On Sun, Oct 24, 2004 at 09:52:19PM -0400, Alec Berryman wrote: Hi mentors, I adopted rdiff-backup and have a new revision ready that fixes ten outstanding bugs, leaving only one of non-wishlist priority. When I adopted rdiff-backup I received two sponsorship offers, but the individuals appear to be too busy at the moment. The package is lintian and linda clean, and has been working well for me the past month. I'm available again. So, if you still have not found a sponsor drop me a line privately. [1] http://www.thened.net/~alec/stuff/debian/rdiff-backup/13.4-4/ In the meantime, I'll take a look here. BTW, why do you not use the service at mentors.debian.net ? --Joe