Re: CDBS duplicate docs installation
* William Vera [EMAIL PROTECTED] [080917 03:57]: 2008/9/16 Charles Plessy [EMAIL PROTECTED]: it is probably that debhelper installs the docs (README AUTHORS ChangeLog TODO) in /usr/share/docs/foo and the makefile in /usr/doc/foo (see Makefile.am). The file names of the docs are generic enough that Debhelper guesses them. Thanks, that appears it is the problem, so I guess just need patch Makefile.am I'm correct? Patching Makefile.am is usually the last thing to do. There are usually many easier things: * just let make do it's game and remove the files from debian/packagename/usr/doc afterwards. (Looking at what is currently at mentors, that seems to be done already).. * tell make to install things elsewhere. Automake generated Makefiles files are usually properly parameterized, so you can just give it an additional argument. Sometimes you can even give that to configure. In this case, just call make install with argument docsdir=/usr/share/doc/scroot (and then tell dh_installdocs to not install those again at the same place with -X) Hochachtungsvoll, Bernhard R. Link P.S: your configure handling looks a bit off. You have an empty config.status: configure which will confuse make if someone asks for build-stamp directly, and your configure-status target depends on patch instead of patch-stamp. (and if you name the rule configure-stamp instead of config.status, you whould create those file at the end). Additionally please also set CFLAGS, otherwise your debian/rules might do funny things when called directly and not via some dpkg-buildpackage helper script. And tell upstream that -O3 does not belong into INCLUDES variable... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Advice about first package building (from sources)
Laurent Guignard wrote: I have read the main documentation about pbuilder but i haven't seen if it is possible to build a package from upstream sources. In all examples, the command is like pbuilder build ???.dsc What is the correct method to build a package from upstream sources ? I thought to build a virtual host (KVM), install all packages needed, import all sources (upstream with all files needed to build package) and run the dpkg-buildpackage command... All this to keep a clean and stable Debian on my laptop ;) Is there another method and where can i found documentation ? You do not need pbuilder for your purposes, not even chroots. What you need is to *create* Debian source package using upstream sources. Read more at http://www.debian.org/doc/maint-guide/ Then, you could build and install the binary package you wanted in your own clean and stable Debian environment. After that, you can safely remove all build dependencies. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Advice about first package building (from sources)
Hi Laurent, Al Nikolov said: Laurent Guignard wrote: I have read the main documentation about pbuilder but i haven't seen if it is possible to build a package from upstream sources. In all examples, the command is like pbuilder build ???.dsc What is the correct method to build a package from upstream sources ? I thought to build a virtual host (KVM), install all packages needed, import all sources (upstream with all files needed to build package) and run the dpkg-buildpackage command... All this to keep a clean and stable Debian on my laptop ;) I fear the answers you got might have been a bit confusing, but it's also because it's not clear what you mean with keeping a clean and stable Debian: only install packaged software (nothing by hand), or really not do anything out of the normal (e.g. compiling and packaging) on your laptop, or both. I'm kind of a both guy, so: - I created an unstable CHROOT jail with debootstrap and do all my packaging in there (as suggested by Neil). For this purpose, KVM, Xen or any VM is as good, but more heavyweight. - I check that my packages build correctly with pbuilder (and pbuilder is really only meant for this). - Neither pbuilder nor debootstrap will help you to learn Debian packaging, hence the advice from Al to read http://www.debian.org/doc/maint-guide/ Hope this helps, Eric PS: I directed my answer back to you because it was not clear if you are subscribed to Mentors. -- Eric de France, d'Allemagne et de Navarre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Quilt and patches directory
В Mon, 15 Sep 2008 21:28:54 +0200, Michael Biebl написа: I didn't know that foo: bar baz will result in bar/baz run in parallel. I thought there is some kind of guarantee that bar is processed first. Consider this example which illustrates that it's not a safe assumption to make always even with non-parallel make: cat makefile 'EOF' do-%: bar-% baz-% @true bar-%: @echo I am first! baz-foo: @echo I should be second. baz-frob: @echo Something else. EOF $ make do-foo I should be second. I am first! $ make -j2 do-foo I should be second. I am first! $ make do-frob Something else. I am first! When pattern rules come to the picture, and a pattern rule has prerequisites which exist or are explicitly mentioned like here, they always take precedence. You just have to be careful. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: wallpaper-tray (updated package)
Hey Vincent, Thanks for all the advice. I'm a little busy this week, I will try to look at it in the weekend. Regards, Guido 2008/9/12 Vincent Bernat [EMAIL PROTECTED] OoO En cette nuit nuageuse du jeudi 21 août 2008, vers 01:10, Guido Loupias [EMAIL PROTECTED] disait : I am looking for a sponsor for the new version 0.5.5-1 of my package wallpaper-tray. Hi Guido! You switched to a patch management system. Good point. However, the patch is unreadable. I suppose that you needed to rerun autoconf stuff. In this case, just patch Makefile.am or configure.ac and depends on autotools to generate all this stuff. This way, you keep the patch to the minimal size. You should look at the list of the opened bugs for this package. Maybe this new upstream package fixes some of them. You should also close #326671. AUTHORS and MAINTAINERS do not contain any new information with respect to debian/copyright. I think that you can safely not ship them. You depend on debhelper 7 but do not use any feature of it. Stick to debhelper 5, this will ease the work of backporters. I am not sure, but since you ship a gconf schema, you need to register it. I think dh_gconf can do it. -- BOFH excuse #300: Digital Manipulator exceeding velocity parameters
How to remove package completely?
Dear Mentors, I'd like to remove bluetooth-alsa and libsbc from Debian completely. It was already removed (at my request) from unstable, but it is still in Lenny. How can I remove it from Lenny? Reportbug tell me that package does not exist when trying to request removal. Should I send my request to release team. Regards, -- Krzysztof Burghardt [EMAIL PROTECTED] http://www.burghardt.pl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to remove package completely?
IIRC the removals from testing should happen automatically or semi-automatically. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to remove package completely?
Hello Krzysztof, On Wed, Sep 17, 2008 at 13:12, Krzysztof Burghardt [EMAIL PROTECTED] wrote: I'd like to remove bluetooth-alsa and libsbc from Debian completely. It was already removed (at my request) from unstable, but it is still in Lenny. How can I remove it from Lenny? It is usually done some days after removal from unstable, in an automatic way. Be worried if in a week or so, nothing will happen. In that case, please contact ftp-master team in order to resolve the situatuon. Kindly, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian/control best practices
Hi mentors I have a question, I am packaginf sitebar package wichis on mentorsdebian.net, and have gotten a suggestion, but it got confused me in one way, debian developeres reference talks about debian control best practices and I understand that ( and one more person say me the same ) that synposys must be on lower cases http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis package-name is a synopsis. but all the packages that I have seen was on this way Package-name is a synopsis. The first leeter is on uppercase what is the right? thanks regards -- Carlos Eduardo Sotelo Pinto ( KrLoS ) Free and OpenSource Software Developer GNULinux Registered User #379182 GNULinux Registered Machine #277661 GNULinux Arequipa Users Group||Debian Arequipa Users Group -- pgp.rediris.es 0xF8554F6B GPG FP:697E FAB8 8E83 1D60 BBFB 2264 9E3D 5761 F855 4F6B -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dbconfig-common
Hi mentors I have a question, I am building the sitebar package wichis on mentorsdebian.net, and this package has whishlist item bug #382166 who is relationed with this lintian report http://lintian.debian.org/maintainer/[EMAIL PROTECTED] I had fixed this problem on sitebar building package changing /usr/sbin/mysql to just mysqld but, how about the bug, itsuggest to change to dbconfig-common, then what i must do first, just correct or change the postinst to debconfig-common regards -- Carlos Eduardo Sotelo Pinto ( KrLoS ) Free and OpenSource Software Developer GNULinux Registered User #379182 GNULinux Registered Machine #277661 GNULinux Arequipa Users Group||Debian Arequipa Users Group -- pgp.rediris.es 0xF8554F6B GPG FP:697E FAB8 8E83 1D60 BBFB 2264 9E3D 5761 F855 4F6B -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/control best practices
Hi Carlos, On Wed, 2008-09-17 at 07:21 -0500, Carlos Eduardo Sotelo Pinto wrote: I have a question, I am packaginf sitebar package wichis on mentorsdebian.net, and have gotten a suggestion, but it got confused me in one way, debian developeres reference talks about debian control best practices and I understand that ( and one more person say me the same ) that synposys must be on lower cases http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis package-name is a synopsis. but all the packages that I have seen was on this way Package-name is a synopsis. The first leeter is on uppercase what is the right? You are only meant to write the 'synopsis' part of the sentence. So if the intended synopsis is Foo is a bar, then the first line of the description in the control file would simply be bar. Hope this helps, Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dbconfig-common
Hi Dne Wed, 17 Sep 2008 07:29:35 -0500 Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] napsal(a): I have a question, I am building the sitebar package wichis on mentorsdebian.net, and this package has whishlist item bug #382166 who is relationed with this lintian report http://lintian.debian.org/maintainer/[EMAIL PROTECTED] I had fixed this problem on sitebar building package changing /usr/sbin/mysql to just mysqld but, how about the bug, itsuggest to change to dbconfig-common, then what i must do first, just correct or change the postinst to debconfig-common Have you looked at debconfig-common docs? -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
rc bug on happydoc
Hi mentors I have a question, I am building the python-happydoc package wichis on mentorsdebian.net, this package has a rc bug #497703, that refer an incomplete debian copyright, wel it happen on upstreamer version 2.1 but was fixed on upstreamer version 3, now I am helping on python happydoc development, but was delted from lenny and it must get back to lenny+ my question is what must i do, fix the problem on hapydoc 2.1 o get the upstreamer new version and fix on this new version the bug thanks -- Carlos Eduardo Sotelo Pinto ( KrLoS ) Free and OpenSource Software Developer GNULinux Registered User #379182 GNULinux Registered Machine #277661 GNULinux Arequipa Users Group||Debian Arequipa Users Group -- pgp.rediris.es 0xF8554F6B GPG FP:697E FAB8 8E83 1D60 BBFB 2264 9E3D 5761 F855 4F6B -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian/control best practices
Carlos Eduardo Sotelo Pinto wrote: Hi mentors I have a question, I am packaginf sitebar package wichis on mentorsdebian.net, and have gotten a suggestion, but it got confused me in one way, debian developeres reference talks about debian control best practices and I understand that ( and one more person say me the same ) that synposys must be on lower cases http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis package-name is a synopsis. but all the packages that I have seen was on this way Package-name is a synopsis. The first leeter is on uppercase what is the right? IANADD Developers Reference and lowercase. -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: dbconfig-common
2008/9/17 Michal Čihař [EMAIL PROTECTED]: Hi Dne Wed, 17 Sep 2008 07:29:35 -0500 Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] napsal(a): I have a question, I am building the sitebar package wichis on mentorsdebian.net, and this package has whishlist item bug #382166 who is relationed with this lintian report http://lintian.debian.org/maintainer/[EMAIL PROTECTED] I had fixed this problem on sitebar building package changing /usr/sbin/mysql to just mysqld but, how about the bug, itsuggest to change to dbconfig-common, then what i must do first, just correct or change the postinst to debconfig-common Have you looked at debconfig-common docs? Yes, I do, because of it I do the question, what must I do about the bug? I must fix it now on this version version? or just fix the problem and fix it on the next revision -- Carlos Eduardo Sotelo Pinto ( KrLoS ) Free and OpenSource Software Developer GNULinux Registered User #379182 GNULinux Registered Machine #277661 GNULinux Arequipa Users Group||Debian Arequipa Users Group -- pgp.rediris.es 0xF8554F6B GPG FP:697E FAB8 8E83 1D60 BBFB 2264 9E3D 5761 F855 4F6B
Re: debian/control best practices
Hi, On Wed, Sep 17, 2008 at 07:21:03AM -0500, Carlos Eduardo Sotelo Pinto wrote: http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis package-name is a synopsis. but all the packages that I have seen was on this way Package-name is a synopsis. two questions: 1) Where did you see this? 2) Why do you think its of interest how Package is written out? You must understand that this sentence is only a help for you how the part _after_ packagename should be. Basically it means that your synopsis must not include Package-name is a, but if your synopsis would be combined with this sentence it should still make sense. Regards, Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dbconfig-common
Dne Wed, 17 Sep 2008 07:44:35 -0500 Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] napsal(a): 2008/9/17 Michal Čihař [EMAIL PROTECTED]: Hi Dne Wed, 17 Sep 2008 07:29:35 -0500 Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] napsal(a): I have a question, I am building the sitebar package wichis on mentorsdebian.net, and this package has whishlist item bug #382166 who is relationed with this lintian report http://lintian.debian.org/maintainer/[EMAIL PROTECTED] I had fixed this problem on sitebar building package changing /usr/sbin/mysql to just mysqld but, how about the bug, itsuggest to change to dbconfig-common, then what i must do first, just correct or change the postinst to debconfig-common Have you looked at debconfig-common docs? Yes, I do, because of it I do the question, what must I do about the bug? I must fix it now on this version version? or just fix the problem and fix it on the next revision Just change scripts to use dbconfig-common instead of your home made database configuration and make a new revision. Or do I miss something? -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: dbconfig-common
Hi, On Wed, Sep 17, 2008 at 07:29:35AM -0500, Carlos Eduardo Sotelo Pinto wrote: I had fixed this problem on sitebar building package changing /usr/sbin/mysql to just mysqld but, how about the bug, itsuggest to change to dbconfig-common, then what i must do first, just correct or change the postinst to debconfig-common dbconfig-common is documented fairly well. See [1] or better (because most likely at the newested version): Install the dbconfig-common package and have a look into /usr/share/doc/dbconfig-common. It also includes some example packages for the most cases. Best Regards, Patrick [1] http://people.debian.org/~seanius/policy/examples/dbconfig-common/doc/dbconfig-common-using.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dbconfig-common
2008/9/17 Michal Čihař [EMAIL PROTECTED]: Dne Wed, 17 Sep 2008 07:44:35 -0500 Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] napsal(a): 2008/9/17 Michal Čihař [EMAIL PROTECTED]: Hi Dne Wed, 17 Sep 2008 07:29:35 -0500 Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] napsal(a): I have a question, I am building the sitebar package wichis on mentorsdebian.net, and this package has whishlist item bug #382166 who is relationed with this lintian report http://lintian.debian.org/maintainer/[EMAIL PROTECTED] I had fixed this problem on sitebar building package changing /usr/sbin/mysql to just mysqld but, how about the bug, itsuggest to change to dbconfig-common, then what i must do first, just correct or change the postinst to debconfig-common Have you looked at debconfig-common docs? Yes, I do, because of it I do the question, what must I do about the bug? I must fix it now on this version version? or just fix the problem and fix it on the next revision Just change scripts to use dbconfig-common instead of your home made database configuration and make a new revision. Or do I miss something? that is right, well my problem just was what must i do first, just correct the bug and later change the script or just change the script to makeit with dbconfig-common, no more... and honestly, I did'nt know what mus be the way, you give a solutions thanks -- Carlos Eduardo Sotelo Pinto ( KrLoS ) Free and OpenSource Software Developer GNULinux Registered User #379182 GNULinux Registered Machine #277661 GNULinux Arequipa Users Group||Debian Arequipa Users Group -- pgp.rediris.es 0xF8554F6B GPG FP:697E FAB8 8E83 1D60 BBFB 2264 9E3D 5761 F855 4F6B
Re: dbconfig-common
Patrick Schoenfeld wrote: dbconfig-common is documented fairly well. I do not agree with this statement. There are dark areas in the doc, particularly nowhere, it's telling how to get a root user on MySQL, and some packages might need it. Also, it's author never replied to my emails. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dbconfig-common
On Thu, 2008-09-18 at 01:00 +0800, Thomas Goirand wrote: Patrick Schoenfeld wrote: dbconfig-common is documented fairly well. I do not agree with this statement. There are dark areas in the doc, particularly nowhere, it's telling how to get a root user on MySQL, and some packages might need it. Why would you need a root user? Richard signature.asc Description: This is a digitally signed message part
Re: dbconfig-common
Richard Laager wrote:
On Thu, 2008-09-18 at 01:00 +0800, Thomas Goirand wrote:
Patrick Schoenfeld wrote:
dbconfig-common is documented fairly well.
I do not agree with this statement. There are dark areas in the doc,
particularly nowhere, it's telling how to get a root user on MySQL, and
some packages might need it.
Why would you need a root user?
Richard
Why do you think no app would need it? How about something that does
mysql backups, or manages MySQL accounts? I have made 2 packages that
needs that, one of them being automysqlbackup, and I had to do hackish
stuff like this:
USERNAME=`grep user /etc/mysql/debian.cnf | tail -n 1 | cut -d= -f2 |
awk '{print $1}'`
PASSWORD=`grep password /etc/mysql/debian.cnf | tail -n 1 | cut -d=
-f2 | awk '{print $1}'`
I would have happily avoid it!
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [Bulk] Re: Advice about first package building (from sources)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Lavarde - Debian a écrit : Hi Laurent, Al Nikolov said: Laurent Guignard wrote: I have read the main documentation about pbuilder but i haven't seen if it is possible to build a package from upstream sources. In all examples, the command is like pbuilder build ???.dsc What is the correct method to build a package from upstream sources ? I thought to build a virtual host (KVM), install all packages needed, import all sources (upstream with all files needed to build package) and run the dpkg-buildpackage command... All this to keep a clean and stable Debian on my laptop ;) I fear the answers you got might have been a bit confusing, but it's also because it's not clear what you mean with keeping a clean and stable Debian: only install packaged software (nothing by hand), or really not do anything out of the normal (e.g. compiling and packaging) on your laptop, or both. I'm kind of a both guy, so: - I created an unstable CHROOT jail with debootstrap and do all my packaging in there (as suggested by Neil). For this purpose, KVM, Xen or any VM is as good, but more heavyweight. - I check that my packages build correctly with pbuilder (and pbuilder is really only meant for this). - Neither pbuilder nor debootstrap will help you to learn Debian packaging, hence the advice from Al to read http://www.debian.org/doc/maint-guide/ Hope this helps, Eric PS: I directed my answer back to you because it was not clear if you are subscribed to Mentors. Thanks for all your answers. I'll build a chroot environment with deboostrap with unstable. I'll have to build the new libnet1 package of David Paleino from all files he upload on mentors.debian.net (with Debian unstable dependencies). After, I'll can build my package from source. It seems to be the better solution... My words clean and stable means that I have a Debian stable and i doesn't want to upgrade to testing or unstable, so i need a specific environment to build package. Thanks again. - -- Laurent Guignard, Registered as user #301590 with the Linux Counter Site : http://www.famille-guignard.org Blog : http://blog.famille-guignard.org Projet : http://sicontact.sourceforge.net GULL de Villefranche sur Saône : http://www.cagull.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI0VPyjcKpXFc/7oYRAkPFAKCAE3MEphIxoCdpcLoUKuLoaPe0cQCffwxK zfxWiRukeU+gEKqInRm6U4E= =EOwr -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dbconfig-common
On Thu, 2008-09-18 at 02:40 +0800, Thomas Goirand wrote: Why do you think no app would need it? I never claimed this. How about something that does mysql backups, or manages MySQL accounts? I have made 2 packages that needs that, one of them being automysqlbackup, and I had to do hackish stuff like this: Wouldn't you just use this: mysqldump --defaults-file=/etc/mysql/debian.cnf ...ARGS... When you're talking about system-level access, the idea of per-application database users loses most of its utility. Richard signature.asc Description: This is a digitally signed message part
RFS: swapspace (adopted and updated package)
Dear mentors, I am looking for a sponsor for the new version 1.10-4 of my package swapspace. It builds these binary packages: swapspace - dynamic swap space manager The package is lintian -ivI-clean. The upload would fix these bugs: 499116 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/swapspace - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/swapspace/swapspace_1.10-4.dsc I would be glad if someone uploaded this package for me. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RFS: cfi (adopted package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for the new version 3.0-8 of package cfi. I have adopted this package. It builds these binary packages: cfi-en - Copyright does not exist, book about hacker culture cfi-sv - Copyright finns inte, book about hacker culture The package appears to be lintian clean. The upload would fix these bugs: 488603 The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/c/cfi - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/c/cfi/cfi_3.0-8.dsc I would be glad if someone uploaded this package for me. Kind regards, - -- Krzysztof Burghardt http://www.burghardt.pl/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkjRaYQACgkQXgk7638/b1ss0wCg8Uhu04v9s9rg52Lr8XoQ3oTC tZUAoPCN/TRKoIdejA/IHOEYCDf6siQz =XIQ6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Best practice for package synopsis (was: debian/control best practices)
Carlos Eduardo Sotelo Pinto [EMAIL PROTECTED] writes: I understand that ( and one more person say me the same ) that synposys must be on lower cases http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis More accurately, the synopsis should be written so that it makes sense in the middle of a sentence. package-name is a synopsis. but all the packages that I have seen was on this way Package-name is a synopsis. This is the example sentence. Your package description should only contain the 'synopsis' part as its first line. That section of the Best Packaging Practices chapter is, to my mind, confusingly written, though I agree with its advice. I'm working with others (slowly) on [EMAIL PROTECTED] to form a better wording. -- \“I hate it when my foot falls asleep during the day, because | `\that means it's gonna be up all night.” —Steven Wright | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
