powerpill_portable.sh does not work in FreeBSD box

Xyne · 2010-12-23 08:05:17

Allan wrote:

Yay for incompatible tar implementations

Yay indeed.

@mfaridi
Can you install bsdtar? If not, what version of tar do you have?

mfaridi · 2010-12-23 08:07:27

Xyne wrote:

Allan wrote:
Yay for incompatible tar implementations
Yay indeed.

@mfaridi
Can you install bsdtar? If not, what version of tar do you have?

right now I test your script on Ubuntu system and I do not use FreeBSD right now , I install ubuntu with Virualbox on FreeBSD Box and use you script in Ubuntu system , I use ubuntu 10.10 AMD64

mfaridi · 2010-12-23 08:41:31

still script does not work

Nezmer · 2010-12-23 14:17:44

edited

Last edited by Nezmer (2010-12-23 14:24:22)

Nezmer · 2010-12-23 14:29:08

mfaridi wrote:

Xyne wrote:
Allan wrote:
Yay for incompatible tar implementations
Yay indeed.

@mfaridi
Can you install bsdtar? If not, what version of tar do you have?
right now I test your script on Ubuntu system and I do not use FreeBSD right now , I install ubuntu with Virualbox on FreeBSD Box and use you script in Ubuntu system , I use ubuntu 10.10 AMD64

Are you running a VM on top of FreeBSD just for this script?

There is no technical reason for this script to not work in native FreeBSD!

JokerBoy · 2010-12-23 15:47:16

this is funny..

mfaridi install archivers/gtar, textproc/gsed and sysutils/coreutils, and modify the script in order to use gtar, gsed, gcp, gmv, gmkdir, grm, etc.

Nezmer · 2010-12-23 16:08:45

JokerBoy wrote:

this is funny..
mfaridi install archivers/gtar, textproc/gsed and sysutils/coreutils, and modify the script in order to use gtar, gsed, gcp, gmv, gmkdir, grm, etc.

There is no need for that.

I think his tar errors came from Ubuntu.
I sure didn't see them!

JokerBoy · 2010-12-23 16:25:06

i thought this topic is about running powerpill_portable.sh in FreeBSD, not Ubuntu..

Xyne · 2010-12-23 19:00:22

@mfaridi
Install bsdtar from the libarchive package on Ubuntu: http://packages.ubuntu.com/lucid/bsdtar
It should be compatible with the script.

Please provide full error messages instead of simply posting that it doesn't work.

@JokerBoy
No. The powerpill_portable.sh script is run on the Arch system without the connection. It copies some Perl modules and Pacman files into a directory named "portable" and creates some scripts. These should be able to be run on a non-Arch system to download upgradable and new packages for the unconnected system.

The problem right now is satisfying all of the dependencies. It seems that the last step right now is getting a compatible version of tar.

@Nezmer
Have you been able to get this working?

Nezmer · 2010-12-23 22:49:23

Xyne wrote:

@Nezmer
Have you been able to get this working?

I thought so. It works partially.

It still complained about undefined fpath. But then continued with rebasing and upgrading from your repo which is the 1st repo in my Arch VPS. I commented out your repo and got:

% ./pp --aria2-bin /usr/local/bin/aria2c -Syyu
error: undefined fpath while loading config
--> Rebasing...
bsdtar: Unrecognized archive format
bsdtar: Error exit delayed from previous errors.

I didn't investigate further.

mfaridi · 2010-12-25 07:46:03

Xyne wrote:

@mfaridi
Install bsdtar from the libarchive package on Ubuntu: http://packages.ubuntu.com/lucid/bsdtar
It should be compatible with the script.
Please provide full error messages instead of simply posting that it doesn't work.

@JokerBoy
No. The powerpill_portable.sh script is run on the Arch system without the connection. It copies some Perl modules and Pacman files into a directory named "portable" and creates some scripts. These should be able to be run on a non-Arch system to download upgradable and new packages for the unconnected system.
The problem right now is satisfying all of the dependencies. It seems that the last step right now is getting a compatible version of tar.

