Bug#718323: another hyperrogue suggestion from debian reviewers

[Damyan Ivanov]

-=| Damyan Ivanov, 25.11.2013 13:34:43 +0200 |=-
> I think I addressed all my points. The result is in pkg-games 
> Git[1]. I hope my contributions are not too invasive.
> 
> [1] http://anonscm.debian.org/gitweb/?p=pkg-games/hyperrogue.git
> 
> If the changes look alright to you, I'll upload soon.

Upload done. So far so good.


signature.asc
Description: Digital signature

Bug#718323: another hyperrogue suggestion from debian reviewers

[Damyan Ivanov]

-=| chrysn, 23.11.2013 16:48:55 +0100 |=-
> On Sat, Nov 23, 2013 at 05:22:29PM +0200, Damyan Ivanov wrote:
> > I intent to work on all the points and eventually upload the 
> > package, if that's alright with you. (I am already member of 
> > pkg-games, cc-ed).
> 
> if you find the time before i do, i'd of course appreciate contributions
> to the package source in the team repo and it being uploaded!

I think I addressed all my points. The result is in pkg-games Git[1]. 
I hope my contributions are not too invasive.

[1] http://anonscm.debian.org/gitweb/?p=pkg-games/hyperrogue.git

If the changes look alright to you, I'll upload soon.

I have only two wishes to upstream:

 * lower CPU consumption
   It seems the game redraws as often as it can, resulting in fps from 
   60 to well over 100 when the window size is reduced. This is an 
   overkill and a great laptop battery drainer
   The same can be observed with the android version (albeit with fps 
   about 20, which is still too often, as the only moving things are 
   the treasures, which could be redrawn more seldom, I think)

 * parallel build
   it is a small issue, but when the source has to be rebuilt numerous 
   times (is when working on the packaging), employing all of the 
   available CPUs would help.
   I tried to produce a patch to implement this, but the changes 
   looked quite invasive, so I'll leave this to Zeno.


Cheers,
dam


signature.asc
Description: Digital signature

Bug#718323: another hyperrogue suggestion from debian reviewers

[Damyan Ivanov]

Hi,

I am joining late, but I just found this bug, while considering 
packaging hyper rogue myself :)

-=| chrysn, 06.08.2013 21:27:17 +0200 |=-
> i therefore still think that the package is suitable for debian from 
> my point of view.

I am impressed by the state of the packaging, very good work, thanks 
to everyone involved!

I've found only a couple of small glitches:

 * there is a new upstream release, featuring freely-licensed music. 
   How about upgrading the package?
 * the debian/watch file is fooled by the different variants published 
   upstream:

   -- Found the following matching hrefs:
hyperrogue-40t.zip (4.0t)
hyperrogue-40t.zip (4.0t)
hyperrogue-40-nomusic.zip (4.0-nomusic)
hyperrogue-40-macos-i386.zip (4.0-macos-i386)
hyperrogue-40t-macos-i386-music.zip (4.0t-macos-i386-music)
   Newest version on remote site is 4.0-nomusic, local version is 3.8+dfsg
(mangled local version number 3.8)

 * the repackaging is documented, but not automated.

I intent to work on all the points and eventually upload the package, 
if that's alright with you. (I am already member of pkg-games, cc-ed).


Cheers,
dam


signature.asc
Description: Digital signature

[uploaded] timelimit (updated package)

[Damyan Ivanov]

-=| Peter Pentchev, Tue, Apr 14, 2009 at 03:50:19PM +0300 |=-
> 
> I am looking for a sponsor for the new version 1.4-2
> of my package "timelimit" which builds a single binary package:
> 
> timelimit  - Simple utility to limit a process's absolute execution time

Uploaded. Thanks for your work.

-- 
damJabberID: d...@jabber.minus273.org


signature.asc
Description: Digital signature

Re: RFS: libnet-nis-perl

[Damyan Ivanov]

-=| Hendrik Frenzel, Wed, Mar 12, 2008 at 06:48:53PM +0100 |=-
> Dear mentors,

There's no much point in seeking sponsors in debian-mentors, when the
package has Debian Perl Group as Maintainer, I think :)

> I am looking for a sponsor for my package "libnet-nis-perl".
> The package can be found on mentors.debian.net:

... and svn+ssh://svn.debian.org/svn/pkg-perl/trunk/libnet-nis-perl :)

I've taken a look and here are some notes:

* debian/copyright

 + there is dh-make-perl boilerplate about copyright info being
   automatically extracted. remove it.
 + author and licensing information are intermixed
   separate AUTHORS, COPYRIGHT and LICENSE sections ease the reading
 + once license is "same as Perl", then there is
This program is free software; you can redistribute it and/or modify
it under the terms of either:

 a) the GNU General Public License as published by...
   the later are Perl licensing terms, yes, but it would be better to
   say "Perl is licensed under the following terms" somewhere.

* debian/rules
  + dh_installexamples is unused
  + install is missing in .PHONY

* debhelper
  + consider if DH compat level 6 could be used

* debian/control
  + Dm-Upload-Allowed: yes
I personally have no observation of your work so I can't upload this
with DM-U-A:yes
I also believe that you don't actually need that flag, as uploads
are rather quick within the group. The "Ready for upload" queue at
http://pkg-perl.alioth.debian.org/cgi-bin/qareport.cgi is usualy
flushed daily.


Thank you for your work so far.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: RFS: libtie-cache-perl (updated package)

[Damyan Ivanov]

-=| Deepak Tripathi, Sat, Mar 01, 2008 at 09:07:15PM +0530 |=-
> Dear mentors,
> 
> I am looking for a sponsor for the new version 0.17-4
> of my package "libtie-cache-perl".

Deepak,

You're a member of pkg-perl Is there any particular reason not to add
libtie-cache-perl to group's packages and co-maintain it?

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: RFS: QA Upload: libpalm-perl - Perl 5 modules for manipulating pdb and prc database files

[Damyan Ivanov]

-=| Frank Lichtenheld, Thu, Feb 28, 2008 at 09:58:50PM +0100 |=-
> On Thu, Feb 28, 2008 at 10:17:31AM -0500, Barry deFreese wrote:
> > Frank Lichtenheld wrote:
> > >The whole OPTIMIZE stuff seems unneccessary, since this is an Arch: all
> > >package.
> > I thought so too but it's on the policy page.  Should I go ahead and 
> > remove it anyway?

Which policy is that? It needs a bug report if it requires OPTIMIZE for
arch:all packages.

> The policy example doesn't handle noopt correctly and you corrected
> that. So you too seem to think that the policy is not everything ;)
> 
> Creating completly unused code just for the sake of it is never a good
> idea in my book. I would still advide to remove it.
> 
> Does anyone on debian-perl disagree?

I routinely remove unneeded OPTIMIZE setting.

I can't tell I am stripping *all* of the redundant bits of the
packaging, but since OPTIMIZE is so clearly unneeded and so easy to
spot, it is an easy target.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: RFS: timelimit (updated, add Conflicts)

[Damyan Ivanov]

-=| Peter Pentchev, Sun, Dec 23, 2007 at 04:04:22AM +0200 |=-
> I am looking for a sponsor for the new version 1.1-2 of my
> package "timelimit".  The new revision adds a conflict with
> the "netpipes" package since both install /usr/bin/timelimit.
> 
> The upload would fix these bugs: 457444
> 
> The package can be found on mentors.debian.net:
> http://mentors.debian.net/debian/pool/main/t/timelimit/timelimit_1.1-2.dsc

I'll take care of this.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: Digital signature

Re: lintian .packlist warning and debian/rules modification

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Jeremiah Foster,  9.09.2007 20:40 |=-
> E: libhtml-treebuilder-xpath-perl: package-installs-packlist
> usr/lib/perl5/auto/HTML/TreeBuilder/XPath/.packlist
> N:
> N:   Packages built using the perl MakeMaker package will have a file named
> N:   .packlist in them. Those files are useless, and (in some cases) have
> N:   the additional problem of creating an architecture-specific directory
> N:   name in an architecture-independent package.
> N:
> N:   They can be suppressed by adding the following to debian/rules:
> N:
> N:   find debian/tmp -type f -name .packlist | xargs rm -f
> N:
> N:   -find debian/tmp/usr/lib/perl5 -type d -empty | xargs rmdir -p
> N:
> N:   Or by telling MakeMaker to use vendor install dirs; consult a recent
> N:   version of perl policy. Perl 5.6.0-12 or higher supports this.
> 
> 
> Below is an example of the output I would receive:
> 
> 
> 
> find debian/tmp -type f -name .packlist | xargs -r rm -f
> find: debian/tmp: No such file or directory
> find debian/tmp -type d -empty | xargs -r rmdir -p
> find: debian/tmp: No such file or directory

Which means that the "debian/tmp" thing is wrong.

> What I did to finally get rid of this error was to change the command to
> this:
> 
> # remove .packlist files inserted by MakeMaker
> find . -type f -name .packlist | xargs -r rm -f
> 
> I then placed the changed code (the line above with my comment) in the
> install section of the debian/rules file and the lintian error went
> away! I hope this helps some one else.
> 
> If you think I was wrong to do it this way please inform me of the
> proper way to do it or any changes I should make.

Use the correct directory when "find ... -delete"-ing things. Look where
$(MAKE) install installs it. I guess this should be $(TMP)
- --
damJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG5DnuHqjlqpcl9jsRAl1IAKCaaGr58O6xDWzOtVN8FAU6F+gY6gCfb/O9
L5eOb2R+bmQP9EpZbNiWdXw=
=zOVR
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: libwhisker2-perl

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Deepak Tripathi,  4.08.2007 22:14 |=-
> Dear mentors,
> 
> I am looking for a sponsor for my package "libwhisker2-perl".
> 
>  Version : 2.4-1
>  Section : interpreters

Should section be "perl" instead?

> It builds these binary packages:
> libwhisker2-perl - Perl module geared for HTTP testing

Is this the same package you imported into pkg-perl SVN repository? What
you imported is named "libwhisker-perl" so I am not sure. Please clarify.
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGtYghHqjlqpcl9jsRAtikAJ0cmEE6/UOU8UufME3icJW47oMaIACfZtNx
Aogcf5LfKF9Kn+Uddj6j/tY=
=I1Jz
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Sponsorship guidelines for codehelp - now online.

[Damyan Ivanov]

-=| Neil Williams, 24.07.2007 17:32 |=-
> http://people.debian.org/~codehelp/#sponsor

Content seems to be missing?

