Re: Install Fedora Button for LiveCD

> The one complaint I > still have is that the window is really huge. I mean, it's taking > up, what, 80% of the desktop real estate? That is just perfect, it's the welcome screen. It should receive complete attention. In Ubuntu there are even no panels/widgets shown until you make the selection

Re: Install Fedora Button for LiveCD

> On Wed, 2012-05-09 at 04:51 -0400, Kamil Paral wrote: > > > Cosimo, can you please also make sure that the Close button gets > > keyboard focus automatically after I click on "Try Fedora"? > > I now fixed this here [1], but it will need to be applied to the c

Re: wine font changes system look and feel

> I'd like to brought to wider attention the bug > https://bugzilla.redhat.com/show_bug.cgi?id=693180 > > What's the matter? > > If you install wine, it brings as a dependency wine-tahoma font, that > is > then included in system wide fonts list. This causes the font to be > used > by application

Re: wine font changes system look and feel

Andreas wrote: > Hi, > > first I would like to point out that I am totally open for a > discussion > about this. IMO bugzilla is just not the right place for it. Thanks, that's great. Chris wrote: > Well, no they don't. They are requesting the font Microsoft calls > Tahoma, not a Wine-provided

Re: wine font changes system look and feel

> We could of course aim for a dual-solution: Let > wine-tahoma-fonts put the fonts in the wine font dir (mandatory for > wine) and add a wine-tahoma-fonts-system package (names suggestions > welcome) which also puts the fonts in the system wide font path > (optional). I believe this would be the

Re: wine font changes system look and feel

> Andreas Bierfert wrote: > > We could of course aim for a dual-solution: Let > > wine-tahoma-fonts put the fonts in the wine font dir (mandatory for > > wine) and add a wine-tahoma-fonts-system package (names suggestions > > welcome) which also puts the fonts in the system wide font path > > (opti

swapping disk with UEFI hardware - a dead end?

If you are knowledgeable about UEFI, I'll welcome your advice. This is the issue I encountered: 1. I enabled UEFI mode in BIOS in Lenovo X220 (more exactly I set UEFI as the preferred method). 2. I installed Fedora 17. 3. "Fedora" item appeared in BIOS in "Boot order" and also in the boot manage

Re: swapping disk with UEFI hardware - a dead end?

> Having sent that mail it became obvious that what's happened is that > your > new x220 board doesn't have the efi boot variable set. Some machines > allow > you to boot from a file, in which case it'll be > /efi/fedora/grubx64.efi . > If your firmware doesn't have that, you'll need to boot some

Re: Phabricator - notifications for patch reviewers

> This sounds great.. but what is Herald? Is it a webapp? Can you link > us to more instructions? It's a 'tool' inside Phab: https://phab.qadevel.cloud.fedoraproject.org/herald/ I covered it a bit in the Phab's FAQ: https://fedoraproject.org/wiki/QA/Phabricator _

Re: Taskotron Data Interfaces

> > It's Task-o-tron, it suggests it's meant to execute _tasks_ :-) On > > the other hand, check is more specific than task, it explains the > > purpose better. I guess native speakers will need to deal with > > language subtleties. I just want to be consistent in naming, it helps > > us and our us

Re: To distro-sync or not distro-sync?

> > From: "Vít Ondruch" > > > > Dne 29.10.2015 v 13:24 Honza Šilhan napsal(a): > > > You can exclude the conflicting packages to proceed the system-upgrade > > > i.e.: > > > "dnf system-upgrade download --releasever=23 --distro-sync -x > > > rubygem-celluloid --allowerasing" > > > > > > Does th

Re: Fedora 23 Final RC10 status is GO !

> Very frequently in such cases the entire test matrix is not completely > retested. A lot of prior tests a carried over because they're known > (or strongly suspected) of not having been touched in any way by the > fix of one or two blocker bugs. > > If hundreds of packages get unfrozen and sync'

Re: On running gui applications as root

> Hi, > > > It's certainly the case that *gnome* might do something ridiculous if > > you 'sudo gedit' something, but 'sudo emacs' really ought to be > > equally acceptable regardless of whether you're using the terminal or > > X frontend. > emacs is probably okay, just by virtue of the fact that

