Re: Fedora for Web Development fail
Hi Máirín, For several years now I've been using VMs with backing files to do what you're trying to achieve. It's basically what Dusty Mabe describes in the last paragraph of this article: https://dustymabe.com/2015/01/11/qemu-img-backing-files-a-poor-mans-snapshotrollback/ Using virt-manager, I set up my base VM exactly the way I want it. Next, I use qemu-img to create as many additional VMs as I need for each project. The disk space they consume is just their delta from the base image. The new files can then be imported into virt-manager and used as regular images, as long as the base image remains unchanged. Use of the terminal is only required when making the snapshots: qemu-img create -f qcow2 -o backing_file=base_env.img test01.img It's not as involved or elegant as using vagrant and ansible, but it's simple and if you are already familiar with virt-manager, you do not need to get acquainted with anything else. Best regards, Alex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora Atomic Host Two Week Release Announcement: 28.20180923.0
On Tue, Sep 25, 2018 at 8:49 PM wrote: > > > A new Fedora Atomic Host update is available via an OSTree update: > > Version: 28.20180923.0 > Commit(x86_64): > 8b82902a0ca203645e9e288b8a0bbf9fe525749ec67cd674e6715daa64e5b7dd > Commit(aarch64): > 9303c782b619bfeccfc8b0fb86a16ebf40b48c7c65e08d16c999b1618fd8b417 > Commit(ppc64le): > d789fe23cb4bba0d5d24fd345358d122b8caef97ab2572ad23292025823888ff > > > We are releasing images from multiple architectures but please note > that x86_64 architecture is the only one that undergoes automated > testing at this time. > > Existing systems can be upgraded in place via e.g. `atomic host upgrade`. > > Corresponding image media for new installations can be downloaded from: > > https://getfedora.org/en/atomic/download/ > > Alternatively, image artifacts can be found at the following links: > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0.aarch64.qcow2 > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0.aarch64.raw.xz > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180923.0.iso > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0.ppc64le.qcow2 > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0.ppc64le.raw.xz > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180923.0.iso > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0.x86_64.qcow2 > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0.x86_64.raw.xz > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180923.0.x86_64.vagrant-libvirt.box > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180923.0.x86_64.vagrant-virtualbox.box > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180923.0.iso > > Respective signed CHECKSUM files can be found here: > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0-aarch64-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180923.0-aarch64-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0-ppc64le-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180923.0-ppc64le-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0-x86_64-CHECKSUM > https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180923.0-x86_64-CHECKSUM > > For direct download, the "latest" targets are always available here: > x86_64: > https://getfedora.org/atomic_qcow2_x86_64_latest > https://getfedora.org/atomic_raw_x86_64_latest > https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest > https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest > https://getfedora.org/atomic_dvd_ostree_x86_64_latest > > aarch64: > https://getfedora.org/atomic_qcow2_aarch64_latest > https://getfedora.org/atomic_raw_aarch64_latest > https://getfedora.org/atomic_dvd_ostree_aarch64_latest > > ppc64le: > https://getfedora.org/atomic_qcow2_ppc64le_latest > https://getfedora.org/atomic_raw_ppc64le_latest > https://getfedora.org/atomic_dvd_ostree_ppc64le_latest > > Filename fetching URLs are available here: > x86_64: > https://getfedora.org/atomic_qcow2_x86_64_latest_filename > https://getfedora.org/atomic_raw_x86_64_latest_filename > https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename > https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename > https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename > > aarch64: > https://getfedora.org/atomic_qcow2_aarch64_latest_filename > https://getfedora.org/atomic_raw_aarch64_latest_filename > https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename > > ppc64le: >
Re: Fedora for Web Development fail
I just tried it. I was able to connect to remote hypervisor, it showed my VM - pretty impressive. It was a little flaky in that when I right clicked to view properties of the VM it hung (with a, wait / force quit dialog popping up) but I was eventually able to load the dialog. It seems to allow memory configuration and snapshotting, but not storage. The latter is an issue bc the Fedora default image is 4 GB and that wasn't enough for my env, I'm currently trying to deal with how to resize the file system (was able to make image being using libvirt commands.) FWIW! Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Add release announcement post to Go/No-Go criteria
On Tue, Sep 25, 2018 at 02:24:16PM -0700, Kevin Fenzi wrote: > I'm prefer to add a new milestone of 'day before release' and put it > there. I think after the 'go' some folks who would be helpful in making > the announcement have more time to devote to it. Also, it would seem sad > to me to be 'go' except for an announcement, and slip a week. "Day before release" is probably too late. Friday before release? -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
So the environment I'm trying to set up involves a backend that consists of three separate containers, and the web front end is separate from that. Because setting up the environment is a difficult task, I'd like it in a VM so I can clone it once it's configured so that I can reproduce it without having to do everything from scratch. And I will just put this out there - the upstream I'm working with, the scripts / instructions are written for OS X, Ubuntu, and docker. I've already dealt with a few snags once I got the base Fedora VM set up - issues with networking (no ifconfig on the base image which is like typing on a keyboard wearing mittens for me), Docker by default installed via Fedora RPM *not* configured with the --selinux-enabled flag in the systemd service file, SELinux avc denials even with that enabled, and now some other issues I'm going to spend hours today figuring out I'm assuming. Once I get it working as scripted by upstream, I would like to get it working with cri-o & friends instead of docker. This is not the kind of work I'd want to do on my baremetal machine because its my primary workstation and I don't want to screw. I hope it makes sense, my logic here. Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Hi Randy, I did consider Vagrant but there are a few issues with it: - There is no GUI for it that I can find. I just like GUIs, especially for this sort of work that I might do for a stretch at a time and then not have to do for months afterwards and have to relearn next time. - I have had - I have been told coincidentally and with just terrible luck - horrible experiences with vagrant. The very first time I tried to use it, there was some kind of bug with the kernel support for it - I don't remember the details - but it amounted to a race condition that with my particular hardware somehow always resulted in a crashing and unworkable environment that ended up eating 2 full workdays to debug. It pretty much sucked. The other experience I've had with it is at a couple of hackfests at conferences, where it involved downloading large files the wifi couldn't handle and passing around USB keys, taking 30 min or more to get the base environment running, and it eating up disk space and generally making my system run slow for weeks afterwards (I think someone trying to help me get it working at one point set it to start on boot which I didn't realize until weeks later after frequently losing my desktop stability to OOM killing.) - My use case here is I have a big beefy workstation, and a few different laptops. I don't want to have to set the environment up multiple times or be moving large files around. I just want to set up the environment once, and be able to ssh into it from wherever. I'm not too worried about damage bc I can clone the VM once I have everything working and setup, and everything else should be in git anyway. Does that make sense or am I trying to fit a square peg in a round hole here? Cheers, ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Semi-serious proposal: drop all optional entries from comps
On Tue, Sep 25, 2018 at 08:17:18AM +0200, Vít Ondruch wrote: > rubygem-rails (which already exists and has its purpose no matter if > there are comps or not) via Suggests for example. The only issue AFAIK > is there is no real support for Suggests in DNF :/ What would that look like? An interactive mode where you Y/N every suggested package? "Install everything suggested" seems too coarse. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Is there a way to use a vagrant image that works with virt-manager? ~m ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
Dne 26.9.2018 v 13:28 Vít Ondruch napsal(a): > If you these two steps from documentation: > > https://developer.fedoraproject.org/tools/vagrant/vagrant-atlas.html > > the vagrant box appears in virt-manager as another machine. The name of > the machine will be derived from the directory name where the Vagrant > file is located. > > Of course it is not smart to do operations such as destroying the > Vagrant managed VM from virt-manager. OTOH some other operations, such as removing unused vagrant images are doable only by tools such as virt-manager :/ V. > > > V. > > > Dne 26.9.2018 v 13:06 Máirín Duffy napsal(a): >> Is there a way to use a vagrant image that works with virt-manager? >> >> ~m >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Add release announcement post to Go/No-Go criteria
On Tue, Sep 25, 2018 at 06:33:28PM -0300, Eduard Lucena wrote: > Basically, the issue on the announcement is that is tight to the Talking > Points, and almost any team is helping us with that. The Marketing task is Almost *no* team, right? I've seen those posts and crickets in return. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, Sep 25, 2018 at 02:18:50PM -, Máirín Duffy wrote: > - Is running a lightweight local VM for web development a usecase we want to > support? Is it dare I ask important? Yeah. I think we really need to straighten out the Fedora Cloud / Fedora Server image thing. As I understand it, everyone is basically agreed but it's hard to find time to *do*. -- Matthew Miller Fedora Project Leader ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Tue, 2018-09-25 at 17:25 -0400, Josh Boyer wrote: > The conversation > went like this: > > Hey, I'm trying to do this and all the documented Fedora > things are really hard or poorly documented. Is this how Fedora > should work? > Oh, use this thing that *Fedora doesn't produce* in a > manner that *Fedora doesn't document* instead. It's much better! > > That is a really bad anti-pattern. > > If we think Vagrant is better for this kind of work, we should be > actively looking at producing vagrant images instead. Fedora does produce Vagrant images. From the example Vagrantfile I posted in my first reply, you can see that I'm pulling the Vagrantfile from Fedora (anyone who does this should really add that checksum line too): https://github.com/fedora-infra/bodhi/blob/3.10.0/Vagrantfile#L13 In addition to the docs that Miro linked, we have also documented it here: https://fedoraproject.org/wiki/Vagrant signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Wed, 2018-09-26 at 11:46 -0400, Randy Barlow wrote: > I ssh to the big system and do all my Vagrant work there. Heh, sorry for so many posts, but I wanted to add to this that it is also possible to point your Vagrantfile at a remote libvirt server. This lets you run Vagrant on your laptop, but have the VM run on some other server. That can be kinda nifty too if you don't want to ssh to the other system for some reason (like if you use an IDE). I personally just work in terminals all day with vim, so I don't do that, but it's possible and might be interesting to you ☺ signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Add release announcement post to Go/No-Go criteria
On Wed, 26 Sep 2018 at 14:44, Brian (bex) Exelbierd wrote: > > > On Tue, Sep 25, 2018 at 11:25 PM Kevin Fenzi wrote: > >> On 09/25/2018 01:35 PM, Ben Cotton wrote: >> > With today's Beta release, the release announcement post for Fedora >> > Magazine was not ready. As a result, the announcement went out a >> > little late and then only due to a drop-everything effort (thanks, >> > stickster!). We have a proposal to add a fourth criterion for the >> > Go/No-Go decision, beginning with F29 Final: >> > >> > 4. The release announcement post for Fedora Magazine is substantially >> complete >> > >> > As a reminder, these are the existing criteria: >> > >> > 1. No remaining blocker bugs >> > 2. Release candidate compose is available >> > 3. Test matrices for [milestone = Alpha, Beta, Final] are fully >> completed >> >> I'm prefer to add a new milestone of 'day before release' and put it >> there. I think after the 'go' some folks who would be helpful in making >> the announcement have more time to devote to it. Also, it would seem sad >> to me to be 'go' except for an announcement, and slip a week. >> > > It is sad. But it is also something we should want. Shipping bits > without telling people how to consume them (docs) or that they exist > (release announcements) is essentially not shipping. We need docs and > release notes to block releases. They are an integral part of attracting > users and contributors. > > regards, > > bex > +1, The magazine article is used by people making reviews of the new Fedora (for example in podcast or videos), I think this is a critical part of the release and we should give ourself sometime to polish them. I hope that having it as a release criterion will allow us to focus on it. If I am not mistaken we experienced the same situation during F28 release cycle so the current situation is far from being ideal. > > >> >> kevin >> >> >> >> ___ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives: >> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >> > > > -- > Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com > Fedora Community Action & Impact Coordinator > @bexelbie | http://www.winglemeyer.org > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Semi-serious proposal: drop all optional entries from comps
Dne 26.9.2018 v 15:51 Matthew Miller napsal(a): > On Tue, Sep 25, 2018 at 08:17:18AM +0200, Vít Ondruch wrote: >> rubygem-rails (which already exists and has its purpose no matter if >> there are comps or not) via Suggests for example. The only issue AFAIK >> is there is no real support for Suggests in DNF :/ > What would that look like? An interactive mode where you Y/N every suggested > package? "Install everything suggested" seems too coarse. > You would have to do something like "dnf install rubygem-rails --including-suggested" (whatever the option would be named, since on some places they are referred as "very weak" while guidelines refer to them as a "hints"). That would be similar to what groupinstall does. And -x to exclude particular packages should still be available. Vít ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Wed, 2018-09-26 at 11:06 +, Máirín Duffy wrote: > Is there a way to use a vagrant image that works with virt-manager? I'll say "sort of" here. If you use vagrant-libvirt, you would use the vagrant CLI to launch/provision the VM, but once it's running you can see it in virt-manager and interact with its console there. You would still want to use the vagrant CLI to destroy it when done otherwise Vagrant will freak out (it freaks out when the state of things is not as expected, which is one of its warts.) So tl;dr; you use vagrant to create/destroy, but can use virt-manager in between if you like. signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora for Web Development fail
On Wed, 2018-09-26 at 11:04 +, Máirín Duffy wrote: > - There is no GUI for it that I can find. I just like GUIs, > especially for this sort of work that I might do for a stretch at a > time and then not have to do for months afterwards and have to > relearn next time. I don't know of a GUI for Vagrant itself, so yeah that's a deficiency. As I noted in my other e-mail, you can use virt-manager for the non- create/destroy actions, but to my knowledge you can't escape writing a little Ruby and using a little bit of CLI. > - I have had - I have been told coincidentally and with just terrible > luck - horrible experiences with vagrant. You aren't alone. I too have had unfun experiences, especially if it gets confused about its state. State is kept in no fewer than three places - in your project dir there's a .vagrant, there's a ~/.vagrant.d, and it keeps some state in libvirt too. If these get out of sync (which can happen if a VM gets destroyed without Vagrant's knowledge) it's super hard to get it working again. I've found that going and just deleting those three places and restarting libvirt can get it back to a clean state, but yeah it's painful. > - My use case here is I have a big beefy workstation, and a few > different laptops. I don't want to have to set the environment up > multiple times or be moving large files around. I just want to set up > the environment once, and be able to ssh into it from wherever. I'm > not too worried about damage bc I can clone the VM once I have > everything working and setup, and everything else should be in git > anyway. FWIW, this is also my use case, but I still use Vagrant. I use a laptop as my workstation, and have the big beefy workstation as a headless server. I ssh to the big system and do all my Vagrant work there. This way my laptop's battery life is way better when I'm on the move, and that big system is faster anyway. Even though I do this, I find it helpful to be able to completely destroy the VM and re-create it, knowing that all the information to re-create it is in git (via the Vagrantfile + Ansible playbook). Before I used it, I would lose time occasionally managing my development VMs, or trying to get them working again if something went wrong. Now when something goes wrong, I don't even bother trying to figure it out - I just destroy and re-create. This is also nice if you want to try out things that might be destructive. Whatever solution you go for, I do recommend you find one that gives you this quality because it will save you time. Using containers would also achieve this goal if that interests you. You can use Vagrant to run your containers too ☺ > Does that make sense or am I trying to fit a square peg in a round > hole here? Yeah makes sense. Vagrant is certainly not perfect and isn't going to fit everyone's needs. I find it overall saves me time and I've spent enough time with it to learn to work around its weird problems so they don't bother me as much anymore. signature.asc Description: This is a digitally signed message part ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Planned Outage - Fedora Production Openshift - 2018-09-27 21:00 UTC
Planned Outage - Fedora Production Openshift - 2018-09-27 21:00 UTC There will be an outage starting at 2018-09-27 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2018-09-27 21:00 UTC' Reason for outage: We will be redeploying our production openshift with more compute nodes, and a number of new features enabled. Affected Services: https://bodhi.fedoraproject.org https://coreos.fedoraproject.org https://greenwave.fedoraproject.org https://waiverdb.fedoraproject.org https://silverblue.fedoraproject.org Ticket Link: https://pagure.io/fedora-infrastructure/issue/7264 Please join #fedora-admin or #fedora-noc on irc.freenode.net or add comments to the ticket for this outage above. signature.asc Description: OpenPGP digital signature ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Semi-serious proposal: drop all optional entries from comps
On Tue, 2018-09-25 at 08:17 +0200, Vít Ondruch wrote: > > Dne 24.9.2018 v 19:32 Adam Williamson napsal(a): > > On Mon, 2018-09-24 at 12:21 +0200, Vít Ondruch wrote: > > > Just FTR, some while ago, I proposed to drop comps entirely: > > > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/ISCIB67JKW7WBC74KA4DSCAP6AZOUY5G/ > > That...doesn't seem like a very serious proposal at all, given that you > > didn't suggest *in any way* how we would replace the critical functions > > it's currently performing. Are you suggesting metapackages? > > Well I proposed "drop comps entirely (or at least trim them down > significantly)". At least the second part is in line with your request I > believe. > > And I am not speaking necessarily about "metapackages". But we should > really start using Recommends more and especially Suggest is unused at > all. E.g. in comps, there is "Ruby on Rails" group installing bunch of > packages. There is no reason to not have these dependencies specified in > rubygem-rails (which already exists and has its purpose no matter if > there are comps or not) via Suggests for example. The only issue AFAIK > is there is no real support for Suggests in DNF :/ How would this work in the identified use case of 'package managers displaying groups of packages for browsing'? Would the package managers have to somehow generate these views on the fly from Suggests? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Packages with cicku as admin or with commit access
On 09/21/2018 12:00 AM, Matthias Runge wrote: > On 20/09/2018 21:30, Jonathan Underwood wrote: >> On Thu, 20 Sep 2018 at 18:17, Jonathan Underwood > >>> In the process of orphaning a few packages lately, I noticed that the >>> user "cicku" (Christopher Meng) still had commit or admin privelidges >>> on the package. That user hasn't been active for a couple of years, >>> and I vaguely remember packages that he owned being orphaned. But, it >>> seems like packages where he was co-maintainer had no changes. >>> >>> Is this desirable for inactive developers? What if their account >>> became compromised? Would it be better if the inactive maintainer >>> process removed priviliges across all packages, rather than only >>> orphaning the packages they own? Well, IMHO, this is to allow the maintainer to come back and resume work without having to re-request access to all their packages. Anyones account could be compromised anytime, I'm not sure inactive people are more at risk. >> I forgot to add this ticket for the relevant non-responsive maintainer >> ticket: https://pagure.io/fesco/issue/1542 > > Yeah, cicku has been inactive for some time, his last build succeeded > more than two years ago. > > However, the ticket suggests, that the non-responsive maintainer process > has not been followed correctly. > > Anyways, there was the FESCO decision to orphan his packages [1], it > seems that didn't happen completely? It did happen. Any package where they were point of contact (Main admin) was changed to 'orphan'. It would be odd to change the point of contact on packages they aren't the main point of contact on. Anyhow, I think we need to revamp the unresponsive maintainer process, but it's unclear to what. Proposals welcome. kevin signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Fedora 29-20180926.n.0 compose check report
No missing expected images. Failed openQA tests: 5/132 (x86_64), 1/24 (i386), 1/2 (arm) ID: 285923 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/285923 ID: 285959 Test: x86_64 Workstation-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/285959 ID: 285975 Test: x86_64 KDE-live-iso desktop_notifications_postinstall URL: https://openqa.fedoraproject.org/tests/285975 ID: 285981 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/285981 ID: 285987 Test: x86_64 universal install_no_swap URL: https://openqa.fedoraproject.org/tests/285987 ID: 286030 Test: x86_64 universal install_blivet_lvmthin@uefi URL: https://openqa.fedoraproject.org/tests/286030 ID: 286069 Test: i386 universal install_scsi_updates_img URL: https://openqa.fedoraproject.org/tests/286069 Soft failed openQA tests: 4/132 (x86_64), 2/24 (i386) (Tests completed, but using a workaround for a known bug) ID: 285917 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/285917 ID: 285918 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/285918 ID: 285943 Test: i386 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/285943 ID: 285944 Test: i386 Server-dvd-iso install_default URL: https://openqa.fedoraproject.org/tests/285944 ID: 285949 Test: x86_64 Workstation-live-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/285949 ID: 286022 Test: x86_64 universal upgrade_server_domain_controller URL: https://openqa.fedoraproject.org/tests/286022 Passed openQA tests: 123/132 (x86_64), 21/24 (i386) Skipped openQA tests: 1 of 158 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Add release announcement post to Go/No-Go criteria
On 09/26/2018 06:55 AM, Matthew Miller wrote: > On Tue, Sep 25, 2018 at 02:24:16PM -0700, Kevin Fenzi wrote: >> I'm prefer to add a new milestone of 'day before release' and put it >> there. I think after the 'go' some folks who would be helpful in making >> the announcement have more time to devote to it. Also, it would seem sad >> to me to be 'go' except for an announcement, and slip a week. > > "Day before release" is probably too late. Friday before release? Possibly, but that just gives the people 1 day after go to put it together... but I guess if they have it all ready before then it would be fine. kevin signature.asc Description: OpenPGP digital signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Proposal: Add release announcement post to Go/No-Go criteria
On Tue, Sep 25, 2018 at 11:25 PM Kevin Fenzi wrote: > On 09/25/2018 01:35 PM, Ben Cotton wrote: > > With today's Beta release, the release announcement post for Fedora > > Magazine was not ready. As a result, the announcement went out a > > little late and then only due to a drop-everything effort (thanks, > > stickster!). We have a proposal to add a fourth criterion for the > > Go/No-Go decision, beginning with F29 Final: > > > > 4. The release announcement post for Fedora Magazine is substantially > complete > > > > As a reminder, these are the existing criteria: > > > > 1. No remaining blocker bugs > > 2. Release candidate compose is available > > 3. Test matrices for [milestone = Alpha, Beta, Final] are fully completed > > I'm prefer to add a new milestone of 'day before release' and put it > there. I think after the 'go' some folks who would be helpful in making > the announcement have more time to devote to it. Also, it would seem sad > to me to be 'go' except for an announcement, and slip a week. > It is sad. But it is also something we should want. Shipping bits without telling people how to consume them (docs) or that they exist (release announcements) is essentially not shipping. We need docs and release notes to block releases. They are an integral part of attracting users and contributors. regards, bex > > kevin > > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexel...@redhat.com | b...@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Orphaning some Java packages
>> Mikolaj Izdebski wrote: >> >> This is exactly what I feared when the modules were first proposed: >> essential packages moving to modules only. >> >> I think this is absolutely a step in the wrong direction. Things like "ant" >> are essential parts of a distribution. They cannot sit in some module with >> arbitrary branches that can be EOLed at any time. >> >> Kevin Kofler As far as I can understand the modules idea and while looking into those yaml files of ant and cmake for instance, I fail see why modules should work without any spec file and therefore also why without rpmbuild. The modules idea seems to be more about how to have a possibility to build a bunch of packages in their own dependency tree for a custom branch (and on which base system that branch should ever work). So in my opinion, modules can never work without any base system built completely from without modules. What I like about modules is that it obsoletes the need to check for the target distribution inside of the spec file (that's now handled with a branch in git). What I don't like is that all dependencies have to get repeated in the yaml file. What real problem do we try to solve? Please calm down and just my 5ct. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
[Bug 1629605] perl-Code-TidyAll-0.71 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1629605 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-Code-TidyAll-0.71-1.fc |perl-Code-TidyAll-0.71-1.fc |30 |30 ||perl-Code-TidyAll-0.71-1.fc ||29 Resolution|--- |ERRATA Last Closed||2018-09-26 16:20:55 --- Comment #3 from Fedora Update System --- perl-Code-TidyAll-0.71-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1625309] perl-Mail-Message-3.007 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1625309 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Mail-Message-3.007-1.f ||c29 Resolution|--- |ERRATA Last Closed||2018-09-26 16:20:02 --- Comment #3 from Fedora Update System --- perl-Mail-Message-3.007-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1628550] perl-BSON-v1.8.0 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1628550 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|perl-BSON-1.8.0-1.fc30 |perl-BSON-1.8.0-1.fc30 ||perl-BSON-1.8.0-1.fc29 Resolution|--- |ERRATA Last Closed||2018-09-26 16:20:29 --- Comment #6 from Fedora Update System --- perl-BSON-1.8.0-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1625310] perl-Mail-Transport-3.003 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1625310 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version||perl-Mail-Transport-3.003-1 ||.fc29 Resolution|--- |ERRATA Last Closed||2018-09-26 16:19:58 --- Comment #3 from Fedora Update System --- perl-Mail-Transport-3.003-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1628413] ctstream-29 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1628413 --- Comment #11 from Fedora Update System --- ctstream-29-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1624942] perl-File-Path-2.16 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1624942 --- Comment #10 from Fedora Update System --- perl-File-Path-2.16-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1632347] perl-MooseX-Getopt-0.74 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1632347 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- perl-MooseX-Getopt-0.74-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-99eb153f14 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1628413] ctstream-29 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1628413 --- Comment #12 from Fedora Update System --- ctstream-29-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[389-devel] 389 DS nightly 2018-09-27 - 91% PASS
https://fedorapeople.org/groups/389ds/ci/nightly/2018/09/27/report-389-ds-base-1.4.0.16-20180926gitc73cd26.fc28.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
[Bug 1630976] EPEL-7 branch for perl-Data-TreeDumper?
https://bugzilla.redhat.com/show_bug.cgi?id=1630976 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #5 from Fedora Update System --- perl-Check-ISA-0.09-7.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 https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-d01a88c839 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1630976] EPEL-7 branch for perl-Data-TreeDumper?
https://bugzilla.redhat.com/show_bug.cgi?id=1630976 --- Comment #6 from Fedora Update System --- perl-Devel-Size-0.82-3.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 https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-d49d91b06c -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[Bug 1630976] EPEL-7 branch for perl-Data-TreeDumper?
https://bugzilla.redhat.com/show_bug.cgi?id=1630976 --- Comment #7 from Fedora Update System --- perl-Data-TreeDumper-0.40-19.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 https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-2db4f7db3a -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 109 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b6c663378c unrtf-0.21.9-8.el6 47 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-f21474267b condor-8.6.11-1.el6 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-130324cf61 gitolite3-3.6.9-1.el6 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-51146daa45 hylafax+-5.6.1-1.el6 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-0d793474b0 mozilla-noscript-10.1.9.6-1.el6 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-8667fe68a8 lcms2-2.8-6.el6 6 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ca7fe27b10 mbedtls-2.7.6-1.el6 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ebecebaa67 python-marshmallow-2.0.0-0.7.gita8b3385.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing gnutls30-3.5.18-1.el6 libmad-0.15.1b-26.el6 php-tcpdf-6.2.25-1.el6 remctl-3.15-1.el6 Details about builds: gnutls30-3.5.18-1.el6 (FEDORA-EPEL-2018-b4c337857d) A TLS protocol implementation Update Information: Updated to 3.5.18 ChangeLog: * Tue Sep 25 2018 Nikos Mavrogiannopoulos 3.5.18-1 - Updated to 3.5.18 References: [ 1 ] Bug #1619524 - CVE-2018-10846 gnutls30: gnutls: "Just in Time" PRIME + PROBE cache-based side channel attack can lead to plaintext recovery [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1619524 [ 2 ] Bug #1619519 - CVE-2018-10845 gnutls30: gnutls: HMAC-SHA-384 vulnerable to Lucky thirteen attack due to use of wrong constant [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1619519 [ 3 ] Bug #1619512 - CVE-2018-10844 gnutls30: gnutls: HMAC-SHA-256 vulnerable to Lucky thirteen attack due to not enough dummy function calls [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1619512 [ 4 ] Bug #1459797 - CVE-2017-7507 gnutls30: gnutls: Crash upon receiving well-formed status_request extension [epel-6] https://bugzilla.redhat.com/show_bug.cgi?id=1459797 libmad-0.15.1b-26.el6 (FEDORA-EPEL-2018-6bc3a525a2) MPEG audio decoder library Update Information: Add patches from Kurt Roeckx ChangeLog: * Mon Sep 24 2018 Nicolas Chauvet - 0.15.1b-26 - Add patches from debian * Fri Jul 13 2018 Fedora Release Engineering - 0.15.1b-25 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Wed Feb 7 2018 Fedora Release Engineering - 0.15.1b-24 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Thu Aug 3 2017 Fedora Release Engineering - 0.15.1b-23 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild * Wed Jul 26 2017 Fedora Release Engineering - 0.15.1b-22 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Fri Feb 10 2017 Fedora Release Engineering - 0.15.1b-21 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild References: [ 1 ] Bug #1477498 - CVE-2017-11552 CVE-2018-7263 libmad: various flaws [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1477498 [ 2 ] Bug #1447358 - CVE-2017-8372 CVE-2017-8373 CVE-2017-8374 libmad: Multiple vulnerabilities [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=1447358 php-tcpdf-6.2.25-1.el6 (FEDORA-EPEL-2018-56bfbe3964) PHP class for generating PDF documents and barcodes Update Information: **Version 6.2.25** - Fix support for image URLs. **Version 6.2.24** - Support remote urls when checking if file exists. **Version 6.2.23** - Simplify file_exists function. **Version 6.2.20** - Fix for security vulnerability: Using the phar:// wrapper it was possible to trigger the unserialization of user provided data. **Version 6.2.19** - Merge various fixes for PHP 7.3 compatibility and security. ChangeLog: * Mon Sep 24 2018 Remi Collet - 6.2.25-1 -
[Bug 1632767] perl-Text-Bidi-2.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1632767 --- Comment #6 from Fedora Update System --- perl-Text-Bidi-2.15-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-9158dc04f4 -- You are receiving this mail because: You are on the CC list for the bug. ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
