Re: WNPP/ITP/... for Amazon SDK for C++ ?
On Sat, Jan 08, 2022 at 10:31:03AM -0600, Dirk Eddelbuettel wrote: > You have a large set there which covers three of the ones I'd need. Could > you upload these: > > https://salsa.debian.org/rvandegrift/aws-c-common > https://salsa.debian.org/rvandegrift/aws-checksums > https://salsa.debian.org/rvandegrift/aws-c-event-stream > > to allow partial progress, and a 'base camp' from which we can continue? > (You have quite the load there too...) Maybe we can then build the AWS SDK > (or parts thereof) we need on top? The cloud team met this week and we discussed this. We're happy to do this, but there's one caveat: as far as we know, upstream won't provide long term supported releases for this stack. They work in the "everyone runs the newest" model. Probably not a big deal for aws-c-common or aws-checksums. But aws-c-event-stream (transitively) depends on s2n and aws-lc where security support is critical. So it's probably not feasible to ship in a stable release. Still, it'd be useful to provide packages so folks can start to experiment - hopefully things will eventually settle down. I'll start making sure these are ready to go, and I'll ping you when they're ready. Would you mind uploading or sponsoring the initial round? I'm nonuploading, so I can't create new binary packages. Thanks, Ross
Re: WNPP/ITP/... for Amazon SDK for C++ ?
On 13 January 2022 at 19:18, Ross Vandegrift wrote: | On Sat, Jan 08, 2022 at 10:31:03AM -0600, Dirk Eddelbuettel wrote: | > You have a large set there which covers three of the ones I'd need. Could | > you upload these: | > | > https://salsa.debian.org/rvandegrift/aws-c-common | > https://salsa.debian.org/rvandegrift/aws-checksums | > https://salsa.debian.org/rvandegrift/aws-c-event-stream | > | > to allow partial progress, and a 'base camp' from which we can continue? | > (You have quite the load there too...) Maybe we can then build the AWS SDK | > (or parts thereof) we need on top? | | The cloud team met this week and we discussed this. We're happy to do | this, but there's one caveat: as far as we know, upstream won't provide | long term supported releases for this stack. They work in the | "everyone runs the newest" model. Probably not a big deal for | aws-c-common or aws-checksums. But aws-c-event-stream (transitively) | depends on s2n and aws-lc where security support is critical. So it's | probably not feasible to ship in a stable release. "Fine by me" (for now). | Still, it'd be useful to provide packages so folks can start to | experiment - hopefully things will eventually settle down. Exactly. Testing support on a rolling basis is great. | I'll start making sure these are ready to go, and I'll ping you when | they're ready. Would you mind uploading or sponsoring the initial | round? I'm nonuploading, so I can't create new binary packages. Great. Happy to do that. Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Re: WNPP/ITP/... for Amazon SDK for C++ ?
On 31 December 2021 at 07:51, Dirk Eddelbuettel wrote: | On 30 December 2021 at 22:17, Ross Vandegrift wrote: | | On Mon, Dec 27, 2021 at 08:10:50AM -0600, Dirk Eddelbuettel wrote: | | > My (very informal) packaging has always been in the open (but on GitHub). A | | > possible first step might be to review the added files in debian/ and in a | | > first pass edit out all references to 'informal' or 'unofficial' packaging | | > and making them more official in the cloud team repo -- which I presume is on | | > salsa? If you or others want to look, I have this currently at github.com in | | > | | > eddelbuettel/pkg-aws-c-common common C layer | | > eddelbuettel/pkg-aws-checksumschecksum for transport | | > eddelbuettel/pkg-aws-c-event-stream another C layer | | > eddelbuettel/pkg-aws-sdk-cpp-only-s3 C++ SDK subset for S3 | | | | I did some work on aws-c-common & aws-c-event-stream from a PoC of packaging | | for awscli v2. Details are in #966573, message 43 [1]. You have a large set there which covers three of the ones I'd need. Could you upload these: https://salsa.debian.org/rvandegrift/aws-c-common https://salsa.debian.org/rvandegrift/aws-checksums https://salsa.debian.org/rvandegrift/aws-c-event-stream to allow partial progress, and a 'base camp' from which we can continue? (You have quite the load there too...) Maybe we can then build the AWS SDK (or parts thereof) we need on top? Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Re: WNPP/ITP/... for Amazon SDK for C++ ?
(Dual reply to two emails) On 30 December 2021 at 23:32, Wookey wrote: | On 2021-12-26 18:08 -0600, Dirk Eddelbuettel wrote: | > | > Does anybody know where we are with respect to the WNPPs / ITPs / ... on the | > Amazon SDK for C++? | > | > I have a package that could take advantage of this if it were packaged, and I | > am sure a number of other packages are in a similar situation given how | > pervasive AWS use is. | | I don't know anything about the state of this, but am in the same | place, in that I am packaging something that uses awsSDK pieces, | specifically tensorflow which wants aws-cpp-sdk-core. | | > FWIW I have packaged _subsets_ of the C++ SDK informally for my own use (also | > at Launchpad) but I don't think I have the time and energy to take this on as | > another package. | | Which bits have you done? They may or may not be sufficient to satisfy tensorflow. In Debian testing (via informal 'PPA for testing' on GitHub) and for focal via ppa:edd/misc edd@rob:~/git/ppa/docs(master)$ ls -1 libaws*deb# omitting double entries libaws-c-common-dev_0.4.59-1.debian.1_amd64.deb libaws-c-event-stream-dev_0.1.6-1.debian.1_amd64.deb libaws-checksums-dev_0.1.9-1.debian.2_amd64.deb libaws-sdk-cpp-only-s3-dev_1.8.117-3.debian.1_amd64.deb edd@rob:~/git/ppa/docs(master)$ edd@rob:~$ dpkg -l | grep libaws | cut -c-80 ii libaws-c-common-dev0.4.59-1.2004.1 ii libaws-c-event-stream-dev 0.1.6-1.2004.1 ii libaws-checksums-dev 0.1.9-1.2004.1 ii libaws-sdk-cpp-only-s3-dev 1.8.117-1.2004.1 edd@rob:~$ | I too, am not bursting to add large packages that I don't use (or even | properly know what they are) to my collection of responsibilities, but | I can spend work time on helping get this going so I don't mind | mucking in on some packaging work. Great! On 30 December 2021 at 22:17, Ross Vandegrift wrote: | On Mon, Dec 27, 2021 at 08:10:50AM -0600, Dirk Eddelbuettel wrote: | > My (very informal) packaging has always been in the open (but on GitHub). A | > possible first step might be to review the added files in debian/ and in a | > first pass edit out all references to 'informal' or 'unofficial' packaging | > and making them more official in the cloud team repo -- which I presume is on | > salsa? If you or others want to look, I have this currently at github.com in | > | > eddelbuettel/pkg-aws-c-common common C layer | > eddelbuettel/pkg-aws-checksumschecksum for transport | > eddelbuettel/pkg-aws-c-event-stream another C layer | > eddelbuettel/pkg-aws-sdk-cpp-only-s3 C++ SDK subset for S3 | | I did some work on aws-c-common & aws-c-event-stream from a PoC of packaging | for awscli v2. Details are in #966573, message 43 [1]. | | So far, I haven't uploaded any of this. The AWS SDK now requires their own | crypto & tls implementations. The cloud team discussed this a while back, no | one found that responsibility very attractive. Still, we'll want awscli v2 | eventually. I think in what I need the crypto etc comes from curl and openssl as usaul. | > The last repo is the one that is 'incomplete' as I skipped everything not | > need by my use case of accessing s3 programmatically from other C++ code. | > >From a casual look at another C++ project I noticed that it had the same | > subset so this may make sense. It would allow us to proceed and start with | > the subset and add as needed (as opposed to be overwhelmed by 'all of it'). | | I'd be worried about confusing users who expect to have the whole SDK | available. But as long as the packages only ship static libraries, I don't see | how it would cause actual issues. Right on with the name and confusion so I picked 'libaws-sdk-cpp-only-s3-dev' to signal the subset nature, at least for now. Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Re: WNPP/ITP/... for Amazon SDK for C++ ?
Hi Dirk, On Mon, Dec 27, 2021 at 08:10:50AM -0600, Dirk Eddelbuettel wrote: > My (very informal) packaging has always been in the open (but on GitHub). A > possible first step might be to review the added files in debian/ and in a > first pass edit out all references to 'informal' or 'unofficial' packaging > and making them more official in the cloud team repo -- which I presume is on > salsa? If you or others want to look, I have this currently at github.com in > > eddelbuettel/pkg-aws-c-common common C layer > eddelbuettel/pkg-aws-checksumschecksum for transport > eddelbuettel/pkg-aws-c-event-stream another C layer > eddelbuettel/pkg-aws-sdk-cpp-only-s3 C++ SDK subset for S3 I did some work on aws-c-common & aws-c-event-stream from a PoC of packaging for awscli v2. Details are in #966573, message 43 [1]. So far, I haven't uploaded any of this. The AWS SDK now requires their own crypto & tls implementations. The cloud team discussed this a while back, no one found that responsibility very attractive. Still, we'll want awscli v2 eventually. > The last repo is the one that is 'incomplete' as I skipped everything not > need by my use case of accessing s3 programmatically from other C++ code. > >From a casual look at another C++ project I noticed that it had the same > subset so this may make sense. It would allow us to proceed and start with > the subset and add as needed (as opposed to be overwhelmed by 'all of it'). I'd be worried about confusing users who expect to have the whole SDK available. But as long as the packages only ship static libraries, I don't see how it would cause actual issues. Ross [1] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966573#43
Re: WNPP/ITP/... for Amazon SDK for C++ ?
On 2021-12-26 18:08 -0600, Dirk Eddelbuettel wrote: > > Does anybody know where we are with respect to the WNPPs / ITPs / ... on the > Amazon SDK for C++? > > I have a package that could take advantage of this if it were packaged, and I > am sure a number of other packages are in a similar situation given how > pervasive AWS use is. I don't know anything about the state of this, but am in the same place, in that I am packaging something that uses awsSDK pieces, specifically tensorflow which wants aws-cpp-sdk-core. > FWIW I have packaged _subsets_ of the C++ SDK informally for my own use (also > at Launchpad) but I don't think I have the time and energy to take this on as > another package. Which bits have you done? They may or may not be sufficient to satisfy tensorflow. I too, am not bursting to add large packages that I don't use (or even properly know what they are) to my collection of responsibilities, but I can spend work time on helping get this going so I don't mind mucking in on some packaging work. Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Re: WNPP/ITP/... for Amazon SDK for C++ ?
Hi Noah, On 26 December 2021 at 20:18, Noah Meyerhans wrote: | On Sun, Dec 26, 2021 at 06:08:56PM -0600, Dirk Eddelbuettel wrote: | > I have a package that could take advantage of this if it were packaged, and I | > am sure a number of other packages are in a similar situation given how | > pervasive AWS use is. So does anybody know where this is at? | > | > FWIW I have packaged _subsets_ of the C++ SDK informally for my own use (also | > at Launchpad) but I don't think I have the time and energy to take this on as | > another package. | | The cloud-team could probably be a reasonable umbrella under which the | package could be co-maintained. Would you be interested in | co-maintaining it as part of that team? I'm not sure any of us have a | lot of expertise or desire to work with C++, but we've got a lot of | familiarity with cloud services, etc, and maintain other cloud service | SDKs. If you can contribute on the C++ side, we could probably | effectively maintain the package together. That could work. Would you be amenable to the subset packaging I have done (as opposed to grabbing all of the (rather large) SDK at GitHub) ? My (very informal) packaging has always been in the open (but on GitHub). A possible first step might be to review the added files in debian/ and in a first pass edit out all references to 'informal' or 'unofficial' packaging and making them more official in the cloud team repo -- which I presume is on salsa? If you or others want to look, I have this currently at github.com in eddelbuettel/pkg-aws-c-common common C layer eddelbuettel/pkg-aws-checksumschecksum for transport eddelbuettel/pkg-aws-c-event-stream another C layer eddelbuettel/pkg-aws-sdk-cpp-only-s3 C++ SDK subset for S3 The last repo is the one that is 'incomplete' as I skipped everything not need by my use case of accessing s3 programmatically from other C++ code. >From a casual look at another C++ project I noticed that it had the same subset so this may make sense. It would allow us to proceed and start with the subset and add as needed (as opposed to be overwhelmed by 'all of it'). Now, these are also not current as I packaged 'when I needed them' / 'when a change happened'. Upstream releases something every few days which we may or may not want to keep track of. I have however built them a few times over via launchpad for amd64. I do not know how they would fare on less common architectures. At least the checksum repo has IIRC some assembler code specific to the common platforms. Is that aspect something the cloud team had to deal with for other SDKs? | Of course, if others are already looking into packaging, they should by | all means continue, with or without coordinating with the cloud-team. Fully agreed. But if nobody steps forward this may be a viable addition. Cheers, Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Re: WNPP/ITP/... for Amazon SDK for C++ ?
On Sun, Dec 26, 2021 at 06:08:56PM -0600, Dirk Eddelbuettel wrote: > I have a package that could take advantage of this if it were packaged, and I > am sure a number of other packages are in a similar situation given how > pervasive AWS use is. So does anybody know where this is at? > > FWIW I have packaged _subsets_ of the C++ SDK informally for my own use (also > at Launchpad) but I don't think I have the time and energy to take this on as > another package. The cloud-team could probably be a reasonable umbrella under which the package could be co-maintained. Would you be interested in co-maintaining it as part of that team? I'm not sure any of us have a lot of expertise or desire to work with C++, but we've got a lot of familiarity with cloud services, etc, and maintain other cloud service SDKs. If you can contribute on the C++ side, we could probably effectively maintain the package together. Of course, if others are already looking into packaging, they should by all means continue, with or without coordinating with the cloud-team. noah
Re: WNPP: adotar pacote
On Thu, May 30, 2013 at 11:42:42PM -0300, Albino B Neto wrote: Oi Na lista dev [1] tem um e-mail sobre alguns pacotes. Sendo possível adotar um pacote [2], acerta seu bug etc. 1 - http://lists.debian.org/debian-devel/2013/05/msg00038.html 2 - http://www.debian.org/devel/wnpp/ Então, resolvi verificar o pacote q está órfão (sem mantenedor) [3] e assim adotar o ARA [4][5] 3 - http://www.debian.org/devel/wnpp/orphaned_byage 4 - http://packages.debian.org/search?searchon=sourcenameskeywords=ara 5 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450876 Como ainda não sou mantenedor de nenhum pacote então resolvi adotar um, acredito q para iniciar fica melhor. Como poderia iniciar essa ajuda no pacote ? :-) Eu acho que o que você não entendeu é que adotar um pacote _significa_ se tornar o mantenedor dele. Isso inclui resolver bugs, revisar o empacotamento, ver se tem uma nova versão upstream, etc. Não sei se o ara é um bom pacote pra iniciar, a não ser que você já conheça ocaml. :) Em geral, o ideal é manter pacotes que você *usa*, porque nesse caso você tem uma motivação intrínseca pra trabalhar nele; se eu fosse você eu escolheria um pacote que está órfão (ou que o mantenedor precisa de ajuda) *e* está instalado no seu sistema. Você pode usar o comando wnpp-alert pra identificar esses pacotes; aqui no meu sistema o wnpp-alert lista 45 pacotes nessa situação. :-) Se tiver dúvidas, pode postar aqui na lista. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Re: WNPP: adotar pacote
Olá Albino, Como foi dito para você há 2 meses nesta mesma lista[1], você deve estudar para entender o processo e ser capaz de manter um pacote com perfeição. Todos os guias citados pelo Terceiro, Marcelo Santana, Fernando Mercês e Fike são válidos e preciosos. Mas, na minha opinião, você deverá começar com o guia do novo mantenedor[2], que é constantemente atualizado e tem, por objetivo, ser um passo a passo para quem quer iniciar. É impossível não aprender por lá. O Debian é um projeto sério e existe a diferença entre querer aprender e querer ter um pacote. Quem aprender, terá um pacote. Quem apenas quiser ter um pacote, nunca terá nada, pois os sponsors verão mil erros e ficará claro que a pessoa não tem capacidade para manter um pacote. Nisso você queimará cartucho. Adotar um pacote para ter um pacote no seu nome rapidamente não é uma boa ideia, pois é muito mais difícil atualizar um pacote existente do que fazer um do zero. Eu acabo de adotar um. Veja como ficou o changelog lá no git[3]. Talvez pareça pouca coisa mas cada linha daquelas envolve inúmeras ações[4] e essas ações exigem um pleno conhecimento sobre as técnicas de empacotamento. Se você simplesmente pegar um pacote, dizer que adotou, e tentar colocar no Debian, ele não será aceito, pois é quase certo que o mesmo estará desatualizado. Como mais um exemplo, esta semana entrou um pacote meu que eu atualizei depois de um tempo (1 ano e 9 meses). Veja quanta coisa mudou nesse intervalo de tempo[5]. Quanto a atender a uma solicitação de ajuda (RFH), a coisa é mais pesada ainda. Quem pediu ajuda já mantém pacotes, conhece bem todo o processo e não consegue manter tudo sozinho atualmente. Então ele precisa de alguém bem experiente em empacotamento para ajudá-lo. Além de tudo, a pessoa que irá ajudar deverá conhecer bem o pacote e até utilizá-lo no seu dia a dia. Conclusão: se você quer manter pacotes, você precisa estudar, ler o guia [2] e a política Debian [6], ver como os outros fazem os seus pacotes (apt-get source) e tirar as dúvidas aqui. Depois, sugiro submeter um trabalho final seu a esta lista para que o mesmo seja analisado. Com isso as suas dúvidas finais serão dirimidas. Há vários DDs e mantenedores aqui em condições de ajudá-lo. Depois disso, você estará apto a manter os seus pacotes futuros. Espero ter ajudado com algum tipo de luz ou direção. []s Eriberto [1] http://lists.debian.org/debian-devel-portuguese/2013/04/msg0.html [2] http://www.debian.org/doc/manuals/maint-guide [3] http://anonscm.debian.org/gitweb/?p=collab-maint/sentinella.git;a=blob_plain;f=debian/changelog [4] http://anonscm.debian.org/gitweb/?p=collab-maint/sentinella.git;a=commitdiff [5] http://anonscm.debian.org/gitweb/?p=collab-maint/jp2a.git;a=blob_plain;f=debian/changelog [6] http://www.debian.org/doc/debian-policy Em 30 de maio de 2013 23:42, Albino B Neto bino...@binoanb.eti.br escreveu: Oi Na lista dev [1] tem um e-mail sobre alguns pacotes. Sendo possível adotar um pacote [2], acerta seu bug etc. 1 - http://lists.debian.org/debian-devel/2013/05/msg00038.html 2 - http://www.debian.org/devel/wnpp/ Então, resolvi verificar o pacote q está órfão (sem mantenedor) [3] e assim adotar o ARA [4][5] 3 - http://www.debian.org/devel/wnpp/orphaned_byage 4 - http://packages.debian.org/search?searchon=sourcenameskeywords=ara 5 - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450876 Como ainda não sou mantenedor de nenhum pacote então resolvi adotar um, acredito q para iniciar fica melhor. Como poderia iniciar essa ajuda no pacote ? :-) Albino -- To UNSUBSCRIBE, email to debian-devel-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+hf7lyq1aaerzh2tnw7vgdgtmwshc5npv4xsyro3fls...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-devel-portuguese-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAP+dXJdc93vkaeEV4=neho9xzzvnntgv4sr3xr_f4jpapya...@mail.gmail.com
Re: wnpp tags ita and rm
Hi Sebastian, * Sebastian Pipping [EMAIL PROTECTED] [2008-01-15 15:58]: -- rm i noticed this bug [1] is the only wnpp bug using the type rm for removal. is this an official type that scripts talking to BTS should support? is it documented somewhere? is it a bug in the bug report? In general this is only used to express why the package should be removed without forcing people to read the whole bug log. I think supporting the possible RM tags would be nice. The meanings are explained on: http://ftp-master.debian.org/removals.html (top of the page) -- ita i noticed the intent to adopt tag is not mentioned on [2] though used frequently. is this on purpose? I guess yes since this part is about adding a new wnpp bug. And adding a bug with ITA as tag does not make much sense. It is documented on http://www.debian.org/devel/wnpp/#l3. if not can somebody witha free minute add it? i don't have write access to that page. It may not hurt to add it with an explanation on the wnpp site. Just file a wishlist bug against www.debian.org if you want this. Kind regards Nico -- Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF For security reasons, all text in this mail is double-rot13 encrypted. pgpyiJ6ecxOmd.pgp Description: PGP signature
Re: wnpp tags ita and rm
On Tue, 2008-01-15 at 15:56 +0100, Sebastian Pipping wrote: -- rm i noticed this bug [1] is the only wnpp bug using the type rm for removal. is this an official type that scripts talking to BTS should support? is it documented somewhere? is it a bug in the bug report? -- ita i noticed the intent to adopt tag is not mentioned on [2] though used frequently. is this on purpose? if not can somebody witha free minute add it? i don't have write access to that page. Well, there's really no official thing on the wnpp bug titles. I've been working on the past on this, you can see some explanation on: http://people.debian.org/~damog/wnpp/malformed-titles.html If you think on adding such new title conventions, please talk first to -wnpp or on -qa. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ El micrófono es mi metralleta.
Re: wnpp tags ita and rm
reassign 453466 ftp.debian.org thanks On Tue, Jan 15, 2008 at 03:56:35PM +0100, Sebastian Pipping wrote: -- rm i noticed this bug [1] is the only wnpp bug using the type rm for removal. is this an official type that scripts talking to BTS should support? is it documented somewhere? is it a bug in the bug report? As the bug log shows, this is a result of a misspelled keyword. Removal bugs are supposed to be assigned to ftp.debian.org. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp tags ita and rm
Nico Golde wrote: i noticed the intent to adopt tag is not mentioned on [2] though used frequently. is this on purpose? I guess yes since this part is about adding a new wnpp bug. And adding a bug with ITA as tag does not make much sense. It is documented on http://www.debian.org/devel/wnpp/#l3. makes sense. thank you! sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Wed, 2005-09-14 at 07:50 +0200, Martin Samuelsson wrote: Wouldn't it make more sense to close bugs that hasn't recieved more info in X days than bugs that had their initial post in Y days? Some packages are trickier than others to create and may therefor take more time. As long as people post to the bug, there is some interest. Yes. That's what it have been done manually with ITPs. RFPs were completely closed now. All of this 600 days, as of today. I'm also trying to work together with Andreas Barth to bring debbugsChangedDate to real life on his bts2ldap gateway and make things better and easier for everybody. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Kumbia King: King of Kumbia. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Wed, 2005-09-14 at 12:03 +0200, Vedran Furac wrote: than 600 days by tonight (or if anything goes wrong -I have an exam Before you do that: Yeah, I know there are packages that should not be closed, probably, and they could just hide from the view and be closed. What I really trust is that if the people with intention of packaging or requesting a package to be included is really committed with the wnpp bug, they will kindly reopen it and will understand why are we doing this. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Not only is it better to have loved and lost, it's cheaper. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Bas Zoetekouw [EMAIL PROTECTED] writes: Hi David! About ITP's, they should be retitled to RFPs, rather than closed. That way, other people can have a go at packaging the software. I concur. If someone did not produce a packge withing NN days (say 3 months) after ITP, the system should automtically send the ITP sumitter mail, that his packaging effort has been returned to stae RFP and he is no longer the owner of that ITP. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Paul TBBle Hampson [EMAIL PROTECTED] writes: On Wed, Sep 14, 2005 at 02:34:51PM +0200, Vedran Furac wrote: Btw. why then mencoder, can't be packaged? Why are only ffmpeg -dev in debian: http://packages.qa.debian.org/f/ffmpeg.html? Only ffmpeg-dev is in Debian as ffmpeg upstream recommends static linking due to not having fixed the API/ABI. Upstream recommends nothing. Upstream simply don't care about shared libraries. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Hi David! You wrote: Talking with adn on IRC, I've decided to launch an script that will close every opened ITP and RFP bug on the BTS with a lifetime greater than 600 days by tonight (or if anything goes wrong -I have an exam tomorrow noon-, by tomorrow night). I'll point to documentation on how to re-open bugs, if the submitters/owners still have interest on the package. I'll do the same a couple of days later for ITPs/RFPs greater than 450 days and finally with those greater than 365 days. Later I'll set a cronjob on gluck to close all of those reaching 365 days old. In principle, I'm fine with closing RFPs after a while of no activity. However, plase don't mistake bugs being open for a long while for bug that have been inactive. You should check the date of the latest post rather than the time of opening. About ITP's, they should be retitled to RFPs, rather than closed. That way, other people can have a go at packaging the software. Also, there's no need to write your own scripts; there are scripts in some qa repsoitory somewhere (I guess tbm can tell you where, exactly) that can do exactly what you want --- and more. -- Kind regards, ++ | Bas Zoetekouw | GPG key: 0644fab7 | || Fingerprint: c1f5 f24c d514 3fec 8bf6 | | [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 | ++ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
David Moreno Garza wrote: On Tue, 2005-09-13 at 11:02 +0200, Henning Makholm wrote: But my intention was not to read the whole list and do this by hand! This should be done by the same script which sends the sem automated mails to the BTS. As there is a consensus that it is a good idea to close long-inactive RFPs with a polite explanation, anyone who care enough should just write a script to do it, and start running it. It can be done without special privileges; the BTS control address is well known... Talking with adn on IRC, I've decided to launch an script that will close every opened ITP and RFP bug on the BTS with a lifetime greater than 600 days by tonight (or if anything goes wrong -I have an exam Before you do that: - note that there is software that probably can't be packaged: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203211 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201734 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232658 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301491 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274003 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321793 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=178062 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=321797 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319860 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=323704 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=149568 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=298763 [...] AFAIK, if they are not DFSG-compliant (or depend it) they should be listed here: http://www.debian.org/devel/wnpp/unable-to-package - also note that there is software that waits some other software to get in: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195236 - popular software with status unknown: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=113238 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=247337 [...] - software that should be packaged because it's good and popular: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200984 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=78209 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=255850 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=188153 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246244 [...] - software you should talk about: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=131404 It's good idea. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Vedran Furac [EMAIL PROTECTED] writes: David Moreno Garza wrote: On Tue, 2005-09-13 at 11:02 +0200, Henning Makholm wrote: [...] - note that there is software that probably can't be packaged: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203211 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201734 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232658 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301491 Package already in Debian : gstreamer0.8-ffmpeg Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Christian Marillat wrote: Vedran Furac [EMAIL PROTECTED] writes: David Moreno Garza wrote: On Tue, 2005-09-13 at 11:02 +0200, Henning Makholm wrote: [...] - note that there is software that probably can't be packaged: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203211 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201734 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=232658 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301491 Package already in Debian : gstreamer0.8-ffmpeg Ops, then it should be closed. Btw. why then mencoder, can't be packaged? Why are only ffmpeg -dev in debian: http://packages.qa.debian.org/f/ffmpeg.html? Or gstreamer0.8-ffmpeg is used only to decode mpeg and not to encode into it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Vedran Furac [EMAIL PROTECTED] writes: Christian Marillat wrote: Vedran Furac [EMAIL PROTECTED] writes: [...] Package already in Debian : gstreamer0.8-ffmpeg Ops, then it should be closed. Btw. why then mencoder, can't be packaged? Why are only ffmpeg -dev in Normaly, encoder can't be packaged. debian: http://packages.qa.debian.org/f/ffmpeg.html? Or gstreamer0.8-ffmpeg is used only to decode mpeg and not to encode into it? Only to decode files : http://gstreamer.freedesktop.org/modules/gst-ffmpeg.html Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Wed, Sep 14, 2005 at 02:34:51PM +0200, Vedran Furac wrote: Btw. why then mencoder, can't be packaged? Why are only ffmpeg -dev in debian: http://packages.qa.debian.org/f/ffmpeg.html? Only ffmpeg-dev is in Debian as ffmpeg upstream recommends static linking due to not having fixed the API/ABI. -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpdC9o1qaIno.pgp Description: PGP signature
Re: wnpp situation
On Wed, 2005-09-14 at 07:50 +0200, Martin Samuelsson wrote: Wouldn't it make more sense to close bugs that hasn't recieved more info in X days than bugs that had their initial post in Y days? Some packages are trickier than others to create and may therefor take more time. As long as people post to the bug, there is some interest. Yes. That's what it have been done manually with ITPs. RFPs were completely closed now. All of this 600 days, as of today. I'm also trying to work together with Andreas Barth to bring debbugsChangedDate to real life on his bts2ldap gateway and make things better and easier for everybody. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Kumbia King: King of Kumbia. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Wed, 2005-09-14 at 12:03 +0200, Vedran Furac wrote: than 600 days by tonight (or if anything goes wrong -I have an exam Before you do that: Yeah, I know there are packages that should not be closed, probably, and they could just hide from the view and be closed. What I really trust is that if the people with intention of packaging or requesting a package to be included is really committed with the wnpp bug, they will kindly reopen it and will understand why are we doing this. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Not only is it better to have loved and lost, it's cheaper. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Hi, * Lars Wirzenius [EMAIL PROTECTED] [2005-09-13 10:37]: ti, 2005-09-13 kello 01:45 +0200, Alexander Schmehl kirjoitti: Close RFP after ... uhm... let's say 1 year inactivity and send the submitter an apology, that we couldn't find a volunteer for the requested package, should to very well. There was a discussion about closing old RFPs on -project in the middle of July (around the 13th, I think). I really should get acting on the consensus of that thread and close the old RFPs. Yes definetly. But my intention was not to read the whole list and do this by hand! This should be done by the same script which sends the sem automated mails to the BTS. Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org pgp7ZbJ124ML3.pgp Description: PGP signature
Re: wnpp situation
Scripsit Nico Golde [EMAIL PROTECTED] * Lars Wirzenius [EMAIL PROTECTED] [2005-09-13 10:37]: There was a discussion about closing old RFPs on -project in the middle of July (around the 13th, I think). I really should get acting on the consensus of that thread and close the old RFPs. But my intention was not to read the whole list and do this by hand! This should be done by the same script which sends the sem automated mails to the BTS. As there is a consensus that it is a good idea to close long-inactive RFPs with a polite explanation, anyone who care enough should just write a script to do it, and start running it. It can be done without special privileges; the BTS control address is well known... -- Henning Makholm I can get fat! I can sing! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Hi! * Brian Nelson [EMAIL PROTECTED] [050913 02:46]: [ long RFPs ] Or don't even open RFP bugs in the first place because they're thoroughly useless? Do you have a proposal for a better way on how our users can request / suggest software to be packaged? I don't think RFPs per se are useless - actually I have a list of some 20 RFPs I would like to take a deeper look to, as soon as I have some time - it's just that it's difficult to look at so many wnpps. Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: wnpp situation
[Alexander Schmehl] I don't think RFPs per se are useless - actually I have a list of some 20 RFPs I would like to take a deeper look to, as soon as I have some time - it's just that it's difficult to look at so many wnpps. I agree. There are packages I would like to assist into the archive as well, but haven't had time to look at. Perhaps we should have some voting mechanism, to let users tell us which missing packages are most wanted? I guess URL:http://popcon.debian.org/unknown/by_inst give us some indication about much used/installed packages missing in debian, but it is not that relevant when it comes to package maintainence (some of it is not possible to put in the archive. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Hi! Do you have a proposal for a better way on how our users can request / suggest software to be packaged? I don't think RFPs per se are useless - actually I have a list of some 20 RFPs I would like to take a deeper look to, as soon as I have some time - it's just that it's difficult to look at so many wnpps. Maybe it would a good idea to create a new web interface for the wnpp bugs. At least something that has the ability to put ITPs,RFPs in separate pages, sort them by different criterias (date, submitter). It would be nice if users had the ability to vote for RFP's (i guess it would be nice if users had the ability to vote for any bugs). An interesting idea would be creating a simpler interface for the regular user to request packaging of an application (maybe directly from the web). Radu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Alexander Schmehl [EMAIL PROTECTED] writes: Hi! * Brian Nelson [EMAIL PROTECTED] [050913 02:46]: [ long RFPs ] Or don't even open RFP bugs in the first place because they're thoroughly useless? Do you have a proposal for a better way on how our users can request / suggest software to be packaged? Considering Debian already seems to have virtually everything in the free software universe, I don't see much of a need to support user requests at all. Given the size of the developer population, if there is something out there that hasn't been packaged yet, and it's even remotely interesting, it will be packaged soon. -- Society is never going to make any progress until we all learn to pretend to like each other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Radu Spineanu [EMAIL PROTECTED] writes: Do you have a proposal for a better way on how our users can request / suggest software to be packaged? I don't think RFPs per se are useless - actually I have a list of some 20 RFPs I would like to take a deeper look to, as soon as I have some time - it's just that it's difficult to look at so many wnpps. Maybe it would a good idea to create a new web interface for the wnpp bugs. At least something that has the ability to put ITPs,RFPs in separate pages, You mean like http://www.us.debian.org/devel/wnpp/? Marc -- Fachbegriffe der Informatik - Einfach erklärt 211: Seriennummernabfrage Geklaute Ware ist vom Umtausch ausgeschlossen. (Konstantin Welke) pgp5tHYgatFT5.pgp Description: PGP signature
Re: wnpp situation
On Tue, 2005-09-13 at 13:05 +0200, Petter Reinholdtsen wrote: Perhaps we should have some voting mechanism, to let users tell us which missing packages are most wanted? Probably something like a rfp-request-seconded tag on the bug could work. Although rfp-request is somehow redundant. Cheers, -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Come to where the flavor is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Re: David Moreno Garza in [EMAIL PROTECTED] Probably something like a rfp-request-seconded tag on the bug could work. Although rfp-request is somehow redundant. Maybe some usertags-hack? But then, the people who know how that works could as well package the RFP themselves... Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: wnpp situation
On Tue, 2005-09-13 at 19:06 +0200, Marc 'HE' Brockschmidt wrote: Maybe it would a good idea to create a new web interface for the wnpp bugs. At least something that has the ability to put ITPs,RFPs in separate pages, You mean like http://www.us.debian.org/devel/wnpp/? But the proposal on date/submitter/whatever sorting on wnpp is quite interesting and easy to manage. Anyway, everybody can already query wnpp by submitters and ownership on: http://qa.debian.org/[EMAIL PROTECTED] But it is not working atm (#326679), since the LDAP thing was moved to master. Anyway, I do agree with making more work on the wnpp front, and I'm willing to help. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Yo no bebo: Es el amor el que me hace beber. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Tue, Sep 13, 2005, Christoph Berg wrote: Maybe some usertags-hack? That is exactly what we are working on, with Clément Stenac and Marc 'HE' Brockschmidt. Here[1] is a list of tags we intend to use. [1] http://wiki.debian.org/WNPPBugsTagging Please no Cc:, I read the list. -- Mohammed Adnène Trojette -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Tue, 2005-09-13 at 19:36 +0200, Mohammed Adnène Trojette wrote: [1] http://wiki.debian.org/WNPPBugsTagging This is a great work, thanks. Is there any plan to start using it and tagging? Cheers, -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D La depresión es una forma de vida.
Re: wnpp situation
* David Moreno Garza [EMAIL PROTECTED] [050913 19:11]: Perhaps we should have some voting mechanism, to let users tell us which missing packages are most wanted? Probably something like a rfp-request-seconded tag on the bug could work. Although rfp-request is somehow redundant. Currently everyone interested in such a package could send a me too mail to the report... Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: wnpp situation
Radu Spineanu [EMAIL PROTECTED] writes: At least something that has the ability to put ITPs,RFPs in separate pages, You mean like http://www.us.debian.org/devel/wnpp/? Yes, something like that. But change the information shown on each page depending of the type of wnpp entry. For example, if it's an O: show in adition to the description and time since the bug was reported how many open bugs the package has, popcon users, time of last upload, and if present the tags from [1]. If it's an ITA show the new maintainer and the corresponding tags. And also the filtering/sorting of listed packages by submitter/date/whatever. Maybe all these in some kind of nice and usable web interface like the one for NEW[2]. I would also be willing to work on this... Radu [1] http://wiki.debian.org/WNPPBugsTagging [2] http://ftp-master.debian.org/new.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Tue, Sep 13, 2005 at 08:06:22PM +0200, Alexander Schmehl wrote: * David Moreno Garza [EMAIL PROTECTED] [050913 19:11]: Perhaps we should have some voting mechanism, to let users tell us which missing packages are most wanted? Probably something like a rfp-request-seconded tag on the bug could work. Although rfp-request is somehow redundant. Currently everyone interested in such a package could send a me too mail to the report... That isn't going to do much good if nobody ever reads them. For a me too thing to be useful, it needs to be immediately clear that bug X has had Y me too votes. -- The amount of time between slipping on the peel and landing on the pavement is precisely one bananosecond -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
* Wouter Verhelst [EMAIL PROTECTED] [050913 21:35]: [ vote for RFPs ] Currently everyone interested in such a package could send a me too mail to the report... That isn't going to do much good if nobody ever reads them. For a me too thing to be useful, it needs to be immediately clear that bug X has had Y me too votes. Yes, you are right. Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: wnpp situation
Hi, * Mohammed Adnène Trojette [EMAIL PROTECTED] [2005-09-13 22:21]: On Tue, Sep 13, 2005, Christoph Berg wrote: Maybe some usertags-hack? That is exactly what we are working on, with Clément Stenac and Marc 'HE' Brockschmidt. Here[1] is a list of tags we intend to use. [1] http://wiki.debian.org/WNPPBugsTagging Please no Cc:, I read the list. What about a tag waiting-co-maintainer? Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org VIM has two modes - the one in which it beeps and the one in which it doesn't -- encrypted mail preferred pgp4Ok5DijnhC.pgp Description: PGP signature
Re: wnpp situation
On Tuesday 13 September 2005 20:36, Mohammed Adnène Trojette wrote: On Tue, Sep 13, 2005, Christoph Berg wrote: Maybe some usertags-hack? That is exactly what we are working on, with Clément Stenac and Marc 'HE' Brockschmidt. Here[1] is a list of tags we intend to use. [1] http://wiki.debian.org/WNPPBugsTagging You may add legal-problem For O also, since the upstream can change the license from free to non-free. -- pub 4096R/0E4BD0AB 2003-03-18 people.fccf.net/danchev/key pgp.mit.edu fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Tue, 2005-09-13 at 11:02 +0200, Henning Makholm wrote: But my intention was not to read the whole list and do this by hand! This should be done by the same script which sends the sem automated mails to the BTS. As there is a consensus that it is a good idea to close long-inactive RFPs with a polite explanation, anyone who care enough should just write a script to do it, and start running it. It can be done without special privileges; the BTS control address is well known... Talking with adn on IRC, I've decided to launch an script that will close every opened ITP and RFP bug on the BTS with a lifetime greater than 600 days by tonight (or if anything goes wrong -I have an exam tomorrow noon-, by tomorrow night). I'll point to documentation on how to re-open bugs, if the submitters/owners still have interest on the package. I'll do the same a couple of days later for ITPs/RFPs greater than 450 days and finally with those greater than 365 days. Later I'll set a cronjob on gluck to close all of those reaching 365 days old. All this will stall a bit the work to be done by the wnpp-tagging team :) Just a couple of days, probably. Or you could just start tagging from the recent ones. If somebody has something to say about this, please speak now. Something similar should be done with ITAs soon (retitling to O or something). -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Yo no bebo: Es el amor el que me hace beber. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
David Moreno Garza [EMAIL PROTECTED] writes: Talking with adn on IRC, I've decided to launch an script that will close every opened ITP and RFP bug on the BTS with a lifetime greater than 600 days by tonight (or if anything goes wrong -I have an exam tomorrow noon-, by tomorrow night). There is no good reason to close old RFPs unless the upstream source has diseappeared. Old ITPs should be turned into RFPs, not closed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
[EMAIL PROTECTED] wrote: There is no good reason to close old RFPs unless the upstream source has diseappeared. The spectacular amount of clutter they provide -- rendering the wnpp bug list unreadable unless you ignore them all -- combined with their total uselessness? Seems like a pair of good reasons to me. Count me in favor of deleting RFPs more than a year and a half old. -- Nathanael Nerode [EMAIL PROTECTED] Make sure your vote will count. http://www.verifiedvoting.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Tue, 2005-09-13 at 19:47 -0700, Thomas Bushnell BSG wrote: There is no good reason to close old RFPs unless the upstream source has diseappeared. Old ITPs should be turned into RFPs, not closed. Well, actually the wnpp bugs are probably the dirtiest part on the BTS: Understanding dirtiest as unattended, abandoned bugs and petitions. Most of the people working on the wnpp bugs has this concern: If nobody cares about a request or an intention to work, over a package, it should be closed, read the backlog to understand this point of view. In an example for this, I could say that I'm strongly against repeated ITPs and merged with the first one reported since they are most of the times useful and full of junk and should be closed. In this sense, this could work since people *really* interested on the ITPs and RFPs would be visible when reopening the bugs. If they don't care about the bugs they requested or were trying to package, well, it really should be closed, nobody will ever care. And just in case someone really cares, they'll file a bug, having 365 days to make it real and not overload garbage on the BTS. -- David Moreno Garza [EMAIL PROTECTED] | http://www.damog.net/ [EMAIL PROTECTED] | GPG: C671257D Pues aquí, echando la weba: Es la vida del filósofo. -Polo
Re: wnpp situation
Nathanael Nerode [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: There is no good reason to close old RFPs unless the upstream source has diseappeared. The spectacular amount of clutter they provide -- rendering the wnpp bug list unreadable unless you ignore them all -- combined with their total uselessness? Seems like a pair of good reasons to me. Count me in favor of deleting RFPs more than a year and a half old. I have no problem with deleting RFPs because you know they don't make sense any more. But mere time isn't necessarily a good test here, the way it is for the other wnpp transitions. However, it's not something I feel particularly strongly about. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Thomas Bushnell BSG [EMAIL PROTECTED] writes: There is no good reason to close old RFPs unless the upstream source has diseappeared. Old ITPs should be turned into RFPs, not closed. I don't agree. If there's no current interest in having the package created, having the bug open actually wastes people's time. Right now, it's just not particularly sane to go through the RFP list and try to package things people have requested, since more often than not it was requested years ago and the person asking for it would no longer even want it. It's also a ton of work to constantly check if upstream is still there, if the package has been superseded, if something else in Debian now does thes same job, etc. Closing after a year sounds great to me. If there's ongoing interest, the bug will be opened again. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
David Moreno Garza @ 2005-09-13 (Tuesday), 18:06 (-0500) Talking with adn on IRC, I've decided to launch an script that will close every opened ITP and RFP bug on the BTS with a lifetime greater than 600 days by tonight Wouldn't it make more sense to close bugs that hasn't recieved more info in X days than bugs that had their initial post in Y days? Some packages are trickier than others to create and may therefor take more time. As long as people post to the bug, there is some interest. -- /Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
On Tue, Sep 13, 2005 at 12:47:33AM +0200, Nico Golde wrote: Hi, If you go through the list of wnpp bugs you will see alot of open bugs which are very very old. Especially the RFPs. What about closing an RFP bug automatically after the third semi automatic notice mail which is sent to the BTS entry? Or have a cron job that automatically closes them after a period of inactivity? With or without three automatic nags? regards Andrew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Hi, * Andrew Pollock [EMAIL PROTECTED] [2005-09-13 01:07]: On Tue, Sep 13, 2005 at 12:47:33AM +0200, Nico Golde wrote: Hi, If you go through the list of wnpp bugs you will see alot of open bugs which are very very old. Especially the RFPs. What about closing an RFP bug automatically after the third semi automatic notice mail which is sent to the BTS entry? Or have a cron job that automatically closes them after a period of inactivity? With or without three automatic nags? Yes that another possibility. I think the only way to handle RFPs which makes sense is to give a period of time (a year or so) and if the bug has not been retilted to ITP in this time delete the RFP. In a year many things (licenses too :) can change in software development so if someone is interrested in a piece of software he can write a wnpp again. If nothing changes in this period of time upstream is inacive and the software shouldn't be packaged. Regards Nico -- Nico Golde - JAB: [EMAIL PROTECTED] | GPG: 0x73647CFF http://www.ngolde.de | http://www.muttng.org | http://grml.org VIM has two modes - the one in which it beeps and the one in which it doesn't -- encrypted mail preferred pgpsJnZAo1eeg.pgp Description: PGP signature
Re: wnpp situation
* Nico Golde [EMAIL PROTECTED] [050913 00:47]: Especially the RFPs. What about closing an RFP bug automatically after the third semi automatic notice mail which is sent to the BTS entry? What is the purpose of this mail? Either there is someone interested in packaging it, or you won't find someone sooner with Please someone do something or we will close the bug mails. And if we have a definite RFPs are closed after n month inactivity policy, everyone can easily calculate, when such a bug is closed. Close RFP after ... uhm... let's say 1 year inactivity and send the submitter an apology, that we couldn't find a volunteer for the requested package, should to very well. Yours sincerely, Alexander -- http://learn.to/quote/ http://www.catb.org/~esr/faqs/smart-questions.html signature.asc Description: Digital signature
Re: wnpp situation
ti, 2005-09-13 kello 01:45 +0200, Alexander Schmehl kirjoitti: Close RFP after ... uhm... let's say 1 year inactivity and send the submitter an apology, that we couldn't find a volunteer for the requested package, should to very well. There was a discussion about closing old RFPs on -project in the middle of July (around the 13th, I think). I really should get acting on the consensus of that thread and close the old RFPs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: wnpp situation
Andrew Pollock [EMAIL PROTECTED] writes: On Tue, Sep 13, 2005 at 12:47:33AM +0200, Nico Golde wrote: Hi, If you go through the list of wnpp bugs you will see alot of open bugs which are very very old. Especially the RFPs. What about closing an RFP bug automatically after the third semi automatic notice mail which is sent to the BTS entry? Or have a cron job that automatically closes them after a period of inactivity? With or without three automatic nags? Or don't even open RFP bugs in the first place because they're thoroughly useless? -- Society is never going to make any progress until we all learn to pretend to like each other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: WNPP pages are now over one month out of date.
On Tue, Dec 10, 2002 at 03:24:02AM +1100, Andrew Lau wrote: I just remembered that the WNPP www pages [1] have been stale for one month and one day now. Their last update was on November 9, and no one has yet looked into bug #171393: WNPP pages are severely out of date. Update mechanism broken? which I also filed. Anyone know what the current situation is? I had a quick look at wml_run.log, and there were a few complaints about very badly formatted wnpp bug titles. I've fixed those, so maybe that will improve matters. Looking at the code, wnpp.pl is supposed to avoid printing those messages to stderr when the host is klecker.debian.org, but this fails for some reason. Assuming my fix solves it, somebody needs to look into that to stop it happening in future. -- Colin Watson [EMAIL PROTECTED]
Re: WNPP pages are now over one month out of date.
* Colin Watson [EMAIL PROTECTED] [2002-12-09 17:22]: Looking at the code, wnpp.pl is supposed to avoid printing those messages to stderr when the host is klecker.debian.org, but this fails for some reason. Because $host is not initialized. I wonder where it should come from. -- Martin Michlmayr [EMAIL PROTECTED]
Re: WNPP pages are now over one month out of date.
On Mon, Dec 09, 2002 at 08:38:49PM +0100, Martin Michlmayr wrote: Because $host is not initialized. I wonder where it should come from. IIRC, it was set in the script. I don't recall the particular reason why those messages weren't printed when ran on klecker, though. -- Marcelo
Re: WNPP pages are now over one month out of date.
* Marcelo E. Magallon [EMAIL PROTECTED] [2002-12-09 21:37]: IIRC, it was set in the script. I don't recall the particular reason why those messages weren't printed when ran on klecker, though. Err, cause those messages break the build.
Re: WNPP pages are now over one month out of date.
On Mon, Dec 09, 2002 at 09:37:53PM +0100, Marcelo E. Magallon wrote: Because $host is not initialized. I wonder where it should come from. IIRC, it was set in the script. It must have gone down the drain when I removed another chunk of code that relied on the hostname without any need. I don't recall the particular reason why those messages weren't printed when ran on klecker, though. Probably for exactly this purpose, to avoid breaking the build. I don't recall seeing that code, which is odd... I wouldn't have removed the hostname stuff if I had noticed that it was used elsewhere. -- 2. That which causes joy or happiness.
Re: wnpp page down?
J.E. Starr wrote: Hi all, As of a of minutes ago, the wnpp page shows no packages up for adoption, none orphaned, none withdrawn, none being worked on, etc. This is most probably a temporary or permanent problem in the LDAP access method on klecker. Please report to debian-www@lists.debian.org next time so somebody can look at it (if it won't be fixed with the next automatic rebuild) Regards, Joey -- It's practically impossible to look at a penguin and feel angry. Please always Cc to me when replying to me on the lists.
Re: wnpp still down
MEM == Marcelo E Magallon [EMAIL PROTECTED] writes: Nicolas SABOURET [EMAIL PROTECTED] writes: Just to inform that the web page devel/wnpp still doesn't work. I don't know wether sby is dealing with that already or not. The WNPP pages use the LDAP frontend to the BTS, which has been affected by a small change in the BTS database[0]. Last weekend I mailed Ben Collins a pseudo patch to fix the affected script but I think he's on vacation as I haven't got any sort of ack. [0] A directory is no longer a directory but a symlink Today the WNPP is still broken. Somebody can do something ? I want to check the WNPP before doing ITP. Christian
Re: wnpp still down
I think bugs.debian.org/wnpp reports correctly the list of packages. El 04 Sep 2001 a las 10:11AM +0200, Christian Marillat escribio: MEM == Marcelo E Magallon [EMAIL PROTECTED] writes: Nicolas SABOURET [EMAIL PROTECTED] writes: Just to inform that the web page devel/wnpp still doesn't work. I don't know wether sby is dealing with that already or not. The WNPP pages use the LDAP frontend to the BTS, which has been affected by a small change in the BTS database[0]. Last weekend I mailed Ben Collins a pseudo patch to fix the affected script but I think he's on vacation as I haven't got any sort of ack. [0] A directory is no longer a directory but a symlink Today the WNPP is still broken. Somebody can do something ? I want to check the WNPP before doing ITP. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Andres Seco Hernandez- [EMAIL PROTECTED] MCP ID 445900 - http://andressh.alamin.org GnuPG public information: pub 1024D/3A48C934 E61C 08A9 EBC8 12E4 F363 E359 EDAC BE0B 3A48 C934 -- Alamin GSM SMS Gateway - http://www.alamin.org Debian GNU/Linux - http://www.debian.org Grupo de Usuarios de GNU/Linux de Guadalajara y alrededores - http://gulalcarria.sourceforge.net -- pgp9sziibxhED.pgp Description: PGP signature
Re: wnpp still down
ASH == Andres Seco Hernandez [EMAIL PROTECTED] writes: I think bugs.debian.org/wnpp reports correctly the list of packages. Yes, but a search in wnpp pages was more easy. Christian
Re: wnpp still down
Christian Marillat [EMAIL PROTECTED] writes: mailed Ben Collins a pseudo patch to fix the affected script but I think he's on vacation as I haven't got any sort of ack. s/pseudo/proper, one line/; s/ but/./; s/on/back from/; s/as I/but I still/; Today the WNPP is still broken. Somebody can do something ? AFAIUI, Ben Collins. A couple of mails from him have showed up here and there, so I think he's reading his mail again. After sending him two mails about the problem, I'd consider a third one rude. -- Marcelo | No matter how fast light travels it finds the darkness [EMAIL PROTECTED] | has always got there first, and is waiting for it. | -- (Terry Pratchett, Reaper Man)
Re: wnpp: ITP: gq - gtk ldap client
* Ond?ej Sur? in wnpp: ITP: gq - gtk ldap client dated 2001/04/27 * 09:48 wrote: Package: wnpp Version: N/A Severity: wishlist GQ is a GTK-based LDAP client. Features include: What's wrong with the current gq package? $ apt-cache show gq Package: gq Priority: optional Section: net Installed-Size: 281 Maintainer: Cord Beermann [EMAIL PROTECTED] Architecture: i386 Version: 0.4.0-1 Depends: libc6 (= 2.2.1), libglib1.2 (= 1.2.0), libgtk1.2 (= 1.2.8-3), libldap2 (= 2.0.2-2), xlibs (= 4.0.1-11) Filename: pool/main/g/gq/gq_0.4.0-1_i386.deb Size: 93850 MD5sum: ee802c5db7cce9d582a67c4d9caad234 Description: GTK-based LDAP client GQ is GTK+ LDAP client and browser utility. It can be used for searching LDAP directory as well as browsing it using a tree view. Features include: - browse and search modes - LDAPv3 schema browser - template editor - edit and delete entries - add entries with templates - export subtree or whole server to LDIF file - use any number of servers - search based on single argument or LDAP filter - TLS support for LDAPv3 -- creaky halls pgp3gUeJ3892i.pgp Description: PGP signature
Re: wnpp: ITP: gq - gtk ldap client
What's wrong with the current gq package? Sorry, I hadn't noticed... I will close that bug. I appologies. -- Ondej Sur [EMAIL PROTECTED] Globe Internet s.r.o. http://globe.cz/ Tel: +420235365000 Fax: +420235365009 Plnikova 1, 162 00 Praha 6 Mob: +420605204544 ICQ: 24944126 Mapa: http://globe.namape.cz/ GPG fingerprint: CC91 8F02 8CDE 911A 933F AE52 F4E6 6A7C C20D F273
Re: wnpp: ITP: gq - gtk ldap client
[EMAIL PROTECTED] (Ondøej Surý) writes: Package: wnpp Version: N/A Severity: wishlist GQ is a GTK-based LDAP client. Features include: - browse and search modes - LDAPv3 schema browser - template editor - edit and delete entries - add entries with templates - export subtree or whole server to LDIF file - use any number of servers - search based on single argument or LDAP filter - TLS support for LDAPv3 Licence is GPLv2, homesite is http://biot.com/gq/ It is already in debian. $ apt-cache show gq Package: gq Priority: optional Section: net Installed-Size: 281 Maintainer: Cord Beermann [EMAIL PROTECTED] Architecture: i386 Version: 0.4.0-1 Depends: libc6 (= 2.2.1), libglib1.2 (= 1.2.0), libgtk1.2 (= 1.2.8-3), libldap2 (= 2.0.2-2), xlibs (= 4.0.1-11) Filename: pool/main/g/gq/gq_0.4.0-1_i386.deb Size: 93850 MD5sum: ee802c5db7cce9d582a67c4d9caad234 Description: GTK-based LDAP client GQ is GTK+ LDAP client and browser utility. It can be used for searching LDAP directory as well as browsing it using a tree view. Features include: - browse and search modes - LDAPv3 schema browser - template editor - edit and delete entries - add entries with templates - export subtree or whole server to LDIF file - use any number of servers - search based on single argument or LDAP filter - TLS support for LDAPv3 Please read http://lists.debian.org/debian-devel-0104/msg00773.html -- Jérôme Marant
Re: wnpp bug reports
On Fri, Dec 22, 2000 at 12:58:54PM -0500, Bob Hilliard wrote: Is there any way to submit an ITP bug on WNPP, so that the bug number appears in the copy to -devel? Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields. -- Digital Electronic Being Intended for Assassination and Nullification
Re: wnpp bug reports
Josip Rodin [EMAIL PROTECTED] writes: On Fri, Dec 22, 2000 at 12:58:54PM -0500, Bob Hilliard wrote: Is there any way to submit an ITP bug on WNPP, so that the bug number appears in the copy to -devel? Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields. When I have done this, the report shows up on -devel the same as I submitted it - the Bug Number doesn't appear. -- _ |_) _ |_ Robert D. Hilliard [EMAIL PROTECTED] |_) (_) |_) 1294 S.W. Seagull Way [EMAIL PROTECTED] Palm City, FL USA GPG Key ID: 390D6559 PGP Key ID: A8E40EB9
Re: wnpp bug reports
On Fri, Dec 22, 2000 at 06:03:28PM -0500, Bob Hilliard wrote: Josip Rodin [EMAIL PROTECTED] writes: Yes, put -devel in Cc: or (X-Debbugs-Cc:) fields. When I have done this, the report shows up on -devel the same as I submitted it - the Bug Number doesn't appear. If you CC it it will - that's just a regular mailing list posting. If you use X-Debbugs-Cc it will go through the BTS first. -- Mark Brown mailto:[EMAIL PROTECTED] (Trying to avoid grumpiness) http://www.tardis.ed.ac.uk/~broonie/ EUFShttp://www.eusa.ed.ac.uk/societies/filmsoc/ pgpEPFtochrQo.pgp Description: PGP signature
Re: WNPP now on the BTS
Hi,
Anthony Towns aj@azure.humbug.org.au writes:
*sip*
After reading and rereading the Developer's Reference and the QA
docs, I did away with that oh-not-so-good WTO/ITO classifications and
added a RFA, as per your suggestion. Attached is the intended
documentation for the WNPP system.
Marcelo Work-Needing and Prospective Packages, WNPP for short, is a pseudo
package on the Debian Bug Tracking System (BTS) and its intention is to
track closely the real status of such things as prospective packages in
Debian and packages in need of new maintainers. Since it uses the BTS,
every developer is already familiar with the technical details, such as
submission of new information, modification of information or closing
of pending requests. On the other hand, in order to achieve the
highest level of automatization, some procedures have to be observed.
In order to submit new information, a bug has to be filed against the
wnpp pseudo package for each (prospective) package that is affected.
The format of the submission should be like this:
To: [EMAIL PROTECTED]
Subject: {TAG}: {package name} -- {short package description}
Package: wnpp
Severity: {see below}
{Some information about the package. If this is an ITP or RFP an
URL where the package can be downloaded from is required, as well
as information concerning its license.}
The tags to be used and their corresponding severities are:
Onormal The package has been Orphaned. It needs a new
maintainer as soon as possible. If the package
as a Priority of standard, required or essential,
the severity should be set to important. If the
package remains in this orphaned state after one
month, the severity will be raised to important and
the ftp maintainers will be asked to move it to
project/orphaned.
RFA normal This is a 'Request for Adoption'. Due to lack of
time, resources, interest or something similar, the
current maintainer is asking for someone else to
maintain this package. Meanwhile the package is
being maintained, but perhaps not in the best
possible way. In short: the package needs a new
maintainer.
ITP wishlist Someone 'Intents To Package' this. Please submit
a package description along with copyright and URL
in such a report.
RFP wishlist This is a 'Request For Package'. Someone has found
an interesting piece of software and would like
someone else to package it for Debian and upload
it to the archives. Please submit a package
description along with copyright and URL in such
a report.
Wwishlist The package has been withdrawn and can be found
in project/orphaned. Such reports should not be
submited directly, but instead should be a product
of retitling and downgrading 'O' reports.
The procedures for closing this bugs are as follow:
Oadopt the package, upload to the main archive and close this
bug once the package has been installed. If you are going
to do this, retitle the bug with 'ITA:' + the old title.
This is necessary in order for other people to know the
package is being adopted and to prevent its automatic removal
from the archive.
RFA adopt the package, upload to the main archive and close this
bug once the package has been installed. If you are going
to do this, retitle the bug with 'ITA:' + the old title.
This is necessary in order for other people to know the
package is being adopted.
If you as the package maintainer decide to Orphan the package,
please retitle as necessary. If you withdraw your request,
please close the bug.
ITP package the software, upload to the main archive and close
this bug once the package has been installed.
If you change your mind, and no longer want to package this,
either close the bug or retitle and reclasify it as RFP, as
you see fit.
RFP package the software, upload to the main archive and close
this bug once the package has been installed. If you are
going to do this, retitle the bug as 'ITP:' + the old title.
Wadopt the package, upload to the main archive and close this
bug once the package has been installed. If you are going
to do this, retitle the bug with 'ITA:' + the old title.
This is necessary in order for other people to
Re: WNPP now on the BTS
On Sat, Aug 19, 2000 at 09:10:50PM +0200, Marcelo E. Magallon wrote: Attached is the intended documentation for the WNPP system. I've formatted this text with html/wml and put it in the web pages. It should appear shortly as http://www.debian.org/devel/wnpp . I'll make a few other changes to it, to indicate the status of [EMAIL PROTECTED] address etc... suggestions welcome. The FTP copy of the old wnpp page will be removed, and the WWW copy will be updated to point at the new place. -- Digital Electronic Being Intended for Assassination and Nullification
Re: wnpp@debian.org still alive ?
On Fri, Mar 31, 2000 at 10:08:57AM +0200, Gregor Hoffleit wrote: Is [EMAIL PROTECTED] still alive and maintained ? During the last few months, I sent several ITP's and a request to remove a package from the list to this address, but AFAICS all of them were ignored. E.g. I requested to remove dgs from the list of packages needing a new maintainer, and I sent an ITP for WorldPilot. We at WNPP (Johnie Ingram and me) don't quite maintain the PP part of WNPP anymore. We decided that it was pointless because the database used is hard to maintain, slow to generate pages, and also a bit buggy. It is planned to integrate the current WNPP list into the list on the QA site (http://qa.debian.org/wnpp.html), but we'd need Raphael or someone else to do large modifications to the pgsql database and the perl scripts for the mail bot... unfortunately it hasn't yet been done. Having said that, I must admit I don't know why wasn't the dgs package entry updated. I'll remove it right away, sorry. -- Digital Electronic Being Intended for Assassination and Nullification
Re: WNPP
Michael == Michael Vogt [EMAIL PROTECTED] writes: Michael If you like the package :-) Of course. The package lacks Michael a good example /etc/aide.conf. If someone has a nice Michael example, please send it to me. I will include it in the Michael package. Let me know once this gets in and I'll happilty orpah tripwire. :) -- Stephen If I claimed I was emporer just cause some moistened bint lobbed a scimitar at me they'd put me away
Re: WNPP\
I've already got it packaged. I posted to debian-devel about it some time ago. I'm working out a couple of minor issues with the potato binary package, the slink one's up. See ftp.madhack.com/debian. I plan to post some info on the postinst problem I'm running into tomorrow, when I have better access to my potato system at work. On Mon, Mar 27, 2000 at 12:39:52PM -0800, Joey Hess wrote: Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's a free tripwire replacement. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Mike Markley [EMAIL PROTECTED] PGP: 0xA9592D4D 62 A7 11 E2 23 AD 4F 57 27 05 1A 76 56 92 D5 F6 GPG: 0x3B047084 7FC7 0DC0 EF31 DF83 7313 FE2B 77A8 F36A 3B04 7084 ... The prejudices people feel about each other disappear when then get to know each other. - Kirk, Elaan of Troyius, stardate 4372.5
Re: WNPP
On Tue, Mar 28, 2000 at 08:58:38AM +0200, Radovan Garabik wrote: On Mon, Mar 27, 2000 at 08:27:29PM -0500, Brian Almeida wrote: ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. Strange... I read everywhere that US export restrictions are now gone. (e.g. just a minute ago the announcement of redhat 6.2) New regulations were adopted in January that lift some of the restrictions on cryptographic software, but it's still treated specially by U.S. law. What's more, those changes were deliberately temporary, and are up for review next month and may be revoked or replaced. It is too soon to tell whether the U.S. is going to join the free world when it comes to crypto or not. Louis Freeh (Director of the FBI) testified before Congress this week, and muttered ominously about increases in cyber-crime. You can rest assured that he trotted out his usual apocalyptic horsemen of child pornography, illegal drug trafficking, and terrorism on U.S. soil to try and scare Congress into permitting universal warrantless wiretaps, key escrow, and other acts of urination on the Fourth Amendment. -- G. Branden Robinson|The errors of great men are venerable Debian GNU/Linux |because they are more fruitful than the [EMAIL PROTECTED] |truths of little men. roger.ecn.purdue.edu/~branden/ |-- Friedrich Nietzsche pgpFFu2lBWToW.pgp Description: PGP signature
Re: WNPP
I'll do this, since it relates to my work. :-) On Mon, Mar 27, 2000 at 12:39:52PM -0800, Joey Hess wrote: Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's a free tripwire replacement. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Brian Almeida Debian Developer | http://www.debian.org Linux Systems Engineer @ Winstar | http://www.winstar.com
Re: WNPP
...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. On Mon, Mar 27, 2000 at 08:12:37PM -0500, Brian Almeida wrote: I'll do this, since it relates to my work. :-) On Mon, Mar 27, 2000 at 12:39:52PM -0800, Joey Hess wrote: Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's a free tripwire replacement. -- Brian Almeida Debian Developer | http://www.debian.org Linux Systems Engineer @ Winstar | http://www.winstar.com
Re: WNPP
On Mon, Mar 27, 2000 at 12:39:52PM -0800, Joey Hess wrote: Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's a free tripwire replacement. I packed aide for my personal needs some weeks ago. I just uploaded a polished version to http://members.xoom.com/mydebs/debian/aide. see shy jo bye Michael -- GPG Fingerprint = EA71 B296 4597 4D8B 343E 821E 9624 83E1 5662 C734 /\ o \ / ASCII RIBBON CAMPAIGN /|\ XAGAINST HTML MAIL / \ o
Re: WNPP
Joey Hess writes:
Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's
a free tripwire replacement.
This was mentioned a week or two ago and at least two people
volunteered. I might be interested too. I've not packaged anything
yet, though, and I am not a Debian developer.
--
#!/usr/bin/perl -w -- # Ari Makela, [EMAIL PROTECTED], http://www.iki.fi/hauva/
use strict;my $s='I am just a poor bear with a startling lack of brain.';my $t=
crypt($s,substr($s,0,2));$t=~y#IEK65c4qx AR#J o srtahuet#;$t=~s/hot/not/;my
@v=split(//,$t);push(@v,split(//,reverse('rekcah lreP')));foreach(@v){print;}
Re: WNPP
On Mon, Mar 27, 2000 at 08:27:29PM -0500, Brian Almeida wrote: ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. Strange... I read everywhere that US export restrictions are now gone. (e.g. just a minute ago the announcement of redhat 6.2) On Mon, Mar 27, 2000 at 08:12:37PM -0500, Brian Almeida wrote: I'll do this, since it relates to my work. :-) On Mon, Mar 27, 2000 at 12:39:52PM -0800, Joey Hess wrote: Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's a free tripwire replacement. -- --- | Radovan Garabik http://melkor.dnp.fmph.uniba.sk/~garabik/ | | __..--^^^--..__garabik @ melkor.dnp.fmph.uniba.sk | --- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread!
Re: WNPP
Brian Almeida [EMAIL PROTECTED] writes: ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. So dpkg must be moved to non-us because it contains an implementation of a cryptographic hashing algorithm (MD5)? - Ruud de Rooij. -- ruud de rooij | [EMAIL PROTECTED] | http://ruud.org
Re: WNPP
Michael Vogt wrote: I packed aide for my personal needs some weeks ago. I just uploaded a polished version to http://members.xoom.com/mydebs/debian/aide. Cool! Do you want me to sponsor this in? -- see shy jo
Re: WNPP
On Mon, Mar 27, 2000 at 11:25:46PM -0800, Joey Hess wrote: Michael Vogt wrote: I packed aide for my personal needs some weeks ago. I just uploaded a polished version to http://members.xoom.com/mydebs/debian/aide. Cool! Do you want me to sponsor this in? If you like the package :-) Of course. The package lacks a good example /etc/aide.conf. If someone has a nice example, please send it to me. I will include it in the package. see shy jo bye Michael -- GPG Fingerprint = EA71 B296 4597 4D8B 343E 821E 9624 83E1 5662 C734 /\ o \ / ASCII RIBBON CAMPAIGN /|\ XAGAINST HTML MAIL / \ o
Re: WNPP
At 20:27 -0500 2000-03-27, Brian Almeida wrote: ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. Hash algorithms aren't (and haven't ever been) export controlled. -- Joel Klecker (aka Espy)Debian GNU/Linux Developer URL:mailto:[EMAIL PROTECTED] URL:mailto:[EMAIL PROTECTED] URL:http://web.espy.org/ URL:http://www.debian.org/
Re: WNPP
On Mon, Mar 27, 2000 at 08:27:29PM -0500, Brian Almeida wrote: ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. On Mon, Mar 27, 2000 at 08:12:37PM -0500, Brian Almeida wrote: Hasing is fine, else glibc, openldapd, PAM, etc..would have to be removed for their password hashing. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: WNPP
On Mon, Mar 27, 2000 at 08:27:29PM -0500, Brian Almeida wrote: ...or maybe not. It's got cryptographic hashing algos (tiger, sha1, etc), so I probably can't package it due to wonderful US laws. Drat. actually the charming US laws appear to be fixed, at least for Free software. The kernel is going to be getting stong crypto merged in soon apparently, and Redhat is now shipping GnuPG and such with there dist, so it seems to apply to binaries too (non commercial anyway) On Mon, Mar 27, 2000 at 08:12:37PM -0500, Brian Almeida wrote: I'll do this, since it relates to my work. :-) On Mon, Mar 27, 2000 at 12:39:52PM -0800, Joey Hess wrote: Someone should package AIDE (http://www.cs.tut.fi/~rammer/aide.html). It's a free tripwire replacement. -- Brian Almeida Debian Developer | http://www.debian.org Linux Systems Engineer @ Winstar | http://www.winstar.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Ethan Benson http://www.alaska.net/~erbenson/ pgp49fUG5IAmR.pgp Description: PGP signature
Re: WNPP: working on xmbdfed
Hello Frederic! On 26 Dec 1997, Frederic Lepied wrote: I'm working on xmbdfed which is a powerfull X11 font editor. It works with lesstif. [...] PS: Anthony could you setup a development package for freetype ? I have to build xmbdfed from your sources... It is finally here! :) Thanks to a libtool patch from Japan, posted on the freetype-devel mailing list, the shared library and development packages are packaged for Debian. They are sitting in Incoming now: look for freetype*1998.01.06*.deb. :) Cheers, Anthony -- Anthony Fok Tung-Ling[EMAIL PROTECTED] Civil Engineeringhttp://www.ualberta.ca/~foka/ University of Alberta, CanadaKeep smiling! *^_^* -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: WNPP: working on xmbdfed
On 26 Dec 1997, Frederic Lepied wrote: I'm working on xmbdfed which is a powerfull X11 font editor. It works with lesstif. [snip] PS: Anthony could you setup a development package for freetype ? I have to build xmbdfed from your sources... Thanks for the note! I'll see what I can do! I haven't made a development package for freetype yet because I have yet to learn how. I will see if I could set up a (lib)freetype and (lib)freetype-dev before the new year. However, if you are in a hurry, you might like to link xmbdfed statically for now. grin Sorry for the inconvenience! :) Have a Happy New Year! (in a few days, that is. :) Anthony -- Anthony Fok Tung-Ling[EMAIL PROTECTED] Civil Engineeringhttp://www.ualberta.ca/~foka/ University of Alberta, CanadaKeep smiling! *^_^* -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
