Hi there.
Several weeks ago I began to receive the following message, when updating packages from the AUR, which I have never encountered before:
Please specify which branch you want to rebase against.
I have searched for a solution & while I have found suggested fixes, I have not solved the issue - I suspect this is due to me not following them correctly due to a lack of understanding.
I would appreciate any assistance you could provide.
Thanks in advance
Ruziel 
How do you do this exactly, what command / program are you using?
Please, post command and whole (error) message.
As a starting point you could delete the corresponding cache in your home folder.
What is the output of
git branch --list
Not a whole lot to go on (you should always post commands used and exact error messages), but Iām thinking git (branches) rather than Manjaros.
Hi Wollie.
Thanks for your assistance. use YAY to update AUR packages. The command & error message is as follows (hopefully it formats the text correctly):
:: Synchronising package databases...
core is up to date
extra is up to date
multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
:: 5 packages to upgrade/install.
5 aur/brave-beta-bin 1.70.100-1 -> 1.74.11-1
4 aur/freetube-bin 0.21.3-1 -> 0.22.0-1
3 aur/nordvpn-bin 3.18.4-1 -> 3.19.1-1
2 aur/skypeforlinux-bin 8.127.0.200-1 -> 8.133.0.202-1
1 aur/zoom 6.1.11-1 -> 6.2.10-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
-> Excluding packages may cause partial upgrades and break systems
==>
AUR Explicit (5): skypeforlinux-bin-8.133.0.202-1, freetube-bin-0.22.0-1, nordvpn-bin-3.19.1-1, zoom-6.2.10-1, brave-beta-bin-1.74.11-1
:: (0/5) Failed to download PKGBUILD: zoom
:: (0/5) Failed to download PKGBUILD: brave-beta-bin
:: (0/5) Failed to download PKGBUILD: freetube-bin
:: (0/5) Failed to download PKGBUILD: nordvpn-bin
:: (0/5) Failed to download PKGBUILD: skypeforlinux-bin
-> error fetching zoom: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
error fetching brave-beta-bin: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
error fetching freetube-bin: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
error fetching nordvpn-bin: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
error fetching skypeforlinux-bin: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
Thanks,
R
PS
git branch --list gives no output
Have you tried to delete
~/.cache/yay/
Have the packages failed to download previously been built with yay or on another way?
Also, please post content of /etc/makepkg.conf
Thanks. there is no āYayā folder to delete with the locationā¦
~/.cache/yay/
I originally installed these packages simply by searching using Yay & selecting the appropriate numbered application to install.
I can also only find something named
/etc/makepkg.conf.d
Does that make sense or am I missing something?
Thanks, R
There should be a file makepkg.conf in folder /etc
At least for one of the not working packages I would try the manual install procedure:
Thanks, my oversight. Contents as follows:
#!/hint/bash
# shellcheck disable=2034
#
# /etc/makepkg.conf
#
#########################################################################
# SOURCE ACQUISITION
#########################################################################
#
#-- The download utilities that makepkg should use to acquire sources
# Format: 'protocol::agent'
DLAGENTS=('file::/usr/bin/curl -qgC - -o %o %u'
'ftp::/usr/bin/curl -qgfC - --ftp-pasv --retry 3 --retry-delay 3 -o %o %u'
'http::/usr/bin/curl -qgb "" -fLC - --retry 3 --retry-delay 3 -o %o %u'
'https::/usr/bin/curl -qgb "" -fLC - --retry 3 --retry-delay 3 -o %o %u'
'rsync::/usr/bin/rsync --no-motd -z %u %o'
'scp::/usr/bin/scp -C %u %o')
# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/wget
#-- The package required by makepkg to download VCS sources
# Format: 'protocol::package'
VCSCLIENTS=('bzr::breezy'
'fossil::fossil'
'git::git'
'hg::mercurial'
'svn::subversion')
#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"
#-- Compiler and Linker Flags
#CPPFLAGS=""
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
-Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
-fstack-clash-protection -fcf-protection \
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"
CXXFLAGS="$CFLAGS -Wp,-D_GLIBCXX_ASSERTIONS"
LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now \
-Wl,-z,pack-relative-relocs"
LTOFLAGS="-flto=auto"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g"
DEBUG_CXXFLAGS="$DEBUG_CFLAGS"
#########################################################################
# BUILD ENVIRONMENT
#########################################################################
#
# Makepkg defaults: BUILDENV=(!distcc !color !ccache check !sign)
# A negated environment option will do the opposite of the comments below.
#
#-- distcc: Use the Distributed C/C++/ObjC compiler
#-- color: Colorize output messages
#-- ccache: Use ccache to cache compilation
#-- check: Run the check() function if present in the PKGBUILD
#-- sign: Generate PGP signature file
#
BUILDENV=(!distcc color !ccache check !sign)
#
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""
#
#-- Specify a directory for package building.
#BUILDDIR=/tmp/makepkg
#########################################################################
# GLOBAL PACKAGE OPTIONS
# These are default values for the options=() settings
#########################################################################
#
# Makepkg defaults: OPTIONS=(!strip docs libtool staticlibs emptydirs !zipman !purge !debug !lto !autodeps)
# A negated option will do the opposite of the comments below.
#
#-- strip: Strip symbols from binaries/libraries
#-- docs: Save doc directories specified by DOC_DIRS
#-- libtool: Leave libtool (.la) files in packages
#-- staticlibs: Leave static library (.a) files in packages
#-- emptydirs: Leave empty directories in packages
#-- zipman: Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge: Remove files specified by PURGE_TARGETS
#-- debug: Add debugging flags as specified in DEBUG_* variables
#-- lto: Add compile flags for building with link time optimization
#-- autodeps: Automatically add depends/provides
#
OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto)
#-- File integrity checks to use. Valid: md5, sha1, sha224, sha256, sha384, sha512, b2
INTEGRITY_CHECK=(sha256)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)
#-- Directory to store source code in for debug packages
DBGSRCDIR="/usr/src/debug"
#-- Prefix and directories for library autodeps
LIB_DIRS=('lib:usr/lib' 'lib32:usr/lib32')
#########################################################################
# PACKAGE OUTPUT
#########################################################################
#
# Default: put built package and cached source in build directory
#
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Log files: specify a fixed directory where all log files will be placed
#LOGDEST=/home/makepkglogs
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <john@doe.com>"
#-- Specify a key to use for package signing
#GPGKEY=""
#########################################################################
# COMPRESSION DEFAULTS
#########################################################################
#
COMPRESSGZ=(gzip -c -f -n)
COMPRESSBZ2=(bzip2 -c -f)
COMPRESSXZ=(xz -c -z -)
COMPRESSZST=(zstd -c -T0 -)
COMPRESSLRZ=(lrzip -q)
COMPRESSLZO=(lzop -q)
COMPRESSZ=(compress -c -f)
COMPRESSLZ4=(lz4 -q)
COMPRESSLZ=(lzip -c -f)
#########################################################################
# EXTENSION DEFAULTS
#########################################################################
#
PKGEXT='.pkg.tar.zst'
SRCEXT='.src.tar.gz'
#########################################################################
# OTHER
#########################################################################
#
#-- Command used to run pacman as root, instead of trying sudo and su
#PACMAN_AUTH=()
# vim: set ft=sh ts=2 sw=2 et:
Thanks, R
The config file looks OK. Again, please try to update one package the manual way.
Apologies, Iām unaware how to update an individual package using Yay. However, when I try to reinstall Brave Browser, I get the followingā¦
[einohr@EinOhr ~]$ yay brave-beta-bin
1 aur/brave-beta-bin 1.74.11-1 (+41 0.06) (Installed: 1.70.100-1)
Web browser that blocks ads and trackers by default (beta binary release).
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 1
AUR Explicit (1): brave-beta-bin-1.74.11-1
:: (0/1) Failed to download PKGBUILD: brave-beta-bin
-> error fetching brave-beta-bin: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
Iām not sure if this helps. Thanks for your patience.
R
Iām wondering if going through the re-installation of Yay would helpā¦
No, definitely not.
It looks like yayās clone directory messed up. By default, itās the location mentioned above: .cache/yay but maybe itās the build directory?
You can try to clean it with
yay -Sc
no
first:
remove the ~/.config/yay directory
rm -rf ~/.config/yay
then use yay like this (with the -S option):
yay -S brave-beta-bin
instead of:
yay brave-beta-bin
I get a different response for the first vs. the second.
The first command works - the second just does nothing (except for printing a message that there is nothing to do)
Thanks. Unfortunately I get the following:
[einohr@EinOhr ~]$ sudo rm -rf ~/.config/yay
[einohr@EinOhr ~]$ yay -S brave-beta-bin
AUR Explicit (1): brave-beta-bin-1.74.11-1
:: (0/1) Failed to download PKGBUILD: brave-beta-bin
-> error fetching brave-beta-bin: There is no tracking information for the current branch.
Please specify which branch you want to rebase against.
See git-pull(1) for details.
git pull <remote> <branch>
If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=origin/<branch> master
context: exit status 1
Feel free to not help any further - you have been very generous.
Thanks, R
Iāll gladly oblige this your wish as well as stay clear of any potential further questions you might ever have.
yay -S brave-beta-bin
AUR Explicit (1): brave-beta-bin-1.74.11-1
:: PKGBUILD up to date, skipping download: brave-beta-bin
1 brave-beta-bin (Installed) (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
and then it downloads and installs the thing
after removing ~/.cache/yay and then issuing the command without the -S option, like you did
yay brave-beta-bin
1 aur/brave-beta-bin 1.74.11-1 (+41 0.06) (Installed)
Web browser that blocks ads and trackers by default (beta binary release).
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==>
there is nothing to do
Thatās a package not involving any git operations, it would download and extract deb package files, see
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=brave-beta-bin
Perhaps you should focus on solving this first as the rest might as well be consequential errors.
Why is your machine seemingly failing to download the PKGBUILD?
edit: Just found this bug report:
Do you have any GIT_ * environment vairables set? Please check:
$ printenv | grep -i '^git'
I think you might find the OP was simply acknowledging your help thus far, and suggesting that you need not feel obligated to continue.
Nonetheless, a possible and perhaps obvious workaround is to use the default (and recommended) application:
pamac update
ā¦orā¦
pamac build brave-beta-bin
pamac build freetube-bin
pamac build nordvpn-bin
pamac build skypeforlinux-bin
pamac build zoom
If this succeeds, the issue might only be with yay.
If unsuccessful, try:
pamac update -a --force-refresh
to refresh the database.
(This may especially be needed if you rarely use pamac).
Good luck.
As you can clearly see from my response, I read it as a rather carefully worded FY.
He is free to clarify ā¦
@Nachlese The comment that you read as a carefully worded FY was actually aimed at @Wollie for all the assistance provided. Wollie had been providing lots of suggestions & I didnāt notice that it was a different poster when I wrote that comment.
Apart from that, Iām not sure someone who was in need of assistance would send an FY comment to an administrator & someone who was kindly giving of their time to assist.
I was merely giving Wallie a easy way out. While your particular suggestion didnāt work, I still appreciated it. I trust this clarifies things but if not, it is unfortunately what you have read into my words.
Thanks for your seeking to assist me.
Ruziel
@soundofthunder Thanks a lot, this fixed my issue. I rarely use Pamac, so I applied the last suggestion you gave & everything is now up to date. Much appreciated!
@Wollie - I appreciated you spending all that time on helping me to fix the issue. It seems that āpamac update -a --force-refreshā finally sorted it out.
This truly is a great community - my son now runs Manjaro!
More power to you all.
Ruziel
Iām wondering if I need to stop using Yay & utilise Pamac instead going forward