RFS: rednotebook

Dear mentors, Piotr is unable to sponsor rednotebook at the moment, so I'm seeking a sponsor for the new version until he's back online. It's a new upstream version only, no packaging changes, and targets unstable. The dsc is on mentors at

Best way to solve a file conflict between packages?

Hi mentors, I'm asking you help about bug #509367. Summarizing, new mono packages introduced a /usr/bin/csc file that conflicts with /usr/bin/csc I used to ship into chicken-bin, so now there's a conflict between these two packages. I think there're at least three possible ways to fix it: 1)

Re: Best way to solve a file conflict between packages?

On Mon, Mar 30, 2009 at 12:08:41PM +0200, Davide Puricelli wrote: I'm asking you help about bug #509367. Summarizing, new mono packages introduced a /usr/bin/csc file that conflicts with /usr/bin/csc I used to ship into chicken-bin, so now there's a conflict between these two packages. I

copyright, authors of little files in app

Hi, What if some of the used parts of the app are copyright by other authors? I've now: Copyright: Copyright (C) 1994-2008 Sean Bolton Copyright (C) 2001,2002 Nick Dowell. Copyright (C) 1999 S. J. Brookes. Copyright (C) 2002 Mats

ITS: rednotebook

Hi! Jonathan Wiltshire schrieb: The dsc is on mentors at http://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_0.6.4-1.dsc and is lintian clean. If you're able to review or sponsor, thanks in advance. I can take a look at it after lunch. Best regards, Alexander -- To

Re: Best way to solve a file conflict between packages?

Le Mon, Mar 30, 2009 at 12:08:41PM +0200, Davide Puricelli a écrit : Summarizing, new mono packages introduced a /usr/bin/csc file that conflicts with /usr/bin/csc I used to ship into chicken-bin, so now there's a conflict between these two packages. Hello Davide, This is covered by our

Re: copyright, authors of little files in app

Le Mon, Mar 30, 2009 at 12:35:01PM +0200, Grammostola Rosea a écrit : Hi, What if some of the used parts of the app are copyright by other authors? I've now: Copyright: Copyright (C) 1994-2008 Sean Bolton Copyright (C) 2001,2002 Nick Dowell. Copyright (C) 1999 S. J.

Re: Best way to solve a file conflict between packages?

Ciao Davide, On Mon, 30 Mar 2009 12:08:41 +0200, Davide Puricelli wrote: Summarizing, new mono packages introduced a /usr/bin/csc file that conflicts with /usr/bin/csc I used to ship into chicken-bin, so now there's a conflict between these two packages. I'm a bit biased here, since I'm part

[done] RFS: rednotebook

Alexander Reichle-Schmehl schrieb: The dsc is on mentors at http://mentors.debian.net/debian/pool/main/r/rednotebook/rednotebook_0.6.4-1.dsc and is lintian clean. I can take a look at it after lunch. Colleagues are busy; uploaded ;) -- To UNSUBSCRIBE, email to

Re: copyright, authors of little files in app

Le Mon, Mar 30, 2009 at 01:02:34PM +0200, Grammostola Rosea a écrit : And what about the years for the author? How define them? In my opinion, there is no need to be more precise as Upstream. If they provide a list or a collective name in their README file, and if their source tarball does not

Re: [done] RFS: rednotebook

On Mon, Mar 30, 2009 at 01:13:59PM +0200, Alexander Reichle-Schmehl wrote: Colleagues are busy; uploaded ;) Cheers :) -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature

(no subject)

From: rosea grammostola rosea.grammost...@gmail.com To: debian-mentors@lists.debian.org Subject: RFS: whysynth Dear mentors, I am looking for a sponsor for my package whysynth. * Package name: whysynth Version : 20080412-1 Upstream Author : Sean Bolton s...@smbolton.com * URL

RFS: whysynth

From: rosea grammostola rosea.grammost...@gmail.com To: debian-mentors@lists.debian.org Subject: RFS: whysynth Dear mentors, I am looking for a sponsor for my package whysynth. * Package name: whysynth Version : 20080412-1 Upstream Author : Sean Bolton s...@smbolton.com * URL

Re: RFS: whysynth

Le Mon, Mar 30, 2009 at 01:37:05PM +0200, Grammostola Rosea a écrit : * Package name: whysynth Version : 20080412-1 Upstream Author : Sean Bolton s...@smbolton.com * URL : http://www.smbolton.com/whysynth.html * License : GPLv3 Hi again, are you sure it is

Re: copyright, authors of little files in app

On Mon, 2009-03-30 at 15:23 +0400, Dmitry E. Oboukhov wrote: I had been rejected from NEW-stage a few times because some copyright records was not included into the debian/copyright. Since last reject I have been doing grep -ir '(c)' . in src-tree and add results into debian/copyright. It

Re: RFS: whysynth

