Hi,
I see that the factory has both python2 and python3.
Are there any plans about switching to python3 as default?
I will also appreciate if the python maintainers can push=20
home:HighwayStar:branches:devel:languages:python python3-matplotlib
Alin
PS can we also, cripple kmail by default, or update the settings of our
mailing list to accept html emails...
It is bloody annoying to get your messages bounced back because of the default
settings of the mail client.
--
Without Questions there are no Answers!
______________________________________________________________________
Alin Marin ELENA
Advanced Molecular Simulation Research Laboratory
School of Physics, University College Dublin
----
Ardionsamblú Móilíneach Saotharlann Taighde
Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath
-----------------------------------------------------------------------------------
http://alin.elenaworld.net
______________________________________________________________________
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi all,
As part of one of the Linux kernel Summit discussions today, it was
brought up that after a kernel is released (for example 3.5), it's a bit
too late to be doing testing to see how well it is working out. The .0
release is usually a bit rough, and it takes until the .1 or .2 release
to get most major issues out of the way.
So, the kernel developers would like to get a wider range of testing,
and one thing proposed would be to have rolling distros switch their
kernel over a bit earlier to the new release than they had been doing.
Specifically, around the -rc5 point in time would be great. That way,
any reported regressions could be fixed sooner and get into the final .0
release for everyone to use.
Now this does place a bit of a larger burden on the users of those
distros to be diligent in reporting problems, and the distro engineers
to report the issues upstream as well, but it sounds like a reasonable
thing to try out.
So, for the next kernel release, I'm thinking of switching the kernel in
Tumbleweed over to 3.6 at the -rc5 timeframe. Does anyone strongly
object to this happening?
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
I just did a dup to a 32 bit Beta 2 P4/Celeron system last dup'd about 6
weeks ago (host t2240). It appeared to complete normally, but after the
zypper ps warning there was a segmentation fault line. Tail of dmesg:
[ 37.342287] Installing knfsd (copyright (C) 1996 okir(a)monad.swb.de).
[ 38.104167] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
recovery directory
[ 38.113952] NFSD: starting 90-second grace period
[ 44.610044] eth0: no IPv6 routers present
[ 475.004020] ------------[ cut here ]------------
[ 475.004041] WARNING: at
/home/abuild/rpmbuild/BUILD/kernel-desktop-3.4.2/linux-3.4/net/sched/sch_generic.c:256
dev_watchdog+0x1e8/0x200()
[ 475.004046] Hardware name:
[ 475.004049] NETDEV WATCHDOG: eth0 (e100): transmit queue 0 timed out
[ 475.004052] Modules linked in: snd_pcm_oss snd_mixer_oss snd_seq
snd_seq_device nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc dm_mod
sr_mod snd_intel8x0 cdrom snd_ac97_codec ac97_bus snd_pcm snd_timer snd
soundcore snd_page_alloc iTCO_wdt iTCO_vendor_support microcode pcspkr e100
i2c_i801 shpchp pci_hotplug floppy i915 drm_kms_helper drm i2c_algo_bit video
button scsi_dh_rdac scsi_dh_alua scsi_dh_hp_sw scsi_dh_emc scsi_dh fan
processor thermal thermal_sys ata_generic ata_piix sata_sil
[ 475.004113] Pid: 0, comm: swapper/0 Not tainted 3.4.2-1-desktop #1
[ 475.004117] Call Trace:
[ 475.004138] [<c02054b9>] try_stack_unwind+0x199/0x1b0
[ 475.004149] [<c02041d7>] dump_trace+0x47/0xf0
[ 475.004155] [<c020551b>] show_trace_log_lvl+0x4b/0x60
[ 475.004161] [<c0205548>] show_trace+0x18/0x20
[ 475.004169] [<c06f02fe>] dump_stack+0x6d/0x72
[ 475.004178] [<c0233188>] warn_slowpath_common+0x78/0xb0
[ 475.004185] [<c0233253>] warn_slowpath_fmt+0x33/0x40
[ 475.004194] [<c0636ef8>] dev_watchdog+0x1e8/0x200
[ 475.004204] [<c0240808>] run_timer_softirq+0xf8/0x300
[ 475.004211] [<c02398a1>] __do_softirq+0x81/0x1b0
[ 475.004217] [<c02040b6>] do_softirq+0x76/0xb0
[ 475.004224] ---[ end trace e91e2e809858261d ]---
[ 475.021328] e100 0000:01:02.0: eth0: NIC Link is Up 100 Mbps Full Duplex
[ 2774.999044] end_request: I/O error, dev fd0, sector 0
[ 3268.406459] udevd[12045]: starting version 182
[ 4264.313985] nfsd: last server has exited, flushing export cache
[ 4269.974101] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state
recovery directory
[ 4269.974153] NFSD: starting 90-second grace period
[ 4875.923898] zypper[2291]: segfault at 0 ip 08140fd8 sp bfcdcd80 error 4 in
zypper[8048000+151000]
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I boot 12.2 in text mode, with this line:
title Desktop -- openSUSE 12.2 - verbose II
root (hd0,2)
kernel /boot/vmlinuz root=/dev/disk/by-label/Main resume=/dev/disk/by-label/Swap showopts splash=verbose console=tty1 loglevel=3 vga=0x333 3
initrd /boot/initrd
This produces a detailed log during boot showing the services as they
start or fail, which I find nice and productive.
The problem is that when the virtual terminals are created, the
previous text is erased. How can I avoid that?
With system V this was controlled in inittab:
1:2345:respawn:/sbin/mingetty --noclear tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
See the first terminal? It is different. Where is the equivalent for
systemd?
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAlAaWO8ACgkQtTMYHG2NR9XIEgCdEqLfs0FFzWcceKr2p8n+i1bY
kAgAn37XmEhBHa4tYwmMgy9jDaBXgb66
=3UB0
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Dear Factory contributors and packagers,
As openSUSE 12.2 is frozen and Factory is 'open to go wild' again, I
would like to announce that the packaging guidelines have some
extensions (not really new) that will be stricter enforced than they
used to be.
Currently a common rule to be 'ignored' or packagers are not aware is
around the topics of:
- .Changes entries
- Patches
First, the .changes entry (rpm changelog) surves two purposes:
- News for the user
- History tracking of packaging changes (often referenced in bugs to
verify if a user has the latest packaging bugfixeS).
A simple "Update to version x.y.z" is, as before, not accepted. There
should be some buzz around the update for the user; some major reasons
to the upgrade should be listed
Changes on the package itself should be mentioned in a way that any
other contributor to the same package can follow traces of why
something is the way it is. Commonly, Added (build)dependencies are
interesting to be seen, special hacks to make something work in a
particular way [..]: Always consider that package maintenance is a
distributed task and various contributors need to be able to step up
at will.
Patches:
The rules about patches are listed at
http://en.opensuse.org/openSUSE:Packaging_Patches_guidelines .
Most prominent is likely the mentioning of the patches life cycle,
which forces you to mention additions and removals of patches in the
changelog. As history shows, this can be helpful if a patch got
removed, and later a regression is reported; finding out when a patch
was removed can be crucial in reconstructing feature sets (including
contacting the contributor that dropped it.. which is easily extracted
from the .changes if listed)
The main appeal is to the devel project maintainers / reviewers, to
keep out for those rules, to live according to them, as it is
frustrating for everybody if a package needs to be declined by the
Factory Review team:
- The dev prj maintainer is the one getting the 'decline' (as it was
usually a forwarded request), which often leaves the 'fixing' to the
devel project maintainers, where the 'originator' of the fix would
have been willing to actually do that...
And the Factory Review team also prefers to see complying submissions
to having to reject SRs... reject is not fun for anybody!
Looking forward to many more SRs to accept!
Dominique / DimStar
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Does anybody mean to package it?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Approaching the release date it would be good if more eyes would take a
look at the release notes and provide feedback. Find the sources of the
release notes in the berlios SVN:
https://svn.berlios.de/svnroot/repos/opensuse/trunk/documentation/release-n…
I'd prefer patches against the XML file, but general feedback based on
the HTML or YaST output format is also fine.
We especially must make sure to eliminate all CHECKIT remarks ;) I added
most of these CHECKIT remarks to old systemd related entries that I took
over from the 12.1 document.
aTdHvAaNnKcSe!
--
Karl Eichwalder SUSE LINUX Products GmbH
R&D / Documentation Maxfeldstraße 5
90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
12.2 RC2
I ran zypper DUP yesterday and it updated around 190 packages. I did it
again just now and there are another 174 today including having to
accept a 12.2 licence agreement that includes a typo. Today's stuff
includes new packages such as samba 3.6.7 and a new kernel 3.4.6-1.10.1
Is this the GM?
Thanks,
L x
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi
Is it too late to ask for the latest nss-pam-ldapd package to be
included in 12.2? The latest stable version is 0.8.10 whilst 12.1 and
12.2 are stuck with the older 0.7.x series.
Thanks
L x
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Last zypper dup on this 64 bit system belonging to Bob Stia was less than a
week ago. None of my own systems have anything 64 bit. Today I tried again,
after 'zypper dup -r KDE49'. Now it wants to downgrade 23 packages including
Firefox and SeaMonkey, and install 68 new packages, most of which are
lib*32bit. There are only 5 to upgrade, 4 of which are qt3/kde3. Should I try
again some other time? Something else?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org