Accepted shellinabox 2.21 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 09 Sep 2018 12:10:40 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.21 Distribution: unstable Urgency: medium Maintainer: Marc Singer Changed-By: Marc Singer Description: shellinabox - publish command line shell through AJAX interface Changes: shellinabox (2.21) unstable; urgency=medium . * Patched DoS vulnerability reported by Imre Rad. Checksums-Sha1: dfc679198ae01ebce510d84016c9c2e730ccd896 1645 shellinabox_2.21.dsc 91778009ece371e8eb32bb6a60483e57b86723af 667672 shellinabox_2.21.tar.xz 8006e7176441e12327dd146d9df007fb41c774d1 236976 shellinabox-dbgsym_2.21_amd64.deb e4dcfba8a19545b7e56c63a8451f1243a9606d84 6300 shellinabox_2.21_amd64.buildinfo 64788d045106e70e8f5dc1343e43eaa67e31c09d 125532 shellinabox_2.21_amd64.deb Checksums-Sha256: 94f6e4b7259db30dc6e575fc6d97eef3cbbd66915b0b0df00ac8b1ba3303ce2b 1645 shellinabox_2.21.dsc 4ec657182b3ec628c2a7b036b360011cef51a23104b2eb332eafede56528a632 667672 shellinabox_2.21.tar.xz 8856dae7c19914bb831838c1f6dbc995bd09a03e916dc6553dd38f770e7864f4 236976 shellinabox-dbgsym_2.21_amd64.deb 50c771f4ec2484e6f899d108813770620bb8dbbe84f928d28e524caea549fd65 6300 shellinabox_2.21_amd64.buildinfo 2dce15029591ae88901d66481d6c29b3863870b3e980ce51c191220d4a1eff0d 125532 shellinabox_2.21_amd64.deb Files: 74c1795abefdd3159f7c3d974c50583c 1645 web optional shellinabox_2.21.dsc eb0e09b82e0dd10f94e882b8f38e9438 667672 web optional shellinabox_2.21.tar.xz d3aa8aa71ee8588a7c3ecdf268b43b6f 236976 debug optional shellinabox-dbgsym_2.21_amd64.deb 4859723d861620c019a45f882aaddfd3 6300 web optional shellinabox_2.21_amd64.buildinfo dc26dec82dff57b0036f356e3fb9e0f4 125532 web optional shellinabox_2.21_amd64.deb -BEGIN PGP SIGNATURE- iQJDBAEBCAAtFiEEpMoD+C8aMr2eF0HMGswR/n05ITwFAluVc3IPHGVsZkBkZWJp YW4ub3JnAAoJEBrMEf59OSE80noP/jD18PtbD4dnbl3Eb5ydQHmcDyAf3DBIYk29 sVK9inStz85fY+DQnhGTGSbNRo9N4zFsEB2ix0ZV10fiLPueisShpTXbf6dfBK6J H2bzHtCWlKlh+QowGjYjb6gt6W1sGlEVMm5/DGjqM++0uKsm91AaHZS6A0cWJFmb VDym4vb9DCmpRg/GGDyR7PZ+cjXapzSULwFs7Ye72Gi3gseCY2oc/6QAKTnklhyQ hMY6UTfZtVmhoz+1lH8OHTqfNeoCMTbHMZF2OHbBHX0cisKmtPAmPyxkyfWDPPvO J/hgqfSU70/KeVt31eWnegkdGbX3tHDcmiaAPG25shHd3Kx+xQioL5tKALgKW3q+ t1aKILhrp54GH+dwz/aRsOGq3Lb3Quc7dGvu3KGEkBv+IqwJBqq6u1O+oNCe5Gdh hjLulsgozyPHcH/PgGHf+smeyO90NZMUtC7svrjEC/7NNBulGg+as1ENusx+II9i dI+Qux66F/kjIyS2PavsgE5Q2BZip4zZmw6NhBBwcT2RpM0d7AsKl30LZHMCBLUF 2/F+cpaN2EUQfBuBnkOSurf7pXjFbScJ9vGjYNPR8DgYnqHkG24qXB1w8gt+u0U8 8TvQuv4YU8ul6CqH4zGK8/adod8l74Y9eTHaZca1ZNtcz1c9/MRmwa7vCiWCLQ0r pcVcxxUe =H+vY -END PGP SIGNATURE-
Accepted shellinabox 2.20 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 09 Nov 2016 09:52:24 -0800 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.20 Distribution: unstable Urgency: medium Maintainer: Marc Singer <e...@debian.org> Changed-By: Marc Singer <e...@debian.org> Description: shellinabox - publish command line shell through AJAX interface Closes: 828542 839066 839067 Changes: shellinabox (2.20) unstable; urgency=medium . * Fixed issue #222, LOGIN service * Fixed issue #360, ignore escape sequences to fix dir listing * Fix for function key presses * Adjusting scale on IE * New option to disable peer check (#364) * Add option for custom SSH port * Support for APL characters * PDF documentation * Fix for BSD build * New ready event support * OpenSSL 1.1 fixes (Closes: #828542) * May build with MUSL library * Documentation added that SSL support is optional and requires installation of openssl on Debian. (Closes: #839067) * Jessie requires explicit installation of openssl because the default package does not include the necessary utilities to support creation of certificates. (Closes: #839066) Checksums-Sha1: 86cd163df62988dea0ec64ccf019002fc22b275f 1616 shellinabox_2.20.dsc 41d28d816cf63fdf3e0de45bdd1878a2d88aac7b 666368 shellinabox_2.20.tar.xz f89a138d3e3aa5a1837ed519af663cd4638d8882 277692 shellinabox-dbgsym_2.20_amd64.deb 461aa427866eaac9a52554a55470fc707404ffd4 124930 shellinabox_2.20_amd64.deb Checksums-Sha256: 01bf4a5b0ea3b2dfb725c7c60e545056ee4d567df69c89cec78ad954aab9e830 1616 shellinabox_2.20.dsc 3a234302fe8d8fdabe20ed31d3b198599e369c6b79cdc4dd11fa43a7fd4803fa 666368 shellinabox_2.20.tar.xz a9afa598ed8553d067ffd7f9cbecb1d02a7d85a0308b752c47c3ce4404c410a1 277692 shellinabox-dbgsym_2.20_amd64.deb e8a74c40ea3cc6370b6d26586a20997aa7b60538e7e603387a25ef7d9f180bcb 124930 shellinabox_2.20_amd64.deb Files: 9bd1a91d8a7fa2447c45823a8d8d882c 1616 web optional shellinabox_2.20.dsc 27307bc2ebf718ae9e241a092b4c15f0 666368 web optional shellinabox_2.20.tar.xz e92a1683f7a15ed16f8b7e24ae480b24 277692 debug extra shellinabox-dbgsym_2.20_amd64.deb cfe8f7006cbdd242c9dacf8965a5923b 124930 web optional shellinabox_2.20_amd64.deb -BEGIN PGP SIGNATURE- iQIsBAEBCAAWBQJYI3zZDxxlbGZAZGViaWFuLm9yZwAKCRAazBH+fTkhPJTZD/4i BJYlrjqXtuuafg1iFxagzQ0Ii4vs5d2AG3lOxG9dHlaRBfXZ6/L8crKm47Q4MmWj 2J6kxt4m3JboF5FJ/AVTT+ongru7JK8bXBnNcV6dbfS1IaUA113x8/XlhkxcFW1L E75UDm1A9ylNOfZoddQaV4JcxKtEqV+wO7XxKEuJ4bQtVgnC7u5aK+RRoeIBFDwW BjHoh0VcPSrb+HGdiNmhTzChptzBosS8fQYROu4qQLWhy99JOb2C+jjkZlqN8cZR cVkpaLRqpWMsfJsltCJD3623axCaUDeIEW72l4L+t8Uhy/vozfp3d+4GPDHUaWhS 3mpOxd2U5gZeSDZTQwE6HunvGGG2iPtPoAxAAsXTtNArU8sHaVEzB+KrseJfMf/l kOGzwZ25G3rY5MIlDlzOSWhGSf2k5szU48JfljUtebLdvjJUZAfWRLQ24AUo/SCi keZY36fgGl84Vpwk/2TJCIfbeWexAyqDroOkVKvIv2m8aqY67NKotQKmrA77ovOz o6Dxv7pUqJribYE2yfBmM1zWDh6Vaj1i0xgo0VzP2qjv2hqpe05gZgJJSbEGu+8z SEtx7/oUMtaiT3w8PrcE7uopITfjFG2TaFqV7Ww9rinJQnsVDGBCr1ziCASGwRdP xTsfRNMxA3eG/vFXQ2LEwxvceSep6ROAYxBOX/vrng== =WwNJ -END PGP SIGNATURE-
Accepted buici-clock 0.4.9.4 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 23 Jul 2016 17:25:31 -0700 Source: buici-clock Binary: buici-clock Architecture: source amd64 Version: 0.4.9.4 Distribution: unstable Urgency: medium Maintainer: Marc Singer <e...@debian.org> Changed-By: Marc Singer <e...@debian.org> Description: buici-clock - attractive desktop clock Closes: 832295 Changes: buici-clock (0.4.9.4) unstable; urgency=medium . * Fixed source archive package build. (Closes: #832295) * Resolves some lintian issues. Checksums-Sha1: 3ba0758df4248d9597f7f97437bc9ff968b9e4d6 1466 buici-clock_0.4.9.4.dsc 16683a5fcb5b3c664b067f1b484b476f0b38083e 108988 buici-clock_0.4.9.4.tar.xz cfe844fd0f1dfbba40804feefe7b8117fdabe58a 87718 buici-clock-dbgsym_0.4.9.4_amd64.deb 6882a03d4ed0fb67ce689053da206f6236f83bab 28536 buici-clock_0.4.9.4_amd64.deb Checksums-Sha256: 8788b722b95c16fc0678d42e6bf4aa0e4842dbed393874c4a20a408530e67e17 1466 buici-clock_0.4.9.4.dsc f5138d220568e3ba5afd272c61a63e5a1a0009a6023387d2a0cbf15af9b3649f 108988 buici-clock_0.4.9.4.tar.xz 0a1c4c9533257c00ba4b682bb09666cf8fa9aefc57bc45067af396b218ebfec5 87718 buici-clock-dbgsym_0.4.9.4_amd64.deb 423bca38fc6f43c4a7a53f1119e2da831b845ab317dfc780fff0e439a288c425 28536 buici-clock_0.4.9.4_amd64.deb Files: bb8b655b142f7e503d2eeca69085f887 1466 x11 optional buici-clock_0.4.9.4.dsc 2e98428d4295690f80f5b817a6474b18 108988 x11 optional buici-clock_0.4.9.4.tar.xz c61065d4955b89e08cf05ace228f115d 87718 debug extra buici-clock-dbgsym_0.4.9.4_amd64.deb c0dfd89446d5530eccf7458e797d9fd7 28536 x11 optional buici-clock_0.4.9.4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXlAu+AAoJEBrMEf59OSE8wdwQAIH4RlO/AIlRW2gQyr8nIYCf Qg2wTfdXtvtj5dkW7imkgR6/X4VQgXDuuua4+SWORWg7aA8TCJBOGyPMt0tZR268 MU5nYJ2G7E9mKw3dvecPoZuHjQQOPRQ15kRMz7vKXNsg9IhWAn6NYytcukIkq8RZ H/pYEMRLu3FxMaABY4wC1Yg+5Cr2VBKpjVHWFU2P/IDG9TjoUjhcfr2gfc/j4F34 t8cH/pG5fgaV5ntdY4X2n3bXldFBbbBvpfUtiIBbpi5qRq1YfHZ96kRfUuVkasOZ F0yMTqOjB0U6uUg2m+Us64bMlW+L3mmMleuzOW69sMSajXgdcJm4Ri9F/1yFCeY4 moBIObOesYxPI2DCmt0cxhO+m9yE8prYGvd985NxjB/MMzUQBelfIHYPMmfRk6AW /KwEqjktTIxfWrQflCsCm3zZcr2AXODnDB7i4R6H2i6a6WN2Ugsnx4l69rZE6f5Q uJtDwtKV1dPVAkQUkN9LQC91g/T6JDtZMt0gIocB/njDT8RkeXJGtX8srximkiDn hxFuuZKZZYf9htpNuYKa81kTYuQiDcAbqTx5uglCzIk1svtQlztIzAt8sqYCZU8+ GLwxCKGdBhkpUwbnomsLpC9A90rVEwmVl2ueJaoyrXdiDOx6cwtoe6+GlaHt2I+m Jpezog2HVCqsatV2UZuw =d7eN -END PGP SIGNATURE-
Accepted buici-clock 0.4.9.3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 13 Jul 2016 23:05:35 -0700 Source: buici-clock Binary: buici-clock Architecture: source amd64 Version: 0.4.9.3 Distribution: unstable Urgency: low Maintainer: Marc Singer <e...@debian.org> Changed-By: Marc Singer <e...@debian.org> Description: buici-clock - attractive desktop clock Closes: 811782 Changes: buici-clock (0.4.9.3) unstable; urgency=low . * Fixed type conversion error in XBM file for C++11 and GCC-6. (Closes: #811782) Checksums-Sha1: 278b8339e4ba0d32db889d3e0232b16a49354c28 1457 buici-clock_0.4.9.3.dsc 4b1e4334631c79e50b0e60195e84a08d8968a003 293092 buici-clock_0.4.9.3.tar.gz ba542c6f1e1f3e74fd375747af6b16ac82961b49 88674 buici-clock-dbgsym_0.4.9.3_amd64.deb 400945dcfb24ad6d8454849510df4739e7bc9f3b 28694 buici-clock_0.4.9.3_amd64.deb Checksums-Sha256: 2d5558a79dfdc51b85f1954f3f3c066a3ebd9657fdad7b53ab44e62a9119ceb2 1457 buici-clock_0.4.9.3.dsc 42f05cafc4c83aa640198fced08526161c0ce6e0d12fc645bf1318b01b9d0fc5 293092 buici-clock_0.4.9.3.tar.gz f0026c35500141a2736dba6245e2a266c0de1a963b19f83f84caae13f08ae245 88674 buici-clock-dbgsym_0.4.9.3_amd64.deb e2e7dcf19cade6c197895a87f893bd13ddcb2d342c2ec8a4325145e74a8fd42a 28694 buici-clock_0.4.9.3_amd64.deb Files: 67d793b8fd8dbd3fdb99e36c4219eeb6 1457 x11 optional buici-clock_0.4.9.3.dsc 1e8b78f48a087eced9d8a78e1dd7dee0 293092 x11 optional buici-clock_0.4.9.3.tar.gz a59e81305389c6f2bfa26fe9c2f5f28a 88674 debug extra buici-clock-dbgsym_0.4.9.3_amd64.deb 1fb4e07b369da96ae1b668b4421c2798 28694 x11 optional buici-clock_0.4.9.3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXhyzIAAoJEBrMEf59OSE84v8P/A2aGaNK6od24WK1JGrcgukg 1uo7CtrMw5RD3I4C5a4ZK15qCijw4ml6UmOpYpQOOY231vUcZDCGPDIOwjoNZfcL +kPaLAi9ZTEBvXvBdUumd5AJ3p1f+5l7Y7Q64RRqmMzn7GMAYw3eucOQzUP2UmE5 4xJT30YmeHqt6ft7alIcYLwienFyxiGHLHV9mMdhF2CHmxsi8bm/XjE8WvhYR8CC nuUJZXRjMm8GzIE7mqkhDXlN/0SovlRI6RWx/BSG0/qbOnUQd6sLybafcjfZMsL2 vC+nQam4CqRA/YlEJh2bSzzyrdsUCf4ZPrA/te7mL/OBqmmTzg/gmChGzFhB/ETQ GGZN/QObOKdtI3JP4iXh7qXqyJgS8AX7IEZuZcZUkSg9UlTfox07rjPRBv8U4AtO XyJLWb1umxRw7Qpes5u2mbGpYP/MuKN66/UltnsNvY/z82AVn//Z20641P+aInZ8 lqz+heB9JKHHRK0sUczIbVQLw07FqUZS/xdvxdNGUbAAO/mpV3KxWZbffcBUy2zr ahiiJIhDzDrDrZWOvcVSqT9bj0FQ9M9KPGHimwh1RG9KYZYnN27YXA0wCvM7yj9z mAFQx+Q1YHbu0ja6dLpjV7m2sMzpCKj78sffyHQCPEvUoIgRYHWheX0NYbVA5xdo /grzxAS9+w2NnD5YkmJJ =gseA -END PGP SIGNATURE-
Accepted shellinabox 2.19 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 05 Dec 2015 10:24:12 -0800 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.19 Distribution: unstable Urgency: high Maintainer: Marc Singer <e...@debian.org> Changed-By: Marc Singer <e...@debian.org> Description: shellinabox - publish command line shell through AJAX interface Changes: shellinabox (2.19) unstable; urgency=high . * Added support for middle-click paste, #350. * Improved iOS support, #354. * New logic to enable soft keyboard icon, #119, #321, #354. * Disable HTTPS fallback using the URL /plain. Consequently disables automatic upgrades from HTTP to HTTPS, #355. (CVE-2015-8400). Checksums-Sha1: d7b5d4585bb4dc6628e782e59bc6428fb29100f6 1610 shellinabox_2.19.dsc 44708b876a923e948185f740b08803fa9e7e01f3 664704 shellinabox_2.19.tar.xz b9363d17e40c389b3e644b23a0056616399ae025 122282 shellinabox_2.19_amd64.deb Checksums-Sha256: dcf7e8ded2a4edb40db5118cbabc6a994ea6b1fd87997c65ca79f381b4be866e 1610 shellinabox_2.19.dsc a54c243fdec817fe66be843f69d04ccd4b6659ca5d37b07b822462e0524eb060 664704 shellinabox_2.19.tar.xz 75e144c6e464da1e53087050edd4684221d94af1050c1b5a60bdc62c233c8d4e 122282 shellinabox_2.19_amd64.deb Files: 62c4b16e84103fc3ca5449d2ebedd66c 1610 web optional shellinabox_2.19.dsc 36d4000648a8f29e83033f0b7f8501ee 664704 web optional shellinabox_2.19.tar.xz 2baf96c8b79222ea86c2e0753ca52536 122282 web optional shellinabox_2.19_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWYy+7AAoJEBrMEf59OSE8pMwP/R7XGQNAq7tFpfIOUTOiU+r3 H+6k8DwikwMHHZFQ1QsoAkCTKnZ6o1LmVS+W3vWS5nGoWrSBumCyXd/EZCr7o39d JXyBgINChqQ2UxO+YvyYYe9RaoQlPs+pPOM6nDX++YtKKzu+escU/taEG7j/RTpv laBhKm5EorwoGcepQgwrQoU8Qx88ycS0tHvIUDI47BVSHwCCbU8ePniMnhADhPgA RHctqDuXQJYEsfUFXnIcJm5MTVGiK2ZTms6/N2VzjDUQduMVpsKto65/fg+J87r2 76NiFNQD+UWnfhdehUSjy9VOh93cT6RA5xlhCNqF7da6Rmwy7rBqjcSSosusc+14 +FTVKsYYgd/e7DWnIujp66gBEBRhunn1tAg1olDH+UQzZNlrc9xQ8Iw4GYdN8u+M 7ZoTgQCM06kbbv2EIIvLiHdPEqMOidyRW8q1geIKC6YFsgRiDfCyC++ypBcYIHkv Zyko9LsMoARiVsjcvtJfdV6X/nYRC/poptuQXMqcE6Cv2fdrC1KU7DW0n+pbOp2Z NRKV6Dd+Jfsghjdxm/15CEo0o2uieK6yWcat1rWby0BkfaRjMgBaXEhaFUS5dI2X jFjOtqAkoIaXsx8OMlvi1giN8Fibxlq8OYhqXinVFvYc0Mu+bqfeVctwzuKo83OQ pXsXIbmZQxMPwiu2Y6Zk =gS1j -END PGP SIGNATURE-
Accepted shellinabox 2.18 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 10 Oct 2015 10:53:38 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.18 Distribution: unstable Urgency: low Maintainer: Marc Singer <e...@debian.org> Changed-By: Marc Singer <e...@debian.org> Description: shellinabox - publish command line shell through AJAX interface Changes: shellinabox (2.18) unstable; urgency=low . * Fixed reverse vide rendering, #341. * Using stdout for version information, #344. * Added CGI session key in HTTP response. * Child process cleanup, #103. * Merged #340. * Autoconf updates. * Disabled utmp logging. * Merge #338, killing children with HUP. * Fixed handling of large HTTP requests. * Enhanced logging clarity with prefix. Checksums-Sha1: 3d0b1351d9da7b124ba06fd1c2ec07837fa879ad 1610 shellinabox_2.18.dsc 9b3ce5f1f0352104cf643ba41b63a7cd8562935d 664228 shellinabox_2.18.tar.xz c36a9eb9f2160fa7a3cf1a8a7f046c62ccda6dd5 122392 shellinabox_2.18_amd64.deb Checksums-Sha256: 01ca18256e482db6ae7a63d4484546a8820fb894a7bfd49f2d0c2a45fe3032de 1610 shellinabox_2.18.dsc 86302de089066da32f00730194b94a46d9fcb88f50f1b2f7485285134fa442c0 664228 shellinabox_2.18.tar.xz 5395de4f2efb39a931a83bafac2d88f00b5f6a8a24f2802218e8b2a5edff7311 122392 shellinabox_2.18_amd64.deb Files: 8b4d6bf17243efbbfbd629a4f9c3d608 1610 web optional shellinabox_2.18.dsc 7adbef53be730fed38635ce53aeec9a9 664228 web optional shellinabox_2.18.tar.xz e0239e79e92c68f90cabdaca46262473 122392 web optional shellinabox_2.18_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWGVjNAAoJEBrMEf59OSE80nUP/0Cl49vx8GrbINee1YqQlE9D CJ2IaSKfTuE6YBX59zFxu1b7Tp1ZHdZe6GkC4MofoFrfq5febtl2UK9+VY6q0+U8 h51Y/UWffxaFG+uPt8ad+B8y6khECIrZCC0+zMkddQAEthcSNbz1LuB4/CFv3gwI 0UjXbb6DljDphrbW4HF7MOyKSjUwI2NvMh+QTacxRD2MxYqieefMpIjXeFa4gn4x 5eIBXKwKY2UAFy2Exfu5JqqBMjcUS9X70wSZOTsP9hLQjKIePtVg2SYto5KQGOfD Nl37/tLNCFY/4iCKxklh7I9IeW1/b47VO02lIIy6eAE8V4e/5iDvqn5sUu/ii8wa r/uJSfOA5B0WJ9UHOCSvoJA6R/hCPLFEnHiaXi3LXmBPwOFOOcnivf/xTcC5alsZ 6zZT41MzaDlSkz7bKUSQmoRRq6k0FA9FCxYNUR3o7Qdyk3dSJw9NO1Jn0wWLz1ET TYLfPR2wEPJAEXgdE/gOyj+4niD8i5u9gWauApRvCimsNWiqoCm5dFFN0yyCtvWV FaDXc5xZdLPTMWspNk2SzKIMHiYbiSvjmT+nMdsk/Z5fZuqw0wrTbfbn8AD+Ld27 PDboo/9u07zye6It9inlDWvvzqnzhW4SkQIe0+WIjKEBjeKfxnq27kRTTkzz8Lq7 wwNz0pAxNcvf8q4vCr13 =qyWR -END PGP SIGNATURE-
Accepted shellinabox 2.17 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 07 Aug 2015 20:48:33 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.17 Distribution: unstable Urgency: medium Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: shellinabox - publish command line shell through AJAX interface Changes: shellinabox (2.17) unstable; urgency=medium . * Generally, SSL updates. * Disabling secure client-initiated renegotiation, an abused and unnecessary feature. * Added support for PFS using ECDHE. * Guarding build against old versions of SSL. Checksums-Sha1: 87110a25af287b27f86d9342f05f73314ab5e553 1610 shellinabox_2.17.dsc 363aeedb53178b02cf5e90225c4abb2bcbbf9b80 226056 shellinabox_2.17.tar.xz e70ecde923afb6f703737b022b6fb6f250011d35 121284 shellinabox_2.17_amd64.deb Checksums-Sha256: baa5112e0b80139c1b958085212a6e5596d8f45fa3081f048d2f5afb91989c3b 1610 shellinabox_2.17.dsc 06dbe781e069c222c39689581cb992796603f219bcb6b28a5201d13725d4b4e8 226056 shellinabox_2.17.tar.xz a217b231a8b98ea24c16d97521e7f5d9481266cc3f49a67f4e4faacd3fea1f40 121284 shellinabox_2.17_amd64.deb Files: 0576fc6ed78beb995cdea1d1840c0aaf 1610 web optional shellinabox_2.17.dsc ec0f8c0f9603d2de338c72804a347db5 226056 web optional shellinabox_2.17.tar.xz 16495658660d41a6099c0885e3af9597 121284 web optional shellinabox_2.17_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVxX2qAAoJEBrMEf59OSE8IkEP/29suLB1lcrwX01cjAgpFm6s R8LsVVA+MfrYPBpDQ0/SdW8uhGBAKM0rJ/isHt7dqNOKlgFpm3gxoH8G3yAn3QZ3 3W6aNkTnOzuqsZsFxE5ETl6v+6Aw8TiOrmuH/bv4JkL/wAN0M3ZmTnHA63yAeqAG oO6bMGKPCZmiPwn+URAsGPSXh4fkB6JxM66KDWpTKEpYvkFUl4R79jNxMCZ9kldi IN+UmJ9+fq5WNR/0div4pz1MfK9BviHD7JNmRM5rxEAL0SUeLvmu5En9xkQeVALy eoSreD8QRbauyZVetccHo6a5itMIMZBjzeDki/91ucAjhs/sNZR0cxBKL47iTmaz znXwB5tjCj1i2jkkhxATlxlO8fOJYmTxElQg4ug9X9d2Z61tlGcMW05nxhk2mVxk lVEbpMOmgAhBzWKf369aNJjKkTCXwqlWfpsE6f3DRh7W1ZMelByO1sX3vJMLiIk4 LCjjASfKxO/z0aLDNmKos9ufh+53ndS+zlRUyM0ICPcPiQAF7Ppr7G2Z+MnuLtpN qCXbOgj6IbHP1vBubCJdWiV953CXdNKAa9F3xErp4Ila8c+f/TrojG3fWgePn1Sr cZJzYNfGwjExtEUr7jkd9TfHg4UYuC8Rs2JBc5g8DAXd8xnligUtO2FsDVcTArz6 I/GsvAuO9RPpk/MgaAte =uN28 -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/e1znvmv-zv...@franck.debian.org
Accepted shellinabox 2.16 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Jul 2015 11:45:22 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.16 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: shellinabox - publish command line shell through AJAX interface Changes: shellinabox (2.16) unstable; urgency=low . * New release to guarantee upgrades for people who had installed a 2.15-1 release candidate. * Update to About dialog to use GitHub URLs. Checksums-Sha1: 06d095bf6a2c316d62b9f9f28962ab0390b2770e 1610 shellinabox_2.16.dsc 02eec7c8ea496c42c230876e74fcde3fe71fcfa3 225144 shellinabox_2.16.tar.xz 07c411f84380a01470f814b6a80102f66b9e673f 120836 shellinabox_2.16_amd64.deb Checksums-Sha256: 1947c68b7ed19a733640352f614da2307856120a04f16ae4026b06a15963a1b2 1610 shellinabox_2.16.dsc fa67a0ffb631257830a75121c2c31cea74c1b5f74cccb5290657ab4a39082c48 225144 shellinabox_2.16.tar.xz ebb0758d040384a29d1b4c513bb1e530cdbb3cb61f70730ed2a3993099ea87ad 120836 shellinabox_2.16_amd64.deb Files: 87776c90c910139dcfdf1f42e0bdde5e 1610 web optional shellinabox_2.16.dsc a5058a7647270bcc6e2acfb27a843832 225144 web optional shellinabox_2.16.tar.xz 5e536d8b7425499c9c53c043559bd39d 120836 web optional shellinabox_2.16_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVsosZAAoJEBrMEf59OSE8mJUP/AtOI9iyddxZtnJvkdH87FQ+ jaY/wqJjftEAI42GrZDepTNFEk7z4mwJO2+KZBTBec+qUJtn5lSimE7R7wCj35WA pM49zjpm+c8HIjr+ZO0SkGoJqDRamYmTSjBE4lLDM/nUxx79XfJ+b1Z1OKs1x70T /dwIg1fjZZJ8m7qWcOeGT5szZHJbPZiji4itJbKW/iLvG83UeQO+LaLWSdZSXXbk 325liUbcwcnkANLPGCHg39uW5tSz6MAdgCe/zJNKMAGpnckIPtvOg5RLvXusK/ft Jl83h2QZ6fWOh+BfX9dYDNVUwKqnJFSbPj5SqUN3oYU282yYHfTAhBwhKmCht7Lg 4KoRSUV+yXpr7tgpf4UzsYRi7W1fcWOUyWj/cs+LrFPdmn/Pl8CkaTeU8pwMOsM5 8y9trLCCeL2NTN4qujWwIU/4rA6PzR4qKRdVEVy4wAcpLAfRuwCvnbHOR2pBJAT6 m55YoGP141zg9Em2YZ5jmkSmnUkwiBl07EDOPrkUYXhy0KSCkandI8xDddvkH/NJ SD3f6MDmKRjUsRJecZ56MXZkuHGhPs5TCZXsV5aLiP2oGMX64AvuvQSlxgPmNZEm Q4sLCC7BDvw1shjSgixBAGHXYHnLoDOO6XO7sVaV/KNP56CM4nCzSUvW66cgz9tV 8yAkqCgCSKjamhx2dmsq =rrrV -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/e1ziixs-0001f6...@franck.debian.org
Accepted shellinabox 2.15 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Jul 2015 09:16:18 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.15 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: shellinabox - publish command line shell through AJAX interface Closes: 785181 786441 Changes: shellinabox (2.15) unstable; urgency=low . * Improved clean-liness so that source archive is clean. * First release from GitHub. (Closes: #785181) . [Contributions by Alexandre Detiste alexandre.deti...@gmail.com] * Bump std version to 3.9.6, no change needed * Bump debhelper compat to 9 * Move lintian exception in d/shellinabox.lintian * Change urls to new GitHub repos * Retain user preferences on upgrade (Closes: #786441) Checksums-Sha1: 207f75d662f01ff86bb6c455c2f4bbd2e62e3b55 1610 shellinabox_2.15.dsc ee7627f1ed838076b82869a9d0464ff24eea264d 225128 shellinabox_2.15.tar.xz 575f498fffbff311d13f6820bb815805f72e29c3 120660 shellinabox_2.15_amd64.deb Checksums-Sha256: 076d7a4469dbc2dac7c92e39eed0d8dddecc70f2db6bf1f4011e40495c4afe60 1610 shellinabox_2.15.dsc ec50f801fa438dc6ed33668575ea2e02be53da6fdd33fb4289939b60a1997ad4 225128 shellinabox_2.15.tar.xz 80370dd580cb9c3ed69a3b917c2a74110ac97a46d606311c2d786edebe714126 120660 shellinabox_2.15_amd64.deb Files: e43b3d9d14a42e32778a44a3492694d8 1610 web optional shellinabox_2.15.dsc d23efb51830c9d47eee262c644e8b4be 225128 web optional shellinabox_2.15.tar.xz a08eef6c281aab2e82ed52edc28ef8ad 120660 web optional shellinabox_2.15_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVsmc7AAoJEBrMEf59OSE8Ee0P/R58LkL0fBT7ogxagkSEYjcC zezMiM4fxYRTxe17SF9rvsFJhW/5G5qyhTwDI49gqH3uhoqjXKJYJGazl1+10b6L HHisRyOlWWtKVS1eJF9RTxIVzZ2O/wP1UWvfR6D9pgnmWvSMpAMUg4ISgwJZ4u6/ KiquxOm/QRnWtERI/B/c8BL5de+mLPNznYsXsd1W1+Ahyw2/6IIW3yHrP9yqFbvt 3KWkzOrh+oHMskUqvhSZhPqkVqW5IDtrxB0qGJpu5Z1ahlU2ELo+09qUhx0ZQGly 8y5X0kp9CEFt1Vn3umpVnAnK2TN3G4Umy7fW/cOBVjH+taqomL2z3v1tYQvM4uxI PHfXJuzG9CDW1pt5EtzQbhzMMPx4F8kFow6OjZtdq543MfyNrjbsLzovUWueSOww QJmaSxl3Hg4qp/l5HyLvTCj6EFFDejXR54nfXu4QeKhVmGs5Xy0G2f2tFdK9HPDl 69uOBiv/Xes2Kxqu6eu12E/mFnJwtmcaSeTK5Ui45awx6t748CSCwzbqHd7J/+V7 rTM3szRWWynozH0ud2hFQxM+Vz/KksVnhL2emiinlZokzY+fBgvSg92G3QJl14NK J3Rxvze3gxT4Q8m6ivjfbotfjO9DhsyV9nKYkLrbdKGM/KGTGlSFBFFNdDET/ole 97r66/hWEjHHh9w1fK0i =Hhdg -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/e1zigjq-0005z5...@franck.debian.org
Accepted shellinabox 2.14-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 21 Apr 2012 10:26:21 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.14-1 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: shellinabox - publish command line shell through AJAX interface Closes: 668720 Changes: shellinabox (2.14-1) unstable; urgency=low . * Revised install target of debian/rules. * Revised postrm and prerm to fix dangling symlinks on purge. (Closes: #668720.) Checksums-Sha1: f30b1d4d1a12dd31be5420fd4b5a221800476613 1247 shellinabox_2.14-1.dsc 9e01f58c68cb53211b83d0f02e676e0d50deb781 544919 shellinabox_2.14.orig.tar.gz 72a3624fba11967919bdf0886395c653fd26bc0e 6901 shellinabox_2.14-1.debian.tar.gz 4ceec7e59d3f620170e87cc173eed135bf831112 133916 shellinabox_2.14-1_amd64.deb Checksums-Sha256: 69d009d428cabfb5367e046a1184ac90035e6d647654871fad93de1562a6b18a 1247 shellinabox_2.14-1.dsc 4126eb7070869787c161102cc2781d24d1d50c8aef4e5a3e1b5446e65d691071 544919 shellinabox_2.14.orig.tar.gz ad192780e13fdf43e7f85e12a1c3b3d548128b0fca522541dd4a98cd0ba43c2c 6901 shellinabox_2.14-1.debian.tar.gz 441541039bbb557643c9dce416136263c695d2f8e7ffa8e239d51a20155bbc66 133916 shellinabox_2.14-1_amd64.deb Files: 1fff98d9d59beae1fc61ecf34426854b 1247 web optional shellinabox_2.14-1.dsc 6c63b52edcebc56ee73a108e7211d174 544919 web optional shellinabox_2.14.orig.tar.gz 05a175aea67a90d352ce567712c003a2 6901 web optional shellinabox_2.14-1.debian.tar.gz 9d8188c23a1cf0d66c81986934f4973d 133916 web optional shellinabox_2.14-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk+S7/sACgkQV+jOBy6uXS1KRwCfToI9XwMv5K8nP0kgw7WwTxeQ 0AQAn1EF+W+JQvqCUTKfd0Dh2h+pcbCi =MnPS -END PGP SIGNATURE- Accepted: shellinabox_2.14-1.debian.tar.gz to main/s/shellinabox/shellinabox_2.14-1.debian.tar.gz shellinabox_2.14-1.dsc to main/s/shellinabox/shellinabox_2.14-1.dsc shellinabox_2.14-1_amd64.deb to main/s/shellinabox/shellinabox_2.14-1_amd64.deb shellinabox_2.14.orig.tar.gz to main/s/shellinabox/shellinabox_2.14.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/e1slepu-0007sb...@franck.debian.org
Accepted shellinabox 2.13-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 09 Apr 2012 18:34:17 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.13-1 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: shellinabox - publish command line shell through AJAX interface Closes: 668130 Changes: shellinabox (2.13-1) unstable; urgency=low . * Typo in web address. (Closes: #668130.) * Removing PATH_MAX reference which should fix Hurd build. Checksums-Sha1: 287c2c4b11501b5587a9d7fa3fedb92aac6973cc 1202 shellinabox_2.13-1.dsc 54d9b1260936225b9026b15eab3d7bf4f992d627 543888 shellinabox_2.13.orig.tar.gz 8127644b5f78b9c1ab52d4d641188fc8dc3ab9a2 6776 shellinabox_2.13-1.debian.tar.gz 69fa9b8262e37c58af21ea96d099b86298ec1502 143700 shellinabox_2.13-1_amd64.deb Checksums-Sha256: d3af0b7922f3e66bf76d3c6e4ee79833250fa4b577cc6e35f94fe4f457259705 1202 shellinabox_2.13-1.dsc fc11670d1cb222f1cc55955630a6c8371b2ae1c8d22cc2543de17ba386a962a8 543888 shellinabox_2.13.orig.tar.gz 6f12abc658325b020b97edb621c79a87416e29d76a7399f53c3103204824ccd6 6776 shellinabox_2.13-1.debian.tar.gz 5096978e0392b65a78a1e887d56ab8b8e3e5df98d2815592d3a327820c9ebfc5 143700 shellinabox_2.13-1_amd64.deb Files: 0f17a4e7a13cb5b334ef5900d2c9ab3c 1202 web optional shellinabox_2.13-1.dsc fcfb216d1144756d352c5a9336c26cb3 543888 web optional shellinabox_2.13.orig.tar.gz 53a4e8cf6e9b56f829278d3bf90e28ec 6776 web optional shellinabox_2.13-1.debian.tar.gz 1e38d575ee3aaf70a70286ff39810f9c 143700 web optional shellinabox_2.13-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk+DmzwACgkQV+jOBy6uXS1ytwCfbbpBdUOg5TkV86b8kmR08d6k 3jkAnjHSsTYHAHzA+mhSZnr5gC9lqyAX =OGoe -END PGP SIGNATURE- Accepted: shellinabox_2.13-1.debian.tar.gz to main/s/shellinabox/shellinabox_2.13-1.debian.tar.gz shellinabox_2.13-1.dsc to main/s/shellinabox/shellinabox_2.13-1.dsc shellinabox_2.13-1_amd64.deb to main/s/shellinabox/shellinabox_2.13-1_amd64.deb shellinabox_2.13.orig.tar.gz to main/s/shellinabox/shellinabox_2.13.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/e1shra7-0001rm...@franck.debian.org
Accepted shellinabox 2.12-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 07 Apr 2012 15:39:11 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.12-1 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: shellinabox - publish command line shell through AJAX interface Closes: 667938 Changes: shellinabox (2.12-1) unstable; urgency=low . * Moved libssl from a dependency to a recommended package using a helper progam. Fixed typo in dependency to lsb-base. (Closes: #667938.) * Added support for runtime naming of the libssl so library. Checksums-Sha1: 0c167481fa0b03c296996cfdc3dc82007e948289 1201 shellinabox_2.12-1.dsc 45303001aa70b411b22bfaef4c8d3395fe797ab9 543463 shellinabox_2.12.orig.tar.gz c1ec9f0c74cc4067e4b86b7ca45597c51351475c 6637 shellinabox_2.12-1.debian.tar.gz 31feae48c72a6cd2408ba39ef434ec55fdae74d1 143336 shellinabox_2.12-1_amd64.deb Checksums-Sha256: fc05b5ab9ae3f034cc2e9a2acad2f5e95fd66e8136679ebc786db5e84f2282d6 1201 shellinabox_2.12-1.dsc 99c80ca4b356b60d04f79c4599d590b8a038de61b6f1e49bb81aaa759c1bb8ba 543463 shellinabox_2.12.orig.tar.gz a35fe703a08251be213e83d52cde9e6b50e447b184386be764a8040e3916372e 6637 shellinabox_2.12-1.debian.tar.gz 9cb360d4b005f992e8a046a3a234e59a11e614c27a22291d456ec33d0b2e7981 143336 shellinabox_2.12-1_amd64.deb Files: 30031f64f802afc310525b8871fc8138 1201 web optional shellinabox_2.12-1.dsc f2032053cc21dfb12fc7f67c4a266598 543463 web optional shellinabox_2.12.orig.tar.gz 8125baf9a485411fdc80ef1481bb78fb 6637 web optional shellinabox_2.12-1.debian.tar.gz 46c0567056c0c396bf5a978d93b87ef1 143336 web optional shellinabox_2.12-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk+AygoACgkQV+jOBy6uXS0aPQCfdnK8UEBT1Pz/DHtjXxAiT1Ga +MoAnR9ZoChBVBivYaookpgMoktFvvAN =JjZm -END PGP SIGNATURE- Accepted: shellinabox_2.12-1.debian.tar.gz to main/s/shellinabox/shellinabox_2.12-1.debian.tar.gz shellinabox_2.12-1.dsc to main/s/shellinabox/shellinabox_2.12-1.dsc shellinabox_2.12-1_amd64.deb to main/s/shellinabox/shellinabox_2.12-1_amd64.deb shellinabox_2.12.orig.tar.gz to main/s/shellinabox/shellinabox_2.12.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/e1sgex1-0001gn...@franck.debian.org
Accepted shellinabox 2.11-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 05 Apr 2012 20:53:32 -0700 Source: shellinabox Binary: shellinabox Architecture: source amd64 Version: 2.11-1 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: shellinabox - publish command line shell through AJAX interface Closes: 535905 Changes: shellinabox (2.11-1) unstable; urgency=low . * First release into archive. (Closes: #535905.) * Applied patches from the issues database. * Rolled major revision so that the tarball is complete. Checksums-Sha1: d6753fc8578b33e6990f87c6379afbfbe7d8827f 1201 shellinabox_2.11-1.dsc 05bb361685607a9ef11dfbc60aa733eea16b7ed3 542818 shellinabox_2.11.orig.tar.gz 951f6e32f75b5c595cc2fb04bd6348de3e098b3b 6104 shellinabox_2.11-1.debian.tar.gz 1964e513b99f81afef3a125f962fba6f694e4f46 142990 shellinabox_2.11-1_amd64.deb Checksums-Sha256: 0b8e20bca83c9eb48a8279d043a61b6a20a142640b4e8cefee9c545d87b2ff6e 1201 shellinabox_2.11-1.dsc 8aa4be08d1fba67998d0628a5d9ae725471f5460c1a8c5a136350db38cb80667 542818 shellinabox_2.11.orig.tar.gz ddf32f762ade30ef98ae3cbbb9c5bd9ce413287ddc1b6e928531160faf65d8d5 6104 shellinabox_2.11-1.debian.tar.gz c4f5962e03e891f8a9bd76c474defcb86318b190e4a1065cab4be65ba5a14133 142990 shellinabox_2.11-1_amd64.deb Files: 7b9d81c0516006290235f5376b7a8a5a 1201 web optional shellinabox_2.11-1.dsc 962f21830ccb70a5fd62e2112cf93f3b 542818 web optional shellinabox_2.11.orig.tar.gz 549123dd8a893ef85d92626181d505c1 6104 web optional shellinabox_2.11-1.debian.tar.gz d364c4241ace292d85ca9721e5607244 142990 web optional shellinabox_2.11-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk9+a1oACgkQV+jOBy6uXS3b/QCeI9JHsCwYSYlV5EgZq/l1DX9w nBIAnj5O/y7lqFb7DJI2vtgAdYE75f06 =iHxP -END PGP SIGNATURE- Accepted: shellinabox_2.11-1.debian.tar.gz to main/s/shellinabox/shellinabox_2.11-1.debian.tar.gz shellinabox_2.11-1.dsc to main/s/shellinabox/shellinabox_2.11-1.dsc shellinabox_2.11-1_amd64.deb to main/s/shellinabox/shellinabox_2.11-1_amd64.deb shellinabox_2.11.orig.tar.gz to main/s/shellinabox/shellinabox_2.11.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/e1sgeui-0007iq...@franck.debian.org
Accepted buici-clock 0.4.9.1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 25 Jul 2011 11:29:38 + Source: buici-clock Binary: buici-clock Architecture: source amd64 Version: 0.4.9.1 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: buici-clock - attractive desktop clock Closes: 634730 635240 Changes: buici-clock (0.4.9.1) unstable; urgency=low . * Reordered link line for libxo.a s.t. libraries succeed objects. (Closes: # 634730) * Upgraded debian rules and compatibility. * Removed libSM and libICE from link as no symbols from libraries were used. Also removed from build dependencies. * Restored support for complete source archive on upload. (Closes: #635240) Checksums-Sha1: 92a1b5bda577b5a61ab094143e119491a18af4d8 757 buici-clock_0.4.9.1.dsc 86b907ea82518513496da81b4e650138acaad4fd 167077 buici-clock_0.4.9.1.tar.gz cef0dd6e326710d1f20d805f376a265ee224ed02 32868 buici-clock_0.4.9.1_amd64.deb Checksums-Sha256: b12e08296a54eb09ce85ef775c38b833b04f17a6aace5ec5412af2f86bfb5706 757 buici-clock_0.4.9.1.dsc 3c5cea3b79e96effc9cc25c4feda116b426fde571a066c26a92c2633d68c8951 167077 buici-clock_0.4.9.1.tar.gz 9bc30981d31660ab42e89a2fef909e0910b952a89a238fe1f64f60a8a9bd97d1 32868 buici-clock_0.4.9.1_amd64.deb Files: 27cf31536d1a37f41c8298a7f509f6b6 757 x11 optional buici-clock_0.4.9.1.dsc 0964f1e5a5badca9f0089aa549c1663a 167077 x11 optional buici-clock_0.4.9.1.tar.gz a50d93b70da88e1038d0672898086dd6 32868 x11 optional buici-clock_0.4.9.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk4tXWkACgkQV+jOBy6uXS3L7wCdGgllWSL52UQTMSkZt4lgYkVW iE8AoIpSwK5yzeOO+iYDzsWDCI/iWioz =DHf/ -END PGP SIGNATURE- Accepted: buici-clock_0.4.9.1.dsc to main/b/buici-clock/buici-clock_0.4.9.1.dsc buici-clock_0.4.9.1.tar.gz to main/b/buici-clock/buici-clock_0.4.9.1.tar.gz buici-clock_0.4.9.1_amd64.deb to main/b/buici-clock/buici-clock_0.4.9.1_amd64.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/e1qlk5s-00071g...@franck.debian.org
Accepted buici-clock 0.4.9.2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 25 Jul 2011 19:38:19 + Source: buici-clock Binary: buici-clock Architecture: source amd64 Version: 0.4.9.2 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: buici-clock - attractive desktop clock Closes: 392675 392821 496094 Changes: buici-clock (0.4.9.2) unstable; urgency=low . * Added pkg-config and libcairo to build dependencies. Unclear how it ever built at all. * Changed menu to conform to recommended section for clocks. (Closes: #496094) * Verified that these NMUs are either incorporated or adequately covered by other changes to the package. (Closes: #392675, #392821) Checksums-Sha1: d36c6c4ebc67091fcf4294f7174af9e2c051efac 784 buici-clock_0.4.9.2.dsc 56689d3789a0e07ac46eec81fde963d76f496845 167987 buici-clock_0.4.9.2.tar.gz e667003a8a89bcb577e0c5549b13f42779cdb6a8 33058 buici-clock_0.4.9.2_amd64.deb Checksums-Sha256: 9e54aa310fecb506a27e6152ed60acfc3e6f5a1f19563a12e2dcf961d82fe0a4 784 buici-clock_0.4.9.2.dsc 06b33420128b5ebfa4063dae0a998527c24a912aefdd69f3e9f8442b7d3a751d 167987 buici-clock_0.4.9.2.tar.gz 1837b176f776a3cc67ae5cf699b57f15f818f3a9bc2921fa7ecb93c6df09e2be 33058 buici-clock_0.4.9.2_amd64.deb Files: a09394e5384c71f9ac72978a201cf9ac 784 x11 optional buici-clock_0.4.9.2.dsc b79536b2b3695b829fde7291fdaf156b 167987 x11 optional buici-clock_0.4.9.2.tar.gz ce926c9d1684dd3d0d4974c446bd4a1b 33058 x11 optional buici-clock_0.4.9.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk4tyjMACgkQV+jOBy6uXS1PkACeKsVEy51DNcJ3Gv9NkEppxikc azYAnj0f6mMyx+l7Bkk/QPt+Zn97FguG =wWKu -END PGP SIGNATURE- Accepted: buici-clock_0.4.9.2.dsc to main/b/buici-clock/buici-clock_0.4.9.2.dsc buici-clock_0.4.9.2.tar.gz to main/b/buici-clock/buici-clock_0.4.9.2.tar.gz buici-clock_0.4.9.2_amd64.deb to main/b/buici-clock/buici-clock_0.4.9.2_amd64.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/e1qls3t-0002ke...@franck.debian.org
Accepted buici-clock 0.4.9 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 24 Jul 2011 00:54:34 + Source: buici-clock Binary: buici-clock Architecture: source amd64 Version: 0.4.9 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: buici-clock - attractive desktop clock Closes: 634730 Changes: buici-clock (0.4.9) unstable; urgency=low . * Reordered link line for libxo.a s.t. libraries succeed objects. (Closes: # 634730) * Upgraded debian rules and compatibility. * Removed libSM and libICE from link as no symbols from libraries were used. Also removed from build dependencies. Checksums-Sha1: 002e1d52edd73bd07e18b9ed69d0984b6bc4c204 749 buici-clock_0.4.9.dsc 0d7015f9c2ea60679297644c59d400cbc1e32fcb 322063 buici-clock_0.4.9.tar.gz b3f93c1a443f1523ce013542292aa03a963019e2 30932 buici-clock_0.4.9_amd64.deb Checksums-Sha256: 5b8dfe27907d9ace2b8c220c9a9f8b9d06bee1f7d0b5c92cc2d157001db55254 749 buici-clock_0.4.9.dsc e0f416f9b899801e293a0496ddfdb97a10e3c3936aa94b91f150b3887f50c980 322063 buici-clock_0.4.9.tar.gz 531e513c9ac529c54476ffd04919732053d6bb8fdb23920dd644141d6f2cc92e 30932 buici-clock_0.4.9_amd64.deb Files: d3b4621e0b0a743219dc8738b30487ef 749 x11 optional buici-clock_0.4.9.dsc 1588181f75bbdff4894b8653dd5b5b5d 322063 x11 optional buici-clock_0.4.9.tar.gz 7e99c79cc7976e3ac88cdb54e514690b 30932 x11 optional buici-clock_0.4.9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk4rpWwACgkQV+jOBy6uXS3IzACgklvvzD/rDDF8bq/4ax/eHTTv LSMAnR26M5p6bV3qmjCll9kkANZR7u46 =JnBa -END PGP SIGNATURE- Accepted: buici-clock_0.4.9.dsc to main/b/buici-clock/buici-clock_0.4.9.dsc buici-clock_0.4.9.tar.gz to main/b/buici-clock/buici-clock_0.4.9.tar.gz buici-clock_0.4.9_amd64.deb to main/b/buici-clock/buici-clock_0.4.9_amd64.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/e1qkqpm-fp...@franck.debian.org
Accepted uphpmvault 0.8 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 03 Jul 2011 11:02:58 -0700 Source: uphpmvault Binary: uphpmvault Architecture: source amd64 Version: 0.8 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: uphpmvault - upload recovery images to HP MediaVault2 via Ethernet Closes: 632569 Changes: uphpmvault (0.8) unstable; urgency=low . * Added stddef.h s.t. offsetof macro is available. Required by GCC 4.6. (closes: bug#632569) Checksums-Sha1: 28e58b77cbcad9b3668a6a2a99fbc2a8e35d8b81 742 uphpmvault_0.8.dsc 1b9a5245656cdbb321f3730bafdb189df061833e 12 uphpmvault_0.8.tar.gz 1aa535b6010dd539cd43d47663f4416d055bd790 10492 uphpmvault_0.8_amd64.deb Checksums-Sha256: 802675c3367207d47d761c3b015f14f171eabad96c6a0dd51660c66c30b0ae3f 742 uphpmvault_0.8.dsc 4c007430fe1e461b86a425e2efb9e90770ce00d672543419603b782471908a79 12 uphpmvault_0.8.tar.gz 8f968e36a544a3915b30f48ab5b94165e0340b129db8faba026b9574abc874c9 10492 uphpmvault_0.8_amd64.deb Files: 599ec1419fcc1d126c2cfe0efd6d78a0 742 utils optional uphpmvault_0.8.dsc 1d34008105e4508917b1024bca4e180a 12 utils optional uphpmvault_0.8.tar.gz f49e896312e6899adbd133e50621c182 10492 utils optional uphpmvault_0.8_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk4Qr10ACgkQV+jOBy6uXS3NjACgkLv39kfQLyLGsxsmYd6MWHQ3 VVIAnjzYzmbccer/ynl1nF7HSDbzQlvP =Jnxv -END PGP SIGNATURE- Accepted: uphpmvault_0.8.dsc to main/u/uphpmvault/uphpmvault_0.8.dsc uphpmvault_0.8.tar.gz to main/u/uphpmvault/uphpmvault_0.8.tar.gz uphpmvault_0.8_amd64.deb to main/u/uphpmvault/uphpmvault_0.8_amd64.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/e1qdrfo-0001zm...@franck.debian.org
Accepted uphpmvault 0.6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 02 May 2011 10:12:31 -0700 Source: uphpmvault Binary: uphpmvault Architecture: source i386 Version: 0.6 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: uphpmvault - upload recovery images to HP MediaVault2 via Ethernet Closes: 624912 Changes: uphpmvault (0.6) unstable; urgency=low . * GCC 4.6 changes (exposes) a missing prototype for ::fstat. Including the proscribed headers solves issue. (closes: bug#624912) * Fixed type-pun warnings. * Fixed sizeof in printf warning exposed on 64 bit host. Checksums-Sha1: 95430b91cadc94782f383c5b2ece32638a17bcd6 739 uphpmvault_0.6.dsc 7419377115c3e33de4403bf090ea240f31746f02 90008 uphpmvault_0.6.tar.gz d370c43b0a7c3127f69219936a22631bac7668a1 9914 uphpmvault_0.6_i386.deb Checksums-Sha256: 1a4721859d7eca2a51ff5574aa4152bb206cc4d30d83ee2d9d776f4c6b22a1cb 739 uphpmvault_0.6.dsc f0865972e9ab5e904d1087e60acf69556c2200c01068e54f677b0a6b226fd604 90008 uphpmvault_0.6.tar.gz 4e573502e2124263c64269e64fd93730cff63ac900e15e5c7938721afaa3a46f 9914 uphpmvault_0.6_i386.deb Files: bfe1a42fa2451fff9f63f7b765a7f72d 739 utils optional uphpmvault_0.6.dsc 380346d493f5551fef0e03f1c0d6a9d3 90008 utils optional uphpmvault_0.6.tar.gz 3903d3c0d1890b11782a1a498f5887c0 9914 utils optional uphpmvault_0.6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk2+5vYACgkQV+jOBy6uXS3C6ACfRrBoOmf7MUFTnM9R21Fy5sjv QtMAnA4ZWbwKf1fxdUW0idQJkGDBCE11 =Ppde -END PGP SIGNATURE- Accepted: uphpmvault_0.6.dsc to main/u/uphpmvault/uphpmvault_0.6.dsc uphpmvault_0.6.tar.gz to main/u/uphpmvault/uphpmvault_0.6.tar.gz uphpmvault_0.6_i386.deb to main/u/uphpmvault/uphpmvault_0.6_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/e1qgwyd-js...@franck.debian.org
Accepted uphpmvault 0.7 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 02 May 2011 10:31:16 -0700 Source: uphpmvault Binary: uphpmvault Architecture: source i386 Version: 0.7 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: uphpmvault - upload recovery images to HP MediaVault2 via Ethernet Changes: uphpmvault (0.7) unstable; urgency=low . * Releasing a second time to remove git control files from source archive. Checksums-Sha1: a3767c058afc1fa8eb33127fab05de3092726833 739 uphpmvault_0.7.dsc fae7dde33e2e6f9b1511abd04ac5715e0bcc3225 15632 uphpmvault_0.7.tar.gz ca882c91c47fc4f6a1d9c27c37e400d90e53a6e7 9982 uphpmvault_0.7_i386.deb Checksums-Sha256: 82d664dab851b774a20d34fa065f1a2c9bd694067b1771f833d37d1857055ddc 739 uphpmvault_0.7.dsc 2b584c77106e15ac21a90932a3ae9df934bfcc814783ede967e2e68c067873e5 15632 uphpmvault_0.7.tar.gz 85b9c2cad3252da06ec9325c71768da0f9ab92c021deecfcf6d5f83667439572 9982 uphpmvault_0.7_i386.deb Files: ef9e72daf270c892f2f79c657dc7762d 739 utils optional uphpmvault_0.7.dsc 2662cb8254459ae029cb0a7963f4ac24 15632 utils optional uphpmvault_0.7.tar.gz a76921552091b252337d462479fa374f 9982 utils optional uphpmvault_0.7_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk2+6o0ACgkQV+jOBy6uXS34IgCghhOCC1GMMFMUitg+bL2DbgRD zf0AoINAuqH5V1DWsLyXdAFtq8poNinC =zxiR -END PGP SIGNATURE- Accepted: uphpmvault_0.7.dsc to main/u/uphpmvault/uphpmvault_0.7.dsc uphpmvault_0.7.tar.gz to main/u/uphpmvault/uphpmvault_0.7.tar.gz uphpmvault_0.7_i386.deb to main/u/uphpmvault/uphpmvault_0.7_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/e1qgxee-0002gq...@franck.debian.org
Accepted apex 1.6.10 (source armel)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 06 Oct 2009 18:45:07 -0700 Source: apex Binary: apex-nslu2 Architecture: source armel Version: 1.6.10 Distribution: unstable Urgency: critical Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@debian.org Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Closes: 548236 Changes: apex (1.6.10) unstable; urgency=critical . * Change to usr/flash-apex to work-around change in shell that could cause script to fail. (Closes: #548236). Checksums-Sha1: ff2cfbb5493fe875f942d41c00b490885b514652 706 apex_1.6.10.dsc bcd8f50206e2951ca4a679da72ac0fc5856466ba 5862664 apex_1.6.10.tar.gz 44faff993b21a0f1c0ad6cde6a6af92e487a6e1a 84696 apex-nslu2_1.6.10_armel.deb Checksums-Sha256: 3a526d4f76e8def700842a276a5f69ad3150a16bb18148ff5afa7fd37fce4657 706 apex_1.6.10.dsc 6d28d1863f2b3d3420aab2d06995af1356b83dc1b425e7dba5d7138daedbf58f 5862664 apex_1.6.10.tar.gz a433f84159d93f268ba4407dbff79f143c7e5805b37d8607b4f96a09a8a3297d 84696 apex-nslu2_1.6.10_armel.deb Files: 2e951120c37b41557170c05ffc1ba393 706 admin optional apex_1.6.10.dsc 06b9ffbed39c07600138d3ed8757df93 5862664 admin optional apex_1.6.10.tar.gz 53aaa3b5260b411006a15fa6fba2086d 84696 admin optional apex-nslu2_1.6.10_armel.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkrMhFsACgkQV+jOBy6uXS3ZjwCZAYBX8rr/eyntX6T436+aTyA+ kx0AnAw+feyTxClRF7miJvur8R9UkHFm =hebe -END PGP SIGNATURE- Accepted: apex-nslu2_1.6.10_armel.deb to pool/main/a/apex/apex-nslu2_1.6.10_armel.deb apex_1.6.10.dsc to pool/main/a/apex/apex_1.6.10.dsc apex_1.6.10.tar.gz to pool/main/a/apex/apex_1.6.10.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 apex 1.6.9 (source armel)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 17 May 2009 18:10:37 -0700 Source: apex Binary: apex-nslu2 Architecture: source armel Version: 1.6.9 Distribution: unstable Urgency: low Maintainer: Marc Singer e...@debian.org Changed-By: Marc Singer e...@buici.com Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Closes: 417757 471476 481736 481843 481846 481848 Changes: apex (1.6.9) unstable; urgency=low . * Including some entries from previous changlog to make sure bugs get closed. * Added CONFIG_AEABI=y to armel (and all configurations). (closes: #481848) * Added shlib dependencies for the sake of apex-env. (closes: #481846) * Revised copyright messages, again, to remove all references to the FSF address. * Removed FSF info from every file and point to debian/copyright file instead. (closes: #481843) (closes: #481736) * Removed rtc-x1205.probe=0,0x6f and rtc-pcf8563.probe=0,0x51 from kernel command lines. (closes: #471476) * Removed warnings is usr/ tools build. * The --force option to apex-env was fixed in a previous release. (closes: #417757) Checksums-Sha1: 17cbde2892cf3376659d8038879975febdec95dc 694 apex_1.6.9.dsc 637117d3ac30168281f36879d20bf67d556319de 5688842 apex_1.6.9.tar.gz ef3792d8c98b4beb1dee393bf646f8385287a301 84328 apex-nslu2_1.6.9_armel.deb Checksums-Sha256: 711c94f340ca40e61aaac347878e9516e2940879f966def93c8c46ad232947d6 694 apex_1.6.9.dsc 3bacc156f667c198b67042d07cdc1ed823d52e1ac71c28f7a417e3a5ef68e496 5688842 apex_1.6.9.tar.gz 64c005618cf30eb6fef1aa303b6140e4a8b8e6168627ad1454db4b7d539bb4a2 84328 apex-nslu2_1.6.9_armel.deb Files: 6810758b749dd7483b0425acddca64f6 694 admin optional apex_1.6.9.dsc 0ffa1509c48b2b85768b4b64e659bc88 5688842 admin optional apex_1.6.9.tar.gz 0e4ff6b36dcc8fdae58587b969000c39 84328 admin optional apex-nslu2_1.6.9_armel.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFKEZHOV+jOBy6uXS0RAkcnAKCHVJJ0WRzl+wjBn3uO7qVaWuz+lgCfRqVz mkAazi9pp+hOlnQ3cd4u2wo= =Wdgq -END PGP SIGNATURE- Accepted: apex-nslu2_1.6.9_armel.deb to pool/main/a/apex/apex-nslu2_1.6.9_armel.deb apex_1.6.9.dsc to pool/main/a/apex/apex_1.6.9.dsc apex_1.6.9.tar.gz to pool/main/a/apex/apex_1.6.9.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#515793: ITP: CGIT -- C-code Web Front-end to GIT
On Wed, Feb 18, 2009 at 06:50:55AM +, Iulian Udrea wrote: 2009/2/18 Marc Singer e...@buici.com Is your package patch available so I can review it? Also, it doesn't look like you're a DD. Why are you so keen to maintain it? Yes, you're right, I'm not a DD. Anyway, I've had no idea that you're a DD. That being said, perhaps it's better to submit wnpp bugs using your d.o address? Sorry about that. My debian address is the same, e...@debian.org. On the other hand, please ignore my intention to maintain this. I'm sorry for this. It was not my intention to shut you down. I am just trying to figure out how far you've gotten in packaging the program. There is a serious blockage in pushing cgit into the archive because libgit.a isn't available from git-core. I've been chatting with the git-core maintainer to see if there will be a change in this. Cheers Iulian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#515793: ITP: CGIT -- C-code Web Front-end to GIT
On Wed, Feb 18, 2009 at 05:47:57PM +, Iulian Udrea wrote: 2009/2/18 Marc Singer e...@buici.com It was not my intention to shut you down. I am just trying to figure out how far you've gotten in packaging the program. Sure, no problem. I haven't gotten too far in packaging it because of bug #407722. I've also been encouraging the author to rethink the configuration of cgit to be more similar to gitweb. It's not a show stopped, but it would make cgit easier to integrate. There is a serious blockage in pushing cgit into the archive because libgit.a isn't available from git-core. I've been chatting with the git-core maintainer to see if there will be a change in this. Indeed, unfortunately, this is one of the reasons why I stopped working on packaging it for now. As far as I can see, you're already talking to Gerrit regarding libgit.a. Perhaps we will find a way to get it back. I'm going to put my package, so far, into git on alioth, in the mean time. If I have some time, I'll ping the git list as well. Cheers. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515793: ITP: CGIT -- C-code Web Front-end to GIT
Package: wnpp Severity: wishlist The upstream build of cgit requires a download of git to build libgit which this package links statically. Thus, this package practically depends on a change to git-core. http://hjemli.net/git/cgit/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#515793: ITP: CGIT -- C-code Web Front-end to GIT
On Tue, Feb 17, 2009 at 06:30:58PM +, Iulian Udrea wrote: Hello Marc. I have already packaged this. I was going to submit an ITP and upload it through a sponsor in the next days. So, I would like to take care of this. May I take over this ITP? Is your package patch available so I can review it? Also, it doesn't look like you're a DD. Why are you so keen to maintain it? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted uphpmvault 0.5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 04 Jul 2008 14:39:30 -0700 Source: uphpmvault Binary: uphpmvault Architecture: source i386 Version: 0.5 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: uphpmvault - upload recovery images to HP MediaVault2 via Ethernet Changes: uphpmvault (0.5) unstable; urgency=low . * Added 'install' target to Makefile. Package not much good without it. * Added man page. Files: 905972a595d5cb3647182fab112bbcc0 530 utils optional uphpmvault_0.5.dsc cd51fdb7f364d94455cccaa38a79cac7 15264 utils optional uphpmvault_0.5.tar.gz 33f3b50e530551ca901164ee771c5ee4 9524 utils optional uphpmvault_0.5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIbuLmV+jOBy6uXS0RAhF3AJ9qGYzyQWOOdXECowfypxzqxMkVKgCfaqgX t2iEuOFB3kdIbQV+wrYPfeM= =rsRq -END PGP SIGNATURE- Accepted: uphpmvault_0.5.dsc to pool/main/u/uphpmvault/uphpmvault_0.5.dsc uphpmvault_0.5.tar.gz to pool/main/u/uphpmvault/uphpmvault_0.5.tar.gz uphpmvault_0.5_i386.deb to pool/main/u/uphpmvault/uphpmvault_0.5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ixp4xx-microcode 2.4-5 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 03 Jun 2008 16:21:22 -0700 Source: ixp4xx-microcode Binary: ixp4xx-microcode Architecture: source arm Version: 2.4-5 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: ixp4xx-microcode - Binary microcode for the IXP4xx ethernet Changes: ixp4xx-microcode (2.4-5) unstable; urgency=low . * Re-upload to preserve the orig.tar.gz/diff type of package that it is. Checksums-Sha1: 4927869533b7f241c3b2db133125977c33151f40 1096 ixp4xx-microcode_2.4-5.dsc 585900548b1c9daa28c3f2a34694d121bc46a0d7 2595 ixp4xx-microcode_2.4-5.diff.gz 894980e7a1d710882655203a075136cd1d07e419 8814 ixp4xx-microcode_2.4-5_arm.deb Checksums-Sha256: a14c17daa6262056517b5706301b7088ecb998bbec3d2a444b40c1e9443e6673 1096 ixp4xx-microcode_2.4-5.dsc 84dfe31533c523d45962760099a7848e410501eb25002fca7d782676f62621be 2595 ixp4xx-microcode_2.4-5.diff.gz 2389011227d46e2f9e5cbf5eeae98f6d94c689aabdcc0c6d8b1dee9ff42f8d9c 8814 ixp4xx-microcode_2.4-5_arm.deb Files: e13f8736e86e373dd8793431a1c5a2f0 1096 non-free/admin extra ixp4xx-microcode_2.4-5.dsc 5ad5314cd7762470ccb74574e7ff6572 2595 non-free/admin extra ixp4xx-microcode_2.4-5.diff.gz a060a1e6ed7a99f131ece5be0334da69 8814 non-free/admin extra ixp4xx-microcode_2.4-5_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIRgH8V+jOBy6uXS0RAmfAAJwJLr8s7ohcpFviXIfULV2GYWbzTwCbB+cY dZINx/SMYZhw+7JFXtpOjjE= =hQv1 -END PGP SIGNATURE- Accepted: ixp4xx-microcode_2.4-5.diff.gz to pool/non-free/i/ixp4xx-microcode/ixp4xx-microcode_2.4-5.diff.gz ixp4xx-microcode_2.4-5.dsc to pool/non-free/i/ixp4xx-microcode/ixp4xx-microcode_2.4-5.dsc ixp4xx-microcode_2.4-5_arm.deb to pool/non-free/i/ixp4xx-microcode/ixp4xx-microcode_2.4-5_arm.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted uboot-mkimage 0.4 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 03 Jun 2008 20:48:17 -0700 Source: uboot-mkimage Binary: uboot-mkimage Architecture: source arm Version: 0.4 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: uboot-mkimage - generate kernel image for U-Boot Changes: uboot-mkimage (0.4) unstable; urgency=low . * Adoption by Marc Singer. Checksums-Sha1: 6b03a33b6a522d70a3ce68756b16251cd94a2636 760 uboot-mkimage_0.4.dsc 4bc80f08e2e8f7db0965d8018fc0385dd7fa2df1 12630 uboot-mkimage_0.4.tar.gz 4a845c0c77d4abfa4c7edf599807bf2685c0fba9 9996 uboot-mkimage_0.4_arm.deb Checksums-Sha256: f13e6ee5cc98c88613bcbeab4a93eff1c8ba4ae1c24aa8a46f8068022c3bfa04 760 uboot-mkimage_0.4.dsc b44dd73b1fc14e4bbd49b7944603a2254a87f0e2ad9c8ad91b00111849c95420 12630 uboot-mkimage_0.4.tar.gz b6ec9f4ba328b8c8d39954191e79e56d0ae7a5690e37a9d4a96221070693d37c 9996 uboot-mkimage_0.4_arm.deb Files: 13c1406058b77baf7ce56a2d969c1c5d 760 utils optional uboot-mkimage_0.4.dsc 6ff36897a50c7fcd26bc088dc52841c8 12630 utils optional uboot-mkimage_0.4.tar.gz 6ea568fd6e085cc5bfc11d41e0c12b40 9996 utils optional uboot-mkimage_0.4_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIRhU+V+jOBy6uXS0RAhzhAJ97zQvgYH/plH1MWapaCZMbPssemgCfbVmi nECjgL9VaBhgIAIXWom8QNs= =6ILs -END PGP SIGNATURE- Accepted: uboot-mkimage_0.4.dsc to pool/main/u/uboot-mkimage/uboot-mkimage_0.4.dsc uboot-mkimage_0.4.tar.gz to pool/main/u/uboot-mkimage/uboot-mkimage_0.4.tar.gz uboot-mkimage_0.4_arm.deb to pool/main/u/uboot-mkimage/uboot-mkimage_0.4_arm.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted ixp4xx-microcode 2.4-4 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 02 Jun 2008 12:01:41 -0700 Source: ixp4xx-microcode Binary: ixp4xx-microcode Architecture: source arm Version: 2.4-4 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: ixp4xx-microcode - Binary microcode for the IXP4xx ethernet Changes: ixp4xx-microcode (2.4-4) unstable; urgency=low . * Adopted by Marc Singer. Checksums-Sha1: 45e6ac6bed2fb9ad4d97a3010cc410a7cb3d9d4d 837 ixp4xx-microcode_2.4-4.dsc cfc4921d86cb613ef14d8eb184a8ab5c053ca158 185015 ixp4xx-microcode_2.4-4.tar.gz 06380be079b83ec59e925a619cb63651ab3c5a8a 8750 ixp4xx-microcode_2.4-4_arm.deb Checksums-Sha256: 6f8a1171ab3c0a881af46971897d613a4857947a48bb7e744a3d720ddf898275 837 ixp4xx-microcode_2.4-4.dsc b6f803d83f3f1b15f145d6d35a348ae7deca27c302827ad7e464554fbfd8568d 185015 ixp4xx-microcode_2.4-4.tar.gz fc8a9d20973a4dc0a60c3d73f41382dfcbb712b0af414415c8c5750e69fef4a7 8750 ixp4xx-microcode_2.4-4_arm.deb Files: 64e0016c7e62f176fbf39c6612f97143 837 non-free/admin extra ixp4xx-microcode_2.4-4.dsc c45b09777cab8f4d274c9d078a347f2c 185015 non-free/admin extra ixp4xx-microcode_2.4-4.tar.gz 2b55e947f9fbdc89fe433c9b9f686fe7 8750 non-free/admin extra ixp4xx-microcode_2.4-4_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIRKRHV+jOBy6uXS0RAt8CAJ9J4ieAsR3Z+icIUvn5RbuvzT+gSQCgkMQo +49UZOi6zGvpg2cWK9HpMx4= =JKaV -END PGP SIGNATURE- Accepted: ixp4xx-microcode_2.4-4.dsc to pool/non-free/i/ixp4xx-microcode/ixp4xx-microcode_2.4-4.dsc ixp4xx-microcode_2.4-4.tar.gz to pool/non-free/i/ixp4xx-microcode/ixp4xx-microcode_2.4-4.tar.gz ixp4xx-microcode_2.4-4_arm.deb to pool/non-free/i/ixp4xx-microcode/ixp4xx-microcode_2.4-4_arm.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.15.2 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 20 May 2008 20:34:48 -0700 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.15.2 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Closes: 482000 Changes: apex (1.4.15.2) unstable; urgency=low . * debian/postinst: Fixed the postinst script to only run on the NSLU2. (closes: #482000) * Makefile: Fixed the construction of the version when there is an EXTRAVERSION. Checksums-Sha1: 533f88b9fe30c5e41efc7599bae103726c9d2fa9 703 apex_1.4.15.2.dsc bad32d0f9be0150645ec71c9f760fd9eae98eddc 997734 apex_1.4.15.2.tar.gz dd12d838b7fea2f7ae6c87c217724b97e1677b91 54874 apex-nslu2_1.4.15.2_arm.deb Checksums-Sha256: 65bb20b3fc850ce2f3899536a22276bd88dce52072d5a85349d3a3008e20928e 703 apex_1.4.15.2.dsc 3cc87d46e6742efae9f7bf9dcae55bd6f83140f84ee7a04b9ea99683be3cff7d 997734 apex_1.4.15.2.tar.gz 57b5f39120644ee8808ee93cf3f46137e7b80d1c3fe59485e89815b194e44c37 54874 apex-nslu2_1.4.15.2_arm.deb Files: 9831bb12d80044dcd9d3755d8baad0ee 703 admin optional apex_1.4.15.2.dsc 5a7c0b772a52fa3ba3d16f32d31f2c3f 997734 admin optional apex_1.4.15.2.tar.gz 51daeee6e11e3179064dc6c9fd1fd568 54874 admin optional apex-nslu2_1.4.15.2_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIM57oV+jOBy6uXS0RAqlxAJ4kDS6ka88z04BQlso6D8HvCd6oDgCfSias tmgeKT88sqLHclXTmXPWU4U= =rVU2 -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.15.2_arm.deb to pool/main/a/apex/apex-nslu2_1.4.15.2_arm.deb apex_1.4.15.2.dsc to pool/main/a/apex/apex_1.4.15.2.dsc apex_1.4.15.2.tar.gz to pool/main/a/apex/apex_1.4.15.2.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.15.1 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 18 May 2008 14:37:51 -0700 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.15.1 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Closes: 421359 451882 Changes: apex (1.4.15.1) unstable; urgency=low . * Release of old APEX version during Debian freeze. * Adding flash-apex so that apex is written to flash on install of the package (closes: #421359). * Expanding CONFIG_RAMDISK_SIZE (closes: #451882). Checksums-Sha1: 5c715990aa267fa27ba210feb1200f66cff66e3a 706 apex_1.4.15.1.dsc b881564cd70cb65837bba94d832823ceff7f4a75 1095806 apex_1.4.15.1.tar.gz b597de293a1d00e67e1775bd9ede6e12b608e710 54706 apex-nslu2_1.4.15.1_arm.deb Checksums-Sha256: c66495ee2c97221783fe713c6a2f23f25d55eb7c7c04591f851603e29e57bc08 706 apex_1.4.15.1.dsc b6ea26c0567aacaf1e313578a8442177ae02513a1d4faebfc36389bf9d2fbecc 1095806 apex_1.4.15.1.tar.gz 286a7ee381343c284d1b72a05f75efa87cb505e271acce67871467252d789f5a 54706 apex-nslu2_1.4.15.1_arm.deb Files: bffacd9436d6287ff72c55d100e7d73d 706 admin optional apex_1.4.15.1.dsc 0676db1584d4a6bb5e7eb35ba46ae9c7 1095806 admin optional apex_1.4.15.1.tar.gz eba626cf5414b9d390cfb2279987bd18 54706 admin optional apex-nslu2_1.4.15.1_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIMZeOV+jOBy6uXS0RAt9PAKCPH/CsVhhdDLjDFbr7jAAeSddRfQCfd6Nx CVHgvHblube5F6lBf/tMix8= =SaHT -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.15.1_arm.deb to pool/main/a/apex/apex-nslu2_1.4.15.1_arm.deb apex_1.4.15.1.dsc to pool/main/a/apex/apex_1.4.15.1.dsc apex_1.4.15.1.tar.gz to pool/main/a/apex/apex_1.4.15.1.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.15 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 5 Feb 2007 18:35:11 -0800 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.15 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Changes: apex (1.4.15) unstable; urgency=low . * Modified the rules file to support cross-building. * Closes bug#409189 * Fixed the output file name. It was inadvertently changed to /boot/apex.bin from /boot/apex.flash. * Closes bug#409747 Files: 2ea4357762e1a038772d9b81603f7319 499 admin optional apex_1.4.15.dsc 2e3a564fd8aac8e49a70798a9aaf4660 619002 admin optional apex_1.4.15.tar.gz 6f3a4950051e93c90d5d7818b3bb1116 52394 admin optional apex-nslu2_1.4.15_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFyBKRV+jOBy6uXS0RAkXSAJ4hUnT8UVvjwqkWJq4ZqpRLBTaGMwCfaH2H 1UYxhrgsh3Ts2amWd5HMmgs= =CZnq -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.15_arm.deb to pool/main/a/apex/apex-nslu2_1.4.15_arm.deb apex_1.4.15.dsc to pool/main/a/apex/apex_1.4.15.dsc apex_1.4.15.tar.gz to pool/main/a/apex/apex_1.4.15.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.14 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 30 Jan 2007 19:19:55 -0800 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.14 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Changes: apex (1.4.14) unstable; urgency=low . * Revised the libfuncs1.S file for arm so that armel can build. * Closes bug#408443 * Changed the rules file to drop the executble bit on the apex.flash file written to /boot. * Closes bug#396447 Files: c177995536957d75c61be41a3eb2f049 499 admin optional apex_1.4.14.dsc a9cb27fb1e04b43e4d9f32368dfe9b18 619533 admin optional apex_1.4.14.tar.gz defd2b93620194b1f65113181b163d9b 51472 admin optional apex-nslu2_1.4.14_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFwBHSV+jOBy6uXS0RAuCnAJ40eOysbiDqnBBtTkPh/FTERJBS1gCdGfTr 9+O9xcbeBi0JAzLguUfElVM= =One7 -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.14_arm.deb to pool/main/a/apex/apex-nslu2_1.4.14_arm.deb apex_1.4.14.dsc to pool/main/a/apex/apex_1.4.14.dsc apex_1.4.14.tar.gz to pool/main/a/apex/apex_1.4.14.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.7 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 22 Oct 2006 14:20:13 -0700 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.7 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Changes: apex (1.4.7) unstable; urgency=low . * New command line starts RTC. * Moved the environment to the same block as the loader. Files: c222ac37fb85761aa3a17db0a6237199 474 admin optional apex_1.4.7.dsc 394626325d5b96e3b42a5ca7dcadc4cd 2033894 admin optional apex_1.4.7.tar.gz 3ea5eb91f065f7f7a1302da484adf94f 37952 admin optional apex-nslu2_1.4.7_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFFO/3hV+jOBy6uXS0RAqz8AJ9+N45yQbqu+gtQnvthOve8GjHNlQCfVP4t zUqPZll64QIiapy/oqyeuWY= =I5JG -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.7_arm.deb to pool/main/a/apex/apex-nslu2_1.4.7_arm.deb apex_1.4.7.dsc to pool/main/a/apex/apex_1.4.7.dsc apex_1.4.7.tar.gz to pool/main/a/apex/apex_1.4.7.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Buildd maintenance for dummies
On Tue, Sep 05, 2006 at 07:58:18PM +0200, Luk Claes wrote: Hi I recently took over the buildd maintenance of signy.farm.ftbfs.de, a mips buildd for experimental, sarge-backports, sarge-volatile and non-free (whitlisted packages). I actually started in helping with the buildd maintenance of odin.farm.ftbfs.de which is a similar buildd for sparc. As newbie I made some stupid mistakes... I hereby want to announce a wiki page to make sure newbies in buildd maintenance don't make this mistakes again :-) Hurah! The wiki page [0] only talks about answering to build logs as there is already some decent information for setting up and configuring a buildd host and wanna-build [1] [2] [3]. Don't hesitate to add or improve content of the page, it's a wiki page after all... Cheers Luk [0] http://wiki.debian.org/Buildd/BuildLogs [1] http://kmuto.jp/open.cgi?buildd [2] http://www.debian.org/devel/buildd/ [3] https://db.farm.ftbfs.de/farm-reference/index.en.html -- Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[PATCH] fix for fglrx driver package builds
The ATI fglrx driver can produce debian packages for easy installation on Debian systems. Unfortunately, the kernel source package build is broken in the latest ATI releases. I'm not sure exactly when it broke as I have had it installed on a machine for several months. Moreover, the driver *does* work without the kernel module, but you won't experience any 3D acceleration and there will may be some glitching with the mouse pointer. There are a couple of caveats with this patch. The ATI package isn't really patchable. What you can do is use the --keep switch so that the archive unpacks to fglx-install/. You can then apply the patch to that directory. Change directories into fglx-install/ and run # ./ati-installed 8.28.8 --buildpkg Debian/etch to perform the build. Debian packages will be saved to the parent directory. The second caveat is that this patch only fixes the build for etch. There are several versions of the rules files, etch, experimental, and sid. If you want to build for these, you'll have to make the same change to the other rules files. Finally, I'm not really sure why the original code failed. I didn't spend enough time with this to determine the root cause. As we are using Debian, I am confident that tar supports the -j switch so there ought to be no problem with change. Cheers. diff -ruB fglrx-install-original/packages/Debian/overlay/etch/rules fglrx-install-fixed/packages/Debian/overlay/etch/rules --- fglrx-install-original/packages/Debian/overlay/etch/rules 2006-08-17 09:10:18.0 -0700 +++ fglrx-install-fixed/packages/Debian/overlay/etch/rules 2006-09-03 18:09:22.0 -0700 @@ -214,7 +214,7 @@ $(KSRCDIR)/debian (cd debian/$(PKG_kernel_src)/usr/src \ chown -R root:src modules \ - tar -c modules | bzip2 fglrx.tar.bz2 \ + tar jcf fglrx.tar.bz2 modules \ rm -rf modules) # install panel files dh_install -A -p$(PKG_control_qt3) usr/X11R6/bin/fireglcontrolpanel usr/bin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.4 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 14 Aug 2006 17:06:58 -0700 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.4 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Changes: apex (1.4.4) unstable; urgency=low . * Small changes to the configurations for debian builds: noirqdebug added command line, removed root= from command line. * Revised copyright file to conform to approved practices. Files: b1ad1e7b8d2a24ccc9bc951be82964f4 473 admin optional apex_1.4.4.dsc 983b49f4866fcd05cb1006a2094fc674 548034 admin optional apex_1.4.4.tar.gz 1b5299c070656d875a0444caafe827b3 37468 admin optional apex-nslu2_1.4.4_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE4RJuV+jOBy6uXS0RAi1lAJ4jkHZiFCSsPFvr5htOdV+4umQ5owCfcgZ8 4gjGowR5RA5sKsi+stYpPFQ= =b1vG -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.4_arm.deb to pool/main/a/apex/apex-nslu2_1.4.4_arm.deb apex_1.4.4.dsc to pool/main/a/apex/apex_1.4.4.dsc apex_1.4.4.tar.gz to pool/main/a/apex/apex_1.4.4.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted apex 1.4.5 (source arm)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 18 Aug 2006 09:44:34 -0700 Source: apex Binary: apex-nslu2 Architecture: source arm Version: 1.4.5 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: apex-nslu2 - APEX Boot Loader for Linksys NSLU2 Changes: apex (1.4.5) unstable; urgency=low . * Fixed the sort comparison function in the fis driver so that the skips are ordered by offset address. * Changed the default startup to copy from fis://kernel and fis://ramdisk. We no longer expect there to be SERCOMM headers on the kernel or ramdisk images. Freedom. Files: c919f06a3ca92ee97e4a77ca5a635b05 473 admin optional apex_1.4.5.dsc 75008aa4a7d5d7a4d1a5cd16cb8ed657 547260 admin optional apex_1.4.5.tar.gz a65a387ff1e7cec624fdfdaf57e3fd65 37688 admin optional apex-nslu2_1.4.5_arm.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFE5fYcV+jOBy6uXS0RArn3AKCWzpLK68DfzlSKVvGABSUxM6jQLQCfd6Li dCgWGzr14/1c8ufam2jAVCc= =2cAL -END PGP SIGNATURE- Accepted: apex-nslu2_1.4.5_arm.deb to pool/main/a/apex/apex-nslu2_1.4.5_arm.deb apex_1.4.5.dsc to pool/main/a/apex/apex_1.4.5.dsc apex_1.4.5.tar.gz to pool/main/a/apex/apex_1.4.5.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installation is FANTASTIC!!!
On Fri, Apr 21, 2006 at 08:14:10AM +0200, Wolfgang Lonien wrote: And for those who still are complaining about the installer not being graphical: please, guys, there's more than your x86 machines. Keep that in mind. And where is the difference between a mouse click and a return key (yes, it's - mostly - that easy!)? Hear hear. I installed Debian with the etch installer to a new AMD64 machine. The only hitch was that I had to use expert mode because the one of the via drivers crashed the system. It handled LVM on RAID deftly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted buici-clock 0.4.6 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 17 Apr 2006 08:23:19 -0700 Source: buici-clock Binary: buici-clock Architecture: source i386 Version: 0.4.6 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: buici-clock - attractive desktop clock Changes: buici-clock (0.4.6) unstable; urgency=low . * Moved the executable from /usr/X11R6 to /usr. Files: 6ceffcd0f0b28a115aca60bbafcdd4e8 561 x11 optional buici-clock_0.4.6.dsc 4b19f4cee7ca72585a5bc4f6e12992cf 140695 x11 optional buici-clock_0.4.6.tar.gz c4607e26e0f5c6ca4a644165c88c5428 27876 x11 optional buici-clock_0.4.6_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFERGgFV+jOBy6uXS0RAqeBAJ49dLB1auMcQrxNna3lA/WByUByHgCdFEiI 1GYzsCxOdP9bm4hkfMmXUs0= =xIdU -END PGP SIGNATURE- Accepted: buici-clock_0.4.6.dsc to pool/main/b/buici-clock/buici-clock_0.4.6.dsc buici-clock_0.4.6.tar.gz to pool/main/b/buici-clock/buici-clock_0.4.6.tar.gz buici-clock_0.4.6_i386.deb to pool/main/b/buici-clock/buici-clock_0.4.6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted buici-clock 0.4.5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 17 Jan 2006 11:54:59 -0800 Source: buici-clock Binary: buici-clock Architecture: source i386 Version: 0.4.5 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: buici-clock - attractive desktop clock Changes: buici-clock (0.4.5) unstable; urgency=low . * Autoconf fix required unstable version of autoconf. This update also fixes: * Updating the control file. Removing xlibs-dev dependency. * Updated the configure script to fix an error in the way that older autoconf's searched for X libraries and header. * Added SM and ICE libraries to the list of build-depends, libraries that the whiz-bang script missed. Files: 5777e3c820f9c18cabcbc33ec83967be 562 x11 optional buici-clock_0.4.5.dsc 8948c3d1f9d70788b7ef0ae6096532f2 154519 x11 optional buici-clock_0.4.5.tar.gz 44d72d4f4de33b23b735b60e5e35b973 26590 x11 optional buici-clock_0.4.5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDzUu3V+jOBy6uXS0RAv0/AJ4kw6U6ugAifylcyFtMzVl5C0RgMwCfYBmV IAkOL3HB3p4IzOw1wMuQMDk= =lqdg -END PGP SIGNATURE- Accepted: buici-clock_0.4.5.dsc to pool/main/b/buici-clock/buici-clock_0.4.5.dsc buici-clock_0.4.5.tar.gz to pool/main/b/buici-clock/buici-clock_0.4.5.tar.gz buici-clock_0.4.5_i386.deb to pool/main/b/buici-clock/buici-clock_0.4.5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted buici-clock 0.4.4 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 16 Jan 2006 15:02:49 -0800 Source: buici-clock Binary: buici-clock Architecture: source i386 Version: 0.4.4 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: buici-clock - attractive desktop clock Changes: buici-clock (0.4.4) unstable; urgency=low . * Rolled revision to propagate configure script change as well as: * Updating the control file. Removing xlibs-dev dependency. * Updared the configure script to fix an error in the way that older autoconf's searched for X libraries and header. Files: cf48a5a85f41c0b11cf8b5469290fd1b 539 x11 optional buici-clock_0.4.4.dsc c68c9a01bac28f289b84eb5768eb4197 121985 x11 optional buici-clock_0.4.4.tar.gz edecad894002467453314d35b6556786 26498 x11 optional buici-clock_0.4.4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDzCbJV+jOBy6uXS0RAhftAKCXF736wjf5ACK/HbKhYoLp3dEpbgCfZbGl 7AnLrM9RsijDqHlnn+nZa84= =RtlL -END PGP SIGNATURE- Accepted: buici-clock_0.4.4.dsc to pool/main/b/buici-clock/buici-clock_0.4.4.dsc buici-clock_0.4.4.tar.gz to pool/main/b/buici-clock/buici-clock_0.4.4.tar.gz buici-clock_0.4.4_i386.deb to pool/main/b/buici-clock/buici-clock_0.4.4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted buici-clock 0.4.3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 13 Jan 2006 19:29:22 -0800 Source: buici-clock Binary: buici-clock Architecture: source i386 Version: 0.4.3 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: buici-clock - attractive desktop clock Changes: buici-clock (0.4.3) unstable; urgency=low . * Updating the control file. Removing xlibs-dev dependency. Files: a062f0b8e8f32b7332890432e89a3560 539 x11 optional buici-clock_0.4.3.dsc 1c24aad51324b71e9f0de28ab4cb9ff4 121889 x11 optional buici-clock_0.4.3.tar.gz 86f3d34108d6033510549dc1758194ba 26424 x11 optional buici-clock_0.4.3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDyIETV+jOBy6uXS0RAnLuAJ93A9RnHB8HEFJWxLT3dMbYitKuPQCZAcsP b1brROmxVQus3KYLYV7ISoo= =YPAh -END PGP SIGNATURE- Accepted: buici-clock_0.4.3.dsc to pool/main/b/buici-clock/buici-clock_0.4.3.dsc buici-clock_0.4.3.tar.gz to pool/main/b/buici-clock/buici-clock_0.4.3.tar.gz buici-clock_0.4.3_i386.deb to pool/main/b/buici-clock/buici-clock_0.4.3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#315903: ITP: evilfinder -- proves that any given subject is evil
On Mon, Jun 27, 2005 at 11:42:34PM -0500, Kenneth Pronovici wrote: On Tue, Jun 28, 2005 at 01:37:25PM +0900, Miles Bader wrote: Kenneth Pronovici [EMAIL PROTECTED] writes: Oh come on, of course not. But if you can't admit that this is a novelty application and not a utility, you're kidding yourself. For the record, I _was_ kidding in my original message -- but I do think it looks like a fun program, and certainly stand by the rest of my message. Fair enough. Whew. That was close. I thought we were gonna lose evilfinder. KEN -- Kenneth J. Pronovici [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dhcp-client package in sarge
On Fri, Jun 03, 2005 at 08:56:07AM +0200, Nicolas Kreft wrote: Hi List! Is it for a special reason that the default dhcp-client in sarge is ancient (version 2.0pl5)? This client does not follow the RFC correctly. When it does a dhcpdiscover and the interface has been previously configured with some ip address it is still using that ip for the dhcpdiscover. This causes the dhcp server (3.0.2) on my network to abandon that ip address. The 3.x series has been released nearly 4 years ago, why not make it the default? I had the same problem with dhclient. I was mounting root over NFS and then using DHCP to fill out resolv.conf. The 'problem' was that the deconfiguring of the interface was happening in a script before dhclient did it's magic. I built pump to solve the problem. IIRC, the issue isn't fixed in newer versions of dhclient, but others may know for sure. Cheers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alternative: Source-Centric Approach [w/code]
On Tue, Mar 15, 2005 at 11:25:23AM -0600, John Goerzen wrote: So, what do you think? Could this work? I like the idea a lot. What I'd like to see is a way to do a cross-platform build for the small system targets. I do a lot of ARM work: low-performance, resource limited targets. Frankly, this is something I'm actively working on. I agree that the Debian infrastructure shouldn't be required to do all of the building. It would be helpful, though, if there was support for other arch's to be built efficiently by the users of those arches. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alternative: Source-Centric Approach [w/code]
On Tue, Mar 15, 2005 at 12:42:54PM -0500, Stephen Frost wrote: - Mirror only the popular archs. - Support buildds for stable-enough archs that run them. - Try to include everything in a release, but drop archs more quickly than has been done in the past if there's a lack of resources, but do outline what people need to do if they want the arch included. - For archs that weren't able to make the cut, provide .debs for the packages which don't have RC bugs. Don't provide .debs for the packages which have RC bugs on that architecture. Attempt to include the archs in security updates, but if it's not built fast enough or whatever then drop the .deb for that package and provide the source update. A fixed .deb can be done later by whomever. I dunno, just some thoughts. I don't like becoming a mostly source-only distro for less common archs. If someone wants to build the debs and upload them, let them. This sounds like the idea already going around of, essentially, 'build what we can'. I'm suggesting that we go a step further and enable a new segment of the user base. The turnkey people use x86 (+relatives) and PPC. The people on other arches can either step-up to provide resources to Debian, or they can build what they need. Of course, I'd rather not cut the support. But John draws, IMHO, a reasonable line in the sand. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alternative: Source-Centric Approach [w/code]
On Tue, Mar 15, 2005 at 02:24:01PM -0600, John Goerzen wrote: On Tue, Mar 15, 2005 at 07:46:23PM +0100, Adrian Bunk wrote: don't handle deps at all) ... So, what do you think? Could this work? Yes, this could work. That's what Gentoo is good at. [ snip ] Your priority are your users, and if Debian has decided to focus only on some key architectures it would be the best for them to help them switching to Gentoo instead of hacking Debian to become some cheap Gentoo clone for most architectures. I don't view this as being a cheap Gentoo clone. In fact, I view srcinst as being the Gentoo idea, done right. Gentoo has a lot of problems, especially relating to difficult upgrades. Because of our superior packaging system, we are in a great position to hit the ground running and, with a little help from something like srcinst, come up with something that works -- and works better than Gentoo -- in a short amount of time. If the Debian developers intereested in the ports Debian intends to drop would switch to Gentoo for helping Gentoo to support all of their architectures and for providing easy Debian - Gentoo transition paths this would serve your users better. Yes, but I hope that this proposal, or other suggestions, can help us avoid dropping ports. This specific proposal, for instance, is meant to provide us with a way forward that addresses the main concerns while still producing a quality, usable result for our users. ...and may encourage development of new architectures as the overhead for each would be much smaller. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Alternative: Source-Centric Approach [w/code]
On Tue, Mar 15, 2005 at 10:45:45PM +0100, Ola Lundqvist wrote: The speed of buildd systems mostly becomes irrelevant. They will still have to keep up with base (the set of .debs that we do distribute for a SO arch). Anything past that is there just for QA purposes -- to make sure packages are buildable on these archs, and would be optional. This is the problem. How do you make sure that the package is buildable on the architecture without building it? And if you have built it why not just add it to the archives. :) So you still need a buildd. :( Not necessarily. I think if we make it easy for end users to perform selective builds we have a chance of making it work. So, what do you think? Could this work? Nice idea, but I do not really see the benefit, more than on ftp disk space and security update speed. While I would like to *not* see a change to the build structure, I agree that removing lesser used arch's from the testing guaranteed support infrastructure gives room for higher frequency releases. IMHO, the disk space issue is a red herring. Security updates, too, are not the primary concern, it's getting all of the cats out the door with some frequency. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
On Tue, Feb 22, 2005 at 03:15:58AM +, Dirk Eddelbuettel wrote: But to the best of my knowledge, Marco's (blog) post from a few months ago which showed download from ftp.it.debian.org by architecture stands undisputed: essentially all users are on i386 clearly dominating all other arches, with a fraction of users in maybe two, three, four other arches --- and comparitively nobody in the other fringe arches we keep around for no good reason. And I still believe it delays our releases. As you say, there are no KDE users on mips. So guys, we need a new framework. Maybe we should pick up on Petter's suggestion of stricter buildd requirements. Maybe we should only build base and essential packages for the minor architectures [ after, apt-source is there for everybody to go further ]. We can still provide the debian-installer for everything with a power cord provided we have the resources to code, maintain, debug, document, improve, ... and all those platforms. IMHO, we are in an awkward position. There are *some* users in the other architectures. Not, many but some. If we drop those architectures then we will have *no* users in other architectures. This debate reminds me of the way that large corporations go for the largest market segment and leave the small fry without anyone catering to their needs. Debian is not a desktop architecture for some of these other architectures, but that doesn't mean it isn't valuable. It is clear that there is a problem with buildd resource efficiency and the fact that large packages delay our release undesirably because of the high buildd latency. I would hate to see Debian throw out the baby. The problem with apt-source is that, if I understand it correctly, it only performs native builds. This isn't necessarily possible for some people. Speaking as an ARM user on embedded systems, there is no chance I'm going to build natively on the targets I support. It does seem prudent to find a way to permit a release on x86 and ppc before all architectures are complete. Especially if this tactic will give Debian the ability to release more often. Is it so bad to allow the smaller architectures to lag as long as problems are fixed? Cheers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Let's remove mips, mipsel, s390, ... (Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space])
On Mon, Feb 21, 2005 at 08:56:27PM -0800, Thomas Bushnell BSG wrote: Marc Singer [EMAIL PROTECTED] writes: It does seem prudent to find a way to permit a release on x86 and ppc before all architectures are complete. Especially if this tactic will give Debian the ability to release more often. Is it so bad to allow the smaller architectures to lag as long as problems are fixed? This would only make sense if we had a complete x86 and ppc release, but not a complete mips release. In practical terms, this doesn't happen. It's not like we do all the x86 work, and then the rest. I agree completely. This makes sense iff the lesser used arches affect release. As I posted in another message, this discussion about removing arch's seems to me to be a red herring. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Who could be able to help SW vendors to support Debian?
On Tue, Feb 01, 2005 at 07:37:27PM +0100, Christian Perrier wrote: During the Solutions Linux expo in Paris, the DD's present at the Debian booth have been approached by a representative from Trend Micro Corp. who develops and sells security software (the most well known being probably a virus scanning software and such similar software suites). We ended with a very interesting and long discussion with their Product Manager for Client/Server messaging products about the proper way for them to support Debian. It seems that such support is a growing request from their customers (some of them being important Ministries in France and probably others worldwide) who use big farms of Debian-based servers. As far as I have understood, supporting Debian for this vendor is a real concern, but they fail to be sure in who to get in touch with for technical issues regarding the compatibility of their products and our distribution in general (which includes direct interaction with the Linux kernel, as far as I have understood from him). Their concernes was also deciding about *which* release of Debian they should support. Though question as one may imagine because just answering thou shalt use stable is obviously not enough. From discussions I previously had with other visitors at the booth, he concluded by himself that focusing their developers on sarge would probably be a better investment than trying to support woody (this is still a matter of months of development, so hopefully sarge will have been released then). Would any people around have pointers which could be given to such people ? Do we already have an entry point for such technical issues as proprietary SW vendors needing technical information about the way to support Debian ? It isn't clear to me what sort of compatibility issues you would be talking about. Is this an x86 thing? Or a release thing? I've been under the impression that the only machine-level incompatibilities are really kernel and driver issues and not issues with Debian per se. Can you be a little more specific? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Who could be able to help SW vendors to support Debian?
On Tue, Feb 01, 2005 at 10:57:08PM +0100, Christian Perrier wrote: Would any people around have pointers which could be given to such people ? Do we already have an entry point for such technical issues as proprietary SW vendors needing technical information about the way to support Debian ? It isn't clear to me what sort of compatibility issues you would be talking about. Is this an x86 thing? Or a release thing? I've been under the impression that the only machine-level incompatibilities are really kernel and driver issues and not issues with Debian per se. Well, I'm not the software vendor here..:-) As far as I've inderstood, this product induces some interaction at kernel-level and the vendor developers may have concerns about the kernel on the distribution they want to support their product on. They probably also have concerns about the library compatibility and such stuff. Again, I can't really speak for them, but I'd like to point them the right direction. I don't like to pass the buck, yet I can't see a way that Debian, as it is can support them directly. Perhaps they ought to look to the Debian consultant's list for someone to help. No matter how the problem is sliced, they're going to need to have someone on their side who can track down issues. This person may not be a kernel hacker, but there is always a need to have someone who will work with folks on the mailing lists who do. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Who could be able to help SW vendors to support Debian?
On Tue, Feb 01, 2005 at 11:01:25PM +0100, Francesco Paolo Lovergine wrote: On Tue, Feb 01, 2005 at 11:35:41AM -0800, Marc Singer wrote: I've been under the impression that the only machine-level incompatibilities are really kernel and driver issues and not issues with Debian per se. Can you be a little more specific? Currently for instance Matlab 6.5+ cannot be installed without a little hack in the installer, that's due to a known bug (or feature ?) in our sarge libc: it is not executable, like RH ones. I don't get the last part of that. 'it is not executable'? Supporting a release involves also those aspects. I think I'm getting the idea. This is an interesting issue as it ought to fall on the shoulders of the application vendor given that their software has specific needs not readily addressable by the distribution. Is this one of those lbrary .so version number incompatibilities? Seems like we're in that gray zone between the distribution and the end-user. Software vendors aren't pulling their weight because many believe that RH *is* Linux, wrong on so many levels. Again, it seems like this is a place where someone ought to commit a little cash to smooth over the wrinkles. OEM hardware vendors already do this to support MS. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: UserLinux white paper
On Tue, Dec 02, 2003 at 04:52:47PM -0800, Bruce Perens wrote: So, our problem is how to rebalance the vendor-customer relationship for our purposes. Probably the most useful tool is the industry group organization, where a number of similar businesses get together to steer their participation in userlinux, and the group involves their vendors from a position of strength, together, rather than one of weakness, apart. Customer group 1 is confident that this will work for them. May I suggest that there is still a role for some sort of ISV support on behalf of UserLinux. I have been asked by several of my clients: what is this Free Software or Open Source thing and how can I benefit? What holds them back is experience with the target system and a fear of the unknown. Their perception, while overstated, is still important. So, to the end of bringing ISVs to appreciate UserLinux perhaps there is a place for a laboratory. The difference between a laboratory and the common, custom ISV/OS Vendor relationship is that the lab is an open resource. It provides an environment of hardware, software, and expert support that guides them, teaches them, to work with the system. The lab is free to any who can show up, provided that adequate funding is available. Or, ISV can be enrolled to support the lab given that they see value in it. I've seen this model work well on several levels. Not only is there a realistic feeling of support, but there the inter-ISV relationships that appear when developers meet at the lab. I believe that for many, the physical presence of such a laboratory is an important factor in their believe that the system, UserLinux in this case, is a real entity. Cheers.
Re: faster boot
On Tue, Oct 21, 2003 at 05:33:38AM +0200, Thomas Hood wrote: On Tue, 2003-10-21 at 05:12, Russell Coker wrote: Hmm, maybe we could make it the rule that anything with number 99 can return before it's finished initialising? If the point here is to speed up boot then I think it would suffice to move the rc symlinks for those leaf services to something later than S99xdm. cd /etc/rc2.d ; mv S??netatalk S99znetatalk Perhaps that means that xdm ought to be midway or, at least, not the last number.
Re: x windows wont start
On Sun, Oct 19, 2003 at 07:21:57PM +0100, stuart whittaker wrote: refuses to start and the retry process fails also...??? thanks for any advice. stuart stuart [EMAIL PROTECTED] This sounds like a user question and not a dev question. No? Usually x doesn't start because of problems with the server configuration. Have you looked at the X log (/var/log/XFree86*) ?
Re: chroot on debian hosts?
On Wed, Oct 15, 2003 at 09:37:51AM +0100, Colin Watson wrote: On Tue, Oct 14, 2003 at 06:20:15PM -0700, Marc Singer wrote: (I thought I sent this, but now I cannot find it to be sure.) I'd like to build against sid on a machine (ia64) I don't own but which Debian does have available. I tried the recipe from the developer's manual using fakeroot. It failed because it could not find a package. Perhaps, this is a bug in debootstrap. Is that method supposed to work? Use dchroot to access chroots on Debian machines. You will not be able to install packages yourself. Quantz doesn't appear to have this program, though the source is in joey's home. I have the impression that I'm swimming up stream on this one. Is this the right way to test a patch for a specific architecture?
chroot on debian hosts?
(I thought I sent this, but now I cannot find it to be sure.) I'd like to build against sid on a machine (ia64) I don't own but which Debian does have available. I tried the recipe from the developer's manual using fakeroot. It failed because it could not find a package. Perhaps, this is a bug in debootstrap. Is that method supposed to work?
Re: Help needed: builds eating all memory
On Sat, Oct 11, 2003 at 04:00:34PM +0200, Sam Hocevar wrote: My openvrml packages have been failing to build on arm [1], mips [2] and mipsel [3] for some time. From the build logs, it looks like g++ is eating all the memory and the OOM killer kills it. What can I do? Ask the buildd admins to add more swap? I would be happy to cross-compile the packages (they don't require any arch-specific bootstrapping) but I don't have enough hard drive space to build a cross- compiler. emdebian.org has cross compilers. I don't think there is mips, but arm is available there.
Accepted curves 0.8.19 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 1 Oct 2003 23:36:36 -0700 Source: curves Binary: curves Architecture: source i386 Version: 0.8.19 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: curves - colorful console interface for CVS version control Changes: curves (0.8.19) unstable; urgency=low . * Changing to debian standards release 3.6.1. Files: 9061cf0d50ae5760e883fe9be761e44f 491 devel optional curves_0.8.19.dsc 6e280f6d87f5620221d14484d054e715 150307 devel optional curves_0.8.19.tar.gz eea6225761d7d416a3c14c2900674717 62786 devel optional curves_0.8.19_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/e8fLV+jOBy6uXS0RAlRHAKCMe1YD05pGAgfhbygEWssJUE/8KACfVftq 8ExMhvixC0I1AOZURCjZkGY= =6Vbr -END PGP SIGNATURE- Accepted: curves_0.8.19.dsc to pool/main/c/curves/curves_0.8.19.dsc curves_0.8.19.tar.gz to pool/main/c/curves/curves_0.8.19.tar.gz curves_0.8.19_i386.deb to pool/main/c/curves/curves_0.8.19_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need help on enhancing Telnet with srp
Firstly, this isn't really the right place to ask this kind of question as this list is for maintainers of packages for the Debian distributions. Tar said, I am not sure that what you want to do is possible with Telnet as the telnet protocol is content-free. That is to say that it has no knowledge of when the user is sending a password and when the user is sending some other type of data. As far as Telnet is concerned, the connection between the client and server is a simple bi-directional stream. (I know this isn't entirely true, but close enough in this case.) You probably need to write a new daemon to go with your client. Good luck. On Mon, Sep 08, 2003 at 08:51:51PM -0700, polavarapu deepti wrote: Hello, I am computer science student and my project is to enhance telnet using srp protocol to avoid passing passwords in plain text. i have no idea how to start about. I have link to your web-site with source code for telnet. I have been going through RFC2944 for telenet authentication:srp. I have already written code implementing SRP(secure Remote Password) in C++, just with a server and client. I have no idea what to do to embed this into telnet. Could anyone please help me to get started. Thanks alot, Deepti __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Latest gcc-3.3 and kernel compilation
Are we expecting the latest unstalble gcc compiler to correctly
compiler the kernel?
gcc --version
gcc (GCC) 3.3.2 20030812 (Debian prerelease)
I'm getting a new error when I compile the kernel. In the structure
below, it doesn't like the declaration for slot_tablen complaining
that
ide-cd.h:440: error: long, short, signed or unsigned used invalidly for
`slot_tablelen'
It looks like it doesn't like the obviously invalid use of short in
the declaration. How does this affect our wish to move to the new
compiler?
struct atapi_mechstat_header {
#if defined(__BIG_ENDIAN_BITFIELD)
__u8 fault : 1;
__u8 changer_state : 2;
__u8 curslot : 5;
#elif defined(__LITTLE_ENDIAN_BITFIELD)
__u8 curslot : 5;
__u8 changer_state : 2;
__u8 fault : 1;
#else
#error Please fix asm/byteorder.h
#endif
#if defined(__BIG_ENDIAN_BITFIELD)
__u8 mech_state: 3;
__u8 door_open : 1;
__u8 reserved1 : 4;
#elif defined(__LITTLE_ENDIAN_BITFIELD)
__u8 reserved1 : 4;
__u8 door_open : 1;
__u8 mech_state: 3;
#else
#error Please fix asm/byteorder.h
#endif
byte curlba[3];
byte nslots;
__u8 short slot_tablelen;
};
Re: Latest gcc-3.3 and kernel compilation
On Thu, Aug 21, 2003 at 12:44:11PM -0400, Ben Collins wrote: __u8 short slot_tablelen; Isn't it just a plain error? Either it's a char, or it's a short. It can't be both, right? That's what I think, too. It looks, too, to be something added in a patch because the indentation is different. As Ben pointed out, it looks like I can only compile 2.4.21 with gcc-3.3. Working on it.
Accepted curves 0.8.18 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Aug 2003 21:39:49 -0700 Source: curves Binary: curves Architecture: source i386 Version: 0.8.18 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: curves - colorful console interface for CVS version control Closes: 147605 Changes: curves (0.8.18) unstable; urgency=low . * Fixed old bug where curves would assert, and may eventually segment fault, when browsing an empty directory. (closes: #147605) * New upload so that the latest gcc-3 is used. Files: 7f903b81acc148e13665ef7cbd5cfdbf 493 devel optional curves_0.8.18.dsc 32ce157e22f5a74e703af488df7564f4 150278 devel optional curves_0.8.18.tar.gz fdf8580ed333656d5adf21856ad1d150 62760 devel optional curves_0.8.18_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/RE6DV+jOBy6uXS0RAh8OAJ0XPQFcI1ZoHhpsysBoizhTS+JWdgCfaGl1 qus4Mg/fWyXEdaUWVQ8Yr64= =tZ3/ -END PGP SIGNATURE- Accepted: curves_0.8.18.dsc to pool/main/c/curves/curves_0.8.18.dsc curves_0.8.18.tar.gz to pool/main/c/curves/curves_0.8.18.tar.gz curves_0.8.18_i386.deb to pool/main/c/curves/curves_0.8.18_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted buici-clock 0.4.2 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Aug 2003 21:52:54 -0700 Source: buici-clock Binary: buici-clock Architecture: source i386 Version: 0.4.2 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: buici-clock - attractive desktop clock Changes: buici-clock (0.4.2) unstable; urgency=low . * Upload to upgrade to new gcc compiler. Files: 5639c5b1b99cdbad38835cbb7a36b74e 552 x11 optional buici-clock_0.4.2.dsc a5028e6c8099db03859b69412aa1fede 121749 x11 optional buici-clock_0.4.2.tar.gz c68ab2421807719cf8b9be5e8357ba80 26478 x11 optional buici-clock_0.4.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/RFBrV+jOBy6uXS0RAqdfAJ9/iFrmCyXp3sWAvnPxKtQ3Zb3rJQCfZKfB b+R9gJj4M/lZuhSRFxfYL5I= =ZGEK -END PGP SIGNATURE- Accepted: buici-clock_0.4.2.dsc to pool/main/b/buici-clock/buici-clock_0.4.2.dsc buici-clock_0.4.2.tar.gz to pool/main/b/buici-clock/buici-clock_0.4.2.tar.gz buici-clock_0.4.2_i386.deb to pool/main/b/buici-clock/buici-clock_0.4.2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bsign 0.4.5 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 6 Aug 2003 14:35:54 -0700 Source: bsign Binary: bsign Architecture: source i386 Version: 0.4.5 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: bsign - Corruption intrusion detection using embedded hashes Changes: bsign (0.4.5) unstable; urgency=low . * Recast the signature data pointer to prevent inappropriate sign extension. Files: aa3a2c8d63c0a6d26882d3d963b41805 488 admin optional bsign_0.4.5.dsc 57984eb43bacd5cfd497cbf36912a14d 77471 admin optional bsign_0.4.5.tar.gz ffc7e3fd6ac7cc77c91774425355a4f2 194292 admin optional bsign_0.4.5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/MXX3V+jOBy6uXS0RAm5tAJ9SxvtGyxBxUInfRJZmw3+ot210tgCeJw1J e5z68SnmYpEQTg4p0x5Rd/I= =PHg9 -END PGP SIGNATURE- Accepted: bsign_0.4.5.dsc to pool/main/b/bsign/bsign_0.4.5.dsc bsign_0.4.5.tar.gz to pool/main/b/bsign/bsign_0.4.5.tar.gz bsign_0.4.5_i386.deb to pool/main/b/bsign/bsign_0.4.5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Access to an ARM system?
On Fri, Aug 08, 2003 at 12:55:11PM -0600, Jamin W. Collins wrote: Does someone have an ARM system that I could gain access to? I'd really like to put the ARM specific bug[1] filed against the Jabber package to bed once and for all. I've seen reports of Jabber running on ARM systems and of course the bug report of it segfaulting. Any assistance in this matter would be most appreciated. I've sent a request to debian-admin, but have heard nothing back from them. I have a couple of ARM boards that boot Debian. I'm not sure what it is you want to do on the machine. What is it you are trying to do?
Re: Access to an ARM system?
On Fri, Aug 08, 2003 at 01:33:05PM -0600, Jamin W. Collins wrote: On Fri, Aug 08, 2003 at 12:00:37PM -0700, Marc Singer wrote: On Fri, Aug 08, 2003 at 12:55:11PM -0600, Jamin W. Collins wrote: Does someone have an ARM system that I could gain access to? I'd really like to put the ARM specific bug[1] filed against the Jabber package to bed once and for all. I've seen reports of Jabber running on ARM systems and of course the bug report of it segfaulting. Any assistance in this matter would be most appreciated. I've sent a request to debian-admin, but have heard nothing back from them. I have a couple of ARM boards that boot Debian. I'm not sure what it is you want to do on the machine. What is it you are trying to do? Ideally, get an installation of Jabber (from the debian package binaries) to run and accept a client connection. According to the bug report, the Jabber server segfaults on startup. So, if I can get the server up and running and connect to it, I'd consider that something of a success. So, you want the Jabber server installed on an ARM system so that you can connect to it and either a) verify that it crashes, or b) demonstrate that it doesn't. If this is so, then I can do this for you and give you a routable address to the ARM machine. Do you need to be able to do anything *on* the ARM? I think I can get ssh and some other utilities running on it. Still, let me be clear. I am using a Sharp KEV7A400 for some embedded systems development. I have a script that produces stripped-down filesystems for the target using the Debian package archive. It isn't hard for me to add programs to the filesystem, but I need to know exactly what has to be there since this isn't exactly an 'apt-get install' situation. Let me know and I'll put some cycles to it. Cheers.
Re: Debconf or not debconf : Conclusion
On Fri, Jul 04, 2003 at 12:18:33AM -0400, Theodore Ts'o wrote: On a separate but related topic, I think a much better approach would be to handle configuration as a step entirely separate from the install phase. Let the install be entirely quiet, and let packages have intelligent defaults. If the package absolutely must be configured before it can be used, then let it be non-functional until someone actually calls dpkg-configure (which would be just like dpkg-reconfigure except that's the only time the questions would be asked). - Ted Hear, hear. There is the related trouble that the only way to disable most packages is to uninstall them. Sometimes, it is desirable to temporarily disable a service without removing the binaries or changing the executability of the init.d script.
Re: Debconf or not debconf : Conclusion
On Fri, Jul 04, 2003 at 01:11:48AM -0400, Joey Hess wrote: Theodore Ts'o wrote: On a separate but related topic, I think a much better approach would be to handle configuration as a step entirely separate from the install phase. Let the install be entirely quiet, and let packages have intelligent defaults. If the package absolutely must be configured before it can be used, then let it be non-functional until someone actually calls dpkg-configure (which would be just like dpkg-reconfigure except that's the only time the questions would be asked). Debconf is flexable enough so you can do that already (assuming all packages use debconf). - comment out the dpkg-preconfigure call in /etc/apt/apt.conf.d/70debconf - set in /etc/debconf.conf: Frontend: noninteractive Admin-Email: - dpkg-configure is the following script: #!/bin/sh -e dpkg-reconfigure --unseen-only --default-priority -freadline $@ My reading of Ted's comment is that this ought to be the *default* policy. I won't go so far as to say that RH made a better choice, but I don't really see the benefit of the all of the warning messages when once displayed they are nowhere to be found. Perhaps, you'll have a command for recovering these messages, but that doesn't change the fact that they are just not really necessary at install time.
policy-rc.d
On Fri, Jul 04, 2003 at 01:06:14AM -0400, Joey Hess wrote: Marc Singer wrote: There is the related trouble that the only way to disable most packages is to uninstall them. Sometimes, it is desirable to temporarily disable a service without removing the binaries or changing the executability of the init.d script. Take a look at invoke-rc.d and its policy program. OK. I can tell that this feature is available, though obscured by the lack of a man page for policy-rc.d or even a reference to a package that implements it. I *did* find a document through google, however. Reading it doesn't make it much clearer. My search through a Contents file doesn't show an implementor for policy-rc.d. Is there one or is it adhoc? -- Luckily, I am familiar with rule 3: 3. any action for a non-executable initscript is denied.
Re: Debian conference in the US?
Perhaps we can look at this a different way. I haven't read anyone voicing the opinion that GWB (can't say the name of the beast out loud) is a 'good fellow'. I'm supposing that all of us agree that he's a snake-oil salesmen of the odious kind, interested most in lining his pockets and the pockets of his pals at the expense of the majority of US citizens as well as international citizens. He is a ignorant bully whose opinions and actions don't represent me or my cohort. Yet, it is reasonable to take personal representing our feelings. There are folks who don't want to contribute an earned farthing to the US economy. So be it. This doesn't mean that we should not have a Debian conference in North America. I'm sure there are many North American DDs who'd like to meet more DDs in person. Having a conference in the US or Canada is not an endorsement of US foreign policy. It seems to me that the best place to have the conference in NA is where we get support. Should there be equal support in, for example, Vancouver and DC, then we can weigh merits. If we host it out of the US, then at least we can keep our shoes on. What do you think of the boycots of French products? Do you oppose them on principle? I just bought some french-cut green beans. %^)
Re: Debian conference in the US?
(Unintentionally, I first sent the reply to you directly.) On Fri, May 23, 2003 at 02:09:24PM +1000, Russell Coker wrote: Incidentally North America != USA. And your point is, what? A Canadian conference would be in North America and satisfy the objections of people who don't like the US, however it may be too far for some USians to travel. There is no forseeable future where everyone is satisfied. I just bought some french-cut green beans. %^) Probably not from France. Canada.
Re: Debian conference in the US?
On Fri, May 23, 2003 at 10:03:38AM -0700, John H. Robinson, IV wrote: Marc Singer wrote: (Unintentionally, I first sent the reply to you directly.) On Fri, May 23, 2003 at 02:09:24PM +1000, Russell Coker wrote: Incidentally North America != USA. And your point is, what? that north america contains not one, but three countries: Candada, USA, and Mexico Good grief. If you'd read the original message carefully, you'd notice that I know the difference. I wrote North America and meant it.
Re: Debian conference in the US?
For those reasons, I am planning to organise Debconf 4 in Vancouver (or maybe somewhere else, if there's a lot of hate for vancouver) sometime in the summer of 2004. Yipee!
Question of casts, lvalues, and operator
I've found that G++ 3.2 has a problem optimizing this code.
#include stdio.h
int func_b (void** ppv)
{
*ppv = (void*) 2;
return 0;
}
char* test (void)
{
char* pa = NULL;
func_b ((void*)pa);
return pa;
}
int main (int, char**)
{
char* p = NULL;
p = test ();
printf (%p\n, p);
return 0;
}
When compiling with -O0, everything is OK. -Os, on the other hand,
will optimize the return and always yield NULL.
I sent a preprocessed version of the errant file to gcc-bugs and was
told that my syntax is faulty and that the compiler will issue
warnings.
Here's his comment:
(Your code should get a warning, or perhaps even a hard error -
you're applying the operator to a cast to non-reference type, which
is not an lvalue, so it's invalid.)
Yet, -Wall does not make the compiler complain.
He says that the line ought to be
f ((void**)p);
which does generate correct code. Still, it seems to me that either
the compiler ought to warn or error, *or* the original code ought to
work.
So, is this simply an example of the compiler failing to warn?
Accepted buici-clock 0.4.1 (i386 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 12 Feb 2003 10:05:10 -0800 Source: buici-clock Binary: buici-clock Architecture: source i386 Version: 0.4.1 Distribution: unstable Urgency: low Maintainer: Marc Singer [EMAIL PROTECTED] Changed-By: Marc Singer [EMAIL PROTECTED] Description: buici-clock - attractive desktop clock Closes: 141442 170242 Changes: buici-clock (0.4.1) unstable; urgency=low . * Reordered dependencies to make xlibs-dev the default xlibs library. (closes: #170242) * Configuring explicitly in the current directory. * Applied suggested patch to xo/Makefile.in. (closes: #141442) Files: 8107fb0144b3bde520b456167f45a9a2 552 x11 optional buici-clock_0.4.1.dsc 00f8dc792c1b0a2071bbf0332a41f96c 121692 x11 optional buici-clock_0.4.1.tar.gz 0613e61b7385a280afc73d82aab7cf7b 29162 x11 optional buici-clock_0.4.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+So9rV+jOBy6uXS0RAkhnAKCJHz+G1AyXpw+c86EtWvC7AMC9RwCffvx+ /Ljs7E6yQsltHyA8KEcjVt8= =r3WV -END PGP SIGNATURE- Accepted: buici-clock_0.4.1.dsc to pool/main/b/buici-clock/buici-clock_0.4.1.dsc buici-clock_0.4.1.tar.gz to pool/main/b/buici-clock/buici-clock_0.4.1.tar.gz buici-clock_0.4.1_i386.deb to pool/main/b/buici-clock/buici-clock_0.4.1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to fetch proper source for libc
I'm tracking a memory leak that appears to stem from regexec(). [EMAIL PROTECTED] ~...coastal/ssem apt-cache policy libc6 libc6: Installed: 2.3.1-5 Candidate: 2.3.1-5 Version Table: *** 2.3.1-5 0 500 file: unstable/main Packages 100 /var/lib/dpkg/status 2.2.5-6 0 500 file: woody/main Packages 2.1.3-24 0 500 http://security.debian.org potato/updates/main Packages However, when I fetch source I get version 2.2.5 [EMAIL PROTECTED] ~...coastal/ssem apt-get source libc6 Reading Package Lists... Done Building Dependency Tree... Done Need to get 0B/11.8MB of source archives. dpkg-source: extracting glibc in glibc-2.2.5 Odd, but I assume apt is doing the right thing. My memory allocator saves a stack backtrace for each allocation so I can pinpoint the culprit. The call stack looks like this: regexec re_search_internal set_regs proceed_next_node re_node_set_insert malloc Note that this program is statically linked so that I can see all of the symbols. On building the library from source (2.2.5), these symbols are not present. If I unpack 2.3.1 source I don't see the symbols in posix/regex.c. Finally, I forced libc6-dev to reinstall the most recent unstable version. The symbols are definitely still present in /usr/lib/libc.a. Any suggestions? - Marc Singer
Re: How to fetch proper source for libc
On Mon, Dec 02, 2002 at 12:02:01AM +, Colin Watson wrote: However, when I fetch source I get version 2.2.5 What does your /etc/apt/sources.list look like? Duh. Right.
Re: How to fetch proper source for libc
On Mon, Dec 02, 2002 at 12:02:01AM +, Colin Watson wrote: On Sun, Dec 01, 2002 at 02:39:48PM -0800, Marc Singer wrote: I'm tracking a memory leak that appears to stem from regexec(). Hmm. What makes you think that this patch fixes a memory leak? I ask because the patch appears to deal with 16-bit characters.
Re: Debian based CD based distros
On Sat, Aug 31, 2002 at 01:42:36PM -0400, Dale Scheetz wrote: The first one I was shown by my neighbor is called Knoppix 3.1 and is produced by a German group. As a result it comes up in German, but there is a simple fix that will boot it in English (boot: knoppix lang=us) that only requires you to know that the equal sign is a shift 0. There appears to be an english ISO. Is this the one you are using? Downloading. It be a couple of hours before I can try it myself.
Re: When bind9 reinstalls, no db.root
On Thu, Aug 22, 2002 at 08:47:46AM +0100, Colin Watson wrote:
On Wed, Aug 21, 2002 at 05:10:58PM -0700, Marc Singer wrote:
I was asking for real examples in order to discuss how the case of
bind and db.root is *not* a member of that set and how there may be a
genuine problem with the handling of installing over missing
configuration files.
Maybe db.root just shouldn't be a conffile, that's all.
{Gesturing} That's what I'm saying.
As far as I can tell there is no way to pass --force-confmiss to dpkg
when using apt-get. Perhaps this is the only real omission.
Sure there is: it's something like -o DPkg::Options=--force-confmiss.
OK. You got me. Is there any hope that's you'll at least cede that
that's not as straightforward as we *could* be?
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 10:19:49PM -0400, Scott K. Ellis wrote:
Still, breaking bind's access to root name servers is particularly
troublesome because it may tend to break all net access. It may be
worthwhile to remove db.root from the list of configuration files.
Especially, because this list isn't something anyone should need to
change.
I beg to disagree. Changing db.root is the primary way to use an alternate
DNS root (either for an all-internal DNS, or to utilize an alternate DNS
root than NetSol's). Just because you can't see why something might be
configured differently doesn't mean other people can't.
One can change the database reference in named.conf to do this. The
difference is that db.root references 'the' root servers. You can
choose which ones you want to use in the zone file:
// prime the server with knowledge of the root servers
zone . {
type hint;
file /etc/bind/db.alternative_root;
};
The trouble with removing db.root is that it may not be obvious how to
recover when it is missing.
Re: When bind9 reinstalls, no db.root
On Thu, Aug 22, 2002 at 08:44:04AM -0400, Matt Zimmerman wrote: On Wed, Aug 21, 2002 at 05:10:58PM -0700, Marc Singer wrote: This terse reply is obviously inappropriate. If you are annoyed, stop writing. No less appropriate than your one-line dismissal of a reasonable and tactful response. So let me get this straight. You equate shut up with a request for concrete examples. How unfortunate. I was asking for real examples in order to discuss how the case of bind and db.root is *not* a member of that set and how there may be a genuine problem with the handling of installing over missing configuration files. Are you saying that you think that the situation with this particular conffile is different enough, and that there are enough other similar conffiles, that it justifies different handling by dpkg? If so, I think that I would disagree. In the particular case of BIND, it is entirely reasonable to move the entire configuration somewhere else (such as into a chroot) and remove /etc/bind and its contents. It would be confusing to have them reappear when BIND is upgraded. The idea is that db.root is a different kind of file. Most of the time, configuration files reflect the personality of the user's machine. db.root contains information about the root name servers. I would differentiate the presence of this information on a user's machine with the application of that information. It has a closer relationship to terminfo files or the POSIX timezone files than the global bash rc file. As far as I can tell there is no way to pass --force-confmiss to dpkg when using apt-get. Perhaps this is the only real omission. man 5 apt.conf, search for 'dpkg', 6th match. That's a global change. Someone else pointed out that it can be passed with -o. Still, breaking bind's access to root name servers is particularly troublesome because it may tend to break all net access. It may be worthwhile to remove db.root from the list of configuration files. Especially, because this list isn't something anyone should need to change. The conffile system does nothing to break BIND's access to root nameservers; this only happens if an administrator explicitly removes db.root. If this was an accident, they need to reinstall with --force-confmiss. If not, then their change is preserved as it should be. What purpose would be served by making db.root not a conffile? Albeit, this isn't a grave consideration, but one that make repairing a broken name server a little easier. Because --force-confmiss isn't a very desirable switch to use, because there is no compelling reason to keep db.root a configuration file, and because making this change would make restoring a missing db.root simple it seems that real question is qhy not?.
Re: When bind9 reinstalls, no db.root
On Thu, Aug 22, 2002 at 01:49:39PM -0700, Blars Blarson wrote: In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: because there is no compelling reason to keep db.root a configuration file But there IS a compelling reason to keep db.root a configuration file: alternic I don't use them, but debian shouldn't trash files that a sysadmin needs to change to use them just because they arn't recomended. (See http://www.alternic.org/ for info on alternic. While I have my problems with the way icann runs the DNS, alternic doesn't show signs of being run better, just differently.) Perhaps the file is poorly named db.root - db.internic-root
When bind9 reinstalls, no db.root
I'm confused by the behavior of apt-get install --reinstall. I found out yesterday that the /etc/bind/db.root file was missing on my name server. I was able to recover by linking to an old copy and restarting bind9. However, when deleted the link and performed the --reinstall command, the db.root file was not restored. I verified that the file exists in the bind9 DEB and, in fact, is listed in the bind9.list file. My question is this. How can the reinstall fail to install the file when there is no extant file with the same name?
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 08:24:58PM +0100, Colin Watson wrote: On Wed, Aug 21, 2002 at 12:09:57PM -0700, Marc Singer wrote: I'm confused by the behavior of apt-get install --reinstall. I found out yesterday that the /etc/bind/db.root file was missing on my name server. I was able to recover by linking to an old copy and restarting bind9. However, when deleted the link and performed the --reinstall command, the db.root file was not restored. Sounds like you want dpkg --force-confmiss. I wouldn't expect that since the documentation states: confmiss: Always install a missing configuration file. This is dangerous, since it means not pre- serving a change (removing) made to the file. How could it be dangerous to install a *missing* configuration file?
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 09:42:53PM +0200, Josip Rodin wrote: Sounds like you want dpkg --force-confmiss. I wouldn't expect that since the documentation states: confmiss: Always install a missing configuration file. This is dangerous, since it means not pre- serving a change (removing) made to the file. How could it be dangerous to install a *missing* configuration file? If the default configuration data in the file do something you don't want. For example...
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 10:04:28PM +0200, Josip Rodin wrote: On Wed, Aug 21, 2002 at 12:49:19PM -0700, Marc Singer wrote: Sounds like you want dpkg --force-confmiss. I wouldn't expect that since the documentation states: confmiss: Always install a missing configuration file. This is dangerous, since it means not pre- serving a change (removing) made to the file. How could it be dangerous to install a *missing* configuration file? If the default configuration data in the file do something you don't want. For example... I don't know, but I know plenty of default configuration files that set something up. Maybe dangerous is a bit extreme choice of words, but the negative effect isn't implausible. Without a single example, I don't see how installing a configuration file where there is none can have *any* affect on the system. Admittedly, replacing a configuration file may be undesirable. Moreover, in this case, db.root is not really a configuration file. It is more like a library. If I ask for a package to be reinstalled, most users will expect all of the programs and libraries to be installed. Are you sure you agree that db.root should not be reinstalled with bind's programs? -- 2. That which causes joy or happiness.
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 03:00:52PM -0500, Steve Greenland wrote: On 21-Aug-02, 14:42 (CDT), Josip Rodin [EMAIL PROTECTED] wrote: On Wed, Aug 21, 2002 at 12:32:00PM -0700, Marc Singer wrote: How could it be dangerous to install a *missing* configuration file? If the default configuration data in the file do something you don't want. To be, perhaps, a little more explicit: there are programs for which the existence of an empty configuration file means something completely different than a missing a configuration file[1]. Thus, for dpkg conffile handling, removing a configuration file is a legitimate edit. It would help to have an example. However, even if there is an example I don't see how db.root fits in this category.
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 10:21:17PM +0200, Oliver Kurth wrote: On Wed, Aug 21, 2002 at 12:49:19PM -0700, Marc Singer wrote: On Wed, Aug 21, 2002 at 09:42:53PM +0200, Josip Rodin wrote: Sounds like you want dpkg --force-confmiss. I wouldn't expect that since the documentation states: confmiss: Always install a missing configuration file. This is dangerous, since it means not pre- serving a change (removing) made to the file. How could it be dangerous to install a *missing* configuration file? If the default configuration data in the file do something you don't want. For example... autofs. First thing I do when I install autofs in at networked environmemt is rm /etc/auto.* because I want to use the NIS maps. I don't think that example works for all of the auto.* files. The master file references the other files. Removing the master eliminates the references to the others. However, adding auto.furball won't affect autofs unless auto.master references it. Greetings, Oliver -- Oliver Kurth mailto:[EMAIL PROTECTED] http://leinekanal.de
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 09:21:39PM +0100, Colin Watson wrote: On Wed, Aug 21, 2002 at 01:10:29PM -0700, Marc Singer wrote: On Wed, Aug 21, 2002 at 03:00:52PM -0500, Steve Greenland wrote: To be, perhaps, a little more explicit: there are programs for which the existence of an empty configuration file means something completely different than a missing a configuration file[1]. Thus, for dpkg conffile handling, removing a configuration file is a legitimate edit. It would help to have an example. However, even if there is an example I don't see how db.root fits in this category. Unfortunately there's no way for a package to override this aspect of dpkg's conffile handling. It would have to be handled entirely in the maintainer scripts in some different (and careful!) way. Is the feature triggered for files appearing in /etc? -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 07:06:22PM -0400, Matt Zimmerman wrote: On Wed, Aug 21, 2002 at 12:49:19PM -0700, Marc Singer wrote: For example... _Any_ program whose default (Debian) configuration file specifies options which are different from the compiled-in defaults. For specific examples, see almost any program on your system with a global config file. Hand-waving doesn't constitute an example. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 07:32:04PM -0400, Matt Zimmerman wrote: On Wed, Aug 21, 2002 at 04:23:16PM -0700, Marc Singer wrote: On Wed, Aug 21, 2002 at 07:06:22PM -0400, Matt Zimmerman wrote: _Any_ program whose default (Debian) configuration file specifies options which are different from the compiled-in defaults. For specific examples, see almost any program on your system with a global config file. Hand-waving doesn't constitute an example. How about bash? A missing /etc/bash.bashrc has a different effect than the default /etc/bash.bashrc. A missing /etc/bash_completion has a different effect than the default /etc/bash_completion. Missing /etc/skel/.bash* will avoid having any .bash* files copied into new users' home directories. I think that you have bash installed (assuming you run Debian), so you now have an example that you can experiment with on your own system. And you didn't have to go to the trouble of figuring it out for yourself. You may shut up now. This terse reply is obviously inappropriate. If you are annoyed, stop writing. I was asking for real examples in order to discuss how the case of bind and db.root is *not* a member of that set and how there may be a genuine problem with the handling of installing over missing configuration files. As far as I can tell there is no way to pass --force-confmiss to dpkg when using apt-get. Perhaps this is the only real omission. Still, breaking bind's access to root name servers is particularly troublesome because it may tend to break all net access. It may be worthwhile to remove db.root from the list of configuration files. Especially, because this list isn't something anyone should need to change.
Re: When bind9 reinstalls, no db.root
On Wed, Aug 21, 2002 at 06:39:55PM -0500, Steve Greenland wrote: On 21-Aug-02, 15:10 (CDT), Marc Singer [EMAIL PROTECTED] wrote: It would help to have an example. I could have sworn I had a footnote about /etc/cron.allow, with a reference to the appropriate manpage :-). Okay, it's not the *best* example, because I don't actually ship a cron.allow, but the point is there: A missing cron.allow permits everybody to use crontab, while an empty cron.allow forbids use of crontab by anybody (except root, of course). It does appear that there are a couple of good examples. In fact, this is not one of them since what you ought to ship is a cron.allow that blocks everything, right? That way the default behavior is obvious to someone browsing the configuration. As far as I can tell, there aren't many 'dangerous' examples. A package may install a crontab file in cron.d that is deleted by the user. Apparently, apache2 performs directory scanning for configuration files, too. Examples such as BASH are definitely *not* dangerous since the default file contains a single, innocuous directive. As I wrote in another message, given that there is an override switch in dpkg, that switch would be helpful if available in apt-get.
Re: Removing Packages in Slink for Debian 2.1
On Wed, Oct 14, 1998 at 09:33:22PM -0700, Jim Pick wrote: Brian White [EMAIL PROTECTED] writes: Okay, everybody... It's that time again. I've gone through the bug logs and made my list of packages to keep/remove should they still have release-critical (i.e. critical, grave, or important) bugs at ship time. What do you think we should do with the Gnome stuff? The Gnome 0.30 stuff is still under rather heavy development. The current packages in Slink are pretty much alpha-quality. Lots of things don't work. It sounds like there will probably be a 1.0 release coming up in a few months that will be thoroughly tested and stable. I'm not sure if it's a good idea to release them as a part of a stable distribution, as they really aren't. There aren't any guarantees that the stuff that runs today is going to run tomorrow. I installed it yesterday to get a glimpse at what they are doing. I'd say it should be left out because it doesn't really work. It is a fine demonstration, but it doesn't add value to Debian until it can be used either a) to hack against, or b) to provide a workable desktop environment.
Re: moving mutt-i from non-us to main
On Thu, Oct 15, 1998 at 06:55:36PM +0200, Marco d'Itri wrote: Can I move mutt-i from non-us to main? There is no crypto code in the package, only SHA-1 (hash algorithm) and code to run pgp or gnupg. (Waiting to resolve this issue I haven't uploaded yet the stripped version to main, I hope Brian will let it slip past the freeze, there are no other differences from the complete version.) I was under the impression that putting hooks in to use crypto was enough to raise the hackles of the export hounds.
Re: Removing Gnome [was: Removing Packages in Slink for Debian 2.1]
On Thu, Oct 15, 1998 at 04:02:41PM -0500, Stephen Crowley wrote: On Thu, Oct 15, 1998 at 08:32:02AM -0400, Brian White wrote: What do you think we should do with the Gnome stuff? The Gnome 0.30 stuff is still under rather heavy development. The current packages in Slink are pretty much alpha-quality. Lots of things don't work. It sounds like there will probably be a 1.0 release coming up in a few months that will be thoroughly tested and stable. I'm not sure if it's a good idea to release them as a part of a stable distribution, as they really aren't. There aren't any guarantees that the stuff that runs today is going to run tomorrow. I would agree with you. They should probably be removed from slink at the time of the freeze. Do you have a list of these packages? That is ridiculous, there is no reason to remove gnome before the freeze, if you dont like it dont use it. There are several programs that wont run without it, including GtkICQ which is about the only usuable icq replacement available (if you dont count those crappy console ones) IMHO it is not appropriate to ship beta software under the guise of release software. If it is really desirable to ship gnome, it sould be categorized as ALPHA and installed only when a user explicitly requests it. I think that keeping it on the CD is spurious because the CD represents what we know works. Packages that don't work can be downloaded from the FTP servers by the people who want to fuss with them. Gnome is high profile because it has fancy screenshots. Users who see the packages and install them with the idea that they work will not be treated with the high standard of quality Debian shows elsewhere.
Re: IA32 vs i386
On Thu, Oct 15, 1998 at 02:09:23PM -0700, Kenneth Scharf wrote: The intel version of debian packages are in some directory path downstream from ../../i386/.. and the package names also carry i386. While this is technically correct, it can be missleading to some that the package only runs on an 80386 cpu. The current name for the cpu family from intel (and clones) that are derived from the 386 is IA32. (and intel's next family will be called IA64). Should the package and directory names be changed from i386 to IA32? It is a bit ridiculous to suggest that we change this now. Whether or not it is correct, it is well understood and deeply entrenched. We use i386 because that was the first intel processor capable of hosting a 'real' operating system. The 286 has a p-mode, but it didn't have the memory management. IIRC the IA32 designation wasn't coined until the pentium's were released.
