Package Details: alacritty-git 1:0.11.0.2004.g2a676dfa-1

Git Clone URL: https://aur.archlinux.org/alacritty-git.git (read-only, click to copy)
Package Base: alacritty-git
Description: A cross-platform, GPU-accelerated terminal emulator
Upstream URL: https://github.com/alacritty/alacritty
Keywords: GPU rust terminal
Licenses: Apache
Conflicts: alacritty
Provides: alacritty
Submitter: quininer
Maintainer: quininer
Last Packager: quininer
Votes: 90
Popularity: 0.069943
First Submitted: 2016-11-01 13:53 (UTC)
Last Updated: 2022-07-16 16:56 (UTC)

Required by (27)

Sources (1)

Latest Comments

b0o commented on 2022-07-11 05:59 (UTC)

If you get the following error:

==> Starting package_alacritty-git()...
install: cannot stat 'extra/linux/io.alacritty.Alacritty.appdata.xml': No such file or directory

You can modify PKGBUILD like so:

:100644 100644 e30c1d8 0000000 M    PKGBUILD

diff --git a/PKGBUILD b/PKGBUILD
index e30c1d8..da33e67 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,6 +1,6 @@
 pkgname='alacritty-git'
 _pkgname="alacritty"
-pkgver=0.10.0.1880.gc96047dc
+pkgver=0.11.0.2002.ge09ff0b4
 pkgrel=1
 epoch=1
 arch=('x86_64' 'i686')
