Nabble - debian-mentors

Re: Need informations about BTS

2008-09-08T01:56:01Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Wise a écrit :

> On Mon, Sep 8, 2008 at 4:05 AM, Laurent Guignard <lguignard2000@...> wrote:
>
>> The bug i need to declare is a dependency of a specific patched version
>> of libnet0 package that is under an ITA procedure ?
>> I have found a "block" command of the BTS but i don't know where to find
>> the "bug" number of ITA of David Paleino that intend to adopt the
>> libnet0 package. Where can i found it if the block command is the one
>> that i need to use ?
>
> David intents to adopt libnet not libnet0:
>
> http://packages.qa.debian.org/libn/libnet.html
> http://bugs.debian.org/483710
>
> libnet0 is marked as an obsolete library, you might want to get
> upstream on dhcp_probe to switch to libnet instead of libnet0. If
> there is no upstream for dhcp_probe you should create a new upstream
> project for it.
>

Sorry for noise i made the mistake on the package name.
It is the libnet package i have in mind and dhcp_probe is needed...

Best regards

- --
Laurent Guignard, Registered as user #301590 with the Linux Counter 
Site : http://www.famille-guignard.org 
Blog : http://blog.famille-guignard.org 
Projet : http://sicontact.sourceforge.net 
GULL de Villefranche sur Saône : http://www.cagull.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIxOihjcKpXFc/7oYRAv8pAJ9KOEat7EYRjt7AVDoo3I5mpPS62QCfUYk0
t/moLSStc1+F8wVmddjuJNc=
=pYOk
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Need informations about BTS

2008-09-07T18:38:05Z

On Mon, Sep 8, 2008 at 4:05 AM, Laurent Guignard <lguignard2000@...> wrote:

> The bug i need to declare is a dependency of a specific patched version
> of libnet0 package that is under an ITA procedure ?
> I have found a "block" command of the BTS but i don't know where to find
> the "bug" number of ITA of David Paleino that intend to adopt the
> libnet0 package. Where can i found it if the block command is the one
> that i need to use ?

David intents to adopt libnet not libnet0:

http://packages.qa.debian.org/libn/libnet.html
http://bugs.debian.org/483710

libnet0 is marked as an obsolete library, you might want to get
upstream on dhcp_probe to switch to libnet instead of libnet0. If
there is no upstream for dhcp_probe you should create a new upstream
project for it.

--
bye,
pabs

http://wiki.debian.org/PaulWise

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: libmarkdown-php

2008-09-07T16:09:40Z

Daniel Watkins wrote:

> On Sun, 07 Sep 2008 14:22:32 -0500
>
> The updated package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/l/libmarkdown-php
> - Source repository: deb-src http://mentors.debian.net/debian unstable
> main contrib non-free
> - dget
>
http://mentors.debian.net/debian/pool/main/l/libmarkdown-php/libmarkdown-php_1.0.1m-1.dsc
>

With the sole exception being the fact that the Readme also contains the
changelog, it looks fine to me now (you could actually add
a 'changelog.gz' -> 'README.gz' symlink).

It is now up to a DD to sponsor the package (I'm stuck on NM, so can't do
it), which shouldn't be so hard now.

>
> Cheers,
>
> Dan
>

Cheers,
--
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Determining native or non-native package inside pbuilder

2008-09-07T15:53:24Z

"Daniel Moerner" <dmoerner@...> writes:

> Actually, most of the vcs-based package builders look in ../tarballs.
> Git-buildpackage looks there if pristine-tar is not being used to
> manage building, as does bzr-builddeb.

Indeed, I mostly use the '${VCS}-buildpackage' commands, which is why
I am accustomed to upstream source appearing in '../tarballs/'. I had
expected 'pbuilder' (and, by extension, 'pdebuild') to behave the
same.

> However, these are only wrappers around dpkg-buildpackage, and tell
> it where to look for the source.

I can't see any option on the 'dpkg-buildpackage' manpage to tell it
the location of the upstream source tarball. What option do I need?

