- Arch-general - lists.archlinux.org

Re: [arch-general] [arch-dev-public] Allow comments on closed bugs?
by Heiko Baums 14 Mar '10

14 Mar '10

Am Sat, 13 Mar 2010 10:58:24 +0100 schrieb Pierre Schmitz <pierre(a)archlinux.de>: > Yes, there are sometimes situations where I wanted to add a more or > less important comment to a bug reports but it was just closed. > > In the other hand I see the problems of never ending discussions and > flame wars. In other bug trackers I haven't seen never ending discussions and flame wars on closed bugs, yet. Sometimes long discussions happen on open bugs, but usually in a factual manner, and usually there's a reason for this, because it's a controversial issue. If a comment is written on a closed bug it's just to give some more details, because the fix is not quite sufficient or could be made still better or the like. And in cases in which it's possible to reopen a bug directly without sending a request, I also haven't seen exploitations. Usually the bug is reopened once or twice to give another argument or another aspect. But then it's alright. How many bug reports are actually invalid because of an imperfect knowledge or (search) laziness of the reporter? How many bug reports are of the type Aaron Griffin has mentioned before (Feature request, closed as "won't implement", reopend with "but it's a good feature", denied with "we won't implement this, wait for upstream", reopened, denied)? Are there really so many of them? I have my doubts. Or is this more the developer's fear that this could happen? And as I've written in other e-mails, don't see only your developer's point of view. See also the user's and reporter's point of view and how a certain bug handling (early closings, forcing reopening requests (begging), etc.) is or at least can be received by the user/reporter. Btw., comments on closed bugs is more or less a minor issue. The bigger issue is the early bug closing. ;-) Heiko

4 3

[arch-general] Where to install python apps: /usr/lib/python2.6/site-packages/xyz??
by David C. Rankin 13 Mar '10

13 Mar '10

Guy, I know nothing about python other than what it is. I need to install repoview-0.6.5 on my arch server, but I'm not sure where. Looking at the other python apps like cairo, FusionIcon, etc.. thay seem to be installed as a subdirectory to: /usr/lib/python2.6/site-packages/ The repoview directory contains: drwxr-xr-x 3 david david 4096 Feb 19 13:31 templates -rw-r--r-- 1 david david 3457 Feb 19 13:31 ChangeLog -rw-r--r-- 1 david david 18009 Mar 3 2005 COPYING -rw-r--r-- 1 david david 708 Jul 19 2007 README -rw-r--r-- 1 david david 2634 Sep 27 2007 repoview.8 -rwxr-xr-x 1 david david 32932 Feb 19 13:31 repoview.py Do I just move the directory to /usr/lib/python2.6/site-packages/? Then is there something else I need to do to "register" (for lack of better words) repoview somewhere so python knows it is there? Then what about the man page? Anything special required to do I just move it to /usr/share/man or /usr/local/man? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com

4 8

[arch-general] gbd missing from extra?
by richard terry 13 Mar '10

13 Mar '10

couldn't retreive the gnu debugger from pacman -S gdb, and looking in the extra repo it didn't seem to be present. any reason? Richard

4 4

Re: [arch-general] [arch-dev-public] Allow comments on closed bugs?
by Xavier Chantry 13 Mar '10

13 Mar '10

On Fri, Mar 12, 2010 at 11:39 PM, Allan McRae <allan(a)archlinux.org> wrote: > On 13/03/10 08:35, Aaron Griffin wrote: >> >> Does anyone have an opinion on this? >> >> In my eyes, I imagine the kind of people who want this feature simply >> wish to argue about the closing. I've had to deal with enough PM >> requests in the past to know that this _does_ happen. >> >> Opinions? >> > > I really do not see the need. > > If a bug is wrongly closed -> request a reopen. > If you just want to confirm a bug has been fixed, there is no need... we > already closed the bug report. > If there is a "better" fix, reopen request or new bug report. > Closing bugs should not be a race, I had several times the feeling that a bug was closed too fast and it can indeed be annoying. Ideally the one who opened the bug should give an ACK for having their bug closed. There is always something to say. At least a confirmation that the bug was fixed. Eventually a comment about how it was fixed. And you might have additional information / explanation / clarification that is mostly interesting for the people who followed that bug. It seems completely stupid to need a reopen request just to do that.

