openSUSE Factory May 2011

factory@lists.opensuse.org

103 participants
98 discussions

[opensuse-factory] Can we expect OpenSUSE 12.1 Milestone 1 This Thursday?
by Roman Bysh 20 May '11

20 May '11

Hello all, Can we expect to see OpenSUSE 12.1 Milestone 1 uploaded for this Thursday's release? Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 6

[opensuse-factory] openFATE 312364 Mobile Broadband Wizard
by Roger Luedecke 20 May '11

20 May '11

https://features.opensuse.org/312364 I have made this feature request. I feel that something like this is critical. Though I am not the most saavy user, I have always been able to resolve a problem eventually. However this one i have been forced to concede defeat. A Wizard allowing easy setup and use of my mobile broadband would be greatly welcome, and I doubt I am the only user in this boat especially since netbooks are becoming more popular. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 5

[opensuse-factory] rpmlint status update
by Ludwig Nussel 20 May '11

20 May '11

Hi, Heads up and status update from the rpmlint front. rpmlint will soon be updated to version 1.2 in Factory. It brings one check that could turn out to be annoying: 'incorrect-fsf-address' warns about outdated or misspelled fsf addresses in files. That's usually something for upstream to fix. We'll see how many packages it catches. A new SUSE specific check warns about init scripts for runlevel 4. That runlevel is supposed to be admin defined so distro packages should not use it. Just remove the '4' from 'Default-Start'. The /var/run check got accepted upstream as non-ghost-in-var-run (was dir-or-file-in-var-run before). I plan to mark that check fatal in near the future as aaa_base now actually mounts tmpfs on /var/run so anything in there must be created at run time. You need to create files in /var/run at run time and mark them as %ghost in the package. Similarly 'non-ghost-in-var-lock' was introduced as /var/lock may use tmpfs too in the future. Packages should actually not use /var/lock at all. It's supposed to be only used for legacy device lock files (e.g. LCK..ttyS0). The new check 'non-position-independent-executable' is a port of prp-pie which in turn got dropped. All setuid binaries as well as network facing daemons should be compiled as position independent executables to make exploits more difficult. The list of binaries where this applies is manually maintained. So if anything is missing please let us know. Additionally we now have the possibility to make certain checks no longer filterable via package specific rpmlintrc. Initially that will be used for mandatory security checks. The shared library packaging policy is probably the next. If you are hit by this outside of Factory you can still get your package to build by setting the badness to zero¹ cu Ludwig [1] http://en.opensuse.org/openSUSE:Packaging_checks#Disarming_Fatal_Errors -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] On the insanity of the licensedigger bot
by Cristian Rodríguez 18 May '11

18 May '11

Hi: This fine piece of software keeps blindly rejecting package submissions for no reason whatsoever,license names that have been accepted for years now are instantly rejected,without human intervention. Will be cool if at least packages remain in state review after the bot has failed its dubious heuristics,so a human can look into it, instead of annoying developers at large. Cheers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 22

Re: [opensuse-factory] New things in 12.1
by Andreas Jaeger 18 May '11

18 May '11

On Tuesday, May 17, 2011 17:49:35 Steven Sroka wrote: > >On 15 May 2011 08:37, Kim Leyendecker <kimleyendecker(a)hotmail.de> wrote: > > Am 15.05.2011 13:16, schrieb Sascha Manns: > >> Hello Mates, > >> > >> some Bloggers asked, which new things are planned for 12.1. Maybe we > >> have a Site for this topic? > > Is there a request to minimize the wave of 32-bit packages being > pulled in when a user tries installing certain 64-bit packages. Could you give an example of such packages, please? > I haven't run into this problem recently myself, but I still hear > people talking about once in a while. In that case ask them for the package that triggers this so that we can figure out why. There might be a valid reason - like flashplayer being a 32-bit instance... Andreas -- Andreas Jaeger, Program Manager openSUSE aj(a){novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

[opensuse-factory] perl 5.14
by Stephan Kulow 18 May '11

18 May '11

Hi, I just submitted mls' perl 5.14 after checking the build failures in devel:languages:perl together with mls. I don't expect a huge problem from it, but it's hard to judge from test suites alone - so be warned. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 4

[opensuse-factory] New FATE#312321: drop blowfish and switch to sha512 as default hash
by Thorsten Kukuk 17 May '11

17 May '11

Hi, long time ago, when glibc did only support DES crypt(), we added libxcrypt with blowfish support to have a better default hash for local accounts. Meanwhile, glibc supports sha256 and sha512, thus I filled FATE#312321 to change the default password hash to sha512, drop blowfish from YaST2 and remove libxcrypt from the distribution to avoid maintaining the same code twice. As result, you cannot create new password hashes with blowfish, but as long as we have the glibc patch, you can still login with the old hash. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] xfprint&mousepad status (Tumbleweed broken packages)
by Jiri Slaby 17 May '11

17 May '11

Hi, these packages are broken in Tumbleweed: mousepad xfce4-panel-plugin-xfapplet xfprint It looks like all of them were deleted from factory (and moved to openSUSE:Dropped). As we have the latest xfce in Tumbleweed, I think those should be removed from Tumbleweed too, right? thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] Unicode support differs between python and python3
by Michal Vyskocil 17 May '11

17 May '11

Hi all, I noticed a difference in unicode support between python and python3. The first one is built with ucs4 support, the later with ucs2 support. That means python3 behaves differently with characters up to 65535 (2**16-1), because with UCS2 support it returns two characters. $ python -c 'print(len(unichr((2**16-1))))' 1 $ python -c 'print(len(unichr((2**16+10))))' 1 $ python3 -c 'print(len(chr((2**16-1))))' 1 $ python3 -c 'print(len(chr((2**16+10))))' 2 I am not sure if this difference is intentional or not, so I'm asking here instead of bugzilla. Maybe this is intended, because you save 50% of memory for most of python programs and you need to port your code to python3, so it's not a big issue I'd say - see PEP 261 [1] for details. If so, then this should be mentioned in README.SUSE. I did a quick review of other distributions: * Debian use UCS4 from 2.3 and most probably in python3 as well - [2] * Fedora use USC2 in python [3] and UCS4 (I assume --with-wide-unicode is UCS4) in python3 [4] What's your opinion here? [1] http://www.python.org/dev/peps/pep-0261/ [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=171062 [3] http://pkgs.fedoraproject.org/gitweb/?p=python.git;a=blob_plain;f=python.sp… [4] http://pkgs.fedoraproject.org/gitweb/?p=python3.git;a=blob_plain;f=python3.… Regards Michal Vyskocil

2 1

[opensuse-factory] openssh + pki
by Hans Witvliet 17 May '11

17 May '11

Hi all, Any vague chance of getting the patch of Roumen Petrov applied? http://roumenpetrov.info/openssh/#features With this patch, one can enjoy the security feautures supplied digital certificates (crl, ocsp, ...), like the one's used by openssl, apache, openvpn, strongswan etc etc. pki support has been included for a long time in the commercial branch of ssh, but (i think) due to the conservative nature of the people of openbsd, who still seems to be in control of openssh, this patch never made it into the mainstream code Patch is around since 2006, and still kept up-to-date Hans -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory May 2011