- Pacman-dev - lists.archlinux.org

[pacman-dev] CVS update of pacman-lib/src/pacman/po (hu.po)
by Dan McGee 30 Mar '07

30 Mar '07

Date: Friday, March 30, 2007 @ 15:55:08 Author: dan Path: /home/cvs-pacman/pacman-lib/src/pacman/po Modified: hu.po (1.16 -> 1.17) * Updated Hungarian translation Nagy Gabor <ngaba(a)petra.hos.u-szeged.hu> -------+ hu.po | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) Index: pacman-lib/src/pacman/po/hu.po diff -u pacman-lib/src/pacman/po/hu.po:1.16 pacman-lib/src/pacman/po/hu.po:1.17 --- pacman-lib/src/pacman/po/hu.po:1.16 Sat Mar 24 00:18:18 2007 +++ pacman-lib/src/pacman/po/hu.po Fri Mar 30 15:55:05 2007 @@ -129,7 +129,7 @@ #: src/pacman/log.h:34 msgid "warning: " -msgstr "figyelmeztetés" +msgstr "figyelmeztetés: " #: src/pacman/package.c:60 msgid "Explicitly installed" @@ -270,7 +270,7 @@ #: src/pacman/package.c:180 #, c-format msgid "error calculating checksums for %s\n" -msgstr "hiba a %s ellenõrzõ összegének számítása közben\n" +msgstr "hiba a(z) %s ellenõrzõ összegének számítása közben\n" #: src/pacman/package.c:193 #, c-format @@ -615,7 +615,7 @@ #: src/pacman/pacman.c:300 #, c-format msgid "'%s' is not a valid debug level" -msgstr "a '%s' nem érvényes hibakeresési szint" +msgstr "a(z) '%s' nem érvényes hibakeresési szint" #: src/pacman/pacman.c:315 #, c-format @@ -687,7 +687,7 @@ #: src/pacman/query.c:105 #, c-format msgid "cannot determine real path for '%s': %s" -msgstr "nem állapítható meg a valódi útvonal a '%s' számára: %s" +msgstr "nem állapítható meg a valódi útvonal a(z) '%s' számára: %s" #: src/pacman/query.c:119 #, c-format @@ -714,7 +714,7 @@ #: src/pacman/query.c:221 #, c-format msgid "group \"%s\" was not found\n" -msgstr "a \"%s\" csoport nem található\n" +msgstr "a(z) \"%s\" csoport nem található\n" #: src/pacman/query.c:232 msgid "no package file was specified for --file\n" @@ -752,7 +752,7 @@ #: src/pacman/remove.c:92 #, c-format msgid "failed to add target '%s' (%s)\n" -msgstr "nem sikerült a '%s' célt hozzáadni a tranzakcióhoz (%s)\n" +msgstr "nem sikerült a(z) '%s' célt hozzáadni a tranzakcióhoz (%s)\n" #: src/pacman/remove.c:106 #, c-format @@ -812,7 +812,7 @@ #: src/pacman/sync.c:223 #, c-format msgid " %s is up to date\n" -msgstr " a %s naprakész\n" +msgstr " a(z) %s naprakész\n" #: src/pacman/sync.c:345 #, c-format

1 0

[pacman-dev] Some pacman/hu.po bugfixes
by Nagy Gabor 30 Mar '07

30 Mar '07

