- Aur-general - lists.archlinux.org

[aur-general] Go package dependencies
by Adam Levy 04 Mar '18

04 Mar '18

Hi there, I am co-maintaining a few AUR packages written in Golang and I just ran namcap on my built package. I got the following output on a few of my golang packages: $ namcap influxdb-1.4.3-1-x86_64.pkg.tar.xz influxdb E: Dependency glibc detected and not included (libraries ['usr/lib/libpthread.so.0', 'usr/lib/libc.so.6'] needed in files ['usr/bin/influx_inspect', 'usr/bin/influx_stress', 'usr/bin/influx', 'usr/bin/influx_tsm', 'usr/bin/influxd']) However 'glibc' is in the base group, and I thought that it wasn't necessary to declare dependencies from the base group since it should always be installed on a fresh OS install. Am I wrong about this point? Should I be including 'glibc' as a dependency in this package? Should I be including 'bash' as a dependency in packages with scripts that use bash? Thank you! Adam Levy (alaskanarcher)

4 5

Re: [aur-general] [PRQ#10789] Merge Request for remarkable-webkit2gtk
by Mikael Blomstrand 04 Mar '18

04 Mar '18

I just made a merge-request for a package I maintain. But I'm curious about what this actually means in practice when it's merged. Will current users be notified in some way? Will they be redirected to the new package? Or is it just about the votes? If users are not notified, is there a smart way to make them move to the new package before deleting? --- Micke On Sat, Mar 03, 2018 at 11:03:03PM +0000, notify(a)aur.archlinux.org wrote: > chawlindel [1] filed a request to merge remarkable-webkit2gtk [2] into > remarkable [3]: > > I'm maintainer of both packages. Decided to patch `remarkable` for > webkit2gtk. > > Aside: Will this mean that people trying to update remarkable- > webkit2gtk will get redirected to remarkable? > > [1] https://aur.archlinux.org/account/chawlindel/ > [2] https://aur.archlinux.org/pkgbase/remarkable-webkit2gtk/ > [3] https://aur.archlinux.org/pkgbase/remarkable/

3 3

[aur-general] Qutebrowser update
by Pierre Neidhardt 02 Mar '18

02 Mar '18

Qutebrowser 1.1.2 is out: https://github.com/qutebrowser/qutebrowser/releases. I'm the current PKGBUILD maintainer but I won't have access to an Arch Linux system before a while, so if anybody wants to update it for me, go ahead, that'd be very nice! Cheers! -- Pierre Neidhardt

3 8

[aur-general] TU (re-)Application
by Brad Fanella 28 Feb '18

28 Feb '18

Hi all, Perhaps this is a bit unorthodox, but in 2011 I resigned from my post as a TU for personal and time-related reasons [1]. Coming up on almost 7 years later, I'm still an avid Arch user, and have struck a balance in my life where I'm much more capable of contributing to open-source projects than I was back then. The warm regards and well-wishes from my fellow TUs at the time [2][3] have left an extremely positive impression on me, and I find myself once again wanting to pick up some orphaned packages in [community] (surprisingly, the MATE desktop is homeless). Therefore, I'm writing this message to see if there's any interest in getting another helping hand around here. Sincerely, Brad Fanella [1] https://www.mail-archive.com/aur-general@archlinux.org/msg14906.htm l [2] https://www.mail-archive.com/aur-general@archlinux.org/msg14915.htm l [3] https://www.mail-archive.com/aur-general@archlinux.org/msg14920.htm l

10 30

Re: [aur-general] aur-out-of-date: determine out-of-date AUR packages w.r.t. upstream
by Adam Levy 27 Feb '18

27 Feb '18

Neat program! It currently doesn't handle release candidate version tags. For example, $ aur-out-of-date -pkg influxdb [OUT-OF-DATE] [influxdb] Package influxdb should be updated from 1.4.3-1 to 1.5.0rc4 It might be worth adding an option to ignore version tags that end in 'rc*'. Or perhaps make that the default and add a flag to *not* ignore release candidate tags. I'm sure there are other conventions for post-fixes on version tags that indicate pre release or testing status. Maybe a more flexible way to go would be to offer an environment variable or option for setting a list of regexes to disregard if matched. Thanks! Adam Levy

2 1

[aur-general] Dropping python-colorlog and python2-colorlog
by Pierre Neidhardt 25 Feb '18

25 Feb '18

python-colorlog and python2-colorlog just got flagged out-of-date, is anyone looking forward to maintaining it in [community]? Otherwise I'll put it back on the AUR.

3 5

[aur-general] PKGBUILD(s) Review
by Ankit R Gadiya 23 Feb '18

23 Feb '18

Hi everyone, I added two new PKGBUILD(s) today in the AUR, both are plugins for vim. Any advice, suggestions or feedback will be greatly appreciated. And if anybody would like the *-git versions of these I will be more then happy to add them as well. 1. ranger-vim: https://aur.archlinux.org/packages/ranger-vim/ 2. tcomment-vim: https://aur.archlinux.org/packages/tcomment-vim/ Ranger-vim # Maintainer: Ankit R Gadiya <arch(a)argp.in> pkgname=ranger-vim pkgver=2.0 pkgrel=1 pkgdesc="Ranger integration for vim" license=('MIT') arch=('any') url="https://github.com/francoiscabrol/ranger.vim" depends=('vim' 'ranger') groups=('vim-plugins') source=("https://github.com/francoiscabrol/${pkgname/-/.}/archive/${pkgver}.tar.gz") md5sums=('59f24462eb5c7561756a646585cd9e4c') package() { install -Dm755 "${srcdir}/${pkgname/-/.}-${pkgver}/plugin/ranger.vim" \ "${pkgdir}/usr/share/vim/vimfiles/plugin/ranger.vim" } tcomment-vim # Maintainer: Ankit R Gadiya <arch(a)argp.in> pkgname=tcomment-vim pkgver=3.08.1 pkgrel=1 pkgdesc="An extensible & universal comment vim-plugin that also handles embedded filetypes" license=('GPL3') arch=('any') url="https://github.com/tomtom/tcomment_vim" depends=('vim') groups=('vim-plugins') source=("https://github.com/tomtom/${pkgname/-/_}/archive/${pkgver}.tar.gz") md5sums=('6ea8f4ce78411efba444a0218e111219') package() { install -d "${pkgdir}/usr/share/vim/vimfiles/"{doc,plugin,autoload} install -Dm755 "${srcdir}/${pkgname/-/_}-${pkgver}/plugin/tcomment.vim" \ "${pkgdir}/usr/share/vim/vimfiles/plugin/tcomment.vim" install -Dm755 "${srcdir}/${pkgname/-/_}-${pkgver}/doc/tcomment.txt" \ "${pkgdir}/usr/share/vim/vimfiles/doc/tcomment.txt" install -Dm755 "${srcdir}/${pkgname/-/_}-${pkgver}/autoload/tcomment.vim" \ "${pkgdir}/usr/share/vim/vimfiles/autoload/tcomment.vim" } -- Ankit R Gadiya

5 14

Re: [aur-general] PKGBUILD depends() question
by Mikael Blomstrand 22 Feb '18

22 Feb '18

In the documentation FAQ there's a "Is there a package for my Operating System?" topic. From there there's a link to install instructions. Look there. Otherwise it seems like they are happy to help you if you ask them. tors 22 feb. 2018 kl. 08:09 skrev Future Trailer <alrii14344(a)gmail.com>: > i'm trying to build this project. https://github.com/Kinto/kinto > > On Thu, Feb 22, 2018 at 1:30 AM, Mikael Blomstrand <mbloms(a)kth.se> wrote: > >> Depends on the project, but upstream usually has a list of dependencies >> in the build instructions or somewhere at the development page. >> >> What package are you trying to make a PKGBUILD for specifically? >> tors 22 feb. 2018 kl. 02:06 skrev Future Trailer via aur-general < >> aur-general(a)archlinux.org>: >> >>> Thank you for the reply. And forgive me for being a newbie. I am just >>> confuse how do you get the upstream lists? >>> >>> On Sun, Feb 18, 2018 at 11:11 PM, Robin Broda via aur-general < >>> aur-general(a)archlinux.org> wrote: >>> >>> > Try to figure out what upstream lists as dependencies, & check against >>> > namcap[1] >>> > >>> > [1] - https://wiki.archlinux.org/index.php/Namcap#Dependencies >>> > >>> > - Rob >>> > >>> > >>> > On 02/19/2018 05:08 AM, Future Trailer via aur-general wrote: >>> > >>> >> When creating PKGBUILD how can I find the dependency of a package to >>> fill >>> >> the depends() array? Many thanks to your help. >>> >> >>> > >>> >> >

1 0

[aur-general] PKGBUILD depends() question
by Future Trailer 22 Feb '18

22 Feb '18

When creating PKGBUILD how can I find the dependency of a package to fill the depends() array? Many thanks to your help.

3 3

[aur-general] Issue with proper packaging
by Konstantin Gizdov 21 Feb '18

21 Feb '18

Hi, I'm having trouble making a package under the Arch Packaging Standards. The package in question is `simpletools`. The problem I'm having is that if I use `prepare()` & `build()` directives as intended, then the target `make install` does not exist when called from inside `package()` directive. I'm wondering if this is an issue because of the way `makepkg` pulls it over git and later handles it, or is it some problem with the CMake configuration in the software itself? I haven't been able to replicate this in a manual way, because obviously when run manually the configuration is persisted locally. Any comments? -- Regards, Konstantin

5 9