@@ -37,7 +37,7 @@ package_alacritty-git() {

    install -D -m755 "target/release/alacritty" "$pkgdir/usr/bin/alacritty"
    install -D -m644 "extra/alacritty.man" "$pkgdir/usr/share/man/man1/alacritty.1"
-   install -D -m644 "extra/linux/io.alacritty.Alacritty.appdata.xml" "$pkgdir/usr/share/appdata/io.alacritty.Alacritty.appdata.xml"
+   install -D -m644 "extra/linux/org.alacritty.Alacritty.appdata.xml" "$pkgdir/usr/share/appdata/org.alacritty.Alacritty.appdata.xml"
    install -D -m644 "alacritty.yml" "$pkgdir/usr/share/doc/alacritty/example/alacritty.yml"
    install -D -m644 "extra/completions/alacritty.bash" "$pkgdir/usr/share/bash-completion/completions/alacritty"
    install -D -m644 "extra/completions/_alacritty" "$pkgdir/usr/share/zsh/site-functions/_alacritty"

This was changed in https://github.com/alacritty/alacritty/commit/e09ff0b4b0654fd6dbcf8c0bdc73fdb9ae7d8016

trouter commented on 2022-01-30 19:40 (UTC)

Hi quininer,

As abhinav mentions below this works just fine on ARM64, so the "aarch64" architecture can be added to the PKGBUILD file.

For me however the tests are failing when installing this AUR package, so I have to use --nocheck. If you remove the "--release" argument from the "cargo test" command then it appears to work just fine.

It would be amazing if these small changes could be incorporated so that it works out of box on ARM64 machines!

Regards, Aaron

polyzen commented on 2021-10-04 17:40 (UTC)

You can just use the --nocheck option for makepkg.

itachi commented on 2021-10-04 13:26 (UTC)

can you please remove test for alacritty-git? as it is really annoying and resource hungry.

abhinav commented on 2021-09-17 04:07 (UTC)

Hey, I've got two patches in https://gist.github.com/abhinav/8d256a97017eeed7e3b67fe1a61dd3be.

One adds libxkbcommon to makedepends. This is necessary to build the package.

The second adds the .png icon to /usr/share/pixmaps so that ChromeOS (with Crostini) renders the correct icon.

abhinav commented on 2021-09-03 04:42 (UTC)

FYI, this worked for me on an ARM64 Linux machine after installing libxkbcommon, so the list of architectures can probably include aarch64 as well.

$ uname -a
Linux arch 5.4.119-14945-gafc97d54f809 #1 SMP PREEMPT Thu Aug 19 18:52:27 PDT 2021 aarch64 GNU/Linux

polyzen commented on 2021-08-01 18:08 (UTC)

Need to add a makedep on libxkbcommon: https://github.com/alacritty/alacritty/commit/01a7ad946e75ef9ff7847ad73f2fe40e3e5d8a5f#diff-09b140a43ebfdd8dbec31ce72cafffd15164d2860fd390692a030bcb932b54a0

zagg commented on 2021-04-04 14:35 (UTC) (edited on 2021-04-04 14:35 (UTC) by zagg)

Hi all.

Just tried to build it today and failed with the following. Any ideas on the root cause?

failures:

---- grid::storage::tests::indexing_above_inner_len stdout ----
note: test did not panic as expected

failures:
    grid::storage::tests::indexing_above_inner_len

test result: FAILED. 111 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.01s

error: test failed, to rerun pass '-p alacritty_terminal --lib'
==> ERROR: A failure occurred in check().
    Aborting...

SoN commented on 2020-11-22 22:24 (UTC)

Hello, I noticed some mixed up spaces and tabs in the indentation, so here I provide this humble patch:

https://gist.github.com/shade-of-noon/c73edcf330617d5bb1b65df5afc295f4

Thanks for maintaining this package and have a nice day.

codyps commented on 2020-11-07 21:13 (UTC)

Thanks for getting back to me on this @quininer. It's not entirely clear from your reply what your concern is here, and I hope you could clarify that for me.

The patch I've proposed doesn't require manual action from folks using makepkg, it just means that a cargo home that is separate from the one they use for doing normal cargo builds will be used for building packages. Is there some type of non-packaged & non-tracked configuration in the cargo home that we expect to have applied to the package? Alternately, are we concerned about having dependencies for this package downloaded/built separately from a particular users cargo home?

Generally, it's advisable to build arch packages in ways that don't depend on other items in the user's environment (which is why so often folks talk about using clean chroots for building packages). This type of thing (not depending on other random state) leads me towards the idea that re-using an existing cargo home isn't a great choice here.

I don't think it's a good idea to require package-specific environment modification to enable a package to build when one is using completely normal options (like debug). It's also the case that the current PKGBUILD behavior here (installing files into home dir when debug is enabled) does not appear to be supported by the Arch package guidelines.

If you're still concerned about having a separate cargo home: consider that you may be able to either: 1. find appropriate -ffile-prefix-map options, or 2. work with makepkg itself to improve support for this particular use case.

If you decide you wish to persue either of those, I encourage fixing the package in the mean time by applying the patch I've already proposed.

Finally, if there's a desire not to support debug for some reason, the PKGBUILD should explicitly disable it in it's OPTIONS (OPTIONS += (!debug)) (I don't like that solution, but it's better than generating packages that depend on the building user's home dir and install files into that same building user's home dir).

quininer commented on 2020-11-07 07:19 (UTC)

@codyps If you need debug package, you can add the environment variable before makepkg, instead of requiring everyone to copy a $HOME/.cargo.

codyps commented on 2020-11-05 22:45 (UTC)

This package still doesn't work properly with OPTIONS+=(debug). Please apply the patch I provided in my previous comment.

https://gist.github.com/jmesmon/6ce967c6a9769b39bab842110f84a665 https://aur.archlinux.org/packages/alacritty-git/#comment-760573

codyps commented on 2020-08-12 16:14 (UTC) (edited on 2020-08-12 16:15 (UTC) by codyps)

tldr: https://gist.github.com/jmesmon/6ce967c6a9769b39bab842110f84a665

Currently, when OPTIONS+=(debug) is set in makepkg.conf, this package tends to install source code files into the home directory of the user that built the package.

This appears to be due to the debug info referencing files in the $HOME/.cargo directory (which are picked out of the debug info to fill the -debug package).

Normally, the debug info would be edited so that all files end up under the /usr/src/debug/<pkgname> directory, but if the source files exist outside of the srcdir (like files in `$HOME/.cargo) this doesn't work.

To resolve this, the environment variable CARGO_HOME should be set to place the directory formerly at $HOME/.cargo into the srcdir.

Here's a patch which makes this change and results in proper /usr/src/debug content: https://gist.github.com/jmesmon/6ce967c6a9769b39bab842110f84a665

sinshutu commented on 2020-03-15 01:19 (UTC)

Thank you for the maintenance. However, the build failed at this commit: c79216caadd5b287f27048fc97454022f791ad73

I don't know the cause, but I solved it by the following method

diff --git a/PKGBUILD b/PKGBUILD
index 79ed747..621b5ca 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -33,7 +33,7 @@ package_alacritty-git() {

        cd $_pkgname

-       desktop-file-install -m 644 --dir "$pkgdir/usr/share/applications/" "$srcdir/$_pkgname/extra/linux/alacritty.desktop"
+       desktop-file-install -m 644 --dir "$pkgdir/usr/share/applications/" "$srcdir/$_pkgname/extra/linux/Alacritty.desktop"

        install -D -m755 "target/release/alacritty" "$pkgdir/usr/bin/alacritty"
        install -D -m644 "extra/alacritty.man" "$pkgdir/usr/share/man/man1/alacritty.1"

There is no confirmation, but there may be a compatibility problem with desktop-file-utils

$ yay -Qi desktop-file-utils
name                   : desktop-file-utils
version                : 0.24-2

FichteFoll commented on 2020-02-20 00:42 (UTC) (edited on 2020-02-20 00:42 (UTC) by FichteFoll)

It appears the terminfo files are now included in ncurses, which is probably why the split package has been removed.

However, git still needs to be added as a makedep.

~ λ pacman -Fl ncurses | grep alacritty
ncurses usr/share/terminfo/a/alacritty
ncurses usr/share/terminfo/a/alacritty+common
ncurses usr/share/terminfo/a/alacritty-direct

~ ∀ pacman -Fl alacritty-terminfo-git
alacritty-terminfo-git usr/
alacritty-terminfo-git usr/share/
alacritty-terminfo-git usr/share/terminfo/
alacritty-terminfo-git usr/share/terminfo/a/
alacritty-terminfo-git usr/share/terminfo/a/alacritty
alacritty-terminfo-git usr/share/terminfo/a/alacritty-direct

FFY00 commented on 2020-02-18 23:26 (UTC) (edited on 2020-02-18 23:27 (UTC) by FFY00)

1ace, sorry for the late reply, AUR is awful at handling notifications.

My comment last comment was referring to alacritty-terminfo (somehow I forgot to mention it, :facepalm:), which you now have seemed to have removed. Please reinstate it and make it any.

jhenson commented on 2020-01-27 22:08 (UTC) (edited on 2020-01-27 22:08 (UTC) by jhenson)

This package should have a git listed as a make dep.

1ace commented on 2020-01-22 09:35 (UTC)

@FFY00: all your comments are correct except the last one.

The arch field is about the compatibility to use the package, not to build it. Once compiled, alacritty can only run on the arch it was built for, not on any arch (like a simple script would, for instance), so the current value is correct and changing it to any would be wrong.

Again, all your other comments are good and should be applied to this package.

FFY00 commented on 2020-01-22 01:54 (UTC) (edited on 2020-01-22 01:55 (UTC) by FFY00)

Hello, could you please fix some issues with the current PKGBUILD?

DrJPepper commented on 2019-06-09 23:14 (UTC)

I had to add

| sed s/-//g

to the echo line in pkgver() to get it to work on the latest rc release.

seo.disparate commented on 2019-05-05 05:14 (UTC)

Just as edacval mentioned, 'python' is a missing build dependency, and also 'libxcb'.

edacval commented on 2019-05-04 16:34 (UTC)

Missing 'python' in makedepends() ? :

error: failed to run custom build command for `xcb v0.8.2`
process didn't exit successfully: `/tmp/makepkg/alacritty-git/src/alacritty/target/release/build/xcb-29582f47a57e4f44/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Unable to find build dependency python3: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:997:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in package_alacritty-git().
    Aborting...

1ace commented on 2019-04-30 12:03 (UTC) (edited on 2019-04-30 12:05 (UTC) by 1ace)

Alacritty has been reorganized a bit, making the current pkgver() fails to read the version.

There's also a new rust-clipboard crate used now, which means the xclip dependency is now gone.

And while at it, git rev-parse --short should be given a length so that it gives the same output regardless of one's default settings :)

diff --git a/PKGBUILD b/PKGBUILD
index e6f0cc3c5e90590a4847..386e8546c024365f9e9d 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,6 +1,6 @@
 pkgname=('alacritty-git' 'alacritty-terminfo-git')
 _pkgname="alacritty"
-pkgver=0.3.2.1190.g9c6d12e
+pkgver=0.3.2.1199.g66fb7cb
 pkgrel=1
 arch=('x86_64' 'i686')
 url="https://github.com/jwilm/alacritty"
@@ -11,12 +11,12 @@ sha256sums=('SKIP')

 pkgver() {
    cd $_pkgname
-   echo "$(grep '^version =' Cargo.toml|head -n1|cut -d\" -f2).$(git rev-list --count HEAD).g$(git rev-parse --short HEAD)"
+   echo "$(grep '^version =' alacritty/Cargo.toml|head -n1|cut -d\" -f2).$(git rev-list --count HEAD).g$(git rev-parse --short=7 HEAD)"
 }

 package_alacritty-git() {
    pkgdesc="A cross-platform, GPU-accelerated terminal emulator"
-   depends=('freetype2' 'fontconfig' 'xclip')
+   depends=('freetype2' 'fontconfig')
    provides=('alacritty')
    conflicts=('alacritty')

danekl commented on 2019-04-27 08:56 (UTC)

Could you please update the "tic" command to: "tic -o "$pkgdir/usr/share/terminfo" -xe alacritty,alacritty-direct alacritty.info"?

Notice the "-xe alacritty,alacritty-direct". This is from the main alacritty package in [community], and according to Alacritty's installation guidelines: https://github.com/jwilm/alacritty/blob/master/INSTALL.md#terminfo

valentjedi commented on 2019-04-24 10:55 (UTC) (edited on 2019-04-24 10:55 (UTC) by valentjedi)

@apetresc "no default toolchain configured" could be fixed by following this SO thread: https://stackoverflow.com/q/44303915/3606603

Basically, it's

rustup default stable # or rustup default nightly

And then retry the build

apetresc commented on 2019-04-15 15:00 (UTC)

Now the build fails immediately with:

==> Starting package_alacritty-git()...
error: no default toolchain configured

(though alacritty-git itself builds just fine)

Chocobo commented on 2019-01-02 13:44 (UTC) (edited on 2019-01-02 13:48 (UTC) by Chocobo)

Hmm the build is failing with the following message:

   Compiling termcolor v1.0.4
   Compiling copypasta v0.0.1 (/home/swinchen/.cache/yay/alacritty-git/src/alacritty/copypasta)
error[E0658]: scoped lint `clippy::all` is experimental (see issue #44690)
 --> copypasta/src/lib.rs:3:9
  |
3 | #![deny(clippy::all, clippy::if_not_else, clippy::enum_glob_use, clippy::wrong_pub_self_convention)]
  |         ^^^^^^^^^^^

error[E0658]: scoped lint `clippy::if_not_else` is experimental (see issue #44690)
 --> copypasta/src/lib.rs:3:22
  |
3 | #![deny(clippy::all, clippy::if_not_else, clippy::enum_glob_use, clippy::wrong_pub_self_convention)]
  |                      ^^^^^^^^^^^^^^^^^^^

error[E0658]: scoped lint `clippy::enum_glob_use` is experimental (see issue #44690)
 --> copypasta/src/lib.rs:3:43
  |
3 | #![deny(clippy::all, clippy::if_not_else, clippy::enum_glob_use, clippy::wrong_pub_self_convention)]
  |                                           ^^^^^^^^^^^^^^^^^^^^^

error[E0658]: scoped lint `clippy::wrong_pub_self_convention` is experimental (see issue #44690)
 --> copypasta/src/lib.rs:3:66
  |
3 | #![deny(clippy::all, clippy::if_not_else, clippy::enum_glob_use, clippy::wrong_pub_self_convention)]
  |                                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to 4 previous errors

For more information about this error, try `rustc --explain E0658`.
error: Could not compile `copypasta`.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in package_alacritty-git().
    Aborting...
Error making: alacritty-git (alacritty-git alacritty-terminfo-git)

This doesn't seem Arch related, but does anyone know of a workaround?

MathieuPetit commented on 2018-11-23 23:05 (UTC)

Answering to myself : it was a temporary dependency problem from upstream. See https://github.com/jwilm/alacritty/pull/1838

MathieuPetit commented on 2018-11-23 22:55 (UTC)

Hello, build fails with this message :

==> Starting pkgver()...
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package_alacritty-git()...
    Updating git repository `https://github.com/zacps/winpty`
error: failed to load source for a dependency on `winpty-sys`                                                                                                                                                                      

Caused by:
  Unable to update https://github.com/zacps/winpty?branch=rust#9ccec645

Caused by:
  revspec '9ccec6459c2c8b7555846910c12ba697b688f44d' not found; class=Reference (4); code=NotFound (-3)
==> ERROR: A failure occurred in package_alacritty-git().
    Aborting...
:: failed to build alacritty-git package(s)

Not sure what to try next.

dreivier commented on 2018-11-13 16:15 (UTC)

Not sure what happened but for me it fails with this message:

error[E0432]: unresolved import `core::hint`
  --> /home/me/.cargo/registry/src/github.com-1ecc6299db9ec823/ordered-float-1.0.1/src/lib.rs:16:11
   |
16 | use core::hint::unreachable_unchecked;
   |           ^^^^ Could not find `hint` in `core`

error[E0658]: the `#[repr(transparent)]` attribute is experimental (see issue #43036)
  --> /home/me/.cargo/registry/src/github.com-1ecc6299db9ec823/ordered-float-1.0.1/src/lib.rs:44:1
   |
44 | #[repr(transparent)]
   | ^^^^^^^^^^^^^^^^^^^^

error[E0658]: the `#[repr(transparent)]` attribute is experimental (see issue #43036)
   --> /home/me/.cargo/registry/src/github.com-1ecc6299db9ec823/ordered-float-1.0.1/src/lib.rs:173:1
    |
173 | #[repr(transparent)]
    | ^^^^^^^^^^^^^^^^^^^^

error: aborting due to 3 previous errors

aignas commented on 2018-11-12 18:41 (UTC)

Another fix is to add at the end of the echo line | tr - _.

nixpulvis commented on 2018-11-12 17:50 (UTC)

To fix this I've replaced the last segment of the pkgver with git rev-parse --short HEAD and it seems to work.

echo "$(grep '^version =' Cargo.toml|head -n1|cut -d\" -f2).$(git rev-list --count HEAD).g$(git rev-parse --short HEAD)"

eggze commented on 2018-11-12 16:50 (UTC)

git describe started returning v0.2.2-2-g4a8d18c because there is now tag v0.2.2; it leads to broken build with the following error:

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: 0.2.2.990.gv0.2.2-2-g4a8d18c

bepvte commented on 2018-09-28 16:39 (UTC)

Spent a long time fighting with this package to get it to build Disabling the "debug" switch in the pkgbuild prevents the DWARF debugging related errors. Remove all lto relating cflags and ldflags from your makepkg.conf

quininer commented on 2018-09-18 12:18 (UTC)

@samhh Please update your rust version.

samhh commented on 2018-09-18 11:52 (UTC) (edited on 2018-09-18 11:52 (UTC) by samhh)

Compilation fails for me:

Compiling font v0.1.0 (file:///home/user/.cache/aurman/alacritty-git/src/alacritty/font) error[E0658]: use of unstable library feature 'pointer_methods' (see issue #43941) --> font/src/ft/fc/font_set.rs:102:60 | 102 | let ptr = (self.font_set.as_ptr()).fonts.add(self.current); | ^^^

error: aborting due to previous error

error: Could not compile font. warning: build failed, waiting for other jobs to finish... error: build failed ==> ERROR: A failure occurred in package_alacritty-git(). Aborting... 2018-09-18 12:51:26,247 - wrappers - makepkg - ERROR - makepkg query ['makepkg', '-cf', '--noconfirm'] failed in directory /home/user/.cache/aurman/alacritty-git

maximbaz commented on 2018-08-31 23:16 (UTC)

FFY00 but this is a -git package, are you planning to rebuild it after every commit?

FFY00 commented on 2018-08-31 22:07 (UTC) (edited on 2018-08-31 22:07 (UTC) by FFY00)

Hey, I want to move this to [community]. Is that ok with you?

SuperIce97 commented on 2018-05-29 11:48 (UTC)

desktop-file-install is part of the desktop-file-utils package. Please add that to the makedepends.

j605 commented on 2018-05-29 09:18 (UTC) (edited on 2018-05-29 09:56 (UTC) by j605)

update-desktop-database hook already exists so no need to have a install file. Please remove it.

edit: realised you are not using the install file after reading the PKGBUILD, sorry for the noise :)

bemeurer commented on 2018-03-08 03:51 (UTC)

@kveldulf Alacritty support for Wayland is experimental, I'm assuming you're using Gnome on Wayland, and so you'll see weird behavior like that. IIRC running alacritty on XWayland helps mitigate the weirdness.

guardian commented on 2018-02-19 16:57 (UTC)

When trying to launch alacritty I was welcomed with "No backend available".

I fixed it by installing libxcursor so likely you want to add it as a dependency

kveldulf commented on 2018-02-05 13:49 (UTC)

Maybe I'm misunderstanding something, but I installed this and whenever I click the Alacritty icon in my favorites bar in GNOME it opens a new icon that says "Unknown" and the UI is pretty weird, and it doesn't have basic features like holding a key down won't repeatedly input the value. Am I missing something?

bemeurer commented on 2017-12-04 03:10 (UTC)

Compiling the package with nightly causes it to not work. Would it be possible to force compilation to be done with the stable toolchain?

suzumiya commented on 2017-11-26 15:52 (UTC)

Thanks. Solved. It works well now after updating it.

quininer commented on 2017-11-15 05:52 (UTC)

@suzumiya update your rust.

suzumiya commented on 2017-11-15 02:29 (UTC)

Compiling nix v0.5.1 Compiling mio v0.5.1 Compiling notify v4.0.1 Compiling env_logger v0.4.3 error: cannot find macro `eprintln!` in this scope --> src/config.rs:1485:49 | 1485 | Err(err) => eprintln!("Ignoring invalid config: {}", err), | ^^^^^^^^ | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/config.rs:373:30 | 373 | _ => eprintln!("unknown modifier {:?}", modifier), | ^^^^^^^^ | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/config.rs:470:30 | 470 | _ => eprintln!("unknown mode {:?}", modifier), | ^^^^^^^^ | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/input.rs:190:25 | 190 | eprintln!("Error loading data from clipboard. {}", Red(err)); | ^^^^^^^^ | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 48 | die!("Waiting for pid {} failed: {}\n", PID, errno()); | ------------------------------------------------------ in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 84 | die!("openpty failed"); | ----------------------- in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 120 | die!("ioctl TIOCSCTTY failed: {}", errno()); | -------------------------------------------- in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 153 | die!("getpwuid_r failed"); | -------------------------- in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 157 | die!("pw not found"); | --------------------- in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 221 | die!("Failed to set session id: {}", errno()); | ---------------------------------------------- in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 269 | die!("Command::spawn() failed: {}", err); | ----------------------------------------- in this macro invocation | = help: did you mean `println!`? error: cannot find macro `eprintln!` in this scope --> src/macros.rs:18:9 | 18 | eprintln!($($arg)*); | ^^^^^^^^ | ::: src/tty.rs | 300 | die!("ioctl TIOCSWINSZ failed: {}", errno()); | --------------------------------------------- in this macro invocation | = help: did you mean `println!`? error: aborting due to 12 previous errors error: Could not compile `alacritty`. To learn more, run the command again with --verbose.

hiciu commented on 2017-08-23 11:49 (UTC)

polyzen, yes, you are correct. It looks like this is common. Shame to admit, I'm using aur for so long and I've noticed this just now :). Sorry about the noise.

polyzen commented on 2017-08-22 19:51 (UTC) (edited on 2017-08-22 19:51 (UTC) by polyzen)

hiciu, this is common usage: https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function

hiciu commented on 2017-08-22 13:43 (UTC)

pkgver() function will set pkgver field to something like this: $VERSION.$GIT_REVISIONS_COUNT.g$GIT_HASH There is a "g" before git hash. So for example this version: 0.1.0.571.g471237d-1 means that alacritty has been built from revision 471237d. This can be confusing, because "g" at the beginning could be mistaken for part of a git hash. I'm not sure if this should considered a problem - just reporting, because I spent last few minutes looking for revision g471237d in git repo :).

quininer commented on 2017-08-16 08:42 (UTC)

@maandree You should use makechrootpkg to build it.

maandree commented on 2017-08-16 07:54 (UTC)

- Creating working copy of alacritty git repo... Cloning into 'alacritty'... done. == Starting pkgver()... == Entering fakeroot environment... == Starting package_alacritty-git()... error: failed to open: /var/empty/.cargo/registry/index/github.com-1ecc6299db9ec823/.cargo-index-lock Caused by: Permission denied (os error 13) The home directory of my package building user is /var/empty. Why is it writting to my home directory rather than a temporary directory?

quininer commented on 2017-08-14 17:55 (UTC)

oops, makedepends must be global.

quininer commented on 2017-08-14 17:38 (UTC) (edited on 2017-08-14 17:39 (UTC) by quininer)

@timofonic Why? What's the problem with you?

timofonic commented on 2017-08-14 17:34 (UTC)

@quininer Can you please fix dependencies on this package? As it is now, I consider this package both broken and outdated.

eggze commented on 2017-08-14 13:56 (UTC) (edited on 2017-08-14 13:58 (UTC) by eggze)

Can we add rust as dependency as discussed here: https://github.com/jwilm/alacritty/issues/718? Rust is now official package in Community repo and it contains cargo too. Maybe change makedepends=('cargo' 'cmake' 'git') to makedepends=('rust' 'cmake' 'git')?

quininer commented on 2017-08-02 16:39 (UTC)

@mmlb It should be in this package. I'll submit a merge request.

mmlb commented on 2017-08-02 15:27 (UTC)

It be nice if the termino file was compiled and installed as part of this package and avoid the need for https://aur.archlinux.org/packages/alacritty-terminfo-git/. Is there a reason for it not being in this package?

polyzen commented on 2017-07-30 03:49 (UTC) (edited on 2017-07-30 08:24 (UTC) by polyzen)

Users of -git packages are expected to follow upstream development. This is probably especially important when the "software is considered to be at an alpha level of readiness".

commented on 2017-07-29 00:34 (UTC)

Is there a need for these files? If so, why aren't they distributed with alacritty-git? Why aren't they mentioned in the readme? If not, what is their purpose? Excuse my ignorance, I just don't know what is their purpose, even after googling. Because other terminals don't ship them, I suppose?

commented on 2017-07-29 00:28 (UTC)

I also maintain a -git package and honeslty - bumping a version once in a while, as soon as an important feature arrives is good for everyone and not really hard. Even if guidelines (IIRC) tell that there's no need to update such packages, I personally prefer to just to make life a bit easier for everyone else. So, thank you, quininer, for keeping it up to date.

maximbaz commented on 2017-07-25 21:17 (UTC)

No doubt about that, my point is that everyone gets these updates automatically, you don't have to update PKGBUILD for that. This is because AUR helpers treat packages with "-git" suffix in a special way, the value of pkgver field is ignored in favor of calling pkgver() function. I'm simply trying to save you from doing meaningless work ;)

quininer commented on 2017-07-25 09:08 (UTC)

@maximbaz alacritty just merged with XIM support, I think this is an important update.

maximbaz commented on 2017-07-25 08:57 (UTC)

Hey @quininer, just so that you know, you don't have to update pkgver every time. Because this is a -git package which has pkgver() function, most AUR helpers are (supposed to be) able to detect changes automatically, i.e. as soon as a new commit is pushed to master we all can update to it without waiting for you to update the pkgver. AUR maintainers have to update pkgver only for those packages that follow official releases, but alacritty is simply not there yet.

Jonhoo commented on 2017-06-03 05:13 (UTC)

maximbaz: the change ended up having to be a little different (using tic -o), but pkgrel=2 should now work correctly. Thanks for the heads up!

maximbaz commented on 2017-06-03 04:59 (UTC)

@Jonhoo looks like the terminfo files have to be compiled with tic before they are placed to /usr/share/terminfo folder. I installed this package and ran the following commands: ❯ infocmp alacritty infocmp: couldn't open terminfo file /usr/share/terminfo/a/alacritty. ❯ sudo tic /usr/share/terminfo/a/alacritty "/usr/share/terminfo/a/alacritty", line 5, col 11, terminal 'alacritty': unknown capability 'Tc' ❯ infocmp alacritty # Reconstructed via infocmp from file: /usr/share/terminfo/a/alacritty alacritty| alacritty, .... Could you maybe add this step to PKGBUILD? I think it's enough to add the following two lines to the end of package(): tic "$pkgdir/usr/share/terminfo/a/alacritty" tic "$pkgdir/usr/share/terminfo/a/alacritty-256color"

Jonhoo commented on 2017-06-02 02:22 (UTC)

Following up from alacritty GitHub issue: now that we have an alacritty terminfo file (see jwilm/alacritty#578), we should probably do the same thing as `rxvt-unicode` does and [provide a split package](https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/rxvt-unicode#n79) with both `alacritty-git` and [`alacritty-terminfo-git`](https://aur.archlinux.org/packages/alacritty-terminfo-git/).

terlar commented on 2017-05-03 11:33 (UTC)

This should have git as makedepends

crashandburn4 commented on 2017-04-12 16:53 (UTC) (edited on 2017-04-12 16:56 (UTC) by crashandburn4)

failed to parse manifest at `alacritty-git/src/alacritty-git/font/Cargo.toml` Caused by: could not parse input as TOML font/Cargo.toml:14:9 expected a key but found an empty string font/Cargo.toml:14:9-14:10 expected `.`, but found `'` The file is like so: [package] name = "font" version = "0.1.0" authors = ["Joe Wilm <joe@jwilm.com>"] description = "Font rendering using the best available solution per platform" license = "Apache-2.0" [dependencies] euclid = "0.6.8" libc = "0.2.11" ffi-util = { path = "../ffi-util" } log = "0.3" [target.'cfg(not(target_os = "macos"))'.dependencies] servo-fontconfig = { git = "https://github.com/jwilm/rust-fontconfig" } freetype-rs = "0.9.0" [target.'cfg(target_os = "macos")'.dependencies] core-text = "1.1.1" core-foundation = "0.2.2" core-graphics = "0.3.2" core-foundation-sys = "0.2.2" The problem is with the line: [target.'cfg(not(target_os = "macos"))'.dependencies]

suzumiya commented on 2017-04-07 12:03 (UTC)

Alacrity has changed to rust stable. But still, compile error. Compile Error. ==> Removing existing $pkgdir/ directory... ==> Starting build()... error: no default toolchain configured ==> ERROR: A failure occurred in build(). Aborting... The official suggests to build it with `rustup`, other than `cargo` directly.

suzumiya commented on 2017-03-29 18:22 (UTC)

Compile Error. Cargo and rust has to be set to nightly. Compiling serde_derive v0.9.8 error: the `proc-macro` crate type is experimental | = help: add #![feature(proc_macro)] to the crate attributes to enable error: the `#[proc_macro_derive]` attribute is an experimental feature (see issue #35900) --> /home/suzumiya/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.9.8/src/lib.rs:24:1 | 24 | #[proc_macro_derive(Serialize, attributes(serde))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: add #![feature(proc_macro)] to the crate attributes to enable error: the `#[proc_macro_derive]` attribute is an experimental feature (see issue #35900) --> /home/suzumiya/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.9.8/src/lib.rs:33:1 | 33 | #[proc_macro_derive(Deserialize, attributes(serde))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = help: add #![feature(proc_macro)] to the crate attributes to enable error: aborting due to 2 previous errors Build failed, waiting for other jobs to finish... error: Could not compile `serde_derive`. To learn more, run the command again with --verbose. ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build alacritty-git.

thelongdivider commented on 2017-03-20 14:10 (UTC)

@polyzen I couldn't compile using yaourt. It appears to know what the default toolchain is if you simply download the program directly.

polyzen commented on 2017-02-15 07:30 (UTC)

Seems there was still an override set for the nightly. Built with current Rust stable (1.15.1).

polyzen commented on 2017-02-04 19:38 (UTC) (edited on 2017-02-15 07:36 (UTC) by polyzen)

Getting the same experimental bug as voyd with having used `rustup toolchain install stable`.

polyzen commented on 2017-02-04 19:07 (UTC)

Turns out Rust 1.15 isn't packaged yet.

Tyranic-Moron commented on 2017-02-04 18:12 (UTC)

@voyd you need to update to the latest stable rust toolchain (1.15.0); `rustup toolchain install stable`

voyd commented on 2017-02-04 11:28 (UTC)

Doesn't compile for me: error: attribute must only have one argument --> /home/voyd/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.9.6/src/lib.rs:20:3 | 20 | #[proc_macro_derive(Serialize, attributes(serde))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: attribute must only have one argument --> /home/voyd/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.9.6/src/lib.rs:29:3 | 29 | #[proc_macro_derive(Deserialize, attributes(serde))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: the `proc-macro` crate type is experimental | = help: add #![feature(proc_macro)] to the crate attributes to enable error: the `#[proc_macro_derive]` attribute is an experimental feature (see issue #35900) --> /home/voyd/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.9.6/src/lib.rs:20:1 | 20 | #[proc_macro_derive(Serialize, attributes(serde))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: the `#[proc_macro_derive]` attribute is an experimental feature (see issue #35900) --> /home/voyd/.cargo/registry/src/github.com-1ecc6299db9ec823/serde_derive-0.9.6/src/lib.rs:29:1 | 29 | #[proc_macro_derive(Deserialize, attributes(serde))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: aborting due to 2 previous errors

emersion commented on 2017-02-04 08:12 (UTC)

Alacritty doesn't need a nightly version of Rust anymore: https://twitter.com/i_am_jwilm/status/827550505349976064

commented on 2017-01-29 10:24 (UTC)

If you're using rustup you can replace the build line with this rustup run $(<rustc-version) cargo build --release which will build using the right nightly. No need for override.

Yamakaky commented on 2017-01-28 23:13 (UTC)

You should not do `cargo update` while packaging. The whole idea of Cargo.lock is replicable builds.

oconnor663 commented on 2017-01-25 22:04 (UTC)

Removing the `set override` line caused the build to break on machines that have rustup installed but which don't have it default to nightly, I think.

mmlb commented on 2017-01-24 19:00 (UTC)

It'd be nice if you could add git sha to the package version. I like to see what has changed between builds/installs. Something like: pkgver() { cd $pkgname echo $(grep '^version =' Cargo.toml|head -n1|cut -d\" -f2).$(git rev-list --count HEAD).g$(git describe --always) }

codybonney commented on 2017-01-21 08:08 (UTC) (edited on 2017-01-21 08:08 (UTC) by codybonney)

@thelongdivider I had to manually run "rustup override set nightly" to get around that error.

thelongdivider commented on 2017-01-19 16:44 (UTC)

error: no default toolchain configured

quininer commented on 2017-01-18 17:14 (UTC)

I decided to remove the `rustup set`.

quenyen commented on 2017-01-18 16:56 (UTC)

rustup override set nightly should be changed to.... rustup override set $(<rustc-version) To ensure a working nightly build. Sometimes nightly is broken whereas the above command works more often.

quenyen commented on 2017-01-18 16:46 (UTC)

I just tried to build with this and it failed....I successfully built manually though....

mmlb commented on 2017-01-10 17:12 (UTC)

you should get rid of setting rustup to the pinned version in the alacritty repo since it's now suggested that any recent nightly should be good. See https://github.com/jwilm/alacritty/issues/196

m3thodic commented on 2017-01-08 02:43 (UTC)

Came here to comment on needing to install rustup but saw the comments below -- thanks for the package!

antouank commented on 2017-01-07 11:08 (UTC)

@quininer installing rustup and doing `rustup default nightly` worked. Thanks!

quininer commented on 2017-01-07 10:28 (UTC)

@antouank use rustup.

antouank commented on 2017-01-07 10:26 (UTC)

@quininer Unfortunately rust-nightly also fails. ==> Validating source files with sha256sums... rustc-nightly-src.tar.gz ... FAILED docs.patch ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build rust-nightly. Any idea when it will go on stable? Thanks.

quininer commented on 2017-01-07 09:12 (UTC)

@antouank Now you need to install rust-nightly or rustup.wait until proc_macro is stable before you can compile with stable channel. @wbthomason @aabmass @jonathanio thanks!

antouank commented on 2017-01-07 08:59 (UTC)

does anyone else get this error? error[E0554]: #[feature] may not be used on the stable release channel

wbthomason commented on 2017-01-07 02:38 (UTC)

@quininer: I believe you may also be missing a few other dependencies - specifically, cmake, freetype2, and fontconfig. Admittedly, I haven't tried building without these installed, but the instructions on the alacritty repo for Arch specify that they are build requirements (https://github.com/jwilm/alacritty#arch-linux). I'll also note that the infinality versions of freetype2 and fontconfig are acceptable substitutes; the manual build works on my system with these packages installed. Thanks!

aabmass commented on 2017-01-07 02:35 (UTC) (edited on 2017-01-07 02:36 (UTC) by aabmass)

Thanks for the package! Would you mind adding the desktop entry to this package? It's $srcdir/Alacritty.desktop

jonathanio commented on 2017-01-05 21:04 (UTC)

@quininer: The current version of rush (i.e. via makedepend) will not build alacritty - you need the latest nightly version - so I have not been able to build it. I've created a patch for you which will use rustup instead of rust for the install and set the appropriate override. I've followed the documentation as it gives a fixed version specification defined by the repository as a requirement, but potentially rust-nightly might be a better choice even if it's slightly ahead of the pinned version given in rustc-version. The patch also saves a copy of the configuration file into /usr/share/alacritty with an install message to tell users to install it before they first run it. https://gist.github.com/jonathanio/b9dcf05ef9e5ec5fc8763713ebe95187 Hope this helps.