Re: RFS: tmux (updated package)
Hello,
On Wed, 11 Mar 2009, Karl Ferdinand Ebert wrote:
I am looking for a sponsor for the new version 0.7-1
of my package tmux.
Here are some comments:
- add FAQ to docs
- add CHANGES file as upstream changelog
- ITP bug will be closed by the first upload not the first packaging attempt
So the Closes should come in the topmost changelog entry.
- some licenses are BSD 3-clause some are BSD-2 and others are of the type
included in the debian/copyright file
- include NOTES file in docs
- include examples in docs
The package appears to be lintian clean.
Not so! :-(
There are Lintian errors in your manpage (hyphen used as minus sign).
The report is attached.
Regards,
Kapil.
--
N: Setting up lab in /tmp/S5enavUQOg ...
N: Processing changes file tmux_0.7-2_amd64.changes ...
N: Processing 2 packages...
N:
N: Processing source package tmux (version 0.7-2) ...
N:
N: Processing binary package tmux (version 0.7-2) ...
I: tmux: hyphen-used-as-minus-sign usr/share/man/man1/tmux.1.gz:340
N:
N: Manual page seems to contain a hyphen where a minus sign was intended.
N: '-' chars are interpreted as hyphens (U+2010) by groff, not as minus
N: signs (U+002D). Since options to programs use minus signs (U+002D),
N: this means for example in UTF-8 locales that you cannot cutpaste
N: options, nor search for them easily.
N:
N: '-' must be escaped ('\-') to be interpreted as minus. If you really
N: intend a hyphen, write it as '\(hy' to emphasise that fact. See
N: groff(7) and especially groff_char(7) for details, and also the thread
N: starting with
N: http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481
N: .html
N:
N: If you use some tool that converts your documentation to groff format,
N: it might be possible that this tool converts dashes of any kind to
N: groff hyphens, while the safe way of converting dashes is usually to
N: convert them to '\-'.
N:
N: Because this error can occur very often we show only the first 10
N: occurrences for each man page and give the number of suppressed
N: occurrences. If you want to see all warnings, run lintian with the
N: -d/--debug option.
N:
I: tmux: hyphen-used-as-minus-sign usr/share/man/man1/tmux.1.gz:342
I: tmux: hyphen-used-as-minus-sign usr/share/man/man1/tmux.1.gz:344
I: tmux: hyphen-used-as-minus-sign usr/share/man/man1/tmux.1.gz:346
I: tmux: hyphen-used-as-minus-sign usr/share/man/man1/tmux.1.gz:999
N: Removing /tmp/S5enavUQOg ...
signature.asc
Description: Digital signature
Re: debian/rules
On Mar 11 2009, Jaromír Mikeš wrote:
Thanks for advice and link it can really save frustration.
I particularly have no problem with the commented lines (they serve me
as a reminder or as a way to put a quick reference on the rules file),
but some people really dislike them.
I have one other question about debian/rules
original variable PREFIX in makefile is PREFIX = /usr/local
I shouldn't edit makefile itself so I should to do it in debian/rules file.
The result should looks like this?
Usually, some makefiles derived from configure scripts accept a --prefix
option that indicates where to install the package.
In other cases, you may just want to use DESTDIR (if the makefile
honours it) or with PREFIX, just like you did.
build-stamp: configure-stamp
dh_testdir
# Add here commands to compile the package.
$(MAKE) -C source/ PREFIX=/usr
Be careful here, because the binaries and everything else will be
installed in a subdirectory of the debian directory of the source
package. Some programs (like, say, Daniel J. Bernstein's utilities) need
special care when specifying the installation directory.
# Add here commands to clean up after the build process.
-$(MAKE) -C source/ PREFIX=/usr clean
Hummm, here you should also make sure that you don't ignore errors from
make (see the hyphen that was put there). Are current versions of
dh_make producing such templates?
Anyway, another point is the following:
Makefile is also nested in source subdirectory ... thats why - C source/
Some upstream have unusual ways of doing things indeed. :-)
Regards, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Fwd: 'uboot-envtools' uploaded to mentors.debian.net
On Mar 09 2009, Luca Capello wrote:
On Sat, 07 Mar 2009 19:25:25 +0100, Per Andersson wrote:
I have upload the uboot-envtools to mentors.debian.net.
Please have a look.
I will take care of this. I cc:ed the d-mentors mailing list so
people will not do twice the same work.
Great for those that are interested in embedded systems.
Regards,
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian/rules
On Thu, Mar 12, 2009 at 05:10:38AM -0300, Rogério Brito wrote: On Mar 11 2009, Jaromír Mike?? wrote: # Add here commands to clean up after the build process. -$(MAKE) -C source/ PREFIX=/usr clean Hummm, here you should also make sure that you don't ignore errors from make (see the hyphen that was put there). Are current versions of dh_make producing such templates? Reported in bug 432667 and fixed in dh-make 0.45 which was released May 2008. Offtopic perhaps, but I'm working on the next release of dh-make which looks like extra features rather than bug-fixing. Some upstream have unusual ways of doing things indeed. :-) You can say that again! - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 http://www.enc.com.au/ csmall at : enc.com.au http://www.debian.org/ Debian GNU/Linux, software should be Free -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Which package cacher to use?
Hi there.
I seem to recall that, in the not so distant past, people were
discussing here the subject of package chachers for the use of building
(and rebuilding etc) packages from sources, something which is necessary
for those that want to help with the mentoring process (or even building
their own packages at home).
OK, so, recently, Linux Weekly News has published an article (right at
http://lwn.net/Articles/318658/) that made some simple comparisons
between apt-cache, apt-proxy, approx and others and, to be honest, the
article has just made me even more confused about which cacher to use.
Worse, when I saw some bugs (e.g., #285360) on the BTS, I felt lost,
since I need to use three arches.
So, I would like to ask you:
* what is the package chacher that you are using?
* Is it able to cope with multiple architectures?
* Can it support multiple distributions? Supporting Debian, Ubuntu and
other non-official repositories would be really handy.
* Does it keep a directory hierarchy neatly organized like the Debian
archive?
Right now, I am using apt-move for a single machine and I thought of
exporting this to other boxes via NFS, but I would prefer to use the
proxy way of doing things, to make life easier.
Thanks for any help, Rogério Brito.
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: dpkg-buildpackage -S error
Od: Ben Finney ben+deb...@benfinney.id.au So, you're trying to build a source package. debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. /usr/bin/make PREFIX = /usr clean make: *** empty variable name. Stop. The command line received the following arguments: ‘/usr/bin/make’ ‘PREFIX’ ‘=’ ‘/usr’ ‘clean’ If you want to set a variable, you need that as a single argument: $(MAKE) PREFIX=/usr clean which will result in command-line arguments as: ‘/usr/bin/make’ ‘PREFIX=/usr’ ‘clean’ Then make will see a single argument setting a variable to a value. Thank you a lot this wrong syntax was exactly the problem ... regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: best practice for updating inetd.conf with a user-chosen port?
On Wed, Mar 11, 2009 at 04:56:20PM +0100, Giacomo A. Catenazzi wrote: how to had new services in /etc/services database? ciao cate Asking netbase maintainer(s)? Just read /etc/services about that. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian/rules
Od: Charles Plessy ple...@debian.org it looks fine, but the ultimate answer comes of course from building the binary package and inspecting its contents with dpkg -c. In addition, you can run the checker `lintian' on the .changes file; it will give you a lot of useful stylistic comments. Hello, Thank you for helpful answer. Actually I am trying build package from source and there are some warning messages already when I install them from source (make). r/share\ -ffast-math -I/usr/include/freetype2 -c -o jkmeter.o jkmeter.cc jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc:43: warning: deprecated conversion from string constant to ‘char*’ jkmeter.cc: In function ‘int main(int, char**)’: jkmeter.cc:85: warning: deprecated conversion from string constant to ‘char*’ I've contacted author because of that before and answer was that this is nothing harmful. And really program run well without any problem. Can these warning messages be problem when I will try latter get this package to debian repository? regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: best practice for updating inetd.conf with a user-chosen port?
Francesco P. Lovergine wrote: On Wed, Mar 11, 2009 at 04:56:20PM +0100, Giacomo A. Catenazzi wrote: how to had new services in /etc/services database? Asking netbase maintainer(s)? Just read /etc/services about that. Hmm. Reading your and dato answers, it seems I wrote wrongly my mail. The question (still in subject) was how to have admin-chosen ports for some services. The first proposal was to dynamically change port in inetd configuration. I proposed to move the dynamic port in the /etc/services level, not necessary modifying such file, but in a way accessible to getservbyname(3). But now I'm not sure about: - if it is a good thing to have admin choosed ports - if /etc/services level is the right thing to do. ciao cate -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian/rules
Od: Rogério Brito rbr...@ime.usp.br # Add here commands to clean up after the build process. -$(MAKE) -C source/ PREFIX=/usr clean Hummm, here you should also make sure that you don't ignore errors from make (see the hyphen that was put there). Are current versions of dh_make producing such templates? I am running dh_make 0.44 and this is a template ... You think I should remove this hyphen? regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: best practice for updating inetd.conf with a user-chosen port?
Hi, On Donnerstag, 12. März 2009, Giacomo A. Catenazzi wrote: But now I'm not sure about: - if it is a good thing to have admin choosed ports I dont think so and I guess I'm not alone and thats why there is no best practice to do that. The only (typo of) package where I can think off where this is sensible as default, is one which sets up a hidden service. What kind of daemon are you packaging? regards, Holger signature.asc Description: This is a digitally signed message part.
Re: Which package cacher to use?
Rogério Brito wrote: So, I would like to ask you: * what is the package chacher that you are using? Squid * Is it able to cope with multiple architectures? Yes * Can it support multiple distributions? Supporting Debian, Ubuntu and other non-official repositories would be really handy. Yes * Does it keep a directory hierarchy neatly organized like the Debian archive? N/A The article lists two issues with Squid (or other general purpose proxies). One is that it doesn't recognise identical files from different repositories - which is fair enough criticism, although most users don't use APT's built in redundancy by listing multiple repositories with the same content, so most users won't be penalised by this that often. And then only when the archive they actually used is down (one could configure Squid to deliver the package if a 304 failed if your preferred mirror is unreliable). The other criticism that other web traffic will expire packages from cache is not really a problem at all. You could either dedicate a squid to repositories, when the issue reduces to just how efficient the resource usage of the different caches are, or more sensibly accept this will happen if the cache is small and give your squid instance as much disk space as it needs to maximize the byte (time) savings. Last I looked Terabyte drives were very cheap, and the entire Debian archive is currently ~335GB (including a load of DVD and similar images), which leaves plenty of disk space free for caching other stuff like Ubuntu, websites etc. Indeed most small organisations only need a few gigabytes of squid cache for regular web traffic. Other than some tweaking to ensure Squid is caching large enough files, it is largely an install and forget job. I'd suggest making Squid transparent, in the years we've been using it as a web proxy I've hit one website that didn't work with Squid correctly (due to an obscure HTTP bug in Firefox), and keep meaning to make it transparent, but in our environment this is more complex than most. You might want to tweak the Squid behaviour for deb files slightly, there is some advice around, but one can over micromanage such details. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: best practice for updating inetd.conf with a user-chosen port?
On Thu, Mar 12, 2009 at 02:13:12PM +0100, Holger Levsen wrote: On Donnerstag, 12. März 2009, Giacomo A. Catenazzi wrote: But now I'm not sure about: - if it is a good thing to have admin choosed ports I dont think so and I guess I'm not alone and thats why there is no best practice to do that. The only (typo of) package where I can think off where this is sensible as default, is one which sets up a hidden service. What kind of daemon are you packaging? I'm packaging approx, which for compatibility with apt-proxy defaults to port (not in /etc/services). That was fine when approx, like apt-proxy, was run as a standalone daemon from an initscript. But I just changed it to run (only) from inetd, hence this thread. Regarding the other thread in -devel about the future of inetd: in my case I found it very sensible to jettison all the code for opening sockets, binding ports, handling IPv6, handling tcp-wrappers, daemonizing processes, etc. and punt it to inetd. Since apt clients keep their connections open for many multiple, the performance hit is negligible. -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libmx4j-java (updated package)
Hi Damien, Hi Varun, [...] The new package still fails to build on many archs and I am not sure why. Could you please check? There is some massive libraries transitions ongoing in unstable. Since yesterday (11/03), there is +3000 uninstallable packages [2]. In our issue, default-jdk isn't available on many arch [1] because of this chain of uninstallable packages : missing java-gcj-compat - missing gcj-4.3 - missing libcairo2 - missing libdirectfb-1.0-0 (which had bump his soname to libdirectfb-1.2-0) So I think we just have to wait for respective DD, to upload new packages with updated Build-Depends and Depends. [1] for example, on PowerPC : http://edos.debian.net/edos-debcheck/results/unstable/1236811202/powerpc/list.php [2] http://edos.debian.net/edos-debcheck/unstable.php Regards, -- Damien Raude-Morvan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Which package cacher to use?
On Thursday 12 March 2009 03:32:35 Rogério Brito wrote: * what is the package chacher that you are using? approx * Is it able to cope with multiple architectures? Yes. * Can it support multiple distributions? Supporting Debian, Ubuntu and other non-official repositories would be really handy. Yes. * Does it keep a directory hierarchy neatly organized like the Debian archive? Yes. For building in pbuilder (or a variant) (or another build daemon) some sort of apt proxy is virtually required. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
sudo pbuilder build - error
Hello, I just trying build package from source and getting this error: ~$ sudo pbuilder build '/home/mira/JK/jkmeter_0.4.0-1.dsc' --buildresult /home/mira ### # Add here commands to install the package into debian/jkmeter. /usr/bin/make -C source/ PREFIX=/usr DESTDIR=/tmp/buildd/jkmeter-0.4.0/debian/jkmeter install make[1]: Entering directory `/tmp/buildd/jkmeter-0.4.0/source' /usr/bin/install -d /usr/bin /usr/bin/install -m 755 jkmeter /usr/bin /usr/bin/install: cannot create regular file `/usr/bin/jkmeter': Permission denied ### Thanks for any advice mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: sudo pbuilder build - error
On Thu, Mar 12, 2009 at 07:40:42PM +0100, Jaromír Mikeš wrote: /usr/bin/install: cannot create regular file `/usr/bin/jkmeter': Permission denied At a guess, the upstream build process isn't taking any notice of your DESTDIR. But if you can put the source somewhere visible, it will be much easier to advise. -- Jonathan Wiltshire PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 signature.asc Description: Digital signature
Re: sudo pbuilder build - error
Od: Jonathan Wiltshire deb...@jwiltshire.org.uk On Thu, Mar 12, 2009 at 07:40:42PM +0100, Jaromír Mikeš wrote: /usr/bin/install: cannot create regular file `/usr/bin/jkmeter': Permission denied At a guess, the upstream build process isn't taking any notice of your DESTDIR. But if you can put the source somewhere visible, it will be much easier to advise. In attachment is my debianized source ... regards mira jkmeter-0.4.0.tar.gz Description: GNU Zip compressed data
Re: best practice for updating inetd.conf with a user-chosen port?
Eric Cooper e...@cmu.edu writes: Regarding the other thread in -devel about the future of inetd: in my case I found it very sensible to jettison all the code for opening sockets, binding ports, handling IPv6, handling tcp-wrappers, daemonizing processes, etc. and punt it to inetd. Since apt clients keep their connections open for many multiple, the performance hit is negligible. Yeah, I disagree with the idea that inetd is a bad choice for new programs. Writing a standalone daemon requires a fair bit of networking knowledge and work, particularly if you also want to support IPv6, and inetd can already do all that for you. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: best practice for updating inetd.conf with a user-chosen port?
Giacomo A. Catenazzi c...@debian.org writes: Francesco P. Lovergine wrote: On Wed, Mar 11, 2009 at 04:56:20PM +0100, Giacomo A. Catenazzi wrote: how to had new services in /etc/services database? Asking netbase maintainer(s)? Just read /etc/services about that. Hmm. Reading your and dato answers, it seems I wrote wrongly my mail. The question (still in subject) was how to have admin-chosen ports for some services. The first proposal was to dynamically change port in inetd configuration. I proposed to move the dynamic port in the /etc/services level, not necessary modifying such file, but in a way accessible to getservbyname(3). But now I'm not sure about: - if it is a good thing to have admin choosed ports Many people run services on non standard ports to avoid password and vulnerability scanners. The kind that repedatly tries to lock into your sshd with stupid user/pass combos. - if /etc/services level is the right thing to do. ciao cate I don't think you can do this through /etc/services. Say I want my proftpd to run on port 2121 so I change ftp to 2121. Now suddenly applications would look for ftp.debian.org on port 2121. MfG Goswin -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: crrcsim
Dear mentors, I am looking for a sponsor for my package crrcsim. * Package name: crrcsim Version : 0.9.10-1 Upstream Authors : Ahmet Inan, Bob Parks, Chris Bailey, Jan Edward Kansky kan...@ll.mit.edu, Jan Reucker jan.reuc...@web.de, Jens Wilhelm Wulf jens...@gmx.net, Joel Lienard, Kees Lemmens, Lionel Cailler, Martin Herrmann, Olivier Bordes, Todd Templeton * URL : http://crrcsim.berlios.de * License : GPL Section : contrib/games It builds these binary packages: crrcsim- Model-Airplane Flight Simulator The upload would fix these bugs: 518217 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/contrib/c/crrcsim - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/contrib/c/crrcsim/crrcsim_0.9.10-1.dsc I would be glad if someone uploaded this package for me. -- Kind regards, Loïc Fejoz -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: sudo pbuilder build - error
On Thu, Mar 12, 2009 at 08:18:45PM +0100, Jaromír Mikeš wrote:
At a guess, the upstream build process isn't taking any notice of your
DESTDIR. But if you can put the source somewhere visible, it will be much
easier
to advise.
In attachment is my debianized source ...
Yes, as I thought you need to tell upstream's makefile about your
DESTDIR variable, like the attached. (p.s. it's not a good idea to
attach big files to a list, because it's distributed to many hundreds of
people - multiplied by the attachment size, which makes for lots of
traffic. A small file is ok, but anything bigger will make the
listmasters grumpy.)
You can make the change directly in the source, so it goes into the
diff, or use a patch system like dpatch [1] or quilt [2]. See the New
Maintainers guide [3] for another example.
There are some other things you need to fix as well, so you might as
well instead of asking for sponsorship and having to go back to them
anyway:
debian/changelog:
You must file an ITP bug [4] and when you get its number, close it in
the changelog like this:
* Initial release (Closes: #123456)
Don't include lines that aren't facts, like my first debian package.
The changelog is a record of what you changed in a package for future
reference.
Be careful of your whitespace as well, check the policy manual for the
exact specification of the changelog.
debian/control:
You should include a Homepage field if you're claiming policy 3.8.1 [5].
Both the short and long descriptions are far too long, consider the
following for the short (which should also be in 'is-a' format):
Description: sophisticated sound level meter in bar graph format
Most of the information in the long description is too specific and
belongs in upstream's README file. Just give a broad overview of the
package: the first sentence of the first and second paragraphs are the
best bits to include. (I don't know what a DAW is, for example, or why I
should want it.)
Your build-depends should have upstream version numbers, not revisions,
like this:
libclxclient-dev (= 3.3.2) instead of libclxclient-dev (= 3.3.2-1)
Are all those build-depends really neccessary? INSTALL only mentions
libclthreads and libclxclient.
debian/copyright:
Only the email addresses need to be in angle brackets.
Don't include the whole GPL text, just the grant text found at the
bottom ('This package is free software; you can re.)
Refer to a versioned GPL file, such as /usr/share/common-licenses/GPL-2
You don't need a debian/dirs file, the neccessary directories are
created by upstream's makefile.
You don't need debian/README.Debian, all this information is in
upstream's README and doesn't need to be duplicated.
There is no manual page included upstream; you should ask them to write
one for each binary created or write your own and get it integrated upsream.
debian/rules:
Consider using debhelper 7 and it can make your rules file much more
manageable by automating lots of the steps and targets (this isn't a
complex package).
Either way, remove all the cruft and boilerplate comments if you're not
using them, they just make the file harder to read.
At the moment, I can't build your package from source because there are
some crucial packages that are broken in unstable. If you prod me in a
couple of days, I will try again then. Once you make the package build
successfully, use the lintian [6] tool from unstable against it and correct
anything it shows up.
If you need more help with any of these please ask (I am not a developer
though, and can't sponsor you).
[1] http://packages.debian.org/dpatch
[2] http://packages.debian.org/quilt
[3] http://http://www.debian.org/doc/maint-guide/
[4] http://www.debian.org/devel/wnpp/
[5] http://www.debian.org/doc/devel-manuals#policy
[6] http://packages.debian.org/lintian
--
Jonathan Wiltshire
PGP/GPG: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52
# Copyright (C) 2008 Fons Adriaensen f...@kokkinizita.net
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
PREFIX = /usr/local
SUFFIX := $(shell uname -m | sed -e 's/^unknown/$//' -e 's/^i.86/$//' -e
's/^x86_64/$/64/')
LIBDIR = lib$(SUFFIX)
SHARED = $(PREFIX)/share
PROGRAM = jkmeter
VERSION = 0.4.0
DISTDIR = jkmeter-$(VERSION)
CPPFLAGS += -O3 -Wall -MMD -MP -DPROGRAM=\$(PROGRAM)\
-DVERSION=\$(VERSION)\
Re: sudo pbuilder build - error
Dear Jonathan, thank you a lot for very complex answer you really moved me forward. You answered so many unspoken questions. I know that there is one unsolved dependency in unstable for this package and I am waiting for upgrading of this library. So I will start with another package for now and continue studying New Maintainers' Guide. Thanks again. mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: tmux (updated package)
Karl Ferdinand Ebert ferdi1...@gmx.de writes: Hi, Am Thursday 12 March 2009 07:37:11 schrieb Kapil Hari Paranjape: On Wed, 11 Mar 2009, Karl Ferdinand Ebert wrote: The package appears to be lintian clean. Not so! :-( There are Lintian errors in your manpage (hyphen used as minus sign). corrected. I was using linitian from stable, therefore I did not recognized these errors. If you upload the package targeted to ‘unstable’, you must build and check it in an environment that is the latest ‘unstable’. See the ‘pbuilder’ package which can make this easier. -- \ “Better not take a dog on the space shuttle, because if he | `\ sticks his head out when you're coming home his face might burn | _o__)up.” —Jack Handey | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: crrcsim
On Fri, Mar 13, 2009 at 5:56 AM, Loïc Fejoz l...@fejoz.net wrote: I am looking for a sponsor for my package crrcsim. * Package name : crrcsim ... Section : contrib/games It builds these binary packages: crrcsim - Model-Airplane Flight Simulator You might want to join the Debian Games Team: http://wiki.debian.org/Games/Team -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: crrcsim
On Fri, Mar 13, 2009 at 5:56 AM, Loïc Fejoz l...@fejoz.net wrote: I am looking for a sponsor for my package crrcsim. * Package name : crrcsim ... Section : contrib/games ... http://mentors.debian.net/debian/pool/contrib/c/crrcsim/crrcsim_0.9.10-1.dsc According to debian-policy, stuff in contrib/non-free has to document in debian/copyright why it cannot be in main. You should do that for crrcsim. Based on the current dependencies and copyright information it should be in main. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: sudo pbuilder build - error
Od: Jonathan Wiltshire deb...@jwiltshire.org.uk Your build-depends should have upstream version numbers, not revisions, like this: libclxclient-dev (= 3.3.2) instead of libclxclient-dev (= 3.3.2-1) Are all those build-depends really neccessary? INSTALL only mentions libclthreads and libclxclient. Actually these dependencies was made by script from http://www.debian.org/doc/maint-guide/ch-dreq.en.html strace -f -o /tmp/log make for x in `dpkg -S $(grep open /tmp/log|\ perl -pe 's!.* open\(\([^\]*).*!$1!' |\ grep ^/| sort | uniq|\ grep -v ^\(/tmp\|/dev\|/proc\) ) 2/dev/null|\ cut -f1 -d:| sort | uniq`; \ do \ echo -n $x (= `dpkg -s $x|grep ^Version|cut -f2 -d:` ), ; \ done You really think I should install only libclthreads and libclxclient? cheers mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
