Re: How to build only linux-image-2.6.18-6-686

[Marc Haber]

On Fri, 6 Jun 2008 22:31:09 -0400, [EMAIL PROTECTED]
(Lennart Sorensen) wrote:
>On Fri, Jun 06, 2008 at 10:14:09PM +0200, Mauro Ziliani wrote:
>> Hi all.
>> I need to rebuild only the linux-image-2.6.18-6-686 deb package from 
>> source code.
>> How can I do that without rebuild all packages in linux-2.6.18 sources 
>> (xen, k7,vserver)?
>
>Remove the other ones from debian/arch/i386/defines, and then run
>debian/rules setupm which should regenerate the control file and exit,
>then you should be able to run the normal package build.

Shouldn't that be easier to do, and - most of all - documented?

Greetings
Marc

-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Holger Levsen]

Hi Marc,

On Saturday 07 June 2008 11:51, Marc Haber wrote:
> Shouldn't that be easier to do,

Send patches?! ;)

> and - most of all - documented? 

http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage


regards,
Holger


pgprFz3NRVvRf.pgp
Description: PGP signature

Re: Automatic debiian installation

[Michael Tautschnig]

[sorry for cross-posting, I guess this thread should move away from
debian-devel, but I'm not subscribed to any of the others]

> Hello,
>
> I would like to use a system to install automatically all my debian pc.
> But
> i don't know wich could be the best between FAI and  PRESSEED.
>
> Somebody could explain the difference 
>
> the avantage and disavantage of the two methodes...!
>

It depends a lot on your specific needs. If you're fine with setting whatever is
debconf-configurable (be it at install time, using d-i's preseeding options, or
rather at the level of the installed packages), preseeding may be an appropriate
way to go. 

FAI, on the other hand, is a very flexible framework for installing systems.
Debconf preseeding is supported, but just one option out of many. You might want
to run several scripts for fine-tuning your system, copy over config files, etc.
Flexibility comes at the cost of probably slightly higher complexity, but people
tend to get to know it quite easily.

HTH,
Michael



pgpRGVX9yoBaG.pgp
Description: PGP signature

Bug#484982: ITP: libdlna -- A reference DLNA implementation for Linux

[Rob Andrews]

Package: wnpp
Severity: wishlist
Owner: Rob Andrews <[EMAIL PROTECTED]>


* Package name: libdlna
  Version : 0.2.3
  Upstream Author : Benjamin Zores <[EMAIL PROTECTED]>
* URL : http://libdlna.geexbox.org/
* License : LGPL
  Programming Lang: C
  Description : A reference DLNA implementation for Linux

libdlna aims at being the reference open-source implementation of DLNA
(Digital Living Network Alliance) standards. Its primary goal is to
provide DLNA support to uShare, an embedded DLNA & UPnP A/V Media
Server, but it will be used to build both DLNA servers and players in
the long term.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Lennart Sorensen]

On Sat, Jun 07, 2008 at 11:51:04AM +0200, Marc Haber wrote:
> Shouldn't that be easier to do, and - most of all - documented?

Playing with source packages isn't normal.  It used to be much worse
(2.6.8 in sarge involved building multiple packages, one which depended
on the other).  The package is designed to make the life of the kernel
image developers easy, not to make the life of people doing weird things
for themselves easier.

You should be installing the linux-source-x.x.x package instead and
using make-kpkg to build custom kernels.  The source package (rather
than the linux-source-x.x.x binary package) is not meant to make custom
kernels.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Packaging a project using cmake

[Mathieu Malaterre]

Hi there,

  I am working on cleaning up the packaging of my project (GDCM) using
cmake so that the .deb produced is consistant with the debian package.
I was wondering if anyone had done the work before ? I am currently
struggling on how to do it properly when installing python module
(what is the layout, how do you know the python target installation
directory...)

Thanks !

-- 
Mathieu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Michael Banck]

On Sat, Jun 07, 2008 at 06:04:53PM +0200, Mathieu Malaterre wrote:
>   I am working on cleaning up the packaging of my project (GDCM) using
> cmake so that the .deb produced is consistant with the debian package.

