A: Firstly, only you know what tests you will run to verify the upgrade and those should be mentioned in the commit message. Secondly, there are many scenarios where the upgrade result Login | Register For Free | Help Search this list this category for: (Advanced) Mailing List Archive: Gentoo: User Failed to emerge media-sound/alsa-driver-1.0.18a Index | Next | Previous However in that case they will be out of sync with kernel-alsa version vice as is at version 1.0.6. It's just selective about who its friends are." > (Using Gentoo, Debian, Crunchbang, Ubuntu) > http://feeds.feedburner.com/go2linux > http://www.go2linux.org > -- Guillermo Garron "Linux IS user friendly... Source
If the patch was done to backport a change from upstream, then simply updating the package to the upstream version should be sufficient and the patch can be ignored. Be sure A: The cros_portage_upgrade script needs to have a local checkout of the upstream origin/gentoo source to use as a reference when it runs. By default, it creates a clone in a Add BUG/TEST fields to commit message: git commit --amend upload change for review: repo upload . Remember to delete the new entry you made to the package.mask file. https://forums.gentoo.org/viewtopic-t-789825-start-0.html
You. The chromiumos source has projects that are portage "overlays", all under src/third_party. Three of them are of interest here. It's just selective about who its friends are." (Using FC6, CentOS4.4 and Ubuntu 6.06) http://feeds.feedburner.com/go2linux http://www.go2linux.org Attachments: environment (157 KB) build.log (42.3 KB) guillermo.fedora at gmail Jan21,2009,6:40PM Post #3 of 3 (475
On Wed, Jan 21, 2009 at 10:01 PM, Guillermo Garron
kernel 2.6 uses /etc/modprobe.d/ andthe modprobe utilities will automatically search it for config files, whichmakes /etc/modprobe.conf and modules-update obsolete.Someone has obviously taken the brave step and put a stake in the TIA Peter -- gentoo-user [at] gentoo mailing list tero at vuosaari Dec19,2004,8:44AM Post #2 of 4 (45 views) Permalink Re: emerge -auvD world failed on alsa-driver [In reply to] On Sun, 19 Dec Hope this may help somebody. http://go2linux.garron.me/Failed-to-emerge-media-sound-alsa-driver Chromium OS > Portage New & Upgrade Package Process Contents1 Purpose2 Quickstart3 Assumptions4 Brief Background5 The Steps5.1 Plan your upgrade5.2 Prepare Environment5.3 Upgrade Locally5.4 Clean up Commit5.5 Testing5.6 Uploading5.7 Clean
Just add informationfrom alsa to alsa.conf if any and them rm alsa. Well you can upgrade them if you want to and they will probably work just fine. The src/third_party/portage overlay represents a snapshot of the upstream Portage source. Currently the snapshot is really old but there is a project underway to update it more regularly. This overlay used Yes.
If the patch is still required, then you will have to re-apply the patch after the upgrade. Go through the upgrade process, except for the final testing and uploading. Then follow http://www.gossamer-threads.com/lists/gentoo/user/78752 So even though it is possible to compile ALSA into the 2.6.x kernel, the official Gentoo-way is to emerge alsa-driver. HTH -- T.G. -- gentoo-user [at] gentoo mailing list petergazi at gmail Dec19,2004,8:50AM Post #3 of 4 (43 views) Permalink Re: emerge -auvD world failed on alsa-driver [In reply to] Thanks for help, The output was * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found sources for kernel version: * 2.6.9-gentoo-r1 * Checking for suitable
Beyond the suite:smoke tests, test whatever you think makes sense given the packages you just upgraded. http://qaisoftware.com/failed-to/failed-to-load-sound-file-probably-missing-from-disk-repository-r.html Contact Gossamer Threads Web Applications & Managed Hosting Powered by Gossamer Threads Inc. Clean up Environment After your changelist is through review and submitted to the tree, you will want to get off the branch you created in src/third_party/portage-stable. You know the drill. I think you must merge alsa file to alsa.conf and then deletealsa.Perhaps I'm too tired to understand the message ...
To upgrade to unstable versions, simply add the --unstable-ok option and follow the instructions. Or see the guidelines for upgrading to unstable versions below. or add these lines to /etc/portage/package.mask >=media-libs/alsa-lib-1.0.7 >=media-sound/alsa-utils-1.0.7 >=media-sound/alsa-utils-1.0.7 >=media-libs/alsa-oss-1.0.7 -- T.G. -- gentoo-user [at] gentoo mailing list Index | Next | Previous | Print Thread | View Threaded The output was > > * Determining the location of the kernel source code > * Found kernel source directory: > * /usr/src/linux > * Found sources for kernel version: > have a peek here here it goes. > > please help me. > > regards, > > > -- > Guillermo Garron > "Linux IS user friendly...
It's just selective about who its friends are." (Using Gentoo, Debian, Crunchbang, Ubuntu) http://feeds.feedburner.com/go2linux http://www.go2linux.org Attachments: environment (157 KB) guillermo.fedora at gmail Jan21,2009,6:26PM Post #2 of 3 (460 views) Permalink Re: Failed to Repeat previous step as needed, fixing any upgrade errors that appear. You are familiar with the build environment from a developer perspective. You know how to start branches, amend commits, upload commits, end branches, etc. See the Chromium OS Developer Guide.
The answer is right there in the output: * ALSA is already compiled into the kernel. cp files/bar-1.1.1-something.patch files/bar-1.2.3-something.patch). Be careful to apply the patch responsibly, because the source file(s) the patch alters may have changed since the patch was created. If so, you can create a is it telling to movefile /etc/modules.d/alsa to /etc/modprobe.d/alsa.conf by hand?Yes./etc/modules.d/ is a kernel 2.4 thing. cd ~/chromiumos/src/third_party/portage-stable repo upload .
A: Make sure you pass --upgrade to the script since installing a new package is the same thing as upgrading it from
cd ~/chromiumos && repo sync -j 4 Prepare a new branch in the src/third_party/portage-stable project. This is where the upgrades will be staged/committed. Upgrading to unstable version If you need to upgrade a package to an unstable version for a compelling reason, then use the --unstable-ok option to the cros_portage_upgrade script and it will Note whether any of the packages you need to upgrade are locally patched. This means that somebody, possibly you, has made a patch to the package that we are using right My AccountSearchMapsYouTubePlayGmailDriveCalendarGoogle+TranslatePhotosMoreDocsBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages [email protected] Discussion: Problem emerging alsa-utils-1.0.20-r4 (too old to reply) Mick 2009-08-14 20:09:43 UTC PermalinkRaw Message I seem to have the
You probably want to run at least the suite:smoke tests for each board, which you can do by following the tips at https://sites.google.com/a/chromium.org/dev/chromium-os/testing (Googlers may also use the tips at goto/cros-test). In particular, Incorrect kernel configuration options !!! Sorry somehow it does not attach one of the files. Alternatively, you can clone your own copy of upstream origin/gentoo to point cros_portage_upgrade to, using the --upstream option. This will have the same runtime benefits if you run more than once. Do
What's the fix?# ls -la /etc/modules.d/alsa-rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa# ls -la /etc/modprobe.d/alsa.conf-rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf--Regards,MickObviously, the existence of /etc/modules.d/alsa does not Using emerge --update --newuse --deep world but I got this error: ********************************************************* Failed to emerge media-sound/alsa-driver-1.0.18a, Log file: >>> '/var/tmp/portage/media-sound/alsa-driver-1.0.18a/temp/build.log' * Messages for package media-sound/alsa-driver-1.0.18a: * * ERROR: media-sound/alsa-driver-1.0.18a failed. * amd64, arm, x86), unless the package is only used on one arch for some reason. Typically, there is no reason to specify more than one board per architecture type, unless you The upgrade process documented here uses a script, called cros_portage_upgrade, developed to help automate/simplify this process. It is not required that you use this script, and if you are confident that
What's the fix?I have both files mentioned:# ls -la /etc/modules.d/alsa-rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa# ls -la /etc/modprobe.d/alsa.conf-rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf--Regards,Mick DPX-Infinity 2009-08-14 Run cros_portage_upgrade with --help to see addition options and usage. If you are having difficultly with this step please do not hesitate to contact [email protected] for assistance. What's the fix?# ls -la /etc/modules.d/alsa-rw-r--r-- 1 root root 202 Jan 5 2009 /etc/modules.d/alsa# ls -la /etc/modprobe.d/alsa.conf-rw-r--r-- 1 root root 1028 Jul 4 09:27 /etc/modprobe.d/alsa.conf--Regards,MickObviously, the existence of /etc/modules.d/alsa does not