Arch-general October 2011

arch-general@lists.archlinux.org

145 participants
94 discussions

[arch-general] cannot generate enough entropy for pacman-key --init
by Alper Kanat 15 Oct '11

15 Oct '11

Hey There, I have an Arch Linux box inside Virtualbox on a Mac that I use for development purposes. I connect to this machine via SSH without any visual interface. It's on [testing] and just upgraded to pacman 4.0 and after installation it asked me to run pacman-key --init to generate the necessary keys for my system. I did all of these inside GNU Screen (also tried without it without any luck): $ sudo pacman-key --init gpg: Generating pacman keychain master key... Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy! (Need 300 more bytes) I pressed random bits with the keyboard but it didn't work so I fired up another window inside screen and did cat /dev/urandom > /dev/null but that also didn't work. So I found this [1] article and tried it again without any luck. So I'm basically stuck here. Can someone please help me? Since pacman is bricked, I can't also install anything. Now I have to manually downgrade pacman if I can't succeed. Thanks! [1] http://www.thingy-ma-jig.co.uk/blog/22-01-2010/generate-entropy-gnupg --- Quis custodiet ipsos custodes?

3 4

[arch-general] VirtualBox not running properly
by Madhurya Kakati 15 Oct '11

15 Oct '11

Hi, I installed Virtual/box from the official repos. However when I try to run a Virtual OS it gives me the following error. http://i.imgur.com/sBzl4.png I followed all the instructions after installing it.

4 12

[arch-general] How to setup Xorg on VirtualBox?
by Jason 15 Oct '11

15 Oct '11

I am a newbie of ArchLinux. I have installed Arch on VirtualBox (Running on windows 7), but unable to startx, does anyone know some instructions about this?

3 2

[arch-general] Problems with .install file and pacman 4.0
by fredbezies 15 Oct '11

15 Oct '11

Hello. I don't have any powers to post on arch-dev-public, so I'm writing here. Since I upgraded to pacman 4.0 (and building tools related to pacman 4.0), some packages which have both an install file and a name like something-git won't build. For example, if I try to build vlc-git, https://aur.archlinux.org/packages.php?ID=16084, I cannot get it build until I comment install=() line : [fred@fredo-arch vlc-git]$ makepkg ==> ERROR : install file (('vlc-git.install')) doesn't exist But a little ls tells me : [fred@fredo-arch vlc-git]$ ls PKGBUILD vlc-git.install Known bug ? install file line in this package : install=('vlc-git.install') I can see the same for a package I try to maintain, kvm-git : https://aur.archlinux.org/packages.php?ID=22041 Any ideas ? -- Frederic Bezies fredbezies(a)gmail.com

3 2

[arch-general] Yaourt and pacman 4.0
by fredbezies 15 Oct '11

15 Oct '11

A little tip for yaourt users having problem with pacman 4.0 in testing. You will have to build both package-query-git and yaourt-git. https://aur.archlinux.org/packages.php?ID=35478 https://aur.archlinux.org/packages.php?ID=18676 -- Frederic Bezies fredbezies(a)gmail.com

1 0

[arch-general] In reply to [arch-dev-public] [signoff] pacman 4.0.0-2
by Karol Blazewicz 14 Oct '11

14 Oct '11

On Fri, Oct 14, 2011 at 2:52 PM, Pierre Schmitz <pierre(a)archlinux.de> wrote: > I see my text was probably hard to read, but it was not about some > packages not being updated for pacman 4.0 yet but a possible bug (or > two) in pacman itself. > > -- > Pierre Schmitz, https://users.archlinux.de/~pierre > Same thing happened when I installed yaourt: [2011-10-14 14:36] Running 'pacman -S yaourt' [2011-10-14 14:36] warning: /etc/pacman.conf installed as /etc/pacman.conf.pacnew [2011-10-14 14:36] warning: /etc/makepkg.conf installed as /etc/makepkg.conf.pacnew [2011-10-14 14:36] upgraded pacman (4.0.0-2 -> 3.5.4-4) [2011-10-14 14:36] installed package-query (0.9-1) [2011-10-14 14:36] installed yaourt (0.10.2-1) Now when I want to upgrade to pacman 4 it behaves as expected: resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: package-query: requires pacman<3.6

