Hey should this pkg be deleted or updated ? A dependency does no longer exist anymore.
Search Criteria
Package Details: jupyterlab-git 1:3.0.0.r0.g63c5989cdd-1
| Git Clone URL: | https://aur.archlinux.org/jupyterlab-git.git (read-only, click to copy) |
|---|---|
| Package Base: | jupyterlab-git |
| Description: | JupyterLab computational environment |
| Upstream URL: | https://github.com/jupyterlab/jupyterlab |
| Keywords: | jupyter notebook python |
| Licenses: | custom |
| Submitter: | fabianz |
| Maintainer: | None |
| Last Packager: | fusion809 |
| Votes: | 4 |
| Popularity: | 0.000000 |
| First Submitted: | 2016-07-31 22:21 (UTC) |
| Last Updated: | 2020-12-24 01:29 (UTC) |
Dependencies (7)
- jupyterlab_server
- jsx-lexerAUR (make)
- nodejs (nodejs-gitAUR, nodejs-lts-fermiumAUR, nodejs-sharedAUR, nodejs-lts-hydrogen, nodejs-lts-iron) (make)
- python-recommonmark (make)
- python-setuptools (make)
- python-sphinx-copybutton (make)
- python-sphinx_rtd_theme (make)
Required by (1)
- jupyter-octave_kernel-git (optional)
Sources (2)
AkechiShiro commented on 2022-04-09 09:15 (UTC)
fusion809 commented on 2020-07-07 12:09 (UTC)
In case anyone is wondering, yes I am well aware that there is a build error at the moment, but a bug report for it exists upstream https://github.com/jupyterlab/jupyterlab/issues/8657, and there's nothing I can do about it downstream until they fix it upstream.
eschwartz commented on 2020-06-23 20:17 (UTC)
Many other AUR helpers implement a --devel flag too. The only recommended way to use yay and get yay to upgrade VCS packages is to use its --devel flag.
Users of plain old makepkg can just use a for loop and try to rebuild every package named *-git. That's what I, personally, do.
eschwartz commented on 2020-06-23 17:52 (UTC)
yay -Syu --devel is the only recommended way to get updates for VCS packages.
Yes, we very specifically want packages which have tagged versions to use those versions in the pkgver. This lets people easily compare the version they have installed to the version which is documented on the upstream website, or the version available as a non-git package, and "1034 commits since the 2.1.0 branchpoint" is a lot more comprehensible than "tens of thousands of commits since the initial commit".
P.S. please add epoch=1 so that users can easily migrate back to the sane version scheme.
katt commented on 2020-06-23 17:24 (UTC)
@fusion809 It'd be nice if at least the ones that can follow the guidelines, did.
I really don't understand why you decided to rip out the perfectly fine (and much saner) pkgver in https://aur.archlinux.org/cgit/aur.git/commit/?h=jupyterlab-git&id=206ec9da6549cda53b15a3a0f4d2ec4868f7d94a
While we're at it, this is a VCS package, there's absolutely no reason at all to keep bumping the pkgver, it just clutters the history like mad.
Pinned Comments
fusion809 commented on 2020-07-07 12:09 (UTC)
In case anyone is wondering, yes I am well aware that there is a build error at the moment, but a bug report for it exists upstream https://github.com/jupyterlab/jupyterlab/issues/8657, and there's nothing I can do about it downstream until they fix it upstream.