Re: On running gui applications as root

> OK, so what are the risks under Wayland? > ... > > Since the security is improved under Wayland, are non-elevated applications > still able to eavesdrop or falsify input/output of elevated applications? > The opposite direction is not that important, I think, because if you run > something as ro

criterion proposal: upgrading across 2 releases

x27;re going to just call dnf-plugin-system-upgrade in the background, hopefully there should be no complications, since it's going to support it (and it already does). Thanks, Kamil - Forwarded Message - From: "Kamil Paral" To: "For testing and quality assurance

Re: Use AutoQA to track changes in "provides" and "requires"?

> Just an idea I had and wanted to float it out to the group... > > I think it would be nice to get an informational (obviously, not a > blocking type check) to get changes in the requires or provides of a > package. It would be a hassle to check it manually but I hope it > would > be fairly easy

Re: Use AutoQA to track changes in "provides" and "requires"?

> On Wed, 2012-08-01 at 11:17 -0500, Richard Shaw wrote: > > On Wed, Aug 1, 2012 at 10:37 AM, Kamil Paral > > wrote: > > > Something like this? [1] [2] > > > > Yup! Something a lot like that! I did look over the AutoQA wiki > > before > > posti

Re: bohdi AutoQA: depcheck test FAILED

> > hi, > i need help, because the AutoQA DepCheck fails on the package > speed-dreams,but the package was pushed anyway. > AutoQA DepCheck log: > http://autoqa.fedoraproject.org/results/418027-autotest/virt04.qa/depcheck/results/speed-dreams-2.1.0-1.html > > the problem was already discussed on

Re: bohdi AutoQA: depcheck test FAILED

> > Following this track: if I look into the build log for the 64-bit f17 > build [1], it seems that the package doesn't require anything but > the > libenet-1.3.3(64-bit). So; in my simple eyes, this looks like AutoQA > doesn't really understand the situation if it says it needs the > 32-bit >

Re: [Test-Announce] Fedora 18 Alpha Test Compose 6 (TC6) Available Now!

> As per the Fedora 18 schedule [1], Fedora 18 Alpha Test Compose 6 > (TC6) > is now available for testing. Please note that Live images are mislabeled (contain 'TC5' in their name), but they are TC6 content. ___ test-announce mailing list test-annou..

Re: Rolling release model philosophy (was Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID)))

> The entire QA team (and the entire anaconda team, for that matter) is > currently spending virtually all its time trying to help bash the new > anaconda into something vaguely resembling shape for a fairly > arbitrary > release deadline, so we can ship something called 'the Fedora 18 > stable > r

Re: Rolling release model philosophy (was Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID)))

