Re: RFS: opencpn
On Mon, Feb 8, 2010 at 6:28 AM, Anton Martchukov wrote: > I am looking for a sponsor for my package "opencpn". Some comments on the debian.tar.gz part of the source package: Standards-Version is out of date, please read the upgrading document and make any changes appropriate. debian/watch doesn't really need any comments or blank lines, you can remove them. Same for the comment in debian/rules. I'd suggest adding DEP3 compliant headers to the patches: http://dep.debian.net/deps/dep3/ Please ensure the .desktop file installed into the binary package validates with desktop-file-validate, IIRC Icon should not be an absolute path and should not have an extension. Generally it isn't a good idea to patch Makefile.in without patching Makefile.am, what is the reason for that? I assume you've sent the manual page and patches upstream? Please ensure that this lintian command produces no complaints: lintian --info --display-info --display-experimental --pedantic --show-overrides --checksums --color auto I'll take a closer look at the package when I'm on a Debian system. Great to see it supports CM93 BTW. > Note that there are two lintian warnings that I left: > > W: opencpn source: configure-generated-file-in-source config.log > W: opencpn source: configure-generated-file-in-source config.status > > Not sure how critical are they, if they are not, I would > better work with upstream to fix it there directly. Upstream should use automake's 'make distcheck' to create tarballs for distribution, best teach them about it. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opencpn
On Mon, Feb 08, 2010 at 04:06:37PM +0800, Paul Wise wrote: > Standards-Version is out of date, please read the upgrading document > and make any changes appropriate. > > debian/watch doesn't really need any comments or blank lines, you can > remove them. Same for the comment in debian/rules. > > > I'd suggest adding DEP3 compliant headers to the patches: Thanks for comments, will fix this. > Please ensure the .desktop file installed into the binary package > validates with desktop-file-validate, IIRC Icon should not be an > absolute path and should not have an extension. I fixed this up to getting no warning from lintian. Will validate with desktop-file-validate too. Btw, I noted that most of the packages supply icons to /usr/share/pixmaps, but some less amount to /usr/share/icons like in case with OpenCPN. Is there any difference between those folders, maybe it's better to fix Makefile to install icons to pixmaps rather than icons? > Generally it isn't a good idea to patch Makefile.in without patching > Makefile.am, what is the reason for that? That's because I use configure supplied in tarball to build the package. I am going to submit patches for Makefile.am to upstream, so in next release we will have clean Maefiles our of the box. Could add patches to Makefile.am to the quilt too. > I assume you've sent the manual page and patches upstream? Not yet, but going to send them today. > Please ensure that this lintian command produces no complaints: > > lintian --info --display-info --display-experimental --pedantic > --show-overrides --checksums --color auto Ok. I see that it compains on the configure-generated files, some bindary in tarball (will check, did not know about that) and lack of patch descriptions. > Upstream should use automake's 'make distcheck' to create tarballs for > distribution, best teach them about it. I'll let them know. So far is it critical to make some hacking on the package level itself? -- Anton Martchukov http://www.martchukov.com 0xFC4FBF28 96BC 3DAB 231A 7FCC 4F49 D783 9A69 65C1 FC4F BF28 signature.asc Description: Digital signature
Re: RFS: opencpn
On Mon, Feb 8, 2010 at 4:38 PM, Anton Martchukov wrote: > Btw, I noted that most of the packages supply icons to > /usr/share/pixmaps, but some less amount to /usr/share/icons > like in case with OpenCPN. Is there any difference between > those folders, maybe it's better to fix Makefile to install > icons to pixmaps rather than icons? /usr/share/icons is better because you can install multiple images of different sizes. You can also install SVG icons there. You can also have different icons for different icon themes and so on. >> Generally it isn't a good idea to patch Makefile.in without patching >> Makefile.am, what is the reason for that? > > That's because I use configure supplied in tarball to build > the package. I am going to submit patches for Makefile.am to > upstream, so in next release we will have clean Maefiles our > of the box. > > Could add patches to Makefile.am to the quilt too. I think it would be a good idea, you never know who will look at your patches and use them blindly. >> Upstream should use automake's 'make distcheck' to create tarballs for >> distribution, best teach them about it. > > I'll let them know. So far is it critical to make some hacking > on the package level itself? >From the lintian tag info it sounds like it is worth it. You'll want to remove the files on clean and before ./configure is run. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opencpn
On Mon, Feb 08, 2010 at 04:47:16PM +0800, Paul Wise wrote: > I think it would be a good idea, you never know who will look at your > patches and use them blindly. > > >From the lintian tag info it sounds like it is worth it. You'll want > to remove the files on clean and before ./configure is run. Ok. Thanks for help! Will send an update to the list when fixed package becomes available at mentors. -- Anton Martchukov http://www.martchukov.com 0xFC4FBF28 96BC 3DAB 231A 7FCC 4F49 D783 9A69 65C1 FC4F BF28 signature.asc Description: Digital signature
E: pbuilder-satisfydepends failed.
Hi there,
I am trying to use pbuilder but it keeps failing with this error:
The following packages will be REMOVED:
liblzma1{u}
The following partially installed packages will be configured:
pbuilder-satisfydepends-dummy
0 packages upgraded, 377 newly installed, 1 to remove and 0 not upgraded.
Need to get 281MB of archives. After unpacking 888MB will be used.
The following packages have unmet dependencies:
gcj-jre-headless: Conflicts: java-gcj-compat-headless (< 1.0.80-6)
but 1.0.80-5.1 is to be installed.
libjpeg8-dev: Conflicts: libjpeg62-dev but 6b-16 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) pbuilder-satisfydepends-dummy
Keep the following packages at their current version:
2) java-gcj-compat [Not Installed]
3) java-gcj-compat-headless [Not Installed]
4) libjpeg62-dev [Not Installed]
5) libtiff4-dev [Not Installed]
6) libvtk5-dev [Not Installed]
Tier: Safe actions, Remove packages (1)
Does anyone knows what I need to do to make it work again ?
Thanks
--
Mathieu
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: E: pbuilder-satisfydepends failed.
On 2010-02-08 12:35 +0100, Mathieu Malaterre wrote:
> I am trying to use pbuilder but it keeps failing with this error:
>
>
> The following packages will be REMOVED:
> liblzma1{u}
> The following partially installed packages will be configured:
> pbuilder-satisfydepends-dummy
> 0 packages upgraded, 377 newly installed, 1 to remove and 0 not upgraded.
> Need to get 281MB of archives. After unpacking 888MB will be used.
> The following packages have unmet dependencies:
> gcj-jre-headless: Conflicts: java-gcj-compat-headless (< 1.0.80-6)
> but 1.0.80-5.1 is to be installed.
This looks like you've been hit by bug #566514¹.
> libjpeg8-dev: Conflicts: libjpeg62-dev but 6b-16 is to be installed.
This might be because your package build-depends on both libjpeg-dev
(which is now provided by libjpeg8-dev) and libjpeg62-dev (pulled in by
some other package). Try to find out which package pulls in
libjpeg62-dev.
Sven
¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566514
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Source format 3.0 (quilt)
Hello, I am considering to convert a package from 1.0 to 3.0 (quilt) format. I found documentation in dpkg-source(1) and on the wiki, but I still miss some information. For the 1.0 source format, I can see two practical, equivalent sub-forms: 1. the packed source, consisting in a .orig.tar.gz and a .diff.gz; 2. the working form, consisting in a .orig.tar.gz and a working directory. For the 3.0 (quilt), the packed source is well defined, but I have a doubt for the working form. According to dpkg-source(1), is seems to be the .orig.tar.ext and a working directory with patches applied *and* present in the debian/patches directory. Is that correct? Then, if I want to store my work in a VCS, it should also be with the patches applied. When I am sure of that, I shall modify the wiki page section that explain how to convert a source package to 3.0 (quilt), adding the instruction to apply the patches. Regards, -- Tanguy Ortolo signature.asc Description: Digital signature
Re: E: pbuilder-satisfydepends failed.
Sven, On Mon, Feb 8, 2010 at 1:17 PM, Sven Joachim wrote: >> ? gcj-jre-headless: Conflicts: java-gcj-compat-headless (< 1.0.80-6) >> but 1.0.80-5.1 is to be installed. > > This looks like you've been hit by bug #566514?. So I guess I have to wait a couple of days for this one. >> ? libjpeg8-dev: Conflicts: libjpeg62-dev but 6b-16 is to be installed. > > This might be because your package build-depends on both libjpeg-dev > (which is now provided by libjpeg8-dev) and libjpeg62-dev (pulled in by > some other package). ?Try to find out which package pulls in > libjpeg62-dev. This is weird. I think this may be caused by libvtk-java: $ apt-cache depends libvtk-java | grep jpeg Depends: libjpeg62 However the Build-Dep seems alright: http://patch-tracker.debian.org/patch/debianonly/view/vtk/5.4.2-4 ... +Build-Depends: debhelper (>= 7), libgl1-mesa-dev | libgl-dev, libglu1-mesa-dev | libglu-dev, libosmesa6-dev, + libx11-dev, libxt-dev, xvfb, x11proto-core-dev, tcl8.5-dev, tk8.5-dev, python-dev, cmake (>> 2.4), + libexpat-dev, libjpeg-dev, libpng-dev, libtiff-dev, zlib1g-dev, default-jdk, ... Any suggestions ? Thanks -- Mathieu ref: http://packages.debian.org/sid/libvtk-java -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: E: pbuilder-satisfydepends failed.
Le Mon, Feb 08, 2010 at 02:17:01PM +0100, Mathieu Malaterre a écrit : > > This is weird. I think this may be caused by libvtk-java: > > $ apt-cache depends libvtk-java | grep jpeg > Depends: libjpeg62 > > However the Build-Dep seems alright: > > http://patch-tracker.debian.org/patch/debianonly/view/vtk/5.4.2-4 > > ... > +Build-Depends: debhelper (>= 7), libgl1-mesa-dev | libgl-dev, > libglu1-mesa-dev | libglu-dev, libosmesa6-dev, > + libx11-dev, libxt-dev, xvfb, x11proto-core-dev, tcl8.5-dev, > tk8.5-dev, python-dev, cmake (>> 2.4), > + libexpat-dev, libjpeg-dev, libpng-dev, libtiff-dev, zlib1g-dev, default-jdk, > ... > > Any suggestions ? Hi Mathieu, libjpeg8-dev does not provide libjpeg-dev… Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: E: pbuilder-satisfydepends failed.
On 2010-02-08 14:17 +0100, Mathieu Malaterre wrote: > This is weird. I think this may be caused by libvtk-java: > > $ apt-cache depends libvtk-java | grep jpeg > Depends: libjpeg62 > > However the Build-Dep seems alright: > > http://patch-tracker.debian.org/patch/debianonly/view/vtk/5.4.2-4 > > ... > +Build-Depends: debhelper (>= 7), libgl1-mesa-dev | libgl-dev, > libglu1-mesa-dev | libglu-dev, libosmesa6-dev, > + libx11-dev, libxt-dev, xvfb, x11proto-core-dev, tcl8.5-dev, > tk8.5-dev, python-dev, cmake (>> 2.4), > + libexpat-dev, libjpeg-dev, libpng-dev, libtiff-dev, zlib1g-dev, default-jdk, > ... > > Any suggestions ? Which package are you trying to build? Sven -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: E: pbuilder-satisfydepends failed.
On 2010-02-08 14:25 +0100, Charles Plessy wrote: > libjpeg8-dev does not provide libjpeg-dev… The latest version (8-2) does. Sven -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: E: pbuilder-satisfydepends failed.
On Mon, Feb 8, 2010 at 2:26 PM, Sven Joachim wrote: > On 2010-02-08 14:17 +0100, Mathieu Malaterre wrote: > >> This is weird. I think this may be caused by libvtk-java: >> >> $ apt-cache depends libvtk-java | grep jpeg >> Depends: libjpeg62 >> >> However the Build-Dep seems alright: >> >> http://patch-tracker.debian.org/patch/debianonly/view/vtk/5.4.2-4 >> >> ... >> +Build-Depends: debhelper (>= 7), libgl1-mesa-dev | libgl-dev, >> libglu1-mesa-dev | libglu-dev, libosmesa6-dev, >> + libx11-dev, libxt-dev, xvfb, x11proto-core-dev, tcl8.5-dev, >> tk8.5-dev, python-dev, cmake (>> 2.4), >> + libexpat-dev, libjpeg-dev, libpng-dev, libtiff-dev, zlib1g-dev, >> default-jdk, >> ... >> >> Any suggestions ? > > Which package are you trying to build? http://packages.qa.debian.org/g/gdcm.html I have some changes I'd like to test before upload. If anyone is interested: svn co svn.debian.org/svn/debian-med/trunk/packages/gdcm/trunk cheers -- Mathieu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: E: pbuilder-satisfydepends failed.
Le Mon, Feb 08, 2010 at 02:28:38PM +0100, Sven Joachim a écrit : > On 2010-02-08 14:25 +0100, Charles Plessy wrote: > > > libjpeg8-dev does not provide libjpeg-dev… > > The latest version (8-2) does. So Matthieu only has to wait for version 8-2 to propagate to his favorite mirror… 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
Re: E: pbuilder-satisfydepends failed.
On 2010-02-08 15:43 +0100, Charles Plessy wrote: > Le Mon, Feb 08, 2010 at 02:28:38PM +0100, Sven Joachim a écrit : >> On 2010-02-08 14:25 +0100, Charles Plessy wrote: >> >> > libjpeg8-dev does not provide libjpeg-dev… >> >> The latest version (8-2) does. > > So Matthieu only has to wait for version 8-2 to propagate to his favorite > mirror… Um, I think you're wrong. Most likely his problem is that it has already propagated -- this transition is responsible for the conflict between libjpeg-dev and libjpeg62-dev. Sven -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
FS: tacacs+ (updated package)
Dear mentors, I am looking for a sponsor for my package "tacacs+". * Package name: tacacs+ Version : 4.0.4.19-1 Upstream Author : Shrubbery * URL : http://www.shrubbery.net/tac_plus/ * License : No license, only a copyright file Section : net It builds these binary packages: libtacacs+1 - TACACS+ authentication daemon libtacacs+1-dev - TACACS+ authentication daemon tacacs+- TACACS+ authentication daemon The upload would fix these bugs: 568161 My motivation for maintaining this package is: It's a very usefull package for ISP or/and large network environement. The most used free solutions are FreeRadius and Tacacs+ but Debian doesn't ship the latest one while it's the only solution if you want a complete accounting solution in a Cisco environement. To resume the situation : that package is a must for an ISP environement :) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/tacacs+ - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/tacacs+/tacacs+_4.0.4.19-1.dsc I would be glad if someone uploaded this package for me. Kind regards Henry-Nicolas Tourneur -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: tacacs+ (updated package)
Sorry for the bad subject, I meant RFS, of course. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opencpn
On Mon, Feb 8, 2010 at 4:06 PM, Paul Wise wrote: > I'll take a closer look at the package when I'm on a Debian system. I took a much closer look at the package and in summary; I'd really like to sponsor this package but it needs a lot of work upstream, especially in the copyright/license department. Please do contact this list again when you have worked with upstream to resolve the issues listed below. Should you have further questions, please don't hesitate to contact this list. I think upstream is installing the icons in the wrong directory. IIRC it should be be installed as /usr/share/icons/hicolor/48x48/apps/opencpn.png for bitmaps of size 48 x 48. XPM is not a good format for modern desktops since it has only 1-bit transparency and therefore no possibility of anti-aliased transparency. Unfortunately the Debian menu system requires it. I'd suggest that the .xpm file be installed in /usr/share/pixmaps, IIRC that has a lower priority in most desktops than /usr/share/icons/. Also, one of the opencpn.svg files could be shipped as /usr/share/icons/hicolor/scalable/apps/opencpn.svg The file 136ReleaseNotes might be relevant to install, in /usr/share/doc/opencpn perhaps. Hmm, half of it seems to be exactly the same as the changelog so maybe not. I suggest contacting upstream about it. Looks like upstream is using the ChangeLog as a NEWS file but have abandoned the NEWS file after the 1.2.6 release and now store NEWS entries in the ChangeLog instead. Whee! The NEWS file should summarise user-visible changes between releases and the ChangeLog file should be similar to VCS logs. The GNU Coding Standards document has more detail here: http://www.gnu.org/prep/standards/standards.html#NEWS-File http://www.gnu.org/prep/standards/standards.html#Change-Logs I'm confused, is upstream using both autotools and CMake? src/grib/bzip2 contains an embedded code copy of bzip2. Please ask upstream to remove it from the tarball. Same for src/grib/zlib-1.2.3. Software maintained elsewhere should not be in the tarball. Same for src/grib. All 3 are already in Debian: http://packages.debian.org/zygrib http://packages.debian.org/zlib http://packages.debian.org/bzip2 src/mygdal, src/myiso8211, src/nmea0183 all look like embedded code copies too. If the reason that they are in the tarball is for operating systems like Windows that don't have good packaging/repository/dependency systems, I'd suggest making a separate tarball containing tarballs for all the dependencies. warzone2100 does this and it seems to work well. src/nmea0183 has no copyright information and this as a license: You can use it any way you like. Unfortunately this does not give Debian permission to copy, modify or distribute. Another embedded code copy, Stackwalker.cpp, probably could be replaced by valgrind. bbox.cpp looks like it was copied from a really old version of wxWidgets; http://wxwindows2.4.sourcearchive.com/documentation/2.4.4.1.1ubuntu2/bbox_8cpp-source.html Surely newer versions of wxWidgets contain similar functionality that could be used instead of this code copy. There are other files that look like they are similar; inpcons.h dymemdc.h inphand.h uniparts.h and anything containing the phrase "Purpose: Optimized". The OpenCPN code contains this template: * Copyright (C) $YEAR$ by $AUTHOR$ * * $EMAIL$ * Upstream really needs to replace these by real information. Some files have the right info but still have the template. BTW, the template is wrong since (C) is not a valid symbol for copyright, IIRC only "Copyright", "Copyr." and "©" are. src/georef.c has this non-free license (non-commercial use/etc is non-free): /* Permission to use, copy, modify, and distribute this software and its */ /* documentation for non-commercial purpose, is hereby granted without fee, */ /* providing that the copyright notice appear in all copies and that both */ /* the copyright notice and this permission notice appear in supporting */ /* documentation. I make no representations about the suitability of this */ /* software for any purpose. It is provides "as is" without express or */ /* implid warranty. */ Similar for gpc.h georef.h macsercomm.cpp looks slightly suspect. I'd like to know its lineage, copyright and license. Same for macutils.c routeprop.cpp scrollingdialog.cpp sercomm.cpp macsercomm.h macutils.h routeprop.h scrollingdialog.h sercomm.h tcmgr.h triangulate.h data/s57data/* data/sounds/alarm2.wav contain these comments: Copyright . Cinematronics 1995 Microsoft Plus! . for Windows 95 It is highly likely that it is non-free, and I'd wager that alarm1.wav is too. The source code for HARMONIC.IDX does not seem to be distributed in the package. It says "This file is automatically generated by Tide2idx", so source code should exist. data/wvsdata/ is claimed to be open source, but is a subset. I'd suggest that it be packaged separately since it
Re: RFS: ceph
On Sat, 6 Feb 2010, Asheesh Laroia wrote: > For your package, I'll take a look right now. Some feedback: > > First of all, you've made it a native package. Fixed this up (after finally sorting out the difference between - and _ in the filename). Also fixed up the debian version (missing in changelog). > The package begins to build fine in a clean sid i386 pbuilder, but the build > ends in errors. See my attached text file for the end of the log. Feel free to > ask me for help setting up a pbuilder if you run into trouble with it. I'm having trouble getting pbuilder working; trying on another machine now. And it's not clear to me from the output you sent where those warnings are coming from. I'll continue to play with in. In the meantime, an updated .dsc is at http://ceph.newdream.net/debian/dists/unstable/main/source/ceph_0.18git20100207100754-1.dsc Thanks for reviewing! sage -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: ceph
On Sun, 7 Feb 2010, Paul Wise wrote: > Upstream keeping debian/ in their tarball is no longer as problematic; > with the dpkg-source 3.0 (quilt) format, dpkg-source deletes the > debian/ dir unpacked from the upstream orig.tar.gz before extracting > the debian.tar.gz, so the upstream debian/ dir is no longer relevant. Good to know. If the .deb ends up diverging from upstream at all (shouldn't!) I'll probably switch, as the patch approach is easier to manage. > >> I'm also interested in becoming a Debian Developer. My company, DreamHost > >> web hosting, is a long time debian user, and we maintain a large number of > >> packages internally that could be contributed upstream (perl modules and > >> such). One way or another, I'd like to see the packaging work we do > >> internally get contributed back to the community. > > For the perl modules, I'd strongly suggest the relevant persons join > the Perl team, you'll easily find sponsors, advice, QA and shared > maintainence there. > > http://wiki.debian.org/Teams/DebianPerlGroup Thanks, I'll get the appropriate people involved. sage
Re: Source format 3.0 (quilt)
Hi, Tanguy Ortolo wrote: > For the 3.0 (quilt), the packed source is well defined, but I have a > doubt for the working form. According to dpkg-source(1), is seems to be > the .orig.tar.ext and a working directory with patches applied *and* > present in the debian/patches directory. Is that correct? Yes, that’s right. > Then, if I > want to store my work in a VCS, it should also be with the patches > applied. Yes, that does tend to work well. The recent thread http://thread.gmane.org/gmane.linux.debian.devel.general/148937 includes some hints about generating the patches. > When I am sure of that, I shall modify the wiki page section that > explain how to convert a source package to 3.0 (quilt), adding the > instruction to apply the patches. Good idea. Thanks for noticing. Ciao, Jonathan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Source format 3.0 (quilt)
On Monday 08 February 2010 19:16:41 Jonathan Nieder wrote: > Hi, > > Tanguy Ortolo wrote: > > > For the 3.0 (quilt), the packed source is well defined, but I have a > > doubt for the working form. According to dpkg-source(1), is seems to be > > the .orig.tar.ext and a working directory with patches applied *and* > > present in the debian/patches directory. Is that correct? > > Yes, that’s right. > > > Then, if I > > want to store my work in a VCS, it should also be with the patches > > applied. > > Yes, that does tend to work well. The recent thread > http://thread.gmane.org/gmane.linux.debian.devel.general/148937 > includes some hints about generating the patches. > > > When I am sure of that, I shall modify the wiki page section that > > explain how to convert a source package to 3.0 (quilt), adding the > > instruction to apply the patches. > > Good idea. Thanks for noticing. > > Ciao, > Jonathan > > I do not use it that way. I use 3.0 to have several .orig.tgz files and no patches. This is because my package uses content from several upstreams. Take that in account when you modify the wiki page, please. The package (if you want to check the disposition) is wmaker-data Cheers Noel er Envite signature.asc Description: This is a digitally signed message part.
Re: Source format 3.0 (quilt)
Le lundi 08 février 2010, Noel David Torres Taño a écrit : > I do not use it that way. I use 3.0 to have several .orig.tgz files and no > patches. This is because my package uses content from several upstreams. Take > that in account when you modify the wiki page, please. Yes, no problem. Why I want to describe is: *if* you have patches, apply them and remove the patch logic from debian/rules. :-) -- Tanguy Ortolo signature.asc Description: Digital signature
Joining Debian
Hello, My name is Luis Pedro and I would like to join you all, and try to do something useful for free software. I am familiar with Linux, familiar with programming, but not much familiar with software development for Debian Linux. I followed some tutorials from Ubuntu, which is the "son" of Debian, about how to start... I have some notions but I feel like I need someone to guide me through development in Debian. Is anyone available? Thank you. Cheers -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Joining Debian
Hi Luis, You should take a look at the documents located at http://www.debian.org/devel/ Namely you should read the New Maintainers Guide: http://www.debian.org/doc/maint-guide/ The Debian Developers' Reference: http://www.debian.org/doc/developers-reference/ And you should also read the Debian Policy Manual: http://www.debian.org/doc/debian-policy/ Those documents will most likely answer many questions that you might have. If you have any specific questions, you can of course ask them. -Chris On Mon, Feb 08, 2010 at 09:26:49PM +, Luis Pedro wrote: > Hello, > > My name is Luis Pedro and I would like to join you all, and try to do > something useful for free software. I am familiar with Linux, familiar > with programming, but not much familiar with software development for > Debian Linux. I followed some tutorials from Ubuntu, which is the "son" > of Debian, about how to start... I have some notions but I feel like I > need someone to guide me through development in Debian. Is anyone > available? > > Thank you. > Cheers > > > -- > To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Joining Debian
On Mon, Feb 08, 2010 at 01:40:29PM -0800, Chris Taylor wrote: > You should take a look at the documents located at > http://www.debian.org/devel/ > > Namely you should read the New Maintainers Guide: > http://www.debian.org/doc/maint-guide/ > The Debian Developers' Reference: > http://www.debian.org/doc/developers-reference/ > And you should also read the Debian Policy Manual: > http://www.debian.org/doc/debian-policy/ In addition, the FAQ for this list: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html might answer some of your questions. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Joining Debian
Matthew Palmer wrote: > In addition, the FAQ for this list: > http://people.debian.org/~mpalmer/debian-mentors_FAQ.html might answer some > of your questions. As a side note, wouldn't the wiki be the perfect place for this? Don't get me wrong, I totally appreciate the work. It just seems like a bit of a waste of potential help, having it in a different place. Cheers -- Leo "costela" Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: pms-linux
Dear mentors, I am looking for a sponsor for my package "pms-linux". * Package name: pms-linux Version : 1.20+svn386-1 Upstream Author : ps3mediaserver, shagr4th * URL : http://code.google.com/p/ps3mediaserver/ * License : GPL v2 Section : video It builds these binary packages: pms-linux - DLNA Java Upnp Media Server dedicated to PS3 The package appears to be lintian clean. The upload would fix these bugs: 551645 My motivation for maintaining this package is: It's software i do use daily for streaming/trancoding my media files from my server ( or any simple computer ) to the TV via the PS3. I've using this software for months now,i expected it to get a .deb package but i decided to do the work since the upstream developper totally gave me his approbation ;) It's a really really good software. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/pms-linux - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/pms-linux/pms-linux_1.20+svn386-1.dsc I would be glad if someone uploaded this package for me. Kind regards DIAKHATE Papa Issa 0xE1F9F391.asc Description: application/pgp-keys 0xE1F9F391.asc Description: application/pgp-keys
Re: Joining Debian
On Monday 08 February 2010 15:26:49 Luis Pedro wrote: > My name is Luis Pedro and I would like to join you all, and try to do > something useful for free software. I am familiar with Linux, familiar > with programming, but not much familiar with software development for > Debian Linux. I followed some tutorials from Ubuntu, which is the "son" > of Debian, about how to start... I have some notions but I feel like I > need someone to guide me through development in Debian. Is anyone > available? Links to some of my replies to previous, similar questions: http://www.mail-archive.com/debian-u...@lists.debian.org/msg544001.html http://www.mail-archive.com/debian-mentors@lists.debian.org/msg63936.html If you have specific questions ask them here or on IRC, you'll usually get a quick turn-around. If you don't, make an attempt at *some* task, and present your work. Trust me, any issues remaining will prompt your peers to correct you. >:) -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
RFS: jcgui
Dear mentors, I am looking for a sponsor for my package "jcgui". * Package name: jcgui Version : 0.7-1 Upstream Author : Hermann Meyer * URL : http://jcgui.sourceforge.net/ * License : GPL-2 Section : sound It builds these binary packages: jcgui - a simple Host wrap around jconvolver/jconv The package appears to be lintian clean. The upload would fix these bugs: 562174 My motivation for maintaining this package is: I am using it myself and I found it very useful. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/j/jcgui - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/j/jcgui/jcgui_0.7-1.dsc I would be glad if someone uploaded this package for me. Kind regards Jaromír Mikeš -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: FS: tacacs+ (updated package)
On Mon, Feb 08, 2010 at 04:38:23PM +0100, Tourneur Henry-Nicolas wrote: > I am looking for a sponsor for my package "tacacs+". I've sponsored and uploaded this package. - Craig -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 http://www.enc.com.au/ csmall at : enc.com.au http://www.debian.org/ Debian GNU/Linux, software should be Free -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: README.Debian updated
On Sun, 7 Feb 2010, David D Lowe wrote: On Sat, 2010-02-06 at 21:51 -0500, Asheesh Laroia wrote: Ping debian-mentors when you've updated README.Debian! I've updated README.Debian, you can get the new version at: - URL: http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/o/ooo-thumbnailer/ooo-thumbnailer_0.2-4.dsc I'm excited about finally getting this into Debian! *Almost* A few lintian warnings: paulprot...@renaissance:~/pbuilder/result/sid-i386 $ lintian ooo*deb W: ooo-thumbnailer: extra-license-file usr/share/doc/ooo-thumbnailer/COPYING.gz W: ooo-thumbnailer: debian-changelog-line-too-long line 2 W: ooo-thumbnailer: debian-changelog-line-too-long line 5 W: ooo-thumbnailer: extra-license-file usr/share/doc/ooo-thumbnailer/COPYING.gz Sorry to not mention these before -- can you give them a look? Don't forget to look into DebianMaintainer status so you can keep shipping this (although, from the length of the script, it's almost hard to imagine you'll have any bugs). -- Asheesh. -- Now that I have my "APPLE", I comprehend COST ACCOUNTING!! -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: ceph
On Mon, 8 Feb 2010, Sage Weil wrote: On Sat, 6 Feb 2010, Asheesh Laroia wrote: For your package, I'll take a look right now. Some feedback: First of all, you've made it a native package. Fixed this up (after finally sorting out the difference between - and _ in the filename). Also fixed up the debian version (missing in changelog). Great. The package begins to build fine in a clean sid i386 pbuilder, but the build ends in errors. See my attached text file for the end of the log. Feel free to ask me for help setting up a pbuilder if you run into trouble with it. I'm having trouble getting pbuilder working; trying on another machine now. And it's not clear to me from the output you sent where those warnings are coming from. I'll continue to play with in. rebuilding! I'll go to sleep now, though, I think. Hopefully I'll say something about this in the morning. As for your pbuilder stuff, feel free to paste me errors, or find me on IRC; I'm paulproteus on OFTC and FreeNode. pbuilder can be a pain to set up. Don't be too easily discouraged. And you'll need sudo, in my experience; I haven't had much luck with setting up pbuilders with fakechroot and other tricks. -- Asheesh. -- Happiness isn't having what you want, it's wanting what you have. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
