Github messages for voidlinux
 help / color / mirror / Atom feed
From: bwalzer866 <bwalzer866@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] xdm package upgrade wipes out configuration changes
Date: Mon, 18 May 2020 19:24:41 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22090@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

New issue by bwalzer866 on void-packages repository

https://github.com/void-linux/void-packages/issues/22090

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.4.30_1 x86_64 AuthenticAMD notuptodate rF
* package:  xdm
  xdm-1.1.12_2

### Expected behavior
Updating the xdm package should not overwrite config files changed by the user.
### Actual behavior
Updating the xdm package _does_ overwrite config files changed by the user.
### Steps to reproduce the behavior
Update the xdm package.

Seriously though, could someone please add the config files to the Void xdm package? This is the list of xdm config files I swiped from the Arch Linux package:

`/etc/X11/xdm/Xaccess`
`/etc/X11/xdm/Xresources/`
`/etc/X11/xdm/Xservers`
`/etc/X11/xdm/xdm-config`
`/etc/pam.d/xdm`
`/etc/X11/xdm/Xsetup_0`
`/etc/X11/xdm/Xsession`

... from [here](https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/xorg-xdm).

             reply	other threads:[~2020-05-18 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 17:24 bwalzer866 [this message]
2020-05-18 20:13 ` ericonr
2020-05-18 20:32 ` bwalzer866
2020-05-18 20:32 ` [ISSUE] [CLOSED] " bwalzer866
2020-05-19  2:45 ` ericonr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22090@inbox.vuxu.org \
    --to=bwalzer866@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).