Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, 2016-10-05 at 16:26 -0500, Michael Catanzaro wrote: > > Probably would should just use the existing freeze exception process > for this purpose? What's the benefit of adding another thing? One thing about the freeze exception process is that we only actually review proposed freeze

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Thu, 2016-10-06 at 00:05 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > I don't want to get in the KDE folks' bad graces, but this likely could > > also affect KDE's graphical update system, so I'd advise against using > > that for the present too. > > > Offline updates in KDE are

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On 10/05/2016 05:24 PM, Matthew Miller wrote: On Wed, Oct 05, 2016 at 04:59:57PM -0400, Przemek Klosowski wrote: Now that systemd kills processes on logout, and session timeout is required by security policies in many workplaces including mine, I fear we'll have more of those. I certainly had

Fedora 25 Beta 1.1 compose check report

Missing expected images: Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 2/101 (x86_64), 1/17 (i386), 2/2 (arm) New failures (same test did not fail in 25 Alpha 1.2): ID: 38800 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL:

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 5, 2016 at 3:53 PM, Adam Williamson wrote: > I honestly think GNOME has this exactly right for the 'general' user: > the safe thing to do is to strongly encourage offline updates, i.e. > don't offer any online update mechanism through the desktop. In a >

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, Oct 05, 2016 at 16:26:54 -0500, Michael Catanzaro wrote: On Wed, 2016-10-05 at 14:19 -0400, Matthew Miller wrote: I propose we create a parallel "Critical Issues"  list, using basically the same procedures. Issues eligible for this status would be those which do

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

5.10.2016 22:21 Dan Book wrote: > [...] I'd like to add that at least the MATE and Cinnamon spins, possibly > others, do not include PackageKit and instead expect users to update using > yumex-dnf or dnf itself. So ideally an offline update mechanism can be added > to dnf, and

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

Adam Williamson wrote: > The Target trackers were discontinued, so far as I recall, because no- > one ever really took a blind bit of notice of them. People would throw > bugs onto the list and then...nothing much would happen. It was just > kind of a wishlist and (IIRC) very few packagers even

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

Matthew Miller wrote: > I propose we create a parallel "Critical Issues" list, using basically > the same procedures. Issues eligible for this status would be those > which do not necessarily fail a release criterion but which have > critical impact on a Fedora Edition or on a council-approved

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 5, 2016 at 3:14 PM, Przemek Klosowski wrote: > On 10/04/2016 08:12 PM, Chris Murphy wrote: > > The first is what happens on the other 90% of the world's computers, > including Android system updates. Consider that. The second exists, > right now, and it

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Thu, 2016-10-06 at 00:36 +0200, Kevin Kofler wrote: > > In fact, I would argue that this should even be done for blockers: A bug > should be a blocker if and only if a SIG/WG behind a release-blocking image > decides that it is important for it to be fixed in the release, no matter >

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On 10/5/2016 2:40 PM, Chris Murphy wrote: On Wed, Oct 5, 2016 at 3:14 PM, Przemek Klosowski wrote: I think it is a mistake to require reboot for _every_ update, even though, as you say, even user apps sometimes _cannot_ be updated online (*). I am comfortable with

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

Adam Williamson wrote: > I don't want to get in the KDE folks' bad graces, but this likely could > also affect KDE's graphical update system, so I'd advise against using > that for the present too. Offline updates in KDE are just not going to happen any time soon. I also don't see offline

Call for help contacting contributor: aledvink

Dear all, Packagers, members of the fedorabugs group and people having a 'watchbugzilla' ACL in pkgdb must have a bugzilla account attached to the email they set in the Fedora Account System (FAS). This is mandatory to allow ACLs to be propagated from pkgdb to bugzilla, allowing the right person

Re: Tracking num-lock state on wayland

- Original Message - > Hi, > > I maintain lockkeys extension for gnome shell. It displays num-lock and > caps-lock states in the panel. It also shows notification if either of > these states change. > > I use Keymap's "state-changed" signal: >

A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

