Re: (forw) Debian installer build: failed or old builds
Quoting Joey Hess (jo...@debian.org): > Christian PERRIER wrote: > > Is there something going on on the box where you're building armel > > daily builds? > > Probably a power failure took the build box down. It will be some days, > probably less than a week until I can hit the button to boot it. Could it be possible that these daily builds are moved to a buildd machine? Most daily builds are now done there. Of course, you'll understand that I don't want to blame the work don, or even the reliability of builds done on your boxes, Joey. You know how I value your work, I think..:-) But I would find it more consistent in the long term to have daily builds done on buildd machines. I'm afraid I don't exactly know what needs to be done:Luk did some moves to buildd machines last year. So did Gaudenz after and during DebConf...and so did Phil Kern recently for...arm(?). signature.asc Description: Digital signature
Bug#606984: Still no sound on my Powermac G4 (digital audio)
I tried out your latest Daily build #3 on my PM G4 (digital audio). Sound still doesn't work, and when I check /etc/modprobe.d/alsa-base-blacklist.conf I found that snd-pcsp is the only file blacklisted. I changed the file to read: # Uncomment these entries in order to blacklist unwanted modem drivers # blacklist snd-atiixp-modem # blacklist snd-intel8x0m # blacklist snd-via82xx-modem # Comment this entry in order to load snd-pcsp driver blacklist snd-pcsp blacklist snd-aoa blacklist snd-aoa-codec-tas blacklist snd-aoa-fabric-layout blacklist snd-aoa-i2sbus blacklist snd-aoa-soundbus # Comment this entry in order to load pcspkr driver After a reboot, the sound worked. Using Volume Control, was able to set a sound theme. The switches tab indicated that the PC Speaker was working. cat /proc/asound/cards gave me: 0 [Tumbler]: PMac Tumbler - PowerMac Tumbler PowerMac Tumbler (Dev 14) Sub-frame 0 This indicates that the snd-powermac is now working. When I tried to play an audio disk, however, Sound Juicer opened and promptly crashed. When I tried to reboot, I got a message that File Manager was not responding. This is probably a separate issue, however, as VLC media player in the weekly-build of debian-testing-powerpc-xfce+lxde works fine with the same modification the alsa-base-blacklist.conf file. Tom -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3dbc7e45-602a-460f-87b7-fc6c81275...@sharedcup.com
up to date links
Hi all, I observed the following when starting the installation manual. The first note says, there may be a more up to date version and then refers to a link, which refers to a page containing another link... which in turns refers to a page with another link, at which point you end up at the page you started from. The manual itself, refers to yet another link, which then opens the HTML version, with a note stating "this manual may not be up to date". Which of course is where we started. Copyright page - The note advises the user to check the debian-installer page for an updated version using the following link: *(http://www.debian.org/devel/debian-installer/). * - The Debian installer page then refers the user to the squeeze page, using the following link: *(http://www.debian.org/releases/squeeze/debian-installer/)* - The Debian Squeeze page then contains a link back to the installation guide. * (http://www.debian.org/releases/squeeze/installmanual/)* - This then returns the user back to the point where they started. - Section 1.6 page 4 "Get the newest version of this document", refers to the following page: *(http://www.debian.org/releases/squeeze/i386)*, for the latest version. - This opens the HTML version of the manual on the copyright page - Where the first note states: "A new version of this manual may be found on the Internet at the debian-installer home page." I'm not sure and I'm probably missing something but this does appear to be a rather circular way of handling updates. Finally, I'm new, I don't want to come across as overly critical, nor as someone whose sole mission is to offer criticism . I plan to review the manual and note things that may appear wrong, missing, or confusing, at least from my perspective. Any advice as to the best way to handle these kind of issues, open e-mail? ...direct to the attention of a specific individual? file a bug report..etc? Direction would be appreciated. Also, if anyone wants to point out how I can help to resolve issues, once verified, I would be happy to contribute solutions where I can. Thanks, Frank
Re: (forw) Debian installer build: failed or old builds
Christian PERRIER wrote: > Could it be possible that these daily builds are moved to a buildd > machine? Most daily builds are now done there. I've repeatedly said I'd prefer that happen. -- see shy jo signature.asc Description: Digital signature
Re: up to date links
Hello, "Francis B. Roderick" wrote: > Finally, I'm new, I don't want to come across as overly critical, nor as > someone whose sole mission is to offer criticism . I plan to review the > manual and note things that may appear wrong, missing, or confusing, at > least from my perspective. > > Any advice as to the best way to handle these kind of issues, open > e-mail? ...direct to the attention of a specific individual? file a bug > report..etc? Direction would be appreciated. > > Also, if anyone wants to point out how I can help to resolve issues, > once verified, I would be happy to contribute solutions where I can. it will be a good idea to checkout the source code for the manual. That would give you the possibility to provide patches, which would be a big help. Read http://d-i.alioth.debian.org/manual/en.i386/apes02.html Holger -- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = Created with Sylpheed 3.0.2 under DEBIAN GNU/LINUX 6.0 - S q u e e z e Registered LinuxUser #311290 - http://counter.li.org/ = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110330213038.593160f4.li...@wansing-online.de
Bug#470144: CONTACT THE UK BRITISH Premier Oil OFFICE FOR CLIAMS OF 750,000.00 GBP. CLAIMS
Name... Tell.. Country... -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4affc54800052...@ms1.iplannetworks.net
Re: up to date links
Francis B. Roderick, le Wed 30 Mar 2011 13:52:53 -0500, a écrit : > Any advice as to the best way to handle these kind of issues, open e-mail? > ...direct to the attention of a specific individual? file a bug report..etc? > Direction would be appreciated. Please file a bug report against the installation-guide package. That'll send us a mail and it'll be kept recorded in the BTS so it'll not be forgetten. Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110330213449.gd5...@const.famille.thibault.fr
Bug#618320: kfreebsd: invalid a.out header
A Segunda 14 Março 2011 11:13:02 Miguel Figueiredo você escreveu: [...] > Initial boot menu is displayed but booting gives the following error: > error: invalid a.out header > error: only ELF kernel supports module. > > screen image available on: http://i.imgur.com/bVjfW.png > An update on the issue: 22:11 < cjwatson> elmig: I think that's fixed in unstable 22:11 < cjwatson> it sounds a bit like this from 1.99~rc1-6: 22:11 < cjwatson> - Account for FreeBSD module headers when calculating allocation size. 22:12 < cjwatson> (25 Mar) 22:12 < cjwatson> 1.99~rc1-8 should generally be happy on kfreebsd daily images are still using 1.99~rc1-3. -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103302253.29036.el...@debianpt.org
Bug#619236: [Cbe-oss-dev] Bug#619236: installation-reports: installation works fine on PS3 now, but we still can't boot after the installation
On 03/22/2011 02:29 AM, Antonio Ospite wrote: > Hi, > > the installation on PS3 now completes pretty fine, however there are > still some details that could be improved. > > The installer warns about the boot loader not being installed, which is > fine, I already had the 'petitboot' bootloader installed, but some > configuration is still needed to make the system actually boot _after_ > the installation. > > petitboot needs a /etc/kboot.conf in the root filesystem with this > content to successfully boot the installed system: > > linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1 quiet > I could successfully do a gnome desktop install using the 20110329 daily: http://cdimage.debian.org/cdimage/daily-builds/daily/20110329-5/powerpc/iso-cd/debian-testing-powerpc-netinst.iso I encountered the same problems as Antonio. Once the installer was finished, but before it rebooted the system I used this from a tty console: echo 'linux=/boot/vmlinux initrd=/boot/initrd.img root=/dev/ps3da1' > /target/etc/kboot.conf -Geoff -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d93a8ae.2090...@infradead.org
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:armel Mar 23 10:01 joey@box build_iop32x_netboot http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_netboot.log * OLD BUILD:armel Mar 23 10:04 joey@box build_iop32x_network-console_glantank http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_glantank.log * FAILED BUILD: armel Mar 23 10:04 joey@box build_iop32x_network-console_glantank http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_glantank.log * OLD BUILD:armel Mar 23 10:09 joey@box build_iop32x_network-console_n2100 http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_n2100.log * FAILED BUILD: armel Mar 23 10:09 joey@box build_iop32x_network-console_n2100 http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_n2100.log * OLD BUILD:armel Mar 23 10:14 joey@box build_iop32x_network-console_ss4000e http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_ss4000e.log * FAILED BUILD: armel Mar 23 10:14 joey@box build_iop32x_network-console_ss4000e http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_ss4000e.log * OLD BUILD:armel Mar 23 10:18 joey@box build_ixp4xx_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_ixp4xx_network-console.log * FAILED BUILD: armel Mar 23 10:18 joey@box build_ixp4xx_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_ixp4xx_network-console.log * OLD BUILD:armel Mar 23 10:24 joey@box build_kirkwood_netboot http://people.debian.org/~joeyh/d-i/armel/images/daily/build_kirkwood_netboot.log * OLD BUILD:armel Mar 23 10:43 joey@box build_kirkwood_netboot-gtk http://people.debian.org/~joeyh/d-i/armel/images/daily/build_kirkwood_netboot-gtk.log * OLD BUILD:armel Mar 23 10:46 joey@box build_kirkwood_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_kirkwood_network-console.log * FAILED BUILD: armel Mar 23 10:46 joey@box build_kirkwood_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_kirkwood_network-console.log * OLD BUILD:armel Mar 23 10:50 joey@box build_orion5x_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_orion5x_network-console.log * FAILED BUILD: armel Mar 23 10:50 joey@box build_orion5x_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_orion5x_network-console.log * OLD BUILD:armel Mar 23 10:56 joey@box build_versatile_netboot http://people.debian.org/~joeyh/d-i/armel/images/daily/build_versatile_netboot.log * OLD BUILD:armel Mar 23 11:02 joey@box build_ads_cf http://people.debian.org/~joeyh/d-i/armel/images/daily/build_ads_cf.log * OLD BUILD:sparc Mar 23 00:12 buildd@zee build_cdrom http://d-i.debian.org/daily-images/sparc/daily/build_cdrom.log * OLD BUILD:sparc Mar 23 00:15 buildd@zee build_netboot http://d-i.debian.org/daily-images/sparc/daily/build_netboot.log * OLD BUILD:sparc Mar 23 00:17 buildd@zee build_miniiso http://d-i.debian.org/daily-images/sparc/daily/build_miniiso.log Totals: 114 builds (6 failed, 14 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q56f2-0001f2...@ravel.debian.org
Bug#598765: debian-installer: FTBFS on alpha: needs mirror update?
Well, there is no squeezy for alpha, it was not released with other architectures, and it will probably not be relesead even after normal release. debian-alpha team is targeting re-release on normal schedule of Debian wheezy. But this is not yet decided oficially, so currently only unstable/sid is available for alpha (and lenny and experimental of course). Would be nice if debian-installer from sid, would use sid distribution for building. Currently according to logs, package is from sid, but it have hardcoded squeezy strings in build process. Neverthless currently building debian-installer is slightly pointless for a while, because of udev issues, which will be fixed when eglibc 2.13 will enter unstable. (it already is fixed for example in libc6.1 2.13-0exp5 for experimental). Regards, Witek -- Witold Baryluk signature.asc Description: Digital signature
