BleachBit is available in the repos, but does not appear when searching in GNOME Software

I contributed an AppStream .metainfo.xml file to the upstream developers. https://github.com/bleachbit/bleachbit/blob/master/org.bleachbit.BleachBit.metainfo.xml Which seems to pass validation during builds based on my RPM spec. https://src.fedoraproject.org/rpms/bleachbit/blob/master/f/ble

Re: User builds can't be viewed in bodhi

Just tried and I can access it now, thanks. -- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com On Thu, Aug 13, 2020 at 1:37 AM Kevin Fenzi wrote: > On Thu, Aug 13, 2020 at 01:16:59AM +0100, Chihurumnaya Ibiam wrote: > > Hi, > > > > While trying to access a user's builds in bodhi I kept getti

Re: User builds can't be viewed in bodhi

On Thu, Aug 13, 2020 at 01:16:59AM +0100, Chihurumnaya Ibiam wrote: > Hi, > > While trying to access a user's builds in bodhi I kept getting this error > . Can you try again now? There was/is just finishing up a planned outage: https://pagure.io/fedora-in

Re: EarlyOOM +ZRAM Only

On Wednesday, August 12, 2020 3:43:24 PM MST Samuel Sieb wrote: > On 8/12/20 12:06 PM, John M. Harris Jr wrote: > > > On Wednesday, August 12, 2020 11:27:37 AM MST Sergio Belkin wrote: > > > >> mem avail: 337 of 15887 MiB ( 2.13%), swap free:0 of 4095 MiB ( > >> 0.00%) > > > low memory! at

User builds can't be viewed in bodhi

Hi, While trying to access a user's builds in bodhi I kept getting this error . -- Ibiam Chihurumnaya ibiamchihurumn...@gmail.com ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an em

Re: EarlyOOM +ZRAM Only

On Wed, Aug 12, 2020 at 5:43 pm, Michael Catanzaro wrote: but it might instead get confused I meant to write: it might *then* get confused. That is, it should always start by killing the right process, but it might then continue to kill more unnecessarily.

Re: EarlyOOM +ZRAM Only

earlyoom actually works best with only zram. If you have a disk-based swap partition, your system is likely to become frozen and unusable before earlyoom gets a chance to save you. On Wed, Aug 12, 2020 at 4:16 pm, Przemek Klosowski via devel wrote: This is weird---your swap was 100% full, an

Re: EarlyOOM +ZRAM Only

On 8/12/20 12:06 PM, John M. Harris Jr wrote: On Wednesday, August 12, 2020 11:27:37 AM MST Sergio Belkin wrote: mem avail: 337 of 15887 MiB ( 2.13%), swap free:0 of 4095 MiB ( 0.00%) low memory! at or below SIGTERM limits: mem 2.52%, swap 10.00% sending SIGTERM to process 1898342 uid 100

Re: EarlyOOM +ZRAM Only

El mié., 12 ago. 2020 a las 17:17, Przemek Klosowski via devel (< devel@lists.fedoraproject.org>) escribió: > On 8/12/20 2:27 PM, Sergio Belkin wrote: > > Hi! > > I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based > > swap partition. > > I was using mainly Zoom (desktop app) +

Re: EarlyOOM +ZRAM Only

El mié., 12 ago. 2020 a las 16:07, John M. Harris Jr () escribió: > On Wednesday, August 12, 2020 11:27:37 AM MST Sergio Belkin wrote: > > Hi! > > I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based > swap > > partition. > > I was using mainly Zoom (desktop app) + Firefox + Virt

Re: EarlyOOM +ZRAM Only

El mié., 12 ago. 2020 a las 15:49, Samuel Sieb () escribió: > On 8/12/20 11:27 AM, Sergio Belkin wrote: > > I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based > > swap partition. > > I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian > > with 4GB of RAM), and

Re: EarlyOOM +ZRAM Only

On 8/12/20 2:27 PM, Sergio Belkin wrote: Hi! I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based swap partition. I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian with 4GB of RAM), and EarlyOOM killed Zoom in the middle of a call :( This is weird---your s

Re: EarlyOOM +ZRAM Only

On Wednesday, August 12, 2020 11:27:37 AM MST Sergio Belkin wrote: > Hi! > I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based swap > partition. > I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian with > 4GB of RAM), and EarlyOOM killed Zoom in the middle of a