--
\ “[On the Internet,] power and control will shift to those who |
`\ are actually contributing something useful rather than just |
_o__) having lunch.” —Douglas Adams |
Ben Finney

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Need informations about BTS

2008-09-07T14:21:47Z

Hello Laurent,

On Sun, Sep 7, 2008 at 22:05, Laurent Guignard <lguignard2000@...> wrote:
> How to set a bug about the package i try to build (dhcp_probe) in the BTS ?

Err, I don't understand here... may you please try to rephrase a bit?

> The bug i need to declare is a dependency of a specific patched version
> of libnet0 package that is under an ITA procedure ?
> I have found a "block" command of the BTS but i don't know where to find
> the "bug" number of ITA of David Paleino that intend to adopt the

ITA/ITP/RFP/O/RFA all belong to wnpp "pseudo-package", so you'll find
all of them searching for wnpp (or looking at PTS page for libnet0[1])
and it's #483713 (but I can't see it as ITA, but still O)

> libnet0 package. Where can i found it if the block command is the one
> that i need to use ?

If you want to state that "my bug can't be solved because it depends
on the resolution of this other bug" than block command is what you're
looking fore.

Sandro

[1] http://packages.qa.debian.org/libn/libnet0.html

--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Need informations about BTS

2008-09-07T14:17:53Z

On Sun, Sep 07, 2008 at 10:05:54PM +0200, Laurent Guignard wrote:

> Hello mentors,
>
> How to set a bug about the package i try to build (dhcp_probe) in the BTS ?
>
> The bug i need to declare is a dependency of a specific patched version
> of libnet0 package that is under an ITA procedure ?
> I have found a "block" command of the BTS but i don't know where to find
> the "bug" number of ITA of David Paleino that intend to adopt the
> libnet0 package. Where can i found it if the block command is the one
> that i need to use ?
>
> Thanks for your answers.

As shown at libnet0's PTS page [0], this package is still orphaned, and
as you can see at [1] it seems like noone ever renamed such bug O->ITA.

Regards,
Cristian

[0] http://packages.qa.debian.org/libn/libnet0.html
[1] http://bugs.debian.org/483713

signature.asc (204 bytes) Download Attachment

Need informations about BTS

2008-09-07T13:05:54Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello mentors,

How to set a bug about the package i try to build (dhcp_probe) in the BTS ?

The bug i need to declare is a dependency of a specific patched version
of libnet0 package that is under an ITA procedure ?
I have found a "block" command of the BTS but i don't know where to find
the "bug" number of ITA of David Paleino that intend to adopt the
libnet0 package. Where can i found it if the block command is the one
that i need to use ?

Thanks for your answers.

- --
Laurent Guignard, Registered as user #301590 with the Linux Counter 
Site : http://www.famille-guignard.org 
Blog : http://blog.famille-guignard.org 
Projet : http://sicontact.sourceforge.net 
GULL de Villefranche sur Saône : http://www.cagull.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIxDQijcKpXFc/7oYRAgN+AJsFfixXzeJjHQBfZXwNrJ25jGyM5ACgoBXT
w3jFgfejfXn9l5ubXSHVnS8=
=FpPu
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: libmarkdown-php

2008-09-07T12:59:15Z

On Sun, 07 Sep 2008 14:22:32 -0500
Raphael Geissert <atomo64+debian@...> wrote:
> You have to rename the file before debhelper builds the package, I.e.
> after install and before binary.
D'oh! Fixed.

> Oh, and:
>
> debian/copyright:
> > The Debian packaging is (C) 2008, Daniel Watkins
> <daniel@...>
> > and is licensed under the BSD, see above.
>
> N: The copyright file contains dh-make's incomplete Debian packaging
> N: copyright boilerplate. As (C) is not considered as a valid way to
> N: express the copyright ownership the word Copyright or the © symbol
> N: should be used instead or in addition to (C).
>
> (based on a check I wrote for lintian, but not yet merged)

Also fixed.

The updated package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/l/libmarkdown-php
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/l/libmarkdown-php/libmarkdown-php_1.0.1m-1.dsc

Cheers,

Dan

--
Daniel Watkins (Odd_Bloke)

signature.asc (204 bytes) Download Attachment

Re: RFS: libmarkdown-php

2008-09-07T12:22:32Z

Daniel Watkins wrote:

> Hi Raphael,
>
> Thanks for the continuing attention.
>
> On Sun, 24 Aug 2008 19:16:14 -0500
> Raphael Geissert <atomo64+debian@...> wrote:
>> debian/rules:
>> The package FTBFS twice in a row because it moves the "PHP Markdown
>> Readme.text" in the main directory without rolling back that change
>> at the clean target (another possible solution would be to rename the
>> file once it is under debian/).
> Fixed.

Hmmm, not quite right:

libmarkdown-php_1.0.1m-1_all.deb
--------------------------------
new debian package, version 2.0.
size 28602 bytes: control archive= 911 bytes.
1009 bytes, 24 lines control
311 bytes, 4 lines md5sums
Package: libmarkdown-php
Version: 1.0.1m-1
Architecture: all
Maintainer: Daniel Watkins <daniel@...>
Installed-Size: 96
Depends: php5 | php5-cli
Section: web
Priority: optional
Homepage: http://michelf.com/projects/php-markdown/
Description: PHP library for rendering Markdown data
"Markdown" is two things: a plain text markup syntax, and a software
tool that converts the plain text markup to HTML for publishing on the
web.
.
The Markdown syntax allows you to write text naturally and format it
without using HTML tags. More importantly: in Markdown format, your text
stays enjoyable to read for a human being, and this is true enough that
it makes a Markdown document publishable as-is, as plain text. If you
are using text-formatted email, you already know some part of the
syntax.
.
PHP Markdown can work as a plug-in for WordPress and bBlog, as a
modifier for the Smarty templating engine, or as a replacement for
textile formatting in any software that support textile.
drwxr-xr-x root/root 0 2008-09-07 14:15 ./
drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/
drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/
drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/php/
-rw-r--r-- root/root 48310 2008-06-21 01:58 ./usr/share/php/markdown.php
drwxr-xr-x root/root 0 2008-09-07 14:15 ./usr/share/doc/
drwxr-xr-x root/root 0 2008-09-07
14:15 ./usr/share/doc/libmarkdown-php/
-rw-r--r-- root/root 9535 2008-06-21
01:58 ./usr/share/doc/libmarkdown-php/PHP Markdown Readme.text.gz
-rw-r--r-- root/root 1475 2008-09-07
14:12 ./usr/share/doc/libmarkdown-php/copyright
-rw-r--r-- root/root 165 2008-09-07
14:12 ./usr/share/doc/libmarkdown-php/changelog.Debian.gz

You have to rename the file before debhelper builds the package, I.e. after
install and before binary.

Oh, and:

debian/copyright:
> The Debian packaging is (C) 2008, Daniel Watkins
<daniel@...>
> and is licensed under the BSD, see above.

N: The copyright file contains dh-make's incomplete Debian packaging
N: copyright boilerplate. As (C) is not considered as a valid way to
N: express the copyright ownership the word Copyright or the © symbol
N: should be used instead or in addition to (C).

(based on a check I wrote for lintian, but not yet merged)

>
> Cheers,
>
> Dan
>

Cheers,
--
Atomo64 - Raphael

Please avoid sending me Word, PowerPoint or Excel attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Determining native or non-native package inside pbuilder

2008-09-07T09:32:50Z

> dpkg-buildpackage expects it to be in ../foo_*. svn-buildpackage is the only one
> that uses ../tarballs AFAIK.
>

Actually, most of the vcs-based package builders look in ../tarballs.
Git-buildpackage looks there if pristine-tar is not being used to
manage building, as does bzr-builddeb. However, these are only
wrappers around dpkg-buildpackage, and tell it where to look for the
source.

--
Daniel Moerner <dmoerner@...>

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: libmarkdown-php

2008-09-07T08:49:36Z

Hi Raphael,

Thanks for the continuing attention.

On Sun, 24 Aug 2008 19:16:14 -0500
Raphael Geissert <atomo64+debian@...> wrote:
> debian/rules:
> The package FTBFS twice in a row because it moves the "PHP Markdown
> Readme.text" in the main directory without rolling back that change
> at the clean target (another possible solution would be to rename the
> file once it is under debian/).
Fixed.

> debian/copyright:
> The same issue about licencing your packaging as GPL (without
> specifying the version of the licence) while upstream uses a
> different licence (in this case BSD) applies.
Fixed.

> debian/control:
> Just out of curiosity, why there isn't a bzr repository for this
> package? :)
I just forgot. Fixed.

The updated package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/l/libmarkdown-php
- Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/l/libmarkdown-php/libmarkdown-php_1.0.1m-1.dsc

Cheers,

Dan

--
Daniel Watkins (Odd_Bloke)

signature.asc (204 bytes) Download Attachment

Re: Determining native or non-native package inside pbuilder

2008-09-07T07:33:24Z

Ben Finney wrote:

> "Paul Wise" <pabs@...> writes:
>
>> On Sun, Sep 7, 2008 at 3:33 PM, Ben Finney <ben+debian@...>
>> wrote:
>> > "Paul Wise" <pabs@...> writes:
>> >
>> >> Usually this warning is produced because of an incorrectly named
>> >> orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good).
>> >> Perhaps that is the issue?
>> >
>> > Perhaps. But as far as I know, I have no control over the name of the
>> > tarball; it's generated automatically as part of 'pdebuild'.
>> >
>> > What do I need to do so that the correct tarball name (i.e. correctly
>> > indicating native or non-native) is used when I run 'pdebuild'?
>>
>> A native tar.gz (rather than a non-native orig.tar.gz) is only
>> generated automatically when you don't have an orig.tar.gz file. I
>> suggest removing all tar.gz files below your source directory and
>> doing something like this in the source directory:
>>
>> wget -O ../foo_1.2.3.orig.tar.gz http://foo.bar.com/foo-1.2.3.tar.gz
>
> Should I expect it to be found at '../tarballs/foo_1.2.3.orig.tar.gz'?
> That's where 'dpkg-buildpackage' and other tools seem to expect it.

dpkg-buildpackage expects it to be in ../foo_*. svn-buildpackage is the only one
that uses ../tarballs AFAIK.

>
> Is 'pbuilder' different in this regard? I'd rather not have the same
> file needing to appear at multiple places just to get the Debian tools
> working in concert.

pbuilder requires whatever you use as a builder. The default is
dpkg-buildpackage, so it will expect the orig in ..

--

Felipe Sateler

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: freeguide (updated package)

2008-09-07T05:09:43Z

Hi Vincent,

On Sun, 07 Sep 2008 12:46:32 +0200
Vincent Bernat <bernat@...> wrote:

> OoO En cette nuit nuageuse du lundi 01 septembre 2008, vers
> 00:10, Daniel Watkins <daniel@...> disait :
>
> > The updated package can be found on mentors.debian.net:
> > - URL: http://mentors.debian.net/debian/pool/contrib/f/freeguide
> > - Source repository: deb-src http://mentors.debian.net/debian
> > unstable main contrib non-free
> > - dget
> > http://mentors.debian.net/debian/pool/contrib/f/freeguide/freeguide_0.10.7-1.dsc
>
> Hi Daniel!
>
> Seems fine. I have uploaded it.

Thanks!

> For the next version, you might want to add a source lintian override
> for this:
> I: freeguide source: build-depends-without-arch-dep ant
> Or file a bug against lintian since, most of the time, ant is used
> in clean target too.
Sure, I'll look into it.

Cheers,

Dan

--
Daniel Watkins (Odd_Bloke)

signature.asc (204 bytes) Download Attachment

Re: Determining native or non-native package inside pbuilder

2008-09-07T04:33:41Z

On Sun, Sep 7, 2008 at 7:27 PM, Ben Finney <ben+debian@...> wrote:

> Should I expect it to be found at '../tarballs/foo_1.2.3.orig.tar.gz'?
> That's where 'dpkg-buildpackage' and other tools seem to expect it.
>
> Is 'pbuilder' different in this regard? I'd rather not have the same
> file needing to appear at multiple places just to get the Debian tools
> working in concert.

Whereever pdbuilder/etc expects it should be fine, I was just guessing
where you keep your tarballs.

--
bye,
pabs

http://wiki.debian.org/PaulWise

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Determining native or non-native package inside pbuilder

2008-09-07T04:27:21Z

"Paul Wise" <pabs@...> writes:

> On Sun, Sep 7, 2008 at 3:33 PM, Ben Finney <ben+debian@...> wrote:
> > "Paul Wise" <pabs@...> writes:
> >
> >> Usually this warning is produced because of an incorrectly named
> >> orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good).
> >> Perhaps that is the issue?
> >
> > Perhaps. But as far as I know, I have no control over the name of the
> > tarball; it's generated automatically as part of 'pdebuild'.
> >
> > What do I need to do so that the correct tarball name (i.e. correctly
> > indicating native or non-native) is used when I run 'pdebuild'?
>
> A native tar.gz (rather than a non-native orig.tar.gz) is only
> generated automatically when you don't have an orig.tar.gz file. I
> suggest removing all tar.gz files below your source directory and
> doing something like this in the source directory:
>
> wget -O ../foo_1.2.3.orig.tar.gz http://foo.bar.com/foo-1.2.3.tar.gz

Should I expect it to be found at '../tarballs/foo_1.2.3.orig.tar.gz'?
That's where 'dpkg-buildpackage' and other tools seem to expect it.

Is 'pbuilder' different in this regard? I'd rather not have the same
file needing to appear at multiple places just to get the Debian tools
working in concert.

--
\ “Pinky, are you pondering what I'm pondering?” “I think so, |
`\ Brain, but three round meals a day wouldn't be as hard to |
_o__) swallow.” —_Pinky and The Brain_ |
Ben Finney

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: winff

2008-09-07T03:57:04Z

OoO En ce début d'après-midi ensoleillé du vendredi 05 septembre 2008,
vers 15:07, Paul Gevers <paul@...> disait :

>> I: winff: desktop-entry-contains-encoding-key /usr/share/applications/winff.desktop:3 Encoding
>> N:
>> N: The Encoding key is now deprecated by the FreeDesktop standard and all
>> N: strings are required to be encoded in UTF-8. This desktop entry
>> N: explicitly specifies an Encoding of UTF-8, which is harmless but no
>> N: longer necessary.
>> N:
>> N: Refer to
>> N: http://standards.freedesktop.org/desktop-entry-spec/1.0/apc.html for
>> N: details.

> Removed the appropriate line. I did not get the lintian warning thou, so
> what did I do wrong during my checking of this package?

Hi Paul!

This is an "informational" warning. You need to use "-I" to get it. I
usually uses "lintian -viI".

> By the way, should I mention the changes for mentors also in the
> changelog? It looks to me that you don't want them in "real" Debian, so
> I left them out, but I am not sure.

It depends of the sponsor. Personally, I don't care: it is easier to
compare what have been done when you put a different version but it is
harder to build the proper package (you need to not forget to include
original tarball and all changelog entries).

> Uploaded again to mentors (bumped version to -2 for comparison):
> - URL: http://mentors.debian.net/debian/pool/main/w/winff
> - Source repository: deb-src http://mentors.debian.net/debian unstable
> main contrib non-free
> - dget http://mentors.debian.net/debian/pool/main/w/winff/winff_0.42-2.dsc

