June 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] source_validator error: signature does not validate
by Kyrill Detinov 25 Aug '14

25 Aug '14

Hello. I can't build a package. Service source_validator failed. % osc build Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmpVbBhay Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector.keyring gpg: enabled debug flags: memstat gpg: keyring `/tmp/check_if_valid_source_dir-NL8Ezs/.checkifvalidsourcedir-gpg-keyring' created gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: key 015475F5: public key "Jakub Wilk <jwilk(a)jwilk.net>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks gpg: enabled debug flags: memstat gpg: Signature made Mon Jun 24 22:36:51 2013 MSK using RSA key ID 015475F5 gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: Good signature from "Jakub Wilk <jwilk(a)jwilk.net>" gpg: aka "Jakub Wilk <jwilk(a)debian.org>" gpg: aka "Jakub Wilk <ubanus(a)users.sf.net>" random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks (E) signature /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector-0.11.1.tar.gz.asc does not validate Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i Source service run failed! As far as I can see, the signature is good. This also happens with another package (graphics/icoutils). What is the problem? -- WBR Kyrill

2 5

[opensuse-factory] what happened to fbset?
by Felix Miata 04 Aug '14

04 Aug '14

in 11.4: # fbset -i mode "1152x864" geometry 1152 864 1152 864 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name : radeondrmfb Address : 0xd80c0000 Size : 3981312 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 1 YPanStep : 1 YWrapStep : 0 LineLength : 4608 Accelerator : No In 13.1B1: # fbset -l if 'fbset' is not a typo, You can use... # zypper se -s fbset ... No packages found. # command-not-found fbset fbset: command not found -- "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

8 18

[opensuse-factory] OSEP: openSUSE Distribution Daemon User and Group Names
by Guido Berhoerster 29 Jul '14

29 Jul '14

Hello, after initial discussion on the -packaging list (see http://lists.opensuse.org/opensuse-packaging/2014-02/msg00136.html) and incorporating some of the feedback we would like to introduce the attached openSUSE Enhancement Proposal about creating a safe namspace of system user and group names. Further comments and reviews would be appreciated. Full text of the OSEP (currently maintained at https://github.com/lnussel/osep_opensuse_usernames/blob/master/opensuse_use…): _____________________________________________________________________ OSEP: XXXX Title: Informational proposal: openSUSE Distribution Daemon User and Group Names Version: 0.1 Last-Modified: 03 Mar 2014 Author: Guido Berhoerster <gber(a)opensuse.org>, Ludwig Nussel <ludwig.nussel(a)suse.de> Status: Draft Type: Informational Created: 28 Feb 2014 Post-History: _____________________________________________________________________ Abstract -------- This OSEP proposes a defined pattern for unprivileged system user and group names. Specification ------------- Packages that add unprivileged users to e.g. run daemons as need to use names that follow the following regular expression: ^_[0-9a-z][0-9a-z_]*$ This policy is meant to be applied to all packages that are new to openSUSE Factory. Existing packages are encouraged to switch to the new policy. An exception are legacy users with a static uid as created on first installation by aaa_base, like e.g. 'root' or 'nobody'. Motivation ---------- Many packages need to add user and group names for their unprivileged daemons. Currently openSUSE Factory has a known lists of more than 130<<A>> such daemon user names. Many names are short for convenience, e.g. 'pop', 'vdr', 'tor' or 'znc'. Since there is no separate name space for system users those names may collide with names of real persons. A common pattern for user names on unix systems also is to combine letters of the given names and the surname which may lead to combinations that may also collide with system user names. Sharing a user name between a system user and a normal user leads to surprising or even security relevant misbehavior as the daemon user may write to files in the real user's home or vice versa. Since introducing a separate namespace is not possible in the current name service model, separating system users and real users must be done by naming them differently. Rationale --------- A special prefix or suffix to user names is a straight forward solution to the same namespace problem. Since long user names may not fully be displayed by e.g. the ps tool the chosen method needs to be short. Therefore using a single letter character may be used. According to the recommended regular expression for usernames in the useradd manpage<<D>> of the shadow package, dollar could be used as suffix or underscore as prefix or suffix. OpenBSD already implemented a policy to use underscore (ASCII character 95) as prefix in 2003<<C>>. This method is therefore considered proven in practice. For symmetry reasons and because many packages also create groups with the same name as the user the same solution should be applied to groups as well. License ------- This document has been placed in the public domain. References ---------- [bibliography] - [[[A]]] current list of known user names in opensuse is maintained in link:https://build.opensuse.org/package/view_file/openSUSE:Factory/rpmlint/… - [[[B]]] link:http://anonscm.debian.org/viewvc/pkg-shadow/upstream/trunk/man/useradd… manpage] - [[[C]]] List of sytem users in link:http://www.openbsd.org/cgi-bin/cvsweb/\~checkout~/ports/infrastructure… with short sentence expressing the "policy" - [[[D]]] some link:http://lists.opensuse.org/opensuse-packaging/2014-02/msg00103.html[num… collected by Guido -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

20 64

[opensuse-factory] factory-oss key expired
by Stefan Seyfried 17 Jul '14

17 Jul '14

Warning: The gpg key signing file 'content' has expired. Repository: factory-oss Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Fingerprint: 22C07BA5 34178CD0 2EFE22AA B88B2FD4 3DBDC284 Key Created: Fri Nov 7 15:10:07 2008 Key Expires: Sun May 4 17:01:33 2014 (EXPIRED) Rpm Name: gpg-pubkey-3dbdc284-49144c3f I already uninstalled gpg-pubkey-3dbdc284-49144c3f (the one I had installed had expired in 2010), but the one I got from the repo then is also already over its time... -- Stefan Seyfried "Your mail is 7 pages of printout. Do you seriously expect people that do openSUSE in their free time to read that? Little less Castro, little more JFK..." -- coolo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] About Factory's Version
by Stephan Kulow 09 Jul '14

