November 2014 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Concerning the release cycle, some ideas for refinement.
by Roger Luedecke 21 Nov '14

21 Nov '14

Poll on Google plus with over 1200 respondents shows 89% of our users support an annual release cycle. https://plus.google.com/110312141834246266844/posts/g5FdGJ9iSqB I think we should however restructure the way we do releases in order to minimize the bumpiness of release. I propose a pseudo-annual release cycle. The idea being that our current state of release is messy at best and could use some last minute repository fixing and bug swatting. I propose that we esentially make the way we release now 'open-beta' at the 11th month. We then use the 12th month to get all repos online and fixed. Also would be a good chance to give us about a month to fix problems with our disc images, and remaster the 'open-beta' 11th month GM with patches and hardware support fixes. With this scheme we should see much smoother official release days by essentially duping the users into considering the state we currently call release to be beta, and giving us a month to clean things up. I hope my idea was clear, I am having trouble explaining the idea. -- Roger Luedecke openSUSE Project Member and Advocate since 2011 http://www.opensuseadventures.blogspot.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

15 49

[opensuse-factory] [Fwd: Re: [opensuse-project] Handling of openSUSE "paper-cut" issues] insane recommends/dependencies
by Roger Luedecke 20 Nov '14

20 Nov '14

-------- Forwarded Message -------- > From: S. <sb56637(a)gmail.com> > To: opensuse-project(a)opensuse.org > Subject: Re: [opensuse-project] Handling of openSUSE "paper-cut" > issues > Date: Thu, 20 Nov 2014 08:09:59 -0500 > > Regarding openSUSE paper-cut issues, another 13.2 review appeared in > Spanish on openSUSE Planet: > http://www.lasombradelhelicoptero.com/2014/11/opensuse-132-cosas-que-mejora… > > The reviewer starts by saying that he likes openSUSE and doesn't want to > bash it, in fact he had declared 13.1 to be the best Linux distro he had > reviewed to date. But he had quite a few issues with 13.2. > > Regarding installation of extraneous packages, notice what happened when > he installed Spanish language packages: > http://3.bp.blogspot.com/-YxAPbyJJ7Wo/VGtnX4b23wI/AAAAAAAAFTw/x0XQpKsE-Xc/s… > In his screenshot, I can see the additional dependencies, including > Sane, Skanlite, Synaptiks, tcpdump, telnet, unrar, and a whole plethora > of mostly unrelated packages. He says that step pulled in a sizable > 500MB of packages, when all he wanted was some small languages packs. > The glut of packages that are pulled in after the initial installation > continues to create a bad impression on almost every review I've read of > openSUSE to date. I think that the recommended packages for already > installed packages option should be disabled by default, and those > "pullin-this-or-that" updater packages should also be eliminated. > > The reviewer also ran into the codecs difficulty. He mentions: > "Something that I know by experience which a novice user has no way of > knowing is that due to license issues openSUSE does not incorporate > hardly any multimedia codecs that are usually employed. However, Ubuntu > doesn't include them either, but this is not an obstacle to a better > multimedia experience thanks to a the simple checkbox during > installation. This is, in my opinion, the main defect of openSUSE, > easily remedied if one knows a bit about the distro or by reading > articles to the tune of 'What to do after installing...' But I try to > look at it from the perspective of a less experienced user, who after > trying to open a video sees a Kaffeine message that warns about needing > to search for 'codecs'. This takes us to YaST, where we have to choose > an option to add community repositories, which then takes us to a list > of sites whose names, sometimes in English, do not make at all clear > which of them to enable or which packages to install. And the worse of > it: after adding Packman, Main OSS and Non-OSS, the result is the same: > No codecs are found to play the file. Where is the problem? Well, the > addition of these repositories will activate a series of packages that > will be installed as recommends in YaST, something that an inexperienced > user is completely unfamiliar with." > > I think he stated the point very well from the viewpoint of a normal > user. The comparison with Ubuntu is perhaps a bit wearisome for the > openSUSE devs, but it's definitely the elephant in the room here. Any > thoughts? > -- > To unsubscribe, e-mail: opensuse-project+unsubscribe(a)opensuse.org > To contact the owner, email: opensuse-project+owner(a)opensuse.org > -- 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] LXDM 0.5.0 Startup issue in Factory
by Dominique Leuenberger a.k.a. Dimstar 19 Nov '14

19 Nov '14

Hi all, It seems we have (again) an issue with LXDE/LXDM in Factory, which blocks us from publihsing it without breaking existing systems using LXDM As you can see in the various tests * https://openqa.opensuse.org/tests/32620/modules/first_boot/steps/1 * https://openqa.opensuse.org/tests/32638/modules/first_boot/steps/1 * https://openqa.opensuse.org/tests/32583/modules/first_boot/steps/1 * https://openqa.opensuse.org/tests/32597/modules/first_boot/steps/1 LXDM seems not to to be starting up at all since the upgrade to 0.5 (or maybe on the wrong VT?) Can I please get a fix from the LXDE Maintainers to get this corrected ASAP? Also, please ensure packages are tested/working prior to submitting them to Factory/Tumbleweed. We are targetting to publish the tree often, but this requires that we get packages passing the test suites. Thanks for your great help and I'm looking forward to get a fix soon. Dominique -- 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] A suggestion for partitioning.
by James Knott 19 Nov '14

19 Nov '14

One difference I noticed between 13.1 and 13.2 is where to find importing partitions. In 13.1 it's on the same list with other options. In 13.2, you have to select Expert, before you see the option to import. This makes it more difficult for a less experienced person to install on a fresh system. So, please move it back to where it was and belongs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 22

[opensuse-factory] Tumbleweed tries to access to wrong update repo
by Jan Papež (honyczek) 19 Nov '14

19 Nov '14

