Re: Orphaning scram

I can take package and upgrade it. ср, 14 февр. 2018 г. в 3:16, Olzhas Rakhimov : > Hi, > > I orphaned scram. > > My hard drive w/ Fedora died a while ago. > Lost all my packaging setup and never caught up w/ the new packaging > changes :( > > There's an open "upgrade-request" [bug 1544524] that

vdr-live build fails for rawhide

when building vdr-live for rawhide it fails [1] for ppc64le and ppc64 when adding "-Wsizeof-pointer-memaccess" to the build flags, then it fails [2] for s390x. %build make CFLAGS="%{optflags} -fPIC" CXXFLAGS="%{optflags} -fPIC -Wsizeof-pointer-memaccess" %{?_smp_mflags} all [1] https://koji.fed

Re: Mass Rebuild for Fedora 28

2018-02-13 0:06 GMT+01:00 Dennis Gilmore : > [3] https://kojipkgs.fedoraproject.org/mass-rebuild/f28-need-rebuild.html Among those are a lot of packages for which it seems the rebuild has not been tried at all, for whatever reason. Instead of asking every maintainer to go manually through his or h

CheckRequire: in spec?

I wonder, when there is a %check in spec, and the testsuite requires more packages than BuildRequires, is there a way to have them installed only if check is running? Or shall I just throw them in as BuildRequire`s? -- Martian ___ devel mailing list

Re: CheckRequire: in spec?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-02-14 at 09:39 +0100, Marian Csontos wrote: > I wonder, when there is a %check in spec, and the testsuite requires > more packages than BuildRequires, is there a way to have them installed > only if check is running? This has been bro

Re: Escaping macros in %changelog

Hi, Actually, the problem is we're all talking about changelogs, when users ask for release notes. That's not exactly the same thing. Regards, -- Nicolas Mailhot ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: CheckRequire: in spec?

%check run only on build stage so you can use just BuildRequire for it. ср, 14 февр. 2018 г. в 11:47, Marian Csontos : > I wonder, when there is a %check in spec, and the testsuite requires > more packages than BuildRequires, is there a way to have them installed > only if check is running? > > O

Re: Usefulness of `copr mock-config ` feature?

Hi, BTW, in my own very basic use of copr, I'm mostly annoyed with: 1. copr failing builds because of problems syncing repodata → not my problem as packager, retry till you manage to sync repositories and package groups 2. copr sometimes starting the next build, before finishing syncing the resu

Re: Usefulness of `copr mock-config ` feature?

On Tuesday, February 13, 2018 10:15:42 PM CET Michal Novotny wrote: > On Tue, Feb 13, 2018 at 9:51 PM, Michal Novotny wrote: > > > Hello, > > > > On Tue, Feb 13, 2018 at 12:54 PM, Michael Šimáček > > wrote: > > > >> On 2018-02-13 11:47, Pavel Raiskup wrote: > >> > >>> Sorry, I wanted to CC fedor

Re: Usefulness of `copr mock-config ` feature?

Hello Pavel, On Wed, Feb 14, 2018 at 10:18 AM, Pavel Raiskup wrote: > On Tuesday, February 13, 2018 10:15:42 PM CET Michal Novotny wrote: > > On Tue, Feb 13, 2018 at 9:51 PM, Michal Novotny > wrote: > > > > > Hello, > > > > > > On Tue, Feb 13, 2018 at 12:54 PM, Michael Šimáček > > > > wrote: >

Re: Usefulness of `copr mock-config ` feature?

On Wednesday, February 14, 2018 10:54:48 AM CET Michal Novotny wrote: > Hello Pavel, > > On Wed, Feb 14, 2018 at 10:18 AM, Pavel Raiskup wrote: > > > On Tuesday, February 13, 2018 10:15:42 PM CET Michal Novotny wrote: > > > On Tue, Feb 13, 2018 at 9:51 PM, Michal Novotny > > wrote: > > > > > >

rubygem-file-tail license change

rubygem-file-tail-1.2.0-1.fc28 changed license from: GPLv2 to: ASL 2.0 Vít ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Usefulness of `copr mock-config ` feature?

On Wed, Feb 14, 2018 at 11:16 AM, Pavel Raiskup wrote: > On Wednesday, February 14, 2018 10:54:48 AM CET Michal Novotny wrote: > > Hello Pavel, > > > > On Wed, Feb 14, 2018 at 10:18 AM, Pavel Raiskup > wrote: > > > > > On Tuesday, February 13, 2018 10:15:42 PM CET Michal Novotny wrote: > > > > O

Re: vdr-live build fails for rawhide

Martin Gansser wrote on 02/14/2018 05:19 PM: when building vdr-live for rawhide it fails [1] for ppc64le and ppc64 when adding "-Wsizeof-pointer-memaccess" to the build flags, then it fails [2] for s390x. %build make CFLAGS="%{optflags} -fPIC" CXXFLAGS="%{optflags} -fPIC -Wsizeof-pointer-memac

Call for users of darkserver

Good Morning Everyone, The week before DevConf, a number of the members of the Fedora Infrastructure met in Brno to discuss states and plans for the infrastructure. One of the question that raised was about darkserver. This application is available at: https://darkserver.fedoraproject.org/ and is

Re: Call for users of darkserver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-02-14 at 11:02 +0100, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > The week before DevConf, a number of the members of the Fedora Infrastructure > met in Brno to discuss states and plans for the infrastructure. > One of the qu

Re: vdr-live build fails for rawhide

Mamoru TASAKA wrote on 02/14/2018 08:21 PM: Martin Gansser wrote on 02/14/2018 05:19 PM: when building vdr-live for rawhide it fails [1] for ppc64le and ppc64 when adding "-Wsizeof-pointer-memaccess" to the build flags, then it fails [2] for s390x. %build make CFLAGS="%{optflags} -fPIC" CXXFLA

Re: vdr-live build fails for rawhide

> Mamoru TASAKA wrote on 02/14/2018 08:21 PM: > > And actually disabling parallel make seems to help this: > https://koji.fedoraproject.org/koji/taskinfo?taskID=25039927 > > Regards, > Mamoru Thanks for your help, disabling %{?_smp_mflags} works Regards Martin ___

Re: CheckRequire: in spec?

On 14 February 2018 at 08:56, Igor Gnatenko < ignatenkobr...@fedoraproject.org> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, 2018-02-14 at 09:39 +0100, Marian Csontos wrote: > > I wonder, when there is a %check in spec, and the testsuite requires > > more packages than Bu

Re: Mass Rebuild for Fedora 28

On 12 February 2018 at 23:06, Dennis Gilmore wrote: [..] > [1] https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild > kloczek (1):xml-security-c Looks like at the moment Fedora build infrastructure is using set of packages which is s

RPM Lint Errors

I have a package that includes a group of Ansible playbooks embedded into a Python module. The playbooks include a number of templates that are designed to be uploaded into remote systems, templated out with appropriate variables, and then executed on the remote system. Since the templates are des

Re: Escaping macros in %changelog

On Tue, 2018-02-13 at 15:33 -0500, Josh Boyer wrote: > > The point is, we have LOTS of places where change information or > discussion occurs. We should try and have a canonical location for > the *descriptive summary* of these changes/discussions. This hit home. Way back in the early 90s when

Re: Escaping macros in %changelog

On Tue, 2018-02-13 at 12:07 -0800, Adam Williamson wrote: > On Mon, 2018-02-12 at 11:59 -0500, David Cantrell wrote: > > The dist-git changelogs are mostly noise and I would prefer better > > organized information about impacts to users and developers. Like > > tell > > me what things changed in t

Re: CheckRequire: in spec?

Marian Csontos wrote: > I wonder, when there is a %check in spec, and the testsuite requires > more packages than BuildRequires, is there a way to have them installed > only if check is running? > > Or shall I just throw them in as BuildRequire`s? use BuildRequires If these extra deps could cau

Re: Call for users of darkserver

On Wed, Feb 14, 2018 at 12:41:36PM +0100, Igor Gnatenko wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, 2018-02-14 at 11:02 +0100, Pierre-Yves Chibon wrote: > > Good Morning Everyone, > > > > The week before DevConf, a number of the members of the Fedora > > Infrastructure

Re: inject rpm dependency depending on library symbol?

Kevin Kofler wrote: > Rex Dieter wrote: >> (I know this would be handled automatically if the Qt_5_PRIVATE_API >> symbol was versioned, but that's an option we'd rather avoid if >> reasonably possible) > > IMHO, the right approach is to do just that. There is already a patch that > does this: > h

Release notes vs. Changelogs [was Re: Escaping macros in %changelog]

On Wed, Feb 14, 2018 at 10:00:18AM +0100, nicolas.mail...@laposte.net wrote: > Actually, the problem is we're all talking about changelogs, when users ask > for release notes. > That's not exactly the same thing. Yes! Thanks, that puts nicely what I'm trying to say. Right now, the git log is basi

[HEADS UP] Package wireshark-gtk going away

Hi, the wireshark-gtk is no longer supported by the upstream since wireshark-2.4.0. You may have noticed that there is new GUI based on Qt since wireshark-2.0. This GUI will become default and the GTK-based GUI will be dropped and no longer provided. This change should appear in Fedora 29. -- Mi

Re: [HEADS UP] Package wireshark-gtk going away

On 14/02/18 15:28, Michal Ruprich wrote: the wireshark-gtk is no longer supported by the upstream since wireshark-2.4.0. You may have noticed that there is new GUI based on Qt since wireshark-2.0. This GUI will become default and the GTK-based GUI will be dropped and no longer provided. This cha

Re: [HEADS UP] Package wireshark-gtk going away

On 14/02/18 15:42, Tom Hughes wrote: As best I can figure you are trying to use alternatives to manage the /usr/sbin/wireshark command as a link to one or the other but alternatives is upset that nothing has created an initial value for that link or something. Actually apparently it's now in /

Re: [HEADS UP] Package wireshark-gtk going away

This is a well known bug for few people who updated from older Wireshark package to a new one while it was moved from sbin to bin. There is a scriptlet, that should take care of this. If it does not work, you can just fix it by hand. Remove the package, remove the alternatives and install it again.

Re: Removal of BuildRoot

No, that commit description was not helpful as it did not explain why you see a need to exert your proven packager privileges, nor the fact that this is a mass change. I had to go around and look for you and some info about your commit. Frankly, I hate it when I notice that someone is stepping o

Re: New "tests" namespace to share test code

Hi! During the last days there have been concerns raised regarding what is an appropriate content for the tests namespace. [1] My original idea was to enable sharing tests even across branches of the same component, not only for tests to be used by completely different packages. The initial exampl

Re: Removal of BuildRoot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-02-14 at 16:17 +, Michael J Gruber wrote: > No, that commit description was not helpful as it did not explain why you see > a need to exert your proven packager privileges, nor the fact that this is a > mass change. I had to go aroun

[Guidelines change] Changes to the packaging guidelines

Just this one change, but it has implications for many packages. The Scriptlet guidelines have received several changes regarding the installation of shared libraries and ldconfig. Use of the new macros is detailed, and there is a new section on the scriptlets required when linker configuration f

Re: Removal of BuildRoot

Le 13/02/2018 à 23:05, Igor Gnatenko a écrit : > Just a small heads up, ... As I said on IRC - waste of time - waste of energy - absolutely no value And - abuse proven packager privileges Remi ___ devel mailing list -- devel@lists.fedoraproject.org

Re: New "tests" namespace to share test code

On 02/14/2018 05:28 PM, Petr Šplíchal wrote: Hi! During the last days there have been concerns raised regarding what is an appropriate content for the tests namespace. [1] My original idea was to enable sharing tests even across branches of the same component, not only for tests to be used by co

Re: RANT: Packaging is changing too fast and is not well documented

On Mon, Feb 12, 2018 at 10:37:38AM -0800, Kevin Fenzi wrote: > On 02/12/2018 10:14 AM, Ken Dreyer wrote: > > On Sat, Feb 10, 2018 at 6:48 AM, Richard Shaw wrote: > >> Not coming from a programming background I found the learning curve pretty > >> steep when I first tried to become a packager, I'm

Re: HEADS UP: yaml-cpp 0.6.0 coming to rawhide

On Sun, Feb 11, 2018 at 1:24 PM, Richard Shaw wrote: > I may wait a few days for all the build problems with gcc 8 and there are > still several packages that haven't been properly rebuilt against boost > 1.66, but I plan to build yaml-cpp 0.6.0 and rebuild its dependencies in > the near future:

Re: Removal of BuildRoot

IMO, bikesheding and stylishness with any actual usefulness. If you really want to enforce this, make it a feature request for f30 and have FESCO vote on it. Ralf ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to

Re: Call for users of darkserver

On Wed, 14 Feb 2018 15:55:20 +0100, Pierre-Yves Chibon wrote: > darkserver itself doesn't store anything. Darkserver was at least in the past using debuginfo storage from ABRT server which is much more rich than what Koji server keeps. Jan ___ devel ma

Re: Removal of BuildRoot

Hi, Thank you for cleaning up the cruft in the repository ! Regards, -- Nicolas Mailhot ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Call for users of darkserver

On Wed, 14 Feb 2018 11:02:52 +0100, Pierre-Yves Chibon wrote: > If there is little interest for this project, we will likely decommission it > in > the coming weeks (say end of March). The darkserver project ws initiated AFAIK by me as there is always a problem how to reproduce an ABRT bugreport.

Re: New "tests" namespace to share test code

On Wed, 2018-02-14 at 17:28 +0100, Petr Šplíchal wrote: > Hi! > > During the last days there have been concerns raised regarding > what is an appropriate content for the tests namespace. [1] My > original idea was to enable sharing tests even across branches of > the same component, not only for t

Re: Removal of BuildRoot

On 02/13/2018 02:05 PM, Igor Gnatenko wrote: > Just a small heads up, BuildRoot tag is not needed since RHEL6 (which is > oldest > supported one nowadays, it's been year or so after EL5 retirement). And we > don't support EL5 anymore, so... > > I wanted to send this heads up before I actually did

Re: clang -mcet -fcf-protection

On 02/13/2018 02:18 AM, Richard W.M. Jones wrote: > > My build of american-fuzzy-lop fails because clang doesn't > understand the ‘-mcet -fcf-protection’ flags which seem to be > added by RPM. > Is there a particular reason this packages uses clang and not gcc? -Tom > clang -O2 -g -pipe -Wal

Re: Removal of BuildRoot

nicolas.mail...@laposte.net wrote: > Hi, > > Thank you for cleaning up the cruft in the repository ! > > Regards, > Agreed. I'm usually pretty anal about others touching packages I maintain without at least a heads-up but in this case it doesn't bother me. I guess particularly since he didn't s

Re: clang -mcet -fcf-protection

On Wed, Feb 14, 2018 at 11:03:28AM -0800, Tom Stellard wrote: > On 02/13/2018 02:18 AM, Richard W.M. Jones wrote: > > > > My build of american-fuzzy-lop fails because clang doesn't > > understand the ‘-mcet -fcf-protection’ flags which seem to be > > added by RPM. > > > > Is there a particular r

Re: Removal of BuildRoot

On 02/14/2018 11:44 AM, Remi Collet wrote: > Le 13/02/2018 à 23:05, Igor Gnatenko a écrit : >> Just a small heads up, ... > > > As I said on IRC > > - waste of time > - waste of energy > - absolutely no value > > And > > - abuse proven packager privileges +1 -- David Cantrell Red Hat, Inc.

Re: Removal of BuildRoot

On Tue, Feb 13, 2018 at 11:05:28PM +0100, Igor Gnatenko wrote: > Just a small heads up, BuildRoot tag is not needed since RHEL6 (which is > oldest > supported one nowadays, it's been year or so after EL5 retirement). And we > don't support EL5 anymore, so... > > I wanted to send this heads up bef

Re: Removal of BuildRoot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-02-14 at 14:25 -0500, David Cantrell wrote: > On 02/14/2018 11:44 AM, Remi Collet wrote: > > Le 13/02/2018 à 23:05, Igor Gnatenko a écrit : > > > Just a small heads up, ... > > > > > > As I said on IRC > > > > - waste of time > > - wa

Re: Call for users of darkserver

I was unaware of it, but I think it looks pretty great! OOC, is there an alternative service that one could use if this is decommissioned? Or would we have to dig through Koji and Bodhi logs? I'll bet the CHAOSS folks [0] would like it, if that helps. Dunno if they're aware of it, though. I'll in

Re: Removal of BuildRoot

On 02/13/2018 03:05 PM, Igor Gnatenko wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Just a small heads up, BuildRoot tag is not needed since RHEL6 (which is oldest supported one nowadays, it's been year or so after EL5 retirement). And we don't support EL5 anymore, so... I wanted to se

Re: [HEADS UP] Replacing %post/%postun -p /sbin/ldconfig

On Wed, Feb 14, 2018 at 09:59:27PM +0100, Igor Gnatenko wrote: > The whole purpose of this is to make installation of packages FASTER and > obviously to comply with guidelines. Most of packages would be possible to > automate, however some would not and you would need to deal with it youself. I'd

Re: Removal of BuildRoot

On 02/14/2018 02:41 PM, Igor Gnatenko wrote: > On Wed, 2018-02-14 at 14:25 -0500, David Cantrell wrote: >> On 02/14/2018 11:44 AM, Remi Collet wrote: >>> Le 13/02/2018 à 23:05, Igor Gnatenko a écrit : Just a small heads up, ... >>> >>> >>> As I said on IRC >>> >>> - waste of time >>> - waste o

Re: HEADS UP: yaml-cpp 0.6.0 coming to rawhide

On Sun, Feb 11, 2018 at 1:24 PM, Richard Shaw wrote: > mongodb-3.6.2-1.fc28.src.rpm > Looks like arch dependent failures for ppc64le and s390x. I don't know if they are yaml-cpp related or not. http://koji.fedoraproject.org/koji/buildinfo?buildID=1044717 Thanks, Richard ___

Re: clang -mcet -fcf-protection

On Tue, Feb 13, 2018 at 02:27:02PM +0100, Florian Weimer wrote: > On 02/13/2018 11:36 AM, Daniel P. Berrangé wrote: > >redhat-rpm-config flags have usually been compatible with both gcc and > >clang, so if there's no newer clang that supports this, it feels like > >we've a few options > > > > 1. H

Re: Release notes vs. Changelogs

Matthew Miller wrote: > 1. Put real changelog info in the git log and have a separate standard >fedora-package-release-notes.md (uh, or better name, but I bet that >one doesn't have any conflicts!) which lives in dist-git (but not in >the package) and gets fed into bodhi and whatever ot

Schedule for Friday's FESCo Meeting (2018-02-16)

Following is the list of topics that will be discussed in the FESCo meeting Friday at 15:00UTC in #fedora-meeting on irc.freenode.net. Note that this is a change in time from the previous FESCo meeting time. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowt

Non-responsive maintainer: Lubomir Rintel (lkundrak)

Hi Does anyone know how to contact Lubomir Rintel (lkundrak)? He is obviously still active since his last koji build is as recent as last Sunday the 11th, but he isn't answering to this ticket [1] and I also had no luck e-mailing him directly. Thanks Sandro [1] https://bugzilla.redhat.com/

Re: [HEADS UP] Replacing %post/%postun -p /sbin/ldconfig

On Wed, Feb 14, 2018 at 4:14 PM, Matthew Miller wrote: > I'd be super-interested in benchmarks comparing before and after > install times. I guess since the plan is to do this _after_ the mass > rebuild, we'll need to wait until after the *next* rebuild to see how > much impact this has. I don't

Re: Fwd: Re: Fedora27: NFS v4 terrible write performance, is async working

On Mon, Feb 05, 2018 at 06:06:29PM -0500, J. Bruce Fields wrote: > Or this?: > > > https://www.newegg.com/Product/Product.aspx?Item=N82E16820156153&cm_re=ssd_power_loss_protection-_-20-156-153-_-Product Ugh, Anandtech explains that their marketing is misleading, that drive can't actually d

Re: Removal of BuildRoot

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2018-02-14 at 14:06 -0500, Rob Crittenden wrote: > nicolas.mail...@laposte.net wrote: > > Hi, > > > > Thank you for cleaning up the cruft in the repository ! > > > > Regards, > > > > Agreed. I'm usually pretty anal about others touching p

Re: Removal of BuildRoot

Le 15/02/2018 à 07:47, Igor Gnatenko a écrit : > On Wed, 2018-02-14 at 14:06 -0500, Rob Crittenden wrote: >> nicolas.mail...@laposte.net wrote: >>> Hi, >>> >>> Thank you for cleaning up the cruft in the repository ! >>> >>> Regards, >>> > >> Agreed. I'm usually pretty anal about others touching pa

GCC 8: camotics fails to build for i686, ARMv7 arches (reading 31 bytes from a region of size 16)

Hello, Need help figuring this out since I have no idea what this means. The cbang code that is included in camotics fails to build with the following messages. It is failing only for i686 and armv7hl architectures. g++ -o build/cbang/log/Logger.o -c -std=c++11 -ggdb -Wall -Werror -I/usr/inclu

Re: Removal of BuildRoot

Dne 15.2.2018 v 07:55 Remi Collet napsal(a): > Le 15/02/2018 à 07:47, Igor Gnatenko a écrit : >> On Wed, 2018-02-14 at 14:06 -0500, Rob Crittenden wrote: >>> nicolas.mail...@laposte.net wrote: Hi, Thank you for cleaning up the cruft in the repository ! Regards, >>> A

Re: [HEADS UP] Replacing %post/%postun -p /sbin/ldconfig

Dne 14.2.2018 v 21:59 Igor Gnatenko napsal(a): > > * Speak up and tell package names I should not touch because … (you should > complete this sentence). > * Fix up packages and tell package names I should not touch because > you did > that already. > * Tell package names you want to remove ldconf

Re: clang -mcet -fcf-protection

On 02/14/2018 08:22 PM, Richard W.M. Jones wrote: It uses both. In this case it uses clang because it has to build a clang extension (as well as a gcc extension). Isn't Clang compiled with GCC, too? (At least in the past, we didn't bootstrap it.) Why is Clang required to build the extension

Granularity in disable mangling shebangs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Since redhat-rpm-config-97-1.fc28 you can use 2 new variables: * `__brp_mangle_shebangs_exclude_from` to exclude specific paths from mangling. * `__brp_mangle_shebangs_exclude` to exclude specific shebangs from mangling. Those are using same syntax