On Saturday, May 12, 2012 07:23:36 PM Graham P Davis wrote:

On Sat, 12 May 2012 22:40:31 +1000

Basil Chupin wrote:

...

I downloaded the KDE LIVE CD Build #369 from here a couple of hours ago-

http://download.opensuse.org/factory/iso/

But don't waste your time - it is as useful as teats on a bull when it comes to even trying to run as a Live CD.

You don't get the usual GUI menu to select from when it starts up but get a command line menu (which take a bit of time to work out what it wants you to type in) and when you do get something to happen you get error messages,

I get something vaguely similar when installing via a CD or DVD on a machine with UEFI. Starts with elilo boot and almost always skips the first couple of pages and goes straight into installation. However, if I install from flash drive instead, I get no such trouble. This occurred with M3 and #358. Haven't bothered burning #369 to CD - just used flash drive.

-- Graham Davis, Bracknell, Berks. openSUSE 12.1 (64-bit); KDE 4.8.3; AMD Phenom II X2 550 Processor; Video: nVidia GeForce 210 (using nVidia driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org I saw the same thing yesterday trying to install 357 and 358 32-bit versions on an older PC that used to run XP (Celron Cpu, 2 GB memory, 122 GB IDE Disk). Gets kernel panic after install when I boot. Kernal is 3.x so no patch was supposed to be need.

I also tried Mageia 32 bit beta 3. Installs fine, but boot hang at splash screen . This system I think has an intel graphics card on board. Wii play with it some more, post anything I find. Not sure if it is the machine or Install. All 32-bit live cd's fail on this system the same way. Any ideas will be appricated. Do not want to try on machine I'm on now as its my production stuff. Russ openSUSE 12.1(3.1.10-1.9-desktop x86_64)|KDE Platform Version 4.8.3 (4.8.3) "release 501"|Intel core2duo 2.5 MHZ,|8GB DDR3|GeForce 8400GS(NVIDIA-Linux-x86_64-295.49) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2012/5/13 Basil Chupin :

On 13/05/12 04:23, Graham P Davis wrote:

...

On Sat, 12 May 2012 22:40:31 +1000 Basil Chupin  wrote:

...

I downloaded the KDE LIVE CD Build #369 from here a couple of hours ago-

http://download.opensuse.org/factory/iso/

But don't waste your time - it is as useful as teats on a bull when it comes to even trying to run as a Live CD.

You don't get the usual GUI menu to select from when it starts up but get a command line menu (which take a bit of time to work out what it wants you to type in) and when you do get something to happen you get error messages,

I get something vaguely similar when installing via a CD or DVD on a machine with UEFI. Starts with elilo boot and almost always skips the first couple of pages and goes straight into installation. However, if I install from flash drive instead, I get no such trouble. This occurred with M3 and #358. Haven't bothered burning #369 to CD - just used flash drive.

Interesting. I have a dual-BIOS which has EFI. So you are suggesting that I, and anyone else, should try puttiing the CD onto a flash card and using that? :-) . And why not - I may just try and do that.

I have been wondering how so many people have gone as far as having Milestone #4 installed and not complain about not being able to use, say, the LIVE CD[@]. I thought, "Maybe the LIVE CDs are being developed on an IBM 'Blue Gene' computer for use by people with CRAY computers :-) .  Well, I asked a friend about this (he is running Milestone #4) and his response overnight was that he installed 12.1 and then uses "zypper dup" to keep upgrading from Milestone to Milestone. Which I suspect is what the developers are doing and so don't see the problems with the CDs. At least this is my thinking :-) .

[@] On the other hand, is seems that the DVDs don't suffer from this same malady - but then it takes a lot of download time (10+ hours for me) to grab a DVD - and for a Milestone? forget it.

I tryed to install openSUSE-DVD-Build0315-x86_64, and appear similar problems. I do'nt have bios; my computer has a dual-BIOS which has EFI (mobo Gigabyte 880-GM-USB3). Because the DVD do'nt worked, then I tryed with the KDE- Live, with 3 different versions, and the problem continues. The only install via that worked without problems to begin the install process without errors, was the NET install version build 359, but I do'nt completed the install process, because it is so slowly, because my adsl connection is 600 kbits/sec. Take a look at the Bug 761984. If some one want to add more info and details, this is the link: https://bugzilla.novell.com/show_bug.cgi?id=761984 Cheers, Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2012/5/12 Juan Erbes :

