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

[Guido van Steen]

> 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...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+tbga0awyjnyz8r8dc14+dgwdft7mbt7mrm-c+bc8r...@mail.gmail.com

Re: notify command

[Guido van Steen]

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...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+t8+a0taezqyy3csb_kqxdujybs7hrvc3jz3sgx_jj...@mail.gmail.com

RFS: fizsh

[Guido van Steen]

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 : shells

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/fizsh

Alternatively, one can download the package with dget using this command:

  dget -x http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.2-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards,

Guido van Steen


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+sUFbfU4V2P=mA=5=uka9pt4oavmy+xemazlqan+bw...@mail.gmail.com

Re: RFS: fizsh

[Guido van Steen]

Dear mentors,

I would like to provide some more information on FIZSH:

FIZSH is intended to be an easy front-end to ZSH, so that it can serve
as a first shell for starting developers and UNIX lovers. Many of them
are drawn to BASH, because it is the default shell on many systems.
Some may try ZSH, but they may give up after they see the message "You
are seeing this message because you have no zsh startup files".

FIZSH is meant to give such people an easier start. It provides a
similar interface as FISH, which aims to be an easy shell as well
(http://fishshell.com). Like FISH, FIZSH provides syntax-highlighting
and an intuitively appealing history-search widget. These widgets are
maintained at https://github.com/zsh-users/zsh-syntax-highlighting and
https://github.com/zsh-users/zsh-history-substring-search,
respectively. (I am a major contributor to the FIZSH's history-search
widget.)

Unlike FISH, FIZSH accepts Bourne compatible syntax. It inherits this
feature from ZSH. This enables users of FIZSH to use many snippets
from the internet. This feature of snippets in Bourne compatible
syntax is not available to people who use FISH.

My intention for writing FIZSH, is definitely not to provide an
competitor to ZSH. The goal of FIZSH is to make life easier for people
who have not yet managed to tweak their ZSH configuration. These
people may later migrate to ZSH, and add FIZSH's and possibly other
useful ZSH features to their startup scripts.

Also, note that the FIZSH package does not at all interfere with files
installed by ZSH. FIZSH deploys its own configuration files. So it
will never mess up someone's existing ZSH configuration.

The uploaded package is more or less "lintian clean". There is one
message about hyphens in the man page. 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 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         : shells
>
> To access further information about this package, please visit the
> following URL:
>
>  http://mentors.debian.net/package/fizsh
>
> Alternatively, one can download the package with dget using this command:
>
>  dget -x http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.2-1.dsc
>
> I would be glad if someone uploaded this package for me.
>
> Kind regards,
>
> Guido van Steen
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+viRHA0vwNCNTrr9bKsfEvyy8ZZh94c51Ar2k=d+n9...@mail.gmail.com

Re: RFS: pygtkplot

[Guido van Steen]

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,
no one has replied to my RFS.

To be honest, I had never heard of a "DEP-5 requirement". Therefore,
my package does not contain debian/copyright file using DEP-5 either.

So, should I also follow the specifications in
"http://dep.debian.net/deps/dep5";!?

Thank you in advance providing clarity!

Guido


On Mon, Aug 22, 2011 at 8:43 AM, Vincent Cheng  wrote:
> On Sun, Aug 21, 2011 at 2:03 PM, Gabriele  wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "pygtkplot".
>>
>>  * Package name    : pygtkplot
>>    Version : 0.1
>>    Upstream Author : Gabriele N. Tornetta 
>>  * URL : https://launchpad.net/pygtkplot
>>  * License : GNU GPL v3
>>    Section : math
>>
>> To access further information about this package, please visit the following
>> URL:
>>     http://mentors.debian.net/package/pygtkplot
>>
>> Alternatively, one can download the package with dget using this command:
>>     dget -x
>> http://mentors.debian.net/debian/pool/universe/p/pygtkplot/pygtkplot_0.1.dsc
>>
>> I would be glad if someone uploaded this package for me.
>>
>> Kind regards,
>> Gabriele N. Tornetta
>>
>> --
>> "Egli è scritto in lingua matematica, e i caratteri son triangoli, cerchi,
>> ed altre figure
>> geometriche, senza i quali mezzi è impossibile a intenderne umanamente
>> parola;
>> senza questi è un aggirarsi vanamente per un oscuro laberinto."
>>
>> -- G. Galilei, Il saggiatore.
>>
>>
>
> Hi,
>
> There are numerous lintian issues with your package, as pointed out by
> mentors.d.n. Please make sure that your package is lintian-clean
> before sending out a RFS.
>
> W: pygtkplot source: diff-contains-bzr-control-dir .bzr
> W: pygtkplot source: debhelper-but-no-misc-depends pygtkplot
> W: pygtkplot source: package-uses-deprecated-debhelper-compat-version 1
> W: pygtkplot source: maintainer-script-lacks-debhelper-token debian/postinst
> W: pygtkplot source: debian-rules-missing-recommended-target build-arch
> W: pygtkplot source: debian-rules-missing-recommended-target build-indep
> W: pygtkplot source: out-of-date-standards-version 3.9.1.0 (current is 3.9.2)
> E: pygtkplot: changelog-file-not-compressed changelog
> E: pygtkplot: no-copyright-file
> E: pygtkplot: description-starts-with-package-name
> W: pygtkplot: description-starts-with-leading-spaces
> W: pygtkplot: unknown-section universe/math
> E: pygtkplot: missing-dependency-on-python-support python-support
> W: pygtkplot: binary-without-manpage usr/bin/pygtkplot
> W: pygtkplot: maintainer-script-empty postinst
> W: pygtkplot: maintainer-script-ignores-errors postinst
>
> Note that sending a RFS on debian-mentors means that you want to get
> your package into Debian (unstable), so your debian/changelog should
> mention "unstable" and not "natty". You're also missing
> debian/copyright, which is not acceptable. There's a laundry list of
> other things you should do to improve your package, e.g. include
> debian/compat and debian/watch, updating to the latest standards
> version, using a dh rules.tiny style debian/rules file, getting rid of
> your debian/postinst file which doesn't do anything, using DEP-5 for
> your debian/copyright, using dh_python2 instead of the deprecated
> python-support.
>
> Feel free to ask if there's anything you don't quite understand and
> I'll be happy to explain in further detail.
>
> Kind regards,
> - Vincent Cheng
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/caczd_tdti+rvpg0upq--__vtxtrav5vro+blsyu_27+qi8...@mail.gmail.com
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+sqsxueng4we1ga9bpa4nqib9rjaskyxeubxjh3v0d...@mail.gmail.com

Re: RFS: pygtkplot

[Guido van Steen]

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 requirement". Therefore,
>> my package does not contain debian/copyright file using DEP-5 either.
>>
>> So, should I also follow the specifications in
>> "http://dep.debian.net/deps/dep5";!?
>
> DEP-5 is not a requirement as per Policy, but many sponsors encourage
> (or even demand) the use of DEP-5, and it seems to be gaining more and
> more momentum in Debian. So I'd encourage you to use DEP-5 as I think
> it improves the clarity and readability of debian/copyright, but
> that's just my personal opinion, and my opinion doesn't really count
> for all that much, given that I'm not a DD and I can't sponsor your
> package.
>
> I've also taken a quick look at your fizsh package, and I've noticed
> that your debian/watch is broken. Run "uscan --report-status" and
> you'll see what I mean. It's pretty simple to fix though...
>
> --- a/debian/watch      2011-08-21 21:28:34.438237710 -0700
> +++ b/debian/watch      2011-08-21 21:24:49.0 -0700
> @@ -1,3 +1,3 @@
>  version=3
> -http://sf.net/fizsh-([0-9]\.[0-9]\.[0-9]+)\.tar\.gz
> +http://sf.net/fizsh/fizsh-([0-9]\.[0-9]\.[0-9]+)\.tar\.gz
>
> Other than that, your package seems to be fine. :)
>
> Kind regards,
> - Vincent Cheng
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+tncnpspjzgsodnobkugxugqhn9uhbmgvc-18gj_el...@mail.gmail.com

