Re: Bug#658204: RFS: bibtool -- tool for BibTeX database manipulation

> I tried to fix the warnings emitted by lintian, but the lintian on my > boxdoes not report the one above: > how can I reproduce this report. Use the Lintian version in backports (or in Sid). Do not use the version in Stable. It is not updated. -- To UNSUBSCRIBE, email to debian-mentors-requ..

Re: notify command

E.g.: user@home ~> sudo apt-get install csh > /dev/null user@home ~> csh % notify notify: No current job. % exit user@home ~> sudo apt-get remove -y csh > /dev/null -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@

RFS: fizsh

Dear mentors, I am looking for a sponsor for my package "fizsh". * Package name: fizsh Version : 1.0.2-1 Upstream Author : Guido van Steen (myself) * URL : http://sourceforge.net/projects/fizsh/ * License : Modified BSD License Section

Re: RFS: fizsh

age. It says they might be intended as minus signs. However, the hyphens used are intended to be actual hyphens. I will clarify this by using "\(hy" in the next release upstream. Best wishes, Guido van Steen On Sat, Aug 20, 2011 at 10:05 PM, Guido van Steen wrote: > Dear mentor

Re: RFS: pygtkplot

Dear Vincent, and other mentors, I read in Vincent's mail WRT the "pygtkplot" package that this package should contain a debian/copyright file "using DEP-5." I have issued a RFS for another package, which is called Fizsh (see: http://lists.debian.org/debian-mentors/2011/08/msg00466.html). So far,

Re: RFS: pygtkplot

Thanks! I have corrected the watch file, and rewritten the copyright file to conform to DEP 5 policy. Guido On Mon, Aug 22, 2011 at 11:31 AM, Vincent Cheng wrote: > On Sun, Aug 21, 2011 at 9:15 PM, Guido van Steen > wrote: >> To be honest, I had never heard of a "DEP-5 requir

Re: Cavalry

Noone said that your package is not very useful. Debian provides an enormous set of packages. Therefore, the people here would like to see what your package has to to offer in addition to what is available in Debian already. You have to convince them of the usefulness of your package. * Explain h

Re: RFS: fizsh

Dear Michael, and other mentors, Thank you very much for reviewing my package! I corrected the errors you spotted. I also added a "lintian-override" file to suppress the lintian "hyphen-used-as-minus-sign" tag. (This "override-file" will not be needed anymore when Upstream releases a newer versio

Re: RFS: fizsh

Hi Michael, Thanks for looking at my package again. > - why not fix the hyphen-used-as-minus-sign via a patch instead of overriding > the warning? Overriding a correct warning for the mere reason of silencing > lintian seems to be of no use. I first tried to create a patch, but I could not add

Re: RFS: fizsh

ch for all your help! Guido On Sun, Sep 4, 2011 at 7:36 PM, Guido van Steen wrote: > Hi Michael, > > Thanks for looking at my package again. > >> - why not fix the hyphen-used-as-minus-sign via a patch instead of overriding >>  the warning? Overriding a correct warnin

Re: RFS: fizsh

Hi Michael. That is excellent news. Thank you very much! Guido On Mon, Sep 5, 2011 at 1:06 AM, Michael Tautschnig wrote: > Hi Guido, > >> I fixed the two remaining issues (added a patch for the man page, and >> used dput to upload the original version of fizsh_1.0.2.orig.tar.gz). >> > [...] >

Fwd: Packaging php app/scripts

I forgot to cc the list: -- Forwarded message -- From: Guido van Steen Date: Tue, Sep 6, 2011 at 10:00 AM Subject: Re: Packaging php app/scripts To: kuLa Hi KuLa, > I forgot one IMHO important info there is no makefile for this project > as php is not compilable. How a

Fwd: Packaging php app/scripts

Fwd-ed to the list... -- Forwarded message -- From: Guido van Steen Date: Tue, Sep 6, 2011 at 5:52 PM Subject: Re: Fwd: Packaging php app/scripts To: kuLa > Ok, I created simple Makefile (content below): > prefix := /tmp > DESTDIR:= $(prefix)/var/www > SRC

Re: RFS: sxiv

sxiv is in sid already... On Thu, Sep 8, 2011 at 10:02 AM, Thomas Goirand wrote: > On 09/08/2011 12:44 PM, Daniel Echeverry wrote: > > Hi, > > > > 2011/9/7 Jakub Wilk mailto:jw...@debian.org>> > > > > * Daniel Echeverry > >, 2011-09-07, 16:15: > > > >

syntax-error-in-dep5-copyright syntax error in section 4 after the tag license

sh Upstream-Contact: Guido van Steen Source: http://sourceforge.net/projects/fizsh/ Files: * Copyright: 2011, Guido van Steen License: BSD-3-clause~FIZSH Files: scripts/*highlighter* Copyright: 2010-2011, zsh-syntax-highlighting contributors License: BSD-3-clause~zsh-syntax-highlighting contribut

Re: syntax-error-in-dep5-copyright syntax error in section 4 after the tag license

Hi Charles and Jan Pascal, Thanks for your help. Your tips on 'space dots' got me on the right track. I also had to include the plain text of an identical BSD license twice, because it appeared in two different sections of my copyright file. Best wishes, Guido On Wed, Oct 12, 2011 at 8:17 AM, J

Re: syntax-error-in-dep5-copyright syntax error in section 4 after the tag license

> You never need to duplicate license text in a DEP 5 document > http://dep.debian.net/deps/dep5/#stand-alone-license-paragraph>. Thank you, Ben! I have updated my copyright file one more time, although Lintian did not complain about the remaining mistakes in the previous version. -- To UNSUBSC

Re: syntax-error-in-dep5-copyright syntax error in section 4 after the tag license

> > http://ddumont.wordpress.com/2011/01/13/debian-copyright-dep5-parsereditorvalidatormigrator-is-released/ It seems a good idea to me to integrate a recent version of this libconfig-model-perl with lintian. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject o

Re: syntax-error-in-dep5-copyright syntax error in section 4 after the tag license

Stupid fools who depend on Lintian :-) Isn't there enough for them to learn!? On Thu, Oct 13, 2011 at 11:21 PM, Ben Finney wrote: > Guido van Steen writes: > >> > You never need to duplicate license text in a DEP 5 document >> > http://dep.debian.net/deps/dep5/#

