- Pacman-dev - lists.archlinux.org

[pacman-dev] undocumented features, bugs and why pacman's speed cannot be tuned...
by Nagy Gabor 27 Feb '07

27 Feb '07

Hi! I looked into the source of pacman (I want to speed it up), I haven't finished yet, but I'd like to share some of my impressions: 1. There are some undocumented features: -Syy (force sync remote repos), -A, -U can install from http://, ftp://; -Sgg list groups with their content 2. The main problem with speed, that pacman always reads the repos: I thought, that in the case of sync repos, this is absolutely not needed in most cases (an "ls" is enough) and when all information is needed (e.g. when -Ss is invoked) we may use the ungziped db. But of course, in local repo we cannot use a db file. I am disappointed, because in almost all cases (-S -A -U) the whole localdb must be cached. Why? Because of conflict checking and provide checking (this problem can be solved, as I wrote in my previous e-mail; but needs to convert (just adding some new symlinks to) the existing local repo). The main problem, when you install a new package, it is needed to fill in the requiredby field (you may say, that this is needless, nut it's not, because you may have broked dependencies with -d earlier) :-( 3. Probably when 2 packages provide the same content and they are not mutual, bugs can happen: as I can see from the source (someone should test) if foo1 and foo2 provides foo, and you install foo3 which needs foo, then requieredby foo3 is set for both foo1 and foo2. And you won't be able to remove neigther foo1 and nor foo2 until you remove foo3, however foo3's foo dependency is satisfied until at least one of the foo-providers is installed. Bye, Nagy Gabor

4 11

[pacman-dev] CVS update of pacman-lib/pactest (4 files)
by Dan McGee 27 Feb '07

27 Feb '07