-- 
damJabberID: [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: ITS: vegastrike, vegastrike-data and vegastrike-music (updated packages)

[Damyan Ivanov]

-=| Gerfried Fuchs, 18.07.2007 12:36 |=-
> On Tue, Jul 17, 2007 at 12:08:20PM -0400, Andres Mejia wrote:
>> I'll fix the tar in tar solution. The problem will be with
>> vegastrike-data. I'm trying to get rid of all the warnings and one
>> error. Fixing the warnings consist of uploading a new orig tarball.
> 
>  You should never ever change the upstream tarball except in cases where
> you want to remove non-DFSG stuff from it to make the package be allowed
> into main.  I don't of any other reason to change the upstream tarball.
> If you do, please elaborate.

Just for completeness: I repackage firebird2.0 because upstream includes
a complete copy of libicu in the tarball. Removing this drops the source
package size from 16 to 6.6MB (actually, upstream distributes tar.bz2
which is 12MB). I guess this falls under the "significant space savings"
hypothesis in DevRef §6.7.8.2

-- 
damJabberID: [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: Change in my sponsorship requirements

[Damyan Ivanov]

-=| Charlie, 17.07.2007 09:45 |=-
> I have a  problem that I'm not sure
> how to fix.   The package I have in NEW is 3.3.3.2-1 I had to remove
> some window support files (.dll and .exe) from the orig.tar.gz and
> reading through the debian manuals I noticed that the package should
> have been 3.3.3.2-dfsg-1.  I have placed a list of all the files
> removed in README.Debian.  Should I package it as 3.3.3.2-dfsg-1 or
> 3.3.3.2.dfsg-2 since this is actually the second debian version?

I'd use 3.3.3.2.dfsg1-1

Deciphered, this is
- upstream 3.3.3.2
- cleaned to comply with dfsg, first take
-- above identify the orig.tar.gz
- first debian revision using _that_ orig.tar.gz

Is the DFSG the reason for that repackaging[1]? If not, you should use
"ds" (as in Debian Source) instead of "dfsg". You may want to consult
the DevRef 6.7.8.2 to make sure that a re-packaging is really needed.

BTW, there is newer upstream version :)


[1] The .dll and .exe files are unneeded, yes, but unless they clash
with DFSG you can leave them (explaining their origin/authors/license
in debian/copyright)
-- 
damJabberID: [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: RFS: libsbc (updated package)

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

[Any reason to keep dropping the mailing list?]

- -=| Krzysztof Burghardt, 16.07.2007 18:24 |=-
> 2007/7/16, Damyan Ivanov <[EMAIL PROTECTED]>:
>> Please make the process of creating the .orig.tar.gz more obvious (and
>> reviewable). A readable shell script in debian/get-orig-source.sh
> 
> Is simple "cvs export ... && tar cfz" sufficient?
> Or do you have an example o such script?

cvs export would be sufficient if you add a date or tag option to it.
Otherwise the result depends on when you run the export.
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGnF97Hqjlqpcl9jsRAsT5AKDIfBzLVb+2HRJJjuoRXWLEUPzJWwCdHzRl
yxw2dpnrVh1q3CqPc1rk59Y=
=EvsO
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Change in my sponsorship requirements

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Charlie, 17.07.2007 00:04 |=-
> Ondrej Certik wrote:
>> uploads it to the NEW queue with a version 0.6.0-1, but it waits there
>> for a month, but I need updates of my package now, so I create
>> versions 0.6.0-1oc1, 0.6.0-1oc2, ..., and when the package hits
>> unstable, I just create a new changelog entry 0.6.0-2 and ask the
>> sponsor for upload.

> As a non DD I believe this is what I will start doing.  As my package
> sets in NEW I have accumulate several bug fixes from upstream (which
> were gathered independent of BTS), not to mention a few minor
> packaging mistakes that I have made and my DD sponsor did not catch
> (typo's mainly) this way I can stay on top of things and I don't miss
> anything while the package sets in NEW.  Thanks for the idea

Ondrej, Charlie,

You can also ask for sponsor for -2, even while -1 is in NEW. This won't
"disturb" the package for sure. The first version in unstable would
simply be -2. For example, see console-setup having two versions in NEW[1].

[1] http://ftp-master.debian.org/new.html

This feature is especially useful when you find serious problems with -1
that could make it rejected.
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGnEaHHqjlqpcl9jsRArs0AKCfjl2HRoJaqBGxcTXKW8rtYcBI7wCfUZkw
DHrUp/uaHtfZj7n7bB7E+GI=
=eeZi
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: libsbc (updated package)

[Damyan Ivanov]

-=| Krzysztof Burghardt, 16.07.2007 16:37 |=-
> 2007/7/16, Damyan Ivanov <[EMAIL PROTECTED]>:
>> I wonder how these tiny changes result in growing the .diff.gz from
>> 2.4K to 230K :)  Was this intentional?
> 
> It wasn't. Sorry. It seems generated files like Makefile.in got into diff.

Yep!

> I will upload fixed version and ask you to re-review, ok?

I may want to post to the list to avoid depending on me :)


May I ask for a couple of wishes while you're there?

Please make the process of creating the .orig.tar.gz more obvious (and
reviewable). A readable shell script in debian/get-orig-source.sh
would be ideal. It wouldn't create an .orig.tar.gz that is
binary-equal to the one already in Debian, but it still can be used by
reviewing people.

Please remove the autoconf-generated files in clean target. See
/usr/share/doc/autotools-dev/examples/rules.gz for an example.
-- 
damJabberID: [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: RFS: libsbc (updated package)

[Damyan Ivanov]

-=| Krzysztof Burghardt, 16.07.2007 11:24 |=-
> 2007/7/14, Krzysztof Burghardt <[EMAIL PROTECTED]>:
>> I am looking for a sponsor for the new version 0.0cvs20070327-2
>> of my package "libsbc".
> 
> It has only 2 small changes to debian/rules and debian/control
> need to be lintian checklist compliant. Review will took 5 minutes :)

I wonder how these tiny changes result in growing the .diff.gz from
2.4K to 230K :)  Was this intentional?
-- 
damJabberID: [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: [RFS] Looking for a sponsor for David's libsvg-perl.

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Charles Plessy, 14.07.2007 14:15 |=-
> In the meantime, the discussion continued in the BTS where I got an
> answer and was informed that Jose made a package which will be uploaded
> this week-end.
> 
> How does it work with the NEW queue, will the latest upload override the
> previous ?

If the version number is bigger - yes. I am not sure whether it is
required for the Maintainer: field to be the same. I guess not.

David, Jose, since it appears you both are interested in maintaining
that package, I very much hope that you end up co-maintaining it :)

Please do not take my upload as an act of preference of one's package
over the other's. It was Charles' polite asking that make me consider it
for upload.
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGmv3lHqjlqpcl9jsRAjVGAKCMSTjFTK+0TD6DNUBpvFyWeBdOBQCcDNiI
cUr9TYNSz5RUUW5xHM5HU0s=
=LytU
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [RFS] Looking for a sponsor for David's libsvg-perl.

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Charles Plessy, 12.07.2007 04:57 |=-
> Here is the link to the package:
> 
> http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=libsvg-perl
> http://mentors.debian.net/debian/pool/main/l/libsvg-perl/libsvg-perl_2.33-1.dsc

Uploaded.

There is a lintian warning that would be nice to have fixed for the next
revision.

Please sent the manpage fixes upstream if you haven't already.
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGmIdiHqjlqpcl9jsRAgOAAKCXhZyRrecIxOVqur2jtSRxpFDsAQCeI07g
rxJFKg1uoSIPyfwfNCVlUbg=
=Gzah
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: Spout, a tiny but wonderful black and white game (ITP with Bug#356492)

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Javier Candeira, 12.07.2007 11:45 |=-
> http://mentors.debian.net/debian/pool/main/s/spout

O, the package looks as ready to me, only two small glitches remain that
I forgot to mention in the previous mail.

Sinte the source is re-packaged, two additional things are needed.

First, the version number should indicate that there was a repackaging.
  1.1a.ds1 should do it
("ds" meaning "debian source")

Second, an additional file in debian/ - README.Debian-source should
explain why the repackaging was done. That file should be installed in
usr/share/doc/spout  See Developer Reference 6.7.8.2 for details and
nice ideas for constructing "proper" tarball.

I guess these are the final nitpicks from my side.

I have a slight concern about this part of your mail:

> Ok, I will do that, though I am ready to bet that the only changes upstream
> will ever make to this game will be to add my licensing wordings, if that.

Packaging something that is not actively developed may pose more burden
on your side (fixing bugs, etc), but since you're the maintainer, that
is your decision to make :)

- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGl5m9Hqjlqpcl9jsRAkOZAJ9Hlh1GqUK4r3YUjzn7giK9Q/ksMwCfaM1w
XD0PI0bUQgZTyxHjqisTJ+Y=
=syfp
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: Spout, a tiny but wonderful black and white game (ITP with Bug#356492)

[Damyan Ivanov]

-=| Javier Candeira, Wed, 11 Jul 2007 15:37:08 +1000 |=-
> Damyan, Thanks so much for answering, and thanks especially for
> agreeing to work with me on the package.

"Work" is a bit strong :) I'll just review/upload. You are supposed to
do the "work" :)

> Here are my answers to your requests. I have taken some time in
> replying to your email because I wanted to finish everything first.

This is fine.

> Upstream is very loose on licensing. His 1.1 release had no license
> whatsoever, and I had to ask him to put a license in the code. He
> finally put the MIT license in license.txt in the file and changed
> version to 1.1a.
> 
> I could hound him to put the header in every source file, I suppose,
> but I have the email exchange proving that he really meant to license
> the game this way. I hope this is enough.

It could be if you put it in debian/copyright, preferably as a
temporary solution. You could prepare the necessary changes and send
them upstream (in form he prefers) so they can be included in the next
upstream release.

> > The game writes its HiScores file (spout.sco) in the current working
> > directory. Can you make it use /var/games for that? Or at least
> > ~/.spout.sco?
> 
> Tried to, but I can't make it work. For some reason, spout gets
> installed with user:group root:root instead of root:games. Is that
> something I am doing wrong?

Try setting the wanted permissions right after dh_fixperms invocation.
Or see the -X option for dh_fixperms.

> [Basically every my concern addressed]

Thank you for your work so far.

Finally, please make the source package available somewhere. I had to
search the list archives to find the location for the last package and
it appears it is still not updated. http://mentors.debian.net is often
used these days (and gives you some "uploading" experience).
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: Spout, a tiny but wonderful black and white game (ITP with Bug#356492)

[Damyan Ivanov]

-=| Javier Candeira, Thu, 05 Jul 2007 15:31:00 +1000 |=-
> * Package name: Spout
>   Version : 1.1a-1
>   Upstream Author : Kumi
> * URL : http://www.din.or.jp/~ku_/junk/spout11a.zip
> * License : MIT
>   Section : games
> 
> * Browse   : http://rowrcolo.net/~kandinski/packages/spout/
>   and you'll find :
>   http://rowrcolo.net/~kandinski/packages/spout/spout_1.1a-1.diff.gz
>   http://rowrcolo.net/~kandinski/packages/spout/spout_1.1a-1.dsc
>   http://rowrcolo.net/~kandinski/packages/spout/spout_1.1a.orig.tar.gz
> 
> Uploading this package will close bug 356492. It is policy-compliant
> and   

Hello, Javier,

I am wiling to sponsor this game, but there are some problems (for me;
others may not share this):

debian/copyright - missing year(s) of copyright

Also, there is SDL/license.txt in the source, but it is not obvious
what is the license of the files outside the SDL directory. You
should check this with upstream. Ideally, every source file should have
a license block in the beginning.

Hm. As far as I see, everything that is needed for the "make" run is in
SDL. So it may be best to omit everything outside SDL out of
the .orig.tar.gz.

Since you're re-packaging (zip -> tar.gz), you may want to remove some
cruft like SDL.dll and Spout.exe from the source archive.

To make this easily reviewable and maintainable, please provide
debian/get-orig-source.sh that automates the process (zip->unzip,
remove cruft->.orig.tar.gz)

Please provide debian/watch file. See uscan(1) for the format.

The .desktop file is invalid. Try desktop-file-validate from
desktop-file-utils package.

Install .desktop file with dh_desktop (in binary-arch target). It
install the .desktop file *and* calls update-desktop-database from the
maintainer scripts. See dh_desktop(1).

Please add debian/menu file. Note that section names are changed. See
recent announcement on debian-devel-announce and menufile(5) (be sure
to have at least version 2.1.35 of the "menu" package)

It would be nice if you can remove the lines from debian/rules that are
presently commented out and for which it is obvious that they'll never
be needed (example: dh_perl).

The game writes its HiScores file (spout.sco) in the current working
directory. Can you make it use /var/games for that? Or at least
~/.spout.sco?
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: codeblocks

[Damyan Ivanov]

-=| Erick Mattos, Sat, 23 Jun 2007 13:10:52 -0300 |=-
> http://mentors.debian.net/debian/pool/main/c/codeblocks/codeblocks_1.0rc2~svn.20070620-1.dsc

More comments, in several categories :)


Nitpicks:
 * debian/codeblocks.desktop contains "GenericName[en_GR]=".
   Can you either fill it or remove it?
 * There are some commented-out lines in debian/rules' binary-arch
   target that are clearly never going to be needed. Please remove them.
 * usr/sbin is not used so no need to put it in debian/dirs. If make
   install creates its directories (as it should), there is no need for
   usr/bin too, rendering debian/dirs redundant.
 * The debian/menu file has no icon assitoated. Note that it needs an
   icon in XPM format so you may need to convert the .png to .xpm

There is a great deal (>11M) of architecture-independent files installed
in /usr/share. Please consider putting them in a separate, Arcitecture:
all package (codeblocks-common) and make codeblocks depend on it. This
will save space on archive mirrors.
 

Shared libraries:
I see you've added postinst/postrm scripts calling ldconfig. I guess
this is because codeblocks installs libcodeblocks and libwxsmith in
/usr/lib.

Is this at all necessary? What is the purpose of these libraries? As
far as I see, libcodeblocks is used bu /usr/bin/codeblocks and
libwxsmith is unused.

Are these libraries to be used by someone else than codeblocks? If they
are for internal codeblocks (+ plugins) usage, they are better placed
in /usr/lib/codeblocks and codeblocks linked with
-rpath /usr/lib/codeblocks.


Development files:
Are the files in /usr/include/codevlocks needed for using Code::Blocks?
If not, for example if they are needed only when developing C::B
plugins, better place them in a separate (Architecture: all) package
(codeblocks-plugin-dev/codeblocks-dev), possibly recommending it in
codeblocks.


There still are some lintian warnings that should be fixed.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: codeblocks

[Damyan Ivanov]

Hi, Erick,