Re: Upstream changelog name change

> there? (I use debhelper -8.9.0ubuntu1). Are you packaging for Debian of for Ubuntu? If I packaged for Debian I would not use an Ubuntu version of debhelper... On Mon, Oct 17, 2011 at 3:28 PM, Ole Streicher wrote: > Ansgar Burchardt writes: >> Ole Streicher writes: >>> my upstream package has

Re: Python build dependencies

Sorry for being a bit unclear. Instead of: > It is not completely clear to me why get this warning. Why do I do NOT > need Python to build the package? Is python needed for debhelper? In > that case should python not be included as a build-depend as well? I meant: > It is not completely clear t

RFS: fizsh (already in Debian, new upstream version 1.0.4)

Dear mentors, I am looking for a sponsor for my package "fizsh". * Package name: fizsh Version : 1.0.4-1 Upstream Author : Guido van Steen (myself) * URL : http://sourceforge.net/projects/fizsh/ * License : Modified BSD License Section

Re: Python build dependencies

Hi David, > Try to build your package in a clean chroot: you'll probably won't have that > message anymore. Thank you. I created a clean chroot, and the python warning disappeared indeed. Best wishes, Guido -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of

Re: Re: Fwd: RFS: kpartsplugin (updated package)

>> Yet there is one lintian warning to be addressed in future uploads: >> >> W: kpartsplugin source: syntax-error-in-dep5-copyright syntax error in > section 4 after the tag license:  You may use this file under the terms of the > BSD license as follows:\n > > I didn't get that lintian warning on m

Re: RFS: fizsh (already in Debian, new upstream version 1.0.4)

Dear Michael and other mentors, An annoying bug in the upstream source of fizsh version 1.0.4 has been discovered, and fixed. Therefore, upstream has released a new bug-fix version 1.0.5. This is why I withdraw this RFS, which is related to the version 1.0.4. I will upload a packaged version of f

RFS: fizsh (already in Debian, new upstream version 1.0.5)

Dear Michael, and other mentors, I am looking for a sponsor for my package "fizsh". * Package name: fizsh Version : 1.0.5-1 Upstream Author : Guido van Steen (myself) * URL : http://sourceforge.net/projects/fizsh/ * License : Modified BSD Licens

Re: Need assistance in packaging / Brauche Hilfe bei der Erstellung von Paketen

The perl program pod2man may interest you if you want to construct a nice looking man page without too much effort. On Mon, Nov 7, 2011 at 2:56 PM, Martin Eberhard Schauer wrote: > Dear Björn, > > perhaps you are also interested in having a look at > man.7 and man-pages.7. They have an up to date

Re: Adopt an abandoned ITP?

