On 11/25/2013 07:58 AM, Adam Williamson wrote:
On Mon, 2013-11-25 at 06:33 +, Tim Landscheidt wrote:
More contested seems to be the multi-boot setup.
https://bugzilla.redhat.com/show_bug.cgi?id=872826 has a
myriad of opinions on how it should be set up;
http://fedoraproject.org/wiki/User:Jl
# Fedora Quality Assurance Meeting
# Date: 2013-11-25
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
It's meeting time again on Monday! We're into Final validation grind
now, so I expect we'll mostly be
On Mon, 2013-11-25 at 06:33 +, Tim Landscheidt wrote:
> More contested seems to be the multi-boot setup.
> https://bugzilla.redhat.com/show_bug.cgi?id=872826 has a
> myriad of opinions on how it should be set up;
> http://fedoraproject.org/wiki/User:Jlaska/Multiple_OS_Bootloader_Guide
> sugges
Hi,
IIRC fedora-review suggested to test packages on all sup-
ported Fedora releases. So, with a larger hard disk, I want
to install Fedora 19, 20 (soon) and Rawhide and throw in
(recent) Debian and Ubuntu as well. As my notebook doesn't
support VMs, I'm interested in best practices for partitio
Hello list,
I'm a computer science major interested in Linux software engineering and
just beginning to learn programming so I'm use-case #1 and #2. Currently
out of all my peers I'm the only one using Linux as far as I know. Most
students and developers even those working on Linux oriented proj
Planned Outage: Server reboots - 2013-11-25 22:00 UTC
There will be an outage starting at 2013-11-25 22:00 UTC, which will
last approximately 2 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2013-11-25 22:00 U
Hi,
Python-tag is broken in F19/20/rawhide. It failed to build during the
boost 1.54 rebuild for some reason and is therefore in FTBFS for
rawhide. I checked out the SCM and rebuilt it in mock, both for F20 and
rawhide, quite successfully. No fixes were needed. Could a proven
packager please bump
On 24.11.2013 21:52, Michael Schwendt wrote:
On Sun, 24 Nov 2013 16:50:51 +0100, Sandro Mani wrote:
Hi,
I wondered what the reason is that debuginfo packages seem to enter the
repos only at the successive push compared to the regular packages,
which ultimately means that debuginfo packages ar
On Sun, 24 Nov 2013 16:50:51 +0100, Sandro Mani wrote:
> Hi,
>
> I wondered what the reason is that debuginfo packages seem to enter the
> repos only at the successive push compared to the regular packages,
> which ultimately means that debuginfo packages are available in updates
> ca 1 day af
On 11/24/2013 10:51 AM, Josh Stone wrote:
> On 11/24/2013 09:13 AM, Sandro Mani wrote:
>> Oh, I never noticed this! I take the reason the debuginfo packages do
>> not live in the "normal" repos is that one wants to reduce the
>> repodata/filelist size? Could the current situation be improved by a
On 11/24/2013 09:13 AM, Sandro Mani wrote:
> Oh, I never noticed this! I take the reason the debuginfo packages do
> not live in the "normal" repos is that one wants to reduce the
> repodata/filelist size? Could the current situation be improved by an
> approach similar to:
> - Move the debuginf
On 24.11.2013 17:55, Michael Catanzaro wrote:
On Sun, 2013-11-24 at 16:50 +0100, Sandro Mani wrote:
From abrt-reported bugs where
people generate the backtraces locally, it occasionally happens that
they send incomplete backtraces due to mismatching debugsymbols, and
it
would certainly help in
On Sun, 2013-11-24 at 16:50 +0100, Sandro Mani wrote:
> From abrt-reported bugs where
> people generate the backtraces locally, it occasionally happens that
> they send incomplete backtraces due to mismatching debugsymbols, and
> it
> would certainly help increasing the quality of backtraces if
Hi,
I wondered what the reason is that debuginfo packages seem to enter the
repos only at the successive push compared to the regular packages,
which ultimately means that debuginfo packages are available in updates
ca 1 day after the regular packages. From abrt-reported bugs where
people gen
On Fri, Nov 22, 2013 at 02:34:28PM +0100, Kevin Kofler wrote:
> I really don't see what is missing there, apart from missing automation for
> the one-time creation process.
Something I just noticed:
- Github allows to reply to ticket notifications via email instead of
requiring to change to a
Compose started at Sun Nov 24 08:15:02 UTC 2013
Broken deps for i386
--
[OpenEXR_CTL]
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libImath.so.6
OpenEXR_CTL-1.0.1-16.fc20.i686 requires libIlmThread.so.6
OpenEXR_CTL-1.0.1-16
On Sun, Nov 24, 2013 at 01:48:53PM +0100, Till Maas wrote:
> On Sun, Nov 24, 2013 at 12:57:25PM +0100, Kevin Kofler wrote:
> > Pierre-Yves Chibon wrote:
> > > You're forgeting, patch/code reviews,
> >
> > Export patch from git, attach to new issue in the bug tracker; as the
> > maintainer, apply
On Sun, Nov 24, 2013 at 12:57:25PM +0100, Kevin Kofler wrote:
> Pierre-Yves Chibon wrote:
> > You're forgeting, patch/code reviews,
>
> Export patch from git, attach to new issue in the bug tracker; as the
> maintainer, apply it with git am and push it; where's the problem?
>
> > possibility to
On Fri, Nov 22, 2013 at 04:25:00PM +0100, Kevin Kofler wrote:
> Richard W.M. Jones wrote:
>
> > Several packages are using git for patch management. eg:
> >
> > http://pkgs.fedoraproject.org/cgit/erlang.git/tree/erlang.spec#n46
> > http://pkgs.fedoraproject.org/cgit/libguestfs.git/tree/libguestf
On Sun, Nov 24, 2013 at 12:57:25PM +0100, Kevin Kofler wrote:
> Pierre-Yves Chibon wrote:
> > You're forgeting, patch/code reviews,
>
> Export patch from git, attach to new issue in the bug tracker; as the
> maintainer, apply it with git am and push it; where's the problem?
It is possible, but I
On Sat, Nov 23, 2013 at 05:34:19PM -0600, Dennis Gilmore wrote:
>By using github you are also eliminating the possibility of some people to
>contribute to your project. I personally won't create an account on
>github. Just because I believe that open projects should be hosted on open
>
Pierre-Yves Chibon wrote:
> You're forgeting, patch/code reviews,
Export patch from git, attach to new issue in the bug tracker; as the
maintainer, apply it with git am and push it; where's the problem?
> possibility to close or refer to a ticket from the git commit,
Referring just works in Tra
On Sat, 2013-11-23 at 13:47 -0500, Simo Sorce wrote:
> On Tue, 2013-11-19 at 15:30 +0800, Mathieu Bridon wrote:
> > libverto
> >
> >
> > Upstream itself requires the pkgconfig file for libev.
> >
> > That's just a terrible idea, as it means libverto won't build on e.g
> > Debian, or with
23 matches
Mail list logo