@Nezmer
Have you been able to get this working?

Thanks , Thanks
your script solve big problem
I install bsdtar in ubuntu and start script
and this script download 11 packages and put it pkg directory , after 15 minute start it and it get 34 packages ,
How much time I run this script ?

Last edited by mfaridi (2010-12-25 07:59:24)

mfaridi · 2010-12-25 14:00:57

another very bad bug
I install in home Arch linux i686 , but powerpill_portable script , download x86_64 packages in work place , I run powerpill in Ubuntu x86_64 ,

Xyne · 2010-12-26 01:33:03

mfaridi wrote:

Thanks , Thanks
your script solve big problem
I install bsdtar in ubuntu and start script
and this script download 11 packages and put it pkg directory , after 15 minute start it and it get 34 packages ,
How much time I run this script ?

The repos were probably updated. Remember that Arch is rolling release, so there will always be new packages if you wait a while. Just run the script once before you leave work to get all of the latest packages. Bring the portable directory home, install the packages, and repeat the same steps the next day or whenver you want to update again.

mfaridi wrote:

another very bad bug
I install in home Arch linux i686 , but powerpill_portable script , download x86_64 packages in work place , I run powerpill in Ubuntu x86_64 ,

You have "Architecture = auto" in "portable/etc/pacman.conf". It should be "Architecture = i686" instead. I havel updated pacman_portable.conf to fix that automatically, but you can edit that file yourself too.

Last edited by Xyne (2010-12-26 01:50:30)

mfaridi · 2010-12-26 06:11:57

great job
I open pacman.conf and change auto to i686 and run that script again and everything go well and everyhting work great

Xyne · 2010-12-26 06:49:59

mfaridi wrote:

great job
I open pacman.conf and change auto to i686 and run that script again and everything go well and everyhting work great

Now all you need to do is run the "sync" script at home. Before you run it, download the new version of powerpill_portable.sh. Delete the "sync" file in "portable", then run "powerpill_portable.sh /path/to/portable" to create a new "sync" script. There was an error in the old "sync" script.

mfaridi · 2010-12-26 06:54:03

Xyne wrote:

mfaridi wrote:
great job
I open pacman.conf and change auto to i686 and run that script again and everything go well and everyhting work great
Now all you need to do is run the "sync" script at home. Before you run it, download the new version of powerpill_portable.sh. Delete the "sync" file in "portable", then run "powerpill_portable.sh /path/to/portable" to create a new "sync" script. There was an error in the old "sync" script.

OK
Thanks
Ok I will download new one and check in home
can make problem for me , I copy portable directory from USB to my hard disk and then move it to Virtual machine and run pp -Syu and then copy portable directory to USB and go to home and run sync in home ?
I am afraid path of directory change ,

Xyne · 2010-12-26 07:07:40

mfaridi wrote:

OK
Thanks
Ok I will download new one and check in home
can make problem for me , I copy portable directory from USB to my hard disk and then move it to Virtual machine and run pp -Syu and then copy portable directory to USB and go to home and run sync in home ?
I am afraid path of directory change ,

That should not cause any problems. The "portable" directory is designed to be portable.
All paths in the "portable" directory are relative. That is why you must run "pp" and "sync" inside the "portable" directory.

*edit*
If anything goes wrong with the "sync" script, just open it in an editor and look at what it does. It is very simple.

The first part copies the downloaded packages from portable/pkg/ to pacman's package cache (/var/cache/pacman/pkg).
The second part copies the sync databases from portable/db/sync to /var/lib/pacman/sync.

If the script doesn't work then you can do that manually. After that, just run the same commands with pacman that you ran with "pp", but without "-y".

For example, if you ran "pp -Syu", then run "pacman -Su".
If you ran "pp -Syu foo", then run "pacman -Su foo".

Last edited by Xyne (2010-12-26 07:12:48)

mfaridi · 2010-12-26 07:13:52

Xyne wrote:

