Bug 16364

Summary:	VDR 2.4.0 (new stable release)
Product:	Mageia	Reporter:	Herbert Poetzl <herbert>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	Normal	CC:	anssi.hannula, herbert, mageia, marja11, ngompa13
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	vdr-2.0.7-1.mga5.src.rpm	CVE:
Status comment:

Description Herbert Poetzl 2015-07-13 07:16:54 CEST

Description of problem:
It would be nice to update vdr to 2.2 in mageia 5 (or at least in cauldron/backports) as 2.2 adds a number of improvements and fixes.

http://www.tvdr.de/changelog.htm

Version-Release number of selected component (if applicable):
vdr-2.0.7-1.mga5

Thanks in advance,
Herbert

Reproducible: 

Steps to Reproduce:

Comment 1 Samuel Verschelde 2016-11-01 13:47:21 CET

Assigning to all packagers collectively since the maintainer Anssi is currently inactive.

Component: RPM Packages => Backports
Assignee: bugsquad => pkg-bugs

Samuel Verschelde 2016-11-01 13:47:32 CET

CC: (none) => anssi.hannula

Comment 2 Marja Van Waes 2018-05-03 08:23:19 CEST

(A backport request for stable can be made after new vdr lands in cauldron)

http://www.tvdr.de/changelog.htm

Version: 5 => Cauldron
Component: Backports => RPM Packages
CC: (none) => marja11
Summary: VDR 2.2 was released in February (new stable release) => VDR 2.4.0 (new stable release)

Comment 3 Marja Van Waes 2018-05-03 08:24:31 CEST

@ Herbert

You're a Mageia packager, you might want to package this for Mageia yourself :-)

Cheers,
Marja

Comment 4 Herbert Poetzl 2018-05-03 13:29:42 CEST

I'm packaging all the 'missing parts' in Mageia myself, but I don't want to waste my time on creating official packages and having endless discussions why it can't be included (tried that several times, didn't really work out for me).

Best,
Herbert

CC: (none) => herbert

Comment 5 Marja Van Waes 2018-05-03 22:23:39 CEST

(In reply to Marja Van Waes from comment #3)
> @ Herbert
> 
> You're a Mageia packager, you might want to package this for Mageia yourself
> :-)
> 


(In reply to Herbert Poetzl from comment #4)
> I'm packaging all the 'missing parts' in Mageia myself, but I don't want to
> waste my time on creating official packages and having endless discussions
> why it can't be included (tried that several times, didn't really work out
> for me).
> 
> Best,
> Herbert

Hi Herbert,

Sorry, but your reply confuses me, I missed the endless discussions and don't manage to think of something that could block upgrading VDR in cauldron and backporting it for stable.

AFAIK:

Upgrading a package in cauldron is always allowed, unless there's a version freeze (which isn't the case, now).

After that, it is always allowed to push it to backports_testing for a stable Mageia release. If it's a pure bugfix upgrade (no new features), then it can become a normal update, and pushing to updates_testing is allowed.

https://wiki.mageia.org/en/Updates_policy#Version_Policy

Normally, when there's a registered maintainer, you'd need to tell him that you'd like to do upgrade the package, but in this case (where the report was assigned to all packagers, because the maintainer is too busy) just assigning the report to yourself would be enough.

CC'ing the packaging team leaders so that they can correct me in case I said something wrong.

Cheers,

Marja

CC: (none) => mageia, ngompa13