-=| Damyan Ivanov, Wed, 13 Jun 2007 14:04:50 +0300 |=-
> -=| Damyan Ivanov, Wed, 13 Jun 2007 13:57:17 +0300 |=-
> > Here's a non-exclusive list in no particular order (:
> 
> Additionally, the configure-stamp target in debian/rules misses "touch
> $@" at the enc, causing repetitive building.
"d"^

Last for today :) the resulting package gives several lintian warnings.
It would be nice if you can comment on them.
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: codeblocks

[Damyan Ivanov]

-=| Damyan Ivanov, Wed, 13 Jun 2007 13:57:17 +0300 |=-
> Here's a non-exclusive list in no particular order (:

Additionally, the configure-stamp target in debian/rules misses "touch
$@" at the enc, causing repetitive building.
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: codeblocks

[Damyan Ivanov]

-=| Erick Mattos, Tue, 12 Jun 2007 21:13:40 -0300 |=-
> * Package name: codeblocks
>   Version : 0.0.20070612-1
>   Upstream Author : Yiannis Mandravellos <[EMAIL PROTECTED]>
> * URL : http://www.codeblocks.org
> * License : GPL
>   Section : devel
> 
> It builds these binary packages:
> codeblocks - Code::Blocks integrated development environment (IDE)
> 
> http://mentors.debian.net/debian/pool/main/c/codeblocks/codeblocks_0.0.20070612-1.dsc

I am considering sponsoring this, but there are some issues.

Here's a non-exclusive list in no particular order (:

* debian/copyright states only one author. AUTHORS suggests there are
more, plus there are some unknown authors yet. Contact upstream for
clarification.

* debian/copyright misses the year(s) of copyright

* debian/copyright ends with 
  # Please also look if there are files or directories which have a
  # different copyright/license attached and list them here.

Did you do what's suggested there?

* since the source was exported from SVN, please document in
debian/copyright which revision was used for the export. A script
(debian/get-orig-source.sh) that generates .orig.tar.gz from given
revision would be nice too.

* debian/rules contains some code for generating revision.m4, but this
file is already shipped. Why not get rid of that code?

* debian/rules contains some commented-out lines in the binary-arch
target that clearly are not needed by this package. Please drop them.

* You provide menu file. Good. Please provide .desktop file too

* Version "0.0.20070612" seems wrong to me. Last thing upstream
released is 1.0 RC4. I'd use a version that is between "1.0 rc4" and
whatever the next planned release will be.

* The build fails, because ./configure is not executable

* debian/control - are *all* of these Build-Depends really necessary? I
didn't try dropping any of those, but the list looks very broad.

On the other hand, some Build-Dependencies are missing. Build
the package with pbuilder and see for yourself.


Thank you for your work so far.
Feel free to ask this list if you have trouble fixing any of the above.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: Sponsored: peless

[Damyan Ivanov]

-=| Giorgio Pioda, Mon, 11 Jun 2007 18:09:09 +0200 |=-
> > One way to fix this is indeed by adding --as-needed to LDFLAGS, but
> > --as-needed is really just a hack. The proper way is to reduce the
> > "-l" parameters to the linker to only those libraries that are used
> > directly by peless.
> 
> Fixed in upstream is better than in debian/rules  of course!

We'll see if Paulo can come with anything better than --as-needed. This
is not an easy task...

> Actually, about dependecies...
> 
> Compilig peless I noted that libgtkmm needs libcairomm internally but
> this dep. is not resolved in debian libgtkmm-dev (mentioning
> libgtkmm-dev doesn't automatically resolve for libcairomm-dev)
> package Should I make a bug report about this ?

If you can demonstrate why this is a bug, go ahead :)

libgtkmm depending on libcairomm does not necessarily mean that
libgtkmm's headers (-dev) depend on libcairomm's headers (-dev)

On the other hand, I bet that libgtkmm Build-Depends on
libcairomm-dev :)
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: Sponsored: peless

[Damyan Ivanov]

-=| Giorgio Pioda, Sun, 10 Jun 2007 16:30:51 +0200 |=-
> 
> I've prepared a new peless package downloadable at:
> 
> http://web.ticino.com/gfwp/debian/peless-1.145/peless_1.145-1.dsc
> 
> [...]
> Please take a look at, and, if good, upload it, THANKS!

Done.

Thank you for your contribution to Debian.
[not to mention your patience... :)]
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: About peless

[Damyan Ivanov]

[back to list, again]

-=| Giorgio Pioda, Sun, 03 Jun 2007 15:33:35 +0200 |=-
> I've cleaned up the peless package:
> 
> http://web.ticino.com/gfwp/debian/peless-1.125/peless_1.125-1.dsc
> 
> *generated from a tar.gz to have md5sums correspondence
> *watch file corrected and tested
> *changelog cleaned up (only 1 entry, initial release (Closes...)

Good. Thanks.

I have three more little things to mention :)

* The .desktop file is invalid, try checking it with
  desktop-file-validate. As a result, peless is nowhere in the gnome
menu. There is also two warnings

* The debian/copyright should point to
http://developer.berlios.de/project/showfiles.php?group_id=1681
as download location, since one currently used results in something
else being downloaded, perhaps some unreleased version.

* The debian/menu entry has no icon. Can you add one? Note that
menufiles use images in xpm format. It would be best if the .xpm is
generated in build time from .png to avoid mismatches if the icon
changes in the future.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: About md5sums of debian sources

[Damyan Ivanov]

-=| Giorgio Pioda, Sat, 02 Jun 2007 17:14:29 +0200 |=-
> If I try to recompress peless-1.125.tar.bz2 to peless-1.125.tar.gz (as
> suggested above) the md5sum changes, and doesn't correspond to md5sum
> of the peless_1.125.orig.tar.gz generated by uupdate. I actually get 3
> different md5sums!

But the md5sum of the uncompressed tarfile will remail the same.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: peless-1.125 repackaged

[Damyan Ivanov]

> http://web.ticino.com/gfwp/debian/peless-1.125/peless_1.125-1.dsc
> 
> I hope now it should be ok

Almost there :)

> P.S. the md5sum of orig.tar.gz and peless.tar.bz2 are obviously not
> the same, but uupdate repackages it automatically during upgrade. If
> this is an issue, the I'll upload a version created from scratch
> using only peless-1.125.tar.bz2.

What you should do in this case is to re-compress the tarfile with
something like "bzcat some.tar.bz2 | gzip -9 > some.tar.gz". This way
the tar itself will remain exactly the same. In any case, no need to
create anything from scratch!

> P.S. for Paul: please choose a tarball compression format anf keep it!
> (tar.gz or tar.bz2 but forever...) otherwise I have to correct the
> debian/watch file all the time.

You don't need to change debian/watch, just use (?:) for grouping
without capturing. See below.

Actually, debian/watch does not work. Here's what works for berlios
(and for both bz2 and gz):

opts=downloadurlmangle=s/prdownload/download/ \
  http://developer.berlios.de/project/showfiles.php?group_id=1681 \
  http://prdownload.berlios.de/peless/peless-(.*).tar.(?:gz|bz2)

I see you've abandoned all detailed changelog entries for 1.125-1.
Either
a) use only "initial release (closes #...)" for 1.125 and drop 1.108
or
b) add to 1.125-1 entry the changes made *in the packagig* since 1.108

I'd go with a)
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: peless-1.125-3 ready

[Damyan Ivanov]

[to the list, again]
-=| Giorgio Pioda, Tue, 29 May 2007 11:06:32 +0200 |=-
> Damyan Ivanov ha scritto:
> > While there, is there a need for that *three* changelog entries for
> > 1.125-x?
> > 
> > Why not simply change the version of the 1.108-1 entry and leave it
> > as is, i.e. simply "initial release". Your package didn't hit
> > Debian yet, so no need to explain the changes.
> 
> You are right. Explanations are not needed, but I used uupdate and
> then I have seen a couple of issues and corrected them repackaging
> and using dch -i. I was a little bored of regenerating all the times
> the debian tree with dh_make and copiing the needed files manually.

dh_make is to be run only *once* - when creating the package skeleton.
Use uupdate when there is new upstream release, followed by
'dch' (without -i) documenting changes done to the packaging. After the
package is uploaded, use 'dch -i' *once* to start new changelog entry.

> >  * I am uncertain, but aren't the checks for BOOST redundant as you
> > have Build-Depends: libboost-regex-dev? I have no strong opinion
> > about this, just wondering.
> 
> Well, just to make it portable on etch is necessary! I can kick out

Then write a comment in debian/rules what has to be changed for the
etch backport.

> this check but then I have to set a static liboost-regex-option=mt
> (otherwise the package doesn't compile) and the source is not
> compilable on etch (where libboost-regex-option='' is needed)... Tell
> me what's your preference. I think, personally, that beiing etch
> "young" we have to make the backport possible.

My preference is that ./configure handles all this stuff, but maybe I
am just daydreaming.
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: peless-1.125-3 ready

[Damyan Ivanov]

-=| Giorgio Pioda, Mon, 28 May 2007 09:52:29 +0200 |=-
> Hi Damyan and Paul
> 
> I've an updated package of peless:
> 
> http://web.ticino.com/gfwp/debian/peless-1.125/peless_1.125-3.dsc
> 
> Please take a look at! The rules still needs some tweaking for boost
> (even more than in the previous 1.108), but now is OK.

Still no dice :/

 * peless_1.125.orig.tar.gz is not *exactly* the same as on upstream
site:

$ md5sum peless_1.125.orig.tar.gz 
150fdd1ae86c01485440397dc0a754ac  peless_1.125.orig.tar.gz

$ md5sum /tmp/peless-1.125.tar.bz2 
4f347a3adaabc89759300cbac241210a  /tmp/peless-1.125.tar.bz2

I downloaded the second one from berlios.de. Did you re-package the
orig.tar.gz? This was not the case with 1.108. Is there real need for
re-packaging?


 * The changelog entries for 1.125 are from "Giorgio Pioda
<[EMAIL PROTECTED]>" - this must match exactly the Maintainer: field
in debian/control. Did you check the package with lintian?

While there, is there a need for that *three* changelog entries for
1.125-x?

Why not simply change the version of the 1.108-1 entry and leave it as
is, i.e. simply "initial release". Your package didn't hit Debian yet,
so no need to explain the changes.

There are exceptions, of course - if you have large number of
installations you want to upgrade or prefer to document the changes for
yourself. In this case please at least merge the three 1.125 entries
into one. I can't believe you've grown large user-base in 30 minutes :)

 * debian/copyright - can you change the download URL to the
distribution-neutral one? Same for debian/watch.


 * I am uncertain, but aren't the checks for BOOST redundant as you have
Build-Depends: libboost-regex-dev? I have no strong opinion about this,
just wondering.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: peless -- dh_helper

[Damyan Ivanov]

-=| Giorgio Pioda, Fri, 25 May 2007 21:29:40 +0200 |=-
> http://web.ticino.com/gfwp/debian/peless-1.108/peless_1.108-1.dsc

Ouch. It seems I've missed something in my previous review :/

In debian/copyright it is written that peless is under GPLv2-or-later
and this is in COPYING as well.

However, gmore.cc, peless.cc, internat.hh, search.cc and search.hh
state something different in their headers.

This is something that has to be sorted out with upstream author
(Hi, Paul :)  ) Ah, and while there, can I gen distribution-neutral
location for the source tarball? Just a wish, but I hope it would not
be a problem.

The copyright year is also different.

And something from before:

* debian/rules still contains commented rows that are never going to be
enabled. Why keep them there?
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: peless -- dh_helper

[Damyan Ivanov]

-=| Paul Elliott, Fri, 25 May 2007 11:32:02 -0500 |=-
> OK, but first let me understand what I am fixing. What is wrong
> with "make install" as it is? There is also a "make install-strip".
> I did not do anything special to create these targets; auto* tools
> created them. What exactly is wrong with "make install"? Thank you.

As far as I understand, Giorgio's concerns were that a plain "make
install" strips the debug information from the binaries installed.

However, I can't confirm this:
$ file debian/peless/usr/bin/peless 
debian/peless/usr/bin/peless: ELF 64-bit LSB executable, x86-64,
version 1 (SYSV), for GNU/Linux 2.6.1, dynamically linked (uses shared
libs), not stripped

(this is after changing debian/rules to use "make install" and break
right after it)

So, Giorgio, it seems perfectly safe to use "make install", no?
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: Fix a bug located in a dependency

[Damyan Ivanov]

