gmane.linux.debian.devel.medical archive
1145 archived articles, newest first (page 9 of 12). Latest articles →
irc #debian-med and #debian-med:matrix.org (was: Re: Debian-Med policy proposal: 64-bit & little-endian only* for new packages)
Fri, 29 Mar 2024 10:00:07 +0100Re: Debian-Med policy proposal: 64-bit & little-endian only* for new packages
Fri, 29 Mar 2024 15:48:07 +0900Re: Debian-Med policy proposal: 64-bit & little-endian only* for new packages
Fri, 29 Mar 2024 07:21:27 +0100Re: Debian-Med policy proposal: 64-bit & little-endian only* for new packages
Fri, 29 Mar 2024 10:13:40 +0530Debian-Med policy proposal: 64-bit & little-endian only* for new packages
Thu, 28 Mar 2024 14:51:01 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 15:48:39 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 12:16:16 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 10:40:38 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 10:34:13 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 10:31:31 +0100Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 09:52:49 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 09:44:04 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 08:51:18 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 08:49:04 +0100Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 06:24:59 +0000Re: Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)
Tue, 19 Mar 2024 07:22:57 +0100Re: Action needed for R-pkg Uploaders
Mon, 18 Mar 2024 10:10:41 +0100Re: Action needed for R-pkg Uploaders
Mon, 18 Mar 2024 08:51:27 +0100libbio-procedural-perl is marked for autoremoval from testing
Mon, 18 Mar 2024 04:39:23 +0000libbio-db-swissprot-perl is marked for autoremoval from testing
Mon, 18 Mar 2024 04:39:22 +0000libbio-db-refseq-perl is marked for autoremoval from testing
Mon, 18 Mar 2024 04:39:22 +0000Re: Fwd: heudiconv FTBFS on i386
Fri, 15 Mar 2024 11:23:58 -0400Fwd: heudiconv FTBFS on i386
Fri, 15 Mar 2024 14:52:55 +0100Re: How is autopkgtest working in Perl packages
Tue, 12 Mar 2024 23:11:55 +0100Re: Bug#1065841: Taking over datalad to either Debian Med or Debian Science team
Tue, 12 Mar 2024 22:03:08 +0100Bug#1065841: Taking over datalad to either Debian Med or Debian Science team
Tue, 12 Mar 2024 15:50:22 -0400Re: How is autopkgtest working in Perl packages
Tue, 12 Mar 2024 14:03:45 +0100Re: How is autopkgtest working in Perl packages
Mon, 11 Mar 2024 22:29:30 +0100Taking over datalad to either Debian Med or Debian Science team
Mon, 11 Mar 2024 21:38:11 +0100Re: How is autopkgtest working in Perl packages
Mon, 11 Mar 2024 20:51:36 +0100How is autopkgtest working in Perl packages
Mon, 11 Mar 2024 19:34:23 +0100Action needed for R-pkg Uploaders
Mon, 11 Mar 2024 15:47:42 +0100clustalw lost in debian/dists/sid/main/binary-i386/Packages.{gx}z ?
Mon, 11 Mar 2024 12:06:58 +0100Build-Dependencies from emboss-lib for bioperl-run and python-biopython (Was: reverse dependencie)
Sat, 9 Mar 2024 22:53:19 +0100Re: regarding filtering architectures
Thu, 7 Mar 2024 21:31:42 +0100Re: regarding filtering architectures
Thu, 7 Mar 2024 12:23:15 +0100Re: regarding filtering architectures
Sun, 3 Mar 2024 21:49:35 +0100Re: autopkgtest-pkg-pybuild
Wed, 28 Feb 2024 12:38:38 +0100Re: autopkgtest-pkg-pybuild (Was: [Git][med-team/python-bx][master] 2 commits: d/control: now run the autopkgtesting using pybuild-autopkgtest.)]
Tue, 27 Feb 2024 20:39:26 +0100Re: Bug#1064291: marked as done (ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms)
Mon, 26 Feb 2024 06:38:34 +0100Re: Bug#1064291: marked as done (ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms)
Mon, 26 Feb 2024 01:30:58 +0530Re: Bug#1064291: marked as done (ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms)
Sun, 25 Feb 2024 20:32:52 +0100Re: Bug#1064291: marked as done (ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms)
Sun, 25 Feb 2024 06:54:48 +0100Bug#1064291: marked as done (ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms)
Sat, 24 Feb 2024 13:09:05 +0000Re: New CamiTK 5.2.0 release
Fri, 23 Feb 2024 11:20:21 +0100Re: New CamiTK 5.2.0 release
Fri, 23 Feb 2024 07:06:44 +0100Re: New CamiTK 5.2.0 release
Thu, 22 Feb 2024 16:07:25 +0100Re: New CamiTK 5.2.0 release
Thu, 22 Feb 2024 11:14:51 +0100Re: New CamiTK 5.2.0 release
Thu, 22 Feb 2024 07:48:53 +0100Bug#1064291: ITP: python-awkward -- manipulate JSON-like data with NumPy-like idioms
Mon, 19 Feb 2024 20:16:36 +0100Help needed to port qiime to Python3.12
Sat, 17 Feb 2024 11:36:41 +0100New CamiTK 5.2.0 release
Fri, 16 Feb 2024 11:01:57 +0100For the sprint attendees: Dinner tomorrow evening
Thu, 15 Feb 2024 19:03:58 +0100Re: Should we restrict libtread-pool to 64bit only
Tue, 13 Feb 2024 08:25:50 +0100Bug#1063800: Should we restrict libtread-pool to 64bit only
Mon, 12 Feb 2024 22:09:43 -0500Should we restrict libtread-pool to 64bit only (Was: Bug#1063800: src:pinfish: fails to migrate to testing for too long: not installable on armel, armhf and i386)
Mon, 12 Feb 2024 22:06:14 +0100Re: gnumed-client is marked for autoremoval from testing
Sat, 10 Feb 2024 21:52:36 +0100Re: gnumed-client is marked for autoremoval from testing
Sat, 10 Feb 2024 21:39:26 +0100Re: gnumed-client is marked for autoremoval from testing
Sun, 11 Feb 2024 00:28:14 +0530Re: gnumed-client is marked for autoremoval from testing
Sat, 10 Feb 2024 18:48:03 +0100Lets do the video conference next week
Sat, 10 Feb 2024 14:18:42 +0100Re: Do we need the Python interface of ghmm
Wed, 7 Feb 2024 14:57:57 +0100Aw: Re: Do we need the Python interface of ghmm
Wed, 7 Feb 2024 14:23:22 +0100Re: Do we need the Python interface of ghmm
Wed, 7 Feb 2024 14:02:54 +0100Inquiry Regarding Product Availability and Delivery Schedule
Tue, 06 Feb 2024 15:08:31 +0000Products Enquiry
06 Feb 2024 07:46:11 +0000Re: [Debian-med-packaging] Bug#1062404: orthanc-python: flaky autopkgtest: Test failed with
Thu, 1 Feb 2024 22:06:20 +0530Bug#1062404: [Debian-med-packaging] Bug#1062404: orthanc-python: flaky autopkgtest: Test failed with
Thu, 1 Feb 2024 13:55:21 +0100Re: User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)
Thu, 1 Feb 2024 13:29:59 +0100Re: ClonalFrameML: Dataset with less computational resourses
Wed, 31 Jan 2024 14:19:56 +0100Re: ClonalFrameML: Dataset with less computational resourses
Wed, 31 Jan 2024 12:17:33 +0000Re: User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)
Wed, 31 Jan 2024 11:28:14 +0000Re: User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)
Wed, 31 Jan 2024 11:08:59 +0100Re: User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)
Wed, 31 Jan 2024 09:57:32 +0000Re: User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)
Wed, 31 Jan 2024 16:27:54 +0900User input needed: Stop supporting 32 bit architectures with emboss (Was: emboss-lib: identified for time_t transition but no ABI in shlibs)
Wed, 31 Jan 2024 07:53:26 +0100Do we need the Python interface of ghmm
Tue, 30 Jan 2024 07:58:34 +0100Re: ClonalFrameML: Dataset with less computational resourses
Mon, 29 Jan 2024 20:19:28 +0100Re: ClonalFrameML: Dataset with less computational resourses
Mon, 29 Jan 2024 18:34:54 +0100Re: ClonalFrameML: Dataset with less computational resourses
Mon, 29 Jan 2024 17:23:47 +0100Re: ClonalFrameML: Dataset with less computational resourses
Mon, 29 Jan 2024 11:59:04 +0000ClonalFrameML: Dataset with less computational resourses
Mon, 29 Jan 2024 11:20:44 +0100Moving neuron and nmodl to Debian Med?
Sun, 28 Jan 2024 04:20:56 +0530Re: Bug#1043240: transition: pandas 1.5 -> 2.1
Mon, 22 Jan 2024 11:51:59 +0000Re: Bug#1043240: transition: pandas 1.5 -> 2.1
Sun, 21 Jan 2024 19:38:30 +0000Re: Bug#1043240: transition: pandas 1.5 -> 2.1
Sun, 21 Jan 2024 19:31:58 +0000Re: Bug#1043240: transition: pandas 1.5 -> 2.1
Sun, 21 Jan 2024 19:29:36 +0100Bug#1043240: transition: pandas 1.5 -> 2.1
Sun, 21 Jan 2024 15:29:21 +0000Debian Med video meeting today Saturday 2024-01-13 19:00 UTC
Sat, 13 Jan 2024 07:02:54 +0100Debian Med sprint February 16.-18. 2024 in Berlin (in person meeting)
Wed, 10 Jan 2024 18:23:33 +0100libbio-db-swissprot-perl is marked for autoremoval from testing
Sat, 06 Jan 2024 04:39:12 +0000libbio-procedural-perl is marked for autoremoval from testing
Sat, 06 Jan 2024 04:39:12 +0000Re: Last call for any other location than Berlin (Was: Any suggestions for next Debian Med sprint (in person meeting)?)
Wed, 3 Jan 2024 19:23:05 +0100Re: Last call for any other location than Berlin (Was: Any suggestions for next Debian Med sprint (in person meeting)?)
Wed, 3 Jan 2024 12:41:23 +0100Re: Last call for any other location than Berlin (Was: Any suggestions for next Debian Med sprint (in person meeting)?)
Wed, 3 Jan 2024 12:11:18 +0100Re: Last call for any other location than Berlin (Was: Any suggestions for next Debian Med sprint (in person meeting)?)
Wed, 3 Jan 2024 10:44:03 +0100Re: Xpore Autopkgtest Review ( Bug #1035276 )
Mon, 1 Jan 2024 03:24:57 +0530 (IST)Bug#1059776: ITP: python-trx-python -- implementation of the trx file-format for tractography data
Sun, 31 Dec 2023 23:05:29 +0100Re: Outreachy Contribution
Mon, 1 Jan 2024 03:22:20 +0530 (IST)Outreachy Contribution
Sun, 31 Dec 2023 22:01:29 +0100
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.