Not sure what you mean here, a .deb is a debian package, so what is
needed to be consistent?

> I was wondering if anyone had done the work before ? I am currently
> struggling on how to do it properly when installing python module
> (what is the layout, how do you know the python target installation
> directory...)

If you mean, how to package software which uses cmake and python, you
could take a look at the opensync package from experimental (version
0.36 currently) for example.


Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Changes to the ddpo-by-mail service

[Emilio Pozuelo Monfort]

Raphael Geissert wrote:
> Emilio Pozuelo Monfort wrote:
> 
>> Raphael Hertzog wrote:
>>> And the fact that he sends one mail per e-mail instead of one mail per
>>> package makes it even better (far less annoying).
>> Agreed, specially for people or teams who maintain lots of packages.
>>
>> Raphael, would it be possible for you to do the same with DEHS mails?
> 
> I really don't understand your request.

I mean: whenever DEHS sends mails about new upstream releases, I get a lot (20
mails on may 28th) of mails in the pkg-gnome-maintainers list, one for each
package, but when for DDPO I get just one mail with the info for all the 
packages.

I think it would be nice if DDPO sent one mail to the maintainer, say once a
week, instead of the current behaviour. Or otherwise if it would be possible to
blacklist packages, as I don't think any Debian GNOME maintainer finds that
information useful, as we are subscribed to the gnome-changes list and we have
overview pages saying what packages are outdated et al.

> 
> Correct me if I'm wrong, but you can't send an email to a 'group of
> maintainers' via the PTS (e.g. the maintainers of foo, bar, and moo).

Hmm, you may be right. DDPO does it, but it indeed looks like it doesn't use the
PTS.

Cheers,
Emilio



signature.asc
Description: OpenPGP digital signature

Re: Packaging a project using cmake

[Sune Vuorela]

On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
> Hi there,
>
>   I am working on cleaning up the packaging of my project (GDCM) using
> cmake so that the .deb produced is consistant with the debian package.
> I was wondering if anyone had done the work before ? I am currently
> struggling on how to do it properly when installing python module
> (what is the layout, how do you know the python target installation
> directory...)

Are you talking about using cmake to *build the deb*  or just about
packaging a project using cmake?

If you are talking about the former, please forget it.

/Sune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Mathieu Malaterre]

On Sat, Jun 7, 2008 at 7:47 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote:
> On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
>> Hi there,
>>
>>   I am working on cleaning up the packaging of my project (GDCM) using
>> cmake so that the .deb produced is consistant with the debian package.
>> I was wondering if anyone had done the work before ? I am currently
>> struggling on how to do it properly when installing python module
>> (what is the layout, how do you know the python target installation
>> directory...)
>
> Are you talking about using cmake to *build the deb*  or just about
> packaging a project using cmake?
>
> If you are talking about the former, please forget it.

What do you mean ? Indeed I want the whole process from src to .deb
handled by cmake.

I made some prelimianary versions at:

http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=603764

You need to use cmake 2.6.0 (none of the dpkg-* utils are needed in
the process).

But if you take the souce tarball, dpkg-buildpackage should work too. Ref:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg03663.html

Thanks,
-- 
Mathieu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

A dream of the Debian-logo

[József Makay]

This picture is a dream of the Debian-logo in the future...
<>

Re: Packaging a project using cmake

[Sune Vuorela]

On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
> On Sat, Jun 7, 2008 at 7:47 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote:
>> On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
>>> Hi there,
>>>
>>>   I am working on cleaning up the packaging of my project (GDCM) using
>>> cmake so that the .deb produced is consistant with the debian package.
>>> I was wondering if anyone had done the work before ? I am currently
>>> struggling on how to do it properly when installing python module
>>> (what is the layout, how do you know the python target installation
>>> directory...)
>>
>> Are you talking about using cmake to *build the deb*  or just about
>> packaging a project using cmake?
>>
>> If you are talking about the former, please forget it.
>
> What do you mean ? Indeed I want the whole process from src to .deb
> handled by cmake.

