gmane.linux.suse.opensuse.devel

More about the KDE Live CD

Larry Finger — 2012-05-26T19:32:51

I rebuilt the KDE Live CD again today as a lot of packages were changed. It 
seems that the OBS is working better; however, the latest Live CD in Factory is 
still from May 20. The new CD boots up as openSUSE 12.2 Milestone 4.

I have noticed a couple of other things. The initial boot screen no longer has 
an entry for direct installation. Is this intentional?

The initial boot screen also lists 12.1, not 12.2. I still do not know my way 
around the build materials, or I would submit a patch.

Larry

Cinnamon > Factory

Nelson Marques — 2012-05-26T17:37:49

I've submitted Cinnamon to Factory since the previous blockers are now
fixed except for the typelib(Meta-3.0), which I followed Vincents
advice and filtered out in the provides post-stream.

Further potential options like adding Cinnamon to YaST, advertising as
a feature or whatever I leave that to the community; regading this
packages (cinnamon and muffin) I'll do only bug triage, issue fixes
and keep it in good shape.

GNOME:Ayatana

Nelson Marques — 2012-05-26T17:32:37

I've got a request from 'damianator' for GNOME:Ayatana to join as
maintainer; He seems to want to continue my past efforts around Unity,
so I've accepted it and gave him full permissions on GNOME:Ayatana.

I suppose this is the best thing to do in the best interests of
openSUSE; Just reporting in case someone wants to help him out, since
I know from my own experience that this is really a huge task.

NM

build 383 use wrong branding

Bruno Friedmann — 2012-05-26T09:12:26

The new 383 doesn't contain the new branding like previous build 381,382
Why ?

Adjust openqa scripts to process ok prompts

2012-05-26T08:01:35

Hello,
Adjust openqa scripts to process ok prompts.

Examples:
http://openqa.opensuse.org/viewimg/openqa/testresults/openSUSE-DVD-x86_64-Build0378-11.2dup/timeout-04.png
http://openqa.opensuse.org/viewimg/openqa/testresults/openSUSE-DVD-x86_64-Build0378-11.2dup/welcome-1.png

Sourced from:
http://openqa.opensuse.org/results/openSUSE-DVD-x86_64-Build0378-11.2dup
Thanls Glenn

RPM 4.10 release

Ilya Chernykh — 2012-05-25T23:35:36

RPM 4.10 release: will it get to 12.2?

The Live CD iso report

Larry Finger — 2012-05-25T21:18:25

Coolo,

I can now report that the Gnome Live CD also builds and boots.

Both KDE and Gnome both will boot from a USB stick written with imagewriter; 
however, both fail when booted using the iso with qemu-kvm. At the point of 
failure, /var/lob/kiwi.boot shows the following:

===========================================================================

+ echo /dev/ram1
+ return
+ ramOnly=1
+ '[' 1 = 1 ']'
++ cat /proc/meminfo
++ cut -f1 -dk
++ grep MemFree
++ cut -f2 -d:
+ haveKByte='          405108 '
++ expr 405108 / 1024
+ haveMByte=
++ expr '*' 7 / 10
expr: syntax error
+ haveMByte=
+ clic_cmd='clicfs -m '
+ '[' '!' -z '' ']'
+ '[' -z /livecd/openSUSE-12.1-livecd-gnome-read-only.x86_64-2.8.0 ']'
+ clicfs -m /livecd/openSUSE-12.1-livecd-gnome-read-only.x86_64-2.8.0 /read-only
can't read from packfile
: Is a directory
read_pack: Invalid argument
+ Echo 'Failed to mount clic filesystem'
+ '[' 0 = 0 ']'
+ set +x
+ echo '[    9.208387] Failed to mount clic filesystem'
+ '[' 0 = 0 ']'
+ set +x
+ return 1
+ retval=1
+ '[' no = no ']'
+ '[' '!' clean = fine ']'
+ '[' 1 = 0 ']'
+ resetMountCounter
+ local curtype=auto
+ local command
+ FSTYPE=auto
+ IFS='
'
+ return 1
+ systemException 'Failed to mount root filesystem' reboot
+ set +x
+ echo '[    9.270200] Failed to mount root filesystem'

===========================================================================

