Package: maint-guide-zh-cn
Version: 1.2.25
Severity: minor
1) in section 5.22,
如果你希望使用版本控制系统(VCS)时，你可以创建一个分支(例如叫做 upstream) 来跟踪上游代码(对于 Git 而言典型的是 master
分支)，和另一个分支来跟踪你的 Debian 软件包。对于后者，通常会将未应用补丁的上游代码和你的 debian/* 文件放在一起以便容易合并上游的新代码。
while original statement is:
When you want to manage Debian
cap_from_text(3) exists on my system:
zhi@debian-testing:~/work/debian/libcap2/debian$ ls
/usr/share/man/man3/cap_from_text*
/usr/share/man/man3/cap_from_text.3.gz
zhi@debian-testing:~/work/debian/libcap2/debian$ dpkg -S
/usr/share/man/man3/cap_from_text.3.gz
libcap-dev:
I have tried to use pam_cap. It works! This bug perhaps shall be closed.
First, my system has a user named 'test1'. I edited
/etc/security/capability.conf:
...
cap_dac_overridetest1
...
Then, use 'su test1'.
zhi@debian-testing:/etc/pam.d$ su test1
Password:
After that, I check the
Package: libcap2-bin
Version: 1:2.21-1
Severity: minor
I have run the following command:
root@debian-testing:/home/zhi/work/tmp# setcap 0+ep t
root@debian-testing:/home/zhi/work/tmp# getcap t
t = cap_chown+ep
root@debian-testing:/home/zhi/work/tmp# setcap -r t
I just noticed that upstream has fixed it:
commit 93c92ed1d826c6759bb83d2168ee818a05280f35
Author: Kamil Dudka kdu...@redhat.com
Date: Wed Dec 22 14:13:27 2010 +0100
getfattr: return non-zero exit code on failure
reported by Jean-Pierre André at https://bugzilla.redhat.com/660619
@@ -1,3 +1,10 @@
+attr (1:2.4.46-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * fix bug 520659, modify do_print() return code.
+
+ -- Zhi Li lizhi1...@gmail.com Mon, 27 Jun 2011 04:18:16 -0400
+
attr (1:2.4.46-1) unstable; urgency=low
* New upstream release (Closes: #626622).
diff
in libcap2-bin/debian/control, remove
those files that were not generated.
+
+ -- Zhi Li lizhi1...@gmail.com Thu, 23 Jun 2011 11:02:25 +0800
+
libcap2 (1:2.21-1) unstable; urgency=low
* New upstream release.
diff -Nru libcap2-2.21/debian/control libcap2-2.21/debian/control
--- libcap2-2.21
7 matches
Mail list logo
