Re: Service units for web applications

On Tue, Feb 25, 2014 at 04:11:23PM -0700, Stephen John Smoogen wrote: > On 25 February 2014 16:04, Simo Sorce wrote: > > On Tue, 2014-02-25 at 22:41 +0100, Lennart Poettering wrote: > > > Mabye httpd.rpm wants to include a tool that has a similar "feel" like > > > systemctl, maybe "httpdctl" or so

Re: F21 Self Contained Change: Allwinner sunxi (A10 / A13 / A20) ARM SoC support

Does the u-boot piece require a new package or sub package of existing u-boot we already have? Just curious. Suppose I'm asking if the sunxi support is upstream in denx? Looking forward to this feature. :-D Thanks On Mar 3, 2014 8:05 AM, "Jaroslav Reznik" wrote: > = Proposed Self Contained Cha

Re: Server Technical Specification: Agenda and First Draft

The base wg has been wondering the same for containers, and at this point we may follow this guidance regarding libvirt too. I'll probably advocate this at our next meeting. Thanks On Mar 3, 2014 6:09 AM, "Stephen Gallagher" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 02/28/2

Re: default file system, was: Comparison to Workstation Technical Specification

On 03/02/2014 10:55 PM, Chris Murphy wrote: On Mar 2, 2014, at 9:35 PM, Nathanael Noblet wrote: On 03/01/2014 04:57 PM, Chris Murphy wrote: The servers were rented with a Fedora produced default/automatic/guided partitioning layout? If not, your example is out of scope. We are only talking

Re: default file system, was: Comparison to Workstation Technical Specification

On 3/3/14, 7:34 PM, Chris Adams wrote: > Once upon a time, Eric Sandeen said: >> The shrink/grow thing was clever, but also a bit abusive from a filesystem >> design point of view. > > How does it compare to the suggested alternative, LVM thin provisioning? > How well does thinp handle fragmentat

Re: default file system, was: Comparison to Workstation Technical Specification

On Mon, 2014-03-03 at 08:59 -0500, Stephen Gallagher wrote: > Now, if you want to talk about having some sort of click-through for > "I want to try out some experimental options without going all the way > to customizing my layout manually", that (to me) needs to be a > different, third path. But

Re: default file system, was: Comparison to Workstation Technical Specification

On Mar 3, 2014, at 4:57 PM, Jon wrote: > > We no longer release Fedora ARM rootfs tarballs, too hard to educate > people to do the right thing with ACL's, xattrs, selinux, etc... > Anyhow, it's actually a great way to ship a Fedora rootfs... just > shrink the filesystem down to the smallest size

Re: default file system, was: Comparison to Workstation Technical Specification

On Mon, 2014-03-03 at 18:50 -0800, Adam Williamson wrote: > On Sun, 2014-03-02 at 14:27 +, Richard W.M. Jones wrote: > > On Fri, Feb 28, 2014 at 01:03:38PM -0800, Adam Williamson wrote: > > > What I came up with is this gem: > > > > > > https://fedoraproject.org/wiki/User:Adamwill/Draft_storag

Re: default file system, was: Comparison to Workstation Technical Specification

On Sun, 2014-03-02 at 14:27 +, Richard W.M. Jones wrote: > On Fri, Feb 28, 2014 at 01:03:38PM -0800, Adam Williamson wrote: > > What I came up with is this gem: > > > > https://fedoraproject.org/wiki/User:Adamwill/Draft_storage_matrix > [...] > > Some of this is susceptible to automation, but

Re: Major release number bump is lower than beta for html5lib module.

On Mon, 2014-03-03 at 11:05 +0100, Kevin Kofler wrote: > Reindl Harald wrote: > > yes it is a hack but better than fake version numbers to > > satisfy RPM and that is *the* reason epoch exists at all > > +1 > > That Ubuntu-style apples-101.reallyoranges versioning is misleading and > against Fed

Re: default file system, was: Comparison to Workstation Technical Specification

