Bug 13228 - QupZilla 1.6.3
Summary: QupZilla 1.6.3
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Backports (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Backport
Depends on:
Blocks:
 
Reported: 2014-04-17 14:19 CEST by Stefan Horn
Modified: 2015-09-21 12:08 CEST (History)
0 users

See Also:
Source RPM: QupZilla 1.4.4-2.mga4
CVE:
Status comment:


Attachments

Description Stefan Horn 2014-04-17 14:19:01 CEST
The current version of QupZilla is 1.6.3 (14. Feb. 2014).
For Mageia 4 only 1.4.4-2 is available
It is possible to include the the current version into repository?
Regards, Stefan

Reproducible: 

Steps to Reproduce:
Comment 1 Jani Välimaa 2014-04-18 11:09:28 CEST
Our updates policy [1] states:
"Updates are not the appropriate place for packages created to satisfy certain user's urges for "the latest". These types of builds belong in backports."

So, the answer is 'no' for an update and 'maybe' for backporting latest version.

[1] https://wiki.mageia.org/en/Updates_policy#Version_Policy

Keywords: (none) => Backport

Comment 2 Manuel Hiebel 2014-04-21 18:12:45 CEST
and its not a "new package request"

Component: New RPM package request => Backports

Comment 3 Samuel Verschelde 2015-09-21 12:08:17 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further updates. As a 
result we are closing this bug report. 

If you would like to help with updates and backports in the future, don't 
hesitate to join the packager team via our mentoring program [1], our QA 
Team (who tests the updates and backport candidates and always welcomes 
help) [2] or join the teams that fit you most [3].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] https://wiki.mageia.org/en/QA_Team
[3] http://www.mageia.org/contribute/

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


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