mfaridi wrote:
OK
Thanks
Ok I will download new one and check in home
can make problem for me , I copy portable directory from USB to my hard disk and then move it to Virtual machine and run pp -Syu and then copy portable directory to USB and go to home and run sync in home ?
I am afraid path of directory change ,
That should not cause any problems. The "portable" directory is designed to be portable.
All paths in the "portable" directory are relative. That is why you must run "pp" and "sync" inside the "portable" directory.

Ok
I will test it today , I will go home with new powerpill.sh and run it in home and come back work and start pp -Syu and then come back home and start sync
I think I must run this script every two weeks , because some application is not ready , for example about KDE , some packages are relative with KDE upgrade to 4.4.9 and some of them are not upgrade to 4.4.9 right now , maybe this packages upgrade to new version tomorrow or next days , and this can break system

Xyne · 2010-12-26 07:20:40

mfaridi wrote:

Ok
I will test it today , I will go home with new powerpill.sh and run it in home and come back work and start pp -Syu and then come back home and start sync
I think I must run this script every two weeks , because some application is not ready , for example about KDE , some packages are relative with KDE upgrade to 4.4.9 and some of them are not upgrade to 4.4.9 right now , maybe this packages upgrade to new version tomorrow or next days , and this can break system

I edited my previous post to include more information. Please read it before going home.

Also remember to run "powerpill_portable.sh /path/to/portable" after you run the pacman commands.
The script will copy the new local database to the "portable" directory. You must do this every time you update your home computer with pacman.
It updates the portable directory.

mfaridi · 2010-12-26 07:27:08

Xyne wrote:

mfaridi wrote:
Ok
I will test it today , I will go home with new powerpill.sh and run it in home and come back work and start pp -Syu and then come back home and start sync
I think I must run this script every two weeks , because some application is not ready , for example about KDE , some packages are relative with KDE upgrade to 4.4.9 and some of them are not upgrade to 4.4.9 right now , maybe this packages upgrade to new version tomorrow or next days , and this can break system
I edited my previous post to include more information. Please read it before going home.
Also remember to run "powerpill_portable.sh /path/to/portable" after you run the pacman commands.
The script will copy the new local database to the "portable" directory. You must do this every time you update your home computer with pacman.
It updates the portable directory.

ok
can you fix this problem to , I have to run this command for work pp -Syu

 sed -i  "s@get_value('PacmanConf')@get_value('PacmanConfig')@" ./Xyne/Arch/{Powerp,Bauerb}ill.pm

Xyne · 2010-12-26 07:29:29

mfaridi wrote:

ok
can you fix this problem to , I have to run this command for work pp -Syu
 sed -i  "s@get_value('PacmanConf')@get_value('PacmanConfig')@" ./Xyne/Arch/{Powerp,Bauerb}ill.pm 

It should be fixed already. Just make sure that you update the "perl-xyne-arch" package on your home computer.

mfaridi · 2010-12-26 07:40:47

Xyne wrote:

mfaridi wrote:
ok
can you fix this problem to , I have to run this command for work pp -Syu
 sed -i  "s@get_value('PacmanConf')@get_value('PacmanConfig')@" ./Xyne/Arch/{Powerp,Bauerb}ill.pm 
It should be fixed already. Just make sure that you update the "perl-xyne-arch" package on your home computer.

I will check it

mfaridi · 2010-12-26 13:38:08

I do not know what happen I download your last script and move it home and run it and come back home and move it to virtualbox and run sh pp -Syu and I see these error

 
error: unable to read /etc/pacman.conf
error: undefined fpath while loading config

and script does not work , so I run this command

sed -i  "s@get_value('PacmanConf')@get_value('PacmanConfig')@" ./Xyne/Arch/{Powerp,Bauerb}ill.pm

and script start working

Xyne · 2010-12-26 15:33:52

mfaridi wrote:

I do not know what happen I download your last script and move it home and run it and come back home and move it to virtualbox and run sh pp -Syu and I see these error
 
error: unable to read /etc/pacman.conf
error: undefined fpath while loading config
and script does not work , so I run this command
sed -i  "s@get_value('PacmanConf')@get_value('PacmanConfig')@" ./Xyne/Arch/{Powerp,Bauerb}ill.pm
and script start working