Then please forget it. That doesn't make proper debs.

> I made some prelimianary versions at:
>
> http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=603764

> You need to use cmake 2.6.0 (none of the dpkg-* utils are needed in
> the process).

And this is where the cmake folks are wrong (I once wrote them a long
email about it).

>
> But if you take the souce tarball, dpkg-buildpackage should work too. Ref:
>
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg03663.html

I stopped looking when
 * no builddepenencies except cmake and debhelper
 * one package filled with development packages and stuff.

/Sune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Mathieu Malaterre]

On Sat, Jun 7, 2008 at 8:07 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote:
> On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
>> On Sat, Jun 7, 2008 at 7:47 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote:
>>> On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
 Hi there,

   I am working on cleaning up the packaging of my project (GDCM) using
 cmake so that the .deb produced is consistant with the debian package.
 I was wondering if anyone had done the work before ? I am currently
 struggling on how to do it properly when installing python module
 (what is the layout, how do you know the python target installation
 directory...)
>>>
>>> Are you talking about using cmake to *build the deb*  or just about
>>> packaging a project using cmake?
>>>
>>> If you are talking about the former, please forget it.
>>
>> What do you mean ? Indeed I want the whole process from src to .deb
>> handled by cmake.
>
> Then please forget it. That doesn't make proper debs.

because...

>> I made some prelimianary versions at:
>>
>> http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=603764
>
>> You need to use cmake 2.6.0 (none of the dpkg-* utils are needed in
>> the process).
>
> And this is where the cmake folks are wrong (I once wrote them a long
> email about it).

link, please ?

>>
>> But if you take the souce tarball, dpkg-buildpackage should work too. Ref:
>>
>> http://www.mail-archive.com/[EMAIL PROTECTED]/msg03663.html
>
> I stopped looking when
>  * no builddepenencies except cmake and debhelper
>  * one package filled with development packages and stuff.

Well thanks ! That was a good bug report, indeed I forgot to duplicate
cmake stuff into the equivalent debian file. I'll fix ASAP. But it
should read:

  SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libc6, libstdc++6 (>= 4.0.2-4),
libuuid1, zlib1g (>= 1:1.2.1), libgcc1 (>= 1:4.0.2), libexpat1, swig")

  Everytime I look at a debian package, it seems that those values are
somehow hardcoded. I would think that a human is actually checking
those versions, correct ? Or is there a tool that would say:

$ superdupertool libfoo.so
=> this lib requires libstdc++6 at least version 4.0.2

Thanks,
-- 
Mathieu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Sune Vuorela]

On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
>>> What do you mean ? Indeed I want the whole process from src to .deb
>>> handled by cmake.
>>
>> Then please forget it. That doesn't make proper debs.
>
> because...

Because they doesn't use
 - dpkg-shlibdeps
 - python-support|python-central for python stuff
 - running ldconfig in postinst
 - interacting with postinst/preinst in other ways

>> And this is where the cmake folks are wrong (I once wrote them a long
>> email about it).
>
> link, please ?

To Alex Neundorff and Bill Hoffmann.

> Well thanks ! That was a good bug report, indeed I forgot to duplicate
> cmake stuff into the equivalent debian file. I'll fix ASAP. But it
> should read:
>
>   SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libc6, libstdc++6 (>= 4.0.2-4),
> libuuid1, zlib1g (>= 1:1.2.1), libgcc1 (>= 1:4.0.2), libexpat1, swig")

you do this *manually* ?

>   Everytime I look at a debian package, it seems that those values are
> somehow hardcoded. I would think that a human is actually checking
> those versions, correct ? Or is there a tool that would say:
>
> $ superdupertool libfoo.so
>=> this lib requires libstdc++6 at least version 4.0.2

dpkg-shlibdeps run during build does that and then dpkg-gencontrol
replaces the ${shlibs:Depends} in control file

/Sune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Eduard Bloch]

#include 
* Sune Vuorela [Sat, Jun 07 2008, 06:28:03PM]:

