Hello,
On Wed, 22 Aug 2007, Luis Rodrigo Gallardo Cruz wrote:
I have uploaded a new version with the suggested fixes. Following your
sugestion I used 3:4.20-4~1 as version. If you consider it worthy of
upload, please change it to -4. And please build with -v3:4.20-2
Thanks for pointing this
On Mon, Aug 20, 2007 at 09:51:49AM +1000, Ben Finney wrote:
If that's the case, what they distribute isn't free
software — unless any recipient can get that source.
Certainly, for it to be included in Debian, we need to
distribute the *entire* corresponding source form of the
work.
Is this
Hi, Felipe.
On Aug 18 2007, Felipe Sateler wrote:
This way, you have automatic update of the authors when updating to a
new upstream version.
This is, indeed, a good way of managing projects with large numbers of
contributors.
Regards, Rogério.
--
Rogério Brito : [EMAIL
On Aug 18 2007, Felipe Sateler wrote:
This is a bug in the xine-lib package because it doesn't ship the
AUTHORS file, even though copyright references it. Filed as #438677.
Thanks for letting me know about this. It is quite welcome.
Regards, Rogério.
--
Rogério Brito : [EMAIL
On Aug 22 2007, Kartik Mistry wrote:
It builds these binary packages:
tagtool- Tool to tag and rename MP3 and Ogg Vorbis files
What does this tool gives the user that, say, easytag (one of the most
powerful tag programs around that I know of) doesn't?
Regards, Rogério.
--
Rogério Brito
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have an application I'd like to package --- plasticfs. Unfortunately, due to
glibc weirdnesses, it needs a copy of glibc built using custom (non-standard)
options. Is this doable, or is it likely to be a lost cause?
Note: it doesn't need the
On Thu, Aug 23, 2007 at 08:56:50PM +0100, David Given wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have an application I'd like to package --- plasticfs. Unfortunately, due to
glibc weirdnesses, it needs a copy of glibc built using custom (non-standard)
options. Is this doable, or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Pryzby wrote:
[...]
I have an application I'd like to package --- plasticfs. Unfortunately, due
to
glibc weirdnesses, it needs a copy of glibc built using custom (non-standard)
options. Is this doable, or is it likely to be a lost cause?
On Thu, Aug 23, 2007 at 10:26:35PM +0100, David Given wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Pryzby wrote:
[...]
I have an application I'd like to package --- plasticfs. Unfortunately,
due to
glibc weirdnesses, it needs a copy of glibc built using custom
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Justin Pryzby wrote:
[...]
which means the
preloader library doesn't get a chance to override it. plasticfs wants a
glibc
compiled with --disable-hidden-plt to expose this interface.
I still don't understand why?
I *presume* so that plasticfs
On Thu, 23 Aug 2007 22:26:35 +0100
David Given [EMAIL PROTECTED] wrote:
Please can you give the details of why this is necessary?
It's an LD_PRELOAD hack. When glibc calls itself --- for example when fopen()
calls open() --- it does so using a hidden private interface, which means the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Williams wrote:
[...]
Do the work and come back to the list with
a detailed reasoning for what is a MAJOR packaging decision. This isn't
yet another customised version of a package it is a COPY of GLIBC!
Don't shout at me, please.
Yes, I am
On Fri, 24 Aug 2007, David Given wrote:
Currently I am merely trying to figure out whether upstream's idea
of using a customised glibc is possible on Debian
It's always possible to do so. However, actually doing so requires
that you convince the security team, the maintainer(s), and the
release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Armstrong wrote:
[...]
The people who have responded to you so far strongly suspect that it's
not worth the effort, but without knowing why the glibc we already
distribute can't be used, it's hard for us to give you a definitive
answer.
14 matches
Mail list logo
