Re: RFS: joystick (updated package)
On Wed, 23 Jul 2008 02:04:41 +, Joe Nahmias <[EMAIL PROTECTED]> wrote: > Thanks for picking this up and for your work on it. Just a few comments: > > 0 - There's a priority mismatch, you should change it to extra to > match the override file. > 1 - You should move to a newer debhelper version, v4 is really old at > this point. Thanks for the suggestions! These are easy enough... > 2 - It doesn't look like it'd take too much to accomodate #475049 -- > just a quick change and the writing of a short manpage. See if you > can do this. I thought about handling this one as well, but evtest is also shipped in lineakd (with a manpage), so adding it would require some coordination. I suppose I could just add a "Conflicts:" and see if anyone complains, but it seems a bit late in the game to get this particular change done correctly and still have an updated package in Lenny, doesn't it? > 3 - It seems to me that some of the patches currently in > debian/patches went upstream a while ago. It might be worthwhile > packaging a newer CVS snapshot and using that. The last CVS update was to inputattach.c, on February 8 2006; apart from that there had been no changes since April 22 2005. The version of inputattach.c used in my updated package is taken from http://kernel.org/pub/linux/kernel/people/dtor/inputattach.c rather than upstream CVS (the version used includes all the changes in the last CVS update). > 4 - Also, it would be better to forward these patches to upstream (if > they're still alive). As far as I can determine there is no upstream now... I'll try contacting Vojtech Pavlik anyway, he's still active on LKML. > Otherwise, it looks good and if you fix 0,1,2 I'd be happy to sponsor it. Thanks! I'll upload a new version with 0 and 1 fixed as well as Ben's updated short description. Regards, Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: joystick (updated package)
On Wed, 23 Jul 2008 11:38:50 +1000, Ben Finney <[EMAIL PROTECTED]> wrote: > Stephen Kitt <[EMAIL PROTECTED]> writes: > > joystick - Testing and calibration tools > > That synopsis should follow the Best Packaging Practices > http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-pkg-synopsis>. > [...] > A better synopsis might be: > > set of testing and calibration tools for joysticks Thanks, I didn't think to check the short description when going over the package! I'll fix it in the next upload. Regards, Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: protobuf
On Sun, Jul 13, 2008 at 06:43:14PM +0200, Iustin Pop wrote: > Dear mentors, > > I am looking for a sponsor for my new package "protobuf". > > * Package name: protobuf > Version : 2.0.0~b-1 > Upstream Author : Google Inc. > * URL : http://code.google.com/p/protobuf/ > * License : Apache-2 > Section : devel Hello, The package has been re-uploaded, now with Java bindings packaged too and a few improvements (see http://git.debian.org/?p=collab-maint/protobuf.git for the packaging history). I would be very glad if some can help me with this upload, or with comments about it. The package builds these binary packages: libprotobuf-dev - protocol buffer C++ library (development headers) libprotobuf-java - Java bindings for protocol buffers libprotobuf0 - protocol buffer C++ library protobuf-compiler - compiler for protocol buffer definition files python-protobuf - Python bindings for protocol buffers It can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/protobuf - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/protobuf/protobuf_2.0.0~b-1.dsc many thanks, iustin signature.asc Description: Digital signature
Re: RFS: dict-foldoc (adopted package)
On Sat, Jul 12, 2008 at 11:13:55AM +0200, Iustin Pop wrote: > On Sat, Jul 12, 2008 at 06:03:14PM +1000, Ben Finney wrote: > > Iustin Pop <[EMAIL PROTECTED]> writes: > > > > > dict-foldoc - FOLDOC Dictionary Database > > > > No need to Capitalise Ordinary Words in the Package Synopsis. A better > > synopsis would be: > > > > FOLDOC dictionary database > > Thanks, fixed and uploaded new version (20080708-2). Hi, Could anyone help me with the upload of this package? Or more comments about it? It can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/dict-foldoc - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/dict-foldoc/dict-foldoc_20080708-2.dsc thanks, iustin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: joystick (updated package)
Hi Stephen, On Wed, Jul 23, 2008 at 01:25:47AM +0200, Stephen Kitt wrote: > Dear mentors, > > I am looking for a sponsor for the new version 20051019-3 > of the package "joystick", which I'd like to adopt (it's been orphaned since > February, and last had a maintainer upload in October 2005). [snip] > The upload would fix these bugs: 144768, 338139, 419342, 444142, 465928; in > particular 338139 is annoying for Lenny since it can lead to warnings when > switching to a dependency-based boot. Thanks for picking this up and for your work on it. Just a few comments: 0 - There's a priority mismatch, you should change it to extra to match the override file. 1 - You should move to a newer debhelper version, v4 is really old at this point. 2 - It doesn't look like it'd take too much to accomodate #475049 -- just a quick change and the writing of a short manpage. See if you can do this. 3 - It seems to me that some of the patches currently in debian/patches went upstream a while ago. It might be worthwhile packaging a newer CVS snapshot and using that. 4 - Also, it would be better to forward these patches to upstream (if they're still alive). Otherwise, it looks good and if you fix 0,1,2 I'd be happy to sponsor it. --Joe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: joystick (updated package)
Stephen Kitt <[EMAIL PROTECTED]> writes: > joystick - Testing and calibration tools That synopsis should follow the Best Packaging Practices http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-pkg-synopsis>. The above synopsis is too vague, not telling the reader what it is for. It also should be an appositive clause, not capitalised like the start of a sentence. A better synopsis might be: set of testing and calibration tools for joysticks -- \ “Liberty, n. One of imagination's most precious possessions.” | `\ —Ambrose Bierce, _The Devil's Dictionary_, 1906 | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: joystick (updated package)
Dear mentors, I am looking for a sponsor for the new version 20051019-3 of the package "joystick", which I'd like to adopt (it's been orphaned since February, and last had a maintainer upload in October 2005). It builds these binary packages: joystick - Testing and calibration tools The package appears to be lintian clean. The upload would fix these bugs: 144768, 338139, 419342, 444142, 465928; in particular 338139 is annoying for Lenny since it can lead to warnings when switching to a dependency-based boot. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/j/joystick - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/j/joystick/joystick_20051019-3.dsc I would be glad if someone uploaded this package for me. Kind regards Stephen Kitt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: quick-lounge-applet (updated package)
Hi, Is anybody interested in review and upload this package? Thanks. El lun, 14-07-2008 a las 20:38 +0200, Diego Fernández Durán escribió: > Dear mentors, > > I am looking for a sponsor for the new version 2.12.5-2 > of my package "quick-lounge-applet". > > It builds these binary packages: > quick-lounge-applet - GNOME panel applet to organise preferred applications > > The package appears to be lintian clean. > > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/q/quick-lounge-applet > - Source repository: deb-src http://mentors.debian.net/debian unstable main > contrib non-free > - dget > http://mentors.debian.net/debian/pool/main/q/quick-lounge-applet/quick-lounge-applet_2.12.5-2.dsc > > I would be glad if someone uploaded this package for me. > > Kind regards > Diego Fernández Durán > -- Diego Fdez. Durán <[EMAIL PROTECTED]> | http://www.goedi.net GPG : 925C 9A21 7A11 3B13 6E43 50DB F579 D119 90D2 66BB signature.asc Description: Esta parte del mensaje está firmada digitalmente
RFS: libmina-java
Hi, On Tuesday 22 July 2008 05:38:42 Rail Aliev wrote: > On Tuesday 22 July 2008 00:28:25 Damien Raude-Morvan wrote: > > You're right : use of cdbs make debian/rules shorter but on the other > > hand I also found jh_build calls cleaner than a custom debian/build.xml > > we must maintain. > > +1, let's go with your one. > > Is there anything in your TODO list or the package ready for mentors? ;) It's now ready for prime time :) Thanks for your help (I've listed you in debian/changelog and granted you copyright on packaging scripts in debian/copyright) The upload would fix #491626 ITP bug. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/m/mina - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/m/mina/mina_1.1.7.dfsg-1.dsc This package build fine in a SID pbuilder. I'm looking for a mentor/sponsor to review it and upload it if it's ok. Cheers, -- Damien Raude-Morvan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: sclapp and pytagsfs (updated packages)
HI Giridhar! Y Giridhar Appaji Nag schrieb: > python-sclapp (0.5.2-1) - framework for Python command-line applications > >* New upstream release > + sclapp.txt is now licensed under GPLv2+ >* Update Standards-Version to 3.8.0 > > http://mentors.debian.net/debian/pool/main/s/sclapp That one is fine... > pytagsfs (0.7.0-1) - maps media files to an arbitrary directory structure > >* New upstream release > + Needs python-fuse >= 0.2 >* Remove patch 02_fuse_exceptions merged upstream >* Update Standards-Version to 3.8.0 (no changes required) ... but that one fails to build from source (tested with an up to date sid using pbuilder): == dpatch cat-all >>patch-stampT mv -f patch-stampT patch-stamp dh_testdir python setup.py build Traceback (most recent call last): File "setup.py", line 22, in from tests.common import TEST_DIR, TEST_DATA_DIR File "tests/common.py", line 17, in from sclapp.util import importName ImportError: No module named sclapp.util make: *** [build-stamp] Error 1 dpkg-buildpackage: failure: debian/rules build gave error exit status 2 pbuilder: Failed autobuilding of package -> Aborting with an error == Yours sincerely, Alexander signature.asc Description: OpenPGP digital signature
Re: RFS: uncrustify (updated existing package)
Hi Johann, > I am looking for a sponsor for the new version 0.48-1 > of my package "uncrustify". > > It builds these binary packages: > uncrustify - C, C++, C#, D, Java and Pawn source code beautifier > Uncrustify is a highly configurable source code formatter. > It aligns preprocessor define's, assigments, arithmetics and is > able to fix spacing between operators. [...] > I would be glad if someone uploaded this package for me. Uploaded. Regards, Laszlo/GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Rply me urgently if interested
新しいメールアドレスをお知らせします新しいメールアドレス： [EMAIL PROTECTED] I am issa khalam Staff of BOA Bank in Burkina faso. I would like you to indicate your interest to receive the transfer of10.5 M Dollars. I will like you to stand as the next of kin to my late client whose account is presently dormant, for claim. Yours faithfully, Dr issa khalam - Dr issa khalam
Re: RFS: libenglab
Quoting Ben Finney <[EMAIL PROTECTED]>: Harry Serenis <[EMAIL PROTECTED]> writes: libenglab - A cross compile mathematical platform with a C like syntax libenglab-dev - A cross compile mathematical platform with a C like syntax Please follow the Best Packaging PRactices for the package synopsis http://www.debian.org/doc/developers-reference/ch-best-pkging-practices#s-bpp-pkg-synopsis>. Also, please ensure the synopsis shows why one package is different from another; the above two synopses are identical. The synopsis has been changed. The grammar is now compliant with debian best packaging practices. The synopsis are now different from another The updated packages can be found: - URL: http://mentors.debian.net/debian/pool/main/l/libenglab - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libenglab/libenglab_0.2.2-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setup Clean Etch Build Environment
On Tue, Jul 22, 2008 at 02:08:34PM +0200, Marko Randjelovic wrote: > How to set clean Etch build environment, so I can backport a package from > testing to etch? pbuilder, just like you would setup a lenny or sid build environment. - Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Setup Clean Etch Build Environment
On Tue, Jul 22, 2008 at 8:08 PM, Marko Randjelovic <[EMAIL PROTECTED]> wrote: > How to set clean Etch build environment, so I can backport a package from > testing to etch? Install etch into a chroot, separate partition or separate computer. For these, you can use debootstrap/cdeboostrap or the Debian installer. cowbuilder/pbuilder should also support creating etch chroots (IIRC, cowbuilder needs a special option passed to it though, see the manpage). -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Setup Clean Etch Build Environment
How to set clean Etch build environment, so I can backport a package from testing to etch? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new maintainer questions
Le Tuesday 22 July 2008 13:41:42 Jeffrey Ratcliffe, vous avez écrit : > 2008/7/22 Andreas Schildbach <[EMAIL PROTECTED]>: > > 1) Is is actually needed to do the packaging work on a Debian system, or > > would a derivative like Ubuntu also do? I would always test my package > > on a "real" Debian before putting it up for sponsoring or uploading, but > > having to do actual development on Debian would mean a parallel > > installation of a Debian Desktop. Those of you packaging for both Debian > > and Ubuntu, do you switch systems all the time? > > I use Ubuntu (Hardy ATM), but the important thing to do before > uploading to -mentors or ftpmaster is to build the package in a sid > chroot. I don't believe it's safe to simply build the package in sid. There can be important difference between ubuntu and debian that would break the package under debian while it is working in ubuntu. As soon as you have a chroot, it's really not difficult at all to also *test* the package in the chroot. Romain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new maintainer questions
2008/7/22 Andreas Schildbach <[EMAIL PROTECTED]>: > 1) Is is actually needed to do the packaging work on a Debian system, or > would a derivative like Ubuntu also do? I would always test my package > on a "real" Debian before putting it up for sponsoring or uploading, but > having to do actual development on Debian would mean a parallel > installation of a Debian Desktop. Those of you packaging for both Debian > and Ubuntu, do you switch systems all the time? I use Ubuntu (Hardy ATM), but the important thing to do before uploading to -mentors or ftpmaster is to build the package in a sid chroot. Having made it into sid, packages get synced into Ubuntu automatically provided that there are no Ubuntu changes to be merged. Intrepid has just gone into Debian sync freeze, so if you want your package in Intrepid, you will have to file a LP bug and give a reason. Regards Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
new maintainer questions
Hi there, being a long time Debian (and derivatives) user, I am thinking about starting to package for Debian. First, I'd like to try my luck on phpMyID, a very simple single-user OpenID identity provider. This isn't available as a Debian package yet, and there is no intent that I am aware of. I have read through the guides and FAQs available for new maintainers, but there are some questions I could not answer: 1) Is is actually needed to do the packaging work on a Debian system, or would a derivative like Ubuntu also do? I would always test my package on a "real" Debian before putting it up for sponsoring or uploading, but having to do actual development on Debian would mean a parallel installation of a Debian Desktop. Those of you packaging for both Debian and Ubuntu, do you switch systems all the time? 2) phpMyID is implemented in PHP, which is not the language I am most familiar with - but it should be easy to learn. My primary language is Java, but I couldn't find any simple Java packages to start with that I actually miss. How important is the implementation language for package maintainers? Should I still try for my first package? 3) The guides suggest to start with adopting an existing package rather than creating a new one. A package that I could imaging adopting would be "jabber" (jabberd, an XMPP server), simply because there is a new upstream version for quite some time now that I'd really like to have packaged. However, I feel that jabberd is a project way too big for my first package, even if I could base my work on an existing package. phpMyId is only 1800 lines of code. How would you decide? Best regards, Andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Question about Debian-native package
El Tuesday 22 July 2008 11:20:40 Ben Finney escribió: > Noel David Torres Taño <[EMAIL PROTECTED]> writes: > > > I'm the (new) maintainer of wmaker-data which is a package > > containing files from several upstream sources. Some files have been > > downloaded from one place, some from other place, etc. > > > > Which is the recommended practice here? > > If the package could reasonably be useful outside the context of > Debian, it should not be a Debian-native package. The Debian > packaging, and the (possibly empty) set of changes to the upstream > source, should be separated from the "pristine" upstream source. Thanks, that mention of "could reasonably be useful outside the context of Debian" is the point I didn't had in mind. > > > I see the following options: > > > > A) - The package was put together specifically for Debian, so it > > must be native > > No. See Developer's Reference §6.7.8.2, "Repackaged Upstream Source": > > You **should** upload packages with a pristine source tarball if > possible, but there are various reasons why it might not be > possible. This is the case if upstream does not distribute the > source as gzipped tar at all, or if [non-free]. > > In these cases the developer must construct a suitable > .orig.tar.gz file himself. We refer to such a tarball as a > repackaged upstream source. Note that a repackaged upstream source > is different from a Debian-native package. A repackaged source > still comes with Debian-specific changes in a separate .diff.gz > and still has a version number composed of and > . > I readed it but I feel it is better to ask if not completely sure. > > B) - The files are not for Debian > > or rather, they are meaningfully useful outside Debian. > > > so it must not be native and needs a orig.tar.gz > > Yes. > > > I feel that correct answer is B but here is where the real problem > > arises for me. How to set up a orig.tar.gz file from several places? > > Construct a procedure to do so automatically, e.g. a command-line > program. Set a target 'get-orig-source' in the 'debian/rules' file > that invokes the program you just wrote. I will do. > > For an example that I recently had to do myself, see the > 'lojban-common' package version 1.5-2. For another, see 'vim-scripts' > version 20080705-1. > > -- > \Hercules Grytpype-Thynne: “Well, Neddie, I'm going to be | > `\ frank.” Ned Seagoon: “Right, I'll be Tom.” Count Moriarty: | > _o__) “I'll be Gladys.” *slap* —The Goon Show, _World War I_ | > Ben Finney > > Many thanks. Next version will behave that way. Thanks (again) Noel Torres er Envite signature.asc Description: This is a digitally signed message part.
RFS: uncrustify (updated existing package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for the new version 0.48-1 of my package "uncrustify". It builds these binary packages: uncrustify - C, C++, C#, D, Java and Pawn source code beautifier Uncrustify is a highly configurable source code formatter. It aligns preprocessor define's, assigments, arithmetics and is able to fix spacing between operators. The package appears to be lintian clean. The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/u/uncrustify - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/u/uncrustify/uncrustify_0.48-1.dsc I would be glad if someone uploaded this package for me. Johann Rudloff -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiFrMIACgkQvK4p2+m5syfC0wCghFSvPIPFHvMX76USOrLfxhAJ 644AnRsOxZB6V6SIheuYhvnPqbz+KFkD =E+im -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Question about Debian-native package
Noel David Torres Taño <[EMAIL PROTECTED]> writes: > I'm the (new) maintainer of wmaker-data which is a package > containing files from several upstream sources. Some files have been > downloaded from one place, some from other place, etc. > > Which is the recommended practice here? If the package could reasonably be useful outside the context of Debian, it should not be a Debian-native package. The Debian packaging, and the (possibly empty) set of changes to the upstream source, should be separated from the "pristine" upstream source. > I see the following options: > > A) - The package was put together specifically for Debian, so it > must be native No. See Developer's Reference §6.7.8.2, "Repackaged Upstream Source": You **should** upload packages with a pristine source tarball if possible, but there are various reasons why it might not be possible. This is the case if upstream does not distribute the source as gzipped tar at all, or if [non-free]. In these cases the developer must construct a suitable .orig.tar.gz file himself. We refer to such a tarball as a repackaged upstream source. Note that a repackaged upstream source is different from a Debian-native package. A repackaged source still comes with Debian-specific changes in a separate .diff.gz and still has a version number composed of and . > B) - The files are not for Debian or rather, they are meaningfully useful outside Debian. > so it must not be native and needs a orig.tar.gz Yes. > I feel that correct answer is B but here is where the real problem > arises for me. How to set up a orig.tar.gz file from several places? Construct a procedure to do so automatically, e.g. a command-line program. Set a target 'get-orig-source' in the 'debian/rules' file that invokes the program you just wrote. For an example that I recently had to do myself, see the 'lojban-common' package version 1.5-2. For another, see 'vim-scripts' version 20080705-1. -- \Hercules Grytpype-Thynne: “Well, Neddie, I'm going to be | `\ frank.” Ned Seagoon: “Right, I'll be Tom.” Count Moriarty: | _o__) “I'll be Gladys.” *slap* —The Goon Show, _World War I_ | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libenglab
Harry Serenis <[EMAIL PROTECTED]> writes:
> libenglab - A cross compile mathematical platform with a C like syntax
> libenglab-dev - A cross compile mathematical platform with a C like syntax
Please follow the Best Packaging PRactices for the package synopsis
http://www.debian.org/doc/developers-reference/ch-best-pkging-practices#s-bpp-pkg-synopsis>.
Also, please ensure the synopsis shows why one package is different
from another; the above two synopses are identical.
Better synopses for these packages might be:
> libenglab - A cross compile mathematical platform with a C like syntax
cross-compiling mathematical platform with C-like syntax - run-time library
> libenglab-dev - A cross compile mathematical platform with a C like syntax
cross-compiling mathematical platform with C-like syntax - development files
There may be other improvements as well.
The synopsis should fit sensibly into the hypothetical sentence
template:
is {a,an,the}
--
\ “I watched the Indy 500, and I was thinking that if they left |
`\ earlier they wouldn't have to go so fast.” —Steven Wright |
_o__) |
Ben Finney
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Question about Debian-native package
Hello all I'm the (new) maintainer of wmaker-data which is a package containing files from several upstream sources. Some files have been downloaded from one place, some from other place, etc. Which is the recommended practice here? I see the following options: A) - The package was put together specifically for Debian, so it must be native B) - The files are not for Debian, so it must not be native and needs a orig.tar.gz I feel that correct answer is B but here is where the real problem arises for me. How to set up a orig.tar.gz file from several places? Thanks in advance Noel Torres er Envite signature.asc Description: This is a digitally signed message part.
