Re: qiime2 status update

Hi Steffen, Steffen Möller, on 2020-12-01 19:42:23 +0100: > Does this mean that the many q2-xyz packages we can now also think about > updating? Sounds like it! :) Cheers, -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse

Re: qiime2 status update

Well done, Étienne! Does this mean that the many q2-xyz packages we can now also think about updating? Best, Steffen On 01.12.20 19:14, Étienne Mollier wrote: > Hi Andreas, > > Andreas Tille, on 2020-12-01 09:46:28 +0100: >> On Tue, Dec 01, 2020 at 12:06:45AM +0100, Étienne Mollier wrote: >>>

Re: qiime2 status update

Hi Andreas, Andreas Tille, on 2020-12-01 09:46:28 +0100: > On Tue, Dec 01, 2020 at 12:06:45AM +0100, Étienne Mollier wrote: > > Changes are not marked ready for > > upload yet, as there might still be some blocking points > > reported by the package tracker[1], notably 32-bits support. > > I'd

Re: qiime2 status update

Hi Étienne, On Tue, Dec 01, 2020 at 12:06:45AM +0100, Étienne Mollier wrote: > Hi there, > > Sorry it took quite a long time, I kind of struggled a bit with > the test suite of qiime. In the end I had to disable the build > time test, since apparently, pkg_resources is rather picky about > the

qiime2 status update

Hi there, Sorry it took quite a long time, I kind of struggled a bit with the test suite of qiime. In the end I had to disable the build time test, since apparently, pkg_resources is rather picky about the location of its modules, and the hack in place was not working with python 3.8 and 3.9.

Re: Status update

Hi Aaron, On Fri, Dec 02, 2016 at 09:48:44 -0500, Aaron M. Ucko wrote: > I have an upload mostly ready, but still have a few HTTPS-related fixes > to take care of. I just haven't pushed anything yet in case I need to > rework any changes first. I just noticed that the upload would also fix

Re: Status update

Andreas Tille writes: > Any help is really appreciated - even urgently appreciated since one of > our users intends to use prokka which just says: I have an upload mostly ready, but still have a few HTTPS-related fixes to take care of. I just haven't pushed anything yet in

Status update (Was: ncbi-tools6: How to write a watch file with version encoded in _ftp_ directory)

Hi Aaron, On Thu, Dec 01, 2016 at 03:54:12PM +0100, Andreas Tille wrote: > Yes - but at least we do now have a working watch file that enabled me > downloading the new upstream source. As I wrote in another mail[1] I > failed injecting it into the packaging Git. I was able to solve this - new

Re: [MoM] kmer-tools status update

Hi Afif, On Thu, May 28, 2015 at 02:58:58AM -0700, Afif Elghraoui wrote: so we do have counter examples to this (surely not build with d-shlibs) and so it might be possibly to forget d-shlibs and move around the files via usual dh_install but I think we should draw a cutting line here. I'd

Re: [MoM] kmer-tools status update

Hi Afif, On Tue, May 26, 2015 at 09:24:58PM -0700, Afif Elghraoui wrote: It might be helpful to add that command in the managing patches section on the Debian Med policy. I was always following the steps there when doing my patching. I know the New Maintainer's Guide has it, but it's not easy

Re: [MoM] kmer-tools status update

Hi, Andreas, On الثلاثاء 26 أيار 2015 04:27, Andreas Tille wrote: Hi Afif, No need to sorry about this. There are long standing developers who not provide DEP3 headers. :-) It might be helpful to add that command in the managing patches section on the Debian Med policy. I was always

Re: [MoM] kmer-tools status update

Hi, Andreas, On الإثنين 25 أيار 2015 00:13, Andreas Tille wrote: Hi Afif, On Sun, May 24, 2015 at 11:12:00PM -0700, Afif Elghraoui wrote: Hi, Andreas, I tried to go ahead with packaging shared libraries, but it looks like I have to read three to five more manuals before I can proceed and know

Re: [MoM] kmer-tools status update

Hi Afif, On Tue, May 26, 2015 at 01:20:19AM -0700, Afif Elghraoui wrote: Hmmm, I can not parse this as a specific question to me - just ask if I can help somehow. Regarding packaging shared libraries I personally recommend using d-shlibs. There are some examples in our repositories for

Re: [MoM] kmer-tools status update

Hi, Andreas, On الثلاثاء 26 أيار 2015 02:33, Andreas Tille wrote: Thanks. These are good enough pointers for me to start trying something. I was mostly confused by having to mind the symbols and sonames. It looks like I should just build the .so files and take care of their placement in

Re: [MoM] kmer-tools status update

Hi Afif, On Tue, May 26, 2015 at 03:06:01AM -0700, Afif Elghraoui wrote: Yes. I like the fact that d-shlibmove makes it easy by simply specifying --multiarch and that you do not neet to care whether sonames are correct or not since d-shlibmove checks it for you. Things basically turn out to

[MoM] kmer-tools status update

Hi, Andreas, I tried to go ahead with packaging shared libraries, but it looks like I have to read three to five more manuals before I can proceed and know what I'm doing. The package is otherwise ready to go. I have man pages for all the executables and I believe everything is in order. My

Re: [MoM] kmer-tools status update

Hi Afif, On Sun, May 24, 2015 at 11:12:00PM -0700, Afif Elghraoui wrote: Hi, Andreas, I tried to go ahead with packaging shared libraries, but it looks like I have to read three to five more manuals before I can proceed and know what I'm doing. Hmmm, I can not parse this as a specific

[FIS-GTM] Packing V6.0-001 - Status Update

I'm writing this mail so that interested parties know where this work stands. I had a call today (2013/01/25) with Luis Ibanez and Brad King from Kitware to get up to speed on the packaging for GT.M (thanks!). * I have an account and uploaded an SSH-key so that I can checkout and commit

Re: [FIS-GTM] Packing V6.0-001 - Status Update

Hi Amul, On Fri, Jan 25, 2013 at 02:45:11PM -0500, Amul Shah wrote: I'm writing this mail so that interested parties know where this work stands. I had a call today (2013/01/25) with Luis Ibanez and Brad King from Kitware to get up to speed on the packaging for GT.M (thanks!). * I have