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
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko
* Package name: pynwb
Version : 0.4.1
Upstream Author : PyNWB Team
* URL : https://github.com/NeurodataWithoutBorders/pynwb
* License : BSD-3 with additional statement
Programming Lang: Python
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:
>
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko
* Package name: mrtrix3
Version : 3.0~rc3+git86-g4b523b413
Upstream Author : Mrtrix3 Team
* URL : http://www.mrtrix3.org
* License : GPL-3
Programming Lang: C++
Description : diffusion-weighted
Thanks for the report and sorry for the silent. I can only confirm ATM
that even the most recent in 0.2.x series 0.2.13 is exhibiting the same issue:
$> ./crash.sh
./crash.sh: line 22: 22040 Segmentation fault env -i MALLOC_CHECK_=0 $GDB
/usr/lib/mrtrix/bin/read_ximg "`cat
Fwiw I will look into updating soon unless someone beats me to it
On August 11, 2018 1:50:42 AM EDT, Andreas Tille wrote:
>Hi,
>
>it seems upstream dealt with issue #3892 in latest upstream version
>0.9.
>As far as I can see this will fix #880245.
>
>Any volunteer to upgrade the package?
>
>Kind
thank you in advance
--
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 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
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
Fwiw asciinema is quite handy! We use it for our demos (generate them
automatically from our *cast scripts, along with possible narrated videos,
actual scripts, or just interactive demonstrations where people get blown away
at "my" typing speed/stability), see eg those asciinemas at
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
Package: rclone
Version: 1.36-3
Severity: wishlist
One of our (datalad) users reported needing rclone 1.42... I'm yet to check if
1.41 which is in debian would suffice but thought that it might be nice to get
it updated anyways. Upstream had >100 commits between the two. Unfortunately
I did
Package: python-h5py
Version: 2.7.1-2
Severity: normal
one of the annoyances of h5py in Debian now is that a bare import leads to
$> python -c 'import h5py'
/usr/lib/python2.7/dist-packages/h5py/__init__.py:36: FutureWarning: Conversion
of the second argument of issubdtype from `float` to
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
Sorry for the late follow up -- would you happen to remember why pymvpa2
is listed as effected? AFAIK we do not use python-decorator, thus we do
not build- or run depend on it. So why are we affected?
On Wed, 14 Mar 2018, Helmut Grohne wrote:
> Source: python-decorator
> Version: 4.1.2-1
>
On Mon, 25 Jun 2018, Torquil Macdonald Sørensen wrote:
> Package: python3-dicom
> Version: 0.9.9-3
> Severity: wishlist
> Hi!
> Please upgrade to pydicom 1.1.0.
> The following might be automatically solved by upgrading:
it might ;-) upstream renamed dicom to pydicom module, so I guess we
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
Package: ftp.debian.org
Severity: normal
There is no easy way to provide support for those architectures ATM.
Should close #902302
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: wnpp
Severity: wishlist
* Package name: cloudflare-zlib
Version : v1.2.8-28-ge55212b
Upstream Author : zlib authors + 9 new contributors
* URL : http://github.com/cloudflare/zlib
* License : BSD-3
Programming Lang: C
Description : compression
Seemed to work like a charm, thank you Piotr! Feel free to close
if you think this should be done manually (and not by default)
On Thu, 31 May 2018, Piotr Ożarowski wrote:
> [Yaroslav Halchenko, 2018-05-31]
> > I will meanwhile provide a workaround one way (skipping tests) o
Package: dh-python
Version: 3.20180326
Severity: normal
My use case is datalad. In upcoming release we will rely on entry points more
and our tests verify that entry points could be correctly loaded etc.
For the "scripts" we just provided a custom workaround, but now we will use
severity 739300 normal
thanks
On Tue, 04 Mar 2014, Sebastian Ramacher wrote:
> - lintian emits a privacy-breach-generic because of this [1].
> ...
> [1] http://lintian.debian.org/tags/privacy-breach-generic.html lists
> some packages that emit the warning for multiple possible MathJax
> URLs. I
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
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko <deb...@onerussian.com>
* Package name: python-sounddevice
Version : 0.3.10
Upstream Author : Matthias Geier <matthias.ge...@gmail.com>
* URL : http://python-sounddevice.readthedocs.io/
* License
On Wed, 04 Apr 2018, Sunil Mohan Adapa wrote:
> Every system that is using firewalld and fail2ban fails upgrading from
> stable to testing (or next stable eventually) because this issue.
> Please consider releasing a fix with priority by taking Fedora's
> workaround in the posted patch.
thanks
Package: python3-pafy
Version: 0.5.2-2
Severity: normal
$> ytdl -i 'https://www.youtube.com/watch?v=Lm4T-ALEIUM'
Traceback (most recent call last):
File "/usr/bin/ytdl", line 194, in
main()
File "/usr/bin/ytdl", line 158, in main
xprint(vid)
File "/usr/bin/ytdl", line 68, in
On Tue, 20 Mar 2018, Yaroslav Halchenko wrote:
> > https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/4
> Unfortunately that patch isn't directly applicable any longer, so I am at your
> mercy to guide me through the darkness:
FWIW -- I went back to Xorg from wayland (jus
On Tue, 20 Mar 2018, Yaroslav Halchenko wrote:
> https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/4
Unfortunately that patch isn't directly applicable any longer, so I am at your
mercy to guide me through the darkness:
hopa:~/deb/debug/gnome-shell-3.28.0
$> wget
It might be a separate issue, but since this one was reopened and not
yet closed, I just decided to follow up. My laptop decided to reboot
this night and I booted into a barely usable desktop -- besides changed
behaviors I have massive slowdowns: since every glitch (2 second
switching between
On Fri, 16 Mar 2018, Afif Elghraoui wrote:
> >Thanks for maintaining and updating the package through the latest
> >releases.
> >But I wondered -- since you also had similar (minor but still) pains --
> >could
> >we retain/maintain compatibility with previous versions of debhelper,
> >e.g. 10
>
Package: singularity-container
Version: 2.4.2-4
Severity: wishlist
Dear Afif
Thanks for maintaining and updating the package through the latest releases.
But I wondered -- since you also had similar (minor but still) pains -- could
we retain/maintain compatibility with previous versions of
I guess I have missed up with inability to version recommended packages...
Yeah, then we should provide as an alternative. Will do
On March 10, 2018 8:10:07 AM EST, Arturo Borrero Gonzalez <art...@debian.org>
wrote:
>On 10 March 2018 at 14:04, Yaroslav Halchenko <y...@onerussian
There is no | for recommends afaik
On March 10, 2018 7:54:01 AM EST, Arturo Borrero Gonzalez <art...@debian.org>
wrote:
>On 9 March 2018 at 16:26, Yaroslav Halchenko <y...@debian.org> wrote:
>> THANKS! but...
>>
>> On Fri, 09 Mar 2018, Arturo Borrero Gon
THANKS! but...
On Fri, 09 Mar 2018, Arturo Borrero Gonzalez wrote:
> Also, no need to `Recommends: iptables`, since is installed by default in
> every
> Debian system.
indeed it is (triple checked with debootstrap) but it could also as
easily be uninstalled. And that is what I guess is
On Sat, 24 Feb 2018, Rock Storm wrote:
> What's the status of this issue?
it is stable. contributions would be welcome(d)
> Will it ever be a python3 binary package?
yes
> I fail to use the package 'python-pyglet' for a python3 application, I
> keep getting the following error even though
Package: python-sympy
Version: 1.1.1-3
Severity: important
Tags: upstream
I am trying to update python-nipy package and it FTBFS due to docs
failing to build, because sphinx parses imported interfaces as well and pukes
due to
https://github.com/numpy/numpydoc/issues/115
since there is two
Indeed, new releases are out and since 3.3.0 there is a new fixture
(caplog) which an increasing number of projects start to use, so
we would need an updated py.test to be able to package them (we run
tests at build time)
Cheers and thanks in advance
--
Yaroslav O. Halchenko
Center for Open
On Sun, 18 Feb 2018, Axel Burri wrote:
> > Hi Axel,
> > On a somewhat tangentially related topic, please address these two
> > lintian errors when you have a chance:
> > https://lintian.debian.org/maintainer/a...@tty0.ch.html#btrbk
> python-script-but-no-python-dep
> The issue here is that
On Wed, 07 Feb 2018, Nicholas D Steeves wrote:
> On Fri, Nov 17, 2017 at 09:50:41AM -0300, Leonhard Weber wrote:
> > Hi,
> > I'd like to second the request for a bpo release due to the exact same
> > rationale.
> > In the meantime deferring btrfs bpo upgrades because of btrbk.
> :-o
> Dear
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 Wed, 31 Jan 2018, Przemysław Pawełczyk wrote:
> ERROR Unable to read the filter
> ERROR Errors in jail 'ssh-ddos'. Skipping...
> It seems that ssh and ssh-ddos were renamed in jail.conf to sshd and
> sshd-ddos.
> So I had to edit /etc/fail2ban/jail.local to replace [ssh] with [sshd]
> and
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
Package: python-ptrace
Version: 0.7-1
Severity: normal
Project migrated to github https://github.com/vstinner/python-ptrace
and its docs to http://python-ptrace.readthedocs.io/en/latest/
so the homepage in the pkg pointing to
http://fusil.hachoir.org/trac/wiki/Ptrace is very outdated
Also
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
Package: rsh-client
Version: 0.17-15
Severity: important
I was truly amazed to find an 11 year old segfault-reporting #366535 but since
my traceback/use case is different, decided that it might be a different
issue.
We use rcp/rsh on our local cluster between nodes. rcp "doesn't work":
Package: numdiff
Version: 5.9.0-1
Severity: wishlist
Tags: upstream
While using numdiff for comparing across a bulk of results files I came
up with some wishes which I have shared with Paolo and we decided to cement
them in an official bug report.
I was whining about "clutter" in the output
Current docker version in Debian started to "break on me"...
Please let us know/guide us if you need help with the update.
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone:
Package: python-numpy
Version: 1:1.13.3-2
Severity: normal
I guess it is a rare usecase since I haven't spotted another bugreport, and we
have managed to miss it for a while I guess.
dh_python2 installs built .so extensions with a arch specific suffix, e.g.:
neurodebian@smaug
guration left from
the
previous version(s) would either not work or would not work as
intended.
You are advised to accept new configuration and adjust it for your
customizations (if any).
-- Yaroslav Halchenko <deb...@onerussian.com> Sun, 21 Jan 2018
22:25
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
tags 498164 + fixed-upstream
reopen 498164
thanks
oops, my bad . As Serge reminded, this will be provided in 0.11 release.
So the issue is pending and fixed upstream
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall,
On Tue, 23 Jan 2018, Vincent Lefevre wrote:
> Package: fail2ban
> Version: 0.10.2-1
that was quick
> Severity: minor
> /etc/fail2ban/action.d/helpers-common.conf has CRLF line terminators:
> $ file /etc/fail2ban/action.d/helpers-common.conf
> /etc/fail2ban/action.d/helpers-common.conf: ASCII
On Mon, 22 Jan 2018, Ben Coleman wrote:
> I ran into this on Ubuntu, and it seems the best way to handle this is
> via a systemd override. I created a file
> /etc/systemd/system/fail2ban.service.d/override.conf with contents:
> [Unit]
> Requires=shorewall.service
> After=shorewall.service
>
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.
I Will try to do that later this week
On January 14, 2018 9:02:03 PM EST, m...@linux.it wrote:
>On Nov 13, Christian Kohlstedde wrote:
>
>> IPv6 usage is growing day by day and so getting fail2ban 0.10 to the
>> official debian repositories gets more important, too. I'm
I don't mind helping to maintain it under any of those teams. Thank you Andreas
for taking care about this new dependency. I will look into updating pandas
package
On January 15, 2018 3:37:53 AM EST, Andreas Tille wrote:
>Hi again,
>
>is it correct to assume that Debian
On Fri, 12 Jan 2018, Andreas Tille wrote:
> On Thu, Jan 11, 2018 at 10:12:52AM -0500, Yaroslav Halchenko wrote:
> > BUT I would appreciate if you do ;)
> Done and fixed / closed all other bugs. I Upgraded to the latest stable
> version by leaving alone beta.
Thanks! I
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
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko <deb...@onerussian.com>
* Package name: json-tricks
Version : 3.11.0
Upstream Author : Mark V <markv.nl@gmail.com>
* URL : https://github.com/mverleg/pyjson_tricks
* License : Revised
Hi Paulo
Saw https://askubuntu.com/a/833995 so decided to check WNPP and found
this ITP. Any progress or should I consider peek'ing into that ppa?
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207,
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
if there was a new release packaged so we could test it well before the
next stable Debian release.
Thank you very much for packaging and maintaining backuppc
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall,
Thanks for checking it out! I will issue an updated package shortly
Cheers and thnks again
On Tue, 07 Nov 2017, Thiago Franco de Moraes wrote:
> Hi
> I cloned the git repo from nibabel and did some tests. I saw the HEAD of
> upstream doesn't have this problem. The difference from the HEAD to
On Tue, 17 Oct 2017, Jeremy Bicha wrote:
> Source: psychopy
> Version: 1.85.3.dfsg-1
> According to http://www.psychopy.org/changelog.html
> the 1.85.3 release was incorrectly generated. You likely want 1.85.4 instead.
oh... thanks Jeremy... I will try to fix it up soonish
for 1.85.4 I had to
On Sat, 14 Oct 2017, Ghislain Vaillant wrote:
> On 14/10/17 07:54, Andreas Tille wrote:
> > On Fri, Oct 13, 2017 at 08:00:36PM +0200, Andreas Tille wrote:
> > ...
> > pandas_datareader: None
> > usage: pytest.py [options] [file_or_dir] [file_or_dir] [...]
> > pytest.py: error: unrecognized
On Fri, 13 Oct 2017, Andreas Tille wrote:
>1. proceed as I suggested here:
> https://lists.debian.org/debian-science/2017/10/msg1.html
>...
> Is there anybody who is no happy about this?
sorry to be the pain, I am ... And first of all -- thanks for taking
care about pandas!
I
On Tue, 10 Oct 2017, Yuri D'Elia wrote:
> On Sat, Sep 16 2017, Yuri D'Elia wrote:
> > Looking at python3-skimage-lib (which also requires a rebuild), it seems
> > that the package failed to pass some tests.
> > Bug #868582 even includes a patch to update to 0.13 [and disables some
> > test
On Thu, 14 Sep 2017, Yaroslav Halchenko wrote:
> On Thu, 14 Sep 2017, Yaroslav Halchenko wrote:
> > I pushed branch debian/pike with all needed changes to my "fork" of
> > upstream (since you package on top of it) to
> > http://github.com/yarikoptic/wra
I pushed branch debian/pike with all needed changes to my "fork" of
upstream (since you package on top of it) to
http://github.com/yarikoptic/wrapt
Please consider adopting ;)
Trying to build now
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
On Thu, 14 Sep 2017, Yaroslav Halchenko wrote:
> I pushed branch debian/pike with all needed changes to my "fork" of
> upstream (since you package on top of it) to
> http://github.com/yarikoptic/wrapt
> Please consider adopting ;)
> Trying to build now
may be no
2.7.13-2
ii python-six 1.10.0-3
pn python:any
python-wrapt recommends no packages.
python-wrapt suggests no packages.
-- no debconf information
>From 571f5a2b7ba75291bc8d8268d96a7a7dc0d2eb04 Mon Sep 17 00:00:00 2001
From: Yaroslav Halchenko <deb...@onerussian.com>
Date: Thu, 14 Sep 2
Package: python-wrapt
Version: 1.9.0-2
Severity: normal
$> debcheckout python-wrapt
declared git repository at
https://anonscm.debian.org/git/openstack/python-wrapt.git
git clone https://anonscm.debian.org/git/openstack/python-wrapt.git
python-wrapt ...
Cloning into 'python-wrapt'...
fatal:
Package: python-wrapt
Version: 1.9.0-2
Severity: important
Tags: upstream
Dear wrapt maintainers,
In our datalad project we ran into a quite nasty issue causing segfaults:
https://github.com/GrahamDumpleton/wrapt/issues/98 which now prevents
tests to pass for the upcoming new release of
Hi Jonathan -- thank you very much for looking into it
> > Subject: patched version needed to avoid fatal: Out of memory, getdelim
> > failed crash
> You could say that about all bugs. A patched version is needed to fix
> the bug. :)
;) indeed... should have said "attached patch is needed to
On August 16, 2017 8:11:50 PM EDT, Andreas Tille wrote:
>Hi Yaroslav,
>
>> apparently it is a problem in recent pandas, which isn't yet resolved
>or
>> worked around in statsmodels
>>
>https://github.com/statsmodels/statsmodels/issues/3841#issuecomment-318630239
>> so we might
the file and if it encounters an
error, but sets errno only in the latter case. Set errno to zero before
calling it to avoid misdiagnosing an out-of-memory condition due to a
left-over value from some other function call.
Reported-by: Yaroslav Halchenko <y...@onerussian.com>
Suggested-by: Junio C Hamano <
On Tue, 08 Aug 2017, Graham Bosworth wrote:
>### Note that this is from Gentoo, rather than Debian
yeah
>On a Pentium at 200MHz,
wow!!! do you have a physical beast like that from 90s?
> it seems that it can indeed terminateprematurely.
any chance you could also try 0.9.7
On Mon, 07 Aug 2017, Lucas Nussbaum wrote:
> Hi,
> On 07/08/17 at 14:32 -0400, Yaroslav Halchenko wrote:
> > severity 871371 important
> > tags 871371 + unreproducible
> > thanks
> > Ran rebuild which succeeded just fine on up to date sid for both amd64
> &g
severity 871371 important
tags 871371 + unreproducible
thanks
Ran rebuild which succeeded just fine on up to date sid for both amd64
and i386 (binary only)
Would need to be able to reproduce to figure out WTF
On Mon, 07 Aug 2017, Lucas Nussbaum wrote:
> Source: singularity-container
> Version:
Oh, we definitely should update Sid version of fail2ban. Thanks for the buzz,
will do later today
Cheers
--
Sent from a phone which beats iPhone.
On Thu, 27 Jul 2017, Andreas Tille wrote:
> > would need to dig in, may be later, meanwhile pushed my slight tune ups,
> > feel
> > welcome to fix up. You do know where to get the .orig.tar.gz ;)
> Sure I know and I used it for building. What about simplifying things
> for your team mates
On Thu, 27 Jul 2017, Andreas Tille wrote:
> Hi,
> I was hoping that taking over the version from experimental to unstable
> might help to fix this bug but I can only confirm that I can reproduce
eh -- plain rebuild doesn't suffice -- tests still fail
and some new failures happen:
On Thu, 27 Jul 2017, Yaroslav Halchenko wrote:
> Is there any demand/requirement for debhelper 10 for this package?
> Could we settle on 9 (to ease backportability to old jessie and alike)?
I would guess that the answers are no and yes, fixed up, building
now, will upload whenever done
On July 27, 2017 9:23:16 AM EDT, Andreas Tille wrote:
>Hi,
>
>I was hoping that taking over the version from experimental to unstable
>might help to fix this bug but I can only confirm that I can reproduce
>the problem here. So it also happens for version 0.8.0. I've
On Thu, 27 Jul 2017, Andreas Tille wrote:
> Hi,
> I was hoping that taking over the version from experimental to unstable
> might help to fix this bug but I can only confirm that I can reproduce
> the problem here. So it also happens for version 0.8.0. I've commited
> my attempt to Git and
Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko <deb...@onerussian.com>
* Package name: git-annex-remote-rclone
Version : 0.5
Upstream Author : Daniel Dent <sourcec...@contactdaniel.net>
* URL : https://github.com/DanielDent/git-annex-remote-rclo
tried on local laptop -- FTBFS, and then in clean sid/testing
built fine on debian stable (stretch) and ubuntu 17.04
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1
201 - 300 of 2789 matches
Mail list logo