Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

2016-12-07 Thread Felipe Sateler 
On 7 December 2016 at 13:57, Vincent Lefevre  wrote:
>
> On 2016-12-07 10:28:45 -0300, Felipe Sateler wrote:
> > Hi ZSH Maintainers,
>
> Not sure they are reading (or have they been Bcc'ed?),

Ooops, I forgot to add the CC.

> but I started
> a thread in zsh-workers:
>
>   http://www.zsh.org/mla/workers/2016/msg02588.html
>
> hoping the issue could be solved in zsh itself. But according to the
> discussion, this is not simple because there are other places where
> one wants the completion system to be sensitive to the user's choice
> of options.
>
> At least in the mean time, removing the repeating single quote would
> be the simplest solution, IMHO.

I agree. I'll post a PR upstream later and when they merge it I'll
backport this to the current package. You are welcome to file the PR
before I do ;)

>
> Note: If for some reason, one wants the single quotes to appear (e.g.
> because the file is automatically generated and the single quotes are
> not removable), then one could write $'' between them:

No need, the file is maintained manually so your patch is enough.


-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

systemd 232-7 MIGRATED to testing

2016-12-07 Thread Debian testing watch 
FYI: The status of the systemd source package
in Debian's testing distribution has changed.

  Previous version: 232-6
  Current version:  232-7

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

2016-12-07 Thread Vincent Lefevre 
On 2016-12-07 10:28:45 -0300, Felipe Sateler wrote:
> Hi ZSH Maintainers,