At first, I thought the differences might be that the USB boot had used the swap 
partition on the real disk; however, when I boot using a VirtualBox VM and the 
iso file, it works whether the attached vdi has a swap partition or not. The 
problem is not due to too little memory in the qemu-kvm VM. It fails with the 
"-m 512" option. I think that should be enough.

The failure seems to start with a blank value for haveMByte.

I have noticed a couple of small bugs with the KDE image.

(1) When one does the media check, it asks for "any key" to continue. In fact, 
the key must be  "Enter".

(2) If one selects the "Boot from hard disk" option when using the USB stick, 
the system reboots from the stick. This situation may arise because the USB disk 
is first in the boot selection. It works correctly when running from the VB VM.

In any case, the Live CDs are a lot closer to release than they have been for a 
while.

Larry

Build disabled for devel packages [Publishing]?

Kyrill Detinov — 2012-05-25T21:02:15

Hello.

I found that some my devel packages are disabled for Factory in 
Publishing project.

Who and why… ?

And I see more disabled in Publishing:
https://build.opensuse.org/project/monitor?arch_i586=1&defaults=0&disabled=1&project=Publishing&repo_openSUSE_Factory=1

Boot failure with latest Live CD iso

Larry Finger — 2012-05-25T17:31:56

Coolo,

Good news.

After 'osc update' this morning, the KDE Live CD builds once again, *and* it 
boots. Thus far, I have run only limited tests, but they include connecting to a 
WPA2-TKIP(AES)-encrypted AP. Networking appears to be fine.

Are there any specific tests you would like me to run?

Larry

Latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my NAS

Daniel Bischof — 2012-05-25T12:34:18

Hi,

the latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my 
NAS (used to work flawlessly with 3.3.6 and before). Accessing the NAS 
with smbclient still works.

Bug?

/etc/fstab excerpt
---
//garcon/media /home/mediarw cifs nodfs,user,noauto,user=daniel,uid=daniel,gid=users,credentials=/home/daniel/.smbcredentials,iocharset=utf8,file_mode=0755,dir_mode=0755 0 0
---