Re: Cavalry

[Guido van Steen]

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 how your package "provides a good way for people with
low-quality connections to access remote data"
* Convince the people here that there is no other package package
providing the same features yet

If you don't there will be litttle chance that your package will be
included indeed.

And indeed, if you do not provide any source code it will not be very
useful to talk about anything your package does.

On Wed, Aug 31, 2011 at 2:21 PM, Andrey Rahmatullin  wrote:
> On Wed, Aug 31, 2011 at 08:40:27AM +0200, Misha Strong wrote:
>> You guys say that my app. won't be very useful, why is that? It provides
>> a good way for people with low-quality connections to access remote
>> data.
> It's hard to say anything specific without seeing the source.
>
> --
> WBR, wRAR
>


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+s6xuqfvi4pmsgejrmfdavya5petcsgfbqnrl6oucs...@mail.gmail.com

Re: RFS: fizsh

[Guido van Steen]

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 version of fizsh.)

I have uploaded the amended fizsh package to
http://mentors.debian.net/package/fizsh.

You can download the package with dget using the command: "dget -x
http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.2-1.dsc";

I would be very glad if you or another sponsor could upload the package for me.

Best wishes,

Guido


On Sat, Sep 3, 2011 at 4:24 PM, Michael Tautschnig  wrote:
> Hi,
>
>> > I am looking for a sponsor for my package "fizsh".
> [...]
>
> I've reviewed your package fizsh and have the following comments:
>
> - .orig.tar.gz differs from upstream:
>  aclocal.m4 |    4
>  configure  |  328 
> ++---
>  2 files changed, 147 insertions(+), 185 deletions(-)
> - No need to depend on coreutils, it is essential.
> - debian/docs is empty
> - (You had already noted yourself the hyphen-used-as-minus-sign.)
>
> Other than the above, the package looks really fine. The first item (differing
> orig.tar.gz), however, is a show stopper.
>
> Best,
> Michael
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+sR0f7AC=1x+unne_mqy4a_uxh1odyzf4pfdu8re_r...@mail.gmail.com

Re: RFS: fizsh

[Guido van Steen]

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 it in a correct way.

Then I thought that arguments to commands (such as "-a" in "ls -a")
start with hyphens, and not with minus signs, so that lintian was
actually wrong. I may be wrong about this though. Anyway for this
reason I added a "lintian-override" file.

I will add working patch in the next upload.

> - The tar.gz file differs in the same way it did before. Why don't you use
>  exactly the file that can be downloaded from sf.net?

I am very sorry. It is only now that I see that this is due to a bug
in a script I used. This bug will not be present in the next upload.

Best wishes,

Guido


On Sun, Sep 4, 2011 at 5:29 PM, Michael Tautschnig  wrote:
> Hi Guido,
>
>> 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 version of fizsh.)
>>
> [...]
>
> I understand that you fixed some of these errors, but
>
> - 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.
>
> Best,
> Michael
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+uccayqzyuqeqjczymtdegvrvdc+wsguaxwm3tfp5h...@mail.gmail.com

Re: RFS: fizsh

[Guido van Steen]

Hi Michael,

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).

The amended package and the original version have been uploaded as:

* http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.2.orig.tar.gz
* http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.2-1.debian.tar.gz

The package can be downloaded with the command: "dget -x
http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.2-1.dsc";

I hope the package is ready for uploading to Debian now.

Thank you very much 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 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 it in a correct way.
>
> Then I thought that arguments to commands (such as "-a" in "ls -a")
> start with hyphens, and not with minus signs, so that lintian was
> actually wrong. I may be wrong about this though. Anyway for this
> reason I added a "lintian-override" file.
>
> I will add working patch in the next upload.
>
>> - The tar.gz file differs in the same way it did before. Why don't you use
>>  exactly the file that can be downloaded from sf.net?
>
> I am very sorry. It is only now that I see that this is due to a bug
> in a script I used. This bug will not be present in the next upload.
>
> Best wishes,
>
> Guido
>
>
> On Sun, Sep 4, 2011 at 5:29 PM, Michael Tautschnig  wrote:
>> Hi Guido,
>>
>>> 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 version of fizsh.)
>>>
>> [...]
>>
>> I understand that you fixed some of these errors, but
>>
>> - 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.
>>
>> Best,
>> Michael
>>
>>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+vXki6Q9Nh2KiODMbJ662QW_cLDMVD�_f_SgWH=j...@mail.gmail.com

Re: RFS: fizsh