Seems fine. Uploaded.
--
printk("autofs: Out of inode numbers -- what the heck did you do??\n");
2.0.38 /usr/src/linux/fs/autofs/root.c

attachment0 (202 bytes) Download Attachment

Re: RFS: freeguide (updated package)

2008-09-07T03:46:32Z

OoO En cette nuit nuageuse du lundi 01 septembre 2008, vers 00:10,
Daniel Watkins <daniel@...> disait :

> The updated package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/contrib/f/freeguide
> - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free
> - dget http://mentors.debian.net/debian/pool/contrib/f/freeguide/freeguide_0.10.7-1.dsc

Hi Daniel!

Seems fine. I have uploaded it. For the next version, you might want to
add a source lintian override for this:
I: freeguide source: build-depends-without-arch-dep ant
Or file a bug against lintian since, most of the time, ant is used in
clean target too.
--
printk("??? No FDIV bug? Lucky you...\n");
2.2.16 /usr/src/linux/include/asm-i386/bugs.h

attachment0 (202 bytes) Download Attachment

mentors.debian.net flaky - but not much longer

2008-09-07T00:59:11Z

Dear maintainers,

I'd like to apologize for the unreliability of mentors.debian.net in the
last weeks. I am experiencing a wild mixture of problems in the backend
code, the PGP verification and the mysql database. That lead to packages
either left in the upload directory or being thrown away randomly during
the import into the repository.

The good news is that I had the honor to be the mentor of the Google Summer
of Code project called 'debexpo' [0] [1] that I proposed and which is a
web-based Debian package repository software. Jonny Lamb - the student and
author - finished the project recently and we are sorting out a few last
things about before I intend to use it for mentors.debian.net. It's no
conincidence that it will look pretty much the same as the current
mentors.debian.net site because that was one of the design goals. But it's
also flexible enough to provide personal package archives (PPAs) [2] or
apt-get'able repositories like 'debpool' [3] creates if anyone is
interested.

Expect an announcement of the beta relaunch of mentors.debian.net based on
debexpo soon on this mailing list. Jonny and I will welcome your feedback
then.

I just wanted to tell you that I'm aware of the problems and am working on
a remedy right now.

Cheers
Christoph

[0] http://debexpo.workaround.org/
[1] http://wiki.debian.org/SummerOfCode2008/debexpo
[2] http://code.google.com/p/debppa/
[3] http://wiki.debian.org/debpool