verbose error messages in /var/log/messages
---
May 24 18:36:39 kernel: [ 5128.053888] /[...]/linux-3.4/fs/cifs/cifsfs.c: Devname: //garcon/Volume_1/ flags: 0 
May 24 18:36:39 kernel: [ 5128.053921] /[...]/linux-3.4/fs/cifs/connect.c: iocharset set to utf8
May 24 18:36:39 kernel: [ 5128.053940] /[...]/linux-3.4/fs/cifs/connect.c: Username: daniel
May 24 18:36:39 kernel: [ 5128.053944] /[...]/linux-3.4/fs/cifs/connect.c: file mode: 0x1ed  dir mode: 0x1ed
May 24 18:36:39 kernel: [ 5128.054003] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 12 with uid: 0
May 24 18:36:39 kernel: [ 5128.054006] /[...]/linux-3.4/fs/cifs/connect.c: UNC: \\garcon\Volume_1 ip: 192.168.42.13
May 24 18:36:39 kernel: [ 5128.054020] /[...]/linux-3.4/fs/cifs/connect.c: Socket created
May 24 18:36:39 kernel: [ 5128.054022] /[...]/linux-3.4/fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x1b58
May 24 18:36:39 kernel: [ 5128.054335] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_get_smb_ses as Xid: 13 with uid: 0
May 24 18:36:39 kernel: [ 5128.054347] /[...]/linux-3.4/fs/cifs/connect.c: Existing smb sess not found
May 24 18:36:39 kernel: [ 5128.054367] /[...]/linux-3.4/fs/cifs/cifssmb.c: secFlags 0x7
May 24 18:36:39 kernel: [ 5128.054381] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 114
May 24 18:36:39 kernel: [ 5128.054389] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 82
May 24 18:36:39 kernel: [ 5128.054428] /[...]/linux-3.4/fs/cifs/connect.c: Demultiplex PID: 3264
May 24 18:36:39 kernel: [ 5128.067828] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x67
May 24 18:36:39 kernel: [ 5128.067854] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=114 mid=1 state=4
May 24 18:36:39 kernel: [ 5128.067861] /[...]/linux-3.4/fs/cifs/cifssmb.c: Dialect: 2
May 24 18:36:39 kernel: [ 5128.067864] /[...]/linux-3.4/fs/cifs/cifssmb.c: negprot rc 0
May 24 18:36:39 kernel: [ 5128.067867] /[...]/linux-3.4/fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0x80f3fd TimeAdjust: -3600
May 24 18:36:39 kernel: [ 5128.067870] /[...]/linux-3.4/fs/cifs/sess.c: sess setup type 1
May 24 18:36:39 kernel: [ 5128.067893] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 115
May 24 18:36:39 kernel: [ 5128.067895] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 244
May 24 18:36:39 kernel: [ 5128.081018] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x68
May 24 18:36:39 kernel: [ 5128.081081] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=115 mid=2 state=4
May 24 18:36:39 kernel: [ 5128.081093] /[...]/linux-3.4/fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release
May 24 18:36:39 kernel: [ 5128.081103] /[...]/linux-3.4/fs/cifs/sess.c: UID = 100 
May 24 18:36:39 kernel: [ 5128.081110] /[...]/linux-3.4/fs/cifs/sess.c: bleft 62
May 24 18:36:39 kernel: [ 5128.081120] /[...]/linux-3.4/fs/cifs/sess.c: serverOS=Unix
May 24 18:36:39 kernel: [ 5128.081128] /[...]/linux-3.4/fs/cifs/sess.c: serverNOS=Samba 3.0.24
May 24 18:36:39 kernel: [ 5128.081136] /[...]/linux-3.4/fs/cifs/sess.c: serverDomain=MYWORKGROUP
May 24 18:36:39 kernel: [ 5128.081145] /[...]/linux-3.4/fs/cifs/sess.c: ssetup freeing small buf f2205e40
May 24 18:36:39 kernel: [ 5128.081153] /[...]/linux-3.4/fs/cifs/connect.c: CIFS Session Established successfully
May 24 18:36:39 kernel: [ 5128.081162] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_smb_ses (xid = 13) rc = 0
May 24 18:36:39 kernel: [ 5128.081174] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 14 with uid: 0
May 24 18:36:39 kernel: [ 5128.081186] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 117
May 24 18:36:39 kernel: [ 5128.081193] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 90
May 24 18:36:39 kernel: [ 5128.091411] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x36
May 24 18:36:39 kernel: [ 5128.091483] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4
May 24 18:36:39 kernel: [ 5128.091498] /[...]/linux-3.4/fs/cifs/connect.c: disk share connection
May 24 18:36:39 kernel: [ 5128.091509] /[...]/linux-3.4/fs/cifs/connect.c: nativeFileSystem=NTFS
May 24 18:36:39 kernel: [ 5128.091516] /[...]/linux-3.4/fs/cifs/connect.c: Tcon flags: 0x3 
May 24 18:36:39 kernel: [ 5128.091525] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 14) rc = 0
May 24 18:36:39 kernel: [ 5128.091532] /[...]/linux-3.4/fs/cifs/connect.c: CIFS Tcon rc = 0
May 24 18:36:39 kernel: [ 5128.091538] /[...]/linux-3.4/fs/cifs/connect.c: DFS disabled (1)
May 24 18:36:39 kernel: [ 5128.091545] /[...]/linux-3.4/fs/cifs/cifssmb.c: In QFSDeviceInfo
May 24 18:36:39 kernel: [ 5128.091555] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 50
May 24 18:36:39 kernel: [ 5128.091563] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 72
May 24 18:36:39 kernel: [ 5128.092535] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x40
May 24 18:36:39 kernel: [ 5128.092580] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=4 state=4
May 24 18:36:39 kernel: [ 5128.092596] /[...]/linux-3.4/fs/cifs/cifssmb.c: In QFSAttributeInfo
May 24 18:36:39 kernel: [ 5128.092607] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 50
May 24 18:36:39 kernel: [ 5128.092614] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 72
May 24 18:36:39 kernel: [ 5128.093353] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x4c
May 24 18:36:39 kernel: [ 5128.093389] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=5 state=4
May 24 18:36:39 kernel: [ 5128.093403] /[...]/linux-3.4/fs/cifs/connect.c: build_unc_path_to_root: full_path=\\garcon\Volume_1
May 24 18:36:39 kernel: [ 5128.093416] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 117
May 24 18:36:39 kernel: [ 5128.093423] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 96
May 24 18:36:39 kernel: [ 5128.094927] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x30
May 24 18:36:39 kernel: [ 5128.094998] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=6 state=4
May 24 18:36:39 kernel: [ 5128.095015] /[...]/linux-3.4/fs/cifs/connect.c: CIFS Tcon rc = 0 ipc_tid = 2
May 24 18:36:39 kernel: [ 5128.095024] /[...]/linux-3.4/fs/cifs/cifssmb.c: In GetDFSRefer the path \garcon\Volume_1
May 24 18:36:39 kernel: [ 5128.095038] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 50
May 24 18:36:39 kernel: [ 5128.095046] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 108
May 24 18:36:39 kernel: [ 5128.096086] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0xc8
May 24 18:36:39 kernel: [ 5128.096132] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=7 state=4
May 24 18:36:39 kernel: [ 5128.096149] /[...]/linux-3.4/fs/cifs/cifssmb.c: Decoding GetDFSRefer response BCC: 145  Offset 56
May 24 18:36:39 kernel: [ 5128.096166] /[...]/linux-3.4/fs/cifs/cifssmb.c: num_referrals: 1 dfs flags: 0x3 ...
May 24 18:36:39 kernel: [ 5128.096205] /[...]/linux-3.4/fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: resolved: garcon to 192.168.42.13
May 24 18:36:39 kernel: [ 5128.096319] /[...]/linux-3.4/fs/cifs/connect.c: iocharset set to utf8
May 24 18:36:39 kernel: [ 5128.096384] /[...]/linux-3.4/fs/cifs/connect.c: Username: daniel
May 24 18:36:39 kernel: [ 5128.096393] /[...]/linux-3.4/fs/cifs/connect.c: cifs_put_tcon: tc_count=1
May 24 18:36:39 kernel: [ 5128.096403] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_put_tcon as Xid: 15 with uid: 0
May 24 18:36:39 kernel: [ 5128.096410] /[...]/linux-3.4/fs/cifs/cifssmb.c: In tree disconnect
May 24 18:36:39 kernel: [ 5128.096421] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 113
May 24 18:36:39 kernel: [ 5128.096429] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 39
May 24 18:36:39 kernel: [ 5128.097409] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x23
May 24 18:36:39 kernel: [ 5128.097447] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=113 mid=8 state=4
May 24 18:36:39 kernel: [ 5128.097459] /[...]/linux-3.4/fs/cifs/connect.c: cifs_put_smb_ses: ses_count=1
May 24 18:36:39 kernel: [ 5128.097470] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_put_smb_ses as Xid: 16 with uid: 0
May 24 18:36:39 kernel: [ 5128.097478] /[...]/linux-3.4/fs/cifs/cifssmb.c: In SMBLogoff for session disconnect
May 24 18:36:39 kernel: [ 5128.097486] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 116
May 24 18:36:39 kernel: [ 5128.097493] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb:  total_len 43
May 24 18:36:39 kernel: [ 5128.098346] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x27
May 24 18:36:39 kernel: [ 5128.098381] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=116 mid=9 state=4
May 24 18:36:39 kernel: [ 5128.098408] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 12) rc = 0
May 24 18:36:39 kernel: [ 5128.098418] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 17 with uid: 0
May 24 18:36:39 kernel: [ 5128.098426] /[...]/linux-3.4/fs/cifs/connect.c: UNC: (null) ip: (null)
May 24 18:36:39 kernel: [ 5128.098432] CIFS VFS: Connecting to DFS root not implemented yet
May 24 18:36:39 kernel: [ 5128.098550] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 17) rc = -22
May 24 18:36:39 kernel: [ 5128.098559] CIFS VFS: cifs_mount failed w/return code = -22
---


