[Test-Announce] Fedora 30 Rawhide 20190211.n.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora 30 Rawhide 20190211.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki

Re: Orphaned packages to be retired

Dne 11. 02. 19 v 4:33 Jens-Ulrik Petersen napsal(a): > On Tue, Feb 5, 2019 at 4:27 AM Miro Hrončok > wrote: > > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you > know for sur

Re: Retiring perl-perlmenu

* Emmanuel Seyman [29/01/2019 00:35] : > > I maintain perl-perlmenu in Fedora and I will be retiring it at the end > of the week unless someone offers to maintain it instead. Tha package has been retired. Emmanuel ___ devel mailing list -- devel@lists.

Re: signing status

Hi, On 08-02-19 17:41, Kevin Fenzi wrote: Just wanted to update everyone on our current status. As you know from the other thread: * The mass rebuild happened and finished. * The mass rebuild side tag was merged into the f30-pending tag (to make sure everything was signed). * In the middle of

Re: Lazarus 2.0 release - push to Rawhide or wait?

Thx. The DoubleCmd builds and runs just fine. Vít Dne 08. 02. 19 v 22:10 Artur Iwicki napsal(a): > I've made a COPR repo so you can test if your packages build ok. > https://copr.fedorainfracloud.org/coprs/suve/lazarus-2.0/ > ___ > devel mailing list

Re: gcc-c++ and libatomic -- link issues

On 08/02/19 19:56 -0600, Patrick Diehl wrote: Hi, I maintain the hpx package and it uses std:atomic and when I install gcc-c++ it seems that libatomic is not a dependency of the gcc-c++ package. My program fails, because it can not link against libatomic. Is this the supposed behavior to install

Re: signing status

On Sun, 2019-02-10 at 09:02 -0800, Kevin Fenzi wrote: > On 2/10/19 8:01 AM, Sérgio Basto wrote: > > On Sat, 2019-02-09 at 10:33 -0800, Kevin Fenzi wrote: > > > On 2/9/19 2:00 AM, Miro Hrončok wrote: > > > > On 08. 02. 19 17:41, Kevin Fenzi wrote: > > > > > Just wanted to update everyone on our curr

Re: compilation of mellowplayer fails on Fedora 30 with gcc-9.0.1 - error: redundant move in return statement [-Werror=redundant-move]

On 07/02/19 11:26 +0100, J. Scheurich wrote: the compilation of mellowplayer-3.5.1 with gcc-9.0.1 fails on Fedora 30, see the build.log [1] Fedora Bugzilla [2] - -Wredundant-move gives false positives in C++11 mode This is not a false positive. Just because GCC *sometimes* gives false positive

Re: gcc-c++ and libatomic -- link issues

* Jonathan Wakely: > On 08/02/19 19:56 -0600, Patrick Diehl wrote: >>Hi, >> >>I maintain the hpx package and it uses std:atomic and when I install >>gcc-c++ it seems that libatomic is not a dependency of the gcc-c++ >>package. My program fails, because it can not link against libatomic. Is >>this

Re: gcc-c++ and libatomic -- link issues

On Mon, Feb 11, 2019 at 12:14:10PM +0100, Florian Weimer wrote: > * Jonathan Wakely: > > > On 08/02/19 19:56 -0600, Patrick Diehl wrote: > >>Hi, > >> > >>I maintain the hpx package and it uses std:atomic and when I install > >>gcc-c++ it seems that libatomic is not a dependency of the gcc-c++ > >>

Re: gcc-c++ and libatomic -- link issues

On 11/02/19 12:14 +0100, Florian Weimer wrote: * Jonathan Wakely: On 08/02/19 19:56 -0600, Patrick Diehl wrote: Hi, I maintain the hpx package and it uses std:atomic and when I install gcc-c++ it seems that libatomic is not a dependency of the gcc-c++ package. My program fails, because it can

Fedora Rawhide-20190211.n.0 compose check report

Missing expected images: Atomichost raw-xz x86_64 Atomichost qcow2 x86_64 Compose FAILS proposed Rawhide gating check! 27 of 47 required tests failed, 17 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could n

Re: compilation of mellowplayer fails on Fedora 30 with gcc-9.0.1 - error: redundant move in return statement [-Werror=redundant-move]