signature.asc (204 bytes) Download Attachment

Re: Determining native or non-native package inside pbuilder

2008-09-07T00:41:00Z

On Sun, Sep 7, 2008 at 3:33 PM, Ben Finney <ben+debian@...> wrote:

> "Paul Wise" <pabs@...> writes:
>
>> Usually this warning is produced because of an incorrectly named
>> orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good).
>> Perhaps that is the issue?
>
> Perhaps. But as far as I know, I have no control over the name of the
> tarball; it's generated automatically as part of 'pdebuild'.
>
> What do I need to do so that the correct tarball name (i.e. correctly
> indicating native or non-native) is used when I run 'pdebuild'?

A native tar.gz (rather than a non-native orig.tar.gz) is only
generated automatically when you don't have an orig.tar.gz file. I
suggest removing all tar.gz files below your source directory and
doing something like this in the source directory:

wget -O ../foo_1.2.3.orig.tar.gz http://foo.bar.com/foo-1.2.3.tar.gz

--
bye,
pabs

http://wiki.debian.org/PaulWise

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Determining native or non-native package inside pbuilder

2008-09-07T00:33:53Z

"Paul Wise" <pabs@...> writes:

> Usually this warning is produced because of an incorrectly named
> orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good).
> Perhaps that is the issue?

Perhaps. But as far as I know, I have no control over the name of the
tarball; it's generated automatically as part of 'pdebuild'.

What do I need to do so that the correct tarball name (i.e. correctly
indicating native or non-native) is used when I run 'pdebuild'?

--
\ “Yesterday I saw a subliminal advertising executive for just a |
`\ second.” —Steven Wright |
_o__) |
Ben Finney

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Determining native or non-native package inside pbuilder

2008-09-07T00:09:27Z

Usually this warning is produced because of an incorrectly named
orig.tar.gz - foo-1.2.orig.tar.gz (bad) vs foo_1.2.orig.tar.gz (good).
Perhaps that is the issue?

--
bye,
pabs

http://wiki.debian.org/PaulWise

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Determining native or non-native package inside pbuilder

2008-09-06T20:19:59Z

Howdy all,

I'm using a 'pbuilder' hook to run 'lintian' over the generated package:

===== B91_lintian =====
#! /bin/sh
# Run lintian on the generated package

echo "I: installing lintian and running it on the package"
apt-get install -y --force-yes lintian &>/dev/null
lintian --allow-root --color=always -I /tmp/buildd/*.changes | tee /tmp/buildd/lintian
=====

I then use 'pdebuild' from the source tree to package and install in
the pbuilder. When this hook runs, I get the following output:

=====
I: installing lintian and running it on the package
W: python-coverage source: debian-watch-file-in-native-package
W: python-coverage source: native-package-with-dash-version
=====

The package is 'python-coverage' version 2.80-2, and is not a native
Debian package.

What do I need to do with 'pbuilder' to allow the 'lintian' running
inside it to correctly determine native or non-native status of the
package?

--
\ “Broken promises don't upset me. I just think, why did they |
`\ believe me?” —Jack Handey |
_o__) |
Ben Finney

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFC: QA vs NMU on ssystem - 3D solar system simulator

2008-09-06T14:53:29Z

Eduardo M KALINOWSKI <eduardo@...> writes:
> Paul Gevers wrote:

>> Further, there is one lintian warning left:
>> I: ssystem: arch-dep-package-has-big-usr-share 1224kB 83%
>> I can (easily) fix this, but that way I change the package more than I
>> think is appropriate for QA. What do others think? Should I fix this as
>> well?

> As far as I understand, if the package is orphaned, you could do that
> change in the package, it would not be considered too 'abusive'. But you
> do not have to, fixing only the bug is already a good contribution.

> However, even if 83% of the package is architecture independent data,
> the whole package uncompressed only takes about 1,5Mb, and the whole
> compressed package is 'Mb. Even considering all the architectures, the
> space saved in mirrors and in bandwidth transferred is not so big, and
> IMHO does not justifies two separate packages (ssystem and ssystem-data).

That would imply that Lintian's threshold for this warning is too low.
What do other people think?

--
Russ Allbery (rra@...) <http://www.eyrie.org/~eagle/>

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFC: QA vs NMU on ssystem - 3D solar system simulator

2008-09-06T13:01:23Z

Paul Gevers wrote:

