Re: Test gate failures

On 03/06/2018 02:26 AM, Kamil Paral wrote: We reported invalid multilib results, so I disabled multilib checking by simply not downloading any i386 packages. However, it didn't occur to me that that will break x86_64 packages that have a hard requirement on i386 packages, like wine does. I'll

Re: Frequently broken Rawhide/Branched composes

On 03/03/2018 01:34 PM, Kevin Kofler wrote: > That is due to the "Rawhide can never go backwards" policy, which I still do > not understand the point of, especially in the light of "distro-sync" having > been supported by both the old yum and the new dnf for years. Sometimes an updated package

Re: Frequently broken Rawhide/Branched composes

Kevin Fenzi wrote: > Do note that distro-sync can downgrade packages, but can't handle all > the cases. ie, upgrade postgresql and update all your data you can't > just downgrade the rpm and be fine. Or any number of other scriptlets > that do things that cannot easily be reversed. The Epoch hack

Re: Frequently broken Rawhide/Branched composes

Randy Barlow wrote: > On 03/03/2018 01:34 PM, Kevin Kofler wrote: >> That is due to the "Rawhide can never go backwards" policy, which I still >> do not understand the point of, especially in the light of "distro-sync" >> having been supported by both the old yum and the new dnf for years. > >

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Il 06/03/2018 18:17, Germano Massullo ha scritto: > Thank you Dennis. Therefore I think that rpmlint messages should be > improved about noarch packages. > I started working on %{_lib} / %{_libdir} on firefox-pkcs11-loader spec > file because originally there were %files entries like >

Re: Critpath karma

On 03/06/2018 10:30 AM, Dennis Gilmore wrote: > In the past we required a proven tester to sign off on testing a > critpath package to provide extra assurance that the update worked and > did not break critical functionality. I do not believe that we are > using proven testers any longer. Having

Re: Critpath karma

I've filed https://github.com/fedora-infra/bodhi/issues/2194 about considering removing this feature from Bodhi. I listed an example there where I thought the feature was actively harmful in a particular case, due to users not knowing that the field doesn't actually count for anything.

Re: Frequently broken Rawhide/Branched composes

On 03/06/2018 07:47 AM, Pierre-Yves Chibon wrote: > On Tue, Mar 06, 2018 at 02:58:45PM +, Stephen Gallagher wrote: ...snip... >> But that has its own issues. > > Sorry, just to be clear, what would have its own issues: > - asking rawhide users to use distro-sync instead of update? > -

Re: Critpath karma

On 03/06/2018 08:53 AM, Peter Robinson wrote: > Critical path were (are) packages that were in blocking deliverables, > it pre-dates the Editions, basically if it was a core blocking package > eg part of Workstaiton, it needed to get more testing/karma before it > could go stable, adamw probably

Re: Frequently broken Rawhide/Branched composes

Nicolas Mailhot wrote: > The “never go backwards” policy means that as soon something hits devel > other packages can rely on your package and start adapting > their packages on the basis of your changes. You can not pull the carpet > from under their feet just because you changed your mind. This

Unannounced soname bump (Rawhide): brotli (libbrotli{common,enc,dec}.so.1.0.1 -> libbrotli{common,enc,dec}.so.1)

