From owner-freebsd-xfce@freebsd.org Fri May 3 14:36:35 2019 Return-Path: Delivered-To: freebsd-xfce@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11F541592145 for ; Fri, 3 May 2019 14:36:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 90E4773C86 for ; Fri, 3 May 2019 14:36:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 51386159213B; Fri, 3 May 2019 14:36:34 +0000 (UTC) Delivered-To: xfce@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1373C159213A for ; Fri, 3 May 2019 14:36:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A414473C82 for ; Fri, 3 May 2019 14:36:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EB7A9FB03 for ; Fri, 3 May 2019 14:36:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x43EaWJs096791 for ; Fri, 3 May 2019 14:36:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x43EaWsC096790 for xfce@FreeBSD.org; Fri, 3 May 2019 14:36:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: xfce@FreeBSD.org Subject: [Bug 237714] [PATCH] sysutils/xfce4-power-manager: fix craches, improve freebsd support, add DEBUG option Date: Fri, 03 May 2019 14:36:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: madpilot@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: xfce@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: flagtypes.name cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xfce@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: XFCE for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 May 2019 14:36:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237714 Guido Falsi changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback?(xfce@F |maintainer-feedback+ |reeBSD.org) | CC| |madpilot@FreeBSD.org Status|New |In Progress --- Comment #1 from Guido Falsi --- Hi, Thanks for the patch. I have some questions: - Why add DEBUG as an option? WITH_DEBUG is not enough to activate it, just adding --enable-debug as needed when WITH_DEBUG is on. While there is no strict rule about this and some ports are adding a DEBUG option, it is not a good practice, and using WITH_DEBUG should be the only = way to enable it. it is not a user flag, it's a developer flag anyway. - Regarding the source changes, I need some clearifications. the g_object_ref change should be upstreamed? Have you already sent a bug report? It looks like a bug to me. Would you propose the patch upstream? I don't get why you need the "return g_strdup (_("Unknown"));" patch. Looki= ng at the code I'd say the intention is for that to never be reached, but maybe there is a bug if 59.0 < value < 60.0. The upstream repository has fixed th= is in a different way. I'd be more comfortable importing the newer upstream co= de [1], to avoid diverging. Could you modify your patch to match upstream code? Fir the xfpm-backlight-helper.c patch, before committing it I'd like to know where the "8" number comes from, and exactly what the patch fixes. This last hunk also contains some gratuitous changes which would make upstreaming it difficult. You should not make whitespace changes (they can = be there for upstream code style rules) and I'd also avoid changing the return logic, and leave it matching what the upstream used. This is because this k= ind of change could be refused by upstream if proposed. Also, while upstream allocating only one gchar looks definitely too little,= 64 is definitely too much, since your code never uses more than 5 (including terminating \0 ). The second argument to g_snprintf could also be calculated correctly. As before, should this be upstreamed? Are you wiling to propose it in an upstream bug report? [1] https://github.com/xfce-mirror/xfce4-power-manager/blob/xfce-4.12/settings/= xfpm-settings.c#L1567 --=20 You are receiving this mail because: You are the assignee for the bug.=