Bug 10833 - svk up broken and doesn't update local repository
Summary: svk up broken and doesn't update local repository
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-24 16:04 CEST by Bruno Cornec
Modified: 2015-03-31 16:05 CEST (History)
0 users

See Also:
Source RPM: svk-2.2.3-5.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Bruno Cornec 2013-07-24 16:04:10 CEST
Description of problem:

After upgrading from MGA2 to MGA3 svk up is broken and doesn't update local repository

Version-Release number of selected component (if applicable):

svk-2.2.3-5.mga3

How reproducible:


Steps to Reproduce:
1. mirror an svn repo
2. perform a svk pull (which works) to get latest update (even if it prints error messages)
3. perform a svk up which doesn't update the repo:
[bruno@localhost pb]$ svk sync //prj/pb
Use of qw(...) as parentheses is deprecated at /usr/lib/perl5/vendor_perl/5.16.2/SVK/Mirror.pm line 455.
Warning: Use of "require" without parentheses is ambiguous at (eval 60) line 2.
Syncing svn+ssh://svn.project-builder.org/prj/svn/pb
[bruno@localhost pb]$ svk pull 
Use of qw(...) as parentheses is deprecated at /usr/lib/perl5/vendor_perl/5.16.2/SVK/Mirror.pm line 455.
Warning: Use of "require" without parentheses is ambiguous at (eval 61) line 2.
Use of uninitialized value $ARGV[0] in ucfirst at /usr/lib/perl5/vendor_perl/5.16.2/App/CLI/Command.pm line 116.
Syncing svn+ssh://svn.project-builder.org/prj/svn/pb
Auto-merging (5374, 5374) /prj/pb to /local/pb (base /prj/pb:5374).
Empty merge.
Syncing //local/pb(/local/pb) in /home/bruno/local/pb to 5391.
g   projects/mondorescue/pbconf/branches/3.0/mondo-doc/pbcl
g   projects/mondorescue/pbconf/branches/3.0/mindi/pbcl
g   projects/mondorescue/pbconf/branches/3.0/mondo/deb/control
g   projects/mondorescue/pbconf/branches/3.0/mondo/pbcl
g   devel/pb-doc/LabProject-Builder.org.pdf
g   devel/pb-modules/etc/pb.conf
[bruno@localhost pb]$ svk up
Use of qw(...) as parentheses is deprecated at /usr/lib/perl5/vendor_perl/5.16.2/SVK/Mirror.pm line 455.
Warning: Use of "require" without parentheses is ambiguous at (eval 60) line 2.
Use of uninitialized value $ARGV[0] in ucfirst at /usr/lib/perl5/vendor_perl/5.16.2/App/CLI/Command.pm line 116.
Syncing //local/pb(/local/pb) in /home/bruno/local/pb to 5391.
g   projects/mondorescue/pbconf/branches/3.0/mondo/pbcl
g   projects/mondorescue/pbconf/branches/3.0/mondo/deb/control
g   projects/mondorescue/pbconf/branches/3.0/mondo-doc/pbcl
g   projects/mondorescue/pbconf/branches/3.0/mindi/pbcl
g   devel/pb-doc/LabProject-Builder.org.pdf
g   devel/pb-modules/etc/pb.conf

If you relaunch the same operations, the local SVK repo is exactly in the same state, and not usable.

Probably linked to the update of perl and the error messages printed may give ideas where issues are, but I have not been able to fix it despite some tries. 


Reproducible: 

Steps to Reproduce:
Comment 1 Bruno Cornec 2013-07-25 02:06:36 CEST
We could benefit from cross distribution work with Fedora at least (Debian and Ubuntu seem to have droped it). Cf: https://bugzilla.redhat.com/show_bug.cgi?id=977592

Having a SW which is not actively maintained shouldn't prevent a distribution to try to maintain it working for its own users, in the latest upstream state.

So If someone with knowledge of latest perl 5.16 diffs with what used to work with 5.14, that would porbably help shorten solvinf the issue. TIA.
Comment 2 Marja Van Waes 2015-03-31 16:05:01 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


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