Date: Tuesday, February 27, 2007 @ 11:15:47 Author: dan Path: /home/cvs-pacman/pacman-lib/pactest Added: tests/upgrade055.py (1.1) Modified: Makefile.am (1.1 -> 1.2) tests/upgrade052.py (1.2 -> 1.3) Removed: COPYING (1.1) * Updated description of test upgrade052. * Added the actual "Nagy's bug" as upgrade055.py. * Updated the Makefile to distribute the pactest readme. * Removed COPYING from the pactest directory- see COPYING at the root for the same license. ---------------------+ COPYING | 340 -------------------------------------------------- Makefile.am | 6 tests/upgrade052.py | 2 tests/upgrade055.py | 26 +++ 4 files changed, 32 insertions(+), 342 deletions(-) Index: pacman-lib/pactest/COPYING diff -u pacman-lib/pactest/COPYING:1.1 pacman-lib/pactest/COPYING:removed --- pacman-lib/pactest/COPYING:1.1 Sun Oct 15 15:04:27 2006 +++ pacman-lib/pactest/COPYING Tue Feb 27 11:15:47 2007 @@ -1,340 +0,0 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 - - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. - - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. - - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. - - 1. You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. - -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - - 2. You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: - - a) You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - - b) You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - - c) If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. - -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. - - 3. You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: - - a) Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - - b) Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - - c) Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. - -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. - - 4. You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. - - 5. You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. - - 6. Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. - - 7. If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. - -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. - -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. - - 8. If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. - - 9. The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. - - 10. If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. - - NO WARRANTY - - 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. - - 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. - - END OF TERMS AND CONDITIONS - - Appendix: How to Apply These Terms to Your New Programs - - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. - - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. - - <one line to give the program's name and a brief idea of what it does.> - Copyright (C) 19yy <name of author> - - This program is free software; you can redistribute it and/or modify - it under the terms of the GNU General Public License as published by - the Free Software Foundation; either version 2 of the License, or - (at your option) any later version. - - This program is distributed in the hope that it will be useful, - but WITHOUT ANY WARRANTY; without even the implied warranty of - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - GNU General Public License for more details. - - You should have received a copy of the GNU General Public License - along with this program; if not, write to the Free Software - Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. - -Also add information on how to contact you by electronic and paper mail. - -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: - - Gnomovision version 69, Copyright (C) 19yy name of author - Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. - This is free software, and you are welcome to redistribute it - under certain conditions; type `show c' for details. - -The hypothetical commands `show w' and `show c' should show the appropriate -parts of the General Public License. Of course, the commands you use may -be called something other than `show w' and `show c'; they could even be -mouse-clicks or menu items--whatever suits your program. - -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: - - Yoyodyne, Inc., hereby disclaims all copyright interest in the program - `Gnomovision' (which makes passes at compilers) written by James Hacker. - - <signature of Ty Coon>, 1 April 1989 - Ty Coon, President of Vice - -This General Public License does not permit incorporating your program into -proprietary programs. If your program is a subroutine library, you may -consider it more useful to permit linking proprietary applications with the -library. If this is what you want to do, use the GNU Library General -Public License instead of this License. Index: pacman-lib/pactest/Makefile.am diff -u pacman-lib/pactest/Makefile.am:1.1 pacman-lib/pactest/Makefile.am:1.2 --- pacman-lib/pactest/Makefile.am:1.1 Thu Feb 22 16:34:52 2007 +++ pacman-lib/pactest/Makefile.am Tue Feb 27 11:15:47 2007 @@ -12,4 +12,8 @@ noinst_SCRIPTS = $(check_SCRIPTS) -EXTRA_DIST = $(check_SCRIPTS) +EXTRA_DIST = \ + README \ + TODO \ + ChangeLog \ + $(check_SCRIPTS) Index: pacman-lib/pactest/tests/upgrade052.py diff -u pacman-lib/pactest/tests/upgrade052.py:1.2 pacman-lib/pactest/tests/upgrade052.py:1.3 --- pacman-lib/pactest/tests/upgrade052.py:1.2 Tue Feb 27 03:29:02 2007 +++ pacman-lib/pactest/tests/upgrade052.py Tue Feb 27 11:15:47 2007 @@ -1,4 +1,4 @@ -self.description = "Nagy's bug (I think) -- in progress" +self.description = "Upgrade to a package that provides less than before" lp1 = pmpkg("pkg1") lp1.depends = ["imaginary"] Index: pacman-lib/pactest/tests/upgrade055.py diff -u /dev/null pacman-lib/pactest/tests/upgrade055.py:1.1 --- /dev/null Tue Feb 27 11:15:47 2007 +++ pacman-lib/pactest/tests/upgrade055.py Tue Feb 27 11:15:47 2007 @@ -0,0 +1,26 @@ +self.description = "Upgrade a package that provides one of two imaginary packages" + +lp1 = pmpkg("pkg1") +lp1.depends = ["imaginary", "imaginary2"] +self.addpkg2db("local", lp1) + +lp2 = pmpkg("pkg2") +lp2.provides = ["imaginary"] +lp2.requiredby = [ "pkg1" ] +self.addpkg2db("local", lp2) + +lp3 = pmpkg("pkg3") +lp3.provides = ["imaginary2"] +lp3.requiredby = [ "pkg1" ] +self.addpkg2db("local", lp3) + +p = pmpkg("pkg2", "1.0-2") +p.provides = ["imaginary"] +self.addpkg(p) + +self.args = "-U %s" % p.filename() + +self.addrule("PACMAN_RETCODE=0") +self.addrule("PKG_EXIST=pkg1") +self.addrule("PKG_VERSION=pkg2|1.0-2") +self.addrule("PKG_EXIST=pkg3")

1 0

[pacman-dev] needless ldconfig
by Nagy Gabor 27 Feb '07

27 Feb '07

That is terrible, that pacman does ldconfig always. A NOLDCONFIG flag would be nice (and easy to implement) somewhere in .PKGINFO. These solution would be compatible with older packeges (because ldconfig is still the default), however we can radically speed up for example -R in the case of packages where no ldconfig is needed. Bye, Nagy Gabor

3 3

