Re: Packaging problems Re: Packaging .deb vs .rpm

[Halim Boukaram]

Hi
 
About the C library for math.
 
I'm making the rpms. but the binary rpm isnt working. its turning out much smaller than the source and only keeps the AUTHOR, README, todo and help documents.
 
Ayone knows if thats normal or not.
 
Since i started trying to make the binary rpm i've made one major overhaul of the source.
 
Halim
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online

RFS: libpam-usb, PAM module allowing authentication via USB-Storage device

[GHERdO]

pam_usb is a PAM module that enables authentication using an USB-Storage
device (such as an USB Pen) through DSA private/public keys.

It can also work with other  devices, such as floppy disks or cdroms. It
can be setup to work with  any application using PAM such as your system
login  (login),   your  X  login   (XDM/KDM/GDM/...),  your  screensaver
(xscreensaver/...), and many others.  It supports multiple users for the
same device, multiple hostnames for the same user, serial numbers access
list and private key encryption.



Package I made:
 name:libpam-usb
 license: GPL
 url: http://debian.firenze.net/


Original software:
 url: http://sig11.org/~al/pam_usb/


-- 
GHERdO, happy GNU/linux user.

... Boys don't Cry!

problem with non PIC code

[Alexandre Pineau]

Helllo,

I maintain the debian  package of the library alogg, and the Bug#216839 
(libalogg.so.1.3.3 is a non-PIC library) was filled against it. I don't know 
how 
to solve this bug :

alogg includes non-PIC code because of the use of "allegro-config --libs" during
its building. If we look the outpoot of "allegro-config --libs", we can see the 
static 
library liballeg_unsharable. It is this librairie which includes non PIC code 
(see bug #
229988 against liballegro4a for more details).

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 executable (Ire) links with alleg_unsharable.
- If I have well understanded, I must build libalogg without alleg_unsharable.
I try to do it with the option --warn-unresolved-symbols but after I fail to 
build
IRE due to unresolved symbols (normal, after all). Any ideas?

Many thanks for your help and sorry for my poor english!

Alexandre Pineau
 
--
Il vente, c'est le vent de la mer qui nous tourmente. - Pierre Mac Orlan
http://alexandre.pineau.free.fr/

Re: problem with non PIC code

[Eduard Bloch]

#include 
* 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 executable (Ire) links with alleg_unsharable.

Okay.

> - If I have well understanded, I must build libalogg without alleg_unsharable.

No. alleg_unsharable contains non-PIC code (x86-optimised object files).

> I try to do it with the option --warn-unresolved-symbols but after I fail to 
> build
> IRE due to unresolved symbols (normal, after all). Any ideas?

You must link the application with that what `allegro-config --libs`
gives you but you must NOT use exactly this to link the library. You can
weed out following components from its output, then it should be okay:
-lalleg_unsharable -lXxf86dga -lXxf86vm -lXext -lX11

If your lib fails to link because of references to Xf86...  symbols,
than your upstream simply expects that static X libs are linked with the
lib. In this case you would have to add the libraries from xlibs-pic
package to the linker call.

Regards,
Eduard (former Allegro maintainer ;).

Re: Bootsplash Updates

[Kilian CAVALOTTI]

Matthew A. Nicholson wrote:
> Some time tommorrow (aka in the morning/afternoon) I should release
> updated (and IMO improved) versons of my bootsplash packages.

Hi !

As far as I tried, only tty1 is 'bootsplashed' with the framebuffer image.
I'd like to know how I can mod the /etc/init.d/rc script (I suppose it's the
one involved in bootsplashing process) to apply the background image to more
ttys.

TIA,

-- 
Kick | GPGKeyId: 0xD657340C
d'ailleurs ici c'est le seul forum ou vous voulez abolument qu'on
ecrive en bas moi je prefere d'ailleurs quand c'est en haut
-+- ELG in : "Le chat rue avant Elbeuf" -+-

Re: questions about packaging a kde app

