Commit Graph

19 Commits

Author SHA1 Message Date
e6379af883 Rename service unit file to match package name
So that debhelper automatically installs it for me, instead of adding my
own install target.
2025-11-19 13:11:44 -06:00
a5734b0174 Patch Makefile to have a var for web root 2025-11-19 13:09:51 -06:00
c8cf70bd52 Override d/rules install to pass web root along 2025-11-19 13:08:51 -06:00
9dbd3d953e Add a Systemd service unit file for the server 2025-11-19 12:54:44 -06:00
41ca417386 Drop unneeded build-dep 2025-11-19 12:34:19 -06:00
6e2482f68c Update changelog for new snapshot 2025-11-19 12:25:16 -06:00
f383836c24 Fix branch name in d/gbp.conf 2025-11-19 12:24:45 -06:00
de58cd8d7c Mangle the rules file, trying to get WASM build 2025-11-19 10:18:15 -06:00
3d9dc77837 Build-Depend on rust-llvm to get default linker
Cargo is trying to use rust-lld by default. Instead of patching the
config file to use "lld", name the dependency in the dependencies list.
2025-11-19 10:14:20 -06:00
f7a49a2760 Revert "Build for WASM32 and use the LLD linker"
This reverts commit 3cabfa46c3.

I don't need to patch the linker, I need to take a dependency on the one
it's trying to use.
2025-11-19 10:13:07 -06:00
3cabfa46c3 Build for WASM32 and use the LLD linker 2025-11-18 14:13:18 -06:00
bb99cc8042 Add build dependency on the LLD linker
Rust defaults to `rust-lld`, which is somehow different from the no-
prefix "lld". I can add a patch to .cargo/config.toml to override the
linker selection.
2025-11-18 14:10:24 -06:00
69db7afd8d Update changelog for 0.6.0-1~1.gbp57907c release 2025-11-18 13:32:25 -06:00
57907c105a Re-diff patch queue 2025-11-18 13:31:47 -06:00
fcdb0f6980 Update changelog, mark Debian release 0.3.0-1.1
The following notice is also in the debian/changelog file. Be advised of
this "fun" build quirk:

  * WARN: The previous version, 0.3.0-1, can no longer be built without making
    corrections. It's debian/gbp.conf file will try to use "v0.3.0" as the up-
    stream release tag, but that is no longer correct. I moved that tag to mark
    the real Crate release and replaced it with the tag "v0.3.0+vendor".
    .
    I've chosen to increment the version by a minor release because I uploaded
    a build of 0.3.0-1 to my GitHub. I don't think anyone has used it or will
    care if the "true" original vanishes, but I'm choosing to operate as if
    there is.
    .
    If you are trying to rebuild that version, you must either patch gbp.conf
    or manually build a tarball from the new tag name. GBP doesn't validate the
    tarball so if it finds one named appropriately, then it will just use it.
2025-11-18 12:33:00 -06:00
3fb81b504c Add "+vendor" to upstream tag name
The real release tag will be on the trunk branch and will NOT include
the vendored dependencies. I have a weird pseudo-release branch thing
going on to make up for this right now. I might have to figure out the
pristine-tar workflow.
2025-11-18 11:53:44 -06:00
47dc685ffb Rediff patches
Add 0003-Use-mini-as-release-profile.patch: <REASON>
Add 0001-Alter-blake3-to-emit-Built-Using-info.patch: <REASON>
Add 0002-Use-pure-Rust-implementation-of-Blake3-parts.patch: <REASON>
2025-09-28 12:58:43 -05:00
736f7ab260 Add missing build-depends 2025-09-28 12:55:15 -05:00
2d5830d3bc Begin package for Debian Trixie 2025-09-28 12:46:23 -05:00