[pacman-dev] CVS update of pacman-lib/etc/abs (5 files)
by Dan McGee 27 Feb '07

27 Feb '07

Date: Tuesday, February 27, 2007 @ 10:53:14 Author: dan Path: /home/cvs-pacman/pacman-lib/etc/abs Modified: supfile.arch (1.1 -> 1.2) supfile.community (1.1 -> 1.2) supfile.extra (1.1 -> 1.2) supfile.testing (1.2 -> 1.3) supfile.unstable (1.1 -> 1.2) * Updated all the supfiles for consistancy, and added a commented out line to set the umask that some people may find helpful with an 'abs' group (but it isn't enabled by default). -------------------+ supfile.arch | 12 +++--------- supfile.community | 1 + supfile.extra | 1 + supfile.testing | 5 +++-- supfile.unstable | 1 + 5 files changed, 9 insertions(+), 11 deletions(-) Index: pacman-lib/etc/abs/supfile.arch diff -u pacman-lib/etc/abs/supfile.arch:1.1 pacman-lib/etc/abs/supfile.arch:1.2 --- pacman-lib/etc/abs/supfile.arch:1.1 Tue Dec 5 02:30:15 2006 +++ pacman-lib/etc/abs/supfile.arch Tue Feb 27 10:53:14 2007 @@ -1,21 +1,15 @@ # -# /etc/abs/supfile +# /etc/abs/supfile.arch # -# this is the host containing the master ABS files +# this is the host containing the current PKGBUILD files *default host=cvs.archlinux.org *default release=cvs *default delete *default use-rel-suffix *default compress +#*default umask=002 -# -# Set tag equal to the package tree you wish to follow. CURRENT and -# STABLE are the most commonly used, but you can specify specific -# versions or tag names. Examples are RELEASE_0_2, VEGA, RELEASE_0_3, -# FIREFLY, etc. -# *default tag=CURRENT - arch Index: pacman-lib/etc/abs/supfile.community diff -u pacman-lib/etc/abs/supfile.community:1.1 pacman-lib/etc/abs/supfile.community:1.2 --- pacman-lib/etc/abs/supfile.community:1.1 Tue Dec 5 02:30:15 2006 +++ pacman-lib/etc/abs/supfile.community Tue Feb 27 10:53:14 2007 @@ -9,6 +9,7 @@ *default delete *default use-rel-suffix *default compress +#*default umask=002 *default tag=CURRENT community Index: pacman-lib/etc/abs/supfile.extra diff -u pacman-lib/etc/abs/supfile.extra:1.1 pacman-lib/etc/abs/supfile.extra:1.2 --- pacman-lib/etc/abs/supfile.extra:1.1 Tue Dec 5 02:30:15 2006 +++ pacman-lib/etc/abs/supfile.extra Tue Feb 27 10:53:14 2007 @@ -9,6 +9,7 @@ *default delete *default use-rel-suffix *default compress +#*default umask=002 *default tag=CURRENT extra Index: pacman-lib/etc/abs/supfile.testing diff -u pacman-lib/etc/abs/supfile.testing:1.2 pacman-lib/etc/abs/supfile.testing:1.3 --- pacman-lib/etc/abs/supfile.testing:1.2 Fri Feb 23 02:45:15 2007 +++ pacman-lib/etc/abs/supfile.testing Tue Feb 27 10:53:14 2007 @@ -2,14 +2,15 @@ # /etc/abs/supfile.testing # -# this is the host containing the master ABS files +# this is the host containing the testing PKGBUILD files *default host=cvs.archlinux.org *default release=cvs *default delete *default use-rel-suffix *default compress -*default tag=TESTING +#*default umask=002 +*default tag=TESTING arch extra Index: pacman-lib/etc/abs/supfile.unstable diff -u pacman-lib/etc/abs/supfile.unstable:1.1 pacman-lib/etc/abs/supfile.unstable:1.2 --- pacman-lib/etc/abs/supfile.unstable:1.1 Tue Dec 5 02:30:15 2006 +++ pacman-lib/etc/abs/supfile.unstable Tue Feb 27 10:53:14 2007 @@ -9,6 +9,7 @@ *default delete *default use-rel-suffix *default compress +#*default umask=002 *default tag=CURRENT unstable

1 0

[pacman-dev] pacman locking the db when downloading with -S ?
by Andreas Radke 27 Feb '07

27 Feb '07

i found this strange behavior: while i had pacman3 -Syu downloading some updates it kept the db locked so makepkg3 couldn't check the deps. [andyrtr@workstation64 pacman3]$ rm -rf src/ && time makepkg3 -L ==> Entering fakeroot environment ==> Making package: pacman-rc 2007.02.25-1 (So 25. Feb 14:34:46 CET 2007) ==> Checking Runtime Dependencies... Fehler: unable to lock database ==> ERROR: pacman3 returned a fatal error (1): Wenn Sie sicher sind, dass nicht bereits ein Paketmanager gestartet ist, können Sie /tmp/pacman.lck entfernen ==> Checking Buildtime Dependencies... Fehler: unable to lock database ==> ERROR: pacman3 returned a fatal error (1): Wenn Sie sicher sind, dass nicht bereits ein Paketmanager gestartet ist, können Sie /tmp/pacman.lck entfernen ==> Retrieving Sources... ==> Validating source files with md5sums ==> Validating source files with sha1sums ==> Extracting Sources... It's ok that the pacman -Syu job locks the db while checking the dependencies but it should unlock them after that immediatly and maybe relock when installing the packages. Andy

3 3

[pacman-dev] CVS update of pacman-lib/pactest (pmpkg.py)
by Aaron Griffin 27 Feb '07

27 Feb '07

Date: Tuesday, February 27, 2007 @ 03:32:52 Author: aaron Path: /home/cvs-pacman/pacman-lib/pactest Modified: pmpkg.py (1.2 -> 1.3) * Fixed a pacman warning when these fake packages didn't create an (empty) .FILELIST ----------+ pmpkg.py | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) Index: pacman-lib/pactest/pmpkg.py diff -u pacman-lib/pactest/pmpkg.py:1.2 pacman-lib/pactest/pmpkg.py:1.3 --- pacman-lib/pactest/pmpkg.py:1.2 Wed Feb 21 01:33:13 2007 +++ pacman-lib/pactest/pmpkg.py Tue Feb 27 03:32:52 2007 @@ -156,9 +156,8 @@ # .INSTALL empty = 1 - for value in self.install.values(): - if value: - empty = 0 + if len(self.install.values()) > 0: + empty = 0 if not empty: mkinstallfile(".INSTALL", self.install) targets += " .INSTALL" @@ -166,7 +165,11 @@ # .FILELIST if self.files: os.system("tar cvf /dev/null * | sort >.FILELIST") - targets += " .FILELIST *" + else: + #prevent some pacman warnings... I expect a real package would + #always have at least one file... + os.system("touch .FILELIST") + targets += " .FILELIST *" # Generate package archive os.system("tar zcf %s %s" % (archive, targets))

1 0

[pacman-dev] CVS update of pacman-lib/pactest/tests (upgrade052.py)
by Aaron Griffin 27 Feb '07

27 Feb '07

Date: Tuesday, February 27, 2007 @ 03:29:02 Author: aaron Path: /home/cvs-pacman/pacman-lib/pactest/tests Modified: upgrade052.py (1.1 -> 1.2) * This test was off. pactest doesn't do all the DB work, so we need to manually add the "requiredby" information that libalpm would have written. Now it succeeds. ---------------+ upgrade052.py | 1 + 1 file changed, 1 insertion(+) Index: pacman-lib/pactest/tests/upgrade052.py diff -u pacman-lib/pactest/tests/upgrade052.py:1.1 pacman-lib/pactest/tests/upgrade052.py:1.2 --- pacman-lib/pactest/tests/upgrade052.py:1.1 Mon Feb 26 20:34:08 2007 +++ pacman-lib/pactest/tests/upgrade052.py Tue Feb 27 03:29:02 2007 @@ -6,6 +6,7 @@ lp2 = pmpkg("pkg2") lp2.provides = ["imaginary", "real"] +lp2.requiredby = [ "pkg1" ] self.addpkg2db("local", lp2) p = pmpkg("pkg2", "1.0-2")

1 0

[pacman-dev] CVS update of pacman-lib/pactest/tests (5 files)
by Dan McGee 27 Feb '07

27 Feb '07

Date: Monday, February 26, 2007 @ 20:34:08 Author: dan Path: /home/cvs-pacman/pacman-lib/pactest/tests Added: upgrade050.py (1.1) upgrade051.py (1.1) upgrade052.py (1.1) upgrade053.py (1.1) upgrade054.py (1.1) * Added 5 new upgrade tests, which check various things with depends, provides, and conflicts. - upgrade051 is known to fail- but we want to eventually make it work. - upgrade052 is Nagy's bug as reported on the ML- I think. If it isn't, let me know. ---------------+ upgrade050.py | 15 +++++++++++++++ upgrade051.py | 15 +++++++++++++++ upgrade052.py | 19 +++++++++++++++++++ upgrade053.py | 19 +++++++++++++++++++ upgrade054.py | 19 +++++++++++++++++++ 5 files changed, 87 insertions(+) Index: pacman-lib/pactest/tests/upgrade050.py diff -u /dev/null pacman-lib/pactest/tests/upgrade050.py:1.1 --- /dev/null Mon Feb 26 20:34:08 2007 +++ pacman-lib/pactest/tests/upgrade050.py Mon Feb 26 20:34:07 2007 @@ -0,0 +1,15 @@ +self.description = "Upgrade package with a conflict == depend (not installed)" + +p1 = pmpkg("pkg1") +p1.conflicts = ["pkg2"] +p1.depends = ["pkg2"] +self.addpkg(p1) + +p2 = pmpkg("pkg2") +self.addpkg(p2) + +self.args = "-U %s" % " ".join([p.filename() for p in p1, p2]) + +self.addrule("PACMAN_RETCODE=1") +self.addrule("!PKG_EXIST=pkg1") +self.addrule("!PKG_EXIST=pkg2") Index: pacman-lib/pactest/tests/upgrade051.py diff -u /dev/null pacman-lib/pactest/tests/upgrade051.py:1.1 --- /dev/null Mon Feb 26 20:34:08 2007 +++ pacman-lib/pactest/tests/upgrade051.py Mon Feb 26 20:34:08 2007 @@ -0,0 +1,15 @@ +self.description = "Upgrade to a package that provides another package" + +lp = pmpkg("pkg1") +self.addpkg2db("local", lp) + +p = pmpkg("pkg2") +p.conflicts = ["pkg1"] +p.provides = ["pkg1"] +self.addpkg(p) + +self.args = "-U %s" % p.filename() + +self.addrule("PACMAN_RETCODE=0") +self.addrule("!PKG_EXIST=pkg1") +self.addrule("PKG_EXIST=pkg2") Index: pacman-lib/pactest/tests/upgrade052.py diff -u /dev/null pacman-lib/pactest/tests/upgrade052.py:1.1 --- /dev/null Mon Feb 26 20:34:08 2007 +++ pacman-lib/pactest/tests/upgrade052.py Mon Feb 26 20:34:08 2007 @@ -0,0 +1,19 @@ +self.description = "Nagy's bug (I think) -- in progress" + +lp1 = pmpkg("pkg1") +lp1.depends = ["imaginary"] +self.addpkg2db("local", lp1) + +lp2 = pmpkg("pkg2") +lp2.provides = ["imaginary", "real"] +self.addpkg2db("local", lp2) + +p = pmpkg("pkg2", "1.0-2") +p.provides = ["real"] +self.addpkg(p) + +self.args = "-U %s" % p.filename() + +self.addrule("PACMAN_RETCODE=1") +self.addrule("PKG_EXIST=pkg1") +self.addrule("PKG_VERSION=pkg2|1.0-1") Index: pacman-lib/pactest/tests/upgrade053.py diff -u /dev/null pacman-lib/pactest/tests/upgrade053.py:1.1 --- /dev/null Mon Feb 26 20:34:08 2007 +++ pacman-lib/pactest/tests/upgrade053.py Mon Feb 26 20:34:08 2007 @@ -0,0 +1,19 @@ +self.description = "Upgrade a package with dependency on provided package (same)" + +lp1 = pmpkg("pkg1") +lp1.depends = ["imaginary"] +self.addpkg2db("local", lp1) + +lp2 = pmpkg("pkg2") +lp2.provides = ["imaginary", "real"] +self.addpkg2db("local", lp2) + +p = pmpkg("pkg1", "1.0-2") +p.depends = ["imaginary"] +self.addpkg(p) + +self.args = "-U %s" % p.filename() + +self.addrule("PACMAN_RETCODE=0") +self.addrule("PKG_VERSION=pkg1|1.0-2") +self.addrule("PKG_EXIST=pkg2") Index: pacman-lib/pactest/tests/upgrade054.py diff -u /dev/null pacman-lib/pactest/tests/upgrade054.py:1.1 --- /dev/null Mon Feb 26 20:34:08 2007 +++ pacman-lib/pactest/tests/upgrade054.py Mon Feb 26 20:34:08 2007 @@ -0,0 +1,19 @@ +self.description = "Upgrade a package with dependency on provided package (different)" + +lp1 = pmpkg("pkg1") +lp1.depends = ["imaginary"] +self.addpkg2db("local", lp1) + +lp2 = pmpkg("pkg2") +lp2.provides = ["imaginary", "real"] +self.addpkg2db("local", lp2) + +p = pmpkg("pkg1", "1.0-2") +p.depends = ["real"] +self.addpkg(p) + +self.args = "-U %s" % p.filename() + +self.addrule("PACMAN_RETCODE=0") +self.addrule("PKG_VERSION=pkg1|1.0-2") +self.addrule("PKG_EXIST=pkg2")

1 0

[pacman-dev] CVS update of pacman-lib/lib/libalpm (db.c)
by Dan McGee 26 Feb '07

26 Feb '07

Date: Monday, February 26, 2007 @ 18:32:08 Author: dan Path: /home/cvs-pacman/pacman-lib/lib/libalpm Modified: db.c (1.61 -> 1.62) * db search optimization- why don't we compile the regex once instead of once per package. ------+ db.c | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) Index: pacman-lib/lib/libalpm/db.c diff -u pacman-lib/lib/libalpm/db.c:1.61 pacman-lib/lib/libalpm/db.c:1.62 --- pacman-lib/lib/libalpm/db.c:1.61 Mon Feb 26 03:38:48 2007 +++ pacman-lib/lib/libalpm/db.c Mon Feb 26 18:32:08 2007 @@ -105,21 +105,21 @@ for(i = needles; i; i = i->next) { char *targ; + regex_t reg; if(i->data == NULL) { continue; } targ = i->data; _alpm_log(PM_LOG_DEBUG, "searching for target '%s'", targ); + + if(regcomp(&reg, targ, REG_EXTENDED | REG_NOSUB | REG_ICASE | REG_NEWLINE) != 0) { + RET_ERR(PM_ERR_INVALID_REGEX, NULL); + } for(j = _alpm_db_get_pkgcache(db, INFRQ_DESC|INFRQ_DEPENDS); j; j = j->next) { pmpkg_t *pkg = j->data; char *matched = NULL; - regex_t reg; - - if(regcomp(&reg, targ, REG_EXTENDED | REG_NOSUB | REG_ICASE | REG_NEWLINE) != 0) { - RET_ERR(PM_ERR_INVALID_REGEX, NULL); - } /* check name */ if (regexec(&reg, pkg->name, 0, 0, 0) == 0) { @@ -130,6 +130,8 @@ matched = pkg->desc; } /* check provides */ + /* TODO: should we be doing this, and should we print something + * differently when we do match it since it isn't currently printed? */ else { for(k = pkg->provides; k; k = k->next) { if (regexec(&reg, k->data, 0, 0, 0) == 0) { @@ -138,13 +140,15 @@ } } } - regfree(&reg); if(matched != NULL) { - _alpm_log(PM_LOG_DEBUG, " search target '%s' matched '%s'", targ, matched); + _alpm_log(PM_LOG_DEBUG, " search target '%s' matched '%s'", + targ, matched); ret = alpm_list_add(ret, pkg); } } + + regfree(&reg); } return(ret);