Thanks,

--D.

OSOC: plymouth for kiwi

Stephan Kulow — 2012-05-25T07:52:02

Hi,

I just started a little project: the openSUSE Spring of Code.
It has many advantages over similiar projects, most prominently it's all
about honor and you don't have to care how to pay taxes on money.

And my first task to offer to the first promising candidate: plymouth
integration into kiwi (and installation-images). plymouth is integrated
into mkinitrd by now, but we have 2 other initrds that are worthy:

one is most likely easy: installation-images builds a pretty hard coded
list of files and packages to include and plymouth needs to replace
bootchart in there. Very similiar work to mkinitrd.

kiwi is a bit harder as it allows custom branding (e.g. for studio
integration) and as such builds bootsplash branding itself depending
on the branding, so plymouth integration is a bit more work.

Whoever picks the task: make sure to talk to snwint< at > and ms< at >suse.com

Greetings, Stephan

Nmap v6

James Knott — 2012-05-24T15:18:58

Any idea on when nmap 6 will be available on openSUSE?
http://www.itworldcanada.com/news/new-nmap-probes-ipv6-networks/145467?sub=146611&utm_source=146611&utm_medium=KC&utm_campaign=enews

tnx jk

Roles for security and convenience

Andreas Jaeger — 2012-05-24T09:25:08

