unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: Matt Armstrong <matt@rfc20.org>, 59064@debbugs.gnu.org
Subject: bug#59064: 29.0.50; build problem git worktree linked to main worktree (repo)
Date: Sun, 06 Nov 2022 15:59:08 +0100	[thread overview]
Message-ID: <87iljsruwz.fsf@no.workgroup> (raw)
In-Reply-To: <87y1so1fso.fsf@no.workgroup>

Hi Matt, emacs developers,
* Gregor Zattler <telegraph@gmx.net> [2022-11-06; 12:30 +01]:
> * Matt Armstrong <matt@rfc20.org> [2022-11-05; 17:04 -07]:
>> I think the next thing to do is to figure out if either:
>>
>> a) This can reproduce this on a Debian/testing or Debian/sid system.  Is
>> it easy for you to spin up a VM to do this?  If so, it would be useful
>> to know if this is related to the Debian version, as you are likely to
>> use steps similar to what you've already done.
>
> I used to use VirtualBox, but since this is not part of
> Debian stable, I will use this opportunity to learn how to
> use KVM.  This will take some time, I will report back.

I did so, the results for bookworm are the same:  build in
detached linked worktree linked to main worktree fails,
build in non-detached linked worktree linked to main
worktree succeeds.

Meanwhile on the bullseye server I tested the same with the
sources from emacs-28.2.  There was no failure building
theses in an detached linked worktree, linked to a main
worktree.

I will try to bisect.  But since I have no clue regarding
the build system I only hope that this will not hit other
build failures in between.  This will take days...



Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-





  reply	other threads:[~2022-11-06 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 23:11 bug#59064: 29.0.50; build problem git worktree linked to main worktree (repo) Gregor Zattler
2022-11-06  0:04 ` Matt Armstrong
2022-11-06 11:30 ` Gregor Zattler
2022-11-06 14:59   ` Gregor Zattler [this message]
2022-11-06 18:17     ` Matt Armstrong
2022-11-06 18:38       ` Philip Kaludercic
2022-11-06 19:05         ` Eli Zaretskii
2022-11-07  8:52           ` Philip Kaludercic
2022-11-07 17:24             ` Matt Armstrong
2022-11-06 21:35       ` Gregor Zattler
2022-11-07 17:19         ` Matt Armstrong

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iljsruwz.fsf@no.workgroup \
    --to=telegraph@gmx.net \
    --cc=59064@debbugs.gnu.org \
    --cc=matt@rfc20.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).