1 0

[pacman-dev] CVS update of pacman-lib (3 files)
by Dan McGee 26 Feb '07

26 Feb '07

Date: Monday, February 26, 2007 @ 10:10:54 Author: dan Path: /home/cvs-pacman/pacman-lib Modified: TODO.dan (1.15 -> 1.16) contrib/Makefile.am (1.2 -> 1.3) scripts/Makefile.am (1.6 -> 1.7) * TODO updates. * Makefile.am updates for Aaron's move of re-pacman to contrib. ---------------------+ TODO.dan | 15 +++++++++++++-- contrib/Makefile.am | 1 + scripts/Makefile.am | 1 - 3 files changed, 14 insertions(+), 3 deletions(-) Index: pacman-lib/TODO.dan diff -u pacman-lib/TODO.dan:1.15 pacman-lib/TODO.dan:1.16 --- pacman-lib/TODO.dan:1.15 Wed Feb 21 23:36:02 2007 +++ pacman-lib/TODO.dan Mon Feb 26 10:10:53 2007 @@ -84,9 +84,20 @@ differ here. Rewrite makepkg to use terminal-safe coloring/bolding. tput utility should -allow us to do this. +allow us to do this. Make universal message functions for systemwide use, +including all pacman utilites- abs, pacman-optimize, etc. -Bugs/FRs to smash: 6468, 6437, 6430?, 6420, 6404, 6389, 6312?, 6284, 6273?, 6255?, 6208, 5987, 5885, 5571, 4182, 3492, 2810?, 1769, 1588, 1571 +Bugs/FRs to smash: 6468, 6437, 6430?, 6420, 6404, 6389, 6312?, 6284, 6273?, +6255?, 6208, 5987, 5885, 5571, 4182, 3492, 2810?, 1769, 1588, 1571 + +Remove _alpm from function names now that we have SYMHIDDEN and static +declarations. + +Remove alpm.c, put functions where they should be. + +Update doxygen comments, they may need some work. Try to document all of the +private internal functions too- it helps a ton for people just getting a +start on pacman hacking. Other smaller things: --------------------- Index: pacman-lib/contrib/Makefile.am diff -u pacman-lib/contrib/Makefile.am:1.2 pacman-lib/contrib/Makefile.am:1.3 --- pacman-lib/contrib/Makefile.am:1.2 Fri Feb 23 03:07:48 2007 +++ pacman-lib/contrib/Makefile.am Mon Feb 26 10:10:53 2007 @@ -2,5 +2,6 @@ bash_completion \ pacsearch \ pacdiff \ + re-pacman \ zsh_completion Index: pacman-lib/scripts/Makefile.am diff -u pacman-lib/scripts/Makefile.am:1.6 pacman-lib/scripts/Makefile.am:1.7 --- pacman-lib/scripts/Makefile.am:1.6 Thu Feb 22 16:34:52 2007 +++ pacman-lib/scripts/Makefile.am Mon Feb 26 10:10:53 2007 @@ -11,7 +11,6 @@ rankmirrors \ repo-add \ repo-remove \ - re-pacman \ updatesync EXTRA_DIST = $(bin_SCRIPTS)

1 0