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

I'm just thinking out loud here, but, given that rpm-ostree does not use grubby, and we do have the Bootloader Spec, and no other distro uses grubby, would it be prudent to take a really hard look at whether grubby is still a path we want to walk? If it is, then more work obviously needs to

Re: Screenshots with Wayland and Dual Displays

On Thu, Oct 6, 2016 at 3:59 PM, Jeffrey Ollie wrote: > I just noticed that I can't take a screenshot of anything on the secondary > display when using two displays - you just get a transparent PNG. In fact, > if you try and grab an area that spans the displays it'll capture the

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

On Thu, Oct 6, 2016 at 3:17 PM, Kevin Fenzi wrote: > On Thu, 6 Oct 2016 17:05:45 -0400 > Eric Griffith wrote: > >> Can anyone answer this relatively simple question: "Why grubby?" I've >> seen a number of discussions on various topics surrounding the boot

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:57:20PM -, Peter Larsen wrote: > > 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

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

On Fri, 2016-10-07 at 01:25 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > Huh - that's handy, and I did not actually know --nopostun (something > > new every day, etc.). It does involve including instructions on how to > > find the package, though, which would inevitably go stale as it

Re: /sbin/nologin in /etc/shells

Once upon a time, Andrew Toskin said: > But now I'm sorta curious about the opposite situation: What's the use case > for blocking a user from accessing their account, rather than just deleting > the account altogether? There are lots of reasons. For example, if someone is

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

Adam Williamson wrote: > Huh - that's handy, and I did not actually know --nopostun (something > new every day, etc.). It does involve including instructions on how to > find the package, though, which would inevitably go stale as it moves > from u-t to stable. Still, thanks. Seeing how this is

[389-devel] Jenkins build is back to normal : 389-DS-COMMIT #112

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

Re: /sbin/nologin in /etc/shells

>My question is: If it were really important to make sure the user could no >longer access the system at all, why not just delete the account? Deleting the >user does not >(necessarily) delete their data, so what's the use case for >keeping the account at all in such a situation? In my

Re: Fedora 25 Beta status is GO, release on Oct 11, 2016

On Thu, 2016-10-06 at 21:22 +, Jeremy Newton wrote: > At risk of asking a redundant question, I'm assuming Wayland is still a go? > IIRC the contingency deadline was the beta. Workstation still uses Wayland by default in the Beta, yep. -- Adam Williamson Fedora QA Community Monkey IRC: adamw

Screenshots with Wayland and Dual Displays

I just noticed that I can't take a screenshot of anything on the secondary display when using two displays - you just get a transparent PNG. In fact, if you try and grab an area that spans the displays it'll capture the screen from the primary display properly while the area from the secondary

Re: Docker/Libvirt networking issue / bug?

maybe I'm come with not right answer , I think that depend by network configuration over internet and routing process over applications. so will not be any conflict. I'm right? > Both docker and libvirt use iptables to direct traffic in various ways. They > may well be in conflict 2016-10-06

Re: /sbin/nologin in /etc/shells

Er, let me clarify: Much of the discussion here, as I see it, has been about how to preserve a user account, but block user access to that account. My question is: If it were really important to make sure the user could no longer access the system at all, why not just delete the account?

Re: /sbin/nologin in /etc/shells

We've discussed how and whether it's best practice to disallow a user from logging into an account they previously had access to. But now I'm sorta curious about the opposite situation: What's the use case for blocking a user from accessing their account, rather than just deleting the account

Re: Fedora 25 Beta status is GO, release on Oct 11, 2016

At risk of asking a redundant question, I'm assuming Wayland is still a go? IIRC the contingency deadline was the beta. I ask because it does not appear to be a part of the changeset, yet this FEDCo ticket seems to suggest otherwise: https://fedorahosted.org/fesco/ticket/1615

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

On Thu, 6 Oct 2016 17:05:45 -0400 Eric Griffith wrote: > Can anyone answer this relatively simple question: "Why grubby?" I've > seen a number of discussions on various topics surrounding the boot > loader that all seem to devolve into "We would love to support that, > but

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

On Thu, 2016-10-06 at 17:05 -0400, Eric Griffith wrote: > Can anyone answer this relatively simple question: "Why grubby?" I've > seen a number of discussions on various topics surrounding the boot > loader that all seem to devolve into "We would love to support that, > but grubby doesn't, so we

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

