Hallo World, Hello David, Hell Andreas,
* David Kalnischkies [Wed, May 15 2013, 10:13:22AM]:
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: bl...@debian.org
Dear mentors (and hi Eduard Bloch),
I am looking for a sponsor for the package module-assistant to get the
needed
#include hallo.h
* Paul Wise [Tue, Oct 18 2005, 02:44:23PM]:
Well, in debian there is a tradition of for each config file, there is
an equivalent .d directory that can be used by packages other than the
one that installs the config file. For example /etc/logrotate.conf
and /etc/logrotate.d.
#include hallo.h
* Jean-Marc Ranger [Sat, Oct 22 2005, 05:57:57PM]:
Many thanks to Paul and Eduard for your comments and hints.
A new edition of adm8211-source_0.0.20050620-1 is available at
http://web.ncf.ca/jmranger/adm8211/
It should fix all items previously mentioned, and more.
Looks
#include hallo.h
* Nico Golde [Sat, Jul 09 2005, 02:14:22AM]:
sudo apt-history show upgrade
2005-07-09 00:12:03: upgrade gstreamer0.8-alsa=0.8.8-3
0.8.10-1
2005-07-09 00:12:03: upgrade libbonobo2-common=2.8.1-2
2.10.0-1
2005-07-09 00:12:03: upgrade
#include hallo.h
* Nico Golde [Sat, Jul 09 2005, 12:06:54PM]:
But for example:
apt-history show install
2005-07-09 00:12:03: install libstdc++6-4.0-dev
4.0.0-12
2005-07-09 00:12:03: install libaa1
1.4p5-28
2005-07-09 00:12:03:
#include hallo.h
* Nico Golde [Sat, Jul 09 2005, 01:04:23PM]:
I think there is apt-history a better way.
For doing what exactly?
For doing this without corebutils.
a) grep it is not in coreutils but in the grep package
b) you seem to have an allergy to essential packages (you know,
#include hallo.h
* David Moreno Garza [Tue, Oct 19 2004, 09:33:52AM]:
Do you want your dependency to be satisfyable by either xmms (which
shlibs suggests), or beep-media-player (which shlibs does not
suggest). If so, you are either going to have to provide your own
shlibs.local file and
#include hallo.h
* David Moreno Garza [Tue, Oct 19 2004, 09:33:52AM]:
Do you want your dependency to be satisfyable by either xmms (which
shlibs suggests), or beep-media-player (which shlibs does not
suggest). If so, you are either going to have to provide your own
shlibs.local file and
#include hallo.h
* martin f krafft [Sun, Oct 17 2004, 10:35:21PM]:
Apart, yes, why not delete dh_* calls?
Because you need to remember them again when you need them or look
around. Okay, it makes no difference when the day ends.
Regards,
Eduard.
--
stockholm Overfiend: why dont you flame him?
#include hallo.h
* martin f krafft [Sun, Oct 17 2004, 10:35:21PM]:
Apart, yes, why not delete dh_* calls?
Because you need to remember them again when you need them or look
around. Okay, it makes no difference when the day ends.
Regards,
Eduard.
--
stockholm Overfiend: why dont you flame him?
#include hallo.h
* martin f krafft [Sun, Oct 17 2004, 11:45:34AM]:
And about dh-make... stop using it anyway. Either switch to using
cdbs, or get a hang of packaging so that you don't have to call this
I disagree. cdbs sucks when it comes to some advanced extensions that
its creators did not
#include hallo.h
* martin f krafft [Sun, Oct 17 2004, 11:45:34AM]:
And about dh-make... stop using it anyway. Either switch to using
cdbs, or get a hang of packaging so that you don't have to call this
I disagree. cdbs sucks when it comes to some advanced extensions that
its creators did not
#include hallo.h
* Gertjan van Zwieten [Tue, Aug 17 2004, 10:40:50PM]:
The existing solutions like apt-cacher and apt-proxy didn't really offer
what I was looking for. I have tried to explain this on the website:
http://gertjan.freezope.org/replicator.
I do not trust your analysis of
#include hallo.h
* Gertjan van Zwieten [Thu, Aug 19 2004, 12:01:12PM]:
I admit I was not aware of this perl one-liner you're referring to. I
Such as... for x in *.deb; do perl -e 'read(STDIN,$a,2000);
$a=~s,^(.*?)\r?\n\r?\n,,ms; print $a, STDIN' $x pure/$x; done
didn't find any of this on
#include hallo.h
* Gertjan van Zwieten [Tue, Aug 17 2004, 10:40:50PM]:
The existing solutions like apt-cacher and apt-proxy didn't really offer
what I was looking for. I have tried to explain this on the website:
http://gertjan.freezope.org/replicator.
I do not trust your analysis of
#include hallo.h
* Gertjan van Zwieten [Thu, Aug 19 2004, 12:01:12PM]:
I admit I was not aware of this perl one-liner you're referring to. I
Such as... for x in *.deb; do perl -e 'read(STDIN,$a,2000);
$a=~s,^(.*?)\r?\n\r?\n,,ms; print $a, STDIN' $x pure/$x; done
didn't find any of this on
#include hallo.h
* Pierre HABOUZIT [Tue, Jul 27 2004, 11:19:22PM]:
please read [1], especialy section called : Advanced customisation
https://wiki.duckcorp.org/DebianPackagingTutorial_2fCDBS
I think, CDBS restricts too much, simply dangerous hocus pocus. For
example, I still don't see how
#include hallo.h
* Pierre HABOUZIT [Tue, Jul 27 2004, 11:19:22PM]:
please read [1], especialy section called : Advanced customisation
https://wiki.duckcorp.org/DebianPackagingTutorial_2fCDBS
I think, CDBS restricts too much, simply dangerous hocus pocus. For
example, I still don't see how
#include hallo.h
* Florian Ernst [Wed, Jul 14 2004, 01:09:44PM]:
My packaging (lintian / linda clean, built in an up-to-date pbuilder
chroot) can be found at http://ernst.uni-hd.de/debian/tree, upstream
is at http://mama.indstate.edu/users/ice/tree/.
Any comments are welcome!
At the first
#include hallo.h
* Florian Ernst [Wed, Jul 14 2004, 05:50:57PM]:
| * Patmatch() code courtesy of Thomas Moore ([EMAIL PROTECTED])
so I don't know whether you've really checked my packaging or some
other stuff. Besides, as it can be seen, this patch had been applied
upstream already some time
#include hallo.h
* Florian Ernst [Wed, Jul 14 2004, 01:09:44PM]:
My packaging (lintian / linda clean, built in an up-to-date pbuilder
chroot) can be found at http://ernst.uni-hd.de/debian/tree, upstream
is at http://mama.indstate.edu/users/ice/tree/.
Any comments are welcome!
At the first
#include hallo.h
* Florian Ernst [Wed, Jul 14 2004, 05:50:57PM]:
| * Patmatch() code courtesy of Thomas Moore ([EMAIL PROTECTED])
so I don't know whether you've really checked my packaging or some
other stuff. Besides, as it can be seen, this patch had been applied
upstream already some time
Example output available at http://fjortis.info/bandwidthd/.
...
Any suggestions, comments, flames welcome!
Nice one. I would like to see this included.
Ack. I would like to sponsor it but it does not work for me!
I see only this messages repeating every minute:
Previouse graphing run
Example output available at http://fjortis.info/bandwidthd/.
...
Any suggestions, comments, flames welcome!
Nice one. I would like to see this included.
Ack. I would like to sponsor it but it does not work for me!
I see only this messages repeating every minute:
Previouse graphing run
Moin Mark!
Mark Wilson schrieb am Donnerstag, den 17. Juni 2004:
YAFFA, is a filemanager and a FTP client with support for secure FTP.
It includes a GTK front end and console mode, this version also has http
support.
Includes an editable scriptlist, configurable button grid (gui).
The
Moin Mark!
Mark Wilson schrieb am Donnerstag, den 17. Juni 2004:
YAFFA, is a filemanager and a FTP client with support for secure FTP.
It includes a GTK front end and console mode, this version also has http
support.
Includes an editable scriptlist, configurable button grid (gui).
The
#include hallo.h
* Magosányi Árpád [Fri, Jun 11 2004, 11:36:14PM]:
So in the latter case, write your name in debian/control in UTF-8 too.
It is already done. Now I have to tell gnupg my name in UTF-8. But how?
(not tested)
Add a new key ID for the proper (UTF-8) name.
Regards,
Eduard.
--
#include hallo.h
* Magosányi Árpád [Fri, Jun 11 2004, 11:36:14PM]:
So in the latter case, write your name in debian/control in UTF-8 too.
It is already done. Now I have to tell gnupg my name in UTF-8. But how?
(not tested)
Add a new key ID for the proper (UTF-8) name.
Regards,
Eduard.
--
#include hallo.h
* David A. Riggs [Sat, Jun 05 2004, 05:06:17PM]:
1. gksu
2. kdesu
3. an xterm prompting with su
I propose that 'su-to-root' look at a configuration file for a preferred
method, first in /etc and then in ~/ so users may specify their
preference. If people think this is a
#include hallo.h
* David A. Riggs [Sat, Jun 05 2004, 05:06:17PM]:
1. gksu
2. kdesu
3. an xterm prompting with su
I propose that 'su-to-root' look at a configuration file for a preferred
method, first in /etc and then in ~/ so users may specify their
preference. If people think this is a
Moin Goswin!
Goswin von Brederlow schrieb am Samstag, den 05. Juni 2004:
So, my question is...is there, or should there be, some virtual
package or system-wide or user-wide preference for gaining root
priviliges under X11? What's the best current way to get this
into the menu
Moin Goswin!
Goswin von Brederlow schrieb am Samstag, den 05. Juni 2004:
So, my question is...is there, or should there be, some virtual
package or system-wide or user-wide preference for gaining root
priviliges under X11? What's the best current way to get this
into the menu
#include hallo.h
* Jeff Breker [Sat, Apr 10 2004, 03:08:35PM]:
Hello debian mentors,
I am looking for a sponsor for bloat, a perl script that extracts an
archive with the necessary utility.
* Package name: bloat
Version : 1.3.0.1
Upstream Author : Dave Wickham [EMAIL
#include hallo.h
* Jeff Breker [Sat, Apr 10 2004, 03:08:35PM]:
Hello debian mentors,
I am looking for a sponsor for bloat, a perl script that extracts an
archive with the necessary utility.
* Package name: bloat
Version : 1.3.0.1
Upstream Author : Dave Wickham [EMAIL
#include hallo.h
* Alexandre Pineau [Sun, Feb 15 2004, 12:40:28PM]:
The allegro's maintainer suggests to me that I need to ensure the
executable wich need alogg links with alleg_unsharable and exports
its symbols to the library alogg with -rdynamic. But I don't know how
to do this.
- The
#include hallo.h
* Alexandre Pineau [Sun, Feb 15 2004, 12:40:28PM]:
The allegro's maintainer suggests to me that I need to ensure the
executable wich need alogg links with alleg_unsharable and exports
its symbols to the library alogg with -rdynamic. But I don't know how
to do this.
- The
#include hallo.h
* Zenaan Harkness [Sat, Feb 07 2004, 04:20:47AM]:
sys-admins on Linux systems, and they feel much better when software is in
.rpm, because that's what they know.
Don't RPM distros now have apt/ alien to install? (ie. so they can
install .deb archives) ???
APT does not
#include hallo.h
* Steve Kemp [Tue, Dec 09 2003, 06:21:02PM]:
2. Providing it in source form and expecting the user to build it,
like the nvidia module.
3. Building on my machine to produce a binary x86 module, and
Either with dh_make templates or (my favorite ;) with m-a,
#include hallo.h
* Max Vozeler [Fri, Nov 28 2003, 04:52:47AM]:
On Fri, Nov 28, 2003 at 01:22:36AM +0100, Max Vozeler wrote:
What's not ready:
- README.Debian hasnt been updated to reflect the switch to module-assistant
- loop-aes-ciphers-source hasnt been converted to module-assistant
#include hallo.h
* Max Vozeler [Fri, Nov 28 2003, 04:52:47AM]:
On Fri, Nov 28, 2003 at 01:22:36AM +0100, Max Vozeler wrote:
What's not ready:
- README.Debian hasnt been updated to reflect the switch to
module-assistant
- loop-aes-ciphers-source hasnt been converted to
#include hallo.h
* Max Vozeler [Wed, Nov 26 2003, 12:31:16AM]:
mv /usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23 \
/usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23-rc3
mv: cannot stat `/usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23': No such
file or directory
#include hallo.h
* Max Vozeler [Wed, Nov 26 2003, 12:31:16AM]:
mv /usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23 \
/usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23-rc3
mv: cannot stat `/usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23':
No such file or directory
#include hallo.h
* Max Vozeler [Fri, Nov 21 2003, 05:54:39AM]:
* URL : http://loop-aes.sourceforge.net
* License : GPL
Description : AES-encryption loopback Linux kernel module
Bugs:
- source depends on utils, why? No other -source package works that way.
-
#include hallo.h
* Eduard Bloch [Tue, Nov 25 2003, 07:37:53AM]:
- source depends on utils, why? No other -source package works that way.
- document properly that your package does NOT build with kernel-headers
- binary-modules is hosed:
PS:
... and you use old dh_make templates which
#include hallo.h
* Eduard Bloch [Tue, Nov 25 2003, 07:37:53AM]:
- source depends on utils, why? No other -source package works that way.
- document properly that your package does NOT build with kernel-headers
- binary-modules is hosed:
PS:
... and you use old dh_make templates which
#include hallo.h
* Max Vozeler [Fri, Nov 21 2003, 05:54:39AM]:
* URL : http://loop-aes.sourceforge.net
* License : GPL
Description : AES-encryption loopback Linux kernel module
Bugs:
- source depends on utils, why? No other -source package works that way.
-
#include hallo.h
* Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
What _stupidness_ are you refering to? I've always just used something
like:
svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
Always? Nice to see that it can work with three arguments and apply the
#include hallo.h
* Fabian Fagerholm [Fri, Aug 29 2003, 12:44:02PM]:
On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
How do I manage a new Debian package with Subversion?
Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
insight into this issue. I will try to summarize
#include hallo.h
* Joey Hess [Fri, Aug 29 2003, 12:35:46PM]:
Actually, dpkg-buildpackage does not care what you name the build
directory of a package.
Persaonally, I use just packagename for the directory names and build
directly from them, using a collection of ugly hacks to ignore the
#include hallo.h
* Fabian Fagerholm [Fri, Aug 29 2003, 12:44:02PM]:
On Thu, 2003-08-28 at 22:24, Fabian Fagerholm wrote:
How do I manage a new Debian package with Subversion?
Thanks to [EMAIL PROTECTED] and [EMAIL PROTECTED] for their
insight into this issue. I will try to summarize
#include hallo.h
* Joey Hess [Fri, Aug 29 2003, 12:35:46PM]:
Actually, dpkg-buildpackage does not care what you name the build
directory of a package.
Persaonally, I use just packagename for the directory names and build
directly from them, using a collection of ugly hacks to ignore the
#include hallo.h
* Jamin W. Collins [Fri, Aug 29 2003, 03:13:44PM]:
What _stupidness_ are you refering to? I've always just used something
like:
svn merge http://pkg/upstream/a.b http://pkg/upstream/current trunk
Always? Nice to see that it can work with three arguments and apply the
#include hallo.h
* Celso González [Fri, Aug 01 2003, 01:14:33PM]:
So when the uploader checks the name of the Maintainer in the control
file (not utf-8) with the name in the changelog says that are different,
^
Why not? If you are not making a Description translation for
#include hallo.h
* Matej Cepl [Mon, Jul 28 2003, 03:11:29PM]:
Hi,
I have created a package for vimoutliner. Is there anybody who would
like to sponsor me?
Package: vimoutliner
Status: install ok installed
Priority: optional
Section: editors
Installed-Size: 204
#include hallo.h
* Matej Cepl [Mon, Jul 28 2003, 03:11:29PM]:
Hi,
I have created a package for vimoutliner. Is there anybody who would
like to sponsor me?
Package: vimoutliner
Status: install ok installed
Priority: optional
Section: editors
Installed-Size: 204
Moin Matthias!
Matthias Urlichs schrieb am Wednesday, den 16. July 2003:
The package is lintian and linda clean.
Download: http://smurf.noris.de/code/debian/unstable/source/videogen*
APT: deb-src http://smurf.noris.de/code/debian/ unstable smurf
videogen (0.32-1) unstable; urgency=low
Moin Matthias!
Matthias Urlichs schrieb am Wednesday, den 16. July 2003:
*Sigh* Upstream has deleted it in version 0.30.
But you're right, it makes sense to have that.
[ Time passes ]
OK -- I have resurrected some_modes.sh and updated the package.
If somebody can check that the tool in
Moin Matthias!
Matthias Urlichs schrieb am Wednesday, den 16. July 2003:
The package is lintian and linda clean.
Download: http://smurf.noris.de/code/debian/unstable/source/videogen*
APT: deb-src http://smurf.noris.de/code/debian/ unstable smurf
videogen (0.32-1) unstable; urgency=low
Moin Matthias!
Matthias Urlichs schrieb am Wednesday, den 16. July 2003:
*Sigh* Upstream has deleted it in version 0.30.
But you're right, it makes sense to have that.
[ Time passes ]
OK -- I have resurrected some_modes.sh and updated the package.
If somebody can check that the tool in
Moin Michael!
Michael Koch schrieb am Thursday, den 05. June 2003:
I have a problem to run fakeroot debian/rules clean in one package
source tree while not in another. Any idea what could be the reason
for this behaviour ?
Something overwritting LD_LIBRARY_PATH? It should extend the
Moin Michael!
Michael Koch schrieb am Thursday, den 05. June 2003:
I have a problem to run fakeroot debian/rules clean in one package
source tree while not in another. Any idea what could be the reason
for this behaviour ?
Something overwritting LD_LIBRARY_PATH? It should extend the
#include hallo.h
* Junichi Uekawa [Thu, Nov 07 2002, 05:26:09AM]:
But the plan is to move all architectures to gcc-3.2 for sarge.
I don't know why this hasn't happened already.
That at least requires working gcc-3.2 and hence probably working
glibc 2.3 for all arches, which has not
#include hallo.h
* Junichi Uekawa [Thu, Nov 07 2002, 05:26:09AM]:
But the plan is to move all architectures to gcc-3.2 for sarge.
I don't know why this hasn't happened already.
That at least requires working gcc-3.2 and hence probably working
glibc 2.3 for all arches, which has not
#include hallo.h
Craig Small wrote on Fri Jul 19, 2002 um 06:48:22PM:
On Fri, Jul 19, 2002 at 12:07:00AM -0500, Joe Wreschnig wrote:
Is there a good tutorial/reference anywhere for how to package (Linux)
kernel modules and source, in a way that works with make-kpkg's
modules_image?
The
#include hallo.h
Ian Duggan wrote on Wed Mar 13, 2002 um 04:07:46PM:
When packaging kernel patches, should the patches be against the debian
kernel sources or the stock kernels? I have several patches I'm
Idealy against the Debian kernel sources.
packaging for the stock kernels. It would be
#include hallo.h
Ian Duggan wrote on Wed Mar 13, 2002 um 04:07:46PM:
When packaging kernel patches, should the patches be against the debian
kernel sources or the stock kernels? I have several patches I'm
Idealy against the Debian kernel sources.
packaging for the stock kernels. It would be
#include hallo.h
Mike Markley wrote on Tue Feb 26, 2002 um 06:00:12PM:
Build-Depends: debhelper ( 3.4.9)
because it sounds like *only* 3.4.9 has this problem, and therefore builds
would work with 3.4.8, etc.
If you know this for sure, use debhelper ( 3.4.9) | debhelper ( 3.4.9).
Why
#include hallo.h
Florian Hinzmann wrote on Sun Nov 04, 2001 um 08:18:47PM:
I can't do a configure run as there is no configure script!
I do have to run the autotools scripts.
The question is when to run it. Before or after the Debian
diff is built.
Well, if you _need_ the makefile to clean
#include hallo.h
Florian Hinzmann wrote on Sat Nov 03, 2001 um 01:27:23PM:
Hello!
Would you consider reading
/usr/share/doc/autotools-dev/README.Debian.gz and then
reading my mail again?
I did. And I do not havy anything to change in my last statement.
Yes, I do run an (modified)
#include hallo.h
Florian Hinzmann wrote on Fri Nov 02, 2001 um 11:58:03AM:
All these are symlinks from file to /usr/share/autoconf/file.
Anyone had this? Anyone knows what to do about it?
Is there an autogen.sh script which you have executed? Or something like
libtoolize -f? It seems like the
#include hallo.h
Florian Hinzmann wrote on Sat Nov 03, 2001 um 01:27:23PM:
Hello!
Would you consider reading
/usr/share/doc/autotools-dev/README.Debian.gz and then
reading my mail again?
I did. And I do not havy anything to change in my last statement.
Yes, I do run an (modified)
#include hallo.h
Florian Hinzmann wrote on Fri Nov 02, 2001 um 11:58:03AM:
All these are symlinks from file to /usr/share/autoconf/file.
Anyone had this? Anyone knows what to do about it?
Is there an autogen.sh script which you have executed? Or something like
libtoolize -f? It seems like the
#include hallo.h
Gergely Nagy wrote on Mon Oct 29, 2001 um 06:33:39PM:
At Sun, 28 Oct 2001 21:24:29 -0500,
Duncan Findlay [EMAIL PROTECTED] wrote:
Are there any resources anywhere to help me create a package for kernel
modules that will work with make-kpkg?
You might want to take a
#include hallo.h
Hamish Moffatt wrote on Fri Oct 12, 2001 um 10:34:06PM:
On Fri, Oct 12, 2001 at 01:10:47PM +0200, Falk Hueffner wrote:
Packages must not overwrite other packages' files. You can perhaps use
the alternatives mechanism. See update-alternatives(8).
Diversions (dpkg-divert)
#include hallo.h
Hamish Moffatt wrote on Fri Oct 12, 2001 um 10:34:06PM:
On Fri, Oct 12, 2001 at 01:10:47PM +0200, Falk Hueffner wrote:
Packages must not overwrite other packages' files. You can perhaps use
the alternatives mechanism. See update-alternatives(8).
Diversions (dpkg-divert)
#include hallo.h
Hereward Cooper wrote on Sun Oct 07, 2001 um 10:21:05PM:
I would like a sponsor for the XMMS Visulization -- Jess. I think it
looks really wickedly slick and even if you don't want to sponsor me, I
think you should have this anyway (if you run XMMS)!
Primaraly I wouldn't
#include hallo.h
Hereward Cooper wrote on Sun Oct 07, 2001 um 10:21:05PM:
I would like a sponsor for the XMMS Visulization -- Jess. I think it
looks really wickedly slick and even if you don't want to sponsor me, I
think you should have this anyway (if you run XMMS)!
Primaraly I wouldn't mind
#include hallo.h
Erich Schubert wrote on Fri Oct 05, 2001 um 12:24:07PM:
Just a question of procedure:
What if i wanted to rename a source package? How would i do this?
Not that i want to rename my package right now
Just change in control and in the latest changelog entry. And make a
note
#include hallo.h
Erich Schubert wrote on Fri Oct 05, 2001 um 12:24:07PM:
Just a question of procedure:
What if i wanted to rename a source package? How would i do this?
Not that i want to rename my package right now
Just change in control and in the latest changelog entry. And make a
note
#include hallo.h
Hereward Cooper wrote on Thu Oct 04, 2001 um 04:23:47PM:
I don't think I understand you. How/why would you want to change the
*upstream* name. It should be enough to change the name used by
Debian.
Sorry didn't word it too great as i was in a rush.
What i just basically
#include hallo.h
Hereward Cooper wrote on Thu Oct 04, 2001 um 04:23:47PM:
I don't think I understand you. How/why would you want to change the
*upstream* name. It should be enough to change the name used by
Debian.
Sorry didn't word it too great as i was in a rush.
What i just basically
#include hallo.h
Christian T. Steigies wrote on Sat Aug 25, 2001 um 01:12:53PM:
debconf (developer): frontend started
debconf (developer): frontend running, package name is moon-buggy
debconf (developer): starting /var/lib/dpkg/info/moon-buggy.config configure 0.5.52-6
debconf (developer):
#include hallo.h
Christian T. Steigies wrote on Sat Aug 25, 2001 um 01:12:53PM:
debconf (developer): frontend started
debconf (developer): frontend running, package name is moon-buggy
debconf (developer): starting /var/lib/dpkg/info/moon-buggy.config configure
0.5.52-6
debconf (developer):
#include hallo.h
Viral wrote on Tue Aug 21, 2001 um 02:29:25PM:
I need to build an i386 version of a package, and also an i686 optimised
version for the same package. Is it possible to build both packages from
one source, instead of doing it twice in two different directories ?
Please don't
#include hallo.h
Philipp Frauenfelder wrote on Tue Aug 21, 2001 um 01:38:35PM:
I guess he wants to build a
foo
package and a
foo-i686
package as it was done with libc6 some time ago.
I guess too, but the foo-i686 would cause Grave-Bugs soon. But there is
another issue: I considered to
#include hallo.h
Viral wrote on Tue Aug 21, 2001 um 02:29:25PM:
I need to build an i386 version of a package, and also an i686 optimised
version for the same package. Is it possible to build both packages from
one source, instead of doing it twice in two different directories ?
Please don't
#include hallo.h
Philipp Frauenfelder wrote on Tue Aug 21, 2001 um 01:38:35PM:
I guess he wants to build a
foo
package and a
foo-i686
package as it was done with libc6 some time ago.
I guess too, but the foo-i686 would cause Grave-Bugs soon. But there is
another issue: I considered to
Hello,
I did never imagine myself asking for help on packaging, but I failed on
this task :(
I am working on kernel-image-2.2.19-udma100-ext3 and have some problems
making the package build the right way. How to do this? The docs
of kernel-package don't give enough info about the creation
Hello,
I did never imagine myself asking for help on packaging, but I failed on
this task :(
I am working on kernel-image-2.2.19-udma100-ext3 and have some problems
making the package build the right way. How to do this? The docs
of kernel-package don't give enough info about the creation
{us,eeting}s,
Eduard.
--
========
Eduard Bloch [EMAIL PROTECTED]; HP: http://eduard.bloch.com/edecosi
0xEDF008C5(GnuPG): E6EB 98E2 B885 8FF0 6C04 5C1D E106 481E EDF0 08C5
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
.
--
Eduard Bloch [EMAIL PROTECTED]; HP: http://eduard.bloch.com/edecosi
0xEDF008C5(GnuPG): E6EB 98E2 B885 8FF0 6C04 5C1D E106 481E EDF0 08C5
n't forget, this is not the best solution. You should develop your
packages in the same environment as the package should later run in.
MfG,
Eduard.
--
=====
Eduard Bloch [EMAIL PROTECTED]; HP: http://eduard.bloch.com/edecosi
0xEDF0
, this is not the best solution. You should develop your
packages in the same environment as the package should later run in.
MfG,
Eduard.
--
=
Eduard Bloch [EMAIL PROTECTED]; HP: http://eduard.bloch.com/edecosi
0xEDF008C5(GnuPG): E6EB
93 matches
Mail list logo
