F28: Mismatch between the program and library build versions detected, gcc-c++, wxGTK3

Hello, a recent F28 update build of poedit [1] shows the following message after starting: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1012,wx containers,compatible with 2.8), and your program used 3.0 (wchar_t,co

[Guidelines change] Changes to the packaging guidelines

Here are the recent changes to the packaging guidelines. - The packaging guidelines for enabling services by default were significantly revised to emphasize that services starting by default should fail only in exceptional conditions, and to provide additional guidance for services related t

Re: Unannounced soname bump (Rawhide): net-snmp (libnetsnmp.so.30 -> libnetsnmp.so.35)

On Tue, 2018-07-24 at 13:49 -0700, Adam Williamson wrote: > net-snmp was updated from 5.7.3-41 to 5.8-1 in Rawhide on 2018-07-20. > This update bumped the soname of libnetsnmp (in the net-snmp-libs > subpackage) from libnetsnmp.so.30 to libnetsnmp.so.35. > This soname bump was not announced, as it

Re: Intent to retire denyhosts

> "CA" == Chris Adams writes: CA> Just as an FYI: I'm not sure fail2ban supports that out of the box, CA> but it is easy enough to: True, but denyhosts has the concept of a central synchronization server which can be shared by all installations globally. The original incarnation (by the ori

Re: Unannounced soname bump: libconfig

Fabio Valentini wrote: > On Tue, Jul 24, 2018 at 9:06 PM Rex Dieter wrote: >> >> Richard W.M. Jones wrote: >> >> > >> > This build: >> > >> > https://koji.fedoraproject.org/koji/buildinfo?buildID=1130189 >> > >> > changed the soname from libconfig.so.9 to libconfig.so.11 thus >> > breaking a nu

/results_* and /*.rpm in .gitignore (was: Source tarballs are being placed in git?)

Todd Zullinger wrote: > […] > For example, the rpmlint's .gitignore contains the > following¹: > /*.rpm > /results_rpmlint/ > /rpmlint-*/ > /rpmlint-*.tar.gz > […] Apropos: Many .gitignores only reference the source files, i. e. not /results_${name} or /${name}-*.rpm. Therefore I usually add

Unannounced soname bump (Rawhide): net-snmp (libnetsnmp.so.30 -> libnetsnmp.so.35)

net-snmp was updated from 5.7.3-41 to 5.8-1 in Rawhide on 2018-07-20. This update bumped the soname of libnetsnmp (in the net-snmp-libs subpackage) from libnetsnmp.so.30 to libnetsnmp.so.35. This soname bump was not announced, as it is supposed to be. This library has many dependencies, and from a

Re: Intent to retire denyhosts

Once upon a time, Jason L Tibbitts III said: > In general, fail2ban is simply a far better choice. The primary feature > it appears to lack is the ability to synchronize lists of blocked hosts > between machines. (And I could be quite wrong about that.) Just as an FYI: I'm not sure fail2ban sup

Intent to retire denyhosts

Denyhosts is a daemon which watches for failed ssh login attempts and blocks them. I have long maintained denyhosts in Fedora and while I did not originally agree with it being branched to EPEL, I have done light maintenance on EPEL7 as well. The EPEL6 branch is, however, very old. The upstream

Re: Source tarballs are being placed in git?

On Tue, Jul 24, 2018 at 10:07 AM, Artur Iwicki wrote: > That section of the guide is a bit poorly worded. You should *not* use > "git add" on source tarballs. These should be added only via means of > "fedpkg new-sources $FILES; git add ./sources". I believe what the guide > means under "new sour

Re: Unannounced soname bump: libconfig

On Tue, Jul 24, 2018 at 9:06 PM Rex Dieter wrote: > > Richard W.M. Jones wrote: > > > > > This build: > > > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1130189 > > > > changed the soname from libconfig.so.9 to libconfig.so.11 thus > > breaking a number of packages. > > Hopefully this

Re: Source tarballs are being placed in git?

Daniel P. Berrangé wrote: > On Tue, Jul 24, 2018 at 01:32:45PM -0400, Todd Zullinger wrote: >> Artur Iwicki wrote: >>> That section of the guide is a bit poorly worded. You should *not* use "git >>> add" on source tarballs. These should be added only via means of "fedpkg >>> new-sources $FILES; g

Re: Unannounced soname bump: libconfig

Richard W.M. Jones wrote: > > This build: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1130189 > > changed the soname from libconfig.so.9 to libconfig.so.11 thus > breaking a number of packages. Hopefully this will help for posterity, https://src.fedoraproject.org/rpms/libconfig

Re: Source tarballs are being placed in git?

On Tue, Jul 24, 2018 at 07:06:49PM +0100, Daniel P. Berrangé wrote: > On Tue, Jul 24, 2018 at 01:32:45PM -0400, Todd Zullinger wrote: > > Artur Iwicki wrote: > > > That section of the guide is a bit poorly worded. You should *not* use > > > "git add" on source tarballs. These should be added only

Re: Intel's Clear Linux optimizations

On Mon, Jul 23, 2018 at 11:56 PM, Samuel Sieb wrote: > On 07/23/2018 10:04 PM, Chris Murphy wrote: >> >> Available Packages >> kernel.src4.18.0-0.rc0.git10.1.fc28 >> pac23-High_Performance_Clear_LInux_kernel_for_Fedora > > > This is what I get: > > # dnf list --all kernel > Installed Packa

Re: Source tarballs are being placed in git?

On Tue, Jul 24, 2018 at 01:32:45PM -0400, Todd Zullinger wrote: > Artur Iwicki wrote: > > That section of the guide is a bit poorly worded. You should *not* use "git > > add" on source tarballs. These should be added only via means of "fedpkg > > new-sources $FILES; git add ./sources". I believe

Re: Source tarballs are being placed in git?

On Tue, Jul 24, 2018 at 05:07:50PM -, Artur Iwicki wrote: > That section of the guide is a bit poorly worded. You should *not* > use "git add" on source tarballs. These should be added only via > means of "fedpkg new-sources $FILES; git add ./sources". Actually "fedpkg new-sources" already doe

Re: [HEADS UP] gcc/gcc-c++ removal from buildroot and more

On 07/23/2018 01:47 AM, Vít Ondruch wrote: > > The question is not about Fedora comps, but about comps from the Koji > repository: > > https://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/ > > specifically: > > https://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/repodata/d

Re: Source tarballs are being placed in git?

Artur Iwicki wrote: > That section of the guide is a bit poorly worded. You should *not* use "git > add" on source tarballs. These should be added only via means of "fedpkg > new-sources $FILES; git add ./sources". I believe what the guide means under > "new source files" is e.g. when upstream d

Fedora testing-20180724.0 compose check report

No missing expected images. Passed openQA tests: 2/2 (x86_64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedorap

Fedora updates-20180724.0 compose check report

No missing expected images. Passed openQA tests: 2/2 (x86_64) Installed system changes in test x86_64 AtomicHost-dvd_ostree-iso install_default: Filesystem for mount /sysroot changed from /dev/mapper/fedora--atomic_ibm--p8--kvm--03--guest--02-root to /dev/mapper/fedora_ibm--p8--kvm--03--g

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 28.20180722.0

On Tue, Jul 24, 2018 at 9:42 PM, wrote: > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 28.20180722.0 > Commit(x86_64): 106a7095fd46741948ba60dbd05866 > 68ae7abe6336671444ec790d7541a88778 > Commit(aarch64): e4cb87910b0729293453004293c1aa > c3d676b8683f4147a6fb3

Re: Source tarballs are being placed in git?

That section of the guide is a bit poorly worded. You should *not* use "git add" on source tarballs. These should be added only via means of "fedpkg new-sources $FILES; git add ./sources". I believe what the guide means under "new source files" is e.g. when upstream does not provide an icon or a

Source tarballs are being placed in git?

I received an email this AM from a fellow packager: *Please, do not put source tarballs in git. This is not what is supposed to happen. Package sources are managed with fedpkg, they are just added to the lookaside cache and to the .gitignore file so you don't add them by mistake to the reposito

Fedora Atomic Host Two Week Release Announcement: 28.20180722.0

A new Fedora Atomic Host update is available via an OSTree update: Version: 28.20180722.0 Commit(x86_64): 106a7095fd46741948ba60dbd0586668ae7abe6336671444ec790d7541a88778 Commit(aarch64): e4cb87910b0729293453004293c1aac3d676b8683f4147a6fb3975092b53810f Commit(ppc64le): 8f316b541744eafb126c06128

Re: dnf history - change in how rpmdb checksum is computed

This thread was about compatibility between dnf and yum: rpm itself has no usage case identifying whether an rpmdb has been changed. But you are correct that installation of a package by any tool -- including dnf and rpm atm -- needlessly causes yum to warn that the rpmdb has changed which is r

Unannounced soname bump: libconfig

This build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1130189 changed the soname from libconfig.so.9 to libconfig.so.11 thus breaking a number of packages. I can't find any announcement. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read

Correcting licenses in several packages I maintain

Hi, I reviewed licenses in files for my packages, so I added several corrections of license tags: cups: - from GPLv2 - to GPLv2+ and LGPLv2+ with exceptions and AML cups-filters: - from GPLv2 and GPLv2+ and GPLv3 and GPLv3+ and LGPLv2+ and MIT - to GPLv2 and GPLv2+ and GPLv3 and GPLv3+ and L

Re: build failed on s390x, other archs building okay

On Tue, 24 Jul 2018 10:12:22 -0400 "Kaleb S. KEITHLEY" wrote: > Is this a spurious failure or ??? looks like an infrastructure problem with build<->hub communication Dan > ... > Task info: > https://koji.fedoraproject.org/koji/taskinfo?taskID=28564187 ... > buildArch (gluster

build failed on s390x, other archs building okay

Is this a spurious failure or ??? ... Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=28564187 ... buildArch (glusterfs-4.1.2-1.fc29.1.src.rpm, s390x): free -> FAILED: Fault: thanks, -- Kaleb ___ devel mailing list -- devel@lists.fedo

Re: RFC: Pass --auto-features=enabled in meson

On Tue, Jul 24, 2018 at 3:43 PM Stephen Gallagher wrote: > On Mon, Jul 23, 2018 at 10:28 PM wrote: > >> On Mon, Jul 23, 2018 at 8:27 PM, Josh Boyer >> wrote: >> > My biggest objection here is that it blindly enables things, which >> > continues to make our package set a web of inter-dependencie

Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

On 06/29/2018 08:42 AM, Stephen Gallagher wrote: > > > On Fri, Jun 29, 2018 at 8:32 AM Daniel Walsh > wrote: > > Users of OpenSHift Origin require CRI-O 1.10 right now.  But Kubernetes > users want to try out the latest packages for kubernetes 1.11 which >

Re: RFC: Pass --auto-features=enabled in meson

On Mon, Jul 23, 2018 at 10:28 PM wrote: > On Mon, Jul 23, 2018 at 8:27 PM, Josh Boyer > wrote: > > My biggest objection here is that it blindly enables things, which > > continues to make our package set a web of inter-dependencies and > > makes any attempts at minimization harder. I don't thin

sharutils license corrected

I corrected sharutils' license tag from: GPLv3+ and (LGPLv3+ or BSD) and LGPLv2+ and Public Domain and GFDL to: GPLv3+ and (GPLv3+ and BSD) and (LGPLv3+ or BSD) and LGPLv2+ and Public Domain and GFDL -- Petr ___ devel mailing list -- devel@lists.fedo

Re: Haskell failures: relocation refers to local symbol "" [1], which is defined in a discarded section

On 24.7.2018 11:53, Nick Clifton wrote: Hi Florian, Linking dist/build/tests-asn1-encoding/tests-asn1-encoding ... /tmp/ghc8eea_0/ghc_2.o(.gnu.build.attributes..text.startup+0x18): error: relocation refers to local symbol "" [11], which is defined in a discarded section    section group signa

Re: Haskell failures: relocation refers to local symbol "" [1], which is defined in a discarded section

Hi Florian, >> Linking dist/build/tests-asn1-encoding/tests-asn1-encoding ... >> /tmp/ghc8eea_0/ghc_2.o(.gnu.build.attributes..text.startup+0x18): error: >> relocation refers to local symbol "" [11], which is defined in a discarded >> section >>    section group signature: "(null)" This should

Re: Intel's Clear Linux optimizations

> It's just a little tricky > installing packages that have the same name, but lower > version numbers than what is in the main Fedora repos. I will update the documentation,thanks. On Tue, 24 Jul 2018, 13:56 Samuel Sieb, wrote: > On 07/23/2018 11:53 PM, Manas Mangaonkar wrote: > > This was m

sisu license correction

sisu license tag has been corrected from: EPL-1.0 to: EPL-1.0 and BSD because of bundled objectweb-asm Michael ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Con

Re: dnf history - change in how rpmdb checksum is computed

I would like to see dnf history not being messed up by direct installations with `rpm -i`. While `dnf history` is a great feature, it would be even greater if the related functionality was implemented directly in rpmdb and both rpm and dnf used that db. Meaning that any consistency checks would be

Re: Intel's Clear Linux optimizations

On 07/23/2018 11:53 PM, Manas Mangaonkar wrote: This was my first repo/package sorry if i messed up somewhere. I don't personally have any interest in this package, but I don't see anything wrong with how it's setup. It's just a little tricky installing packages that have the same name, but

Re: Fedora 29 Self-Contained Change: xfce 4.1

On Mon, Jul 23, 2018 at 09:51:21PM -0400, Ben Cotton wrote: > == Summary == > Xfce desktop environment has utilized GTK-2 up until version 4.12.x > which is currently available in Fedora. Significant work has been > completed to migrate the DE to GTK-3 completely. The obvious benefit > to this mig

Re: RFC: Pass --auto-features=enabled in meson

On Tue, Jul 24, 2018 at 4:23 AM Josh Boyer wrote: > On Mon, Jul 23, 2018 at 6:40 PM Igor Gnatenko > wrote: > > > > Hello, > > > > meson 0.47.0 has new option type - feature (tri-state option - > enabled/disabled/auto). It is quite common that in autofoo and less in > cmake worlds people rely on