> >   SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libc6, libstdc++6 (>= 4.0.2-4),
> > libuuid1, zlib1g (>= 1:1.2.1), libgcc1 (>= 1:4.0.2), libexpat1, swig")
> 
> you do this *manually* ?

Relay, he cannot beat
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=258723 ;-)

Regards,
Eduard.

-- 
 Ja, da hast Du Dich mal wieder nur von meinen riesigen
sekundären Geschlechtsmerkmalen leiten lassen ;)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A dream of the Debian-logo

[Wesley J. Landaker]

On Saturday 07 June 2008 11:44:42 József Makay wrote:
> This picture is a dream of the Debian-logo in the future...

Very cool looking!

-- 
Wesley J. Landaker <[EMAIL PROTECTED]> 
OpenPGP FP: 4135 2A3B 4726 ACC5 9094  0097 F0A9 8A4C 4CD6 E3D2


signature.asc
Description: This is a digitally signed message part.

Re: A dream of the Debian-logo

[Miriam Ruiz]

It's a very nice picture, but I guess maybe it would belong more to
somewhere like DebianArt [1] than to this mailing list.

Greetings,
Miry

[1] http://www.debianart.org


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A dream of the Debian-logo

[Deepak Tripathi]

Hi,
I do think so that its a really nice picture , but one of my suggestion is
can't you create "e"  in Circle/Spiral way.
that is my personal opinion ,your work is extremely good.


On Sun, Jun 8, 2008 at 12:39 AM, Miriam Ruiz <[EMAIL PROTECTED]> wrote:

> It's a very nice picture, but I guess maybe it would belong more to
> somewhere like DebianArt [1] than to this mailing list.
>
> Greetings,
> Miry
>
> [1] http://www.debianart.org
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
>
>


-- 
Deepak Tripathi
E3 71V3 8Y C063 (We Live By Code)
http://deepkatripathi.blogspot.com

Re: Packaging a project using cmake

[Mathieu Malaterre]

On Sat, Jun 7, 2008 at 8:28 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote:
> On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
 What do you mean ? Indeed I want the whole process from src to .deb
 handled by cmake.
>>>
>>> Then please forget it. That doesn't make proper debs.
>>
>> because...
>
> Because they doesn't use
>  - dpkg-shlibdeps

I cannot figure out how to get this thing working. It keeps on
complaining when fed with an exe that I just build :
dpkg-shlibdeps: failure: no dependency information found for
/tmp/local/lib/libgdcmjpeg12.so.62.1 (used by
/tmp/local/bin/gdcmdump).

>  - python-support|python-central for python stuff

That's the thing I as asking for in the first place, will look into it, thanks.

>  - running ldconfig in postinst

AFAIK that's not always required...

>  - interacting with postinst/preinst in other ways

I can tell cmake to package my own postinst/preinst file, eg:

http://gdcm.svn.sourceforge.net/viewvc/gdcm/Sandbox/gdcmreadahead/

>>> And this is where the cmake folks are wrong (I once wrote them a long
>>> email about it).
>>
>> link, please ?
>
> To Alex Neundorff and Bill Hoffmann.

I originally wrote the deb plugin, Alex simply integrated in cmake. If
you've lost the email, I'll check with them.

>> Well thanks ! That was a good bug report, indeed I forgot to duplicate
>> cmake stuff into the equivalent debian file. I'll fix ASAP. But it
>> should read:
>>
>>   SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libc6, libstdc++6 (>= 4.0.2-4),
>> libuuid1, zlib1g (>= 1:1.2.1), libgcc1 (>= 1:4.0.2), libexpat1, swig")
>
> you do this *manually* ?

I had to look at what packages I had installed on my machine. Using
ldd I just selected a couple of them (I might be missing some).
As I said I could not figure out what tool was used to dump that
particular line in the control file.

>>   Everytime I look at a debian package, it seems that those values are
>> somehow hardcoded. I would think that a human is actually checking
>> those versions, correct ? Or is there a tool that would say:
>>
>> $ superdupertool libfoo.so
>>=> this lib requires libstdc++6 at least version 4.0.2
>
> dpkg-shlibdeps run during build does that and then dpkg-gencontrol
> replaces the ${shlibs:Depends} in control file

