AUR (en) - chromium-dev

Search Criteria

Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL:	https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base:	chromium-dev
Description:	The open-source project behind Google Chrome (Dev Channel)
Upstream URL:	http://www.chromium.org
Keywords:	browser web
Licenses:	BSD
Submitter:	None
Maintainer:	sl1pkn07
Last Packager:	sl1pkn07
Votes:	158
Popularity:	0.005026
First Submitted:	2010-05-17 09:04 (UTC)
Last Updated:	2024-04-21 19:18 (UTC)

Git Clone URL:

https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)

Package Base:

chromium-dev

Description:

The open-source project behind Google Chrome (Dev Channel)

Upstream URL:

http://www.chromium.org

Keywords:

browser web

Licenses:

BSD

Submitter:

None

Maintainer:

sl1pkn07

Last Packager:

sl1pkn07

Votes:

158

Popularity:

0.005026

First Submitted:

2010-05-17 09:04 (UTC)

Last Updated:

2024-04-21 19:18 (UTC)

Latest Comments

« First ‹ Previous 1 .. 55 56 57 58 59 60 61 62 63 64 65 .. 152 Next › Last »

juston_li commented on 2014-09-17 18:29 (UTC)

chromium-system-jinja-r7.patch ... FAILED ==> ERROR: One or more files did not pass the validity check!

abandonedaccount commented on 2014-09-07 19:47 (UTC)

that pacman-git bug is tracked here: https://bugs.archlinux.org/task/41862

abandonedaccount commented on 2014-09-07 17:28 (UTC)

I'll try to find out why it isn't softlinked for me(likely pacman-git), I'll let you know what I find. I've tested so far with untouched makepkg.conf and pacman.conf but the error persists, pwd is: /tmp/yaourt-tmp-emacs/aur-chromium-dev/src and all other files are softlinked. Btw, thank you for maintaining this package! Much appreciated!

sl1pkn07 commented on 2014-09-07 17:20 (UTC)

maybe is a pacman-git problem all my test is with pacman 4.1.2-6 and yaourt 1.5-1

sl1pkn07 commented on 2014-09-07 17:15 (UTC)

is softlinked. add that option versions ago. always work the softlink is added if the files exist in sources array

abandonedaccount commented on 2014-09-07 17:01 (UTC)

I think the reason the tar.gz isn't softlinked is because of this line: noextract=("chromium-${pkgver}.tar.xz") haven't tested yet

sl1pkn07 commented on 2014-09-07 16:51 (UTC)

from yaourt (same test) http://sl1pkn07.wtf/paste/view/9a74f85f

sl1pkn07 commented on 2014-09-07 16:44 (UTC)

makepkg and yaourt softlink the sources from SRCDEST to srcdir http://sl1pkn07.wtf/paste/view/9dfbc763 tested with edit the pkgbuild and add pwd ls -la exit in lines 102, 103 and 104 (http://wstaw.org/m/2014/09/07/plasma-desktopil2384.png) all with untouch /etc/makepkg.conf

abandonedaccount commented on 2014-09-07 16:32 (UTC)

I was afraid that was the case which means it may be my (newer)pacman version: Pacman v4.1.2-406-g3e19-dirty - libalpm v8.0.2 putting an echo `pwd` before the bsdtar command shows current folder to be: /tmp/makepkg/chromium-dev/src while the .tar.gz resides in /tmp/sources/ I've the following /etc/makepkg.conf settings: BUILDDIR=/tmp/makepkg PKGDEST=/tmp/packages SRCDEST=/tmp/sources SRCPKGDEST=/tmp/srcpackages testing with SRCDEST unset in /etc/makepkg.conf leaves the downloaded tar.xz file in /tmp/yaourt-tmp-emacs/aur-chromium-dev and still fails. Rebuilding pacman yields the same version. makepkg (pacman) 4.1.2-406-g3e19-dirty (August 7 commit was last) was using yaourt 1.5 but now(next) using yaourt-git: yaourt 1.4-1-gb6b8 nothing changed. bsdtar: Error opening archive: Failed to open 'chromium-39.0.2145.4.tar.xz' pwd is: /tmp/makepkg/chromium-dev/src archive is actually in /tmp/sources/ or when SRCDEST above isn't set(and running yaourt in a new terminal) then archive is in: /tmp/yaourt-tmp-emacs/aur-chromium-dev/ where PKGBUILD &co. are also downloaded