Hello, I'd like to present a new free tool for maintainers of software libraries — Package ABI Diff Tool (Pkg-ABIdiff). It's a tool for backward compatibility analysis of API/ABI interfaces in RPM packages. It is based on ABICC and ABI Dumper tools. The tool does the following: 1.

Re: ... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Tue, 2016-10-04 at 18:19 -0500, Ian Pilcher wrote: > On 10/04/2016 01:03 PM, Tomasz Torcz wrote: > > > > On Tue, Oct 04, 2016 at 12:31:43PM -0500, Ian Pilcher wrote: > > > > > > > > > Can you clarify?  In what circumstances would the dnf command > > > running > > > within a screen session

Re: Call for help contacting contributor: spike

On Mon, Sep 05, 2016 at 12:45:44PM +0200, Pierre-Yves Chibon wrote: > Dear all, > > Packagers, members of the fedorabugs group and people having a 'watchbugzilla' > ACL in pkgdb must have a bugzilla account attached to the email they set in > the > Fedora Account System (FAS). > This is

Re: A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

On Wed, Oct 5, 2016 at 8:05 AM, Ponomarenko Andrey wrote: > Hello, > > I'd like to present a new free tool for maintainers of software libraries — > Package ABI Diff Tool (Pkg-ABIdiff). It's a tool for backward compatibility > analysis of API/ABI interfaces in RPM

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

Kevin, now you mention Wayland... Could it be possible to be a Wayland related issue? I have Nvidia but no Wayland and never an issue updating from desktop. Cheers, Sylvia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe

Fedora 25 Beta 1.1 compose check report

Missing expected images: Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 3/101 (x86_64), 1/17 (i386), 1/2 (arm) New failures (same test did not fail in 25 Alpha 1.2): ID: 38800 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL:

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Wednesday, October 5, 2016 10:49:26 AM CEST Dan Horák wrote: > I haven't thought much about it yet how feasible it would be, but why > not "abuse" rpm infrastructure even for the tests? Introduce foo-test > package as a test-suite for package foo and do everything within its > spec file -

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

I never needed to reboot. I just keep working on my stuff, when I'm done I turn the laptop off. Is there any reason to reboot right after updating? Cheers, Sylvia ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

Stephen Gallagher wrote: > That seems like a waste of effort, considering we have the offline updates > process which just boots into a special, minimalist environment with > almost nothing but the updater running. But the offline process is highly impractical, it requires you to interrupt all

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Thu, 2016-10-06 at 00:36 +0200, Kevin Kofler wrote: > In fact, I would argue that this should even be done for blockers: A > bug  > should be a blocker if and only if a SIG/WG behind a release-blocking > image  > decides that it is important for it to be fixed in the release, no > matter  >

Schedule for Thursday's FPC Meeting (2016-10-06 16:00 UTC)

 Following is the list of topics that will be discussed in the FPC meeting Thursday at 2016-10-06 16:00 UTC in #fedora-meeting-1 on irc.freenode.net.  Local time information (via. rktime): 2016-10-06 09:00 Thu US/Pacific PDT 2016-10-06 12:00 Thu US/Eastern EDT 2016-10-06

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Tue, Oct 4, 2016 at 10:37 AM, Chris Murphy wrote: > On Tue, Oct 4, 2016 at 11:26 AM, Andrew Lutomirski wrote: >> On Tue, Oct 4, 2016 at 10:05 AM, Kevin Fenzi wrote: >>> On Tue, 4 Oct 2016 09:51:16 -0700 >>> Andrew Lutomirski

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

Kevin Kofler writes: Adam Williamson wrote: > I don't want to get in the KDE folks' bad graces, but this likely could > also affect KDE's graphical update system, so I'd advise against using > that for the present too. Offline updates in KDE are just not going to happen any time soon. I also

Re: A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

