Re: RFS (take 2): libbash
On Wed, May 13, 2009 at 12:32 AM, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: In cfb54190905121411u71ae6971r499e87a0895b8...@mail.gmail.com, Hai Zaar wrote: I need separate 1777 directory for locks library of libbash, since it may create rather complex file structure there, so I do not want to put it to just /tmp or /var/tmp/, since it may lead to collisions with files created manually by users It took me a while, but I've fixed this issue. Now temporary files are stored under /tmp/.dirlocks-$USER. I've uploaded fixed version to mentors.debian.net. Patrick, can you look at it please? That's a *desire*, not a *need*. Follow the lead set by GPG, KDE, ORBit, PulsaAudio, SCIM, and SSH.[1] Put files in /tmp and if you need a complex directory structure, create a per- user (or instance) directory in /tmp and place your files inside. mkdtemp is your friend here, although it is not completely portable. mktemp+mkdir are portable, but make sure your code does not have a race condition. So far you haven't provided any evidence that /tmp or /var/tmp are inappropriate for your program. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/ [1] Taken together, it is a good crowd to be in. -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Tue, May 12, 2009 at 8:01 PM, Patrick Matthäi pmatth...@debian.org wrote: Hmm there are some new lintian warnings in http://mentors.debian.net/debian/pool/main/l/libbash/libbash_0.9.10c-1.dsc I: libbash source: debian-watch-file-is-missing Oops... fixed I: libbash source: build-depends-without-arch-dep doxygen Fixed - doxygen moved to Build-Depends-Indep. Uploaded. E: libbash: dir-or-file-in-var-lock var/lock/dirlocks/ Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
Hai Zaar schrieb: On Tue, May 12, 2009 at 8:01 PM, Patrick Matthäi pmatth...@debian.org wrote: Hmm there are some new lintian warnings in http://mentors.debian.net/debian/pool/main/l/libbash/libbash_0.9.10c-1.dsc I: libbash source: debian-watch-file-is-missing Oops... fixed I: libbash source: build-depends-without-arch-dep doxygen Fixed - doxygen moved to Build-Depends-Indep. Uploaded. E: libbash: dir-or-file-in-var-lock var/lock/dirlocks/ Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) Wouldn't it make sense to write those lockfiles to ~/ instead of a systemwide dir? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Tue, May 12, 2009 at 10:55 PM, Patrick Matthäi pmatth...@debian.org wrote: Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) Wouldn't it make sense to write those lockfiles to ~/ instead of a systemwide dir? Some tools that use libbash (my custom app for example), run scripts as system users that do not have valid ~/ -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
Hai Zaar schrieb: On Tue, May 12, 2009 at 10:55 PM, Patrick Matthäi pmatth...@debian.org wrote: Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) Wouldn't it make sense to write those lockfiles to ~/ instead of a systemwide dir? Some tools that use libbash (my custom app for example), run scripts as system users that do not have valid ~/ A valid point maybe also /tmp, your /var/lock/dirlocks has currently the same functions (meant as permissions) as /tmp. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Tue, May 12, 2009 at 11:00 PM, Patrick Matthäi pmatth...@debian.org wrote: Hai Zaar schrieb: On Tue, May 12, 2009 at 10:55 PM, Patrick Matthäi pmatth...@debian.org wrote: Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) Wouldn't it make sense to write those lockfiles to ~/ instead of a systemwide dir? Some tools that use libbash (my custom app for example), run scripts as system users that do not have valid ~/ A valid point maybe also /tmp, your /var/lock/dirlocks has currently the same functions (meant as permissions) as /tmp. Sure. But still I need to create /tmp/dirlocks (or better /var/tmp/dirlocks) on boot. How do I do it? -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
In cfb54190905121302h695d3eb6t61f08bb9294fe...@mail.gmail.com, Hai Zaar wrote: On Tue, May 12, 2009 at 11:00 PM, Patrick Matthäi pmatth...@debian.org wrote: Hai Zaar schrieb: On Tue, May 12, 2009 at 10:55 PM, Patrick Matthäi pmatth...@debian.org wrote: Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) Wouldn't it make sense to write those lockfiles to ~/ instead of a systemwide dir? Some tools that use libbash (my custom app for example), run scripts as system users that do not have valid ~/ A valid point maybe also /tmp, your /var/lock/dirlocks has currently the same functions (meant as permissions) as /tmp. Sure. But still I need to create /tmp/dirlocks on boot. How do I do it? I believe Patrick meant to put the files in /tmp, not in /tmp/dirlocks. If you need the locks to last across reboots, /var/tmp, not /var/tmp/dirlocks. Both /tmp and /var/tmp have the 1777 permissions you want and are present on any Debian system. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: RFS (take 2): libbash
On Tue, May 12, 2009 at 11:15 PM, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: In cfb54190905121302h695d3eb6t61f08bb9294fe...@mail.gmail.com, Hai Zaar wrote: On Tue, May 12, 2009 at 11:00 PM, Patrick Matthäi pmatth...@debian.org wrote: Hai Zaar schrieb: On Tue, May 12, 2009 at 10:55 PM, Patrick Matthäi pmatth...@debian.org wrote: Well... does it mean I'll have to create /var/log/dirlocks during boot process? If yes, is there any service in Debian that can create requested files/dirs on boot? (Please do not tell me that I need to write init script to do it :) Wouldn't it make sense to write those lockfiles to ~/ instead of a systemwide dir? Some tools that use libbash (my custom app for example), run scripts as system users that do not have valid ~/ A valid point maybe also /tmp, your /var/lock/dirlocks has currently the same functions (meant as permissions) as /tmp. Sure. But still I need to create /tmp/dirlocks on boot. How do I do it? I believe Patrick meant to put the files in /tmp, not in /tmp/dirlocks. If you need the locks to last across reboots, /var/tmp, not /var/tmp/dirlocks. I need separate 1777 directory for locks library of libbash, since it may create rather complex file structure there, so I do not want to put it to just /tmp or /var/tmp/, since it may lead to collisions with files created manually by users (yes, I understand that users can occasionally, or on purpose to create files in /var/tmp/dirlocks as well, but that is another story). -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
In cfb54190905121411u71ae6971r499e87a0895b8...@mail.gmail.com, Hai Zaar wrote: I need separate 1777 directory for locks library of libbash, since it may create rather complex file structure there, so I do not want to put it to just /tmp or /var/tmp/, since it may lead to collisions with files created manually by users That's a *desire*, not a *need*. Follow the lead set by GPG, KDE, ORBit, PulsaAudio, SCIM, and SSH.[1] Put files in /tmp and if you need a complex directory structure, create a per- user (or instance) directory in /tmp and place your files inside. mkdtemp is your friend here, although it is not completely portable. mktemp+mkdir are portable, but make sure your code does not have a race condition. So far you haven't provided any evidence that /tmp or /var/tmp are inappropriate for your program. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ [1] Taken together, it is a good crowd to be in. signature.asc Description: This is a digitally signed message part.
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: On Mon, May 11, 2009 at 1:26 AM, Patrick Matthäi pmatth...@debian.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Will you accept it if I rewrite it according to DEP-5? I would welcome this step :) All done. Reuploaded. Please do not upload yet - just tell me if its OK. I want to build against officially released tarball. Could you just put the gpl-3 license header to the Files: * part please. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoIVEQACgkQ2XA5inpabMf6cQCglxgl8fBRE7qTZzcoBS1cua4F TOQAn2lvaIVqN5wOpJ2ivh25Qhtf7Vme =+Bbb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Mon, May 11, 2009 at 7:37 PM, Patrick Matthäi pmatth...@debian.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: On Mon, May 11, 2009 at 1:26 AM, Patrick Matthäi pmatth...@debian.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Will you accept it if I rewrite it according to DEP-5? I would welcome this step :) All done. Reuploaded. Please do not upload yet - just tell me if its OK. I want to build against officially released tarball. Could you just put the gpl-3 license header to the Files: * part please. What for? - I cite it later under separate License: field. It looks like this example from DEP, isn't it?: Example 2 (recurrent license). Files: src/js/editline/* Copyright: 1993, John Doe 1993, Joe Average License: MPL-1.1 Files: src/js/fdlibm/* Copyright: 1993, J-Random Corporation License: MPL-1.1 License: MPL-1.1 [LICENSE TEXT] -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Could you just put the gpl-3 license header to the Files: * part please. What for? - I cite it later under separate License: field. It looks like this example from DEP, isn't it?: Example 2 (recurrent license). Files: src/js/editline/* Copyright: 1993, John Doe 1993, Joe Average License: MPL-1.1 Files: src/js/fdlibm/* Copyright: 1993, J-Random Corporation License: MPL-1.1 License: MPL-1.1 [LICENSE TEXT] You are right, sorry. It is okay for me at whole. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoIYxYACgkQ2XA5inpabMdd8QCeNN7ViXl3zwfa3+livjwY5ThZ 7K8An1RuxVmN/5xNsNFK4xrmidzd+GAL =y0z2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Mon, May 11, 2009 at 8:40 PM, Patrick Matthäi pmatth...@debian.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Could you just put the gpl-3 license header to the Files: * part please. What for? - I cite it later under separate License: field. It looks like this example from DEP, isn't it?: Example 2 (recurrent license). Files: src/js/editline/* Copyright: 1993, John Doe 1993, Joe Average License: MPL-1.1 Files: src/js/fdlibm/* Copyright: 1993, J-Random Corporation License: MPL-1.1 License: MPL-1.1 [LICENSE TEXT] You are right, sorry. It is okay for me at whole. Great! I've rolled out new SF release and rebuilt debs (reuploaded to mentors). Looking forward for your upload. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoIYxYACgkQ2XA5inpabMdd8QCeNN7ViXl3zwfa3+livjwY5ThZ 7K8An1RuxVmN/5xNsNFK4xrmidzd+GAL =y0z2 -END PGP SIGNATURE- -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hai Zaar schrieb:
It builds these binary packages:
libbash- a tool that enables bash dynamic-like shared libraries
libbash-doc - user and developer documentation for libbash
The package appears to be lintian clean.
The upload would fix these bugs: 526739
The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/l/libbash
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget
http://mentors.debian.net/debian/pool/main/l/libbash/libbash_0.9.10b.dsc
I would be glad if someone uploaded this package for me.
Hello,
* debian/control:
- - Out of date standards-version
* debian/changelog:
- - It is wrong, that the package has been made native
* debian/control:
- - Missing ${misc:Depends}
- - Why does libbash-doc depend on libbash?
- - For what do you need in an arch all only package autotools-dev as
build-depend?
* debian/rules:
- - Ehm, why do you need 1777 for var/lock/dirlock/?
* debian/libbash-doc.doc-base:
- - = Author: insert document author here
* debian/copyright:
- - There is also a GPLv2 file in your source, add this license.
- - There is a missing copyright holder on lib/urlcoding.sh
Lintian:
W: libbash source: debhelper-but-no-misc-depends libbash
W: libbash source: debhelper-but-no-misc-depends libbash-doc
W: libbash source: out-of-date-standards-version 3.8.0 (current is 3.8.1)
I: libbash source: build-depends-without-arch-dep autotools-dev
I: libbash source: build-depends-without-arch-dep doxygen
E: libbash: dir-or-file-in-var-lock var/lock/dirlocks/
W: libbash: non-standard-dir-perm var/lock/dirlocks/ 1777 != 0755
- --
/*
Mit freundlichem Gruß / With kind regards,
Patrick Matthäi
GNU/Linux Debian Developer
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
Comment:
Always if we think we are right,
we were maybe wrong.
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoG+j0ACgkQ2XA5inpabMdiggCgit0uM1zdLuJcvcakRu2jTE02
tqEAoJZJzIR+lDlPqGUlyYA+JcsdlDHS
=o/fS
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Sun, May 10, 2009 at 7:01 PM, Patrick Matthäi pmatth...@debian.org wrote:
Hello,
* debian/control:
- - Out of date standards-version
Fixed
* debian/changelog:
- - It is wrong, that the package has been made native
Well, I'm the author of the project, and I want to debian dir to be
part of the project tree (with all of the consequences I know about
it). Does not it make it native?
I've incremented version (to 0.9.10c) to signify that its a new
version (a not packaging of 0.9.10b version that was released quite a
while ago).
* debian/control:
- - Missing ${misc:Depends}
Added.
- - Why does libbash-doc depend on libbash?
It should not. Fixed.
- - For what do you need in an arch all only package autotools-dev as
build-depend?
I do not understand. The policy[1] says that all indicates an
architecture-independent package. Should I make it any instead of
all?
* debian/rules:
- - Ehm, why do you need 1777 for var/lock/dirlock/?
For one of the libbash library, dirlocks, I need to store temporary
lock files. I thought that natural place for these is /var/lock/
Such a dir should be writable by any user, but I want to prevent users
from stepping on other's files. That's why 1777.
* debian/libbash-doc.doc-base:
- - = Author: insert document author here
Fixed
* debian/copyright:
- - There is also a GPLv2 file in your source, add this license.
Fixed. All files are GPLv3 now
- - There is a missing copyright holder on lib/urlcoding.sh
Fixed
Thank you!
The fixed package has been reuploaded to:
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=libbash
[1]
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture
--
Zaar
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: * debian/changelog: - - It is wrong, that the package has been made native Well, I'm the author of the project, and I want to debian dir to be part of the project tree (with all of the consequences I know about it). Does not it make it native? I've incremented version (to 0.9.10c) to signify that its a new version (a not packaging of 0.9.10b version that was released quite a while ago). See: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html -- quote # When to use a native vs a non-native debian package You should only use a native Debian package when it is clear that the package would only ever be of use in Debian. Even if the software is currently only available in Debian, if someone could reasonably use the software on another distribution or on another operating system, then the package should be non-native. A few examples of normal packages are: libc6, apache, phpmyadmin. But linda, lintian, dpkg and some other tools are purely developed for debian, and make no sense being released in another distribution. quote -- - - For what do you need in an arch all only package autotools-dev as build-depend? I do not understand. The policy[1] says that all indicates an architecture-independent package. Should I make it any instead of all? No, but I see no reason why you should build-dep on it. But I personaly did not test it yet without, please do so. The fixed package has been reuploaded to: http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=libbash [1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture I will review it again if (especially the first) both issues are fixed. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoHD1AACgkQ2XA5inpabMd9lQCeOTijDkyXMoO67mZFkFPuMJ+J uxYAn2nROptYaAxREqHeEa/I1XUfgdiV =ROeM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Sun, May 10, 2009 at 8:30 PM, Patrick Matthäi pmatth...@debian.org wrote: See: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html -- quote # When to use a native vs a non-native debian package You should only use a native Debian package when it is clear that the package would only ever be of use in Debian. Even if the software is currently only available in Debian, if someone could reasonably use the software on another distribution or on another operating system, then the package should be non-native. A few examples of normal packages are: libc6, apache, phpmyadmin. But linda, lintian, dpkg and some other tools are purely developed for debian, and make no sense being released in another distribution. quote -- Can you please advice on how to create orig package, when debian dir is part of the project file-tree? Do I need to checkout sources and then just delete debian subdir, pack orig tarball, then restore debian dir and proceed? -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Can you please advice on how to create orig package, when debian dir is part of the project file-tree? Do I need to checkout sources and then just delete debian subdir, pack orig tarball, then restore debian dir and proceed? The best solution would be, to poke upstream until he does not deliver the debian dir within his release tarballs, and while you are the upstream developer.. :) If you do not want to release again today just because of removing the tarball from your source, then do a repack and document this in debian/README.source and take care of it in the next release. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoHFycACgkQ2XA5inpabMfO1gCcCRgt0qa7ReP9o2MDAdBfU6ej aTYAoKx22DDlJg5Ft6eJMcaFa8h3YffB =GOQQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
Hai Zaar wrote: Can you please advice on how to create orig package, when debian dir is part of the project file-tree? Do I need to checkout sources and then just delete debian subdir, pack orig tarball, then restore debian dir and proceed? I don't know how you are creating the tarball, but if you are using automake et al., the debian/ directory will only be part of the tarball if you ask it to be. Just leave it out, and a 'make dist' will create a tarball only with upstream sources. -- You are taking yourself far too seriously. Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Sun, May 10, 2009 at 8:30 PM, Patrick Matthäi pmatth...@debian.org wrote: I will review it again if (especially the first) both issues are fixed. All done: 1. I've decided to go for a new release 0.9.10c. The version package is set to 0.9.10c-1. And I'll do official release (with tarballs, etc.) as soon we'll done polishing Debian part. 2. Yes, since package arch independent, and after reading autotools-dev documentation, I see that its indeed should not be required, so current package builds without it. Thank you, -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Mon, May 11, 2009 at 12:22 AM, Hai Zaar haiz...@haizaar.com wrote: On Sun, May 10, 2009 at 8:30 PM, Patrick Matthäi pmatth...@debian.org wrote: I will review it again if (especially the first) both issues are fixed. All done: 1. I've decided to go for a new release 0.9.10c. The version package is set to 0.9.10c-1. And I'll do official release (with tarballs, etc.) as soon we'll done polishing Debian part. 2. Yes, since package arch independent, and after reading autotools-dev documentation, I see that its indeed should not be required, so current package builds without it. Thank you, -- Zaar P.S. The package were reuploaded. -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: On Sun, May 10, 2009 at 8:30 PM, Patrick Matthäi pmatth...@debian.org wrote: I will review it again if (especially the first) both issues are fixed. All done: 1. I've decided to go for a new release 0.9.10c. The version package is set to 0.9.10c-1. And I'll do official release (with tarballs, etc.) as soon we'll done polishing Debian part. 2. Yes, since package arch independent, and after reading autotools-dev documentation, I see that its indeed should not be required, so current package builds without it. Thank you, Okay nice. But the copyright holder of lib/urlcoding.sh is still missing in debian/copyright: lib/urlcoding.sh:# Copyright (c) 2005 Alon Keren - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoHR+8ACgkQ2XA5inpabMdk8wCdGOJrYQHvePuiA81LxHHHekDV E8AAnA5WlvSdR5etDpMVqoSbfoORiX82 =GkkT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Mon, May 11, 2009 at 12:32 AM, Patrick Matthäi pmatth...@debian.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: On Sun, May 10, 2009 at 8:30 PM, Patrick Matthäi pmatth...@debian.org wrote: I will review it again if (especially the first) both issues are fixed. All done: 1. I've decided to go for a new release 0.9.10c. The version package is set to 0.9.10c-1. And I'll do official release (with tarballs, etc.) as soon we'll done polishing Debian part. 2. Yes, since package arch independent, and after reading autotools-dev documentation, I see that its indeed should not be required, so current package builds without it. Thank you, Okay nice. But the copyright holder of lib/urlcoding.sh is still missing in debian/copyright: lib/urlcoding.sh:# Copyright (c) 2005 Alon Keren Will you accept it if I rewrite it according to DEP-5? -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Will you accept it if I rewrite it according to DEP-5? I would welcome this step :) - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoHVK4ACgkQ2XA5inpabMdRhwCfcRD05J6HjPzunccKpTzRlrJd oicAniBWO6Kr8tZ5BPy0gCfdJQHkt/NC =8lnc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Mon, May 11, 2009 at 1:26 AM, Patrick Matthäi pmatth...@debian.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hai Zaar schrieb: Will you accept it if I rewrite it according to DEP-5? I would welcome this step :) All done. Reuploaded. Please do not upload yet - just tell me if its OK. I want to build against officially released tarball. -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
Hi there.
I just caught this, and I'm talking about the quote without even reading
its current version.
On May 10 2009, Patrick Matthäi wrote:
See: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html
-- quote
# When to use a native vs a non-native debian package
(...)
But linda, lintian, dpkg and some other tools are purely developed for
debian, and make no sense being released in another distribution.
quote --
Those packages are used by distributions like Ubuntu, for instance, and
the wording of that part may leave newer maintainers puzzled.
Oh, linda seems to be deprecated (dead?) in favor of lintian. :-)
I would, BTW, say that even one of the packages that I maintain (which
is usbmount) should be non-native, but I'm keeping it native for
historic purposes...
Regards,
--
Rogério Brito : rbr...@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS (take 2): libbash
On Sun, 2009-05-10 at 20:37 -0300, Rogério Brito wrote: On May 10 2009, Patrick Matthäi wrote: See: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html -- quote # When to use a native vs a non-native debian package (...) But linda, lintian, dpkg and some other tools are purely developed for debian, and make no sense being released in another distribution. quote -- Those packages are used by distributions like Ubuntu, for instance, and the wording of that part may leave newer maintainers puzzled. No more so than using 'dpkg' to install packages. -Rob signature.asc Description: This is a digitally signed message part
Re: RFS (take 2): libbash
In 20090510233757.gb6...@ime.usp.br, Rogério Brito wrote: On May 10 2009, Patrick Matthäi wrote: But linda, lintian, dpkg and some other tools are purely developed for debian, and make no sense being released in another distribution. quote -- Those packages are used by distributions like Ubuntu, for instance, and the wording of that part may leave newer maintainers puzzled. Use in other Debian-based systems is not always reason enough to make something non-native. (Use in a non-Debian-based OS generally is.) -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: RFS (take 2): libbash
2009/5/11 Boyd Stephen Smith Jr. b...@iguanasuicide.net: In 20090510233757.gb6...@ime.usp.br, Rogério Brito wrote: On May 10 2009, Patrick Matthäi wrote: But linda, lintian, dpkg and some other tools are purely developed for debian, and make no sense being released in another distribution. quote -- Those packages are used by distributions like Ubuntu, for instance, and the wording of that part may leave newer maintainers puzzled. Use in other Debian-based systems is not always reason enough to make something non-native. (Use in a non-Debian-based OS generally is.) dpkg and friends version numbers in Ubuntu are released with native ubuntu version numbers. So really anyone who is using dpkg in their distribution is more correctly maintains his/her own native branch which is similar to debian one. I don't think debian wants to become universal upstream for e.g. dpkg and try to please *everyone* (just picture wishlist bugs against dpkg to nativly handle eggs and jars =0) ps. sorry if you get this twice.. -- With best regards Dmitrijs Ledkovs (for short Dima), Ледков Дмитрий Юрьевич -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
