On Wed Jul 3 02:44:42 UTC 2013, Matthew Miller wrote:
On Tue, Jul 02, 2013 at 03:47:25PM -0700, Garrett Holmstrom wrote:
Hi, folks,
Since a large number of people have requested new features in
python-boto I'd like to update it from version 2.5.2 to the current
version, 2.9.6. API-wise it
On Wed, Jul 3, 2013 at 7:33 PM, Kevin Fenzi ke...@scrye.com wrote:
On Wed, 3 Jul 2013 18:58:56 -0700
T.C. Hollingsworth tchollingswo...@gmail.com wrote:
Hi all! I filed a ticket [1] in rel-eng's trac about this because I'm
fairly certain something weird happened here, but just in case I'm
On 07/03/2013 07:42 AM, Alex G. wrote:
On 07/02/2013 08:28 PM, Neal Becker wrote:
Not d/l speed related. I just want to share. I update a very fast 8 core
server, with a conventional disk drive. Took 2-3 hours, not including d/l.
I update my laptop which has an ssd (and MORE packages).
On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal dan.mas...@gmail.com wrote:
On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten p...@luyten.fr wrote:
Not sure if it makes any sense but maybe could we have something like
freeze tag changes until desc is better.
I propose this because testers will
On Wed, Jul 3, 2013 at 9:32 AM, drago01 drag...@gmail.com wrote:
On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal dan.mas...@gmail.com wrote:
On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten p...@luyten.fr wrote:
Not sure if it makes any sense but maybe could we have something like
freeze tag
Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit :
On Wed, Jul 3, 2013 at 9:32 AM, drago01 drag...@gmail.com wrote:
On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal
dan.mas...@gmail.com wrote:
On Mon, Jul 1, 2013 at 2:52 PM, Pierre-Yves Luyten
On Wed, Jul 3, 2013 at 9:47 AM, Michael Scherer m...@zarb.org wrote:
Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit :
On Wed, Jul 3, 2013 at 9:32 AM, drago01 drag...@gmail.com wrote:
On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal
dan.mas...@gmail.com
Le mercredi 03 juillet 2013 à 09:54 +0200, Johannes Lips a écrit :
On Wed, Jul 3, 2013 at 9:47 AM, Michael Scherer m...@zarb.org wrote:
Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a
écrit :
On Wed, Jul 3, 2013 at 9:32
Hi,
There is a new simple way to track changes in API/ABI of system
libraries using a new ABI dumper [1] tool. Just compile two library
versions with -g additional option (to contain DWARF debug info) or take
them from the appropriate debug packages and create ABI dumps of both:
On 07/03/2013 09:59 AM, Panu Matilainen wrote:
On 07/03/2013 07:42 AM, Alex G. wrote:
On 07/02/2013 08:28 PM, Neal Becker wrote:
Not d/l speed related. I just want to share. I update a very fast 8
core
server, with a conventional disk drive. Took 2-3 hours, not
including d/l.
I update my
On 07/03/2013 03:23 AM, Panu Matilainen wrote:
On 07/03/2013 09:59 AM, Panu Matilainen wrote:
On 07/03/2013 07:42 AM, Alex G. wrote:
On 07/02/2013 08:28 PM, Neal Becker wrote:
Not d/l speed related. I just want to share. I update a very fast 8
core
server, with a conventional disk drive.
On 07/03/2013 11:29 AM, Alex G. wrote:
On 07/03/2013 03:23 AM, Panu Matilainen wrote:
On 07/03/2013 09:59 AM, Panu Matilainen wrote:
On 07/03/2013 07:42 AM, Alex G. wrote:
On 07/02/2013 08:28 PM, Neal Becker wrote:
Not d/l speed related. I just want to share. I update a very fast 8
core
On 3 July 2013 08:47, Michael Scherer m...@zarb.org wrote:
Le mercredi 03 juillet 2013 à 09:44 +0200, Johannes Lips a écrit :
On Wed, Jul 3, 2013 at 9:32 AM, drago01 drag...@gmail.com wrote:
On Mon, Jul 1, 2013 at 11:54 PM, Dan Mashal
dan.mas...@gmail.com wrote:
On
Hi everyone,
I have just submitted a package review request for xen-tools
(http://www.xen-tools.org/software/xen-tools/) here:
https://bugzilla.redhat.com/show_bug.cgi?id=980851
From the same website, you can easily reach other Xen related tools,
like xen-shell, and also rinse, which I plan to
Just want to say I updated 2 machines using fedup, and everything seems to have
gone perfectly.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote:
Richard W.M. Jones wrote:
%changelog -f changelog_file
%changelog -g git_repo
And, I suppose:
%changelog -s Subversion_repo
%changelog -c CVS_repo
%changelog -m Monotone_repo
%changelog -h Mercurial_repo
%changelog -a
On Wed, 2013-07-03 at 09:32 +0200, drago01 wrote:
This is also a perfect example of useless does not fix bug x karma.
If it is not *worse* then the previous package there is no reason to
give it negative karma.
Yes, that is a problem too. Particularly so with selinux updates.
But getting back
Compose started at Wed Jul 3 08:15:02 UTC 2013
Broken deps for x86_64
--
[avgtime]
avgtime-0-0.6.git20130201.fc20.x86_64 requires
libphobos-ldc.so.60()(64bit)
[contour]
contour-0.3-2.fc19.x86_64 requires
I've got it packaged up and ready for review request.
I'm assuming there is interest in automating this.
Thanks,
Richard
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/02/2013 09:02 AM, Michael Schwendt wrote:
On Mon, 01 Jul 2013 23:28:00 +0200, Antonio Trande wrote:
Then let's not hack the paths, but find out why %find_lang doesn't
find the files. If %name is not part of the filenames, normally
you
On 07/01/2013 03:52 PM, Orion Poplawski wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=959696. Renaming ht to
t4ht was clearly the wrong thing to do. I'm reverting it for now.
texlive and gnuplot now have been rebuilt in rawhide.
--
Orion Poplawski
Technical Manager
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings.
This is a reminder email about the end of life process for Fedora 17.
Fedora 17 will reach end of life on 2013-07-30, and no further updates
will be pushed out after that time. Additionally, with the recent
release of Fedora 19, no new
The Fedora Secondary Arch Team for Power is delighted to announce the
release of Fedora 19 (Schrödinger's Cat) for Power architecture. Open
the box and take a look for yourself!
Fedora is a leading-edge, free and open source operating system that
continues to deliver innovative features to
Review request submitted:
https://bugzilla.redhat.com/show_bug.cgi?id=980937
It took me a bit to work some txt2man magic to get a decent manpage.
Thanks,
Richard
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On 07/03/2013 03:12 PM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote:
Richard W.M. Jones wrote:
%changelog -f changelog_file
%changelog -g git_repo
And, I suppose:
%changelog -s Subversion_repo
%changelog -c CVS_repo
%changelog -m Monotone_repo
On Wed, Jul 03, 2013 at 06:21:51PM +0300, Panu Matilainen wrote:
On 07/03/2013 03:12 PM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote:
Richard W.M. Jones wrote:
%changelog -f changelog_file
%changelog -g git_repo
And, I suppose:
%changelog -s
Am 03.07.2013 09:54, schrieb Johannes Lips:
Could be, but if the still broken bugs are going to be closed, when the
update becomes stable
since when do bugs get magically closed?
signature.asc
Description: OpenPGP digital signature
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, Jul 03, 2013 at 12:25:19AM -0500, Alex G. wrote:
aptitude has something called deferred ldconfig processing, and
annoyingly, aptitude updates faster than yum. I've always wondered how
yum/rpm can be smartized to speed things up this way. But this
discussion is for a brighter day.
Well,
On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote:
Could be, but if the still broken bugs are going to be closed, when the
update becomes stable
since when do bugs get magically closed?
Since 2007 or so?
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
Hi everybody,
Yesterday we made a simultaneous release of F19 on ARM and x86, a first
ever. Thank you to everybody who contributed- it was truly a great team
effort, and it produced the best Fedora on ARM release yet.
It's a holiday week in the US and Canada and half the members of the ARM
Hi,
I've submitted a package review request for rpmgrill:
https://bugzilla.redhat.com/show_bug.cgi?id=980960
rpmgrill is yet another QA tool for catching problems in koji builds.
About me: I've been writing UNIXy software tools in one form or
another since the late 80s, open-sourcing when
On Mon, 01 Jul 2013 01:35:14 +0200
Sandro Mani manisan...@gmail.com wrote:
Hello all,
As described here [1], the upcoming python-pillow 2.2 will break
import _imaging, and from PIL.Image import core as _imaging
should be used instead). This does not break backwards compatibility
with
https://fedorahosted.org/389/ticket/47384
https://fedorahosted.org/389/attachment/ticket/47384/0001-Ticket-47384-Plugin-library-path-validation.3.patch
Description: commit a4b81c0ae59a4246d2d44790efea093a62fc972c
https://fedorahosted.org/389/changeset/a4b81c0ae59a4246d2d44790efea093a62fc972c/
I've left some candies there :-D
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the lateness of this email. FESCo meeting *IS* scheduled for
today.
Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.
To convert UTC to your local
On Wed, Jul 3, 2013 at 1:04 PM, Stephen Gallagher sgall...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the lateness of this email. FESCo meeting *IS* scheduled for
today.
Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at
I've just built python-setuptools-0.7.7 for rawhide. As mentioned in the
Changes Planning page:
https://fedoraproject.org/wiki/Changes/Python_setuptools_0.7#Summary
This is a switch of code base so there is the possibility of failures
however it isn't a major change of API so it should hopefully
Am 03.07.2013 18:21, schrieb Matthew Miller:
On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote:
Could be, but if the still broken bugs are going to be closed, when the
update becomes stable
since when do bugs get magically closed?
Since 2007 or so?
what sense makes this?
a
On Wed, 03 Jul 2013 19:38:00 +0200
Reindl Harald h.rei...@thelounge.net wrote:
Am 03.07.2013 18:21, schrieb Matthew Miller:
On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote:
Could be, but if the still broken bugs are going to be closed,
when the update becomes stable
Am 03.07.2013 19:54, schrieb Kevin Fenzi:
On Wed, 03 Jul 2013 19:38:00 +0200
Reindl Harald h.rei...@thelounge.net wrote:
a new upstream-release does not implicitly close any bug
on the other hand it makes hardly sense to hold back a update
not fixing all bugreports - this all makes no
On Wed, Jul 3, 2013 at 7:54 PM, Kevin Fenzi ke...@scrye.com wrote:
On Wed, 03 Jul 2013 19:38:00 +0200
Reindl Harald h.rei...@thelounge.net wrote:
Am 03.07.2013 18:21, schrieb Matthew Miller:
On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote:
Could be, but if the still broken
On Jul 2, 2013 2:20 PM, Richard Shaw hobbes1...@gmail.com wrote:
I saw this during the update:
Updating : abrt-libs-2.1.5-1.fc18.x86_64
10/76
cp: cannot create regular file
â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/environâ: No such file or
directory
cp: cannot create regular file
On 2013-07-03 0:54, Johannes Lips wrote:
If it doesn't fix the bugs, the update should fix, it is
appropriate
to give negative karma. Otherwise the bugs would be closed, when
it
becomes stable, but won't be fixed.
That's not what the guidelines say :
On 2013-07-03 1:11, Michael Scherer wrote:
Then we could decide on :
- better process, ie if you happen to notice a bug is not fixed by
update, please reopen it
- better tooling, ie a way to say do not close this bug to bodhi.
Either a message in bodhi, or something on bugzilla side.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
===
#fedora-meeting: FESCO (2013-07-03)
===
Meeting started by sgallagh at 18:01:28 UTC. The full logs are available
at
On 2013-07-03 2:28, Ian Malone wrote:
Tooling issues aside (and it is undesireable that bugs should get
marked fixed if they haven't been) I think this rule is wrong under a
strict reading. If an update claims to fix two bugs and fixes neither
then neither is the *only* change (highlighting is
On 2013-07-03 8:21, Panu Matilainen wrote:
On 07/03/2013 03:12 PM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 12:28:19AM +0200, Björn Persson wrote:
Richard W.M. Jones wrote:
%changelog -f changelog_file
%changelog -g git_repo
And, I suppose:
%changelog -s Subversion_repo
%changelog
On 2013-07-03 10:54, Kevin Fenzi wrote:
On Wed, 03 Jul 2013 19:38:00 +0200
Reindl Harald h.rei...@thelounge.net wrote:
Am 03.07.2013 18:21, schrieb Matthew Miller:
On Wed, Jul 03, 2013 at 10:25:12AM +0200, Reindl Harald wrote:
Could be, but if the still broken bugs are going to be closed,
On Wed, 03 Jul 2013 12:55:11 -0700
Adam Williamson awill...@redhat.com wrote:
As discussed up thread, this is not the current policy and I'd really
prefer people don't do this. -1 is a Serious Thing, not to be used
lightly.
Sorry, you are right.
If an update claims to fix multiple bugs
I initially got abi-compliance-checker into Fedora because one of my
packages does not maintain any sort of API/ABI compatibility or even
versioning for that matter. That way I could always check a new release to
see if any of its dependencies needed to be rebuilt.
Since then, I've started using
On Tue, 02.07.13 10:08, Jean-Marc Pigeon (j...@safe.ca) wrote:
This little project gave satisfactory results with various distributions when
I designed and tested it 2 years ago. First I checked it with a standard
EL6.4 template (400 Megs) under this new kernel (3.9.4, HOST
EL6.4) to see if
On 3 July 2013 20:48, Adam Williamson awill...@redhat.com wrote:
On 2013-07-03 2:28, Ian Malone wrote:
Tooling issues aside (and it is undesireable that bugs should get
marked fixed if they haven't been) I think this rule is wrong under a
strict reading. If an update claims to fix two bugs
On Tue, 02.07.13 16:57, Jean-Marc Pigeon (j...@safe.ca) wrote:
As expected the problem stand on a very small detail (within /etc/fstab)
Not working
/vzgot/ ext4defaults0 0
proc /proc procdefaults0 0
sysfs /sys
On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote:
I initially got abi-compliance-checker into Fedora because one of my
packages does not maintain any sort of API/ABI compatibility or even
versioning for that matter. That way I could always check a new
release to see if any of its
On 03.07.2013 18:49, Kevin Fenzi wrote:
On Mon, 01 Jul 2013 01:35:14 +0200
Sandro Mani manisan...@gmail.com wrote:
Hello all,
As described here [1], the upcoming python-pillow 2.2 will break
import _imaging, and from PIL.Image import core as _imaging
should be used instead). This does not
On 07/03/2013 10:03 PM, Richard Shaw wrote:
I initially got abi-compliance-checker into Fedora because one of my packages
does not maintain any sort of API/ABI compatibility or even versioning for
that
matter. That way I could always check a new release to see if any of its
dependencies
On Wed, 2013-07-03 at 16:33 +0100, Richard W.M. Jones wrote:
SuSE too ...
Rich.
But they reformat everything by hand. For a representative example,
compare:
https://git.gnome.org/browse/evolution/tree/NEWS
with
On Wed, Jul 3, 2013 at 4:33 PM, Sérgio Basto ser...@serjux.com wrote:
On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote:
I initially got abi-compliance-checker into Fedora because one of my
packages does not maintain any sort of API/ABI compatibility or even
versioning for that matter.
IBook. 'Kiomjm
Em 03/07/2013 19:00, Xavier Bachelot xav...@bachelot.org escreveu:
On 07/03/2013 10:03 PM, Richard Shaw wrote:
I initially got abi-compliance-checker into Fedora because one of my
packages
does not maintain any sort of API/ABI compatibility or even versioning
for that
/ lo m'
Em 03/07/2013 21:16, Richard Shaw hobbes1...@gmail.com escreveu:
On Wed, Jul 3, 2013 at 4:33 PM, Sérgio Basto ser...@serjux.com wrote:
On Qua, 2013-07-03 at 15:03 -0500, Richard Shaw wrote:
I initially got abi-compliance-checker into Fedora because one of my
packages does not
This is an extreme example, but after removing the offending headers I got
this:
https://dl.dropboxusercontent.com/u/34775202/compat_reports/ffmpeg/0.10.7_to_1.2.1/compat_report.html
Thanks,
Richard
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, 2013-07-03 at 15:03 -0500, Richard Shaw wrote:
If anyone is curious about it, I don't mind typing up the process I go
through to make the checks. I think I've found a pretty good path of least
resistance method :)
I've never used it, but I'd certainly be interested in reading that if
On Qui, 2013-07-04 at 00:00 +0200, Xavier Bachelot wrote:
On 07/03/2013 10:03 PM, Richard Shaw wrote:
I initially got abi-compliance-checker into Fedora because one of my
packages
does not maintain any sort of API/ABI compatibility or even versioning for
that
matter. That way I could
Le 03/07/2013 22:03, Richard Shaw a écrit :
I initially got abi-compliance-checker into Fedora because one of my
packages does not maintain any sort of API/ABI compatibility or even
versioning for that matter. That way I could always check a new release
to see if any of its dependencies needed
commit eb35a044805c5edf79be78f28bcd93973725d5b6
Author: Jitka Plesnikova jples...@redhat.com
Date: Wed Jul 3 10:06:58 2013 +0200
Specify all dependencies
perl-XML-LibXML.spec | 14 +-
1 files changed, 13 insertions(+), 1 deletions(-)
---
diff --git a/perl-XML-LibXML.spec
A file has been added to the lookaside cache for perl-Tree-DAG_Node:
a6ad9e49800448b2823239276a4530b6 Tree-DAG_Node-1.12.tgz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
commit 695fefa0b9bbf3a3d01f1c7bd455fbe467f88da3
Author: Paul Howarth p...@city-fan.org
Date: Wed Jul 3 10:09:15 2013 +0100
Update to 1.12
- New upstream release 1.12
- Change text in README referring to licence to match text in body of
source,
since it was in
The lightweight tag 'perl-Tree-DAG_Node-1.12-1.fc20' was created pointing to:
695fefa... Update to 1.12
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
A file has been added to the lookaside cache for perl-IO-Socket-SSL:
dcaec234df6c405609fef322f6e0c3f9 IO-Socket-SSL-1.951.tar.gz
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
commit 5289b4544b356a6f0b3c58e3f8d1afb184676940
Author: Paul Howarth p...@city-fan.org
Date: Wed Jul 3 13:04:57 2013 +0100
Update to 1.951
- New upstream release 1.951
(1.950)
- MAJOR BEHAVIOR CHANGE:
- ssl_verify_mode now defaults to verify_peer for client
The lightweight tag 'perl-IO-Socket-SSL-1.95.1-1.fc20' was created pointing to:
5289b45... Update to 1.951
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-devel@lists.fedoraproject.org
perl-PDL has broken dependencies in the rawhide tree:
On x86_64:
perl-PDL-2.4.10-6.fc19.x86_64 requires libgd.so.2()(64bit)
On i386:
perl-PDL-2.4.10-6.fc19.i686 requires libgd.so.2
Please resolve this as soon as possible.
--
Fedora Extras Perl SIG
perl-Bio-ASN1-EntrezGene has broken dependencies in the rawhide 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
perl-Bio-SamTools has broken dependencies in the rawhide tree:
On x86_64:
perl-Bio-SamTools-1.35-2.fc19.x86_64 requires
perl(Bio::SeqFeature::Lite)
perl-Bio-SamTools-1.35-2.fc19.x86_64 requires perl(Bio::PrimarySeq)
On i386:
perl-Bio-SamTools-1.35-2.fc19.i686 requires
https://bugzilla.redhat.com/show_bug.cgi?id=980883
Bug ID: 980883
Summary: perl-DBD-MySQL requires libmysqlclient.so.18 provided
by mariadb.-libs
Product: Fedora
Version: 19
Component: perl-DBD-MySQL
Severity:
https://bugzilla.redhat.com/show_bug.cgi?id=967719
--- Comment #2 from Petr Pisar ppi...@redhat.com ---
What's expected output on the client site?
I have patched perl so that it links all XS modules to libperl.so explicitly in
my private F20 machine, and I do not get any segfaults. Instead I
https://bugzilla.redhat.com/show_bug.cgi?id=967719
--- Comment #3 from Jan Synacek jsyna...@redhat.com ---
All LDAP operations should succeed without any errors. You don't have
sufficient access rights to modify the LDAP database. Running the script as
root should do it.
You should see something
https://bugzilla.redhat.com/show_bug.cgi?id=967719
--- Comment #4 from Petr Pisar ppi...@redhat.com ---
I run it as a non-root. I get much better results as a root:
# ./try.sh
SASL/EXTERNAL authentication started
SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
SASL SSF: 0
commit c788fc6121798b171ca3b687a9b6326344c760f8
Author: Petr Písař ppi...@redhat.com
Date: Wed Jul 3 16:45:08 2013 +0200
Correct changelog entry
perl-XML-LibXML.spec |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/perl-XML-LibXML.spec
commit 8f9ce19eb3e8e68ba9b3714ad033d26a5487fbe7
Author: Jitka Plesnikova jples...@redhat.com
Date: Wed Jul 3 17:15:30 2013 +0200
Change license to CC0
perl-XML-Writer.spec |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
---
diff --git a/perl-XML-Writer.spec
https://bugzilla.redhat.com/show_bug.cgi?id=828819
--- Comment #1 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=867046
--- Comment #12 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=979621
--- Comment #2 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=838700
--- Comment #1 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=890721
--- Comment #1 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=850971
--- Comment #1 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=863303
--- Comment #4 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=818651
--- Comment #4 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=825678
--- Comment #11 from Fedora End Of Life endofl...@fedoraproject.org ---
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It
https://bugzilla.redhat.com/show_bug.cgi?id=967719
--- Comment #5 from Jan Synacek jsyna...@redhat.com ---
(In reply to Petr Pisar from comment #4)
I run it as a non-root. I get much better results as a root:
Yes, that's how the output is supposed to look.
However the server sometimes
---
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-tflink.rhcloud.com/r/31/
---
(Updated July 3, 2013, 9:01 a.m.)
Status
--
This change has been
---
This is an automatically generated e-mail. To reply, visit:
http://reviewboard-tflink.rhcloud.com/r/34/
---
Review request for blockerbugs.
Repository: blockerbugs
Description
#390: modifying milestone through admin web interface generates http 500 errors
--+
Reporter: tflink| Owner: tflink
Type: defect| Status: new
Priority: critical
93 matches
Mail list logo
