#fossilscm — Public Fediverse posts

#Fossil er distribuert forum, wiki, saksbehandler o.l. på toppen av #SQLite.

Nesten som en atproto-app som Eurosky-folka pusher 😜

Eks på oppsett for å kjøre greia på domeneshop:

https://få.rødsei.no/wiki?name=Fossil+på+domenshop&p

#FossilSCM #cgi

#Fossil er distribuert forum, wiki, saksbehandler o.l. på toppen av #SQLite.

Nesten som en atproto-app som Eurosky-folka pusher 😜

Eks på oppsett for å kjøre greia på domeneshop:

https://få.rødsei.no/wiki?name=Fossil+på+domenshop&p

#FossilSCM #cgi

@henrik If you’re going with #fossilscm you can host your project free at https://chiselapp.com 😎

@henrik If you’re going with #fossilscm you can host your project free at https://chiselapp.com 😎

Fossil https://fossil-scm.org is forum, chat, bug tracker, wiki. And a distributed version control.

#FossilSCM #Fossil #SQLite #Discord

Fossil https://fossil-scm.org is forum, chat, bug tracker, wiki. And a distributed version control.

#FossilSCM #Fossil #SQLite #Discord

Oh man how cool Fossil is! I updated the Goophy devlog entry on my gopher hole and with just one command: ' fossil commit -m "Update Goophy Devlog" ', it commited the changes and synced them with my remote fossil server.

#fossilscm #fossil

Oh man how cool Fossil is! I updated the Goophy devlog entry on my gopher hole and with just one command: ' fossil commit -m "Update Goophy Devlog" ', it commited the changes and synced them with my remote fossil server.

#fossilscm #fossil

@krille perhaps switching to platforms as the all-in-one #FossilSCM - easily self hosted on lowest tier vps - or #Codeberg would assuage who is annoyed at GitHub’s #softwareBloat. And boost participation.

Hi guys, I know this risk to become the dumbest question ever made on the #fediverse but I must ask it not matter what…

For all the experts and non-experts… Is it possible, or would it possible, to have a plain text image format?

Something that can be diffable and you can track changes as for instance the #SVG format. It looks like all these control versions, like #git, aren't very suitable to handle format like #png, #jpg ,etc… They can only handle them as a binary blob and track if it has changed and re-upload or re-download fully.

Long-story short: handle the creation of catalog with #Fossil-scm hasn't been very good regarding managing the huge amount of pictures…

#DesignWithOpenSource #gimp #opensource

Hi guys, I know this risk to become the dumbest question ever made on the #fediverse but I must ask it not matter what…

For all the experts and non-experts… Is it possible, or would it possible, to have a plain text image format?

Something that can be diffable and you can track changes as for instance the #SVG format. It looks like all these control versions, like #git, aren't very suitable to handle format like #png, #jpg ,etc… They can only handle them as a binary blob and track if it has changed and re-upload or re-download fully.

Long-story short: handle the creation of catalog with #Fossil-scm hasn't been very good regarding managing the huge amount of pictures…

#DesignWithOpenSource #gimp #opensource

Fossil-scm help

#fossilscm expert I need your help...

The repo on the server has an error on a hash:

size mismatch on artifact 1271: wanted 261534 but got 0
wrong hash on artifact 1271
954 non-phantom blobs (out of 1297 total) checked:  2 errors
low-level database integrity-check: ok

How can I fix it?
From the local machine I can't do anything:

