Re: Problematic perl file header and lintian
Norbert Preining wrote:
>Hi all!
>
>I need help in fixing the following perl header, since lintian moans
>that shell-script-fails-syntax-check:
>
>#! /bin/sh
>eval '(exit $?0)' && eval 'PERL_BADLANG=x;export PERL_BADLANG;: \
>;exec perl -x -S -- "$0" ${1+"$@"};#'if 0;
>eval 'setenv PERL_BADLANG x;exec perl -x -S -- "$0" $argv:q;#'.q+
>#!perl -w
>package Htex::a2ping; $0=~/(.*)/s;[EMAIL PROTECTED],'.';do($1);[EMAIL
>PROTECTED]@;__END__+if !1;
># This Perl script was generated by JustLib2 at Wed Apr 23 09:14:13 2003.
># Don't touch/remove any lines above; http://www.inf.bme.hu/~pts/justlib
>
>I can only say that it definitely works on a lot of systems, finds perl.
>What I tried is removing all the stuff before the perl -w and changing
>it to /usr/bin/perl -w, but this kicks the script into an endless loop.
>Strange.
>
>
Try removing everything before #!perl -w, changing that to
#!/usr/bin/perl -w just as you did, and also removing everything after
Package Htex::a2ping; (the weird code starting with $0=. But I didn't
try that.
--
There's small choice in rotten apples.
-- William Shakespeare, "The Taming of the Shrew"
Eduardo M KALINOWSKI
[EMAIL PROTECTED]
http://move.to/hpkb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: KildClient - Powerful MUD client with a built-in Perl interpreter
I'm looking for a sponsor for a program I wrote and packaged. Package name: kildclient Version : 2.3.0 Upstream Author : Eduardo Kalinowski <[EMAIL PROTECTED]> URL : http://kildclient.sf.net License : GPL ITP : 303635 Description : Powerful MUD client with a built-in Perl interpreter KildClient is a MUD Client written with the GTK+ windowing toolkit. It supports many common features of other clients, such as triggers, gags, aliases, macros, timers, and much more. But its main feature is the built-in Perl interpreter. You can at any moment execute Perl statements and functions to do things much more powerful than simply sending text the the mud. Perl statements can also be run, for example, as the action of a trigger, allowing you to do complex things. Some built-in functions of KildClient allow interaction with the world, such as sending commands to it. KildClient's ANSI support is extensive: it supports not only the common 16 colors, but also support underlined text (singly and doubly), text in italics, text striked through, reverse video and "hidden" text. It also supports vt100's line-drawing characters, and xterm's escape sequences for a 256-color mode. All these features make KildClient one of the clients with the most features for displaying the mud output. Kildclient supports the MCCP (Mud Client Compression Protocol) protocol, versions 1 and 2, to reduce the necessary bandwidth. The package is linda and lintian clean, and builds fine under pbuilder. Package is available at http://kildclient.sf.net/debian -- One difference between a man and a machine is that a machine is quiet when well oiled. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lintian warning problem, RFS: gaupol
Piotr Ozarowski wrote: >Andrea Bolognani ([EMAIL PROTECTED]): > > >>It means the man page is not correct. >>See http://lintian.debian.org/reports/Tmanpage-has-errors-from-man.html >> >> > >But I'm not getting "cannot adjust", "can't break" or "can't find >numbered character". All I get is: > >$ lintian ./gaupol_0.4.0-1_all.deb >/tmp/eOvxYgXVnE/binary/gaupol/unpacked >W: gaupol: manpage-has-errors-from-man usr/share/man/man1/gaupol.1.gz >/tmp/eOvxYgXVnE/binary/gaupol/unpacked/usr/share/man > >$lintian ./lintian_1.23.16_all.deb >/tmp/cazjEVq6iH/binary/lintian/unpacked >W: lintian: manpage-has-errors-from-man usr/share/man/man1/lintian.1.gz >/tmp/cazjEVq6iH/binary/lintian/unpacked/usr/share/man >W: lintian: manpage-has-errors-from-man usr/share/man/man1/lintian-info.1.gz >/tmp/cazjEVq6iH/binary/lintian/unpacked/usr/share/man > >Is it possible that even lintian package has bugs? > > Do you perchance have the -v flag in the GZIP environment variable, or are passing it to gzip (and gunzip) by default somehow? Because if this is the case, then lintian will consider the output of gzip (something like "file: 80.2% -- etc, etc") as an error message from man, and emit that warning. -- Genius, n.: A chemist who discovers a laundry additive that rhymes with "bright." Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: plea to sponsees about announcing location of packages
martin f krafft wrote: > also sprach Christoph Haas <[EMAIL PROTECTED]> [2006.07.27.1150 +0100]: > >> If you are sponsoring packages that's just a one-time action. Then >> sponsorees can tell you that a new package is available on >> mentors.debian.net and you just run "apt-get update && apt-get source >> foobar". IMHO it's pretty useful that m.d.n's has an apt-get'able >> directory layout. >> > > dget is *way* faster, less trouble, and requires no root access. > > Why don't you include *both* options in the template, so that messages will contain both dget instructions and apt-get source instructions for mentors.debian.net, this way it will make things easy for those who prefer dget and for those who prefer m.d.n. -- "You know, of course, that the Tasmanians, who never committed adultery, are now extinct." -- M. Somerset Maugham Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: KildClient - Powerful MUD client with a built-in Perl interpreter
Dear mentors, I am looking for a sponsor for my package "kildclient". * Package name: kildclient Version : 2.5.0 Upstream Author : Eduardo M Kalinowski * URL : http://kildclient.sf.net * License : GPL Section : games The package is lintian and linda clean, and builds fine on pbuilder. The upload would fix these bugs: 303635 Package files can be downloaded from http://kildclient.sourceforge.net/debian/ or dget http://kildclient.sourceforge.net/debian/kildclient_2.5.0-1.dsc I would be glad if someone reviewed and/or uploaded this package for me. TIA, Eduardo M Kalinowski -- There goes the good time that was had by all. -- Bette Davis, remarking on a passing starlet Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to register manpages?
Michelle Konzack wrote: > Hello, > > I have for all of my tools/packages manpages (de and fr too) and > using dh_installman wich works perfectly. > > Now I have read I must register manpages from the "postinst" script. > > How can this be done? > What exactly do you mean with "registering manpages"? You only need to copy them to the appropriate directory, depending on the section, and man(1) will find them. -- If you teach your children to like computers and to know how to gamble then they'll always be interested in something and won't come to no real harm. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Recurring "please do" patterns in debian-mentors
Sune Vuorela wrote: > On 2007-01-01, Nico Golde <[EMAIL PROTECTED]> wrote: > >> I guess not since this is not defined in the policy. Maybe=20 >> if Homepage becomes a real control field. >> > > with two spaces it is formatted on the web like this: > http://packages.debian.org/unstable/kde/yakuake > > with one space like this: > http://packages.debian.org/unstable/kde/kfolding > > frontends format it different wether it starts with one or two spaces. > > I don't know about you, but to me the one-space style looks much better, at least in the web frontend. The whole description has a more consistent appearance, and I personally find monospaced fonts much uglier. -- He's like a function -- he returns a value, in the form of his opinion. It's up to you to cast it into a void or not. -- Phil Lapsley Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: gtkimageview
Carl Fürstenberg wrote: > Dear mentors, > > I am looking for a sponsor for my package "gtkimageview". > > The package is lintian clean. > It has two linda warnings: > W: libgtkimageview0-dev; File gtkimageview.devhelp not symlinked to > from devhelp dirs > The file shown above exists outside of /usr/share/gtk-doc/html or > /usr/share/devhelp/books, and does not symlink back into either of > those two directories > W: libgtkimageview0; Long descriptions contains short description. > The long description of this package contains the short description. > This is a bad idea, as the long description should be long, and not > just reiterate the short description. > I'm no DD, but I'd recommend fixing these warnings --- the second one is surely very easy to fix. As for the first, I can't help you much as I've never dealt with that. -- A jury consists of twelve persons chosen to decide who has the better lawyer. -- Robert Frost Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: package that depends from non-free package
Francesco Namuri wrote: > Hi, > I'm trying to make a package that depends on xmame that is in non-free, > the program under GPL and so I think it can uploaded to main, but how to > manage the dependency on xmame? > > If a free package depends on a package of non-free, then this package belongs to contrib: http://www.debian.org/doc/debian-policy/ch-archive.html#s-contrib (And see above under Main too.) -- Revenge is a form of nostalgia. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS/RFC: sketch - 3D line drawings from scene descriptions
David Bremner escreveu: Dear mentors, I am looking for a sponsor for my package "sketch". It builds these binary packages: sketch - Produce 3D line drawings from scene description language I'd change the short description to mention that this program is meant to be used with latex, outputting tikz or pstricks code. And I hope this program gets into Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: iceweasel-firegpg -- an iceweasel extension to use gnupg in web pages
Eriberto wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Stew! I think when a software has multiples optional licenses, I must to choose one. The license file says: "Alternatively, the contents of this source code may be used under the terms of either the GNU General Public License Version 2 or later (the "GPL"), or the GNU Lesser General Public License Version 2.1 or later (the "LGPL"), in which case the provisions of the GPL or the LGPL are applicable instead of those above. If you wish to allow use of your version of this source code only under the terms of either the GPL or the LGPL, and not to allow others to use your version of this source code under the terms of the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the GPL or the LGPL. If you do not delete the provisions above, a recipient may use your version of this source code under the terms of any one of the MPL, the GPL or the LGPL." The last paragraph shows that if one chooses neither license, the triple license keeps valid. -- QOTD: "Unlucky? If I bought a pumpkin farm, they'd cancel Halloween." Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: megazeux
Alistair John Strachan wrote: Dear mentors, I am looking for a sponsor for my package "megazeux". [snip] NOTE: This package is intentionally native as I am both the author of the MegaZeux program and the Debian package maintainer Unless the package really is something that only applies to debian (which does not seem the case), this is not a reason for the package to be native. Make it non-native and also don't ship the debian/ subdirectory in the source tarball. It's a bit more trouble, but it's worth it. -- intoxicate <--> excitation -- anagrama Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debiandoc2html
David Schulberg wrote: Hi, Have taken a documentation package and trying to make it I get an error ‘debiandoc2html: command not found’. What am I missing? You're missing the package with the debiandoc2html command. A quick search reveals that you need the 'debiandoc-sgml' package. -- Cheap things are of no value, valuable things are not cheap. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#470887: RFP: bibus -- bibliographic and reference management software
Charles Plessy wrote: Package: wnpp Severity: wishlist Package name: bibus Version : 1.4.1 Upstream Author : Pierre Martineau <[EMAIL PROTECTED]> URL : http://bibus-biblio.sourceforge.net License : GPL-2+ Programming Lang: Python Description : bibliographic and reference management software Bibus is a bibliographic database entirely written in python that uses the cross-platform wxWidget library. Bibus has been developed with OpenOffice.org (http://www.openoffice.org/) in mind and can directly insert citations and format the bibliographic index in an opened Openoffice.org writer document. Personnal comment: As a user, I really like Bibus. I find it easier to use and more stable than its proprietary competitor, EndNote. Upstream author is responsive and packaged Bibus as a Debian native pacakge. In the following SourceForge bug, he invites people to finish the work and make bibus an official Debian package. As this is not a Debian-specific package, it should not be a native package. Please repackage it as a non-native package. -- What is the robbing of a bank compared to the founding of a bank? -- Bertold Brecht Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Regarding package installation
On Fri, Apr 11, 2008 at 10:29 AM, Zainab Rehman <[EMAIL PROTECTED]> wrote: > > While running commands(red coloured font) to install a source package i am > having problems (bolded text) > > > > debianabc:/home/fast# cd debian > debianabc:/home/fast/debian# apt-get source bnfc > Reading package lists... Done > Building dependency tree... Done > E: You must put some 'source' URIs in your sources.list > debianabc:/home/fast/debian# apt-get build-dep bnfc > Reading package lists... Done > Building dependency tree... Done > E: You must put some 'source' URIs in your sources.list > debianabc:/home/fast/debian# cd bnfc2.2 > bash: cd: bnfc2.2: No such file or directory > debianabc:/home/fast/debian# cd bnfc-2.2 > debianabc:/home/fast/debian/bnfc-2.2# debuild -uc -us > bash: debuild: command not found > debianabc:/home/fast/debian/bnfc-2.2# The messages are pretty explanatory. (You even marked the ones that need some atention.) Add deb-src lines to the /etc/apt/sources.list file pointing to the source repositories. You also need the package with debuild. (I don't remember if there is a package only for 'debuild' or if it is part of another, so you'll have to search.) BTW, unless you are packaging bnfc (which does not seem to be the case), this is not the best mailing list for the question. Try debian-user. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to request package rebuild?
I'm the maintainer (but I'm not a DD) of the KildClient package, which uses libperl. Recently a new version of the package has been uploaded to the archive. However, for some of the architectures (the ones in which the build started first, as it seems) the package was build with version 5.8 of libperl, but for others it was built using the latest version, 5.10, as can be seen from http://packages.debian.org/sid/kildclient . However, libperl5.8 and libperl5.10 cannot both exist simultaneously because both depend on different versions of perl-base. Thus the packages that depend on libperl5.8 are not installable once Perl is upgraded to 5.10. There is even a bug report about this (#480499), even though it was reported against the version currently in testing (Perl 5.10 is only in unstable). I've built the program against libperl5.10 and saw that it works fine, no changes to the program are necessary, nor to the debian package. The only thing I need is to request a rebuild of the packages from source in the four affected architectures (i386, kfreebsd-amd64, kfreebsd-i386, m68k), which will pull the latest version of libperl from unstable, 5.10. How can I arrange so that it is done? -- Hanging on in quiet desperation is the English way. -- Pink Floyd Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: swac-get & swac-explore
nico wrote: > Dear mentors, > > I am looking for a sponsor for my packages "swac-get" and "swac-explore". > (I wrote about them in my mail "swac-tools - software for Audio > Collections of Words") > > Swac-get: > = > * Package name: swac-get > Version : 0.3-1 > Upstream Author : [fill in name and email of upstream] > * URL : [fill in URL of upstreams web site] > * License : [fill in] > That would be a nice place to start. Try also to provide the full description of the package, it helps potential sponsors to decide if they will take a look at the package. -- O Sol é 330.330 vezes maior que a Terra. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: New Packager question again: can you point me to a not flawed package?
Paul Johnson wrote: > So in my usual process of package development, I'd have the original > source, a modified source tree, I'd run "diff -rc orig source > > whatever.patch" after making specific changes and I'd collect those > up. > > Here are some example. GCC's version of objective C has become more > strict in its interpretation of methods and return arguments. It > generates warnings and errors where it did not do so in the past. To > fix those, I have to go in the source and tighten up some things. > Those changes need to be in a separate patch in order to allow the > developer to approve the changes I make. > > Here's another example. We've been using a graph library a long time, > at least 12 years. The developer seems to go missing for months at a > time. We don't make changes in his source, rather we collect up > patches representing changes we think are needed, and we use the > software. He's uninterested in packaging for Debian, Redhat, or > whatnot. If we collected up all those little changes into one massive > diff.gz, there's no way he'd have the patience to wade through it. > > If the person who is doing the actual software development makes a > Debian package, I say hooray, that person can do whatever the hell > she/he wants inside the code. That is what developers do. Packagers, > on the other hand, should not make unaccountable changes. > It is certainly preferable to use a patch system such as dpatch or quilt to register Debian-specific changes. However, it is not mandatory to do that, and it's unlikely to change in the future. So I'd recommend that you do use the patch system in the packages you create. You can't go wrong doing that. As for those who don't, they probably have their reasons. Sometimes a patch system is an overkill, and it's OK to make the changes directly in the .diff.gz that constitutes the source package. In some cases it could be the case that a patch system would make the package better to manage, but there isn't much that can be done except for contacting the maintainer and offering help to convert to a patch system --- with no guarantees that he will accept. However, note that both methods keep the original upstream source tarball (distributed along the .diff.gz in the package) intact. Changes are made to a local extracted copy used when the package is actually built. I cannot give an example of a package that only changes the source via a patch system, nor point you to good documentation (but I'm sure it exists) because the package I maintain does not need patching the sources. But if you need to alter the source, you can use the patch system (even if you are not required to). -- A beautiful man is paradise for the eyes, hell for the soul, and purgatory for the purse. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: atmailopen (2nd attempt - updated description)
Eugene V. Lyubimkin wrote: > > Description: elegant and intuitive ajax webmail client written in php > [snip] > > Kind regards > > Giuseppe Iuculano > > > Debian developers reference suggest not no put "written in " > into one-line > descriptions - it is useless for users to know what language the > program written in. In this particular case, it actually can be useful, since it's a web application to be run in a web browser, which will need support for the particular language. Naturally, the same can be guessed from the package dependencies, but especially if it were something more exotic than PHP, the information is not as useless as when it is given for a compiled program used directly by the users. -- Distrust all those who love you extremely upon a very slight acquaintance and without any visible reason. -- Lord Chesterfield Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: atmailopen (2nd attempt - updated description)
Ben Finney wrote: > Eduardo M KALINOWSKI <[EMAIL PROTECTED]> writes: > > >> Eugene V. Lyubimkin wrote: >> >>> Debian developers reference suggest not no put "written in >>> " into one-line descriptions - it is useless for users >>> to know what language the program written in. >>> >> In this particular case, it actually can be useful, since it's a web >> application to be run in a web browser, which will need support for the >> particular language. >> > > I've never needed PHP support in my web browser to use web > applications written in PHP. > > Perhaps you mean the web *server* needs PHP support? > Sure, it was a typo. And I meant that from the server admin's point of view, it he who will be installing the package, not the users. -- Nem que eu tivesse dois pulmões eu alcançava essa bola. -- Bradock, amigo de Romário reclamando de um passe longo Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mentors.debian.net SSL certificate under Ubuntu?
Andreas Schildbach wrote: > Hi there, > > Surfing to on my Ubuntu Hardy machine > > https://mentors.debian.net/ > > gives me the error > > mentors.debian.net uses an invalid security certificate. > The certificate is not trusted because the issuer certificate is > unknown. > (Error code: sec_error_unknown_issuer) > > What is the recommended and most secure way to have the SSL certificate > installed on Ubuntu Hardy (which I use for Debian packaging)? > Which browser? Iceweasel pops a dialog box (2.x) or shows information in the main display area (3.x) that allows you add that certificate to your list of trusted certificates so the warning does not appear again. -- Get a grip <--> Great pig -- anagrama Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: dagger
Stephan Windmüller wrote:
> I changed the control information to:
>
>
>
> Description: utility which tags and renames audio files
> dagger is a command line utility written in Python which tags and renames
> audio files. Currently supported formats are MP3 and Ogg Vorbis. dagger's
> configuration file supports different profiles with their own sets of
> options.
>
>
>
Going further, you can drop 'written in Python', as the language in
which the program is written is not really relevant to the user in most
of the cases.
--
You can fool all the people all of the time if the advertising is right
and the budget is big enough.
-- Joseph E. Levine
Eduardo M KALINOWSKI
[EMAIL PROTECTED]
http://move.to/hpkb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lintian warning messages
Richard Hurt escreveu: W: : script-non-executable -- Since this is a scripted web application (RoR) there are quite a few "scripts" that are not executable directly in the shell. Can I turn this warning off for these files? If the scripts are not directly executable, you can remove the #! line from them. That should make the warning go away. It would be better to talk with upstream so he does that. Meanwhile, patches can be used, but I don't think this warning is grave enough to make that a necessity. W: : extra-license-file -- There are several LICENSE files scattered throughout the package and I have documented them in the copyright file. Do I need to do anything with these? Should I remove them or is there a way to ignore them? If they are common licenses, they shouldn't be part of the resulting package. If the package uses make install and they are installed as part of that, you can rm them after that line so they do not appear in the package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lintian warning messages
Joey Hess wrote: > Eduardo M KALINOWSKI wrote: > >> If the scripts are not directly executable, you can remove the >> #! line from them. That should make the warning go away. >> It would be better to talk with upstream so he does that. >> > > If I were upstream and was pestered by a distribution to remove the > hashbang lines that I add to all code files as a matter of course > (because it's the most portable way to tell editors what type of code it > is), and their rationalle was that an internal tool in the distribution > was complaining about it, I'd be hard pressed to not laugh in their > face. > If the policy suggestion that leads to that lintian warning is so unreasonable, it might as well be taken off the policy. > Lintian has overrides so that you can turn off this type of warning, > which is useful in detecting scripts that were accidentially not > installed executable, but that has a large number of false positives. > Except, perhaps, from scripts which end up installed in the directories in the path. For scripts that are not in the path (and even if the execute bit set can only be executed with extra measures from the user) it should not matter whether they have a shebang or not. -- BOFH excuse #312: incompatible bit-registration operators Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Lintian warning messages
Joey Hess wrote: > Eduardo M KALINOWSKI wrote: > >> If the policy suggestion that leads to that lintian warning is so >> unreasonable, it might as well be taken off the policy. >> > > I'm not aware of any such thing in policy Then maybe the lintian warning could be removed. -- BOFH excuse #376: Budget cuts forced us to sell all the power cords for the servers. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: No sponsor found for weeks, what to do now?
Andreas Schildbach escreveu: > Hello everyone, > > I have created and uploaded (to mentors.debian.net) two Debian packages > some weeks ago, and have advertized them on this group. However, until > now, no sponsor was looking after the packages. > > I'd like to know what to do now? Just wait? Starting to personally > e-mail Debian developers I happen to know? > > The packages in question: > > phpmyid - standalone, single user, OpenID identity provider > http://mentors.debian.net/debian/pool/main/p/phpmyid > > wordpress-openid - OpenID consumer plugin for WordPress > http://mentors.debian.net/debian/pool/main/w/wordpress-openid > I'd recommend periodcally (say, once in a month) reposting the RFS to the list, to see if it catches the eye of someone. Sometimes it takes time, but eventually you should find a sponsor. Also, for packages for which there is a team (games, perl, science and others that I don't recall), try posting to the team's mailing list, or get in contact with members of the team in some other way. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC: QA vs NMU on ssystem - 3D solar system simulator
Paul Gevers wrote: > Hello mentors, > > I like some comments on the following: > > I made some small changes to an orphaned package (ssystem), to fix a bug > (#482936) and to fix some lintian errors/warnings. I understand that > this should be a QA upload because QA is maintainer, but I might be > wrong and that this should be a NMU. Am I right? Because upstream is > dead, I don't know if I should adopt it, I don't know much about C yet. > The program is pretty old, but apparently a lot leaner on processing > power than it's descendant called celestia. > > Further, there is one lintian warning left: > I: ssystem: arch-dep-package-has-big-usr-share 1224kB 83% > I can (easily) fix this, but that way I change the package more than I > think is appropriate for QA. What do others think? Should I fix this as > well? > As far as I understand, if the package is orphaned, you could do that change in the package, it would not be considered too 'abusive'. But you do not have to, fixing only the bug is already a good contribution. However, even if 83% of the package is architecture independent data, the whole package uncompressed only takes about 1,5Mb, and the whole compressed package is 'Mb. Even considering all the architectures, the space saved in mirrors and in bandwidth transferred is not so big, and IMHO does not justifies two separate packages (ssystem and ssystem-data). -- mother-in-law <--> woman Hitler -- anagrama Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: quick-lounge-applet, must I contact debian-release?
Diego Fernández Durán escreveu: > Hi, > > I'm very new in this and the maintainer of quick-lounge-applet. > > quick-lounge-applet is in freeze, the version in testing is 2.12.1 and in > unstable 2.12.5. The new version doesn't fix any major bug. > > Must I contact debian-relase to request the package update? > No, and if you did your request would probably be denied (freeze exceptions are for bug fixes, not general updates). Lenny will have 2.12.1, the new version will have to wait until Lenny+1. -- Eduardo M Kalinowski [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SCons.
Alessio Giovanni Baroni wrote: > Hi to all, > the drqueue package use SCons as build system. The drqueue package > actually on > Debian no. I must to reconfigure the packge to use standard build > system? (autoconf/automake) No, add scons to the Build-Depends:, and then in debian/rules call the necessary commands to build with scons. -- Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: literally '?' in debconf template
markus schnalke wrote: > Hello mentors, > > lintian reports this warning: > using-question-in-extended-description-in-templates > (see [1]) > > But there is no question where lintian sees one. Instead it's a > literally question mark. The text is: > "You can use wildcard expressions like '*' or '?'." > > How can I solve the situation? > Is there a way to escape the questions mark? > Do I have to override the warning? > I'd add an override for this case, seems the easiest way. -- I'm a gnus person myself. It's an editor! It's a floorwax! It's a dessert topping! Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian policy, a problem or a misunderstand ?
Ben Finney wrote: > Laurent Guignard <[EMAIL PROTECTED]> writes: > > >> [...] >> It is also important, of course, that *they don’t exit with a non-zero >> status if everything went well.*" >> > >> How do i have understand that ? >> > > Perhaps the double negatives are confusing you. > They are confusing indeed. It would be better if it was written "... that they exit with a zero return status if everything went well." Comments, your could a wishlist bug be filled suggesting this wording change? -- Your program is sick! Shoot it and put it out of its memory. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: fig2sxd
Alexander Bürger wrote: > Ouch, I sent my last mail too early. I wanted to add that: > > >> No. I say that uploading in unstable a version that will never go in >> testing because of the freeze would put some difficulties on you if you >> need to upload a fix (a small fix that would be 0.18-2 for example). >> > > I do not understand why will it never go in testing? I expected it would > go there after the next release. > The 'never' in that sentence does not mean forever, but only while the freeze is active. :-) After lenny is released, updates start to go to testing, which will eventually become the next release. -- Your password is pitifully obvious. Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Average time to get an answer about package sponsoring
Laurent Guignard wrote:
> Hi mentors,
>
> I would like to know the average time to get an answer from the upload
> of the package on "mentors.debian.net" and an answer a mentor.
> After one month could i have any information about all errors i made in
> my package and anything else about ?
> Is this a normal time ?
As Michael said, if you have not send a mail with the usual RFS template
to this list, you should do so.
However, even with the list warned about your package, there is no
expected time to get replies. Some packages get reviewed/sponsored very
fast, others take a long time and several posts to the list. It all
depends on whether a potential sponsor sees the mail and becomes
interested in the package.
--
Don't everyone thank me at once!
-- Han Solo
Eduardo M KALINOWSKI
[EMAIL PROTECTED]
http://move.to/hpkb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Someone to 'proofread' a .deb please
Andy Hawkins wrote:
> I'll look at getting it packaged up tomorrow and uploaded to 'mentors'. Is
> the request for sponsorship automatic? Or is there an 'approved' format?
>
No, you'll have to post a request here on the list. I believe the site
provides a template (that unfortunatelly does not ask for the detailed
description, which you should include). Or search the archives of this
list for RFS messages.
--
If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system.
-- Linus Torvalds
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
http://move.to/hpkb
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Debian etch - Rebuilding a package from source.
Chris Jones wrote: What I have done so far is pretty much what is describe in the above: . apt-get source .. . build-dep .. . debuild .. . dpkg -i .. The process appears to work - as tested on gnu/screen - when I'm just recreating the same deb that I would install via apt-get. That's a good procedure. It's what I do when I need to rebuild a package. One problem, though, is that since the build is pretty much automated, I'm not sure how I could add --xxx configure options that override the defaults. In particular after reading the man page I wasn't able to find an option that would let me achieve this. The configure script gets called in debian/rules. Editing the file you should be able to find a call to it and modify appropriately. Another concern is what kind of naming standard I should/could adopt for my custom .debs so that they integrate smoothly with the apt packaging system. In other words.. in a way that will be easy to manage over time and not interfere with possible future apt-get actions, such as upgrades to a new release etc. One possibility is to increase the package revision and append something like '~yourname0'. If the package is 1.4.5-3, you make 1.4.5-4~something0, which is greater than 1.4.5-3 but smaller than 1.4.5-4 or any newer upstream version. But there are other possibilities regarding suffixes. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: What to do if the original tarball contains a debian subdirectory
Luca Niccoli wrote: > A related question: > The original debian/ contains a changelog, which documents the past > releases (packaged in .deb for i386 by upstream); should I get rid of > that or keep it/import it? > I'd say it depends on what you are doing. If you are building on the work already there, keep the changelog. But if you are ignoring upstream's debian/ directory and starting your packaging from scratch, you can drop it. -- System checkpoint complete. Eduardo M KALINOWSKI edua...@kalinowski.com.br http://move.to/hpkb -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: What to do if the original tarball contains a debian subdirectory
Dmitrijs Ledkovs wrote: > 2009/1/29 Eduardo M KALINOWSKI : > >> I'd say it depends on what you are doing. If you are building on the >> work already there, keep the changelog. But if you are ignoring >> upstream's debian/ directory and starting your packaging from scratch, >> you can drop it. >> >> > > By keep the changelog you mean add my own new changelog entry at the > top of the file as if it was the debian changelog? > Wasn't it a debian/changelog file, describing the releases upstream has made? -- Never commit yourself! Let someone else commit you. Eduardo M KALINOWSKI edua...@kalinowski.com.br http://move.to/hpkb -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Licensecheck returns UNKOWN, but it's GPL
Luca Niccoli wrote: > Two of them are actually kernel headers, I think from an old 2.4 version. > Now, I tried removing them and build depending on linux-headers-2.6, > it works fine. > I guess upstream wouldn't be happy to ask his users to install the > whole kernel headers, just to compile that tiny package; what is the > correct way to deal with this, repackage orig.tar.gz? > Not necessary in this case. > Or just patch the source not to use the headers included in the > tarball is enough? > That's the way to do it. Preferably using a patch system. And build-depend on the package with the kernel headers. > Sticking with the files provided buy upstream makes the compilation a > far less painful activity (no time and space wasted for unpacking > kernel headers), but I think it's reckoned a Bad Thing... > You could try talking to upstream about removing those files. It's not really a nice idea. If the kernel API changes, one might be able to compile with the old provided headers, but the module will crash. Using the latest kernel headers compilation will be correct if possible, or fail if some incompatible change was introduced, which is better than being able to compile something that will not run and possibly crash the machine. > As of the third file without copyright statement, it comes from > project non packaged in debian. > Is appending a note to debian/copyright about the author of that file ok? > If it's GPL or any other license that is OK (and compatible with the other licenses of other files), yes. -- Genetics explains why you look like your father, and if you don't, why you should. Eduardo M KALINOWSKI edua...@kalinowski.com.br http://move.to/hpkb -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Fixing old-fsf-address-in-copyright-file
Ben Finney wrote: > If we distribute a package with ‘debian/copyright’ so that it > deliberately differs from upstream in this regard, are we not > violating policy §12.5 “Every package must be accompanied by a > verbatim copy of its copyright and distribution license in the file > `/usr/share/doc//copyright'.”? > IANAL, but I don't think the address is part of the license. I believe the address can be changed to reflect the correct information, if the rest of the license information is kept. -- 15% gratuity added for parties over 8. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: fsprotect
Stefanos Harhalakis wrote: > I'll add it when it is available. Since this is a debian native package, I'm > waiting for it to enter debian (if it ever happens) before creating a page. > Whis is this native? From what I understood of the package, there is nothing Debian-specific in this package, why couldn't it be used in other distributions? -- All truths are true to an extend, including this one. -XA Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: mpg321 (updated package)
From: Elías A. M. > Ok, I will take it into account. But first I would like first, the upstream > author's opinion or some mentor. > I think may be: popular command-line mp3 player > (according to: http://mpg321.sourceforge.net/) I'd use just "command-line mp3 player". "popular" sounds like advertising and adds nothing. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: ripit (updated package)
Elimar Riesebieter wrote: > * Neil Williams [090426 13:50 +0100] > >> The RFS wasn't sufficiently interesting. >> >> http://people.debian.org/~codehelp/#lang >> >> Tell sponsors why they should care about the package - your initial RFS >> was bare, incomplete and just plain uninteresting. >> > > Hey, my package is an update. > You didn't say that clearly in the first message. Nevertheless, tt still helps to say something about the package. At least its long description. -- < doogie> asuffield: how do you think dpkg was originally written? :| < asuffield> by letting iwj get dangerously near a computer -- in #debian-devel Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
Hai Zaar wrote: > Can you please advice on how to create "orig" package, when debian dir > is part of the project file-tree? Do I need to checkout sources and > then just delete debian subdir, pack orig tarball, then restore debian > dir and proceed? > I don't know how you are creating the tarball, but if you are using automake et al., the debian/ directory will only be part of the tarball if you ask it to be. Just leave it out, and a 'make dist' will create a tarball only with upstream sources. -- You are taking yourself far too seriously. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libapache2-mod-authnz-external
On Seg, 11 Mai 2009, Hai Zaar wrote: On Mon, May 11, 2009 at 5:21 PM, LI Daobing wrote: comments: 1. lintian warning: W: libapache2-mod-authnz-external source: dh-clean-k-is-deprecated 2. no debian/watch 3. how about add Homepage field in debian/control? All fixed. Reuploaded. How come my lintian -viI does not show this warnings? You're probably running an older version of lintian. You should use the one from debian unstable. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: change glib-config to pkgconfig in configure.in
On Sex, 15 Mai 2009, Francesco Namuri wrote:
Hi,
I'm trying to solve bug #523713, it regards pmidi package, the problem
is that the build depends on glib 1.2 that is going to be removed from
unstable. I've seen that the program compiles fine with glib 2.0, but
the configure look only to 1.2 version using the glib-config tool.
Now, I've managed to solve this problem changing these lines in
config.in
from:
if test "$included_glib" = "auto" || test "$included_glib" =
"no"; then
AC_PATH_PROG(GLIBCNF, glib-config, true, $PATH)
CFLAGS="$CFLAGS `$GLIBCNF --cflags`"
LIBS="$LIBS `$GLIBCNF --libs`"
WITH_INCLUDED_GLIB=0
AC_SUBST(GLIBCNF)
fi
to something like:
if test "$included_glib" = "auto" || test "$included_glib" =
"no"; then
AC_PATH_PROG(GLIBCNF, glib-config, true, $PATH)
CFLAGS="$CFLAGS `pkg-config --cflags glib-2.0`"
LIBS="$LIBS `pkg-config --libs glib-2.0`"
WITH_INCLUDED_GLIB=0
AC_SUBST(GLIBCNF)
fi
There is an easier way, you can use the PKG_CHECK_MODULES macro:
PKG_CHECK_MODULES(PKGNAME, glib)
This checks for pkg-config, checks that glib is installed, and sets
the variables PKGNAME_CFLAGS and PKGNAME_LIBS to the necessary flags
and libraries. Then you can, for example, call
AC_SUBST(PKGNAME_CFLAGS)
AC_SUBST(PKGNAME_LIBS)
and access the flags in ${PKGNAME_CFLAGS} and ${PKGNAME_LIBS} in the Makefile.
--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [OT] C (was: QA uploads primer)
On Ter, 16 Jun 2009, Stefanos Harhalakis wrote:
[snip]
Of course you need to look at the C spec to
claim that you understand C in depth (you did... didn't you?) and in order to
understand why
int n=1; int main() { n=n; printf("%d", n); }
will not output '1'
[snip]
I couldn't figure why it wouldn't output 1, so I tried (with gcc
4.2.3) and it did print "1". :-) Surely it complains about printf not
being defined previously, but it works and since the parameters happen
to be correct (even though the compiler does not know that), the
correct output is printed.
So I'm still curious why you say it would not work. Care to explain?
--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [OT] C (was: QA uploads primer)
On Qua, 17 Jun 2009, Stefanos Harhalakis wrote: I meant that they are not very popular and that they are not covered in most books or tutorials. Thus, it is not obvious that this: I'd say they are not covered because they were never popular, and nowadays they are basically unnecessary. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: djmount
On Dom, 09 Ago 2009, Ben Finney wrote: You mean, the list should lie about the author of messages so that when you use the “reply to author” feature, it doesn't go only to the author? No, that's not a viable option. It doesn't need to change the author, only the "reply to" field. And yes, I've read "reply to considered harmful". Spare your links. And I'm not advocating it, I'm just saying what would be changed. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: immv
On Seg, 24 Ago 2009, Marco Herrn wrote: I know of the lintian warning about this package, that upstream sources don't differ from debian sources. The reason is that I am the upstream author and it is convenient for me to store the /debian in the same repository as the programs source. It's fine to keep the debian subdirectory in the same repository as the source. But it is preferred not to include it in the tarball, so that the debian-specific information in contained in the .diff.gz file. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Test of a package on a specific architecture
Benoit Mortier wrote: > Hello, > > You can run 64bit system on virtualbox on a 32bit cpu. I'am doing it to > compile stuff for amd64. For this to work you have to have vt extensions > on your cpu and virtualbox 2.2.0. > > see: > > model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz > > just activate those options on virtualbox > This is a 64-bit capable processor. You could run a 64-bit system directly if you wanted to. Since qemu is an emulator, it should be able to run 64-bit guests in a 32-bit system, even with vt support in the processor. But it probably would be somewhat slow. -- May a Misguided Platypus lay its Eggs in your Jockey Shorts. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS:openpref
tangke wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "openpref".
>
> openpref - OpenPref is open source game
>
I did not look at the package, but let me start by pointing out that
this description is essentially useless.
First, no need to mention that it's open source. All software in Debian
conforms to Debian notion of open-source, so it's redundant.
It's also preferable not to repeat the package name in the short
description.
And, most importantly, what kind of game? Try to briefly describe the
game so that users have at least a basic idea.
There is a games team, you might find a sponsor there more easily.
--
I am not afraid of tomorrow, for I have seen yesterday and I love today.
-- William Allen White
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760065: RFS: kildclient/3.0.0-1 [new upstream version of package already in Debian]
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "kildclient"
* Package name: kildclient
Version : 3.0.0-1
Upstream Author : Eduardo Kalinowski
* URL : http://www.kildclient.org
* License : GPL-2+
Section : games
It builds those binary packages:
kildclient - powerful MUD client with a built-in Perl interpreter
kildclient-doc - powerful MUD client with a built-in Perl
interpreter - manual
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/kildclient
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/k/kildclient/kildclient_3.0.0-1.dsc
Changes since the last upload:
* New upstream version: 3.0.0.
* control: Updated VCS urls.
* control: Reintroduced Homepage field that was lost and made it point
to the new URL.
* copyright: Point to new homepage.
* control: New dependency: libjson-perl
* control: glib >= 2.32.0, gtk+3 >= 3.10.0 and gtkspell3 are now
required. gtk3-perl is suggested instead of gtk2-perl.
* control: Use debhelper 9.
* control: Mentioned HTTP proxies in description.
* control: Updated Vcs fields to point to new git repository.
* control: Updated policy compliance to 3.9.5; no changes were
necessary.
* rules: Added hardening flags.
* control, rules: dh-autoreconf is now used instead of autotools-dev.
* copyright: Change URL of Format: line to point to Version 1.0 of the
machine-readable format.
* copyright: util_cursor.h is no longer used, so it has been removed.
--
It is impossible to travel faster than light, and certainly not desirable,
as one's hat keeps blowing off.
-- Woody Allen
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/540313e9.6020...@kalinowski.com.br
Bug#760065: RFS: kildclient/3.0.0-1 [new upstream version of package already in Debian]
On Seg, 01 Set 2014, Eriberto Mota wrote: 1. d/changelog: add ACK for NMU. See details here[1]. I included the NMU changelog entry in debian/changelog (after my changes), is something else necessary? 2. d/rules: please, update to new (reduced) format. Ask me if you have doubts. An example is here[2]. For details, see the 'dh' manpage. 3. d/rules: add 'export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed' to solve these warnings: I'll be working on these items and will soon upload a new version. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140902181602.horde.xh1zpypdj6v0mwgadecs...@mail.kalinowski.com.br
How to acknowledge NMU
(This discussion started here[0], but I'm bringing it to a new thread in hope it's seen by a wider range of people.) [0] https://lists.debian.org/debian-mentors/2014/09/msg00034.html How to proper acknowledge a NMU? As described, I included the NMU version changelog in debian/changelog after the new version I'm preparing. From the devref, this appears to be all that's necessary, at least in my interpretation. But there are some cases (see [1], for example), albeit older, that add an entry in the changelog explicitely acknowledging it and closing the bug. [1] http://metadata.ftp-master.debian.org/changelogs/main/g/gconjugue/unstable_changelog So what's really necessary? Thanks, -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905144840.horde.ln2bhxlj4j5xnrurvgan...@mail.kalinowski.com.br
Bug#760065: RFS: kildclient/3.0.0-1 [new upstream version of package already in Debian]
tags 760065 - moreinfo thanks On 08/31/2014 11:02 PM, Eriberto Mota wrote: > 1. d/changelog: add ACK for NMU. See details here[1]. > > 2. d/rules: please, update to new (reduced) format. Ask me if you have > doubts. An example is here[2]. For details, see the 'dh' manpage. > > 3. d/rules: add 'export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed' to > solve these warnings: I believe I have addressed all these issues, the update package remains at the same address: http://mentors.debian.net/package/kildclient or dget -x http://mentors.debian.net/debian/pool/main/k/kildclient/kildclient_3.0.0-1.dsc -- Due to a shortage of devoted followers, the production of great leaders has been discontinued. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/540aec26.5090...@kalinowski.com.br
Re: Can /usr/share/doc/ be deleted on upgrade ?
On Qui, 26 Nov 2009, "Lucas B. Cohen" wrote:
Esteemed Debian mentors,
Is it considered acceptable for a package to blindly delete, then
recreate its entire directory under /usr/share/doc upon installation or
upgrade ?
Although I probably will do a conditional backup of such a hypothtical
folder in {pre,post}inst anyhow ("polite" feels like better goal than
"acceptable"), I mostly raise this because it doesn't seem covered in
the FHS, Debian Policy or other maintainer-oriented material I've read.
The most related items I could find were:
- "Any program or package which contains or requires data that doesn?t
need to be modified should store that data in /usr/share" (FHS 2.3)
- "The system administrator should be able to delete files in
/usr/share/doc/ without causing any programs to break" (Debian Policy
12.3, footnote 7)"
In worse-case scenarios, these could be illogically interpreted as
explicit permission for a package to rule unilateraly on its doc directory.
Why exactly do you want to do that? What do you want to achieve?
I'm not sure that's allowed, but even if it is, there's probably a
better way to do what you want, if you explain us the reasons for
doing that.
--
You will think of something funnier than this to add to the fortunes.
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: parse error in changelog
On Seg, 21 Fev 2011, Lars Buitinck wrote: Hello, Can someone pinpoint the error in the changelog below: dbxml (2.5.16-1) unstable; urgency=low * Initial release (Closes: #573859) -- Lars BuitinckMon, 21 Feb 2011 14:30:22 +0100 When I run dpkg-buildpackage, I get the error parsechangelog/debian: warning: debian/changelog(l5): badly formatted trailer line LINE: -- Lars BuitinckMon, 21 Feb 2011 14:30:22 +0100 parsechangelog/debian: warning: debian/changelog(l5): found eof where expected more change data or trailer but I really don't see where it conflicts with the changelog format specification. Might be a missing new line if that's the last line. -- BOFH excuse #12: dry joints on cable plug Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110221105842.444169vf8mzzp...@mail.kalinowski.com.br
RFS: kildclient - A Powerful MUD client with a built-in Perl interpreter
I'm looking for someone to sponsor my program, KildClient. It is released under the GPL. I've been making .deb files since some upstream versions ago and putting them for users to download, but now I'd like to make the life of users simpler by adding KildClient to the Debian archive. Here's the program's description: KildClient is a MUD Client written with the GTK+ windowing toolkit. It supports many common features of other clients, such as triggers, gags, aliases, macros, timers, and much more. But its main feature is the built-in Perl interpreter. You can at any moment execute Perl statements and functions to do things much more powerful than simply sending text the the mud. Perl statements can also be run, for example, as the action of a trigger, allowing you to do complex things. Some built-in functions of KildClient allow interaction with the world, such as sending commands to it. More information can be found at http://kildclient.sf.net The package can be downloaded from http://kildclient.sourceforge.net/debian/ . -- "How do I love thee? My accumulator overflows." Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: kildclient - A Powerful MUD client with a built-in Perl interpreter
I'm looking for someone to sponsor my program, KildClient. It is released under the GPL. I've been making .deb files since some upstream versions ago and putting them for users to download, but now I'd like to make the life of users simpler by adding KildClient to the Debian archive. Here's the program's description: KildClient is a MUD Client written with the GTK+ windowing toolkit. It supports many common features of other clients, such as triggers, gags, aliases, macros, timers, and much more. But its main feature is the built-in Perl interpreter. You can at any moment execute Perl statements and functions to do things much more powerful than simply sending text the the mud. Perl statements can also be run, for example, as the action of a trigger, allowing you to do complex things. Some built-in functions of KildClient allow interaction with the world, such as sending commands to it. More information can be found at http://kildclient.sf.net The package can be downloaded from http://kildclient.sourceforge.net/debian/ . -- "How do I love thee? My accumulator overflows." Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
martin f krafft wrote: What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. What about the case in which the upstream maintainer is the Debian maintainer? I create packages for a piece of sofware I've written (and for which I'm looking a sponsor, see http://lists.debian.org/debian-mentors/2005/04/msg00106.html ). The debian/ directory is in CVS, naturally. It is currently distributed in the .tar.gz file. Should it be removed? This would make things more difficult for me, because in the case of a new version, I would need to untar the new .tar.gz file and then copy the debian/ directory from CVS. -- Are there those in the land of the brave Who can tell me how I should behave When I am disgraced Because I erased A file I intended to save? Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: kildclient - A Powerful MUD client with a built-in Perl interpreter
I'm looking for someone to sponsor my program, KildClient. It is released under the GPL. WNPP entry: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=303635 I've been making .deb files since some upstream versions ago and putting them for users to download, but now I'd like to make the life of users simpler by adding KildClient to the Debian archive. The package is lintian-clean. Here's the program's description: KildClient is a MUD Client written with the GTK+ windowing toolkit. It supports many common features of other clients, such as triggers, gags, aliases, macros, timers, and much more. But its main feature is the built-in Perl interpreter. You can at any moment execute Perl statements and functions to do things much more powerful than simply sending text the the mud. Perl statements can also be run, for example, as the action of a trigger, allowing you to do complex things. Some built-in functions of KildClient allow interaction with the world, such as sending commands to it. Kildclient supports the MCCP (Mud Client Compression Protocol) protocol, versions 1 and 2, to reduce the necessary bandwidth. More information at http://kildclient.sf.net The package can be downloaded from http://kildclient.sourceforge.net/debian/ . I'm requesting again because I didn't find a sponsor last time, there is a new upstream version and, following advice given in a recent thread, I've removed the debian/ subdirectory from the upstream tarball, and now it lies entirely in the .diff.gz file. -- "How do I love thee? My accumulator overflows." Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lintian: spelling
On Sex, 21 Out 2016, Jakub Wilk wrote: [Disclaimer: I'm not a native speaker of English.] * Jerome BENOIT , 2016-10-21, 01:36: is there a list where we can deal on how correct spelling error as detected by lintian ? For the curious. In the source, there is the sentence: :param int max_no_dec: number of rounds we allow to be stuck Lintian complains about "allow to" because "allow" requires an object, and in most cases[*] this object goes between "allow" and "to". But here, "number of rounds" is the object. IOW, this line could be paraphrased as: We allow $max_no_dec rounds to be stuck. Perhaps also "number of rounds allowed to be stuck". -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#847709: RFS: kildclient/3.1.0-1 [update of package already in Debian]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "kildclient" * Package name: kildclient Version : 3.1.0-1 Upstream Author : Eduardo Kalinowski * URL : https://www.kildclient.org * License : GPL-2+ Section : games It builds those binary packages: kildclient - powerful MUD client with a built-in Perl interpreter kildclient-doc - powerful MUD client with a built-in Perl interpreter - manual To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kildclient Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kildclient/kildclient_3.1.0-1.dsc Changes since the last upload: * New upstream version: 3.1.0. * Dropped fix-scroll-to-end patch, this change was incorporated upstream. * rules, control: The helpfile (kildclient.hlp) and html manual are now regenerated at build time from the XML source. New build-dependencies: docbook-xsl-ns, libxml-libxml-perl, xsltproc. * control: kildclient-doc is marked as Multi-Arch: foreign since it consists only of static documentation. * watch: Added support for GPG signature checking. * control: Require libgtk-3-dev >= 3.12.0. * control: liblocale-gettext-perl is no longer required. * kildclient-doc.doc-base: Updated path of index file (it now ends in xhtml), and adjusted Files field to include images and css. * menu: removed as per TC resolution of #741573. * Added upstream metadata. * copyright, control: Changed URLs to use https. * control: Updated policy compliance to 3.9.8; no changes were necessary. * control, compat, rules: Use debhelper 10. There are two minor lintian warnings: * vcs-field-uses-insecure-uri: Sourceforge does not offer annonymous https support for git. * no-upstream-changelog: There really isn't. I've also tested the package with pbuilder and piuparts and no problems were detected. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#847709: RFS: kildclient/3.1.0-1 [update of package already in Debian]
Control: tags -1 - moreinfo On 14-12-2016 14:34, Andrey Rahmatullin wrote: > On Sat, Dec 10, 2016 at 05:35:19PM -0200, Eduardo M KALINOWSKI wrote: >> * control: kildclient-doc is marked as Multi-Arch: foreign since it >> consists only of static documentation. > Actually kildclient is marked, not kildclient-doc. Oops. I've fixed the package and reuploaded to mentors. -- This restaurant was advertising breakfast any time. So I ordered french toast in the renaissance. -- Steven Wright, comedian Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#772743: RFS: kildclient/3.0.0-2 [Fixes important bug]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "kildclient" * Package name: kildclient Version : 3.0.0-2 Upstream Author : Eduardo Kalinowski * URL : http://www.kildclient.org * License : GPL-2+ Section : games It builds those binary packages: kildclient - powerful MUD client with a built-in Perl interpreter kildclient-doc - powerful MUD client with a built-in Perl interpreter - manual This upload fixes https://bugs.debian.org/772096 . I've asked for an unblock ( http://bugs.debian.org/772672 ), and received permission to upload to unstable. The debdiff between the version in testing and the new version is at https://bugs.debian.org/cgi- bin/bugreport.cgi?msg=17;filename=kildclient_3.0.0-1_to_3.0.0-2.diff;att=1;bug=772672 and corresponds to these changes: kildclient (3.0.0-2) unstable; urgency=medium * Added work-around to enable scroll-to-end feature to work with GTK+ >= 3.13. Closes: #772096 There's a lintian warning about outdated standards version, I did not fix it in order make the changes as small as possible as requested by the freeze policy. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/kildclient Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/k/kildclient/kildclient_3.0.0-2.dsc Thanks -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141210185808.29054.37584.reportbug@tyrion
Re: Dropping debian/ directory vs Continuous Integration / daily-debs
On Qua, 05 Ago 2015, Fabrice Aeschbacher wrote: I did also read on debian-devel that putting the debian/ directory in the same (git) repo has some drawbacks and is not recommended (at least not in the same branch). I cannot remember all arguments, but some can be found here : https://wiki.debian.org/DebianMentorsFaq#What.27s_wrong_with_upstream_shipping_a_debian.2F_directory.3F That is about having the debian/ directory in the tarball (which I understand is not recommended). You can keep the debian/ directory in the source control, just don't include it in the tarballs. That is even mentioned in the last paragraph. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150805115311.horde.kug1uoyum1jkymacgyft...@mail.kalinowski.com.br
Re: Bug#809623: RFS: telegram-purple/1.2.3-1
On 02-01-2016 19:08, Jakub Wilk wrote: > >> and how Russion plurals work(?!). > > The Russian PO file reads: > > Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 > && n%10<=4 && (n%100<12 || n%100>14) ? 1 : n%10==0 || (n%10>=5 && > n%10<=9) || (n%100>=11 && n%100<=14)? 2 : 3); > > Even though I don't speak Russian, I can tell that this Plural-Forms > can't possibly be correct. Here 4 plural forms are declared, but the > expression never evaluates to 3. > These links show expected plural forms: http://localization-guide.readthedocs.org/en/latest/l10n/pluralforms.html https://www.gnu.org/software/gettext/manual/gettext.html#Plural-forms They seem to agree on the expression for Russian. -- Landru! Guide us! -- A Beta 3-oid, "The Return of the Archons", stardate 3157.4 Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#885336: RFS: kildclient/3.2.0-1 [Updated version, fixes non-DSA CVE]
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "kildclient". This version
fixes a minimal impact CVE bug (that was considered as not needing a DSA
by the security team)
* Package name: kildclient
Version : 3.2.0-1
Upstream Author : Eduardo M Kalinowski
* URL : https://www.kildclient.org/site/
* License : GPL-2+
Section : games
It builds those binary packages:
kildclient - powerful MUD client with a built-in Perl interpreter
kildclient-doc - powerful MUD client with a built-in Perl interpreter -
manual
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/kildclient
Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/k/kildclient/kildclient_3.2.0-1.dsc
Changes since the last upload:
* New upstream version: 3.2.0.
- Fix for CVE-2017-17511. New dependency 'gvfs' required in order to
use GTK+ function for opening URLs. Closes: #885007
* control: Require libgtk-3-dev >= 3.22.0.
* control: Removed unnecessary dependency on dh-autoreconf, as debhelper
enables it by default.
* control: Use https:// instead of git:// for Vcs-Git.
* compat, control: Use compatibility level 11.
* rules: Support nodoc in DEB_BUILD_OPTIONS.
* control: Updated policy compliance to 4.1.2: the only change was the
support for nodoc as described above.
--
Truly great madness can not be achieved without significant intelligence.
-- Henrik Tikkanen
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
Great minds run in great circles.
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
RFS: kildclient (updated packages, fixes FTBS)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package "kildclient". * Package name: kildclient Version : 2.11.0-1 Upstream Author : me (Eduardo M Kalinowski) * URL : http://kildclient.sourceforge.net/ * License : GPL-2+ Section : games It builds these binary packages: kildclient - powerful MUD client with a built-in Perl interpreter kildclient-doc - powerful MUD client with a built-in Perl interpreter - - manual The package is lintian clean, and builds in pbuilder. This is an updated package, my usual sponsor (Christoph Haas) is busy at the moment and cannot upload it. It includes a new upstream version, DEP-5 copyright format, uses the new dpkg-source 3.0 (quilt format) and fixes FTBS bug #555000. The files are at http://kildclient.sourceforge.net/debian/, or just dget http://kildclient.sourceforge.net/debian/kildclient_2.11.0-1.dsc I would be glad if someone uploaded this package for me. - -- Alone, adj.: In bad company. -- Ambrose Bierce, "The Devil's Dictionary" Eduardo M KALINOWSKI edua...@kalinowski.com.br -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3G5CcACgkQJAYvFKXQ6TpiFwCcDDfuTHQZz+R0WXdsyullWmMf kIAAn2KhpMGWYQrh1LQLh8kb6j7EpRNQ =ejgR -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dc6e428.6070...@kalinowski.com.br
Re: RFS: kildclient (updated packages, fixes FTBS)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 05/08/2011 03:42 PM, Eduardo M KALINOWSKI wrote: > Dear mentors, > > I am looking for a sponsor for my package "kildclient". > > * Package name : kildclient Version : 2.11.0-1 Upstream > Author : me (Eduardo M Kalinowski) * URL : > http://kildclient.sourceforge.net/ * License : GPL-2+ > Section : games > > It builds these binary packages: kildclient - powerful MUD > client with a built-in Perl interpreter kildclient-doc - powerful > MUD client with a built-in Perl interpreter - manual > > The package is lintian clean, and builds in pbuilder. > > This is an updated package, my usual sponsor (Christoph Haas) is > busy at the moment and cannot upload it. It includes a new > upstream version, DEP-5 copyright format, uses the new dpkg-source > 3.0 (quilt format) and fixes FTBS bug #555000. > > The files are at http://kildclient.sourceforge.net/debian/, or > just dget > http://kildclient.sourceforge.net/debian/kildclient_2.11.0-1.dsc > > I would be glad if someone uploaded this package for me. Anyone? - -- The English country gentleman galloping after a fox -- the unspeakable in full pursuit of the uneatable. -- Oscar Wilde, "A Woman of No Importance" Eduardo M KALINOWSKI edua...@kalinowski.com.br -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3MNrUACgkQJAYvFKXQ6ToJ9gCglBlfIpCEO8syopxpXpP2nckV YrQAoImzUYPICtPcdDWmGKl5GDoFL7i+ =upHZ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dcc36b5.4010...@kalinowski.com.br
Re: RFS: kildclient (updated packages, fixes FTBS)
On Sex, 13 Mai 2011, Asheesh Laroia wrote: what I suggest is that you: * Prepare a tiny hot-fix with the old packaging, and ask Dominic Hargreaves to sponsor it as per the offer at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555000 . I wanted to kill to birds with one stone by fixing the bug and introducing the new upstream version. But I understand it takes more time to review the bigger changes. I'll prepare the quick fix so as not risk disrupting the perl transition. -- Postmen never die, they just lose their zip. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110513105150.88957ap79hh75...@mail.kalinowski.com.br
Re: RFS: kildclient (updated packages, fixes FTBS)
On 05/13/2011 01:31 PM, Sebastian Ramacher wrote:
> On 05/08/2011 08:42 PM, Eduardo M KALINOWSKI wrote:
>> The package is lintian clean, and builds in pbuilder.
> Actually, It's not:
>
> W: kildclient source: format-3.0-but-debian-changes-patch
>
> debian/patches/debian-changes-2.11.0-1 contains the changes from overwriting
> configu.guess. You can use the the scripts from autotools-dev to perform this
> task for you. Have a look at dh_autotools-dev_updateconfig(1) and
> dh_autotools-dev_restoreconfig(1).
That's strange, I could not get this warning with lintian 2.5.0 (just
installed from unstable). And I see no patches for config.{sub,guess} in
the kildclient_2.11.0-1.debian.tar.gz file, it only includes the normal
files in debian/
But I'll take a look at the mentioned tools nevertheless.
Anyway, if some DD is thinking about uploading this package, please
wait. I've submitted a quick fix for the FTBS bug 555000 to Dominic
Hargreaves as per his offer in that bug report, so I'll prepare a new
version soon.
> And concerning the dpkg-shlibdeps warnings you could consider linking with
> -Wl,--as-needed.
Is that the recommended way, or should I keep hoping that one day the
pkg-config files for gtk+ will not list so many libraries as
dependencies (that aren't really dependencies)?
--
Nothing is more admirable than the fortitude with which millionaires
tolerate the disadvantages of their wealth.
-- Nero Wolfe
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4dcd9af7.2080...@kalinowski.com.br
RFS: kildclient (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package "kildclient". * Package name: kildclient Version : 2.11.1-1 Upstream Author : me (Eduardo M Kalinowski) * URL : http://kildclient.sourceforge.net/ * License : GPL-2+ Section : games It builds these binary packages: kildclient - powerful MUD client with a built-in Perl interpreter kildclient-doc - powerful MUD client with a built-in Perl interpreter - - manual The package is lintian clean, and builds in pbuilder. This is an updated package, my usual sponsor (Christoph Haas) is busy at the moment and cannot upload it. It includes a new upstream version, DEP-5 copyright format, uses the new dpkg-source 3.0 (quilt format). The files are at http://kildclient.sourceforge.net/debian/, or just dget http://kildclient.sourceforge.net/debian/kildclient_2.11.1-1.dsc I would be glad if someone uploaded this package for me. - -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3iupoACgkQJAYvFKXQ6Tp2LACdGhp1171y3kqY0mIZOE2pDiQU 7skAn1XcmTcgOkoGAZsH8M4bIZdmGL0x =oGYk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4de2ba9a.4030...@kalinowski.com.br
Re: RFS: kildclient (updated package)
On 06/02/2011 06:05 PM, Craig Small wrote:
> On Sun, May 29, 2011 at 06:28:58PM -0300, Eduardo M KALINOWSKI wrote:
>> I am looking for a sponsor for my package "kildclient".
> I'll upload it for you.
>
Thanks a lot.
--
My favorite sandwich is peanut butter, baloney, cheddar cheese, lettuce
and mayonnaise on toasted bread with catsup on the side.
-- Senator Hubert Humphrey
Eduardo M KALINOWSKI
edua...@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4de80350.4010...@kalinowski.com.br
Re: Automake help to find boost_regexp needed
On 21/06/2020 18:43, Andreas Tille wrote: > Hi, > > in the Debian Med Covid-19 sprint I'm trying to package ufasta[1]. > Unfortunately the configure step leads to > > >checking for libboost_regex... no > > > I wonder what I'm doing wrong here. Well, is libboost-regex-dev (or an specific version) installed? -- "I don't care who does the electing as long as I get to do the nominating." -- Boss Tweed Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#1051298: RFS: kildclient/3.2.1-1 -- powerful MUD client with a built-in Perl interpreter
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "kildclient": * Package name : kildclient Version : 3.2.1-1 Upstream contact : Eduardo M Kalinowski * URL : https://www.kildclient.org * License : public-domain, GPL-2+, LGPL-2.1+ * Vcs : https://sourceforge.net/p/kildclient/git/ci/master/tree/debian/ Section : games The source builds the following binary packages: kildclient - powerful MUD client with a built-in Perl interpreter kildclient-doc - powerful MUD client with a built-in Perl interpreter - manual To access further information about this package, please visit the following URL: https://mentors.debian.net/package/kildclient/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/k/kildclient/kildclient_3.2.1-1.dsc Changes since the last upload: kildclient (3.2.1-1) unstable; urgency=low * rules, clean: Handle automatically generated html files in clean target. Closes: #1048469 * control: Use debhelper 13, and specify the compatibility level with a dependency on debhelper-compat (= 13). * control: Set Rules-Requires-Root to no. * watch: Change compatibility to version 4. * upstream/signing-key.asc: Extra signatures were removed from the signing key. * NEWS, docs: renamed NEWS.Debian to NEWS; it is no longer necessary to list this file in docs. * control: Updated policy compliance to 4.6.2, no changes were necessary. There's a litian warning 'debian-news-entry-has-unknown-version', this is because Changelog entries are being trimmed, but not NEWS entries (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021607 ). Other than that, a pedantic warning about a long line in aclocal.m4 (which is an auto-generated flag), and an experimental warning about -Wl,--as-needed. I'd rather keep this flag for the moment should the need to target buster arise. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#1051298: RFS: kildclient/3.2.1-1 -- powerful MUD client with a built-in Perl interpreter
On 23/10/2023 15:50, Bastian Germann wrote: Control: tags -1 moreinfo Please exclude the generated file src/kildclient.gresource.c from the source package. You can use debian/copyright's Files-Excluded field. When you are done, untag moreinfo. Isn't it a bit extreme to repack the source because of a file that is automatically generated, but is still distributable? I could instead set this file aside before building, force it to be regenerated, and restore it in the clean target. That's similar to what's done for the docs: a version of the generated html files is included in the tarball but it's not used, instead they are regenerated during build. -- A penny saved is ridiculous. Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#1051298: RFS: kildclient/3.2.1-1 -- powerful MUD client with a built-in Perl interpreter
On 25/10/2023 01:10, Paul Wise wrote: On Tue, 2023-10-24 at 17:57 -0300, Eduardo M KALINOWSKI wrote: Isn't it a bit extreme to repack the source because of a file that is automatically generated, but is still distributable? Indeed, it isn't necessary to repack source to remove generated files. https://wiki.debian.org/AutoGeneratedFiles The best option is to send upstream a patch removing the file from their VCS and tarballs so that it is always built from source. I am also the upstream. In the case of this file (kildclient.gresource.c) I agree that it can be removed from the upstream tarball. Even though an extra tool is required to generate the file, if someone that is building from source has the glib development package (which is a requirement), they're likely to have the necessary tool. As I mentioned, the tarball also has automatically generated html files for the manual (and the xml source). Bastian did not raise an issue about these files, but those I think should not be removed from the upstream tarball, because rebuilding them requires a whole other set of tools (docbook and a xlst processor), and this seems like an unnecessary complication for an end user that is building from source. But the packages files are ignored, and they're rebuilt from the source when the package is built. All that being said, while the next version of the upstream tarball will probably not include the kildclient.gresource.c file, I'd rather not release an upstream version just for that. So for the moment, I intend to fix the packaging to rm this file so that it's regenerated from the sources. Would this be acceptable, Bastian? (And when there's a new upstream release, I can remove this special treatment of the file.) -- It's lucky you're going so slowly, because you're going in the wrong direction. Eduardo M KALINOWSKI edua...@kalinowski.com.br
Bug#1051298: RFS: kildclient/3.2.1-1 -- powerful MUD client with a built-in Perl interpreter
Control: tags -1 - moreinfo On 25/10/2023 15:39, Bastian Germann wrote: Am 25.10.23 um 19:24 schrieb Eduardo M KALINOWSKI: All that being said, while the next version of the upstream tarball will probably not include the kildclient.gresource.c file, I'd rather not release an upstream version just for that. So for the moment, I intend to fix the packaging to rm this file so that it's regenerated from the sources. Would this be acceptable, Bastian? Yes. I've uploaded a new version to mentors with this change. I've also simplified the regeneration of the html docs. Let me know if you spot any further changes to be made. -- Eduardo M KALINOWSKI edua...@kalinowski.com.br
RFS: kildclient - A Powerful MUD client with a built-in Perl interpreter
I'm looking for someone to sponsor my program, KildClient. It is released under the GPL. WNPP entry: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=303635 I've been making .deb files since some upstream versions ago and putting them for users to download, but now I'd like to make the life of users simpler by adding KildClient to the Debian archive. The package is lintian-clean. Here's the program's description: KildClient is a MUD Client written with the GTK+ windowing toolkit. It supports many common features of other clients, such as triggers, gags, aliases, macros, timers, and much more. But its main feature is the built-in Perl interpreter. You can at any moment execute Perl statements and functions to do things much more powerful than simply sending text the the mud. Perl statements can also be run, for example, as the action of a trigger, allowing you to do complex things. Some built-in functions of KildClient allow interaction with the world, such as sending commands to it. Kildclient supports the MCCP (Mud Client Compression Protocol) protocol, versions 1 and 2, to reduce the necessary bandwidth. More information at http://kildclient.sf.net The package can be downloaded from http://kildclient.sourceforge.net/debian/ . The package is linda and lintian clean. Thanks, -- "How do I love thee? My accumulator overflows." Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: A dream of cut -m
On 29/06/2024 01:50, Kayven Riese wrote: If anyone has any advice on what I am missing to try to help improve GNU coreutils, I would greatly appreciate the advice. Before you start actively coding, I'd suggest you contact the upstream maintainers[0] and check whether they are interested in this new feature, and whether they'd be willing to incorporate your changes. coreutils, as the name says, is a very basic part of the GNU/Linux ecosystem, so they might be reluctant to accept changes. [0] There are some mailing lists listed at https://www.gnu.org/software/coreutils/ -- Just remember, wherever you go, there you are. -- Buckaroo Bonzai Eduardo M KALINOWSKI edua...@kalinowski.com.br