Obviously, you should give the ITP/RFP bug author much more than a few days to respond... Have you mentioned your interest to the bug page? I would try to contact the bug author at least a few more times. On Tue, Nov 8, 2011 at 12:21 PM, Gergely Nagy wrote: > Mathias Ertl writes: > >> There is

Re: Adopt an abandoned ITP?

You could also offer to co-maintain... On Tue, Nov 8, 2011 at 12:36 PM, Guido van Steen wrote: > Obviously, you should give the ITP/RFP bug author much more than a few > days to respond...  Have you mentioned your interest to the bug page? > I would try to contact the bug author at le

Re: RFS: nbc (2nd try)

> Restrictions > Without the expressed, written consent of the Author, you may NOT: > * distribute modified versions of TGIFImage, in whole or in part. > * rent or lease TGIFImage. > * sell any portion of TGIFImage on its own, without integrating it into > your Applications as Executable Cod

Re: RFS: yubiserver

Hi Nanakos, I am not a Debian Developer, so I cannot sponsor anyway. However, I am interested in your package. Yet, I am getting a configure error: "configure: error: cannot find install-sh, install.sh, or shtool in build-aux "."/build-aux" Do I miss something? Best wishes, Guido -- To UNS

Bug#751048: RFS: fizsh/1.0.6-1 (already in Debian)

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "fizsh". * Package name: fizsh Version : 1.0.6-1 Upstream Author : Guido van Steen (myself) * URL : http://sourceforge.net/projects/fizsh/

Bug#751048: Sponsorship of newer Fizsh package

kage to have > the version 1.0.6-1, too.) > > On Sun, Jun 08, 2014 at 11:21:03AM +0200, Guido van Steen wrote: > > I have just uploaded a new version of Fizsh to Sourceforge. This is > version > > 1.0.6. I have also uploaded the corresponding Debian source package to >

Bug#751048: Sponsorship of newer Fizsh package

Hi Axel, I noticed some bugs in version 1.0.6 of fizsh. Most of them were related to my treatment of autoconf and friends. Therefore, I decided to release version 1.0.7, which corrects these bugs. I have also uploaded the new version to mentors: > dget -x http://mentors.debian.net/debian/pool/mai

Bug#751048: Sponsorship of newer Fizsh package

Hi Axel, } Thanks for the notice. Maybe this was the cause of this unexpected } closing of this bug report... Then again "Package fizsh has been } removed from mentors." sounded as if it was removed from mentors and } not updated... This may have happened because the original bug report explicitl

Re: how to properly remove an empty config directory

> 3. remove the empty directory /etc/apt.conf.d that shouldn't exits. More precise: 3. remove the empty directory /etc/apt.conf.d if it is empty. Best wishes, Guido van Steen

Re: how to properly remove an empty config directory

> well, the command rmdir only removes a dir when it is empty. The command rmdir wasn't mentioned in this thread. The OP said "remove the empty directory /etc/apt.conf.d that shouldn't exits".

Bug#752301: RFS: fizsh/1.0.7-1 (already in Debian)

Upstream Author : Guido van Steen (myself) * URL : http://sourceforge.net/projects/fizsh/ * License : Modified BSD License Section : shells It builds those binary packages: * fizsh - Friendly Interactive ZSHell The Fizsh packages provides an easy interface to Zsh

Re: Bug#752782: RFS: kvmcs-server_0.4.0 server part in kvm client server environment

-native is needed indeed. What you should do is explained quite well in the packaging guide lines (https://www.debian.org/doc/manuals/maint-guide/). Best wishes, Guido van Steen

Re: Bug#752782: RFS: kvmcs-server_0.4.0 server part in kvm client server environment

as per https://wiki.debian.org/DebianMentorsFaq# What.27s_wrong_with_upstream_shipping_a_debian.2F_directory.3F). ​* Upload both the adjusted original package and the debian package. Best wishes, Guido van Steen

Re: Bug#752782: RFS: kvmcs-server_0.4.0 server part in kvm client server environment

Hi Willem, Your kvmcs software looks very promising! I have one more question: Why are the server and the client packages conflicting? I have not tried it, but couldn't it in some way be useful to have both client and server installed at the same machine? Best wishes Guido

Re: Licensing question

Hi Eric, It looks like your question has been discussed before: https://lists.debian.org/debian-legal/2012/12/msg00020.html In the thread Charles Plessy argues that the licence seems to lack the right to "disseminate modified information", which would make it non-free from a Debian perspective. C

Re: About debuild -i

} I found that if I use -i I will get the following problems, whereas if -i } is omitted, then they won't show up. } } I: ddclient: unused-debconf-template ddclient/hostslist } I: ddclient: unused-debconf-template ddclient/blankhostslist I cannot replicate this. AFAIK the debuild parameter "-i"