Re: EarlyOOM +ZRAM Only

On 8/12/20 11:27 AM, Sergio Belkin wrote: I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based swap partition. I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian with 4GB of RAM), and EarlyOOM killed Zoom in the middle of a call :( This is the log: The log

EarlyOOM +ZRAM Only

Hi! I 've just had a problem using EarlyOOM + ZRAM. I haven't a disk-based swap partition. I was using mainly Zoom (desktop app) + Firefox + VirtualBox (Debian with 4GB of RAM), and EarlyOOM killed Zoom in the middle of a call :( This is the log: mem avail: 399 of 15887 MiB ( 2.51%), swap free:

Re: Fedora 33, can't access NAS

On Wed, 2020-08-12 at 19:24 +0200, Andreas Tunek wrote: > I made a fresh install with Fedora Workstation 33 today and everything > seems to be working except for one problem. I can see my NAS in Files, but > I can't connect to it. It looks exactly the same as F32 where everything > works as expecte

Fedora 33, can't access NAS

I made a fresh install with Fedora Workstation 33 today and everything seems to be working except for one problem. I can see my NAS in Files, but I can't connect to it. It looks exactly the same as F32 where everything works as expected. Does anyone have any pointers on how to debug this, or shoul

Re: Fedora 33 Mass Branching

Il 12/08/20 16:26, Mohan Boddu ha scritto: > > Yes, you are right, but maintainers shouldn't think that bodhi is > active and try to submit builds as updates in bodhi. > > Maybe, it should be better to reword it > > Actually, this should not be possible, Bodhi 5.5 will refuse to manually create an

where to add new documentation (and how)

On Sat, Aug 01, 2020 at 01:18:39PM -0500, Richard Shaw wrote: > Perhaps... Is docs open? Or is there some process for getting this > approved? I'm heavily making updates right now. I'm somewhat > selfishly documenting it so I remember how I set everything up as I'm sure > I won't remember a year fr

Re: Fedora 33 Mass Branching

On Wed, Aug 12, 2020 at 8:14 AM Miro Hrončok wrote: > > On 12. 08. 20 1:09, Mohan Boddu wrote: > > Bodhi is currently not > > active for Fedora 33, it will be enabled in a couple of weeks when we > > hit Beta change freeze point in the Fedora 33 schedule[1]. > > It seems that this is not true this

Summary/Minutes from today's FESCo Meeting (2020-08-12)

= #fedora-meeting-2: FESCO (2020-08-12) = Meeting started by mhroncok at 14:00:07 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2020-08-12/fesco.2020-08-12-14.00.log.html . Meeting

Re: nothing provides kernel needed by libguestfs-1:1.43.1-4.fc33.x86_64

On 12. 08. 20 14:39, Richard W.M. Jones wrote: There is indeed no kernel package I can find that's tagged into f34, but there is one tagged into f33: https://koji.fedoraproject.org/koji/buildinfo?buildID=1579426 Shouldn't that be enough to satisfy the dependency above through tag inheritance

nothing provides kernel needed by libguestfs-1:1.43.1-4.fc33.x86_64

I suppose this might be a temporary issue caused by branching, but this build in Rawhide has been failing since yesterday: https://koji.fedoraproject.org/koji/taskinfo?taskID=49144308 The error is a bit odd: DEBUG util.py:621: Error: DEBUG util.py:621: Problem: package libguestfs-devel

Re: Fedora 33 Mass Branching

On 12. 08. 20 1:09, Mohan Boddu wrote: Bodhi is currently not active for Fedora 33, it will be enabled in a couple of weeks when we hit Beta change freeze point in the Fedora 33 schedule[1]. It seems that this is not true this time due to gaitng. My f33 builds go trough Bodhi (where they rest

Re: CPE Team Engagement Feedback

Hi Everyone, It has been a little over a month since I have sent this email on changes we have made to our work processes, how we are categorizing work within our team and how we are planning projects in advance, so thank you to everyone who replied to me with your feedback! If you caught the CPE

Re: Fedora 33 Mass Branching

Hi All, Fedora 33 has now been branched, please be sure to do a git pull --rebase to pick up the new branch, as an additional reminder rawhide/f34 has been completely isolated from previous releases, so this means that anything you do for f33 you also have to do in the master branch and do a build

Re: Highlights from the latest Copr release

Unfortunately, Copr still deletes data without warning: https://bugzilla.redhat.com/show_bug.cgi?id=1868367 Kevin Kofler ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org F

Re: Zanata removal is soon, please finish migration

Hi, see my answers below. On Tue, 2020-08-11 at 05:28 +, Jean-Baptiste Holcroft wrote: > python-mehhttps://github.com/rhinstaller/python-meh/issues/25 This project didn't have a release in decade. I will try to look on this soon. > python-simpleline > https://github.com/rhinstaller/

Re: Highlights from the latest Copr release

On Wed, 12 Aug 2020 at 12:32, Pavel Raiskup wrote: > > On Wednesday, August 12, 2020 11:19:00 AM CEST Iñaki Ucar wrote: > > On Wed, 12 Aug 2020 at 10:29, Pavel Raiskup wrote: > > > - Copr newly provides a build-time macro %buildtag. Its format is > > > `.copr` and is useable for auto-increment

Re: Highlights from the latest Copr release

On Wednesday, August 12, 2020 11:19:00 AM CEST Iñaki Ucar wrote: > On Wed, 12 Aug 2020 at 10:29, Pavel Raiskup wrote: > > > > Hello. > > > > On Aug 12 2020, a new Copr release landed production. Here is the list > > of visible changes: > > > > - Project karma implemented; Logged-in users can give

Re: Highlights from the latest Copr release

On 12. 08. 20 11:19, Iñaki Ucar wrote: - Copr newly provides a build-time macro %buildtag. Its format is `.copr` and is useable for auto-incrementing the package's NVR in subsequent builds. It may be used in spec file like: Release: 1%{?dist}%{?buildtag} It could be useful a

Re: Highlights from the latest Copr release

On 12. 08. 20 11:20, Pavel Raiskup wrote: - Copr newly provides a build-time macro %buildtag. Its format is `.copr` and is useable for auto-incrementing the package's NVR in subsequent builds. It may be used in spec file like: Release: 1%{?dist}%{?buildtag} It could be u

Re: Highlights from the latest Copr release

On Wednesday, August 12, 2020 10:51:56 AM CEST Miro Hrončok wrote: > On 12. 08. 20 10:29, Pavel Raiskup wrote: > > - Project karma implemented; Logged-in users can give > >thumbs-up/thumbs-down to the existing copr projects. [snip] > >This is just > > Assuming the arrows up and down near t

Re: Highlights from the latest Copr release

On Wed, 12 Aug 2020 at 10:29, Pavel Raiskup wrote: > > Hello. > > On Aug 12 2020, a new Copr release landed production. Here is the list > of visible changes: > > - Project karma implemented; Logged-in users can give > thumbs-up/thumbs-down to the existing copr projects. This is just > anoth

Re: Highlights from the latest Copr release

On 12. 08. 20 10:29, Pavel Raiskup wrote: Hello. On Aug 12 2020, a new Copr release landed production. Here is the list of visible changes: - Project karma implemented; Logged-in users can give thumbs-up/thumbs-down to the existing copr projects. This is just another way to give feedbac

Re: LTO and the F33 mass rebuild

Dne 11. 08. 20 v 18:43 Kevin Fenzi napsal(a): > On Sun, Aug 09, 2020 at 10:06:49PM -0600, Jeff Law wrote: >> On Sun, 2020-08-09 at 12:02 +0200, Fabio Valentini wrote: >>> On Sun, Aug 9, 2020 at 12:03 AM Jeff Law wrote: So I've done two passes over the F33 build failures here: https

Highlights from the latest Copr release

Hello. On Aug 12 2020, a new Copr release landed production. Here is the list of visible changes: - Project karma implemented; Logged-in users can give thumbs-up/thumbs-down to the existing copr projects. This is just another way to give feedback about a particular Copr project quality. T