Charles Plessy wrote: Le Mon, Mar 30, 2009 at 01:37:05PM +0200, Grammostola Rosea a écrit : * Package name: whysynth Version : 20080412-1 Upstream Author : Sean Bolton s...@smbolton.com * URL : http://www.smbolton.com/whysynth.html * License : GPLv3 Hi

Re: copyright, authors of little files in app

On 20:04 Mon 30 Mar , Chow Loong Jin wrote: CLJ On Mon, 2009-03-30 at 15:23 +0400, Dmitry E. Oboukhov wrote: I had been rejected from NEW-stage a few times because some copyright records was not included into the debian/copyright. Since last reject I have been doing grep -ir '(c)' . in

Re: RFS: whysynth

Le Mon, Mar 30, 2009 at 01:52:16PM +0200, Grammostola Rosea a écrit : In my Debianized package, copyright file says: License: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software

Re: copyright, authors of little files in app

Charles Plessy wrote: Le Mon, Mar 30, 2009 at 12:35:01PM +0200, Grammostola Rosea a écrit : Hi, What if some of the used parts of the app are copyright by other authors? I've now: Copyright: Copyright (C) 1994-2008 Sean Bolton Copyright (C) 2001,2002 Nick Dowell. Copyright

How to depend on 32bit libs on amd64? (and what to do with ia32-libs)

ftpmaster: Please comment on the last section concerning DAK behaviour. Hi, before Lenny ftpmaster asked us (ia32-libs maintainers) to do something about the mess that is ia32-libs. Specifically that it is a HUGE source duplication and a security nightmare. Unfortunaetly there wasn't enough time

Re: RFS: whysynth

Charles Plessy wrote: Le Mon, Mar 30, 2009 at 01:52:16PM +0200, Grammostola Rosea a écrit : In my Debianized package, copyright file says: License: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published

Re: RFS: whysynth

Grammostola Rosea wrote: Charles Plessy wrote: Le Mon, Mar 30, 2009 at 01:37:05PM +0200, Grammostola Rosea a écrit : * Package name: whysynth Version : 20080412-1 Upstream Author : Sean Bolton s...@smbolton.com * URL : http://www.smbolton.com/whysynth.html * License

Re: copyright, authors of little files in app

On 20:12 Mon 30 Mar , Charles Plessy wrote: CP Le Mon, Mar 30, 2009 at 01:02:34PM +0200, Grammostola Rosea a écrit : And what about the years for the author? How define them? CP In my opinion, there is no need to be more precise as Upstream. If they provide CP a list or a collective name

Re: How to depend on 32bit libs on amd64? (and what to do with ia32-libs)

Goswin von Brederlow, le Mon 30 Mar 2009 14:33:32 +0200, a écrit : Ia32-apt-get provides wrappers for dpkg.deb and apt-get that allow installing deb packages from an i386 repository (or local file) directly. Mmm, couldn't there be any possible relation with the multiarch support mentioned

Re: Best way to solve a file conflict between packages?

Hello, On Mon, 30 Mar 2009, Davide Puricelli wrote: I'm asking you help about bug #509367. As you can imagine similar problems have come-up in the past. 2) just putting a Conflicts between mono-devel and chicken-bin, but I think it's not a good solution for users. This is not correct since

Re: RFS: whysynth

Grammostola Rosea wrote: Charles Plessy wrote: Le Mon, Mar 30, 2009 at 01:52:16PM +0200, Grammostola Rosea a écrit : In my Debianized package, copyright file says: License: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General

Re: RFS: whysynth

Le Mon, Mar 30, 2009 at 02:39:51PM +0200, Grammostola Rosea a écrit : I've it now like this: http://pastebin.com/m79eaf139 Hi again, this is a much better copyright file. Unless you have reasons to disallow your packaging work to be relicensed to a later version of the GPL (Upstream may

Re: RFS: whysynth

Charles Plessy wrote: Le Mon, Mar 30, 2009 at 02:39:51PM +0200, Grammostola Rosea a écrit : I've it now like this: http://pastebin.com/m79eaf139 Hi again, this is a much better copyright file. Unless you have reasons to disallow your packaging work to be relicensed to a later

Re: How to depend on 32bit libs on amd64? (and what to do with ia32-libs)

* Goswin von Brederlow [Mon, 30 Mar 2009 14:33:32 +0200]: Hello, [-mentors only Bcc'ed to drop it from the discussion] Executive summary: concerns about ia32-apt-get raised, lesser hack proposed for comments. before Lenny ftpmaster asked us (ia32-libs maintainers) to do something about

RFC: dma -- the DragonFly Mail Agent

Dear mentors, This is not even an RFS :) Now, seriously - I've prepared a package for dma, the DragonFly Mail Agent, as ITP'd in my #511410, I've uploaded it to mentors.d.n, and I've sent out a request for debconf translations. The call for translations should hit the -i18n list in a couple of

Re: How to depend on 32bit libs on amd64? (and what to do with ia32-libs)