On Wed, Oct 05, 2016 at 06:36:16PM +0300, Ponomarenko Andrey wrote: > The tool is based on different software stack for analysis of backward > compatibility developed since 2009: https://github.com/lvc (ABI Compliance > Checker, ABI Dumper, etc.) > > RedHat created an alternative libabigail tool

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, 2016-10-05 at 19:17 -0700, Gerald B. Cox wrote: > On Wed, Oct 5, 2016 at 3:53 PM, Adam Williamson > wrote: > > > I honestly think GNOME has this exactly right for the 'general' user: > > the safe thing to do is to strongly encourage offline updates, i.e. > >

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, 2016-10-05 at 20:38 -0700, Andrew Lutomirski wrote: > I don't understand how you arrive at this conclusion. dnf is sitting > > on the top of a house of cards when it's running in Terminal. If > > anything below it dies, dnf dies and by extension so is rpm. Could dnf > > be put into it's

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, 2016-10-05 at 23:54 -0400, Sam Varshavchik wrote: > * As a general workaround for this type of crashes, we need a > > complete-transaction command in DNF – please add your voices to: > > https://bugzilla.redhat.com/show_bug.cgi?id=1091702 > > – and not the sledgehammer approach of

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Tuesday, October 4, 2016 8:09:14 PM CEST Richard W.M. Jones wrote: > And related to this question, do we also need to define > "TestRequires" packages/dependencies? Sounds like natural approach would be to install the built packages into some minimal environment, and the packages itself should

[Test-Announce] Fedora 25 Candidate Beta-1.1 Available Now!

According to the schedule [1], Fedora 25 Candidate Beta-1.1 is now available for testing. Please help us complete all the validation testing! For more information on release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Wed, Oct 05, 2016 at 07:54:59AM +0200, Pavel Raiskup wrote: > On Tuesday, October 4, 2016 8:09:14 PM CEST Richard W.M. Jones wrote: > > And related to this question, do we also need to define > > "TestRequires" packages/dependencies? > > Sounds like natural approach would be to install the

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Wed, 5 Oct 2016 09:32:49 +0100 "Richard W.M. Jones" wrote: > On Wed, Oct 05, 2016 at 07:54:59AM +0200, Pavel Raiskup wrote: > > On Tuesday, October 4, 2016 8:09:14 PM CEST Richard W.M. Jones > > wrote: > > > And related to this question, do we also need to define > > >

Tracking num-lock state on wayland

Hi, I maintain lockkeys extension for gnome shell. It displays num-lock and caps-lock states in the panel. It also shows notification if either of these states change. I use Keymap's "state-changed" signal: Gdk.Keymap.get_default().connect('state-changed', ...); to receive numlock and capslock

Packages left behind on f24->f25 upgrade

Hey, I upgraded from f24 to f25 yesterday with dnf system-upgrade. I had a few issues during the upgrade: - ghc-nats has been removed from f25, but was installed on f24 if you had pandoc installed for example. Since ghc is newer and had a soname bump, the upgrade cannot go smoothly unless

Re: /sbin/nologin in /etc/shells

On Tue, Oct 04, 2016 at 07:33:40PM -, Toby Goodwin wrote: > Stephen, I've been striving to keep my comments technically focused. > That remark slipped below my own standards. I didn't mean it as a > personal jibe, just a slightly light hearted way of characterizing one > side of the debate. I

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Tue, Oct 4, 2016 at 8:30 PM, Adam Williamson wrote: > Querying the package database and installing new packages. A system > update, on the other hand, is...it's not *configurable*, really. You > say 'update my system, please!' and you get an updated system. That's

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 05, 2016 at 01:13:35AM +0200, Björn Persson wrote: > I don't get any notifications at all. I just try to remember to run Yum > periodically, and there I'm not told which updates are security updates. If you install fedora-motd, it'll update /etc/motd with pending update info when you

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On 2016-10-05, Pavel Raiskup wrote: > Right, or more - it would be fine to have testsuite `make install`able > (automatically by Automake e.g.). Then anybody could create 'foo-test' > package and than end-users could do the testing themselves too, > transparently - the same

Re: ... and Fedora 25! - Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 05, 2016 at 12:38:15PM +0200, Martin Kolman wrote: > > >    KillUserProcesses=yes > > Ouch!  Forgot about that. > BTW, was there any progress in making screen & tmux aware of this, so > that screen and tmux sessions are not killed when the user logs out or > - as in this case - the

Re: Cloud and Server Q

