Accepted rsyncrypto 1.14-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 06 Sep 2017 20:30:22 +0300 Source: rsyncrypto Binary: rsyncrypto Architecture: source amd64 Version: 1.14-1 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh <shac...@debian.org> Changed-By: Shachar Shemesh <shac...@debian.org> Description: rsyncrypto - rsync friendly encryption Closes: 849437 Changes: rsyncrypto (1.14-1) unstable; urgency=medium . * New upstream release. * Fix problems with --trim and --filelist * Fix dependencies on openssl to be >= 1.1.0 (Closes: #849437) * Update watch file to include signature Checksums-Sha1: 9db39840308aa8a0280eb7bf582d26cd34236422 1686 rsyncrypto_1.14-1.dsc da23edab14c366254a52fa16dc4f2d16cf81aa07 405166 rsyncrypto_1.14.orig.tar.bz2 fde31080334c7147cdd98d25653a5adc04d8b277 488 rsyncrypto_1.14.orig.tar.bz2.asc 70df5147c3129bb57ab99f68f1feedd6da72f2d1 29360 rsyncrypto_1.14-1.debian.tar.xz 6c25b7e372d51d270425ceffb4155f520d3f77b3 404980 rsyncrypto-dbgsym_1.14-1_amd64.deb 77af1f40d8e74b79c0721f6642be986eba6b4480 5729 rsyncrypto_1.14-1_amd64.buildinfo d5a77065abb85381bf541b8acd9b2309e4342657 298526 rsyncrypto_1.14-1_amd64.deb Checksums-Sha256: 78631328a4b23806670975411ccd52fe966ac109476d6b11a97462aa0541cfda 1686 rsyncrypto_1.14-1.dsc 4f1e2605449c7d35b69d77bce95cb652a8ba1a0996b3babd776fcc98a5a7deff 405166 rsyncrypto_1.14.orig.tar.bz2 f6727de88f032df09ec74675d8dfea188ffafb8026411b4478ce252c1ee7ad39 488 rsyncrypto_1.14.orig.tar.bz2.asc 1538a87376601317155ca2fe2541496f581a86af9116f0dcf683e2dc408f8546 29360 rsyncrypto_1.14-1.debian.tar.xz 587b0f8cba4140d957270d2892aebe72c3138c05f6c19954fa1d01b377eabb4f 404980 rsyncrypto-dbgsym_1.14-1_amd64.deb 682db3d53dca10ee8264451373aade682ca3d52b2115816b32e7d6707005 5729 rsyncrypto_1.14-1_amd64.buildinfo c7a9c91f1c68c9dcd36fd6272f8aaccba7a83dc92fff14c5ae1480e2bd0620cd 298526 rsyncrypto_1.14-1_amd64.deb Files: 6f60fcd5f6bfe47f644a45a7de93476d 1686 utils optional rsyncrypto_1.14-1.dsc 8c3b4ddbaa9f1d401860e7df3742357f 405166 utils optional rsyncrypto_1.14.orig.tar.bz2 65afc39d72177fa99bb0ae3b49e6b9a9 488 utils optional rsyncrypto_1.14.orig.tar.bz2.asc 14b80ed5484fab7c03b60a6c1f56adb9 29360 utils optional rsyncrypto_1.14-1.debian.tar.xz 6f398c5112c803e87dae0c8cbb716f76 404980 debug extra rsyncrypto-dbgsym_1.14-1_amd64.deb 4c784cd903e4ccc25595d7718baf1015 5729 utils optional rsyncrypto_1.14-1_amd64.buildinfo 7c23271892c98be3cfcdd15c9e7a2e66 298526 utils optional rsyncrypto_1.14-1_amd64.deb -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8tZDpVi5kkwGSSB7oMWtE1nNNlMFAlmwRLIACgkQoMWtE1nN NlNC/ggAivc3sFEGNlFrfhz6zMWSSi4gQtC8tSPCVlu240gyX9f06renESI4sYzr PNNgx6lLGdZDlw9waV71XYFrf7OqbZzLOWSIvfD0OigqeEGcRR2FfY8ViUmU4HN8 I/0r+ouVpsxYEXn/YOMyLHy8zHFZn8LSvBtR3DZDIIU3kLlUNAAUXvB/2jl+G/r/ q+ezB9WSUo/HpUVkLquPZq5O2MFcyRBb9H4YLkB0N5dcjvSrn3OSVtn5XH7kULjJ kIvFijNH2Rb603WSKlrE9KfEfID1/7I7XBRln5p+kDaluoziIEKXbi3x+1vU5fyD miumkJUUfdwa0Wr0q8fR0bmKm+oEOA== =qbTH -END PGP SIGNATURE-
Accepted rsyncrypto 1.13-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 27 Nov 2016 20:26:18 +0200 Source: rsyncrypto Binary: rsyncrypto Architecture: source amd64 Version: 1.13-1 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh <shac...@debian.org> Changed-By: Shachar Shemesh <shac...@debian.org> Description: rsyncrypto - rsync friendly encryption Closes: 828534 Changes: rsyncrypto (1.13-1) unstable; urgency=medium . * New upstream release * Fix "FTBFS with openssl 1.1.0": Added openssl 1.1.0 support (Closes: #828534) * Disabled precompiled headers check, as it wouldn't play nice with dpkg-buildpackage Checksums-Sha1: db457b410d4f905ce2ccd99af96479fecc840f74 1434 rsyncrypto_1.13-1.dsc 9b7cbae45fe556e85c825fef46dc84ba48ace819 405118 rsyncrypto_1.13.orig.tar.bz2 c9640577f61abf0bf16615e03475326ec4609251 84848 rsyncrypto_1.13-1.debian.tar.xz 74fe6a7950c95c0ad0d2d1bfc01446899734f8d4 411496 rsyncrypto-dbgsym_1.13-1_amd64.deb 8e499dcff2aaa9fe68b1cf2e7d5415085d6691c6 5110 rsyncrypto_1.13-1_amd64.buildinfo 040b16f28513bb57a3e9d1474b6f5d2b1fef5390 298784 rsyncrypto_1.13-1_amd64.deb Checksums-Sha256: a67e835802a0ecdc9ad03c3c4729cb346acdcd275c3a3cebf6b8e50b1a163751 1434 rsyncrypto_1.13-1.dsc c12faf6a3c8c91c4e55e6e98327bd4ff1a12860a037193e9701915044c369bc7 405118 rsyncrypto_1.13.orig.tar.bz2 45b579a241a874fbd2e275ad3b20c8f0faa4a421455dab6ee2177045121bf6c7 84848 rsyncrypto_1.13-1.debian.tar.xz 7c612de5751fed873a3373c800ee50d3dcdb725dbac37979680027d3411db42c 411496 rsyncrypto-dbgsym_1.13-1_amd64.deb fa2abcfb41b1603480a3af28e54af666bbd7ab6ac105e77cf7694842708c83df 5110 rsyncrypto_1.13-1_amd64.buildinfo 6dfd2aefecf2b05875031b70223a25d37bb2b0d7558ff344cfad5eb5e131f7af 298784 rsyncrypto_1.13-1_amd64.deb Files: e549d067bec6d12d22ee3c5baf57d069 1434 utils optional rsyncrypto_1.13-1.dsc 631330a386a8e1f54798ba2776bbf7c3 405118 utils optional rsyncrypto_1.13.orig.tar.bz2 bbd9d4b3840525c3f49303fa3ac03f92 84848 utils optional rsyncrypto_1.13-1.debian.tar.xz 88127b417e4607a48d523f91ee9d3e1f 411496 debug extra rsyncrypto-dbgsym_1.13-1_amd64.deb b541c9516d1cb6605af779ba6f6a3876 5110 utils optional rsyncrypto_1.13-1_amd64.buildinfo c1f874ab4316fc1c5e7d55ad2b03816a 298784 utils optional rsyncrypto_1.13-1_amd64.deb -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEE8tZDpVi5kkwGSSB7oMWtE1nNNlMFAlg7LlQACgkQoMWtE1nN NlP08wf/VjdpafXDLeMYV5gkgt8PUBTMFsuN2l37LBqoYpLQzxXXX/2Z9ojUROON ixLr9bNZZjNaIA5uEiTEVcVMkuUENIsnm6toBQ7V+95PWYrdpX+jXMO9oZpSkXf+ VrhJzH9+m0o420gNJ8jODR0uRcvE5X3P+OYmI0smphpL1x20mOlIIfHDdocM0bNj OotcmfemK5GCH4kLxQfarU9y1BD2MYGGVM5CWua49W4xbfPeD8nT8OC9adb1kSwS dYakM/gKzjvSykKScEgY9UhAxwdwlIMS6g9PZpwO2y6O6bA6N7aJM+UHGV2hWocV oybnmJbL9N2TyDJelg2ZTtCs7cPiEw== =aXlE -END PGP SIGNATURE-
Accepted argtable2 13-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 16 Jul 2016 20:45:15 +0300 Source: argtable2 Binary: libargtable2-dev libargtable2-docs libargtable2-0 Architecture: source amd64 all Version: 13-1 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh <shac...@debian.org> Changed-By: Shachar Shemesh <shac...@debian.org> Description: libargtable2-0 - Library for parsing GNU style command line arguments libargtable2-dev - Library for parsing GNU style command line arguments (development libargtable2-docs - Library for parsing GNU style command line arguments (documentati Closes: 643048 805995 Changes: argtable2 (13-1) unstable; urgency=medium . * New upstream version * Add hardening flags to build * Fix "FTBFS: dpkg-buildpackage: error: dpkg-source -b argtable2-12 gave error exit status 2" bug irrelevant after package update (Closes: #643048) * Fix "FTBFS when built with dpkg-buildpackage -A (No such file or directory)" debian/rules changed to only use dh (Closes: #805995) * Update the copyright file to machine readable format * Update policy to 3.9.8.0 Checksums-Sha1: d60fae880028a75acec511cc340fb914bcb000bd 1514 argtable2_13-1.dsc bce828c64c35e16f4c3f8e1f355e4a2a97fe3289 3326444 argtable2_13.orig.tar.gz 762cb42e68e7946b477e04c7cc73a17226576564 7828 argtable2_13-1.debian.tar.xz 85dfc9da2fe250a5cdd68cc63b4709b25329dc5f 29582 libargtable2-0-dbgsym_13-1_amd64.deb 226daaf5ff930d5c5087229a678b71d3b9f55b30 17420 libargtable2-0_13-1_amd64.deb 1b8955469ea04e54de70ea865c93c1c4e3068df8 56916 libargtable2-dev_13-1_amd64.deb 0a239ec3c9b0ef801498dc062fc6598fe6a39e57 2621298 libargtable2-docs_13-1_all.deb Checksums-Sha256: fbde9b03942dcef9568b6df05bb12e5a10efbe650c5cf0b4d91d5f719b6b90f8 1514 argtable2_13-1.dsc 8f77e8a7ced5301af6e22f47302fdbc3b1ff41f2b83c43c77ae5ca041771ddbf 3326444 argtable2_13.orig.tar.gz 51b25043824a09f4def6be785ae4c469d9bf59daa3fc2c0d67485187cd682df8 7828 argtable2_13-1.debian.tar.xz ef14b55cfffc954f35caef42778a05d9bf989494dd9caed5831cd46740af1ec1 29582 libargtable2-0-dbgsym_13-1_amd64.deb cb41f6413828fbc5aeedbf47f3eac64bcd01e4da943a9d9a743829c1144600f1 17420 libargtable2-0_13-1_amd64.deb 870f93a1c996fc5fa1cf8c4b48d0b4bd8086dfc3350768690a6c5f2c2409f4cf 56916 libargtable2-dev_13-1_amd64.deb f4d9b95004a4e2abf1078b314606b3a8ea82cb2374c111da0c6c546e9d08c08d 2621298 libargtable2-docs_13-1_all.deb Files: f07b47b548945212b94ba941ef8e7cc2 1514 libs optional argtable2_13-1.dsc 156773989d0d6406cea36526d3926668 3326444 libs optional argtable2_13.orig.tar.gz 06e7e9193a026e7bf46f9af9b470ca6e 7828 libs optional argtable2_13-1.debian.tar.xz d765be432c88b10166431842040385af 29582 debug extra libargtable2-0-dbgsym_13-1_amd64.deb 94397e533432ad819b15ccad2956e3dd 17420 libs optional libargtable2-0_13-1_amd64.deb b3f448c3a8c1005ab3dccf803194d78f 56916 libdevel optional libargtable2-dev_13-1_amd64.deb 5218cc6a6f4032484e23c1341203cb53 2621298 doc optional libargtable2-docs_13-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJXi6EIAAoJEKDFrRNZzTZTgjgH/i4VHx0a6NIHaoGm0LcvnUWs ASJ0S0/FyvEFP8eqXejXysJ13p5Odi9e0b1Q1+c3sEoPZDAYxLeNmw0iPd2jC2Zm nZlOaKA82MsVwHdMzsgGUHsFgg0plFm3+FO5GJ+Da+jn0EwE/IydMqdYJxEfsksZ +VwBsKWeLCVlL39N/VtwoieDwqmvqW2fZbZ8bO1uvqHR/Z+o+4TmhsYuE4bbtFis 9FtNTgB+M56F8B2LpNzaMpjnjme4A+XPUO7G1tz3FBmDPuqPK9K4tv4dmu26H2Xn yEKTGQlEDlAPYxg4UoQiHtsRxSCF3PfcH4vgWjIBfLka54RsZ6P4Mu0zSsA8aEg= =YOJu -END PGP SIGNATURE-
Policy 12.3: should I rename?
I am working on bringing the libargtable2 package up to date with both upstream changes and the Debian policy. One of the changes state: recommend to ship additional documentation for package |pkg| in a separate package |pkg-doc| and install it into |/usr/share/doc/pkg|. The package currently ships the docs in a package calles "libargtable2-docs" (plural). I am wondering whether I should rename it, and how to do it. As far as I can tell, I have three options: 1. Don't rename. It's only a "recommends". 2. Rename with full transitional package 3. Rename without transitional package The incentive for doing 3 is that the dev package already depends on the docs package, so a transitional package might not be all that important. Another question I have is regarding packaging. The Policy suggests that libargtable2-doc should install the docs to /usr/share/doc/libargtable2. It seems that debhelper is not a friend in that regard, pushing me to install to /usr/share/doc/libargtable2-doc. Am I missing some option that would make that easy? Shachar
Accepted sshpass 1.06-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 02 Jul 2016 05:43:19 + Source: sshpass Binary: sshpass Architecture: source amd64 Version: 1.06-1 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh <shac...@debian.org> Changed-By: Shachar Shemesh <shac...@debian.org> Description: sshpass- Non-interactive ssh password authentication Changes: sshpass (1.06-1) unstable; urgency=medium . * New upstream version * Update copyright file to be machine readable * Update policy to 3.9.8.0 Checksums-Sha1: f8e552971911cfdfdc8aa9789369f9a7c1be2f1c 1353 sshpass_1.06-1.dsc 633652e2160819ac7c7e1a351327027d2faa4fd6 112205 sshpass_1.06.orig.tar.gz d5a674fa5c8fb6967926e35b9930c253d87d5c43 2952 sshpass_1.06-1.debian.tar.xz 720d10b59c3d851ad8709b9414d39b9d61ebfde5 10836 sshpass-dbgsym_1.06-1_amd64.deb 7046e48a14651cc324278b52e976055561ae8895 11278 sshpass_1.06-1_amd64.deb Checksums-Sha256: cfcd5fcb566354899b52134472812966a840d8c3b887545ed6823726a0f60dfc 1353 sshpass_1.06-1.dsc c6324fcee608b99a58f9870157dfa754837f8c48be3df0f5e2f3accf145dee60 112205 sshpass_1.06.orig.tar.gz 7c5d833394625a897b48243fb7af48cc4cf22156742284b8a396938429240862 2952 sshpass_1.06-1.debian.tar.xz 16c1199e0e2005d4f0e0b6c4972b2ac449aaff4ee3ff970f8cb47d36a13bb2af 10836 sshpass-dbgsym_1.06-1_amd64.deb d490e5db91a0dbaf96e12e9af4682c2e6afbd258c7ad3858897baabfc12d2cfe 11278 sshpass_1.06-1_amd64.deb Files: bf097374355360c79189053957db5912 1353 utils extra sshpass_1.06-1.dsc f59695e3b9761fb51be7d795819421f9 112205 utils extra sshpass_1.06.orig.tar.gz 2e665f00d4a24441309885a1425786ef 2952 utils extra sshpass_1.06-1.debian.tar.xz 08fd83b01ccbc0966f865b94e597601f 10836 debug extra sshpass-dbgsym_1.06-1_amd64.deb e843319f7d0649761affe9fcc53957f2 11278 utils extra sshpass_1.06-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJXd2ElAAoJEKDFrRNZzTZTmBAH/3eKwZFA7HD06BY+7U8t7zqP COOmP7Q2z0lDATlAqMdlyl5l/d3giOVv5mSTrbpEPzPbawEPJDC/Fy5S/42Qf9Og H9ZS4AGTDuSQYH+LXxt+QYiWkS0ggh7nJgj75mg7rrPLdXnoTRsek1q7hQdo+MR6 hU3btwHgnUcW9tlEUWGIGvun0AW2DHOv07BjNCFeUnMdHM+HNMZIhPeM11sq9UFU cFeaWA23sCTiccGHYGBwtvTR9aAaVSHiTMPDhb2koxn11IP30chmi+xdUntRnIFx y/t75+Amez0In5JtTn82lNFaKxM573za1M3oeMJsxZQQDlvwPs/n7AWXP+9xlww= =XZiG -END PGP SIGNATURE-
Accepted rsyncrypto 1.12-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 24 Jun 2016 08:48:31 + Source: rsyncrypto Binary: rsyncrypto Architecture: source amd64 Version: 1.12-2 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh <shac...@debian.org> Changed-By: Shachar Shemesh <shac...@debian.org> Description: rsyncrypto - rsync friendly encryption Closes: 817660 Changes: rsyncrypto (1.12-2) unstable; urgency=medium . * Fix "Removal of debhelper compat 4" - packaging brough up to date (Closes: #817660) * Switch to dpkg-source 3.0 (quilt) format * Change debian/copyright format to be machine readable * Add hardening flags Checksums-Sha1: 3e3ed9731f3b9e886b3fdc092e6bcd6c00a3ceee 1416 rsyncrypto_1.12-2.dsc 155a35715fe895b4dfb12838aa45a64c51081b73 83768 rsyncrypto_1.12-2.debian.tar.xz 2f3add197cfbfd30f68409819760add22e53b66d 323916 rsyncrypto-dbgsym_1.12-2_amd64.deb a691c81857ba36e32b46d8220ff6a377f5d4322b 297234 rsyncrypto_1.12-2_amd64.deb Checksums-Sha256: 5ff68186d550319eea3f76ccdea826162ddab7ea7c9ac8b9f743a05386da4992 1416 rsyncrypto_1.12-2.dsc 7d9674d012d0ebbe7542be6fe9fbeff4cfec92146b14d415a22d6d1929df20fa 83768 rsyncrypto_1.12-2.debian.tar.xz 9e7d0649f49e5bdec40b911065b0bd08ed53c46adfcd90a1333de050120d46cf 323916 rsyncrypto-dbgsym_1.12-2_amd64.deb 138d689473f4907a09798c8d3628d893a5933983b79f928d201fadb782233389 297234 rsyncrypto_1.12-2_amd64.deb Files: 597cd4c1cade62c06d1e4bcf213af07b 1416 utils optional rsyncrypto_1.12-2.dsc fdf30565b53a9ec7b9d83c1a6450bbbe 83768 utils optional rsyncrypto_1.12-2.debian.tar.xz 376edb6ef6af79490ab73f54beeea814 323916 debug extra rsyncrypto-dbgsym_1.12-2_amd64.deb ca86b183e07a809815fa01138c9a4a14 297234 utils optional rsyncrypto_1.12-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJXbQy3AAoJEKDFrRNZzTZTnToH/2Y8gyNGslsHC1v+POEDLvxG Xiyy/IkZ70ypcd6iXyrwPawKdwPahQdBwuokfopNIhqRkcJL46Mv1/Ufhp+jkeaK CrN30JurU1fXU8W2ILpBGbDPHHvWqqWd2RLv5jBt0PqBQX3kydTgFe7kvxkP6+Jl k3YTukR1aUwBc19L8Hb0OTP8N7GWQPWisTNpShPxa/15rRov+gr9hgd6ZuGHKz63 MdXJ2/wW1TH7bGOgW9oyn6e8HR9Lvg+mCf5WH4Bi64Oi+LLGHyAxFag+wsZW0z3P lP5DpQSRZRERT42bpyoHG8Yzlbx+pD5oUhBunSUaqQFgHd4XhmACbH7Xth4sjVQ= =9WDH -END PGP SIGNATURE-
Re: Being part of a community and behaving
On 16/11/14 17:16, Scott Kitterman wrote: The cure for inappropriate speech is more speech. Calling people on things that are inappropriate or that cause problems in the project is exactly the right thing to do. I was trying to point out the futility of trying to ask people to show restraint, as calling a (subjectively) innocent joke offensive is every bit as offensive as the original joke. Refrain from stirring the fire by saying it's wrong is backwards. Over a decade ago I worked for a company I will not name. Suffice it to say it is a company producing firewalls. In the course of debugging one feature, I managed to create a RST storm. It is the same as an ACK storm[1], only with RST packets. The discussion here reminds me of those times. I am not telling anyone to shut up. Everyone are free to criticize whatever and wherever. I am merely suggesting that shutting up might be a smarter course of action. Of course, I'm sure there are those who will find my mail offensive, and will be most prudent in letting me, and everyone else, know about it. As such, I promise to henceforth accept my own advice. This is my last email on this thread. Shachar 1 - http://security.stackexchange.com/questions/49827/how-are-ack-storms-created-and-whats-a-good-mitigation-strategy-for-them
Re: Being part of a community and behaving
On 13/11/14 18:22, Tobias Frost wrote: Sometimes, a joke is just inappropriate, regardless how funny it may seem. Sometimes, a joke is better not made, regardless how funny it is. We have enough bad karma these days, no need to pour gasoline on the fires. Civility ism after all, so important to free speech (http://www.popehat.com/2014/09/06/u-c-berkeley-chancellor-nicholas-dirks-gets-free-speech-very-wrong/). I mean, people have the right not to be offended (http://rationalwiki.org/wiki/Freedom_of_speech#Right_not_to_be_offended). I assume we're all adults after all. Including the ones doing the reading? Seriously. You are free to feel the joke was in poor taste. My stake in this particular game is not deep enough for me to think so, but taste is a matter of opinion. Which is precisely the point. Taste is a matter of opinion. Limiting speech to only the things everyone agree are in good taste greatly limits the speech (see first link for in depth explanation of why). I don't think I'd like this forum to regress to that point. I'd say more, but I just feel like I'm repeating what the two links I provided are saying. I suggest we do, indeed, act like adults. Please try to refrain from jokes other will find offending. If you see such a joke, please try to refrain from stirring the fire by saying it's wrong. Just, you know, be adults... Shachar
Gcc and undefined behavior
Just a quick FYI for anyone who missed it. Following the discussion from a few days ago about Cava (C like language with no undefined behavior), gcc 4.9 is now out[1]. One of the changes there is a runtime check for undefined behavior. Just compile with -fsanitize=undefined, and your program will crash with log if it performs an operation that C/C++ considers to be undefined. Have not tried it myself, but feedback would be great. Shachar [1] http://gcc.gnu.org/gcc-4.9/changes.html
Re: Having fun with the following C code (UB)
On 15/04/14 19:45, Jakub Wilk wrote: * Thorsten Glaser t...@mirbsd.de, 2014-04-15, 11:24: we need to go further. We need a programming language (with at least two compiler implementations), which I will call Ͻ, that looks like C so much that *every* C program¹ is also a valid Ͻ program, and *every* Ͻ program that does not make use of the additional guarantees (i.e. no C UB) is also a valid C program. […] find a non-sucking name that is ISO 646 IRV, Let's call it Cava. If we didn't have C, we'd all still be writing in obol,.pasal and basi. Oh, and Fortran, of course. Shachar
Re: Having fun with the following C code (UB)
On 13/04/14 06:32, Russ Allbery wrote: Like I said before, I am not against the compilers warning about such cases. I just think that these warnings need to be done very carefully, or they become worse than useless. As such, if you see a case in which you feel gcc (or clang, or whatever) should warn, by all means open a bug for it. Just make sure you make it a feature request and not a security hole severity. In other words, don't get mad merely because the compiler author did not read your mind. I'll be sure to keep that in mind, since I've never reported a bug or discussed issues with compiler writers before. No issues with most of what you said. It boils down to this: Different people write in C/C++ for different reasons, and therefor have different needs. I think the compiler writers are doing what they can, but there really is no pleasing everyone. Personally, I simply try to have my code compile on as broad a range of compilers as I can, and thus enjoy their combined warnings. The thing about the above is this. In the past, we've seen some people really explode over these issues. I think this is incorrect. The bug is, when all is said and done, in the code. While it's perfectly acceptable, in my eyes, to ask the compiler to help you find that bug, getting mad at it for not doing so makes no sense. Shachar
Re: Having fun with the following C code (UB)
On 12/04/14 23:38, Henrique de Moraes Holschuh wrote:
On Thu, 10 Apr 2014, Shachar Shemesh wrote:
I never did understand what people expect. gcc uses the undefined
Warn the hell out of any line of code with per-spec undefined behaviour, if
not by default, at least under -Wall.
I have no argument with that, in those places it is possible.
I will point out that it is not always is possible, and is quite often
not easy. For example, the famous undefined after NULL dereference
would probably cause a warning every time a function uses a pointer it
was given without first validating its non-NULLness.
THAT would be a good start. Too bad not even gcc knows every time it hits
undefined behaviour...
My understanding of things is that undefined behaviors are fairly
common, and almost always benign. Look at the following code:
int add( int a, int b )
{
return a+b;
}
Do you really want to get a Warning: signed integer overflow yields
undefined behavior on this function?
Shachar
Re: Having fun with the following C code (UB)
On 13/04/14 05:39, Russ Allbery wrote:
One can make a good argument that such checks are exactly what you should
be doing.
Then the answer is very simple. Write in Java.
My understanding of things is that undefined behaviors are fairly
common, and almost always benign. Look at the following code:
int add( int a, int b )
{
return a+b;
}
Do you really want to get a Warning: signed integer overflow yields
undefined behavior on this function?
I would certainly like to be able to enable such a thing. I write a lot
of code where I'd love the compiler to double-check that I've established
bounds checks on a and b before doing the addition that guarantee that it
won't overflow.
I am not a compiler writer, so I have no actual data. I suspect your
common 20k line will yield about a thousand such warnings, the huge
majority of which there will be nothing for you to do about.
Also, it turns out gcc does have such an option. See
http://www.airs.com/blog/archives/120. -Wstrict-overflow will let you
know when the optimizer uses the assumption of no overflow to change
other code.
Put a different way, the answer to your question is quite different if
that function were instead:
int compute_offset_into_network_packet( int a, int b )
{
return a+b;
}
No?
In most cases, you will overflow the packet long before you overflow the
integer. If that's the case, the compiler won't help you. There is a
good case to claim that the warning would be appropriate for the
following code:
int compute_offset_into_network_packet( int a, int b )
{
int offset = a+b;
if( offset0 || offsetPACKET_SIZE )
offset = 0;
return offset;
}
But, then again, what should the warning be? Like I said before, if you
don't like to deal with overflows, use Java and take Java's performance
hit. In fact, most of the world is doing precisely that.
Like I said before, I am not against the compilers warning about such
cases. I just think that these warnings need to be done very carefully,
or they become worse than useless. As such, if you see a case in which
you feel gcc (or clang, or whatever) should warn, by all means open a
bug for it. Just make sure you make it a feature request and not a
security hole severity. In other words, don't get mad merely because
the compiler author did not read your mind.
I don't know whether -Wstrict-overflow is on for -Wall (or -Wextra). If
it isn't, I do think it should be. Just checked, and it is on for -Wall,
sort of. See http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html.
Shachar
Accepted fakeroot-ng 0.18-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 12 Apr 2014 16:34:11 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source amd64 Version: 0.18-4 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.18-4) unstable; urgency=medium . * Remove /dev/shm. Again. * Rebuild to support yama debugger scope (no change in source) Checksums-Sha1: 4c2f6e9ae37bfd33e60e6ea960f1b10fe0f9d784 1443 fakeroot-ng_0.18-4.dsc 28f508c94cc2bd736b588a4124c7a800da675335 4540 fakeroot-ng_0.18-4.debian.tar.xz aabb8430fd7df451e9a6e6deba89a964b2db3f96 58162 fakeroot-ng_0.18-4_amd64.deb Checksums-Sha256: 1e99296e6456a2beb1d10b4756d61cacf0eb4680bfa77fbe51b7574295caad76 1443 fakeroot-ng_0.18-4.dsc 70f5c4c302ba2012388f28354b05243fce9ebe141c7b6d880fd22c6a48fd365f 4540 fakeroot-ng_0.18-4.debian.tar.xz 3b9b2add55096a715656e132b843d316244515e7acc6d81262de641370fad057 58162 fakeroot-ng_0.18-4_amd64.deb Files: 0dcf20161297254d3e4f419d89b66490 1443 utils extra fakeroot-ng_0.18-4.dsc 9a49cc5ef7f90f37bbe6588413488580 4540 utils extra fakeroot-ng_0.18-4.debian.tar.xz 262a88e560c2dd7a6de8586b176c03bf 58162 utils extra fakeroot-ng_0.18-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTSW2QAAoJEKDFrRNZzTZTqfAH+wb+jQxJjLzLfWO8RCGPOZDt QSHMQ19FHOAJCQRwx4TYhVCGHqoYzTSiyGssloSwlSAjFRuvXxFsdDKzRz3zNeYb JT0QRKAHFRxuT1ywK0x25/QvLnUjKf2zlbeYL2EFjoCS3XhYS/DV31NBVVlorNKi R4W0hRs6sRB/9G/H0ny/mqq53Hy9PqN3Kbji5wq3vcYod6o6zSzCZ/Pv2s9JzRzv fiG4+H+2sdRfjKsYFrdvJsZ7XehRVwPtgZKXHxiivJws+4Y9lZgIImeVxYSLSq3C KB4auSnt5Xyh8lGJ10O9hKlnJHmk7Rc+XjYSPQhW4lbI5wRQAFVUcI4CbAJAbO0= =apfO -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/e1wz16w-00031z...@franck.debian.org
Re: Having fun with the following C code (UB)
On 11/04/14 13:49, Ansgar Burchardt wrote: Hi, On 04/11/2014 12:42, Ian Jackson wrote: What people expect is that the compiler compiles programs the way C was traditionally compiled. Shouldn't -O0 come close to that expectation? I think that Ansgar's answer is spot on, but against all good sense, I still want to expand it. Neither the compiler nor its authors are doing anything out of spite. It is, indeed, painful when a compiler optimizes away a security check due to some standard defining a feature to be undefined behavior. However, for any such case there are hundreds in which this optimization saves on an if that would strain the branch prediction cache, or allows coalescing operations that would otherwise need to be done one after the other, or any number of other cases in which the output machine language looks nothing like your written high level C or C++. Not only is this good for performance, it is also good for security. For example, in C++ I can run the following code: for( unsigned int i=0; isize; ++i ) vector1.at(i) = vector2.at(i); at is better than square brackets, because it does bounds checking. I think you'll agree with me that bounds checking is good for security. Running this code as written, however, results in too many bounds checking. Luckily, the same compiler optimization that angered you will now realize that the bounds only ever need to be tested once. The result is machine code that looks nothing like my C++ source, but which does things both quickly and securely. The quickly part is important. If I had to actually run the bounds checking each and every time, this code would, likely, be too slow to be practical. I would, then, have no choice but to use the version that does not do bounds checking. I'd like to hear how that would make my code more secure. Alternatively, I might re-write the loop. This loop is relatively easy to write with explicit bounds checking, but explicit bounds checking has two major disadvantages: 1. It is easy to forget to do it correctly (see the heartbleed problem) 2. It makes the code less readable and less maintainable. Both of those problems, again, translate to less secure code. I, for one, accept the extra liability that modern optimizers provide in exchange for the easier to maintain, more secure code they allow me to write. Shachar
Re: Having fun with the following C code (UB)
On 10/04/14 20:59, Ian Jackson wrote: Vincent Lefevre writes (Re: Having fun with the following C code (UB)): On 2014-04-10 11:48:44 +, Thorsten Glaser wrote: And GCC is a repeat offender which actually does do that. If you don't like that, you should use the -fwrapv option. Sadly that doesn't deal with all of these malicious optimisations. I never did understand what people expect. gcc uses the undefined behavior to not emit checks it would otherwise have to, so that your code runs faster. This affects not only those corner cases, where you are relying on this behaving a certain way, but especially in everyday code, where those undefined behavior allows GCC to save you lots of cycles. Are you really sure you want to have slower code just so that your corner cases are easier for you? How is that a reasonable trade-off to make? Shachar
Re: stop posting useless cruft and get to work (systemd and Linux are *fundamentally incompatible* - and I can prove it)
On 26/03/14 17:13, Kevin Toppins wrote: I am going to have to respectfully disagree with you on my post being useless. With the hope of contributing constructive criticism, I'll answer that. As far as the systemd vs. upstart discussion, I was leaning in upstart (more precisely, against systemd). As such, your email was very interesting to me. Unfortunately, it was unreadable. You said you'll start with background, but instead of providing technical background, you provided meaningless and irrelevant he said, I said arguments. Trying to skim ahead to find where the meat starts did not easily detect such a point. At this point, I simply assumed the email had nothing more to say. If I'm wrong, feel free to answer with the technical gist of your arguments. If you want me to read it, please adhere to the following guidelines: * No more than one page. * No *asterisks* and - arrows. * No references to previous discussions, or other people's arguments for/against systemd. I believe in free discussion. As such, feel free to ignore these suggestions, just as I'll feel free to ignore your email if you do so. Shachar
Re: Valve games for Debian Developers
On 23/01/14 13:45, Richard Hartmann wrote: The risk of any outsider to become a DD for this offer alone is slim to none. You're forgetting the free LWN subscription. Shachar
Specifying a C++11 compatible pre-dependency
Hi all, I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Is there some better way to cause the system to use a C++11 capable compiler? Shachar P.S. I no longer have a PowerPC platform to test with, and qemu-user isn't emulating deep enough for fakeroot-ng to work under (and is extremely buggy for PowerPC emulation anyways). As such, the best I can tell at the moment is that under ppc, when specifying gcc-4.8 compiler, the code compiles. 1 - http://packages.qa.debian.org/f/fakeroot-ng.html
Specifying a C++11 compatible pre-dependency
Hi all, I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Is there some better way to cause the system to use a C++11 capable compiler? Shachar P.S. I no longer have a PowerPC platform to test with, and qemu-user isn't emulating deep enough for fakeroot-ng to work under (and is extremely buggy for PowerPC emulation anyways). As such, the best I can tell at the moment is that under ppc, when specifying gcc-4.8 compiler, the code compiles. 1 - http://packages.qa.debian.org/f/fakeroot-ng.html
Accepted fakeroot-ng 0.18-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Apr 2013 08:09:46 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source amd64 Version: 0.18-3 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.18-3) unstable; urgency=low . * Failed to specify gcc dependency (needs =4.7) * Update the home page Checksums-Sha1: 59016940a006a0776c7f2c4ec487bcf0b54bdf21 1420 fakeroot-ng_0.18-3.dsc 8d8495988d05648abf281ffd71b872a4c55393a8 4681 fakeroot-ng_0.18-3.debian.tar.gz eb1d7e37432e3a8da208bb03e7eb3465a2498fae 70360 fakeroot-ng_0.18-3_amd64.deb Checksums-Sha256: 5994900f9cbcf5413ae4dadf1e6cb21832da308c507c22c93446477753973e42 1420 fakeroot-ng_0.18-3.dsc 027942778f0255a1f55d0bdbd6b2b66af148fdbf7a981dbb05fcbeb9577b3055 4681 fakeroot-ng_0.18-3.debian.tar.gz 0a527086febfc8e22a5a8599de5addc10268e5abeccbb66d8b1f44fb361f1631 70360 fakeroot-ng_0.18-3_amd64.deb Files: 0ef9059a79c9ebfc9276a3feb7988664 1420 utils extra fakeroot-ng_0.18-3.dsc 3f061f4e87354e1e42faf66214d4be51 4681 utils extra fakeroot-ng_0.18-3.debian.tar.gz 36380a215a00936633261aa4d289d8c3 70360 utils extra fakeroot-ng_0.18-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJRaRgXAAoJEKDFrRNZzTZTA5EH/1A/uDKuhsxq+rCATKTEi9m6 jqUIyCBO0cyLZYOWqJiszfeqNrwA94vUuzW5YcCBpOQkUzZMv6jJG5/VFiyp9fPD JW5MpxhSSefI/cKApj1OZ2SRX3EQEN9b8cCFjK1RWNPag2UUy+1NDHqAN4ezvcwY dg3DWl6bFPeAn/DIm1Bm+qpFfWfDq6pq3FCA+x8Zs0ZB2OgU/Bdk0zLczt0hdePi FMqbtrPCXgzVbjCsRdSDzRVI7rDbaeQqIi5LJyKx6uzuNWTzY9eI3M0nJY+m5jIP RDy/id8gn68V5NemFQfwuX4o9uBGixxuJLYOPv2YEDga5F7Uy7Mg2NC9MnVjF7U= =vPi5 -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: http://lists.debian.org/e1uqw7g-0007ki...@franck.debian.org
Accepted fakeroot-ng 0.18-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Apr 2013 13:14:05 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source amd64 Version: 0.18-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Closes: 566026 701451 Changes: fakeroot-ng (0.18-1) unstable; urgency=low . * New upstream version * Fix debhelper: dh_fixperms fails when it tries to run chmod fixed bug in fchmodat implementation (Closes: #566026) * Fix ftbfs with eglibc-2.17 Problem was probably with gcc 4.8 rather than eglibc itself. (Closes: #701451) * Fixed problem with threads support Checksums-Sha1: 24603b65c0ff899ff82dbe626397f096c34ad15c 1388 fakeroot-ng_0.18-1.dsc 288dadbd50ff36a9eb11d4bc14213c6d1beaafaa 207870 fakeroot-ng_0.18.orig.tar.gz c9fa6ce8faff6f2e9686606ea3580eb7ea35bff4 4037 fakeroot-ng_0.18-1.debian.tar.gz a9afe815264b149db101a6e9d5a019335d861903 70344 fakeroot-ng_0.18-1_amd64.deb Checksums-Sha256: ce27ee158944b0d7bc863b2f01bc154015446263b703b35ad6b83956390685fc 1388 fakeroot-ng_0.18-1.dsc 189eacda630752980d40e34b2c01ce23d839daab3d691a4706bb9eac79f7e144 207870 fakeroot-ng_0.18.orig.tar.gz 3eb76f0ee7b8ae423aadabf1618d7c005b8f3f4cfafd5290148e8c3b3d5a733e 4037 fakeroot-ng_0.18-1.debian.tar.gz e2889de1848e853b1c669e837df654910aa7e56003ab7798dda5dcdc809a2d81 70344 fakeroot-ng_0.18-1_amd64.deb Files: e6310f1c80fd4c87495413a11cbfd17f 1388 utils extra fakeroot-ng_0.18-1.dsc 7bdfd3a72d00b4847e2023d922c289fa 207870 utils extra fakeroot-ng_0.18.orig.tar.gz 9f5a7d4d6d5a9ff2dbf85e1df20532fb 4037 utils extra fakeroot-ng_0.18-1.debian.tar.gz 7aad4cd296c1f6eb24b08b616c9966f0 70344 utils extra fakeroot-ng_0.18-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJRaCwcAAoJEKDFrRNZzTZTvt4H/2x5tzICc/O2SMbUJ6Q0LFEN XxrbHifbQFKY/1p04uYDG9wAdajSXvTl8Kz7KVIUeVFjycu3SpUOUXw4Og0lO5we sibAoFULjnWTdDuOXXUuiJnXW4IzPInf4JlDVt2cXQ3jtBwEdU9HeoBo1OG+R0Dm GLod/jKvuOoIaMOAKDn6Sx1LaD5Bl/crzuuMYLkTx/m2uPpvgigIPdWohJktGypJ +9VoszVZlWcVYJsjOetEtNHcWeWMhJXJhi3qLcLoyQWJwVAXbAS+W1andxYvjH0f PcUPCviXiZFRiwUVU88Gq/HaQ2rXHHtOHhSJMD8gYPKHRM1Ri9MRUv7e9CroNis= =f8rU -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: http://lists.debian.org/e1uqgqs-0004kf...@franck.debian.org
Accepted fakeroot-ng 0.18-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Apr 2013 17:26:11 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source amd64 Version: 0.18-2 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.18-2) unstable; urgency=low . * Regression - fakeroot-ng uses /dev/shm again * Broken build on 32bit platforms Checksums-Sha1: 363e755c58841809415237835ee933ae6150ce11 1388 fakeroot-ng_0.18-2.dsc 49654adefb9d2e1e982045300a2b6c70b5203cea 4588 fakeroot-ng_0.18-2.debian.tar.gz 056f781eaa8b5de7e56b856e98bf7ce569d1e773 70430 fakeroot-ng_0.18-2_amd64.deb Checksums-Sha256: f1624c20edd729137faaa44498aa71f219b7dcbf52a9bbfe54fff726cc1d5284 1388 fakeroot-ng_0.18-2.dsc 0a20862f05dd606853cb97788a0c4d7f16026ddb79ef9fd621f61c7fda8a 4588 fakeroot-ng_0.18-2.debian.tar.gz 624028e61b8d78d5e7536abc88edc2f1c96657b16c1d919f1b3e543ee4ab3024 70430 fakeroot-ng_0.18-2_amd64.deb Files: 128520b4a823f4787b7d5fe6330d7285 1388 utils extra fakeroot-ng_0.18-2.dsc 718d1e952ce495ee3d0bf6e02181efaf 4588 utils extra fakeroot-ng_0.18-2.debian.tar.gz a86569002fd84f78780d4d1fcd59fe91 70430 utils extra fakeroot-ng_0.18-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJRaFWPAAoJEKDFrRNZzTZTroUIAIzwhDXkopAA6oGhNhUaeKSi SMKEAz2bUEBHWWfiibM+A+g+h7kiKwCcDYDnP/SPWLpAwz4NZCQU5MeFi6TAWESj fRFgLMX1oWicVCXuGOC2IG7Jd7aqDLjkx6DLmLd23GVvuER1j+D0qQzpIK74+FnL UQwvKKhA2GClit7J5kn3Z4TzANMEwCprJ+AESywbVi+oSEKd6lYzvCUCrY4FA4sg o7uBdSN3GFAjCtW1mt6LU1F3loyhNSdeIERXfpdJcPQtTUkeo56hT0DmkCPdoCzd HDPAY6BIxscWzQ+npNSovpjNoULaEesZ79LKula59LHEyOYQli5TL6VCQL4In3o= =WLx2 -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: http://lists.debian.org/e1uqj0e-0006dh...@franck.debian.org
Accepted sshpass 1.05-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Aug 2011 20:23:50 +0300 Source: sshpass Binary: sshpass Architecture: source amd64 Version: 1.05-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: sshpass- Non-interactive ssh password authentication Closes: 616565 636039 Changes: sshpass (1.05-1) unstable; urgency=low . * Fix sshpass -e not working any more with openssh-client: A different workaround for the EIO on PTY problem. (Closes: #636039) * Fix Segfault when calling with no argument: Problem did not reproduce, but print usage when run without parameters anyways. (Closes: #616565) * Switch to dpkg-source 3.0 (quilt) format * Policy update to 3.9.10 (no changes needed) Checksums-Sha1: 23f5517d33dda2da83ad4d2effaa0bb67e319998 1322 sshpass_1.05-1.dsc 6dafec86dd74315913417829542f4023545c8fd7 98362 sshpass_1.05.orig.tar.gz d9dc41734062c6f4faced35c800a5943ebb9b767 2704 sshpass_1.05-1.debian.tar.gz 455f0daff3b79599b958c39eab310462d2815d69 11246 sshpass_1.05-1_amd64.deb Checksums-Sha256: 3a47c51af141f474d7584ac738edfdff76888da169e983ed409d21ecc8e005ac 1322 sshpass_1.05-1.dsc c3f78752a68a0c3f62efb3332cceea0c8a1f04f7cf6b46e00ec0c3000bc8483e 98362 sshpass_1.05.orig.tar.gz 22332fc4cd559633121894eb3c54982f3004163a845053c0655b454c0b220c60 2704 sshpass_1.05-1.debian.tar.gz f79290ed742f5ff1a078148a229dd712f8ca3f2237717ab4942281b4e3f6c3e1 11246 sshpass_1.05-1_amd64.deb Files: 494df7e0cccaf4b6607daa010a734120 1322 utils extra sshpass_1.05-1.dsc c52d65fdee0712af6f77eb2b60974ac7 98362 utils extra sshpass_1.05.orig.tar.gz c1d42d1dcc59689695edc19e04d3b54f 2704 utils extra sshpass_1.05-1.debian.tar.gz 801945628cdb7b0d284a6503c5ad2f9d 11246 utils extra sshpass_1.05-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJOPZZUAAoJEKDFrRNZzTZT8w0H/RLDg9PZeIDu55bSiRFJeLbQ YB/AyUQIPZcODtZWPOXlb3xfCf8WELnPanNj0kEsN/EAlOjphMnlYZASmV/Zf2kG 3cd7UqB36WseJmXJ5v8WIo15J4iCz+T6XhRg7MKLZYC9YR/OW5fILIo81JEkVjoZ JpFiN8OXvod3snTST6XlzNpu4/adV0HE7qI7AHvJHMWuuOOkJuBpypdxl7FkcFDg yisrQoAXDz/B6W5c8XO6BhXzPbHI78RKT9/YWZuOk4zegADTmdAlNa+oNCeM7i8X S9BqszhFRl6K5q4o2GRCV67ynVX+ePlkXn6UMBxbVsiaHEmzM4jmVh7lHcKYwPY= =dsBs -END PGP SIGNATURE- Accepted: sshpass_1.05-1.debian.tar.gz to main/s/sshpass/sshpass_1.05-1.debian.tar.gz sshpass_1.05-1.dsc to main/s/sshpass/sshpass_1.05-1.dsc sshpass_1.05-1_amd64.deb to main/s/sshpass/sshpass_1.05-1_amd64.deb sshpass_1.05.orig.tar.gz to main/s/sshpass/sshpass_1.05.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/e1qpmql-0005np...@franck.debian.org
Re: oops I sent a courtesy copy in violation of the code of conduct
On 13/03/11 08:19, Ben Finney wrote: Shachar Shemeshshac...@debian.org writes: Personally, I think the code of conduct should be amended, along with the list software. While this shouldn't turn into a counting of popularity, I'd like to register that there are people who think the list behaviour currently (leave the Reply-To field untouched) is correct. Never mentioned Reply-To, don't think Reply-To munging is correct, and don't understand why you brought it up. When talking about change to the list software, I was referring to the Avoid duplicates option, discussed below. I am subscribed to lots and lots of mailing lists. All mail from those lists gets automatically delivered to dedicated folders automatically. This means I'm highly likely to miss a reply to my own emails to the list unless I get another, direct, copy (which doesn't have the list hidden headers, and therefor stays in my inbox). I *like* to get two copies, as it increases the chance that I actually get to see the replies to my own emails. If you like to get two copies, why can't you arrange to generate the extra copies you want without involving anyone else's configuration? Any suggestions on how to do it? Conversely, I *don't* want any message to the forum to also be sent to me individually via email. In some cases that's because the individual message arrives first, is often read first, yet is the one that I want to avoid receiving. No filter can help with that, since it has no “other copy” to work with at the time it's needed. In other cases that's because I don't participate in the forum via email at all, so I don't want to receive any messages in that forum via email. I'm not trying to start an argument here, but I will point out that disregarding unwanted messages is easier to do with filters than generating new ones (and, more importantly, automatically figuring out for which messages duplicates should be generated). I understand and respect the fact that other people, due to using a mail client that does not allow filtering based on hidden headers, because they are only subscribed to a couple of mailing lists, or for whatever other reason, do not appreciate the extra copy. The problem is that I cannot tell them apart. Why do you need to tell those classes of people apart? Why is being unable to tell them apart a problem? As an example - the list charter clearly states that if someone indicates they wish to receive a copy you should CC him. I do not think I could have more clearly indicated my wish to do so than in my previous email, and yet you didn't. The reason I need to tell those apart from those is because that's what the list's charter says I should do. This is impossible to follow, and therefor should be amended. Since the default for all non-mailing list communication should be reply to all (after all, if someone decided to CC a third party on a conversation they started with you, it's a bit impolite to cut said third party off from the reply) I object to this idea quite strongly. The “forgot to include someone” mistake you identify is easily rectified after the message is sent; the “included someone whom I didn't intend” is impossible to rectify after the fact. For that reason among others, “reply to all” should not be the default but should be a deliberate decision in each instance. I totally accept that argument in the context of automatically adding reply to to lists, but not as a code of conduct for email at large. This is why I specifically said non-mailing list communication. If I wrote you an email, and thought it necessary to CC someone, then this discussion is obviously part of a discussion said someone need to be aware of. It would be impolite of you to exclude him from your answer unless there is a good reason to do so. In other words, the default (not the software's default - your default as a human) should be to reply to all. There is a growing trend to make hitting reply to all illegitimate under any and all circumstances, which I think is in error. The solution I propose is already implemented in mailing list software such as mailman. In it, there is a per-user settable flag called avoid duplicates. I'm not a “user” recognised by the mailing list servers of many of the forums in which I participate, so your proposal is not a solution for my case. I know I'm not the only one who participates in Debian (and other) mailing lists as non-email forums. But I believe that this is also something that can be resolved using technical means. I think the current policy is unnecessarily complex if followed, and in practice is not followed at all, leading to sub-optimal behavior. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas
Re: oops I sent a courtesy copy in violation of the code of conduct
On 13/03/11 11:29, Andrei Popescu wrote: Any suggestions on how to do it? By setting 'Reply-To:' appropriately, this is what it's for. If I set reply-to to myself, the mail won't go to the list. If I set it to the list, it won't go to me. Either way, the desired effect isn't achieved. Also, reply-to is the wrong tool for this job (this is NOT what it's for), as it prohibits distinction between replies to the list and reply to me. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d7d04b9.2050...@shemesh.biz
Re: oops I sent a courtesy copy in violation of the code of conduct
On 13/03/11 20:55, Andrei Popescu wrote: At least with mutt I distinctively recall it replied both to the list and CCd the poster on list-reply. That is a specific Mutt work around for broken lists that add reply-to automatically. It is not generally available. Not sure about other mailers though and you could also set Reply-To: to both the list and your address. A. I'm not at all sure what the standard says about multiple Reply-To: headers. I don't think they are supported B. Even if they are, they still don't allow people to reply privately. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d7d9e6f.1060...@shemesh.biz
Re: oops I sent a courtesy copy in violation of the code of conduct
On 12/03/11 05:14, jida...@jidanni.org wrote: Therefore perhaps http://www.debian.org/MailingLists/#codeofconduct could be amended to mention that adding a Mail-Followup-To header might add an additional wall of defense for those who wish to cut down even further the possibility they might receive a courtesy copy from the less technically adept. Personally, I think the code of conduct should be amended, along with the list software. So far, my research shows that the difference between people (like myself) who prefer to get the two copies and people who don't does not depend on level of technical knowledge, but specifics of method of reading the lists. I am subscribed to lots and lots of mailing lists. All mail from those lists gets automatically delivered to dedicated folders automatically. This means I'm highly likely to miss a reply to my own emails to the list unless I get another, direct, copy (which doesn't have the list hidden headers, and therefor stays in my inbox). I *like* to get two copies, as it increases the chance that I actually get to see the replies to my own emails. I understand and respect the fact that other people, due to using a mail client that does not allow filtering based on hidden headers, because they are only subscribed to a couple of mailing lists, or for whatever other reason, do not appreciate the extra copy. The problem is that I cannot tell them apart. Since the default for all non-mailing list communication should be reply to all (after all, if someone decided to CC a third party on a conversation they started with you, it's a bit impolite to cut said third party off from the reply), I think the current internet trend to treat the use of reply to all as a mistake is misguided. The solution I propose is already implemented in mailing list software such as mailman. In it, there is a per-user settable flag called avoid duplicates. If it is set, if the mailing list detects that a CC or To recipient is also a mailing list subscriber, that subscriber does not get mailed a copy of the mail. This allows everyone to always hit 'reply to all', and have those who wish to receive an extra copy get it, and those who do not (such as most other subscribers to this list) not. I should point out that several mailing lists I'm subscribed to where this topic was a constant cause of bickering among the mailing participants switched to mailman, and the result was quiet on the 'reply to all' front for several years now. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d7aea4c.2060...@debian.org
Re: potential MBF: first alternate depends not available in main
On 02/03/11 12:45, Paul Wise wrote: On Wed, Mar 2, 2011 at 5:53 PM, Emilio Pozuelo Monfortpo...@debian.org wrote: If you have non-free enabled and install a package from main, it should install the dependencies from main. So you should have e.g. rar | rar-nonfree instead of the other way round. non-free stuff shouldn't be in main depends at all IMO, even as an alternative. Then please state what you think should happen in the case pointed out by Emilio. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d6e2409.20...@debian.org
Re: discussing upstream software on -devel (Re: Bug#614601: ITP: libsafewrite -- Simple functions for performing safe atomic replacement of files
On 23/02/11 12:23, Holger Levsen wrote: Hi, On Mittwoch, 23. Februar 2011, Shachar Shemesh wrote: Giving feedback over the upstream trustworthiness is not the purpose of ITP bugs, oh, hell yes, it is. Where else should we discuss what software fits into Debian? debian-qa@ when it's too late? Sorry. I phrased it wrong. I committed a largish change to git and then tested when I had the chance (a few days later). Upon testing, I used the wrong variable in a couple of places, which obviously caused things to not work. I committed this with the log message Fix bugs a few small bugs. Redundant word aside, the word small is what brought The Wrath of Ben on my head. Don't get me wrong. After the initial instinct to flame subsided, I didn't mind that much. I got a bunch of comments, about 50% of which were actually useful to some degree (all of which are already fixed), and I learned something about the Linux kernel that I didn't before. If a maintainer's decision to relate to the size of the fix rather than the size of the consequence is a reason to boycott a package from Debian, then do let me know, because as things stand I intend to continue with the submitting process. and I have been warned by the list masters that discussing a specific package's upstream bugs on Debian-devel is off topic. I dont think this is neither true nor what they said. Surely a discussion about upstream bugs can become off-topic on debian-devel though. I'm sorry, Neil, but I'm quoting your message almost in full. Neil Williams sent me the following on January 3rd, regarding the previous thread about safewrite: Please remember,debian-devel@lists.debian.org is for discussion between Debian developers about issues within Debian (like problems within groups of packages or with particular tools), it's not intended for individual source code project development. This issue is general filesystem/programming issues, it is not Debian specific. Please can you find / setup a list for this project and move the discussion elsewhere from here on? If you want to keep it within the realm of source code related to Debian, an Alioth mailing list would be better. To which I replied that I cannot terminate an already running thread, and the setting up a mailing list for a project which is likely to reach maturity in a couple of versions is a bit of a waste, but that I'll try to wind down the discussion thread. I'm assuming that his lack of response indicates that he found my answer satisfactory. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d675de4.4050...@debian.org
Bug#614601: ITP: libsafewrite -- Simple functions for performing safe atomic replacement of files
Package: wnpp Severity: wishlist Owner: Shachar Shemesh shac...@debian.org * Package name: libsafewrite Version : 1.00 Upstream Author : Shachar Shemesh shac...@lingnu.com * URL : http://www.lingnu.com/opensource/safewrite.html * License : MIT Programming Lang: C Description : Simple functions for performing safe atomic file updates Safewrite is a library for simple, almost drop-in replacement to the usual open and close calls. Using safewrite, however, guarantees that the files be updated in an atomic way - anyone trying to read the file is guaranteed to get a complete version, either the old or the new, but never a partially updated file. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110222144115.9844.58744.report...@dellosun.office.lingnu.com
Re: Bug#614601: ITP: libsafewrite -- Simple functions for performing safe atomic replacement of files
On 22/02/11 19:54, Ben Hutchings wrote: Judging by what you consider 'small bugs' in https://github.com/Shachar/safewrite/commit/efafcd4260375a41257709c7eb5a8d6065366849 why should anyone trust their important data to this library? Feel free not to use it/file bugs against it. Giving feedback over the upstream trustworthiness is not the purpose of ITP bugs, and I have been warned by the list masters that discussing a specific package's upstream bugs on Debian-devel is off topic. I quickly reviewed the code and found: Did you read the accompanying manual pages first? safe_open() might not return correct error codes, since the library and system calls in its cleanup code may overwrite the original error code. Thank you for your input. I'll fix it. It uses a fixed extension for the temporary file name, and unlinks whatever was there before; this could be a security flaw. The matter has been discussed before. If you have a specific scenario where this will cause a security flaw, please feel free to file a bug or contact me directly. Pending that happening, my analysis is that there is no security flaw in that case. It doesn't check for failure of fstat() (this is unlikely but possible, e.g. when using a network filesystem). Interesting point. I'll have to think about it. Copying setuid and setgid bits to an empty file is pointless, since they are cleared by write() (this is a good thing!). Frankly, I was not aware of this. I could not find it documented in the man pages. In any case, this is no regression from the non-safe_open case, as these would get cleared on write either way. If this is a Linux only feature, I'm actually inclined to leave the code in (which is why I needed the manual pages). safe_close() doesn't actually close the file or free the 'context' if fsync() fails. This is inconsistent with close(). But consistent with what the man page says about it. The alternative is to not allow the user to retry saving the file's content, which I don't see as preferable. Thank you for your feedback. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d648429.5010...@debian.org
Re: Fun with libtool and cross-builds
On 09/02/11 22:10, Simon Josefsson wrote: Please try to debug where the -L/usr/lib comes from, I don't believe libtool is adding this by itself but instead it is told to add it by some incorrect .la file or similar. This is from memory, as I also ran into the same problem. The problem is, if my memory serves me right, in the following scenario: Cross build library A and install it with DESTDIR (obviously) to /tmp/otheroot Try to cross build library B, that needs library A. Obviously, you're going to give it -L /tmp/otheroot/usr/lib. The problem is that the .la files in /tmp/otheroot/usr/lib point to /usr/lib as the place to find the library. This only becomes a problem when a native version of library A is installed on the real system, at which point the compiler prefers that version, and then fails as it is of the wrong architecture. In my projects I wound up fixing the la file with sed as part of the build process, but that was an embedded project where: 1. The la files were not installed to the destination machine, and 2. The entire build was controlled by a single governing makefile. If either one of these conditions is not present, my solution simply wouldn't work. Another solution is to build A with --prefix=/tmp/otheroot/usr, but I think we can all see how that might break stuff in the library if the destination path is used inside the code. The only real solution I see for this is for libtool to have specific support for linking against DESTDIR installed libraries (maybe make it respect DESTDIR if it's defined during the build? That could be a solution that is both easy to understand and simple to integrate) Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com
Re: Safe file update library ready (sort of)
On 06/02/11 18:40, Goswin von Brederlow wrote: I absolutely hate that. A header file should be compilable on its own. The times when #includefoo.h would slow down the compiler are long gone and all include files are protected with #ifndef NAME so duplicate includes are harmless. On the other hand finding out what include files to include and in what order is a real pain if you have multiple files. Even if you have read the manual you will have to reread it every time you start a new project again and again to get that right. The includes necessary for safe_open are those necessary for open, plus safe_write.h itself. I don't see that as particularly burdensome. I'm not sure how platform independent any includes I put inside my header are going to be, and would rather not open this particular can of worms. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d51bcb3.7010...@debian.org
Re: Safe file update library ready (sort of)
On 26/01/11 13:03, Goswin von Brederlow wrote:
Some things I noticed:
safewrite.h:
- missing headers, e.g. for mode_t
No. That's intentional. I'm assuming the people who will use safewrite.h
are going to RTFM, where it clearly says that those includes are needed.
I might reconsider if valid reasons are provided, but I would like to
avoid keep including the same headers over and over.
- no 'extern C {'
You are right. Fixed now.
I don't like how your functions are destructive to the path argument.
I don't think that is a major issue, but I do think that the reliance on
PATH_MAX is. I think the current implementation solves both of these
concerns.
Shachar
--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d4d984b.9070...@debian.org
Re: Safe file update library ready (sort of)
On 04/01/11 16:24, Ian Jackson wrote: Shachar Shemesh writes (Safe file update library ready (sort of)): This is not a formal release just yet (plus one function is still missing an implementation, trivial though it might be). It's just that the list obviously has a few people knowledgeable on the subject who can give my code a second look and see whether there is anything I have missed. I think this kind of approach is the wrong way to solve most instances of this kind of problem. A better way is userv, which I wrote over a decade ago and have been using with success on chiark since. Ian. I'm sorry, it might be me, but I fail to see the overlap between the functionalities of safewrite vs. userv. The premises for safewrite is that a program wants to make sure data integrity is maintained when writing files. Userv seems to be about trust and a user level tool. The two seem to revolve around two completely different interpretations to the word safe, as well as two completely different use scenarios. Am I missing something here? Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d2330be.2070...@debian.org
Re: Safe File Update (atomic)
On 02/01/11 17:37, Olaf van der Spek wrote: A userspace lib is fine with me. In fact, I've been asking for it multiple times. Result: no response. Excuse me? You (well, Henrique, but you were CCed) said how about a user space lib? I said I'm working on one, will be ready about this weekend. I even gave a URL to watch (https://github.com/Shachar/safewrite). If you check it out right now, you will find there a fully implemented and fairly debugged user space solution, even including a build tool and man page. BTW - feedback welcome. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d21a67b.50...@debian.org
Safe file update library ready (sort of)
Hi all, I've promised to get a library out there, and here it is. The base URL is https://github.com/Shachar/safewrite, and the actual code is at https://github.com/Shachar/safewrite/blob/master/safewrite.c This is not a formal release just yet (plus one function is still missing an implementation, trivial though it might be). It's just that the list obviously has a few people knowledgeable on the subject who can give my code a second look and see whether there is anything I have missed. I'll probably make an official release over the next couple of days. Feedback most appreciated. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d21a84c.4060...@debian.org
Re: Safe file update library ready (sort of)
On 03/01/11 14:10, Adam Borowski wrote: There's a race condition: while [ 1 ]; do ln -s /etc/passwd somefile.tmp; done Hey root, could you please use this program using libsafewrite on 'somefile'? Two questions: 1. Is this race a regression from the single file case? 2. Is this race avoidable? In essence, it is impossible, as far as I know (patches welcome) to avoid a race when symlinks are involved (with specific exceptions). The assumption is, and has always been, that the directory resides inside a location that is secure from attacks. In this particular case, for example, you don't need this race at all. Simply do ln -s /etc/passwd somefile and ask root to write to somefile, with or without safewrite. That would work equally well, and does not require to race with anything. You might be wondering, if that is the case, why I'm unlinking somefile.tmp before opening it with O_CREAT|O_TRUNC. The reason is that it might have permissions (say, from a previous run that failed - unlikely, but not impossible) that prevent proper functioning. It has nothing to do with permissions. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d21d59c.3010...@debian.org
Re: libsafewrite
On 03/01/11 14:54, Olaf van der Spek wrote: That's one of the more interesting parts. It sure is to you. I'm not sure about other users. I'll tell you what - I'll make the project's home page a wiki, and you can document these to your heart's content. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d21d64d.3070...@debian.org
Re: libsafewrite
On 03/01/11 16:05, Olaf van der Spek wrote: Doesn't the Debian project care about regressions (and quality in general)? I'm sorry, but from scanning the conversation so far, no one but you seems to regard this as either a regression or a loss of quality. I will shut up at this point to let anyone who disagrees with this statement come forward and say so. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d21d87f.5020...@debian.org
Re: Safe file update library ready (sort of)
On 03/01/11 14:10, Adam Borowski wrote: There's a race condition: while [ 1 ]; do ln -s /etc/passwd somefile.tmp; done Hey root, could you please use this program using libsafewrite on 'somefile'? Two questions: 1. Is this race a regression from the single file case? 2. Is this race avoidable? In essence, it is impossible, as far as I know (patches welcome) to avoid a race when symlinks are involved (with specific exceptions). The assumption is, and has always been, that the directory resides inside a location that is secure from attacks. In this particular case, for example, you don't need this race at all. Simply do ln -s /etc/passwd somefile and ask root to write to somefile, with or without safewrite. That would work equally well, and does not require to race with anything. You might be wondering, if that is the case, why I'm unlinking somefile.tmp before opening it with O_CREAT|O_TRUNC. The reason is that it might have permissions (say, from a previous run that failed - unlikely, but not impossible) that prevent proper functioning. It has nothing to do with permissions. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d21d57d.1030...@shemesh.biz
Re: Safe File Update (atomic)
On 30/12/10 13:46, Henrique de Moraes Holschuh wrote: Is there a code snippet or lib function that handles this properly? I don't know. I'd be interested in the answer, though :-) I'm working on one under the MIT license. Will probably release it by the end of this week. Will also handle copying the permissions over and following symlinks. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1c9d3b.6060...@debian.org
Re: Safe File Update (atomic)
On 30/12/10 17:02, Olaf van der Spek wrote: On Thu, Dec 30, 2010 at 3:51 PM, Shachar Shemeshshac...@shemesh.biz wrote: I'm working on one under the MIT license. Will probably release it by the end of this week. Will also handle copying the permissions over and following symlinks. Sounds great! Got a project page already? No. I was doing it as code to accompany an article on my company's site about how it should be done. I was originally out to write the article, and then decided to add code. A good thing, too, as recursively resolving symbolic links is not trivial. There is an extremely simple way to do it on Linux, but it will not work on all platforms (the *BSD platforms, including Mac, do not have /proc by default). What aboue file owner? Meta-data (ACL)? Olaf The current code (I'm still working on it, or I would have released it already, but it's about 80% done) does copy owner data over (but ignores failures), but does not handle ACLs. I decided to postpone this particular hot potato until I can get a chance to see how to do it (i.e. - never had a chance on Linux) AND how to do it in a cross-platform way (the code is designed to work on any Posix). Pointers/patches once released are, of course, welcome :-) Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1ca143.9020...@debian.org
Re: Safe File Update (atomic)
On 30/12/10 13:46, Henrique de Moraes Holschuh wrote: Is there a code snippet or lib function that handles this properly? I don't know. I'd be interested in the answer, though :-) I'm working on one under the MIT license. Will probably release it by the end of this week. Will also handle copying the permissions over and following symlinks. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1c9c74.2050...@shemesh.biz
Re: Safe File Update (atomic)
On 30/12/10 19:48, Henrique de Moraes Holschuh wrote: It doesn't. You need a copy inode without the file data filesystem interface to be able to do that in the first place. It might exist, but I never heard of it. If my (extremely leaky) memory serves me right, Windows has it. It's called delete and then rename. It is not atomic (since when do Windows care about not breaking stuff), but it does exactly that. If you delete a file and quickly (yes, this feature is time based) rename a different file to the same name, the new file will receive all metadata information the old file had (including owner, permissions etc.) Just thought I'd share this little nugget to show you how much worse non-posix has it. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1ccc38.6000...@debian.org
Re: Safe File Update (atomic)
On 30/12/10 17:17, Olaf van der Spek wrote: On Thu, Dec 30, 2010 at 4:12 PM, Shachar Shemeshshac...@debian.org wrote: No. I was doing it as code to accompany an article on my company's site about how it should be done. I was originally out to write the article, and then decided to add code. A good thing, too, as recursively resolving symbolic links is not trivial. There is an extremely simple way to do it on Linux, but it will not work on all platforms (the *BSD platforms, including Mac, do not have /proc by default). Depending on /proc is probably not reasonable. Are you sure it will be atomic? ;) open old file, get fd (we'll assume it's 5). Do readlink on /proc/self/fd/5, and get file's real path. Do everything in said path. It's atomic, in the sense that the determining point in time is the point in which you opened the old file. How do you preserve owner (as non-root)? I thought I answered that. Best effort. You perform the chown, but do not bother with the return code. If it succeeded, great. If not, well, you did your best. The reason I asked for a kernelland solution is because it's hard if not impossible to do properly in userland. But some kernel devs (Ted and others) don't agree. They reason that the desire to preserve all meta-data isn't reasonable by itself. I'm with Henrique on that one. I am more concerned with the amount of non-Posix code that needs to go into this than preserving all attributes. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1ccd81.3010...@debian.org
Re: Safe File Update (atomic)
On 30/12/10 17:02, Olaf van der Spek wrote: Got a project page already? Watch this space. Actual code coming soon(tm). https://github.com/Shachar/safewrite Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d1d743b.8080...@shemesh.biz
RFH - fakeroot-ng and ptrace, not Debian specific
Hi all, I'm sending this request for help in the hope that it randomly hit one of the smart people on this list, but it is, as far as I can tell, not Debian specific. Fakeroot-ng is a clean re-implementation of the fakeroot principle, based on ptrace rather than LD_PRELOAD. As a result it can go where fakeroot cannot (no problem with statically compiled binaries, can do almost full chroot with full chroot planned) on the one hand, but has some drawbacks as well (no hope of being as quick as fakeroot, has some highly platform specific code, fairly complex). You can read more about it at http://fakeroot-ng.lingnu.com The version currently in trunk has an attempt to remove some Linux specific hacks when attaching to a newly created process. It does so by changing a fork into clone, and adding the CLONE_PTRACE whether the original specified it or not. This is the exact same thing strace does. Unlike strace, however, fakeroot-ng is failing to attach itself to newly created threads. I'd say I was passing the wrong flags to the kernel, but if I watch all system calls performed by the debugger (yes, using strace), I seem to see that strace and fakeroot-ng do exactly the same thing. The only difference is that for strace it works. I need someone who is either a ptrace expert, or who has a fresh set of eyes and some patience, to help me look at it and figure out what I'm doing wrong. Thanks, Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d09c41b.70...@debian.org
Accepted argtable2 12-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 22 Aug 2010 16:33:24 +0300 Source: argtable2 Binary: libargtable2-dev libargtable2-docs libargtable2-0 Architecture: source amd64 all Version: 12-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: libargtable2-0 - A library for parsing GNU style command line arguments libargtable2-dev - A library for parsing GNU style command line arguments libargtable2-docs - A library for parsing GNU style command line arguments Closes: 488585 Changes: argtable2 (12-1) unstable; urgency=low . * New upstream version * Upgraded the Debian policy to 3.9.1.0 * Change the debhelper compatibility level to V8 * Various Lintian cleanups * Reduce debian/rules to rely on debhelper more (Closes: #488585) Checksums-Sha1: b7e78a2d2f6719f571d170903f8e311bd570e550 1073 argtable2_12-1.dsc 29857965b6849332cd862ca934cee11228673994 3358604 argtable2_12.orig.tar.gz dccf747f7875982dfa1d4c6260ad7354c11c4830 41888 argtable2_12-1.debian.tar.gz 183ac0fa48ff80279f85fa9f5410669af0b45ea2 60174 libargtable2-dev_12-1_amd64.deb 294fc26b2ef3c6eaed1aff01b5b9f3b0583b05fd 2957588 libargtable2-docs_12-1_all.deb d4be43f710fc0a901f62c991c0ce9bfed64804b4 19188 libargtable2-0_12-1_amd64.deb Checksums-Sha256: 2c0b88cebea82e68dbb54479fcb6551d14b7facd1f05596285c49df1b803d4d9 1073 argtable2_12-1.dsc 40c13da72b48717afcf94d4c53909b768587b44b4dab84f38bd5c69c7667c693 3358604 argtable2_12.orig.tar.gz fd1a69f6e727cfd08b69e91042df52d559e9d4a938be42b7869670ab538489e5 41888 argtable2_12-1.debian.tar.gz 4d07e067b3049788499ac829db066afedb145bf7d947434d712638ad31f384ad 60174 libargtable2-dev_12-1_amd64.deb 2aa5e98f0547194fe6f7731c659987c8a38500551c3ed3cfe5674a025c5239f2 2957588 libargtable2-docs_12-1_all.deb be78e9ce93ac0b7f313277dd22da319096e03a50e5ff0762377ec43cefcbba70 19188 libargtable2-0_12-1_amd64.deb Files: 953cb3f9a2d5b90f4547dd85a2ed871d 1073 libs optional argtable2_12-1.dsc 291e249ea60f4d0637e467356a8ae41a 3358604 libs optional argtable2_12.orig.tar.gz 36338d0469b627f513ea58251e2ba6e4 41888 libs optional argtable2_12-1.debian.tar.gz 3daea9717d63ead2f0c6bd17ea9c42d0 60174 libdevel optional libargtable2-dev_12-1_amd64.deb c964346342eb72ce8167bf141d532aa9 2957588 doc optional libargtable2-docs_12-1_all.deb 245f6d5fa77f1d81034a688f6536f8c7 19188 libs optional libargtable2-0_12-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxxKGsACgkQg8ByFc29vOLchwCgr9PZA7aQKQ4K3ejN3d+qY5VC ossAnj2puSUgbNXKnk1hIZWgqZjkOOYp =JFWl -END PGP SIGNATURE- Accepted: argtable2_12-1.debian.tar.gz to main/a/argtable2/argtable2_12-1.debian.tar.gz argtable2_12-1.dsc to main/a/argtable2/argtable2_12-1.dsc argtable2_12.orig.tar.gz to main/a/argtable2/argtable2_12.orig.tar.gz libargtable2-0_12-1_amd64.deb to main/a/argtable2/libargtable2-0_12-1_amd64.deb libargtable2-dev_12-1_amd64.deb to main/a/argtable2/libargtable2-dev_12-1_amd64.deb libargtable2-docs_12-1_all.deb to main/a/argtable2/libargtable2-docs_12-1_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1onbpf-xy...@franck.debian.org
Accepted privbind 1.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 03 Apr 2010 05:56:36 + Source: privbind Binary: privbind Architecture: source amd64 Version: 1.2-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: privbind - Allow unprivileged apps to bind to a privileged port Closes: 576244 Changes: privbind (1.2-1) unstable; urgency=low . * Fix 1-byte buffer overflow explain what you changed and why (Closes: #576244) * Switch to dpkg-source 3.0 (quilt) format * Update the policy version. Checksums-Sha1: 31ce87395e5c1211d20ee997fc603bf0593597bd 1028 privbind_1.2-1.dsc 0f5ba2d14436ef9db927e012fd7faa8743ab2b94 328381 privbind_1.2.orig.tar.gz 65323dfd271821d0f33a68c4ca74995b30b9054f 10891 privbind_1.2-1.debian.tar.gz 269feafc1b5db5d462498253fd141e4d3d7fd79f 18532 privbind_1.2-1_amd64.deb Checksums-Sha256: 9d124bea031dfc9124bd7419d1793b8c813e10b0194813d8f7b787aea4224953 1028 privbind_1.2-1.dsc 16169c25f3429e530bd3e8b448898649f19f7870f1359e815383692d5615ba97 328381 privbind_1.2.orig.tar.gz 8a932d92e15e46e6eb7ae96ea7fe98a1693070a0c0a5988a03fd24b362b14d0f 10891 privbind_1.2-1.debian.tar.gz 648ab16f91dd2551472744359f3030582ceb628baa7c2274760e0f96052285be 18532 privbind_1.2-1_amd64.deb Files: 39c0f9e0e93e31049d02d396e913dba7 1028 utils extra privbind_1.2-1.dsc 07e06409bf8f5f0bc1e64a9ad3ea8f98 328381 utils extra privbind_1.2.orig.tar.gz 0ccaf93cff3148b00b7d03c68b510229 10891 utils extra privbind_1.2-1.debian.tar.gz 22358578ff41c13a970283629a4ae310 18532 utils extra privbind_1.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAku22VkACgkQg8ByFc29vOJFJwCfeH73HqiagAZNqxv4/Y8j2a44 TicAnAsjWey8lsNsunJj65mZITxWDSh4 =ZWnh -END PGP SIGNATURE- Accepted: privbind_1.2-1.debian.tar.gz to main/p/privbind/privbind_1.2-1.debian.tar.gz privbind_1.2-1.dsc to main/p/privbind/privbind_1.2-1.dsc privbind_1.2-1_amd64.deb to main/p/privbind/privbind_1.2-1_amd64.deb privbind_1.2.orig.tar.gz to main/p/privbind/privbind_1.2.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ny8nf-0005l1...@ries.debian.org
Accepted fakeroot-ng 0.16-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 23 Jun 2009 21:42:23 +0300 Source: fakeroot-ng Binary: fakeroot-ng Architecture: source amd64 Version: 0.16-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Closes: 532994 Changes: fakeroot-ng (0.16-1) unstable; urgency=low . * New upstream version (major bug fixes) * fakeroot-ng should use /dev/shm for shared memory files (Closes: #532994) Checksums-Sha1: 6579da7fc62191705ba95ef5af3615a133143a7c 1023 fakeroot-ng_0.16-1.dsc 00f502d0d4d6140168683d8e4e7274ed5ab692c3 186344 fakeroot-ng_0.16.orig.tar.gz 697b028a5ebfd519c58b8acf1e82373842c68e9e 4299 fakeroot-ng_0.16-1.diff.gz ddd119a7ce102b8f69607dbb1aeb2c60b12ede89 56480 fakeroot-ng_0.16-1_amd64.deb Checksums-Sha256: 90af6dae96ba2107a934b7480bc15d1a8c9841d89e0abca6b1f60c715f242684 1023 fakeroot-ng_0.16-1.dsc 9ac2e514f3796cea591226471ffef47796f4b5bc11348ee1bc76b237a668033a 186344 fakeroot-ng_0.16.orig.tar.gz f074082314ab275aa0d27411e19bed6543f3dfe629eb28e763f6929753052ff7 4299 fakeroot-ng_0.16-1.diff.gz 6c4b7a42c993fb9daa8f9d9726a38ba45b9e204b5512381eb6896674cd427a0c 56480 fakeroot-ng_0.16-1_amd64.deb Files: 807293d61005b6a0bc6a4d47d88ee4da 1023 utils extra fakeroot-ng_0.16-1.dsc 4d4e1f4636736e3c64483b450e2d44ed 186344 utils extra fakeroot-ng_0.16.orig.tar.gz 6440bb0c31a111c57e301775475ede60 4299 utils extra fakeroot-ng_0.16-1.diff.gz ca0533af954d09906ba35b6bf477b464 56480 utils extra fakeroot-ng_0.16-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkpBJe0ACgkQg8ByFc29vOKSFwCgphdgMjbxa0XXdVr8PWibsgiE JMgAn3a95hPXXTg8jziHK+ZcZSTqNXCH =Pk35 -END PGP SIGNATURE- Accepted: fakeroot-ng_0.16-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.16-1.diff.gz fakeroot-ng_0.16-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.16-1.dsc fakeroot-ng_0.16-1_amd64.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.16-1_amd64.deb fakeroot-ng_0.16.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.16.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted fakeroot-ng 0.15-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 28 May 2009 14:46:43 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source amd64 Version: 0.15-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Closes: 521784 Changes: fakeroot-ng (0.15-1) unstable; urgency=low . * New upstream version * Fix package description says chroot interception is not implemented - Package description updated (Closes: #521784) Checksums-Sha1: f40918069e5215080e456d6819cbed6125d4a4f9 1023 fakeroot-ng_0.15-1.dsc f3721578f9829255fbd13edbb682b01178aaa1a0 181944 fakeroot-ng_0.15.orig.tar.gz 49e98d266f6c84ca8810d2451ed7721b56771d1c 4222 fakeroot-ng_0.15-1.diff.gz 2c07764c422f469820120b824f44dd330ab14c2d 53964 fakeroot-ng_0.15-1_amd64.deb Checksums-Sha256: 0b4aea1186fd0dacca1bc25e9ed8333791f05112e37e252f9dad3e0a1bcd8c70 1023 fakeroot-ng_0.15-1.dsc 50263067fc5043698a96b78b6c9672364604a9157c181161427363bfcb0e4ee0 181944 fakeroot-ng_0.15.orig.tar.gz 93a816a9027973c57403e6da69dae6028079d0687cd6f20083346f4518a94ea6 4222 fakeroot-ng_0.15-1.diff.gz 0b0895cd8f66a99edc64b48b44f155879275f55aec35370ee76a127ef2b12da9 53964 fakeroot-ng_0.15-1_amd64.deb Files: bfd9574552686e92a27f0522731b6179 1023 utils extra fakeroot-ng_0.15-1.dsc cc4f8bf12205156fd6a8e737bfd32f20 181944 utils extra fakeroot-ng_0.15.orig.tar.gz a2072ea481cadff74d36b465dccce5e7 4222 utils extra fakeroot-ng_0.15-1.diff.gz 9afbf790dd76449b3b76311b35bae1c8 53964 utils extra fakeroot-ng_0.15-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkofeuAACgkQg8ByFc29vOK4tgCfTJaU5qoqarC1WHnGyl2S2rJO rUAAoJ07vzN6U2UMZqAnnFFSqU6ehOcz =rtY0 -END PGP SIGNATURE- Accepted: fakeroot-ng_0.15-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.15-1.diff.gz fakeroot-ng_0.15-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.15-1.dsc fakeroot-ng_0.15-1_amd64.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.15-1_amd64.deb fakeroot-ng_0.15.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.15.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted rsyncrypto 1.12-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 20 Feb 2009 11:01:12 + Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.12-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: rsyncrypto - rsync friendly encryption Closes: 489654 Changes: rsyncrypto (1.12-1) unstable; urgency=low . * Fix bashism in /bin/sh script - Change let to assignement (Closes: #489654) * New upstream release Checksums-Sha1: e01a88e556289dc91a3dde255cb15a95142817cf 1050 rsyncrypto_1.12-1.dsc 9379603c21e4a180e85e0411cc237fe8c7ca52ec 420652 rsyncrypto_1.12.orig.tar.gz d73ec913310d6fe5ae45e13ae9c9c8e59d0b8e94 26798 rsyncrypto_1.12-1.diff.gz fdeb0f88e8a638d8a676f44a076b0c40eedee003 306268 rsyncrypto_1.12-1_i386.deb Checksums-Sha256: fdfddbd77aea73f6edd661d7a4c7990bf9c84ca68f4743563d7672059bde9a6c 1050 rsyncrypto_1.12-1.dsc 1fbe640af6db598e105d9e9554cddce05ed78849f0afa26d4cc8b1e1a2df9ace 420652 rsyncrypto_1.12.orig.tar.gz 8dd4a641955a6492c328d6c078578aa0f6419cf1d600bbd863e0134d007c80de 26798 rsyncrypto_1.12-1.diff.gz b4b5313630c92ad3383e8f35fc1512bb4a3a1c03ea046e439330142ff3283d49 306268 rsyncrypto_1.12-1_i386.deb Files: b03ac7e061b7cabf168967d84664a7d3 1050 utils optional rsyncrypto_1.12-1.dsc 62367d5458ceaab58bbe73030880f538 420652 utils optional rsyncrypto_1.12.orig.tar.gz 912b2a0e3b1049027c3d8eac5e8a23cf 26798 utils optional rsyncrypto_1.12-1.diff.gz ff5baae5cf39256fec4d812d8555bf48 306268 utils optional rsyncrypto_1.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmej04ACgkQg8ByFc29vOIL3gCgpTttZWT+5lTEQ9BhJ8rPKB4c e2EAn2Y0LxE1BVtuBol+FdYK4ueFb3q6 =Vq+s -END PGP SIGNATURE- Accepted: rsyncrypto_1.12-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.12-1.diff.gz rsyncrypto_1.12-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.12-1.dsc rsyncrypto_1.12-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.12-1_i386.deb rsyncrypto_1.12.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.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
Accepted sshpass 1.04-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 20 Feb 2009 11:25:27 + Source: sshpass Binary: sshpass Architecture: source i386 Version: 1.04-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: sshpass- Non-interactive ssh password authentication Closes: 506208 Changes: sshpass (1.04-1) unstable; urgency=low . * Fix fails when ssh asks for host key confirmation: sshpass now detects the situation and returns a coded error (Closes: #506208) * Several new upstream versions fixing some crashes * Update the version file to explicitly state GPL version 2 Checksums-Sha1: ac0d799a784d8d8b14373140ae1157120b5d73a9 1008 sshpass_1.04-1.dsc c91a6e0d128cc8d27e8cd0cff05b030abf367ccf 93734 sshpass_1.04.orig.tar.gz b1923bdc7c6cfa8cf9d9ffeb377f5cd22871e831 26056 sshpass_1.04-1.diff.gz b8a7bba0c8c4a82f8677f09b2e1acbae30c6407c 9610 sshpass_1.04-1_i386.deb Checksums-Sha256: 7cc178a1f87586ac43a1df5f2253d4e62b8fcda4ad40a01503d5ec64d8922d8d 1008 sshpass_1.04-1.dsc e8abb9a409f25928722251a5855a74854f6d64af3eb136b804a04fd630d70c80 93734 sshpass_1.04.orig.tar.gz 0b93fe2fdbfadb1cf1ff3cf3135979f0d8f20c7f644e5215c80c39024f7b0ecc 26056 sshpass_1.04-1.diff.gz 787dbfe056fe17a1c1b248acc637878c02f006d9f523db2592b214d9fe64a402 9610 sshpass_1.04-1_i386.deb Files: b379d6bd9390bd6a2f0feaa9504ecc64 1008 utils extra sshpass_1.04-1.dsc 87e7c72e319691c5fdf219f6c7effb4a 93734 utils extra sshpass_1.04.orig.tar.gz 501bd1d27b54115a25c361383d4f4936 26056 utils extra sshpass_1.04-1.diff.gz a3f566a48ddf42adda82268f273822c9 9610 utils extra sshpass_1.04-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmelFsACgkQg8ByFc29vOKE8QCeIqFsqbnwgceoYTV5nqQDZc4a 17EAnihze1hEqmESOzFoxr6tLCqa7ihA =8oSv -END PGP SIGNATURE- Accepted: sshpass_1.04-1.diff.gz to pool/main/s/sshpass/sshpass_1.04-1.diff.gz sshpass_1.04-1.dsc to pool/main/s/sshpass/sshpass_1.04-1.dsc sshpass_1.04-1_i386.deb to pool/main/s/sshpass/sshpass_1.04-1_i386.deb sshpass_1.04.orig.tar.gz to pool/main/s/sshpass/sshpass_1.04.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted fakeroot-ng 0.14-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 20 Feb 2009 21:48:32 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.14-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh shac...@debian.org Changed-By: Shachar Shemesh shac...@debian.org Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.14-1) unstable; urgency=low . * New upstream version * Update the common licenses link to GPL version 2 Checksums-Sha1: eb315e083024fe253d05b53390982b8a5015a995 1023 fakeroot-ng_0.14-1.dsc 9a3e6f5227a1ad41f5aa4b65c66cb43baaed3dbf 179368 fakeroot-ng_0.14.orig.tar.gz 4355c82bcc7a8b568f770cf4f8650e95603f877f 4197 fakeroot-ng_0.14-1.diff.gz 1312c9b45eb93e39e02fa5e61cd5e43924b37c3d 49040 fakeroot-ng_0.14-1_i386.deb Checksums-Sha256: fb40854986eb3de9cc338177f9c8b322d9c8c90ee4fb1309222ce6e57672a4e3 1023 fakeroot-ng_0.14-1.dsc c4342ec01cce14950131f9e3a1cb7f8f1a1324ed69a6514e850d5092fe348d76 179368 fakeroot-ng_0.14.orig.tar.gz e6c5376a4a2a8eeb619e323a02a77fe6d1f91cd130d794d2d26620e89dbd4a93 4197 fakeroot-ng_0.14-1.diff.gz 84988941aaf8568e8aa41411125d413624b15ab3d1810b8bcf504f70c5c60f2b 49040 fakeroot-ng_0.14-1_i386.deb Files: 92c18784e6bab6afe8b02daa863b76c2 1023 utils extra fakeroot-ng_0.14-1.dsc acd3df83dac9cee7cec9bd30397ac2db 179368 utils extra fakeroot-ng_0.14.orig.tar.gz 9295ad745036832bc178cf9caae19fec 4197 utils extra fakeroot-ng_0.14-1.diff.gz 875820d554b99bef61c762b73f8176c8 49040 utils extra fakeroot-ng_0.14-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmfJtcACgkQg8ByFc29vOJ7vgCgnIgzy/2U1PXHvMBymyZkArGw VqQAoJlLVT0UzX+G5Xpe8LtgNlTrybR0 =3MHg -END PGP SIGNATURE- Accepted: fakeroot-ng_0.14-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.14-1.diff.gz fakeroot-ng_0.14-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.14-1.dsc fakeroot-ng_0.14-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.14-1_i386.deb fakeroot-ng_0.14.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.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
Accepted sshpass 1.01-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 18 Oct 2008 08:13:59 +0200 Source: sshpass Binary: sshpass Architecture: source i386 Version: 1.01-2 Distribution: unstable Urgency: medium Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: sshpass- Non-interactive ssh password authentication Closes: 502585 Changes: sshpass (1.01-2) unstable; urgency=medium . * sshpass taking 100% CPU while the ssh session is running (Closes: #502585) * Update policy version to 3.8.0.0 - Added Homepage to package. * Fixed lintian warning about copyright file Checksums-Sha1: 4fc751b6dd6f003c8f8937db9e10de2bcb002eaf 1008 sshpass_1.01-2.dsc cef4c8e9fe40ffce6919d6d085b98c7ca95b8c7b 27063 sshpass_1.01-2.diff.gz 20e6a2acf7995bfdafd656884340f4f4739ad93c 8452 sshpass_1.01-2_i386.deb Checksums-Sha256: 749e820a29e28ab51a68ca5e2c16c8c7b7b7727602439f8ee20e3ca46211da48 1008 sshpass_1.01-2.dsc bc6e56060c431d98e38cec4dcc62a8e0d28f6794e27e3fe105efb2f776070738 27063 sshpass_1.01-2.diff.gz c87b3217d2dbaac9fb6f126a5d1f590e6a0c925726de7e4813a154cc6f0f 8452 sshpass_1.01-2_i386.deb Files: 9bb2ed405d7440323c5bc3b5b8c49926 1008 utils extra sshpass_1.01-2.dsc ab3b894bed583c10a428243453144df1 27063 utils extra sshpass_1.01-2.diff.gz ed1390c7791a35acac80822819622645 8452 utils extra sshpass_1.01-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkj5koUACgkQg8ByFc29vOIXKQCeK2DsrrCjyCLYQwXRfIufpqfJ xXsAn1/Ps+igfAToDulNoWvc8KiTzDGD =x9ml -END PGP SIGNATURE- Accepted: sshpass_1.01-2.diff.gz to pool/main/s/sshpass/sshpass_1.01-2.diff.gz sshpass_1.01-2.dsc to pool/main/s/sshpass/sshpass_1.01-2.dsc sshpass_1.01-2_i386.deb to pool/main/s/sshpass/sshpass_1.01-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.12-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 20 Aug 2008 11:43:51 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.12-3 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Closes: 495421 Changes: fakeroot-ng (0.12-3) unstable; urgency=low . * Fakeroot-ng silently fails when /tmp is mount noexec (Closes: #495421) Checksums-Sha1: 074e648067c2ec7423ba46700c7241c1cd513c60 1023 fakeroot-ng_0.12-3.dsc 31394dfe51b7e3b5253e22a31f6dab9145133e8c 6350 fakeroot-ng_0.12-3.diff.gz b291c73df5dda2b394ac7819899ac03c92673813 47496 fakeroot-ng_0.12-3_i386.deb Checksums-Sha256: 612ef25cc74bee14e4699b47135868b2817794718cb643961ca929a15bdda016 1023 fakeroot-ng_0.12-3.dsc 723f643a230f5ca54dd2791fa9784279457911df2d28b1b6bf1dba0a0cfa6cbf 6350 fakeroot-ng_0.12-3.diff.gz 63159df90e1934ebe2b3f3d419499a5099a76adbd8c9a2fd8cb6bea70470632e 47496 fakeroot-ng_0.12-3_i386.deb Files: 62df08fa2797b3a1dc6f368adcf05c52 1023 utils extra fakeroot-ng_0.12-3.dsc 0d7602bba97f4b7f2c381369a6a79c77 6350 utils extra fakeroot-ng_0.12-3.diff.gz bf6bd22f60930b4780d6a7e0f994d462 47496 utils extra fakeroot-ng_0.12-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkisEhAACgkQg8ByFc29vOIWNgCeIoUg2+1TsW9M39Aoltn6k+hK WPIAoIrXdsHIblLovNyegxP/BCQhyR7p =q6E3 -END PGP SIGNATURE- Accepted: fakeroot-ng_0.12-3.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-3.diff.gz fakeroot-ng_0.12-3.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-3.dsc fakeroot-ng_0.12-3_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.12-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 15 Aug 2008 05:32:36 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.12-2 Distribution: unstable Urgency: high Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Closes: 493061 495174 Changes: fakeroot-ng (0.12-2) unstable; urgency=high . * fakeroot rm file gives a weird rmdir error, breaks debhelper. (Closes: #493061) * debian/rules clean does not clean, resulting in FTBS twice problems (Closes: #495174) * Reduce use of continuation line in debian/postinst to work around a lintian false positive (filed bug #495176) Checksums-Sha1: c4199235c02d50c1ab7611c2ce4bf6ab66a86189 1023 fakeroot-ng_0.12-2.dsc be9bcf8af67ebc947b88f8417270879a506eed3b 4493 fakeroot-ng_0.12-2.diff.gz df98b56f8bd64ee13dea617a482e484fedbda153 46400 fakeroot-ng_0.12-2_i386.deb Checksums-Sha256: 7740f79ad27ac57d3bf6e63d0afd188fcce40d392aa1f9eefe6290babee29cb8 1023 fakeroot-ng_0.12-2.dsc 06c5c7a4149d395b4a3277e73ea5e2af62a7bb539d9743145bb5cb0612e0b4c0 4493 fakeroot-ng_0.12-2.diff.gz 1204bf085704bf50ee435cc5d39c653eede92829b966d6ed654305814fda0bf1 46400 fakeroot-ng_0.12-2_i386.deb Files: fc6ff4031b827e3924dcd66a134a492b 1023 utils extra fakeroot-ng_0.12-2.dsc f1cb8cc467c165073b04176c45aa492b 4493 utils extra fakeroot-ng_0.12-2.diff.gz caa422b15c40a81a9821d38be9067de4 46400 utils extra fakeroot-ng_0.12-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkilHC8ACgkQg8ByFc29vOLGKACfQrudqu2aZ5dczO8pAo15xKST 9Z0Anj13+3eDOgnqjGhEu3jsl9jZPqyv =Jen3 -END PGP SIGNATURE- Accepted: fakeroot-ng_0.12-2.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-2.diff.gz fakeroot-ng_0.12-2.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-2.dsc fakeroot-ng_0.12-2_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
FTBS twice - what is the priority for it?
Hi all, I am preparing an upload to Sid, with the intent of getting it into Lenny, for a package of mine (to solve bug #493061 for fakeroot-ng, if it matters). While working on it, I found out that the package also has a FTBS twice bug, which resulted from empty lines (with no leading tab character) in debian/rules in the clean target. My question is - what to do? Do I open a FTBS twice bug for the package and upload the fix? If so, what priority should the new bug be? I saw FTBS bugs ranging from wishlist to important. I don't think it is an actual policy violation (am I wrong? Can someone point me to the relevant section?) Alternatively, as the delta has only white spaces between fixing the tabs and not fixing it, I can just put the fix in and hope the release managers (hi!) don't catch me when I ask them to allow the fix for 493061 through. Then again, if the bug is not important enough, I can upload a fix that only handles 493061, and doesn't touch the double FTBS bug at all. What should I do? Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.11-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 25 Jun 2008 05:26:53 + Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.11-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.11-1) unstable; urgency=low . * New upstream release Checksums-Sha1: 936168596682307f1356273164a53ff9f5156789 1050 rsyncrypto_1.11-1.dsc 5679511221d3368f845d4b924cd02975bed96ff4 419204 rsyncrypto_1.11.orig.tar.gz 524807a381826c80647aa0bef78a23a008368ebb 26723 rsyncrypto_1.11-1.diff.gz d4c9eb40133f9e653d715f0fb737bbd28118755f 305638 rsyncrypto_1.11-1_i386.deb Checksums-Sha256: 66e31ac999a40cb1bd619887da1c6990ab4e867090973820cb1fa60e40b4732e 1050 rsyncrypto_1.11-1.dsc 8089a10adcdabc36c79aa0edc1b50aa900f20eeada93c343087779b973b81d0a 419204 rsyncrypto_1.11.orig.tar.gz 4e2613ec1ded7c96b96377d779d449b0a829c68c5b6ad3b4b675c2ad77c99b6a 26723 rsyncrypto_1.11-1.diff.gz 1d518720e85f80a30fc646df87f50eedbaae2e3cb44d6a2db0bb5324d57adea1 305638 rsyncrypto_1.11-1_i386.deb Files: 5ffd6f8f123633c403c080d10c605fc1 1050 utils optional rsyncrypto_1.11-1.dsc bd7b7f09595cbc5be4cf1e7fb5d6081b 419204 utils optional rsyncrypto_1.11.orig.tar.gz e8db1b2b1f9758ecfb92195e282a3873 26723 utils optional rsyncrypto_1.11-1.diff.gz 088dcb35d3d8d7641bf5125e6cc3eb21 305638 utils optional rsyncrypto_1.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhh14sACgkQg8ByFc29vOInXgCeMWmE2eg9Lc2tSFHaC4bM1sQU xkwAnAwPaqh/JeN+ebeZ9X96JcdDbg9p =QsQg -END PGP SIGNATURE- Accepted: rsyncrypto_1.11-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.11-1.diff.gz rsyncrypto_1.11-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.11-1.dsc rsyncrypto_1.11-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.11-1_i386.deb rsyncrypto_1.11.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Considerations for lilo removal
William Pitcock wrote: It seems like moving to grub for everything may be a good choice on the archs where lilo is used. Lilo has one killer feature that is totally missing from GRUB - the -R option. It allows me to upgrade a kernel on remote servers, knowing that if the upgrade fails, I will get the original kernel after a few minutes without asking a local hand to push the reset button. Until Grub has something similar, removing Lilo entirely seems like a bad idea to me. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFH: porting fakeroot-ng to more platforms
Fakeroot-ng is a clean reimplementation of fakeroot, using a totally different technology. Fakeroot-ng uses the ptrace interface to track the syscalls performed by the fooled program. This means fakeroot-ng is immune to problems that may happen as a result of races, cross-library interactions, different versions of glibc and statically compiled executables. As a result, tracking difficult syscalls, such as open(2), is possible. For example, as of version 0.12 (the latest version), fakeroot-ng has complete support for chroot, symlink resolving included. Obviously, there is a down side. Due to the low level interaction with the kernel, fakeroot-ng has to be specifically ported to each new platform. This porting is a non-trivial process, involving parsing of the register arguments as they are being passed to the kernel. It is a more complicated process than merely extracting the sources on a new platform and running make. That said, the porting is not an extremely complicated process either. There is a README.porting file that explains most of the tasks required. Every attempt has been made to place all platform dependent code into a separate library, and many of that library's functions apply to all Linux platforms and need not be rewritten. I have personally ported fakeroot-ng to x86, amd64 and PowerPC, with the later two being platforms that I have access to, but have never learned before the porting effort. The PowerPC port took me about three hours, and the AMD64 port took not much longer. I would like to receive help in either one of two ways. Either someone with platform access and the know how can do the porting, or someone can provide me with access to a development machine running one of the other platforms, and I can perform the porting there. I have tried to shell machines Debian currently has, and they proved insufficient. Either they were far too slow for repeated compilations (or any interactive work, for that matter), or they lack some of the tools needed (objdump, compilation tools, etc.) Any help would be greatly appreciated. Thanks, Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.12-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 11 Jun 2008 08:48:57 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.12-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.12-1) unstable; urgency=low . * New upstream version * Support for chroot for all Linux syscalls is now complete. Checksums-Sha1: 6d368d7f042609a9e1b1e54f537361d6de792775 1023 fakeroot-ng_0.12-1.dsc c00bc409bd24511d37ac8a84950abb6f4d0c126e 388638 fakeroot-ng_0.12.orig.tar.gz c134a26430ab4f481b0db24bf7faba9dc1f69a13 3969 fakeroot-ng_0.12-1.diff.gz e0a03252466babfd3555c35ec25be76bc5b69348 46198 fakeroot-ng_0.12-1_i386.deb Checksums-Sha256: fcfd03bf6f73cb468fc070b335e2d6a8ea9e38bdf9ccc1c320500c2df9ccbefb 1023 fakeroot-ng_0.12-1.dsc 92e06d7af449de2843b97be65a04f3e22e45d126e0b6bf654a11dd01f256dc5b 388638 fakeroot-ng_0.12.orig.tar.gz 09bcda5debb05ba7585b731fe4f83bf199cc0c99e997d33feeece311a5e9a881 3969 fakeroot-ng_0.12-1.diff.gz 10723830453ab485f2e8b30d9a6f5f7c16df09de872313ecfc24916422b51ec2 46198 fakeroot-ng_0.12-1_i386.deb Files: 71b0c43c343eb0e8f91465192cac837f 1023 utils extra fakeroot-ng_0.12-1.dsc d4011ab0059b6168d49c45d2f93c0898 388638 utils extra fakeroot-ng_0.12.orig.tar.gz 61db8e0b1e0f6951f62f46e4208fdf91 3969 utils extra fakeroot-ng_0.12-1.diff.gz f3cc5bb1bada356a6c09066f8ed58419 46198 utils extra fakeroot-ng_0.12-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhPkkgACgkQg8ByFc29vOLHxwCgh/BXJb8JXZLVeRmxdv88e1xG n1gAoKRUail1bH3zXCrmElPPqUgjviPD =KjfT -END PGP SIGNATURE- Accepted: fakeroot-ng_0.12-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-1.diff.gz fakeroot-ng_0.12-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-1.dsc fakeroot-ng_0.12-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.12-1_i386.deb fakeroot-ng_0.12.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.12.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.10-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 09 Jun 2008 16:02:31 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.10-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Closes: 472564 Changes: fakeroot-ng (0.10-1) unstable; urgency=low . * New upstream version * FTBFS with g++-4.3: Missing includes (Closes: #472564) * Now has (limited) support for chroot Checksums-Sha1: 95332cea790391d57a01eba01ae4a2a4f9c44b9d 1023 fakeroot-ng_0.10-1.dsc ed832f6501d0ac5bc58e4a4e139ea09fc37ebb6c 387668 fakeroot-ng_0.10.orig.tar.gz e090684859e40f67d6d38d12a7d7e7ea6b287e47 3989 fakeroot-ng_0.10-1.diff.gz 72df590bce20d50f90dc4803fd93c15e42ae3f4f 44994 fakeroot-ng_0.10-1_i386.deb Checksums-Sha256: 4b2d0269b32a619c330514661cde07604e9e484d6d3f0cf293e871fb7e78eed7 1023 fakeroot-ng_0.10-1.dsc c1dbeecc2c26115aacec275a336da64fe13f069f76864098f6fcb410374da7df 387668 fakeroot-ng_0.10.orig.tar.gz 255cfe7812561379dffad2e367e5da7c710608711514dd258787b8a8f179d9ff 3989 fakeroot-ng_0.10-1.diff.gz 854c2d6cb9105d0bc0dc369d2863f534e20e9973c97cb9db303b0677cfadd700 44994 fakeroot-ng_0.10-1_i386.deb Files: 704e1b4ac9c3b01ea1127444272d14c6 1023 utils extra fakeroot-ng_0.10-1.dsc f9fe2c9406a1d85213c8ee475721c43b 387668 utils extra fakeroot-ng_0.10.orig.tar.gz 664e52347ed893c91952a85d507cd6fe 3989 utils extra fakeroot-ng_0.10-1.diff.gz 3707c61daaebf590934a8c7d52ab85f0 44994 utils extra fakeroot-ng_0.10-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhNW3gACgkQg8ByFc29vOLwxwCeJVxa/npQU+KmUGRzfXzfaQGs wrgAnRiovSdRxZY0Jl8pIGZesgcOgwBc =iIWf -END PGP SIGNATURE- Accepted: fakeroot-ng_0.10-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.10-1.diff.gz fakeroot-ng_0.10-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.10-1.dsc fakeroot-ng_0.10-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.10-1_i386.deb fakeroot-ng_0.10.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.10.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.11-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 09 Jun 2008 20:47:55 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.11-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.11-1) unstable; urgency=low . * New upstream version * Fixes problem with vfork and fork Checksums-Sha1: 04389bd5c1981ece335a120b468f27cdf1b92596 1023 fakeroot-ng_0.11-1.dsc cb693d389cf5beba9325838f500c64aadee3f8ca 387840 fakeroot-ng_0.11.orig.tar.gz 059f70b1c740340a79dfb29fc7b03a2c9bf37dea 3925 fakeroot-ng_0.11-1.diff.gz 55fb68fb173468ca2d4fa74d0d76cccbbe41fa8e 45150 fakeroot-ng_0.11-1_i386.deb Checksums-Sha256: 779a8ecb1a26bc936330f3e13c07662073b8050c00263f2dfdbd4b629d3937fe 1023 fakeroot-ng_0.11-1.dsc 811810cc291bf57a15870e660d2a4ed09ff937883283bfcce5568ef4eacf6390 387840 fakeroot-ng_0.11.orig.tar.gz 05adf7a4f1b97185dea560af6839b83571447fac24e39ef18f68dc3da7358d8b 3925 fakeroot-ng_0.11-1.diff.gz d4911c91d8087d752f46ee9271f2503d2e6b39667f028576fbaba2c24fb56333 45150 fakeroot-ng_0.11-1_i386.deb Files: 318f1d87e2f913e7d7ac9d4f9ad21dc8 1023 utils extra fakeroot-ng_0.11-1.dsc aae3e2331f44d208c5d5df346c75ec43 387840 utils extra fakeroot-ng_0.11.orig.tar.gz f4eccf487e55be070c3c737aa3cbe9ff 3925 utils extra fakeroot-ng_0.11-1.diff.gz 5d9cb52ce91bd8e833b9f6c135a69fb8 45150 utils extra fakeroot-ng_0.11-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkhNmYUACgkQg8ByFc29vOLPQQCaA3mkvMlvzmMVlgAPcaJtswhk hvgAoKaqz+ZYEu3EM74Pg/PCwvooWOCB =DVrS -END PGP SIGNATURE- Accepted: fakeroot-ng_0.11-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.11-1.diff.gz fakeroot-ng_0.11-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.11-1.dsc fakeroot-ng_0.11-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.11-1_i386.deb fakeroot-ng_0.11.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.11.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.10-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 24 May 2008 06:51:59 + Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.10-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.10-1) unstable; urgency=low . * New upstream release Checksums-Sha1: ed8067488ff3e277bcb808a018e9fc764ec360f1 1003 rsyncrypto_1.10-1.dsc ef5cca2b25fdeaffec5445317d9a6c2569d04b24 420234 rsyncrypto_1.10.orig.tar.gz 93c424a6bc1b0ba1367ad57083390905ca667c12 26697 rsyncrypto_1.10-1.diff.gz 47f3ee1b84e24d4fe8e15381a064978c417a2ecd 303718 rsyncrypto_1.10-1_i386.deb Checksums-Sha256: 1c8ed152fe82234e830cf8c1561eacc2b75ee5fa803e179a39543589c3da91d6 1003 rsyncrypto_1.10-1.dsc 2df38d8fd5a003210fc7633bd4594fd3742f26415197c84ceb02e40dc062834e 420234 rsyncrypto_1.10.orig.tar.gz 58ea46014586ae5661e54c245d95c90bfce796fc5e2388e7d43ebc0502010081 26697 rsyncrypto_1.10-1.diff.gz 25cc15624c6df7ce31b5f3aba4f3dbb18c3203c1ed578160e8dacd13faa2d21c 303718 rsyncrypto_1.10-1_i386.deb Files: c68f00603fa14e1cdccbb58294da2fa0 1003 utils optional rsyncrypto_1.10-1.dsc a69f577a71a407e8c5a9acd5eb09fc50 420234 utils optional rsyncrypto_1.10.orig.tar.gz e6b64edfdf3a981b1c8a66113de8c241 26697 utils optional rsyncrypto_1.10-1.diff.gz 2f335944985ca718fa74c0deb33c 303718 utils optional rsyncrypto_1.10-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIN9KPg8ByFc29vOIRAsWUAKCSbl3YlPO959KWYrweFOeHzoYRWQCggLKX fFvaAaYKAl2Z+W0l9eL1nOQ= =0YB+ -END PGP SIGNATURE- Accepted: rsyncrypto_1.10-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.10-1.diff.gz rsyncrypto_1.10-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.10-1.dsc rsyncrypto_1.10-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.10-1_i386.deb rsyncrypto_1.10.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.10.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.09-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 15 May 2008 15:09:43 +0300 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.09-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.09-1) unstable; urgency=low . * New upstream release * New tool, rsyncrypto_recover, for recovering corrupted file maps Checksums-Sha1: a729e0be43f18ede9ad7734a2666575c88120edc 1003 rsyncrypto_1.09-1.dsc 8bf4b0bed9f8a57427003df3ab7e18939bdf3f67 418717 rsyncrypto_1.09.orig.tar.gz 16dec51a1dfc116f8a8b90a744929cfc1ac92543 26842 rsyncrypto_1.09-1.diff.gz e5fef4d7702efa9bae389987eb284ee4b0f88561 300456 rsyncrypto_1.09-1_i386.deb Checksums-Sha256: d4c47eaa7e3af929ba8b7da1696e5dc2f38007eb3826caba7bb64dbe2f32014a 1003 rsyncrypto_1.09-1.dsc af9d3bc690a36905c108db9636ea6b47cbc37da0f6ecdd099b30216d954c88c7 418717 rsyncrypto_1.09.orig.tar.gz 7ea78b55b08fee24cd3190f2db0ed43c643370eb158792740f1c7c6a026d3e20 26842 rsyncrypto_1.09-1.diff.gz c04ce84371331cd974c4c76d2a35ce287318d9ca6b894a3c3b598e1d15eb8f7b 300456 rsyncrypto_1.09-1_i386.deb Files: 63fc8d36570ff5c33ce678c28ea9b0cb 1003 utils optional rsyncrypto_1.09-1.dsc 1fc648f9533ded3ab24e6316f869c3e4 418717 utils optional rsyncrypto_1.09.orig.tar.gz c7d76170809166b5830879e236a56f9f 26842 utils optional rsyncrypto_1.09-1.diff.gz b35d262d0cc8ffc8cafba067ee01964c 300456 utils optional rsyncrypto_1.09-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFILCxdg8ByFc29vOIRAve9AJ4l5h5LyGcQn/QYlqg8cNXKQE8NDgCeOPQX aszcUtyYVWZHcr/2w/x6m5o= =m3WW -END PGP SIGNATURE- Accepted: rsyncrypto_1.09-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.09-1.diff.gz rsyncrypto_1.09-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.09-1.dsc rsyncrypto_1.09-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.09-1_i386.deb rsyncrypto_1.09.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.09.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.08-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 May 2008 18:51:25 +0300 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.08-2 Distribution: unstable Urgency: high Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.08-2) unstable; urgency=high (fixes corruption of filemap file under certain circumstance) . * Backport of critical path to prevent rsyncrypto from corrupting its own map files. Checksums-Sha1: 4f13895b199f0fda74a9ac93d2a83eec3af2b6d7 1003 rsyncrypto_1.08-2.dsc 183477aef2c228cf4879e927db0dfe48fb966eea 27432 rsyncrypto_1.08-2.diff.gz d89b5439de8ede77cc8c0d14e6d23122de3bde32 294716 rsyncrypto_1.08-2_i386.deb Checksums-Sha256: 5a5328bad87554a732266acc812b3cc16214bb81c4be38c9a3eb1e838a594ea0 1003 rsyncrypto_1.08-2.dsc bbad87d5736bc7dae6ecf1df55d91da5b78ad2d82a16d75e2258f53319e26d1e 27432 rsyncrypto_1.08-2.diff.gz b0f70d70f41f46220c93f3b6b3533a2fe8dabea27bbdd925ca9b17466201620c 294716 rsyncrypto_1.08-2_i386.deb Files: 304af8052d22922884e3bff9cd95200e 1003 utils optional rsyncrypto_1.08-2.dsc b6641f5e856e4d11fa99b217753495a0 27432 utils optional rsyncrypto_1.08-2.diff.gz 2dd38360648215bd05559b007cb1e95f 294716 utils optional rsyncrypto_1.08-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIKcB+g8ByFc29vOIRAlZwAJ9yRHYD9ZFIZLb6AX6ht7p7r5OIXACeOg+v /EBARJ9relG8liaQiDRC/jE= =4zh4 -END PGP SIGNATURE- Accepted: rsyncrypto_1.08-2.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.08-2.diff.gz rsyncrypto_1.08-2.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.08-2.dsc rsyncrypto_1.08-2_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.08-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.08-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 11 May 2008 20:49:21 +0300 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.08-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.08-1) unstable; urgency=low . * New upstream version Checksums-Sha1: 69e56a49f1d205e4244efd3a353f7fac395910ee 1003 rsyncrypto_1.08-1.dsc e8d23228d17a433cf9c2f8d5be89d500e6974247 403206 rsyncrypto_1.08.orig.tar.gz 22060f6db1df9a787ae3af3b411bdfb11cf4e8d7 26876 rsyncrypto_1.08-1.diff.gz 05e39dae32db73a2be640a1f6c46c5d3c4aa0541 294598 rsyncrypto_1.08-1_i386.deb Checksums-Sha256: 1ec3780d369b58a530d1e6633c157d2934c683ab78e5830d795c40affb413022 1003 rsyncrypto_1.08-1.dsc 77d22baab984502cfa85585dff72ce1de55ccee4c7f88ba060b8c7489cfe883d 403206 rsyncrypto_1.08.orig.tar.gz 625e962abb525deee70c072bee0792f6c66d50afa6449296e19ee8545ea25d20 26876 rsyncrypto_1.08-1.diff.gz 2ef359f8a75b91105ddd93f16662d5080350bd62937d3c4e80653c7851ac1c01 294598 rsyncrypto_1.08-1_i386.deb Files: fb2b953532f8a138251c30801f5cb105 1003 utils optional rsyncrypto_1.08-1.dsc 48a3efbfd8e4aea58f529bf09abb9e21 403206 utils optional rsyncrypto_1.08.orig.tar.gz 7b39188de4653ad8df707dfbbff0c486 26876 utils optional rsyncrypto_1.08-1.diff.gz 22a0cc6912070a0c947599b612e52864 294598 utils optional rsyncrypto_1.08-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIJznHg8ByFc29vOIRAimwAJ98gZAwIopslTJOeLLSpBh/tGpwnQCfaR4S i47EseHxk0xWoCELORIJ8pE= =Fa14 -END PGP SIGNATURE- Accepted: rsyncrypto_1.08-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.08-1.diff.gz rsyncrypto_1.08-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.08-1.dsc rsyncrypto_1.08-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.08-1_i386.deb rsyncrypto_1.08.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.08.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted argtable2 9-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 07 May 2008 19:54:52 + Source: argtable2 Binary: libargtable2-dev libargtable2-docs libargtable2-0 Architecture: source i386 all Version: 9-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: libargtable2-0 - A library for parsing GNU style command line arguments libargtable2-dev - A library for parsing GNU style command line arguments libargtable2-docs - A library for parsing GNU style command line arguments Changes: argtable2 (9-1) unstable; urgency=low . * New upstream version. Checksums-Sha1: fa165f7fa0c8fb86d8663f634b1cb0c7c10421a4 993 argtable2_9-1.dsc 78cc8676ee90cfae3bbcf62a4427d42ffdc33acf 3364642 argtable2_9.orig.tar.gz 524f4ea63ca8a06a1943e658d366b48fb2acc7a4 40436 argtable2_9-1.diff.gz 6419438963eda68410f553af58039610cf6809a4 39330 libargtable2-dev_9-1_i386.deb f390c587be065a3deb7085861a73fcc2b184df46 2963174 libargtable2-docs_9-1_all.deb a917d8d4ec2673135575a8f354f65d5e4a734550 13240 libargtable2-0_9-1_i386.deb Checksums-Sha256: fccca008fe87ad3c431c760fe1b0a72580f65b75a4c6f1cff77b681b049af44f 993 argtable2_9-1.dsc 6d43739df542b1afe00e6792c32523465300db8fc9691389e68a9239b225d683 3364642 argtable2_9.orig.tar.gz 82ccde9f752b94768c9da3eb8da3c73886fd9a1f664870805d9b50068213e60c 40436 argtable2_9-1.diff.gz 131ca78ed02719699a42440a602b01aaa5035c7c600ef7cad715a9838e9bf04c 39330 libargtable2-dev_9-1_i386.deb 973bad85870981aa0ee856f0bde8fdc08355252ba05ae36e5761b3c96ec0a6b6 2963174 libargtable2-docs_9-1_all.deb b7ba52b64f1656f76294481820803422da3a4df619c252ceea0cb4c2bf61e4a9 13240 libargtable2-0_9-1_i386.deb Files: f2f436dc1e60e3c665af33a80b8e6e3e 993 libs optional argtable2_9-1.dsc a7fcddef768db0ae66534ec4c4a51dee 3364642 libs optional argtable2_9.orig.tar.gz c9f9d0f870bfd4d13f4625936aa8655f 40436 libs optional argtable2_9-1.diff.gz f04a14b2653aedc592a7c5b2ec0d7fde 39330 libdevel optional libargtable2-dev_9-1_i386.deb c4d99bf1d76937e7bfb12bfefe3a5216 2963174 doc optional libargtable2-docs_9-1_all.deb 7e596a60e2dbbe4e47d7fc7cbcdf3d84 13240 libs optional libargtable2-0_9-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIIhYlg8ByFc29vOIRAnasAJ91w+fov9hp2q8+hX/qmLf94H9+OwCfS77R ZWp2LtxeJkReS5tyDZDvktY= =Qpf2 -END PGP SIGNATURE- Accepted: argtable2_9-1.diff.gz to pool/main/a/argtable2/argtable2_9-1.diff.gz argtable2_9-1.dsc to pool/main/a/argtable2/argtable2_9-1.dsc argtable2_9.orig.tar.gz to pool/main/a/argtable2/argtable2_9.orig.tar.gz libargtable2-0_9-1_i386.deb to pool/main/a/argtable2/libargtable2-0_9-1_i386.deb libargtable2-dev_9-1_i386.deb to pool/main/a/argtable2/libargtable2-dev_9-1_i386.deb libargtable2-docs_9-1_all.deb to pool/main/a/argtable2/libargtable2-docs_9-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.07-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 07 May 2008 21:05:14 + Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.07-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.07-1) unstable; urgency=low . * New upstream version Checksums-Sha1: 7831675dc3e2171c9e3d9dbab2b8935dc194a4f3 1003 rsyncrypto_1.07-1.dsc a023e75c77742ce0505ad9296e9d6e252859f559 402769 rsyncrypto_1.07.orig.tar.gz 46ab3e658e27fab00ac9cb4d5098ffe026de72c7 26861 rsyncrypto_1.07-1.diff.gz 2d318832aff23979549ab6313327c4715a784d66 294124 rsyncrypto_1.07-1_i386.deb Checksums-Sha256: 77d9463ca34a5af07a61871aae456a15632af312ca8a1e42564ad159e04b4de7 1003 rsyncrypto_1.07-1.dsc 6ce6f2832c634d97d3f21197e4d6cc4c7410c7b204fea5ecf612990bac0ad658 402769 rsyncrypto_1.07.orig.tar.gz c032a6fe72b62874c41f377dc97088d834a32d4efda2f42b6794c22234d9bbba 26861 rsyncrypto_1.07-1.diff.gz 84ed34709af6933122bb6ef36b49786a1c5719d4458f368fb0c69c3f51b7 294124 rsyncrypto_1.07-1_i386.deb Files: 33faac64302d783d363b5c668a5167c8 1003 utils optional rsyncrypto_1.07-1.dsc f5231a85a2c706faaa89e0ec8e78ca1a 402769 utils optional rsyncrypto_1.07.orig.tar.gz 19b0a2057d076791c2411a951aa8e63c 26861 utils optional rsyncrypto_1.07-1.diff.gz 2d3d16199f48e3b6b794193b623c9142 294124 utils optional rsyncrypto_1.07-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIIhpPg8ByFc29vOIRAtBUAKCkCdf2VlXzd26depPl6zUj7TdmdACePWQx ui7sDbaZMpPM9F7qBnhBpbU= =i/xq -END PGP SIGNATURE- Accepted: rsyncrypto_1.07-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.07-1.diff.gz rsyncrypto_1.07-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.07-1.dsc rsyncrypto_1.07-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.07-1_i386.deb rsyncrypto_1.07.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.07.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.09-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 12 Apr 2008 12:28:35 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.09-2 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Closes: 474793 Changes: fakeroot-ng (0.09-2) unstable; urgency=low . * FTBFS: arch/platform.h:17: error: 'pid_t' has not been declared (Closes: #474793) * Merge support for gcc 4.3 from upstream SVN Checksums-Sha1: cac23a055533ac5957bbb10e73e74ca3e3affe4c 1013 fakeroot-ng_0.09-2.dsc cbdf820f3cbdfdbc500b7756e3f44430388dd9e9 3822 fakeroot-ng_0.09-2.diff.gz a9ba1c30e28c42756262e1f79e1017ce7182b51f 38920 fakeroot-ng_0.09-2_i386.deb Checksums-Sha256: 84ba33730a50060ae6216a12c171089fb86caf9c3ca74fb478cf61c2190a4f20 1013 fakeroot-ng_0.09-2.dsc fc5ac8147aabe631eb73cceee6310593bcc8187e9840994dd711ffc431288117 3822 fakeroot-ng_0.09-2.diff.gz d8c0957e125b1105e967ba56aa265884c4fbf19efe84bbf7d896429fd4b38340 38920 fakeroot-ng_0.09-2_i386.deb Files: 5bbec1775661f25ede2561594414cc6a 1013 utils extra fakeroot-ng_0.09-2.dsc 23b295d1fb5111dc2547b6e34f133ccd 3822 utils extra fakeroot-ng_0.09-2.diff.gz cbf80cb76f62b21b6b25a68ce399d918 38920 utils extra fakeroot-ng_0.09-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIAK3sg8ByFc29vOIRAltYAKCGee7eCdX/Zn7dE0yMx5HzxgrlXwCfQcBi o2B89sDt3Q2KEIfn4ljaOIo= =j/NF -END PGP SIGNATURE- Accepted: fakeroot-ng_0.09-2.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.09-2.diff.gz fakeroot-ng_0.09-2.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.09-2.dsc fakeroot-ng_0.09-2_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.09-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.09-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Mar 2008 15:21:55 +0200 Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.09-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.09-1) unstable; urgency=low . * New upstream release * Now supports strace on AMD64 platform Files: 694b7bfc51c6dfb44b46d6a61b4cc05b 625 utils extra fakeroot-ng_0.09-1.dsc 998cc8f437f9bc677d123cdbb1f87a07 753542 utils extra fakeroot-ng_0.09.orig.tar.gz 9ad525622f2a0f9f882acbf2fd153e19 3645 utils extra fakeroot-ng_0.09-1.diff.gz 9053d3e562988c38ab7de5d64caa6daa 38618 utils extra fakeroot-ng_0.09-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH29VTg8ByFc29vOIRAtt2AJ91NLbzebBS3+Md65glXNCBmvFvhACcC/gb l/jLQg4aVMqNaPq/6f4mkQE= =mxUg -END PGP SIGNATURE- Accepted: fakeroot-ng_0.09-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.09-1.diff.gz fakeroot-ng_0.09-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.09-1.dsc fakeroot-ng_0.09-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.09-1_i386.deb fakeroot-ng_0.09.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.09.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Lintian over sensitivity?
Hi all, I'm packaging a new version of fakeroot-ng, and I get the following warning from Lintian -iI: W: fakeroot-ng: copyright-without-copyright-notice N: N: The copyright file for this package does not appear to contain a N: copyright notice. You should copy the copyright notice from the N: upstream source (or add one of your own for a native package). A N: copyright notice must consist of Copyright, Copr., or the Unicode N: symbol of C in a circle followed by the years and the copyright N: holder. N: N: If the package is in the public domain rather than copyrighted, be N: sure to mention public domain in the copyright file. Please be aware N: that this is very rare and not the same as a DFSG-free license. True N: public domain software is generally limited to such special cases as a N: work product of a United States government agency. N: N: Refer to http://ftp-master.debian.org/REJECT-FAQ.html for details. N: This is the copyright file: his package was debianized by Shachar Shemesh [EMAIL PROTECTED] on Tue, 08 Jan 2008 20:27:55 +. It was downloaded from http://sourceforge.net/projects/fakerootng Fakeroot-ng is copyrighted (C) 2007-2008 by Shachar Shemesh Further copyright and credits can be found at /usr/share/doc/fakeroot-ng/AUTHORS License: This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This package is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this package; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA On Debian systems, the complete text of the GNU General Public License can be found in `/usr/share/common-licenses/GPL'. The Debian packaging is (C) 2008, Shachar Shemesh [EMAIL PROTECTED] and is licensed under the GPL, see above. At least superficially, the copyright file lives up to all of the requirements that lintian asks for. Lintian version 1.23.45 Changing the line to read: Copyright (C) 2007-2008 by Shachar Shemesh pacifies lintian, but I still think this is over sensitivity on its behalf. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.08-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Feb 2008 16:32:47 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.08-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Closes: 465042 Changes: fakeroot-ng (0.08-1) unstable; urgency=low . * New upstream release * New platform supported - AMD64 (Closes: #465042) * New porting HOWTO for yet unsupported platforms Files: e07be5305dafa02f2fe9a23537796ba0 625 utils extra fakeroot-ng_0.08-1.dsc 05a5f4dd62cffb1d57156a1e70f1281d 752751 utils extra fakeroot-ng_0.08.orig.tar.gz e7ebaf85b72e1ffdea760bb2757e3a29 3608 utils extra fakeroot-ng_0.08-1.diff.gz 167ba109e164e10b25fb32996eee1530 38530 utils extra fakeroot-ng_0.08-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHvFmCg8ByFc29vOIRAj/dAJ4mUI34Z90BWF+amx5FqNzS8yln7ACeKtmz i8WfBZjkeSp4cFw/T8vP6kI= =/Omc -END PGP SIGNATURE- Accepted: fakeroot-ng_0.08-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.08-1.diff.gz fakeroot-ng_0.08-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.08-1.dsc fakeroot-ng_0.08-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.08-1_i386.deb fakeroot-ng_0.08.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.08.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.06-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 06 Feb 2008 17:21:17 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.06-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Closes: 463697 Changes: fakeroot-ng (0.06-1) unstable; urgency=low . * New upstream release * Support for all *at Linux syscalls (openat, fstatat etc.) (Closes: #463697) * Much better strace support (still no -f support) Files: bedf80ef584b6680cc729164ad38a062 620 utils extra fakeroot-ng_0.06-1.dsc 79d00d8572a45120bc2de3b413ec6b54 728892 utils extra fakeroot-ng_0.06.orig.tar.gz e1d0206ccec89d90deb292b18877149c 14374 utils extra fakeroot-ng_0.06-1.diff.gz 75e9078c656e0549e2885a0f7c3f0521 32804 utils extra fakeroot-ng_0.06-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHqgudg8ByFc29vOIRAmR0AJ4hUU9k5XWcfHKv4DOOf2jT9vARNgCfZtH1 V24Bpkfivnz6CUwNKCwrGco= =JYFr -END PGP SIGNATURE- Accepted: fakeroot-ng_0.06-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.06-1.diff.gz fakeroot-ng_0.06-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.06-1.dsc fakeroot-ng_0.06-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.06-1_i386.deb fakeroot-ng_0.06.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.06.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.05-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 31 Jan 2008 14:47:59 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.05-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.05-1) unstable; urgency=low . * New upstream release - add (slightly limited) support for strace inside fakeroot Files: 1caeb54acedacb2f4aff0edd08ae9572 619 utils extra fakeroot-ng_0.05-1.dsc d8e7fc16aa65577d48aa954038a90182 726983 utils extra fakeroot-ng_0.05.orig.tar.gz 501f6e3816c9057f971320f9e12cd6f0 3578 utils extra fakeroot-ng_0.05-1.diff.gz 59053d5530b0e0b1649149ce14adb7b9 31736 utils extra fakeroot-ng_0.05-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHogG2g8ByFc29vOIRAv10AJ0fpFCsjOjmms8YyqKgFfiBk/fu0ACfXAVf dBvOQRfja867uT94pJtb2yM= =c70F -END PGP SIGNATURE- Accepted: fakeroot-ng_0.05-1.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.05-1.diff.gz fakeroot-ng_0.05-1.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.05-1.dsc fakeroot-ng_0.05-1_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.05-1_i386.deb fakeroot-ng_0.05.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.05.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.06-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 22 Jan 2008 13:17:40 + Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.06-2 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Closes: 459123 Changes: rsyncrypto (1.06-2) unstable; urgency=low . * Closes: #459123: rsyncrypto: FTBFS with dash * Made the test script depend on bash - contains dependency on regular expression globs. Files: 5fcd8ff86f20020013dc2dbbe2d40890 619 utils optional rsyncrypto_1.06-2.dsc 370ec53665d94e7f1acc8cadb6b00a43 27298 utils optional rsyncrypto_1.06-2.diff.gz 7df03d115544beb1df63fc1cdb123b34 293426 utils optional rsyncrypto_1.06-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHlfoZg8ByFc29vOIRAogpAKCI/myDv8PwXOtR1drispMdIk/O8gCeP89T Yr9qWoNwNtRqTJ7v9vEOEV8= =f5+f -END PGP SIGNATURE- Accepted: rsyncrypto_1.06-2.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.06-2.diff.gz rsyncrypto_1.06-2.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.06-2.dsc rsyncrypto_1.06-2_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.06-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted fakeroot-ng 0.04-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 12 Jan 2008 20:08:06 + Source: fakeroot-ng Binary: fakeroot-ng Architecture: source i386 Version: 0.04-2 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: fakeroot-ng - Gives a fake root environment Changes: fakeroot-ng (0.04-2) unstable; urgency=low . * Fix copyright file to list copyright holders (ftpmasters feedback) Files: 33a9c3e129766cbf25210b011d1e9808 619 utils extra fakeroot-ng_0.04-2.dsc 31c80bbfa6013b5e0ab2346521ce50fd 713880 utils extra fakeroot-ng_0.04.orig.tar.gz 5045414702cff16e7cc797013d5bf347 3551 utils extra fakeroot-ng_0.04-2.diff.gz bcde442130ba99d3a4676864a01afc6c 23022 utils extra fakeroot-ng_0.04-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHiSUNg8ByFc29vOIRAlFTAJ947bbeKcmNh9j9mGgimsyTEQgxYgCgrW+o L1iIn4Da4ZB6oa2g6Jp0atc= =9zbA -END PGP SIGNATURE- Accepted: fakeroot-ng_0.04-2.diff.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.04-2.diff.gz fakeroot-ng_0.04-2.dsc to pool/main/f/fakeroot-ng/fakeroot-ng_0.04-2.dsc fakeroot-ng_0.04-2_i386.deb to pool/main/f/fakeroot-ng/fakeroot-ng_0.04-2_i386.deb fakeroot-ng_0.04.orig.tar.gz to pool/main/f/fakeroot-ng/fakeroot-ng_0.04.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Reordering the boot for fun and profit
Petter Reinholdtsen wrote: And of course, it also make it possible to dynamically order the scripts based on their dependencies. When you said and of course, I thought you were going to say allow scripts that have no inter-dependency to start in parallel. Having a concurrency level of at least 2 should speed the start up considerably, especially when packages are taking long to start mostly because they do a sleep in wait for some hardware to settle. Coming to think of it, maybe concurrency level of 2 is a little low. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted sshpass 1.01-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 09 Jan 2008 10:12:33 + Source: sshpass Binary: sshpass Architecture: source i386 Version: 1.01-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: sshpass- Non-interactive ssh password authentication Closes: 408707 441083 Changes: sshpass (1.01-1) unstable; urgency=low . * New upstream release * Update policy version to 3.7.3 (no changes necessary) * sshpass now passes tty resize to ssh (upstream fix) (Closes: #441083) * Package now recommends ssh-client instead of depending on ssh (Closes: #408707) Files: a7bc8731276022b28d08ca4f7cc737a5 576 utils extra sshpass_1.01-1.dsc a192bf3325144150e7ed6901ff2ffe54 81364 utils extra sshpass_1.01.orig.tar.gz 41b70075211c88d3b9be69e3db28d1e0 25593 utils extra sshpass_1.01-1.diff.gz 0994622950ec7ddeadf4f78ba7827907 8272 utils extra sshpass_1.01-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHhJ9mg8ByFc29vOIRAhYyAJ4rkcsD1fgqi8RjjCibhkhPA4lURQCfTHD2 mttzmnM8E1zT40UtnUmE9YI= =kdLZ -END PGP SIGNATURE- Accepted: sshpass_1.01-1.diff.gz to pool/main/s/sshpass/sshpass_1.01-1.diff.gz sshpass_1.01-1.dsc to pool/main/s/sshpass/sshpass_1.01-1.dsc sshpass_1.01-1_i386.deb to pool/main/s/sshpass/sshpass_1.01-1_i386.deb sshpass_1.01.orig.tar.gz to pool/main/s/sshpass/sshpass_1.01.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.06-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 28 Nov 2007 16:21:09 +0200 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.06-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.06-1) unstable; urgency=low . * New upstream release Files: 6bde187b4b7c8058b8747ee5e53455c8 617 utils optional rsyncrypto_1.06-1.dsc b5a170edcc150ac550c0bda990a098b4 407932 utils optional rsyncrypto_1.06.orig.tar.gz 8d130d4bcde6cd0fe448083454048580 26772 utils optional rsyncrypto_1.06-1.diff.gz fb8d3d860dda0bbfcb9e9222824ad738 293234 utils optional rsyncrypto_1.06-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHTXmGg8ByFc29vOIRAq9iAKCOLpYYJ4/+Q6vI43jmRA1t/gbJegCbB0a8 ih/fOz+3arBB8lxAMKGvNKw= =TFPX -END PGP SIGNATURE- Accepted: rsyncrypto_1.06-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.06-1.diff.gz rsyncrypto_1.06-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.06-1.dsc rsyncrypto_1.06-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.06-1_i386.deb rsyncrypto_1.06.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.06.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted argtable2 7-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 19 Nov 2007 13:00:52 +0200 Source: argtable2 Binary: libargtable2-dev libargtable2-0 Architecture: source i386 Version: 7-2 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: libargtable2-0 - A library for parsing GNU style command line arguments libargtable2-dev - A library for parsing GNU style command line arguments Closes: 451899 Changes: argtable2 (7-2) unstable; urgency=low . * argtable2 - FTBFS: No rule to make target `distclean#39;. Stop. (Closes: #451899) Files: 48ed564fc85d0ed4496e2a64a681cd61 600 libs optional argtable2_7-2.dsc e842e885045b28dfacd784f8de0dc094 39351 libs optional argtable2_7-2.diff.gz c65f502e6d4b333ad2f7b775fd7f1161 3001752 libdevel optional libargtable2-dev_7-2_i386.deb 0eecf1717f41414cd51771413285c5e0 13144 libs optional libargtable2-0_7-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHQW5jg8ByFc29vOIRAkB5AKCK5cCzDBJNnge7q8rViFDbJUSnTQCgs2nG mpkn7KB8Y1hm3989qK9Horo= =NGrv -END PGP SIGNATURE- Accepted: argtable2_7-2.diff.gz to pool/main/a/argtable2/argtable2_7-2.diff.gz argtable2_7-2.dsc to pool/main/a/argtable2/argtable2_7-2.dsc libargtable2-0_7-2_i386.deb to pool/main/a/argtable2/libargtable2-0_7-2_i386.deb libargtable2-dev_7-2_i386.deb to pool/main/a/argtable2/libargtable2-dev_7-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted argtable2 7-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 18 Nov 2007 09:39:23 +0200 Source: argtable2 Binary: libargtable2-dev libargtable2-0 Architecture: source i386 Version: 7-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: libargtable2-0 - A library for parsing GNU style command line arguments libargtable2-dev - A library for parsing GNU style command line arguments Changes: argtable2 (7-1) unstable; urgency=low . * New upstream release Files: 197ee32b8ee6e0a8ff9663a371b22b68 600 libs optional argtable2_7-1.dsc a84130293aab3bc09631cbee717ede93 3347056 libs optional argtable2_7.orig.tar.gz 634a3c3a28771afcf75b1331d7136148 39270 libs optional argtable2_7-1.diff.gz 75fcf9914cb99023d4af9efac2db6433 3001668 libdevel optional libargtable2-dev_7-1_i386.deb caf22740df6b923ce74c08b4d9b0e9f3 13068 libs optional libargtable2-0_7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHP+75g8ByFc29vOIRAvECAJ9Yy5tzBHCv+5VxBFKg0jZsrpzGmACeK0Ow dhGYHFWhZSIM5Z7wtzPcwmU= =pSzg -END PGP SIGNATURE- Accepted: argtable2_7-1.diff.gz to pool/main/a/argtable2/argtable2_7-1.diff.gz argtable2_7-1.dsc to pool/main/a/argtable2/argtable2_7-1.dsc argtable2_7.orig.tar.gz to pool/main/a/argtable2/argtable2_7.orig.tar.gz libargtable2-0_7-1_i386.deb to pool/main/a/argtable2/libargtable2-0_7-1_i386.deb libargtable2-dev_7-1_i386.deb to pool/main/a/argtable2/libargtable2-dev_7-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 1.05-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 18 Nov 2007 09:24:40 +0200 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 1.05-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (1.05-1) unstable; urgency=low . * New upstream release Files: 7d2db04f9bf95cc5e3d02a674f175127 617 utils optional rsyncrypto_1.05-1.dsc 6ac7d66e33f5fdb45e4e1ea37f52d646 401368 utils optional rsyncrypto_1.05.orig.tar.gz 6e629baaa249ed304360291126a6154b 26756 utils optional rsyncrypto_1.05-1.diff.gz cc091d0dbabaf5765f26ccfd581a1077 292504 utils optional rsyncrypto_1.05-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHP/P4g8ByFc29vOIRAqoyAJ9V5eoa7kZ46aclqX7EOu24cqoyJgCgnKpk 3jXjkv1mvOY048JGiMS7+MA= =Jz5K -END PGP SIGNATURE- Accepted: rsyncrypto_1.05-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_1.05-1.diff.gz rsyncrypto_1.05-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_1.05-1.dsc rsyncrypto_1.05-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_1.05-1_i386.deb rsyncrypto_1.05.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_1.05.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Packaging a library that requires cross-compiled code
David Anderson wrote: Therefore, question: how should I get from this situation to having a working .deb (including the cross-compiled driver), while at the same time playing nicely with Debian packaging policies? In the general case, the problem is much wider. Let me give you an example. We currently package Xen and other free virtualization solutions. Some of them can even run proprietary OSes, such as Windows. Now, suppose that one would like to improve the way Windows runs under Xen by writing, say, a custom mouse driver for Windows that para-virtualizes the mouse on Windows. Such things are quite common in todays' world. The problem is that this driver is a kernel level driver for Windows. If it were user space we could still claim it could be compiled with cross-mingw, but this is not the case here. Setting up an environment for compiling Windows kernel drivers merely so we can build this tiny blob seems out of proportion. I think we need a change in policy for handling cases where free software requires free software in order to compile which is, non the less, non buildable on the same platform. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to start porting to a new ARCHITECTURE?
David Given wrote: You've got two major tasks ahead of you: - - port gcc - - port the kernel - - cross-compile a basic userland Nobody expects the Spanish inquisition. Actually, there is one more major headache, which is porting a boot loader. Probably uBoot or something similar. Memory needs to be set up so it can be accessed by the kernel, the kernel (and initrd) pulled from the flash, and flow passed into it. If the system uses hardware controllers that exist elsewhere, the kernel port may be easier than that. It may be that the system has an ethernet controller that is already supported under Linux. Of course, the startup code and everything else under the arch directory will still need to be handled, but at least as far as the drivers are concerned, some work may be saved. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Non-security updates between stable releases?
Tim Hull wrote: I knew about that, though it's not actually an official Debian repository (to my knowledge). If I were looking for a date that was tall yes compact, what would you tell me? How about a date with fair brown eyes? What you are asking for is a contradiction. There are only two ways to update stable once it's out: Issue another stable or lie about its stability. There are specific exceptions to this rule. In particular, not updating certain programs is, in itself, a problem. One such example is an anti-virus, which needs fresh definitions, and sometimes, fresh code as well. If that is where your interests lie, I suggest you have a look at the debian-volatile repository. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted privbind 1.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 10 Jul 2007 13:59:32 +0300 Source: privbind Binary: privbind Architecture: source i386 Version: 1.1-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: privbind - Allow unprivileged apps to bind to a privileged port Changes: privbind (1.1-1) unstable; urgency=low . * New upstream release * Cleanup the debian/rules file from dh_make cruft * Fix lintian error on calling make distclean and ignoring error Files: 9738392f8bc01f441f50f0887afa2a5b 573 utils extra privbind_1.1-1.dsc f5345e834aad62897dae4643a6cb5bd3 319484 utils extra privbind_1.1.orig.tar.gz 7cac76be9cc0d51f54be66e461e0fc42 4466 utils extra privbind_1.1-1.diff.gz 216a7d2afe561a1c9b46790fa9dffdfc 17162 utils extra privbind_1.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGk2b9g8ByFc29vOIRAkZjAJ4oczGt5eMpEodGdlABu6yTxP2CTwCeJlGd ZO5SIR8DYImoHnBSl8Ej38A= =9Tdx -END PGP SIGNATURE- Accepted: privbind_1.1-1.diff.gz to pool/main/p/privbind/privbind_1.1-1.diff.gz privbind_1.1-1.dsc to pool/main/p/privbind/privbind_1.1-1.dsc privbind_1.1-1_i386.deb to pool/main/p/privbind/privbind_1.1-1_i386.deb privbind_1.1.orig.tar.gz to pool/main/p/privbind/privbind_1.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted privbind 0.2-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 5 Jun 2007 16:34:16 +0300 Source: privbind Binary: privbind Architecture: source i386 Version: 0.2-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: privbind - Allow unprivileged apps to bind to a privileged port Closes: 427605 Changes: privbind (0.2-1) unstable; urgency=low . * Initial release (Closes: #427605) Files: 90c59b0b24e2d1504a6a0e4270b6ba21 573 utils extra privbind_0.2-1.dsc f2839b2ce2502970fc4e2b2bde334c63 315424 utils extra privbind_0.2.orig.tar.gz e62853efde27ee240ca2eab86ba0cff4 4442 utils extra privbind_0.2-1.diff.gz 434bf2e9650481148e501ee47f79c50a 14004 utils extra privbind_0.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGZaGQg8ByFc29vOIRAuC4AKC0QbLN6NF6fDtGksk3NbED4crbmACdEjbF PxAAcm0QnWvRGFYOLC6MhR0= =Pl1i -END PGP SIGNATURE- Accepted: privbind_0.2-1.diff.gz to pool/main/p/privbind/privbind_0.2-1.diff.gz privbind_0.2-1.dsc to pool/main/p/privbind/privbind_0.2-1.dsc privbind_0.2-1_i386.deb to pool/main/p/privbind/privbind_0.2-1_i386.deb privbind_0.2.orig.tar.gz to pool/main/p/privbind/privbind_0.2.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#427605: ITP: privbind -- Allow unprivileged apps to bind to a privileged port
Russell Coker wrote: On Tuesday 05 June 2007 16:52, Shachar Shemesh [EMAIL PROTECTED] wrote: Package: wnpp Severity: wishlist Owner: Shachar Shemesh [EMAIL PROTECTED] What benefits does this offer over authbind which has been in Debian for ages? It uses a (I think) much more secure mode of operation. In particular: - No SUID executables - User who launches the daemon must be root - Privileges go down, never up And, as a result: - No global configuration necessary (though one will probably be added later if necessary). Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#427605: ITP: privbind -- Allow unprivileged apps to bind to a privileged port
Russell Coker wrote: On Wednesday 06 June 2007 20:05, Shachar Shemesh [EMAIL PROTECTED] wrote: What benefits does this offer over authbind which has been in Debian for ages? Before I begin answering your questions, the bug report has a link to technical explanation of how privbind is implemented. Have you read it? It uses a (I think) much more secure mode of operation. In particular: - No SUID executables - User who launches the daemon must be root Having a daemon instead of a SUID executable does not inherently make it more secure (there has been no shortage of exploits for bugs in daemons in the past). s/daemon/program that needs low port binding/ privbind does not allow regular users to bind to low ports. Privbind allows root to run program that bind to low port as non-root. The usual system is that a process with UID != 0 can not bind to ports below 1024. Breaking this involves increasing the privileges of some programs. Please read the privbind man page. It does not do what you think it does. And, as a result: - No global configuration necessary (though one will probably be added later if necessary). How can there be no global configuration needed? Please read the privbind man page. It does not do what you think it does. The sysadmin needs to decide which users are granted the privilege to bind to low ports and which ports those users may bind to. Please read the privbind man page. It does not do what you think it does. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427605: ITP: privbind -- Allow unprivileged apps to bind to a privileged port
Package: wnpp Severity: wishlist Owner: Shachar Shemesh [EMAIL PROTECTED] * Package name: privbind Version : 0.2 Upstream Author : Shachar Shemesh [EMAIL PROTECTED] * URL : http://sourceforge.net/projects/privbind * License : GPL Programming Lang: C Description : Allow unprivileged apps to bind to a privileged port This program allows running another program as a non-root user, except the other program will be able to bind to privileged (1024) ports. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US, LC_CTYPE=he_IL (charmap=ISO-8859-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 0.19-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 21 Nov 2006 22:40:10 +0200 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 0.19-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (0.19-1) unstable; urgency=low . * New upstream release Files: 87ab8f7e7b1ef001f613c10e3461b9ef 617 utils optional rsyncrypto_0.19-1.dsc 2f886cf71034d76ee8d4e11c3a68d699 399906 utils optional rsyncrypto_0.19.orig.tar.gz f01a2d30b963eb789055639c0104078d 16956 utils optional rsyncrypto_0.19-1.diff.gz db3540d3d2ffb1b9da2e5442869c1e9a 292854 utils optional rsyncrypto_0.19-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFY2Wlg8ByFc29vOIRAh+LAJ0ZmPix0dDqUmW2RwZgRvPfGVBuGwCaAxgp eO4Bns+hmYNMHWkK4zy6QQY= =U+F0 -END PGP SIGNATURE- Accepted: rsyncrypto_0.19-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_0.19-1.diff.gz rsyncrypto_0.19-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_0.19-1.dsc rsyncrypto_0.19-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_0.19-1_i386.deb rsyncrypto_0.19.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_0.19.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bidiui 0.7.3-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 29 Oct 2006 15:08:17 +0200 Source: bidiui Binary: thunderbird-bidiui Architecture: source all Version: 0.7.3-1 Distribution: unstable Urgency: low Maintainer: Debian Hebrew Packaging Team [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: thunderbird-bidiui - BiDirectional support for Thunderbird Closes: 380711 Changes: bidiui (0.7.3-1) unstable; urgency=low . * Initial release (Closes: #380711) Files: 1d939143aa547d2d29ddf551ff016996 739 mail optional bidiui_0.7.3-1.dsc 66bdc4be56c189427ca625e1de9d9b46 94302 mail optional bidiui_0.7.3.orig.tar.gz 79bf4fb8e552f1d3af809bcc6d5d2366 9348 mail optional bidiui_0.7.3-1.diff.gz dedc8afe285dbf2d281d96a81031677f 62772 mail optional thunderbird-bidiui_0.7.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFRLG+g8ByFc29vOIRAvA9AKCmMcqBeMU1lOMgNWgMzwsQ7vaUIQCfaDhO xCVvAmjl4HnBAWYcP+7Qwek= =RJ9S -END PGP SIGNATURE- Accepted: bidiui_0.7.3-1.diff.gz to pool/main/b/bidiui/bidiui_0.7.3-1.diff.gz bidiui_0.7.3-1.dsc to pool/main/b/bidiui/bidiui_0.7.3-1.dsc bidiui_0.7.3.orig.tar.gz to pool/main/b/bidiui/bidiui_0.7.3.orig.tar.gz thunderbird-bidiui_0.7.3-1_all.deb to pool/main/b/bidiui/thunderbird-bidiui_0.7.3-1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted bidiui 0.7.3-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 3 Nov 2006 10:31:11 +0200 Source: bidiui Binary: icedove-bidiui Architecture: source all Version: 0.7.3-2 Distribution: unstable Urgency: low Maintainer: Debian Hebrew Packaging Team [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: icedove-bidiui - BiDirectional support for Icedove Changes: bidiui (0.7.3-2) unstable; urgency=low . * Change dependencies to reflect thunderbird's rename to icedove Files: 52a02720c724946f00dfb5119428dbea 735 mail optional bidiui_0.7.3-2.dsc 6f66dfbe7db2f7509b7862cd679f018f 9415 mail optional bidiui_0.7.3-2.diff.gz 34837585d78dd464057abbff6b811e05 62900 mail optional icedove-bidiui_0.7.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFXKDAg8ByFc29vOIRAoqSAKCjCTw3d/YQj+fumYurLThVJuKPbACff3Gg N55KB63Pqosvk0oM5Qajfaw= =jNtx -END PGP SIGNATURE- Accepted: bidiui_0.7.3-2.diff.gz to pool/main/b/bidiui/bidiui_0.7.3-2.diff.gz bidiui_0.7.3-2.dsc to pool/main/b/bidiui/bidiui_0.7.3-2.dsc icedove-bidiui_0.7.3-2_all.deb to pool/main/b/bidiui/icedove-bidiui_0.7.3-2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted rsyncrypto 0.18-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 16 Nov 2006 13:32:54 +0200 Source: rsyncrypto Binary: rsyncrypto Architecture: source i386 Version: 0.18-1 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: rsyncrypto - rsync friendly encryption Changes: rsyncrypto (0.18-1) unstable; urgency=low . * New upstream release * Update maintainer's address (now a Debian Developer) * Update policy version to 3.7.2 (no changes required) * Make sure that the build rules run the regression tests * Reintroduce the regression testing files under examples * Introduce a lintian override file to stop it complaining about en empty file (rot files under tests). Files: a193c6cba01999dbb56d3ec4940a809f 617 utils optional rsyncrypto_0.18-1.dsc ceb7a1ef921939fee31f2cd42486cc70 396063 utils optional rsyncrypto_0.18.orig.tar.gz f94b967fe73c3b084b817cfdfdd5cf5b 16935 utils optional rsyncrypto_0.18-1.diff.gz 53f264b5c23c599fa9b5db4fce3f5326 292036 utils optional rsyncrypto_0.18-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFXE1yg8ByFc29vOIRAg37AKClSQ14JZi7m+/dwUqGrKk3/0In4gCghDUG to0UDqbVDFvXSneu4NTFgXA= =xogE -END PGP SIGNATURE- Accepted: rsyncrypto_0.18-1.diff.gz to pool/main/r/rsyncrypto/rsyncrypto_0.18-1.diff.gz rsyncrypto_0.18-1.dsc to pool/main/r/rsyncrypto/rsyncrypto_0.18-1.dsc rsyncrypto_0.18-1_i386.deb to pool/main/r/rsyncrypto/rsyncrypto_0.18-1_i386.deb rsyncrypto_0.18.orig.tar.gz to pool/main/r/rsyncrypto/rsyncrypto_0.18.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted argtable2 6-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 14 Nov 2006 16:13:36 +0200 Source: argtable2 Binary: libargtable2-dev libargtable2-0 Architecture: source i386 Version: 6-3 Distribution: unstable Urgency: low Maintainer: Shachar Shemesh [EMAIL PROTECTED] Changed-By: Shachar Shemesh [EMAIL PROTECTED] Description: libargtable2-0 - A library for parsing GNU style command line arguments libargtable2-dev - A library for parsing GNU style command line arguments Changes: argtable2 (6-3) unstable; urgency=low . * Update maintainer's email address (now a Debian Developer) * Update the policy version to 3.7.2 (no changes required) Files: 4036e47cdc6ca20b34e444792111b7a3 601 libs optional argtable2_6-3.dsc e58cc983db7368887ac0d883fbcdae19 137487 libs optional argtable2_6-3.diff.gz b8fcfb65581cb4f79564eabc1172e16e 3001964 libdevel optional libargtable2-dev_6-3_i386.deb 77b677d0e221183c1aee5180e6fb8d14 13054 libs optional libargtable2-0_6-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFWdABg8ByFc29vOIRAnZsAJ4ymTOaH0keBVp7Wt+ah+wSrt5OIQCfWVYH dISw6ZBeff1+stUDFX1+l4Y= =OBBm -END PGP SIGNATURE- Accepted: argtable2_6-3.diff.gz to pool/main/a/argtable2/argtable2_6-3.diff.gz argtable2_6-3.dsc to pool/main/a/argtable2/argtable2_6-3.dsc libargtable2-0_6-3_i386.deb to pool/main/a/argtable2/libargtable2-0_6-3_i386.deb libargtable2-dev_6-3_i386.deb to pool/main/a/argtable2/libargtable2-dev_6-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397295: ITP: bitefusion -- Simple 15 level snake game
Package: wnpp Severity: wishlist Owner: Shachar Shemesh [EMAIL PROTECTED] * Package name: bitefusion Version : 1.0.1 Upstream Author : JC3¸rgen Jacobsen [EMAIL PROTECTED] and Morten Hustveit [EMAIL PROTECTED] * URL : http://www.junoplay.com/ * License : GPL Programming Lang: C Description : Simple 15 level snake game A snake game with 15 levels. Great if you need to shut off your brain for a few minutes and occupy your hands in the meantime. Guaranteed no adrenaline rush! -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
