Hi,
during our Hackweek at SUSE I spent a day or two to improve my tool to
help finding the maintainer for software in Factory, which comes in
handy for bugzilla-screening (getting bugs to the right people).
You can use the tool at
http://maintainer.zq1.de/
You can give it command names, full filepath, or package names
(exact matches (including case) only)
If you want to run or extend it,
the code is all open on https://github.com/bmwiedemann/susepkginfo
and the databases can be fetched from http://aw.zq1.de/db.suse/
The actual maintainer information comes from OBS, so is always current.
Ciao
Bernhard M.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
> 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,
I was told on the opensuse(a)opensuse.org list to post this here.
Debian GNU/Linux has a program called Mandos, which allows computers with encrypted root filesystem to boot unattended as long as they are in the same LAN segment as the mandos server. If someone steals the computer or copies the storage of an ecrypted VM then they'll still have to enter the password on boot.
It needs to install its client in the initrd of the encrypted machine, which is why it only works on Debian GNU/Linux for now.
I feel like it would be a great addition to openSUSE GNU/Linux, but it needs a lot of changes in the boot process in order to work.
More info about Mandos: https://wiki.recompile.se/wiki/Mandos
Regards,
mots
Hi,
we are currently trying to get openSUSE:Factory:Rings:0-Bootstrap and
openSUSE:Factory:Rings:1-MinimalX clean to build with GCC 5 in the
openSUSE:Factory:Staging:Gcc49 project. Once that works reasonably
I will push GCC 5 to Factory without enabling it as a default - that
will be done when it works fully (help appreciated at that point).
There is a porting-to document that explains some issues you may run
into (also consider the 4.9 variant as we didn't transition to that):
https://gcc.gnu.org/gcc-5/porting_to.htmlhttps://gcc.gnu.org/gcc-4.9/porting_to.html
You may also find the analysis of Fedora interesting which explains
why some packages now fail to build:
https://lists.fedoraproject.org/pipermail/devel/2015-February/207549.html
GCC 5 packages can be installed from devel:gcc where they are regularly
updated. Those sources also feed openSUSE:Factory:Staging:Gcc49.
Richard.
--
Richard Biener <rguenther(a)suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Jennifer Guild,
Dilip Upmanyu, Graham Norton HRB 21284 (AG Nuernberg)
--
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
Hello people,
I am going to clean up the mess we have in Java namespace by removing all the
experimental subprojects which were not updated.
As most of this will just delete packages that fail to build or are broken one
way or other it should be no biggie, but still scream now if you think it will
ruin your mojo :-)
The current setup:
base Base Java platform for SUSE
base:maven2
base:scratch Scratch
esmska Packages for esmska
Factory Devel project of Java packages for openSUSE:Factory
jpackage-1.7 JPackage 1.7 packages
jpackage-5.0 Jpackage 5.0
jpackage-5.0:bootstrap jpackage-5.0 bootstrap
jpackage-6.0 Jpackage 6.0 development
jpackage-6.0:bootstrap jpackage-6.0 bootstrap
packages Factory Java packages
packages:maven Maven testing playground
After cleanup:
esmska Packages for esmska
Factory Devel project of Java packages for openSUSE:Factory
packages Factory Java packages
packages:maven Maven testing playground
I will do this removal next monday unless I get decent reason why I should not
as I already announced this once beforehand.
Cheers
Tom
Hi,
The "build all binaries with PIE" has been proceeding slowly.
- gcc-PIE package is in Tumbleweed, after installing it PIE is default.
- making it default will be done via Requires in the "rpm-build" subpackage of rpm.
https://build.opensuse.org/project/show/openSUSE:Factory:Staging:PIE
is tracking build.
- kmod: bug was exposed by PIE building, fix submitted and upstream.
- cmake: the newer "file" in Factory broke "PIE binary" detection in cmake.
SRed to devel project and mailed upstream
- various package using assembler that uses %EBX (PIC register for x86).
Common pattern seems to be inline "cpuid" assembler, as CPUID reports
some flags in %EBX.
I fixed one or two, for others building without PIE is probably better
(syslinux and memtest86+)
- kernel does not build (just does not like PIC building)
- gcc48 does not build (not debugged yet)
Ciao, Marcus
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
I'm considering trying OpeSuse, is (/when it will be) Plasma 5
default(?)-Desktop?
Regards,
Tatu
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org