Bug#544074: ITP: libsockets -- C++ Sockets Library
Package: wnpp Severity: wishlist Owner: Leinier Cruz Salfran salfra...@ipigto.rimed.cu * Package name: libsockets Version : 2.3.6 Upstream Author : Anders Hedstrom gry...@alhem.net * URL : http://www.alhem.net/Sockets/ * License : GPL Programming Lang: C++ Description : C++ Sockets Library This is a C++ class library wrapping the berkeley sockets C API, and therefore works on most unixes and also win32. The library is in use in a number of real world applications, both commercial and open source. Features include, but are not limited to: - TCP and UDP sockets (client and server) - HTTP protocol (client and server) - IPv6 support - SSL support - XML support - Highly customizable error handling - Threaded model (can create threads too) Testing has been done on Linux and Windows 2000, and to some part on Solaris and Mac OS X. The source code is released under the terms of the GNU GPL, but is also available under an alternative license (http://www.alhem.net/Sockets/ for further details). -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#544074: ITP: libsockets -- C++ Sockets Library
#539568 was my first ITP, unfortunatelly, I made some mistakes I fixed in #544074 and the new package .. the main change: - the library name comply with the upstream library name upstream: Sockets library: sockets in #539568 I set the library name to 'sockets++' in order to make available space to other related project (e.g. 'sockets' [C]) but I understood that I can not change the upstream things I dont' know how to delete #539568, so I suppose it will be there some time .. if you know how to delete it let me know, please El vie, 28-08-2009 a las 13:27 -0300, Mauro Lizaur escribió: Hola Leinier, 2009-08-28, Leinier Cruz Salfran: Package: wnpp Severity: wishlist Owner: Leinier Cruz Salfran salfra...@ipigto.rimed.cu * Package name: libsockets Version : 2.3.6 Upstream Author : Anders Hedstrom gry...@alhem.net * URL : http://www.alhem.net/Sockets/ * License : GPL Programming Lang: C++ Description : C++ Sockets Library What happened with #539568 [0] [0] http://bugs.debian.org/539568 Saludos, Mauro -- JID: lavaram...@jabber.org | http://lusers.com.ar/ 2B82 A38D 1BA5 847A A74D 6C34 6AB7 9ED6 C8FD F9C1 signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Taking care of exising packages
Hello
I want to take this opportunity to add that the bugs need to be
addressed, especially the wish list. There are people who send bugs to
request to be added or taken into consideration certain properties and
functionality in the packages and maintainers are ignoring. Another
thing is the system of new packages (debian-mentors,
mentors.debian.net) .. I think that there could be a team dedicated to
addressing this important task, same as the team dedicated to the
kernel, the core packages, translation, among other important packages.
I believe that this significantly affects the quality of the
distribution
El mié, 19-08-2009 a las 08:55 -0300, Rogério Brito escribió:
Dear all,
Motivated by some unfortunate trends seen in debian-mentors, I would
like to raise (again) the question of wheter we are doing the right
thing or not.
Here is my plea:
,
| Attn Debian/Ubuntu/whatever developers and maintainers:
|
| It is with sadness that I see many NEW packages uploaded to the Debian
| repository and little thought about some packages that are already in
| the distribution, but that are bit-rotting.
|
| Please, if an existing package has not been updated for some time, just
| publicize this fact more conspicuously. Let us engage the existing (and
| prospective) maintainers in taking care of aging, but still useful
| packages.
|
| If, OTOH, the packages are not useful, or no one is willing to maintain
| it in Debian, I would propose to remove it as soon as possible from the
| archives, since they present problems (two of the first that come to
| mind are: users installing packages that won't work/might break their
| systems, and the burden of having to worry about security updates).
|
| In a certain sense, more *MAINTAINANCE* of programs should be expected
| from Debian Developers/Maintainers (and not only of packages, but also
| regarding the ports).
|
| Let us take a moment of reflextion regarding the archive as a whole and
| not just fire up/accept new ITP's and RFS's without taking into
| consideration the current state (and the Release Critical bug counts) of
| the existent packages.
|
| This is not meant to say that new packages should be unnacepted: just
| that a second (and third, fourth, etc) thought should be given if you
| can help improve the Distribution, so that we don't end up with a lot of
| half-working packages where all but a few are actually usable.
`
Regards, Rogério Brito.
P.S.: Please, CC'me as I am only subscribed to -mentors, but not -devel.
--
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
signature.asc
Description: Esta parte del mensaje está firmada digitalmente
Re: Bug#454993: RFH: fglrx-driver -- non-free AMD/ATI r5xx, r6xx display driver
hello. I see this post and I would ask the team that keep the old version of theses packages in order to allow me to use my old integrated video card 'ati radeon xpress 200' El mar, 18-08-2009 a las 23:11 +0200, Patrick Matthäi escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, it is an old RFH, but I want to remind it: We are needing help with the fglrx packaging. The person who would apply for this job should require the following: - - Using a radeon card 2000 HD, which is supported by fglrx = 9.4 - - Using unstable for testing out new releases - - He/She hasn't got to be a DD, but minor packaging experience should be available, at least he/she should know how to build a package from svn trunk - - Interested in testing out and hopefully also hunting open bugreports. FAQ: - - Why we do not need stable users for this job? The only issues we may fix in stable releases are packaging ones, which is our code, in some *realy rare* cases also on the kernel module.. - - Why do we require ppl with a radeon card 2000 HD? fglrx 9.3 dropped support for all belower chipsets, the current team is unable to realy test the new uploaded releases, because of the lack of hardware. - -- /* 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) iEYEARECAAYFAkqLGQsACgkQ2XA5inpabMcrxwCfT2XoTo+1QSwsc2PkDeirgSgq IBoAnifftV357ov6+cV5ITS/lvgPMCK5 =HmgG -END PGP SIGNATURE- signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Taking care of exising packages
El mié, 19-08-2009 a las 20:07 +0200, Patrick Matthäi escribió: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Leinier Cruz Salfran schrieb: Hello I want to take this opportunity to add that the bugs need to be addressed, especially the wish list. There are people who send bugs to request to be added or taken into consideration certain properties and functionality in the packages and maintainers are ignoring. Another Examples? Personaly on wishlist items (new upstream functionalitys) it is the job of upstream to address them, the maintainer should forward it to them and maybe upstream does not want it? You're right in that part, it all depends from the point of view we look, now evaluate this: if the sender requests that maintainer of the package to take into consideration to add or modify any part of the package, or add something missing and that can be added? For example, if I create a program in Perl or Python, I pack and upload it and someone asks me to consider adding a file that may help, or someone requests a modification of the code? That is what I mentioned in my previous post. thing is the system of new packages (debian-mentors, mentors.debian.net) .. I think that there could be a team dedicated to addressing this important task, same as the team dedicated to the kernel, the core packages, translation, among other important packages. I think you do not know how much work it is to sponsor a packages, especially if it is NEW or the maintainer does not have enough experience yet and the whole sponsoring requests ends up in a 30 mails conversation.. I do not think you're right in that part. I do not deny that I lack experience, but I know that to create a package takes time and dedication and thus, to evaluate and see if the package meets the minimum requirements takes more time. For the same reason is that, as a suggestion, I explained to DD to assess the possibility of creating a team of DD that can be charged with this task that is as important as many other I believe that this significantly affects the quality of the distribution Debian has the biggest software repository of every distribution. I do not think that it is a *such important* part to include new software. The most important RFS reports are such which fixes bugs (especially RC ones). I agree with you in the part that is more important to address a package that updates or fixes a bug, but it is also important to address the new revenue package. An example of this, when I started using Debian one of the things that impressed me was the amount of programs, games, tools, and libraries that exist in the repository. Just ordered a 'apt-get' and was installed and almost ready to use. For some weeks I take a look on the mentors mail archive and the packages list for sponsors on mentors.debian.net - I wanted to sponsor packages which are waiting since ages to get uploaded. My result was, that most packages are more or less quickly uploaded, but neither the sponsor and maintainer replied to the thread on the mailing list / removed the package from mentors, which is bad. I have for you a scenario: Suppose you're excited about Debian, you like Debian, you want to help to make Debian better and spend part of your time to package a program, game, tool or a library. When you finished, you test it with 'lintian', install, uninstall, then uploaded to the 'mentors.debian.net' and finally sent an RFS. Spend one week, two weeks, three weeks and it's time that you ask yourself: What is happening? Until the time comes to desist from a help and good day, after a very long time, you receive a message talking about a DD package, then what are you doing? And the time comes that you no longer want to help. A good day, after a very long time, you receive a message from a DD talking about your package, what you would do in that time? What I want to say: I think the current situation is not as dramatical as some people state it here, please correct me if I have got a wrong view of it. Not misinterpret me, please, my only goal is to assess how DD can improve the current situation of the incoming packages for the sake of those want to help not be disappointed. - -- /* 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) iEYEARECAAYFAkqMP20ACgkQ2XA5inpabMdEIgCeLET/h/2n8CDkpgS6WTShKNBa eeEAn2pvmlsMiyhI1/u+ug1FZtUEUjsC =3XMu -END PGP SIGNATURE- signature.asc Description: Esta parte del mensaje está firmada digitalmente
can i use 'piuparts' within 'pbuilder'
hello dd. 1- can i use 'piuparts' within 'pbuilder'? 2- is required use 'piuparts' in order to upload a package? i'm not sure .. waiting ;) signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Quiero borrar un Bug ITP
esto del empaquetado se vuelve dificil cuando quien crea la libreria es otra persona .. uno debe ajustarse a sus condiciones asi haya liberado la libreria con gpl3 .. quiero empaquetar esta libreria por varios motivos: - mi primer paquete - es una libreria que uso desde hace un ano aproximadamente - le tengo carino - quiero hacerlo - quiero hacerlo como sea bueno hablando con el autor ahora me veo en la necesidad de cambiarle el nombre al paquete luego de haberlo creado, vaya rollo .. le quitare '++', y la libreria sera hasta con inicial mayuscula, vaya rollo, pero bueno, que asi sea una pregunta, si la libreria usa openssl, puedo subirla? El jue, 13-08-2009 a las 11:37 -0500, Gunnar Wolf escribió: Leinier Cruz Salfran dijo [Wed, Aug 12, 2009 at 08:06:45AM +]: gracias ya actualice el paquete .. corregi estos errores: (...) - corregido los errores de 'lintian -i' .. solo queda uno, no se como agregar una excepcion ¿Qué error queda? ¿Estás seguro de que no puedes corregirlo también? En todo caso, puedes crear un archivo de overrides¹. Pero en general, evita hacerlo. Lintian tiene casi siempre la razón. ahora hace falta un patrocinador .. viene solo o tengo que buscarlo en alguna parte Tienes que buscarlo. Dependiendo de qué se trata tu paquete, tal vez alguien de aquí lo pueda hacer - pero lo más común sería buscar a través de mentors. Aprovecho la mención de mentors — Esta lista tiene bajo tráfico, así que no nos ponemos difíciles para ayudarte con estas cosas de la empaquetada. Sin embargo, es conveniente que vayas más bien a la lista adecuada: debian-ment...@lists.debian.org³. Saludos, ¹ http://taquiones.net/debian/lintian_overrides.html ² http://mentors.debian.net/cgi-bin/welcome ³ http://lists.debian.org/debian-mentors/ -- Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244 signature.asc Description: Esta parte del mensaje está firmada digitalmente
puedo usar 'piuparts' dentro de 'pbuilder'
hola dd. 1- puedo usar 'piuparts' dentro de 'pbuilder'? 2- es obligatorio usa 'piuparts' en aras de subir un paquete? en espera de que me despejen la duda .. gracias de antemano ;) signature.asc Description: Esta parte del mensaje está firmada digitalmente
I want to delete an ITP
Hello. I'm creating my first package, after reading the debian policy and others mails in 'debian-mentors' list I want to delete the ITP Bug #539568 in order to create a new one with the same library but with other name .. How can I do that? Thanks signature.asc Description: Esta parte del mensaje está firmada digitalmente
Quiero borrar un Bug ITP
Hola. Hace algunos dias atras cree un Bug ITP #539568 .. Despues de algunas pruebas, de leer las Reglas de Debian y otros correos en 'debian-mentors' quiero borrar ese Bug ITP viejo y crear otro con otro nombre .. Como puedo hacerlo? Gracias... signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Quiero borrar un Bug ITP
supuse que eso debia si quiero cambiar la descripcion hago un 'merge'??? El mié, 12-08-2009 a las 21:52 +, Jose Luis Rivas escribió: Simplemente usa cont...@b.d.o y desde ahí haz un retitle del bug -Original Message- From: Leinier Cruz Salfran salfra...@ipigto.rimed.cu Date: Wed, 12 Aug 2009 05:30:08 To: debian-devel-spanish@lists.debian.org Subject: Quiero borrar un Bug ITP Hola. Hace algunos dias atras cree un Bug ITP #539568 .. Despues de algunas pruebas, de leer las Reglas de Debian y otros correos en 'debian-mentors' quiero borrar ese Bug ITP viejo y crear otro con otro nombre .. Como puedo hacerlo? Gracias... signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Quiero borrar un Bug ITP
una duda si envio el mensaje a control, en donde pongo las ordenes? asunto o cuerpo? si son varias ordenes en un mensaje? ejemplo: # cambiar version del itp to: control subject: package libsockets++ reassign 539568 libsockets++ 2.3.5 quit #cambiar descripcion to: control subject: retitle 539568 libsockets++2: C++ sockets class library descripcion corregida del paquete ? El mié, 12-08-2009 a las 22:02 +, Jose Luis Rivas escribió: No, simplemente vuelves a enviar la descripción. Igual eso es más protocolar. Donde debe ir realmente bien es en el debian/control, no te preocupes tanto pot lo que dice el itp -Original Message- From: Leinier Cruz Salfran salfra...@ipigto.rimed.cu Date: Wed, 12 Aug 2009 05:53:36 To: debian-devel-spanish@lists.debian.org Subject: Re: Quiero borrar un Bug ITP supuse que eso debia si quiero cambiar la descripcion hago un 'merge'??? El mié, 12-08-2009 a las 21:52 +, Jose Luis Rivas escribió: Simplemente usa cont...@b.d.o y desde ahí haz un retitle del bug -Original Message- From: Leinier Cruz Salfran salfra...@ipigto.rimed.cu Date: Wed, 12 Aug 2009 05:30:08 To: debian-devel-spanish@lists.debian.org Subject: Quiero borrar un Bug ITP Hola. Hace algunos dias atras cree un Bug ITP #539568 .. Despues de algunas pruebas, de leer las Reglas de Debian y otros correos en 'debian-mentors' quiero borrar ese Bug ITP viejo y crear otro con otro nombre .. Como puedo hacerlo? Gracias... signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: Quiero borrar un Bug ITP
gracias ya actualice el paquete .. corregi estos errores: - debian/copyright mal formado .. ahora ya cumple con los requisitos - debian/control con errores menores .. me fije en otros paquetes de libreria y ahora creo que si esta al kilo - actualizado a Standards-Version: 3.8.2 - corregido los errores de 'lintian -i' .. solo queda uno, no se como agregar una excepcion - la libreria la instale y desinstale con exito y no quedo restos de ella en la desinstalacion ahora hace falta un patrocinador .. viene solo o tengo que buscarlo en alguna parte gracias El mié, 12-08-2009 a las 18:05 -0500, Gunnar Wolf escribió: Leinier Cruz Salfran dijo [Wed, Aug 12, 2009 at 06:02:13AM +]: una duda si envio el mensaje a control, en donde pongo las ordenes? asunto o cuerpo? si son varias ordenes en un mensaje? ejemplo: # cambiar version del itp to: control subject: package libsockets++ reassign 539568 libsockets++ 2.3.5 quit #cambiar descripcion to: control subject: retitle 539568 libsockets++2: C++ sockets class library descripcion corregida del paquete No te preocupes si es sólo el número de versión. Tú sigue trabajando, y punto. Un ITP no está destinado a que lo procese una computadora, sino para que lo vean los humanos y eviten pisarse los mutuos callos. Si el paquete que vas a empaquetar es libsockets++ o algo substancialmente similar (no sé si sea un dedazo lo de libsockets++2), yo lo dejaría como está. Pero bueno, como sea - El paquete no está asignado a libsockets++, dado que no es un paquete que forme aún parte de Debian. Está asignado al metapaquete wnpp - Y así debe quedar hasta que sea cerrado. Puedes cambiarle la descripción, pero no tiene mucho sentido. Saludos, -- Gunnar Wolf • gw...@gwolf.org • (+52-55)5623-0154 / 1451-2244 signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: maybe a problem with sid branch
Hello Muammar I understand you also .. The only purpose of my post was to warn the person concerned had an error in package dependencies that uploaded to the sid branch in order that he might realize the problem and correct the package My intentions have been good at all times. El lun, 03-08-2009 a las 01:36 -0430, Muammar El Khatib escribió: Hi, 2009/8/1 Leinier Cruz Salfran salfra...@ipigto.rimed.cu: I disagree with you on this point .. where is success? in a civilized discussion on the proposal and the exchange of ideas .. if we discover that there is a problem why we will not publish this list, for example, although it is obvious that this is a problem of dependencies and is the branch where are shown all recent changes and new packages that have probability of failure? .. I think if we want development we can not be put obstacles .. that is my humble opinion I understand your point, but you should be aware of the definition of this Debian branch: 1) http://www.debian.org/releases/unstable/ 2) http://en.wikipedia.org/wiki/Debian#Distributions As you can see, in 1) there says: sid is subject to massive changes and in-place library updates. This can result in a very unstable system which contains packages that cannot be installed due to missing libraries, dependencies that cannot be fulfilled etc. So, in spite of your correct rationale about this, sid may have problems related to _minor_ dependencies and this is the case (because of its changing-nature). This is a common problem when trying to create a base.tgz in pbuilder. Just try again later. Regards, -- Muammar El Khatib. Linux user: 403107. GPG Key = 127029F1 http://muammar.me | http://proyectociencia.org ,''`. : :' : `. `' `- signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: maybe a problem with sid branch
thanks both of you frans and daniel i must to get involved with reportbug El dom, 02-08-2009 a las 08:59 +0200, Frans Pop escribió: Leinier Cruz Salfran wrote: The following packages have unmet dependencies: aptitude: Depends: libapt-pkg-libc6.9-6-4.7 but it is not installable Depends: libept0 (= 0.5.26+b1) but it is not going to be installed This is not a problem with sid, but very simply how sid works. It is *normal* that packages are uninstallable sometimes due to uploads of new versions of packages they depend on. That's the whole point of having sid. Sure, it can be inconvenient if that lasts a bit longer sometimes, but normally the people responsible for solving such issues are well aware of them and such mails (or even bug reports like #539376) are not needed. I disagree with you on this point .. where is success? in a civilized discussion on the proposal and the exchange of ideas .. if we discover that there is a problem why we will not publish this list, for example, although it is obvious that this is a problem of dependencies and is the branch where are shown all recent changes and new packages that have probability of failure? .. I think if we want development we can not be put obstacles .. that is my humble opinion If you use sid and there are minor dependency issues: tough luck, just be patient and try again later! Cheers, FJP signature.asc Description: Esta parte del mensaje está firmada digitalmente
Bug#539568: ITP: libsockets++ -- C++ sockets wrapper library
Package: wnpp Severity: wishlist Owner: Leinier Cruz Salfran salfra...@ipigto.rimed.cu -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: libsockets++ Version : 2.3.4 Upstream Author : gry...@alhem.net * URL : http://www.alhemt.net/Sockets/ * License : GPL Programming Lang: C++ Description : C++ sockets class library This is a GPL licensed C++ class library wrapping the berkeley sockets C API, and therefore works on most unixes and also win32. The library is in use in a number of real world applications, both commercial and open source. .. Features include, but are not limited to, SSL support, IPv6 support, tcp and udp sockets, sctp sockets, http protocol, highly customizable error handling. Testing has been done on Linux and Windows 2000, and to some part on Solaris and Mac OS X. .. The source code is released under the terms of the GNU GPL, but is also available under an alternative license. - -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpz9C0ACgkQ8shpC1uVsMtHMwCdG/5Puo3yQddeN0ULd2h61jZL n34Anibxjw0sSzFCvF2rCmigQBlYLfSm =smrz -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
maybe a problem with sid branch
salfrancl:~# pbuilder create --distribution sid [...] The following packages have unmet dependencies: aptitude: Depends: libapt-pkg-libc6.9-6-4.7 but it is not installable Depends: libept0 (= 0.5.26+b1) but it is not going to be installed E: Broken packages - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/build//31827 and its subdirectories signature.asc Description: Esta parte del mensaje está firmada digitalmente
intento ser un nuevo dd
hola dd intento colaborar con el proyecto empaquetando una libreria creada en c ++ que uso desde hace algun tiempo .. intento llamarla: - libsockets++ (libreria compilada) - libsockets++-dev (cabeceras para el desarrollo de aplicaciones) el sitio de la bilbioteca es http://www.alhem.net/ segun el manual del nuevo desarrollador: - usa licencia gpl - es mantenida - el autor estuvo de acuerdo con el empaquetamiento por ser mi debut: - no tiene nada que ver con setuid ni guid - no es un demonio segun el manual del ndd necesito que me firmen mi llave gpg .. bueno, en espera de alguien que me ayude en el proceso un abrazo a todos desde guantanamo, cuba signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: intento ser un nuevo dd
gracias estan siendo de ayuda los vinculos aun continuo con mi meta de ser un dd un abrazo a todos El sáb, 01-08-2009 a las 20:32 -0300, Mauro Lizaur escribió: On Sat, 01 Aug 2009, Mauro Lizaur wrote: segun el manual del ndd necesito que me firmen mi llave gpg .. bueno, en espera de alguien que me ayude en el proceso 2 cosas: 1. es imposible para todos adivinar tu llave gpg 2. ni aunque la supiera, te la firmaria (creo que muchos estaran de acuerdo con esto), ya que no te conozco. Y en el caso de conocerte (via email), al mismo tiempo necesitaria algo que verifique que sos quien decis ser. Incluso al ver esa documentacion tuya, quizas tampoco te firme tu llave, porque sobretodo se trata de confiar en la persona a la cual se la estas firmando. Ahora que releo esto que escribi, quizas suene un poco mal y realmente no era la intension. Saludos, Mauro -- JID: lavaram...@jabber.org | http://lusers.com.ar/ 2B82 A38D 1BA5 847A A74D 6C34 6AB7 9ED6 C8FD F9C1 signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: intento ser un nuevo dd
gracias segun el manual dice que hay que tener trayectoria primero, bueno la estoy creando un abrazo El sáb, 01-08-2009 a las 20:22 -0300, Lisandro Damián Nicanor Pérez Meyer escribió: On Saturday 01 August 2009 00:49:55 Leinier Cruz Salfran wrote: hola dd intento colaborar con el proyecto empaquetando una libreria creada en c ++ que uso desde hace algun tiempo .. intento llamarla: - libsockets++ (libreria compilada) - libsockets++-dev (cabeceras para el desarrollo de aplicaciones) el sitio de la bilbioteca es http://www.alhem.net/ segun el manual del nuevo desarrollador: - usa licencia gpl - es mantenida - el autor estuvo de acuerdo con el empaquetamiento por ser mi debut: - no tiene nada que ver con setuid ni guid - no es un demonio segun el manual del ndd necesito que me firmen mi llave gpg .. bueno, en espera de alguien que me ayude en el proceso un abrazo a todos desde guantanamo, cuba En lo único que puedo *intentar* ayudarte es contándote que el firmado de claves se hace normalmente en persona con documentación que avale tu identidad (normalmente pasaporte). Lo que no sé es si es necesario como para empezar con un paquete, ya que dependés del sponsor de un DD. No sé si hay DDs en Cuba, pero si en algún momento llegás a viajar al exterior, avisá y en una de ésas alguien puede estar dispuesto a firmarte tu clave. Saludos, Lisandro. signature.asc Description: Esta parte del mensaje está firmada digitalmente
Re: intento ser un nuevo dd
efectivamente no hay .. por algo es que estoy pasando trabajo El sáb, 01-08-2009 a las 19:11 -0600, Moises Brenes escribió: No sé si hay DDs en Cuba, pero si en algún momento llegás a viajar al exterior, avisá y en una de ésas alguien puede estar dispuesto a firmarte tu clave. Si esta actualizado no los hay. http://db.debian.org/search.cgi -- シャカ mbrenes.blogspot.com | sibu.homelinux.org Geloof is een wens om niet te weten wat echt is signature.asc Description: Esta parte del mensaje está firmada digitalmente
quiza hay un error con la rama sid
salfrancl:~# pbuilder create --distribution sid [...] The following packages have unmet dependencies: aptitude: Depends: libapt-pkg-libc6.9-6-4.7 but it is not installable Depends: libept0 (= 0.5.26+b1) but it is not going to be installed E: Broken packages - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/build//31827 and its subdirectories signature.asc Description: Esta parte del mensaje está firmada digitalmente
