openSUSE Factory October 2019

factory@lists.opensuse.org

100 participants
86 discussions

[opensuse-factory] Have 32-bit builds changed requirements?

by Larry Finger

Hi, Since yesterday, the i586 builds of VirtualBox have begun failing with the following logged information: [ 183s] + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' --nosignature --define '_build_create_debug 1' --define 'disturl obs://build.opensuse.org/openSUSE:Factory/standard/ea6c140a96158796b77bfb1a…' /home/abuild/rpmbuild/SOURCES/pesign-repackage.spec [ 183s] rpmbuild: error while loading shared libraries: librpmbuild.so.8: cannot open shared object file: No such file or directory Has OBS changed, or is this just a transient problem? The package does not have this problem with local osc builds. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 year, 11 months

[opensuse-factory] Tumbleweed - Review of the week 2019/42

by Dominique Leuenberger / DimStar

Dear Tumbleweed users and hackers, Another week has passed with again four snapshots published. This pace seems to be holding pretty solid and I think it’s not the worst speed there is. During this week, we have released the snapshots 1011, 1012, 1014 and 1016. As usual, some were smaller, some were bigger. The changes include: * GStreamer 1.16.1 * Linux kernel 5.3.5 * KDE Plasma 5.17.0 * KDE Frameworks 5.63.0 * KDE Applications 19.08.2 * LLVM 9.0 (added to the repo, but not yet the default llvm version in use) The staging areas (and the next snapshot in production) already contain some updates again. Those include: * GNOME 3.34.1 (finally!) * Kubernetes 1.16 * Mesa 19.2 * openssl 1.1.1d: breaks nodejs8, nodejs10 and python3 * More work to support /usr/etc * LLVM 9.0 as the default when using llvm Besides all this, I’d like to bring yout attention to a change done to the setup of the openSUSE:Factory/snapshot build target. You can read all the needed information in the post published on the Factory mailing list at https://lists.opensuse.org/opensuse-factory/2019-10/msg00142.html Cheers, Dominique

1 year, 11 months

[opensuse-factory] no response on SR#736237

by Cor Blom

Hi, I have submitted a request to improve the DMZ cursors in the Plasma DE almost two weeks ago. Some kind of response would be nice, even if it's just: we don't want this. https://build.opensuse.org/request/show/736237 Thanks, Cor -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 year, 11 months

[opensuse-factory] Tumbleweed QEMU 3.1x and 4.1 problems

by Frans de Boer

