Bug 4874

Summary: mgarepo should automatically run "svn upgrade"
Product: Mageia Reporter: Olav Vitters <olav>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: enhancement    
Priority: Normal CC: marja11, sysadmin-bugs
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: mgarepo CVE:
Status comment:

Description Olav Vitters 2012-03-11 13:40:13 CET
I have a bot which runs mgarepo amongst other things. It executes "mgarepo co $package" (even on existing directories), though could also run "mgarepo up $package".

It failed when I was away on:

> svn: E155036: Please see the 'svn upgrade' command
> svn: E155036: Working copy '/home/src/pkgs/PACKAGE' is too old (format 10, created by Subversion 1.6)

Apparently, since svn 1.7 you have to upgrade manually instead of svn handling this for you :-(

Please either do so in "mgarepo", or change svn to automatically upgrade the repository version.
Manuel Hiebel 2012-03-11 15:36:19 CET

Component: BuildSystem => RPM Packages
Version: unspecified => Cauldron
Assignee: sysadmin-bugs => boklm
Product: Infrastructure => Mageia
Source RPM: (none) => mgarepo

Comment 1 Marja Van Waes 2012-05-26 13:08:38 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 2 Marja Van Waes 2012-07-15 06:14:02 CEST
@ Nicolas

If you agree with this request and are one day going to work on it: please put "OK" on the whiteboard or set status to ASSIGNED.

If you don't agree with the assignment (AFAICS it is nobody's package), please assign back to bugsquad

If you think it should be closed (wontfix, fixed), please close

Keywords: NEEDINFO => (none)
CC: (none) => marja11

Comment 3 Manuel Hiebel 2012-10-20 22:04:06 CEST
boklm leave Mageia

Assignee: boklm => bugsquad

Comment 4 Marja Van Waes 2015-04-14 20:19:25 CEST
No action since over 2 yrs ago and still assigned to Bug Squad

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

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