Hi,
I'm playing with an idea of building lua libraries against compat-lua to
allow luajit working with them. My initial motivation for this is that
there are projects which don't work with Lua-5.2 and developers for
various reasons don't want to port it to lua-5.2 yet (for example
Prosody pac
On even weeks WG meeting will be at 12:00 UTC, 14:00 Central Europe,
8:00 (noon) Boston, 5:00 San Francisco, 21:00 Tokyo in #fedora-meeting
on Freenode.
= Topics =
* continue with https://fedorahosted.org/rel-eng/ticket/5894
* there might be needed changes in scl-utils
* OpenFloor
--
devel mai
#fedora-meeting: Env and Stacks (2014-05-13)
Meeting started by mmaslano at 12:00:05 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2014-05-13/env-and-stacks.2014-05-13-
As packages age sometimes build requirements chance and may not be caught
by the package maintainer. Is there a known way of determining if there are
unnecessary build requirements in a package?
I would think you would need to step through the BR:'s get the capabilities
of the packages that the -d
Hello,
Red Hat is going to take over maintainership of Ceph so I'm orphaning
it and Kaleb Keithley is taking over it. Thanks,
Josef
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 17:00UTC in #fedora-meeting on irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '20
On Tue, May 13, 2014 at 5:14 PM, Richard Shaw wrote:
> I would think you would need to step through the BR:'s get the capabilities
> of the packages that the -devel package pull in, and then check that against
> the requires of the resultant packages.
BR's don't always map/result into any depende
Hi,
apitrace 5.0 bundles libbacktrace, which looks like is living within the
gcc sources. libbacktrace is not build as a shared library from the gcc
sources, and not packaged.
Is it feasible to build libbacktrace as a shared library and ship it in
a corresponding package? Or should I rather
On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
> apitrace 5.0 bundles libbacktrace, which looks like is living within
> the gcc sources. libbacktrace is not build as a shared library from
> the gcc sources, and not packaged.
>
> Is it feasible to build libbacktrace as a shared librar
On 13.05.2014 19:02, Jakub Jelinek wrote:
On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
apitrace 5.0 bundles libbacktrace, which looks like is living within
the gcc sources. libbacktrace is not build as a shared library from
the gcc sources, and not packaged.
Is it feasible to b
Can dnf be made to explain conflicts? In this case, some other package needs
libLLVM-3.4 and julia needs to be rebuilt, it still wants libLLVM-3.3. Can dnf
be made to give a better explanation?
sudo dnf install julia -v
Config time: 0.005
cachedir: /var/cache/dnf/x86_64/20
Repository google-c
Am 13.05.2014 18:23, schrieb Ville Skyttä:
> On Tue, May 13, 2014 at 5:14 PM, Richard Shaw wrote:
>> I would think you would need to step through the BR:'s get the capabilities
>> of the packages that the -devel package pull in, and then check that against
>> the requires of the resultant packag
On Tue, May 13, 2014 at 11:23 AM, Ville Skyttä wrote:
> On Tue, May 13, 2014 at 5:14 PM, Richard Shaw
> wrote:
> > I would think you would need to step through the BR:'s get the
> capabilities
> > of the packages that the -devel package pull in, and then check that
> against
> > the requires of
Planned Outage: Upgrade to pkgdb2 - 2014-05-14 12:00 UTC
There will be an outage starting at 2014-05-14 12:00 UTC, which will
last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2014-05-14 12:
How do I go about contacting the "workstation working group"?
-
Made a mistake in my original post - the package ibus-libs was not supposed
to be included.
Here is the updated command:
sudo yum remove ibus ibus-chewing ibus-gtk2 ibus-gtk3 ibus-hangul ibus-kkc
ibus-libpinyin ibus-m17
Could someone please build that. The blank PDF print thing is a bit
annoying with 29.
Thanks,
--
Bojan
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, May 13, 2014 at 14:16:10 -0700,
quickbooks office wrote:
How do I go about contacting the "workstation working group"?
https://fedoraproject.org/wiki/Workstation has their mailing list
(they use the desktop list) and their ticket tracker.
--
devel mailing list
devel@lists.fedoraproj
On 13.05.2014 19:08, Sandro Mani wrote:
On 13.05.2014 19:02, Jakub Jelinek wrote:
On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
apitrace 5.0 bundles libbacktrace, which looks like is living within
the gcc sources. libbacktrace is not build as a shared library from
the gcc sourc
Reposted from
http://fedoramagazine.org/five-things-in-fedora-this-week-2014-05-13/
Fedora is a big project, and it’s hard to follow it all. This series
highlights interesting happenings in five different areas every week.
It isn’t comprehensive news coverage — just quick summaries with links
to
On 13/05/14 20:07, Neal Becker wrote:
Can dnf be made to explain conflicts? In this case, some other package needs
libLLVM-3.4 and julia needs to be rebuilt, it still wants libLLVM-3.3. Can dnf
be made to give a better explanation?
sudo dnf install julia -v
Config time: 0.005
cachedir: /var/
On Tue, 2014-05-13 at 14:07 -0400, Neal Becker wrote:
> Can dnf be made to explain conflicts? In this case, some other
> package needs
> libLLVM-3.4 and julia needs to be rebuilt, it still wants libLLVM-3.3.
> Can dnf
> be made to give a better explanation?
I always use `--best`, and I have ver
21 matches
Mail list logo
