- Arch-dev-public - lists.archlinux.org

[arch-dev-public] restructure our printing system
by Andreas Radke 22 Jun '07

22 Jun '07

after talking to Till Kampeter at Linuxtag in Berlin and reading around how other distributions are packaging the printer drivers i want to restructure our packages(cups, gutenprint, foomatic, gimp-print-lprng,cups-pdf....): - package only still developed software - stick with stable tree releases - drop outdated packages/move to AUR rarely - improve features the last point will force us to have almost all printing related packages in either current or extra. now they are splitted and can not depend on each other. i suggest to move such hardware related packages + virtual printers all into current/system or current/office. but extra would also be fine for me. where's the better location? AndyRTR

2 4

Re: [arch-dev-public] [pacman-dev] pacman screws up permissions
by Dan McGee 20 Jun '07

20 Jun '07

On 6/20/07, Thomas Bächler <thomas.baechler(a)gmx.de> wrote: > I just installed the ntfs-3g package with pacman 3.0.5-1: > > $ /bin/ls -lhF /bin/ntfs-3g /usr/man/man8/ntfs-3g.8.gz > -rwxrwxrwx 1 root root 36K 20. Jun 01:45 /bin/ntfs-3g* > -rwxrwxrwx 1 root root 3,0K 20. Jun 01:44 /usr/man/man8/ntfs-3g.8.gz* > > The permissions in the tarfile are 755 for /bin/ntfs-3g (and I suppose > they are 644 for the manpage, didn't check that). This behaviour can > cause critical bugs and in this case is security-relevant, as a user > could change the ntfs-3g binary, which is executed at boot time on many > systems. This has to be fixed FAST. Has anyone read my recent emails? I've said the same thing, and I think it is due to a "fix" that didn't get tested well in pacman 3.0.5. I think I'm going to roll back that fix tonight unless someone else can come up with a solution. Relevant stuff: http://archlinux.org/pipermail/arch-dev-public/2007-June/001048.html http://archlinux.org/pipermail/pacman-dev/2007-June/008567.html http://archlinux.org/pipermail/pacman-dev/2007-June/008567.html http://bugs.archlinux.org/task/7461 http://bugs.archlinux.org/task/7323 -Dan

2 2

[arch-dev-public] Cleanup of some base libs
by Dan McGee 20 Jun '07

20 Jun '07

While trying to figure out my libtool libarchive issue, I looked at the PKGBUILDs for acl and attr and was pretty scared at what I saw. I attempted to clean them up a lot, and I think I succeeded, but I wanted some testing from you guys first before I push these to testing and then maybe to current. I also want to make sure no one sees an issue with building them this way. I set up a small repo here: [baseclean] Server = http://archlinux.org/~dan/baseclean The repo has the following packages (I rebuilt those that depend directly on acl/attr): acl, attr, libarchive, pacman (because libarchive has been upgraded), and xfsdump. The one package missing that should be here is coreutils, but I had a build failure (not sure if this is related to the gcc 4.2 upgrade). In addition, has anyone else noticed this issue- http://bugs.archlinux.org/task/7461? It is kind of a big deal, and I'm going to be gone starting tomorrow for the entire weekend so I want to find some resolution before then. -Dan Note to self: add some comments to the acl/attr PKGBUILDs explaining those weird variable settings used in the install line (include/builddefs, buildmacros, etc.).

1 1

[arch-dev-public] libarchive, pacman, and libtool-slaying
by Dan McGee 20 Jun '07

20 Jun '07

I'm sending this to two lists to see who can offer some insight, as I tried and failed earlier to get pacman to correctly build with a newer version of libarchive. I think it may deal with having la files in the package, but I am not sure so I'll outline what I've tried and know so far. Libarchive website: http://people.freebsd.org/~kientzle/libarchive/ Current version: 2.2.3 Current Arch Linux version: 1.3.1-2 As you can see, we are a ways behind. I up-ed the PKGBUILD for libarchive, rebuilt it without problems (as far as I can tell), and then pacman -U <new libarchive> and tried to compile pacman. The ldd output showed that it correctly linked against the new libarchive.so.2, but it had somehow also linked against libarchive.so.1. I tried rebuilding libarchive using options=(!libtool), but that didn't seem to fix anything- it actually just spit some more errors saying libarchive was missing la files and such. OK, long explanation, but it comes down to this: 1. How can we get pacman to compile with libarchive without needing the la files? libdownload seems to work fine without them, etc. 2. Where is this mysterious link to libarchive.so.1 coming from when it isn't even present on my system anymore? This applies to both the most recent CVS release and our GIT tree at projects.al.org. -Dan

4 5

[arch-dev-public] Updating gcc3 package
by Jason Chu 20 Jun '07

20 Jun '07

Does anyone have any problems with me updating the gcc3 package to gcc3.4? It looks like the only packages that depend on it in extra are qemu and kvm-modules. Like tpowa said, kvm doesn't compile with gcc 3.3 but will with gcc 3.4. It seems that qemu doesn't care, just as long as it's not gcc 4. Do any packages depend on gcc 3.3? Jason

5 4

[arch-dev-public] curl rebuild TODO, archstats only left!
by Tobias Powalowski 19 Jun '07

19 Jun '07

Hi in order to move in the stuff fast would be great if Simo or anyone else would fix archstats, it doesn't compile anymore with latest curl. please fix this soon that we can start moving in the stuff to current/extra thanks greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa(a)archlinux.org

2 3

[arch-dev-public] Devices >2TB
by Paul Mattal 19 Jun '07

19 Jun '07

Anyone know if our standard kernels are capable of seeing/handling devices that are >2TB in size? I know you need 48-bit LBA to do this, but clearly 48-bit LBA is supported on the machines I'm using and in our kernel. The 2TB limit, as I understand it, comes from something *somewhere* being limited to a 32-bit address. Is it the kernel, or perhaps my SATA controller somehow? Or the sata_nv driver? The setup is that I'm hooking up a hardware-raid-enclosure external cabinet up via the ESATA port to the SATA controller built into the NVidia NForce 430 chipset on the motherboard. We can't see more than 2TB. Thanks for any helpful hints that people may know! - P

2 3

[arch-dev-public] DB rebuilds
by Dan McGee 19 Jun '07

19 Jun '07

I just threw up a pacman release (3.0.5) that fixes the following issue (http://bugs.archlinux.org/task/7338): conflicts lines from packages were not correctly added to a sync DB, causing issues when it comes to replacing stock packages with an -svn version, for example. Two things this likely affects: 1. If version 3.0.4 of pacman is installed on al.org, we should probably upgrade to 3.0.5 to get the fixed repo-add script (which is used by gensync, which may be used by our other scripts?) 2. The community DB should probably be rebuilt completely to ensure all the conflicts lines are now present, if this is a problem. Questions on this? Let me know if I wasn't clear about anything here. -Dan

2 2

[arch-dev-public] reverse staging idea
by Paul Mattal 18 Jun '07

18 Jun '07

Since I know there have been complaints about packages remaining in the ftp directories when new ones are uploaded, how about we modify the /arch/db-* update scripts run by the devs to move old versions of updated packages into ~/staging/<repo>/old? This makes the default behavior that they stick around but aren't cluttering the ftp directory. Just an idea I had that I didn't want us to lose. - P

6 9

[arch-dev-public] Away for a while, the hunt for funds
by Alexander Baldeck 18 Jun '07

18 Jun '07

Hey all, as you may have noticed I've stepped back from my enthusiasm a little on and after Linuxtag. This is primarily because I'm a little short on cash these days. Several things aren't going as well as I would like them to. Anyways, I'm on a job hunt atm which is probably taking most of my time during the next few days. On the other hand, if anyone has hints you're welcome to forward contacts. ;) I will work on the most cirtical packages as much as I can but if something takes to long, feel free to bump/fix/drop them. Cheers, Alex

4 3