بسم الله الرّحمن الرّحيم
Hi,
I try to build arched subpackage from main (noarch) package. I can't and have
this message :
error: line 153: Only noarch subpackages are supported: BuildArch: noarch noarch
Any ideas ??
Regards
Mosaab
--
devel
On Wed, 2013-10-30 at 09:05 +0200, مصعب الزعبي wrote:
بسم الله الرّحمن الرّحيم
Hi,
I try to build arched subpackage from main (noarch) package. I can't and have
this message :
error: line 153: Only noarch subpackages are supported: BuildArch: noarch
noarch
Any ideas ??
The message
Ok,
I read that message, but I search for a tweak.
So I'll separate main package into (-core) nonarched, and meta one arched.
Regards
==
Mosaab
Subject: Re: Drive arched subpackage from nonarched one
From: boche...@fedoraproject.org
To: devel@lists.fedoraproject.org
Date: Wed, 30 Oct
# F20 Beta Blocker Review meeting #6
# Date: 2013-10-30
# Time: 16:00 UTC (12:00 EDT, 09:00 PDT)
# Location: #fedora-blocker-review on irc.freenode.net
It's time for another round of F20 beta blocker bug review!
We'll be running through the final blockers and freeze exception bugs.
The current
On 10/29/2013 02:13 PM, Dridi Boukelmoune wrote:
Hi,
I'm on the CC list of the review request for rubygem-vagrant [1] and
randomly found a new review request for vagrant [2]. The two packages
are AFAICT the same, and the former is stalled due to missing
dependencies, the last one being
Am 30.10.2013 02:03, schrieb Chris Adams:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
[root@srv-rhsoft:~]$ mkdir test
i could rm -rf ~/ here
[root@srv-rhsoft:~]$ cat /usr/local/bin/mkdir
#!/bin/bash
echo i could rm -rf ~/ here
If I can write to files you own, it doesn't
#445: upgradepath is failing rawhide builds due to not being higher version than
other releases
+-
Reporter: tflink | Owner:
Type: defect | Status: new
Priority: major | Milestone: Hot issues
Component: tests |
On 30/10/13 09:16, Josef Stribny wrote:
yes, according to guidelines[1], it should be named rubygem-vagrant
since it's convention for all RubyGems.
Is vagrant not an Application package that mainly provides user-level
tools that happen to be written in Ruby though? In which case by the
What prevails between the ruby naming guidelines and the prior art
rule (other distros package name) in the general naming guidelines ?
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming
http://packages.ubuntu.com/raring/vagrant
http://packages.debian.org/stable/vagrant
My
On 2013-10-30 10:23, Reindl Harald wrote:
Am 30.10.2013 02:03, schrieb Chris Adams:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
[root@srv-rhsoft:~]$ mkdir test
i could rm -rf ~/ here
[root@srv-rhsoft:~]$ cat /usr/local/bin/mkdir
#!/bin/bash
echo i could rm -rf ~/ here
If I
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald wrote:
Am 30.10.2013 02:03, schrieb Chris Adams:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
[root@srv-rhsoft:~]$ mkdir test
i could rm -rf ~/ here
[root@srv-rhsoft:~]$ cat /usr/local/bin/mkdir
Hi,
this is a contact attempt for the wipe maintainer Scott Henson according
to
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
Bug with contact attempts:
https://bugzilla.redhat.com/show_bug.cgi?id=1019179
There are two other bugs without any response:
Hi,
I have just submitted the latest dnf as an F20 update [1]. It brings
quite a few fixes and improvements, most significant of which are the
history undo support and limiting the number of installed kernels. See
the release notes [2] and the blog post [3].
Ales Kozumplik
[1]
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald wrote:
Am 30.10.2013 02:03, schrieb Chris Adams:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
[root@srv-rhsoft:~]$ mkdir test
i could rm -rf ~/ here
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald wrote:
Am 30.10.2013 02:03, schrieb Chris Adams:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
[root@srv-rhsoft:~]$
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald wrote:
Am 30.10.2013 02:03, schrieb Chris Adams:
Once upon a time, Reindl Harald
Am 30.10.2013 11:27, schrieb Alec Leamas:
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald wrote:
Am 30.10.2013 02:03, schrieb Chris
On 2013-10-30 11:46, Reindl Harald wrote:
Am 30.10.2013 11:27, schrieb Alec Leamas:
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald
On 10/30/2013 10:45 AM, Dridi Boukelmoune wrote:
What prevails between the ruby naming guidelines and the prior art
rule (other distros package name) in the general naming guidelines ?
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming
Am 30.10.2013 11:55, schrieb Alec Leamas:
On 2013-10-30 11:46, Reindl Harald wrote:
Am 30.10.2013 11:27, schrieb Alec Leamas:
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec
perl-PDL has broken dependencies in the F-20 tree:
On x86_64:
perl-PDL-2.4.10-6.fc19.x86_64 requires perl(:MODULE_COMPAT_5.16.2)
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 perl(:MODULE_COMPAT_5.16.2)
perl-Padre has broken dependencies in the F-20 tree:
On x86_64:
perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0)
On i386:
perl-Padre-0.90-6.fc18.noarch requires perl(:MODULE_COMPAT_5.16.0)
On armhfp:
perl-Padre-0.90-6.fc18.noarch requires
perl-Language-Expr has broken dependencies in the F-20 tree:
On x86_64:
perl-Language-Expr-0.19-4.fc19.noarch requires
perl(:MODULE_COMPAT_5.16.2)
On i386:
perl-Language-Expr-0.19-4.fc19.noarch requires
perl(:MODULE_COMPAT_5.16.2)
On armhfp:
perl-BerkeleyDB has broken dependencies in the F-20 tree:
On x86_64:
perl-BerkeleyDB-0.53-1.fc20.x86_64 requires libdb = 0:5.3.21
On i386:
perl-BerkeleyDB-0.53-1.fc20.i686 requires libdb = 0:5.3.21
On armhfp:
perl-BerkeleyDB-0.53-1.fc20.armv7hl requires libdb = 0:5.3.21
perl-MIME-Lite-HTML has broken dependencies in the F-20 tree:
On x86_64:
perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires
perl(:MODULE_COMPAT_5.16.0)
On i386:
perl-MIME-Lite-HTML-1.24-4.fc18.noarch requires
perl(:MODULE_COMPAT_5.16.0)
On armhfp:
slic3r has broken dependencies in the F-20 tree:
On x86_64:
slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3)
On i386:
slic3r-0.9.10b-2.fc20.noarch requires perl(:MODULE_COMPAT_5.16.3)
On armhfp:
slic3r-0.9.10b-2.fc20.noarch requires
On 2013-10-30 12:25, Reindl Harald wrote:
Am 30.10.2013 11:55, schrieb Alec Leamas:
On 2013-10-30 11:46, Reindl Harald wrote:
Am 30.10.2013 11:27, schrieb Alec Leamas:
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald
Am 30.10.2013 13:00, schrieb Alec Leamas:
On 2013-10-30 12:25, Reindl Harald wrote:
i gave you a starting point to learn about security and the reason
for sftp-chroot doing so is that someone could use race-conditions
to bypass the security
if you do not understand that allowing any random
On Wed, Oct 30, 2013 at 09:26:49AM +0200, مصعب الزعبي wrote:
I read that message, but I search for a tweak.
So I'll separate main package into (-core) nonarched, and meta one arched.
Yes, that's the normal way to deal with this. -core or -common, depending on
what makes sense.
--
Matthew
Hello everyone. Our initial Cloud WG meeting today is today at 19:00 UTC
(3pm EDT). We'll use #fedora-meeting-1 (because the FESCo meeting in
#fedora-meeting has been running more than an hour). All are welcome.
== Communications ==
- mailing list vs. irc meetings
- trac instance
== Next Steps
On Wed, Oct 30, 2013 at 12:04 PM, Josef Stribny jstri...@redhat.com wrote:
On 10/30/2013 10:45 AM, Dridi Boukelmoune wrote:
What prevails between the ruby naming guidelines and the prior art
rule (other distros package name) in the general naming guidelines ?
On 2013-10-30 13:08, Reindl Harald wrote:
Am 30.10.2013 13:00, schrieb Alec Leamas:
On 2013-10-30 12:25, Reindl Harald wrote:
i gave you a starting point to learn about security and the reason
for sftp-chroot doing so is that someone could use race-conditions
to bypass the security
if you do
Compose started at Wed Oct 30 09:15:02 UTC 2013
Broken deps for armhfp
--
[blueman]
blueman-1.23-7.fc20.armv7hl requires obex-data-server = 0:0.4.3
blueman-1.23-7.fc20.armv7hl requires gvfs-obexftp
[bwm-ng]
On 10/30/2013 01:08 PM, Reindl Harald wrote:
Am 30.10.2013 13:00, schrieb Alec Leamas:
On 2013-10-30 12:25, Reindl Harald wrote:
i gave you a starting point to learn about security and the reason
for sftp-chroot doing so is that someone could use race-conditions
to bypass the security
if
And how vagrant differs from rhc and other client command line tools
that are distributed as gems and follow this convention?
What I would like to see in both rhc and vagrant would be:
Provides: rhc
respectively
Provides: vagrant
It feels natural to me, I have issued yum install rhc several
On Wed, Oct 30, 2013 at 1:41 PM, Lukas Zapletal l...@redhat.com wrote:
And how vagrant differs from rhc and other client command line tools
that are distributed as gems and follow this convention?
What I would like to see in both rhc and vagrant would be:
Provides: rhc
respectively
Dne 30.10.2013 13:23, Dridi Boukelmoune napsal(a):
On Wed, Oct 30, 2013 at 12:04 PM, Josef Stribny jstri...@redhat.com wrote:
On 10/30/2013 10:45 AM, Dridi Boukelmoune wrote:
What prevails between the ruby naming guidelines and the prior art
rule (other distros package name) in the general
Hi All,
Below is a draft governance charter for the Workstation WG. I have
taken much of this from the Cloud WG draft charter (found here:
https://fedoraproject.org/wiki/Cloud_WG) to have some commonality
between groups. I left some of the sections from that off for now, as
I think that is
On Wed, Oct 30, 2013 at 8:20 AM, Matthew Miller
mat...@fedoraproject.org wrote:
Hello everyone. Our initial Cloud WG meeting today is today at 19:00 UTC
(3pm EDT). We'll use #fedora-meeting-1 (because the FESCo meeting in
#fedora-meeting has been running more than an hour). All are welcome.
(Apologies for the lateness.)
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 time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2013-10-30 18:00
What prevails between the ruby naming guidelines and the prior art
rule (other distros package name) in the general naming guidelines ?
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming
http://packages.ubuntu.com/raring/vagrant
On 10/30/2013 01:41 PM, Lukas Zapletal wrote:
And how vagrant differs from rhc and other client command line tools
that are distributed as gems and follow this convention?
What I would like to see in both rhc and vagrant would be:
Provides: rhc
respectively
Provides: vagrant
It feels
https://bugzilla.redhat.com/show_bug.cgi?id=1024821
Bug ID: 1024821
Summary: ctstream-9 is available
Product: Fedora
Version: rawhide
Component: ctstream
Keywords: FutureFeature, Triaged
Assignee: ppi...@redhat.com
perl-Language-Expr has broken dependencies in the rawhide tree:
On x86_64:
perl-Language-Expr-0.19-4.fc19.noarch requires
perl(:MODULE_COMPAT_5.16.2)
On i386:
perl-Language-Expr-0.19-4.fc19.noarch requires
perl(:MODULE_COMPAT_5.16.2)
On armhfp:
On Wed, Oct 30, 2013 at 2:18 PM, Josef Stribny jstri...@redhat.com wrote:
What prevails between the ruby naming guidelines and the prior art
rule (other distros package name) in the general naming guidelines ?
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#General_Naming
On Wed, Oct 30, 2013 at 09:06:30AM -0400, Josh Boyer wrote:
You have basically the top-level landing page for the WG there. It
has all the relevant information one would expect, but I think some of
the sections go beyond governance. Specifically, the Mission, Role in
Fedora, and
On Wed, Oct 30, 2013 at 6:27 AM, Alec Leamas leamas.a...@gmail.com wrote:
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
On 2013-10-30 10:23, Reindl Harald wrote:
Am
Il giorno mar, 29/10/2013 alle 16.57 -0400, Przemek Klosowski ha
scritto:
On 10/29/2013 02:07 PM, Dario Lesca wrote:
Il giorno mar, 29/10/2013 alle 09.38 +0100, Dario Lesca ha scritto:
Sorry for cross post, but I would avoid to reinstall my notebook
Someone can help me?
Since I had
On 10/30/2013 01:08 PM, Reindl Harald wrote:
Am 30.10.2013 13:00, schrieb Alec Leamas:
On 2013-10-30 12:25, Reindl Harald wrote:
No, it should not. However, the right decision is in many cases a
trade-off between security and usabilty, not always with a single
answer. Allowing users to
On 2013-10-30 15:05, Christopher wrote:
On Wed, Oct 30, 2013 at 6:27 AM, Alec Leamas leamas.a...@gmail.com wrote:
On 2013-10-30 11:23, Reindl Harald wrote:
Am 30.10.2013 11:20, schrieb Alec Leamas:
On 2013-10-30 10:58, Reindl Harald wrote:
Am 30.10.2013 10:53, schrieb Alec Leamas:
Some kind
Am 30.10.2013 15:29, schrieb Ralf Corsepius:
On 10/30/2013 01:08 PM, Reindl Harald wrote:
Besides that, what and where users put things underneath of $HOME is not a
distro's busness
and so it is not a distro's business to add something to $PATH
inside the userhome and finally you agreed
On Wed, Oct 30, 2013 at 09:01:52AM -0400, Josh Boyer wrote:
The Fedora Workstation Work Group has nine voting members, with one
member selected by the Fedora Engineering Steering Committee as the
liaison to FESCo.
Is the FESCo appointed member one of the nine voting members?
--
Matthew
https://bugzilla.redhat.com/show_bug.cgi?id=1024884
Bug ID: 1024884
Summary: perl-Devel-Symdump-2.11 is available
Product: Fedora
Version: rawhide
Component: perl-Devel-Symdump
Keywords: FutureFeature, Triaged
Assignee:
On Mon, Oct 28, 2013 at 10:56 AM, Josh Boyer jwbo...@fedoraproject.org wrote:
On Mon, Oct 28, 2013 at 10:43 AM, Phil Knirsch pknir...@redhat.com wrote:
On 10/28/2013 03:36 PM, Jóhann B. Guðmundsson wrote:
On 10/28/2013 01:20 PM, Phil Knirsch wrote:
Hi everyone.
As FESCO appointed me last
On Wed, Oct 30, 2013 at 10:39 AM, Matthew Garrett mj...@srcf.ucam.org wrote:
On Wed, Oct 30, 2013 at 09:01:52AM -0400, Josh Boyer wrote:
The Fedora Workstation Work Group has nine voting members, with one
member selected by the Fedora Engineering Steering Committee as the
liaison to FESCo.
https://bugzilla.redhat.com/show_bug.cgi?id=1024894
Bug ID: 1024894
Summary: perl-Perl-Critic-Deprecated-1.119 is available
Product: Fedora
Version: rawhide
Component: perl-Perl-Critic-Deprecated
Keywords: FutureFeature, Triaged
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/29/2013 09:03 PM, Chris Adams wrote:
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
[root@srv-rhsoft:~]$ mkdir test i could rm -rf ~/ here
[root@srv-rhsoft:~]$ cat /usr/local/bin/mkdir #!/bin/bash echo i could
rm -rf ~/ here
https://bugzilla.redhat.com/show_bug.cgi?id=1024896
Bug ID: 1024896
Summary: perl-Perl-Critic-More-1.003 is available
Product: Fedora
Version: rawhide
Component: perl-Perl-Critic-More
Keywords: FutureFeature, Triaged
On 10/30/2013 03:36 PM, Reindl Harald wrote:
Am 30.10.2013 15:29, schrieb Ralf Corsepius:
On 10/30/2013 01:08 PM, Reindl Harald wrote:
Besides that, what and where users put things underneath of $HOME is not a
distro's busness
and so it is not a distro's business to add something to $PATH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/30/2013 10:44 AM, Josh Boyer wrote:
On Mon, Oct 28, 2013 at 10:56 AM, Josh Boyer
jwbo...@fedoraproject.org wrote:
On Mon, Oct 28, 2013 at 10:43 AM, Phil Knirsch
pknir...@redhat.com wrote:
On 10/28/2013 03:36 PM, Jóhann B. Guðmundsson wrote:
On 2013-10-30 15:50, Ralf Corsepius wrote:
On 10/30/2013 03:36 PM, Reindl Harald wrote:
Am 30.10.2013 15:29, schrieb Ralf Corsepius:
On 10/30/2013 01:08 PM, Reindl Harald wrote:
Besides that, what and where users put things underneath of $HOME is
not a distro's busness
[cut]
Is it really
Thank you for all your ideas!
I am going to change the default template to:
[abrt] component: function(): executable killed by SIGnum|name
Conclusion:
- do not drop component because some email clients cannot display
custom headers in index
- drop VR from component because Ales
The following Fedora EPEL 6 Security updates need testing:
Age URL
556
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5620/bugzilla-3.4.14-2.el6
70
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11274/ssmtp-2.61-21.el6
31
The following Fedora EPEL 5 Security updates need testing:
Age URL
556
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-5630/bugzilla-3.2.10-5.el5
70
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2013-11276/ssmtp-2.61-21.el5
46
On 10/30/2013 10:47 AM, thierry bordaz wrote:
Hello,
This tickets implement a test case and propose a layout of the CI
tests in the 389-ds.
The basic idea is to put CI tests under:
head/dirsrvtests/
tickets/
standalone_test.py
m1c1_test.py
On Wed, Oct 30, 2013 at 10:23 AM, Reindl Harald h.rei...@thelounge.net wrote:
If I can write to files you own, it doesn't matter if there's a
directory in the PATH or not. I can write this to your .bash_profile:
/bin/mkdir $HOME/.bin 2 /dev/null
echo 'echo i could rm -rf ~/ here'
https://bugzilla.redhat.com/show_bug.cgi?id=1025004
Bug ID: 1025004
Summary: Update from F19 to F20 fails due to perl version
dependencies
Product: Fedora
Version: rawhide
Component: perl-Language-Expr
Assignee:
On 10/30/2013 06:59 PM, Rich Megginson wrote:
On 10/30/2013 10:47 AM, thierry bordaz wrote:
Hello,
This tickets implement a test case and propose a layout of the CI
tests in the 389-ds.
The basic idea is to put CI tests under:
head/dirsrvtests/
tickets/
Am 30.10.2013 18:59, schrieb Miloslav Trmač:
On Wed, Oct 30, 2013 at 10:23 AM, Reindl Harald h.rei...@thelounge.net
wrote:
If I can write to files you own, it doesn't matter if there's a
directory in the PATH or not. I can write this to your .bash_profile:
/bin/mkdir $HOME/.bin 2
Hi guys,
I hope all is well.
I am writing in regards to something I had written about two months ago.
This in regards to the search engine.
https://fedorahosted.org/fedora-infrastructure/ticket/1055#trac-add-comment
I think we need to seriously fix this thing once and for all.
I am looking
Giving the FESCO rep a two year term seems to be a potential problem as
they wouldn't be guaranteed to be in FESCO for two years and most of
the time you'd probably want the rep to be a member of FESCO. Maybe the
FESCO rep should just serve at the pleasure of FESCO?
--
devel mailing list
On Wed, Oct 30, 2013 at 19:15:11 +0100,
Reindl Harald h.rei...@thelounge.net wrote:
which is not possible at all, any application running with your
user can write in your home directory and any security relevant
bug in that application may result in changes
That doesn't have to be the case.
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2013-10-31 16:00 UTC in #fedora-meeting-1 on
irc.freenode.net.
Local time information (via. rktime):
2013-10-31 09:00 Thu US/Pacific PDT
2013-10-31 12:00 Thu US/Eastern EDT
2013-10-31
Am 30.10.2013 19:51, schrieb Bruno Wolff III:
On Wed, Oct 30, 2013 at 19:15:11 +0100,
Reindl Harald h.rei...@thelounge.net wrote:
which is not possible at all, any application running with your
user can write in your home directory and any security relevant
bug in that application may
On Wed, Oct 30, 2013 at 2:42 PM, Bruno Wolff III br...@wolff.to wrote:
Giving the FESCO rep a two year term seems to be a potential problem as they
wouldn't be guaranteed to be in FESCO for two years and most of the time
you'd probably want the rep to be a member of FESCO. Maybe the FESCO rep
Hi,
On Wed, Oct 30, 2013 at 9:01 AM, Josh Boyer jwbo...@fedoraproject.org wrote:
The other positions will be filled by general election
every two years. As a special exception, four seats will be filled in
one year, with those positions chosen at random (unless some number of
members decide
On Wed, Oct 30, 2013 at 3:16 PM, Ray Strode halfl...@gmail.com wrote:
Hi,
On Wed, Oct 30, 2013 at 9:01 AM, Josh Boyer jwbo...@fedoraproject.org wrote:
The other positions will be filled by general election
every two years. As a special exception, four seats will be filled in
one year, with
Frankie Onuonga wrote:
I am writing in regards to something I had written about two months ago.
This in regards to the search engine.
https://fedorahosted.org/fedora-infrastructure/ticket/1055#trac-add-comment
I think we need to seriously fix this thing once and for all.
I am looking at
Hi,
On Wed, Oct 30, 2013 at 3:22 PM, Josh Boyer jwbo...@fedoraproject.org wrote:
In your opinion, should we have term limits imposed to ensure we have
fresh members coming into the WG? As I said in another email, I think
we should shoot for some continuity while also encouraging new members
On Wed, Oct 30, 2013 at 7:29 PM, Michael Cronenworth m...@cchtml.comwrote:
Frankie Onuonga wrote:
I am writing in regards to something I had written about two months ago.
This in regards to the search engine.
https://fedorahosted.org/**fedora-infrastructure/ticket/**
On 10/30/2013 07:56 PM, Jan Rusnacko wrote:
Hello Thierry,
layout OK.
As for tests - instead of reinventing the wheel by defing class Test_standAlone
to set up instance, use py.test fixture.
Also, you should not force setup, test, teardown execution for each test by
specifying sub-methods for
Frankie Onuonga wrote:
My notion has always been that people always want something that is made in
house.
I do not think they will take up something that is in a black box but I might
be wrong.
Site search engines are mostly useless to me, and I know I'm not alone. Why else
would the ticket
Ok I realise it is not a good idea. I will reimplement it and send an
other review :-)
Thanks for all your feedbacks.
thierry
On 10/30/2013 08:11 PM, Rich Megginson wrote:
On 10/30/2013 12:56 PM, Jan Rusnacko wrote:
Hello Thierry,
layout OK.
As for tests - instead of reinventing the wheel
On 10/30/2013 02:09 PM, thierry bordaz wrote:
On 10/30/2013 07:56 PM, Jan Rusnacko wrote:
Hello Thierry,
layout OK.
As for tests - instead of reinventing the wheel by defing class Test_standAlone
to set up instance, use py.test fixture.
Also, you should not force setup, test, teardown
===
#fedora-meeting: FESCO (2013-10-30)
===
Meeting started by notting at 18:01:19 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2013-10-30/fesco.2013-10-30-18.01.log.html
.
Meeting summary
=
#fedora-meeting-1: Cloud (2013-10-30)
=
Meeting started by mattdm at 19:00:22 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedora-meeting-1.2013-10-30-19.00.log.html
.
On Wed, Oct 30, 2013 at 8:11 PM, Michael Cronenworth m...@cchtml.comwrote:
Frankie Onuonga wrote:
My notion has always been that people always want something that is made
in house.
I do not think they will take up something that is in a black box but I
might
be wrong.
Site search
On Wed, Oct 30, 2013 at 7:15 PM, Reindl Harald h.rei...@thelounge.net wrote:
and no, you can't imagine an attack like hey i have a sehll now and
try around where i can compromise your setup - in most cases after
a buffer overlow and such things you have *one* chance to execture
your code
On Wed, Oct 30, 2013 at 01:08:48PM +0100, Reindl Harald wrote:
Am 30.10.2013 13:00, schrieb Alec Leamas:
Current defaults already has ~/bin in $PATH, and user can certainly put
things there. Isn't the issue here if having a hidden, writeable directory
in $PATH is such a bad idea, given
Please check #350 again.
Thanks.
--
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 Wed, 30 Oct, 2013 at 14:05:05 GMT, Christopher wrote:
And, the xdg argument doesn't seem like a sufficient argument for
me... we're talking about login scripts, not X. It is very unintuitive
that an xdg-related directory would be on the default path for a bash
login, if you're not even
Once upon a time, Reindl Harald h.rei...@thelounge.net said:
you can do this and that - but that's no valid argumentation
doing bad things in default setups
But you are calling it bad with no real argument except repitition.
I've shown that it is not _any_ worse for security.
*at least* do
Summary of changes:
47ab221... 1.128 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
Summary of changes:
cbe6a87... 1.127 bump, test suite enhancements (*)
fc1d09c... Perl 5.18 rebuild (*)
30e0549... - Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass (*)
47ab221... 1.128 bump (*)
(*) This commit already existed in another branch; no separate mail sent
--
Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=1023711
--- Comment #1 from Fedora Update System upda...@fedoraproject.org ---
perl-Text-Table-1.128-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/perl-Text-Table-1.128-1.fc20
--
You are receiving this
https://bugzilla.redhat.com/show_bug.cgi?id=1023711
--- Comment #2 from Fedora Update System upda...@fedoraproject.org ---
perl-Text-Table-1.128-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/perl-Text-Table-1.128-1.fc19
--
You are receiving this
https://bugzilla.redhat.com/show_bug.cgi?id=1025004
Paul Howarth p...@city-fan.org changed:
What|Removed |Added
Status|NEW |CLOSED
https://bugzilla.redhat.com/show_bug.cgi?id=992666
Paul Howarth p...@city-fan.org changed:
What|Removed |Added
CC|
https://bugzilla.redhat.com/show_bug.cgi?id=992666
--- Comment #9 from Miro Hrončok mhron...@redhat.com ---
Is there something I can do to prevent failures such as bz1025004? E.g. delete
the package from F20 somehow?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=992666
--- Comment #10 from Paul Howarth p...@city-fan.org ---
Well you could retire the package and anything that depended on it but then
you'd still have the problem that people with the package installed at F-19
would have dependency errors trying
1 - 100 of 108 matches
Mail list logo
