It will be migrated when we do the bulk migration.
Until then, if you want to do the less work possible, I think that what
Michael has said is fine:
- Create new repositories on salsa
- Don't migrate anything, unless you update the rewritemap, setup the
right branch permissions and hooks
Done.
On Tue, Feb 20, 2018 at 8:30 AM, Arnaud
wrote:
>
>
>
>>
>> For the repository we're talking about right now, I understand there's no
>> need to bump the version right now, as long as I'm not sure it's needed.
>>
>> Should I just delete it, or at least take
>
>
>
> For the repository we're talking about right now, I understand
> there's no need to bump the version right now, as long as I'm not
> sure it's needed.
>
> Should I just delete it, or at least take it out of the go
> packages group, and keep it as a personal repo ?
>
On Tue, Feb 20, 2018 at 8:09 AM, Arnaud
wrote:
>
>
> On 02/20/2018 12:08 AM, Michael Stapelberg wrote:
>
> Are you certain that this commit is actually a requirement, or just
> happens to be the latest version the containerd people tried?
>
>
> It's just the
On 02/20/2018 12:08 AM, Michael Stapelberg wrote:
> Are you certain that this commit is actually a requirement, or just
> happens to be the latest version the containerd people tried?
It's just the version that is vendored by containerd. I assumed they
used it for a good reason, that's all.
Dear Debian Go Packaging Team,
The latest version of containerd requires a recent snapshot of
github.com/urfave/cli. This can be seen with a command such as:
wget --quiet \
https://raw.githubusercontent.com/containerd/containerd/master/vendor.conf \
-O - | \
grep urfave
At the