> No, please don't confuse people, if you add more repos than just
> Tumbleweed you really had better know what you are doing or bad things
> can, and will, happen :)
I understand.
I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed -
between ## is the new stuff:
"The only supported method of repo use for Tumbleweed is to have only the main repos
(Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more
repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT
support this ## "
It would also be good to move this information to "Special concerns" and to move the
whole "Special concerns"-section up. For example
"Special Concerns
Virtual Machines ...
Third Party Drivers ...
## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the
Tumbleweed-Standard repo. Everything else is not supported and might break the system ## "
>You do know the legal reasons behind why packman is
there, right?
Yes. Then I do not whish you personaly to support Packman with TW - I understand now
that this is not possible from your perspectivg. But...as the OS community discusses
right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be
supported BY Packman. So I will ask the Packman-guys to do that... I hope this is
possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;)
thanks anyway :D
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello.
Recently updated my Factory running workstation (x86_64, Xfce).
Monospace font interval is increased badly.
I'm sure, I use DejaVu Sans Mono as a monospace font.
I choose 'monospace 9' in programs settings.
There is a screenshot: http://susepaste.org/view/simple/38919191
Changing to 'DejaVu Sans Mono 9':
http://susepaste.org/view/simple/70371539
It looks like it was before.
% fc-match Monospace
Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 14: reading
configurations from ~/.fonts.conf is deprecated. please move it
to /home/kent/.config/fontconfig/fonts.conf manually Monospace:
"Monospace" "Regular"
--
WBR
Kyrill
Export button is greyed out no matter what.
--
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 everyone,
is there any reason (other than "lack of time" or "no one did it", why
there is no package for bind's latest version 9.10 on the OBS (except
for one arch package)?
I had a look at the spec and suddenly decided, that I lack the skills
to update the package. Too many patches doing whatever it is, etc.
9.10 has some features, that would come in handy, so I would
appreciate if someone had time to update (or guide me through
updating...).
Thanks in advance.
Regards,
Johannes
- --
I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.
(Linus Torvalds)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlPaZ9UACgkQzi3gQ/xETbKeYwCeLzq6umhcepTr8yoID64hmjdn
GnQAnio6XDDvbvJ6eExyg0rG49aWeVNJ
=VPXk
-----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
Hi List Mates,
Just a very early warning with regards to the latest released systemd version
(version 210). In the release notes the following two items will have an
effect on people that are utilizing laptops with a docking station and an
external monitor.
* logind is now a lot more aggressive when suspending the
machine due to a closed laptop lid. Instead of acting only
on the lid close action it will continuously watch the lid
status and act on it. This is useful for laptops where the
power button is on the outside of the chassis so that it can
be reached without opening the lid (such as the Lenovo
Yoga). On those machines logind will now immediately
re-suspend the machine if the power button has been
accidentally pressed while the laptop was suspended and in a
backpack or similar.
* logind will now watch SW_DOCK switches and inhibit reaction
to the lid switch if it is pressed. This means that logind
will not suspend the machine anymore if the lid is closed
and the systemd is docked, if the laptop supports SW_DOCK
notifications via the input layer. Note that ACPI docking
stations do not generate this currently. Also note that this
logic is usually not fully sufficient and Desktop
Environments should take a lid switch inhibitor lock when an
external display is connected, as systemd will not watch
this on its own.
The first item concerns a change that systemd is monitoring if the lid is
closed or not. This monitoring starts already during the system boot process
which would lead to the effect that the system is forced into suspend mode
even before the login manager is reached. To prevent this, the second item was
implemented, however as indicated current kernels (including the latest 3.14-
rc4) do not support this yet for all laptops. The issue however is that the
system will not reach the Desktop Environment yet as that this new principle
already kicks in during the boot process. So implementing a lid switch
inhibitor in GNOME/KDE/etc does not make any sense as that the system will
never reach the desktop environment.
I had a couple of email conversations with Lennart about this topic yesterday
and finally with my last message he got the real issue that this happens
during system boot and therefore systemd should handle this properly. He
indicated that he will resolve the issue in one of the upcoming versions of
systemd and also probably move the external monitor detection out of
the DEs into logind. (The situation will then be that if the lid is closed and
an external monitor is connected, then systemd will not suspend the system).
If the decision is taken by the systemd maintainers, then in my opinion it
would be good to revert the two commits in systemd version 210 that implement
the two items mentioned so that the old lid switch behavior is restored.
Regards
Raymond
--
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 everyone,
while updating lxc to the latest version I came across one question:
Is there any particular reason, why the virtualization-project
(https://build.opensuse.org/project/show/Virtualization) is not built
against/for tumbleweed? If not, could one of the maintainers please
correct that?
Regards,
Johannes
- --
You know the world is going crazy when the best rapper is a white guy,
the best golfer is a black guy, the Swiss hold the America's Cup,
France is accusing the US of arrogance, and Germany doesn't want to go
to war. (aus alt.jokes)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/
iEYEARECAAYFAlMh+nYACgkQzi3gQ/xETbKLxwCfajUC5ZU1bCAghqGNY1u5eOyO
GFsAn3njjuzTONetwWTIaNAdNVVA0gSP
=RhDV
-----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
Good afternoon!
I've written and packaged a compatibility library for flash to enable
playback of DRM content (this removes the dependency on the HAL
package). I'd like to know what steps I can take to have the package
considered for inclusion in openSUSE 12.3 and 13.1. Can I submit the
package to devel:openSUSE:Factory, or is there another action I should
be taking?
Details of the bug and links to upstream are here (please briefly review):
https://bugzilla.novell.com/show_bug.cgi?id=768562#c19
OBS location:
https://build.opensuse.org/package/show?package=hal-flash&project=home%3Ach…
I will maintain the package until such time that HTML5 Video content
is a viable alternative or the Flash plugin is completely withdrawn.
RPMs, debs... are all available on the build service.
Three noteworthy points:
- package naming (libhal1-flash) doesn't 100% align with the Shared
Library Policy (I've suffixed -flash to make clear this is not a fully
functional HAL layer and also to avoid naming conflicts as some
distros seem to have a shared library package already named libhal1).
- The packages depends on dbus and udisks. It seems to work find when
udisks is launched on demand (as for openSUSE 12.3)
- The flash-player package could have some kind of RPM dependency on
this package to assist the user when looking in YaST (Install / Remove
Software) / Package Manager.
Chris
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org