Hi all,
The release team made openSUSE 13.1 RC2 available - help us test it, as we're
close to release! See https://news.opensuse.org/?p=16786 for some idea of
what's new and what needs extra attention: the live images, secure boot and
of course btrfs.
It's all over our mirrors, see software.opensuse.org/developer and get it.
/J
In case anyone is interested: http://xiphmont.livejournal.com/61927.html
The short of it is, Cisco is making H.264 available at no cost to
anyone who wants to use it. It is a legal way (a hack, but legal) to
include/distribute H.264.
Mozilla is including it in Firefox. Quoting: These modules will be
usable by downstream distributions of Firefox, as well as by any other
project." (source:
https://blog.mozilla.org/blog/2013/10/30/video-interoperability-on-the-web-…
)
How does that affect openSUSE? Does this mean a possible change to
openSUSE's use/inclusion/availability of H.264 (currently H.264 is
included in the Fluendo package)?
C.
--
openSUSE 12.3 x86_64, KDE 4.11
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
All,
Do we have any idea how big the "zypper up" will be from 13.1 RC2 to
13.1 general release?
== why I ask ==
I have a friend that wants to try out Linux for the first time. I
don't want to wait for 13.1 Gold (which is a couple weeks away).
I'm thinking of loading 13.1 RC2 on his system. I can download the
DVD and burn it easily enough.
Trouble is he has a low bandwidth connection so if there is going to
be a GB or more of upgrades from RC2 to Gold, I need to figure out a
different solution.
Thanks
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Just tried to build (using configure) a package
that failed in the gcc test.
Seems like the graphite loop optimizer is missing. The
manpage infers that the wrong build options were used.(?)
(was present in earlier versions).
The error was:
conftest.c:1:0: sorry, unimplemented: Graphite loop optimizations cannot be used
(-fgraphite, -fgraphite-identity, -floop-block, -floop-interchange,
-floop-strip-mine, -floop-parallelize-all, and -ftree-loop-linear)
/* confdefs.h */
The manpage says this about the loop optimizer:
To use this code transformation, GCC has to be
configured with --with-ppl and --with-cloog to enable the Graphite
loop transformation infrastructure.
gcc-4.8-1.3.x86_64.rpm dated Aug 5
rpm -V gcc verifies it as integrous. (yeah, it's a valid word)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi all,
I've just ran across an issue with Bluetooth in openSUSE 13.1; mainly,
the GNOME Stack does not work with BlueZ 4.x anymore.
There are several components that have been ported to Bluez 5 already;
and, as most of the stuff is not relying on the library (as this has
been marked obsolete by upstream anyway), not much was seen prior to
actually finding a BT device to pair it.
The D-Bus APi changed and, as a result, stuff relying on it simply has a
50% chance to work or not work.
To make matters worse, we can't even just 'parallel install' bluez and
bluez5, as the DBus services clash (same name space).
So, we have the hard bullet to bite: either we update (Fedora decided to
do so, see
https://lists.fedoraproject.org/pipermail/devel/2013-August/187738.html
for reference) or we accept to have a non-working BT stack in GNOME.
Updating it would likely still leave a few breakages here and there; but
KDE's BlueDevil for example does have support in git.
The 2nd alternative would be to 'try to undo' the Bluez 5 porting in the
GNOME Stack; No idea if and how well this will work; we would be the
only distro with GNOME 3.10 running on Bluez 4.
Any opinions around here?
--
Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
can one of the factory maintainers please approve deleterequest
203778 for pdksh? It's been sitting there for 11 days and I have
some followup changes. Thanks.
--
Guido Berhoerster
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
(its finished now)
Hi Folks,
I finally have a chance to work on my previously reported
issue with btrfs where I can't write more than about 15-TB
to a single partition.
Here's the machine:
Supermicro X9DRH mobo
2-ea Xeon E5-2643
64-GB RAM
1-ea LSI MegaRAID SAS 2208 RAID controller
2-ea SSD 120-GB drives configured as RAID-1 mirror
24-ea 2-TB SATA drives configured as two 11-disk RAID-6 arrays with 2-hotswaps
So I loaded 13.1 beta1 and pulled a "zipper dup". Here are
my initial observations.
1. No more reiserfs!
2. The installer complains about using XFS on the boot partition
3. The installer complains if the boot partition is less than 12-MB (good!)
But the installer won't let the install proceed past the final
summary screen if I have multiple system partitions. It complains
that there isn't enough room for the selected packages (default load).
There is room, but it complains nevertheless. Here's the error:
"Not enough disk space. Remove some packages in the Single Selection"
The screen said that 3.2-GB was required, but there was more than 50-GB
available.
I got around the error by just having one swap and one root partition.
I configured the root partition and one of the data arrays with btrfs. The
second data array was formatted as XFS.
The test uses dd to copy a 4-GB binary file in ~root on the SSD disk to
the btrfs array that contains 17576753152 1K-blocks as reported by df.
The copy is repeated 4,000 times. The process is then repeated for the
XFS array.
Failure:
The btrfs process failed when creating file #3688 when the file length truncated. But
it went on to create 6 more truncated files after the initial failure, as shown here:
-rw-r--r-- 1 root root 4194304000 Oct 15 23:37 test3686
-rw-r--r-- 1 root root 4194304000 Oct 15 23:37 test3687
-rw-r--r-- 1 root root 938475520 Oct 15 23:38 test3688
-rw-r--r-- 1 root root 41943040 Oct 15 23:38 test3689
-rw-r--r-- 1 root root 114294784 Oct 15 23:38 test3690
-rw-r--r-- 1 root root 2097152 Oct 15 23:38 test3691
-rw-r--r-- 1 root root 2097152 Oct 15 23:38 test3697
-rw-r--r-- 1 root root 2097152 Oct 15 23:38 test3703
-rw-r--r-- 1 root root 8388608 Oct 15 23:39 test3819
df shows this:
/dev/sdb1 17576753152 15140885368 2434798528 87% /export/data0
While dd reported:
dd: failed to open test3818: No space left on device
So this is a rather messy failure.
But the XFS formatted filesystem worked as expected.
/dev/sdc1 17574666240 16384034856 1190631384 94% /export/data1
Times for the two process are:
btrfs
real 365m4.381s
user 0m6.292s
sys 128m51.396s
XFS
real 282m6.769s
user 0m10.008s
sys 177m24.177s
Thus XFS seems to be faster by a fair margin, even when writing more data.
Regards,
Lew
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi all,
A reminder: if you have not added things to
https://en.opensuse.org/openSUSE:Major_features please do so!
And go over it to review what's there if you can.
Help your marketing team do great marketing!
Hugs,
J
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
I have updated a real HW (32bit) from 12.3 to 13.1 RC1 with zypper dup.
The upgrade was smooth.
Some observations though:
findutils-locate was replaced by mlocate.
users who want to use locate have to be added to the group "locate".
Probably this should be mentioned in the release notes.
The new database /var/lib/mlocate/mlocate.db
is only created when cron.daily is run.
The old database /var/lib/locatedb is not deleted during the upgrade.
BTW: the installed release notes still contain a lot of "CHECKIT:12.3".
This machine has a matrox video card which worked fine with the mga
driver in the previous openSUSE releases even when the performance got
worse and worse because of degrading support for this HW. With 13.1RC1
it seems there is no signal (or not acceptable for the display) although
the xserver starts and runs. I had to switch to the fbdev driver to get
graphics back.
On this system I can not reproduce
https://bugzilla.novell.com/show_bug.cgi?id=834898
while I still see this with 13.1 RC1 64bit in a virtual machine.
Regards,
Dieter
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
I did a test install of 12.3 using a DVD iso. I applied all available
patches for 12.3 and then upgraded using another DVD iso -
openSUSE-13.1-DVD-Build0041-x86_64.iso to be more precise.
During the installation I recall that I was asked for what to to with
the currently defined repos, and I left the default option - Remove.
After the installation, I was only left with the 'DVD' repo. That is
unexpected to me since the DVD installation properly set up the online
repos.
Is this expected behaviour of a bug to file?
Thanks,
Robert
--
http://robert.muntea.nu/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org