Samuel Thibault samuel.thiba...@ens-lyon.org writes: Goswin von Brederlow, le Mon 30 Mar 2009 14:33:32 +0200, a écrit : Ia32-apt-get provides wrappers for dpkg.deb and apt-get that allow installing deb packages from an i386 repository (or local file) directly. Mmm, couldn't there be any

uploading for the 2nd time

Hi, I changed something in my packages and want to upload them again. But it says: $ sudo dupload -t mentors whysynth_20080412-1_i386.changes dupload note: no announcement will be sent. Checking signatures before upload..signatures are ok Uploading (ftp) to mentors.debian.net:/ [ job

Building outside of build directory (build error on power pc etc)

Hi, The above issue hit my package, and I'd very much like someone to check it is no longer happening: http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=siege I have tested this myself under pbuilder. It does not seem to be causing errors now, but would appreciate

Re: uploading for the 2nd time

On Mon, Mar 30, 2009 at 07:23:19PM +0200, Grammostola Rosea wrote: I changed something in my packages and want to upload them again. But it says: $ sudo dupload -t mentors whysynth_20080412-1_i386.changes whysynth_20080412-1_i386.changes ok, already done for mentors ] Nothing to upload

RFS: libdrizzle

Dear mentors, I am looking for a sponsor for my package libdrizzle. * Package name: libdrizzle Version : 0.2.0-1 Upstream Author : Eric Day * URL : http://launchpad.net/libdrizzle * License : BSD Section : libs It builds these binary packages:

Re: RFS: whysynth

Grammostola Rosea wrote: From: rosea grammostola rosea.grammost...@gmail.com To: debian-mentors@lists.debian.org Subject: RFS: whysynth Dear mentors, I am looking for a sponsor for my package whysynth. * Package name: whysynth Version : 20080412-1 Upstream Author : Sean Bolton

RFS: smoviedb

Dear mentors, I am looking for a sponsor for my package smoviedb. * Package name: smoviedb Version : 0.80-1 Upstream Author : Victor J Chamorro * URL : http://sourceforge.net/projects/smoviedb, http://smoviedb.sourceforge.net * License : GNU/GPL v2

/doc and/or manpage

Hi, My package does have an /doc folder. Does it mean that there is some documentation which I should include in the package? How? Besides that, should each package have an manpage? How should I create one? What if an package has an documentation, should there also be an manpage? What is

Re: /doc and/or manpage

On Mon, Mar 30, 2009 at 08:39:58PM +0200, Grammostola Rosea wrote: My package does have an /doc folder. Does it mean that there is some documentation which I should include in the package? How? Do the contents look useful to a user? If so, they should be installed into /usr/share/doc/package.

Scripts in upstream sources

Hi mentors, In a package the upstream programmers have included some PERL scripts that are based on a manual PERL installation (/usr/local/...). How do i manage to include these scripts in path /usr/{sbin|bin} ? Have i to patch these scripts and review them to put parameters in a file located in

Re: Scripts in upstream sources

On Mon, 30 Mar 2009 21:09:06 +0200 Laurent Guignard lguignard.deb...@gmail.com wrote: In a package the upstream programmers have included some PERL scripts that are based on a manual PERL installation (/usr/local/...). These references will need to be modified. How do i manage to include

Re: Scripts in upstream sources

On Mon, 30 Mar 2009 20:29:14 +0100, Neil Williams wrote: On Mon, 30 Mar 2009 21:09:06 +0200 Laurent Guignard lguignard.deb...@gmail.com wrote: [...] If the perl scripts are package specific, there is no need to put them in /usr/bin, they can go into /usr/share and the rest of the package

Re: Scripts in upstream sources

On Mon, 30 Mar 2009 21:47:37 +0200 Laurent Guignard lguignard.deb...@gmail.com wrote: On Mon, 30 Mar 2009 20:29:14 +0100, Neil Williams wrote: On Mon, 30 Mar 2009 21:09:06 +0200 Laurent Guignard lguignard.deb...@gmail.com wrote: [...] If the perl scripts are package specific, there is

Re: Scripts in upstream sources

Le Mon, Mar 30, 2009 at 09:47:37PM +0200, Laurent Guignard a écrit : How to document these scripts if they are located in /usr/share (man or /usr/share/doc) ? Hi Laurent, since it is Perl script, the embedded POD (“plain old documentation”) format is probably the best way to document their

RFS: siege [fix for build breaking due to $HOME write attempt]

Dear mentors, I am looking for a sponsor for the new version 2.67-3 of my package siege. It builds these binary packages: siege - HTTP regression testing and benchmarking utility The package appears to be lintian clean. The upload would fix these bugs: 321816 The package can be found on

Re: Building outside of build directory (build error on power pc etc)

On Tue, Mar 31, 2009 at 1:27 AM, Tristan Greaves tris...@extricate.org wrote: I'm wondering if there is a simple way when running pbuilder to 'see' if it has put any files in $HOME ? If it completes successfully, it clears its staging area, so I can't go in afterwards to see what it did.