openSUSE Factory December 2012

factory@lists.opensuse.org

87 participants
90 discussions

[opensuse-factory] Current Factory Status

by Bernhard M. Wiedemann

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, current Factory status is still poor as seen in openQA.o.o results of recent weeks. Inspite of popular belief, this has little to do with KVM's cirrus graphics, but rather with https://bugzilla.novell.com/show_bug.cgi?id=790424 hitting all DVD/NET installs since 2012-10-26, https://bugzilla.novell.com/show_bug.cgi?id=790724 hitting all LVM installs since 2012-11-06 and LiveCD installs slightly suffering from https://bugzilla.novell.com/show_bug.cgi?id=793065 I'd consider the first two to be blockers which should be fixed before the next Milestone. Ciao Bernhard M. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDAJ1cACgkQSTYLOx37oWQLGACg+f4HmQycbIjHGPnKD2+8RJgG CT0AmgLAiZOJzBZWhb1CuoBVy14EXEIM =aH/u -----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

9 years, 6 months

[opensuse-factory] mysql-community-server

by Nelson Marques

https://bugzilla.novell.com/show_bug.cgi?id=792669 Anyone can point me the correct way so I can prepare an update to fix this annoying issue? NM -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] build time verification of GPG signatures

by Stanislav Brabec

Hi. As discussed in past[1], Factory now has gpg-offline package, which is a wrapper on top of gnupg, which allows simple build time offline verification of GPG signatures. It makes possible to verify tarballs in the build time. The use of gpg-offline in spec files is really simple: https://build.opensuse.org/package/view_file?expand=1&file=gpg-offline.PACK… The package also contains a man page. The first time step is very security-sensitive: You define your package keyring - a list of trusted keys, that can be used by the upstream to sign the source of your package. Check carefully that you are not adding a malicious keys there. Be paranoid! The gpg_verify tool is able to detect hacked source on the upstream servers (and such bad thing really already happened[2]!), but it is not able to detect maliciously uploaded false signature on the key servers. If the upstream author is in your web of trust, you are on a safe side. But if he/she is not in your web of trust, you have to use alternative ways to trust the key: - If you can mail to the author and verify the key, it is very probably an authorized signature. - If the signing key is the same as the one used a year ago, it is probably an authorized signature. - If the signing key was used in mailing list many times to sign developer mails, or at least it was announced there, it is probably an authorized signature. - If you can find the public key or footprint on more servers on different hostings, it is probably an authorized signature. I just implemented signature verification for all packages, that already contained signature and/or trusted keyring. But I did not verify, that signature submitted by packagers is the signature of the real author. Feedback, feature requests and bug reports are welcome. [1] http://lists.opensuse.org/opensuse-packaging/2012-09/msg00029.html [2] http://scarybeastsecurity.blogspot.cz/2011/07/alert-vsftpd-download-backdoo… There is still one FIXME: If anybody knows, how to use trust model "all keys in the local keyring are trusted" without "gpg: WARNING: Using untrusted key!", please advise. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +49 911 7405384547 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] SR 144031 stuck in factory-auto review waiting for its own packages

by Peter Trommler

SR 144031 is currently stuck in review for factory-auto with the following comment: > please make sure to wait before these depencencies are in openSUSE:Factory: ghc-array, ghc-base, ghc-haskell98, ghc-filepath, ghc-old- locale, ghc-old-time, ghc-directory, ghc-time, ghc-containers, ghc-process, ghc-deepseq, ghc-unix None of those packages mentioned are "BuildRequires" for ghc (yet) but they will be created as a result of that package's build (and only then the respective *-devel packages will require those packages). My previous SR was stuck for almost two weeks before I re-submitted an SR with the conditional dependecies removed. Can someone please unblock SR 144031 and move it on to the next review stage? Finishing this SR is the final step to have a working Haskell compiler (ghc) in Factory. Thanks, Peter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] long delay in factory AppArmor builds

by Christian Boltz