On Tue, Oct 4, 2016 at 6:21 AM, Kushal Das wrote: > On 30/09/16, Josh Berkus wrote: >> On 09/30/2016 02:01 PM, Josh Boyer wrote: >> >> > 16:44:56 Cloud base image is the only blocking deliverable. >> > 16:44:59 Atomic is not. >> > >> > I realize this WG is in the middle of

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Tue, Oct 4, 2016 at 8:31 PM, Chris Murphy wrote: > > And really the bottom line is, dnf update is fine the vast majority of > the time, except when it isn't. Failures are somewhere in between a > bug and not at all surprising. And people have been working hard on >

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

> I never needed to reboot. I just keep working on my stuff, when I'm > done I turn the laptop off. Is there any reason to reboot right after > updating? That's actually a very common misunderstanding. People think that "yum/dnf update" leaves their system in a new updated stage. But it

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 5, 2016 at 6:51 AM, Gerald B. Cox wrote: > > That said, they basically already do it with the dnf-system-upgrade > plugin; so why not just expand > that a bit. Also, while i completely understand that it is much easier to > just use a sledgehammer and say "offline

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Tue, Oct 04, 2016 at 20:42:11 -0700, Adam Williamson wrote: I'd say broadly speaking both, but the most disruptive and potentially catastrophic effect is when the update process itself crashes or is killed. Because of how RPM transactions work, this generally

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, 5 Oct 2016 10:56:35 -0500 Bruno Wolff III wrote: > On Tue, Oct 04, 2016 at 20:42:11 -0700, > Adam Williamson wrote: > > > >I'd say broadly speaking both, but the most disruptive and > >potentially catastrophic effect is when the update

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Tue, 4 Oct 2016 20:09:14 +0100 "Richard W.M. Jones" wrote: > On Mon, Oct 03, 2016 at 08:21:42PM +, Zbigniew Jędrzejewski-Szmek > wrote: > > On Mon, Oct 03, 2016 at 01:50:33PM -0600, Tim Flink wrote: > > > One of the features for Taskotron that we've been planning

Re: Assistance to build LuxRender 1.6

Luya Tshimbalanga wrote: > Because upstream requires embree as dependency (only available for 64 bit > architectures), the conditional statement "%{?_lib} == "lib64" is no > longer valid. This is nonsense. Even if your package is ExclusiveArch: x86_64, %{_lib} will still be defined to "lib64",

[Fedocal] Reminder meeting : Fedora 25 Beta Go/No-Go Meeting

Dear all, You are kindly invited to the meeting: Fedora 25 Beta Go/No-Go Meeting on 2016-10-06 from 17:00:00 to 19:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Before each public release Development, QA and Release Engineering meet to determine if the release

spot pushed to perl-Image-Info (el5). "- Requires: rgb, not Requires: /usr/share/X11/rgb.txt"

From e702799918e3752b235f239306930aec541cc900 Mon Sep 17 00:00:00 2001 From: Adam Jackson Date: Mon, 9 Nov 2009 19:24:19 + Subject: - Requires: rgb, not Requires: /usr/share/X11/rgb.txt --- perl-Image-Info.spec | 7 +-- 1 file changed, 5 insertions(+), 2

spot pushed to perl-Image-Info (el5). "Update to 1.24."

From 05b659e6b572d0f8c9250c42a99a9b40ca155b78 Mon Sep 17 00:00:00 2001 From: Jose Pedro Oliveira Date: Mon, 26 Feb 2007 10:13:15 + Subject: Update to 1.24. --- .cvsignore | 2 +- perl-Image-Info.spec | 9 ++--- sources | 2 +- 3 files

spot pushed to perl-Image-Info (el5). "- Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild"

From 610337cd56f8fc7e88829eed2f2bd07557a87833 Mon Sep 17 00:00:00 2001 From: Jesse Keating Date: Thu, 26 Feb 2009 20:21:34 + Subject: - Rebuilt for https://fedoraproject.org/wiki/Fedora_11_Mass_Rebuild --- perl-Image-Info.spec | 5 - 1 file changed, 4

spot pushed to perl-Image-Info (el5). "Rebuild for new perl"