[Guido van Steen]

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).
>>
> [...]
>
> Thanks a lot for this quick update. I've checked the changes, built the 
> package,
> signed, and uploaded it.
>
> Thanks a lot for your work,
> Michael
>
>


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+vKhn=txz9rvge8nyzqcmuxqu7w-fedo0kg-jnd2z6...@mail.gmail.com

Fwd: Packaging php app/scripts

[Guido van Steen]

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 are you supposed to build/install the package? Can't you adjust
the package to have a - possibly empty - "Makefile.am"s?

> But package_1.0.0.orig.tar.gz created during build process is containing
> all files I need.

Package_1.0.0.orig.tar.gz should be a exact copy of the upstream
tar-ball. Therefore it has to contain all the files needed.

> cp: cannot stat `debian/tmp/src/index.php': No such file or directory
> My whole php app code is in src directory, so all files from this dir
> should be copied into package and they aren't.

It would be handy if you provided the contents of your package as well.

Best wishes,

Guido

On Tue, Sep 6, 2011 at 8:57 AM, kuLa  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/09/11 22:20, Igor Pashev wrote:
>> 06.09.2011 00:44, kuLa пишет:
>>> Hi all,
>>> I have simple app in php and would like to package it. Source is in git
>>> (2 branches; upstream and debian, gbp.conf is pointing into these branches).
>>> I used dh_make to debianised package, relevant packages has been edited.
>>> When running git buildpackage final deb package is containing only docs
>>> in usr/share/doc/[package] dir (dh_installdocs i surnning as meant).
>>> When I'm trying to override_dh_install with dh_install --sourcedir=src
>>> I'm still having:
>>> cp: cannot stat `debian/tmp/src/index.php': No such file or directory
>>> My whole php app code is in src directory, so all files from this dir
>>> should be copied into package and they aren't.
>>> But package_1.0.0.orig.tar.gz created during build process is containing
>>> all files I need.
>>> Can anybody point me what should I change to achieve my goal?
>>> Thx for any help in advance.
>>
>> Would be nice if you show all files in ./debian
>> (and its content)
>
> 1st thx for your reply :-)
> I forgot one IMHO important info there is no makefile for this project
> as php is not compilable.
> There is nothing unique in my list of files for this package, I removed
> all files I'm not going to use, *.ex files on the list will be used
> later on.
> List:
> changelog
> compat
> control
> copyright
> docs
> rules
> gbp.conf
> README.Debian
> postinst.ex, postrm.ex, preinst.ex, prerm.ex, glocon.doc-base.EX
>
> 
> Content of d/control:
> Source: [app]
> Section: php
> Priority: extra
> Maintainer: kuLa 
> Build-Depends: debhelper (>= 7)
> Standards-Version: 3.8.3
> Homepage: http://www.app.com
>
> Package: [app]
> Architecture: any
> Depends: ${shlibs:Depends}, ${misc:Depends}, apache2 (>=2.2.9), php5
> (>=5.2.6)
> Description: GUI allowing to manage and maintain backend application
>
> 
> Content of d/gbp.conf:
> [DEFAULT]
> upstream-branch = upstream
> debian-branch = debian
> export-dir=../build
>
> sign-tags = True
> keyid = 0x83adec84
>
> 
> Content of d/rules:
> export DH_VERBOSE=1
>
> %:
>        dh  $@
>
> override_dh_install:
>        dh_install --sourcedir=src
> - --
>
> |_|0|_|                                          |
> |_|_|0|         "Heghlu'Meh QaQ jajVam"          |
> |0|0|0|          kuLa -          |
>
> gpg --keyserver pgp.mit.edu --recv-keys 0xC100B4CA
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJOZcRJAAoJEOqHloDBALTKPFEH+QEnClEwrJggQgMMb6jn1jZQ
> vVlyamJcDzzJ0aavko3BwNPlb0xpMoQpQ6NtVjXuRejT81AQ5+g+mfa5cJdProWS
> 2ZHMLu5RCi8V+ELN9vPZQorDI6X4eay+R4icWfn5NNLOWeKyYJADwkGLBaFjZQ0w
> PHLcn0NOL4ZfX7/zIAU9Tjd0J/09QAOTr4qWx5NVIIJgluYOFf+5flEEhB2BPvfZ
> LdMaDHTNK1NajfKIfgWoN05OjQmMPi9VTxVf74kiXOmuC/GCd/nv3xDJB3h+v+jJ
> FMBVX1gHpe9k36CzKM4GSej5sCKMp8/FfFV5MohgyLTwTI99hY1bQ7/FfVywc3w=
> =d8XN
> -END PGP SIGNATURE-
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4e65c449.2020...@kulisz.net
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+vpiuokwg9nzatjzoymxr9k6m9z0mbqbrwdqce8ha-...@mail.gmail.com

Fwd: Packaging php app/scripts