3 3

[arch-general] pacman 4.0.0 signing
by Sander Jansen 14 Oct '11

14 Oct '11

After upgrading to the new pacman 4.0, the system update following fails due a lot of untrusted signatures (unknown trust error). I'm guessing we need to verify we really trust these signatures. I've found this guide regarding validating gpg keys: http://www.pps.jussieu.fr/~jch/software/pgp-validating.html. I assume this will be a lot similar, except using the pacman-key frontend to do the verification. So let me step through and see if understand correctly: All the developers keys seem to be published here: http://www.archlinux.org/developers/ and http://www.archlinux.org/trustedusers So to trust Andrea Scarpino's key I would get the pgp key from the above webpage (PGP Key: 0xD30DB0AD) and finger it: pacman-key --finger 0xD30DB0AD then compare the finger print with the one thats linked to his profile: http://pgp.mit.edu:11371/pks/lookup?op=vindex&fingerprint=on&exact=on&searc… It seems to match, so there is a good chance it's the real deal, so now I can locally sign it: pacman-key --lsign-key 0xD30DB0AD Correct? In examples of the article also marks the key as trusted. Would that be a good idea? We have to do this for each and every Arch developer I guess? Is there a faster way? Sander

3 3

Re: [arch-general] [arch-dev-public] [signoff] pacman 4.0.0-2
by Oon-Ee Ng 14 Oct '11

14 Oct '11

On Fri, Oct 14, 2011 at 3:42 AM, Rémy Oudompheng <remy(a)archlinux.org> wrote: > On 2011/10/13 Pierre Schmitz <pierre(a)archlinux.de> wrote: >> Am 13.10.2011 20:22, schrieb Dan McGee: >>> The most anticipated release EVER has landed in [testing]. Do I expect >>> it to make it out before we need a 4.0.1? Not really. :) >>> >>> Upstream NEWS/changes: >>> http://projects.archlinux.org/pacman.git/tree/NEWS?h=maint >>> Disregard the 4.0.1 stuff that isn't in this package yet and hasn't >>> been actually released. >>> >>> Questions? Concerns? Comments? >> >> Big thanks to everybody involved with this great release. About that >> issue I am not supposed to talk here I'll send a mail tomorrow. :-) >> >> Good thing you moved this into testing so there are no excuses not to >> test the new pacman. Do you know if porting pyalpm will be easy or is >> already done? Would be beter to have this sorted out before moving 4.0 >> to core. (pyalpm is needed by namcap) I also need to have a look at this >> code: >> https://projects.archlinux.org/dbscripts.git/tree/cron-jobs/check_archlinux >> But should be easy enough to port if even necessary. > > I've followed pacman API changes in pyalpm's trunk all along and will > do the appropriate release asap. > > Rémy. > Something to note, even though pyalpm is updated to support pacman 4.0 some user intervention would be required, since they'd get this error on upgrade if they answer Y to the question below:- :: The following packages should be upgraded first : pacman :: Do you want to cancel the current operation :: and upgrade these packages now? [Y/n] resolving dependencies... looking for inter-conflicts... error: failed to prepare transaction (could not satisfy dependencies) :: pyalpm: requires pacman<3.6 Don't think there's a way to deal with that though, either the user answers 'n' or upgrades pacman with -d? Both are manual-intervention-required =)

1 0

[arch-general] wintv-hvr 850 (hybrid) not detecting any signal.
by Javier Vasquez 14 Oct '11

14 Oct '11

