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 flooding evreything else should be mostly
non-existant. And hence, what you are
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.
We've got a working GDAL build again.
Volker
--
On Thu, 27 Jun 2013 20:52:25 -0500
Dennis Gilmore den...@ausil.us 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
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:
Hello Jan,
- Original Message -
From: Jan Kaluza jkal...@redhat.com
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
-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
to
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
-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. This
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
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 store pidfile in
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
-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 tmpfilesd
-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 have
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, you'd
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 would
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 p...@pricom.com.au 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
-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
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
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
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
On Fri, Jun 28, 2013 at 12:36:24 +0200,
Reindl Harald h.rei...@thelounge.net 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
Philip Rhoades p...@pricom.com.au 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
Am 28.06.2013 16:49, schrieb Bruno Wolff III:
On Fri, Jun 28, 2013 at 12:36:24 +0200,
Reindl Harald h.rei...@thelounge.net 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
On Fri, 28 Jun 2013 17:09:43 +0200
Reindl Harald h.rei...@thelounge.net 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
On Fri, Jun 28, 2013 at 17:09:43 +0200,
Reindl Harald h.rei...@thelounge.net 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
On Fri, Jun 28, 2013 at 2:44 PM, Stephen Gallagher sgall...@redhat.com 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
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
Am 28.06.2013 17:42, schrieb Kevin Fenzi:
On Fri, 28 Jun 2013 17:09:43 +0200
Reindl Harald h.rei...@thelounge.net 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
On Fri, Jun 28, 2013 at 12:01 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 28.06.2013 17:42, schrieb Kevin Fenzi:
On Fri, 28 Jun 2013 17:09:43 +0200
Reindl Harald h.rei...@thelounge.net wrote:
which does not explain why 3.9.6 and 3.9.7 was not in updates-testing
and 3.9.7 got there
On Fri, 28 Jun 2013 17:00:40 +0100
Matthew Garrett mj...@srcf.ucam.org 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
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 saying
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 sorry,
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
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.
979205 got
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 awill...@redhat.com 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
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 awill...@redhat.com 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
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
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 flooding
-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
awill...@redhat.com wrote:
There is another 'workaround' you haven't considered: we can
simply
On Fri, Jun 28, 2013 at 1:31 PM, Stephen Gallagher sgall...@redhat.com 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
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
awill...@redhat.com wrote:
There is another 'workaround' you haven't considered:
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 this
On Fri, Jun 28, 2013 at 6:33 PM, Adam Williamson awill...@redhat.com 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
-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, Adam
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 track
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. Many
On Fri, Jun 28, 2013 at 10:38 AM, Matthew Garrett mj...@srcf.ucam.org 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
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
On Fri, 28 Jun 2013 10:46:51 -0700
Richard Vickery richard.vicker...@gmail.com wrote:
On Fri, Jun 28, 2013 at 10:38 AM, Matthew Garrett
mj...@srcf.ucam.org 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
On Jun 28, 2013, at 10:26 AM, DJ Delorie d...@redhat.com 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
2013/6/28 Volker Fröhlich volke...@gmx.at:
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
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 pbrobin...@gmail.com 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
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 system
On Jun 28, 2013, at 11:14 AM, Przemek Klosowski przemek.klosow...@nist.gov
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
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 will log
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 logged in
On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett mj...@srcf.ucam.org 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
On Fri, Jun 28, 2013 at 6:25 PM, Kevin Fenzi ke...@scrye.com 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
On Fri, 2013-06-28 at 22:13 +0200, drago01 wrote:
On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett mj...@srcf.ucam.org 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
On Fri, 28 Jun 2013 22:14:51 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 6:25 PM, Kevin Fenzi ke...@scrye.com 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
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
On Fri, Jun 28, 2013 at 10:32 PM, Kevin Fenzi ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:14:51 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 6:25 PM, Kevin Fenzi ke...@scrye.com wrote:
it makes sense from a logistic standpoint.
But from any other POV it makes no
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
mj...@srcf.ucam.org 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
On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
mj...@srcf.ucam.org wrote:
and we have no history of producing updated
install images.
Is there *any*
Hi,
- Original Message -
From: Lennart Poettering mzerq...@0pointer.de
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,
On 28 June 2013 14:43, drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 drag...@gmail.com wrote:
* Mirrors willing to have another pile of release bits
* Marketing/press folks willing to put
On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 6:00 PM, Matthew Garrett
mj...@srcf.ucam.org wrote:
and we have no
FChE,
On 2013-06-29 01:24, f...@redhat.com wrote:
Philip Rhoades p...@pricom.com.au 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,
On Jun 28, 2013, at 10:39 AM, Matthew Garrett mj...@srcf.ucam.org 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
On Jun 28, 2013, at 11:39 AM, Peter Robinson pbrobin...@gmail.com 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
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 awill...@redhat.com wrote:
On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at
On Sat, 2013-06-29 at 00:24 +0200, drago01 wrote:
On Fri, Jun 28, 2013 at 11:16 PM, Adam Williamson awill...@redhat.com wrote:
On Fri, 2013-06-28 at 22:43 +0200, drago01 wrote:
On Fri, Jun 28, 2013 at 10:36 PM, Kevin Fenzi ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:13:09 +0200
On Fri, 2013-06-28 at 15:14 -0300, Paulo César Pereira de Andrade wrote:
2013/6/28 Volker Fröhlich volke...@gmx.at:
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 login each
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 about a
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
On Jun 28, 2013, at 4:20 PM, Adam Williamson awill...@redhat.com 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:
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 what to
On Sat, 29.06.13 04:46, P J P (pj.pan...@yahoo.co.in) wrote:
Hi,
- Original Message -
From: Lennart Poettering mzerq...@0pointer.de
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
On 2013-06-28 17:51, Chris Murphy wrote:
On Jun 28, 2013, at 4:20 PM, Adam Williamson awill...@redhat.com
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
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 ke...@scrye.com wrote:
On Fri, 28 Jun 2013 22:13:09 +0200
drago01 drag...@gmail.com wrote:
On Fri, Jun 28, 2013 at 6:00 PM,
On 29/06/2013, at 7:12, Chris Murphy li...@colorremedies.com wrote:
On Jun 28, 2013, at 10:39 AM, Matthew Garrett mj...@srcf.ucam.org 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
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
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 bare
https://bugzilla.redhat.com/show_bug.cgi?id=844988
--- Comment #1 from lionel.c...@cern.ch ---
The latest version of Test::Class on CPAN is now 0.39.
This is the version to use everywhere. Please upgrade in Fedora as well as
EPEL5 and EPEL6.
--
You are receiving this mail because:
You are on
https://bugzilla.redhat.com/show_bug.cgi?id=979143
Petr Pisar ppi...@redhat.com changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1
A file has been added to the lookaside cache for perl-Digest-SHA:
7e9d19d00a66363012a6fdb3ae3ffd22 Digest-SHA-5.85.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
commit 4b6c557a95836d21ac898dd851350bc950ddf523
Author: Petr Písař ppi...@redhat.com
Date: Fri Jun 28 10:48:08 2013 +0200
5.85 bump
.gitignore |1 +
perl-Digest-SHA.spec | 14 +-
sources |2 +-
3 files changed, 15 insertions(+), 2 deletions(-)
Summary of changes:
4b6c557... 5.85 bump (*)
(*) This commit already existed in another branch; no separate mail sent
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
commit b186646a945e0d41dfccd035710c521b0961a71a
Author: Petr Písař ppi...@redhat.com
Date: Fri Jun 28 14:12:28 2013 +0200
Deal with calling destructor multiple times
Digest-SHA-5.84-repeated_shaclose.patch | 30 ++
perl-Digest-SHA.spec|
perl-Bio-ASN1-EntrezGene has broken dependencies in the F-19 tree:
On x86_64:
perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires
perl(Bio::Index::AbstractSeq)
On i386:
perl-Bio-ASN1-EntrezGene-1.091-17.fc19.noarch requires
perl(Bio::Index::AbstractSeq)
Please resolve this
1 - 100 of 110 matches
Mail list logo
