Bug#906110: freecad-{common,python2},libfreecad-python2-0.17: missing Breaks+Replaces: freecad (<< 0.17)

2018-08-14 Thread Kurt Kremitzki
Hello Andreas, On 08/14/2018 05:17 AM, Andreas Beckmann wrote: > Package: freecad-common,freecad-python2,libfreecad-python2-0.17 > Version: 0.17+dfsg1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package fail

Bug#930563: (no subject)

2019-06-24 Thread Kurt Kremitzki
severity 930563 important thanks Downgrading severity since this issue is not "rendering it completely unusable to everyone."

Bug#956543: freecad: FTBFS with new opencascade 7.4 (library transition)

2020-05-12 Thread Kurt Kremitzki
Hello Gregor, On Tuesday, May 12, 2020 6:58:04 PM CDT Gregor Riepl wrote: > > Status update why this package has not yet been updated: > > If the freecad is rebuilt against pyside2, it will run > > into 945376 at runtime, namely when opening the PartDesign workbench. > > As this is a major feature

Bug#961131: closed by Kurt Kremitzki (Re: freecad: autopkgtest regression with opencascade 7.4)

2020-05-23 Thread Kurt Kremitzki
On Saturday, May 23, 2020 2:56:59 AM CDT Graham Inggs wrote: > > This was fixed in an upload done slightly before the bug was filed, though > > with > > a different patch; I'll probably replace it with this one in a subsequent > > upload. > > Great, thank you! Would you like a merge request, or

Bug#926500: freecad: FreeCad crashes when attemting to edit a existing sketch

2019-04-22 Thread Kurt Kremitzki
Hello Pere, This issue has also been reported in the FreeCAD forums, and there are two likely culprits. One user reported that temporarily moving the ~/.FreeCAD directory and then launching FreeCAD resulted in the issue no longer occurring, which would narrow the cause down to some file in t

Bug#927808: gmsh: FTBFS in buster (/usr/include/occt/Standard_Version.hxx cannot be read)

2019-05-17 Thread Kurt Kremitzki
Hello Ansgar, On 5/17/19 4:14 AM, Ansgar wrote: > On Sun, 2019-05-05 at 18:08 +0100, Rebecca N. Palmer wrote: >> The fix was probably removing the line >> -DOCC_INC:STRING="/usr/include/occt" \ >> from debian/rules (commit 3556b0a, but please don't include the >> reformatting), but I have not tes

Bug#927808:

2019-05-27 Thread Kurt Kremitzki
On 5/27/19 2:45 AM, Nico Schlömer wrote: >> I was going to go ahead and do a +really upload with this fix either today >> or this weekend. > > This is getting rather urgent now. Do you need any help? > No, I just was waiting for the response on #929108. I'm traveling with poor connection now

Bug#945041: openfoam: severe build time regression

2019-12-18 Thread Kurt Kremitzki
On Thursday, December 19, 2019 12:11:33 AM CST Adrian Bunk wrote: > On Mon, Nov 18, 2019 at 10:17:10PM +0100, Julien Cristau wrote: > > Source: openfoam > > Version: 1906+dfsg1-1 > > Severity: serious > > > > Hi, > > > > Looking at https://buildd.debian.org/status/logs.php?pkg=openfoam the > > bu

Bug#942193: dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed.

2019-10-11 Thread Kurt Kremitzki
Package: dwz Version: 0.12-3 Severity: critical Justification: breaks unrelated software Dear Maintainer, I'm not certain if critical is the correct severity, but it seems dwz is causing a build regression in freecad. As part of Python 3 removal, I dropped the Python 2 build and packages in a new

Bug#942193: dwz: dh_dwz freecad build regression: write_die: Assertion `value

2019-10-11 Thread Kurt Kremitzki
Just as an addendum, I just tested the build with sbuild in a dirty unstable-i386 schroot where I had installed dwz 0.12-3 from stable, and the build succeeds, where it fails with 0.13-1.

Bug#942193: dwz: dh_dwz freecad build regression: write_die: Assertion `value && refdcu->cu_kind != CU_ALT' failed.

2019-10-13 Thread Kurt Kremitzki
Hi Matthias, On Saturday, October 12, 2019 12:34:30 PM CDT Matthias Klose wrote: > Control: tags -1 + moreinfo > Control: severity -1 grave > > please could you attach the binary, or put it somewhere on the web? > Sorry, which binary are you referring to? Here are a few links in the meantime t

Bug#923465: fixed in freecad 0.18~pre1+dfsg1-5

2019-03-10 Thread Kurt Kremitzki
Hi Salman, On 3/10/19 9:05 AM, Salman Mohammadi wrote: > Dear Maintainer, > > > I could install this package (0.18~pre1+dfsg1-4) with no problem and > this bug seems to be resolved. But on the tracker page, this package has > been marked for autoremoval on 29 March, with this message: > > Versi

Bug#923465: fixed in freecad 0.18~pre1+dfsg1-5

2019-03-12 Thread Kurt Kremitzki
Hi Robert, On 3/11/19 5:43 PM, Robert LeBlanc wrote: <-snip-> > rleblanc@riker:~/code$ sudo apt -t unstable install freecad <-snip-> Because of file replacements, it requires a `sudo apt full-upgrade`, this installation method won't work.

Bug#917788: libmedc11: Overwrites a file from libmedc1v5

2018-12-30 Thread Kurt Kremitzki
Hi Rock & Gilles, On Sun, 30 Dec 2018 11:01:07 + Rock Storm wrote: > Package: libmedc11 > Severity: grave > > Dear Maintainer, > > While trying to update freecad I run into the following broken apt > state: > > Preparing to unpack .../libmedc11_4.0.0+repack-3_amd64.deb ... > Unpacking libm

Bug#963709: pyside2: FTBFS with Qt 5.14: 'PySide2.QtCore.QDate' called with wrong argument types: PySide2.QtCore.QDate(date)

2020-06-25 Thread Kurt Kremitzki
Hello, On Thursday, June 25, 2020 2:34:19 PM CDT Dmitry Shachnev wrote: > <-snip-> > > The version from experimental (5.15.0-1~exp1) seems to build fine, maybe it > can be uploaded to unstable? > > -- > Dmitry Shachnev Yes, it can be uploaded, I meant to get to it last weekend but wasn't able t