Le mer. 24 avr. 2019 à 17:02, Santiago Vila a écrit :
> On Wed, Apr 24, 2019 at 04:47:16PM +0200, Sylvestre Ledru wrote:
> > Le 24/04/2019 à 16:45, Santiago Vila a écrit :
> > > On Wed, Apr 24, 2019 at 04:24:59PM +0200, ghisv...@gmail.com wrote:
> > > > Anyone objecting on applying Santiago's pat
Le mar. 5 févr. 2019 à 20:21, Rebecca N. Palmer a
écrit :
> Package: clsparse
> Severity: serious
> X-Debbugs-Cc: debian-scie...@lists.debian.org, ghisv...@gmail.com
> (plus an identical one for freefem3d)
>
> This package is dead upstream, and it has been suggested [0] that
> because of this, it
I am away right now and can't investigate before two weeks.
Looks Cython related from a first look.
Ghis
Le ven. 29 juin 2018 à 11:17, Andreas Tille a écrit :
> Hi Ghislain,
>
> since one of the Debian Med packages seems to be affected I tried to
> upgrade h5py (see Git repository). Unfortuna
Another option could be to patch the build system to use setuptools instead
of distutils as recommended by the PyPA?
Le mer. 21 mars 2018 à 20:45, Rebecca N. Palmer a
écrit :
> Source: sympy
> Severity: serious
> Control: tags -1 patch
> X-Debbugs-Cc: debian-pyt...@lists.debian.org
>
> python3-d
> Source: node-xterm
> Version: 2.7.0+ds1-1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/no
> de-xterm.html
>
> ...
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/build/1st/node-xterm-2.7.0+ds1'
> tsc --project .
> src/utils/
cc'd to Pirate Praveen who reported a similar issue for a version on
experimental?
Do you have an idea what's going on? Why is Adrian's log different to
yours?
On Thu, 18 Jan 2018 09:23:11 +0200 Adrian Bunk wrote:
> Source: libjs-fetch
> Version: 2.0.3-1
> Severity: serious
>
> https://tests.re
Dear Jonathan,
I was suprised to discover that backintime had been removed from
testing despite RC bug #881205 being fixed upstream [1].
For testing/unstable an update of the package to version 1.1.24 should
do the trick, whilst stretch/wheezy will require a backport of this
particular commit.
I
you raised. I am
waiting for my mentor to review it before uploading.
Ana
On Tue, Nov 14, 2017, at 08:59 AM, Ghislain Vaillant wrote:
> Thank you Matthias for raising this issue. CC'ing the maintainer in case
> she's not subscribed.
>
> On Mon, 6 Nov 2017 11:52:00 +0100 Ma
Thank you Matthias for raising this issue. CC'ing the maintainer in case
she's not subscribed.
On Mon, 6 Nov 2017 11:52:00 +0100 Matthias Klose wrote:
Package: yapf3
Version: 0.17.0-1
Severity: serious
Tags: sid buster
yapf3 explicitly depends on python3.5. One mistake certainly is the b-d on
On 10/10/17 11:58, Adrian Bunk wrote:
On Tue, Oct 10, 2017 at 12:08:29AM +0100, Ghislain Vaillant wrote:
On 09/10/17 23:06, Adrian Bunk wrote:
On Mon, Oct 09, 2017 at 12:28:22PM +0100, Ghislain Vaillant wrote:
...
I was complaining about the insufficiencies behind this RC, more than the
On 09/10/17 23:06, Adrian Bunk wrote:
On Mon, Oct 09, 2017 at 12:28:22PM +0100, Ghislain Vaillant wrote:
...
I was complaining about the insufficiencies behind this RC, more than the
situation with Sphinx. No offense to Adrian, but getting an RC bug reported
without much context to work with is
On 03/10/17 12:28, Dmitry Shachnev wrote:
Control: forwarded -1 https://bitbucket.org/pybtex-devs/pybtex/pull-requests/9/
Hi Ghislain,
On Sat, Sep 30, 2017 at 10:40:52AM +0100, Ghislain Vaillant wrote:
And what the hell am I supposed to do with this?!
Nice of you to report the issue but
Control: forwarded -1 https://github.com/shoyer/h5netcdf/issues/32
sphinx (1.6.4-1) unstable; urgency=medium
...
* dh_sphinxdoc: Turn warning about missing SOURCELINK_SUFFIX to an error.
...
-- Dmitry Shachnev Tue, 26 Sep 2017 17:47:54 +0300
And what the hell am I supposed to do with this?!
Nice of you to report the issue but, without further context, I c
On 18/08/17 17:26, Sebastiaan Couwenberg wrote:
On Mon, 7 Aug 2017 08:49:19 +0100 Ghislain Vaillant wrote:
control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194
Instead of packaging a snapshot as suggested by upstream, I suggest to
explicitly build the package with GCC 6 (as per
control: forwarded -1
https://github.com/QuantStack/xtensor-python/issues/102
control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194
control: forwarded -1 https://github.com/spyder-ide/spyder/pull/4311
control: reassign -1 spyder
control: affects -1 spyder-memory-profiler
On Fri, 2017-03-31 at 10:33 +0100, Chris Lamb wrote:
> Ghislain Vaillant wrote:
>
> > I am going to need some more context here. The build ran fine on the
> > builders when the package was initially upload
Hi Chris,
On Thu, 30 Mar 2017 08:26:36 +0100 Chris Lamb wrote:
Source: spyder-memory-profiler
Version: 0.1.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
D
On Sun, 19 Feb 2017 09:00:07 +0100 Andreas Tille wrote:
Package: mgltools-pmv
Version: 1.5.7-1
Severity: grave
Justification: renders package unusable
Hi,
I intended to reproduce #855485 but I was running into a different
problem:
$ runPmv
Run PMV from /usr/lib/python2.7/dist-packages/Pmv
Tr
On Fri, 17 Feb 2017 13:20:28 +1300 Chris Lamb wrote:
> I just ACCEPTed libopenshot from NEW but noticed it was missing
> attribution in debian/copyright for at least:
>
> include/DecklinkInput.h:8: * Copyright (c) 2009 Blackmagic Design
> include/DecklinkOutput.h:8: * Copyright (c) 2009 Blackmag
On Sat, 17 Dec 2016 11:24:17 +0100 Hugo Lefeuvre wrote:
> Hi Afif,
>
> Thanks for reporting bugs.
>
> The problem comes from the fact that pytest-benchmark needs the
> statistics module, which I haven't declared in the dependencies as
> it is not packaged yet and is in the extra section of the s
Cc'd to debian-powerpc
On Fri, 13 Jan 2017 10:17:18 + Ghislain Vaillant
wrote:
control: forwarded -1 https://github.com/h5py/h5py/issues/817
Upstream is running out of ideas, so any help from the team would be
warmly welcome.
Cheers,
Ghis
control: forwarded -1 https://github.com/h5py/h5py/issues/817
control: retitle -1 h5py: FTBFS [mips, s390x]: test failures
control: usertag -1 - ppc64el
Splitting this FTBFS into 2 different issues. This one for mips / s390x
and one for ppc* architectures.
There is a fix pending upstream for the mips / s390x issue.
Ghis
control: block -1 by 850277
Now CC'd to the Debian CMake Team
On 05/01/17 12:26, Ghislain Vaillant wrote:
CC'd the Debian CMake Team, who might be able to help.
On 05/01/17 10:48, Ghislain Vaillant wrote:
CC'd to the src:glm maintainer,
On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant
wrote:
CC'd the Debian CMake Team, who might be able to help.
On 05/01/17 10:48, Ghislain Vaillant wrote:
CC'd to the src:glm maintainer,
On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant
wrote:
Source: forge
Version: 0.9.2-2
Severity: serious
Justification: fails to build f
CC'd to the src:glm maintainer,
On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant
wrote:
Source: forge
Version: 0.9.2-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
Since the latest update of the packaging, src:fo
CC'd to d-science,
On Fri, 30 Dec 2016 01:24:07 + James Cowgill
wrote:
Hi,
On 30/12/16 00:50, Ghislain Vaillant wrote:
> On Thu, 29 Dec 2016 00:30:58 + James Cowgill wrote:
>> Control: severity -1 serious
>> Control: clone -1 -2
>> Control: reassign -
On Thu, 29 Dec 2016 00:30:58 + James Cowgill wrote:
> Control: severity -1 serious
> Control: clone -1 -2
> Control: reassign -2 libfftw3-single3 3.3.5-1
> Control: block -1 by -2
> Control: retitle -2 libfftw3-single3: dependencies in shlibs file not tight
> enough
>
> Hi,
>
> On 29/12/16
On Fri, 23 Dec 2016 19:28:09 + Ghislain Vaillant wrote:
> I have forwarded the issue upstream with a build log on the latest
> upstream version done on debomatic.
Alright, upstream claims the issue is fixed on `master`. I intend to
cherry-pick the fix onto 2.8.1, unless upstream deci
Hopefully, updating the package to the latest upstream (2.8.1) may fix
these test problems. That's what I am trying now.
Ghis
control: forwarded -1 https://github.com/pydata/numexpr/issues/239
On Fri, 2016-12-23 at 10:43 +0100, Andreas Tille wrote:
> Hi,
>
> I have cloned bug #848758 where I suggested to revert the python-numpy
> transition which other posters agreed upon. Besides breaking
> python-skbio I spotted another package python-skimage which fails with:
>
>
> ===
On 14/12/16 19:58, Stefan van der Walt wrote:
I would have absolutely no problem moving skimage to team maintenance.
If Yarik agrees, I'd appreciate some pointers on how to move forward
with that. What I would like is to remain in the loop w.r.t. packaging
changes. python-dask should be package
On 14/12/16 09:59, Ole Streicher wrote:
Since skimage is one of the central packages, I would again ask to put
it under science|python team maintenance. Especially when under some
time pressure (upcoming freeze, combined with autoremovals of packages)
it would help a lot if the problems could be
I would just drop the `test_symlink_time_handling` testcase and check
with upstream what might be going on here.
Apart from that, it looks like the internet access errors are fixed.
Ghis
On Tue, 13 Dec 2016 09:27:17 +0100 Andreas Tille wrote:
> Hi Kevin,
>
> you injected a "Closes: #845737" in the latest changelog but I get:
>
>
> ==
> FAIL: tests.tests.test_symlink_time_handling
> -
I could not repeat the exact output Chris got.
Still FTBFS on my end in a clean chroot, with the following output:
standardPregraph/contig.o: In function `call_heavygraph':
contig.c:(.text+0x8a6): undefined reference to `I'
contig.c:(.text+0x91f): undefined reference to `no symbol'
contig.c:(.tex
On Fri, 11 Nov 2016 14:17:13 -0800 Afif Elghraoui wrote:
> Hi, Andreas,
>
> على الأربعاء 9 تشرين الثاني 2016 ‫03:11، كتب
> Andreas Tille:
> >
> > do you have any news with this issue?
> >
>
> I should have posted an update. Upstream has moved consensuscore2 into a
On Mon, 05 Dec 2016 11:53:59 +0100 Hilko Bengen wrote:
> control: tag -1 patch
>
> Hi,
>
> I have verified that aff4 builds just fine if the "keepalive=0.5" line
> is removed from the requires.txt, so the extra python-keepalive package
> is not actually needed.
>
> Please consider adding the pa
control: tags -1 pending
It is fixed on my end. Will push soon after testing.
Ghis
control: forwarded -1 https://bitbucket.org/snakemake/snakemake/issues/
426/random-test-hangs-during-debian-package
On 01/12/16 10:01, Iain Lane wrote:
On Thu, Dec 01, 2016 at 08:27:16AM +, Ghislain Vaillant wrote:
Hi Ian,
Thanks for looking into this issue. Indeed the HDF5 transition has made
quite a few RCs pop the last few days.
Please drop the deferred and let me prepare a conventional update with
On 01/12/16 08:27, Ghislain Vaillant wrote:
Hi Ian,
Thanks for looking into this issue. Indeed the HDF5 transition has made
quite a few RCs pop the last few days.
Please drop the deferred and let me prepare a conventional update with
your changes in, plus some cleaning of the packaging. Can I
Hi Ian,
Thanks for looking into this issue. Indeed the HDF5 transition has made
quite a few RCs pop the last few days.
Please drop the deferred and let me prepare a conventional update with
your changes in, plus some cleaning of the packaging. Can I ping you
back for sponsorship when I am do
control: tags -1 pending
I have pushed a tentative fix on a staging branch. I have yet to
validate it on debomatic.
Ghis
control: tags -1 pending
On Sat, 19 Nov 2016 08:03:46 +0100 Lucas Nussbaum wrote:
> The following tests FAILED:
>421 - vf-invert-trans-1 (Failed)
>422 - vf-invert-trans-1-stats (Failed)
>423 - vf-invert-trans-1-check (Failed)
>426 - wed-c (Failed)
> Errors while running CTest
>
CC-ing this reply to the Debian bug report.
Thanks Paul for the patch. I applied it (fixed a missing import for
ungroup), used your name for the commit authorship and acknowledged
your contribution to the packaging changelog.
I will also forward the patch upstream.
Many thanks for your contri
Dear Salvatore, Balint,
Thanks for forwarding the CVE to us and verifying which versions of the
package were affected.
I'll monitor the progress of this CVE. The CVE reporter offered some
clues as to how to mitigate the problem, but I wonder how appropriate
closure of this vulnerability can be v
Hi Jorg,
I could not reproduce the problem you are having. Both my laptops
successfully upgraded to the latest version of network-manager.
Regards,
Ghis
2016-09-22 9:33 GMT+02:00 Ghislain Vaillant :
I have had a look at updating the package to the newest upstream
release and fixing this FTBFS. However, I have got strong concerns as
to whether it is worth keeping this package maintained in the archive:
- The latest release on PyPI [1] is busted
I have had a look at updating the package to the newest upstream
release and fixing this FTBFS. However, I have got strong concerns as
to whether it is worth keeping this package maintained in the archive:
- The latest release on PyPI [1] is busted (missing files). The issue
was reported [2] but
control: tags -1 + fixed pending
I am working on it. The issue is fixed in my fork, and the fix should be
rolled with the next update which will include a new upstream release.
Thanks,
Ghis
control: severity -1 normal
Previous builds on mips and mipsel have been removed [1]. Downgrading
the severity of this bug to allow the updated package to transition.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836740
Cheers,
Ghis
Upstream failed to find the cause for the test issues.
I have requested the removal of the shark binaries currently sitting in
testing for mips and mipsel. Once done, I plan to downgrade this bug to
a non-RC severity to allow the package to transition.
I guess it will be up to mips porters to ge
control: forwarded -1 https://github.com/Shark-ML/Shark/issues/112
Forwarded upstream. Not sure whether this package was intended to work
on these architectures, so upstream might just not care about this.
I'll wait for their reply. The options are:
- Upstream fixes it hopefully.
- Disable testi
control: forwarded -1 https://github.com/pyFFTW/pyFFTW/issues/128
Upstream confirmed the non-portability of the package due to both heavy
reliance on x86 alignment, and availability of the long-double precision
of the FFTW library. The latter is not supported by all architectures.
Solving this i
control: forwarded -1 https://github.com/ismrmrd/ismrmrd/pull/70
Forwarded upstream with a fix.
Ghis
control: forwarded -1 https://github.com/opengm/opengm/issues/475
Thanks for reporting this issue. Upstream has been notified.
Perhaps an explicit cast to size_t where appropriate could solve the compile
error then.
Best regards,
Ghislain
control: forwarded -1 https://github.com/Shark-ML/Shark/issues/110
Indeed, some tests were fixed but not all. Forwarded upstream.
Ghis
On 24/07/16 21:49, Ghislain Vaillant wrote:
Regarding rope, the package has a wishlist bug for Python 3 and also a
CVE (which is bad). It might be worth checking with the package
maintainer whether he still actively maintains it, and propose a
migration to the DPMT Git. I'll contact hi
On 24/07/16 21:10, Jitse Niesen wrote:
On 18/07/16 15:15, Ghislain Vaillant wrote:
If you want to be helpful, please consider reviewing whether the
current state of Debian unstable and check whether it contains all the
necessary dependencies for the packaging of Spyder 3.x to happen.
It&#
interested.
Thanks for the offer. I was hoping for something less time consuming :)
but I will look into packaging Spyder for Debian if that's what it takes.
Spyder is already packaged for Debian FYI.
I believe Ghislain Vaillant (copied in) was thinking at some point to
work on updatin
You are correct, here is the following line in conf.py:
intersphinx_mapping = {'https://docs.python.org/': None}
Thanks for spotting this.
Cheers,
Ghis
On 19/12/15 10:49, Ghislain Vaillant wrote:
Hi Andreas,
Thanks for reporting this bug.
I am not quite sure what the appropriate course of action is here. My
thinking was the following:
libarrayfire-cpu-dev [3.0.2] shipped all CMake configuration files,
since it was the only backend available
Forwarded upstream. Thanks for reporting this issue.
Ghis.
Hi Andreas,
Thanks for reporting this bug.
I am not quite sure what the appropriate course of action is here. My
thinking was the following:
libarrayfire-cpu-dev [3.0.2] shipped all CMake configuration files,
since it was the only backend available at the time.
With the recent inclusion of
On 02/11/15 09:41, Gianfranco Costamagna wrote:
Hi Ghislain, please don't forget to subscribe to your packages...
Currently ismrmrd has an RC bug and is out of testing #802172
can you please have a look at it?
cheers,
G.
Hi Gianfranco, thanks for the heads-up.
I am aware of the RC bug, wh
Hi Matthias,
The setup.py only lists pyzolib as install_requires, not setup_requires.
Therefore, I assumed they were not intended to be installed at build time.
I am also not quite sure whether this package has an official test
suite, so unittest.discover may be picking something which was
u
far as I understand openjpeg is already in Debian [1].
So, let`s do it?
[1] https://tracker.debian.org/pkg/openjpeg2
Cheers
Anton
2015-09-16 11:17 GMT+02:00 Ghislain Vaillant :
Hello everyone,
From Raphael:
Hopefully one the of the people who will discover this RC bug (because
their package
Hello everyone,
From Raphael:
> Hopefully one the of the people who will discover this RC bug
(because their package depends on freeimage or whatever) can be
convinced to take over this package... it has been orphaned for way too
long.
I am one such package maintainers (ArrayFire) affected b
Hi Chris, thanks for reporting this.
Seems that upstream forgot to update the results of some of the doctests.
Forwared upstream here:
https://github.com/pchanial/pyoperators/issues/22
Kind regards,
Ghis
Thanks for reporting this issue, it has been forwarded upstream.
Waiting for upstream to advise on an alternative name for the entry script.
Ghis
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Version 3.12.4 has been recently released upstream, which fixes a decent
list of bugs.
http://ftp.acc.umu.se/pub/GNOME/sources/evolution/3.12/evolution-3.12.4.news
How hard would it be to update the current package ?
Ghis
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
wi
Hi Aaron,
Mea culpa, I messed up my sbuild settings and did not test the package
under proper buildd configuration before flagging the package as ready
for upload. I have added the necessary override on dh_sphinxdoc to avoid
this issue in version 0.8.2-2 of the package.
Thanks,
Ghis
--
To UNS
Hi Aaron,
The failing tests were dropped upstream, so I believe the problem you
are reporting is fixed in the latest version of the package, which now
ships the latest upstream version (0.8.2).
Please let me know if there are further issues with this.
Ghislain
--
To UNSUBSCRIBE, email to debi
Thank you Aaron for reporting the bug and Andreas for providing
instructions for testing the bug.
I have uploaded a new version of the package to the git repository and
tested it against pdebuild with and without the --binary-arch option.
Do I need to do anything else ?
Ghis
--
To UNSUBSCRIBE
Builds of linop covering only its architecture-dependent binary
packages and skipping its architecture-independent -doc package (as on
the autobuilders) have been faiing:
dh_sphinxdoc -a -O--buildsystem=pybuild
dh_sphinxdoc: Sphinx documentation not found
make: *** [binary-arch] Error 2
GDM 3.8 just migrated to unstable and I am also hit by this bug.
A workaround for logging in is to use an alternate logging manager for
now. LightDM did the job well and does not pull a lot of additional
dependencies.
I can't really add anything more to this bug report at this point,
although if
82 matches
Mail list logo
