Re: Change to DSO-linking semantics of the compiler

On 01/11/2010 10:45 AM, Charley Wang wrote: > Hi Fedora Developers, > > This is a quick announcement of the proposed change to DSO linking > (https://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking). > > The change will force explicit declaration of links rather than implicitly > detec

Re: Is abrt broken?

On 01/15/2010 05:41 AM, Jiri Moskovcak wrote: > On 01/15/2010 01:10 PM, Neal Becker wrote: >> This is the second time in a row, generating backtrace seems to run forever. >> Something wrong? >> abrt-1.0.3-1.fc12.x86_64 >> > > What is it you're trying to process? If it's some bigger thing like > F

Re: Adding ~/.local/bin to default PATH

On 07/26/2011 09:49 AM, Richard W.M. Jones wrote: > On Tue, Jul 26, 2011 at 08:45:11AM -0430, Robert Marcano wrote: >> In /etc/skel/.bash_profile they are added to the end and I think that is ok >> >> PATH=$PATH:$HOME/.local/bin:$HOME/bin > > This was added between bash-4.2.10 -2 and -3: > > http

Re: Fedora 14 Python 2.7.1?

On 07/31/2011 05:07 PM, Michel Alexandre Salim wrote: > On 08/01/2011 12:21 AM, Richard Shaw wrote: >> I figure there's a reason but I went ahead and tried a mock build of >> the F15 source in F14 and ran into a build problem[1]. I'm assuming >> that's the reason? >> > That build problem is similar

Re: Orphaning dnsmasq

On 08/24/2011 12:24 PM, Ian Pilcher wrote: > When libvirt starts dnsmasq, it tells it to ignore the configuration > file and passes all of the parameters on the command line. If you want > dnsmasq to not listen on 0.0.0.0:53 when it's started by libvirt, you'll > have to take that up with the libv

Re: yum-builddep (Re: Compiling 32bit on 64bit Fedora)

On 09/08/2011 06:27 AM, Adam Jackson wrote: > On Thu, 2011-09-08 at 10:44 +1000, Tony Breeds wrote: >> Hi All, >> On a related but different note. How hard would it be to get >> yum-builddep to take an --arch arg to that we can esily get the 32-bit >> builddeps on a 64-bit system? > > Is 'se

Re: UsrMove feature (was Re: FESCo meeting minutes for 2011-10-24)

On 10/25/2011 11:24 AM, Michał Piotrowski wrote: > W dniu 25 października 2011 09:26 użytkownik Michał Piotrowski > napisał: >> W dniu 25 października 2011 09:20 użytkownik Harald Hoyer >> napisał: >>> On 10/24/2011 10:12 PM, Michał Piotrowski wrote: In any case #!/usr/bin/env sh s

serial kernel console vs. systemd

Hi, I'm trying to debug some kernel crashes that I'm getting in a virtual machine running rawhide. Adding "console=ttyS0,57600 console=tty0" to the guest kernel used to work so "virsh console my-vm" would get me all the kernel messages. Now in this systemd world, I get *some* messages as it runs

Re: serial kernel console vs. systemd

On 05/19/2011 11:57 AM, Lennart Poettering wrote: > systemd does not redirect kmsg. > > We actually are no longer reading console= from the kernel cmdline. We > now rely entirely on /sys/class/tty/console/active which gives us > similar information. And we use it only and exclusively to spawn a ge

Re: serial kernel console vs. systemd

On 05/19/2011 12:56 PM, Bill Nottingham wrote: > Josh Stone (jist...@redhat.com) said: >>> Anyway, if kmsg msgs are lost for you this probably happens inside of >>> ply or something related, but not systemd. >> >> Is "ply" part of (or short for) plymo

Re: serial kernel console vs. systemd

On 05/26/2011 01:09 AM, Richard W.M. Jones wrote: > A rather late follow-up, but next time your VM crashes hard you could > try this: > > https://rwmj.wordpress.com/2011/05/25/fun-new-virt-tools-virt-dmesg-and-virt-uname/ > http://people.redhat.com/~rjones/virt-dmesg/ > > You will need the update

rawhide missed an implicit dependency for #!python

Hi, Our dtrace script in systemtap-sdt-devel starts "#!/usr/bin/python". Usually this leads to an implicit "Requires: /usr/bin/python", but for some reason our rawhide build did not get this. The F15, F14, and F13 builds from the same spec required python as expected. The rawhide build which mis

Re: rawhide missed an implicit dependency for #!python

On 06/02/2011 01:34 PM, Peter Robinson wrote: > Is it set as executable? If not the department scan will ignore it. Yes, it is executable: http://koji.fedoraproject.org/koji/fileinfo?rpmID=2556409&filename=/usr/bin/dtrace -- devel mailing list devel@lists.fedoraproject.org https://admin.fedorapro

Re: rawhide missed an implicit dependency for #!python

On 06/02/2011 01:26 PM, Josh Stone wrote: > Our dtrace script in systemtap-sdt-devel starts "#!/usr/bin/python". > Usually this leads to an implicit "Requires: /usr/bin/python", but for > some reason our rawhide build did not get this. The F15, F14, and F13 > bu

Re: Reminder: Fedora 13 end of life on 2011-06-24

On 06/12/2011 04:11 PM, nomnex wrote: > I might wait for F16 to do a clean install. It's the first time I reach > an EOL. Can you tell me if the packages in the F13 repository > remains available (even though the packages are not updated) > past June, or not? Thanks The archives are here: http://

Re: Heads up: impending IPv6 Test Day

On 06/21/2011 05:54 AM, Andreas Schwab wrote: > David Woodhouse writes: > >> And curl is just broken for numeric IPv6 addresses completely: >> >> [dwmw2@i7 activesyncd]$ curl http://[2001:8b0:10b:1:21d:7dff:fe04:dbe2]/ >> curl: (3) [globbing] error: bad range specification after pos 9 > > $ curl

Re: Name that Tree!

On 02/12/2010 04:45 PM, Jesse Keating wrote: > As part of no frozen rawhide, we'll have a new tree on the mirrors, > pub/fedora/linux/development/13 That's where we'll be putting things > that are tagged for the release after they get through testing. We > don't yet have a clever name for this co

Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)

