Re: RFS: faenza-icon-theme
Oh, there's one obvious thing that I didn't catch in the previous look
at your package: it is a Debian native package (meaning that it is
intended to be used only with Debian), but it should be non-native
instead.
Fixed, re-uploaded.
Adnan
2010/8/31 Rogério Brito rbr...@ime.usp.br:
Hi.
On Aug 30 2010, Rogério Brito wrote:
On Aug 30 2010, Adnan Hodzic wrote:
- dget
http://mentors.debian.net/debian/pool/main/f/faenza-icon-theme/faenza-icon-theme_0.7.dsc
Oh, there's one obvious thing that I didn't catch in the previous look
at your package: it is a Debian native package (meaning that it is
intended to be used only with Debian), but it should be non-native
instead.
Regards,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktinklmc__aqhb58wpilra_mwank6kbe2kb7ea...@mail.gmail.com
No response from official maintainer
Dear mentors! Recently I started a conversation about uploading new release of buildbot package with a lot of changes in the Debian part of the package too (http://lists.debian.org/debian-mentors/2010/08/msg00258.html). Since the package has an official maintainer who uploads his work on other packages periodically I was considered as the one who hijacked the package (http://lists.debian.org/debian-mentors/2010/08/msg00268.html). I've sent private message to the official maintainer as well since that time but still with no response. I'd like to know what steps should be done so I could work on this package in future without being misunderstood. That conversation also showed me some things on Debian release management I didn't know about (http://lists.debian.org/debian-mentors/2010/08/msg00264.html). I understood that the package cannot be uploaded to unstable since it could pass to testing just with the flow of time without any humanity checks. But I know nothing concerning upload to experimental branch and its policy. Can you advice any documents or other information sources on these policies concerning approving huge changes in the package structure? Another question I am worried about is a quality of my solution made in the package. I believe it is not bad but I feel there's could be better ways to do that. Can you please advice where I can discuss my solution and the way to improve them? Currently I participate in the buildbot project and I hope I can improve the software as well as it's representation in Debian. -- with best regards, Andriy Senkovych -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikdj2w4yghsjh5awttm=owwdhuv7cad6npz_...@mail.gmail.com
Type 3.0 (quilt) source packages aditional original tarballs
Dear Mentors, My package uses 4 original tarballs, one of the files within these needs to be patched, however the patch fails. I think this is because it is not extracting the additional original tarballs in to the temporary build directory. This is part of the build log: dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building lejos-nxj using existing ./lejos-nxj_0.8.5.orig.tar.gz patching file gcc-4.3.2/gcc/config/arm/t-arm-elf I think it should say something about the other original tarballs there as well. Is there anything I am missing? Thanks, Chris signature.asc Description: This is a digitally signed message part
RFS: QA: libjackasyn 0.11-5
This is a QA upload that really fixes #527416. It was supposed to be fixed in -3, but * Package name: libjackasyn Version : 0.11 Debian Revision : 5 * URL : http://covered.sourceforge.net * License : GPL-2+ Languages : C, Tcl Section : electronics Long description: Libjackasyn is an asynchronous library for interfacing with the JACK sound server. Programs that do sound input or output via the OSS system can be converted into JACK clients by starting them with the jacklaunch command. It builds these binary packages: libjackasyn-dev - Development files for libjackasyn libjackasyn0 - The Asynchrounous JACK Library The latest entry in the Debian changelog is: libjackasyn (0.11-5) unstable; urgency=low * QA upload. * Really Build-Dep on libjack-dev (Really Closes: #527416) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libjackasyn - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libjackasyn/libjackasyn_0.11-5.dsc I would be glad if someone uploaded this package for me. Kind regards, -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 (@ subkeys.pgp.net) GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100901125021.ga13...@ants.dhis.net
Re: Type 3.0 (quilt) source packages aditional original tarballs
Hi, On Wed, Sep 01, 2010 at 01:37:37PM +0100, Chris Baines wrote: I think it should say something about the other original tarballs there as well. Is there anything I am missing? Look at my package foundry for an example on how to use multiple tarballs. Simon -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100901131300.ga21...@richter
Re: RFS: packagekit
Something left to do? Regards Matthias --- The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/packagekit - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/p/packagekit/packagekit_0.6.7-1.dsc -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/db90e36d5f9e6d996cf66247352c6...@mb8-2.1blu.de
RFS: sslh (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.7a-1 of my package sslh. It builds these binary packages: sslh - ssl/ssh multiplexer The package appears to be lintian clean. The upload would fix these bugs: 563156, 565858, 593673, 593766, 594019, 594124, 594212, 594508, 594751 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/sslh - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/sslh/sslh_1.7a-1.dsc I would be glad if someone uploaded this package for me. Kind regards signature.asc Description: This is a digitally signed message part
Re: Type 3.0 (quilt) source packages aditional original tarballs
Thanks, I was using incorrect names for the additional source packages. Thanks again, Chris On Wed, 2010-09-01 at 15:13 +0200, Simon Richter wrote: Hi, On Wed, Sep 01, 2010 at 01:37:37PM +0100, Chris Baines wrote: I think it should say something about the other original tarballs there as well. Is there anything I am missing? Look at my package foundry for an example on how to use multiple tarballs. Simon signature.asc Description: This is a digitally signed message part
question about proprietary libraries
Hello, This is a general question about linking to proprietary libraries. Specifically I am thinking about developing a library which will work normally in the general case, but in some cases the user might have a proprietary library installed on their system, in which case I'd like to dynamically load that library and call out to its functions. The proprietary library in this case would be for doing I/O with a particular hardware device, for which there is currently no open source alternative. Therefore the user owning such a device would have installed the software and expect my library to work with it. Conversely, he would not have the proprietary library unless he has the device in question.. so I sort of think of this library as being part of the device. I don't have the ability to reverse engineer it and write my own drivers, but I'd still like users of this device to be able to make use of my software. Would such a library have difficulty getting accepted by Debian? Are there other examples of libraries in Debian which optionally leverage proprietary code if it is available? thanks, Steve -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=k5pyo6j4843t_-giynsrboresbn4=xtqqj...@mail.gmail.com
Re: question about proprietary libraries
On 01/09/10 20:40, Stephen Sinclair wrote: Hello, This is a general question about linking to proprietary libraries. Specifically I am thinking about developing a library which will work normally in the general case, but in some cases the user might have a proprietary library installed on their system, in which case I'd like to dynamically load that library and call out to its functions. The proprietary library in this case would be for doing I/O with a particular hardware device, for which there is currently no open source alternative. Therefore the user owning such a device would have installed the software and expect my library to work with it. Conversely, he would not have the proprietary library unless he has the device in question.. so I sort of think of this library as being part of the device. I don't have the ability to reverse engineer it and write my own drivers, but I'd still like users of this device to be able to make use of my software. Would such a library have difficulty getting accepted by Debian? Are there other examples of libraries in Debian which optionally leverage proprietary code if it is available? Not exactly a library, but the kernel will load proprietary firmware if it finds it available and the device in question exists. As long as your software is useful without said proprietary library, it can go in main. If not, it should go in contrib. -- Saludos, Felipe Sateler signature.asc Description: OpenPGP digital signature