Hi, I'm not able to get my wintv-hvr 850 to work. It fails to find signal in both x86-32 and x86-64 machines... Some of the things I get (dmesg): [ 143.746636] cx231xx v4l2 driver loaded. [ 143.746862] cx231xx #0: New device Hauppauge Hauppauge Device @ 480 Mbps (2040:b140) with 6 interfaces [ 143.746865] cx231xx #0: registering interface 1 [ 143.747068] cx231xx #0: Identified as Hauppauge EXETER (card=8) [ 143.747189] IR RC5(x) protocol handler initialized [ 143.761855] IR RC6 protocol handler initialized [ 143.763836] IR JVC protocol handler initialized [ 143.767621] IR Sony protocol handler initialized [ 143.772576] lirc_dev: IR Remote Control driver registered, major 249 [ 143.778304] IR LIRC bridge handler initialized [ 143.911324] cx231xx #0: cx231xx_dif_set_standard: setStandard to ffffffff [ 143.933691] cx25840 3-0044: cx23102 A/V decoder found @ 0x88 (cx231xx #0) [ 143.951787] cx25840 3-0044: Firmware download size changed to 16 bytes max length [ 145.954902] cx25840 3-0044: loaded v4l-cx231xx-avcore-01.fw firmware (16382 bytes) [ 146.002106] i2c-core: driver [tuner] using legacy suspend method [ 146.002109] i2c-core: driver [tuner] using legacy resume method [ 146.039520] All bytes are equal. It is not a TEA5767 [ 146.039526] tuner 4-0060: Tuner -1 found with type(s) Radio TV. [ 146.058870] tda18271 4-0060: creating new instance [ 146.061146] Unknown device (0) detected @ 4-0060, device not supported. [ 146.061149] tda18271_attach: [4-0060|M] error -22 on line 1275 [ 146.061152] tda18271 4-0060: destroying instance [ 146.066665] tuner 4-0060: Tuner has no way to set tv freq [ 146.067769] cx231xx #0: cx231xx #0: v4l2 driver version 0.0.1 [ 146.081785] cx231xx #0: cx231xx_dif_set_standard: setStandard to b000 [ 146.155662] cx231xx #0: video_mux : 0 [ 146.155670] cx231xx #0: do_mode_ctrl_overrides : 0xb000 [ 146.156407] cx231xx #0: do_mode_ctrl_overrides NTSC [ 146.163080] cx231xx #0: cx231xx #0/0: registered device video0 [v4l2] [ 146.163173] cx231xx #0: cx231xx #0/0: registered device vbi0 [ 146.163179] cx231xx #0: V4L2 device registered as video0 and vbi0 [ 146.163188] cx231xx #0: EndPoint Addr 0x84, Alternate settings: 5 [ 146.163194] cx231xx #0: Alternate setting 0, max size= 512 [ 146.163200] cx231xx #0: Alternate setting 1, max size= 184 [ 146.163205] cx231xx #0: Alternate setting 2, max size= 728 [ 146.163211] cx231xx #0: Alternate setting 3, max size= 2892 [ 146.163217] cx231xx #0: Alternate setting 4, max size= 1800 [ 146.163224] cx231xx #0: EndPoint Addr 0x85, Alternate settings: 2 [ 146.163230] cx231xx #0: Alternate setting 0, max size= 512 [ 146.163235] cx231xx #0: Alternate setting 1, max size= 512 [ 146.163241] cx231xx #0: EndPoint Addr 0x86, Alternate settings: 2 [ 146.163247] cx231xx #0: Alternate setting 0, max size= 512 [ 146.163252] cx231xx #0: Alternate setting 1, max size= 576 [ 146.163258] cx231xx #0: EndPoint Addr 0x81, Alternate settings: 6 [ 146.163264] cx231xx #0: Alternate setting 0, max size= 512 [ 146.163269] cx231xx #0: Alternate setting 1, max size= 64 [ 146.163274] cx231xx #0: Alternate setting 2, max size= 128 [ 146.163280] cx231xx #0: Alternate setting 3, max size= 316 [ 146.163285] cx231xx #0: Alternate setting 4, max size= 712 [ 146.163291] cx231xx #0: Alternate setting 5, max size= 1424 [ 146.163452] usbcore: registered new interface driver cx231xx [ 146.171942] cx231xx #0: cx231xxcx231xx: called cx231xx_uninit_vbi_isoc [ 146.171947] cx231xx #0: cx231xx_stop_stream():: ep_mask = 10 [ 146.172279] cx231xx #0: cx231xx_stop_stream():: ep_mask = 8 [ 146.183690] cx231xx #0: cx231xx-audio.c: probing for cx231xx non standard usbaudio [ 146.183955] cx231xx #0: EndPoint Addr 0x83, Alternate settings: 3 [ 146.183957] cx231xx #0: Alternate setting 0, max size= 512 [ 146.183960] cx231xx #0: Alternate setting 1, max size= 28 [ 146.183962] cx231xx #0: Alternate setting 2, max size= 52 [ 146.183964] cx231xx: Cx231xx Audio Extension initialized [ 146.193525] cx231xx #0: Changing the i2c master port to 1 [ 146.316797] dvb_init: looking for tuner / demod on i2c bus: 4 [ 146.336561] tda18271 4-0060: creating new instance [ 146.338672] TDA18271HD/C2 detected @ 4-0060 [ 146.338800] cx231xx #0: UsbInterface::sendCommand, failed with status --32 [ 146.338811] tda18271_write_regs: [4-0060|M] ERROR: idx = 0x0, len = 39, i2c_transfer returned: -32 [ 146.537690] DVB: registering new adapter (cx231xx #0) [ 146.537703] DVB: registering adapter 0 frontend 0 (LG Electronics LGDT3305 VSB/QAM Frontend)... [ 146.538628] Successfully loaded cx231xx-dvb [ 146.539056] cx231xx: Cx231xx dvb Extension initialized [ 205.380044] cx231xx #0: Reloading firmware for XC5000 [ 205.382731] cx231xx #0: UsbInterface::sendCommand, failed with status --32 [ 205.382736] tda18271_write_regs: [4-0060|M] ERROR: idx = 0x0, len = 39, i2c_transfer returned: -32 [ 205.584115] tda18271: performing RF tracking filter calibration [ 207.151305] tda18271: RF tracking filter calibration complete [ 207.151310] cx231xx #0: XC5000 firmware download completed [ 207.181681] cx231xx #0: cx231xx_dif_set_standard: setStandard to b000 [ 207.255567] cx231xx #0: video_mux : 0 [ 207.255569] cx231xx #0: do_mode_ctrl_overrides : 0xb000 [ 207.256316] cx231xx #0: do_mode_ctrl_overrides NTSC [ 207.280078] tuner 4-0060: Tuner has no way to set tv freq [ 207.280105] cx231xx #0: vidioc_s_std : 0x1000 [ 207.297331] tuner 4-0060: Tuner has no way to set tv freq [ 207.302954] cx231xx #0: do_mode_ctrl_overrides : 0x1000 [ 207.303702] cx231xx #0: do_mode_ctrl_overrides NTSC [ 207.317904] cx231xx #0: cx231xx_stop_stream():: ep_mask = 8 [ 207.319284] cx231xx #0: cx231xx_initialize_stream_xfer: set video registers [ 207.319577] cx231xx #0: cx231xx_start_stream():: ep_mask = 8 [ 207.338332] cx231xx #0: cx231xx_dif_set_standard: setStandard to 1000 [ 207.414696] cx231xx #0: video_mux : 0 [ 207.414702] cx231xx #0: do_mode_ctrl_overrides : 0x1000 [ 207.415440] cx231xx #0: do_mode_ctrl_overrides NTSC [ 207.421954] tuner 4-0060: Tuner has no way to set tv freq [ 207.421969] cx231xx #0: vidioc_s_std : 0x1000 [ 207.421971] tuner 4-0060: Tuner has no way to set tv freq [ 207.427577] cx231xx #0: do_mode_ctrl_overrides : 0x1000 [ 207.428312] cx231xx #0: do_mode_ctrl_overrides NTSC [ 207.507462] cx231xx #0: Enter vidioc_s_frequency()f->frequency=2900;f->type=2 [ 207.515705] tuner 4-0060: Tuner has no way to set tv freq [ 207.515708] cx231xx #0: cx231xx_tuner_post_channel_change dev->tuner_type =083 [ 207.517325] cx231xx #0: if_frequency is set to 5400000 [ 207.517328] cx231xx #0: Enter cx231xx_set_Colibri_For_LowIF() [ 207.537963] cx231xx #0: colibri_carrier_offset=4832000, standard=0x1000 [ 207.537971] cx231xx #0: if_freq=10232000;spectral_invert=0x1;mode=0x1 [ 207.540340] cx231xx #0: Enter IF=2489 [ 207.555844] cx231xx #0: Set New FREQUENCY to 2900 [ 210.794599] cx231xx #0: Enter vidioc_s_frequency()f->frequency=2804;f->type=2 [ 210.802958] tuner 4-0060: Tuner has no way to set tv freq [ 210.802962] cx231xx #0: cx231xx_tuner_post_channel_change dev->tuner_type =083 [ 210.804582] cx231xx #0: if_frequency is set to 5400000 [ 210.804585] cx231xx #0: Enter cx231xx_set_Colibri_For_LowIF() [ 210.824119] cx231xx #0: colibri_carrier_offset=4832000, standard=0x1000 [ 210.824122] cx231xx #0: if_freq=10232000;spectral_invert=0x1;mode=0x1 [ 210.826593] cx231xx #0: Enter IF=2489 [ 210.840973] cx231xx #0: Set New FREQUENCY to 2804 [ 213.461728] cx231xx #0: Enter vidioc_s_frequency()f->frequency=1332;f->type=2 [ 213.470088] tuner 4-0060: Tuner has no way to set tv freq ... Any hints? I don't have ms-windows machine, but I asked a guy to try the usb device with the proprietary CD that came with it, and it worked out out of the box (what a surprise for these things thought for ms-windows only), so the device is working nice. I would really appreciate any help you can provide. BTW: core/linux 3.0.4-1 (base) [installed] The Linux Kernel and modules extra/v4l-utils 0.8.5-1 [installed] Userspace tools and conversion library for Video 4 Linux community/linuxtv-dvb-apps 1.1.1-4 [installed] Viewer programs for DVB cards community/tvtime 1.0.2-2 [installed] A high quality television application for use with video capture cards I've tried channels scan with scantv, tvtime and tvtime-scanner. Neither detect a thing, :-( Thanks, -- Javier.