LS, I tried to use Qemu 4.1. under Tumbleweed, but the client does not get an IP address. Compiled it myself, same result. Tried to compile Qemu 3.1 series, but all failed during compile with the message: (loadable library and perl binaries are mismatched (got handshake key 0xde00080, needed 0xce00080) Compiling and using the 3.1.x and 4.1 version under Opensuse 15.1 is no problem. Except when using 4.1 and wanting to use spice where there is only a very old version available under 15.1. So, the problem must be in the Tumbleweed distribution, which somehow blocks Qemu 4.1 networking or disallows compiling Qemu 3.1 series. Suggestions? Regards, Frans -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 year, 11 months

[opensuse-factory] openSUSE Leap 15.2 start of development

by Ludwig Nussel

Hi, After the release is before the release. So engines for 15.2 are on already. It builds, passes openQA and even released the first iso image to download.opensuse.org¹ last week. As usual you can find the sources in openSUSE:Leap:15.2 in OBS². The project is in a very early stage so it's not much more than 15.1 + updates yet. 15.2 again will be a service pack like update in the 15 series of Leap. As such by default packages will *not* be updated to Factory versions automatically and it's discouraged to drop packages. The core packages will be inherited automatically from SLE15SP2 that also started development recently. From what we know already we will get version updates for the Kernel, GNOME and Qt from SLE. If you think a package you take care of needs to be updated, please check whether the package is inherited from Factory or SLE. If it's from Factory submit manually once to let the tools know to follow Factory. If the package is from SLE please file a bug report and/or get in touch with the maintainer on SLE side ASAP. Updates for packages coming from SLE need to be evaluated this year still to have a chance. Note that despite some version updates in core components we do not aim at providing the latest and greatest of everything in Leap 15. So no batch updates please! cu Ludwig [1] http://download.opensuse.org/distribution/leap/15.2/iso/ [2] https://build.opensuse.org/project/dashboard/openSUSE:Leap:15.2 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Mary Higgins, Sri Rasiah, HRB 21284 (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

1 year, 11 months

[opensuse-factory] kmail problem after Tumbleweed snapshot 20191014

by Cons Brouerius van Nidek

After the update with zypper dup I was left with a non working kmail. The information after using the konsole to start kmail was: kmail: symbol lookup error: /usr/lib64/libKF5ContactEditor.so.5: undefined symbol: _ZN9KContacts9Addressee16staticMetaObjectE No further explanation. Other kmail users with the same problem? Solutions, anybody? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 year, 11 months

[opensuse-factory] Upgrade tests from Leap 42.3 to Tumbleweed were using an old disk image without latest updates

by Sergio Lindo Mansilla

Hi all, I am working on https://progress.opensuse.org/issues/39305 I have succesfuly create the qcow2 images with Leap 42.3 + latest updates to be use for upgrade scenarios to Tumbleweed: - GNOME: https://openqa.opensuse.org/tests/1056940 - HDD_1: opensuse-42.3-x86_64-GM-latest-updates-gnome(a)64bit.qcow2 - KDE: https://openqa.opensuse.org/tests/1056103 - HDD_1: opensuse-42.3-x86_64-GM-latest-updates-kde(a)64bit.qcow2 - KDE+system_performance: https://openqa.opensuse.org/tests/1055618 - HDD_1: opensuse-42.3-x86_64-GM-latest-updates-kde(a)64bit.qcow2 I am having the problem of the /var directory being yet included in the BTRFS root module and therefore taking a lot space on the upgrade snapshots. For kryptlvm scenarios those symptoms cause the test to fail on matching needles, since notification of "Low Disk Space.." are shown sporadically during the test. The disk images are using 40GB. I have two ideas to avoid this problem. One is increasing the disk image up to 50GB for those two specific scenarios "Leap 42.3 + cryptlvm upgrade to Tumbleweed, 64bit (BIOS/legacy) or UEFI": - https://openqa.opensuse.org/tests/1055631#step/first_boot/2 - https://openqa.opensuse.org/tests/1055632#step/first_boot/2 That would mean that the recommended hard disk size to upgrade from Leap 42.3 to Tumbleweed would be 50GB. Anyway, I would recommend to anyone having the old BTRFS partition schema (pre-Leap15) to perform a new installation with the new partitioning schema, since the old one will still give a lot of space problems. Here is a verification run using a 50GB virtual disk: - https://openqa.opensuse.org/tests/1058471 The other solution would be to delete the upgrade snapshot with snapper on the test module first_boot, and perform the "cleanup BTRFS tasks" to free the space. Any opinion on that? Are you ok with using 50GB for those and only those two specific scenarios? Kind Regards -- Sergio Lindo Mansilla <slindomansilla(a)suse.com> QA Engineer SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nürnberg Germany https://www.suse.com/ (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer

1 year, 11 months

[opensuse-factory] kdesu broken and mc error on bash startup on TW 20191014

by Maximilian Trummer

I've been directed here so I'll repost this from opensuse-support: After upgrading to Tumbleweed 20191014, I'm getting this message whenever I start a bash session: >bash: mc: line 1: syntax error: unexpected end of file >bash: error importing function definition for `mc' It seems to be a problem with the file /etc/profile.d/mc.sh mc is installed from the main OSS repo. I don't have any "weird" repos installed either, my activated ones are: Packman games network:vpn:wireguard repo-debug repo-non-oss repo-oss repo-update Also, kdesu doesn't function anymore, see https://bugzilla.opensuse.org/show_bug.cgi?id=1154342 Interestingly, both issues appeared together after an upgrade, just like for this user here https://forums.opensuse.org/showthread.php/537708-Weird-behaviour-after-zyp… and it affects other TW users too https://forums.opensuse.org/showthread.php/537708-Weird-behaviour-after-zyp…

1 year, 11 months

[opensuse-factory] The "GROUP" tag is still in Fedora rpms

by Dave Plater

I've noted the argument that Fedora have dropped the group tag so I decided to download an FC30 rpm and inspect it, it still contains the GROUP tag but it is set to unspecified. I'm really curious as to why removing the group tag is so important? I've seen reasons why Yast doesn't use it anymore but the Package-group section is nearly useless for package selection, why remove something that can be parsed by third party applications that does no harm and the way that removal is being performed creates a lot of extra work for unpaid maintainers. I haven't yet seen a reason why there is a need to remove the group tag in such a hurry. Thanks Dave Plater -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 year, 11 months

[opensuse-factory] Please stop the Group Tag fight on packagers back!

by Thorsten Kukuk

Hi, please stop the Group Tag War on the back of the packagers! Since one side escalated this to the board, I think the other side should escalate the same from the oppsite now. It's really a stupid idea to escalate something and then do something similar. Especially that Jan Engelhardt is changing the packaging policy in the openSUSE wiki without anouncing it on the packagers mailing list and let them comment it for two weeks, but change the packages of other people immeaditly! https://en.opensuse.org/openSUSE:Packaging_guidelines_change_process I cannot find such a RFC on the packaging mailing list and I cannot find a two week long discussion. And it's only allowed to change the wiki if there are no strong objections, but as the discussion here shows, there are strong objections for all variants! Let the package maintainers decide if they want the Group tags or not. If that concept would work, they will choose one. If there is no working concept, they will remove it. Quite simple. For me: as long as there are no useful Group Tags for my packages and no working concept, I will not accept SRs which add wrong or misleading Group Tags to my packages only to make here one person happy. And I will not accept SRs with changes not following our openSUSE guidelines. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, 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

1 year, 11 months

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

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory October 2019