09 Jul '14

Hi, As mentioned in several situations, it's my declared goal to seperate Factory from openSUSE releases in people's mindset and run it as a rolling distribution with its own agenda. So far Factory was meant purely as testbed for the next openSUSE release. But this has changed, and e.g. Factory releases DVDs whenever they are tested as good enough - see http://download.opensuse.org/factory/iso/ While openSUSE releases benefit from being "13.2", I feel we need something else than "13.2 Milestone 0" for Factory. But I miss a good idea what it can be - the "Snapshot20140605" the ISOs bear is unfortunately not good enough as this is tagged when the ISOs are ready - but the SuSE-release file is generated from things I need to copy. - I can image commiting an increasing commit ID whenever Factory is changed. We would talk about "I'm running Factory 20272, 172 builds behind"? - I can also imagine commiting every first of a month or every sunday or ... Now it's time for your creativity - what are your preferences for a Factory version? Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 25

[opensuse-factory] Reasons to switch to Factory
by Stephan Kulow 06 Jul '14

06 Jul '14

Hi, We[¹]'re working on a news article on Factory becoming a true rolling distribution[²] instead of being the development branch. As you will be very well aware, it's been a while since 13.1 (acording to the original 8 month cycle we would release in 3 weeks - and I'm actually quite happy we're not putting a release out a day after the Final ;-) But I still would like to listen reasons why people should not be sad 13.2 is not released, but rather take a second look at switching to Factory. And for this I need your help: why did you switch to Factory or why do you consider it? What are the selling points of Factory? What killer features are in Factory that we don't have in 13.1? Greetings, Stephan [1] The etherpad has 8 authors and it's just a draft :) [2] http://en.wikipedia.org/wiki/Rolling_Release#True-rolling_distributions -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

19 23

[opensuse-factory] BFQ KMP for testing
by Takashi Iwai 03 Jul '14

03 Jul '14

Hi, I made a quick add-on KMP for BFQ I/O scheduler that has been posted recently to LKML: https://lkml.org/lkml/2014/5/29/411 If you have a problem regarding I/O and desktop latency, this might be interesting. The KMP is found in OBS home:tiwai:bfq/bfq repo. It's currently built for openSUSE-FACTORY, openSUSE-13.1, SLE12 and Kernel:HEAD kernels. After installing the KMP, load bfq-iosched kernel module, and change the scheduler like: # echo bfq > /sys/block/sda/queue/scheduler If you want to make BFQ as default from the beginning, do like below: - Put "bfq-iosched" in $INITRD_MODULES in /etc/sysconfig/kernel - Run /sbin/mkinitrd once to rebuild initrd - Add a boot parameter "elevator=bfq" Then the BFQ module will be loaded automatically and used as default I/O scheduler at the next reboot. Have fun, Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 15