ok

All this is kindda new to me. When I was looking at debian package
that use cmake to be build, I assumed the value in the control files
where hardcoded.

So, I changed my mind, I am not looking into deb-packaging my project
directly, but instead have the minimum debian specific files that
start cmake and in the end produce a valid/consistant .deb file. I was
suggest libopensync, is this a good start ?

Thanks again,
-- 
Mathieu
Ps: I had the discussion with Alex whether or not we should rely on
the dpkg-* tool to build a .deb file, since it appeared to me as being
only simply a 'ar' file , I assumed we could bypass them. Anyway
dpkg-shlibdeps seems to be a much more complex tool than just objdump
or ldd on the lib, this will be difficult to avoid.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Request for qsynth NMU

[Sergey Rudchenko]

Hello, Debian developers,

During the ubuntu package merging I have found that package qsynth is
strongly outdated (0.2.5 from 2006-03-05 against 0.3.2 from 2007-12-1) and
formed not so well (changes directly to the original source and numerous
issues in debian/*). I already have repackaged it from scratch carefully so
it needs at least sponsorship for upload.
I would like to maintain it and, possibly, several more packages to help
Debian.

--
Best regards,
Sergey Rudchenko

Re: Packaging a project using cmake

[Russ Allbery]

"Mathieu Malaterre" <[EMAIL PROTECTED]> writes:

> You need to use cmake 2.6.0 (none of the dpkg-* utils are needed in
> the process).

I believe the current thinking on this is that using the dpkg-* utilities
is required for uploads to the Debian repositories.  Even if you can
duplicate their behavior now, we don't define exactly what they do in
Policy.  Policy just says "use them."  That means that there isn't a
standard to which to write other tools that do the same thing.

(I personally think it would be cool if we had that, in that "it's a lot
of work but being there would be kind of neat" sort of way.)

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Russ Allbery]

"Mathieu Malaterre" <[EMAIL PROTECTED]> writes:
> On Sat, Jun 7, 2008 at 8:28 PM, Sune Vuorela <[EMAIL PROTECTED]> wrote:

>>  - running ldconfig in postinst

> AFAIK that's not always required...

Policy 8.1.1.

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Request for qsynth NMU

[Vincent Bernat]

OoO En  ce début de soirée du  samedi 07 juin 2008,  vers 21:19, "Sergey
Rudchenko" <[EMAIL PROTECTED]> disait:

> During the ubuntu package merging I have found that package qsynth is strongly
> outdated (0.2.5 from 2006-03-05 against 0.3.2 from 2007-12-1) and formed not 
> so
> well (changes directly to the original source and numerous issues in 
> debian/*).
> I already have repackaged it from scratch carefully so it needs at least
> sponsorship for upload.
> I would like to maintain it and, possibly, several more packages to help
> Debian.

Hi Sergey!

Did you contact the current maintainer? It would be easier if he orphans
himself the package.
-- 
printk(KERN_ERR "msp3400: chip reset failed, penguin on i2c bus?\n");
2.2.16 /usr/src/linux/drivers/char/msp3400.c


pgphm9nWbbJJA.pgp
Description: PGP signature

Bug#485037: ITP: tomcat-native -- Tomcat native library using apache portable runtime

[Michael Koch]

Package: wnpp
Severity: wishlist
Owner: Michael Koch <[EMAIL PROTECTED]>


* Package name: tomcat-native
  Version : 1.1.13
  Upstream Author : Apache Software Foundation
* URL : http://tomcat.apache.org/
* License : Apache License 2.0
  Programming Lang: C
  Description : Tomcat native library using apache portable runtime

 Tomcat can use the Apache Portable Runtime to provide superior scalability,
 performance, and better integration with native server technologies. 
 The Apache Portable Runtime is a highly portable library that is at the
 heart of Apache HTTP Server 2.x. APR has many uses, including access to
 advanced IO functionality (such as sendfile, epoll and OpenSSL), OS level
 functionality (random number generation, system status, etc), and native
 process handling (shared memory, NT pipes and Unix sockets).
 . 
 These features allows making Tomcat a general purpose webserver, will
 enable much better integration with other native web technologies, and
 overall make Java much more viable as a full fledged webserver platform
 rather than simply a backend focused technology.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Tzafrir Cohen]

On Sat, Jun 07, 2008 at 11:31:14AM -0400, Lennart Sorensen wrote:
> On Sat, Jun 07, 2008 at 11:51:04AM +0200, Marc Haber wrote:
> > Shouldn't that be easier to do, and - most of all - documented?
> 
> Playing with source packages isn't normal.  It used to be much worse
> (2.6.8 in sarge involved building multiple packages, one which depended
> on the other).  The package is designed to make the life of the kernel
> image developers easy, not to make the life of people doing weird things
> for themselves easier.
> 
> You should be installing the linux-source-x.x.x package instead and
> using make-kpkg to build custom kernels.  The source package (rather
> than the linux-source-x.x.x binary package) is not meant to make custom
> kernels.

My problem with make-kpkg has always been that I could never rely on its
generated -headers packages to actually work.

So it was fine to build a kernel. But if I wanted to build some modules
for that kernel, I still have a problem.

My ugly workaround is to keep the source directory and hope for the
best.

-- 
Tzafrir Cohen | [EMAIL PROTECTED] | VIM is
http://tzafrir.org.il || a Mutt's
[EMAIL PROTECTED] ||  best
ICQ# 16849754 || friend


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Packaging a project using cmake

[Sune Vuorela]

On 2008-06-07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
 And this is where the cmake folks are wrong (I once wrote them a long
 email about it).
>>>
>>> link, please ?
>>
>> To Alex Neundorff and Bill Hoffmann.
>
> I originally wrote the deb plugin, Alex simply integrated in cmake. If
> you've lost the email, I'll check with them.

The content is what I wrote earlier + something more, like:
 - binary incompability between distributions. A package for debian
   should be build on a debian system and so on
* Different compiler flags
* Different sonames of related libraries
 - there is as mentioned the dpkg-shlibdeps issue, but also the issue
   with generation of shlibs files
 - Interactino with debian specific changes to other packages

> I had to look at what packages I had installed on my machine. Using
> ldd I just selected a couple of them (I might be missing some).
> As I said I could not figure out what tool was used to dump that
> particular line in the control file.

Don't.


> ok
>
> All this is kindda new to me. When I was looking at debian package
> that use cmake to be build, I assumed the value in the control files
> where hardcoded.

Just to make everything clear:  You wrote a tool to bulid debian
packages without actually looking in to the policies for doing debian
packages? And get tools released to actually do this?

> So, I changed my mind, I am not looking into deb-packaging my project
> directly, but instead have the minimum debian specific files that
> start cmake and in the end produce a valid/consistant .deb file. I was
> suggest libopensync, is this a good start ?

I haven't looked at opensync, but usually Michael Banck knows what he is
doing.
Another thing to look at could be kde4 or some of the related packages
like soprano.

/Sune


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Lennart Sorensen]

On Sat, Jun 07, 2008 at 08:31:47PM +, Tzafrir Cohen wrote:
> My problem with make-kpkg has always been that I could never rely on its
> generated -headers packages to actually work.

Odd, the headers it generated allways worked for me.

> So it was fine to build a kernel. But if I wanted to build some modules
> for that kernel, I still have a problem.
> 
> My ugly workaround is to keep the source directory and hope for the
> best.

Nothing wrong with doing that if you are compiling the kernel anyhow.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Tzafrir Cohen]

On Sat, Jun 07, 2008 at 05:23:19PM -0400, Lennart Sorensen wrote:
> On Sat, Jun 07, 2008 at 08:31:47PM +, Tzafrir Cohen wrote:
> > My problem with make-kpkg has always been that I could never rely on its
> > generated -headers packages to actually work.
> 
> Odd, the headers it generated allways worked for me.

Taken to another system?

The problems I remember:

1. the "source" and "build" links pointed to an incorrect place. An
invalid build link is a problem.

2. If I actually changed the source to make the base supplied
linux-headers package not good enough, I found no way to generate a
complete one (linux-headers-2.6.18-6 vs linux-headers-2.6.18-6-686).

> 
> > So it was fine to build a kernel. But if I wanted to build some modules
> > for that kernel, I still have a problem.
> > 
> > My ugly workaround is to keep the source directory and hope for the
> > best.
> 
> Nothing wrong with doing that if you are compiling the kernel anyhow.

Doesn't work well if you want to allow building stuff on other
computers :-(

This is to say that I got spolit by how well 'm-a a-i' works.

-- 
Tzafrir Cohen | [EMAIL PROTECTED] | VIM is
http://tzafrir.org.il || a Mutt's
[EMAIL PROTECTED] ||  best
ICQ# 16849754 || friend


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Lennart Sorensen]

On Sat, Jun 07, 2008 at 09:35:28PM +, Tzafrir Cohen wrote:
> Taken to another system?

I don't remember if I did or not.

> The problems I remember:
> 
> 1. the "source" and "build" links pointed to an incorrect place. An
> invalid build link is a problem.

Where do they point?

> 2. If I actually changed the source to make the base supplied
> linux-headers package not good enough, I found no way to generate a
> complete one (linux-headers-2.6.18-6 vs linux-headers-2.6.18-6-686).

So running make-kpkg binary-arch, doesn't build a useful kernel and
header package set?

> Doesn't work well if you want to allow building stuff on other
> computers :-(
> 
> This is to say that I got spolit by how well 'm-a a-i' works.

Well I must admit I don't build custom kernels for my main computers.  I
only do so far a router I work with at work, and that one I do by
patching and changing the source package since I run it through a mini
build server.

You should not need the linux-headers-2.6.18-6 when using make-kpkg as
far as I can tell, although perhaps make-kpkg isn't always doing the
right thing when building from source.  Not sure about that.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Marc Haber]

On Sat, 7 Jun 2008 14:53:03 +0200, Holger Levsen
<[EMAIL PROTECTED]> wrote:
>On Saturday 07 June 2008 11:51, Marc Haber wrote:
>> Shouldn't that be easier to do,
>
>Send patches?! ;)

Since I pay more attention to my personal and mental health, I tend to
minimize my contact to the Debian Kernel "Team".

Greetings
Marc

-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Marc Haber]

On Sat, 7 Jun 2008 11:31:14 -0400, [EMAIL PROTECTED]
(Lennart Sorensen) wrote:
>On Sat, Jun 07, 2008 at 11:51:04AM +0200, Marc Haber wrote:
>> Shouldn't that be easier to do, and - most of all - documented?
>
>Playing with source packages isn't normal.

>The package is designed to make the life of the kernel
>image developers easy, not to make the life of people doing weird things
>for themselves easier.

I find that attitute totally unacceptable.

Greetings
Marc

-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Claim Award!!!!!!!!

[[EMAIL PROTECTED]]

__REMOVED__

===

Benvenuto in Maxi Mail di Virgilio e Tin.it!

[EMAIL PROTECTED] tramite il servizio Maxi Mail ha messo a tua disposizione i 
seguenti allegati :


* loo.txt (0 byte)

per prelevarli, fai click sul seguente link che ti porterà su una pagina dove 
troverai i comandi per visualizzare o scaricare gli allegati sul tuo PC:

http://communicator.maximail.alice.it/r.jsp?d=virgilio.it&wr=_unreg_4dfv14yl&ws=6aoq7ozi&e=virgilio.it&c=covfu6WcaAS4DrPP13ocGhom4Z2n62uZ953137

Ti ricordiamo che questi allegati saranno a tua disposizione fino al 06/06/2008 
alle ore 20:33 e che il mittente potrebbe ricevere le informazioni relative 
alla tua apertura della Maxi Mail e all'avvenuto download degli allegati.

Maxi Mail è il nuovo servizio gratuito, di Virgilio e Tin.it che ti permette di 
inviare a chi vuoi, allegati di grandi dimensioni, in modo semplice e veloce, 
senza occupare spazio utile nella tua casella di posta. Per saperne di più 
visita il sito www.tin.it


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: A dream of the Debian-logo

[Victor H De la Luz]

On Sat, Jun 7, 2008 at 2:16 PM, Deepak Tripathi <[EMAIL PROTECTED]> wrote:
> Hi,
> I do think so that its a really nice picture , but one of my suggestion is
> can't you create "e"  in Circle/Spiral way.
> that is my personal opinion ,your work is extremely good.
>
>
> On Sun, Jun 8, 2008 at 12:39 AM, Miriam Ruiz <[EMAIL PROTECTED]> wrote:
>>
>> It's a very nice picture, but I guess maybe it would belong more to
>> somewhere like DebianArt [1] than to this mailing list.
>>
>> Greetings,
>> Miry
>>
>> [1] http://www.debianart.org
>>
>>
>> --
>> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>> with a subject of "unsubscribe". Trouble? Contact
>> [EMAIL PROTECTED]
>>
>
>
>
> --
> Deepak Tripathi
> E3 71V3 8Y C063 (We Live By Code)
> http://deepkatripathi.blogspot.com
>


Is like a "greca" maya! good work.

-- 
Atte

ItZtLi

¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸
 Nahui Tonalli Icniuhtli.
¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Mass bug filing: FTBFS because of using imake without Build-Depends on xutils-dev

[Daniel Schepler]

From the changelog for xorg 1:7.3+11:

  * Remove the dependency of xutils against xutils-dev, it was only useful
for transitional purpose in Etch, closes: #418123.

This means that any package which used xmkmf/imake and had xutils, instead of 
xutils-dev, for the Build-Depends will now FTBFS.  It seems there were 
several packages which fall into this category (at this point, I've found 11 
packages starting with [0-9a-d]).  So unless there are any objections, I'll 
start filing bugs as I find them.
-- 
Daniel Schepler


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: How to build only linux-image-2.6.18-6-686

[Lennart Sorensen]

On Sun, Jun 08, 2008 at 12:41:01AM +0200, Marc Haber wrote:
> I find that attitute totally unacceptable.

Well it looks that way to me.  In fact I would say that is true of ever
source package.  The goal is to make the maintainers job easy, since
they are the ones that deal with the source package.  Most people only
ever deal with the binary packages and as long as the maintainer does a
good job, it works fine.

For building custom kernels I think the real issue is to find out what
is wrong with make-kpkg if it isn't doing what it is supposed to be
doing.

I am not a kernel team person (or a debian developer at all for that
matter, although I do now assist with the nvidia driver package), but to
me the current kernel package works great and I do deal with the source
package.  It is way better than what we used to have before Etch.  It is
one of the most complex packages to deal with since it has to work on
every architecture while at the same time dealing with completely
different configurations for each architecture as well as multiple
flavours per architecture.  I can't think of any other package that
comes close.

-- 
Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Mass bug filing: FTBFS because of using imake without Build-Depends on xutils-dev

[Steve Langasek]

On Sat, Jun 07, 2008 at 07:26:05PM -0700, Daniel Schepler wrote:
> From the changelog for xorg 1:7.3+11:

>   * Remove the dependency of xutils against xutils-dev, it was only useful
> for transitional purpose in Etch, closes: #418123.

> This means that any package which used xmkmf/imake and had xutils, instead of 
> xutils-dev, for the Build-Depends will now FTBFS.  It seems there were 
> several packages which fall into this category (at this point, I've found 11 
> packages starting with [0-9a-d]).  So unless there are any objections, I'll 
> start filing bugs as I find them.

Mass bugfiling seems appropriate and reasonable, but if you've already found
11 build failures in [0-9a-d], I think a severity: serious bug should be
filed against the new xorg in unstable to hold it out of lenny until the
full impact is known and the release team can make an informed decision
about whether this is acceptable for the release.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]