Bug 17980 - Qterminal update
Summary: Qterminal update
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-13 13:23 CET by Otto Leipälä
Modified: 2018-07-12 11:02 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Otto Leipälä 2016-03-13 13:23:38 CET
Qterminal should be updated to newer version,Mageia 5 have 0.4.0 from 2012 original build new version to Mageia 3.
Newer version fix tons of bugs from 0.4.0 it would make sense to update or backport it.
http://sophie.zarb.org/rpms/ffecc99ebe5b1b96219cbf56dc4a7ad2/changelog
Comment 1 Marja Van Waes 2016-03-14 09:45:14 CET
Maintainer is MIA, so assigning to all packagers collectively to decide to update or backport.

@ Matteo

Please feel free to comment, reassing to yourself or do anything you wish with this report... it is still your package ;-)

CC: (none) => marja11, matteo.pasotti
Assignee: bugsquad => pkg-bugs

Comment 2 Rémi Verschelde 2016-03-14 17:18:28 CET
CC'ing Nicolas as IIUC qterminal is part of the LXDE stack: https://github.com/lxde/qterminal

CC: (none) => nicolas.salguero

Comment 3 Nicolas Salguero 2016-03-14 17:30:55 CET
In fact, it is part of LXQt (in LXDE, the equivalent is LXTerminal) but I can try to update it if it helps.
Comment 4 Rémi Verschelde 2016-03-14 17:38:30 CET
CC'ing LXQt maintainer too then :)

I was mislead by the GitHub namespace, though I also wondered but could not find a LXQt-branded repository with qterminal.

CC: (none) => doktor5000

Comment 5 Florian Hubold 2016-03-16 00:50:23 CET
(In reply to Rémi Verschelde from comment #4)
> I was mislead by the GitHub namespace, though I also wondered but could not
> find a LXQt-branded repository with qterminal.

Well, all the LXQt components are under https://github.com/lxde :)

(In reply to Otto Leipälä from comment #0)
> Qterminal should be updated to newer version,Mageia 5 have 0.4.0 from 2012
> original build new version to Mageia 3.
> Newer version fix tons of bugs from 0.4.0 it would make sense to update or
> backport it.

Which particular bug, and how can it be reproduced? We don't simply push version updates to stable releases just because there's a newer version ...
Comment 6 Otto Leipälä 2016-03-16 11:23:57 CET
(In reply to Florian Hubold from comment #5)
> (In reply to Rémi Verschelde from comment #4)
> > I was mislead by the GitHub namespace, though I also wondered but could not
> > find a LXQt-branded repository with qterminal.
> 
> Well, all the LXQt components are under https://github.com/lxde :)
> 
> (In reply to Otto Leipälä from comment #0)
> > Qterminal should be updated to newer version,Mageia 5 have 0.4.0 from 2012
> > original build new version to Mageia 3.
> > Newer version fix tons of bugs from 0.4.0 it would make sense to update or
> > backport it.
> 
> Which particular bug, and how can it be reproduced? We don't simply push
> version updates to stable releases just because there's a newer version ...


I know we don't update packages because there is new version need to be bugfix release or otherwise it have to go to backports,like i did said update or backport it.

Upstream bug fixes big bug is fixed it now remember size of terminal when you save settings old qt4 version don't remember size of terminal,even you edit manually settings file with editor.
Comment 7 Nicolas Lécureuil 2016-11-10 15:31:03 CET
i don't find qterminal 0.4.0 sources.

Where can i find them ?

CC: (none) => mageia

Comment 8 Otto Leipälä 2016-11-15 19:52:40 CET
No you won't and don't need to find.

It's 4 years old and very buggy version this was to backport qterminal 0.6.0 to Mageia 5 because it fixes lot bugs in 0.4.0,like you can't change it size it reset it always to default.

It's now same to me do somebody do it or not as i use Cauldron/Mageia 6 rc in my main laptop install.
Comment 9 Nicolas Lécureuil 2016-11-16 15:16:30 CET
ok for me, i update to 0.6.0 ( i couldn't invent, it is written 0.6.0 nowhere on the bugreport ;) ).
Comment 10 Marja Van Waes 2018-07-12 11:02:16 CEST
Closing as OLD, because this bug doesn't exist in Mga6 or later, the reporter already stopped using Mga5 long ago and Mga5 is no longer officially maintained, anyway.

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


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