How to note the license in copyright
Hello, I've faced the sources with the following copyright header: / ** ** Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). ** ** Use, modification and distribution is allowed without limitation, ** warranty, liability or support of any kind. ** / This header makes me think about public domain or WTFPL. However it's not strictly expressed, and neither me nor the upstream author (he's not the author of that code) is sure, how to express the copyright information in COPYING and debian/copyright. Thanks in advance. Best wishes and have a nice day, Vsevolod Velichko -- 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/CAAtb-VSKU=3l8+wxsouvf9emmf-bvjwjchh3eucfswsobvy...@mail.gmail.com
Bug#658235: RFS: libjreen, the xmpp library (3rd try, 2 months later)
Dear Benoît, I'm very thankful for your package review. I've just fixed most of the things you mentioned. However, there're a couple of moments I'm unsure. I: libjreen1: no-symbols-control-file usr/lib/libjreen.so.1.0.1 There was a long C++ vs symbols discussion[1] recently with pros and contras. I suppose, that symbols really doesn't make sense for C++ and too hard to maintain (just to create the appropriate symbols file, I have to somehow upload the package with initial .symbols version, wait for build fails everywhere, collect buildd logs, and only there I'll be able to create real .symbols file). For example, dpkg-gensymbols generates 1633 lines of .symbols for this library. Are you sure that it's really needed? The dh_auto_install override could also be replaced by using debian/package.install files (see dh_install(1) for details). I'm unsure that .install is better solution. The one of mine should work in most cases, even if one change library and package names, I'll have to change only a package name in dh_auto_install override. In the case of .install files there would be more work. Am I right? I've uploaded new version to mentors[2], if you agree with my comments above, could you review and probably sponsor the fixed version, please? [1] http://lists.debian.org/debian-devel/2012/01/thrd2.html#00671 [2] http://mentors.debian.net/debian/pool/main/libj/libjreen/libjreen_1.0.1-1.dsc Best wishes and have a nice day, Vsevolod Velichko 2012/2/20 Benoît Knecht benoit.kne...@fsfe.org: Hi Vsevolod, Vsevolod Velichko wrote: I am looking for a sponsor for my package libjreen (and do this for the 3rd time, because I've got no answer, neither positive nor negative since November 2011). * Package name : libjreen Version : 1.0.1-1 Upstream Author : Ruslan Nigmatullin euroeles...@yandex.ru * URL : http://qutim.org/jreen * License : GPL2+ Section : libs It builds those binary packages: libjreen-dev - powerful Jabber/XMPP library - development files libjreen1 - powerful Jabber/XMPP library implemented in Qt/C++ I took a look at your package, here are a few things you may want to look into: - Some warnings from lintian: I: libjreen source: binary-control-field-duplicates-source field section in package libjreen1 P: libjreen source: unversioned-copyright-format-uri http://dep.debian.net/deps/dep5 I: libjreen1: no-symbols-control-file usr/lib/libjreen.so.1.0.1 - In debian/control, your long description repeats the synopsis, and it doesn't consist of full sentences. See [1] for guidelines about writing good descriptions. [1] http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-pkg-desc If you're not using a VCS, you should remove those commented-out lines. - In debian/rules, the dh_installchangelogs override isn't needed; debhelper will pick up the upstream changelog automatically. The dh_auto_install override could also be replaced by using debian/package.install files (see dh_install(1) for details). - In debian/copyright, you should use the predefined short names for licenses; what you call MIT/X11 (BSD Like) is the Expat license. And even though it's more cosmetic than anything, GPL-2.0+ could be replaced by GPL-2+. I'm also not sure your debian/README.source is particularly relevant. First of all, one _should_ care about that copyright in Debian since those files are shipped in the source package (so clauses about distribution of those files certainly apply). If you want to say that the binary package doesn't contain any code from these files, perhaps a Comment in the relevant File paragraph in debian/copyright would be better (as this file is actually installed along with the binary package). I've built your package, but I haven't installed and tested it, so I cannot comment on that. Cheers, -- Benoît Knecht -- 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/caatb-vrurpbwmyrmwku-165qgo6epnq36gf9tg7nexummw6...@mail.gmail.com
RFS: libjreen (2nd try, 11 days later)
Since I got no response, neither positive, nor negative, I'm retrying my sponsorship request. Please, forgive me, if you are get bored by the letter, but I would be very thankful if one could review and upload this package. You can see the package description in the quotation below. Best wishes and have a nice day, Vsevolod Velichko 2011/11/15 Vsevolod Velichko torkv...@gmail.com: Dear mentors, I am looking for a sponsor for my package libjreen. * Package name : libjreen Version : 1.0.1-1 Upstream Author : Ruslan Nigmatullin euroeles...@yandex.ru * URL : http://qutim.org/jreen * License : GPL2+ Section : libs It builds those binary packages: libjreen-dev - powerful Jabber/XMPP library - development files libjreen1 - powerful Jabber/XMPP library implemented in Qt/C++ Jreen is the library, which aims to provide an fast and extensible Jabber implementation with the full support of large variety of useful XEP's ignored by most developers. It's already used in qutIM[1] and Tomahawk[2] projects. The package appears to be lintian clean. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libjreen Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libj/libjreen/libjreen_1.0.1-1.dsc I would be glad if someone uploaded this package for me. [1] http://qutim.org (Multiprotocol instant messenger) [2] http://gettomahawk.com/ (Social media player) Best wishes and have a nice day, Vsevolod Velichko -- 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/caatb-vr-ox8rrl2rt8x-fmw5ek2irutyxua7nadqmutxrvk...@mail.gmail.com
Re: Best practice for changelog file
Dear Charles,
this the very thing I want to do, but as far as I can understand, I
should replace that variables myself, am I right? When I try to put
the variables in debian/changelog, dpkg-buildpackage fails with error:
dpkg-buildpackage: source version 1.1.0-7~bpo${debian_release}+${build_int}
dpkg-buildpackage: error: version number contains illegal character `$'
I realize that I can add new ~bpoXX record into changelog myself each
time I'm building new version, but I want to find if there any way to
do it automatically during build-time?
Obviously, I could use some build-script that would use sed to replace
version in changelog and then run dpkg-buildpackage, but this way
seems to be a not clear workaround.
Best wishes and have a nice day,
Vsevolod Velichko
2011/8/25 Charles Plessy ple...@debian.org:
Le Wed, Aug 24, 2011 at 02:18:40PM +0400, Vsevolod Velichko a écrit :
I'm trying to build package for two debian versions: squeeze and
lenny. Build process doesn't require any source or packaging
modifications, so I can just dpkg-buildpackage or debuild on both
lenny and squeeze to obtain the deb-file. The problem is that in this
case I have the same version for both systems, so I can't put them in
the same repository. Is there any well-known way to take a changelog
version record (e.g. 1.1.0-5) and produce deb with debian-specific
package version (e.g. 1.1.0-5+squeeze1) ?
Dear Vsevolod,
you can probably adopt a similar strategy as for the Debian backports:
Append ~bpo${debian_release}+${build_int} to the version number, e.g.
1.2.3-4 now becomes 1.2.3-4~bpo60+1, or for native packages, 1.2.3
becomes 1.2.3~bpo60+1
http://backports-master.debian.org/Contribute/#index5h3
This way, the package built on a more recent suite will always have a higher
version.
Of course, keeping ‘bpo’ in the version number will be confusing, so it would
be better to replace it something else, ideally that sorts lower. The --local
option of dch may help you to automate the task.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--
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/20110825021711.gd30...@merveille.plessy.net
--
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/cahvbjfsj9wnrwvg2eeamphyggwvhdvrhk2pfgtozz62vb9+...@mail.gmail.com
Best practice for changelog file
Hello all! I'm trying to build package for two debian versions: squeeze and lenny. Build process doesn't require any source or packaging modifications, so I can just dpkg-buildpackage or debuild on both lenny and squeeze to obtain the deb-file. The problem is that in this case I have the same version for both systems, so I can't put them in the same repository. Is there any well-known way to take a changelog version record (e.g. 1.1.0-5) and produce deb with debian-specific package version (e.g. 1.1.0-5+squeeze1) ? Thanks in advance. Best wishes and have a nice day, Vsevolod Velichko -- 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/CAHvbjfvNGrrfwXN5iMM_0WwCm4nxA9+q1SCO5ku7Fu-ao8=z...@mail.gmail.com
Re: RFS: qca-cyrus-sasl - Cyrus SASL plugin for Qt Cryptographic Architecture
Hi, 2011/5/1 Michael Tautschnig m...@debian.org * Package name : qca-cyrus-sasl Version : 2.0.0-beta3-1 I'm looking for a sponsor for my package qca-cyrus-sasl. [...] Sorry for the massive delay until anyone got around to review your package. I finally did so, built, and uploaded it. The package looked pretty much ok, I'd only have minor requests for you to fix in future uploads: Michael, thanks for your sponsorship. It seems that I fixed all the things you've mentioned, so I've created a new upload with version 2.0.0-beta3-2. It's available on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/q/qca-cyrus-sasl - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/q/qca-cyrus-sasl/qca-cyrus-sasl_2.0.0-beta3-2.dsc It'll be nice, if you could find some time to look into it. Thanks again and my kind regards. - debian/copyright should be converted to DEP-5 format (http://dep.debian.net/deps/dep5/). The current file is already very tidy and hence a conversion should be very painless. - Although upstream doesn't seem to be releasing too many new versions recently, a watch file would be desirable. - There is no need to duplicate the Section field in the binary package in debian/control. Best wishes and have a nice day, Vsevolod Velichko -- 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/BANLkTimMqLJfLQzR44ss=i6jv0nuymk...@mail.gmail.com
RFS: qca-cyrus-sasl - Cyrus SASL plugin for Qt Cryptographic Architecture
Hello, dear Mentors, I'm looking for a sponsor for my package qca-cyrus-sasl. * Package name: qca-cyrus-sasl Version : 2.0.0-beta3-1 Upstream Author : Justin Karneges jus...@affinix.com * URL : http://delta.affinix.com/download/qca/2.0/plugins/qca-cyrus-sasl-2.0.0-beta3.tar.bz2 * License : LGPL 2.1 Section : libs It builds these binary packages: libqca2-plugin-cyrus-sasl - QCA Cyrus SASL plugin for libqca2 The package appears to be lintian clean. The upload would fix these bugs: 464863 My motivation for maintaining this package is desire to help those Qt applications who use SASL (e.g. IM applications like Psi or qutIM) and have to link this plugin statically with their software or just ignore Debian and Ubuntu, requiring users to build this plugin themselves. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/q/qca-cyrus-sasl - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/q/qca-cyrus-sasl/qca-cyrus-sasl_2.0.0-beta3-1.dsc I would be glad if someone uploaded this package for me. Best wishes and have a nice day, Vsevolod Velichko -- 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/aanlktinoy-kxmj86tvx-hgszhvztayop1qscbuhjn...@mail.gmail.com
