On Wed, 2013-06-19 at 12:23 +0200, Nicolas Mailhot wrote:
> Le Mer 19 juin 2013 10:07, Krzysztof Daniel a écrit :
> > Hello everyone,
>
> > I'd like to be able to define a build trigger for Eclipse, so when a
> > "vital" dependency changes, Eclipse is rebuild, BR/R are updated, and a
> > bodhi upd
Once upon a time, Adam Williamson said:
> Matthew's post about it was precisely what kicked off this sub-thread. I
> wonder if there is a theorem covering the topic of the minimum number of
> messages required in a thread before one is posted which is clearly
> unaware of the first one. =)
D'oh!
On Thu, 2013-06-20 at 23:27 +0200, Reindl Harald wrote:
> but how F15/F16 in context of
> systemd was released is a sign of poor or absent QA
Ahem. It is absolutely not QA's job to dictate strategic decisions. The
project as a whole decided that a gradual conversion from sysv to
systemd was the a
On Thu, 2013-06-20 at 16:17 +0200, Reindl Harald wrote:
> i say it again:
Please, please, don't.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
--
devel mailing list
devel@lists.fedoraproject.org
https://ad
On Wed, 2013-06-19 at 10:00 -0600, Eric Smith wrote:
> On Wed, Jun 19, 2013 at 4:23 AM, Nicolas Mailhot
> wrote:
> > You don't need a special trigger. You need your requirements to match the
> > constraints declared at the rpm level, then incompatibilities will be
> > caught at this level by norma
On Thu, 2013-06-20 at 14:06 -0500, Chris Adams wrote:
> Once upon a time, Matthew Miller said:
> > Hence, the RFE -- a mode which sets up the above, and then goes away.
>
> I had not seen that mode (or a request for it).
Matthew's post about it was precisely what kicked off this sub-thread. I
Am 21.06.2013 01:05, schrieb Bill Nottingham:
> Reindl Harald (h.rei...@thelounge.net) said:
>> yes - why was such a basic service *not* a systemd-unit
>> at the F15 release-day?
>
> Because it's not a service in the traditional sense at all. To
> move it to systemd requires one of:
>
> - addi
Reindl Harald (h.rei...@thelounge.net) said:
> yes - why was such a basic service *not* a systemd-unit
> at the F15 release-day?
Because it's not a service in the traditional sense at all. To
move it to systemd requires one of:
- adding a minimum wrapper that just execs the same pile of shell, w
On Thu, Jun 20, 2013 at 1:43 PM, Eric Smith wrote:
> That's one development model. Another is to do a more gradual
> transition, instead of a sharp cliff. We could debate the relative
> merits of the two models until the cows come home, but it's a moot
> point as the gradual transition is what w
On Thu, Jun 20, 2013 at 3:27 PM, Reindl Harald wrote:
> yes - why was such a basic service *not* a systemd-unit
> at the F15 release-day?
>
> in my understanding of develop quality software this
> would not have happened and systemd at all not be
> shipped as replacement until the rest of the dist
Am 20.06.2013 23:13, schrieb Matthew Miller:
> On Thu, Jun 20, 2013 at 04:17:13PM +0200, Reindl Harald wrote:
>> why does *anything* still use sysv-init stuff and packages
>> whichare not converted simply not dropped to wake up the
>> maintainer which does *clearly* not his work?
>
> Like. /
On Thu, Jun 20, 2013 at 04:17:13PM +0200, Reindl Harald wrote:
> why does *anything* still use sysv-init stuff and packages
> whichare not converted simply not dropped to wake up the
> maintainer which does *clearly* not his work?
Like. /etc/init.d/network?
--
Matthew Miller ☁☁☁ Fedora Cl
Thanks Don, for your answer. How can I follow progress in this area? Is
there a mailing list, or a wiki page for that?
@Lars: I'll try the preview repo nonetheless and report the result tomorrow.
With best regards,
Mario
On 20 June 2013 16:39, Don Dutile wrote:
> On 06/20/2013 03:27 AM, Mari
Am 20.06.2013 22:14, schrieb Kevin Fenzi:
> On Thu, 20 Jun 2013 21:59:16 +0200
> Reindl Harald wrote:
>
>> because i do *not* need it?
>> becuase i maintain around 30 fedora machines
>> because they are all wroking perfect
>
> Thats great that that is your use case.
>
> Keep in mind that this
On Thu, 20 Jun 2013 21:59:16 +0200
Reindl Harald wrote:
> because i do *not* need it?
> becuase i maintain around 30 fedora machines
> because they are all wroking perfect
Thats great that that is your use case.
Keep in mind that this list is talking about development of Fedora for
ALL the peo
Am 20.06.2013 20:55, schrieb Matthew Miller:
> On Thu, Jun 20, 2013 at 01:15:37PM -0500, Chris Adams wrote:
>>> Mind if I ask why you think this way about NetworkManager? The NM
>>> currently shipping in Fedora 19 has full support for managing static
>>> NICs, as well as bonding, bridging and VLA
Am 20.06.2013 17:37, schrieb Matthew Miller:
> On Thu, Jun 20, 2013 at 05:08:48PM +0200, Reindl Harald wrote:
>>> We are on track to replace the "legacy" network and firewall init scripts
>>> with these. It's a slow track, but that's the direction
>> *do not* remove iptables.service for a lot od
Am 20.06.2013 20:01, schrieb Stephen Gallagher:
>> *do not* remove iptables.service for a lot od reason explained
>> often enough as well as NM is utterly useless on servers and
>> workstations with several *static* configured NIC's
>
>
> Mind if I ask why you think this way about NetworkMana
> From: "Chris Adams"
> I prefer the "modern" secondaries vs. the old-style eth0:123, although I
> have run into vendor software (such as the Plesk web hosting control
> panel) that can't handle it. I expect if that was the "one true way" in
> some future version of RHEL, they'd adapt.
AFAIK wit
On Thu, 2013-06-20 at 14:06 -0500, Chris Adams wrote:
> Once upon a time, Matthew Miller said:
> > Hence, the RFE -- a mode which sets up the above, and then goes away.
>
> I had not seen that mode (or a request for it). That would be nice. In
> a perfect world (hah!), replacing "ifup" and "ifd
On Thu, 2013-06-20 at 13:59 -0500, Chris Adams wrote:
> Once upon a time, Bill Nottingham said:
> > No, it does not support that at this time. Also note that (if I'm
> > remembering right) NM adds all aliases as secondary IP addresses, not as
> > ':x' style additional devices.
>
> I prefer the "m
Once upon a time, Matthew Miller said:
> Hence, the RFE -- a mode which sets up the above, and then goes away.
I had not seen that mode (or a request for it). That would be nice. In
a perfect world (hah!), replacing "ifup" and "ifdown" with scripts that
just make the appropriate "nmcli" (or wha
Once upon a time, Bill Nottingham said:
> No, it does not support that at this time. Also note that (if I'm
> remembering right) NM adds all aliases as secondary IP addresses, not as
> ':x' style additional devices.
I prefer the "modern" secondaries vs. the old-style eth0:123, although I
have run
On Thu, 2013-06-20 at 12:13 -0600, Eric Smith wrote:
> Does NM in F19 support statically assigning multiple subnets to the
> same physical interface, WITHOUT using VLANs? I often need that on
> server machines, and wasn't able to figure out any way to do it with
> NM on F17, but I haven't yet trie
On Thu, Jun 20, 2013 at 01:15:37PM -0500, Chris Adams wrote:
> > Mind if I ask why you think this way about NetworkManager? The NM
> > currently shipping in Fedora 19 has full support for managing static
> > NICs, as well as bonding, bridging and VLAN support for enterprise
> > use-cases.
> I think
Chris Adams (li...@cmadams.net) said:
> Once upon a time, Eric Smith said:
> > Does NM in F19 support statically assigning multiple subnets to the
> > same physical interface, WITHOUT using VLANs? I often need that on
> > server machines, and wasn't able to figure out any way to do it with
> > N
On Thu, 2013-06-20 at 12:13 -0600, Eric Smith wrote:
> Does NM in F19 support statically assigning multiple subnets to the
> same physical interface, WITHOUT using VLANs?
Yes. You can easily do this in the GNOME Control center, just try it.
Click "Manual", and then the "+" will allow adding multi
https://bugzilla.redhat.com/show_bug.cgi?id=976544
Bug ID: 976544
Summary: perl-HTTP-Tiny-0.032 is available
Product: Fedora
Version: rawhide
Component: perl-HTTP-Tiny
Keywords: FutureFeature, Triaged
Severity: unspecified
On Thu, 2013-06-20 at 13:15 -0500, Chris Adams wrote:
> I think most "traditional" system admins see a running NM daemon as an
> additional point of failure in a static network. If my server's network
> setup is static, I don't want a daemon running attempting to "manage"
> it. If it has a bug,
On Thu, Jun 20, 2013 at 12:13:54PM -0600, Eric Smith wrote:
> Does NM in F19 support statically assigning multiple subnets to the
> same physical interface, WITHOUT using VLANs? I often need that on
> server machines, and wasn't able to figure out any way to do it with
> NM on F17, but I haven't y
Once upon a time, Eric Smith said:
> Does NM in F19 support statically assigning multiple subnets to the
> same physical interface, WITHOUT using VLANs? I often need that on
> server machines, and wasn't able to figure out any way to do it with
> NM on F17, but I haven't yet tried it on F19.
Als
Once upon a time, Stephen Gallagher said:
> Mind if I ask why you think this way about NetworkManager? The NM
> currently shipping in Fedora 19 has full support for managing static
> NICs, as well as bonding, bridging and VLAN support for enterprise
> use-cases.
I think most "traditional" system
Does NM in F19 support statically assigning multiple subnets to the
same physical interface, WITHOUT using VLANs? I often need that on
server machines, and wasn't able to figure out any way to do it with
NM on F17, but I haven't yet tried it on F19.
With the old-style network configuration, it wa
The lightweight tag 'perl-Perl-Critic-1.118-4.fc20' was created pointing to:
bcc9c8d... BR: perl(Fatal) for the test suite
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
perl-devel mailing list
perl-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/20/2013 11:08 AM, Reindl Harald wrote:
>
>
> Am 20.06.2013 17:01, schrieb Matthew Miller:
>> On Thu, Jun 20, 2013 at 11:52:54AM +0200, Harald Hoyer wrote:
>>> And why is NetworkManager and firewalld in the minimal
>>> install?
>>
>> We are on
commit bcc9c8d75b847340927b6609ad7c84d12b8eac60
Author: Paul Howarth
Date: Thu Jun 20 18:41:08 2013 +0100
BR: perl(Fatal) for the test suite
perl-Perl-Critic.spec |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
---
diff --git a/perl-Perl-Critic.spec b/perl-Perl-Critic.spec
Fedora 19 Test Candidate 6 cloud images are now available from:
https://dl.fedoraproject.org/pub/alt/stage/19-TC6/Images/
in either qcow2 or raw.xz format. You should be able to use Glance in
OpenStack to just import the qcow2 images directly and go.
They're also in Amazon EC2 in the US East r
On 06/20/2013 10:37 AM, Matthew Miller wrote:
> Well, like I just said, it's a slow track. I certainly am vigorously opposed
> to removing it before the replacement has the same functionality and
> reliability.
... and resource usage. Having Python fully loaded for a firewall isn't
my first choice
Can I offer to maintain it then? Who would I need to email to make that happen?
Daniel
Daniel Newkirk
Graduate Student
Yokomori Lab, Xie Lab
Dept. of Biological Chemistry, UCI
tel: 949-824-2158
email: dnewk...@uci.edu
--
Fedora Extras Perl SIG
http://www.fedoraproject.org/wiki/Extras/SIGs/Perl
Am 20.06.2013 16:02, schrieb Christopher Meng:
> Hmm...
>
> Subversion uses it...
why does *anything* still use sysv-init stuff and packages
whichare not converted simply not dropped to wake up the
maintainer which does *clearly* not his work?
it is very poor push F15 out with a halfbaken syste
Am 20.06.2013 17:01, schrieb Matthew Miller:
> On Thu, Jun 20, 2013 at 11:52:54AM +0200, Harald Hoyer wrote:
>> And why is NetworkManager and firewalld in the minimal install?
>
> We are on track to replace the "legacy" network and firewall init scripts
> with these. It's a slow track, but that'
On Thu, Jun 20, 2013 at 05:08:48PM +0200, Reindl Harald wrote:
> > We are on track to replace the "legacy" network and firewall init scripts
> > with these. It's a slow track, but that's the direction
> *do not* remove iptables.service for a lot od reason explained
> often enough as well as NM is u
On Thu, 20.06.13 08:48, Jon Ciesla (limburg...@gmail.com) wrote:
> On Thu, Jun 20, 2013 at 8:42 AM, Miloslav Trmač wrote:
>
> > On Thu, Jun 20, 2013 at 3:18 PM, Lennart Poettering
> > wrote:
> > > When systemd was first adopted by Fedora a requirement mandated by FESCO
> > > (or was it FPC?) wa
On Thu, 20.06.13 15:42, Miloslav Trmač (m...@volny.cz) wrote:
> On Thu, Jun 20, 2013 at 3:18 PM, Lennart Poettering
> wrote:
> > When systemd was first adopted by Fedora a requirement mandated by FESCO
> > (or was it FPC?) was that the script "systemd-sysv-convert" (which I
> > wrote) should be a
On Thu, Jun 20, 2013 at 11:52:54AM +0200, Harald Hoyer wrote:
> And why is NetworkManager and firewalld in the minimal install?
We are on track to replace the "legacy" network and firewall init scripts
with these. It's a slow track, but that's the direction.
Overall, I'm in favor of having a sing
On 06/20/2013 03:27 AM, Mario Ceresa wrote:
Thanks Lars, I'll do as you suggest!
Best,
Mario
On 19 June 2013 23:35, Lars Seipel mailto:lars.sei...@gmail.com>> wrote:
On Wed, Jun 19, 2013 at 04:42:30PM +0200, Mario Ceresa wrote:
> does anybody know if it is currently possible to do G
Hmm...
Subversion uses it...
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On 06/20/2013 01:48 PM, Jon Ciesla wrote:
As much as I'd like to see it go, I don't think we should until we're
a lot farther along the SysV->systemd migration path, just as a
practical matter. I don't think removing this tool now will help us
travel farther along it. There are other obstac
On 2013-06-20 14:19, Jonathan Masters wrote:
Indeed. This was a concern I raised when we first began the bootstrap. Blindly
rerunning autoreconf in every case is a really bad idea. But doing it in a
discretionary way, allowing the package maintainer to influence what happens
(they in theory kn
On 06/20/2013 01:42 PM, Miloslav Trmač wrote:
On Thu, Jun 20, 2013 at 3:18 PM, Lennart Poettering
wrote:
When systemd was first adopted by Fedora a requirement mandated by FESCO
(or was it FPC?) was that the script "systemd-sysv-convert" (which I
wrote) should be added which is supposed to save
On Thu, Jun 20, 2013 at 8:42 AM, Miloslav Trmač wrote:
> On Thu, Jun 20, 2013 at 3:18 PM, Lennart Poettering
> wrote:
> > When systemd was first adopted by Fedora a requirement mandated by FESCO
> > (or was it FPC?) was that the script "systemd-sysv-convert" (which I
> > wrote) should be added w
Revised fix based off of Rich and Ludwig's comments
https://fedorahosted.org/389/ticket/47329
https://fedorahosted.org/389/attachment/ticket/47329/0001-Ticket-47329-Improve-slapi_back_transaction_begin-re.patch
--
Mark Reynolds
Red Hat, Inc
mreyno...@redhat.com
--
389-devel mailing list
389
On Thu, Jun 20, 2013 at 3:18 PM, Lennart Poettering
wrote:
> When systemd was first adopted by Fedora a requirement mandated by FESCO
> (or was it FPC?) was that the script "systemd-sysv-convert" (which I
> wrote) should be added which is supposed to save the old runlevel
> configuration of sysv s
Heya!
When systemd was first adopted by Fedora a requirement mandated by FESCO
(or was it FPC?) was that the script "systemd-sysv-convert" (which I
wrote) should be added which is supposed to save the old runlevel
configuration of sysv scripts before we replace them with systemd units.
Now we are
Compose started at Thu Jun 20 09:15:02 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
Indeed. This was a concern I raised when we first began the bootstrap. Blindly
rerunning autoreconf in every case is a really bad idea. But doing it in a
discretionary way, allowing the package maintainer to influence what happens
(they in theory know whether this will work for their package and
On Mon, 17 Jun, 2013 at 15:29:39 GMT, Michael Schwendt wrote:
> One problem with that is, one cannot "blindly" run autoreconf -fi and
> expect it to be 100% compatible with the multitude of Autotools' based
> projects. Typically one will need to update the configure script, m4
> macros as well as M
Freeze exception required for this update.
https://bugzilla.redhat.com/976306
Remi.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Le 20/06/2013 12:18, Harald Hoyer a écrit :
> On 06/20/2013 11:59 AM, Remi Collet wrote:
>> Le 20/06/2013 11:52, Harald Hoyer a écrit :
>>> $ rpm -q --whatrequires json-c
>>> no package requires json-c
>>
>> Probably should try
>>
>> $ rpm -q --whatrequires \
>> "libjson.so.0()(64bit)" \
>> "li
On 06/20/2013 11:59 AM, Remi Collet wrote:
> Le 20/06/2013 11:52, Harald Hoyer a écrit :
>> $ rpm -q --whatrequires json-c
>> no package requires json-c
>
> Probably should try
>
> $ rpm -q --whatrequires \
> "libjson.so.0()(64bit)" \
> "libjson-c.so.2()(64bit)"
>
> => pulseaudio, abrt, libr
On 06/20/2013 11:59 AM, Remi Collet wrote:
> Le 20/06/2013 11:52, Harald Hoyer a écrit :
>> $ rpm -q --whatrequires json-c
>> no package requires json-c
>
> Probably should try
>
> $ rpm -q --whatrequires \
> "libjson.so.0()(64bit)" \
> "libjson-c.so.2()(64bit)"
>
> => pulseaudio, abrt, libr
Le 20/06/2013 11:52, Harald Hoyer a écrit :
> $ rpm -q --whatrequires json-c
> no package requires json-c
Probably should try
$ rpm -q --whatrequires \
"libjson.so.0()(64bit)" \
"libjson-c.so.2()(64bit)"
=> pulseaudio, abrt, libreport, ...
Remi.
--
devel mailing list
devel@lists.fedorapro
On 06/20/2013 09:21 AM, Adam Williamson wrote:
> As it may be interesting and I have the data on hand, here's the package
> diff between a minimal install of F16 and a minimal install of F19. F16
> has 203 packages (I think it's really 202 but I somehow got an extra one
> into my test), F19 TC6 has
Hi,
Marcin Dulak: working with RedHat/Fedora systems for 6 years, and a
Linux user for about 10.
Here is my fist package: https://bugzilla.redhat.com/show_bug.cgi?id=973084
I have packaged several software for internal use, mostly python and
science oriented:
https://build.opensuse.org/proje
Hi,
Thank you very much! It's a great feature :)
2013/6/20 Remi Collet
> https://fedoraproject.org/wiki/Features/Php55
>
> I just create the update to PHP 5.5.0 final.
>
> https://admin.fedoraproject.org/updates/php-5.5.0-1.fc19
>
> Very very short before F19 release !
>
>
> Remi.
> --
> devel
https://fedoraproject.org/wiki/Features/Php55
I just create the update to PHP 5.5.0 final.
https://admin.fedoraproject.org/updates/php-5.5.0-1.fc19
Very very short before F19 release !
Remi.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/d
Thanks Lars, I'll do as you suggest!
Best,
Mario
On 19 June 2013 23:35, Lars Seipel wrote:
> On Wed, Jun 19, 2013 at 04:42:30PM +0200, Mario Ceresa wrote:
> > does anybody know if it is currently possible to do GPU passthrough in
> kvm?
>
> You might want to ask that on the Fedora virt list[1
As it may be interesting and I have the data on hand, here's the package
diff between a minimal install of F16 and a minimal install of F19. F16
has 203 packages (I think it's really 202 but I somehow got an extra one
into my test), F19 TC6 has 238.
--- 16min.txt 2013-06-19 09:06:52.075305098 -0
68 matches
Mail list logo
