October 2008 - openSUSE Testing - openSUSE Mailing Lists

encrypted suspend - and some questions about other features
by Christian Boltz 27 Oct '08

27 Oct '08

Hello, http://en.opensuse.org/Testing:Features_11.1#Security_Issues_with_Suspend_a… says that 11.1 supports encrypted syspend - including encrypted swap. Unfortunately there's no description how to setup this, and the feature is also not public available on features.opensuse.org. Can someone please tell me some details? I'd really like to use this feature... Some other features that need some more information to be tested: - Package history (Feature No: 110205) - how can a user/admin view the history? - Whole software management stack should warn about oudated update repo (Feature No: 301904) - since this was (also?) my idea, I'd be interested in the whole FATE entry and how it is implemented in the repository metadata - how to test this without setting up a private mirror and let it expire? ;-) - Public directory support for encrypted home directories (Feature No: 301923) - how is this implemented? - Include a friendly graphical user interface for Subversion (Feature No: 303292) - nice, but which application should I install/start? - Acoustic signal for bootloader when booting from installation medium (Feature No: 303481) - obviously works, since grub is annoying me with a beep at every boot - is this beep optional? how to disable it? (the feature says _optional_ beep ;-) - Compress cracklib password database (Feature No: 303536) - which files is this about? - if the answer is /usr/share/cracklib/pw_dict.pwd, then be prepared for a bugreport ;-) - 'Security health status' YaST Module ('Bastille' like functionality) (Feature No: 303598) - sounds promising, but obviously wasn't installed by zypper dup :-( - which package? - Ability to log all configuration changes done via YaST (Feature No: 303700) - how can I enable this mode? - Patch terminology standard (Feature No: 304512) - Result? Most of these features have a common problem: They are not available via features.opensuse.org and therefore it's impossible to know details what and how to test :-( The best solution would be to make all listed features available on features.opensuse.org - and to add links to them from the Testing page. (If this is not possible for whatever reason, please add more details to the listed features on the Testing page.) Oh, BTW, IPv6 transport for NFS (TI-RPC User-Space Library) (Feature No: 300607) is probably outdated since NFS over ipv6 was disabled in beta3 AFAIK. Regards, Christian Boltz -- Wir brauchen ein "postfixbuchconf"-Kommando, damit wir Autor und Version bestimmen können... ;) [Patrick Ben Koetter in postfixbuch-users] -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

2 1

openSUSE 11.1 Beta 3 ready to test
by Holger Sickenberg 23 Oct '08

23 Oct '08

Hi everybody, openSUSE 11.1 Beta 3 is official announced now. It is available at http://software.opensuse.org/developer Please have a look at http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.1_dev before you start your installation. Again we ask you to test if new features are working as expected. Those we created a wiki page containing a list of features at http://en.opensuse.org/Testing:Features_11.1 Further information on testing are available at http://en.opensuse.org/Testing I also attached the announcement mail from Christoph. Looking forward to your feedback. Thanks, Holgi

3 2

Yast2 software management bug
by Dave Plater 22 Oct '08

22 Oct '08

Hi, there are two bugs filed for yast2 software management that seem the same to me but are inactive. https://bugzilla.novell.com/show_bug.cgi?id=436833 and https://bugzilla.novell.com/show_bug.cgi?id=437215 Yast2 software management is almost unusable as a result but they haven't been assigned yet. Regards Dave Plater -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

3 2

squid on 11.1 beta2
by medwinz 13 Oct '08

13 Oct '08

I try to setup transparent proxy with squid 3 on beta2 with only one Network card, but i didn't success. The same setting runs well with ubuntu. Is it by design? I know that the squid 3 on beta2 is not compile with --enable-linux-netfilter, but when i try to compile it with it, I still cannot manage the transparent proxy. Also the squid configuration in yast2 only works with squid 2 not squid 3. Should I fill the bug report? Regards, medwinz -- Imelda Marcos - "I did not have three thousand pairs of shoes, I had one thousand and sixty." -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

2 1

