Re: [aur-general] Update notifications

2015-06-22 Thread Jiachen Yang
Might be irreverent to this topic, but we ArchlinuxCN community have this tool `nvchecker`[1] that can check updates of version numbers for packages. It currently have support for pulling version infomation from aur4/aur, github, pypi, and many other upsteam sources. It records the current versio

Re: [aur-general] Update notifications

2015-06-22 Thread Eli Schwartz
On Mon, Jun 22, 2015 at 9:13 PM, Justin Dray wrote: > Because that would only work for the current version, and back one, this > way you could see the relevant change happening after an issue is reported > and such. It seems like a much easier way to view the differences to me at > least. > > - J

Re: [aur-general] Update notifications

2015-06-22 Thread Justin Dray
Why not just check the last updated date? -- Eli Schwartz Because that would only work for the current version, and back one, this way you could see the relevant change happening after an issue is reported and such. It seems like a much easier way to view the differences to me at least. - Just

Re: [aur-general] Update notifications

2015-06-22 Thread Eli Schwartz
On Mon, Jun 22, 2015 at 7:12 PM, Justin Dray wrote: > Hi, > > I was thinking it could be useful to show in comments when a new version is > pushed by the maintainer of a package; just a line break and maybe v1 -> v2 > or the git commit message or something. It would be easier to make sense of > c

[aur-general] Update notifications

2015-06-22 Thread Justin Dray
Hi, I was thinking it could be useful to show in comments when a new version is pushed by the maintainer of a package; just a line break and maybe v1 -> v2 or the git commit message or something. It would be easier to make sense of comments on many of the packages I've seen and allow us to see if

Re: [aur-general] [AUR4] Single binary package for different architectures

2015-06-22 Thread Eli Schwartz
On Mon, Jun 22, 2015 at 4:46 PM, Bruno Pagani wrote: > I’m not sure to understand you. How would you package this one for > instance: > > https://aur4.archlinux.org/packages/chromium-pepper-flash-standalone/ > > ? > > Bruno > See this diff: http://pastebin.com/EggVuYpH -- Eli Schwartz

Re: [aur-general] Need help with some patching for my package (gcc44-multilib)

2015-06-22 Thread Giovanni Santini
Il 21/06/2015 21:30, carstene1ns ha scritto: tl;dr: Here[1] is a working patch. ... Hope this helps. best regards, carstene1ns It really helped! The build went fine for x86_64, now I'm testing i686 build. Thank you very much! I'll put proper credits in the patch :) -- Giovanni Santini My

Re: [aur-general] [AUR4] Single binary package for different architectures

2015-06-22 Thread Bruno Pagani
Le 14/06/2015 16:31, Johannes Löthberg a écrit : > On 14/06, Johannes Löthberg wrote: >> On 14/06, Reventlov wrote: In which way is it cleaner and more structured? It's a bash hack instead of actually using properly structured and supported features. >>> >>> Please take this not-a-bu

Re: [aur-general] Will AUR3 PKGBUILDs be kept somewhere?

2015-06-22 Thread Ralf Mardorf
On Mon, 22 Jun 2015 21:17:35 +0200, Giovanni Santini wrote: >There should already be a git repository with all AUR PKGBUILDs, if >I'm not wrong. https://aur.archlinux.org/packages/aur-git/

Re: [aur-general] Will AUR3 PKGBUILDs be kept somewhere?

2015-06-22 Thread Marcel Korpel
* Giovanni Santini (Mon, 22 Jun 2015 21:17:35 +0200): > As in title, I just want to know if the PKGBUILDs of AUR3 will be > deleted or kept somewhere. Yes, there will be a read-only site for AUR3 packages. > There should already be a git repository with all AUR PKGBUILDs, if > I'm not wrong. h

[aur-general] Will AUR3 PKGBUILDs be kept somewhere?

2015-06-22 Thread Giovanni Santini
Hello everybody, As in title, I just want to know if the PKGBUILDs of AUR3 will be deleted or kept somewhere. There should already be a git repository with all AUR PKGBUILDs, if I'm not wrong. I'm asking so in case I miss some old packages I can update them and push them to AUR4 :) -- Giovann

[aur-general] [AURv4] Shallow HTTPS clones do not work

2015-06-22 Thread Chris Warrick
I’m trying to create a shallow clone of an AURv4 repository with `--depth 1`, but I can’t get it to work. $ git clone https://aur4.archlinux.org/pkgbuilder.git/ Cloning into 'pkgbuilder'... remote: Counting objects: 23, done. remote: Compressing objects: 100% (17/17), done. remote: Total 23 (delta

[aur-general] Package Naming Of libvterm

2015-06-22 Thread Mark Weiman
I think that is reasonable, I will create a new package on the aur4 called libvterm-vwm and will open a merge request and let the other package be named libvterm. Mark Weiman (markzz) signature.asc Description: This is a digitally signed message part

Re: [aur-general] Package Naming Of libvterm

2015-06-22 Thread Johannes Dewender
Am 22.06.2015 um 16:06 schrieb Johannes Dewender: > http://www.leonerd.org.uk/code/libvterm/ by Paul "LeoNerd" Evans > is the "original" libvterm from 2007 [1] (Copyright 2008 in LICENSE). > There is a Launchpad project [2] and also a GitHub mirror [2] as part of > the NeoVim project. > The last co

Re: [aur-general] Package Naming Of libvterm

2015-06-22 Thread Johannes Dewender
Am 22.06.2015 um 15:32 schrieb Mark Weiman: > I was contacted by maintainer fwalch and he wants to submit a package > that is named libvterm and is from this site ( > http://www.leonerd.org.uk/code/libvterm/) and is concerned with how he > should name it and how my package libvterm ( > https://aur4

[aur-general] Package Naming Of libvterm

2015-06-22 Thread Mark Weiman
I was contacted by maintainer fwalch and he wants to submit a package that is named libvterm and is from this site ( http://www.leonerd.org.uk/code/libvterm/) and is concerned with how he should name it and how my package libvterm ( https://aur4.archlinux.org/packages/libvterm/) should be named.

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

2015-06-22 Thread Arch Website Notification
=== Signoff report for [community-testing] === https://www.archlinux.org/packages/signoffs/ There are currently: * 0 new packages in last 24 hours * 0 known bad packages * 0 packages not accepting signoffs * 2 fully signed off packages * 175 packages missing signoffs * 4 packages older than 14 day