3 2

Re: [arch-general] Customising arch iso
by Dieter Plaetinck 12 Mar '10

12 Mar '10

On Fri, 12 Mar 2010 12:17:07 +0000 Damien Churchill <damoxc(a)gmail.com> wrote: > On 12 March 2010 12:14, Dieter Plaetinck <dieter(a)plaetinck.be> wrote: > > you can also build your own iso's using archiso. > > it's pretty easy, although you need archiso from git and you must > > let it look in a repository that contains a 2.6.33 package (ie > > archlinux testing) > > > > Dieter > > > > Ok cool, thanks! > > I'm just going to try installing using the core cd and then copying > the kernel and firmware packages over via flash, if that fails too > then I'll resort to creating my own cd! you could also try a netinstall cd and enable the testing repository in /tmp/pacman.conf. IIRC aif (the installer) uses pacman with that config file, so it might just work, although i never tried it myself. if you are not afraid of looking at bash scripts, look at the source code of aif then you'll see how exactly it works. Dieter

6 9

[arch-general] LTS kernel still boots but MPPC patched one does not after manual updates
by Nigel Henry 12 Mar '10

12 Mar '10

Big problemo. Wanting to get access to my sons MS vpn server which needs MPPC, I found and installed an MPPC patched kernel26, and MPPC patched ppp. No problems so far, and both the LTS, and the MPPC patched kernels booted with no problems. My Arch install hadn't been updated since 20090928, and as accessing the vpn server and retrieving the shares still wasn't working, I did a pacman -Sy, and pacman -Su hoping that some update might resolve the problem. After saying yes to a bunch of stuff to do with klibc (replacing packages), pacman -Su failed saying kdelib needs phonon. Can't install phonon because it wants to remove qt (qt4). I have KDEmod3 so there is no need for phonon anyway. Not the best way to do a full system upgrade, but I went at it manually, working my way through starting at (A). Some packages wont upgrade, wanting to remove mkinitcpio, which you can't remove as it's needed by the kernels. Others didn't want to upgrade saying warning: provider package was selected (that was resolved later on during my manual upgrading). All went ok the first day 20090309, and the only thing I needed to say yes to was replacing kernel-headers with linux-api-headers. The next morning I booted with the MPPC patched kernel with no problems, just to see if any of the updates had resolved the vpn problem, but no. Rebooted with the LTS kernel, and continued with the updates, rebooting from time to time with the LTS kernel to make sure that nothing had broken. Got as far as ntp, then had a go at gdm, which I'd been putting off (I've had problems with that before). rebooted after that, and gdm failed with the below output. gdm (gdm-binary:2033) couldn't connect to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket No such file or directory Having already had the machine down one day, working in runlevel 1 to resolve the missing libpng12 problem (that was on the 8th march) I was a bit T'd off now, but startx worked, so I reinstalled the previous gdm which thankfully worked. I'd now had enough for the days work, so shut down. Day 20100311. Now the manure starts to hit the fan. Tried to boot the MPPC patched kernel, which failed with: cannot find /dev/sda7, device does not exist. Gave udev time, but nothing. Tried the MPPC failsafe kenel, but the same there. Tried the LTS kernel, and thankfully that booted ok. Googled a lot, and found references to the problem, but didn't see any fixes. One mentioned udev, and knowing that the udev update had been pulled in by one of the packages I'd updated, I looked at /etc/udev/rules.d, and udev.rules was showing as udev.rules.pacnew (I presume that is due to the new mkinitcpio and mkinitcpio-busybox using mdev, but mkinitcpio wont upgrade, claiming that a bunch of files still exist.). I renamed udev.rules.pacnew to udev.rules, and rebooted with the MPPC kernel, but it still wont boot. Tried reinstalling MPPC patched kernel, but no change. Original install output below (when it booted ok prior to my manual updating fiasco), followed by the install output from the reinstall (which still wont boot). Had to remove madwifi, and ndiswrapper to originally install this kernel. :: madwifi: requires kernel26>=2.6.30 :: ndiswrapper: requires kernel26>=2.6.30 [root@myhost Archlinux-mppc-kernel]# pacman -U kernel26-2.6.24.3-3-i686.pkg.tar.gz loading package data... checking dependencies... (1/1) checking for file conflicts [#####################] 100% (1/1) upgrading kernel26 [#####################] 100% >>> >>> If you use the LILO bootloader, you should run 'lilo' before rebooting. >>> >>> Updating module dependencies. Please wait ... >>> MKINITCPIO SETUP >>> ---------------- >>> If you use LVM2, Encrypted root or software RAID, >>> Ensure you enable support in /etc/mkinitcpio.conf . >>> More information about mkinitcpio setup can be found here: >>> http://wiki.archlinux.org/index.php/Mkinitcpio >>> Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image "default" ==> Running command: /sbin/mkinitcpio -k 2.6.24-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img :: Begin build :: Parsing hook [base] :: Parsing hook [udev] :: Parsing hook [autodetect] :: Parsing hook [pata] :: Parsing hook [scsi] :: Parsing hook [sata] :: Parsing hook [keymap] :: Parsing hook [filesystems] :: Generating module dependencies :: Generating image '/boot/kernel26.img'...SUCCESS ==> SUCCESS ==> Building image "fallback" ==> Running command: /sbin/mkinitcpio -k 2.6.24-ARCH -c /etc/mkinitcpio.d/kernel26-fallback.conf -g /boot/kernel26-fallback.img :: Begin build :: Parsing hook [base] :: Parsing hook [udev] :: Parsing hook [ide] ERROR: module 'ide[-_]gd[-_]mod' not found :: Parsing hook [pata] :: Parsing hook [scsi] :: Parsing hook [sata] :: Parsing hook [usbinput] :: Parsing hook [raid] :: Parsing hook [filesystems] :: Generating module dependencies :: Generating image '/boot/kernel26-fallback.img'...SUCCESS ==> SUCCESS [root@myhost Archlinux-mppc-kernel]# pacman -U ppp-2.4.4-6-i686.pkg.tar.gz loading package data... checking dependencies... (1/1) checking for file conflicts [#####################] 100% (1/1) upgrading ppp [#####################] 100% [root@myhost Archlinux-mppc-kernel]# Reinstall output: [djmons@myhost ~]$ cd Downloads/Archlinux-mppc-kernel [djmons@myhost Archlinux-mppc-kernel]$ su Password: [root@myhost Archlinux-mppc-kernel]# pacman -U kernel26-2.6.24.3-3-i686.pkg.tar.gz loading package data... checking dependencies... (1/1) checking for file conflicts [#####################] 100% (1/1) upgrading kernel26 [#####################] 100% >>> >>> If you use the LILO bootloader, you should run 'lilo' before rebooting. >>> >>> Updating module dependencies. Please wait ... >>> MKINITCPIO SETUP >>> ---------------- >>> If you use LVM2, Encrypted root or software RAID, >>> Ensure you enable support in /etc/mkinitcpio.conf . >>> More information about mkinitcpio setup can be found here: >>> http://wiki.archlinux.org/index.php/Mkinitcpio >>> Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image "default" ==> Running command: /sbin/mkinitcpio -k 2.6.24-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img :: Begin build :: Parsing hook [base] :: Parsing hook [udev] :: Parsing hook [autodetect] /lib/initcpio/functions: line 7: resolve-modalias: command not found /lib/initcpio/functions: line 7: resolve-modalias: command not found Whole bunch of these lines until autodetect gives up /lib/initcpio/functions: line 7: resolve-modalias: command not found /lib/initcpio/functions: line 7: resolve-modalias: command not found :: Parsing hook [pata] :: Parsing hook [scsi] :: Parsing hook [sata] :: Parsing hook [keymap] :: Parsing hook [filesystems] :: Generating module dependencies :: Generating image '/boot/kernel26.img'...SUCCESS ==> SUCCESS ==> Building image "fallback" ==> Running command: /sbin/mkinitcpio -k 2.6.24-ARCH -c /etc/mkinitcpio.d/kernel26-fallback.conf -g /boot/kernel26-fallback.img :: Begin build :: Parsing hook [base] :: Parsing hook [udev] :: Parsing hook [ide] ERROR: module 'ide[-_]gd[-_]mod' not found :: Parsing hook [pata] :: Parsing hook [scsi] :: Parsing hook [sata] :: Parsing hook [usbinput] :: Parsing hook [raid] :: Parsing hook [filesystems] :: Generating module dependencies :: Generating image '/boot/kernel26-fallback.img'...SUCCESS ==> SUCCESS [root@myhost Archlinux-mppc-kernel]# Then tried reinstalling kernel26 which was before the MPPC patched one. I get the same output as above, apart from one error line below that is not there on the failsafe kernel26 build. Strangely although the kernel26 wont boot, here the failsafe version boots ok. All a bit weird. ERROR: module 'ide[-_]gd[-_]mod' not found I've put the list of packages I installed on 20100310 from the pacman log below if anyone might see some package or other that I upgraded which might be responsible for the MPPC kernel failing to boot, but the LTS kernel unaffected and booting ok. Btw: The klibc packages are still installed at this time, and presume that if I had been able to get pacman -Su to run, one of the updates would have removed them. Any help would be really appreciated. Nigel. [2010-03-10 12:55] upgraded hal-info (0.20090716-2 -> 0.20091130-1) [2010-03-10 12:55] upgraded hal (0.5.13-2 -> 0.5.14-2) [2010-03-10 12:55] upgraded hicolor-icon-theme (0.10-2 -> 0.11-1) [2010-03-10 12:55] upgraded hunspell (1.2.8-1 -> 1.2.8-2) [2010-03-10 13:04] upgraded hwdetect (2009.09-5 -> 2010.02-3) [2010-03-10 13:04] upgraded imlib (1.9.15-6 -> 1.9.15-9) [2010-03-10 13:04] upgraded imlib2 (1.4.2-3 -> 1.4.2-6) [2010-03-10 13:04] upgraded inetutils (1.6-4 -> 1.7-2) [2010-03-10 13:04] upgraded initscripts (2009.08-1 -> 2010.01-1) [2010-03-10 13:09] upgraded iproute2 (2.6.29-1 -> 2.6.31-1) [2010-03-10 13:09] upgraded iptables (1.4.4-1 -> 1.4.7-1) [2010-03-10 13:09] upgraded iputils (20071127-2 -> 20100214-2) [2010-03-10 13:28] upgraded ipw2100-fw (1.3-3 -> 1.3-4) [2010-03-10 13:28] upgraded ipw2200-fw (3.1-1 -> 3.1-2) [2010-03-10 13:28] upgraded iso-codes (3.10.1-1 -> 3.14-1) [2010-03-10 13:28] upgraded iwlwifi-3945-ucode (15.32.2.9-1 -> 15.32.2.9-2) [2010-03-10 13:28] upgraded iwlwifi-4965-ucode (228.61.2.24-1 -> 228.61.2.24-2) [2010-03-10 14:04] upgraded k3b (1.66.0alpha2-3 -> 1.90.0rc1-1) [2010-03-10 14:04] upgraded kbd (1.15-2 -> 1.15.1-1) [2010-03-10 14:17] upgraded lame (3.98.2-2 -> 3.98.3-1) [2010-03-10 14:17] upgraded lesstif (0.95.0-3 -> 0.95.2-2) [2010-03-10 14:17] upgraded libarchive (2.7.1-1 -> 2.8.0-1) [2010-03-10 14:17] upgraded libass (0.9.6-2 -> 0.9.8-1) [2010-03-10 14:17] upgraded libassuan (1.0.5-1 -> 1.0.5-2) [2010-03-10 15:41] installed libssh (0.4.1-1) [2010-03-10 15:41] installed qca (2.0.2-2) [2010-03-10 15:41] installed shared-desktop-ontologies (0.2-1) [2010-03-10 15:41] installed attica (0.1.2-1) [2010-03-10 15:42] upgraded kdelibs (4.3.1-1 -> 4.4.1-1) [2010-03-10 15:42] upgraded kdebase-runtime (4.3.1-1 -> 4.4.1-1) [2010-03-10 15:42] upgraded kdemultimedia-kioslave (4.3.1-1 -> 4.4.1-1) [2010-03-10 16:03] [2010-03-10 16:03] If you use the LILO bootloader, you should run 'lilo' after upgrading. [2010-03-10 16:03] [2010-03-10 16:03] upgraded lilo (22.8-3 -> 22.8-4) [2010-03-10 16:03] upgraded lirc-utils (0.8.5-1 -> 0.8.6-3) [2010-03-10 16:19] upgraded lsof (4.82-1 -> 4.83-1) [2010-03-10 16:19] upgraded man-pages (3.22-1 -> 3.23-1) [2010-03-10 16:20] upgraded m4 (1.4.13-1 -> 1.4.14-1) [2010-03-10 16:59] upgraded xcb-proto (1.5-1 -> 1.6-1) [2010-03-10 16:59] upgraded libxcb (1.4-1 -> 1.5-1) [2010-03-10 16:59] upgraded kbproto (1.0.3-2 -> 1.0.4-1) [2010-03-10 16:59] upgraded libx11 (1.2.2-1 -> 1.3.3-1) [2010-03-10 16:59] upgraded libxt (1.0.6-1 -> 1.0.7-1) [2010-03-10 16:59] upgraded libdrm (2.4.13-1 -> 2.4.18-2) [2010-03-10 16:59] upgraded mesa (7.5.1-2 -> 7.7-1) [2010-03-10 16:59] upgraded zenity (2.26.0-2 -> 2.28.0-1) [2010-03-10 16:59] upgraded metacity (2.26.0-2 -> 2.28.1-1) [2010-03-10 17:00] synchronizing package lists [2010-03-10 17:12] upgraded module-init-tools (3.10-1 -> 3.11.1-2) [2010-03-10 17:12] upgraded mpg123 (1.9.0-1 -> 1.10.1-1) [2010-03-10 17:12] upgraded mtools (4.0.10-5 -> 4.0.12-1) [2010-03-10 17:12] upgraded mxml (2.5-1 -> 2.6-1) [2010-03-10 17:12] warning: /etc/nanorc installed as /etc/nanorc.pacnew [2010-03-10 17:12] upgraded nano (2.0.9-2 -> 2.2.3-1) [2010-03-10 17:13] upgraded musicbrainz (2.1.5-2 -> 2.1.5-3) [2010-03-10 17:25] installed rrdtool (1.4.2-2) [2010-03-10 17:25] upgraded lm_sensors (3.1.1-1 -> 3.1.2-1) [2010-03-10 17:25] upgraded mpfr (2.4.1-1 -> 2.4.2-1) [2010-03-10 17:43] upgraded net-snmp (5.4.2.1-1 -> 5.5-1) [2010-03-10 17:43] installed libgssglue (0.1-2) [2010-03-10 17:43] upgraded libtirpc (0.2.0-1 -> 0.2.1-1) [2010-03-10 17:43] upgraded librpcsecgss (0.18-1 -> 0.19-2) [2010-03-10 17:43] upgraded nfs-utils (1.2.0-3 -> 1.2.2-1) [2010-03-10 17:43] upgraded normalize (0.7.7-3 -> 0.7.7-4) [2010-03-10 17:53] upgraded nspr (4.8-1 -> 4.8.3-1) [2010-03-10 17:53] upgraded nss (3.12.4-1 -> 3.12.4-2) [2010-03-10 17:53] upgraded ntp (4.2.4p7-3 -> 4.2.6-2) [2010-03-10 17:54] upgraded ntfs-3g (2009.4.4-1 -> 2010.1.16-1) [2010-03-10 18:07] upgraded udev (146-2 -> 151-3) [2010-03-10 19:33] upgraded libcanberra (0.14-1 -> 0.23-1) [2010-03-10 19:33] upgraded libwnck (2.26.2-1 -> 2.28.0-1) [2010-03-10 19:33] upgraded gnome-menus (2.26.2-1 -> 2.28.0.1-1) [2010-03-10 19:33] upgraded libsoup (2.26.3-1 -> 2.28.2-1) [2010-03-10 19:33] installed libsoup-gnome (2.28.2-1) [2010-03-10 19:33] upgraded libgweather (2.26.2.1-1 -> 2.28.0-1) [2010-03-10 19:33] upgraded libical (0.43-1 -> 0.44-1) [2010-03-10 19:33] upgraded libbonobo (2.24.1-1 -> 2.24.2-1) [2010-03-10 19:33] upgraded evolution-data-server (2.26.3-1 -> 2.28.3.1-1) [2010-03-10 19:33] upgraded gnome-desktop (2.26.3-1 -> 2.28.2-1) [2010-03-10 19:33] upgraded libgnome (2.26.0-2 -> 2.28.0-2) [2010-03-10 19:33] upgraded libbonoboui (2.24.1-1 -> 2.24.2-1) [2010-03-10 19:33] upgraded libgnomeui (2.24.1-1 -> 2.24.2-1) [2010-03-10 19:33] upgraded gnome-panel (2.26.3-1 -> 2.28.0-2) [2010-03-10 19:33] upgraded libxklavier (3.9-2 -> 4.0-1) [2010-03-10 19:33] installed devicekit-power (013-1) [2010-03-10 19:33] installed polkit-gnome (0.96-1) [2010-03-10 19:33] upgraded gnome-session (2.26.2-1 -> 2.28.0-1) [2010-03-10 19:34] upgraded gdm (2.20.10-2 -> 2.28.2-1) [2010-03-10 19:41] upgraded gdm (2.28.2-1 -> 2.28.2-1) [2010-03-10 20:34] upgraded dbus (1.2.20-1 -> 1.2.20-1) [2010-03-10 21:14] upgraded openssh (5.2p1-1 -> 5.3p1-4) [2010-03-10 21:24] upgraded gdm (2.28.2-1 -> 2.20.10-2) [2010-03-10 21:55] upgraded polkit-qt (0.9.2-2 -> 0.95.1-1) [2010-03-10 23:03] installed kdemod3-smb4k (0.9.9-1)

1 0

Re: [arch-general] security
by Gordon Campbell 12 Mar '10

12 Mar '10

Hi, Thanks for all your advice. So far I am enjoying my experience with Arch Linux since I changed my Distro over from Fedora about a month ago. Gordy

2 1

[arch-general] Security
by Gordon Campbell 12 Mar '10

12 Mar '10

Hi all, I am new to this list and fairly new to Arch Linux. My Question is do I need to install a firewall? if so which one? Thanks in advance, Gordy

7 6

[arch-general] Customising arch iso
by Damien Churchill 12 Mar '10

12 Mar '10

I was just wondering if there are there any up to date instructions available for customising the arch installer? I only need to upgrade the kernel to 2.6.32 in order to install (at least that is the first problem I have encountered). Thanks in advance, Damien

3 4

[arch-general] Update register/log
by Manne Merak 12 Mar '10

12 Mar '10

Is there a register or log that lists the history of package updates. I need to know what versions of encfs and openssl were updated and when. I am still unable to mount my 1.5 year old volume because of broken encfs and openssl update. (I did read all the bug reports associated with this, they recommend downgrading to openssl 0.9.8l, which I already tried) Manne

2 1