Can anyone answer this relatively simple question: "Why grubby?" I've seen a number of discussions on various topics surrounding the boot loader that all seem to devolve into "We would love to support that, but grubby doesn't, so we can't." At what point does the maintenance burden of using

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

Adam Williamson wrote: > Next time maybe I'll just say 'screw this' and go play golf instead, if this > is the thanks I get for trying to help people out. Others have thanked you, actually, but parts of this email chain have gotten a little heated, so I guess it's worth repeating: Thanks for

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

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

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

On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > > What exactly would you have had me do? Just sit on this and pretend > > there was no bug and when we saw more and more people come into #fedora > > and complain about it, tell them the risk was minimal so they

Re: Systemd Security

- Original Message - > From: "Tomasz Torcz" > To: devel@lists.fedoraproject.org > Sent: Thursday, October 6, 2016 3:11:36 PM > Subject: Re: Systemd Security > > On Thu, Oct 06, 2016 at 04:05:34PM -0400, Ivan Chavero wrote: > > > On Thu, Oct 06, 2016 at 12:33:30PM

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

On Wed, Oct 05, 2016 at 03:26:10PM -0700, Japheth Cleaver wrote: > I don't know what the dnf equivalent is, but isn't that precisely what the > 'needs-restarting' command provided? DNF has the tracer plugin for doing exactly that, including printing a list of commands to restart the affected

[EPEL-devel] Using devtoolset for EPEL builds

Hi, I need/want/would like to build new node 6 for EL6, but gcc is too old. For that reason, I'd like to use devtoolset-4-gcc, but the build fails (obviously) because the package doesn't exist. So, is there a way to make that work somehow? I am not sure about enabling external repos during

Re: Fedora 25 Beta 1.1 compose check report

On Thu, 2016-10-06 at 15:11 -0500, Dennis Gilmore wrote: > For the sake of clarity (It was resolved on IRC) we deliver all artifacts as > part of teh nightly branched/rawhide composes, the atomic host production > deliverables are only delivered via the two week atomic host process and not >

[Bug 807793] Please build pcsc-perl for EPEL6

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

Re: Systemd Security

- Original Message - > From: "Lennart Poettering" > To: "Development discussions related to Fedora" > > Sent: Thursday, October 6, 2016 11:58:06 AM > Subject: Re: Systemd Security > > On Thu, 06.10.16 12:33, Ivan Chavero

Re: Fedora 25 Beta 1.1 compose check report

676919782db4ef29d6bf5ce6e79f9dbe91ad95cbe7155682a73b09d0" }, > "disc_count": 1, > "disc_number": 1, > "format": "raw.xz", > "implant_md5&quo

Re: Systemd Security

Once upon a time, Ivan Chavero said: > I'm not hijacking any thread, I STARTED this thread No, you didn't start a thread. You posted a reply to an unrelated message (the subject of that message was "Re: Fedora 25 Beta 1.1 compose check report"). When you want to start a

Re: Systemd Security

On Thu, 2016-10-06 at 16:05 -0400, Ivan Chavero wrote: > I'm not hijacking any thread, I STARTED this thread (BTW, just searched for > emails > with the "Systemd Security" subject in this mailing list and didn't find any > immediate matches) because i have an honest concern for Systemd Security

Re: Systemd Security

On Thu, Oct 06, 2016 at 04:05:34PM -0400, Ivan Chavero wrote: > > On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wrote: > > > > > > I found this article stating some alarming claims about systemd > > > security, are this claims true? > > > > > > > First of all, do not hijack threads.

Re: Systemd Security

- Original Message - > From: "Tomasz Torcz" > To: devel@lists.fedoraproject.org > Sent: Thursday, October 6, 2016 11:53:23 AM > Subject: Re: Systemd Security > > On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wrote: > > > > I found this article stating

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

On Thu, Oct 06, 2016 at 08:20:34AM -0700, Adam Williamson wrote: > On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote: > > rpm -Uvh --nodeps --nopostun \ > > > > http://$MIRROR/updates/testing/25/x86_64/s/systemd-udev-231-8.fc25.x86_64.rpm > > Huh - that's handy, and I did not actually know

Re: Fedora 25 Beta Release Readiness Meeting, Thursday, October 6th @ 19:00 UTC

Hi everyone, the F25 Beta Readiness meeting has shown readiness of all teams for the F25 Beta release. There were no major issues reported during the meeting and all teams stated we are ready to release the F25 Beta as planned, on October 11th, 2016 at 14:00 UTC. For more details please check the

Re: Docker/Libvirt networking issue / bug?

On Thu, Oct 06, 2016 at 02:02:09PM -0500, Dan Williams wrote: > On Thu, 2016-10-06 at 12:39 -0600, Nathanael D. Noblet wrote: > > On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote: > > > > > > I rarely mess with docker, but I expect that the docker0 bridge has > > > an ip > > > address on it

Re: Docker/Libvirt networking issue / bug?

On Thu, 2016-10-06 at 12:39 -0600, Nathanael D. Noblet wrote: > On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote: > > > > I rarely mess with docker, but I expect that the docker0 bridge has > > an ip > > address on it which may conflict with the one on libvirt > > bridge.  That is to > > say,

Fedora Rawhide-20161006.n.0 compose check report

Missing expected images: Kde live i386 Workstation live i386 Server dvd i386 Server boot x86_64 Server dvd x86_64 Kde live x86_64 Cloud_base raw-xz x86_64 Cloud_base raw-xz i386 Server boot i386 Atomic raw-xz x86_64 Kde raw-xz armhfp Minimal raw-xz armhfp Workstation live x86_64 Failed openQA

Re: Docker/Libvirt networking issue / bug?

On Thu, 2016-10-06 at 14:28 -0400, Neil Horman wrote: > I rarely mess with docker, but I expect that the docker0 bridge has > an ip > address on it which may conflict with the one on libvirt > bridge.  That is to > say, if they are on the same subnet, and the route for the docker0 > bridge takes >

Re: Docker/Libvirt networking issue / bug?

On Thu, Oct 06, 2016 at 11:08:21AM -0600, Nathanael D. Noblet wrote: > Hello, > >   I have an issue that likely needs a bug or something to fix but I'm > not sure which component is at fault. So I'm writing here in the hopes > that someone will know where to point me. > >   I have a F24

Fedora 25 Beta status is GO, release on Oct 11, 2016

At the Fedora 25 Beta Go/No-Go Meeting [1][2] that just ended, has been agreed by QA, Release Engineering and Development representatives to go live with the Fedora 25 Beta [3]. Fedora 25 Beta will be publicly available on Oct 11, 2016. Meeting details can be seen here: [1] Minutes:

Re: Fedora 25 Beta 1.1 compose check report

, "checksums": { "sha256": "79e98c18676919782db4ef29d6bf5ce6e79f9dbe91ad95cbe7155682a73b09d0" }, "disc_count": 1, "disc_number": 1,

Fedora 25-20161006.n.0 compose check report

Missing expected images: Kde live i386 Workstation live i386 Server dvd i386 Server boot x86_64 Server dvd x86_64 Kde live x86_64 Cloud_base raw-xz x86_64 Xfce raw-xz armhfp Cloud_base raw-xz i386 Server boot i386 Atomic raw-xz x86_64 Minimal raw-xz armhfp Workstation live x86_64 Failed openQA

Re: Call for help contacting contributor: spike

On Thu, Oct 06, 2016 at 07:20:55PM +0200, spike wrote: > On 05.10.2016 12:44, Pierre-Yves Chibon wrote: > > It has been a month, more than I expected, so I asked FESCo to consider the > > user > > spike MIA: https://fedorahosted.org/fesco/ticket/1632 > > Sorry, must have missed that mail. Just

Re: Using devtoolset for EPEL builds

On Thu, Oct 6, 2016 at 10:32 AM, Zuzana Svetlikova wrote: > Hi, > > I need/want/would like to build new node 6 for EL6, but gcc is too old. > For that reason, I'd like to use devtoolset-4-gcc, but the build fails > (obviously) because the package doesn't exist. > > So, is

Re: Call for help contacting contributor: spike

On 05.10.2016 12:44, Pierre-Yves Chibon wrote: > It has been a month, more than I expected, so I asked FESCo to consider the > user > spike MIA: https://fedorahosted.org/fesco/ticket/1632 Sorry, must have missed that mail. Just changed my Bugzilla EMail address back to what is was.

Docker/Libvirt networking issue / bug?

Hello,   I have an issue that likely needs a bug or something to fix but I'm not sure which component is at fault. So I'm writing here in the hopes that someone will know where to point me.   I have a F24 Workstation where I've been using libvirt/qemu VMs for development for awhile now. It works

Many directories without owning packages

Hello, I was surprised to see /usr/share/texlive on my system although I remembered very well removing it months ago. It turned out to be caused by two rpmsave files, although some *empty* directories weren't removed: $ find /usr/share/texlive/ /usr/share/texlive/ /usr/share/texlive/texmf-dist

Re: Systemd Security

On Thu, 06.10.16 12:33, Ivan Chavero (ichav...@redhat.com) wrote: > Setting a umask of 0 means that, by default, any file created by systemd > will be world-readable and -writable. Systemd defines a macro called > RUN_WITH_UMASK > which is used to temporarily set a more restrictive umask when

Re: Systemd Security

On Thu, Oct 06, 2016 at 12:33:30PM -0400, Ivan Chavero wrote: > > I found this article stating some alarming claims about systemd > security, are this claims true? > First of all, do not hijack threads. If you want to start something new, start it, and do not reply to unrelated thread.

Schedule for Friday's FESCo Meeting (2016-10-07)

Following is the list of topics that will be discussed in the FESCo meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-10-07 16:00 UTC' Links to all tickets below

Systemd Security

I found this article stating some alarming claims about systemd security, are this claims true? If so, as developers should we be hardening systemd? It states stuff like this: " Systemd's "we don't make mistakes" attitude towards security can be seen in other places, such as this code from

Using devtoolset for EPEL builds

Hi, I need/want/would like to build new node 6 for EL6, but gcc is too old. For that reason, I'd like to use devtoolset-4-gcc, but the build fails (obviously) because the package doesn't exist. So, is there a way to make that work somehow? I am not sure about enabling external repos during

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

On Thu, Oct 6, 2016 at 7:43 AM, Tomasz Kłoczko wrote: > So how problem of consistent upgrade have been solved on Solaris using ZFS > and IPS? > ZFS has ability to create snapshot of the vol (RO resource) and create on > top of the shapshot clone (RW resource). > Whole

[Bug 1380152] perl-HTTP-Tiny 0.068 pulls in lots of new dependencies including Xorg

https://bugzilla.redhat.com/show_bug.cgi?id=1380152 --- Comment #14 from Petr Pisar --- That's also an option. And the more I think about all the involved packages, the more it looks like the best solution. -- You are receiving this mail because: You are on the CC list for

Re: Fedora 25 Beta 1.1 compose check report

On Thu, Oct 6, 2016 at 5:30 PM, Adam Williamson wrote: > On Thu, 2016-10-06 at 10:26 -0500, Dennis Gilmore wrote: >> On Wednesday, October 5, 2016 11:08:10 PM CDT Fedora compose checker wrote: >> > Missing expected images: >> > >> > Cloud_base raw-xz i386 >> > Atomic

[Bug 1380152] perl-HTTP-Tiny 0.068 pulls in lots of new dependencies including Xorg

https://bugzilla.redhat.com/show_bug.cgi?id=1380152 --- Comment #13 from Paul Howarth --- How about just making perl(Business::ISBN) a Suggests: instead of a Requires: from perl-URI? I think that's how URI's upstream considers it, certainly not as a hard dependency. -- You

Re: Fedora 25 Beta 1.1 compose check report

On Thu, 2016-10-06 at 10:26 -0500, Dennis Gilmore wrote: > On Wednesday, October 5, 2016 11:08:10 PM CDT Fedora compose checker wrote: > > Missing expected images: > > > > Cloud_base raw-xz i386 > > Atomic raw-xz x86_64 > > > These are not expected, they are not things configured to be built in

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

On Thu, 2016-10-06 at 10:39 +0200, Hans de Goede wrote: > > So I like the idea, I do propose to simply re-use most of > the blocker bug process for this, rather then inventing yet > another process. I guess this could even be integrated and > the way to get bugs on the list would be to propose

Re: [Base] adopting the Docker base image into Atomic WG

On Wednesday, October 5, 2016 2:41:50 PM CDT Colin Walters wrote: > 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'

Re: Fedora 25 Beta 1.1 compose check report

On Wednesday, October 5, 2016 11:08:10 PM CDT Fedora compose checker wrote: > Missing expected images: > > Cloud_base raw-xz i386 > Atomic raw-xz x86_64 These are not expected, they are not things configured to be built in the compose. Dennis signature.asc Description: This is a digitally

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

On Thu, 2016-10-06 at 08:20 -0700, Adam Williamson wrote: > On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote: > Adam Williamson wrote: > What exactly would you have had me do? Just sit on this and pretend > there was no bug and when we saw more and more people come into #fedora > and complain

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

On Thu, 2016-10-06 at 10:18 +0200, Kevin Kofler wrote: Adam Williamson wrote: What exactly would you have had me do? Just sit on this and pretend there was no bug and when we saw more and more people come into #fedora and complain about it, tell them the risk was minimal so they should just suck

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

06.10.2016, 08:23, "Pierre-Yves Chibon": > 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.)

jplesnik pushed to perl-DateTime-TimeZone (f23). "Add BR perl(DateTime) to run more tests"

From 3b52f76e5a74482f1c8b156d68b83e95aec3e195 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova Date: Thu, 6 Oct 2016 16:17:05 +0200 Subject: Add BR perl(DateTime) to run more tests --- perl-DateTime-TimeZone.spec | 9 - 1 file changed, 8 insertions(+), 1 deletion(-)

jplesnik pushed to perl-DateTime-TimeZone (f24). "Add BR perl(DateTime) to run more tests"

From a76fdeb57b782663b422bbb8c389dcb3ea09eaed Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova Date: Thu, 6 Oct 2016 16:11:59 +0200 Subject: Add BR perl(DateTime) to run more tests --- perl-DateTime-TimeZone.spec | 9 - 1 file changed, 8 insertions(+), 1 deletion(-)

jplesnik pushed to perl-DateTime-TimeZone (f25). "Add BR perl(DateTime) to run more tests"

From a08db4e7e809fa5a7d566048e9922cabef53c04c Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova Date: Thu, 6 Oct 2016 15:26:03 +0200 Subject: Add BR perl(DateTime) to run more tests --- perl-DateTime-TimeZone.spec | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-)

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

On Thu, Oct 06, 2016 at 12:44:02PM +, Zbigniew Jędrzejewski-Szmek wrote: > Maybe we should standardize the prefix for git commits: "taskotron: " > or "tests: " or whatever, so it's easy to stop in git history. That'll have to be automated somehow or I don't think people will remember. --

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

Hi every one, Reading all ideas about solving issues with upgrading systems from working systems are more or less ideas of ad choc solving some issues or even more or less reinventing the wheel. IMO all those ideas will not solve anything and will only increase total level of entropy. After this

jplesnik pushed to perl-DateTime-TimeZone (master). "Add BR perl(DateTime) to run more tests"

From e66a16eb8a449797e995ab660d6e4c3700cae542 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova Date: Thu, 6 Oct 2016 15:26:03 +0200 Subject: Add BR perl(DateTime) to run more tests --- perl-DateTime-TimeZone.spec | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-)

Broken dependencies: perl-Alien-ROOT

perl-Alien-ROOT has broken dependencies in the rawhide tree: On aarch64: perl-Alien-ROOT-5.34.36.1-1.fc26.noarch requires root-core Please resolve this as soon as possible. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To

Broken dependencies: perl-Data-Alias

perl-Data-Alias has broken dependencies in the rawhide tree: On aarch64: perl-Data-Alias-1.20-2.fc24.aarch64 requires libperl.so.5.22()(64bit) perl-Data-Alias-1.20-2.fc24.aarch64 requires perl(:MODULE_COMPAT_5.22.1) On x86_64: perl-Data-Alias-1.20-2.fc24.x86_64 requires

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

In theory, I like this idea. In practice, Kevin Kofler is probably right. Unless there is a big hammer, bugs don't get fixed in many cases. So I think the solution should be different: gfx team needs more manpower so they can handle bug reports. Right now, for some packages bugzilla serves

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

On Wed, Oct 5, 2016 at 8:43 PM, Adam Williamson wrote: > > OK, from now on when I see bugs causing serious real world consequences > for multiple real world reporters I'll just shut up and pretend it's > not happening, shall I? Wouldn't want to be all 'alarmist' about

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

On Wed, Oct 05, 2016 at 12:16:32PM -0600, Tim Flink wrote: > 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' > > >

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

