On 5/8/23 21:22, Paul Gevers wrote:
Hi Tobias,
On Sat, 6 May 2023 10:24:41 + Tobias Hansen wrote:
Note that we could also just remove python3-sage and the autopkgtest.
I assume you mean python3-brial here.
Yes indeed.
Nothing in Debian depends on it
Not true (and it'
On 5/2/23 14:20, plugwash wrote:
I've prepared a NMU, and intend to open a pre-approval
request with the release team. If you have any objections
to the NMU please tell me ASAP (I do not intend to upload
it until I receive a response from the release team, if you
would preffer to make the upload
On 2/6/23 23:23, Adrian Bunk wrote:
> I can make a 0-day NMU if you don't want to upload giac.
>
> That's not a nice thing to do, but given the freeze deadline it's pretty
> urgent.
>
> cu
> Adrian
That would be great, thanks! It's team maintained, I don't think anyone will be
upset about it.
B
Control: block -1 by 1030687
I applied the patches and confirmed that the package builds now. I can upload
it once giac is fixed.
Hi Rogo,
awesome, that helps a lot! Thanks for figuring all this out. I had already
started determining which patches need to be applied, but wasn't finished yet.
Could you please file a bug against giac to get the uchar issue fixed?
Best,
Tobias
Control: retitle -1 "FTBFS with setuptools >= 64"
Control: block 1028345 by -1
Control: block 1013399 by -1
Control: block 1022254 by -1
Control: block 1022278 by -1
Control: block 1028433 by -1
Control: block 1025874 by -1
Just to clarify that the issue is simply that I can't build sagemath due t
On 12/23/22 12:56, Nilesh Patra wrote:
> On Sat, 10 Dec 2022 18:07:53 +0530 Nilesh Patra wrote:
>> On Mon, 28 Nov 2022 21:05:07 +0000 Tobias Hansen wrote:
>>> On 11/27/22 19:24, Nilesh Patra wrote:
>>>> On Sun, Nov 27, 2022 at 05:35:17PM +, Tobias Hansen
On 11/27/22 19:24, Nilesh Patra wrote:
> On Sun, Nov 27, 2022 at 05:35:17PM +0000, Tobias Hansen wrote:
>> On 11/27/22 06:37, Nilesh Patra wrote:
>>> Tobias, since this is done, would you consider to check sagemath now and
>>> get the ball rolling? :-)
>> Hi,
>
On 11/27/22 06:37, Nilesh Patra wrote:
> Tobias, since this is done, would you consider to check sagemath now and get
> the ball rolling? :-)
Hi,
I actually tried building with the new pari and gap versions a while ago (using
sagemath 9.5 with upstream patches for the new pari and gap versions
Thanks! I will apply the patch once the pari version with the other fixes is
uploaded.
Best wishes,
Tobias
On 10/26/22 10:55, Bill Allombert wrote:
> Also I consider the error message change
> - PariError: call_python: forbidden multiplication t_VEC (1 elts) * t_VEC
> (1 elts)
> + PariE
Hi Ileana,
are you aware of the bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020436
Bill posted a suggestion how to fix this test there yesterday.
Best wishes,
Tobias
On 10/19/22 14:44, Ileana Dumitrescu wrote:
> Hi Julien,
>
> I applied pari.patch to fix the compile issues with new u
I tried rebuilding with this patch from sagemath:
|diff --git a/src/pari.cc b/src/pari.cc index 76ce8e1..50d08ab 100644 ---
a/src/pari.cc +++ b/src/pari.cc @@ -40,6 +40,13 @@ using namespace std; #ifdef
HAVE_LIBPARI +// Anyarg disappeared from PARI 2.15.0 +#ifdef __cplusplus +#
define ANYARG ..
Control: block -1 by 1020436 1020456
Before sagemath can be fixed, cypari2 and giac have to be built against pari
2.15.
On 10/13/22 19:08, Paul Gevers wrote:
> Control: severity -1 serious
>
> Hi,
>
> On Fri, 23 Sep 2022 15:55:41 +0200 Bill Allombert wrote:
>> Please update sagemath so that i
Hi,
not all tests are expected to pass in sagemath's test suite.
The issue is always described at the end:
Success: 62 tests failed, up to 100 failures are tolerated
Error: critical test failures (e.g. timeout, segfault, etc.)
And in the overview above that, it indicates a segfault:
sage/src/sa
Package: libglu1-mesa-dev
Version: 9.0.2-1
Severity: serious
Control: block 1008372 by -1
Hi,
recently sludge started to FTBFS with the following error, see #1008372:
Package 'opengl', required by 'glu', not found
I believe this is because glu.pc now depends on opengl.pc which means that
libgl
Hi,
this is not a regression, as the armhf and mips64el tests never passed, see
#1004872 and #920147. There was a bug in the package that caused the tests not
to be run when building with python 3.10, so the armhf and mips64el package
builds succeeded. The packages for these architectures shoul
On 12/11/21 22:22, Jochen Sprickerhof wrote:
> Package: ecl
> Version: 21.2.1+ds-1
> Severity: critical
> X-Debbugs-Cc: jspri...@debian.org
>
> Hi,
>
> according to policy:
>
> "The run-time shared library must be placed in a package whose name
> changes whenever the SONAME of the shared library
Version: 9.4-1
Hi,
memory-allocator passed NEW now.
Best,
Tobias
On 12/24/21 10:33 PM, Alexandre Lymberopoulos wrote:
> Hi, Tobias.
>
> Thanks for the prompt elucidation.
>
> Best, Alexandre
>
> On December 24, 2021 6:17:16 PM GMT-03:00, Tobias Hansen
> wrote:
>
Hi,
memory-allocator is in NEW (https://ftp-master.debian.org/new.html) since two
weeks and waiting to be approved for inclusion in Debian. I uploaded sagemath
9.4 after memory-allocator but it passed NEW faster.
Best,
Tobias
On 12/24/21 9:45 PM, Alexandre Lymberopoulos wrote:
> Package: pytho
Source: sagemath
Version: 9.2-2
Severity: serious
Control: block -1 by 992003
Control: block 986527 by -1
Control: block 993149 by -1
I started updating sagemath to version 9.4, which is the first version that
supports pari 2.13 (which is already in Debian and causes a large part of the
failing
I started updating sagemath to version 9.4, which is the first version that
supports pari 2.13 (which is already in Debian and causes a large part of the
failing doctests). I got stuck for now because we need an update of singular
(see #992003).
Best,
Tobias
On 8/27/21 7:37 PM, Paul Gevers wro
Thanks a lot for the patches Ahzo. Especially fixing the file handle leak
should help a lot.
I guess it's too late for bullseye now, but I can at least upload a fixed
package to experimental. I'll also try to fix many of the failing tests by
including sage's (large) patch to support pari 2.13 w
Hi,
On 5/18/21 8:25 PM, Jochen Sprickerhof wrote:
>
> I think there are a number of problems:
> - Tests not being executed due to the open file limit ("Killing test" in
> the log). If you want to use the tests as an indicator if the build works,
> you should make sure the all tests are execu
Control: tags -1 + pending
It should be fixed in git, but before another upload cypari2 needs to be
updated.
Best,
Tobias
On 10/27/20 5:17 PM, Graham Inggs wrote:
> Control: reopen -1
>
> Hi
>
> The new upload of sagemath/9.2-1 still FTBFS [1] with Python 3.9 as
> default. I've copied what I h
Control: tag -1 pending
Hello,
Bug #955082 in pexpect 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:
https://salsa.debian.org/python-team/modules/pexpect/-/commit/4fd5b97f7a2b625628406
Hi,
since flint 2.6.3 is now in unstable, can this be fixed with a rebuild?
Best,
Tobias
On Wed, 29 Jul 2020 09:36:31 +0200 Jerome BENOIT wrote:
> Hello Lucas, thanks for the report. I am working on it. Jerome
> --
> Jerome BENOIT | calculus+at-rezozer^dot*net
> https://qa.debian.org/developer.
Control: tags 963338 + help
Just yesterday I just did a test build of vanilla sage (not the Debian package)
9.2.beta6 with the python 3.8 patch from [1] and Debian's python 3.8 to see if
the file handle leak that happens during parallel builds of the Debian package
also happens there. It didn't
Source: gap-atlasrep
Version: 2.1.0-1
Severity: grave
Hi Bill,
during a test build of sage I noticed that the newly updated gap-atlasrep
package seems to be seriously broken. Trying the first commands from the
atlasrep tutorial yields this:
$ gap
┌───┐ GAP 4.10.2 of 19-Jun-2019
│ GAP
The reason for this is that src/scripts/cysignals-CSI calls python which is not
installed. The script has to be ported to python3.
Best,
Tobias
On 2/23/20 2:37 PM, Lucas Nussbaum wrote:
> Source: cysignals
> Version: 1.10.2+ds-3
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullsey
Control: block -1 by 953633
We have a patch for this but I'm waiting for a fix of a bug in pari that causes
test failures and a test timeout.
Best,
Tobias
On Wed, 29 Jan 2020 17:46:47 +0100 Tobias Hansen wrote:
> It does if applied first. But ok, the ipython 7 patch needed so
Hi,
yes, it also looks more like doxygen bug to me. I didn't reassign yet because
if doxygen upstream does not want to fix it, a workaround in ppl (not pplpy)
might be needed.
Best,
Tobias
On 2/23/20 8:46 PM, Julien Puydt wrote:
> Hi,
>
> it looks more like a doxygen 1.8.16 bug than a pplpy i
Hi Matthias,
you reassigned the two bugs #945522 and #949029 to brial, however I don't see
any connection to brial. Neither beancount nor python-bleach depends on brial,
which is a math library for dealing with polynomials over boolean rings by the
way.
Did you confuse brial with something els
Package: libm4rie-0.0.20200125
Version: 20200125-1
Severity: serious
Hi,
seems that something went wrong with the binary upload of libm4rie on amd64. On
this architecture libm4rie-0.0.20200125 depends on libm4ri-0.0.20200115 which
makes it uninstallable. This might be fixable with a source-only
Control: forwarded 944648 https://trac.sagemath.org/ticket/28795
On 11/28/19 2:09 AM, peter green wrote:
>> All three failures give the error message
>>
>> OverflowError: Python int too large to convert to C long
>>
>> from
>>
>> File "sage/rings/polynomial/polynomial_integer_dense_flint.pyx", lin
It seems like the build failures are related to timeouts of jmol. These
timeouts started roughly at the time when the default Java version was changed
in java-common from 10 to 11 in October 2018.
There are also other reports of jmol being broken depending on the jre version,
see
https://ask.sa
Source: sagemath
Version: 8.9-2
Severity: serious
Since the switch to Python 3 in 8.9~beta9-1, sagemath fails to build from
source on i386. The reason are segmentation faults in the following three tests:
sage -t --long src/sage/schemes/elliptic_curves/isogeny_small_degree.py #
Killed due to s
Control: affects 941557 - src:maxima-sage
Thanks for providing the solution for the problem!
Best,
Tobias
On 10/29/19 2:24 PM, Norbert Preining wrote:
> reassign 941557 src:gri
> tags 941557 + patch
> retitle 941557 texi file need @documentencoding
> thanks
>
> With texinfo 6.7 finally the defa
Control: reassign 941557 src:texinfo 6.7.0.dfsg.2-5
Control: affects 941557 + src:gri src:maxima-sage
Control: retitle 941557 texinfo: Malformed UTF-8 character in ParserNonXS.pm
This is probably a bug in texinfo, since both the program giving the error
(makeinfo) and the file it is complaining a
On 6/21/19 10:54 PM, Adam Borowski wrote:
> Control: severity -1 grave
> Control: tags -1 +patch
>
> (patch is
> https://salsa.debian.org/pulseaudio-team/pulseaudio/merge_requests/5)
>
> On Fri, Jun 21, 2019 at 11:37:48AM +0200, Tobias Hansen wrote:
>> I just update
On 1/22/19 8:59 AM, peter green wrote:
> sagemath versions from 8.4-2 through to 8.6-2 have failed to build on mipsel
> and mips64el.
snip
> This will need to be dealt with one way or the other (either by fixing the
> build failures or by requesting removal of the old binaries) before sagemath
>
On 12/30/18 2:59 AM, Sandro Tosi wrote:
>> You are right, I didn't notice the new matplotlib2 package and sagemath
>> failed to build due to the missing matplotlibrc in python-matplotlib-data.
> this should be fixed, does sagemath build fine now?
>
It fixes the errors from matplotlib, thanks! Now
27;m not sure
>what is the problem you're having - check again?
>
>On Thu, Dec 27, 2018 at 12:08 PM Tobias Hansen
>wrote:
>>
>> Hi Sandro,
>>
>> I was just about to finish an update to the sagemath package when you
>uploaded matplotlib 3.0.2 to unstable
Hi Sandro,
I was just about to finish an update to the sagemath package when you uploaded
matplotlib 3.0.2 to unstable. We need the Python 2 package for sagemath (see
#917428). Would you be ok with me uploading matplotlib 2.2.3 as a separate
source package that provides python-matplotlib? Or wo
Package: src:sagemath
Version: 8.4-2
Severity: serious
Tags: sid buster
Control: block 912980 by -1
Control: block 912593 by -1
Control: block 890231 by -1
matplotlib 3.0 was recently uploaded to Debian unstable. This version requires
Python 3 and hence the package python-matplotlib was removed.
Package: grub-efi-amd64
Version: 2.02~beta3-5+deb9u1
Severity: critical
After updating grub2 in Debian stable to 2.02~beta3-5+deb9u1 the UEFI boot
option was removed on my Dell Latitude 5480. After rebooting I was greeted with
"No bootable devices found". In the setup utility (reached by pressin
Control: tags -1 + pending
This bug is easy enough to fix, however it doesn't make sense to upload a new
version at the moment due to #912980.
debian/control is in .gitignore because it is generated in debian/rules from
debian/control.in, mostly to avoid writing the control fields for all the
Package: src:sagemath
Version: 8.4-2
Severity: serious
Tags: sid buster
Control: forwarded -1 https://trac.sagemath.org/ticket/22626
Control: block -1 by 912862
gap 4.9.3 was recently uploaded to Debian unstable. sagemath is not yet
compatible to this version, see upstream bug.
Control: reassign -1 cantor-backend-sage
Please provide more information. How can the bug be triggered? I'm not familiar
with cantor. If someone can demonstrate that the segfault is really in sage,
the bug can be reassigned to sagemath.
Best,
Tobias
On 10/15/2018 03:34 PM, Kinky Nekoboi wrote:
It looks like it's just a typo in the maintscript. The path is
/usr/share/doc/libecm1-dev-common but the mainscript file is:
symlink_to_dir /usr/share/doc/libecm1-dev /usr/share/doc/libecm1-common-dev
7.0.4+ds-2~
Best,
Tobias
On Fri, 5 Oct 2018 09:49:34 +0400 Jerome BENOIT wrote:
> Hi Andreas
ange
> Control: affects -1 sagemath
>
> On Thu, Oct 11, 2018 at 05:55:06PM +0200, Tobias Hansen wrote:
>> It's not a bug in sagemath. The problem is that the singular library package
>> was not renamed even though the library name changed.
>> However this is only a pro
It's not a bug in sagemath. The problem is that the singular library package
was not renamed even though the library name changed.
However this is only a problem for people who somehow do partial updates.
Best,
Tobias
On 10/11/2018 05:44 PM, Rann Bar-On wrote:
> That does the trick. Should it be
Hi,
please update libpynac18 to 0.7.22-3.
Best,
Tobias
On 10/11/2018 05:19 PM, Rann Bar-On wrote:
> Package: sagemath
> Version: 8.3-3
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The relevant output from the crash report:
>
> ImportError: libsingular-fact
On Mon, 6 Nov 2017 02:08:44 +0100 Steve Cotton
wrote:
> On Fri, Oct 27, 2017 at 07:55:52AM +0200, Steve Cotton wrote:
> > On Thu, 19 Oct 2017 22:47:00, Ximin Luo wrote:
> > > These files are clearly not source code. But luckily it should
> > > be possible to regenerate them from the git repo I me
Hi,
please upgrade your packages and try again. Your version of libfint-arb2 should
be 1:2.12.0-3.
Best,
Tobias Hansen
On 07/02/2018 06:26 PM, Rann Bar-On wrote:
> Package: sagemath
> Version: 8.2-5
> Severity: grave
> Justification: renders package unusable
>
> Dear Mainta
Control: severity -1 normal
Hi Helmut,
thanks for the bug report. We are aware that brial has a circular dependency
with sagemath. src:sagemath build-depends on src:brial and python-brial should
depend on sagemath. We didn't add this dependency in order not to manifest the
circular dependency
Control: block -1 by 888459 888911
Not a surprise as long as some dependencies are built against libmpfr4.
On 01/31/2018 06:01 AM, Matthias Klose wrote:
> Package: src:sagemath
> Version: 8.2-1
> Severity: serious
> Tags: sid buster
>
> see https://buildd.debian.org/status/package.php?p=sagemath&
Hi,
yes, I think you can update cysignals in unstable. I applied upstream patches
for new mpfr and matplotlib versions to sagemath and built it with both
versions of cysignals yesterday and got the same problems:
sage -t --long src/sage/rings/number_field/number_field.py # Bad exit: 1
sage -t
On 01/27/2018 01:41 PM, Jerome BENOIT wrote:
> Hello Vincent, thanks for your bugreport.
>
>
>
> On 27/01/18 06:31, Vincent Lefevre wrote:
>> Package: src:mpfi
>> Version: 1.5.3+ds-1
>> Severity: serious
>> Justification: Policy 7.2
>>
>> The current libmpfi-dev version is 1.5.3+ds-1+b1, which has:
Control: tags -1 +pending
Fixed in git, but we need for a libgap-sage update before the next upload.
Control: affects -1 + python-scipy python-fpylll
Cython autogenerated code uses the fpectl macros, so removing fpectl
breaks the ABI of probably all Cython modules, see [1] for a more
detailed explanation.
The last sagemath build [2] shows that at least also scipy and fpylll
are affected, with er
On 07/28/2017 03:06 PM, Jerome BENOIT wrote:
>
> On 28/07/17 17:53, Tobias Hansen wrote:
>> On 07/28/2017 02:38 PM, Jerome BENOIT wrote:
>>> On 28/07/17 17:28, Tobias Hansen wrote:
>>>> On 07/28/2017 02:24 PM, Jerome BENOIT wrote:
>>>>> On 24/07/17 1
Hi Yaroslav,
looks like upstream included the fix in cython 0.25.2, so if you don't
wait too long this bug can still be fixed by just uploading the new version.
Best,
Tobias
On Fri, 2 Dec 2016 08:14:24 -0500 Antonio Russo
wrote:
> tags -1 + patch
>
> Upstream has posted a patch for this issue.
And also #831442, which has a workaround that can be applied to tachyon.
Best,
Tobias
On 12/15/2016 05:03 PM, Tobias Hansen wrote:
> Hi,
>
> yes, this looks like #842881.
>
> Note by the way that libtachyon-mpich-0 already depends on libmpich12 on
> hurd-i386, m68k, mips, mip
Hi,
yes, this looks like #842881.
Note by the way that libtachyon-mpich-0 already depends on libmpich12 on
hurd-i386, m68k, mips, mipsel, ppc64 and sh4.
Best,
Tobias
On 12/15/2016 04:56 PM, Jerome BENOIT wrote:
> Hello,
>
> I can reproduce the issue in schroot Sid environment on an amd64 box.
On 11/29/2016 06:01 PM, Tobias Hansen wrote:
> On 11/29/2016 03:53 PM, Doug Torrance wrote:
>> Control: reassign -1 src:givaro
>>
>> On 11/29/2016 09:58 AM, Tobias Hansen wrote:
>>> I think I figured out at least the test failures with "Illegal
>>> inst
On 11/29/2016 03:53 PM, Doug Torrance wrote:
> Control: reassign -1 src:givaro
>
> On 11/29/2016 09:58 AM, Tobias Hansen wrote:
>> I think I figured out at least the test failures with "Illegal
>> instruction" on i386. The problem is that givaro is built using
Hi Doug,
I think I figured out at least the test failures with "Illegal
instruction" on i386. The problem is that givaro is built using cpu
extensions that are not allowed.
Jerome figured out in [1] that the problem happens when givaro code is
called. And sure enough:
objdump -S /usr/lib/i386-li
On Thu, 3 Nov 2016 20:25:23 +0100 Julian Taylor
wrote:
> On 03.11.2016 20:17, Sandro Tosi wrote:
> >> Looks like your last upload fixed the build on most architectures. However
> >> the
> >> package still failed to build on arm64.
> >>
> >> https://buildd.debian.org/status/package.php?p=pyzmq
> >
Control: tags -1 + patch
Here is a patch that contains the two upstream commits that fix the
issue. I tested it on i386. Yaroslav, do you mind if I upload the fix or
do you want?
Best,
Tobias
>From afeb193f97a5f7b85f7128f252b6071127e4031a Mon Sep 17 00:00:00 2001
From: Stefan Behnel
Date: Sun, 2
Source: cython
Severity: serious
Version: 0.25.2~b0-1
Control: forwarded -1 https://github.com/cython/cython/issues/1530
Dear maintainer,
the package fails to build on 32 bit architectures. There is already an
upstream bug report and a partial fix.
Best,
Tobias
On 11/21/2016 01:03 PM, Sebastian P. Luque wrote:
> On Sun, 20 Nov 2016 19:57:53 -0600,
> Sebastian P. Luque wrote:
>
>> On Sun, 20 Nov 2016 21:01:08 +0000,
>> Tobias Hansen wrote:
>
>> [...]
>
>>>> $ ls -alh ~/.local/lib/python2.7/site-packages/
On 11/21/2016 01:57 AM, Sebastian P. Luque wrote:
> On Sun, 20 Nov 2016 21:01:08 +,
> Tobias Hansen wrote:
>
> [...]
>
>>> $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K
>>> drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 . drwx-- 20
On 11/20/2016 08:29 PM, Sebastian P. Luque wrote:
> On Sun, 20 Nov 2016 19:17:49 +,
> Tobias Hansen wrote:
>
>> If you google this you see that tons of people have similar issues:
>> https://github.com/ipython/ipython/issues/9656
>> https://github.com/ipython/i
If you google this you see that tons of people have similar issues:
https://github.com/ipython/ipython/issues/9656
https://github.com/ipython/ipython/issues/9815
https://github.com/chrippa/backports.shutil_get_terminal_size/issues/9
The most common "solution" there is reinstalling something with
Control: tags -1 + patch
This was fixed upstream. Here is the patch:
https://github.com/cython/cython/commit/6dd263aa3d2d6d80f2d7b96a640a27538fdaa0b2.patch
Best,
Tobias
On Wed, 10 Aug 2016 14:20:36 +0200 Andreas Tille wrote:
> On Wed, Aug 10, 2016 at 02:12:20PM +0200, Jakub Wilk wrote:
> > *
e ppl 1.2 transition:
https://bugs.debian.org/844100
Best,
Tobias
On 11/14/2016 02:05 PM, Roberto Bagnara wrote:
>
> Hello Tobias.
>
> Sorry for the delay in answering your message: I was traveling.
>
> On 11/11/2016 02:08 AM, Tobias Hansen wrote:
>> I noticed today tha
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi Release Team,
I noticed yesterday that ppl has two RC bugs and was removed from
testing. I would like to take over the package and fix it, but one of
the RC bugs (#811825) is best fix
Hi Roberto,
I noticed today that ppl was removed from Debian testing due to two RC
bugs. The problem is that ppl 1.2 has a new soname (14), that means it
requires a library transition. We are now already past the library
transition freeze for Debian stretch. Are you shure that the ABI of ppl
chang
Control: severity -1 important
I'm lowering the severity to important to allow testing migration.
fflas-ffpack 1.6.0 in testing is broken since it build-depends on givaro
3.7.2, which is not in testing anymore. For now it is best to have a
working package for the architectures that work (and no pa
Hi Ian,
the response on the upstream bug report looks like it could take a while
with the new release. With regard to the upcoming freeze, could you
please apply the patches so that the package can migrate to testing?
Best,
Tobias
On Tue, 1 Nov 2016 11:23:19 +1100 Ian Wienand wrote:
> I'm sorry
61cb26ca92c352d1d2f3230d446147b7c7c3e47c
Author: Tobias Hansen
Date: Fri Aug 12 13:38:56 2016 +
Set http_proxy='127.0.0.1:9' for sphinx-build to prevent internet access.
diff --git a/debian/changelog b/debian/changelog
index a07972c..a77f626 100644
--- a/debian/changelog
+++ b/debian/changelo
the report.
>
>
>
> On 05/07/16 18:46, Tobias Hansen wrote:
>> Source: mpfi
>> Version: 1.5.1+ds-4
>> Severity: grave
>> Justification: prevents package upgrade
>
>> Hi Jerome,
>
>> When upgrading from version 1.5.1+ds-2, I get the following
Source: mpfi
Version: 1.5.1+ds-4
Severity: grave
Justification: prevents package upgrade
Hi Jerome,
When upgrading from version 1.5.1+ds-2, I get the following error:
Preparing to unpack .../libmpfi-dev_1.5.1+ds-4_amd64.deb ...
dpkg-query: no packages found matching libmpfi-dev:amd64
dpkg-query:
Control: severity -1 important
I'm lowering the severity for now because i suspect this happens only with
some older graphics cards.
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
Hi,
it works for me. Which graphics card and driver are you using?
Best,
Tobias Hansen
Am 03.05.2015 um 14:26 schrieb Nils Dagsson Moskopp:
> Package: out-of-order
> Version: 1.0-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> I sta
Control: tags -1 +pending
A fix for this is currently in the NEW queue.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Dear Eric,
I noticed that there was this reply to your bug report, directed at you
but apparently not sent to you (only to the bug). So, would it be
possible to share this file?
Best,
Tobias
On Sat, 13 Dec 2014 20:14:07 +0100 Thomas Girard
wrote:
> tag 767423 + moreinfo
> thanks
>
>
> Hello,
Am 21.12.2014 um 17:09 schrieb Mario Izquierdo Rodríguez:
>
>>
>> Hi,
>>
>> I just realized that there are already different versions in testing and
>> unstable. That means we have to upload a targeted fix for the bug for
>> the package version that is in testing (0.89.93) to
>> testing-proposed-u
Am 21.12.2014 um 16:31 schrieb Mario Izquierdo Rodríguez:
> El 21/12/14 a las 16:17, Tobias Hansen escribió:
>> Am 21.12.2014 um 16:05 schrieb Mario Izquierdo Rodríguez:
>>> El 19/12/14 a las 22:03, Tobias Hansen escribió:
>>>> On Tue, 02 Dec 2014
Am 21.12.2014 um 16:05 schrieb Mario Izquierdo Rodríguez:
> El 19/12/14 a las 22:03, Tobias Hansen escribió:
>> On Tue, 02 Dec 2014 21:29:29 +0100
>> =?UTF-8?B?TWFyaW8gSXpxdWllcmRvIFJvZHLDrWd1ZXo=?=
>>wrote:
>>> El 24/11/14 a las 15:28, Jonathan Wiltshire escrib
On Tue, 02 Dec 2014 21:29:29 +0100
=?UTF-8?B?TWFyaW8gSXpxdWllcmRvIFJvZHLDrWd1ZXo=?=
wrote:
> El 24/11/14 a las 15:28, Jonathan Wiltshire escribió:
> > On Mon, Nov 24, 2014 at 12:05:21AM +0100, Mario Izquierdo RodrÃguez wrote:
> >> El 23/11/14 a las 19:40, Jonathan Wiltshire escribió:
> >>> Con
t; Best regards,
>
> --
> Arnaud Degroote
> ISAE DMIA
>
>
diff -Nru morse-simulator-1.2.1/debian/changelog
morse-simulator-1.2.1/debian/changelog
--- morse-simulator-1.2.1/debian/changelog 2014-07-14 15:09:04.0
+0200
+++ morse-simulator-1.2.1/debian/changelog 20
Control: tags -1 + pending
Thanks. I told upstream about the bug in the resizing algorithm and will
upload either a fix or disable the test soon.
Best,
Tobias
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
Control: tags -1 + patch
Hi,
the problem is a faulty postrm script that removes /usr/bin/ecl on
upgrade after the new files are unpacked, see [1]. A workaround is to
remove ecl and then install it again. The attached patch fixes the
postrm script but since the old postrm script is run on upgrade
Hi,
this bug was now reported as
#722161 against cogl
#745901 against fglrx-driver
#744152 against gdm3
I posted a workaround to #745901 [1]. The bugs should be merged and
linked to the affected packages with "affects" but I'm not sure if the
bug is in cogl or fglrx. It should probably be fixed
Comment 4 from [1] has a workaround that lets you use GNOME and fglrx
together. I had to switch to lightdm since gdm3 doesn't work and use
this ~/.xsession:
export COGL_DRIVER=gl
export COGL_OVERRIDE_GL_VERSION=1.4
export COGL_RENDERER=GLX
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/fglrx/fglrx-li
Here are links to the gnome and (unofficial) amd bugs that seem relevant:
https://bugzilla.gnome.org/show_bug.cgi?id=712340
http://ati.cchtml.com/show_bug.cgi?id=949
It seems related to GNOME enabling EGL/Wayland support. The first
version of clutter-1.0 with EGL support enabled that migrated to
found 745901 1:14.3~beta1.0-1
thanks
I have the same problem with the fglrx version in testing with a Radeon
HD 7750 (Southern Islands).
Cheers,
Tobias
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Hi Bill,
I already did.
Cheers,
Tobias
On 04/15/2014 11:02 AM, Bill Allombert wrote:
> Woould anybody object if I asked for the removal of this package ?
> As far as I can see it is not maintained, buggy, and quite useless now
> that gp includes the functionnality (without the bugs).
>
> Cheers,
tag 733362 + patch fixed-upstream
forwarded 733362 https://bugzilla.gnome.org/show_bug.cgi?id=706462
thanks
Should be fixed by the upstream patch in
https://bugzilla.gnome.org/show_bug.cgi?id=706462
See also
https://bugzilla.gnome.org/show_bug.cgi?id=705401
which has the same compile error as rep
1 - 100 of 156 matches
Mail list logo