6 10

[opensuse-factory] ATTENTION lxc users on Tumbleweed: creating a container deletes packages on the host (sic!)
by Johannes Kastl 19 Nov '14

19 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everyone, I hope I am wrong and this is not how it looks. Since I upgrade two of my machines to the new tumbleweed, lxc starts to delete packages on the *host* during creation of openSUSE containers. (sic!). I am digging into it right now, but it seems to be the build call in the lxc-opensuse template: > CLEAN_BUILD=1 BUILD_ARCH="$arch" BUILD_ROOT="$cache/partial-$arch" > BUILD_DIST="$cache/partial-$arch-packages/opensuse.conf" > PATH="$PATH:/usr/lib/build" /usr/lib/build/init_buil\ dsystem > --clean --configdir /usr/lib/build/configs --cachedir > $cache/partial-$arch-cache --repository > $cache/partial-$arch-packages/var/cache/zypp/packages/repo-oss/suse/$arch > --repository > $cache/partial-$arch-packages/var/cache/zypp/packages/repo-oss/suse/noarch > > - --repository $cache/partial-$arch-packages/var/cache/zypp/packages/update/$arch > --repository > $cache/partial-$arch-packages/var/cache/zypp/packages/update/noarch > > || return 1 This outputs the following, and then starts to delete packages on the host. Not in the container. http://susepaste.org/77400215 On one machine it starts by deleting a2ps, on the other (yesterday) it started with Mesa. Can someone please prove me that this is not related to tumbleweed, but is only my fault or a misconfiguration on my machine? (Keeping a list of installed rpms at hand is a very good idea...) Regards, Johannes - -- `Even if I could, I wouldn't. Scars can come in useful. I have one myself above my left knee which is a perfect map of the London Underground.´ (Albus Dumbledore, Harry Potter I) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlRmHbgACgkQzi3gQ/xETbIYEgCfTR/Q4QaY8cXkk2rYkC0pgc8E ZF0AoJb9iyrugerzdFNZSmY5JIzr4l2r =UcMS -----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

2 10

[opensuse-factory] TW : kernel-desktop-3.17.2-1.2.x86_64
by ellanios82 18 Nov '14

18 Nov '14

Hello List , TW : kernel-desktop-3.17.2-1.2.x86_64 : - in case of interest : boot process comes to a halt, and sticks at "start job running for udev" .............. [ booted without probs on kernel-desktop-3.16.4-1.6.g7a8842b.x86_64 ] ............... regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3

[opensuse-factory] [Tumbleweed] kernel-pae-3.17.1
by Achim Gratz 17 Nov '14

17 Nov '14

I've had my machine hanging on shutdown from KDE with a blank screen (mouse cursor still visible) and dead mouse and keyboard, right at the point where you'd normally be switched back to the console. Before the keyboard went out there was a bit of disk activity that I don't remember at that point in the shutdown sequence. Hard reset would then end up clearing four or five inodes on the root partition. By some luck I managed to switch to the console once right before the hang and was then greeted by a "soft lockup" message from the kernel that was repeating every 22 seconds or so (the kernel seemed to be stuck in some page fault handler and a second routine that I have no clue about). This is only happening after I've used KDE for quite a while, so if I just log into KDE, start all my applications and then do an immediate shutdown it never happens, so it is quite hard to drill to the bottom of this. I've done some more experimentations and found that this is only happening with the 3.17.1 kernels, but not with the 3.16.3 which I've now rolled back to. I'm AFK for the next few days, but maybe someone else might have an idea what's going on. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- 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] Current snapshot failing
by Stephan Kulow 17 Nov '14

17 Nov '14

Hi, Something broke lxde again - it fails independent of the media: opensuse-Tumbleweed-KDE-Live-x86_64-Build-kde-live@USBboot_64 https://openqa.opensuse.org/tests/32671 zypper_ref 3 opensuse-Tumbleweed-DVD-x86_64-Build-gnome@Laptop_64 https://openqa.opensuse.org/tests/32659 livecdreboot 3 opensuse-Tumbleweed-DVD-x86_64-Build-lxde@64bit https://openqa.opensuse.org/tests/32638 first_boot 3 opensuse-Tumbleweed-DVD-i586-Build-install_only@smp_32 https://openqa.opensuse.org/tests/32627 first_boot 3 opensuse-Tumbleweed-DVD-i586-Build-lxde@32bit https://openqa.opensuse.org/tests/32620 first_boot 3 opensuse-Tumbleweed-NET-x86_64-Build-uefi-os@64bit https://openqa.opensuse.org/tests/32609 partitioning 3 opensuse-Tumbleweed-NET-x86_64-Build-lxde@64bit https://openqa.opensuse.org/tests/32597 first_boot 3 opensuse-Tumbleweed-NET-i586-Build-lxde@32bit https://openqa.opensuse.org/tests/32583 first_boot 3 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

1 0

[opensuse-factory] Usage of gpg_verify in .spec files
by Dimstar / Dominique Leuenberger 16 Nov '14

16 Nov '14

Hi geeko packagers, Please note that we are receiving a new version of gpg (2.1.0) in Factory probably rather soon... One thing to note is that the current version of %gpg_verify passes --gpg2 to the command, which is no longer understood. There are obviously two ways to fix it: - Fix %gpg_verify to no longer pass --gpg; surely simple, but I don't prefer the solution - Remove the gpg_verify commands from the .spec files; In fact, usage of gpg_verify has been deprecated in favor of the obs service source_validator (which runs at each osc ci call or you can call it using osc service lr source_validator). As we already have implicit verification of the signatures there, it is of no use to verify the signature during build again. Which is also the reason why option one is not that appealing. Can I please ask the package maintainers to work with us and eliminate this wherever it is still used in Factory? Thanks a lot! -- Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 9