Hi Andreas,
Thank you very much for offering help. I think Tiziano would not mind,
so please feel very welcome to a) for the sake of b) or any other
goodness you would like to bring ;)
Note though that MDP is pretty much inactive project since a few years
back. It seems it is still used by
oh, sorry about that and thanks for the ping!
I fixed it upstream already (the bug is really in datalad), and will
look to release it asap (i.e. now) and then see if we can update package
(might need to also upload new version of dcmstack first)
On Thu, 29 Sep 2022, Nilesh Patra wrote:
> Hi
THANK YOU Adrian!
Apparently I have forgotten to upload updated debian package after all
those now automated bugfix releases in datalad-container... I will do
that now, and if I fail -- your NMU would proudly solve the issue -- no
need to cancel.
On Thu, 26 May 2022, Adrian Bunk wrote:
>
omplete (1.12.3-0.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules
+- provide workaround for tests to not fail (Closes: #1010941).
+ Upstream issue: https://github.com/kislyuk/argcomplete/issues/337
+
+ -- Yaroslav Halchenko Fri, 13 May 2022 13:07:30 -0400
+
Package: python3-argcomplete
Version: 1.12.3-0.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Wanted to build a backport but failed to have it built even in current sid.
A complete log is at
http://www.onerussian.com/tmp/python-argcomplete_1.12.3-0.1_amd64.build
and
> openopt seems dead upstream and has been dropped from testing for almost
> two years, let's remove it?
sounds good to me
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:
Control: tag -1 pending
Hello,
Bug #982503 in neurodebian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #982503 in neurodebian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #982503 in neurodebian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Mon, 15 Feb 2021, Paul Gevers wrote:
> Hi Yaroslav,
> On 15-02-2021 05:51, Debian Bug Tracking System wrote:
> > bats (1.2.1-2) unstable; urgency=medium
> > .
> >* debian/patches
> > - adopted patch from https://github.com/bats-core/bats-core/pull/387 to
> >resolve
failed to arrive with working minimal patch against that elderly 1.2.1
FWIW built current snapshot which seems to be ok. but I am reluctant to
upload that one since it has breaking (we have no rev-depends though in
debian ATM) changes.
On Sun, 14 Feb 2021, Andreas Tille wrote:
> Hi Yaroslav,
Thanks, on it. also needs a patch now for datalad 0.14 deprecation
On Sat, 06 Feb 2021, Adrian Bunk wrote:
> Package: heudiconv
> Version: 0.9.0-1
> Severity: serious
> This looks like a forgotten conversion:
> https://sources.debian.org/src/heudiconv/0.9.0-1/debian/control/#L28
--
Yaroslav
Thanks!
Test building and will upload if all good with
$> git show
commit e9f88704d2fd8bf5f0053904222e66dcc69db621 (HEAD -> debian, tag:
debian/0.8-2)
Author: Yaroslav Halchenko
Date: Sat Feb 6 12:29:39 2021 -0500
Replace nosetests-3 with python3 -m nose for autopkgtest invo
Great, thanks for the info and the buzz -- missed this, will try now and
upload if all good.
Cheers,
On Wed, 13 Jan 2021, s3v wrote:
> Dear Maintainer,
> I tried to build your package in a sid chroot environment
> and I confirm that patch fixes this issue.
> Kind Regards
--
Yaroslav O.
On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:
> > Thanks for the hint. While this could possibly speet up the upload of
> > nipype I for myself are fine with waiting for the new Build-Depends.
> > Anybody who wants to speed up things is kindly invited to add this patch
> > and upload.
>
FWIW those were reported "upstream"
https://github.com/nipy/nipy/issues/466
unfortunately I had no time to look at them (again :-/)
On Tue, 08 Dec 2020, Andreas Tille wrote:
> Control: tags -1 pending
> Control: tags -1 help
> Hi,
> I've updated nipy Git[1] to version 0.4.3~rc1 which solves
On Thu, 03 Dec 2020, Rafael Laboissière wrote:
> Dear Yaroslav and Michael,
> Are you aware of the problem related in Bug#976325, regarding the email
> address t...@neuro.debian.net?
thanks Rafael. I think that elderly mail server didn't re-emerge from
the dead upon recent power outage. I
Feel welcome to NMU without delay. Sorry for being slow etc.
Thank you!
On Sun, 25 Oct 2020, Lisandro Damián Nicanor Pérez Meyer wrote:
> severity 972163 serious
> severity 972166 serious
> block 972176 by 972163
> block 972176 by 972166
> thanks
> Hi! We are close to begin the Qt transition
On Fri, 17 Jul 2020, Andreas Tille wrote:
> Control: tags -1 help
> Hi,
> the new upstream version I've just pushed to git solves the issue
thanks!
> that is reported here, but I'm running into a different issue:
>TypeError: data type 'uint15' not understood
I do not understand it
Old python ones are listed only as alternative dependencies to easy backports
for ancient systems.
https://packages.debian.org/sid/svgtune
I don't think this package holds any python removal
On June 20, 2020 12:49:59 AM EDT, Sandro Tosi wrote:
>Control: reopen -1
>
>This bug was closed, but
As the upstream and Debian maintainer for it, I am ok with it. It could be
easily made to build for python 3 but tests would show that it is not entirely
kosher. I better reupload it when it i an sure it is functioning correctly again
On June 13, 2020 1:16:58 PM EDT, "Moritz Mühlenhoff" wrote:
all' instead of 'any'
* Boosted policy to 3.8.3:
- -dbg got correct "section: debug" and "priority: extra"
-- Yaroslav Halchenko Mon, 16 Nov 2009
08:55:44 -0500
so indeed it is time for it to RiP ;) please RM
On Wed, 13 May 2020, Sco
Package: python3-h5py
Version: 2.10.0-7
Followup-For: Bug #959940
Please see https://github.com/hdmf-dev/hdmf/issues/343#issuecomment-625972582
for possibly more info:
@tillea @yarikoptic the debian port contains this code in
h5py_2.10.0-7.debian/debian/wrapper_module/h5py/__init__.py
Control: tag -1 pending
Hello,
Bug #959575 in neurodebian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Sun, 03 May 2020, Lucas Nussbaum wrote:
> > [ ! -d build/icons ] && mkdir -p build/icons
> > inkscape artwork/icon.svg -w 32 -h 32 \
> > -e build/icons/neurodebian.png
> > ** (process:15028): WARNING **: 05:07:11.653: Unable to create profile
> > directory (Permission denied) (13)
> >
> > yes, AFAIK it is dead. Let's RM. you ? me ? ;)
> Please go ahead :-)
FTR #959213
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834
On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:
> On Wed, Feb 26, 2020 at 04:15:03PM +0100, Andreas Tille wrote:
> > On Wed, Feb 26, 2020 at 08:37:30AM -0500, Yaroslav Halchenko wrote:
> > > thank you Andreas!!!
> > > re etelemetry: I made it optional for previous v
On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:33:35AM +, Matthias Klose wrote:
> > Package: src:pyepl
> > Version: 1.1.0+git12-g365f8e3-3
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
> > Python2
Thanks for the alert, FWIW, done now:
(git)lena:~exppsy/libfreenect[debian]git
$> gbp push salsa
gbp:info: Pushing debian/1%0.5.3-1 to salsa
gbp:info: Pushing upstream/0.5.3 to salsa
gbp:info: Pushing refs/heads/debian to salsa:refs/heads/debian
gbp:info: Pushing refs/heads/dfsg to
On Thu, 09 Apr 2020, Sandro Tosi wrote:
> Control: tags 936857 + patch
> Dear maintainer,
> I've prepared an upload for libfreenect (versioned as 1:0.5.3-2). The diff
> is attached to this message.
Thank you Sandro!
--
Yaroslav O. Halchenko
Center for Open Neuroscience
On Sun, 22 Mar 2020, Lucas Nussbaum wrote:
> Source: datalad-container
> Version: 0.5.0-1
Thank you for the report. 1.0.0-1 was built but forgotten to be
uploaded at the end of Feb. Now it would need to wait until datalad
0.12.4 is uploaded first which would resolve incompatibilities with
On Fri, 06 Mar 2020, Paul Gevers wrote:
> Control: tags -1 pending
> Dear maintainer,
> I have uploaded a no-changes source only version to DELAYED/15. Please
> tell me if I should delay or cancel the upload.
oh, I have missed that
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942615
and
FWIW, this issue should be fully addressed in recent releases.
in Debian we have 4.30.0-1, upstream release is v4.43.0, and this issue
was fixed in
https://github.com/tqdm/tqdm/commit/0fcf9ed4c191fa224afd5581ac1a47b2cf80bc54#diff-79a0b30dff238cd3aa6b9f8e665a57a0
pandas: support v1.0.0 (so even
thank you Andreas!!!
re etelemetry: I made it optional for previous version of the
package:
$> quilt series
deb-no-demand-on-etelemetry
$> git describe
debian/0.6.0-1
On Tue, 25 Feb 2020, Andreas Tille wrote:
> Hi,
> here is some update I'm also forwarding
On Thu, 06 Feb 2020, Yaroslav Halchenko wrote:
> On Wed, 15 Jan 2020, Abhijith PA wrote:
> > Hi Adrian,
> > On 15/01/20 5:47 pm, Adrian Bunk wrote:
> > > On Tue, Dec 17, 2019 at 03:21:07PM +, Debian Bug Tracking System
> > > wrote:
> > >> ...
&
Control: tag -1 pending
Hello,
Bug #936305 in citeproc-py reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Wed, 15 Jan 2020, Abhijith PA wrote:
> Hi Adrian,
> On 15/01/20 5:47 pm, Adrian Bunk wrote:
> > On Tue, Dec 17, 2019 at 03:21:07PM +, Debian Bug Tracking System wrote:
> >> ...
> >> Architecture: source all
> >> Version: 1.12-4
> >> ...
> > Please make a source-only upload to allow
On Mon, 27 Jan 2020, Sandro Tosi wrote:
> in the archive we have 0.5.3, released in 2015; the latest upstream
> release is 0.5.7 which was released in 2017; the first release to
> support python3 is 0.5.4 of 2016.
> I see 2 paths forward:
> 1. (longer) the package gets upgraded to 0.5.7 (with
On Mon, 20 Jan 2020, Andreas Tille wrote:
> On Mon, Jan 20, 2020 at 01:01:00PM -0500, Yaroslav Halchenko wrote:
> > > I'm fine with re-doing what I changed if you consider it really of
> > > practical relevance. If you ask me we two would spent time we could
> &
On Mon, 20 Jan 2020, Andreas Tille wrote:
> > so I should be able to transfer over to debian-med. May be rename yours
> > into nibabel-med-initial so I could do it?
> I'm fine with re-doing what I changed if you consider it really of
> practical relevance. If you ask me we two would spent
On Mon, 20 Jan 2020, Andreas Tille wrote:
> Hi Yaroslav,
> On Mon, Jan 20, 2020 at 10:50:07AM -0500, Yaroslav Halchenko wrote:
> > > I think it would be helpful if you would remove the old repository
> > > in neurodebian-team.
> > shouldn't I (you) just "
On Mon, 20 Jan 2020, Andreas Tille wrote:
> Hi Yaroslav,
> On Sun, Jan 19, 2020 at 02:41:52PM -0500, Yaroslav Halchenko wrote:
> > actually as far as I see it Sando has pushed everything for
> > 2.5.1-2
> > https://salsa.debian.org/neurodebian-team/nibabel/blob/d
On Sun, 19 Jan 2020, Andreas Tille wrote:
> Hi Yaroslav,
> can you please push your latest changes to nibabel? I'd volunteer
> to fix #948372 and when doing so move the repository to Debian Med
> if you do not mind.
actually as far as I see it Sando has pushed everything for
2.5.1-2
On Fri, 09 Aug 2019, Elena ``of Valhalla'' wrote:
> Yaroslav Halchenko wrote:
> > If new version building is problematic, why not to upload just a patched
> > version?
> That would only delay the removal a bit: I'm sure that the current
> version doesn't work with p
thanks! fixing now
On Thu, 19 Dec 2019, Andreas Beckmann wrote:
> Followup-For: Bug #936450
> Control: found -1 0.7.0-2
> There are some references to python2 left, causing the package to FTBFS:
> https://buildd.debian.org/status/fetch.php?pkg=duecredit=all=0.7.0-2=1576039796=0
> fakeroot
On Tue, 17 Dec 2019, Sandro Tosi wrote:
> Control: tags 913015 + patch
> Control: tags 936372 + patch
> Control: tags 942992 + patch
> Dear maintainer,
> I've prepared an upload for dcmstack (versioned as 0.7-2). The diff
> is attached to this message.
> i dont have access to the GH repos,
On Sat, 23 Nov 2019, Andreas Tille wrote:
> Package: python3-joblib
> Version: 0.14.0-0.2
> Severity: critical
> Tags: patch
> Justification: breaks unrelated software
> Hi,
> as per latest debci log of spades[1] joblib needs python3--pkg-resources.
> I will add this to the dependencies but
On Thu, 17 Oct 2019, peter green wrote:
> severity 934868 serious
> thanks
> python-pynwb depends on python-h5py, which is no longer built by the h5py
> source package.
> unfortunately it seems hdmf is still stuck in new, can you go ahead with
> uploading the python2 removal with the
On Tue, 06 Aug 2019, Santiago Vila wrote:
> reopen 903213
> found 903213 0.4.1-1
> fixed 903213 0.10.2-1
> thanks
> Hi. Could we please fix this in stretch?
> (Packages in stretch must be buildable in stretch).
...
FAILED (SKIP=65, errors=63, failures=15)
I will unlikely embark on that
I guess it could indeed be removed, even if only to raise later from ashes as
pymc3
Cheers
On September 26, 2019 7:18:08 PM EDT, Sandro Tosi wrote:
>Source: pymc
>Severity: serious
>
>Hello,
>pymc is abandoned upstream and replaced by pymc3 (python3 only module),
On Mon, 02 Sep 2019, Debian FTP Masters wrote:
> Version: 0.5.3-1+rm
oh well -- I have missed all the reports (misconfigured debian.net
MX for a few months, heh). So only saw the effect of RM. Just want to
clarify
heudiconv is maintained
python3 support was added upstream as of 0.3 I
Dear Sandro, Steve, and Peter
Thank you for all the modernization of DataLad package. Feel welcome to
upload to shorter NMU if desired/needed. Some of those changes are now
addressed upstream and I will include/ack your NMUs with the next
release of datalad package.
Cheers,
--
Yaroslav O.
Package: rst2pdf
Version: 0.93-7
Followup-For: Bug #929954
If new version building is problematic, why not to upload just a patched
version? I have verified that adding import reportlab to
/usr/lib/python2.7/dist-packages/rst2pdf/flowables.py addresses the issue
I ran into this one while
TL;DR summary:
interesting... in my case reliably fails locally on python 3.6 and 3.7 but not
2.7 even with fresh release of 0.13.0
reported upstream https://github.com/joblib/joblib/issues/870
Thanks for the patch -- I will xfail it in 0.13.0-1 with this, upload to
unstable, and then upload
On Wed, 27 Feb 2019, Andreas Tille wrote:
> Dear Rebecca,
> On Wed, Feb 27, 2019 at 07:25:26AM +, Rebecca N. Palmer wrote:
> > On 27/02/2019 07:00, Andreas Tille wrote:
> > > Dear Rebecca,
> > > I do not think that there is any
> > > need for a separate branch. Just stick to the debian
upstream shortly - so we will see if reproduces then
On Sun, 03 Feb 2019, Yaroslav Halchenko wrote:
> CHANGES error is benign , will clarify upstream
> https://github.com/nipy/nipype/issues/2873
> the actual issue is
> > raise TypeError("expected str, bytes o
CHANGES error is benign , will clarify upstream
https://github.com/nipy/nipype/issues/2873
the actual issue is
> raise TypeError("expected str, bytes or os.PathLike object, "
> > "not " + path_type.__name__)
> E TypeError: expected
On Mon, 21 Jan 2019, Torsten Rohlfing wrote:
>Hi there -
>Upstream owner of CMTK here. It looks like DCMTK in release 3.6.4 changed
>their API for locking/unlocking the global data dictionary.
>I am going to look into fixing this, but it'll take a while since I'll
>have to
Dear Andreas
Thank you for taking a stab at this! I will try to not forget to look
at it tomorrow (need to meet some other deadlines today). If you had a
chance to try figuring out in what part segfault happens (I would just
strace -f -o /tmp/strace.log python -m pytest ...) it might give a
Dear Yangfl and other Debian-science folks
could you please have a look at the scikit-learn packaging, which was
heavily tuned up recently and I have little to no clue how to
augment it reliably back or to avoid parallel build and its gotchas.
See http://bugs.debian.org/911830 for more details
Great, thanks
For starters I would just disable parallel invocation of debian/rules since
indeed there is no guarantee of absent races. Will do and reupload when get
back from dentist ;-)
--
Yaroslav O. Halchenko (mobile version)
Center for Open Neuroscience
On Sun, 02 Dec 2018, Yaroslav Halchenko wrote:
> > There's no visible progress on this problem in git -- is there progress
> > elsewhere?
> you could find some traces of the progress which lead to i386 fixes on
> https://github.com/scikit-learn/scikit-learn/issues?utf8=%E
On Sun, 02 Dec 2018, Stuart Prescott wrote:
> Dear Yaroslav & Michael,
> scikit-learn currently FTBFS everywhere.
please define your version of "everywhere". From
https://buildd.debian.org/status/package.php?p=scikit-learn=unstable
I see that 0.20.1+dfsg-1 builds fine on all intel and mips
Control: tag -1 pending
Hello,
Bug #908555 in pydicom reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
thanks! upstream says the issue was fixed in
https://github.com/pydata/patsy/pull/131
so I will just build a fresh snapshot
Cheers!
On Sat, 27 Oct 2018, Julian Taylor wrote:
> this problem probably has the same python change as cause as this issue:
>
Thank you Andreas for looking into it
2.3.1 bugfix is around the corner
https://github.com/nipy/nibabel/pull/667
so I will aim to make sure the #909990 is fixed within it (for starters
- I do not think I observed this exception when building from current RC
branch)
On Mon, 08 Oct 2018,
update:
- uploaded sympy 1.3 which resolves sympy bug
- running by upstream the resolution for the other failed test:
https://github.com/nipy/nipy/pull/445
and will upload fixed up package tomorrow
On Tue, 02 Oct 2018, Yaroslav Halchenko wrote:
> FWIW, two of the errors are caused by a
FWIW, two of the errors are caused by a bug in sympy which was fixed in
1.3 . I am preparing sympy 1.3 although didn't check yet if it would
fix it in nipy tests (not clear why it wasn't triggered before)
On Fri, 17 Aug 2018, Santiago Vila wrote:
> Package: src:nipy
> Version: 0.4.2-1
>
On Mon, 01 Oct 2018, Andreas Tille wrote:
> Hi Yaroslav,
> was this helpful for you?
sorry -- didn't look into scikit-learn yet. BTW - 0.20 release was
posted, so we should update and try again. Will you have time or should
I ?
--
Yaroslav O. Halchenko
Center for Open Neuroscience
Control: tag -1 pending
Hello,
Bug #866455 in psychopy reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
On Mon, 24 Sep 2018, Andreas Tille wrote:
> Probably due to racing condition since I migrated the repository before
> your pushes.
> > > either needed to be imported as quilt patches or alternatively you can
> > > use git mode in d/watch which creates a new tarball for you
> > > incorporating
On Mon, 24 Sep 2018, Andreas Tille wrote:
> > > When you talked about new upstream version: Do you want to give 0.20rc1
> > I did give it a try...
> > From the now empty list of
> > https://github.com/scikit-learn/scikit-learn/issues/created_by/yarikoptic it
> > might be that all of the ones
On Sun, 23 Sep 2018, Mattia Rizzolo wrote:
> Control: tags 902817 + patch
> Control: tags 902817 + pending
> Dear maintainer,
> I've prepared an NMU for fail2ban (versioned as 0.10.2-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
I guess if
On Mon, 24 Sep 2018, Andreas Tille wrote:
> When you talked about new upstream version: Do you want to give 0.20rc1
I did give it a try...
From the now empty list of
https://github.com/scikit-learn/scikit-learn/issues/created_by/yarikoptic it
might be that all of the ones I've filed are
On Mon, 10 Sep 2018, Andreas Tille wrote:
> On Mon, Sep 10, 2018 at 10:54:02AM -0400, Yaroslav Halchenko wrote:
> > Outstanding few issues so far are reported/dealt with upstream:
> > https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+author%3Ayarikoptic+
On Mon, 10 Sep 2018, Andrey Rahmatullin wrote:
> On Mon, Sep 10, 2018 at 04:33:21PM +0200, Andreas Tille wrote:
> > Hi,
> > looking at the bug log of scikit-learn[1] it seems to be a simple means to
> > do
> > --- a/debian/control
> > +++ b/debian/control
> > @@ -20,6 +20,7 @@ Build-Depends:
FWIW - waiting on upstream to fixup issues I've reported leading to
FTBFS of 0.20rc:
https://github.com/scikit-learn/scikit-learn/issues?q=is%3Aopen+is%3Aissue+author%3Ayarikoptic+label%3ABlocker
when done, will upload the 0.20 to address this one
On Sun, 02 Sep 2018, Santiago Vila wrote:
>
Tags +pending
Sorry I caused us duplicate work. for a minor slip it wasn't uploaded
to debian proper, I will build (now) and upload tomorrow morning
cheers,
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman
Should be fixable, concerns only testing
On July 8, 2018 9:02:07 AM EDT, Sean Whitton wrote:
>Hello Santiago,
>
>On Sat, Jul 07 2018, Santiago Vila wrote:
>
>> This is just how the build ends in my autobuilder with
>dpkg-buildpackage -A,
>> but there are full build logs available here:
>>
>>
I bet it is the security fix which was recently introduced... Would need a
patch to datalad from https://github.com/datalad/datalad/pull/2670
Hopefully still easy to apply since datalad moved way far ahead since 0.4 .
For buster/sid we will just release fresh version soon which would be
FWIW -- about to upload, cosmetics now
On Mon, 25 Jun 2018, Graham Inggs wrote:
> On 25 June 2018 at 18:21, Yaroslav Halchenko wrote:
> > I am loosely involved and highly interested ;-) If someone could help
> > maintaining it, I would appreciate.
> > meanwhile sinc
On Mon, 25 Jun 2018, Graham Inggs wrote:
> On 25 June 2018 at 18:21, Yaroslav Halchenko wrote:
> > I am loosely involved and highly interested ;-) If someone could help
> > maintaining it, I would appreciate.
> > meanwhile since there were no other activity re
On Sat, 23 Jun 2018, Graham Inggs wrote:
> Hi Stefan, Yaroslav
> On 22 June 2018 at 21:15, Stefan van der Walt wrote:
> > That sounds like a good solution to me. That said, scikit-image in
> > Debian is now maintained by the science team, so it would be good to
> > hear from a member of that
Thank you Adrian
Yes, we will proceed the RM way, will deal with it tomorrow
Cheers
On June 24, 2018 2:30:35 PM EDT, Adrian Bunk wrote:
>Source: connectome-workbench
>Version: 1.3.1-1
>Severity: serious
>
>https://buildd.debian.org/status/package.php?p=connectome-workbench=sid
>
>...
>In file
Package: docker.io
Version: 18.03.1+dfsg1-3
Severity: grave
Filing an official report so it doesn't get forgotten (we had some private
correspondence about it). New behavior was detected while testing new version
in experimental (17.12.1+dfsg-2) and maintains with current one: running any
Package: python-cffi
Version: 1.11.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
testing/cffi0/test_verify.py ..s [ 35%]
[ 39%]
meanwhile may be let me just take care about this tiny issue myself
On Sun, 08 Apr 2018, Yaroslav Halchenko wrote:
> Ok. Go ahead. Thanks.
> But indeed please keep it in a shape so it could be easily backported.
> On April 8, 2018 1:59:53 AM EDT, Andreas Tille <andr...@fam-til
Ok. Go ahead. Thanks.
But indeed please keep it in a shape so it could be easily backported.
On April 8, 2018 1:59:53 AM EDT, Andreas Tille wrote:
>Hi Yaroslav and Michael,
>
>as I did in the past with other scientific packages I would like to
>take
>over scikit-learn into
Feel welcome to upload without delays
On February 3, 2018 7:47:15 AM EST, Adrian Bunk wrote:
>Control: tags 866433 + patch
>Control: tags 866433 + pending
>
>Dear maintainer,
>
>I've prepared an NMU for impressive (versioned as 0.11.2-1.1) and
>uploaded it to DELAYED/15. Please
On Tue, 30 Jan 2018, Yaroslav Halchenko wrote:
> On Tue, 30 Jan 2018, Adrian Bunk wrote:
> > Control: reopen -1
> > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
> > >...
> > > pymvpa2 (2.6.4-1) unstable; urgency=medium
On Tue, 30 Jan 2018, Yaroslav Halchenko wrote:
> On Tue, 30 Jan 2018, Adrian Bunk wrote:
> > Control: reopen -1
> > On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
> > >...
> > > pymvpa2 (2.6.4-1) unstable; urgency=medium
On Tue, 30 Jan 2018, Adrian Bunk wrote:
> Control: reopen -1
> On Tue, Jan 30, 2018 at 03:39:04AM +, Debian Bug Tracking System wrote:
> >...
> > pymvpa2 (2.6.4-1) unstable; urgency=medium
> >...
> >* debian/rules
> > - run tests under fixed MVPA_SEED=1 to avoid surprises, so
severity 867550 normal
thanks
On Fri, 07 Jul 2017, Manonam wrote:
> Package: libgiftiio-dev
> Version: 1.0.9-1+b2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
Sorry for a delayed reply. As far as I see
- it builds fine for me in a clean
On Sat, 20 Jan 2018, Andreas Tille wrote:
> Could you please bring the Git repository in sync to enable me to make
> a proper team upload instead of putting the work to inject a NMU into
> the repository for something that is so simple that if it would be less
> work if you do it yourself.
Regarding the original report:
$> grep python-pil debian/control
python-pytest, python-pil | python-imaging,
Recommends: python-pytest, python-pil, python-imaging
so the only "harm" here is a possible recommends of python-imaging.
IMHO severity is exaggerated.
Anyways, I will
Thanks!
On Mon, 18 Dec 2017, Juhani Numminen wrote:
> Control: tags -1 + patch
> This patch removes -Werror to resolve this FTBFS. Removing the deprecated
> exception specifications is another option but I didn't feel like editing
> the public headers of the library.
--
Yaroslav O. Halchenko
Thanks -- I have submitted them for upstream review/feedback
https://github.com/singularityware/singularity/pull/1195
On Mon, 04 Dec 2017, James Cowgill wrote:
> Source: singularity-container
> Version: 2.4-1
> Severity: serious
> Tags: sid buster patch
> Hi,
> singularity-container FTBFS on
On Mon, 04 Dec 2017, Alexandre Gramfort wrote:
>oh mayavi
>I would really be in favor of removing mayavi as a hard dependency.
>is it an option?
well, it is not a hard dependency already... I just hate when
users keep reporting all those and then I need to react. Prefer not to
On Mon, 04 Dec 2017, Alexandre Gramfort wrote:
>Hi Andreas,
>I don't have the bandwidth to address this sorry.
>Also mne 0.13 is now 2 versions behind where we are now.
>Nobody found the time to do the debian packaging for 0.14
>and 0.15 so far.
>Really sorry about this.
I will look into updating it in upcoming days
On December 4, 2017 8:54:28 AM EST, Alexandre Gramfort
wrote:
>Hi Andreas,
>
>I don't have the bandwidth to address this sorry.
>
>Also mne 0.13 is now 2 versions behind where we are now.
>Nobody found the time to do the
1 - 100 of 523 matches
Mail list logo