On 02/27/2010 02:05 PM, Orcan Ogetbil wrote: > About F-11, F-12, F-13: yeah, pretty much. They should all contain the > same stable version of most software. Then why have numbered Fedora releases at all? Just so we can bump the wallpaper every once in a while? Josh -- devel mailing list devel@

Re: OT: fas-username vs. local username for fedora-cvs

On 03/01/2010 11:05 AM, Josephine Tannhäuser wrote: > Hi all! > > My username on my private pc is josephine, my username on my > workstation is josephine.tannhauser, but my fas-username is tannhauser. > > how can I use fedora-cvs on these machines? It seems that fedora-cvs > want to use the local

Re: FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)

On 03/01/2010 11:46 AM, Seth Vidal wrote: >>> One thing to consider: while from a psychological standpoint, a regression >>> is indeed perceived as much worse than an unfixed bug, from a technical / >>> practical standpoint it's actually the smaller issue: you can rollback to >>> the version of the

Re: Update question: some user data

On 03/06/2010 11:04 AM, Adam Williamson wrote: > I tried to present the poll in a very neutral way, and as far as I know, > it hasn't been linked to from anywhere else; only regular forum members > are likely to come across it. So it shouldn't be massively inherently > biased, and has a reasonable

Re: Proposed udpates policy change

On 03/09/2010 05:32 AM, Joe Orton wrote: > On Tue, Mar 09, 2010 at 02:20:20PM +0100, Mathieu Bridon wrote: >> If the issues this update was solbing really bothered them, they would >> have provided feedback earlier. > > Hah, right. Back in the real world, most users expect free cake and > compla

Re: QA's Package update policy proposal

On 03/09/2010 03:43 PM, Kevin Kofler wrote: > James Laska wrote: >> 3. Package must be newer than previously released versions - can't >> ship newer package in N-1. > > Definitely, but we must make sure that it's still possible to queue the same > update for N and N-1 at the same tim

Re: QA's Package update policy proposal

On 03/09/2010 04:11 PM, Jesse Keating wrote: > Even if you put an update for N and N-1 in the same form, once you > submit the request it splits it into two requests, one per Fedora > release. This means you'd have one set of karma per Fedora release. Aha, I forgot that. Thanks. Josh -- devel

Re: Stable Release Updates types proposal (was Re: Fedora Board Meeting Recap 2010-03-11)

Matthew Woehlke wrote: > Anyone know of a distro that doesn't lag like Ubuntu/NewFedora? Is > Mandrake kept up to date, or do they also make you wait months for new > versions? Because I am *seriously* considering switching right now... Arch? -- devel mailing list devel@lists.fedoraproject.org

Re: Why does git merge have so much trouble with Fedora package branches?

On 11/10/2011 10:15 AM, Jesse Keating wrote: > On Nov 10, 2011, at 1:52 AM, Fabian Deutsch wrote: >> >> Someone might correct me, but rebasing introduces problems for >> co-maintainers, if upstream (maintainer) decides to rebase some >> branch. >> >> See http://man.he.net/man1/git-rebase > > Ou

