It looks like Ultimaker dropped official 32 bit support:
https://github.com/Ultimaker/CuraEngine/issues/547
@pere fixed a few obvious bugs, but testing and more patches (if required) are
welcome.
cura-engine 2.5.0 is available in sid.
Note that it's currently missing libArcus for integration into
>> Uranium and Cura are both ready for review.
>
> Very good. I'll have a look, and hope we can coordinate any fixes on
> IRC.
>
> Btw, are you aware of http://dep.debian.net/deps/dep3/ >?
Partially. I know the guidelines for patches, but wasn't aware of this DEP.
I'll look at it.
[Gregor Riepl]
>> The only packages left now are uranium and cura.
>
> Uranium and Cura are both ready for review.
Very good. I'll have a look, and hope we can coordinate any fixes on
IRC.
Btw, are you aware of http://dep.debian.net/deps/dep3/ >?
--
Happy hacking
Petter Reinholdtsen
> I've just uploaded libsavitar to NEW, after giving the d/copyright file a
> close
> look. I am aware of the several proposals for improvements, but concluded
> that those can be uploaded next time, and decided it was more important
> to get a slot in the NEW queue for now.
>
> The only package
[Gregor Riepl]
> For some very strange reason, I don't see this SEGFAULT when I run the build
> process in a 32-bit VM on an amd64 system. Valgrind doesn't report any errors
> either.
The cause was incorrect use of sprintf() with int64_t. I've added patches
for this to the latest upload, see
http
A little update on the StringTest failures on 32-bit systems.
This was already reported upstream by thopiekar:
https://github.com/Ultimaker/CuraEngine/issues/619
I linked the sid build results there.
For some very strange reason, I don't see this SEGFAULT when I run the build
process in a 32-bit
[Gregor Riepl]
> Before you upload cura-engine, please pull again.
> I forgot to change the Maintainer to the list.
Then thing is, I can not upload cura-engine depending on libarcus as
long as libarcus is in NEW, as it will fail to build. But I can upload
libsavitar and uranium, as they will go i
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
Before you upload cura-engine, please pull again.
I forgot to change the Maintainer to the list.
Hi Petter
> So, libarcus is uploaded and in NEW, and cura-engine is ready to be
> uploaded but held off until its build dependency libarcus is in
> unstable (what about uploading without arcus support for now?)
CuraEngine is not of much use without libArcus, I'm afraid...
I'm not sure if it even
So, libarcus is uploaded and in NEW, and cura-engine is ready to be
uploaded but held off until its build dependency libarcus is in
unstable (what about uploading without arcus support for now?)
I'm reluctant to touch the git repository of the remaining packages,
given that their structure is goi
Hi,
Thanks both for getting this moving again! I was distracted, so didn't reply,
sorry about that. I agree that the packages are in pretty good shape, and any
problems that they still have can be dealt with after they have moved into
unstable.
If I'm to sponsor the package, I would suggest bec
[Gregor Riepl]
> That must have changed in the meantime...
> It was still ok when I packaged 2.5.0 AFAIR.
Yes, it changed fairly recently.
> I did quite a bit of research, and I'm almost certain it's a false positive.
> The docs mention posting to
> https://bugs.debian.org/cgi-bin/bugreport.cgi?b
> Do you plan to maintain these packages as part of the 3dprinter group?
> If so, the maintainer should be changed from your name to the mailing
> list, to make sure the packages show up on
> https://qa.debian.org/developer.php?login=3dprinter-gene...@lists.alioth.debian.org
> >.
Ok.
> The pack
[Gregor Riepl]
> Yes. The source packages I pushed to Debian Mentors correspond to the
> branches on git.debian.org.
Very good. I had a quick look at some of the packages, and noticed a
few things, none of which is serious enough to delay an upload to the
NEW queue for review.
Do you plan to mai
>> The package is on mentors.debian.net, but you also need to get all the
>> dependencies if you want to build it yourself:
>> https://mentors.debian.net/packages/uploader/onitake%40gmail.com
>
> Is this the same code as on git.debian.org?
Yes. The source packages I pushed to Debian Mentors corre
Hi Gregor.
[Gregor Riepl]
> sorry about the delay. I was waiting for a review from Bas (or another
> DD). The package is also currently stuck at version 2.5.0, due to a
> lack of time on my side, but I'll try to prepare and push an update
> ASAP.
No worries.
> The package is on mentors.debian.n
Hi Petter,
sorry about the delay. I was waiting for a review from Bas (or another DD).
The package is also currently stuck at version 2.5.0, due to a lack of time on
my side, but I'll try to prepare and push an update ASAP.
The package is on mentors.debian.net, but you also need to get all the
de
Hi. What is the status for getting Cura into Debian? What is holding up
the upload?
I need it for a project, and would love to get official Debian packages for
it. If a sponsor is needed, feel free to get in touch. My sponsoring
preferences
are available from http://www.hungry.com/~pere/debia
Hi,
after going through another series of revisions and some cleanup, here is the
set of Cura 2.5 packages for review:
https://mentors.debian.net/package/libarcus
https://mentors.debian.net/package/libsavitar
https://mentors.debian.net/package/uranium
https://mentors.debian.net/package/cura-engin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Wed, May 03, 2017 at 08:57:54AM +0200, Gregor Riepl wrote:
> I just found a few more packages to build:
> https://github.com/Ultimaker/cura-build/tree/master/projects
>
> fdm_materials seems relatively important, I packaged it and added it as
Hi,
I just found a few more packages to build:
https://github.com/Ultimaker/cura-build/tree/master/projects
fdm_materials seems relatively important, I packaged it and added it as a
"Recommends" dependency to Cura. Cura will work without the definitions, but
having them makes it much more useful.
> I agree this is the best way; my point was that you should not have a
> repository on github with a copy of the source, and the watch file should
> point
> to Ultimaker's github. Having a repository with the packaging is good. You
> can also host that in our team repository on Alioth. You are
> Ah yes, clipper has weird and annoying naming. I talked to upstream about it,
> but they don't want to change it. I think it had something to do with a
> package naming conflict in Red Hat. In any case, the package is called
> libpolyclipping. There is a pkg-config file with it, but it's brok
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Apr 04, 2017 at 11:36:37PM +0200, Gregor Riepl wrote:
> > Of course it is still useful to have your packaging (the debian directory)
> > under version control as well, and using names for those releases also
> > makes sense. If you want to na
>> I'll probably settle for debian-2.3.1 (branches) and debian-2.3.1-1
>> (tags).
>
> Ah, I see. I think you should use upstream's releases anyway; if you need
> to make changes for the packaging, they should just be part of the package,
> not a fork from upstream. Especially if the only change
> Any reason you took this off-list? I'm not sending your mail back to it
> without your permission, but if it was a mistake, feel free to post any of my
> replies back to the list as well.
I'm sorry, that wasn't my intention. I believe one of your responses was
addressed to me personally, so I t
And here's my (updated) response to Rock's comments:
> libArcus
>
>
> debian/changelog
>
>
> * There seems to be a line in the changelog that is too long, it'd be
>nice to split it into two so it fits into the "80 character limit".
Done.
> * Typically, new packa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Mon, Mar 27, 2017 at 09:04:21AM +0200, Gregor Riepl wrote:
> > It looks like this has been forgotten? I would like to get Cura into
> > Debian,
> > so if there's anything I can do to help, let me know.
>
> I'm sorry for the lack of action on
Hi,
> It looks like this has been forgotten? I would like to get Cura into Debian,
> so if there's anything I can do to help, let me know.
I'm sorry for the lack of action on my part, progress was stalled since some
of the criticised points are a bit difficult to fix, and I've been too busy to
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
It looks like this has been forgotten? I would like to get Cura into Debian,
so if there's anything I can do to help, let me know.
I also have some comments on the comments:
On Mon, Dec 19, 2016 at 10:51:52PM +0100, Gregor Riepl wrote:
> > * Th
Hi Rock,
Here are my comments, I must say I don't use the software so I only
checked the building and the packaging. I trust you are testing that
once installed all four packages perform as expected :).
Thanks for the review!
I'll comment below.
> libArcus
>
>
> debian/changelog
> --
Hi Gregor,
Here are my comments, I must say I don't use the software so I only
checked the building and the packaging. I trust you are testing that
once installed all four packages perform as expected :).
libArcus
debian/changelog
* There seems to be a line in the ch
Hi Alvaro,
I'm sorry it took me this long to start reviewing your work. I was about to
try to build your packages but I haven't been able to figure out how to do it.
How do you build your packages? Do you use git-buildpackage? I'm missing a
branch named "upstream" or something similar. A typical
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Gregor,
On Thu, Sep 22, 2016 at 01:02:26PM +0200, Gregor Riepl wrote:
> > I can help you with that. If you choose to maintain it in the 3-D printer
> > team, others in the team can also help you out with that.
>
> Very good, how do I sign up? :)
Hi Bas,
> Thanks for taking this on! I've been meaning to do that for quite some
> time, but didn't get to it so far.
>
> Would you be interested in maintaining it inside the 3-D printer team?
Thanks for your comments!
Working with others will certainly speed up things.
I also got pointed to t
Gregor Riepl writes:
> Package: wnpp
> Followup-For: Bug #706656
> Owner: Gregor Riepl
>
> Hello, I've been using Cura (new Cura, not the legacy one) for a while, and
> decided that it would be a good idea to package it up for Debian.
>
> Upstream does not make this particularly easy, but thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Gregor,
Thanks for taking this on! I've been meaning to do that for quite some time,
but didn't get to it so far.
Would you be interested in maintaining it inside the 3-D printer team?
Last time I tried to upload Cura (that was before Uranium, s
I forgot one thing:
- libArcus carries the same version as the rest of the packages, but it
actually uses a different versioning scheme. The shared library is named
libArcus.so.1.0.0, with the SONAME = libArcus.so.2. This may or may not be
correct. A bug report was filed upstream: https://github
Package: wnpp
Followup-For: Bug #706656
Owner: Gregor Riepl
Hello, I've been using Cura (new Cura, not the legacy one) for a while, and
decided that it would be a good idea to package it up for Debian.
Upstream does not make this particularly easy, but thanks to the use of
standard build tools,
Update: I'm having a discussion with upstream, and hopefully we will
soon have a package in the archive. I was waiting for the new release,
which has now happened; now we're looking at the clipperlib that is
used, which seems to be different from the one in Debian.
Thanks,
Bas
On Sat, Jul 27, 20
+1
On May 2, 2013 6:18 PM, "Bas Wijnen" wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Bas Wijnen
>
> * Package name: cura
> Version : 13.04~git20130502-1
> Upstream Author : David Braam (daid...@gmail.com)
> * URL : http://daid.github.io/Cura/
> * License
Package: wnpp
Severity: wishlist
Owner: Bas Wijnen
* Package name: cura
Version : 13.04~git20130502-1
Upstream Author : David Braam (daid...@gmail.com)
* URL : http://daid.github.io/Cura/
* License : AGPL-3+
Programming Lang: Python
Description : Contro
42 matches
Mail list logo