2012/5/12

...

Hello, Some questions: - Why are builds not at the same level and build date? [1] - Can the KDE-LiveCD-x86_64 be fixed so its at the same level and date as the NET iso build ? - Which project builds the KDE-LiveCD-x86_64 iso's ? - Have you a link to it please ? Thanks Glenn

[1]Sourced from http://ftp5.gwdg.de/pub/opensuse/factory/iso/

openSUSE-KDE-LiveCD-x86_64-Build0358-Media.iso   04-May-2012 23:39  650M openSUSE-NET-x86_64-Build0369-Media.iso          11-May-2012 20:30  225M

I mean it's time to open a Bug in Bugzilla.

This problem is 4 months old: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/...

I opened a thread in this list as "Opensuse 12.2 M3 and M4 is getting worse", with this title to have a little attention about it, but nothing happened.

They are a topic "Status: M3", with this text:

On 04/10/2012 03:22 PM, Andreas Jaeger wrote:

   On 04/10/2012 09:13 PM, Larry Finger wrote:

       On 04/10/2012 02:13 AM, Andreas Jaeger wrote:

           Just a short update: The x86-64 media look fine but the i686 have broken            metadata or contents, installation is not possible at all with them.

       I tried the KDE Live CD x86_64 Build 315 on a VirtualBox VM. It fails        the same way that the i686 version does with the following:

       Loading KIWI CD Boot-System...        ------------------------------        Creating device nodes with udev        /sbin/udevd: error while loading shared libraries: libkmod.so.2: cannot        open shared object file: No such file or directory        /sbin/udevadm: <Same error message>        /sbin/udevadm: <Same error message>        [ 0.983960] Searching for boot device in Application ID...............        [ 75.614699] Failed to find MBR identifier !        [ 75.635841] rebootException: error consoles at Alt-F3/F4        [ 75.649460] rebootException: reboot in 120 sec...

       It appears that libkmod.so.2 is not available. On the VM, I have not        been able to access the error console.

   Yeah, those are totally broken. Anybody interested in looking into this?

Know and fixed issue, we need a new version of KIWI in Factory. SR is pending.... anyone with the appropriate powers just needs to pull this into Factory ;)

fixed issue??????

The boot image, for opensuse 12.2, appear to be from opensuse 12.1: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/...

[ 6.59949] Activating Image: [/cdrom/openSUSE-12.1-livecd-kde.x64_64-2.8.0]

I placed the pictures of the screen of my computer, with the same problem on the topic:  "Opensuse 12.2 M3 and M4 is getting worse"

Bug 761984 Submitted If some one want to add more info and details, this is the link: https://bugzilla.novell.com/show_bug.cgi?id=761984 Cheers, Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2012/5/13 Stephan Kulow :

Am 12.05.2012 17:03, schrieb Juan Erbes:

...

Bug 761984 Submitted

If some one want to add more info and details, this is the link:

https://bugzilla.novell.com/show_bug.cgi?id=761984

