Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Johannes Schindelin
    @dscho
    Do I have a Cloud console?
    David Macek
    @elieux
    If you have a Google account, yes.
    It may require you to specify few things first.
    Johannes Schindelin
    @dscho
    Wow, I have no idea what I should do there.
    And why I am seeing that project "1234".
    And who this gyg3131 person is.
    David Macek
    @elieux
    So you do see it.
    Okay, at least I'm not alone.
    Maybe you can remove the group from there.
    Johannes Schindelin
    @dscho
    image.png
    Nope.
    David Macek
    @elieux
    Well, then. :D
    Johannes Schindelin
    @dscho
    @elieux FYI I finally managed to rebase Git for Windows' BusyBox-w32 patches to a newer version. There are quite a few hacks still, and I am pretty unsure that I want to keep the \\?\ business (read: I intend to drop it completely), but I managed to compile it here. I pushed up the result as wip-rebase-2021-02-19 to https://github.com/dscho/busybox-w32.
    David Macek
    @elieux
    Ooh. Nice. I should try it. I know of at least one bug in path handling with the current version.
    Johannes Schindelin
    @dscho
    Cool. Maybe you can also help with cleaning up the TO-SPLIT and the Ensure... patches?
    David Macek
    @elieux
    You got a response on that 0-bit relocation.
    Johannes Schindelin
    @dscho
    Yes, and it's a good one.
    David Macek
    @elieux
    Not sure if relevant, but there's a new busybox-w32 release from today.
    Johannes Schindelin
    @dscho
    It is relevant. There are fixes in there that I provided ;-)
    David Macek
    @elieux
    The update-patches.sh scripts in msys2-runtime...
    Nevermind. Now I understand, the first cd is not related to the git repository.
    David Macek
    @elieux
    2.31.0.rc1.windows.1-1 was pulled?
    Johannes Schindelin
    @dscho
    No, why?
    It was superseded by v2.30.2 (which is newer, and "more official").
    David Macek
    @elieux
    Because the supersession is not obvious from the version number.
    Pacman complained that it's a downgrade..
    Anyway, that's enough explanation. Thanks.
    Johannes Schindelin
    @dscho
    But v2.30.2 was superseded by v2.31.0-rc2 (as far as mingw-w64-git goes) in the meantime, anyway...

    Pacman complained that it's a downgrade..

    Oh right, I didn't think of that.

    It shouldn't have been a big deal, but I was a bit too tired to do v2.30.2 and v2.31.0-rc2 on the same day (besides, I needed to wait for a GCM Core update before I could release v2.31.0-rc2).
    Brent Arias
    @brentarias

    Hey all, I have done a git merge --no-commit --no-ff {my_branch}. I decided I don't want the result, so I typed git merge --abort. I get this error:

    error: Entry 'O365OutlookConnector.Test/O365OutlookGeneratorTest.cs' not uptodate. Cannot merge.
    fatal: Could not reset index file to revision 'HEAD'

    What can I do?

    Brent Arias
    @brentarias
    Never mind. I fixed it by unstaging all changes, then again trying git merge --abort.
    pjujeczko
    @pjujeczko
    Hello @elieux . I got problems after istalling git for windows in my MSYS2. I ended up without Pacman... I thought I was doing steps 1-5 of https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper right, but then I realised I was using wrong shell (Mingw64 instead of Msys). Msys2 was up to date before that, I use win10. Is it possible to restore Pacman without reinstalling the whole Msys2?
    David Macek
    @elieux
    I don't think the used shell would have a significant effect on the process.
    Did you get any errors during the process?
    pjujeczko
    @pjujeczko
    No, there were no errors. Step 5 - the console has closed and after that there was no pacman;)
    One more thing - in step 4 instead of "pacman -Syyuu" i wrote "pacman -Syu", but as I said the system was upgraded that same day
    David Macek
    @elieux
    How do you know you don't have Pacman anymore?
    @pjujeczko
    pjujeczko
    @pjujeczko
    there is no pacman in /usr/bin - command is deleted. What's more - I've installed pacman from the repo (msys2-keyring-1~20210213-1-any.pkg.tar.zst,
    pacman-5.2.2-13-x86_64.pkg.tar.zst,
    pacman-mirrors-20210227-1-any.pkg.tar.zst), but after extracting pacman, I can use it once before it gets self-deleted from /usr/bin with such errors:
    error: GPGME error: Invalid crypto engine
    error: GPGME error: Invalid crypto engine
    error: GPGME error: Invalid crypto engine
    error: GPGME error: Invalid crypto engine
    error: database 'mingw32' is not valid (invalid or corrupted database (PGP signature))
    error: database 'mingw64' is not valid (invalid or corrupted database (PGP signature))
    error: database 'msys' is not valid (invalid or corrupted database (PGP signature))
    error: database 'git-for-windows' is not valid (invalid or corrupted database (PGP signature))
    pjujeczko
    @pjujeczko
    @elieux
    David Macek
    @elieux
    I don't think Pacman will delete itself unless you tell it to.
    This is something else deleting it.
    Check BLODA.
    pjujeczko
    @pjujeczko
    Ok, thanks
    pjujeczko
    @pjujeczko
    You're right, I had to add exception for my Msys2 location in my anti-virus soft (Avast, free). It was the cause of pacman disappearance. However after untaring the pacman (in root directory by $ tar -x -I zstd -vf ~/pacman/pacman-5.2.2-13-x86_64.pkg.tar.zst) I get same errors. I tried to install libgpgme and mingw-w64-gpgme packages that same way, but it makes no difference.
    @elieux