Package Details: python2-yenc 0.4.0-3

Git Clone URL: https://aur.archlinux.org/python2-yenc.git (read-only)
Package Base: python2-yenc
Description: yEnc encoding/decoding module for python2
Upstream URL: http://www.golug.it/yenc.html
Licenses: GPL
Conflicts: python-yenc
Replaces: python-yenc
Submitter: Lucky
Maintainer: cdemoulins
Last Packager: cdemoulins
Votes: 107
Popularity: 1.508458
First Submitted: 2011-08-13 17:24
Last Updated: 2015-07-02 09:34

Dependencies (1)

Required by (5)

Sources (1)

Latest Comments

cdemoulins commented on 2015-07-04 21:20

All is fine for me. Maybe a temporary issue with aur4.

binhex commented on 2015-06-30 08:36

this is broken on aur4, cannot download snapshot and attempting to view pkgbuild returns "Invalid branch: python2-yenc"

marker5a commented on 2014-07-11 23:19

@cdemoulins: I appreciate the quick feedback. So, I looked through the makepkg.conf file and found the culprit, most likely as you suspected.

I changed the -march=x86_64 for CFLAGS and for CXXFLAGS to -march=x86-64 and that fixed everything!

Thanks again and cheers amigo!

marker5a commented on 2014-07-11 23:18

@cdemoulins: I appreciate the quick feedback. So, I looked through the makepkg.conf file and found the culprit, most likely as you suspected.

I changed the -march=x86-64 for CFLAGS and for CXXFLAGS to -march=x86-64 and that fixed everything!

Thanks again and cheers amigo!

cdemoulins commented on 2014-07-11 16:45

Can you check (or post) your makepkg.conf ?

marker5a commented on 2014-07-11 11:49

I have a fresh Arch x86_64 install and tried installing sabnzbd (ive never previously had issues installing sabnzbd)

Upon running makepkg, I get an error right off of the bat

gcc -pthread -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -march=x86_64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c src/_yenc.c -o build/temp.linux-x86_64-2.7/src/_yenc.o -O2 -g
src/_yenc.c:1:0: error: bad value (x86_64) for -march= switch
I am able to manually call gcc and remove the -march=x86_64 flag and it compiles fine, but I cannot find where this flag is derived from in the compile instruction... is this inherent to my system or is the instruction provided by this package? Kind of confused here...

marker5a commented on 2014-07-11 11:48

I have a fresh Arch x86_64 install and tried installing sabnzbd (ive never previously had issues installing sabnzbd)

Upon running makepkg, I get an error right off of the bat

gcc -pthread -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -march=x86_64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c src/_yenc.c -o build/temp.linux-x86_64-2.7/src/_yenc.o -O2 -g

I am able to manually call gcc and remove the -march=x86_64 flag and it compiles fine, but I cannot find where this flag is derived from in the compile instruction... is this inherent to my system or is the instruction provided by this package? Kind of confused here...
src/_yenc.c:1:0: error: bad value (x86_64) for -march= switch

BlackIkeEagle commented on 2013-04-28 08:32

@tehsu as long as arm is not a supported architecture you might need to ticker around with packages from aur

gcc is for sure not needed since you must have base-devel installed (which contains gcc) to use AUR

tehsu commented on 2013-04-28 05:50

when trying to install sabnzbd from aur, this fails since the arch does not include arm and gcc needs to be a depend otherwise new systems without gcc fail. Installing gcc and adding arm fixed it for my install.

fjim commented on 2012-03-24 20:40

@BlackIkeEagle I think you meant "got compiled from source code". True, I was mistaken because it works flawlessly (after fixing the arch in the PKGBUILD) under ARM architecture, but since _yenc.so is compiled from C code, the resulting package is architecture dependent.

BlackIkeEagle commented on 2012-03-04 09:10

@fjim: sorry that is not correct, python libs can be architecture dependent since they may contain native libs

here you have such a case, checkout the built package, there you will find "usr/lib/python2.7/site-packages/_yenc.so" which got compiled from native code, hence arch=('i686' 'x86_64')

fjim commented on 2012-03-04 07:55

Architecture should be any:

arch=(any)

Python code is architecture independent.

cdemoulins commented on 2011-12-20 20:08

fixed

Anonymous comment on 2011-12-18 04:02

0.4.0 fails checksum, yaourt exits with error.

cdemoulins commented on 2011-09-30 12:35

Thanks for the notification, i just update the package.

BlackIkeEagle commented on 2011-09-30 12:08

https://bitbucket.org/dual75/yenc/downloads
0.4.0 is out

pkgbuild sample https://github.com/BlackIkeEagle/herecura/tree/master/herecura-stable/python2-yenc

lfleischer commented on 2011-09-21 11:22

Merged python-yenc into python2-yenc.

cdemoulins commented on 2011-09-14 08:01

Sorry i miss that, i fix it immediately.

Revelation60 commented on 2011-09-14 07:12

Could you please add a conflict for python-yenc for now, since it currently is the same package.

cdemoulins commented on 2011-08-29 12:15

@lucky
thanks, i just upload the package python2-yenc

I will ask a deletion of this package in 2 week.

Lucky commented on 2011-08-14 09:15

Lucky commented on 2011-08-13 12:49

@cdemoulins
rename python-yenc to python2-yenc, because it's an python2 module.
I update your PKGBUILD and use the sources of the python-yenc developer, maybe you merge something.

http://hydra.lky.cc/lucky/pkgbuild_sources/python2-yenc-0.3-1.src.tar.gz

cdemoulins commented on 2011-07-16 17:23

Python yenc module was developed by the developers of hellanzb that is abandoned now so i don't think there will be an update soon.

Anonymous comment on 2011-07-14 14:26

Will this pkgbuild get updated for python3?

zatricky commented on 2010-10-28 11:38

change python to python2 in both the depends= line as well as in the build{} section

cb474 commented on 2010-10-21 07:31

Does the pkgbuild need to be upgraded to deal with the change to python 3?

@vedix95, I edited the pkgbuild manually, and change "python" to "python2" in the depends line. Then it built okay for me. I'm not sure this was the right or only thing needed, but things like that have helped with other packages. I'm still unable to get sabnzbd to work right after the change to python 3, though.

Anonymous comment on 2010-10-20 22:36

Hi had problem for the compiling of this package for use with sabnzbd can you help me ?

Here my paste bin error.
http://aur.pastebin.com/cpKiHG7B

Thanx