[pacman-dev] pacman-git releases
I use pacman-git from 1 or 2 weeks (local build from PKGBUILD) , its fast and stable,good job.Thank you. Name : pacman-git Version : 20071121-1 ... Architecture : x86_64 ... [~]:: pacman -Q|wc -l 1251 :) no problems for pacman [~]:: pacman -Ss|wc -l 9521 this its a feature or a bug? i have made a build for bsc-beta,i have a line: make PREFIX=$startdir/pkg/opt/bsc install || return 1 variable its wrong,makepkg make empty pkg and skip "return 1" make: Nothing to be done for `install'. ==> Tidying install... -> Removing info/doc files... -> Compressing man pages... -> Stripping debugging symbols from binarie ==> Creating package... -> Generating .FILELIST file... -> Generating .PKGINFO file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: bsc-beta (Thu Nov 22 19: in the stable version this thing is working correct and return an error ==> Removing info/doc files... ==> Compressing man pages... ==> Stripping debugging symbols from libraries... ==> Stripping symbols from binaries... ==> Generating .FILELIST file... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> Generating .PKGINFO file... ==> Compressing package... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> ERROR: Failed to create package file. also makepkg doesn't work with directory with spaces for example try to build pacman-git in "~/new\ folder/pacman-git"
On Nov 22, 2007 2:59 PM, fancris3 <fancris3@aol.com> wrote:
[~]:: pacman -Ss|wc -l 9521 this its a feature or a bug?
What, that pacman -Ss returns every package? I'm pretty sure that's by design, so it's not a bug. - Hide quoted text -
i have made a build for bsc-beta,i have a line:
make PREFIX=$startdir/pkg/opt/bsc install || return 1
variable its wrong,makepkg make empty pkg and skip "return 1"
make: Nothing to be done for `install'. ==> Tidying install... -> Removing info/doc files... -> Compressing man pages... -> Stripping debugging symbols from binarie ==> Creating package... -> Generating .FILELIST file... -> Generating .PKGINFO file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: bsc-beta (Thu Nov 22 19:
in the stable version this thing is working correct and return an error
==> Removing info/doc files... ==> Compressing man pages... ==> Stripping debugging symbols from libraries... ==> Stripping symbols from binaries... ==> Generating .FILELIST file... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> Generating .PKGINFO file... ==> Compressing package... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> ERROR: Failed to create package file.
That's a bugfix - the previous version is the buggy one. A packager should be able to build empty packages if they want. It's up to you to ensure your package was built correctly.
On Nov 22, 2007 3:12 PM, Travis Willard <travis@archlinux.org> wrote:
On Nov 22, 2007 2:59 PM, fancris3 <fancris3@aol.com> wrote:
[~]:: pacman -Ss|wc -l 9521 this its a feature or a bug?
What, that pacman -Ss returns every package? I'm pretty sure that's by design, so it's not a bug.
Yeah, I'm not sure what you were trying to do here at all- get a line count of packages with their descriptions? Seems like a weird statistic to me... -Dan
On Thu, Nov 22, 2007 at 11:37:21PM -0500, Dan McGee wrote:
On Nov 22, 2007 3:12 PM, Travis Willard <travis@archlinux.org> wrote:
On Nov 22, 2007 2:59 PM, fancris3 <fancris3@aol.com> wrote:
[~]:: pacman -Ss|wc -l 9521 this its a feature or a bug?
What, that pacman -Ss returns every package? I'm pretty sure that's by design, so it's not a bug.
Yeah, I'm not sure what you were trying to do here at all- get a line count of packages with their descriptions? Seems like a weird statistic to me...
I see mainly two possible behaviors for "pacman -Ss" : 1) list everything 2) fail and print a help message asking for an argument I don't think the first one is problematic, but maybe he was expecting the second one.
On Fri, 23 Nov 2007 08:51:37 +0200, Xavier <shiningxc@gmail.com> wrote:
I see mainly two possible behaviors for "pacman -Ss" : 1) list everything 2) fail and print a help message asking for an argument I don't think the first one is problematic, but maybe he was expecting the second one.
yes,i expect the second because of pacman.pot : #: src/pacman/pacman.c:562 msgid "no targets specified (use -h for help)\n"
The "return 1" isn't skipped as it was pretented? That would be a bit odd.
here its PKGBUILD pkgname=bsc-beta pkgver=4.0.05 pkgrel=1 pkgdesc="Two panels file mamager" arch=('i686' 'x86_64') url="http://www.beesoft.org/bsc.html" license="GPL" depends=('qt4') source=(http://www.beesoft.org/download/bsc_${pkgver}.beta_src.tar.bz2) md5sums=() build() { cd $startdir/src/bsc /usr/bin/qmake make PREFIX=/opt/bsc make PREFIX=$startdir/pkg/opt/bsc install || return 1 } I thing its bad to hide a error by default,maybe its useful a options like options=(emptypkg)
On Fri, Nov 23, 2007 at 09:17:06AM +0200, fancris3 wrote:
here its PKGBUILD
pkgname=bsc-beta pkgver=4.0.05 pkgrel=1 pkgdesc="Two panels file mamager" arch=('i686' 'x86_64') url="http://www.beesoft.org/bsc.html" license="GPL" depends=('qt4') source=(http://www.beesoft.org/download/bsc_${pkgver}.beta_src.tar.bz2) md5sums=()
build() { cd $startdir/src/bsc /usr/bin/qmake make PREFIX=/opt/bsc make PREFIX=$startdir/pkg/opt/bsc install || return 1 }
I thing its bad to hide a error by default,maybe its useful a options like options=(emptypkg)
Ok, I see. But what you don't understand is that there are no errors! That make install doesn't do anything, but it does it without errors :) So there is nothing wrong at all, no hidden errors..
On Thu, Nov 22, 2007 at 03:12:41PM -0500, Travis Willard wrote:
i have made a build for bsc-beta,i have a line:
make PREFIX=$startdir/pkg/opt/bsc install || return 1
variable its wrong,makepkg make empty pkg and skip "return 1"
make: Nothing to be done for `install'. ==> Tidying install... -> Removing info/doc files... -> Compressing man pages... -> Stripping debugging symbols from binarie ==> Creating package... -> Generating .FILELIST file... -> Generating .PKGINFO file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: bsc-beta (Thu Nov 22 19:
in the stable version this thing is working correct and return an error
==> Removing info/doc files... ==> Compressing man pages... ==> Stripping debugging symbols from libraries... ==> Stripping symbols from binaries... ==> Generating .FILELIST file... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> Generating .PKGINFO file... ==> Compressing package... tar: *: Cannot stat: No such file or directory tar: Error exit delayed from previous errors ==> ERROR: Failed to create package file.
That's a bugfix - the previous version is the buggy one. A packager should be able to build empty packages if they want. It's up to you to ensure your package was built correctly.
I'm confused here. So the error comes from tar, and not from "make install", right? The "return 1" isn't skipped as it was pretented? That would be a bit odd.
participants (4)
-
Dan McGee
-
fancris3
-
Travis Willard
-
Xavier