Not sure they are reading (or have they been Bcc'ed?), but I started
a thread in zsh-workers:

  http://www.zsh.org/mla/workers/2016/msg02588.html

hoping the issue could be solved in zsh itself. But according to the
discussion, this is not simple because there are other places where
one wants the completion system to be sensitive to the user's choice
of options.

At least in the mean time, removing the repeating single quote would
be the simplest solution, IMHO.

Note: If for some reason, one wants the single quotes to appear (e.g.
because the file is automatically generated and the single quotes are
not removable), then one could write $'' between them:

cventin:~> printf %s 'ab''cd' | hd
  61 62 27 63 64|ab'cd|
0005
cventin:~> printf %s 'ab'$'''cd' | hd
  61 62 63 64   |abcd|
0004

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#829180: upstream bug

2016-12-07 Thread Daniel Pocock 


I also reported the issue upstream:

https://github.com/systemd/systemd/issues/4812


and noticed somebody else reported a similar bug upstream for Btrfs:

https://github.com/systemd/systemd/issues/927

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#829180: appears to be failing because of fsck

2016-12-07 Thread Daniel Pocock 
Control: tags -1 - moreinfo

I've observed this problem again today

Looking more closely, I noticed that it started to fsck the mount just
before it tried to mount it.  It didn't appear to wait for fsck to finish:




Dec 03 10:51:37 systemd[1]: Started File System Check on
/dev/mapper/vg00-foo_host1_bak.
Dec 03 10:51:37 systemd[1]:
systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service: cgroup is empty
Dec 03 10:51:37 systemd[1]: Mounting /backup/host1/foo...
Dec 03 10:51:38 systemd[1]: About to execute: /bin/mount -n
/dev/mapper/vg00-foo_host1_bak /backup/host1/foo -t ext4
Dec 03 10:51:38 systemd[1]: backup-host1-foo.mount changed dead -> mounting
Dec 03 10:51:38 systemd[1068]: Executing: /bin/mount -n
/dev/mapper/vg00-foo_host1_bak /backup/host1/foo -t ext4
Dec 03 10:51:38 mount[1068]: mount: /dev/mapper/vg00-foo_host1_bak is
already mounted or /backup/host1/foo busy





More complete log attached

Dec 03 10:51:32 systemd[1]: Installed new job backup-host1-foo.mount/start as 58
Dec 03 10:51:32 systemd[1]: Installed new job dev-mapper-vg00\x2dfoo_host1_bak.device/start as 59
Dec 03 10:51:32 systemd[1]: Installed new job systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service/start as 60
Dec 03 10:51:32 systemd[1]: Expecting device dev-mapper-vg00\x2dfoo_host1_bak.device...
Dec 03 10:51:36 systemd[1]: dev-vg00-foo_host1_bak.device changed dead -> plugged
Dec 03 10:51:36 systemd[1]: dev-mapper-vg00\x2dfoo_host1_bak.device changed dead -> plugged
Dec 03 10:51:36 systemd[1]: Job dev-mapper-vg00\x2dfoo_host1_bak.device/start finished, result=done
Dec 03 10:51:36 systemd[1]: Found device /dev/mapper/vg00-foo_host1_bak.
Dec 03 10:51:36 systemd[1]: dev-disk-by\x2did-dm\x2dname\x2dvg00\x2dfoo_host1_bak.device changed dead -> plugged
Dec 03 10:51:36 systemd[1]: Starting File System Check on /dev/mapper/vg00-foo_host1_bak...
Dec 03 10:51:36 systemd[1]: About to execute: /lib/systemd/systemd-fsck /dev/mapper/vg00-foo_host1_bak
Dec 03 10:51:36 systemd[1]: systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service changed dead -> start
Dec 03 10:51:36 systemd[935]: Executing: /lib/systemd/systemd-fsck /dev/mapper/vg00-foo_host1_bak
Dec 03 10:51:37 systemd-fsck[935]: /dev/mapper/vg00-foo_host1_bak: clean, 269/2293760 files, 8636385/9175040 blocks
Dec 03 10:51:37 systemd[1]: Child 935 belongs to systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service
Dec 03 10:51:37 systemd[1]: systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service: main process exited, code=exited, status=0/SUCCESS
Dec 03 10:51:37 systemd[1]: systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service changed start -> exited
Dec 03 10:51:37 systemd[1]: Job systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service/start finished, result=done
Dec 03 10:51:37 systemd[1]: Started File System Check on /dev/mapper/vg00-foo_host1_bak.
Dec 03 10:51:37 systemd[1]: systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service: cgroup is empty
Dec 03 10:51:37 systemd[1]: Mounting /backup/host1/foo...
Dec 03 10:51:38 systemd[1]: About to execute: /bin/mount -n /dev/mapper/vg00-foo_host1_bak /backup/host1/foo -t ext4
Dec 03 10:51:38 systemd[1]: backup-host1-foo.mount changed dead -> mounting
Dec 03 10:51:38 systemd[1068]: Executing: /bin/mount -n /dev/mapper/vg00-foo_host1_bak /backup/host1/foo -t ext4
Dec 03 10:51:38 mount[1068]: mount: /dev/mapper/vg00-foo_host1_bak is already mounted or /backup/host1/foo busy
Dec 03 10:51:38 systemd[1]: Child 1068 belongs to backup-host1-foo.mount
Dec 03 10:51:38 systemd[1]: backup-host1-foo.mount mount process exited, code=exited status=32
Dec 03 10:51:38 systemd[1]: backup-host1-foo.mount changed mounting -> failed
Dec 03 10:51:38 systemd[1]: Job backup-host1-foo.mount/start finished, result=failed
Dec 03 10:51:38 systemd[1]: Failed to mount /backup/host1/foo.
Dec 03 10:51:38 systemd[1]: Unit backup-host1-foo.mount entered failed state.
Dec 03 10:57:12 systemd[1]: Failed to send unit remove signal for backup-host1-foo.mount: Transport endpoint is not connected
Dec 03 10:57:12 systemd[1]: Failed to send unit remove signal for systemd-fsck@dev-mapper-vg00\x2dfoo_host1_bak.service: Transport endpoint is not connected
Dec 03 10:57:12 systemd[1]: Failed to send unit remove signal for dev-mapper-vg00\x2dfoo_host1_bak.device: Transport endpoint is not connected
Dec 03 10:57:12 systemd[1]: Failed to send unit remove signal for dev-disk-by\x2did-dm\x2dname\x2dvg00\x2dfoo_host1_bak.device: Transport endpoint is not connected
Dec 03 10:57:12 systemd[1]: Failed to send unit remove signal for dev-vg00-foo_host1_bak.device: Transport endpoint is not connected
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: appears to be failing because of fsck

2016-12-07 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 - moreinfo
Bug #829180 [systemd] mounts sometimes fail at boot
Removed tag(s) moreinfo.

-- 
829180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: policy bug

2016-12-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 834228 selinux-policy-default
Bug #834228 [systemd] systemd: /run/utmp is created with the wrong SE Linux 
context
Bug reassigned from package 'systemd' to 'selinux-policy-default'.
No longer marked as found in versions systemd/231-1.
Ignoring request to alter fixed versions of bug #834228 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
834228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#834228: policy bug

2016-12-07 Thread Russell Coker 
reassign 834228 selinux-policy-default
thanks

Turns out this was a policy bug.  I'll fix it soon.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: affects 831924, found 821831 in 4.6.1.3+dfsg-8, found 673972 in 6.2.16~dfsg-2 ...

2016-12-07 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> affects 831924 + ovn-central
Bug #831924 [src:openvswitch] openvswitch: FTBFS with dpkg-buildpackage -A: cp: 
cannot create regular file 
'debian/openvswitch-switch/usr/share/openvswitch/switch/default.template': No 
such file or directory
Added indication that 831924 affects ovn-central
> found 821831 4.6.1.3+dfsg-8
Bug #821831 [ca-certificates-mono] ca-certificates-mono: unowned files after 
purge (policy 6.8, 10.8): /etc/mono/certstore/certs/Trust/*.cer and the 
/etc/mono/certstore/ tree
Marked as found in versions mono/4.6.1.3+dfsg-8.
> found 673972 6.2.16~dfsg-2
Bug #673972 [sympa] sympa: unowned directories after purge: /var/spool/sympa/*
Marked as found in versions sympa/6.2.16~dfsg-2.
> found 839929 8.13.6+dfsg2-1
Bug #839929 [gitlab] gitlab: does not clean up after purge
Marked as found in versions gitlab/8.13.6+dfsg2-1.
> found 670437 2.0.18.4+nmu1
Bug #670437 [pygopherd] pygopherd: unowned files after purge (policy 6.8, 
10.8): /var/gopher/gophermap
Marked as found in versions pygopherd/2.0.18.4+nmu1.
> found 788253 gfarm/2.6.15+dfsg-1
Bug #788253 [init-system-helpers] gfsd: unowned files after purge (policy 6.8, 
10.8): /var/lib/systemd/deb-systemd-helper-masked/gfsd.service
Marked as found in versions gfarm/2.6.15+dfsg-1.
> found 782156 2.02~beta3-3
Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8): 
/boot/grub/{locale, x86_64-xen}/* and some more
Marked as found in versions grub2/2.02~beta3-3.
> found 744165 1.21-3
Bug #744165 [libfakeroot] '/usr/lib/i386-linux-gnu/libfakeroot' not empty so 
not removed
Bug #786386 [libfakeroot] dpkg: warning: while removing libfakeroot:i386, 
directory '/usr/lib/i386-linux-gnu/libfakeroot' not empty so not removed
Marked as found in versions fakeroot/1.21-3.
Marked as found in versions fakeroot/1.21-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
670437: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670437
673972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673972
744165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744165
782156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156
786386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786386
788253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788253
821831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821831
831924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831924
839929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#847203: systemd: journalctl zsh completion fails with RC_QUOTES

2016-12-07 Thread Felipe Sateler 
Hi ZSH Maintainers,

I'd like to ask for your help with the following issue.

As per the title, the journalctl completion function fails when
RC_QUOTES option is set (there is a double single-colon in one of the
completion lines). I asked Vincent to try if using emulate (as I saw
in other completions) worked. Yet it didn't.

On 6 December 2016 at 12:02, Vincent Lefevre  wrote:
> On 2016-12-06 11:40:35 -0300, Felipe Sateler wrote:
>> I think the better fix is to somehow make zsh use default option
>> values when evaluating the completion functions. I see that some
>> completions use `emulate -LR zsh` (although both -L and -R are skipped
>> in some completions). Could you try if that fixes the issue for you?
>
> No, this has no effect. Even
>
> emulate -LR zsh
> unsetopt RC_QUOTES
>
> has no effect. I think that the problem comes from the fact that
> the '' is parsed at completion time.
>
> Actually, the "emulate -LR zsh" is even worse, as I get another
> message with it and my config:
>
> cventin:~> journalctl [TAB]
> (eval):1: no matches found: *:globbed-files
> cventin:~> journalctl
> zsh: do you wish to see all 255 possibilities (88 lines)?
>
> But I don't know the cause.

So the question is, is there a way to ensure a default mode of
operation during the completion function evaluation? With the number
of options zsh provides I find it unlikely that the completions are
compatible with setting/unsetting all possible combinations of them.
So if possible, I'd like to ensure the completions are run in a
consistent environment.

A short reproducer given by Vincent is:

zsf -f
% autoload -U compinit
% compinit
% setopt RC_QUOTES
% journalctl [TAB]
_arguments:comparguments:319: invalid argument: (--directory -D -M
--machine --root --file)'--root=[Operate on catalog hierarchy under
specified directory]:directories:_directories

-- 

Saludos,
Felipe Sateler

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#843063: Related bugs regarding systemctl status nfs-kernel-server

2016-12-07 Thread Martin Steigerwald 
Hello Riccardo,

Bug#847204: nfs-kernel-server: `systemctl status` incorrectly reports server 
"active" even if not started

and

Bug#843063: systemd: does not show failed nfs mount when nfs server not 
available on booting the client

are likely related to one another.

Seems status reporting is completely broken regarding systemd service 
definition. Your choosing of nfs-kernel-server may be better fit tough than my 
choosing of systemd package, but lets see what maintainers say about this.

Thanks,

-- 
Martin Steigerwald  | Trainer

teamix GmbH
Südwestpark 43
90449 Nürnberg

Tel.:  +49 911 30999 55 | Fax: +49 911 30999 99
mail: martin.steigerw...@teamix.de | web:  http://www.teamix.de | blog: 
http://blog.teamix.de

Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard Müller

teamix Support Hotline: +49 911 30999-112
 
 *** Bitte liken Sie uns auf Facebook: facebook.com/teamix ***

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers