| Summary: | dev-vcs/git-2.16.4: segfault on submodule command | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Raymond Jennings <shentino> |
| Component: | Current packages | Assignee: | Robin Johnson <robbat2> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jstein, polynomial-c |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 667942 | ||
| Bug Blocks: | |||
| Attachments: |
gdb backtrace
emerge --info emerge --info |
||
|
Description
Raymond Jennings
2018-09-29 07:07:47 UTC
Created attachment 548148 [details]
gdb backtrace
Created attachment 548150 [details]
emerge --info
Created attachment 548152 [details]
emerge --info
It is sad to read that you have problems with the software. It works for me. The situation seems to be a bit more complicate and requires some analysis. We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3]. I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4]. Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://forums.gentoo.org/ [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html [4] https://www.gentoo.org/support/ I reported it upstream, their devs are working with me on getting a reproducible test case. Here is no bugfix IN_PROGRESS. Reverting back to worksforme. Link to the mailinglist: https://public-inbox.org/git/CAGDaZ_oBpLxD0cutrsNsFBEtH+-Fn2eT40gDsnGZhhU0qm2Ofw@mail.gmail.com/ Please provide a reproducible example. Upstream requested the same. Do not reopen unless you have additional information. Upstream has already fixed this in version 2.18 [14:47:42] <veremitz> I'd wait until the stabilisation has run its course, before closing the original bug .. [14:47:57] <veremitz> but you could push for the stabilisation because of the presence of said bug .. So I'll open a stabilization request for this As far I can see, upstream did not write about a "bug". They just suggested to use a more recent version and it worked for you. This can be anything. Git could be more robust towards broken repositories There could be a bug in the old Git 2.16 It could be a broken compilation However it is good to know that it is not reproducible in 2.18 for you. Not yet but one of their follow up comments did: https://public-inbox.org/git/CAGZ79kYX3ZgmE3S-2cq0F_27Ctq_wwuSo53znRrBquik3ODXew@mail.gmail.com/ (In reply to Raymond Jennings from comment #10) > Not yet but one of their follow up comments did: > > https://public-inbox.org/git/CAGZ79kYX3ZgmE3S- > 2cq0F_27Ctq_wwuSo53znRrBquik3ODXew@mail.gmail.com/ I mean not yet by the time you checked. |
