November 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Fwd: mozilla-nspr: declined by factory-auto
by Wolfgang Rosenauer 06 Nov '13

06 Nov '13

Hi, is there any way to avoid that check to fail? I know I can remove the full URL but this is a temporary thing. That file is not yet available since upstream is very slow in publishing tarballs for releases and many times we cannot/don't want to wait until they appear. So do I need to remove the full path? Wolfgang -------- Original-Nachricht -------- State of submit-request #201261 was changed by factory-auto: review -> declined Comment: Output of check script: ERROR: Failed to download ftp://ftp.mozilla.org/pub/nspr/releases/v4.10.1/src/nspr-4.10.1.tar.bz2 Source URLs are not valid. Try "osc service localrun download_files" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] "What the udevmountd"
by Jan Engelhardt 06 Nov '13

06 Nov '13

Hi, so doing `zypper dup` just got me a new package "udevmountd" installed in the Factory du jour. Apparently it comes from sysconfig rather than systemd. But what on earth is this, and what do we need it for? There is no manpage or anything for it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] release notes 13.1 review
by Ludwig Nussel 06 Nov '13

06 Nov '13

Hi, I just had a quick look at the CHECKIT items in http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/ and I think the following items should be removed: 2.2. No Network after Installation 2.3. The proprietary NVIDIA driver requires users to have access to /dev/nvidia* devices 3.1. openSUSE Documentation 3.4. Enable Secure Boot in YaST Not Enabled by Default When in Secure Boot Mode 3.5. Wrong Bootloader When Installing from a Live Medium in a UEFI Environment 3.6. Crypted LVM in UEFI Mode Needs /boot Partition 4.1. systemd: Activating NetworkManager with a network.service Alias Link The following items still apply 3.3. UEFI—Unified Extensible Firmware Interface 4.2. SYSLOG_DAEMON Variable Removed 5.2. Configuring Postfix I'm unsure about 5.1. Initializing Graphics with KMS (Kernel Mode Setting) -> It refers to 11.3 so maybe time to remove? 5.3. GNOME: Workaround to Set Shift or Ctrl+Shift as Shortcut Keys for Input Source Selection -> someone from the gnome team may be able to comment here cu Ludwig -- (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 To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 34

Re: [opensuse-factory] SOLVED: postfix does not run
by Christian Boltz 06 Nov '13

06 Nov '13

Hello, Am Freitag, 22. März 2013 schrieb Patrick Shanahan: > /etc/postfix/main.cf had @_some-parameter_@ setting for every > "xxxxxxx_directory =" line. > > After correcting "xxxxxxxx_directory =" settings per my Tumbleweed > machine, postfix appears working correctly. > > This mess probably occurred on installing/upgrading postfix: > postfix-2.9.6-2.1.x86_64 Sun Mar 10 11:14:39 2013 > but the rpm main.cf does not contain "@.............@". This sounds like https://bugzilla.novell.com/show_bug.cgi?id=796162 which should be fixed since some time. I'd guess some older postfix package broke your main.cf. Nevertheless, if you want to be really sure, uninstall postfix, move away /etc/postfix and re-install the postfix package. Regards, Christian Boltz -- Argh, ich wollte heute doch gar nicht mehr siggen! [Michael Hoffmann in dag°] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Secure Boot 13.1 RC2
by Günther J. Niederwimmer 06 Nov '13

06 Nov '13

