Stefano Zacchiroli writes:
> On Sun, Feb 10, 2013 at 03:16:05PM -0800, Nikolaus Rath wrote:
>> The "You can see a non-exhaustive list of Debian trademarks [...] at our
>> trademarks page" link just loops back to the page itself, but there
>> doesn't seem to be a list anywhere on it.
>
> Oh but the
On 10 February 2013 16:54, Matthias Klose wrote:
> There are 126 source packages needing updates. The list of packages
> and maintainers is attached below. I'll file bug reports later (user:
> d...@debian.org, tag: pillow).
>
I see that a few packages were identified to work out of the box by
fed
Le 11/02/2013 19:05, Russ Allbery a écrit :
> Charles Williams writes:
>
>> However, I still have 1 problem. This package controls entire clusters
>> (corosync, pacemaker, et al) and thus is designed with directory rights
>> of 0700 for user hacluster (user used to run corosync). The problem is
>
Package: wnpp
Severity: wishlist
Owner: Jose Calhariz
* Package name: kibana
Version : 0.2.0
Upstream Author : Rashid Khan
* URL : http://kibana.org
* License : ???
Programming Lang: ruby, JavaScript
Description : is a friendly way to view your log data
Package: wnpp
Severity: wishlist
Owner: Alessio Treglia
* Package name: ino-headers
Version : 0.4.0
Upstream Author : Stefano D'Angelo
* URL : http://naspro.sourceforge.net
* License : ISC
Programming Lang: C
Description : C API to execute JavaScript c
Perfect!
Lenin Rossmann(hades)
De: Holger Levsen
Para: debconf-t...@lists.debconf.org
CC: debian-devel-annou...@lists.debian.org; debconf-annou...@lists.debconf.org
Enviado: Lunes, 11 de febrero, 2013 8:43 A.M.
Asunto: [Debconf-announce] deadline for DebCo
Charles Williams writes:
> However, I still have 1 problem. This package controls entire clusters
> (corosync, pacemaker, et al) and thus is designed with directory rights
> of 0700 for user hacluster (user used to run corosync). The problem is
> that 0700 directories are against policy in /usr/s
Hi,
as we haven't done so yet, we've decided to set the deadline for DebConf14
bids for evaluation to February 28th 2013 (23:59 according to your timezone).
Please see https://wiki.debconf.org/wiki/DebConf14 for more information on how
to submit a bid.
Further details of the dc14 timeline will
On Sun, Feb 10, 2013 at 03:16:05PM -0800, Nikolaus Rath wrote:
> The "You can see a non-exhaustive list of Debian trademarks [...] at our
> trademarks page" link just loops back to the page itself, but there
> doesn't seem to be a list anywhere on it.
Oh but there is. The very first section on tha
[ Mail-Followup-To: -project ]
On Sun, Feb 10, 2013 at 12:57:40PM -0800, Steve Langasek wrote:
> This policy states that the contact for trademark questions is
> tradem...@debian.org. Where does this address go? I think it's important
> for transparency that the responsible parties be listed on
* Игорь Пашев , 2013-02-11, 16:46:
The thing I concern it that I need to know exact file name for link
target.
Why is that a problem?
Because final file name is out of my control :-)
It is controlled by dh_installman and dh_compress
Both of them behave in a predictable, documented way.
--
Ja
Hi!
On Mon, Feb 11, 2013 at 5:14 PM, Arno Töll wrote:
> Hi,
>
> On 11.02.2013 14:00, Игорь Пашев wrote:
>> If you look at dh_installman, you will see that it replaces such dummy pages
>> with symlinks.
>
> Which solves your problem, doesn't it? And no, I don't think that's ugly
> - it's a pragmat
Hi,
On 11.02.2013 14:00, Игорь Пашев wrote:
> If you look at dh_installman, you will see that it replaces such dummy pages
> with symlinks.
Which solves your problem, doesn't it? And no, I don't think that's ugly
- it's a pragmatic workaround.
--
with kind regards,
Arno Töll
IRC: daemonkeeper
2013/2/11 Arno Töll :
> Hi,
>
> On 11.02.2013 13:46, Игорь Пашев wrote:
>> I have foo.1 in d/xxx.manpages, and only want to have
>> bar.1 -> foo.1, no matter where foo.1 get its location
>> or how it is compressed.
>
> You should not use symlinks, but source pages such tasks [1].
>
> Install a manp
2013/2/11 Игорь Пашев :
>
> a) compress foo.1 to foo.1.gz (or whatever)
> b) rm bar.1
> c) create symlink bar.1.gz -> foo.1.gz
hm.. dh_compress does it already.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.
And http://www.debian.org/doc/debian-policy/ch-docs.html
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CALL-Q8x707OpshOhd6LzAf3ow_NT5dxz-UmK0YN_CiwR=j1...@mail.gmai
Does it make sense?
1. Extend d/xxx.manpages to form:
bar.1 foo.1
2. dh_installman will create symlink bar.1 -> foo.1
3. dh_compress will take care of symlinks, e. i.:
a) compress foo.1 to foo.1.gz (or whatever)
b) rm bar.1
c) create symlink bar.1.gz -> foo.1.gz
I remember such a thing in Sla
Hi,
On 11.02.2013 13:46, Игорь Пашев wrote:
> I have foo.1 in d/xxx.manpages, and only want to have
> bar.1 -> foo.1, no matter where foo.1 get its location
> or how it is compressed.
You should not use symlinks, but source pages such tasks [1].
Install a manpage like:
bar.1:
.so man1/foo.1
[1
2013/2/11 Jakub Wilk :
>> The thing I concern it that I need to know exact file name for link
>> target.
>
>
> Why is that a problem?
Because final file name is out of my control :-)
It is controlled by dh_installman and dh_compress
I have foo.1 in d/xxx.manpages, and only want to have
bar.1 ->
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
My name is Chuck and I am new to the list. I have already posted this
to debian-mentors but was advised to post here as well.
I am currently working on building a package based on the ClusterLabs
Hawk web GUI. Thanks to the people in #deb
2013/2/11 Kartik Mistry :
> On Mon, Feb 11, 2013 at 4:48 PM, Игорь Пашев wrote:
>> Is there any handy way to "link" manpages? That is I could just write
>> "`bar` is described in `foo`". I know about .so, but looks urgly because
>> debhelper finally replaces it with symlink :-)
>
> dh_link will do
* Игорь Пашев , 2013-02-11, 15:18:
The thing I concern it that I need to know exact file name for link
target.
Why is that a problem?
If I write foo.1m in d/XXX.manpages, it results in foo.1M.gz (with
capital M) in a package.
"If dh_installman seems to install a man page into the wrong sect
On Mon, Feb 11, 2013 at 4:48 PM, Игорь Пашев wrote:
> Is there any handy way to "link" manpages? That is I could just write
> "`bar` is described in `foo`". I know about .so, but looks urgly because
> debhelper finally replaces it with symlink :-)
dh_link will do.
For example: dh_link usr/share/
Hi all.
Some manpages describe several utilities in one page,
so I have to create symlink for manpages, e. g. dcopy.1.gz -> clri.1.gz
(while clri.1.gz is installed with dh_installman).
The thing I concern it that I need to know exact file name for link target.
If I write foo.1m in d/XXX.manpages,
24 matches
Mail list logo