-=| Mike Hommey, Fri, 25 May 2007 08:12:15 +0200 |=-
> On Thu, May 24, 2007 at 11:41:49PM +0300, Damyan Ivanov
> <[EMAIL PROTECTED]> wrote:
> > -=| Mike Hommey, Thu, 24 May 2007 19:39:20 +0200 |=-
> > > A standard example of this are bugs in applications that are due
> > > to bugs in libraries they depend on. Users would report bugs on
> > > the application, but it would be reassigned to the library. Next
> > > users reporting the bug would not see it in the list of bugs for
> > > the application with reportbug.
> > 
> > How about cloning the bug, reassigning the clone to the library and
> > making the "original" bug be blocked by the clone?
> 
> Sadly, the block stuff doesn't even notify the blocked bug when the
> blocker bug is closed...

This is #323663, I guess.

Is the other solution (proposed by Don) - reassign #n A,B going to
work in your case?
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: peless -- GTK Text browser

[Damyan Ivanov]

-=| Giorgio Pioda, Fri, 25 May 2007 07:17:11 +0200 |=-
> But why the dpkg-buildpackage command doesn't wrap automatically .dsc

It should, unless given '-us' or '-uc' options.

> and .cheanges? Do I have to activate specific options? Actually my gpg
> key is set and dpkg is not complaining for a missing gpg-key (actually
> when I try to compile on machines where my gpg key is not present dpkg
> complains...)

You can add it semi-manually with "debsign /path/to/package.changes"
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: peless -- GTK Text browser

[Damyan Ivanov]

[added the list again]
-=| Giorgio Pioda, Thu, 24 May 2007 21:11:19 +0200 |=-
> > If I were you, I'd try to make "make install" not strip anything,
> > patching if necessary[1]. The problem with dh_install approach is
> > that you have to check carefully if there is something new to
> > install every now and then, which leads to problems (as already
> > seen).
> > 
> The world is nice because it is possible to find many different
> opinions...

I see your confusion and I understand it. It is not so good feeling to
try to satisfy contradicting requirements.

I, personally, will not sponsor a package that replaces a perfectly
working "make install" with broken dh_install usage. Even if
dh_install usage is fixed, I still don't like it. This, of course, does
not mean that nobody else will want to sponsor it.

About the signing. the .dsc file is (wrapped):
--
Format: 1.0
Source: peless
Binary: peless
[...]
Files:
c56508f8e052b10cd799c8e0a9253909 109646 peless_1.108.orig.tar.gz
ccdc4f9b61f88c324acbd707f03cb5d2 2659 peless_1.108-1.diff.gz
--

Compare this to (a random example)
ftp://ftp.debian.org/debian/pool/main/g/glibc/glibc_2.3.6.ds1-13.dsc

Without a proper signature[1], how can I be sure that the .dsc file I am
downloading is the same you created?
-- 
damJabberID: [EMAIL PROTECTED]

[1] missing trust-path aside


signature.asc
Description: PGP signature

Re: Fix a bug located in a dependency

[Damyan Ivanov]

-=| Mike Hommey, Thu, 24 May 2007 19:39:20 +0200 |=-
> A standard example of this are bugs in applications that are due to
> bugs in libraries they depend on. Users would report bugs on the
> application, but it would be reassigned to the library. Next users
> reporting the bug would not see it in the list of bugs for the
> application with reportbug.

How about cloning the bug, reassigning the clone to the library and
making the "original" bug be blocked by the clone?

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: peless -- GTK Text browser

[Damyan Ivanov]

-=| Giorgio Pioda, Thu, 24 May 2007 11:33:09 +0200 |=-
> Hi Damyan and Paul
> Damyan Ivanov ha scritto:
> > Good. Giorgio, since you don't use "make install", this file does
> > not get installed. Is there a reason to prefer debian/install over
> > "make install"? Either way, please include the .desktop file in the
> > final .deb
> 
> The reason is the 10.1 policy; I tried to set up nostrip versions for
> debugging with the original "make install" but it doesn't work
> properly so I switched to dh_istall and dh_strip.

Hm. 10.1 contains only recommendations about the mater. Following
them is no excuse for breaking other things ;-)

If I were you, I'd try to make "make install" not strip anything,
patching if necessary[1]. The problem with dh_install approach is that
you have to check carefully if there is something new to install every
now and then, which leads to problems (as already seen).

-- 
damJabberID: [EMAIL PROTECTED]

[1] The smoothest approach is to make stripping in "make install"
optional, defaulting to "do strip". This way, simple "make install"
works as before, but when given special option (or environment
variable) it does not strip. This patch would be easier to push
upstream.


signature.asc
Description: PGP signature

Re: RFS: peless -- GTK Text browser

[Damyan Ivanov]

[Added debiam-mentors and dropped Thomas from CC]

-=| Paul Elliott, Thu, 24 May 2007 00:29:35 -0500 |=-
> On Wed, May 23, 2007 at 12:08:16AM +0300, Damyan Ivanov wrote:
> > -=| Giorgio Pioda, Tue, 22 May 2007 21:51:48 +0200 |=-
> > > I have packaged a nice GTK text reader that can be very usefull to
> > > compare files (shown in separated tabs), and search for text in
> > > files. The package seems to me quite mature and is downloadable
> > > at:
> > > http://web.ticino.com/gfwp/debian/peless-1.108/peless_1.108-1.dsc
> 
> Gentlemen, do any of these questions/issues, require that I do
> anything to the upstream source? Is there anything I need to do?

I think not. Perhaps the only wish of mine is to publish the source in
the berlios download area.

> > * A .desktop file would be nice
> I think there is one. look in /usr/local/share/applications after a
> "make install".

Good. Giorgio, since you don't use "make install", this file does not
get installed. Is there a reason to prefer debian/install over "make
install"? Either way, please include the .desktop file in the final .deb

> A developer would know that these are not
> relevant if not  working with that distro.

Sure. I am confused not by the contents of the file, but by its
location on the site. ftp/site/debian/source.tar.gz looks like
something debian-specific, which (I believe) is not the case.

> > * Do you find the program useful and why?
> 
> I use it, but I am biased. I like to jump between files. [...]

Sure, you're the author :) My question was to Giorgio. It is best
if the maintainer uses the package so (s)he can triage bug reports,
provide patches and otherwise be of help. This is not a strict
requirement, but a recommendation.

> By the way, is it too late for changes to the upstream source?
> I have found a superior way to build peless.
> [...]
> If these changes are inconvient I will put them on hold
> until the next changes in the source become necessary.

Not at all. When you're happy with them, release as usual, incrementing the 
version string. The maintainer can prepare new packages when it is
convenient for him.

> Sometime in the future, I would like to get peless's error
> messages translated into languages other than English to make
> peless multi-lingual. The prep is all there, all user visible
> strings are indicated by the _() macro! I just have to find
> someone to do the translation.

When you get non-English-native users, the translations will follow
naturally :) If you publish the .pot somewhere, I can try the Bulgarian
translation.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: peless -- GTK Text browser

[Damyan Ivanov]

-=| Giorgio Pioda, Tue, 22 May 2007 21:51:48 +0200 |=-
> I have packaged a nice GTK text reader that can be very usefull to
> compare files (shown in separated tabs), and search for text in files.
> The package seems to me quite mature and is downloadable at:
> 
> http://web.ticino.com/gfwp/debian/peless-1.108/peless_1.108-1.dsc

Some comments/questions:

* Why aren't the .dsc and .changes files gpg-signed?
* Upstream URL is missing from debian/copyright
* There are some commented lines in debian/rules that will never be
used. Why not get rid of these?
* Similarly, debian/watch may be cleaned up somewhat.
* Long description misses a space between "them." and "It". The second
sentence seems redundant to me
* A .desktop file would be nice
* The URL in debian/watch
(ftp://ftp.berliOS.de/pub/peless/ubuntu.704/peless-(.*)\.tar\.gz) looks
strange. Is there a "distribution-neutral" source?
* Do you find the program useful and why?
-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: Rebuilding the whole archive.

[Damyan Ivanov]

-=| Charles Plessy, Mon, 14 May 2007 09:15:23 +0900 |=-
> I would like to do a mass rebuild of at least a significant part of
> the archive to investigate a potential problem on G5 running the
> powerpc port.  I am currently trying to use

Impressive!

> /usr/share/doc/pbuilder/examples/pbuildd/buildd.sh from the
> pbuilder package, but I have a few problems with it.

Perhaps you may use strace -p $PID for some clue who is waiting for
what?

> Even if I manage with buildd.sh, I would be interested to know about
> alternatives. My main interest is to generate build logs, but I do not
> need to keep the .debs. Are there better tools for this ?

cowbuilder should spare you some untar time.

I've heard sbuild is used as an autobuilder these days. Never used it
myself though.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: ibpp

[Damyan Ivanov]

-=| David Paleino, Sat, 12 May 2007 16:21:31 +0200 |=-
> Well, I've found a reference to "libibpp" when trying to repackage
> gambas2 (in particular, the gb.db.firebird component, which provides
> firebird accessibility to gambas projects).
[cut]

> > source (as flamerobin does). Your package is not a library one, but
> > still, did you talk to upstream stating your intention to package
> > IBPP?
> 
> Well, not, I didn't talk to Olivier (or anybody else). I didn't think
> it was necessary.

It is not strictly required, but having a friendly communication with
upstream is very comfortable when you come to report bugs, request
enhancements etc, as part of the maintainer's job.

-=| David Paleino, Sat, 12 May 2007 16:25:00 +0200 |=-
> Some (bad) news: I've just found the ibpp sources included in gambas.
> D'oh. -.-'

It seems gambas developers followed IBPP author's recommendation
too.

> Now, what should I do? Abandon the ITP (maybe a wontfix)? If any
> project using ibpp includes it in the sources, there's no reason in
> having this package.

I'd just close the bug (mailto:423507-done) with an explanation of the
situation.

Or, if you have time and energy, try to explain upstream why a
separate package would be a benefit.

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: ibpp

[Damyan Ivanov]

Hi, David,

-=| David Paleino, Sat, 12 May 2007 14:54:12 +0200 |=-
> I am looking for a sponsor for my package "ibpp".
> 
>   Version : 2.5.3.1-1
> * URL : http://www.ibpp.org

> It builds these binary packages:
> ibpp   - C++ client interface for Firebird

> - - URL: http://mentors.debian.net/debian/pool/main/i/ibpp

As I understand it, the IBPP files are simply copied
in /usr/include/ibpp. While this is not bad by itself, I wonder, what
is the purpose of the package?

Don't get me wrong, I am not against the package, it would be just
interesting to hear the reasons why you need it.

When packaging flamerobin, I talked to Olivier (IBPP lead developer)
and his preference was not to make IBPP a separate *library* package,
but simply continue to include it in the applications' source (as
flamerobin does). Your package is not a library one, but still, did you
talk to upstream stating your intention to package IBPP?

> It seems to me that the IBPP License is a free software license.
> It can be read at . Should I contact
> debian-legal?

Flamerobin[1] includes IBPP in its sources and it passed
d-legal and ftp-master approval.


dam
[1] http://packages.qa.debian.org/f/flamerobin.html (see "copyright"
link below)

-- 
damJabberID: [EMAIL PROTECTED]


signature.asc
Description: PGP signature

Re: RFS: revoco

[Damyan Ivanov]

-=| Evgeni Golov,  6.05.2007 01:39 |=-
> On Sat, 05 May 2007 20:52:33 +0300 Damyan Ivanov wrote:
> 
>>> http://mentors.debian.net/debian/pool/main/r/revoco/revoco_0.3-1.dsc
>> SUID binary... this is scaring me. Is it really necessary?
> 
> Well, it is not necessary, but helps $USER to control the mouse.
> You need to write some hex-values to /dev/usb/hiddevX to change the
> settings of the mouse, and as this file is owned by root, you need
> either to be root or to change the permissions... The possibilities to
> work with are:
> 1. let the binary as it is, and tell $USER he has to use sudo or su
> 2. set the binary suid-root (the code looks OK for me - IANASE)
> 3. create some new group and let udev give this group write permission
> to the 'file' -> IMHO overkill for such a small util

I guess this is the only way to give user permissions to write to that
file. If you don't want to invent a new group for this - look at the
groups that are already used - there may be some useful for "desktop
users". If not, IMHO another group is not that much of an overhead.

> I could live with 1, but I think 2 is more userfriendly.

3. would be user-friendly too :)

>> You set CFLAGS in debian/rules and then patch Makefile to contain the
>> same CFLAGS. I'd remove the CFLAGS from Makefile at all to leave only
>> one place to change (if there is need).
> 
> Hm, yeah. The problem is, I need -DVERSION=foo in CFLAGS, which I think
> I should not set from debian/rules... I've changed the patch now to
> -CFLAGS=-Os -DVERSION=\"$(V)\"
> +CFLAGS += -DVERSION=\"$(V)\"
> 
> and call
> CFLAGS="$(CFLAGS)" $(MAKE)
> from debian/rules - why the hell I need to set them before make?

make is black magic :)

-- 
dam