Hello, can any tell me, is it possible to Install with active secure boot? On my system ASUS P8C WS it is not :(. I have installed a W8 on this system, with secure boot. With active secure boot it is not possible to start a uEFI Installation from DVD, when it is possible the Installation is starting in "normal" Mode. With deactivatet Secure Boot it is possible to install in uEFI Mode. When I activate secure Boot after the Installation in the oS the system is nerer starting. Only when I deactivate Secure Boot in the Bios, oS is starting again in uEFI mode. -- mit freundlichen Grüssen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

[opensuse-factory] zypper dup from 12.3 fails
by Sankar P 06 Nov '13

06 Nov '13

Hi, I was running 12.3+updates in my laptop and wanted to upgrade to 13.1 But adding the 13.1 DVD iso as the only installation source and doing a zypper dup fails with an error: Problem: cannot install both rpm-4.10.2-2.1.1.x86_64 and rpm-4.11.1-6.2.1.i586 Solution 1: Following actions will be done: keep obsolete rpm-4.10.2-2.1.1.x86_64 ... and a list of few rpms. Is this a known issue ? -- Sankar P http://psankar.blogspot.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] [opensuse-packaging] Re: Some Python questions (Was: Re: devel:language:python3)
by Yamaban 06 Nov '13

06 Nov '13

On Mon, 28 Oct 2013 09:17, Sascha Peilicke <speilicke@...> wrote: > On Thursday 24 October 2013 15:07:49 Adam Spiers wrote: >> Sascha Peilicke (speilicke(a)suse.com) wrote: >>> On Saturday 12 October 2013 14:19:57 you wrote: >>>> Hi Sascha ! >>>> >>>> Is there any possibility we (all python maintainers) discuss our goals >>>> both python2 and python3 ? >>> >>> sure, since Juergen joined recently too, I CC'ed everyone. I dunno how you >>> guys prefer it, we could have an IRC meeting at some point but I guess >>> it's >>> easier to stay with mails just now. Therefore I added opensuse-packaging@ >>> because that's really where we should discuss things. >>> >>>> We receive requests sometimes update and/or >>>> new packages which are Python3 compatible. >>> [snip] >>> In the long run, py3k will gradually replace py2k in openSUSE, that means >>> if the critical mass is reached and most upstreams moved on, py2k pkgs >>> will slowly fade from Factory. Meanwhile, some pkg upstreams already >>> stopped caring for py2k, so their pkgs simply stay with the last working >>> version. Currently it's more manual work, I agree. >> >> Just saw this interesting data-point - Fedora is going to switch to >> Python 3 by default: >> >> http://lwn.net/Articles/571528/ > > Jupp. I guess it's more obvious for Fedora than us since they always want to > be bleeding edge. But what does that mean in reality? They're not likely going > to ditch py2 any time soon. there's just far too much software out there that > needs it. Since RH did a wise choice in standardizing on Python for most of > their tooling, I'd bet they would have to port a whole lot of stuff first. So > in the end it boils down to what /usr/bin/python points too. On openSUSE, it's > the same as /usr/bin/python-2.7. I thought about changing this and we > discussed this in length. Finally, we decided against it [0]. Others than > that, py3k is in very good shape inside 13.1 and will get more packages during > the next dev cycle. > > [0] http://lists.opensuse.org/opensuse-packaging/2013-08/msg00089.html IMHO, we need the first step: separate - the (very) Good (python ver does not matter) - the nice (need either py2 or py3 and be honest about) - the bad (work only with one special python version) - the ugly (need either py2 or py3 and tell not, or lie about) The Good is what we want to prefere, they can point to /usr/bin/python . The nice need to point to either /usr/bin/python2 or /usr/bin/python3 . The bad will have to point to a more specific version, e.g. /usr/bin/python2.7 and need to have a special cared for spec file. Goal would be to get them to the nice point. The ugly, well they will need work, no matter what. The more cleanly defined the needs of a package are the easier it will be to handle it in the long run. We will need a time with a (peacefull) coexistence of python 2 and 3 . Having the programs point to either python2 or python3 is a step in the right direction, and helps to keep the hassle down. Some packages (e.g. calibre) will need special care, no matter what. Our goal should be raising sensitivity upstream. Having them in the know and care about this lowers the problem for all distros. The trouble will be getting some of upstream to care about this. Thats my 2ct on this. - Yamaban. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] journalctl very slow
by Ruediger Meier 05 Nov '13

05 Nov '13

Hi, I'am trying to watch the logs but it's a bit too slow. journalctl is running since 8 hours now and it has printed only 120MB text yet. That's only 4K/s. Is this normal? journalctl also consumes 100% CPU the whole time so the machine is useless currently. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

18 53

[opensuse-factory] 13.1 grub probe and bios_grub partition
by Bruno Friedmann 05 Nov '13

05 Nov '13

Hello, on a 13.1 with a double disque mostly used to Raid1 the system I've the following layout Model: ATA WDC WD3000HLFS-0 (scsi) Disk /dev/sdg: 300GB Sector size (logical/physical): 512B/512B Partition Table: gpt_sync_mbr Number Start End Size File system Name Flags 1 1049kB 2097kB 1049kB primary bios_grub 2 2097kB 1085MB 1083MB ext4 primary boot, legacy_boot 3 1085MB 300GB 299GB primary raid Model: ATA WDC WD3000HLFS-0 (scsi) Disk /dev/sdh: 300GB Sector size (logical/physical): 512B/512B Partition Table: gpt_sync_mbr Number Start End Size File system Name Flags 1 1049kB 2097kB 1049kB primary bios_grub 2 2097kB 1085MB 1083MB ext4 primary boot, legacy_boot 3 1085MB 300GB 299GB primary raid /boot is build on mdadm -D /dev/md126 /dev/md126: Version : 1.0 Creation Time : Wed Oct 23 09:35:33 2013 Raid Level : raid1 Array Size : 1057728 (1033.11 MiB 1083.11 MB) Used Dev Size : 1057728 (1033.11 MiB 1083.11 MB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Tue Nov 5 10:21:32 2013 State : active Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : kusco.disney.interne:mdboot UUID : 599c149a:9d172f66:aae67d69:21533069 Events : 19 Number Major Minor RaidDevice State 0 8 98 0 active sync /dev/sdg2 1 8 114 1 active sync /dev/sdh2 grub-probe is set on (by default) I collect a number of kernel crashes Anyone has seen that too ? [1117363.858728] EXT4-fs (sdg1): VFS: Can't find ext4 filesystem [1117363.862534] EXT4-fs (sdg1): VFS: Can't find ext4 filesystem [1117363.866341] EXT4-fs (sdg1): VFS: Can't find ext4 filesystem [1117363.877396] ISOFS: Unable to identify CD-ROM format. [1117363.885167] REISERFS warning (device sdg1): sh-2021 reiserfs_fill_super: can not find reiserfs on sdg1 [1117363.897389] XFS (sdg1): bad magic number [1117363.897402] ffff8803d7cd2000: 52 56 be 1b 81 e8 39 01 5e bf f4 81 66 8b 2d 83 RV....9.^...f.-. [1117363.897408] ffff8803d7cd2010: 7d 08 00 0f 84 e2 00 80 7c ff 00 74 46 66 8b 1d }.......|..tFf.. [1117363.897414] ffff8803d7cd2020: 66 8b 4d 04 66 31 c0 b0 7f 39 45 08 7f 03 8b 45 f.M.f1...9E....E [1117363.897419] ffff8803d7cd2030: 08 29 45 08 66 01 05 66 83 55 04 00 c7 04 10 00 .)E.f..f.U...... [1117363.897427] XFS (sdg1): Internal error xfs_sb_read_verify at line 780 of file /home/abuild/rpmbuild/BUILD/kernel-default-3.11.6/linux-3.11/fs/xfs/xfs_mount.c. Caller 0xffffffffa079b295 [1117363.897437] CPU: 3 PID: 239 Comm: kworker/3:1H Tainted: G W 3.11.6-1-default #1 [1117363.897443] Hardware name: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H/GA-890GPA-UD3H, BIOS FF 11/24/2010 [1117363.897497] Workqueue: xfslogd xfs_buf_iodone_work [xfs] [1117363.897502] 0000000000000001 ffffffff81560e60 ffff8803d7f55000 ffffffffa079d7d6 [1117363.897511] 0000030c7d08000f ffffffffa079b295 ffff88041107ae40 0000000000000016 [1117363.897519] ffff8803d7f55000 ffffe8ffffcc1300 ffffffffa07eccdd ffffffffa079b295 [1117363.897527] Call Trace: [1117363.897556] [<ffffffff81004868>] dump_trace+0x78/0x2c0 [1117363.897569] [<ffffffff81004b3f>] show_stack_log_lvl+0x8f/0x170 [1117363.897581] [<ffffffff81005e0c>] show_stack+0x1c/0x50 [1117363.897593] [<ffffffff81560e60>] dump_stack+0x41/0x51 [1117363.897643] [<ffffffffa079d7d6>] xfs_corruption_error+0x56/0x80 [xfs] [1117363.897774] [<ffffffffa07eccdd>] xfs_sb_read_verify+0xfd/0x120 [xfs] [1117363.898052] [<ffffffffa079b295>] xfs_buf_iodone_work+0x75/0xd0 [xfs] [1117363.898111] [<ffffffff810687fd>] process_one_work+0x16d/0x420 [1117363.898123] [<ffffffff810693c6>] worker_thread+0x116/0x3b0 [1117363.898135] [<ffffffff8106f8df>] kthread+0xaf/0xc0 [1117363.898147] [<ffffffff8156ee7c>] ret_from_fork+0x7c/0xb0 [1117363.898158] XFS (sdg1): Corruption detected. Unmount and run xfs_repair [1117363.898199] XFS (sdg1): SB validate failed with error 22. [1117363.907358] FAT-fs (sdg1): invalid media value (0xe2) [1117363.907367] FAT-fs (sdg1): Can't find a valid FAT filesystem [1117363.911298] FAT-fs (sdg1): invalid media value (0xe2) [1117363.911306] FAT-fs (sdg1): Can't find a valid FAT filesystem [1117363.915213] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device sdg1. [1117363.919058] hfsplus: unable to find HFS+ superblock [1117363.922844] qnx4: wrong fsid in superblock. [1117363.926526] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [1117363.926735] ufs_read_super: bad magic number [1117363.938417] hfs: can't find a HFS filesystem on dev sdg1 If I understand why the system try to get information about the partition or disk the result look like very sub-optimal making any alarm software worrying administrator. another one is why I saw tainted CPU: 3 PID: 239 Comm: kworker/3:1H Tainted: when I only have oss installed ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 5

[opensuse-factory] user@.service was unmasked after zypper dup
by Andrey Borzenkov 04 Nov '13

04 Nov '13

I masked user@.service after update to RC1 because it was reliably causing long delay on shutdown (https://bugzilla.novell.com/show_bug.cgi?id=841544) After zypper dup recently I observed the same delay and was surprised to see user(a)0.service running again. Is not "systemctl mask" presumed to be persistent? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1