[Guido van Steen]

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
> SRCDIR := ./src
>
> install:
>install -d $(DESTDIR)
>cp -R $(SRCDIR)/* $(DESTDIR)/
>
> uninstall:
>rm -rf $(DESTDIR)/*
>
You may decide to use autotools. This way you make sure everything in your
files is more or less standard.

I remember trying to package a self-rolled makefile as well. I saw errors
everywhere.

After I changed to autotools the packaging process went smoothly.

Best wishes,

Guido

Re: RFS: sxiv

[Guido van Steen]

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:
> >
> > http://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc
> >
> >
> > I tried to build the package with DEB_BUILD_OPTIONS=noopt, but -O2
> > was used as optimization anyway. Could you please fix that?
> >
> >
> > --
> > Jakub Wilk
> >
> >
> > Fixed.
> >
> > Please check out:
> > http://mentors.debian.net/debian/pool/main/s/sxiv/sxiv_0.9-1.dsc
> >
> > Thank you!
> Hi,
>
> We have already quite a large amount of image viewers in Debian.
> Can you explain why we need that one too?
>
> Thomas
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/4e68769d.1050...@goirand.fr
>
>

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

[Guido van Steen]

Hi,

Could someone tell me what is wrong with my debian/copyright file.
Lintian keeps giving me the following (recent) warning:

"W: fizsh source: syntax-error-in-dep5-copyright syntax error in
section 4 after the tag license: Redistribution and use in source and
binary forms, with or without modification, are permitted provided
that the following conditions are met:\n"

I have been amending the file but I still get this warning. This is
the current debian/copyright file:

"Format: http://anonscm.debian.org/viewvc/dep/web/deps/dep5.mdwn?op=file&rev=174
Upstream-Name: Fizsh
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 contributors

Files: scripts/zsh-history-substring-search.zsh
Copyright: 2009, Peter Stephenson 
           2011, Guido van Steen 
   2011, Suraj N. Kurapati 
   2011, Sorin Ionescu 
   2011, Vincent Guerci 
License: BSD-3-clause~FIZSH and BSD-3-clause~zsh-syntax-highlighting
contributors

License: BSD-3-clause~FIZSH
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

 * Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
 * Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
 * Neither the name of FIZSH nor the names of its contributors may
be used to endorse or promote products derived from this software
without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

License: BSD-3-clause~zsh-syntax-highlighting contributors
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

 * Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
 * Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the
distribution.
 * Neither the name of the zsh-syntax-highlighting contributors
nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written
permission.

 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

"


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+t58exfhlf9az227gqrzd9zvqmmayzn1wa77c6n6hk...@mail.gmail.com

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

[Guido van Steen]

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, Jan-Pascal van Best
 wrote:
> Hoi Guido,
>
> This hit me also and it took some time to figure out.
> - indent multi-line fields with a space
> - use 'space dot' - ' .' for empty lines in a multi-line field.
>
> Like this:
>
> License: BSD-3-clause~FIZSH
>  Redistribution and use in source and binary forms, with or without
>  modification, are permitted provided that the following conditions are
>  met:
>  .
>      * Redistributions of source code must retain the above copyright
>        notice, this list of conditions and the following disclaimer.
>      * Redistributions in binary form must reproduce the above
>        copyright notice, this list of conditions and the following disclaimer
>        in the documentation and/or other materials provided with the
>        distribution.
>      * Neither the name of FIZSH nor the names of its contributors may
>        be used to endorse or promote products derived from this software
>        without specific prior written permission.
>  .
>  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>  "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>  LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
>  A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
>  OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
>  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
>  LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
>  DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
>  THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
>  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
>  OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> Cheers
>
> Jan-Pascal
>
>
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+vkpyesq27nkkey_bbfm1+saws5rjk5q2de8+q4ahr...@mail.gmail.com

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

[Guido van Steen]

> 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 UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+ucpbd0r4azwdgw38ew4oarrkjthqxyp6uolny1au8...@mail.gmail.com

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

[Guido van Steen]

>  
> 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 of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+uHBj3Y_zvb=rvjy1v4y9xtjn_z8v7yqz_r5et-m9n...@mail.gmail.com

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

[Guido van Steen]

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/#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.
>
> The moral, then, is to learn the specifications and apply them
> intelligently. Lintian is not a substitute :-)
>
> --
>  \         “If history and science have taught us anything, it is that |
>  `\     passion and desire are not the same as truth.” —E. O. Wilson, |
> _o__)                                              _Consilience_, 1998 |
> Ben Finney
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/87y5wovb8p@benfinney.id.au
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+sX9GQvDEKuvvXDP63Tqi3sEWnRu=mm1kfn7tqx...@mail.gmail.com

Re: Upstream changelog name change

[Guido van Steen]

> 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 a file "CHANGELOG" which does not get installed
>>> by default. When I just include this file name into debian/docs, lintian
>>> complains about "wrong-name-for-upstream-changelog".
>>
>> If you use debhelper compat level 7 or higher, it should add the file
>> automatically.
>
> debian/compat is set to 7, but without mentioning CHANGELOG in
> debian/docs, I get the "no-upstream-changelog" warning, and if it is in
> debian/docs, I get the "wrong-name" error. Since I would like to have
> debian/rules as clean as possible, how should I make sure that it is
> there? (I use debhelper -8.9.0ubuntu1).
>
> Best regards
>
> Ole
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/ytzlisjwxvx@news.ole.ath.cx
>
>


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+u2pmdfms_tddxgjvxaamzxiwpeadnuhiyh8zwy0a5...@mail.gmail.com

Re: Python build dependencies

[Guido van Steen]

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 to me why get this warning. Why do I do
> 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?

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+uqcT_cwSkDXqhYkSoMEgGdT63psRegRiA9xiQa=bk...@mail.gmail.com

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

[Guido van Steen]

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 : shells

To access further information about this package, please visit the
following URL:

 http://mentors.debian.net/package/fizsh

You can download the package with dget using this command:

 dget -x http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.4-1.dsc

The package seems lintian clean.

I would be glad if someone uploaded this package for me.

Kind regards,

Guido van Steen

P.S. For those less familiar with FIZSH:

FIZSH is intended to be an easy front-end to ZSH, so that it can serve
as a first shell for starting developers and UNIX lovers. Many of them
are drawn to BASH, because it is the default shell on many systems.
Some may try ZSH, but they may give up after they see the message "You
are seeing this message because you have no zsh startup files".

FIZSH is meant to give such people an easier start. It provides a
similar interface as FISH, which aims to be an easy shell as well
(http://fishshell.com). Like FISH, FIZSH provides syntax-highlighting
and an intuitively appealing history-search widget. These widgets are
maintained at https://github.com/zsh-users/zsh-syntax-highlighting and
https://github.com/zsh-users/zsh-history-substring-search,
respectively. (I am a major contributor to the FIZSH's history-search
widget.)

Unlike FISH, FIZSH accepts Bourne compatible syntax. It inherits this
feature from ZSH. This enables users of FIZSH to use many snippets
from the internet. This feature of snippets in Bourne compatible
syntax is not available to people who use FISH.

My intention for writing FIZSH, is definitely not to provide an
competitor to ZSH. The goal of FIZSH is to make life easier for people
who have not yet managed to tweak their ZSH configuration. These
people may later migrate to ZSH, and add FIZSH's and possibly other
useful ZSH features to their startup scripts.

Also, note that the FIZSH package does not at all interfere with files
installed by ZSH. FIZSH deploys its own configuration files. So it
will never mess up someone's existing ZSH configuration.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+thuqfrbbeug-n2iq1jk_xfpsnmph9r9swg4pdnszx...@mail.gmail.com

Re: Python build dependencies

[Guido van Steen]

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 "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+uq-0Fw=OJGng_Kv1EmRbNZ7i5B-Vnp_R843T9=d_4...@mail.gmail.com

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

[Guido van Steen]

>> 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 my system, nor it appears on mentors.
> I'll check it and correct it as soon as possible.

Lintian is a moving target. This warning must have been added
somewhere between September and October. For more information see:
http://lists.debian.org/debian-mentors/2011/10/msg00167.html

Best wishes,

Guido


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+tzm9s9cff0xzgkdng3lxbbpgqexalkzjixl7czgvz...@mail.gmail.com

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

[Guido van Steen]

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 fizsh 1.0.5 shortly.

I am very sorry for the inconvenience this causes, especially to those
of you who may have looked at version 1.0.4 already. There is some
good news too: In order to debianize version 1.0.5, only the changelog
will have to be updated.

Best wishes,

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+tkpu3ycj+usfhfptycxbwgg4u8oalkcpfeowtjswb...@mail.gmail.com

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

[Guido van Steen]

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 License
 Section : shells

To access further information about this package, please visit the
following URL:

 http://mentors.debian.net/package/fizsh

You can download the package with dget using this command:

 dget -x http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.5-1.dsc

The package seems lintian clean.

I would be glad if someone uploaded this package for me.

Kind regards,

Guido van Steen

NOTE: This RFS with respect to fizsh version 1.0.5 replaces my
previous RFS with respect fizsh version 1.0.4. For more information
see the thread "RFS: fizsh (already in Debian, new upstream version
1.0.4)"

P.S. For those less familiar with FIZSH:

FIZSH is intended to be an easy front-end to ZSH, so that it can serve
as a first shell for starting developers and UNIX lovers. Many of them
are drawn to BASH, because it is the default shell on many systems.
Some may try ZSH, but they may give up after they see the message "You
are seeing this message because you have no zsh startup files".

FIZSH is meant to give such people an easier start. It provides a
similar interface as FISH, which aims to be an easy shell as well
(http://fishshell.com). Like FISH, FIZSH provides syntax-highlighting
and an intuitively appealing history-search widget. These widgets are
maintained at https://github.com/zsh-users/zsh-syntax-highlighting and
https://github.com/zsh-users/zsh-history-substring-search,
respectively. (I am a major contributor to the FIZSH's history-search
widget.)

Unlike FISH, FIZSH accepts Bourne compatible syntax. It inherits this
feature from ZSH. This enables users of FIZSH to use many snippets
from the internet. This feature of snippets in Bourne compatible
syntax is not available to people who use FISH.

My intention for writing FIZSH, is definitely not to provide an
competitor to ZSH. The goal of FIZSH is to make life easier for people
who have not yet managed to tweak their ZSH configuration. These
people may later migrate to ZSH, and add FIZSH's and possibly other
useful ZSH features to their startup scripts.

Also, note that the FIZSH package does not at all interfere with files
installed by ZSH. FIZSH deploys its own configuration files. So it
will never mess up someone's existing ZSH configuration.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+uhesebyrvo3o0aph7fqyztms2akdmjivnoqurdqau...@mail.gmail.com

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

[Guido van Steen]

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 German translation
> in manpages-de-0.9.
>
> Cheers,
>   Martin
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/4eb7e382.7090...@gmx.de
>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+tfjutuyzmbzjtosjbgqqyyv5mbe-pj8nzj5qgsswd...@mail.gmail.com

Re: Adopt an abandoned ITP?

[Guido van Steen]

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 a package I desperately want in Debian and there already is an ITP
>> for it that is almost a year old. There wasn't any activity on it except that
>> the author reverted the automatic ITP -> RFP conversion after 6 monts of
>> inactivity. I did write to the bug-author a few days ago if he still intends
>> to package it but haven't received a response yet.
>>
>> So in general: What is appropriate the procedure in adopting such a bug? I
>> don't want to 'hijack' anything. How long should I wait for a response from
>> the author? Should I file a new bug or change the owner of the old one?
>
> This largely depends on which ITP bug we're talking about, as there
> might be good reasons the ITP is still pending. Without more
> information, though, no reasonable suggestion can be made, in my
> opinion.
>
> --
> |8]
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/87d3d2svv3.fsf@algernon.balabit
>
>


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+vs0aslkwrgbdatxayxonsrzgw4wkxfcbqu89d_xnl...@mail.gmail.com

Re: Adopt an abandoned ITP?

[Guido van Steen]

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 least a few more times.
>
> On Tue, Nov 8, 2011 at 12:21 PM, Gergely Nagy  wrote:
>> Mathias Ertl  writes:
>>
>>> There is a package I desperately want in Debian and there already is an ITP
>>> for it that is almost a year old. There wasn't any activity on it except 
>>> that
>>> the author reverted the automatic ITP -> RFP conversion after 6 monts of
>>> inactivity. I did write to the bug-author a few days ago if he still intends
>>> to package it but haven't received a response yet.
>>>
>>> So in general: What is appropriate the procedure in adopting such a bug? I
>>> don't want to 'hijack' anything. How long should I wait for a response from
>>> the author? Should I file a new bug or change the owner of the old one?
>>
>> This largely depends on which ITP bug we're talking about, as there
>> might be good reasons the ITP is still pending. Without more
>> information, though, no reasonable suggestion can be made, in my
>> opinion.
>>
>> --
>> |8]
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>> Archive: http://lists.debian.org/87d3d2svv3.fsf@algernon.balabit
>>
>>
>


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/camtvz+u7sxzcd_gumgavkcx8ppfq+82m6tfx1buiyf4da+e...@mail.gmail.com

Re: RFS: nbc (2nd try)

[Guido van Steen]

> 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 Code.
>  * bundle TGIFImage with commercial development libraries.
>  * Charge for the value TGIFImage adds to your Applications.

These restriction are all incompatible with free software (according
to Debian definition).

You should either ask the author to adjust the license or exclude the
images from the package.

Best wishes,

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+uecgB_w=bzbktvrdi+s+jz3apmv4uttm89nwd3qbo...@mail.gmail.com

Re: RFS: yubiserver

[Guido van Steen]

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 UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAMtVZ+ubN7dQQxQ2Y92xbOGuSfLYRf55iNSvAzzf9TEZb=k...@mail.gmail.com

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

[Guido van Steen]

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/
 * License : Modified BSD License
   Section : shells

It builds those binary packages:

* fizsh - Friendly Interactive ZSHell

The Fizsh packages provides an easy interface to Zsh. To access further
information about this package, please visit the following URL:

 https://mentors.debian.net/package/fizsh

Alternatively, you can download the package with dget using this command:

 dget -x
http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.6-1.dsc

Changes since the last upload:

  * New upstream version
  * Increased standards-version to 3.9.5. This yielded 2 warnings:
  syntax-error-in-dep5-copyright and debian-watch-may-check-gpg-signature
  * Corrected the dep5 syntax errors in ./debian/copyright
  * Upgraded from dep5 to copyright-format 1.0
  * Updated the years in ./debian/copyright
  * Added the option "pgpsigurlmangle" to ./debian/watch
  * Added ./debian/upstream/signing-key.asc
  * Added ./debian/README with information on how to debianize a new version
  of fizsh
  * Increased debian/compat to '9'
  * Increased the Build-depend on debhelper to '(>= 9)'
  * Added a build-depend on perl in order to enable the use of pod2man
  * Added override_dh_auto_configure. Without this override ./configure is
  called with unknown parameters
  * Added override_dh_install. dh_install copies some scripts to both
  debian/fizsh/etc/fizsh and debian/fizsh/usr/share/fizsh.
override_dh_install
  removes them from debian/fizsh/usr/share/fizsh again
  * Added override_dh_installman. This override causes pod2man to create the
  manpage. It also takes care of some cleaning
  * Removed debian/fizsh.manpages because it is not needed anymore.
  override_dh_installman takes care of creating the man page
  * Added override_dh_builddeb. This override removes a file called
man/fizsh.1
  which is created during the debian building process
  * Removed the ./debian/patches directory and ./debian/source/options.
  Upstream corrected the issue, which the patch was addressing

The package appears to be lintian clean.

I would be glad if someone uploaded this package for me.

Best wishes

Guido van Steen

Bug#751048: Sponsorship of newer Fizsh package

[Guido van Steen]

Hi Axel,

Thank you for your review.

Regarding the upstream signature file I (as upstream) have produced a file
called ./fizsh-1.0.6.tar.gz.asc:

> gpg --armor --detach-sig ./fizsh-1.0.6.tar.gz

I uploaded it to:

http://sourceforge.net/projects/fizsh/files/fizsh-1.0.6.tar.gz.asc

After this I amended the watch file:

"""version=3

options=pgpsigurlmangle=s/$/.asc/ \
http://sf.net/fizsh/fizsh-([0-9]\.[0-9]\.[0-9]+)\.tar\.gz"""

and issued:

> uscan --verbose --debug --force-download

This seems to work OK. Both the source file and the signature file are
downloaded, and the signature is checked.

Is this how it can be done?

Thank for your help!

Guido

P.S. I will finish the remaining issues within a few days.



On Tue, Jun 10, 2014 at 1:06 AM, Axel Beckert  wrote:

> Hi Guido,
>
> TL;DR: Most stuff is fine, but for an upload, I'd like to have at least
> debian/copright to be streamlined. Fixes for the remaining remarks are
> of course appreciated, too. Details see below.
>
> (And if you don't mind that it there will be a slightly different
> package in Debian than on SourceForge, I'd prefer that package 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
> > Debian Mentors. This package is availabe at
> > http://mentors.debian.net/debian/pool/main/f/fizsh
> >
> > Could you please review the package? I looking forward to reading your
> > review.
>
> So far I noticed the following things:
>
>
> debian/copyright:
>
> * The licenses "BSD-3-clause~zsh-history-substring-search-contributors",
>   "BSD-3-clause~fizsh" and
>   "BSD-3-clause~zsh-syntax-highlighting-contributors" seem to be
>   identical word-wise. In that case the license only needs to be
>   spelled out respectively defined once.
>
>   Of course they differ in the copyright holders, but those are
>   already listed in the "Files:" starting paragraphs and should only
>   be listed there.
>
> * The "License:" starting paragraphs only define the license text and
>   do not need verbatim formatting. They should be word-wrapped if
>   lines are longer than 80 columns. Comments signs from licenses
>   copied from source code headers can and should be dropped.
>
>
> debian/README: This file should be probably better named
> debian/README.source.
>
>
> debian/rules:
>
> * lintian warning script-not-executable
>
>   # the scripts in the "./scripts/" directory of the source package are
>   # copied to both "./debian/usr/bin/" and "./debian/etc/fizsh/". they
>   # are also copied to "./debian/fizsh/usr/share/fizsh/", but they are
>   # not meant to be copied there. moreover they end up there without the
>   # executable bit, which causes lintian to complain about
>   # "script-not-executable". therefore they are explicitly removed after
>   # dh_install.
>
>   While it is good to not have the files in the package twice, this
>   maybe a case where it may have been better to override the lintian
>   warning as the files are meant to be sourced (if it works without
>   them being executables). This not seldom with shell-related
>   packages.
>
>   So just decided if you want them user-modifiable or not and put them
>   in either /etc/fizsh or /usr/share/fizsh and override the above
>   mentioned lintian warning.
>
>   Another way to get rid of that lintian warning would be to remove the
>   shebang lines from those scripts. They're not needed anyway if the
>   scripts are just sourced.
>
> * A general remark on lines like the following:
>
>   [ -d foo ] && rm -rf foo || true
>
>   Just using "rm -rf foo" should suffice and is easier to read:
>
>   * If the directory doesn't exist, it does nothing
>   * It does exit with return code 0 even if the file does not exist.
>
> * Warnings from configure:
>
>   # without the following override the ./configure script would be called
> with two
>   # unrecognized options: --disable-maintainer-mode,
> --disable-dependency-tracking
>   override_dh_auto_configure:
> ./configure \
> --prefix=/usr \
> --includedir=\${prefix}/include \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info \
> --sysconfdir=/etc \
> --localstatedir=/var
>
>   I think those warnings can be safely ignored and hence the override
>   could be dropped. I'm though fine if you are annoy

Bug#751048: Sponsorship of newer Fizsh package

[Guido van Steen]

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/main/f/fizsh/fizsh_1.0.7-1.dsc

} debian/copyright:
}
} * The licenses "BSD-3-clause~zsh-history-substring-search-contributors",
}   "BSD-3-clause~fizsh" and
}   "BSD-3-clause~zsh-syntax-highlighting-contributors" seem to be
}   identical word-wise. In that case the license only needs to be
}   spelled out respectively defined once.
}
}   Of course they differ in the copyright holders, but those are
}   already listed in the "Files:" starting paragraphs and should only
?   be listed there.

} * The "License:" starting paragraphs only define the license text and
}   do not need verbatim formatting. They should be word-wrapped if
}   lines are longer than 80 columns. Comments signs from licenses
}   copied from source code headers can and should be dropped.

Done.

} debian/README: This file should be probably better named
} debian/README.source.

Done

} debian/rules:
}
} * lintian warning script-not-executable
}
}   # the scripts in the "./scripts/" directory of the source package are
}   # copied to both "./debian/usr/bin/" and "./debian/etc/fizsh/". they
}   # are also copied to "./debian/fizsh/usr/share/fizsh/", but they are
}   # not meant to be copied there. moreover they end up there without the
}   # executable bit, which causes lintian to complain about
}   # "script-not-executable". therefore they are explicitly removed after
}   # dh_install.
}
}   While it is good to not have the files in the package twice, this
}   maybe a case where it may have been better to override the lintian
}   warning as the files are meant to be sourced (if it works without
}   them being executables). This not seldom with shell-related
}   packages.
}
}   So just decided if you want them user-modifiable or not and put them
}   in either /etc/fizsh or /usr/share/fizsh and override the above
}   mentioned lintian warning.
}
}   Another way to get rid of that lintian warning would be to remove the
}   shebang lines from those scripts. They're not needed anyway if the
}   scripts are just sourced.

The scripts ended up in the package twice because of a bug that was
introduced
upstream (me as well :< ). The bug has been corrected, and so I have dropped
the override.

} * A general remark on lines like the following:
}
}   [ -d foo ] && rm -rf foo || true
}
}   Just using "rm -rf foo" should suffice and is easier to read:
}
}   * If the directory doesn't exist, it does nothing
}   * It does exit with return code 0 even if the file does not exist.

Done

} * Warnings from configure:
}
}   # without the following override the ./configure script would be called
with two
}   # unrecognized options: --disable-maintainer-mode,
--disable-dependency-tracking
}   override_dh_auto_configure:
} ./configure \
} --prefix=/usr \
} --includedir=\${prefix}/include \
} --mandir=\${prefix}/share/man \
} --infodir=\${prefix}/share/info \
} --sysconfdir=/etc \
} --localstatedir=/var
}
}   I think those warnings can be safely ignored and hence the override
}   could be dropped. I'm though fine if you are annoyed by the warnings
}   and prefer to keep the override. (I'd be rather annoyed by such a
}   long override. :-)

Done

} debian/changelog:
}
} * While it is acceptable, I find the style with a blank line between
}   each item hard to read.
}
} * I'd also indent any line not starting wit "*" by two blanks.

Done

} debian/watch and .sig files:
}
} * The .sig files mentioned in the context of pgpsigurlmangle are meant
}   to be signature files, not public key files as on [1]. See the
}   documentation for "gpg --sign" for details. The public key file goes
}   into debian/upstream/signing-key.asc as done correctly with the
}   package.
}
}   [1] http://sourceforge.net/projects/fizsh/files/
}
}   I'd be nice if you could fix that at "upstream".

Done. I have changed the watch file, so that it will look for signature
files
ending in ".asc". Upstream has uploaded a file called
https://sourceforge.net/projects/fizsh/files/fizsh-1.0.7.tar.gz.asc. it
should match the signature in ./debian/upstream/signing-key.asc

} To not only mention negative stuff I noticed, I was also positively
} surprised that the package is indeed lintian clean, even with
} --pedantic and --experimental!

Thank you for reviewing the package!

Best wishes

Guido

Bug#751048: Sponsorship of newer Fizsh package

[Guido van Steen]

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 explicitly dealt
with version 1.0.6-1 its subject. I did not realize that it might have been
necessary to open a new RFS bug report.

Thank you for reopening the original bug report.

} I'll have a closer look later, hopefully this evening.

Thanks!

Best wishes,

Guido

Re: how to properly remove an empty config directory

[Guido van Steen]

> 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

[Guido van Steen]

> 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)

[Guido van Steen]

Package: sponsorship-requests
Severity: normal

Dear Axel and other mentors,

Earlier this month I uploaded version 1.0.6-1 to mentors.debian.net.
However,
the upstream version on which the package was based (1.0.6) contained some
bugs. These bugs were eliminated in upstream version 1.0.7, which upstream
released today. Therefore, I have now also uploaded a new version 1.0.7-1 of
the fizsh package to mentors.debian.net.

I apologize for the inconvenience caused by the version update.

This updated RFS concerns the following package:

 * Package name: fizsh
   Version : 1.0.7-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 Interactive ZSHell

The Fizsh packages provides an easy interface to Zsh. To access further
information about this package, please visit the following URL:

 https://mentors.debian.net/package/fizsh

Alternatively, you can download the package with dget using this command:

 dget -x
http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.7-1.dsc

Changes since the last upload:

   * New upstream release
   * Increased standards-version to 3.9.5. This gave rise to 2 warnings:
 syntax-error-in-dep5-copyright and debian-watch-may-check-gpg-signature
   * Corrected the dep5 syntax errors in ./debian/copyright
   * Upgraded from dep5 to copyright-format 1.0
   * Updated the years in ./debian/copyright
   * Added the option "pgpsigurlmangle" to ./debian/watch
   * Added ./debian/upstream/signing-key.asc
   * Added ./debian/README.source with information on how to debianize a new
 version of fizsh
   * Increased debian/compat to '9'
   * Increased the Build-depend on debhelper to '(>= 9)'
   * Added a Build-depend on automake and autoconf to enable the build
   * Added a Build-depend on perl to enable the use of pod2man
   * Added override_dh_installman. This override causes pod2man to create
the
 manpage. It also takes care of some cleaning
   * Added override_dh_builddeb. This override clean up the file
man/fizsh.1,
 which is generated during the build process
   * Removed debian/fizsh.manpages because it is not needed anymore.
 override_dh_installman takes care of creating the man page
   * Removed the ./debian/patches directory and ./debian/source/options.
 Upstream corrected the issue, which the patch was addressing

The package appears to be lintian clean.

Best wishes

Guido van Steen

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

[Guido van Steen]

Hi Willem,

I'm not a DD so cannot sponsor your package either.

} That can also be confusing. Is there
} something comparable that I can use to solve this

Can't upstream (you) skip a version number for the server part?

} Maybe you can give me a hint how to solve this when needed.

Non-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

[Guido van Steen]

(Excuse me for the general reference I gave you earlier.)

A bit more specific:

* Change ./debian/source/format into "3.0 (quilt)"
* Change "(0.4.0)" into "(0.4.0-1)" in the first line of ./debian/changelog
* Remove the ./debian directory from your source package (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

[Guido van Steen]

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

[Guido van Steen]

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. Charles's answer was not
conclusive though.

Best wishes,

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+ufyc2tvhjr7vmfza2exjgsdoqassfu4bkfjml_j_c...@mail.gmail.com

Re: About debuild -i

[Guido van Steen]

} 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" is passed to dkpg-build, from where
it is passed to dpkg-source. The "-i" parameter (or "--diff-ignore")
forces dpkg-source to filter out unwanted files.

The debuild parameter "-i" is NOT passed to Lintian. Moreover, Lintian
only shows info tags when it is called with "-I" (or
"--display-info"). Calling lintian with the parameter "-i" (or
"--info") yields different behavior: It forces lintian to display
explanatory information on the tags shown.

Best wishes,

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAMtVZ+tscMx4jJ0tpX4CYiN77YhNKXig_7fzhqkfTCJ=nsk...@mail.gmail.com

Re: Autoreconfing guide

[Guido van Steen]

> 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...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+vwvz3v4dhurm92cq_pzfcikvu-f4zy8zn+hyl_dgr...@mail.gmail.com

Re: Autoreconfing guide

[Guido van Steen]

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
this case I need neither dh-autoreconf nor autotools-dev. Correct me
if I am wrong though... IMO this could be useful information for the
wiki as well.

I also find https://wiki.debian.org/AutoTools/autoconf quite interesting.

Best wishes,

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+vsgx1rbycbxod8ypbeuffd6fsyekox7wdec3a4rsy...@mail.gmail.com

Re: Autoreconfing guide

[Guido van Steen]

} 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 and config.sub.

Apparently I was wrong. Thank you for pointing this out! Next time I will
use autoreconf as well.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+sfqan-xbybgyvogypkw8mymfckhc7h42tk6wkbt-4...@mail.gmail.com

Re: ghdl package has been removed from Mentors

[Guido van Steen]

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 report again debexpo, or is this mailing list
the place for a discussion?

Best wishes,

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAMtVZ+vO=yvrq0cc7b1q8jt5odsfxjdrq_g_v0hhmmeflja...@mail.gmail.com

Re: ghdl package has been removed from Mentors

[Guido van Steen]

} 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-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+utjlwja7usdj-gxtphkfhxgvu8ymcwgrcetxync61...@mail.gmail.com

Re: ghdl package has been removed from Mentors

[Guido van Steen]

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 could take care of handling
this automatically.

} Debexpo has its own bug tracker:
} https://alioth.debian.org/tracker/?atid=413115&group_id=100127&func=browse

Thanks for the url of the debexpo's bug tracker. Bug# 314604 seems to
reflect the remarks by Joris van Rantwijk. However, noone has
addressed the "lost comments feature" yet.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+t1nxpvwymumvffn3bw9hkijpqossrsezj+de5fian...@mail.gmail.com

Re: ghdl package has been removed from Mentors

[Guido van Steen]

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 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 could take care of handling
> this automatically.
>
> } Debexpo has its own bug tracker:
> } https://alioth.debian.org/tracker/?atid=413115&group_id=100127&func=browse
>
> Thanks for the url of the debexpo's bug tracker. Bug# 314604 seems to
> reflect the remarks by Joris van Rantwijk. However, noone has
> addressed the "lost comments feature" yet.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+vimo+ayyks8w3k4qm8djluszmfqh0dmtxryhrnu+i...@mail.gmail.com

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

[Guido van Steen]

} The lintian pedantic 'no-upstream-changelog' looks to be a false positive
} as upstream changes are documented in the installed README.

The Lintian tag says: "If upstream provides a changelog, it should be
accessible as /usr/share/doc/pkg/changelog.gz." So I guess you 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 listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+sze8w-fapi3mswfmr3hqh9c9rurmbq-nylxduuxrn...@mail.gmail.com

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

[Guido van Steen]

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)

[Guido van Steen]

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.seravo.fi/~otto/mariadb-repo/logs/mariadb-10.0/mariadb-10.0_10.0.13-1_amd64.build-d992d30.log).
If it is a false positive, please explain why.

Yesterday Arnoud Fontaine expressed his willingness to sponsor
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745135#69). He asks
"What's blocking the upload to unstable?". Other sponsors may have the
same question.

Good luck!

Guido


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+s7z-tuaa+_myhxapew2csiq7fgh6qrjhjam0u7+78...@mail.gmail.com

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)

[Guido van Steen]

> 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?bug=706694#8.
It is indeed a false positive.

Good luck getting Mariadb sponsored!


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+t13uut04iewvnsozma7aaqhedggvyyvf8ol1m3ob2...@mail.gmail.com

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

[Guido van Steen]

>> 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 so I cannot sponsor any packages.

However, from my own experience I have noticed that getting things
sponsored is quite an undertaking. It is possible, but it takes
perseverance and time.

You should take into account that Debian sponsors refrain from
uploading packages that do not conform to Debian's high quality
standards. This is a good thing, because otherwise someelse's rough
package might cause havoc on your Debian system.

A good primer is: https://wiki.debian.org/Packaging

Good luck!


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/camtvz+sjeofoi4xgtstlvqfkynvtqcn+glyjtbvls-azhuu...@mail.gmail.com

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

[Guido van Steen]

Package: sponsorship-requests
Severity: normal

Dear Axel and other mentors,

I have uploaded a new version 1.0.9-1 of the fizsh package to
mentors.debian.net.

The reason for this RFS is a number of upstream enhancements and bugfixes.

I am therefore looking for a sponsor for my package "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 Interactive ZSHell

The Fizsh packages provides an easy interface to Zsh. To access
further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/fizsh

Alternatively, you can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/f/fizsh/fizsh_1.0.9-1.dsc

Changes since the last upload:

  * New upstream release
  * Increased standards-version to 4.0.0. This did not cause an warnings
  * Updated years and authors in ./debian/copyright
  * Updated to version 1.0.9 in ./debian/rules

The package appears to be lintian clean.

Kind regards,

Guido van Steen