> Hello mentors,
>
> I like some comments on the following:
>
> I made some small changes to an orphaned package (ssystem), to fix a bug
> (#482936) and to fix some lintian errors/warnings. I understand that
> this should be a QA upload because QA is maintainer, but I might be
> wrong and that this should be a NMU. Am I right? Because upstream is
> dead, I don't know if I should adopt it, I don't know much about C yet.
> The program is pretty old, but apparently a lot leaner on processing
> power than it's descendant called celestia.
>
> Further, there is one lintian warning left:
> I: ssystem: arch-dep-package-has-big-usr-share 1224kB 83%
> I can (easily) fix this, but that way I change the package more than I
> think is appropriate for QA. What do others think? Should I fix this as
> well?
>

As far as I understand, if the package is orphaned, you could do that
change in the package, it would not be considered too 'abusive'. But you
do not have to, fixing only the bug is already a good contribution.

However, even if 83% of the package is architecture independent data,
the whole package uncompressed only takes about 1,5Mb, and the whole
compressed package is 'Mb. Even considering all the architectures, the
space saved in mirrors and in bandwidth transferred is not so big, and
IMHO does not justifies two separate packages (ssystem and ssystem-data).

--
mother-in-law <--> woman Hitler
-- anagrama

Eduardo M KALINOWSKI
eduardo@...
http://move.to/hpkb

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

RFC: QA vs NMU on ssystem - 3D solar system simulator

2008-09-06T12:46:48Z

Hello mentors,

I like some comments on the following:

I made some small changes to an orphaned package (ssystem), to fix a bug
(#482936) and to fix some lintian errors/warnings. I understand that
this should be a QA upload because QA is maintainer, but I might be
wrong and that this should be a NMU. Am I right? Because upstream is
dead, I don't know if I should adopt it, I don't know much about C yet.
The program is pretty old, but apparently a lot leaner on processing
power than it's descendant called celestia.

Further, there is one lintian warning left:
I: ssystem: arch-dep-package-has-big-usr-share 1224kB 83%
I can (easily) fix this, but that way I change the package more than I
think is appropriate for QA. What do others think? Should I fix this as
well?

I uploaded to mentors.d.n but I am still waiting until it is processed.
It probably will be available at:
- URL: http://mentors.debian.net/debian/pool/main/s/ssystem
- dget
http://mentors.debian.net/debian/pool/main/s/ssystem/ssystem_1.6-18.dsc

With kind regards,
Paul

signature.asc (196 bytes) Download Attachment

Re: RFS: sqlmap

2008-09-06T09:53:48Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Sandro,

Sandro Tosi wrote:
> ...
> Next time, please file it before start packaging it (so we can avoid
> duplicate work on the same tool, etc etc).

Ok.

> ...
> diff.gz is the difference applied to upstream source code by the
> packager (so it usually contains debian/ directory only). You have
> "merged" both in orig tarball.

I read the documentation again and understood, fixed.

> Please split that and only release upstream tarball without debian/
> dir, and apply it only in a second moment. I just give a fast look,
> and I noticed:

Done.

> * debian/changelog has to contain changes related to debian package
> *only*, so jsut one entry with "Initial package; Closes #<ITP
> bugnumber>" is what we expect there

Fixed.

> * debian/copyright has Daniele's email wrongly typed; if the source is
> GPLv2, than link to /usr/share/common-licenses/GPL-2 (GPL is a link to
> the lastest GPL version available, so now is GPL-3)

Fixed.

> * it would have been better if you leave debian/rules as dh_make
> template proposed to you

Fixed.

> * moreover, dpatch integration is done wrong: check
> http://wiki.debian.org/DebianPackagingHandbook/PatchSystems

Fixed.

> * if you're upstream, why you need a patch system? can't you simply
> release a new version? :)

Because the changes applied by dpatch files in the sqlmap Debian package
has to be there only when sqlmap is installed by root within the
operating system.

> * don't ship pdf (in docs) if they are not generated a build time

Done.

> * check if some Build-Depends can go to Build-Depends-Indep

If you mean debian/control, I think nothing.

> * adding a watch file might be intersting

Done.

> * I still see "Description: an automatic SQL injection tool entirely
> developed in Python" and I know why: you uploaded -2 revsion, that
> DON'T upload the orig.tar.gz file (see why debianization has to be
> separated?)

I see.
I removed the old sqlmap entry then reuploaded to mentors.debian.net the
new sqlmap with all the above fixes and changes, but at the moment I
can't see it on the 'Start page' yet and more than 10 minutes passed
since the upload.

> That's enough for a 5 minutes check :)

Thanks a lot.

Regards,
- --
Bernardo Damele A. G.

E-mail / Jabber: bernardo.damele (at) gmail.com
Mobile number: +39-3493821385
PGP Key ID: 0x05F5A30F
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIwrWcdntYwQX1ow8RAnx6AKCQwrVneNL7uTOw2AHJ+jkxNamZjQCgoQC9
TFn2XgMYGv3P+W7Xy9FKEtM=
=sXuq
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: CLAM, C++ library for audio and music

2008-09-05T13:22:29Z

OoO La nuit ayant déjà recouvert d'encre ce jour du jeudi 04 septembre
2008, vers 23:26, David García Garzón <dgarcia@...> disait :

>> Please, file an ITP for this package. This will be useful to track any
>> progress, especially if someone has handled the upload or not.

> I filled it before sending the RFS:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493282

OK.

>> Moreover, the .dsc file is not signed.

> Must the key be validated by any debian maintainer at all?

This would be better but this is not mandatory. However, this should be
your key.

> As they are different source packages i don't know whether I should fill a
> single ITP bug and RFS request or just one for each.

It would be better. For example, clam could be uploaded soon while
clam-XXX could have a lot of problems and its upload would be delayed
for several months. This would be better to have its own ITP.

>> At first glance, here are the problems with the current package:
>> - debian/changelog has an incorrect distribution

> I think that dhc has an --distribution option that could do the work.

Or you can just edit by hand. ;-)

> We are creating the dsc files from ubuntu and then generating all the packages
> for debian and ubuntu with pbuilder using that same dsc. The script we are
> using, at clam/CLAM/scripts/doDebianPackages.py, is very convenient for us to
> provide non-official debian and ubuntu packages. But maybe not the way to
> proceed when officializing the procedure. Any suggestions are wellcome in
> that sense.

Everybody is free to generate packages as they want to. However, keep in
mind that you need to write sensible changelog (the script will have
some difficulties). As long as the script gives good results, this is
fine to use it.

>> - Vcs-* fields is for Debian packaging, not upstream VCS repository