Re: Changing kernel API / Breaking VirtualBox - update criteria violation?

On 11/22/2011 09:51 AM, Michael Cronenworth wrote: > -#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 1, 0) It may have be helpful for the faked 2.6.4x kernels to still present a 3ish LINUX_VERSION_CODE. AFAIK, faking the number is for the benefit of userspace, not any kernel module. Perhaps it's not

Re: Changing kernel API / Breaking VirtualBox - update criteria violation?

On 11/28/2011 12:47 PM, Chuck Ebbert wrote: > On Tue, 22 Nov 2011 10:06:32 -0800 > Josh Stone wrote: > >> On 11/22/2011 09:51 AM, Michael Cronenworth wrote: >>> -#if LINUX_VERSION_CODE < KERNEL_VERSION(3, 1, 0) >> >> It may have be helpful for the faked 2.

Re: Changing kernel API / Breaking VirtualBox - update criteria violation?

On 12/05/2011 01:05 PM, Sérgio Basto wrote: > Hi, Now I'm co-maintaining VirtualBox on rpmfusion > you got on my external link VB 4.1.4 for F15 > http://www.serjux.com/virtualbox/ > if you try it let me know , I grabbed and extracted just the kmodsrc, all the modules within now build fine. So th

Re: Changing kernel API / Breaking VirtualBox - update criteria violation?

On 12/05/2011 05:09 PM, Sérgio Basto wrote: > On Mon, 2011-12-05 at 15:41 -0800, Josh Stone wrote: >> I grabbed and extracted just the kmodsrc, all the modules within now >> build fine. So the new version information is doing the right thing, >> representing itself a

Re: sched_autogroup interactivity patch for the desktop

On 11/16/2010 09:14 AM, Lennart Poettering wrote: > This appears completely backwards to me. Attaching things like this to a > TTY is just wrong, because normally we don't have a single TTY around on > most graphical sessions. > > The kernel doesn't really have a notion of what a "session" is (onl

Re: heads-up: systemtap-sdt-devel rebase in rawhide

On 01/19/2011 02:20 PM, Tom Lane wrote: > f...@redhat.com (Frank Ch. Eigler) writes: >> I agree. It's not a great situation, but local GCC/C++ experts have >> found no better way to type-analyze the parameters, to ensure their >> safe passage to the tool. (Our testing shows is not >> offensive t

Re: The move to git!

Thanks for dist-git -- one step closer to banishing CVS from my life! :) A git trick I'd like fedpkg to learn is to use separate url/pushurl, e.g. in .git/config: [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = git://pkgs.fedoraproject.org/foo pushurl =

Re: The move to git!

On 07/30/2010 11:36 AM, Hans Ulrich Niedermann wrote: > On Fri, 2010-07-30 at 11:15 -0700, Jesse Keating wrote: >> On 07/30/2010 09:14 AM, Josh Stone wrote: >>> A git trick I'd like fedpkg to learn is to use separate url/pushurl, >>> e.g. in .git/config: >>

Re: Boost updated to 1.58.0 in rawhide and f23

On 07/22/2015 07:50 AM, Jonathan Wakely wrote: > On 22/07/15 15:30 +0100, Tom Hughes wrote: >> On 22/07/15 14:54, Jonathan Wakely wrote: >> >>> mapnik-0:2.2.1-0.4.20150127git0639d54.fc23.src >>> nodejs-mapnik-vector-tile-0:0.6.2-6.fc23.src >> >> I did these for both branches when you announced it a

Re: Boost updated to 1.58.0 in rawhide and f23

On 07/23/2015 02:33 PM, Josh Stone wrote: > Is this a general failure in f23-boost, or just a few packages? The f23-boost target tag is using build tag f23-build! http://koji.fedoraproject.org/koji/buildtargetinfo?targetID=150 vs f24-boost has itself for both build and destination tag: h

Re: Boost updated to 1.58.0 in rawhide and f23

On 07/24/2015 02:31 AM, Jonathan Wakely wrote: > On 23/07/15 14:39 -0700, Josh Stone wrote: >> On 07/23/2015 02:33 PM, Josh Stone wrote: >>> Is this a general failure in f23-boost, or just a few packages? >> >> The f23-boost target tag is using build tag f23-build! &g

Re: Same comand names in /usr/bin and /usr/sbin

On 08/10/2015 11:12 AM, Orion Poplawski wrote: > iproute has /usr/sbin/ss > stripesnoop has /usr/bin/ss > > This causes problems: https://bugzilla.redhat.com/show_bug.cgi?id=1249328 > > It seems like we should have a policy prohibiting different programs with the > same command names being in /us