Your bug report is useless - the reason for the live cd not working changes from week to week, but in general it has one reason: no one is maintaining them and they are basically test cases for kiwi, that most often fail ;(

Well, if I the last DVD fails to install, after 24 hours of downloadong the iso image, the only way to test opensuse with the option to install, is the CD Live, because at my home I have only one computer, and I could'nt leave the computer useles a complete day installing the NET install version. Do You understand me? How do You test any DVD version of opensuse, if it really installs without problems? I hope You do'nt make the tests in a virtual machine like VMware... Regards, Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2012/5/14 Stephan Kulow :

On 14.05.2012 00:29, Juan Erbes wrote:

...

Well, if I the last DVD fails to install, after 24 hours of downloadong the iso image, the only way to test opensuse with the option to install, is the CD Live, because at my home I have only one computer, and I could'nt leave the computer useles a complete day installing the NET install version.

Do You understand me? Yes, but beside "well" you don't appear to answer my point, but just repeating yours.

...

How do You test any DVD version of opensuse, if it really installs without problems? I hope You do'nt make the tests in a virtual machine like VMware...

Nah, of course not! We use kvm.

I'm Sorry, because my english is so poor! And I'm sorry again, because the DVD x86-64- build 315, I only tested it testee on a single computer that had recently builded with a used Athlon 2 X2 240 with a new mobo ASROCK 880-GM-LE FX, and the dvd failed, with similar fails than all the cd live from opensuse 12.2. Later, I tested in the same computer a older dvd version of opensuse (11.1 or 11.2), and it has installed without errors. Yesterday, I wanted to see what errors gives the DVD x86-64 build 315 on my computer (Phenom 2 X4 965 - mobo Gigabyte GM-880-USB3) on the boot and the begin of the install procces until the begin the format of the partitions, on which I canceled it, and I got no errors. I'ts a little strange, because has the same chipset than the other on which failed (Athlon 2 X2 240 with a new mobo ASROCK 880-GM-LE FX). I do'nt remember right now, but I mean the error on this computer was related to the TSC clock calibration. Regards, Juan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 13.05.2012 20:14, Stephan Kulow wrote:

Someone needs to fix them build and then this will be the case. But as the only one who cares for this is me, it only gets very little attention. And with so little interest the live cds get, I consider dropping them alltogether.

That might have to do with the fact that the byzantine build system in openSUSE:Factory:Live is completely undocumented. A couple of weeks ago I started looking into producing an Xfce LiveCD, building a simple non-installable CD with kiwi was rather straightforward, integrating with the openSUSE:Factory:Live packages was not and I gave up in frustration after some time. I'm still interested though and have a bunch of questions queued up, are you the only one who has an understanding of how these LiveCDs are built? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 14.05.2012 10:52, Stephan Kulow wrote:

On 13.05.2012 21:50, Guido Berhoerster wrote:

...

On 13.05.2012 20:14, Stephan Kulow wrote:

...

Someone needs to fix them build and then this will be the case. But as the only one who cares for this is me, it only gets very little attention. And with so little interest the live cds get, I consider dropping them alltogether.

That might have to do with the fact that the byzantine build system in openSUSE:Factory:Live is completely undocumented. A couple of weeks ago I started looking into producing an Xfce LiveCD, building a simple non-installable CD with kiwi was rather straightforward, integrating with the openSUSE:Factory:Live packages was not and I gave up in frustration after some time. I'm still interested though and have a bunch of questions queued up, are you the only one who has an understanding of how these LiveCDs are built?

It's not really complicated, I wonder where you failed - and I'm really having a huge IRC time window to not miss me. Anyway.

It wasn't my intent to blame you, I simply wasn't able to figure out *by myself* from looking through the packages without any further documentation why things are done the way they are done and how it fits together (e.g. why the manual package-lists-* and repo creation rather than using a pattern in kiwi, what the _product stuff does). I am still planning to get back to this to produce an installable Xfce LiveCD, I had a catalog of questions that I was going to ask but now you've already answered most of it and I need to look into this again to see how far I get this time.

The only thing that's different between a normal kiwi build and openSUSE:Factory:Live is that the package lists change so often with factory. So I have a process that calculates a package list for GNOME and KDE (and the DVDs and addons). That process commits a plain text file in e.g. package-lists-gnome.i586. That creates a package named package-lists-openSUSE-GNOME-cd that will require all those packages.

These requires then make up most of the buildrequires of kiwi-image-livecd-gnome.i586. This package will then create a local repo of the buildrequires and then call kiwi.

After that happens some preparations for the profiling, but that's not the part that usually fails. But for completness: the package built from kiwi-image-livecd-gnome.i586 is downloaded and run in a kvm to create a clicfs profile. That again is commited into preload-lists-gnome-i586 and the preload list and the original kiwi image will then be profiled in a 3rd package called kiwi-profiled-livecd-gnome.i586. Out of this the final ISO drops.

To get it on download.opensuse.org though we need a FTP product, which then again lives in openSUSE:Factory and is generated from _product and is called _product:openSUSE-ftp-livetree-gnome-i586. But that is just a wrapper product to give the resulting ISO the final file name including build number for factory.

Leaving out the profiling would this make quite a bit simpler, but I considered a big advantage - and as I said: normally it's not the problem. The problems are *way* more often problems you would get with plain kiwi too. Factory is just moving too fast for kiwi. UsrMerge was the latest example.

Thanks, that is very useful information. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 14.05.2012 00:33, Larry Finger wrote:

On 05/13/2012 01:14 PM, Stephan Kulow wrote:

...

Am 12.05.2012 08:48, schrieb doiggl@velocitynet.com.au:

...

Hello, Some questions: - Why are builds not at the same level and build date? [1] Because they do not build.

...

- Can the KDE-LiveCD-x86_64 be fixed so its at the same level and date as the NET iso build ? Someone needs to fix them build and then this will be the case. But as the only one who cares for this is me, it only gets very little attention. And with so little interest the live cds get, I consider dropping them alltogether.

...

- Which project builds the KDE-LiveCD-x86_64 iso's ? openSUSE:Factory builds all isos and FTP trees.

...

- Have you a link to it please ? http://s.kulow.org/images is what I have as bootmark.

Greetings, Stephan

I think the Live CDs should be preserved. They are a great resource for testing an unknown system to see how much trouble there will be with the hardware. They are also the fastest way to install a working system.

I feel strongly enough that I am volunteering to help with fixing those builds. Please send me details on what I should do next.

Hi Larry, There are many things to do, but the biggest problem is to keep an eye on https://build.opensuse.org/project/monitor?project=openSUSE%3AFactory:Live You will need to get used to parse kiwi log files to learn that e.g. right now zypper crashes. Here we need to reproduce the issue locally (you need to osc build --userootforbuild) and then chroot into it and debug the issue. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/14/2012 03:34 AM, Stephan Kulow wrote:

...

There are many things to do, but the biggest problem is to keep an eye on https://build.opensuse.org/project/monitor?project=openSUSE%3AFactory:Live

You will need to get used to parse kiwi log files to learn that e.g. right now zypper crashes. Here we need to reproduce the issue locally (you need to osc build --userootforbuild) and then chroot into it and debug the issue.

I got started and I thought I set up a user project correctly; however, when I start a build, the message "nothing provides package-lists-openSUSE-GNOME-cd" appears. Could someone point me to a resource that explains how to overcome this problem? It would have been great if you listed what you did exactly. You would do only osc co openSUSE:Factory:Live kiwi-image-livecd-gnome; cd ki*gnome; osc build --usebuildforroot (that

Am 14.05.2012 21:04, schrieb Larry Finger: option I always grep out of --help, so it's most likely misspelled :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 16.05.2012 12:58, doiggl@velocitynet.com.au wrote:

Hello, Is the build iso process broken because: - a) Kiwi broken. or - b) is the iso image too big.

c) because of other problems. openSUSE-images is too big because glibc-devel is required for xorg-x11, this should be fixed already, but needs to end in factory first. The live cds are broken because they fail. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 16.05.2012 17:41, doiggl@velocitynet.com.au wrote:

Hello, I thought LiveCDs creation could be bigger because for example, - openSUSE-12.1-KDE-LiveCD-x86_64.iso 12-Nov-2011 19:56 674M

is greater than the following test. + size=502772 + test 502772 -gt 500000 + echo 'this looks unreasonable' this looks unreasonable + exit 1

openSUSE-images are not live cds and have different limits. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, May 16, 2012 at 1:11 PM, Larry Finger wrote:

I am still trying to find what sets the size of /dev/loop0. If anyone can give me some pointers, I would appreciate the help.

The file it was made to point to with losetup? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 16.05.2012 18:11, Larry Finger wrote:

/dev/loop0 2485632 2485632 0 100% /mnt

The bulk of the space is in /mnt/usr (2078212) with that split into bin (280976), lib (280976), lib64 (621648), and share (866636).

I am still trying to find what sets the size of /dev/loop0. If anyone can give me some pointers, I would appreciate the help.

Hi Larry, Now starts the interesting part: debugging kiwi :) The /mnt is full because the resizing didn't work before that, to debug this further I start qemu-kvm with -serial stdio and then use cat /var/log/boot.kiwi > /dev/ttyS0 to get the debug log into an environment with more text viewers. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 21.05.2012 19:58, schrieb Larry Finger:

