Mageia's current approach of a vpnc client can only connect to cisco concentrators, but not to Fritzbox routers built-in vpnc server as well. In the past there was an attempt to solve the issue, but there were more than one change per subversion commit necessary, and so it was cancelled. Working strategy according to mageia's policy, based on patch from openSuse: - get 'https://ftp.gwdg.de/pub/opensuse/source/distribution/leap/15.6/repo/oss/src/vpnc-0.5.3r550-bp156.4.6.src.rpm' - extract patch 'vpnc-restart-after-timeout.diff' - in mageia's source 'vpnc-0.5.3-17.mga9.src.rpm': - replace (useless) patch 'vpnc-0.5.3-linkage.patch' with patch from openSuse 'vpnc-restart-after-timeout.diff' - adapt spec file and leave everything else as is - recompile / repackage Feel free to contact me for feature / verification / stress testing
. *** This bug has been marked as a duplicate of bug 25245 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
No - this describes how to solve the issue. Don't close tickets you have no clue about.
Resolution: DUPLICATE => (none)Status: RESOLVED => REOPENEDPriority: Normal => High
The last remark was not sympathetic. However, having looked at the old bug, that was too long & complicated to continue. Yes, you give a sophisticated solution, and thank you for that. Assigning globally. Your offer to test the result is important, and the packager|QA should heed it.
Assignee: bugsquad => pkg-bugs
Hi Lewis, in the binary, as well as the source rpm I see something like "umeabot" as packager - does this mean the package is orphaned without maintainer? For better understanding: Some time ago, I created a fully working version (cisco and avm) because I need this for myself, and then I had put it on my server to provide it for others also. I opened this ticket because my server's logfiles show that people are downloading this package over and over from my site -- nice, yes! -- but it would be much better to have a fully functional version in the official mga repo. Then I can remove my version from my server without side effects. How to proceed?
(In reply to Markus Robert Keßler from comment #4) > Hi Lewis, > > in the binary, as well as the source rpm I see something like "umeabot" as > packager - does this mean the package is orphaned Yes. This was already explained 4 years ago in one of you other duplicate reports.
Hi, somehow offtopic, but, just tested on one of my mga9 instances and found around 700 packages with "Packager:umeabot" (out of around 3300 packages installed). Just curious - what happens when a package made by "umeabot" needs a security update? Is this request then assigned to all packagers, in the hope that someone will pick it up and updates it? Thanks!