> >* A release for general users with low volume of security fixes and > >important bug fixes. > >** Bug fixes would be pushed monthly and QA would be performed on > >this monthly batch of updates. > > Some packages need more than bug fix updates (unless you are taking a > very > broad view of what

Re: Rolling release model philosophy (was Re: Anaconda is totally trashing the F18 schedule (was Re: f18: how to install into a LVM partitions (or RAID)))

> >> This tool is still not going to be able to do magic and there will > >> be > >> config > >> things that still need to be redone. Third party repos will still > >> be > >> an issue. > > > >It's a clean installation, I don't think it needs any magic. Also > >third-party repos are not a problem,

[Test-Announce] 2012-11-07 @ 17:00 UTC - F18 Beta Blocker Bug Review #7

# F18 Beta Blocker Review meeting #7 # Date: 2012-11-07 # Time: 17:00 UTC # Location: #fedora-qa on irc.freenode.net Note: The UTC time was changed. If your country switched from summer time to winter time the last weekend, your local time of the meeting should stay the same. Keeping with what

Re: Fedora Minimal Core SIG -- please join if you're interested

> So, here's a proposal for a semi-informal group linking different > stakeholders interested in curating the @core package selection: > > https://fedoraproject.org/wiki/SIGs/Minimal_Core I wonder whether "Core" is a good word for Fedora Minimal installation SIG. Because currently the minimal in

Re: Fedora Minimal Core SIG -- please join if you're interested

> > I wonder whether "Core" is a good word for Fedora Minimal > > installation SIG. Because currently the minimal installation uses > > @base yum group. @core group is included always, whether you want > > it > > or not. If you really want to have a_core_ system, you must use > > kickstart like th

Re: Blocker Bug Voting and Conversation

> Affected Voters: > - Do you vote on blocker status in bug comments? If necessary, but I don't like it much. In my experience the discussion in the meeting is often very helpful to understand the nature of the bug, and it can shift my opinion substantially. Also I don't like spamming bugzilla

Re: Blocker Bug Voting and Conversation

> Is it the meeting itself which you find helpful or the discussion and > information during the review meetings? Could you see asynchronous > conversation (exact method TBD) being as useful? The discussion is very helpful. It can be asynchronous, of course. It won't be as efficient, but that's a

Re: Detecting soname bumps

> On Tue, 2012-12-04 at 23:24 -0500, Rahul Sundaram wrote: > > Hi > > > > On Tue, Dec 4, 2012 at 2:35 PM, Ville Skyttä > > wrote: > > IMO if a maintainer of a shared lib package goes as far as > > submitting a > > koji build without noticing a soname bump in it, the > >

Re: AutoQA Upgradepath doesn't consider updates-testing?

> >Shouldn't updates-testing be taken into account by the Upgradepath test? > > Probably only for stuff that is part of the same update. Otherwise there > is no guaranty that both will be released at the same time. Exactly. Also see 2) in https://fedoraproject.org/wiki/AutoQA_tests/Upgradepath#Fi

Re: F20 System Wide Change: No Default Syslog

> Because you are able to read txt file with *anything*. But you are not > always able to read binary files. Because journalctl is not available. It's true that if you want to debug/fix your Fedora system from a LiveCD, and the only available LiveCD you have around is a non-systemd distribution,

Re: Rawhide tree now includes install images

> > Is there still a plan to do builds of the normal install iso, > > analagous to the nightly composes for live images? > > Yep. Dennis was going to look into doing some kind of weekly dvd iso > compose. I'm not sure DVD is worthwhile, and it will add quite some extra bandwidth for mirrors. Da

Re: F20 Self Contained Change: Application Installer

> > So, do I understand you correctly that you as Yum/Dnf guys would be ok to > > have a different backend for GUI and non-GUI use cases as mentioned in > > this thread and agreed by FESCo previously? I'd be more than happy to > > see your sign off for this change and state this too there. > > Wel

Re: [Yum-devel] dnf-0..3.10

> Again I would caution you against just blindly changing defaults to be > incompatible with yum ... even if the yum defaults are bad, every > incompatibility incurs a cost for all users (and it will exist as long > as yum and dnf are being used ... so like 10 years from now). At worst > speak wit

Re: [Yum-devel] dnf-0..3.10

> > I responded to your comments in the bugzila: > > https://bugzilla.redhat.com/show_bug.cgi?id=867389 > > > > Regarding Dropbox, it is broken for at least a month after each Fedora > > release, regularly. For F19 they added their repository just very > > recently. You can't force them to fix it.

Re: [Test-Announce] Fedora 20 Alpha Test Compose 5 (TC5) Available Now!

> I might be a little confused now. Yesterday, or Friday I did > > sudo fedup-cli --network 19 > > and I got F20, and I'm up on F20 at the moment. That is highly unlikely, that would indicate a bug in fedup. Are you sure you used "19" and that you really are on "20"? > > Now am I to do a ...-

[Test-Announce] Fwd: Fedora 20 Alpha Change freeze

A bit late, but forwarding here anyway. - Forwarded Message - From: "Dennis Gilmore" To: devel-annou...@lists.fedoraproject.org Sent: Wednesday, September 4, 2013 7:24:40 AM Subject: Fedora 20 Alpha Change freeze -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, as the Fedora 20 sc

Re: Dracut HostOnly or ConfigurationOnly?

> On 09/06/2013 10:15 AM, Jiri Eischmann wrote: > > Can this not be done automatically? If the system fails to boot because > > of significant hardware changes, it's an obvious option to regenerate > > initramfs. I can't image a normal user go to the rescue mode and run > > "dracut --regenerate-all

Re: Dracut HostOnly or ConfigurationOnly?

> On 09/09/2013 11:48 AM, Kamil Paral wrote: > >> On 09/06/2013 10:15 AM, Jiri Eischmann wrote: > >>> Can this not be done automatically? If the system fails to boot because > >>> of significant hardware changes, it's an obvious option to regenerate > &

Re: AutoQA ??? (was: Re: Building and submitting updates for Fedora 20)

Right, Tim fixed the issue and updates in Bodhi should once again receive comments regarding "depcheck" and "upgradepath" checks. There's an opt-in support for rpmlint/rpmguard checks for every package built (the emails are sent to their maintainers), but I'm not clear whether this opt-in suppo

Re: Code Hosting, Development Tools and Open Source

> I've been kicking this idea around for a bit and have chatted a little > with people on IRC but as we're looking to start up development on > taskbot, I want to have a larger discussion on two issues: where do we > host code and what do we want to use for dev support tools (issue > tracking, code

Re: Code Hosting, Development Tools and Open Source

> With the conversation we've been having and the persona developments, I > propose the following: > > - create FAS groups for git-taskbot-core and git-taskbot-tasks which >will control access to the git repos What will git-taskbot-tasks be used to? I thought we were going to have decentral

[Test-Announce] Shared System Certificates - TEST DAY, Thursday 2013-03-28

Hi testers, developer, users, hackers, and friends! We'd like to invite you to our Shared System Certificates Test Day [1] on this Thursday, March 28 [2]. You can test this feature running from Fedora 19 live images and help to make this release better. Join IRC #fedora-test-day on FreeNode and a

[Test-Announce] Fedora 19 Alpha Change freeze

- Forwarded Message - From: "Dennis Gilmore" To: devel-annou...@lists.fedoraproject.org Sent: Tuesday, April 2, 2013 4:40:41 AM Subject: Fedora 19 Alpha Change freeze Hi all, as the Fedora 19 schedule[1] states the Alpha change freeze is upon us. As we are now at the change freeze bodhi

[Test-Announce] MariaDB Test Day tomorrow (2013-04-30)

Dear testers, a new test day awaits! This time it is MariaDB test day, which is scheduled tomorrow (2013-04-30). As some of you might know, Fedora 19 is going to experience an interesting change in default implementation of MySQL RDBMS. MariaDB is a fork of original MySQL and in comparison to M

[Test-Announce] F19 ABRT Test Day

Hi all, today is the Fedora 19 ABRT test day! In the new version of Automatic Bug Reporting Tool we are focusing on testing of the new features such as catching SELinux alerts (aka. setroubleshoot integration), ABRT Server user experience or imporved information on reporting problems with taint

[Test-Announce] Announcement: AnacondaNewUI Followup Test Day on May 21st

Good morning everyone, We would like to invite you to another Fedora 19 Test Day. The test day on Tuesday, May 21st [1] will be focused on recent changes in Anaconda (the installer) introduced as a part of follow-up to AnacondaNewUI project [2]. The main item for testing during this event is adva

Re: [Test-Announce] Fedora 19 Final Test Compose 3 (TC3) Available Now!

Please note that TC3 has changed during the day. Make sure you have the correct one by comparing your checksums to checksums at dl.fedoraproject.org. If you have downloaded TC3 after the announcement was sent, you should be safe. -- devel mailing list devel@lists.fedoraproject.org https://admin.

Re: Fedora Gooey Karma as GSOC project

> Hi, > > On Wed, Jun 05, 2013 at 06:48:55PM +0200, Branislav Blaskovic wrote: > > > My proposal [1] is available on fedoraproject wiki page where you can find > > main features of this new tool. > > > If you have any questions, please feel free to contact me here on mailing > > list, off-list o

Re: Too fast karma on Bodhi updates

> Any kind of feedback after package gets into updates repository should > be denied, I can't think of a case where package moves to updates > repository and bodhi still allows to add comments/karma. Any feedback > after that can be either reported in bugzilla or to the package > maintainers direct

Re: Too fast karma on Bodhi updates

> On 07/11/2016 10:49 AM, Kamil Paral wrote: > >> Any kind of feedback after package gets into updates repository should > >> be denied, I can't think of a case where package moves to updates > >> repository and bodhi still allows to add comments/karma. Any fee

Re: dnf system upgrade has zero progress on text boot (`quiet no rhgb`)

> One of my laptops has quiet and no rhgb in the grub line, so no pretty UI. > As I wasn't paying attention, I used the fedup commands (download, reboot), > which got routed to dnf. Upon reboot, the on-screen output showed a partial > boot (from systemd messages) and no indication that an upgrade

Re: Requiring package test instructions

> Oh no, that is not what we're aiming for. We are aiming for a set of > automated *sanity tests* that run for every update. Over time maybe > we could add regression tests to it that can't be added to the > upstream testsuite for some reason (requiring root privs for example, > much easier to do

Re: Testing request: AMD chipset kernel issue

> On 18/08/16 02:45 PM, Adam Williamson wrote: > > On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote: > >> On 18/08/16 12:07 PM, Adam Williamson wrote: > >>> Hi folks! > >>> > >>> There is a bug nominated as a Fedora 25 Alpha blocker: > >>> > >>> https://bugzilla.redhat.com/show_bug.cgi?id

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

> Based on today's blocker review meeting discussion, and this email > thread [1] I'd like to propose making only Fedora Media Writer the > *officially supported* USB installation media creation tool, starting > with Fedora 26. > > The practical implication of "officially support" means bugs for w

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

> > If we do not 'support' livecd-iso-to-disk any more, we no longer > > support: > > > > 1) persistent storage (via overlays) > > 2) non-destructive write > > Does anyone know why we can't have Fedora Media Writer support these > functions as well? I hope it won't. Or if it will, I hope it won'

Re: Installation validation test change proposal: merge USB tests into 'default boot and install', add more environment columns

> Hi folks! Sending this to devel@ as well as test@ as there's been some > relevant discussion there recently. We've been kicking around a couple > of issues lately: > > 1. Exactly what do we need to test and block on, in terms of writing > images to USB sticks? > > 2. 'Default boot and install'

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

> Speaking for myself only here, my experience in the gfx team > is that there are so many bugs that I cannot see the forest > through the trees. > > A list with issues which are not blockers, but only barely so > and it would be really really good to have them fixed, > would certainly be a list I

Re: GRUB menu hidden by default?

> Here's what our policies say: > > https://fedoraproject.org/wiki/Packaging:Guidelines#All_patches_should_have_an_upstream_bug_link_or_comment > > "All patches should have an upstream bug link or comment > > All patches in Fedora spec files SHOULD have a comment above them > about > their upstr

Re: Most buggy packages

> Hi, > since we opened the question of the most buggy applications I would > like > to introduce you the Fedora crash statistics generated from ABRT > reports. It actually doesn't show the most buggy applications, but > the > number of crashes per application encountered by users in some period >

Re: Most buggy packages

> > Are you going to let bugzilla maintainers know somehow? I would > > assume that once the crash count surpasses a certain threshold, > > you could add a comment to the bugzilla report: > > > > "This has crashed for 100 users, see [FAF URL] for details." > > "This has crashed for 1000 users, see

Re: Fedora 19 schedule's new home & plans

> Dne 1.3.2013 14:09, Jaroslav Reznik napsal(a): > > Hi all! (and sorry for post to sooo many lists) > > As we already have a final schedule (for a three weeks now) and > > we're > > getting closer to release windmills - I'd like to make the schedule > > easy to use for everyone (and that means for

Re: Proposal: Rawhide tracker bug

> - bugs that break the rawhide buildroot. In practice these are > usually > noticed pretty quickly and the offending build is just untagged > until > it can be fixed, but there could be cases where the fix is more > complex and has a bug associated with it. For those of us who are not ski

Re: rawhide report: 20130313 changes

> The message bus is your friend here: > > Mar 13 13:34:10 compose.rawhide.rsync.start -- > started rsyncing rawhide compose for public consumption > https://alt.fedoraproject.org/pub/fedora/linux/development/rawhide Is there a web page where I can see the whole history of fedmsg messages (e.g.

Re: Bodhi policy for pushing updates to stable

> Hi all. > > When upgrading F20 to F21 using FedUp, some users had a problem > with some packages not being upgraded (e.g. [1]). The problem was > caused by broken update path F20 -> F21. Just a note: That problem is even more complex. Fedora Branched some has freeze periods, when you can't pus

Re: Taskotron misses dropped subpackages

> Taskotron doesn't notice if subpackages have been dropped and cause > unresolvable dependencies because they are not obsoleted anywhere. Yes, depcheck doesn't currently handle that. I've created: https://phab.qadevel.cloud.fedoraproject.org/T384 -- devel mailing list devel@lists.fedoraproject.o

Re: GUI applications writing garbage to stdout/stderr

> Thanks for the encouragement. For the record, I filed > > https://bugzilla.redhat.com/show_bug.cgi?id=1184038 (GTK apps) > https://bugzilla.redhat.com/show_bug.cgi?id=1184868 (evince) I very much recommend you to report these issues (also) to GNOME Bugzilla. GNOME/GTK developers don't follow

Re: GUI applications writing garbage to stdout/stderr

> The warnings only happen when using development versions of GTK+. So it > shouldn't happen in F21, or in the future in F22, just in rawhide. So when I talked about GTK, I meant the whole GNOME stack, like GLib, gvfs, st, clutter, mutter, gnome-shell, gstreamer, etc. I guess not all of these par

Re: Plan of Record for Fedora 22 Network Install Media

> In Fedora 22, we will be producing four network install ISOs: > * Fedora Server > - Server branding > - Default environment group: Fedora Server > - Auto-partitioning defaults: LVM on XFS (except /boot) > - Responsible WG: Server WG > * Fedora Workstation > - Workstation branding >

Re: GUI applications writing garbage to stdout/stderr

> > All those are warnings, not "garbage" or debug output. File bugs about > > those, > > there should be zero warnings in normal usage. > > Shouldn't they trigger abrt then? more importantly, is it possible to capture > that in the QA process during distribution composition? I believe a lot of >

Re: taskotron dep failure false positive

> I got a complaint about this: > > not ok - depcheck for Bodhi update vtk-6.1.0-23.fc21 # FAIL >--- >arch: x86_64 >details: > output: |- >Build vtk-6.1.0-23.fc21 failed depcheck >package vtk-qt-python-6.1.0-23.fc21.i686 requires vtk(x86-32) = > 6.1.0-23.fc21, but

Re: taskotron failiure

> Updates seem to have been pushed out now, thanks!. > > But I see a different problem with my update. Taskotron failure which > I don't understand: > > not ok - depcheck for Bodhi update systemd-216-20.fc21# FAIL > --- > arch: x86_64 > details: > output: |- > Build system

Re: [Test-Announce] Fedora 22 Branched 20150217 nightly compose nominated for testing

> > You can see all results, find testing instructions and image download > > locations, and enter results on the Summary page: > > > > https://fedoraproject.org/wiki/Test_Results:Fedora_22_Branched_20150217_Summary > > > > The individual test result pages are: > > > > https://fedoraproject.org/wik

[Test-Announce] Cancelling 2017-02-06 meetings

Hello, we have AdamW on the plane and no QA meeting can be ever complete without AdamW :-) Joking aside, there's only 1 proposed blocker for F26 Alpha, so there should be no harm in cancelling both QA and Blocker Review meeting today. If there are any topics you'd like to discuss, please start a

Re: Semi-automated (and automated) testing of laptops for Fedora

> Hi, > > we are currently looking into enabling us to test laptops more > effectively. There are two main parts to the issue, which is to >    1. have a system to run semi-automated tests on a standalone machine >   and submit the results to an online server ("Fedora Tested Laptops") >   

Re: Critpath - questions

On Wed, Apr 5, 2017 at 12:20 PM, Michal Schorm wrote: > Hi, > > some questions about Critpath, I was not able to find, looking at [1] > and [2] > . > > TL;DR: why is MariaDB Crit

Re: running MTF tests in taskotron

On Mon, Jun 19, 2017 at 10:13 AM, Tomas Tomecek wrote: > The way I envision this is that the test would be invoked via taskotron's > API, > something like: > > $ taskotron trigger --koji-build= > > The CLI tool would contact taskotron's API and would submit a new test > run. For > me, it's an im

Re: [Test-Announce] Proposal to CANCEL: 2017-06-26 Fedora QA Meeting

On Mon, Jun 26, 2017 at 10:26 AM, Silvia Sanchez wrote: > > Where is the the Blocker review meeting? > See the *other* email in test-announce :-) ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.

