http://bugzilla.suse.com/show_bug.cgi?id=900558http://bugzilla.suse.com/show_bug.cgi?id=900558#c20
--- Comment #20 from Dr. Werner Fink <werner(a)suse.com> ---
(In reply to Dr. Werner Fink from comment #19)
To be exact, the boot parameter rd.break=pre-mount is for dracut. No idea if
this exists in the initrd done by mkinitrd.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=900558http://bugzilla.suse.com/show_bug.cgi?id=900558#c19
--- Comment #19 from Dr. Werner Fink <werner(a)suse.com> ---
(In reply to Olaf Hering from comment #17)
And we are patching and patching instead to explain that e.g. the boot
parameter
rd.break=pre-mount
would drop into a shell before accession the root file system. Repairing the
main root partition should happn in the initrd before switching over into
single user mode before chroot on that root partition.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=900558http://bugzilla.suse.com/show_bug.cgi?id=900558#c17
--- Comment #17 from Olaf Hering <ohering(a)suse.com> ---
Its the fault of grub developers to force everyone to mount root read-only. A
bootloader has simply no business to force kernel command line options on
anyone.
We patch that upstream failure out of our grub2 package. Looks like we have to
patch it out of our systemd package as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=936463http://bugzilla.novell.com/show_bug.cgi?id=936463#c14
--- Comment #14 from Richard Biener <rguenther(a)suse.com> ---
(In reply to Stanislav Brabec from comment #13)
> Created attachment 639727 [details]
> Proposed fix for 2)
>
> I have an easy fix for 2)
>
> However I have a problem:
>
> It compiled libgcc.a and others several hours ago. But now sources in
> Factory are newer than compiler there, and it does not compile. I am not
> sure, whether it is a temporary rebuild problem. Let's see tomorrow.
>
> https://build.opensuse.org/project/monitor/home:sbrabec:branches:devel:gcc
This generally doesn't work as most targets need glibc headers to build
target libraries and using the glibc headers from the host is wrong here
(thus for avr you'd need to BuildRequire avr-libc which should install
into the avr sysroot).
the %gcc_icecream 1 path is especially meant to not build target libraries
but only host binaries - those binaries now also get packaged as cross-*-gcc5
for easy access as requested by kernel developers who do _not_ need target
libraries.
Andreas did some preliminary work to build real cross-compilers for the
non %gcc_icecream path. Thus as a first step to build target libraries for
avr you'd need to change change_spec like
Index: change_spec
===================================================================
--- change_spec (revision 64)
+++ change_spec (working copy)
@@ -133,7 +133,7 @@
add_cross cross-aarch64-gcc$base_ver aarch64 aarch64-suse-linux %define
gcc_icecream 1
add_cross cross-armv6hl-gcc$base_ver armv6hl armv6hl-suse-linux-gnueabi
%define gcc_icecream 1
add_cross cross-armv7hl-gcc$base_ver armv7hl armv7hl-suse-linux-gnueabi
%define gcc_icecream 1
-add_cross cross-avr-gcc$base_ver avr avr-suse-linux %define gcc_icecream 1
+add_cross cross-avr-gcc$base_ver avr avr
add_cross cross-i386-gcc$base_ver i386 i586-suse-linux %define gcc_icecream 1
add_cross cross-x86_64-gcc$base_ver x86_64 x86_64-suse-linux %define
gcc_icecream 1
add_cross cross-s390-gcc$base_ver s390 s390-suse-linux %define gcc_icecream 1
thus drop the gcc_icecream define for avr. You'll then run into
make %{?jobs:-j%jobs}
which might or might not succeed. You also get a proper sysroot defined
automagically (you have to double-check whether that agrees with the
binutils one)
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=934214http://bugzilla.opensuse.org/show_bug.cgi?id=934214#c6
Dominique Leuenberger <dimstar(a)opensuse.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #6 from Dominique Leuenberger <dimstar(a)opensuse.org> ---
gio does indeed depend on dbus-launch.. pinentry, the issue at hand, has been
corrected to not do UI stuff to store the keys
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=914370
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|obs:running:3880:moderate |obs:running:3880:important
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=931401
Bug ID: 931401
Summary: Request to add upstream kdesvn patch to openSUSE 13.2
Classification: openSUSE
Product: openSUSE Distribution
Version: 13.2
Hardware: x86-64
OS: openSUSE 13.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Applications
Assignee: kde-maintainers(a)suse.de
Reporter: mmarinchenko(a)yahoo.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Upstream bug reports (fixed):
https://bugs.kde.org/show_bug.cgi?id=325074https://bugs.kde.org/show_bug.cgi?id=330624
--
You are receiving this mail because:
You are on the CC list for the bug.