Hi! Here is the patch: ------------------ --- pacman-lib/src/pacman/po/hu.po.old 2007-03-29 15:27:46.000000000 +0200 +++ pacman-lib/src/pacman/po/hu.po 2007-03-29 15:59:43.000000000 +0200 @@ -129,7 +129,7 @@ #: src/pacman/log.h:34 msgid "warning: " -msgstr "figyelmeztetés" +msgstr "figyelmeztetés: " #: src/pacman/package.c:60 msgid "Explicitly installed" @@ -270,7 +270,7 @@ #: src/pacman/package.c:180 #, c-format msgid "error calculating checksums for %s\n" -msgstr "hiba a %s ellenőrző összegének számítása közben\n" +msgstr "hiba a(z) %s ellenőrző összegének számítása közben\n" #: src/pacman/package.c:193 #, c-format @@ -615,7 +615,7 @@ #: src/pacman/pacman.c:300 #, c-format msgid "'%s' is not a valid debug level" -msgstr "a '%s' nem érvényes hibakeresési szint" +msgstr "a(z) '%s' nem érvényes hibakeresési szint" #: src/pacman/pacman.c:315 #, c-format @@ -687,7 +687,7 @@ #: src/pacman/query.c:105 #, c-format msgid "cannot determine real path for '%s': %s" -msgstr "nem állapítható meg a valódi útvonal a '%s' számára: %s" +msgstr "nem állapítható meg a valódi útvonal a(z) '%s' számára: %s" #: src/pacman/query.c:119 #, c-format @@ -714,7 +714,7 @@ #: src/pacman/query.c:221 #, c-format msgid "group \"%s\" was not found\n" -msgstr "a \"%s\" csoport nem található\n" +msgstr "a(z) \"%s\" csoport nem található\n" #: src/pacman/query.c:232 msgid "no package file was specified for --file\n" @@ -752,7 +752,7 @@ #: src/pacman/remove.c:92 #, c-format msgid "failed to add target '%s' (%s)\n" -msgstr "nem sikerült a '%s' célt hozzáadni a tranzakcióhoz (%s)\n" +msgstr "nem sikerült a(z) '%s' célt hozzáadni a tranzakcióhoz (%s)\n" #: src/pacman/remove.c:106 #, c-format @@ -812,7 +812,7 @@ #: src/pacman/sync.c:223 #, c-format msgid " %s is up to date\n" -msgstr " a %s naprakész\n" +msgstr " a(z) %s naprakész\n" #: src/pacman/sync.c:345 #, c-format --------------------

2 2

[pacman-dev] Git guide for pacman
by Dan McGee 30 Mar '07

30 Mar '07

I put this together last night and today to help everyone out with GIT usage. It is meant to be a overview, not a "step-by-step type exactly what I say" type of thing. Let me know if it is helpful, unhelpful, and what needs to be made more clear. I don't want to make it much more complex then this- once you understand the basics, you should start picking up the power of git on your own. -Dan ================= Super quick GIT guide This isn't meant to be an all-encompassing guide by any means- it is meant to be a really quick walk-through on how to do some basic operations on the pacman codebase in git, such as submitting a patch. For more extensive tutorials, check out the following: http://www.kernel.org/pub/software/scm/git/docs/tutorial.html www.kernel.org/pub/software/scm/git/docs/everyday.html http://wiki.winehq.org/GitWine (talks a lot about maintaining patches) In addition, all git commands have decent manpages to refer to. They can be reached one of two ways- for the git-add command, type 'man git-add' or 'git help add'. =Getting Started= The first step with git is cloning a remote repository. This is known in the CVS and SVN camps as checking out. GIT checkout has a different purpose, but that will be covered later. To grab the pacman source, run the following: git clone http://code.toofishes.net/gitprojects/pacman.git This will check out a local copy of the repository for you. This means you have the FULL history of the project on your computer, not just the most recent revision. This allows you to get work done even when offline, for example. The first steps after cloning may be just to look around. If you have read the tutorials mentioned above, even if you do not understand everything in them, you will be much better off. You will probably want to set up your name and email address for use in commit logs: git repo-config user.name "Your Name" git repo-config user.email "me(a)example.com" If you pass the '--global' flag to the above commands, the name and email will be stored in ~/.gitconfig, so will be used for all git projects unless overridden by a setting in the individual project. To update your local repository with any new branches, run 'git pull'. =Next Steps= 'git branch' will show you a list of branches. Initially, master is the only branch. However, if you pulled from a remote repo, you may have grabbed other branches- these can be seen with 'git branch -r'. Read the manpage for details. When working with git, it is good practice to never do your work on the master branch. This should stay clean to allow you to run 'git pull' and ensure that conflicts do not happen on the update. To create your own working branch, do the following (naming it whatever your heart desires): git branch working git checkout working Or compress the above into one command: git checkout -b working I highly recommend you read the man page for both of these commands. 'git-status' is highly helpful, read up on that too. =Making a patch= Woo! You found a bug in pacman (what a surprise) and know how to fix it. Ensure you have your working branch checked out ('git checkout working'). Then edit the file(s) you need in order to make your changes. Compiling is a good idea to ensure your patch didn't break anything, and if it is a big change, running 'make check' is highly recommended. So what do you do now? First, run 'git status'. You should see a list or even a few lists of files. The descriptions by each are a bit confusing, but you should be able to figure it out. GIT takes a different approach than CVS or SVN to committing changes- it doesn't commit a thing by default. You have to tell it what to commit, usually by running 'git add <filename>'. At this point, the file in its current state will be sent to a staging area for the commit. If you go back and change something in the file, you will have to git-add it again if you want the changes to be reflected in the commit. To commit your patch to your branch: git add <all edited files> git commit -s When writing a commit message, keep the following in mind. The first line is used as a patch summary- keep it short and concise. Next, skip a line and type out a full description of what your patch does. By full, I don't mean long- if you described everything in the summary line, then don't even bother with a message. Finally, skip one more line and you will have your Signed-off-by. This should have been automatically added by passing the '-s' parameter to 'git commit'. There is one more important step before submission. Because git is distributed, you don't have the most current version of the repository unless you go out and get it. In the easiest case, this is just running 'git pull'. You also want to make sure your patches are based off the most recent revision, known as the 'head'. To do this, checkout your branch with your patches, and use the following command: git rebase master To visualize what the above command did, qgit can be very helpful. To format a patch for email submission and review: git format-patch master This command will format all patches that make up the difference between your working branch and the master branch. They will be saved in the local directory; to store them elsewhere read up on the '-o' option. =Fixing your patch= So you sent off your patch to the ML and you got a few suggestions back. How does one fix it? Hopefully you did it on a branch and not the master branch, otherwise you are going to have a much tougher time. :) If it was the last patch on a branch: (edit the required files) git add <edited files> git commit --append -s If it was deeper in your patch tree: (ensure you are in the branch you wish to edit) git checkout -b tmp HEAD~<number> (where number is how far back you want to go, use 'git log' to determine) git reset HEAD^ (edit the required files) git commit -s -c ORIG_HEAD git rebase --onto tmp working~<number> working (replace working with your current working branch) git branch -D tmp http://wiki.winehq.org/GitWine has good information on the above, that is where most of this came from. After fixing your patch, you will probably want to rebase it as described above, and then use format-patch to submit it again. =Further reading= Commands you will definitely want to be knowledgeable on: clone (only once!), branch, checkout, status, pull, fetch, diff, add, commit, rebase, format-patch =Helpful Hints= 'git' itself is a wrapper script that calls the other commands. Thus, git-add can be called with either 'git add' or 'git-add'. qgit in extra is a great GUI viewer for git repositories. In addition, read up on 'git-instaweb'. Keep typing 'git co' instead of 'git checkout'? Try this: git config --global alias.co checkout

