October 2014 - Arch-general - lists.archlinux.org

[arch-general] systemd-journal groups?
by Magnus Therning 02 Oct '14

02 Oct '14

I have a feeling this should be documented somewhere, but I can't seem to find anything about it. When catching up with the latest package updates just now I noticed I had a passwd.pacnew file in /etc. When merging in the changes I found I have two systemd user entries that don't appear in the upstream file: systemd-journal-remote:x:997:997:systemd Journal Remote:/:/usr/bin/nologin systemd-journal-upload:x:996:996:systemd Journal Upload:/:/usr/bin/nologin Are they safe to remove? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus(a)therning.org jabber: magnus(a)therning.org twitter: magthe http://therning.org/magnus The results point out the fragility of programmer expertise: advanced programmers have strong expectations about what programs should look like, and when those expectations are violated--in seemingly innocuous ways--their performance drops drastically. -- Elliot Soloway and Kate Ehrlich

3 3

[arch-general] wireshark-qt 1.12
by G. Richard Bellamy 01 Oct '14

01 Oct '14

When looking at the PKGBUILD for the wireshark split package [1], I see that both wireshark-cli and wireshark-gtk use "conflicts=(wireshark)" but wireshark-qt does not. Should it? The use of "replaces=(wireshark)" is also inconsistent. I'm just wondering if there's some rationale behind the use (or non-use) of these functions inside one split package over another, or if it's a simple oversight? -rb [1] https://projects.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h…

2 1

Re: [arch-general] [aur-general] lists.archlinux.org mailing list memberships reminder
by Florian Pritz 01 Oct '14

01 Oct '14

On 01.10.2014 09:09, Florian Bruhin wrote: > * Martti Kühne <mysatyre(a)gmail.com> [2014-10-01 08:51:35 +0200]: >> This is news to me. I never got this kind of stuff from this mailing list. > > This is a standard mailman message - maybe they changed the setting > lately? I moved mailman to a new server and it looks like the old one never ran mailman cronjobs (the new one does). That said, yes it is a standard message and it defaults to being enabled, but since nobody complained before we've disabled it again for our lists.

5 4