Marcus Meissner schrieb:
> Some of you noticed that we have not yet released a new
> factory snapshot with bash fixes.
>
> This is due to the fact that Factory is not releasable
> currently, as the GNOME desktop would totally break and
> no longer work and the KDE desktop would break once.
>
> This has not been fixed for the last two weeks yet.
Here is my current openSUSE install
NAME=openSUSE
VERSION="20140924 (Harlequin)"
VERSION_ID="20140924"
PRETTY_NAME="openSUSE 20140924 (Harlequin) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:20140924"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"
I have tested both kde live iso and gnome live iso build 0015 on virtual
box and as usb on real hardware
with little or no problems.
The kde live usb wants a yes or nof on initial boot. sdx has a ext2
file system proceed anyway (y,n) y
the gnome live usb boots straight away but needs a alt ctl bacspace ic
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi!
This is the second time I've been told to use Base:System for get a
working systemd.
https://bugzilla.novell.com/show_bug.cgi?id=893797
Why is the stock systemd from openSUSE 13.1 not worth fixing?
Does every user have to use Base:System to get a sane system?
Sorry guys, I'm kind of pissed.
--
Thanks,
//richard
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
It is typical that after the system is installed, the installation media
is not used again. But unless you manually remove the installation media
repo, it is asked for when yast or zypper start, with errors like:
Empty destination in URI:
hd:///?device=/dev/disk/by-id/scsi-1SanDisk_Cruzer_Glide_.......-part2
That the cd/usb stick is not present is not crucial, as the same content
is available from the oss + non-oss default repos. So that particular repo
could be marked "optional" (or not, for people with slow Internet).
Also, when a repo or a URL fails, we could have another repo or URL as
failover.
Example 1.
I export the installation image via NFS on my local network. My laptop
could mount and use that while at home, or the usb stick if connected,
when not at home.
With a failover repo, zypper would try first the stick, if unavailable
failover to NFS, and if that were also missing, it could stop with a
message, as it does now, or skip if the whole is defined "optional".
Example 2.
On some cases, people have problems with the mirrors selected by the
Brain. We could in that case define a failover URL, instead of having to
manually edit the URLs and try again.
No, I don't know how to code all that... sorry. Just some ideas I throw
to the people that can :-))
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlQpSmwACgkQtTMYHG2NR9VYlACfX7yXBhmmXoKeWoaQYf1VjMIM
rjUAoJkXrZEMP849lDmIoXcu6dGxRLq9
=bzg9
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello List,
- in case of interest :
boinc-manager-7.2.42-1.3.x86_64
- does not function : impossible to Add Project [ SETI@Home ]
..................
regards
ellan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Current Factory uses XFS as default filesystem for /home partition.
Unfortunately I found easy way to damage filesystem on my laptop with data
loss (it is not delayed writing): suspend to ram + low battery level. And it
is reproducible.
Are there ideas for avoidance of this situation? Or maybe it's better to go
back to EXT4 as default, I don't remember similar for years.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Dear all,
today I have updated a workstation here in the office to the current beta version; everything works nicely after solving a few problems configuring the ldap/kerberos part and autofs (configured via LDAP); I could solve all problems - everything is documented in http://bugzilla.opensuse.org/show_bug.cgi?id=897955
Thank you to all who worked on it!
--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
As you might have heard, there is a pretty ugly security problem in bash.
Unfortunately I can't publish Factory as it's too unstable, so if
you run your system in the public, please grab bash from
http://download.opensuse.org/repositories/Base:/System/openSUSE_Factory/
We're still debugging the failures we see - as they do not appear in
staging projects, it's most likely some very bizzare problem.
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello List,
- what please is the Function of the Debug Repository as used by zypper ?
thanks,
regards
ellan
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org