fossil update
SQLITE_NOTICE(539): recovered 9 pages from /home/me/sp/projects/ctlg0.fossil-journal
Pull from ssh://me/sp/ctlg0.fossil
bind [127.0.0.1]:12000: Address already in use
Round-trips: 1   Artifacts sent: 0  received: 0
wrong hash on received artifact: 3661aa5b091f6eb3937419b05697b7ddc0e645cab2a5cf0e6a95fcc20203fe5f
Round-trips: 1   Artifacts sent: 0  received: 12
hash of rid 889 does not match its uuid (
fish: Job 1, 'fossil update' terminated by signal SIGABRT (Abort)

Is there any magic command to auto repair or discard that hash?

Thanks in advance!

#linux #freebsd #mastohelp #fossil

@aslakr @bert_hubert
And he also created the source management for SQLite: fossil-scm, which includes pikchr support (and webGUI, ticketing system, forum, developer chat, ...)
https://www.fossil-scm.org/
#sqlite #fossilscm

Anyone migrate from #GitHub or #GitLab to #Codeberg or other options? Curious what your experience might have been like. The 3 features I have a lot of interest in are Public #Repositories, Private Repositories, and #GitHubPages. GitHub offering all 3 of these for "#free" is a huge advantage for "users". #Forge #Foregejo #FossilSCM

Is there a #git command to create a single file backup of an entire repository? Say I'm self-hosted and I want to back up offsite now and then. In #fossilscm the repo is already a single file so it's trivial.

Is there a #git command to create a single file backup of an entire repository? Say I'm self-hosted and I want to back up offsite now and then. In #fossilscm the repo is already a single file so it's trivial.

Considering to replace #git with #fossilscm company wide.

Considering to replace #git with #fossilscm company wide.

If you're using #fossilscm then you might find these #nix flakes and #rust bindings useful:

https://git.sr.ht/~cgenie/libfossil-flake (#nix flake to download & compile libfossil source code)

https://git.sr.ht/~cgenie/libfossil-rs-ffi (low-level #rust bindings from bindgen)

https://git.sr.ht/~cgenie/libfossil-rs (a bit higher level #rust lib)

If you're using #fossilscm then you might find these #nix flakes and #rust bindings useful:

https://git.sr.ht/~cgenie/libfossil-flake (#nix flake to download & compile libfossil source code)

https://git.sr.ht/~cgenie/libfossil-rs-ffi (low-level #rust bindings from bindgen)

https://git.sr.ht/~cgenie/libfossil-rs (a bit higher level #rust lib)

#FossilSCM is cooler than I thought and https://fossil-scm.org really is like a fossil default server. It even has built in chat! :D

The last #Apache security update on #Debian broke something with #fossil #fossilscm.

This is fixed in Fossil trunk. Details here: https://fossil-scm.org/forum/forumpost/52e042d35a

If you get the "server did not reply" error when syncing a repo, update your client and server to the last snapshot. An official Fossil 2.24 release should be out in the coming days.

I deeply respect @briankrebs, but in this case I think the data he's presenting is fundamentally invalid. A little-known fact about #Git history is that #timestamps are both definable and mutable. While you might be able to make statements about when a Git commit was pushed to a server using the server-side SSH or HTTP logs, the fact that you can set GIT_AUTHOR_DATE and GIT_COMMITTER_DATE as environment variables means you can't rely on commit timestamps alone for this type of analysis.

This is a feature of Git since the ability to squash or rewrite its mutable history is a key differentiator compared to #FossilSCM or other #SCMs that treat history as immutable(ish). For example, allowing one to do things like report a commit as the time a patch or source document was originally written rather than just noting when it was committed or merged can be very useful in accurately representing the real-world evolution of data created outside the repository.

This is not a flaw in Git. Anyone savvy enough to craft the #xz attack could just as easily have adjusted their system clocks instead, leading to fraudulent timestamps in the commit history anyway.

Forensically, you'd need to look at the timestamps from NTP-backed server or router logs, not just the Git history. All Git clients are technically "offline" until they push one or more commits to a remote, so there's really no way to validate client-side SCM timestamps. This is also true of email headers, filesystem attributes, and any other data that relies on real system clocks or user-defined timestamps, so you'd need more points of correlation than are provided here.

https://www.linkedin.com/posts/bkrebs_one-of-the-more-interesting-graphics-ive-activity-7181358250112471040-fzeG

I deeply respect @briankrebs, but in this case I think the data he's presenting is fundamentally invalid. A little-known fact about #Git history is that #timestamps are both definable and mutable. While you might be able to make statements about when a Git commit was pushed to a server using the server-side SSH or HTTP logs, the fact that you can set GIT_AUTHOR_DATE and GIT_COMMITTER_DATE as environment variables means you can't rely on commit timestamps alone for this type of analysis.

This is a feature of Git since the ability to squash or rewrite its mutable history is a key differentiator compared to #FossilSCM or other #SCMs that treat history as immutable(ish). For example, allowing one to do things like report a commit as the time a patch or source document was originally written rather than just noting when it was committed or merged can be very useful in accurately representing the real-world evolution of data created outside the repository.

This is not a flaw in Git. Anyone savvy enough to craft the #xz attack could just as easily have adjusted their system clocks instead, leading to fraudulent timestamps in the commit history anyway.

Forensically, you'd need to look at the timestamps from NTP-backed server or router logs, not just the Git history. All Git clients are technically "offline" until they push one or more commits to a remote, so there's really no way to validate client-side SCM timestamps. This is also true of email headers, filesystem attributes, and any other data that relies on real system clocks or user-defined timestamps, so you'd need more points of correlation than are provided here.

https://www.linkedin.com/posts/bkrebs_one-of-the-more-interesting-graphics-ive-activity-7181358250112471040-fzeG

Started to play with http://fossil-scm.org/ recently and I’m surprised it’s not widely used in the industry.

#fossilscm #git #scm

Fossil SCM users here? #fossil #fossilscm

I'm considering using it for my notebase. Any experiences or links to share?

Fossil SCM users here? #fossil #fossilscm

I'm considering using it for my notebase. Any experiences or links to share?

AsmBB - by John Found. "fully written in assembly language and uses SQLite as a database back-end. That is why it can work on really weak hosting and in the same time serve huge amount of visitors without lags and delays."
https://asmbb.org/what-is-asmbb.1/

The initial user experience is quite impressive with a number of small affordances that build a silky feeling. Now on my shortlist for when I next desire to host a forum.

Found by way of #fossilscm forum and Brian Tiffin.
#SmallWeb

@cvennevik If you're willing to consider Fossil instead of Git, https://chiselapp.com is handy.

E.g. https://chiselapp.com/user/cmacleod/repository/tartaniser/home
#programming #sourcecontrol #fossilscm #git

@cvennevik If you're willing to consider Fossil instead of Git, https://chiselapp.com is handy.

E.g. https://chiselapp.com/user/cmacleod/repository/tartaniser/home
#programming #sourcecontrol #fossilscm #git

I tagged sqlite, but really it's #fossilscm that represents my ideal. A single self contained application that wraps data and UI and disconnected offline/online synchronization in one package. It's awesome, and I don't understand why more projects haven't copied it.

@maphew @beto @sara #FossilSCM is absolutely wonderful. For many people the use would be much simpler with Fossil. The default is to sync, and everything contained in an easily compilable binary, with the repository being one file. Plus, as you mention, distributed tickets, wiki etc.

For my personal projects I don’t use git anymore.

@beto @sara #FossilSCM is the better designed product. Distributed version control & tickets & comments & web UI & syncing across servers in a single executable & database file & cross platform. It's brilliant, full stop.

But, it's not interested in appealing to masses. It either works for you or doesn't. Not a fit for me. Still, I wish many people to see & experience it so they know what is possible, and build another one. It shouldn't be the only project in its class!
https://fossil-scm.org/

@projectgus VC is also nice especially when one uses #fossilscm

New #cxxomfort Release.

The newest commit, "Welcome to 2020 + [0, 1) ", primarily focuses on improving the backports from <random>. In particular, it overrides some of the utilities from that header in MSVC and GCC TR1 that were hilariously broken. There are also some other small improvements, such as adding basic support for Digital Mars 8.5x.

http://ryan.gulix.cl/fossil.cgi/cxxomfort

#softwaredevelopment #cxx #cpp #softwareprogramming #fossilscm

New #cxxomfort Release.

The new 2020-12-09 "Alatreon Expansion".

Includes a number of new benefits such as promoting array_ref, cstring_view and function_caller out of Supplements and into Utils; adds swap_if proposal, adds at_or, adds printf-like literals, and enhances compatibility with Clang 5.x and GCC 5.x.

http://ryan.gulix.cl/fossil.cgi/cxxomfort

#softwaredevelopment #cxx #cpp #softwareprogramming #fossilscm

New #cxxomfort Release.

Technically a beta release, the newest commit primarily marks an update to enhance type_traits and hash compatibility, and test the foundations for conformance with MSVC 2015 onward. The next "release" release should include correct support for MSVC 2015 and 2017, Clang 5.x and 6.x, and better <random>.

http://ryan.gulix.cl/fossil.cgi/cxxomfort

#softwaredevelopment #cxx #cpp #softwareprogramming #fossilscm

New #cxxomfort Release: the COVID Fonda Release.

Named as such because I thought it and coded it while eating empanadas, drinking vino tinto and "enjoying" confinement; this update primarily marks an update for the Doxygen documentation and the addition of a few C++20 features, most notably bind_front(), and the addition of some compatibility fixes to enhance support of MSVC 2013 and potentially MSVC 2015.

http://ryan.gulix.cl/fossil.cgi/cxxomfort

#softwaredevelopment #cxx #cpp #softwareprogramming #fossilscm