signature.asc
Description: OpenPGP digital signature

Re: RFS: revoco

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Evgeni Golov,  5.05.2007 00:45 |=-
> On Tue, 17 Apr 2007 09:55:48 +0200 Evgeni Golov wrote:
> 
>> I am looking for a sponsor for my package "revoco".
> 
> I am still looking, so I ping this RFS ;)
> 
> I've just uploaded a slightly updated version of the package, fixing
> some small issues, enjoy it:
> http://mentors.debian.net/debian/pool/main/r/revoco/revoco_0.3-1.dsc

SUID binary... this is scaring me. Is it really necessary? Did you audit
the code? (Sorry if you already answered this)

You set CFLAGS in debian/rules and then patch Makefile to contain the
same CFLAGS. I'd remove the CFLAGS from Makefile at all to leave only
one place to change (if there is need).


dam
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGPMRhHqjlqpcl9jsRAv0GAJ9vX7lr6QXPbGUZdBVywVR/nMAqKQCfcYEI
ZqEQ515kpG/WTVQTQoNFzYA=
=6FJ8
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: [sponsored] libconfig-general-perl new release.

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Francesco Cecconi,  4.05.2007 22:16 |=-
> On Friday 04 May 2007, Gunnar Wolf wrote:
> 
>> Hi,
> Hi,
>> Your .orig.tar.gz is not the same as the one published in CPAN:
>>
>> [EMAIL PROTECTED]:/tmp$ wget 
>> http://mentors.debian.net/debian/pool/main/l/libconfig-general-perl/libconfig-general-perl_2.33.orig.tar.gz
>> (...)
>> [EMAIL PROTECTED]:/tmp$ wget 
>> www.cpan.org/modules/by-module/Config/Config-General-2.33.tar.gz
>> (...)
>> [EMAIL PROTECTED]:/tmp$ diff Config-General-2.33.tar.gz 
>> libconfig-general-perl_2.33.orig.tar.gz
>> Binary files Config-General-2.33.tar.gz and 
>> libconfig-general-perl_2.33.orig.tar.gz differ
>>
>> Why?
> 
> Many thanks Wolf, I have fixed this problem with orig. 

Uploaded.

dam
- --
Damyan IvanovJabberID: [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGPMCMHqjlqpcl9jsRAly6AKC5jvKJNB+lcm8CHAlgpmIg+t34kQCfbbZE
HXSgJmckSseM7DnNFDU8YLM=
=sH/7
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: truncate

[Damyan Ivanov]

-=| Peter Pentchev, 19.04.2007 00:54 |=-

> Or should I file a wishlist bug against bsdmainutils to get
> truncate(1) included there?

I'd say bsdmainutils fits perfect. Its description says:

  lots of small programs many people expect to find when they use a
  BSD-style Unix system

So please file a whishlist bug for bsdmainutils. Bonus points for
providing a patch :)


    dam
-- 
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: RFS: openjpeg

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Paul TBBle Hampson, 30.03.2007 17:58 |=-
> On Fri, Mar 30, 2007 at 12:06:26AM +0300, Damyan Ivanov wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
> 
>> - -=| Paul TBBle Hampson, 29.03.2007 19:37 |=-
>>> And
>>> although I haven't done it in a while, I don't recall dpatch-edit-patch
>>> being particularly fun to use on a non-applying patch...
> 
>> My experience exactly. This is why I use quilt instead :)
> 
> I'm going to have to have a look at quilt. I was under the impression
> that it was a rather complicated patch-management system, used for
> example by Andrew Morton for managing the -mm tree pre git.

It was used for this, yes. But still I don't think it is complicated. I
find it more natural than dpatch. I used to think like you, but once I
actually read the quilt manpage and tried it in action, I never looked
back at dpatch again. There is some learning curve, but it is surely not
as complicated as "used by -mm tree pre-git" would suggest.

That said, you are of course free to use whatever way of patch-handling
you feel comfortable with. It seems that some sponsors have preference
of how this is done, that's all.


dam
- --
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGDSrIHqjlqpcl9jsRAoeRAKCs0btIm1PzKnfGSMVW7txL3VBMwwCgsYYR
TJarrAR8M26qRlkXKK3DhSQ=
=Zo3B
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: openjpeg

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Paul TBBle Hampson, 29.03.2007 19:37 |=-
> And
> although I haven't done it in a while, I don't recall dpatch-edit-patch
> being particularly fun to use on a non-applying patch...

My experience exactly. This is why I use quilt instead :)


    dam
- --
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGDCpSHqjlqpcl9jsRAoOjAJ9FBDt3pY6iQ1si5eFvy99/WsLOiwCfanbv
VwUGAcoBXrRsDMOkLrUk6IU=
=3BSr
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: xchat-idle: XChat plugin that marks you /away and /back automatically

[Damyan Ivanov]

-=| Sam Morris, 21.03.2007 00:51 |=-
> Hello folks, I am looking for a sponsor for a small XChat plugin I wrote
> called idle.

Is there a reason why this can't be a patch to XChat? A whole package
just for this seems like an overkill to me.

Otherwise, I really miss that functionality in XChat.

Some ideas for improvements:
- time before going auto-away should be configurable
- make both auto-away and auto-back optional
- make away/back text optional/configurable

Of course, I don't know if such configuration is at all possible with
XChat, but I thought I'd mention it just in case :)


    dam
-- 
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: Legends The Game, new debian package

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Bart Martens,  4.03.2007 01:11 |=-
> Related to what Roberto wrote above about the shared libraries, here is
> how I would create the .orig.tar.gz :
> 
> sh legends_linux-0.4.1.42.run --noexec --keep --nox11 \
>  --target legends-0.4.1.42/legends_release
> rm legends-0.4.1.42/legends_release/libSDL-1.2.so.0
> rm legends-0.4.1.42/legends_release/libSDL-1.3.so.0
> rm legends-0.4.1.42/legends_release/libogg.so.0
> rm legends-0.4.1.42/legends_release/libvorbis.so.0
> rm legends-0.4.1.42/legends_release/libopenal.so
> rm legends-0.4.1.42/legends_release/OPENAL32.DLL
> rm legends-0.4.1.42/legends_release/ReadMe_legals.txt
> rm legends-0.4.1.42/legends_release/runlegends
> rm legends-0.4.1.42/legends_release/install.sh
> tar czf legends.tgz legends-0.4.1.42

Shouldn't the source package name reflect that it has been re-packaged?
Something like "legends-0.4.1.42.ds.1" ?
On the other hand, isn't it sufficient to only remove these in the clean
target (thus making them disappear from the .deb), avoiding repackaging
the source tarball ?

Please don't take this as a nitpicking, I am trying to understand if I
miss something.


dam
- --
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF6pxWHqjlqpcl9jsRAveFAJsFxjR5Fz0w1OjB02910nni7oGoPQCgyDuE
VrMx0QsfUql8bcQ2vJHHdxw=
=Iuac
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Legends The Game, new debian package

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| olaf,  3.03.2007 09:20 |=-
> Thanks for your replies. Would it be allowed to put the binaries 
> in /usr/lib/legends and create links to /usr/share/legends where the 
> data-packages are? 

Sure (for the symlinks).

Better use /usr/share/games/legends instead of /usr/share/legends.


dam
- --
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF6UA/Hqjlqpcl9jsRAjvaAJwJEtCzskJi3Cba2d8BgaaGSadJhQCfZ6Vl
vCkNRzM5xCM5DCIlZV0Ze7I=
=CwWZ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: new package splix

[Damyan Ivanov]

-=| Carlos Pasqualini, 16.02.2007 16:49 |=-
>> Next, you upload the source package (.dsc, .orig.tar.gz, .diff.gz)
>> somewhere and ask on this list for someone to review it.
> 
> i use the provided tar.bz2 with the default compilation options on my
> i386 PC.
> i must learn what i must change (if is something) i haven't read the
> Debian Policy yet, i'm only packing into a deb a package that compiles
> too easy on my system. (otherwise i have not the knowledge to do the
> work)

I am not sure I understand correctly, but it seems to me you missed
some important readings. Please visit
http://www.bg.debian.org/doc/maint-guide/ and start from there.

>> Did you file an ITP bug?
> 
> ITP ?? what it means?

"Intent to package". This is a special kind of bug report, filed
against the "wnpp" package on the debian bug tracking system. More on
this in section 2.1. of the guide above.


    dam