On 05/21/2012 02:28 AM, Stephan Kulow wrote:

...

On 16.05.2012 18:11, Larry Finger wrote:

...

/dev/loop0 2485632 2485632 0 100% /mnt

The bulk of the space is in /mnt/usr (2078212) with that split into bin (280976), lib (280976), lib64 (621648), and share (866636).

I am still trying to find what sets the size of /dev/loop0. If anyone can give me some pointers, I would appreciate the help.

Hi Larry,

Now starts the interesting part: debugging kiwi :)

The /mnt is full because the resizing didn't work before that, to debug this further I start qemu-kvm with -serial stdio and then use cat /var/log/boot.kiwi> /dev/ttyS0 to get the debug log into an environment with more text viewers.

Coolo,

Thanks for the suggestion. I was wondering how to get a better viewer. I did not find 'cat' and 'grep' to be that much help. That's why I told you how I do it - I use cat to dump it into the serial console and then I can use the host system's eclipse to view the file.

Today, both Gnome and KDE Live CD builds fail with the following:

buildinfo is broken... it says: unresolvable: nothing provides PackageKit = 0.7.3 needed by PackageKit-branding-openSUSE

That's temporary - but if you find the issue with yesterday's live cd, it will still apply I'm pretty sure. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/22/2012 04:45 AM, Stephan Kulow wrote:

Hi,

OK, I did the digging myself and there are 2 kiwi bugs:

+ tune2fs -m 0 /read-only/fsdata.ext3 tune2fs: error while loading shared libraries: libext2fs.so.2: cannot open shared object file: No such file or directory

and

+ /sbin/reboot -f -i /include: line 283: /sbin/reboot: No such file or directory