Let's start a new thread to look a bit more at different roles.

I saw these two proposals:

Stefan Seyfried proposed a machine use case:

Hans Witvliet seems to suggest user roles:

I think that we need different settings for different users - even on the 
same machine. So, some kind of roles. I like the idea of having some 
configuration module for special purposes and also the idea of role-based 
administration - just fear it might be difficult to do.

So, my call for help again: Please give some proposals on what kind of 
roles/scenarios we want to offer - and be as precise on the different 
roles/scenarios as possible.

Andreas

Status: Beta

Stephan Kulow — 2012-05-24T04:31:21

Hi,

As we have no real estimate when the build service will be in a working
state again, I can't forecast when we will have the first builds to test 
either.

This is something that I did not expect - our servers really do
not like 12.2 to be released ;(

Greetings, Stephan

IPv6 support Yast Firewall

James Knott — 2012-05-23T15:38:20

With use of IPv6 increasing, would it be possible to get support for 
IPv6 added to Yast Firewall?  Also, I use a 6in4 tunnel to obtain IPv6 
and the 6in4 tunnel (tun-00) doesn't appear in Yast.  As that is how 
many currently obtain IPv6, support for that is important.

tnx jk

Midnight Commander needs maintainer?/maintenance!

Felix Miata — 2012-05-22T15:35:56

https://bugzilla.novell.com/buglist.cgi?query_format=advanced&emailassigned_to1=1&short_desc=mc%20midnight&field0-0-0=resolution&short_desc_type=anywordssubstr&email1=nadvornik%40suse.com&type0-0-0=notequals&value0-0-0=duplicate&classification=openSUSE&product=openSUSE%2011.4&product=openSUSE%2012.1&product=openSUSE%2012.2&emailtype1=exact 
shows 14 mc bugs against supported releases and Factory assigned to 
nadvornik, one of two "maintainers" listed by osc. 4 are marked fixed, and 
none of those show any activity by nadvornik.

dlovasko has no mc bugs against supported releases assigned, and is only 
associated to two mc bugs, though via bug comments it appears he is somehow 
related to two recent fixes.

So it appears mc needs maintainer (and version) maintenance. The current 
Factory version is 4.8.1.3, while the latest is 4.8.3, which will miss 
version cutoff if it isn't updated soon, if that milestone hasn't already passed.

Speeding up SRs process to devel projects

Togan Muftuoglu — 2012-05-22T14:43:12

Hi,

I have made SR# 115787 to Publishing for dblatex which is a version
update. However after almost a month it is still waiting for decision.

As the beta is coming in soon I am not sure if this package if approved
by the devel project will go to factory in a timely manner, but the real
problem is I do not thing I am the only one in this situation, so the
question what can be done in situations where the upstream ( in this
case the devel project or the package maintainer) is lagging in the
process of SR's

Togan

Security or Convenience? Defining a better policy

Andreas Jaeger — 2012-05-22T12:48:12

I just put the following on my blog as well (http://jaegerandi.blogspot.de) 
and look forward to your help defining a better policy:

The openSUSE security concepts have been changed gradually over the years
with new tools like PolicyKit, PolKit and its usage in system tools.

It's time now to step back, and review what we have and want.

Marcus and Ludwig from the SUSE security team and myself have
discusssed over the last weeks a bit and like to open this to a
broader round now to get your help defining what needs to be done.

= Challenges we face =

Administrating a system in a secure way is always balancing the needs
and requests of security, convenience and usability.  There's also the
additional challenge that upstream projects often have a different
view on either of these and therefore make different decisions and
influencing upstream projects is quite often a difficult task.

= Background =
Linus Torvalds in his Google+ rant
(https://plus.google.com/u/0/102150693225130002912/posts/1vyfmNCYpi5)

"I first spent weeks arguing on a bugzilla that the security policy of
requiring the root password for changing the timezone and adding a new
wireless network was moronic and wrong.

I think the wireless network thing finally did get fixed, but the
timezone never did - it still asks for the admin password.

And today Daniela calls me from school, because she can't add the
school printer without the admin password.

...
So here's a plea: if you have anything to do with security in a
distro, and think that my kids (replace "my kids" with "sales people
on the road" if you think your main customers are businesses) need to
have the root password to access some wireless network, or to be able
to print out a paper, or to change the date-and-time settings, ..."

= How to continue? =

We've collected a couple of use cases for the administration of a
local system at:
http://en.opensuse.org/openSUSE:Security_use_cases

For each use case we added a short security evaluation but in most
cases don't give a recommendation on what to do. 

Call for action: Review and discuss
http://en.opensuse.org/openSUSE:Security_use_cases using the following
questions:
* Are there any use cases missing?
* Is there any thing missing in the specific use cases?
* How can we solve these use cases so that a system is easy to setup
  for the most common usage scenarios?

Let's do the discussion on the opensuse-factory mailing list, I'll
update the document with any improvements. Feel free to enhance it as
well.

Andreas

worries about Mono repositories

Marguerite Su — 2012-05-22T12:25:07

Hi, list,

I'm a little bit worried about our Mono:* repositories...

it seems main packages in them haven't been updated since openSUSE 11.4.

and I watched Mono official page...still 11.4 too.

I have a SR opened for 4 weeks...(114334, pinta, a gimp-like
mono-based graphics package)

earlier this month I sent emails to their maintainers, and one of them
told me to ask mono release manager. no reply for now unluckily but
seems they added 12.1 for some repositories.

and there're rumors on the internet saying when attachmate acquires
SuSE, they didn't acquire our mono developers.


anyway we have a half-dead mono in openSUSE for a while.

and mono is sometimes important for openSUSE gnome.(eg:
banshee...which depends a lot on Mono, and our mono versions are
obsolete enough that to make it unstable...on KDE you can't even get
it running; another eg: monodevelop)

so

1. is there any plan we continue collaboration with mono official
developers or we take these repositories back into our own
hands...while that's not important at all...just curious to know

2. what more important is, we have to call enough volunteers to update
them all for our coming 12.2 beta. 12.2 will be released on late 2012,
but our mono version is in 2011...nearly 12 months ago. latest stable
mono is released on Dec 19 2011.

any idea or news about it?

Greetings

marguerite

Status: Distribution

Stephan Kulow — 2012-05-22T08:56:36

Hi,

While factory has a lot of broken packages, it doesn't look too bad for
the beta to be released, BUT the build service has major performance
problems for a while now and it seems to become worse and worse every day ;(

So I can't even foresee when we can have images to test - and as a
reminder: this comes before the fixing, which comes before the
releasing. So this is my top priority right now: finding the problem
with the build service or at least work around it as good as we can.

On unrelated news: Raymond is confident enough to made plymouth the
default, so we'll have that for the Beta - and kernel 3.4 made it! :)

Greetings, Stephan

curses/ncurses crazyness

Cristian Rodríguez — 2012-05-19T21:20:00

Hi:

What do people think about providing just one ncurses/curses variant in 
12.2 ?

Currently there is ncurses5, ncurses6 each one having a "widechar" 
variant whose headers are provided by the same package at the same time...

I have a few mutually-exclusive proposals to cleanup this:

Proposal 1:

- Provide only ncurses6 in widechar variant as libncurses.so, with 
headers in /usr/include/ncurses fix the fallout if any.

This is my favorite option.

Proposal 2:

- Separate curses5, curses6 , their headers and its variants in separate 
packages,

libncurses5-devel
libncurses5w-devel
libncurses6-devel
libncurses6w-devel

all providing an update-alternative script for ncurses-config and making 
the widely used ncurses-devel package name a provides of  libncurses6w-devel


any thoughts or suggestions appreciated.