P.SA. Please don't reply directly, always CC the list too.
-- 
Damyan Ivanov   Modular Software Systems
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  JID [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: Choice between ubuntu or brand new package for Bug#345039

[Damyan Ivanov]

-=| David Newgas, 16.02.2007 11:31 |=-
> Bug#345039 is an request for
> "kzenexplorer" (http://kzenexplorer.sourceforge.net/) to be included in
> Debian.  It is currently already in Ubuntu
> (http://packages.ubuntu.com/kzenexplorer). I created a brand new Debian
> package (lintian clean except for lack of a man page) before noticing it
> was in Ubuntu.  Which is preferred, a new package or using the Ubuntu
> one?  And if the latter, is it simply done by using the Ubuntu
> orig.tar.gz/diff.gz/dsc ?

You are still responsible for the debian package, so simply taking the
ubuntu one without further checks that it follows the debian
requirements is not good.

If I was you, I'd go with what I had created since this is what I know
and can guarantee for. Taking a look at the ubuntu package and
borrowing some ideas from it if appropriate is also good (check
packaging licensing though).

On the other hand, if ubuntu package is much superior, you may want to
take it and check if everything is alright - debian/copyright, other
control files etc, pretending that you see it for the first time.

In any case, cooperation with the ubuntu maintainer should be more
productive than two solo performances, I guess.


HTH,
dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: new package splix

[Damyan Ivanov]

Hi, Carlos,

-=| Carlos Pasqualini, 15.02.2007 23:09 |=-
> i found a package called splix, it has no deb available.

> This driver works much better than GDI for my Samsung ML-2010 printer,

sounds cool.

> SOMEBODY TELL ME WHAT'S NEXT!!

No need to yell, we all hear pretty well :)

Next, you upload the source package (.dsc, .orig.tar.gz, .diff.gz)
somewhere and ask on this list for someone to review it.

Did you file an ITP bug?


Thank you for your time,
    dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  [EMAIL PROTECTED]



signature.asc
Description: OpenPGP digital signature

Re: Few questions

[Damyan Ivanov]

-=| Thomas Goirand, 29.01.2007 10:08 |=-
> Hi!
> 
> I have few questions that would help me to solve things in my package. I
> have package1 and package2 being same but with different dependencies,
> so the user can choose between them.
> 
> First, if my package produces many binaryies, is it ok to do symlinks of
> the postinst if they are same. Like:
> 
> debian/package1.postinst would link to debian/package2.postinst

I had a similar dilemma and my solution was to write
"master.postinst", which gets copied to packageX.postinst in
debian/rules. packageX.postinst are deleted by the clean target.

You could apply this to the cron snippet too.


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: jabbin

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Andrew Donnellan, 27.01.2007 23:03 |=-
> SSL is required for use with Google Talk, so unfortunately I don't
> think it can be removed without making it mostly useless. However I
> think that it uses QCA for that.

SSL is implemented also by GNU TLS...
You may point upstream to this implementation to avoid SSL licensing
problems.

Just an idea.


    dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvHynHqjlqpcl9jsRAskEAJ9C6retdwoBv8mLfjL0VWjCsIZ9TACeICSD
QE55LeVRKA2+l89bhKL/7ns=
=S7M3
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: softbeep (updated package)

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Thijs Kinkhorst, 27.01.2007 19:11 |=-
> On Sat, 2007-01-27 at 00:08 +0100, Florent Rougon wrote:
>>> IMHO, this is something that makes 3.7.2.0 and 3.7.2.2 two non-equal
>>> Policy versions. I wonder why wasn't this 3.7.3.0 instead?
>> Hmmm... maybe because the "should" in 3.7.2.0 was actually obviously a
>> "must" for security reasons?
> 
> Exactly... since it's plain stupid to have these files world-writable,
> it is a "bug" in the text that it was not written that way, not a change
> of what you should do. You should already not make these world-writable
> of course.

Sure.

I simply wondered how s/should/must/ can be considered editorial change,
as "should" presents a recommendation, as "must" states a strict rule.

I didn't find any lintian check on this matter so how can you tell what
part of the archive is affected? With "editorial" revision maintainers
may not be aware of the problem.

Of course, I very much hope that the count of packages with
world-writeable maintainer scripts is zero, but would like to be sure.
Making the change non-"editorial" and implementing a check in lintian
would help towards this. I'll file a bug for lintian these days.


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFvHuDHqjlqpcl9jsRAlCOAKCXTMWJIB8RLjbxljh94ui6hQejlACcCpL8
oVf3uxbOEHkexh36QxHOvpk=
=5U0K
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Time before closing an unreproducible bug

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Julien Valroff, 27.01.2007 10:47 |=-
> Hi,
> 
> Is there any globally accepted consensus about when closing an
> unreproducible bug?
> 
> #396653[0] was opened 86 days ago, and nobody can reproduce this bug,
> which was already downgraded from grave to important with the RMs'
> permission.
> I would like to close the bug to keep the BTS as clean as possible, but
> do not want to break established rules.
> 
> Any hints?

I'd mail the reporter and ask of (s)he has any news.


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067  [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFuyQzHqjlqpcl9jsRAsmDAJ0bpzEhNFkb7yTl0rVbgdYXLetQZwCgtkOK
YiytZ4lXYd5Bq8IvFyFtYO8=
=gpHT
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: softbeep (updated package)

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Thijs Kinkhorst, 26.01.2007 15:18 |=-
> * I personally think that "3.7.2.2" is too precise for a
>   standards-version, since the last part should not make any difference
>   for a package. I suggest to keep only the significant "3.7.2" part.

It is funny, but the last ".2" is not insignificant change. See
upgrading-checklist.txt.gz:

 3.7.2.2Oct 2006
  * Maintainer scripts must not be world writeable (up from a
should to a must) [6.1]

IMHO, this is something that makes 3.7.2.0 and 3.7.2.2 two non-equal
Policy versions. I wonder why wasn't this 3.7.3.0 instead?


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFujxBHqjlqpcl9jsRAqmIAKDGILxD+MntrBx5bR7gnsn5mqJ1swCgjuNK
bMmgxn/5iSbXdnDXs7dnQl0=
=Y2so
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: jabbin

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Andrew Donnellan, 23.01.2007 10:46 |=-
> I'll have a look at the patches that were suggested earlier - I may
> apply them upstream as I have access to their repo.
> 
> I'm also going to prepare a new version very soon.

While there, could you consider removing jabbin.1 in debian/rules' clean
target? It seems confusing to me to ship both the .xml source and the
resulting .1 in the .diff, considering that the .1 is automatically built.


    dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFtdDWHqjlqpcl9jsRAiicAKCmEo07UN+9nHXAp7zjhlAHYcHtnwCghbl/
99JrH1Bk2eRDVwAgH9L69bM=
=Cw6Z
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: sshproxy

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Vincent Bernat, 20.01.2007 21:23 |=-
> But I get the point and fixed this problem by not using dh_installinit
> and invoking rc.d "by hand".

Strange. dh_installinit works for me every time. I don't use cdbs,
however so I guess my case is not the same.

Anyway, if you call the init.d script directly, you may want to use the
following often used snippet. It is actually what debhelper tries to put
in your postinst.

if [ -x "/etc/init.d/$DAEMON" ]; then
update-rc.d $DAEMON defaults >/dev/null
if [ -x "`which invoke-rc.d 2>/dev/null`" ]; then
invoke-rc.d $DAEMON start || exit $?
else
$DAEMON start || exit $?
fi
fi

(replacing $DAEMON with the name of the init.d script)

> I have also changed the default to yes. I don't see any valid reason a
> user  would install  sshproxy  and  not launch  it.  Most daemons  are
> packaged  in a  way they  are  automatically launched  in Debian.  One
> exception is rsyncd  that comes with rsync package  and most users are
> not interested in the daemon.
> 
> Do you really think I should add a debconf question about this ?

It's your decision. Judging from what you wrote, I guess a debconf
question would be an overkill.


Good night,
dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFso3wHqjlqpcl9jsRAg7mAKCunHMoqHS6YChiilmHo00eF4WVfgCfYWco
dUL+v8Jx/ihdRAQ1pNaHvdE=
=rt7g
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: sshproxy

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, Vinvent,

Kust a tiny little comment:

- -=| Vincent Bernat, 20.01.2007 15:38 |=-
> It builds these binary packages:
> sshproxy   - ssh gateway to apply ACLs on ssh connections
> sshproxy-backend-mysql - ssh gateway to apply ACLs on ssh connections
> sshproxy-client - ssh gateway to apply ACLs on ssh connections
> sshproxy-extra-plugins - ssh gateway to apply ACLs on ssh connections

Can you provide different short description for different binary
packages where appropriate?

> There is currently one bug in the package due to a problem in cdbs :
> bug #386970. I don't know wthat the correct work around is. This

Many people here advise not to use build system you don't understand
enough as to fix it.

> results in sshproxy not being able to run on install (but this works
> on upgrade). The current workaround is to default to not launch
> sshproxy  on install  (a settings  in /etc/default/sshproxy).  Maybe a
> cleaner workaround would be to use invoke-rc.d by hand ?

Not launch sshproxy by default is good idea (perhaps governed by a
debconf question), but using this as a workaround looks like a quibble
to me :)

Good luck with your package,
dam
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFslcvHqjlqpcl9jsRAj80AJ0arxwihyvTwkmstAX4/+plQ4yPAACeMrNs
dkGgnGhrGYgemqslapt3+04=
=SkDc
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RFC: firebird2.0

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Here[1] you may find the newly packaged firebird2.0. This is the 2.0
version of firebird RDBMS. Debian archive currently contains 1.5 version
(src:firebird), also maintained by me.

I would be glad to get as much comments as possible on possible
packaging issues before I try to get this in the archive.

Thank you for your time,
dam
[1]
ftp://ftp.modsoftsys.net/public/pool/main/f/firebird2.0/firebird2.0_2.0.0.12748.ds1-1.dsc
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFrw07Hqjlqpcl9jsRArpoAJsE7tzZ4bLpvvNy6y2l33ogCEFC4ACffM0l
FcUrOZrNy4MzyoMYeyJB/Go=
=A/Qm
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: reasons why downgrades are Not Supported

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Tobias Richter, 14.01.2007 13:29 |=-
> [EMAIL PROTECTED] wrote:
>> (pre|post)rm of package version 1.5 must undo the actions.
>> However, what exactly is undone must depend on the new version (1.3,
>> 1.0, 0.4), which would clutter the code.
> 
> Correct me if I'm wrong, but the old (pre|post)rm can only be called
> with 'remove', 'pruge' or 'upgrade'. So the script does not know that 
> there is a downgrade (to which version?) being installed afterwards. 

See the section "Downgrades" on the following excellent page:
http://women.debian.org/wiki/English/MaintainerScripts


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFqiKgHqjlqpcl9jsRAg1XAKCuAtBqNFgrVc2glr9mxBIg7iTh0ACfXtpV
XRT1IEnKaH1ePf/Y2/eDwYU=
=KgR9
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: reasons why downgrades are Not Supported

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Sune Vuorela, 14.01.2007 12:31 |=-
> On 2007-01-14, Justin Pryzby <[EMAIL PROTECTED]> wrote:
>> maintscripts often don't support downgrades just because downgrading has 
>> always
>> been advertised as "not guaranteed to work", so very few maintainers put the
>> additional effort and clutter into their code.
> 
> It is not about 'additional effort' but more like 'not being able to
> predict the future'
> 
> how should the (pre|post)inst of package version 1.3 be able to undo the
> changes made in the (pre|post)inst of package version 1.5 ?

It is the other way around.

(pre|post)rm of package version 1.5 must undo the actions.
However, what exactly is undone must depend on the new version (1.3,
1.0, 0.4), which would clutter the code.

So it is no "predicting the future" but "remembering the past".

The big problem IMHO is that not everything may be undone. File format
changes come to mind.


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFqgo5Hqjlqpcl9jsRAkpwAKC/W0B5TwR3C5rPMZQFWu5ggLR4VgCgm7EG
kR7XW/ot+ID/OJBlItoEVOg=
=X0bU
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: Legends: The Game

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Tim Hessint, 13.01.2007 04:01 |=-
>> Why do you insist on creating that package then? If it is included in
>> the distribution, you'll have to take care of it - fix bugs etc. Some
>> of these tasks will be very hard if you don't use the package...
> 
> Because we have a lot of users new to linux that struggle with any
> command line tasks. When this happens I'm usually the one that has to
> walk them through the install process and installing video drivers.
> 
> We're making distro packages to get more exposure and make installation
> easier.

You  may want to create a local package repository then and install from
there. Just add it to each user's /etc/apt/sources.list.

Information on creating repositories is available in this list's
archives. I for one use 'reprepro'.

Just make sure you do the packaging right to avoid breakage.

> Newbie question: How do I get my replies to indent at the proper
> level? I click on "Reply to: debian-mentors@lists.debian.org"

Nothing special. Perhaps your mail program does something magic :)


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFqK7oHqjlqpcl9jsRAv9JAKDNFYd34yBY9MUAEJSA2vWbegtHQQCeL4G4
8EUU9elsrQOFNpELBUXs6DM=
=Qo9U
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: fbxkb

[Damyan Ivanov]

-=| Daniel Baumann, 12.01.2007 11:24 |=-
> Damyan Ivanov wrote:
>> And how Build-Depending on autotools-dev fixes this?
> 
> no, but if he updates the config.{sub,guess} files while clean: in your
> rules. check the libextractor package if unsure.
> 
> however, his package does not make use of config.{sub,guess}, that is
> why i wrote he should remove autotools-dev build-dependency.

Indeed.


    dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: fbxkb

[Damyan Ivanov]

-=| Yavor Doganov, 12.01.2007 10:27 |=-
> В Thu, 11 Jan 2007 23:37:28 +0200, Damyan Ivanov написа:
> 
>> * Why do you build-depend on autotools-dev? I see no auto* usage in
>> debian/rules - just simple ./configure; make.
> 
> If you have outdated config.{sub,guess} the package (probably) will fail to
> build on GNU/k*BSD, GNU/Hurd and some peculiar GNU/Linux arches, such as
> armeb, for instance.

And how Build-Depending on autotools-dev fixes this?


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: Legends: The Game

[Damyan Ivanov]

-=| Tim Hessint, 12.01.2007 03:01 |=-
> I'm still unsure as to whether this will be accepted into Debian. It's a
> fairly large package for Debian to add to its mirrors, especially as
> it's non-free. I haven't been able to find any other non-free games in
> Debian (I'm not a Debian user BTW...nobody's perfect ;) ), so it'd be

Why do you insist on creating that package then? If it is included in
the distribution, you'll have to take care of it - fix bugs etc. Some
of these tasks will be very hard if you don't use the package...


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: fbxkb

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi, Vadim,

- -=| Vadim Vatlin, 11.01.2007 22:41 |=-
> * Package name: fbxkb
>   Version : 0.6-1
>   Upstream Author : Anatoly Asviyan <[EMAIL PROTECTED]>
> * URL : http://fbxkb.sf.net
> * License : GPL like
>   Section : x11
> 
> It builds these binary packages:
> fbxkb  - X11 keyboard indicator and switcher
> 
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/f/fbxkb
> 
> I would be glad if someone uploaded this package for me.

I can't sponsor the package, but I have some small comments (some of
which may well be wrong).

* You seem to heavily patch the manpage. The original manpage looks like
it is taken from another binary (fbpanel). Please remember to send
changes upstream.

* You don't invoke "make clean" in your debian/rules' clean target. To
see why this is bad, try building the package twice with
dpkg-buildpackage (not pbuilder).

* config.h is included in the diff, although it is generated as part of
the build process. It'd be better if you simply remove in the clean
target of debian/rules (and send patch upstream so "make clean" does
this too)

* Why do you build-depend on autotools-dev? I see to auto* usage in
debian/rules - just simple ./configure; make. Did you try building the
package with pbuilder without autotools-dev?

Overall I'd be very glad to see this package in Debian and use it.
Gnome's keyboard applet uses layout names instead of flags and this
makes it hard to quickly see what is the active layout.


Kind regards,
dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFpq4YHqjlqpcl9jsRAtk5AJsElTxeVFcC0yn+F4DPsfXmkaqQhACfUkIq
5En1nd8VetQbq2Kr3WFaXU4=
=dUQj
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: what is debian way to modify Makefile.frag ?

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Marc 'HE' Brockschmidt,  7.12.2006 18:49 |=-
> Daniel Baumann <[EMAIL PROTECTED]> writes:
>> ...but using a patch management system is strongly recommended from the
>> q&a point of view.
> 
> Assuming you meant QA here: No, it's not. If there would be only one
> patch system, you would be right. But between no patch system, dpatch,
> cdbs-simplepatchsys, quilt, dbs and home-brewn patch systems, half of
> the QA work becomes figuring out how to apply the friggin patch for the
> actual problem.
> 
> It's more comfortable for normal package maintainers, though: Moving
> changes to new upstream versions is reduced to cp -r $old/debian/
> $new/debian, apply errors can easily be seperated and it's easy to
> forward stuff to upstream.

