Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Vladyslav Ivasyuk <vlady.ivasyuk@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Re: [Windows] Unable to build latest wireguard missing i686-w64-mingw32-windres
Date: Mon, 1 Feb 2021 16:08:43 +0200	[thread overview]
Message-ID: <CAJ0ZNNmwpRVdygsgUnTqJCZR436RhcCWvw2bgUG3KpM5s0=otg@mail.gmail.com> (raw)

Hi,

the problem with "unknown revision" is happening because git history
was rewritten. There are two projects which are kept in branches of
the Windows WireGuard client project. Those are "github.com/lxn/walk"
and "github.com/lxn/win" and branches for them are "pkg/walk" and
"plg/walk-win" respectively. Both branches have a number of
customization commits which are kept at the top of the git history.
Hence sync with lxn's code is done with rebasing and then force
pushing. So after the sync, old commit id is lost and replaced with a
new one. Each time those branches are updated, you can also see the
"mod: bump" commit in the main branch. All commits before that will
not work anymore. Therefore old tags are not reliable too.

Probably, it can be fixed by keeping separate branch for at least
every tag, so build on tags does not break. Though, it would be better
to create a new branch on every update/sync. Another options to
consider are maintaining the lxn in a separate repository or keep
changes as a set of patches.

Best,
Vladyslav

             reply	other threads:[~2021-02-04  0:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 14:08 Vladyslav Ivasyuk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-28 23:24 Manikandan Thiagarajan

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='CAJ0ZNNmwpRVdygsgUnTqJCZR436RhcCWvw2bgUG3KpM5s0=otg@mail.gmail.com' \
    --to=vlady.ivasyuk@gmail.com \
    --cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).