> Debian packaging is currently maintained at the upstream VCS. That is also
> very convenient for us at the moment as we are doing fixes to the packaging
> as we do changes on the install. But we really need advice as this seems also
> to produce some inconveniences. Being debian maintained in the same
> repository, are those fields ok? Should we keep a separate repository? Could
> we just to store the diff of the debian a part and keep most of debian
> folders in upstream svn?

Both questions are related. Even if now, upstream and Debian packager
are closely related, this may not be the case in the future. Debian
packaging should only be targeted to go into Debian, not to be
downloaded from the website, not to be included into Ubuntu (even if it
will eventually migrate to Ubuntu when present in Debian).

For example, in the packages that you propose to download from the
website, you could widen the dependencies by depending on software not
available any more or by suggesting softwares not available into
Debian. Therefore, you need a dedicated branch or repository.

>> - some of the files are licensed under MIT/X11, some are GPLv2 only

> I guess they are included 3rd party files. Any suggestion on how to deal with
> that?

You just have to mention the files licensed under different licenses in
debian/copyright. As long as the licenses are compatible, there is no
problem.

>> - examples should be packaged with dh_examples

> Do you mean dh_installexamples?

Yes.

> Well i saw that qt4 package just ships a tarball. Is it that done by
> dh_installexamples? Well i'll use dh_installexamples and see what i
> get.

Dunno. I think this is a bad idea to install examples as tar.gz. The
user need to unpack them somewhere while he has explicitely asked for
their installation.

> Thanks for all the suggestions and fixes. We might need advice regarding how
> to adapt our current release process to something more debian
> friendly.

Start with a fresh changelog, just for Debian. Try to apply the above
suggestions and we will review the packages again.
--
I NO LONGER WANT MY MTV
I NO LONGER WANT MY MTV
I NO LONGER WANT MY MTV
-+- Bart Simpson on chalkboard in episode 3G02

attachment0 (202 bytes) Download Attachment

Re: RFS: vbackup

2008-09-05T13:00:30Z

OoO En ce début de soirée du jeudi 04 septembre 2008, vers 21:18,
Stefanos Harhalakis <v13@...> disait :

> I fixed them all in the debian package and added the man page fix
> to "upstream" too for the next release. I've also removed the Makefile.in
> modifications, config.sub, config.guess and the following lines from
> debian/rules:

> ifneq "$(wildcard /usr/share/misc/config.sub)" ""
> cp -f /usr/share/misc/config.sub config.sub
> endif
> ifneq "$(wildcard /usr/share/misc/config.guess)" ""
> cp -f /usr/share/misc/config.guess config.guess
> endif

You can keep those lines.

> I also have a question. Should I change anything else in debian/rules to
> indicate that this is not an architecture dependend package? I don't like
> seeing the file: vbackup_0.1.6-2_i386.changes (why i386 and not all?).
> Everything is listed as binary-indep but should I also modify the configure
> line to remove --host, --build, CFLAGS and LDFLAGS?

No, your package is currently arch independant because in
debian/control, you have "Architecture: all". The arch in .changes is
the arch used to compile the packages. Your .deb is:
vbackup_0.1.6.1-1_all.deb

> The latest version (-2) is available in mentors.

I wait for you to add back lines about putting a more up-to-date
config.sub and config.guess. They are not outdated right now but they
could be in some distant future.
--
printk("Illegal format on cdrom. Pester manufacturer.\n");
2.2.16 /usr/src/linux/fs/isofs/inode.c

attachment0 (202 bytes) Download Attachment

ITP dhcp_probe - Discover rogue DHCP-servers on your lan

2008-09-05T12:34:14Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: wnpp
Severity: wishlist

Debian Bug report logs - #495959

* Package name : dhcp_probe
Version : 1.2.1
Upstream Author : Irwin Tillman <networking@...>
* URL : http://www.net.princeton.edu/software/dhcp_probe/
* License : Main program has a custom BSD-like license, with
parts covered by GPL2.
Programming Lang: C
Description : Discover rogue DHCP-servers on your lan

dchp_probe attempts to discover DHCP and BootP servers on a
directly-attached Ethernet network. A network administrator can use
this tool to locate unauthorized DHCP and BootP servers.

(I'm not aware of any existing Debian package with that functionality).

I have already contact the upstream programmers and the maintainer of
libnet0 package (dependency of dhcp_probe).
To package dhcp_probe, i need to apply a patch t libnet0. So i am
blocked in my ITP by the ITA of David Paleino on the libnet0 package.

I'll read manuals about the BTS to make this situation up to date and I
surely need more links about the BTS handling in order to suite all
Debian rules.

Tanks for reading.
- --
Laurent Guignard, Registered as user #301590 with the Linux Counter 
Site : http://www.famille-guignard.org 
Blog : http://blog.famille-guignard.org 
Projet : http://sicontact.sourceforge.net 
GULL de Villefranche sur Saône : http://www.cagull.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIwYm2jcKpXFc/7oYRAikaAJ461f87W+RaeYFQJv0zn409faqDPACgwSbH
KtS1ydJ9/2VT8dzLKQc0VOQ=
=WlH5
-----END PGP SIGNATURE-----

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: copher

2008-09-05T11:25:32Z

On Fri, Sep 05, 2008 at 06:08:14PM +0100, Daniel Watkins wrote:
> http://sf.net is expanded to the full SF URL by tools that use watch
> files and, I presume, will be updated if SF ever changes its URL schema.

Ah, that makes more sense, thanks.

--
Jonathan Wiltshire

signature.asc (204 bytes) Download Attachment

Re: RFS: copher

2008-09-05T10:08:14Z

On Fri, 5 Sep 2008 15:32:33 +0100
Jonathan Wiltshire <debian@...> wrote:
> > debian/watch:
> > > http://qa.debian.org/watch/sf.php/copher copher-(.*).tar.gz debian
> > Did you know that the first part can be written as
> > http://sf.net/copher ?
>
> I get a 404. I was under the impression that the URL I have used was
> required to allow for SF's load-balancing redirections.
http://sf.net is expanded to the full SF URL by tools that use watch
files and, I presume, will be updated if SF ever changes its URL schema.

--
Daniel Watkins (Odd_Bloke)

signature.asc (204 bytes) Download Attachment

RFS: assogiate

2008-09-05T08:54:52Z

Dear mentors,

I am looking for a sponsor for my package "assogiate".

* Package name : assogiate
Version : 0.2.1-1
Upstream Author : Kevin Daughtridge <kevin@...>
* URL : http://www.kdau.com/projects/assogiate/
* License : GPL
Section : utils

It builds these binary packages:
assogiate - editor of the MIME file types database

The package appears to be lintian clean.

The upload would fix these bugs: 434794

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/a/assogiate
- Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/a/assogiate/assogiate_0.2.1-1.dsc

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

Kind regards
Vincent Legout

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: Need help writing watch file for unusual, troublesome case.

2008-09-05T08:51:00Z

Am Dienstag, den 02.09.2008, 16:31 -0700 schrieb Brandon:
> Creating a separate script wouldn't really make much sense in my case.
> I was only fixing the watch file as a formality. Upstream is dead, so I
> wouldn't be using it, but it would satisfy projects like dehs, and my
> QA page warns me about my broken watch file.
>
> I think I will just use the watch file that I mentioned in my original
> post. This one:
> version=3
> http://www.xevil.com/xevil/dev/download.html (.*)/download_stable.shtml

This is a good starting point. Using filenamemangle and
downloadurlmangle you can use the above for a working watch file. I
attached it. As long as upstreams stays with this scheme (besides it is
a dead project), this should work.

Regards, Daniel

watch (268 bytes) Download Attachment

RFS: sitebar (updated package)

2008-09-05T07:55:40Z

Dear mentors,

I am looking for a sponsor for the new version 3.3.9-2
of my package "sitebar".

It builds these binary packages:
sitebar - web based bookmark manager written in PHP

The package appears to be lintian clean.

The upload would fix these bugs: 483011

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/s/sitebar
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget http://mentors.debian.net/debian/pool/main/s/sitebar/sitebar_3.3.9-2.dsc

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

Kind regards

--
Carlos Eduardo Sotelo Pinto ( KrLoS )
Free and OpenSource Software Developer
GNULinux Registered User #379182
GNULinux Registered Machine #277661
GNULinux Arequipa Users Group||Debian Arequipa Users Group
--
pgp.rediris.es 0xF8554F6B
GPG FP:697E FAB8 8E83 1D60 BBFB 2264 9E3D 5761 F855 4F6B

--
To UNSUBSCRIBE, email to debian-mentors-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

Re: RFS: copher

2008-09-05T07:31:07Z

On Mon, Sep 01, 2008 at 07:33:44PM -0500, Raphael Geissert wrote:
>
> Makefile:
> This file is useless, you don't need it, you should drop it.

Removed, all the logic is moved to debian/rules

> debian/watch:
> > http://qa.debian.org/watch/sf.php/copher copher-(.*).tar.gz debian
> Did you know that the first part can be written as http://sf.net/copher ?

I get a 404. I was under the impression that the URL I have used was
required to allow for SF's load-balancing redirections.

> Also note that the unquoted dots after the closing parenthesis is actually
> interpreted as part of the regex and could actually match anything?

Fixed.

> debian/control:
> > Priority: extra
> why?

http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html states:
"Extra: packages that either conflict with others with higher
priorities, are only likely to be useful if you already know what they
are [...]"

Perhaps I'm being a newbie, but this sounds a good fit. One would
probably already know of copher if one was going to use it; should it
be in Optional instead?

> > Architecture: any
> > Depends: libwww-mechanize-perl, ${shlibs:Depends}
> The perl script is architecture-dependent, isn't it?

Set architecture to 'all', removed shlibs placeholder.

> > Copher makes a SourceForge release automatically. It is useful as part
> > of a build and release system.
>
> This doesn't really tell me much about Copher; I am the admin of a project
> at sf.net and that description doesn't tell me it could be useful to me.
>
> > of a build and release system. Support for other GForge-based sites is
> > in development.
>
> SF.net is not 'GForge-based', that sentence should be rephrased.

This originally came from the RFP; I have rewritten it into something
more useful.

> debian/copher.1:

Same here, and removed the manpage boilerplate that I overlooked.

> debian/rules:
> debian/compat:
> debian/control:
> You build-depend on debhelper 7 but use none of its features? you
> should/could use a lower compat level such as 5 instead.

Set to 5. Is there anywhere that details the feature in each
compatibility level for future reference?

> debian/dirs:
> file is useless, remove it
>
> $ xlintian -I -E copher*changes
> W: copher: extra-license-file usr/share/doc/copher/COPYING.gz
> I: copher: package-contains-empty-directory usr/sbin/

Gone.

The updated package can be found at:
http://mentors.debian.net/debian/pool/main/c/copher

Thanks for your time and feedbacki.

--
Jonathan Wiltshire

signature.asc (204 bytes) Download Attachment