Marc,

Where is the "proper" place for documenting the patch system used?
README.Debian-source?
By "proper" I mean where does QA team look for such information?
How can we make QA's job easier, while still benefit from using a patch
system?


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFeEtTHqjlqpcl9jsRAjqSAJ9GEhwQGJNiMqmuWsVkOR2R07jAlACgsCPb
/XgUQJCa1tnRfdaYPptmTQo=
=VbVa
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: hostname -- utility to set/show the host name or domain name

[Damyan Ivanov]

Hi, Jari,

I've noticed two small problems with the changelog that you may want
to fix.

-=| Jari Aalto,  4.12.2006 13:21 |=-
> hostname (2.94) unstable; urgency=low
> 
>   * Mention that /etc/hostname should only contain domain name and not
> the full FQD. (Closes: #253956)

"domain" -> "host" ?

>   * Print warning to stderr when trying to set doemain name to FDQN
> (Closes: #239888)

"doemain" --> "domain".


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: How to unpack upstream tarball in a dpatch-using package?

[Damyan Ivanov]

Marc Haber -- 29.11.2006 13:36 --:
> Be given a source package with the following layout:
> 
> foo/
> foo/debian
> foo/debian/rules
> foo/debian/patches
> foo/debian/patches/00list
> foo/debian/patches/01bar
> foo/upstream/package.tar.bz2
> 
> So I want the package build process to unpack
> foo/upstream/packag.tar.bz2 before trying to apply the patches with
> dpatch.
> 
> Is it better to do some makefile magic for this unpacking (as having
> an unpack-stamp which patch depends on, or would one better have a
> foo/debian/patches/00unpack dpatch snippet doing the unpacking?

I'd do it with makefile magic.

This will allow you to move to another patch system if such need arises.


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: Help with updating nco package?

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- -=| Charlie Zender, 11.11.2006 09:44 |=-
> I am making a stab at incorporating downstream Debian modifications
> into a source package that I maintain called nco.
> My goal is to make the changes to the Debian packaging necessary to
> bring the latest Debian version, nco_2.9.9-3, up to date with my
> latest upstream version, nco-3.1.7.

nco is currently maintained by Debian QA Group. Are you willing to take
over? If so, you should tell them.

> Everything seems to go swimmingly with the build itself until the
> last fifty lines or so of output from dpkg-buildpackage -rfakeroot.
> The text output and packages built by dpkg-buildpackage are at
> 
> http://dust.ess.uci.edu/nco/src/nco_3.1.7-1.dpkg-buildpackage.txt

This gives "404 Not found" error.

dpkg-buildpackage creates a .build file that you can readily publish.


Good luck,
dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFVanKHqjlqpcl9jsRAvaSAJwKuKKi/VQNhrOvGpEIZhFvec5gAACgix8/
Uk5Zu/IuSUoSN2X8LXcgKos=
=PNqq
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: flamerobin (updated package)

[Damyan Ivanov]

Damyan Ivanov -- 30.10.2006 14:31 --:
> > Dear mentors,
> >
> > I am looking for a sponsor for the new version 0.7.5-2
> > of my package "flamerobin".

Now that's what I call "quick"!

abi just uploaded it. Thanks.

dam

-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

RFS: flamerobin (updated package)

[Damyan Ivanov]

Dear mentors,

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

It builds these binary packages:
flamerobin - graphical database administration tool for Firebird DBMS

The package is lintian/linda clean.

Changelog:
 flamerobin (0.7.5-2) unstable; urgency=low

   * Moved linker flags to LDFLAGS
   * Added --as-needed to LDFLAGS to avoid unnecessary NEEDED entries.
 Thanks to Christian 'Greek0' Aichinger.
   * use dh_link to create html docs symlink. Spares a line in debian/dirs
 Thanks to Isaac Clerencia.
   * Remove debian/dirs and use dh_createdirs, since only one dir has
to be
 created.


The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/f/flamerobin
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/f/flamerobin/flamerobin_0.7.5-2.dsc

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

Kind regards,
    dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: Overriding linda source package warnings

[Damyan Ivanov]

Bas Wijnen -- 10.10.2006 12:09 --:
> Then again, looking at the warning there's something wrong with the check as
> well.  That is, assuming you did remove the files in the clean target, the
> hint about that suggests that they don't check what they want.  So even
> without an override you may want to report a bug. :-)

(IIUC)
The check is done on the source package - .orig.tar.gz+diff. The
problem is in the .orig.tar.gz, so clean target has no chance to
correct it.

My vote also is to leave the warning there to remind maintainer to ask
upstream for a fix.


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: Doubt about license

[Damyan Ivanov]

Nelson A. de Oliveira -- 26.09.2006 15:05 --:
> Hi mentors!
> 
> I am creating a package of a program that have several files with:
> 
> * The contents of this file are subject to the Netscape Public
> * License Version 1.1 (the "License"); you may not use this file
> * except in compliance with the License. You may obtain a copy of
> * the License at http://www.mozilla.org/NPL/
> 
> Asking the upstream author about the license of the program, he said
> that it's legacy code and the program is licensed under GPL only.
> 
> My doubt is if it's OK to say on debian/copyright that it's licensed
> under GPL, as the author said, or if I can't say that it's GPL until
> he releases a new source code saying that it's GPL and not NPL.

I'd quote the mail in debian/copyright with explanation of the situation.

And still urge upstream to release the properly licensed code :)



dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: File permissions

[Damyan Ivanov]

Adam Cécile (Le_Vert) -- 11.09.2006 15:49 --:
> I don't think exec bit in a tarball is right. Best way is to repack upstream 
> sources.

Repackaging only to fix permissions is an overkill. Better fix then in
debian/rules and kindly ask upstream to provide sane permissions on
next release.


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFC/RFS: jlhafrontend -- command-line lzh archiver written in Java

[Damyan Ivanov]

Ying-Chun Liu (PaulLiu) --  5.09.2006 06:52 --:
> Henrique de Moraes Holschuh wrote:
>> Why it is named "frontend", if it is in fact the entire tool and not just a
>> wrapper to call lha, which is what "lhafrontend" implies?
>>
> 
> "jlha" is a library written in Java. It can be found at
> http://homepage1.nifty.com/dangan/Content/Program/Java/jLHA/jLHA.html
> 
> "jlhafrontend" is just a wrapper to call "jlha" and provides
> command-line compatibility to the non-free "lha".
> 
> If the package/project name is bad, I can change it. Please give me some
> idea, thanks.

jlha-bin?


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: aria2 [sponsored again]

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Christoph Haas wrote:
> On Saturday 02 September 2006 20:19, Patrick Ruckstuhl wrote:
>> So does the bts look at all changelog entries? Not only the latest
>> (and would therefore not close the bug)?
> 
> You got me. I believe only bugs are closed in the BTS that are listed in 
> the most current changelog entry because that's what makes it into the 
> source control file during the upload.

Bug are closed following .changes content. Normally, this is only the
last changelog entry, but using -v switch of dpkg-buildpackage one can
easily put several revisions in .changes and close all really closed bugs.



dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE+ekTHqjlqpcl9jsRAjsUAJ41qUYuZ+pmeBqrmk9BoGT8Tgdx7wCdFo2g
ZKABCZ/xrQUuUyjb6tIuLz4=
=WohR
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Huge private Debian repository...

[Damyan Ivanov]

Michelle Konzack -- 28.08.2006 15:08 --:
> I need an archive system like the Debian FTP's for woody, sarge, etch
> and sid.  I was searching the Debian website and the Internet but have
> not found any HOWTO's or documentations HOWTO install such system.
> 
> Can anyone point me to the approprieted resources please?

Have a look at reprepro package. There are others as well.



dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: How to write a good manpage ?

[Damyan Ivanov]

Hi, Marco,

Marco Bertorello написа:
> I always used help2man to generate a manpage for those packages that
> hasn't one.
> 
> But now, I'm working on a package that has a non useful help output:
> 
> $ gcstar --help
> Usage: /usr/bin/gcstar [[-u|--update [-a|--all] [-c|--collection]
> [-w|--website] [-i|--import] [-e|--export] [-l|--lang]] | [FILE]]
> 
> How can I write a manpage good for debian?

/usr/share/doc/man-db/examples/manpage.example
/usr/share/debhelper/dh_make/debian/manpage.xml.ex
/usr/share/debhelper/dh_make/debian/manpage.sgml.ex
/usr/share/debhelper/dh_make/debian/manpage.1.ex

(last three from dh-make package)

Except for the synopsis above, you should describe each option's
meaning and what the program does. Write in the manpage whatever you'd
expect to read if you face the program for the first time :)


HTH,
dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: plea to sponsees about announcing location of packages

[Damyan Ivanov]

Christoph Haas написа:
> Damyan Ivanov meant the long description. And that is not contained in 
> the .dsc or .changes file. So I believe the short description is 
> sufficient to get an idea of what the package is doing at a glance.

That's right. Unfortunatelly "long description" is not so well-defined
 when .changes contains multiple binary packages so just forget what I
wrote.


Thanks,
dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: plea to sponsees about announcing location of packages

[Damyan Ivanov]

Matthew Palmer написа:
> On Tue, Jul 25, 2006 at 10:46:47AM +0100, martin f krafft wrote:
>> Matthew, could we please add this to the FAQ?
> 
> It shall be done.  I'll also note about dget (which is a little-known tool,
> I think).

It would be good if this is used in mendors.d.n-generated RFS
templates. (Christof Haas CC-ed). Something like:

  Or just dget http://mentors.debian.net/debian/pool/main//pkg.dsc

instead of the paragraph speaking about "apt-get source".

And being on the whishlist line, May long description be included in
the RFS templates too?


TIA,
dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: contribution in Debian,

[Damyan Ivanov]

Deepak Kumar Tripathi написа:
> I am Deepak and I asked this question many times that how will start
> contribution in Debian (particularly in perl or python / ruby area).
> But I have got any good reply .

If you stop sending HTML mails you may get replies...

> Please send me link  that which packages are looking form help .

Did you ever read http://www.debian.org ? There is a link there, named
"Help Debian" in the lower part of the links section at left.

> And how will I contact them.

Just read on. It takes time, but you should be able to figure out this
by yourself.


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: Request-For-Sponsorship (xfardic)

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Christoph Haas wrote:
> On Wed, Jun 21, 2006 at 10:31:46PM +0200, Adam Borowski wrote:
>> On Wed, Jun 21, 2006 at 09:36:59AM +, Alan Baghumian wrote:
>>> * Package name  : xfardic
>> First, it would be nice if the subject could contain the package's
>> name.  Perhaps the m.d.n boilerplate could include it.
> 
> Good hint. Added to the boilerplate. :)

I have a wish abot the bolierplate too. How about including short and
long description? Something like:

* Package name: flamerobin
  Version : 0.7.2-7
  Upstream Author : [fill in]
* URL : [fill in]
* License : [fill in]
  Section : utils
  Description : graphical database administration tool for Firebird
DBMS

 FlameRobin is a graphical database administration tool for Firebird
 database management system.
 .
 Its goals are:
   - to be lightweight (small footprint, fast execution)
   - cross-platform (Linux, Windows for start, others planned too)
   - dependent only on other open source software
 .
 You need to setup firebird server on local or remote machine before
 using FlameRobin. See packages firebird2-super-server and
 firebird2-classic-server.
 .
  Homepage: http://www.flamerobin.org/

It builds . and so on


Thanks for considering,
dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEmtrVHqjlqpcl9jsRArSxAJoDfX4uDeB+u2NtRqjew07Wc2LXyQCfR3u2
pe2mVXTTAfU1YDirlu66D74=
=jP3B
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[RFS] flamerobin - graphical database administration tool for Firebird DBMS (new)

[Damyan Ivanov]

Dear mentors,

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

This is my second call, first (a week ago)[1] resulted in some
comments (thanks Thijs, Kari, Justin), all resolved.

* Package name: flamerobin
  Version : 0.7.2-7
  Upstream authors: The Flamerobin Development Team
  <http://www.flamerobin.org/>
T.I.P. Group S.A <http://www.tipgroup.com/>
IBPP Team <http://www.ibpp.com/>
Ximian, Inc. <http://www.ximian.com/>
* URL : http://www.flamerobin.org
* License : Expat, IBPPL 1.1 (modified Expat), LGPL
(see copyright file for details)
  Section : utils

It builds single binary package:
flamerobin - graphical database administration tool for Firebird DBMS

The package is lintian and linda clean.

ITP: #334489

The package can be found on mentors.debian.net at
http://mentors.debian.net/debian/pool/main/f/flamerobin

Or just "apt-get source flamerobin" if your sources.list contains:
deb-src http://mentors.debian.net/debian unstable main

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