beta2 torrent still not working?
by Per Jessen 06 Oct '08

06 Oct '08

Is anyone looking at getting the torrents to work? I have been getting this error since Saturday: These errors occurred during execution: [09:53:28] Aborting the torrent as it was rejected by the tracker while not connected to any peers. Message from the tracker: unregistered torrent /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

1 1

openSUSE 11.1 Beta 2 ready to test
by Holger Sickenberg 06 Oct '08

06 Oct '08

Hi everybody, openSUSE 11.1 Beta 2 is official announced now. It is available at http://software.opensuse.org/developer Please have a look at http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.1_dev before you start your installation. Again we ask you to test if new features are working as expected. Those we created a wiki page containing a list of features at http://en.opensuse.org/Testing:Features_11.1 Further information on testing are available at http://en.opensuse.org/Testing I also attached the announcement mail from Christoph. Looking forward to your feedback. Thanks, Holgi

1 0

Re: [opensuse-testing] NUI - France would like to test SLE 11
by Quentin Jackson 04 Oct '08

04 Oct '08

Yes, I understand. So I guess the question is, what is the short and long term goal of OpenSuSE? Personally I think the long term goal automatically = the short term goal without a lot of people realising it. When I first started using linux, the idea of building brick upon brick and improving on previous releases was and still is fantastic, I think it actually drives a lot of people to keep doing this, but inevitably changes mean bugs and bugs mean some of the bricks get kicked out below us but most people don't think far enough ahead to realise what is happening here. The way I see it, the manner in which we are making these changes means the goal of having a truly stable OS will never be achieved which leaves me wondering what is the point of all this? Where is the next step for distro's in the opensource movement? How will a community distro ever reach mainstream with such unpredictable results? Let's face it, even post release there are no gaurantees that anything unfixed will be fixed, maybe in the next release but chances are something different will be broken there too. At times we will get close, other times will be bad, but there will still be no way anyone will know how good a release is unless they try it for themselves which I think you'll agree is not a very good advertisement for a distro. >From personal experience there have been 2 good releases since the 9.x series only, SuSE 9.3 and OpenSuSE 10.3 and even they were not perfect. That's 2 out of 8 releases or 25% of the great work that is done. It seems like a waste to me. I think you'll also agree that there are some things that you just cannot release with if they're not running right. Two examples would be no X or no bootloader. There are many more, these should truly be blockers, maybe we could start by tasking someone with identifying those and laying down the beginnings of some absolute rules? All in all, if this isn't already mandated somewhere perhaps a compromise could be that no release is considered final until an x.3 release and maybe even only that release will continue to receive the best backporting of fixes, stability improvements etc? That way people who want the latest can always upgrade to any release, bug test etc, people who want stable know to get a .3 release which comes around every 2 years. We could effectively consider x.0, x.1 x.2 = RC1, RC2, RC3 and the x.3 = final. I think these two points would start to give to point us in the right direction, maybe even start giving us an advantage over other distros including some of the more stable ones. What do you think? Q On Thu, 2008-09-25 at 18:08 +0200, Andreas Jaeger wrote: > "Quentin Jackson" <Quentin.Jackson(a)exclamation.co.nz> writes: > > > Well I found the priority documentation at > > http://en.opensuse.org/Bugs/Definitions#Bug_Severities, it seems quite > > good, so further to below, I feel we should not be releasing a distro > > with any outstanding job having a criticality over Normal. Obviously > > there would be exceptions, but it seems that we do indeed release a > > distro with 'Major' severity outstanding calls correct? So by proxy > > that would be saying that we're OK releasing a distro that has "Major > > loss of function"? > > We include priorities as well - not have any P1 bugs. > > In the past we had as policy no blocker. No bugs with severity above > normal is not feasible - we would never ever release ;-) or release with > an outdated distribution. > > There's indeed quite a difficult balance between time and quality - and > we do this also with limiting the changes we allow to make to the > distribution at some time, > > Andreas -- To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-testing+help(a)opensuse.org

1 0