Re: Status report on Flatpaks in Fedora Infrastructure

On Mon, Jul 3, 2017 at 8:47 PM, Owen Taylor wrote: > I've just submitted a change proposal for creating Flatpaks out of Fedora > package content: > > https://fedoraproject.org/wiki/Changes/Graphical_ > Applications_as_Flatpaks > > This is submitted as a F27 change proposal, but it's expected th

Re: F27 System Wide Change: Reduce Initial Setup Redundancy

On Fri, Jul 7, 2017 at 4:24 PM, Jaroslav Reznik wrote: > User Account > > Currently, users have the option of creating the initial user account > in Anaconda, or not. Anaconda does not require this if the user sets a > root password. Users who do not create a user account in Anaconda are > requir

Re: F27 System Wide Change: Reduce Initial Setup Redundancy

On Mon, Jul 10, 2017 at 5:53 PM, Michael Catanzaro wrote: > OK, I see the problem. > > On the one hand, systemd needs fixed, as disabled root account is already > a popular pattern on the largest Linux distro out there. This is an issue > for rescue prompts too. That would be great. > But it'

Re: F26 dnf makecache timer hanging

On Tue, Jul 18, 2017 at 3:54 PM, Chris Murphy wrote: > [chris@f26s ~]$ sudo dnf update > Waiting for process with pid 3379 to finish. > ^CKeyboardInterrupt: Terminated. > I haven't seen this exact problem (timer blocking standard dnf command), but I started experience dnf hangs when downloading

