On Tuesday 24 June 2014 08:34:27 Alexey D. wrote:
> https://aur.archlinux.org/packages/opera-dev/
It had several votes and comments, so I've merged it into opera-developer [1].
Thank you.
BTW, I think that 'opera-dev' is more convenient package name, but according
to the upstream [2] this versi
On Monday 23 June 2014 21:32:00 Leif Warner wrote:
> https://aur.archlinux.org/packages/idris-neweffects-git/
>
> It was a separate library for the Idris language, but has since been merged
> into the language distribution proper:
> https://github.com/idris-lang/Idris-dev/tree/master/libs/effects
On Saturday 21 June 2014 16:36:07 Aaron DeVore wrote:
> I have several misnamed Python 2 packages that I need merged or renamed:
>
> parallel-python: The project is named Parallel Python, so perhaps it should
> be python2-parallel-python?
> python-couchdb: Move to python2-couchdb
> python-couchdbk
https://aur.archlinux.org/packages/opera-dev/
https://aur.archlinux.org/packages/idris-neweffects-git/
It was a separate library for the Idris language, but has since been merged
into the language distribution proper:
https://github.com/idris-lang/Idris-dev/tree/master/libs/effects
This version is obsolete.
Thanks,
-Leif
On Monday 23 June 2014 17:31:49 Storm Dragon wrote:
> As per the instructions from earlier, I made a new pypump package called
> python-pypump-git. This will replace both pypump-git and pypump2-git. I
> made it as a split package that covers both python2 and python3. I think I
> finally got all th
On Thursday 19 June 2014 21:21:24 Jeremy Audet wrote:
> Please delete ruby-reek. [1] As a tool intended primarily for use by users
> on the command line, it is badly named, and I have uploaded reek [2] to
> take its place. There are no votes or comments of worth, so there is little
> reason to merg
On Monday, June 23, 2014 22:09:33 Rikard Falkeborn wrote:
> Hello,
> Please merge xbmc-skin-transparency-svn [1] into xbmc-skin-transparency-git
> [2]. Upstream has switched to git.
>
> 1: https://aur.archlinux.org/packages/xbmc-skin-transparency-svn/
> 2: https://aur.archlinux.org/packages/xbmc-s
On Tue, Jun 24, 2014 at 8:31 AM, Storm Dragon
wrote:
> Hi,
> I'm back again lol.
> Ok, so when I made p-git depend on the package pypump2-git that I made,
> and when I installed python2-click after modifying the python-click
> PKGBUILD everything works as expected.
> When, however, I make p-git r
Hi,
I'm back again lol.
Ok, so when I made p-git depend on the package pypump2-git that I made, and
when I installed python2-click after modifying the python-click PKGBUILD
everything works as expected.
When, however, I make p-git require python2-click and python2-pypump-git it
fails to build.
Hi,
that's what I had:
source=("p::git+https://github.com/xray7224/p.git";)
Thanks
Storm
On Mon, Jun 23, 2014 at 06:00:45PM -0400, Kyle wrote:
https on Github shouldn't require a username and password. I do believe
you'll need something like git+https declared in your git source so that
makepkg w
https on Github shouldn't require a username and password. I do believe
you'll need something like git+https declared in your git source so that
makepkg will know it's a git package and how to build it.
~Kyle
http://kyle.tk/
--
"Kyle? ... She calls her cake, Kyle?"
Out of This World, season 2 epis
Hi,
As per the instructions from earlier, I made a new pypump package called
python-pypump-git. This will replace both pypump-git and pypump2-git. I made it
as a split package that covers both python2 and python3. I think I finally got
all this stuff done the right way :)
Please delete the pac
Hi,
I remember now why I was told to use git://. If I try the other way with
https:// it wants a user name and password. I guess people who are behind a
firewall that restricts git:// could edit the PKGBUILD so long as they have a
github account?
Thanks
Storm
On Mon, Jun 23, 2014 at 11:18:57PM
On 23/06, Storm Dragon wrote:
Hi,
I used to use https for all my git packages. Then, someone told me I
should use git:// lol. I searched for the email with that in it, but
there are thousands of them and I couldn't find it. Anyway, Just to
make absolutely sure, github offers https:i// or git:/
Hello,
Please merge xbmc-skin-transparency-svn [1] into xbmc-skin-transparency-git
[2]. Upstream has switched to git.
1: https://aur.archlinux.org/packages/xbmc-skin-transparency-svn/
2: https://aur.archlinux.org/packages/xbmc-skin-transparency-git/
Hi,
I used to use https for all my git packages. Then, someone told me I should use
git:// lol. I searched for the email with that in it, but there are thousands
of them and I couldn't find it. Anyway, Just to make absolutely sure, github
offers https:i// or git://. So, any time there is a git
On Sat, Jun 21, 2014 at 8:36 PM, Aaron DeVore
wrote:
> I have several misnamed Python 2 packages that I need merged or renamed:
>
> parallel-python: The project is named Parallel Python, so perhaps it should
> be python2-parallel-python?
> python-couchdb: Move to python2-couchdb
> python-couchdbk
bump
> Does this PKGBUILD look ok?
If pypump is a tool that users interact with directly (e.g. through the
command line or a graphical program), then sure, that looks fine. However,
if pypump is a library, then the package should be named python-pypump-git.
I've had a quick look at the documentation fo
https://aur.archlinux.org/packages/weka/
It should use the latest stable version 3.6.11, instead of current 3.7
branch.
Current weka should be renamed to something like weka-devel. Although a
previous maintainer states that " The difference between stable and
development upstream is pointless,
On 23/06, Storm Dragon wrote:
Hi,
I went about this the wrong way the first time around. Please delete
pypump2-git. pypump-git handles both versions.
thanks, and sorry for the extra file
Storm
When the pypump2-git package is removed you probably want to turn it
into a split PKGBUILD so that i
On 23/06, Storm Dragon wrote:
Hi,
Sometimes this python stuff is confusing. I built the python-click package by
hand after removing the python3 options. It built and installed and not p isn't
complaining about click any more.
So, I guess I'm just not requesting the right package be installed or
On 22/06, Storm Dragon wrote:
Hi,
The pypump docs say it works for all versions of python, 2.7, through 3.4 I
think. I made the PKGBUILD using the python3 dependancy because I figure that
is what most people will have by default. Does this PKGBUILD look ok?
Thanks
Storm
Hey,
It's mostly fine
=== 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
* 0 fully signed off packages
* 1 package missing signoffs
* 1 package older than 14 days
(
25 matches
Mail list logo
