[SOLVED] Error with PKGBUILD for package hash-identifier

Hi,
I tried to install the package hash-identifier.
While running makepkg -s, there is an error:
==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.
I guess this is due to the New Line character at line 17 of the PKGBUILD:
sed -e 's|
||g' -i Hash_ID_v${pkgver}.py
So I remove it, but then I get this other error and I don't know what to do with it:
==> Extracting sources...
==> Starting prepare()...
sed: -e expression #1, char 0: no previous regular expression
==> ERROR: A failure occurred in prepare().
Aborting...
Last edited by PâtéDeCerf (2015-03-11 08:18:34)

Thanks for your reply. I'm not familiar with package build syntax nor python, so I don't understand everything you wrote.
It would be good if you could explain more clearly though.
By applying the change you propose, I was able to build the package and install it.
NB: To run the program, type from the command-line :
$ hash-id
...and not simply "hash-identifier"
Last edited by PâtéDeCerf (2015-03-11 08:21:10)

Similar Messages

[solved] new abs PKGBUILD for package kernel26...old kernel?

I was looking into the new PKGBUILD in the /var/abs/core/kernel26 folder, as I wanted to update my custom kernel. I was editing the new PKGBUILD when I saw something weird...references to kernel.org files and archlinux.org patch seems to be same as the 2.6.37 version. Is _basekernel value not updated? Am I wrong?
Take a look:
new PKGBUILD (I copied only relevant lines):
_basekernel=2.6.37
pkgver=${_basekernel}
pkgrel=6
_patchname="patch-${pkgver}-4-ARCH"
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$_basekernel.tar.bz2
ftp://ftp.archlinux.org/other/kernel26/${_patchname}.bz2
now...these is exactly the same as PKGBUILD for 2.6.37. But the new files are:
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.37.1.tar.bz2
ftp://ftp.archlinux.org/other/kernel26/patch-2.6.37.1-1-ARCH.bz2
If I am right, someone has to update variable values...
TIA
Gemon
Last edited by gemon (2011-02-21 22:17:23)