Re: Same comand names in /usr/bin and /usr/sbin

On 08/10/2015 11:54 AM, Reindl Harald wrote: > > Am 10.08.2015 um 20:50 schrieb Josh Stone: >> On 08/10/2015 11:12 AM, Orion Poplawski wrote: >>> iproute has /usr/sbin/ss >>> stripesnoop has /usr/bin/ss >>> >>> This causes problems: https://bugzil

Re: Is it time to allow Chromium in Fedora?

On 08/11/2015 12:12 PM, Chris Murphy wrote: > Yet I see a Linux tar.bz2 for Firefox at downloads.mozilla.org so I > wonder why that binary doesn't just run unmodified anywhere and I'm > waiting for 40.0 to show up in Bodhi? If you don't see the value of distro integration and testing, then by all

Re: Is it time to allow Chromium in Fedora?

On 08/11/2015 12:38 PM, Chris Murphy wrote: > On Tue, Aug 11, 2015 at 1:18 PM, Josh Stone wrote: >> On 08/11/2015 12:12 PM, Chris Murphy wrote: >>> Yet I see a Linux tar.bz2 for Firefox at downloads.mozilla.org so I >>> wonder why that binary doesn't just

Re: Is it time to allow Chromium in Fedora?

On 08/11/2015 02:04 PM, Reindl Harald wrote: > > > Am 11.08.2015 um 23:00 schrieb Mustafa Muhammad: >> >> On Aug 11, 2015 11:29 PM, "Reindl Harald" > > wrote: >> > >> > Am 11.08.2015 um 22:18 schrieb Mustafa Muhammad: >> >> >> >> > If I knew Mozilla's Linux bin

Re: Same comand names in /usr/bin and /usr/sbin

On 08/14/2015 10:24 AM, Lennart Poettering wrote: > On Mon, 10.08.15 11:50, Josh Stone (jist...@redhat.com) wrote: > >> On 08/10/2015 11:12 AM, Orion Poplawski wrote: >>> iproute has /usr/sbin/ss >>> stripesnoop has /usr/bin/ss >>> >>> T

Re: Rawhide plans

On 08/19/2015 08:18 AM, Kevin Fenzi wrote: > * Setup some gating. I think it should work like this: > > today you build a rawhide build and it tags into f24 tag, which is used > by the daily compose. > > I'd like to change that to build into a f24-candidate tag. At that > point taskotron or oth

Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking

I update from nss-3.19.3-1.0.fc22.x86_64 to nss-3.20.0-1.0.fc22.x86_64 this morning, and now I get this stderr output: $ /usr/bin/stap -V >/dev/null /usr/bin/stap: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking The message comes from ld.so; that symbol co

Re: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking

On 09/04/2015 07:11 AM, Jakub Jelinek wrote: > On Fri, Sep 04, 2015 at 03:58:12PM +0200, Florian Weimer wrote: >> On 09/04/2015 03:49 PM, Jakub Jelinek wrote: >> >>> Clearly it is used by some programs, so it should be considered part of the >>> public API. If it wasn't meant to be exported, it sh

Re: [Fedora-packaging] Proposal to reduce anti-bundling requirements

On 09/11/2015 10:35 AM, Stephen Gallagher wrote: > Actually, the opposite is true. RHEL has fewer limitations in this > space. Red Hat's layered projects ship a fair amount of bundled stuff. > This problem is entirely Fedora's. Fedora has far stricter rules than > RHEL in this regard. It helps tha

Re: Heads up: glibmm/gtkmm now requires -std=c++11

On 09/22/2015 05:49 PM, Mamoru TASAKA wrote: > Kalev Lember wrote on 09/23/2015 09:35 AM: >> Hi, >> >> A quick heads up to anybody who might run into cryptic build errors when >> building apps that use glibmm/gtkmm: >> >> Latest glibmm/gtkmm stack in rawhide and F23 now uses C++11 features in >> he

Re: Brokenness in newly created dist-git repositories

On 07/22/2014 12:11 PM, Richard W.M. Jones wrote: > > Two new packages/repositories have been created for me recently. > Both appear to be broken in a subtle, non-fatal way: > > $ fedpkg clone ocaml-camlp4 > $ cd ocaml-camlp4/ > $ fedpkg verrel > Exception AttributeError: '_read_only' in

Re: Finding all the source packages that include a copy of valgrind.h

On 09/12/2014 08:09 AM, Mark Wielaard wrote: > Hi, > > valgrind 3.10.0 was just released and I created packages for rawhide and > f21. Then I noticed some packages include their own copy of valgrind.h > (at least libsecret, gcr, libgnome-keyring, realmd, ipxe and pidgin). > That means they won't h

