On Wednesday, November 13, 2019 12:24:38 P.M. CST Gert Wollny wrote:
> Hello Steven,
>
> I've seen that you uploaded a new version of castxml (0.2.0-3) but it
> seems you forgot to push the changes to salsa. Could you do this?
Done. Sorry for neglecting.
-Steve
signature.asc
Description:
On Thursday, September 17, 2020 3:07:23 P.M. CDT Thomas Goirand wrote:
> On 9/16/20 2:55 PM, Steven Robbins wrote:
> > Since you're soliciting opinions, here's mine. In the absence of a
> > documented consensus, ftpmaster should respect the packager's judgement
> > rather tha
On Tuesday, September 15, 2020 11:18:28 P.M. CDT Andreas Tille wrote:
> Hi Paul,
>
> On Tue, Sep 15, 2020 at 10:00:45PM +0200, Paul Gevers wrote:
> > On 14-09-2020 21:04, Andreas Tille wrote:
> > > In the case of larger data sets it seems to be natural to provide the
> > > data in a separate
Hi Étienne,
On Thursday, August 6, 2020 2:09:46 P.M. CDT Étienne Mollier wrote:
> If someone else attempts a run with git buildpackage, note the
> external data fetched by debian/rules get-orig-source, which
> need to be put into an appropriate archive .orig-data.tar.gz;
> something specific to
On Saturday, August 8, 2020 4:34:39 P.M. CDT Étienne Mollier wrote:
> > 2. I wonder whether some of the older patches (dating from 2016) should be
> > dropped; in particular:
> >
> > atomic_load.patch
>
> I'm missing context, and the issue tracker pointed to by the URL
> in the header does not
On Friday, August 7, 2020 12:24:56 P.M. CDT Étienne Mollier wrote:
> Hi Gert, Hi Steve, Hi Andreas,
>
> Andreas Tille, on 2020-08-06 21:45:49 +0200:
> > thanks a lot for all your work. I'd love if the usual uploaders
> > Gert or Steve would take over the sponsoring since I never touched
> > that
Hi Étienne,
(& hopefully Gert will chime in!)
On Thursday, August 6, 2020 2:09:46 P.M. CDT Étienne Mollier wrote:
> Good day,
>
> This night's build of insighttoolkit 4.13.3 in the clean chroot
> went through, and test suite validated without particular
> issues. I pushed the part of my work
On Saturday, August 8, 2020 3:28:45 P.M. CDT Étienne Mollier wrote:
> Hi Steven, Hi Gert,
>
> Steven Robbins, on 2020-08-08 14:22:08 -0500:
> > I've looked through all the changes now. I have some questions.
> >
> > Inline ITK data v4.13.3
> > 7c3eb77
On Saturday, August 8, 2020 2:22:08 P.M. CDT Steven Robbins wrote:
> I've looked through all the changes now. I have some questions.
Two more issues:
1. My build failed Test #2625: PythonExtras
Traceback (most recent call last):
File "extras.py", line 163
Hello,
On Saturday, August 8, 2020 4:34:39 P.M. CDT Étienne Mollier wrote:
> Hi Steven, Hi Gert,
>
> Steven Robbins, on 2020-08-08 15:06:53 -0500:
> > Two more issues:
> >
> > 1. My build failed Test #2625: PythonExtras
> > [...]
> > This puzzles me.
On Tuesday, August 11, 2020 2:43:09 A.M. CDT Gert Wollny wrote:
> > No, I think you did the right thing. I actually like the tag
> > "upstream/ 4.13.3-dfsg1+data" that you used. It provides a hint
> > that it is not the bare upstream tarball.
> >
> > All we need to do is call the source
On Monday, November 16, 2020 5:49:09 A.M. CST Gert Wollny wrote:
> > My thought is to upload to experimental first. I don't see any
> > "experimental" branch in salsa, but maybe I can just create one? Or
> > would it be better to make an itk5 branch?
>
> I'd suggest to use a new project
Hi,
I have a bit of time today and thought I'd look into packaging ITK 5.1.1.
My thought is to upload to experimental first. I don't see any "experimental"
branch in salsa, but maybe I can just create one? Or would it be better to
make an itk5 branch?
Also, I recall that someone (Gert, I
On Tuesday, December 21, 2021 10:22:49 A.M. CST Nilesh Patra wrote:
> On 12/21/21 9:00 PM, Pierre Gruet wrote:
> > On 21/12/2021 14:33, Lance Lin wrote:
> >> Debian Medical Team,
> >>
> >> I have started looking at adding autopkgtest suites for a variety of
> >> packages. Two of the packages
Hi,
As far as I can discern, the build job for Elastix successfully builds the
package, but then fails trying to upload artifacts. Can anyone shed light on
what's going on or how to fix it?
Uploading artifacts for successful job
01:11
Uploading artifacts...
On Wednesday, November 17, 2021 4:00:30 A.M. CST Tony Travis wrote:
> I use the "zim" personal Wiki for this purpose which, although it is not
> ideal, is very simple to install from the Debian/Ubuntu repo's and easy
> to use. I have been looking for a better alternative and was keen to try
> out
Hi,
I finally spent a few hours last night to get ITK v5 sources building. There's
still packaging work to do but I've pushed the interim results into salsa.
Note: as previously discussed, python bindings are removed.
On Tuesday, October 12, 2021 1:34:22 A.M. CDT ghisv...@gmail.com wrote:
>
On Monday, November 8, 2021 1:09:43 A.M. CST Andreas Tille wrote:
> Hi,
>
> this mail from Jose
>
> Am Sat, Nov 06, 2021 at 01:33:29AM +0100 schrieb Jose Luis Rivero:
> > Hello! Gazebo maintainer here, affected by this RC bug. Looking into
> > upstream repository there is a potential commit that
On Saturday, December 11, 2021 3:02:02 A.M. CST Étienne Mollier wrote:
> I considered pushing a change yesterday to disable those tests
> on insighttoolkit4,
Let's please agree to NEVER do that.
> not to hide dust under the carpet, but to
> give a chance to reverse dependencies to make it to
Hi,
I've built the ITK package on my AMD64 machine without trouble, but the 32-bit
build is failing with the error below.
The errors seem to point to using SSE instructions. Is there a recommended
set of flags to use when building for x86? I tried "-march=i686" but it gives
the same error.
Hi Nilesh,
On Tuesday, January 4, 2022 1:32:37 A.M. CST Nilesh Patra wrote:
> On 1/4/22 5:40 AM, Steven Robbins wrote:
> > Hi,
> >
> > As far as I can discern, the build job for Elastix successfully builds the
> > package, but then fails trying to upload artifa
Package: wnpp
Severity: wishlist
Owner: "Steve M. Robbins"
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-med@lists.debian.org
* Package name: ubpm
Version : 1.9.0
Upstream Contact: Thomas Löwe
* URL : https://codeberg.org/LazyT/ubpm
* License : GPL v3
On Wednesday, September 14, 2022 3:21:57 P.M. CDT Nilesh Patra wrote:
> Hi,
>
> There are some packages listed under our team and science team namespace
> as listed below (I snipped the rest of the dd_list)
> Please consider to port them to new wxwidgets if you happen to
> work on these packages
On Tuesday, July 4, 2023 5:25:34 A.M. CDT Andreas Tille wrote:
> The thread[2] actually was about the cnvkit example and IMHO we should
> decide now what to do here. I'm persinally in favour of shipping
> upstream names. They moved from setup.py to pyproject.toml so our patch
> does not work
On Wednesday, June 28, 2023 2:06:04 P.M. CDT Étienne Mollier wrote:
> Hi Steve,
>
> [I'm doing a group reply and send from debian.org smtp to check
> whether this is domain specific or something else and increase
> probability you receive at least one copy.]
Well ... today I got two copies --
On Wednesday, June 28, 2023 4:33:22 A.M. CDT olivier sallou wrote:
> I think I fixed the issue.
>
> I deleted upstream/5.3.0 tag on remote , went to upstream branch, and
> put tag again:
Awesome, thanks so much!!
I found that "gbp pull" initially failed on me. I had to delete my local tag
Hello,
I have a strange problem with Salsa's git repo for ITK. Today I did a fresh
clone and confirmed that it's not something I did locally. I don't understand
what the issue is and hoping someone here can help.
After the clone, I did a simple change to the control file, built the source
( https://salsa.debian.org/med-team/insighttoolkit/-/
pipelines/545076 ) triggered by Steven Robbins ( https://salsa.debian.org/smr
)
had 1 failed job.
Job #4370340 ( https://salsa.debian.org/med-team/insighttoolkit/-/jobs/
4370340/raw )
Stage: provisioning
Name: extract-source
--
You're receiving this
Hello Étienne!
First of all: many thanks for helpful suggestions on both my recent problems.
One odd thing, though: I have received all the mail in the two threads EXCEPT
those from you. I can see emails in the threads from others that are only to
the list (as yours are) and some that also CC
On Monday, April 15, 2024 2:06:00 A.M. CDT Andrius Merkys wrote:
> GDB localises the issue in a string formatting function. I have a hunch
> this might be related to time_64 transition, but cannot say more, alas.
Perhaps that is something worth transmitting to the s390 porters list?
If true, it
On Thursday, March 28, 2024 8:51:01 A.M. CDT Michael R. Crusoe wrote:
> Therefore I personally conclude that:
> Support Debian-Med packages for 32-bit and/or big-endian architectures is
> not a good use of our limited resources.
I've used that as a personal policy for years.
In my case, I
Hello,
On Sunday, May 19, 2024 9:31:02 A.M. CDT Tony Travis wrote:
> You can't ignore the host OS when you talk about HPC applications and
> the HEP (High Energy Physics) community put a lot of effort into
> developing good node provisioning systems and job-scheduling for HPC.
> Consequently,
On Saturday, April 6, 2024 7:39:10 A.M. CDT Michael R. Crusoe wrote:
> On 29/03/2024 19.44, Steven Robbins wrote:
> > I am left with a question whether [reactively dropping troublesome
> > architectures] is what you are proposing, or
> > whether you mean to preemptively restr
33 matches
Mail list logo
