On Thu, 27 Jun 2013 20:52:25 -0500
Dennis Gilmore wrote:
>
> The tooling can not make split media. its not possible.
I meant us in Freemedia?
on our own pcs
--
Regards,
Frank "When in doubt PANIC!"
I check for new mail app. 20min
www.frankly3d.com
--
devel mailing list
devel@lists.fedora
Hi,
Tinyproxy package has a problem since F16 - because of missing tmpfilesd
snippet,
the program won't start without intervention of admin. Tinyproxy wnats to store
pidfile in /run/tinyproxy. This directory does not exist after fresh boot.
There's a bug open: https://bugzilla.redhat.com/show_b
Hello Jan,
- Original Message -
> From: Jan Kaluza
> Subject: Re: logrotate(8) and copytruncate as default
>
> Right now, without locking, logrotate would loss more messages if the
> logs are big, because copying takes more time. It would be interesting
> to mention the file size in y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 01:50 AM, Peter Lemenkov wrote:
> Hello. I've got bugreport that Erlang doesn't work on EL6 PPC64
> achitecture.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=958953
>
> I don't have resources to fix this issue, and nobody volunteered
Compose started at Fri Jun 28 09:15:03 UTC 2013
Broken deps for x86_64
--
[avgtime]
avgtime-0-0.5.git20120724.fc19.x86_64 requires
libphobos-ldc.so.60()(64bit)
[derelict]
derelict-ogg-3-13.20130516gitd8aa11d.fc19.i686 require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 05:43 AM, Tomasz Torcz wrote:
> Hi,
>
> Tinyproxy package has a problem since F16 - because of missing
> tmpfilesd snippet, the program won't start without intervention of
> admin. Tinyproxy wnats to store pidfile in /run/tinyproxy. Thi
On 06/28/2013 12:47 PM, Stephen Gallagher wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 05:43 AM, Tomasz Torcz wrote:
Hi,
Tinyproxy package has a problem since F16 - because of missing
tmpfilesd snippet, the program won't start without intervention of
admin. Tinyproxy wnat
On Fri, Jun 28, 2013 at 12:46:52PM +, "Jóhann B. Guðmundsson" wrote:
> On 06/28/2013 12:47 PM, Stephen Gallagher wrote:
> >>
> >>Tinyproxy package has a problem since F16 - because of missing
> >>tmpfilesd snippet, the program won't start without intervention of
> >>admin. Tinyproxy wnats to st
Dne 25.6.2013 15:41, Vít Ondruch napsal(a):
Hi,
Is there some common practice, where to place architecture specific
header files? From output of the following command, I can't see any
such place.
$ `gcc -print-prog-name=cc1` -v
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-redhat-lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 08:53 AM, Tomasz Torcz wrote:
> On Fri, Jun 28, 2013 at 12:46:52PM +, "Jóhann B. Guðmundsson"
> wrote:
>> On 06/28/2013 12:47 PM, Stephen Gallagher wrote:
Tinyproxy package has a problem since F16 - because of
missing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 08:44 AM, Stephen Gallagher wrote:
> On 06/28/2013 01:50 AM, Peter Lemenkov wrote:
>> Hello. I've got bugreport that Erlang doesn't work on EL6 PPC64
>> achitecture.
>
>> https://bugzilla.redhat.com/show_bug.cgi?id=958953
>
>> I don't
On Fri, Jun 28, 2013 at 02:58:12PM +0200, Vít Ondruch wrote:
> Dne 25.6.2013 15:41, Vít Ondruch napsal(a):
> >Is there some common practice, where to place architecture
> >specific header files? From output of the following command, I
> >can't see any such place.
gcc doesn't have such location, yo
On Fri, 28.06.13 13:23, P J P (pj.pan...@yahoo.co.in) wrote:
> > The systemd-journald takes care of all of: receiving messages, writing
> > them to storage, and rotating the storage.
> >
> > We do synchronous rotation before each write. i.e. the moment we append
> > to a file we check if the write
People,
This command:
yum groupinstall development-tools
fails with these errors:
Transaction Check Error:
file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of
systemtap-devel-2.2.1-1.fc18.x86_64 conflicts with file from package
systemtap-sdt-devel-2.1-2.fc18.x86_64
file
On Fri, Jun 28, 2013 at 10:32 AM, Philip Rhoades wrote:
> People,
>
> This command:
>
> yum groupinstall development-tools
>
> fails with these errors:
>
> Transaction Check Error:
> file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of
> systemtap-devel-2.2.1-1.fc18.x86_64 confli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Jun 28, 2013 at 11:43:44AM +0200, Tomasz Torcz wrote:
> Tinyproxy package has a problem since F16 - because of missing tmpfilesd
> snippet,
> the program won't start without intervention of admin. Tinyproxy wnats to
> store
> pidfile in /r
On 06/28/2013 03:32 PM, Philip Rhoades wrote:
People,
This command:
yum groupinstall development-tools
fails with these errors:
Transaction Check Error:
file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of
systemtap-devel-2.2.1-1.fc18.x86_64 conflicts with file from packag
Brendan,
On 2013-06-28 23:47, Brendan Jones wrote:
On 06/28/2013 03:32 PM, Philip Rhoades wrote:
People,
This command:
yum groupinstall development-tools
fails with these errors:
Transaction Check Error:
file /usr/share/locale/en/LC_MESSAGES/systemtap.mo from install of
systemtap-dev
why does "yum --enablerepo=updates-testing -q check-update --security"
today the first time show a kernel built a week ago?
this is *way* too long to get it in *updates-testing* and after that
wait forever to go to stable while 3.9.8 is still built, and new builts
especially security relevant ones
Dne 28.6.2013 15:04, Jakub Jelinek napsal(a):
On Fri, Jun 28, 2013 at 02:58:12PM +0200, Vít Ondruch wrote:
Dne 25.6.2013 15:41, Vít Ondruch napsal(a):
Is there some common practice, where to place architecture
specific header files? From output of the following command, I
can't see any such pla
On Fri, Jun 28, 2013 at 12:36:24 +0200,
Reindl Harald wrote:
why does "yum --enablerepo=updates-testing -q check-update --security"
today the first time show a kernel built a week ago?
this is *way* too long to get it in *updates-testing* and after that
wait forever to go to stable while 3.9.
Philip Rhoades writes:
> [...]
> yum --exclude=systemtap-sdt-devel* groupinstall development-tools
> still gives the same errors . .
How about a "yum update systemtap\*" first?
- FChE
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Am 28.06.2013 16:49, schrieb Bruno Wolff III:
> On Fri, Jun 28, 2013 at 12:36:24 +0200,
> Reindl Harald wrote:
>> why does "yum --enablerepo=updates-testing -q check-update --security"
>> today the first time show a kernel built a week ago?
>>
>> this is *way* too long to get it in *updates-testi
On Fri, 28 Jun 2013 17:09:43 +0200
Reindl Harald wrote:
...snip...
> which does not explain why 3.9.6 and 3.9.7 was not in updates-testing
> and 3.9.7 got there today, a week after it was built and after 3.9.8
> was built on koji for F17
Only the kernel maintainers can answer that. How about we
On Fri, Jun 28, 2013 at 17:09:43 +0200,
Reindl Harald wrote:
so if the would be a link from koji to give karma i would have
done that last sunday as i installed it on my test-VM and as
said having users testing kernels and many other packages
often before the maintainer knows that the build h
On Fri, Jun 28, 2013 at 2:44 PM, Stephen Gallagher wrote:
> Your best bet would be to add ppc64 to the ExclusiveArch on erlang,
> rebuild it, get it pushed to stable, then the broken deps would make
> it clear what packages were descended from it (and can also be patched
> then to exclude ppc64).
On Thu, Jun 27, 2013 at 07:34:06PM -0400, Jaroslav Reznik wrote:
> At the Fedora 19 Final Go/No-Go Meeting that just occurred, it was
> agreed to Go with the Fedora 19 by Fedora QA, development, release
> engineering and FPM.
979205 got filed yesterday, which makes it incredibly difficult to
inst
Am 28.06.2013 17:42, schrieb Kevin Fenzi:
> On Fri, 28 Jun 2013 17:09:43 +0200
> Reindl Harald wrote:
>> which does not explain why 3.9.6 and 3.9.7 was not in updates-testing
>> and 3.9.7 got there today, a week after it was built and after 3.9.8
>> was built on koji for F17
>
> Only the kernel
On Fri, Jun 28, 2013 at 12:01 PM, Reindl Harald wrote:
>
>
> Am 28.06.2013 17:42, schrieb Kevin Fenzi:
>> On Fri, 28 Jun 2013 17:09:43 +0200
>> Reindl Harald wrote:
>>> which does not explain why 3.9.6 and 3.9.7 was not in updates-testing
>>> and 3.9.7 got there today, a week after it was built a
On Fri, 28 Jun 2013 17:00:40 +0100
Matthew Garrett wrote:
> 979205 got filed yesterday, which makes it incredibly difficult to
> install F19 on Macs while keeping OS X. This is rather frustrating,
> since Fedora's the only distribution with any significant support for
> running on Apple hardwa
Am 28.06.2013 18:13, schrieb Josh Boyer:
>> if i install kernel from koji on several machines and
>> have a option to give karma if it works it would be in
>> any case a useful information for the maintainers which
>> is indepedent from what they desired intentionally
>
> You can always email us
On Fri, Jun 28, 2013 at 10:25:58AM -0600, Kevin Fenzi wrote:
> - Say we ground all the wheels to a halt and slipped for this bug.
> Where to do we draw the line? If someone comes up with a bug at
> 9:50am on release morning, do we cancel everything? There has to be a
> point where we say "so
A file has been added to the lookaside cache for perl-Regexp-Grammars:
a87a0204466d3e833f8e826c3eb75ebf Regexp-Grammars-1.030.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.
On Fri, 2013-06-28 at 17:00 +0100, Matthew Garrett wrote:
> On Thu, Jun 27, 2013 at 07:34:06PM -0400, Jaroslav Reznik wrote:
> > At the Fedora 19 Final Go/No-Go Meeting that just occurred, it was
> > agreed to Go with the Fedora 19 by Fedora QA, development, release
> > engineering and FPM.
>
> 97
Quick summary from our meeting today- we will be shipping Fedora 19 for ARM on
July 2nd.
This marks a significant milestone for ARM, being our first release that will
ship alongside
the primary architectures on day one. Many thanks to those who made this
possible.
Thanks to those that were
On Fri, Jun 28, 2013 at 1:13 PM, Adam Williamson wrote:
> There is another 'workaround' you haven't considered: we can simply
> build an updates.img that fixes the issue (or works around it, by
> ditching the commit from 19.13.10 that apparently broke this case), and
> link to that from the common
2013-06-27 20:57, Elio Maldonado Batiz skrev:
> I brought this up with the nss/nspr team upstream. Kai added a good
> explanation for them and proposedchanging the naming scheme two use
> three numbersalwaysas the long term solution. Until that is accepted and
> implemented upstream option (1) is a
On Fri, 2013-06-28 at 13:19 -0400, Josh Boyer wrote:
> On Fri, Jun 28, 2013 at 1:13 PM, Adam Williamson wrote:
> > There is another 'workaround' you haven't considered: we can simply
> > build an updates.img that fixes the issue (or works around it, by
> > ditching the commit from 19.13.10 that ap
If at 9:50am on release morning, aliens threatened to blow up the
world if we shipped, we'd certainly do something about it.
But it would be insane to expect us to *document* that we'd do
something about it.
IMHO it's perfectly reasonable for documented policy to simply say
"bugs after this poin
On Thu, Jun 27, 2013 at 11:24:07PM -0700, Adam Williamson wrote:
> On Thu, 2013-06-27 at 18:41 -0400, Colin Walters wrote:
> > On Thu, 2013-06-27 at 23:38 +0200, Lennart Poettering wrote:
> >
> > > Why would you want this? I mean, we rate-limit per-service anyway, so
> > > the issue of one app flo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 01:24 PM, Adam Williamson wrote:
> On Fri, 2013-06-28 at 13:19 -0400, Josh Boyer wrote:
>> On Fri, Jun 28, 2013 at 1:13 PM, Adam Williamson
>> wrote:
>>> There is another 'workaround' you haven't considered: we can
>>> simply build an up
On Fri, Jun 28, 2013 at 1:31 PM, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 06/28/2013 01:24 PM, Adam Williamson wrote:
>> On Fri, 2013-06-28 at 13:19 -0400, Josh Boyer wrote:
>>> On Fri, Jun 28, 2013 at 1:13 PM, Adam Williamson
>>> wrote:
There is anot
On Fri, 2013-06-28 at 13:31 -0400, Stephen Gallagher wrote:
> On 06/28/2013 01:24 PM, Adam Williamson wrote:
> > On Fri, 2013-06-28 at 13:19 -0400, Josh Boyer wrote:
> >> On Fri, Jun 28, 2013 at 1:13 PM, Adam Williamson
> >> wrote:
> >>> There is another 'workaround' you haven't considered: we can
On Fri, Jun 28, 2013 at 01:26:52PM -0400, DJ Delorie wrote:
>
> If at 9:50am on release morning, aliens threatened to blow up the
> world if we shipped, we'd certainly do something about it.
>
> But it would be insane to expect us to *document* that we'd do
> something about it.
Why? "Beyond thi
On Fri, Jun 28, 2013 at 6:33 PM, Adam Williamson wrote:
> On Fri, 2013-06-28 at 13:31 -0400, Stephen Gallagher wrote:
>> On 06/28/2013 01:24 PM, Adam Williamson wrote:
>> > On Fri, 2013-06-28 at 13:19 -0400, Josh Boyer wrote:
>> >> On Fri, Jun 28, 2013 at 1:13 PM, Adam Williamson
>> >> wrote:
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/28/2013 01:33 PM, Adam Williamson wrote:
> On Fri, 2013-06-28 at 13:31 -0400, Stephen Gallagher wrote:
>> On 06/28/2013 01:24 PM, Adam Williamson wrote:
>>> On Fri, 2013-06-28 at 13:19 -0400, Josh Boyer wrote:
On Fri, Jun 28, 2013 at 1:13 PM
On Fri, Jun 28, 2013 at 10:13:15AM -0700, Adam Williamson wrote:
> Well, I'd say _limited_ compatibility. We've had all kinds of bugs in
> Mac support in, well, pretty much all previous releases too. It's not as
> if we have a track record of excellent support, we have a track record
> of 'you can
On Fri, 2013-06-28 at 18:40 +0100, Matthew Garrett wrote:
> On Fri, Jun 28, 2013 at 10:13:15AM -0700, Adam Williamson wrote:
>
> > Well, I'd say _limited_ compatibility. We've had all kinds of bugs in
> > Mac support in, well, pretty much all previous releases too. It's not as
> > if we have a tra
On Fri, Jun 28, 2013 at 01:18:59PM -0400, Paul Whalen wrote:
>
> Quick summary from our meeting today- we will be shipping Fedora 19 for ARM
> on July 2nd.
>
> This marks a significant milestone for ARM, being our first release that will
> ship alongside
> the primary architectures on day one
On Fri, Jun 28, 2013 at 10:38 AM, Matthew Garrett wrote:
> On Fri, Jun 28, 2013 at 01:26:52PM -0400, DJ Delorie wrote:
>>
>> If at 9:50am on release morning, aliens threatened to blow up the
>> world if we shipped, we'd certainly do something about it.
>>
>> But it would be insane to expect us to
On Fri, Jun 28, 2013 at 10:43:33AM -0700, Adam Williamson wrote:
> With all respect, the bug reports and blogs I've read would not lead me
> to support that assertion.
With all respect, bug numbers.
--
Matthew Garrett | mj...@srcf.ucam.org
--
devel mailing list
devel@lists.fedoraproject.org
ht
On Fri, 28 Jun 2013 10:46:51 -0700
Richard Vickery wrote:
> On Fri, Jun 28, 2013 at 10:38 AM, Matthew Garrett
> wrote:
> > On Fri, Jun 28, 2013 at 01:26:52PM -0400, DJ Delorie wrote:
> >>
> >> If at 9:50am on release morning, aliens threatened to blow up the
> >> world if we shipped, we'd certai
On Jun 28, 2013, at 10:26 AM, DJ Delorie wrote:
> If at 9:50am on release morning, aliens threatened to blow up the
> world if we shipped, we'd certainly do something about it.
So what you're saying is that you negotiate with terrorists? :-p
On a more serious note, though it hasn't been a foc
2013/6/28 Volker Fröhlich :
> On 27/06/13 17:31, Orion Poplawski wrote:
>>
>> On 06/26/2013 08:01 AM, Volker Fröhlich wrote:
>>>
>>>
>>> GDAL is currently broken because it needs a rebuild for Poppler, but the
>>> Texlive build is broken, as far as I can see.
>>
>>
>> texlive has now been rebuilt.
On 06/28/2013 01:31 PM, Stephen Gallagher wrote:
Yee, I just _love_ me some Macs. Thanks; I'll take that into
account for commonbugs. When did Macs stop having ethernet ports?
When the MacBook Air became the flagship Mac.
We just got a MacBook Air and it came with a Thunderbolt pigtail
Eth
> So what you're saying is that you negotiate with terrorists? :-p
"Anyone else want to negotiate?"
(sorry, couldn't resist ;)
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Jun 28, 2013, at 10:39 AM, Peter Robinson wrote:
>
> I don't think any of the thunderbolt equipped MBPs (or maybe the later
> ones) have them. The thunderbolt ethernet adapters apparently work if
> you plug them in before you power them on and presumably all the usb
> ethernet adapters would
Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) said:
> Splitting is controlled by SplitMode=
>
> Controls whether to split up journal files per user. One of "login",
> "uid" and "none". If "login" each logged in user will get his own
> journal files, but systemd user IDs will log into the
On Jun 28, 2013, at 11:14 AM, Przemek Klosowski
wrote:
> On 06/28/2013 01:31 PM, Stephen Gallagher wrote:
>
>>> Yee, I just _love_ me some Macs. Thanks; I'll take that into
>>> account for commonbugs. When did Macs stop having ethernet ports?
>>
>> When the MacBook Air became the flagship Ma
On Fri, Jun 28, 2013 at 07:27:30PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> Splitting is controlled by SplitMode=
> Controls whether to split up journal files per user. One of "login",
> "uid" and "none". If "login" each logged in user will get his own
> journal files, but systemd user IDs
On Fri, Jun 28, 2013 at 02:46:25PM -0400, Matthew Miller wrote:
> On Fri, Jun 28, 2013 at 07:27:30PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> > Splitting is controlled by SplitMode=
> > Controls whether to split up journal files per user. One of "login",
> > "uid" and "none". If "login" each
On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett wrote:
> and we have no history of producing updated
> install images.
Is there *any* reason why we can't? This sounds like a reasonable
thing to do. Just because we have not done it in the past is not a
reason not to.
--
devel mailing list
devel@
On Fri, Jun 28, 2013 at 6:25 PM, Kevin Fenzi wrote:
> it makes sense from a logistic standpoint.
But from any other POV it makes no sense. There is no reason why we
cannot produce and ship updated images if we find a bug that is
important enough.
--
devel mailing list
devel@lists.fedoraprojec
On Fri, 2013-06-28 at 22:13 +0200, drago01 wrote:
> On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett wrote:
> > and we have no history of producing updated
> > install images.
>
> Is there *any* reason why we can't? This sounds like a reasonable
> thing to do. Just because we have not done it in
On Fri, 28 Jun 2013 22:14:51 +0200
drago01 wrote:
> On Fri, Jun 28, 2013 at 6:25 PM, Kevin Fenzi wrote:
>
> > it makes sense from a logistic standpoint.
>
> But from any other POV it makes no sense. There is no reason why we
> cannot produce and ship updated images if we find a bug that is
>
On Fri, Jun 28, 2013 at 09:48:58PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> 'uid' as default doesn't make sense, at least with the current way of accesing
> logs. It is really nice to be able to view messages about a service
> interleaved from various sources. Now when you say 'journalctl -u htt
On Fri, Jun 28, 2013 at 10:32 PM, Kevin Fenzi wrote:
> On Fri, 28 Jun 2013 22:14:51 +0200
> drago01 wrote:
>
>> On Fri, Jun 28, 2013 at 6:25 PM, Kevin Fenzi wrote:
>>
>> > it makes sense from a logistic standpoint.
>>
>> But from any other POV it makes no sense. There is no reason why we
>> ca
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 wrote:
> On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
> wrote:
> > and we have no history of producing updated
> > install images.
>
> Is there *any* reason why we can't? This sounds like a reasonable
> thing to do. Just because we have not done it
On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi wrote:
> On Fri, 28 Jun 2013 22:13:09 +0200
> drago01 wrote:
>
>> On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
>> wrote:
>> > and we have no history of producing updated
>> > install images.
>>
>> Is there *any* reason why we can't? This sounds l
Hi,
- Original Message -
> From: Lennart Poettering
> Subject: Re: logrotate(8) and copytruncate as default
>
> journald is the only writer, it doesn't need locking. The changes it
> does are done in a way so that concurrent readers will either see the
> changes or not, but never half-w
On 28 June 2013 14:43, drago01 wrote:
> On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi wrote:
> > On Fri, 28 Jun 2013 22:13:09 +0200
> > drago01 wrote:
> >
> > * Mirrors willing to have another pile of release bits
> > * Marketing/press folks willing to put together stuff for the release
> > * D
On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
> On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi wrote:
> > On Fri, 28 Jun 2013 22:13:09 +0200
> > drago01 wrote:
> >
> >> On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
> >> wrote:
> >> > and we have no history of producing updated
> >> > insta
FChE,
On 2013-06-29 01:24, f...@redhat.com wrote:
Philip Rhoades writes:
[...]
yum --exclude=systemtap-sdt-devel* groupinstall development-tools
still gives the same errors . .
How about a "yum update systemtap\*" first?
That did it! - Good to remember . .
Thanks,
Phil.
--
Philip Rhoa
On Jun 28, 2013, at 10:39 AM, Matthew Garrett wrote:
> On Fri, Jun 28, 2013 at 10:25:58AM -0600, Kevin Fenzi wrote:
>
>> - Say we ground all the wheels to a halt and slipped for this bug.
>> Where to do we draw the line? If someone comes up with a bug at
>> 9:50am on release morning, do we ca
On Jun 28, 2013, at 11:39 AM, Peter Robinson wrote:
>
> I don't think any of the thunderbolt equipped MBPs (or maybe the later
> ones) have them. The thunderbolt ethernet adapters apparently work if
> you plug them in before you power them on and presumably all the usb
> ethernet adapters would
On Fri, 2013-06-28 at 15:42 -0600, Chris Murphy wrote:
> But the final release series of RC's happen very quickly, and any
> allowed change is by definition significant (i.e. necessary) or it
> simply wouldn't happen, but that also makes the change higher risk
> than other changes. So I think more
On Fri, Jun 28, 2013 at 11:16 PM, Adam Williamson wrote:
> On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
>> On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi wrote:
>> > On Fri, 28 Jun 2013 22:13:09 +0200
>> > drago01 wrote:
>> >
>> >> On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
>> >> wrot
On Sat, 2013-06-29 at 00:24 +0200, drago01 wrote:
> On Fri, Jun 28, 2013 at 11:16 PM, Adam Williamson wrote:
> > On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
> >> On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi wrote:
> >> > On Fri, 28 Jun 2013 22:13:09 +0200
> >> > drago01 wrote:
> >> >
> >>
On Fri, 2013-06-28 at 15:14 -0300, Paulo César Pereira de Andrade wrote:
> 2013/6/28 Volker Fröhlich :
> > On 27/06/13 17:31, Orion Poplawski wrote:
> >>
> >> On 06/26/2013 08:01 AM, Volker Fröhlich wrote:
> >>>
> >>>
> >>> GDAL is currently broken because it needs a rebuild for Poppler, but the
>
On Fri, 28.06.13 14:46, Matthew Miller (mat...@fedoraproject.org) wrote:
> On Fri, Jun 28, 2013 at 07:27:30PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> > Splitting is controlled by SplitMode=
> > Controls whether to split up journal files per user. One of "login",
> > "uid" and "none". If "l
On Fri, 28.06.13 16:33, Matthew Miller (mat...@fedoraproject.org) wrote:
> On Fri, Jun 28, 2013 at 09:48:58PM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> > 'uid' as default doesn't make sense, at least with the current way of
> > accesing
> > logs. It is really nice to be able to view messages ab
There still seems to be an issue with the update descriptions that we
present in PackageKit. A lot of people just write "update to version
x.y.z" which is not great, but a whole lot better than some of the ones
we've been seeing recently. For example, from two updates I got today:
* "Not tested lo
On Jun 28, 2013, at 4:20 PM, Adam Williamson wrote:
>
> I think you may be labouring under a bit of a misapprehension about what
> should be tested, here. The distinction between a TC and an RC is not
> large. An RC can only happen after freeze and must have all blockers
> fixed: if a build afte
On 2013-06-28 17:44, Michael Catanzaro wrote:
There still seems to be an issue with the update descriptions that we
present in PackageKit. A lot of people just write "update to version
x.y.z" which is not great, but a whole lot better than some of the ones
we've been seeing recently. For example,
On Fri, 28.06.13 01:17, Jan Kaluza (jkal...@redhat.com) wrote:
> > > Why would you want this? I mean, we rate-limit per-service anyway, so
> > > the issue of one app flooding evreything else should be mostly
> > > non-existant. And hence, what you are asking for is some policy control
> > > about
On Sat, 29.06.13 04:46, P J P (pj.pan...@yahoo.co.in) wrote:
>
> Hi,
> - Original Message -
> > From: Lennart Poettering
> > Subject: Re: logrotate(8) and copytruncate as default
> >
> > journald is the only writer, it doesn't need locking. The changes it
> > does are done in a way so
On 2013-06-28 17:51, Chris Murphy wrote:
On Jun 28, 2013, at 4:20 PM, Adam Williamson
wrote:
I think you may be labouring under a bit of a misapprehension about
what
should be tested, here. The distinction between a TC and an RC is not
large. An RC can only happen after freeze and must have
On Sex, 2013-06-28 at 14:16 -0700, Adam Williamson wrote:
> On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
> > On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi wrote:
> > > On Fri, 28 Jun 2013 22:13:09 +0200
> > > drago01 wrote:
> > >
> > >> On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
> > >
On 29/06/2013, at 7:12, Chris Murphy wrote:
>
> On Jun 28, 2013, at 10:39 AM, Matthew Garrett wrote:
>
>> On Fri, Jun 28, 2013 at 10:25:58AM -0600, Kevin Fenzi wrote:
>>
>>> - Say we ground all the wheels to a halt and slipped for this bug.
>>> Where to do we draw the line? If someone comes
On Sat, Jun 29, 2013 at 02:42:11AM +0200, Lennart Poettering wrote:
> That's why we are so strong on filtering the dataset when you look at
> it. May I recommend watching this video?
> https://www.youtube.com/watch?v=i4CACB7paLc
I was there at that talk. :)
I think the journal is cool. It does gr
>
>
>
> We do actually have more than a few people with Macs: you, Fedora QA's Brno
> team, mjg59, and I think someone on anaconda team has one. It would be nice
> if at least one of the above could test each *C, though I realize bare metal
> testing is a PITA and I hate it myself.
>
I do b
91 matches
Mail list logo
