Re: Please help: Amendments for packages-arch-specific
On Sat, 2006-06-17 at 20:35 +1000, Andree Leidenfrost wrote: > Dear mentors, > > I've had no luck so far with getting architectures added for my packages > in > http://cvs.debian.org/srcdep/Packages-arch-specific?cvsroot=dak&rev=HEAD > as kindly suggested by Justin Pryzby here: > http://lists.debian.org/debian-mentors/2006/04/msg00340.html > > I have asked the maintainers of the Packages-arch-specific file twice as > per the messages below with no result and no response thus far. With GRASS I never got a response from those folks. I filed a bug detailing my request against the ftp.debian.org pseudo-package and eventually that led to it getting done. Steve > > I am a bit at a loss here as to what to do next. Am I not asking for the > right thing? Could I make the changes myself somehow or is the file > off-limits? > > Any help would be greatly appreciated. (Quite a bit of work has gone > into the amd64 version of the packages and it would really be good to > have them available in the repository so that a broader audience can > test them and I can fix bugs before etch freezes.) > > Thanks a lot & best regards, > Andree > > Forwarded Message > From: Andree Leidenfrost <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: [Fwd: Amendments for packages-arch-specific] > Date: Tue, 23 May 2006 22:30:46 +1000 > Hi Lamont, > > I sent the message below a while ago. I noticed that you changed the > Packages-arch-specific file on 8 May, so I thought I nudge you about it > this time. > > It would be really cool if you could do these changes. (If there is > anything else I need to do to get this changed please let me know.) > > Cheers, > Andree > > Forwarded Message > From: Andree Leidenfrost <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: Amendments for packages-arch-specific > Date: Thu, 27 Apr 2006 19:02:07 +1000 > Dear James, > > It would be great if you could amend the architecture specific > information of my packages as follows: > > mindi: i386 ia64 amd64 > mindi-busybox: i386 ia64 amd64 > mondo: i386 amd64 > > Thank you very much and best regards, > Andree > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Need help getting package built on arm
Hi, My package, qgis, has failed to build on arm. The error is: uic: error while loading shared libraries: libICE.so.6: cannot open shared object file: No such file or directory When this first happened, I checked on packages.d.o and IIRC could not find a package on arm that contained that file. Now I can. So I suspect that it will work now. Should I just bump up my xlibs-dev build dep to the latest version and upload the package to be built again? Thanks for your help, Steve
Re: library files are not included in the .deb files
On Sat, 2005-07-09 at 16:00 -0400, kamaraju kusumanchi wrote:
> Mattia Dongili wrote:
>
> >On Sat, Jul 09, 2005 at 02:13:58PM -0400, kamaraju kusumanchi wrote:
> >
> >
> >>I am trying to package a library whose upstream is located at
> >>http://sourceforge.net/projects/fortranposix
> >>
> >>
> >>I already read the libpkg-guide, maint-guide. This problem was not
> >>discussed in any of them. I googled and also asked in the irc about this
> >>problem.
> >>
> >>There were no errors/warnings when I checked the final packages with
> >>linda -i and lintian -i. But when I did dpkg -c, there are no libraries
> >>in the packages.
> >>
> >>
> >
> >maybe it's just something wrong within your
> >debian/.{install,dirs,whatever} files (if you're using
> >debhelper scripts
> >
> >[...]
> >
> >
> >>$dpkg -c libfortranposix0-dev_0.1-1_i386.deb
> >>drwxr-xr-x root/root 0 2005-07-09 13:46:00 ./
> >>drwxr-xr-x root/root 0 2005-07-09 13:46:00 ./usr/
> >>drwxr-xr-x root/root 0 2005-07-09 13:45:59 ./usr/bin/
> >>drwxr-xr-x root/root 0 2005-07-09 13:45:59 ./usr/sbin/
> >>
> >>
> >
> >/usr/sbin and /usr/sbin are useless, don't create them. They look like
> >the default entries for the dirs file created by dh_make :)
> >
> >
> done.
>
> >[...]
> >
> >
> >>make[1]: Leaving directory `/home/rajulocal/practice/fortranposix-0.1'
> >>dh_testdir
> >>dh_testroot
> >>dh_installchangelogs CHANGES
> >>dh_installdocs
> >>dh_installexamples
> >>dh_installman
> >>dh_link
> >>dh_strip
> >>dh_compress
> >>dh_fixperms
> >>dh_installdeb
> >>dh_shlibdeps
> >>dh_gencontrol
> >>dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
> >>dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
> >>dh_md5sums
> >>dh_builddeb
> >>dpkg-deb: building package `libfortranposix0-dev' in
> >>`../libfortranposix0-dev_0.1-1_i386.deb'.
> >>dpkg-deb: building package `libfortranposix0' in
> >>`../libfortranposix0_0.1-1_i386.deb'.
> >> signfile fortranposix_0.1-1.dsc
> >>
> >>
> >
> >can't see dh_install in the above list, might be the problem?
> >Could you eventually put your debian/* scrips somewhere to give them a
> >look?
> >
> >
>
> I have added dh_install in the binary-arch: stanza of the rules files.
> Still the library files are not included in the .deb files.
Try:
dh_install --sourcedir=debian/tmp
in the rules file.
Steve
> The new
> build.log can be found at
>
> http://24.58.7.0/debian-mentors/fortranposix-0.1/build.log
>
> Is there any website where I can upload the debian directory? For now, I
> have set up a web server on my laptop and all the relevent files can be
> found at
>
> http://24.58.7.0/debian-mentors/
>
> If there is any public website where I can upload this stuff that would
> be great.
>
> thanks
> raju
>
> --
> Kamaraju S Kusumanchi
> Graduate Student, MAE
> Cornell University
> http://www.people.cornell.edu/pages/kk288/
>
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
library naming problem
Hi, I've been helping to package the GDAL library. It contains a C and a C++ API. The upstream maintainer has decided not to guarantee ABI compatibility even between minor releases. He updates the SONAME correctly for the C API. Hopefully we can manage to split the two APIs into different packages. But for now, how should I name the package when the ABI has changed, but the SONAME hasn't? The SONAME is libgdal.so.1. The new release is 1.3.1. I've thought of using libgdal1.3.1-1 as the package name. Thanks for any pointers, Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: QGIS
Hi, I'm looking for a sponsor for QGIS. QGIS is a geographic data viewer capable of displaying shapefiles. It supports feature identification and display of attribute tables. It also supports display of georeferenced raster images and Digital Elevation Models. The web site for QGIS is http://qgis.sourceforge.net/ . You can access the package using: deb http://bullhorn.org/debian unstable main deb-src http://bullhorn.org/debian unstable main Thanks, Steve Halasz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: QGIS
Jochen, Thanks very much! > Just two comments: > > You created a native Debian package for QGIS. In October, there was a > short discussion in d-mentors about the gdal package from Silke Reimer > whether to use native packages or not (see > http://lists.debian.org/debian-mentors/2003/debian-mentors-200310/msg00176.html > ). Please have a second thought whether to use a native package or not. Ok, I see the problem with creating a native package. I'll recreate the package based on the last release (0.0.13). > My first attempt to build on Alpha failed: > > qtiffio.cpp:22:20: tiffio.h: No such file or directory > > Apparently, the build depends are not sufficient (probably libtiff3g-dev > is missing). You can avoid problems like this by trying to build your > package using pbuilder in a clean chroot environment. I'll do this. Thanks again, Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Need help getting package built on arm
Hi, My package, qgis, has failed to build on arm. The error is: uic: error while loading shared libraries: libICE.so.6: cannot open shared object file: No such file or directory When this first happened, I checked on packages.d.o and IIRC could not find a package on arm that contained that file. Now I can. So I suspect that it will work now. Should I just bump up my xlibs-dev build dep to the latest version and upload the package to be built again? Thanks for your help, Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Erroneous postrm-unsafe-ldconfig?
Hi, lintian gives the following complaint about the libgrass package: W: libgrass: postrm-unsafe-ldconfig The postrm is below and it looks to me like ldconfig will only be called when the first argument is remove. Am I missing something? Should I file a bug against lintian? Thanks, Steve #!/bin/sh # Make sure grass library dir is removed from ld.so.conf # Lifted from xfree86 package's shell-lib.sh script set -e dir="/usr/lib/grass/lib" ldsoconf="/etc/ld.so.conf" if [ "$1" = "remove" ]; then # is the line present? if fgrep -qsx "$dir" "$ldsoconf"; then # rewrite the file (very carefully) set +e fgrep -svx "$dir" "$ldsoconf" > "$ldsoconf.dpkg-tmp" fgrep_status=$? set -e case $fgrep_status in 0|1) ;; # we don't actually care if any lines matched or not *) die "error reading \"$ldsoconf\"; fgrep exited with status" \ "$fgrep_status" ;; esac set +e cmp -s "$ldsoconf.dpkg-tmp" "$ldsoconf" cmp_status=$? set -e case $cmp_status in 0) rm "$ldsoconf.dpkg-tmp" ;; # files are identical 1) mv "$ldsoconf.dpkg-tmp" "$ldsoconf" ;; # files differ *) die "error comparing \"$ldsoconf.dpkg-tmp\" to \"$ldsoconf\"; cmp" \ "exited with status $cmp_status" ;; esac ldconfig fi fi exit 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
On Tue, 2005-04-12 at 20:44 +0200, Miriam Ruiz wrote: > Hi, > > The author of one of the packages I was packaging for > my own use has asked me to be the maintainer of the > debian's package. The problem that I found is that in > latest versions he includes his own version of > debian's directory inside the original tar.gz file as > you download it from the web. > > I've tried to explain to him the reasons behind doing > it the proper way, with a diff file, but I don't think > I was able to do that too well. Quoting him: "The > reason I added debian subdirectory is to distribute it > with the source files." > > Any suggestions on how to deal with that? You could explain that distributing the debian dir in this way is problematic because the debian files in the release will never be up-to-date with respect to the release as you change things and increment the debian revision. And the author isn't going to make a new release for each debian revision. In addition it makes your job harder because you are patching against an out of date debian dir in the release. And it causes confusion for others trying to build a deb who end up using out of date files in the release (I have experienced this). For one program I package upstream was anxious to have the debian dir in CVS, but I was able to convince them to exclude it from the releases for these reasons. Steve > Greetings, > Miry > > > > > __ > Renovamos el Correo Yahoo!: Â250 MB GRATIS! > Nuevos servicios, mÃs seguridad > http://correo.yahoo.es > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
On Tue, 2005-04-12 at 22:40 +0200, martin f krafft wrote: > also sprach Margarita Manterola <[EMAIL PROTECTED]> [2005.04.12. +0200]: > > It makes sense for software developers to have their own ./debian > > directory so that they can use debian/rules binary to compile and > > test their software while developing it. > > Huh? Why not just use ./Makefile? > > > What does not make a lot of sense is to release the .tar.gz with > > the ./debian directory, as Steve Halasz said, it's perfectly valid > > to have it in CVS the important point would be to convince them > > not to include it in the release. > > I disagree. ./debian is the domain of the Debian maintainer, not of > the upstream. Unless you are developing software *for* *Debian* > (native), there is no reason why you should bother with ./debian at > all. In my case some upstream developers were debian users who liked to be able to build debs from CVS. This has been helpful since they can make sure the app will work ok in debian before they release. It's not strictly necessary, but I'm glad they're thinking of Debian and don't want to discourage them. Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: QGIS
Hi, I'm looking for a sponsor for QGIS. QGIS is a geographic data viewer capable of displaying shapefiles. It supports feature identification and display of attribute tables. It also supports display of georeferenced raster images and Digital Elevation Models. The web site for QGIS is http://qgis.sourceforge.net/ . You can access the package using: deb http://bullhorn.org/debian unstable main deb-src http://bullhorn.org/debian unstable main Thanks, Steve Halasz
Re: RFS: QGIS
Jochen, Thanks very much! > Just two comments: > > You created a native Debian package for QGIS. In October, there was a > short discussion in d-mentors about the gdal package from Silke Reimer > whether to use native packages or not (see > http://lists.debian.org/debian-mentors/2003/debian-mentors-200310/msg00176.html > ). Please have a second thought whether to use a native package or not. Ok, I see the problem with creating a native package. I'll recreate the package based on the last release (0.0.13). > My first attempt to build on Alpha failed: > > qtiffio.cpp:22:20: tiffio.h: No such file or directory > > Apparently, the build depends are not sufficient (probably libtiff3g-dev > is missing). You can avoid problems like this by trying to build your > package using pbuilder in a clean chroot environment. I'll do this. Thanks again, Steve
