Failed compose.
- [41588033](https://koji.fedoraproject.org/koji/taskinfo?taskID=41588033)
Live media log:https://kojipkgs.fedoraproject.org//work/tasks/8092/41588092/livemedia-…
error:
2020-02-18 08:42:41,890 INFO pylorax: Non interactive installation failed:
2020-02-18 08:42:41,890 INFO pylorax: Problem: conflicting requests
2020-02-18 08:42:41,890 INFO pylorax: - nothing provides libcgns.so.3.4 needed by paraview-5.6.0-14.fc32.i686
2020-02-18 08:42:41,890 INFO pylorax: - nothing provides libcgns.so.3.4()(64bit) needed by paraview-5.6.0-14.fc32.x86_64.
2020-02-18 08:42:41,890 INFO pylorax:
Root log:https://kojipkgs.fedoraproject.org//work/tasks/8092/41588092/root.log
DEBUG util.py:596: 2020-02-18 08:42:41,890: Non interactive installation failed:
DEBUG util.py:596: 2020-02-18 08:42:41,890: Problem: conflicting requests
DEBUG util.py:596: 2020-02-18 08:42:41,890: - nothing provides libcgns.so.3.4 needed by paraview-5.6.0-14.fc32.i686
DEBUG util.py:596: 2020-02-18 08:42:41,890: - nothing provides libcgns.so.3.4()(64bit) needed by paraview-5.6.0-14.fc32.x86_64.
DEBUG util.py:596: 2020-02-18 08:42:41,890:
--
Danny Lee <dreamer(a)panix.com>
I have been impressed with the urgency of doing. Knowing is not enough;
we must apply. Being willing is not enough; we must do. ~ Leonardo da Vinci
Hello,
What needs to go into the next blog post?
- our FTBFS updates, (me)
- updates in packages, (me)
- compose info, (me)
- FOSDEM bits, (major),
@major, please send me your bit when its ready.
Everyone: if there's anything else that needs to go in, please reply to
this thread to let me know before Friday so that I can publish on
Monday.
We're looking for a new Marketing/Social media manager, so I'll write a
different post for that.
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
Hello there
Here are the logs for today's meeting.
HTML Logs: https://meetbot.fedoraproject.org/fedora-neuro/2020-02-25/neurofedora.2020-…
HTML Minutes: https://meetbot.fedoraproject.org/fedora-neuro/2020-02-25/neurofedora.2020-…
Minutes in plain text are pasted below.
=====================================
#fedora-neuro: NeuroFedora 2020-02-25
=====================================
Meeting started by MeWjOr at 16:00:16 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-neuro/2020-02-25/neurofedora.2020-…
.
Meeting summary
---------------
* Agenda Summary (MeWjOr, 16:01:45)
*
https://lists.fedoraproject.org/archives/list/neurofedora@lists.fedoraproje…
(MeWjOr, 16:03:07)
* Introductions and roll call (MeWjOr, 16:03:17)
* Tasks from last meeting (MeWjOr, 16:03:21)
* Pagure tickets (MeWjOr, 16:03:28)
* Bugs (MeWjOr, 16:03:34)
* Neuroscience query of the week
https://pagure.io/neuro-sig/NeuroFedora/issue/318 (MeWjOr,
16:03:43)
* Open floor (MeWjOr, 16:03:47)
* Introductions and roll call (MeWjOr, 16:03:59)
* Tasks from last meeting on 2020-02-11 (MeWjOr, 16:07:12)
* Minutes:
https://meetbot.fedoraproject.org/fedora-neuro/2020-02-11/neurofedora.2020-…
(MeWjOr, 16:07:29)
* MeWjOr write event report, send to ML, submit to Mindshare ---
Written a draft so far... Will review and add more stuff soon
(MeWjOr, 16:08:37)
* MeWjOr e-mail ML with other discussion points that came up during
FOSDEM --- Done (MeWjOr, 16:08:47)
* LoKoMurdoK file ticket with Mindshare requesting some NeuroFedora
swag --- waiting for a reply from mindshare (MeWjOr, 16:09:46)
* Once the badge has been imported to badges, I'll be able to award
them: https://pagure.io/fedora-badges/issue/678#comment-628475
(FranciscoD, 16:11:06)
* FranciscoD ask bt0 alciregi if they know how badges are to be given
out manually --- Done. (MeWjOr, 16:11:12)
* LoKoMurdoK comment on the ticket thanking riecatnor and asking what
needs to be next: how do we give the badges out, manually to start
with. --- done. Waiting for the badges team to push the badge online
(MeWjOr, 16:11:19)
* Everyone look for nice brain images with a CC license for the banner
image --- let's do this over this week? (MeWjOr, 16:11:55)
* ACTION: lbazan ping on the mindshare ticket for swag (MeWjOr,
16:13:48)
* ACTION: Everyone look for nice brain images with a CC license for
the banner image (MeWjOr, 16:13:52)
* FranciscoD take care of all the other tickets this week --- I'll
help you with this.... (MeWjOr, 16:14:17)
* ACTION: FranciscoD, MeWjOr take care of all the other tickets this
week (MeWjOr, 16:14:52)
* FranciscoD write abstract for CNS*2020 this week also --- did you
write it? (MeWjOr, 16:15:16)
* ACTION: FranciscoD finalize the draft of the abstract for CNS*2020
this week also (MeWjOr, 16:16:00)
* FranciscoD add some packaging tickets to kanban for folks to test
out --- You added the FTBFS bugs, so great (MeWjOr, 16:16:30)
* FranciscoD send a list of FTBFS bugs to ML --- done. ^.^ (MeWjOr,
16:16:45)
* FranciscoD send out logs, update tickets --- done. (MeWjOr,
16:17:31)
* Pagure tickets (MeWjOr, 16:21:04)
*
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+m…
(MeWjOr, 16:21:14)
* LinkedIn Group Research
https://pagure.io/neuro-sig/NeuroFedora/issue/338 (MeWjOr,
16:21:53)
* ACTION: dan1mal create the LinkedIn group and post it on the
ticket. (MeWjOr, 16:25:29)
* Once the group is active, we will have to add it to
neuro{,blog}.fp.o as well (MeWjOr, 16:28:45)
* Estimating team resources:
https://pagure.io/neuro-sig/NeuroFedora/issue/337 (MeWjOr,
16:29:27)
* LINK:
https://neuroblog.fedoraproject.org/2019/08/07/open-position-neurofedora-is…
(FranciscoD, 16:38:10)
* Use teams.fedoraproject.org (Taiga) kanban board for better planning
--- https://pagure.io/neuro-sig/NeuroFedora/issue/336 (MeWjOr,
16:41:36)
* The next issues are for the comp-neuro lab... Featured apps, banner
images, screenshots, summary and content (MeWjOr, 16:43:37)
* https://pagure.io/neuro-sig/NeuroFedora/issue/307 (MeWjOr,
16:49:24)
* Figure out badges rule to award badge automatically to pagure group
members: https://pagure.io/neuro-sig/NeuroFedora/issue/250 (MeWjOr,
16:51:18)
* Open bugs (MeWjOr, 16:52:39)
* Open bugs: https://tinyurl.com/neurofedora-bugs (MeWjOr, 16:52:50)
* LINK: https://koji.fedoraproject.org/koji/packageinfo?packageID=2729
(FranciscoD, 16:54:34)
* AGREED: ? (MeWjOr, 16:57:25)
* AGREED: (MeWjOr, 16:57:30)
* AGREED: (MeWjOr, 16:57:33)
* AGREED: Drop paraview from the image (MeWjOr, 16:57:51)
* AGREED: Drop paraview from the image (MeWjOr, 16:57:55)
* LINK: https://fedoraproject.org/wiki/Meeting:Guide#MeetBot_Commands
-> agreed <info> (FranciscoD, 16:58:08)
* We agree on dropping paraview from the image (MeWjOr, 16:58:38)
* ACTION: dan1mal Make a PR on fedora-kickstarts to remove paraview
from the image (MeWjOr, 17:00:12)
* LINK:
https://teams.fedoraproject.org/project/neurofedora-ftbfs-bugs-f32/kanban
(FranciscoD, 17:00:57)
* FTBFS bugs are in control:
https://teams.fedoraproject.org/project/neurofedora-ftbfs-bugs-f32/kanban
(FranciscoD, 17:01:44)
* Next meeting --- Time and Chair (MeWjOr, 17:02:50)
* ACTION: dan1mal will chair the next meeting (MeWjOr, 17:04:12)
* next meeting will take place on 10th March 2020, same time (1600
UTC) (MeWjOr, 17:04:35)
Meeting ended at 17:05:00 UTC.
Action Items
------------
* lbazan ping on the mindshare ticket for swag
* Everyone look for nice brain images with a CC license for the banner
image
* FranciscoD, MeWjOr take care of all the other tickets this week
* FranciscoD finalize the draft of the abstract for CNS*2020 this week
also
* dan1mal create the LinkedIn group and post it on the ticket.
* dan1mal Make a PR on fedora-kickstarts to remove paraview from the
image
* dan1mal will chair the next meeting
Action Items, by person
-----------------------
* dan1mal
* dan1mal create the LinkedIn group and post it on the ticket.
* dan1mal Make a PR on fedora-kickstarts to remove paraview from the
image
* dan1mal will chair the next meeting
* FranciscoD
* FranciscoD, MeWjOr take care of all the other tickets this week
* FranciscoD finalize the draft of the abstract for CNS*2020 this week
also
* MeWjOr
* FranciscoD, MeWjOr take care of all the other tickets this week
*lbazan
* ping on the mindshare ticket for swag
* Everyone
* look for nice brain images with a CC license for the banner
image
People Present (lines said)
---------------------------
* MeWjOr (124)
* FranciscoD (115)
* dan1mal (35)
* zodbot (23)
* fm-neuro (5)
* gicmo (2)
* tg-fedneuro3 (1)
* alciregi (0)
* bt0 (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Thanks
Regards
Aniket Pradhan
http://home.iiitd.edu.in/~aniket17133/
Aliases: MeWjOr/major
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Hey there!
You are invited to attend the next Open NeuroFedora team meeting this
week on Tuesday at 1600UTC in #fedora-neuro on IRC (Freenode):
https://webchat.freenode.net/?channels=#fedora-neuro
You can convert the meeting time to your local time using:
$ date --date='TZ="UTC" 1600 next Tue'
or use this link:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=NeuroFedora+Meeti…
The meeting will be chaired by @major. The agenda for the meeting is:
- Introductions and roll call.
- Tasks from last week's meeting: NA
- Pagure tickets:
https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&tags=S%3A+Next+m…
- Neuroscience query of the week.
- Next meeting day, and chair.
- Open floor.
In the "Neuroscience query of the week" section, attendees can ask
about/discuss a neuroscience topic that they are curious about.
We hope to see you there! :D
--
Thanks
Regards
Aniket Pradhan
http://home.iiitd.edu.in/~aniket17133/
Aliases: MeWjOr/major
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Hello people,
GSoC and Outreachy are coming, and I was wondering if we can have a
project based on packaging/testing this time [0]?
GSoC would be a great outreach method to the younger audience
(students) who can take an interest in packaging and learn more about
the Fedora community.
Many other orgs have mentored projects based on packaging, and
therefore it is not uncommon if we bring a project on the same. We can
maybe have a mentored project on some other topic, but I cannot think
of any other topic for our sig.
I would love to hear everyone's review on the same topic, and I hope
we are able to submit at least one mentored project for GSoC or
Outreachy this time.
[0]: https://communityblog.fedoraproject.org/call-for-projects-and-mentors-gsoc-…
--
Thanks
Regards
Aniket Pradhan
http://home.iiitd.edu.in/~aniket17133/
Aliases: MeWjOr/major
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
[livemedia]
https://kojipkgs.fedoraproject.org//work/tasks/6820/41796820/livemedia-out.…
2020-02-23 09:03:26,627 INFO pylorax: The exact error message is:
2020-02-23 09:03:26,628 INFO pylorax:
2020-02-23 09:03:26,628 INFO pylorax: Non interactive installation failed:
2020-02-23 09:03:26,628 INFO pylorax: Problem: conflicting requests
2020-02-23 09:03:26,628 INFO pylorax: - nothing provides libcgns.so.3.4 needed by paraview-5.6.0-14.fc32.i686
2020-02-23 09:03:26,628 INFO pylorax: - nothing provides libcgns.so.3.4()(64bit) needed by paraview-5.6.0-14.fc32.x86_64.
2020-02-23 09:03:26,628 INFO pylorax:
2020-02-23 09:03:26,628 INFO pylorax: The installer will now terminate.
[root log]https://kojipkgs.fedoraproject.org//work/tasks/6820/41796820/root.log
DEBUG util.py:596: 2020-02-23 09:03:26,627: The exact error message is:
DEBUG util.py:596: 2020-02-23 09:03:26,628:
DEBUG util.py:596: 2020-02-23 09:03:26,628: Non interactive installation failed:
DEBUG util.py:596: 2020-02-23 09:03:26,628: Problem: conflicting requests
DEBUG util.py:596: 2020-02-23 09:03:26,628: - nothing provides libcgns.so.3.4 needed by paraview-5.6.0-14.fc32.i686
DEBUG util.py:596: 2020-02-23 09:03:26,628: - nothing provides libcgns.so.3.4()(64bit) needed by paraview-5.6.0-14.fc32.x86_64.
DEBUG util.py:596: 2020-02-23 09:03:26,628:
DEBUG util.py:596: 2020-02-23 09:03:26,628: The installer will now terminate.
From kevin's comments in issue #1023:
kevin<https://pagure.io/user/kevin>commented 2 days ago
<https://pagure.io/releng/failed-composes/issue/1023#comment-627609>
It seems that paraview likely needs a rebuild:
➜ ~ sudo dnf repoquery --provides cgnslib-3.4.1-1.fc33.x86_64
cgnslib = 3.4.1-1.fc33
cgnslib(x86-64) = 3.4.1-1.fc33
libcgns.so.3.4.1()(64bit)
So, it provides '3.4.1' and paraview is looking for just 3.4.
Rebuilding paraview would hopefully link it to the new one...
kevin<https://pagure.io/user/kevin>commented 2 days ago
<https://pagure.io/releng/failed-composes/issue/1023#comment-627610>
Ah, but it
failed:https://koji.fedoraproject.org/koji/buildinfo?buildID=1463562
-------- Forwarded Message --------
Subject: [releng/failed-composes] Issue #1037:
Fedora-Rawhide-20200223.n.0 FINISHED_INCOMPLETE
Date: Sun, 23 Feb 2020 12:11:22 +0000 (UTC)
From: release engineering <pagure(a)pagure.io>
Reply-To:
reply+8bc112611267717d6c2805dd108f55ba023bb697bd1d4b75f3450f045307c157fc96def4e1afe7fa5f4f628d8baccd128922446779674f2edba9ee0813af54fe(a)pagure.io
To: dreamer(a)panix.com
- [41796802](https://koji.fedoraproject.org/koji/taskinfo?taskID=41796802)
```
[LIVE_MEDIA ] [ERROR ] [FAIL] Live media (variant Labs, arch *,
subvariant Comp_Neuro) failed, but going on anyway.
[LIVE_MEDIA ] [ERROR ] Live media task failed: 41796802. See
/mnt/koji/compose/rawhide/Fedora-Rawhide-20200223.n.0/logs/x86_64/livemedia-Labs-Comp_Neuro.x86_64.log
for more details.
```
To reply, visit the link below or just reply to this email
https://pagure.io/releng/failed-composes/issue/1037
Hello,
Just an FYI, apologies for the cross-post.
Koschei is a CI for rpm packages that helps us packagers track package
dependency changes. It'll help us ensure that our packages are always
installable. You can read more about it here:
https://fedoraproject.org/wiki/Koschei
mizdebsk was kind enough to set up automatic tracking for all packages
in the `scitech_sig` and `neuro-sig` packager groups for us on Koschei.
So every few hours, Koschei will automatically add any new packages that
are maintained by these packager groups.
https://pagure.io/fedora-infrastructure/issue/8678
You can see these here:
https://koschei.fedoraproject.org/groups/scitech_sighttps://koschei.fedoraproject.org/groups/neuro-sig
Please keep an eye on Koschei. Please also remember to thank mizdebsk
(by giving them a cookie over IRC, for example: in #fedora-devel,
mizdebsk++ will do).
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
Hello,
Based on the discussion here:
https://pagure.io/neuro-sig/NeuroFedora/issue/339
I've written up a simple test case for the nest simulator here:
https://fedoraproject.org/wiki/QA:Testcase_nest_run
It'll allow us to:
- learn about how the simulator works and what it does,
- test the package while we learn.
If folks are interested, please give it a go and give feedback on how it
can be improved. This will hopefully allow us to get more people
involved: they can run simple tests and learn how to use these tools as
they do.
Thoughts?
--
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London
Hello folks!
Following FOSDEM, today I presented NeuroFedora on eLife Innovation Leaders.
The topic for the discussion was "road mapping for an open project",
and I presented NeuroFedora the roadmap for our sig as well. The main
points to highlight from the discussion was how the sig formed, the
real problem that we intend to solve, how would we solve that, and our
plans for the future.
There were some interesting questions in the discussion as well, but
the most interesting was, how do we actually test the tools before
packaging them. Apart from the basic unit tests (that upstream
provides), do we do any other tests to ensure it's correctness?
Since, we have a lack of neuroscientists in the sig, who actually use
the packaged tools, I believe that we should test the tools packaged
by us, as a QA to actually verify that they work in Fedora.
As an example, if we package a DICOM image viewer, then we should make
sure that we are able to view images in it, other than the actual math
behind it that is verified by the unit tests. This may turn out to be
quite difficult for some complicated tools, but it would help us
gradually shift from packaging to testing as well.
Other than that, below are the notes made by Emmy during the talk for
everyone's reference. The slides for the talk are present here [0].
[0]: https://docs.google.com/presentation/d/1iZq5rOx6wX4jl5pFByUvywdsgz5fQgGDWTo…
-------------------------------------------------------------
Neurofedora: https://neuroblog.fedoraproject.org/
> How we roadmap Neurofedora and implemented our ideology!
> Vision: make it easier for people to use neuroscience software
> At the beginning:
> > Why do people need NeuroFedora?
> > Neuroscience is very multi-disciplinary
> > Only a few are trained software developers; most neuroscientists struggle with software installation
> Neurofedora is a volunteer-driven group
> > They ensure quality of software – that the research produced (at least parts that are handled by the software) is reproducible
> > Good documentation is key!
> Current challenges
> > Challenging to recruit workforce, time is precious for existing users and contributors!
> > Challenges to conduct proper review
> How they built a roadmap: setting up project milestones
> > Build core community - people that share similar visions
> > Ensure the problem actually exist
> > Provide the tools!
> > Marketing and reaching out to the community - if people don’t know about you, then people cannot try and it and use it?
> > Future prospects: what else can we do for the community? We value the quality of our work, and we’d like to work with the community to safeguard that
> Current core team: 10 members, 4 neuroscientists
--
Thanks
Regards
Aniket Pradhan
http://home.iiitd.edu.in/~aniket17133/
Aliases: MeWjOr/major
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Hello there!
I recently represented NeuroFedora at FOSDEM, and it was a great
experience. I met many people from Fedora who knew about us, but also
met a few who did not. I feel that at the very least, people from
Fedora should know more about the group, our motivation, and what we
do. We also seem to have a low number of contributors.
After my discussion with Sumantro, he recommended some steps to
increase our community involvement within the Fedora community, which
are summarised below:
1. Send out a call-for-participation to the -devel (or any other that
may seem fit) mailing list (if we feel that we have a lack of
contributor base),
2. More frequent blog posts (in the Fedora blogs or Fedora magazine)
about the community.
3. Organize hackfests. Hackfests will attract more contributors. We
can have packaging hackfests, where we spend straight hours packaging
and reviewing software. A similar hackfest organized by the Badges
community is present here[0].
4. Talk to the Fedora Project Leader (Matthew Miller) about our sig
and ask what we can do to increase the community outreach of our sig.
Since he is the FPL, he can guide us more appropriately.
We can also have a brainstorming session as well on these points (in
one of our future meetings) and discuss the forward direction of our
sig.
[0]: https://fedoraproject.org/wiki/Badges_Hackfest_2020?rd=Badges_Hackfest_2019
--
Thanks
Regards
Aniket Pradhan
http://home.iiitd.edu.in/~aniket17133/
Aliases: MeWjOr/major
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments