Re: Release criteria proposal: i18n criteria
Thanks for considering to add a criterion for translations. I'm excited to see that. Since I missed this post, sorry for not bringing this up earlier. So I'd clarify this, what exactly "popular languages" is. that sounds like a quite vague and might make a flamewar when any case is raising. So that would be nice if it explicitly has the measurable way what we are fully going to support on the release, such as languages meets over 90% of translations complete at the translation deadline or stats on smolt etc. - 元のメッセージ - | During Final blocker review meetings, we've come up against a couple | of | bugsto do with missing translations that we'd like to consider for | Final | blocker status: | | https://bugzilla.redhat.com/show_bug.cgi?id=706756 | https://bugzilla.redhat.com/show_bug.cgi?id=676488 | | however we don't currently actually have any criteria that cover i18n | (translation) issues. We should probably require some basic level of | translation to be in place for particularly popular languages. How | about | a Final criterion, something like: | | * The installer, bootup and login processes should correctly display | all | translations that are available for use | | the intent is that where the translation team has actually provided | translations of this key content, they should be displayed, but we're | not going to block on no translations being available for some | language | or another. | | Thoughts? Thanks! | -- | Adam Williamson | Fedora QA Community Monkey | IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora | http://www.happyassassin.net | | -- | test mailing list | test@lists.fedoraproject.org | To unsubscribe: | https://admin.fedoraproject.org/mailman/listinfo/test | -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[Test-Announce] Cloud Test Day Today
The Fedora 16 cloud test day is going on today in #fedora-test-day. The main test day page [1] lists the details on all of the projects that are taking part in the test day. If you're interested, stop by and help test any or all of: - Aeolus [2] * Aeolus is software for running virtual machines both internally on your own equipment, and in Clouds from several leading vendors. All at the same time. - EC2 [3] * Fedora 16 will have official AMIs at the same time that final is released. You can use amazon's free usage tier or temporary accounts for the test day (details on the test day page). - OpenStack [4] * OpenStack builds and scales private and public clouds. - HekaFS [5] * CloudFS is a distributed fileysystem specifically intended to solve problems faced by a cloud provider when offering filesystem access “as a service” to cloud users (a.k.a. tenants). 1 http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Test_Day 2 http://fedoraproject.org/wiki/QA:Testcase_Aeolus 3 http://fedoraproject.org/wiki/Test_Day:2011-10-20_Cloud_SIG_Fedora_EC2 4 http://fedoraproject.org/wiki/Test_Day:2011-10-20_OpenStack_Test_Day 5 http://fedoraproject.org/wiki/SimpleHekaFS signature.asc Description: PGP signature ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: repo=hd: question
- Original Message - > From: "Chuck Forsberg WA7KGX N2469R" > To: "Fedora" > Sent: Thursday, October 20, 2011 4:21:43 AM > Subject: repo=hd: question > > > I have been experimenting with trying to load Fedora 16 > off a hard drive partition but can't quite get it to work. > The documentation I've found via Google is poor and > seems to conflict with what almost works. > > At some points it seems to be looking for a tree, not an ISO. > No tree,so not pass go. Later it complains about not finding > an iso image. > > So --- assuming I have /dev/sda2 reserved for storing Fedora > files, please state what goes where and what to specify > to which prompt. Please no references to dead URLs. > > -- > Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com > Developer of Industrial ZMODEM(Tm) for Embedded Applications >Omen Technology Inc "The High Reliability Software" > 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 Hi, Chuck, Since this is still no F16 release documents, so maybe the old release not does not work. There two way to install from hard drive. First upload the iso to the hard drive, such as /dev/sda2, then you can pass kernel arguments repo=hd:sda2:/path or askmethod, the latter will promote a dialogue box ask you to choose URL, NFS, Hard Drive etc. You much make sure you do not use sda2 during the installation, otherwise, the sda2 will be formatted, and the iso on it will be lost. Hongqing -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Pre TC2 Test boot.iso
There are new builds for anaconda and lorax, so we all know what that means ... Pre-TC2 Test Installer Time! http://tflink.fedorapeople.org/iso/20111019_preTC2.x64.iso http://tflink.fedorapeople.org/iso/20111019_preTC2.x64.iso.sha256 If you're able to install, please add karma to anaconda: - https://admin.fedoraproject.org/updates/anaconda-16.22-1.fc16 Thanks, Tim signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: repo=hd: question
On Wed, 2011-10-19 at 13:21 -0700, Chuck Forsberg WA7KGX N2469R wrote: > I have been experimenting with trying to load Fedora 16 > off a hard drive partition but can't quite get it to work. > The documentation I've found via Google is poor and > seems to conflict with what almost works. > > At some points it seems to be looking for a tree, not an ISO. > No tree,so not pass go. Later it complains about not finding > an iso image. > > So --- assuming I have /dev/sda2 reserved for storing Fedora > files, please state what goes where and what to specify > to which prompt. Please no references to dead URLs. https://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/s1-steps-hd-installs-x86.html https://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/ch-Boot-x86.html#s2-x86-starting-bootopts https://docs.fedoraproject.org/en-US/Fedora/15/html/Installation_Guide/s1-begininstall-hd-x86.html seem to cover the process. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
repo=hd: question
I have been experimenting with trying to load Fedora 16 off a hard drive partition but can't quite get it to work. The documentation I've found via Google is poor and seems to conflict with what almost works. At some points it seems to be looking for a tree, not an ISO. No tree,so not pass go. Later it complains about not finding an iso image. So --- assuming I have /dev/sda2 reserved for storing Fedora files, please state what goes where and what to specify to which prompt. Please no references to dead URLs. -- Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Bugzilla-Triage-Scripts 1.4.10 not working in firefox 7.0.1
> I hope this has been fixed in 1.4.11. Let me know if it is. It seems plugin still broken in 1.4.11. I have provided a screenshot. Take a look. https://fedorahosted.org/bugzilla-triage-scripts/ticket/117 Thanks, Mohan R -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
On Wed, 2011-10-19 at 13:37 -0500, Chris Adams wrote:
> Once upon a time, David Lehman said:
> > Ah, yes. Same bug for partitions. Presumably also for raid.
>
> Oh, you said it worked for you. What version were you testing?
I was not using --onpart. You were. That's the difference.
>
> > anaconda-16.18-1 added support for specifying reserved space in a _new_
> > vg for snapshots or whatever. I'm adding it to the wiki options page
> > now. The new options are both to the volgroup command:
> >
> > --reserved-space= (reserved space in mb)
> > --reserved-percent= (reserved percentage of vg space)
>
> Go to know.
>
> > Why do you care about the ordering of the LVs?
>
> Because ordering affects performance. For example, I set up a separate
> LV "queue" for the mail queue on a mail server; I also have a separate
> LV for /usr/local ("usrl", grows to fill the VG, minus space for
> snapshots) and /var ("var", where the logs live). Anaconda orders LVs
> alphabetically (last time I checked), which could put the mail queue and
> mail logs at nearly opposite ends of the disk.
I didn't realize lvm guarantees all lvs are allocated from adjacent
extents.
>
> > > Anaconda also doesn't allow custom RAID configuration options, such as
> > > metadata versions, chunk size, bitmaps, creation of RAID with missing
> > > devices (or IIRC RAID1 with 1 drive) for later expansion.
> >
> > We do create bitmaps where they make sense when creating md arrays since
> > around F13.
>
> That covers one option.
We also choose metadata version sensibly for you, unless you have some
highly specialized use-case. In that case you are free to use %pre as
you do now.
>
> I don't necessarily expect anaconda to expand to cover all the available
> options, but at the same time, anaconda shouldn't prevent admins from
> using the available options via %pre.
Anaconda doesn't prevent admins from using %pre, as you have
demonstrated.
Root filesystem creation is a special case. We have provided a mechanism
to specify custom options. Apparently nobody uses them the way that you
do, so you win the prize of discovering a bug. That's life on the
bleeding edge.
Dave
> --
> Chris Adams
> Systems and Network Administrator - HiWAAY Internet Services
> I don't speak for anybody but myself - that's enough trouble.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
Once upon a time, David Lehman said:
> Ah, yes. Same bug for partitions. Presumably also for raid.
Oh, you said it worked for you. What version were you testing?
> anaconda-16.18-1 added support for specifying reserved space in a _new_
> vg for snapshots or whatever. I'm adding it to the wiki options page
> now. The new options are both to the volgroup command:
>
> --reserved-space= (reserved space in mb)
> --reserved-percent= (reserved percentage of vg space)
Go to know.
> Why do you care about the ordering of the LVs?
Because ordering affects performance. For example, I set up a separate
LV "queue" for the mail queue on a mail server; I also have a separate
LV for /usr/local ("usrl", grows to fill the VG, minus space for
snapshots) and /var ("var", where the logs live). Anaconda orders LVs
alphabetically (last time I checked), which could put the mail queue and
mail logs at nearly opposite ends of the disk.
> > Anaconda also doesn't allow custom RAID configuration options, such as
> > metadata versions, chunk size, bitmaps, creation of RAID with missing
> > devices (or IIRC RAID1 with 1 drive) for later expansion.
>
> We do create bitmaps where they make sense when creating md arrays since
> around F13.
That covers one option.
I don't necessarily expect anaconda to expand to cover all the available
options, but at the same time, anaconda shouldn't prevent admins from
using the available options via %pre.
--
Chris Adams
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Meeting log/Summary from today's Proventesters meetup (2011-10-19)
=== #fedora-meeting: proventesters (2011-10-19) === Meeting started by nirik at 17:59:58 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2011-10-19/proventesters.2011-10-19-17.59.log.html Meeting summary --- * Into/Gather topics (nirik, 18:00:07) * Followups (nirik, 18:02:51) * LINK: https://fedoraproject.org/wiki/Package_tester_resources (nirik, 18:03:41) * LINK: http://lists.fedoraproject.org/pipermail/websites/2011-October/018915.html (tflink, 18:05:27) * Recruitment (nirik, 18:06:55) * Pending critpath/security updates in stable releases. (nirik, 18:08:19) * F14: 11 security updates, 13 critpath (nirik, 18:09:09) * F15: 11 security updates, 23 critpath (nirik, 18:09:46) * F16: 8 security updates, 23 critpath (nirik, 18:10:25) * LINK: https://admin.fedoraproject.org/updates/glibc-2.14.90-13 (nirik, 18:15:38) * bodhi bug to try and get more readable updates-testing reports: https://fedorahosted.org/bodhi/ticket/644 (nirik, 18:16:02) * Open Floor (nirik, 18:27:47) * will meet next week (nirik, 18:32:37) Meeting ended at 18:33:41 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * nirik (58) * tflink (19) * brunowolff (8) * zodbot (3) * Southern_Gentlem (2) * satellit_ (2) -- 17:59:58 #startmeeting proventesters (2011-10-19) 17:59:58 Meeting started Wed Oct 19 17:59:58 2011 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:59:58 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:59:58 #meetingname proventesters 17:59:58 The meeting name has been set to 'proventesters' 18:00:03 * Southern_Gentlem 18:00:07 #topic Into/Gather topics 18:00:18 Who all is around for a packager tester meeting? ;) 18:00:36 * Southern_Gentlem 18:01:18 hey Southern_Gentlem. ;) Might be it's just us today... 18:01:27 * tflink is here 18:02:24 hey tflink 18:02:24 * satellit_ listening 18:02:30 morning satellit_ 18:02:35 : ) 18:02:45 ok, so I guess lets dive in... 18:02:51 #topic Followups 18:03:27 nirik to try and make a resource page, help welcome -> 18:03:34 I made a start on one. 18:03:41 https://fedoraproject.org/wiki/Package_tester_resources 18:03:50 needs a lot of work, but it's a start. 18:04:10 I'd like to add links to everything to make it easy for people to click thru to whatever they need. 18:04:39 So, help needed, feel free to edit it. ;) 18:04:45 tflink: tflink to ping websites about changing how tester is setup in join-fedora 18:05:03 that fell off my todo list until today 18:05:15 * nirik doesn't see athmane or tomspur around for their items. 18:05:20 I sent a message a little while ago, no response as of yet 18:05:27 http://lists.fedoraproject.org/pipermail/websites/2011-October/018915.html 18:05:41 cool. Thanks. 18:05:55 any other followup items/ 18:05:56 ? 18:06:55 #topic Recruitment 18:07:07 Any recruitment ideas we can move on... 18:07:53 I can't think of any that we haven't already covered 18:08:19 #topic Pending critpath/security updates in stable releases. 18:09:09 #info F14: 11 security updates, 13 critpath 18:09:46 #info F15: 11 security updates, 23 critpath 18:10:25 #info F16: 8 security updates, 23 critpath 18:10:47 * nirik is reminded to submit that bodhi bug asking for the names back in the updates-testing report. 18:11:42 Can we talk about the glibc update? 18:11:52 brunowolff: sure. The f16 one? 18:12:09 for F16, aren't the 2 pending grub updates obsolete? 18:12:15 -81 and -82 18:12:34 I gave it a +1 because it fixed a bug that was impacting me and of the two -1s, one had no indication why it was -1 and the other 18:13:17 reported a problem with building another package, which depending on why it wasn't building, didn't seem to necessarily be a blocker. 18:13:54 So should I have just done a +0 with a note that it fixed the bug, or was a +1 more appropriate. 18:14:10 brunowolff: +1 was ok there I think. 18:14:40 * nirik notes there's a newer one already. 18:14:48 It turns out my vote was the one that allowed it to go to updates. 18:15:05 I saw there was a newer one, but haven't tested it yet. 18:15:26 I think it was ok to go to updates, because it fixed runtime issues... the FTBFS needs to be fixed, but letting that one go out at least fixed runtime issues. 18:15:38 https://admin.fedoraproject.org/updates/glibc-2.14.90-13 18:15:54 I thought this was a good case to get feedback on some of the nuances of providing testing feedback. 18:16:02 #info bodhi bug to try and get more readable updates-testing reports: https://fedorahosted.org/bodhi/ticket/644 18:16:16 sadly, we only have +1, -1... which makes it hard 18:17:11 true, but would it really be better to have stuff like +/- .5 or ar
Re: firstaidkit-plugin-grub breaking tree compose.
On Wed, Oct 19, 2011 at 09:24:20AM -0600, Kevin Fenzi wrote: > On Wed, 19 Oct 2011 11:20:49 -0400 > Dave Jones wrote: > > > On Tue, Oct 18, 2011 at 10:49:17AM -0400, Dave Jones wrote: > > > On Mon, Oct 17, 2011 at 08:17:20PM -0500, den...@ausil.us wrote: > > > > And the night before grub changes broke lorax. > > > > > > and today they broke firstaidkit-plugin-grub. > > > > > > yum transaction error: [u'ERROR with transaction check vs > > > depsolve:', 'grub is needed by > > > firstaidkit-plugin-grub-0.3.1-1.fc16.i686' > > (http://kojipkgs.fedoraproject.org/mash/branched-20111018/logs/pungify-i386.log) > > > > So this is continuing to break the daily compose. > > Should it just be dropped from 16, or is there a grub2 version > > waiting ? > > > > Martin ? > > My understanding is that a new lorax is coming that doesn't have this > dep in place. Not sure what the status is on that thought. > > kevin Martin private-mailed me to let me know a build of firstaidkit without the grub plugin has been done, so it should just sort itself out soon. Dave -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F16 : bash paint and paste gone?
On F16 with xfce (left gnome because it's too strange): I can't just paint text with a mouse and the paste it with a click of the scroll wheel. I have to rt-click copy and rt-click paste. Is this a feature gone with F16, or is this a gnome-ism that doesn't exist in xfce? sean -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Re: Grub -> grub2?
On Sunday 16 Oct 2011 16:44:29 David wrote: > > Thank you. That is where I had expected it to go. Hi David, quick update... I don't know if you've noticed but with that vga=0x305 on that linux line, I get a message at boot time telling me that its depreciated and to use 'set gfxpayload=1024x768x8,1024x768' instead so I did just that, remove the vga=0x305 and then just above that there is already a line saying 'set gfxpayload=keep', I changed the 'keep' to '1024x768x8,1024x768' and it boots now with the right resolution and no depreciated message at boot. Martin signature.asc Description: This is a digitally signed message part. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
On Wed, 2011-10-19 at 07:51 -0400, Kamil Paral wrote: > > > I imagine this could be very inconvenient for me when switching > > > distributions. I always have / and /home on the same partition. If > > > I > > > want hypothetically to go from let's say Ubuntu to Fedora, I delete > > > all files except /home and then select that partition for /. If you > > > force me to format that partition then I can't easily switch to > > > Fedora, because my /home is huge and I have no external space to > > > back > > > it up. > > > > Why not have /home as a separate partition? This is the classic > > reason > > for doing so. I mean, what you're doing in the above is basically > > 'faking' a /home partition. > > -- > > Adam Williamson > > Because I never saw reason to do so. Having / and /home on the same > partition saves you from problems with insufficient disk space in one > place and too much space in the second place. So does LVM, which is exactly why we started using it by default. Resizing an LVM 'partition' is extremely simple to do and very safe. If you find you got the sizes of / and /home wrong, just change 'em. > The only concern I ever had for my layout is whether the next distro > installer would be smart enough to let me skip formatting of the / > partition. Therefore I'm not thrilled to see Anaconda go the other > way. Anaconda team consider skipping format of / to be a *dumb* thing to do, not a smart one... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
On Wed, 2011-10-19 at 11:00 -0500, Chris Adams wrote: > Once upon a time, David Lehman said: > > You found a bug. We don't honor fsprofile when --useexisting is passed > > to the logvol command. If you file a bug it can be fixed pretty easily. > > Or, if you just let anaconda create your logical volumes for you you > > won't hit the bug. > > I wondered if that was the problem. However, I also don't see my test > settings applied to /boot. Ah, yes. Same bug for partitions. Presumably also for raid. > > > Out of curiosity, why are you doing the partitioning and lvm stuff in % > > pre? > > Anaconda doesn't give any controls of ordering or layout of LVs. For > example, I use LVM snapshots for backups. I create the LVs with a > little empty space at the end to use for the snapshot (so it stays close > to the original data). I also then need to leave a certain amount (that > I figure in percent) of the VG free for snapshot space. anaconda-16.18-1 added support for specifying reserved space in a _new_ vg for snapshots or whatever. I'm adding it to the wiki options page now. The new options are both to the volgroup command: --reserved-space= (reserved space in mb) --reserved-percent= (reserved percentage of vg space) > > I've also used mirrored LVs for some setups in the past. I actually did > that with a crazy hack that involved bind mounting a wrapper script over > lvcreate (so I didn't do partitioning/LV setup in %pre). :-) > > The ordering wouldn't be hard to handle in anaconda, but the other > things would be tricky. I guess if anaconda had ordering controls, I > could use a bunch of scratch LVs in between each "real" LV (and then > delete the scratch LVs in %post). That might also work to reserve space > for snapshots. Why do you care about the ordering of the LVs? > > Anaconda also doesn't allow custom RAID configuration options, such as > metadata versions, chunk size, bitmaps, creation of RAID with missing > devices (or IIRC RAID1 with 1 drive) for later expansion. We do create bitmaps where they make sense when creating md arrays since around F13. Dave > > -- > Chris Adams > Systems and Network Administrator - HiWAAY Internet Services > I don't speak for anybody but myself - that's enough trouble. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
Once upon a time, David Lehman said: > You found a bug. We don't honor fsprofile when --useexisting is passed > to the logvol command. If you file a bug it can be fixed pretty easily. > Or, if you just let anaconda create your logical volumes for you you > won't hit the bug. I wondered if that was the problem. However, I also don't see my test settings applied to /boot. > Out of curiosity, why are you doing the partitioning and lvm stuff in % > pre? Anaconda doesn't give any controls of ordering or layout of LVs. For example, I use LVM snapshots for backups. I create the LVs with a little empty space at the end to use for the snapshot (so it stays close to the original data). I also then need to leave a certain amount (that I figure in percent) of the VG free for snapshot space. I've also used mirrored LVs for some setups in the past. I actually did that with a crazy hack that involved bind mounting a wrapper script over lvcreate (so I didn't do partitioning/LV setup in %pre). :-) The ordering wouldn't be hard to handle in anaconda, but the other things would be tricky. I guess if anaconda had ordering controls, I could use a bunch of scratch LVs in between each "real" LV (and then delete the scratch LVs in %post). That might also work to reserve space for snapshots. Anaconda also doesn't allow custom RAID configuration options, such as metadata versions, chunk size, bitmaps, creation of RAID with missing devices (or IIRC RAID1 with 1 drive) for later expansion. -- Chris Adams Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: F16 TC1 graphics problem
On Tue, 2011-10-18 at 14:38 -0500, Michael Cronenworth wrote: > Adam Williamson wrote: > > That's not the same thing at all. That's exactly the*opposite* thing. > > Maybe it's opposite day for Mr. Chambers, Adam. :p Yea SMH haha -- Mike Chambers Madisonville, KY "The best town on Earth!" -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Error adding second ide disk in virt-manager
Hello,
I have F15 + virt-preview environment.
I configured a vm with "kernel 2.6 with virtio" (in virt-manager.log I
get "OS: linux:virtio26").
Then I changed config and deleted disk0 and created it as an ide disk.
Booting from CD I installed the OS without problems.
I then added a second ide disk.
Now I get an error on start after adding this second ide disk
Error starting domain: internal error Process exited while reading
console log output: qemu-kvm: -drive
file=/var/lib/libvirt/images/ovm1-2.img,if=none,id=drive-ide0-0-0,format=raw:
Duplicate ID 'drive-ide0-0-0' for drive
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in startup
self._backend.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 510, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Process exited while reading console log
output: qemu-kvm: -drive
file=/var/lib/libvirt/images/ovm1-2.img,if=none,id=drive-ide0-0-0,format=raw:
Duplicate ID 'drive-ide0-0-0' for drive
the relevant part written in xml file is indeed:
With virsh edit I change the second to
and I'm able to boot with the new second disk in place...
Do I have to file a bug or is this an "unsupported" way of operation
(create as 2.6+virtio and then remove virtio disk and use ide)?
Gianuca
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
On Tue, 2011-10-18 at 21:57 -0500, Chris Adams wrote:
> Once upon a time, David Lehman said:
> > I just tried it and it worked fine. If you put your ks.cfg and
> > the /tmp/storage.log from your install somewhere I can take a look and
> > tell you what went wrong.
>
> Okay, I'm probably doing it wrong then. Here's my simplified ks.cfg.
> It is a simplified example of partitioning and setting up LVM in %pre
> (this example obviously doesn't do anything special, but I have actual
> kickstarts that do), but I switched to letting anaconda make the
> filesystems. I set a couple of simple ext4 options that stand out
> clearly after the fact. Looking at program.log, the "-T myopt" didn't
> get passed to mke2fs.
You found a bug. We don't honor fsprofile when --useexisting is passed
to the logvol command. If you file a bug it can be fixed pretty easily.
Or, if you just let anaconda create your logical volumes for you you
won't hit the bug.
Out of curiosity, why are you doing the partitioning and lvm stuff in %
pre?
Dave
>
> If you still want the storage.log (i.e. I'm not doing something
> obviously wrong), I'll send it to you off-list (it is 83K).
>
>
> repo --name="Fedora 16 Beta"
> --baseurl=http://mirror.hiwaay.net/pub/fedora/linux/releases/test/16-Beta/Fedora/x86_64/os/
>
> rootpw testpw
> sshpw --username=root testpw --plaintext
> network --device=eth0 --bootproto dhcp
> lang en_US.UTF-8
> install
> text
> skipx
> halt
> selinux --permissive
> keyboard us
> timezone --utc America/Chicago
> auth --useshadow --passalgo=sha512
> firewall --disabled
> # See BZ 720027
> bootloader --location=mbr --append="rd.plymouth=0 console=tty0
> console=ttyS0,115200"
>
> part /boot --onpart=vda1 --fstype=ext4 --fsprofile=myopt
> part pv.1 --onpart=vda2 --noformat
> volgroup fdev pv.1 --noformat
> logvol / --vgname=fdev --name=root --fstype=ext4 --useexisting
> --fsprofile=myopt
> logvol swap --vgname=fdev --name=swap --fstype=ext4 --useexisting
>
> %packages --nobase
> @ Core --nodefaults
> yum
> %end
>
> %pre --erroronfail
> set -e
>
> cat >> /etc/mke2fs.conf < myopt = {
> inode_ratio = 65536
> options = stride=32,stripe-width=64
> }
> EOF
>
> dd if=/dev/zero bs=512 count=63 of=/dev/vda
> parted -s /dev/vda "unit s" "mklabel msdos" \
> "mkpart primary ext2 2048 1048575" \
> "mkpart primary ext2 1048576 -1" \
> "set 2 lvm on"
> lvm pvcreate -ff -y /dev/vda2
> lvm vgcreate -ff -s 16M fdev /dev/vda2
> lvm lvcreate -n root -L 1500M fdev
> lvm lvcreate -n swap -L 1000M fdev
> lvm vgchange -an
> %end
>
>
> --
> Chris Adams
> Systems and Network Administrator - HiWAAY Internet Services
> I don't speak for anybody but myself - that's enough trouble.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: firstaidkit-plugin-grub breaking tree compose.
On Wed, 19 Oct 2011 11:20:49 -0400 Dave Jones wrote: > On Tue, Oct 18, 2011 at 10:49:17AM -0400, Dave Jones wrote: > > On Mon, Oct 17, 2011 at 08:17:20PM -0500, den...@ausil.us wrote: > > > And the night before grub changes broke lorax. > > > > and today they broke firstaidkit-plugin-grub. > > > > yum transaction error: [u'ERROR with transaction check vs > > depsolve:', 'grub is needed by > > firstaidkit-plugin-grub-0.3.1-1.fc16.i686' > (http://kojipkgs.fedoraproject.org/mash/branched-20111018/logs/pungify-i386.log) > > So this is continuing to break the daily compose. > Should it just be dropped from 16, or is there a grub2 version > waiting ? > > Martin ? My understanding is that a new lorax is coming that doesn't have this dep in place. Not sure what the status is on that thought. kevin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
firstaidkit-plugin-grub breaking tree compose.
On Tue, Oct 18, 2011 at 10:49:17AM -0400, Dave Jones wrote: > On Mon, Oct 17, 2011 at 08:17:20PM -0500, den...@ausil.us wrote: > > And the night before grub changes broke lorax. > > and today they broke firstaidkit-plugin-grub. > > yum transaction error: [u'ERROR with transaction check vs depsolve:', 'grub > is needed by firstaidkit-plugin-grub-0.3.1-1.fc16.i686' > (http://kojipkgs.fedoraproject.org/mash/branched-20111018/logs/pungify-i386.log) So this is continuing to break the daily compose. Should it just be dropped from 16, or is there a grub2 version waiting ? Martin ? Dave -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
rawhide report: 20111019 changes
Compose started at Wed Oct 19 08:15:57 UTC 2011 Broken deps for x86_64 -- 389-admin-1.1.23-1.fc17.i686 requires libicuuc.so.46 389-admin-1.1.23-1.fc17.i686 requires libicui18n.so.46 389-admin-1.1.23-1.fc17.i686 requires libicudata.so.46 389-admin-1.1.23-1.fc17.x86_64 requires libicuuc.so.46()(64bit) 389-admin-1.1.23-1.fc17.x86_64 requires libicui18n.so.46()(64bit) 389-admin-1.1.23-1.fc17.x86_64 requires libicudata.so.46()(64bit) 389-adminutil-1.1.14-1.fc16.i686 requires libicuuc.so.46 389-adminutil-1.1.14-1.fc16.i686 requires libicui18n.so.46 389-adminutil-1.1.14-1.fc16.i686 requires libicudata.so.46 389-adminutil-1.1.14-1.fc16.x86_64 requires libicuuc.so.46()(64bit) 389-adminutil-1.1.14-1.fc16.x86_64 requires libicui18n.so.46()(64bit) 389-adminutil-1.1.14-1.fc16.x86_64 requires libicudata.so.46()(64bit) 389-dsgw-1.1.7-2.fc16.x86_64 requires libicuuc.so.46()(64bit) 389-dsgw-1.1.7-2.fc16.x86_64 requires libicui18n.so.46()(64bit) 389-dsgw-1.1.7-2.fc16.x86_64 requires libicudata.so.46()(64bit) assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libicuuc.so.46()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libicui18n.so.46()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit) cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit) comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1 contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit) couchdb-1.0.3-2.fc16.x86_64 requires libicuuc.so.46()(64bit) couchdb-1.0.3-2.fc16.x86_64 requires libicui18n.so.46()(64bit) couchdb-1.0.3-2.fc16.x86_64 requires libicudata.so.46()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper ease-0.4-9.fc17.i686 requires libclutter-gtk-0.10.so.0 ease-0.4-9.fc17.x86_64 requires libclutter-gtk-0.10.so.0()(64bit) ease-devel-0.4-9.fc17.i686 requires pkgconfig(clutter-gtk-0.10) ease-devel-0.4-9.fc17.x86_64 requires pkgconfig(clutter-gtk-0.10) emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave fldigi-3.21.7-1.fc16.x86_64 requires libfltk_images.so.1.1()(64bit) fldigi-3.21.7-1.fc16.x86_64 requires libfltk.so.1.1()(64bit) gcc-python2-debug-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gcc-python2-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gcc-python3-debug-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gcc-python3-plugin-0.6-3.fc17.x86_64 requires gcc = 0:4.6.1-9.fc17 gdcm-2.0.17-7.fc17.i686 requires libvtkverdict.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtksys.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtksqlite.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkmetaio.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkftgl.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkexoIIc.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkWidgets.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkRenderingPythonD.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkRendering.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkParallel.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkNetCDF_cxx.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkNetCDF.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkImagingPythonD.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkImaging.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkIOPythonD.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkIO.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkHybrid.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkGraphicsPythonD.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkGraphics.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkFilteringPythonD.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkFiltering.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkDICOMParser.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkCommonPythonD.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libvtkCommon.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libVPIC.so.5.6 gdcm-2.0.17-7.fc17.i686 requires libCosmo.so.5.6 gdcm-2.0.17-7.fc17.x86_64 requires libvtkverdict.so.5.6()(64bit) gdcm-2.0.17-7.fc17.x86_64 requires libvtksys.so.5.6()(64bit) gdcm-2.0.17-7.fc17.x86_64 requires libvtksqlite.so.5.6()(64bit) gdcm-2.0.17-7.fc17.x86_64 requires libvtkmetaio.so.5.6()(64bit) gdcm-2.0.17-7.fc17.x86_64 requires libvtkftgl.so.5.6()(64bit) gdcm-2.0.17-7.fc17.x86_64 requires libvtkexoIIc.so.5.6()(64bit) gdcm-2.0.17-7.fc17.x86_64 requires libv
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
On Wed, 19 Oct 2011 07:51:40 -0400 (EDT) Kamil Paral wrote: > > > I imagine this could be very inconvenient for me when switching > > > distributions. I always have / and /home on the same partition. If > > > I > > > want hypothetically to go from let's say Ubuntu to Fedora, I > > > delete all files except /home and then select that partition > > > for /. If you force me to format that partition then I can't > > > easily switch to Fedora, because my /home is huge and I have no > > > external space to back > > > it up. > > > > Why not have /home as a separate partition? This is the classic > > reason > > for doing so. I mean, what you're doing in the above is basically > > 'faking' a /home partition. > > -- > > Adam Williamson > > Because I never saw reason to do so. Having / and /home on the same > partition saves you from problems with insufficient disk space in one > place and too much space in the second place. FWIW, this was exactly our reason too, especially a few years back when disk space was relatively expensive compared to a Fedora install (ie 20 GB harddrives with 5 GB fedora -> 25%). Nowadays there is much less reason not to have separate filesystems wrt space, agreed. But it will cause some migration pain as we have a nice system in place to preserve local user data. We will manage, but I just wanted to state that there was a "valid" use case. Regards, --Stijn -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
F-16 Branched report: 20111019 changes
Compose started at Wed Oct 19 08:16:10 UTC 2011 Broken deps for x86_64 -- aeolus-all-0.4.0-1.fc16.noarch requires rubygem(aeolus-cli) aeolus-conductor-0.4.0-1.fc16.noarch requires rubygem(oauth) aeolus-conductor-0.4.0-1.fc16.noarch requires rubygem(deltacloud-client) >= 0:0.4.0 aeolus-conductor-devel-0.4.0-1.fc16.noarch requires rubygem(webmock) assogiate-0.2.1-5.fc15.x86_64 requires libgnomevfsmm-2.6.so.1()(64bit) bibletime-2.8.1-1.fc16.x86_64 requires libclucene.so.0()(64bit) cluster-snmp-0.18.7-1.fc16.x86_64 requires libnetsnmp.so.25()(64bit) comoonics-cdsl-py-0.2-18.noarch requires comoonics-base-py comoonics-cluster-py-0.1-24.noarch requires comoonics-base-py contextkit-0.5.15-2.fc15.i686 requires libcdb.so.1 contextkit-0.5.15-2.fc15.x86_64 requires libcdb.so.1()(64bit) dh-make-0.55-3.fc15.noarch requires debhelper dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-tks-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-ra-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-kra-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-tps-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-console-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-ocsp-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-common-theme >= 0:9.0.9 dogtag-pki-9.0.0-7.fc16.noarch requires dogtag-pki-ca-theme >= 0:9.0.9 emacs-spice-mode-1.2.25-5.fc15.noarch requires gwave fawkes-core-0.4.2-4.fc16.i686 requires libopencv_core.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_features2d.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_ml.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_legacy.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_contrib.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_flann.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_highgui.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_video.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_objdetect.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_calib3d.so.2.2 fawkes-core-0.4.2-4.fc16.i686 requires libopencv_imgproc.so.2.2 fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_imgproc.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_objdetect.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_contrib.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_core.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_legacy.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_highgui.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_flann.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_ml.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_video.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_features2d.so.2.2()(64bit) fawkes-core-0.4.2-4.fc16.x86_64 requires libopencv_calib3d.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_objdetect.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_flann.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_calib3d.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_core.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_ml.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_legacy.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_contrib.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_highgui.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_imgproc.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_video.so.2.2 fawkes-firevision-0.4.2-4.fc16.i686 requires libopencv_features2d.so.2.2 fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_legacy.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_imgproc.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_highgui.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_features2d.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_objdetect.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_ml.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_video.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x86_64 requires libopencv_calib3d.so.2.2()(64bit) fawkes-firevision-0.4.2-4.fc16.x8
Re: / must be on a partition or LV that will be formatted. Reusing an existing / is not allowed.
> > I imagine this could be very inconvenient for me when switching > > distributions. I always have / and /home on the same partition. If > > I > > want hypothetically to go from let's say Ubuntu to Fedora, I delete > > all files except /home and then select that partition for /. If you > > force me to format that partition then I can't easily switch to > > Fedora, because my /home is huge and I have no external space to > > back > > it up. > > Why not have /home as a separate partition? This is the classic > reason > for doing so. I mean, what you're doing in the above is basically > 'faking' a /home partition. > -- > Adam Williamson Because I never saw reason to do so. Having / and /home on the same partition saves you from problems with insufficient disk space in one place and too much space in the second place. The only concern I ever had for my layout is whether the next distro installer would be smart enough to let me skip formatting of the / partition. Therefore I'm not thrilled to see Anaconda go the other way. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Anaconda: Check before Destroy PLS
> Would it be too much to have Anaconda check for the > repodata files it wants before scribbling on the hard drive(s)? > > -- > Chuck Forsberg WA7KGX N2469R c...@omen.com www.omen.com > Developer of Industrial ZMODEM(Tm) for Embedded Applications >Omen Technology Inc "The High Reliability Software" > 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 > Hello. You probably want to contact Anaconda team: https://fedoraproject.org/wiki/Anaconda#Mailing_Lists -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
