Package Details: linux-bcachefs-git-docs 6.14.0.rc1.1.bcachefs.git.00042.g63bbe0ca4167.dirty-1

Git Clone URL: https://aur.archlinux.org/linux-bcachefs-git.git (read-only, click to copy)
Package Base: linux-bcachefs-git
Description: Documentation for the Linux kernel
Upstream URL: https://github.com/koverstreet/bcachefs
Licenses: GPL-2.0-only
Submitter: Chiruno
Maintainer: QuartzDragon
Last Packager: QuartzDragon
Votes: 16
Popularity: 0.000050
First Submitted: 2018-01-13 15:37 (UTC)
Last Updated: 2025-02-06 08:46 (UTC)

Pinned Comments

QuartzDragon commented on 2019-06-11 15:15 (UTC) (edited on 2019-06-11 15:17 (UTC) by QuartzDragon)

If there are bugs related to the PKGBUILD or config, report here.

Otherwise, please report here:

https://github.com/koverstreet/bcachefs/issues

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 Next › Last »

tscs37 commented on 2019-10-08 18:24 (UTC)

@nicman23 yeah that was pretty much the issue

creating a ext4 /tmp and patching makepkg fixes the issue afaict.

nicman23 commented on 2019-10-08 12:44 (UTC) (edited on 2019-10-08 12:45 (UTC) by nicman23)

@tscs37

this is a known issue when packaging anything on a bcachefs root. either compile the package on some other fs (tmpfs is also a choice) or patch your makepkg like so

--- /usr/bin/makepkg    2019-03-01 03:41:56.000000000 +0200
+++ /home/nikos/.local/bin/makepkg      2019-07-21 11:47:22.353595608 +0300
@@ -1465,10 +1465,10 @@

 if [[ $BUILDDIR -ef "$startdir" ]]; then
        srcdir="$BUILDDIR/src"
-       pkgdirbase="$BUILDDIR/pkg"
+       pkgdirbase="/tmp/$BUILDDIR/pkg"
 else
        srcdir="$BUILDDIR/$pkgbase/src"
-       pkgdirbase="$BUILDDIR/$pkgbase/pkg"
+       pkgdirbase="/tmp/$BUILDDIR/$pkgbase/pkg"

 fi

QuartzDragon commented on 2019-10-08 08:28 (UTC)

@tscs37

Hmmm. Cannot reproduce, sorry. :/

How are you building this? What PKGBUILD settings are you using?

tscs37 commented on 2019-10-08 04:32 (UTC)

I'm getting a bunch of errors from mkinitcpio after installing the latest version of this kernel;

depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/btrfs.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/trusted.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/scsi_mod.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/sd_mod.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/sr_mod.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/cxgb4.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/usb-storage.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/mmc_block.ko.xz: Exec format error
depmod: ERROR: failed to load symbols from /tmp/mkinitcpio.5iO0rN/root/lib/modules/5.2.0-arch1-1-bcachefs-git-180243-gb83dba0d3fde/kernel/virtio.ko.xz: Exec format error

QuartzDragon commented on 2019-10-07 20:33 (UTC)

I've changed the package version scheme to better reflect the commit of the build, so if you need to report a bug upstream, you can see what commit you're using at a glance.

QuartzDragon commented on 2019-07-24 06:22 (UTC)

I think I might cautiously wait until Kent fixes up bcachefs proper.

I guess I don't quite trust the conflict handler to do a proper fixup that won't cause issues...

nicman23 commented on 2019-07-21 08:02 (UTC) (edited on 2019-07-21 20:39 (UTC) by nicman23)

https://pastebin.com/zDhCzA9r

diff to the pkgbuild, it includes:

  • automatic latest x.x.y detection ie if you set _srcver_tag=5.1 then it goes to 5.1.19 + it correctly sets pkgver

  • automatic conflict handler (the below code did not work because git merge is silly with tags)

  • removal of bluetooth patch - it is included iirc E: it is

  • having the upstream git repo fetched in source=() from makepkg and added as a local filesystem remote

  • renaming prepare to actual_prepare because makepkg ordering is silly

compiling right now will update you within the hour for any possible issues but there ought to be none

E: running it since a couple of hours ago, nothing wrong to report

QuartzDragon commented on 2019-07-20 09:53 (UTC)

Implemented the first suggestion.

Second suggestion is borked:

merge: upstream_stable/v5.1.18 - not something we can merge
fatal: '--ours/--theirs' cannot be used with switching branches

nicman23 commented on 2019-07-20 08:16 (UTC) (edited on 2019-07-20 08:50 (UTC) by nicman23)

(echo "$_subarch"; yes) | make oldconfig

is better

also for simple conflicts, such as the one that is blocking 5.1.17, remove the git pull and add this

git fetch --tags upstream_stable
if ! git merge upstream_stable/v${_srcver_tag}
  then if ! git diff --name-only --diff-filter=U | xargs git checkout --theirs
    then git diff --name-only --diff-filter=U |
    while read line
    do sleep 0.1; if ! git checkout --theirs $line
      then sleep 0.1; git rm $line
      fi
    done
  fi
fi

QuartzDragon commented on 2019-07-04 23:27 (UTC)

Stuck at 5.1.15 for now.

5.1.16 produces an auto-merge conflict.