Hallo, I noticed a long delay (several minutes) in factory builds in the AppArmor package. Builds for Tumbleweed and released openSUSE versions do not have this delay. Can someone please check this and give me a hint what could be wrong? Full build log: https://build.opensuse.org/package/rawlog?arch=i586&package=apparmor&projec… relevant part: (note the long delay between 159s and 1168s) [ 159s] pam-devel-1.1.6-2.1 ######################################## [ 159s] pam-config-0.84-1.1 ######################################## [ 159s] *** write_config (account, /etc/pam.d/common-account-pc, ...) [...] [ 159s] **** write config for pam_ecryptfs.so (session, disabled) [ 159s] **** write config for pam_env.so (session, enabled) [ 1168s] removing nis flags from //etc/nsswitch.conf... [ 1168s] now finalizing build dir... [ 1168s] /usr/sbin/Check is obsolete, don't call it! [ 1168s] mktexlsr: Updating /etc/texmf/ls-R... [ 1169s] mktexlsr: Updating /var/lib/texmf/main/ls-R... [ 1169s] mktexlsr: Updating /var/lib/texmf/dist/ls-R... [ 1169s] mktexlsr: Updating /var/cache/texmf/fonts/ls-R... [ 1169s] mktexlsr: Updating /var/lib/texmf/ls-R... [ 1169s] mktexlsr: Done. The delay doesn't seem to be constant - for example, AppArmor in my home project builds "faster": https://build.opensuse.org/package/rawlog?arch=x86_64&package=apparmor&proj… [ 182s] **** write config for pam_ecryptfs.so (session, disabled) [ 182s] **** write config for pam_env.so (session, enabled) [ 881s] removing nis flags from //etc/nsswitch.conf... [ 881s] now finalizing build dir... Regards, Christian Boltz -- wodim is based on a cdrecord from September 2004 with additional bugs added by Debian and with the DVD support code ripped off and replaced by something that works on weekends wit full-moon. [Jörg Schilling in opensuse-factory] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] Re: Why does MS-Windows need no "initrd-equivalent" in order to boot w/a wider range of x86[-64] compat HW?

by Linda Walsh

Philipp Thomas wrote: > For the umteentht time: STOP the stupid cross posting and make up your > mind as to where to discuss this. ---- You tell me where it belongs. It's about Suse 12.2 and suse 12.3 and beyond. Last person I asked which list I should shut out of the discussion, I got no answer, so what's your answer. > >> Windows doesn't need extra disks / drivers to be pre-loaded >> unless you are booting from a rescue disk/installation disk. > > You have followed the links to the Wikipedia articles describing the > boot mechanisms in various Windows versions that David posted > yesterday? ==== Why should I? I've read the Windows system internal's book written by a Windows "Fellow", that describes the process in considerably more detail in chapter 13. Maybe you should read the book 'Windows System Internals (5th ed). It tells you why -- boot sector loads a basic device aware booter like lilo, that can then boot images off of any of windows devices... None of them require an initrd. Any other questions? I had stopped cross posting the past several posts, but you seemed to be a case-in-point of not getting the fact that if it was NEVER appropriate to cross post, it could be blocked for everyone at the list-reflector. If it is the case that it is appropriate at times -- then what about a cross-topic subject like this isn't appropriate - what would be an example of something that would be if this isn't? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] Tumbleweed: Gnome 3.6

by Joachim Bremer

Hi all, on my system I had a small problem on upgrading. System is 64-bit. The installed libgtk-3-0-32bit-3.6.2-3.4.x86_64 needs libatk-bridge-2_0-0-32bit-2.6.2-3.1.x86_64 which in turn needs libatspi.0-2.6.2-3.1 - which not exist and I think never existed - at least not in Gnome 3.4. I had to ignore that and everything else works fine so far. Thanks Joachim -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] Nvidia now requires devel packages ?!

by Daniele

Hi, I don't know if this is a packaging bug but: Loading repository data... Reading installed packages... Computing distribution upgrade... The following NEW packages are going to be installed: gcc gcc47 glibc-devel kernel-default-devel kernel-devel linux-glibc- devel The following packages are going to be upgraded: nvidia-computeG02 nvidia-gfxG02-kmp-default x11-video-nvidiaG02 3 packages to upgrade, 6 new. Overall download size: 43.3 MiB. After the operation, additional 64.3 MiB will be used. Continue? [y/n/?] (y): n Why gcc and *-devel for binary driver ? bug/change/something for next opensuse ?! -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] snapper snapshot comparison algorithm

by nafisa mandliwala

Hello, I wanted to know what algorithm snapper uses for snapshot comparison? From what I have interpreted from the code, it first compares metadata and then does a block by block compare using 'memcmp'. I also wanted to know how the directories are 'diff'ed and if there is a scope of improvement in the current implementation. Also, if anyone has taken it up yet. Thank you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

[opensuse-factory] jdk6

by Hans Witvliet

Hi all, can somebody explain why java-1_6_0-openjdk-1.6.0 been removed from the OBS for OS_12.2? It is still there for OS_11.4, OS_12,1 and even sles11_sp2. (repo/Java:/openjdk6:/) Reason for asking is a comment from a developper: "All distros still have OpenJDK 6, but offer OpenJDK 7 as well. So you have to select the right packages. JBoss 5 does not work with java 7." Hans. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 years, 7 months

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

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory December 2012