Bug 3989

Summary: mgarepo doesn't work in RO mode (and URL is bogus in error message)
Product: Mageia Reporter: Thierry Vignaud <thierry.vignaud>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal CC: dmorganec
Version: 1   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: mgarepo CVE:
Status comment:

Description Thierry Vignaud 2012-01-01 14:04:26 CET
mgarepo doesn't work in RO mode, aka when not having/using an account, when following instructions in /etc/mgarepo.conf:

## uncomment it in case you don't have a account in the Mageia build system:
#mirror = http://svn.mageia.org/svn/packages/cauldron/

Example:

[fabienne@localhost ~]$ mgarepo co gutenprint
Permission denied (publickey,password,keyboard-interactive).
svn: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: La connexion réseau a été fermée de façon inattendue

It seems ssh-agent or ForwardAgent are not setup or your username is wrong. See http://www.mageia.org/wiki/doku.php?id=svn-faq for more information.



Also, URL is bogus in error message since we switched to the new wiki...
Manuel Hiebel 2012-01-01 15:42:21 CET

CC: (none) => dmorganec
Assignee: dmorganec => boklm

Comment 1 Nicolas Vigier 2012-01-01 17:01:27 CET
The mgarepo.conf from version of mgarepo currently in cauldron should have the correct URL :
## uncomment it in case you don't have a account in the Mageia build system:
#mirror = svn://svn.mageia.org/svn/packages/

For the wiki URLs, it's corrected in svn, and will be in cauldron when next mgarepo version is released.
Comment 2 Thierry Vignaud 2012-01-01 18:12:00 CET
Indeed that URLs work.
So it's only the mga1 version that needs to be updated.

Version: Cauldron => 1

Comment 3 Marja Van Waes 2012-07-06 15:04:46 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 4 Manuel Hiebel 2012-10-20 22:04:11 CEST
boklm leave Mageia

Assignee: boklm => bugsquad

Comment 5 Manuel Hiebel 2012-11-05 16:52:39 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 6 Manuel Hiebel 2012-12-02 14:32:08 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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.

--
Mageia Bugsquad

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