I was trying to finalize a 1.2 release for the end of july
Most of the new stuff is rather stable now.
We have a serious bug with a gentoo distribution (the very important
filter dialog does not show up on some linux distributions),
and a couple of plugins that needs a bit of polishing, but nothin
On Thu, Jul 10, 2008 at 10:34 PM, Yaroslav Halchenko
<[EMAIL PROTECTED]> wrote:
> any new updates on meshlab situation?
Ftp-master rejected the 1.1.1 version because of incomplete copyright
information. This was promptly fixed in the upstream SVN version, so
now I'm waiting for the 1.2 release.
O
any new updates on meshlab situation?
On Wed, 18 Jun 2008, Ian Jackson wrote:
> Yaroslav Halchenko writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
> > ok -- upload is sponsored [stuff]
> Thanks for picking this up while I dropped off the face of
Yaroslav Halchenko writes ("Re: Bug#426581: meshlab - anyone still working on
this"):
> ok -- upload is sponsored [stuff]
Thanks for picking this up while I dropped off the face of the Debian
planet for a couple of months.
Ian.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
ok -- upload is sponsored but for the next upload set a little more
precise dependencies since libqt4-opengl-dev is not available on
hurd-i386, sparc, and you have architecture any, thus it will be FTBFS
on those architectures. Now we should just hope that no major problems
will be detected by ftpm
On Thu, May 15, 2008 at 6:13 PM, Yaroslav Halchenko
<[EMAIL PROTECTED]> wrote:
> got into problem with uptodate sid chroot for pbuilder, although it builds
> fine
> with mixed lenny/sid box (so some versions are from lenny) and it boils
> down to the recent split in libqt4-dev which now has open
got into problem with uptodate sid chroot for pbuilder, although it builds fine
with mixed lenny/sid box (so some versions are from lenny) and it boils
down to the recent split in libqt4-dev which now has opengl relevant headers in
libqt4-opengl-dev...
for some reason
http://packages.debian.org/se
On Mon, May 12, 2008 at 7:33 PM, Yaroslav Halchenko
<[EMAIL PROTECTED]> wrote:
> seems to be missing space upfront of signature... may be smth else as
> well -- just make sure to run lintian on fixed package to assure that it is
> ok
>
> btw -- since you are altering changelog, might be useful
GREAT! but 1 hiccup
*$> lintian -i meshlab_1.1.1-2_i386.changes
W: meshlab: syntax-error-in-debian-changelog line 14 "badly formatted heading
line"
N:
N: While parsing the Debian changelog, an syntax error was found.
N:
N: Refer to Policy Manual, section 4.4 for details.
N:
W: meshlab: syntax
Hi all,
I just put a new version of the meshlab package to mentors.debian.net:
http://mentors.debian.net/debian/pool/main/m/meshlab/
All the problems mentioned previously should be now solved, so to
whoever who wants to sponsor this, please do so.
Teemu
--
To UNSUBSCRIBE, email to [EMAIL PRO
Thank you Paolo!
just 2 cents from me: to don't bother with learning [tg]roff (or
whatever is native man language) I would suggest to make use of help2man
tool http://packages.debian.org/sid/help2man but for that cmdline tools
should have reasonable output on --help ;)
doing it that way you solve
Hi,
for the man pages i have just committed two files named meshlab.1 and
meshlabserver.1 under the docs directory of the new SVN repository of
meshlab.
I have no experience in the formatting language of man so, please
someone should check that
In the next days I would like to try incorporat
Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> The package has not been updated to 1.1.1, and I may not have time to
> do it very soon. Ian did promise to sponsor the package, but I haven't
> heard anything from him lately.
I do exi
Hi Teemu,
Sorry for a delay -- had a look at it:
Here are my comments:
* update copyright years in debian/copyright since there was a new upstream
release this year
* why to have those
#if defined(DEBIAN)
if we are patching sources anyways?
and those points about hardcoded paths already
On Wed, Apr 30, 2008 at 11:58:35AM +0200, Teemu Ikonen wrote:
> On Tue, Apr 29, 2008 at 3:59 AM, Yaroslav Halchenko
> <[EMAIL PROTECTED]> wrote:
> > first -- just to make sure
> > http://esko.osmas.info/~tmx/meshlab/meshlab_1.1.1-1.dsc
> > this one? not the newer by mod date but not in version
>
On Tue, Apr 29, 2008 at 3:59 AM, Yaroslav Halchenko
<[EMAIL PROTECTED]> wrote:
> first -- just to make sure
> http://esko.osmas.info/~tmx/meshlab/meshlab_1.1.1-1.dsc
> this one? not the newer by mod date but not in version
> http://esko.osmas.info/~tmx/meshlab/meshlab_1.1.0b~cvs20070528-1.dsc
>
first -- just to make sure
http://esko.osmas.info/~tmx/meshlab/meshlab_1.1.1-1.dsc
this one? not the newer by mod date but not in version
http://esko.osmas.info/~tmx/meshlab/meshlab_1.1.0b~cvs20070528-1.dsc
right?
or was it sponsored already? (I just get into the mailing list for a
while and that
On Fri, Apr 4, 2008 at 6:21 PM, Teemu Ikonen <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 4, 2008 at 4:15 PM, Yaroslav Halchenko
> <[EMAIL PROTECTED]> wrote:
> > So what was the outcome? ;-) 1.1.1 upstream is out but ITP is still
> > open. Is help/sponsoring needed?
Ok, I updated the package to 1.
On Fri, Apr 4, 2008 at 4:15 PM, Yaroslav Halchenko
<[EMAIL PROTECTED]> wrote:
> So what was the outcome? ;-) 1.1.1 upstream is out but ITP is still
> open. Is help/sponsoring needed?
The package has not been updated to 1.1.1, and I may not have time to
do it very soon. Ian did promise to sponsor
So what was the outcome? ;-) 1.1.1 upstream is out but ITP is still
open. Is help/sponsoring needed?
On Mon, 17 Mar 2008, Teemu Ikonen wrote:
> On Sat, Mar 8, 2008 at 7:00 PM, Paolo Cignoni <[EMAIL PROTECTED]> wrote:
> > we are going to release the v1.1.1 of meshlab
> > and i have arranged the
On Sat, Mar 8, 2008 at 7:00 PM, Paolo Cignoni <[EMAIL PROTECTED]> wrote:
> we are going to release the v1.1.1 of meshlab
> and i have arranged the source with hopefully all the issues that you
> have raised.
>
> Before releasing officially , could you check that the following sources are
> ok?
(__DISABLE_AUTO_STATS__)
checkForUpdates(false);
#endif
Let me know for any compilation problem or other issues. I will try to
patch them.
Cheers
P.
On Wed, Feb 27, 2008 at 3:15 AM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab
Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> We use QT with QSettings mechanism for saving config files in a portable way
Can these files be written other than by Qt ? Our configuration
management systems often need to write to configuration
On Tue, Feb 26, 2008 at 8:01 PM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
>
> > So adding a compile option disabling the default home phoning is
> > probably the best idea.
&g
Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> So adding a compile option disabling the default home phoning is
> probably the best idea.
That would certainly suffice.
> At least can I ask for enabling at the first run?
> Or even thi
On Sun, Feb 24, 2008 at 6:42 PM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
>
> > Ok, I understand your point, I respect and, as i told you since
> > beginning, i agree on disa
Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> Ok, I understand your point, I respect and, as i told you since
> beginning, i agree on disabling it for very pure, and ethically
> coherent distributions like Debian.
>
> As you understood
On Sun, Feb 24, 2008 at 2:54 PM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
>
> > Yes, it phones home regularly.
> >
> > It is well written in the docs
> > http:
Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> Yes, it phones home regularly.
>
> It is well written in the docs
> http://meshlab.sourceforge.net/wiki/index.php/Licenses
Thanks for the reference.
> It seems to me that it is not
Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> (shortened and with intermixed answers...)
Thanks, that's absolutely the right way to respond. So much so that
we don't normally feel the need to mention it :-).
> On Fri, Feb 22, 200
On Fri, Feb 22, 2008 at 10:06 PM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
> > > After I built it (on lenny), I ran meshlab from an xterm. It opened
> > > an entirely
On Fri, Feb 22, 2008 at 10:06 PM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
>
> However I have discovered one thing that we in Debian ought to
> consider release-critical: I h
(shortened and with intermixed answers...)
On Fri, Feb 22, 2008 at 10:00 PM, Ian Jackson
<[EMAIL PROTECTED]> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
>
> > After I built it (on lenny), I ran meshlab from an xter
Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> Thanks for the review. I fixed the problems you found except these:
> > After I built it (on lenny), I ran meshlab from an xterm. It opened
> > an entirely blank override-redirect pale gre
Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> I am a bit ignorant about debian package creation so be patient with my
> naiveness :)
> I would try to help as I can.
> My comments intermixed below.
Thanks for your reply and sorry for the
On Feb 9, 2008 7:08 PM, Ian Jackson <[EMAIL PROTECTED]> wrote:
> Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on
> this"):
> > http://esko.osmas.info/~tmx/meshlab/
> I've reviewed this and it's looking reasonably good.
Hi Ian, Pa
Hi to all,
I am a bit ignorant about debian package creation so be patient with my
naiveness :)
I would try to help as I can.
My comments intermixed below.
(Thanks for your effort!)
After I built it (on lenny), I ran meshlab from an xterm. It opened
> an entirely blank override-redirect pale gr
Teemu Ikonen writes ("Re: Bug#426581: meshlab - anyone still working on this"):
> http://esko.osmas.info/~tmx/meshlab/
I've reviewed this and it's looking reasonably good.
Firstly, two general observations:
* You should run lintian, particularly after making a wholly ne
Teemu Ikonen writes ("Fwd: Bug#426581: meshlab - anyone still working on this"):
> Since you asked about meshlab packages a while ago, are you still
> interested in sponsoring them? I have packages ready for review, see
> the mail below for details.
Thanks.
Teemu Ikone
On Jan 29, 2008 6:42 PM, Paolo Cignoni <[EMAIL PROTECTED]> wrote:
> Hi to all,
> With the new release 1.1.0
> i have prepared, as you requested, a tarball with (hopefully) all the
> needed sources (including vcg)
> it is available at sourceforge at
>
> http://downloads.sourceforge.net/meshlab/MeshL
Hi all,
I made a small effort to bring the meshlab package up to date with the
current CVS version, but had to give up. There were some errors on the
code, such as missing functions or declarations (I probably hit the
CVS on a wrong day), but what stopped me was that the dependency on
lib3ds-dev i
Hi,
I do not have a debian machine directly available for testing,nor i
know how to build debian packages,
but I can help any volunteer in this task.
Version 1.1.0 is almost ready
so if also a debian version would be ready i will be really happy.
Feel free to ask me, (and/or to the meshlab devel
On 2008-01-24 20:50:41 +0100 Ian Jackson
<[EMAIL PROTECTED]> wrote:
Is anyone still working on the meshlab package (and the vcg library) ?
I can do that, I just didn't because there was an ITP and I didn't
want to
do doublework. But since I didn't recieve any reply to my ping, I guess
I'll
Is anyone still working on the meshlab package (and the vcg library) ?
I have a use for it and hoped to find a package, or failing that I
might try to put one together myself.
How far has anyone got ? Any information or pointers would be
valuable.
I found this:
http://gnu.ethz.ch/debian/meshl
44 matches
Mail list logo