2 7

[arch-general] In reply to [arch-dev-public] [signoff] pacman 4.0.0-2
by Karol Blazewicz 14 Oct '11

14 Oct '11

I don't have the permissions to post to [arch-dev-public] so I'm posting it here. On Thu, Oct 13, 2011 at 8:22 PM, Dan McGee <dpmcgee(a)gmail.com> wrote: > The most anticipated release EVER has landed in [testing]. Do I expect > it to make it out before we need a 4.0.1? Not really. :) > > Questions? Concerns? Comments? I'm telling you as little as possible > about this release and how to make things work to put more people in > the "standard user who doesn't follow development like a hawk" shoes. > > -Dan A question about the manpage and '-xx' switches e.g.: -u, --sysupgrade <snip> Pass this option twice to enable package downgrade; in this case pacman will select sync packages whose version does not match with the local version. This can be useful when the user switches from a testing repo to a stable one. <snip> People often overlook it - especially for '-dd'. Compare this with 'pacman -Sh' output: <snip> -u, --sysupgrade upgrade installed packages (-uu allows downgrade) <snip> '-uu' is explicitly mentioned. Do you think pacman manpage should be made more scannable (i.e. you can just glance over and know what to do) / searchable - the '-uu' switch is not exp[licitly mentioned anywhere, you can't grep it. On the other hand 'pacman -Sh' doesn't tell you about '-yy': -y, --refresh download fresh package databases from the server What do you think about such changes? Do you want them at all and if yes, will you write them or do you prefer I come up with a proposal / patch? -Karol

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Arch-general October 2011