[opensuse-factory] Grub2 with XFS in root and no /boot ?
by vetter＠physik.uni-wuerzburg.de 02 Jul '14

02 Jul '14

Hi, should it be possible to have XFS in the root partition without separate /boot partition, when using grub2? Here is why I'm asking: I downloaded the Net-Install-CD: openSUSE-Factory-NET-x86_64-Snapshot20140619-Media.iso I booted a VMware VM from it. The VM has 1 GB RAM and a 60 GB disk. I partitioned: sda1 512 MB swap sda2 59.5 GB / xfs Then installed default KDE selection. There are 2 things: 1) When the machine has only 1 GB RAM, installation of bootloader gives no error, but after reboot system hangs in grub2 shell complaining: error: not a correct XFS inode. error: attempt to read or write outside of oartition. error: file '/boot/grub/i386-pc/xxxxx' not found I'm not sure, what xxxxx was. When I use ls (hd0,msdos2)/ it complains: error: not a correct XFS inode. error: attempt to read or write outside of oartition. error: not a correct XFS inode. 2) When system has 2 GB RAM, installing bootloader gives an error, giving the chance to do it again. But that also does not work. rebooting gives the same problems as above. In this case the missing file xxxxx is normal.mod. -- Mit freundlichen Gruessen, Andreas Vetter -- 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] FYI: OBS is currently down
by Richard Brown 30 Jun '14

30 Jun '14

The below has already been announced on opensuse-buildservice@ , but as it affects everyone contributing to factory quite heavily I figured I could get away with cross-posting the below here: >From Adrian Schröter (adrian(a)suse.de) > JFYI, the system is still down for SAN storage reasons again :/ > > Just some background, our admins tried to move from the "old" SAN > storage to a new (more reliable and expensive) SAN storage over the > weekend. That is something what should usally happen in online mode > because we are using LVM and are able to do an pvmove operation. > > At that point of time the old SAN storage saw their data escaping and > attempted a suicide. > > Our admins are trying to rescue the situation atm. I am not aware of > all details, but I see that the pvmove is at 22% atm. > > sorry for that > adrian I hear the pvmove is progressing well, but still under 40% at this time. Hope this helps, Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] openSUSE 13.1 cannot find /dev/root during boot up
by Roman Bysh 29 Jun '14

29 Jun '14

Hello List Mates, After reinstalling openSUSE 13.1 for the "8th" time, I am now posting what I believe is a serious problem with "mkinitrd" . I have a openSUSE 13.1 installed on my entire primary SATA Western Digital Black 500 GB drive. The secondary SATA is a Western Digital Blue 500 GB drive with OSX Mavericks installed on the first partition. The second partition is Linux /Data backup. Over the last few months, I've had to disconnect the secondary drive when updating openSUSE 13.1 so that Grub2 didn't add additional entries for OS X 32-bit and 64-bit. When the last update had finished, I shut down the PC two days ago without a reboot. This shouldn’t have given any problems. The following day I restarted the PC, changed the BIOS setting from AHCI to IDE. I noticed that the start up was taking too long. I hit the "ESC" key to read that " /dev/root could not be found ". See: https://bugzilla.novell.com/show_bug.cgi?id=853914 I proceeded with the DVD Rescue and typed: # fdisk -l mount /dev/sda1 /mnt mount --bind /dev /mnt/dev chroot /mnt mount /proc mount /sys grub2-install /dev/sda grub2-mkconfig -o /boot/grub2/grub.cfg umount /sys is busy or in use. umount /proc is busy or in use. umount /mnt # shutdown -r now The last two "mount" commands with /proc and /sys showed a message that "the file or directory was missing". After "grub2-mkconfig -o /boot/grub2/grub.cfg" I got an error on line info ........ I should have written it down . At the end, the first two "umount" commands indicated that they are "busy or in use". ------------------------------------------------------------------------------------------------------- I rebooted with the Live openSUSE Rescue disk, started the Yast Boot Loader and noticed the: "Optional Kernel Command Line Parameter" and "Failsafe Kernel Command Line Parameters"fields were empty. Is it possible that "mkinitrd" was missing the ide and ahci control driver modules? And should I have changed or replaced the last two grub2 commands with: mkinitrd grub2-install /dev/sda -- Cheers! Roman -------------------------------------------- openSUSE -- Get it! Discover it! Share it! -------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5