Bug 30888 – Move duplicity to maintained

Bug 30888 - Move duplicity to maintained


Summary:	Move duplicity to maintained

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	UCS 3.2
Assigned To:	Felix Botner
QA Contact:	Moritz Muehlenhoff

URL:
Keywords:	interim-1

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-03-24 22:05 CET by Stefan Gohmann
Modified:	2013-11-19 06:43 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Stefan Gohmann

2013-03-24 22:05:36 CET

The package duplicity should be moved to maintained.

Comment 1 Moritz Muehlenhoff

2013-05-31 10:45:39 CEST

We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.

As such, this bug is moved to the new target milestone.

Comment 2 Felix Botner

2013-06-18 14:07:13 CEST

cherry picked duplicity and librsync from 3.0-0 to 3.2, added duplicity to trigger list

Comment 3 Moritz Muehlenhoff

2013-07-30 12:14:53 CEST

jmm@omar:/mnt/omar/vmwares/mirror/testing/3.2$ find . -name duplicity*deb                         
./maintained/3.2-0/amd64/duplicity_0.6.08b/1.15.201306181351_amd64.deb                            
./maintained/3.2-0/i386/duplicity_0.6.08b-1.15.201306181351_i386.deb    

Changelog entry exists.

Comment 4 Stefan Gohmann

2013-11-19 06:43:38 CET

UCS 3.2 has been released:
 http://docs.univention.de/release-notes-3.2-en.html
 http://docs.univention.de/release-notes-3.2-de.html

If this error occurs again, please use "Clone This Bug".