Re: Possibly interested in
On Mon, Apr 11, 2005 at 08:51:17PM -0400, Brett Meadors wrote: Hi, I am possibly interested in finding a sponsor. I would like to help with documentation, or maybe help with PR. I can provide more information if necessary. I haven't written much documentation for Open source projects, but use words well and can provide a simple easy to read/use type documentation. People can only sponsor your for a package you have actually done. Sponsoring means looking into a package you have created, checking it and uploading it to the archive. When you look at a PR and give additional informations you will need no sponsor. Mciahel -- Escape the Java Trap with GNU Classpath! http://www.gnu.org/philosophy/java-trap.html Join the community at http://planet.classpath.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly interested in
Brett Meadors wrote: Hi, Hi Brett I am possibly interested in finding a sponsor. I would like to help with documentation, or maybe help with PR. I can provide more information if necessary. I havent written much documentation for Open source projects, but use words well and can provide a simple easy to read/use type documentation. The best way to start is probably to contact debian-doc@lists.debian.org for documentation and [EMAIL PROTECTED] for PR. Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITP: libqt4lab -- Qt4Lab widget plugins library
Package: wnpp Severity: wishlist Owner: Fathi BOUDRA [EMAIL PROTECTED] hi, I'm looking for a sponsor to my qt4lab package. qt4lab is an already promising project and collaborate with qwt project. You can find my package : http://fboudra.free.fr/debian/ best regards, Fathi * Package name: libqt4lab Version : 0.1.1 Upstream Author : Paolo Sereno [EMAIL PROTECTED] * URL : http://www.qt4lab.org/ * License : LGPL Description : Qt4Lab widget plugin library Qt4Lab is an extension to the Qt application framework from Trolltech. This project will be developed according to the Open Source philosophy and will be distributed under LGPL. Qt4Lab provides plugins and utilities for Rapid Application Prototyping for developing SCADA application. The application field is automotive/aerospace. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7 Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
ITA: log4cpp -- A C++ library for flexible logging
hi, i forgot to say that you can find my package here : http://fboudra.free.fr/debian/ cheers, Fathi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Possibly interested in
Hello Brett, * Brett Meadors [EMAIL PROTECTED] [2005-04-12 07:53]: I am possibly interested in finding a sponsor. I would like to help with documentation, or maybe help with PR. I can provide more information if necessary. I haven't written much documentation for Open source projects, but use words well and can provide a simple easy to read/use type documentation. You only have to search a sponsor if you will upload a package as a non dd. If you want to help with documentation stuff, choose some mailing lists from lists.debian.org Regards Nico -- Nico Golde - [EMAIL PROTECTED] | GPG: 1024D/73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org VIM has two modes - the one in which it beeps and the one in which it doesn't -- encrypted mail preferred pgpCBcTA1Ik5w.pgp Description: PGP signature
Re: RFS: tinywm - Ridiculously tiny window manager
Hi, The package files are available from http://www.hemamu.com/hemamu/debian/ . I've looked at the directory. I can point out that you have only created a Debian native package, You will need an upstream file as ../tinywm_1.3.orig.tar.gz when building. regards, junichi -- Junichi Uekawa, Debian Developer 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4 http://www.netfort.gr.jp/~dancer/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian directory included in upstream
Hi, The author of one of the packages I was packaging for my own use has asked me to be the maintainer of the debian's package. The problem that I found is that in latest versions he includes his own version of debian's directory inside the original tar.gz file as you download it from the web. I've tried to explain to him the reasons behind doing it the proper way, with a diff file, but I don't think I was able to do that too well. Quoting him: The reason I added debian subdirectory is to distribute it with the source files. Any suggestions on how to deal with that? Greetings, Miry __ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
It then becomes a native debian package with no -# revisions. C.S. On Tue, 12 Apr 2005, Miriam Ruiz wrote: Hi, The author of one of the packages I was packaging for my own use has asked me to be the maintainer of the debian's package. The problem that I found is that in latest versions he includes his own version of debian's directory inside the original tar.gz file as you download it from the web. I've tried to explain to him the reasons behind doing it the proper way, with a diff file, but I don't think I was able to do that too well. Quoting him: The reason I added debian subdirectory is to distribute it with the source files. Any suggestions on how to deal with that? Greetings, Miry __ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es -- Carlo U. Segre -- Professor of Physics Associate Dean for Special Projects, Graduate College Illinois Institute of Technology Voice: 312.567.3498Fax: 312.567.3494 [EMAIL PROTECTED]http://www.iit.edu/~segre
Re: debian directory included in upstream
also sprach Miriam Ruiz [EMAIL PROTECTED] [2005.04.12.2044 +0200]: I've tried to explain to him the reasons behind doing it the proper way, with a diff file, but I don't think I was able to do that too well. Quoting him: The reason I added debian subdirectory is to distribute it with the source files. Any suggestions on how to deal with that? Tell him that the ./debian directory has no value when the software is available from the Debian archive and that you need to make modifications to it frequently. Tell him to remove it from the upstream tarball, which is how it's done almost everywhere. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! glaube heißt nicht wissen wollen, was wahr ist. - friedrich nietzsche signature.asc Description: Digital signature
Re: debian directory included in upstream
also sprach Carlo Segre [EMAIL PROTECTED] [2005.04.12.2047 +0200]: It then becomes a native debian package with no -# revisions. No, it does not necessarily. You can have an empty .diff.gz file, which would make sense in this case. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! eine schlechte sache erregt, eine gute verträgt viel kritik. -- charles tschopp signature.asc Description: Digital signature
Re: debian directory included in upstream
On Tue, 2005-04-12 at 20:44 +0200, Miriam Ruiz wrote: Hi, The author of one of the packages I was packaging for my own use has asked me to be the maintainer of the debian's package. The problem that I found is that in latest versions he includes his own version of debian's directory inside the original tar.gz file as you download it from the web. I've tried to explain to him the reasons behind doing it the proper way, with a diff file, but I don't think I was able to do that too well. Quoting him: The reason I added debian subdirectory is to distribute it with the source files. Any suggestions on how to deal with that? You could explain that distributing the debian dir in this way is problematic because the debian files in the release will never be up-to-date with respect to the release as you change things and increment the debian revision. And the author isn't going to make a new release for each debian revision. In addition it makes your job harder because you are patching against an out of date debian dir in the release. And it causes confusion for others trying to build a deb who end up using out of date files in the release (I have experienced this). For one program I package upstream was anxious to have the debian dir in CVS, but I was able to convince them to exclude it from the releases for these reasons. Steve Greetings, Miry __ Renovamos el Correo Yahoo!: 250 MB GRATIS! Nuevos servicios, ms seguridad http://correo.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
Hi! On Tuesday 12 April 2005 20:44, Miriam Ruiz wrote: The reason I added debian subdirectory is to distribute it with the source files. Any suggestions on how to deal with that? For sam2p I created my own orig.tar.gz with the debian subdirectory renamed to debian.dist. I don't delete it because the upstream changelog is in there (installed with dh_installchangelogs debian.dist/changelog). Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
On Tuesday 12 April 2005 21.16, martin f krafft wrote: also sprach Miriam Ruiz [EMAIL PROTECTED] [2005.04.12.2044 +0200]: I've tried to explain to him the reasons behind doing it the proper way, with a diff file, but I don't think I was able to do that too well. Quoting him: The reason I added debian subdirectory is to distribute it with the source files. Any suggestions on how to deal with that? Tell him that the ./debian directory has no value when the software is available from the Debian archive and that you need to make modifications to it frequently. Tell him to remove it from the upstream tarball, which is how it's done almost everywhere. I think having the debian/ directory in the upstream source makes sense if the packager works closely with the upstream author (or is the same), ideally the package maintainer should have write access to upstream's scm tool. It is only problematic when upstream ships an outdated debian/ directory. -- I got more room in iptables then they got ip allocations :) -- Some Bastard, news.admin.net-abuse.email, 2004-02-13 pgpFFooc42sse.pgp Description: PGP signature
Re: debian directory included in upstream
also sprach Stefan Fritsch [EMAIL PROTECTED] [2005.04.12.2109 +0200]: For sam2p I created my own orig.tar.gz with the debian subdirectory renamed to debian.dist. Then it's not .orig anymore. The MD5 sum will differ. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! i always choose my friends for their good looks and my enemies for their good intellects. man cannot be too careful in his choice of enemies. -- oscar wilde signature.asc Description: Digital signature
Re: debian directory included in upstream
also sprach Adrian von Bidder [EMAIL PROTECTED] [2005.04.12.2135 +0200]: I think having the debian/ directory in the upstream source makes sense if the packager works closely with the upstream author (or is the same), ideally the package maintainer should have write access to upstream's scm tool. It is only problematic when upstream ships an outdated debian/ directory. Sure, but there is no point in having ./debian available upstream. It's backwards. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! the mind of the thoroughly well-informed man is a dreadful thing. it is like a bric-à-brac shop, all monsters and dust, with everything priced above its proper value. -- oscar wilde signature.asc Description: Digital signature
Re: debian directory included in upstream
On Apr 12, 2005 4:44 PM, martin f krafft [EMAIL PROTECTED] wrote: Sure, but there is no point in having ./debian available upstream. It's backwards. It makes sense for software developers to have their own ./debian directory so that they can use debian/rules binary to compile and test their software while developing it. What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. -- Besos, Marga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
also sprach Margarita Manterola [EMAIL PROTECTED] [2005.04.12. +0200]: It makes sense for software developers to have their own ./debian directory so that they can use debian/rules binary to compile and test their software while developing it. Huh? Why not just use ./Makefile? What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! military intelligence is a contradiction in terms. -- groucho marx signature.asc Description: Digital signature
Re: debian directory included in upstream
On Tue, 2005-04-12 at 22:40 +0200, martin f krafft wrote: also sprach Margarita Manterola [EMAIL PROTECTED] [2005.04.12. +0200]: It makes sense for software developers to have their own ./debian directory so that they can use debian/rules binary to compile and test their software while developing it. Huh? Why not just use ./Makefile? What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. In my case some upstream developers were debian users who liked to be able to build debs from CVS. This has been helpful since they can make sure the app will work ok in debian before they release. It's not strictly necessary, but I'm glad they're thinking of Debian and don't want to discourage them. Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
also sprach Steve Halasz [EMAIL PROTECTED] [2005.04.12.2249 +0200]: In my case some upstream developers were debian users who liked to be able to build debs from CVS. This has been helpful since they can make sure the app will work ok in debian before they release. It's not strictly necessary, but I'm glad they're thinking of Debian and don't want to discourage them. Well, then they should be using branches. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! hi! i'm a .signature virus! copy me into your ~/.signature to help me spread! signature.asc Description: Digital signature
Re: debian directory included in upstream
martin f krafft wrote: What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. What about the case in which the upstream maintainer is the Debian maintainer? I create packages for a piece of sofware I've written (and for which I'm looking a sponsor, see http://lists.debian.org/debian-mentors/2005/04/msg00106.html ). The debian/ directory is in CVS, naturally. It is currently distributed in the .tar.gz file. Should it be removed? This would make things more difficult for me, because in the case of a new version, I would need to untar the new .tar.gz file and then copy the debian/ directory from CVS. -- Are there those in the land of the brave Who can tell me how I should behave When I am disgraced Because I erased A file I intended to save? Eduardo M KALINOWSKI [EMAIL PROTECTED] http://move.to/hpkb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
I demand that martin f krafft may or may not have written... also sprach Margarita Manterola [EMAIL PROTECTED] [2005.04.12. +0200]: It makes sense for software developers to have their own ./debian directory so that they can use debian/rules binary to compile and test their software while developing it. Huh? Why not just use ./Makefile? I use both in gxine: debian/rules to get a known good version of the package built and installed, then Makefile (with modified source) to build a modified executable which can use the installed files. What does not make a lot of sense is to release the .tar.gz with the ./debian directory, as Steve Halasz said, it's perfectly valid to have it in CVS the important point would be to convince them not to include it in the release. I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. That's a matter for the Debian maintainer and upstream. All that I can say is that I've marked bugs as fixed in the Debian changelog without there being any complaint... -- | Darren Salt | nr. Ashington, | linux (or ds) at | sarge,| Northumberland | youmustbejoking | RISC OS | Toon Army | demon co uk | Retrocomputing: a PC card in a Risc PC Always the dullness of the fool is the whetstone of the wits. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
On Tue, Apr 12, 2005 at 06:27:52PM -0300, Eduardo M KALINOWSKI wrote: I disagree. ./debian is the domain of the Debian maintainer, not of the upstream. Unless you are developing software *for* *Debian* (native), there is no reason why you should bother with ./debian at all. What about the case in which the upstream maintainer is the Debian maintainer? I create packages for a piece of sofware I've written (and for which I'm looking a sponsor, see http://lists.debian.org/debian-mentors/2005/04/msg00106.html ). The debian/ directory is in CVS, naturally. It is currently distributed in the .tar.gz file. Should it be removed? This would make things more difficult for me, because in the case of a new version, I would need to untar the new .tar.gz file and then copy the debian/ directory from CVS. Well that's the way it is. Consider someone will fill bugreport stating that you have a typo in your package description. Having native package you will have to upload whole new source.tar.gz. Having Debian packaging infrastructure in diff.gz you will have to reupload only this part. Developing software != making Debian packages. At least in general. SuSE, Fedora, Mandrake, Slackware, put anything here won't use your debian/* stuff so why do you want to include it in your releases? For Debian users? They'll use Debian OFFICIAL package. If you don't have official package then... that's not a case here. regards fEnIo -- ,''`. Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo : :' : 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Poland `. `' phone:+48602383548 | proud Debian maintainer and user `- http://skawina.eu.org | jid:[EMAIL PROTECTED] | rlu:172001 signature.asc Description: Digital signature
The debian directory in upstream sources.
Hi all, It seems a hard problem to understand what a native and a non-native debian package is. And get through the trouble if upstream provide a debian directory in the source. I'll try to explain: 1. Non-Native Debian Package A non-native debian source package contains a dsc, diff.gz and a orig.tar.gz file. The version for a non-native debian package looks like UpstreamVersion-DebianVersion for example: 2.8-1 In the dsc file contains fields containing information about the debian package it also contains information about the md5sums of the files. In the diff.gz: These are the modifications you made to the package. It contains the debian directory and the modifications you made to the source tree, if you make use of some patch system like dpatch you have only the debian directory in it. In the orig.tar.gz: This is the upstream tarball. Never ever make changes to this tarball, they should go into the diff.gz. 2. Native Debian Package: The Version number for a debian native package is only the version, it doesn't have a debian revision number or something, it looks like: 2.8 A native package contains only a dsc and a orig.tar.gz file. Native debian packages are often accidentally built when upstream tarball (.orig.tar.gz) is named incorrectly. 3. When using a native and when using a non-native debian package But when using a native package and when a non-native package: If upstream is not actively involved to debian development then it's non-native debian package. A few examples of normal packages are: libc6, apache, phpmyadmin. But linda, lintian, dpkg and some other tools are purely developed for debian. 4. Now the big problem: It seems that upstream has an debian directory. With upstream i mean the people who write the source code and maintain it. Most of the time these packages are faulty, they have lintian/linda errors and such. It is hard to modify the debian directory. (Specially for New Maintainers) What to do in this situation: Ask upstream that they remove or rename the directory to something else. Or ask them to remove the debian directory from the released source (so that the orig.tar.gz doesn't contain the debian directory). Last option: you can ask for repository access. So that you can work on a real debian package. I hope this will explain a little bit about native and non native debian packages. Regards, Matthijs Mohlmann signature.asc Description: This is a digitally signed message part
Re: debian directory included in upstream
also sprach Eduardo M KALINOWSKI [EMAIL PROTECTED] [2005.04.12.2327 +0200]: http://lists.debian.org/debian-mentors/2005/04/msg00106.html ). The debian/ directory is in CVS, naturally. Use a branch! It is currently distributed in the .tar.gz file. Should it be removed? Yes, in my opinion. Keep it in a separate branch. This would make things more difficult for me, because in the case of a new version, I would need to untar the new .tar.gz file and then copy the debian/ directory from CVS. An alternative is to keep it in the tarball and create an empty .diff.gz. This may be okay if maintainer == author. However, if the author is upstream, it makes no sense. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! arthur slapped his arms about himself to try and get his circulation a little more enthusiastic about its job. -- hitchhiker's guide to the galaxy signature.asc Description: Digital signature
Re: The debian directory in upstream sources.
also sprach Matthijs Mohlmann [EMAIL PROTECTED] [2005.04.12.2351 +0200]: A native package contains only a dsc and a orig.tar.gz file. Actually, it's not called .orig.tar.gz, just .tar.gz -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! oxymoron: micro$oft works signature.asc Description: Digital signature
Sources with missing dependencies
Hello, for some hours I have tried to compile a SARGE source under SARGE with: 8 SARGE base-install apt-get install build-essential fakeroot apt-get build-dep package apt-get source package cd package $EDIT debian/changelog dpkg-buildpackage ... 8 and now it stops, because missing build dependencies. Now two quesions: 1) What should I do in such situation? Write a BUG report against the package ? 2) How does buildd handel such situation? I have clients which must run STABLE for security reason but need sometimes backports from selected software. If a new version apear, my 'tdautobuilder' download automaticly the sources and build it for STABLE... No need to do it manualy... Now it had stoped!!! Note: I have never had such problem with my own packages because I have all build-depencies declared. Good night, we hear us in 6-8 hours... It was a long day. Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: debian directory included in upstream
Stefan == Stefan Fritsch [EMAIL PROTECTED] writes: [...] Stefan For sam2p I created my own orig.tar.gz with the debian Stefan subdirectory renamed to debian.dist. I don't delete it because Stefan the upstream changelog is in there (installed with Stefan dh_installchangelogs debian.dist/changelog). Tell your upstream to move his changelog. There isn't any reason for it to be there. The debian directory is for things specific to the Debian package. -- Hubert Chan [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
martin == martin f krafft [EMAIL PROTECTED] writes: [...] martin Tell him that the ./debian directory has no value when the martin software is available from the Debian archive and that you need martin to make modifications to it frequently. ... It may be of value to users of stable who want to make their own package of the latest version of the software for some reason. -- Hubert Chan [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: debian directory included in upstream
Miriam == Miriam Ruiz [EMAIL PROTECTED] writes: Miriam Hi, The author of one of the packages I was packaging for my own Miriam use has asked me to be the maintainer of the debian's Miriam package. The problem that I found is that in latest versions he Miriam includes his own version of debian's directory inside the Miriam original tar.gz file as you download it from the web. I have an upstream who did that -- he took my debian directory, and stuck it in his source tree, and he syncs once in a while. I just maintain as I normally do, and the diff file includes a diff of my debian directory against upstream's. The success of such an approach will depend on how much your upstream's debian directory differs from your own. In my own case, since my upstream uses my debian directory, it isn't very problematic; the diff usually just adds a few lines to the changelog, so it's a pretty clean diff. If your upstream absolutely insists on including a debian directory, you can ask that he uses your debian directory instead of using his own. Since he has asked you to be the Debian maintainer, I assume that shouldn't be much of a problem. Miriam Quoting him: The reason I added debian subdirectory is to Miriam distribute it with the source files. You can then ask him why he needs/wants to distribute it with the source files. -- Hubert Chan [EMAIL PROTECTED] - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
You might transform to the most advantageous human for your woman !!!
Each remedy at 1.81 USD per draught !! http://Orestes.brillianthealth.info/?determinedxtvuyFrancizezsvnineteens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