From 95030ac3618418301e04e0daa756359273278280 Mon Sep 17 00:00:00 2001 From: Tom Callaway Date: Mon, 28 Jan 2008 21:19:43 + Subject: Rebuild for new perl --- perl-Image-Info.spec | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

Re: A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

05.10.2016, 15:13, "Josh Boyer": > On Wed, Oct 5, 2016 at 8:05 AM, Ponomarenko Andrey wrote: >>  Hello, >> >>  I'd like to present a new free tool for maintainers of software libraries — >> Package ABI Diff Tool (Pkg-ABIdiff). It's a tool for backward compatibility >> analysis of API/ABI

Re: RFC: Storing Automated Tasks/Tests In Dist-Git (git-submodules)

I didn't notice that my reply went only to Pavel, resending to devel@ On Tue, 04 Oct 2016 10:25:46 +0200 Pavel Raiskup wrote: > On Monday, October 3, 2016 1:50:33 PM CEST Tim Flink wrote: > >

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Tue, 4 Oct 2016 11:08:36 -0600 Kevin Fenzi wrote: > > That being said, we're fine with either storage paradigm and it > > doesn't matter much if we look for tasks in a directory inside > > dist-git branches or a separate repo which only holds tasks as long > > as there is a

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On 10/05/2016 01:19 PM, Matthew Miller wrote: In any case, what do you all think? What happened to the Nice-To-Have (NTH) tag? ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Fedora Rawhide-20161005.n.0 compose check report

Missing expected images: Cloud_base raw-xz x86_64 Cloud_base raw-xz i386 Atomic raw-xz x86_64 Failed openQA tests: 70/102 (x86_64), 17/17 (i386), 1/2 (arm) New failures (same test did not fail in Rawhide-20161004.n.1): ID: 38912 Test: x86_64 Workstation-live-iso install_default_upload

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, 5 Oct 2016 13:29:41 -0500 Michael Cronenworth wrote: > On 10/05/2016 01:19 PM, Matthew Miller wrote: > > In any case, what do you all think? > > What happened to the Nice-To-Have (NTH) tag? It was renamed to "Freeze Exception" to better match what we were actually

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, Oct 05, 2016 at 13:29:41 -0500, Michael Cronenworth wrote: On 10/05/2016 01:19 PM, Matthew Miller wrote: In any case, what do you all think? What happened to the Nice-To-Have (NTH) tag? It was renamed to freeze exception. But it covers a different set of fixes.

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Tue, 4 Oct 2016 15:07:28 +0200 Vít Ondruch wrote: > Hi Tim, > > How about this use case: > > Let say I have Ruby on Rails. This framework is much broader then one > rubygem-rails package. Where test for such framework will be stored? Honestly, it depends on where you

PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

I've talked about this before, but maybe the F26 cycle is time to make it happen. Right now, we have only one way of saying "this bug is important to the project as a whole; could we please get resources focused on it?" — and that way is to stop the whole vehicle until someone does something about

Fedora 25-20161005.n.0 compose check report

Missing expected images: Cloud_base raw-xz i386 Failed openQA tests: 7/102 (x86_64), 1/17 (i386) New failures (same test did not fail in 25-20161004.n.0): ID: 39037 Test: x86_64 Workstation-live-iso base_service_manipulation URL: https://openqa.fedoraproject.org/tests/39037 ID: 39052

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, Oct 05, 2016 at 14:19:12 -0400, Matthew Miller wrote: In any case, what do you all think? I don't think the tracking side would be hard to do. What I'd like to hear about is how the list will work for getting bugs better fixed than bugzilla entries will?

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Tue, 4 Oct 2016 10:25:26 +0200 Jakub Jelen wrote: > On 10/03/2016 09:50 PM, Tim Flink wrote: > > One of the features for Taskotron that we've been planning since the > > beginning was a way for contributors to maintain their own automated > > tasks/tests which would be run

Re: Assistance to build LuxRender 1.6

