Bug 16618 - qtiplot: Calculations made between data stored in different columns results in error
Summary: qtiplot: Calculations made between data stored in different columns results i...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL: http://www.qtiplot.com/download.html
Whiteboard: MGA5TOO MGA6TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-20 16:59 CEST by José Eduardo Martins
Modified: 2022-05-01 19:20 CEST (History)
5 users (show)

See Also:
Source RPM: qtiplot-0.9.8.5-12.mga6
CVE:
Status comment:


Attachments

Description José Eduardo Martins 2015-08-20 16:59:47 CEST
Calculations made between data stored in different columns results in error which states that there's no line number 0 in table 1.

steps to reproduce the problem:

1) insert a number in line 1 column 1 and line 1 column 2 of table 1
2) create a new column (ALT+C)
3) rightclick on the new column (=3) and select "define column values"
4) Insert the operation Col("1")+Col("2") which should put the result in line 1 column 3
5) The following message appears "Não existe a linha 0 da tabela 1" (= "There's no line 0 in table 1")

The problem has been corrected in the most recent version o qtiplot (0.9.8.7).
José Eduardo Martins 2015-08-20 17:02:07 CEST

URL: (none) => http://www.qtiplot.com/download.html
CC: (none) => jemartins
Source RPM: (none) => qtiplot-0.9.8.5-9.mga5.src.rpm

Rémi Verschelde 2015-08-20 17:03:58 CEST

Summary: Calculations made between data stored in different columns results in error => qtiplot: Calculations made between data stored in different columns results in error

Comment 1 Samuel Verschelde 2015-09-09 09:10:54 CEST
Hi, unfortunately this package has no dedicated maintainer for now. CC-ing our Qt/KDE packagers, maybe they can have a look.

CC: (none) => juan.baptiste, lmenut, mageia

Luc Menut 2016-08-25 16:42:24 CEST

CC: lmenut => (none)

Comment 2 Marja Van Waes 2017-01-10 12:55:34 CET
(In reply to Samuel Verschelde from comment #1)
> Hi, unfortunately this package has no dedicated maintainer for now. CC-ing
> our Qt/KDE packagers, maybe they can have a look.

We can assign to all packagers collectively now :-)

Doing so.

However, José, please tell us whether you still have this bug in fully updated Mageia 5 and/or fully updated cauldron.

If the problem disappeared, then please change the status of this bug report to "RESOLVED - FIXED"

Thanks!

Keywords: (none) => NEEDINFO
Assignee: bugsquad => pkg-bugs
CC: (none) => marja11

Comment 3 José Eduardo Martins 2017-01-10 14:35:59 CET

Yes, the bug still remain in Mageia 5 and Caldron [qtiplot 0.9.8.5 version]

As said, the problem was solved up stream in qtiplot 0.9.8.7

Thank You, guys!
Comment 4 Rémi Verschelde 2017-01-10 14:40:03 CET
Thanks :)

Cauldron and Mageia 5 should likely both be updated to the latest upstream veersion, 0.9.8.9.

Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA5TOO
Version: 5 => Cauldron

Comment 5 José Eduardo Martins 2017-08-05 12:24:19 CEST
Hi, Rémi,

Did you had time to release that package?

Thanks.
Comment 6 Rémi Verschelde 2017-08-08 10:58:02 CEST
Nope, but I'll try to have a look since no other packager seems to be stepping up.

Assignee: pkg-bugs => rverschelde
CC: (none) => pkg-bugs
Whiteboard: MGA5TOO => MGA5TOO MGA6TOO
Source RPM: qtiplot-0.9.8.5-9.mga5.src.rpm => qtiplot-0.9.8.5-12.mga6

Comment 7 José Eduardo Martins 2017-08-08 11:23:18 CEST
I did a package for 0.9.8.9 qtiplot version (thanks to debian and openmandriva team and yours patchs)

I am not expert so you feel free to review and use.

See in: https://ifserv.fis.unb.br/ftp/pub/linux/qtiplot/

Cheers
Comment 8 sturmvogel 2022-05-01 19:20:47 CEST
Last time we shipped qtiplot was with Mageia 6. 

No actual distribution provides this package any longer (project long time dead since 2011).

As qtiplot is no longer available in Mageia, closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.