Xyne wrote:

It should be fixed already. Just make sure that you update the "perl-xyne-arch" package on your home computer.

Update to the latest version of perl-xyne-arch. That will fix the error. After you upgrade, you do not need to run the "sed" command. The error was caused by an older version of perl-xyne-arch.

mfaridi · 2010-12-27 05:28:28

Xyne wrote:

mfaridi wrote:
I do not know what happen I download your last script and move it home and run it and come back home and move it to virtualbox and run sh pp -Syu and I see these error
 
error: unable to read /etc/pacman.conf
error: undefined fpath while loading config
and script does not work , so I run this command
sed -i  "s@get_value('PacmanConf')@get_value('PacmanConfig')@" ./Xyne/Arch/{Powerp,Bauerb}ill.pm
and script start working
Xyne wrote:
It should be fixed already. Just make sure that you update the "perl-xyne-arch" package on your home computer.
Update to the latest version of perl-xyne-arch. That will fix the error. After you upgrade, you do not need to run the "sed" command. The error was caused by an older version of perl-xyne-arch.

if I do not have internet connection at home , how I can upgrade perl-xyne-arch ,?
how I can upgrade it in home ?
what I must do , when I download last version of perl-xyne-arch in work with wget or something like wget and move it to home and upgrade last version to new one ?

Arch Linux

#26 2010-12-23 08:05:17

Re: powerpill_portable.sh does not work in FreeBSD box

#27 2010-12-23 08:07:27

Re: powerpill_portable.sh does not work in FreeBSD box

#28 2010-12-23 08:41:31

Re: powerpill_portable.sh does not work in FreeBSD box

#29 2010-12-23 14:17:44

Re: powerpill_portable.sh does not work in FreeBSD box

#30 2010-12-23 14:29:08

Re: powerpill_portable.sh does not work in FreeBSD box

#31 2010-12-23 15:47:16

Re: powerpill_portable.sh does not work in FreeBSD box

#32 2010-12-23 16:08:45

Re: powerpill_portable.sh does not work in FreeBSD box

#33 2010-12-23 16:25:06

Re: powerpill_portable.sh does not work in FreeBSD box

#34 2010-12-23 19:00:22

Re: powerpill_portable.sh does not work in FreeBSD box

#35 2010-12-23 22:49:23

Re: powerpill_portable.sh does not work in FreeBSD box

#36 2010-12-25 07:46:03

Re: powerpill_portable.sh does not work in FreeBSD box

#37 2010-12-25 14:00:57

Re: powerpill_portable.sh does not work in FreeBSD box

#38 2010-12-26 01:33:03

Re: powerpill_portable.sh does not work in FreeBSD box

#39 2010-12-26 06:11:57

Re: powerpill_portable.sh does not work in FreeBSD box

#40 2010-12-26 06:49:59

Re: powerpill_portable.sh does not work in FreeBSD box

#41 2010-12-26 06:54:03

Re: powerpill_portable.sh does not work in FreeBSD box

#42 2010-12-26 07:07:40

Re: powerpill_portable.sh does not work in FreeBSD box

#43 2010-12-26 07:13:52

Re: powerpill_portable.sh does not work in FreeBSD box

#44 2010-12-26 07:20:40

Re: powerpill_portable.sh does not work in FreeBSD box

#45 2010-12-26 07:27:08

Re: powerpill_portable.sh does not work in FreeBSD box

#46 2010-12-26 07:29:29

Re: powerpill_portable.sh does not work in FreeBSD box

#47 2010-12-26 07:40:47

Re: powerpill_portable.sh does not work in FreeBSD box

#48 2010-12-26 13:38:08

Re: powerpill_portable.sh does not work in FreeBSD box

#49 2010-12-26 15:33:52

Re: powerpill_portable.sh does not work in FreeBSD box

#50 2010-12-27 05:28:28

Re: powerpill_portable.sh does not work in FreeBSD box

Board footer