Re: Help needed with updating some Java libraries (netlib-java, libmtj-java)
On 08/29/2014 02:38 AM, tony mancill wrote: > On 08/28/2014 07:01 AM, Andreas Tille wrote: >> Hi, >> >> when checking my Maintainer dashboard dashboard I realised that the >> watch file of netlib-java and libmtj-java became disfunctional and when >> tracking down the issue I noticed that both projects moved from SF to >> Github. While I updated the URLs in SVN accordingly I noticed that the >> Build system has changed as well which just crosses my (low) level of >> Java competence (again). >> >> Since both packages are definitely not really in the field of Debian Med >> but just preconditions for some biological package (beast) I wonder >> whether this might be the right point in time to move the package to >> Debian Java. I'd volunteer to inject the package into Debian Java Git >> but in turn I would need some help (starting with netlib-java). I have >> the feeling that the amount of work for a skilled Java packager is low >> (but I really would not regard myself as such a person). >> >> BTW, the packages are hanging around in contrib since netlib depends >> from f2j (at least the current version). I'll send a separate mail to >> f2j authors to try (again) to convince them to use a DFSG free license. >> >> Kind regards >> >> Andreas. >> > Hello Andreas, > > If you're willing to migrate these to the pkg-java repo, I'll work on > updating them and uploading them as Java Team packages. > > Also, I've been meaning to send you a mail regarding libsnappy-java, > since we have an RC bug there. The last commit makes it appear that you > were considering moving it debian-med in 2012. Is that still the case? We have a libsnappy-java version available in DebianMed [0], but a specific release (certainly due to a package which needed this specific release and upstream broke its API). I do not know if we need to manage snappy by itself in DebianMed repo as it has nothing related to bio/med but is only a dependency. [0] https://packages.qa.debian.org/s/snappy1.0.3-java.html Olivier > > Cheers, > tony > -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- 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/54001c42.9070...@irisa.fr
Re: Help needed with updating some Java libraries (netlib-java, libmtj-java)
On 08/28/2014 07:01 AM, Andreas Tille wrote: > Hi, > > when checking my Maintainer dashboard dashboard I realised that the > watch file of netlib-java and libmtj-java became disfunctional and when > tracking down the issue I noticed that both projects moved from SF to > Github. While I updated the URLs in SVN accordingly I noticed that the > Build system has changed as well which just crosses my (low) level of > Java competence (again). > > Since both packages are definitely not really in the field of Debian Med > but just preconditions for some biological package (beast) I wonder > whether this might be the right point in time to move the package to > Debian Java. I'd volunteer to inject the package into Debian Java Git > but in turn I would need some help (starting with netlib-java). I have > the feeling that the amount of work for a skilled Java packager is low > (but I really would not regard myself as such a person). > > BTW, the packages are hanging around in contrib since netlib depends > from f2j (at least the current version). I'll send a separate mail to > f2j authors to try (again) to convince them to use a DFSG free license. > > Kind regards > > Andreas. > Hello Andreas, If you're willing to migrate these to the pkg-java repo, I'll work on updating them and uploading them as Java Team packages. Also, I've been meaning to send you a mail regarding libsnappy-java, since we have an RC bug there. The last commit makes it appear that you were considering moving it debian-med in 2012. Is that still the case? Cheers, tony signature.asc Description: OpenPGP digital signature
Re: Status bowtie + tophat (Was: [Help] Need help for architecture specific code)
Le Thu, Aug 28, 2014 at 11:04:10AM +0200, Andreas Tille a écrit : > > I rephrase: Does anybody have a better idea to get tophat into testing > than simply restrict it to amd64? Hi Andreas, this is fine with me. I actually wonder if we should not restrict such programs to amd64 by default, and only extend their architecture coverage on demand. That would save us some precious time, and to porters too. Have a nice day, Charles -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- 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/20140828221241.ga17...@falafel.plessy.net
Re: [MoM] Packaging Camp for Debian
Hi Corentin, On Thu, Aug 28, 2014 at 04:58:49PM +0200, Corentin Desfarges wrote: > >https://github.com/greenjava/camp/releases > >.*/archive/(\d[\d.-]+)\.(?:tar(?:\.gz|\.bz2)?|tgz) > >(untested, but should work) The "how to download" answer is simply: > >uscan --verbose --force-download > >This is beating two birds with one stone: You *test* the d/watch file > >and *do* the download. Easy, isn't it? > > Yes it is. I was a bit slow to understand, but this time, I've understood. :-) > >I could do it but I think it is better if you follow the steps described > >in the Debian Med policy (browse [1] a bit down for 'setup-repository'). > >Its easy, be bold, just do it. :-) > > Indeed, it wasn't too hard. ;) +1 > >Hmmm, I'm not sure what you really mean. Is there any problem with > >the code you can download from > >https://github.com/greenjava/camp/releases > >If no, just use it. If yes, what exactly is the problem and what do > >you mean be 'fork'? > > No there is no problem. If a problem happened in the future, it will be fix > with a patch from debian/patches/*, right ? > I've just push what I've done, can you have a look on it ? Its a bit late now for me. But when I had a look at your commits in the afternoon I remember several lintian issues. Please run lintian -i -I *.changes on the resulting packages to learn what might be left to do. I also had seen that the *-dev package was basically empty missing a *.a file and the includes. I have not looked for the last couple of hours when I was offline. 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: https://lists.debian.org/20140828214808.gb16...@an3as.eu
Re: r17823 - in trunk/packages/arb/trunk/debian: . conf patches source
Hi Andreas! I've completed my TODOs and think the package is ready now. Elmar -- 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/53ff7ac9.9030...@pruesse.net
Re: DebianMed sprint, January 2015 - Saint Malo, France
2014-08-28 16:27 GMT+02:00 Tim Booth : > Hi Olivier, > > Looking forward to it! Thanks for organising. > > The most promising transport option for me looks like: > > Friday 30th: > Fly from Southampton to Rennes (arrive 13:35) > Train to St. Malo > Depending on number of person and time arrival in Rennes, I could catch a few on Friday at the airport and go to Saint Malo with my car. Olivier > > Monday 2nd: > Ferry to Portsmouth (10:30 departure) > > I suspect that those from further north in the UK will prefer to just > fly both ways. > > TIM > > On Fri, 2014-08-22 at 09:46 +0100, olivier sallou wrote: > > Hi, > > the next DebianMed sprint will occur at 30/01/15 -> 02/02/15, in Saint > > Malo, France. > > > > > > The wiki page is available for information and registration [0]. > > > > > > There is a pending issue with Wifi at the hotel, I should get more > > info mid-september about this issue. I will send a new notification > > end of september. > > > > > > The hotel has rooms with 2 or 3 beds. Please arrange yourselves to > > share some rooms to lower the cost. Those rooms should be reserved > > soon enough to be sure to get them. > > > > > > I expect to have lunches and breaks sponsored. > > > > > > Please forward the message to anyone interested for participating, > > willing to train to packaging, or simply needing key signing. > > > > > > Do not hesitate to contact me. > > > > > > [0] https://wiki.debian.org/Sprints/2015/DebianMed2015 > > > > > > Olivier > > > > > > -- > Tim Booth > NERC Environmental Bioinformatics Centre > > Centre for Ecology and Hydrology > Maclean Bldg, Benson Lane > Crowmarsh Gifford > Wallingford, England > OX10 8BB > > http://nebc.nerc.ac.uk > +44 1491 69 2705 > -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Re: [MoM] Packaging Camp for Debian
Hi Andreas, This answers the question "from where" but not "how". In "To create a new local git repository" in our policy[1] it is recommended to do svn export svn://anonscm.debian.org/svn/debian-med/trunk/package_template debian I always start with editing the debian/watch file from there and adapt it to the upstream location (here Github release). Once you adapted> the debian/watch file to version=3 https://github.com/greenjava/camp/releases .*/archive/(\d[\d.-]+)\.(?:tar(?:\.gz|\.bz2)?|tgz) (untested, but should work) The "how to download" answer is simply: uscan --verbose --force-download This is beating two birds with one stone: You *test* the d/watch file and *do* the download. Easy, isn't it? Yes it is. I was a bit slow to understand, but this time, I've understood. >>And first, does this repository already exist ? Because I can't >>clone it for now, and I don't see it anywhere... >This repository does not yet exist ... I just "invented" this string for >the moment. :-) Fine! Is it to me to create it ? (When I will be in the team) I could do it but I think it is better if you follow the steps described in the Debian Med policy (browse [1] a bit down for 'setup-repository'). Its easy, be bold, just do it. :-) Indeed, it wasn't too hard. ;) Hmmm, I'm not sure what you really mean. Is there any problem with the code you can download from https://github.com/greenjava/camp/releases If no, just use it. If yes, what exactly is the problem and what do you mean be 'fork'? No there is no problem. If a problem happened in the future, it will be fix with a patch from debian/patches/*, right ? I've just push what I've done, can you have a look on it ? Thank you! Corentin -- 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/53ff43a9.1070...@gmail.com
Re: DebianMed sprint, January 2015 - Saint Malo, France
Hi Olivier, Looking forward to it! Thanks for organising. The most promising transport option for me looks like: Friday 30th: Fly from Southampton to Rennes (arrive 13:35) Train to St. Malo Monday 2nd: Ferry to Portsmouth (10:30 departure) I suspect that those from further north in the UK will prefer to just fly both ways. TIM On Fri, 2014-08-22 at 09:46 +0100, olivier sallou wrote: > Hi, > the next DebianMed sprint will occur at 30/01/15 -> 02/02/15, in Saint > Malo, France. > > > The wiki page is available for information and registration [0]. > > > There is a pending issue with Wifi at the hotel, I should get more > info mid-september about this issue. I will send a new notification > end of september. > > > The hotel has rooms with 2 or 3 beds. Please arrange yourselves to > share some rooms to lower the cost. Those rooms should be reserved > soon enough to be sure to get them. > > > I expect to have lunches and breaks sponsored. > > > Please forward the message to anyone interested for participating, > willing to train to packaging, or simply needing key signing. > > > Do not hesitate to contact me. > > > [0] https://wiki.debian.org/Sprints/2015/DebianMed2015 > > > Olivier > > -- Tim Booth NERC Environmental Bioinformatics Centre Centre for Ecology and Hydrology Maclean Bldg, Benson Lane Crowmarsh Gifford Wallingford, England OX10 8BB http://nebc.nerc.ac.uk +44 1491 69 2705 -- 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/1409236024.5164.112.camel@balisaur
[MoM] Please use same version as upstream version in d/changelog [was: [camp] 02/02: add debian/*]
Hi Corentin,
if you wonder why your commit does not work with git-buildpackage just try
diff --git a/debian/changelog b/debian/changelog
index 805b3fc..5fd65fa 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,4 +1,4 @@
-camp (0.7.1-1) UNRELEASED; urgency=low
+camp (0.7.1.1-1) UNRELEASED; urgency=low
* Initial release (Closes: #759244)
Hope this helps
Andreas.
- Forwarded message from Corentin Desfarges
-
Date: Thu, 28 Aug 2014 14:30:51 +
From: Corentin Desfarges
To: debian-med-com...@lists.alioth.debian.org
Subject: [camp] 02/02: add debian/*
This is an automated email from the git hooks/post-receive script.
corentin-guest pushed a commit to branch master
in repository camp.
commit e69cc1e28ea8314b6cb32ab931f277a3fffa61a3
Author: Corentin Desfarges
Date: Thu Aug 28 16:20:47 2014 +0200
add debian/*
---
debian/README.source| 10 +
debian/changelog| 5 +
debian/compat | 1 +
debian/control | 46 +
debian/copyright| 29 ++
debian/patches/add_soname | 11 ++
debian/patches/rm_boost_version | 22
debian/patches/series | 2 ++
debian/postinst | 2 ++
debian/rules| 35 +++
debian/source/format| 1 +
debian/watch| 2 ++
12 files changed, 166 insertions(+)
diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 000..9fe48b2
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,10 @@
+camp for Debian
+---
+
+
+
+
+
+ -- root Wed, 20 Aug 2014 15:02:43 +0200
+
diff --git a/debian/changelog b/debian/changelog
new file mode 100644
index 000..805b3fc
--- /dev/null
+++ b/debian/changelog
@@ -0,0 +1,5 @@
+camp (0.7.1-1) UNRELEASED; urgency=low
+
+ * Initial release (Closes: #759244)
+
+ -- Corentin Desfarges Mon, 25 Aug 2014
16:00:00 +0200
diff --git a/debian/compat b/debian/compat
new file mode 100644
index 000..ec63514
--- /dev/null
+++ b/debian/compat
@@ -0,0 +1 @@
+9
diff --git a/debian/control b/debian/control
new file mode 100644
index 000..2e654a7
--- /dev/null
+++ b/debian/control
@@ -0,0 +1,46 @@
+Source: camp
+Priority: optional
+Maintainer: Corentin Desfarges
+Build-Depends: debhelper (>= 9),
+ cmake,
+ libboost-all-dev
+Standards-Version: 3.9.5
+Section: science
+Homepage: https://github.com/tegesoft/camp
+Vcs-Git: git://git.debian.org/git/debian-med/camp.git
+#Vcs-Browser: http://anonscm.debian.org/?p=collab-maint/camp.git;a=summary
+
+Package: camp
+Architecture: any
+Section: libs
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Description: C++ multi-purpose reflection library
+ CAMP is a multi-purpose reflection library developed by Technogerma Systems
France (http://www.tegesoft.com).
+ It provides an abstraction for most of the high-level concepts of C++
+ - Classes
+ - Enumerations
+ - Properties
+ - Functions
+ - Objects
+ - Variables
+ By wrapping all these concepts into abstract structures, CAMP provides an
extra layer of flexibility to programs, and allow them to fully expose their
data structures at runtime.
+ Many applications can take advantage of CAMP, in order to automate tasks
which would otherwise require a huge amount of work. For example, CAMP can be
used to expose and edit objects' attributes into a graphical user interface. It
can also be used to do automatic binding of C++ classes to script languages
such as Python or Lua.
+ Another possible application would be the serialization of objects to XML,
text or binary formats. Or you can even combine all these examples to provide a
powerful and consistent interface for manipulating your objects outside C++
code.
+
+Package: camp-dev
+Architecture: any
+Section: libdevel
+Depends: camp, ${shlibs:Depends}, ${misc:Depends}
+Description: C++ multi-purpose reflection library
+ CAMP is a multi-purpose reflection library developed by Technogerma Systems
France (http://www.tegesoft.com).
+ It provides an abstraction for most of the high-level concepts of C++
+ - Classes
+ - Enumerations
+ - Properties
+ - Functions
+ - Objects
+ - Variables
+ By wrapping all these concepts into abstract structures, CAMP provides an
extra layer of flexibility to programs, and allow them to fully expose their
data structures at runtime.
+ Many applications can take advantage of CAMP, in order to automate tasks
which would otherwise require a huge amount of work. For example, CAMP can be
used to expose and edit objects' attributes into a graphical user interface. It
can also be used to do automatic binding of C++ classes to script languages
such as Python or Lua.
+ Another possible application would be the serialization of objects to XML,
text or binary formats. Or you can even combine all these examples to provide a
Please help contacting responsible person for f2j (Was: Please consider a free software license)
Hello, I'm writing you on behalf of the Debian Med project which tries to assemble free software in life sciences into Debian to support this field of endevour as best as possible. (Here you can find a list of the packaged software[0].) Currently we are in trouble to bring beast (see on our list) into main Debian since there is some dependency chain which ends in f2c which has a non-free license. F2c was developed at Indiana University and the e-mail address of the contact person Dennis Gannon bounces (and he is also not listed on your web site any more). I wonder whether you might be able to provide us with some valid contact point where we could ask for a free license. Sorry if I just bother you with this topic but I had no better clue than trying to find somebody who might potentially be interested in the work of the Debian Med team. Thanks for considering and kind regards Andreas. [0] http://blends.debian.org/med/tasks/bio - Forwarded message from Andreas Tille - Date: Thu, 28 Aug 2014 16:11:48 +0200 From: Andreas Tille To: Dennis Gannon , Debian Med Project List Cc: Debian Java Maintainers , Keith Seymour Subject: Please condifer a free software license Hi, some time ago there was a discussion[1] about the f2c lincense, specifically about the part goto_trans/* which says: ... it is freely available without fee for education, research, and non-profit purposes. The restriction to certain purposes is considered non-free according to the Open Source definition[2] since item 6. does not allow discrimination against fields of endeavor. We have packaged f2c in Debian format but because of this license it can not become part of Debian but is rather provided in non-free. The problem is that f2c is at the beginning of some chain of dependencies which makes it impossible to put all these into main Debian. Since so far nobody followed Keith's hint[1] to replace the functionality of goto_trans/* by Apache Commons BCEL or something like this I wonder whether you as the author might consider droping the restriction and using a really free license. Thanks for considering Andreas. [1] https://lists.debian.org/debian-med/2012/03/msg00235.html [2] http://opensource.org/osd-annotated -- http://fam-tille.de - End forwarded message - -- 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/20140828142425.gk27...@an3as.eu
Please condifer a free software license
Hi, some time ago there was a discussion[1] about the f2c lincense, specifically about the part goto_trans/* which says: ... it is freely available without fee for education, research, and non-profit purposes. The restriction to certain purposes is considered non-free according to the Open Source definition[2] since item 6. does not allow discrimination against fields of endeavor. We have packaged f2c in Debian format but because of this license it can not become part of Debian but is rather provided in non-free. The problem is that f2c is at the beginning of some chain of dependencies which makes it impossible to put all these into main Debian. Since so far nobody followed Keith's hint[1] to replace the functionality of goto_trans/* by Apache Commons BCEL or something like this I wonder whether you as the author might consider droping the restriction and using a really free license. Thanks for considering Andreas. [1] https://lists.debian.org/debian-med/2012/03/msg00235.html [2] http://opensource.org/osd-annotated -- 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/20140828141148.gj27...@an3as.eu
Help needed with updating some Java libraries (netlib-java, libmtj-java)
Hi, when checking my Maintainer dashboard dashboard I realised that the watch file of netlib-java and libmtj-java became disfunctional and when tracking down the issue I noticed that both projects moved from SF to Github. While I updated the URLs in SVN accordingly I noticed that the Build system has changed as well which just crosses my (low) level of Java competence (again). Since both packages are definitely not really in the field of Debian Med but just preconditions for some biological package (beast) I wonder whether this might be the right point in time to move the package to Debian Java. I'd volunteer to inject the package into Debian Java Git but in turn I would need some help (starting with netlib-java). I have the feeling that the amount of work for a skilled Java packager is low (but I really would not regard myself as such a person). BTW, the packages are hanging around in contrib since netlib depends from f2j (at least the current version). I'll send a separate mail to f2j authors to try (again) to convince them to use a DFSG free license. 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: https://lists.debian.org/20140828140127.gi27...@an3as.eu
Re: [MoM] Your Git commit (Was: [fis-gtm] branch master updated (3a6c8c0 -> c8316bd))
Hi Amul, On Thu, Aug 28, 2014 at 08:51:51AM -0400, Amul Shah wrote: > Hi Andreas, > I apologize for the mix-up. Is there a way for me to back those changes out > of the master branch? At a second thought it might be that nothing really bad has happened. Perhaps you just gbp-clone the current status and redo `git import-orig` to "cure" the mixup. I assume this could work. Otherwise there is some Git documentation out there how to revert commits (I'm no Git expert myself so would need to web-search for it as well). If all else might fail we could recreate the bare Git repository on the server and I'll push my local clone which remains at the state before your latest push. I never tried this but it should work as well. > I will go through the earlier mail and repeat my changes. It looks like I > deleted my GPG keys, so I will regenerate them. It's not the best idea to delete your GPG key. B-) > Thank you for your patience. You are welcome to take the beginners hurdles with our help 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/20140828132230.gh27...@an3as.eu
Re: [MoM] Your Git commit (Was: [fis-gtm] branch master updated (3a6c8c0 -> c8316bd))
Hi Andreas, I apologize for the mix-up. Is there a way for me to back those changes out of the master branch? I will go through the earlier mail and repeat my changes. It looks like I deleted my GPG keys, so I will regenerate them. Thank you for your patience. Regards, Amul On 08/28/14 02:19, Andreas Tille wrote: Hi Amul, as you wrote your latest commits seem to have endet up all in the master branch which is wrong. While we now know, that you are able to commit (which is good) I wonder whether this might become a serious problem for git-buildpackage in the long run. Please try to follow the step by step instructions I have given in my other mail. Kind regards Andreas. On Thu, Aug 28, 2014 at 04:13:53AM +, Amul Shah wrote: This is an automated email from the git hooks/post-receive script. tuskentower-guest pushed a change to branch master in repository fis-gtm. from 3a6c8c0 Updated Standards version to 3.9.5. new 880ee72 Imported Upstream version 6.1-000 new e8b7885 Merge tag 'upstream/6.1-000' new 90715ea Patch maintenance new c8316bd Update versions and changelog The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: CMakeLists.txt |92 +- README |20 +- debian/changelog | 7 +- debian/control | 9 +- debian/copyright | 2 +- debian/patches/install_help_files.patch|14 - debian/patches/series | 4 +- ...estdir_Refactor-object-file-source-name-storage |22 +- ...pport-source-to-object-compilation-in-a-DESTDIR | 4 +- debian/patches/up_gtm_destdir_substitution |10 +- debian/patches/upstream_backport_README_change |24 + .../upstream_backport_i586_default_32bit_linux |21 + sr_avms/release_name.h | 4 +- sr_i386/emit_code.c| 206 +- sr_i386/gdeerrors_ctl.c|64 +- sr_i386/merrors_ansi.h |35 +- sr_i386/merrors_ctl.c |82 +- sr_i386/ttt.c | 792 +- sr_linux/gtm_env_sp.csh| 3 +- sr_linux/release_name.h|12 +- sr_port/act_in_gvt.c |37 +- sr_port/alias_funcs.c | 4 +- sr_port/anticipatory_freeze.h |14 +- sr_port/buddy_list.h | 4 +- sr_port/cdbg_dump.c|29 +- sr_port/cdbg_dump.h| 3 +- sr_port/collseq.h |13 +- sr_port/compiler.h |92 +- sr_port/compiler_ch.c | 4 +- sr_port/compiler_startup.c |40 +- sr_port/cre_jnl_file.c |58 +- sr_port/cre_private_code_copy.c| 9 +- sr_port/create_dummy_gbldir.c |85 +- sr_port/dbcertify_base_ch.c|76 +- sr_port/dbcertify_scan_phase.c |44 +- sr_port/deviceparameters.c |32 +- sr_port/dfa_calc.c |16 +- sr_port/dpgbldir.c | 117 +- sr_port/dpgbldir.h |14 +- sr_port/dse.h |11 +- sr_port/dse.hlp|44 +- sr_port/dse_adrec.c|23 +- sr_port/dse_adstar.c |13 +- sr_port/dse_all.c |51 +- sr_port/dse_chng_bhead.c | 7 +- sr_port/dse_chng_rhead.c |13 +- sr_port/dse_dmp.c | 4 +- sr_port/dse_f_blk.c|16 +- sr_port/dse_f_key.c| 108 +- sr_port/dse_f_reg.c|89 +- sr_port/dse_find_gvt.c |71 + sr_port/dse_getki.c|66 +- sr_port/dse_ksrch.c|16 +- sr_port/dse_over.c |16 +- sr_port/dse_rest.c |37 +- sr_port/dse_rmrec.c| 5 +
Re: [MoM] Packaging Camp for Debian
Hi Corentin, On Thu, Aug 28, 2014 at 11:50:08AM +0200, Corentin Desfarges wrote: > Hi Andreas > > >>- I've compressed the sources of Camp in camp-0.7.1.tar.gz, > >Question: How did you obtained these sources before compressing them. > > I downloaded these source here : https://github.com/greenjava/camp This answers the question "from where" but not "how". In "To create a new local git repository" in our policy[1] it is recommended to do svn export svn://anonscm.debian.org/svn/debian-med/trunk/package_template debian I always start with editing the debian/watch file from there and adapt it to the upstream location (here Github release). Once you adapted the debian/watch file to version=3 https://github.com/greenjava/camp/releases .*/archive/(\d[\d.-]+)\.(?:tar(?:\.gz|\.bz2)?|tgz) (untested, but should work) The "how to download" answer is simply: uscan --verbose --force-download This is beating two birds with one stone: You *test* the d/watch file and *do* the download. Easy, isn't it? > >>- Then on the wiki page of MoM, there is a link to a git repository > >>for my project, but I'm asking if I have a writing access on it ? > > >You need to create an account on alioth.debian.org first and ask for > becoming added to the Debian Med team. > > Done. Yup, I accepted your application some time ago. > >>And first, does this repository already exist ? Because I can't > >>clone it for now, and I don't see it anywhere... > >This repository does not yet exist ... I just "invented" this string for > >the moment. :-) > > Fine! Is it to me to create it ? (When I will be in the team) I could do it but I think it is better if you follow the steps described in the Debian Med policy (browse [1] a bit down for 'setup-repository'). Its easy, be bold, just do it. :-) > >>- About "debian/watch" : The problem is there are some forks from > >>it, and the more recent is one year old. Does one of forks could be > >>used ? (Knowing that they look like that : > >>https://github.com/tegesoft/camp). > > >We are packaging the source which is mentioned in d/watch (this is > >connected to my "get sources" question). If *you* (as an educated > >person about the code) decide to package a fork for whatever reason > >this for should be fetched with d/watch and you should document the > >reasons for this in the file debian/README.source. > > So do you think that I have to fork the repository ? Hmmm, I'm not sure what you really mean. Is there any problem with the code you can download from https://github.com/greenjava/camp/releases If no, just use it. If yes, what exactly is the problem and what do you mean be 'fork'? > >>The organization of the Git repository doesn't include the > >>different version, like it by example : > >>http://sourceforge.net/projects/vxl/files/vxl/ > >>What do you think about it ? > > >I'm afraid I do not understand this question. (BTW, I just uploaded vxl > to unstable.) > > By example, in the case of VXL, there are many directories on > http://sourceforge.net/projects/vxl/files/vxl/ for each version. Is d/watch > available to work with a repository containing only the source files (as > https://github.com/greenjava/camp) ? Look at the examples in the d/watch from package_template above. This works to 95% of the given repositories (at least). Kind regards Andreas. [1] http://debian-med.alioth.debian.org/docs/policy.html#git-tips -- 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/20140828113048.gf27...@an3as.eu
Re: [MoM] Packaging Camp for Debian
Hi Andreas - I've compressed the sources of Camp in camp-0.7.1.tar.gz, Question: How did you obtained these sources before compressing them. I downloaded these source here : https://github.com/greenjava/camp - Then on the wiki page of MoM, there is a link to a git repository for my project, but I'm asking if I have a writing access on it ? You need to create an account on alioth.debian.org first and ask for becoming added to the Debian Med team. Done. And first, does this repository already exist ? Because I can't clone it for now, and I don't see it anywhere... This repository does not yet exist ... I just "invented" this string for the moment. :-) Fine! Is it to me to create it ? (When I will be in the team) - About "debian/watch" : The problem is there are some forks from it, and the more recent is one year old. Does one of forks could be used ? (Knowing that they look like that : https://github.com/tegesoft/camp). We are packaging the source which is mentioned in d/watch (this is connected to my "get sources" question). If *you* (as an educated person about the code) decide to package a fork for whatever reason this for should be fetched with d/watch and you should document the reasons for this in the file debian/README.source. So do you think that I have to fork the repository ? The organization of the Git repository doesn't include the different version, like it by example : http://sourceforge.net/projects/vxl/files/vxl/ What do you think about it ? I'm afraid I do not understand this question. (BTW, I just uploaded vxl to unstable.) By example, in the case of VXL, there are many directories on http://sourceforge.net/projects/vxl/files/vxl/ for each version. Is d/watch available to work with a repository containing only the source files (as https://github.com/greenjava/camp) ? - I've opened a new thread on https://lists.debian.org/debian-devel/2014/08/msg00845.html . Does it seem all right for you ? Yes, it is. (Just for the wording: I would have said here in this mail s/I've opened a new thread on/I filed an ITP bug/ ... and I would not refer to the thread on debian-devel but rather to #759244) - In this thread, as Upstream Author, I put the name of the last person I know who worked on Camp. Is it ok ? The ITP bug is not really relevant for this since once the package the bug is closed and forgotten. Please make sure you document things properly inside the package (README.source). I did it after have read this part of the "Debian New Maintainers’ Guide" : "If no one else is working on it, file an ITP (Intent To Package) bug report to the wnpp pseudo-package using reportbug." Thank you for your answer, Best regards, Corentin -- 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/53fefb50.4040...@gmail.com
Re: Status bowtie + tophat (Was: [Help] Need help for architecture specific code)
Hi, I rephrase: Does anybody have a better idea to get tophat into testing than simply restrict it to amd64? Kind regards Andreas. On Sun, Aug 24, 2014 at 10:16:14PM +0200, Andreas Tille wrote: > Hi Charles, > > On Sun, Aug 24, 2014 at 04:14:09PM +0900, Charles Plessy wrote: > > Le Sat, Aug 23, 2014 at 07:30:21PM +0200, Andreas Tille a écrit : > > > > > > What can we do to get tophat and bowtie into testing? > > > > > > tophat: > > > 1. tophat only Recommends: bowtie2 | bowtie or > > > 2. tophat Architecture: amd64 kfreebsd-amd64 > > > I think 1. is the better option > > > > Hi Andreas, > > > > In my understanding, it is not possible to run TopHat without Bowtie > > (version 1 > > or 2). Therefore, the “Depends” relationship is the most appropriate. > > > > Regarding the migration to Testing, it looks like both bowtie2 and bowtie > > must > > be installable to satisfy “bowtie2 | bowtie”, so we need to adapt ourselves > > to > > this constraint. Here are two possible solutions to the problem : > > > > 1. bowtie2 and bowtie provide a virtual “bowtie-aligner”, and tophat > > depends on “bowtie2 | bowtie-aligner”. > > > > 2. tophat depends on bowtie2 only. > > I do not think that this is necessary. If tophat would be tophat > >Architecture: amd64 kfreebsd-amd64 > > it can migrate smoothly since the "Depends: bowtie2 | bowtie" is > perfectly fullfilled on these architectures. The only thing is that > this means we give up in trying to build bowtie (1) on other than amd64 > architectures. > > > Given that bowtie and bowtie2 can be co-installed, and given that most users > > will want to use Bowtie 2 with TopHat, how about solution 2 ? > > I'm fine with any solution which has tophat in Jessie on the practically > used architectures. A bonus would be if it would work on all > architectures and as far as I understand people on debian-mentors the > amd64 optimisation code is overestimated but I guess we will not make it > without upstream and I do not remember that upstream mindet about any > response in this thread. > > 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: https://lists.debian.org/20140824201614.gi31...@an3as.eu > > -- 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/20140828090410.gd27...@an3as.eu
