fix nesting in projects tooling
Closed, ResolvedPublic

Description

when updating projects kde-telepathy cannot be cloned because for some reason the tooling attempts to clone git://anongit.neon.kde.org/kde-extras_kde-telepathy/kte-collaborative which is a bogus url as telepathy is a subdir

this causes continious slowdown of updates as it tries to clone over and over again

sitter created this task.Oct 25 2016, 9:52 AM
sitter moved this task from Ready To Do to Review on the Neon board.Feb 15 2017, 4:02 PM
sitter closed this task as Resolved.
sitter claimed this task.

I worked around this a while ago. Not worth tracking this any longer for neon

bshah added a subscriber: bshah.Feb 8 2018, 6:38 AM

Can we remove the bazzilions of warnings

06:30:47 shitpile -- stepped into a shit pile --> https://phabricator.kde.org/T4160
06:30:47 shitpile -- stepped into a shit pile --> https://phabricator.kde.org/T4160
06:30:47 shitpile -- stepped into a shit pile --> https://phabricator.kde.org/T4160
06:30:48 stepped into a shit pile --> https://phabricator.kde.org/T4160
06:30:48 stepped into a shit pile --> https://phabricator.kde.org/T4160
06:30:48 stepped into a shit pile --> https://phabricator.kde.org/T4160
06:32:17 Tree is up to date at revision 1352 of branch http://bazaar.launchpad.net/~kdeneon/livecd-rootfs-neon/trunk
06:32:17 rm -r /tmp/d20180208-7234-zx28dt
06:32:17 ln -s /var/lib/jenkins/workspace/mgmt_job-updater/cache/projects/lp:livecd-rootfs-neon /tmp/d20180208-7234-zx28dt
06:32:18 Tree is up to date at revision 6405 of branch http://bazaar.launchpad.net/~kdeneon/ubiquity-neon/trunk
06:32:18 rm -r /tmp/d20180208-7234-1yi20bi
06:32:18 ln -s /var/lib/jenkins/workspace/mgmt_job-updater/cache/projects/lp:ubiquity-neon /tmp/d20180208-7234-1yi20bi
06:36:35 shitpile -- stepped into a shit pile --> https://phabricator.kde.org/T4160
06:36:35 shitpile -- stepped into a shit pile --> https://phabricator.kde.org/T4160
06:36:35 shitpile -- stepped into a shit pile --> https://phabricator.kde.org/T4160
06:36:37 stepped into a shit pile --> https://phabricator.kde.org/T4160
06:36:37 stepped into a shit pile --> https://phabricator.kde.org/T4160
06:36:37 stepped into a shit pile --> https://phabricator.kde.org/T4160

If the issue is workarounded?

sitter added a comment.Feb 8 2018, 9:30 AM

We cannot. The way it is worked around is by skipping too deep directories so if this ever becomes a necessary use case it would not work and no one would remember why that is.