well...I had time to check so...this is the content for the PKGBUILD after I run abs yesterday (pasted only relevant lines):
# $Id: PKGBUILD 109724 2011-02-12 08:01:06Z tpowa $
pkgbase="kernel26"
pkgname=('kernel26' 'kernel26-headers' 'kernel26-docs') # Build stock -ARCH kernel
_kernelname=${pkgname#kernel26}
_basekernel=2.6.37
pkgver=${_basekernel}
pkgrel=6
_patchname="patch-${pkgver}-4-ARCH"
this is the one I run tonight...looks updated now
# $Id: PKGBUILD 110322 2011-02-18 20:13:49Z tpowa $
pkgbase="kernel26"
pkgname=('kernel26' 'kernel26-headers' 'kernel26-docs') # Build stock -ARCH kernel
_kernelname=${pkgname#kernel26}
_basekernel=2.6.37
pkgver=${_basekernel}.1
pkgrel=1
_patchname="patch-${pkgver}-${pkgrel}-ARCH"
now patch filename and kernel sources correctly resolve to the latest ones.
but believe me, right after I had the 2.6.37.1-arch kernel, the abs PKGBUILD was outdated...probably it is updated after kernel package is released. doesn't matter
all in all...now it's ok
Gemon

[SOLVED] Error with Wickr deb package

Hi people, I was trying to running wickr on Arch Linux. (I am under Gnome), I used debtap utility, attempted to convert wickr deb package to work with pacman but failed with this dependency:
warning: cannot resolve "libavutil52|libavutil54", a dependency of "wickr"
:: The following package cannot be upgraded due to unresolvable dependencies:
error: failed to prepare transaction (could not satisfy dependencies)
:: wickr: requires libavutil52|libavutil54
I am pretty sure I have already got the libavutil-52 installed and does not help. I even managed to convert libavutil54 from debian and installed but still no progress.
Any help? thx in advance.
Last edited by sakuya16 (2015-05-06 11:06:50)

Hi sakuya16,
the | character does not work as logical or inside the PKGBUILD, depends is an array of strings separated by withe spaces. Also you must specify only one version of libavutil and its name is libavutil-52 and not libavutil52. For more information read the wiki https://wiki.archlinux.org/index.php/PKGBUILD#depends
--edit:
Yeah, tomk is right, try to see if it works with the current libavutil.so.54 first.
Last edited by mauritiusdadd (2015-05-06 10:42:02)

Cant download itunes, because ' there is an error with windows installer package' please help?

cant download itunes, because ' there is an error with windows installer package' please help?

I am getting the same message when I try to install the latest version of iTunes, I am running on Windows Vista Home Premium. I have tried so many different things to try to correct this and have now completly unistalled it from my laptop..... Now I have no iTunes what-so-ever on it and still can't install it. I found an older versin of iTunes and it installed without any problems, but I can't access it because my library was created on a newer version! Talk about frustrated..... WE NEED HELP!!!!!

[Solved]Error with installing package: /usr/lib64 exists in filesystem

So i know there are other posts about this and i have read them and I have also read the wiki https://wiki.archlinux.org/index.php/De … _in_.2Flib and also this forum post https://bbs.archlinux.org/viewtopic.php?id=156942
the error i get when trying to install a package from the AUR
error: failed to commit transaction (conflicting files)
hp-health: /usr/lib64 exists in filesystem
Errors occurred, no packages were upgraded.
I tried to find who owned the files/package in the /lib by the following commands
$ grep '^lib/' /var/lib/pacman/local/*/files
$ find /lib -exec pacman -Qo -- {} +
the output was
/lib is owned by filesystem 2015.02-1
Im confused what to do at this point as the wiki that I linked above says
If any package apart from glibc is listed as owning a file, that package needs to be updated to install its files in /usr/lib
Last edited by PigsInSpace (2015-03-01 02:25:24)

You are following directions for a file conflict with /lib for a very specific one-time manual intervention, but you don't have that file conflict according to the error message you posted and it is not for that intervention. See this instead: https://wiki.archlinux.org/index.php/Pa … 9.22_error then report the error on the aur page for that package.
This fixes it:
package() {
cd "$srcdir"
+ mv usr/lib64 usr/lib
cp -a opt usr var "$pkgdir"

[SOLVED] Error with the php5 module for apache

Hi!
I've installed Apache 2.0.55-1 and PHP5 5.1.4-4. When I try to run the apache server it fails. Then I do httpd -k start and I get:
Syntax error on line 262 of /etc/httpd/conf/httpd.conf:
API module structure `php5_module' in file /usr/lib/apache/libphp5.so is garbled - perhaps this is not an Apache module DSO?
The file libphp5 exists, but seems corrupted.
See you
NeOnsKuLL

That version of the package has been built with apache 2.2.x. Be sure to use that version of apache too, as 2.0 won't work with that specific package.

Help with PKGBUILD for nvidia driver cards

Hello, I'm trying to make a PKGBUILD for the new geforce beta driver for the kernel26-mm kernel, geforce-utils went just fine, but the the geforce package was more tricky, here's the PKGBUILD:
pkgname=geforce-mm
pkgver=173.08
_kernver='2.6.25-mm'
pkgrel=1
pkgdesc="NVIDIA drivers for kernel26mm."
arch=(i686 x86_64)
[ "$CARCH" = "i686" ] && ARCH=x86
[ "$CARCH" = "x86_64" ] && ARCH=x86_64
url="http://www.nvidia.com/"
depends=('kernel26mm' 'geforce-utils')
install=geforce.install
source=(http://us.download.nvidia.com/XFree86/Linux-$ARCH/${pkgver}/NVIDIA-Linux-$ARCH-${pkgver}-pkg1.run)
md5sums=()
[ "$CARCH" = "x86_64" ] && md5sums=()
build()
# Extract
cd $startdir/src/
sh NVIDIA-Linux-$ARCH-${pkgver}-pkg1.run --extract-only
cd NVIDIA-Linux-$ARCH-${pkgver}-pkg1
cd usr/src/nv/
ln -s Makefile.kbuild Makefile
make SYSSRC=/lib/modules/${_kernver}/build module || return 1
# install kernel module
mkdir -p $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
install -m644 nvidia.ko $startdir/pkg/lib/modules/${_kernver}/kernel/drivers/video/
sed -i -e "s/KERNEL_VERSION='.*'/KERNEL_VERSION='${_kernver}'/" $startdir/*.install
Output when running it:
[roberth@Magda geforce-mm]$ makepkg
==> Making package: geforce-mm 173.08-1 (Mon Apr 14 22:44:41 CEST 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
-> Downloading NVIDIA-Linux-x86-173.08-pkg1.run...
--2008-04-14 22:44:41-- http://us.download.nvidia.com/XFree86/Linux-x86/173.08/NVIDIA-Linux-x86-173.08-pkg1.run
Resolving us.download.nvidia.com... 193.213.121.82, 193.213.121.74
Connecting to us.download.nvidia.com|193.213.121.82|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18958181 (18M) [application/octet-stream]
Saving to: `NVIDIA-Linux-x86-173.08-pkg1.run'
100%[===========================================================================================================================================================================================>] 18,958,181 710K/s in 26s
2008-04-14 22:45:07 (720 KB/s) - `NVIDIA-Linux-x86-173.08-pkg1.run' saved [18958181/18958181]
==> WARNING: Integrity checks (md5) are missing or incomplete.
==> Extracting Sources...
==> Entering fakeroot environment...
==> Starting build()...
Creating directory NVIDIA-Linux-x86-173.08-pkg1
Verifying archive integrity... OK
Uncompressing NVIDIA Accelerated Graphics Driver for Linux-x86 173.08...............................................................................................................................................................................................................................................................................................
NVIDIA: calling KBUILD...
make CC=cc KBUILD_VERBOSE=1 -C /lib/modules/2.6.25-mm/build SUBDIRS=/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv modules
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/.tmp_versions ; rm -f /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/.tmp_versions/*
make -f scripts/Makefile.build obj=/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv
cc -Wp,-MD,/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/.nv.o.d -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.3.0/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -O2 -fno-stack-protector -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=i686 -mtune=generic -ffreestanding -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -Iinclude/asm-x86/mach-default -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wno-pointer-sign -I/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wparentheses -Wpointer-arith -Wno-multichar -Werror -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"173.08\" -UDEBUG -U_DEBUG -DNDEBUG -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(nv)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.o /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c
In file included from include/linux/list.h:8,
from include/linux/preempt.h:11,
from include/linux/spinlock.h:49,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/timex.h:57,
from include/linux/sched.h:54,
from include/linux/utsname.h:35,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv-linux.h:19,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:14:
include/linux/prefetch.h: In function 'prefetch_range':
include/linux/prefetch.h:57: warning: pointer of type 'void *' used in arithmetic
In file included from include/linux/gfp.h:4,
from include/linux/slab.h:14,
from include/linux/percpu.h:5,
from include/linux/rcupdate.h:41,
from include/linux/pid.h:4,
from include/linux/sched.h:74,
from include/linux/utsname.h:35,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv-linux.h:19,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:14:
include/linux/mmzone.h: In function 'first_zones_zonelist':
include/linux/mmzone.h:778: warning: comparison between signed and unsigned
include/linux/mmzone.h:781: warning: comparison between signed and unsigned
include/linux/mmzone.h: In function 'next_zones_zonelist':
include/linux/mmzone.h:798: warning: comparison between signed and unsigned
include/linux/mmzone.h:801: warning: comparison between signed and unsigned
In file included from include/asm/dma-mapping_32.h:5,
from include/asm/dma-mapping.h:2,
from include/linux/dma-mapping.h:52,
from include/asm-generic/pci-dma-compat.h:7,
from include/asm/pci.h:90,
from include/linux/pci.h:937,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv-linux.h:86,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:14:
include/linux/scatterlist.h: In function 'sg_virt':
include/linux/scatterlist.h:199: warning: pointer of type 'void *' used in arithmetic
In file included from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv-linux.h:109,
from /home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:14:
include/linux/highmem.h: In function 'zero_user_segments':
include/linux/highmem.h:134: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:134: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:134: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:134: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:137: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:137: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:137: warning: pointer of type 'void *' used in arithmetic
include/linux/highmem.h:137: warning: pointer of type 'void *' used in arithmetic
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c: In function 'nv_kern_vma_nopage':
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:1846: error: 'NOPAGE_SIGBUS' undeclared (first use in this function)
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:1846: error: (Each undeclared identifier is reported only once
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:1846: error: for each function it appears in.)
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c: At top level:
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:1853: error: unknown field 'nopage' specified in initializer
/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.c:1853: warning: initialization from incompatible pointer type
make[3]: *** [/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv/nv.o] Error 1
make[2]: *** [_module_/home/roberth/pkg/geforce-mm/src/NVIDIA-Linux-x86-173.08-pkg1/usr/src/nv] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
==> ERROR: Build Failed.
Aborting...
Anybody have a clue?

It seems I was wrong! I found a patch on the nvidia forums which actually makes it works
I don't know if it will work for you, or how safe it is, but I guess it is worth a shot.
The patch:
--- os-agp.c.25 2008-04-02 01:34:49.000000000 -0400
+++ os-agp.c 2008-04-02 01:39:00.000000000 -0400
@@ -293,7 +293,7 @@
nv_pte_t *page_ptr = at->page_table[i];
- page_ptr->phys_addr = (ptr->memory[i] & PAGE_MASK);
+ page_ptr->phys_addr = (ptr->memory[i]);
page_ptr->virt_addr = (unsigned long) __va(page_ptr->phys_addr);
page_ptr->dma_addr = page_ptr->phys_addr;
--- nv.c.25 2008-03-15 22:00:46.000000000 -0400
+++ nv.c 2008-04-02 01:31:46.000000000 -0400
@@ -613,7 +613,7 @@
nv_state_t *nv;
nv_linux_state_t *nvl;
- proc_nvidia = create_proc_entry("nvidia", d_flags, proc_root_driver);
+ proc_nvidia = create_proc_entry("driver/nvidia", d_flags, NULL);
if (!proc_nvidia)
goto failed;
@@ -1811,6 +1811,19 @@
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 24))
+int nv_kern_vma_fault(struct vm_area_struct *vma, struct vm_fault *vmf)
+{
+struct page *page;
+
+ page = pfn_to_page(vma->vm_pgoff);
+ if (!page)
+ return VM_FAULT_SIGBUS;
+ get_page(page);
+ vmf->page = page;
+ return 0;
+}
+#else
struct page *nv_kern_vma_nopage(
struct vm_area_struct *vma,
unsigned long address,
@@ -1832,11 +1845,16 @@
return NOPAGE_SIGBUS;
#endif
+#endif /* 2.6.24 */
struct vm_operations_struct nv_vm_ops = {
.open = nv_kern_vma_open,
.close = nv_kern_vma_release, /* "close" */
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 24))
+ .fault = nv_kern_vma_fault,
+#else
.nopage = nv_kern_vma_nopage,
+#endif
static nv_file_private_t *

ALSA errors with PKGBUILD

I have a fancy Echo Audio pcmcia sound card (Indigo IO). The Indigo IO module is built into the latest versions of the alsa-driver package. I set up a PKGBUILD to configure the Indigo IO module. Makepkg runs successfully. When I use pacman to install ALSA, I get the following:
[root@bobarch1 alsa-driver]# pacman -U alsa-driver-*.pkg.tar.gz
loading package data... done.
checking for file conflicts...
error: the following file conflicts were found:
alsa-driver: /lib/modules/2.6.10-ARCH/modules.alias: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.ccwmap: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.dep: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.ieee1394map: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.inputmap: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.isapnpmap: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.pcimap: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.symbols: exists in filesystem
alsa-driver: /lib/modules/2.6.10-ARCH/modules.usbmap: exists in filesystem
errors occurred, no packages were upgraded.
I'd appreciate any insights into how to proceed. The Intel sound hardware on my Thinkpad notebook is non-functional, and I'd like to have some way to play music.
Bob Pisciotta

Thanks, Snowman. This worked great. Now my issue is that having installed the new build of ALSA it's still not finding the soundcard: snd-indigoio. I'll do a little research into this issue. Had the Echo/Indigo soundcard working with a Slackware installation, but I just had to try Arch on the machine. I really like Arch--a lot--and would like to get my sound working. Bob
Snowman wrote:
This error happened because your package contains files already on the system (they belong to the kernel package). In your PKGBUILD, after the make install line, put a line to remove them: rm $startdir/pkg/lib/modules/2.6.10-ARCH/modules.*
This will remove the file conflicts.

Semantic Error with ProC for a granted package

Hi,
we are now switching to Oracle 11gR2, and I encounter an error when precompiling our ProC code. The error is PLS-S-00201, identifier 'XXXXXX' must be declared.
Let me explain what I do.
The identifier in question is a package. The owner of this package is a schema user USER1. In the same database instance, I have an other schema user, USER2.
USER1 granted EXECUTE to USER2. And a SYNONYM has been created for USER2. So now, connecting with USER2 with SqlDeveloper, I can see the synonym from the granted package.
When precompiling with ProC, I use the SQLCHECK=SEMANTICS USERID=USER2/PWD@INSTANCE.
Other flags are : DBMS=V8 CHAR_MAP=VARCHAR2 ireclen=80 oreclen=80 parse=NONE select_error=NO maxliteral=1024 maxopencursors=10 ltype=NONE release_cursor=YES
This is when I get the error. I must connect with USER2, because it is the main schema, and only a package is in another schema. But if I change the USERID for ProC to USER1, and precompile only the part of the code that need USER1, it works (same package here, but in the owner schema). It seems there is a problem with the GRANT.
Does anyone have any idea ?
Thank you.
Jessy Saint.

Of course, it was the ovious. The grant was removed from someone else, testing something else. The problem with big dev teams using the same databases....
Thanks again.

No way to view changes with PKGBUILD for community packages

I noticed that you can't view PKGBUILD changes for new community packages. I thought we move community to svn so it should be viewable.
Example:
http://repos.archlinux.org/viewvc.cgi/c … nity-i686/
Just my 2 cents.

Everything that is need for the transition is still a work in progress... This a known issues. As a workaround you can use ABS or check out the SVN for the packages you are interested in.

[SOLVED] Satisfying a dependency for package X with my package Y

Hi,
let's assume there are packages which depend on package X. Now I created a package Y in aur which is a slightly modified version of package X (some other configure options) but will also work with every package which depends on package X.
Now I used
conflicts=('X')
so my package can't be installed together with X because they have the same binaries, libs,... in the same places. But how can I make sure that the packages depending on X will be satisfied with package Y and don't want X to be installed? Is
provides=('X')
the correct thing?
greetings
Last edited by Rorschach (2009-05-25 10:24:09)

Yes, provides=('X') is what you want. You might want provides=("X=version") to satisfy versioned dependencies.

[SOLVED] errors with fdisk and cryptsetup; is my drive going bad?

I'm having issues with re-formatting an external hard drive using dm-crypt. It was previously formatted with TrueCrypt/NTFS, which I used as a shared backup drive between Windows and Arch. At some point, it stopped being able to mount, which I attributed to allowing Windows to "fix" it after improper dismount (e.g. a hard kill).
I decided to re-format with ext4 and only use it from Arch, but now I'm wondering if I may have a hardware issue with the drive. I've tried a lot more (like going through the full zero write after mounting the drive as a temporary dm-crypt device), but here's the condensed version to illustrate the problem.
system info
This is on a fresh boot. Just adding that as I've had issues with kernel modules after updating if a new kernel comes through. A fresh boot removes that potential issue.
$ uname -a
Linux arch_840 4.0.3-1-ARCH #1 SMP PREEMPT Wed May 13 15:38:47 CEST 2015 x86_64 GNU/Linux
$ lsmod | grep dm_
dm_crypt 28672 2
dm_mod 98304 5 dm_crypt
$ lsmod |grep xts
xts 16384 2 serpent_sse2_x86_64,twofish_x86_64_3way
gf128mul 16384 2 lrw,xts
smartctl status
Figured I should check the drive. There's a lot of old age and pre-fail warnings, but this post would seem to suggest I'm okay?
# smartctl -A /dev/sdb
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-4.0.3-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0
2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0
3 Spin_Up_Time 0x0023 090 089 025 Pre-fail Always - 3330
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 703
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 3707
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 104
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 734
191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 064 053 000 Old_age Always - 24 (Min/Max 16/47)
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 104
225 Load_Cycle_Count 0x0032 079 079 000 Old_age Always - 214068
Disk info, delete existing partition, new MBR, create new partition
# fdisk /dev/sdb
Welcome to fdisk (util-linux 2.26.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x76d37b6d
Device Boot Start End Sectors Size Id Type
/dev/sdb1 63 976768064 976768002 465.8G 83 Linux
Command (m for help): d
Selected partition 1
Partition 1 has been deleted.
Command (m for help): o
Created a new DOS disklabel with disk identifier 0x2cd60f13.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-976773167, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-976773167, default 976773167):
Created a new partition 1 of type 'Linux' and of size 465.8 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
trying to format with cryptsetup
I had a bunch of custom options, but other Arch posts suggested just trying the default, which is what I've done here. It fails with the same error as when I try to pass a cipher, key size, etc. ("Command failed with code 5: IO error while encrypting keyslot.").
# truecrypt -v --debug luksFormat /dev/sdb1
bash: truecrypt: command not found
[root@arch_840 jwhendy]# cryptsetup -v --debug luksFormat /dev/sdb1
# cryptsetup 1.6.6 processing "cryptsetup -v --debug luksFormat /dev/sdb1"
# Running command luksFormat.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
WARNING!
========
This will overwrite data on /dev/sdb1 irrevocably.
Are you sure? (Type uppercase yes): YES
# Allocating crypt device /dev/sdb1 context.
# Trying to open and read device /dev/sdb1.
# Initialising device-mapper backend library.
# Timeout set to 0 miliseconds.
# Iteration time set to 1000 miliseconds.
# Interactive passphrase entry requested.
Enter passphrase:
Verify passphrase:
# Formatting device /dev/sdb1 as type LUKS1.
# Crypto backend (gcrypt 1.6.3) initialized.
# Detected kernel Linux 4.0.3-1-ARCH x86_64.
# Topology: IO (512/0), offset = 0; Required alignment is 1048576 bytes.
# Checking if cipher aes-xts-plain64 is usable.
# Using userspace crypto wrapper to access keyslot area.
# Generating LUKS header version 1 using hash sha1, aes, xts-plain64, MK 32 bytes
# KDF pbkdf2, hash sha1: 996745 iterations per second.
# Data offset 4096, UUID 181fed4d-42f2-4f0f-8b70-cb7ba459e25f, digest iterations 121625
# Updating LUKS header of size 1024 on device /dev/sdb1
# Key length 32, device size 976771120 sectors, header size 2050 sectors.
# Reading LUKS header of size 1024 from device /dev/sdb1
# Key length 32, device size 976771120 sectors, header size 2050 sectors.
# Adding new keyslot -1 using volume key.
# Calculating data for key slot 0
# KDF pbkdf2, hash sha1: 1008246 iterations per second.
# Key slot 0 use 492307 password iterations.
# Using hash sha1 for AF in key slot 0, 4000 stripes
# Updating key slot 0 [0x1000] area.
# Using userspace crypto wrapper to access keyslot area.
IO error while encrypting keyslot.
# Releasing crypt device /dev/sdb1 context.
# Releasing device-mapper backend.
# Unlocking memory.
Command failed with code 5: IO error while encrypting keyslot.
Things also tend to hang with respect to the drive at this point. For example, fdisk -l spits out /dev/sda partitions immediately and then just hangs instead of printing out /dev/sdb info, then eventually quits (without ever writing it).
Any suggestions on where to look/how to troubleshoot? I found some possibly related posts, but nothing that looks promising:
- Impossible to crypt the drive using cryptsetup (fixed by rebooting)
- cryptsetup fails to open Udev cookie 0xd4d94f5 (semid 0) waiting for z (no responses; the hang after seems similar)
There's a couple odds and ends references to cryptsetup 1.6.6 having issues. I downloaded 1.6.4-1 and 1.6.5-1 and -2 from ARM to try, but wanted to post this in the meantime in case something stuck out.
Last edited by jwhendy (2015-05-29 16:01:40)

@qinohe I thought of that and the other day started formatting with mkfs.ext4; unfortunately, it was at work and I had to leave before I could let it finish. It had been chugging along a good few hours, and I was surprised it would take that long. I was able to format it with ext4 using Windows 7 (I dual boot) with the MiniTool Partition Wizard but I didn't use it like that before trying to solve the cryptsetup issue again.
This last time around, I was getting unresponsive behavior. I think I need to reboot each time I try something with cryptsetup, as any commands related to that drive seem to hang afterwards (fdisk, umount, eject, mkfs, or trying crypsetup again). Perhaps I'll just let it cook overnight with mkfs and see if I can at least have an unencrypted, but functional drive.
One interesting tidbit is that even though cryptsetup fails, when I've tried to issue mkfs afterward, it asks me to confirm that I want to format the disk since it has a LUKS header... so something appears to have been written. Is it possible the header is causing some issues? I don't know much about the structure of a disk (like what range the MBR resides in, what constitutes a header, etc.) but have been wondering if there's some way to start really, really clean with the disk. Like I'd just bought it -- something appears to be lingering around from previous efforts?
@frostschutz I'll check tomorrow. That's a good question. Just checked journalctl and here are some of the errors that appear; unfortunately, I wasn't watching so I can't tell you what matches up with what command:
May 23 09:32:22 arch_840 systemd-udevd[7784]: inotify_add_watch(7, /dev/sdb1, 10) failed: No such file or directory
May 23 09:32:22 arch_840 kernel: usb 3-4: stat urb: status -108
### there's lots like this; like 10 in a row with various sector values listed
May 23 09:32:19 arch_840 kernel: Buffer I/O error on dev sdb1, logical block 61341696, lost async page write
May 23 09:32:19 arch_840 kernel: blk_update_request: I/O error, dev sdb, sector 490735616
### there's also a bunch like this, from tab #0 -> #29 (not colored red, so not sure they're errors?)
May 23 09:32:19 arch_840 kernel: sd 2:0:0:0: [sdb] tag#0 CDB: opcode=0x2a 2a 00 1d 07 bc 10 00 04 00 00
May 23 09:32:18 arch_840 kernel: sd 2:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
I paged down quite a ways and those seem like the unique messages when I search the journal for "sdb". Anything stand out? I will say that the same sector numbers appeared in multiple blocks of the third error type listed, so that makes me wonder if something is genuinely wrong with the disk. I'll post the output of the full smartctl scan when I hopefully run it tomorrow.
Thanks for chiming in!

[SOLVED] help with PKGBUILD-svn

I am able to build a python-based package from svn using bash, but am having a problem writing the PKGBUILD. The bash commands are as follows:
svn co http://svn.berlios.de/svnroot/repos/wsjt/branches/wspr
cd wspr
export PYTHON="/usr/bin/python2"
export F2PY="/usr/bin/python2 f2py.py"
./configure --enable-gfortran --prefix=/usr
make
and this works fine. Following the ABS PKGBUILD-svn.proto template, I came up with the following PKGBUILD:
pkgname=wspr-svn
pkgver=1
pkgrel=1
pkgdesc="Weak Signal Propagation Reporter"
arch=('any')
url="http://physics.princeton.edu/pulsar/K1JT/wsjt.html"
license=('GPL')
optdepends=('g95')
depends=('python2' 'python-imaging' 'python2-numpy' 'libsamplerate' 'portaudio' 'fftw')
makedepends=('subversion')
_svntrunk="http://svn.berlios.de/svnroot/repos/wsjt/branches/wspr"
_svnmod="wspr"
build() {
export PYTHON="/usr/bin/python2"
export F2PY="/usr/bin/python2 f2py.py"
cd "$srcdir"
if [ -d $_svnmod/.svn ]; then
(cd $_svnmod && svn up -r $pkgver)
else
svn co $_svntrunk --config-dir ./ -r $pkgver $_svnmod
fi
msg "SVN checkout done or server timeout"
msg "Starting make..."
rm -rf "$srcdir/$_svnmod-build"
cp -r "$srcdir/$_svnmod" "$srcdir/$_svnmod-build"
cd "$srcdir/$_svnmod-build"
./configure --prefix=/usr --enable-gfortran
make
but get stuck with the following error:
Found executable /usr/bin/gfortran
error: unknown file type '' (from '-Wl,--hash-style=gnu')
make: *** [WsprMod/w.so] Error 1
Aborting...
I've been googling for hours, but feel like I might be getting in over my head. I suspect I'm missing something trivial since everything is in place for a successful build.
Last edited by sportscliche (2011-03-14 11:03:38)

Thanks for the fast reply Snowman. You had the right idea. Although your suggested edit did not work, the following line did:
unset LDFLAGS
I got this from the discussion here:
https://bbs.archlinux.org/viewtopic.php?pid=668971
(Note: in that thread there is an alternative approach suggested by Ranguvar:
export LDFLAGS="${LDFLAGS//-Wl,--as-needed}"
export LDFLAGS="${LDFLAGS//,--as-needed}"
export LDFLAGS="${LDFLAGS//--as-needed}"
which did not work for me.)
The PKGBUILD concludes with:
package() {
cd "$srcdir/$_svnmod-build"
sudo make DESTDIR="$pkgdir/" install
This runs makepkg -s to completion although I get a warning about a reference to $srcdir. Performing pacman -U on the tarball installs python files in /usr/lib/python2.7/site-packages/WsprMod and adds wspr.py in /usr/bin/. Launching the program with python2 wspr.py leads to an immediate segmentation fault. After the manual build, all the files were in the same directory. I tried moving everything into the same python directory and still got the seg fault.
When I built manually, I did not have to do a sudo make install. If I leave out this step in PKGBUILD, however, setup.py does not run and the package doesn't install anything. So I tried this instead
package() {
cd "$srcdir/$_svnmod-build"
python2 setup.py install --root=$pkgdir/ --optimize=1
which aborts makepkg because of file conflicts.
Can anyone see what I'm doing wrong?

[Partially Solved] Error with bsdtar and symbolic links

I'm trying to install a package (asymptote) from AUR but am running into an odd error. During the extract phase I get errors like
asymptote-1.70/base/asy-keywords.el: Can't update time for asymptote-1.70/base/asy-keywords.el: Function not implemented
bsdtar: Error exit delayed from previous errors.
I found a post that may help: http://bbs.archlinux.org/viewtopic.php?id=50750. Do I really have to do this?
By the way, I too am running on a Linode (Xen virtualization).
Thanks,
Luis
Last edited by banbh (2009-05-24 00:22:13)

I have not got to the bottom of my problems with bsdtar and symlinks. I suspect it must have something to do with either my configuration (derived from the Arch image provided by Linode) or running under virtualisation.
However, others might find my work-around useful, so I document it below.
I downloaded asymptote from AUR using wget ("wget http://aur.archlinux.org/packages/asymptote/asymptote.tar.gz"), unpacked it, then patched the PKGBUILD
$ diff -u PKGBUILD.orig PKGBUILD
--- PKGBUILD.orig 2009-05-23 17:58:47.000000000 -0400
+++ PKGBUILD 2009-05-23 18:00:49.000000000 -0400
@@ -11,9 +11,12 @@
'used if present at compile time: freeglut, gsl, fftw')
source=(http://downloads.sourceforge.net/sourceforge/asymptote/$pkgname-$pkgver.src.tgz)
md5sums=('1ded335bc63b662a6eb920a4c065706c')
+noextract=($pkgname-$pkgver.src.tgz)
build() {
- cd $srcdir/$pkgname-$pkgver
+ cd $srcdir
+ tar xzf $pkgname-$pkgver.src.tgz
+ cd $pkgname-$pkgver
./configure --enable-gc=/usr --prefix=/usr \
--with-latex=/usr/share/texmf/tex/latex || return 1
make asy || return 1
After that I simply did a "makepkg" followed by "sudo pacman -U asymptote-1.73-1-i686.pkg.tar.gz"

Error with PL/SQL package

Hi ,
I have written a package specification given below :
create or replace PACKAGE BILL_PACKAGE AS
storeId varchar2(5);
startDate varchar2(10);
FUNCTION F_Bill(str_id IN tel_tr_ltm_bl_py.id_str_rt%TYPE,ws_id IN tel_tr_ltm_bl_py.id_ws%TYPE,v_date IN tel_tr_ltm_bl_py.dc_dy_bsn%TYPE) RETURN boolean;
END BILLPAYPACKAGE;
I have written the package body also .Now when i am calling the function F_Bill , I am gettin this error :
PLS-00201: identifier 'BILL_PACKAGE.STARTDATE' must be declared
ORA-06550: line 2, column 1:
PL/SQL: Statement ignored
ORA-06550: line 3, column 1:
PLS-00201: identifier 'BILL_PACKAGE.STOREID' must be declared
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored
This same package is running fine on another local database.
What could be the reason for this?
Is this an acess issue ?In db which we are getting an error , we are using a user 'ConUser' to connect to a schema 'b_owner'.
How can we check this if this is a privilege issue.
Thanks!

>
This same package is running fine on another local database.
What could be the reason for this?
Is this an acess issue ?In db which we are getting an error , we are using a user 'ConUser' to connect to a schema 'b_owner'.
How can we check this if this is a privilege issue.The user "ConUSer" needs execute privileges for the pacakge.
Also it depends how he calls the package or the variables in it.
You can check the privs with
select * from all_tab_privs where table_name = 'BILL_PACKAGE';this must be run as user ConUser.
You could also have a problem with name resolution. The name of the package is not BILL_PACKAGE. It is "b_owner.BILL_PACKAGE".
If you omit the schema name then the current user is tried. So if you call BILL_PACKAGE then this is translated into "ConUSer.BILL_PACKAGE".
You can change this by creating a synonym like
create synonym bill_package for b_owner.bill_package;

[SOLVED] Error with PKGBUILD for package hash-identifier

Similar Messages

Maybe you are looking for