5 6

[pacman-dev] CVS update of pacman-lib/src/pacman/po (ru_RU.po)
by Dan McGee 30 Mar '07

30 Mar '07

Date: Friday, March 30, 2007 @ 14:06:04 Author: dan Path: /home/cvs-pacman/pacman-lib/src/pacman/po Modified: ru_RU.po (1.7 -> 1.8) * Updated Russian translation Владимир Байраковский <4rayven(a)gmail.com> ----------+ ru_RU.po | 58 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 29 insertions(+), 29 deletions(-) Index: pacman-lib/src/pacman/po/ru_RU.po diff -u pacman-lib/src/pacman/po/ru_RU.po:1.7 pacman-lib/src/pacman/po/ru_RU.po:1.8 --- pacman-lib/src/pacman/po/ru_RU.po:1.7 Mon Mar 26 18:47:57 2007 +++ pacman-lib/src/pacman/po/ru_RU.po Fri Mar 30 14:06:04 2007 @@ -134,7 +134,7 @@ #: src/pacman/package.c:60 msgid "Explicitly installed" -msgstr "Неявно установлен" +msgstr "Явно установлен" #: src/pacman/package.c:63 msgid "Installed as a dependency for another package" @@ -173,7 +173,7 @@ #: src/pacman/package.c:78 src/pacman/package.c:130 msgid "Provides :" -msgstr "Обеспечивает :" +msgstr "Предоставляет :" #: src/pacman/package.c:79 src/pacman/package.c:131 msgid "Depends On :" @@ -311,32 +311,32 @@ #: src/pacman/pacman.c:92 #, c-format msgid " %s {-A --add} [options] <file>\n" -msgstr " %s {-A --add} [опции] <файл>\n" +msgstr " %s {-A --add} [параметры] <файл>\n" #: src/pacman/pacman.c:93 #, c-format msgid " %s {-F --freshen} [options] <file>\n" -msgstr " %s {-F --freshen} [опции] <файл>\n" +msgstr " %s {-F --freshen} [параметры] <файл>\n" #: src/pacman/pacman.c:94 #, c-format msgid " %s {-Q --query} [options] [package]\n" -msgstr " %s {-Q --query} [опции] [пакет]\n" +msgstr " %s {-Q --query} [параметры] [пакет]\n" #: src/pacman/pacman.c:95 #, c-format msgid " %s {-R --remove} [options] <package>\n" -msgstr " %s {-R --remove} [опции] <пакет>\n" +msgstr " %s {-R --remove} [параметры] <пакет>\n" #: src/pacman/pacman.c:96 #, c-format msgid " %s {-S --sync} [options] [package]\n" -msgstr " %s {-S --sync} [опции] [пакет]\n" +msgstr " %s {-S --sync} [параметры] [пакет]\n" #: src/pacman/pacman.c:97 #, c-format msgid " %s {-U --upgrade} [options] <file>\n" -msgstr " %s {-U --upgrade} [опции] <файл>\n" +msgstr " %s {-U --upgrade} [параметры] <файл>\n" #: src/pacman/pacman.c:98 #, c-format @@ -351,13 +351,13 @@ #: src/pacman/pacman.c:101 #, c-format msgid "usage: %s {-A --add} [options] <file>\n" -msgstr "использование: %s {-A --add} [опции] <файл>\n" +msgstr "использование: %s {-A --add} [параметры] <файл>\n" #: src/pacman/pacman.c:102 src/pacman/pacman.c:107 src/pacman/pacman.c:119 #: src/pacman/pacman.c:124 src/pacman/pacman.c:138 #, c-format msgid "options:\n" -msgstr "опции:\n" +msgstr "параметры:\n" #: src/pacman/pacman.c:103 src/pacman/pacman.c:109 src/pacman/pacman.c:120 #: src/pacman/pacman.c:140 @@ -375,7 +375,7 @@ #: src/pacman/pacman.c:106 #, c-format msgid "usage: %s {-R --remove} [options] <package>\n" -msgstr "использование: %s {-R --remove} [опции] <пакет>\n" +msgstr "использование: %s {-R --remove} [параметры] <пакет>\n" #: src/pacman/pacman.c:108 #, c-format @@ -407,17 +407,17 @@ #: src/pacman/pacman.c:115 #, c-format msgid "usage: %s {-F --freshen} [options] <file>\n" -msgstr "использование: %s {-F --freshen} [опции] <файл>\n" +msgstr "использование: %s {-F --freshen} [параметры] <файл>\n" #: src/pacman/pacman.c:117 #, c-format msgid "usage: %s {-U --upgrade} [options] <file>\n" -msgstr "использование: %s {-U --upgrade} [опции] <файл>\n" +msgstr "использование: %s {-U --upgrade} [параметры] <файл>\n" #: src/pacman/pacman.c:123 #, c-format msgid "usage: %s {-Q --query} [options] [package]\n" -msgstr "использование: %s {-Q --query} [опции] [пакет]\n" +msgstr "использование: %s {-Q --query} [параметры] [пакет]\n" #: src/pacman/pacman.c:125 #, c-format @@ -468,7 +468,7 @@ #, c-format msgid " -p, --file <package> query a package file instead of the database\n" msgstr "" -" -p, --file <пакет> извлечь информацию из файла пакета <пакет>, а не из " +" -p, --file <пакет> извлечь информацию из файла пакета <пакет>, а не из " "базы данных\n" #: src/pacman/pacman.c:134 @@ -477,7 +477,7 @@ " -s, --search <regex> search locally-installed packages for matching " "strings\n" msgstr "" -" -s, --search <regex> искать указанную строку в локально установленных " +" -s, --search <regex> искать указанную строку в локально установленных " "пакетах\n" #: src/pacman/pacman.c:135 @@ -490,7 +490,7 @@ #: src/pacman/pacman.c:137 #, c-format msgid "usage: %s {-S --sync} [options] [package]\n" -msgstr "использование: %s {-S --sync} [опции] [пакет]\n" +msgstr "использование: %s {-S --sync} [параметры] [пакет]\n" #: src/pacman/pacman.c:139 #, c-format @@ -539,8 +539,7 @@ " -w, --downloadonly download packages but do not install/upgrade " "anything\n" msgstr "" -" -w, --downloadonly загрузить пакеты с сервера, но ничего не " -"устанавливать и не обновлять\n" +" -w, --downloadonly загрузить пакеты с сервера, но не устанавливать\n" #: src/pacman/pacman.c:150 #, c-format @@ -642,7 +641,7 @@ #: src/pacman/pacman.c:363 #, c-format msgid "'%s' is not a valid root path\n" -msgstr "'%s' не является верным корневым каталогом\n" +msgstr "некорректный корневой каталог: '%s'\n" #: src/pacman/pacman.c:390 msgid "only one operation may be used at a time\n" @@ -659,12 +658,13 @@ #: src/pacman/pacman.c:489 msgid "you cannot perform this operation unless you are root.\n" -msgstr "Вы не можете выполнить эту операцию если вы не root.\n" +msgstr "" +"Вы не можете выполнить эту операцию не являясь суперпользователем (root).\n" #: src/pacman/pacman.c:505 #, c-format msgid "failed to parse config (%s)\n" -msgstr "не удалось разобрать конфигурационный файл (%s)\n" +msgstr "не удалось обработать конфигурационный файл (%s)\n" #: src/pacman/pacman.c:516 msgid "Targets :" @@ -673,15 +673,15 @@ #: src/pacman/pacman.c:522 #, c-format msgid "could not register 'local' database (%s)\n" -msgstr "не могу зарегистрировать 'локальную' базу данных (%s)\n" +msgstr "не могу зарегистрировать локальную базу данных (%s)\n" #: src/pacman/pacman.c:529 msgid "no targets specified (use -h for help)\n" -msgstr "не задано целей (для помощи используйте -h)\n" +msgstr "не задано целей (для справки используйте -h)\n" #: src/pacman/pacman.c:542 msgid "no operation specified (use -h for help)\n" -msgstr "не указаны конкретные операции (для помощи используйте -h)\n" +msgstr "не задана операция (для справки используйте -h)\n" #: src/pacman/query.c:90 msgid "no file was specified for --owns\n" @@ -730,7 +730,7 @@ #: src/pacman/query.c:232 msgid "no package file was specified for --file\n" -msgstr "не указан файл пакета для опции --file\n" +msgstr "не указан файл пакета для параметра --file\n" #: src/pacman/query.c:236 #, c-format @@ -852,7 +852,7 @@ #: src/pacman/sync.c:491 msgid "synchronizing package lists" -msgstr "синхронизирую список пакетов" +msgstr "синхронизирую списки пакетов" #: src/pacman/sync.c:493 msgid "failed to synchronize any databases" @@ -884,7 +884,7 @@ #: src/pacman/sync.c:522 msgid ":: Upgrade pacman first? [Y/n] " -msgstr ":: Сначала обновить pacman? [Y/n] " +msgstr ":: Обновить pacman в первую очередь? [Y/n] " #: src/pacman/sync.c:537 #, c-format @@ -908,7 +908,7 @@ #: src/pacman/sync.c:603 #, c-format msgid "'%s': not found in sync db\n" -msgstr "'%s': не найдено в базе данных\n" +msgstr "'%s': не найдено в базе пакетов\n" #: src/pacman/sync.c:621 msgid "requires"

