X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h=
	cc:content-transfer-encoding:content-type:content-type:date:date
	:from:from:in-reply-to:message-id:mime-version:reply-to:sender
	:subject:subject:to:to; s=fm2; t=1679939312; x=1680025712; bh=rg
	qTIHxU8pvKCk9InTYTWZk1E7048gLBFLSCd6fkoxo=; b=aCTmrkshJNCYoU0rLI
	eEHkUZQuBOqRB/6px3EF1XDkEBfTrMWHRRx4ieM2f0EzhWsjVjR/jvv9FilJE3YH
	sWJvWo0cMj2UI28r3oXPbWjLKI/b/Apad6/y6lD4gicUmMF7DEvX3xh0ccLyEwlt
	77JJIOshnB5JILISGkld8owOBwAo8HSTMgzADkUNuRerRZBNRjd4MVl0I9cTk1JO
	oYAJfBNbPNiosRdlEYpx7S+PEkfcWyieZFZz5clXsVibORtOfXP4nIoGomJ1u9qo
	fj2TwYEli78GAopnwDbnT8R+3CGgtuM8DyOJzHw5FpHS91EDLG5dvu+5dlWdoeJw
	jYFw==
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-transfer-encoding:content-type
	:content-type:date:date:feedback-id:feedback-id:from:from
	:in-reply-to:message-id:mime-version:reply-to:sender:subject
	:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
	:x-sasl-enc; s=fm2; t=1679939312; x=1680025712; bh=rgqTIHxU8pvKC
	k9InTYTWZk1E7048gLBFLSCd6fkoxo=; b=Oyhju85b2RE7ueYw811z1y0XR+rld
	yakYpBf0yM40NOnxUEoM91EXMZcw6BBbOeVHGz+UoUZsuJ+Shf+UcejM23rfmdRi
	bmRIlrmV/iXS/jsgTViheJAzVU9xxMe++6pi215msasF9CrzP20UeI9453Dzu1Np
	8YXekmXU7UBQxClKlgStuTdsh2o3lYc7xEwgR4i+YafoWF47/vf4BWtRfMSgUOM/
	W8R0NceKI/W8nutG9CG9Vt7zJ+u4TgYfT8xwwpbOZYGzGH/Q/vOHjfdzp4Nnavtp
	NZ+FWKCQpsXRopEc7HbjOp3LxQ1+Jvm4WZvz89ypM0+RnbdaHYPX//jYA==
X-ME-Sender: <xms:7dYhZOFFKO1woSWxDxp4BxeRWndsQf31PkOceuSwkoywLjTkufC2Cw>
    <xme:7dYhZPUCUPqSX8nPbOn72KsNTBpmVsQj3g1Z9EkuFz9RWGFiL92j0aGkAQwu1PZfx
    8MCbUmYsiF2X6Z2lw>
X-ME-Received: <xmr:7dYhZIK49Z28qZEGiALei6yjqgjlQcv7rRxnZKIE_ny0xjX_w3OJEqM9MxGq2b9w9Rc_bxBeOXgAg6WaMhiXWmMFNbePFswdzF_tOsGO5CU_6LPQb_JvakNj6Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdehvddguddulecutefuodetggdotefrod
    ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh
    necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd
    enucfjughrpefvhffurffkffgfgggtgfesthejredttdefjeenucfhrhhomhepifhirhhv
    ihhnucfjvghrrhcuoehghhgvrhhrlhdvsehfrghsthhmrghilhdrtghomheqnecuggftrf
    grthhtvghrnhepleffuedvudevleeghfefffegjeevffejgfdvhedtkeevfeetvedvudel
    heffvddvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh
    epghhhvghrrhhlvdesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:7dYhZIHHHx7pvM4Y3qKETncU1ZUe415nCaKJ7VxRVih_sw93UemDuw>
    <xmx:7dYhZEWc9WXano07wUPCLTigpQs6RXtKw7AlJfQXlw9MJx5UYz_Wcg>
    <xmx:7dYhZLMjfHrWl7kPRuoCeNUKLABNsqeW3l5Q3F7j1UF8t-Kuz4jg8g>
    <xmx:8NYhZHC_U_5kjxYJ1tQxNA-T8fAQuDs053x3rsMbk2uYMVItAQifrw>
Feedback-ID: iee494631:Fastmail
To: gEDA User Mailing List <geda-user AT delorie DOT com>
From: "Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: [geda-user] Changing gschem backup file permissions
X-Priority: 2 (High)
Message-ID: <4772851a-fca0-4370-d6bb-ef854127e604@fastmail.com>
Date: Mon, 27 Mar 2023 10:48:23 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101
 Thunderbird/68.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Reply-To: geda-user AT delorie DOT com

Greetings,

I am using gschem under Slackware Linux 14.2 (K4.4.301) and xfce4. My 
umask is set to 022 in my ~/.bash_profile.

I am having an annoying problem with gschem setting the backup file 
(*.sch~) to read-only, even for the owner (permissions 0444). When I do 
my system backup, which is a flat copy, not using tar, and I copy the 
gschem files to a blank USB Flash Disk, it works fine. But when I copy 
the next time's backups to that same Flash disk, attempting to overwrite 
some of the previous gschem backups, the copy fails because the previous 
backups on the Flash Disk are read-only. This is an extra annoyance when 
the backup is done by a script. No other application I use exhibits this 
problem.

Is there a way to change the gschem backup file permissions within 
gschem to at least read/write for the owner (0644)?

Thanks.
Girvin Herr