Re: Broken dependencies: freesteam
by Antonio Trande
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all.
On 08/25/2014 01:39 PM, buildsys(a)fedoraproject.org wrote:
> freesteam has broken dependencies in the F-21 tree: On x86_64:
> freesteam-ascend-2.1-6.20140724svn753.fc21.x86_64 requires
> libascend.so.1()(64bit) On i386:
> freesteam-ascend-2.1-6.20140724svn753.fc21.i686 requires
> libascend.so.1 On armhfp:
> freesteam-ascend-2.1-6.20140724svn753.fc21.armv7hl requires
> libascend.so.1 Please resolve this as soon as possible.
>
buildsys(a)fedoraproject.org sends me above message via mail.
It's okay to me:
$repoquery -R freesteam-ascend --enablerepo=updates-testing
ascend-libs(x86-64)
freesteam(x86-64) = 2.1-6.20140724svn753.fc20
libascend.so.1()(64bit)
libc.so.6(GLIBC_2.3.4)(64bit)
libfreesteam.so.1()(64bit)
rtld(GNU_HASH)
$repoquery --whatprovides libascend.so.1*
- --enablerepo=updates-testing --archlist=x86_64
ascend-libs-0:0.9.8-10.20140710svn4695.fc20.x86_64
I don't know what's the problem...
- --
Antonio Trande
mailto: sagitterATfedoraproject.org
http://fedoraos.wordpress.com/
https://fedoraproject.org/wiki/User:Sagitter
GPG Key: D400D6C4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBAgAGBQJT+y1PAAoJED2vIvfUANbEv/cP+QG2OQj6MBAeg0C7WowrrOqU
n7x789PtBZnxpkOiIvItqyL/Tm4Mg0W7u3ylQpcXzSYRnhyQtNQQfFzEL+EiPWRX
Vm12tTtjyqSgYC3A3fY5ycIHlLz1IhbmNV9Rd8oSWc7CVLOiADat1ocWrhm+1xN7
2sC2scpCvVaJXxOh3j/4WaStmHxANUShTeTIV5e6AKpMx3RGBTgSRdeXqN4zu5uG
zJ4tzzodQKv4R510oSlsKotuY2apP3ccpqq0DrGIExXsMvSd3DbQxT7qK4GPoaOj
mfXaxW1dZMsJ8HaTXJVwj71aUqaG4k4XIE1izx8RRwR9/OuHshxGh24cGuGIuE65
Q+QHArIKAioZvCLURJfZZUG/ODaOzVNvYK9FK91E6WDsTD0cy3KUWf8DSoGyy1Je
DQ0WTc24wfoN8V27h0/alxw8v1jI8eKbY+0hJBc0OaKQ14VBKfHczgkRjSFHoqeJ
xeqp74D2wnmaty4AM119oaCO5g0rVJooVXUgsdFvERDby2Bb5lGCv/a2dZ6e+Y0q
C2nGmL5sTN+wBHwHi2JejbdHKh6mSL9JyXf7YouRkPs1GuuOfed0IpSHKRKLcsB0
Syej5dVc1qXq34Gnf1kviifVmZHFEW/bkNC3nxNUOLO/foOqfaeQUx8dByXgb0tQ
vmGe4BAmbVKVHOKOqJRl
=g0XH
-----END PGP SIGNATURE-----
9 years, 6 months
Self Introduction: David Parsons
by David Parsons
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/>*
9 years, 7 months
fakesystemd package breaking builds
by Rex Dieter
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
9 years, 7 months
systemd dependencies
by Vít Ondruch
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
9 years, 7 months
Proposal for every WG to send a short summary *to other WGs directly*
by Honza Horak
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/0004...
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
9 years, 7 months