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

Re: [arch-dev-public] gcc-4.4.0 toolchain rebuild with query about gcc-gcj and related packages
by Andreas Radke 27 Apr '09

27 Apr '09

To me it seems new gcc is more restrictive with missing headers. Go-OOo failed with a missing printf inclusion. Don't push the toolchain too fast to core. Give us and the upstream devs enough time to find fixes. example: http://cvs.fedoraproject.org/viewvc/rpms/openoffice.org/devel/openoffice.or… -Andy

2 1

Re: [arch-dev-public] [arch-commits] Commit in htdig/trunk (PKGBUILD)
by Pierre Schmitz 26 Apr '09

26 Apr '09

Am Samstag, 25. April 2009 16:29:03 schrieb Giovanni Scafora: > ln -s /srv/http/cgi-bin/htsearch ${pkgdir}/usr/bin || return 1 I thnik it should be the other way round. Imho no package should install anything into /srv. What do you guys think about this? -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre(a)jabber.archlinux.de WWW http://www.archlinux.de

6 11

Re: [arch-dev-public] [arch-general] [arch-commits] Commit in htdig/trunk (PKGBUILD)
by Daenyth Blank 26 Apr '09

26 Apr '09

On Sat, Apr 25, 2009 at 15:01, Abhishek Dasgupta <abhidg(a)gmail.com> wrote: > 2009/4/25 Pierre Schmitz <pierre(a)archlinux.de>: >> Am Samstag, 25. April 2009 17:36:19 schrieb Dan McGee: >>> Installing into srv is no different than installing into /home/, >>> IMO. It might be worse as it presents a relatively big security risk >>> for those that do run public facing services, and suddenly a new >>> script has been made available for web site users to run. >> >> If we agree to this we should add such a rule to namcap. >> > > Removing 'srv/' in Namcap/directoryname.py will make namcap > issue a warning about a file in a non-standard directory. > > -- > Abhishek > +1 to this change.

1 0

[arch-dev-public] [signoff] openssl 0.9.8k-2
by Pierre Schmitz 25 Apr '09

25 Apr '09

Removing the rpath as suggested in http://bugs.archlinux.org/task/14367 The previous rpath was /usr/lib; so afaik no security problem. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre(a)jabber.archlinux.de WWW http://www.archlinux.de

3 2

[arch-dev-public] Integrity Check x86_64 24-04-2009
by repomaint＠archlinux.org 24 Apr '09

24 Apr '09

======================================== = Integrity Check x86_64 of core,extra = ======================================== Performing integrity checks... ==> parsing pkgbuilds ==> checking mismatches ==> checking archs ==> checking dependencies ==> checking makedepends ==> checking for circular dependencies Missing Dependencies ---------------------- archboot --> 'netkit-telnet>=0.17-8' archboot --> 'wlan-ng26>=0.2.9-2' archboot --> 'atl2>=2.0.5-2' Missing Makedepends --------------------- v86d --> 'kernel26<2.6.29' gnome-speech --> 'espeak' Repo Hierarchy for Makedepends -------------------------------- core/crda depends on extra/python-m2crypto core/iputils depends on extra/opensp core/iputils depends on extra/libxslt core/iputils depends on extra/docbook-xsl core/madwifi-utils depends on extra/sharutils core/e2fsprogs depends on extra/bc core/syslog-ng depends on extra/libcap core/sqlite3 depends on extra/tcl core/ca-certificates depends on extra/ruby core/madwifi depends on extra/sharutils Circular Dependencies ----------------------- gcc-gcj>eclipse-ecj>gcc-gcj Summary --------- Missing PKGBUILDs: 0 Invalid PKGBUILDs: 0 Mismatching PKGBUILD names: 0 Duplicate PKGBUILDs: 0 Invalid archs: 0 Missing (make)dependencies: 5 Repo hierarchy problems: 10 Circular dependencies: 1

1 0

[arch-dev-public] Integrity Check i686 24-04-2009
by repomaint＠archlinux.org 24 Apr '09

24 Apr '09

====================================== = Integrity Check i686 of core,extra = ====================================== Performing integrity checks... ==> parsing pkgbuilds ==> checking mismatches ==> checking archs ==> checking dependencies ==> checking makedepends ==> checking for circular dependencies Missing Dependencies ---------------------- archboot --> 'netkit-telnet>=0.17-8' archboot --> 'wlan-ng26>=0.2.9-2' archboot --> 'atl2>=2.0.5-2' Missing Makedepends --------------------- v86d --> 'kernel26<2.6.29' gnome-speech --> 'espeak' Repo Hierarchy for Makedepends -------------------------------- core/crda depends on extra/python-m2crypto core/iputils depends on extra/opensp core/iputils depends on extra/libxslt core/iputils depends on extra/docbook-xsl core/madwifi-utils depends on extra/sharutils core/e2fsprogs depends on extra/bc core/syslog-ng depends on extra/libcap core/sqlite3 depends on extra/tcl core/ca-certificates depends on extra/ruby core/madwifi depends on extra/sharutils Circular Dependencies ----------------------- gcc-gcj>eclipse-ecj>gcc-gcj Summary --------- Missing PKGBUILDs: 0 Invalid PKGBUILDs: 0 Mismatching PKGBUILD names: 0 Duplicate PKGBUILDs: 0 Invalid archs: 0 Missing (make)dependencies: 5 Repo hierarchy problems: 10 Circular dependencies: 1

1 0

[arch-dev-public] dhclient is up for grabs
by Thayer Williams 24 Apr '09

24 Apr '09

Hi all, Can someone adopt the dhclient package from me? It's outdated and I don't really have the time troubleshoot/patch the latest version, not to mention I'm not actively using the tool myself. I believe it's popular among the Wicd crowd. Cheers

2 1

[arch-dev-public] [signoff] dnsutils 9.6.0.P1-2
by Jan de Groot 23 Apr '09

23 Apr '09

Please signoff for both architectures. This is just a rebuild of the package with the replaces=('host') option set. This is done because the "host" package is 2 years old and doesn't work correctly (FS#14158). Looking at the small size of dnsutils, I see no need to keep an old resolving package with old outdated and insecure resolver code in the repositories.

2 1

[arch-dev-public] Resigning
by Tom K 23 Apr '09

23 Apr '09

Hi all. The practical effect of this message is precisely nothing, as I have been inactive for quite a while now. For the last few months, real life has been increasingly demanding, but I was hoping I would find a way to accommodate Arch activities alongside the usual chaos and mayhem. It's now clear that this is not going to happen any time soon, so I've orphaned my remaining packages, and I'm now returning the key to the Arch executive washroom. I hope to return at some point, but I can't say when that will be. Being an Arch dev has been a revelation to me, and it has been wonderful working with you all. I will continue to be a keen Arch user, and will do my best to contribute in some capacity, as time permits. I would like to retain my subscription to this list, read-only of course, and I will discuss my status as forum mod and irc op with the respective teams. I have no doubt that Arch will continue to thrive, guided by an extraordinarily committed dev team, and supported by an enthusiastic user community. I wish you all the very best of luck. Go n-eírí an bóthar leat Tom K.

10 11

[arch-dev-public] Nautilus extension for packages
by K. Piche 21 Apr '09

21 Apr '09

Hey everyone, For fun I hacked together a Nautilus extension to add an extra file property page for pacman packages. I've got a binary package cleverly called nautilus-pacman available at http://kpiche.archlinux.ca/repo/nautilus-pacman-0.1-1-i686.pkg.tar.gz or use my repo: [kpiche] Server = http://kpiche.archlinux.ca/repo The package also adds a mime type and a mime type icon. Install then logout & login or run 'nautilus -q'. No source yet as I wish to scan for embarrassments first. :) Some notes and things I found out: - It's not amazingly useful since most of us probably use the CLI and don't manage packages with a file manager. Could add some "Install" context menus later perhaps. - The property page is ugly, sorry. not sure the best way to display the other package attributes just yet - No i18n - The extra mime bits are not tied to Nautilus and should be in a general package - libalpm could use a pkgconfig file for use in autoconf. - You can't initialize, release, then initialize the library in the same instance of a program. Took a while to find those SIG11's. - Curious if we have a logo that would look better as an icon, maybe an outline? Later, K -- K. Piche <kpiche(a)rogers.com>

2 1