Both are kiwi bugs - most likely due to /usr merge. Kind of puzzling because the libext2fs one should have been fixed already ;(

Thanks for finding these. I'm still having trouble getting /var/log/boot.kiwi into an environment where I can work with it. I did learn how to get qemu-kvm to switch to the kiwi debug console where a minimal shell is available, but none of my attempts to get the log file transferred back to the host have worked. I first used the '-serial stdio' method that you listed, then I tried a direct file, and finally a netcat socket. No success with any of them. I will keep on trying, but if someone has the magic trick, I would appreciate it. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/23/2012 03:31 AM, Andreas Jaeger wrote:

On 05/22/2012 08:32 PM, Larry Finger wrote:

...

On 05/22/2012 04:45 AM, Stephan Kulow wrote:

...

Hi,

OK, I did the digging myself and there are 2 kiwi bugs:

+ tune2fs -m 0 /read-only/fsdata.ext3 tune2fs: error while loading shared libraries: libext2fs.so.2: cannot open shared object file: No such file or directory

and

+ /sbin/reboot -f -i /include: line 283: /sbin/reboot: No such file or directory

Both are kiwi bugs - most likely due to /usr merge. Kind of puzzling because the libext2fs one should have been fixed already ;(

Thanks for finding these. I'm still having trouble getting /var/log/boot.kiwi into an environment where I can work with it. I did learn how to get qemu-kvm to switch to the kiwi debug console where a minimal shell is available, but none of my attempts to get the log file transferred back to the host have worked. I first used the '-serial stdio' method that you listed, then I tried a direct file, and finally a netcat socket. No success with any of them.

I will keep on trying, but if someone has the magic trick, I would appreciate it.

I suggest that somebody documents this in the wiki for the next time we hit this,

I added a new Q (#21) to the FAQ at http://en.opensuse.org/Portal:KIWI. I'll check in a few days to see if Google has indexed it. Any suggestions on wording changes? Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 22.05.2012 21:29, schrieb Larry Finger:

There is one other error in kiwi that I just found:

+ resize2fs /read-only/fsdata.ext3 4916992s resize2fs: error while loading shared libraries: libe2p.so.2: cannot open shared object file: No such file or directory

Both should be fixed in the latest kiwi - Marcus tested it this time :) Unfortunately with the OBS problems we see, it will take some time before we can actually verify.

I still do not see the contents of /var/log/boot.kiwi outside qemu-kvm, but I used your example above to search for "error" in the logfile.

What I did to gather it, was doing this: qemu-kvm -cdrom livecd.iso -serial stdio boot with kiwidebug=1 then I went to alt-f2 and called mount -t devtmpfs /dev /dev cat /var/log/boot.kiwi > /dev/ttyS0 Of course I type these commands now from memory, but I hope if I did a mistake, it's easy to spot for you :) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Larry Finger [05-21-12 13:58]:

Today, both Gnome and KDE Live CD builds fail with the following:

buildinfo is broken... it says: unresolvable: nothing provides PackageKit = 0.7.3 needed by PackageKit-branding-openSUSE

In my experience most remove PackageKit as it's functionality is quite suspect. Why don't you remove the requirements for PackageKit-branding-opensuse? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Stephan Kulow [05-21-12 14:09]:

Am 21.05.2012 20:06, schrieb Patrick Shanahan:

...

* Larry Finger [05-21-12 13:58]:

...

Today, both Gnome and KDE Live CD builds fail with the following:

buildinfo is broken... it says: unresolvable: nothing provides PackageKit = 0.7.3 needed by PackageKit-branding-openSUSE

In my experience most remove PackageKit as it's functionality is quite What kind of experience is that? Can you please explain?

notifications which are not applicable, mostly patches not respecting locks I removed it in favor of cl/zypper quite a while ago and have not missed it. Of course I would have missed any changes or improvements to it's function. I perform manual updates often enough to not miss anything I would gain from it's notices. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Stephan Kulow [05-21-12 14:22]:

OK, but you are not most - you said in your experience most remove it and I would like to learn where you found out what most do. It really can gain us a lot if we know what most users do.

Sorry for mis-leading. It was feeling I got from discussion on opensuse list....., especially after I had removed it soon after first installing 12.1/tumbleweed. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 05/21/12 14:19, Stephan Kulow pecked at the keyboard and wrote:

Am 21.05.2012 20:14, schrieb Patrick Shanahan:

...

* Stephan Kulow [05-21-12 14:09]:

...

Am 21.05.2012 20:06, schrieb Patrick Shanahan:

...

* Larry Finger [05-21-12 13:58]:

...

Today, both Gnome and KDE Live CD builds fail with the following:

buildinfo is broken... it says: unresolvable: nothing provides PackageKit = 0.7.3 needed by PackageKit-branding-openSUSE

In my experience most remove PackageKit as it's functionality is quite What kind of experience is that? Can you please explain?

notifications which are not applicable, mostly patches not respecting locks

I removed it in favor of cl/zypper quite a while ago and have not missed it. Of course I would have missed any changes or improvements to it's

OK, but you are not most - you said in your experience most remove it and I would like to learn where you found out what most do. It really can gain us a lot if we know what most users do.

Greetings, Stephan

I remove it as it hinders the times *_I_* want to use zypper or YaST to install/remove a program. It doesn't play nice and refuses to shutdown when asked by zypper/YaST. Repeat... It doesn't respect locks you put on packages and installs/upgrades them anyway. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 22 May 2012 10:13:00 +0200 Stephan Kulow wrote:

On 21.05.2012 21:13, Ken Schneider - openSUSE wrote:

...

I remove it as it hinders the times *_I_* want to use zypper or YaST to install/remove a program. It doesn't play nice and refuses to shutdown when asked by zypper/YaST.

Repeat... It doesn't respect locks you put on packages and installs/upgrades them anyway.

OK, let us raise the priority of your bug report. Your attached zypp and PackageKit logs should be helpful.

Greetings, Stephan

The trouble with packagekit not shutting down appears to have been fixed in 12.2 M3. -- Graham Davis, Bracknell, Berks. openSUSE 12.1 (64-bit); KDE 4.8.3; AMD Phenom II X2 550 Processor; Video: nVidia GeForce 210 (using nVidia driver); Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org