RFS: libgnupdf (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.1~20100604-1 of my package libgnupdf. It builds these binary packages: libgnupdf-dbg - PDF support library (debug) libgnupdf-dev - PDF support library (development) libgnupdf0 - PDF support library The package appears to be lintian clean. The upload would fix these bugs: 543848 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libgnupdf - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libgnupdf/libgnupdf_0.1~20100604-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Bhavani Shankar.R https://launchpad.net/~bhavi, a proud ubuntu community member. What matters in life is application of mind!, It makes great sense to have some common sense..!
Re: RFS: xpdf (updated package)
On Fri, Jun 04, 2010 at 12:29:07AM -0400, Michael Gilbert wrote: In terms of xpdf performance, can those concerned please try files that they consider big with the poppler-ized version and compare that to the original xpdf so we can actually quantify the impact (if there even is one). Speculating doesn't really get us anywhere. We need a quantified impact. I have not tested the poplerized version of xdpf yet. Because you mentioned speculations, let me in turn say that I have not seen your answers yet on the questions I raised in my first mail (besides some speculations, of course). Rogério mentioned some facts (thanks!) but could you please provide more details? Again, I want to upload this package to experemental first for testing purposes; and large file handling would be a very good set of tests. Yes, this sounds reasonable. -- Stanislav -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604075600.ga24...@kaiba.homelan
RFS: vmtk
Dear mentors, debian-science, I am looking for a sponsor for my package vmtk. * Package name: vmtk Version: 0.9~bzr276 Upstream Author: Luca Antiga and David Steinman * URL: http://www.vmtk.org * License: BSD, Modified MIT Section: non-free/science It builds these binary packages: vmtk - the Vascular Modeling Toolkit libvmtk0.9 - runtime libraries for vmtk libvmtk-dev - shared links and header files for vmtk python-vmtk - Python interface for vmtk The package appears to be lintian clean. The upload would fix ITP bug 584222. The package can be found on packages.simula.no: - URL: http://packages.simula.no/pool/main/v/vmtk/ - Source repository: deb-src http://packages.simula.no/ unstable main - dget http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc or - svn co svn://svn.debian.org/svn/debian-science/packages/vmtk/trunk The package needs to go into non-free because it links against non-free software (Tetgen). The upstream tarball also includes files from Tetgen. This has been discussed with upstream. I would appreciate it very much if someone uploaded this package for me. Kind regards, Johannes Ring PS: It would be nice if the DM-Upload-Allowed: yes control field could be added. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilwykp5qyz0uti74lgarafa1eklpqudevyia...@mail.gmail.com
Re: RFS: xpdf (updated package)
On 06/04/2010 01:36 AM, Michael Gilbert wrote:
Thanks for spotting this! I've just uploaded xpdf with a versioned
depenedency on libpoppler-dev:
http://mentors.debian.net/debian/pool/main/x/xpdf
Just for the record, it seems that things will break again with poppler 0.13.x.
At least, it does with my version of xpdf-poppler. Not sure with yours. But,
then, I intend to get your version and cherry pick some of the patches that I
have produced and put them together.
I have one patch, in particular, that would be good to send you.
To be honest, I don't like this my and yours here. Can we join efforts here?
I want to have everything integrated, alive and healthy. I don't like fragmented
efforts.
Regards,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c08c2e1.9070...@ime.usp.br
RFS: rush
Dear mentors, I am seeking an __active__ sponsor for this package. In comparison to the first packaging attempt, the Debian specific documentation has been expanded, in particular concerning chrooted service access, and a helper program 'mkchroot-rush.pl' has been included in order to ease the population of minimal chroot directories. These are the particulars of this new package: Package name: rush Version:1.6-1 Upstream author:Sergey Poznyakoff g...@gnu.org.ua URL:http://puszcza.gnu.org.ua/projects/rush/ License:GPL-3 Section:Shells This source package builds one binary package: gnurush-- restricted user shell The package is pedantically lintian clean and builds in pbuilder for testing as well as for unstable, using i386 and amd64. I am motivated to maintain this package as I keep an interest of providing limited access accounts for special purpose systems. Presently, I am not in a position to put this package to professional use, but I hope to be in the future, or at least see spin-off knowledge from keeping this package under my supervision. Access to the package is achieved at mentors.debian.net: URL http://mentors.debian.net/debian/pool/main/r/rush dget http://mentors.debian.net/debian/pool/main/r/rush/rush_1.6-1.dsc Repos deb-src http://mentors.debian.net/debian/pool/main/r/rush unstable main Best regards, Mats Erik Andersson, fil. dr mats.anders...@gisladisker.se Subscriptions: debian-mentors, debian-devel-games, debian-perl, debian-ipv6, debian-qa signature.asc Description: Digital signature
Re: RFS: trimage
Paul Gevers wrote: I have: /trimage_1.0.2.orig.tar.gz (containing the whole source but not debian/) /trimage_1.0.2.diff.tar.gz (containing just debian/) /trimage-1.0.2/ (from which I build, containing both) Yet the empty-debian-diff error persists. What am I doing wrong? Oops and of course the should NOT be in that directory, but in the parent directory of /trimage-1.0.2 For instance my winff package looks like: ~/winff ~/winff/winff-1.2.0/ ~/winff/winff_1.2.0-2.debian.tar.gz ~/winff/winff_1.2.0.orig.tar.gz I didn't create the debian tar manually, but let the package builder create it (in my case pbuilder). Paul In your ~/winff/winff-1.2.0/ directory, is there a debian/ folder? Because that would be the exact configuration I use (A *.debian.tar.gz gets generated for me, as well) Kilian -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c08d420.1060...@kilianvalkhof.com
Re: RFS: vmtk
Hi Christophe, On Fri, Jun 4, 2010 at 12:09 PM, Christophe Prud'homme prudh...@debian.org wrote: Hi Johannes I am compiling it now. Thanks, that is great! I let you know when it is done if all goes right I upload ! could I upload the package in Debian science too (svn-buildpackage) ? I'm not sure. I didn't inject the package. Is it maybe enough to set the svn property 'mergeWithUpstream' on the debian directory? Like this: svn propset mergeWithUpstream 1 debian If so, please go ahead and do that. If not, maybe it is better to remove the directory and inject it properly with this: http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc ? Best regards, Johannes Best regards C. On Fri, Jun 4, 2010 at 10:23 AM, Johannes Ring joha...@simula.no wrote: Dear mentors, debian-science, I am looking for a sponsor for my package vmtk. * Package name: vmtk Version: 0.9~bzr276 Upstream Author: Luca Antiga and David Steinman * URL: http://www.vmtk.org * License: BSD, Modified MIT Section: non-free/science It builds these binary packages: vmtk - the Vascular Modeling Toolkit libvmtk0.9 - runtime libraries for vmtk libvmtk-dev - shared links and header files for vmtk python-vmtk - Python interface for vmtk The package appears to be lintian clean. The upload would fix ITP bug 584222. The package can be found on packages.simula.no: - URL: http://packages.simula.no/pool/main/v/vmtk/ - Source repository: deb-src http://packages.simula.no/ unstable main - dget http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc or - svn co svn://svn.debian.org/svn/debian-science/packages/vmtk/trunk The package needs to go into non-free because it links against non-free software (Tetgen). The upstream tarball also includes files from Tetgen. This has been discussed with upstream. I would appreciate it very much if someone uploaded this package for me. Kind regards, Johannes Ring PS: It would be nice if the DM-Upload-Allowed: yes control field could be added. -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilwykp5qyz0uti74lgarafa1eklpqudevyia...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiluer3712lrk5f1ecdgwxzj9itx6sw8lq2in...@mail.gmail.com
Re: RFS: vmtk
Hi Johannes I am compiling it now. I let you know when it is done if all goes right I upload ! could I upload the package in Debian science too (svn-buildpackage) ? Best regards C. On Fri, Jun 4, 2010 at 10:23 AM, Johannes Ring joha...@simula.no wrote: Dear mentors, debian-science, I am looking for a sponsor for my package vmtk. * Package name: vmtk Version: 0.9~bzr276 Upstream Author: Luca Antiga and David Steinman * URL: http://www.vmtk.org * License: BSD, Modified MIT Section: non-free/science It builds these binary packages: vmtk - the Vascular Modeling Toolkit libvmtk0.9 - runtime libraries for vmtk libvmtk-dev - shared links and header files for vmtk python-vmtk - Python interface for vmtk The package appears to be lintian clean. The upload would fix ITP bug 584222. The package can be found on packages.simula.no: - URL: http://packages.simula.no/pool/main/v/vmtk/ - Source repository: deb-src http://packages.simula.no/ unstable main - dget http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc or - svn co svn://svn.debian.org/svn/debian-science/packages/vmtk/trunk The package needs to go into non-free because it links against non-free software (Tetgen). The upstream tarball also includes files from Tetgen. This has been discussed with upstream. I would appreciate it very much if someone uploaded this package for me. Kind regards, Johannes Ring PS: It would be nice if the DM-Upload-Allowed: yes control field could be added. -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilwykp5qyz0uti74lgarafa1eklpqudevyia...@mail.gmail.com
Re: RFS: rush
Mats Erik Andersson mats.anders...@gisladisker.se writes: I am seeking an __active__ sponsor for this package. What distinction are you drawing with that qualifier (“__active__”)? What are you seeking beyond a sponsor for the package? -- \“The whole area of [treating source code as intellectual | `\property] is almost assuring a customer that you are not going | _o__) to do any innovation in the future.” —Gary Barnett | Ben Finney pgp2P0hubtPtV.pgp Description: PGP signature
Re: RFS: rush
fredag den 4 juni 2010 klockan 20:58 skrev Ben Finney detta: Mats Erik Andersson mats.anders...@gisladisker.se writes: I am seeking an __active__ sponsor for this package. What distinction are you drawing with that qualifier (???__active__???)? What are you seeking beyond a sponsor for the package? Well, I had one in the mid of April, he made a quick look, made an excuse for making it superficial, and have not been heard of since for this package, or for windowlab, which he also accepted. My use of __active__ was to catch somewhone that will not go missing for months on end. I do not deserve to be hanging, the package does not, and the Debian community as a whole does not. I would rather see a quick denial of a package, with sound motivation, than be hanging on a loose thread. My capability in maintainership should not be missing, since I am a co-maintainer of netkit-ftp and linux-ftpd. -- Mats Erik Andersson, fil. dr 2459 41E9 C420 3F6D F68B 2E88 F768 4541 F25B 5D41 Abonnerar på: debian-mentors, debian-devel-games, debian-perl, debian-ipv6, debian-qa -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604111220.ga2...@mea.homelinux.org
Re: RFS: vmtk
Johannes I just uploaded vmtk. I removed vtm from DebianScience and svn-injected it (with mergeWithUpstream) Best regards C. On Fri, Jun 4, 2010 at 12:24 PM, Johannes Ring joha...@simula.no wrote: Hi Christophe, On Fri, Jun 4, 2010 at 12:09 PM, Christophe Prud'homme prudh...@debian.org wrote: Hi Johannes I am compiling it now. Thanks, that is great! I let you know when it is done if all goes right I upload ! could I upload the package in Debian science too (svn-buildpackage) ? I'm not sure. I didn't inject the package. Is it maybe enough to set the svn property 'mergeWithUpstream' on the debian directory? Like this: svn propset mergeWithUpstream 1 debian If so, please go ahead and do that. If not, maybe it is better to remove the directory and inject it properly with this: http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc ? Best regards, Johannes Best regards C. On Fri, Jun 4, 2010 at 10:23 AM, Johannes Ring joha...@simula.no wrote: Dear mentors, debian-science, I am looking for a sponsor for my package vmtk. * Package name: vmtk Version: 0.9~bzr276 Upstream Author: Luca Antiga and David Steinman * URL: http://www.vmtk.org * License: BSD, Modified MIT Section: non-free/science It builds these binary packages: vmtk - the Vascular Modeling Toolkit libvmtk0.9 - runtime libraries for vmtk libvmtk-dev - shared links and header files for vmtk python-vmtk - Python interface for vmtk The package appears to be lintian clean. The upload would fix ITP bug 584222. The package can be found on packages.simula.no: - URL: http://packages.simula.no/pool/main/v/vmtk/ - Source repository: deb-src http://packages.simula.no/ unstable main - dget http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc or - svn co svn://svn.debian.org/svn/debian-science/packages/vmtk/trunk The package needs to go into non-free because it links against non-free software (Tetgen). The upstream tarball also includes files from Tetgen. This has been discussed with upstream. I would appreciate it very much if someone uploaded this package for me. Kind regards, Johannes Ring PS: It would be nice if the DM-Upload-Allowed: yes control field could be added. -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilwykp5qyz0uti74lgarafa1eklpqudevyia...@mail.gmail.com
Re: RFS: vmtk
Christophe, On Fri, Jun 4, 2010 at 1:01 PM, Christophe Prud'homme prudh...@debian.org wrote: Johannes I just uploaded vmtk. Great! Thanks! I removed vtm from DebianScience and svn-injected it (with mergeWithUpstream) Good. Actually I see now that I did in fact svn-inject that package but I somehow forgot. Sorry about that. I see that you didn't add the DM-Upload-Allowed flag in debian/control. It would be great if I could upload after it is accepted the first time. What do you think? Best regards, Johannes Best regards C. On Fri, Jun 4, 2010 at 12:24 PM, Johannes Ring joha...@simula.no wrote: Hi Christophe, On Fri, Jun 4, 2010 at 12:09 PM, Christophe Prud'homme prudh...@debian.org wrote: Hi Johannes I am compiling it now. Thanks, that is great! I let you know when it is done if all goes right I upload ! could I upload the package in Debian science too (svn-buildpackage) ? I'm not sure. I didn't inject the package. Is it maybe enough to set the svn property 'mergeWithUpstream' on the debian directory? Like this: svn propset mergeWithUpstream 1 debian If so, please go ahead and do that. If not, maybe it is better to remove the directory and inject it properly with this: http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc ? Best regards, Johannes Best regards C. On Fri, Jun 4, 2010 at 10:23 AM, Johannes Ring joha...@simula.no wrote: Dear mentors, debian-science, I am looking for a sponsor for my package vmtk. * Package name: vmtk Version: 0.9~bzr276 Upstream Author: Luca Antiga and David Steinman * URL: http://www.vmtk.org * License: BSD, Modified MIT Section: non-free/science It builds these binary packages: vmtk - the Vascular Modeling Toolkit libvmtk0.9 - runtime libraries for vmtk libvmtk-dev - shared links and header files for vmtk python-vmtk - Python interface for vmtk The package appears to be lintian clean. The upload would fix ITP bug 584222. The package can be found on packages.simula.no: - URL: http://packages.simula.no/pool/main/v/vmtk/ - Source repository: deb-src http://packages.simula.no/ unstable main - dget http://packages.simula.no/pool/main/v/vmtk/vmtk_0.9~bzr276-1.dsc or - svn co svn://svn.debian.org/svn/debian-science/packages/vmtk/trunk The package needs to go into non-free because it links against non-free software (Tetgen). The upstream tarball also includes files from Tetgen. This has been discussed with upstream. I would appreciate it very much if someone uploaded this package for me. Kind regards, Johannes Ring PS: It would be nice if the DM-Upload-Allowed: yes control field could be added. -- To UNSUBSCRIBE, email to debian-science-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilwykp5qyz0uti74lgarafa1eklpqudevyia...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktim-mrmrd7zmk6rbwofyk55pntivy2nwkf0kp...@mail.gmail.com
editing former patches
Manao ahoana, Hello, Bonjour, Let's consider the package slim, from here: https://launchpad.net/ubuntu/lucid/+source/slim/1.3.1-4/+files/ When I get it with apt-get source the untared folder is already patched. I dont like the way it's patched because it defaults to the Debian theme. And also, most of the patch is the Debian theme (debian-moreblue-orbit). I would like to build a separate package for themes and keep the other patches, which are, I think, necessary: - adding the debian/ directory - patching the original code for various reasons How to? Would you please help me? Misaotra, Thanks, Merci. -- Architecte Informatique chez Blueline/Gulfsat: Administration Systeme, Recherche Developpement +261 3456 000 19 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604144432.60d1e...@pbmiha.malagasy.com
Re: editing former patches
Mihamina Rakotomandimby miham...@gulfsat.mg wrote on 2010-06-04 14:44: When I get it with apt-get source the untared folder is already patched. This is the new behaviour with Debian's source format 3.0 (quilt). I would like to build a separate package for themes and keep the other patches, which are, I think, necessary: - adding the debian/ directory - patching the original code for various reasons How to? Would you please help me? Simple use this command: dpkg-source -x --skip-patches foo.dsc Then the patches will no more executed. Fondest regards, Joachim Wiedorn signature.asc Description: PGP signature
Re: RFS: trimage
On Fri, Jun 04, 2010 at 12:23:28PM +0200, Kilian Valkhof wrote: Paul Gevers wrote: For instance my winff package looks like: ~/winff ~/winff/winff-1.2.0/ ~/winff/winff_1.2.0-2.debian.tar.gz ~/winff/winff_1.2.0.orig.tar.gz I didn't create the debian tar manually, but let the package builder create it (in my case pbuilder). Paul In your ~/winff/winff-1.2.0/ directory, is there a debian/ folder? Because that would be the exact configuration I use (A *.debian.tar.gz gets generated for me, as well) Hmm, are you using source format 3.0 (as shown by debian/source/format) ? I guess you may be from the multiple tarballs. I'm afraid I don't have any experience with that yet, I don't know what it's supposed to do about the (possibly empty) .diff.gz. Nick -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604121311.ga15...@leverton.org
Re: editing former patches
Joachim Wiedorn wrote: Mihamina Rakotomandimby miham...@gulfsat.mg wrote on 2010-06-04 14:44: When I get it with apt-get source the untared folder is already patched. This is the new behaviour with Debian's source format 3.0 (quilt). Nope, the slim package referred to is a 1.0 package. From what I can tell (but I did not dig too deep) the theme is put in to the debian/ part, not sure if the build part includes it from there or not (I never looked up the debian/rules). I would like to build a separate package for themes and keep the other patches, which are, I think, necessary: - adding the debian/ directory - patching the original code for various reasons How to? Would you please help me? Simple use this command: dpkg-source -x --skip-patches foo.dsc Then the patches will no more executed. Fondest regards, Joachim Wiedorn ~Niels signature.asc Description: OpenPGP digital signature
Re: editing former patches
Niels Thykier ni...@thykier.net wrote on 2010-06-04 14:46: Nope, the slim package referred to is a 1.0 package. From what I can tell (but I did not dig too deep) the theme is put in to the debian/ part, not sure if the build part includes it from there or not (I never looked up the debian/rules). No I have looked into the package. The themes can be found in the debian directory as: - debian-moreblue.shar - debian-moreblue-orbit.shar Both files are bash-files and they will be executed by debian/rules. Only the theme text04 theme is inside the original source (slim_1.3.1.orig.tar.gz) Fondest regards, Joachim Wiedorn signature.asc Description: PGP signature
Re: RFS: rush
Mats Erik Andersson mats.anders...@gisladisker.se writes: Well, I had one in the mid of April, he made a quick look, made an excuse for making it superficial, and have not been heard of since for this package, or for windowlab, which he also accepted. There may be a misconception, then. A sponsor only has a commitment to the one upload that they sponsor. If you manage to establish an ongoing relationship with a person who consistently sponsors subsequent releases, great! But it's not something to demand or expect. My use of __active__ was to catch somewhone that will not go missing for months on end. I do not deserve to be hanging, the package does not, and the Debian community as a whole does not. Right. You should always feel free to ask for sponsors here if the previous sponsor is too busy or unresponsive. I would rather see a quick denial of a package, with sound motivation, than be hanging on a loose thread. That would certainly be nice. But as described above, you have other options than simply waiting powerlessly in that case. -- \ “I knew things were changing when my Fraternity Brothers threw | `\ a guy out of the house for mocking me because I'm gay.” | _o__) —postsecret.com, 2010-01-19 | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87hbliao3h@benfinney.id.au
Re: editing former patches
Joachim Wiedorn ad_deb...@joonet.de : Simple use this command: dpkg-source -x --skip-patches foo.dsc This will skip all the patches. It helps me. Now, how to split the diff.gz in order to select the only patches I want? Is there a tool for that? -- Architecte Informatique chez Blueline/Gulfsat: Administration Systeme, Recherche Developpement +261 3456 000 19 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604171039.4da16...@pbmiha.malagasy.com
Re: RFS: xpdf (updated package)
Hi Rogério,
On Do, 03 Jun 2010, Rogério Brito wrote:
http://rb.doesntexist.org/blog/2010/05/27/please-let-me-zoom-my-documents/
I read that, and might I suggest ps_view? (also pdf viewer). It is
installed by default on TeX Live on Windows, and it is available
form source forege. It is *MINIMAL* small, uses lua, some ps code,
and it is hundredthousandtimes better than any ps/pdf viewer I have
seen. You can zoom ad infinitum, because it is the only program
that does not render the full page, but uses PS clipping. It has nice
rulers for evaluating the desing, etc etc etc
Probably the best place to get it is from the TeX Live svn/rsync
as we did the necessary chagnes.
Well, I have it running here, too, but I am too lazy to make a
package for Debian for it.
Best wishes
Norbert
Norbert Preiningprein...@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
which will engulf the
Galaxy in fire and destruction, and possibly bring the
Universe to a premature doom. I mean it,' he added.
with luck I'll be
drunk enough not to notice.'
--- Ford ensuring everyone knew where his priorities lay.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100604143154.gw22...@gamma.logic.tuwien.ac.at
Re: editing former patches
Mihamina Rakotomandimby miham...@gulfsat.mg wrote on 2010-06-04 17:10: This will skip all the patches. It helps me. Now, how to split the diff.gz in order to select the only patches I want? For this work I recommend to make the usual unpack: dpkg-source -x --skip-patches foo.dsc (for format 3.0) or dpkg-source -x foo.dsc (for format 1.0) and then use the both theme files inside debian directory: - debian/debian-moreblue.shar - debian/debian-moreblue-orbit.shar Start these script files as shown in debian/rules: sh debian/debian-moreblue.shar sh debian/debian-moreblue-orbit.shar The result should be: - debian/debian-moreblue/ - debian/debian-moreblue-orbit/ Then you need to change a line in slim.conf (see one patch file): # current theme, use comma separated list to specify a set to # randomly choose from -current_theme default +current_theme debian-moreblue-orbit Fondest regards, Joachim Wiedorn signature.asc Description: PGP signature
Re: editing former patches
Joachim Wiedorn ad_deb...@joonet.de : Mihamina Rakotomandimby miham...@gulfsat.mg wrote on 2010-06-04 17:10: This will skip all the patches. It helps me. Now, how to split the diff.gz in order to select the only patches I want? and then use the both theme files inside debian directory: - debian/debian-moreblue.shar - debian/debian-moreblue-orbit.shar Start these script files as shown in debian/rules: sh debian/debian-moreblue.shar sh debian/debian-moreblue-orbit.shar The result should be: - debian/debian-moreblue/ - debian/debian-moreblue-orbit/ -current_theme default +current_theme debian-moreblue-orbit Hum... Joachim, I just want to do the opposite: - remove patches related to the debian-more-blue - keep all remaining patches -- Architecte Informatique chez Blueline/Gulfsat: Administration Systeme, Recherche Developpement +261 3456 000 19 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604181118.2f72b...@pbmiha.malagasy.com
Re: RFS: rush
On 4 June 2010 12:12, Mats Erik Andersson mats.anders...@gisladisker.se wrote: fredag den 4 juni 2010 klockan 20:58 skrev Ben Finney detta: Mats Erik Andersson mats.anders...@gisladisker.se writes: I am seeking an __active__ sponsor for this package. What distinction are you drawing with that qualifier (???__active__???)? What are you seeking beyond a sponsor for the package? Well, I had one in the mid of April, he made a quick look, made an excuse for making it superficial, and have not been heard of since for this package, or for windowlab, which he also accepted. That would be me. :) I have been busy, and had to fix my own RC bugs this week - I don't think I've seen a second version of the 'rush' packaging from you since I commented on the version in April, although I could just have missed it. Yes, I should look at windowlab as well, and I should have acked your mails. -- Tim Retout t...@retout.co.uk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimeb4d4f0jcrow0q6dk88lkfppcpx4xztdfq...@mail.gmail.com
RFS: micro-evtd (updated package)
Dear mentors, I am looking for a sponsor for the new version 1:3.3+svn147-1 of my package micro-evtd. It builds these binary packages: micro-evtd - Linkstation Pro/Kurobox Pro special features support micro-evtd-udeb - Linkstation Pro/Kurobox Pro special features support - udeb (udeb) The package appears to be lintian --pedantic clean. I am submitting this package update for sponsorship because the original maintainer does not have time to prepare a new revision and is not a full DD with upload access. My primary interest in the package is to fix bug #580549 and thus complete the support for this NAS platform in debian-installer, hopefully in time for squeeze. The upload would fix these bugs: 534257, 534931, 580549 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/micro-evtd - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/micro-evtd/micro-evtd_3.3+svn147-1.dsc Thanks, Ryan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimyjam06xwmrnkgcs9wavmrjh5rvqq1rk19g...@mail.gmail.com
Re: RFS: xpdf (updated package)
On Fri, 4 Jun 2010 11:56:00 +0400, Stanislav Maslovski wrote: On Fri, Jun 04, 2010 at 12:29:07AM -0400, Michael Gilbert wrote: In terms of xpdf performance, can those concerned please try files that they consider big with the poppler-ized version and compare that to the original xpdf so we can actually quantify the impact (if there even is one). Speculating doesn't really get us anywhere. We need a quantified impact. I have not tested the poplerized version of xdpf yet. Because you mentioned speculations, let me in turn say that I have not seen your answers yet on the questions I raised in my first mail (besides some speculations, of course). Rogério mentioned some facts (thanks!) but could you please provide more details? I can't say anything definitive, but I can speculate that it will not be a problem, and here is the logic: xpdf's rendering code is itself essentially an older version of poppler. I doubt the poppler developers have intentionally made that code itself any slower, and it was possible to interface xpdf to poppler without a significant rewrite (a couple minor few-line patches and a bunch of variable renaming that doesn't have any impact). Hence any performance differences to be found between evince and xpdf will reside in the non-poppler code. Restated; even with switch to poppler, the original xpdf zoom/display logic remains, and that will be the primary driving factor for performance. But even so, it should be tested. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604160521.3e6dc593.michael.s.gilb...@gmail.com
Re: RFS: xpdf (updated package)
* Rogério Brito rbr...@ime.usp.br, 2010-06-03, 16:00: I have been keeping in touch with Michael about such smaller version of xpdf and, in fact, I started a xpdf-poppler project, Count me as one who won't use such a bastardized version of xpdf. Thank you very much for your warm reception. :-) Don't get me wrong: I believe that all PDF readers in Debian suck and I appreciate that you want to change that state. However, I'd like you to bear in mind that some people are using xpdf because of features that you are going to inadvertently kill e.g. decent font handling or modest dependencies. -- Jakub Wilk signature.asc Description: Digital signature
Re: Overriding upstream build system
Am Donnerstag, den 03.06.2010, 23:18 +0200 schrieb Stefano Canepa: Hi all, I'm trying to release the new gsoap libraries as dynamic libraries, as I know I need to release a -dev package with the static libraries and I'm not able to patch the autotools files used by gsoap but I know how to get the desired result using cmake may I provide a CMakelist.txt as a patch and use cmake to build my package? Why does gsoap ship a diff.gz, which patches all Makefiles from automake 1.9.2 to 1.6.3? JFTR: The soapcpp2/Makefile.am file defines the libraries in lib_LIBRARIES. But this is an automake variable and it builds AFAIK static libraries only. To build the shared library you need libtool and a corresponding _LTLIBRARIES variable. The patch is trivial, but you'll need to libtoolize the sources and rerun all autotools. So it is probably better to talk to upstream. Regards, Daniel -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1275689884.5305.29.ca...@haktar.wgdd.de
Re: RFS: gedit-r-plugin
Hi, On Tue, Jun 1, 2010 at 08:44, Mateusz Kaduk mateusz.ka...@gmail.com wrote: Dear Sandro, I activated Vcs fields, fixed copyright for 2009-2010, removed python-support and uploaded package to http://mentors.debian.net/debian/pool/main/g/gedit-r-plugin I hope everything is fine now and package can be uploaded. What did you use to import the package in git? there is a tool, git-import-dsc to handle this, creating one branch for upstream code, and then merging it into master where you can do teh packaging, you might want to try it and update teh repo then. Other than that, it looked fine, so i've just uploaded: thanks for your contribution to Debian! Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimstaix2bcnopmbmh6gog6kz6fwp4jnrruoj...@mail.gmail.com
Re: editing former patches
On Jun 04 2010, Mihamina Rakotomandimby wrote:
This will skip all the patches. It helps me.
Now, how to split the diff.gz in order to select the only patches I
want?
Have a look at filterdiff, lsdiff and friends. And, for the love of
$DEITY, split the patches in sets that make things like this easier, if
they are not split yet.
And contribute back what you've done.
Regards,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100604213630.ga16...@ime.usp.br
Re: RFS: xpdf (updated package)
On Fri, Jun 04, 2010 at 04:05:21PM -0400, Michael Gilbert wrote: I can't say anything definitive, but I can speculate that it will not be a problem, and here is the logic: xpdf's rendering code is itself essentially an older version of poppler. I doubt the poppler developers have intentionally made that code itself any slower, and it was possible to interface xpdf to poppler without a significant rewrite (a couple minor few-line patches and a bunch of variable renaming that doesn't have any impact). Hence any performance differences to be found between evince and xpdf will reside in the non-poppler code. Restated; even with switch to poppler, the original xpdf zoom/display logic remains, and that will be the primary driving factor for performance. But even so, it should be tested. BTW, where did you get it from that my main concerns are about speed? You seem to be focused only on this. Actually, my point was quite the contrary, please re-read my mails. We already have a poppler-based viewer which is reasonably fast - it is evince, but unfortunately it does not work enough well with every possible pdf file (often crashes). On the other hand, xpdf opens all files without any problems, but can be a bit slower in scrolling sometimes. The last is not a problem. I am simply afraid that with your change xpdf will follow evince's path and there will be no reliable pdf viewer in the repository anymore. -- Stanislav -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100604222022.ga28...@kaiba.homelan
Re: RFS: libgnupdf (updated package)
Please do not use HTML email: http://www.debian.org/MailingLists/#codeofconduct On Fri, Jun 4, 2010 at 3:31 PM, Bhavani Shankar R bh...@ubuntu.com wrote: I am looking for a sponsor for the new version 0.1~20100604-1 of my package libgnupdf. Some comments: Please read libpkg-guide and its two bugs if you haven't already. debian/rules upstream target should be named get-orig-source: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules debian/watch should not mention lintian. In addition it isn't very clear, I'd suggest this instead: # Right now GNUpdf is under heavy development and they have not released a version yet. debian/changelog need not mention lintian either, except maybe in thanks. Insert my standard comment about library package descriptions being almost duplicates of each other. Think about the audience for each one. -dev package will be manually installed by people developing apps using liboauth and also as part of build-depends. The library should only be installed automatically so it doesn't need a verbose description. The debug symbols will be manually installed (at least for now) but don't need the detail of the -dev package. Similarly, the library package does not need AUTHORS installed. Your orig.tar.gz contains two copies of the source code, one in trunk/ - I imagine your debian/rules upstream target is broken. Since it is an autotools based project, I would suggest running upstream's 'make distcheck' to create the tarball instead of doing manually. If any files are missing from the result or if it fails to build you can send upstream a patch. There are some files upstream forgot to add a license grant to: ./src/base/pdf-stm-be.h: *No copyright* UNKNOWN ./src/base/pdf-stm-be.c: *No copyright* UNKNOWN ./torture/unit/runtests.c: UNKNOWN The copyright years in debian/control should be 1987 to 2010. The info documentation should not be in the library package, instead put it in the -dev package or a separate documentation package. It is a policy violation to put files whose names do not change into the library package. Please either move the utils and info docs to the -dev package or split them out into gnupdf-utils/libgnupdf-doc packages (or similar). The package FTBFS in pbuilder (missing build-depends on check). In addition it requires a newer version of check than is in sid or released upstream: The following required libraries are too old: libcheck (svn required) In addition, I wonder if the following need to be added to build-deps: checking for libjpeg... no checking for libjbig2dec... no checking for libcurl... no checking for libiconv... no checking for texi2html... no I stopped reviewing the package at this point due to the FTBFS. Once you figure out how to work around the issues with 'check', please run the following lintian command: lintian --info --display-info --display-experimental --pedantic --show-overrides --checksums --color auto foo.changes -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimxeh54eubufzujeem2kyxt2ibytu-s22xwt...@mail.gmail.com
Re: RFS: xburst-tools
Hi, Paul Wise wrote: Please remove these prebuilt files from the debian/ directory and don't add them to the upstream tarball. ./debian/xburst_stage1.bin ./debian/xburst_stage2.bin ./debian/stage1.bin [...] The README.source indicates that this requires a cross-compiler for MIPS in the $PATH. Since we don't have one in Debian yet, your package cannot be uploaded as-is. You could however, build and upload from a MIPS machine with gcc installed. This part was my doing, sorry. It should be possible to build these on mipsel (and they should probably be split out to an arch-all package anyway), but that makes it difficult for people without access to a non-pocket-sized MIPS machine to test the build process. From http://db.debian.org/machines.cgi?sortby=architecturesortorder=asc I infer that there is not even a mipsel porterbox available to DDs. Would the cross-compiled version would be a candidate for contrib? The correct long-term solution, of course, is to get gcc-mips into Debian. Anyone with ideas about how to make that happen? You include an embedded code copy (or fork) of the Qi bootloader. Please remove it and package Qi separately. I wonder if usbboot/ is also an embedded code copy. The source package is based on the upstream xburst-tools repository; it probably should be split into separate packages for qiboot, xbboot, usbboot, and so on, since they do not depend at build-time or run-time on one another. It is not my impression that these have been split already. The piece most people currently use is usbboot (which is based on a Windows tool from Ingenic). Earlier versions of the packaging included just that. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100605041356.ga2...@progeny.tock
Re: RFS: libgnupdf (updated package)
On Sat, Jun 5, 2010 at 8:49 AM, Paul Wise p...@debian.org wrote: Please do not use HTML email: http://www.debian.org/MailingLists/#codeofconduct On Fri, Jun 4, 2010 at 3:31 PM, Bhavani Shankar R bh...@ubuntu.com wrote: I am looking for a sponsor for the new version 0.1~20100604-1 of my package libgnupdf. Some comments: Please read libpkg-guide and its two bugs if you haven't already. debian/rules upstream target should be named get-orig-source: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules debian/watch should not mention lintian. In addition it isn't very clear, I'd suggest this instead: # Right now GNUpdf is under heavy development and they have not released a version yet. debian/changelog need not mention lintian either, except maybe in thanks. Insert my standard comment about library package descriptions being almost duplicates of each other. Think about the audience for each one. -dev package will be manually installed by people developing apps using liboauth and also as part of build-depends. The library should only be installed automatically so it doesn't need a verbose description. The debug symbols will be manually installed (at least for now) but don't need the detail of the -dev package. Similarly, the library package does not need AUTHORS installed. Your orig.tar.gz contains two copies of the source code, one in trunk/ - I imagine your debian/rules upstream target is broken. Since it is an autotools based project, I would suggest running upstream's 'make distcheck' to create the tarball instead of doing manually. If any files are missing from the result or if it fails to build you can send upstream a patch. There are some files upstream forgot to add a license grant to: ./src/base/pdf-stm-be.h: *No copyright* UNKNOWN ./src/base/pdf-stm-be.c: *No copyright* UNKNOWN ./torture/unit/runtests.c: UNKNOWN The copyright years in debian/control should be 1987 to 2010. The info documentation should not be in the library package, instead put it in the -dev package or a separate documentation package. It is a policy violation to put files whose names do not change into the library package. Please either move the utils and info docs to the -dev package or split them out into gnupdf-utils/libgnupdf-doc packages (or similar). The package FTBFS in pbuilder (missing build-depends on check). In addition it requires a newer version of check than is in sid or released upstream: The following required libraries are too old: libcheck (svn required) In addition, I wonder if the following need to be added to build-deps: checking for libjpeg... no checking for libjbig2dec... no checking for libcurl... no checking for libiconv... no checking for texi2html... no I stopped reviewing the package at this point due to the FTBFS. Once you figure out how to work around the issues with 'check', please run the following lintian command: lintian --info --display-info --display-experimental --pedantic --show-overrides --checksums --color auto foo.changes Okay paul thanks for your real good review .. ll work on it Regards -- Bhavani Shankar.R https://launchpad.net/~bhavi, a proud ubuntu community member. What matters in life is application of mind!, It makes great sense to have some common sense..!
Re: RFS: xburst-tools
On Sat, Jun 5, 2010 at 12:13 PM, Jonathan Nieder jrnie...@gmail.com wrote: This part was my doing, sorry. It should be possible to build these on mipsel (and they should probably be split out to an arch-all package anyway), but that makes it difficult for people without access to a non-pocket-sized MIPS machine to test the build process. From http://db.debian.org/machines.cgi?sortby=architecturesortorder=asc I infer that there is not even a mipsel porterbox available to DDs. Seems that is the case, things are improving though: http://lists.debian.org/debian-devel-announce/2010/04/msg00010.html http://lists.debian.org/debian-devel-announce/2010/05/msg5.html A temporary solution to this would be to find a sponsor with a Debian mips/mipsel install on MIPS hardware. Some pointers to possible places to find such people can be found here (page needs updating btw): http://www.debian.org/ports/mips/ Alternatively get sharism.cc to donate/lend a Ben NanoNote to some willing person. I imagine Would the cross-compiled version would be a candidate for contrib? I think yes. I assume this woud be a source package that build-depends on the gcc MIPS cross compiler package generated by the new buildcross package in unstable. The correct long-term solution, of course, is to get gcc-mips into Debian. Anyone with ideas about how to make that happen? One option is to update the gcc-X.Y source packages to build gcc-X.Y-mips cross-compiler packages on i386/amd64. This means a lot of extra buildd and maintainer build time. The approach taken by gcc-mingw32 (cross-compiler for Windows 32-bit and 64-bit) seems to be to duplicate the gcc source code. Something that may be possible down the track, once the Debian archive can support source package synchronisation (for license compliance), is to create gcc-X.Y-mips source packages that build-depend on gcc-X.Y-source and build and ship a cross-compilers from them. The source package is based on the upstream xburst-tools repository; it probably should be split into separate packages for qiboot, xbboot, usbboot, and so on, since they do not depend at build-time or run-time on one another. It is not my impression that these have been split already. Sounds good to me. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin9enh27bhiq7hmmxb3uf-8nqtb9qg0v5tkp...@mail.gmail.com
Re: RFS: xburst-tools
Paul Wise wrote: I assume this woud be a source package that build-depends on the gcc MIPS cross compiler package generated by the new buildcross package in unstable. Oh! Thanks for the pointer. Something that may be possible down the track, once the Debian archive can support source package synchronisation (for license compliance), is to create gcc-X.Y-mips source packages that build-depend on gcc-X.Y-source and build and ship a cross-compilers from them. Ah, so dak is the place to fix this[1]? Very good, will take a look... Sounds good to me. Thanks for all the advice. Regards, Jonathan [1] I remember http://lists.debian.org/debian-devel/2009/11/msg00136.html http://lists.debian.org/debian-devel-announce/2009/11/msg1.html but was not aware of anything coming of it. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100605053632.ga2...@progeny.tock
Re: RFS: xburst-tools
On Sat, Jun 5, 2010 at 1:36 PM, Jonathan Nieder jrnie...@gmail.com wrote: Ah, so dak is the place to fix this[1]? Very good, will take a look... Yes. I'm sure the ftpmasters would be very grateful for a helping hand there. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinutq3112k8t0xp5jdbjktmhdgd6fe-0lpz1...@mail.gmail.com
