Hi,
I am having trouble understanding how to build a quilt based
source-package. My packaging is based on quilt, but when running
debuild, debuild creates a traditional style source package.
I've tried to add Format: 3.0 (quilt) to the control file and a Format
3 source package is correctly
Hi Paul
Thanks a lot for your feedback on the packaging for udav.
On Sun, May 03, 2009 at 11:45:21AM +0800, Paul Wise wrote:
Some feedback based on the diff.gz:
Please get your package description reviewed by the
debian-l10n-englist email list, it contains some gramatical errors.
I sent a
On Sun, May 3, 2009 at 2:35 PM, Salvatore Bonaccorso
salvatore.bonacco...@gmail.com wrote:
How the above spelling-error-in-binary was done?
I have a pbuilder hook that runs this lintian command and always use
the latest lintian from sid:
lintian --info --display-info --display-experimental
Dear mentors,
I am looking for a sponsor for my package inosync.
* Package name: inosync
Version : 0.2-1
Upstream Author : Benedikt Böhm b...@xnull.de
* URL : http://bb.xnull.de/projects/inosync/
* License : BSD
Section : utils
It builds these
Hi, Russ.
I'd like to make it clear that I'm just brainstorming here and that at
this stage, I'm not really concerned with the feasibility of the ideas.
I'm just doing a what if thing.
On May 02 2009, Russ Allbery wrote:
Rogério Brito rbr...@ime.usp.br writes:
* for instance deprecated
Quoting Magnus Holmgren holmg...@debian.org:
On lördagen den 2 maj 2009, Dmitrijs Ledkovs wrote:
2009/5/2 Magnus Holmgren holmg...@debian.org:
On torsdagen den 26 mars 2009, Michal Čihař wrote:
Dne Thu, 26 Mar 2009 15:21:29 +0100
Adam Ziaja a...@ziaja.name napsal(a):
The package appears
Hi, Paul.
As you read my message earlier, I think that it would be a good thing to
take this reply of yours to illustrate what I had in mind when I said
things of doing more extensive automated checks:
On May 03 2009, Paul Wise wrote:
Some feedback based on the diff.gz:
(...)
It might be a
On Sun, May 3, 2009 at 3:26 PM, George Danchev danc...@spnet.net wrote:
Running just lintian on m.d.o is not enough, what is indeed needed is
lintian from *sid* to be run over the package. I'm guessing that m.d.o is
running lintian from stable which knows less than the lintian from sid for
Rogério Brito rbr...@ime.usp.br writes:
I'd like to make it clear that I'm just brainstorming here and that at
this stage, I'm not really concerned with the feasibility of the ideas.
I'm just doing a what if thing.
Oh, sure, totally understood.
On May 02 2009, Russ Allbery wrote:
Lintian
2009/5/3 Rogério Brito rbr...@ime.usp.br:
On May 03 2009, Paul Wise wrote:
Some feedback based on the diff.gz:
(...)
It might be a good idea to put an icon in the menu file. From the
upstream screenshots it looks like they have one you could use.
This one could be automated, perhaps?
A
On Sun, 03 May 2009 01:01:51 -0700
Russ Allbery r...@debian.org wrote:
* seeing if a given package providing a library has the -dev package
containing the soname in the name of the package (e.g., libfoo0-dev).
This is sometimes the right thing to do, sometimes not.
I know, I know.
Quoting Paul Wise p...@debian.org:
On Sun, May 3, 2009 at 3:26 PM, George Danchev danc...@spnet.net wrote:
Running just lintian on m.d.o is not enough, what is indeed needed is
lintian from *sid* to be run over the package. I'm guessing that m.d.o is
running lintian from stable which knows
2009/5/2 Neil Williams codeh...@debian.org:
One important fact missing from your RFS: what programming language(s)
is/are in use in the package? No need to specify the build system, just
the basic C, C++, C#, python, perl, etc. although it would be better to
mention C source code using
On Sun, May 3, 2009 at 4:01 PM, Russ Allbery r...@debian.org wrote:
I wonder if the easy way to do this would be to write something (this
wouldn't be Lintian) that analyzes a build log for interesting issues.
debexpo will probably do this. IIRC the hppa (or was it ia64) porters
do this for gcc
2009/5/3 George Danchev danc...@spnet.net:
Nod. I'm in favour of removing any lintian assertions from m.d.o, since that
might be misleading.
Maybe write something like:
[Check the package with lintian --pedantic and explain the reason for
warnings and errors or state that is clean]
In the RFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Luca Niccoli schrieb:
Depending on the answer to the above, I may sponsor it - one step I
At the moment Patrick is doing an extensive review of it, so it would
be doubled work I guess.
If he won't be able/willing to sponsor it, I will ask again,
This is a big package with a high popcon count, do you have the time
for such a large task? On your own? Is there any upstream activity?
I have the intention to try. And of course all help is appreciated, but
I would say that any improvement over inactivity is good. I really think
this cleaning
Dear mentors,
I am looking for a sponsor for my package valkyrie.
* Package name: valkyrie
Version : 1.4.0-1
Upstream Author : Donna Robinson
* URL : [fill in URL of upstreams web site]
* License : [fill in]
Section : devel
It builds these binary
On Sunday 03 May 2009 08:15:42 Benjamin Mesing wrote:
Hi,
I am having trouble understanding how to build a quilt based
source-package. My packaging is based on quilt, but when running
debuild, debuild creates a traditional style source package.
I've tried to add Format: 3.0 (quilt) to the
Dear mentors,
I am looking for a sponsor for my package libbash.
* Package name: libbash
Version : 0.9.10b
Upstream Author : Hai Zaar haiz...@haizaar.com
* URL : http://libbash.sf.net
* License : GPLv3
Section : libs
It builds these binary packages:
On Tuesday 23 December 2008, Charles Plessy wrote:
I see from your home page that you have some interest in neuroscience. Do you
know the Debian Med project? If your neuroLab library is used by other free
softwares, you are welcome to package it within our team.
At the moment I'm busy
On Sunday 03 May 2009 13:24:12 Luca Niccoli wrote:
2009/5/3 George Danchev danc...@spnet.net:
Nod. I'm in favour of removing any lintian assertions from m.d.o, since
that might be misleading.
Maybe write something like:
[Check the package with lintian --pedantic and explain the reason for
Dear mentors,
I am looking for a sponsor for my package libapache2-mod-authz-unixgroup.
* Package name: libapache2-mod-authz-unixgroup
Version : 1.0.1-1
Upstream Author : Jan Wolter j...@unixpapa.com
* URL : http://www.unixpapa.com/mod_authz_unixgroup/
* License
Hi Paul and all
On Sun, May 03, 2009 at 11:45:21AM +0800, Paul Wise wrote:
On Sun, May 3, 2009 at 6:39 AM, Salvatore Bonaccorso
salvatore.bonacco...@gmail.com wrote:
- dget http://mentors.debian.net/debian/pool/main/u/udav/udav_0.5.1-1.dsc
Some feedback based on the diff.gz:
Please
Dear mentors,
I am looking for a sponsor for my package libapache2-mod-authnz-external.
* Package name: libapache2-mod-authnz-external
Version : 3.2.3
Upstream Author : Jan Wolter j...@unixpapa.com
* URL : http://www.unixpapa.com/mod_auth_external/
* License :
+ Paul Wise (Sun, 03 May 2009 15:56:23 +0800):
m.d.n (currently) only has source packages to deal with so that makes
the lintian warnings from there much less useful.
Will/could/should debexpo require that uploads are accompanied with
binaries, even if to throw them away after running eg.
On Sun, 3 May 2009 22:25:07 +0200
Adeodato Simó d...@net.com.org.es wrote:
+ Paul Wise (Sun, 03 May 2009 15:56:23 +0800):
m.d.n (currently) only has source packages to deal with so that
makes the lintian warnings from there much less useful.
Will/could/should debexpo require that
Dear mentors,
I am looking for a sponsor for my package drraw. It is a simple yet
powerful tool for producing graphs out of RRD files and showing them
on the web.
I guess I've done a tolerable work of packaging it. However this is my
first package an I need your advice and sponsorship for
Luca Niccoli lultimou...@gmail.com writes:
Maybe write something like:
[Check the package with lintian --pedantic and explain the reason for
warnings and errors or state that is clean]
I suppose it makes sense to recommend --pedantic if that's what all the
mentors are using, but just to be
Dear mentors,
I am looking for a sponsor for my package pwauth.
* Package name: pwauth
Version : 2.3.8-1
Upstream Author : Jan Wolter j...@unixpapa.com
* URL : http://code.google.com/p/pwauth/
* License : BSD
Section : utils
It builds these binary
Dear mentors,
still looking for a sponsor for my package texttrainer (1).
* Package name: texttrainer
Version : 0.0.3-1
Upstream Author : Jacob Kanev j_ka...@arcor.de
* URL : http://home.arcor.de/j_kanev/texttrainer
* License : GPL 3
Language: C++
Dear mentors,
I've accidentally hit send button to early. I want to submit my RFS
again with all fields filled in.
I am looking for a sponsor for my package valkyrie.
* Package name : valkyrie
Version : 1.4.0-1
Upstream Author : Donna Robinson do...@valgrind.org
* URL :
In 87d4aq2t1l@windlord.stanford.edu, Russ Allbery wrote:
Luca Niccoli lultimou...@gmail.com writes:
Maybe write something like:
[Check the package with lintian --pedantic and explain the reason for
warnings and errors or state that is clean]
I suppose it makes sense to recommend --pedantic
In 20090503202507.ga2...@chistera.yi.org, Adeodato Simó wrote:
+ Paul Wise (Sun, 03 May 2009 15:56:23 +0800):
m.d.n (currently) only has source packages to deal with so that makes
the lintian warnings from there much less useful.
Will/could/should debexpo require that uploads are accompanied
34 matches
Mail list logo
