Re: your mail
Hi Kerim, On Sun, Oct 16, 2016 at 05:53:44PM +0300, Kerim Ölçer wrote: > Hello Andreas, I looked at Emperors liscences. Some of them use copyright > liscences ( no MIT,GPL etc.). You looked it before is this a problem if it > is what should i do ? Best Regards. I think the first thing to do is mentioning all licenses in debian/copyright. If there is something non-free we should check whether it is really needed or could be droped. If its really needed we should contact the authors. Kind regards Andreas. -- http://fam-tille.de
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 800339 by 800335 Bug #800339 [wnpp] ITP: salmon -- wicked-fast transcript quantification from RNA-seq data 800339 was not blocked by any bugs. 800339 was not blocking any bugs. Added blocking bug(s) of 800339: 800335 > block 800339 by 800336 Bug #800339 [wnpp] ITP: salmon -- wicked-fast transcript quantification from RNA-seq data 800339 was blocked by: 800335 800339 was not blocking any bugs. Added blocking bug(s) of 800339: 800336 > block 800339 by 800337 Bug #800339 [wnpp] ITP: salmon -- wicked-fast transcript quantification from RNA-seq data 800339 was blocked by: 800335 800336 800339 was not blocking any bugs. Added blocking bug(s) of 800339: 800337 > End of message, stopping processing here. Please contact me if you need assistance. -- 800339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800339 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > retitle 778589 "ITP: berkeley-express -- Streaming quantification for high Bug #778589 [wnpp] ITP: express -- Streaming quantification for high-throughput sequencing Changed Bug title to '"ITP: berkeley-express -- Streaming quantification for high' from 'ITP: express -- Streaming quantification for high-throughput sequencing' > throughput sequencing" Unknown command or malformed arguments to command. > End of message, stopping processing here. Please contact me if you need assistance. -- 778589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > owner 787977 debian-med-packag...@lists.alioth.debian.org Bug #787977 [wnpp] ITP: smrtanalysis -- software suite for single molecule, real-time sequencing Owner changed from Debian Med Packaging Team to debian-med-packag...@lists.alioth.debian.org. > owner 787982 debian-med-packag...@lists.alioth.debian.org Bug #787982 [wnpp] ITP: python-pbh5tools -- tools for manipulating HDF5 files produced by, Pacific Biosciences sequencing instruments Owner changed from Debian Med Packaging Team to debian-med-packag...@lists.alioth.debian.org. > -- Stopping processing here. Please contact me if you need assistance. -- 787977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787977 787982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.14380695928589.transcr...@bugs.debian.org
Re: your mail
Dear Hervé and Steffen, On Mon, Jul 13, 2015 at 02:16:57PM +, Hervé Ménager wrote: > Dear all, > I and Steffen are currently meeting at ISMB2015 to discuss and hack the > description of debian-med packages using EDAM. We will try to come up with > a workable solution. Please get in touch if you'd like to make comments or > suggestions regarding this. nice to see you working on this. I'd happily provide comments - but where can I see anything to comment on? Kind regards and have fun at ISMB2015 Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150713145726.gg17...@an3as.eu
Re: your mail
On Sun, Jul 22, 2012 at 11:31:37AM -0400, Yaroslav Halchenko wrote: > On Sun, 22 Jul 2012, Andreas Tille wrote: > > you are directly addressing Yaroslav and thus I will not actively look > > into this until further notice. However, I would like to do some > > comment: The fields Vcs-Git and Vcs-Browser should point to the > > repository where the Debian packaging is done and should be probably on > > git.debian.org. If I were your sponsor I would request this. > > well, technically speaking there is no strict requirement to host packaging > repository on git.debian.org That's correct - I just explained that *I* as a sponsor would request this. There are a lot of very good reasons to use git.debian.org and that's why I have this personal policy. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120722190348.gd23...@an3as.eu
Re: your mail
1. On Sun, 22 Jul 2012, Andreas Tille wrote: > you are directly addressing Yaroslav and thus I will not actively look > into this until further notice. However, I would like to do some > comment: The fields Vcs-Git and Vcs-Browser should point to the > repository where the Debian packaging is done and should be probably on > git.debian.org. If I were your sponsor I would request this. well, technically speaking there is no strict requirement to host packaging repository on git.debian.org but it is indeed strongly encouraged! Somewhat stronger advisory (almost requirement) is to point to the repository which has a branch with debian/ packaging in its default HEAD -- that seems to be the case (although once again it is outdated so do not know if building package out of its fresh git clone would work just fine with dpkg-buildpackage ;-) ) My concern is already existing proliferation of different git repositories especially that the one pointed by Vcs-git field is already outdated I believe (carries 0.11 packaging): Vcs-Git: git://github.com/hmmr/cnrun.git Vcs-Browser: http://cnrun.git.sourceforge.net/git/gitweb-index.cgi so please make your choice ;-) 2. there is no need to upload to experimental since this is a NEW pkg -- target unstable 3. "building on original work by Thomas Nowotny " so I guess worth adjusting debian/copyright? ;-) I will try building it meanwhile ;-) cheers -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120722153137.gj21...@onerussian.com
Re: your mail
Hi Andrei,
you are directly addressing Yaroslav and thus I will not actively look
into this until further notice. However, I would like to do some
comment: The fields Vcs-Git and Vcs-Browser should point to the
repository where the Debian packaging is done and should be probably on
git.debian.org. If I were your sponsor I would request this.
Kind regards
Andreas.
On Sun, Jul 22, 2012 at 01:28:09AM +0300, andrei zavada wrote:
> Hi Yaroslav,
>
> Following up on the just filed ITP for my new package, cnrun: here's
> the dsc link:
> http://johnhommer.com//academic/code/cnrun/source/deb/cnrun_1.1.12-1.dsc.
>
> Herewith kindly requesting my trusty mentor to do the final QA and
> build and upload. I verified the build my end using nd_build for
> {nd+,}debian wheezy and sid, and also for ubuntu precise.
>
> Hope this one goes without a hitch.
>
> Cheers,
> Andrei
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120721230852.gi21...@an3as.eu
Re: your mail
Hi Yaroslav, Thanks a lot for the sponsorship! What about an i386 package? Shall I build some and post it to where you can fetch it, like we did with amd64.deb? Cheers, Andrei On Tue, 3 Jan 2012 19:53:04 -0500 Yaroslav Halchenko wrote: > ok -- please find attached the slightly corrected version -- this should > be sufficient -- reupload and I think we should be ready to go -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120104144226.486b6e0b@christian
Re: your mail
Yaroslav Halchenko wrote: > ok -- please find attached the slightly corrected version -- this should > be sufficient -- reupload and I think we should be ready to go Done, uploaded to the same URL. -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/28744.1325639515@ra
Re: your mail
ok -- please find attached the slightly corrected version -- this should be sufficient -- reupload and I think we should be ready to go On Wed, 04 Jan 2012, andrei zavada wrote: > I am uploading the same version 0.4.4-1 again, but with debian/copyright > and changelog amended: > http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_0.4.4-1.dsc -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: Aghermann Upstream-Contact: Andrei Zavada Source: http://johnhommer.com/academic/code/aghermann/source/ Files: * Copyright: 2008-2012 Andrei Zavada License: GPL-2+ Files: src/libexstrom/exstrom.hh Copyright: 2007 Exstrom Laboratories LLC http://www.exstrom.com License: GPL-2+ Files: src/libsigfile/psd.hh Copyright: 1980-2010 George B. Moody License: LGPL-2 This library is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. . This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Library General Public License for more details. . On Debian systems, the full text of the GNU Library General Public License version 2 can be found in the file `/usr/share/common-licenses/LGPL-2'. License: GPL-2+ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. . This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. . You should have received a copy of the GNU General Public License along with this package; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA . On Debian systems, the full text of the GNU General Public License version 2 can be found in the file `/usr/share/common-licenses/GPL-2'. signature.asc Description: Digital signature
Re: your mail
Hi, I am uploading the same version 0.4.4-1 again, but with debian/copyright and changelog amended: http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_0.4.4-1.dsc Cheers -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/17624.1325636998@ra
Re: aghermann for debian-med (was: Your mail)
On Tue, 3 Jan 2012 08:51:02 -0500 Yaroslav Halchenko wrote: > Sorry -- I just can't parse this: -- somewhat really liked wrapping > things up: Ok, I've had enough of gmail in a browser. I'm switching to claws immediately. This is the original snip: --- Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Upstream-Name: Aghermann Upstream-Contact: Andrei Zavada Source: http://johnhommer.com/academic/code/aghermann/source/ Files: * Copyright: 2008-2012 Andrei Zavada License: GPL-2+ Files: src/libexstrom/exstrom.hh Copyright: 2007 Exstrom Laboratories LLC http://www.exstrom.com License: GPL-2+ Files: src/libsigfile/psd.hh Copyright: 1980-2010 George B. Moody License: LGPL-2 --- -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120103160124.0e07a569@christian
Re: your mail
Sorry -- I just can't parse this: -- somewhat really liked wrapping things up: > ---8<--- > Format: > http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/Upstream-Name: > AghermannUpstream-Contact: Andrei Zavada Source: > http://johnhommer.com/academic/code/aghermann/source > Files: *Copyright: 2008-2012 Andrei Zavada License: > GPL-2+ > Files: src/libexstrom/exstrom.hhCopyright: 2007 Exstrom Laboratories > LLC http://www.exstrom.comLicense: GPL-2+ > Files: src/libsigfile/psd.hhCopyright: 1980-2010 George B. Moody > License: LGPL-2 > ---8<--- > The file includes the text of a short version of GPL-2 (even though > the guide says citing common licenses like this is not necessary). I > know including the full text will not hurt; but perhaps I should > either also include the text of LGPL-2, or exclude both? Is it ok to > exclude the text of both licenses altogether (as I provisorily did)? yes -- it was good as it was before, just needed few missing entries and separate line with License: GPL-2+ -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120103135102.gw16...@onerussian.com
Re: your mail
Hi Yaroslav, On 3 January 2012 02:16, Yaroslav Halchenko wrote: > * Author: Andrei Zavada > * Parts from PhysioToolKit > (http://www.physionet.org/physiotools, > * by George B. Moody (geo...@mit.edu)) After studying debian maintainer's guide, I changed it as follows: ---8<--- Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/Upstream-Name: AghermannUpstream-Contact: Andrei Zavada Source: http://johnhommer.com/academic/code/aghermann/source Files: *Copyright: 2008-2012 Andrei Zavada License: GPL-2+ Files: src/libexstrom/exstrom.hhCopyright: 2007 Exstrom Laboratories LLC http://www.exstrom.comLicense: GPL-2+ Files: src/libsigfile/psd.hhCopyright: 1980-2010 George B. Moody License: LGPL-2 ---8<--- The file includes the text of a short version of GPL-2 (even though the guide says citing common licenses like this is not necessary). I know including the full text will not hurt; but perhaps I should either also include the text of LGPL-2, or exclude both? Is it ok to exclude the text of both licenses altogether (as I provisorily did)? > > additionally IIRC according to DEP-5 shouldn't have double Copyright: fields > > Copyright: 2007 Exstrom Laboratories LLC > 2010-2012 Andrei Zavada > > also add 'License: GPL-2+' prior that detached paragraph with the license (I > know that here it would look like a duplicate but actually it just opens the > paragraph and tells what it is about, so those references to GPL-2+ license > now > have the 'destination') Fixed. > also the last (most recent) changelog entry should close the ITP, so should > be something like > > Initial Debian release (Closes: #650393) and distribution could be > changed from UNRELEASED to unstable. Now the topmost entry in debian changelog goes: ---8<--- aghermann (0.4.4-1) unstable; urgency=low * Initial Debian release (Closes: #650393). * Version bump. ---8<--- If the proposed changes are ok, I'll make them into a tarball and upload in some 10h. Cheers, Andrei -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADRQDB03XpMmUsVZrnq72DP1iFbahv+D8iwfARRaX_KeWVR=b...@mail.gmail.com
Re: your mail
1. heh -- debian/copyright seems still to need some work just ran into * Author: Andrei Zavada * Parts from PhysioToolKit (http://www.physionet.org/physiotools, * by George B. Moody (geo...@mit.edu)) additionally IIRC according to DEP-5 shouldn't have double Copyright: fields Copyright: 2007 Exstrom Laboratories LLC 2010-2012 Andrei Zavada also add 'License: GPL-2+' prior that detached paragraph with the license (I know that here it would look like a duplicate but actually it just opens the paragraph and tells what it is about, so those references to GPL-2+ license now have the 'destination') 2. also the last (most recent) changelog entry should close the ITP, so should be something like Initial Debian release (Closes: #650393) and distribution could be changed from UNRELEASED to unstable. will build it now and let you know if I run into anything else On Tue, 03 Jan 2012, andrei zavada wrote: > Hi Yaroslav, > > I am still to do a quick code-review and testing and then with > > those copyright file changes we might be all set to go > The rest of the holidays (green tea works!) was actually quite > productive, and here's version 0.4.4 for your code-reviewing pleasure. > I've even updated copyright year in various files. Find it at the > usul place on johnhommer.com/academic/code/aghermann/sources/deb. > Cheers, > Andrei -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120103001626.gu16...@onerussian.com
Re: your mail
Hi Yaroslav, > I am still to do a quick code-review and testing and then with > those copyright file changes we might be all set to go The rest of the holidays (green tea works!) was actually quite productive, and here's version 0.4.4 for your code-reviewing pleasure. I've even updated copyright year in various files. Find it at the usul place on johnhommer.com/academic/code/aghermann/sources/deb. Cheers, Andrei -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cadrqdb0kbi4qv46s5a+2z90tcz59kcurc0vpudqjpodkiqs...@mail.gmail.com
Re: your mail
> once again -- would be nice if you verify that I can get them:My bad, too > much typos, sorry. Yes, the source tarball should not have "-1" in the file > name; I renamed it at johnhommer.com/... > BTW -- you might like to discover the tool 'dput' so you could just give it a > .changes files and it would upload it to your server (just configure > ~/.dput.cf > correspondingly).. e.g. I have Good advice indeed, the only catch being that my hosting provider will not authenticate me by a ssh key, only by password. I tend to think, though, that my account at alioth would serve this purpose better. I'll set up dput once I get to my home laptop. >> > you need to list src/libexstropm/exstrom.hh copyright holder/license >> > since you derived from their work (if I got it right) >> The license and proper attribution of original C code are all actually >> there; perhaps you want it to appear *strictly* in the header (i.e., >> without any code coming in between parts of the header)? Assuming my >> guess is right, I made cosmetic changes in libexstrom/exstrom.hh >> header to this effect, as you can see here: >> https://github.com/hmmr/aghermann/blob/master/src/libexstrom/exstrom.hh. > debian/copyright must list all copyright/license's for what is shipped in the > sources. At the moment it has only > > > Files: * > Copyright: 2008-2011 Ulla Upstream > License: GPL-2+ Oh such a shame... "Ulla Upstream" is a copypasto directly from Debian maintainer guide! Fixed and pushed to github. > so it needs additional entry Fixed. Now, I've uploaded aghermann_0.3.4.5.orig.tar.bz2 to johnhommer.com/academic/code/aghermann/source/deb; the corresponding .dsc will follow in a few hours. However, other than the copyright fixes we dealt with above, the new version is identical to the 0.3.4.4, and therefore the older one should be buildable (or not) from the .dsc. Now that I renamed the source tarball, I suggest you try to build it (so we can at least get past the build-depends issue)? We can do it before going to table! :} Cheers -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADRQDB0ESJdk6oELJ32O21evwrrTkodzLHSnSDr=xx+zhvb...@mail.gmail.com
Re: your mail
On Fri, 30 Dec 2011, andrei zavada wrote:
> Indeed, I misunderestimated build-depends, now corrected. Strange
> that debuild did not complain about unsatisfied build dependencies,
> contrary to what `debuild --help` says ("option -D enabled by
> default"). After passing -D explicitly to debuild, I was able to sort
> this one out.
;-) you just misunderstood the meaning of -D -- it checks that those
build-depends listed in your Build-Depends are present on the system
where you are trying to build. in your case you pretty much didn't have
any build-depends specified (e.g. boost libs etc)
> Humbly asking to give it one last try before the NY, grab it here:
> https://sourceforge.net/projects/aghermann/files/deb/amd64/
> (johnhommer.com seems to have a glitch or whatever at the moment).
oh no... please no sf with it mad set of redirects etc... I would be
grateful if you just verify that you can "dget http://URL_TO.dsc"; and
get all needed sources to build
in this case you also forgotten .orig.tar.gz for 0.4.3.4 so I can't even
try to build
also quickly looked at debian/copyright
you need to list src/libexstropm/exstrom.hh copyright holder/license
since you derived from their work (if I got it right)
> Cheers,
> Andrei
--
=--=
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111230011431.gf15...@onerussian.com
Re: your mail
Hi Yaroslav,
Indeed, I misunderestimated build-depends, now corrected. Strange
that debuild did not complain about unsatisfied build dependencies,
contrary to what `debuild --help` says ("option -D enabled by
default"). After passing -D explicitly to debuild, I was able to sort
this one out.
Humbly asking to give it one last try before the NY, grab it here:
https://sourceforge.net/projects/aghermann/files/deb/amd64/
(johnhommer.com seems to have a glitch or whatever at the moment).
Cheers,
Andrei
On 28 December 2011 01:19, Yaroslav Halchenko wrote:
> Hi Andrei,
>
> damn holidays keep us away from all the fun!... before reply in full --
> regarding build-depends -- did you try/build in a clean
> environment (e.g. using pbuilder or cowbuilder?) if not -- give it a
> shout and then adjust build-depends accordingly ;)
>
> here is my protocol of 'struggle':
> http://www.onerussian.com/tmp/aghermann_0.4.3.3-1_amd64.build
>
> Cheers
>
> On Sun, 25 Dec 2011, andrei zavada wrote:
>
>> Hi Yaroslav,
>
>> Sorry for taking a week to respond. There was not a single day last
>> week I could have a contiguous space of one hour to address the
>> issues.
> --
> =--=
> Keep in touch www.onerussian.com
> Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CADRQDB14b09jE9+HjORr=FYyrLjnjm3rmbeEO=-quit-rjl...@mail.gmail.com
Re: your mail
Hi Andrei, damn holidays keep us away from all the fun!... before reply in full -- regarding build-depends -- did you try/build in a clean environment (e.g. using pbuilder or cowbuilder?) if not -- give it a shout and then adjust build-depends accordingly ;) here is my protocol of 'struggle': http://www.onerussian.com/tmp/aghermann_0.4.3.3-1_amd64.build Cheers On Sun, 25 Dec 2011, andrei zavada wrote: > Hi Yaroslav, > Sorry for taking a week to respond. There was not a single day last > week I could have a contiguous space of one hour to address the > issues. -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111227231936.gj15...@onerussian.com
Re: your mail
Hi Yaroslav, Sorry for taking a week to respond. There was not a single day last week I could have a contiguous space of one hour to address the issues. > there is 1 more crucial step: projects which are not Debian specific > should not be packaged in "native debian" format, i.e. when you > have only .orig.tar.gz + .dsc -- they should have .diff.gz or > .debian.tar.gz ( source format quilt 3.0, which I would recommend to use > as well) , and their version must include debian revision... I set up quilt, but there is no .diff.gz as there is no patches, for the simple reason that the communication between maintainer (me) and the upstream (me again) never leaves localhost. The newly created debian/source/format now contains "3.0 (quilt)". I also set up pbuilder, and with little effort, it successfully builds aghermann from upstream tarball (after renaming aghermann-0.4.3.3.tar.bz2 to aghermann_0.4.3.3.orig.tar.bz2). And, no warnings from lintian. > so if 0.4.3.2 is the "upstream" release number, debian release should be > 0.4.3.2-1 and version in debian/changelog should be adjusted > accordingly. My changelog now has all entries as you suggest. Also, "unstable" is replaced with "UNRELEASED" throughout. > looking at > https://github.com/hmmr/aghermann/blob/master/debian/control > it looks incomplete -- have you tried to build the package in a clean > environment (e.g. using pbuilder, or git-pbuilder if you use > git-buildpackage, or cowbuilder)? On this point, I'd like to clarify that I would rather do Debian releases from upstream tarballs (i.e., as produced by "make dist-bzip2" and not directly from Git). As matters stand, git snapshots can be buggy, or not in a buildable state at all. Put differently, the workflow goes like this: (1) make dist-bzip2 when it's ready and upload to the URL mentioned in debian/watch; (2) fetch it, rename replacing '-' with '_' and inserting '.orig'; (3) untar, cd and debuild. > having vcs- fields (useful for debcheckout) would be + as well I did add vcs entries, but as I said above, I don't propose to build from git, so perhaps vcs- fields are not applicable? > I bet you lack build-depends My debian/control file contiained: "Build-Depends: debhelper (>= 7)". As g++ >= 4.6.2 is required, I changed this record accordingly. > https://github.com/hmmr/aghermann/blob/master/debian/copyright > I would strongly recommend to convert it to use DEP-5: > http://dep.debian.net/deps/dep5/ Done. > Do you have GPG key btw? doesn't have to be signed by a DD (yet) but it > would be great to identify at least that we are talking to the same > person ;-) so, just sign you source package (debsign) and either upload > to mentors.debian.org (preferrable) or make it available anywhere else > -- I could then grab it from there, do review, build, upload (if > everything is ok of cause) Now I have a PGP key associated with this email address (public part is available here: http://johnhommer.com/academic/pgpkey, and also uploaded to subkeys.pgp.net). > 4. alioth project -- probably others could comment on that ... but we > don't need to wait -- for me to do final review and sponsor its upload > to Debian I would just need source package (.orig.tar.gz + .dsc + > .debian.tar.gz or .diff.gz) . Oh, I was probably missing something dead obvious here... Alioth being suspiciously similar to berlios.de (where I tried to host my git tree before giving up in favour of github.com), I suspect I might/should be able to eventually do git push to. After poking around a second time, I did git init and git clone in my ~ at aghermann.alioth.debian.org, and then it was the Aha moment.. :} Now, the corresponding record in .git/config is: [remote "origin-da"] url = ssh://hmmr-gu...@aghermann.alioth.debian.org/home/users/hmmr-guest/public.git/aghermann fetch = +refs/heads/*:refs/remotes/origin-da/* So this should be it. Again, sorry for confusion. Finally, I have uploaded all the files produced by debuild to johnhommer.com/academic/code/aghermann/source, and pushed the last changes to github.com/hmmr/aghermann, much hopeful this time I will pass :} Cheers -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADRQDB0Jg9TJ+92kcxWxeso=s+ejrtsebdqgg9s3ozgdhv0...@mail.gmail.com
Aghermann packaging (Was: your mail)
Hi, On Tue, Dec 20, 2011 at 07:07:16PM -0500, Yaroslav Halchenko wrote: > > also I myself do that and recommend others -- I leave changelog entries > with UNRELEASED (or neurodebian ;-) ) instead of unstable unless it > actually got into unstable. That helps later on to see which versions > made into Debian just by looking at the changelog Yes! Please regard http://debian-med.alioth.debian.org/docs/policy.html#debian-changelog > 2. > looking at > https://github.com/hmmr/aghermann/blob/master/debian/control > it looks incomplete -- have you tried to build the package in a clean > environment (e.g. using pbuilder, or git-pbuilder if you use > git-buildpackage, or cowbuilder)? I bet you lack build-depends > > having vcs- fields (useful for debcheckout) would be + as well See item 8. in http://debian-med.alioth.debian.org/docs/policy.html#debian-control > 3. > https://github.com/hmmr/aghermann/blob/master/debian/copyright > I would strongly recommend to convert it to use DEP-5: > http://dep.debian.net/deps/dep5/ See http://debian-med.alioth.debian.org/docs/policy.html#debian-copyright > 4. alioth project -- probably others could comment on that ... but we > don't need to wait -- for me to do final review and sponsor its upload > to Debian I would just need source package (.orig.tar.gz + .dsc + > .debian.tar.gz or .diff.gz) . Lacking the original question I can not properly comment on this. If the question was whether you should upload before commiting the code to Alioth I'd say it is no precondition but definitely helps. If you want to set Vcs fields properly and valid (see question 2.) it should be quite logical that you should commit to Alioth first and finally it is not that much of work. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111221083518.gb12...@an3as.eu
Re: your mail
Hi Andrei, congrats on becoming friends with lintian ;) 1. there is 1 more crucial step: projects which are not Debian specific should not be packaged in "native debian" format, i.e. when you have only .orig.tar.gz + .dsc -- they should have .diff.gz or .debian.tar.gz ( source format quilt 3.0, which I would recommend to use as well) , and their version must include debian revision... so if 0.4.3.2 is the "upstream" release number, debian release should be 0.4.3.2-1 and version in debian/changelog should be adjusted accordingly. also I myself do that and recommend others -- I leave changelog entries with UNRELEASED (or neurodebian ;-) ) instead of unstable unless it actually got into unstable. That helps later on to see which versions made into Debian just by looking at the changelog 2. looking at https://github.com/hmmr/aghermann/blob/master/debian/control it looks incomplete -- have you tried to build the package in a clean environment (e.g. using pbuilder, or git-pbuilder if you use git-buildpackage, or cowbuilder)? I bet you lack build-depends having vcs- fields (useful for debcheckout) would be + as well 3. https://github.com/hmmr/aghermann/blob/master/debian/copyright I would strongly recommend to convert it to use DEP-5: http://dep.debian.net/deps/dep5/ 4. alioth project -- probably others could comment on that ... but we don't need to wait -- for me to do final review and sponsor its upload to Debian I would just need source package (.orig.tar.gz + .dsc + .debian.tar.gz or .diff.gz) . Do you have GPG key btw? doesn't have to be signed by a DD (yet) but it would be great to identify at least that we are talking to the same person ;-) so, just sign you source package (debsign) and either upload to mentors.debian.org (preferrable) or make it available anywhere else -- I could then grab it from there, do review, build, upload (if everything is ok of cause) Cheers On Tue, 20 Dec 2011, andrei zavada wrote: > Hi Yaroslav, > After learning some Makefile.am-fu, aghermann-0.4.3.2 is now > lintian-clean: the single remaining .so file is stowed into > /usr/lib/aghermann. Please have a look at sf.net/projects/aghermann > or review it online at gihub.com/hmmr/aghermann (there is an > -amd64.deb, too). > What do I do next? Whatever I do, I understand the powers that be > would first approve my project at alioth, right? I am patiently > waiting for this to happen, sigh.. > Cheers, > Andrei > On 11 December 2011 17:31, Yaroslav Halchenko wrote: > > Hi Andrei, > > Great -- thanks. > > Since the library is "internal" ideal resolution imho would be to hide > > it away under usr/lib/aghermann/ and link all binaries against it > > (rpath). that should take care about lintian issues ;) > > On Sun, 11 Dec 2011, andrei zavada wrote: > >> Hi Yaroslav, > >> I have fixed all lintian issues with Aghermann except this one: > >> W: aghermann: package-name-doesnt-match-sonames libsigfile0 > >> W: aghermann: non-dev-pkg-with-shlib-symlink usr/lib/libsigfile.so.0.0.0 > >> usr/lib/libsigfile.so > >> This libsigfile is an internal library which is used by the main > >> executable (aghermann) and by two accessory programs contained in the > >> same package. I tend to think splitting the whole project in three > >> (aghermann, libsigfile and aghermann-tools) would be a little overkill, > >> and that simply overriding this warning might be sufficient, for now. > >> What do you think? > >> Other than that, as of the latest version (0.4.3.1) Aghermann is ready > >> for packaging AFAICT. I am still waiting for the admission approval from > >> Alioth admins, though. > > -- > > =--= > > Keep in touch www.onerussian.com > > Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111221000716.gl15...@onerussian.com
Re: your mail
Hi Yaroslav, After learning some Makefile.am-fu, aghermann-0.4.3.2 is now lintian-clean: the single remaining .so file is stowed into /usr/lib/aghermann. Please have a look at sf.net/projects/aghermann or review it online at gihub.com/hmmr/aghermann (there is an -amd64.deb, too). What do I do next? Whatever I do, I understand the powers that be would first approve my project at alioth, right? I am patiently waiting for this to happen, sigh.. Cheers, Andrei On 11 December 2011 17:31, Yaroslav Halchenko wrote: > Hi Andrei, > > Great -- thanks. > > Since the library is "internal" ideal resolution imho would be to hide > it away under usr/lib/aghermann/ and link all binaries against it > (rpath). that should take care about lintian issues ;) > > On Sun, 11 Dec 2011, andrei zavada wrote: > >> Hi Yaroslav, > >> I have fixed all lintian issues with Aghermann except this one: > >> W: aghermann: package-name-doesnt-match-sonames libsigfile0 >> W: aghermann: non-dev-pkg-with-shlib-symlink usr/lib/libsigfile.so.0.0.0 >> usr/lib/libsigfile.so > >> This libsigfile is an internal library which is used by the main >> executable (aghermann) and by two accessory programs contained in the >> same package. I tend to think splitting the whole project in three >> (aghermann, libsigfile and aghermann-tools) would be a little overkill, >> and that simply overriding this warning might be sufficient, for now. >> What do you think? > >> Other than that, as of the latest version (0.4.3.1) Aghermann is ready >> for packaging AFAICT. I am still waiting for the admission approval from >> Alioth admins, though. > > -- > =--= > Keep in touch www.onerussian.com > Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADRQDB0_ZAwoibebWsJgsY1F8TVJC5QDjwJTjÞoiwvm1x...@mail.gmail.com
Re: your mail
Hi Andrei, Great -- thanks. Since the library is "internal" ideal resolution imho would be to hide it away under usr/lib/aghermann/ and link all binaries against it (rpath). that should take care about lintian issues ;) On Sun, 11 Dec 2011, andrei zavada wrote: > Hi Yaroslav, > I have fixed all lintian issues with Aghermann except this one: > W: aghermann: package-name-doesnt-match-sonames libsigfile0 > W: aghermann: non-dev-pkg-with-shlib-symlink usr/lib/libsigfile.so.0.0.0 > usr/lib/libsigfile.so > This libsigfile is an internal library which is used by the main > executable (aghermann) and by two accessory programs contained in the > same package. I tend to think splitting the whole project in three > (aghermann, libsigfile and aghermann-tools) would be a little overkill, > and that simply overriding this warning might be sufficient, for now. > What do you think? > Other than that, as of the latest version (0.4.3.1) Aghermann is ready > for packaging AFAICT. I am still waiting for the admission approval from > Alioth admins, though. -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111211153118.go2...@onerussian.com
