Hi,
I would like to update libinfinity to 0.6.1 where possible. I prepared a
copr build at:
https://copr.fedoraproject.org/coprs/till/gobby05/
I did not yet test whether the gedit or kte plugins rebuild properly,
but I will do so before updating Rawhide.
Regards
Till
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2014-08-21 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2014-08-28 09:00 Thu US/Pacific PDT
2014-08-28 12:00 Thu US/Eastern EDT
2014-08-28 16:00 Thu UTC <-
2014-08-28 17:00 Thu Europe/London BST
2014-08-28 18:00 Thu Europe/Paris CEST
2014-08-28 18:00 Thu Europe/Berlin CEST
2014-08-28 21:30 Thu Asia/Calcutta IST
------------------new day----------------------
2014-08-29 00:00 Fri Asia/Singapore SGT
2014-08-29 00:00 Fri Asia/Hong_Kong HKT
2014-08-29 01:00 Fri Asia/Tokyo JST
2014-08-29 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
https://fedorahosted.org/fpc/report/12
= Followups =
(approval and retirement sections already passed, /opt exception passed,
basename passed)
#topic #339 software collections in Fedora
.fpc 339
https://fedorahosted.org/fpc/ticket/339
(comment #16 is the current winner)
#topic #341 How to replace "docker" package with an entirely
different package of the same name?
.fpc 341
https://fedorahosted.org/fpc/ticket/341
#topic #382 Go Packaging Guidelines Draft
.fpc 382
https://fedorahosted.org/fpc/ticket/382
(more votes needed, or defer to FESCO?)
#topic #444 Officially recommend to releng that SCLs be placed in
separate packages rather than separate branches in git
.fpc 444
https://fedorahosted.org/fpc/ticket/444
= New business =
#topic #447 Bundling exception for axmail
.fpc 447
https://fedorahosted.org/fpc/ticket/447
#topic #448 Copylib exception for fastlz
.fpc 448
https://fedorahosted.org/fpc/ticket/448
#topic #450 Temporary jsquery packing exception for kimchi
.fpc 450
https://fedorahosted.org/fpc/ticket/450
#topic #452 Crypto policies packaging guideline
.fpc 452
https://fedorahosted.org/fpc/ticket/452
#topic #453 Changes/SystemdSysusers updates for
Packaging:UsersAndGroups
.fpc 453
https://fedorahosted.org/fpc/ticket/453
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
https://fedorahosted.org/fpc/report/12
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
Hi all,
I am new to the Fedora Project and I understand I should introduce myself here.
I'm a french research engineer in bioinformatics and computational biology.
My main interests are about Evolution and its dynamics but I'm also involved in sequence analysis and image analysis.
Here's a link to my first review request: https://bugzilla.redhat.com/show_bug.cgi?id=1134835
The packaged piece of software, namely kissplice, allows one to detect different kinds of polymorphism (primarily alternative splicing events) from RNA-seq data with or without a reference genome.
Any kind of input/comment would be most welcome !
Thank you,
David
--
Untitled
logo
*David Parsons* <http://www.parsons.eu/>
Service d'Expérimentation et de Développement
Antenne Inria Lyon - La Doua
Bâtiment CEI-2
56 Boulevard Niels Bohr
CS 52132
69603 Villeurbanne
Tel : +33 (0)4 72 43 74 97
*www.inria.fr <http://www.inria.fr/>*
Seems the fakesystemd package is breaking some rawhide builds, particularly
because it is getting pulled into the buildroot and that it contains:
Conflicts: systemd
Example qt:
https://koji.fedoraproject.org/koji/taskinfo?taskID=7452802
(which is no direct systemd dependencies, mind you)
I can guess why this fakesystemd package came into existence, but I question
the wisdom behind it's implementation. As far as I can tell, it contains
only:
Provides: systemd
(and a few other systemd-related dependencies)
systemd-related directories
systemd macros
I'd argue
* these last 2 items could easily be shared with the real systemd package
(ie, systemd could grow systemd-filesystem and/or systemd-macros subpkgs)
and should not be duplicated here.
* fakesystemd should be untagged until the reasons behind these failures are
better understood and fixed
-- Rex
According to Policy for nonresponsive package maintainers.
Takanori Matsuura did not respond on https://bugzilla.redhat.com/show_bug.cgi?id=1105916, contact email is silent too.
Moreover, his last build on koji was in late 2012.
As for both above mentioned, I want to take ownership on CVector and NearTree packages that needed for rasmol package I maintain.
krege
Hi,
Recently I have noticed that systemd package dependency is creeping into
some packages where it is not necessary. subversion [1] or rsync [2] are
good examples. Please consider moving daemon parts into independent
subpackages. When I install rsync/subversion, I am typically interested
just in client side.
Just to be clear, systemd-libs is in minimal build root already, so I am
not complaining about systemd-libs package, but about systemd package.
Thanks,
Vít
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1133786
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1123813
Hi working groups members,
since we have learned on Flock that new Fedora working groups do not
communicate with each other much (or enough), I'd like to propose the
following:
Every working group will time to time (e.g. weekly) send short summary
about what they did / were talking about directly to mailing lists of
other working groups + to devel(a)fp.o. Really only a short summary with
links where one can find details.
I tried to collect such info from the meeting logs and mailing lists for
the last few weeks for Env and Stacks WG:
https://lists.fedoraproject.org/pipermail/env-and-stacks/2014-August/000487…
I found many notes are really worth spreading beyond groups' borders,
but it takes too much time for one person to collect all the
information. Thus, proposing to "do a summary once per group and share
with other groups".
Another benefit would be that Matt would have better content for his 5tiftw.
I don't think we need to sync about date or frequency, just remembering
to send a direct mail if anything interesting is done/discussed should
work fine.
List of proposed MLs to send this summary to:
server(a)lists.fedoraproject.org
desktop(a)lists.fedoraproject.org
cloud(a)lists.fedoraproject.org
env-and-stacks(a)lists.fedoraproject.org
devel(a)lists.fedoraproject.org
Comments, ideas or better solutions are welcome as usually, but I might
be offline until Sunday, so do not expect any answers from me in that
time :)
Cheers,
Honza