Re: Taskbot: TAP vs Subunit

> = TAP = > > TAP is not unittest-specific, and is human-readable plaintext format. > > It also has just PASS/FAIL logic, but there is a possibility to add YAML > 'metadata' to any result (since TAP v. 13). > > The real issue with TAP is Python support. > There is a TAP-consumer library created

autoqa rpmlint crashes

A lot of autoqa rpmlint jobs crash lately. Just to let you know, this is a problem in rpmlint and I reported it here: https://bugzilla.redhat.com/show_bug.cgi?id=1026328 ___ qa-devel mailing list qa-de...@lists.fedoraproject.org https://admin.fedoraproj

[Test-Announce] Printing Test Day today (Tuesday 2013-11-05)

The Printing Test Day for Fedora 20 is today. https://fedoraproject.org/wiki/Test_Day:2013-11-05_Printing This test day is for testing all aspects of printing, including setting up the printer, sharing printers on the network, and printing jobs. The changes in Fedora 20 are relatively minor: swi

Re: New Bug Tracker Ready for Use (Finally)

> > Actually I think this behavior (send me my own emails) can be even > > disabled in Trac admin configuration. I looked into Phabricator user > > settings and it's not present there. But at least the From header > > contains my name. Oh, actually in email preferences you can set to disable your

