- Pacman-dev - lists.archlinux.org

[pacman-dev] release roadmap?
by VMiklos 01 Mar '06

01 Mar '06

hi all just wanted to suggest let's make a list of bugs that blocks us to release a public rc (and then the first stable) release of pacman3 we have several ideas, for example replacing the ugly chroot system() call, adding gettext support, etc, but these features were not in pacman2, and i think they're not "musthave" so what are the points from TODO that must be solved before a release? i think the only one is the lack of handling of package conflicts during packages replacement, and maybe the manpages of public funtions (via doxygen) udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

3 37

[pacman-dev] [PATCH] pacman: disable progressbar by default if the output is redirected
by VMiklos 01 Mar '06

01 Mar '06

hi http://darcs.frugalware.org/darcsweb/darcsweb.cgi?r=pacman;a=plain_commitdi…; idea from wget ;) udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 1

[pacman-dev] [PATCH] remove corrupted packages if requested
by VMiklos 28 Feb '06

28 Feb '06

hi http://frugalware.org/~vmiklos/patches/libpacman-proposed/unlink_corrupt.di… udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

1 0

[pacman-dev] [PATCH] use sudo everywhere for makepkg -iS
by VMiklos 28 Feb '06

28 Feb '06

hi http://frugalware.org/~vmiklos/patches/libpacman-proposed/makepkg_install.d… if a package already built, and makepkg was called with -iS, then we should use sudo to install the package. if there were no -S and we're not root, then we should inform the user about we can't auto-install the packages - the same way as we do with the dependency auto-install. as the package install code was duplicated, i've moved it to a separate function udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

1 0

[pacman-dev] Away
by Aurelien Foret 24 Feb '06

24 Feb '06

I'll be away for the next 3 or 4 days (skiing). I hope the patch queue will not inflate too much in the meantime ;) -- Aurelien

1 0

[pacman-dev] [PATCH] whitespace fixes for libalpm
by VMiklos 24 Feb '06

24 Feb '06

hi http://frugalware.org/~vmiklos/patches/libpacman-proposed/alpm_db_cosmetics… somehow these tabs are replaced with spaces udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

3 5

[pacman-dev] test/sync999 - pacman segfault
by Aurelien Foret 23 Feb '06

23 Feb '06

Hi, Running pactest today showed that sync999 test case no longer works. Eventually, pactest return on investment does not seem null anymore :) It seems the flaw appeared with lib/libalpm/conflict.c:1.15. The same test with conflict.c:1.14 is ok. Here's the log from pactest: flow2: PM_OPT_DBPATH set to 'var/lib/pacman' flow2: PM_OPT_CACHEDIR set to 'var/cache/pacman/pkg' debug: opening database 'local' debug: opening database 'sync' :: Starting local database upgrade... flow1: checking for package replacements debug: loading package cache (infolevel=0x3) for repository 'sync' flow1: checking for package upgrades debug: loading package cache (infolevel=0x3) for repository 'local' debug: CACHE: fetching 'sync/pkg1' flow2: pkg1-1.0-1 elected for upgrade (1.0-1 => 1.0-2) debug: CACHE: fetching 'sync/pkg2' flow2: pkg2-1.0-1 elected for upgrade (1.0-1 => 1.0-2) resolving dependencies... flow1: resolving targets dependencies done. looking for inter-conflicts... flow1: looking for unresolvable dependencies debug: CACHE: fetching 'local/pkg1' debug: CACHE: fetching 'local/pkg2' flow1: looking for conflicts debug: targs vs db: found pkg2 as a conflict for pkg1 debug: targs vs targs: found pkg2 as a conflict for pkg1 debug: db vs targs: found pkg1 as a conflict for pkg2 flow2: package 'pkg1' is conflicting with 'pkg2' debug: CACHE: fetching 'local/pkg2' debug: package 'pkg1' provides its own conflict debug: resolving package 'pkg1' conflict flow2: electing 'pkg2' for removal flow2: removing 'pkg2' from target list flow2: package 'pkg2' is conflicting with 'pkg1' debug: CACHE: fetching 'local/pkg1' When handling conflict pkg1, pkg2 is removed from targets. Then, the library tries to handle pkg2 conflict... but find_pkginsync() returns NULL... I've committed a fix (sync.c:1.66) to skip conflict resolution in such a case. Thoughts? The test suite is ok with it ;) -- Aurelien

2 4

[pacman-dev] Sorry, test mail for me :)
by Christian Hamar 23 Feb '06

23 Feb '06

Hey. Just a test email, sorry from list members, i need to figure out why i got bounced on this list :( Regards -krix-

1 0

[pacman-dev] makepkg: removing empty directories?
by VMiklos 21 Feb '06

21 Feb '06

from makepkg: 1.12 (aurelien 16-Feb-06): # remove empty directories 1.12 (aurelien 16-Feb-06): if [ "`check_option NOEMPTYDIRS`" ]; then 1.12 (aurelien 16-Feb-06): msg "Removing empty directories..." 1.12 (aurelien 16-Feb-06): find pkg -mindepth 1 -type d -empty -exec rmdir {} \; 1.12 (aurelien 16-Feb-06): fi cmiiw, but openssh creates an empty /var/empty directory and it _does_ need it. any idea how to solve this problem? for now, i haven't merged this hunk to our tree udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 2

[pacman-dev] Fwd: [ Re: Patch queue ]
by VMiklos 21 Feb '06

21 Feb '06

----- Forwarded message from Christian Hamar <krics(a)linuxforum.hu> ----- > Date: Mon, 20 Feb 2006 01:27:19 +0100 > From: Christian Hamar <krics(a)linuxforum.hu> > To: VMiklos <vmiklos(a)frugalware.org> > Subject: Re: [pacman-dev] Patch queue > X-Mailer: Evolution 2.4.2.1 Frugalware Linux Distribution > > 2006. 02. 18, szombat keltezéssel 16.38-kor VMiklos ezt írta: > > On Fri, Feb 17, 2006 at 11:37:46PM +0100, Aurelien Foret <aurelien(a)archlinux.org> wrote: > > > Hi all, > > > > > > Following today's discussion on the ML, here is the list of pending > > > patches, with an updated status. > > > If one got lost during the struggle, thanks to let me know. > > > > > > > > > [6] doxygen: support for autotools > > > http://www.archlinux.org/pipermail/pacman-dev/2006-January/000170.html > > > > > > Commited. But I had to comment the part in the file doc/Makefile.am for now. > > > It generates the following error: > > > doc/Makefile.am:22: man_MANS must be set with `=' before using `+=' > > Hm. I don't understand why this problem occurs at you. If you view the > Makefile.am then you can see that there is a man_MANS = (without +) > > That man_MANS "runs" everytime. So there is no way to just only man_MANS > += "run" because the man_MANS = isn't in any ifdef define. > > Ps.: Why i'm banned from the pacman list ?? I saw that > krics(a)linuxforum.hu too many bounced messages ... But my email works > fine. Any idea ?! > > Regards > -krix- ----- End forwarded message ----- udv / greetings, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org

2 4