The developer has already fixed the warnings in the new version 3.5.2. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduc

Re: F30 change, bootloaderspec by default

Le 2019-02-10 20:05, Chris Murphy a écrit : On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas Between this feature for F30, and the F29 feature to hide the grub menu which comes with boot success+fail marking by using the grubenv, there are substantial changes in bootloading on Fedora th

Re: MBI (Playground 2.0)

On Sun, Feb 10, 2019 at 5:18 PM Stephen John Smoogen wrote: > > On Fri, 8 Feb 2019 at 16:00, Stephen John Smoogen wrote: > > > > On Fri, 8 Feb 2019 at 14:31, Adam Williamson > > wrote: > > > > > > On Thu, 2019-02-07 at 12:21 -0500, Stephen John Smoogen wrote: > > > > On Thu, 7 Feb 2019 at 09:40

Re: Policy regarding service preset enabled (e.g. performance co-pilot)

On Sun, Feb 10, 2019 at 4:40 AM Georg Sauthoff wrote: > > Hello, > > On Sun, Feb 10, 2019 at 10:08:51AM +1100, Nathan Scott wrote: > > On Sun, Feb 10, 2019 at 6:47 AM Georg Sauthoff wrote: > > > [...] > > > I'm asking because installing the dstat replacement[1] in Fedora 29 > > > resulted in 3 ad

Re: F30 Self-Contained Change proposal: Bash 5.0

On Mon, Feb 11, 2019 at 3:30 AM Neal Gompa wrote: > > On Sun, Feb 10, 2019 at 9:22 PM Dridi Boukelmoune > wrote: > > > > > I don't read repodata manually, libsolv does it for me. Using libdnf > > > and/or libmodulemd is not something what (for example) OBS would do. They > > > rely on libsolv f

Re: MBI (Playground 2.0)

Le 2019-02-11 13:51, Fabio Valentini a écrit : Either I am unreasonably unlucky, or your statistics are wrong: Looking at [0], 35 of the last 44 build tasks failed due to network issues (not counting all sub-tasks), which is about 80%. You're not unreasonably unlucky, and the stats are not wro

Re: Policy regarding service preset enabled (e.g. performance co-pilot)

On Mon, Feb 11, 2019 at 07:53:57AM -0500, Stephen Gallagher wrote: > On Sun, Feb 10, 2019 at 4:40 AM Georg Sauthoff wrote: > > On Sun, Feb 10, 2019 at 10:08:51AM +1100, Nathan Scott wrote: > > > On Sun, Feb 10, 2019 at 6:47 AM Georg Sauthoff wrote: > > > > [...] > > > > I'm asking because install

Schedule for Monday's FESCo Meeting (2019-02-11)

Following is the list of topics that will be discussed in the FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2019-02-11 15:00 UTC' Links to all issues to be

F30 change: update mercurial to version 4.9

I'm proposing to update to mercurial 4.9 for F30. The following packages are reported by dnf repoquery --whatrequires to depend on mercurial: git-cinnabar-0:0.5.0-1.fc29.x86_64 git-remote-hg-0:0.3-9.fc29.noarch gitifyhg-0:0.8.4-11.fc29.noarch golang-bin-0:1.11-1.fc29.x86_64 golang-bin-0:1.11.5-1.

Agenda for Tuesday's Modularity Team Meeting (2019-02-12)

Find below a list of topics which are planned to be discussed in the Fedora Modularity Team meeting on Tuesday at 15:00 UTC in #fedora-meeting-3 on irc.freenode.net. To find out when this is in your local time zone, check the Fedora Calendar (if you've set it and are logged in): https://apps.fed

Re: signing status

On Sun, 10 Feb 2019 at 21:17, Kevin Fenzi wrote: > Just wanted to update everyone on our current status. > > As you know from the other thread: > > * The mass rebuild happened and finished. > Is there anywhere some summary stats about mass update? How many packages has been sent to rebuild vs th

Summary/Minutes from today's FESCo Meeting (2019-02-11)

= #fedora-meeting-1: FESCO (2019-02-11) = Meeting started by jforbes at 15:00:14 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2019-02-11/fesco.2019-02-11-15.00.log.html . Meeting s

Re: Fedora Rawhide-20190211.n.0 compose check report

