From: "René Jochum" <rene@jochum.dev>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] Actual ubuntu Kernel and ZFSOnLinux on git.proxmox.com
Date: Sat, 19 Sep 2020 01:48:31 +0200 [thread overview]
Message-ID: <37c39b98-2bee-f989-3683-6633d5c60e50@jochum.dev> (raw)
In-Reply-To: <1600413207.cykqkbuev3.astroid@nora.none>
Thank you Fabian, it works now without `git fetch --tags`.
Documented this in the Forum:
https://forum.proxmox.com/threads/a.76137/
<https://forum.proxmox.com/threads/building-the-pve-kernel-on-proxmox-ve-6-x.76137/>
Kind regards,
René
On 18.09.20 09:21, Fabian Grünbichler wrote:
> On September 18, 2020 12:31 am, René Jochum wrote:
>> Hi,
>>
>> how have you guys been? I have a nice time back here in Vorarlberg :)
> busy developing PBS, as you can probably tell ;)
>
>> Can you please update the focal kernel and zfsonlinux on git.proxmox.com
>> pve-kernel doesn't seem to download its required submodules.
> if you enter the submodule and run `git fetch --tags` it should work.
>
> the problem here is that git submodules, once initialized/checked out,
> only pull. we sometimes need to push tags that are not (yet) part of the
> checked out branch in our mirrors (e.g., Ubuntu likes to tag in their
> force-pushed branch, and only merge once it passes QA, and sometimes it
> happens that a new release got cut in the meantime and that version only
> exists as a tag, but is never on the fast-forward master branch).
>
> another alternative is to de-init the submodule altogether, or clone the
> whole repo from scratch (the latter works, so it's not the commits which
> are missing, but just git submodule strangeness preventing them from
> being found).
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2020-09-18 23:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 22:31 René Jochum
2020-09-18 7:21 ` Fabian Grünbichler
2020-09-18 23:48 ` René Jochum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37c39b98-2bee-f989-3683-6633d5c60e50@jochum.dev \
--to=rene@jochum.dev \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox