[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** No longer affects: fglrx-installer-experimental-9 (Ubuntu Quantal) ** No longer affects: jockey (Ubuntu Quantal) ** No longer affects: jockey (Ubuntu Raring) ** No longer affects: fglrx-installer-experimental-9 (Ubuntu Raring) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Triaged Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/fglrx-installer- experimental-12/precise-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Triaged Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “fglrx-installer-experimental-9” source package in Quantal: Triaged Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Triaged Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Please accept fglrx-installer-experimental-12 (2:12.100-0ubuntu0.1) in precise-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Triaged Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “fglrx-installer-experimental-9” source package in Quantal: Triaged Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Triaged Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** Changed in: fglrx-installer-experimental-9 (Ubuntu Quantal) Importance: Undecided = High ** Changed in: fglrx-installer-experimental-9 (Ubuntu Raring) Importance: Undecided = High ** Changed in: fglrx-installer-experimental-9 (Ubuntu Quantal) Status: Confirmed = Triaged ** Changed in: fglrx-installer-experimental-9 (Ubuntu Raring) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Triaged Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “fglrx-installer-experimental-9” source package in Quantal: Triaged Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Triaged Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
A fglrx package newer than 12.10 is required in Quantal as well. Team Fortress 2 (and potentially other Valve/Source Engine games?) appear not to work with fglrx 12.10. IMHO, fixing/releasing this for all supported Ubuntu releases should be a high priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
I've also double-checked that after installing jockey 0.9.7-0ubuntu7.7, fglrx-experimental-9 installs cleanly and boots up to a usable Unity session. Looks good, I'll close out the jockey task as well. ** No longer affects: fglrx-installer (Ubuntu) ** No longer affects: fglrx-installer (Ubuntu Precise) ** No longer affects: fglrx-installer (Ubuntu Quantal) ** No longer affects: fglrx-installer (Ubuntu Raring) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Actually, I take that back. I see that jockey 0.9.7-0ubuntu7.4 is in -updates currently, but fglrx-experimental-9 won't install properly with that version of jockey. It looks like 0.9.7-0ubuntu7.5 or 0.9.7-0ubuntu7.6 are required at a minimum. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
This bug was fixed in the package jockey - 0.9.7-0ubuntu7.7 --- jockey (0.9.7-0ubuntu7.7) precise-proposed; urgency=low * data/handlers/fglrx.py: - Fix typo which caused the handler to fail (LP: #1080588). jockey (0.9.7-0ubuntu7.6) precise-proposed; urgency=low * jockey/oslib.py, jockey/xorg_driver.py: - Add some checks for quantal's backported xserver so as not to provide drivers which don't support it (LP: #1080588). * data/handlers/fglrx.py: - Make sure to mark the experimental driver as such (LP: #1078290). - Always pass fglrx to get the alternative name or jockey will fail to set the correct alternative. jockey (0.9.7-0ubuntu7.5) precise-proposed; urgency=low * data/handlers/fglrx.py: - Add support for the experimental-9 flavour (LP: #1078290). -- Alberto Milone alberto.mil...@canonical.com Mon, 07 Jan 2013 10:55:32 +0100 ** Changed in: jockey (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
On a ThinkPad E435 running 12.04, I updated to jockey 0.9.7-0ubuntu7.7. I confirmed that the new version of jockey presents fglrx-experimental-9 and installs the package correctly. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
This bug was fixed in the package fglrx-installer-experimental-9 - 2:9.010-0ubuntu0.1 --- fglrx-installer-experimental-9 (2:9.010-0ubuntu0.1) precise-proposed; urgency=low * Initial release (LP: #1078290). -- Alberto Milone alberto.mil...@canonical.com Tue, 13 Nov 2012 14:52:54 +0100 ** Changed in: fglrx-installer-experimental-9 (Ubuntu Precise) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Hello Alberto, or anyone else affected, Accepted jockey into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/jockey/0.9.7-0ubuntu7.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: jockey (Ubuntu Precise) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
This is probably no longer required, because AMD released a stable Catalyst 13.1 yesterday. So now waiting for it to hit fglrx-updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Confirmed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
AFAICT, this *-experimental package was uploaded to precise-proposed, but not to quantal-proposed. I'd like to be able to use this driver on quantal without manually installing it from AMD's web page. The bug description for this bug also states that the package was meant to be available for quantal and precise. So as a quantal user, I'd vote for verification-failed unless the package shows up in quantal-proposed as well. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Confirmed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Putting back to Confirmed, as the SRU failed to verify. Please upload a fixed version. bug #1080588 indicates that the 7.7 upload needs to have the 7.6 changelog entry added. ** Changed in: jockey (Ubuntu Precise) Status: Fix Committed = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Confirmed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Alberto, do you need help on this? I keep building packages from the beta drivers as they come out, so I would be happy to contribute to this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** Changed in: fglrx-installer-experimental-9 (Ubuntu Quantal) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer-experimental-9 (Ubuntu Raring) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer-experimental-9 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer-experimental-9 (Ubuntu Quantal) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
Hello Alberto, or anyone else affected, Accepted jockey into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/jockey/0.9.7-0ubuntu7.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: jockey (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: New Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: New Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: New Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** Branch linked: lp:ubuntu/precise-proposed/jockey -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: New Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: New Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: New Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** Also affects: fglrx-installer-experimental-9 (Ubuntu) Importance: Undecided Status: New ** Changed in: fglrx-installer-experimental-9 (Ubuntu Precise) Importance: Undecided = High ** Changed in: fglrx-installer-experimental-9 (Ubuntu Precise) Status: New = In Progress ** Changed in: fglrx-installer-experimental-9 (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: New Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: In Progress Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: New Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: New Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
** Branch linked: lp:~ubuntu-branches/ubuntu/precise/fglrx-installer- experimental-9/precise-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “jockey” source package in Precise: In Progress Status in “fglrx-installer” source package in Quantal: In Progress Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
