#libgit2 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #libgit2, aggregated by home.social.
-
Git в браузере. Расширяем возможности с помощью LFS
Привет, Хабр! Я Паша, разработчик
https://habr.com/ru/companies/gram_ax/articles/994384/
#git #libgit2 #lfs #webassembly #rust #ffi #emscripten #docsascode #opensource #localfirst
-
Git в браузере. Расширяем возможности с помощью LFS
Привет, Хабр! Я Паша, разработчик
https://habr.com/ru/companies/gram_ax/articles/994384/
#git #libgit2 #lfs #webassembly #rust #ffi #emscripten #docsascode #opensource #localfirst
-
Git в браузере. Расширяем возможности с помощью LFS
Привет, Хабр! Я Паша, разработчик
https://habr.com/ru/companies/gram_ax/articles/994384/
#git #libgit2 #lfs #webassembly #rust #ffi #emscripten #docsascode #opensource #localfirst
-
Git в браузере. Расширяем возможности с помощью LFS
Привет, Хабр! Я Паша, разработчик
https://habr.com/ru/companies/gram_ax/articles/994384/
#git #libgit2 #lfs #webassembly #rust #ffi #emscripten #docsascode #opensource #localfirst
-
Как мы засунули Git в браузер (и чего нам это стоило)
Привет, Хабр! Меня зовут Паша, я разработчик
https://habr.com/ru/companies/gram_ax/articles/928144/
#emscripten #rust #webassembly #libgit2 #wasm #git #wysiwyg #open_source #localfirst
-
Как мы засунули Git в браузер (и чего нам это стоило)
Привет, Хабр! Меня зовут Паша, я разработчик
https://habr.com/ru/companies/gram_ax/articles/928144/
#emscripten #rust #webassembly #libgit2 #wasm #git #wysiwyg #open_source #localfirst
-
Как мы засунули Git в браузер (и чего нам это стоило)
Привет, Хабр! Меня зовут Паша, я разработчик
https://habr.com/ru/companies/gram_ax/articles/928144/
#emscripten #rust #webassembly #libgit2 #wasm #git #wysiwyg #open_source #localfirst
-
Как мы засунули Git в браузер (и чего нам это стоило)
Привет, Хабр! Меня зовут Паша, я разработчик
https://habr.com/ru/companies/gram_ax/articles/928144/
#emscripten #rust #webassembly #libgit2 #wasm #git #wysiwyg #open_source #localfirst
-
I wrote a post on my recent rabbit holes delving, alternatively titled "A Journey to the Centre of the Earth".
https://kaka.farm/posts/2025/02/27/work-on-guile-git-and-therefore-gnu-guix-sha256-hash-function-support.html
#c
#cc
#clang
#guile
#guix
#irc
#libgit2
#programming -
Some stuff that may or may not be useful to me later on:
https://developer.ibm.com/tutorials/l-dynamic-libraries/
https://libgit2.org/docs/reference/main/oid/index.html
(@ (git repository) repository-open <directory>) -
Sytuacja: są trzy konkurujące ze sobą łatki na dodanie wsparcia #libgit2 1.8 do libgit2-glib. I każda z nich jest trochę inna, niektóre z jasną sugestią, że autor nie miał pojęcia, co robi.
Serio, czy pokolenie GitHuba naprawdę nie potrafi poszukać, zanim wyśle własną łatkę?
A tak przy okazji, wygląda na to, że ten projekt umarł.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Situation: there are 3 competing merge requests to add #libgit2 1.8 support to libgit2-glib. And all of them are slightly different, some with clear indication that the author had no clue what they were doing.
Seriously, can't #GitHub generation actually search before sending something?
Also, the project seems entirely dead.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
I was planning on using #libgit2 for my next project, and I wanted a bit of crash course on #git #internals, and came across this absolutely fantastic series of tutorials on #YouTube by Omer Rosenbaum. If you want to dig into git in more detail, these are a great place to start. https://youtu.be/fWMKue-WBok?si=yygfpQ-il-G4EeCN
-
#SwiftGit2 is the #Swift language binding that the #libgit2 project references. For reasons, I wanted SwiftGit2 to be available as a Swift package. I discovered that @mathijsb had made libgit2 itself available as a Swift package and then used that to simplify and clean up SwiftGit2 as a Swift package. This makes consuming SwiftGit2 with up-to-date libgit2 dependencies much easier! Links:
#SPM support for SwiftGit2: https://github.com/mbernson/SwiftGit2
#SPM support for libgit2: https://github.com/mbernson/libgit2
-
It's been a while since I've complained about #RustLang itself, so…
Cargo insists on interacting with #git repositories. At the same time, cargo insists on vendoring an old version of #LibGit2 (1.6.2 FWICS). So, if your system is using a new git version (2.44.0), you won't be able to `cargo build`:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```You have to clone everything with `-c index.skipHash=false` to work around this.
But yeah, I'm sure there's a great benefit to using an outdated vendored C library that NIHs git.
-
Już dłuższą chwilę nie narzekałem na Rusta samego w sobie, więc…
Cargo upiera się na interakcji z repozytoriami #git. Jednocześnie, Cargo upiera się przy używaniu włączonej (zamiast systemowej), starej wersji #LibGit2 (z tego, co widzę: 1.6.2). Tak więc, jeżeli wasz system używa nowego gita (2.44.0), to `cargo build` nie przejdzie:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```Można to obejść, klonując wszystko z `-c index.skipHash=false`.
Ale spoko, na pewno jest wielka zaleta z użycia przestarzałej, włączonej na sztywno biblioteki w C, która wynajduje gita na nowo.
-
Sytuacja: są trzy konkurujące ze sobą łatki na dodanie wsparcia #libgit2 1.8 do libgit2-glib. I każda z nich jest trochę inna, niektóre z jasną sugestią, że autor nie miał pojęcia, co robi.
Serio, czy pokolenie GitHuba naprawdę nie potrafi poszukać, zanim wyśle własną łatkę?
A tak przy okazji, wygląda na to, że ten projekt umarł.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Sytuacja: są trzy konkurujące ze sobą łatki na dodanie wsparcia #libgit2 1.8 do libgit2-glib. I każda z nich jest trochę inna, niektóre z jasną sugestią, że autor nie miał pojęcia, co robi.
Serio, czy pokolenie GitHuba naprawdę nie potrafi poszukać, zanim wyśle własną łatkę?
A tak przy okazji, wygląda na to, że ten projekt umarł.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Sytuacja: są trzy konkurujące ze sobą łatki na dodanie wsparcia #libgit2 1.8 do libgit2-glib. I każda z nich jest trochę inna, niektóre z jasną sugestią, że autor nie miał pojęcia, co robi.
Serio, czy pokolenie GitHuba naprawdę nie potrafi poszukać, zanim wyśle własną łatkę?
A tak przy okazji, wygląda na to, że ten projekt umarł.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Sytuacja: są trzy konkurujące ze sobą łatki na dodanie wsparcia #libgit2 1.8 do libgit2-glib. I każda z nich jest trochę inna, niektóre z jasną sugestią, że autor nie miał pojęcia, co robi.
Serio, czy pokolenie GitHuba naprawdę nie potrafi poszukać, zanim wyśle własną łatkę?
A tak przy okazji, wygląda na to, że ten projekt umarł.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Situation: there are 3 competing merge requests to add #libgit2 1.8 support to libgit2-glib. And all of them are slightly different, some with clear indication that the author had no clue what they were doing.
Seriously, can't #GitHub generation actually search before sending something?
Also, the project seems entirely dead.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Situation: there are 3 competing merge requests to add #libgit2 1.8 support to libgit2-glib. And all of them are slightly different, some with clear indication that the author had no clue what they were doing.
Seriously, can't #GitHub generation actually search before sending something?
Also, the project seems entirely dead.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Situation: there are 3 competing merge requests to add #libgit2 1.8 support to libgit2-glib. And all of them are slightly different, some with clear indication that the author had no clue what they were doing.
Seriously, can't #GitHub generation actually search before sending something?
Also, the project seems entirely dead.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
Situation: there are 3 competing merge requests to add #libgit2 1.8 support to libgit2-glib. And all of them are slightly different, some with clear indication that the author had no clue what they were doing.
Seriously, can't #GitHub generation actually search before sending something?
Also, the project seems entirely dead.
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/40
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/43
https://gitlab.gnome.org/GNOME/libgit2-glib/-/merge_requests/44 -
I was planning on using #libgit2 for my next project, and I wanted a bit of crash course on #git #internals, and came across this absolutely fantastic series of tutorials on #YouTube by Omer Rosenbaum. If you want to dig into git in more detail, these are a great place to start. https://youtu.be/fWMKue-WBok?si=yygfpQ-il-G4EeCN
-
I was planning on using #libgit2 for my next project, and I wanted a bit of crash course on #git #internals, and came across this absolutely fantastic series of tutorials on #YouTube by Omer Rosenbaum. If you want to dig into git in more detail, these are a great place to start. https://youtu.be/fWMKue-WBok?si=yygfpQ-il-G4EeCN
-
#SwiftGit2 is the #Swift language binding that the #libgit2 project references. For reasons, I wanted SwiftGit2 to be available as a Swift package. I discovered that @mathijsb had made libgit2 itself available as a Swift package and then used that to simplify and clean up SwiftGit2 as a Swift package. This makes consuming SwiftGit2 with up-to-date libgit2 dependencies much easier! Links:
#SPM support for SwiftGit2: https://github.com/mbernson/SwiftGit2
#SPM support for libgit2: https://github.com/mbernson/libgit2
-
#SwiftGit2 is the #Swift language binding that the #libgit2 project references. For reasons, I wanted SwiftGit2 to be available as a Swift package. I discovered that @mathijsb had made libgit2 itself available as a Swift package and then used that to simplify and clean up SwiftGit2 as a Swift package. This makes consuming SwiftGit2 with up-to-date libgit2 dependencies much easier! Links:
#SPM support for SwiftGit2: https://github.com/mbernson/SwiftGit2
#SPM support for libgit2: https://github.com/mbernson/libgit2
-
#SwiftGit2 is the #Swift language binding that the #libgit2 project references. For reasons, I wanted SwiftGit2 to be available as a Swift package. I discovered that @mathijsb had made libgit2 itself available as a Swift package and then used that to simplify and clean up SwiftGit2 as a Swift package. This makes consuming SwiftGit2 with up-to-date libgit2 dependencies much easier! Links:
#SPM support for SwiftGit2: https://github.com/mbernson/SwiftGit2
#SPM support for libgit2: https://github.com/mbernson/libgit2
-
#SwiftGit2 is the #Swift language binding that the #libgit2 project references. For reasons, I wanted SwiftGit2 to be available as a Swift package. I discovered that @mathijsb had made libgit2 itself available as a Swift package and then used that to simplify and clean up SwiftGit2 as a Swift package. This makes consuming SwiftGit2 with up-to-date libgit2 dependencies much easier! Links:
#SPM support for SwiftGit2: https://github.com/mbernson/SwiftGit2
#SPM support for libgit2: https://github.com/mbernson/libgit2
-
It's been a while since I've complained about #RustLang itself, so…
Cargo insists on interacting with #git repositories. At the same time, cargo insists on vendoring an old version of #LibGit2 (1.6.2 FWICS). So, if your system is using a new git version (2.44.0), you won't be able to `cargo build`:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```You have to clone everything with `-c index.skipHash=false` to work around this.
But yeah, I'm sure there's a great benefit to using an outdated vendored C library that NIHs git.
-
It's been a while since I've complained about #RustLang itself, so…
Cargo insists on interacting with #git repositories. At the same time, cargo insists on vendoring an old version of #LibGit2 (1.6.2 FWICS). So, if your system is using a new git version (2.44.0), you won't be able to `cargo build`:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```You have to clone everything with `-c index.skipHash=false` to work around this.
But yeah, I'm sure there's a great benefit to using an outdated vendored C library that NIHs git.
-
It's been a while since I've complained about #RustLang itself, so…
Cargo insists on interacting with #git repositories. At the same time, cargo insists on vendoring an old version of #LibGit2 (1.6.2 FWICS). So, if your system is using a new git version (2.44.0), you won't be able to `cargo build`:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```You have to clone everything with `-c index.skipHash=false` to work around this.
But yeah, I'm sure there's a great benefit to using an outdated vendored C library that NIHs git.
-
It's been a while since I've complained about #RustLang itself, so…
Cargo insists on interacting with #git repositories. At the same time, cargo insists on vendoring an old version of #LibGit2 (1.6.2 FWICS). So, if your system is using a new git version (2.44.0), you won't be able to `cargo build`:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```You have to clone everything with `-c index.skipHash=false` to work around this.
But yeah, I'm sure there's a great benefit to using an outdated vendored C library that NIHs git.
-
Już dłuższą chwilę nie narzekałem na Rusta samego w sobie, więc…
Cargo upiera się na interakcji z repozytoriami #git. Jednocześnie, Cargo upiera się przy używaniu włączonej (zamiast systemowej), starej wersji #LibGit2 (z tego, co widzę: 1.6.2). Tak więc, jeżeli wasz system używa nowego gita (2.44.0), to `cargo build` nie przejdzie:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```Można to obejść, klonując wszystko z `-c index.skipHash=false`.
Ale spoko, na pewno jest wielka zaleta z użycia przestarzałej, włączonej na sztywno biblioteki w C, która wynajduje gita na nowo.
-
Już dłuższą chwilę nie narzekałem na Rusta samego w sobie, więc…
Cargo upiera się na interakcji z repozytoriami #git. Jednocześnie, Cargo upiera się przy używaniu włączonej (zamiast systemowej), starej wersji #LibGit2 (z tego, co widzę: 1.6.2). Tak więc, jeżeli wasz system używa nowego gita (2.44.0), to `cargo build` nie przejdzie:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```Można to obejść, klonując wszystko z `-c index.skipHash=false`.
Ale spoko, na pewno jest wielka zaleta z użycia przestarzałej, włączonej na sztywno biblioteki w C, która wynajduje gita na nowo.
-
Już dłuższą chwilę nie narzekałem na Rusta samego w sobie, więc…
Cargo upiera się na interakcji z repozytoriami #git. Jednocześnie, Cargo upiera się przy używaniu włączonej (zamiast systemowej), starej wersji #LibGit2 (z tego, co widzę: 1.6.2). Tak więc, jeżeli wasz system używa nowego gita (2.44.0), to `cargo build` nie przejdzie:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```Można to obejść, klonując wszystko z `-c index.skipHash=false`.
Ale spoko, na pewno jest wielka zaleta z użycia przestarzałej, włączonej na sztywno biblioteki w C, która wynajduje gita na nowo.
-
Już dłuższą chwilę nie narzekałem na Rusta samego w sobie, więc…
Cargo upiera się na interakcji z repozytoriami #git. Jednocześnie, Cargo upiera się przy używaniu włączonej (zamiast systemowej), starej wersji #LibGit2 (z tego, co widzę: 1.6.2). Tak więc, jeżeli wasz system używa nowego gita (2.44.0), to `cargo build` nie przejdzie:
```
error: failed to determine package fingerprint for build script for uv v0.1.38 (/tmp/uv/crates/uv)Caused by:
failed to determine the most recently modified file in /tmp/uv/crates/uvCaused by:
failed to determine list of files in /tmp/uv/crates/uvCaused by:
failed to open git index at /tmp/uv/.git/Caused by:
invalid data in index - calculated checksum does not match expected; class=Index (10)
```Można to obejść, klonując wszystko z `-c index.skipHash=false`.
Ale spoko, na pewno jest wielka zaleta z użycia przestarzałej, włączonej na sztywno biblioteki w C, która wynajduje gita na nowo.