1 0

[pacman-dev] pacman return values
by bardo 30 Mar '07

30 Mar '07

I noticed that pacman3 returns 0 on query (-Q, -Si) even if the package doesn't exist. I have no CVS access ATM, so I can't check out if this has been fixed... bardo

3 3

[pacman-dev] DB-Fix for dup Required-By
by Travis Willard 30 Mar '07

30 Mar '07

Hi all, If you're like me and have been installing the pacman3 RC's to help test, you may have been bitten by a bug that caused "Required By" entries in the local pacman DB to become duplicated, resulting in something that may have looked like this: ----------8<----------8<----------8<----------8<----------8< $ pacman -Qi xorg-server Name : xorg-server Version : 1.2.0-3 ...blah blah... Required By : ati-fglrx-utils xorg xorg xorg xorg ----------8<----------8<----------8<----------8<----------8< While harmless, I found this annoying after a while, so I whipped up a script to scan the DB for these discrepancies, collect a list of affected packages, then pacman -S them all to fix it up. I've tested this script a few times on my own system, seems to do the job correctly, though one line is a bit of a hack. ;) As always, "Use at your own risk!", although I think it's perfectly safe to use - the very worst I can imagine that can happen is that you'll reinstall a few packages you didn't need to. -- Travis

2 1

[pacman-dev] Russian translation update
by Владимир Байраковский 30 Mar '07