Re: What are the ELF shared lib symbol versioning best practices?

On 10/21/2014 10:59 AM, David Howells wrote: > Is there a good description of ELF shared library symbol versioning best > practices somewhere? If you haven't already read Uli's paper, that's a start: http://www.akkadia.org/drepper/dsohowto.pdf (section 3 in particular) -- devel mailing list deve

Re: Packaging rust-lang

On 04/27/2015 02:35 AM, Fabian Deutsch wrote: > Hey, > > there is some interest (the interested people are BCC'ed) in packaging > [Rust](http://www.rust-lang.org). > The packaging request is tracked here: Bug 915043 - Package rust (lang) > > There are two main parts to get the packaging done: > (

Re: Packaging rust-lang

On 04/30/2015 02:56 AM, Dominik 'Rathann' Mierzejewski wrote: > On Wednesday, 29 April 2015 at 19:15, Josh Stone wrote: >> On 04/27/2015 02:35 AM, Fabian Deutsch wrote: >>> Hey, >>> >>> there is some interest (the interested people are BCC'e

Re: In Fedora22, GCC not enabled the -fstack-protector by default, why?

On 06/29/2015 07:47 AM, 乱雪 wrote: > Such as: > > // x.c > #include > > int main(void) { > char x[] = "abc"; > printf("%s\n", x); > return 0; > } > > and using GCC compile it: > > ➜ gcc x.c -v > > .. > /usr/libexec/gcc/x86_64-redhat-linux/5.1.1/cc1 -quiet -v x.c -quiet > -dumpbase

Re: Fwd: Re: late generation of assemble code

On 5/29/20 4:02 AM, Paul Dufresne via devel wrote: > * more space on the hard disks of the servers, because they contains > repositories only for LLVM IR packages rather than one by supported > architectures LLVM IR is not really arch-independent -- by the time you get to this level, all of the

Re: Fedora 33 System-Wide Change proposal: CompilerPolicy Change

On 6/5/20 5:27 AM, Neal Gompa wrote: >> Note that having stuff mix compilers is also a bad idea because LTO is >> compatible across the two compilers. If you want to use LTO, you need >> to use the same compiler across the chain, or stuff will break. >> > Yay thinkos... I mean that LTO is *not* com

Re: Dropping elfutils-libelf-devel-static and elfutils-devel-static subpackages

On 7/21/20 2:24 PM, Mark Wielaard wrote: > Nothing seems to require these packages, but that might be simply be > because they are static libraries, so there aren't any runtime > requirements. Is there some way to determine if anything would start > failing to build if I simply remove them? Apart f

Re: Dropping elfutils-libelf-devel-static and elfutils-devel-static subpackages

On 7/21/20 3:12 PM, Mark Wielaard wrote: >>> Is there a procedure to follow for dropping these sub-packages, or can >>> I simply remove them from the spec file? >> >> Maybe add Obsoletes to the devel subpackages, but not Provides. >> >> https://docs.fedoraproject.org/en-US/packaging-guidelines/#ren

License change for rust-crossbeam-channel

rust-crossbeam-channel-0.4.3-1.fc33 has changed its license from a combined "(MIT or ASL 2.0) and BSD" to just "MIT or ASL 2.0". See also: https://github.com/crossbeam-rs/crossbeam/issues/536 ___ devel mailing list -- devel@lists.fedoraproject.org To unsu

Re: R: Re: Primary Architectures: Another Proposal (RFC)

On 04/10/2012 10:12 AM, Digimer wrote: > Can someone remove this user from the list until they fix their email > program? From the headers, it looks like bastion.fedoraproject.org repeatedly sending it out. Everything up to that has the same Received header. -- devel mailing list devel@lists.fed

Re: R: Re: Primary Architectures: Another Proposal (RFC)

On 04/10/2012 10:17 AM, Josh Stone wrote: > On 04/10/2012 10:12 AM, Digimer wrote: >> Can someone remove this user from the list until they fix their email >> program? > > From the headers, it looks like bastion.fedoraproject.org repeatedly > sending it out. Everything

Re: While we're talking about RPM dependencies ...

On 04/12/2012 01:54 PM, Richard W.M. Jones wrote: > On Thu, Apr 12, 2012 at 04:40:14PM -0400, seth vidal wrote: >> On Thu, 12 Apr 2012 21:39:16 +0100 >> "Richard W.M. Jones" wrote: >> >>> On Thu, Apr 12, 2012 at 05:18:02PM +0200, Kevin Kofler wrote: Richard W.M. Jones wrote: > I think it

Re: GitHub is a terrible upstream

On 04/23/2012 01:08 PM, Orion Poplawski wrote: > Nice! I'll note explicitly that this also works with short git tags, so: > > > %global commit bd245c9 > > Source0: > https://github.com/jukka/pcfi/tarball/%{commit}/jukka-pcfi-%{commit}.tar.gz > > %setup -q -n jukka-pcfi-%{commit} > > works.

Re: Tests fail in mock env : unable to import BuildRequires Python module

On 03/12/2014 10:42 AM, Dan Scott wrote: > Per https://bugzilla.redhat.com/show_bug.cgi?id=1070074 I'm working on > updating python-rdflib to 4.1.1, but currently having trouble with a > new dependency on python-html5lib. > > The problem is that running a mock build fails as a few tests claim > th

python packages versus pydoc -k

Do we have any packaging requirements or guidelines for python modules to behave nicely with pydoc? I've seen this break a number of times, and sometimes the bugs I've filed have been fixed, sometimes ignored. Before I go through another round, I'd like to know if we have (or should have) some off

Re: python packages versus pydoc -k

On 03/12/2014 06:12 PM, Toshio Kuratomi wrote: > On Wed, Mar 12, 2014 at 12:18:17PM -0700, Josh Stone wrote: >> Do we have any packaging requirements or guidelines for python modules >> to behave nicely with pydoc? I've seen this break a number of times, >> and sometime

Re: python packages versus pydoc -k

On 03/13/2014 10:39 AM, Florian Festi wrote: > On 03/12/2014 08:18 PM, Josh Stone wrote: >> For instance, right now I get: >> >>> $ pydoc -k xyzzy >>> lib2to3.fixes.fix_repr - Fixer that transforms `xyzzy` into repr(xyzzy). >>> Traceback (most recent call

Re: over-riding an autodep for a sharedlib?

On 03/18/2014 08:30 AM, Kaleb KEITHLEY wrote: > > the samba.spec has: > >%package vfs-glusterfs >.. >Requires: glusterfs-api >= 3.4.0.16 >Requires: glusterfs >= 3.4.0.16 >.. > > The samba-vfs-glusterfs has these Requires (rpm -q --requires > samba-vfs-gluster) >glusterfs

Re: F21 System Wide Change: lbzip2 as default bzip2 implementation

On 04/02/2014 11:33 AM, Reindl Harald wrote: > packages using the library (output of yum remove > bzip2-libs-1.0.6-9.fc20.x86_64) Try: repoquery --whatrequires 'libbz2.so.1()(64bit)' We'll certainly need to keep the library around. -- devel mailing list devel@lists.fedoraproject.org https://adm

Re: libdwarf soname bump

On 05/22/2014 02:37 PM, Tom Hughes wrote: > I'm about to land a libdwarf update to version 20140519 in rawhide that > includes an soname bump to libdwarf.so.1. > > There only appears to be one dependant package, dyninst, so that will > need to be rebuilt - a quick check suggests that it doesn't

Re: Heads up: LLVM repackaging in F24

On 01/27/2016 10:25 AM, Stephen John Smoogen wrote: > > On Jan 27, 2016 11:26, "Neal Gompa" > wrote: >> >> On Wed, Jan 27, 2016 at 11:21 AM, Adam Jackson > wrote: >> > LLVM upstream is (eventually) dropping their autotools build system in >> > f

Re: [ACTION REQUIRED] [FINAL NOTICE] Retiring packages for F-18

On 07/31/2012 02:03 PM, Peter Robinson wrote: > On Tue, Jul 31, 2012 at 9:42 PM, Kevin Kofler wrote: >> Are those build.log files really so large that they cannot be kept for >> longer? :-( It's so annoying to see those build failures and to have no idea >> why the builds failed. > > There's 3 pe

Re: systemd requires HTTP server and serves QR codes

On 10/09/2012 05:19 PM, J. Randall Owens wrote: > Just on the naming, I'd rather steer clear of the actual concept, let me > get this straight: You want a group called "adm", presumably short for > "administrator", the point of which is that it can view system things, > but not actually *administer

Re: LVM thin provisioning and virt-manager

On 10/15/2013 02:46 PM, Richard W.M. Jones wrote: > On Tue, Oct 15, 2013 at 03:29:38PM -0600, Chris Murphy wrote: >> The better snapshots sound ideal for VM testing. Snapshot a >> successful install and then try to break the snapshot. Etc. >> >> Presently virt-manager ignores thinp pools and only c

Re: LVM thin provisioning and virt-manager

On 10/15/2013 05:15 PM, Chris Murphy wrote: > > On Oct 15, 2013, at 4:30 PM, Josh Stone wrote: > >> On 10/15/2013 02:46 PM, Richard W.M. Jones wrote: >>> On Tue, Oct 15, 2013 at 03:29:38PM -0600, Chris Murphy wrote: >>>> The better snapshots so

Re: F25 Self Contained Change: Rust Compiler

On 07/12/2016 11:45 PM, Dan Horák wrote: > How does the new language (and compiler) affect secondary architectures? > Will it just work? Rust has their own tier system of architecture support: https://doc.rust-lang.org/book/getting-started.html#platform-support Only i686 and x86_64 are Tier 1 at

Re: F25 Self Contained Change: Rust Compiler

On 07/13/2016 12:29 AM, Stefan Nuxoll wrote: > Rust supports dynamic linking, would it be worth investigating that > route instead of copying the proposed Go guidelines? I'm not against > static linking at all costs, but it would make package maintenance > (especially security updates) a lot more p

Re: F25 Self Contained Change: Rust Compiler

On 07/13/2016 02:24 AM, Dridi Boukelmoune wrote: > Since 1.10 (the target of this change) it has become possible to > create "cdylib" (C dynamic library) crates, basically shared objects > that can be linked to by non-Rust programs. > > It isn't supported by cargo yet, but it's available.. Yes, y

Re: F25 Self Contained Change: Rust Compiler

On 07/12/2016 09:18 PM, Jan Kurik wrote: > Rust 1.10.0 was released on July 7 along with Cargo 0.11.0. These will > be the initial targets to package. Rust's next release is scheduled > for August 18 on a 6-week cycle. Backwards compatibility is taken very > seriously, so it should be possible to k

Re: F25 Self Contained Change: Rust Compiler

On 07/13/2016 09:10 AM, Stefan Nuxoll wrote: > ABI stability is entirely dependent on compiler version, AFAIK. > Within the same version of rustc there should be no issues with > dynamic linking, I suspect that may true in general, but I don't think it's promised, and I don't really trust it. We

Re: F25 Self Contained Change: Rust Compiler

On 07/13/2016 07:50 AM, Adam Jackson wrote: > On Wed, 2016-07-13 at 07:26 +, Stefan Nuxoll wrote: >> Rust uses LLVM for codegen, so in theory, yes. This excludes any >> potential platform-specific bugs that may affect rustc, which are >> certainly a possibility. > > At the moment llvm has code

Re: F25 Self Contained Change: Rust Compiler

On 07/14/2016 05:15 PM, Simo Sorce wrote: > Until the Rust ecosystem becomes more stable, it is better to upgrade > it regularly than have a stale tool nobody can really use. > There are even crates that work only with nightlies for now, so trying > to stay on par is necessary to make it useful. Al

Re: comiing to koji aarch64

On 09/10/2016 07:19 AM, Dennis Gilmore wrote: > Hi All, > > We are in the process of importing aarch64 to the primary koji instance as > part of https://fedoraproject.org/wiki/Architectures/ > RedefiningSecondaryArchitectures The import and enablement of aarch64 is for > rawhide only, we expec

Re: OCaml 4.00.1 for Fedora 18

On 12/14/2012 07:34 AM, Kevin Kofler wrote: > Richard W.M. Jones wrote: >> It's my understanding that when the update goes out, the build >> overrides are automatically expired, which is why I selected a very >> long expiry. > > AIUI, that's actually not the case. But you can expire the stuff manu

Re: OCaml 4.00.1 for Fedora 18

On 12/14/2012 11:12 AM, Josh Stone wrote: > On 12/14/2012 07:34 AM, Kevin Kofler wrote: >> Richard W.M. Jones wrote: >>> It's my understanding that when the update goes out, the build >>> overrides are automatically expired, which is why I selected a very >

Re: fedup: does not verify source

On 12/17/2012 10:58 AM, Adam Williamson wrote: > When you do a yum distro-sync according to the instructions on the wiki, > you are supposed to manually import the GPG key for the next release. If > you're doing things Properly, you should somehow verify you're importing > the correct key and not j

Re: Installing glib2-devel.i686 alongside glib2-devel.x86_64 on Fedora?

On 12/27/2012 05:30 AM, Ilyes Gouta wrote: > Hi, > > I'm attempting to build a software requiring glib2-devel.i686, however > when attempting to yum install it, RPM generates a transaction error and > states that few files from glib2-devel.i686 conflict w/the x86_64 flavor. > > The listed conflic

Re: Status to make btsfs to the standard filesystem of Fedora

On 01/16/2013 01:16 PM, William Brown wrote: > If root isn't placed into a subvolume, say /root then mounted > as /dev/sda1 subvolid=255 / lets say, you can't snapshot the root fs, > which defeats the whole point of using btrfs . Yes you can -- the btrfs wiki even has this example: mount -

Re: Why do we have a kernel with version number - 20X?

On 01/22/2013 11:28 AM, Chris Murphy wrote: > 7xx, 8xx, 9xx, 0xx, > > The first number of a Fedora release seems mostly superfluous. 9xx->0xx breaks the goal "that updates will work better". -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/deve

OK to bump soname for a lesser-used library?

It's clear to me that library soname bumps should generally be avoided in released Fedoras, but can it be allowed for more fringe libraries? Specifically, I'd like to get Dyninst 8.1 into Fedora 18, which would bump everything from ".so.8.0" to ".so.8.1". The only in-distro package that BuildRequ

Re: OK to bump soname for a lesser-used library?

On 03/05/2013 07:59 AM, Adam Jackson wrote: > On Mon, 2013-03-04 at 14:07 -0800, Josh Stone wrote: > >> So given that this library's use is pretty well contained, might it be >> OK to go ahead and update in F18? > > Yeah, that's fine. > > In the future,

Re: Power consumption with Fedora

On 12/02/2014 12:05 PM, Chris Murphy wrote: > Question: Shouldn't the evaluation and fix be targeted at Rawhide > first, and then see about "backporting" demonstrated fixes to Fedora Beware of things like debug-enabled kernels though. Rawhide runs a bit slower for this, and more work means more p

Re: fedup speed

On 12/10/2014 11:18 AM, Zbigniew Jędrzejewski-Szmek wrote: > 2. at the end, fedup creates a log by running 'journalctl -a -m', >which is --all --merge. This seems a bit excessive. On this machine >I have 4.5 GB of logs from this machine, plus a few GB more from >other sources. journalct

Re: Results of a test mass rebuild of rawhide/x86_64 with gcc-5.0.0-0.5.fc22

On 02/10/2015 07:05 AM, Ralf Corsepius wrote: > Well, wouldn't you agree that developers should be able to read warnings > and filter out the serious one? If a project has more than a screen-full of "harmless" warnings, then it's very easy to miss when a serious one slips in. I prefer -Werror so

Re: F26 Self Contained Change: Anaconda LVM RAID

On 02/07/2017 12:27 PM, Samuel Sieb wrote: > On 01/31/2017 12:02 PM, Chris Murphy wrote: >> On Tue, Jan 31, 2017 at 7:33 AM, Chris Adams wrote: >>> How do LVM RAID volumes get tested? There's a regular cron job for >>> testing MD RAID volumes, but I'm not aware of something like that for >>> LVM

LLVM compatibility hazard on F24/F25

re https://bugzilla.redhat.com/show_bug.cgi?id=1422930 This is an indirect consequence of the LLVM update for bug 1376213. In the initial llvm-3.8.1-1 update, ajax enabled the Mips target, but this was never pushed out due to unrelated build issues. Then later I found I needed an LLVM update for

Re: Static libraries in Fedora distribution (Was: Re: [Help Wanted] PPC64LE build for thrift)

On 03/14/2017 05:05 PM, Jonathan Wakely wrote: > If glibc-static was removed from Fedora and that change propagated to > RHEL I know of companies that might stop being customers of Red Hat. Even if Fedora removed it, we could still make the business decision to add it back to RHEL. > Being unable

Re: Static libraries in Fedora distribution (Was: Re: [Help Wanted] PPC64LE build for thrift)

On 03/15/2017 10:08 AM, Daniel P. Berrange wrote: > On Wed, Mar 15, 2017 at 09:56:50AM -0700, Josh Stone wrote: >> On 03/14/2017 05:05 PM, Jonathan Wakely wrote: >>> If glibc-static was removed from Fedora and that change propagated to >>> RHEL I know of companies that

Re: Static libraries in Fedora distribution (Was: Re: [Help Wanted] PPC64LE build for thrift)

On 03/15/2017 05:32 PM, Tomasz Kłoczko wrote: > ./r/rust.git/rust.spec:BuildRequires: llvm-static This one is conditional, generally disabled. We use it to break rust's bootstrap dependency when llvm is being rebased to a new soname. ___ devel mailing

Re: Retiring Packages with Broken Dependencies in branched (2017-06-12)

On 06/12/2017 03:38 PM, t...@fedoraproject.org wrote: > lldb airlied, daveisfera, 71 weeks ago >jankratochvil, jvcelak, >siddharths, tstellar Where d

  1   2   >