Once upon a time, Eric Sandeen said: > The shrink/grow thing was clever, but also a bit abusive from a filesystem > design point of view. How does it compare to the suggested alternative, LVM thin provisioning? How well does thinp handle fragmentation; is there a "defrag" for thinp available (or

Re: Has support for Pentium III been terminated?

On Mon, Mar 03, 2014 at 06:48:15PM -0500, Felix Miata wrote: > Anyone know where to find a howto for capturing a crash that > triggers a system halt or reboot? Try a serial console or maybe netconsole. Zbyszek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mai

Re: default file system, was: Comparison to Workstation Technical Specification

On 3/3/14, 5:57 PM, Jon wrote: > On Sat, Mar 1, 2014 at 3:18 PM, Chris Murphy wrote: >> >> On Mar 1, 2014, at 1:19 PM, Jon wrote: >> >>> The inability to shrink or reduce XFS is rather disappointing. I've >>> seen a few sarcastic remarks along the lines of (paraphrased): why >>> would anyone ever

Re: default file system, was: Comparison to Workstation Technical Specification

On Sat, Mar 1, 2014 at 3:18 PM, Chris Murphy wrote: > > On Mar 1, 2014, at 1:19 PM, Jon wrote: > >> The inability to shrink or reduce XFS is rather disappointing. I've >> seen a few sarcastic remarks along the lines of (paraphrased): why >> would anyone ever want to shrink a volume? > > In the co

Re: Has support for Pentium III been terminated?

Peter wrote: you'll need to capture the crash though, I suspect it's a driver crash or similar. Anyone know where to find a howto for capturing a crash that triggers a system halt or reboot? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (N

Fedora Atomic Initiative (rpm-ostree 2014.5)

Hi, I'm happy to announce a new version of rpm-ostree - v2014.5: https://github.com/cgwalters/rpm-ostree/commit/848fdcb350877ab509c2fef3e482d8da8c97c717 With this new release, there is now a new overarching name/brand for the project formerly known as "rpm-ostree": Fedora Atomic Initiative --

Re: copr epel-7-ppc64?

On 03/03/2014 12:46 AM, Miroslav Suchý wrote: On 03/01/2014 05:32 AM, Orion Poplawski wrote: Is there any chance of being able to do epel-7-ppc64 copr builds anytime in the near future? I'd to test if a particular fix to gcc will fix an ICE I'm seeing while compiling eigen3. copr seems to be t

Re: default file system, was: Comparison to Workstation Technical Specification

On 03/03/2014 11:29 PM, Eric Sandeen wrote: On 3/3/14, 3:16 PM, Matthias Clasen wrote: On Mon, 2014-03-03 at 16:16 +0200, Ric Wheeler wrote: I am fine with something like what is proposed by Steve above - let users have the GUI present an option that gives preference to the default without to

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 04:29 PM, Eric Sandeen wrote: > On 3/3/14, 3:16 PM, Matthias Clasen wrote: >> On Mon, 2014-03-03 at 16:16 +0200, Ric Wheeler wrote: >> >> >>> I am fine with something like what is proposed by Steve above - >>> let users have the GUI pre

Re: default file system, was: Comparison to Workstation Technical Specification

On 3/3/14, 3:16 PM, Matthias Clasen wrote: > On Mon, 2014-03-03 at 16:16 +0200, Ric Wheeler wrote: > > >> I am fine with something like what is proposed by Steve above - let users >> have >> the GUI present an option that gives preference to the default without >> totally >> hiding other opti

Re: default file system, was: Comparison to Workstation Technical Specification

On 03/03/2014 11:16 PM, Matthias Clasen wrote: On Mon, 2014-03-03 at 16:16 +0200, Ric Wheeler wrote: I am fine with something like what is proposed by Steve above - let users have the GUI present an option that gives preference to the default without totally hiding other options. You and Jose

Re: default file system, was: Comparison to Workstation Technical Specification

On Mon, 2014-03-03 at 16:16 +0200, Ric Wheeler wrote: > I am fine with something like what is proposed by Steve above - let users > have > the GUI present an option that gives preference to the default without > totally > hiding other options. You and Josef are sending mixed messages here: "

Re: default file system, was: Comparison to Workstation Technical Specification

> On Mon, Mar 03, 2014 at 09:22:53AM -0500, Stephen Gallagher wrote: >> On 03/03/2014 09:16 AM, Ric Wheeler wrote: >>> On 03/03/2014 04:06 PM, Josef Bacik wrote: On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > On

Empathy takes over Polari

Hi list Everytime I try to start Polari Empathy's IRC client takes over (and shuts down Polari). Is this a reported bug, and if so, in which package (Polari or empathy)? /Andreas -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Cod

Re: [Base] Fedora Base Design Working Group (2014-02-21) meeting minutes and logs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 01:53 PM, Chuck Anderson wrote: > On Mon, Mar 03, 2014 at 11:19:29AM -0700, Chris Murphy wrote: >> >> On Mar 3, 2014, at 10:42 AM, Miloslav Trmač >> wrote: >> >>> 2014-02-22 3:08 GMT+01:00 Chris Murphy >>> : On Feb 21, 2014, at 2:38 P

Re: [Base] Fedora Base Design Working Group (2014-02-21) meeting minutes and logs

On Mon, Mar 03, 2014 at 11:19:29AM -0700, Chris Murphy wrote: > > On Mar 3, 2014, at 10:42 AM, Miloslav Trmač wrote: > > > 2014-02-22 3:08 GMT+01:00 Chris Murphy : > > On Feb 21, 2014, at 2:38 PM, john.flor...@dart.biz wrote: > > The necessary context to add here is that both OS X and Windows ha

Re: [Base] Fedora Base Design Working Group (2014-02-21) meeting minutes and logs

On Mar 3, 2014, at 10:42 AM, Miloslav Trmač wrote: > 2014-02-22 3:08 GMT+01:00 Chris Murphy : > On Feb 21, 2014, at 2:38 PM, john.flor...@dart.biz wrote: > > > That makes a lot of sense, but I'd like to add that when doing custom > > partitioning, you can easily spend the bulk of your actual i

Re: [Base] Fedora Base Design Working Group (2014-02-21) meeting minutes and logs

2014-02-22 3:08 GMT+01:00 Chris Murphy : > On Feb 21, 2014, at 2:38 PM, john.flor...@dart.biz wrote: > > > That makes a lot of sense, but I'd like to add that when doing custom > partitioning, you can easily spend the bulk of your actual interaction time > getting the partitioning customized exact

Fwd: Re: default file system, was: Comparison to Workstation Technical Specification

> On Mon, Mar 03, 2014 at 09:22:53AM -0500, Stephen Gallagher wrote: >> On 03/03/2014 09:16 AM, Ric Wheeler wrote: >>> On 03/03/2014 04:06 PM, Josef Bacik wrote: On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > On 0

Re: default file system, was: Comparison to Workstation Technical Specification

On Mar 3, 2014, at 6:59 AM, Stephen Gallagher wrote: > > To something like: > * XFS-LVM (Recommended) > * XFS > * EXT4-LVM > * EXT4 > * BTRFS (Experimental) I realize this is not a serious recommendation. However, please no file system Smögåsbord in the guided option. The ice cream truck offe

Re: libgcrypt soname bump in rawhide

On Pá, 2014-02-28 at 14:51 -0500, Simo Sorce wrote: > On Fri, 2014-02-28 at 19:37 +, Richard Hughes wrote: > > On 28 February 2014 15:38, Tomas Mraz wrote: > > > This should not break builds of any reasonably current software. > > > > libgcrypt.so.11()(64bit) is needed by (installed) > > goog

Re: default file system, was: Comparison to Workstation Technical Specification

On 03/03/2014 04:40 PM, David Cantrell wrote: On Mon, Mar 03, 2014 at 09:22:53AM -0500, Stephen Gallagher wrote: On 03/03/2014 09:16 AM, Ric Wheeler wrote: On 03/03/2014 04:06 PM, Josef Bacik wrote: On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher wrote: -BEGIN PGP SIGNED MESSAGE- H

[Bug 1071641] perl-Path-IsDev-1.001000 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1071641 Jitka Plesnikova changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

[Owner-change] Fedora packages ownership change

Change in ownership over the last 168 hours === 1 packages were orphaned gnomeradio [f19] was orphaned by rathann Graphical FM-Tuner program for GNOME https://admin.fedoraproject.org/pkgdb/acls/name/gnomeradio 8 packages u

rawhide report: 20140303 changes

Broken deps for i386 -- [boost] boost-graph-mpich-1.54.0-11.fc21.i686 requires libmpichcxx.so.10 boost-graph-mpich-1.54.0-11.fc21.i686 requires libmpich.so.10 boost-mpich-1.54.0-11.fc21.i686 requires libmpichcxx.so.10

[perl-Test-Kwalitee-Extra/f19] Initial import (perl-Test-Kwalitee-Extra-0.2.0-2)

Summary of changes: 7075169... Initial import (perl-Test-Kwalitee-Extra-0.2.0-2) (*) (*) 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-de...@lists.fedoraproject.org h

F21 Self Contained Change: Lohit Odia Gurumukhi font naming

= Proposed Self Contained Change: Lohit Odia Gurumukhi font naming = https://fedoraproject.org/wiki/Changes/Lohit_Odia_Gurumukhi Change owner(s): Pravin Satpute This is a change to make Lohit Oriya fonts name as per the guidelines by Odisha governement and improve Lohit Punjabi font name to a

Re: default file system, was: Comparison to Workstation Technical Specification

On Mon, Mar 03, 2014 at 09:22:53AM -0500, Stephen Gallagher wrote: > On 03/03/2014 09:16 AM, Ric Wheeler wrote: > > On 03/03/2014 04:06 PM, Josef Bacik wrote: > >> On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher > >> wrote: > >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > >>> > >>> On 03/

Re: Service units for web applications

On 02/25/2014 08:07 PM, Lennart Poettering wrote: > On Tue, 25.02.14 14:55, Stephen Gallagher (sgall...@redhat.com) wrote: > >> There are actually two pieces to this that I'd like to see (and >> hopefully have someone tell me are already possible): >> >> 1. The ability to add new ExecStartPre com

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 09:16 AM, Ric Wheeler wrote: > On 03/03/2014 04:06 PM, Josef Bacik wrote: >> On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher >> wrote: >>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >>> >>> On 03/03/2014 08:51 AM, Ric Wheeler wrot

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 09:06 AM, Josef Bacik wrote: > On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher > wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 03/03/2014 08:51 AM, Ric Wheeler wrote: >>> On 03/03/2014 03:43 PM, Stephen Gallagher wr

Re: default file system, was: Comparison to Workstation Technical Specification

On 03/03/2014 04:06 PM, Josef Bacik wrote: On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 08:51 AM, Ric Wheeler wrote: On 03/03/2014 03:43 PM, Stephen Gallagher wrote: So if you were asking me "Are we removing btrfs from t

Re: default file system, was: Comparison to Workstation Technical Specification

On Mon, Mar 3, 2014 at 8:59 AM, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/03/2014 08:51 AM, Ric Wheeler wrote: >> On 03/03/2014 03:43 PM, Stephen Gallagher wrote: >>> So if you were asking me "Are we removing btrfs from the install >>> options completely?

F21 Self Contained Change: Allwinner sunxi (A10 / A13 / A20) ARM SoC support

= Proposed Self Contained Change: Allwinner sunxi (A10 / A13 / A20) ARM SoC support = https://fedoraproject.org/wiki/Changes/AllwinnerSunxiSupport Change owner(s): Hans de Goede , Peter Robinson Allwinner A10 / A13 / A20 SoCs are used in a number of popular low cost arm development boards and

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 08:51 AM, Ric Wheeler wrote: > On 03/03/2014 03:43 PM, Stephen Gallagher wrote: >> So if you were asking me "Are we removing btrfs from the install >> options completely?", the answer is a resounding "NO". However, >> if you're asking "A

Re: default file system, was: Comparison to Workstation Technical Specification

On 03/03/2014 03:43 PM, Stephen Gallagher wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 08:32 AM, Josef Bacik wrote: On Mar 3, 2014 7:34 AM, "Stephen Gallagher" mailto:sgall...@redhat.com>> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/2014 06:38 PM, Chris

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/03/2014 08:32 AM, Josef Bacik wrote: > > On Mar 3, 2014 7:34 AM, "Stephen Gallagher" > wrote: >> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> >> On 03/01/2014 06:38 PM, Chris Murphy wrote: >>> >>> On Mar 1,

Re: default file system, was: Comparison to Workstation Technical Specification

On Mar 3, 2014 7:34 AM, "Stephen Gallagher" wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/01/2014 06:38 PM, Chris Murphy wrote: > > > > On Mar 1, 2014, at 3:58 PM, Reindl Harald > > wrote: > > > >> > >> > >> Am 01.03.2014 22:55, schrieb poma: > >>> On 27.02.2014 01:33, Jose

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/2014 06:38 PM, Chris Murphy wrote: > > On Mar 1, 2014, at 3:58 PM, Reindl Harald > wrote: > >> >> >> Am 01.03.2014 22:55, schrieb poma: >>> On 27.02.2014 01:33, Josef Bacik wrote: >>> Just popping in here to say that btrfs is not r

Re: default file system, was: Comparison to Workstation Technical Specification

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/01/2014 04:18 PM, Chris Murphy wrote: > > On Mar 1, 2014, at 1:19 PM, Jon wrote: > >> The inability to shrink or reduce XFS is rather disappointing. >> I've seen a few sarcastic remarks along the lines of >> (paraphrased): why would anyone ev

Re: Server Technical Specification: Agenda and First Draft

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/28/2014 07:19 PM, Lennart Poettering wrote: > On Fri, 28.02.14 15:37, Daniel J Walsh (dwa...@redhat.com) wrote: > >>> sgallagh: "systemd-nspawn will be used to manage >>> containerization capabilities. " did I miss something or >>> doesn't upst

Re: fedpkg build failing (due to NSS?)

Am 03.03.2014 09:14, schrieb Mathieu Bridon: > On Mon, 2014-03-03 at 16:06 +0800, Christopher Meng wrote: >> I've left a negative karma there, they forgot to add the new nss-util >> into overrides list. > > No, it's been added, but then it was expired: > https://admin.fedoraproject.org/updates/o

Re: default file system, was: Comparison to Workstation Technical Specification

On 2 March 2014 14:56, Ric Wheeler wrote: > On 03/02/2014 01:17 PM, Ian Malone wrote: >>> >>> Can we get some definition of "legacy" here? kernel/nfs-utils versions? >>> > >> >> I'd have to check what I can share. If it helps: not current RHEL or >> recent Fedora, until recently some that were ov

Agenda for Env-and-Stacks WG meeting (2014-03-03)

WG meeting will be at 13:00 UTC in #fedora-meeting on Freenode. == Topic == # additional repository # Playground requirements # let's discuss: https://fedoraproject.org/wiki/Env_and_Stacks/Playground_repository_%28draft%29 # Git for Copr - let's come to conclusion # chair(wo)man for next wee

[perl-Devel-Autoflush] 0.06 bump

commit c2fa71edd54bfb8445cba4675cd0f4013035aa0e Author: Petr Písař Date: Mon Mar 3 11:26:38 2014 +0100 0.06 bump .gitignore|1 + perl-Devel-Autoflush.spec | 29 ++--- sources |2 +- 3 files changed, 20 insertions(+), 12 d

Re: Has support for Pentium III been terminated?

Felix Miata wrote: > I have a F20 I switched to Rawhide on host gx150. Shortly after getting > KDE started, the system reboots. Something similar happens in openSUSE: > https://bugzilla.novell.com/show_bug.cgi?id=856606 This looks like a driver bug to me. By the way, for Qt 4, Qt upstream does no

Re: Major release number bump is lower than beta for html5lib module.

Reindl Harald wrote: > yes it is a hack but better than fake version numbers to > satisfy RPM and that is *the* reason epoch exists at all +1 That Ubuntu-style apples-101.reallyoranges versioning is misleading and against Fedora packaging guidelines. Kevin Kofler -- devel mailing list

Re: libgcrypt soname bump in rawhide

On 03/03/2014 10:13 AM, Vít Ondruch wrote: > Dne 28.2.2014 20:51, Simo Sorce napsal(a): >> On Fri, 2014-02-28 at 19:37 +, Richard Hughes wrote: >>> On 28 February 2014 15:38, Tomas Mraz wrote: This should not break builds of any reasonably current software. >>> libgcrypt.so.11()(64bit) is

Re: exclude people from giving karma?

Michael Catanzaro wrote: > Or requiring min time in updates-testing (2-3 days) before an > autokarma-assisted push. Please no even more complex heuristics! The system is already hard enough to understand as is. Just turn the flawed heuristics off. Kevin Kofler -- devel mailing list dev

Re: libgcrypt soname bump in rawhide

Dne 28.2.2014 20:51, Simo Sorce napsal(a): > On Fri, 2014-02-28 at 19:37 +, Richard Hughes wrote: >> On 28 February 2014 15:38, Tomas Mraz wrote: >>> This should not break builds of any reasonably current software. >> libgcrypt.so.11()(64bit) is needed by (installed) >> google-chrome-stable-33

Re: fedpkg build failing (due to NSS?)

Le 03/03/2014 09:34, Mathieu Bridon a écrit : > This would tell you when it's ready: > $ koji wait-repo f20-build --build=nss-softokn-3.15.5-1.fc20 > --build=nss-util-3.15.5-1.fc20 F20 buldroot is now fixed. Remi. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraprojec

Re: fedpkg build failing (due to NSS?)

On Mon, 2014-03-03 at 16:34 +0800, Mathieu Bridon wrote: > > That is completely the wrong way to communicate this and it doesn't > > "get them the news" and in fact often stops people getting critical > > security or stability fixes for a pathetic little game. The way to > > communicate this proble

Re: fedpkg build failing (due to NSS?)

On Mon, 2014-03-03 at 08:26 +, Peter Robinson wrote: > >>> I've left a negative karma there, they forgot to add the new nss-util > >>> into overrides list. > >> > >> No, it's been added, but then it was expired: > >> https://admin.fedoraproject.org/updates/override/edit?build=nss-util-3.15.5-1.

Re: fedpkg build failing (due to NSS?)

>>> I've left a negative karma there, they forgot to add the new nss-util >>> into overrides list. >> >> No, it's been added, but then it was expired: >> https://admin.fedoraproject.org/updates/override/edit?build=nss-util-3.15.5-1.fc20 >> https://admin.fedoraproject.org/updates/override/edit?build

Re: fedpkg build failing (due to NSS?)

On Mon, Mar 3, 2014 at 4:14 PM, Mathieu Bridon wrote: > On Mon, 2014-03-03 at 16:06 +0800, Christopher Meng wrote: >> I've left a negative karma there, they forgot to add the new nss-util >> into overrides list. > > No, it's been added, but then it was expired: > https://admin.fedoraproject.org/up

Re: fedpkg build failing (due to NSS?)

On Mon, 2014-03-03 at 16:06 +0800, Christopher Meng wrote: > I've left a negative karma there, they forgot to add the new nss-util > into overrides list. No, it's been added, but then it was expired: https://admin.fedoraproject.org/updates/override/edit?build=nss-util-3.15.5-1.fc20 https://admin.f

Re: fedpkg build failing (due to NSS?)

I've left a negative karma there, they forgot to add the new nss-util into overrides list. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: fedpkg build failing (due to NSS?)

On Mon, 2014-03-03 at 08:56 +0100, Nikos Mavrogiannopoulos wrote: > Hello, > I'm trying to make an update for #1071795 using 'fedpkg build' for > gnutls fails consistently for f20 and rawhide with the error: > "BuildrootError: could not init mock buildroot, mock exited with status > 30; see root.l