30 Mar '07

Hi! This is a new patch for src/pacman/po/ru_RU.po with some improvements.

1 0

[pacman-dev] CVS update of pacman-lib/lib/libalpm (util.c)
by Aaron Griffin 30 Mar '07

30 Mar '07

Date: Friday, March 30, 2007 @ 00:46:17 Author: aaron Path: /home/cvs-pacman/pacman-lib/lib/libalpm Modified: util.c (1.51 -> 1.52) commit 1d35c4dcc6399023217e41eaa8ff4733b1ad2b0d Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Mar 29 22:44:10 2007 -0500 Report an error on setmntent failure Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> --------+ util.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) Index: pacman-lib/lib/libalpm/util.c diff -u pacman-lib/lib/libalpm/util.c:1.51 pacman-lib/lib/libalpm/util.c:1.52 --- pacman-lib/lib/libalpm/util.c:1.51 Thu Mar 22 04:22:48 2007 +++ pacman-lib/lib/libalpm/util.c Fri Mar 30 00:46:17 2007 @@ -560,11 +560,13 @@ static long long get_freespace() { struct mntent *mnt; - char *table = MOUNTED; + const char *table = MOUNTED; FILE *fp; long long ret=0; if((fp = setmntent(table, "r")) == NULL) { + _alpm_log(PM_LOG_ERROR, _("cannot read disk space information from %s: %s"), + table, strerror(errno)); return(-1); }

1 0

[pacman-dev] CVS update of pacman-lib/scripts (repo-add)
by Aaron Griffin 30 Mar '07

30 Mar '07

Date: Thursday, March 29, 2007 @ 23:33:19 Author: aaron Path: /home/cvs-pacman/pacman-lib/scripts Modified: repo-add (1.6 -> 1.7) commit 970d2e942eb29bf78fe89895ace4d781970b6e94 Author: Aaron Griffin <aaronmgriffin(a)gmail.com> Date: Thu Mar 29 21:30:40 2007 -0500 repo-add leaves .PKGINFO in the current directory * Misuse of 'tar xf', which should be 'tar tf' Signed-off-by: Aaron Griffin <aaronmgriffin(a)gmail.com> ----------+ repo-add | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: pacman-lib/scripts/repo-add diff -u pacman-lib/scripts/repo-add:1.6 pacman-lib/scripts/repo-add:1.7 --- pacman-lib/scripts/repo-add:1.6 Tue Mar 13 11:01:15 2007 +++ pacman-lib/scripts/repo-add Thu Mar 29 23:33:19 2007 @@ -246,7 +246,7 @@ fi else if [ -f "$arg" ]; then - if ! tar xf "$arg" .PKGINFO 2>&1 >/dev/null; then + if ! tar tf "$arg" .PKGINFO 2>&1 >/dev/null; then echo "error: '$arg' is not a package file, skipping" else echo ":: adding package '$arg'"

1 0

[pacman-dev] [patch] makepkg (actually tar) can't extract .tar.Z archives.
by Andrew Fyfe 30 Mar '07

30 Mar '07

Found a bug last night when trying to build rcs, 'tar -xf' doesn't work when trying to extract .tar.Z archives. You need to use 'tar -xzf'. Patch attached. Andrew >From 2d6993d638a46da68c23927e609000764c4b2b0c Mon Sep 17 00:00:00 2001 From: Andrew Fyfe <andrew(a)neptune-one.net> Date: Thu, 29 Mar 2007 11:11:36 +0100 Subject: [PATCH 1/1] Fix bug where makepkg can't extract .tar.Z archives. For some reason 'tar -xf' doesn't work with .tar.Z, you need to use 'tar -xzf' to extract the archive. Signed-off-by: Andrew Fyfe <andrew(a)neptune-one.net> --- scripts/makepkg | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/scripts/makepkg b/scripts/makepkg index 5afb285..92d8ab2 100755 --- a/scripts/makepkg +++ b/scripts/makepkg @@ -809,6 +809,8 @@ else file_type=$(file -biz "$file") unset cmd case "$file_type" in + *application/x-tar*application/x-compress*) + cmd="tar -xzf $file" ;; *application/x-tar*) cmd="tar -xf $file" ;; *application/x-zip*) -- 1.5.0.5

2 1