On 05/10/16 10:07 AM, Kevin Kofler wrote: > Luya Tshimbalanga wrote: >> Because upstream requires embree as dependency (only available for 64 bit >> architectures), the conditional statement "%{?_lib} == "lib64" is no >> longer valid. > This is nonsense. Even if your package is ExclusiveArch:

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On 10/5/2016 9:37 AM, Kevin Fenzi wrote: On Wed, 5 Oct 2016 10:56:35 -0500 Bruno Wolff III wrote: On Tue, Oct 04, 2016 at 20:42:11 -0700, Adam Williamson wrote: The one thing I absolutely would advise against: don't do an update over ssh!

Re: RFC: Storing Automated Tasks/Tests In Dist-Git

On Tue, 4 Oct 2016 09:19:15 -0400 Matthew Miller wrote: > On Mon, Oct 03, 2016 at 02:35:00PM -0600, Kevin Fenzi wrote: > > Another alternate here is that we could make taskotron a 'namespace' > > like currently rpms/ and docker/ are. Then we would have > > perhaps:

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, Oct 5, 2016 at 3:16 PM, Chris Murphy wrote: > On Wed, Oct 5, 2016 at 12:19 PM, Matthew Miller > wrote: >> I've talked about this before, but maybe the F26 cycle is time to make >> it happen. Right now, we have only one way of saying

[Base] adopting the Docker base image into Atomic WG

Now that Cloud -> Atomic and will be focusing on Project Atomic, can we move the Docker base image into this group from the "Fedora Base" group? It never really made sense to me in Base; in: $ git log --format='%ae' fedora-docker-base.ks | sort -u admil...@redhat.com den...@ausil.us

[Fedocal] Reminder meeting : Fedora 25 Beta Release Readiness Meeting

Dear all, You are kindly invited to the meeting: Fedora 25 Beta Release Readiness Meeting on 2016-10-06 from 19:00:00 to 21:00:00 UTC At fedora-meetin...@irc.freenode.net The meeting will be about: Join us on irc.freenode.net in #fedora-meeting for the Fedora 25 Beta Release Readiness

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, Oct 5, 2016 at 12:19 PM, Matthew Miller wrote: > I've talked about this before, but maybe the F26 cycle is time to make > it happen. Right now, we have only one way of saying "this bug is > important to the project as a whole; could we please get resources >

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, 2016-10-05 at 06:18 -0700, Gerald B. Cox wrote: > On Tue, Oct 4, 2016 at 8:30 PM, Adam Williamson > wrote: > > > Querying the package database and installing new packages. A system > > update, on the other hand, is...it's not *configurable*, really. You > >

Re: A new tool for backward compatibility analysis of API/ABI interfaces in RPM packages

On Qua, 2016-10-05 at 18:36 +0300, Ponomarenko Andrey wrote: > 05.10.2016, 15:13, "Josh Boyer": > > > > On Wed, Oct 5, 2016 at 8:05 AM, Ponomarenko Andrey wrote: > > > > > >  Hello, > > > > > >  I'd like to present a new free tool for maintainers of software > > > libraries — Package ABI Diff

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, 2016-10-05 at 10:43 -0700, Japheth Cleaver wrote: > > After a check-update preview, I can count the number of times "yum -y > update &" has ever failed me over the years on one hand. That still sounds like somewhere between 1 and 5 times too many. =) The thing is, the case where dnf

Re: F26 proposal: Make Fedora Media Writer the officially supported USB install media creator

Adam Williamson wrote: > It's simply the case that no-one's cared enough about those features to > rewrite them. A few people have kicked around ideas for how to do it at > various points, but it's never gone beyond that. I think the main issue there is that the use cases for live USB media have

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 5, 2016 at 11:59 AM, Gerald B. Cox wrote: > > > I created a RFE bug requesting that the upgrade function in DNF be changed > to incorporate "offline" upgrades as an option. If it is really > an issue, DNF should handle it. >

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On 10/04/2016 12:06 PM, Andrew Lutomirski wrote: How hard would it be to make dnf do the rpm transaction inside a proper system-level service (transient or otherwise)? This would greatly increase robustness against desktop crashes, ssh connection loss, KillUserProcs, and other damaging

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

Giant +1 There are few things more frustrating than being bitten by a bug that goes unfixed for release after release, while being told by the maintainer that they simply don't have time to fix anything but release blockers. This wouldn't automaticall fix this, but it would certainly provide a

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 05, 2016 at 04:59:57PM -0400, Przemek Klosowski wrote: > Now that systemd kills processes on logout, and session timeout is > required by security policies in many workplaces including mine, I > fear we'll have more of those. I certainly had update sessions that > involved hundreds of

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On Wed, Oct 05, 2016 at 05:14:11PM -0400, Przemek Klosowski wrote: > What do you mean by 'system'? Android apps update online just fine. > Fedora does not have this distinction betwen apps and core system: > it's just a bunch of packages. I think it is a mistake to require > reboot for _every_

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, 2016-10-05 at 14:19 -0400, Matthew Miller wrote: > I propose we create a parallel "Critical Issues"  list, using > basically > the same procedures. Issues eligible for this status would be those > which do not necessarily fail a release criterion but which have > critical impact on a

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, 5 Oct 2016 14:19:12 -0400 Matthew Miller wrote: ...snip... > In any case, what do you all think? Well, we sort of have something like this today: common bugs. ie, things we think people will hit and we couldn't/didn't fix in time for release? But we only do

Re: PSA: Do not run 'dnf update' inside GNOME, KDE or any other graphical desktop on Fedora 24

On 10/04/2016 08:12 PM, Chris Murphy wrote: The first is what happens on the other 90% of the world's computers, including Android system updates. Consider that. The second exists, right now, and it works and it's a lot better than what the rest of the world uses. What do you mean by 'system'?

Re: PROPOSAL: Blocking the release is our only "big hammer" — let's add a softer one.

On Wed, 2016-10-05 at 14:19 -0400, Matthew Miller wrote: > I've talked about this before, but maybe the F26 cycle is time to make > it happen. Right now, we have only one way of saying "this bug is > important to the project as a whole; could we please get resources > focused on it?" — and that

[389-devel] Jenkins build is back to normal : 389-ds-base #1088

See ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org

[389-devel] Build failed in Jenkins: 389-ds-base #1087

See Changes: [William Brown] Ticket 48996 - update DS for ns 0.2.0 -- Started by an SCM change Building remotely on F23 (fedora Fedora23 Fedora fedora23) in workspace

[Bug 1382195] New: perl-Perl-Tidy-Sweetened-1.12 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1382195 Bug ID: 1382195 Summary: perl-Perl-Tidy-Sweetened-1.12 is available Product: Fedora Version: rawhide Component: perl-Perl-Tidy-Sweetened Keywords: FutureFeature, Triaged

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

The following Fedora EPEL 5 Security updates need testing: Age URL 847 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-1626 puppet-2.7.26-1.el5 696 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-3849 sblim-sfcb-1.3.8-2.el5 339

[Bug 1381897] perl-Messaging-Message-1.6.1 is available

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

[Bug 1379557] perl-Image-Info: XXE in SVG files [epel-5]

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

[Bug 1381896] perl-No-Worries-1.3 is available

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

[Bug 1382179] New: perl-Clownfish-0.6.0.3 is available

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

[Bug 1382191] New: perl-Mock-Sub-1.07 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1382191 Bug ID: 1382191 Summary: perl-Mock-Sub-1.07 is available Product: Fedora Version: rawhide Component: perl-Mock-Sub Keywords: FutureFeature, Triaged Assignee:

[Bug 1382191] perl-Mock-Sub-1.07 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1382191 --- Comment #1 from Upstream Release Monitoring --- Patching or scratch build for perl-Mock-Sub-1.06 failed. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 1382191] perl-Mock-Sub-1.07 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1382191 --- Comment #3 from Upstream Release Monitoring --- Patches were not touched. All were applied properly -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 1382191] perl-Mock-Sub-1.07 is available

https://bugzilla.redhat.com/show_bug.cgi?id=1382191 --- Comment #2 from Upstream Release Monitoring --- Created attachment 1207727 --> https://bugzilla.redhat.com/attachment.cgi?id=1207727=edit Rebase-helper rebase-helper-debug.log log file.

  1   2   3   >