Transition to new mirror infrastructure
bcooksley at kde.org
Tue Nov 3 21:44:00 GMT 2020
On Wed, Nov 4, 2020 at 10:34 AM Rex Dieter <rdieter at gmail.com> wrote:
> I'm stumped here why this isn't working as before on milonia, to
> transfer a whole bunch of files at a time with wildcards.
> While individual transfers are fine:
> rsync deino.kde.org:stable/release-service/20.08.3/src/yakuake-20.08.3.tar.xz
> . -v
> Wildcards no longer work:
> rsync deino.kde.org:stable/release-service/20.08.3/src/*.xz .
> rsync: link_stat
> "/srv/archives/ftp/stable/release-service/20.08.3/src/*.xz" failed: No such
> file or directory (2)
> rsync error: some files/attrs were not transferred (see previous errors)
> (code 23) at main.c(1816) [Receiver=3.2.3]
> rsync: [Receiver] write error: Broken pipe (32)
As noted in my email to distributions@ yesterday, wildcards in this form
are not functionality natively supported by RSync.
This worked because bash was interpreting the regexes/wildcards for you.
The correct behaviour here would be to use the --include or --exclude
switches to rsync to obtain the desired behaviour.
> Any ideas?
> On Sat, Oct 31, 2020 at 1:01 PM Ben Cooksley <bcooksley at kde.org> wrote:
>> On Sun, Nov 1, 2020 at 4:49 AM Christoph Feck <cfeck at kde.org> wrote:
>>> On 10/31/20 03:08, Ben Cooksley wrote:
>>> > This transition has now been completed, and going forward all access
>>> > now be directed to deino.kde.org.
>>> Did I understand it correctly, that "deino" is the replacement for
>>> "milona", but shouldn't offer ssh/scp access anymore, but need to use
>> Deino is the replacement to Milonia yes.
>> The restriction on access only applies to packagers and those with
>> accounts for managing data on
>> files.kde.org/cdn.kde.org/distribute.kde.org and doesn't apply to
>>> For what it's worth, I could successfully ssh login to
>>> ftpadmin at deino.kde.org (using the credentials I used previously on
>>> milona), and could use mkdir/chmod in stable/release-service path,
>>> albeit response time was very laggy.
>> I've investigated that issue with response times and found that the
>> network adapter was extremely unhappy and regularly resetting itself.
>> Following a system reboot it appears to have been corrected, however
>> we'll monitor the system to confirm this is the case.
>>> If that's not the correct replacement procedure, please clarify.
>> Many thanks,
>>> Christoph Feck
>>> KDE Release Team
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the release-team