[Paul Cupis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Saturday 14 February 2004 11:57, Tommaso Moroni 
<[EMAIL PROTECTED]> wrote:
> Also, is it normal that the program doesn't install the manual in
> KHelpCenter?

This is because your package install the KHelp files 
in /usr/share/doc/HTML (per KDE specs), which is against Debian package 
policy, as that directory is owned by dhelp. The KDE documentation 
should be installed in /usr/share/doc/kde/HTML.

To fix this, in your install: target you should change:

  $(MAKE) install DESTDIR=$(CURDIR)/debian/knights

for:

  $(MAKE) install DESTDIR=$(CURDIR)/debian/knights \
kde_htmldir=$(CURDIR)/debian/knights/usr/share/doc/kde/HTML

Regards,

Paul Cupis
- -- 
[EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iEYEARECAAYFAkAvyFwACgkQIzuKV+SHX/nE3QCdHTKiKjpiwsHYII7vX5MnBD2b
4OIAnjDICOHwPTSPyQDQ3b0RGnqNYP3o
=AYEw
-END PGP SIGNATURE-

maintaining new packages,upgrading to newer upstream versions

[Lucas Albers]

I just recently started using debian, 6 months ago.
I have run into a number of situations in which I needed to build a
package, or thought a package could be useful.
The packages I have been working on are:
sara security scanner,
nagios-modules, nagios doesn't have all the modules package for nagios.
snort-webmin (just doing QA for the webmin maintainer.)
dcc rhyolite, want to upgrade from 1.1.17 to 1.2.32.
dynfw, based on dynfw from gentoo dynamic ipblock/ipadd script.
(dynamically block unblock a single ip address in iptables via bash script.)
Useful for opening up a a port for one machine, or automatically blocking
a bad machine via portsentry.

I use all of these packages for my servers at work, so I work on them at
work


This must be a dumb question, but I am running into problems determining
how to upgrade an older version of a package to a newer version of the
package.
Example, i have the deb.dsc and similar files for sara, and it is based on
sara 3.x, I wish to upgrade it to version 5.0, which is the current
release.
What is the correct/easiest way to do this?
I am not creating a new package from scratch, I am just updating packages
based on newer versions.
I have looked at the debian docs, but they were still sort of confusing.
If their are references I missed, let me know.

I've got to the point where i can run dpkg-buildpackage and generate a deb
file from existing files I've created via
dpkg-source on the dsc file.
I got the buildroots, dependencies figured out.

I am just now sure what I need to do to upgrade it to a newer upstream
version.

Could someone perhaps provide help (and probable answer a number of simple
questions) concerning this?
Luke Computer Science, System Administrator.
Montana State University, Bozeman MT.

Re: questions about packaging a kde app

[Eike \"zyro\" Sauer]

Paul Cupis schrieb:
>   $(MAKE) install DESTDIR=$(CURDIR)/debian/knights \
> kde_htmldir=$(CURDIR)/debian/knights/usr/share/doc/kde/HTML

Thanks, this made my rules file much more transparent. 
But it worked "better" to use kde_htmldir=/usr/share/doc/kde/HTML.

Is there a similiar solution for icons? 
ATM I do:

dh_install src/hi16-app-kdiff3.png usr/share/icons/hicolor/16x16/apps/
dh_install src/hi32-app-kdiff3.png usr/share/icons/hicolor/32x32/apps/
dh_install src/lo16-app-kdiff3.png usr/share/icons/locolor/16x16/apps/
dh_install src/lo32-app-kdiff3.png usr/share/icons/locolor/32x32/apps/
mv debian/kdiff3/usr/share/icons/hicolor/16x16/apps/hi16-app-kdiff3.png \
debian/kdiff3/usr/share/icons/hicolor/16x16/apps/kdiff3.png
mv debian/kdiff3/usr/share/icons/hicolor/32x32/apps/hi32-app-kdiff3.png \
debian/kdiff3/usr/share/icons/hicolor/32x32/apps/kdiff3.png
mv debian/kdiff3/usr/share/icons/locolor/16x16/apps/lo16-app-kdiff3.png \
debian/kdiff3/usr/share/icons/locolor/16x16/apps/kdiff3.png
mv debian/kdiff3/usr/share/icons/locolor/32x32/apps/lo32-app-kdiff3.png \
debian/kdiff3/usr/share/icons/locolor/32x32/apps/kdiff3.png

Ciao,
Eike

Re: questions about packaging a kde app

[Paul Cupis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday 15 February 2004 20:17, "Eike \"zyro\" Sauer" 
<[EMAIL PROTECTED]> wrote:

> Is there a similiar solution for icons?

There is kde_icondir, but...

> ATM I do:
>
> dh_install src/hi16-app-kdiff3.png
> usr/share/icons/hicolor/16x16/apps/ dh_install
> src/hi32-app-kdiff3.png usr/share/icons/hicolor/32x32/apps/
> dh_install src/lo16-app-kdiff3.png
> usr/share/icons/locolor/16x16/apps/ dh_install
> src/lo32-app-kdiff3.png usr/share/icons/locolor/32x32/apps/ mv
> debian/kdiff3/usr/share/icons/hicolor/16x16/apps/hi16-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/hicolor/16x16/apps/kdiff3.png mv
> debian/kdiff3/usr/share/icons/hicolor/32x32/apps/hi32-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/hicolor/32x32/apps/kdiff3.png mv
> debian/kdiff3/usr/share/icons/locolor/16x16/apps/lo16-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/locolor/16x16/apps/kdiff3.png mv
> debian/kdiff3/usr/share/icons/locolor/32x32/apps/lo32-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/locolor/32x32/apps/kdiff3.png

Are you sure this is necessary? I've just had a look at kdiff3 0.9.81 
from Debian/unstable, and it seems to me that the normal install target 
will place these files in the right place for you, yet you also install 
them manually in the binary-arch target.

Have I missed something? Can you try removing the referenced code from 
debian/rules and seeing if the resulting package is "correct"?

Thanks,

Paul Cupis
- -- 
[EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iEYEARECAAYFAkAv2TgACgkQIzuKV+SHX/mWVgCdEurzvT4zzm3GWkLGRkCwDywE
LsQAn2GFnNzCa16bANGIo+OYg0cXnZ9M
=UkV6
-END PGP SIGNATURE-

Re: questions about packaging a kde app

[Eike \"zyro\" Sauer]

Paul Cupis schrieb:
> Have I missed something? Can you try removing the referenced code from
> debian/rules and seeing if the resulting package is "correct"?

I'm sure I had a compelling reason to do this some day 
- but I can't remember it. And the package seems to be fine
with all those lines removed. So I'll do just that.

Thanks,
Eike

RFS: mozilla-locale-hu

[GCS]

Dear Mentors,

 I have a locale (Hungarian) package for Mozilla 1.6:
* Package name: mozilla-locale-hu
  Version : 1.6
  Upstream Author : András Tímár <[EMAIL PROTECTED]>
* URL : http://mozilla.fsf.hu/langpack.html
* License : Mozilla Public License 1.1
  Description : Hungarian language pack for Mozilla

The package is lintian clean, but linda complains:
E: mozilla-locale-hu; File /usr/lib/mozilla/chrome/hu-unix.jar contained in 
/usr/lib of Architecture: all package.
I think it can be safely ignored. If I am wrong on this, please get my
attention and I will try to fix it somehow.
The Hungarian translation of Mozilla is an old project, I think it began
with Mozilla 0.9.x, proven to be an accurate translation with many happy
users. Unfortunately no one could make a package for Debian yet. :(

Thanks in advance,
GCS/Laszlo

Need Sponsor/Mentor for bbslashdot (Retrieve news from slashdot...)

[obake]

Hi, i want a sponsor/mentor for me (and my package :). If someone can 
(and want to) work together if me, i would be extremely thankful.


bbslashdot is a small package written originaly for blackbox (but must 
work in other WMs as well) that retrieves the most recent news from 
www.slashdot.org and shows in the screen. You can click on the news to 
open the site and see the full news in the site.


I've already packaged it (made the Manpage, fixed some simple bugs, 
wrote some docs...)


Thanks! :)

(erm, sorry if i mispelled something, my english isn't excelent)

Thanks again.. lol

Re: maintaining new packages,upgrading to newer upstream versions

[Frank Lichtenheld]

On Sun, Feb 15, 2004 at 12:47:28PM -0700, Lucas Albers wrote:
> This must be a dumb question, but I am running into problems determining
> how to upgrade an older version of a package to a newer version of the
> package.
> Example, i have the deb.dsc and similar files for sara, and it is based on
> sara 3.x, I wish to upgrade it to version 5.0, which is the current
> release.
> What is the correct/easiest way to do this?

You should take a look at uupdate. If you're not using some sort of
version control system (that may have their own methods or tools)
this is probably what you're looking for.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/

Re: Need Sponsor/Mentor for bbslashdot (Retrieve news from slashdot...)

[Frank Lichtenheld]

On Sun, Feb 15, 2004 at 10:05:05PM +0300, obake wrote:
> I've already packaged it (made the Manpage, fixed some simple bugs, 
> wrote some docs...)

Could you upload it somewhere (the _source_ package)
so we can take a look? This increases normally your chances for
comments and offers of sponsorship.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/

Why is debconf not preconfiguring?

[Joshua Kwan]

Hi all,

I'm interested in using debconf to warn a user that's upgrading from an
old version of ircd-hybrid and uses some now-unsupported directives in
the configuration file about the big change that was made. However I'd
like this to happen before the package is unpacked, but the config
script only seems to get run during the postinst.

How does apt determine whether to do a 'Preconfiguring packages...' or
not? I'm stumped. Another package of mine does get Preconfigured, but I
fail to see how it differs from ircd-hybrid.

Completely stumped,

-- 
Joshua Kwan


signature.asc
Description: Digital signature

Re: Packaging problems Re: Packaging .deb vs .rpm

[Halim Boukaram]

Hi
 
About the C library for math.
 
I'm making the rpms. but the binary rpm isnt working. its turning out much smaller than the source and only keeps the AUTHOR, README, todo and help documents.
 
Ayone knows if thats normal or not.
 
Since i started trying to make the binary rpm i've made one major overhaul of the source.
 
Halim
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online

RFS: libpam-usb, PAM module allowing authentication via USB-Storage device

[GHERdO]

pam_usb is a PAM module that enables authentication using an USB-Storage
device (such as an USB Pen) through DSA private/public keys.

It can also work with other  devices, such as floppy disks or cdroms. It
can be setup to work with  any application using PAM such as your system
login  (login),   your  X  login   (XDM/KDM/GDM/...),  your  screensaver
(xscreensaver/...), and many others.  It supports multiple users for the
same device, multiple hostnames for the same user, serial numbers access
list and private key encryption.



Package I made:
 name:libpam-usb
 license: GPL
 url: http://debian.firenze.net/


Original software:
 url: http://sig11.org/~al/pam_usb/


-- 
GHERdO, happy GNU/linux user.

... Boys don't Cry!


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

problem with non PIC code

[Alexandre Pineau]

Helllo,

I maintain the debian  package of the library alogg, and the Bug#216839 
(libalogg.so.1.3.3 is a non-PIC library) was filled against it. I don't know how 
to solve this bug :

alogg includes non-PIC code because of the use of "allegro-config --libs" during
its building. If we look the outpoot of "allegro-config --libs", we can see the static 
library liballeg_unsharable. It is this librairie which includes non PIC code (see bug 
#
229988 against liballegro4a for more details).

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 executable (Ire) links with alleg_unsharable.
- If I have well understanded, I must build libalogg without alleg_unsharable.
I try to do it with the option --warn-unresolved-symbols but after I fail to build
IRE due to unresolved symbols (normal, after all). Any ideas?

Many thanks for your help and sorry for my poor english!

Alexandre Pineau
 
--
Il vente, c'est le vent de la mer qui nous tourmente. - Pierre Mac Orlan
http://alexandre.pineau.free.fr/


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

Re: problem with non PIC code

[Eduard Bloch]

#include 
* 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 executable (Ire) links with alleg_unsharable.

Okay.

> - If I have well understanded, I must build libalogg without alleg_unsharable.

No. alleg_unsharable contains non-PIC code (x86-optimised object files).

> I try to do it with the option --warn-unresolved-symbols but after I fail to build
> IRE due to unresolved symbols (normal, after all). Any ideas?

You must link the application with that what `allegro-config --libs`
gives you but you must NOT use exactly this to link the library. You can
weed out following components from its output, then it should be okay:
-lalleg_unsharable -lXxf86dga -lXxf86vm -lXext -lX11

If your lib fails to link because of references to Xf86...  symbols,
than your upstream simply expects that static X libs are linked with the
lib. In this case you would have to add the libraries from xlibs-pic
package to the linker call.

Regards,
Eduard (former Allegro maintainer ;).


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

Re: Bootsplash Updates

[Kilian CAVALOTTI]

Matthew A. Nicholson wrote:
> Some time tommorrow (aka in the morning/afternoon) I should release
> updated (and IMO improved) versons of my bootsplash packages.

Hi !

As far as I tried, only tty1 is 'bootsplashed' with the framebuffer image.
I'd like to know how I can mod the /etc/init.d/rc script (I suppose it's the
one involved in bootsplashing process) to apply the background image to more
ttys.

TIA,

-- 
Kick | GPGKeyId: 0xD657340C
d'ailleurs ici c'est le seul forum ou vous voulez abolument qu'on
ecrive en bas moi je prefere d'ailleurs quand c'est en haut
-+- ELG in : "Le chat rue avant Elbeuf" -+-



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

Re: questions about packaging a kde app

[Paul Cupis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Saturday 14 February 2004 11:57, Tommaso Moroni 
<[EMAIL PROTECTED]> wrote:
> Also, is it normal that the program doesn't install the manual in
> KHelpCenter?

This is because your package install the KHelp files 
in /usr/share/doc/HTML (per KDE specs), which is against Debian package 
policy, as that directory is owned by dhelp. The KDE documentation 
should be installed in /usr/share/doc/kde/HTML.

To fix this, in your install: target you should change:

  $(MAKE) install DESTDIR=$(CURDIR)/debian/knights

for:

  $(MAKE) install DESTDIR=$(CURDIR)/debian/knights \
kde_htmldir=$(CURDIR)/debian/knights/usr/share/doc/kde/HTML

Regards,

Paul Cupis
- -- 
[EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iEYEARECAAYFAkAvyFwACgkQIzuKV+SHX/nE3QCdHTKiKjpiwsHYII7vX5MnBD2b
4OIAnjDICOHwPTSPyQDQ3b0RGnqNYP3o
=AYEw
-END PGP SIGNATURE-


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

maintaining new packages,upgrading to newer upstream versions

[Lucas Albers]

I just recently started using debian, 6 months ago.
I have run into a number of situations in which I needed to build a
package, or thought a package could be useful.
The packages I have been working on are:
sara security scanner,
nagios-modules, nagios doesn't have all the modules package for nagios.
snort-webmin (just doing QA for the webmin maintainer.)
dcc rhyolite, want to upgrade from 1.1.17 to 1.2.32.
dynfw, based on dynfw from gentoo dynamic ipblock/ipadd script.
(dynamically block unblock a single ip address in iptables via bash script.)
Useful for opening up a a port for one machine, or automatically blocking
a bad machine via portsentry.

I use all of these packages for my servers at work, so I work on them at
work


This must be a dumb question, but I am running into problems determining
how to upgrade an older version of a package to a newer version of the
package.
Example, i have the deb.dsc and similar files for sara, and it is based on
sara 3.x, I wish to upgrade it to version 5.0, which is the current
release.
What is the correct/easiest way to do this?
I am not creating a new package from scratch, I am just updating packages
based on newer versions.
I have looked at the debian docs, but they were still sort of confusing.
If their are references I missed, let me know.

I've got to the point where i can run dpkg-buildpackage and generate a deb
file from existing files I've created via
dpkg-source on the dsc file.
I got the buildroots, dependencies figured out.

I am just now sure what I need to do to upgrade it to a newer upstream
version.

Could someone perhaps provide help (and probable answer a number of simple
questions) concerning this?
Luke Computer Science, System Administrator.
Montana State University, Bozeman MT.


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

Re: questions about packaging a kde app

[Eike \"zyro\" Sauer]

Paul Cupis schrieb:
>   $(MAKE) install DESTDIR=$(CURDIR)/debian/knights \
> kde_htmldir=$(CURDIR)/debian/knights/usr/share/doc/kde/HTML

Thanks, this made my rules file much more transparent. 
But it worked "better" to use kde_htmldir=/usr/share/doc/kde/HTML.

Is there a similiar solution for icons? 
ATM I do:

dh_install src/hi16-app-kdiff3.png usr/share/icons/hicolor/16x16/apps/
dh_install src/hi32-app-kdiff3.png usr/share/icons/hicolor/32x32/apps/
dh_install src/lo16-app-kdiff3.png usr/share/icons/locolor/16x16/apps/
dh_install src/lo32-app-kdiff3.png usr/share/icons/locolor/32x32/apps/
mv debian/kdiff3/usr/share/icons/hicolor/16x16/apps/hi16-app-kdiff3.png \
debian/kdiff3/usr/share/icons/hicolor/16x16/apps/kdiff3.png
mv debian/kdiff3/usr/share/icons/hicolor/32x32/apps/hi32-app-kdiff3.png \
debian/kdiff3/usr/share/icons/hicolor/32x32/apps/kdiff3.png
mv debian/kdiff3/usr/share/icons/locolor/16x16/apps/lo16-app-kdiff3.png \
debian/kdiff3/usr/share/icons/locolor/16x16/apps/kdiff3.png
mv debian/kdiff3/usr/share/icons/locolor/32x32/apps/lo32-app-kdiff3.png \
debian/kdiff3/usr/share/icons/locolor/32x32/apps/kdiff3.png

Ciao,
Eike



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

Re: questions about packaging a kde app

[Paul Cupis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday 15 February 2004 20:17, "Eike \"zyro\" Sauer" 
<[EMAIL PROTECTED]> wrote:

> Is there a similiar solution for icons?

There is kde_icondir, but...

> ATM I do:
>
> dh_install src/hi16-app-kdiff3.png
> usr/share/icons/hicolor/16x16/apps/ dh_install
> src/hi32-app-kdiff3.png usr/share/icons/hicolor/32x32/apps/
> dh_install src/lo16-app-kdiff3.png
> usr/share/icons/locolor/16x16/apps/ dh_install
> src/lo32-app-kdiff3.png usr/share/icons/locolor/32x32/apps/ mv
> debian/kdiff3/usr/share/icons/hicolor/16x16/apps/hi16-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/hicolor/16x16/apps/kdiff3.png mv
> debian/kdiff3/usr/share/icons/hicolor/32x32/apps/hi32-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/hicolor/32x32/apps/kdiff3.png mv
> debian/kdiff3/usr/share/icons/locolor/16x16/apps/lo16-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/locolor/16x16/apps/kdiff3.png mv
> debian/kdiff3/usr/share/icons/locolor/32x32/apps/lo32-app-kdiff3.png
> \ debian/kdiff3/usr/share/icons/locolor/32x32/apps/kdiff3.png

Are you sure this is necessary? I've just had a look at kdiff3 0.9.81 
from Debian/unstable, and it seems to me that the normal install target 
will place these files in the right place for you, yet you also install 
them manually in the binary-arch target.

Have I missed something? Can you try removing the referenced code from 
debian/rules and seeing if the resulting package is "correct"?

Thanks,

Paul Cupis
- -- 
[EMAIL PROTECTED]

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iEYEARECAAYFAkAv2TgACgkQIzuKV+SHX/mWVgCdEurzvT4zzm3GWkLGRkCwDywE
LsQAn2GFnNzCa16bANGIo+OYg0cXnZ9M
=UkV6
-END PGP SIGNATURE-


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

Re: questions about packaging a kde app

[Eike \"zyro\" Sauer]

Paul Cupis schrieb:
> Have I missed something? Can you try removing the referenced code from
> debian/rules and seeing if the resulting package is "correct"?

I'm sure I had a compelling reason to do this some day 
- but I can't remember it. And the package seems to be fine
with all those lines removed. So I'll do just that.

Thanks,
Eike



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

RFS: mozilla-locale-hu

[GCS]

Dear Mentors,

 I have a locale (Hungarian) package for Mozilla 1.6:
* Package name: mozilla-locale-hu
  Version : 1.6
  Upstream Author : András Tímár <[EMAIL PROTECTED]>
* URL : http://mozilla.fsf.hu/langpack.html
* License : Mozilla Public License 1.1
  Description : Hungarian language pack for Mozilla

The package is lintian clean, but linda complains:
E: mozilla-locale-hu; File /usr/lib/mozilla/chrome/hu-unix.jar contained in /usr/lib 
of Architecture: all package.
I think it can be safely ignored. If I am wrong on this, please get my
attention and I will try to fix it somehow.
The Hungarian translation of Mozilla is an old project, I think it began
with Mozilla 0.9.x, proven to be an accurate translation with many happy
users. Unfortunately no one could make a package for Debian yet. :(

Thanks in advance,
GCS/Laszlo


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

Need Sponsor/Mentor for bbslashdot (Retrieve news from slashdot...)

[obake]

Hi, i want a sponsor/mentor for me (and my package :). If someone can 
(and want to) work together if me, i would be extremely thankful.

bbslashdot is a small package written originaly for blackbox (but must 
work in other WMs as well) that retrieves the most recent news from 
www.slashdot.org and shows in the screen. You can click on the news to 
open the site and see the full news in the site.

I've already packaged it (made the Manpage, fixed some simple bugs, 
wrote some docs...)

Thanks! :)

(erm, sorry if i mispelled something, my english isn't excelent)

Thanks again.. lol

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

Re: maintaining new packages,upgrading to newer upstream versions

[Frank Lichtenheld]

On Sun, Feb 15, 2004 at 12:47:28PM -0700, Lucas Albers wrote:
> This must be a dumb question, but I am running into problems determining
> how to upgrade an older version of a package to a newer version of the
> package.
> Example, i have the deb.dsc and similar files for sara, and it is based on
> sara 3.x, I wish to upgrade it to version 5.0, which is the current
> release.
> What is the correct/easiest way to do this?

You should take a look at uupdate. If you're not using some sort of
version control system (that may have their own methods or tools)
this is probably what you're looking for.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


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

Re: Need Sponsor/Mentor for bbslashdot (Retrieve news from slashdot...)

[Frank Lichtenheld]

On Sun, Feb 15, 2004 at 10:05:05PM +0300, obake wrote:
> I've already packaged it (made the Manpage, fixed some simple bugs, 
> wrote some docs...)

Could you upload it somewhere (the _source_ package)
so we can take a look? This increases normally your chances for
comments and offers of sponsorship.

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


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

Why is debconf not preconfiguring?

[Joshua Kwan]

Hi all,

I'm interested in using debconf to warn a user that's upgrading from an
old version of ircd-hybrid and uses some now-unsupported directives in
the configuration file about the big change that was made. However I'd
like this to happen before the package is unpacked, but the config
script only seems to get run during the postinst.

How does apt determine whether to do a 'Preconfiguring packages...' or
not? I'm stumped. Another package of mine does get Preconfigured, but I
fail to see how it differs from ircd-hybrid.

Completely stumped,

-- 
Joshua Kwan


signature.asc
Description: Digital signature