brotli was updated from 1.0.1-3 to 1.0.3-1 in Rawhide on 2018-03-03. This update bumped the sonames from libbrotli{common,enc,dec}.so.1.0.1 to libbrotli{common,enc,dec}.so.1 (not a typo, that's really the change). This soname bump was not announced, as it is supposed to be. httpd (Apache) and

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Germano Massullo wrote: > # in noarch builds, %%{_libdir} is not defined in cmake, so the default > # installation would try installing for example > # file onepinopenscpkcs11.json > # into /usr/lib/mozilla/pkcs11-modules/onepinopenscpkcs11.json > # even if the system architecture is 64bit. This

Re: Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze

Stephen Gallagher wrote: > Intuitively, I completely agree with you. I want to have a last warning > that I need to hurry up and land my changes before I miss my window. > > But when I think about it further, I have other thoughts too. The schedule > is public and anyone can look it up at will,

Re: Frequently broken Rawhide/Branched composes

On Fri, 2018-03-02 at 04:40 +0100, Kevin Kofler wrote: > > > I disagree entirely with the above. I think the solution is to gate > > packages coming into rawhide and hold or reject those that break the > > compose until they are fixed. I think being proactive is VASTLY better > > than being

Re: Unannounced soname bump (Rawhide): brotli (libbrotli{common,enc,dec}.so.1.0.1 -> libbrotli{common,enc,dec}.so.1)

On Tue, 06 Mar 2018 14:46:46 -0800 Adam Williamson wrote: > brotli was updated from 1.0.1-3 to 1.0.3-1 in Rawhide on 2018-03-03. > This update bumped the sonames from libbrotli{common,enc,dec}.so.1.0.1 > to libbrotli{common,enc,dec}.so.1 (not a typo, that's really the

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Thank you Björn you clarified all my remaining doubts! I will remove "BuildArch: noarch" because in my opinion is the best solution. Then I will resume the %{_libdir} macros ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Re: Critpath karma

On Tue, 2018-03-06 at 08:48 -0500, Randy Barlow wrote: > Greetings! > > Does anybody here know the history and/or purpose behind Bodhi's > critical path karma? A brief grepping of Bodhi's codebase makes me think > it isn't really used by Bodhi for any purpose other than recording and > displaying

Re: Unannounced soname bump (Rawhide): brotli (libbrotli{common,enc,dec}.so.1.0.1 -> libbrotli{common,enc,dec}.so.1)

I see in the file list: %{_libdir}/*.so.* I've lost count of how many problems we've had from unannounced soname bumps recently. It's going to keep happening so long as our packaging guidelines continue to allow this construction. Anyway, the only thing better than one soname bump is a

Re: Please test f28-backgrounds package

On Mon, 2018-03-05 at 21:58 -0800, Luya Tshimbalanga wrote: > f28-backgrounds just got packaged and ready for beta release. Please > test and give positive if everything works as intended. > >

grubby - /boot on btrfs support

https://bodhi.fedoraproject.org/updates/grubby-8.40-10.fc28 We've built grubby with support for /boot on btrfs. We're trying to land this in F28. But we need testers. That's where you come in! If you ever interact with grubby and especially if you have an exotic grub2 setup, please download and

Re: Unannounced soname bump (Rawhide): brotli (libbrotli{common,enc,dec}.so.1.0.1 -> libbrotli{common,enc,dec}.so.1)

mcatanz...@gnome.org wrote: > Anyway, the only thing better than one soname bump is a second one, so: > https://github.com/google/brotli/pull/645 That change is just wrong: https://github.com/google/brotli/pull/645#issuecomment-371011990 Kevin Kofler

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

On Tue, Mar 6, 2018 at 7:08 AM, Jan Rybar wrote: > done: procps-ng, psmisc, psacct > > > On 02/18/2018 06:09 PM, Igor Gnatenko wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA256 >> >> Over this weekend I've performed scratch-mass-rebuild without having gcc >> and

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Il 06/03/2018 17:42, Dennis Gilmore ha scritto: > El mar, 06-03-2018 a las 17:20 +0100, Germano Massullo escribió: >> Il 06/03/2018 16:35, Dennis Gilmore ha scritto: >>> El mar, 06-03-2018 a las 15:29 +0100, Germano Massullo escribió: During package firefox-pkcs11-loader build, the following

[ACTION NEEDED #2] Missing BuildRequires: gcc/gcc-c++

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This is the second iteration of my mass-scratch-rebuild without gcc/gcc-c++ in the buildroot[0]. Everything what was written in original mail still applies. Since people might have fixed their packages after I started rebuild, I decided to include

Re: Frequently broken Rawhide/Branched composes

On Sat, Mar 03, 2018 at 07:35:00PM +0100, Kevin Kofler wrote: > Kevin Fenzi wrote: > > with using Epoch's much more commonly. > > That is due to the "Rawhide can never go backwards" policy, which I still do > not understand the point of, especially in the light of "distro-sync" having > been

[HEADS UP] Changes in wireshark package name

Hi, the plan to drop the GTK+ GUI [1] was approved by FESCO, so I will be dropping the wireshark-gtk package in rawhide(currently F29). Also I would like to propose that we change the name of wireshark-qt. There are three packages now - wireshark-cli, wireshark-gtk and wireshark-qt. Since the

Fedora 28 screen freezing with AMD OLAND

Using Fedora 28 in my system(i7-3612qm/AMD HD8750M(OLAND)/4.16/GNOME 3.28/Wayland) ,almost when i try to navigate between apps, screen freezes for a bit and then unfreezes. No problem appears in ABRT nor SELinux alert. Only in the dmesg , a error in radeon driver appears: radeon :01:00.0:

Re: -z defs linker flag activated in Fedora rawhide

On 03/05/2018 05:55 PM, Sérgio Basto wrote: On Mon, 2018-01-22 at 16:24 +0100, Florian Weimer wrote: ### Disable strict symbol checks in the link editor (ld) By default, the link editor will refuse to link shared objects which contain undefined symbols. In some cases (such as when a DSO is

Re: Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze

On Tue, Mar 06, 2018 at 09:25:16AM +0100, Jan Kurik wrote: > Today, on 2018-Mar-06, we reach two important milestones of the Fedora > 28 release [1]: > > == Change Checkpoint: 100% Code Complete Deadline [2] == > * New accepted changes must be code complete, meaning all the code > required to

Re: Patching JSON tag without hardcoding library path (package firefox-pkcs11-loader)

Il 05/03/2018 12:10, Florian Weimer ha scritto: > On 03/05/2018 11:43 AM, Germano Massullo wrote: >> Il 05/03/2018 08:25, Florian Weimer ha scritto: >>> On 03/04/2018 03:02 PM, Germano Massullo wrote: This tag is wrong and for example on x86_64 CPU architecture systems, it must be

Re: Call for testing of xserver 1.20 release candidates

On Tue, 2018-03-06 at 12:57 +, Leigh Scott wrote: > > On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote: > > > > Much as I would like to, the change process does exist, and says it's > > far too late for that for F28 gold. > > Can't new Xorg wait till F29?, isn't this change to big and

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

On Tue, Mar 06, 2018 at 04:19:48PM +0100, Germano Massullo wrote: > Il 06/03/2018 15:50, Daniel P. Berrangé ha scritto: > > On Tue, Mar 06, 2018 at 03:46:38PM +0100, Germano Massullo wrote: > >> Il 06/03/2018 15:34, Daniel P. Berrangé ha scritto: > >>> %{_lib} expands to 'lib64' on x86_64, and

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

El mar, 06-03-2018 a las 15:29 +0100, Germano Massullo escribió: > During package firefox-pkcs11-loader build, the following two spec > file > lines > > %dir %_prefix/%{_lib}/mozilla/pkcs11-modules/ > %_prefix/%{_lib}/mozilla/pkcs11-modules/onepinopenscpkcs11.json > > and also this variant > >

Critpath karma

Greetings! Does anybody here know the history and/or purpose behind Bodhi's critical path karma? A brief grepping of Bodhi's codebase makes me think it isn't really used by Bodhi for any purpose other than recording and displaying people's entries. I.e., it doesn't seem to be used in Bodhi's

Re: Critpath karma

On Tue, Mar 6, 2018 at 1:48 PM, Randy Barlow wrote: > Greetings! > > Does anybody here know the history and/or purpose behind Bodhi's > critical path karma? A brief grepping of Bodhi's codebase makes me think > it isn't really used by Bodhi for any purpose other than

Re: Kernel marking files in /boot as %ghost

On Tue, Mar 6, 2018, at 3:27 AM, Samuel Rakitničan wrote: > But what are the original reasons exactly? Seems like those files are > used by rpm-ostree. The `/usr` files are also copied by grubby. And while it's true *today* that rpm-ostree adapted to the /usr/lib/modules change, in fact the

Re: [SO-NAME BUMP] libjson-c.so.4 comes to fc28 and Rawhide

On 03/06/2018 03:24 PM, Björn 'besser82' Esser wrote: > Am Dienstag, den 06.03.2018, 15:18 +0100 schrieb Kalev Lember: >> Can you wait with this until after the F28 beta freeze is lifted? If >> you >> do a large scale soname bump during the freeze it pretty much makes it >> impossible to get

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

On Tue, Mar 06, 2018 at 03:29:58PM +0100, Germano Massullo wrote: > During package firefox-pkcs11-loader build, the following two spec file > lines > > %dir %_prefix/%{_lib}/mozilla/pkcs11-modules/ > %_prefix/%{_lib}/mozilla/pkcs11-modules/onepinopenscpkcs11.json > > and also this variant > >

Re: Frequently broken Rawhide/Branched composes

Pierre-Yves Chibon wrote: > On Sat, Mar 03, 2018 at 07:35:00PM +0100, Kevin Kofler wrote: >> So please let us just repeal that "Rawhide can never go backwards" >> policy. > > This is actually a fair point, but I wonder what prevents us from doing it > today. Technically, nothing. This is purely

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Il 06/03/2018 15:50, Daniel P. Berrangé ha scritto: > On Tue, Mar 06, 2018 at 03:46:38PM +0100, Germano Massullo wrote: >> Il 06/03/2018 15:34, Daniel P. Berrangé ha scritto: >>> %{_lib} expands to 'lib64' on x86_64, and %{_libdir} thus expands >>> to "/usr/lib64", but your app is installing files

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Il 06/03/2018 16:19, Germano Massullo ha scritto: > Il 06/03/2018 15:50, Daniel P. Berrangé ha scritto: >> On Tue, Mar 06, 2018 at 03:46:38PM +0100, Germano Massullo wrote: >>> Il 06/03/2018 15:34, Daniel P. Berrangé ha scritto: %{_lib} expands to 'lib64' on x86_64, and %{_libdir} thus

Re: Critpath karma

El mar, 06-03-2018 a las 08:48 -0500, Randy Barlow escribió: > Greetings! > > Does anybody here know the history and/or purpose behind Bodhi's > critical path karma? A brief grepping of Bodhi's codebase makes me > think > it isn't really used by Bodhi for any purpose other than recording > and >

[Modularity] Working Group IRC meeting minutes (2018-03-06)

= #fedora-meeting-3: Meeting of the Modularity Working Group (once every two weeks) = Meeting started by nils at 15:00:00 UTC.

Re: Frequently broken Rawhide/Branched composes

On Tue, Mar 06, 2018 at 02:58:45PM +, Stephen Gallagher wrote: >On Tue, Mar 6, 2018 at 9:54 AM Pierre-Yves Chibon >wrote: > > On Tue, Mar 06, 2018 at 03:33:44PM +0100, Kevin Kofler wrote: > > Pierre-Yves Chibon wrote: > > > > > On Sat, Mar 03,

Re: Frequently broken Rawhide/Branched composes

Le mardi 06 mars 2018 à 15:53 +0100, Pierre-Yves Chibon a écrit : > On Tue, Mar 06, 2018 at 03:33:44PM +0100, Kevin Kofler wrote: > > Pierre-Yves Chibon wrote: > > > > > On Sat, Mar 03, 2018 at 07:35:00PM +0100, Kevin Kofler wrote: > > > > So please let us just repeal that "Rawhide can never go >

[SO-NAME BUMP] libjson-c.so.4 comes to fc28 and Rawhide

Hello folks, I'll update json-c to v0.13.1 for fc28 and Rawhide. This will bump libjson-c so-name from 3 to 4 without any changes to the API. The bump was done, because some distributions already bumped the so-name to 3 with json-c v0.12 on their own. I'll bump and rebuild all affected

Re: systemd 238 and sysusers

On Tue, Mar 06, 2018 at 01:03:30PM +0100, Steve Grubb wrote: > On Mon, 5 Mar 2018 23:11:12 + > Zbigniew Jędrzejewski-Szmek wrote: > > > - somewhat independently, systemd-sysusers has been beefed up so it is > > possible to use it to create system users before any files

Re: [SO-NAME BUMP] libjson-c.so.4 comes to fc28 and Rawhide

Am Dienstag, den 06.03.2018, 15:18 +0100 schrieb Kalev Lember: > On 03/06/2018 03:10 PM, Björn 'besser82' Esser wrote: > > Hello folks, > > > > I'll update json-c to v0.13.1 for fc28 and Rawhide. This will bump > > libjson-c so-name from 3 to 4 without any changes to the API. The > > bump > >

Re: Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze

Jan Kurik wrote: > " Beta and Final freezes are in effect from 00:00 UTC of the freeze day." I always find this very misleading. IMHO, the freeze date announced should be the day before (i.e., this needs no actual change to the policies, just to the announced days) so that the announced date is

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Il 06/03/2018 15:34, Daniel P. Berrangé ha scritto: > %{_lib} expands to 'lib64' on x86_64, and %{_libdir} thus expands > to "/usr/lib64", but your app is installing files into "/usr/lib" > instead. I suspected this, but I found no hardcoded paths in

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

On Tue, Mar 06, 2018 at 03:46:38PM +0100, Germano Massullo wrote: > Il 06/03/2018 15:34, Daniel P. Berrangé ha scritto: > > %{_lib} expands to 'lib64' on x86_64, and %{_libdir} thus expands > > to "/usr/lib64", but your app is installing files into "/usr/lib" > > instead. > > I suspected this,

Re: Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze

On Tue, Mar 6, 2018 at 9:43 AM Kevin Kofler wrote: > Jan Kurik wrote: > > " Beta and Final freezes are in effect from 00:00 UTC of the freeze day." > > I always find this very misleading. IMHO, the freeze date announced should > be the day before (i.e., this needs no

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

done: procps-ng, psmisc, psacct On 02/18/2018 06:09 PM, Igor Gnatenko wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Over this weekend I've performed scratch-mass-rebuild without having gcc and gcc-c++ in buildroot of all Fedora packages, many of which failed due to random reasons and

Re: [SO-NAME BUMP] libjson-c.so.4 comes to fc28 and Rawhide

On 03/06/2018 03:10 PM, Björn 'besser82' Esser wrote: > Hello folks, > > I'll update json-c to v0.13.1 for fc28 and Rawhide. This will bump > libjson-c so-name from 3 to 4 without any changes to the API. The bump > was done, because some distributions already bumped the so-name to 3 > with

%{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

During package firefox-pkcs11-loader build, the following two spec file lines %dir %_prefix/%{_lib}/mozilla/pkcs11-modules/ %_prefix/%{_lib}/mozilla/pkcs11-modules/onepinopenscpkcs11.json and also this variant %dir %{_libdir}/mozilla/pkcs11-modules/

Re: systemd 238 and sysusers

On Tue, Mar 6, 2018 at 9:24 AM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Tue, Mar 06, 2018 at 01:03:30PM +0100, Steve Grubb wrote: > > On Mon, 5 Mar 2018 23:11:12 + > > Zbigniew Jędrzejewski-Szmek wrote: > > > > > - somewhat independently,

Re: [HEADS UP] Changes in wireshark package name

Michal Ruprich wrote: > the plan to drop the GTK+ GUI [1] was approved by FESCO, so I will be > dropping the wireshark-gtk package in rawhide(currently F29). Also I > would like to propose that we change the name of wireshark-qt. There are > three packages now - wireshark-cli, wireshark-gtk and

Re: Frequently broken Rawhide/Branched composes

On Tue, Mar 06, 2018 at 03:33:44PM +0100, Kevin Kofler wrote: > Pierre-Yves Chibon wrote: > > > On Sat, Mar 03, 2018 at 07:35:00PM +0100, Kevin Kofler wrote: > >> So please let us just repeal that "Rawhide can never go backwards" > >> policy. > > > > This is actually a fair point, but I wonder

Re: Frequently broken Rawhide/Branched composes

On Tue, Mar 6, 2018 at 9:54 AM Pierre-Yves Chibon wrote: > On Tue, Mar 06, 2018 at 03:33:44PM +0100, Kevin Kofler wrote: > > Pierre-Yves Chibon wrote: > > > > > On Sat, Mar 03, 2018 at 07:35:00PM +0100, Kevin Kofler wrote: > > >> So please let us just repeal that "Rawhide

Fedora-Atomic 27-20180307.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

Re: systemd 238 and sysusers

On Tue, 06 Mar 2018 14:34:58 + Stephen Gallagher wrote: > On Tue, Mar 6, 2018 at 9:24 AM Zbigniew Jędrzejewski-Szmek < > zbys...@in.waw.pl> wrote: > > > On Tue, Mar 06, 2018 at 01:03:30PM +0100, Steve Grubb wrote: > > > On Mon, 5 Mar 2018 23:11:12 + > > >

Re: [HEADS UP] Changes in wireshark package name

On 03/06/2018 06:23 AM, Michal Ruprich wrote: > the plan to drop the GTK+ GUI [1] was approved by FESCO, so I will be > dropping the wireshark-gtk package in rawhide(currently F29). Also I > would like to propose that we change the name of wireshark-qt. There are > three packages now -

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

Il 06/03/2018 16:35, Dennis Gilmore ha scritto: > El mar, 06-03-2018 a las 15:29 +0100, Germano Massullo escribió: >> During package firefox-pkcs11-loader build, the following two spec >> file >> lines >> >> %dir %_prefix/%{_lib}/mozilla/pkcs11-modules/ >>

Re: systemd 238 and sysusers

On Tue, 6 Mar 2018 14:24:27 + Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Mar 06, 2018 at 01:03:30PM +0100, Steve Grubb wrote: > > On Mon, 5 Mar 2018 23:11:12 + > > Zbigniew Jędrzejewski-Szmek wrote: > > > > > - somewhat independently,

Re: systemd 238 and sysusers

On Tue, Mar 06, 2018 at 05:15:45PM +0100, Steve Grubb wrote: > On Tue, 06 Mar 2018 14:34:58 + > Stephen Gallagher wrote: > > > On Tue, Mar 6, 2018 at 9:24 AM Zbigniew Jędrzejewski-Szmek < > > zbys...@in.waw.pl> wrote: > > > > > On Tue, Mar 06, 2018 at 01:03:30PM

Re: %{_lib} leads to dir not found, whereas lib works fine (firefox-pkcs11-loader)

El mar, 06-03-2018 a las 17:20 +0100, Germano Massullo escribió: > Il 06/03/2018 16:35, Dennis Gilmore ha scritto: > > El mar, 06-03-2018 a las 15:29 +0100, Germano Massullo escribió: > > > During package firefox-pkcs11-loader build, the following two > > > spec > > > file > > > lines > > > > > >

Re: -z defs linker flag activated in Fedora rawhide

On Tue, 2018-03-06 at 12:20 +0100, Florian Weimer wrote: > On 03/05/2018 05:55 PM, Sérgio Basto wrote: > > On Mon, 2018-01-22 at 16:24 +0100, Florian Weimer wrote: > > > ### Disable strict symbol checks in the link editor (ld) > > > > > > By default, the link editor will refuse to link shared

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

Hi, I fixed all my packages. my package list: google-noto-emoji-fonts ibus-libpinyin ibus-libzhuyin ibus-pinyin ibus-rime libpinyin librime libthai opencc pyzy scim scim-bridge scim-fcitx scim-pinyin scim-thai sunpinyin zinnia Thanks, Peng Wu On Mon, Feb 19, 2018 at 1:09 AM, Igor

Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze

Today, on 2018-Mar-06, we reach two important milestones of the Fedora 28 release [1]: == Change Checkpoint: 100% Code Complete Deadline [2] == * New accepted changes must be code complete, meaning all the code required to enable a new Change is finished. * The level of code completeness is

Re: Attempting to contact unresponsive maintainers - xing, noriko, aortega, jcholast, mzatko

Dne 5.3.2018 v 21:03 Kevin Fenzi napsal(a): > On 02/07/2018 10:27 AM, Kevin Fenzi wrote: >> Greetings, we've been told that the email addresses for these package >> maintainers are no longer valid. I'm starting the unresponsive >> maintainer policy to find out if they are still interested in >>

Re: Test gate failures

On Sat, Mar 3, 2018 at 5:15 PM, Michael Cronenworth wrote: > Hello, > > The "Test Gating" mechanism is preventing two updates from being pushed. > > * F27 Wine 3.3 >- "The update can not be pushed: no test results found" >-

Software Translation Deadline has been reached

Today on 2018-Mar-06 [1] we have reached the Software Translation Deadline [2]. At this time all the strings translations should be substantially finished. [1] https://fedoraproject.org/wiki/Releases/28/Schedule [2] https://fedoraproject.org/wiki/L10N_Freezes#Translation_Deadline Regards, Jan --

Re: Kernel marking files in /boot as %ghost

> On Fri, Mar 2, 2018 at 1:11 AM, Samuel Rakitničan > > What is the result you expect from this email? You filed a bug, it > was closed because the packaging was done intentionally and there is > no other solution when considering the original reasons

Re: Trying out More Go Packaging: Bugs and Questions

Hi Robert-André, thank you for your patience and all comments pointing out pieces that are not working as expected. Introduction of new macros is a time-consuming process and it requires resilience so we keep up till the state where the macros are generally usable for a lot of our use cases.

Re: Attempting to contact unresponsive maintainers - xing, noriko, aortega, jcholast, mzatko

- Original Message - > From: "Kevin Fenzi" > To: devel@lists.fedoraproject.org > Sent: Monday, March 5, 2018 9:03:50 PM > Subject: Re: Attempting to contact unresponsive maintainers - xing, noriko, > aortega, jcholast, mzatko > > On 02/07/2018 10:27 AM, Kevin Fenzi

Re: Trying out More Go Packaging: Bugs and Questions

Hi Fabio, thank you for staying with us in the Go packaging world and for sharing any difficulty or problem you encounter with. I created github repository [1] where you can report all issues wrt. macros used in Go packaging. We are currently in a process of iterating over all the macros.

Re: Re: Trying out More Go Packaging: Bugs and Questions

On 02/27/2018 07:22 PM, Nicolas Mailhot wrote: Le mardi 27 février 2018 à 18:34 +0100, Robert-André Mauchin a écrit : How do we test this? I installedtho go-srpm-macros from Rawhide but it doesn't seem to have the required macros? Yes in rawhide go-compilers and go-srpm-macros are in an

Re: systemd 238 and sysusers

On Mon, 5 Mar 2018 23:11:12 + Zbigniew Jędrzejewski-Szmek wrote: > - somewhat independently, systemd-sysusers has been beefed up so it is > possible to use it to create system users before any files are > installed on disk, but honouring admin overrides. In short, we

Re: Re: Re: Trying out More Go Packaging: Bugs and Questions

Hi Athos, hope everything is fine and you have better things to do than spending much time updating the Go spec files :) Anything you need and/or anything that could help you to minimize your packaging time, please, let us know :). On 03/04/2018 08:20 PM, Nicolas Mailhot wrote: Le samedi

Re: Call for testing of xserver 1.20 release candidates

> On Mon, 2018-03-05 at 18:03 +0100, Kalev Lember wrote: > > Much as I would like to, the change process does exist, and says it's > far too late for that for F28 gold. > > - ajax Can't new Xorg wait till F29?, isn't this change to big and prone to breakage to be pushed after F28 release?

Re: Fedora 28 Change Checkpoint: 100% Code Complete Deadline & Beta Freeze

On Tue, Mar 6, 2018 at 10:34 AM, Zbigniew Jędrzejewski-Szmek wrote: > On Tue, Mar 06, 2018 at 09:25:16AM +0100, Jan Kurik wrote: >> Today, on 2018-Mar-06, we reach two important milestones of the Fedora >> 28 release [1]: >> >> == Change Checkpoint: 100% Code Complete Deadline

[Bug 1550526] Upgrade perl-Image-ExifTool to 10.80

https://bugzilla.redhat.com/show_bug.cgi?id=1550526 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA

[Bug 1550526] Upgrade perl-Image-ExifTool to 10.80

https://bugzilla.redhat.com/show_bug.cgi?id=1550526 --- Comment #6 from Fedora Update System --- perl-Image-ExifTool-10.80-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See

[EPEL-devel] [Fedocal] Reminder meeting : EPEL Steering Committee

Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2018-03-07 from 18:00:00 to 19:00:00 GMT At fedora-meet...@irc.freenode.net The meeting will be about: The EPEL Steering Committee will have a weekly meeting to cover current tasks and problems needed to keep EPEL

[Bug 1550526] Upgrade perl-Image-ExifTool to 10.80

https://bugzilla.redhat.com/show_bug.cgi?id=1550526 --- Comment #7 from Fedora Update System --- perl-Image-ExifTool-10.80-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. See

[EPEL-devel] Fedora EPEL 7 updates-testing report

The following Fedora EPEL 7 Security updates need testing: Age URL 1093 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 856 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 438

[Bug 1550526] Upgrade perl-Image-ExifTool to 10.80

https://bugzilla.redhat.com/show_bug.cgi?id=1550526 --- Comment #8 from Fedora Update System --- perl-Image-ExifTool-10.80-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See

[EPEL-devel] Fedora EPEL 6 updates-testing report

The following Fedora EPEL 6 Security updates need testing: Age URL 966 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 856 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb mcollective-2.8.4-1.el6 827

[EPEL-devel] Re: Adding devtoolset to EPEL

On 02/14/2018 08:36 AM, Peter Robinson wrote: >>> I have gotten scl's for RH PPCLE and x86_64 downloaded to the Fedora >>> Infrastructure batcave. I have not been able to get aarch64 >>> downloaded. I need help here on getting the cdn address correct. >>> >>> I need someone from releng (I guess it

[EPEL-devel] Meeting Agenda for 2018-03-07

I am currently sick due to pertussis so may not be able to run the meeting. The items on the agenda are: * Has anyone evaluated changes in upcoming 7.5? * Developertoolset 7 has been synced and turned on in koji * What to do with other SCL's? * What to do when dts-8 comes out? * Other? --

[Bug 1552358] New: perl-Test2-Suite-0.000106 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1552358 Bug ID: 1552358 Summary: perl-Test2-Suite-0.000106 is available Product: Fedora Version: rawhide Component: perl-Test2-Suite Keywords: FutureFeature, Triaged Assignee:

[Bug 1438957] icons are missing on bugzilla's front page

https://bugzilla.redhat.com/show_bug.cgi?id=1438957 Fedora Update System changed: What|Removed |Added Status|ON_QA

[Bug 1544277] perl-Dist-Zilla-6.011 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1544277 Fedora Update System changed: What|Removed |Added Status|ON_QA

[Bug 1546584] perl-Importer-0.025 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1546584 --- Comment #6 from Fedora Update System --- perl-Importer-0.025-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. -- You are

[Bug 1479864] Upgrade perl-Net-SSH-Perl to 2.12

https://bugzilla.redhat.com/show_bug.cgi?id=1479864 Bug 1479864 depends on bug 1546648, which changed state. Bug 1546648 Summary: Review Request: perl-IO-Socket-Socks - Provides a way to create socks (4 or 5) client or server https://bugzilla.redhat.com/show_bug.cgi?id=1546648 What

[Bug 1546961] perl-Dancer-Session-Cookie-0.29 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1546961 --- Comment #6 from Fedora Update System --- perl-Dancer-Session-Cookie-0.29-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. -- You

[Bug 1544162] perl-Dancer-Session-Cookie-0.28 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1544162 --- Comment #10 from Fedora Update System --- perl-Dancer-Session-Cookie-0.29-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. -- You

[Bug 1547462] perl-Term-Chrome-2.01 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1547462 --- Comment #6 from Fedora Update System --- perl-Term-Chrome-2.01-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. -- You are

[Bug 1548207] perl-DateTime-Format-Flexible-0.29 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1548207 --- Comment #6 from Fedora Update System --- perl-DateTime-Format-Flexible-0.29-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. --

[Bug 1544277] perl-Dist-Zilla-6.011 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1544277 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Dist-Zilla-6.011-1.fc2

  1   2   >