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
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
I've just installed nmap to test the ciphersuites offered by some
webservers and the RPM install failed with an illegal instruction. That
went away after several retries. When I now use nmpa I see sporadic
"Illegal instruction" failures right after starting nmap. Re-starting
the same command always succeeds.
model name : Intel(R) Xeon(R) CPU E3-1225 v3 @ 3.20GHz
stepping : 3
microcode : 0x1c
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
pbe syscall nx pdpe1gb rdtscp lm constant_tsc
arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64
monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr
pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm
abm ida arat epb pln pts dtherm tpr_shadow vnmi
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2
smep bmi2 erms invpcid xsaveopt
(BTW, ht is disabled for this CPU, even though it's reported that some
batch escaped with the HT feature not fused off).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Upgrade from 13.1 -> 13.2 removed support for traditional/stable if-up/if-down network control, replacing it with wicked.
In 13.2, wicked's currently badly broken; there are existing/critical issues, that prevent production use; those issues include, among mounting others, e.g.,
(1) tun
https://bugzilla.suse.com/show_bug.cgi?id=904903
(2) up/down script usage
https://bugzilla.suse.com/show_bug.cgi?id=907215
(3) ipv6
https://bugzilla.suse.com/show_bug.cgi?id=907694
Those issues need fixing, and are getting some attention already.
In current state, these network problems leave 13.2 unstable at best, unusable at worst.
In 13.1 all the aforementioned issues are not a problem -- everything was working.
IMO, disabling working if up/down prior to full-release-vetting of wicked et al is an operational mistake.
We'd prefer to stay with 13.2 .... but our available production solutions atm are
(1) downgrade 13.2 -> 13.1
(2) switch to a known/working other distribution (Redhat/Centos 7, e.g.)
(1) is messy and painful, and functionally regresses many of the OTHER solutions that modern/current 13.2 brings.
(2) is what we've done -- currently at all our production/edge boxes.
In lieu of immeidate fixes to 13.2, is it possible to reenable 'old' ifup/ifdown networking, disabling wicked, so we can get the distro back to working/production state? Or is wicked simply too wired-into 13.2?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
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
Hi,
Request for discussion: Should we offer firewalld as alternative/complement for SuSEfirewall2?
I think we should...
reasoning:
mobile users (laptops) who use NetworkManager / Wicked for managing their ip connectivity "in userspace" would want to be able to have multiple wifi setups that end up being in different zones.
I'm going to try to package the latest firewalld from fedora for openSUSE, and test it with 13.2.
Progress report will follow in due time.
cheers
MH
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org