On Mon, 2019-02-11 at 11:44 +, Fedora compose checker wrote: > Missing expected images: > > Atomichost raw-xz x86_64 > Atomichost qcow2 x86_64 > > Compose FAILS proposed Rawhide gating check! > 27 of 47 required tests failed, 17 results missing > openQA tests matching unsatisfied gating requi

Re: rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

Hello, Florian, I don't see any problem in this. Even if an extension function receives a pointer to a local variable, it should be fine as long as the variable is up the stack. Should it be downwards, it is undefined behavior anyways, linked or not. Maybe I have just misunderstood, can you please

Re: Blocking criteria proposal for F30+: Printing

On Fri, Nov 16, 2018 at 7:18 PM Adam Williamson wrote: > > On Thu, 2018-09-20 at 08:33 -0400, Stephen Gallagher wrote: > > There was a bug[1] filed recently that indicated that printing was > > broken on certain printers. As a result of that discussion, it became > > apparent that there was no cri

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Mon, 2019-02-11 at 17:57 +0100, Miro Hrončok wrote: > The following packages require above mentioned packages: > (this is in fact so long that I've posted it to > https://churchyard.fedorapeople.org/orphans-2019-02-11.txt) It would be rather handy to get some sort of graph view, especially whe

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 11/02/2019 17:02, Adam Williamson wrote: On Mon, 2019-02-11 at 17:57 +0100, Miro Hrončok wrote: The following packages require above mentioned packages: (this is in fact so long that I've posted it to https://churchyard.fedorapeople.org/orphans-2019-02-11.txt) It would be rather handy to g

Re: Fedora Rawhide-20190211.n.0 compose check report

On Mon, Feb 11, 2019 at 08:56:30AM -0800, Adam Williamson wrote: > On Mon, 2019-02-11 at 11:44 +, Fedora compose checker wrote: > > Missing expected images: > > > > Atomichost raw-xz x86_64 > > Atomichost qcow2 x86_64 > > > > Compose FAILS proposed Rawhide gating check! > > 27 of 47 required

Re: Orphaned packages that will be retired (and everything will most likely burn)

I don't think you can generate graph... Because how would you display "Requires: (foo if bar)"? :) On Mon, Feb 11, 2019 at 6:11 PM Adam Williamson wrote: > On Mon, 2019-02-11 at 17:57 +0100, Miro Hrončok wrote: > > The following packages require above mentioned packages: > > (this is in fact so

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 11/02/19 17:57, Miro Hrončok wrote: > The following packages are orphaned and will be retired when they > are orphaned for six weeks, unless someone adopts them. If you know for > sure > that the package should be retired, please do so now with a proper reason: > https://fedoraproject.org/wiki/H

Re: rpmlint: library-not-linked-against-libc (parts of Python stdlib, after gcc 9)

* Marcel Plch: > Hello, Florian, > > I don't see any problem in this. > Even if an extension function receives a pointer to a local variable, > it should be fine as long as the variable is up the stack. Should it be > downwards, it is undefined behavior anyways, linked or not. > Maybe I have just

Re: [Test-Announce] 2019-02-11 @ 17:00 UTC - Fedora 30 Blocker Review Meeting

Hi, Adam, you should send these emails with more time prior the meeting, only now I read them. :-/ Kind regards, Silvia On Sun, 10 Feb 2019 at 18:00, Adam Williamson wrote: > # F30 Blocker Review meeting > # Date: 2019-02-11 > # Time: 17:00 UTC > # Location: #fedora-blocker-review on irc.fr

Re: F30 Self-Contained Change proposal: Retire YUM 3

On 2/5/19 1:37 PM, Randy Barlow wrote: > On Mon, 2019-02-04 at 09:56 -0600, Mátyás Selmeci wrote: >> What's the replacement? > > Bodhi switched from mash to pungi, and I think Bodhi might have been > the last thing using mash. The last thing _we_ use mash for. ;) There may be other users out the

Re: MBI (Playground 2.0)

On 2/10/19 3:09 AM, Fabio Valentini wrote: > > That's exactly my experience, as well. > > First I've put it off as "my internet connection being unreliable". > But, since almost everything works fine, but mock builds continue to fail > (mostly because of "Failed to synchronize cache for repo 'foo

Re: MBI (Playground 2.0)

On Mon, 2019-02-11 at 10:23 -0800, Kevin Fenzi wrote: > The repo issues seem to be our mirrorlist containers sometimes throwing > a 503 when they shouldn't. ;( This is made worse by dnf never retrying > them, so if it happens once thats it. We are investigating and trying to > fix whatever is causi

Re: signing status

On 2/11/19 3:10 AM, Martin Kolman wrote: > On Sun, 2019-02-10 at 09:02 -0800, Kevin Fenzi wrote: >> It crashed/died and the status didn't update. >> >> It's not still composing, it will just be stuck in started forever. ;( >> >> Yesterdays failed in an anaconda traceback on the kde live, so I am >

Re: MBI (Playground 2.0)

On 2/11/19 5:46 AM, Nicolas Mailhot wrote: > Le 2019-02-11 13:51, Fabio Valentini a écrit : > >> Either I am unreasonably unlucky, or your statistics are wrong: >> Looking at [0], 35 of the last 44 build tasks failed due to network >> issues (not counting all sub-tasks), which is about 80%. > > Y

Re: signing status

On 2/11/19 8:13 AM, Tomasz Kłoczko wrote: > On Sun, 10 Feb 2019 at 21:17, Kevin Fenzi wrote: > >> Just wanted to update everyone on our current status. >> >> As you know from the other thread: >> >> * The mass rebuild happened and finished. >> > > Is there anywhere some summary stats about mass

Re: MBI (Playground 2.0)

On 2/11/19 10:26 AM, Adam Williamson wrote: > On Mon, 2019-02-11 at 10:23 -0800, Kevin Fenzi wrote: >> The repo issues seem to be our mirrorlist containers sometimes throwing >> a 503 when they shouldn't. ;( This is made worse by dnf never retrying >> them, so if it happens once thats it. We are in

Re: MBI (Playground 2.0)

> I've filed > https://pagure.io/fedora-infrastructure/issue/7553 > to track this. FWIW: https://github.com/rpm-software-management/dnf/pull/1109 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fe

fedpkg push fails

I haven't done any fedora packaging work for some time. I tried to fix https://bugzilla.redhat.com/show_bug.cgi?id=1674789 today, but I get: fedpkg push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 threads Compressing objects: 100% (3/3), don

Re: fedpkg push fails

On Mon, 11 Feb 2019, Neal Becker wrote: I haven't done any fedora packaging work for some time. I tried to fix https://bugzilla.redhat.com/show_bug.cgi?id=1674789 today, but I get: fedpkg push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 thr

Re: fedpkg push fails

Scott Talbert wrote: > On Mon, 11 Feb 2019, Neal Becker wrote: > >> I haven't done any fedora packaging work for some time. I tried to fix >> https://bugzilla.redhat.com/show_bug.cgi?id=1674789 >> today, but I get: >> >> fedpkg push >> Enumerating objects: 5, done. >> Counting objects: 100% (5/5

Re: fedpkg push fails

On Mon, 11 Feb 2019, Neal Becker wrote: I haven't done any fedora packaging work for some time. I tried to fix https://bugzilla.redhat.com/show_bug.cgi?id=1674789 today, but I get: fedpkg push Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 4 thr

Re: Blocking criteria proposal for F30+: Printing

On Mon, Feb 11, 2019 at 9:58 AM Stephen Gallagher wrote: > > On Fri, Nov 16, 2018 at 7:18 PM Adam Williamson > wrote: > > > > On Thu, 2018-09-20 at 08:33 -0400, Stephen Gallagher wrote: > > > There was a bug[1] filed recently that indicated that printing was > > > broken on certain printers. As a

Re: F30 change: update mercurial to version 4.9

On Mon, Feb 11, 2019 at 09:19:08AM -0500, Neal Becker wrote: > I'm proposing to update to mercurial 4.9 for F30. What is the effect on those dependent packages? How many need adjustments? Zbyszek > > The following packages are reported by dnf repoquery --whatrequires to > depend on mercurial:

Re: F30 change, bootloaderspec by default

On Mon, Feb 11, 2019 at 5:40 AM Nicolas Mailhot wrote: > > Le 2019-02-10 20:05, Chris Murphy a écrit : > > On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas > > > Between this feature for F30, and the F29 feature to hide the grub > > menu which comes with boot success+fail marking by using t

Re: F30 change, bootloaderspec by default

Le lundi 11 février 2019 à 12:52 -0700, Chris Murphy a écrit : > On Mon, Feb 11, 2019 at 5:40 AM Nicolas Mailhot > wrote: > > Le 2019-02-10 20:05, Chris Murphy a écrit : > > > On Wed, Feb 6, 2019 at 1:08 AM Javier Martinez Canillas > > > Between this feature for F30, and the F29 feature to hide th

Re: Blocking criteria proposal for F30+: Printing

On Mon, Feb 11, 2019 at 2:24 PM Chris Murphy wrote: > > On Mon, Feb 11, 2019 at 9:58 AM Stephen Gallagher wrote: > > > > Sorry that it's taken me so long to get back to this. > > > > I think the feedback on this has been mostly positive on the Beta > > criteria, but I'd like to tweak the phrasing

Re: F30 change, bootloaderspec by default

On Mon, Feb 11, 2019 at 1:14 PM Nicolas Mailhot wrote: > > That was during dnf update to the result of the latest rawhide mass > rebuild, on two UEFI systems, one initially installed in september 2015, > the other in january 2019, with whatever was most current then and then > switched to rawhide

Draft Fedora 31 schedule available

It's almost time for me to submit the Fedora 31 schedule to FESCo for approval. Before I do that, I'm sharing it with the community for comment. Take a look at the full schedule[1]. If you have any questions or comments, join me in the FPgM office hours on Wednesday[2] or file an issue in the sched

Retire apiextractor?

Currently apiextractor is FTBFS[1] because all the test fail. It looking to see if there is a newer version that better supports gcc 9.0.x I found this[2] which states that apiextrator was merged into shiboken. So can someone with more familiarity with pyside/shiboken/apiextractor say if apiextra

Ownership of rogue

As per https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package ...I will be taking ownership of the rogue package. I was actually the maintainer for this package many years ago, and would hate to see it dropped. --Wart _

GCC 9 OpenMP issues

Looks like GCC 9 is finally enforcing an OpenMP change: From https://gcc.gnu.org/ml/gcc-patches/2018-11/msg00628.html - change data sharing for readonly variables without mutable members, they are no longer predetermined shared (this actually changed in earlier OpenMP standard releases, bu

Re: GCC 9 OpenMP issues

I also have OpenMP issues in ufraw [1] and can help me too ? Thanks [1] https://bugzilla.redhat.com/show_bug.cgi?id=1671080 https://koji.fedoraproject.org/koji/taskinfo?taskID=32347242 On Mon, 2019-02-11 at 19:17 -0700, Orion Poplawski wrote: > Looks like GCC 9 is finally enforcing an OpenMP

[Fedocal] Reminder meeting : Modularity Team (weekly)

Dear all, You are kindly invited to the meeting: Modularity Team (weekly) on 2019-02-12 from 15:00:00 to 16:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Meeting of the Modularity Team. More information available at: [Modularity Team Docs](https://docs.pagure.o

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini wrote: > I'm curious: What happens to modules when a package's master branch > gets retired? Nothing. Modules will continue to exist and will continue to be delivered to users. -- Mikolaj Izdebski ___ de

Re: F30 Self-Contained Change proposal: Ibus-typing-booster default for Indian languages

Hi folks, If it's not a single input source, I'd think it could be an idea to implement the languages tag besides language tag in that ibus compose file. Fujiwara On 2019/01/29 15:33, Mike FABIAN-san wrote: Owen Taylor さんはかきました: Currently, ibus-m17n is the default input method for Indian l

Re: Orphaned packages that will be retired (and everything will most likely burn)

On 2/12/19 8:22 AM, Mikolaj Izdebski wrote: On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini wrote: I'm curious: What happens to modules when a package's master branch gets retired? Nothing. Modules will continue to exist and will continue to be delivered to users. Actually, I consider ant

Re: Orphaned packages that will be retired (and everything will most likely burn)

On Tue, Feb 12, 2019 at 9:51 AM Ralf Corsepius wrote: > On 2/12/19 8:22 AM, Mikolaj Izdebski wrote: > > On Mon, Feb 11, 2019 at 11:19 PM Fabio Valentini > wrote: > >> I'm curious: What happens to modules when a package's master branch > >> gets retired? > > > > Nothing. Modules will continue to