Bug#668076: reSIProcate packages RFS
Hi, On Sun, Apr 08, 2012 at 09:07:49PM +0200, Daniel Pocock wrote: Hi, I've recently filed an RFS for reSIProcate http://lists.debian.org/debian-mentors/2012/04/msg00168.html I didn't yet try to build it, but at first glance the packaging looks good. One minor nit: The license is a 4-cluase BSD-like license. Is this intended to be a used as a library? Clause (3) from the license makes it *GPL incompatible. Any hope of fixing that? If anyone is interested in reviewing or collaborating on this, please get in touch. I'd also be interested to know if pkg-voip-maintainers should be registered as the maintainer for this work. In particular, the packages provide a working instance of the repro SIP proxy and the reTurn TURN server Looks interesting. I see you've already merged your autotool fixes in upstream trunk. Also note that if you switch to dpkg v.3, there's nothing wrong with having a debian/ directory upstream (if it helps them). It just gets deleted at packaging time. -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- 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/20120409084100.gn5...@xorcom.com
Bug#668148: RFS: xshisen/1:1.51-4
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package xshisen * Package name: xshisen Version : 1:1.51-4 Upstream Author :Masaoki Kobayashimasa...@techfirm.co.jp * URL : http://www.techfirm.co.jp/~masaoki/xshisen.html * License : BSD-3 Section : games It builds those binary packages: xshisen- Shisen-sho puzzle game for X11 To access further information about this package, please visit the following URL: http://mentors.debian.net/package/xshisen Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/x/xshisen/xshisen_1.51-4.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * Acknowledge NMUS * dpkg-source 3.0 (finally doing away cdbs in favor of dh) * Fix a couple of bugs (FTBFS for gcc-4.7 and manpage typos) Regards, zakame -- 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/4f82b036.1000...@zakame.net
Bug#668076: reSIProcate packages RFS
On 09/04/12 10:41, Tzafrir Cohen wrote: Hi, On Sun, Apr 08, 2012 at 09:07:49PM +0200, Daniel Pocock wrote: Hi, I've recently filed an RFS for reSIProcate http://lists.debian.org/debian-mentors/2012/04/msg00168.html I didn't yet try to build it, but at first glance the packaging looks good. One minor nit: The license is a 4-cluase BSD-like license. Is this intended to be a used as a library? Clause (3) from the license makes it *GPL incompatible. Any hope of fixing that? I believe you are referring to this clause: 3. The names VOCAL, Vovida Open Communication Application Library, and Vovida Open Communication Application Library (VOCAL) must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact vo...@vovida.org. http://www.resiprocate.org/License Here is some background info about VOCAL: http://www.voip-info.org/wiki/view/VOCAL I'm not sure if Vovida or VOCAL still exists in some formal sense, and if so, I don't know whether the clause is still valid or even relevant reSIProcate broke away from SIPfoundry and some of the other projects some years ago too, so it is quite independent Can you comment more on the relationship of this clause with the GPL? Does it just prevent linking with *GPL apps, or does it prevent inclusion in Debian outright? As it is now, could it go in contrib or non-free rather than main? If anyone is interested in reviewing or collaborating on this, please get in touch. I'd also be interested to know if pkg-voip-maintainers should be registered as the maintainer for this work. In particular, the packages provide a working instance of the repro SIP proxy and the reTurn TURN server Looks interesting. I see you've already merged your autotool fixes in upstream trunk. Also note that if you switch to dpkg v.3, there's nothing wrong with having a debian/ directory upstream (if it helps them). It just gets deleted at packaging time. It may be better to manage it separately on alioth/collab-maint (Gregor already started a Git repo there), so that people who are not members of the reSIProcate project can make changes if needed. Having two versions (one in upstream and another on alioth) may also lead to confusion, even though it is technically permitted now. However, I don't mind either way. -- 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/4f82ad56.6020...@pocock.com.au
hints for creating deb packages with cmake build system
Hi, I am looking for instructions on how to create a debian package that uses cmake as build system as I'm wondering how the debian/rules should look and what it should contain for cmake? Can anyone tell me a small package that uses cmake as build system, where i could peak for a debian/rules file? Any other good hints or links? :) Thanks, Werner -- 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/4f82d3e0@aloah-from-hell.de
Re: hints for creating deb packages with cmake build system
On Mon, Apr 09, 2012 at 02:19:44PM +0200, Werner Detter wrote: I am looking for instructions on how to create a debian package that uses cmake as build system as I'm wondering how the debian/rules should look and what it should contain for cmake? Can anyone tell me a small package that uses cmake as build system, where i could peak for a debian/rules file? Any other good hints or links? :) dh_auto_configure(1) supports cmake. -- WBR, wRAR signature.asc Description: Digital signature
Re: hints for creating deb packages with cmake build system
On 09/04/12 14:19, Werner Detter wrote: Hi, I am looking for instructions on how to create a debian package that uses cmake as build system as I'm wondering how the debian/rules should look and what it should contain for cmake? Can anyone tell me a small package that uses cmake as build system, where i could peak for a debian/rules file? Any other good hints or links? :) cdbs makes it very easy http://build-common.alioth.debian.org/cdbs-doc.html#id2561559 I've used cdbs for autotools projects, the debian/rules file is minimal: http://dynalogin.git.sourceforge.net/git/gitweb.cgi?p=dynalogin/dynalogin;a=blob;f=debian/rules;h=6fc978435cf87e22878768cbe97a7d6d3953784f;hb=39ecf66329b9bd0d6333baf52b10592d1a7f2ee9 Notice where I include autotools.mk, I think you can use include this instead: include /usr/share/cdbs/1/class/cmake.mk -- 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/4f82d6e7.5080...@pocock.com.au
Re: hints for creating deb packages with cmake build system
On Mon, Apr 9, 2012 at 2:19 PM, Werner Detter wer...@aloah-from-hell.de wrote: Hi, I am looking for instructions on how to create a debian package that uses cmake as build system as I'm wondering how the debian/rules should look and what it should contain for cmake? Can anyone tell me a small package that uses cmake as build system, where i could peak for a debian/rules file? Any other good hints or links? :) I use dh directly (no cdbs): http://anonscm.debian.org/gitweb/?p=collab-maint/kwstyle.git;a=blob;f=debian/rules;h=2e854096a086a53312ec488891a5f75e2d5294d2;hb=HEAD HTH -- 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/CA+7wUsw4-EevcdJd=eeN5kjBc_sVLWsuwFnM=QpN=qjT=gj...@mail.gmail.com
Bug#664766: RFS: ember/0.6.2-1 [ITA]
tag 664766 + moreinfo confirmed
Hi,
sorry for taking a while, but here is the first round of comments:
Stephen M. Webb stephen.w...@bregmasoft.ca writes:
ember (0.6.2-1) unstable; urgency=low
* new upstream release (closes: #633854)
- removed dependency on libceguiogre-dev (closes: #629767)
* removed old unused build dependencies
* converted to 3.0 (quilt) source format, removed obsolete patches
* converted to use dh sequencer
* new maintainer: Debian games team (closes: #653970)
-added myself as uploader
^^^
There is a space missing here.
* adjusted paths in installed launcher script to use defaults
* used xz compression in packaging
* debian/control: updated Standards-Version to 3.9.3
* debian/copyright: changed to computer-readable format (DEP-5)
Comments about the packaging:
Looks good, only some minor nitpicks:
- debian/ember.1: Debian GNU/Linux should be changed to just Debian.
- Are the patches forwarded upstream?
- d/rules: find -exec rm can be replaced with find -delete
- d/rules: find . could be replaced with find debian/tmp as I
understand you only want to remove duplicate COPYING files.
- d/rules: # force use of local version of tolua++ and newer libtool
doesn't seem related to the command below it.
About copyright information:
- src/components/ogre/environment/pagedgeometry/include/MersenneTwister.h:
BSD-*3*-clause, also:
When you use this, send an email to: m-...@math.sci.hiroshima-u.ac.jp
with an appropriate reference to your work.
This additional clause makes the license non-free (postcardware),
see also the first example in question 12 of the [DFSGFAQ].
I believe having seeing this before and it might have changed by
upstream, but I haven't checked.
- FastDelegate.h: released under CPOL according to [FASTDELEGATE].
See [CPOL] for the license. I haven't read the license text yet,
please check it fulfills the DFSG requirements and is compatible with
the other licenses.
- DRGNURBSSurface.{h,cpp}: Copyright 1999 Intel Corporation.
See file for license.
- EmberPagingSceneManager/*: mostly LGPL-2+, not -2.1+
There are additional copyright holders and years of copyright should
probably be updated as well. I noticed at least these, but didn't look
that careful:
- years of copyright need to be updated:
Erik Hjortsberg erik.hjortsb...@gmail.com, (C) 2011
(from EmberPagingTerrainObserver.h and others)
- Copyright (C) 2009 Manuel A. Fernandez Montecelo
- Copyright (C) 2011 Erik Ogenvik GPL-2+
- src/components/ogre/gui/RenderedColourStringTextComponent.cpp:
contains code lifted from the CEGUI project. Has additional
copyright holder and license.
- Copyright (c) 2000-2006 Torus Knot Software Ltd
About upstream code:
- ./ember should probably use `set -e' and maybe also `set -u'.
Also it's not possible to pass both --home and --debug.
- ./ember.in seems to be no longer needed (it has the same contents as
./ember).
- src/components/ogre/terrain/ICompilerTechniqueProvider.h:
The header states C++ Interface: ITerrainMaterialFinalizer which
looks like a copy-and-paste error. The include guards use
EMBER_OGREVIEW_ITERRAINMATERIALFINALIZER_H as well.
- spelling error: To switch bach to attached mode, close the frame
window with the dialog: bach - back
Regards,
Ansgar
[CPOL] http://www.codeproject.com/info/cpol10.aspx
[DFSGFAQ] http://people.debian.org/~bap/dfsg-faq.html
[FASTDELEGATE] http://www.codeproject.com/cpp/FastDelegate.asp
--
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/87hawtas9v@deep-thought.43-1.org
Processed (with 5 errors): Re: Bug#664766: RFS: ember/0.6.2-1 [ITA]
Processing commands for cont...@bugs.debian.org: tag 664766 + moreinfo confirmed Bug #664766 [sponsorship-requests] RFS: ember/0.6.2-1 [ITA] Added tag(s) confirmed and moreinfo. Hi, Unknown command or malformed arguments to command. sorry for taking a while, but here is the first round of comments: Unknown command or malformed arguments to command. Stephen M. Webb stephen.w...@bregmasoft.ca writes: Unknown command or malformed arguments to command. ember (0.6.2-1) unstable; urgency=low Unknown command or malformed arguments to command. Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 664766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.133398205025448.transcr...@bugs.debian.org
Re: hints for creating deb packages with cmake build system
Hi, cdbs makes it very easy http://build-common.alioth.debian.org/cdbs-doc.html#id2561559 I've decided to go with cdbs now, my debian/rules looks now like: #!/usr/bin/make -f include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/rules/patchsys-quilt.mk include /usr/share/cdbs/1/class/cmake.mk As I'm currently trying to package a C library that should be available on different architectures i think I have to tell the build process the right architecture. How is this dynamically accomplished with cmake/cdbs as the underlying build system ? Thanks, Werner -- 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/4f82f441.2050...@aloah-from-hell.de
Re: hints for creating deb packages with cmake build system
On 09/04/12 16:37, Werner Detter wrote: Hi, cdbs makes it very easy http://build-common.alioth.debian.org/cdbs-doc.html#id2561559 I've decided to go with cdbs now, my debian/rules looks now like: #!/usr/bin/make -f include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/rules/patchsys-quilt.mk include /usr/share/cdbs/1/class/cmake.mk As I'm currently trying to package a C library that should be available on different architectures i think I have to tell the build process the right architecture. How is this dynamically accomplished with cmake/cdbs as the underlying build system ? You just specify the architecture `any' in the debian/control file Architecture: any dpkg-buildpackage, cdbs and cmake should then figure out the rest for you, give correct CFLAGS to your compiler, etc, no matter what machine someone tries to build the package on. -- 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/4f82f529.5020...@pocock.com.au
Re: hints for creating deb packages with cmake build system
Hi Daniel, You just specify the architecture `any' in the debian/control file Architecture: any dpkg-buildpackage, cdbs and cmake should then figure out the rest for you, give correct CFLAGS to your compiler, etc, no matter what machine someone tries to build the package on. Perfect, thanks for your response :) Regards, Werner -- 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/4f82f791.8050...@aloah-from-hell.de
package bundle versioning
I have a source package which contains a number of packages that are inter-dependent. Is there a way to make sure that the versions of the different packages inside the bundle are in sync when installed? This came up last weekend when someone ran into problems after upgrading one but not another package from the bundle. One way to do it manually would be to hardcode the version from the changelog file and append this to each of the individual Depends fields in conrol. But this would mean having to update the control file for every version. Is there a better way? Thank you, Jeroen
Re: package bundle versioning
Jeroen Ooms jeroen.o...@stat.ucla.edu writes:
I have a source package which contains a number of packages that are
inter-dependent. Is there a way to make sure that the versions of the
different packages inside the bundle are in sync when installed?
As long as only one source package is involved you can easily do so by
using Depends: foo (= ${source:Version}) or (= ${binary:Version}) in
debian/control. See also deb-substvars(5).
You usually want to use source:Version for dependencies on an arch:all
package and binary:Version for dependencies of an arch:any package on
another arch:any package. This way the dependencies will be correct
even after a binNMU of the arch:any packages.
Dependencies of an arch:any on a arch:all package are a bit trickier.
Regards,
Ansgar
--
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/874nssbpn7@deep-thought.43-1.org
Bug#664765: RFS: ember-media/0.6.2.1-1 [ITA]
Hi, Stephen M. Webb stephen.w...@bregmasoft.ca writes: dget -x http://mentors.debian.net/debian/pool/main/e/ember-media/ember-media_0.6.2.1-1.dsc I haven't had time for a proper review, but here are some first comments: - typo in the package description: media data user at runtime should be media data *used* at runtime. - The WF packages currently use three different forms to refer to WF: Worldforge, WorldForge and World Forge. Please decide on one of them. - I prefer if the short description would tell more about the package, not only that it is related to ember. Maybe 3D client of the WorldForge project -- media files or something along that lines? - The package creates links to fonts shipped in other packages, but does not depend on them. - debian/copyright should use GPL-2+ or GFDL-NIV-1.1+ for dual-licensed files and have two license paragraphs (one for GPL-2+ and one GFDL-NIV-1.1+). Regards, Ansgar -- 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/87y5q4a948@deep-thought.43-1.org
Re: RFS: gogglesmm
Hi Michael, Are you aware of the ongoing transitions that (also) concern gogglesmm? Looking at http://packages.qa.debian.org/g/gogglesmm.html it seems to be preferable not to upload at this time, unless well coordinated with the release team. thank you for mentioning that. The package also fixes the recently reported Bug#668178. I have uploaded an new version of the package, which states that in the changelog. Please let me know if there is anything that I have to take care of concerning the libpng transition. I think I have to wait for a new version of the fox-1.6 (libfox) package. Regards, Hendrik signature.asc Description: This is a digitally signed message part
