Re: MiniDebConf BH 2024: contribua para financimento coletivo
On Sun, Feb 18, 2024 at 07:24:37PM -0300, Paulo Henrique de Lima Santana wrote: > Olá pessoal, > > Colocamos como meta de arredação pelo menos o valor de uma cota Ouro de > patrocínio, que é de R$ 3.000,00. > > Já alcançamos 53% desse valor! (R$ 1.610,00). > > Vamos bater essa meta!? > > Vamos ajudar e mostrar que a comunidade brasileira apoia o mais importante > evento nacional do Debian no Brasil? :-) > > Veja no link abaixo como doar e tenha seu nome listado na página de doares: > > https://bh.mini.debconf.org/doacoes/ > > Abraços, > Oi, Paulo. Infelizmente a data não vai funcionar pra mim por motivos pessoais. Mas gostaria de tentar conseguir algum patrocínio. Você tem o material em inglês? Abraços. Cascardo. > Em 21/01/2024 12:28, Paulo Henrique de Lima Santana escreveu: > > Olá, > > > > Já está rolando a inscrição de participante e a chamada de atividades > > para a MiniDebConf Belo Horizonte 2024, que acontecerá de 27 a 30 de > > abril no Campus Pampulha da UFMG. Este ano estamos ofertando bolsas de > > alimentação, hospedagem e passagens para contribuidores(as) ativos(as) > > do Projeto Debian. > > > > Mais informações: > > https://debianbrasil.org.br/blog/minidebconf-bh-2024-abertura-de-inscricao-e-chamada-de-atividades > > > > Patrocínio: > > === > > > > Para a realização da MiniDebConf, estamos buscando patrocínio financeiro > > de empresas e entidades. Então se você trabalha em uma empresa/entidade > > (ou conhece alguém que trabalha em uma) indique o nosso plano de > > patrocínio para ela. Lá você verá os valores de cada cota e os seus > > benefícios. > > > > Acesso o nosso plano de patrocínio em: > > https://bh.mini.debconf.org/patrocinio/seja-patrocinador > > > > Financiamento coletivo: > > === > > > > Mas você também pode ajudar a realização da MiniDebConf por meio do > > nosso financiamento coletivo! > > > > Faça uma doação de qualquer valor e tenha o seu nome publicado no site > > do evento como apoiador(a) da MiniDebConf Belo Horizonte 2024. > > > > Mesmo que você não pretenda vir a Belo Horizonte para participar do > > evento, você pode doar e assim contribuir para o mais importante evento > > do Projeto Debian no Brasil. > > > > Veja como doar: > > https://bh.mini.debconf.org/doacoes > > > > Contato: > > > > > > Qualquer dúvida, mande um email para cont...@debianbrasil.org.br > > > > Organização: > > > > > > - Comunidade Debian Brasil > > - Comunidade Debian MG > > - DCC/UFMG - Departamento de Ciência da Computação da UFMG > > > > Abraços, > > > > -- > Paulo Henrique de Lima Santana (phls) > Belo Horizonte - Brasil > Debian Developer > Site: http://phls.com.br > GPG ID: 0443C450 signature.asc Description: PGP signature
Accepted makedumpfile 1:1.6.6-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Dec 2019 10:50:47 -0300 Source: makedumpfile Architecture: source Version: 1:1.6.6-4 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Launchpad-Bugs-Fixed: 1741860 Changes: makedumpfile (1:1.6.6-4) unstable; urgency=medium . * Let the kernel decide the crashkernel offset for ppc64el (LP: #1741860) * kdump-config: implement try-reload * udev: hotplug: use try-reload * Set Rules-Requires-Root to no Checksums-Sha1: 07a277fd87845716a3f4c2265b2ccbba66cd6e76 2442 makedumpfile_1.6.6-4.dsc d35f221d2f2574506cc539c912fe8eaf1d633f5e 36420 makedumpfile_1.6.6-4.debian.tar.xz Checksums-Sha256: 3f1930756c081ee7e5d87b0968bd7244ae05edee32e7fb7598c0f81de7da892c 2442 makedumpfile_1.6.6-4.dsc cd5b5401c45cb873ac840c97d1a2963f60bfd91303d089ebf67857cfc36adb78 36420 makedumpfile_1.6.6-4.debian.tar.xz Files: b81f2bcda488c2c2daa9370e7606c586 2442 devel optional makedumpfile_1.6.6-4.dsc 3192f7f87dc80bf4c0d28f23b5297cf0 36420 devel optional makedumpfile_1.6.6-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE34E7Im3TmixTD299CrplA3L9lXEFAl36MMQUHGNhc2NhcmRv QGRlYmlhbi5vcmcACgkQCrplA3L9lXGV1Q/9GSHP88EoFT+R9GjMPESSL9YfAW6y bnZujaEa4tOLPBzHWvgix94tvR9NMlfn36u48rMc36XCB3ODE2h/g1ULMUYq9t9o d2vSQk9nrKVLcezAAmcIF/KE8vWbbkRG9AZdKOE4SJJXG5O6vi75lO1gmCNPPN2f idFDYBbhyjnCkXmPX0ZL9iFvkYnlELtgA4XIFaXKviwW5W5WmOcTSZK8IuiLPUR7 Jxxk7/cj5SHm50l85CMb+9UWM1Kik/i37Pxmznc2DlqA9W65TcMA6O38IPf2FT/a diE3Yqttolv8PB7XKossrCGiiR2cG7jnm+XqjecQW7fI0nF6j8AxIEL9A7D8Y2Vd lLRz2TX5FifWhY/xHCiGfJceVIuYejBSwZ88o3wsQHJGN/YJ3jlIG1/WUwoDEIHy o6DpETYRWVGjJq8ZGwZ6jcdhXPTBbdKdYh79sXuPCaDJD1RU2jLvgIHOBqGMFYbs yOt7xUiHaAFcrrQB5uyWxW60xXo1l3v4VE4Bu/gQMi1olrk+PnuN46NwVwCUNedf W3U7cW6NyCeKa6G8hU6r/ORcO13jbZxBQFcLYWeX0lUTuzZ4Yh1zAK7OdGAIBGWE hRrCTo0mIijsbMQluAYFZWQHpcxBs9vhfDxlHSsF35p9wvBtFy8H3soLgJhG+UTy miDBJhR29TwecIg= =rgUu -END PGP SIGNATURE-
Accepted acpi-override 0.1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 31 Oct 2019 16:32:35 -0300 Source: acpi-override Binary: acpi-override-initramfs Architecture: source all Version: 0.1 Distribution: unstable Urgency: medium Maintainer: Thadeu Lima de Souza Cascardo Changed-By: Thadeu Lima de Souza Cascardo Description: acpi-override-initramfs - initramfs-tools hook to override ACPI tables Changes: acpi-override (0.1) unstable; urgency=medium . * Upload to debian. Checksums-Sha1: d16b22da80904af3b4637f09a4f256261f7b5b73 1470 acpi-override_0.1.dsc 12a28acfe78fc914f581c9808a0aeb03cca28d40 7760 acpi-override_0.1.tar.xz 3db73102bfe3dfa88fe6876a0d7aca004a5bc96a 2456 acpi-override-initramfs_0.1_all.deb ac42fee9e1b4077e059f6b0706b4264e13701fb5 6546 acpi-override_0.1_amd64.buildinfo Checksums-Sha256: 99f059b8901c1b0544ce5c0c79f2fa95bcb6473ba3aecc40d27cbd376400b58a 1470 acpi-override_0.1.dsc 9baaa12156c6623298bb4f2b1917d79afe81802cb9d7b592a178976e9f3aa150 7760 acpi-override_0.1.tar.xz 6919c4232876aef5202e2f7d65df08e5168b6da3c584ada784fe8f79568edf70 2456 acpi-override-initramfs_0.1_all.deb cc40630a4b66d3bc1bdc1123fe9dd93c7c972543f9bfaeab42768ddb5ba5d826 6546 acpi-override_0.1_amd64.buildinfo Files: a1f7c509bc62487cb83e4fe95a2f8eda 1470 admin optional acpi-override_0.1.dsc c35d2061c56641e356392d6011bd652c 7760 admin optional acpi-override_0.1.tar.xz 074167fe00f7354c1ce7be69bbfd74e9 2456 admin optional acpi-override-initramfs_0.1_all.deb 57df3c898face7694b0acb9ca3481fb8 6546 admin optional acpi-override_0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAl27WJ0ACgkQCrplA3L9 lXFRRg/+IxZwzMVj7WWIxeT0WXzl6/XFjmQUISdPD4MSJoZDiZDxyT2R9Q+9Frkl xK8iD9X3d3OFfYtE01Uyst+d56vovnegNGtywRxCofjKqszk84odUMZ1fAxnrwWi +pTi62aJjuDM8ejWz0OdwUBeX8r01m8T+KcBspFY7zyVqqVH5IK3HpRTxmB5LwqN 0csG5VihJVcqVnnxERI7Ugrg7/jq82u7zgFZI3KxQkJvs9FcLe9cUYmr+BD4ufJ9 ZS31PEafnKkS/SAreq4YvNwk32Q8IFaGcJJbik474gFylSXsAroVQhSCQMppGADM qsHyyqJaT6bcuEf/Uh5d6+ijMxVxXv2bOwwVZj1yGJiJpezfnqqx/d4h8bXi8SE3 UovIy+Er3vFhWSOSSPCFP3tR0n0Mf/4ZBDibYLNc4h+AiHTyLSS3hoqpo5nnfDHP /Z3ekazVUc8mmZ8whzfd5LQIEcOxqMr3DOGHV2pvjgCAx/f7IOsGpD09qsQSrCjU io+BhZMil0opJHvSiQk8hPTYtLIQXnK0+zEXDzRfh1M8TfW3qlIy79tufSLLt3ZT 4Qg28HJ8+3b1M/8NES8EN9w1WsfR7EFXhKkSewjdi/S8zm5BidInCJq+mUU3ESJO 1wGwevYyYd/D2fbhzbu5gM+b5muar5eWtj0/34OdH/C5DN5VB+0= =PwXE -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.6-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Sep 2019 01:00:16 + Source: makedumpfile Architecture: source Version: 1:1.6.6-3 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Changes: makedumpfile (1:1.6.6-3) unstable; urgency=medium . * Add a reload command. * Use kdump-config reload after cpu or memory hotplug. * Use reset_devices as a cmdline parameter. Checksums-Sha1: 4051ae21b3576dd718da74e3f0a6fc0e6aa0b1de 2442 makedumpfile_1.6.6-3.dsc 7484d692daf629e954fa8491511b06fd6f65d37d 36264 makedumpfile_1.6.6-3.debian.tar.xz Checksums-Sha256: 1d0b10f23af21ea416b86f6a54dfc653c986802219e5ea3f9e6683a68a4f7d39 2442 makedumpfile_1.6.6-3.dsc 0177fafe9bfa3d8491e2c1b481e1ef3356935bfd1e0b91a0a91e2582fd5c056c 36264 makedumpfile_1.6.6-3.debian.tar.xz Files: 488cc5e2cf023010395e0b3314cd 2442 devel optional makedumpfile_1.6.6-3.dsc d83a784c9fecf50e5d9d4a7092a52969 36264 devel optional makedumpfile_1.6.6-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE34E7Im3TmixTD299CrplA3L9lXEFAl2B98YUHGNhc2NhcmRv QGRlYmlhbi5vcmcACgkQCrplA3L9lXHQXhAAnEAVcdpDT2YpWsejgCmhrK/UFIGx wACVrrIGeTWjB4vatSyUBk6ZNYwQ2d+s3uPDMz4mCeNISGcjajcSWQsD5UqpyX3y kPDyYv5GWrYUkZRoUE6cCqqc/6GdenJQg6BK3V7PTZKHBLJt/qz/hmt2WSt6OeHA 8bypxvTTudMrOJIkfgV9omh/ih0CQGe+u7Xk1115r0ouqNjINOpZM8OdNtTb1URX wu3hrFQVezQJetigdtKveT63NvUh6gI8KyrRkPhB9AGlr2FP7UeJNJMcz88WoWwb gwRaahY8Cq/9DtcJHQ9kskH+HmZErC1zx373Cv20+YPFiAqCVEtKEDO6l/rKU0ML 2kc0AhwCdrHVrocvmUYKDywdExYb07d4A/dVPIP2wj7Ud6BKELr7PVF6u5JAHgpl Fts/ii+daOHGXcatTq9tD5aE9tu3Zb78YRjXlRCxeo+WcVM+/AljlBOZ01BHqwaY a9P7vK51/pkr/rEbCwlJzDfUgtOerlGI8bHyqZLSNPGpJgov987JWqERBpJeuC9u pXkK7hfgxtwOVchDXlL6UXyUt9n3uwRGggZT03Ytkxwk/JHOKqsLrb1xD9KTNM5S W55Iyz8hHX7migvv0/D2pa7Y1mT+ArH/2k9LJFMGwOj4JToxfrXlRifMn/KwSiV8 HjxH+5cvz699cm8= =6A8l -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.6-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 20 Jul 2019 11:25:01 -0300 Source: makedumpfile Architecture: source Version: 1:1.6.6-2 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Changes: makedumpfile (1:1.6.6-2) unstable; urgency=medium . [ Guilherme G. Piccoli ] * Add kdump retry/delay mechanism when dumping over network . [ Thadeu Lima de Souza Cascardo ] * Use a different service for vmcore dump. * Use maxcpus instead of nr_cpus on ppc64el. * Reload kdump when CPU is brought online. * Allow proper reload of kdump after multiple hotplug events. Checksums-Sha1: 01afbbcb627c09a821c1fe1b8967542ea699c4dd 2442 makedumpfile_1.6.6-2.dsc bc6a7102ded267d79377ff646498b4c1a10931b8 36192 makedumpfile_1.6.6-2.debian.tar.xz Checksums-Sha256: d0b38b1d19e19c35a5500ba12b29aa23c149c66d6a569ae8ef2ff1a42ceb6570 2442 makedumpfile_1.6.6-2.dsc 4e94cc1396f24b5ab33cf1a9e3866227a1b3f9e39469b402c02e896ae34daa34 36192 makedumpfile_1.6.6-2.debian.tar.xz Files: a519b40988936651f85da30dcaf7af74 2442 devel optional makedumpfile_1.6.6-2.dsc 2f11c8ade3825941f74eb1710b67bd0c 36192 devel optional makedumpfile_1.6.6-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE34E7Im3TmixTD299CrplA3L9lXEFAl0zJp0UHGNhc2NhcmRv QGRlYmlhbi5vcmcACgkQCrplA3L9lXFrFw/9EDimVKB7ggQbsxvqlOduhdjGEJjT DY9921iCEO726BHxsYBDHpsnQd5RItdgEyKOGBYGt5rzxkocT4z0eX6l91XwKYBf lr5LgMy9dLH5b+SAIR4q+AiTyVfEA3EQeOs9+B+at+sEnUnI9hop16efWG0cbrfN y0hU0GdPDBGnU370C6Lunt+RU/MEcxz58n/OB91Zg2VTcykdyMxFDX0AuHSvqPg1 8mSkSWfUDeGTeYe7Bsa1VxgIjTA49wQofcjd60qlfjHx3vqA+5p4FjNsqPtEyaiU RSvsf3kVXxTYAwaPaq66KtpLrv9wMi/IDDhkhLu0iRGDTtOl+gxnFQ7jtjGAyN71 KqRruRN69ZK670wrE+utzpodHxww6VJxurpbHD7r0JA4y/bF4arvAnxhKhexIqIR 2qPkGbeyJi9WJNAcDrtdky2Ps7ebkEFMvyBLGRPCvAB8YiOaJV5XPly3NxEnY531 IswGM13iOuRbZItvK9t6ckfA5kxKFsx5RjZr6whyopEPXnurXM06TmgmovhqXpUw iwA6QGXoGwaJafax6G08ZK5hZdeCuVQKzvGfdAcc0QsuvPWTRiT6ZM6VsqiXwC4M Ay75l6kpjQr1pMiFtb2q1xtUAIVSlAHghWaAvwfttTFgk1QDtY9k2fh7cyBT6LM8 eebH7/vSV/9/zGw= =vo/v -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.6-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 12 Jul 2019 16:24:14 -0300 Source: makedumpfile Architecture: source Version: 1:1.6.6-1 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Changes: makedumpfile (1:1.6.6-1) unstable; urgency=medium . * Update to new upstream version 1.6.6. Checksums-Sha1: da1a160a1b7435cfdac0096a3e4e2f7354e41319 2442 makedumpfile_1.6.6-1.dsc 68f5276d82091b54452f754aa41e2e8746f47814 193625 makedumpfile_1.6.6.orig.tar.gz 009f174c90a3bea523ad352ab71829886be5e553 35896 makedumpfile_1.6.6-1.debian.tar.xz Checksums-Sha256: 2ac01a07c00b80168f38f5022168d6daa9a26f48680bf75f530f309fe29d7307 2442 makedumpfile_1.6.6-1.dsc d007eec05cb14f0155f2d06a0d4dc70d321dbb2aec65fccdce953145c8230324 193625 makedumpfile_1.6.6.orig.tar.gz 10858dbc18923c6dc2cba1b393be10ced49468932fc2a72228c936ba783794f9 35896 makedumpfile_1.6.6-1.debian.tar.xz Files: 840f90068285f32c1fe273fe337b39a9 2442 devel optional makedumpfile_1.6.6-1.dsc 6fd632b97ad78d9a0a3b0f0989094064 193625 devel optional makedumpfile_1.6.6.orig.tar.gz 584b35df8251ff037da9684813ddd1f2 35896 devel optional makedumpfile_1.6.6-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE34E7Im3TmixTD299CrplA3L9lXEFAl0o4rcUHGNhc2NhcmRv QGRlYmlhbi5vcmcACgkQCrplA3L9lXEtlw/+JqoUSQh+sRozvxXiuquUdFcwIFfQ 3Qgxv9OW1/hK0nZLBbz6zU5W4ab+IUvMjY9JymyOApKXwAcMJYT85FuKXHMztuV+ Ov4cQ2TnDXlyIpHdrxTe9HxSDO8WzTTeAkD4P8Rrvl2V622oWgaPCFco9X5Dazls 8aUK6G9Dq55iSL1yiMq8afY8nndniX90ck1Gp+ewxyjWK+xeugUPaXCnX8Z/uVLE fCRyTfbJhvWh7CeKyIbOGuTnvofY+8Fiw2H71JUtfxWFho80uc6vkj+bW+GN5KIr 0NiEuCl7qqpDg/tvShHsW0WIuAyqkCMwt5n/7rtIgrwFwLImCdj093dohQY+3398 FhSasilWe0XDOquZ1m7aaaPo2hBZzlP45XlxpWR+bda6cCRok+dl/D5+iLOYwyI3 NbX+rui69ClCnu0K+ErV+kmLY5AHyl3mlvhH+mv5QW6GkeeR24wk4lkYM9pKHdGK jWMC7hCdIIcD6ikN+prIyLo4k2aey6/0PtRGL2eyFmriCV5QkYf0M8uR0ZUBb41r bov3799N30q9WhYNyIKTxwGD35qrtlXjApQm+umPqMMju9nQ6jL+zQNPySHXWSxY 3/g3L9H8MiUQXESHulmnuQ92x22KfnAhyU/YhHjpWBW9jE4GlkUPKzW3edQDRb/m Ztfja1RufY+Htk0= =+uxq -END PGP SIGNATURE-
Re: DDs brasileiros(as) na DebConf19
On Fri, Apr 05, 2019 at 12:33:50PM -0400, Sergio Durigan Junior wrote: > On Friday, April 05 2019, Paulo Henrique de Lima Santana wrote: > > > Olá pessoal, > > Opa, > > > Como está a expectativa para vir para a DebConf19? > > Alguém não vem? :-) > > É praticamente certo que irei :-). É praticamente certo que não irei. ;-( Cascardo. > > Abraços, > > -- > Sergio > GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 > Please send encrypted e-mail if possible > http://sergiodj.net/
Accepted makedumpfile 1:1.6.5-1 (amd64 source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 05 Jan 2019 09:01:02 -0200 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: amd64 source Version: 1:1.6.5-1 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Closes: 910465 Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Changes: makedumpfile (1:1.6.5-1) unstable; urgency=medium . * Update to new upstream version 1.6.5. * debian: remove debian/source/local-options * [i18n] Move PT debconf translation (Closes: #910465) Checksums-Sha1: c41b00297e33db32b1ddb17164a7de7ff4d00393 2442 makedumpfile_1.6.5-1.dsc 700f2ff13f75d97a0df2303ff9f580cdddadf7b0 193093 makedumpfile_1.6.5.orig.tar.gz e274351219b18dd77db94d5230691feeb19718a0 35888 makedumpfile_1.6.5-1.debian.tar.xz 12ec9e718349a26f49ff3dbb219c8a02cf0b544a 39572 kdump-tools_1.6.5-1_amd64.deb aa4550b11638006e4cd77720f3e770bed86b4d57 303416 makedumpfile-dbgsym_1.6.5-1_amd64.deb d78ecea5f4d8594c238869c6530a78501bbeb0bd 6087 makedumpfile_1.6.5-1_amd64.buildinfo 6eb4d61ca8b393baed7359a6235b44a5bccfd57f 177364 makedumpfile_1.6.5-1_amd64.deb Checksums-Sha256: ae4186769300d67eae36feff719e87ad9a3d0fb2772133a5c74b796bb3cf0ffd 2442 makedumpfile_1.6.5-1.dsc 5d4f1d6ded8dca6951eeabcf4bb1ebf6575288fee947529397103c040eb5c760 193093 makedumpfile_1.6.5.orig.tar.gz 734ef328773396dbedeb639dd945299090cb84b7e28f1c48661a9247f0b9b05d 35888 makedumpfile_1.6.5-1.debian.tar.xz 61bc379753c361bcb1de5f196ce7c2cc77d6180fce1411072e9096a77767 39572 kdump-tools_1.6.5-1_amd64.deb 6597fb1b956ac66a8752343aeb40515187f39ee9288b8ddf2be6963b14a34815 303416 makedumpfile-dbgsym_1.6.5-1_amd64.deb 30eca29d280a39c88c32da70f177f0c22ec905f5c176de7d36b33694541e0b2d 6087 makedumpfile_1.6.5-1_amd64.buildinfo 3efadd9051b2369bb3c576a9af4894dcf2b5e3c1a1775e0d9e93bb129662ab1c 177364 makedumpfile_1.6.5-1_amd64.deb Files: eac2b6fd24ff592e4f31144dbea7cc3b 2442 devel optional makedumpfile_1.6.5-1.dsc 1737f8e8904d565629f0c9e702f92d02 193093 devel optional makedumpfile_1.6.5.orig.tar.gz b93b8f7f6b9d6b0dbfc69aacdd26b666 35888 devel optional makedumpfile_1.6.5-1.debian.tar.xz 5043ce0293e27a7f9da2148568e5bd96 39572 devel optional kdump-tools_1.6.5-1_amd64.deb d1ce8e990343c63510664eda8f01d82b 303416 debug optional makedumpfile-dbgsym_1.6.5-1_amd64.deb 9e7874701a81e135be1dc8517a58a366 6087 devel optional makedumpfile_1.6.5-1_amd64.buildinfo d12f39deac32d17f52f109e1ada9ec77 177364 devel optional makedumpfile_1.6.5-1_amd64.deb -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE34E7Im3TmixTD299CrplA3L9lXEFAlwwn3oUHGNhc2NhcmRv QGRlYmlhbi5vcmcACgkQCrplA3L9lXH6iw/8DDpOm24Ysvs0nFUPjYjHY0jCFpJC 4VbbJkTZC7xJCpbZwRW8fuKUnu8HAMu9UtHwgjocIi/JDxUr0YslnlSb2n3KRqw3 1Y9eodHt9flRAWWeomXi3PFC0emgjRw6TfA6n34iyEAc9yhD5FsNDE2zjy0vdm1m ChhWMUXMBV9FRGdX9M7VFmoSaoWClB2lkq7v/pyExdRiM+XDUvXtTYW6q3xFHHTt MBynG9z210qL7EHKf0aHy6Gm77h7Q5f6IYPSG6z2K3KTo5L6hNu+siJhd2RiVus3 7I/RDnIZR2dHCmd+GXA6L76vZMSWSiLrwvj47y9HKsZDHIvaZZDA8hgHKa1bdhsN +RwlbvV/n3XcjBY9bs+L8Xojxx/lrrGwwbIeRTAdYsifZjVGUsAfLXNwQ6pXwG0P IOGbQdhKh4NsFXFhbshsylXJgjiTbT70y7XBORR2eN+j87y7m1XxuXQUUihv0l5P AkN3QZrCXbQjJMJCfNUdhQLFHypbdLItv5c2WYRYrfkqVK2/o2LwJe4CQW5/4CD/ OcCJ68C7pFrTikUJjzkgKliGzqtxesd0JazS2y732C1XzlvAn3fZvoEddNHBf+9h 9SGXtl8mlO8T0RGsOf67Co334hK/5roSmoyvDPZnOaGIn/qYoFu7swjqB5i3OeAT XPnfcfcD4t8FaNU= =tR1n -END PGP SIGNATURE-
Re: Confusing our users - who is supporting LTS?
On Fri, Oct 26, 2018 at 11:05:18AM -0400, Antoine Beaupré wrote: > On 2018-10-26 10:26:09, Thadeu Lima de Souza Cascardo wrote: > > I am guessing one of the other (incorrect) assumption users might make > > is that the "LTS version" is preferred over other versions. That's how > > LTS works for Linux and Ubuntu, for example. So, a user would rather > > install Ubuntu 18.04 that is supported for 5 years than Ubuntu 18.10, > > that is supported for 9 months. The same happens with Linux 4.14 versus > > Linux 4.18. > > I agree that is a concern... > > > I am not sure it's clear to users that all Debian stable versions would > > have Long Term Support, because the releases are not *labeled* as LTS. I > > know the wiki says: > > > > "Debian Long Term Support (LTS) is a project to extend the lifetime of > > *all* Debian stable releases to (at least) 5 years." (emphasis mine) > > > > But I believe the table right below that would still confuse some users > > that would understand that Jessie is supported by LTS, while Stretch is > > not, even though there is a schedule column there. > > ... but, well, that is pretty clear isn't it? "All" releases are > supported, and "stretch" is explicitely mentioned in the table. I think > we've done our part. > I agree here, my suggestions below were just asking how could we make things better or even more clear to the uneducated user, who comes from these other projects, which have a different release/maintenance process. I would refute some of the suggestions myself, but thought about suggesting anyway because I didn't want to assume how other people would feel about them. > > Using the LTS term in a slightly different way than the "industry > > standard" now means we need to spend a little more effort on users > > education. > > I'm not sure we're using it that differently. But it's true normal > stable releases don't immediately get marked as LTS. There are good > reasons for that, and those would be very hard to work around. To get > more explicit, we can answer your questions one by one: > > > Should we: > > > > 1) Start calling the stable releases as LTS releases? > > No. That would be very confusing, as the stable releases are (to > simplify greatly) under the responsability of the security team (ST) and > the stable release managers (SRM), not the LTS team. > > > 2) Say "supported by Security team" versus "supported by Freexian", > > instead of just saying "supported by LTS"? > > Hm... I'm not sure what that refers to or what you're proposing, but LTS > releases are *not* supported by the security team, but by the LTS team. > I meant that we would say that stable is supported by the security team. And instead of saying that Jessie was supported by the LTS team, we would say supported by Freexian. The table at https://wiki.debian.org/LTS doesn't even say "supported by LTS team", but "supported by LTS", which might be confusing to these users. So, maybe just fix this nitpick? > > 3) Stop using LTS as a "label" for oldstable releases? > > I am not sure how that would help anything. :) I do like, however, the > idea brought by Jeremy Stanley in a reply to your email of using the > "Extended Maintenance" label instead of "Long Term Support" because the > latter is usually attached to a *current* release, while the former is > seen as an *extension*. > > But renaming the project seems like a huge undertaking and I'm not sure > it would really resolve this conendrum. Ubuntu started supporting an EOL release with "Extended Security Maintenance". So, maybe start using something like those two projects have been doing? > > 4) Just advise users all the time that they should prefer the latest > > stable release, as that is going to have the "latest term support"? > > Right. So maybe that's a piece that's been missing in our > communications, and that could be the reason why people still think they > should install jessie cloud images. ;) > > So maybe we could make some proeminent statement on the LTS and > LTS/Using pages in the wiki? > Agreed. Advising new users that they should be using the latest stable release if they have no explicit need to use any older ones. > > 5) Is that not true anymore with Extended LTS and CIP? > > Sorry, what is not true? #4? If so, I think people should *still* > install the latest supported Debian release (stable or stretch right > now) and not LTS or ELTS, when deploying new systems. Yeah, not true that Stretch would have a latest term support compared to any earlier release
Re: Confusing our users - who is supporting LTS?
On Wed, Oct 24, 2018 at 09:30:46AM +0800, Paul Wise wrote: > On Wed, Oct 24, 2018 at 4:15 AM Sean Whitton wrote: > > > > On Tue 23 Oct 2018 at 05:06PM +0200, Markus Koschany wrote: > > > > > > In short: Make it very clear if you want to provide long-term support > > > for your project. Talk to the LTS team in case you need help. Nobody is > > > forced to do anything. > > > > This is a good idea, but ISTM the assumption should be that the > > subproject does not participate unless it explicitly says that it does. > > This thread started because users have the opposite assumption. So I > think it would be better to be explicit about support teams and > timelines. > > -- > bye, > pabs > > https://wiki.debian.org/PaulWise > I am guessing one of the other (incorrect) assumption users might make is that the "LTS version" is preferred over other versions. That's how LTS works for Linux and Ubuntu, for example. So, a user would rather install Ubuntu 18.04 that is supported for 5 years than Ubuntu 18.10, that is supported for 9 months. The same happens with Linux 4.14 versus Linux 4.18. I am not sure it's clear to users that all Debian stable versions would have Long Term Support, because the releases are not *labeled* as LTS. I know the wiki says: "Debian Long Term Support (LTS) is a project to extend the lifetime of *all* Debian stable releases to (at least) 5 years." (emphasis mine) But I believe the table right below that would still confuse some users that would understand that Jessie is supported by LTS, while Stretch is not, even though there is a schedule column there. Using the LTS term in a slightly different way than the "industry standard" now means we need to spend a little more effort on users education. Should we: 1) Start calling the stable releases as LTS releases? 2) Say "supported by Security team" versus "supported by Freexian", instead of just saying "supported by LTS"? 3) Stop using LTS as a "label" for oldstable releases? 4) Just advise users all the time that they should prefer the latest stable release, as that is going to have the "latest term support"? 5) Is that not true anymore with Extended LTS and CIP? Cascardo.
Accepted makedumpfile 1:1.6.4-3 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 16 Oct 2018 15:30:16 -0300 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source Version: 1:1.6.4-3 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Changes: makedumpfile (1:1.6.4-3) unstable; urgency=medium . * Reload kdump after memory/CPU hotplug. (LP: #1655280) * Fix adding crashkernel to zipl.conf when no quotation mark is used. (LP: #1790788) Checksums-Sha1: 3e672a9f54d5b6de81539aad4fc90ecbcb04c757 2293 makedumpfile_1.6.4-3.dsc 7ef3ce57b7cd3d904f4aeeefaa78dfe5a2eeb72f 35804 makedumpfile_1.6.4-3.debian.tar.xz 49266db5611b9f82891c1c70eb70707d8ff3f89c 6343 makedumpfile_1.6.4-3_amd64.buildinfo Checksums-Sha256: be7c97c4408aa03ef521110b0c699392f76788ac962d9f504603f64a8c14c5a7 2293 makedumpfile_1.6.4-3.dsc fb148fc2652ebbefbc23c3d050ad52d6b49ecadb5b47ec883c53eb57dc34fa6a 35804 makedumpfile_1.6.4-3.debian.tar.xz a26a366bdb30e190633a2f4bebfc7f384c3cc31ab661f04f7e83a70e38cd9b4c 6343 makedumpfile_1.6.4-3_amd64.buildinfo Files: bdda78b2575a1dccb91bf347433ccdb8 2293 devel optional makedumpfile_1.6.4-3.dsc 31b09c555abe06a2ef1a278b9d85867d 35804 devel optional makedumpfile_1.6.4-3.debian.tar.xz 6c313a851e9f38f87ac6c86951a1691d 6343 devel optional makedumpfile_1.6.4-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAlvGY+sACgkQCrplA3L9 lXF70w/+JcSpOq2fcVWU/dw/FceyEatVsWWqyvrcroKb457dAbSdKgKEOftXhdSW OQ6i4eWD1eDwPIPsIJclWTfE0DjNSlu8k1Sh2JvptSGOz97Wdt+pE3FhHCS3htX+ rhhi4IgDJryF6YGRjAYDgdlVZ3UrrIrypmBBx2eOY1h14CMIbwFSArUS2qKnfG/F GGq3qSaDMbFRRTGHhIyIofAM8r1ZJc580CSUpmhgG8XeAKEaXDMOs4jiFmOaukLS axbkx2myFLv39zKxv1oHoNpDzsfKHYVj7L8cISz2jhYPrD20QteFAwpgE1luuKpJ PgqI9YBz7xNsJJSPonzahLkrLY8NPk/l8OcCnCLHEB44QkDxxG/X6Dd0d5dzvZoL RcVHJJqYpfYjsWIBHN9XTMm2vO7VjeIQeLp6T5RCFtmVcPNZdAH1fdngnyqqiS6C VNKdlk4a51hET6fkB4pRD7MD3ZezIXe0RVO7Hv8zX07Tz3mpdzRs+VvknMnFbElE RekINWRPRyPS6dt3+pgOMnxUSQTvkd14aXXaiHZrlCHghMqzzgLdKIp/rc489Mtx SuKIGusHk2f2/GqYWL7OQyMMBfzSw7cnzZvFUvuHVXWNUJ2Op92OYWPDU8MJFYGE BsRf4m8XM/5jR23RT4ZmqklHeGTFJ+VXg0gKnUjhULD00L0Lgc4= =AW2A -END PGP SIGNATURE-
Accepted xtables-addons 3.1-0.1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 22 Aug 2018 11:19:11 -0300 Source: xtables-addons Binary: xtables-addons-common xtables-addons-dkms xtables-addons-source Architecture: source amd64 all Version: 3.1-0.1 Distribution: unstable Urgency: medium Maintainer: Pierre Chifflier Changed-By: Thadeu Lima de Souza Cascardo Description: xtables-addons-common - Extensions targets and matches for iptables [tools, libs] xtables-addons-dkms - Extensions targets and matches for iptables xtables-addons-source - Extensions targets and matches for iptables [modules sources] Closes: 906445 Changes: xtables-addons (3.1-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release + Support for linux 4.18 (Closes: #906445) + Update cross.patch Checksums-Sha1: 119a023b0535de5083b7eac1c33abaa95af1e271 2169 xtables-addons_3.1-0.1.dsc 781e2fef2edd5f140034a0546182911c807fb731 323684 xtables-addons_3.1.orig.tar.xz 9accc5dc13e2887b7e095ca3698b0c54592067c5 11204 xtables-addons_3.1-0.1.debian.tar.xz afb22b50eebb6d3d99c9ca7cd65fc691779a421e 183524 xtables-addons-common-dbgsym_3.1-0.1_amd64.deb cc8bec2009957b9e6638e08652afe015ae941b84 59160 xtables-addons-common_3.1-0.1_amd64.deb a93ef8bca4abb17955d8dc01705ed9fb9b9d4285 286488 xtables-addons-dkms_3.1-0.1_all.deb 3fa8e0cc6d08b3a263d7b472fca813f1f58b9705 324420 xtables-addons-source_3.1-0.1_all.deb 32123ed9fe9e93edb5e1cd98d82ac301869f6b66 8182 xtables-addons_3.1-0.1_amd64.buildinfo Checksums-Sha256: a86d71969d3fb99c48c5c9e10471b98647294188bd32d54e099873345bd3c762 2169 xtables-addons_3.1-0.1.dsc df54ce9e681749f8b2a725489af61b2fbc3ac2153710a73b78751fd7ed79e354 323684 xtables-addons_3.1.orig.tar.xz 6455635163ee38edb68211b761870f769a93c15b8eb2266794224340856e2d80 11204 xtables-addons_3.1-0.1.debian.tar.xz 02d3b04fef06352dda0d4a3c317dd81efbb3492c71f42a05c7c81739b2386cbc 183524 xtables-addons-common-dbgsym_3.1-0.1_amd64.deb b18cd569981d05fda8ea7eab04ebb1fdb8ab97ff87c771b3d3b5ebf84d8b4192 59160 xtables-addons-common_3.1-0.1_amd64.deb 448678a5c22c448e90041d02fa0eea3b173b2b2310d77e54b96bf0adab941f19 286488 xtables-addons-dkms_3.1-0.1_all.deb 8b956a9a6b4f63b3c804c0b348505c8f3b915088ed02e588ae35bfa6124079dc 324420 xtables-addons-source_3.1-0.1_all.deb 24e51613d14c1b59191507cda8580b471ff4a01c59f05d8f0a2cdc896c065ca9 8182 xtables-addons_3.1-0.1_amd64.buildinfo Files: abfd4185fbcf888efd922b77d9af78bb 2169 admin extra xtables-addons_3.1-0.1.dsc a77d2fc2151eed97f903d7905640e549 323684 admin extra xtables-addons_3.1.orig.tar.xz 347d727f35f55d2a532c14e9f571b28a 11204 admin extra xtables-addons_3.1-0.1.debian.tar.xz 651f31ef4a997dd8b34e5e6e4de84e43 183524 debug optional xtables-addons-common-dbgsym_3.1-0.1_amd64.deb 3baf8a662d5a34a806b73e05e9e3ab2b 59160 admin extra xtables-addons-common_3.1-0.1_amd64.deb 42acc440b7912c511c32d78e060fc2c4 286488 kernel extra xtables-addons-dkms_3.1-0.1_all.deb a3158961f5bb9b1325d15ed25966e1f7 324420 admin extra xtables-addons-source_3.1-0.1_all.deb f6dcf5528000f7f3534177465c9ba6b3 8182 admin extra xtables-addons_3.1-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAlt9dEMACgkQCrplA3L9 lXE5nxAAm0qCtL/SxcjD+HPMmjDHBC2D+tDQyABmYac1sLGP16C079Zw/H2ge+Fd whqb7xAMEzWhBGMVB5io+XJjYtazFP0+7gME4wZRik8x8q0CrNY9orJzfKBiJwL7 r74X5yzp3+PcolChBGQtz+VJw654pu9/M75O2nBzbYH54AhBkoF6hHt8PAHtnBYf sKeUHGvmL0p2wkVzG6g7imwzPiJM/M6rdn3qbxEKSXDTycZ28NFK+X9U3/yubmPl IifTP2jzyQCU5NO/hW7V+LhZdWoeLpMPVrdfL6qjQhIc3DHVlYF50IOAOw2ElGlc +SNjMmCbHcOCtm3h/AdNtauVsgEiKdpgejxuFo9/nuW0rPoPEuvjfieUL4T+5ZMi 0aUdSpIaYxZ9VXVgUsg+ZAalO8sJbPa8ZCwazzlnMRX27ybmtKKOBVndZS12kd/W YsGvdwD0vio+tXc0yvaqY5r+6J0NA6jsRmbQ8XRZZyzLGzPorOWJFX7AkU2rXEP/ 5jiz3Mc4WdjmbwZ6sJhJkj4evUgHX9Z24Yc3vz5J0hHM88ingPZD+rKkyJyCHJXm rqoAZcDGsQsUTvwRY2AyUPfwZ6TwjrjSuoDbBCdPRo9Koc0lDz9lqPlT8fdMg6OX lYyl9RdA5wkZw5GH1w6HgI3X/YARZueXrvSjoIx8n1cQbLN+Bvk= =nAOj -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.4-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 26 Jul 2018 10:02:40 -0300 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source Version: 1:1.6.4-2 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Closes: 904524 Changes: makedumpfile (1:1.6.4-2) unstable; urgency=medium . * Ignore uninstalled kernels when doing the kernel postinst. (Closes: #904524) Checksums-Sha1: c633181091f15f6a2e7265fb163a03bc7c28bd45 2293 makedumpfile_1.6.4-2.dsc acb3eb1a9b9e8bd76ff48c8faf36f52edae5da8f 35564 makedumpfile_1.6.4-2.debian.tar.xz Checksums-Sha256: a89efd74d33c0a123c8ec598d199125bac7a9745121205a0366b5a5d76dc0c54 2293 makedumpfile_1.6.4-2.dsc d39607d0300af0d9d640ba21b95d4b42821b518fad715e8e56bb7c918c2ae850 35564 makedumpfile_1.6.4-2.debian.tar.xz Files: da357b0471a9c1d0f1eed991767436e6 2293 devel optional makedumpfile_1.6.4-2.dsc 3ce5720ac6212216de1a8dc27c6dd01c 35564 devel optional makedumpfile_1.6.4-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAltlBakACgkQCrplA3L9 lXFUehAAkmG7KPmD9h+0mrjjBj36G06vOVDzAx6JxG28xOkGbwC972rzP3cWQwc3 PrCedOfwsg4oUQMpAMFh7aQihnWhZNMl+vfaV8gplAPdcICS0RxjJEq2X+9PdVJ6 hAx8Xyynh7UsafWq3s3q0bOJ8IlpRQUua7rxs/xjn5p4XtlsPpTeLbj3/jYyxDAe C4q17qJ1GWAKsK/UKrGChknxtqluY79K9c4b8VxK8aYZGaevmz3kk1R+K5G1h8ts ZuMKdGuWVsku5c3bmN/gAooSZ/djkUHxDlAsyYloxtSTS+rXqvfwZbVyXul/qQO2 CQ3FF044riT1Raqveyh1Fn8tw5f7qUqPL7/HuYFeHgJv1693RfT4fUJ1PLeiB4g2 j3wO2HkDJ1bJ8yG7xMJJOeQbO4lZFhi1+k5S1TKqlx/0oRc1uB3jHRBSjhmikj01 rvbHn9LLNsveWnnLm+Dnljk5MHZXt3K0P0+FlrkUDmHb5Z9qEiDPCDNJ+28Qhrg9 HCJGjssxGuYNDgYWu05PC3/i0TIxr1CehowLgXSG+Lt74nauGQsOAS0iAn7PaewB t1Ak8LE+WO9Run9I8jZaoJX7CIs7HHmhjwaEf4lE+qgFbZ+CwSUWvIl8DRcIv+LF +BB8F21s958D6pMwD/eijFc5r0M/b4WYST6QUlMvu0oG4yCI0cY= =hhha -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.4-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 19 Jul 2018 16:34:06 -0300 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source Version: 1:1.6.4-1 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard Changed-By: Thadeu Lima de Souza Cascardo Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Closes: 856784 883139 898280 Changes: makedumpfile (1:1.6.4-1) unstable; urgency=medium . * New upstream release. Main new features: o 5-level paging support - 5-level paging on x86_64 system is supported from this version. . o --mem-usage support for arm64 - The makedumpfile --mem-usage option is now supported on arm64 system. And the option was also tested on ppc64 and s390x by Bhupesh Sharma. . o Support new kernels - The supported kernel is updated to 4.17.0 in this version. . * Changelog: o New feature - [PATCH v2 0/3] arm64: Add '--mem-usage' support (Bhupesh Sharma) f49ca13 - [PATCH v2 1/3] Add a new helper file 'tools.c' that provides some useful APIs (Bhupesh Sharma) 4d86cc7 - [PATCH v2 2/3] arm64: Add support to read symbols like _stext from '/proc/kallsyms' (Bhupesh Sharma) d1e7805 - [PATCH v2 3/3] Documentation: Update documentation regarding --mem-usage' option (Bhupesh Sharma) 8449bda - [PATCH 0/4] Add 5-level paging support (Baoquan He) 342fdab - [PATCH 2/4] Add pgtable_l5_enabled to number_table (Baoquan He) 8ae6f36 - [PATCH 3/4] Add a new function check_5level_paging() (Baoquan He) 33ca808 - [PATCH 4/4] arch/x86_64: Add 5-level paging support (Dou Liyang) 30a3214 - [PATCH] handle mem_section as either a pointer or an array (Thadeu Lima de Souza Cascardo) 14876c4 - [PATCH] ppc64: Increase the VA range (Hari Bathini) bd1ae9c . o Bugfix - [PATCH] sadump: Fix a problem of PTI enabled kernel (Takao Indoh) 38de12a - [PATCH] Fix a bug when multi-threads feature meets enospace (Zhou Wenjian) 63b05c9 - [PATCH] Fix array index out of bound exception (Lianbo Jiang) e5f96e7 - [PATCH] fix for hugepages filtering (Hari Bathini) 246801c - [PATCH v2] Use integer arithmetics for the progress bar (Petr Tesarik) c6b79cb - [PATCH 2/2] Check PG_swapbacked for swap cache pages (Petr Tesarik) ca1f31e - [PATCH] Fix -g for change of mem_section (Kazuhito Hagio) f3c87e0 - [PATCH] Fix -i for KASLR (Kazuhito Hagio) 08db98c - [PATCH] Fix validate_mem_section() (Kazuhito Hagio) 8f1aafa - [PATCH] arm64: Fix calculation of page_offset in case we are running cases other than mem-usage (Bhupesh Sharma) cb7af5f . o Cleanup - [PATCH v2] Always use bigger SECTION_MAP_MASK (Petr Tesarik) 6c6789f - [PATCH 1/2] Add is_cache_page() helper to check if a page belongs to the cache (Petr Tesarik) 694f28c - [PATCH 1/4] arch/x86_64: Cleanup the address translation of the 4-level page tables (Dou Liyang) acab2a2 - [PATCH] Fix some compilation warnings on x86 system (Kazuhito Hagio) 2148e43 - [PATCH] Update maintainers (Masaki Tachibana) bc7420b . * Remove 0003-sparsemem_extreme.patch, applied upstream. * Update pt_PT debconf translation, thanks Rui Branco. (Closes: #898280) * Update ru debconf translation, thanks Lev Lamberov. (Closes: #883139) * Update da debconf translation, thanks Joe Dalton. (Closes: #856784) * Make ADT check for systemd service. * Skip test if crashkernel was not reserved. Checksums-Sha1: 7ae564801d248f68cb705ab7dc2ea435091c6c6d 2293 makedumpfile_1.6.4-1.dsc 2ec04ae267c7a216193c1c7a227aca78fe40a3fd 191786 makedumpfile_1.6.4.orig.tar.gz 6e7df6c2d5e576c57425401e3b635ebf3d27d227 35500 makedumpfile_1.6.4-1.debian.tar.xz 8422f6593d946b90c5d566b3e175c4e21fd7ac72 6838 makedumpfile_1.6.4-1_source.buildinfo Checksums-Sha256: 3e178792aca9c024116b2ba353a541d215e8c968aabb9dbfb0b753452b39724c 2293 makedumpfile_1.6.4-1.dsc 7e06f72d5f291fcab9e92975f405a76e37d4f7fc8fa4172f199636398ae812b1 191786 makedumpfile_1.6.4.orig.tar.gz 7c1ffd2e8e9b8bf1dce20e7e8ad0481ce7f91f35a904d56fb6a5cf11ad872260 35500 makedumpfile_1.6.4-1.debian.tar.xz 6b319a6d41c103c0095ffd9a3101c8baf0efd67e9a235db4856aaebfd5ab0644 6838 makedumpfile_1.6.4-1_source.buildinfo Files: b861bd03aa451955f65656e665cc3686 2293 devel optional makedumpfile_1.6.4-1.dsc 7dfbca19f487604c271e2892ba07f4bd 191786 devel optional makedumpfile_1.6.4.orig.tar.gz 3fbbfe1ddc33ccaadcaae8679c83e5bb 35500 devel optional makedumpfile_1.6.4-1.debian.tar.xz b7f3b08d42e5e27cd37fd532eba5b774 6838 devel optional makedumpfile_1.6.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAltY1nUACgkQCrplA3L9 lXFaQg/+LcUkjUDbB3tY+VHiozQe18LrdroGL3nSjIEEBia4Uf3/+E1KYtfDOkOp 0Utiw2rhLrjFJv1lyEfoykSB/jT+fDiggJK0vuJfTTDoP2f6tJet/uRetU3SZ2Q2 Ccc
Re: Fwd: Uso de AR nos pacotes .DEB
On Fri, Jul 13, 2018 at 03:29:48PM -0300, Antonio Terceiro wrote: > On Fri, Jul 13, 2018 at 02:28:29PM -0300, Thiago Marinello wrote: > > Olá, pessoal. > > > > Recorro a experiência de vocês para tentar me explicar por que diabos > > os pacotes .deb usam "ar" e não "tar"? > > > > O formato do ar usa um campo de 10 bytes para representar o tamanho do > > arquivo, o problema é que o valor é codificado em ASCII, o que me > > parece muito tosto. Isso faz com que o limite seja "99" bytes, > > mas poderia ser 2^80 caso o valor fosse codificado em binário. > > > > Alguém sabe por que o ar é o formato escolhido? > > O motivo exato é difícil de saber, eu acho que provavelmente foi só a > escolha arbitrária de quem implementou o formato na época (1994). > Olhando o Changelog.old em https://anonscm.debian.org/git/dpkg/dpkg.git: * dpkg-deb now supports new flexible format, but old format still default. É a única indicação. ar era o formato utilizado para bibliotecas na época do a.out, se não me engano. Ainda é o formato para bibliotecas estáticas. E olhando o código do dpkg 1.0.0 [1], pareceu bem fácil de implementar, além de permitir o uso de uma ferramenta ubíqua na época. tar tem vários formatos incompatíveis entre si, mas não foi impeditivo pra usá-lo pro control.tar e data.tar. Tudo isso é especulação. Talvez valesse perguntar ao Ian Jackson, caso ele se lembre. [1] http://archive.debian.org/debian/dists/Debian-0.93R6/source/base/dpkg-1.0.0.tar.gz Curiosamente, o formato antigo ainda é suportado, mesmo depois de 25 anos. `man 5 deb-old`. E `man 5 deb` para o formato novo. > > E no caso de > > precisarmos de um pacote .deb com tamanho da ordem de 10Gbytes, há > > alguma forma elegante de suportar isso? > > se você precisar de um .deb de 10GB, provavelmente está fazendo algo > errado. existem ferramentas pra distribuir arquivos imensos assim, e um > pacote .deb certamente não é uma delas. Algum caso específico que você esbarrou? Daí, talvez seja possível sugerir outra forma de distribuir tal conteúdo. Além do mais, dpkg hoje suporta diferentes formas de compressão pro data.tar, e talvez alguma permita reduzir o tamanho de forma suficiente. Abraços. Cascardo. signature.asc Description: PGP signature
Re: Announce: docker-buildpackage
On Wed, May 02, 2018 at 11:29:29AM +0200, gregor herrmann wrote: > On Wed, 02 May 2018 11:23:56 +0200, Thomas Goirand wrote: > > > Instead, I very much would prefer a patch to puiparts so that it could > > use sbuild's schroot system instead of tarballs. > > piuparts has support for using chroots: > > -e dirname, --existing-chroot=dirname > Use the specified directory as source for the new chroot, > instead of building a new one with debootstrap. This is > similar to --basetgz, but the contents are not archived. See > also the --hard-link option. > > I haven't tried it with schroot's chroots yet but it works with > cowbuilder's chroots for me. And it has --schroot, and just noticed that it also has --docker-image. I used the former in the recent past, though not the latter. --schroot=SCHROOT-NAME Use schroot session named SCHROOT-NAME for the testing environment, instead of building a new one with debootstrap. --docker-image=DOCKER-IMAGE Use a container created from the docker image DOCKER-IMAGE for the testing environment, instead of building a new one with debootstrap. This only supports overlay2 for now and it uses the MergedDir layer where piuparts can access, add, edit and remove files easily. Cascardo. > > Cheers, > gregor > > -- > .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 > `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe >`- BOFH excuse #213: Change your language to Finnish. > signature.asc Description: PGP signature
Accepted makedumpfile 1:1.6.3-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 Mar 2018 09:28:55 -0300 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source Version: 1:1.6.3-2 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard <louis.bouch...@ubuntu.com> Changed-By: Thadeu Lima de Souza Cascardo <casca...@debian.org> Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Changes: makedumpfile (1:1.6.3-2) unstable; urgency=medium . * Add support for SPARSEMEM_EXTREME mem_section as a pointer. (LP: #1750021) * Add an autopkgtest that test that a crash produces a compressed dump file. * Create initrd for previously installed kernels. (LP: #1751329) Checksums-Sha1: ed9ca4b8e8dfd09538ac096fac30e40d0f31f1cc 2293 makedumpfile_1.6.3-2.dsc dfee6b51026308bbb85eb6cfd9939e93cf1f805f 35384 makedumpfile_1.6.3-2.debian.tar.xz 9db2ae69ed47fe9c1e94d4689d2bd1b1ff5a142d 6338 makedumpfile_1.6.3-2_source.buildinfo Checksums-Sha256: 523bc36951b50015fcc8a67886536c444cc79cae51f3b88bcfc8796a621582d5 2293 makedumpfile_1.6.3-2.dsc 4cb59e9530f04634caac472c25108b59ae6bbad94be03bd1d83229fa1f6acbca 35384 makedumpfile_1.6.3-2.debian.tar.xz f8c87cf65a9f5ad12d96838353e2e98758c1da8c4a14a5f18eb22d793d6d4e5e 6338 makedumpfile_1.6.3-2_source.buildinfo Files: da52fe89a7c185def16e7591233cf935 2293 devel optional makedumpfile_1.6.3-2.dsc cf7776359a4597c5021d51471054a316 35384 devel optional makedumpfile_1.6.3-2.debian.tar.xz 68e036b26e4cea9d0e26c63cf8509582 6338 devel optional makedumpfile_1.6.3-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAlqdZh0ACgkQCrplA3L9 lXG1ERAAwC7q4zYl1dxLRPG1HLtZpiH/WT35MMowerY/uqxTvaSyDReFhcqVciYV GapehZugSJsW7O5+aRu/V1g5PkdUopvNpFEVKd5BYb3BTeN4tNm1IPVt1kiiwI3m uZEJykD267VPXJQFVNtQNpYMBg/QfN9/2DdZTZohbWciarg6JFo00mL64SkjtI6J CdNLIMDgxZg30fYt4iIwqrNkxouOtDAbe8tW+uRNriNLrAyGSblDKjuWYsgSInGf 7itHF/QLiGkqoia75NquQ39scPeOk23NzPF907UBHKrbxexUPqyjHO/2uHZIJ7hd pg6fXbzPPnD/CRWECyRRDKuynLifRj36oytva71QH9z8rExGqgIBdvF6M9FfEUpD jDJHugxsY93kuTgaIR+RN9NaISPtXbBWCQ5udaqbFEm88kI1Oo7+TgVnNEJ915ha jJW1EwCV36ExnwwtWPqzKYFuv3jmCXofgXSZpi+qDOxZYW/K6mcMUAkycSm5itSU r05BbK0aBLnak/i0hPQSL2zuBgDjdISIC7cn/3VL0850pLumKo5phd41c/zIQGlg HN8uz9cHjVv29ZRfbdNH1MSFcGm79tp/aswZPhB0vG2whVf6jz7OjhLOzlWyHtEu WD/oKQDFi89mI4O0pPZYkDdK8nR6xqp+02qfO/79sQ/z01L50b0= =vwm3 -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.3-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 Feb 2018 12:53:14 -0200 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source Version: 1:1.6.3-1 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard <louis.bouch...@ubuntu.com> Changed-By: Thadeu Lima de Souza Cascardo <casca...@debian.org> Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Changes: makedumpfile (1:1.6.3-1) unstable; urgency=medium . * New upstream release. Main new feature: o Support new kernels - The supported kernel is updated to 4.14.8 in this version. (LP: #1746299) 4.14.9 and later can't be filtered correctly due to inappropriate VMCOREINFO, it will be resolved in kernel 4.15. . * Changelog: o New feature - [PATCH v2] x86_64: Take care of init_level4_pgt rename in kernel (by Pratyush Anand) 64bd5db - [PATCH v2] Fix SECTION_MAP_MASK for kernel >= v.13 (by Pratyush Anand) 4bf4f2b - [PATCH v2] book3s/ppc64: Lower the max real address to 53 bits for kernels >= v4.11 (by Bhupesh Sharma) 6c83e74 - [PATCH v3 1/4] Support symbol __cpu_online_mask (by Takao Indoh) 3b11c00 - [PATCH] ppc64: update hash page table geometry (by Hari Bathini) 3c39f13 - [PATCH] handle renamed init_level4_pgt -> init_top_pgt (by Jeff Mahoney) 5e54d53 . o Bugfix - [PATCH v2] arm64: Fix page table walk of 1GB section (by Bradley Bolen) 27508f1 - [PATCH v2 1/2] ppc64: set page_offset in get_versiondep_info_ppc64() (by Pingfan Liu) 52319d2 - [PATCH v2 2/2] ppc64: get the info of mem reserved for crashkernel (by Pingfan Liu) c7fcbbc - [PATCH v3 3/4] sadump: Fix a KASLR problem of sadump (by Takao Indoh) b4f7d95 - [PATCH v3 4/4] sadump: Fix a KASLR problem of sadump while kdump is working (by Takao Indoh) 13d3059 - [PATCH 2/2] Fix 'kernel_version' variable being uninitialized & introduce minor reorganization (by Bhupesh Sharma) d1ffe82 - [PATCH 1/2] Fix off-by-one errors in exclude_segment() (by Petr Tesarik) 590f35e - [PATCH 2/2] Fix physical-to-virtual conversion in exclude_segment() (by Petr Tesarik) 6c1bf2a . o Cleanup - [PATCH] Fix formatting problems in header file (by Eric DeVolder) cefea9e - [PATCH v3 2/4] Introduce vtop4_x86_64_pagetable (by Takao Indoh) 6de5d37 - [PATCH 1/2] Fix compilation warnings on ppc64/ppc64le platforms (by Bhupesh Sharma) 0df157a - [PATCH] Make good use of is_cyclic_region() (by Atsushi Kumagai) 6bfd7a3 - [PATCH] Fix the regression about getting kernel version (by Atsushi Kumagai) 254c116 - [PATCH] Update maintainers (by Atsushi Kumagai) 9d3147e . * Use multi-user.target. (LP: #1708409) * kdump-tools Recommends initramfs-tools-core. * Add myself as uploader. * Move Vcs control fields to salsa. Checksums-Sha1: d9732d11817a5fb55fb5ebcb59046f9206e8deb7 2245 makedumpfile_1.6.3-1.dsc 4d3dd4248ebe2e2ecc72e2ad5bf03782d30ef4a4 186492 makedumpfile_1.6.3.orig.tar.gz 53312e86bf105cd6d66b2453f9531d52772e60c4 33224 makedumpfile_1.6.3-1.debian.tar.xz f91a71e5f94bd2bde71647f631d0702611f1e794 6246 makedumpfile_1.6.3-1_source.buildinfo Checksums-Sha256: eafdd4dd285d1bc3a24a6ddb28243c6eac46cf1b2c99746b6ab0a74778fd73fe 2245 makedumpfile_1.6.3-1.dsc cb1afe2cf24147eac983694bfbcf8c1b149eeeb92289562d4d25fbe3b100b125 186492 makedumpfile_1.6.3.orig.tar.gz a12c291ce24d3748bde3ede22a4c4935c663716ac7f1c127e4f1229f1aa2828e 33224 makedumpfile_1.6.3-1.debian.tar.xz a60ed56f335cc15272c1a8ac3233f1e98f15781cc62b488878e1d9c519eaed65 6246 makedumpfile_1.6.3-1_source.buildinfo Files: 758631638c823cd7a73410e557c3494e 2245 devel optional makedumpfile_1.6.3-1.dsc 5b4a814c1e74f3b08e06d02bc88c743c 186492 devel optional makedumpfile_1.6.3.orig.tar.gz 32b3089014e8584690f45b9465716f4a 33224 devel optional makedumpfile_1.6.3-1.debian.tar.xz 7a73f09ce91fb60fdc5c6e908a2f44d2 6246 devel optional makedumpfile_1.6.3-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAlp61YgACgkQCrplA3L9 lXHgUQ/+JJFL1RNaA56qj0ESmo6Yey1cgnmb4R+b1QbKHGVDU1AZlVgUFGui9GO9 Nvz4fm44clh4ZSYdhHWlC0pumSyhG9B52MUIL0QFBZqnbsj86bmxcm4ZpsdgqUtT LTjpxkA6L8BLhGYpSTsSIbNCh2ctLr3ey7WHPehJs8r/XvYh2VZxu6zwahQYI1b/ sE3BOp0fjchSBvcUQcesBWcVhBYfi9+eIvaHwfBXrlKPdhbZzrZaz0priSrzI7xa 99NB2AAPtJ7ZlKmDiX/dNRS6CKNC3oSM2rtgEZvQGO7dazausXnpIyWZyFlRBSD3 kEz20qwTTn+YqW8+Jws7vzi+USdUKbZPiPSxLL+WwONzLuwC1S5IyGhqf8mPHklH YvOjqE0nsnImMKhN/Gf4UbTzBEZJyp058SKaCsOao8Epcp34ztJoTvA6KaI4gB+3 2BIwPAeA5BzjcOEzEgveniYHhq+9YJH6iUSCylvCFErMQOOHy2F5Qt5e0CjoGNR1 XzEWIAR0pHqnH/l6WOL+G9S1RFT3glknZf8J8M0z1XiFOtPpLMCHudrXQunzdPeU P2X3Q26sl51m51fzCdYuaVuehD86lbN1k1jTxjodm6eFQPKrY07OaaTeLaeeVv5k JKNS9qh5USlsohuQihkPLwJHgkJCDUji/LC/JIe9nx2EIguiRS0= =2mCo -END PGP SIGNATURE-
Accepted sendxmpp 1.24-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 03 Nov 2017 08:02:27 -0200 Source: sendxmpp Binary: sendxmpp Architecture: source Version: 1.24-2 Distribution: unstable Urgency: medium Maintainer: Thadeu Lima de Souza Cascardo <casca...@debian.org> Changed-By: Thadeu Lima de Souza Cascardo <casca...@debian.org> Description: sendxmpp - command line XMPP (jabber) utility Closes: 868447 Changes: sendxmpp (1.24-2) unstable; urgency=medium . * Adopt package (Closes: #868447). * Add VCS fields. Checksums-Sha1: 51c9340e04490d0cf8c21adcd2cc1cd55275c07f 1839 sendxmpp_1.24-2.dsc 6373795ad2134659a556a7ced20bf08592b4b213 4116 sendxmpp_1.24-2.debian.tar.xz 5e1ea4ade11d9f8c7d44127d2edb939070c48cb2 5823 sendxmpp_1.24-2_source.buildinfo Checksums-Sha256: 61fb2b2237da135e2dcfecdad28126d242b0355016d927c526911b90a549d3b5 1839 sendxmpp_1.24-2.dsc 590d12af52899d0163949c4225da0517414205e7c7ed1420958ef4045bda377b 4116 sendxmpp_1.24-2.debian.tar.xz 4bbe67a9c04ff1027bf99640a4cbb4fdda73ec5d5ad7f8340a2a40333b28a4e6 5823 sendxmpp_1.24-2_source.buildinfo Files: 3e2386788be3758df0acb631b61e080a 1839 net optional sendxmpp_1.24-2.dsc 68053e845ebc2d9c42e97d481db78978 4116 net optional sendxmpp_1.24-2.debian.tar.xz 736ebc48e1f23f79da57a066f54ad9ac 5823 net optional sendxmpp_1.24-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAln8RWsACgkQCrplA3L9 lXEmPBAAoKrXfUOpA8TzxhhMWkXx8XXjtRGg1V/0Yf0pdSJo8+E5mC1ZZmZ+U6Z4 23P5+6LqG0rJrUTYzUSr8l1w4m+ZB7wTxRkMKhRigOq5cPUFasxHfoOpjN/UUpSt MLRGBekHlX3qnCQab9kIcQUxkS+Jjw16wWkBjG6gQ6mYK8xO26Vy37SPVXIi5/nT lUdxLBpad6cefSDs161Thgtud/8Vr6ZLRhcjdPW8FfCAMm7aprrNLNoa48g0kTe0 R6GoOZaOV0t14RKOQkDGUaU8tk65K86q/qtHIyiYH/OiCdPnZA+ZKa3OUwdZW3aZ pSnC+2CRhZx2X4QQER9J724ck3sM6odIR243AQH0Awi2KbE52IolY4dY1zkfEN8c i2MS40GySp6KRhbk06zQfspQ+JR77Wl9kHGM6uKXnx+i/khm2PyM3+o+XzS1UpNa 9GsPSRjTlcSgOUCE8IObKS/CqRCZ7RDvZX+yqP67lGy5UJ9vUOTK5Aak1sjFlZvS 8bkbqD+b6qk2E9T3Hy1P1xkf0XY1gvWuAUgwfT/Gi/AI+npNEEFatzrgI5COB3M1 HAgmkintLadd+oGYiMzama9ohnwDcFbv8XCg+BdtMcf6u7KbcrGqIqkWLuhkNQUW nuicZlCH3B78qFLShYlxSVZXwvFeDNGDtOjMESOmKpaIPknFhE8= =A3v1 -END PGP SIGNATURE-
Accepted makedumpfile 1:1.6.2-0.1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Sep 2017 16:21:35 -0300 Source: makedumpfile Binary: makedumpfile kdump-tools Architecture: source Version: 1:1.6.2-0.1 Distribution: unstable Urgency: medium Maintainer: Louis Bouchard <louis.bouch...@ubuntu.com> Changed-By: Thadeu Lima de Souza Cascardo <casca...@debian.org> Description: kdump-tools - scripts and tools for automating kdump (Linux crash dumps) makedumpfile - VMcore extraction tool Closes: 857051 Changes: makedumpfile (1:1.6.2-0.1) unstable; urgency=medium . * Non-maintainer upload. . * New upstream release. Main new feature: o Support for sparc64 - sparc64 is supported from this version, it's tested on kernel-4.1.12. . o Add new option for --dump-dmesg - Introduce the new option "--partial-dmesg", it can exclude the buffers cleared by "dmesg --clear" while the current --dump-dmesg always extracts the whole ring buffer. . o Support new kernels - The supported kernel is updated to 4.11 in this version. . * Changelog: o New feature - [PATCH] Add initial sparc64 support (by Tom Hromatka) 001d9b7 - [PATCH v5 1/2] Add runtime kaslr offset if it exists (by Pratyush Anand) 2bfb7f1 - [PATCH v5 2/2] x86_64: Calculate page_offset in case of re-filtering/ sadump/virsh dump (by Pratyush Anand) 4944f93 - [PATCH v2] Add the --partial-dmesg option to dump only non-cleared dmesg (by Ivan Delalande) ec5da81 - [PATCH v3 1/2] Fold the calc of time delta into a func (by Pingfan Liu) 1192446 - [PATCH v3 2/2] print_info: Show the remaining time of dump progress (by Pingfan Liu) 3438e8d . o Bugfix - [PATCH] elf_info.c: fix memory leak in get_kcore_dump_loads() (by Pingfan Liu) f10d1e2 - [PATCH] Error on re-filtering the dump file with no free pages (by Mikhail Zaslonko) deb8e1f - [PATCH] Fix get_kcore_dump_loads() error case (by Pratyush Anand) a569d63 - [PATCH] sadump: set info->page_size before cache_init() (by Hatayama, Daisuke) b98e6e0 - [PATCH] Fix the use of Xen physical and machine addresses (by Petr Tesarik) e765785 - [PATCH V3] elf_info: Fix file_size if segment is excluded (by Pratyush Anand) 88731c7 - [PATCH v3] Prevent data loss in last page of ELF core dumpfile (by Eric DeVolder) 622f0d7 - [PATCH] Consider not page-size aligned phys_end for paddr_to_pfn() (by Atsushi Kumagai) 25259e6 - [PATCH] Fix the regression caused by moving cache_init() earlier (by Atsushi Kumagai) be0461f . o Cleanup - [PATCH 1/4] eppic: Rename scripts to reflect validity of kernel version (by Kamalesh Babulal) b55b29f - [PATCH 2/4] eppic/vhost_net_buffers: Introduce changes for kernel 3.19 (by Kamalesh Babulal) 0a1d8ee - [PATCH 3/4] eppic/dir_names: Introduce changes for kernel 3.14 (by Kamalesh Babulal) 5c822a7 - [PATCH 4/4] eppic/keyring: Introduce changes for kernel 4.4 (by Kamalesh Babulal) 19fe701 - [PATCH v3 1/7] show_mem_usage(): calculate page offset after elf load (by Pratyush Anand) 4b0bed3 - [PATCH v3 2/7] initial(): call cache_init() a bit early (by Pratyush Anand) 8e2834b - [PATCH v3 3/7] x86_64: check physical address in PT_LOAD for none direct mapped regions (by Pratyush Anand) f136302 - [PATCH v3 4/7] elf_info: kcore: check for invalid physical address (by Pratyush Anand) f4ab689 - [PATCH v3 5/7] makedumpfile: Correct the calculation of kvaddr in set_kcore_vmcoreinfo (by Baoquan He) 4c53423 - [PATCH v3 6/7] makedumpfile: Discard process_dump_load (by Baoquan He) f3ff8c6 - [PATCH v3 7/7] mem-usage: allow to work only with -f for kernel version < 4.11 (by Pratyush Anand) 78cbb40 - [PATCH] Fix typo in the ERRMSG of function show_mem_usage (by Eric Desrochers) ade8512 (Closes: #857051) - [PATCH] Fix other typos in messages (by Atsushi Kumagai) b171374 - [PATCH] Fix compiler warnings (by Eric DeVolder) 04dab93 . * Update debian patches to latest release. . * Add file to the list of kdump-tools dependencies, it's used by kdump-config. . * Add watch file. Checksums-Sha1: a14c5f6a2e921843c4a75096c041ab92c8a98ad2 2197 makedumpfile_1.6.2-0.1.dsc 3f1b8092a71cf174c4685634982f1d5abc30d3e6 182149 makedumpfile_1.6.2.orig.tar.gz c9ada0b91f919385b62a8aea8175a8855d078280 31864 makedumpfile_1.6.2-0.1.debian.tar.xz 8067b96fbc8f712331d193170d0ce1094f6e2a61 5748 makedumpfile_1.6.2-0.1_source.buildinfo Checksums-Sha256: cec947b061095edfcd6276452449b3e704108abaa7da123ba75
Accepted taningia 0.2.2-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 18 Sep 2016 20:28:51 -0300 Source: taningia Binary: libtaningia-dev libtaningia0 Architecture: source amd64 Version: 0.2.2-2 Distribution: unstable Urgency: low Maintainer: Debian XMPP Maintainers <pkg-xmpp-de...@lists.alioth.debian.org> Changed-By: Thadeu Lima de Souza Cascardo <casca...@debian.org> Description: libtaningia-dev - Development files for lib taningia libtaningia0 - Taningia is a generic communication library based on XMPP Closes: 749046 838066 Changes: taningia (0.2.2-2) unstable; urgency=low . * Remove unreachable addresses from control and watch file. (Closes: #838066) (Closes: #749046) * Fix spelling in description. * Update Standards-Version to latest 3.9.8. Checksums-Sha1: 3977973a4189b421fe2bd655c9eb85f0313d7e62 1839 taningia_0.2.2-2.dsc f1520fb56eb51a3b074c54943a22973b2cce8b69 3408 taningia_0.2.2-2.debian.tar.xz 5ae99bc8d69ca55774d1bc51602d2f7ec1721219 43784 libtaningia-dev_0.2.2-2_amd64.deb 5e70aa95a9c89c04a1044d7e8366363d5d4e5ddd 59770 libtaningia0-dbgsym_0.2.2-2_amd64.deb 7b4023f8bcc5bf4ed26a15d93e2d1e22d3c32c8a 27536 libtaningia0_0.2.2-2_amd64.deb Checksums-Sha256: d0b4f72c76d8f750a236a4bd8d66535e968c77aa8637fdbc31e21dc42887f387 1839 taningia_0.2.2-2.dsc ff67251ef5696ea595e5e0abe55600f2ef84918f46b1b23d25546696a3f938fd 3408 taningia_0.2.2-2.debian.tar.xz 7943f2f6237498c841942324dcfdb23195eb9cdb81c78f696a9328697d64bcd0 43784 libtaningia-dev_0.2.2-2_amd64.deb c7c21e00a19250f735b215337058e94341265118b2f6a80a8c3b35109298414d 59770 libtaningia0-dbgsym_0.2.2-2_amd64.deb 348fda45745a1f6fc8f260730d547b40c829a47f0ef71ca75e82af4372a5dfcd 27536 libtaningia0_0.2.2-2_amd64.deb Files: d74437569f43243288d415ccc6cf7c3e 1839 libs extra taningia_0.2.2-2.dsc e4d80d687c26aceebe28faf5194c2317 3408 libs extra taningia_0.2.2-2.debian.tar.xz 70dfd8770fa2dc21e0b0a8e93202553f 43784 libdevel extra libtaningia-dev_0.2.2-2_amd64.deb 0d7b84e578358d5233e79c63d0063aab 59770 debug extra libtaningia0-dbgsym_0.2.2-2_amd64.deb 881b8459263cd99c3b083c16a14c98ba 27536 libs extra libtaningia0_0.2.2-2_amd64.deb -BEGIN PGP SIGNATURE- iQIcBAEBCAAGBQJX3y9tAAoJEAq6ZQNy/ZVxmVMQANveHxDBRQOrKCDddr7XlDbh 7q8gfA5/tyHhmlfuvpD9OcQNn0A3+JygmMxwDgl12QZ+Zar/rtfv2AIj3DEEbhRp VBEcDE6I0ISCV1rtIpUUIjUWAu2oSQ/28z18qGQy+sAKFewpsze6QIYQhVSEso2b rsKI4N03fNkl8e0N6rIk6cbFZz5RcZjrpNG2Fn36S0kDKBU6Vg2PrEqb+BmpGUy1 VKJoZPOxOQ7L8ptdDET5YHkLZvJ1fjzqAfESuAvUcJ+CXmNN1C8gNWYYgGe6b2Q1 Eei/a3tLCEFxffJ/sBkfe8qjHAQHYymv0XVI9HDxSEHnEGF589ZNkABG8VZDQbq/ /d5KCc5YpixIyHj3jjhirfyffqGOyffic5CqZib2f7p14Z7S4hoCaxuOFaXmp2Ng SHzYrZxglO5uyE7PZ+EYonar7aUt1GEWasWOm4yvB6umBed3l/OAgDThF4xvVTBA DueldAZGlJTw05QI4LiOj5oL9EZ4nziJvi6YObZxZFR3ALnUpnKP2mbm2JcZPz5p b5Q/2NZMl7icuawPzf0IG1Gdj7tOrFljMR0uEKwCgD3e/31ceQ89EVPXdCmTCEAW tW8XqkPaRswR9tvon+yJvZkEFWHE5avd0VdJyoSfISaG42Mm4gEx/ykXntUmHpFC UYBo1KGMZPyH7ugW9yCj =ERjF -END PGP SIGNATURE-
Re: interested in (co-)maintaining midori
On September 13, 2015 9:33:52 PM GMT-03:00, Sergio Durigan Junior <sergi...@sergiodj.net> wrote: >On Wednesday, September 09 2015, I wrote: > >> On Monday, August 24 2015, I wrote: >> >>> On Friday, August 14 2015, Andres Salomon wrote: >>> >>>>> Your work was done back in June, so if you prefer I can provide >>>>> patches against your branch to implement/fix the issues I have >been >>>>> working on. It won't really matter much, I think: in the end, >we'll >>>>> have to use the "official" repository anyway and patch it. >>>>> >>>> >>>> That would be highly preferred, simply for reviewing purposes. I'm >>>> also happy to rewrite parts of my history to, for example, not >include >>>> the -O--buildsystem stuff. But the existing git history is useful, >and >>>> I'd rather work from that. >>> >>> OK, I've done it: >>> >>> <http://git.sergiodj.net/?p=debian/midori.git;a=summary> >>> >>> It's the same link, but the repository is a new one, based on the >>> official repository. >> >> Just another update. >> >> I've re-created the repository above (the previous version contained >> some mistakes, and I thought it made sense to restart from scratch). >> Now, you can find the latest version of Midori (0.5.11, released a >few >> days ago) along with all the other changes that I had already made. >> >> Still builds successfully, and I'm using this latest version without >> problems. IOW, everything is ready to be used in Debian, and I'm >pretty >> happy with the current state of the repository. > >One (last?) update. > >I have upgrade/recreated the repository one more time now. Thadeu >Cascardo pointed me to two lintian warnings that I had not seen before >(they're fixed now), and I've cherry-picked Andreas's commits (those >that import the NMU-0.2 and merge it to master), so now I think >everything is *really* covered. Oh, and I've searched the BTS and >found >two bugs that requested a new version to be packaged, so I'm closing >them in the changelog. I intend to do a full bug triage once the >package is back to life. > >Just for the record, I've kept *all* history from the previous git >branches, so absolutely nothing is deleted nor lost. > >In other words, the package is ready to be re-uploaded. > >Thanks, Thanks, Sergio. I find the repo and package in a good state for an upload. I will do it tomorrow night, if there are no further strong objections. Thanks Andres for his work as well, and all the others for their past contributions. Cascardo. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Bug#784405: ITP: rnetclient -- Client to submit the Brazilian Income Tax Report to the Brazilian Tax Authority
Let me add here some of the history about rnetclient and IRPF Livre, concerning legal and government matters. As already said, Oliva has been publishing IRPF Livre for a while. He decompiled that software when it was using GPL libraries, which would make it GPL software, even though SERPRO or Receita didn't distribute it on the same terms. That could be interpreted as a legal liability, but he has not found any problems since then. Here is what has happened instead. As Sergio also pointed out, Oliva has gone through the process of trying to get the software released, claiming that recent law for transparency meant the government needed to publish it. SERPRO, who is the developer of the software, claimed there was secrets in the software that would allow people's income to be leaked. That is a lie! As Oliva pointed out in his counter-claim, his own IRPF Livre would allow such a leak if that was true. And that would be a huge security breach in the whole process of tax paying/refund. Unfortunately, the judge decided against the publishing of the software. But Oliva stated that he has done the reverse engineering, publishes the software, and no action against him has been taken. When I was developing rnetclient, I found some concerning problems in its trust model (software trusts certificate that is shipped with itself, certificate has a weak password, easily found on the software, even software hashing checking can be easily circumvented, software is not distributed with any signature - not even over https). I thought that publishing that would put me into trouble. I gave a talk on a big event in Brasil (FISL, 5k people, 300 watched the talk live, video was published, SERPRO president was at FISL), and no action has been taken against me. Oliva and I even talked to SERPRO president at the time, he couldn't care less, or even seemed favorable to what we were doing. I have been shipping rnetclient since then, 2013. This year I even managed to have it updated at the same day that Receita has published its own software (they didn't do Betas this year). The fix came the next day. I have an intention to publish a version that should work for years to come, until the protocol breaks from what it has been for the last 5 years. And, in fact, it's still useful to submit corrections to previous years files. So, if you have to publish 2013 and 2014 again for any reason, 2015.1 can be used. And the software will still be useful for at least the next 5 years, when people might still want to resubmit their 2015 files. Unless Receita breaks the whole thing, as I mentioned, but hasn't done for at least the last 5 years. About my own process of reverse engineering: I did some decompiling and read some of the code. I wrote a very small Java class to override the certificate verification, allowing me to do some MITM. Most of the process after that involved me writing tests to simulate a server and a client, and see how the client and server responded. Reading the code just helped me get the basics on the encoding so I could write the tests. After that, I wrote the program from scratch. Even though it was not completely clean room, it's hard to conceive there was any copy of SERPRO's code. Their code is in Java, with its own APIs, I used C, with GNUTLS, BSD sockets, zlib, my own decoding of the file that came after I started writing the tests (so I didn't read any code related to that). Also, Brazilian law says: Art. 6º Não constituem ofensa aos direitos do titular de programa de computador: [...] III - a ocorrência de semelhança de programa a outro, preexistente, quando se der por força das características funcionais de sua aplicação, da observância de preceitos normativos e técnicos, ou de limitação de forma alternativa para a sua expressão; Which means that it's not a copyright infringement when a program is similar to a preexisting one because of its functional characteristics, or because it follows technical or normative references, or there is a limitation for other forms of expression. Hope that helps moving the discussion forward. I, at least, found it delightful to write this for posterity. Cascardo. signature.asc Description: Digital signature
Accepted gsasl 1.8.0-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 10 Jul 2014 21:50:24 -0300 Source: gsasl Binary: libgsasl7-dev libgsasl7 gsasl gsasl-dbg Architecture: source amd64 Version: 1.8.0-3 Distribution: unstable Urgency: low Maintainer: Debian XMPP Maintainers pkg-xmpp-de...@lists.alioth.debian.org Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Description: gsasl - GNU SASL command line utility gsasl-dbg - GNU SASL debugging symbols libgsasl7 - GNU SASL library libgsasl7-dev - Development files for the GNU SASL library Closes: 753598 Changes: gsasl (1.8.0-3) unstable; urgency=low . [ Simon Josefsson ] * Add README.source. . [ Thadeu Lima de Souza Cascardo ] * Use autoreconf on rules (Closes: #753598). * Build against libgnutls28-dev (Closes #753037). Checksums-Sha1: 39faac60c246eabf90734ba19af516a5beed5fcf 2291 gsasl_1.8.0-3.dsc e93d0e4f99ef8e7b9f379a71e279d5f8b6b3ce2d 6144 gsasl_1.8.0-3.debian.tar.xz 3a9f49a6504088fb8cff95bf1393c311b6d8bd53 273408 libgsasl7-dev_1.8.0-3_amd64.deb 301ace21ab6d5a6331b571c91c1915b38c5dc636 205452 libgsasl7_1.8.0-3_amd64.deb 6033f35a50943e6dbf8b3482bbd75f9ff748202b 204582 gsasl_1.8.0-3_amd64.deb 3f485c24316c1daeef58604f4912011303138b81 272774 gsasl-dbg_1.8.0-3_amd64.deb Checksums-Sha256: c2bae95d675751c03012546eacd5d7419be88374cf5035e56321de87e9b1e76d 2291 gsasl_1.8.0-3.dsc 8c189c89b6b43936c9bb25f395e74fa2e48ec851acd4ec21818788fa7e010794 6144 gsasl_1.8.0-3.debian.tar.xz 54845d65f767b2686da3e8fd374ecc2861b3e96a95f77b6a282a531fc7ac02f6 273408 libgsasl7-dev_1.8.0-3_amd64.deb cb2f9fd042b79155efa00e835e530bc76656aefd191c854d233e17a401d7f4c4 205452 libgsasl7_1.8.0-3_amd64.deb d64b97135645d0c400a6157ff32a2700dcbede39d8726549a1a58259e6178cc7 204582 gsasl_1.8.0-3_amd64.deb e8102665225dd355d2a01182ec24c5be2396279115de2d7db3efd01c5bb23ccb 272774 gsasl-dbg_1.8.0-3_amd64.deb Files: 249f762a4c79e65418e72acc33701aa7 273408 libdevel optional libgsasl7-dev_1.8.0-3_amd64.deb eecc8f80ecf4838823edc93b5148a24d 205452 libs optional libgsasl7_1.8.0-3_amd64.deb 1197084442fd395467790778324f55e9 204582 devel optional gsasl_1.8.0-3_amd64.deb 9684d05391eaa6b5e26fe7d250dd8976 272774 debug extra gsasl-dbg_1.8.0-3_amd64.deb 5cba394a93495712d8456cb706204160 2291 devel optional gsasl_1.8.0-3.dsc 9029029c44bc09db5d28c92e48d06a84 6144 devel optional gsasl_1.8.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT07HCAAoJEAq6ZQNy/ZVxJw8P/RZanpsNm21W3HbIiDmEpmsW jA1/uPgLeMyWb07AA6ec1wz0pv4T6AZUzTVpgjqJdDkdquPy2s+IgpSjKyPEaNbC wRzxDk8QSa80XTFM5r4KbEgakW7/DGzZtf/4TFnnD1eCHmsDgY23eFG9b4AWMVih k9eVmtkDaxC9yZ4h2G5QtIOysXuRfzo7m2dC/4ia//OSpFG5D3h/uwe+zNGdoofM olTonJl4iHbNcwsyCsdtqlBi8T59/tlec2TU6ozg6S+SHsddqToXAwaYVNzRap7f GV7JcblDPwZ1ot2MS/tlJkDjoXR+5Mos4vzUF+SRCVOjJGOkVZsKP6P5AYCM44kN eCbGgMNoWDTwIUhdlPf+ubo2GoWU1KagzLg7PUXzF1B6Z1MYvwlk88ACt3opHKSM O0aDeoCY8JwXxuz9PuEObogZHSogPI/PnXuarCrjRA7D3NFDiu39JfUj85YoodMN fT+1HK5szkT8VChhQ9onnzr1/ruxUTWMEkHDSIyX5Ffp80BNUl8KGCtHbRH0/Oq5 dNboAse72cf4oNkM/JTkoMku0IY7SUfz1M1VMHcXU8IhQ+La5MSrYmDy3xxsqE1k NRaTdeS0554m3RZlrtuh7czd8t4eoExpmWauD1tJvgadHMsz2+h5sETZQ7qJzrLn 7xbvOY3WiC+/I8urczUl =050f -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xb41j-0004xf...@franck.debian.org
Re: ITA: jabberd2 -- Jabber instant messenger server
On Wed, Dec 26, 2012 at 12:53:53AM +0100, Willem van den Akker wrote: Hi, I havent received any response about my ITA message for Jabberd2 (see below). It seems the current maintainer is MIA. Is it possible someone of the pkg-xmpp-devel group can reply? I would like to adopt it, but must get a chance to get so ;) Greetings, Willem Hi, Willem. Jorge Salamero used to be the main maintainer of jabberd2. I accepted to be a comaintainer in the xmpp team, which has seen most work coming from Marcelo Metal on some Javascript XMPP packages. I have no problems with you either working with us on a common repository as a team to maintain jabberd2, or adopting it entirely. Of course, we'd rather see it as a community maintainership, using the xmpp infrastructure as it is already setup. Do you have a git repository with your changes? Regards. Thadeu Cascardo. On Thu, 2012-12-20 at 23:28 +0100, Willem van den Akker wrote: Package: wnpp Severity: normal X-Debbugs-CC: debian-devel@lists.debian.org Hi, I am interested in adopting jabberd2. Now a new version of udns is uploaded into unstable, I hope we can update jabberd2 also. I have placed a new version online: https://mentors.debian.net/package/jabberd2 I hope you can check if it is valid and upload if it is. If not, I will correct it ;) Greetings, Willem vdAkker signature.asc Description: Digital signature
Accepted gstreamer-hplugins 0.2.0-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 22 Jul 2011 16:09:37 -0300 Source: gstreamer-hplugins Binary: gstreamer0.10-hplugins Architecture: source i386 Version: 0.2.0-2 Distribution: unstable Urgency: low Maintainer: Samuel Ribeiro da Costa Vale srcv...@holoscopio.com Changed-By: Thadeu Lima de Souza Cascardo casca...@holoscopio.com Description: gstreamer0.10-hplugins - Holoscópio plugins for GStreamer Changes: gstreamer-hplugins (0.2.0-2) unstable; urgency=low . * Added me as Uploader. * Change homepage to that of Landell. * Fixed git repository location. * Update to last policy version. * Add license for livekeeper. * Add plugin descriptions in package description. Checksums-Sha1: 6b719e57366029d415909b9ed203216895bb7696 2122 gstreamer-hplugins_0.2.0-2.dsc f2ffbbdc9ad4834e0b325771ddb0f37583dd6d5b 316641 gstreamer-hplugins_0.2.0.orig.tar.gz 4961a21dd4f628eae21809a2cf0f8e2219a6a888 1686 gstreamer-hplugins_0.2.0-2.debian.tar.gz a10e59fe8152d84a972ef766428fd9160feaf5fd 11160 gstreamer0.10-hplugins_0.2.0-2_i386.deb Checksums-Sha256: 803d90b1e2657f031ea632d88f6f4bcff47f27346ba227bb955d0323bb262fbd 2122 gstreamer-hplugins_0.2.0-2.dsc f71a5b1e7695776dcda178b96e82d5c0d957f300e885df46472af575c371b29f 316641 gstreamer-hplugins_0.2.0.orig.tar.gz 3dd4600cb592e4fa0ded4c467f3c04ba4c161b921175a90df21da69bf1643552 1686 gstreamer-hplugins_0.2.0-2.debian.tar.gz ac28f55a337f3ec3c412f040dee56ff344a59d65e8f267a40b4718a902a1ed40 11160 gstreamer0.10-hplugins_0.2.0-2_i386.deb Files: 8b23abbf22e585dba4f3cecd154d73bd 2122 libs optional gstreamer-hplugins_0.2.0-2.dsc 33f568adcfebd19c5d4602e21ca77155 316641 libs optional gstreamer-hplugins_0.2.0.orig.tar.gz 0a4fe36bdfa44caa0df8156f3f9aab9e 1686 libs optional gstreamer-hplugins_0.2.0-2.debian.tar.gz 964846542f40e8c382806efc77032020 11160 libs optional gstreamer0.10-hplugins_0.2.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOKeL5AAoJEAGffgcyZKXEB5QP/jmZxHNKTREAxYsIKbZze/Mp 6UIxqQmcuGavT/ugIokplWt5ROznIBS880dGKcBTwTEBW6pKKU1t52b3pm0uqSFJ JyxyX+s7ybZYBCn4/5DONjIGzCqB1u9rQ+vmXzwKQbnv5q9RONuiUvuf2Osi8c63 TLMKblkGiQY9F7qoV7GVCndfk004boNPTnSF2EQ17z3wW3ZwrRc2J8rcfQqQ/B0w rIAfNB8hPiiJERo9ASfvHTK64ZLK8yED0bZp5gUIsLOOsAFnG0HerzFvg0d4lmQE 6b+eTNOjkcnAtLwpmmCZJD4KLzx6zGESwojmG5BFKVcXsKKKXyuIDaPmnA/z8+x1 q2sgQPF9DowdGW7ppVMnfvrzDLYO22LFG/UBMtyl3oIKw8DGjtQAoTushwaj/5mw ZrKfS8gnzynZxRoCIn5Uz7cFNNWtvexgYigAKY9rNGBziZC6UXjD4e6tJYOA33N1 opuShXIq5Mrg+ySJKQIDrRxltmR4QCz3ejFne8ceGjCyssDcVosGynLvGZz6n9Qf hMvkCNsRMPxtDfHh2ACn0Sr12K2lNHwRu7huNhYO0e7CopI2nKaxHtakJDE/vwub I3qPxa/Wg3ifffn33su8s1cG3T01fHnNjDpA2xlIhoU+M32TDZn4dkrDu1rk/JOR k3jXUlvy8J7IwhOSCbuB =jbCp -END PGP SIGNATURE- Accepted: gstreamer-hplugins_0.2.0-2.debian.tar.gz to main/g/gstreamer-hplugins/gstreamer-hplugins_0.2.0-2.debian.tar.gz gstreamer-hplugins_0.2.0-2.dsc to main/g/gstreamer-hplugins/gstreamer-hplugins_0.2.0-2.dsc gstreamer-hplugins_0.2.0.orig.tar.gz to main/g/gstreamer-hplugins/gstreamer-hplugins_0.2.0.orig.tar.gz gstreamer0.10-hplugins_0.2.0-2_i386.deb to main/g/gstreamer-hplugins/gstreamer0.10-hplugins_0.2.0-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qkynb-0003ad...@franck.debian.org
Bug#619348: ITP: drupal6-trans-pt-br -- Brazilian Portuguese translation for Drupal 6
Package: wnpp Severity: wishlist Owner: Thadeu Lima de Souza Cascardo casca...@minaslivre.org * Package name: drupal6-trans-pt-br Version : 1.5 Upstream Author : Portuguese, Brazil translation team * URL : http://drupal.org/project/pt-br * License : GPL Programming Lang: po Description : Brazilian Portuguese translation for Drupal 6 Drupal uses English by default, but may be translated to many other languages. . This is the Brazilian Portuguese translation. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110323021454.3487.25846.report...@nautilus.holoscopio.com
Re: O retorno da Super Vaca
On Wed, Jan 19, 2011 at 02:04:21PM +, Rafael Cunha de Almeida wrote: O Valéssio, o marcot e o eu criamos, populamos e anunciamos o site, respectivamente. Se ninguém tiver nenhuma sugestão para estar fazendo a partir deste momento então sugiro que a gente esteja já anunciando o site da super vaca. Estamos todos se acordando? http://www.supercowpowers.co.cc Por mim, manda ver!! Assim que sobrar algum dinheiro na minha carteira, tô fazendo minha doação. Só uma dúvida: algum motivo pra não aceitar doações menores que R$50,00, mas sem a camiseta? Abraços, Cascardo. signature.asc Description: Digital signature
Accepted jsjac 1.3.2+dfsg-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Aug 2010 23:48:53 -0300 Source: jsjac Binary: libjs-jac Architecture: source all Version: 1.3.2+dfsg-1 Distribution: unstable Urgency: high Maintainer: Debian XMPP Maintainers pkg-xmpp-de...@lists.alioth.debian.org Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Description: libjs-jac - JavaScript Jabber Client Library Closes: 593799 Changes: jsjac (1.3.2+dfsg-1) unstable; urgency=high . [ Marcelo Jorge Vieira (metal) ] * Imported Upstream version 1.3.2 * Changing my email for Debian address * Using minified file instead of creating a symlink to it . [ Thadeu Lima de Souza Cascardo (with mentoring from metal) ] * Imported Upstream version 1.3.2+dfsg. Remove some non-free files. (Closes: #593799) * Use DH 7. * Create get-orig-source rule to remove some files from source. * Do not use jsmin and pack file using PHP Javascript Packer. * Switch to dpkg-source 3.0 (quilt) format. * libjs-jac should depend on libjs-xmlextras, instead of shiping its copy. * Add BSD-like license from source file. * Mangle version in watch file. * Update Standards-Version to 3.9.1. * Install jsjac.uncompressed.js and create a jsjac.js symlink to it. * Use yui-compressor to pack javascript. * jsjac currently does not work without its copy of xmlextras. * debhelper overrides need versioned build depends (= 7.0.50~). Checksums-Sha1: ac9ecb97e28885c373efa8fd162ac334fa531095 2016 jsjac_1.3.2+dfsg-1.dsc 616ddd942762ae8a935af90345d882463d6af836 135610 jsjac_1.3.2+dfsg.orig.tar.gz c2cd645d8b9a705a338d2fef0b056b012f9ca8d6 13811 jsjac_1.3.2+dfsg-1.debian.tar.gz ebb43b33760c332a07e8f4ba7573cc03ad172c86 198006 libjs-jac_1.3.2+dfsg-1_all.deb Checksums-Sha256: 3fd5a1c0f17d9bb4d715377e60f52109143c8504ced49b46ecf00de9ff4d86f4 2016 jsjac_1.3.2+dfsg-1.dsc 140ec020e23464c2e592be4e17e26f5d008389d84a593eeabb94a03e4ecf5f4d 135610 jsjac_1.3.2+dfsg.orig.tar.gz 8ace449e84e7e2bafeef3f6ad39192413547c8fb359b8b99c48cb4069387caa5 13811 jsjac_1.3.2+dfsg-1.debian.tar.gz 62db9981b8f2fe2551262bc35dd432f7e68158d2abb033a93916082bc4e3b7dd 198006 libjs-jac_1.3.2+dfsg-1_all.deb Files: a6345c96895094e73b467703c350d2f9 2016 web optional jsjac_1.3.2+dfsg-1.dsc 6120b1687bd803217c946996eefaaec9 135610 web optional jsjac_1.3.2+dfsg.orig.tar.gz 0dc5fe272caa8281cc9ba61e954eafe1 13811 web optional jsjac_1.3.2+dfsg-1.debian.tar.gz 9347d06625093f9d789d9ab67f47bef1 198006 web optional libjs-jac_1.3.2+dfsg-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCAAGBQJMduj4AAoJEAGffgcyZKXE9skP/314KIu+s9Sj1LQoNqPKrL1J Ah9yQ9l7I47E44SSesGB7iNujbFgC2fTImV6HW3h5EzXeY6484hDzIxErosTLa77 4Kajo6Ym3BqiDsP61qLUUgHXMUnV0GgXZX6Jj79JbOoYubCeQiWffRxMAtH+ycKu ebAXeaY55IYYAL/qs3f5Y/RHXIyAnF6sLfz0vSG/hkoXIcl833mSpFmNNBZRRnrJ wEUYme3xqvvt+DDbo73EeDS15jqtzxONruMNvLPGO5Gj2Zhem7y8xqVjHTkg5qBT NByyENqbDelORAJv/Q2jE04/L9dx7JNrYJVPvqSsFQEqBxWjL4/69V4IF6xfjdiV lWaNMAC/YW1Yq4oBgpR9y+Dh9GzUMg7ya6iEmA4TFyh7jXo1aWo5inf2ER3VEC3r wxJ/rApFF7EqS34YM2EGtlAVf/gdi6oncBROvvu95Y1UXLzy2og8uFooBDDQtc0O jj7aiVEHQqKJPq1OvlXpIxY2/xotO3MmLREYFbPP14l9FxdUzXuL9dIwg/iSHTG5 XXHG6UzLCP9xMLZPcdqoMpHiVNfVA2w7DXsDP2koBJ1V2piz2K+qfx6KfB+FVr4i 1y0QTLrL2PUW+d8QMrhPIMrqLE80dpLSZhb8SGObe18Ewm6PlGf6T7chNdC6PTUj NsJWOdAft1ya+nm57+zQ =RV7M -END PGP SIGNATURE- Accepted: jsjac_1.3.2+dfsg-1.debian.tar.gz to main/j/jsjac/jsjac_1.3.2+dfsg-1.debian.tar.gz jsjac_1.3.2+dfsg-1.dsc to main/j/jsjac/jsjac_1.3.2+dfsg-1.dsc jsjac_1.3.2+dfsg.orig.tar.gz to main/j/jsjac/jsjac_1.3.2+dfsg.orig.tar.gz libjs-jac_1.3.2+dfsg-1_all.deb to main/j/jsjac/libjs-jac_1.3.2+dfsg-1_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ookzo-0003wp...@franck.debian.org
Accepted libntlm 1.2-1 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 30 Mar 2010 12:26:30 -0300
Source: libntlm
Binary: libntlm0-dev libntlm0
Architecture: source i386
Version: 1.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian XMPP Maintainers pkg-xmpp-de...@lists.alioth.debian.org
Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org
Description:
libntlm0 - NTLM authentication library
libntlm0-dev - Development files for the NTLM authentication library
Closes: 554722
Changes:
libntlm (1.2-1) unstable; urgency=low
.
* New Upstream Version. Closes: #554722
* Add ${misc:Depends} to binaries' Depends since we use debhelper.
This makes lintian happier.
* Update Standards-Version to 3.8.4. We still use GNU style variables
for architecture specification, but that's because we use them with
upstream build system, as allowed by policy.
* Change Maintainer to XMPP team and add Simon Josefsson as uploader.
Checksums-Sha1:
a30866730621ff104fc9f667a11231fbad82e984 1764 libntlm_1.2-1.dsc
27538a3375690a37574fa991fbd327d150d8b505 439103 libntlm_1.2.orig.tar.gz
6a8819b81d2a78aacb0aa48cd7e2e819bb55d24a 2686 libntlm_1.2-1.diff.gz
79cb2e0ff5e9414c7fb4f66afe38f46a2e00c423 25524 libntlm0-dev_1.2-1_i386.deb
d7edbed3c36ec1fc4b46722947367301b8ca5339 18118 libntlm0_1.2-1_i386.deb
Checksums-Sha256:
448e1f7b179fda091ca272bb28bb1aa9fc8846887d7223125149003f348f2cb5 1764
libntlm_1.2-1.dsc
7f5f64e561bf156f918536174c7fc86a20138126c6aaa441d6cd224c52a8db68 439103
libntlm_1.2.orig.tar.gz
e858112cbbe44c53fe1416820a345060174d4906be4852eab641d7b862d6c5b5 2686
libntlm_1.2-1.diff.gz
ba0746a891273b6eb1556144743e86d56c02f3a77606ed162072c90936a9c1dd 25524
libntlm0-dev_1.2-1_i386.deb
2db33bd33f794321f66bbeddfcbea61899246d5a27b99de9124e588bfe45cec0 18118
libntlm0_1.2-1_i386.deb
Files:
900dcc4e08b7d07f3b174ee062137415 1764 libs optional libntlm_1.2-1.dsc
13b40af721b29005652fb429a3ae9582 439103 libs optional libntlm_1.2.orig.tar.gz
fcfe3badce261282b5fb9455e07ecca6 2686 libs optional libntlm_1.2-1.diff.gz
8baccf00e7f414a0bb1053126c1d6393 25524 libdevel optional
libntlm0-dev_1.2-1_i386.deb
e20408f757540a260682a323e18b6cc8 18118 libs optional libntlm0_1.2-1_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMV0BdAAoJEAGffgcyZKXEqBIQAIfjZtIsqfkVJQOU+v2DTh53
JXHHK3uae5wfY99eFE1Wi+XRhm30aqMZQef5l4wOLdcjGjn9yFCZ92iUF4IJO8kB
1I06p9tCUpVVBRTqr41nay28URlI4VoV84bzqn+/mFzVIMjMMAUz19PtlWp2FS9g
dlVZ40QnybvMBsD06c524Zemutd4kZcWkUhPlhjXDjuGgx+dR7q/BZGZWwbWE8yG
FC1sOEz/Rywro7jn9yp2gOBEO3hAYork+NGaFxnRqKqSgjM5AD8mJmg2iVDXYaJe
We3vOfbYAPRtFjBukVIELu3ZjLNPP/3c48e+AySeq/OxOaeByFs/Cc9AxsLvPFCs
kVMVdW+w2ZM/gAwbqMkT7jkBX7ieTLBwTyRUv2H3fpcqa30fx6UJQr8RPAWp6x46
Dno6AzcDu9FofcjzRxCwp59LTB1dO8Dt+rxSATgRkVOiTh+Vn9dYIB95aFXXWJ//
GKzC8WVo523xU0MZ8Ix+VRIhLu+sKBPIMrlHuyKQsATbZwHReb24ygxiXg9A6VK4
1Tlhmy2disrUwVSmaeBXGABt4WydVotrvMCkt4gzlVuUPwhthhFJvsWfF+JeKAl8
CIRSxtcvFa+JlXVpMOIu+taOcUGNs462MaB/J0QjOUxxNlZT24yyDB8RvzIsOOP0
J7OBrsHS5lZi82l33nAA
=rZAm
-END PGP SIGNATURE-
Accepted:
libntlm0-dev_1.2-1_i386.deb
to main/libn/libntlm/libntlm0-dev_1.2-1_i386.deb
libntlm0_1.2-1_i386.deb
to main/libn/libntlm/libntlm0_1.2-1_i386.deb
libntlm_1.2-1.diff.gz
to main/libn/libntlm/libntlm_1.2-1.diff.gz
libntlm_1.2-1.dsc
to main/libn/libntlm/libntlm_1.2-1.dsc
libntlm_1.2.orig.tar.gz
to main/libn/libntlm/libntlm_1.2.orig.tar.gz
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ogdlw-0003ap...@franck.debian.org
Aptitude wishlist bug with a package - how to get it merged?
Hello, Daniel. I've submitted bug 497206 for aptitude with a patch attached almost two years ago. It's a new feature, to allow packages to be grouped by source. It's usually easier to upgrade all packages from the same source, without having to look for (and sometimes guess) what are the other packages from that given source package. At that time, I've got some feedback (my first implementation required a change to apt), and have responded with another patch. I've been missing some aptitude upgrades or rebuilding it ever since. This is a simple patch, since it looks like very much other code already in aptitude to group packages by other criteria. I know aptitude has lots of reported bugs and maintaining it must really take a lot of time. I would like to know what I can do to help get this merged. Unfortunately, I cannot commit to co-maintain aptitude. But I could help fixing any bugs that arise from my patch and those come to my knowledge (perhaps, I should subscribe for the aptitude bug list for a while). At last, I would like to thank you for developing and maintaining this great software. Cheers, Cascardo. signature.asc Description: Digital signature
Accepted apt-listchanges 2.84 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 04 Jan 2010 12:17:21 -0200 Source: apt-listchanges Binary: apt-listchanges Architecture: source all Version: 2.84 Distribution: unstable Urgency: low Maintainer: Pierre Habouzit madco...@debian.org Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Description: apt-listchanges - package change history notification tool Closes: 172113 510618 Changes: apt-listchanges (2.84) unstable; urgency=low . [ Christian Perrier ] * Fix typo in Polish translation. Closes: #510618 . [ Thadeu Lima de Souza Cascardo ] * Introduce the --reverse option to list entries in the reverse order. Closes: #172113: Checksums-Sha1: a8d3c7ee275bbde31f066c66af6d678e01f4cab3 1386 apt-listchanges_2.84.dsc 905a20311ed598ec61c3976adcc69e8654d4e449 99691 apt-listchanges_2.84.tar.gz bdad2bd6837333563d458a78686fb5dd9bc48ac3 80898 apt-listchanges_2.84_all.deb Checksums-Sha256: 31c05aaf69946c3f924f6aec610272485b14902372c49e3849428455d4e5623d 1386 apt-listchanges_2.84.dsc 69df45d6c91ae72d109c3b34b51d3099aca13ee388c83057eef940e55474e8a3 99691 apt-listchanges_2.84.tar.gz 77d6cb92bbd777a1e8c60b5402b356ec069d30fd17054104241211e80588cfe8 80898 apt-listchanges_2.84_all.deb Files: abcc088065a1a4b162c308ca9d99e2f4 1386 utils standard apt-listchanges_2.84.dsc 644eedd67f74622d330874114e634212 99691 utils standard apt-listchanges_2.84.tar.gz 822a321f729ed48c36217ece25238a56 80898 utils standard apt-listchanges_2.84_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBCAAGBQJLQh9uAAoJENIA6zCg+12mxlsH/jnXLR0vnlBipqzf1NcATju4 3+AvYhdABl5F20xP3zRtzZjvYcOXd7/vTGpxxlP901Bt+I7rVAxxWp4NetCcplJe O0ETlV5QMMjJ4/358ChogTRgrUcasX8m/ZMwl3pRxKVddH7nxKqHbN6Oe8dD+qY5 9ziQzuwIrj01++rKN8H+LhWKicyLcmYKB1YYZ9WLvety3HnjyjcztjKTwtes6za0 vLnAwEumMVn5KrGBUos+ZmOlPlWz5GGcV/V5BRy5oXAwZttdHAmvh229KfGfy7GS gB7jv//l3nTHUKdGok9SL7Z6CCkfWmUXYUUpf2IuUM+TewFyDt+4lqgcAmMyftA= =zth0 -END PGP SIGNATURE- Accepted: apt-listchanges_2.84.dsc to main/a/apt-listchanges/apt-listchanges_2.84.dsc apt-listchanges_2.84.tar.gz to main/a/apt-listchanges/apt-listchanges_2.84.tar.gz apt-listchanges_2.84_all.deb to main/a/apt-listchanges/apt-listchanges_2.84_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libntlm 1.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 11 Jul 2009 22:49:39 -0300 Source: libntlm Binary: libntlm0-dev libntlm0 Architecture: source i386 Version: 1.1-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Description: libntlm0 - NTLM authentication library libntlm0-dev - Development files for the NTLM authentication library Closes: 471587 Changes: libntlm (1.1-1) unstable; urgency=low . * New Upstream Version * Remove test.txt from debian docs, thanks Ted Percival. Closes: #471587 * Backup and restore autogenerated files. * There's no /usr/share/pkgconfig/ any more. * Remove autotools-dev build-dependency. * Complies with Standards Version 3.8.2. Checksums-Sha1: 24b605b6d1347602de884fc5cbf60a0e400cb8d5 1008 libntlm_1.1-1.dsc d7608bea4820cdf879a5b10bc956391fb3973f08 430158 libntlm_1.1.orig.tar.gz a2da238d067eeb3d77b2c83b83ad5d22750b3301 2443 libntlm_1.1-1.diff.gz 6ff7323fd4a6d008f8d5bb0686729fce8df5ab98 24432 libntlm0-dev_1.1-1_i386.deb 8c4bfe2a5a91690ba9365b6bde083d26f7e0fbd0 17208 libntlm0_1.1-1_i386.deb Checksums-Sha256: f596fb3339c78ca20920c444553fe8aabb6824e3632a6bf2dabb6007c89ddaa6 1008 libntlm_1.1-1.dsc 738f1ae216b7a1d28e6f370e82a4ae1ea6b47954f9a4155f821dd005b7fabf2f 430158 libntlm_1.1.orig.tar.gz f5752d2e4951fd53a3b88dfd76c7676a54a09190cd8f9eaa6c7a3a9f8b2335e8 2443 libntlm_1.1-1.diff.gz 1755349dc9a550d672258a0175d1e0f38dcc7e55295319c6ce055285c1206fdc 24432 libntlm0-dev_1.1-1_i386.deb e839f34b6607705eddcf4b4c8a70ee420f3683f6204c3124537e5ac1b0ff15fe 17208 libntlm0_1.1-1_i386.deb Files: c9009550d38c6bfb74982c32d075d074 1008 libs optional libntlm_1.1-1.dsc 9ae0b6fa77c3f789e68db1fd708159e1 430158 libs optional libntlm_1.1.orig.tar.gz 26e3c98d9c8cd1ef426a65c2b4341e7b 2443 libs optional libntlm_1.1-1.diff.gz c941173544a900f7ecffac15b6e9f107 24432 libdevel optional libntlm0-dev_1.1-1_i386.deb fb974d31c1fc8170abedb1c8c42323c7 17208 libs optional libntlm0_1.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAksNsT4ACgkQQUuEI2/szeCRNQCdHfsrlC+3FX8DTUI9W8v6Pmcm pXwAnRJCIBfhpU86iL3UaenWFfME68eL =01Bn -END PGP SIGNATURE- Accepted: libntlm0-dev_1.1-1_i386.deb to main/libn/libntlm/libntlm0-dev_1.1-1_i386.deb libntlm0_1.1-1_i386.deb to main/libn/libntlm/libntlm0_1.1-1_i386.deb libntlm_1.1-1.diff.gz to main/libn/libntlm/libntlm_1.1-1.diff.gz libntlm_1.1-1.dsc to main/libn/libntlm/libntlm_1.1-1.dsc libntlm_1.1.orig.tar.gz to main/libn/libntlm/libntlm_1.1.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted udns 0.0.9-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 11 Jul 2009 18:17:24 -0300 Source: udns Binary: libudns0 libudns-dev udns-utils Architecture: source i386 Version: 0.0.9-3 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Description: libudns-dev - async-capable DNS stub resolver library, development files libudns0 - async-capable DNS stub resolver library udns-utils - Some DNS-related utilities built on top of udns library Changes: udns (0.0.9-3) unstable; urgency=low . * Rewrite NEWS file using Debian changelog format and use the same date as the last release, when it was written. * Add Homepage control field. * Complies with Debian Policy version 3.8.2 (no changes required). * Rewrite descriptions to inform more and use punctuation, as well as capitalize UDNS name. Checksums-Sha1: f375ba1b3fbfcaf0c664a8ca71dc44025b60934e 1014 udns_0.0.9-3.dsc 342918b450dd04d6ebdfd50981a6d78a6b86e634 6135 udns_0.0.9-3.diff.gz 01df1cbddbe0e0e3bd2e1d482cd4f9a352bf0a00 33614 libudns0_0.0.9-3_i386.deb 390dde58ab91c606da1baaba02339f115639e9e7 57672 libudns-dev_0.0.9-3_i386.deb 32074d0fd746e848bf68f081839d7dde73549912 31342 udns-utils_0.0.9-3_i386.deb Checksums-Sha256: 675d582ae39bda98a96f3fcd491423399a5e8fce55f66cc52284d426a886 1014 udns_0.0.9-3.dsc 567c394d8ef548badab5a46be48e9db6aab3630dae134182b7cc5ef7ef90cc3a 6135 udns_0.0.9-3.diff.gz b3a9a4b2825687c412f59473b3b48644e802f2159851fb50794169bf3d220d37 33614 libudns0_0.0.9-3_i386.deb ed27f211ee12f022aaafd54b17ab753fb9bc39cd7a87a1ac0d1972db52e329d0 57672 libudns-dev_0.0.9-3_i386.deb 91833552b9f9eb174bdd8d0f1e846dd8b479fdb06c3317b06f80685a54b93cde 31342 udns-utils_0.0.9-3_i386.deb Files: 093e885a8f6cdf6f8a02f5917cfc7171 1014 libs optional udns_0.0.9-3.dsc 0e841dd84352e45d78571b8e3ab1d392 6135 libs optional udns_0.0.9-3.diff.gz 7157f40793c199f66ccd7446bcbfe5d9 33614 libs optional libudns0_0.0.9-3_i386.deb e2a4f60aab7f64b97aa7f0c4d8c2215e 57672 libdevel optional libudns-dev_0.0.9-3_i386.deb f81248f976023bd8edfac716216f024e 31342 net optional udns-utils_0.0.9-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpeQ7sACgkQQUuEI2/szeCr2gCfVFYB5DLc0rbOnmrabT0UdCrq 4iYAni51byTZ+9yn6fHmSfrqJ8F/oSht =X30B -END PGP SIGNATURE- Accepted: libudns-dev_0.0.9-3_i386.deb to pool/main/u/udns/libudns-dev_0.0.9-3_i386.deb libudns0_0.0.9-3_i386.deb to pool/main/u/udns/libudns0_0.0.9-3_i386.deb udns-utils_0.0.9-3_i386.deb to pool/main/u/udns/udns-utils_0.0.9-3_i386.deb udns_0.0.9-3.diff.gz to pool/main/u/udns/udns_0.0.9-3.diff.gz udns_0.0.9-3.dsc to pool/main/u/udns/udns_0.0.9-3.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: cgroup mount point
On Tue, Feb 03, 2009 at 11:44:00PM +1100, Ben Finney wrote: Daniel P. Berrange berra...@redhat.com writes: On Mon, Feb 02, 2009 at 07:41:53PM -0200, Thadeu Lima de Souza Cascardo wrote: So, we have some more options now: /cgroups, /containers, /dev/cpuset, /dev/cpuctl, /opt/cgroup, /opt/cpuset. Putting new mount points in / is not really acceptable, so that rules out the first two. /opt is just totally wrong, since that is intended for add on software packages. /dev/ feels a little odd, since it is not really device nodes I agree with all that Thadeu Lima says here. I would add that cgroups are nothing to do with device nodes, so definitely don't belong in ‘/dev/’ either. The message you quoted is from Daniel Berrange, not me. Could you also tell your rationale for not agreeing with /? Regards, Cascardo. Since they're a filesystem mapping “for browsing and manipulation from user space” of a kernel facility, I think ‘/sys/cgroups/’ is appropriate. -- \ “It's my belief we developed language because of our deep inner | `\ need to complain.” —Jane Wagner, via Lily Tomlin | _o__) | Ben Finney signature.asc Description: Digital signature
Re: cgroup mount point
On Tue, Feb 03, 2009 at 10:24:16AM +, Daniel P. Berrange wrote: On Mon, Feb 02, 2009 at 07:41:53PM -0200, Thadeu Lima de Souza Cascardo wrote: From what I've seen, most of them are in the same phases as Debian, or, perhaps, behind. Fedora seems to plan that for Fedora 11, and they have some support in libvirt. libvirt is not going to impose any policy for mount points, nor mount anything itself. When we use cgroups, libvirt just looks up the mount table to find out where the admin or distro has put the mount points for each cgroups controller. I've also not done anything in default Fedora install to automatically setup cgroups, since doing that hits the hard-to-answer question of whether to mount all controllers in one, or a separate mount per controller, or a hybrid. Sorry. I didn't mean to imply that libvirt or Fedora did anything in respect to the mountpoint themselves. But that they are supporting or planning to support cgroups. And I think that one time we will need to sort the problem of the mountpoint, either let the applications mount it (in this case, libvirt) or the system do it (Fedora install, Debian initscripts, et al). I have some experience with lxc tools from http://lxc.sf.net/ and these tools also look up the mountpoint at /proc/mounts. So it is up to the system or the user to mount it. So, we have some more options now: /cgroups, /containers, /dev/cpuset, /dev/cpuctl, /opt/cgroup, /opt/cpuset. Putting new mount points in / is not really acceptable, so that rules out the first two. /opt is just totally wrong, since that is intended for add on software packages. /dev/ feels a little odd, since it is not really device nodes, but perhaps that doesn't matter. So my pref would be something in /dev/cgroups or /sys/cgroups My suggestions were /proc/cgroup, /sys/cgroup, /cgroup or /dev/cgroup. I sent the problems with the former two, and the rationale for the latter two in a previous message. I agree that /opt/ is not the place for it (and that's the one I called 'funny'). I've head some people telling that /dev/ is for devices, but I can't see a problem (/dev/log is a socket and it is there, the FHS refers to special files). /proc/ and /sys/ are two good options if the kernel does not put anything else there. /proc/cgroups already exist, for example. Could you please give your rationale why / is not really acceptable? I also think 'cgroups' is a better name than 'containers', since 'containers' is refering to just one specific use case. Agreed on this one, although I still prefer the singular (it is also the name of the filesystem type). Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| Regards, Cascardo. signature.asc Description: Digital signature
cgroup mount point
Hello, Some software I intend to package work with the new cgroup feature in Linux. I would like to open a discussion about what would be the better place to mount it and how/when to mount it. Some of the options are: /sys/cgroup /proc/cgroup These two would not be very wise, since some kernel change may create those two, and, then, we would hide them, at least. /proc/cgroups, for example, is already there. /cgroup The FHS says why we should not create a new subdirectory in the root filesystem: 1) It demands space on a root partition which the system administrator may want kept small and simple for either performance or security reasons. This does not apply here, since we do not require any storage for /cgroup, but for the directory entry itself. 2) It evades whatever discipline the system administrator may have set up for distributing standard file hierarchies across mountable volumes. Since /cgroup is totally local, I can't see why this will evade anything. procfs and sysfs are in the root filesystem too. So why not put /cgroup there? /dev/cgroup Many people have been using this. FHS says this is the location for special and device files. What is not special about cgroup anyway? After deciding where to mount it, we may write some code for some of the init scripts to mount it. I think mountkernfs.sh may be a good place, since it also mounts /proc and /sys. Any opinions and comments appreciated. Regards, Cascardo. signature.asc Description: Digital signature
Re: cgroup mount point
On Mon, Feb 02, 2009 at 09:52:46PM +0100, Mike Hommey wrote: On Mon, Feb 02, 2009 at 09:26:11PM +0100, Julien Cristau wrote: On Mon, 2009-02-02 at 18:00 -0200, Thadeu Lima de Souza Cascardo wrote: Hello, Some software I intend to package work with the new cgroup feature in Linux. I would like to open a discussion about what would be the better place to mount it and how/when to mount it. What do other distros use? Even better: what do the kernel folks want to do? Mike From what I've seen, most of them are in the same phases as Debian, or, perhaps, behind. Fedora seems to plan that for Fedora 11, and they have some support in libvirt. Linux Documentation is not consistent and have some funny options. In Documentation/cgroups/*, we have: cgroups.txt: /dev/cgroup cpuacct.txt: /cgroups devices.txt: /cgroups memcg_test.txt: /opt/cgroup /opt/cpuset /cgroup memory.txt: /cgroups cpusets.txt: /dev/cpuset freezer-subsystem.txt: /containers There is also: Documentation/scheduler/sched-design-CFS.txt: /dev/cpuctl /cgroup Documentation/scheduler/sched-rt-group.txt: /cgroup Documentation/accounting/cgroupstats.txt: /cgroup So, we have some more options now: /cgroups, /containers, /dev/cpuset, /dev/cpuctl, /opt/cgroup, /opt/cpuset. I am copying the container and the kernel guys. Perhaps, we can find an agreement (if we want to find one at all) and change all that Documentation to get consistent. Regards, Cascardo. signature.asc Description: Digital signature
Re: cgroup mount point
On Mon, Feb 02, 2009 at 04:54:58PM -0600, Chris Friesen wrote: Thadeu Lima de Souza Cascardo wrote: Linux Documentation is not consistent and have some funny options. In Documentation/cgroups/*, we have: So, we have some more options now: /cgroups, /containers, /dev/cpuset, /dev/cpuctl, /opt/cgroup, /opt/cpuset. I am copying the container and the kernel guys. Perhaps, we can find an agreement (if we want to find one at all) and change all that Documentation to get consistent. I'd vote for cgroups or containers, mounted at / or /sys/. /opt feels more like where software should live, and /dev should be for devices rather than capabilities/management. cpuctl and cpuset are subsets of the full capabilities of cgroups, so they're suboptimal as far as naming. Chris Since the original post didn't go to lkml or lxc, here it is. Sorry d-d, but I want to keep it in the loop. And I agree with Chris in regards that cpuctl and cpuset are not only what is provided under a cgroup mountpoint, so they are not very good options. I prefer cgroup over container, and I prefer the singular. However, I'd rather not see this in /sys/ for the reason stated below. But since we may end up agreeing on this with the kernel people, we would be safe not to clash with a /sys/cgroup. But I see no problems with /dev/cgroup/ but would also be glad to see /cgroup/ as the choice. -- Hello, Some software I intend to package work with the new cgroup feature in Linux. I would like to open a discussion about what would be the better place to mount it and how/when to mount it. Some of the options are: /sys/cgroup /proc/cgroup These two would not be very wise, since some kernel change may create those two, and, then, we would hide them, at least. /proc/cgroups, for example, is already there. /cgroup The FHS says why we should not create a new subdirectory in the root filesystem: 1) It demands space on a root partition which the system administrator may want kept small and simple for either performance or security reasons. This does not apply here, since we do not require any storage for /cgroup, but for the directory entry itself. 2) It evades whatever discipline the system administrator may have set up for distributing standard file hierarchies across mountable volumes. Since /cgroup is totally local, I can't see why this will evade anything. procfs and sysfs are in the root filesystem too. So why not put /cgroup there? /dev/cgroup Many people have been using this. FHS says this is the location for special and device files. What is not special about cgroup anyway? After deciding where to mount it, we may write some code for some of the init scripts to mount it. I think mountkernfs.sh may be a good place, since it also mounts /proc and /sys. Any opinions and comments appreciated. Regards, Cascardo. -- signature.asc Description: Digital signature
Accepted gst-plugins-good0.10 0.10.8-4.1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 27 Jan 2009 20:12:10 -0200 Source: gst-plugins-good0.10 Binary: gstreamer0.10-plugins-good-doc gstreamer0.10-esd gstreamer0.10-plugins-good gstreamer0.10-plugins-good-dbg Architecture: source all i386 Version: 0.10.8-4.1 Distribution: unstable Urgency: high Maintainer: Maintainers of GStreamer packages pkg-gstreamer-maintain...@lists.alioth.debian.org Changed-By: Thadeu Lima de Souza Cascardo casca...@minaslivre.org Description: gstreamer0.10-esd - GStreamer plugin for ESD gstreamer0.10-plugins-good - GStreamer plugins from the good set gstreamer0.10-plugins-good-dbg - GStreamer plugins from the good set gstreamer0.10-plugins-good-doc - GStreamer documentation for plugins from the good set Closes: 512818 Changes: gst-plugins-good0.10 (0.10.8-4.1) unstable; urgency=high . * NMU * debian/patches/20_Fix_for_security_advisory_TKADV2009-0xx.patch: + Fix SA33650 and TKADV2009-03 (Closes: #512818) * Urgency set to high due to urgency bug Checksums-Sha1: 8cca6f20b4db4acd7e6de070e2d34a5ddf8fe5d2 2832 gst-plugins-good0.10_0.10.8-4.1.dsc fd6290a73e16ec307c6f01831953ae79a5e2379d 29385 gst-plugins-good0.10_0.10.8-4.1.diff.gz 432bfff80c8719d7611c5cc865e66727a6a1e434 171952 gstreamer0.10-plugins-good-doc_0.10.8-4.1_all.deb ecf494de90bab29aa848fd4bf7f2b728a573e576 46330 gstreamer0.10-esd_0.10.8-4.1_i386.deb 93a55ab4f21f3bc2730eaa7c6fdb698d13785cb1 967976 gstreamer0.10-plugins-good_0.10.8-4.1_i386.deb 00343e210d74545de661bd79778b203df520cc78 2517792 gstreamer0.10-plugins-good-dbg_0.10.8-4.1_i386.deb Checksums-Sha256: 2a745fdceb7bd350e38b15e624ce6e441db1043448d5679cfec21021a5040a5d 2832 gst-plugins-good0.10_0.10.8-4.1.dsc 987127321c4f41bd6da096516541f73993e151d81c7802813506dd694a8334b8 29385 gst-plugins-good0.10_0.10.8-4.1.diff.gz 4ffea1e58a76074aec945da52d8becffb5d154c33df1f59a0bbe6ecbc9de69ac 171952 gstreamer0.10-plugins-good-doc_0.10.8-4.1_all.deb 32739961378e138d9b9d8ed85d91385299c4e9d42dc1a58af6b28a8023589d5a 46330 gstreamer0.10-esd_0.10.8-4.1_i386.deb 728fe5d01635cfd6cca2a5f86fe01486de24bc0acb813056a9ece0da1b3015d4 967976 gstreamer0.10-plugins-good_0.10.8-4.1_i386.deb 78ab6b1a490143d9e269308a28d6777bbdaaefb613b30e2a5419036a52293e1f 2517792 gstreamer0.10-plugins-good-dbg_0.10.8-4.1_i386.deb Files: d08688268842898194f1fdd23a9e97bd 2832 libs optional gst-plugins-good0.10_0.10.8-4.1.dsc 96f8af61a4c4be6856926372f69c443f 29385 libs optional gst-plugins-good0.10_0.10.8-4.1.diff.gz 74a69e23a53b01a39fa8c65e0351f6ef 171952 doc optional gstreamer0.10-plugins-good-doc_0.10.8-4.1_all.deb 98a699f80ff78dc79cc8c440b85cb0c8 46330 libs optional gstreamer0.10-esd_0.10.8-4.1_i386.deb d22a834ab82867d6ba290f4e007a23f9 967976 libs optional gstreamer0.10-plugins-good_0.10.8-4.1_i386.deb 0852c36676b4ace3c2001043688cc9c8 2517792 libdevel extra gstreamer0.10-plugins-good-dbg_0.10.8-4.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJJf7AiAAoJENIA6zCg+12mhFwH/A2vxRoeZDC4X9X/d//kYhiL 2+arROssYTdnKNh3xCr9cPH/sRcuk7I70/cT2fmFANBInWchm4hMgm6kwtag/WTM vQZnHh6JDajbrYLTvGMkKD1DP7mTUhuxNR/IIZ5f3dDteOn5iTbkbVFUqxWzl7Vf 7heEaImHkHJ96F07xBNVqP9lJ8mXKqxVIuqjboRapDwchH6i1ourDl51fbDEz0ap NzOWa2iwZVsUe4NJsS0H1nGiQrraq9uDHjiFb95JNUeBOx7f7V6fwcqqX7cNjX4x hhNfxasTZSrl5GcGX5d9w8ZCwLPVCBi/6wUX2W0fs4+53UQRlkJehpkIRfwd2tw= =oXkw -END PGP SIGNATURE- Accepted: gst-plugins-good0.10_0.10.8-4.1.diff.gz to pool/main/g/gst-plugins-good0.10/gst-plugins-good0.10_0.10.8-4.1.diff.gz gst-plugins-good0.10_0.10.8-4.1.dsc to pool/main/g/gst-plugins-good0.10/gst-plugins-good0.10_0.10.8-4.1.dsc gstreamer0.10-esd_0.10.8-4.1_i386.deb to pool/main/g/gst-plugins-good0.10/gstreamer0.10-esd_0.10.8-4.1_i386.deb gstreamer0.10-plugins-good-dbg_0.10.8-4.1_i386.deb to pool/main/g/gst-plugins-good0.10/gstreamer0.10-plugins-good-dbg_0.10.8-4.1_i386.deb gstreamer0.10-plugins-good-doc_0.10.8-4.1_all.deb to pool/main/g/gst-plugins-good0.10/gstreamer0.10-plugins-good-doc_0.10.8-4.1_all.deb gstreamer0.10-plugins-good_0.10.8-4.1_i386.deb to pool/main/g/gst-plugins-good0.10/gstreamer0.10-plugins-good_0.10.8-4.1_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511341: ITP: libstrophe -- Library for writing XMPP clients
Package: wnpp Severity: wishlist Owner: Thadeu Lima de Souza Cascardo casca...@minaslivre.org * Package name: libstrophe Version : 0.7.x Upstream Author : StanzIQ * URL : http://code.stanziq.com/strophe/wiki * License : GPLv2+ Programming Lang: C Description : Library for writing XMPP clients Strophe provides the following features: * XMPP compliant * TLS support via SChannel, GNUTLS or OpenSSL * SASL authentication using ANONYMOUS, DIGEST-MD5 or PLAIN methods as well as legacy jabber authentication * Customizable logging and memory management -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') 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: [DRAFT] resolving DFSG violations
On Sun, Nov 09, 2008 at 09:25:18AM +0100, Michelle Konzack wrote: So the only option for Ben ist, to send the corrected source back to the manufacturer and ask him to test and relicense it... The problem is, that certifying cost up to 40.000 Euro and re-certifying arround 10-15.000 Euro. So after ONE bugfix, no manufacturer would recertify the software. IF the hardware is not sold at least 50-100.000 times where arround 30-80¢ are calculated for software updates over the first 2 years after first hardware sell. IANAL, IANADDY. And what if Ben himself or another party, let's say, Cascardo, wants to pay that to recertify the original hardware + fixed software or a new designed hardware or even an existing but different hardware with the fixed software? As pointed out in another thread, would it really be illegal to distribute said software if Debian does not distribute the hardware it would run on? No one said it is illegal (and I am not pointing it out that it is legal). But I wouldn't deny that freedom for software that runs on my cell phone, my wireless network card, my video card has the same benefits that software that runs on my computer laptop, computer desktop or computer server. What makes them so different, anyway? If that's because it could hurt people, that's why we have laws and certification process. Nothing is currently preventing somebody to use Debian on an airplane, a medical facility or whatever. That's why DFSG#6 exists. So, if the copyright license of said firmware is DFSG-compliant and it is legal to distribute it in wherever jurisdiction ftpmaster is working, I can't see a problem in distributing it, even if it was worthless for most people (which I don't think it would be). 2 years is the normal European Waranty for NEW bought hardware. This is WHY most cell-phones get not a singel software update (no mather which manufacturer as Nokia, Ericsson, Sony, Siemans/BenQ, LG, ...) Thanks, Greetings and nice Day/Evening Michelle Konzack Regards, Cascardo. signature.asc Description: Digital signature
Re: Sun RPC libraries and other stories
On Wed, Nov 05, 2008 at 03:32:35PM -0600, Ean Schuessler wrote: I'm here at ApacheCon with Simon Phipps and he said that Sun would be delighted to help Debian resolve the RPC licensing problems. He wanted to note that the Free Software Definition did not exist at the time when Sun released to the community and they couldn't have predicted that it would violate the DFSG. Considering when it was released, its very open. He also noted that Sun hasn't pursued any legal action in all this time and that is a good indicator of their position on the whole thing. All we need to do is get Simon a diff of what changes we need made and he will help us make the arrangements. In short, Sun is all for Debian keeping the RPC code in libc6 or the kernel and will do what is necessary to make it happen. -- Ean Schuessler, CTO Brainfood.com [EMAIL PROTECTED] - http://www.brainfood.com - 214-720-0700 x 315 Please, remember that portmap has some of that code too. Best Regards, Cascardo. signature.asc Description: Digital signature
Re: [DRAFT] resolving DFSG violations
On Wed, Oct 29, 2008 at 10:33:27PM +0100, Michelle Konzack wrote: Am 2008-10-28 02:45:31, schrieb Thadeu Lima de Souza Cascardo: If it's not clear by now, people are not arguing that hardware should not be used if it is not free hardware (either it is feasible or not to distribute or exist source code). The matter is whether source for code that will not execute in the main CPU is needed for those codes in the main section. So, your point that it is not x86 code is moot in the case firmware is considered to be the same as other software in Debian. If source code isn't available or possible for the chip carries the same requirements for DFSG as the case would be for the x86 code, in the case firmware should still follow DFSG. Anw what do you do with sourcode, for which there is not even a compiler availlable under Linux/BSD? And you HAV to buy a 8000 US$ development suit from the chip manufacturer to build the firmware? If the source code is not human-readable, but it is free/libre, I would study it in the case I consider the chance there is a bug. Perhaps, if it was of my interest, I would even study the possibility of reverse-engineering it, so it could be more human-readable and provide tools to build it. I have such software and EVEN me can not read the firmware. I have ONLY a project in my IDE and it produce the firmware. And now you! I consider that a problem with the tool you use. It has a major defect (by design): it is not free/libre. So you cannot modify your IDE to give you any more human-readable format or something else. Even machine readable form would still be considered source if its interpretation by the machine could be presented to someone to make modifications to it. If it is not modifiable for some reason and every design should be done from scratch, perhaps there is a problem with the tools and/or processes used. Do you have already tried to modify a binary blob or simply opened a (no mather which) binary from /bin/ in a HEX editor and tried to modify it? In my /bin/ directory? If I had to really modify it, why would I use a hex-editor if I have source code in C? However, I have programmed a microcontroller using a text editor and hexadecimal numbers, even had to recode some constants present in code because I had to add a single instruction in the middle of it. Until I stopped being too lazy to code a simple assembler. Even the chip manufacturers don't know what they are. It's totally machine generated chip garbage as far as they are concerned. Once you Which machines do generate this garbage? Do they do it all by themselves? Are there machines designing new hardware now without human intervention? Or are those chips magically enhanced so they could make some sense of any random bitstream and there is no real mistery in generating this garbage? The software/IDE use projects which are not in human readable form... ...and if you have finisched, you klick the button Output firmware and then you have the firmware blob. Again, this is a issue with your IDE. It could certainly be modified to output some more human-readable format that represents its internal representation of the project... if only it were free/libre. If the manufacturers are unaware of it, I doubt the designer is unaware of it. ??? It seems you have never designed Hardware or realy coded software for it Does writing a microprocessor in Verilog count as designing hardware? Thanks, Greetings and nice Day/Evening Michelle Konzack Anyway, this is about the DFSG and the requirement of distributing source code. I would really like that the requirement for distributing the needed tools to build and modify this source code was in DFSG too. Unfortunately, they are not. Fortunately, many packages that Build-Depends on packages on non-free are in contrib. I hope that will be the case too for any firmware. So, it doesn't matter if the preferred form of modification (by the way, do you open on your IDE your output firmware or your project?) is human-readable or not. It is, in anyway, required by DFSG. If it is the same as the binary distributed, the other DSFG requirementes still apply. Regards, Cascardo. signature.asc Description: Digital signature
Re: [DRAFT] resolving DFSG violations
On Wed, Oct 29, 2008 at 10:40:03PM +0100, Michelle Konzack wrote: Am 2008-10-28 09:33:07, schrieb Tristan Seligmann: Again, assuming I'm not misspeaking, that form of the work is already what we have. ACK ;-) Thanks, Greetings and nice Day/Evening Michelle Konzack In which cases? Which of the firmwares? How can you be sure? Regards, Cascardo. signature.asc Description: Digital signature
Re: [DRAFT] resolving DFSG violations
On Wed, Oct 29, 2008 at 10:58:12PM +0100, Michelle Konzack wrote: Am 2008-10-27 17:01:50, schrieb Felipe Sateler: Jeff Carr wrote: But the opencore case is the easy case, hybrid chips don't even have source. The firmware blob is often generated when you fabricate the chip changes with the physical board layout. You guys just don't understand the issues here. Please explain what the issues are, then. The firmware blob has to be generated *somehow*. There is a tool that generates the blob. Which data does the tool need to generate it? The IDE/Software which produce the firmware blobs mostly generate it directly and the projects the developers are using are binary stuff. And what do you type in this software to produce this project? This project would be source code, anyway. Even if we did not have the tools to produce the same firmware from this. Parts of it maybe human readable but not suffisant to compile it or do anything usefull with it. And as I have already written, SDCC compiled code is 3 times bigger as the firmeware blob generated by a 8000 US$ IDE. And do you write C code in your IDE? What else does this IDE provide you to help you optimize your C code? If it's not C code, what is it? And it would be very hard to compare C-code with hand-written assembly. And using a Microcontroller/ASIC with bigger memory is no solution since sometimes it would be very costly... In my case arround 3 million Euro more for the final production (18mio). A good solution would be to improve the free/libre software available in Debian, since you seem to claim that SDCC is an option as a development tool to this said micro-controller. Is it a 8051? Thanks, Greetings and nice Day/Evening Michelle Konzack signature.asc Description: Digital signature
Re: Free OS versus free hw
On Tue, Oct 28, 2008 at 10:51:55PM +1100, Ben Finney wrote: [...] *without* access to any specific extra data, vendor-specific programs, or other non-free software. I agree here, although, I wouldn't say the DFSG requires that source code should be modifiable with software distributed in Debian. But it would certainly be an improvement, mainly in the presence of bitstreams which are the corresponding source code themselves and are only modified using vendor-specific tools, which may not be available as free/libre software. [...] Ben Finney Cascardo. signature.asc Description: Digital signature
Re: [DRAFT] resolving DFSG violations
it as possible, so hoping for a source release seems fairly futile. Write a replacement! Go for other hardware! Copy the firmware yourself if you have the author permission! But do not distribute non-free/libre software in Debian main! Now, imagine Debian having this hypothetical yearly conference, called, oh, let's say DebConf. During that conference we organise a special day for our users, let's call it Debian Day. Lots of potential new Debian users show up with their laptops and wants to install Debian. As the kind souls we are, we hand out credit-card CD's with netinst images that they can use with the WiFi available at the conference. Oh, but wait. They cannot access the WiFi, because their wireless cards are not supported. Or rather, the drivers are available, but they all report the same error message Firmware not found. Happy, happy, joy, joy. I'm sure those potential Debian users will feel really happy about Debian's consistent policy that dictates that software running on non-cpu == software running on cpu. They might not feel equally please The hardware manufacturer is at fault! Not Debian! with the fact that Debian isn't consistent in its dedication to prioritising the users though... I will try to be short in telling something about the history of education in my place. The government passed some resolution that students must be approved always. Well, some teachers interpreted that as that they should just give some grade to the student so they could achieve that. What they should have done was everything so the student would learn and not be able to fail. If Debian interprets that its prioritising of users' software and firmware availability is in favor of their freedom, why don't forget the DFSG and include whichever distributable work in main? Debian could tell them about the known issues with known hardware as well as tell them about known issues with known network services and ask them for help. [snip] Regards: David -- /) David Weinehall [EMAIL PROTECTED] /) Rime on my window (\ // ~ // Diamond-white roses of fire // \) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/ Regards, Cascardo. signature.asc Description: Digital signature
Re: [DRAFT] resolving DFSG violations
On Mon, Oct 27, 2008 at 08:30:38PM -0700, Jeff Carr wrote: I guess it's really hard to explain because there is a massive gap; I can't teach you to be an electrical engineer or logician here :) I You are assuming there is gap when there may be not. think if you had the time to go through and synthesize firmware blobs for some chips then you would see why this doesn't make sense. It would also expose you to the tools that the hardware and logic engineers use to do this process. It would also expose you to the Would those be tools like a Verilog or VHDL synthetizer distributed by a FPGA manufacturer? Considering the hardware is FPGA, of course. In the case it is not, I assume there would still be procedures like logic design, routing, etc. pre-requisite knowledge of the board design (layout, etc) that you have to have. Then I think it would make sense to you why this conversation doesn't make sense right now. It's that these binary only blobs only make sense to the chip. It's like they are a map of So, why do they only make sense to the chip? Is it because there is no current implementation of a software simulator? And why would a software simulator not be feasible? The binary blobs would make sense to the simulator. how the transistors are to function -- an oversimplification -- but generally that's the nature of it. * For example, lets say you have a pci device. If you don't load the firmware blob, the pins will just remain in an uninitialized state. That is; the chip default. Programming in the firmware blob will tell the chip how to work as a pci bus. Now you are good to go. It's now possible to write a pci device there are registers, etc. As a hardware engineer I can give you all the registers and an API and even some sample GPL code so you can write a device driver. Now, some people are smucks like nvidia and they don't give out diddly. Still, the firmware blob that you load into the chip isn't x86 code for the host -- it's raw junk for the chip. It's a totally different issue If it's not clear by now, people are not arguing that hardware should not be used if it is not free hardware (either it is feasible or not to distribute or exist source code). The matter is whether source for code that will not execute in the main CPU is needed for those codes in the main section. So, your point that it is not x86 code is moot in the case firmware is considered to be the same as other software in Debian. If source code isn't available or possible for the chip carries the same requirements for DFSG as the case would be for the x86 code, in the case firmware should still follow DFSG. than distributing a binary only nvidia driver. That's not what I'm talking about here. I'm only trying to explain there are binary only firmware blobs for most chips, you have them for most of the chips on your motherboard and in many cases, there is no human readable form. Even machine readable form would still be considered source if its interpretation by the machine could be presented to someone to make modifications to it. If it is not modifiable for some reason and every design should be done from scratch, perhaps there is a problem with the tools and/or processes used. Even the chip manufacturers don't know what they are. It's totally machine generated chip garbage as far as they are concerned. Once you Which machines do generate this garbage? Do they do it all by themselves? Are there machines designing new hardware now without human intervention? Or are those chips magically enhanced so they could make some sense of any random bitstream and there is no real mistery in generating this garbage? If the manufacturers are unaware of it, I doubt the designer is unaware of it. have the chip initialized then you can hook it up to an oscilloscope to debug it (or maybe you're lucky and you can already talk to it from your device driver). * http://en.wikipedia.org/wiki/Floorplan_(microelectronics) * http://en.wikipedia.org/wiki/Logic_synthesis * http://en.wikipedia.org/wiki/Place_and_route -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Regards, Cascardo. signature.asc Description: Digital signature
Accepted gsasl 0.2.26-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 20 Oct 2008 11:12:27 -0200 Source: gsasl Binary: libgsasl7-dev libgsasl7 gsasl Architecture: source i386 Version: 0.2.26-2 Distribution: unstable Urgency: high Maintainer: Debian XMPP Maintainers [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: gsasl - GNU SASL command line utility libgsasl7 - GNU SASL library libgsasl7-dev - Development files for the GNU SASL library Closes: 502469 Changes: gsasl (0.2.26-2) unstable; urgency=high . * Set Maintainer as the Debian XMPP Team and add Jorge Salamero Sanz as an Uploader * Development package must depend on libkrb5-dev. Thanks Philipp Kern. (Closes: #502469) * Urgency high because of RC bug. Checksums-Sha1: deb79a50b0dd04eb9e979c701920deb87b3023f7 1688 gsasl_0.2.26-2.dsc 23c4f38d5d44ae3d58cc9c693988851be992a363 181116 gsasl_0.2.26-2.diff.gz d5294ba2a7883da8592a8db3d94f95df165279e7 217088 libgsasl7-dev_0.2.26-2_i386.deb 79e2c6bcb6b37cdd418fe7e1c25b0d27b18f37c4 146452 libgsasl7_0.2.26-2_i386.deb da4e03552c809a955cfc5125675f92a62fa56c25 170874 gsasl_0.2.26-2_i386.deb Checksums-Sha256: 9aac892d51181f4ea885e5d1aaa668edf7960564ff55ea22aee36ad3daca2a2e 1688 gsasl_0.2.26-2.dsc 732e268f873e8f6a869eefccc800c4c89d16c81b29962ed9f3a5552b82e6d3c2 181116 gsasl_0.2.26-2.diff.gz 667ff0b536174492bef0176dc4c90be451ef20372973aa5c43c0f4a9d2f2dbc6 217088 libgsasl7-dev_0.2.26-2_i386.deb 1854dd85bf4531cd0072860033767d69fd7b1bc96cbf279896730ebae5d55326 146452 libgsasl7_0.2.26-2_i386.deb 94824a2140675407ea3641712cd16239e92ca661ed2efde9db5c61308438b4d0 170874 gsasl_0.2.26-2_i386.deb Files: a46ef42ba08cb19ca5b50431b99989e8 1688 devel optional gsasl_0.2.26-2.dsc 8169124f0444cf871340e4e34947004b 181116 devel optional gsasl_0.2.26-2.diff.gz 2def1e142b0a7c4cb98036a01f7278f8 217088 libdevel optional libgsasl7-dev_0.2.26-2_i386.deb 4b3d9933ba8fdd3d15f4380ebe2101aa 146452 libs optional libgsasl7_0.2.26-2_i386.deb 1d848dd918151664d389e8d022d03cd7 170874 devel optional gsasl_0.2.26-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJI/LbLAAoJENIA6zCg+12mZVkH/2URdTTfreO6dzMvki9bGj2P lGg0HwWjh0WodKJubN1OjeLqlsimM66QQlHG6PEMLDFGRfyv1EwN9OodXTWz7GdJ epHfeygo0zXJpJY7nt+RKoLIJso8kxAGy6iCvEkL5uhv5NPlmzIwTZEymOT8w94p NPdUtw+SIeG68zgM+WrP46M/3zc0Zc4wC45XlnoZ8KQjDU9wijf2LKr9pEIiRcRE iTlCqIdLhgm4QbfWrsQNd6sDlTlajsaxN4alNWyRbbEXDZunARDgM/4yLTtC/nK4 Qfh/AoC18Y5Uh33aqun0RuxevXliNRFcMoavGr8ZwoHHOc+tsbLp9Q7kAun7/DQ= =dE4h -END PGP SIGNATURE- Accepted: gsasl_0.2.26-2.diff.gz to pool/main/g/gsasl/gsasl_0.2.26-2.diff.gz gsasl_0.2.26-2.dsc to pool/main/g/gsasl/gsasl_0.2.26-2.dsc gsasl_0.2.26-2_i386.deb to pool/main/g/gsasl/gsasl_0.2.26-2_i386.deb libgsasl7-dev_0.2.26-2_i386.deb to pool/main/g/gsasl/libgsasl7-dev_0.2.26-2_i386.deb libgsasl7_0.2.26-2_i386.deb to pool/main/g/gsasl/libgsasl7_0.2.26-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500397: debian-goodies: opens a package homepage
Package: debian-goodies
Version: 0.47
Severity: wishlist
Tags: patch
This little wrapper opens a package homepage in a sensible browser.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.27-rc6-1-g46bec93 (PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debian-goodies depends on:
ii curl 7.18.2-7 Get a file from an HTTP, HTTPS or
ii dctrl-tools [grep-dctrl] 2.13.0 Command-line tools to process Debi
ii dialog1.1-20080819-1 Displays user-friendly dialog boxe
ii less 418-1 Pager program similar to more
ii lsof 4.78.dfsg.1-4 List open files
ii python2.5.2-1An interactive high-level object-o
ii whiptail 0.52.2-11.3Displays user-friendly dialog boxe
debian-goodies recommends no packages.
-- no debconf information
diff --git a/debian/control b/debian/control
index a45b2a9..619c7dd 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Standards-Version: 3.5.2
Package: debian-goodies
Architecture: all
-Depends: dctrl-tools | grep-dctrl, curl, python (= 2.4), lsof, whiptail | dialog, less
+Depends: dctrl-tools | grep-dctrl, debianutils, curl, python (= 2.4), lsof, whiptail | dialog, less
Suggests: popularity-contest, xdg-utils, zenity
Conflicts: debget
Replaces: debget
diff --git a/dhomepage b/dhomepage
new file mode 100755
index 000..9b6e587
--- /dev/null
+++ b/dhomepage
@@ -0,0 +1,68 @@
+#!/bin/sh
+#
+# Copyright (C) 2008 Thadeu Lima de Souza Cascardo [EMAIL PROTECTED]
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; either version 2 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+
+VERSION=0.1
+
+function version()
+{
+ echo dhomepage version $VERSION
+ echo dhomepage is licensed under the GNU General Public License
+ echo version 2 or later
+}
+
+function usage()
+{
+ echo dhomepage PACKAGE
+ echo
+ echo --version Show version information
+ echo --help Show this help message
+ echo
+}
+
+PACKAGE=$1
+
+if [ -z $PACKAGE ]; then
+ usage
+ exit 0
+fi
+
+case $1 in
+ --help)
+ usage
+ exit 0
+ ;;
+ --version)
+ version
+ exit 0
+ ;;
+esac
+
+HOMEPAGE=`grep-aptavail -PX $PACKAGE -s Homepage | sed 's,^Homepage: ,,'`
+
+if [ -z $HOMEPAGE ]; then
+ HOMEPAGE=`grep-aptavail -PX $PACKAGE -s Description | \
+sed -n '/^ Homepage: /{s,^ Homepage: ,,;p}'`
+fi
+
+if [ -z $HOMEPAGE ]; then
+ echo $PACKAGE has no homepage
+ exit 1
+fi
+
+sensible-browser $HOMEPAGE
diff --git a/dhomepage.1 b/dhomepage.1
new file mode 100644
index 000..5c3baf8
--- /dev/null
+++ b/dhomepage.1
@@ -0,0 +1,48 @@
+.\
+.\ Copyright (C) 2008 Thadeu Lima de Souza Cascardo [EMAIL PROTECTED]
+.\
+.\ This program is free software; you can redistribute it and/or modify
+.\ it under the terms of the GNU General Public License as published by
+.\ the Free Software Foundation; either version 2 of the License, or
+.\ (at your option) any later version.
+.\
+.\ This program is distributed in the hope that it will be useful,
+.\ but WITHOUT ANY WARRANTY; without even the implied warranty of
+.\ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+.\ GNU General Public License for more details.
+.\
+.\ You should have received a copy of the GNU General Public License along
+.\ with this program; if not, write to the Free Software Foundation, Inc.,
+.\ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+.\
+
+.TH DHOMEPAGE 1 2008-09-27
+
+.SH NAME
+dhomepage - show the homepage of a package in a browser
+
+.SH SYNOPSIS
+dhomepage PACKAGE
+
+.SH DESCRIPTION
+Shows the homepage of a Debian package using a sensible browser.
+
+.SH OPTIONS
+
+.TP
+\fB\-\-help\fR
+Print help message
+
+.TP
+\fB\-\-help\fR
+Print version message
+
+.SH EXIT STATUS
+Returns 0 if homepage was found, and 1 otherwise.
+
+.SH BUGS
+Report bugs to this man page and program to [EMAIL PROTECTED]
+
+.SH SEE ALSO
+.BR dgrep (1)
+.BR sensible-browser (1)
Re: Source field in binary Packages list
On Sun, Aug 31, 2008 at 02:20:27PM -0700, Daniel Burrows wrote:
Why do you need #497205? Is it too slow to just use SourcePkg() in
the package records object?
Daniel
Sorry! I was lazy/stupid/whatever enough to not read more about apt and
learn how to do it without adding a field to the cache. So, I am
attaching the patch to the patch for aptitude, which does not need this
other patch to APT. I will close the apt bug after that.
I still like the patch to be reviewed, if you can, please.
Thanks,
Thadeu Cascardo.
diff -u aptitude-0.4.11.8/src/pkg_grouppolicy.cc aptitude-0.4.11.8/src/pkg_grouppolicy.cc
--- aptitude-0.4.11.8/src/pkg_grouppolicy.cc
+++ aptitude-0.4.11.8/src/pkg_grouppolicy.cc
@@ -1676,11 +1676,11 @@
void add_package(const pkgCache::PkgIterator pkg, pkg_subtree *root)
{
-string source;
-if (!pkg.Source())
+if (pkg.VersionList().end() || pkg.VersionList().FileList().end())
+ return;
+string source=apt_package_records-Lookup(pkg.VersionList().FileList()).SourcePkg();
+if (source.length()==0)
source=pkg.Name();
-else
- source=pkg.Source();
childmap::iterator found=children.find(source);
signature.asc
Description: Digital signature
Source field in binary Packages list
Hello, I am working on a grouping feature for aptitude, to group binary packages by their source package. However, some packages in the Packages file do not have a Source field. My guess was to use the package name as the source package name. Is this right? Thanks, Thadeu Cascardo. signature.asc Description: Digital signature
Re: Source field in binary Packages list
On Sat, Aug 30, 2008 at 03:21:36PM -0500, Raphael Geissert wrote: Thadeu Lima de Souza Cascardo wrote: Hello, I am working on a grouping feature for aptitude, to group binary packages by their source package. However, some packages in the Packages file do not have a Source field. My guess was to use the package name as the source package name. Is this right? Yup Thanks, Thadeu Cascardo. Thanks again! For those interested, I've submitted the patches to the BTS as bugs 497205 and 497206. Note that 497205 should break libapt-pkg ABI, so take care. :-) Comments welcome. Regards, Thadeu Cascardo. signature.asc Description: Digital signature
Accepted jsjac 1.3-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 02 Jul 2008 00:10:20 -0300 Source: jsjac Binary: libjs-jac Architecture: source all Version: 1.3-1 Distribution: unstable Urgency: low Maintainer: Debian XMPP Maintainers [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libjs-jac - JavaScript Jabber Client Library Closes: 458484 Changes: jsjac (1.3-1) unstable; urgency=low . [ Marcelo Jorge Vieira (metal) ] * Initial release (Closes: #458484) . [ Thadeu Lima de Souza Cascardo ] * Updated copyright information. * Added fields Vcs-Svn and Vcs-Browser, pointing to upstream VCS. * Updated Standards-Version, no changes needed. * Package name now is libjs-jac and includes only the packed version of the source, including a symlink from its unpacked name * Changed Maintainers to Debian XMPP team and Uploaders to me and Marcelo Jorge Vieira * Changed VCS information from upstream VCS to maintainers VCS. Checksums-Sha1: ecf659516d9a36cf6df314bdbfcd4f8d0b7969f6 1522 jsjac_1.3-1.dsc c2fb862379a21e7fb7320bcef685f414af251dbb 273109 jsjac_1.3.orig.tar.gz 3baa85e31a9c8c4698fcb9edd225b995defd407e 2128 jsjac_1.3-1.diff.gz 398a4b4a908d5127cfb135bbc699a617096a4c74 123150 libjs-jac_1.3-1_all.deb Checksums-Sha256: e263afcd144dbbb1c5bffb651d14c7df05b3e044b766fbc733f3598ec77130a1 1522 jsjac_1.3-1.dsc 0b5c8ba1ac59bb6bddd97934e17de790bdbb8b4607ed717a99791909a91773fb 273109 jsjac_1.3.orig.tar.gz 7e8f01632f54e88579cbe89ee4bc97c84e83396b50258c577b1e66b979af6b46 2128 jsjac_1.3-1.diff.gz 230d77bb10505cf20cb0d879151c2a9b2af6bce31b46dc2d0c8e6b3070637fe4 123150 libjs-jac_1.3-1_all.deb Files: 78a3db323901b7ababce58a9ca32e02a 1522 web optional jsjac_1.3-1.dsc 2863edbe089e50a4ae8a03d19929839e 273109 web optional jsjac_1.3.orig.tar.gz 4916d2d62d5542ab1bd952f26174cacf 2128 web optional jsjac_1.3-1.diff.gz 3a8cf6149f7d90ee1ec28a5d074b5014 123150 web optional libjs-jac_1.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJIbEDfAAoJENIA6zCg+12mCHAIALaNqpk4UtZwCJqzCblxNYhl NA3njN97zw5f5HLi5KRQl/uhO7phCkruiSdwtmazHNzda3HDykB49pKVongWcpRd YF1fNdER629BKXpincA8/u/ZsCdq9Z2fyjPRktCOVEK+CLTkw1UZwsafmS3+w2fW ArHWuGiGTK6IzLlNKfqicq2hQuRv716wh2D+lBdzPaXvZXO2Y0mfzvdYrRvcumzP JDTiMOcgPSOedXrF3oo2IpRjYOfDdP41T59w1jPmuWotOpmGXbATwXfOzQJoj+tm +1stx3q+f1BRHQRllsfBEnTHNBIn8MQpxL4HtDIpEQLpbCV+pyw/w2jhAanQp+I= =xX5f -END PGP SIGNATURE- Accepted: jsjac_1.3-1.diff.gz to pool/main/j/jsjac/jsjac_1.3-1.diff.gz jsjac_1.3-1.dsc to pool/main/j/jsjac/jsjac_1.3-1.dsc jsjac_1.3.orig.tar.gz to pool/main/j/jsjac/jsjac_1.3.orig.tar.gz libjs-jac_1.3-1_all.deb to pool/main/j/jsjac/libjs-jac_1.3-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gsasl 0.2.26-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 24 May 2008 21:41:16 -0300 Source: gsasl Binary: libgsasl7-dev libgsasl7 gsasl Architecture: source i386 Version: 0.2.26-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: gsasl - GNU SASL command line utility libgsasl7 - GNU SASL library libgsasl7-dev - Development files for the GNU SASL library Closes: 482470 Changes: gsasl (0.2.26-1) unstable; urgency=low . * New upstream release (Closes: #482470) Checksums-Sha1: 781e4dfdba6455fbc7d252a8e7eb585f32e8e159 1568 gsasl_0.2.26-1.dsc bd6d201bc2d35291e1b2a24a32932d709ec4c0f5 3371738 gsasl_0.2.26.orig.tar.gz c2a121a0210371b5d01c0b420b6c13ca1313ec4e 25746 gsasl_0.2.26-1.diff.gz c9eb07f946991443f9cd8c7b36a9dbf774030930 216800 libgsasl7-dev_0.2.26-1_i386.deb b8fce429ae1144a4c2e8e765de7c346aac618fbf 146060 libgsasl7_0.2.26-1_i386.deb de8f01a235bdcb156baca7dc3d9c90a382417256 170646 gsasl_0.2.26-1_i386.deb Checksums-Sha256: 50f26489258f9949d3c087f993c9b90470f0d029d52dc16f5dfedb0f6bd9c232 1568 gsasl_0.2.26-1.dsc 5362c550a5ec8e1aeb2a5fe866998e060129aca6216eb0e1523178f30ead383e 3371738 gsasl_0.2.26.orig.tar.gz 5b05a816a8ba932f4c118836c41d8e87be0b8ff9c52224796d4887f8c36bcedc 25746 gsasl_0.2.26-1.diff.gz e67c44712fd3a2572b71158bc6cc4192610b7703d300e170cc355ebc3bcaeb9a 216800 libgsasl7-dev_0.2.26-1_i386.deb ff2ffefa4244482fb239a9870b6c9bb94a5dbc83b16935b76d3dfe851412651c 146060 libgsasl7_0.2.26-1_i386.deb 9036b68a738ad5e7a3c71b31aa4e0d323a1311ba9d29a1c9b2a154a3162e600f 170646 gsasl_0.2.26-1_i386.deb Files: 878749785df6863c83f1f955eebd632c 1568 devel optional gsasl_0.2.26-1.dsc 1debd9f67068ffbf73fa6ca4e4e2ffd4 3371738 devel optional gsasl_0.2.26.orig.tar.gz af7512de151fdee5a085d7c6b2a0d623 25746 devel optional gsasl_0.2.26-1.diff.gz 9bd1e56f1dc6cf5e0ed5e3ff162b35c9 216800 libdevel optional libgsasl7-dev_0.2.26-1_i386.deb 687cbdb825585c85ac1a4f3ae6b09139 146060 libs optional libgsasl7_0.2.26-1_i386.deb e763f681bd9d5993feb8d62938eb773c 170646 devel optional gsasl_0.2.26-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJIVtBTAAoJENIA6zCg+12mCL8H/Ro92hmZYe86UGsJPyHvb9n2 BIDRTn50jSwn75LAX7Xl0aL2Os0ya9TL5CBiFA2rW2G+orMoqWpmUJTWC+7UXTpC oEIDXx3Qxd9fTwDliIsmI+7rvCTG7Gz7b7mi1JXuGaDVOsDJAklOBvddwADbxl/v imbSRNj8PQDPmAS07ZKPISZztLJNJHzpufN25v21ajg4YqRXs42hEjMFAj7bchI3 dKDitR/xJEr9qPmTi0oiThsGYfAfIcDblxLSY4n50CvVZi5jcb2Ij2ilzKMpVN/E X61EQMJK2EmLk7/xgIYNN1RgcRoHLtM8qOEjVIVT0Spui5LJotJxjEB8TirU8fs= =1FPe -END PGP SIGNATURE- Accepted: gsasl_0.2.26-1.diff.gz to pool/main/g/gsasl/gsasl_0.2.26-1.diff.gz gsasl_0.2.26-1.dsc to pool/main/g/gsasl/gsasl_0.2.26-1.dsc gsasl_0.2.26-1_i386.deb to pool/main/g/gsasl/gsasl_0.2.26-1_i386.deb gsasl_0.2.26.orig.tar.gz to pool/main/g/gsasl/gsasl_0.2.26.orig.tar.gz libgsasl7-dev_0.2.26-1_i386.deb to pool/main/g/gsasl/libgsasl7-dev_0.2.26-1_i386.deb libgsasl7_0.2.26-1_i386.deb to pool/main/g/gsasl/libgsasl7_0.2.26-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libiksemel 1.2-4 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 22 Jan 2008 15:15:22 -0200
Source: libiksemel
Binary: libiksemel-dev libiksemel3 libiksemel-utils
Architecture: source i386
Version: 1.2-4
Distribution: unstable
Urgency: low
Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED]
Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED]
Description:
libiksemel-dev - C library for the Jabber IM platform
libiksemel-utils - utilities from the iksemel library
libiksemel3 - C library for the Jabber IM platform
Changes:
libiksemel (1.2-4) unstable; urgency=low
.
* Added manpages for binaries in libiksemel-utils.
* Mention copyright and license of new manpages, as well as info
documentation, which are GPL.
* Uses ${binary:Version} instead of ${Source-Version}.
* Updated Standards-Version to 3.7.3.
Checksums-Sha1:
7f13b1b0e91438edd435152317cc5274f207635a 1337 libiksemel_1.2-4.dsc
f904e7940da75da73e6cea70dec9d1f15d589eee 16014 libiksemel_1.2-4.diff.gz
77fb32a83fc5438254f0d32de09b58d01a462d46 56704 libiksemel-dev_1.2-4_i386.deb
aee7a2662dd7cbc02725d10972aa95275eeb1420 35212 libiksemel3_1.2-4_i386.deb
b7387b16638f590a21c1da9e5b67b85c389628dd 25790 libiksemel-utils_1.2-4_i386.deb
Checksums-Sha256:
72b60204743f64ffaea419e8c7da911b77f468a639bb68c0f35df098567080c7 1337
libiksemel_1.2-4.dsc
0c4614c9fdd8893e7b16697c5d2d5d2f8feb92f6ca0ab86bcbf7a535df82526f 16014
libiksemel_1.2-4.diff.gz
b651bbb8e3d7e744a097dd95221f411eb0d292620f86d876c6ec1e05d9fa 56704
libiksemel-dev_1.2-4_i386.deb
05351b0a7aeb293543f246c4f1ac49e574950efff990a163498bf48b9847e15d 35212
libiksemel3_1.2-4_i386.deb
fb8ed88fe3e0fe27a2725b463f71fba46b7a8cb3abbb4f77a683ff1ba2173e76 25790
libiksemel-utils_1.2-4_i386.deb
Files:
4be6656186ca3be579521d7d7ff74d34 1337 libs optional libiksemel_1.2-4.dsc
1eaebfc439bff99bf64b6ac88988eeab 16014 libs optional libiksemel_1.2-4.diff.gz
062091d623bf88afa19df7cd09936203 56704 libdevel optional
libiksemel-dev_1.2-4_i386.deb
811de80aaff42ef8a4a5aff2b4697b65 35212 libs optional libiksemel3_1.2-4_i386.deb
aa94c35eb97a9cdb45fea2123902d6e4 25790 utils optional
libiksemel-utils_1.2-4_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iQEcBAEBAgAGBQJIVs2wAAoJENIA6zCg+12m6T4H/2Q8inNNglimKNuadjC0Elg4
5qW3OLK0eGZJRn4hvXKrz6ca/XNgunv12oLNUSQsK6LYA8EpXpVUlYjbMoxVAomw
xFhy/eMzDrqYT6B1LKyq93jRWT3CxDIsd7i7QIm7ud0o3g8tuVrszBCz3WJ9/sJc
0LfqZbASg6+HX89CuD+btYnhWlb3zLhEoT9Cbindy/LC6CJzrbBO/ur8bT/RVQrt
lBoPnC41l36UCSMVqj+zQwsU31SXdSDjwNeqLq6617ZK+nVHtR7AXAJVsK4tommq
7trCptclyUrde1ZuxY9s5hc50aOcyssdvWgGIBGsrovh0BwgAG4h2DBsjcQbvyU=
=hU7H
-END PGP SIGNATURE-
Accepted:
libiksemel-dev_1.2-4_i386.deb
to pool/main/libi/libiksemel/libiksemel-dev_1.2-4_i386.deb
libiksemel-utils_1.2-4_i386.deb
to pool/main/libi/libiksemel/libiksemel-utils_1.2-4_i386.deb
libiksemel3_1.2-4_i386.deb
to pool/main/libi/libiksemel/libiksemel3_1.2-4_i386.deb
libiksemel_1.2-4.diff.gz
to pool/main/libi/libiksemel/libiksemel_1.2-4.diff.gz
libiksemel_1.2-4.dsc
to pool/main/libi/libiksemel/libiksemel_1.2-4.dsc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#485827: ITP: cpuset -- A tool to manage Linux cpusets
Subject: ITP: cpuset -- A tool to manage Linux cpusets Package: wnpp Owner: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Severity: wishlist * Package name: cpuset Version : 1.0 Upstream Author : Alex Tsariounov [EMAIL PROTECTED] * URL : http://developer.novell.com/wiki/index.php/Cpuset * License : GPLv2 Programming Lang: Python Description : A tool to manage Linux cpusets Linux cpusets allow system administrators to control which processes execute on a given processor or which share of a processor they have to take. This tool provides an interface to control these cpusets. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.25 (PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gsasl 0.2.21-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 13 Jan 2008 11:03:26 -0200 Source: gsasl Binary: libgsasl7 libgsasl7-dev gsasl Architecture: source i386 Version: 0.2.21-2 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: gsasl - GNU SASL command line utility libgsasl7 - GNU SASL library libgsasl7-dev - Development files for the GNU SASL library Closes: 448230 Changes: gsasl (0.2.21-2) unstable; urgency=low . * Bump debhelper compat to 5. * Switched to CDBS. * Includes shlibs files. (Closes: #448230) * Update Homepage field in control to the new format. * Added Vcs-Browser and Vcs-Git fields to source control. * Updated Standards-Version to 3.7.3.0: no changes needed Files: 5dc739a049763ff481d2640d3595e061 892 devel optional gsasl_0.2.21-2.dsc b05024178b2e65bea0643c1ade695dbb 25566 devel optional gsasl_0.2.21-2.diff.gz 2168fdad1bdca6b7f1021f535a209e6c 211472 libdevel optional libgsasl7-dev_0.2.21-2_i386.deb 9ddeeb42d7e39e6938b9a0095404d663 138268 libs optional libgsasl7_0.2.21-2_i386.deb 691163b1ba0b8d551ed2419c2430b5e4 164404 devel optional gsasl_0.2.21-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHkgNWWSOgCCdjSDsRAptmAJ95zlroHpMhZH/CnnSykS7ZvHTr9QCdHP56 CWdOaejYAOg21f8wJeoD90M= =dq/f -END PGP SIGNATURE- Accepted: gsasl_0.2.21-2.diff.gz to pool/main/g/gsasl/gsasl_0.2.21-2.diff.gz gsasl_0.2.21-2.dsc to pool/main/g/gsasl/gsasl_0.2.21-2.dsc gsasl_0.2.21-2_i386.deb to pool/main/g/gsasl/gsasl_0.2.21-2_i386.deb libgsasl7-dev_0.2.21-2_i386.deb to pool/main/g/gsasl/libgsasl7-dev_0.2.21-2_i386.deb libgsasl7_0.2.21-2_i386.deb to pool/main/g/gsasl/libgsasl7_0.2.21-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libntlm 0.3.13-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Sep 2007 10:14:45 -0300 Source: libntlm Binary: libntlm0 libntlm0-dev Architecture: source i386 Version: 0.3.13-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libntlm0 - NTLM authentication library libntlm0-dev - Development files for the NTLM authentication library Closes: 432220 443445 Changes: libntlm (0.3.13-1) unstable; urgency=low . * New upstream release (Closes: #432220) * New maintainer (Closes: #443445) * Uses substvar binary:Version instead of Source-Version for binary NMUs * Complies with policy 3.7.2.2 * Does not ignore make clean errors Files: 69f76e196417ff74a6f1b13965126786 619 libs optional libntlm_0.3.13-1.dsc 14e8aa077e032ae353b885a6d82ee668 419505 libs optional libntlm_0.3.13.orig.tar.gz f29de957cb7883eef3f5135ecb1f818d 24829 libs optional libntlm_0.3.13-1.diff.gz 12cbeb6afec37572f95fa6f9b4e85b49 22078 libdevel optional libntlm0-dev_0.3.13-1_i386.deb 230f9d5d45870e0207d26ef33f1d3e7c 15398 libs optional libntlm0_0.3.13-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG9Q6I7tjUzB3rjq4RAjIeAJ9VT3fd3D8DYkDrwOSPz0GY7TpBZQCfalIN 1B7SCBVcn/Z44cr4iBgZsjw= =Pqpi -END PGP SIGNATURE- Accepted: libntlm0-dev_0.3.13-1_i386.deb to pool/main/libn/libntlm/libntlm0-dev_0.3.13-1_i386.deb libntlm0_0.3.13-1_i386.deb to pool/main/libn/libntlm/libntlm0_0.3.13-1_i386.deb libntlm_0.3.13-1.diff.gz to pool/main/libn/libntlm/libntlm_0.3.13-1.diff.gz libntlm_0.3.13-1.dsc to pool/main/libn/libntlm/libntlm_0.3.13-1.dsc libntlm_0.3.13.orig.tar.gz to pool/main/libn/libntlm/libntlm_0.3.13.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted gsasl 0.2.21-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 21 Sep 2007 17:53:04 -0300 Source: gsasl Binary: libgsasl7 libgsasl7-dev gsasl Architecture: source i386 Version: 0.2.21-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: gsasl - GNU SASL command line utility libgsasl7 - GNU SASL library libgsasl7-dev - Development files for the GNU SASL library Closes: 335417 402156 402158 442273 Changes: gsasl (0.2.21-1) unstable; urgency=low . * New upstream release (Closes: #402156, #402158) * Does not ignore make clean errors * New Maintainer (Closes: #442273) * Replaced substvar Source-Version by binary:Version for binary NMUs * Updated Standards-Version up to 3.7.2.2 * Updated copyright to the right versions of GPL and LGPL. * Enables ntlm support (Closes: #335417) Files: 6cdc60170fb39e854ff5aca6404ee273 734 devel optional gsasl_0.2.21-1.dsc e4e3ad374a5317d0860b08aa0b5c63b6 3293537 devel optional gsasl_0.2.21.orig.tar.gz 6f82d5eaf92b14913ba052ebd5c3a970 25970 devel optional gsasl_0.2.21-1.diff.gz 8a7cc3589ab5f805eaeb7aac1c99c3c3 192584 libdevel optional libgsasl7-dev_0.2.21-1_i386.deb 90276de836572e372d82b07ddbffb4db 111674 libs optional libgsasl7_0.2.21-1_i386.deb 3e6bf8886832f3134a7966afecb5c0e9 137212 devel optional gsasl_0.2.21-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG9Q7p7tjUzB3rjq4RAl+VAJ4kul7OvoL7KVh3Am08DO0W9vi0PgCfcCY2 trDmuKIvlIzKAB5zZjSukiA= =LbUL -END PGP SIGNATURE- Accepted: gsasl_0.2.21-1.diff.gz to pool/main/g/gsasl/gsasl_0.2.21-1.diff.gz gsasl_0.2.21-1.dsc to pool/main/g/gsasl/gsasl_0.2.21-1.dsc gsasl_0.2.21-1_i386.deb to pool/main/g/gsasl/gsasl_0.2.21-1_i386.deb gsasl_0.2.21.orig.tar.gz to pool/main/g/gsasl/gsasl_0.2.21.orig.tar.gz libgsasl7-dev_0.2.21-1_i386.deb to pool/main/g/gsasl/libgsasl7-dev_0.2.21-1_i386.deb libgsasl7_0.2.21-1_i386.deb to pool/main/g/gsasl/libgsasl7_0.2.21-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted udns 0.0.9-2 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Wed, 12 Sep 2007 09:39:36 -0300
Source: udns
Binary: libudns0 udns-utils libudns-dev
Architecture: source i386
Version: 0.0.9-2
Distribution: unstable
Urgency: low
Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED]
Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED]
Description:
libudns-dev - async-capable DNS stub resolver library, development files
libudns0 - async-capable DNS stub resolver library
udns-utils - Several DNS-related utilities built on top of udns library
Closes: 437890
Changes:
udns (0.0.9-2) unstable; urgency=low
.
* debian/rules: links debian/README to
debian/package.README.Debian. Closes: #437890
* Do not use DH_COMPAT but debian/compat, changed from 4 to 5, changed
Build-Depends too.
* Replaced ${Source-Version} with ${binary:Version}.
Files:
986f00d442477fdcbc68666ef1f908f3 599 libs optional udns_0.0.9-2.dsc
7705c9e7852532e8e346deb72d4536c5 5699 libs optional udns_0.0.9-2.diff.gz
614402a6b94e974c9103b192bdc5d1d6 32814 libs optional libudns0_0.0.9-2_i386.deb
143d96f23f6ef12b5e08adcaf8b9c285 56984 libdevel optional
libudns-dev_0.0.9-2_i386.deb
d60116c0b16e39f6805ddeb6a57c05ec 31194 net optional udns-utils_0.0.9-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFG5983D99I1lm5V64RAjwfAJ93YbbADWYVNx6TDMQsujDPHisz1wCcDrL6
qSrwbqjT4g0yNsFN5SFGURg=
=9HZs
-END PGP SIGNATURE-
Accepted:
libudns-dev_0.0.9-2_i386.deb
to pool/main/u/udns/libudns-dev_0.0.9-2_i386.deb
libudns0_0.0.9-2_i386.deb
to pool/main/u/udns/libudns0_0.0.9-2_i386.deb
udns-utils_0.0.9-2_i386.deb
to pool/main/u/udns/udns-utils_0.0.9-2_i386.deb
udns_0.0.9-2.diff.gz
to pool/main/u/udns/udns_0.0.9-2.diff.gz
udns_0.0.9-2.dsc
to pool/main/u/udns/udns_0.0.9-2.dsc
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using standardized SI prefixes
On Fri, Jun 15, 2007 at 01:46:10PM -0400, Phillip Susi wrote: Because we needed a name, and Kilo is a good one to use. There is no rule that says you can't use the word for a different meaning in a different context. Which context would this be? Computer Science? Computer Engineering? Computer Networks? Storage Disks? Magnetic or Optical? File sizes? Memory size? Cache size? I agree that in computer science, many (not necessarily most of) times it would very bad sense to use a power of 10 instead of a power of 2. Like back when they used ten's complement. However, this makes the point stronger, since 10 was a base used with some digital computers. And before computers were invented the word mouse always referred to a small hairy rodent. I don't see you complaining that it can also refer to the computer pointing device on your desk. When someone says they caught a mouse or they clicked with their mouse, you can easily infer which one they mean. Yes. But you can't infer which one (1000 or 1024) MB mean. When you buy a disk, what do the vendor says the capacity is? 80 GB. But your software states it is no more than 75GB. What the fuck!? If GiB is confusing to users, so is base 2. People use base 10 and k (kilo) means 1000, M (Mega) means 10^6, G (Giga) means 10^9, etc., because they are used to base 10. I don't want to read some manual or source code just to know which base is used when I read or write 10G. When I write, how can I unambiguously tell the program that I mean 1000 or 1024? Only using G and Gi, this would be possible. The context clearly indicates the meaning is 1024. When referring to bytes that context uses 1024. Also capitalizing the K is another indicator. There is no ambiguity in that sentence to anyone familiar with the computer science context. When you use K, this could be true. But remember not all users are familiar with the computer science context. So, you type 600 and see 5.7MB. And users not familiar with the computer science context will think: What the ...?. So, if reading 5.7MiB will do them no favor, that should read 6.0MB. Regards, Thadeu Cascardo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GSASL Maintainer Missing in Action?
Hello, libgsasl and libntlm are maintained by Yvan Bassuel and were uploaded by Anibal Salazar. I am CC'ing them. Two weeks ago I've sent an email no Yvan, asking if he was still interested in maintaining those packages. Both have newer upstream versions. There is a bug with a patch for libgsasl7 that was not answered by Yvan. It is dated as of last December. libgasl7 and libntlm0 were last uploaded in March 2006 and June 2006, respectively. I've sent another message to Yvan on Monday. Does anyone know the whereabouts of Yvan? May I consider him missing in action? I am interested in maintaining those packages. How should I proceed? NMU before taking maintainership and wait another two weeks? Take maintainership now? Or wait another two weeks and, then, uploading those new versions? (I will need sponsorship, but that I can arrange.) Best Regards, Thadeu Cascardo. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted udns 0.0.9-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 1 Mar 2007 23:00:48 -0300 Source: udns Binary: libudns0 udns-utils libudns-dev Architecture: source i386 Version: 0.0.9-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libudns-dev - async-capable DNS stub resolver library, development files libudns0 - async-capable DNS stub resolver library udns-utils - Several DNS-related utilities built on top of udns library Changes: udns (0.0.9-1) unstable; urgency=low . * New upstream release. Closes #408329 * Removes libudns.so in rules clean * Copies zone entries in rblcheck.c. Closes #403349 * Includes README and NEWS related to Debian explaining an ABI breakage * Back in sid. Closes #408820 * Install upstream NOTES and TODO Files: 73b00a7800e6dba6fad14b74483070a6 599 libs optional udns_0.0.9-1.dsc 78843added6f6b690bc6019ab8ef03c9 84307 libs optional udns_0.0.9.orig.tar.gz a56e9ac15f7e1574431833ac8ef4becf 5367 libs optional udns_0.0.9-1.diff.gz aa46f1ec8757f2b87e0cf28e9814ccbf 31918 libs optional libudns0_0.0.9-1_i386.deb e0eec0f21737e70a20d552850d3fdc49 56598 libdevel optional libudns-dev_0.0.9-1_i386.deb a6d80f6de6a1e686deaa693c9aee8d39 30930 net optional udns-utils_0.0.9-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF7MiMD99I1lm5V64RAm8uAKCk/YhHeUJboPTd47REx6r/CTU+QwCfXeuV zWkIeseSZx0xseZeWxRYCD8= =lb3m -END PGP SIGNATURE- Accepted: libudns-dev_0.0.9-1_i386.deb to pool/main/u/udns/libudns-dev_0.0.9-1_i386.deb libudns0_0.0.9-1_i386.deb to pool/main/u/udns/libudns0_0.0.9-1_i386.deb udns-utils_0.0.9-1_i386.deb to pool/main/u/udns/udns-utils_0.0.9-1_i386.deb udns_0.0.9-1.diff.gz to pool/main/u/udns/udns_0.0.9-1.diff.gz udns_0.0.9-1.dsc to pool/main/u/udns/udns_0.0.9-1.dsc udns_0.0.9.orig.tar.gz to pool/main/u/udns/udns_0.0.9.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted udns 0.0.8-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 11 Dec 2006 20:50:35 -0200 Source: udns Binary: libudns0 udns-utils libudns-dev Architecture: source i386 Version: 0.0.8-2 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libudns-dev - async-capable DNS stub resolver library, development files libudns0 - async-capable DNS stub resolver library udns-utils - Several DNS-related utilities built on top of udns library Changes: udns (0.0.8-2) unstable; urgency=low . * Applied patch by Mikael Magnusson, to allow udns to be used in C++ programs. Should use dpatch and report upstream. Closes #400476 Files: 3f83a626976e807b95022702a0043ec4 599 libs optional udns_0.0.8-2.dsc 390f0668a9b7d965701ce4d693ffed51 4140 libs optional udns_0.0.8-2.diff.gz 010cb6dbd0ef60001b7c98795a79f5da 22642 libs optional libudns0_0.0.8-2_i386.deb 7732ce831ef9553fc9de2f691581d43f 46042 libdevel optional libudns-dev_0.0.8-2_i386.deb fdb2184e169e4dfcf95a3f5c0adf491e 22234 net optional udns-utils_0.0.8-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFfeTtD99I1lm5V64RAgEoAJkBJt8HrvaqKat0q3zXPVnXrYOsVgCdEEyA VDPs2T9SjV9NeTxeg1FLezo= =OLpz -END PGP SIGNATURE- Accepted: libudns-dev_0.0.8-2_i386.deb to pool/main/u/udns/libudns-dev_0.0.8-2_i386.deb libudns0_0.0.8-2_i386.deb to pool/main/u/udns/libudns0_0.0.8-2_i386.deb udns-utils_0.0.8-2_i386.deb to pool/main/u/udns/udns-utils_0.0.8-2_i386.deb udns_0.0.8-2.diff.gz to pool/main/u/udns/udns_0.0.8-2.diff.gz udns_0.0.8-2.dsc to pool/main/u/udns/udns_0.0.8-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted udns 0.0.8-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 2 Sep 2006 22:52:04 -0300 Source: udns Binary: libudns0 udns-utils libudns-dev Architecture: source i386 Version: 0.0.8-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libudns-dev - async-capable DNS stub resolver library, development files libudns0 - async-capable DNS stub resolver library udns-utils - Several DNS-related utilities built on top of udns library Changes: udns (0.0.8-1) unstable; urgency=low . * Moved upstream debian changelog into upstream changlog. * Changed rules to install doc changelog. * Changed maintainer to me. * Fixed sections for Source and Binary packages in control. * Fixed FSF address in copyright file. Files: 5aadaf670a6d4a7ea2f746c0346bcf23 599 libs optional udns_0.0.8-1.dsc 2452dfbeee2e18bc1ece07d53f79cfc7 64224 libs optional udns_0.0.8.orig.tar.gz 88aa081edc771d7225dcdc2228757c5c 3852 libs optional udns_0.0.8-1.diff.gz 147e660c7a4acf92bbe2972dd6042754 22504 libs optional libudns0_0.0.8-1_i386.deb b7da5bdd0ac53da80b10c0418814eed1 45956 libdevel optional libudns-dev_0.0.8-1_i386.deb 954a96bd35ebacc6a6767847b8c0cc41 22102 net optional udns-utils_0.0.8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFPXK9D99I1lm5V64RAjcrAJ9FSDvAs3Pvv0uT3vuoecPOnqTbGQCgoweu 2eFy73qxSAnJLVWQUEfc1JY= =0Zg6 -END PGP SIGNATURE- Accepted: libudns-dev_0.0.8-1_i386.deb to pool/main/u/udns/libudns-dev_0.0.8-1_i386.deb libudns0_0.0.8-1_i386.deb to pool/main/u/udns/libudns0_0.0.8-1_i386.deb udns-utils_0.0.8-1_i386.deb to pool/main/u/udns/udns-utils_0.0.8-1_i386.deb udns_0.0.8-1.diff.gz to pool/main/u/udns/udns_0.0.8-1.diff.gz udns_0.0.8-1.dsc to pool/main/u/udns/udns_0.0.8-1.dsc udns_0.0.8.orig.tar.gz to pool/main/u/udns/udns_0.0.8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libiksemel 1.2-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 28 Sep 2006 23:25:06 -0300 Source: libiksemel Binary: libiksemel-utils libiksemel3 libiksemel-dev Architecture: source i386 Version: 1.2-3 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libiksemel-dev - C library for the Jabber IM platform libiksemel-utils - utilities from the iksemel library libiksemel3 - C library for the Jabber IM platform Closes: 390068 Changes: libiksemel (1.2-3) unstable; urgency=low . * Fixed info file installation in rules and libiksemel-dev.info. closes: #390068 * Added HACKING file to libiksemel-dev docs. * Updated Standards-Version to 3.7.20, no changes required. * Removed prerm and postrm since dh_installinfo automatically generates them for the purpose they were being used. * Modified source texinfo file to include the section and description for the info directory, which install-info will use. * Added Section for source in control. * Included texinfo as Build-Dep. * Removed useless libiksemel-utils.dirs. * Changed packages descriptions. * Added copyright and the LGPL notices to the copyright file. Files: 7502be30057a98995b8a8951efa8fda9 655 libs optional libiksemel_1.2-3.dsc 1d771761699a14e05110c952ca5b79d8 14924 libs optional libiksemel_1.2-3.diff.gz 69ae1762bb00358993d297ee50e4f583 56254 libdevel optional libiksemel-dev_1.2-3_i386.deb 1d9126d1081c00b77d105280b099d0ef 34260 libs optional libiksemel3_1.2-3_i386.deb e08e6dd8ed31e69113d72659b74be26d 24040 utils optional libiksemel-utils_1.2-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFHIn+GJU/LHOwJZIRAg8FAKCB1GAGRSF3K3D/4FvOhCFAXr1/vQCgtult FsHS5W99REbDwAsOLORGDSU= =Rohi -END PGP SIGNATURE- Accepted: libiksemel-dev_1.2-3_i386.deb to pool/main/libi/libiksemel/libiksemel-dev_1.2-3_i386.deb libiksemel-utils_1.2-3_i386.deb to pool/main/libi/libiksemel/libiksemel-utils_1.2-3_i386.deb libiksemel3_1.2-3_i386.deb to pool/main/libi/libiksemel/libiksemel3_1.2-3_i386.deb libiksemel_1.2-3.diff.gz to pool/main/libi/libiksemel/libiksemel_1.2-3.diff.gz libiksemel_1.2-3.dsc to pool/main/libi/libiksemel/libiksemel_1.2-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted libiksemel 1.2-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 25 Oct 2005 18:58:28 -0200 Source: libiksemel Binary: libiksemel-utils libiksemel3 libiksemel-dev Architecture: source i386 Version: 1.2-2 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libiksemel-dev - iksemel is a C library for the Jabber IM platform libiksemel-utils - iksemel is a C library for the Jabber IM platform libiksemel3 - iksemel is a C library for the Jabber IM platform Closes: 335758 Changes: libiksemel (1.2-2) unstable; urgency=low . * Build-Depends on libgnutls-dev instead of libgnutls11-dev, closes: #335758 * Renames package from libiksemel1 to libiksemel3, fixing the soname relationship with the package name. * Builds a new package which distributes the utilities, libiksemel-utils. Files: ed933d65989da2f27d3159e1d03a756b 647 - optional libiksemel_1.2-2.dsc d57bb07016bbba41a314828f56651b66 1752 - optional libiksemel_1.2-2.diff.gz e8decdabeff8a1e9b93c16e902651283 37484 libdevel optional libiksemel-dev_1.2-2_i386.deb 9306e02ab8cbb5660b0035385ec34555 33514 libs optional libiksemel3_1.2-2_i386.deb 1be0f55fb3cf0e1fecaab966d5e95057 23194 utils optional libiksemel-utils_1.2-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD/NmRt1anjIgqbEsRAnf3AKCJmKBoiho8Ef4+iLk9sv0vttlAcwCgmOX/ Cul7jiGWDJ8D1FqF8U4oz50= =Yn30 -END PGP SIGNATURE- Accepted: libiksemel-dev_1.2-2_i386.deb to pool/main/libi/libiksemel/libiksemel-dev_1.2-2_i386.deb libiksemel-utils_1.2-2_i386.deb to pool/main/libi/libiksemel/libiksemel-utils_1.2-2_i386.deb libiksemel3_1.2-2_i386.deb to pool/main/libi/libiksemel/libiksemel3_1.2-2_i386.deb libiksemel_1.2-2.diff.gz to pool/main/libi/libiksemel/libiksemel_1.2-2.diff.gz libiksemel_1.2-2.dsc to pool/main/libi/libiksemel/libiksemel_1.2-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian based GNU/Solaris: pilot program
On Fri, Nov 04, 2005 at 07:40:34AM -0500, Michael Poole wrote: Frank Küster writes: Michael Poole [EMAIL PROTECTED] wrote: Andrew Suffield writes: On Thu, Nov 03, 2005 at 12:48:53PM -0800, Erast Benson wrote: CDDL works similar way, except on per-file basis. This is incomprehensible gibberish. This is unsupportable hyperbole. Erast's statement may be inapt, wrong, misleading, or have any number of other flaws, but it is neither incomprehensible nor gibberish. I do not comprehend what he means with CDDL works on a per-file basis, GPL does not. One can of course create a project made up of GPL'ed source files and other source files with different, GPL-compatible licenses. The CDDL (based as it is on the MPL) allows you to mix CDDL-licensed files in a project with files under CDDL-incompatible licenses and distribute the resulting executable. The GPL applies to the work as a whole. The relevant sections of the GPL are below; this trait is why people say that, even though CDDL is a copyleft license, it allows developers to create proprietary applications on top of the CDDL base. Sorry, but the relevant sections below do not belong to the GPL, but to the CDDL. 1.3. Covered Software means (a) the Original Software, or (b) Modifications, or (c) the combination of files containing Original Software with files containing Modifications, in each case including portions thereof. 1.9. Modifications means the Source Code and Executable form of any of the following: A. Any file that results from an addition to, deletion from or modification of the contents of a file containing Original Software or previous Modifications; B. Any new file that contains any part of the Original Software or previous Modification; or C. Any new file that is contributed or otherwise made available under the terms of this License. 1.12. Source Code means (a) the common form of computer software code in which modifications are made and (b) associated documentation included in or with such code. 3.1. Availability of Source Code. Any Covered Software that You distribute or otherwise make available in Executable form must also be made available in Source Code form and that Source Code form must be distributed only under the terms of this License. You must include a copy of this License with every copy of the Source Code form of the Covered Software You distribute or otherwise make available. You must inform recipients of any such Covered Software in Executable form as to how they can obtain such Covered Software in Source Code form in a reasonable manner on or through a medium customarily used for software exchange. Does this help? Michael Poole Thadeu Cascardo -- signature.asc Description: Digital signature
Re: Request: Source for parts of GNU/Solaris
On Mon, Nov 07, 2005 at 04:48:52PM -0800, Erast Benson wrote: Dear Erast! On Tuesday 08 November 2005 01:01, Erast Benson wrote: Specifically requested were the source for libintl.so.3, libiconv.so.2, libc.so.1, libz.so, libbz2.so.1.0, and libgcc_s.so.1, which must be provided under terms no more restrictive than GPL sections one and two. http://www.gnusolaris.org/cgi-bin/trac.cgi/browser/gnusolaris1/gnu its in progress process, we are moving gnusolaris1/gnu code to .. you have to look at both directories at this point. Sorry for inconvenience. Also some stuff not committed yet, becase we are testing them. In 2-3 months we are hoping to sort out all these starting issues with code browsing, scripts availability, etc. The GPL specifically requests that offers for download are made offering equivalent access to copy the source code from the same place. While I appreciate the fine source control browser, I really cannot download the whole sources over this interface. Notwithstanding the technical difficulties www.gnusolaris.org is *the same place*. [...] *equivalent* access [...] If binaries are distributed in an ISO image, you should distribute the sources in an ISO image too. Erast Thadeu Cascardo. -- signature.asc Description: Digital signature
Re: ITP: g-wrap -- Scripting interface generator for C
Please, check the following bugs, rename or close them, however you prefer. 1) #242467: ITA: gwrapguile -- Tool for exporting C libraries into Scheme int 2) #263127: O: gwrapguile -- g-wrap: Tool for exporting C libraries into Sche Thanks, Thadeu Cascardo signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activity monitor
On Wed, Dec 08, 2004 at 12:00:14AM -0800, Steve Langasek wrote: On Tue, Dec 07, 2004 at 11:17:46AM -0300, Fabricio Cannini wrote: --- Michelle Konzack [EMAIL PROTECTED] escreveu: Am 2004-12-07 10:39:42, schrieb Fabricio Cannini: Me wonders if simply NOT installing hot-babe wouldn't fix this. IMO Seems to be the easiest solution. In theory ! In many countries it is illegal to have some stuff on CD or other Media. Don't put it on the CD!! And WHO stores the CD-Images ? Servers located on coutries that do not have such prohibitions would store these packages. I'm talking about NOT putting such packages in the official medias (CDs, .iso, etc). I don't think this is a very useful compromise. If a package is going to be included in the Debian archive, it should also be included in the official Debian CD sets. I think it's a good idea to provide enough metadata in the archive to let people build localized CD sets that are legal in their jurisdiction, but I don't think we should be excluding any Debian packages from official CD sets -- if there are reasons that we can't distribute a package in main as part of our CD images, we shouldn't be distributing it from the mirrors either. What about non-US? If some packages can be distributed from only some mirrors outside US, why shouldn't some packages be distributed only from some countries where they are legal to be distributed? Or are there only two countries for Debian? US (main) and non-US? Regards, Thadeu Cascardo. ObRC: #245810 -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bug#283578: ITP: hot-babe -- erotic graphical system activitymonitor
On Thu, Dec 02, 2004 at 07:18:58PM +0100, cobaco (aka Bart Cornelis) wrote: It is impossible for Debian to cater to all different ideas of what's acceptable and what's not (prOn-lovers is just as valid a group as prOn-haters). For that reason alone it's rather pointless for Debian _as_a_whole_ to enforce any kind of policy (beyond 'it must be Free'), What we _should_ do is make it easy for any group/person to exclude on CD's/ mirrors/installations whatever they find offensive/unacceptable. At the moment is perfectly possible to exclude whatever you find offensive from you own installation, what appears to be lacking is an easy way to exclude those packages from a CD/Mirror (maybe something like an 'exlude everything with a certain debtag' option for the CD/mirrorring scripts) Any group of Debian users that cares enough about an issue (whether prOn, religion, politics, vi-usage, ...) can then make their own set of metadata to distinguish things acceptable from things unacceptable. It is not (and should not be) Debian's job to cater to their sensitivities. -- Cheers, cobaco (aka Bart Cornelis) My opinion is that if master or non-us can't distribute it and we find any interested mirror which can and would distribute it, then Debian should make it possible. Perhaps, being more worldwide aware would be a very good thing for Debian. Since there's only non-us, we should conclude that Debian is very US-concerned. As someone has pointed out, having 10 lawyers for each developer is not wanted. But since someone can point it out that there are issues distributing any software, we should search for a mirror where we could be located and try to get people to be concerned about those packages. My half cent. Regards, Thadeu Cascardo. signature.asc Description: Digital signature
Accepted libiksemel 1.2-1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 25 Nov 2004 02:18:51 -0200 Source: libiksemel Binary: libiksemel1 libiksemel1-dev Architecture: source i386 Version: 1.2-1 Distribution: unstable Urgency: low Maintainer: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Changed-By: Thadeu Lima de Souza Cascardo [EMAIL PROTECTED] Description: libiksemel1 - iksemel is a C library for the Jabber IM platform libiksemel1-dev - iksemel is a C library for the Jabber IM platform Closes: 282266 282296 Changes: libiksemel (1.2-1) unstable; urgency=low . * New upstream release * New Maintainer, closes: #282296 * Included pkg-config file in libiksemel1-dev, closes: #282266 Files: ede2af8af4d6160b70d68e75ff24991a 630 - optional libiksemel_1.2-1.dsc 82e7c8fdb6211839246b788c040a796b 429405 - optional libiksemel_1.2.orig.tar.gz 87716d489aa00baef1f8a0c1b363bf46 1327 - optional libiksemel_1.2-1.diff.gz b9f92461f74b22a2b431871ba567b3d7 64534 libdevel optional libiksemel1-dev_1.2-1_i386.deb e90fbff82cdadc46d30f2a4f119aa6d0 32960 libs optional libiksemel1_1.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBrGKKt1anjIgqbEsRAh01AKDBEZHSb2GeAi/HNBiT6lLkUv4RLACg43Md Eejv3MwwfKBeE2UlMYXLlbU= =f32M -END PGP SIGNATURE- Accepted: libiksemel1-dev_1.2-1_i386.deb to pool/main/libi/libiksemel/libiksemel1-dev_1.2-1_i386.deb libiksemel1_1.2-1_i386.deb to pool/main/libi/libiksemel/libiksemel1_1.2-1_i386.deb libiksemel_1.2-1.diff.gz to pool/main/libi/libiksemel/libiksemel_1.2-1.diff.gz libiksemel_1.2-1.dsc to pool/main/libi/libiksemel/libiksemel_1.2-1.dsc libiksemel_1.2.orig.tar.gz to pool/main/libi/libiksemel/libiksemel_1.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