[Test-Announce] Power Management Test Day today (2013-11-14)

Forwarding an invite from Jan Scotka: Hi, There is planned Power Management testday today. If you are interested to see capabilities of your machine or measure power consumption please join us, you will see what your HW know. Everybody with various HW configuration welcomed (Old & New & Obscure

Re: ecryptfs alternatives

> On Wed, Dec 11, 2013 at 10:33:34PM +0100, Michał Piotrowski wrote: > > The beauty of ecryptfs is that I can encrypt one dir - not whole file > > system. > > What's the concern with encrypting the whole filesystem? It's better > for you because you leave significant personal information all over

Re: Taskotron (was: Re: Unannounced ABI change without soname bump in libevdev-0.6 in Rawhide (and F19 and F20...) breaks GNOME, probably other consumers)

> On Thu, Dec 26, 2013 at 07:52:04PM -0800, Adam Williamson wrote: > > No. There's a bad one, which is AutoQA. The problem with it is it's more > > or less considered obsolete now as far as new development goes; the devs > > are working on Taskotron to replace it, but I don't believe it's ready > >

Re: RFC: Taskotron task description format

I've finally read it as well :) Comments below. > At the moment, that task yaml file for rpmlint [1] looks like: > > dependencies: > - rpmlint > - libtaskbot > > input: > args: envr,arch These arguments are provided by the event trigger, right? So, the event trigger offer

gitflow and branch naming conventions

So, we're going the gitflow way [1][2]. However, when I looked at our bitbucket repositories today, only the libtaskotron branch uses 'develop' branch, all other projects use only 'master' branch - even taskotron-trigger or task-rpmlint. Does it mean we use gitflow only for libtaskotron? Or is i

Smoker - Smoke Testing Framework

Just out of curiosity, there is yet another testing framework, open sourced by GoodData company. Written in Python. I haven't studied it too well, just skimmed the readme. https://github.com/gooddata/smoker ___ qa-devel mailing list qa-de...@lists.fedo

Re: F24 Self Contained Change: Graphical System Upgrades

> Also can we ensure that gnome software/packagekit updates the dnf database > correctly before we recommend, or even enable, this upgrade method? > It's bad enough right now with F23 and dnf autoremoving stuff installed via > the packagekit interfaces but add in a whole system upgrade being out o

Re: Fedora 24 Mass Rebuild

> > #2) Not sure how the rpmlint notification system is setup, but I > > found it odd that I received notification of packages that passed. > > Really why send those? Or is it something I can configure what type > > of notification I would want? > > It seems there's only triggers on 'new result' o

Re: rpmlint FAILED for cppad-20160000.0-2.fc24

> I have comments at the top of the spec file that explain the reason for > the warning below. In addition, I have posted messages about this > warning on this list; see > project.org/thread/GI3L74J47OLRTYLQIMSEUA7SUZR5VLU7/#JUUSDFET2HBPUDIP3G7CPHB7Q7XCCLEG > > Should I just ignore the message bel

Re: rpmlint FAILED for cppad-20160000.0-2.fc24

> >>>>> "KP" == Kamil Paral writes: > > KP> Hello, we have an RFE for adding a rpmlint whitelist feature here: > KP> https://phab.qadevel.cloud.fedoraproject.org/T692 > > I can't actually log into phabricator to respond there, Just log in

Re: [Guidelines change] Changes to the packaging guidelines

> RWMJ> Is that new? > > Not really. The change relating to what's in the buildroot was made > about nine months ago: https://fedorahosted.org/fpc/ticket/497 I created my first COPR over this weekend. I worked according to: https://fedoraproject.org/wiki/How_to_create_an_RPM_package because that

Re: [Test-Announce] 2016-03-14 @ 17:00 UTC - Fedora 24 Blocker Review

> # F24 Blocker Review meeting > # Date: 2016-03-14 > # Time: 17:00 UTC Actually, I believe it should be 16:00 UTC, because North America just moved to summer time, and we're usually tied to NA local time for our meetings. So if anyone's reading this, be there an hour earlier, just to be sure, a

Re: ThinkPad X220 does not wake up after suspend (since Saturday)

> Hi, > > my ThinkPad X220 runs Fedora 23 with automatic updates, Chromium and > Spotify Copr. Up until Friday night, it worked just fine. > > Friday afternoon the new Kernel 4.4.5 was installed. It was only loaded > on Saturday when I started the machine in the afternoon. I suspended the > lapto

Re: Automatic ABI checks for new package updates in bodhi using taskotron

> Hi all, > Last year, discussion happened around "Checking the ABI of packages submitted > to the updates-testing Fedora repository" on Fedora devel ML [1]. > We felt that taskotron[2] will be the best place to run automatic ABI checks > for a new package update pushed in bodhi for testing again

<    1   2   3   4   5   >