Adam Williamson writes: 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

berrange pushed to perl-Sys-Virt (master). "Update to 2.3.0 release"

From c1a1484fb99663c2d6e132eac20ab9efa1bea6bd Mon Sep 17 00:00:00 2001 From: "Daniel P. Berrange" Date: Thu, 6 Oct 2016 12:04:24 +0100 Subject: Update to 2.3.0 release --- perl-Sys-Virt.spec | 5 - sources| 2 +- 2 files changed, 5 insertions(+), 2

berrange uploaded Sys-Virt-2.3.0.tar.gz for perl-Sys-Virt

95546825ea6962c5f632c2089bcd9aa9 Sys-Virt-2.3.0.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Sys-Virt/Sys-Virt-2.3.0.tar.gz/md5/95546825ea6962c5f632c2089bcd9aa9/Sys-Virt-2.3.0.tar.gz ___ perl-devel mailing list --

Re: [SO-NAME BUMP] jsoncpp 1.7.7 comes to rawhide (and maybe to fc25)

Am 06.10.2016 um 11:09 schrieb Igor Gnatenko: On Tue, Oct 4, 2016 at 10:18 AM, Björn Esser wrote: Am 03.10.2016 um 06:10 schrieb Björn Esser: Chain-build is running: https://koji.fedoraproject.org/koji/taskinfo?taskID=15917326 Am 03.10.2016 um 05:38 schrieb Björn Esser:

[EPEL-devel] Reminder: Red Hat Enterprise Linux 5 Six-Month Retirement Notice

Just a reminder that there's 6 months left of the standard RHEL-5 life-cycle so 6 months left of EPEL-5. https://rhn.redhat.com/errata/RHSA-2016-1990.html ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

Re: [SO-NAME BUMP] jsoncpp 1.7.7 comes to rawhide (and maybe to fc25)

On Tue, Oct 4, 2016 at 10:18 AM, Björn Esser wrote: > Am 03.10.2016 um 06:10 schrieb Björn Esser: >> >> Chain-build is running: >> https://koji.fedoraproject.org/koji/taskinfo?taskID=15917326 >> >> >> Am 03.10.2016 um 05:38 schrieb Björn Esser: >>> >>> I'm upgrading jsoncpp to

Re: [HEADS UP] libtimidity-0.2.0 comes to rawhide

On Tue, Oct 4, 2016 at 10:42 AM, Igor Gnatenko wrote: > Hi, > > I'm preparing update for new version. According to release notes[0], > there is only API additions and couple of changes. I will rebuild all > dependent packages: > * gstreamer-plugins-bad-free Rebuilt and patch

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

The following Fedora EPEL 6 Security updates need testing: Age URL 455 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 449 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 381

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

As for the KDE part: Adam Williamson wrote: > The 'standard Fedora solution' for KDE is...well I don't know, The standard updater on the KDE Spin is plasma-pk-updates. The other tools can also do updates (or at least they claim to be able to), but the applet in the system tray that

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

https://bugzilla.redhat.com/show_bug.cgi?id=1381897 --- Comment #4 from Fedora Update System --- perl-Messaging-Message-1.6.1-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

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

https://bugzilla.redhat.com/show_bug.cgi?id=1381896 --- Comment #3 from Fedora Update System --- perl-No-Worries-1.3-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

pghmcfc pushed to perl-Modern-Perl (master). "Update to 1.20161005 (..more)"

From 3f34ff3babc2efa40fb60cfba0c467546e2724f2 Mon Sep 17 00:00:00 2001 From: Paul Howarth Date: Thu, 6 Oct 2016 08:41:34 +0100 Subject: Update to 1.20161005 - New upstream release 1.20161005 - Updated for 2016 release - Added support for 5.24 - Add back in the package

pghmcfc pushed to perl-Modern-Perl (perl-Modern-Perl-1.20161005-1.fc26). "Update to 1.20161005 (..more)"

This commit already existed in another branch. http://pkgs.fedoraproject.org/cgit/perl-Modern-Perl.git/commit/?h=perl-Modern-Perl-1.20161005-1.fc26=3f34ff3babc2efa40fb60cfba0c467546e2724f2 ___ perl-devel mailing list --

pghmcfc pushed to perl-Modern-Perl (perl-Modern-Perl-1.20161005-1.fc25). "Update to 1.20161005 (..more)"

