Re: [aur-general] pkgbuild - suggestion

Sometimes there may be a new version out, but the maintainer needs to test and make sure it's working as expected. It may need a patch to work correctly, or it may have a major flaw and every other distro is also avoiding updating to the latest version. The flagging system, I feel at least, is

Re: [aur-general] Continuous integration of AUR packages

I was using the chroot tools for a year and a half or so before that, but had some issues occasionally with things like updating it, or using package caches inside the chroot, or other various things. I do still have the shell script I used at the time, it was called by jenkins and cloned a chroot

Re: [aur-general] Continuous integration of AUR packages

On Thu, 18 Feb 2016 12:51:19 +0100 Baptiste Jonglez wrote: > Hi, > > The scripts in devtools [1] look like they should work just fine to > automate these kind of builds. After all, they are used to build the > official Archlinux packages. > > However, I found that

Re: [aur-general] Continuous integration of AUR packages

Hi, On Thu, Feb 18, 2016 at 12:25:53PM +, Justin Dray wrote: > I actually have a Jenkins setup for my packages that does almost exactly > that, I have a job generator build that I give an AUR package name to and > that's all the config for new packages, and it builds them in a docker >

Re: [aur-general] pkgbuild - suggestion

automatic notification sending is i believe a way to hell (10th+ notification for the same package would only make maintainer more angry). the idea is to only show it (when asked to) to user. then it's up to him/her to either notify maintainer, make a patch and do the update him/herself or

Re: [aur-general] Continuous integration of AUR packages

I actually have a Jenkins setup for my packages that does almost exactly that, I have a job generator build that I give an AUR package name to and that's all the config for new packages, and it builds them in a docker container. You can obviously set up dependencies between the jobs to build in

[aur-general] Continuous integration of AUR packages

Hi, I would like to run some kind of continuous integration of my AUR packages. The goal is to know when a package I maintain fails to build because either: 1/ its dependencies have been updated (new API, new incompatible version of GCC, ...) 2/ for -git packages, changes made upstream

Re: [aur-general] pkgbuild - suggestion

i think it is the job of a maintainer to keep the pkgbuild updated (while buildable at the same time). with keeping an eye on new upstream releases.. not sure. why the "notify" button on aur webpage exists in the first place. and then you also have pkgbuilds that lost their maintainers,

[aur-general] Signoff report for [community-testing]

=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 1 new package in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 0 fully signed off packages * 8 packages missing signoffs * 4 packages older than 14 days