Kind regards
 Damyan Ivanov
(with the help of mentors.debian.net)

[1]
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: flamerobin

[Damyan Ivanov]

Kari Pahula wrote:
> On Tue, Jun 13, 2006 at 06:50:19PM +0300, Damyan Ivanov wrote:
>> Thijs Kinkhorst wrote:
>>> * debian/control: Architecture is set to "i386 amd64". What prevents
>>>   the package from being usable on other architectures? Are you sure
>>>   you don't mean "any"?
>> flamerobin depends on libfbclient1, which is currently available only
>> on i386 and amd64. Additionally, flamerobin Build-Depends on
>> firebird2-dev, which is also available only for i386 and amd64.
> 
> That's not a proper reason to set architectures.  Buildds can
> correctly detect if the build dependencies are missing on an
> architecture.  You should only set specific architectures if it is
> because of something related directly to your package.
> 
> If your dependencies were ever to come available to the missing
> architectures, you would need to make a new revision instead of just
> triggering a rebuild on the corresponding buildds.

I see. Better leave it in dep-wait state on (B-Deps-)unsupported
architectures than require a manual intervention to add an
architecture in the future.

Thanks, Kari.

For those interrested, this is documented in wanna-build-states[1]



Updated package is available at
ftp://shrek.creditreform.bg/public/pool/main/f/flamerobin/flamerobin_0.7.2-7.dsc

Please, consider checking/uploading it.

dam
[1] http://www.debian.org/devel/buildd/wanna-build-states
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: RFS: flamerobin

[Damyan Ivanov]

Thijs Kinkhorst wrote:
> Hello Damyan,
> 
>> I am looking for a sponsor for flamerobin - а graphical database
>> administration tool for Firebird DBMS. (ITP# 334489)
> 
> I can't sponsor you (yet), but I did review your package. Here's some
> things I found.

Thanks, Thijs, for your time!

> * debian/control: Architecture is set to "i386 amd64". What prevents
>   the package from being usable on other architectures? Are you sure
>   you don't mean "any"?

flamerobin depends on libfbclient1, which is currently available only
on i386 and amd64. Additionally, flamerobin Build-Depends on
firebird2-dev, which is also available only for i386 and amd64.

> * debian/docs: you install BUILD.txt as documentation, but Debian users
>   do not need that info at all. Better leave it out. You install the

Good catch!

>   'real' documentation under /usr/share/flamerobin/docs, why not under
>   /usr/share/doc ?

This documentation is intended for browsing via flamerobin's internal
help browser. In that sense it clasifies better as "data", than as
"package documentation".

On the other side, someone may want to browse it withoout graphical
environment, so I've put a html symlink in /usr/share/doc/flamerobin
pointing to /usr/share/flamerobin/docs.

> * debian/changelog: you mention in the -3 version that that's the first
>   upload to the Debian archive, but it's not. Maybe better to not claim
>   that and move the text + bug closing to the -4 version.

Moved to -5 (current)

> * debian/patches: what's with the commented out patches in 00list that
>   aren't packaged? Doesn't make sense to refer to patches that aren't 
>   included. What's the intent of the 137kB patch
>   remove-supplied-fbheaders.dpatch? I can't really judge from its
>   description, but it's huge - is that necessary?

Now that upstream doesn't ship the headers in question any more, it is
of historical value. Removed. As well as the rest. dpatch
dependency/rules still left to ease adding patches in a future release.

> * debian/postinst,postrm: these are essentially empty and can be
>   removed.

Removed indeed.

> * debian/watch: some people prefer to use
>   http://qa.debian.org/watch/sf.php instead of direct queries of sf.net.

As Frank Thomas pointed out, this works exactly the way you suggest.


Thanks again, Thijs.


New release -6 ready for sponsoring.

ftp://shrek.creditreform.bg/public/pool/main/f/flamerobin/flamerobin_0.7.2-6.dsc



dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

RFS: flamerobin

[Damyan Ivanov]

Hi,

[I'm subscribed]

I am looking for a sponsor for flamerobin - а graphical database
administration tool for Firebird DBMS. (ITP# 334489)

 FlameRobin is a graphical database administration tool for Firebird
database
 management system.
 .
 Its goals are:
   - to be lightweight (small footprint, fast execution)
   - cross-platform (Linux, Windows for start, others planned too)
   - dependent only on other open source software
 .
 You need to setup firebird server on local or remote machine before using
 FlameRobin. See packages firebird2-super-server and
firebird2-classic-server.
 .
  Homepage: http://www.flamerobin.org/

lintian/linda-clean, builds in pbuilder.

Source/binary packages are available on
ftp://shrek.creditreform.bg/public/pool/main/f/flamerobin/


Current package is at revision -4, please use "-sa" when building.
Also, since ITP is closed in -3, please use "-v0.7.2-2" or even
"-v0.4.0-0"


Thanks for considering,
dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: Problem uploading on mentors.debian.net

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Charles Plessy wrote:
> I wanted to correct an error on a package I recently uploaded on
> Mentors (forgot dpatch in the build-dependancies), however, as some
> files did not change their md5sum, I can not dput the new version:
> 
> kunpuu|charles|$ dupload --to mentors probcons_1.10-1_powerpc.changes
> Uploading (scpb) to mentors.debian.net:~
> [ job probcons_1.10-1_powerpc from probcons_1.10-1_powerpc.changes
>   announce (probcons_1.10-1_powerpc.changes) to [EMAIL PROTECTED] already done
>  probcons_1.10-1_powerpc.deb, md5sum ok, already done for mentors
>  probcons_1.10-1.diff.gz, md5sum ok, already done for mentors
>  probcons_1.10.orig.tar.gz, md5sum ok, already done for mentors
>  probcons-extra_1.10-1_powerpc.deb, md5sum ok, already done for mentors
>  probcons_1.10-1.dsc, md5sum ok, already done for mentors
>  probcons_1.10-1_powerpc.changes ok, already done for mentors ]
> Nothing to upload

Did you read the fourth paragraph of dupload's manpage?


dam
- --
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEiGUQHqjlqpcl9jsRAv1kAJ0aY9Q4LJ0t7HByqTf5Kt8DLNjMcwCgswt7
j/zsYcuMLTUF9vJe1nTsoCE=
=veD/
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Custom Perl library location

[Damyan Ivanov]

Mattias Nordstrom wrote:
> I'm packaging cdrw-taper and it replaces Amandas /usr/lib/amanda/taper
> with a Perl script. This Perl script uses a taperlib.pm library which is
> now located in the same path. Linda however doesn't like this and reports:
> 
> W: cdrw-taper; File /usr/lib/amanda/taperlib.pm contained in /usr/lib of
> Architecture: all package.
>  The file shown above is installed into /usr/lib, but the package that
>  contains it is a architecture-independent package. This file should be
>  installed into /usr/share instead.
> 
> Can I just override this or should taperlib.pm be put somewhere else,
> like /usr/share/perl5/taperlib.pm ?

I'd do the followoing:

It taperlib.pm is useful for other packages, the perhaps put it in
/usr/share/perl5 (and maybe even in a separate package libtaberlib-perl).

If, on the other hand, cdrw-taper is the only package that uses
taperlib, put in in /usr/share/cdrw-taper and "use lib
'/usr/share/cdrw-taper';" in cdrw-taper.


dam
-- 
Damyan Ivanov   Modular Software Systems
[EMAIL PROTECTED]
phone +359(2)928-2611, 929-3993  fax +359(2)920-0994
mobile +359(88)856-6067 [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: How can I simply test building a package with a different compiler version?

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Fabian Guter wrote:
> Hi!
> 
> I'm using svn-buildpackage to build a debian package.
> To test with other versions of g++ I changed the link /usr/bin/g++ to
> point to g++-4.1 rather than to g++-4.0 and change it back after the test.
> 
> Is there a simpler way to tell svn-buildpackage (or the underlying build
> tools) which compiler it should use?

In case your package uses auto*, then configure script most probably
honours CC, CXX, CPP and CXXPP environment variables. Put
 # Force usage of 4.1
 export CC=gcc-4.1
 export CXX=g++-4.1
 export CPP=cpp-4.1
 export CXXPP=cpp-4.1
before invoking configure and you should be fine.



dam
- --
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEWi4gHqjlqpcl9jsRAvyXAKCN6EgOEj6yFDelztrA5gOBbghm0gCfQHaR
VILsWd63jpv0BKLVOwWABSQ=
=Uk/B
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: how to create a Release file

[Damyan Ivanov]

Tomas Davidek wrote:
> Damyan Ivanov wrote:
>> See second paragraph. Perhaps a couple of "-o APT::FTPArchive::Xyz=Foo"
>> options could help?
>>  
>>
> Thanks for the answer, unfortunately it does not work (at least not in
> stable release). Any option I specified is not taken into account (no
> error messages on the output either!), the Release file still begins
> only with:
> --
> Date: Tue, 25 Apr 2006 08:30:22 UTC
> MD5Sum:
> ...
> --
> Maybe upgrading to testing solves the problem ?? Another question -
> where the Release file should be located ? According to docs I placed it
> into dists/, but when looking at the debian mirrors I see also
> some Release files in dist//main/binary-i386 etc
> 
> Can anyone comment on it, please ?

I can't help you with this one either. I personally use reprepro for
maintaining private repositories. It works if you obey to not try to
upload each revision more than once... May be looking at reprepro's
source can give you some ideas as of how to generate Release files.

Not very helpful, sory.


dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature

Re: how to create a Release file

[Damyan Ivanov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tomas Davidek wrote:
> I rather suspect that there is something wrong with the Release file
> itself, it seems some header is missing. My Release looks like:
> --
> Date: Fri, 21 Apr 2006 13:45:27 UTC
> MD5Sum:
> d41d8cd98f00b204e9800998ecf8427e0 Release
> 44a11d9ba1cc5fe28646ca9b9e3c 1269
> main/binary-amd64/Packages.gz
> ab29d796accdd96e9f700399d1f70ef9  925
> main/binary-amd64/Sources.gz
> a7a653a9884509b6f6612cab71047ab9 1269
> main/binary-i386/Packages.gz
> --
> while the Debian ones have a header in the beginning:
> ---
> Origin: Debian
> Label: Debian-Security
> Suite: testing
> Codename: etch
> Date: Mon, 17 Apr 2006 08:35:59 UTC
> Architectures: amd64 alpha arm hppa i386 ia64 m68k mips mipsel powerpc
> s390 sparc
> Components: updates/main updates/contrib updates/non-free
> Description: Debian testing Security Updates
> MD5Sum:
> 5c8b4d953e776a92ca7d6da9edcb7196 7914
> main/binary-alpha/Packages
> 927ab0a52245a0be815c50f5fdb58ca5 1867
> main/binary-alpha/Packages.gz
> 
> Is that important ? If so, is there any script to generate the header or
> do I have to do it myself ?

apt-ftparchive(1) gives:
   release
  The  release  command  generates a Release file from a directory
  tree. It recursively searches the given directory for  Packages,
  Packages.gz, Packages.bz2, Sources, Sources.gz, Sources.bz2, Re‐
  lease and md5sum.txt files. It then writes to stdout  a  Release
  file containing an MD5 digest and SHA1 digest for each file.

  Values  for  the  additional metadata fields in the Release file
  are  taken  from  the  corresponding  variables  under  APT::FT‐
  PArchive::Release,  e.g.  APT::FTPArchive::Release::Origin.  The
  supported fields are: Origin, Label, Suite,  Version,  Codename,
  Date, Architectures, Components, Description.

See second paragraph. Perhaps a couple of "-o APT::FTPArchive::Xyz=Foo"
options could help?


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

iD8DBQFESgJtHqjlqpcl9jsRAoAFAJ9Kg1/7Ifm7P06s3YCfDU3N7kOu3wCgjxqK
WSEhAnEGi5pt2/l94y/FbtM=
=abrM
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: RFS: libhtml-fromtext-perl

[Damyan Ivanov]

Francesco Cecconi wrote:
> I'm looking a sponsor for adopt libhtml-fromtext-perl!
> 
> I have another two packages in Debian!
> 
> libemail-find-perl
> libconfig-general-perl

If you fail to find a sponsor here, you might want to try
[EMAIL PROTECTED]

Since you seem interested in maintaining perl packages it really is a
god idea to join the group :)


Good luck,
dam
-- 
Damyan Ivanov  Creditreform Bulgaria
[EMAIL PROTECTED]  http://www.creditreform.bg/
phone: +359(2)928-2611, 929-3993fax: +359(2)920-0994
mob. +359(88)856-6067   [EMAIL PROTECTED]/Gaim



signature.asc
Description: OpenPGP digital signature