Re: Autoreconfing guide

> I've written a wiki page on how and when to use dh-autoreconf and > autotools-dev. Could you provide an url? Thank you! Guido van Steen -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lis

Re: Autoreconfing guide

Hi Wooky, } https://wiki.debian.org/Autoreconf Your wikipage looks very good! Thanks! I maintain a package that does not need any compiling. Still upstream development is done using autoconf and autotools. Building the Debian package yields a single binary package for all architectures. AFAIK in

Re: Autoreconfing guide

} but I think the Autoconf and Automake files are better treated as source, } and the generated files regenerated on every build. I thought that regenerating generated files was achieved by adding build-depends on autoconf and automake, and that autoreconf was only needed to generate config.guess

Re: ghdl package has been removed from Mentors

I agree with Joris. Users are not properly informed that discussions on mentors.debian.net may be automatically lost after a package is removed from mentors.debian.net. This should be changed. I would rather see the information backed-up in some way before it is deleted. Does this require a bug r

Re: ghdl package has been removed from Mentors

} IMHO, the right place for discussing a particular package is it's ITP } bug (when the package is prospective) or the RFS bug. AFAIAA there is no ITP or RFS for the package debexpo (the software at issue, which is running at mentors.debian.net). Guido -- To UNSUBSCRIBE, email to debian-mentor

Re: ghdl package has been removed from Mentors

Hi Thibaut, } this is not what I mean: I don't like the "comments" feature of debexpo, } my opinion is that comments on a to-be-sponsored package should be sent } to the corresponding RFS bug. Sorry for my misunderstanding. Yes, comments could indeed be "referred" to the RFS/ITP bug. Debexpo coul

Re: ghdl package has been removed from Mentors

I have just submitted the issue as bug# 314771. On Mon, Jul 21, 2014 at 5:17 PM, Guido van Steen wrote: > Hi Thibaut, > > } this is not what I mean: I don't like the "comments" feature of debexpo, > } my opinion is that comments on a to-be-sponsored packag

Bug#759742: (RFS: tkinfo/2.8-5 [ITA, RC])

should install this specific README file (in which upstream records its changes) as "/usr/share/doc/tkinfo/changelog.gz". Best wishes, Guido van Steen -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact lis

Bug#759742: (RFS: tkinfo/2.8-5 [ITA, RC])

Hi Peter, } I've now used a sed extract for changelog.gz, as I want to preserve the } upstream README as originally named. } (If I copy it intact I get a duplicate file warning) This solution sounds sane to me. Best wishes, Guido

Bug#745135: Top 10 reasons you should sponsor MariaDB 10.0 into Debian this weekend (Re: Bug#745135: RFS: mariadb-10.0/10.0.13-1 [ITP] -- Latest version of worlds most popular non-Oracle database)

Dear Otto, I would like Mariadb to be accepted before the freeze as well. However I am not a DD, so I cannot sponsor it myself. In order to get Mariadb sponsored you might handle at least the Lintian error (https://lintian.debian.org/tags/build-depends-on-obsolete-package.html, http://labs.serav

Bug#745135: Top 10 reasons you should sponsor MariaDB 10.0 into Debian this weekend (Re: Bug#745135: RFS: mariadb-10.0/10.0.13-1 [ITP] -- Latest version of worlds most popular non-Oracle database)

> You are talking about: > E: mariadb-10.0 source: missing-build-dependency dpkg-dev (>= 1.16.1~) I had not looked into it yet. Your explanation about this convinces me. Moreover, the following Lintian bug has been reported more than a year ago: see https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Re: [Fwd: Re: ITP? Sponsors of eudev, consolekit2, uselessd?]

>> I'm currently looking into packaging eudev, consolekit2, uselessd for >> Debian. If doing so, is anybody interested in sponsoring uploads of >> these packages? It would be great to know, before digging into the >> details. If you wish, please reply to me privately. I am not a Debian member, and

Bug#870490: RFS: fizsh/1.0.9-1 (already in Debian)

fizsh": * Package name: fizsh Version : 1.0.9-1 Upstream Author : Guido van Steen (myself) * URL : http://sourceforge.net/projects/fizsh/ * License : Modified BSD License Section : shells It builds those binary packages: fizsh - Friendly I