RFS: python-sqlkit
Dear mentors, I'd like to find a sponsor for my package 'python-sqlkit' * Package name: python-sqlkit Version : 0.8.6 Upstream Author : Sandro Dentella (san...@e-den.it) - myself * URL : http://sqlkit.argolinux.org * License : GPL-3+ Programming Lang: python Description : GUI app and package to build database based applications It's a package for pygtk library 'sqlkit'. The package can be downloaded from: - http://sqlkit.argolinux.org/sqlkit/download.html - hg clone http://hg.argolinux.org/py/sqlkit (mercurial) Sqlkit it's a pygtk package that provides GUI widgets to edit databases in table or mask (form) fasion. It lets you edit joins of almost any sqlalchemy selectable, lets you edit related table and much more. Official home is http://sqlkit.argolinux.org The release 0.8.6, the first stable release after 10 month trial period in a production environment will be released in a couple of days. The package appears lintian clean, but some more work may be needed, and I'd be glad to do it after clearifying some issues on the list as for name (it both a python package and a GUI application) and upstream (packaging has the debian folder that seems not to be the suggested solution). Thanks for the attention sandro dentella *:-) -- Sandro Dentella *:-) http://sqlkit.argolinux.orgSQLkit home page - PyGTK/python/sqlalchemy -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libsockets
В Fri, 28 Aug 2009 17:36:11 -0400, Leinier Cruz Salfran написа: libsockets (2.3.6-2) unstable; urgency=low * Added debugging symbols package lintian's authors do not recommend running it with root privileges! Indeed, so why do you do that? ;-) I: libsockets2: no-symbols-control-file usr/lib/libsockets.so.2.3.6 This is not about debugging symbols at all -- read the lintian tag description and the documentation it points to. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: dma (updated, bugs fixed)
Dear mentors, I am looking for a sponsor for the new version 0.0.2009.07.17-2 of my package dma. It updates the packaging a bit and fixes two bugs from the Debian BTS - allows the spool directory to live on a filesystem like XFS that does not set the d_type field in the dirent structure, and generates better, longer, more random, more reliable Message-Id fields on new messages if the MUA has not done so. It builds a single binary package: dma- lightweight mail transport agent The package has been tested with lintian and pbuilder. The upload would fix these bugs: 544357 (spool on XFS), 544475 (better Message-Id) The package can be found on mentors.debian.net: http://mentors.debian.net/debian/pool/main/d/dma/dma_0.0.2009.07.17-2.dsc I would be glad if someone uploaded this package for me. JFYI, here's the changelog entry: dma (0.0.2009.07.17-2) unstable; urgency=low * Allow the spool directory to live on a filesystem that does not set the d_type member of the dirent structure, like XFS. Closes: #544357 * Randomize the Message-Id a bit more. Closes: #544475 * Bump Standards-Version to 3.8.3 with no changes. * Only enable the build hardening wrapper if the hardening build option is specified. * Switch the copyright file header from the Wiki to DEP 5. * Remove the manual page .Dx patch - the groff version in Squeeze knows about the .Dx mdoc macro. Add a lintian override for the Unknown DragonFly version error. * Convert the patch file headers to the DEP 3 format. -- Peter Pentchev r...@ringlet.net Tue, 01 Sep 2009 13:36:33 +0300 G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 If I were you, who would be reading this sentence? pgppBHmgWU1T3.pgp Description: PGP signature
Re: RFS: dma (updated, bugs fixed)
Quoting Peter Pentchev r...@ringlet.net: Dear mentors, Excellent reaction. No comments. Uploaded. Thanks! I am looking for a sponsor for the new version 0.0.2009.07.17-2 of my package dma. It updates the packaging a bit and fixes two bugs from the Debian BTS - allows the spool directory to live on a filesystem like XFS that does not set the d_type field in the dirent structure, and generates better, longer, more random, more reliable Message-Id fields on new messages if the MUA has not done so. Hm, I was not aware of that XFS `feature' as dictated by POSIX. P.S. Anyways, that appears to be quite a hot package ;-) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: update-inetd (98% popcon; closes ITA and 10 other bugs)
Serafeim Zanikolas schrieb: Hi Patrick, On Mon, Aug 31, 2009 at 08:46:08PM +0200, Patrick Matthäi wrote [edited]: W: update-inetd: manpage-has-errors-from-man usr/share/man/man8/update-inetd.8.gz 200: warning [p 3, 6.0i]: can't break line not much I can do about this, it's just a long line that gives a syntactic example so I'd rather refrain from reformatting it (it'd add confusion) I: update-inetd: hyphen-used-as-minus-sign usr/share/man/man8/update-inetd.8.gz:14 [..] fixed I: update-inetd: unused-debconf-template update-inetd/title I: update-inetd: unused-debconf-template update-inetd/ask-several-entries I: update-inetd: unused-debconf-template update-inetd/ask-entry-present I: update-inetd: unused-debconf-template update-inetd/ask-remove-entries I: update-inetd: unused-debconf-template update-inetd/ask-disable-entries These are false positives (I've added an override): $ lintian-info -t unused-debconf-template ... N: In some cases, the template is used but Lintian is unable to determine N: this. Common causes are: ... N: - the template is not used by the maintainer scripts but is used by a N: program in the package ... N: If any of the above apply, please install an override. BTW I took this opportunity to make the xinetd warning less ugly: --- a/update-inetd +++ b/update-inetd -print STDERR Note: xinetd seems to be installed but update-inetd does not\n; -print STDERR currently support it. For more information see\n; -print STDERR /usr/share/doc/xinetd/README.Debian and itox(8).\n; +print STDERR Note: xinetd currently is not fully supported by update-inetd.\n; +print STDERR Please consult /usr/share/doc/xinetd/README.Debian and itox(8).\n; The .dsc url remains the same. Thanks for your contribution, I have uploaded http://members.hellug.gr/serzan/tmp/deb/update-inetd_4.32.dsc Cheers. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: nautilus-dropbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package nautilus-dropbox. * Package name: nautilus-dropbox Version : 0.4.1 * URL : http://www.getdropbox.com/ * License : GPL for code, artwork is not free Programming Lang: C Description : nautilus plugin for dropbox Dropbox is a service to sync and share files online. This is a plugin for nautilus that makes your dropbox folder available on the Gnome desktop. - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) It builds these binary packages: nautilus-dropbox - Dropbox integration for Nautilus The package appears to be lintian clean. The upload would fix these bugs: 544499 The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/n/nautilus-dropbox - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/n/nautilus-dropbox/nautilus-dropbox_0.6.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards aliceinwire - -- *alice ferrazzi* CEO *Drunk Geisha* http://maps.google.com/maps?q=hl=en *Email:* jingcom...@email.it mailto:jingcom...@email.it *IM:* aliceinwire (AIM) *http://www.linkedin.com/in/aliceinwire* See who we know in common http://www.linkedin.com/e/wwk/44328377/ Want a signature like this? http://www.linkedin.com/e/sig/44328377/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqdEo0ACgkQIjqejaX9O3BHggCgg8qHEa0jFfkP83GGeiV6pDfj ncQAn00Xd26VbiD65IJoXtNMI7azuq3W =I+mc -END PGP SIGNATURE- attachment: aliceinwire.vcf
Re: RFS: nautilus-dropbox
On Tue, Sep 1, 2009 at 5:54 PM, Alice Ferrazzialiceinw...@gnumerica.org wrote:
I am looking for a sponsor for my package nautilus-dropbox.
Hi,
Some comments from first look, haven't check/compiled it yet..
* debian/control:
Section: unknown
Why duplicate URL in extented description? Homepage is there to show it.
Why different priority for source and binary?
* debian/rules:
Remove unneeded dh_ calls
* debian/copyright:
All images included in this package constitute data and are not licensed
for you to use under the terms of the GPL. You may not use the images
included in this package for any reason other than redistributing
this package without first obtaining permission from Evenflow, Inc.
You are explicitly forbidden from using these images in any other
software package.
I am not sure this is Ok with DFSG. Please check before putting it in package.
--
Cheers,
Kartik Mistry | 0xD1028C8D | IRC: kart_
Debian GNU/Linux Developer | Identica: @kartikm
Blogs: {ftbfs, kartikm}.wordpress.com
Our problems are so serious that the best way to talk about them is
lightheartedly. - http://kingsly.net/tmp/fortune.php/1251771290
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: trend (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.1-2 of my package trend. It builds these binary packages: trend - a general-purpose, efficient trend graph The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/trend - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/trend/trend_1.1-2.dsc I would be glad if someone uploaded this package for me. Kind regards Yuri D'Elia -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Issue with dpkg-shlibdepds
In 20090901055635.gc6...@glandium.org, Mike Hommey wrote: On Mon, Aug 31, 2009 at 04:03:06PM -0700, Joe Smith wrote: Another issue sprung up, though. What I need to be able to do now is have libngi3 (0.8) and libngi3 (0.9) installed at the same time. They don't share any binaries that are the same. Why would you want that, actually ? Most of the time, this is not something you'd want. If they are compatible, you don't even need that. If they are not compatible, then the SONAME should be changed, not the package name. However, changing the (binary) package name could possibly allow side-by-side installation of the old ABI and the new ABI. This may be desirable in the short term for any library. For the long-term, multiple source packages will probably be required. -- 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: nautilus-dropbox
In 85c01b290909010539g4db763d2w52c90a1b68bc4...@mail.gmail.com, Kartik Mistry wrote: * debian/copyright: All images included in this package constitute data and are not licensed for you to use under the terms of the GPL. You may not use the images included in this package for any reason other than redistributing this package without first obtaining permission from Evenflow, Inc. You are explicitly forbidden from using these images in any other software package. I am not sure this is Ok with DFSG. Please check before putting it in package. Definitely not. The images are under a (restricted) redistribution-only license. They could be put into non-free, but they certainly can't reside in main. -- 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: Issue with dpkg-shlibdepds
Hi Mike, The scenario is this: We're making a set of interface libraries for use in cross-platform application development. We want to 100% guarantee that if an application is compiled against a particular version of the library, then it's guarateed to work indefinitely with the same level of functionality. As such, we can't upgrade the libraries underneath or we risk regression. Plus this way we can break binary compatibility without issue between versions. The other problem is that applications built against different versions can be installed at the same time, and thus different versions of the actual libraries themselves must also be installed at the same time. For this, I don't see how we can get around it with a single package name. To cope with this, we have different names for the libraries for each version. In linux, it's easy enough to vary the so version for this purpose, but goes against the normal way of doing so I'm trying to come up with the easiest way of getting it to work. The other option is to forget packaging altogether for the libraries and package them with each application instead, but it would be more work for the application developer to deal with that. Clancy On Mon, Aug 31, 2009 at 10:56 PM, Mike Hommey m...@glandium.org wrote: On Mon, Aug 31, 2009 at 04:03:06PM -0700, Joe Smith wrote: Thanks Mike. Sorted that issue out. Didn't realize I'd commented out dh_makeshlibs =) Another issue sprung up, though. What I need to be able to do now is have libngi3 (0.8) and libngi3 (0.9) installed at the same time. They don't share any binaries that are the same. I assume this means that I actually have to make libngi3-0.9 and libngi3-0.8 packages as separate entities? Or is there a way to make a package not replace itself if there's something using it? Why would you want that, actually ? Most of the time, this is not something you'd want. If they are compatible, you don't even need that. If they are not compatible, then the SONAME should be changed, not the package name. Mike
CDBS question
I have several patches for a package called varlkyrie. Some of these patches change configure.in and Makefile.am. I.e. I need to run autoreconf after applying patches. Following CDBS documentation, I've added these lines to debian/rules makebuilddir/valkyrie:: cat m4/* acinclude.m4 autoreconf But the problem is that this got executed _before_ patches get applied. Here is the log: debian/rules build test -x debian/rules cat m4/* acinclude.m4 autoreconf valkyrie/Makefile.am:18: `%'-style pattern rules are a GNU make extension valkyrie/Makefile.am:146: `:='-style assignments are not portable vk_logmerge/Makefile.am:19: `%'-style pattern rules are a GNU make extension vk_logmerge/Makefile.am:45: `:='-style assignments are not portable mkdir -p . /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory `/build/user-valkyrie_1.4.0-1-amd64-cdE7Mo/valkyrie-1.4.0' make[1]: Nothing to be done for `reverse-config'. make[1]: Leaving directory `/build/user-valkyrie_1.4.0-1-amd64-cdE7Mo/valkyrie-1.4.0' if [ debian/stamp-patched = reverse-patches ]; then rm -f debian/stamp-patched; fi patches: debian/patches/valkyrie-1.3.0-docdir-fix-1.patch debian/patches/valkyrie-1.3.0-honour-system-style-1.patch debian/patches/valkyrie-1.3.0-kate-use-1.patch Trying patch debian/patches/valkyrie-1.3.0-docdir-fix-1.patch at level 1 ... success. Trying patch debian/patches/valkyrie-1.3.0-honour-system-style-1.patch at level 1 ... success. Trying patch debian/patches/valkyrie-1.3.0-kate-use-1.patch at level 1 ... 0 ... success. How can I make it to run after patching? Thanks, -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: CDBS question
On Tue, 2009-09-01 at 17:23 +0300, Hai Zaar wrote: I have several patches for a package called varlkyrie. Some of these patches change configure.in and Makefile.am. I.e. I need to run autoreconf after applying patches. Following CDBS documentation, I've added these lines to debian/rules makebuilddir/valkyrie:: cat m4/* acinclude.m4 autoreconf But the problem is that this got executed _before_ patches get applied. Here is the log: [...] How can I make it to run after patching? Try the post-patches target, like this: post-patches:: cat m4/* acinclude.m4 autoreconf Though I would usually defer to an autogen.sh if its supplied in the source (and if it doesn't prompt for stuff like gettextize,) over autoreconf. -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: RFS: nautilus-dropbox
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Boyd Stephen Smith Jr. wrote: In 85c01b290909010539g4db763d2w52c90a1b68bc4...@mail.gmail.com, Kartik Mistry wrote: * debian/copyright: All images included in this package constitute data and are not licensed for you to use under the terms of the GPL. You may not use the images included in this package for any reason other than redistributing this package without first obtaining permission from Evenflow, Inc. You are explicitly forbidden from using these images in any other software package. I am not sure this is Ok with DFSG. Please check before putting it in package. Definitely not. The images are under a (restricted) redistribution-only license. They could be put into non-free, but they certainly can't reside in main. i have update the package and correct some error for the non-free can be also good because is a wnpp requested package - -- *alice ferrazzi* CEO *Drunk Geisha* http://maps.google.com/maps?q=hl=en *Email:* jingcom...@email.it mailto:jingcom...@email.it *IM:* aliceinwire (AIM) *http://www.linkedin.com/in/aliceinwire* See who we know in common http://www.linkedin.com/e/wwk/44328377/ Want a signature like this? http://www.linkedin.com/e/sig/44328377/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqdOAMACgkQIjqejaX9O3AuwQCdELar6lMtudgZ4z0pnnxOHPRL fzYAnR3TnASDHHsAhF9E3d43YFdsrlvj =Mgbn -END PGP SIGNATURE- attachment: aliceinwire.vcf
Re: Issue with dpkg-shlibdepds
First of all, TOFU is generally frowned upon as a posting style on technical mailing lists. Second, IANADD and TINASOTODP; I speak only for myself. On Tuesday 01 September 2009 08:55:45 Joe Smith wrote: We're making a set of interface libraries for use in cross-platform application development. We want to 100% guarantee that if an application is compiled against a particular version of the library, then it's guarateed to work indefinitely with the same level of functionality. I think this is an unreasonable goal. That said, even if it is to remain the goal it should be implemented through disciplined library development and a thorough test suite, not through the linker. You *should* use the linker to retain backward compatibility (symbol versioning) and you *should* use other technical means to detect ABI changes before a release. As such, we can't upgrade the libraries underneath or we risk regression. This is misguided. If there is a security issue in the library, it needs to be able to be fixed in one place without recompiling all the programs that use the library. Plus this way we can break binary compatibility without issue between versions. While I guess it makes the library user happy, it will not make the application developers or packagers happy. Also, having so many versions that appear incompatible to the linker when they are actually compatible defeats the purpose of shared libraries; applications are much less likely to share them. This increases both RAM and HD usage needlessly. The increased RAM usage can also cause longer run times indirectly as there are more cache misses. The other problem is that applications built against different versions can be installed at the same time, and thus different versions of the actual libraries themselves must also be installed at the same time. For this, I don't see how we can get around it with a single package name. You might be able to have a single source package, but most likely you will need a different source package for each version. The other option is to forget packaging altogether for the libraries and package them with each application instead, but it would be more work for the application developer to deal with that. It would also be more work for the security team. You might be able to use static linking, but that's generally frowned upon on Debian. Shipping the library along-side the application is also generally frowned upon. -- 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.
RFS: gforth (updated)
Dear mentors, I am looking for a sponsor for the new version 0.7.0+ds1-3 of my package gforth. This is an attempt to fix three different failures to build on mips, armel, and s390 respectively. It builds these binary packages: gforth - GNU Forth Language Environment gforth-common - GNU Forth architecture-independent dictionaries The package has been tested with lintian and pbuilder. The package can be found on mentors.debian.net: http://mentors.debian.net/debian/pool/main/g/gforth/gforth_0.7.0+ds1-3.dsc I would be glad if someone uploaded this package for me. JFYI, here's the changelog entry: gforth (0.7.0+ds1-3) unstable; urgency=low * Explicitly depend on libtool and libltdl-dev; several benefits: - make the build environment-agnostic and not dependent on what just happens to be installed - fix a FTBFS if libtool is installed but libltdl-dev isn't; some of the autobuilders are configured that way * Add a missing semicolon in engine/support.c to try and fix the FTBFS on s390. * Temporarily use libffi instead of libffcall on armel, until libffcall's issues are resolved. -- Peter Pentchev r...@ringlet.net Tue, 01 Sep 2009 17:58:12 +0300 G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence no verb. pgpwMBpXo3Swi.pgp Description: PGP signature
Re: RFS: libsockets
El mar, 01-09-2009 a las 09:30 +, Yavor Doganov escribió: В Fri, 28 Aug 2009 17:36:11 -0400, Leinier Cruz Salfran написа: libsockets (2.3.6-2) unstable; urgency=low * Added debugging symbols package lintian's authors do not recommend running it with root privileges! Indeed, so why do you do that? ;-) that happens because i'm making the package inside 'pbuilder' environment ;) I: libsockets2: no-symbols-control-file usr/lib/libsockets.so.2.3.6 This is not about debugging symbols at all -- read the lintian tag description and the documentation it points to. that library have a shared library and seems doesn't have that control file, well, I think it's not critical i need this library in order to make the other package: wircc (web irc client) .. any sponsor please :) signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: RFS: poco (updated package)
On Sunday 30 August 2009 20:37:13 Krzysztof Burghardt wrote: 2009/8/30 George Danchev danc...@spnet.net: * it would be better to explicitly build-depends on zlib1g-dev Dependency add and new package uploaded to mentors.d.n. This is now uploaded. No need to CC me, I'm subscribed. Thanks. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: gforth (updated)
Peter Pentchev schrieb: Dear mentors, I am looking for a sponsor for the new version 0.7.0+ds1-3 of my package gforth. This is an attempt to fix three different failures to build on mips, armel, and s390 respectively. It builds these binary packages: gforth - GNU Forth Language Environment gforth-common - GNU Forth architecture-independent dictionaries The package has been tested with lintian and pbuilder. The package can be found on mentors.debian.net: http://mentors.debian.net/debian/pool/main/g/gforth/gforth_0.7.0+ds1-3.dsc I would be glad if someone uploaded this package for me. JFYI, here's the changelog entry: gforth (0.7.0+ds1-3) unstable; urgency=low * Explicitly depend on libtool and libltdl-dev; several benefits: - make the build environment-agnostic and not dependent on what just happens to be installed - fix a FTBFS if libtool is installed but libltdl-dev isn't; some of the autobuilders are configured that way * Add a missing semicolon in engine/support.c to try and fix the FTBFS on s390. * Temporarily use libffi instead of libffcall on armel, until libffcall's issues are resolved. -- Peter Pentchev r...@ringlet.net Tue, 01 Sep 2009 17:58:12 +0300 Uploaded. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: CDBS question
On Tue, Sep 1, 2009 at 5:40 PM, Zak B. Elepzak...@zakame.net wrote: On Tue, 2009-09-01 at 17:23 +0300, Hai Zaar wrote: I have several patches for a package called varlkyrie. Some of these patches change configure.in and Makefile.am. I.e. I need to run autoreconf after applying patches. Following CDBS documentation, I've added these lines to debian/rules makebuilddir/valkyrie:: cat m4/* acinclude.m4 autoreconf But the problem is that this got executed _before_ patches get applied. Here is the log: [...] How can I make it to run after patching? Try the post-patches target, like this: That helped indeed. Thank you!! post-patches:: cat m4/* acinclude.m4 autoreconf Though I would usually defer to an autogen.sh if its supplied in the source (and if it doesn't prompt for stuff like gettextize,) over autoreconf. -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers -- Zaar -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libsockets
On Tuesday 01 September 2009 17:34:20 Leinier Cruz Salfran wrote: El mar, 01-09-2009 a las 09:30 +, Yavor Doganov escribió: В Fri, 28 Aug 2009 17:36:11 -0400, Leinier Cruz Salfran написа: libsockets (2.3.6-2) unstable; urgency=low * Added debugging symbols package lintian's authors do not recommend running it with root privileges! Indeed, so why do you do that? ;-) that happens because i'm making the package inside 'pbuilder' environment ;) You can also login into the chroot environment: # cowbuilder --login (--bindmount /dir - if you need something from outside, eventually) and get adduser installed, then build your package, provided you also installed the needed build-dependencies. This way you can also test your package for install/remove/upgrade from previous version/whatever in a clean chroot environment. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libsockets
thanks for the tips .. actually I use pbuilder --login --bindmounts /home/salfrancl --save-after-login and after package creation I install/remove within the environment .. the line lintian's authors do not recommend running it with root privileges! is because 'lintian' detects I'm using user 'root' (within 'pbuilder' environment) .. I think it's not a problem thanks anyway ;) El mar, 01-09-2009 a las 19:40 +0200, George Danchev escribió: On Tuesday 01 September 2009 17:34:20 Leinier Cruz Salfran wrote: El mar, 01-09-2009 a las 09:30 +, Yavor Doganov escribió: В Fri, 28 Aug 2009 17:36:11 -0400, Leinier Cruz Salfran написа: libsockets (2.3.6-2) unstable; urgency=low * Added debugging symbols package lintian's authors do not recommend running it with root privileges! Indeed, so why do you do that? ;-) that happens because i'm making the package inside 'pbuilder' environment ;) You can also login into the chroot environment: # cowbuilder --login (--bindmount /dir - if you need something from outside, eventually) and get adduser installed, then build your package, provided you also installed the needed build-dependencies. This way you can also test your package for install/remove/upgrade from previous version/whatever in a clean chroot environment. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Issue with dpkg-shlibdepds
On Tue, Sep 01, 2009 at 07:45:53AM -0500, Boyd Stephen Smith Jr. wrote: In 20090901055635.gc6...@glandium.org, Mike Hommey wrote: On Mon, Aug 31, 2009 at 04:03:06PM -0700, Joe Smith wrote: Another issue sprung up, though. What I need to be able to do now is have libngi3 (0.8) and libngi3 (0.9) installed at the same time. They don't share any binaries that are the same. Why would you want that, actually ? Most of the time, this is not something you'd want. If they are compatible, you don't even need that. If they are not compatible, then the SONAME should be changed, not the package name. However, changing the (binary) package name could possibly allow side-by-side installation of the old ABI and the new ABI. It doesn't possibly allow it, it *does* allow it, since different ABIs *must* have different package and library names. Mike -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libsockets
On Tuesday 01 September 2009 19:37:18 Leinier Cruz Salfran wrote: thanks for the tips .. actually I use pbuilder --login --bindmounts /home/salfrancl --save-after-login and after package creation I install/remove within the environment .. the line lintian's authors do not recommend running it with root privileges! is because 'lintian' detects I'm using user 'root' (within 'pbuilder' environment) .. I think it's not a problem It is not a problem per se for your packages, but might be a problem for your system, which is highly unlikely, since lintian hardly does rm -rf frivolously, but bugs happen and anyway nice to have in mind when lintian authors say so. What I meant to write was to install lintian as root inside the cow chroot, and then check your packages as non-root, but I now see I missed to write that in my previous message. This way your system is safe enough - nothing beats, non-root inside chroot ;-) thanks anyway ;) Welcome. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: libsockets
El mar, 01-09-2009 a las 20:58 +0200, George Danchev escribió: On Tuesday 01 September 2009 19:37:18 Leinier Cruz Salfran wrote: thanks for the tips .. actually I use pbuilder --login --bindmounts /home/salfrancl --save-after-login and after package creation I install/remove within the environment .. the line lintian's authors do not recommend running it with root privileges! is because 'lintian' detects I'm using user 'root' (within 'pbuilder' environment) .. I think it's not a problem It is not a problem per se for your packages, but might be a problem for your system, which is highly unlikely, since lintian hardly does rm -rf o_O frivolously, but bugs happen and anyway nice to have in mind when lintian authors say so. What I meant to write was to install lintian as root inside the cow chroot, and then check your packages as non-root, but I now see I missed to write that in my previous message. This way your system is safe enough - nothing beats, non-root inside chroot ;-) thanks once again .. i'll follow your advice because i'm using '--save-after-login' thanks anyway ;) Welcome. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Issue with dpkg-shlibdepds
On Tuesday 01 September 2009 12:54:21 Mike Hommey wrote: On Tue, Sep 01, 2009 at 07:45:53AM -0500, Boyd Stephen Smith Jr. wrote: In 20090901055635.gc6...@glandium.org, Mike Hommey wrote: On Mon, Aug 31, 2009 at 04:03:06PM -0700, Joe Smith wrote: Another issue sprung up, though. What I need to be able to do now is have libngi3 (0.8) and libngi3 (0.9) installed at the same time. They don't share any binaries that are the same. Why would you want that, actually ? Most of the time, this is not something you'd want. If they are compatible, you don't even need that. If they are not compatible, then the SONAME should be changed, not the package name. [C]hanging the (binary) package name could possibly allow side-by-side installation of the old ABI and the new ABI. It doesn't possibly allow it, it *does* allow it, since different ABIs *must* have different package and library names. If the library package also ships utility binaries or data[1], changing the binary package name would not allow side-by-side installation since the packages would still conflict. I was speaking in the general case. For this package, separate binary package names (and SO_VERSIONs) will all side-by-side installation. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ [1] For example, because they are/were too small to in a separate binary package. signature.asc Description: This is a digitally signed message part.
RFS: aptoncd (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.1.98+bzr112-1 of my package aptoncd. It builds these binary packages: aptoncd- Installation disc creator for packages downloaded via APT The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/a/aptoncd - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/a/aptoncd/aptoncd_0.1.98+bzr112-1.dsc I would be glad if someone uploaded this package for me. Kind regards Fabrice Coutadeur -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: evilvte (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for the new version 0.4.4.2-1 of my package evilvte. (Programming language: C) It builds the binary package: evilvte The latest entry in the Debian changelog is: evilvte (0.4.4.2-1) unstable; urgency=low . * New upstream bugfix release - fix an CLOSE_DIALOG bug which could destroy the program by accident * Update debian/rules to use $(MAKE) distclean instead of $(MAKE) clean * Add debian/README.source * Bump Standards-Version to 3.8.3, no changes needed. Description: an VTE based super lightweight terminal emulator evilvte is a terminal emulator. It supports almost everything VTE provides. It also supports tabs, tabbar autohide, and switch encoding at runtime. Configuration is via editing source code and recompilation. . This build provides all runtime changeable options in the right-click menu. The package is lintian clean. The package can be found on mentors.debian.net: - - dget http://mentors.debian.net/debian/pool/main/e/evilvte/evilvte_0.4.4.2-1.dsc I would be glad if someone uploaded this package for me. :-) Kind regards Wen-Yen Chuang - -- My GPG key is signed by Debian Developer Masayuki Hatta. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqd1PoACgkQdEpXpumNYVlHngCgj1fQIV8PbcMv5tpNgsFCuhvb G/4An14am96CIN7FqaypKTu4DTUIkw4A =eRqj -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: Issue with dpkg-shlibdepds
On Wed, Sep 2, 2009 at 3:11 AM, Boyd Stephen Smith Jr.b...@iguanasuicide.net wrote: If the library package also ships utility binaries or data[1], changing the binary package name would not allow side-by-side installation since the packages would still conflict. That makes the package fail to comply with Policy 8.2: http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-support-files If your package contains files whose names do not change with each change in the library shared object version, you must not put them in the shared library package. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
