Search results

...r you add an entry which covers a bug listed in Bugzilla, please set the ''CommonBugs'' keyword for the bug, and add a link to the Common Bugs page entry to the ...case. Regular package updates can't fix installer bugs, but there is an [[Anaconda/Updates|update image mechanism]]. If an updates image is made available for

{{header|anaconda}} [[Anaconda]] 是被 Fedora、Red Hat Enterprise Linux 以及 [[Anaconda/Distros| 一些其他发行版]] 采用的系统安装程序。

...do añada un problema con informe en Bugzilla, por favor incluya la clave ''CommonBugs'' al informe, así como un enlace al ítem correspondiente de la página de ...pueden corregir errores en el instalador antes de instalar, pero hay un [[Anaconda/Updates/es|mecanismo de actualización de las imágenes]]. Si hay una image

* [[Common_F17_bugs|Common bugs page]]: [http://bit.ly/fedora-commonbugs-proposed this query] lists the bugs proposed for inclusion but not yet adde ...ussion to next week due to the U.S. holiday depriving us of tflink and the anaconda crew

{{header|anaconda}} ...амма установки, которая применяется в Fedora, Red Hat Enterprise Linux и [[Anaconda/Distros| некоторых других дистрибутивах]].

{{header|anaconda}} [[Image:DSC_3217.JPG | 400px | Entering Anaconda, Montana. A city probably named after this installation program.]]

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

...Oppure, se usi Bugzilla, al bug-report, dovresti aggiungere la dicitura ''CommonBugs''. In tal caso qualcuno del [[QA]] team, dopo aver analizzato il problema d ...ti (e per evitare doppioni), puoi cercare in Bugzilla i bug contrassegnati CommonBugs:

* adamw to co-ordinate with anaconda team on TC1 date planning | style="color: #488888" | in the CommonBugs page I referenced http://fedoraproject.org/wiki/Upgrading a few times

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

* anaconda recently revised how containers (LVM, btrfs) are handled in custom partitio | style="color: #407a40" | i've already done the commonbugs page, might be one or two proposed left

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

* adamw to check F19 and F18 commonbugs for issues that should be copied to F20 | style="color: #407a40" | i worked on the commonbugs page over the weekend, i think it's in fairly good shape: https://fedorapro

* Need to spin RC4 ASAP: blockers remained in anaconda/preupgrade and selinux | style="color: #407a40" | brunowolff: stick 'commonbugs' in the keywords list

# '''Drop''' - Remove keyword CommonBugs | {{bz|533350}} || NEW || anaconda || Can't shrink encrypted partition

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

* ''adamw to co-ordinate with anaconda team on TC1 date planning'' - not done yet but planned for same day, TC1 ex ...release announcement which mentioned fedup and kparal and adamw worked on commonbugs

* ACTION: jlaska to discuss next anaconda build with clumens for RC1 ...removing F15Beta if this only impacts a single router. Also, add this to CommonBugs to be documented for any others who may encounter the problem.

...monbugs for issues that should be copied to F20'' - this was done, and F19 commonbugs cleaned up a bit * cmurf was working on a mail to anaconda list proposing a restriction on the breadth of custom partitioning coverage

# jlaska and adamw discussed documenting the outstanding bugs requesting CommonBugs documentation. The process is detailed at https://fedoraproject.org/wiki/C | style="color: #407a40" | adamw: I started documenting the installer related CommonBugs ... I should have the remaining installer issues knocked out shortly. If y

== Fedora 17 pre-planning: anaconda GUI rewrite == * Anaconda team has a complete rewrite of the GUI pending and tentatively planned to l

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

* adamw to talk to anaconda devs and get a build done for beta tc1 with live keyboard bug fixed ...one: https://fedoraproject.org/wiki/Common_F20_bugs . Do add or mark with 'CommonBugs' keyword any other bugs you think ought to be listed

| style="color: #407a40" | did we get the new anaconda and NM in RC1? | style="color: #488888" | dennis says the new anaconda was in there

| style="color: #407a40" | that doesn't quite tie in with anaconda views it, but then i don't think we're quite at the point where GNOME gets | style="color: #407a40" | if you install GNOME and don't create a user in anaconda, yes.

#* pungi is going to inherit splittree and pkgorder from anaconda-runtime; need to integrate the functionality of those into pungi code ...<td class="text" style="color: #8c4a4a">I'm still collecting stuff for the CommonBugs page</td><td class="time">13:26</td></tr>

* anaconda » master * ACTION: several remaining CommonBugs? needing documentation(jlaska, 01:25:15)

...iki/Common_F16_bugs will need entries for the bugs on http://bit.ly/fedora-commonbugs-proposed # j_dulaney - check in with anaconda and releng teams on the feasibility of making the rats point (08-31) an ear

...144" | so the obvious action item that we need to get done today is to get commonbugs up | style="color: #818144" | roshi: have you worked on commonbugs at all yet?

...r: #488888" | jreznik: define top issues - the list that adamw started in #anaconda? | style="color: #488888" | #topic (892621) Anaconda FC18-TC4 does not present BIOS RAID as available storage

| style="color: #818144" | i've pretty much done commonbugs ...bugs that should be called out there...do add them or tag the bug with the commonbugs keyword

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

: Identify and document '''CommonBugs?''' issues (see [[Common_F14_bugs#My_bug_is_not_listed|process]]) ...only outstanding items on the QA plate that I'm aware of for F-14-Beta are CommonBugs?

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

| style="color: #488888" | #info Proposed Blocker, anaconda, VERIFIED | style="color: #407a40" | it's already fixed anyway, and anaconda 18.28 is pending stable

...be great if everyone could ensure that their 'favourite' alpha bug has the CommonBugs keyword, i tried to mark the biggest ones as we went along but i may have m | style="color: #4b904b" | tflink, adamw: actually for anaconda, fesco required in ticket status report week before beta change deadline

...hat before F-15-Alpha is released, we need to document the current list of CommonBugs -- [[Common_F15_bugs]] | style="color: #488888" | given that we didn't change anaconda, i would expect rc2 to wind up good.

* Add the CommonBugs keyword to the bug report, and contact the Fedora QA team with the Bugzilla When adding issues to this page, ensure to add the CommonBugs keyword to the bug report, and place the anchor link to the entry on this p

...adding issues to it and marking bugs which should be added to it with the CommonBugs keyword. [[User:Jlaska|James Laska]] provided a search URL<ref>http://tinyu === Cracklib Translations for Anaconda ===

...aska discussed whether this was an Alpha blocker and decided to note it in CommonBugs and wait for Jens feedback to better assess the impact to Alpha testers. | style="color: #818144" | there was an install issue with anaconda

* Add the CommonBugs keyword to the bug report, and contact the Fedora QA team with the Bugzilla When adding issues to this page, ensure to add the CommonBugs keyword to the bug report, and place the anchor link to the entry on this p

| style="color: #854685" | how's the commonbugs page coming? ...="color: #407a40" | a lot of bugs not yet documented: http://bit.ly/fedora-commonbugs-proposed

# jlaska will discuss CommonBugs entry for {{bz|552423}} with halfline | style="color: #407a40" | #info jlaska will discuss CommonBugs entry for RHBZ #552423 with halfline

* jlaska will investigate the 5 anaconda F12Beta issues to determine when the failures were introduced ...add it (there's guidelines on layout in the wiki page source) or add the 'CommonBugs' keyword to the bug report.''

...e composes run in a mock chroot using the dist... so it would need the new anaconda/lorax to be in stable/base repo. ;) | style="color: #407a40" | it looks like it hits the bug where anaconda can't shut down correctly after completion

* Or, add the ''CommonBugs'' keyword to the bug report. Someone from the [[QA]] team will then inspec For reference, you can query Bugzilla for bugs tagged CommonBugs:

* [jlaska] - review anaconda bugs | style="color: #818144" | | round up by topic or sub-blocker - anaconda blicker, Xorg bugs, etc

** Should anaconda display release notes again (or pull down release notes from an html page)? ...JesseKeating need to release the bits to the mirrors - confirmation of the anaconda-devel beta readiness criteria

| style="color: #407a40" | right. For the final releases we typically have a CommonBugs page ...ms: 1) rpmdiff for each build, and 2) a set of automated tests for nightly anaconda image builds

jlaska asked if {{bz|503824}} (anaconda-maint-list, NEW, x86_64 upgrade in KVM hangs (OOM) with 512MB RAM + encrypt | style="color: #42427e" | | I at least plan to circle around the anaconda issues again

...James' reply...I guess it would be useful to hear opinions on whether the CommonBugs keyword is useful. | style="color: #818144" | [Bug 557588] File "/usr/lib/anaconda/iw/filter_gui.py", line 634

| style="color: #4b904b" | and I'm not sure if that's a grub feature, or an anaconda feature | style="color: #854685" | i'm sure i never put it in commonbugs, though.