-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
martin f krafft wrote:
[ snip ]
> I am using dh_strip --keep-debug to keep these binaries purposely in
> place. Thus, I should probably override the last two errors.
> However, I am unsure about the first six lines. What do they mean?
> What am I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
martin f krafft wrote:
[ snip ]
> I am using dh_strip --keep-debug to keep these binaries purposely in
> place. Thus, I should probably override the last two errors.
> However, I am unsure about the first six lines. What do they mean?
> What am I
Hallo Colin,
* Colin Watson <[EMAIL PROTECTED]> [2004-07-30 17:41]:
> > > I'm looking for a sponsor to upload a new gbuffy version for me. I've
> > > decided to adopt the gbuffy package since it is in bad shape, I use it
> > > every day and I wouldn't like it to be removed from Debian. The wnpp
>
Hallo Colin,
* Colin Watson <[EMAIL PROTECTED]> [2004-07-30 17:41]:
> > > I'm looking for a sponsor to upload a new gbuffy version for me. I've
> > > decided to adopt the gbuffy package since it is in bad shape, I use it
> > > every day and I wouldn't like it to be removed from Debian. The wnpp
>
I maintain libcwd. For the latest release 0.99.37-2, linda reports
the following problems:
E: libcwd0; Object /usr/lib/debug/usr/lib/libcwd.so.0.99.37 is not directly
linked against libc.
E: libcwd0; Object /usr/lib/debug/usr/lib/libcwd_r.so.0.99.37 is not directly
linked against libc.
E: libcwd
On 2004-07-30 Frank Küster <[EMAIL PROTECTED]> wrote:
> Justin Pryzby <[EMAIL PROTECTED]> schrieb:
> > I think what you want is described in the "dpkg programmers manual":
> >
> > A directory will never be replaced by a symbolic links to a
> > directory or vice versa; instead, the existing
Justin Pryzby <[EMAIL PROTECTED]> schrieb:
> I think what you want is described in the "dpkg programmers manual":
>
> A directory will never be replaced by a symbolic links to a
> directory or vice versa; instead, the existing state (symlink or
> not) will be left alone and dpkg
I maintain libcwd. For the latest release 0.99.37-2, linda reports
the following problems:
E: libcwd0; Object /usr/lib/debug/usr/lib/libcwd.so.0.99.37 is not directly linked
against libc.
E: libcwd0; Object /usr/lib/debug/usr/lib/libcwd_r.so.0.99.37 is not directly linked
against libc.
E: libcwd
On Thu, Jul 29, 2004 at 11:41:37PM +0200, Laszlo 'GCS' Boszormenyi wrote:
> I have a seemingly stupid question. Say I am not a DD yet, and has a
> security bug in a package I help maintaining. Upstream fixed it, so the
> package is ready, but upstream requires new library version from a
> depende
I think what you want is described in the "dpkg programmers manual":
A directory will never be replaced by a symbolic links to a
directory or vice versa; instead, the existing state (symlink or
not) will be left alone and dpkg will follow the symlink if
there is one
On 2004-07-30 Frank Küster <[EMAIL PROTECTED]> wrote:
> Justin Pryzby <[EMAIL PROTECTED]> schrieb:
> > I think what you want is described in the "dpkg programmers manual":
> >
> > A directory will never be replaced by a symbolic links to a
> > directory or vice versa; instead, the existing
Hi,
I think I have raised this somewhere before, but I can't remember or
find it in the list archives. In the tetex-bin package, there is a
symlink:
/usr/share/texmf/web2c --> /var/lib/texmf/web2c
Now I want to make /usr/share/texmf/web2c an ordinary directory with
some static files in it, while
Justin Pryzby <[EMAIL PROTECTED]> schrieb:
> I think what you want is described in the "dpkg programmers manual":
>
> A directory will never be replaced by a symbolic links to a
> directory or vice versa; instead, the existing state (symlink or
> not) will be left alone and dpkg
On Thu, Jul 29, 2004 at 11:41:37PM +0200, Laszlo 'GCS' Boszormenyi wrote:
> I have a seemingly stupid question. Say I am not a DD yet, and has a
> security bug in a package I help maintaining. Upstream fixed it, so the
> package is ready, but upstream requires new library version from a
> depende
I think what you want is described in the "dpkg programmers manual":
A directory will never be replaced by a symbolic links to a
directory or vice versa; instead, the existing state (symlink or
not) will be left alone and dpkg will follow the symlink if
there is one
Hi,
I think I have raised this somewhere before, but I can't remember or
find it in the list archives. In the tetex-bin package, there is a
symlink:
/usr/share/texmf/web2c --> /var/lib/texmf/web2c
Now I want to make /usr/share/texmf/web2c an ordinary directory with
some static files in it, while
On Чтв, 2004-07-29 at 23:48 +0400, Dan Korostelev wrote:
> I made a package for rhythmbox-applet (look on mentors.debian.net) and
> now looking for a sponsor. Please, check it out and upload to Debian if
> you want. Any suggestions accepted :)
And "oh yes" thing:
* Package name: rhythmbox-app
On ÐÑÐ, 2004-07-29 at 23:48 +0400, Dan Korostelev wrote:
> I made a package for rhythmbox-applet (look on mentors.debian.net) and
> now looking for a sponsor. Please, check it out and upload to Debian if
> you want. Any suggestions accepted :)
And "oh yes" thing:
* Package name: rhythmbox-app
18 matches
Mail list logo