From 3f34ff3babc2efa40fb60cfba0c467546e2724f2 Mon Sep 17 00:00:00 2001 From: Paul Howarth Date: Thu, 6 Oct 2016 08:41:34 +0100 Subject: Update to 1.20161005 - New upstream release 1.20161005 - Updated for 2016 release - Added support for 5.24 - Add back in the package

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

Hi, On 05-10-16 20:30, Bruno Wolff III wrote: 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

pghmcfc uploaded Modern-Perl-1.20161005.tar.gz for perl-Modern-Perl

660fb7d591a84825ee43475ab5b52889 Modern-Perl-1.20161005.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Modern-Perl/Modern-Perl-1.20161005.tar.gz/md5/660fb7d591a84825ee43475ab5b52889/Modern-Perl-1.20161005.tar.gz ___ perl-devel mailing

pghmcfc pushed to perl-Modern-Perl (f25). "Update to 1.20161005 (..more)"

From 3f34ff3babc2efa40fb60cfba0c467546e2724f2 Mon Sep 17 00:00:00 2001 From: Paul Howarth Date: Thu, 6 Oct 2016 08:41:34 +0100 Subject: Update to 1.20161005 - New upstream release 1.20161005 - Updated for 2016 release - Added support for 5.24 - Add back in the package

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

On 10/05/2016 03:00 AM, Adam Williamson wrote: On Tue, 2016-10-04 at 20:43 -0400, Sam Varshavchik wrote: But ordinary regular app updates will happily run on cruise control, without bringing the system down into single user mode. If Android can do that, I see no reason why Fedora can't, either.

jplesnik pushed to perl-Perl-Tidy-Sweetened (f25). "1.12 bump"

From 1d202b311ba7d3b6b2000ea898a5f5a9e8b4401e Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova Date: Thu, 6 Oct 2016 08:54:25 +0200 Subject: 1.12 bump --- .gitignore| 1 + perl-Perl-Tidy-Sweetened.spec | 9 ++--- sources | 2 +-

jplesnik pushed to perl-Perl-Tidy-Sweetened (master). "1.12 bump"

From ae8ae610fe8f4f077911b6c9a3c7a544188734a8 Mon Sep 17 00:00:00 2001 From: Jitka Plesnikova Date: Thu, 6 Oct 2016 08:54:25 +0200 Subject: 1.12 bump --- .gitignore| 1 + perl-Perl-Tidy-Sweetened.spec | 9 ++--- sources | 2 +-

jplesnik uploaded Perl-Tidy-Sweetened-1.12.tar.gz for perl-Perl-Tidy-Sweetened

998c206f189a7802299798744f6e7a54 Perl-Tidy-Sweetened-1.12.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Perl-Tidy-Sweetened/Perl-Tidy-Sweetened-1.12.tar.gz/md5/998c206f189a7802299798744f6e7a54/Perl-Tidy-Sweetened-1.12.tar.gz ___

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

On 10/06/2016 05:45 AM, Adam Williamson wrote: 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

ppisar pushed to perl-Clownfish (master). "0.6.0.3 bump"

From 6436d5d42d72d44d15b6cf937de7002f0e7bc39a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= Date: Thu, 6 Oct 2016 07:48:36 +0200 Subject: 0.6.0.3 bump --- .gitignore | 1 + perl-Clownfish.spec | 5 - sources | 2 +- 3 files

ppisar uploaded Clownfish-0.6.0.3.tar.gz for perl-Clownfish

89603284f5662d94034efb4dc4b113e4 Clownfish-0.6.0.3.tar.gz http://pkgs.fedoraproject.org/lookaside/pkgs/perl-Clownfish/Clownfish-0.6.0.3.tar.gz/md5/89603284f5662d94034efb4dc4b113e4/Clownfish-0.6.0.3.tar.gz ___ perl-devel mailing list --

[Bug 1078438] Templated types are causing " Could not find a typemap for C type"

https://bugzilla.redhat.com/show_bug.cgi?id=1078438 Petr Pisar changed: What|Removed |Added CC|perl-devel@lists.fedoraproj |

[Bug 1078438] Templated types are causing " Could not find a typemap for C type"

https://bugzilla.redhat.com/show_bug.cgi?id=1078438 Petr Pisar changed: What|Removed |Added Keywords||FastFix -- You are

  1   2   >