From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-August/017841.html | 89 + zarb-ml/mageia-dev/2012-August/017842.html | 80 + zarb-ml/mageia-dev/2012-August/017843.html | 94 + zarb-ml/mageia-dev/2012-August/017844.html | 104 + zarb-ml/mageia-dev/2012-August/017845.html | 122 + zarb-ml/mageia-dev/2012-August/017846.html | 94 + zarb-ml/mageia-dev/2012-August/017847.html | 92 + zarb-ml/mageia-dev/2012-August/017848.html | 103 + zarb-ml/mageia-dev/2012-August/017849.html | 132 + zarb-ml/mageia-dev/2012-August/017850.html | 78 + zarb-ml/mageia-dev/2012-August/017851.html | 133 + zarb-ml/mageia-dev/2012-August/017852.html | 73 + zarb-ml/mageia-dev/2012-August/017853.html | 72 + zarb-ml/mageia-dev/2012-August/017854.html | 69 + zarb-ml/mageia-dev/2012-August/017855.html | 110 + zarb-ml/mageia-dev/2012-August/017856.html | 84 + zarb-ml/mageia-dev/2012-August/017857.html | 106 + zarb-ml/mageia-dev/2012-August/017858.html | 119 + zarb-ml/mageia-dev/2012-August/017859.html | 87 + zarb-ml/mageia-dev/2012-August/017860.html | 98 + zarb-ml/mageia-dev/2012-August/017861.html | 88 + zarb-ml/mageia-dev/2012-August/017862.html | 91 + zarb-ml/mageia-dev/2012-August/017863.html | 88 + zarb-ml/mageia-dev/2012-August/017864.html | 110 + zarb-ml/mageia-dev/2012-August/017865.html | 98 + zarb-ml/mageia-dev/2012-August/017866.html | 94 + zarb-ml/mageia-dev/2012-August/017867.html | 101 + zarb-ml/mageia-dev/2012-August/017868.html | 80 + zarb-ml/mageia-dev/2012-August/017869.html | 108 + zarb-ml/mageia-dev/2012-August/017870.html | 81 + zarb-ml/mageia-dev/2012-August/017871.html | 89 + zarb-ml/mageia-dev/2012-August/017872.html | 92 + zarb-ml/mageia-dev/2012-August/017873.html | 87 + zarb-ml/mageia-dev/2012-August/017874.html | 91 + zarb-ml/mageia-dev/2012-August/017875.html | 83 + zarb-ml/mageia-dev/2012-August/017876.html | 85 + zarb-ml/mageia-dev/2012-August/017877.html | 261 ++ zarb-ml/mageia-dev/2012-August/017878.html | 98 + zarb-ml/mageia-dev/2012-August/017879.html | 96 + zarb-ml/mageia-dev/2012-August/017880.html | 117 + zarb-ml/mageia-dev/2012-August/017881.html | 104 + zarb-ml/mageia-dev/2012-August/017882.html | 98 + zarb-ml/mageia-dev/2012-August/017883.html | 63 + zarb-ml/mageia-dev/2012-August/017884.html | 96 + zarb-ml/mageia-dev/2012-August/017885.html | 89 + zarb-ml/mageia-dev/2012-August/017886.html | 77 + zarb-ml/mageia-dev/2012-August/017887.html | 105 + zarb-ml/mageia-dev/2012-August/017888.html | 81 + zarb-ml/mageia-dev/2012-August/017889.html | 338 +++ zarb-ml/mageia-dev/2012-August/017890.html | 96 + zarb-ml/mageia-dev/2012-August/017891.html | 134 + zarb-ml/mageia-dev/2012-August/017892.html | 76 + zarb-ml/mageia-dev/2012-August/017893.html | 78 + zarb-ml/mageia-dev/2012-August/017894.html | 122 + zarb-ml/mageia-dev/2012-August/017895.html | 112 + zarb-ml/mageia-dev/2012-August/017896.html | 117 + zarb-ml/mageia-dev/2012-August/017897.html | 121 + zarb-ml/mageia-dev/2012-August/017898.html | 140 + zarb-ml/mageia-dev/2012-August/017899.html | 130 + zarb-ml/mageia-dev/2012-August/017900.html | 140 + zarb-ml/mageia-dev/2012-August/017901.html | 80 + zarb-ml/mageia-dev/2012-August/017902.html | 78 + zarb-ml/mageia-dev/2012-August/017903.html | 64 + zarb-ml/mageia-dev/2012-August/017904.html | 70 + zarb-ml/mageia-dev/2012-August/017905.html | 69 + zarb-ml/mageia-dev/2012-August/017906.html | 71 + zarb-ml/mageia-dev/2012-August/017907.html | 67 + zarb-ml/mageia-dev/2012-August/017908.html | 89 + zarb-ml/mageia-dev/2012-August/017909.html | 99 + zarb-ml/mageia-dev/2012-August/017910.html | 97 + zarb-ml/mageia-dev/2012-August/017911.html | 69 + zarb-ml/mageia-dev/2012-August/017912.html | 89 + zarb-ml/mageia-dev/2012-August/017913.html | 114 + zarb-ml/mageia-dev/2012-August/017914.html | 113 + zarb-ml/mageia-dev/2012-August/017915.html | 79 + zarb-ml/mageia-dev/2012-August/017916.html | 76 + zarb-ml/mageia-dev/2012-August/017917.html | 118 + zarb-ml/mageia-dev/2012-August/017918.html | 123 + zarb-ml/mageia-dev/2012-August/017919.html | 139 + zarb-ml/mageia-dev/2012-August/017920.html | 67 + zarb-ml/mageia-dev/2012-August/017921.html | 68 + zarb-ml/mageia-dev/2012-August/017922.html | 65 + zarb-ml/mageia-dev/2012-August/017923.html | 65 + zarb-ml/mageia-dev/2012-August/017924.html | 74 + zarb-ml/mageia-dev/2012-August/017925.html | 90 + zarb-ml/mageia-dev/2012-August/017926.html | 165 ++ zarb-ml/mageia-dev/2012-August/017927.html | 68 + zarb-ml/mageia-dev/2012-August/017928.html | 71 + zarb-ml/mageia-dev/2012-August/017929.html | 67 + zarb-ml/mageia-dev/2012-August/017930.html | 84 + zarb-ml/mageia-dev/2012-August/017931.html | 91 + zarb-ml/mageia-dev/2012-August/017932.html | 74 + zarb-ml/mageia-dev/2012-August/017933.html | 90 + zarb-ml/mageia-dev/2012-August/017934.html | 87 + zarb-ml/mageia-dev/2012-August/017935.html | 84 + zarb-ml/mageia-dev/2012-August/017936.html | 90 + zarb-ml/mageia-dev/2012-August/017937.html | 98 + zarb-ml/mageia-dev/2012-August/017938.html | 80 + zarb-ml/mageia-dev/2012-August/017939.html | 67 + zarb-ml/mageia-dev/2012-August/017940.html | 123 + zarb-ml/mageia-dev/2012-August/017941.html | 128 + zarb-ml/mageia-dev/2012-August/017942.html | 91 + zarb-ml/mageia-dev/2012-August/017943.html | 78 + zarb-ml/mageia-dev/2012-August/017944.html | 63 + zarb-ml/mageia-dev/2012-August/017945.html | 70 + zarb-ml/mageia-dev/2012-August/017946.html | 77 + zarb-ml/mageia-dev/2012-August/017947.html | 79 + zarb-ml/mageia-dev/2012-August/017948.html | 96 + zarb-ml/mageia-dev/2012-August/017949.html | 89 + zarb-ml/mageia-dev/2012-August/017950.html | 87 + zarb-ml/mageia-dev/2012-August/017951.html | 87 + zarb-ml/mageia-dev/2012-August/017952.html | 102 + zarb-ml/mageia-dev/2012-August/017953.html | 69 + zarb-ml/mageia-dev/2012-August/017954.html | 91 + zarb-ml/mageia-dev/2012-August/017955.html | 75 + zarb-ml/mageia-dev/2012-August/017956.html | 80 + zarb-ml/mageia-dev/2012-August/017957.html | 81 + zarb-ml/mageia-dev/2012-August/017958.html | 79 + zarb-ml/mageia-dev/2012-August/017959.html | 75 + zarb-ml/mageia-dev/2012-August/017960.html | 81 + zarb-ml/mageia-dev/2012-August/017961.html | 93 + zarb-ml/mageia-dev/2012-August/017962.html | 62 + zarb-ml/mageia-dev/2012-August/017963.html | 94 + zarb-ml/mageia-dev/2012-August/017964.html | 80 + zarb-ml/mageia-dev/2012-August/017965.html | 91 + zarb-ml/mageia-dev/2012-August/017966.html | 106 + zarb-ml/mageia-dev/2012-August/017967.html | 72 + zarb-ml/mageia-dev/2012-August/017968.html | 66 + zarb-ml/mageia-dev/2012-August/017969.html | 117 + zarb-ml/mageia-dev/2012-August/017970.html | 99 + zarb-ml/mageia-dev/2012-August/017971.html | 95 + zarb-ml/mageia-dev/2012-August/017972.html | 82 + zarb-ml/mageia-dev/2012-August/017973.html | 76 + zarb-ml/mageia-dev/2012-August/017974.html | 90 + zarb-ml/mageia-dev/2012-August/017975.html | 82 + zarb-ml/mageia-dev/2012-August/017976.html | 101 + zarb-ml/mageia-dev/2012-August/017977.html | 116 + zarb-ml/mageia-dev/2012-August/017978.html | 105 + zarb-ml/mageia-dev/2012-August/017979.html | 84 + zarb-ml/mageia-dev/2012-August/017980.html | 97 + zarb-ml/mageia-dev/2012-August/017981.html | 79 + zarb-ml/mageia-dev/2012-August/017982.html | 82 + zarb-ml/mageia-dev/2012-August/017983.html | 86 + zarb-ml/mageia-dev/2012-August/017984.html | 90 + zarb-ml/mageia-dev/2012-August/017985.html | 100 + zarb-ml/mageia-dev/2012-August/017986.html | 110 + zarb-ml/mageia-dev/2012-August/017987.html | 89 + zarb-ml/mageia-dev/2012-August/017988.html | 90 + zarb-ml/mageia-dev/2012-August/017989.html | 81 + zarb-ml/mageia-dev/2012-August/017990.html | 107 + zarb-ml/mageia-dev/2012-August/017991.html | 65 + zarb-ml/mageia-dev/2012-August/017992.html | 103 + zarb-ml/mageia-dev/2012-August/017993.html | 99 + zarb-ml/mageia-dev/2012-August/017994.html | 84 + zarb-ml/mageia-dev/2012-August/017995.html | 104 + zarb-ml/mageia-dev/2012-August/017996.html | 95 + zarb-ml/mageia-dev/2012-August/017997.html | 87 + zarb-ml/mageia-dev/2012-August/017998.html | 128 + zarb-ml/mageia-dev/2012-August/017999.html | 157 ++ zarb-ml/mageia-dev/2012-August/018000.html | 109 + zarb-ml/mageia-dev/2012-August/018001.html | 96 + zarb-ml/mageia-dev/2012-August/018002.html | 101 + zarb-ml/mageia-dev/2012-August/018003.html | 90 + zarb-ml/mageia-dev/2012-August/018004.html | 86 + zarb-ml/mageia-dev/2012-August/018005.html | 84 + zarb-ml/mageia-dev/2012-August/018006.html | 111 + zarb-ml/mageia-dev/2012-August/018007.html | 83 + zarb-ml/mageia-dev/2012-August/018008.html | 84 + zarb-ml/mageia-dev/2012-August/018009.html | 92 + zarb-ml/mageia-dev/2012-August/018010.html | 98 + zarb-ml/mageia-dev/2012-August/018011.html | 76 + zarb-ml/mageia-dev/2012-August/018012.html | 81 + zarb-ml/mageia-dev/2012-August/018013.html | 85 + zarb-ml/mageia-dev/2012-August/018014.html | 82 + zarb-ml/mageia-dev/2012-August/018015.html | 87 + zarb-ml/mageia-dev/2012-August/018016.html | 97 + zarb-ml/mageia-dev/2012-August/018017.html | 93 + zarb-ml/mageia-dev/2012-August/018018.html | 93 + zarb-ml/mageia-dev/2012-August/018019.html | 99 + zarb-ml/mageia-dev/2012-August/018020.html | 124 + zarb-ml/mageia-dev/2012-August/018021.html | 107 + zarb-ml/mageia-dev/2012-August/018022.html | 113 + zarb-ml/mageia-dev/2012-August/018023.html | 100 + zarb-ml/mageia-dev/2012-August/018024.html | 101 + zarb-ml/mageia-dev/2012-August/018025.html | 117 + zarb-ml/mageia-dev/2012-August/018026.html | 93 + zarb-ml/mageia-dev/2012-August/018027.html | 121 + zarb-ml/mageia-dev/2012-August/018028.html | 104 + zarb-ml/mageia-dev/2012-August/018029.html | 126 + zarb-ml/mageia-dev/2012-August/018030.html | 114 + zarb-ml/mageia-dev/2012-August/018031.html | 115 + zarb-ml/mageia-dev/2012-August/018032.html | 132 + zarb-ml/mageia-dev/2012-August/018033.html | 102 + zarb-ml/mageia-dev/2012-August/018034.html | 96 + zarb-ml/mageia-dev/2012-August/018035.html | 126 + zarb-ml/mageia-dev/2012-August/018036.html | 116 + zarb-ml/mageia-dev/2012-August/018037.html | 143 + zarb-ml/mageia-dev/2012-August/018038.html | 119 + zarb-ml/mageia-dev/2012-August/018039.html | 104 + zarb-ml/mageia-dev/2012-August/018040.html | 95 + zarb-ml/mageia-dev/2012-August/018041.html | 142 + zarb-ml/mageia-dev/2012-August/018042.html | 99 + zarb-ml/mageia-dev/2012-August/018043.html | 95 + zarb-ml/mageia-dev/2012-August/018044.html | 88 + zarb-ml/mageia-dev/2012-August/018045.html | 102 + zarb-ml/mageia-dev/2012-August/018046.html | 118 + zarb-ml/mageia-dev/2012-August/018047.html | 186 ++ zarb-ml/mageia-dev/2012-August/018048.html | 110 + zarb-ml/mageia-dev/2012-August/018049.html | 82 + zarb-ml/mageia-dev/2012-August/018050.html | 136 + zarb-ml/mageia-dev/2012-August/018051.html | 153 ++ zarb-ml/mageia-dev/2012-August/018052.html | 154 ++ zarb-ml/mageia-dev/2012-August/018053.html | 89 + zarb-ml/mageia-dev/2012-August/018054.html | 100 + zarb-ml/mageia-dev/2012-August/018055.html | 107 + zarb-ml/mageia-dev/2012-August/018056.html | 127 + zarb-ml/mageia-dev/2012-August/018057.html | 137 + zarb-ml/mageia-dev/2012-August/018058.html | 125 + zarb-ml/mageia-dev/2012-August/018059.html | 127 + zarb-ml/mageia-dev/2012-August/018060.html | 116 + zarb-ml/mageia-dev/2012-August/018061.html | 130 + zarb-ml/mageia-dev/2012-August/018062.html | 122 + zarb-ml/mageia-dev/2012-August/018063.html | 121 + zarb-ml/mageia-dev/2012-August/018064.html | 124 + zarb-ml/mageia-dev/2012-August/018065.html | 157 ++ zarb-ml/mageia-dev/2012-August/018066.html | 112 + zarb-ml/mageia-dev/2012-August/018067.html | 120 + zarb-ml/mageia-dev/2012-August/018068.html | 119 + zarb-ml/mageia-dev/2012-August/018069.html | 128 + zarb-ml/mageia-dev/2012-August/018070.html | 130 + zarb-ml/mageia-dev/2012-August/018071.html | 115 + zarb-ml/mageia-dev/2012-August/018072.html | 121 + zarb-ml/mageia-dev/2012-August/018073.html | 122 + zarb-ml/mageia-dev/2012-August/018074.html | 115 + zarb-ml/mageia-dev/2012-August/018075.html | 114 + zarb-ml/mageia-dev/2012-August/018076.html | 128 + zarb-ml/mageia-dev/2012-August/018077.html | 115 + zarb-ml/mageia-dev/2012-August/018078.html | 86 + zarb-ml/mageia-dev/2012-August/018079.html | 125 + zarb-ml/mageia-dev/2012-August/018080.html | 100 + zarb-ml/mageia-dev/2012-August/018081.html | 105 + zarb-ml/mageia-dev/2012-August/018082.html | 112 + zarb-ml/mageia-dev/2012-August/018083.html | 84 + zarb-ml/mageia-dev/2012-August/018084.html | 84 + zarb-ml/mageia-dev/2012-August/018085.html | 104 + zarb-ml/mageia-dev/2012-August/018086.html | 102 + zarb-ml/mageia-dev/2012-August/018087.html | 101 + zarb-ml/mageia-dev/2012-August/018088.html | 109 + zarb-ml/mageia-dev/2012-August/018089.html | 88 + zarb-ml/mageia-dev/2012-August/018090.html | 116 + zarb-ml/mageia-dev/2012-August/018091.html | 124 + zarb-ml/mageia-dev/2012-August/018092.html | 106 + zarb-ml/mageia-dev/2012-August/018093.html | 84 + zarb-ml/mageia-dev/2012-August/018094.html | 78 + zarb-ml/mageia-dev/2012-August/018095.html | 114 + zarb-ml/mageia-dev/2012-August/018096.html | 135 + zarb-ml/mageia-dev/2012-August/018097.html | 127 + zarb-ml/mageia-dev/2012-August/018098.html | 96 + zarb-ml/mageia-dev/2012-August/018099.html | 102 + zarb-ml/mageia-dev/2012-August/018100.html | 98 + zarb-ml/mageia-dev/2012-August/018101.html | 149 ++ zarb-ml/mageia-dev/2012-August/018102.html | 96 + zarb-ml/mageia-dev/2012-August/018103.html | 129 + zarb-ml/mageia-dev/2012-August/018104.html | 111 + zarb-ml/mageia-dev/2012-August/018105.html | 150 ++ zarb-ml/mageia-dev/2012-August/018106.html | 150 ++ zarb-ml/mageia-dev/2012-August/018107.html | 107 + zarb-ml/mageia-dev/2012-August/018108.html | 160 ++ zarb-ml/mageia-dev/2012-August/018109.html | 160 ++ zarb-ml/mageia-dev/2012-August/018110.html | 90 + zarb-ml/mageia-dev/2012-August/018111.html | 94 + zarb-ml/mageia-dev/2012-August/018112.html | 98 + zarb-ml/mageia-dev/2012-August/018113.html | 107 + zarb-ml/mageia-dev/2012-August/018114.html | 117 + zarb-ml/mageia-dev/2012-August/018115.html | 100 + zarb-ml/mageia-dev/2012-August/018116.html | 118 + zarb-ml/mageia-dev/2012-August/018117.html | 107 + zarb-ml/mageia-dev/2012-August/018118.html | 107 + zarb-ml/mageia-dev/2012-August/018119.html | 92 + zarb-ml/mageia-dev/2012-August/018120.html | 104 + zarb-ml/mageia-dev/2012-August/018121.html | 91 + zarb-ml/mageia-dev/2012-August/018122.html | 107 + zarb-ml/mageia-dev/2012-August/018123.html | 114 + zarb-ml/mageia-dev/2012-August/018124.html | 118 + zarb-ml/mageia-dev/2012-August/018125.html | 93 + zarb-ml/mageia-dev/2012-August/018126.html | 89 + zarb-ml/mageia-dev/2012-August/018127.html | 91 + zarb-ml/mageia-dev/2012-August/018128.html | 99 + zarb-ml/mageia-dev/2012-August/018129.html | 83 + zarb-ml/mageia-dev/2012-August/018130.html | 119 + zarb-ml/mageia-dev/2012-August/018131.html | 98 + zarb-ml/mageia-dev/2012-August/018132.html | 105 + zarb-ml/mageia-dev/2012-August/018133.html | 94 + zarb-ml/mageia-dev/2012-August/018134.html | 125 + zarb-ml/mageia-dev/2012-August/018135.html | 98 + zarb-ml/mageia-dev/2012-August/018136.html | 89 + zarb-ml/mageia-dev/2012-August/018137.html | 76 + zarb-ml/mageia-dev/2012-August/018138.html | 92 + zarb-ml/mageia-dev/2012-August/018139.html | 118 + zarb-ml/mageia-dev/2012-August/018140.html | 114 + zarb-ml/mageia-dev/2012-August/018141.html | 74 + zarb-ml/mageia-dev/2012-August/018142.html | 98 + zarb-ml/mageia-dev/2012-August/018143.html | 89 + zarb-ml/mageia-dev/2012-August/018144.html | 113 + zarb-ml/mageia-dev/2012-August/018145.html | 78 + zarb-ml/mageia-dev/2012-August/018146.html | 108 + zarb-ml/mageia-dev/2012-August/018147.html | 86 + zarb-ml/mageia-dev/2012-August/018148.html | 75 + zarb-ml/mageia-dev/2012-August/018149.html | 98 + zarb-ml/mageia-dev/2012-August/018150.html | 99 + zarb-ml/mageia-dev/2012-August/018151.html | 70 + zarb-ml/mageia-dev/2012-August/018152.html | 86 + zarb-ml/mageia-dev/2012-August/018153.html | 110 + zarb-ml/mageia-dev/2012-August/018154.html | 80 + zarb-ml/mageia-dev/2012-August/018155.html | 86 + zarb-ml/mageia-dev/2012-August/018156.html | 88 + zarb-ml/mageia-dev/2012-August/018157.html | 101 + zarb-ml/mageia-dev/2012-August/018158.html | 86 + zarb-ml/mageia-dev/2012-August/018159.html | 109 + zarb-ml/mageia-dev/2012-August/018160.html | 137 + zarb-ml/mageia-dev/2012-August/018161.html | 101 + zarb-ml/mageia-dev/2012-August/018162.html | 88 + zarb-ml/mageia-dev/2012-August/018163.html | 103 + zarb-ml/mageia-dev/2012-August/018164.html | 81 + zarb-ml/mageia-dev/2012-August/018165.html | 104 + zarb-ml/mageia-dev/2012-August/018166.html | 99 + zarb-ml/mageia-dev/2012-August/018167.html | 123 + zarb-ml/mageia-dev/2012-August/018168.html | 123 + zarb-ml/mageia-dev/2012-August/018169.html | 108 + zarb-ml/mageia-dev/2012-August/018170.html | 114 + zarb-ml/mageia-dev/2012-August/018171.html | 84 + zarb-ml/mageia-dev/2012-August/018172.html | 109 + zarb-ml/mageia-dev/2012-August/018173.html | 81 + zarb-ml/mageia-dev/2012-August/018174.html | 106 + zarb-ml/mageia-dev/2012-August/018175.html | 113 + zarb-ml/mageia-dev/2012-August/018176.html | 92 + zarb-ml/mageia-dev/2012-August/018177.html | 121 + zarb-ml/mageia-dev/2012-August/018178.html | 82 + zarb-ml/mageia-dev/2012-August/018179.html | 96 + zarb-ml/mageia-dev/2012-August/018180.html | 82 + zarb-ml/mageia-dev/2012-August/018181.html | 92 + zarb-ml/mageia-dev/2012-August/018182.html | 85 + zarb-ml/mageia-dev/2012-August/018183.html | 87 + zarb-ml/mageia-dev/2012-August/018184.html | 90 + zarb-ml/mageia-dev/2012-August/018185.html | 91 + zarb-ml/mageia-dev/2012-August/018186.html | 91 + zarb-ml/mageia-dev/2012-August/018187.html | 118 + zarb-ml/mageia-dev/2012-August/018188.html | 76 + zarb-ml/mageia-dev/2012-August/018189.html | 112 + zarb-ml/mageia-dev/2012-August/018190.html | 102 + zarb-ml/mageia-dev/2012-August/018191.html | 109 + zarb-ml/mageia-dev/2012-August/018192.html | 81 + zarb-ml/mageia-dev/2012-August/018193.html | 140 + zarb-ml/mageia-dev/2012-August/018194.html | 139 + zarb-ml/mageia-dev/2012-August/018195.html | 136 + zarb-ml/mageia-dev/2012-August/018196.html | 124 + zarb-ml/mageia-dev/2012-August/018197.html | 113 + zarb-ml/mageia-dev/2012-August/018198.html | 72 + zarb-ml/mageia-dev/2012-August/018199.html | 87 + zarb-ml/mageia-dev/2012-August/018200.html | 79 + zarb-ml/mageia-dev/2012-August/018201.html | 87 + zarb-ml/mageia-dev/2012-August/018202.html | 82 + zarb-ml/mageia-dev/2012-August/018203.html | 84 + zarb-ml/mageia-dev/2012-August/018204.html | 99 + zarb-ml/mageia-dev/2012-August/018205.html | 123 + zarb-ml/mageia-dev/2012-August/018206.html | 120 + zarb-ml/mageia-dev/2012-August/018207.html | 109 + zarb-ml/mageia-dev/2012-August/018208.html | 99 + zarb-ml/mageia-dev/2012-August/018209.html | 86 + zarb-ml/mageia-dev/2012-August/018210.html | 88 + zarb-ml/mageia-dev/2012-August/018211.html | 110 + zarb-ml/mageia-dev/2012-August/018212.html | 83 + zarb-ml/mageia-dev/2012-August/018213.html | 205 ++ zarb-ml/mageia-dev/2012-August/018214.html | 84 + zarb-ml/mageia-dev/2012-August/018215.html | 101 + zarb-ml/mageia-dev/2012-August/018216.html | 90 + zarb-ml/mageia-dev/2012-August/018217.html | 90 + zarb-ml/mageia-dev/2012-August/018218.html | 98 + zarb-ml/mageia-dev/2012-August/018219.html | 103 + zarb-ml/mageia-dev/2012-August/018220.html | 99 + zarb-ml/mageia-dev/2012-August/018221.html | 126 + zarb-ml/mageia-dev/2012-August/018222.html | 126 + zarb-ml/mageia-dev/2012-August/018223.html | 129 + zarb-ml/mageia-dev/2012-August/018224.html | 132 + zarb-ml/mageia-dev/2012-August/018225.html | 136 + zarb-ml/mageia-dev/2012-August/018226.html | 139 + zarb-ml/mageia-dev/2012-August/018227.html | 107 + zarb-ml/mageia-dev/2012-August/018228.html | 93 + zarb-ml/mageia-dev/2012-August/018229.html | 79 + zarb-ml/mageia-dev/2012-August/018230.html | 83 + zarb-ml/mageia-dev/2012-August/018231.html | 86 + zarb-ml/mageia-dev/2012-August/018232.html | 95 + zarb-ml/mageia-dev/2012-August/018233.html | 110 + zarb-ml/mageia-dev/2012-August/018234.html | 93 + zarb-ml/mageia-dev/2012-August/018235.html | 96 + zarb-ml/mageia-dev/2012-August/018236.html | 95 + zarb-ml/mageia-dev/2012-August/018237.html | 98 + zarb-ml/mageia-dev/2012-August/018238.html | 87 + zarb-ml/mageia-dev/2012-August/018239.html | 120 + zarb-ml/mageia-dev/2012-August/018240.html | 93 + zarb-ml/mageia-dev/2012-August/018241.html | 79 + zarb-ml/mageia-dev/2012-August/018242.html | 96 + zarb-ml/mageia-dev/2012-August/018243.html | 90 + zarb-ml/mageia-dev/2012-August/018244.html | 99 + zarb-ml/mageia-dev/2012-August/018245.html | 99 + zarb-ml/mageia-dev/2012-August/018246.html | 118 + zarb-ml/mageia-dev/2012-August/018247.html | 98 + zarb-ml/mageia-dev/2012-August/018248.html | 95 + zarb-ml/mageia-dev/2012-August/018249.html | 86 + zarb-ml/mageia-dev/2012-August/018250.html | 78 + zarb-ml/mageia-dev/2012-August/018251.html | 86 + zarb-ml/mageia-dev/2012-August/018252.html | 85 + zarb-ml/mageia-dev/2012-August/018253.html | 84 + zarb-ml/mageia-dev/2012-August/018254.html | 83 + zarb-ml/mageia-dev/2012-August/018255.html | 109 + zarb-ml/mageia-dev/2012-August/018256.html | 76 + zarb-ml/mageia-dev/2012-August/018257.html | 92 + zarb-ml/mageia-dev/2012-August/018258.html | 98 + zarb-ml/mageia-dev/2012-August/018259.html | 102 + zarb-ml/mageia-dev/2012-August/018260.html | 103 + zarb-ml/mageia-dev/2012-August/018261.html | 101 + zarb-ml/mageia-dev/2012-August/018262.html | 103 + zarb-ml/mageia-dev/2012-August/018263.html | 154 ++ zarb-ml/mageia-dev/2012-August/018264.html | 94 + zarb-ml/mageia-dev/2012-August/018265.html | 96 + zarb-ml/mageia-dev/2012-August/018266.html | 86 + zarb-ml/mageia-dev/2012-August/018267.html | 85 + zarb-ml/mageia-dev/2012-August/018268.html | 112 + zarb-ml/mageia-dev/2012-August/018269.html | 123 + zarb-ml/mageia-dev/2012-August/018270.html | 98 + zarb-ml/mageia-dev/2012-August/018271.html | 92 + zarb-ml/mageia-dev/2012-August/018272.html | 78 + zarb-ml/mageia-dev/2012-August/018273.html | 125 + zarb-ml/mageia-dev/2012-August/018274.html | 135 + zarb-ml/mageia-dev/2012-August/018275.html | 139 + zarb-ml/mageia-dev/2012-August/018276.html | 106 + zarb-ml/mageia-dev/2012-August/018277.html | 130 + zarb-ml/mageia-dev/2012-August/018278.html | 84 + zarb-ml/mageia-dev/2012-August/018279.html | 87 + zarb-ml/mageia-dev/2012-August/018280.html | 129 + zarb-ml/mageia-dev/2012-August/018281.html | 95 + zarb-ml/mageia-dev/2012-August/018282.html | 78 + zarb-ml/mageia-dev/2012-August/018283.html | 96 + zarb-ml/mageia-dev/2012-August/018284.html | 110 + zarb-ml/mageia-dev/2012-August/018285.html | 102 + zarb-ml/mageia-dev/2012-August/018286.html | 111 + zarb-ml/mageia-dev/2012-August/018287.html | 122 + zarb-ml/mageia-dev/2012-August/018288.html | 117 + zarb-ml/mageia-dev/2012-August/018289.html | 81 + zarb-ml/mageia-dev/2012-August/018290.html | 82 + zarb-ml/mageia-dev/2012-August/018291.html | 75 + zarb-ml/mageia-dev/2012-August/018292.html | 89 + zarb-ml/mageia-dev/2012-August/018293.html | 82 + zarb-ml/mageia-dev/2012-August/018294.html | 115 + zarb-ml/mageia-dev/2012-August/018295.html | 84 + zarb-ml/mageia-dev/2012-August/018296.html | 78 + zarb-ml/mageia-dev/2012-August/018297.html | 82 + zarb-ml/mageia-dev/2012-August/018298.html | 71 + zarb-ml/mageia-dev/2012-August/018299.html | 75 + zarb-ml/mageia-dev/2012-August/018300.html | 108 + zarb-ml/mageia-dev/2012-August/018301.html | 101 + zarb-ml/mageia-dev/2012-August/018302.html | 125 + zarb-ml/mageia-dev/2012-August/018303.html | 95 + zarb-ml/mageia-dev/2012-August/018304.html | 75 + zarb-ml/mageia-dev/2012-August/018305.html | 92 + zarb-ml/mageia-dev/2012-August/018306.html | 87 + zarb-ml/mageia-dev/2012-August/018307.html | 94 + zarb-ml/mageia-dev/2012-August/018308.html | 107 + zarb-ml/mageia-dev/2012-August/018309.html | 103 + zarb-ml/mageia-dev/2012-August/018310.html | 100 + zarb-ml/mageia-dev/2012-August/018311.html | 79 + zarb-ml/mageia-dev/2012-August/018312.html | 94 + zarb-ml/mageia-dev/2012-August/018313.html | 78 + zarb-ml/mageia-dev/2012-August/018314.html | 99 + zarb-ml/mageia-dev/2012-August/018315.html | 108 + zarb-ml/mageia-dev/2012-August/018316.html | 73 + zarb-ml/mageia-dev/2012-August/018317.html | 77 + zarb-ml/mageia-dev/2012-August/018318.html | 95 + zarb-ml/mageia-dev/2012-August/018319.html | 68 + zarb-ml/mageia-dev/2012-August/018320.html | 75 + zarb-ml/mageia-dev/2012-August/018321.html | 68 + zarb-ml/mageia-dev/2012-August/018322.html | 85 + zarb-ml/mageia-dev/2012-August/018323.html | 69 + zarb-ml/mageia-dev/2012-August/018324.html | 71 + zarb-ml/mageia-dev/2012-August/018325.html | 95 + zarb-ml/mageia-dev/2012-August/018326.html | 94 + zarb-ml/mageia-dev/2012-August/018327.html | 85 + zarb-ml/mageia-dev/2012-August/018328.html | 70 + zarb-ml/mageia-dev/2012-August/018329.html | 74 + zarb-ml/mageia-dev/2012-August/018330.html | 73 + zarb-ml/mageia-dev/2012-August/018331.html | 89 + zarb-ml/mageia-dev/2012-August/018332.html | 77 + zarb-ml/mageia-dev/2012-August/018333.html | 71 + zarb-ml/mageia-dev/2012-August/018334.html | 130 + zarb-ml/mageia-dev/2012-August/018335.html | 75 + zarb-ml/mageia-dev/2012-August/018336.html | 108 + zarb-ml/mageia-dev/2012-August/018337.html | 84 + zarb-ml/mageia-dev/2012-August/018338.html | 70 + zarb-ml/mageia-dev/2012-August/018339.html | 74 + zarb-ml/mageia-dev/2012-August/018340.html | 115 + zarb-ml/mageia-dev/2012-August/018341.html | 88 + zarb-ml/mageia-dev/2012-August/018342.html | 103 + zarb-ml/mageia-dev/2012-August/018343.html | 91 + zarb-ml/mageia-dev/2012-August/018344.html | 96 + zarb-ml/mageia-dev/2012-August/018345.html | 90 + zarb-ml/mageia-dev/2012-August/018346.html | 79 + zarb-ml/mageia-dev/2012-August/018347.html | 68 + zarb-ml/mageia-dev/2012-August/018348.html | 68 + zarb-ml/mageia-dev/2012-August/018349.html | 89 + zarb-ml/mageia-dev/2012-August/018350.html | 119 + zarb-ml/mageia-dev/2012-August/018351.html | 76 + zarb-ml/mageia-dev/2012-August/018352.html | 104 + zarb-ml/mageia-dev/2012-August/018353.html | 69 + zarb-ml/mageia-dev/2012-August/018354.html | 94 + zarb-ml/mageia-dev/2012-August/018355.html | 97 + zarb-ml/mageia-dev/2012-August/018356.html | 98 + zarb-ml/mageia-dev/2012-August/018357.html | 96 + zarb-ml/mageia-dev/2012-August/018358.html | 96 + zarb-ml/mageia-dev/2012-August/018359.html | 78 + zarb-ml/mageia-dev/2012-August/018360.html | 78 + zarb-ml/mageia-dev/2012-August/018361.html | 112 + zarb-ml/mageia-dev/2012-August/018362.html | 79 + zarb-ml/mageia-dev/2012-August/018363.html | 90 + zarb-ml/mageia-dev/2012-August/018364.html | 80 + zarb-ml/mageia-dev/2012-August/018365.html | 84 + zarb-ml/mageia-dev/2012-August/018366.html | 90 + zarb-ml/mageia-dev/2012-August/018367.html | 83 + zarb-ml/mageia-dev/2012-August/018368.html | 80 + zarb-ml/mageia-dev/2012-August/018369.html | 106 + zarb-ml/mageia-dev/2012-August/018370.html | 94 + zarb-ml/mageia-dev/2012-August/018371.html | 75 + zarb-ml/mageia-dev/2012-August/018372.html | 84 + zarb-ml/mageia-dev/2012-August/018373.html | 71 + zarb-ml/mageia-dev/2012-August/018374.html | 69 + zarb-ml/mageia-dev/2012-August/018375.html | 89 + zarb-ml/mageia-dev/2012-August/018376.html | 77 + zarb-ml/mageia-dev/2012-August/018377.html | 94 + zarb-ml/mageia-dev/2012-August/018378.html | 86 + zarb-ml/mageia-dev/2012-August/018379.html | 83 + zarb-ml/mageia-dev/2012-August/018380.html | 74 + zarb-ml/mageia-dev/2012-August/018381.html | 95 + zarb-ml/mageia-dev/2012-August/018382.html | 78 + zarb-ml/mageia-dev/2012-August/018383.html | 92 + zarb-ml/mageia-dev/2012-August/018384.html | 58 + zarb-ml/mageia-dev/2012-August/018385.html | 62 + zarb-ml/mageia-dev/2012-August/018386.html | 66 + zarb-ml/mageia-dev/2012-August/018387.html | 81 + zarb-ml/mageia-dev/2012-August/018388.html | 77 + zarb-ml/mageia-dev/2012-August/018389.html | 72 + zarb-ml/mageia-dev/2012-August/018390.html | 81 + zarb-ml/mageia-dev/2012-August/018391.html | 65 + zarb-ml/mageia-dev/2012-August/018392.html | 74 + zarb-ml/mageia-dev/2012-August/018393.html | 58 + zarb-ml/mageia-dev/2012-August/018394.html | 73 + zarb-ml/mageia-dev/2012-August/018395.html | 74 + zarb-ml/mageia-dev/2012-August/018396.html | 70 + zarb-ml/mageia-dev/2012-August/author.html | 2827 ++++++++++++++++++++ zarb-ml/mageia-dev/2012-August/date.html | 2827 ++++++++++++++++++++ zarb-ml/mageia-dev/2012-August/index.html | 1 + zarb-ml/mageia-dev/2012-August/subject.html | 2827 ++++++++++++++++++++ zarb-ml/mageia-dev/2012-August/thread.html | 3779 +++++++++++++++++++++++++++ 561 files changed, 66858 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-August/017841.html create mode 100644 zarb-ml/mageia-dev/2012-August/017842.html create mode 100644 zarb-ml/mageia-dev/2012-August/017843.html create mode 100644 zarb-ml/mageia-dev/2012-August/017844.html create mode 100644 zarb-ml/mageia-dev/2012-August/017845.html create mode 100644 zarb-ml/mageia-dev/2012-August/017846.html create mode 100644 zarb-ml/mageia-dev/2012-August/017847.html create mode 100644 zarb-ml/mageia-dev/2012-August/017848.html create mode 100644 zarb-ml/mageia-dev/2012-August/017849.html create mode 100644 zarb-ml/mageia-dev/2012-August/017850.html create mode 100644 zarb-ml/mageia-dev/2012-August/017851.html create mode 100644 zarb-ml/mageia-dev/2012-August/017852.html create mode 100644 zarb-ml/mageia-dev/2012-August/017853.html create mode 100644 zarb-ml/mageia-dev/2012-August/017854.html create mode 100644 zarb-ml/mageia-dev/2012-August/017855.html create mode 100644 zarb-ml/mageia-dev/2012-August/017856.html create mode 100644 zarb-ml/mageia-dev/2012-August/017857.html create mode 100644 zarb-ml/mageia-dev/2012-August/017858.html create mode 100644 zarb-ml/mageia-dev/2012-August/017859.html create mode 100644 zarb-ml/mageia-dev/2012-August/017860.html create mode 100644 zarb-ml/mageia-dev/2012-August/017861.html create mode 100644 zarb-ml/mageia-dev/2012-August/017862.html create mode 100644 zarb-ml/mageia-dev/2012-August/017863.html create mode 100644 zarb-ml/mageia-dev/2012-August/017864.html create mode 100644 zarb-ml/mageia-dev/2012-August/017865.html create mode 100644 zarb-ml/mageia-dev/2012-August/017866.html create mode 100644 zarb-ml/mageia-dev/2012-August/017867.html create mode 100644 zarb-ml/mageia-dev/2012-August/017868.html create mode 100644 zarb-ml/mageia-dev/2012-August/017869.html create mode 100644 zarb-ml/mageia-dev/2012-August/017870.html create mode 100644 zarb-ml/mageia-dev/2012-August/017871.html create mode 100644 zarb-ml/mageia-dev/2012-August/017872.html create mode 100644 zarb-ml/mageia-dev/2012-August/017873.html create mode 100644 zarb-ml/mageia-dev/2012-August/017874.html create mode 100644 zarb-ml/mageia-dev/2012-August/017875.html create mode 100644 zarb-ml/mageia-dev/2012-August/017876.html create mode 100644 zarb-ml/mageia-dev/2012-August/017877.html create mode 100644 zarb-ml/mageia-dev/2012-August/017878.html create mode 100644 zarb-ml/mageia-dev/2012-August/017879.html create mode 100644 zarb-ml/mageia-dev/2012-August/017880.html create mode 100644 zarb-ml/mageia-dev/2012-August/017881.html create mode 100644 zarb-ml/mageia-dev/2012-August/017882.html create mode 100644 zarb-ml/mageia-dev/2012-August/017883.html create mode 100644 zarb-ml/mageia-dev/2012-August/017884.html create mode 100644 zarb-ml/mageia-dev/2012-August/017885.html create mode 100644 zarb-ml/mageia-dev/2012-August/017886.html create mode 100644 zarb-ml/mageia-dev/2012-August/017887.html create mode 100644 zarb-ml/mageia-dev/2012-August/017888.html create mode 100644 zarb-ml/mageia-dev/2012-August/017889.html create mode 100644 zarb-ml/mageia-dev/2012-August/017890.html create mode 100644 zarb-ml/mageia-dev/2012-August/017891.html create mode 100644 zarb-ml/mageia-dev/2012-August/017892.html create mode 100644 zarb-ml/mageia-dev/2012-August/017893.html create mode 100644 zarb-ml/mageia-dev/2012-August/017894.html create mode 100644 zarb-ml/mageia-dev/2012-August/017895.html create mode 100644 zarb-ml/mageia-dev/2012-August/017896.html create mode 100644 zarb-ml/mageia-dev/2012-August/017897.html create mode 100644 zarb-ml/mageia-dev/2012-August/017898.html create mode 100644 zarb-ml/mageia-dev/2012-August/017899.html create mode 100644 zarb-ml/mageia-dev/2012-August/017900.html create mode 100644 zarb-ml/mageia-dev/2012-August/017901.html create mode 100644 zarb-ml/mageia-dev/2012-August/017902.html create mode 100644 zarb-ml/mageia-dev/2012-August/017903.html create mode 100644 zarb-ml/mageia-dev/2012-August/017904.html create mode 100644 zarb-ml/mageia-dev/2012-August/017905.html create mode 100644 zarb-ml/mageia-dev/2012-August/017906.html create mode 100644 zarb-ml/mageia-dev/2012-August/017907.html create mode 100644 zarb-ml/mageia-dev/2012-August/017908.html create mode 100644 zarb-ml/mageia-dev/2012-August/017909.html create mode 100644 zarb-ml/mageia-dev/2012-August/017910.html create mode 100644 zarb-ml/mageia-dev/2012-August/017911.html create mode 100644 zarb-ml/mageia-dev/2012-August/017912.html create mode 100644 zarb-ml/mageia-dev/2012-August/017913.html create mode 100644 zarb-ml/mageia-dev/2012-August/017914.html create mode 100644 zarb-ml/mageia-dev/2012-August/017915.html create mode 100644 zarb-ml/mageia-dev/2012-August/017916.html create mode 100644 zarb-ml/mageia-dev/2012-August/017917.html create mode 100644 zarb-ml/mageia-dev/2012-August/017918.html create mode 100644 zarb-ml/mageia-dev/2012-August/017919.html create mode 100644 zarb-ml/mageia-dev/2012-August/017920.html create mode 100644 zarb-ml/mageia-dev/2012-August/017921.html create mode 100644 zarb-ml/mageia-dev/2012-August/017922.html create mode 100644 zarb-ml/mageia-dev/2012-August/017923.html create mode 100644 zarb-ml/mageia-dev/2012-August/017924.html create mode 100644 zarb-ml/mageia-dev/2012-August/017925.html create mode 100644 zarb-ml/mageia-dev/2012-August/017926.html create mode 100644 zarb-ml/mageia-dev/2012-August/017927.html create mode 100644 zarb-ml/mageia-dev/2012-August/017928.html create mode 100644 zarb-ml/mageia-dev/2012-August/017929.html create mode 100644 zarb-ml/mageia-dev/2012-August/017930.html create mode 100644 zarb-ml/mageia-dev/2012-August/017931.html create mode 100644 zarb-ml/mageia-dev/2012-August/017932.html create mode 100644 zarb-ml/mageia-dev/2012-August/017933.html create mode 100644 zarb-ml/mageia-dev/2012-August/017934.html create mode 100644 zarb-ml/mageia-dev/2012-August/017935.html create mode 100644 zarb-ml/mageia-dev/2012-August/017936.html create mode 100644 zarb-ml/mageia-dev/2012-August/017937.html create mode 100644 zarb-ml/mageia-dev/2012-August/017938.html create mode 100644 zarb-ml/mageia-dev/2012-August/017939.html create mode 100644 zarb-ml/mageia-dev/2012-August/017940.html create mode 100644 zarb-ml/mageia-dev/2012-August/017941.html create mode 100644 zarb-ml/mageia-dev/2012-August/017942.html create mode 100644 zarb-ml/mageia-dev/2012-August/017943.html create mode 100644 zarb-ml/mageia-dev/2012-August/017944.html create mode 100644 zarb-ml/mageia-dev/2012-August/017945.html create mode 100644 zarb-ml/mageia-dev/2012-August/017946.html create mode 100644 zarb-ml/mageia-dev/2012-August/017947.html create mode 100644 zarb-ml/mageia-dev/2012-August/017948.html create mode 100644 zarb-ml/mageia-dev/2012-August/017949.html create mode 100644 zarb-ml/mageia-dev/2012-August/017950.html create mode 100644 zarb-ml/mageia-dev/2012-August/017951.html create mode 100644 zarb-ml/mageia-dev/2012-August/017952.html create mode 100644 zarb-ml/mageia-dev/2012-August/017953.html create mode 100644 zarb-ml/mageia-dev/2012-August/017954.html create mode 100644 zarb-ml/mageia-dev/2012-August/017955.html create mode 100644 zarb-ml/mageia-dev/2012-August/017956.html create mode 100644 zarb-ml/mageia-dev/2012-August/017957.html create mode 100644 zarb-ml/mageia-dev/2012-August/017958.html create mode 100644 zarb-ml/mageia-dev/2012-August/017959.html create mode 100644 zarb-ml/mageia-dev/2012-August/017960.html create mode 100644 zarb-ml/mageia-dev/2012-August/017961.html create mode 100644 zarb-ml/mageia-dev/2012-August/017962.html create mode 100644 zarb-ml/mageia-dev/2012-August/017963.html create mode 100644 zarb-ml/mageia-dev/2012-August/017964.html create mode 100644 zarb-ml/mageia-dev/2012-August/017965.html create mode 100644 zarb-ml/mageia-dev/2012-August/017966.html create mode 100644 zarb-ml/mageia-dev/2012-August/017967.html create mode 100644 zarb-ml/mageia-dev/2012-August/017968.html create mode 100644 zarb-ml/mageia-dev/2012-August/017969.html create mode 100644 zarb-ml/mageia-dev/2012-August/017970.html create mode 100644 zarb-ml/mageia-dev/2012-August/017971.html create mode 100644 zarb-ml/mageia-dev/2012-August/017972.html create mode 100644 zarb-ml/mageia-dev/2012-August/017973.html create mode 100644 zarb-ml/mageia-dev/2012-August/017974.html create mode 100644 zarb-ml/mageia-dev/2012-August/017975.html create mode 100644 zarb-ml/mageia-dev/2012-August/017976.html create mode 100644 zarb-ml/mageia-dev/2012-August/017977.html create mode 100644 zarb-ml/mageia-dev/2012-August/017978.html create mode 100644 zarb-ml/mageia-dev/2012-August/017979.html create mode 100644 zarb-ml/mageia-dev/2012-August/017980.html create mode 100644 zarb-ml/mageia-dev/2012-August/017981.html create mode 100644 zarb-ml/mageia-dev/2012-August/017982.html create mode 100644 zarb-ml/mageia-dev/2012-August/017983.html create mode 100644 zarb-ml/mageia-dev/2012-August/017984.html create mode 100644 zarb-ml/mageia-dev/2012-August/017985.html create mode 100644 zarb-ml/mageia-dev/2012-August/017986.html create mode 100644 zarb-ml/mageia-dev/2012-August/017987.html create mode 100644 zarb-ml/mageia-dev/2012-August/017988.html create mode 100644 zarb-ml/mageia-dev/2012-August/017989.html create mode 100644 zarb-ml/mageia-dev/2012-August/017990.html create mode 100644 zarb-ml/mageia-dev/2012-August/017991.html create mode 100644 zarb-ml/mageia-dev/2012-August/017992.html create mode 100644 zarb-ml/mageia-dev/2012-August/017993.html create mode 100644 zarb-ml/mageia-dev/2012-August/017994.html create mode 100644 zarb-ml/mageia-dev/2012-August/017995.html create mode 100644 zarb-ml/mageia-dev/2012-August/017996.html create mode 100644 zarb-ml/mageia-dev/2012-August/017997.html create mode 100644 zarb-ml/mageia-dev/2012-August/017998.html create mode 100644 zarb-ml/mageia-dev/2012-August/017999.html create mode 100644 zarb-ml/mageia-dev/2012-August/018000.html create mode 100644 zarb-ml/mageia-dev/2012-August/018001.html create mode 100644 zarb-ml/mageia-dev/2012-August/018002.html create mode 100644 zarb-ml/mageia-dev/2012-August/018003.html create mode 100644 zarb-ml/mageia-dev/2012-August/018004.html create mode 100644 zarb-ml/mageia-dev/2012-August/018005.html create mode 100644 zarb-ml/mageia-dev/2012-August/018006.html create mode 100644 zarb-ml/mageia-dev/2012-August/018007.html create mode 100644 zarb-ml/mageia-dev/2012-August/018008.html create mode 100644 zarb-ml/mageia-dev/2012-August/018009.html create mode 100644 zarb-ml/mageia-dev/2012-August/018010.html create mode 100644 zarb-ml/mageia-dev/2012-August/018011.html create mode 100644 zarb-ml/mageia-dev/2012-August/018012.html create mode 100644 zarb-ml/mageia-dev/2012-August/018013.html create mode 100644 zarb-ml/mageia-dev/2012-August/018014.html create mode 100644 zarb-ml/mageia-dev/2012-August/018015.html create mode 100644 zarb-ml/mageia-dev/2012-August/018016.html create mode 100644 zarb-ml/mageia-dev/2012-August/018017.html create mode 100644 zarb-ml/mageia-dev/2012-August/018018.html create mode 100644 zarb-ml/mageia-dev/2012-August/018019.html create mode 100644 zarb-ml/mageia-dev/2012-August/018020.html create mode 100644 zarb-ml/mageia-dev/2012-August/018021.html create mode 100644 zarb-ml/mageia-dev/2012-August/018022.html create mode 100644 zarb-ml/mageia-dev/2012-August/018023.html create mode 100644 zarb-ml/mageia-dev/2012-August/018024.html create mode 100644 zarb-ml/mageia-dev/2012-August/018025.html create mode 100644 zarb-ml/mageia-dev/2012-August/018026.html create mode 100644 zarb-ml/mageia-dev/2012-August/018027.html create mode 100644 zarb-ml/mageia-dev/2012-August/018028.html create mode 100644 zarb-ml/mageia-dev/2012-August/018029.html create mode 100644 zarb-ml/mageia-dev/2012-August/018030.html create mode 100644 zarb-ml/mageia-dev/2012-August/018031.html create mode 100644 zarb-ml/mageia-dev/2012-August/018032.html create mode 100644 zarb-ml/mageia-dev/2012-August/018033.html create mode 100644 zarb-ml/mageia-dev/2012-August/018034.html create mode 100644 zarb-ml/mageia-dev/2012-August/018035.html create mode 100644 zarb-ml/mageia-dev/2012-August/018036.html create mode 100644 zarb-ml/mageia-dev/2012-August/018037.html create mode 100644 zarb-ml/mageia-dev/2012-August/018038.html create mode 100644 zarb-ml/mageia-dev/2012-August/018039.html create mode 100644 zarb-ml/mageia-dev/2012-August/018040.html create mode 100644 zarb-ml/mageia-dev/2012-August/018041.html create mode 100644 zarb-ml/mageia-dev/2012-August/018042.html create mode 100644 zarb-ml/mageia-dev/2012-August/018043.html create mode 100644 zarb-ml/mageia-dev/2012-August/018044.html create mode 100644 zarb-ml/mageia-dev/2012-August/018045.html create mode 100644 zarb-ml/mageia-dev/2012-August/018046.html create mode 100644 zarb-ml/mageia-dev/2012-August/018047.html create mode 100644 zarb-ml/mageia-dev/2012-August/018048.html create mode 100644 zarb-ml/mageia-dev/2012-August/018049.html create mode 100644 zarb-ml/mageia-dev/2012-August/018050.html create mode 100644 zarb-ml/mageia-dev/2012-August/018051.html create mode 100644 zarb-ml/mageia-dev/2012-August/018052.html create mode 100644 zarb-ml/mageia-dev/2012-August/018053.html create mode 100644 zarb-ml/mageia-dev/2012-August/018054.html create mode 100644 zarb-ml/mageia-dev/2012-August/018055.html create mode 100644 zarb-ml/mageia-dev/2012-August/018056.html create mode 100644 zarb-ml/mageia-dev/2012-August/018057.html create mode 100644 zarb-ml/mageia-dev/2012-August/018058.html create mode 100644 zarb-ml/mageia-dev/2012-August/018059.html create mode 100644 zarb-ml/mageia-dev/2012-August/018060.html create mode 100644 zarb-ml/mageia-dev/2012-August/018061.html create mode 100644 zarb-ml/mageia-dev/2012-August/018062.html create mode 100644 zarb-ml/mageia-dev/2012-August/018063.html create mode 100644 zarb-ml/mageia-dev/2012-August/018064.html create mode 100644 zarb-ml/mageia-dev/2012-August/018065.html create mode 100644 zarb-ml/mageia-dev/2012-August/018066.html create mode 100644 zarb-ml/mageia-dev/2012-August/018067.html create mode 100644 zarb-ml/mageia-dev/2012-August/018068.html create mode 100644 zarb-ml/mageia-dev/2012-August/018069.html create mode 100644 zarb-ml/mageia-dev/2012-August/018070.html create mode 100644 zarb-ml/mageia-dev/2012-August/018071.html create mode 100644 zarb-ml/mageia-dev/2012-August/018072.html create mode 100644 zarb-ml/mageia-dev/2012-August/018073.html create mode 100644 zarb-ml/mageia-dev/2012-August/018074.html create mode 100644 zarb-ml/mageia-dev/2012-August/018075.html create mode 100644 zarb-ml/mageia-dev/2012-August/018076.html create mode 100644 zarb-ml/mageia-dev/2012-August/018077.html create mode 100644 zarb-ml/mageia-dev/2012-August/018078.html create mode 100644 zarb-ml/mageia-dev/2012-August/018079.html create mode 100644 zarb-ml/mageia-dev/2012-August/018080.html create mode 100644 zarb-ml/mageia-dev/2012-August/018081.html create mode 100644 zarb-ml/mageia-dev/2012-August/018082.html create mode 100644 zarb-ml/mageia-dev/2012-August/018083.html create mode 100644 zarb-ml/mageia-dev/2012-August/018084.html create mode 100644 zarb-ml/mageia-dev/2012-August/018085.html create mode 100644 zarb-ml/mageia-dev/2012-August/018086.html create mode 100644 zarb-ml/mageia-dev/2012-August/018087.html create mode 100644 zarb-ml/mageia-dev/2012-August/018088.html create mode 100644 zarb-ml/mageia-dev/2012-August/018089.html create mode 100644 zarb-ml/mageia-dev/2012-August/018090.html create mode 100644 zarb-ml/mageia-dev/2012-August/018091.html create mode 100644 zarb-ml/mageia-dev/2012-August/018092.html create mode 100644 zarb-ml/mageia-dev/2012-August/018093.html create mode 100644 zarb-ml/mageia-dev/2012-August/018094.html create mode 100644 zarb-ml/mageia-dev/2012-August/018095.html create mode 100644 zarb-ml/mageia-dev/2012-August/018096.html create mode 100644 zarb-ml/mageia-dev/2012-August/018097.html create mode 100644 zarb-ml/mageia-dev/2012-August/018098.html create mode 100644 zarb-ml/mageia-dev/2012-August/018099.html create mode 100644 zarb-ml/mageia-dev/2012-August/018100.html create mode 100644 zarb-ml/mageia-dev/2012-August/018101.html create mode 100644 zarb-ml/mageia-dev/2012-August/018102.html create mode 100644 zarb-ml/mageia-dev/2012-August/018103.html create mode 100644 zarb-ml/mageia-dev/2012-August/018104.html create mode 100644 zarb-ml/mageia-dev/2012-August/018105.html create mode 100644 zarb-ml/mageia-dev/2012-August/018106.html create mode 100644 zarb-ml/mageia-dev/2012-August/018107.html create mode 100644 zarb-ml/mageia-dev/2012-August/018108.html create mode 100644 zarb-ml/mageia-dev/2012-August/018109.html create mode 100644 zarb-ml/mageia-dev/2012-August/018110.html create mode 100644 zarb-ml/mageia-dev/2012-August/018111.html create mode 100644 zarb-ml/mageia-dev/2012-August/018112.html create mode 100644 zarb-ml/mageia-dev/2012-August/018113.html create mode 100644 zarb-ml/mageia-dev/2012-August/018114.html create mode 100644 zarb-ml/mageia-dev/2012-August/018115.html create mode 100644 zarb-ml/mageia-dev/2012-August/018116.html create mode 100644 zarb-ml/mageia-dev/2012-August/018117.html create mode 100644 zarb-ml/mageia-dev/2012-August/018118.html create mode 100644 zarb-ml/mageia-dev/2012-August/018119.html create mode 100644 zarb-ml/mageia-dev/2012-August/018120.html create mode 100644 zarb-ml/mageia-dev/2012-August/018121.html create mode 100644 zarb-ml/mageia-dev/2012-August/018122.html create mode 100644 zarb-ml/mageia-dev/2012-August/018123.html create mode 100644 zarb-ml/mageia-dev/2012-August/018124.html create mode 100644 zarb-ml/mageia-dev/2012-August/018125.html create mode 100644 zarb-ml/mageia-dev/2012-August/018126.html create mode 100644 zarb-ml/mageia-dev/2012-August/018127.html create mode 100644 zarb-ml/mageia-dev/2012-August/018128.html create mode 100644 zarb-ml/mageia-dev/2012-August/018129.html create mode 100644 zarb-ml/mageia-dev/2012-August/018130.html create mode 100644 zarb-ml/mageia-dev/2012-August/018131.html create mode 100644 zarb-ml/mageia-dev/2012-August/018132.html create mode 100644 zarb-ml/mageia-dev/2012-August/018133.html create mode 100644 zarb-ml/mageia-dev/2012-August/018134.html create mode 100644 zarb-ml/mageia-dev/2012-August/018135.html create mode 100644 zarb-ml/mageia-dev/2012-August/018136.html create mode 100644 zarb-ml/mageia-dev/2012-August/018137.html create mode 100644 zarb-ml/mageia-dev/2012-August/018138.html create mode 100644 zarb-ml/mageia-dev/2012-August/018139.html create mode 100644 zarb-ml/mageia-dev/2012-August/018140.html create mode 100644 zarb-ml/mageia-dev/2012-August/018141.html create mode 100644 zarb-ml/mageia-dev/2012-August/018142.html create mode 100644 zarb-ml/mageia-dev/2012-August/018143.html create mode 100644 zarb-ml/mageia-dev/2012-August/018144.html create mode 100644 zarb-ml/mageia-dev/2012-August/018145.html create mode 100644 zarb-ml/mageia-dev/2012-August/018146.html create mode 100644 zarb-ml/mageia-dev/2012-August/018147.html create mode 100644 zarb-ml/mageia-dev/2012-August/018148.html create mode 100644 zarb-ml/mageia-dev/2012-August/018149.html create mode 100644 zarb-ml/mageia-dev/2012-August/018150.html create mode 100644 zarb-ml/mageia-dev/2012-August/018151.html create mode 100644 zarb-ml/mageia-dev/2012-August/018152.html create mode 100644 zarb-ml/mageia-dev/2012-August/018153.html create mode 100644 zarb-ml/mageia-dev/2012-August/018154.html create mode 100644 zarb-ml/mageia-dev/2012-August/018155.html create mode 100644 zarb-ml/mageia-dev/2012-August/018156.html create mode 100644 zarb-ml/mageia-dev/2012-August/018157.html create mode 100644 zarb-ml/mageia-dev/2012-August/018158.html create mode 100644 zarb-ml/mageia-dev/2012-August/018159.html create mode 100644 zarb-ml/mageia-dev/2012-August/018160.html create mode 100644 zarb-ml/mageia-dev/2012-August/018161.html create mode 100644 zarb-ml/mageia-dev/2012-August/018162.html create mode 100644 zarb-ml/mageia-dev/2012-August/018163.html create mode 100644 zarb-ml/mageia-dev/2012-August/018164.html create mode 100644 zarb-ml/mageia-dev/2012-August/018165.html create mode 100644 zarb-ml/mageia-dev/2012-August/018166.html create mode 100644 zarb-ml/mageia-dev/2012-August/018167.html create mode 100644 zarb-ml/mageia-dev/2012-August/018168.html create mode 100644 zarb-ml/mageia-dev/2012-August/018169.html create mode 100644 zarb-ml/mageia-dev/2012-August/018170.html create mode 100644 zarb-ml/mageia-dev/2012-August/018171.html create mode 100644 zarb-ml/mageia-dev/2012-August/018172.html create mode 100644 zarb-ml/mageia-dev/2012-August/018173.html create mode 100644 zarb-ml/mageia-dev/2012-August/018174.html create mode 100644 zarb-ml/mageia-dev/2012-August/018175.html create mode 100644 zarb-ml/mageia-dev/2012-August/018176.html create mode 100644 zarb-ml/mageia-dev/2012-August/018177.html create mode 100644 zarb-ml/mageia-dev/2012-August/018178.html create mode 100644 zarb-ml/mageia-dev/2012-August/018179.html create mode 100644 zarb-ml/mageia-dev/2012-August/018180.html create mode 100644 zarb-ml/mageia-dev/2012-August/018181.html create mode 100644 zarb-ml/mageia-dev/2012-August/018182.html create mode 100644 zarb-ml/mageia-dev/2012-August/018183.html create mode 100644 zarb-ml/mageia-dev/2012-August/018184.html create mode 100644 zarb-ml/mageia-dev/2012-August/018185.html create mode 100644 zarb-ml/mageia-dev/2012-August/018186.html create mode 100644 zarb-ml/mageia-dev/2012-August/018187.html create mode 100644 zarb-ml/mageia-dev/2012-August/018188.html create mode 100644 zarb-ml/mageia-dev/2012-August/018189.html create mode 100644 zarb-ml/mageia-dev/2012-August/018190.html create mode 100644 zarb-ml/mageia-dev/2012-August/018191.html create mode 100644 zarb-ml/mageia-dev/2012-August/018192.html create mode 100644 zarb-ml/mageia-dev/2012-August/018193.html create mode 100644 zarb-ml/mageia-dev/2012-August/018194.html create mode 100644 zarb-ml/mageia-dev/2012-August/018195.html create mode 100644 zarb-ml/mageia-dev/2012-August/018196.html create mode 100644 zarb-ml/mageia-dev/2012-August/018197.html create mode 100644 zarb-ml/mageia-dev/2012-August/018198.html create mode 100644 zarb-ml/mageia-dev/2012-August/018199.html create mode 100644 zarb-ml/mageia-dev/2012-August/018200.html create mode 100644 zarb-ml/mageia-dev/2012-August/018201.html create mode 100644 zarb-ml/mageia-dev/2012-August/018202.html create mode 100644 zarb-ml/mageia-dev/2012-August/018203.html create mode 100644 zarb-ml/mageia-dev/2012-August/018204.html create mode 100644 zarb-ml/mageia-dev/2012-August/018205.html create mode 100644 zarb-ml/mageia-dev/2012-August/018206.html create mode 100644 zarb-ml/mageia-dev/2012-August/018207.html create mode 100644 zarb-ml/mageia-dev/2012-August/018208.html create mode 100644 zarb-ml/mageia-dev/2012-August/018209.html create mode 100644 zarb-ml/mageia-dev/2012-August/018210.html create mode 100644 zarb-ml/mageia-dev/2012-August/018211.html create mode 100644 zarb-ml/mageia-dev/2012-August/018212.html create mode 100644 zarb-ml/mageia-dev/2012-August/018213.html create mode 100644 zarb-ml/mageia-dev/2012-August/018214.html create mode 100644 zarb-ml/mageia-dev/2012-August/018215.html create mode 100644 zarb-ml/mageia-dev/2012-August/018216.html create mode 100644 zarb-ml/mageia-dev/2012-August/018217.html create mode 100644 zarb-ml/mageia-dev/2012-August/018218.html create mode 100644 zarb-ml/mageia-dev/2012-August/018219.html create mode 100644 zarb-ml/mageia-dev/2012-August/018220.html create mode 100644 zarb-ml/mageia-dev/2012-August/018221.html create mode 100644 zarb-ml/mageia-dev/2012-August/018222.html create mode 100644 zarb-ml/mageia-dev/2012-August/018223.html create mode 100644 zarb-ml/mageia-dev/2012-August/018224.html create mode 100644 zarb-ml/mageia-dev/2012-August/018225.html create mode 100644 zarb-ml/mageia-dev/2012-August/018226.html create mode 100644 zarb-ml/mageia-dev/2012-August/018227.html create mode 100644 zarb-ml/mageia-dev/2012-August/018228.html create mode 100644 zarb-ml/mageia-dev/2012-August/018229.html create mode 100644 zarb-ml/mageia-dev/2012-August/018230.html create mode 100644 zarb-ml/mageia-dev/2012-August/018231.html create mode 100644 zarb-ml/mageia-dev/2012-August/018232.html create mode 100644 zarb-ml/mageia-dev/2012-August/018233.html create mode 100644 zarb-ml/mageia-dev/2012-August/018234.html create mode 100644 zarb-ml/mageia-dev/2012-August/018235.html create mode 100644 zarb-ml/mageia-dev/2012-August/018236.html create mode 100644 zarb-ml/mageia-dev/2012-August/018237.html create mode 100644 zarb-ml/mageia-dev/2012-August/018238.html create mode 100644 zarb-ml/mageia-dev/2012-August/018239.html create mode 100644 zarb-ml/mageia-dev/2012-August/018240.html create mode 100644 zarb-ml/mageia-dev/2012-August/018241.html create mode 100644 zarb-ml/mageia-dev/2012-August/018242.html create mode 100644 zarb-ml/mageia-dev/2012-August/018243.html create mode 100644 zarb-ml/mageia-dev/2012-August/018244.html create mode 100644 zarb-ml/mageia-dev/2012-August/018245.html create mode 100644 zarb-ml/mageia-dev/2012-August/018246.html create mode 100644 zarb-ml/mageia-dev/2012-August/018247.html create mode 100644 zarb-ml/mageia-dev/2012-August/018248.html create mode 100644 zarb-ml/mageia-dev/2012-August/018249.html create mode 100644 zarb-ml/mageia-dev/2012-August/018250.html create mode 100644 zarb-ml/mageia-dev/2012-August/018251.html create mode 100644 zarb-ml/mageia-dev/2012-August/018252.html create mode 100644 zarb-ml/mageia-dev/2012-August/018253.html create mode 100644 zarb-ml/mageia-dev/2012-August/018254.html create mode 100644 zarb-ml/mageia-dev/2012-August/018255.html create mode 100644 zarb-ml/mageia-dev/2012-August/018256.html create mode 100644 zarb-ml/mageia-dev/2012-August/018257.html create mode 100644 zarb-ml/mageia-dev/2012-August/018258.html create mode 100644 zarb-ml/mageia-dev/2012-August/018259.html create mode 100644 zarb-ml/mageia-dev/2012-August/018260.html create mode 100644 zarb-ml/mageia-dev/2012-August/018261.html create mode 100644 zarb-ml/mageia-dev/2012-August/018262.html create mode 100644 zarb-ml/mageia-dev/2012-August/018263.html create mode 100644 zarb-ml/mageia-dev/2012-August/018264.html create mode 100644 zarb-ml/mageia-dev/2012-August/018265.html create mode 100644 zarb-ml/mageia-dev/2012-August/018266.html create mode 100644 zarb-ml/mageia-dev/2012-August/018267.html create mode 100644 zarb-ml/mageia-dev/2012-August/018268.html create mode 100644 zarb-ml/mageia-dev/2012-August/018269.html create mode 100644 zarb-ml/mageia-dev/2012-August/018270.html create mode 100644 zarb-ml/mageia-dev/2012-August/018271.html create mode 100644 zarb-ml/mageia-dev/2012-August/018272.html create mode 100644 zarb-ml/mageia-dev/2012-August/018273.html create mode 100644 zarb-ml/mageia-dev/2012-August/018274.html create mode 100644 zarb-ml/mageia-dev/2012-August/018275.html create mode 100644 zarb-ml/mageia-dev/2012-August/018276.html create mode 100644 zarb-ml/mageia-dev/2012-August/018277.html create mode 100644 zarb-ml/mageia-dev/2012-August/018278.html create mode 100644 zarb-ml/mageia-dev/2012-August/018279.html create mode 100644 zarb-ml/mageia-dev/2012-August/018280.html create mode 100644 zarb-ml/mageia-dev/2012-August/018281.html create mode 100644 zarb-ml/mageia-dev/2012-August/018282.html create mode 100644 zarb-ml/mageia-dev/2012-August/018283.html create mode 100644 zarb-ml/mageia-dev/2012-August/018284.html create mode 100644 zarb-ml/mageia-dev/2012-August/018285.html create mode 100644 zarb-ml/mageia-dev/2012-August/018286.html create mode 100644 zarb-ml/mageia-dev/2012-August/018287.html create mode 100644 zarb-ml/mageia-dev/2012-August/018288.html create mode 100644 zarb-ml/mageia-dev/2012-August/018289.html create mode 100644 zarb-ml/mageia-dev/2012-August/018290.html create mode 100644 zarb-ml/mageia-dev/2012-August/018291.html create mode 100644 zarb-ml/mageia-dev/2012-August/018292.html create mode 100644 zarb-ml/mageia-dev/2012-August/018293.html create mode 100644 zarb-ml/mageia-dev/2012-August/018294.html create mode 100644 zarb-ml/mageia-dev/2012-August/018295.html create mode 100644 zarb-ml/mageia-dev/2012-August/018296.html create mode 100644 zarb-ml/mageia-dev/2012-August/018297.html create mode 100644 zarb-ml/mageia-dev/2012-August/018298.html create mode 100644 zarb-ml/mageia-dev/2012-August/018299.html create mode 100644 zarb-ml/mageia-dev/2012-August/018300.html create mode 100644 zarb-ml/mageia-dev/2012-August/018301.html create mode 100644 zarb-ml/mageia-dev/2012-August/018302.html create mode 100644 zarb-ml/mageia-dev/2012-August/018303.html create mode 100644 zarb-ml/mageia-dev/2012-August/018304.html create mode 100644 zarb-ml/mageia-dev/2012-August/018305.html create mode 100644 zarb-ml/mageia-dev/2012-August/018306.html create mode 100644 zarb-ml/mageia-dev/2012-August/018307.html create mode 100644 zarb-ml/mageia-dev/2012-August/018308.html create mode 100644 zarb-ml/mageia-dev/2012-August/018309.html create mode 100644 zarb-ml/mageia-dev/2012-August/018310.html create mode 100644 zarb-ml/mageia-dev/2012-August/018311.html create mode 100644 zarb-ml/mageia-dev/2012-August/018312.html create mode 100644 zarb-ml/mageia-dev/2012-August/018313.html create mode 100644 zarb-ml/mageia-dev/2012-August/018314.html create mode 100644 zarb-ml/mageia-dev/2012-August/018315.html create mode 100644 zarb-ml/mageia-dev/2012-August/018316.html create mode 100644 zarb-ml/mageia-dev/2012-August/018317.html create mode 100644 zarb-ml/mageia-dev/2012-August/018318.html create mode 100644 zarb-ml/mageia-dev/2012-August/018319.html create mode 100644 zarb-ml/mageia-dev/2012-August/018320.html create mode 100644 zarb-ml/mageia-dev/2012-August/018321.html create mode 100644 zarb-ml/mageia-dev/2012-August/018322.html create mode 100644 zarb-ml/mageia-dev/2012-August/018323.html create mode 100644 zarb-ml/mageia-dev/2012-August/018324.html create mode 100644 zarb-ml/mageia-dev/2012-August/018325.html create mode 100644 zarb-ml/mageia-dev/2012-August/018326.html create mode 100644 zarb-ml/mageia-dev/2012-August/018327.html create mode 100644 zarb-ml/mageia-dev/2012-August/018328.html create mode 100644 zarb-ml/mageia-dev/2012-August/018329.html create mode 100644 zarb-ml/mageia-dev/2012-August/018330.html create mode 100644 zarb-ml/mageia-dev/2012-August/018331.html create mode 100644 zarb-ml/mageia-dev/2012-August/018332.html create mode 100644 zarb-ml/mageia-dev/2012-August/018333.html create mode 100644 zarb-ml/mageia-dev/2012-August/018334.html create mode 100644 zarb-ml/mageia-dev/2012-August/018335.html create mode 100644 zarb-ml/mageia-dev/2012-August/018336.html create mode 100644 zarb-ml/mageia-dev/2012-August/018337.html create mode 100644 zarb-ml/mageia-dev/2012-August/018338.html create mode 100644 zarb-ml/mageia-dev/2012-August/018339.html create mode 100644 zarb-ml/mageia-dev/2012-August/018340.html create mode 100644 zarb-ml/mageia-dev/2012-August/018341.html create mode 100644 zarb-ml/mageia-dev/2012-August/018342.html create mode 100644 zarb-ml/mageia-dev/2012-August/018343.html create mode 100644 zarb-ml/mageia-dev/2012-August/018344.html create mode 100644 zarb-ml/mageia-dev/2012-August/018345.html create mode 100644 zarb-ml/mageia-dev/2012-August/018346.html create mode 100644 zarb-ml/mageia-dev/2012-August/018347.html create mode 100644 zarb-ml/mageia-dev/2012-August/018348.html create mode 100644 zarb-ml/mageia-dev/2012-August/018349.html create mode 100644 zarb-ml/mageia-dev/2012-August/018350.html create mode 100644 zarb-ml/mageia-dev/2012-August/018351.html create mode 100644 zarb-ml/mageia-dev/2012-August/018352.html create mode 100644 zarb-ml/mageia-dev/2012-August/018353.html create mode 100644 zarb-ml/mageia-dev/2012-August/018354.html create mode 100644 zarb-ml/mageia-dev/2012-August/018355.html create mode 100644 zarb-ml/mageia-dev/2012-August/018356.html create mode 100644 zarb-ml/mageia-dev/2012-August/018357.html create mode 100644 zarb-ml/mageia-dev/2012-August/018358.html create mode 100644 zarb-ml/mageia-dev/2012-August/018359.html create mode 100644 zarb-ml/mageia-dev/2012-August/018360.html create mode 100644 zarb-ml/mageia-dev/2012-August/018361.html create mode 100644 zarb-ml/mageia-dev/2012-August/018362.html create mode 100644 zarb-ml/mageia-dev/2012-August/018363.html create mode 100644 zarb-ml/mageia-dev/2012-August/018364.html create mode 100644 zarb-ml/mageia-dev/2012-August/018365.html create mode 100644 zarb-ml/mageia-dev/2012-August/018366.html create mode 100644 zarb-ml/mageia-dev/2012-August/018367.html create mode 100644 zarb-ml/mageia-dev/2012-August/018368.html create mode 100644 zarb-ml/mageia-dev/2012-August/018369.html create mode 100644 zarb-ml/mageia-dev/2012-August/018370.html create mode 100644 zarb-ml/mageia-dev/2012-August/018371.html create mode 100644 zarb-ml/mageia-dev/2012-August/018372.html create mode 100644 zarb-ml/mageia-dev/2012-August/018373.html create mode 100644 zarb-ml/mageia-dev/2012-August/018374.html create mode 100644 zarb-ml/mageia-dev/2012-August/018375.html create mode 100644 zarb-ml/mageia-dev/2012-August/018376.html create mode 100644 zarb-ml/mageia-dev/2012-August/018377.html create mode 100644 zarb-ml/mageia-dev/2012-August/018378.html create mode 100644 zarb-ml/mageia-dev/2012-August/018379.html create mode 100644 zarb-ml/mageia-dev/2012-August/018380.html create mode 100644 zarb-ml/mageia-dev/2012-August/018381.html create mode 100644 zarb-ml/mageia-dev/2012-August/018382.html create mode 100644 zarb-ml/mageia-dev/2012-August/018383.html create mode 100644 zarb-ml/mageia-dev/2012-August/018384.html create mode 100644 zarb-ml/mageia-dev/2012-August/018385.html create mode 100644 zarb-ml/mageia-dev/2012-August/018386.html create mode 100644 zarb-ml/mageia-dev/2012-August/018387.html create mode 100644 zarb-ml/mageia-dev/2012-August/018388.html create mode 100644 zarb-ml/mageia-dev/2012-August/018389.html create mode 100644 zarb-ml/mageia-dev/2012-August/018390.html create mode 100644 zarb-ml/mageia-dev/2012-August/018391.html create mode 100644 zarb-ml/mageia-dev/2012-August/018392.html create mode 100644 zarb-ml/mageia-dev/2012-August/018393.html create mode 100644 zarb-ml/mageia-dev/2012-August/018394.html create mode 100644 zarb-ml/mageia-dev/2012-August/018395.html create mode 100644 zarb-ml/mageia-dev/2012-August/018396.html create mode 100644 zarb-ml/mageia-dev/2012-August/author.html create mode 100644 zarb-ml/mageia-dev/2012-August/date.html create mode 120000 zarb-ml/mageia-dev/2012-August/index.html create mode 100644 zarb-ml/mageia-dev/2012-August/subject.html create mode 100644 zarb-ml/mageia-dev/2012-August/thread.html (limited to 'zarb-ml/mageia-dev/2012-August') diff --git a/zarb-ml/mageia-dev/2012-August/017841.html b/zarb-ml/mageia-dev/2012-August/017841.html new file mode 100644 index 000000000..4a7fc72f2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017841.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] Mageia 2 in VirtualBox fails to upgrade to Mageia Cauldron due to /usr move + + + + + + + + + +

[Mageia-dev] Mageia 2 in VirtualBox fails to upgrade to Mageia Cauldron due to /usr move

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Wed Aug 1 00:09:39 CEST 2012 +

+
+ +
Le mardi 31 juillet 2012 20:46:11 Shlomi Fish a écrit :
+> Hi John,
+> 
+> On Tue, 31 Jul 2012 14:42:03 -0300
+> 
+> John Balcaen <mikala at mageia.org> wrote:
+> > 2012/7/31 Shlomi Fish <shlomif at shlomifish.org>:
+> > > Hi all,
+> > > 
+> > > I am including here a log of the IRC conversation I had with some people
+> > > on
+> > > upgrading my x86-64 VBox virtual machine from Mageia 2 to Mageia Linux
+> > > Cauldron. I could not get an adequate answer regarding it from anyone
+> > > there and hope someone can help me here (I've waited long enough).
+> > > 
+> > > For the record, I'm trying to restore my backups into the VM to a
+> > > working
+> > 
+> > > state, and ran into a problem, see:
+> > [...]
+> > Did you install rpm/urpmi from updates/testing before ?
+> > If no you'll have (as i did) have to manually install first rpm &
+> > dependencies directly via rpm due to the filesystem require [1] ,
+> 
+> Where can I find a script that will do that for me? Is there one?
+
+I had this pb today when migrating one of my desktop machines from mageia 2 to 
+cauldron. I installed manually rpm from testing ( ftp://distrib-
+coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/2/i586/media/core/updates_testing/ 
+) and after all did well as wanted.
+
+so 
+
+1 install rpm from testing, 
+2- test  urpmi --auto-update ( should be fine ).
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017842.html b/zarb-ml/mageia-dev/2012-August/017842.html new file mode 100644 index 000000000..182df22e2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017842.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release attica-0.4.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release attica-0.4.0-1.mga3

+ Balcaen John + mikala at mageia.org +
+ Wed Aug 1 03:19:46 CEST 2012 +

+
+ +
Le mardi 31 juillet 2012 16:27:52 shlomif a écrit :
+> Name        : attica                       Relocations: (not relocatable)
+> Version     : 0.4.0                             Vendor: Mageia.Org
+> Release     : 1.mga3                        Build Date: Tue Jul 31 16:20:41
+> 2012 Install Date: (not installed)               Build Host:
+> ecosse.mageia.org Group       : System/Base                   Source RPM:
+> (none)
+> Size        : 59480                            License: GPLv2+
+> Signature   : (none)
+> Packager    : shlomif <shlomif>
+> URL         : https://projects.kde.org/projects/kdesupport/attica
+> Summary     : Open Collaboration Service providers library
+> Description :
+> A library to access Open Collaboration Service providers.
+> Required to access OSC providers in get hot new stuff in KDE4.
+> 
+> shlomif <shlomif> 0.4.0-1.mga3:
+> + Revision: 276773
+> - New version 0.4.0 - thanks to fedya
+Could you please ask to maintainer before committing & changing a spec.
+especially when this change force a rebuild of kde before a kde release ...
+
+-- 
+Mageia Contributor
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017843.html b/zarb-ml/mageia-dev/2012-August/017843.html new file mode 100644 index 000000000..25cb13cec --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017843.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Balcaen John + mikala at mageia.org +
+ Wed Aug 1 03:20:45 CEST 2012 +

+
+ +
Le mardi 31 juillet 2012 18:42:00 tv a écrit :
+> Name        : kdelibs4                     Relocations: (not relocatable)
+> Version     : 4.9.0                             Vendor: Mageia.Org
+> Release     : 2.mga3                        Build Date: Tue Jul 31 18:15:54
+> 2012 Install Date: (not installed)               Build Host:
+> ecosse.mageia.org Group       : Graphical desktop/KDE         Source RPM:
+> (none)
+> Size        : 11884847                         License: GPLv2 and LGPLv2 and
+> GFDL and BSD and QPL and Artistic Signature   : (none)
+> Packager    : tv <tv>
+> URL         : http://www.kde.org
+> Summary     : K Desktop Environment - Libraries
+> Description :
+> Libraries for the K Desktop Environment.
+> 
+> tv <tv> 2:4.9.0-2.mga3:
+> + Revision: 276808
+> - rebuild for new libattica
+> 
+>   + mikala <mikala>
+>     - Silent: Fix Source URL
+>     - Update tarball to KDE 4.9.0
+
+Oh damn that !!!
+kde 4.9.0 is not supposed to be released & now because a padawan without a 
+commit right send a patch, his mentor feels obligate to push the package 
+*without* checking the side effect of this change (yeah it's a update & we're 
+late let's push it ) of course we could have stay only with kdelibs 4.9.0 but 
+now i noticed that fwang is pushing the whole kde stack especially when we're 
+not sure that some kde package are not going to be respun ....
+damn that !
+
+I guess i'll won't commit anything more if it's just to see some stuff like 
+this .
+
+
+-- 
+Mageia Contributor
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017844.html b/zarb-ml/mageia-dev/2012-August/017844.html new file mode 100644 index 000000000..09e24d2c6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017844.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Wed Aug 1 03:44:32 CEST 2012 +

+
+ +
Le mardi 31 juillet 2012 22:20:45 Balcaen John a écrit :
+> Le mardi 31 juillet 2012 18:42:00 tv a écrit :
+> > Name        : kdelibs4                     Relocations: (not relocatable)
+> > Version     : 4.9.0                             Vendor: Mageia.Org
+> > Release     : 2.mga3                        Build Date: Tue Jul 31
+> > 18:15:54
+> > 2012 Install Date: (not installed)               Build Host:
+> > ecosse.mageia.org Group       : Graphical desktop/KDE         Source RPM:
+> > (none)
+> > Size        : 11884847                         License: GPLv2 and LGPLv2
+> > and GFDL and BSD and QPL and Artistic Signature   : (none)
+> > Packager    : tv <tv>
+> > URL         : http://www.kde.org
+> > Summary     : K Desktop Environment - Libraries
+> > Description :
+> > Libraries for the K Desktop Environment.
+> > 
+> > tv <tv> 2:4.9.0-2.mga3:
+> > + Revision: 276808
+> > - rebuild for new libattica
+> > 
+> >   + mikala <mikala>
+> >   
+> >     - Silent: Fix Source URL
+> >     - Update tarball to KDE 4.9.0
+> 
+> Oh damn that !!!
+> kde 4.9.0 is not supposed to be released & now because a padawan without a
+> commit right send a patch, his mentor feels obligate to push the package
+> *without* checking the side effect of this change (yeah it's a update &
+> we're late let's push it ) of course we could have stay only with kdelibs
+> 4.9.0 but now i noticed that fwang is pushing the whole kde stack
+> especially when we're not sure that some kde package are not going to be
+> respun ....
+> damn that !
+> 
+> I guess i'll won't commit anything more if it's just to see some stuff like
+> this .
+
+please don't, we need you :(
+
+Rindolf we can't loose packagers like mikala, you really need to follow rules.
+
+If you need more infos about rules please ask we are here to help but don't 
+touch mikala's packages w/o his authorisation.
+
+just do a mgarepo maintdb get $package    and see who is the maintainer and 
+ask before commiting.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017845.html b/zarb-ml/mageia-dev/2012-August/017845.html new file mode 100644 index 000000000..65a9a80ce --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017845.html @@ -0,0 +1,122 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Thomas Spuhler + thomas at btspuhler.com +
+ Wed Aug 1 05:05:02 CEST 2012 +

+
+ +
On Tuesday, July 31, 2012 06:44:32 PM Nicolas Lécureuil wrote:
+> Le mardi 31 juillet 2012 22:20:45 Balcaen John a écrit :
+> > Le mardi 31 juillet 2012 18:42:00 tv a écrit :
+> > > Name        : kdelibs4                     Relocations: (not
+> > > relocatable) Version     : 4.9.0                             Vendor:
+> > > Mageia.Org Release     : 2.mga3                        Build Date: Tue
+> > > Jul 31 18:15:54
+> > > 2012 Install Date: (not installed)               Build Host:
+> > > ecosse.mageia.org Group       : Graphical desktop/KDE         Source
+> > > RPM: (none)
+> > > Size        : 11884847                         License: GPLv2 and
+> > > LGPLv2 and GFDL and BSD and QPL and Artistic Signature   : (none)
+> > > Packager    : tv <tv>
+> > > URL         : http://www.kde.org
+> > > Summary     : K Desktop Environment - Libraries
+> > > Description :
+> > > Libraries for the K Desktop Environment.
+> > > 
+> > > tv <tv> 2:4.9.0-2.mga3:
+> > > + Revision: 276808
+> > > - rebuild for new libattica
+> > > 
+> > >   + mikala <mikala>
+> > >   
+> > >     - Silent: Fix Source URL
+> > >     - Update tarball to KDE 4.9.0
+> > 
+> > Oh damn that !!!
+> > kde 4.9.0 is not supposed to be released & now because a padawan without
+> > a commit right send a patch, his mentor feels obligate to push the
+> > package *without* checking the side effect of this change (yeah it's a
+> > update & we're late let's push it ) of course we could have stay only
+> > with kdelibs 4.9.0 but now i noticed that fwang is pushing the whole kde
+> > stack especially when we're not sure that some kde package are not going
+> > to be respun ....
+> > damn that !
+> > 
+> > I guess i'll won't commit anything more if it's just to see some stuff
+> > like this .
+> 
+> please don't, we need you :(
+> 
+> Rindolf we can't loose packagers like mikala, you really need to follow
+> rules.
+> 
+> If you need more infos about rules please ask we are here to help but don't
+> touch mikala's packages w/o his authorisation.
+> 
+> just do a mgarepo maintdb get $package    and see who is the maintainer and
+> ask before commiting.
+
+I would like to join this discussion. it's not very motivatingif you work on a 
+package (you are the owner) and then someone is going to upgrade it. We have a 
+lot of packages unmaintained and we do not have the resources for different 
+packagers doing the same work.
+
+I guess, the kde upgrade  now has to be completed because it broke the caulron 
+boxes. 
+I know  kamil has worked on upgrading boost and this morning I saw it pushed 
+by someone else.
+We all need help once in a while, maybe asking the maintainer would help?
+
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017846.html b/zarb-ml/mageia-dev/2012-August/017846.html new file mode 100644 index 000000000..d27b02e2a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017846.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] "svn copy" issiues - adding mdv2010.1/2 packages to mga1 and mga2 from Cauldron + + + + + + + + + +

[Mageia-dev] "svn copy" issiues - adding mdv2010.1/2 packages to mga1 and mga2 from Cauldron

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 1 06:37:00 CEST 2012 +

+
+ +
I'm about to copy a package (etc-update) from cauldron to 1/updates, as per the instructions on the wiki. (See bug 6178)
+Does anyone have a suggestion on what to write as the commit message? "importing blah" hardly seems correct when the package alreaddy exist in Cauldron but not in mga1 and mga2.
+
+
+Also, when attemting this copy, the vi editor window freeze, I cannot write anything, and so i have to kill vi.
+anyone else having this problem?
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120801/7d2dde33/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017847.html b/zarb-ml/mageia-dev/2012-August/017847.html new file mode 100644 index 000000000..f747abd01 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017847.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 1 08:46:29 CEST 2012 +

+
+ +
On 1 August 2012 05:29, fwang <buildsystem-daemon at mageia.org> wrote:
+> fwang <fwang> 3-21.mga3:
+> + Revision: 277136
+> - obsolete db5.2 in favour of db5.3
+
+# urpmi --auto-select --keep -vv --debug
+(...)
+installed libreoffice-core-3.6.0.1-1.mga3.x86_64 is conflicting
+because of unsatisfied libdb-5.2.so()(64bit)
+unselecting task-obsolete-3-21.mga3.noarch
+A requested package cannot be installed:
+task-obsolete-3-21.mga3.noarch (in order to keep
+libreoffice-core-3.6.0.1-1.mga3.x86_64)
+Continue installation anyway? (Y/n)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017848.html b/zarb-ml/mageia-dev/2012-August/017848.html new file mode 100644 index 000000000..3bae94bac --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017848.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Wed Aug 1 09:31:29 CEST 2012 +

+
+ +
Le 01/08/2012 08:46, Thierry Vignaud a écrit :
+> On 1 August 2012 05:29, fwang <buildsystem-daemon at mageia.org> wrote:
+>> fwang <fwang> 3-21.mga3:
+>> + Revision: 277136
+>> - obsolete db5.2 in favour of db5.3
+>
+> # urpmi --auto-select --keep -vv --debug
+> (...)
+> installed libreoffice-core-3.6.0.1-1.mga3.x86_64 is conflicting
+> because of unsatisfied libdb-5.2.so()(64bit)
+> unselecting task-obsolete-3-21.mga3.noarch
+> A requested package cannot be installed:
+> task-obsolete-3-21.mga3.noarch (in order to keep
+> libreoffice-core-3.6.0.1-1.mga3.x86_64)
+> Continue installation anyway? (Y/n)
+Whoever had the brilliant idea of forcing package uninstallation just 
+because "they are not supported anymore" deserve a good spanking... 
+Especially when applied to libraries, whereas shipping them in specific 
+versioned subpackage 'libfication' was meant precisely to avoid this issue.
+
+
+-- 
+BOFH excuse #344:
+
+Network failure -  call NBC
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017849.html b/zarb-ml/mageia-dev/2012-August/017849.html new file mode 100644 index 000000000..a74e34247 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017849.html @@ -0,0 +1,132 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Anne Nicolas + ennael at mageia.org +
+ Wed Aug 1 10:19:56 CEST 2012 +

+
+ +
Le 01/08/2012 05:05, Thomas Spuhler a écrit :
+> On Tuesday, July 31, 2012 06:44:32 PM Nicolas Lécureuil wrote:
+>> Le mardi 31 juillet 2012 22:20:45 Balcaen John a écrit :
+>>> Le mardi 31 juillet 2012 18:42:00 tv a écrit :
+>>>> Name        : kdelibs4                     Relocations: (not
+>>>> relocatable) Version     : 4.9.0                             Vendor:
+>>>> Mageia.Org Release     : 2.mga3                        Build Date: Tue
+>>>> Jul 31 18:15:54
+>>>> 2012 Install Date: (not installed)               Build Host:
+>>>> ecosse.mageia.org Group       : Graphical desktop/KDE         Source
+>>>> RPM: (none)
+>>>> Size        : 11884847                         License: GPLv2 and
+>>>> LGPLv2 and GFDL and BSD and QPL and Artistic Signature   : (none)
+>>>> Packager    : tv<tv>
+>>>> URL         : http://www.kde.org
+>>>> Summary     : K Desktop Environment - Libraries
+>>>> Description :
+>>>> Libraries for the K Desktop Environment.
+>>>>
+>>>> tv<tv>  2:4.9.0-2.mga3:
+>>>> + Revision: 276808
+>>>> - rebuild for new libattica
+>>>>
+>>>>    + mikala<mikala>
+>>>>
+>>>>      - Silent: Fix Source URL
+>>>>      - Update tarball to KDE 4.9.0
+>>>
+>>> Oh damn that !!!
+>>> kde 4.9.0 is not supposed to be released&  now because a padawan without
+>>> a commit right send a patch, his mentor feels obligate to push the
+>>> package *without* checking the side effect of this change (yeah it's a
+>>> update&  we're late let's push it ) of course we could have stay only
+>>> with kdelibs 4.9.0 but now i noticed that fwang is pushing the whole kde
+>>> stack especially when we're not sure that some kde package are not going
+>>> to be respun ....
+>>> damn that !
+>>>
+>>> I guess i'll won't commit anything more if it's just to see some stuff
+>>> like this .
+>>
+>> please don't, we need you :(
+>>
+>> Rindolf we can't loose packagers like mikala, you really need to follow
+>> rules.
+>>
+>> If you need more infos about rules please ask we are here to help but don't
+>> touch mikala's packages w/o his authorisation.
+>>
+>> just do a mgarepo maintdb get $package    and see who is the maintainer andy
+>> ask before commiting.
+>
+> I would like to join this discussion. it's not very motivatingif you work on a
+> package (you are the owner) and then someone is going to upgrade it. We have a
+> lot of packages unmaintained and we do not have the resources for different
+> packagers doing the same work.
+>
+> I guess, the kde upgrade  now has to be completed because it broke the caulron
+> boxes.
+> I know  kamil has worked on upgrading boost and this morning I saw it pushed
+> by someone else.
+> We all need help once in a while, maybe asking the maintainer would help?
+>
+
+Please try to work properly ie asking maintainer before. It takes a mail 
+to do it and save lot of work for everybody. This should be applied 
+especially by new comers and mentors. If not we will have to write some 
+strict rules down which is, imho, too restrictive while common sense 
+should be enough to avoid such situation. Rondolf, please, try to follow 
+this.
+
+Cheers
+
+-- 
+Anne
+http://mageia.org
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017850.html b/zarb-ml/mageia-dev/2012-August/017850.html new file mode 100644 index 000000000..5deb3bfc9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017850.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Sander Lepik + sander.lepik at eesti.ee +
+ Wed Aug 1 11:47:17 CEST 2012 +

+
+ +
01.08.2012 11:19, Anne Nicolas kirjutas:
+> Please try to work properly ie asking maintainer before. It takes a 
+> mail to do it and save lot of work for everybody. This should be 
+> applied especially by new comers and mentors. If not we will have to 
+> write some strict rules down which is, imho, too restrictive while 
+> common sense should be enough to avoid such situation. Rondolf, 
+> please, try to follow this.
+>
+> Cheers
+>
+What about wiki page where maintainers can state what they allow on 
+their packages w/o asking? Like "Updating minor versions is OK", "Always 
+ask before you touch", "Do whatever you like", etc. So other packagers 
+can check and don't have to wait for response. Of course maintainer can 
+add exceptions too.
+
+WDYT?
+
+--
+Sander
+
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017851.html b/zarb-ml/mageia-dev/2012-August/017851.html new file mode 100644 index 000000000..da1e25959 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017851.html @@ -0,0 +1,133 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Shlomi Fish + shlomif at shlomifish.org +
+ Wed Aug 1 12:00:42 CEST 2012 +

+
+ +
On Wed, 01 Aug 2012 03:44:32 +0200
+Nicolas Lécureuil <nicolas.lecureuil at free.fr> wrote:
+
+> Le mardi 31 juillet 2012 22:20:45 Balcaen John a écrit :
+> > Le mardi 31 juillet 2012 18:42:00 tv a écrit :
+> > > Name        : kdelibs4                     Relocations: (not relocatable)
+> > > Version     : 4.9.0                             Vendor: Mageia.Org
+> > > Release     : 2.mga3                        Build Date: Tue Jul 31
+> > > 18:15:54
+> > > 2012 Install Date: (not installed)               Build Host:
+> > > ecosse.mageia.org Group       : Graphical desktop/KDE         Source RPM:
+> > > (none)
+> > > Size        : 11884847                         License: GPLv2 and LGPLv2
+> > > and GFDL and BSD and QPL and Artistic Signature   : (none)
+> > > Packager    : tv <tv>
+> > > URL         : http://www.kde.org
+> > > Summary     : K Desktop Environment - Libraries
+> > > Description :
+> > > Libraries for the K Desktop Environment.
+> > > 
+> > > tv <tv> 2:4.9.0-2.mga3:
+> > > + Revision: 276808
+> > > - rebuild for new libattica
+> > > 
+> > >   + mikala <mikala>
+> > >   
+> > >     - Silent: Fix Source URL
+> > >     - Update tarball to KDE 4.9.0
+> > 
+> > Oh damn that !!!
+> > kde 4.9.0 is not supposed to be released & now because a padawan without a
+> > commit right send a patch, his mentor feels obligate to push the package
+> > *without* checking the side effect of this change (yeah it's a update &
+> > we're late let's push it ) of course we could have stay only with kdelibs
+> > 4.9.0 but now i noticed that fwang is pushing the whole kde stack
+> > especially when we're not sure that some kde package are not going to be
+> > respun ....
+> > damn that !
+> > 
+> > I guess i'll won't commit anything more if it's just to see some stuff like
+> > this .
+> 
+> please don't, we need you :(
+> 
+> Rindolf we can't loose packagers like mikala, you really need to follow rules.
+> 
+> If you need more infos about rules please ask we are here to help but don't 
+> touch mikala's packages w/o his authorisation.
+> 
+> just do a mgarepo maintdb get $package    and see who is the maintainer and 
+> ask before commiting.
+
+OK, I'll keep it in mind. I thought the change was harmless because it didn't
+bump the library's libmajor, but apparently the KDE packages require an exact
+version 0.3 of attica's libraries which seems broken to me. In any case, I'll
+check for package maintainership later on and also will always try to install
+the packages first to see if they break anything.
+
+Thanks for the heads' up.
+
+BTW, you should not call me "Rindolf" outside IRC. My name is Shlomi.
+
+Regards,
+
+	Shlomi Fish 
+
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+Rethinking CPAN - http://shlom.in/rethinking-cpan
+
+In the Technion, there are many ways to get from one place to the other, but
+they are all the same length.
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017852.html b/zarb-ml/mageia-dev/2012-August/017852.html new file mode 100644 index 000000000..1be1b9501 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017852.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 1 12:21:20 CEST 2012 +

+
+ +
On Wednesday 01 August 2012 12:00, Shlomi Fish wrote:
+> BTW, you should not call me "Rindolf" outside IRC. My name is Shlomi.
+
+I suspect that many do that because the Mageia systems doesn't show anything by our usernames n changelogs and whatnot.
+Untill that bug is fixed, you should expect them to continue to refer to you by your username.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120801/044e6a40/attachment.asc>
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017853.html b/zarb-ml/mageia-dev/2012-August/017853.html new file mode 100644 index 000000000..18d981cc4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017853.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 1 12:22:16 CEST 2012 +

+
+ +
On Wednesday 01 August 2012 12:21, Johnny A. Solbu wrote:
+> anything by our usernames
+
+That should be "anything but our usernames..."
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120801/41acface/attachment.asc>
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017854.html b/zarb-ml/mageia-dev/2012-August/017854.html new file mode 100644 index 000000000..1535b41ce --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017854.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Sander Lepik + sander.lepik at eesti.ee +
+ Wed Aug 1 12:24:05 CEST 2012 +

+
+ +
01.08.2012 13:00, Shlomi Fish kirjutas:
+> BTW, you should not call me "Rindolf" outside IRC. My name is Shlomi.
+Yet another wiki page i would like to see. Place where brave people 
+could list their email, irc nick + real name. As it's sometimes very 
+hard to find out who is really behind the svn username :/
+Of course everybody would have to list themselves as we don't disclose 
+such info by default but if there would be such a list i would be in it..
+
+--
+Sander
+
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017855.html b/zarb-ml/mageia-dev/2012-August/017855.html new file mode 100644 index 000000000..30202ad27 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017855.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Wed Aug 1 13:26:48 CEST 2012 +

+
+ +
Le 01/08/2012 09:31, Guillaume Rousse a écrit :
+> Le 01/08/2012 08:46, Thierry Vignaud a écrit :
+>> On 1 August 2012 05:29, fwang <buildsystem-daemon at mageia.org> wrote:
+>>> fwang <fwang> 3-21.mga3:
+>>> + Revision: 277136
+>>> - obsolete db5.2 in favour of db5.3
+>>
+>> # urpmi --auto-select --keep -vv --debug
+>> (...)
+>> installed libreoffice-core-3.6.0.1-1.mga3.x86_64 is conflicting
+>> because of unsatisfied libdb-5.2.so()(64bit)
+>> unselecting task-obsolete-3-21.mga3.noarch
+>> A requested package cannot be installed:
+>> task-obsolete-3-21.mga3.noarch (in order to keep
+>> libreoffice-core-3.6.0.1-1.mga3.x86_64)
+>> Continue installation anyway? (Y/n)
+> Whoever had the brilliant idea of forcing package uninstallation just
+> because "they are not supported anymore" deserve a good spanking...
+> Especially when applied to libraries, whereas shipping them in specific
+> versioned subpackage 'libfication' was meant precisely to avoid this issue.
+
+Morevoer, it's quite ridiculous to focus on removing obsoleted package 
+from end users machines, without first cleaning our own infrastructure: 
+db5.2 is still present in the subversion repository, for instance...
+
+So, removing a package from the distribution should imply:
+1) removing it from the subversion repository
+2) removing it from the master package tree (adding obsoletes tag in any 
+package just for this is overkill)
+3) eventually removing it from end user machines, provided this last 
+step bring some added value (which is still unproven)
+
+
+-- 
+BOFH excuse #47:
+
+Complete Transient Lockout
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017856.html b/zarb-ml/mageia-dev/2012-August/017856.html new file mode 100644 index 000000000..49f7edc5c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017856.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ andre999 + andre999mga at laposte.net +
+ Wed Aug 1 14:37:36 CEST 2012 +

+
+ +
Sander Lepik a écrit :
+> 01.08.2012 11:19, Anne Nicolas kirjutas:
+>> Please try to work properly ie asking maintainer before. It takes a 
+>> mail to do it and save lot of work for everybody. This should be 
+>> applied especially by new comers and mentors. If not we will have to 
+>> write some strict rules down which is, imho, too restrictive while 
+>> common sense should be enough to avoid such situation. Rondolf, 
+>> please, try to follow this.
+>>
+>> Cheers
+>>
+> What about wiki page where maintainers can state what they allow on 
+> their packages w/o asking? Like "Updating minor versions is OK", 
+> "Always ask before you touch", "Do whatever you like", etc. So other 
+> packagers can check and don't have to wait for response. Of course 
+> maintainer can add exceptions too.
+>
+> WDYT?
+>
+> -- 
+> Sander
+>
+Excellent idea.
+The maintainer could put comments to specify by specific package or 
+group of packages, as well.
+
+-- 
+André
+
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017857.html b/zarb-ml/mageia-dev/2012-August/017857.html new file mode 100644 index 000000000..7e7e02494 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017857.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] Invitation à se connecter sur LinkedIn + + + + + + + + + +

[Mageia-dev] Invitation à se connecter sur LinkedIn

+ Fabrice Facorat + fabrice.facorat at gmail.com +
+ Wed Aug 1 14:41:32 CEST 2012 +

+
+ +
LinkedIn
+------------
+
+
+
+Mageia,
+
+J'aimerais vous inviter à rejoindre mon réseau professionnel en ligne, sur le site LinkedIn.
+
+Fabrice
+
+Fabrice Facorat
+Sysadmin chez Orange Business Services: Enablers Portal, PNS team
+Région de Nice , France
+
+Veuillez confirmer que vous connaissez Fabrice Facorat :
+https://www.linkedin.com/e/wnk75a-h5cen71o-37/isd/8072999478/E-5G09wb/?hs=false&tok=0NlNUcfPipM5k1
+
+--
+Vous recevez des invitations à vous connecter par e-mail. Cliquez ici si vous ne souhaitez plus recevoir ces e-mails :
+http://www.linkedin.com/e/wnk75a-h5cen71o-37/XuJfPVo1XXuftlZXGqyrld81gvXO0ji0_p/goo/mageia-dev%40mageia%2Eorg/20061/I2721592599_1/?hs=false&tok=0Q_GGgZwypM5k1
+
+(c) 2012 LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA.
+
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120801/11b1287b/attachment-0001.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017858.html b/zarb-ml/mageia-dev/2012-August/017858.html new file mode 100644 index 000000000..f5b798033 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017858.html @@ -0,0 +1,119 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ andre999 + andre999mga at laposte.net +
+ Wed Aug 1 15:00:48 CEST 2012 +

+
+ +
Guillaume Rousse a écrit :
+> Le 01/08/2012 09:31, Guillaume Rousse a écrit :
+>> Le 01/08/2012 08:46, Thierry Vignaud a écrit :
+>>> On 1 August 2012 05:29, fwang <buildsystem-daemon at mageia.org> wrote:
+>>>> fwang <fwang> 3-21.mga3:
+>>>> + Revision: 277136
+>>>> - obsolete db5.2 in favour of db5.3
+>>>
+>>> # urpmi --auto-select --keep -vv --debug
+>>> (...)
+>>> installed libreoffice-core-3.6.0.1-1.mga3.x86_64 is conflicting
+>>> because of unsatisfied libdb-5.2.so()(64bit)
+>>> unselecting task-obsolete-3-21.mga3.noarch
+>>> A requested package cannot be installed:
+>>> task-obsolete-3-21.mga3.noarch (in order to keep
+>>> libreoffice-core-3.6.0.1-1.mga3.x86_64)
+>>> Continue installation anyway? (Y/n)
+>> Whoever had the brilliant idea of forcing package uninstallation just
+>> because "they are not supported anymore" deserve a good spanking...
+>> Especially when applied to libraries, whereas shipping them in specific
+>> versioned subpackage 'libfication' was meant precisely to avoid this 
+>> issue.
+>
+> Morevoer, it's quite ridiculous to focus on removing obsoleted package 
+> from end users machines, without first cleaning our own 
+> infrastructure: db5.2 is still present in the subversion repository, 
+> for instance...
+>
+> So, removing a package from the distribution should imply:
+> 1) removing it from the subversion repository
+> 2) removing it from the master package tree (adding obsoletes tag in 
+> any package just for this is overkill)
+> 3) eventually removing it from end user machines, provided this last 
+> step bring some added value (which is still unproven)
+>
++1
+This last point reminds me of the obsoletes of openoffice put in the 
+libreoffice spec, when there was no real conflicts and there were some 
+differences.  So a regression in libreoffice required me to install 
+upstream libreoffice so I could install openoffice alongside, to work 
+around the regressions when I needed to.
+So definitely no added value.
+These obsoletes are still there.
+
+-- 
+André
+
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017859.html b/zarb-ml/mageia-dev/2012-August/017859.html new file mode 100644 index 000000000..93b29dace --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017859.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Olivier Blin + mageia at blino.org +
+ Wed Aug 1 15:19:33 CEST 2012 +

+
+ +
Guillaume Rousse <guillomovitch at gmail.com> writes:
+
+> Morevoer, it's quite ridiculous to focus on removing obsoleted package
+> from end users machines, without first cleaning our own
+> infrastructure: db5.2 is still present in the subversion repository,
+> for instance...
+
+IIRC, the obsoleted package are supposed to be removed on upload by youri.
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017860.html b/zarb-ml/mageia-dev/2012-August/017860.html new file mode 100644 index 000000000..668c39248 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017860.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Wed Aug 1 15:33:49 CEST 2012 +

+
+ +
Le 01/08/2012 15:19, Olivier Blin a écrit :
+> Guillaume Rousse <guillomovitch at gmail.com> writes:
+>
+>> Morevoer, it's quite ridiculous to focus on removing obsoleted package
+>> from end users machines, without first cleaning our own
+>> infrastructure: db5.2 is still present in the subversion repository,
+>> for instance...
+>
+> IIRC, the obsoleted package are supposed to be removed on upload by youri.
+They are only removed from the master package tree (task 2 in my list).
+
+What was originally supposed to be a side-effect of adding an obsoletes 
+tag to a package (if foo is supposed to replace bar on end users 
+machines, there is no reason to let bar exist on the mirror, and this 
+will save an rm -f command to some sysadmin) is now largely perceived as 
+the dedicated way to manage mirror content (in order to remove bar from 
+mirrors, we have to obsoletes it somewhere). Which is a dangereous 
+practice, as illustrated this morning.
+
+-- 
+BOFH excuse #391:
+
+We already sent around a notice about that.
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017861.html b/zarb-ml/mageia-dev/2012-August/017861.html new file mode 100644 index 000000000..03fb31da2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017861.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Wed Aug 1 15:34:51 CEST 2012 +

+
+ +
On Wed, 1 Aug 2012, andre999 wrote:
+
+> This last point reminds me of the obsoletes of openoffice put in the 
+> libreoffice spec, when there was no real conflicts and there were some 
+> differences.  So a regression in libreoffice required me to install upstream 
+> libreoffice so I could install openoffice alongside, to work around the 
+> regressions when I needed to.
+> So definitely no added value.
+> These obsoletes are still there.
+
+Within mageia, libreoffice packages are supposed to replace old openoffice 
+packages, so obsoletes are needed. The solution to the problem you 
+describe is to make the obsoletes versioned so they only replace those old 
+mga/mdv/mdk openoffice packages, not new ones.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017862.html b/zarb-ml/mageia-dev/2012-August/017862.html new file mode 100644 index 000000000..ebfb3adc0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017862.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Wed Aug 1 15:43:43 CEST 2012 +

+
+ +
Le 01/08/2012 15:34, Christiaan Welvaart a écrit :
+> On Wed, 1 Aug 2012, andre999 wrote:
+>
+>> This last point reminds me of the obsoletes of openoffice put in the
+>> libreoffice spec, when there was no real conflicts and there were some
+>> differences.  So a regression in libreoffice required me to install
+>> upstream libreoffice so I could install openoffice alongside, to work
+>> around the regressions when I needed to.
+>> So definitely no added value.
+>> These obsoletes are still there.
+>
+> Within mageia, libreoffice packages are supposed to replace old
+> openoffice packages, so obsoletes are needed.
+Unless they are effective file conflict, and libreoffice can't be 
+installed simultaneously, I see no actual reason to force its removal.
+
+-- 
+BOFH excuse #195:
+
+We only support a 28000 bps connection.
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017863.html b/zarb-ml/mageia-dev/2012-August/017863.html new file mode 100644 index 000000000..02bdadd52 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017863.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 1 16:17:53 CEST 2012 +

+
+ +
On 1 August 2012 15:43, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>> Within mageia, libreoffice packages are supposed to replace old
+>> openoffice packages, so obsoletes are needed.
+>
+> Unless they are effective file conflict, and libreoffice can't be installed
+> simultaneously, I see no actual reason to force its removal.
+
+They do conflicts.
+We do not maintain it anymore.
+We do no want to have bugs reports about package Y on mgaX about
+packages "that were obviously build by mga" (yes but for mgaX-10).
+
+In that case, it's even worse, as it would have been a mdv package on mga
+after mdv->mga upgrade
+
+And anyway this is a different case than obsoleting a library (though I do
+understand Funda's move about libdb and his intents)
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017864.html b/zarb-ml/mageia-dev/2012-August/017864.html new file mode 100644 index 000000000..2867919da --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017864.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Wed Aug 1 16:29:53 CEST 2012 +

+
+ +
* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> On 1 August 2012 15:43, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+> >> Within mageia, libreoffice packages are supposed to replace old
+> >> openoffice packages, so obsoletes are needed.
+> >
+> > Unless they are effective file conflict, and libreoffice can't be installed
+> > simultaneously, I see no actual reason to force its removal.
+> 
+> They do conflicts.
+> We do not maintain it anymore.
+> We do no want to have bugs reports about package Y on mgaX about
+> packages "that were obviously build by mga" (yes but for mgaX-10).
+
+Yes but:
+- it's up to packagers to point the package is not supported anymore (as
+  it is not on mirrors)
+- the obsolete should be in the package that replace the previous one
+  (the word 'replace' is important)
+- it is really a bad practice to choose for users what is good or not.
+
+Moreover there is a really bad effect: updating a system can cause to a
+package to removed because task-obsolete is installed.
+
+I am in favor to drop this package.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120801/376885e2/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017865.html b/zarb-ml/mageia-dev/2012-August/017865.html new file mode 100644 index 000000000..70fd8e3b6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017865.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 1 16:38:00 CEST 2012 +

+
+ +
On 1 August 2012 16:29, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+>> >> Within mageia, libreoffice packages are supposed to replace old
+>> >> openoffice packages, so obsoletes are needed.
+>> >
+>> > Unless they are effective file conflict, and libreoffice can't be installed
+>> > simultaneously, I see no actual reason to force its removal.
+>>
+>> They do conflicts.
+>> We do not maintain it anymore.
+>> We do no want to have bugs reports about package Y on mgaX about
+>> packages "that were obviously build by mga" (yes but for mgaX-10).
+>
+> Yes but:
+> - it's up to packagers to point the package is not supported anymore (as
+>   it is not on mirrors)
+> - the obsolete should be in the package that replace the previous one
+>   (the word 'replace' is important)
+
+Agreed.
+
+> - it is really a bad practice to choose for users what is good or not.
+
+Well, in the libreoffice case, this was well documented (and anyway, OO wasn't
+even supported upstream for ~ 2 years)
+For the db case, it's about a older version of a low level library that never
+went into a released version.
+The end user doesn't care whether it's apps are builded against libdb-5.2,
+or 5.3 (even more since 5.2 was only available in cauldron)
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017866.html b/zarb-ml/mageia-dev/2012-August/017866.html new file mode 100644 index 000000000..1e193bed5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017866.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Scott Chevalley + avalon at osguru.org +
+ Wed Aug 1 17:00:17 CEST 2012 +

+
+ +
I was just reading about some package issues, and I notice that urpmi
+--auto-select is asking a lot of questions that it normally wouldn't ask.  I've
+tried running it with --keep and it seems to be having problems with some of the
+packages that were mentioned recently on the list:
+
+# urpmi --auto-select --keep
+Some requested packages cannot be installed:
+kcm_cddb-handbook-4.9.0-1.mga3.x86_64 (in order to keep
+kde4-audiocd-handbook-4.8.97-1.mga3.noarch)
+kdebase4-runtime-4.9.0-1.mga3.x86_64 (due to conflicts with
+lib64attica0-0.4.0-1.mga3.x86_64, trying to promote libattica.so.0.3()(64bit))
+lib64attica0-0.4.0-1.mga3.x86_64 (in order to keep
+plasma-dataengine-ocs-4.8.97-2.mga3.x86_64)
+task-obsolete-3-21.mga3.noarch (in order to keep lib64ebackend2-3.4.3-1.mga3.x86_64)
+Continue installation anyway? (Y/n) y
+
+
+If I continue will it break KDE or other stuff?
+
+Just thought I'd check.
+
+Thanks!
+Scott
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017867.html b/zarb-ml/mageia-dev/2012-August/017867.html new file mode 100644 index 000000000..e8a3ee869 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017867.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Wed Aug 1 17:06:59 CEST 2012 +

+
+ +
Le mercredi 1 août 2012 11:00:17 Scott Chevalley a écrit :
+> I was just reading about some package issues, and I notice that urpmi
+> --auto-select is asking a lot of questions that it normally wouldn't ask. 
+> I've tried running it with --keep and it seems to be having problems with
+> some of the packages that were mentioned recently on the list:
+> 
+> # urpmi --auto-select --keep
+> Some requested packages cannot be installed:
+> kcm_cddb-handbook-4.9.0-1.mga3.x86_64 (in order to keep
+> kde4-audiocd-handbook-4.8.97-1.mga3.noarch)
+> kdebase4-runtime-4.9.0-1.mga3.x86_64 (due to conflicts with
+> lib64attica0-0.4.0-1.mga3.x86_64, trying to promote
+> libattica.so.0.3()(64bit)) lib64attica0-0.4.0-1.mga3.x86_64 (in order to
+> keep
+> plasma-dataengine-ocs-4.8.97-2.mga3.x86_64)
+> task-obsolete-3-21.mga3.noarch (in order to keep
+> lib64ebackend2-3.4.3-1.mga3.x86_64) Continue installation anyway? (Y/n) y
+> 
+> 
+> If I continue will it break KDE or other stuff?
+> 
+> Just thought I'd check.
+> 
+> Thanks!
+> Scott
+
+i could say that this is what happens when people push KDE when not knowing 
+the real number of packages to push, etc etc.
+
+ I will look what is missing.
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017868.html b/zarb-ml/mageia-dev/2012-August/017868.html new file mode 100644 index 000000000..347b0ed58 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017868.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] "svn copy" issiues - adding mdv2010.1/2 packages to mga1 and mga2 from Cauldron + + + + + + + + + +

[Mageia-dev] "svn copy" issiues - adding mdv2010.1/2 packages to mga1 and mga2 from Cauldron

+ Damien Lallement + mageia at damsweb.net +
+ Wed Aug 1 16:41:10 CEST 2012 +

+
+ +
Le 01/08/2012 06:37, Johnny A. Solbu a écrit :
+> I'm about to copy a package (etc-update) from cauldron to 1/updates, as per the instructions on the wiki. (See bug 6178)
+> Does anyone have a suggestion on what to write as the commit message? "importing blah" hardly seems correct when the package alreaddy exist in Cauldron but not in mga1 and mga2.
+
+When I import this kind of package, I say:
+"Create branch for mageia 1 update as requested in mga#%{BUG}"
+
+> [...]
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017869.html b/zarb-ml/mageia-dev/2012-August/017869.html new file mode 100644 index 000000000..cc5c94100 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017869.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Wed Aug 1 17:28:35 CEST 2012 +

+
+ +
Le mercredi 1 août 2012 17:06:59 Nicolas Lécureuil a écrit :
+> Le mercredi 1 août 2012 11:00:17 Scott Chevalley a écrit :
+> > I was just reading about some package issues, and I notice that urpmi
+> > --auto-select is asking a lot of questions that it normally wouldn't ask.
+> > I've tried running it with --keep and it seems to be having problems with
+> > some of the packages that were mentioned recently on the list:
+> > 
+> > # urpmi --auto-select --keep
+> > Some requested packages cannot be installed:
+> > kcm_cddb-handbook-4.9.0-1.mga3.x86_64 (in order to keep
+> > kde4-audiocd-handbook-4.8.97-1.mga3.noarch)
+> > kdebase4-runtime-4.9.0-1.mga3.x86_64 (due to conflicts with
+> > lib64attica0-0.4.0-1.mga3.x86_64, trying to promote
+> > libattica.so.0.3()(64bit)) lib64attica0-0.4.0-1.mga3.x86_64 (in order to
+> > keep
+> > plasma-dataengine-ocs-4.8.97-2.mga3.x86_64)
+> > task-obsolete-3-21.mga3.noarch (in order to keep
+> > lib64ebackend2-3.4.3-1.mga3.x86_64) Continue installation anyway? (Y/n) y
+> > 
+> > 
+> > If I continue will it break KDE or other stuff?
+> > 
+> > Just thought I'd check.
+> > 
+> > Thanks!
+> > Scott
+> 
+> i could say that this is what happens when people push KDE when not knowing
+> the real number of packages to push, etc etc.
+> 
+>  I will look what is missing.
+
+i though more packages were pushed :( 
+i pushed all the remaining w/o our upload script, i will see if all builds 
+well.
+
+
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017870.html b/zarb-ml/mageia-dev/2012-August/017870.html new file mode 100644 index 000000000..e8a2c66ff --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017870.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] "svn copy" issiues - adding mdv2010.1/2 packages to mga1 and mga2 from Cauldron + + + + + + + + + +

[Mageia-dev] "svn copy" issiues - adding mdv2010.1/2 packages to mga1 and mga2 from Cauldron

+ Jani Välimaa + jani.valimaa at gmail.com +
+ Wed Aug 1 17:31:54 CEST 2012 +

+
+ +
On 01.08.2012 17:41, Damien Lallement wrote:
+> Le 01/08/2012 06:37, Johnny A. Solbu a écrit :
+>> I'm about to copy a package (etc-update) from cauldron to 1/updates,
+>> as per the instructions on the wiki. (See bug 6178)
+>> Does anyone have a suggestion on what to write as the commit message?
+>> "importing blah" hardly seems correct when the package alreaddy exist
+>> in Cauldron but not in mga1 and mga2.
+> 
+> When I import this kind of package, I say:
+> "Create branch for mageia 1 update as requested in mga#%{BUG}"
+> 
+
+Also note that this msg ends to a pkg %changelog too unless SILENT is used.
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017871.html b/zarb-ml/mageia-dev/2012-August/017871.html new file mode 100644 index 000000000..5596b1e1c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017871.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3

+ Sander Lepik + sander.lepik at eesti.ee +
+ Wed Aug 1 17:42:18 CEST 2012 +

+
+ +
01.08.2012 18:39, neoclust kirjutas:
+> Name        : kmplot                       Relocations: (not relocatable)
+> Version     : 4.9.0                             Vendor: Mageia.Org
+> Release     : 1.mga3                        Build Date: Wed Aug  1 17:34:45 2012
+> [...]
+>
+> mikala <mikala> 4.9.0-1.mga3:
+> + Revision: 277048
+> - Silent: Fix Source URL
+Hmm, I think SILENT should be used :)
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017872.html b/zarb-ml/mageia-dev/2012-August/017872.html new file mode 100644 index 000000000..937a7abe9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017872.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Wed Aug 1 17:45:15 CEST 2012 +

+
+ +
Le mercredi 1 août 2012 18:42:18 Sander Lepik a écrit :
+> 01.08.2012 18:39, neoclust kirjutas:
+> > Name        : kmplot                       Relocations: (not relocatable)
+> > Version     : 4.9.0                             Vendor: Mageia.Org
+> > Release     : 1.mga3                        Build Date: Wed Aug  1
+> > 17:34:45 2012 [...]
+> > 
+> > mikala <mikala> 4.9.0-1.mga3:
+> > + Revision: 277048
+> > - Silent: Fix Source URL
+> 
+> Hmm, I think SILENT should be used :)
+> 
+> --
+> Sander
+
+or maybe silent SILENT SiLeNt SIlent, ...  should be understood by the BS :)
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017873.html b/zarb-ml/mageia-dev/2012-August/017873.html new file mode 100644 index 000000000..d21d59df9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017873.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3

+ Sander Lepik + sander.lepik at eesti.ee +
+ Wed Aug 1 17:50:23 CEST 2012 +

+
+ +
01.08.2012 18:45, Nicolas Lécureuil kirjutas:
+> Le mercredi 1 août 2012 18:42:18 Sander Lepik a écrit :
+>> Hmm, I think SILENT should be used :)
+>>
+>> --
+>> Sander
+> or maybe silent SILENT SiLeNt SIlent, ...  should be understood by the BS :)
+This might kill some needed comments. Or not?
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017874.html b/zarb-ml/mageia-dev/2012-August/017874.html new file mode 100644 index 000000000..6fedf4b52 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017874.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kmplot-4.9.0-1.mga3

+ Jani Välimaa + jani.valimaa at gmail.com +
+ Wed Aug 1 17:54:13 CEST 2012 +

+
+ +
On 01.08.2012 18:50, Sander Lepik wrote:
+> 01.08.2012 18:45, Nicolas Lécureuil kirjutas:
+>> Le mercredi 1 août 2012 18:42:18 Sander Lepik a écrit :
+>>> Hmm, I think SILENT should be used :)
+>>>
+>>> --
+>>> Sander
+>> or maybe silent SILENT SiLeNt SIlent, ...  should be understood by the BS :)
+> This might kill some needed comments. Or not?
+> 
+
+IIUC only SILENT with caps works.
+
+If it's the first word in the first line, the whole commit msg is
+silenced and if it's in somewhere else, only the corresponding line is
+silenced.
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017875.html b/zarb-ml/mageia-dev/2012-August/017875.html new file mode 100644 index 000000000..fa2d0a597 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017875.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ John Balcaen + mikala at mageia.org +
+ Wed Aug 1 18:37:56 CEST 2012 +

+
+ +
2012/7/31 Balcaen John <mikala at mageia.org>:
+[...]
+> Oh damn that !!!
+> kde 4.9.0 is not supposed to be released & now because a padawan without a
+> commit right send a patch, his mentor feels obligate to push the package
+> *without* checking the side effect of this change (yeah it's a update & we're
+> late let's push it ) of course we could have stay only with kdelibs 4.9.0 but
+> now i noticed that fwang is pushing the whole kde stack especially when we're
+> not sure that some kde package are not going to be respun ....
+> damn that !
+For the record kdelibs tarball has been respun .... funny...
+
+
+-- 
+Balcaen John
+Jabber-id: mikala at jabber.littleboboy.net
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017876.html b/zarb-ml/mageia-dev/2012-August/017876.html new file mode 100644 index 000000000..c30dfce9f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017876.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ John Balcaen + mikala at mageia.org +
+ Wed Aug 1 18:48:15 CEST 2012 +

+
+ +
2012/8/1 Nicolas Lécureuil <nicolas.lecureuil at free.fr>:
+> i though more packages were pushed :(
+> i pushed all the remaining w/o our upload script, i will see if all builds
+> well.
+Build has no reason (except rpmlint issue) to fail since it was tested
+before committing.
+Regarding the conflicts for handbooks, it's a normal issue since the
+conflict was added on purpose.
+For libattica issue, it's a "let's push an update without testing it
+before" issue, but since most of kde should has been pushed/built
+against the new attica it should be safe.
+
+
+
+-- 
+Balcaen John
+Jabber-id: mikala at jabber.littleboboy.net
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017877.html b/zarb-ml/mageia-dev/2012-August/017877.html new file mode 100644 index 000000000..5fdf01594 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017877.html @@ -0,0 +1,261 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 1 21:31:15 CEST 2012 +

+
+ +
'Twas brillig, and Shlomi Fish at 01/08/12 11:00 did gyre and gimble:
+> On Wed, 01 Aug 2012 03:44:32 +0200
+> Nicolas Lécureuil <nicolas.lecureuil at free.fr> wrote:
+> 
+>> Le mardi 31 juillet 2012 22:20:45 Balcaen John a écrit :
+>>> Le mardi 31 juillet 2012 18:42:00 tv a écrit :
+>>>> Name        : kdelibs4                     Relocations: (not relocatable)
+>>>> Version     : 4.9.0                             Vendor: Mageia.Org
+>>>> Release     : 2.mga3                        Build Date: Tue Jul 31
+>>>> 18:15:54
+>>>> 2012 Install Date: (not installed)               Build Host:
+>>>> ecosse.mageia.org Group       : Graphical desktop/KDE         Source RPM:
+>>>> (none)
+>>>> Size        : 11884847                         License: GPLv2 and LGPLv2
+>>>> and GFDL and BSD and QPL and Artistic Signature   : (none)
+>>>> Packager    : tv <tv>
+>>>> URL         : http://www.kde.org
+>>>> Summary     : K Desktop Environment - Libraries
+>>>> Description :
+>>>> Libraries for the K Desktop Environment.
+>>>>
+>>>> tv <tv> 2:4.9.0-2.mga3:
+>>>> + Revision: 276808
+>>>> - rebuild for new libattica
+>>>>
+>>>>   + mikala <mikala>
+>>>>   
+>>>>     - Silent: Fix Source URL
+>>>>     - Update tarball to KDE 4.9.0
+>>>
+>>> Oh damn that !!!
+>>> kde 4.9.0 is not supposed to be released & now because a padawan without a
+>>> commit right send a patch, his mentor feels obligate to push the package
+>>> *without* checking the side effect of this change (yeah it's a update &
+>>> we're late let's push it ) of course we could have stay only with kdelibs
+>>> 4.9.0 but now i noticed that fwang is pushing the whole kde stack
+>>> especially when we're not sure that some kde package are not going to be
+>>> respun ....
+>>> damn that !
+>>>
+>>> I guess i'll won't commit anything more if it's just to see some stuff like
+>>> this .
+>>
+>> please don't, we need you :(
+>>
+>> Rindolf we can't loose packagers like mikala, you really need to follow rules.
+>>
+>> If you need more infos about rules please ask we are here to help but don't 
+>> touch mikala's packages w/o his authorisation.
+>>
+>> just do a mgarepo maintdb get $package    and see who is the maintainer and 
+>> ask before commiting.
+> 
+> OK, I'll keep it in mind. I thought the change was harmless because it didn't
+> bump the library's libmajor, but apparently the KDE packages require an exact
+> version 0.3 of attica's libraries which seems broken to me.
+
+I have to agree here that something is "funny" in the libattica package
+which ultimately helped to contribute to this issue.
+
+e.g. on my system before update (tho' with similar results after):
+
+[colin at jimmy ~]$ rpm -q --provides lib64attica0
+libattica.so.0.3()(64bit)
+lib64attica0 = 0.3.0-1.mga2
+lib64attica0(x86-64) = 0.3.0-1.mga2
+[colin at jimmy ~]$ rpm -ql lib64attica0
+/usr/lib64/libattica.so.0.3
+/usr/lib64/libattica.so.0.3.0
+
+IMO this *should* be:
+
+[colin at jimmy ~]$ rpm -q --provides lib64attica0
+libattica.so.0()(64bit)
+lib64attica0 = 0.3.0-1.mga2
+lib64attica0(x86-64) = 0.3.0-1.mga2
+[colin at jimmy ~]$ rpm -ql lib64attica0
+/usr/lib64/libattica.so.0
+/usr/lib64/libattica.so.0.3.0
+
+
+So I can see how this mistake was made and TBH I could have made the
+same mistake myself (with the caveat that I likely would not have bumped
+the version of someone else's package with out confirming first and that
+it should have been obvious from testing and installing the build)
+
+But either way this seems like an issue to fix properly (possibly with
+an upstream fix or some modification to the library policy when the
+minor version is "presented" like this).
+
+
+FWIW there are some other examples I can find:
+
+This one just looks "odd" generally:
+[colin at jimmy ~]$ rpm -qf /usr/lib64/libxenctrl.so.4.0
+lib64xen3.0-4.1.2-4.mga2
+[colin at jimmy ~]$ rpm -q --provides lib64xen3.0
+libblktap.so.3.0()(64bit)
+libblktapctl.so.1.0()(64bit)
+libflask.so.1.0()(64bit)
+libfsimage.so.1.0()(64bit)
+libvhd.so.1.0()(64bit)
+libxenctrl.so.4.0()(64bit)
+libxenguest.so.4.0()(64bit)
+libxenlight.so.1.0()(64bit)
+libxenstore.so.3.0()(64bit)
+libxlutil.so.1.0()(64bit)
+lib64xen3.0 = 4.1.2-4.mga2
+lib64xen3.0(x86-64) = 4.1.2-4.mga2
+
+
+This one is even more strange as the "major" appears to be the
+concatenation of the major and minor:
+
+
+[colin at jimmy ~]$ rpm -q --provides lib64ice33
+libFreeze.so.33()(64bit)
+libGlacier2.so.33()(64bit)
+libIce.so.33()(64bit)
+libIceBox.so.33()(64bit)
+libIceGrid.so.33()(64bit)
+libIcePatch2.so.33()(64bit)
+libIceSSL.so.33()(64bit)
+libIceStorm.so.33()(64bit)
+libIceStormService.so.33()(64bit)
+libIceUtil.so.33()(64bit)
+libIceXML.so.33()(64bit)
+libSlice.so.33()(64bit)
+lib64ice33 = 3.3.1-5.mga2
+lib64ice33(x86-64) = 3.3.1-5.mga2
+[colin at jimmy ~]$ rpm -ql lib64ice33
+/usr/lib64/libFreeze.so.3.3.1
+/usr/lib64/libFreeze.so.33
+/usr/lib64/libGlacier2.so.3.3.1
+/usr/lib64/libGlacier2.so.33
+/usr/lib64/libIce.so.3.3.1
+/usr/lib64/libIce.so.33
+/usr/lib64/libIceBox.so.3.3.1
+/usr/lib64/libIceBox.so.33
+/usr/lib64/libIceGrid.so.3.3.1
+/usr/lib64/libIceGrid.so.33
+/usr/lib64/libIcePatch2.so.3.3.1
+/usr/lib64/libIcePatch2.so.33
+/usr/lib64/libIceSSL.so.3.3.1
+/usr/lib64/libIceSSL.so.33
+/usr/lib64/libIceStorm.so.3.3.1
+/usr/lib64/libIceStorm.so.33
+/usr/lib64/libIceStormService.so.3.3.1
+/usr/lib64/libIceStormService.so.33
+/usr/lib64/libIceUtil.so.3.3.1
+/usr/lib64/libIceUtil.so.33
+/usr/lib64/libIceXML.so.3.3.1
+/usr/lib64/libIceXML.so.33
+/usr/lib64/libSlice.so.3.3.1
+/usr/lib64/libSlice.so.33
+
+
+And finally here is one that provides symlinks at both levels of major:
+
+[colin at jimmy ~]$ rpm -q --provides lib64qtxml4
+qtxmllib = 4:4.8.2
+lib64qtxml4 = 4:4.8.2-4.mga3
+lib64qtxml4(x86-64) = 4:4.8.2-4.mga3
+libQtXml.so.4()(64bit)
+[colin at jimmy ~]$ rpm -ql lib64qtxml4
+/usr/lib64/libQtXml.so.4
+/usr/lib64/libQtXml.so.4.8
+/usr/lib64/libQtXml.so.4.8.2
+
+Not an exhaustive list, just some random looks at my /usr/lib64 folder.
+
+
+So can someone familiar with the project have a bit of a think about it
+and maybe see if they can fix it properly in a future proof way?
+
+> BTW, you should not call me "Rindolf" outside IRC. My name is Shlomi.
+
+Provided it doesn't offend you too much, most of us tend to chop and
+change between real names and IRC nicks even on mailing lists. I'll
+quite often refer to ennael, tmb, blino or tv etc. In some cases it's
+because I can't remember the exact spelling of names and sometimes it's
+pure laziness! While I'll try to remember your preference I hope you
+don't take active office at it (otherwise it's a particularly bad choice
+of IRC nicks :p).
+
+FWIW I still get surprised when people call me "Col" rather than "Colin"
+even tho' that's how I sign pretty much all my emails - same deal there
+I suppose :)
+
+Col(in)[g]
+
+:p
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017878.html b/zarb-ml/mageia-dev/2012-August/017878.html new file mode 100644 index 000000000..9d4da7167 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017878.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 1 21:33:39 CEST 2012 +

+
+ +
'Twas brillig, and John Balcaen at 01/08/12 17:48 did gyre and gimble:
+> 2012/8/1 Nicolas Lécureuil <nicolas.lecureuil at free.fr>:
+>> i though more packages were pushed :(
+>> i pushed all the remaining w/o our upload script, i will see if all builds
+>> well.
+> Build has no reason (except rpmlint issue) to fail since it was tested
+> before committing.
+> Regarding the conflicts for handbooks, it's a normal issue since the
+> conflict was added on purpose.
+> For libattica issue, it's a "let's push an update without testing it
+> before" issue, but since most of kde should has been pushed/built
+> against the new attica it should be safe.
+
+Just submitted kdeplasma-addons which still needed the old attica.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017879.html b/zarb-ml/mageia-dev/2012-August/017879.html new file mode 100644 index 000000000..03b2b4a11 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017879.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] wine [263611] new version 1.5.7 + + + + + + + + + +

[Mageia-dev] wine [263611] new version 1.5.7

+ Anssi Hannula + anssi at mageia.org +
+ Wed Aug 1 21:50:19 CEST 2012 +

+
+ +
27.07.2012 19:22, Frank Griffin kirjoitti:
+> On 07/27/2012 12:20 PM, Anssi Hannula wrote:
+>> 27.07.2012 19:18, Frank Griffin kirjoitti:
+>>>
+>>> Please also address the issue of a similar initial Wine popup
+>>> complaining that it can't find a usable mono.  The current mono is
+>>> installed on my system, but apparently has the same problem being
+>>> recognized as gecko.
+>> Thanks, will look into it. (I guess I had installed it at some point and
+>> forgot it)
+>>
+> The mono prompts are relatively recent, probably introduced in the last 
+> couple of versions.  Thanks.
+
+Submitted now.
+
+For the record, it'd be nice if someone volunteered to maintain our
+mingw cross-toolchain (~5 packages, ~directly from Fedora).
+
+For now I just bundled a minimal version in the wine-mono package (like
+with wine-gecko), but it isn't really very nice, especially considering
+that two packages need it now...
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017880.html b/zarb-ml/mageia-dev/2012-August/017880.html new file mode 100644 index 000000000..1c9085b04 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017880.html @@ -0,0 +1,117 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Charles A Edwards + CAE at eslrahc.com +
+ Wed Aug 1 22:04:38 CEST 2012 +

+
+ +
On Wed, 01 Aug 2012 17:28:35 +0200
+Nicolas Lécureuil wrote:
+
+> > > plasma-dataengine-ocs-4.8.97-2.mga3.x86_64)
+> > > task-obsolete-3-21.mga3.noarch (in order to keep
+> > > lib64ebackend2-3.4.3-1.mga3.x86_64) Continue installation anyway?
+> > > (Y/n) y
+> > > 
+> > > 
+> > > If I continue will it break KDE or other stuff?
+> > > 
+> > > Just thought I'd check.
+> > > 
+> > > Thanks!
+> > > Scott  
+> > 
+> > i could say that this is what happens when people push KDE when not
+> > knowing the real number of packages to push, etc etc.
+> > 
+> >  I will look what is missing.  
+> 
+> i though more packages were pushed :( 
+> i pushed all the remaining w/o our upload script, i will see if all
+> builds well.
+
+I saw the same yesterday but knew what was causing it (kde) so
+simply added --keep to the update script.
+
+Just ran --auto-update today and all updated normally.
+
+
+    Charles
+
+-- 
+[Peter's new car has an electronic navigator with a Yakov Smirnoff
+mode] Yakov Smirnoff Voice:  Turn left at fork in road. In Soviet
+Russia, road forks you. ----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.0-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120801/58756a12/attachment.asc>
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017881.html b/zarb-ml/mageia-dev/2012-August/017881.html new file mode 100644 index 000000000..fe20a78d4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017881.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release db53-5.3.21-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release db53-5.3.21-1.mga3

+ Charles A Edwards + CAE at eslrahc.com +
+ Wed Aug 1 22:14:02 CEST 2012 +

+
+ +
On Tue, 31 Jul 2012 16:14:46 +0800
+Funda Wang wrote:
+
+> > Conflict should now be
+> >
+> > Conflicts:      db5_nss-devel < %{__soversion}  
+> Which will become useless untill all packages be built upon db 5.3.
+> Then we will have only db 4.8 and db 5.3 for mga3.
+
+
+Then the same issue will occur unless the next release is
+db6.x
+
+db5_nss-devel=5.x and every subsequent release (5.4, 5.5, 5.6, etc.)  
+will conflict with the previous release.
+
+
+    Charles
+
+-- 
+BE ALOOF!  (There has been a recent population explosion of lerts.)
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.0-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120801/59d357c6/attachment-0001.asc>
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017882.html b/zarb-ml/mageia-dev/2012-August/017882.html new file mode 100644 index 000000000..597c2592d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017882.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Thu Aug 2 00:09:40 CEST 2012 +

+
+ +
On Wed, 1 Aug 2012, Colin Guthrie wrote:
+
+> I have to agree here that something is "funny" in the libattica package
+> which ultimately helped to contribute to this issue.
+>
+> e.g. on my system before update (tho' with similar results after):
+>
+> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+> libattica.so.0.3()(64bit)
+> lib64attica0 = 0.3.0-1.mga2
+> lib64attica0(x86-64) = 0.3.0-1.mga2
+> [colin at jimmy ~]$ rpm -ql lib64attica0
+> /usr/lib64/libattica.so.0.3
+> /usr/lib64/libattica.so.0.3.0
+
+> So I can see how this mistake was made and TBH I could have made the
+> same mistake myself (with the caveat that I likely would not have bumped
+> the version of someone else's package with out confirming first and that
+> it should have been obvious from testing and installing the build)
+>
+> But either way this seems like an issue to fix properly (possibly with
+> an upstream fix or some modification to the library policy when the
+> minor version is "presented" like this).
+
+Good catch! Of course it's never the library policy that's wrong. The 
+library major version is apparently 0.4 so the correct package name is
+    lib64attica0.3  for the previous one
+    lib64attica0.4  for the current one
+
+... in the specfile:   %define attica_major 0.4
+
+Can the maintainer of this package please fix this?
+
+To find the version to use, look up the 'soname' of the library. I use:
+   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+=>
+...                    Library soname: [libattica.so.0.4]
+
+What follows ".so." is the major version of the library.
+
+
+     Christiaan
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017883.html b/zarb-ml/mageia-dev/2012-August/017883.html new file mode 100644 index 000000000..7e3ea0902 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017883.html @@ -0,0 +1,63 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3

+ John Balcaen + mikala at mageia.org +
+ Thu Aug 2 00:28:39 CEST 2012 +

+
+ +
The major is explicitly set to 0 by upstream while the minor is set to 4.
+It's of course possible to change the library name to also match the minor(
+it was part of my idea but I guess someone else is going to take care of
+this)
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120801/b60d4843/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017884.html b/zarb-ml/mageia-dev/2012-August/017884.html new file mode 100644 index 000000000..525282b5c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017884.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] %_libexecdir - Re: [5228] revert some duplicated manbo stuff (all identical to default but + + + + + + + + + +

[Mageia-dev] %_libexecdir - Re: [5228] revert some duplicated manbo stuff (all identical to default but

+ Olivier Blin + mageia at blino.org +
+ Thu Aug 2 00:34:17 CEST 2012 +

+
+ +
Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+
+> On 31 July 2012 16:32, Olivier Blin <mageia at blino.org> wrote:
+>>>> The question is: should we enable minidebuginfo by default?
+>>>> This adds 1-3% to each package but it makes us have usefufull traces by default
+>>>> (at least with function names)
+>>>> Not as good as having debug packages installed by default, but still better.
+>>>> This is enabled in FC18.
+>>>>
+>>> Correction: like FC, we only keep compressed symbol list, not line numbers.
+>>> So overhead is 0.5% for the whole /usr according to RH.
+
+[...]
+
+> as those sections are already compressed, I would say the overhead
+> would be slight bigger,
+> maybe 1% instead of 0.5%
+>
+> I suggests we go with it.
+> If it proves too big, we can disable it globally and enable it on a
+> per package case
+> (eg: glibc/rpm/perl-URPM/perl/glib/gtk/pango/cairo/libx11/perl-Gtk2/perl-Glib/kde*)
+
+Looks good, go for it :)
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017885.html b/zarb-ml/mageia-dev/2012-August/017885.html new file mode 100644 index 000000000..e566044dd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017885.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] [RFC] drop "rpm -bX" aliases + + + + + + + + + +

[Mageia-dev] [RFC] drop "rpm -bX" aliases

+ Olivier Blin + mageia at blino.org +
+ Thu Aug 2 00:35:12 CEST 2012 +

+
+ +
Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+
+> Hi
+>
+> For a _very loooonng time_, "rpm -bX" doesn't work anymore, one must
+> call "rpmbuild -bX" instead.
+> This is like this on every other distro.
+> However, for a very long time, we provides alias for "rpm -bX" that
+> call rpmb_deprecated,
+> which prints '"rpm -b" is deprecated, use "rpmbuild -b"' and calls rpmbuild
+>
+> I suggest it's time to drop these aliases and this wrapper.
+>
+> WDYT?
+
+Yep, it's time to drop this, even if it might be a bit painful to get
+along at first...
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017886.html b/zarb-ml/mageia-dev/2012-August/017886.html new file mode 100644 index 000000000..caa36c4ee --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017886.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Aug 2 04:45:58 CEST 2012 +

+
+ +
On 08/01/2012 11:06 AM, Nicolas Lécureuil wrote:
+> i could say that this is what happens when people push KDE when not 
+> knowing the real number of packages to push, etc etc. I will look what 
+> is missing. 
+THANK YOU.
+
+I've been wondering why KDE is so fragile lately.  Any file selection 
+dialog takes forever to come up (probably some ill-conceived timeout for 
+unavailable NFS mounts), the panel keeps going unresponsive and 
+crashing, leaving you no way to close down windows on different desktops 
+before either CTRL-ALT-BKSP, and Power Management on laptops is AFU.
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017887.html b/zarb-ml/mageia-dev/2012-August/017887.html new file mode 100644 index 000000000..7ee7c297c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017887.html @@ -0,0 +1,105 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Pedro Gs + simplew8 at gmail.com +
+ Thu Aug 2 05:38:16 CEST 2012 +

+
+ +
2012/8/1 Colin Guthrie <mageia at colin.guthr.ie>:
+> 'Twas brillig, and John Balcaen at 01/08/12 17:48 did gyre and gimble:
+>> 2012/8/1 Nicolas Lécureuil <nicolas.lecureuil at free.fr>:
+>>> i though more packages were pushed :(
+>>> i pushed all the remaining w/o our upload script, i will see if all builds
+>>> well.
+>> Build has no reason (except rpmlint issue) to fail since it was tested
+>> before committing.
+>> Regarding the conflicts for handbooks, it's a normal issue since the
+>> conflict was added on purpose.
+>> For libattica issue, it's a "let's push an update without testing it
+>> before" issue, but since most of kde should has been pushed/built
+>> against the new attica it should be safe.
+>
+> Just submitted kdeplasma-addons which still needed the old attica.
+
+I think would be better to keep the old libattica0 package and rename
+the library to libattica0.4 since ABI was changed.
+In attica changelog we can see there a warning regarding this change:
+
+Warning: Non-*ABI* compatible commit. You must rebuild KDE plugins after
+    updating or you might/will experience crashes. API compatible.
+
+This way would not break anything, and i think this would be the more
+correct approach, at least its what i saw in other libraries.
+
+> Col
+>
+>
+> --
+>
+> Colin Guthrie
+> colin(at)mageia.org
+> http://colin.guthr.ie/
+>
+> Day Job:
+>   Tribalogic Limited http://www.tribalogic.net/
+> Open Source:
+>   Mageia Contributor http://www.mageia.org/
+>   PulseAudio Hacker http://www.pulseaudio.org/
+>   Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017888.html b/zarb-ml/mageia-dev/2012-August/017888.html new file mode 100644 index 000000000..016fa30f5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017888.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] is it okay to update? + + + + + + + + + +

[Mageia-dev] is it okay to update?

+ Thomas Spuhler + thomas at btspuhler.com +
+ Thu Aug 2 05:51:31 CEST 2012 +

+
+ +
On Wednesday, August 01, 2012 07:45:58 PM Frank Griffin wrote:
+> On 08/01/2012 11:06 AM, Nicolas Lécureuil wrote:
+> > i could say that this is what happens when people push KDE when not
+> > knowing the real number of packages to push, etc etc. I will look what
+> > is missing.
+> 
+> THANK YOU.
+> 
+> I've been wondering why KDE is so fragile lately.  Any file selection
+> dialog takes forever to come up (probably some ill-conceived timeout for
+> unavailable NFS mounts), the panel keeps going unresponsive and
+> crashing, leaving you no way to close down windows on different desktops
+> before either CTRL-ALT-BKSP, and Power Management on laptops is AFU.
+Same here on a virtualbox. I was thinking it's the virtualbox.
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017889.html b/zarb-ml/mageia-dev/2012-August/017889.html new file mode 100644 index 000000000..c1498497a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017889.html @@ -0,0 +1,338 @@ + + + + [Mageia-dev] new task-obsolete its uninstalling all libreoffice and other packages + + + + + + + + + +

[Mageia-dev] new task-obsolete its uninstalling all libreoffice and other packages

+ Pedro Gs + simplew8 at gmail.com +
+ Thu Aug 2 05:52:26 CEST 2012 +

+
+ +
Hi,
+
+The new package task-obsolete is causinf that all libreoffice and
+other packages are uninstalled, here is the output:
+
+~]# LC_ALL=C urpmi --noclean --auto-select
+In order to satisfy the
+'libreoffice-langpack-pt-BR|libreoffice-langpack-cs|libreoffice-langpack-zh_CN|libreoffice-langpack-pt-PT|libreoffice-langpack-th|libreoffice-langpack-nn|libreoffice-langpack-eu|libreoffice-langpack-ko|libreoffice-langpack-si|libreoffice-langpack-nl|libreoffice-langpack-es|libreoffice-langpack-it|libreoffice-langpack-cy|libreoffice-langpack-gl|libreoffice-langpack-sk|libreoffice-langpack-nr|libreoffice-langpack-tr|libreoffice-langpack-mai|libreoffice-langpack-pl|libreoffice-langpack-mai|libreoffice-langpack-ga|libreoffice-langpack-da|libreoffice-langpack-ro|libreoffice-langpack-es|libreoffice-langpack-pt-BR|libreoffice-langpack-sl|libreoffice-langpack-st|libreoffice-langpack-gu|libreoffice-langpack-pa|libreoffice-langpack-fi|libreoffice-langpack-tn|libreoffice-langpack-te|libreoffice-langpack-el|libreoffice-langpack-fr|libreoffice-langpack-bg|libreoffice-langpack-nso|libreoffice-langpack-kn|libreoffice-langpack-pl|libreoffice-langpack-nl|libreoffice-langpack-te|libreoffice-langpack-as|libreoffice-langpack-nr|libreoffice-langpack-zu|libreoffice-langpack-gl|libreoffice-langpack-pa|libreoffice-langpack-ru|libreoffice-langpack-or|libreoffice-langpack-th|libreoffice-langpack-af|libreoffice-langpack-fr|libreoffice-langpack-nn|libreoffice-langpack-ta|libreoffice-langpack-ja|libreoffice-langpack-pt-BR|libreoffice-langpack-cs|libreoffice-langpack-ro|libreoffice-langpack-lt|libreoffice-langpack-hr|libreoffice-langpack-ve|libreoffice-langpack-ca|libreoffice-langpack-mr|libreoffice-langpack-sl|libreoffice-langpack-da|libreoffice-langpack-bn|libreoffice-langpack-bn|libreoffice-langpack-ca|libreoffice-langpack-he|libreoffice-langpack-or|libreoffice-langpack-zh_CN|libreoffice-langpack-ss|libreoffice-langpack-ko|libreoffice-langpack-sv|libreoffice-langpack-ts|libreoffice-langpack-nb|libreoffice-langpack-ve|libreoffice-langpack-hi|libreoffice-langpack-hu|libreoffice-langpack-hr|libreoffice-langpack-cy|libreoffice-langpack-zh_TW|libreoffice-langpack-de|libreoffice-langpack-el|libreoffice-langpack-xh|libreoffice-langpack-lt|libreoffice-langpack-hu|libreoffice-langpack-af|libreoffice-langpack-kn|libreoffice-langpack-ss|libreoffice-langpack-hi|libreoffice-langpack-zu|libreoffice-langpack-ta|libreoffice-langpack-ar|libreoffice-langpack-as|libreoffice-langpack-et|libreoffice-langpack-dz|libreoffice-langpack-he|libreoffice-langpack-fi|libreoffice-langpack-ml|libreoffice-langpack-mr|libreoffice-langpack-nso|libreoffice-langpack-et|libreoffice-langpack-it|libreoffice-langpack-nb|libreoffice-langpack-ts|libreoffice-langpack-eu|libreoffice-langpack-uk|libreoffice-langpack-ga|libreoffice-langpack-ru|libreoffice-langpack-sk|libreoffice-langpack-si|libreoffice-langpack-st|libreoffice-langpack-en|libreoffice-langpack-sr|libreoffice-langpack-en|libreoffice-langpack-ar|libreoffice-langpack-bg|libreoffice-langpack-uk|libreoffice-langpack-dz|libreoffice-langpack-gu|libreoffice-langpack-sv|libreoffice-langpack-de|libreoffice-langpack-ja|libreoffice-langpack-tn|libreoffice-langpack-zh_TW|libreoffice-langpack-xh|libreoffice-langpack-ml|libreoffice-langpack-tr|libreoffice-langpack-sr'
+dependency, one of the following packages is needed:
+ 1- libreoffice-langpack-pt-BR-3.6.0.1-1.mga3.x86_64: Brazilian
+Portuguese language pack for LibreOffice (to install)
+ 2- libreoffice-langpack-en-3.6.0.1-1.mga3.x86_64: English language
+pack for LibreOffice (to install)
+ 3- libreoffice-langpack-nso-3.6.0.1-1.mga3.x86_64: Northern Sotho
+language pack for LibreOffice (to install)
+What is your choice? (1-3)
+Some requested packages cannot be installed:
+lib64ebackend2-3.4.1-1.mga2.x86_64 (in order to keep
+lib64ebackend2-3.4.3-1.mga3.x86_64)
+libreoffice-calc-3.5.3.2-1.mga2.x86_64 (in order to keep
+libreoffice-calc-3.6.0.1-1.mga3.x86_64)
+libreoffice-core-3.5.3.2-1.mga2.x86_64 (in order to keep
+libreoffice-core-3.6.0.1-1.mga3.x86_64)
+libreoffice-langpack-pt-BR-3.6.0.1-1.mga3.x86_64 (due to unsatisfied
+libreoffice-core[== 3.6.0.1-1.mga3])
+libreoffice-pyuno-3.5.3.2-1.mga2.x86_64 (in order to keep
+libreoffice-pyuno-3.6.0.1-1.mga3.x86_64)
+libreoffice-ure-3.5.3.2-1.mga2.x86_64 (in order to keep
+libreoffice-ure-3.6.0.1-1.mga3.x86_64)
+libreoffice-writer-3.5.3.2-1.mga2.x86_64 (in order to keep
+libreoffice-writer-3.6.0.1-1.mga3.x86_64)
+Continue installation anyway? (Y/n)
+The following packages have to be removed for others to be upgraded:
+gnome-documents-0.5.4-2.mga3.x86_64
+ (due to missing unoconv)
+lib64ebackend2-3.4.3-1.mga3.x86_64
+ (due to missing libdb-5.2.so()(64bit))
+lib64edata-book13-3.4.3-1.mga3.x86_64
+ (due to missing libebackend-1.2.so.2()(64bit))
+lib64edata-cal15-3.4.3-1.mga3.x86_64
+ (due to missing libebackend-1.2.so.2()(64bit))
+libreoffice-base-3.6.0.1-1.mga3.x86_64
+ (due to missing libjvmfwk.so.3()(64bit),
+  due to missing libutllo.so()(64bit),
+  due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libtllo.so()(64bit),
+  due to missing libsvxlo.so()(64bit),
+  due to missing libtklo.so()(64bit),
+  due to missing libdbtoolslo.so()(64bit),
+  due to missing libsvxcorelo.so()(64bit),
+  due to missing libi18nisolang1gcc3.so()(64bit),
+  due to missing libsvtlo.so()(64bit),
+  due to missing libsvllo.so()(64bit),
+  due to missing libsotlo.so()(64bit),
+  due to missing libsaxlo.so()(64bit),
+  due to missing libfwelo.so()(64bit),
+  due to missing libsfxlo.so()(64bit),
+  due to missing libucbhelper4gcc3.so()(64bit),
+  due to missing libeditenglo.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libxolo.so()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libdbulo.so()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit),
+  due to unsatisfied libreoffice-calc == 3.6.0.1-1.mga3,
+  due to missing libforlo.so()(64bit))
+libreoffice-calc-3.6.0.1-1.mga3.x86_64
+ (due to missing libavmedialo.so()(64bit),
+  due to missing libutllo.so()(64bit),
+  due to missing libbasegfxlo.so()(64bit),
+  due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libmsfilterlo.so()(64bit),
+  due to missing libtllo.so()(64bit),
+  due to missing libfilelo.so()(64bit),
+  due to missing libsvxlo.so()(64bit),
+  due to missing libtklo.so()(64bit),
+  due to missing libvbahelperlo.so()(64bit),
+  due to missing libdbtoolslo.so()(64bit),
+  due to missing libooxlo.so()(64bit),
+  due to missing libsvxcorelo.so()(64bit),
+  due to missing libi18nisolang1gcc3.so()(64bit),
+  due to missing libsvtlo.so()(64bit),
+  due to missing libsvllo.so()(64bit),
+  due to missing libdrawinglayerlo.so()(64bit),
+  due to missing libsotlo.so()(64bit),
+  due to missing libsaxlo.so()(64bit),
+  due to missing libsfxlo.so()(64bit),
+  due to missing libucbhelper4gcc3.so()(64bit),
+  due to missing libeditenglo.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libsblo.so()(64bit),
+  due to missing libxolo.so()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libuno_salhelpergcc3.so.3()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-core-3.6.0.1-1.mga3.x86_64
+ (due to missing libdb-5.2.so()(64bit),
+  due to missing libuno_salhelpergcc3.so.3()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-draw-3.6.0.1-1.mga3.x86_64
+ (due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to unsatisfied libreoffice-graphicfilter == 3.6.0.1-1.mga3,
+  due to unsatisfied libreoffice-pdfimport == 3.6.0.1-1.mga3)
+libreoffice-emailmerge-3.6.0.1-1.mga3.x86_64
+ (due to unsatisfied libreoffice-writer == 3.6.0.1-1.mga3,
+  due to unsatisfied libreoffice-pyuno == 3.6.0.1-1.mga3)
+libreoffice-graphicfilter-3.6.0.1-1.mga3.x86_64
+ (due to missing libutllo.so()(64bit),
+  due to missing libbasegfxlo.so()(64bit),
+  due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libtllo.so()(64bit),
+  due to missing libsvxcorelo.so()(64bit),
+  due to missing libsvtlo.so()(64bit),
+  due to missing libsvllo.so()(64bit),
+  due to missing libsaxlo.so()(64bit),
+  due to missing libeditenglo.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libxolo.so()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-impress-3.6.0.1-1.mga3.x86_64
+ (due to missing libsaxlo.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit),
+  due to unsatisfied libreoffice-ogltrans == 3.6.0.1-1.mga3,
+  due to unsatisfied libreoffice-presenter-screen == 3.6.0.1-1.mga3)
+libreoffice-kde-3.6.0.1-1.mga3.x86_64
+ (due to missing libutllo.so()(64bit),
+  due to missing libbasegfxlo.so()(64bit),
+  due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libtllo.so()(64bit),
+  due to missing libi18nisolang1gcc3.so()(64bit),
+  due to missing libi18nutilgcc3.so()(64bit),
+  due to missing libsotlo.so()(64bit),
+  due to missing libucbhelper4gcc3.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libvclplug_genlo.so()(64bit),
+  due to missing libjvmaccessgcc3.so.3()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-langpack-pt-PT-3.6.0.1-1.mga3.x86_64
+ (due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3)
+libreoffice-math-3.6.0.1-1.mga3.x86_64
+ (due to missing libutllo.so()(64bit),
+  due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libmsfilterlo.so()(64bit),
+  due to missing libtllo.so()(64bit),
+  due to missing libsvxlo.so()(64bit),
+  due to missing libtklo.so()(64bit),
+  due to missing libooxlo.so()(64bit),
+  due to missing libsvxcorelo.so()(64bit),
+  due to missing libsvtlo.so()(64bit),
+  due to missing libsvllo.so()(64bit),
+  due to missing libi18nutilgcc3.so()(64bit),
+  due to missing libsotlo.so()(64bit),
+  due to missing libsaxlo.so()(64bit),
+  due to missing libsfxlo.so()(64bit),
+  due to missing libucbhelper4gcc3.so()(64bit),
+  due to missing libeditenglo.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libxolo.so()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-ogltrans-3.6.0.1-1.mga3.x86_64
+ (due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libcanvastoolslo.so()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit),
+  due to unsatisfied libreoffice-impress == 3.6.0.1-1.mga3)
+libreoffice-pdfimport-3.6.0.1-1.mga3.x86_64
+ (due to missing libreoffice-core[*],
+  due to missing libuno_cppu.so.3()(64bit),
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit),
+  due to unsatisfied libreoffice-draw == 3.6.0.1-1.mga3)
+libreoffice-presentation-minimizer-3.6.0.1-1.mga3.x86_64
+ (due to missing libreoffice-core[*],
+  due to missing libuno_cppu.so.3()(64bit),
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit),
+  due to unsatisfied libreoffice-impress == 3.6.0.1-1.mga3)
+libreoffice-presenter-screen-3.6.0.1-1.mga3.x86_64
+ (due to missing libreoffice-core[*],
+  due to missing libuno_cppu.so.3()(64bit),
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit),
+  due to unsatisfied libreoffice-impress == 3.6.0.1-1.mga3)
+libreoffice-pyuno-3.6.0.1-1.mga3.x86_64
+ (due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libreoffice-core[*],
+  due to missing libuno_salhelpergcc3.so.3()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-report-builder-3.6.0.1-1.mga3.x86_64
+ (due to missing libreoffice-core[*],
+  due to unsatisfied libreoffice-base == 3.6.0.1-1.mga3)
+libreoffice-ure-3.6.0.1-1.mga3.x86_64
+ (due to missing libjvmfwk.so.3()(64bit),
+  due to missing libjvmaccessgcc3.so.3()(64bit))
+libreoffice-wiki-publisher-3.6.0.1-1.mga3.x86_64
+ (due to missing libreoffice-core[*],
+  due to unsatisfied libreoffice-writer == 3.6.0.1-1.mga3)
+libreoffice-writer-3.6.0.1-1.mga3.x86_64
+ (due to missing libutllo.so()(64bit),
+  due to missing libbasegfxlo.so()(64bit),
+  due to missing libcomphelpgcc3.so()(64bit),
+  due to missing libmsfilterlo.so()(64bit),
+  due to missing libtllo.so()(64bit),
+  due to missing libsvxlo.so()(64bit),
+  due to missing libtklo.so()(64bit),
+  due to missing libvbahelperlo.so()(64bit),
+  due to missing libooxlo.so()(64bit),
+  due to missing libsvxcorelo.so()(64bit),
+  due to missing libi18nisolang1gcc3.so()(64bit),
+  due to missing libsvtlo.so()(64bit),
+  due to missing libsvllo.so()(64bit),
+  due to missing libswlo.so()(64bit),
+  due to missing libi18nutilgcc3.so()(64bit),
+  due to missing libsotlo.so()(64bit),
+  due to missing libsaxlo.so()(64bit),
+  due to missing libsfxlo.so()(64bit),
+  due to missing libucbhelper4gcc3.so()(64bit),
+  due to missing libeditenglo.so()(64bit),
+  due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3,
+  due to missing libsblo.so()(64bit),
+  due to missing libxolo.so()(64bit),
+  due to missing libvcllo.so()(64bit),
+  due to missing libuno_cppu.so.3()(64bit),
+  due to unsatisfied libreoffice-ure == 3.6.0.1-1.mga3,
+  due to missing libuno_cppuhelpergcc3.so.3()(64bit),
+  due to missing libuno_sal.so.3()(64bit))
+libreoffice-xsltfilter-3.6.0.1-1.mga3.x86_64
+ (due to unsatisfied libreoffice-core == 3.6.0.1-1.mga3)
+unoconv-0.4-1.mga2.noarch
+ (due to missing libreoffice-core,
+  due to missing libreoffice-pyuno) (y/N) y
+To satisfy dependencies, the following packages are going to be installed:
+  Package                        Version      Release       Arch
+(medium "Core Release (distrib1)")
+  kdebase4-workspace-plasma-con> 4.9.0        1.mga3        noarch
+  task-obsolete                  3            21.mga3       noarch
+313MB of disk space will be freed.
+36KB of packages will be retrieved.
+Proceed with the installation of the 2 packages? (Y/n)
+
+regards,
+Pedro
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017890.html b/zarb-ml/mageia-dev/2012-August/017890.html new file mode 100644 index 000000000..b019afe36 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017890.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] new task-obsolete its uninstalling all libreoffice and other packages + + + + + + + + + +

[Mageia-dev] new task-obsolete its uninstalling all libreoffice and other packages

+ Charles A Edwards + CAE at eslrahc.com +
+ Thu Aug 2 07:03:04 CEST 2012 +

+
+ +
On Thu, 2 Aug 2012 04:52:26 +0100
+Pedro Gs wrote:
+
+> The new package task-obsolete is causinf that all libreoffice and
+> other packages are uninstalled, here is the output
+
+I detest task-obsolete.
+
+The first thing I do after a new install is to put
+task-obsolete at the top of /etc/urpmi/skip. list.
+
+
+    Charles
+
+-- 
+Our country has plenty of good five-cent cigars, but the trouble is
+they charge fifteen cents for them.
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.0-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120802/cec738cd/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017891.html b/zarb-ml/mageia-dev/2012-August/017891.html new file mode 100644 index 000000000..496f7e16e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017891.html @@ -0,0 +1,134 @@ + + + + [Mageia-dev] db5.3 rebuilds still needed + + + + + + + + + +

[Mageia-dev] db5.3 rebuilds still needed

+ Charles A Edwards + CAE at eslrahc.com +
+ Thu Aug 2 07:34:17 CEST 2012 +

+
+ +
The following is a list of the apps which still require 
+libdb-5.2.so()/(64bit) that need a rebuild for db5.3
+
+apr-util-dbm-db
+c-icap-client
+c-icap-modules
+c-icap-modules-extra
+cyrus-imapd
+cyrus-imapd-murder
+cyrus-imapd-nntp
+cyrus-imapd-utils
+cyrus-sasl 
+dsniff
+evolution-data-server
+evolution-exchange
+evolution-exchange 
+heimdal-libs
+hotkeys
+inn
+iproute2 
+lib64ebackend1.2_4  
+libreoffice-core
+libreoffice-core
+mutt
+mutt-utf8
+netatalk
+ocaml-dbm
+ocaml-ocsigenserver
+openldap-servers
+pam_abl
+perl
+perl-BDB
+perl-BerkeleyDB
+perl-Cyrus
+perl-DB_File
+php-dba
+poedit
+python
+ruby-bdb
+satsolver-demo
+satsolver-tools
+sendmail
+squid
+squidguard
+
+Warning: If you have any of the above installed and have task-obsolete
+installed it Will remove the above listed apps.
+
+
+    Charles
+
+
+-- 
+Why won't sharks eat lawyers?   Professional courtesy.
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.0-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120802/5e5d4e04/attachment.asc>
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017892.html b/zarb-ml/mageia-dev/2012-August/017892.html new file mode 100644 index 000000000..c5e0e8629 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017892.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] net_applet segfaulting + + + + + + + + + +

[Mageia-dev] net_applet segfaulting

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 2 09:39:10 CEST 2012 +

+
+ +
On 1 July 2012 17:21, Shlomi Fish <shlomif at shlomifish.org> wrote:
+> That's the wrong way to use gdb. You should do:
+>
+> $ gdb /usr/bin/perl
+> $ run /usr/bin/net_applet
+
+The following is way simpler:
+gdb -q --args perl /usr/bin/net_applet
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017893.html b/zarb-ml/mageia-dev/2012-August/017893.html new file mode 100644 index 000000000..9c57c7592 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017893.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] %_libexecdir - Re: [5228] revert some duplicated manbo stuff (all identical to default but + + + + + + + + + +

[Mageia-dev] %_libexecdir - Re: [5228] revert some duplicated manbo stuff (all identical to default but

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 2 09:51:42 CEST 2012 +

+
+ +
On 2 August 2012 00:34, Olivier Blin <mageia at blino.org> wrote:
+>> as those sections are already compressed, I would say the overhead
+>> would be slight bigger,
+>> maybe 1% instead of 0.5%
+>>
+>> I suggests we go with it.
+>> If it proves too big, we can disable it globally and enable it on a
+>> per package case
+>> (eg: glibc/rpm/perl-URPM/perl/glib/gtk/pango/cairo/libx11/perl-Gtk2/perl-Glib/kde*)
+>
+> Looks good, go for it :)
+
+Done in git :-)
+Along killing deprecated rpm->rpmbuild aliases
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017894.html b/zarb-ml/mageia-dev/2012-August/017894.html new file mode 100644 index 000000000..2ed78dcc0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017894.html @@ -0,0 +1,122 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 2 10:28:28 CEST 2012 +

+
+ +
'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+gimble:
+> On Wed, 1 Aug 2012, Colin Guthrie wrote:
+> 
+>> I have to agree here that something is "funny" in the libattica package
+>> which ultimately helped to contribute to this issue.
+>>
+>> e.g. on my system before update (tho' with similar results after):
+>>
+>> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+>> libattica.so.0.3()(64bit)
+>> lib64attica0 = 0.3.0-1.mga2
+>> lib64attica0(x86-64) = 0.3.0-1.mga2
+>> [colin at jimmy ~]$ rpm -ql lib64attica0
+>> /usr/lib64/libattica.so.0.3
+>> /usr/lib64/libattica.so.0.3.0
+> 
+>> So I can see how this mistake was made and TBH I could have made the
+>> same mistake myself (with the caveat that I likely would not have bumped
+>> the version of someone else's package with out confirming first and that
+>> it should have been obvious from testing and installing the build)
+>>
+>> But either way this seems like an issue to fix properly (possibly with
+>> an upstream fix or some modification to the library policy when the
+>> minor version is "presented" like this).
+> 
+> Good catch! Of course it's never the library policy that's wrong. The
+> library major version is apparently 0.4 so the correct package name is
+>    lib64attica0.3  for the previous one
+>    lib64attica0.4  for the current one
+> 
+> ... in the specfile:   %define attica_major 0.4
+> 
+> Can the maintainer of this package please fix this?
+> 
+> To find the version to use, look up the 'soname' of the library. I use:
+>   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+> =>
+> ...                    Library soname: [libattica.so.0.4]
+> 
+> What follows ".so." is the major version of the library.
+
+Is that really the correct definition of what a "major" version is?
+
+I always thought the major was just the first number.
+
+The library policy certainly doesn't mention "double digit majors" or
+similar.
+
+Is this something upstream is doing deliberately or is it just an oversight?
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017895.html b/zarb-ml/mageia-dev/2012-August/017895.html new file mode 100644 index 000000000..653e0fdc6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017895.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Balcaen John + mikala at mageia.org +
+ Thu Aug 2 11:01:03 CEST 2012 +

+
+ +
Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit :
+> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+> 
+> gimble:
+> > On Wed, 1 Aug 2012, Colin Guthrie wrote:
+> >> I have to agree here that something is "funny" in the libattica package
+> >> which ultimately helped to contribute to this issue.
+> >> 
+> >> e.g. on my system before update (tho' with similar results after):
+> >> 
+> >> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+> >> libattica.so.0.3()(64bit)
+> >> lib64attica0 = 0.3.0-1.mga2
+> >> lib64attica0(x86-64) = 0.3.0-1.mga2
+> >> [colin at jimmy ~]$ rpm -ql lib64attica0
+> >> /usr/lib64/libattica.so.0.3
+> >> /usr/lib64/libattica.so.0.3.0
+> >> 
+> >> So I can see how this mistake was made and TBH I could have made the
+> >> same mistake myself (with the caveat that I likely would not have bumped
+> >> the version of someone else's package with out confirming first and that
+> >> it should have been obvious from testing and installing the build)
+> >> 
+> >> But either way this seems like an issue to fix properly (possibly with
+> >> an upstream fix or some modification to the library policy when the
+> >> minor version is "presented" like this).
+> > 
+> > Good catch! Of course it's never the library policy that's wrong. The
+> > library major version is apparently 0.4 so the correct package name is
+> > 
+> >    lib64attica0.3  for the previous one
+> >    lib64attica0.4  for the current one
+> > 
+> > ... in the specfile:   %define attica_major 0.4
+> > 
+> > Can the maintainer of this package please fix this?
+> > 
+> > To find the version to use, look up the 'soname' of the library. I use:
+> >   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+> > 
+> > =>
+> > ...                    Library soname: [libattica.so.0.4]
+> > 
+> > What follows ".so." is the major version of the library.
+> 
+> Is that really the correct definition of what a "major" version is?
+> 
+> I always thought the major was just the first number.
+> 
+> The library policy certainly doesn't mention "double digit majors" or
+> similar.
+> 
+> Is this something upstream is doing deliberately or is it just an oversight?
+https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt
+
+
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017896.html b/zarb-ml/mageia-dev/2012-August/017896.html new file mode 100644 index 000000000..cda979349 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017896.html @@ -0,0 +1,117 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 2 11:11:52 CEST 2012 +

+
+ +
On Thu, Aug 2, 2012 at 10:01 AM, Balcaen John <mikala at mageia.org> wrote:
+> Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit :
+>> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+>>
+>> gimble:
+>> > On Wed, 1 Aug 2012, Colin Guthrie wrote:
+>> >> I have to agree here that something is "funny" in the libattica package
+>> >> which ultimately helped to contribute to this issue.
+>> >>
+>> >> e.g. on my system before update (tho' with similar results after):
+>> >>
+>> >> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+>> >> libattica.so.0.3()(64bit)
+>> >> lib64attica0 = 0.3.0-1.mga2
+>> >> lib64attica0(x86-64) = 0.3.0-1.mga2
+>> >> [colin at jimmy ~]$ rpm -ql lib64attica0
+>> >> /usr/lib64/libattica.so.0.3
+>> >> /usr/lib64/libattica.so.0.3.0
+>> >>
+>> >> So I can see how this mistake was made and TBH I could have made the
+>> >> same mistake myself (with the caveat that I likely would not have bumped
+>> >> the version of someone else's package with out confirming first and that
+>> >> it should have been obvious from testing and installing the build)
+>> >>
+>> >> But either way this seems like an issue to fix properly (possibly with
+>> >> an upstream fix or some modification to the library policy when the
+>> >> minor version is "presented" like this).
+>> >
+>> > Good catch! Of course it's never the library policy that's wrong. The
+>> > library major version is apparently 0.4 so the correct package name is
+>> >
+>> >    lib64attica0.3  for the previous one
+>> >    lib64attica0.4  for the current one
+>> >
+>> > ... in the specfile:   %define attica_major 0.4
+>> >
+>> > Can the maintainer of this package please fix this?
+>> >
+>> > To find the version to use, look up the 'soname' of the library. I use:
+>> >   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+>> >
+>> > =>
+>> > ...                    Library soname: [libattica.so.0.4]
+>> >
+>> > What follows ".so." is the major version of the library.
+>>
+>> Is that really the correct definition of what a "major" version is?
+>>
+>> I always thought the major was just the first number.
+>>
+>> The library policy certainly doesn't mention "double digit majors" or
+>> similar.
+>>
+>> Is this something upstream is doing deliberately or is it just an oversight?
+> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt
+
+Yet something includes the minor in the soname
+
+This leads to https://lists.fedoraproject.org/pipermail/scm-commits/2011-December/698438.html
+or it being flagged in debian by the package-name-doesnt-match-sonames
+lintian test.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017897.html b/zarb-ml/mageia-dev/2012-August/017897.html new file mode 100644 index 000000000..205bd914b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017897.html @@ -0,0 +1,121 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 2 11:15:16 CEST 2012 +

+
+ +
On Thu, Aug 2, 2012 at 10:11 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Thu, Aug 2, 2012 at 10:01 AM, Balcaen John <mikala at mageia.org> wrote:
+>> Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit :
+>>> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+>>>
+>>> gimble:
+>>> > On Wed, 1 Aug 2012, Colin Guthrie wrote:
+>>> >> I have to agree here that something is "funny" in the libattica package
+>>> >> which ultimately helped to contribute to this issue.
+>>> >>
+>>> >> e.g. on my system before update (tho' with similar results after):
+>>> >>
+>>> >> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+>>> >> libattica.so.0.3()(64bit)
+>>> >> lib64attica0 = 0.3.0-1.mga2
+>>> >> lib64attica0(x86-64) = 0.3.0-1.mga2
+>>> >> [colin at jimmy ~]$ rpm -ql lib64attica0
+>>> >> /usr/lib64/libattica.so.0.3
+>>> >> /usr/lib64/libattica.so.0.3.0
+>>> >>
+>>> >> So I can see how this mistake was made and TBH I could have made the
+>>> >> same mistake myself (with the caveat that I likely would not have bumped
+>>> >> the version of someone else's package with out confirming first and that
+>>> >> it should have been obvious from testing and installing the build)
+>>> >>
+>>> >> But either way this seems like an issue to fix properly (possibly with
+>>> >> an upstream fix or some modification to the library policy when the
+>>> >> minor version is "presented" like this).
+>>> >
+>>> > Good catch! Of course it's never the library policy that's wrong. The
+>>> > library major version is apparently 0.4 so the correct package name is
+>>> >
+>>> >    lib64attica0.3  for the previous one
+>>> >    lib64attica0.4  for the current one
+>>> >
+>>> > ... in the specfile:   %define attica_major 0.4
+>>> >
+>>> > Can the maintainer of this package please fix this?
+>>> >
+>>> > To find the version to use, look up the 'soname' of the library. I use:
+>>> >   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+>>> >
+>>> > =>
+>>> > ...                    Library soname: [libattica.so.0.4]
+>>> >
+>>> > What follows ".so." is the major version of the library.
+>>>
+>>> Is that really the correct definition of what a "major" version is?
+>>>
+>>> I always thought the major was just the first number.
+>>>
+>>> The library policy certainly doesn't mention "double digit majors" or
+>>> similar.
+>>>
+>>> Is this something upstream is doing deliberately or is it just an oversight?
+>> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt
+>
+> Yet something includes the minor in the soname
+>
+> This leads to https://lists.fedoraproject.org/pipermail/scm-commits/2011-December/698438.html
+> or it being flagged in debian by the package-name-doesnt-match-sonames
+> lintian test.
+
+The change https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34
+is the culprit
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017898.html b/zarb-ml/mageia-dev/2012-August/017898.html new file mode 100644 index 000000000..fe0636bf6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017898.html @@ -0,0 +1,140 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 2 11:17:51 CEST 2012 +

+
+ +
'Twas brillig, and Balcaen John at 02/08/12 10:01 did gyre and gimble:
+> Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit :
+>> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+>>
+>> gimble:
+>>> On Wed, 1 Aug 2012, Colin Guthrie wrote:
+>>>> I have to agree here that something is "funny" in the libattica package
+>>>> which ultimately helped to contribute to this issue.
+>>>>
+>>>> e.g. on my system before update (tho' with similar results after):
+>>>>
+>>>> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+>>>> libattica.so.0.3()(64bit)
+>>>> lib64attica0 = 0.3.0-1.mga2
+>>>> lib64attica0(x86-64) = 0.3.0-1.mga2
+>>>> [colin at jimmy ~]$ rpm -ql lib64attica0
+>>>> /usr/lib64/libattica.so.0.3
+>>>> /usr/lib64/libattica.so.0.3.0
+>>>>
+>>>> So I can see how this mistake was made and TBH I could have made the
+>>>> same mistake myself (with the caveat that I likely would not have bumped
+>>>> the version of someone else's package with out confirming first and that
+>>>> it should have been obvious from testing and installing the build)
+>>>>
+>>>> But either way this seems like an issue to fix properly (possibly with
+>>>> an upstream fix or some modification to the library policy when the
+>>>> minor version is "presented" like this).
+>>>
+>>> Good catch! Of course it's never the library policy that's wrong. The
+>>> library major version is apparently 0.4 so the correct package name is
+>>>
+>>>    lib64attica0.3  for the previous one
+>>>    lib64attica0.4  for the current one
+>>>
+>>> ... in the specfile:   %define attica_major 0.4
+>>>
+>>> Can the maintainer of this package please fix this?
+>>>
+>>> To find the version to use, look up the 'soname' of the library. I use:
+>>>   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+>>>
+>>> =>
+>>> ...                    Library soname: [libattica.so.0.4]
+>>>
+>>> What follows ".so." is the major version of the library.
+>>
+>> Is that really the correct definition of what a "major" version is?
+>>
+>> I always thought the major was just the first number.
+>>
+>> The library policy certainly doesn't mention "double digit majors" or
+>> similar.
+>>
+>> Is this something upstream is doing deliberately or is it just an oversight?
+> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt
+
+Actually it's this file/line:
+
+https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/lib/CMakeLists.txt#L120
+
+So it's seems like this was done deliberately due to a ABI breakage a
+while ago:
+
+https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34
+
+Now, this is an interesting point (regarding our lib policy) bumping the
+major for an API change and the minor for an ABI change seems kinda
+sensible to me. So how should we deal with that in our policy? Just use
+0.4 as the "major" value here as Christiaan suggested?
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017899.html b/zarb-ml/mageia-dev/2012-August/017899.html new file mode 100644 index 000000000..12e29125a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017899.html @@ -0,0 +1,130 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 2 11:31:04 CEST 2012 +

+
+ +
On Thu, Aug 2, 2012 at 10:17 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Balcaen John at 02/08/12 10:01 did gyre and gimble:
+>> Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit :
+>>> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+>>>
+>>> gimble:
+>>>> On Wed, 1 Aug 2012, Colin Guthrie wrote:
+>>>>> I have to agree here that something is "funny" in the libattica package
+>>>>> which ultimately helped to contribute to this issue.
+>>>>>
+>>>>> e.g. on my system before update (tho' with similar results after):
+>>>>>
+>>>>> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+>>>>> libattica.so.0.3()(64bit)
+>>>>> lib64attica0 = 0.3.0-1.mga2
+>>>>> lib64attica0(x86-64) = 0.3.0-1.mga2
+>>>>> [colin at jimmy ~]$ rpm -ql lib64attica0
+>>>>> /usr/lib64/libattica.so.0.3
+>>>>> /usr/lib64/libattica.so.0.3.0
+>>>>>
+>>>>> So I can see how this mistake was made and TBH I could have made the
+>>>>> same mistake myself (with the caveat that I likely would not have bumped
+>>>>> the version of someone else's package with out confirming first and that
+>>>>> it should have been obvious from testing and installing the build)
+>>>>>
+>>>>> But either way this seems like an issue to fix properly (possibly with
+>>>>> an upstream fix or some modification to the library policy when the
+>>>>> minor version is "presented" like this).
+>>>>
+>>>> Good catch! Of course it's never the library policy that's wrong. The
+>>>> library major version is apparently 0.4 so the correct package name is
+>>>>
+>>>>    lib64attica0.3  for the previous one
+>>>>    lib64attica0.4  for the current one
+>>>>
+>>>> ... in the specfile:   %define attica_major 0.4
+>>>>
+>>>> Can the maintainer of this package please fix this?
+>>>>
+>>>> To find the version to use, look up the 'soname' of the library. I use:
+>>>>   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+>>>>
+>>>> =>
+>>>> ...                    Library soname: [libattica.so.0.4]
+>>>>
+>>>> What follows ".so." is the major version of the library.
+>>>
+>>> Is that really the correct definition of what a "major" version is?
+>>>
+>>> I always thought the major was just the first number.
+>>>
+>>> The library policy certainly doesn't mention "double digit majors" or
+>>> similar.
+>>>
+>>> Is this something upstream is doing deliberately or is it just an oversight?
+>> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/CMakeLists.txt
+>
+> Actually it's this file/line:
+>
+> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/master/entry/lib/CMakeLists.txt#L120
+>
+> So it's seems like this was done deliberately due to a ABI breakage a
+> while ago:
+>
+> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34
+>
+> Now, this is an interesting point (regarding our lib policy) bumping the
+> major for an API change and the minor for an ABI change seems kinda
+> sensible to me. So how should we deal with that in our policy? Just use
+> 0.4 as the "major" value here as Christiaan suggested?
+
+A minor change is supposed to only add interfaces and be backwards
+compatible, that's why it is not in the soname.
+If there has been an ABI breakage, the major should be incremented.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017900.html b/zarb-ml/mageia-dev/2012-August/017900.html new file mode 100644 index 000000000..82e5ca204 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017900.html @@ -0,0 +1,140 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Thu Aug 2 11:35:55 CEST 2012 +

+
+ +
Le jeudi 2 août 2012 10:31:04 Pascal Terjan a écrit :
+> On Thu, Aug 2, 2012 at 10:17 AM, Colin Guthrie <mageia at colin.guthr.ie> 
+wrote:
+> > 'Twas brillig, and Balcaen John at 02/08/12 10:01 did gyre and gimble:
+> >> Le jeudi 2 août 2012 09:28:28 Colin Guthrie a écrit :
+> >>> 'Twas brillig, and Christiaan Welvaart at 01/08/12 23:09 did gyre and
+> >>> 
+> >>> gimble:
+> >>>> On Wed, 1 Aug 2012, Colin Guthrie wrote:
+> >>>>> I have to agree here that something is "funny" in the libattica
+> >>>>> package
+> >>>>> which ultimately helped to contribute to this issue.
+> >>>>> 
+> >>>>> e.g. on my system before update (tho' with similar results after):
+> >>>>> 
+> >>>>> [colin at jimmy ~]$ rpm -q --provides lib64attica0
+> >>>>> libattica.so.0.3()(64bit)
+> >>>>> lib64attica0 = 0.3.0-1.mga2
+> >>>>> lib64attica0(x86-64) = 0.3.0-1.mga2
+> >>>>> [colin at jimmy ~]$ rpm -ql lib64attica0
+> >>>>> /usr/lib64/libattica.so.0.3
+> >>>>> /usr/lib64/libattica.so.0.3.0
+> >>>>> 
+> >>>>> So I can see how this mistake was made and TBH I could have made the
+> >>>>> same mistake myself (with the caveat that I likely would not have
+> >>>>> bumped
+> >>>>> the version of someone else's package with out confirming first and
+> >>>>> that
+> >>>>> it should have been obvious from testing and installing the build)
+> >>>>> 
+> >>>>> But either way this seems like an issue to fix properly (possibly with
+> >>>>> an upstream fix or some modification to the library policy when the
+> >>>>> minor version is "presented" like this).
+> >>>> 
+> >>>> Good catch! Of course it's never the library policy that's wrong. The
+> >>>> library major version is apparently 0.4 so the correct package name is
+> >>>> 
+> >>>>    lib64attica0.3  for the previous one
+> >>>>    lib64attica0.4  for the current one
+> >>>> 
+> >>>> ... in the specfile:   %define attica_major 0.4
+> >>>> 
+> >>>> Can the maintainer of this package please fix this?
+> >>>> 
+> >>>> To find the version to use, look up the 'soname' of the library. I use:
+> >>>>   readelf -a /usr/lib64/libattica.so.0.4|grep SONAME
+> >>>> 
+> >>>> =>
+> >>>> ...                    Library soname: [libattica.so.0.4]
+> >>>> 
+> >>>> What follows ".so." is the major version of the library.
+> >>> 
+> >>> Is that really the correct definition of what a "major" version is?
+> >>> 
+> >>> I always thought the major was just the first number.
+> >>> 
+> >>> The library policy certainly doesn't mention "double digit majors" or
+> >>> similar.
+> >>> 
+> >>> Is this something upstream is doing deliberately or is it just an
+> >>> oversight?>> 
+> >> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/
+> >> master/entry/CMakeLists.txt> 
+> > Actually it's this file/line:
+> > 
+> > https://projects.kde.org/projects/kdesupport/attica/repository/revisions/m
+> > aster/entry/lib/CMakeLists.txt#L120
+> > 
+> > So it's seems like this was done deliberately due to a ABI breakage a
+> > while ago:
+> > 
+> > https://projects.kde.org/projects/kdesupport/attica/repository/revisions/a
+> > c2270b1f9c445fd39e48051b99d35d9b9693a34
+> > 
+> > Now, this is an interesting point (regarding our lib policy) bumping the
+> > major for an API change and the minor for an ABI change seems kinda
+> > sensible to me. So how should we deal with that in our policy? Just use
+> > 0.4 as the "major" value here as Christiaan suggested?
+> 
+> A minor change is supposed to only add interfaces and be backwards
+> compatible, that's why it is not in the soname.
+> If there has been an ABI breakage, the major should be incremented.
+
+I think that we better should see with attica devs to ask a major increase.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017901.html b/zarb-ml/mageia-dev/2012-August/017901.html new file mode 100644 index 000000000..4ac4acf4a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017901.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 2 11:59:57 CEST 2012 +

+
+ +
'Twas brillig, and Nicolas Lécureuil at 02/08/12 10:35 did gyre and gimble:
+>> A minor change is supposed to only add interfaces and be backwards
+>> compatible, that's why it is not in the soname.
+>> If there has been an ABI breakage, the major should be incremented.
+> 
+> I think that we better should see with attica devs to ask a major increase.
+
+Good idea. Thanks for volunteering :p
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017902.html b/zarb-ml/mageia-dev/2012-August/017902.html new file mode 100644 index 000000000..960187c88 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017902.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3) + + + + + + + + + +

[Mageia-dev] Library policy query: What do we do when SONAME includes both major and minor? (Re: [changelog] [RPM] cauldron core/release kdelibs4-4.9.0-2.mga3)

+ Olivier Blin + mageia at blino.org +
+ Thu Aug 2 13:46:14 CEST 2012 +

+
+ +
Pascal Terjan <pterjan at gmail.com> writes:
+
+>> So it's seems like this was done deliberately due to a ABI breakage a
+>> while ago:
+>>
+>> https://projects.kde.org/projects/kdesupport/attica/repository/revisions/ac2270b1f9c445fd39e48051b99d35d9b9693a34
+>>
+>> Now, this is an interesting point (regarding our lib policy) bumping the
+>> major for an API change and the minor for an ABI change seems kinda
+>> sensible to me. So how should we deal with that in our policy? Just use
+>> 0.4 as the "major" value here as Christiaan suggested?
+>
+> A minor change is supposed to only add interfaces and be backwards
+> compatible, that's why it is not in the soname.
+> If there has been an ABI breakage, the major should be incremented.
+
+If the ABI change occurs in a development or unstable version, it is
+normal to break it without bumping the major.
+
+Is this attica release considered stable?
+
+-- 
+Olivier Blin - blino
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017903.html b/zarb-ml/mageia-dev/2012-August/017903.html new file mode 100644 index 000000000..73946894a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017903.html @@ -0,0 +1,64 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Aug 2 16:25:15 CEST 2012 +

+
+ +
Le 02/08/2012 15:55, tv a écrit :
+> tv <tv> 3.6.0.4-2.mga3:
+> + Revision: 277879
+> - patch 1000: workaround build faillure
+> - 3.6.0 rc4
+That is not consistent with package version (3.6.0.4).
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017904.html b/zarb-ml/mageia-dev/2012-August/017904.html new file mode 100644 index 000000000..0117b048c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017904.html @@ -0,0 +1,70 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3

+ D.Morgan + dmorganec at gmail.com +
+ Thu Aug 2 16:38:36 CEST 2012 +

+
+ +
On Thu, Aug 2, 2012 at 4:25 PM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 02/08/2012 15:55, tv a écrit :
+>
+>> tv <tv> 3.6.0.4-2.mga3:
+>> + Revision: 277879
+>> - patch 1000: workaround build faillure
+>> - 3.6.0 rc4
+>
+> That is not consistent with package version (3.6.0.4).
+
+this is how libreoffice is numbered btw.
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017905.html b/zarb-ml/mageia-dev/2012-August/017905.html new file mode 100644 index 000000000..5a5632ab4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017905.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 2 16:44:14 CEST 2012 +

+
+ +
On 2 August 2012 16:25, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>> tv <tv> 3.6.0.4-2.mga3:
+>> + Revision: 277879
+>> - patch 1000: workaround build faillure
+>> - 3.6.0 rc4
+>
+> That is not consistent with package version (3.6.0.4).
+
+Be my guest, fee free to complain upstream:
+http://www.mail-archive.com/libreoffice@lists.freedesktop.org/msg35878.html
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017906.html b/zarb-ml/mageia-dev/2012-August/017906.html new file mode 100644 index 000000000..47874a6e8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017906.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] Weird boost subpackage (lib64 in i586) + + + + + + + + + +

[Mageia-dev] Weird boost subpackage (lib64 in i586)

+ n54 at gmx.com + n54 at gmx.com +
+ Thu Aug 2 19:26:40 CEST 2012 +

+
+ +
OK, Funda was quicker.. I was to busy to finish it immediately.
+
+----- Original Message -----
+From: Thomas Spuhler
+Sent: 07/26/12 04:07 PM
+To: Mageia development mailing-list
+Subject: Re: [Mageia-dev] Weird boost subpackage (lib64 in i586)
+
+ On Wednesday, July 25, 2012 05:13:37 PM n54 at gmx.com wrote: > ----- Original Message ----- > From: Thomas Spuhler > Sent: 07/25/12 06:06 AM > To: Mageia development mailing-list > Subject: Re: [Mageia-dev] Weird boost subpackage (lib64 in i586) > > BTW, don't use cmake for build, it will not :) -- Best regards Thomas > Spuhler Hi! > > I am building the newest Boost with the upstream builder.. but I need some > time to investigate closer all files & subpackages. Please be patient. > > kamil You will also need to patch the xtime.hpp file There is a "}" at almost the end that shouldn't be there -- Best regards Thomas Spuhler
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120802/e28a6e81/attachment.html>
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017907.html b/zarb-ml/mageia-dev/2012-August/017907.html new file mode 100644 index 000000000..4f0cbfe00 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017907.html @@ -0,0 +1,67 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release drakx-installer-stage2-14.32-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release drakx-installer-stage2-14.32-2.mga3.nonfree

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 2 21:58:08 CEST 2012 +

+
+ +
On 2 August 2012 21:22, kamil <buildsystem-daemon at mageia.org> wrote:
+> kamil <kamil> 14.32-2.mga3:
+> + Revision: 277994
+> - rebuild against new drakx-installer-help v. 3.0
+
+Err why a nonfree build?
+This is useless...
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017908.html b/zarb-ml/mageia-dev/2012-August/017908.html new file mode 100644 index 000000000..0cbac6276 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017908.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 3 01:23:13 CEST 2012 +

+
+ +
On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> OK, so the packages have now all been uploaded.
+>
+> You should see several packages now that you cannot install on Cauldron.
+> This is intended behaviour.
+>
+> Here is how to update your cauldron systems:
+>
+>  1. Run "urpmi --auto-update" install everything that can be installed.
+>  2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
+> sure (it may have been excluded in the --auto-update if it was in a
+> transaction with other packages that could not be installed).
+>  3. Ensure that you do not have zapata or dpkg installed (rpm -e zapata;
+> rpm -e dpkg)
+>  4. Generate a new initrd and include the conversion script: dracut -f
+> -a convertfs
+>  5. If you have /usr on a separate partition
+>      - Ensure there is enough free space to hold /bin, /sbin, /lib and
+> /lib64 content.
+>      - If your /usr is mounted readonly, change your /etc/fstab to mount
+> it rw.
+>  6. Reboot.
+>  7. At the bootloader prompt, edit the command line and append: "rw
+> rd.convertfs" (without the quotes) to your command line and then boot.
+>
+> That should be all that is needed :)
+
+How to update a chroot?
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017909.html b/zarb-ml/mageia-dev/2012-August/017909.html new file mode 100644 index 000000000..4ad9f4e00 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017909.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 3 01:40:06 CEST 2012 +

+
+ +
On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>> OK, so the packages have now all been uploaded.
+>>
+>> You should see several packages now that you cannot install on Cauldron.
+>> This is intended behaviour.
+>>
+>> Here is how to update your cauldron systems:
+>>
+>>  1. Run "urpmi --auto-update" install everything that can be installed.
+>>  2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
+>> sure (it may have been excluded in the --auto-update if it was in a
+>> transaction with other packages that could not be installed).
+>>  3. Ensure that you do not have zapata or dpkg installed (rpm -e zapata;
+>> rpm -e dpkg)
+>>  4. Generate a new initrd and include the conversion script: dracut -f
+>> -a convertfs
+>>  5. If you have /usr on a separate partition
+>>      - Ensure there is enough free space to hold /bin, /sbin, /lib and
+>> /lib64 content.
+>>      - If your /usr is mounted readonly, change your /etc/fstab to mount
+>> it rw.
+>>  6. Reboot.
+>>  7. At the bootloader prompt, edit the command line and append: "rw
+>> rd.convertfs" (without the quotes) to your command line and then boot.
+>>
+>> That should be all that is needed :)
+>
+> How to update a chroot?
+
+Answering to myself:
+
+chroot $chroot urpmi dracut
+$chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
+
+That did the conversion, but I still can't update, probably because my
+rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
+it before the conversion (it pulls filesystem).
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017910.html b/zarb-ml/mageia-dev/2012-August/017910.html new file mode 100644 index 000000000..c3883017f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017910.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Fri Aug 3 05:53:08 CEST 2012 +

+
+ +
* Pascal Terjan (pterjan at gmail.com) wrote:
+> On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+> > On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> >
+> > How to update a chroot?
+> 
+> Answering to myself:
+> 
+> chroot $chroot urpmi dracut
+> $chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
+> 
+> That did the conversion, but I still can't update, probably because my
+> rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
+> it before the conversion (it pulls filesystem).
+
+Search the thread "My feeeling about the rpmlib(X-CheckUnifiedSystemdir)
+dependency" on this list.
+
+You have first to update rpm using the one in mga2/update_testing.
+
+But indeed you can have a migrated fs but just not the rpm.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120803/d25130bf/attachment-0001.asc>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017911.html b/zarb-ml/mageia-dev/2012-August/017911.html new file mode 100644 index 000000000..1574bdd6b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017911.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release drakx-installer-stage2-14.32-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release drakx-installer-stage2-14.32-2.mga3.nonfree

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 3 10:10:13 CEST 2012 +

+
+ +
On 2 August 2012 21:58, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>> kamil <kamil> 14.32-2.mga3:
+>> + Revision: 277994
+>> - rebuild against new drakx-installer-help v. 3.0
+>
+> Err why a nonfree build?
+> This is useless...
+
+Can sysadmin remove the nonfree package for drakx-installer-stage2?
+Thx
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017912.html b/zarb-ml/mageia-dev/2012-August/017912.html new file mode 100644 index 000000000..9509475b3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017912.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release drakx-installer-stage2-14.32-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release drakx-installer-stage2-14.32-2.mga3.nonfree

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Aug 3 11:16:50 CEST 2012 +

+
+ +
'Twas brillig, and Thierry Vignaud at 03/08/12 09:10 did gyre and gimble:
+> On 2 August 2012 21:58, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>> kamil <kamil> 14.32-2.mga3:
+>>> + Revision: 277994
+>>> - rebuild against new drakx-installer-help v. 3.0
+>>
+>> Err why a nonfree build?
+>> This is useless...
+> 
+> Can sysadmin remove the nonfree package for drakx-installer-stage2?
+
+Think I've done the necessary to do this.
+
+(move the rpms + debug rpms to ~schedbot/old/ and run the hdlist update
+script for cauldron)
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017913.html b/zarb-ml/mageia-dev/2012-August/017913.html new file mode 100644 index 000000000..837051b49 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017913.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] db5.3 rebuilds still needed + + + + + + + + + +

[Mageia-dev] db5.3 rebuilds still needed

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri Aug 3 10:22:24 CEST 2012 +

+
+ +
On Thursday, 2 August 2012 01:34:17 Charles A Edwards wrote:
+> The following is a list of the apps which still require
+> libdb-5.2.so()/(64bit) that need a rebuild for db5.3
+> 
+> apr-util-dbm-db
+> c-icap-client
+> c-icap-modules
+> c-icap-modules-extra
+> cyrus-imapd
+> cyrus-imapd-murder
+> cyrus-imapd-nntp
+> cyrus-imapd-utils
+> cyrus-sasl
+> dsniff
+> evolution-data-server
+> evolution-exchange
+> evolution-exchange
+> heimdal-libs
+> hotkeys
+> inn
+> iproute2
+> lib64ebackend1.2_4
+> libreoffice-core
+> libreoffice-core
+> mutt
+> mutt-utf8
+> netatalk
+> ocaml-dbm
+> ocaml-ocsigenserver
+> openldap-servers
+> pam_abl
+> perl
+> perl-BDB
+> perl-BerkeleyDB
+> perl-Cyrus
+> perl-DB_File
+> php-dba
+> poedit
+> python
+> ruby-bdb
+> satsolver-demo
+> satsolver-tools
+> sendmail
+> squid
+> squidguard
+> 
+> Warning: If you have any of the above installed and have task-obsolete
+> installed it Will remove the above listed apps.
+
+Why? Isn't that a bit premature? Especially considering it seems almost 
+everyone will have perl and task-obsolete (I didn't ask for it, and I have 
+it). IOW, this will break any systems where users aren't looking carefully.
+
+Regards,
+Buchan
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120803/dddb47be/attachment.html>
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017914.html b/zarb-ml/mageia-dev/2012-August/017914.html new file mode 100644 index 000000000..0f3ba876a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017914.html @@ -0,0 +1,113 @@ + + + + [Mageia-dev] db5.3 rebuilds still needed + + + + + + + + + +

[Mageia-dev] db5.3 rebuilds still needed

+ Buchan Milne + bgmilne at zarb.org +
+ Fri Aug 3 11:18:09 CEST 2012 +

+
+ +
On Thursday, 2 August 2012 01:34:17 Charles A Edwards wrote:
+> The following is a list of the apps which still require
+> libdb-5.2.so()/(64bit) that need a rebuild for db5.3
+> 
+> apr-util-dbm-db
+> c-icap-client
+> c-icap-modules
+> c-icap-modules-extra
+> cyrus-imapd
+> cyrus-imapd-murder
+> cyrus-imapd-nntp
+> cyrus-imapd-utils
+> cyrus-sasl
+> dsniff
+> evolution-data-server
+> evolution-exchange
+> evolution-exchange
+> heimdal-libs
+> hotkeys
+> inn
+> iproute2
+> lib64ebackend1.2_4
+> libreoffice-core
+> libreoffice-core
+> mutt
+> mutt-utf8
+> netatalk
+> ocaml-dbm
+> ocaml-ocsigenserver
+> openldap-servers
+> pam_abl
+> perl
+> perl-BDB
+> perl-BerkeleyDB
+> perl-Cyrus
+> perl-DB_File
+> php-dba
+> poedit
+> python
+> ruby-bdb
+> satsolver-demo
+> satsolver-tools
+> sendmail
+> squid
+> squidguard
+> 
+> Warning: If you have any of the above installed and have task-obsolete
+> installed it Will remove the above listed apps.
+
+Why? Isn't that a bit premature? Especially considering it seems almost 
+everyone will have perl and task-obsolete (I didn't ask for it, and I have 
+it). IOW, this will break any systems where users aren't looking carefully.
+
+Regards,
+Buchan
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120803/96782a9f/attachment-0001.html>
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017915.html b/zarb-ml/mageia-dev/2012-August/017915.html new file mode 100644 index 000000000..f53de5833 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017915.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Buchan Milne + bgmilne at zarb.org +
+ Fri Aug 3 11:18:18 CEST 2012 +

+
+ +
On Wednesday, 1 August 2012 05:29:55 fwang wrote:
+
+> fwang <fwang> 3-21.mga3:
+> + Revision: 277136
+> - obsolete db5.2 in favour of db5.3
+
+Funda,
+
+Before you push a change like this, you should ensure you aren't going to 
+break people's machines and make cauldron uninstallable.
+
+Regards,
+Buchan
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120803/5753b400/attachment.html>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017916.html b/zarb-ml/mageia-dev/2012-August/017916.html new file mode 100644 index 000000000..e9f2c638d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017916.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Buchan Milne + bgmilne at staff.telkomsa.net +
+ Fri Aug 3 10:30:21 CEST 2012 +

+
+ +
On Wednesday, 1 August 2012 05:29:55 fwang wrote:
+
+> fwang <fwang> 3-21.mga3:
+> + Revision: 277136
+> - obsolete db5.2 in favour of db5.3
+
+Funda,
+
+Before you push a change like this, you should ensure you aren't going to 
+break people's machines and make cauldron uninstallable.
+
+Regards,
+Buchan
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120803/b97ce171/attachment.html>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017917.html b/zarb-ml/mageia-dev/2012-August/017917.html new file mode 100644 index 000000000..fb65f53ff --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017917.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Aug 3 12:15:55 CEST 2012 +

+
+ +
'Twas brillig, and Pascal Terjan at 03/08/12 00:40 did gyre and gimble:
+> On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+>> On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>> OK, so the packages have now all been uploaded.
+>>>
+>>> You should see several packages now that you cannot install on Cauldron.
+>>> This is intended behaviour.
+>>>
+>>> Here is how to update your cauldron systems:
+>>>
+>>>  1. Run "urpmi --auto-update" install everything that can be installed.
+>>>  2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
+>>> sure (it may have been excluded in the --auto-update if it was in a
+>>> transaction with other packages that could not be installed).
+>>>  3. Ensure that you do not have zapata or dpkg installed (rpm -e zapata;
+>>> rpm -e dpkg)
+>>>  4. Generate a new initrd and include the conversion script: dracut -f
+>>> -a convertfs
+>>>  5. If you have /usr on a separate partition
+>>>      - Ensure there is enough free space to hold /bin, /sbin, /lib and
+>>> /lib64 content.
+>>>      - If your /usr is mounted readonly, change your /etc/fstab to mount
+>>> it rw.
+>>>  6. Reboot.
+>>>  7. At the bootloader prompt, edit the command line and append: "rw
+>>> rd.convertfs" (without the quotes) to your command line and then boot.
+>>>
+>>> That should be all that is needed :)
+>>
+>> How to update a chroot?
+> 
+> Answering to myself:
+> 
+> chroot $chroot urpmi dracut
+> $chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
+> 
+> That did the conversion, but I still can't update, probably because my
+> rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
+> it before the conversion (it pulls filesystem).
+
+Yeah in this case if the conversion is done, I'd just recommend
+installing filesystem --nodeps and the rest should flow. It's not ideal
+certainly, but there is still time to polish this a bit before upgraders
+get hit by this (and as there will be updated rpm packages in the stable
+releases, it should mitigate this specific problem, but we should still
+see if we can do things better)
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017918.html b/zarb-ml/mageia-dev/2012-August/017918.html new file mode 100644 index 000000000..00ba1db4a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017918.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Fri Aug 3 12:27:37 CEST 2012 +

+
+ +
On Fri, 3 Aug 2012, Colin Guthrie wrote:
+
+> 'Twas brillig, and Pascal Terjan at 03/08/12 00:40 did gyre and gimble:
+>> On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+>>> On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>>> OK, so the packages have now all been uploaded.
+>>>>
+>>>> You should see several packages now that you cannot install on Cauldron.
+>>>> This is intended behaviour.
+>>>>
+>>>> Here is how to update your cauldron systems:
+>>>>
+>>>>  1. Run "urpmi --auto-update" install everything that can be installed.
+>>>>  2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
+>>>> sure (it may have been excluded in the --auto-update if it was in a
+>>>> transaction with other packages that could not be installed).
+>>>>  3. Ensure that you do not have zapata or dpkg installed (rpm -e zapata;
+>>>> rpm -e dpkg)
+>>>>  4. Generate a new initrd and include the conversion script: dracut -f
+>>>> -a convertfs
+>>>>  5. If you have /usr on a separate partition
+>>>>      - Ensure there is enough free space to hold /bin, /sbin, /lib and
+>>>> /lib64 content.
+>>>>      - If your /usr is mounted readonly, change your /etc/fstab to mount
+>>>> it rw.
+>>>>  6. Reboot.
+>>>>  7. At the bootloader prompt, edit the command line and append: "rw
+>>>> rd.convertfs" (without the quotes) to your command line and then boot.
+>>>>
+>>>> That should be all that is needed :)
+>>>
+>>> How to update a chroot?
+>>
+>> Answering to myself:
+>>
+>> chroot $chroot urpmi dracut
+>> $chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
+>>
+>> That did the conversion, but I still can't update, probably because my
+>> rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
+>> it before the conversion (it pulls filesystem).
+>
+> Yeah in this case if the conversion is done, I'd just recommend
+> installing filesystem --nodeps and the rest should flow. It's not ideal
+> certainly, but there is still time to polish this a bit before upgraders
+> get hit by this (and as there will be updated rpm packages in the stable
+> releases, it should mitigate this specific problem, but we should still
+> see if we can do things better)
+
+Polish this a bit? It is not at all ready, and as I said earlier rpmlib is 
+broken. Please don't upload broken rpm packages to stable releases.
+
+Maybe the instructions should be:
+   - install dracut and kernel-desktop-latest from mga3
+   - reboot, make sure the "usrmove filesystem update"
+     kernel entry is chosen in the bootloader
+   - upgrade to mga3 as usual
+
+But that means a lot of things are still missing:
+   - dracut automatically including the conversion script
+     (only when needed?)
+   - automatic generation of the bootloader entry mentioned above
+   - removal of this bootloader entry after conversion
+
+
+     Christiaan
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017919.html b/zarb-ml/mageia-dev/2012-August/017919.html new file mode 100644 index 000000000..6780b6ba4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017919.html @@ -0,0 +1,139 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 3 12:32:24 CEST 2012 +

+
+ +
On Fri, Aug 3, 2012 at 11:27 AM, Christiaan Welvaart
+<cjw at daneel.dyndns.org> wrote:
+> On Fri, 3 Aug 2012, Colin Guthrie wrote:
+>
+>> 'Twas brillig, and Pascal Terjan at 03/08/12 00:40 did gyre and gimble:
+>>>
+>>> On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+>>>>
+>>>> On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie>
+>>>> wrote:
+>>>>>
+>>>>> OK, so the packages have now all been uploaded.
+>>>>>
+>>>>> You should see several packages now that you cannot install on
+>>>>> Cauldron.
+>>>>> This is intended behaviour.
+>>>>>
+>>>>> Here is how to update your cauldron systems:
+>>>>>
+>>>>>  1. Run "urpmi --auto-update" install everything that can be installed.
+>>>>>  2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
+>>>>> sure (it may have been excluded in the --auto-update if it was in a
+>>>>> transaction with other packages that could not be installed).
+>>>>>  3. Ensure that you do not have zapata or dpkg installed (rpm -e
+>>>>> zapata;
+>>>>> rpm -e dpkg)
+>>>>>  4. Generate a new initrd and include the conversion script: dracut -f
+>>>>> -a convertfs
+>>>>>  5. If you have /usr on a separate partition
+>>>>>      - Ensure there is enough free space to hold /bin, /sbin, /lib and
+>>>>> /lib64 content.
+>>>>>      - If your /usr is mounted readonly, change your /etc/fstab to
+>>>>> mount
+>>>>> it rw.
+>>>>>  6. Reboot.
+>>>>>  7. At the bootloader prompt, edit the command line and append: "rw
+>>>>> rd.convertfs" (without the quotes) to your command line and then boot.
+>>>>>
+>>>>> That should be all that is needed :)
+>>>>
+>>>>
+>>>> How to update a chroot?
+>>>
+>>>
+>>> Answering to myself:
+>>>
+>>> chroot $chroot urpmi dracut
+>>> $chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
+>>>
+>>> That did the conversion, but I still can't update, probably because my
+>>> rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
+>>> it before the conversion (it pulls filesystem).
+>>
+>>
+>> Yeah in this case if the conversion is done, I'd just recommend
+>> installing filesystem --nodeps and the rest should flow. It's not ideal
+>> certainly, but there is still time to polish this a bit before upgraders
+>> get hit by this (and as there will be updated rpm packages in the stable
+>> releases, it should mitigate this specific problem, but we should still
+>> see if we can do things better)
+>
+>
+> Polish this a bit? It is not at all ready, and as I said earlier rpmlib is
+> broken. Please don't upload broken rpm packages to stable releases.
+>
+> Maybe the instructions should be:
+>   - install dracut and kernel-desktop-latest from mga3
+>   - reboot, make sure the "usrmove filesystem update"
+>     kernel entry is chosen in the bootloader
+>   - upgrade to mga3 as usual
+>
+> But that means a lot of things are still missing:
+>   - dracut automatically including the conversion script
+>     (only when needed?)
+>   - automatic generation of the bootloader entry mentioned above
+
+I would vote to also force the reboot into this entry at next boot
+
+>   - removal of this bootloader entry after conversion
+>
+>
+>     Christiaan
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017920.html b/zarb-ml/mageia-dev/2012-August/017920.html new file mode 100644 index 000000000..fa9323de6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017920.html @@ -0,0 +1,67 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release mesa-8.1.0-0.git20120802.1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release mesa-8.1.0-0.git20120802.1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 3 12:44:21 CEST 2012 +

+
+ +
On 3 August 2012 10:47, blino <buildsystem-daemon at mageia.org> wrote:
+> blino <blino> 8.1.0-0.git20120802.1.mga3:
+> + Revision: 278175
+> - update to snapshot from 20120802
+> - remove unneeded gl.pc patch now that osmesa.pc is in drivers/osmesa
+
+You forgot nonfree build..
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017921.html b/zarb-ml/mageia-dev/2012-August/017921.html new file mode 100644 index 000000000..c3d55ea6b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017921.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-21.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 3 13:08:02 CEST 2012 +

+
+ +
On 3 August 2012 11:18, Buchan Milne <bgmilne at zarb.org> wrote:
+>> - obsolete db5.2 in favour of db5.3
+>
+> Before you push a change like this, you should ensure you aren't going to
+> break people's machines and make cauldron uninstallable.
+
+Well, when Funda did, there were only 2 remaining packages build against db-5.2:
+libreoffice & evolution-exchange (precisely thanks to Funda's work!).
+That does NOT prevent cauldron to install at all.
+
+What's more, only evolution-exchange needs fixing now.
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017922.html b/zarb-ml/mageia-dev/2012-August/017922.html new file mode 100644 index 000000000..03471a2de --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017922.html @@ -0,0 +1,65 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release firefox-beta-15.0-0.b3.1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release firefox-beta-15.0-0.b3.1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 3 13:37:27 CEST 2012 +

+
+ +
On 3 August 2012 13:33, tv <buildsystem-daemon at mageia.org> wrote:
+> tv <tv> 15.0-0.b3.1.mga3:
+> + Revision: 278209
+> - new release
+
+now we only need to add opus support :-)
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017923.html b/zarb-ml/mageia-dev/2012-August/017923.html new file mode 100644 index 000000000..c829801b4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017923.html @@ -0,0 +1,65 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release mkinitrd-6.0.93-30.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release mkinitrd-6.0.93-30.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 3 14:18:58 CEST 2012 +

+
+ +
On 3 August 2012 13:50, fwang <buildsystem-daemon at mageia.org> wrote:
+> fwang <fwang> 6.0.93-30.mga3:
+> + Revision: 278243
+> - rebuild for new parted
+
+Humm, I think it's time to let dracut obsolete mkinitrd anyway...
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017924.html b/zarb-ml/mageia-dev/2012-August/017924.html new file mode 100644 index 000000000..7cb9d471b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017924.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release mesa-8.1.0-0.git20120802.1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release mesa-8.1.0-0.git20120802.1.mga3

+ Olivier Blin + mageia at blino.org +
+ Fri Aug 3 14:20:55 CEST 2012 +

+
+ +
Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+
+> On 3 August 2012 10:47, blino <buildsystem-daemon at mageia.org> wrote:
+>> blino <blino> 8.1.0-0.git20120802.1.mga3:
+>> + Revision: 278175
+>> - update to snapshot from 20120802
+>> - remove unneeded gl.pc patch now that osmesa.pc is in drivers/osmesa
+>
+> You forgot nonfree build..
+
+I did not, I will do it when mesa core/release is ok.
+
+We should really find a solution to automate double upload to core and
+non-free...
+
+-- 
+Olivier Blin - blino
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017925.html b/zarb-ml/mageia-dev/2012-August/017925.html new file mode 100644 index 000000000..65896a87f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017925.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release mkinitrd-6.0.93-30.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release mkinitrd-6.0.93-30.mga3

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Aug 3 14:43:52 CEST 2012 +

+
+ +
'Twas brillig, and Thierry Vignaud at 03/08/12 13:18 did gyre and gimble:
+> On 3 August 2012 13:50, fwang <buildsystem-daemon at mageia.org> wrote:
+>> fwang <fwang> 6.0.93-30.mga3:
+>> + Revision: 278243
+>> - rebuild for new parted
+> 
+> Humm, I think it's time to let dracut obsolete mkinitrd anyway...
+
+Yeah, I was waiting for the usrmove before pushing any major changes to
+the dracut package but the time is now right I think.
+
+I have the latest dracut package (023) so I'll just do a bit of testing
+locally first (not rebooted yet) to make sure all is vaguely well and
+then will push it and kill off mkinitrd in the process.
+
+Col
+
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017926.html b/zarb-ml/mageia-dev/2012-August/017926.html new file mode 100644 index 000000000..5987eb018 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017926.html @@ -0,0 +1,165 @@ + + + + [Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions + + + + + + + + + +

[Mageia-dev] ANNOUNCE: The /usr move cometh! <---- Instructions

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Aug 3 14:57:51 CEST 2012 +

+
+ +
'Twas brillig, and Pascal Terjan at 03/08/12 11:32 did gyre and gimble:
+> On Fri, Aug 3, 2012 at 11:27 AM, Christiaan Welvaart
+> <cjw at daneel.dyndns.org> wrote:
+>> On Fri, 3 Aug 2012, Colin Guthrie wrote:
+>>
+>>> 'Twas brillig, and Pascal Terjan at 03/08/12 00:40 did gyre and gimble:
+>>>>
+>>>> On Fri, Aug 3, 2012 at 12:23 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+>>>>>
+>>>>> On Sun, Jul 22, 2012 at 1:12 AM, Colin Guthrie <mageia at colin.guthr.ie>
+>>>>> wrote:
+>>>>>>
+>>>>>> OK, so the packages have now all been uploaded.
+>>>>>>
+>>>>>> You should see several packages now that you cannot install on
+>>>>>> Cauldron.
+>>>>>> This is intended behaviour.
+>>>>>>
+>>>>>> Here is how to update your cauldron systems:
+>>>>>>
+>>>>>>  1. Run "urpmi --auto-update" install everything that can be installed.
+>>>>>>  2. Ensure that latest dracut is installed. Run "urpmi dracut" to make
+>>>>>> sure (it may have been excluded in the --auto-update if it was in a
+>>>>>> transaction with other packages that could not be installed).
+>>>>>>  3. Ensure that you do not have zapata or dpkg installed (rpm -e
+>>>>>> zapata;
+>>>>>> rpm -e dpkg)
+>>>>>>  4. Generate a new initrd and include the conversion script: dracut -f
+>>>>>> -a convertfs
+>>>>>>  5. If you have /usr on a separate partition
+>>>>>>      - Ensure there is enough free space to hold /bin, /sbin, /lib and
+>>>>>> /lib64 content.
+>>>>>>      - If your /usr is mounted readonly, change your /etc/fstab to
+>>>>>> mount
+>>>>>> it rw.
+>>>>>>  6. Reboot.
+>>>>>>  7. At the bootloader prompt, edit the command line and append: "rw
+>>>>>> rd.convertfs" (without the quotes) to your command line and then boot.
+>>>>>>
+>>>>>> That should be all that is needed :)
+>>>>>
+>>>>>
+>>>>> How to update a chroot?
+>>>>
+>>>>
+>>>> Answering to myself:
+>>>>
+>>>> chroot $chroot urpmi dracut
+>>>> $chroot/usr/lib/dracut/modules.d/30convertfs/convertfs.sh $chroot
+>>>>
+>>>> That did the conversion, but I still can't update, probably because my
+>>>> rpm is too old (rpm-4.9.1.3-2.mga2) as it was not possible to update
+>>>> it before the conversion (it pulls filesystem).
+>>>
+>>>
+>>> Yeah in this case if the conversion is done, I'd just recommend
+>>> installing filesystem --nodeps and the rest should flow. It's not ideal
+>>> certainly, but there is still time to polish this a bit before upgraders
+>>> get hit by this (and as there will be updated rpm packages in the stable
+>>> releases, it should mitigate this specific problem, but we should still
+>>> see if we can do things better)
+>>
+>>
+>> Polish this a bit? It is not at all ready, and as I said earlier rpmlib is
+>> broken. Please don't upload broken rpm packages to stable releases.
+>>
+>> Maybe the instructions should be:
+>>   - install dracut and kernel-desktop-latest from mga3
+>>   - reboot, make sure the "usrmove filesystem update"
+>>     kernel entry is chosen in the bootloader
+>>   - upgrade to mga3 as usual
+>>
+>> But that means a lot of things are still missing:
+>>   - dracut automatically including the conversion script
+>>     (only when needed?)
+>>   - automatic generation of the bootloader entry mentioned above
+> 
+> I would vote to also force the reboot into this entry at next boot
+
+Yeah I was intending to have a new package that would be pushed into
+mga2 that ensures dracut is installed (as opposed to mkinitrd - not sure
+why you're suggesting kernel-desktop-latest here).
+
+This new package would take care to install an initrd and add bootloader
+entry for (probably) the newest currently installed kernel and probably
+ensure it was the default entry until the boot was complete at which
+point it would be automatically removed.
+
+TBH I'm less worried about the "broken" rpmlib issue than Christiaan.
+While I can't argue against him technically, I think practical
+pragmatism is such that it's not going to be an issue for all but a
+handful of people, in which case it's likely not worth me spending
+several days working on a more elegant and technically correct solution.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017927.html b/zarb-ml/mageia-dev/2012-August/017927.html new file mode 100644 index 000000000..113f8e960 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017927.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted

+ Olivier Blin + mageia at blino.org +
+ Fri Aug 3 22:18:16 CEST 2012 +

+
+ +
tv <buildsystem-daemon at mageia.org> writes:
+
+> Name        : mesa                         Relocations: (not relocatable)
+> Version     : 8.1.0                             Vendor: Mageia.Org
+> Release     : 0.git20120802.1.mga3.tainted   Build Date: Fri Aug  3 20:06:54 2012
+
+You forgot to upload it in core/release.
+
+-- 
+Olivier Blin - blino
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017928.html b/zarb-ml/mageia-dev/2012-August/017928.html new file mode 100644 index 000000000..c48c480ac --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017928.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release gitolite3-3.04-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release gitolite3-3.04-1.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sat Aug 4 10:57:25 CEST 2012 +

+
+ +
Le 04/08/2012 03:24, dmorgan a écrit :
+> dmorgan <dmorgan> 3.04-1.mga3:
+> + Revision: 278374
+> - imported package gitolite3
+Which should be named 'gitolite', not 'gitolite3'.
+
+-- 
+BOFH excuse #321:
+
+Scheduled global CPU outage
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017929.html b/zarb-ml/mageia-dev/2012-August/017929.html new file mode 100644 index 000000000..5d32f7d80 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017929.html @@ -0,0 +1,67 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Sat Aug 4 12:15:17 CEST 2012 +

+
+ +
On 3 August 2012 22:18, Olivier Blin <mageia at blino.org> wrote:
+>> Name        : mesa                         Relocations: (not relocatable)
+>> Version     : 8.1.0                             Vendor: Mageia.Org
+>> Release     : 0.git20120802.1.mga3.tainted   Build Date: Fri Aug  3 20:06:54 2012
+>
+> You forgot to upload it in core/release.
+
+
+B/c you already uploaded it in core/release. dumb troller
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017930.html b/zarb-ml/mageia-dev/2012-August/017930.html new file mode 100644 index 000000000..e2b08bed9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017930.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sat Aug 4 13:49:01 CEST 2012 +

+
+ +
'Twas brillig, and Olivier Blin at 03/08/12 21:18 did gyre and gimble:
+> tv <buildsystem-daemon at mageia.org> writes:
+> 
+>> Name        : mesa                         Relocations: (not relocatable)
+>> Version     : 8.1.0                             Vendor: Mageia.Org
+>> Release     : 0.git20120802.1.mga3.tainted   Build Date: Fri Aug  3 20:06:54 2012
+> 
+> You forgot to upload it in core/release.
+
+:p
+
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017931.html b/zarb-ml/mageia-dev/2012-August/017931.html new file mode 100644 index 000000000..5eeb3c5f2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017931.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] [ANN] dracut 023 now in updates_testing: Feedback wanted + + + + + + + + + +

[Mageia-dev] [ANN] dracut 023 now in updates_testing: Feedback wanted

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sat Aug 4 14:37:19 CEST 2012 +

+
+ +
Hi,
+
+There is now a new dracut in cauldron's core/updates_testing. Please do
+the following test:
+
+1. Ensure your system is fully up to date and reboot it.
+2. Install dracut from updates_testing
+3. Generate a new initrd: dracut /boot/foo.img
+4. Reboot and at the prompt edit the initrd used to be foo.img
+5. Make sure things boot as expected.
+6. Let me know if something goes horribly wrong
+
+Failing any critical failures, I'll push it into core/release next week
+sometime.
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017932.html b/zarb-ml/mageia-dev/2012-August/017932.html new file mode 100644 index 000000000..760917851 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017932.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted

+ Olivier Blin + mageia at blino.org +
+ Sat Aug 4 15:03:25 CEST 2012 +

+
+ +
Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+
+> On 3 August 2012 22:18, Olivier Blin <mageia at blino.org> wrote:
+>>> Name        : mesa                         Relocations: (not relocatable)
+>>> Version     : 8.1.0                             Vendor: Mageia.Org
+>>> Release     : 0.git20120802.1.mga3.tainted   Build Date: Fri Aug  3 20:06:54 2012
+>>
+>> You forgot to upload it in core/release.
+>
+> B/c you already uploaded it in core/release. dumb troller
+
+Yep, sorry, I saw only later that you forced upload of the previous
+release.
+
+Anyway, radeonsi can not be built together with r600 right now...
+
+-- 
+Olivier Blin - blino
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017933.html b/zarb-ml/mageia-dev/2012-August/017933.html new file mode 100644 index 000000000..2797ebeb7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017933.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] wrong action for a specific usb device + + + + + + + + + +

[Mageia-dev] wrong action for a specific usb device

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sat Aug 4 16:48:16 CEST 2012 +

+
+ +
Hello list.
+
+I can't suceed to access the content of my new shiny nikon camera SD 
+card. When pluging the camera, I saw an MTP probe attempt and failure:
+
+Aug  4 16:44:04 localhost kernel: [98204.334342] usb 8-1: new high-speed 
+USB device number 10 using ehci_hcd
+Aug  4 16:44:04 localhost kernel: [98204.449649] usb 8-1: New USB device 
+found, idVendor=04b0, idProduct=042c
+Aug  4 16:44:04 localhost kernel: [98204.449661] usb 8-1: New USB device 
+strings: Mfr=1, Product=2, SerialNumber=3
+Aug  4 16:44:04 localhost kernel: [98204.449668] usb 8-1: Product: NIKON 
+DSC D3200
+Aug  4 16:44:04 localhost kernel: [98204.449674] usb 8-1: Manufacturer: 
+NIKON
+Aug  4 16:44:04 localhost kernel: [98204.449680] usb 8-1: SerialNumber: 
+000006045584
+Aug  4 16:44:04 localhost mtp-probe: checking bus 8, device 10: 
+"/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1"
+Aug  4 16:44:04 localhost mtp-probe: bus: 8, device: 10 was not an MTP 
+device
+
+Manually loading mass-storage module doesn't help.
+
+So, what am I supposed to do here? I guess there is some udev rule to 
+fix, but I can't find which one.
+-- 
+BOFH excuse #311:
+
+transient bus protocol violation
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017934.html b/zarb-ml/mageia-dev/2012-August/017934.html new file mode 100644 index 000000000..e03f65384 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017934.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] wrong action for a specific usb device + + + + + + + + + +

[Mageia-dev] wrong action for a specific usb device

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Sat Aug 4 19:15:42 CEST 2012 +

+
+ +
On Sat, 4 Aug 2012, Guillaume Rousse wrote:
+
+> I can't suceed to access the content of my new shiny nikon camera SD card. 
+> When pluging the camera, I saw an MTP probe attempt and failure:
+>
+> Aug  4 16:44:04 localhost kernel: [98204.334342] usb 8-1: new high-speed USB 
+> device number 10 using ehci_hcd
+> Aug  4 16:44:04 localhost kernel: [98204.449649] usb 8-1: New USB device 
+> found, idVendor=04b0, idProduct=042c
+> Aug  4 16:44:04 localhost kernel: [98204.449661] usb 8-1: New USB device 
+> strings: Mfr=1, Product=2, SerialNumber=3
+> Aug  4 16:44:04 localhost kernel: [98204.449668] usb 8-1: Product: NIKON DSC 
+> D3200
+> Aug  4 16:44:04 localhost kernel: [98204.449674] usb 8-1: Manufacturer: NIKON
+> Aug  4 16:44:04 localhost kernel: [98204.449680] usb 8-1: SerialNumber: 
+> 000006045584
+> Aug  4 16:44:04 localhost mtp-probe: checking bus 8, device 10: 
+> "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-1"
+> Aug  4 16:44:04 localhost mtp-probe: bus: 8, device: 10 was not an MTP device
+>
+> Manually loading mass-storage module doesn't help.
+
+So what does gphoto say? Are you sure it acts as a usb storage device?
+
+
+     Christiaan
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017935.html b/zarb-ml/mageia-dev/2012-August/017935.html new file mode 100644 index 000000000..64644aaaf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017935.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] A new QA page for updates candidates + + + + + + + + + +

[Mageia-dev] A new QA page for updates candidates

+ Samuel Verschelde + stormi at laposte.net +
+ Sat Aug 4 20:11:40 CEST 2012 +

+
+ +
Hi,
+
+For our internal needs, I developed for QA team a new page that allows us to 
+have an overview of all current updates candidates. It simply gathers data 
+from bugzilla and formats them so that it's convenient for us.
+
+I added it as a page to Mageia App Db, for two reasons:
+- easier for me to add it to an existing project I know well, it saved me a 
+few hours.
+- I hope in the long run to be able to link packages and bug reports together 
+in madb, so I thought it was not totally irrelevant to put it in madb.
+
+Of course, nothing (but time) prevents to develop it for mageia.org, or as a 
+dynamic page in the wiki, it that's possible (is it?).
+
+The page: http://mageia.madb.org/tools/updates
+
+Of course, don't hesitate to pick an update and test it! The list has been 
+considerably reduced in the previous days.
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017936.html b/zarb-ml/mageia-dev/2012-August/017936.html new file mode 100644 index 000000000..6107d77f5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017936.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] A new QA page for updates candidates + + + + + + + + + +

[Mageia-dev] A new QA page for updates candidates

+ Thomas Spuhler + thomas at btspuhler.com +
+ Sat Aug 4 20:51:18 CEST 2012 +

+
+ +
On Saturday, August 04, 2012 11:11:40 AM Samuel Verschelde wrote:
+> Hi,
+> 
+> For our internal needs, I developed for QA team a new page that allows us
+> to have an overview of all current updates candidates. It simply gathers
+> data from bugzilla and formats them so that it's convenient for us.
+> 
+> I added it as a page to Mageia App Db, for two reasons:
+> - easier for me to add it to an existing project I know well, it saved me a
+> few hours.
+> - I hope in the long run to be able to link packages and bug reports
+> together in madb, so I thought it was not totally irrelevant to put it in
+> madb.
+> 
+> Of course, nothing (but time) prevents to develop it for mageia.org, or as
+> a dynamic page in the wiki, it that's possible (is it?).
+> 
+> The page: http://mageia.madb.org/tools/updates
+> 
+> Of course, don't hesitate to pick an update and test it! The list has been
+> considerably reduced in the previous days.
+> 
+> Best regards
+> 
+> Samuel Verschelde
+Thanks for doing this.
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017937.html b/zarb-ml/mageia-dev/2012-August/017937.html new file mode 100644 index 000000000..20e611c5f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017937.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Free software needing non-free data + + + + + + + + + +

[Mageia-dev] Free software needing non-free data

+ Samuel Verschelde + stormi at laposte.net +
+ Sat Aug 4 22:51:05 CEST 2012 +

+
+ +
Hi,
+
+I've reread our policy, but it's unclear to me where to put free software that 
+can't work (in a useful way for a user) without non-free data.
+
+We currently have a mix of situations (sometimes in core, sometimes in 
+nonfree), which shows that it's not totally clear to other packagers either.
+
+I see 2 different situations:
+
+--- redistributable data ---
+Data is put in nonfree media, so the binaries are put in nonfree too because 
+we can't put a requires from core to nonfree
+
+Example : warsow and warsow-data
+
+--- non redistributable data ---
+Here two different policies seem to be applied, depending on the packager:
+1°) put the binaries in core, since they are free
+2°) put the binaries in non-free, since they are useless without non-free data 
+(extrapolation of the "self-contained" rule of core)
+
+And there are grayzone cases, such as:
+- prboom (free) which is meant to work with Doom's wads (nonfree) but can also 
+work with freedoom (free), so it's in core even if we apply 2°
+- ioquake3, which is an engine that can be used by other free games (although 
+I think they often ship their own modified version), so it's in core even if we 
+apply 2°
+
+
+So, can we reach a consensus about something we could write in the policy so 
+that there's no more confusion, and move the relevant packages from nonfree to 
+core or core to nonfree?
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017938.html b/zarb-ml/mageia-dev/2012-August/017938.html new file mode 100644 index 000000000..8dea11b4d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017938.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] Free software needing non-free data + + + + + + + + + +

[Mageia-dev] Free software needing non-free data

+ Johnny A. Solbu + cooker at solbu.net +
+ Sat Aug 4 23:41:24 CEST 2012 +

+
+ +
On Saturday 04 August 2012 22:51, Samuel Verschelde wrote:
+> And there are grayzone cases, such as:
+> - prboom (free) which is meant to work with Doom's wads (nonfree) but can also 
+> work with freedoom (free), so it's in core even if we apply 2°
+
+The way I see it, if it works without non-free data, then it is free software. Just because something /works/ with non-free software is no excuse to put it in non-free.
+There's a difference in requires non-free data and working /best/ with non-free data. If it requires non-free data, then it belongs in non-free.
+
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120804/3d2eac84/attachment-0001.asc>
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017939.html b/zarb-ml/mageia-dev/2012-August/017939.html new file mode 100644 index 000000000..12e788e1e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017939.html @@ -0,0 +1,67 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron tainted/release mesa-8.1.0-0.git20120802.1.mga3.tainted

+ Manuel Hiebel + manuel.mageia at hiebel.eu +
+ Sun Aug 5 00:52:36 CEST 2012 +

+
+ +
Le 03/08/2012 22:18, Olivier Blin a écrit :
+> tv<buildsystem-daemon at mageia.org>  writes:
+>
+>> Name        : mesa                         Relocations: (not relocatable)
+>> Version     : 8.1.0                             Vendor: Mageia.Org
+>> Release     : 0.git20120802.1.mga3.tainted   Build Date: Fri Aug  3 20:06:54 2012
+> You forgot to upload it in core/release.
+>
+And nobody for fixing the same on mga2 ? (two different version between 
+tainted and core)
+https://bugs.mageia.org/show_bug.cgi?id=6674
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017940.html b/zarb-ml/mageia-dev/2012-August/017940.html new file mode 100644 index 000000000..ea70abc3e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017940.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] Free software needing non-free data + + + + + + + + + +

[Mageia-dev] Free software needing non-free data

+ AL13N + alien at rmail.be +
+ Sun Aug 5 16:09:14 CEST 2012 +

+
+ +
> Hi,
+>
+> I've reread our policy, but it's unclear to me where to put free software
+> that
+> can't work (in a useful way for a user) without non-free data.
+>
+> We currently have a mix of situations (sometimes in core, sometimes in
+> nonfree), which shows that it's not totally clear to other packagers
+> either.
+>
+> I see 2 different situations:
+>
+> --- redistributable data ---
+> Data is put in nonfree media, so the binaries are put in nonfree too
+> because
+> we can't put a requires from core to nonfree
+>
+> Example : warsow and warsow-data
+>
+> --- non redistributable data ---
+> Here two different policies seem to be applied, depending on the packager:
+> 1°) put the binaries in core, since they are free
+> 2°) put the binaries in non-free, since they are useless without non-free
+> data
+> (extrapolation of the "self-contained" rule of core)
+>
+> And there are grayzone cases, such as:
+> - prboom (free) which is meant to work with Doom's wads (nonfree) but can
+> also
+> work with freedoom (free), so it's in core even if we apply 2°
+> - ioquake3, which is an engine that can be used by other free games
+> (although
+> I think they often ship their own modified version), so it's in core even
+> if we
+> apply 2°
+>
+
+
+there's also eduke32, which is free; but, there are some grayzones.
+
+in theory, you need Duke Nukem 3D CD.
+
+but there's also mods for it and some work with duke3D files.
+
+there's also a duke3D-hrp (high resolution content) which needs duke3D cd
+to work.
+
+then there's also the demo, which is shareware (allthough redistributable
+status is unclear), and should be possible to use this without the CD.
+
+It's definately possible to use eduke32 with your own content. and might
+be possible to run some of the mods without the duke nukem CD. (allthough
+i haven't doublechecked).
+
+for this, i would like to have the eduke32-hrp (400MB) in non-free because
+it requires non-redistributable data, but the eduke32 in free. because
+it's free. even if you make your own content or find some mods that are
+free and have no requirement on non-free content.
+
+i would add a message that this free program can/might depend on non-free
+or even non-distributable content. so that if nonfree is disabled, the
+person would be notified and the suggests be invalidated (not require)
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017941.html b/zarb-ml/mageia-dev/2012-August/017941.html new file mode 100644 index 000000000..9f1c4d203 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017941.html @@ -0,0 +1,128 @@ + + + + [Mageia-dev] Free software needing non-free data + + + + + + + + + +

[Mageia-dev] Free software needing non-free data

+ andre999 + andre999mga at laposte.net +
+ Sun Aug 5 17:25:12 CEST 2012 +

+
+ +
Samuel Verschelde a écrit :
+> Hi,
+>
+> I've reread our policy, but it's unclear to me where to put free software that
+> can't work (in a useful way for a user) without non-free data.
+>
+> We currently have a mix of situations (sometimes in core, sometimes in
+> nonfree), which shows that it's not totally clear to other packagers either.
+>
+> I see 2 different situations:
+>
+> --- redistributable data ---
+> Data is put in nonfree media, so the binaries are put in nonfree too because
+> we can't put a requires from core to nonfree
+>
+> Example : warsow and warsow-data
+>
+> --- non redistributable data ---
+> Here two different policies seem to be applied, depending on the packager:
+> 1°) put the binaries in core, since they are free
+> 2°) put the binaries in non-free, since they are useless without non-free data
+> (extrapolation of the "self-contained" rule of core)
+>
+> And there are grayzone cases, such as:
+> - prboom (free) which is meant to work with Doom's wads (nonfree) but can also
+> work with freedoom (free), so it's in core even if we apply 2°
+> - ioquake3, which is an engine that can be used by other free games (although
+> I think they often ship their own modified version), so it's in core even if we
+> apply 2°
+>
+>
+> So, can we reach a consensus about something we could write in the policy so
+> that there's no more confusion, and move the relevant packages from nonfree to
+> core or core to nonfree?
+>    
+
+- If a package has any dependancies (requires or suggests) in nonfree, 
+it should go into nonfree.
+Why I include suggests is because in the rpmdrake, the main graphical 
+interface, suggests are treated the same as requires.  And in urpmi, 
+suggests are installed by default.  If the user were queried for each 
+suggest, I might change my mind about suggests.
+
+- If the package cannot be run without non-free data, I would also put 
+it in nonfree, since it would be useless without non-free data.  
+Following the principal of core not requiring non-free.
+
+However if free data is readily available (or creatable), even if the 
+default data is non-free, I would put the package into core. (without 
+the default non-free data.)
+This I would do even if the default non-free data were redistributable.  
+I don't see a problem with putting redistributable non-free data in 
+nonfree, with a comment to that effect in the free core package, as long 
+as free alternative data exists.  (But no link to such non-free data 
+from core.)
+In such a case, I would prefer to install the alternate free data with 
+the main package, or at least instructions detailing how to create or 
+otherwise obtain it.
+> Best regards
+>
+> Samuel Verschelde
+>
+>    
+My 2 cents :)
+
+-- 
+André
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017942.html b/zarb-ml/mageia-dev/2012-August/017942.html new file mode 100644 index 000000000..4e24eb522 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017942.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] Crashes with Firefox 13 + Flash (inc. fix) + + + + + + + + + +

[Mageia-dev] Crashes with Firefox 13 + Flash (inc. fix)

+ Olivier Blin + mageia at blino.org +
+ Sun Aug 5 17:35:13 CEST 2012 +

+
+ +
Colin Guthrie <mageia at colin.guthr.ie> writes:
+
+> Hi,
+>
+> Just in case others are experiencing this, I've noticed recently that
+> since Cauldron went to Firefox 13 I've seen frequent crashes, most often
+> when interacting with Flash.
+
+For the record, this is https://bugs.mageia.org/show_bug.cgi?id=6299
+
+> After getting annoyed enough about it today, I did some digging, got a
+> (rubbish but mildly usable) backtrace and managed to do some educated
+> Googling.
+>
+> I ended up finding this:
+> https://bugzilla.novell.com/show_bug.cgi?id=759123
+>
+> The suggested solution of installing lib64proxy-webkit and removing
+> lib64proxy-mozjs did the trick. Firefox has been much more stable.
+>
+> Just thought I'd share this with others should they also be suffering
+> the same problem.
+>
+> Depending on how widespread the problem is, we should maybe consider
+> adding conflicts to firefox package on lib*proxy-mozjs.
+
+I am not sure this fix is good engouh, any lib used by firefox pulling
+mozjs will make the problem pop again.
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017943.html b/zarb-ml/mageia-dev/2012-August/017943.html new file mode 100644 index 000000000..162a7935f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017943.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Crashes with Firefox 13 + Flash (inc. fix) + + + + + + + + + +

[Mageia-dev] Crashes with Firefox 13 + Flash (inc. fix)

+ Digigold + digigold808 at gmail.com +
+ Sun Aug 5 18:30:33 CEST 2012 +

+
+ +
>> Hi,
+>>
+>> Just in case others are experiencing this, I've noticed recently that
+>> since Cauldron went to Firefox 13 I've seen frequent crashes, most often
+>> when interacting with Flash.
+> For the record, this is https://bugs.mageia.org/show_bug.cgi?id=6299
+> I am not sure this fix is good engouh, any lib used by firefox pulling
+> mozjs will make the problem pop again.
+Just a heads up, I had that issue allot in FF 13.  It appears to have 
+been fixed in FF 14 which is now in the Cauldron repo.  Also, the 
+workaround I used in FF 13  was to boot FF in safe-mode (no exts but 
+still flash) and it prevented crashing as well.
+
+/"A mind that is stretched by a new experience can never go back to its 
+old dimensions."/
+
+  *~Oliver Wendell Holmes, Jr.*
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017944.html b/zarb-ml/mageia-dev/2012-August/017944.html new file mode 100644 index 000000000..72fa83116 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017944.html @@ -0,0 +1,63 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ David Walser + luigiwalser at yahoo.com +
+ Sun Aug 5 20:15:51 CEST 2012 +

+
+ +
It has a new upstream version 3.0.11 available.  It builds fine here.
+
+The major number changes from 5 to 6 in this version, which is why I am asking if it is OK to update this package.
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017945.html b/zarb-ml/mageia-dev/2012-August/017945.html new file mode 100644 index 000000000..465b638ec --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017945.html @@ -0,0 +1,70 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ John Balcaen + mikala at mageia.org +
+ Sun Aug 5 21:17:11 CEST 2012 +

+
+ +
2012/8/5 David Walser <luigiwalser at yahoo.com>:
+> It has a new upstream version 3.0.11 available.  It builds fine here.
+>
+> The major number changes from 5 to 6 in this version, which is why I am asking if it is OK to update this package.
+did you try it before ? (i mean at least rebuild major packages based on it? )
+
+
+-- 
+Balcaen John
+Jabber-id: mikala at jabber.littleboboy.net
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017946.html b/zarb-ml/mageia-dev/2012-August/017946.html new file mode 100644 index 000000000..23e5b52e0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017946.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ David Walser + luigiwalser at yahoo.com +
+ Sun Aug 5 21:41:41 CEST 2012 +

+
+ +
John Balcaen <mikala at ...> writes:
+> 2012/8/5 David Walser <luigiwalser at ...>:
+> > It has a new upstream version 3.0.11 available.  It builds fine here.
+> >
+> > The major number changes from 5 to 6 in this version, which is why I am
+asking if it is OK to update this package.
+> did you try it before ? (i mean at least rebuild major packages based on it? )
+
+No, but predicting what will build in Cauldron is a crapshoot at best anyway.
+
+I don't know exactly what this package does or even what most of the packages
+that require it are.  I just know that it's installed on my system and I don't
+want unmaintained stuff bitrotting away on my system, hence the interest.
+
+Hopefully someone with some insight can say yay or nay.
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017947.html b/zarb-ml/mageia-dev/2012-August/017947.html new file mode 100644 index 000000000..f2e42fff9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017947.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release locales-2.16-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release locales-2.16-2.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Sun Aug 5 21:48:19 CEST 2012 +

+
+ +
On 5 August 2012 21:44, fwang <buildsystem-daemon at mageia.org> wrote:
+> fwang <fwang> 2.16-2.mga3:
+> + Revision: 278906
+> - rebuild for updated zh_CN definition
+
+Which helps raise the question: is it still pertinent to have a
+separate locales SRPM?
+WDYT Cauldron people?
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017948.html b/zarb-ml/mageia-dev/2012-August/017948.html new file mode 100644 index 000000000..5778603eb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017948.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release locales-2.16-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release locales-2.16-2.mga3

+ Thomas Backlund + tmb at mageia.org +
+ Sun Aug 5 22:17:05 CEST 2012 +

+
+ +
Thierry Vignaud skrev 5.8.2012 22:48:
+> On 5 August 2012 21:44, fwang <buildsystem-daemon at mageia.org> wrote:
+>> fwang <fwang> 2.16-2.mga3:
+>> + Revision: 278906
+>> - rebuild for updated zh_CN definition
+>
+> Which helps raise the question: is it still pertinent to have a
+> separate locales SRPM?
+> WDYT Cauldron people?
+>
+
+Actually changes like this was the reason for separate locales,
+by doing locale changes/updates only in locales package
+without the need for rebuilding glibc...
+
+And the other way, no need to rebuild locales everytime
+glibc is patched...
+
+I see this was a change done in both packages, but it might
+have been doable in locales only at buildtime...
+
+--
+Thomas
+
+
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017949.html b/zarb-ml/mageia-dev/2012-August/017949.html new file mode 100644 index 000000000..a6ecd88c4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017949.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Olivier Blin + mageia at blino.org +
+ Sun Aug 5 23:31:29 CEST 2012 +

+
+ +
David Walser <luigiwalser at yahoo.com> writes:
+
+> John Balcaen <mikala at ...> writes:
+>> 2012/8/5 David Walser <luigiwalser at ...>:
+>> > It has a new upstream version 3.0.11 available.  It builds fine here.
+>> >
+>> > The major number changes from 5 to 6 in this version, which is why I am
+> asking if it is OK to update this package.
+>> did you try it before ? (i mean at least rebuild major packages based on it? )
+>
+> No, but predicting what will build in Cauldron is a crapshoot at best anyway.
+>
+> I don't know exactly what this package does or even what most of the packages
+> that require it are.  I just know that it's installed on my system and I don't
+> want unmaintained stuff bitrotting away on my system, hence the interest.
+>
+> Hopefully someone with some insight can say yay or nay.
+
+It looks safe to update, the major change seems to be mostly because
+some debug functions are not exported anymore.
+
+Our biggest users are glib, mesa, wayland, python and llvm.
+They will have to be rebuilt.
+
+Go for it, if you can handle rebuilding all its dependencies.
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017950.html b/zarb-ml/mageia-dev/2012-August/017950.html new file mode 100644 index 000000000..ef7f4e3ef --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017950.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Balcaen John + mikala at mageia.org +
+ Mon Aug 6 00:22:17 CEST 2012 +

+
+ +
Le dimanche 5 août 2012 19:41:41 David Walser a écrit :
+> John Balcaen <mikala at ...> writes:
+> > 2012/8/5 David Walser <luigiwalser at ...>:
+> > > It has a new upstream version 3.0.11 available.  It builds fine here.
+> > > 
+> > > The major number changes from 5 to 6 in this version, which is why I am
+> 
+> asking if it is OK to update this package.
+> 
+> > did you try it before ? (i mean at least rebuild major packages based on
+> > it? )
+> No, but predicting what will build in Cauldron is a crapshoot at best
+> anyway.
+> 
+> I don't know exactly what this package does or even what most of the
+> packages that require it are.  I just know that it's installed on my system
+> and I don't want unmaintained stuff bitrotting away on my system, hence the
+> interest.
+urpmf --requires libtiff.so.5 is enough to have an idea of thoses packages 
+linked against this library.
+& to have the (minimal) list of package using it as devel br you can use
+urpmf --requires libtiff-devel --media Core_SRPMS
+where Core_SRPMS is the media cauldron/SRPMS/core/release
+
+--
+Balcaen John
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017951.html b/zarb-ml/mageia-dev/2012-August/017951.html new file mode 100644 index 000000000..f9fba4460 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017951.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Mon Aug 6 00:24:49 CEST 2012 +

+
+ +
On Sun, 5 Aug 2012, Olivier Blin wrote:
+
+> David Walser <luigiwalser at yahoo.com> writes:
+>
+>> John Balcaen <mikala at ...> writes:
+>>> 2012/8/5 David Walser <luigiwalser at ...>:
+>>>> It has a new upstream version 3.0.11 available.  It builds fine here.
+>>>>
+>>>> The major number changes from 5 to 6 in this version, which is why I am
+>> asking if it is OK to update this package.
+>>> did you try it before ? (i mean at least rebuild major packages based on it? )
+>>
+>> No, but predicting what will build in Cauldron is a crapshoot at best anyway.
+>>
+>> I don't know exactly what this package does or even what most of the packages
+>> that require it are.  I just know that it's installed on my system and I don't
+>> want unmaintained stuff bitrotting away on my system, hence the interest.
+>>
+>> Hopefully someone with some insight can say yay or nay.
+
+> Our biggest users are glib, mesa, wayland, python and llvm.
+> They will have to be rebuilt.
+
+Also firefox at least from version 15, unless we want to use the bundled 
+libffi (add --enable-system-ffi to firefox-beta's configure options).
+
+
+     Christiaan
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017952.html b/zarb-ml/mageia-dev/2012-August/017952.html new file mode 100644 index 000000000..c9f032491 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017952.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Balcaen John + mikala at mageia.org +
+ Mon Aug 6 00:26:55 CEST 2012 +

+
+ +
Le dimanche 5 août 2012 19:22:17 Balcaen John a écrit :
+> Le dimanche 5 août 2012 19:41:41 David Walser a écrit :
+> > John Balcaen <mikala at ...> writes:
+> > > 2012/8/5 David Walser <luigiwalser at ...>:
+> > > > It has a new upstream version 3.0.11 available.  It builds fine here.
+> > > > 
+> > > > The major number changes from 5 to 6 in this version, which is why I
+> > > > am
+> > 
+> > asking if it is OK to update this package.
+> > 
+> > > did you try it before ? (i mean at least rebuild major packages based on
+> > > it? )
+> > 
+> > No, but predicting what will build in Cauldron is a crapshoot at best
+> > anyway.
+> > 
+> > I don't know exactly what this package does or even what most of the
+> > packages that require it are.  I just know that it's installed on my
+> > system
+> > and I don't want unmaintained stuff bitrotting away on my system, hence
+> > the
+> > interest.
+> 
+> urpmf --requires libtiff.so.5 is enough to have an idea of thoses packages
+> linked against this library.
+> & to have the (minimal) list of package using it as devel br you can use
+> urpmf --requires libtiff-devel --media Core_SRPMS
+> where Core_SRPMS is the media cauldron/SRPMS/core/release
+
+humf :p
+wrong paste when chekcing something else
+so it's 
+urpmf --requires libffi.so.5
+for linked package against libffi
+& 
+ urpmf --requires ffi5-devel --media Core_SRPMS
+ urpmf --requires libffi-devel --media Core_SRPMS
+urpmf --requires --literal 'pkgconfig(libffi)' --media Core_SRPMS
+for the src.rpm having it explicitly in their BR.
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017953.html b/zarb-ml/mageia-dev/2012-August/017953.html new file mode 100644 index 000000000..7f47149b2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017953.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Mon Aug 6 00:29:34 CEST 2012 +

+
+ +
Le dimanche 5 août 2012 11:15:51 David Walser a écrit :
+> It has a new upstream version 3.0.11 available.  It builds fine here.
+> 
+> The major number changes from 5 to 6 in this version, which is why I am
+> asking if it is OK to update this package.
+
+i think you should, update it on your machine, install it, and see if all rpms 
+that need it builds OK first ( as this seems an important piece )
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017954.html b/zarb-ml/mageia-dev/2012-August/017954.html new file mode 100644 index 000000000..92d4bc334 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017954.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 6 00:29:37 CEST 2012 +

+
+ +
Balcaen John <mikala at ...> writes:
+> urpmf --requires libtiff.so.5 is enough to have an idea of thoses packages 
+> linked against this library.
+> & to have the (minimal) list of package using it as devel br you can use
+> urpmf --requires libtiff-devel --media Core_SRPMS
+> where Core_SRPMS is the media cauldron/SRPMS/core/release
+
+I know how to find them, I'm just unfamiliar with most of those packages.
+
+I can only check on Mageia 2 because Sophie is not giving me any answers,
+so this is the list I have:
+
+beid-middleware
+gambas3
+hardinfo
+jffi
+jna
+mesa
+gobject-introspection
+gjs
+glib2.0
+guile
+llvm
+wayland
+perl-Glib-Object-Introspection
+python
+python-gobject
+python-gudev
+ruby-ffi
+seed
+
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017955.html b/zarb-ml/mageia-dev/2012-August/017955.html new file mode 100644 index 000000000..ff650b41b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017955.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 6 00:32:58 CEST 2012 +

+
+ +
Nicolas Lécureuil <nicolas.lecureuil at ...> writes:
+> Le dimanche 5 août 2012 11:15:51 David Walser a écrit :
+> > It has a new upstream version 3.0.11 available.  It builds fine here.
+> > 
+> > The major number changes from 5 to 6 in this version, which is why I am
+> > asking if it is OK to update this package.
+> 
+> i think you should, update it on your machine, install it, and see if all rpms 
+> that need it builds OK first ( as this seems an important piece )
+
+Like I said, even if I could do all of that, that wouldn't guarantee things
+for current Cauldron.  Anyway, I this is why I asked.  It sounds like it should
+be OK, any if there's any build errors, we'll deal with it then.
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017956.html b/zarb-ml/mageia-dev/2012-August/017956.html new file mode 100644 index 000000000..e485b13f3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017956.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Olivier Blin + mageia at blino.org +
+ Mon Aug 6 00:44:26 CEST 2012 +

+
+ +
Nicolas Lécureuil <nicolas.lecureuil at free.fr> writes:
+
+> Le dimanche 5 août 2012 11:15:51 David Walser a écrit :
+>> It has a new upstream version 3.0.11 available.  It builds fine here.
+>> 
+>> The major number changes from 5 to 6 in this version, which is why I am
+>> asking if it is OK to update this package.
+>
+> i think you should, update it on your machine, install it, and see if all rpms 
+> that need it builds OK first ( as this seems an important piece )
+
+It should be ok, there is no ABI change that should impact us, it is
+mostly debug symbols being gone.
+
+See http://permalink.gmane.org/gmane.comp.lib.ffi.general/441
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017957.html b/zarb-ml/mageia-dev/2012-August/017957.html new file mode 100644 index 000000000..7ff7017b4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017957.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Mon Aug 6 00:47:35 CEST 2012 +

+
+ +
Le lundi 6 août 2012 00:44:26 Olivier Blin a écrit :
+> Nicolas Lécureuil <nicolas.lecureuil at free.fr> writes:
+> > Le dimanche 5 août 2012 11:15:51 David Walser a écrit :
+> >> It has a new upstream version 3.0.11 available.  It builds fine here.
+> >> 
+> >> The major number changes from 5 to 6 in this version, which is why I am
+> >> asking if it is OK to update this package.
+> > 
+> > i think you should, update it on your machine, install it, and see if all
+> > rpms that need it builds OK first ( as this seems an important piece )
+> 
+> It should be ok, there is no ABI change that should impact us, it is
+> mostly debug symbols being gone.
+> 
+> See http://permalink.gmane.org/gmane.comp.lib.ffi.general/441
+
+ok cool so update should be harmless ( better explaination that "it builds 
+fine" ;) )
+
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017958.html b/zarb-ml/mageia-dev/2012-August/017958.html new file mode 100644 index 000000000..721d1f1f6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017958.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 6 02:21:35 CEST 2012 +

+
+ +
David Walser <luigiwalser at ...> writes:
+> It sounds like it should be OK, any if there's any build errors,
+> we'll deal with it then.
+
+So not too bad, there are three packages that don't build.
+
+seed is failing to link to libgobject, even though the updated patch should fix
+that.  It could be that something is wrong with glib, which needed some fixes to
+build because of UsrMove.
+
+guile is giving this error:
+./stdio.h:1030:1: error: 'gets' undeclared here (not in a function)
+
+beid-middleware fails to build when it tries to call close() on a socket, but the
+close() function is undefined, and I don't see anywhere that it is defined, so I
+don't know where it thinks it's supposed to be coming from.  It also seems likely
+that the beid-middleware-4.0.0.r954_fix_xpi_for_FF5.patch needs to be updated for
+this thing to actually work.
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017959.html b/zarb-ml/mageia-dev/2012-August/017959.html new file mode 100644 index 000000000..bd0305e9e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017959.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] OK to update libffi? + + + + + + + + + +

[Mageia-dev] OK to update libffi?

+ AL13N + alien at rmail.be +
+ Mon Aug 6 10:26:07 CEST 2012 +

+
+ +
> David Walser <luigiwalser at ...> writes:
+[...]
+> beid-middleware fails to build when it tries to call close() on a socket,
+> but the
+> close() function is undefined, and I don't see anywhere that it is
+> defined, so I
+> don't know where it thinks it's supposed to be coming from.  It also seems
+> likely
+> that the beid-middleware-4.0.0.r954_fix_xpi_for_FF5.patch needs to be
+> updated for
+> this thing to actually work.
+>
+>
+
+don't worry about beid-middleware, this is for cauldron, right? i'll do an
+updated package in a few weeks
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017960.html b/zarb-ml/mageia-dev/2012-August/017960.html new file mode 100644 index 000000000..658d8285b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017960.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] smaller debug packages + + + + + + + + + +

[Mageia-dev] smaller debug packages

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 6 11:19:17 CEST 2012 +

+
+ +
Hi
+
+Here's some preliminary results with "compressed" debug packages.
+
+For some packages (rpm, firefox), no gain has been seen.
+For some others, there's interesting results:
+
+glibc:        77845759 (87% => 13% saved)
+libreoffice:  31245576 (83.1% => 17% saved)
+perl:         34588108 (94.7% => 5% saved)
+perl-Gtk2:    12793813 (79.97% => 20% saved)
+
+For very small packages with few symbols, there's not much to save:
+perl-URPM:     635185 (98% => 2% saved)
+
+This will result in:
+- smaller size on mirrors for mga3
+- slighty faster download for users when we ask them to install debug package
+- less space usag for users when we ask them to install debug package
+
+See you
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017961.html b/zarb-ml/mageia-dev/2012-August/017961.html new file mode 100644 index 000000000..980bd78a7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017961.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] [ANN] dracut 023 now in updates_testing: Feedback wanted + + + + + + + + + +

[Mageia-dev] [ANN] dracut 023 now in updates_testing: Feedback wanted

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Aug 6 14:34:36 CEST 2012 +

+
+ +
'Twas brillig, and Colin Guthrie at 04/08/12 13:37 did gyre and gimble:
+> Hi,
+> 
+> There is now a new dracut in cauldron's core/updates_testing. Please do
+> the following test:
+> 
+> 1. Ensure your system is fully up to date and reboot it.
+> 2. Install dracut from updates_testing
+> 3. Generate a new initrd: dracut /boot/foo.img
+> 4. Reboot and at the prompt edit the initrd used to be foo.img
+> 5. Make sure things boot as expected.
+> 6. Let me know if something goes horribly wrong
+> 
+> Failing any critical failures, I'll push it into core/release next week
+> sometime.
+
+Ping. I'll assume from the lack of reply that it works fine for all the
+many, many people who tested it!? :p
+
+ETA Wednesday if no-one pipes up with failures before then :)
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017962.html b/zarb-ml/mageia-dev/2012-August/017962.html new file mode 100644 index 000000000..6d1912268 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017962.html @@ -0,0 +1,62 @@ + + + + [Mageia-dev] distrib-coffee + + + + + + + + + +

[Mageia-dev] distrib-coffee

+ Frank Griffin + ftg at roadrunner.com +
+ Mon Aug 6 14:47:48 CEST 2012 +

+
+ +
...appears to have been down (or at least refusing rsync) for a few 
+hours now.
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017963.html b/zarb-ml/mageia-dev/2012-August/017963.html new file mode 100644 index 000000000..66b1b5f05 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017963.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] [packages-commits] [279280] enable opus support + + + + + + + + + +

[Mageia-dev] [packages-commits] [279280] enable opus support

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Mon Aug 6 14:57:27 CEST 2012 +

+
+ +
On Mon, 6 Aug 2012, root at mageia.org wrote:
+
+> Revision: 279280
+> Author:   tv
+
+> Modified: cauldron/firefox-beta/current/SPECS/firefox-beta.spec
+> ===================================================================
+> --- cauldron/firefox-beta/current/SPECS/firefox-beta.spec	2012-08-06 11:46:36 UTC (rev 279279)
+> +++ cauldron/firefox-beta/current/SPECS/firefox-beta.spec	2012-08-06 11:49:09 UTC (rev 279280)
+> @@ -72,6 +72,7 @@
+> BuildRequires:	python-virtualenv
+> BuildRequires:	gstreamer0.10-devel
+> BuildRequires:	libgstreamer0.10-plugins-base-devel
+> +BuildRequires:  pkgconfig(opus)
+>
+> Provides:	webclient
+> #Requires:	indexhtml
+> @@ -156,6 +157,7 @@
+> ac_add_options --with-valgrind
+> ac_add_options --with-java-include-path=%{java_home}/include
+> ac_add_options --with-java-bin-path=%{java_home}/bin
+> +ac_add_options --enable-opus
+> EOF
+>
+> export LDFLAGS="%ldflags"
+
+Mozilla source code comes with bundled ogg, vorbis, libopus and has no 
+support for using system libraries AFAICT. So the BuildRequires on opus is 
+currently not needed. But maybe someone can patch it to allow using the 
+packaged libraries (or find such a patch).
+
+
+     Christiaan
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017964.html b/zarb-ml/mageia-dev/2012-August/017964.html new file mode 100644 index 000000000..a9e6e31f9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017964.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] distrib-coffee + + + + + + + + + +

[Mageia-dev] distrib-coffee

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Mon Aug 6 15:13:50 CEST 2012 +

+
+ +
* Frank Griffin (ftg at roadrunner.com) wrote:
+> ...appears to have been down (or at least refusing rsync) for a few  
+> hours now.
+
+Nop, Distrib-coffee is working fine, It's a network issue on our
+provider side (Renater).
+
+I don't have more information...
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120806/66bb3d54/attachment.asc>
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017965.html b/zarb-ml/mageia-dev/2012-August/017965.html new file mode 100644 index 000000000..a27182e16 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017965.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] Rebuild failed on x86_64 for @278007:evolution-exchange-3.5.2-2.mga3.src.rpm + + + + + + + + + +

[Mageia-dev] Rebuild failed on x86_64 for @278007:evolution-exchange-3.5.2-2.mga3.src.rpm

+ Olav Vitters + olav at vitters.nl +
+ Mon Aug 6 16:15:16 CEST 2012 +

+
+ +
On Mon, Aug 06, 2012 at 02:54:07PM +0200, Thierry Vignaud wrote:
+> On 2 August 2012 21:59, Ulri the scheduler bot <mageia-sysadm at mageia.org> wrote:
+> > Build of the following packages failed:
+> >
+> > - @278007:evolution-exchange-3.5.2-2.mga3.src.rpm
+> >
+> > Failure details available in http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120802195734.tv.valstar.10411/log
+> > Reason:
+> > @278007:evolution-exchange-3.5.2-2.mga3.src.rpm: build_failure
+> >
+> > Log files generated:
+> > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120802195734.tv.valstar.10411/log/evolution-exchange-3.5.2-2.mga3/build.0.20120802195734.log
+> > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120802195734.tv.valstar.10411/log/evolution-exchange-3.5.2-2.mga3/install_deps-1.0.20120802195734.log
+> > http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20120802195734.tv.valstar.10411/log/evolution-exchange-3.5.2-2.mga3/rpm_qa.0.20120802195734.log
+> evolution-data-server needs fixing regarding this:
+[..]
+> In file included from e2k-utils.c:29:0:
+> /usr/include/evolution-data-server-3.6/libedataserver/e-time-utils.h:12:2:
+> error: #error "Only <libedataserver/libedataserver.h> should be
+> included directly."
+> 
+> which breaks other applications
+
+The API of evolution-data-server changed. evolution-exchange IIRC is not
+maintained anymore by Novell. So likelyhood of evolution-exchange being
+fixed is quite low. There also exists evolution-ews. That is still
+maintained by Novell.
+
+-- 
+Regards,
+Olav
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017966.html b/zarb-ml/mageia-dev/2012-August/017966.html new file mode 100644 index 000000000..f1aec0832 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017966.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] [ANN] dracut 023 now in updates_testing: Feedback wanted + + + + + + + + + +

[Mageia-dev] [ANN] dracut 023 now in updates_testing: Feedback wanted

+ Shlomi Fish + shlomif at shlomifish.org +
+ Mon Aug 6 17:54:32 CEST 2012 +

+
+ +
Hi Colin,
+
+On Mon, 06 Aug 2012 13:34:36 +0100
+Colin Guthrie <mageia at colin.guthr.ie> wrote:
+
+> 'Twas brillig, and Colin Guthrie at 04/08/12 13:37 did gyre and
+> gimble:
+> > Hi,
+> > 
+> > There is now a new dracut in cauldron's core/updates_testing.
+> > Please do the following test:
+> > 
+> > 1. Ensure your system is fully up to date and reboot it.
+> > 2. Install dracut from updates_testing
+> > 3. Generate a new initrd: dracut /boot/foo.img
+> > 4. Reboot and at the prompt edit the initrd used to be foo.img
+> > 5. Make sure things boot as expected.
+> > 6. Let me know if something goes horribly wrong
+> > 
+> > Failing any critical failures, I'll push it into core/release next
+> > week sometime.
+> 
+> Ping. I'll assume from the lack of reply that it works fine for all
+> the many, many people who tested it!? :p
+> 
+
+I tested it according to your procedure and it works fine here. (Core i3, desktop
+machine, x86-64 mode).
+
+Regards,
+
+	Shlomi Fish
+
+> ETA Wednesday if no-one pipes up with failures before then :)
+> 
+> Col
+> 
+> 
+
+
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+Optimising Code for Speed - http://shlom.in/optimise
+
+God gave us two eyes and ten fingers so we will type five times as much as we
+read.
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017967.html b/zarb-ml/mageia-dev/2012-August/017967.html new file mode 100644 index 000000000..f27a6d82b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017967.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] distrib-coffee + + + + + + + + + +

[Mageia-dev] distrib-coffee

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Aug 6 18:19:37 CEST 2012 +

+
+ +
On Mon, Aug 6, 2012 at 2:13 PM, Olivier Thauvin
+<nanardon at nanardon.zarb.org> wrote:
+> * Frank Griffin (ftg at roadrunner.com) wrote:
+>> ...appears to have been down (or at least refusing rsync) for a few
+>> hours now.
+>
+> Nop, Distrib-coffee is working fine, It's a network issue on our
+> provider side (Renater).
+>
+> I don't have more information...
+
+I would guess http://pasillo.renater.fr/TICKETS/requete_ticket.php?NUMBER=2458162&DATER=1344263482
+
+"Cable & Wireless have located a problem in their backbone and a fix
+is in progress"
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017968.html b/zarb-ml/mageia-dev/2012-August/017968.html new file mode 100644 index 000000000..c6c0f1135 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017968.html @@ -0,0 +1,66 @@ + + + + [Mageia-dev] wrong action for a specific usb device + + + + + + + + + +

[Mageia-dev] wrong action for a specific usb device

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Tue Aug 7 09:29:41 CEST 2012 +

+
+ +
Le 04/08/2012 19:15, Christiaan Welvaart a écrit :
+> So what does gphoto say? Are you sure it acts as a usb storage device?
+gphoto works OK, actually. I wrongly assumed than every modern camera 
+was using usb storage.
+
+Is there anything to do with the failed mtp-probe attempt ?
+-- 
+BOFH excuse #407:
+
+Route flapping at the NAP.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017969.html b/zarb-ml/mageia-dev/2012-August/017969.html new file mode 100644 index 000000000..f1b726b3a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017969.html @@ -0,0 +1,117 @@ + + + + [Mageia-dev] Missing in Action - 3G F5521gw + + + + + + + + + +

[Mageia-dev] Missing in Action - 3G F5521gw

+ Robert Fox + rfox at foxconsult.com +
+ Tue Aug 7 12:32:59 CEST 2012 +

+
+ +
Since the latest kernel updates in Cauldron - I am no longer able to see
+my WAN modem again (Ericsson F5521gw)
+
+The solution below doesn't work either . . . 
+
+[root at ThinkFox rfox]# lsmod | grep cdc
+cdc_ncm                18345  0 
+usbnet                 36447  1 cdc_ncm
+cdc_wdm                18885  0 
+cdc_acm                28752  0 
+usbcore               212051  9
+btusb,uvcvideo,ehci_hcd,usbhid,usbnet,cdc_acm,cdc_ncm,cdc_wdm,xhci_hcd
+[root at ThinkFox rfox]# mount -n -t usbfs -o
+devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb
+mount: mount point /proc/bus/usb does not exist
+
+Looks like /proc/bus/ doesn't have usb anymore:
+[root at ThinkFox rfox]# ls /proc/bus/
+input/ pci/
+
+Should I raise a bug?
+
+Thx,
+R.Fox
+
+On Wed, 2012-03-28 at 09:15 +0100, Colin Guthrie wrote:
+> 'Twas brillig, and Robert Fox at 27/03/12 20:11 did gyre and gimble:
+> > Since recent Cauldron updates, I can't get my 3G card (Ericsson F5521gw)
+> > to work - looks like the modules are loading:
+> > 
+> > [root at ThinkFox rfox]# lsmod | grep cdc
+> > cdc_ncm                18343  0 
+> > usbnet                 32360  1 cdc_ncm
+> > cdc_acm                28712  0 
+> > cdc_wdm                18241  0 
+> > usbcore               206950  10
+> > uvcvideo,btusb,cdc_ncm,usbnet,cdc_acm,cdc_wdm,xhci_hcd,usbhid,ehci_hcd
+> > 
+> > but when I start drakconnect, I get "no device for this connection type"
+> > 
+> > On the same notebook (Thinkpad x220) it works fine under Ubuntu 12.04
+> > B1)
+> > 
+> > Any hints would be welcome.
+> 
+> Try running as root:
+> 
+> mount -n -t usbfs -o devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb
+> 
+> 
+> Then run drakconnect.
+> 
+> aka: https://bugs.mageia.org/show_bug.cgi?id=4500
+> 
+> Col
+> 
+
+
+
+
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017970.html b/zarb-ml/mageia-dev/2012-August/017970.html new file mode 100644 index 000000000..a06ec1bcb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017970.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Aug 7 13:31:13 CEST 2012 +

+
+ +
Hi,
+
+Many people already complain about it, but for me task-obsolete must
+die.
+
+First I just remove but urpmi claim it must come back on my system...
+probably because it claim to replace lib64db5.2, even maybe still need
+it.
+
+Secondly it contains non-sense dependencies:
+Obsoletes: lib64db5.2 < 5.2.42-3
+
+Any lib64db5.2 over this version will by definition obsoletes any
+packages having same name.
+So this mean anyone can keep the lib64db5.2 as soon the release tag
+is increased or someone push into mga 2 / update any libdb higher
+than 5.2.42 (5.2.43 for example).
+
+Moreover, any package lacking of requirements during an upgrade is
+removed by urpmi.
+
+I no-one complain, I'll do a major cleanup (eg removing everything at
+least everything starting by lib) in package this week
+
+But I am still in favor to remove it. In past, package we didn't want to
+support anymore was just removed from mirrors, and this was enough to
+show their status.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120807/473cde4f/attachment.asc>
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017971.html b/zarb-ml/mageia-dev/2012-August/017971.html new file mode 100644 index 000000000..3b4b24b6c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017971.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Pascal Terjan + pterjan at gmail.com +
+ Tue Aug 7 13:39:51 CEST 2012 +

+
+ +
On Tue, Aug 7, 2012 at 12:31 PM, Olivier Thauvin
+<nanardon at nanardon.zarb.org> wrote:
+> Hi,
+>
+> Many people already complain about it, but for me task-obsolete must
+> die.
+
+I don't think so, but people should not be allowed to add random
+obsoletes there.
+
+> First I just remove but urpmi claim it must come back on my system...
+> probably because it claim to replace lib64db5.2, even maybe still need
+> it.
+>
+> Secondly it contains non-sense dependencies:
+> Obsoletes: lib64db5.2 < 5.2.42-3
+>
+> Any lib64db5.2 over this version will by definition obsoletes any
+> packages having same name.
+> So this mean anyone can keep the lib64db5.2 as soon the release tag
+> is increased or someone push into mga 2 / update any libdb higher
+> than 5.2.42 (5.2.43 for example).
+>
+> Moreover, any package lacking of requirements during an upgrade is
+> removed by urpmi.
+>
+> I no-one complain, I'll do a major cleanup (eg removing everything at
+> least everything starting by lib) in package this week
+>
+> But I am still in favor to remove it. In past, package we didn't want to
+> support anymore was just removed from mirrors, and this was enough to
+> show their status.
+
+But people will not be notified of it.
+If a system is obsolete with the new distribution and known to break
+things/contain major security problems, I think having a place to put
+the obsoletes is good.
+But really I wouldn't expect more than 2 or 3 such packages in a release...
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017972.html b/zarb-ml/mageia-dev/2012-August/017972.html new file mode 100644 index 000000000..2d9396698 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017972.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Tue Aug 7 13:54:03 CEST 2012 +

+
+ +
On Tue, 7 Aug 2012, Pascal Terjan wrote:
+
+> On Tue, Aug 7, 2012 at 12:31 PM, Olivier Thauvin
+> <nanardon at nanardon.zarb.org> wrote:
+>> But I am still in favor to remove it. In past, package we didn't want to
+>> support anymore was just removed from mirrors, and this was enough to
+>> show their status.
+>
+> But people will not be notified of it.
+
+> If a system is obsolete with the new distribution and known to break
+> things/contain major security problems, I think having a place to put
+> the obsoletes is good.
+> But really I wouldn't expect more than 2 or 3 such packages in a release...
+
+The package manager (urpmi) can also notify people because it sees which 
+installed packages are not in the configured repositories. Zypper even 
+removes such packages automatically. This would give users the choice to 
+keep an 'obsolete' package installed, while that choice doesn't exist with 
+task-obsolete.
+
+
+     Christiaan
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017973.html b/zarb-ml/mageia-dev/2012-August/017973.html new file mode 100644 index 000000000..2f7b85bda --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017973.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Frank Griffin + ftg at roadrunner.com +
+ Tue Aug 7 15:27:50 CEST 2012 +

+
+ +
In current cauldron, my desktop system's monitor keeps powering down 
+after a relatively small period of inactivity.  I've checked what's 
+running, and the only two likely candidates I could find were sensord 
+and upowerd, but I've killed both of them and it still happens.
+
+Any idea what's doing this ?  syslog, messages, and other things in 
+/var/log give no hint.
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017974.html b/zarb-ml/mageia-dev/2012-August/017974.html new file mode 100644 index 000000000..aa3d3a75e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017974.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Aug 7 15:30:15 CEST 2012 +

+
+ +
* Pascal Terjan (pterjan at gmail.com) wrote:
+> On Tue, Aug 7, 2012 at 12:31 PM, Olivier Thauvin
+> <nanardon at nanardon.zarb.org> wrote:
+> > Hi,
+> >
+> > But I am still in favor to remove it. In past, package we didn't want to
+> > support anymore was just removed from mirrors, and this was enough to
+> > show their status.
+> 
+> But people will not be notified of it.
+> If a system is obsolete with the new distribution and known to break
+> things/contain major security problems, I think having a place to put
+> the obsoletes is good.
+> But really I wouldn't expect more than 2 or 3 such packages in a release...
+
+Indeed, people are not notified, whereas currently packages are removed
+w/o any notification neither, I am not sure it is better.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120807/b2e02ee2/attachment.asc>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017975.html b/zarb-ml/mageia-dev/2012-August/017975.html new file mode 100644 index 000000000..985fa4b9f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017975.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Frank Griffin + ftg at roadrunner.com +
+ Tue Aug 7 17:08:55 CEST 2012 +

+
+ +
On 08/07/2012 09:27 AM, Frank Griffin wrote:
+> In current cauldron, my desktop system's monitor keeps powering down 
+> after a relatively small period of inactivity.  I've checked what's 
+> running, and the only two likely candidates I could find were sensord 
+> and upowerd, but I've killed both of them and it still happens.
+>
+> Any idea what's doing this ?  syslog, messages, and other things in 
+> /var/log give no hint.
+>
+The period of inactivity that causes this is exactly 30 seconds. I've 
+checked both Display and Power Management in the KDE tools, and nothing 
+is set which should cause this.  Screensaver is off, and so is any PM 
+setting that would do this.
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017976.html b/zarb-ml/mageia-dev/2012-August/017976.html new file mode 100644 index 000000000..f4adb9231 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017976.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Aug 7 18:33:11 CEST 2012 +

+
+ +
Hello,
+
+Am I the only one to have such behavior:
+
+[root at apus olivier]# LC_ALL=C urpmi --auto-update
+The following package has to be removed for others to be upgraded:
+glibc-2.16-8.mga3.x86_64
+ (in order to install glibc-2.16-8.mga3.x86_64) (y/N)
+
+If I accept the transaction fails saying glibc-2.16-8.mga3.x86_64 is
+already installed, obviously.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120807/3e245965/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017977.html b/zarb-ml/mageia-dev/2012-August/017977.html new file mode 100644 index 000000000..7100de601 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017977.html @@ -0,0 +1,116 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Philippe Reynes + tremyfr at yahoo.fr +
+ Tue Aug 7 18:56:03 CEST 2012 +

+
+ +
Hi Olivier,
+
+I've got the same behaviour.
+If I accept, I have: 
+L'installation a échoué :    paquetage glibc-6:2.16-8.mga3.i586 déjà installé
+
+Regards,
+trem
+
+
+
+
+________________________________
+ De : Olivier Thauvin <nanardon at nanardon.zarb.org>
+À : mageia-dev at mageia.org 
+Envoyé le : Mardi 7 août 2012 18h33
+Objet : [Mageia-dev] strange urpmi --auto-update with glibc
+ 
+Hello,
+
+Am I the only one to have such behavior:
+
+[root at apus olivier]# LC_ALL=C urpmi --auto-update
+The following package has to be removed for others to be upgraded:
+glibc-2.16-8.mga3.x86_64
+(in order to install glibc-2.16-8.mga3.x86_64) (y/N)
+
+If I accept the transaction fails saying glibc-2.16-8.mga3.x86_64 is
+already installed, obviously.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120807/5d2f748e/attachment-0001.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017978.html b/zarb-ml/mageia-dev/2012-August/017978.html new file mode 100644 index 000000000..b9e642288 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017978.html @@ -0,0 +1,105 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 7 19:48:31 CEST 2012 +

+
+ +
'Twas brillig, and Frank Griffin at 07/08/12 16:08 did gyre and gimble:
+> On 08/07/2012 09:27 AM, Frank Griffin wrote:
+>> In current cauldron, my desktop system's monitor keeps powering down
+>> after a relatively small period of inactivity.  I've checked what's
+>> running, and the only two likely candidates I could find were sensord
+>> and upowerd, but I've killed both of them and it still happens.
+>>
+>> Any idea what's doing this ?  syslog, messages, and other things in
+>> /var/log give no hint.
+>>
+> The period of inactivity that causes this is exactly 30 seconds. I've
+> checked both Display and Power Management in the KDE tools, and nothing
+> is set which should cause this.  Screensaver is off, and so is any PM
+> setting that would do this.
+
+Try: xset -dpms?
+
+Dunno what else would be doing it tho'. Likely related to graphics card
+driver tho', so probably worth mentioning what you're using.
+
+Col
+
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017979.html b/zarb-ml/mageia-dev/2012-August/017979.html new file mode 100644 index 000000000..90c97b8c3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017979.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 7 19:57:51 CEST 2012 +

+
+ +
'Twas brillig, and Christiaan Welvaart at 07/08/12 12:54 did gyre and
+gimble:
+> The package manager (urpmi) can also notify people because it sees which
+> installed packages are not in the configured repositories. Zypper even
+> removes such packages automatically. This would give users the choice to
+> keep an 'obsolete' package installed, while that choice doesn't exist
+> with task-obsolete.
+
+urpmq --not-available?
+
+But maybe run automatically at the end of an auto-update/select in much
+the same way as the current "orphans" stuff is handled?
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017980.html b/zarb-ml/mageia-dev/2012-August/017980.html new file mode 100644 index 000000000..d633c0f0d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017980.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] Qt5 in mageia cauldron + + + + + + + + + +

[Mageia-dev] Qt5 in mageia cauldron

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Tue Aug 7 20:12:15 CEST 2012 +

+
+ +
Hello,
+
+i just pushed on the Buildsystem a rpm of qt5, ( this is a snapshot of current 
+git repos ( will be real beta when it will come out).
+
+I fixed some packages using pkgconfig as buildrequire to be sure they link 
+against Qt4 and not qt5.
+
+Please report if it is installed by some apps ( shouldn't currently ) or if it 
+cause troubles when installed.
+
+a separate qtwebkit5 rpm will come and fixes on the current qt5 spec file ( this 
+is a moving target yet )
+
+Thank you and good test.
+Nicolas.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017981.html b/zarb-ml/mageia-dev/2012-August/017981.html new file mode 100644 index 000000000..64d16972d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017981.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Frank Griffin + ftg at roadrunner.com +
+ Tue Aug 7 20:43:24 CEST 2012 +

+
+ +
On 08/07/2012 01:48 PM, Colin Guthrie wrote:
+> Try: xset -dpms?
+
+> Dunno what else would be doing it tho'. Likely related to graphics 
+> card driver tho', so probably worth mentioning what you're using. Col 
+Spot on !  That was it.
+
+This is a fresh install as of a couple of days ago, using the free ATI 
+driver + nonfree firmware.  Is anyone aware of a change to issue xset 
++dpms ?  Cos I certainly didn't do it.
+
+Thanks for figuring this out.  It was driving me batty.
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017982.html b/zarb-ml/mageia-dev/2012-August/017982.html new file mode 100644 index 000000000..305d938d6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017982.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Olivier Blin + mageia at blino.org +
+ Tue Aug 7 21:15:58 CEST 2012 +

+
+ +
Colin Guthrie <mageia at colin.guthr.ie> writes:
+
+> 'Twas brillig, and Christiaan Welvaart at 07/08/12 12:54 did gyre and
+> gimble:
+>> The package manager (urpmi) can also notify people because it sees which
+>> installed packages are not in the configured repositories. Zypper even
+>> removes such packages automatically. This would give users the choice to
+>> keep an 'obsolete' package installed, while that choice doesn't exist
+>> with task-obsolete.
+>
+> urpmq --not-available?
+
+This would also remove packages installed from third-party vendors,
+there are still some proprietary RPM packages out there.
+
+There is also this command:
+urpmi_rpm-find-leaves -g
+
+It finds unused library packages, or actually unused packages in the
+System/Libraries group. But there are quite a few false-positive
+results, because of packages incorrectly using System/Libraries as
+group.
+
+-- 
+Olivier Blin - blino
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017983.html b/zarb-ml/mageia-dev/2012-August/017983.html new file mode 100644 index 000000000..e9dcb9b7e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017983.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ David Walser + luigiwalser at yahoo.com +
+ Wed Aug 8 03:40:58 CEST 2012 +

+
+ +
Frank Griffin wrote:
+> On 08/07/2012 01:48 PM, Colin Guthrie wrote:
+>> Try: xset -dpms?
+> 
+>> Dunno what else would be doing it tho'. Likely related to graphics 
+>> card driver tho', so probably worth mentioning what you're using. Col 
+> Spot on !  That was it.
+> 
+> This is a fresh install as of a couple of days ago, using the free ATI 
+> driver + nonfree firmware.  Is anyone aware of a change to issue xset 
+> +dpms ?  Cos I certainly didn't do it.
+> 
+> Thanks for figuring this out.  It was driving me batty.
+
+It's not a matter of doing xset +dpms, it's generally enabled by default.  It's a matter of how it's 
+configured.  It has three numbers for different levels of powerdown, usually you'll see three 
+numbers in the GUI configurators too.  So "xset dpms 0 0 0" would have fixed your problem too.  So 
+the question is what is setting your settings to something crazy and why.  I usually set mine to 
+xset dpms 0 0 1200 which turns the monitor off after 20 minutes of inactivity.
+
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017984.html b/zarb-ml/mageia-dev/2012-August/017984.html new file mode 100644 index 000000000..6dbc4ea85 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017984.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 8 07:25:13 CEST 2012 +

+
+ +
On 7 August 2012 18:33, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> Hello,
+>
+> Am I the only one to have such behavior:
+>
+> [root at apus olivier]# LC_ALL=C urpmi --auto-update
+> The following package has to be removed for others to be upgraded:
+> glibc-2.16-8.mga3.x86_64
+>  (in order to install glibc-2.16-8.mga3.x86_64) (y/N)
+>
+> If I accept the transaction fails saying glibc-2.16-8.mga3.x86_64 is
+> already installed, obviously.
+
+I would need the bug-glibc.tar.xz file resulting from running the
+following commands:
+urpmi --auto-update --bug bug-glibc
+tar cfa bug-glibc{.tar.xz,}
+
+Send this file to me (privately, not to the ml (too big)).
+Thx
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017985.html b/zarb-ml/mageia-dev/2012-August/017985.html new file mode 100644 index 000000000..99a9561b2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017985.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ andre999 + andre999mga at laposte.net +
+ Wed Aug 8 07:35:54 CEST 2012 +

+
+ +
Olivier Blin a écrit :
+> Colin Guthrie<mageia at colin.guthr.ie>  writes:
+>
+>    
+>> 'Twas brillig, and Christiaan Welvaart at 07/08/12 12:54 did gyre and
+>> gimble:
+>>      
+>>> The package manager (urpmi) can also notify people because it sees which
+>>> installed packages are not in the configured repositories. Zypper even
+>>> removes such packages automatically. This would give users the choice to
+>>> keep an 'obsolete' package installed, while that choice doesn't exist
+>>> with task-obsolete.
+>>>        
+>> urpmq --not-available?
+>>      
+> This would also remove packages installed from third-party vendors,
+> there are still some proprietary RPM packages out there.
+>
+> There is also this command:
+> urpmi_rpm-find-leaves -g
+>
+> It finds unused library packages, or actually unused packages in the
+> System/Libraries group. But there are quite a few false-positive
+> results, because of packages incorrectly using System/Libraries as
+> group.
+>    
+
+Tried it.
+Being cautious, I left about 10 of the 50 or so packages listed.  Most 
+listed were obviously useless, but otherwise hard to find.  Used 
+rpmdrake to see their descriptions and remove them.
+Some of the packages seemed to be used by others, if I'm not mistaken.  
+Maybe by suggests ?
+
+For everyone's info, -g alone scans System/Libraries.
+Using -g {group} will scan whatever other group.
+
+In sum, a useful tool if used cautiously.
+A lot better than task-obsoletes or whatever else that would remove 
+packages indiscriminately and/or automatically.
+
+-- 
+André
+
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017986.html b/zarb-ml/mageia-dev/2012-August/017986.html new file mode 100644 index 000000000..47f7752df --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017986.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Wed Aug 8 07:41:57 CEST 2012 +

+
+ +
* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> On 7 August 2012 18:33, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> > Hello,
+> >
+> > Am I the only one to have such behavior:
+> >
+> > [root at apus olivier]# LC_ALL=C urpmi --auto-update
+> > The following package has to be removed for others to be upgraded:
+> > glibc-2.16-8.mga3.x86_64
+> >  (in order to install glibc-2.16-8.mga3.x86_64) (y/N)
+> >
+> > If I accept the transaction fails saying glibc-2.16-8.mga3.x86_64 is
+> > already installed, obviously.
+> 
+> I would need the bug-glibc.tar.xz file resulting from running the
+> following commands:
+> urpmi --auto-update --bug bug-glibc
+> tar cfa bug-glibc{.tar.xz,}
+> 
+> Send this file to me (privately, not to the ml (too big)).
+
+Or I let you downloading it from here:
+
+http://olivier.thauvin.page.latmos.ipsl.fr/bug-glibc.tar.xz
+
+Regards.
+
+> Thx
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120808/370a1354/attachment-0001.asc>
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017987.html b/zarb-ml/mageia-dev/2012-August/017987.html new file mode 100644 index 000000000..0d1bb11f3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017987.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release glib2.0-2.33.8-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release glib2.0-2.33.8-1.mga3

+ Olav Vitters + olav at vitters.nl +
+ Wed Aug 8 10:03:20 CEST 2012 +

+
+ +
On Wed, Aug 08, 2012 at 07:35:08AM +0200, tv wrote:
+> tv <tv> 2.33.8-1.mga3:
+> + Revision: 279924
+> - looks like man pages & HTML doc are no more build
+> - looks like man pages are no more build
+
+Wasn't included in the tarball and the glib build is a bit broken:
+https://bugzilla.gnome.org/show_bug.cgi?id=681336
+
+Basically: if not in tarball, only built if gtk-doc is enabled.
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017988.html b/zarb-ml/mageia-dev/2012-August/017988.html new file mode 100644 index 000000000..6bbdd02a6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017988.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] [soft-commits] [5307] Initial btrfs support + + + + + + + + + +

[Mageia-dev] [soft-commits] [5307] Initial btrfs support

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Aug 8 10:56:11 CEST 2012 +

+
+ +
On Wed, Aug 8, 2012 at 1:17 AM,  <root at mageia.org> wrote:
+> Revision 5307 Author pterjan Date 2012-08-08 02:17:24 +0200 (Wed, 08 Aug
+> 2012)
+>
+> Log Message
+>
+> Initial btrfs support
+
+In case someone is interested:
+- It works fine here
+- Building a package on my machine takes 12/13s vs 18/20s using a
+tarball. Savings would be less visible if using tmpfs or a ssd (time
+savings happen at two times: when creating the chroot we don't need to
+untar it, and when deleting it we don't need to rm -rf)
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017989.html b/zarb-ml/mageia-dev/2012-August/017989.html new file mode 100644 index 000000000..dfdeb2408 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017989.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Frank Griffin + ftg at roadrunner.com +
+ Wed Aug 8 12:28:19 CEST 2012 +

+
+ +
On 08/07/2012 09:40 PM, David Walser wrote:
+> It's not a matter of doing xset +dpms, it's generally enabled by 
+> default. It's a matter of how it's configured. It has three numbers 
+> for different levels of powerdown, usually you'll see three numbers in 
+> the GUI configurators too. So "xset dpms 0 0 0" would have fixed your 
+> problem too. So the question is what is setting your settings to 
+> something crazy and why. I usually set mine to xset dpms 0 0 1200 
+> which turns the monitor off after 20 minutes of inactivity. 
+This is a fresh install about a week old.  After install, I have some 
+scripts that re-install all packages that had been installed on the last 
+system and do some configuration.  But I don't touch xset, and in fact I 
+didn't know anything about dpms until Col posted and I looked it up.
+
+So, I guess that whatever enables it by default is the first place to 
+look for the 30-second problem.  After that, it would have to have been 
+in a package install script.
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017990.html b/zarb-ml/mageia-dev/2012-August/017990.html new file mode 100644 index 000000000..64170ca12 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017990.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 8 13:42:09 CEST 2012 +

+
+ +
'Twas brillig, and Frank Griffin at 08/08/12 11:28 did gyre and gimble:
+> On 08/07/2012 09:40 PM, David Walser wrote:
+>> It's not a matter of doing xset +dpms, it's generally enabled by
+>> default. It's a matter of how it's configured. It has three numbers
+>> for different levels of powerdown, usually you'll see three numbers in
+>> the GUI configurators too. So "xset dpms 0 0 0" would have fixed your
+>> problem too. So the question is what is setting your settings to
+>> something crazy and why. I usually set mine to xset dpms 0 0 1200
+>> which turns the monitor off after 20 minutes of inactivity. 
+> This is a fresh install about a week old.  After install, I have some
+> scripts that re-install all packages that had been installed on the last
+> system and do some configuration.  But I don't touch xset, and in fact I
+> didn't know anything about dpms until Col posted and I looked it up.
+> 
+> So, I guess that whatever enables it by default is the first place to
+> look for the 30-second problem.  After that, it would have to have been
+> in a package install script.
+
+Generally speaking these settings are done in the display environment
+GUIs (i.e. Gnome and KDE) thus avoiding having to call xset directly by
+the user or in scripts etc. This is just a command line interface to
+things the DE's should wrap already.
+
+So I'd go looking for those bits breaking and/or something in your user
+account messing up. i.e. try it with a fresh boot and logging into a
+fresh user account and see if the problem still occurs. That might help
+narrow down where the real problem lies.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017991.html b/zarb-ml/mageia-dev/2012-August/017991.html new file mode 100644 index 000000000..59c3c675c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017991.html @@ -0,0 +1,65 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release libreoffice-3.6.0.4-2.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 8 14:06:03 CEST 2012 +

+
+ +
On 2 August 2012 16:44, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>> - 3.6.0 rc4
+>>
+>> That is not consistent with package version (3.6.0.4).
+>
+> Be my guest, fee free to complain upstream:
+> http://www.mail-archive.com/libreoffice@lists.freedesktop.org/msg35878.html
+
+And anyway RC4 is now the final 3.6.0 release.
+("This release is bit-for-bit identical to the 3.6.0 Release Candidate 4")
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017992.html b/zarb-ml/mageia-dev/2012-August/017992.html new file mode 100644 index 000000000..7613669b9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017992.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Frank Griffin + ftg at roadrunner.com +
+ Wed Aug 8 15:17:34 CEST 2012 +

+
+ +
On 08/08/2012 07:42 AM, Colin Guthrie wrote:
+> Generally speaking these settings are done in the display environment
+> GUIs (i.e. Gnome and KDE) thus avoiding having to call xset directly by
+> the user or in scripts etc. This is just a command line interface to
+> things the DE's should wrap already.
+>
+> So I'd go looking for those bits breaking and/or something in your user
+> account messing up. i.e. try it with a fresh boot and logging into a
+> fresh user account and see if the problem still occurs. That might help
+> narrow down where the real problem lies.
+>
+>
+This is getting muddy.  I've done a lot of cauldron updating since my 
+last logout/reboot, and when I tried a fresh boot GDM hung repeatedly, 
+and I had to switch to KDM.
+
+The problem doesn't occur with a fresh user, but it no longer occurs on 
+my userid either.  Either it's a function of the DM, or else the "xset 
+-dpms" I did previously is sticky:
+
+[root at ftgme2 ftg]# xset q
+Keyboard Control:
+...
+DPMS (Energy Star):
+   Standby: 600    Suspend: 600    Off: 600
+   DPMS is Disabled
+
+But knowing that dpms is involved got some google results, and I think 
+the problem is https://bugs.kde.org/show_bug.cgi?id=295814
+
+The similarity between my case and the reported ones is that I had set 
+all Power Management off, so that the screen would never dim or 
+disable.  I had done this because I have some WINE stuff run overnight 
+by cron, and when KDE blanks or disables the screen, graphical apps 
+won't start.
+
+According to the report, a disabled PM enables dpms with a random set of 
+numbers.  I just happened to get 30 seconds.  One poor sod had a 
+1-second timeout.
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017993.html b/zarb-ml/mageia-dev/2012-August/017993.html new file mode 100644 index 000000000..c674b405f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017993.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] Issue with latest Evolution (evolution-3.5.5-1.mga3) + + + + + + + + + +

[Mageia-dev] Issue with latest Evolution (evolution-3.5.5-1.mga3)

+ Robert Fox + rfox at foxconsult.com +
+ Wed Aug 8 15:18:43 CEST 2012 +

+
+ +
Lately, Evolution as been acting a bit odd - I have always had it set up
+under Mail Preferences -> HTML Messages -> Loading Images -> set to
+"Never Load Images from the Internet"
+
+When I want to load the messages, I just click "Ctrl-i" and it would
+normally load the images.
+
+Now, if I click on "Ctrl-i" - a task starts below which states "Saving
+user interface" - but evolution stops responding - and when I click on
+something else further tasks start but hang - and I have to use "killev"
+to kill Evolution.
+
+Strangely, after killev, this is still running:
+
+rfox      3947  0.0  0.1 594848  8488 ?        SLl  11:36
+0:00 /usr/lib64/evolution-source-registry
+
+So I can force this to happen if I try and load images on an HTML mail 
+
+Anybody have the same issue?
+
+Cheers,
+R.Fox
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017994.html b/zarb-ml/mageia-dev/2012-August/017994.html new file mode 100644 index 000000000..12a40a093 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017994.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Desktop monitor powering down + + + + + + + + + +

[Mageia-dev] Desktop monitor powering down

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 8 16:20:33 CEST 2012 +

+
+ +
'Twas brillig, and Frank Griffin at 08/08/12 14:17 did gyre and gimble:
+> One poor sod had a 1-second timeout.
+
+Hey who turned out the lights!
+
+That looks like the correct bug at least :)
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017995.html b/zarb-ml/mageia-dev/2012-August/017995.html new file mode 100644 index 000000000..2a10a6aea --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017995.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] packagers meeting + + + + + + + + + +

[Mageia-dev] packagers meeting

+ Anne Nicolas + ennael1 at gmail.com +
+ Thu Aug 9 18:42:04 CEST 2012 +

+
+ +
hi there
+
+On my side, I'm just going back from vacation and still did not get back 
+in touch with Mageia stuff. boklm is also on vacation so we will have 
+our next meeting next week. As usual you can mail here any emergencies 
+to be discussed.
+
+Cheers
+
+-- 
+Anne
+http://mageia.org
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017996.html b/zarb-ml/mageia-dev/2012-August/017996.html new file mode 100644 index 000000000..d42d9c886 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017996.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Suspending package maintainership + + + + + + + + + +

[Mageia-dev] Suspending package maintainership

+ Florian Hubold + doktor5000 at arcor.de +
+ Wed Aug 8 21:57:06 CEST 2012 +

+
+ +
Hi all,
+
+sadly i need to announce that i'll suspend maintainership
+because lack of time currently, and in the near future, say
+at least for the next half year or so. I've already waited a bit too
+long and some others already did some security updates on my behalf
+like for wireshark and avidemux.
+
+Quite sad about this, but in the end it's better than falsely
+pretending packages are maintained when they are effectively not.
+I'll try to take on the bugs which are currently assigned to me
+as i find the time to do so.
+
+In exchange i'd try to mentor one or two new padawans, to
+somehow make up for the gap.
+
+
+Best Regards
+
+Florian
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017997.html b/zarb-ml/mageia-dev/2012-August/017997.html new file mode 100644 index 000000000..d2fd42be9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017997.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] How to Test the new uClibc? + + + + + + + + + +

[Mageia-dev] How to Test the new uClibc?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 8 22:24:45 CEST 2012 +

+
+ +
On 14 June 2012 07:11, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>> since the new busybox (which I maintain in Mageia) package did not build with
+>> the uClibc version that was present in Cauldron, I grab maintainership for
+>> uClibc too, and commited a new uClibc package to the svn (based a lot on the
+>> Mandriva Cooker package).
+>>
+>> However, now I'm wondering how to best test it to make sure nothing got broken.
+>> Which programs are using it on a Mageia system that I can use to test?
+>
+> Not that much.
+> If busybox tools still work, just go on...
+
+Ping! It's time to make cauldron hot!
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017998.html b/zarb-ml/mageia-dev/2012-August/017998.html new file mode 100644 index 000000000..ce71ba676 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017998.html @@ -0,0 +1,128 @@ + + + + [Mageia-dev] How to Test the new uClibc? + + + + + + + + + +

[Mageia-dev] How to Test the new uClibc?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 09:10:06 CEST 2012 +

+
+ +
On 9 August 2012 08:31, Shlomi Fish <shlomif at iglu.org.il> wrote:
+>> wrote:
+>> >> since the new busybox (which I maintain in Mageia) package did not
+>> >> build with the uClibc version that was present in Cauldron, I grab
+>> >> maintainership for uClibc too, and commited a new uClibc package
+>> >> to the svn (based a lot on the Mandriva Cooker package).
+>> >>
+>> >> However, now I'm wondering how to best test it to make sure
+>> >> nothing got broken. Which programs are using it on a Mageia system
+>> >> that I can use to test?
+>> >
+>> > Not that much.
+>> > If busybox tools still work, just go on...
+>>
+>> Ping! It's time to make cauldron hot!
+>
+> I don't know if you attended that IRC conversation, so let me quote it (I am rindolf):
+
+I didn't.
+
+(...)
+
+> So I'm back at square 1, and don't know how to further proceed. If someone more capable than me can take
+> it upon themselves, then it would be great.
+
+I think's Neoclust worries for nothing.
+
+There not that much packages using uclibc:
+
+busybox-1.20.2-1.mga3.src
+CCfits-2.4-1.mga3.src
+liblzo-2.06-1.mga2.src
+libx86-1.1-11.mga2.src
+lvm2-2.02.95-5.mga3.src
+newt-0.52.14-2.mga3.src
+pciutils-3.1.10-1.mga3.src
+slang-2.2.4-4.mga3.src
+sysfsutils-2.1.0-14.1.mga3.src
+util-linux-2.21.2-3.mga3.src
+wmbattery-2.40-1.mga2.src
+wmfire-1.2.4-1.mga2.src
+zlib-1.2.7-4.mga3.src
+
+Note that of those are unused
+(busybox/pciutils/newt/slang/sysfsutils/zlib) unlike
+mdv who choose to bloat installer by compiling with uclibc instead of dietlibc
+
+What's more, the remaining ones (util-linux, lvm2 (maybe busybox?)) were
+used with old mkinitrd but I think dracut now use glibc linked ones.
+Colin, can you confirm?
+
+So I don't think it's that much critical.
+At worst, we can check that regenerating initrd on a LVM machine still
+boots.
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/017999.html b/zarb-ml/mageia-dev/2012-August/017999.html new file mode 100644 index 000000000..8e743a295 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/017999.html @@ -0,0 +1,157 @@ + + + + [Mageia-dev] How to Test the new uClibc? + + + + + + + + + +

[Mageia-dev] How to Test the new uClibc?

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 10:39:05 CEST 2012 +

+
+ +
'Twas brillig, and Thierry Vignaud at 09/08/12 08:10 did gyre and gimble:
+> On 9 August 2012 08:31, Shlomi Fish <shlomif at iglu.org.il> wrote:
+>>> wrote:
+>>>>> since the new busybox (which I maintain in Mageia) package did not
+>>>>> build with the uClibc version that was present in Cauldron, I grab
+>>>>> maintainership for uClibc too, and commited a new uClibc package
+>>>>> to the svn (based a lot on the Mandriva Cooker package).
+>>>>>
+>>>>> However, now I'm wondering how to best test it to make sure
+>>>>> nothing got broken. Which programs are using it on a Mageia system
+>>>>> that I can use to test?
+>>>>
+>>>> Not that much.
+>>>> If busybox tools still work, just go on...
+>>>
+>>> Ping! It's time to make cauldron hot!
+>>
+>> I don't know if you attended that IRC conversation, so let me quote it (I am rindolf):
+> 
+> I didn't.
+> 
+> (...)
+> 
+>> So I'm back at square 1, and don't know how to further proceed. If someone more capable than me can take
+>> it upon themselves, then it would be great.
+> 
+> I think's Neoclust worries for nothing.
+> 
+> There not that much packages using uclibc:
+> 
+> busybox-1.20.2-1.mga3.src
+> CCfits-2.4-1.mga3.src
+> liblzo-2.06-1.mga2.src
+> libx86-1.1-11.mga2.src
+> lvm2-2.02.95-5.mga3.src
+> newt-0.52.14-2.mga3.src
+> pciutils-3.1.10-1.mga3.src
+> slang-2.2.4-4.mga3.src
+> sysfsutils-2.1.0-14.1.mga3.src
+> util-linux-2.21.2-3.mga3.src
+> wmbattery-2.40-1.mga2.src
+> wmfire-1.2.4-1.mga2.src
+> zlib-1.2.7-4.mga3.src
+> 
+> Note that of those are unused
+> (busybox/pciutils/newt/slang/sysfsutils/zlib) unlike
+> mdv who choose to bloat installer by compiling with uclibc instead of dietlibc
+> 
+> What's more, the remaining ones (util-linux, lvm2 (maybe busybox?)) were
+> used with old mkinitrd but I think dracut now use glibc linked ones.
+> Colin, can you confirm?
+
+Dracut just uses what is on the system, so yeah it'll use glibc unless
+some module pulls it in. There is a busybox module in dracut to allow it
+to be installed but it's not enabled by default AFAICT.
+
+> So I don't think it's that much critical.
+> At worst, we can check that regenerating initrd on a LVM machine still
+> boots.
+
+My machine is an LVM one, so I can likely test this, but as my current
+initrd does not have ulibc in it, I doubt very much this test will show
+anything other than success :)
+
+Cheers
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018000.html b/zarb-ml/mageia-dev/2012-August/018000.html new file mode 100644 index 000000000..f9846b4c4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018000.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] Suspending package maintainership + + + + + + + + + +

[Mageia-dev] Suspending package maintainership

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 10:42:24 CEST 2012 +

+
+ +
'Twas brillig, and Florian Hubold at 08/08/12 20:57 did gyre and gimble:
+> Hi all,
+> 
+> sadly i need to announce that i'll suspend maintainership
+> because lack of time currently, and in the near future, say
+> at least for the next half year or so. I've already waited a bit too
+> long and some others already did some security updates on my behalf
+> like for wireshark and avidemux.
+> 
+> Quite sad about this, but in the end it's better than falsely
+> pretending packages are maintained when they are effectively not.
+> I'll try to take on the bugs which are currently assigned to me
+> as i find the time to do so.
+> 
+> In exchange i'd try to mentor one or two new padawans, to
+> somehow make up for the gap.
+
+Sad to hear but such is the way of things sometimes. Thankfully you'll
+still be "around" generally which is very nice to hear :)
+
+All the best
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018001.html b/zarb-ml/mageia-dev/2012-August/018001.html new file mode 100644 index 000000000..da343111c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018001.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] [ANN] dracut 023 landing in core + + + + + + + + + +

[Mageia-dev] [ANN] dracut 023 landing in core

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 11:02:33 CEST 2012 +

+
+ +
Hi,
+
+I only got one bit of feedback from the testing call and it was positive
+so now everyone is getting the new dracut.
+
+Goodbye mkinitrd! So long and thanks for all the fish.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018002.html b/zarb-ml/mageia-dev/2012-August/018002.html new file mode 100644 index 000000000..017cc6ca5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018002.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] How to Test the new uClibc? + + + + + + + + + +

[Mageia-dev] How to Test the new uClibc?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 12:40:03 CEST 2012 +

+
+ +
On 9 August 2012 10:39, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>>>> If busybox tools still work, just go on...
+>>>>
+>>>> Ping! It's time to make cauldron hot!
+>>>
+>>> I don't know if you attended that IRC conversation, so let me quote it (I am rindolf):
+
+(...)
+
+>>> So I'm back at square 1, and don't know how to further proceed. If someone more capable than me can take
+>>> it upon themselves, then it would be great.
+
+(...)
+
+> Dracut just uses what is on the system, so yeah it'll use glibc unless
+> some module pulls it in. There is a busybox module in dracut to allow it
+> to be installed but it's not enabled by default AFAICT.
+>
+>> So I don't think it's that much critical.
+>> At worst, we can check that regenerating initrd on a LVM machine still
+>> boots.
+>
+> My machine is an LVM one, so I can likely test this, but as my current
+> initrd does not have ulibc in it, I doubt very much this test will show
+> anything other than success :)
+
+So since it's largely unused and doesn't affect much, let's update uclibc
+and just check that a rebuild busybox tools still work,
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018003.html b/zarb-ml/mageia-dev/2012-August/018003.html new file mode 100644 index 000000000..6ac41d5f3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018003.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] Issue with latest Evolution (evolution-3.5.5-1.mga3) + + + + + + + + + +

[Mageia-dev] Issue with latest Evolution (evolution-3.5.5-1.mga3)

+ Olav Vitters + olav at vitters.nl +
+ Thu Aug 9 13:18:30 CEST 2012 +

+
+ +
On Wed, Aug 08, 2012 at 03:18:43PM +0200, Robert Fox wrote:
+> Lately, Evolution as been acting a bit odd - I have always had it set up
+> under Mail Preferences -> HTML Messages -> Loading Images -> set to
+> "Never Load Images from the Internet"
+[..]
+> Anybody have the same issue?
+
+Please just file a bug upstream:
+https://bugzilla.gnome.org/enter_bug.cgi?product=evolution
+
+IIRC in this version Evolution might switch from using gtkhtml to
+webkit... though don't recall changing the build requirements. In any
+case, best to let upstream know.
+
+If you want, cc me on upstream (bugzilla-gnome at vitters.nl)
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018004.html b/zarb-ml/mageia-dev/2012-August/018004.html new file mode 100644 index 000000000..38ac825fc --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018004.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release libappindicator-12.10.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release libappindicator-12.10.0-1.mga3

+ Olav Vitters + olav at vitters.nl +
+ Thu Aug 9 15:16:25 CEST 2012 +

+
+ +
On Thu, Aug 09, 2012 at 02:23:36PM +0200, shlomif wrote:
+> Name        : libappindicator              Relocations: (not relocatable)
+[..]
+> shlomif <shlomif> 12.10.0-1.mga3:
+> + Revision: 280137
+> - New version 12.10.0
+
+I thought these things required patches to GTK+? To be clear: I don't
+want GTK+ to rely on this.
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018005.html b/zarb-ml/mageia-dev/2012-August/018005.html new file mode 100644 index 000000000..2444dc359 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018005.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm + + + + + + + + + +

[Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm

+ Luis Daniel Lucio Quiroz + dlucio at okay.com.mx +
+ Thu Aug 9 16:56:11 CEST 2012 +

+
+ +
I dont find why this is failling
+
+objc is installed, what other could be?
+-------------- next part --------------
+An embedded message was scrubbed...
+From: Ulri the scheduler bot <mageia-sysadm at mageia.org>
+Subject: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm 
+Date: Thu, 09 Aug 2012 07:00:05 +0200
+Size: 3734
+URL: </pipermail/mageia-dev/attachments/20120809/c295b28f/attachment.mht>
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018006.html b/zarb-ml/mageia-dev/2012-August/018006.html new file mode 100644 index 000000000..7ed779d74 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018006.html @@ -0,0 +1,111 @@ + + + + [Mageia-dev] Conflict between glibc and kernel headers ? + + + + + + + + + +

[Mageia-dev] Conflict between glibc and kernel headers ?

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Aug 9 17:18:03 CEST 2012 +

+
+ +
I have the following error while trying to build wpa_supplicant:
+
+In file included from /usr/include/linux/sysinfo.h:4:0,
+                  from /usr/include/linux/kernel.h:4,
+                  from /usr/src/madwifi/include/compat.h:69,
+                  from ../src/drivers/driver_madwifi.c:37:
+/usr/include/linux/types.h:31:25: erreur: conflicting types for ‘u_int64_t’
+In file included from /usr/include/stdlib.h:319:0,
+                  from ../src/utils/includes.h:25,
+                  from ../src/drivers/driver_madwifi.c:22:
+/usr/include/sys/types.h:203:1: note: previous declaration of 
+‘u_int64_t’ was here
+make: *** [../src/drivers/driver_madwifi.o] Erreur 1
+
+If I'm understanding it correctly, there would be a mismatch between 
+/usr/include/linux/types.h (from the kernel) and 
+/usr/include/sys/types.h (from glibc). However, it's a bit difficult to 
+figure how they differ/conflict, as both declaration heavily relies on 
+preprocessing dark magic...
+
+glibc version:
+# define __u_intN_t(N, MODE) \
+   typedef unsigned int u_int##N##_t __attribute__ ((__mode__ (MODE)))
+__u_intN_t (64, __DI__);
+
+kernel version:
+typedef __u64 __bitwise __le64;
+
+So ?
+
+-- 
+BOFH excuse #69:
+
+knot in cables caused data stream to become twisted and kinked
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018007.html b/zarb-ml/mageia-dev/2012-August/018007.html new file mode 100644 index 000000000..b0b1caea9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018007.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm + + + + + + + + + +

[Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Aug 9 17:29:36 CEST 2012 +

+
+ +
Le 09/08/2012 16:56, Luis Daniel Lucio Quiroz a écrit :
+> I dont find why this is failling
+>
+> objc is installed, what other could be?
+Is there a way to retrieve the config.log file ?
+
+-- 
+BOFH excuse #141:
+
+disks spinning backwards - toggle the hemisphere jumper.
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018008.html b/zarb-ml/mageia-dev/2012-August/018008.html new file mode 100644 index 000000000..9449e2613 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018008.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm + + + + + + + + + +

[Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 17:39:25 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 4:29 PM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 09/08/2012 16:56, Luis Daniel Lucio Quiroz a écrit :
+>
+>> I dont find why this is failling
+>>
+>> objc is installed, what other could be?
+>
+> Is there a way to retrieve the config.log file ?
+
+I have some ideas but I would prefer not sharing them :)
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018009.html b/zarb-ml/mageia-dev/2012-August/018009.html new file mode 100644 index 000000000..e8640b3a7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018009.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm + + + + + + + + + +

[Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Aug 9 17:42:34 CEST 2012 +

+
+ +
Le 09/08/2012 17:39, Pascal Terjan a écrit :
+> On Thu, Aug 9, 2012 at 4:29 PM, Guillaume Rousse
+> <guillomovitch at gmail.com> wrote:
+>> Le 09/08/2012 16:56, Luis Daniel Lucio Quiroz a écrit :
+>>
+>>> I dont find why this is failling
+>>>
+>>> objc is installed, what other could be?
+>>
+>> Is there a way to retrieve the config.log file ?
+>
+> I have some ideas but I would prefer not sharing them :)
+You mean like running an exploit against the build host to check if it's 
+really vulnerable :) ?
+
+-- 
+The probability of diarrhea increases with the square of the thistle 
+content of the local vegetation
+		-- Murphy's Laws of Camping n°4
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018010.html b/zarb-ml/mageia-dev/2012-August/018010.html new file mode 100644 index 000000000..878a7ea25 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018010.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm + + + + + + + + + +

[Mageia-dev] Fwd: Rebuild failed on x86_64 for @280102:openvpn-2.2.2-6.mga3.src.rpm

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 17:54:39 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 4:42 PM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 09/08/2012 17:39, Pascal Terjan a écrit :
+>
+>> On Thu, Aug 9, 2012 at 4:29 PM, Guillaume Rousse
+>> <guillomovitch at gmail.com> wrote:
+>>>
+>>> Le 09/08/2012 16:56, Luis Daniel Lucio Quiroz a écrit :
+>>>
+>>>> I dont find why this is failling
+>>>>
+>>>> objc is installed, what other could be?
+>>>
+>>>
+>>> Is there a way to retrieve the config.log file ?
+>>
+>>
+>> I have some ideas but I would prefer not sharing them :)
+>
+> You mean like running an exploit against the build host to check if it's
+> really vulnerable :) ?
+
+After some irc discussion to improve the solution I don't want to
+post, we got a better one
+
+%configure || cat config.log
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018011.html b/zarb-ml/mageia-dev/2012-August/018011.html new file mode 100644 index 000000000..93a052f8f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018011.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] Suggested change to %configure + + + + + + + + + +

[Mageia-dev] Suggested change to %configure

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 18:00:18 CEST 2012 +

+
+ +
Would anyone oppose adding '|| (echo config.log; exit 1)' inside the macro ?
+
+That would help people debugging missing buildrequires on the build system
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018012.html b/zarb-ml/mageia-dev/2012-August/018012.html new file mode 100644 index 000000000..237d4105d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018012.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] Suggested change to %configure + + + + + + + + + +

[Mageia-dev] Suggested change to %configure

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 18:06:21 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 5:00 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> Would anyone oppose adding '|| (echo config.log; exit 1)' inside the macro ?
+>
+> That would help people debugging missing buildrequires on the build system
+
+Thinking more about it, this makes sense only on the build system, and
+I'd prefer not copy the macro to iurt config...
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018013.html b/zarb-ml/mageia-dev/2012-August/018013.html new file mode 100644 index 000000000..94b354ae0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018013.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] Suggested change to %configure + + + + + + + + + +

[Mageia-dev] Suggested change to %configure

+ Olivier Blin + mageia at blino.org +
+ Thu Aug 9 18:30:36 CEST 2012 +

+
+ +
Pascal Terjan <pterjan at gmail.com> writes:
+
+> Would anyone oppose adding '|| (echo config.log; exit 1)' inside the macro ?
+
+Wouldn't "cat" be a tad more useful than "echo" there? :)
+
+> That would help people debugging missing buildrequires on the build system
+
+Yep
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018014.html b/zarb-ml/mageia-dev/2012-August/018014.html new file mode 100644 index 000000000..169bb6c49 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018014.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 20:10:15 CEST 2012 +

+
+ +
Hi
+
+I've the impression that for some time, kernels do not power off machines
+anymore on shutdown.
+The kernel prints "System halted." but the machine remains powered.
+I've seen that with VMs and with real PCs.
+
+Does someone else see that?
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018015.html b/zarb-ml/mageia-dev/2012-August/018015.html new file mode 100644 index 000000000..7a3224253 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018015.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 20:18:42 CEST 2012 +

+
+ +
On 9 August 2012 20:10, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+> I've the impression that for some time, kernels do not power off machines
+> anymore on shutdown.
+> The kernel prints "System halted." but the machine remains powered.
+> I've seen that with VMs and with real PCs.
+>
+> Does someone else see that?
+
+Humm, in fact it looks like halt == shutdown -H now whereas in the
+old days it was equivalent to "shudown -P" (which still works OK).
+
+Since "halt" is now provided by systemd, this is were the regression
+come from...
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018016.html b/zarb-ml/mageia-dev/2012-August/018016.html new file mode 100644 index 000000000..843a3c92f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018016.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 20:29:01 CEST 2012 +

+
+ +
On 9 August 2012 20:18, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>> I've the impression that for some time, kernels do not power off machines
+>> anymore on shutdown.
+>> The kernel prints "System halted." but the machine remains powered.
+>> I've seen that with VMs and with real PCs.
+>>
+>> Does someone else see that?
+>
+> Humm, in fact it looks like halt == shutdown -H now whereas in the
+> old days it was equivalent to "shudown -P" (which still works OK).
+>
+> Since "halt" is now provided by systemd, this is were the regression
+> come from...
+
+I would suggests sg like this in order to restore previous behaviour
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: halt.diff
+Type: application/octet-stream
+Size: 843 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120809/334d1008/attachment.obj>
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018017.html b/zarb-ml/mageia-dev/2012-August/018017.html new file mode 100644 index 000000000..51c3ac57f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018017.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Olivier Blin + mageia at blino.org +
+ Thu Aug 9 20:35:02 CEST 2012 +

+
+ +
Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+
+> Hi
+>
+> I've the impression that for some time, kernels do not power off machines
+> anymore on shutdown.
+> The kernel prints "System halted." but the machine remains powered.
+> I've seen that with VMs and with real PCs.
+
+That's more likely related to systemd.
+How do you shutdown?
+
+The shutdown and halt commands will not automatically power off the
+system, you have to use halt -p from command line.
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018018.html b/zarb-ml/mageia-dev/2012-August/018018.html new file mode 100644 index 000000000..00a290c18 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018018.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Aug 9 20:45:37 CEST 2012 +

+
+ +
On 08/09/2012 02:35 PM, Olivier Blin wrote:
+> Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+>
+>> Hi
+>>
+>> I've the impression that for some time, kernels do not power off machines
+>> anymore on shutdown.
+>> The kernel prints "System halted." but the machine remains powered.
+>> I've seen that with VMs and with real PCs.
+>
+There was a discussion some months back about this (I forget whether it 
+was here or cooker).  Basically, someone discovered that "halt" had been 
+out-of-spec for years because it wasn't *supposed* to power the machine 
+off --- you were supposed to use "poweroff" for that. So it got "fixed", 
+and a bunch of people started asking "what happened ?".
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018019.html b/zarb-ml/mageia-dev/2012-August/018019.html new file mode 100644 index 000000000..338d95cdb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018019.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 21:04:16 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 7:45 PM, Frank Griffin <ftg at roadrunner.com> wrote:
+> On 08/09/2012 02:35 PM, Olivier Blin wrote:
+>>
+>> Thierry Vignaud <thierry.vignaud at gmail.com> writes:
+>>
+>>> Hi
+>>>
+>>> I've the impression that for some time, kernels do not power off machines
+>>> anymore on shutdown.
+>>> The kernel prints "System halted." but the machine remains powered.
+>>> I've seen that with VMs and with real PCs.
+>>
+>>
+> There was a discussion some months back about this (I forget whether it was
+> here or cooker).  Basically, someone discovered that "halt" had been
+> out-of-spec for years because it wasn't *supposed* to power the machine off
+> --- you were supposed to use "poweroff" for that. So it got "fixed", and a
+> bunch of people started asking "what happened ?".
+
+Yes because it totally makes sense to have a command to halt the
+operating system but leave the machine using some power for nothing
+(and preventing you from powering it on with wol). I am sure someone
+believes it can be useful in some strange scenario.
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018020.html b/zarb-ml/mageia-dev/2012-August/018020.html new file mode 100644 index 000000000..f5b57fd70 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018020.html @@ -0,0 +1,124 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 21:25:23 CEST 2012 +

+
+ +
'Twas brillig, and Thierry Vignaud at 09/08/12 19:29 did gyre and gimble:
+> On 9 August 2012 20:18, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>> I've the impression that for some time, kernels do not power off machines
+>>> anymore on shutdown.
+>>> The kernel prints "System halted." but the machine remains powered.
+>>> I've seen that with VMs and with real PCs.
+>>>
+>>> Does someone else see that?
+>>
+>> Humm, in fact it looks like halt == shutdown -H now whereas in the
+>> old days it was equivalent to "shudown -P" (which still works OK).
+>>
+>> Since "halt" is now provided by systemd, this is were the regression
+>> come from...
+> 
+> I would suggests sg like this in order to restore previous behaviour
+
+
+This has already been reported and I've simply closed the bugs and said
+that I will not fix this.
+
+What is the point in having two commands if they both do the same thing?
+I actually find the halt command useful for ensuring the correct thing
+happens on shutdown (e.g. that we re-enter the initrd and pivot root out
+of the main filesystem to ensure /usr us unmounted and LVM/raid etc.
+properly tidied up). If you cannot issue a halt, it's nigh on impossible
+to debug these things, so a patch to systemd would be IMO be a very bad
+idea. I wouldn't necessarily be completely against a patch that made
+running "halt" work differently to "systemctl halt", but such a patch
+would likely be ugly and it's certainly not going to be accepted
+upstream and it means inconsistent behaviour and as a result I'd rather
+just let people adapt to the current (and IMO correct) behaviour - I
+still maintain the old behaviour was broken and this that systemd simply
+restores what the behaviour should have been all along.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018021.html b/zarb-ml/mageia-dev/2012-August/018021.html new file mode 100644 index 000000000..e3ccb9390 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018021.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 21:31:45 CEST 2012 +

+
+ +
'Twas brillig, and Pascal Terjan at 09/08/12 20:04 did gyre and gimble:
+> Yes because it totally makes sense to have a command to halt the
+> operating system but leave the machine using some power for nothing
+> (and preventing you from powering it on with wol). I am sure someone
+> believes it can be useful in some strange scenario.
+
+It's very useful and it was essential for me during the previous release
+to debug shutdown logic.
+
+I want to see and read the debug that happens here and with a regular
+poweroff the debug disappears before you can read it. It's maybe not
+something you want to use regularly, but it doesn't mean it's not
+useful. There were always "poweroff" and "halt" commands - the names
+speak for themselves, it's just people got used to broken behaviour in
+the past. If you want to power your machine down, just type "poweroff".
+If you want to halt it, then type "halt". Kinda self explanatory really.
+Use the right tool for the right job :)
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018022.html b/zarb-ml/mageia-dev/2012-August/018022.html new file mode 100644 index 000000000..a44786229 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018022.html @@ -0,0 +1,113 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 21:32:04 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 8:25 PM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Thierry Vignaud at 09/08/12 19:29 did gyre and gimble:
+>> On 9 August 2012 20:18, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>>> I've the impression that for some time, kernels do not power off machines
+>>>> anymore on shutdown.
+>>>> The kernel prints "System halted." but the machine remains powered.
+>>>> I've seen that with VMs and with real PCs.
+>>>>
+>>>> Does someone else see that?
+>>>
+>>> Humm, in fact it looks like halt == shutdown -H now whereas in the
+>>> old days it was equivalent to "shudown -P" (which still works OK).
+>>>
+>>> Since "halt" is now provided by systemd, this is were the regression
+>>> come from...
+>>
+>> I would suggests sg like this in order to restore previous behaviour
+>
+>
+> This has already been reported and I've simply closed the bugs and said
+> that I will not fix this.
+>
+> What is the point in having two commands if they both do the same thing?
+> I actually find the halt command useful for ensuring the correct thing
+> happens on shutdown (e.g. that we re-enter the initrd and pivot root out
+> of the main filesystem to ensure /usr us unmounted and LVM/raid etc.
+> properly tidied up). If you cannot issue a halt, it's nigh on impossible
+> to debug these things, so a patch to systemd would be IMO be a very bad
+> idea. I wouldn't necessarily be completely against a patch that made
+> running "halt" work differently to "systemctl halt", but such a patch
+> would likely be ugly and it's certainly not going to be accepted
+> upstream and it means inconsistent behaviour and as a result I'd rather
+> just let people adapt to the current (and IMO correct) behaviour - I
+> still maintain the old behaviour was broken and this that systemd simply
+> restores what the behaviour should have been all along.
+
+The behavior has been incorrect for more than 10 years and everyone
+uses it like that.
+What is the point of changing the behavior in a way that will make it
+do something bad and annoying for most users?
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018023.html b/zarb-ml/mageia-dev/2012-August/018023.html new file mode 100644 index 000000000..85814e251 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018023.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 21:33:52 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 8:31 PM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Pascal Terjan at 09/08/12 20:04 did gyre and gimble:
+>> Yes because it totally makes sense to have a command to halt the
+>> operating system but leave the machine using some power for nothing
+>> (and preventing you from powering it on with wol). I am sure someone
+>> believes it can be useful in some strange scenario.
+>
+> It's very useful and it was essential for me during the previous release
+> to debug shutdown logic.
+
+But you are one of the very few people in the world interested in it,
+and you are doing something special (debugging) so you can run any
+command it.
+
+> I want to see and read the debug that happens here and with a regular
+> poweroff the debug disappears before you can read it. It's maybe not
+> something you want to use regularly, but it doesn't mean it's not
+> useful. There were always "poweroff" and "halt" commands - the names
+> speak for themselves, it's just people got used to broken behaviour in
+> the past. If you want to power your machine down, just type "poweroff".
+> If you want to halt it, then type "halt". Kinda self explanatory really.
+> Use the right tool for the right job :)
+
+But even since I know it has changed, 10 years habits had me typing
+halt and then saying some bad words as it meant I would not be able to
+power it on again for a few days.
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018024.html b/zarb-ml/mageia-dev/2012-August/018024.html new file mode 100644 index 000000000..3a4e056da --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018024.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 21:38:08 CEST 2012 +

+
+ +
'Twas brillig, and Pascal Terjan at 09/08/12 20:33 did gyre and gimble:
+> But even since I know it has changed, 10 years habits had me typing
+> halt and then saying some bad words as it meant I would not be able to
+> power it on again for a few days.
+
+OK, how about a compromise, "urpmi restore-broken-halt-command" which
+just contains a single file /etc/profile.d/99broken-halt-command.sh
+which contains:
+
+alias halt=poweroff
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018025.html b/zarb-ml/mageia-dev/2012-August/018025.html new file mode 100644 index 000000000..1d0faf8ff --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018025.html @@ -0,0 +1,117 @@ + + + + [Mageia-dev] Packaging request: GStreamer 1.0 / 0.11.93 + + + + + + + + + +

[Mageia-dev] Packaging request: GStreamer 1.0 / 0.11.93

+ Olav Vitters + olav at vitters.nl +
+ Thu Aug 9 21:42:51 CEST 2012 +

+
+ +
Could someone package Gstreamer 1.0?
+
+GNOME 3.6 will require GStreamer 1.0. At least sound-juicer currently
+cannot be built due to missing gstreamer 1.0 package. The plan is that
+all the "Core" GNOME applications are ported to the GStreamer 1.0 API
+before GNOME 3.6.0
+
+At the moment Gstreamer 1.0 has version 0.11.93. Gstreamer 1.0 is
+parallel installable with 0.10.
+
+Fedora has called the 1.0 packages with an "1", e.g. gstreamer1. I
+didn't notice any packaged 1.0 plugins.
+
+OpenSUSE has called the 1.0 packages just 'gstreamer',
+'gstreamer-plugins-good', etc. Their 0.10 are e.g.
+gstreamer-0_10-plugins-good.
+
+URL:
+http://gstreamer.freedesktop.org/src/
+http://download.gnome.org/sources/gstreamer/0.11/gstreamer-0.11.93.tar.xz
+
+Suggest packaging at least:
+gstreamer 0.11.93
+gst-plugins-good 0.11.93
+gst-plugins-base 0.11.93
+
+
+Many thanks!
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018026.html b/zarb-ml/mageia-dev/2012-August/018026.html new file mode 100644 index 000000000..372872838 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018026.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 9 21:44:52 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 8:38 PM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Pascal Terjan at 09/08/12 20:33 did gyre and gimble:
+>> But even since I know it has changed, 10 years habits had me typing
+>> halt and then saying some bad words as it meant I would not be able to
+>> power it on again for a few days.
+>
+> OK, how about a compromise, "urpmi restore-broken-halt-command" which
+> just contains a single file /etc/profile.d/99broken-halt-command.sh
+> which contains:
+>
+> alias halt=poweroff
+>
+
+Well my own machine already has halt='halt -p' since the day I lost it
+like that :)
+What annoys me is that I don't see the point of changing the default
+behavior of a (quite important) command while the new default is
+something people would only want to use in very rare cases and will
+cause problems to most of them.
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018027.html b/zarb-ml/mageia-dev/2012-August/018027.html new file mode 100644 index 000000000..48e937916 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018027.html @@ -0,0 +1,121 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 21:51:06 CEST 2012 +

+
+ +
'Twas brillig, and Pascal Terjan at 09/08/12 20:44 did gyre and gimble:
+> On Thu, Aug 9, 2012 at 8:38 PM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>> 'Twas brillig, and Pascal Terjan at 09/08/12 20:33 did gyre and gimble:
+>>> But even since I know it has changed, 10 years habits had me typing
+>>> halt and then saying some bad words as it meant I would not be able to
+>>> power it on again for a few days.
+>>
+>> OK, how about a compromise, "urpmi restore-broken-halt-command" which
+>> just contains a single file /etc/profile.d/99broken-halt-command.sh
+>> which contains:
+>>
+>> alias halt=poweroff
+>>
+> 
+> Well my own machine already has halt='halt -p' since the day I lost it
+> like that :)
+> What annoys me is that I don't see the point of changing the default
+> behavior of a (quite important) command while the new default is
+> something people would only want to use in very rare cases and will
+> cause problems to most of them.
+
+Well, for me personally, I always prefer to fix things that are broken
+and not use history as an excuse for keeping broken behaviour. It
+doesn't take long to adapt to new commands and the people of the future
+will never need to learn the history behind why such a quirk exists.
+
+Anyway, I very much do not want to patch systemd to change upstream
+behaviour here. If we have to work around it then someone who cares
+enough can create the package as I suggested above, or take the cause to
+upstream systemd and get them to change the behaviour.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018028.html b/zarb-ml/mageia-dev/2012-August/018028.html new file mode 100644 index 000000000..1bcff7e1e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018028.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 21:52:20 CEST 2012 +

+
+ +
On 9 August 2012 21:31, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Pascal Terjan at 09/08/12 20:04 did gyre and gimble:
+>> Yes because it totally makes sense to have a command to halt the
+>> operating system but leave the machine using some power for nothing
+>> (and preventing you from powering it on with wol). I am sure someone
+>> believes it can be useful in some strange scenario.
+>
+> It's very useful and it was essential for me during the previous release
+> to debug shutdown logic.
+
+That's off topic.
+We hide kernel messages on boot despite them being usefull for debugging
+
+And for end users, it's horrible: they think the computer is frozen.
+If they didn't press <escape> before, they've no way to understand what
+happen!
+
+> I want to see and read the debug that happens here and with a regular
+> poweroff the debug disappears before you can read it. It's maybe not
+> something you want to use regularly, but it doesn't mean it's not
+> useful. There were always "poweroff" and "halt" commands - the names
+> speak for themselves, it's just people got used to broken behaviour in
+> the past. If you want to power your machine down, just type "poweroff".
+> If you want to halt it, then type "halt". Kinda self explanatory really.
+> Use the right tool for the right job :)
+
+Yet it's again 12 years of pratice, against documentation on internet
+and the like
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018029.html b/zarb-ml/mageia-dev/2012-August/018029.html new file mode 100644 index 000000000..2e4f862d4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018029.html @@ -0,0 +1,126 @@ + + + + [Mageia-dev] Packaging request: GStreamer 1.0 / 0.11.93 + + + + + + + + + +

[Mageia-dev] Packaging request: GStreamer 1.0 / 0.11.93

+ D.Morgan + dmorganec at gmail.com +
+ Thu Aug 9 21:55:22 CEST 2012 +

+
+ +
On Thu, Aug 9, 2012 at 9:42 PM, Olav Vitters <olav at vitters.nl> wrote:
+> Could someone package Gstreamer 1.0?
+>
+> GNOME 3.6 will require GStreamer 1.0. At least sound-juicer currently
+> cannot be built due to missing gstreamer 1.0 package. The plan is that
+> all the "Core" GNOME applications are ported to the GStreamer 1.0 API
+> before GNOME 3.6.0
+>
+> At the moment Gstreamer 1.0 has version 0.11.93. Gstreamer 1.0 is
+> parallel installable with 0.10.
+>
+> Fedora has called the 1.0 packages with an "1", e.g. gstreamer1. I
+> didn't notice any packaged 1.0 plugins.
+>
+> OpenSUSE has called the 1.0 packages just 'gstreamer',
+> 'gstreamer-plugins-good', etc. Their 0.10 are e.g.
+> gstreamer-0_10-plugins-good.
+>
+> URL:
+> http://gstreamer.freedesktop.org/src/
+> http://download.gnome.org/sources/gstreamer/0.11/gstreamer-0.11.93.tar.xz
+>
+> Suggest packaging at least:
+> gstreamer 0.11.93
+> gst-plugins-good 0.11.93
+> gst-plugins-base 0.11.93
+>
+>
+> Many thanks!
+>
+> --
+> Regards,
+> Olav
+
+Hi,
+
+i started before going in vacations ( see
+http://svnweb.mageia.org/packages/cauldron/gstreamer1.0/ )
+
+the patch needs to be fixed ( see line 235 ).
+
+if someone wants to continue please do if not i will when back ( i
+have nearly no internet access for now )
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018030.html b/zarb-ml/mageia-dev/2012-August/018030.html new file mode 100644 index 000000000..9609daaee --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018030.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 21:55:20 CEST 2012 +

+
+ +
On 9 August 2012 21:51, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>>> But even since I know it has changed, 10 years habits had me typing
+>>>> halt and then saying some bad words as it meant I would not be able to
+>>>> power it on again for a few days.
+>>>
+>>> OK, how about a compromise, "urpmi restore-broken-halt-command" which
+>>> just contains a single file /etc/profile.d/99broken-halt-command.sh
+>>> which contains:
+>>>
+>>> alias halt=poweroff
+>>>
+>>
+>> Well my own machine already has halt='halt -p' since the day I lost it
+>> like that :)
+>> What annoys me is that I don't see the point of changing the default
+>> behavior of a (quite important) command while the new default is
+>> something people would only want to use in very rare cases and will
+>> cause problems to most of them.
+>
+> Well, for me personally, I always prefer to fix things that are broken
+> and not use history as an excuse for keeping broken behaviour.
+
+I could counter argue that's a lame excuse for breaking existing documented
+behavior. Scores of people rely on that behavior.
+
+What's more it's an established behavior in some communauties (eg: the kernel
+one) to not break usage for the purpose to fix things if it breaks
+existing apps or
+usage.
+
+> It
+> doesn't take long to adapt to new commands and the people of the future
+> will never need to learn the history behind why such a quirk exists.
+
+And what about DMs that call "halt" ?
+
+> Anyway, I very much do not want to patch systemd to change upstream
+> behaviour here. If we have to work around it then someone who cares
+> enough can create the package as I suggested above, or take the cause to
+> upstream systemd and get them to change the behaviour.
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018031.html b/zarb-ml/mageia-dev/2012-August/018031.html new file mode 100644 index 000000000..8e40ee4d6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018031.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Thu Aug 9 22:18:59 CEST 2012 +

+
+ +
Under cauldron I do over a project at work:
+
+[olivier at localhost forge]$ LC_ALL=C urpmi --buildrequires forge.spec 
+
+
+installing forge.spec
+Preparing...
+#############################################################################################################################################################
+error: perl-Forge-0.4.5-1.mga3.noarch: install failed
+
+In past trying to install a spec did not end by an erreur (even
+--buildrequires was not specified).
+
+Can we back to a more standard behavior ?
+
+Moreover french translation is wrong:
+"erreur : perl-Forge-0.4.5-1.mga3.noarch: installer échoué"
+but mayve this should be reported elsewhere.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120809/d449bb88/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018032.html b/zarb-ml/mageia-dev/2012-August/018032.html new file mode 100644 index 000000000..a6f36c39e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018032.html @@ -0,0 +1,132 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 9 22:28:21 CEST 2012 +

+
+ +
'Twas brillig, and Thierry Vignaud at 09/08/12 20:55 did gyre and gimble:
+> On 9 August 2012 21:51, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>>>> But even since I know it has changed, 10 years habits had me typing
+>>>>> halt and then saying some bad words as it meant I would not be able to
+>>>>> power it on again for a few days.
+>>>>
+>>>> OK, how about a compromise, "urpmi restore-broken-halt-command" which
+>>>> just contains a single file /etc/profile.d/99broken-halt-command.sh
+>>>> which contains:
+>>>>
+>>>> alias halt=poweroff
+>>>>
+>>>
+>>> Well my own machine already has halt='halt -p' since the day I lost it
+>>> like that :)
+>>> What annoys me is that I don't see the point of changing the default
+>>> behavior of a (quite important) command while the new default is
+>>> something people would only want to use in very rare cases and will
+>>> cause problems to most of them.
+>>
+>> Well, for me personally, I always prefer to fix things that are broken
+>> and not use history as an excuse for keeping broken behaviour.
+> 
+> I could counter argue that's a lame excuse for breaking existing documented
+> behavior. Scores of people rely on that behavior.
+> 
+> What's more it's an established behavior in some communauties (eg: the kernel
+> one) to not break usage for the purpose to fix things if it breaks
+> existing apps or
+> usage.
+
+Well as I've said if you can convince upstream I'll happily go with
+that. I do not want to introduce patches for this, although I will be
+happy enough with a workaround.
+
+>> It
+>> doesn't take long to adapt to new commands and the people of the future
+>> will never need to learn the history behind why such a quirk exists.
+> 
+> And what about DMs that call "halt" ?
+
+They can, and should be updated to call poweroff instead. Or better to
+integrate into dbus and call things that way (which is needed to provide
+nice warnings about other users/sessions etc. anyway).
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018033.html b/zarb-ml/mageia-dev/2012-August/018033.html new file mode 100644 index 000000000..69ee589c1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018033.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 22:35:59 CEST 2012 +

+
+ +
On 9 August 2012 22:18, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> Under cauldron I do over a project at work:
+>
+> [olivier at localhost forge]$ LC_ALL=C urpmi --buildrequires forge.spec
+>
+>
+> installing forge.spec
+> Preparing...
+> #############################################################################################################################################################
+> error: perl-Forge-0.4.5-1.mga3.noarch: install failed
+>
+> In past trying to install a spec did not end by an erreur (even
+> --buildrequires was not specified).
+>
+> Can we back to a more standard behavior ?
+
+That has nothing to do with urpmi.
+That message came from rpm.
+Your package is bogus.
+
+Regards.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018034.html b/zarb-ml/mageia-dev/2012-August/018034.html new file mode 100644 index 000000000..a9a3c7335 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018034.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Packaging request: GStreamer 1.0 / 0.11.93 + + + + + + + + + +

[Mageia-dev] Packaging request: GStreamer 1.0 / 0.11.93

+ Olav Vitters + olav at vitters.nl +
+ Thu Aug 9 22:37:04 CEST 2012 +

+
+ +
On Thu, Aug 09, 2012 at 09:55:22PM +0200, Dexter Morgan wrote:
+> i started before going in vacations ( see
+> http://svnweb.mageia.org/packages/cauldron/gstreamer1.0/ )
+> 
+> the patch needs to be fixed ( see line 235 ).
+> 
+> if someone wants to continue please do if not i will when back ( i
+> have nearly no internet access for now )
+
+Cool!
+
+I don't have the skills to fix the patch, but nice to know there was
+already progress on gstreamer 1.0!
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018035.html b/zarb-ml/mageia-dev/2012-August/018035.html new file mode 100644 index 000000000..07021d874 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018035.html @@ -0,0 +1,126 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Thu Aug 9 22:42:32 CEST 2012 +

+
+ +
* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> On 9 August 2012 22:18, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> > Under cauldron I do over a project at work:
+> >
+> > [olivier at localhost forge]$ LC_ALL=C urpmi --buildrequires forge.spec
+> >
+> >
+> > installing forge.spec
+> > Preparing...
+> > #############################################################################################################################################################
+> > error: perl-Forge-0.4.5-1.mga3.noarch: install failed
+> >
+> > In past trying to install a spec did not end by an erreur (even
+> > --buildrequires was not specified).
+> >
+> > Can we back to a more standard behavior ?
+> 
+> That has nothing to do with urpmi.
+> That message came from rpm.
+> Your package is bogus.
+
+Hu ?
+
+In what the spec file can be bogus (and not the package)?
+
+No message is ouput but indeed, a spec file is not a noarch rpm and I
+don't see why urpmi/rpm assume I'am installing a noarch rpm from spec
+file.
+
+
+
+> 
+> Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120809/706231bf/attachment-0001.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018036.html b/zarb-ml/mageia-dev/2012-August/018036.html new file mode 100644 index 000000000..5295e0993 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018036.html @@ -0,0 +1,116 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 9 22:47:50 CEST 2012 +

+
+ +
On 9 August 2012 22:42, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+>> > [olivier at localhost forge]$ LC_ALL=C urpmi --buildrequires forge.spec
+>> >
+>> >
+>> > installing forge.spec
+>> > Preparing...
+>> > #############################################################################################################################################################
+>> > error: perl-Forge-0.4.5-1.mga3.noarch: install failed
+>> >
+>> > In past trying to install a spec did not end by an erreur (even
+>> > --buildrequires was not specified).
+>> >
+>> > Can we back to a more standard behavior ?
+>>
+>> That has nothing to do with urpmi.
+>> That message came from rpm.
+>> Your package is bogus.
+>
+> Hu ?
+>
+> In what the spec file can be bogus (and not the package)?
+>
+> No message is ouput but indeed, a spec file is not a noarch rpm and I
+> don't see why urpmi/rpm assume I'am installing a noarch rpm from spec
+> file.
+
+Sorry but I really don't understand what you try to tell.
+
+What's the link with "assume I'am installing a noarch rpm" and
+"from spec file" ???
+
+You asked urpmi to install missing BR from the spec, it tries
+to do so, and one of the needed BR is provided by this perl-Forge
+package of yours (so we can't check it) and it must do something
+very weird (maybe silent error in %pre, I really can't tell w/o
+looking at that package).
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018037.html b/zarb-ml/mageia-dev/2012-August/018037.html new file mode 100644 index 000000000..cbef0ea53 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018037.html @@ -0,0 +1,143 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Fri Aug 10 00:07:12 CEST 2012 +

+
+ +
* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> 
+> What's the link with "assume I'am installing a noarch rpm" and
+> "from spec file" ???
+> 
+> You asked urpmi to install missing BR from the spec, it tries
+> to do so, and one of the needed BR is provided by this perl-Forge
+> package of yours (so we can't check it) and it must do something
+> very weird (maybe silent error in %pre, I really can't tell w/o
+> looking at that package).
+
+There is no buidrequires related to perl-Forge in this spec and there is
+no error output (perl-Forge is the name of this package).
+
+Urpmi wrongly assumed the spec file as binary package:
+
+Example:
+
+QUOTE:
+    %define name toto
+    %define version 1
+    %define release %mkrel 1
+
+    Summary: test
+    Name: %{name}
+    Version: %{version}
+    Release: %{release}
+    License: GPL
+    Group: test
+    BuildRoot: %{_tmppath}/%{name}-buildroot
+
+    %description
+    test
+
+    %files
+    %defattr(-,root,root)
+END QUOTE
+
+$ urpmi toto.spec
+error: toto-1-1.mga3.x86_64: install failed
+
+Now if replace the name by prboom (installed):
+
+A requested package cannot be installed:
+prboom-1-1.mga3.x86_64 (in order to keep prboom-2.5.0-10.mga3.x86_64)
+
+So clearly the specfile is treat as a binary rpm and the error reported
+incorrectly.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120810/a59ebcc9/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018038.html b/zarb-ml/mageia-dev/2012-August/018038.html new file mode 100644 index 000000000..cc112b221 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018038.html @@ -0,0 +1,119 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 10 00:14:18 CEST 2012 +

+
+ +
On 10 August 2012 00:07, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> Urpmi wrongly assumed the spec file as binary package:
+>
+> Example:
+>
+> QUOTE:
+>     %define name toto
+>     %define version 1
+>     %define release %mkrel 1
+>
+>     Summary: test
+>     Name: %{name}
+>     Version: %{version}
+>     Release: %{release}
+>     License: GPL
+>     Group: test
+>     BuildRoot: %{_tmppath}/%{name}-buildroot
+>
+>     %description
+>     test
+>
+>     %files
+>     %defattr(-,root,root)
+> END QUOTE
+>
+> $ urpmi toto.spec
+> error: toto-1-1.mga3.x86_64: install failed
+>
+> Now if replace the name by prboom (installed):
+>
+> A requested package cannot be installed:
+> prboom-1-1.mga3.x86_64 (in order to keep prboom-2.5.0-10.mga3.x86_64)
+>
+> So clearly the specfile is treat as a binary rpm and the error reported
+> incorrectly.
+
+ah OK.
+It's b/c of this commit
+http://svnweb.mageia.org/soft/rpm/perl-URPM/trunk/URPM.xs?r1=5029&r2=5031
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018039.html b/zarb-ml/mageia-dev/2012-August/018039.html new file mode 100644 index 000000000..e1b2438ad --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018039.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 10 00:20:50 CEST 2012 +

+
+ +
On 10 August 2012 00:14, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>> $ urpmi toto.spec
+>> error: toto-1-1.mga3.x86_64: install failed
+>>
+>> Now if replace the name by prboom (installed):
+>>
+>> A requested package cannot be installed:
+>> prboom-1-1.mga3.x86_64 (in order to keep prboom-2.5.0-10.mga3.x86_64)
+>>
+>> So clearly the specfile is treat as a binary rpm and the error reported
+>> incorrectly.
+>
+> ah OK.
+> It's b/c of this commit
+> http://svnweb.mageia.org/soft/rpm/perl-URPM/trunk/URPM.xs?r1=5029&r2=5031
+
+The following patch fixes it.
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: a.diff
+Type: application/octet-stream
+Size: 520 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120810/e2b5927e/attachment.obj>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018040.html b/zarb-ml/mageia-dev/2012-August/018040.html new file mode 100644 index 000000000..f5818abdd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018040.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Urpmi raise an erreur when installing a .spec file + + + + + + + + + +

[Mageia-dev] Urpmi raise an erreur when installing a .spec file

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 10 00:31:01 CEST 2012 +

+
+ +
On 10 August 2012 00:20, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>> ah OK.
+>> It's b/c of this commit
+>> http://svnweb.mageia.org/soft/rpm/perl-URPM/trunk/URPM.xs?r1=5029&r2=5031
+>
+> The following patch fixes it.
+
+Or even simpler:
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: b.diff
+Type: application/octet-stream
+Size: 597 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120810/7d0a53d3/attachment.obj>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018041.html b/zarb-ml/mageia-dev/2012-August/018041.html new file mode 100644 index 000000000..e60e0af5d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018041.html @@ -0,0 +1,142 @@ + + + + [Mageia-dev] Missing in Action - 3G F5521gw + + + + + + + + + +

[Mageia-dev] Missing in Action - 3G F5521gw

+ Robert Fox + rfox at foxconsult.com +
+ Fri Aug 10 08:56:19 CEST 2012 +

+
+ +
+Since the latest kernel updates in Cauldron - I am no longer able to see
+my WAN modem again (Ericsson F5521gw)
+
+The solution below doesn't work either . . . 
+
+[root at ThinkFox rfox]# lsmod | grep cdc
+cdc_ncm                18345  0 
+usbnet                 36447  1 cdc_ncm
+cdc_wdm                18885  0 
+cdc_acm                28752  0 
+usbcore               212051  9
+btusb,uvcvideo,ehci_hcd,usbhid,usbnet,cdc_acm,cdc_ncm,cdc_wdm,xhci_hcd
+[root at ThinkFox rfox]# mount -n -t usbfs -o
+devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb
+mount: mount point /proc/bus/usb does not exist
+
+Looks like /proc/bus/ doesn't have usb anymore:
+[root at ThinkFox rfox]# ls /proc/bus/
+input/ pci/
+
+Should I raise a bug?
+
+Thx,
+R.Fox
+
+On Wed, 2012-03-28 at 09:15 +0100, Colin Guthrie wrote:
+> 'Twas brillig, and Robert Fox at 27/03/12 20:11 did gyre and gimble:
+> > Since recent Cauldron updates, I can't get my 3G card (Ericsson F5521gw)
+> > to work - looks like the modules are loading:
+> > 
+> > [root at ThinkFox rfox]# lsmod | grep cdc
+> > cdc_ncm                18343  0 
+> > usbnet                 32360  1 cdc_ncm
+> > cdc_acm                28712  0 
+> > cdc_wdm                18241  0 
+> > usbcore               206950  10
+> > uvcvideo,btusb,cdc_ncm,usbnet,cdc_acm,cdc_wdm,xhci_hcd,usbhid,ehci_hcd
+> > 
+> > but when I start drakconnect, I get "no device for this connection type"
+> > 
+> > On the same notebook (Thinkpad x220) it works fine under Ubuntu 12.04
+> > B1)
+> > 
+> > Any hints would be welcome.
+> 
+> Try running as root:
+> 
+> mount -n -t usbfs -o devmode=0664,devgid=43 /proc/bus/usb /proc/bus/usb
+> 
+> 
+> Then run drakconnect.
+> 
+> aka: https://bugs.mageia.org/show_bug.cgi?id=4500
+> 
+> Col
+> 
+
+
+
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018042.html b/zarb-ml/mageia-dev/2012-August/018042.html new file mode 100644 index 000000000..5d131633e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018042.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Fri Aug 10 10:39:30 CEST 2012 +

+
+ +
On Thu, 9 Aug 2012, Colin Guthrie wrote:
+
+> 'Twas brillig, and Pascal Terjan at 09/08/12 20:04 did gyre and gimble:
+>> Yes because it totally makes sense to have a command to halt the
+>> operating system but leave the machine using some power for nothing
+>> (and preventing you from powering it on with wol). I am sure someone
+>> believes it can be useful in some strange scenario.
+>
+> It's very useful and it was essential for me during the previous release
+> to debug shutdown logic.
+
+The shutdown command has always been used for this. Apparently you need to 
+pass -H to it now, though. To power off aka 'halt' a machine, shutdown -h 
+was used and this still works according to the manpage.
+
+
+Please read the halt manpage (and others):
+
+"These are legacy commands available for compatibility only."
+
+So you arguing its behavior is now "fixed" because it was "broken" does 
+not make sense.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018043.html b/zarb-ml/mageia-dev/2012-August/018043.html new file mode 100644 index 000000000..850585036 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018043.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Olivier Blin + mageia at blino.org +
+ Fri Aug 10 14:30:31 CEST 2012 +

+
+ +
Christiaan Welvaart <cjw at daneel.dyndns.org> writes:
+
+> On Thu, 9 Aug 2012, Colin Guthrie wrote:
+>
+>> 'Twas brillig, and Pascal Terjan at 09/08/12 20:04 did gyre and gimble:
+>>> Yes because it totally makes sense to have a command to halt the
+>>> operating system but leave the machine using some power for nothing
+>>> (and preventing you from powering it on with wol). I am sure someone
+>>> believes it can be useful in some strange scenario.
+>>
+>> It's very useful and it was essential for me during the previous release
+>> to debug shutdown logic.
+>
+> The shutdown command has always been used for this.
+
+But with the previous initscripts/sysvinit, the halt command was
+eventually handled by /etc/init.d/halt, which automatically passed the
+-p argument to halt.
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018044.html b/zarb-ml/mageia-dev/2012-August/018044.html new file mode 100644 index 000000000..f0fd67574 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018044.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Jose Jorge + lists.jjorge at free.fr +
+ Fri Aug 10 20:04:11 CEST 2012 +

+
+ +
Le 09/08/2012 20:10, Thierry Vignaud a écrit :
+> Hi
+>
+> I've the impression that for some time, kernels do not power off machines
+> anymore on shutdown.
+> The kernel prints "System halted." but the machine remains powered.
+> I've seen that with VMs and with real PCs.
+>
+> Does someone else see that?
+Yes, and some other distros do the same (at least Slitaz). Before Mageia 
+2, there was no interest in having both halt and poweroff doing the same.
+
+Now, we can do "poweroff" to cut the power after stopping the kernel, or 
+"halt" to keep  the power on.
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018045.html b/zarb-ml/mageia-dev/2012-August/018045.html new file mode 100644 index 000000000..834ddcb25 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018045.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 10 21:11:24 CEST 2012 +

+
+ +
On Fri, Aug 10, 2012 at 7:04 PM, Jose Jorge <lists.jjorge at free.fr> wrote:
+> Le 09/08/2012 20:10, Thierry Vignaud a écrit :
+>
+>> Hi
+>>
+>> I've the impression that for some time, kernels do not power off machines
+>> anymore on shutdown.
+>> The kernel prints "System halted." but the machine remains powered.
+>> I've seen that with VMs and with real PCs.
+>>
+>> Does someone else see that?
+>
+> Yes, and some other distros do the same (at least Slitaz). Before Mageia 2,
+> there was no interest in having both halt and poweroff doing the same.
+>
+> Now, we can do "poweroff" to cut the power after stopping the kernel, or
+> "halt" to keep  the power on.
+
+How many people expect their machine to power off when they type halt?
+How many people will want their machine to not halt and not poweroff?
+
+Said in another way:
+- How many people will this change cause problem to?
+- How many people will benefit from it?
+
+I would expect the ratio to be about at least 99.9/0.1 which is why I hate it.
+
+This change seem to be done without any consideration for users.
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018046.html b/zarb-ml/mageia-dev/2012-August/018046.html new file mode 100644 index 000000000..483bc93ce --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018046.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Fri Aug 10 21:27:50 CEST 2012 +

+
+ +
On Fri, 10 Aug 2012, Pascal Terjan wrote:
+
+> On Fri, Aug 10, 2012 at 7:04 PM, Jose Jorge <lists.jjorge at free.fr> wrote:
+>> Le 09/08/2012 20:10, Thierry Vignaud a écrit :
+>>
+>>> I've the impression that for some time, kernels do not power off machines
+>>> anymore on shutdown.
+>>> The kernel prints "System halted." but the machine remains powered.
+>>> I've seen that with VMs and with real PCs.
+>>>
+>>> Does someone else see that?
+>>
+>> Yes, and some other distros do the same (at least Slitaz). Before Mageia 2,
+>> there was no interest in having both halt and poweroff doing the same.
+>>
+>> Now, we can do "poweroff" to cut the power after stopping the kernel, or
+>> "halt" to keep  the power on.
+
+As I said earlier, if you are looking for these system shutdown commands, 
+use:
+   systemctl reboot
+   systemctl halt
+   systemctl poweroff
+directly. The "halt, "reboot", and "poweroff" commands are only there for 
+backwards compatibility.
+
+> How many people expect their machine to power off when they type halt?
+> How many people will want their machine to not halt and not poweroff?
+>
+> Said in another way:
+> - How many people will this change cause problem to?
+> - How many people will benefit from it?
+>
+> I would expect the ratio to be about at least 99.9/0.1 which is why I hate it.
+>
+> This change seem to be done without any consideration for users.
+
+So fix it, no change to systemctl is needed AFAICT, just replace the 
+symlink with a tool that does "the right thing", probably running 
+"poweroff" passing all arguments verbatim. Don't forget to fix the 
+manpage as well.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018047.html b/zarb-ml/mageia-dev/2012-August/018047.html new file mode 100644 index 000000000..d7359264c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018047.html @@ -0,0 +1,186 @@ + + + + [Mageia-dev] Security updates - help needed! + + + + + + + + + +

[Mageia-dev] Security updates - help needed!

+ David Walser + luigiwalser at yahoo.com +
+ Fri Aug 10 21:56:08 CEST 2012 +

+
+ +
I've picked off all of the low-hanging fruit, so the remaining packages on this list really do need help to get fixed.
+
+......... updated initial message below ........
+
+There are several packages that need security updates that either have not been built yet, or there are some issues that need help and/or input from packagers.
+
+Please help out with these where you can.
+
+I'll try to organize these into categories and give a little info on them so it's easy to see if you can and want to help.
+
+Web apps
+--------
+ocsinventory - Mageia 1 package needs to be updated or patched (patches available from MDV)
+https://bugs.mageia.org/show_bug.cgi?id=5252
+https://bugs.mageia.org/show_bug.cgi?id=2129
+
+mediawiki - versions we have are at or nearing EOL upstream, probably should be updated.  Oliver Burger is working on this.
+https://bugs.mageia.org/show_bug.cgi?id=3448
+
+drupal - update built, issues found by QA need fixing.  Oliver Burger is working on this.
+https://bugs.mageia.org/show_bug.cgi?id=5844
+
+GNOME software
+--------------
+mono - upstream commit linked
+https://bugs.mageia.org/show_bug.cgi?id=6789
+
+libvirt - patch available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6526
+
+libguestfs - patch available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6818
+
+gjs - doesn't rebuild against xulrunner in Mageia 1, but doesn't seem to be used by anything
+https://bugs.mageia.org/show_bug.cgi?id=6382
+
+Games
+-----
+openarena, alienarena - affected by DoS bug in quake3 engine.  Juan Luis Baptiste is working on this.
+https://bugs.mageia.org/show_bug.cgi?id=5496
+
+Java-related
+------------
+jruby - fixed upstream in 1.6.5.1
+https://bugs.mageia.org/show_bug.cgi?id=6742
+
+poi - In progress by D Morgan.  Additional updates pending.
+https://bugs.mageia.org/show_bug.cgi?id=6011
+
+apache-commons-compress - In progress by D Morgan.  Mageia 1 updates pending.
+https://bugs.mageia.org/show_bug.cgi?id=6331
+
+apache-commons-daemon - fixed upstream in 1.0.7 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7004
+
+Ruby-related
+------------
+Several security issues, one possible packaging issue
+https://bugs.mageia.org/show_bug.cgi?id=6487
+
+No response has been received from packagers yet
+------------------------------------------------
+ganglia - patch available from Fedora, we have another bug report saying it doesn't start
+https://bugs.mageia.org/show_bug.cgi?id=6874
+
+libreoffice - Mageia 1 only, patch available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6944
+
+stunnel - package has several other issues as well, should probably just be updated
+https://bugs.mageia.org/show_bug.cgi?id=3951
+
+phpmyadmin - needs updated to 3.5.2.1 and fixed in Cauldron for new apache conf layout
+https://bugs.mageia.org/show_bug.cgi?id=6905
+
+python-django - issues fixed upstream in 1.3.2.  Philippe Makowski said he'll work on this.
+https://bugs.mageia.org/show_bug.cgi?id=6986
+
+empathy - XSS issues fixed upstream in 3.2.1 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7008
+
+abrt/libreport/btparser - should probably be upgraded to newer versions available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6523
+
+sos - 62 patches available from Fedora
+https://bugs.mageia.org/show_bug.cgi?id=6525
+
+x11-server - upstream diffs linked by RedHat, maybe patches available from Ubuntu or Gentoo, plus other security issues fixed by RH/OpenSuSE/Ubuntu
+https://bugs.mageia.org/show_bug.cgi?id=6744
+
+In progress (help needed to finish)
+-----------------------------------
+dhcp - issues fixed upstream in 4.2.4-P1
+https://bugs.mageia.org/show_bug.cgi?id=6872
+
+bind - issues fixed upstream in 9.8.3-P2 and 9.9.1-P2
+https://bugs.mageia.org/show_bug.cgi?id=6873
+
+xen - doesn't build in Cauldron (incompatible pointer type in i8259.c)
+https://bugs.mageia.org/show_bug.cgi?id=6931
+
+gc - links to upstream and Fedora patches available in bug, already fixed in Cauldron
+https://bugs.mageia.org/show_bug.cgi?id=6652
+
+bip - patch in Mageia 1 didn't fix it according to QA, patch wasn't applied in Mageia 2
+https://bugs.mageia.org/show_bug.cgi?id=4319
+
+emacs - re-diffing patch for Emacs 23.2 (Mageia 1) is non-trivial
+https://bugs.mageia.org/show_bug.cgi?id=6995
+
+psi - fixed in SVN, does not build in Cauldron (can't find qca2-devel even though it's installed)
+https://bugs.mageia.org/show_bug.cgi?id=7002
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018048.html b/zarb-ml/mageia-dev/2012-August/018048.html new file mode 100644 index 000000000..4497f0c3d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018048.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] latest kernels not powering off machines on shutdown + + + + + + + + + +

[Mageia-dev] latest kernels not powering off machines on shutdown

+ Digigold + digigold808 at gmail.com +
+ Sat Aug 11 00:12:41 CEST 2012 +

+
+ +
On 08/10/2012 03:27 PM, Christiaan Welvaart wrote:
+> On Fri, 10 Aug 2012, Pascal Terjan wrote:
+>
+>> How many people expect their machine to power off when they type halt?
+>> How many people will want their machine to not halt and not poweroff?
+>>
+>> Said in another way:
+>> - How many people will this change cause problem to?
+>> - How many people will benefit from it?
+>>
+>> I would expect the ratio to be about at least 99.9/0.1 which is why I 
+>> hate it.
+>>
+>> This change seem to be done without any consideration for users.
+>
+> So fix it, no change to systemctl is needed AFAICT, just replace the 
+> symlink with a tool that does "the right thing", probably running 
+> "poweroff" passing all arguments verbatim. Don't forget to fix the 
+> manpage as well.
+>
+>
+>     Christiaan
+
+Another possible fix would be to create an alias, maybe add it to 
+.bashrc.  Personally I have always just preferred to use the good old 
+'init 0' and 'init 6' commands.  No matter what version of whatever 
+distro you may be using they always do the same thing.
+
+-- 
+
+
+        /"A mind that is stretched by a new experience can never go back
+        to its old dimensions."/
+
+
+          *~Oliver Wendell Holmes, Jr.*
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018049.html b/zarb-ml/mageia-dev/2012-August/018049.html new file mode 100644 index 000000000..9210816af --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018049.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Potential future problem with kernel provides / synthesis + + + + + + + + + +

[Mageia-dev] Potential future problem with kernel provides / synthesis

+ Pascal Terjan + pterjan at gmail.com +
+ Sat Aug 11 02:42:32 CEST 2012 +

+
+ +
Currently the list of provides for kernel packages make lines of 55k
+characters in the synthesis
+
+URPM uses a 64k buffer to read lines and will reject longer lines
+
+Next in the list is gcstar with 42727 due to the huge number of perl
+modules provided
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018050.html b/zarb-ml/mageia-dev/2012-August/018050.html new file mode 100644 index 000000000..0b1834c82 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018050.html @@ -0,0 +1,136 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kernel-3.5.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kernel-3.5.0-1.mga3

+ Dick Gevers + dvgevers at xs4all.nl +
+ Sat Aug 11 09:33:36 CEST 2012 +

+
+ +
On Sat, 28 Jul 2012 12:03:49 +0000, Dick Gevers wrote about Re:
+[Mageia-dev] [changelog] [RPM] cauldron core/release kernel-3.5.0-1.mga3:
+
+>On Sat, 28 Jul 2012 05:11:35 +0200 (CEST), tmb wrote about [changelog]
+>[RPM] cauldron core/release kernel-3.5.0-1.mga3:
+>
+>>Name        : kernel                       Relocations: (not relocatable)
+>>Version     : 3.5.0                             Vendor: Mageia.Org
+>>Release     : 1.mga3                        Build Date: Sat Jul 28
+>
+>In combination with fglrx-8.980.3.mga3 I cannot start X, nor change to
+>another tty. But on my laptop which uses nouveau, I have no problem:
+>
+>
+>The only thing I can find in the logs which is different from before is
+>this:
+>
+>Jul 28 09:45:31 dvg kernel: [   13.289114] ACPI Warning:
+>0x0000000000000830-0x0000000000000833 SystemIO conflicts with Region \PMRG
+>1 (20120320/utaddress-251)
+>Jul 28 09:45:31 dvg kernel: [   13.289118] ACPI Warning:
+>0x0000000000000830-0x0000000000000833 SystemIO conflicts with Region
+>\_SB_.PCI0.SBRG.SMIE 2 (20120320/utaddress-251) 
+>Jul 28 09:45:31 dvg kernel: [   13.289122] lpc_ich: Resource conflict(s)
+>found affecting iTCO_wdt
+>Jul 28 09:45:31 dvg kernel: [   13.289124] ACPI Warning:
+>0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \PMRG
+>1 (20120320/utaddress-251) 
+>Jul 28 09:45:31 dvg kernel: [   13.289128] ACPI Warning:
+>0x0000000000000500-0x000000000000053f SystemIO conflicts with Region \GPS0
+>1 (20120320/utaddress-251) 
+>Jul 28 09:45:31 dvg kernel:[   13.289131] lpc_ich: Resource conflict(s)
+>found affecting gpio_ich 
+>Jul 28 09:45:31 dvg kernel: [   13.558339] ACPI Warning:
+>0x0000000000000400-0x000000000000041f SystemIO conflicts with Region \SMRG
+>1 (20120320/utaddress-251)
+>
+>while if using the older kernels I only get this:
+>
+>Jul 28 09:50:18 dvg kernel: [   14.724078] ACPI Warning:
+>0x0000000000000400-0x000000000000041f SystemIO conflicts with Region \SMRG
+>1 (20120320/utaddress-251) 
+>Jul 28 09:50:18 dvg kernel: [   38.563510] ACPI
+>Warning: 0x0000000000000295-0x0000000000000296 SystemIO conflicts with
+>Region \_SB_.PCI0.SBRG.SIOR.HWRE 1 (20120320/utaddress-251) 
+>
+>but I see no real problems anywhere with the older kernels.
+>
+>What am I missing?
+>
+>Thanks in advance for any advice!
+
+The same problem with kernel-3.5.1-1.mga3: I'm stuck at using 3.4.6-1 and
+can't get any further with this machine - and I haven't a clue why!
+
+Cheers,
+=Dick Gevers=
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018051.html b/zarb-ml/mageia-dev/2012-August/018051.html new file mode 100644 index 000000000..01dad2f12 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018051.html @@ -0,0 +1,153 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Sat Aug 11 11:00:25 CEST 2012 +

+
+ +
Hello,
+
+If you want to help kde upstream, feel free to join the bugDay;
+
+
+----------  Message transmis  ----------
+
+Sujet : [Bugsquad] BugDays for Kmail on 18/19 and 25/26 August - please join 
+the fun!
+Date : mercredi 8 août 2012, 22:21:42
+Hi everyone,
+
+We are organizing a BugDay on 2 consecutive weekends to find the
+kmail1 bugs reproducible in kmail2, so we can close the kmail1
+remaining bugs as unmaintained.
+
+You can find all the necessary information in my bog:
+http://blogs.fsfe.org/myriam/2012/08/08/triagers-and-testers-needed/
+but here is a summary:
+
+What needs to be done?
+
+* We need to get rid of open duplicate reports.
+* We will check if a bug is reproducible in Kmail 2 and reassign it there.
+* We will close the Kmail1-only reports as unmaintained.
+* We also need to clean up and remove duplicates form the Kmail2 bugs list.
+
+To make sure we can work reasonably well, this is the setup you should
+have to help with the testing:
+
+* KDE SC 4.8.4 with Kmail 4.8.4 at least, but 4.9 would be better and
+if you can run from Git it would be even more helpful.
+* Either a POP3 or an IMAP setup, to make sure we can test both extensively.
+
+I will be around most of the time (in my UTC+2 timezone at least) and
+will try to give a hand in #kde-bugs on irc.freenode.net
+
+So let’s meet on Saturday, August 18th on #kde-bugs and get this
+sorted as much as possible.
+
+Of course, you can start earlier: you will find two saved searches in
+http://bugs.kde.org called “Kmail1 open bugs” and “Kmail2 open bugs”.
+Just add these to your footer, so you can easily access the list
+whenever you feel a triaging itch.
+(if you can't see saved searches then you do not yet have enough
+rights in b.k.o, please talk to me about that so we can fix that).
+
+If this is your first triaging experience, don’t be shy, just ping me
+in #kde-bugs – type: “Mamarok: ping” – and I will try to give you the
+necessary help ASAP
+
+And finally: if you want to be kept updated about the Bugsprints we
+organize, you can subscribe to this Calendar:
+https://www.google.com/calendar/ical/8q4v2jv05dusqo03lq53mtdqqg%40group.calendar.google.com/public/basic.ics
+
+
+See you on Saturday!
+
+Regards, Myriam
+
+PS. A good read for triagers 2be:
+http://techbase.kde.org/Contribute/Bugsquad/Guide_To_BugTriaging
+
+-- 
+Proud member of the Amarok and KDE Community
+Protect your freedom and join the Fellowship of FSFE:
+http://www.fsfe.org
+Please don't send me proprietary file formats,
+use ISO standard ODF instead (ISO/IEC 26300)
+_______________________________________________
+Bugsquad mailing list
+Bugsquad at kde.org
+https://mail.kde.org/mailman/listinfo/bugsquad
+
+-----------------------------------------
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018052.html b/zarb-ml/mageia-dev/2012-August/018052.html new file mode 100644 index 000000000..c40a5d5a6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018052.html @@ -0,0 +1,154 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Olivier Blin + mageia at blino.org +
+ Sat Aug 11 12:33:47 CEST 2012 +

+
+ +
nicolas vigier <boklm at mars-attacks.org> writes:
+
+> On Mon, 29 Aug 2011, Michael Scherer wrote:
+
+[...]
+
+>> > After looking at the problem, I suspect it could be linked to texmf.
+>> > Each time iurt install it, the process stop.  
+>> 
+>> Boklm found the problem, it was urpmi segfaulting.
+>> 
+>> We remove the chroot, and thing seems to be ok now again.
+>
+> But we probably still have the problem, as segfaults seems to be
+> happenning not all the time.
+>
+> After succesfully reproducing the error using the old chroot and running
+> urpmi several times, the backtrace :
+>
+> #0  0xf7405b29 in _int_malloc () from /lib/i686/libc.so.6
+> #1  0xf7408177 in malloc () from /lib/i686/libc.so.6
+> #2  0xf6eadfa8 in __os_malloc (env=0xb442db8, size=4149199776, storep=0xffbbf5cc) at ../os/os_alloc.c:253
+> #3  0xf6eac47c in __memp_sync_int (env=0xb442db8, dbmfp=0xb893130, trickle_max=0, flags=8, wrote_totalp=0x0, interruptedp=0x0)
+>     at ../mp/mp_sync.c:294
+> #4  0xf6eacfaf in __memp_fsync (dbmfp=0xb893130) at ../mp/mp_sync.c:202
+> #5  0xf6e3cdf9 in __db_sync (dbp=0xb8963e8) at ../db/db_am.c:706
+> #6  0xf6e3aa68 in __db_refresh (dbp=0xb8963e8, txn=0x0, flags=0, deferred_closep=0xffbbf6fc, reuse=0) at ../db/db.c:819
+> #7  0xf6e3adc5 in __db_close (dbp=0xb8963e8, txn=0x0, flags=0) at ../db/db.c:695
+> #8  0xf6e52a38 in __db_close_pp (dbp=0xb8963e8, flags=0) at ../db/db_iface.c:253
+> #9  0xf72fec45 in db3close (dbi=0xb893030, flags=0) at backend/db3.c:494
+> #10 0xf73071c6 in dbiClose (db=0xb2b6950) at ../lib/rpmdb_internal.h:453
+> #11 rpmdbClose (db=0xb2b6950) at rpmdb.c:852
+> #12 0xf73379d6 in rpmtsCloseDB (ts=0xb231b20) at rpmts.c:64
+> #13 0xf7337a48 in rpmtsFree (ts=0xb231b20) at rpmts.c:567
+> #14 0xf736c7a1 in XS_URPM__DB_DESTROY (my_perl=0x8d42008, cv=0x8e2d420) at URPM.xs:2794
+
+[...]
+
+Hello,
+
+After hitting the issue yesterday with the "git" package, we had a look
+at the issue together with pterjan.
+I had to merge some patches in valgrind to support the new compressed
+debug info first, but then valgrind spotted some interesting issues.
+
+pterjan fixed some of them, fixes are now in perl-URPM 4.12.
+It should help preventing "build loops" in the BS.
+
+Attached is the valgrind log with remaining issues, maybe insightful for
+Titi.
+
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: valgrind.log.bz2
+Type: application/x-bzip2
+Size: 7174 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120811/3ce980ee/attachment.bz2>
+-------------- next part --------------
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018053.html b/zarb-ml/mageia-dev/2012-August/018053.html new file mode 100644 index 000000000..20fef97e8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018053.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] Potential future problem with kernel provides / synthesis + + + + + + + + + +

[Mageia-dev] Potential future problem with kernel provides / synthesis

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sat Aug 11 13:53:54 CEST 2012 +

+
+ +
Le 11/08/2012 02:42, Pascal Terjan a écrit :
+> Currently the list of provides for kernel packages make lines of 55k
+> characters in the synthesis
+>
+> URPM uses a 64k buffer to read lines and will reject longer lines
+>
+> Next in the list is gcstar with 42727 due to the huge number of perl
+> modules provided
+I just fixed gcstart: private perl modules should generate dependencies.
+
+
+-- 
+BOFH excuse #56:
+
+Electricians made popcorn in the power supply
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018054.html b/zarb-ml/mageia-dev/2012-August/018054.html new file mode 100644 index 000000000..1a6e975c0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018054.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Sander Lepik + sander.lepik at eesti.ee +
+ Sat Aug 11 14:17:44 CEST 2012 +

+
+ +
11.08.2012 13:33, Olivier Blin kirjutas:
+> pterjan fixed some of them, fixes are now in perl-URPM 4.12.
+> It should help preventing "build loops" in the BS.
+Thank you! \o/
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018055.html b/zarb-ml/mageia-dev/2012-August/018055.html new file mode 100644 index 000000000..b643ab2b1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018055.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] Mass rebuild? + + + + + + + + + +

[Mageia-dev] Mass rebuild?

+ Sander Lepik + sander.lepik at eesti.ee +
+ Sat Aug 11 19:25:33 CEST 2012 +

+
+ +
Alpha 1 is getting closer and closer but still no rebuild. AFAIK we should have all major
+packages in for now. So what is stopping mass rebuild? :)
+
+Even if there won't be any mass rebuild before alpha 1, can maintainers please check their
+packages from this list: http://check.mageia.org/cauldron/dependencies.html - some may need
+just a rebuild.
+
+-- 
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018056.html b/zarb-ml/mageia-dev/2012-August/018056.html new file mode 100644 index 000000000..5a7822995 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018056.html @@ -0,0 +1,127 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Bersuit Vera + bersuit.cooker at gmail.com +
+ Sat Aug 11 21:38:35 CEST 2012 +

+
+ +
Hi all.
+I'am Bersuit a novice packager. I'am working  in taglib-sharp update
+I have problems with  the location of mono lib files
+
+ %files
+ %defattr(-, root, root)
+ %doc AUTHORS NEWS README
+-%{_libexecdir}/mono/taglib-sharp
+-%{_libexecdir}/mono/gac/taglib-sharp
+-%{_libexecdir}/mono/gac/policy.2.0.taglib-sharp
++%{_prefix}/lib/mono/taglib-sharp
++%{_prefix}/lib/mono/gac/taglib-sharp
++%{_prefix}/lib/mono/gac/policy.2.0.taglib-sharp
+
+
+If use in the spec %{_libdir} o %{libexecdir} x64 does not compile
+(/usr/lib vs /usr/lib64)
+to prevent problems use %{_prefix}/lib,  rpmlint is not happy with this and
+generates an error
+What is the mageia policy ?
+
+The fedora wiki . does not help me :-)
+https://fedoraproject.org/wiki/Packaging:Mono#rpmlint_and_mono_packages
+
+
+Best regards.
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120811/bf6b8523/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018057.html b/zarb-ml/mageia-dev/2012-August/018057.html new file mode 100644 index 000000000..f5b1758cf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018057.html @@ -0,0 +1,137 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Sat Aug 11 21:43:37 CEST 2012 +

+
+ +
Le samedi 11 août 2012 21:38:35 Bersuit Vera a écrit :
+
+Hi all.
+I'am Bersuit a novice packager. I'am working  in taglib-sharp update
+I have problems with  the location of mono lib files
+
+ %files
+ %defattr(-, root, root)
+ %doc AUTHORS NEWS README
+-%{_libexecdir}/mono/taglib-sharp
+-%{_libexecdir}/mono/gac/taglib-sharp
+-%{_libexecdir}/mono/gac/policy.2.0.taglib-sharp
++%{_prefix}/lib/mono/taglib-sharp
++%{_prefix}/lib/mono/gac/taglib-sharp
++%{_prefix}/lib/mono/gac/policy.2.0.taglib-sharp
+
+
+If use in the spec %{_libdir} o %{libexecdir} x64 does not compile (/usr/lib 
+vs /usr/lib64)
+to prevent problems use %{_prefix}/lib,  rpmlint is not happy with this and 
+generates an error 
+What is the mageia policy ?
+
+The fedora wiki . does not help me :-)
+https://fedoraproject.org/wiki/Packaging:Mono#rpmlint_and_mono_packages
+
+
+Best regards.
+
+
+Hi,
+
+%{_prefix}/lib is the correct path ( i looked on kimono  spec file to confirm )
+
+what is the rpmlint error ? maybe we should learn him about mono.
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120811/dbe89d0d/attachment-0001.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018058.html b/zarb-ml/mageia-dev/2012-August/018058.html new file mode 100644 index 000000000..7c09b2bfb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018058.html @@ -0,0 +1,125 @@ + + + + [Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro + + + + + + + + + +

[Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro

+ Balcaen John + mikala at mageia.org +
+ Sat Aug 11 23:02:55 CEST 2012 +

+
+ +
Le samedi 11 août 2012 18:47:35 root at mageia.org a écrit :
+
+> Revision
+> 280684
+> Author
+> luigiwalser
+[...]
+
+> -BuildRequires: pkgconfig(QtCore) <= 5.0.0
+> +BuildRequires: qt4-devel >= 2:4.5
+>  %if %{build_sys_rootcerts}
+>  BuildRequires: rootcerts
+>  %endif
+Why switching back to qt4-devel instead of pkgconfig() ?
+
+-- 
+Balcaen John
+
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018059.html b/zarb-ml/mageia-dev/2012-August/018059.html new file mode 100644 index 000000000..646289ef0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018059.html @@ -0,0 +1,127 @@ + + + + [Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro + + + + + + + + + +

[Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Sat Aug 11 23:05:25 CEST 2012 +

+
+ +
Le samedi 11 août 2012 18:02:55 Balcaen John a écrit :
+> Le samedi 11 août 2012 18:47:35 root at mageia.org a écrit :
+> > Revision
+> > 280684
+> > Author
+> > luigiwalser
+> 
+> [...]
+> 
+> > -BuildRequires: pkgconfig(QtCore) <= 5.0.0
+> > +BuildRequires: qt4-devel >= 2:4.5
+> > 
+> >  %if %{build_sys_rootcerts}
+> >  BuildRequires: rootcerts
+> >  %endif
+> 
+> Why switching back to qt4-devel instead of pkgconfig() ?
+
+Yes please revert and use :
+
+BuildRequires: pkgconfig(QtCore) < 5.0.0
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018060.html b/zarb-ml/mageia-dev/2012-August/018060.html new file mode 100644 index 000000000..7c653fc80 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018060.html @@ -0,0 +1,116 @@ + + + + [Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro + + + + + + + + + +

[Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro

+ Balcaen John + mikala at mageia.org +
+ Sat Aug 11 23:18:02 CEST 2012 +

+
+ +
Le samedi 11 août 2012 14:11:22 vous avez écrit :
+> Because it didn't work.  It looked like you even tried to tell it to use
+> LESS THAN version 5, but it still installed qt5 stuff, but didn't install a
+> devel package, and the %cmake_qt4 macro was undefined.
+Hum it's strange because it was working under iurt cauldron.
+I'll check again but something is weird.
+
+-- 
+Balcaen John
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018061.html b/zarb-ml/mageia-dev/2012-August/018061.html new file mode 100644 index 000000000..76539e5e5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018061.html @@ -0,0 +1,130 @@ + + + + [Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro + + + + + + + + + +

[Mageia-dev] [packages-commits] [280684] SILENT: revert qt BR change for cmake macro

+ Balcaen John + mikala at mageia.org +
+ Sat Aug 11 23:20:02 CEST 2012 +

+
+ +
Le samedi 11 août 2012 18:02:55 Balcaen John a écrit :
+> Le samedi 11 août 2012 18:47:35 root at mageia.org a écrit :
+> > Revision
+> > 280684
+> > Author
+> > luigiwalser
+> 
+> [...]
+> 
+> > -BuildRequires: pkgconfig(QtCore) <= 5.0.0
+> > +BuildRequires: qt4-devel >= 2:4.5
+> > 
+> >  %if %{build_sys_rootcerts}
+> >  BuildRequires: rootcerts
+> >  %endif
+> 
+> Why switching back to qt4-devel instead of pkgconfig() ?
+Ok i found the typo
+it should be 
+pkgconfig(QtCore) < 5.0.0 and not 
+pkgconfig(QtCore) <= 5.0.0
+(which match qt5 in this case :p )
+
+-- 
+Balcaen John
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018062.html b/zarb-ml/mageia-dev/2012-August/018062.html new file mode 100644 index 000000000..44246a1c5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018062.html @@ -0,0 +1,122 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sun Aug 12 00:32:34 CEST 2012 +

+
+ +
Hello list.
+
+While trying to rebuild mod_ruby, I get this error:
+mod_ruby.c:507:5: erreur: le format n'est pas une chaîne littérale et 
+pas d'argument de format [-Werror=format-security]
+
+The line 505 is;
+vsnprintf(buf, BUFSIZ, fmt, args);
+
+Apparently, the test fails to recognize the 'fmt' variable as the format...
+
+Unfortunatly, I can't disable the use of those flags in the package, as 
+they are actually enforced by apxs usage.
+-- 
+BOFH excuse #381:
+
+Robotic tape changer mistook operator's tie for a backup tape.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018063.html b/zarb-ml/mageia-dev/2012-August/018063.html new file mode 100644 index 000000000..cc642ad0b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018063.html @@ -0,0 +1,121 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Pascal Terjan + pterjan at gmail.com +
+ Sun Aug 12 00:41:35 CEST 2012 +

+
+ +
On Sat, Aug 11, 2012 at 11:32 PM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Hello list.
+>
+> While trying to rebuild mod_ruby, I get this error:
+> mod_ruby.c:507:5: erreur: le format n'est pas une chaīne littérale et pas
+> d'argument de format [-Werror=format-security]
+>
+> The line 505 is;
+> vsnprintf(buf, BUFSIZ, fmt, args);
+>
+> Apparently, the test fails to recognize the 'fmt' variable as the format...
+
+Well, it complains that fmt is a variable, which is the point of the
+test, so it is not broken
+Only constant formats are allowed
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018064.html b/zarb-ml/mageia-dev/2012-August/018064.html new file mode 100644 index 000000000..a26165474 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018064.html @@ -0,0 +1,124 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Pascal Terjan + pterjan at gmail.com +
+ Sun Aug 12 00:45:48 CEST 2012 +

+
+ +
On Sat, Aug 11, 2012 at 11:41 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Sat, Aug 11, 2012 at 11:32 PM, Guillaume Rousse
+> <guillomovitch at gmail.com> wrote:
+>> Hello list.
+>>
+>> While trying to rebuild mod_ruby, I get this error:
+>> mod_ruby.c:507:5: erreur: le format n'est pas une chaīne littérale et pas
+>> d'argument de format [-Werror=format-security]
+>>
+>> The line 505 is;
+>> vsnprintf(buf, BUFSIZ, fmt, args);
+>>
+>> Apparently, the test fails to recognize the 'fmt' variable as the format...
+>
+> Well, it complains that fmt is a variable, which is the point of the
+> test, so it is not broken
+> Only constant formats are allowed
+
+Ah no sorry, it should accept a variable when there are arguments.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018065.html b/zarb-ml/mageia-dev/2012-August/018065.html new file mode 100644 index 000000000..19020a9cf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018065.html @@ -0,0 +1,157 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Pascal Terjan + pterjan at gmail.com +
+ Sun Aug 12 00:55:24 CEST 2012 +

+
+ +
On Sat, Aug 11, 2012 at 11:45 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Sat, Aug 11, 2012 at 11:41 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+>> On Sat, Aug 11, 2012 at 11:32 PM, Guillaume Rousse
+>> <guillomovitch at gmail.com> wrote:
+>>> Hello list.
+>>>
+>>> While trying to rebuild mod_ruby, I get this error:
+>>> mod_ruby.c:507:5: erreur: le format n'est pas une chaīne littérale et pas
+>>> d'argument de format [-Werror=format-security]
+>>>
+>>> The line 505 is;
+>>> vsnprintf(buf, BUFSIZ, fmt, args);
+>>>
+>>> Apparently, the test fails to recognize the 'fmt' variable as the format...
+>>
+>> Well, it complains that fmt is a variable, which is the point of the
+>> test, so it is not broken
+>> Only constant formats are allowed
+>
+> Ah no sorry, it should accept a variable when there are arguments.
+
+The full log, which explains the problem:
+
+mod_ruby.c: In function 'ruby_log_error':
+mod_ruby.c:507:5: warning: passing argument 5 of 'ap_log_error_' makes
+integer from pointer without a cast [enabled by default]
+In file included from mod_ruby.h:104:0,
+                 from mod_ruby.c:33:
+/usr/include/httpd/http_log.h:372:18: note: expected 'apr_status_t'
+but argument is of type 'const struct server_rec *'
+mod_ruby.c:507:5: warning: passing argument 6 of 'ap_log_error_' from
+incompatible pointer type [enabled by default]
+In file included from mod_ruby.h:104:0,
+                 from mod_ruby.c:33:
+/usr/include/httpd/http_log.h:372:18: note: expected 'const struct
+server_rec *' but argument is of type 'char *'
+mod_ruby.c:507:5: error: format not a string literal and no format
+arguments [-Werror=format-security]
+
+The error is not on the line 505 but 507:
+
+    ap_log_error(file, line, level, 0, s, "mod_ruby: %s", buf);
+
+Which is defined as:
+
+AP_DECLARE(void) ap_log_error_(const char *file, int line, int module_index,
+                               int level, apr_status_t status,
+                               const server_rec *s, const char *fmt, ...)
+                              __attribute__((format(printf,7,8)));
+
+so the call is missing module_index, parameters are shiffted and buf
+is considered to be the format.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018066.html b/zarb-ml/mageia-dev/2012-August/018066.html new file mode 100644 index 000000000..9a02de4a2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018066.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Juan Luis Baptiste + juancho at mageia.org +
+ Sun Aug 12 02:51:26 CEST 2012 +

+
+ +
On Sat, Aug 11, 2012 at 2:43 PM, Nicolas Lécureuil
+<nicolas.lecureuil at free.fr> wrote:
+> Hi,
+>
+> %{_prefix}/lib is the correct path ( i looked on kimono spec file to confirm
+> )
+>
+
+Yeah, I looked at several mono packages and all of them do it like
+that, regarless that rpmlint doesn't like it.
+
+-- 
+Juancho
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018067.html b/zarb-ml/mageia-dev/2012-August/018067.html new file mode 100644 index 000000000..b82ccc890 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018067.html @@ -0,0 +1,120 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Bersuit Vera + bersuit.cooker at gmail.com +
+ Sun Aug 12 10:28:59 CEST 2012 +

+
+ +
Hi Nico:
+rpmlint says warning:
+hardcoded-library-path in% {_prefix} / lib
+
+A library path is hardcoded to one of the Following paths: / lib, / usr /
+lib. It
+Should Be Replaced by something like /% {_lib} or% {_libdir}.
+
+
+Hi,
+>
+> %{_prefix}/lib is the correct path ( i looked on kimono spec file to
+> confirm )
+>
+>
+>
+> what is the rpmlint error ? maybe we should learn him about mono.
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120812/04b31432/attachment-0001.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018068.html b/zarb-ml/mageia-dev/2012-August/018068.html new file mode 100644 index 000000000..e2fbea107 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018068.html @@ -0,0 +1,119 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Bersuit Vera + bersuit.cooker at gmail.com +
+ Sun Aug 12 10:29:45 CEST 2012 +

+
+ +
Thanks,  Juancho, Nicolas  %{_prefix}/lib it's Ok
+
+2012/8/12 Juan Luis Baptiste <juancho at mageia.org>
+
+> On Sat, Aug 11, 2012 at 2:43 PM, Nicolas Lécureuil
+> <nicolas.lecureuil at free.fr> wrote:
+> > Hi,
+> >
+> > %{_prefix}/lib is the correct path ( i looked on kimono spec file to
+> confirm
+> > )
+> >
+>
+> Yeah, I looked at several mono packages and all of them do it like
+> that, regarless that rpmlint doesn't like it.
+>
+> --
+> Juancho
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120812/cd7130d7/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018069.html b/zarb-ml/mageia-dev/2012-August/018069.html new file mode 100644 index 000000000..408feef64 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018069.html @@ -0,0 +1,128 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Angelo Naselli + anaselli at linux.it +
+ Sun Aug 12 11:45:22 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 12/08/2012 10:28, Bersuit Vera ha scritto:
+> 
+> Hi Nico: rpmlint says warning: hardcoded-library-path in% {_prefix}
+> / lib
+> 
+> A library path is hardcoded to one of the Following paths: / lib, /
+> usr / lib. It
+
+Hmm are you sure? I'm not. They are noarch for the most, and
+for any lib64 you add, (using %libdir) you also need to patch
+Makfiles & co...
+
+Maybe we can consider a different solution for the future,
+but i don't think patching all to get rid of rpmlint is
+the best one...
+
+My 2? cents
+	Angelo
+
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAney4ACgkQqEs9DA4DquBLiwCgqP8/BxMmimSGoWJjQOrUutlM
+AXYAn1QEylhnLPmqmb8KaH2IZcDzsMV5
+=yAQI
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018070.html b/zarb-ml/mageia-dev/2012-August/018070.html new file mode 100644 index 000000000..ea135922b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018070.html @@ -0,0 +1,130 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Angelo Naselli + anaselli at linux.it +
+ Sun Aug 12 11:46:57 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 12/08/2012 11:45, Angelo Naselli ha scritto:
+> Il 12/08/2012 10:28, Bersuit Vera ha scritto:
+> 
+>> Hi Nico: rpmlint says warning: hardcoded-library-path in%
+>> {_prefix} / lib
+> 
+>> A library path is hardcoded to one of the Following paths: / lib,
+>> / usr / lib. It
+Sorry I missed this line in replying:
+>> Should Be Replaced by something like /% {_lib} or% {_libdir}.
+
+> 
+> Hmm are you sure? I'm not. They are noarch for the most, and for
+> any lib64 you add, (using %libdir) you also need to patch Makfiles
+> & co...
+> 
+> Maybe we can consider a different solution for the future, but i
+> don't think patching all to get rid of rpmlint is the best one...
+> 
+> My 2? cents Angelo
+> 
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAne5EACgkQqEs9DA4DquAnYACggjNd03kw0GBJ/Prqpv+AVbzX
+9d8AoKkP23pScTbYiC1I/nsM/+Jwlyet
+=p+tt
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018071.html b/zarb-ml/mageia-dev/2012-August/018071.html new file mode 100644 index 000000000..4f98d35a5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018071.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sun Aug 12 12:10:25 CEST 2012 +

+
+ +
Le 12/08/2012 00:55, Pascal Terjan a écrit :
+> so the call is missing module_index, parameters are shiffted and buf
+> is considered to be the format.
+Thanks, I 'fixed' this call, just to run another compilation error:
+apachelib.c: In function ‘rb_init_apache’:
+apachelib.c:374:50: erreur: ‘OPT_INCNOEXEC’ undeclared (first use in 
+this function)
+
+As the last news on http://modruby.net/en/index.rbx is from 11/2008, is 
+this project still maintained upstream ? Otherwise, we may as well drop it.
+
+-- 
+BOFH excuse #433:
+
+error: one bad user found in front of screen
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018072.html b/zarb-ml/mageia-dev/2012-August/018072.html new file mode 100644 index 000000000..e9ff97d49 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018072.html @@ -0,0 +1,121 @@ + + + + [Mageia-dev] Mass rebuild? + + + + + + + + + +

[Mageia-dev] Mass rebuild?

+ Angelo Naselli + anaselli at linux.it +
+ Sun Aug 12 12:13:36 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 11/08/2012 19:25, Sander Lepik ha scritto:
+> Alpha 1 is getting closer and closer but still no rebuild. AFAIK we
+> should have all major packages in for now. So what is stopping mass
+> rebuild? :)
+> 
+> Even if there won't be any mass rebuild before alpha 1, can
+> maintainers please check their packages from this list:
+> http://check.mageia.org/cauldron/dependencies.html - some may need 
+> just a rebuild.
+> 
+I will take care of my packages as soon as I'm back home from
+holidays, if no mass rebuilding is done.
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAngdAACgkQqEs9DA4DquCTnQCfV3T5zQYhz+CRRLUOxiezaSAo
+8XQAn1TLCPId5Ih/l6qaKX1zAVzPfhAG
+=7gS4
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018073.html b/zarb-ml/mageia-dev/2012-August/018073.html new file mode 100644 index 000000000..58b617162 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018073.html @@ -0,0 +1,122 @@ + + + + [Mageia-dev] Mass rebuild? + + + + + + + + + +

[Mageia-dev] Mass rebuild?

+ Manuel Hiebel + manuel.mageia at hiebel.eu +
+ Sun Aug 12 12:50:30 CEST 2012 +

+
+ +
Le 12/08/2012 12:13, Angelo Naselli a écrit :
+> -----BEGIN PGP SIGNED MESSAGE-----
+> Hash: SHA1
+>
+> Il 11/08/2012 19:25, Sander Lepik ha scritto:
+>> Alpha 1 is getting closer and closer but still no rebuild. AFAIK we
+>> should have all major packages in for now. So what is stopping mass
+>> rebuild? :)
+>>
+>> Even if there won't be any mass rebuild before alpha 1, can
+>> maintainers please check their packages from this list:
+>> http://check.mageia.org/cauldron/dependencies.html - some may need
+>> just a rebuild.
+>>
+> I will take care of my packages as soon as I'm back home from
+> holidays, if no mass rebuilding is done.
+>
+> Angelo
+> -----BEGIN PGP SIGNATURE-----
+> Version: GnuPG v1.4.12 (GNU/Linux)
+> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+>
+> iEYEARECAAYFAlAngdAACgkQqEs9DA4DquCTnQCfV3T5zQYhz+CRRLUOxiezaSAo
+> 8XQAn1TLCPId5Ih/l6qaKX1zAVzPfhAG
+> =7gS4
+> -----END PGP SIGNATURE-----
+see https://wiki.mageia.org/en/Feature:Mageia3MassRebuild
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018074.html b/zarb-ml/mageia-dev/2012-August/018074.html new file mode 100644 index 000000000..c6b160059 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018074.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Pascal Terjan + pterjan at gmail.com +
+ Sun Aug 12 13:45:49 CEST 2012 +

+
+ +
On Sun, Aug 12, 2012 at 11:10 AM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 12/08/2012 00:55, Pascal Terjan a écrit :
+>
+>> so the call is missing module_index, parameters are shiffted and buf
+>> is considered to be the format.
+>
+> Thanks, I 'fixed' this call, just to run another compilation error:
+> apachelib.c: In function ‘rb_init_apache’:
+> apachelib.c:374:50: erreur: ‘OPT_INCNOEXEC’ undeclared (first use in this
+> function)
+>
+> As the last news on http://modruby.net/en/index.rbx is from 11/2008, is this
+> project still maintained upstream ? Otherwise, we may as well drop it.
+
+It seems quite dead, I guess most web ruby is rails and people would
+prefer passenger
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018075.html b/zarb-ml/mageia-dev/2012-August/018075.html new file mode 100644 index 000000000..bbaa415f1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018075.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] broken format-error test ? + + + + + + + + + +

[Mageia-dev] broken format-error test ?

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sun Aug 12 13:58:07 CEST 2012 +

+
+ +
Le 12/08/2012 13:45, Pascal Terjan a écrit :
+>> As the last news on http://modruby.net/en/index.rbx is from 11/2008, is this
+>> project still maintained upstream ? Otherwise, we may as well drop it.
+>
+> It seems quite dead, I guess most web ruby is rails and people would
+> prefer passenger
+OK, so we have two packages candidate for removal:
+- apache-mod_ruby
+- apache-mod_python (https://bugs.mageia.org/show_bug.cgi?id=7024)
+
+This will save a few hours to the next guy foolish enough to make the 
+future switch from apache 2.4 to 2.6...
+-- 
+BOFH excuse #452:
+
+Somebody ran the operating system through a spelling checker.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018076.html b/zarb-ml/mageia-dev/2012-August/018076.html new file mode 100644 index 000000000..3e5711d74 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018076.html @@ -0,0 +1,128 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sun Aug 12 14:06:28 CEST 2012 +

+
+ +
'Twas brillig, and Bersuit Vera at 12/08/12 09:28 did gyre and gimble:
+> 
+> Hi Nico:
+> rpmlint says warning:
+> hardcoded-library-path in% {_prefix} / lib
+> 
+> A library path is hardcoded to one of the Following paths: / lib, / usr
+> / lib. It
+> Should Be Replaced by something like /% {_lib} or% {_libdir}.
+
+Normally yes, but in this case it doesn't really apply.
+
+We have previously discussed the "correct" location for these kind of
+things, but ultimately using %{_prefix}/lib seemed to be the correct
+solution I think.
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018077.html b/zarb-ml/mageia-dev/2012-August/018077.html new file mode 100644 index 000000000..e6dad02c5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018077.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] File location in mono packages + + + + + + + + + +

[Mageia-dev] File location in mono packages

+ Pascal Terjan + pterjan at gmail.com +
+ Sun Aug 12 14:27:38 CEST 2012 +

+
+ +
On Sun, Aug 12, 2012 at 1:06 PM, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+> 'Twas brillig, and Bersuit Vera at 12/08/12 09:28 did gyre and gimble:
+>>
+>> Hi Nico:
+>> rpmlint says warning:
+>> hardcoded-library-path in% {_prefix} / lib
+>>
+>> A library path is hardcoded to one of the Following paths: / lib, / usr
+>> / lib. It
+>> Should Be Replaced by something like /% {_lib} or% {_libdir}.
+>
+> Normally yes, but in this case it doesn't really apply.
+>
+> We have previously discussed the "correct" location for these kind of
+> things, but ultimately using %{_prefix}/lib seemed to be the correct
+> solution I think.
+
+I would have expected /usr/share if they are noarch but well
+perl/ruby/... do the same...
+rpmlint doesn't complain because we have macros for them
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018078.html b/zarb-ml/mageia-dev/2012-August/018078.html new file mode 100644 index 000000000..6e20daa54 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018078.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] Suggested change to %configure + + + + + + + + + +

[Mageia-dev] Suggested change to %configure

+ Olivier Blin + mageia at blino.org +
+ Sun Aug 12 14:34:34 CEST 2012 +

+
+ +
Pascal Terjan <pterjan at gmail.com> writes:
+
+> On Thu, Aug 9, 2012 at 5:00 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+>> Would anyone oppose adding '|| (echo config.log; exit 1)' inside the macro ?
+>>
+>> That would help people debugging missing buildrequires on the build system
+>
+> Thinking more about it, this makes sense only on the build system, and
+> I'd prefer not copy the macro to iurt config...
+
+We could maybe do that only if the shell is not interactive.
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018079.html b/zarb-ml/mageia-dev/2012-August/018079.html new file mode 100644 index 000000000..ff8758537 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018079.html @@ -0,0 +1,125 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Philippe Reynes + tremyfr at yahoo.fr +
+ Sun Aug 12 16:21:12 CEST 2012 +

+
+ +
Hi all,
+
+I've found that I have three glibc installed on my box.
+
+[trem at localhost ~]$ rpm -q glibc
+glibc-2.14.1-8.mga2
+glibc-2.16-7.mga3
+glibc-2.16-8.mga3
+
+
+I've removed glibc-2.16-7.mga3, and the issue seems to be solved.
+
+
+Regards,
+trem
+
+
+
+________________________________
+ De : Olivier Thauvin <nanardon at nanardon.zarb.org>
+À : Mageia development mailing-list <mageia-dev at mageia.org> 
+Envoyé le : Mercredi 8 août 2012 7h41
+Objet : Re: [Mageia-dev] strange urpmi --auto-update with glibc
+ 
+* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> On 7 August 2012 18:33, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> > Hello,
+> >
+> > Am I the only one to have such behavior:
+> >
+> > [root at apus olivier]# LC_ALL=C urpmi --auto-update
+> > The following package has to be removed for others to be upgraded:
+> > glibc-2.16-8.mga3.x86_64
+> >  (in order to install glibc-2.16-8.mga3.x86_64) (y/N)
+> >
+> > If I accept the transaction fails saying glibc-2.16-8.mga3.x86_64 is
+> > already installed, obviously.
+> 
+> I would need the bug-glibc.tar.xz file resulting from running the
+> following commands:
+> urpmi --auto-update --bug bug-glibc
+> tar cfa bug-glibc{.tar.xz,}
+> 
+> Send this file to me (privately, not to the ml (too big)).
+
+Or I let you downloading it from here:
+
+http://olivier.thauvin.page.latmos.ipsl.fr/bug-glibc.tar.xz
+
+Regards.
+
+> Thx
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120812/73082834/attachment-0001.html>
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018080.html b/zarb-ml/mageia-dev/2012-August/018080.html new file mode 100644 index 000000000..657304fdc --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018080.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Angelo Naselli + anaselli at linux.it +
+ Sun Aug 12 18:06:49 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 11/08/2012 11:00, Nicolas Lécureuil ha scritto:
+[...]
+> What needs to be done?
+> 
+> * We need to get rid of open duplicate reports. * We will check if 
+> a bug is reproducible in Kmail 2 and reassign it there. * We will 
+> close the Kmail1-only reports as unmaintained. * We also need to 
+> clean up and remove duplicates form the Kmail2 bugs list.
+
+I think we could resume all in one:
+* We Just need a kmail 2 working
+
+Sorry i couldn't resist :p
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAn1JcACgkQqEs9DA4DquCmBACeMbz779omYdqyKIWtcX0o8G3R
+DwUAn3T6VcAS/qERtGUrsEzzAJIxEF0/
+=ITO7
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018081.html b/zarb-ml/mageia-dev/2012-August/018081.html new file mode 100644 index 000000000..32eb5d464 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018081.html @@ -0,0 +1,105 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ David Walser + luigiwalser at yahoo.com +
+ Sun Aug 12 19:28:40 CEST 2012 +

+
+ +
There's an issue with the default openssh configuration now that we've switched to UsePAM yes as the default.
+
+Through the PAM configuration for SSH shipped with the openssh-server package, root login is broken.  Here's why.  /etc/pam.d/sshd has:
+auth required pam_listfile.so item=user sense=deny file=/etc/ssh/denyusers
+
+The file /etc/ssh/denyusers has "root" in it by default.
+
+Whether allowing root login through SSH is "bad" is irrelevant here.  This is not an appropriate way to disable it by default.  There is already a configuration parameter in the regular configuration file, /etc/ssh/sshd_config, for whether or not to allow root login, and this is where it should be set.  It is set by msec to "without-password" which means only with SSH keys in the default security level, and set to "no" in the secure level, so basically we already have this disabled by default, and in a way that people know about and know how to change if they want.
+
+Redundantly disabling it through some unintuitive PAM thing is not a good idea.  We actually had the same exact problem with KDM late in the Mageia 2 development cycle.  KDM has its normal way of disabling root logins in its standard kdmrc config file, but our package had additionally disabled it through PAM, which was confusing people.  This was reverted before the Mageia 2 release, so now it's just disabled in kdmrc, as it should be.
+
+We should remove "root" from /etc/ssh/denyusers in our default configuration.  I asked Colin and he said ask the list about this as he's not the maintainer.  Whoever is, consider yourself asked :o)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018082.html b/zarb-ml/mageia-dev/2012-August/018082.html new file mode 100644 index 000000000..97745fe51 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018082.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Johnny A. Solbu + cooker at solbu.net +
+ Sun Aug 12 20:02:45 CEST 2012 +

+
+ +
On Sunday 12 August 2012 19:28, David Walser wrote:
+> Through the PAM configuration for SSH shipped with the openssh-server package, root login is broken.  Here's why.  /etc/pam.d/sshd has:
+> auth required pam_listfile.so item=user sense=deny file=/etc/ssh/denyusers
+> 
+> The file /etc/ssh/denyusers has "root" in it by default.
+
+I read somewhere some time ago that PermitRootLogin in sshd_config is ignored if PAM is used.
+That may be the reason for this.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120812/51a43a7e/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018083.html b/zarb-ml/mageia-dev/2012-August/018083.html new file mode 100644 index 000000000..fb1e97eb6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018083.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Maurice Batey + maurice at bcs.org.uk +
+ Sun Aug 12 20:05:07 CEST 2012 +

+
+ +
On Sun, 12 Aug 2012 18:06:49 +0200, Angelo Naselli wrote:
+
+> * We Just need a kmail 2 working
+
+  Yes, indeed - especially Find Messages...
+
+-- 
+/\/\aurice 
+	
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018084.html b/zarb-ml/mageia-dev/2012-August/018084.html new file mode 100644 index 000000000..d12969ff2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018084.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Balcaen John + mikala at mageia.org +
+ Sun Aug 12 20:12:27 CEST 2012 +

+
+ +
Le dimanche 12 août 2012 19:05:07 Maurice Batey a écrit :
+> On Sun, 12 Aug 2012 18:06:49 +0200, Angelo Naselli wrote:
+> > * We Just need a kmail 2 working
+> 
+>   Yes, indeed - especially Find Messages...
+Well it's working better with kdepim 4.9.x  (not perfect thought)
+
+-- 
+Balcaen John
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018085.html b/zarb-ml/mageia-dev/2012-August/018085.html new file mode 100644 index 000000000..f3f7c581d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018085.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Dimitrios Glentadakis + dglent at gmail.com +
+ Sun Aug 12 20:24:16 CEST 2012 +

+
+ +
2012/8/12 Balcaen John <mikala at mageia.org>
+
+> Le dimanche 12 août 2012 19:05:07 Maurice Batey a écrit :
+> > On Sun, 12 Aug 2012 18:06:49 +0200, Angelo Naselli wrote:
+> > > * We Just need a kmail 2 working
+> >
+> >   Yes, indeed - especially Find Messages...
+> Well it's working better with kdepim 4.9.x  (not perfect thought)
+>
+> --
+> Balcaen John
+>
+>
+
+Thanks for the kde 4.8.5 i updated from testig for mageia 2.
+This version has solved an issue that i had with the asking of the imap
+password at every startup.
+It rests the bug with the autocompletion of the addreses
+https://bugs.kde.org/show_bug.cgi?id=259949
+It is a great application with very very much features. With konqueror,
+they are my main applications.
+
+And congratulations to our KDE team !
+
+-- 
+Dimitrios Glentadakis
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120812/f5df3be3/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018086.html b/zarb-ml/mageia-dev/2012-August/018086.html new file mode 100644 index 000000000..255c83ae4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018086.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Angelo Naselli + anaselli at linux.it +
+ Sun Aug 12 21:51:05 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 12/08/2012 20:12, Balcaen John ha scritto:
+> Well it's working better with kdepim 4.9.x  (not perfect thought)
+kmail 1 was not perfect, but worked well for the most (or at least
+for what i used), kmail 2 is a disaster :D.
+You know i tried to stay, but loosing mails, not working filters,
+multiple imap and pop accounts mess, always on line with errors if
+use in a notebook off-line... I could not use it at work... so i had
+to test a migration to thunderbird, and i did it at home first :)
+
+Anyway I'm ready to see if a way-back is possible... let's see ;)
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAoCSYACgkQqEs9DA4DquBpcQCfSBdLUGwTzmaY9tsPuUuKA4RZ
+CGIAniRCy5a9+5gUdVcMJZWlzc021uU8
+=Uw9X
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018087.html b/zarb-ml/mageia-dev/2012-August/018087.html new file mode 100644 index 000000000..00b0f428a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018087.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ David Walser + luigiwalser at yahoo.com +
+ Sun Aug 12 21:57:06 CEST 2012 +

+
+ +
Johnny A. Solbu wrote:
+> On Sunday 12 August 2012 19:28, David Walser wrote:
+>> Through the PAM configuration for SSH shipped with the openssh-server package, root login is broken.  Here's why.  /etc/pam.d/sshd has:
+>> auth required pam_listfile.so item=user sense=deny file=/etc/ssh/denyusers
+>> 
+>> The file /etc/ssh/denyusers has "root" in it by default.
+> 
+> I read somewhere some time ago that PermitRootLogin in sshd_config is ignored if PAM is used.
+> That may be the reason for this.
+
+Nope, I just tested it and that is not true.
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018088.html b/zarb-ml/mageia-dev/2012-August/018088.html new file mode 100644 index 000000000..043f416ba --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018088.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Johnny A. Solbu + cooker at solbu.net +
+ Sun Aug 12 22:13:16 CEST 2012 +

+
+ +
On Sunday 12 August 2012 21:57, David Walser wrote:
+> > I read somewhere some time ago that PermitRootLogin in sshd_config is ignored if PAM is used.
+> > That may be the reason for this.
+> 
+> Nope, I just tested it and that is not true.
+
+Then I agree, this should be changes ASAP!
+/Many/ boxes will be unavailable for administrator access because of this. If this is an upstream configuration, the change should -also- be pushed upstream, not instead of.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120812/d1825208/attachment-0001.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018089.html b/zarb-ml/mageia-dev/2012-August/018089.html new file mode 100644 index 000000000..b7ae6b55a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018089.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Balcaen John + mikala at mageia.org +
+ Sun Aug 12 22:32:37 CEST 2012 +

+
+ +
Le dimanche 12 août 2012 20:24:16 Dimitrios Glentadakis a écrit :
+
+> It rests the bug with the autocompletion of the addreses 
+https://bugs.kde.org/show_bug.cgi?id=259949
+> It is a great application with very very much features. With konqueror, they 
+are my main applications.
+> 
+
+Yep i'm trying to understand why it's working for me (or at least last time i 
+check) with KDE 4.9.x while it is not under 4.8.x :/
+
+-- 
+Balcaen John
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018090.html b/zarb-ml/mageia-dev/2012-August/018090.html new file mode 100644 index 000000000..21ab7064c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018090.html @@ -0,0 +1,116 @@ + + + + [Mageia-dev] svn copy - forgotten mandriva packages. + + + + + + + + + +

[Mageia-dev] svn copy - forgotten mandriva packages.

+ Johnny A. Solbu + cooker at solbu.net +
+ Sun Aug 12 22:44:48 CEST 2012 +

+
+ +
I am unsure of one aspect of the svn copy procedure.
+
+If a package is imported and pushed to Cauldron the mgarepo wiki page says to svn copy from cauldron to 1/updates and then push to mga1/updates.
+Should I also svn copy to 2/updates when pushing to mga2?
+
+The wiki page is clearly written before mga2 came out, so it is now unclear as to the actuall procedure. At least for those of us who still lack the mind reading abillity. ;-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120812/6e6cbf9d/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018091.html b/zarb-ml/mageia-dev/2012-August/018091.html new file mode 100644 index 000000000..e83514aad --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018091.html @@ -0,0 +1,124 @@ + + + + [Mageia-dev] svn copy - forgotten mandriva packages. + + + + + + + + + +

[Mageia-dev] svn copy - forgotten mandriva packages.

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Aug 13 01:52:28 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 12/08/12 21:44 did gyre and gimble:
+> Should I also svn copy to 2/updates when pushing to mga2?
+
+Yeah the same rules for mga1 with regards to svn copying. I think at the
+time the "just push it to updates without going through the proper
+updates procedure" was a bit of an exception for mga1 and we all agreed
+that the same exception probably shouldn't apply to mga2 (I guess the
+argument being that it shouldn't be needed by then). It doesn't bother
+me personally but this might want to be discussed quickly all the same.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018092.html b/zarb-ml/mageia-dev/2012-August/018092.html new file mode 100644 index 000000000..0823afe16 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018092.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release v4l-utils-0.8.8-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release v4l-utils-0.8.8-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 13 07:54:14 CEST 2012 +

+
+ +
On 13 August 2012 03:32, luigiwalser <buildsystem-daemon at mageia.org> wrote:
+> luigiwalser <luigiwalser> 0.8.8-1.mga3:
+> + Revision: 281023
+> - spec fixes from mdv
+
+This is wrong. Your real fix was adding a patch, which you did as SILENT.
+Please remove the SILENT keyword
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018093.html b/zarb-ml/mageia-dev/2012-August/018093.html new file mode 100644 index 000000000..c0648ce46 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018093.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Potential future problem with kernel provides / synthesis + + + + + + + + + +

[Mageia-dev] Potential future problem with kernel provides / synthesis

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 13 08:21:26 CEST 2012 +

+
+ +
On 11 August 2012 13:53, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>> Currently the list of provides for kernel packages make lines of 55k
+>> characters in the synthesis
+>>
+>> URPM uses a 64k buffer to read lines and will reject longer lines
+>>
+>> Next in the list is gcstar with 42727 due to the huge number of perl
+>> modules provided
+>
+> I just fixed gcstart: private perl modules should generate dependencies.
+
+You meant "should not", didn't you?
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018094.html b/zarb-ml/mageia-dev/2012-August/018094.html new file mode 100644 index 000000000..c1650d30a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018094.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Potential future problem with kernel provides / synthesis + + + + + + + + + +

[Mageia-dev] Potential future problem with kernel provides / synthesis

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 13 08:24:33 CEST 2012 +

+
+ +
On 11 August 2012 02:42, Pascal Terjan <pterjan at gmail.com> wrote:
+> Currently the list of provides for kernel packages make lines of 55k
+> characters in the synthesis
+>
+> URPM uses a 64k buffer to read lines and will reject longer lines
+
+That can be fixed.
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018095.html b/zarb-ml/mageia-dev/2012-August/018095.html new file mode 100644 index 000000000..c2e0a8b36 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018095.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 13 09:34:46 CEST 2012 +

+
+ +
Le 12/08/2012 21:57, David Walser a écrit :
+> Johnny A. Solbu wrote:
+>> On Sunday 12 August 2012 19:28, David Walser wrote:
+>>> Through the PAM configuration for SSH shipped with the openssh-server package, root login is broken.  Here's why.  /etc/pam.d/sshd has:
+>>> auth required pam_listfile.so item=user sense=deny file=/etc/ssh/denyusers
+>>>
+>>> The file /etc/ssh/denyusers has "root" in it by default.
+>>
+>> I read somewhere some time ago that PermitRootLogin in sshd_config is ignored if PAM is used.
+>> That may be the reason for this.
+>
+> Nope, I just tested it and that is not true.
+There is an explicit comment in the configuration file:
+# Depending on your PAM configuration,
+# PAM authentication via ChallengeResponseAuthentication may bypass
+# the setting of "PermitRootLogin without-password".
+
+My understanding is just than some specific PAM configuration would 
+eventually allow root user to authenticate through a password, instead 
+of a key.
+
+Regarding your original problem, feel free to commit the relevant 
+modifications.
+-- 
+BOFH excuse #405:
+
+Sysadmins unavailable because they are in a meeting talking about why 
+they are unavailable so much.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018096.html b/zarb-ml/mageia-dev/2012-August/018096.html new file mode 100644 index 000000000..c905fdc45 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018096.html @@ -0,0 +1,135 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Anne Wilson + annew at kde.org +
+ Mon Aug 13 10:39:07 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 13/08/12 08:34, Guillaume Rousse wrote:
+> Le 12/08/2012 21:57, David Walser a écrit :
+>> Johnny A. Solbu wrote:
+>>> On Sunday 12 August 2012 19:28, David Walser wrote:
+>>>> Through the PAM configuration for SSH shipped with the 
+>>>> openssh-server package, root login is broken.  Here's why. 
+>>>> /etc/pam.d/sshd has: auth required pam_listfile.so item=user
+>>>> sense=deny file=/etc/ssh/denyusers
+>>>> 
+>>>> The file /etc/ssh/denyusers has "root" in it by default.
+>>> 
+>>> I read somewhere some time ago that PermitRootLogin in
+>>> sshd_config is ignored if PAM is used. That may be the reason
+>>> for this.
+>> 
+>> Nope, I just tested it and that is not true.
+> There is an explicit comment in the configuration file: # Depending
+> on your PAM configuration, # PAM authentication via
+> ChallengeResponseAuthentication may bypass # the setting of
+> "PermitRootLogin without-password".
+> 
+> My understanding is just than some specific PAM configuration
+> would eventually allow root user to authenticate through a
+> password, instead of a key.
+> 
+> Regarding your original problem, feel free to commit the relevant 
+> modifications.
+
+Why would anyone need root login over ssh?  I don't allow it on my
+server and it has never caused me any problems.  Su to root works
+perfectly well and avoids the security risk, so I don't understand
+this thread.
+
+Anne
+- -- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAovSkACgkQj93fyh4cnBc8AQCbBY28p9fxW2LtWV9G89b1VlnT
+spYAn3hJGydYD5jdpNtSYTnjDznI4hED
+=c6wq
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018097.html b/zarb-ml/mageia-dev/2012-August/018097.html new file mode 100644 index 000000000..e95c22ff9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018097.html @@ -0,0 +1,127 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Aug 13 10:58:06 CEST 2012 +

+
+ +
On Mon, Aug 13, 2012 at 9:39 AM, Anne Wilson <annew at kde.org> wrote:
+> -----BEGIN PGP SIGNED MESSAGE-----
+> Hash: SHA1
+>
+> On 13/08/12 08:34, Guillaume Rousse wrote:
+>> Le 12/08/2012 21:57, David Walser a écrit :
+>>> Johnny A. Solbu wrote:
+>>>> On Sunday 12 August 2012 19:28, David Walser wrote:
+>>>>> Through the PAM configuration for SSH shipped with the
+>>>>> openssh-server package, root login is broken.  Here's why.
+>>>>> /etc/pam.d/sshd has: auth required pam_listfile.so item=user
+>>>>> sense=deny file=/etc/ssh/denyusers
+>>>>>
+>>>>> The file /etc/ssh/denyusers has "root" in it by default.
+>>>>
+>>>> I read somewhere some time ago that PermitRootLogin in
+>>>> sshd_config is ignored if PAM is used. That may be the reason
+>>>> for this.
+>>>
+>>> Nope, I just tested it and that is not true.
+>> There is an explicit comment in the configuration file: # Depending
+>> on your PAM configuration, # PAM authentication via
+>> ChallengeResponseAuthentication may bypass # the setting of
+>> "PermitRootLogin without-password".
+>>
+>> My understanding is just than some specific PAM configuration
+>> would eventually allow root user to authenticate through a
+>> password, instead of a key.
+>>
+>> Regarding your original problem, feel free to commit the relevant
+>> modifications.
+>
+> Why would anyone need root login over ssh?  I don't allow it on my
+> server and it has never caused me any problems.  Su to root works
+> perfectly well and avoids the security risk, so I don't understand
+> this thread.
+
+Allowing login as root over ssh with a key can save things when for
+some reason non local auth is down, like to fix the connection to the
+ldap server (you can also create a local emergency account for that
+usage).
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018098.html b/zarb-ml/mageia-dev/2012-August/018098.html new file mode 100644 index 000000000..3792d5989 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018098.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Dimitrios Glentadakis + dglent at gmail.com +
+ Mon Aug 13 11:42:38 CEST 2012 +

+
+ +
Στις 12/08/2012 17:32:37 Balcaen John έγραψε:
+>Le dimanche 12 août 2012 20:24:16 Dimitrios Glentadakis a écrit :
+>
+>> It rests the bug with the autocompletion of the addreses 
+>https://bugs.kde.org/show_bug.cgi?id=259949
+>> It is a great application with very very much features. With konqueror, they 
+>are my main applications.
+>> 
+>
+>Yep i'm trying to understand why it's working for me (or at least last time i 
+>check) with KDE 4.9.x while it is not under 4.8.x :/
+>
+>
+
+Another one kmail bug just has been fixed:
+https://bugs.kde.org/show_bug.cgi?id=304964
+this time very fast !
+
+
+
+
+
+-- 
+Dimitrios Glentadakis
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018099.html b/zarb-ml/mageia-dev/2012-August/018099.html new file mode 100644 index 000000000..03d21e60c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018099.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 13 11:52:11 CEST 2012 +

+
+ +
Le 13/08/2012 10:58, Pascal Terjan a écrit :
+> Allowing login as root over ssh with a key can save things when for
+> some reason non local auth is down, like to fix the connection to the
+> ldap server (you can also create a local emergency account for that
+> usage).
+Actually, David question was not
+"is allowing root login through ssh a good idea ?"
+
+which is not decidable anyway, but
+"in order to prevent root login in default configuration, should also 
+make use of pam_listfile in ssh pam configuration file, which is 
+redundant and unknown currently of out security-assistant-wizard ?"
+
+-- 
+BOFH excuse #434:
+
+Please state the nature of the technical emergency
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018100.html b/zarb-ml/mageia-dev/2012-August/018100.html new file mode 100644 index 000000000..97f0320e3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018100.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Aug 13 11:54:18 CEST 2012 +

+
+ +
On Mon, Aug 13, 2012 at 10:52 AM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 13/08/2012 10:58, Pascal Terjan a écrit :
+>
+>> Allowing login as root over ssh with a key can save things when for
+>> some reason non local auth is down, like to fix the connection to the
+>> ldap server (you can also create a local emergency account for that
+>> usage).
+>
+> Actually, David question was not
+> "is allowing root login through ssh a good idea ?"
+
+But I was not replying to him :)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018101.html b/zarb-ml/mageia-dev/2012-August/018101.html new file mode 100644 index 000000000..adc8e2958 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018101.html @@ -0,0 +1,149 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Anne Wilson + annew at kde.org +
+ Mon Aug 13 12:01:23 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 13/08/12 09:58, Pascal Terjan wrote:
+> On Mon, Aug 13, 2012 at 9:39 AM, Anne Wilson <annew at kde.org>
+> wrote:
+>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
+>> 
+>> On 13/08/12 08:34, Guillaume Rousse wrote:
+>>> Le 12/08/2012 21:57, David Walser a écrit :
+>>>> Johnny A. Solbu wrote:
+>>>>> On Sunday 12 August 2012 19:28, David Walser wrote:
+>>>>>> Through the PAM configuration for SSH shipped with the 
+>>>>>> openssh-server package, root login is broken.  Here's
+>>>>>> why. /etc/pam.d/sshd has: auth required pam_listfile.so
+>>>>>> item=user sense=deny file=/etc/ssh/denyusers
+>>>>>> 
+>>>>>> The file /etc/ssh/denyusers has "root" in it by default.
+>>>>> 
+>>>>> I read somewhere some time ago that PermitRootLogin in 
+>>>>> sshd_config is ignored if PAM is used. That may be the
+>>>>> reason for this.
+>>>> 
+>>>> Nope, I just tested it and that is not true.
+>>> There is an explicit comment in the configuration file: #
+>>> Depending on your PAM configuration, # PAM authentication via 
+>>> ChallengeResponseAuthentication may bypass # the setting of 
+>>> "PermitRootLogin without-password".
+>>> 
+>>> My understanding is just than some specific PAM configuration 
+>>> would eventually allow root user to authenticate through a 
+>>> password, instead of a key.
+>>> 
+>>> Regarding your original problem, feel free to commit the
+>>> relevant modifications.
+>> 
+>> Why would anyone need root login over ssh?  I don't allow it on
+>> my server and it has never caused me any problems.  Su to root
+>> works perfectly well and avoids the security risk, so I don't
+>> understand this thread.
+> 
+> Allowing login as root over ssh with a key can save things when
+> for some reason non local auth is down, like to fix the connection
+> to the ldap server (you can also create a local emergency account
+> for that usage).
+
+OK, thanks for the answer.  Looks like some more reading on this
+subject is required :-)  Although I do use login over ssh with keys
+(as user) I don't use ldap, so I've never come across this.
+
+Anne
+
+- -- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAo0GsACgkQj93fyh4cnBfqXACePg37FlvBQ8xkei9+GNXivQdo
+IA4AoIppYO9aPb2YGG8aXA16fy86RxNg
+=Om7Z
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018102.html b/zarb-ml/mageia-dev/2012-August/018102.html new file mode 100644 index 000000000..3745051ee --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018102.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Olav Vitters + olav at vitters.nl +
+ Mon Aug 13 12:04:36 CEST 2012 +

+
+ +
On Mon, Aug 13, 2012 at 09:39:07AM +0100, Anne Wilson wrote:
+> Why would anyone need root login over ssh?  I don't allow it on my
+> server and it has never caused me any problems.  Su to root works
+> perfectly well and avoids the security risk, so I don't understand
+> this thread.
+
+Remote backups. Quite easy to setup an SSH key which only runs rsync.
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018103.html b/zarb-ml/mageia-dev/2012-August/018103.html new file mode 100644 index 000000000..d387ec9cd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018103.html @@ -0,0 +1,129 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Aug 13 12:44:31 CEST 2012 +

+
+ +
On Sun, Jul 22, 2012 at 12:00 AM, Iurt the rebuild bot
+<buildsystem-daemon at mageia.org> wrote:
+> Name        : coreutils                    Relocations: (not relocatable)
+> Version     : 8.17                              Vendor: Mageia.Org
+> Release     : 2.mga3                        Build Date: Sat 21 Jul 2012 09:49:45 PM CEST
+> Install Date: (not installed)               Build Host: jonund.mageia.org
+> Group       : System/Base                   Source RPM: (none)
+> Size        : 5273984                          License: GPLv3+
+> Signature   : (none)
+> Packager    : Iurt the rebuild bot <mageia-sysadm at mageia.org>
+> URL         : http://www.gnu.org/software/coreutils/
+> Summary     : The GNU core utilities: a set of tools commonly used in shell scripts
+> Description :
+> This package is the union of the old GNU fileutils, sh-utils, and
+> textutils packages.
+>
+> These tools are the GNU versions of common useful and popular
+> file & text utilities which are used for:
+> - file management
+> - shell scripts
+> - modifying text file (spliting, joining, comparing, modifying, ...)
+>
+> Most of these programs have significant advantages over their Unix
+> counterparts, such as greater speed, additional options, and fewer
+> arbitrary limits.
+>
+> colin <colin> 8.17-2.mga3:
+> + Revision: 273158
+> - Update for usrmove
+
+This broke a few packages requiring /bin/rm or /bin/ln which are no
+longer provided by coreutils
+
+apache-portlet-1.0-api-javadoc (from apache-portlet-1.0-api)
+esmska-javadoc (from esmska)
+mx4j
+regexp-javadoc (from regexp)
+rt
+tomcat5-admin-webapps (from tomcat5)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018104.html b/zarb-ml/mageia-dev/2012-August/018104.html new file mode 100644 index 000000000..d92cc9b68 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018104.html @@ -0,0 +1,111 @@ + + + + [Mageia-dev] madwifi-source package ? + + + + + + + + + +

[Mageia-dev] madwifi-source package ?

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 13 12:54:09 CEST 2012 +

+
+ +
We have a madwifi-source package, which seems to be used as a build 
+dependency only from wpa_supplicant package. Mandriva used to also have 
+a madwifi package which wasn't imported.
+
+Given than madwifi support currently prevent wpa_supplication 1.0 to 
+build (conflicting types declaration for ‘u_int64_t'), and than we seems 
+to be perfectly happy without madwifi driver package in the 
+distribution, is it reasonable to consider than:
+- we no longer need the 'madwifi-source' package ?
+- madwifi support in wpa_supplication isn't needed anymore ?
+
+-- 
+BOFH excuse #392:
+
+It's union rules. There's nothing we can do about it. Sorry.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018105.html b/zarb-ml/mageia-dev/2012-August/018105.html new file mode 100644 index 000000000..a69d84c5a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018105.html @@ -0,0 +1,150 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Aug 13 13:02:51 CEST 2012 +

+
+ +
'Twas brillig, and Pascal Terjan at 13/08/12 11:44 did gyre and gimble:
+> On Sun, Jul 22, 2012 at 12:00 AM, Iurt the rebuild bot
+> <buildsystem-daemon at mageia.org> wrote:
+>> Name        : coreutils                    Relocations: (not relocatable)
+>> Version     : 8.17                              Vendor: Mageia.Org
+>> Release     : 2.mga3                        Build Date: Sat 21 Jul 2012 09:49:45 PM CEST
+>> Install Date: (not installed)               Build Host: jonund.mageia.org
+>> Group       : System/Base                   Source RPM: (none)
+>> Size        : 5273984                          License: GPLv3+
+>> Signature   : (none)
+>> Packager    : Iurt the rebuild bot <mageia-sysadm at mageia.org>
+>> URL         : http://www.gnu.org/software/coreutils/
+>> Summary     : The GNU core utilities: a set of tools commonly used in shell scripts
+>> Description :
+>> This package is the union of the old GNU fileutils, sh-utils, and
+>> textutils packages.
+>>
+>> These tools are the GNU versions of common useful and popular
+>> file & text utilities which are used for:
+>> - file management
+>> - shell scripts
+>> - modifying text file (spliting, joining, comparing, modifying, ...)
+>>
+>> Most of these programs have significant advantages over their Unix
+>> counterparts, such as greater speed, additional options, and fewer
+>> arbitrary limits.
+>>
+>> colin <colin> 8.17-2.mga3:
+>> + Revision: 273158
+>> - Update for usrmove
+> 
+> This broke a few packages requiring /bin/rm or /bin/ln which are no
+> longer provided by coreutils
+> 
+> apache-portlet-1.0-api-javadoc (from apache-portlet-1.0-api)
+> esmska-javadoc (from esmska)
+> mx4j
+> regexp-javadoc (from regexp)
+> rt
+> tomcat5-admin-webapps (from tomcat5)
+
+Hmm, indeed. How are these things "Provided" anyway? I mean they are not
+in the list of the --provides, so how is this resolved? Does rpm have a
+special mode for detecting these kind of provides? If so how does it
+resolve it with urpmi?
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018106.html b/zarb-ml/mageia-dev/2012-August/018106.html new file mode 100644 index 000000000..5add1f9b8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018106.html @@ -0,0 +1,150 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 13 13:17:20 CEST 2012 +

+
+ +
Le 13/08/2012 13:02, Colin Guthrie a écrit :
+> 'Twas brillig, and Pascal Terjan at 13/08/12 11:44 did gyre and gimble:
+>> On Sun, Jul 22, 2012 at 12:00 AM, Iurt the rebuild bot
+>> <buildsystem-daemon at mageia.org> wrote:
+>>> Name        : coreutils                    Relocations: (not relocatable)
+>>> Version     : 8.17                              Vendor: Mageia.Org
+>>> Release     : 2.mga3                        Build Date: Sat 21 Jul 2012 09:49:45 PM CEST
+>>> Install Date: (not installed)               Build Host: jonund.mageia.org
+>>> Group       : System/Base                   Source RPM: (none)
+>>> Size        : 5273984                          License: GPLv3+
+>>> Signature   : (none)
+>>> Packager    : Iurt the rebuild bot <mageia-sysadm at mageia.org>
+>>> URL         : http://www.gnu.org/software/coreutils/
+>>> Summary     : The GNU core utilities: a set of tools commonly used in shell scripts
+>>> Description :
+>>> This package is the union of the old GNU fileutils, sh-utils, and
+>>> textutils packages.
+>>>
+>>> These tools are the GNU versions of common useful and popular
+>>> file & text utilities which are used for:
+>>> - file management
+>>> - shell scripts
+>>> - modifying text file (spliting, joining, comparing, modifying, ...)
+>>>
+>>> Most of these programs have significant advantages over their Unix
+>>> counterparts, such as greater speed, additional options, and fewer
+>>> arbitrary limits.
+>>>
+>>> colin <colin> 8.17-2.mga3:
+>>> + Revision: 273158
+>>> - Update for usrmove
+>>
+>> This broke a few packages requiring /bin/rm or /bin/ln which are no
+>> longer provided by coreutils
+>>
+>> apache-portlet-1.0-api-javadoc (from apache-portlet-1.0-api)
+>> esmska-javadoc (from esmska)
+>> mx4j
+>> regexp-javadoc (from regexp)
+>> rt
+>> tomcat5-admin-webapps (from tomcat5)
+>
+> Hmm, indeed. How are these things "Provided" anyway? I mean they are not
+> in the list of the --provides, so how is this resolved? Does rpm have a
+> special mode for detecting these kind of provides? If so how does it
+> resolve it with urpmi?
+Unless something changed, files dependencies are resolved at 
+hdlist-generation time as soon as another package requires them.
+
+For instance, the following line in RT spec file will make genhdlist map 
+/bin/rm to coreutils in the hdlist.cz:
+Requires(postun): /bin/rm
+
+I don't know how this work at rpm level, tough, in order to make 'rpm 
+-Uvh rt-4.0.6-1.mga3.noarch" work without urpmi support. Probably 
+checking in the list of files available in the target rpm.
+
+-- 
+BOFH excuse #133:
+
+It's not plugged in.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018107.html b/zarb-ml/mageia-dev/2012-August/018107.html new file mode 100644 index 000000000..e349a2055 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018107.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 13 13:33:49 CEST 2012 +

+
+ +
On 13 August 2012 13:17, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>> Hmm, indeed. How are these things "Provided" anyway? I mean they are not
+>> in the list of the --provides, so how is this resolved? Does rpm have a
+>> special mode for detecting these kind of provides? If so how does it
+>> resolve it with urpmi?
+>
+> Unless something changed, files dependencies are resolved at
+> hdlist-generation time as soon as another package requires them.
+
+Only part of them (see media/media_info/file-deps)
+
+> For instance, the following line in RT spec file will make genhdlist map
+> /bin/rm to coreutils in the hdlist.cz:
+> Requires(postun): /bin/rm
+>
+> I don't know how this work at rpm level, tough, in order to make 'rpm -Uvh
+> rt-4.0.6-1.mga3.noarch" work without urpmi support. Probably checking in the
+> list of files available in the target rpm.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018108.html b/zarb-ml/mageia-dev/2012-August/018108.html new file mode 100644 index 000000000..036195098 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018108.html @@ -0,0 +1,160 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Olivier Blin + mageia at blino.org +
+ Mon Aug 13 14:00:53 CEST 2012 +

+
+ +
Guillaume Rousse <guillomovitch at gmail.com> writes:
+
+> Le 13/08/2012 13:02, Colin Guthrie a écrit :
+>> 'Twas brillig, and Pascal Terjan at 13/08/12 11:44 did gyre and gimble:
+>>> On Sun, Jul 22, 2012 at 12:00 AM, Iurt the rebuild bot
+>>> <buildsystem-daemon at mageia.org> wrote:
+>>>> Name        : coreutils                    Relocations: (not relocatable)
+>>>> Version     : 8.17                              Vendor: Mageia.Org
+>>>> Release     : 2.mga3                        Build Date: Sat 21 Jul 2012 09:49:45 PM CEST
+
+[...]
+
+>>>> colin <colin> 8.17-2.mga3:
+>>>> + Revision: 273158
+>>>> - Update for usrmove
+>>>
+>>> This broke a few packages requiring /bin/rm or /bin/ln which are no
+>>> longer provided by coreutils
+>>>
+>>> apache-portlet-1.0-api-javadoc (from apache-portlet-1.0-api)
+>>> esmska-javadoc (from esmska)
+>>> mx4j
+>>> regexp-javadoc (from regexp)
+>>> rt
+>>> tomcat5-admin-webapps (from tomcat5)
+>>
+>> Hmm, indeed. How are these things "Provided" anyway? I mean they are not
+>> in the list of the --provides, so how is this resolved? Does rpm have a
+>> special mode for detecting these kind of provides? If so how does it
+>> resolve it with urpmi?
+> Unless something changed, files dependencies are resolved at
+> hdlist-generation time as soon as another package requires them.
+
+Yes, using the file-deps file.
+
+> For instance, the following line in RT spec file will make genhdlist
+> map /bin/rm to coreutils in the hdlist.cz:
+> Requires(postun): /bin/rm
+
+IIRC, if a package contains files listed in file-deps, these files are
+added to its "provides" list by genhdlist.
+
+$ zcat
+/distrib/mageia/distrib/2/x86_64/media/core/release/media_info/synthesis.hdlist.cz
+| grep -A 6 '^\@provides.*\@/bin/rm'
+@provides at mktemp[== 8.15]@stat[==
+8.15]@/usr/bin/env@/bin/env at libstdbuf.so()(64bit)@coreutils[==
+8.15-1.mga2]@coreutils(x86-64)[==
+8.15-1.mga2]@/bin/rm@/bin/ls@/bin/stty@/usr/bin/tr@/bin/ln@/bin/cp
+@conflicts at tetex[< 1.0.7-49]
+@obsoletes at mktemp[< 8.15]@base64
+@requires at pam[>=
+0.66-12]@libacl.so.1()(64bit)@libattr.so.1()(64bit)@libc.so.6()(64bit)@libc.so.6(GLIBC_2.14)(64bit)@libc.so.6(GLIBC_2.2.5)(64bit)@libc.so.6(GLIBC_2.3)(64bit)@libc.so.6(GLIBC_2.3.4)(64bit)@libc.so.6(GLIBC_2.4)(64bit)@libc.so.6(GLIBC_2.6)(64bit)@libc.so.6(GLIBC_2.7)(64bit)@libcap.so.2()(64bit)@libgmp.so.10()(64bit)@libpam.so.0()(64bit)@libpam_misc.so.0()(64bit)@libpthread.so.0()(64bit)@libpthread.so.0(GLIBC_2.2.5)(64bit)@libpthread.so.0(GLIBC_2.3.2)(64bit)@librt.so.1()(64bit)@librt.so.1(GLIBC_2.2.5)(64bit)@librt.so.1(GLIBC_2.3.3)(64bit)@rtld(GNU_HASH)
+@summary at The GNU core utilities: a set of tools commonly used in shell
+scripts
+@filesize at 1803563
+@info at coreutils-8.15-1.mga2.x86_64@0 at 12798923@System/Base
+
+> I don't know how this work at rpm level, tough, in order to make 'rpm
+> -Uvh rt-4.0.6-1.mga3.noarch" work without urpmi support. Probably
+> checking in the list of files available in the target rpm.
+
+rpm is likely using the list of files from its db
+
+$ rpm -q --provides coreutils | grep /bin/rm
+$ rpm -q --whatprovides /bin/rm
+coreutils-8.17-3.mga3
+
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018109.html b/zarb-ml/mageia-dev/2012-August/018109.html new file mode 100644 index 000000000..52fa8f261 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018109.html @@ -0,0 +1,160 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Aug 13 14:17:02 CEST 2012 +

+
+ +
On Mon, Aug 13, 2012 at 1:00 PM, Olivier Blin <mageia at blino.org> wrote:
+> Guillaume Rousse <guillomovitch at gmail.com> writes:
+>
+>> Le 13/08/2012 13:02, Colin Guthrie a écrit :
+>>> 'Twas brillig, and Pascal Terjan at 13/08/12 11:44 did gyre and gimble:
+>>>> On Sun, Jul 22, 2012 at 12:00 AM, Iurt the rebuild bot
+>>>> <buildsystem-daemon at mageia.org> wrote:
+>>>>> Name        : coreutils                    Relocations: (not relocatable)
+>>>>> Version     : 8.17                              Vendor: Mageia.Org
+>>>>> Release     : 2.mga3                        Build Date: Sat 21 Jul 2012 09:49:45 PM CEST
+>
+> [...]
+>
+>>>>> colin <colin> 8.17-2.mga3:
+>>>>> + Revision: 273158
+>>>>> - Update for usrmove
+>>>>
+>>>> This broke a few packages requiring /bin/rm or /bin/ln which are no
+>>>> longer provided by coreutils
+>>>>
+>>>> apache-portlet-1.0-api-javadoc (from apache-portlet-1.0-api)
+>>>> esmska-javadoc (from esmska)
+>>>> mx4j
+>>>> regexp-javadoc (from regexp)
+>>>> rt
+>>>> tomcat5-admin-webapps (from tomcat5)
+>>>
+>>> Hmm, indeed. How are these things "Provided" anyway? I mean they are not
+>>> in the list of the --provides, so how is this resolved? Does rpm have a
+>>> special mode for detecting these kind of provides? If so how does it
+>>> resolve it with urpmi?
+>> Unless something changed, files dependencies are resolved at
+>> hdlist-generation time as soon as another package requires them.
+>
+> Yes, using the file-deps file.
+>
+>> For instance, the following line in RT spec file will make genhdlist
+>> map /bin/rm to coreutils in the hdlist.cz:
+>> Requires(postun): /bin/rm
+>
+> IIRC, if a package contains files listed in file-deps, these files are
+> added to its "provides" list by genhdlist.
+>
+> $ zcat
+> /distrib/mageia/distrib/2/x86_64/media/core/release/media_info/synthesis.hdlist.cz
+> | grep -A 6 '^\@provides.*\@/bin/rm'
+> @provides at mktemp[== 8.15]@stat[==
+> 8.15]@/usr/bin/env@/bin/env at libstdbuf.so()(64bit)@coreutils[==
+> 8.15-1.mga2]@coreutils(x86-64)[==
+> 8.15-1.mga2]@/bin/rm@/bin/ls@/bin/stty@/usr/bin/tr@/bin/ln@/bin/cp
+> @conflicts at tetex[< 1.0.7-49]
+> @obsoletes at mktemp[< 8.15]@base64
+> @requires at pam[>=
+> 0.66-12]@libacl.so.1()(64bit)@libattr.so.1()(64bit)@libc.so.6()(64bit)@libc.so.6(GLIBC_2.14)(64bit)@libc.so.6(GLIBC_2.2.5)(64bit)@libc.so.6(GLIBC_2.3)(64bit)@libc.so.6(GLIBC_2.3.4)(64bit)@libc.so.6(GLIBC_2.4)(64bit)@libc.so.6(GLIBC_2.6)(64bit)@libc.so.6(GLIBC_2.7)(64bit)@libcap.so.2()(64bit)@libgmp.so.10()(64bit)@libpam.so.0()(64bit)@libpam_misc.so.0()(64bit)@libpthread.so.0()(64bit)@libpthread.so.0(GLIBC_2.2.5)(64bit)@libpthread.so.0(GLIBC_2.3.2)(64bit)@librt.so.1()(64bit)@librt.so.1(GLIBC_2.2.5)(64bit)@librt.so.1(GLIBC_2.3.3)(64bit)@rtld(GNU_HASH)
+> @summary at The GNU core utilities: a set of tools commonly used in shell
+> scripts
+> @filesize at 1803563
+> @info at coreutils-8.15-1.mga2.x86_64@0 at 12798923@System/Base
+>
+>> I don't know how this work at rpm level, tough, in order to make 'rpm
+>> -Uvh rt-4.0.6-1.mga3.noarch" work without urpmi support. Probably
+>> checking in the list of files available in the target rpm.
+>
+> rpm is likely using the list of files from its db
+>
+> $ rpm -q --provides coreutils | grep /bin/rm
+> $ rpm -q --whatprovides /bin/rm
+> coreutils-8.17-3.mga3
+
+Yes rpm uses the list of files to satisfy provides, urpmi does not
+when using synthesis as synthesis does not contain the list of files
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018110.html b/zarb-ml/mageia-dev/2012-August/018110.html new file mode 100644 index 000000000..a05a9b8c0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018110.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Maurice Batey + maurice at bcs.org.uk +
+ Mon Aug 13 14:23:08 CEST 2012 +

+
+ +
On Sun, 12 Aug 2012 15:12:27 -0300, Balcaen John wrote:
+
+> Well it's working better with kdepim 4.9.x
+
+  Glad to hear of some progress!
+
+But I can't move over from Mandriva (KDE 4.5.2) to Mageia until KMail's
+Find Messages is back to normal.
+
+  (Apart from that, KMail in Mageia-2 was working very well for me.)
+
+-- 
+/\/\aurice 
+	
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018111.html b/zarb-ml/mageia-dev/2012-August/018111.html new file mode 100644 index 000000000..8cf61d09a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018111.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Angelo Naselli + anaselli at linux.it +
+ Mon Aug 13 14:28:48 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 13/08/2012 14:23, Maurice Batey ha scritto:
+> But I can't move over from Mandriva (KDE 4.5.2) to Mageia until
+> KMail's Find Messages is back to normal.
+I'm not sure but finding messages should managed by nepomuk now
+(another thing that on my amd X6 takes 95% of cpu for indexing :/ )
+and as far as i know it works...
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAo8v0ACgkQqEs9DA4DquCWcwCdGUGZmgLPoBSFP04nXaTPW0sk
+GlsAni+oinRvzqvppDRF/hbY5A5D6R7v
+=hTip
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018112.html b/zarb-ml/mageia-dev/2012-August/018112.html new file mode 100644 index 000000000..ff8f7de0f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018112.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Dimitrios Glentadakis + dglent at gmail.com +
+ Mon Aug 13 14:39:23 CEST 2012 +

+
+ +
Στις 13/08/2012 13:23:08 Maurice Batey έγραψε:
+>On Sun, 12 Aug 2012 15:12:27 -0300, Balcaen John wrote:
+>
+>> Well it's working better with kdepim 4.9.x
+>
+>  Glad to hear of some progress!
+>
+>But I can't move over from Mandriva (KDE 4.5.2) to Mageia until KMail's
+>Find Messages is back to normal.
+>
+>  (Apart from that, KMail in Mageia-2 was working very well for me.)
+>
+>
+
+What exact it does nt work in Find Messages?
+I don't use it (i use the search bar in the top) but i tried from the Edit menu → Find messages, there i entered a keyword of a subject
+and i had as result all mached messagest.
+Is this function which it does nt work for you ?
+(i have nepomuk enabled)
+
+
+-- 
+Dimitrios Glentadakis
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018113.html b/zarb-ml/mageia-dev/2012-August/018113.html new file mode 100644 index 000000000..ccb643cf2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018113.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] madwifi-source package ? + + + + + + + + + +

[Mageia-dev] madwifi-source package ?

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Mon Aug 13 15:11:37 CEST 2012 +

+
+ +
On Mon, 13 Aug 2012, Guillaume Rousse wrote:
+
+> We have a madwifi-source package, which seems to be used as a build 
+> dependency only from wpa_supplicant package. Mandriva used to also have a 
+> madwifi package which wasn't imported.
+>
+> Given than madwifi support currently prevent wpa_supplication 1.0 to build 
+> (conflicting types declaration for ‘u_int64_t'), and than we seems to be 
+> perfectly happy without madwifi driver package in the distribution, is it 
+> reasonable to consider than:
+> - we no longer need the 'madwifi-source' package ?
+> - madwifi support in wpa_supplication isn't needed anymore ?
+
+I dropped support for this driver from hostapd because of that build 
+problem, but I don't know if anyone is going to complain about that. 
+AFAICT there is now an alternative "free" driver for these devices: ath5k.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018114.html b/zarb-ml/mageia-dev/2012-August/018114.html new file mode 100644 index 000000000..2ac7d3746 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018114.html @@ -0,0 +1,117 @@ + + + + [Mageia-dev] madwifi-source package ? + + + + + + + + + +

[Mageia-dev] madwifi-source package ?

+ Angelo Naselli + anaselli at linux.it +
+ Mon Aug 13 16:21:40 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 13/08/2012 12:54, Guillaume Rousse ha scritto:
+> We have a madwifi-source package, which seems to be used as a
+> build dependency only from wpa_supplicant package. Mandriva used to
+> also have a madwifi package which wasn't imported.
+> 
+> Given than madwifi support currently prevent wpa_supplication 1.0
+> to build (conflicting types declaration for ‘u_int64_t'), and than
+> we seems to be perfectly happy without madwifi driver package in
+> the distribution, is it reasonable to consider than: - we no longer
+> need the 'madwifi-source' package ? - madwifi support in
+> wpa_supplication isn't needed anymore ?
+> 
+Well I have an old dlink card that used madwifi and that
+i'm not using any more at the moment, I could try it
+again -when back from holidays- with the free driver and see
+if i have any problems and eventually going back on this subject.
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlApDXEACgkQqEs9DA4DquAORgCfe3FotK6fpppBCxmPSRDO1ARf
+t1kAnRAOCtwCyJVksitlL6Qs0J4NV2Lk
+=k9EJ
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018115.html b/zarb-ml/mageia-dev/2012-August/018115.html new file mode 100644 index 000000000..fbe488552 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018115.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] madwifi-source package ? + + + + + + + + + +

[Mageia-dev] madwifi-source package ?

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 13 16:23:18 CEST 2012 +

+
+ +
Le 13/08/2012 16:21, Angelo Naselli a écrit :
+> Well I have an old dlink card that used madwifi and that
+> i'm not using any more at the moment, I could try it
+> again -when back from holidays- with the free driver and see
+> if i have any problems and eventually going back on this subject.
+The point is: what other alternative do you have, as we don't seem to 
+have any madwifi driver package in the distribution ?
+
+-- 
+BOFH excuse #294:
+
+PCMCIA slave driver
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018116.html b/zarb-ml/mageia-dev/2012-August/018116.html new file mode 100644 index 000000000..20ddebd55 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018116.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] madwifi-source package ? + + + + + + + + + +

[Mageia-dev] madwifi-source package ?

+ Angelo Naselli + anaselli at linux.it +
+ Mon Aug 13 16:28:33 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Il 13/08/2012 16:23, Guillaume Rousse ha scritto:
+> Le 13/08/2012 16:21, Angelo Naselli a écrit :
+>> Well I have an old dlink card that used madwifi and that i'm not
+>> using any more at the moment, I could try it again -when back
+>> from holidays- with the free driver and see if i have any
+>> problems and eventually going back on this subject.
+> The point is: what other alternative do you have, as we don't seem
+> to have any madwifi driver package in the distribution ?
+
+Well as said i'm not using it any more, so i hadn't noticed that :)
+
+I always built drivers by myself in past, iirc it has not been always
+available in mandrake repositories just in the recent past...
+
+The point is also if we have any other users needing it and,
+can we support all old hardware? I'd like that, but i think it's not
+always possible by our resources... am I wrong?
+
+Angelo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlApDxEACgkQqEs9DA4DquDQDACeOwK9dSOdNKI/89srYsjfdBq+
+naMAn2mcu5bdelDptIWbU9KZdfc1hzzx
+=QpMJ
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018117.html b/zarb-ml/mageia-dev/2012-August/018117.html new file mode 100644 index 000000000..6128524c4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018117.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2 + + + + + + + + + +

[Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2

+ Scott Chevalley + avalon at osguru.org +
+ Mon Aug 13 17:04:06 CEST 2012 +

+
+ +
In trying to update my system today I noticed that urpmi wanted to remove a log
+of kdepim packages so I ran urpmi with --keep and noticed:
+
+# urpmi --auto-select --keep
+A requested package cannot be installed:
+lib64gpgme11-1.3.2-1.mga3.x86_64 (in order to keep
+lib64gpgme++2-4.9.0-2.mga3.x86_64)
+Continue installation anyway? (Y/n) n
+
+
+I do have lib64gpgme11-1.3.1-2 installed, and doing urpmq --conflicts or
+--obsoletes on the new version of lib64gpgme11 shows nothing, so I'm not sure
+why it wants to remove a kde core lib during the update.
+
+Just thought I'd throw it out there in case no one has seen it yet.
+
+
+Thanks!
+Scott
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018118.html b/zarb-ml/mageia-dev/2012-August/018118.html new file mode 100644 index 000000000..cb137e5e8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018118.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Mon Aug 13 17:06:47 CEST 2012 +

+
+ +
* Philippe Reynes (tremyfr at yahoo.fr) wrote:
+> Hi all,
+> 
+> I've found that I have three glibc installed on my box.
+> 
+> [trem at localhost ~]$ rpm -q glibc
+> glibc-2.14.1-8.mga2
+> glibc-2.16-7.mga3
+> glibc-2.16-8.mga3
+
+Indeed:
+
+[root at apus bug-glibc]# rpm -q glibc
+glibc-2.14.1-8.mga2
+glibc-2.16-5.mga3
+glibc-2.16-8.mga3
+
+I wonder if it's not systemd fault:
+
+- systemd is installed and the line is added to /etc/pam.d/system-auth
+  (sshd is not restarted)
+- later I urpmi --auto-update, a new glibc is installed and at end of
+  install sshd get restarted - this included my session - rpm is killed
+  too.
+
+But also the good question is why sshd is restarted when the glibc get
+updated. This is no real reason and this can cause issue if locale need
+an update too.
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120813/a4921019/attachment.asc>
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018119.html b/zarb-ml/mageia-dev/2012-August/018119.html new file mode 100644 index 000000000..5744ba331 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018119.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 13 17:18:58 CEST 2012 +

+
+ +
On 13 August 2012 17:06, Olivier Thauvin <nanardon at nanardon.zarb.org> wrote:
+> Indeed:
+>
+> [root at apus bug-glibc]# rpm -q glibc
+> glibc-2.14.1-8.mga2
+> glibc-2.16-5.mga3
+> glibc-2.16-8.mga3
+>
+> I wonder if it's not systemd fault:
+>
+> - systemd is installed and the line is added to /etc/pam.d/system-auth
+>   (sshd is not restarted)
+> - later I urpmi --auto-update, a new glibc is installed and at end of
+>   install sshd get restarted - this included my session - rpm is killed
+>   too.
+>
+> But also the good question is why sshd is restarted when the glibc get
+> updated. This is no real reason and this can cause issue if locale need
+> an update too.
+
+Remember 10 years ago, flepied wanted us to restart services on glibc upgrade
+for security concerns & b/c:
+
+  # On upgrade the services doesn't work because libnss couldn't be
+  # loaded anymore.
+
+Over the time, only sshd remains.
+Now that urpmi advices to reboot, we could skip that %post script bit
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018120.html b/zarb-ml/mageia-dev/2012-August/018120.html new file mode 100644 index 000000000..1480203ec --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018120.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Maurice Batey + maurice at bcs.org.uk +
+ Mon Aug 13 17:36:49 CEST 2012 +

+
+ +
On Mon, 13 Aug 2012 14:39:23 +0200, Dimitrios Glentadakis wrote:
+
+> What exact it does nt work in Find Messages?
+
+See:  https://bugs.kde.org/show_bug.cgi?id=281227
+         https://bugs.kde.org/show_bug.cgi?id=294568
+
+In there you will see, e.g. this posting from me:
+
+    "As a test, I did a Find Messages for "gmail.com" in the 'To' fields
+    of  a  Sent-mail folder containing 4,886 emails. 
+
+   KDE 4.5.2's  KMail (1.13.5) found *395* emails sent to someone at
+   gmail.com 
+
+   KDE 4.8.2 on the other hand - given the same email Sent-mail
+   folder  - found only *11*  matches:
+	      5 'this week' 
+              1 last week 
+              1 in 2005 
+              4 in 2004 
+     - which leads me to conclude that 4.8.2's Find Messages is well and
+     truly  broken, and so unusable, thus rendering KMail 4.8.2 itself
+     unusable.."
+
+See also postings there from many other users.
+
+-- 
+/\/\aurice 
+	
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018121.html b/zarb-ml/mageia-dev/2012-August/018121.html new file mode 100644 index 000000000..654a22604 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018121.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 13 17:41:53 CEST 2012 +

+
+ +
Colin Guthrie wrote:
+> Hmm, indeed. How are these things "Provided" anyway? I mean they are not
+> in the list of the --provides, so how is this resolved? Does rpm have a
+> special mode for detecting these kind of provides? If so how does it
+> resolve it with urpmi?
+
+Since the UsrMove, I've seen Fedora add explicit Provides: /bin/{foo} things to some packages, presumably because of this same problem.
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018122.html b/zarb-ml/mageia-dev/2012-August/018122.html new file mode 100644 index 000000000..0416579e5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018122.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ nicolas vigier + boklm at mars-attacks.org +
+ Mon Aug 13 17:49:33 CEST 2012 +

+
+ +
On Tue, 07 Aug 2012, Pascal Terjan wrote:
+
+> On Tue, Aug 7, 2012 at 12:31 PM, Olivier Thauvin
+> <nanardon at nanardon.zarb.org> wrote:
+> > Hi,
+> >
+> > Many people already complain about it, but for me task-obsolete must
+> > die.
+> 
+> I don't think so, but people should not be allowed to add random
+> obsoletes there.
+> 
+> > First I just remove but urpmi claim it must come back on my system...
+> > probably because it claim to replace lib64db5.2, even maybe still need
+> > it.
+> >
+> > Secondly it contains non-sense dependencies:
+> > Obsoletes: lib64db5.2 < 5.2.42-3
+> >
+> > Any lib64db5.2 over this version will by definition obsoletes any
+> > packages having same name.
+> > So this mean anyone can keep the lib64db5.2 as soon the release tag
+> > is increased or someone push into mga 2 / update any libdb higher
+> > than 5.2.42 (5.2.43 for example).
+> >
+> > Moreover, any package lacking of requirements during an upgrade is
+> > removed by urpmi.
+> >
+> > I no-one complain, I'll do a major cleanup (eg removing everything at
+> > least everything starting by lib) in package this week
+> >
+> > But I am still in favor to remove it. In past, package we didn't want to
+> > support anymore was just removed from mirrors, and this was enough to
+> > show their status.
+> 
+> But people will not be notified of it.
+> If a system is obsolete with the new distribution and known to break
+> things/contain major security problems, I think having a place to put
+> the obsoletes is good.
+> But really I wouldn't expect more than 2 or 3 such packages in a release...
+
+Maybe we could change task-obsolete to conflict with obsolete packages
+instead of obsoleting them :
+- people who want to remove unsupported packages from their system
+  install task-obsolete
+- people who don't want to remove unsupported packages don't install
+  task-obsolete
+
+This will also make urpmi/rpmdrake warn before removing packages,
+instead of silently removing them.
+
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018123.html b/zarb-ml/mageia-dev/2012-August/018123.html new file mode 100644 index 000000000..86afab9dd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018123.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Anne Wilson + annew at kde.org +
+ Mon Aug 13 19:06:13 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 13/08/12 11:04, Olav Vitters wrote:
+> On Mon, Aug 13, 2012 at 09:39:07AM +0100, Anne Wilson wrote:
+>> Why would anyone need root login over ssh?  I don't allow it on
+>> my server and it has never caused me any problems.  Su to root
+>> works perfectly well and avoids the security risk, so I don't
+>> understand this thread.
+> 
+> Remote backups. Quite easy to setup an SSH key which only runs
+> rsync.
+> 
+I use rsync on the server for local backups, and I use SSH with keys
+to access the server from laptops for maintenance tasks, but I have
+never managed to make rsync over ssh with keys work.  People tell me
+to just use ssh without keys, but I'm reluctant to do that.  Maybe one
+day I'll find something that steps me through it, so that I can find
+the missing link.
+
+Of course, I tend to back up user data rather than system, so again, I
+don't need remote root login.
+
+Anne
+- -- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlApNAMACgkQj93fyh4cnBctjwCfWyyeZqyuNQZMF8kgHcBodOJL
+88kAn05B09a/3oVNwyoJkfHZ2sSZ3DdZ
+=iwl/
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018124.html b/zarb-ml/mageia-dev/2012-August/018124.html new file mode 100644 index 000000000..85615aa80 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018124.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Dimitrios Glentadakis + dglent at gmail.com +
+ Mon Aug 13 19:16:43 CEST 2012 +

+
+ +
2012/8/13 Maurice Batey <maurice at bcs.org.uk>
+
+> On Mon, 13 Aug 2012 14:39:23 +0200, Dimitrios Glentadakis wrote:
+>
+> > What exact it does nt work in Find Messages?
+>
+> See:  https://bugs.kde.org/show_bug.cgi?id=281227
+>          https://bugs.kde.org/show_bug.cgi?id=294568
+>
+> In there you will see, e.g. this posting from me:
+>
+>     "As a test, I did a Find Messages for "gmail.com" in the 'To' fields
+>     of  a  Sent-mail folder containing 4,886 emails.
+>
+>    KDE 4.5.2's  KMail (1.13.5) found *395* emails sent to someone at
+>    gmail.com
+>
+>    KDE 4.8.2 on the other hand - given the same email Sent-mail
+>    folder  - found only *11*  matches:
+>               5 'this week'
+>               1 last week
+>               1 in 2005
+>               4 in 2004
+>      - which leads me to conclude that 4.8.2's Find Messages is well and
+>      truly  broken, and so unusable, thus rendering KMail 4.8.2 itself
+>      unusable.."
+>
+> See also postings there from many other users.
+>
+> --
+> /\/\aurice
+>
+>
+>
+When i tried a search in the 'To' field the results were wrong to me too,
+and when i repeated the search there were worst !
+Hope to be fixed soon, as this one:
+https://bugs.kde.org/show_bug.cgi?id=301099
+and this one:
+https://bugs.kde.org/show_bug.cgi?id=304741
+
+
+-- 
+Dimitrios Glentadakis
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120813/58f09019/attachment.html>
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018125.html b/zarb-ml/mageia-dev/2012-August/018125.html new file mode 100644 index 000000000..113390157 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018125.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release coreutils-8.17-2.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Mon Aug 13 20:09:51 CEST 2012 +

+
+ +
On Mon, Aug 13, 2012 at 11:44 AM, Pascal Terjan <pterjan at gmail.com> wrote:
+> This broke a few packages requiring /bin/rm or /bin/ln which are no
+> longer provided by coreutils
+>
+> apache-portlet-1.0-api-javadoc (from apache-portlet-1.0-api)
+> esmska-javadoc (from esmska)
+> mx4j
+> regexp-javadoc (from regexp)
+> rt
+> tomcat5-admin-webapps (from tomcat5)
+
+Good news is that the *-javadoc ones seem to be hardcoded
+Requires(post): /bin/rm,/bin/ln which are useless as the packages
+don't have %post
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018126.html b/zarb-ml/mageia-dev/2012-August/018126.html new file mode 100644 index 000000000..744dc3c7f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018126.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2 + + + + + + + + + +

[Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 13 23:03:17 CEST 2012 +

+
+ +
Scott Chevalley <avalon at ...> writes:
+> # urpmi --auto-select --keep
+> A requested package cannot be installed:
+> lib64gpgme11-1.3.2-1.mga3.x86_64 (in order to keep
+> lib64gpgme++2-4.9.0-2.mga3.x86_64)
+> Continue installation anyway? (Y/n) n
+
+Maybe kdepimlibs4 needs to be rebuilt.
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018127.html b/zarb-ml/mageia-dev/2012-August/018127.html new file mode 100644 index 000000000..a45f74ea0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018127.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2 + + + + + + + + + +

[Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Mon Aug 13 23:04:37 CEST 2012 +

+
+ +
Le lundi 13 août 2012 21:03:17 David Walser a écrit :
+> Scott Chevalley <avalon at ...> writes:
+> > # urpmi --auto-select --keep
+> > A requested package cannot be installed:
+> > lib64gpgme11-1.3.2-1.mga3.x86_64 (in order to keep
+> > lib64gpgme++2-4.9.0-2.mga3.x86_64)
+> > Continue installation anyway? (Y/n) n
+> 
+> Maybe kdepimlibs4 needs to be rebuilt.
+
+i take a look then. thanks
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018128.html b/zarb-ml/mageia-dev/2012-August/018128.html new file mode 100644 index 000000000..b0aa6cb4f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018128.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2 + + + + + + + + + +

[Mageia-dev] lib64gpgme11-1.3.2-1 is wanting to remove lib64gpgme++2

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Mon Aug 13 23:19:06 CEST 2012 +

+
+ +
Le lundi 13 août 2012 21:03:17 David Walser a écrit :
+> Scott Chevalley <avalon at ...> writes:
+> > # urpmi --auto-select --keep
+> > A requested package cannot be installed:
+> > lib64gpgme11-1.3.2-1.mga3.x86_64 (in order to keep
+> > lib64gpgme++2-4.9.0-2.mga3.x86_64)
+> > Continue installation anyway? (Y/n) n
+> 
+> Maybe kdepimlibs4 needs to be rebuilt.
+
+i looked to understand the issue.
+
+libgpgme-pth does not exist anymore   ( from gpgme NEWS file )
+
+* Remove support for libgpgme-pth.  As far as we know, this was never used,
+   and GnuPG is going to use our own npth in the future.
+
+So as kdepimlibs4 required this lib, i just asked for a rebuild, should be OK 
+soon.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018129.html b/zarb-ml/mageia-dev/2012-August/018129.html new file mode 100644 index 000000000..3b1d950f6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018129.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Balcaen John + mikala at mageia.org +
+ Mon Aug 13 23:53:22 CEST 2012 +

+
+ +
Le lundi 13 août 2012 11:42:38 Dimitrios Glentadakis a écrit :
+[...]
+> 
+> Another one kmail bug just has been fixed:
+> https://bugs.kde.org/show_bug.cgi?id=304964
+> this time very fast !
+Fix added locally,
+I'll check 4.9 tree to see if there's anything which can be easily backported.
+And if you have some i'm open to suggestions of course ;o)
+
+
+-- 
+Balcaen John
+
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018130.html b/zarb-ml/mageia-dev/2012-August/018130.html new file mode 100644 index 000000000..005049eb2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018130.html @@ -0,0 +1,119 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ andre999 + andre999mga at laposte.net +
+ Tue Aug 14 01:55:23 CEST 2012 +

+
+ +
nicolas vigier a écrit :
+> On Tue, 07 Aug 2012, Pascal Terjan wrote:
+>
+>    
+>> On Tue, Aug 7, 2012 at 12:31 PM, Olivier Thauvin
+>> <nanardon at nanardon.zarb.org>  wrote:
+>>      
+>>> Hi,
+>>>
+>>> Many people already complain about it, but for me task-obsolete must
+>>> die.
+>>>        
+>> I don't think so, but people should not be allowed to add random
+>> obsoletes there.
+>>
+>>      
+>>> First I just remove but urpmi claim it must come back on my system...
+>>> probably because it claim to replace lib64db5.2, even maybe still need
+>>> it.
+>>>
+>>> Secondly it contains non-sense dependencies:
+>>> Obsoletes: lib64db5.2<  5.2.42-3
+>>>
+>>> Any lib64db5.2 over this version will by definition obsoletes any
+>>> packages having same name.
+>>> So this mean anyone can keep the lib64db5.2 as soon the release tag
+>>> is increased or someone push into mga 2 / update any libdb higher
+>>> than 5.2.42 (5.2.43 for example).
+>>>
+>>> Moreover, any package lacking of requirements during an upgrade is
+>>> removed by urpmi.
+>>>
+>>> I no-one complain, I'll do a major cleanup (eg removing everything at
+>>> least everything starting by lib) in package this week
+>>>
+>>> But I am still in favor to remove it. In past, package we didn't want to
+>>> support anymore was just removed from mirrors, and this was enough to
+>>> show their status.
+>>>        
+>> But people will not be notified of it.
+>> If a system is obsolete with the new distribution and known to break
+>> things/contain major security problems, I think having a place to put
+>> the obsoletes is good.
+>> But really I wouldn't expect more than 2 or 3 such packages in a release...
+>>      
+> Maybe we could change task-obsolete to conflict with obsolete packages
+> instead of obsoleting them :
+> - people who want to remove unsupported packages from their system
+>    install task-obsolete
+> - people who don't want to remove unsupported packages don't install
+>    task-obsolete
+>
+> This will also make urpmi/rpmdrake warn before removing packages,
+> instead of silently removing them.
+>
+>    
++1
+Conflicts would also make it easier to remove task-obsolete, if one had 
+inadvertantly installed it.
+
+-- 
+André
+
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018131.html b/zarb-ml/mageia-dev/2012-August/018131.html new file mode 100644 index 000000000..6f63d375f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018131.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 02:49:40 CEST 2012 +

+
+ +
I have deliberately postponed updating my cauldron install, waiting for most issues to be resolved, so tonight after the usrmove thread died out, I figured most issues were resolved and I attempted to move forward and update my system.
+However it fails, and only 7 packages is upgraded/installed before it exits with an error.
+
+Here is the session logs.
+These packages was installed, according to syslog: http://www.solbu.net/usrmove/urpmi-update-fail-2.txt
+
+And this is the output after the second try: http://www.solbu.net/usrmove/urpmi-update-fail.txt 
+	(the only difference between the first try and this is that i used "--auto-update" the first time)
+
+Now what? :-)=
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/10786e14/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018132.html b/zarb-ml/mageia-dev/2012-August/018132.html new file mode 100644 index 000000000..ef70331a1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018132.html @@ -0,0 +1,105 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Funda Wang + fundawang at gmail.com +
+ Tue Aug 14 02:59:45 CEST 2012 +

+
+ +
There is a newer drakconf in mga2 than mga3.
+
+在 2012年8月14日星期二，Johnny A. Solbu <cooker at solbu.net> 写道：
+> I have deliberately postponed updating my cauldron install, waiting for
+most issues to be resolved, so tonight after the usrmove thread died out, I
+figured most issues were resolved and I attempted to move forward and
+update my system.
+> However it fails, and only 7 packages is upgraded/installed before it
+exits with an error.
+>
+> Here is the session logs.
+> These packages was installed, according to syslog:
+http://www.solbu.net/usrmove/urpmi-update-fail-2.txt
+>
+> And this is the output after the second try:
+http://www.solbu.net/usrmove/urpmi-update-fail.txt
+>         (the only difference between the first try and this is that i
+used "--auto-update" the first time)
+>
+> Now what? :-)=
+> --
+> Johnny A. Solbu
+> PGP key ID: 0xFA687324
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120814/2e9865d5/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018133.html b/zarb-ml/mageia-dev/2012-August/018133.html new file mode 100644 index 000000000..f544291d6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018133.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 03:08:24 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 02:59, Funda Wang wrote:
+> There is a newer drakconf in mga2 than mga3.
+
+Looks like the maintainer (Vignaud) should update drakconf then.
+I can wait for that. :-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/ecf08ea3/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018134.html b/zarb-ml/mageia-dev/2012-August/018134.html new file mode 100644 index 000000000..63aeffb14 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018134.html @@ -0,0 +1,125 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Charles A Edwards + CAE at eslrahc.com +
+ Tue Aug 14 04:26:02 CEST 2012 +

+
+ +
On Tue, 14 Aug 2012 01:49:40 +0100
+Johnny A. Solbu wrote:
+
+> I have deliberately postponed updating my cauldron install, waiting
+> for most issues to be resolved, so tonight after the usrmove thread
+> died out, I figured most issues were resolved and I attempted to move
+> forward and update my system. However it fails, and only 7 packages
+> is upgraded/installed before it exits with an error.
+> 
+> Here is the session logs.
+> These packages was installed, according to syslog:
+> http://www.solbu.net/usrmove/urpmi-update-fail-2.txt
+> 
+> And this is the output after the second try:
+> http://www.solbu.net/usrmove/urpmi-update-fail.txt (the only
+> difference between the first try and this is that i used
+> "--auto-update" the first time)
+
+Have you actually done the fs conversion or not?
+
+If you have not it must be done before you can properly update your
+system.
+
+If you have done the conversion you need to take the block off of
+filesystem, ncurses.
+Not updating filesystem is the main cause of the urpmi removals/install
+failures you received not drakconf. 
+
+
+    Charles
+
+-- 
+Just because the message may never be received does not mean it is
+not worth sending.
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.1-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120813/4dcb4e04/attachment-0001.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018135.html b/zarb-ml/mageia-dev/2012-August/018135.html new file mode 100644 index 000000000..178b3d06e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018135.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 05:20:31 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 04:26, Charles A Edwards wrote:
+> Have you actually done the fs conversion or not?
+
+No.
+According to the usrMove page, it says that _some_ packages will not be installed due to not having converted it, and skipping them.
+In my case it's the other way around, most packages was not installed, and urpmi exited with an error, and gave a huge scroll history so large I couldn't scroll back farr enout to se if anything was installed at all.
+
+I haven't updated my cauldron in about two months or so. Mostly because of a few threads warning not to update because of new this and that which would reasult in crashing KDE or the like.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/dc08785f/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018136.html b/zarb-ml/mageia-dev/2012-August/018136.html new file mode 100644 index 000000000..8a873033c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018136.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Dimitrios Glentadakis + dglent at gmail.com +
+ Tue Aug 14 06:59:03 CEST 2012 +

+
+ +
Στις 13/08/2012 18:53:22 Balcaen John έγραψε:
+>Le lundi 13 août 2012 11:42:38 Dimitrios Glentadakis a écrit :
+>[...]
+>> 
+>> Another one kmail bug just has been fixed:
+>> https://bugs.kde.org/show_bug.cgi?id=304964
+>> this time very fast !
+>Fix added locally,
+>I'll check 4.9 tree to see if there's anything which can be easily backported.
+>And if you have some i'm open to suggestions of course ;o)
+>
+>
+>
+
+
+This one too has be fixed yesterday:
+https://bugs.kde.org/show_bug.cgi?id=301099
+
+
+-- 
+Dimitrios Glentadakis
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018137.html b/zarb-ml/mageia-dev/2012-August/018137.html new file mode 100644 index 000000000..497794550 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018137.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 14 07:20:54 CEST 2012 +

+
+ +
On 13 August 2012 17:49, nicolas vigier <boklm at mars-attacks.org> wrote:
+
+> > But people will not be notified of it.
+> > If a system is obsolete with the new distribution and known to break
+> > things/contain major security problems, I think having a place to put
+> > the obsoletes is good.
+> > But really I wouldn't expect more than 2 or 3 such packages in a release...
+>
+> Maybe we could change task-obsolete to conflict with obsolete packages
+> instead of obsoleting them :
+> - people who want to remove unsupported packages from their system
+>   install task-obsolete
+> - people who don't want to remove unsupported packages don't install
+>   task-obsolete
+>
+> This will also make urpmi/rpmdrake warn before removing packages,
+> instead of silently removing them.
+
+This would also be removing all obsoleted/unsupported packages
+or none of them....
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018138.html b/zarb-ml/mageia-dev/2012-August/018138.html new file mode 100644 index 000000000..d0ce50cb4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018138.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Aug 14 07:48:14 CEST 2012 +

+
+ +
* Thierry Vignaud (thierry.vignaud at gmail.com) wrote:
+> On 13 August 2012 17:49, nicolas vigier <boklm at mars-attacks.org> wrote:
+> 
+> > > But people will not be notified of it.
+> > > If a system is obsolete with the new distribution and known to break
+> > > things/contain major security problems, I think having a place to put
+> > > the obsoletes is good.
+> > > But really I wouldn't expect more than 2 or 3 such packages in a release...
+> >
+> > Maybe we could change task-obsolete to conflict with obsolete packages
+> > instead of obsoleting them :
+> > - people who want to remove unsupported packages from their system
+> >   install task-obsolete
+> > - people who don't want to remove unsupported packages don't install
+> >   task-obsolete
+> >
+> > This will also make urpmi/rpmdrake warn before removing packages,
+> > instead of silently removing them.
+> 
+> This would also be removing all obsoleted/unsupported packages
+> or none of them....
+
+It's already the case with Obsoletes.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120814/d1da4cf3/attachment.asc>
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018139.html b/zarb-ml/mageia-dev/2012-August/018139.html new file mode 100644 index 000000000..92361c107 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018139.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release gdb-7.4.91.20120801-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release gdb-7.4.91.20120801-1.mga3

+ Sander Lepik + sander.lepik at eesti.ee +
+ Tue Aug 14 08:17:31 CEST 2012 +

+
+ +
14.08.2012 01:43, tv kirjutas:
+> Name        : gdb                          Relocations: (not relocatable)
+> [...]
+>
+> tv <tv> 7.4.91.20120801-1.mga3:
+> + Revision: 281165
+> - new release
+> - sync patches with FC
+What is that FC? ;P Are you living in the past or is this something new 
+i don't know yet? :)
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018140.html b/zarb-ml/mageia-dev/2012-August/018140.html new file mode 100644 index 000000000..f5ba11c93 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018140.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release gdb-7.4.91.20120801-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release gdb-7.4.91.20120801-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 14 08:46:45 CEST 2012 +

+
+ +
On 14 August 2012 08:17, Sander Lepik <sander.lepik at eesti.ee> wrote:
+>> tv <tv> 7.4.91.20120801-1.mga3:
+>> + Revision: 281165
+>> - new release
+>> - sync patches with FC
+>
+> What is that FC? ;P Are you living in the past or is this something new i
+> don't know yet? :)
+
+FC=Fedora (Core)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018141.html b/zarb-ml/mageia-dev/2012-August/018141.html new file mode 100644 index 000000000..a2a0370a6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018141.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Olav Vitters + olav at vitters.nl +
+ Tue Aug 14 09:31:06 CEST 2012 +

+
+ +
On Mon, Aug 13, 2012 at 05:06:47PM +0200, Olivier Thauvin wrote:
+> But also the good question is why sshd is restarted when the glibc get
+> updated. This is no real reason and this can cause issue if locale need
+> an update too.
+
+Make sure UsePAM is set in sshd_config.
+
+IIRC during glibc upgrades the services are either restarted or
+reloaded. Without UsePAM, systemd will kill your existing session.
+
+
+-- 
+Regards,
+Olav
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018142.html b/zarb-ml/mageia-dev/2012-August/018142.html new file mode 100644 index 000000000..293dd8a61 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018142.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Tue Aug 14 10:06:18 CEST 2012 +

+
+ +
* Olav Vitters (olav at vitters.nl) wrote:
+> On Mon, Aug 13, 2012 at 05:06:47PM +0200, Olivier Thauvin wrote:
+> > But also the good question is why sshd is restarted when the glibc get
+> > updated. This is no real reason and this can cause issue if locale need
+> > an update too.
+> 
+> Make sure UsePAM is set in sshd_config.
+> 
+> IIRC during glibc upgrades the services are either restarted or
+> reloaded. Without UsePAM, systemd will kill your existing session.
+
+Either a change in Pam configuration or in sshd_config will need a
+restart, but for both of this it is too late as systemd is already
+in place and so any restart will kill all session.
+
+And the behavior I explained happend to me on a computer already having
+UsePam in sshd_config (to use ldap).
+
+Sshd has no reload facility, only a restart.
+
+I still think no RPM should trigger a restart on a not directly releated
+service, especially the glibc because any issue with this package can
+break your system (inlike the kernel there is no backup for the libc).
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 197 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120814/96992daa/attachment.asc>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018143.html b/zarb-ml/mageia-dev/2012-August/018143.html new file mode 100644 index 000000000..a74b1949a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018143.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] strange urpmi --auto-update with glibc + + + + + + + + + +

[Mageia-dev] strange urpmi --auto-update with glibc

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Tue Aug 14 10:41:40 CEST 2012 +

+
+ +
Le 14/08/2012 10:06, Olivier Thauvin a écrit :
+> * Olav Vitters (olav at vitters.nl) wrote:
+>> On Mon, Aug 13, 2012 at 05:06:47PM +0200, Olivier Thauvin wrote:
+>>> But also the good question is why sshd is restarted when the glibc get
+>>> updated. This is no real reason and this can cause issue if locale need
+>>> an update too.
+>>
+>> Make sure UsePAM is set in sshd_config.
+>>
+>> IIRC during glibc upgrades the services are either restarted or
+>> reloaded. Without UsePAM, systemd will kill your existing session.
+>
+> Either a change in Pam configuration or in sshd_config will need a
+> restart, but for both of this it is too late as systemd is already
+> in place and so any restart will kill all session.
+>
+> And the behavior I explained happend to me on a computer already having
+> UsePam in sshd_config (to use ldap).
+Which reminds me I wanted to fix the message in sshd_configuration file:
+https://www.mageia.org/pipermail/mageia-dev/2012-May/015683.html
+
+> Sshd has no reload facility, only a restart.
+The sshd daemon support SIGHUP, according to its manpage, so 'systemctl 
+reload sshd.service' should work.
+
+
+-- 
+BOFH excuse #39:
+
+terrorist activities
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018144.html b/zarb-ml/mageia-dev/2012-August/018144.html new file mode 100644 index 000000000..46a508e8b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018144.html @@ -0,0 +1,113 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 10:54:03 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 04:20 did gyre and gimble:
+> I haven't updated my cauldron in about two months or so. Mostly
+> because of a few threads warning not to update because of new this
+> and that which would reasult in crashing KDE or the like.
+
+There is a slight chicken and egg problem at the moment, but what you
+see here is expected. After you do the conversion you will likely get
+stuck with the more serious issue of not actually being able to update
+rpm to a version that understands the new check added to the filesystem
+package without also updating the filesystem package!
+
+Basically:
+
+ 1. install the latest dracut
+ 2. install the latest kernel
+ 3. reboot and make sure all is well.
+ 4. regenerate initrd as per instructions
+ 5. reboot with kernel command line params and convert the fs
+ 6. try an install the new rpm package. It will likely fail due to
+trying to also pull in the new filesystem package as part of the same
+transaction.
+ 7. If it fails, double check that the files /bin /sbin /lib /lib64
+/var/run /var/lock are all symlinks and then manually install filesystem
+package with --allow-nodeps
+
+The rest of the upgrade should go smoothly from there.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018145.html b/zarb-ml/mageia-dev/2012-August/018145.html new file mode 100644 index 000000000..807cf5a4c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018145.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 10:57:43 CEST 2012 +

+
+ +
'Twas brillig, and nicolas vigier at 13/08/12 16:49 did gyre and gimble:
+> Maybe we could change task-obsolete to conflict with obsolete packages
+> instead of obsoleting them :
+
+task-obsolete is also used to remove packages from the mirror too. So if
+we change how it works, then we have to find another user friendly
+mechanism to remove packages (not necessarily a bad idea tho')
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018146.html b/zarb-ml/mageia-dev/2012-August/018146.html new file mode 100644 index 000000000..c7a3d499d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018146.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 11:01:52 CEST 2012 +

+
+ +
'Twas brillig, and Anne Wilson at 13/08/12 18:06 did gyre and gimble:
+> On 13/08/12 11:04, Olav Vitters wrote:
+>> On Mon, Aug 13, 2012 at 09:39:07AM +0100, Anne Wilson wrote:
+>>> Why would anyone need root login over ssh?  I don't allow it on
+>>> my server and it has never caused me any problems.  Su to root
+>>> works perfectly well and avoids the security risk, so I don't
+>>> understand this thread.
+> 
+>> Remote backups. Quite easy to setup an SSH key which only runs
+>> rsync.
+> 
+> I use rsync on the server for local backups, and I use SSH with keys
+> to access the server from laptops for maintenance tasks, but I have
+> never managed to make rsync over ssh with keys work.  People tell me
+> to just use ssh without keys, but I'm reluctant to do that.  Maybe one
+> day I'll find something that steps me through it, so that I can find
+> the missing link.
+
+In this case if you want a special key that can *only* run rsync you
+need to configure your authorized_keys correctly with appropriate
+command= definition.
+
+But even without specific setup if you can ssh between hosts happily,
+just do "rsync -e ssh"  on the client side and just use
+foo at remote:/path/to/files syntax. Job done :)
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018147.html b/zarb-ml/mageia-dev/2012-August/018147.html new file mode 100644 index 000000000..d31cda3f2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018147.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 11:02:18 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 10:54, Colin Guthrie wrote:
+> There is a slight chicken and egg problem at the moment, but what you
+> see here is expected.
+
+Then the instructions should be more clear on the fact that it is possible that most, if not all packages will fail to install, and not just -some- packages as it's written now.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/3e00b4ff/attachment.asc>
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018148.html b/zarb-ml/mageia-dev/2012-August/018148.html new file mode 100644 index 000000000..b66d261f9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018148.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Tue Aug 14 11:05:41 CEST 2012 +

+
+ +
Le 14/08/2012 10:57, Colin Guthrie a écrit :
+> 'Twas brillig, and nicolas vigier at 13/08/12 16:49 did gyre and gimble:
+>> Maybe we could change task-obsolete to conflict with obsolete packages
+>> instead of obsoleting them :
+>
+> task-obsolete is also used to remove packages from the mirror too.
+s/task-obsolete/obsoletes tags in any package/
+
+> So if
+> we change how it works, then we have to find another user friendly
+> mechanism to remove packages (not necessarily a bad idea tho')
+Is asking an admin on IRC or a mailing-list user-friendy enough ? Or a 
+wrapper accessible by ssh (as other similar admin tools on BS) taking 
+care both of subversion removal and package tree cleanup ?
+
+-- 
+BOFH excuse #242:
+
+Software uses US measurements, but the OS is in metric...
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018149.html b/zarb-ml/mageia-dev/2012-August/018149.html new file mode 100644 index 000000000..fae0180b2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018149.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 11:07:09 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 10:02 did gyre and gimble:
+> On Tuesday 14 August 2012 10:54, Colin Guthrie wrote:
+>> There is a slight chicken and egg problem at the moment, but what
+>> you see here is expected.
+> 
+> Then the instructions should be more clear on the fact that it is
+> possible that most, if not all packages will fail to install, and not
+> just -some- packages as it's written now.
+
+Sorry. It *was* some at the time, I guess now that's grown. However, I'd
+rather retarget those instructions now for upgrades anyway, rather than
+cauldron users as there can't be too many stragglers left now (or at
+least not ones who cannot read a mailing list and see solutions to their
+problems).
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018150.html b/zarb-ml/mageia-dev/2012-August/018150.html new file mode 100644 index 000000000..59b8b0ca3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018150.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 11:09:41 CEST 2012 +

+
+ +
'Twas brillig, and Guillaume Rousse at 14/08/12 10:05 did gyre and gimble:
+> Le 14/08/2012 10:57, Colin Guthrie a écrit :
+>> 'Twas brillig, and nicolas vigier at 13/08/12 16:49 did gyre and gimble:
+>>> Maybe we could change task-obsolete to conflict with obsolete packages
+>>> instead of obsoleting them :
+>>
+>> task-obsolete is also used to remove packages from the mirror too.
+> s/task-obsolete/obsoletes tags in any package/
+> 
+>> So if
+>> we change how it works, then we have to find another user friendly
+>> mechanism to remove packages (not necessarily a bad idea tho')
+
+> Is asking an admin on IRC or a mailing-list user-friendy enough ? 
+
+Well in the past such requests can go unheeded for a while as happens
+from time to time.
+
+>Or a
+> wrapper accessible by ssh (as other similar admin tools on BS) taking
+> care both of subversion removal and package tree cleanup ?
+
+That would be much better, but made available to packagers easily to
+prevent unnecessary sysadmin overhead.
+
+Col
+
+
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018151.html b/zarb-ml/mageia-dev/2012-August/018151.html new file mode 100644 index 000000000..5f40ae774 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018151.html @@ -0,0 +1,70 @@ + + + + [Mageia-dev] Task-obsolete and non-sense obsoletes + + + + + + + + + +

[Mageia-dev] Task-obsolete and non-sense obsoletes

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Tue Aug 14 11:16:58 CEST 2012 +

+
+ +
Le 14/08/2012 11:09, Colin Guthrie a écrit :
+>> Or a
+>> wrapper accessible by ssh (as other similar admin tools on BS) taking
+>> care both of subversion removal and package tree cleanup ?
+>
+> That would be much better, but made available to packagers easily to
+> prevent unnecessary sysadmin overhead.
+As all other helper commands defined in /etc/mgarepo.conf: 
+/usr/local/bin/submit_package, /usr/local/bin/wrapper.upload-bin, etc...
+
+
+-- 
+BOFH excuse #139:
+
+UBNC (user brain not connected)
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018152.html b/zarb-ml/mageia-dev/2012-August/018152.html new file mode 100644 index 000000000..53744c55e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018152.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 11:21:58 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 10:54, Colin Guthrie wrote:
+> 3. reboot and make sure all is well.
+
+And now I can't even do that. ;-)=
+
+It halts on automatic fsck failure, and prompts me to run fsck manually. However fsck is NOT available. Almost No tools of any kind is available to use. I can't even access the fstab to figure out which device I need to fsck, hence I CANNOT check the filesystem.
+
+Any ideas?
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/d1041bba/attachment-0001.asc>
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018153.html b/zarb-ml/mageia-dev/2012-August/018153.html new file mode 100644 index 000000000..eb1206f67 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018153.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 11:34:48 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 10:21 did gyre and gimble:
+> On Tuesday 14 August 2012 10:54, Colin Guthrie wrote:
+>> 3. reboot and make sure all is well.
+> 
+> And now I can't even do that. ;-)=
+> 
+> It halts on automatic fsck failure, and prompts me to run fsck
+> manually. However fsck is NOT available. Almost No tools of any kind
+> is available to use. I can't even access the fstab to figure out
+> which device I need to fsck, hence I CANNOT check the filesystem.
+> 
+> Any ideas?
+
+So I guess you're in the initrd? What kind of filesystem are you
+running? I happily have e2fsck in my initrd.
+
+Reboot with an older kernel and make sure that's still OK first then try
+and investigate why dracut will not generate a working initrd for you.
+
+I deliberately held back on updating dracut until after the usrmove as I
+wanted to use the same version as on mga2. Since the usrmove is quite
+far behind us now, dracut has been upgraded. I called for tests a while
+back but received no negative feedback so now it's out to the masses.
+I'd investigate exactly what's causing the broken initrd first and
+foremost. e.g. by looking at what it says when it's generating etc.
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018154.html b/zarb-ml/mageia-dev/2012-August/018154.html new file mode 100644 index 000000000..805b4224c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018154.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun! + + + + + + + + + +

[Mageia-dev] Fwd: [Bugsquad] KDE BugDays for Kmail on 18/19 and 25/26 August - please join the fun!

+ Balcaen John + mikala at mageia.org +
+ Tue Aug 14 11:46:29 CEST 2012 +

+
+ +
Le mardi 14 août 2012 06:59:03 Dimitrios Glentadakis a écrit :
+> Στις 13/08/2012 18:53:22 Balcaen John έγραψε:
+> >Le lundi 13 août 2012 11:42:38 Dimitrios Glentadakis a écrit :
+> >[...]
+> >
+> >> Another one kmail bug just has been fixed:
+> >> https://bugs.kde.org/show_bug.cgi?id=304964
+> >> this time very fast !
+> >
+> >Fix added locally,
+> >I'll check 4.9 tree to see if there's anything which can be easily
+> >backported. And if you have some i'm open to suggestions of course ;o)
+> 
+> This one too has be fixed yesterday:
+> https://bugs.kde.org/show_bug.cgi?id=301099
+It was already added when i sent this mail :p
+Ok so i'll push a new package & you can confirm that thoses 2 bugs are fixed for 
+you.
+
+-- 
+Balcaen John
+
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018155.html b/zarb-ml/mageia-dev/2012-August/018155.html new file mode 100644 index 000000000..156b77a06 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018155.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 11:50:31 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 10:54, Colin Guthrie wrote:
+> 5. reboot with kernel command line params and convert the fs
+
+Once I figured out the use of e2fsck, it boots, but it does Not convert the filesystem. If it doesit is invisible to me.
+All the usual root folders (bin, sbin, lib, lib64 etc) are still there. No new symlinks of any kind. Nothing.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/29794361/attachment.asc>
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018156.html b/zarb-ml/mageia-dev/2012-August/018156.html new file mode 100644 index 000000000..9bcef7ddf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018156.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 12:13:48 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 11:34, Colin Guthrie wrote:
+> I happily have e2fsck in my initrd.
+
+Which was not my whole point. The average user is trained to use fsck to check filesystems when this prompt comes along. Almost every guide out there directed to the normal user describes running fsck, not e2fsck. It is even written in the prompt text that one should run fsck, not e2fsck. Either the text in the prompt should be changed or fsck should be included in the initrd/dracut.
+I even instruct people to use the TABulator to auto complete paths and filenames, to reduce the risk of typos in commands. This doesn't work in the initrd prompt, either. 
+This should be fixed.
+
+In my 12 years of using Linux, this is the first time I've had to use it. It is the first time ever that the various fsck.* tools were Not available. It is also the first time the up-arrow did not work in command line. So any typo in commands resulted in having to manually retype the entire command. Which is a royal pain in the Ass when fscking multiple filesystems. No, really.
+
+Another problem with this new setup is that local helper scripts to check filesystems is not available. My brother had Mandriva for about a year. He even thinks Windows is dificult. So I made a shellscript for him to run the next time he saw the fsck prompt, which would run "/sbin/fsck.ext3 -y /dev/sdxx" on all partitions. This no longer works in the current setup, forcing every user to manually running a complicated command in the shell, with options they have never heard of.
+I do not believe I'm alone in having to making this kind of local helper scripts for users who have no intentions of learning to use the command line.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/126da080/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018157.html b/zarb-ml/mageia-dev/2012-August/018157.html new file mode 100644 index 000000000..653c26c7b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018157.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Remco Rijnders + remco at webconquest.com +
+ Tue Aug 14 12:42:16 CEST 2012 +

+
+ +
On Tue, Aug 14, 2012 at 11:13:48AM +0100, Johnny wrote in 
+<201208141213.52280.cooker at solbu.net>:
+>On Tuesday 14 August 2012 11:34, Colin Guthrie wrote:
+>> I happily have e2fsck in my initrd.
+>
+>Which was not my whole point. The average user is trained to use fsck to check filesystems when this prompt comes along. Almost every guide out there directed to the normal user describes running fsck, not e2fsck. It is even written in the prompt text that one should run fsck, not e2fsck. Either the text in the prompt should be changed or fsck should be included in the initrd/dracut.
+>I even instruct people to use the TABulator to auto complete paths and filenames, to reduce the risk of typos in commands. This doesn't work in the initrd prompt, either.
+>This should be fixed.
+>
+>In my 12 years of using Linux, this is the first time I've had to use it. It is the first time ever that the various fsck.* tools were Not available. It is also the first time the up-arrow did not work in command line. So any typo in commands resulted in having to manually retype the entire command. Which is a royal pain in the Ass when fscking multiple filesystems. No, really.
+>
+>Another problem with this new setup is that local helper scripts to check filesystems is not available. My brother had Mandriva for about a year. He even thinks Windows is dificult. So I made a shellscript for him to run the next time he saw the fsck prompt, which would run "/sbin/fsck.ext3 -y /dev/sdxx" on all partitions. This no longer works in the current setup, forcing every user to manually running a complicated command in the shell, with options they have never heard of.
+>I do not believe I'm alone in having to making this kind of local helper scripts for users who have no intentions of learning to use the command line.
+
+Ok... valid as these points may or may not be... I think this no longer 
+has to do with the /usr move procedure? A normal user will not be required 
+to update their systems the way we (devs and other interested Cauldron 
+users) will have to do this for now using a number of detailed steps.
+
+If the system prompts one to use tools not available, then that's a 
+seperate issue that should be addressed (probably not by Colin).
+
+Back on track: 1) Do ensure that when you run the dracut command that an 
+image is generated for your current kernel (uname -a) and that you don't 
+boot into another kernel. 2) Don't forget to edit the boot options on the 
+first boot after doing the above.
+
+Remmy
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 836 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120814/21857068/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018158.html b/zarb-ml/mageia-dev/2012-August/018158.html new file mode 100644 index 000000000..ef540b976 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018158.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 13:10:24 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 12:42, Remco Rijnders wrote:
+> 1) Do ensure that when you run the dracut command that an 
+> image is generated for your current kernel (uname -a) and that you don't 
+> boot into another kernel. 
+
+> 2) Don't forget to edit the boot options on the  
+> first boot after doing the above.
+
+I've done both steps twice now. It still don't convert the filesystem.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/26230d1f/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018159.html b/zarb-ml/mageia-dev/2012-August/018159.html new file mode 100644 index 000000000..980e795a7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018159.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 13:39:34 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 10:50 did gyre and gimble:
+> On Tuesday 14 August 2012 10:54, Colin Guthrie wrote:
+>> 5. reboot with kernel command line params and convert the fs
+> 
+> Once I figured out the use of e2fsck, it boots, but it does Not convert the filesystem. If it doesit is invisible to me.
+> All the usual root folders (bin, sbin, lib, lib64 etc) are still there. No new symlinks of any kind. Nothing.
+
+OK then some questions:
+ 1. Did you definitely regenerate the initrd and include the convertfs
+module?
+ 2. Did you definitely add the correct kernel command line options to
+mount / rw and trigger conversion process?
+
+If both the above are true, then, as per the instructions, try passing
+rd.break=pre-pivot to the command line and remove the "splash" option.
+
+When booting. You will be dropped to a debug shell *before* conversion.
+Just type "exit" and it should do the conversion and dump you to another
+shell.
+
+If things are failing you should see that there and it should roll back.
+
+A typical problem would be mounting /usr readonly if it's on a separate
+partition but the instructions are clear on that one too.
+
+Hope this helps.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018160.html b/zarb-ml/mageia-dev/2012-August/018160.html new file mode 100644 index 000000000..ae0286cb9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018160.html @@ -0,0 +1,137 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 13:49:35 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 11:13 did gyre and gimble:
+> On Tuesday 14 August 2012 11:34, Colin Guthrie wrote:
+>> I happily have e2fsck in my initrd.
+> 
+> Which was not my whole point. The average user is trained to use fsck
+> to check filesystems when this prompt comes along. Almost every guide
+> out there directed to the normal user describes running fsck, not
+> e2fsck. It is even written in the prompt text that one should run
+> fsck, not e2fsck. Either the text in the prompt should be changed or
+> fsck should be included in the initrd/dracut. I even instruct people
+> to use the TABulator to auto complete paths and filenames, to reduce
+> the risk of typos in commands. This doesn't work in the initrd
+> prompt, either. This should be fixed.
+
+Probably something worth reporting upstream to dracut maintainers then.
+I'll do this next time I speak to Harald, but if you would like to fix
+it it's probably quite trivial.
+
+> In my 12 years of using Linux, this is the first time I've had to use
+> it. It is the first time ever that the various fsck.* tools were Not
+> available. It is also the first time the up-arrow did not work in
+> command line. So any typo in commands resulted in having to manually
+> retype the entire command. Which is a royal pain in the Ass when
+> fscking multiple filesystems. No, really.
+
+You've maybe not played with very many very minimal systems as I've come
+across this kind of thing quire frequently. Having played about in
+dracut shells rather a lot of late I have to admit it's a total pain.
+
+I'll see what can be done to make this a bit more friendly.
+
+> Another problem with this new setup is that local helper scripts to
+> check filesystems is not available. My brother had Mandriva for about
+> a year. He even thinks Windows is dificult. So I made a shellscript
+> for him to run the next time he saw the fsck prompt, which would run
+> "/sbin/fsck.ext3 -y /dev/sdxx" on all partitions. This no longer
+> works in the current setup, forcing every user to manually running a
+> complicated command in the shell, with options they have never heard
+> of. I do not believe I'm alone in having to making this kind of local
+> helper scripts for users who have no intentions of learning to use
+> the command line.
+
+If such helper scripts exist and are useful, we can easily add them to a
+dracut.conf.d snippet. These config snippets can be included in the
+packages that provide these helpers rather than in dracut itself to
+allow for proper separation of need (although the complex dependancies
+may mean that we do not want to include e.g. the xfs helper (which may
+or may not pull in a lot of other tools) if you do not have any xfs
+filesystems - in which case it has to be patched into the various dracut
+modules instead of done generically.
+
+
+That said, as with your other point above, anything added to the initrd
+will make it bigger and thus delay the boot. So you have to strike a
+happy balance with having enough to be useful in a (rare) emergency case
+and small enough to be spritely during the (more frequent rebooting
+process).
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018161.html b/zarb-ml/mageia-dev/2012-August/018161.html new file mode 100644 index 000000000..67f980cb7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018161.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 14:09:06 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 13:39, Colin Guthrie wrote:
+> OK then some questions:
+>  1. Did you definitely regenerate the initrd and include the convertfs
+> module?
+
+Yes: dracut -f -a convertfs
+
+>  2. Did you definitely add the correct kernel command line options to
+> mount / rw and trigger conversion process?
+
+Yes - added "rw rd.convertfs" and pressed "enter" and "b" to boot.
+
+> If both the above are true, then, as per the instructions, try passing
+> rd.break=pre-pivot to the command line 
+
+> remove the "splash" option. 
+
+Unless it is not my own system, splash is the first thing I remove after installing, before customizing anything.
+
+> When booting. You will be dropped to a debug shell *before* conversion.
+> Just type "exit" and it should do the conversion and dump you to another
+> shell.
+
+Which did nothing. :-/=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/06e5f9b6/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018162.html b/zarb-ml/mageia-dev/2012-August/018162.html new file mode 100644 index 000000000..8606accc6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018162.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 14:13:43 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 14:09, Johnny A. Solbu wrote:
+> > When booting. You will be dropped to a debug shell *before* conversion.
+> > Just type "exit" and it should do the conversion and dump you to another
+> > shell.
+> 
+> Which did nothing. :-/=
+
+To be more specific: I got the two debug shells, and no conversion was done, not that I could see anyway.
+I pressed CTRL+D on teh first shell, and some 4-6 lines of messages apeared, and in less that half a second i got the next prompt. upon exiting that, it booted normaly.
+
+All 4 folders which should be converted to symlinks (if I understand correctly) are still there. No symlinks.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/71b36ef3/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018163.html b/zarb-ml/mageia-dev/2012-August/018163.html new file mode 100644 index 000000000..cc6903292 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018163.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Charles A Edwards + CAE at eslrahc.com +
+ Tue Aug 14 14:47:12 CEST 2012 +

+
+ +
On Tue, 14 Aug 2012 13:13:43 +0100
+Johnny A. Solbu wrote:
+
+> To be more specific: I got the two debug shells, and no conversion
+> was done, not that I could see anyway. I pressed CTRL+D on teh first
+> shell, and some 4-6 lines of messages apeared, and in less that half
+> a second i got the next prompt. upon exiting that, it booted normaly.
+> 
+> All 4 folders which should be converted to symlinks (if I understand
+> correctly) are still there. No symlinks.
+
+This sounds like what was happening to me when I did the conversion.
+
+Are you booting with lilo or grub?
+
+I was using lilo and you Have to execute 'lilo/lilo -v' after you
+have created the new initrd for it to be mapped/used correctly.
+
+
+    Charles
+
+-- 
+Whistler's Law:
+	You never know who is right, but you always know who is in
+charge. ----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.1-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120814/dbf6e65a/attachment-0001.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018164.html b/zarb-ml/mageia-dev/2012-August/018164.html new file mode 100644 index 000000000..716649770 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018164.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 14:57:16 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 14:47, Charles A Edwards wrote:
+> Are you booting with lilo or grub?
+
+Grub.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/a9068905/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018165.html b/zarb-ml/mageia-dev/2012-August/018165.html new file mode 100644 index 000000000..708f01da9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018165.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 15:14:04 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 13:57 did gyre and gimble:
+> On Tuesday 14 August 2012 14:47, Charles A Edwards wrote:
+>> Are you booting with lilo or grub?
+> 
+> Grub.
+
+All very strange.
+
+It looks like there is simply no conversion script in the initrd.
+
+Can I ask what version of dracut you are using? It should be 023 now but
+perhaps it could not be installed for some reason? I've not tested the
+conversion with dracut 023, but AFAICS there are no real changes to the
+script itself.
+
+Also after booting, does "lsinitrd | grep convert" confirm that you do
+indeed have the convert script in the initrd?
+
+I guarantee the cause will be a weird little trivial thing, but it'll be
+one of those annoying ones that take a while to show themselves!! I hate
+those bugs :p
+
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018166.html b/zarb-ml/mageia-dev/2012-August/018166.html new file mode 100644 index 000000000..509bd360f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018166.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 15:58:03 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 15:14, Colin Guthrie wrote:
+> Can I ask what version of dracut you are using? It should be 023 now but
+> perhaps it could not be installed for some reason? I've not tested the
+> conversion with dracut 023, but AFAICS there are no real changes to the
+> script itself.
+> 
+> Also after booting, does "lsinitrd | grep convert" confirm that you do
+> indeed have the convert script in the initrd?
+
+(17:50:05) [solbu at cauldron ~]$ rpm -qa dracut
+dracut-023-2.mga3
+(17:50:14) [solbu at cauldron ~]$ lsinitrd |grep convert
+-rwxr-xr-x   1 root     root          304 Aug 14 15:06 lib/dracut/hooks/pre-pivot/99-do-convertfs.sh
+-rwxr-xr-x   1 root     root         8031 Aug 14 15:06 usr/bin/convertfs
+
+
+> I guarantee the cause will be a weird little trivial thing, but it'll be
+> one of those annoying ones that take a while to show themselves!! I hate
+> those bugs :p
+
+In Norway there is a saying which goes something like this; 
+	a small tuft of grass can bring down a big load. ;-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/edae5e91/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018167.html b/zarb-ml/mageia-dev/2012-August/018167.html new file mode 100644 index 000000000..864c1401f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018167.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Anne Wilson + annew at kde.org +
+ Tue Aug 14 16:56:33 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 14/08/12 10:01, Colin Guthrie wrote:
+> 'Twas brillig, and Anne Wilson at 13/08/12 18:06 did gyre and
+> gimble:
+>> On 13/08/12 11:04, Olav Vitters wrote:
+>>> On Mon, Aug 13, 2012 at 09:39:07AM +0100, Anne Wilson wrote:
+>>>> Why would anyone need root login over ssh?  I don't allow it
+>>>> on my server and it has never caused me any problems.  Su to
+>>>> root works perfectly well and avoids the security risk, so I
+>>>> don't understand this thread.
+>> 
+>>> Remote backups. Quite easy to setup an SSH key which only runs 
+>>> rsync.
+>> 
+>> I use rsync on the server for local backups, and I use SSH with
+>> keys to access the server from laptops for maintenance tasks, but
+>> I have never managed to make rsync over ssh with keys work.
+>> People tell me to just use ssh without keys, but I'm reluctant to
+>> do that.  Maybe one day I'll find something that steps me through
+>> it, so that I can find the missing link.
+> 
+> In this case if you want a special key that can *only* run rsync
+> you need to configure your authorized_keys correctly with
+> appropriate command= definition.
+> 
+> But even without specific setup if you can ssh between hosts
+> happily, just do "rsync -e ssh"  on the client side and just use 
+> foo at remote:/path/to/files syntax. Job done :)
+> 
+Sure, but knowing how prone we all are to forget, my intention was to
+do it by cron :-)  As I said, I can manually do anything I need to,
+but I want scheduled checks for changed files.  Annoyingly, I have to
+say that the only part I have working for that is the Windows 7 backup
+of my embroidery project files.  When I'm working there, changes are
+backed up four times a day.
+
+I'm guessing that Windows is using my local mount of the appropriate
+drive on the server, and I tried doing that in Linux, thinking it
+would solve it, but no matter what I do, I still get "denied".  It has
+to be something about the way the keys are passed to the server when
+using cron, as I can use the local mount to move things around in
+Dolphin with no problems whatsoever.  If I ssh from konsole it is
+clear that my keys are being passed.  I don't think cron is doing that.
+
+Anne
+- -- 
+Need KDE help? Try
+http://userbase.kde.org or
+http://forum.kde.org
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iEYEARECAAYFAlAqZx8ACgkQj93fyh4cnBdnowCgillA7xTkrC2YvQg5Et1gxT2k
+wNMAn0a8hRmIkOWYd+iBJ75X6Xn1BgWN
+=K4Z6
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018168.html b/zarb-ml/mageia-dev/2012-August/018168.html new file mode 100644 index 000000000..a8d1b637b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018168.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 17:10:43 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 14:58 did gyre and gimble:
+> On Tuesday 14 August 2012 15:14, Colin Guthrie wrote:
+>> Can I ask what version of dracut you are using? It should be 023 now but
+>> perhaps it could not be installed for some reason? I've not tested the
+>> conversion with dracut 023, but AFAICS there are no real changes to the
+>> script itself.
+>>
+>> Also after booting, does "lsinitrd | grep convert" confirm that you do
+>> indeed have the convert script in the initrd?
+> 
+> (17:50:05) [solbu at cauldron ~]$ rpm -qa dracut
+> dracut-023-2.mga3
+> (17:50:14) [solbu at cauldron ~]$ lsinitrd |grep convert
+> -rwxr-xr-x   1 root     root          304 Aug 14 15:06 lib/dracut/hooks/pre-pivot/99-do-convertfs.sh
+> -rwxr-xr-x   1 root     root         8031 Aug 14 15:06 usr/bin/convertfs
+
+OK, colour me confused... :s
+
+Everything looks in place. The kernel modules, the initrd, the kernel
+command line. It just doesn't seem to actually happen :s
+
+I'll fire up an old VM tonight to test this and see if I can reproduce.
+I may have to come back to you if I cannot get it done.
+
+It should be quite safe to run "convertfs /sysroot" after the first exit
+(with rd.break=pre-pivot) but I *really* want to figure out why it's
+just not working.
+
+Just so I can pick the right VM, what's your disk layout? ext3/4? /usr
+on a separate partition or not?
+
+(/me is now wondering if the "rw" command line option is enough to mount
+/ rw... perhaps that's what changed - even still you should have gotten
+an error message about it after the first exit with rd.break...)
+
+
+>> I guarantee the cause will be a weird little trivial thing, but it'll be
+>> one of those annoying ones that take a while to show themselves!! I hate
+>> those bugs :p
+> 
+> In Norway there is a saying which goes something like this; 
+> 	a small tuft of grass can bring down a big load. ;-)=
+> 
+
+:)
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018169.html b/zarb-ml/mageia-dev/2012-August/018169.html new file mode 100644 index 000000000..f063b6b13 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018169.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 17:40:06 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 17:10, Colin Guthrie wrote:
+> Just so I can pick the right VM, what's your disk layout? ext3/4? 
+
+
+df -T|grep -v fs
+Filesystem     Type      Size  Used Avail Use% Mounted on
+/dev/sda1      ext4       12G  6,4G  4,9G  57% /
+/dev/sda6      ext4      9,5G  8,7G  769M  93% /home
+
+> /usr on a separate partition or not?
+
+Only on real systems. I don't bother with separate /usr on virtual machines, such as Cauldron and Cooker.
+
+> (/me is now wondering if the "rw" command line option is enough to mount
+> / rw... perhaps that's what changed - even still you should have gotten
+> an error message about it after the first exit with rd.break...)
+
+I tried it again, to se what errors show up. They just might tell you more than they tell me. ;-)=
+(Typed in here manually, beware of typos)
+===
+pre-pivot:/# (Pressing CTRL+D)
+[   91.3330211} dracut: /bin/bash: error while loading shared libraries: libtermcap.so.2
+pre-pivot
+
+[   91.3330211] dracut Warning: Break before switch_root
+dracut Warning: Break before switch_root
+
+Dropping to debug shell.
+
+/bin/sh: 0: can't access tty; job control turned off
+switch_root:/#
+===
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/db81da85/attachment.asc>
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018170.html b/zarb-ml/mageia-dev/2012-August/018170.html new file mode 100644 index 000000000..6a7eaa55f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018170.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 18:20:21 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 16:40 did gyre and gimble:
+> On Tuesday 14 August 2012 17:10, Colin Guthrie wrote:
+>> Just so I can pick the right VM, what's your disk layout? ext3/4? 
+> 
+> 
+> df -T|grep -v fs
+> Filesystem     Type      Size  Used Avail Use% Mounted on
+> /dev/sda1      ext4       12G  6,4G  4,9G  57% /
+> /dev/sda6      ext4      9,5G  8,7G  769M  93% /home
+> 
+>> /usr on a separate partition or not?
+> 
+> Only on real systems. I don't bother with separate /usr on virtual machines, such as Cauldron and Cooker.
+> 
+>> (/me is now wondering if the "rw" command line option is enough to mount
+>> / rw... perhaps that's what changed - even still you should have gotten
+>> an error message about it after the first exit with rd.break...)
+> 
+> I tried it again, to se what errors show up. They just might tell you more than they tell me. ;-)=
+> (Typed in here manually, beware of typos)
+> ===
+> pre-pivot:/# (Pressing CTRL+D)
+> [   91.3330211} dracut: /bin/bash: error while loading shared libraries: libtermcap.so.2
+> pre-pivot
+
+Oh that *is* interesting.
+
+What is in your initrd regarding termcap stuff?
+
+lsinitrd | grep -E "bash|termcap"
+
+Mine looks OK here, but perhaps with the several packages being updated
+from earlier it might not go as smoothly in this regards it once did...
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018171.html b/zarb-ml/mageia-dev/2012-August/018171.html new file mode 100644 index 000000000..5f56f8e6d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018171.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 18:28:50 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 18:20, Colin Guthrie wrote:
+> What is in your initrd regarding termcap stuff?
+> 
+> lsinitrd | grep -E "bash|termcap"
+
+lsinitrd | grep -E "bash|termcap"
+-rwxr-xr-x   1 root     root       786328 Aug 14 15:06 bin/bash
+
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/2d6ec56d/attachment-0001.asc>
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018172.html b/zarb-ml/mageia-dev/2012-August/018172.html new file mode 100644 index 000000000..0a71cb4e0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018172.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 19:30:17 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 17:28 did gyre and gimble:
+> On Tuesday 14 August 2012 18:20, Colin Guthrie wrote:
+>> What is in your initrd regarding termcap stuff?
+>>
+>> lsinitrd | grep -E "bash|termcap"
+> 
+> lsinitrd | grep -E "bash|termcap"
+> -rwxr-xr-x   1 root     root       786328 Aug 14 15:06 bin/bash
+
+OK, so the basic problem is that for whatever reason, when dracut
+created the initrd, it was unable to find all the deps (i.e. libs) for
+the bash binary.
+
+This is IMO a regression in latest dracut. I'll dig into why it's doing
+it but I suspect strongly it's related to a "lazy" depsolving mode, that
+doesn't work well in this case for some reason.
+
+Now that I know what's wrong you can probably generate a valid initrd
+simply by doing:
+
+ mv /usr/lib/dracut/dracut-install /usr/lib/dracut/dracut-install.x
+
+Before generating the initrd and then moving it back when done. Verify
+with lsinitrd as before.
+
+However, if you can wait, I'll try and suss out the problem and issue an
+updated dracut package.
+
+Cheers
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018173.html b/zarb-ml/mageia-dev/2012-August/018173.html new file mode 100644 index 000000000..5a193eac4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018173.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Tue Aug 14 19:32:52 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 19:30, Colin Guthrie wrote:
+> if you can wait, I'll try and suss out the problem and issue an
+> updated dracut package.
+
+I can wait.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/d8349c7d/attachment.asc>
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018174.html b/zarb-ml/mageia-dev/2012-August/018174.html new file mode 100644 index 000000000..0d4876c30 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018174.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 19:45:14 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 18:32 did gyre and gimble:
+> On Tuesday 14 August 2012 19:30, Colin Guthrie wrote:
+>> if you can wait, I'll try and suss out the problem and issue an
+>> updated dracut package.
+> 
+> I can wait.
+
+Actually, just in case I cannot reproduce, you can try the following:
+
+1. cd
+2. mkdir foo
+3. /usr/lib/dracut/dracut-install -D $HOME/foo bash
+
+This should just copy the bash binary to the foo tree. Nothing more.
+
+4. find $HOME/foo -type f '(' -perm -0100 -or -perm -0010 -or -perm
+-0001 ')' -print0 | xargs -r -0 /usr/lib/dracut/dracut-install --debug
+-D $HOME/foo -R
+
+
+This should install all the needed libs for bash.
+
+The output from step 4 and and "ls -lR $HOME/foo" at the end would be
+interesting I think.
+
+I will still try and set this up at home when I get back from work tho'.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018175.html b/zarb-ml/mageia-dev/2012-August/018175.html new file mode 100644 index 000000000..fc1cd820f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018175.html @@ -0,0 +1,113 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 21:18:16 CEST 2012 +

+
+ +
'Twas brillig, and Colin Guthrie at 14/08/12 18:45 did gyre and gimble:
+> 'Twas brillig, and Johnny A. Solbu at 14/08/12 18:32 did gyre and gimble:
+>> On Tuesday 14 August 2012 19:30, Colin Guthrie wrote:
+>>> if you can wait, I'll try and suss out the problem and issue an
+>>> updated dracut package.
+>>
+>> I can wait.
+> 
+> Actually, just in case I cannot reproduce, you can try the following:
+> 
+> 1. cd
+> 2. mkdir foo
+> 3. /usr/lib/dracut/dracut-install -D $HOME/foo bash
+> 
+> This should just copy the bash binary to the foo tree. Nothing more.
+> 
+> 4. find $HOME/foo -type f '(' -perm -0100 -or -perm -0010 -or -perm
+> -0001 ')' -print0 | xargs -r -0 /usr/lib/dracut/dracut-install --debug
+> -D $HOME/foo -R
+> 
+> 
+> This should install all the needed libs for bash.
+> 
+> The output from step 4 and and "ls -lR $HOME/foo" at the end would be
+> interesting I think.
+> 
+> I will still try and set this up at home when I get back from work tho'.
+
+OK, I can reproduce the problem now in a VM. That said, the above stuff
+works fine... so go figure :s
+
+I'll puzzle it out.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018176.html b/zarb-ml/mageia-dev/2012-August/018176.html new file mode 100644 index 000000000..c0bab49dd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018176.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] SSH PAM configuration + + + + + + + + + +

[Mageia-dev] SSH PAM configuration

+ Renaud MICHEL + r.h.michel+mageia at gmail.com +
+ Tue Aug 14 23:12:52 CEST 2012 +

+
+ +
Hello
+On Tuesday 14 August 2012 at 16:56:33, Anne Wilson wrote :
+> > But even without specific setup if you can ssh between hosts
+> > happily, just do "rsync -e ssh"  on the client side and just use
+> > foo at remote:/path/to/files syntax. Job done :)
+> 
+> Sure, but knowing how prone we all are to forget, my intention was to
+> do it by cron :-)
+
+If you want to run rsync over ssh from cron, I know two possible solutions.
+
+The first is to have a passwordless key (not readable by anyone else), then 
+you simply need to use that key when connecting. That is done with the -i 
+switch of ssh, so your rsync command will become
+rsync -e 'ssh -i /path/to/key'
+The problem is that, if you computer is stolen they can use the key as it is 
+unprotected.
+
+The other, more secure solution is to use the ssh agent. You start the agent 
+with -c or -s (depending on your shell) and store its output in a file, and 
+you add the necessary key to the agent (keychain can do that for you, you 
+only have to type the key password). Then from your cron script, you source 
+that file and the agent will be available to the rest of the script.
+The drawback here, is that you must start the agent manually each time the 
+computer is restarted.
+
+Regards
+-- 
+Renaud Michel
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018177.html b/zarb-ml/mageia-dev/2012-August/018177.html new file mode 100644 index 000000000..83c83eebf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018177.html @@ -0,0 +1,121 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 14 23:35:50 CEST 2012 +

+
+ +
'Twas brillig, and Colin Guthrie at 14/08/12 20:18 did gyre and gimble:
+> 'Twas brillig, and Colin Guthrie at 14/08/12 18:45 did gyre and gimble:
+>> 'Twas brillig, and Johnny A. Solbu at 14/08/12 18:32 did gyre and gimble:
+>>> On Tuesday 14 August 2012 19:30, Colin Guthrie wrote:
+>>>> if you can wait, I'll try and suss out the problem and issue an
+>>>> updated dracut package.
+>>>
+>>> I can wait.
+>>
+>> Actually, just in case I cannot reproduce, you can try the following:
+>>
+>> 1. cd
+>> 2. mkdir foo
+>> 3. /usr/lib/dracut/dracut-install -D $HOME/foo bash
+>>
+>> This should just copy the bash binary to the foo tree. Nothing more.
+>>
+>> 4. find $HOME/foo -type f '(' -perm -0100 -or -perm -0010 -or -perm
+>> -0001 ')' -print0 | xargs -r -0 /usr/lib/dracut/dracut-install --debug
+>> -D $HOME/foo -R
+>>
+>>
+>> This should install all the needed libs for bash.
+>>
+>> The output from step 4 and and "ls -lR $HOME/foo" at the end would be
+>> interesting I think.
+>>
+>> I will still try and set this up at home when I get back from work tho'.
+> 
+> OK, I can reproduce the problem now in a VM. That said, the above stuff
+> works fine... so go figure :s
+> 
+> I'll puzzle it out.
+
+Thanks for your patience with this. I've now fixed the bugs in dracut,
+so it *should* work a lot better now!
+
+When dracut-023-3.mga3 hits the mirrors, just urpmi it and go through
+the motions again and *hopefully* it'll be a lot smoother now :)
+
+I've submitted the bugfixes upstream.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018178.html b/zarb-ml/mageia-dev/2012-August/018178.html new file mode 100644 index 000000000..97c667a49 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018178.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 15 00:36:06 CEST 2012 +

+
+ +
On Tuesday 14 August 2012 23:35, Colin Guthrie wrote:
+> Thanks for your patience with this. I've now fixed the bugs in dracut,
+> so it *should* work a lot better now!
+
+It works. \o/
+
+Now I have to figure out how to install rpm, with all dependencies. in order to complete the upgrade. But that should be easier. ;-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120814/289491b3/attachment.asc>
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018179.html b/zarb-ml/mageia-dev/2012-August/018179.html new file mode 100644 index 000000000..03df7f77b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018179.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 15 00:54:45 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 14/08/12 23:36 did gyre and gimble:
+> On Tuesday 14 August 2012 23:35, Colin Guthrie wrote:
+>> Thanks for your patience with this. I've now fixed the bugs in dracut,
+>> so it *should* work a lot better now!
+> 
+> It works. \o/
+
+Yay! Thanks for confirming :)
+
+
+> Now I have to figure out how to install rpm, with all dependencies. in order to complete the upgrade. But that should be easier. ;-)=
+
+Yeah at the start of the thread (before you identified where the problem
+was), I think I mentioned installing the filesystem package first with
+--allow-nodeps. Then everything else should go as smoothly as any other
+update :)
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018180.html b/zarb-ml/mageia-dev/2012-August/018180.html new file mode 100644 index 000000000..86238df2d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018180.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] UsrMove failure + + + + + + + + + +

[Mageia-dev] UsrMove failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 15 02:04:34 CEST 2012 +

+
+ +
On Wednesday 15 August 2012 00:54, Colin Guthrie wrote:
+> Yeah at the start of the thread (before you identified where the problem
+> was), I think I mentioned installing the filesystem package first with
+> --allow-nodeps. Then everything else should go as smoothly as any other
+> update :)
+
+It did. 
+I found it on bugzilla before you sent the mail. :-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120815/6f0c46f6/attachment-0001.asc>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018181.html b/zarb-ml/mageia-dev/2012-August/018181.html new file mode 100644 index 000000000..28256850a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018181.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] Can I upgrade dpkg and related packages? + + + + + + + + + +

[Mageia-dev] Can I upgrade dpkg and related packages?

+ Shlomi Fish + shlomif at shlomifish.org +
+ Wed Aug 15 10:10:15 CEST 2012 +

+
+ +
Hi all,
+
+I filed a bug about dpkg being out-of-date on Mageia Cauldron:
+
+https://bugs.mageia.org/show_bug.cgi?id=6924
+
+I filed it two weeks ago, and did not get a reply, although it was marked as a junior
+job. This bug report was prompted by this bug report:
+
+https://bugs.mageia.org/show_bug.cgi?id=6887
+
+which was reported against the alien package.
+
+Can I update dpkg? Any replies will be appreciated.
+
+Regards,
+
+	Shlomi Fish
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+Funny Anti-Terrorism Story - http://shlom.in/enemy
+
+If God exists and is the ego‐maniacal, sadistic and helpless creature that is
+described in the Old Testament, then we’re in deep trouble.
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018182.html b/zarb-ml/mageia-dev/2012-August/018182.html new file mode 100644 index 000000000..2fef3040b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018182.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] problem building grass - changes in ffmpeg + + + + + + + + + +

[Mageia-dev] problem building grass - changes in ffmpeg

+ Oliver Burger + oliver.bgr at googlemail.com +
+ Wed Aug 15 10:36:44 CEST 2012 +

+
+ +
Hi there,
+
+I have a problem with grass since we updated ffmpeg on Cauldron.
+The problem is a change in ffmpeg which results in grass not building 
+anymore.
+I tried to fix it myself, but I was not able to so I asked upstream 
+about it, who were not really responsive.
+As I searched further for a solution I noticed that none of the other 
+big distros (openSUSE, Fedora, Debian, Ubuntu) do compile grass with 
+ffmpeg support.
+So here is the question.
+Should I just disable the ffmpeg support in grass as the others do or is 
+anyone willing into it?
+
+Oliver
+
+-- 
+Oliver Burger aka obgr_seneca
+
+Mageia contributor
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018183.html b/zarb-ml/mageia-dev/2012-August/018183.html new file mode 100644 index 000000000..14584e9ad --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018183.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Wed Aug 15 11:44:28 CEST 2012 +

+
+ +
After some update( I don't do regular reboot after update, so I can't
+
+trace which one triggers this), I got my Dell screen constantly fall into
+
+powersave mode directly. I had tried with windows, which got no problem at  
+all.
+
+The reason may lies in the driver? For now, if I use the ati driver,
+
+the I can boot into the system, but after some time, the screen would  
+directly
+
+goes into powersave mode. If I use the fglrx driver, it's even worse: I  
+can't
+
+even boot into KDM.
+
+The system is still functional, because I can still ssh into it. Any  
+additional
+
+message needed? This is driving me crazy.
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018184.html b/zarb-ml/mageia-dev/2012-August/018184.html new file mode 100644 index 000000000..5f8734629 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018184.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Remco Rijnders + remco at webconquest.com +
+ Wed Aug 15 11:54:11 CEST 2012 +

+
+ +
On Wed, Aug 15, 2012 at 05:44:28PM +0800, Kira wrote in 
+<op.wi2tcehfct0cxl at kira-notebook.kirayao>:
+>After some update( I don't do regular reboot after update, so I can't
+>
+>trace which one triggers this), I got my Dell screen constantly fall into
+>
+>powersave mode directly. I had tried with windows, which got no 
+>problem at all.
+
+Hi Kira,
+
+Please see the thread on this list started by Frank on the 7th of this 
+month in message <502117D6.303 at roadrunner.com> .
+
+I hope that helps!
+
+Remmy
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 836 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120815/d3548ec1/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018185.html b/zarb-ml/mageia-dev/2012-August/018185.html new file mode 100644 index 000000000..6f37fbe2f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018185.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Wed Aug 15 12:04:46 CEST 2012 +

+
+ +
在 Wed, 15 Aug 2012 17:54:11 +0800, Remco Rijnders  
+<remco at webconquest.com>寫道:
+
+> On Wed, Aug 15, 2012 at 05:44:28PM +0800, Kira wrote in
+> <op.wi2tcehfct0cxl at kira-notebook.kirayao>:
+>> After some update( I don't do regular reboot after update, so I can't
+>>
+>> trace which one triggers this), I got my Dell screen constantly fall  
+>> into
+>>
+>> powersave mode directly. I had tried with windows, which got no
+>> problem at all.
+>
+> Hi Kira,
+>
+> Please see the thread on this list started by Frank on the 7th of this
+> month in message <502117D6.303 at roadrunner.com> .
+>
+> I hope that helps!
+>
+> Remmy
+My problem is that, even I boot in the rescue mode, the monitor still
+
+shutdown on its own.
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018186.html b/zarb-ml/mageia-dev/2012-August/018186.html new file mode 100644 index 000000000..394180454 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018186.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 15 12:43:37 CEST 2012 +

+
+ +
I finally managed to complete the usrmove conversion, and today KDE failed.
+When login in it complaiins: "Could not start ksmserver. Check your installation". Same happens with startx.
+When I manually launch /usr/bin/ksmserver in a terminal, it segfaults.
+
+kdebase4-workspace is the newest package, which was installed after completing the usrmove.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120815/e8957c28/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018187.html b/zarb-ml/mageia-dev/2012-August/018187.html new file mode 100644 index 000000000..d9d4b1d60 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018187.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 15 12:54:00 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 15/08/12 11:43 did gyre and gimble:
+> I finally managed to complete the usrmove conversion, and today KDE failed.
+> When login in it complaiins: "Could not start ksmserver. Check your installation". Same happens with startx.
+> When I manually launch /usr/bin/ksmserver in a terminal, it segfaults.
+> 
+> kdebase4-workspace is the newest package, which was installed after completing the usrmove.
+> 
+
+I wouldn't necessarily jump to the conclusion that this is *caused* by
+the usrmove. Once it's done, there is very little it does in and off
+itself to get in the way. All the paths that worked before still work.
+The only difference would be if some code does some strange things with
+checking folders in /bin /sbin, /lib* etc. which is very, very unlikely.
+
+A more likely fallout is the conversion of /var/run and /var/lock to
+symlinks to /run. This speeds up boot by a few seconds (I've seen
+mandriva-clean-var-run-lock.service taking >5s on some machines with
+slow disks) so it's a very useful change.
+
+That said there are still a few pagages that need fixing up for this:
+
+urpmf "/var/(run|lock)" | grep ":/var"
+
+About 87 packages in total. Perhaps one of them is to blame for your
+problem, but it doesn't look immediately obvious that any of those
+packages would cause any problems. Maybe policykit, but even then I'm
+not sure.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018188.html b/zarb-ml/mageia-dev/2012-August/018188.html new file mode 100644 index 000000000..d59b936a2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018188.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Frank Griffin + ftg at roadrunner.com +
+ Wed Aug 15 13:08:59 CEST 2012 +

+
+ +
On 08/15/2012 06:04 AM, Kira wrote:
+> My problem is that, even I boot in the rescue mode, the monitor still
+>
+> shutdown on its own.
+>
+Try
+         xset -q
+
+and then
+         xset -dpms
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018189.html b/zarb-ml/mageia-dev/2012-August/018189.html new file mode 100644 index 000000000..4920f2ee3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018189.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Shlomi Fish + shlomif at shlomifish.org +
+ Wed Aug 15 13:06:05 CEST 2012 +

+
+ +
Hi Johnny,
+On Wed, 15 Aug 2012 11:43:37 +0100
+"Johnny A. Solbu" <cooker at solbu.net> wrote:
+
+> I finally managed to complete the usrmove conversion, 
+
+Would you mind sharing how you were able to?
+
+> and today KDE
+> failed. When login in it complaiins: "Could not start ksmserver.
+> Check your installation". Same happens with startx. When I manually
+> launch /usr/bin/ksmserver in a terminal, it segfaults.
+> 
+> kdebase4-workspace is the newest package, which was installed after
+> completing the usrmove.
+
+KDE is working fine here. Does it work for you fine in a new UNIX user?
+
+Regards,
+
+	Shlomi Fish
+
+> 
+
+
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+Free (Creative Commons) Music Downloads, Reviews and more - http://jamendo.com/
+
+In the Technion, there are many ways to get from one place to the other, but
+they are all the same length.
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018190.html b/zarb-ml/mageia-dev/2012-August/018190.html new file mode 100644 index 000000000..5fff7e390 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018190.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 15 13:22:18 CEST 2012 +

+
+ +
On Wednesday 15 August 2012 13:06, Shlomi Fish wrote:
+> On Wed, 15 Aug 2012 11:43:37 +0100
+> "Johnny A. Solbu" <cooker at solbu.net> wrote:
+> 
+> > I finally managed to complete the usrmove conversion, 
+> 
+> Would you mind sharing how you were able to?
+
+It turned out to be a bug in dracut, which colin fixed last night. After installing the updated dracut and regenerating initrd with teh convertfs module/script, it was converted.
+then it was as simple as instaling "filesystem" with -allow-nodepa switch, th erest of the update went flawless.
+
+> Does it work for you fine in a new UNIX user?
+
+No. Creating a new test user changes nothing.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120815/8cd56710/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018191.html b/zarb-ml/mageia-dev/2012-August/018191.html new file mode 100644 index 000000000..cc18f8627 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018191.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 15 13:39:10 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 15/08/12 12:22 did gyre and gimble:
+> On Wednesday 15 August 2012 13:06, Shlomi Fish wrote:
+>> On Wed, 15 Aug 2012 11:43:37 +0100 "Johnny A. Solbu"
+>> <cooker at solbu.net> wrote:
+>> 
+>>> I finally managed to complete the usrmove conversion,
+>> 
+>> Would you mind sharing how you were able to?
+> 
+> It turned out to be a bug in dracut, which colin fixed last night.
+
+Yeah, just for reference, the bug was in the newer dracut versions. Most
+people doing the upgrade did so with (approximately) the same version of
+dracut as in mga2 (I deliberately held back on updating dracut for this
+reason).
+
+So this bug would only affect users trying to convert with dracut 023+
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018192.html b/zarb-ml/mageia-dev/2012-August/018192.html new file mode 100644 index 000000000..1eafad37b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018192.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Wed Aug 15 14:19:31 CEST 2012 +

+
+ +
在 Wed, 15 Aug 2012 19:08:59 +0800, Frank Griffin <ftg at roadrunner.com>寫道:
+
+> On 08/15/2012 06:04 AM, Kira wrote:
+>> My problem is that, even I boot in the rescue mode, the monitor still
+>>
+>> shutdown on its own.
+>>
+> Try
+>          xset -q
+>
+> and then
+>          xset -dpms
+Already Tried. It tells me DPMS is off, but then the screen goes off
+
+by itself. I had tried with different plug(DVI & D-Sub), but same problem.
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018193.html b/zarb-ml/mageia-dev/2012-August/018193.html new file mode 100644 index 000000000..5c1402400 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018193.html @@ -0,0 +1,140 @@ + + + + [Mageia-dev] ANN: Recent changes in QA updates validation + + + + + + + + + +

[Mageia-dev] ANN: Recent changes in QA updates validation

+ Samuel Verschelde + stormi at laposte.net +
+ Wed Aug 15 15:35:51 CEST 2012 +

+
+ +
Hi,
+
+During summer QA has not stopped working, and is still trying to improve the 
+process so that updates are pushed as quickly as possible.
+
+First, the QA team now uses http://mageia.madb.org/tools/updates to have an 
+overview of current updates candidates. Major security updates are first in 
+list, in bold (or even red bold for highly critical ones). Those are usually 
+pushed very fast.
+
+Other changes include :
+
+--- Taking into account packager tests for updates they provided ---
+
+Until now, packagers could not test their own updates. We decided to change 
+this rule because packagers often know their packages better than QA team. So 
+now packagers can test their own updates, within the following conditions: 
+only one arch per Mageia version, and final update validation must still be 
+done by a QA team member.
+
+So when you provide an update, you can tell us what you have tested, on which 
+version and arch, and how (step by step instructions much appreciated!). Then 
+a QA team member will just have to test the other arch and validate the 
+update, hopefully very fast if a procedure is provided. 
+
+This policy change can be reviewed later if problems arise.
+
+For the record, here is how QA tests update candidates: 
+https://wiki.mageia.org/en/QA_process_for_validating_updates#Test
+
+--- Identification of update candidates coming with a testing procedure ---
+
+Update candidates that have a testing procedure (either provided by the 
+packager or by QA team members) are validated really faster than updates 
+candidates without a procedure. Indeed, most of QA's time is put in trying to 
+find how a package works, so we really appreciate testing instructions.
+
+We added a new "has_procedure" whiteboard marker in bugzilla to identify 
+updates that have a testing procedure. They show in 
+http://mageia.madb.org/tools/updates
+
+--- Identification of update candidates pending packager input ---
+
+We added a new "feedback" whiteboard marker in bugzilla to identify updates 
+for which packager input has been requested. They have a gray background in 
+the aforementioned page. 
+
+Update candidates with that marker are held for a few days in hope that the 
+packager will answer (a simple "please push regardless of this issue" is 
+sometimes enough as a feedback), and QA members give priority to other updates 
+in the meantime. 
+
+Note : they are not held forever, unless the problem is found to be blocking. 
+We review stalled updates regularly, although we don't like pushing updates 
+when the packager doesn't answer our questions at al, of coursel. Critical 
+security fixes are usually not held this way. When questions are answered, QA 
+team usually removes the feedback marker itself, but don't hesitate to do so 
+yourself when answering!
+
+Do you have any questions or remark?
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018194.html b/zarb-ml/mageia-dev/2012-August/018194.html new file mode 100644 index 000000000..565e3ec10 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018194.html @@ -0,0 +1,139 @@ + + + + [Mageia-dev] Ruby update issues in cauldron + + + + + + + + + +

[Mageia-dev] Ruby update issues in cauldron

+ Maât + maat-ml at vilarem.net +
+ Wed Aug 15 16:58:47 CEST 2012 +

+
+ +
Hi there,
+
+I don't know how to fill the bugtracker for that:
+
+[root at localhost ~]# LC_ALL=C urpmi --auto-update
+...
+Some requested packages cannot be installed:
+ruby-actionpack-3.2.5-2.mga3.noarch (due to unsatisfied
+rubygem(sprockets)[< 2.2])
+ruby-activerecord-3.2.5-1.mga3.noarch (due to unsatisfied
+rubygem(activemodel)[== 3.2.5])
+ruby-activeresource-3.2.5-2.mga3.noarch (due to unsatisfied
+rubygem(activemodel)[== 3.2.5])
+ruby-linecache-0.46-1.mga3.x86_64 (due to unsatisfied
+rubygem(rbx-require-relative)[> 0.0.4])
+
+if i answer yes then it tries to remove many ruby packages (including
+rails !):
+
+The following packages have to be removed for others to be upgraded:
+lib64freerdp0-0.8.2-1.mga1.x86_64
+ (due to unsatisfied freerdp == 0.8.2-1.mga1)
+ruby-actionmailer-2.3.14-1.mga2.noarch
+ (due to unsatisfied rubygem(actionpack) == 2.3.14)
+ruby-actionpack-2.3.14-1.mga2.noarch
+ (due to unsatisfied rubygem(activesupport) == 2.3.14)
+ruby-activerecord-2.3.14-1.mga2.noarch
+ (due to unsatisfied rubygem(activesupport) == 2.3.14)
+ruby-activeresource-2.3.14-1.mga2.noarch
+ (due to unsatisfied rubygem(activesupport) == 2.3.14)
+ruby-after_commit-1.0.8-1.mga1.noarch
+ (due to unsatisfied rubygem(activerecord) < 3.0.0)
+ruby-oa-oauth-0.2.2-1.mga1.noarch
+ (due to unsatisfied rubygem(nokogiri) < 1.5)
+ruby-paperclip-2.3.8-1.mga1.noarch
+ (due to missing rubygem(activerecord))
+ruby-rails-2.3.14-1.mga2.noarch
+ (due to unsatisfied rubygem(activesupport) == 2.3.14,
+  due to unsatisfied rubygem(activerecord) == 2.3.14,
+  due to unsatisfied rubygem(actionpack) == 2.3.14,
+  due to unsatisfied rubygem(activeresource) == 2.3.14,
+  due to unsatisfied rubygem(actionmailer) == 2.3.14)
+ruby-text-format-1.0.0-2.mga1.noarch
+ (due to unsatisfied rubygem(text-hyphen) < 1.1)
+ruby-thinking-sphinx-1.4.3-2.mga1.noarch
+ (due to unsatisfied rubygem(activerecord) < 3.0.0,
+  due to unsatisfied rubygem(activerecord) >= 1.15.6,
+  due to unsatisfied rubygem(after_commit) >= 1.0.7)
+ruby-vestal_versions-1.0.2-1.mga1.noarch
+ (due to unsatisfied rubygem(activerecord) >= 2.1.0)
+teambox-2.2-7.mga2.noarch
+ (due to unsatisfied rubygem(rails) >= 2.3.5,
+  due to unsatisfied rubygem(paperclip) >= 2.3.6,
+  due to unsatisfied rubygem(thinking-sphinx) >= 1.3.15,
+  due to unsatisfied rubygem(vestal_versions) >= 1.0.2)
+teambox-httpd-2.2-7.mga2.noarch
+ (due to unsatisfied teambox == 2.2-7.mga2)
+
+What do you think ?
+
+Maat
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018195.html b/zarb-ml/mageia-dev/2012-August/018195.html new file mode 100644 index 000000000..2ae4c939c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018195.html @@ -0,0 +1,136 @@ + + + + [Mageia-dev] no mouse in cauldron boot.iso + + + + + + + + + +

[Mageia-dev] no mouse in cauldron boot.iso

+ eatdirt + dirteat at gmail.com +
+ Wed Aug 15 19:28:45 CEST 2012 +

+
+ +
Hi there,
+I know it is very early to test the installer; but after screwing up the 
+/usr migration I reinstalled cauldron from thye current boot.iso; which 
+was not finding any mouse on my machine.
+
+Let me know if you want me to open a bug report.
+
+Cheers,
+Christophe.
+
+
+
+
+lspci output>>>>>
+
+00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller 
+Hub (rev 02)
+00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root 
+Port (rev 02)
+00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition 
+Audio Controller (rev 01)
+00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 
+1 (rev 01)
+00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 
+4 (rev 01)
+00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI 
+Controller #1 (rev 01)
+00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI 
+Controller #2 (rev 01)
+00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI 
+Controller #3 (rev 01)
+00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI 
+Controller #4 (rev 01)
+00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI 
+Controller (rev 01)
+00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
+00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC 
+Interface Bridge (rev 01)
+00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE 
+Controller (rev 01)
+00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller 
+[IDE mode] (rev 01)
+00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
+01:00.0 USB controller: ALi Corporation USB 1.1 Controller (rev 03)
+01:00.1 USB controller: ALi Corporation USB 1.1 Controller (rev 03)
+01:00.3 USB controller: ALi Corporation USB 2.0 Controller (rev 01)
+01:00.4 FireWire (IEEE 1394): ALi Corporation M5253 P1394 OHCI 1.1 
+Controller
+01:01.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI
+01:02.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
+02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
+RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
+04:00.0 VGA compatible controller: ATI Technologies Inc R580 [Radeon 
+X1900 XT] (Primary)
+04:00.1 Display controller: ATI Technologies Inc R580 [Radeon X1900 XT] 
+(Secondary)
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018196.html b/zarb-ml/mageia-dev/2012-August/018196.html new file mode 100644 index 000000000..854f88ff7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018196.html @@ -0,0 +1,124 @@ + + + + [Mageia-dev] Ruby update issues in cauldron + + + + + + + + + +

[Mageia-dev] Ruby update issues in cauldron

+ Shlomi Fish + shlomif at shlomifish.org +
+ Wed Aug 15 20:26:29 CEST 2012 +

+
+ +
Hi Maât,
+
+On Wed, 15 Aug 2012 16:58:47 +0200
+Maât <maat-ml at vilarem.net> wrote:
+
+> Hi there,
+> 
+> I don't know how to fill the bugtracker for that:
+> 
+> [root at localhost ~]# LC_ALL=C urpmi --auto-update
+> ...
+> Some requested packages cannot be installed:
+> ruby-actionpack-3.2.5-2.mga3.noarch (due to unsatisfied
+> rubygem(sprockets)[< 2.2])
+> ruby-activerecord-3.2.5-1.mga3.noarch (due to unsatisfied
+> rubygem(activemodel)[== 3.2.5])
+> ruby-activeresource-3.2.5-2.mga3.noarch (due to unsatisfied
+> rubygem(activemodel)[== 3.2.5])
+> ruby-linecache-0.46-1.mga3.x86_64 (due to unsatisfied
+> rubygem(rbx-require-relative)[> 0.0.4])
+> 
+> if i answer yes then it tries to remove many ruby packages (including
+> rails !):
+
+Currently, we have begun the update of the ruby packages on Mageia Linux Cauldron, but
+it was not finished, so it is kinda in a limbo. We have also ran into this bug,
+which prevents further progress:
+
+https://bugs.mageia.org/show_bug.cgi?id=7052
+
+( "ruby gems' automatic dependency detection [in rpm-build] is broken").
+
+Sorry for the inconvenience.
+
+Regards,
+
+	Shlomi Fish
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+http://www.shlomifish.org/humour/ways_to_do_it.html
+
+  :)-<
+   +--
+    — Moses the Smiley by Shlomi Fish
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018197.html b/zarb-ml/mageia-dev/2012-August/018197.html new file mode 100644 index 000000000..5a74917f2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018197.html @@ -0,0 +1,113 @@ + + + + [Mageia-dev] Can I upgrade dpkg and related packages? + + + + + + + + + +

[Mageia-dev] Can I upgrade dpkg and related packages?

+ Shlomi Fish + shlomif at shlomifish.org +
+ Thu Aug 16 10:21:47 CEST 2012 +

+
+ +
Hi Bruno,
+
+On Thu, 16 Aug 2012 00:10:35 +0200
+Bruno Cornec <bruno at victoria.frmug.org> wrote:
+
+> On Wed, Aug 15, 2012 at 11:10:15AM +0300, Shlomi Fish wrote:
+> > Can I update dpkg? Any replies will be appreciated.
+> 
+> I do not see any issue with that. I'm on vacation now, so have not
+> worked on it earlier.
+
+OK, thanks for your reply. I (or one of my apprentices) will get to it soon.
+
+Regards,
+
+	Shlomi Fish
+
+> 
+> I'm using it to build and sign deb packages on mageia myself.
+> 
+> Bruno.
+
+
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+What Makes Software Apps High Quality -  http://shlom.in/sw-quality
+
+mplayer 0.9.999.2010.03.11-rc5-adc83b19e793491b1c6ea0fd8b46cd9f32e592fc is
+now available for download.
+    — Shlomi Fish and d3x.
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018198.html b/zarb-ml/mageia-dev/2012-August/018198.html new file mode 100644 index 000000000..f385b9610 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018198.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Thu Aug 16 10:33:34 CEST 2012 +

+
+ +
在 Wed, 15 Aug 2012 20:19:31 +0800, Kira <elegant.pegasus at gmail.com>寫道:
+> Already Tried. It tells me DPMS is off, but then the screen goes off
+>
+> by itself. I had tried with different plug(DVI & D-Sub), but same  
+> problem.
+Anyone think of other possibility? This is really disturbing....
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018199.html b/zarb-ml/mageia-dev/2012-August/018199.html new file mode 100644 index 000000000..26fd5c0bd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018199.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ andre999 + andre999mga at laposte.net +
+ Thu Aug 16 12:21:47 CEST 2012 +

+
+ +
Kira a écrit :
+> 在 Wed, 15 Aug 2012 20:19:31 +0800, Kira <elegant.pegasus at gmail.com>寫道:
+>> Already Tried. It tells me DPMS is off, but then the screen goes off
+>>
+>> by itself. I had tried with different plug(DVI & D-Sub), but same 
+>> problem.
+> Anyone think of other possibility? This is really disturbing....
+>
+I use gnome (thus gdm), and dpms is off on my system as well. and I have 
+a similar problem from time to time (almost every day).
+I found a workaround by chance : if I click the mouse several times when 
+this happens, then the screen turns on after a few seconds, and 
+everything is still running.  Otherwise I have to reboot to get my 
+display back.
+I also use the ati driver and not fglrx, and leave my system on most of 
+the time.
+So maybe try this workaround ?
+
+-- 
+André
+
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018200.html b/zarb-ml/mageia-dev/2012-August/018200.html new file mode 100644 index 000000000..ba419f975 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018200.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Thu Aug 16 12:31:30 CEST 2012 +

+
+ +
在 Thu, 16 Aug 2012 18:21:47 +0800, andre999 <andre999mga at laposte.net>寫道:
+>>
+> I use gnome (thus gdm), and dpms is off on my system as well. and I have  
+> a similar problem from time to time (almost every day).
+> I found a workaround by chance : if I click the mouse several times when  
+> this happens, then the screen turns on after a few seconds, and  
+> everything is still running.  Otherwise I have to reboot to get my  
+> display back.
+> I also use the ati driver and not fglrx, and leave my system on most of  
+> the time.
+> So maybe try this workaround ?
+>
+I had tried it before, but it just died.....
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018201.html b/zarb-ml/mageia-dev/2012-August/018201.html new file mode 100644 index 000000000..d2559ed67 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018201.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Johnny A. Solbu + cooker at solbu.net +
+ Thu Aug 16 15:48:11 CEST 2012 +

+
+ +
On Wednesday 15 August 2012 12:54, Colin Guthrie wrote:
+> I wouldn't necessarily jump to the conclusion that this is *caused* by
+> the usrmove.
+
+I never said it did, nor did I imply it.
+I said it happened as a result of upgrading packages, /after/ the usrmove. There is a difference. ;-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120816/1f57da88/attachment.asc>
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018202.html b/zarb-ml/mageia-dev/2012-August/018202.html new file mode 100644 index 000000000..24e2fd926 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018202.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Sander Lepik + sander.lepik at eesti.ee +
+ Thu Aug 16 15:53:12 CEST 2012 +

+
+ +
16.08.2012 16:48, Johnny A. Solbu kirjutas:
+> On Wednesday 15 August 2012 12:54, Colin Guthrie wrote:
+>> I wouldn't necessarily jump to the conclusion that this is *caused* by
+>> the usrmove.
+> I never said it did, nor did I imply it.
+> I said it happened as a result of upgrading packages, /after/ the usrmove. There is a difference. ;-)=
+>
+Your title pretty much sounds like usrmove is to blame :P
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018203.html b/zarb-ml/mageia-dev/2012-August/018203.html new file mode 100644 index 000000000..999bac722 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018203.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] The life After usrMove - KDE failure + + + + + + + + + +

[Mageia-dev] The life After usrMove - KDE failure

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Aug 16 15:55:50 CEST 2012 +

+
+ +
Le 16/08/2012 15:53, Sander Lepik a écrit :
+> 16.08.2012 16:48, Johnny A. Solbu kirjutas:
+>> On Wednesday 15 August 2012 12:54, Colin Guthrie wrote:
+>>> I wouldn't necessarily jump to the conclusion that this is *caused* by
+>>> the usrmove.
+>> I never said it did, nor did I imply it.
+>> I said it happened as a result of upgrading packages, /after/ the usrmove. There is a difference. ;-)=
+>>
+> Your title pretty much sounds like usrmove is to blame :P
+It could as well have implied than KDE was the actual culprit :P
+
+-- 
+BOFH excuse #93:
+
+Feature not yet implemented
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018204.html b/zarb-ml/mageia-dev/2012-August/018204.html new file mode 100644 index 000000000..24af1cd29 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018204.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] network interface renaming not working anymore + + + + + + + + + +

[Mageia-dev] network interface renaming not working anymore

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Thu Aug 16 21:30:53 CEST 2012 +

+
+ +
hi,
+
+When I finally rebooted a cauldron system that acts as a router, it turned 
+out the network interfaces eth0 and eth1 were switched, exposing 
+"internal" services to the outside world and leaving me without internet 
+access. Syslog contains:
+Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface name eth0 to eth1: File exists
+Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface name eth1 to eth0: File exists
+
+Of course this has worked for years, so it breaking is not something 
+anyone would expect. It also seems to be unneeded. After some looking 
+around I could (temporarily) fix it quite easily by adding:
+         ifrename -i eth0 -n rename0
+         ifrename -i eth1 -n rename1
+         ifrename -i rename0
+         ifrename -i rename1
+to /etc/init.d/network and describing the mapping in /etc/iftab . 
+So now I have two questions:
+- Has anyone else seen this?
+- What change is causing this: kernel, udev/systemd, or something else?
+
+The network devices use the same driver so there is no other way to 
+distinguish them than by MAC address or PCI ID.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018205.html b/zarb-ml/mageia-dev/2012-August/018205.html new file mode 100644 index 000000000..2aee589c8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018205.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] network interface renaming not working anymore + + + + + + + + + +

[Mageia-dev] network interface renaming not working anymore

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 16 21:58:31 CEST 2012 +

+
+ +
'Twas brillig, and Christiaan Welvaart at 16/08/12 20:30 did gyre and
+gimble:
+> hi,
+> 
+> When I finally rebooted a cauldron system that acts as a router, it
+> turned out the network interfaces eth0 and eth1 were switched, exposing
+> "internal" services to the outside world and leaving me without internet
+> access. Syslog contains:
+> Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface
+> name eth0 to eth1: File exists
+> Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface
+> name eth1 to eth0: File exists
+> 
+> Of course this has worked for years, so it breaking is not something
+> anyone would expect. It also seems to be unneeded. After some looking
+> around I could (temporarily) fix it quite easily by adding:
+>         ifrename -i eth0 -n rename0
+>         ifrename -i eth1 -n rename1
+>         ifrename -i rename0
+>         ifrename -i rename1
+> to /etc/init.d/network and describing the mapping in /etc/iftab . So now
+> I have two questions:
+> - Has anyone else seen this?
+> - What change is causing this: kernel, udev/systemd, or something else?
+> 
+> The network devices use the same driver so there is no other way to
+> distinguish them than by MAC address or PCI ID.
+
+Yeah this is no longer supported upstream as it was apparently very
+hacky. Last time I asked Kay about it, there was something else to
+replace it but I've not followed up what that is recently. I'll ask him
+again next time we're chatting.
+
+Cheers
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018206.html b/zarb-ml/mageia-dev/2012-August/018206.html new file mode 100644 index 000000000..fca676043 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018206.html @@ -0,0 +1,120 @@ + + + + [Mageia-dev] network interface renaming not working anymore + + + + + + + + + +

[Mageia-dev] network interface renaming not working anymore

+ Christiaan Welvaart + cjw at daneel.dyndns.org +
+ Thu Aug 16 22:55:19 CEST 2012 +

+
+ +
On Thu, 16 Aug 2012, Colin Guthrie wrote:
+
+> 'Twas brillig, and Christiaan Welvaart at 16/08/12 20:30 did gyre and
+> gimble:
+>> hi,
+>>
+>> When I finally rebooted a cauldron system that acts as a router, it
+>> turned out the network interfaces eth0 and eth1 were switched, exposing
+>> "internal" services to the outside world and leaving me without internet
+>> access. Syslog contains:
+>> Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface
+>> name eth0 to eth1: File exists
+>> Aug 15 22:48:29 zem systemd-udevd[404]: error changing net interface
+>> name eth1 to eth0: File exists
+>>
+>> Of course this has worked for years, so it breaking is not something
+>> anyone would expect. It also seems to be unneeded. After some looking
+>> around I could (temporarily) fix it quite easily by adding:
+>>         ifrename -i eth0 -n rename0
+>>         ifrename -i eth1 -n rename1
+>>         ifrename -i rename0
+>>         ifrename -i rename1
+>> to /etc/init.d/network and describing the mapping in /etc/iftab . So now
+>> I have two questions:
+>> - Has anyone else seen this?
+>> - What change is causing this: kernel, udev/systemd, or something else?
+>>
+>> The network devices use the same driver so there is no other way to
+>> distinguish them than by MAC address or PCI ID.
+>
+> Yeah this is no longer supported upstream as it was apparently very
+> hacky. Last time I asked Kay about it, there was something else to
+> replace it but I've not followed up what that is recently. I'll ask him
+> again next time we're chatting.
+
+So it's udev (I tried to install an old udev but that didn't work). Commit 
+looks to be:
+http://cgit.freedesktop.org/systemd/systemd/commit/src/udev?id=97595710b77aa162ca5e20da57d0a1ed7355eaad
+
+Waiting 90s hoping the interface name becomes available is no fun of 
+course but in fact this works fine when the user configured it properly: 
+it did exactly what I now use as workaround only without global control. 
+So we could simply revert it but I wonder why this change was considered 
+necessary. So far I have not found any discussion about it.
+
+
+     Christiaan
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018207.html b/zarb-ml/mageia-dev/2012-August/018207.html new file mode 100644 index 000000000..4e7778cbf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018207.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release kmod-nvidia-current-295.71-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release kmod-nvidia-current-295.71-2.mga3.nonfree

+ Charles A Edwards + CAE at eslrahc.com +
+ Thu Aug 16 23:28:13 CEST 2012 +

+
+ +
On Thu, 16 Aug 2012 17:55:40 +0200 (CEST)
+tmb wrote:
+
+> Name        : kmod-nvidia-current          Relocations: (not
+> relocatable) Version     : 295.71                            Vendor:
+> Mageia.Org Release     : 2.mga3.nonfree                Build Date:
+> Thu Aug 16 17:51:07 2012 Install Date: (not installed)
+> Build Host: ecosse.mageia.org Group       : System/Kernel and
+> hardware    Source RPM: (none) Size        :
+> 9229                             License: Freeware Signature   :
+> (none) Packager    : tmb <tmb>
+> URL         : http://www.nvidia.com/object/unix.html
+
+
+No biggie but the latest certified driver is now 304.37
+released 2012.08.13
+
+
+    Charles
+
+-- 
+After all is said and done, a lot more is said than done
+		-- Murphy's Laws on Technology n°22
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.1-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120816/c56997de/attachment-0001.asc>
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018208.html b/zarb-ml/mageia-dev/2012-August/018208.html new file mode 100644 index 000000000..1633bbbeb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018208.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release kmod-nvidia-current-295.71-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release kmod-nvidia-current-295.71-2.mga3.nonfree

+ Thomas Backlund + tmb at mageia.org +
+ Thu Aug 16 23:31:47 CEST 2012 +

+
+ +
17.08.2012 00:28, Charles A Edwards skrev:
+> On Thu, 16 Aug 2012 17:55:40 +0200 (CEST)
+> tmb wrote:
+>
+>> Name        : kmod-nvidia-current          Relocations: (not
+>> relocatable) Version     : 295.71                            Vendor:
+>> Mageia.Org Release     : 2.mga3.nonfree                Build Date:
+>> Thu Aug 16 17:51:07 2012 Install Date: (not installed)
+>> Build Host: ecosse.mageia.org Group       : System/Kernel and
+>> hardware    Source RPM: (none) Size        :
+>> 9229                             License: Freeware Signature   :
+>> (none) Packager    : tmb <tmb>
+>> URL         : http://www.nvidia.com/object/unix.html
+>
+>
+> No biggie but the latest certified driver is now 304.37
+> released 2012.08.13
+>
+
+Yep, I know, but I wanted to get the 295.71 more tested as it's being 
+pushed to Mageia 2 in order to fix the security issue.
+
+--
+Thomas
+
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018209.html b/zarb-ml/mageia-dev/2012-August/018209.html new file mode 100644 index 000000000..579937f30 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018209.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] Upgrade of Kolab to 3.0 Alpha + + + + + + + + + +

[Mageia-dev] Upgrade of Kolab to 3.0 Alpha

+ Thomas Spuhler + thomas at btspuhler.com +
+ Fri Aug 17 06:01:27 CEST 2012 +

+
+ +
I am starting to upgrade Kolab to 3 Alpha. It will break a lot.
+Also there will be some additional packages.
+I think it's worth the work
+
+http://kolab.org/blog/grote/2012/08/07/alpha-kolab-3.0-and-roundcube-0.8-
+released
+
+We can also get some exposure, they would list the Mageia disti on their WEB 
+site.
+
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018210.html b/zarb-ml/mageia-dev/2012-August/018210.html new file mode 100644 index 000000000..985f08960 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018210.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] Upgrade of Kolab to 3.0 Alpha + + + + + + + + + +

[Mageia-dev] Upgrade of Kolab to 3.0 Alpha

+ Johnny A. Solbu + cooker at solbu.net +
+ Fri Aug 17 06:41:39 CEST 2012 +

+
+ +
On Friday 17 August 2012 06:01, Thomas Spuhler wrote:
+> I am starting to upgrade Kolab to 3 Alpha. It will break a lot.
+
+As in also break non-kolab packages?
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120817/0720de8e/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018211.html b/zarb-ml/mageia-dev/2012-August/018211.html new file mode 100644 index 000000000..ba31cbfa8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018211.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] Ruby update issues in cauldron + + + + + + + + + +

[Mageia-dev] Ruby update issues in cauldron

+ Maât + maat-ml at vilarem.net +
+ Fri Aug 17 08:12:13 CEST 2012 +

+
+ +
Le 15/08/2012 20:26, Shlomi Fish a écrit :
+> Hi Maât,
+>
+> On Wed, 15 Aug 2012 16:58:47 +0200
+> Maât <maat-ml at vilarem.net> wrote:
+>
+>> Hi there,
+>>
+>> I don't know how to fill the bugtracker for that:
+>>
+>> [root at localhost ~]# LC_ALL=C urpmi --auto-update
+>> ...
+>> Some requested packages cannot be installed:
+>> ruby-actionpack-3.2.5-2.mga3.noarch (due to unsatisfied
+>> rubygem(sprockets)[< 2.2])
+>> ruby-activerecord-3.2.5-1.mga3.noarch (due to unsatisfied
+>> rubygem(activemodel)[== 3.2.5])
+>> ruby-activeresource-3.2.5-2.mga3.noarch (due to unsatisfied
+>> rubygem(activemodel)[== 3.2.5])
+>> ruby-linecache-0.46-1.mga3.x86_64 (due to unsatisfied
+>> rubygem(rbx-require-relative)[> 0.0.4])
+>>
+>> if i answer yes then it tries to remove many ruby packages (including
+>> rails !):
+> Currently, we have begun the update of the ruby packages on Mageia Linux Cauldron, but
+> it was not finished, so it is kinda in a limbo. We have also ran into this bug,
+> which prevents further progress:
+>
+> https://bugs.mageia.org/show_bug.cgi?id=7052
+>
+> ( "ruby gems' automatic dependency detection [in rpm-build] is broken").
+>
+> Sorry for the inconvenience.
+>
+> Regards,
+>
+> 	Shlomi Fish
+>
+thx Shlomi...
+
+
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018212.html b/zarb-ml/mageia-dev/2012-August/018212.html new file mode 100644 index 000000000..8b26aca85 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018212.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Upgrade of Kolab to 3.0 Alpha + + + + + + + + + +

[Mageia-dev] Upgrade of Kolab to 3.0 Alpha

+ Thomas Spuhler + thomas at btspuhler.com +
+ Fri Aug 17 16:16:28 CEST 2012 +

+
+ +
On Thursday, August 16, 2012 09:41:39 PM Johnny A. Solbu wrote:
+> On Friday 17 August 2012 06:01, Thomas Spuhler wrote:
+> > I am starting to upgrade Kolab to 3 Alpha. It will break a lot.
+> 
+> As in also break non-kolab packages?
+I don't expect it will break none Kolab packages.
+But it will add dependencies missing until all is done.
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018213.html b/zarb-ml/mageia-dev/2012-August/018213.html new file mode 100644 index 000000000..9b819e9de --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018213.html @@ -0,0 +1,205 @@ + + + + [Mageia-dev] Security updates - help needed (status update) + + + + + + + + + +

[Mageia-dev] Security updates - help needed (status update)

+ David Walser + luigiwalser at yahoo.com +
+ Fri Aug 17 19:56:14 CEST 2012 +

+
+ +
Here's a status update, as some have been fixed and new ones have been found.
+
+I'll be really busy at work for the next couple weeks, so I'll update this in September.
+
+......... updated initial message below ........
+
+There are several packages that need security updates that either have not been built yet, or there are some issues that need help and/or input from packagers.
+
+Please help out with these where you can.
+
+I'll try to organize these into categories and give a little info on them so it's easy to see if you can and want to help.
+
+Web apps
+--------
+ocsinventory - Mageia 1 package needs to be updated or patched (patches available from MDV)
+https://bugs.mageia.org/show_bug.cgi?id=5252
+https://bugs.mageia.org/show_bug.cgi?id=2129
+
+mediawiki - versions we have are at or nearing EOL upstream, probably should be updated.  Oliver Burger is working on this.
+https://bugs.mageia.org/show_bug.cgi?id=3448
+
+drupal - update built, issues found by QA need fixing.  Oliver Burger is working on this.
+https://bugs.mageia.org/show_bug.cgi?id=5844
+
+GNOME software
+--------------
+empathy - XSS issues fixed upstream in 3.2.1 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7008
+
+libvirt - patches available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6526
+
+libgnomesu - re-diffing the patch might be non-trivial since OpenSuSE has many other patches too
+https://bugs.mageia.org/show_bug.cgi?id=7068
+
+gjs - doesn't rebuild against xulrunner in Mageia 1, but doesn't seem to be used by anything
+https://bugs.mageia.org/show_bug.cgi?id=6382
+
+Games
+-----
+openarena, alienarena - affected by DoS bug in quake3 engine.  Juan Luis Baptiste is working on this.
+https://bugs.mageia.org/show_bug.cgi?id=5496
+
+Java-related
+------------
+jruby - fixed upstream in 1.6.5.1
+https://bugs.mageia.org/show_bug.cgi?id=6742
+
+poi - In progress by D Morgan.  Additional updates pending.
+https://bugs.mageia.org/show_bug.cgi?id=6011
+
+apache-commons-compress - In progress by D Morgan.  Mageia 1 updates pending.
+https://bugs.mageia.org/show_bug.cgi?id=6331
+
+apache-commons-daemon - fixed upstream in 1.0.7 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7004
+
+Ruby-related
+------------
+Several security issues, one possible packaging issue
+https://bugs.mageia.org/show_bug.cgi?id=6487
+
+No response has been received from packagers yet
+------------------------------------------------
+ganglia - patch available from Fedora, we have another bug report saying it doesn't start
+https://bugs.mageia.org/show_bug.cgi?id=6874
+
+libreoffice - Mageia 1 only, patch available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6944
+
+phpmyadmin - needs updated to 3.5.2.1 and fixed in Cauldron for new apache conf layout
+https://bugs.mageia.org/show_bug.cgi?id=6905
+
+openafs - patches available from Debian, plus a newer version is in Mageia 1 than Mageia 2
+https://bugs.mageia.org/show_bug.cgi?id=7085
+
+openswan - patches are available from RedHat, one needs re-diffing
+https://bugs.mageia.org/show_bug.cgi?id=7095
+
+torque - also a permissions problem in the package
+https://bugs.mageia.org/show_bug.cgi?id=6082
+
+tor - issues fixed upstream in 0.2.2.34 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=5351
+
+erlang - issue fixed in R14B03 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7062
+
+fuse - patches available from RedHat (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7063
+
+blender - patch available from Fedora (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7065
+
+libvoikko - issue fixed in 3.2.1 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7067
+
+php-ZendFramework - issues fixed upstream in 1.11.6 (only Mageia 1 is affected)
+https://bugs.mageia.org/show_bug.cgi?id=7083
+
+abrt/libreport/btparser - should probably be upgraded to newer versions available from RedHat
+https://bugs.mageia.org/show_bug.cgi?id=6523
+
+sos - 62 patches available from Fedora
+https://bugs.mageia.org/show_bug.cgi?id=6525
+
+x11-server - upstream diffs linked by RedHat, maybe patches available from Ubuntu or Gentoo, plus other security issues fixed by RH/OpenSuSE/Ubuntu
+https://bugs.mageia.org/show_bug.cgi?id=6744
+
+In progress (help needed to finish)
+-----------------------------------
+dhcp - issues fixed upstream in 4.2.4-P1
+https://bugs.mageia.org/show_bug.cgi?id=6872
+
+bind - issues fixed upstream in 9.8.3-P2 and 9.9.1-P2
+https://bugs.mageia.org/show_bug.cgi?id=6873
+
+xen - doesn't build in Cauldron (incompatible pointer type in i8259.c), other patches missing
+https://bugs.mageia.org/show_bug.cgi?id=6931
+
+stunnel - updated/fixed in Cauldron, probably should just port updated version back
+https://bugs.mageia.org/show_bug.cgi?id=3951
+
+gc - links to upstream and Fedora patches available in bug, already fixed in Cauldron
+https://bugs.mageia.org/show_bug.cgi?id=6652
+
+bip - patch in Mageia 1 didn't fix it according to QA, patch wasn't applied in Mageia 2
+https://bugs.mageia.org/show_bug.cgi?id=4319
+
+emacs - re-diffing patch for Emacs 23.2 (Mageia 1) is non-trivial
+https://bugs.mageia.org/show_bug.cgi?id=6995
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018214.html b/zarb-ml/mageia-dev/2012-August/018214.html new file mode 100644 index 000000000..f59922a5a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018214.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sat Aug 18 11:27:45 CEST 2012 +

+
+ +
Le 17/08/2012 19:07, nanardon a écrit :
+> nanardon <nanardon> 2.2.2-7.mga3:
+> + Revision: 281885
+> - fix startup with systemd
+> - fix initscript
+We are supposed to get rid of initscripts, not fix them...
+
+-- 
+BOFH excuse #40:
+
+not enough memory, go get system upgrade
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018215.html b/zarb-ml/mageia-dev/2012-August/018215.html new file mode 100644 index 000000000..82b5751e9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018215.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Sat Aug 18 12:09:20 CEST 2012 +

+
+ +
* Guillaume Rousse (guillomovitch at gmail.com) wrote:
+> Le 17/08/2012 19:07, nanardon a écrit :
+> >nanardon <nanardon> 2.2.2-7.mga3:
+> >+ Revision: 281885
+> >- fix startup with systemd
+> >- fix initscript
+> We are supposed to get rid of initscripts, not fix them...
+
+No problem to me, feel free to fix the systemd part so.
+
+> 
+> -- 
+> BOFH excuse #40:
+> 
+> not enough memory, go get system upgrade
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120818/72d5b886/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018216.html b/zarb-ml/mageia-dev/2012-August/018216.html new file mode 100644 index 000000000..134eb8b99 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018216.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3

+ Johnny A. Solbu + cooker at solbu.net +
+ Sat Aug 18 16:16:02 CEST 2012 +

+
+ +
On Saturday 18 August 2012 11:27, Guillaume Rousse wrote:
+> We are supposed to get rid of initscripts, not fix them...
+
+We are?
+Replacing them with systemd equivalent then I presume. How do we do that? 
+Is there a guide and possibly a conversion tool we can use?
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120818/9bce3683/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018217.html b/zarb-ml/mageia-dev/2012-August/018217.html new file mode 100644 index 000000000..c223bf20b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018217.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release openvpn-2.2.2-7.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sat Aug 18 19:23:00 CEST 2012 +

+
+ +
Le 18/08/2012 16:16, Johnny A. Solbu a écrit :
+> On Saturday 18 August 2012 11:27, Guillaume Rousse wrote:
+>> We are supposed to get rid of initscripts, not fix them...
+>
+> We are?
+> Replacing them with systemd equivalent then I presume. How do we do that?
+> Is there a guide and possibly a conversion tool we can use?
+I usually check first in Fedora git repositories:
+http://pkgs.fedoraproject.org/cgit
+
+Otherwise, systemd.{unit,service,exec} man pages, and someone with nick 
+'coling' on mageia-dev IRC channel :)
+
+-- 
+BOFH excuse #150:
+
+Arcserve crashed the server again.
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018218.html b/zarb-ml/mageia-dev/2012-August/018218.html new file mode 100644 index 000000000..3368a7bfb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018218.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-22.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-22.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Sat Aug 18 19:24:30 CEST 2012 +

+
+ +
Le 18/08/2012 18:56, spuhler a écrit :
+> Name        : task-obsolete                Relocations: (not relocatable)
+> Version     : 3                                 Vendor: Mageia.Org
+> Release     : 22.mga3                       Build Date: Sat Aug 18 18:55:36 2012
+> Install Date: (not installed)               Build Host: jonund.mageia.org
+> Group       : System/Base                   Source RPM: (none)
+> Size        : 17297                            License: GPLv2+
+> Signature   : (none)
+> Packager    : spuhler <spuhler>
+> Summary     : Meta package obsoleting old packages
+> Description :
+> This package is used to obsolete packages that are no longer supported.
+>
+> spuhler <spuhler> 3-22.mga3:
+> + Revision: 282007
+> - removed Obsoletes:  perl-kolab <= 2.2.4-3 because its still needed by current kolab
+>    This need to be removed when upgrading to new version of kolab
+Why are you using task-obsolete package for this, whereas you could 
+perfectly do it from kolab package directly ?
+
+
+-- 
+BOFH excuse #182:
+
+endothermal recalibration
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018219.html b/zarb-ml/mageia-dev/2012-August/018219.html new file mode 100644 index 000000000..b08bc6ec8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018219.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-22.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release task-obsolete-3-22.mga3

+ Thomas Spuhler + thomas at btspuhler.com +
+ Sat Aug 18 19:35:48 CEST 2012 +

+
+ +
On Saturday, August 18, 2012 10:24:30 AM Guillaume Rousse wrote:
+> Le 18/08/2012 18:56, spuhler a écrit :
+> > Name        : task-obsolete                Relocations: (not relocatable)
+> > Version     : 3                                 Vendor: Mageia.Org
+> > Release     : 22.mga3                       Build Date: Sat Aug 18
+> > 18:55:36 2012 Install Date: (not installed)               Build Host:
+> > jonund.mageia.org Group       : System/Base                   Source
+> > RPM: (none)
+> > Size        : 17297                            License: GPLv2+
+> > Signature   : (none)
+> > Packager    : spuhler <spuhler>
+> > Summary     : Meta package obsoleting old packages
+> > Description :
+> > This package is used to obsolete packages that are no longer supported.
+> > 
+> > spuhler <spuhler> 3-22.mga3:
+> > + Revision: 282007
+> > - removed Obsoletes:  perl-kolab <= 2.2.4-3 because its still needed by
+> > current kolab
+> > 
+> >    This need to be removed when upgrading to new version of kolab
+> 
+> Why are you using task-obsolete package for this, whereas you could
+> perfectly do it from kolab package directly ?
+
+I am not. I removed it. I still need the package.  JQ added it and I have no 
+idea why.
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018220.html b/zarb-ml/mageia-dev/2012-August/018220.html new file mode 100644 index 000000000..74a944642 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018220.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Anssi Hannula + anssi at mageia.org +
+ Sun Aug 19 21:07:48 CEST 2012 +

+
+ +
19.08.2012 21:58, tmb kirjoitti:
+> Name        : nvidia-current               Relocations: (not relocatable)
+> Version     : 304.37                            Vendor: Mageia.Org
+> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19 20:54:19 2012
+> Install Date: (not installed)               Build Host: ecosse.mageia.org
+> Group       : System/Kernel and hardware    Source RPM: (none)
+> Size        : 105048604                        License: Freeware
+> Signature   : (none)
+> Packager    : tmb <tmb>
+> URL         : http://www.nvidia.com/object/unix.html
+> Summary     : NVIDIA proprietary X.org driver and libraries, current driver series
+> Description :
+> Source package of the current NVIDIA proprietary driver. Binary
+> packages are named x11-driver-video-nvidia-current.
+> 
+> tmb <tmb> 304.37-2.mga3:
+> + Revision: 282319
+> - add provides kmod(nvidia-current) as upstream now has provides kmod(nvidis) (mga #7113)
+
+What?
+
+/usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+in dkms.conf.
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018221.html b/zarb-ml/mageia-dev/2012-August/018221.html new file mode 100644 index 000000000..dc097f6b1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018221.html @@ -0,0 +1,126 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Thomas Backlund + tmb at mageia.org +
+ Sun Aug 19 21:26:50 CEST 2012 +

+
+ +
Anssi Hannula skrev 19.8.2012 22:07:
+> 19.08.2012 21:58, tmb kirjoitti:
+>> Name        : nvidia-current               Relocations: (not relocatable)
+>> Version     : 304.37                            Vendor: Mageia.Org
+>> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19 20:54:19 2012
+>> Install Date: (not installed)               Build Host: ecosse.mageia.org
+>> Group       : System/Kernel and hardware    Source RPM: (none)
+>> Size        : 105048604                        License: Freeware
+>> Signature   : (none)
+>> Packager    : tmb <tmb>
+>> URL         : http://www.nvidia.com/object/unix.html
+>> Summary     : NVIDIA proprietary X.org driver and libraries, current driver series
+>> Description :
+>> Source package of the current NVIDIA proprietary driver. Binary
+>> packages are named x11-driver-video-nvidia-current.
+>>
+>> tmb <tmb> 304.37-2.mga3:
+>> + Revision: 282319
+>> - add provides kmod(nvidia-current) as upstream now has provides kmod(nvidis) (mga #7113)
+>
+> What?
+>
+> /usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+> in dkms.conf.
+>
+
+Thats just it:
+
+--- dkms.conf.295       2012-07-27 02:44:55.000000000 +0300
++++ dkms.conf.304       2012-08-19 03:32:59.000000000 +0300
+@@ -1,8 +1,7 @@
+-PACKAGE_NAME="nvidia-current"
+-PACKAGE_VERSION="295.59-2.mga3.nonfree"
+-BUILT_MODULE_NAME[0]="nvidia"
+-DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
+-DEST_MODULE_NAME[0]="nvidia-current"
+-MAKE[0]="make SYSSRC=${kernel_source_dir} module"
+-CLEAN="make -f Makefile.kbuild clean"
++PACKAGE_NAME="nvidia"
++PACKAGE_VERSION="304.37"
++BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
++DEST_MODULE_LOCATION[0]="/kernel/drivers/video"
++MAKE[0]="make module SYSSRC=${kernel_source_dir}"
++CLEAN="make clean"
+  AUTOINSTALL="yes"
+
+
+--
+
+Thomas
+
+
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018222.html b/zarb-ml/mageia-dev/2012-August/018222.html new file mode 100644 index 000000000..b7993b912 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018222.html @@ -0,0 +1,126 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Thomas Backlund + tmb at mageia.org +
+ Sun Aug 19 21:37:01 CEST 2012 +

+
+ +
Thomas Backlund skrev 19.8.2012 22:26:
+> Anssi Hannula skrev 19.8.2012 22:07:
+>> 19.08.2012 21:58, tmb kirjoitti:
+>>> Name        : nvidia-current               Relocations: (not
+>>> relocatable)
+>>> Version     : 304.37                            Vendor: Mageia.Org
+>>> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19
+
+
+>>> tmb <tmb> 304.37-2.mga3:
+>>> + Revision: 282319
+>>> - add provides kmod(nvidia-current) as upstream now has provides
+>>> kmod(nvidis) (mga #7113)
+>>
+>> What?
+>>
+>> /usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+>> in dkms.conf.
+>>
+>
+> Thats just it:
+>
+> --- dkms.conf.295       2012-07-27 02:44:55.000000000 +0300
+> +++ dkms.conf.304       2012-08-19 03:32:59.000000000 +0300
+> @@ -1,8 +1,7 @@
+> -PACKAGE_NAME="nvidia-current"
+> -PACKAGE_VERSION="295.59-2.mga3.nonfree"
+> -BUILT_MODULE_NAME[0]="nvidia"
+> -DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
+> -DEST_MODULE_NAME[0]="nvidia-current"
+> -MAKE[0]="make SYSSRC=${kernel_source_dir} module"
+> -CLEAN="make -f Makefile.kbuild clean"
+> +PACKAGE_NAME="nvidia"
+> +PACKAGE_VERSION="304.37"
+> +BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
+> +DEST_MODULE_LOCATION[0]="/kernel/drivers/video"
+> +MAKE[0]="make module SYSSRC=${kernel_source_dir}"
+> +CLEAN="make clean"
+>   AUTOINSTALL="yes"
+>
+
+Ah,
+I see nvidia is now providing their own kernel/dkms.conf in tarballs 
+wich gets used ...
+
+I guess we need to remove that one / install our own...
+
+
+--
+Thomas
+
+
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018223.html b/zarb-ml/mageia-dev/2012-August/018223.html new file mode 100644 index 000000000..617bd261a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018223.html @@ -0,0 +1,129 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Anssi Hannula + anssi at mageia.org +
+ Sun Aug 19 21:37:16 CEST 2012 +

+
+ +
19.08.2012 22:26, Thomas Backlund kirjoitti:
+> Anssi Hannula skrev 19.8.2012 22:07:
+>> 19.08.2012 21:58, tmb kirjoitti:
+>>> Name        : nvidia-current               Relocations: (not relocatable)
+>>> Version     : 304.37                            Vendor: Mageia.Org
+>>> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19 20:54:19 2012
+>>> Install Date: (not installed)               Build Host: ecosse.mageia.org
+>>> Group       : System/Kernel and hardware    Source RPM: (none)
+>>> Size        : 105048604                        License: Freeware
+>>> Signature   : (none)
+>>> Packager    : tmb <tmb>
+>>> URL         : http://www.nvidia.com/object/unix.html
+>>> Summary     : NVIDIA proprietary X.org driver and libraries, current driver series
+>>> Description :
+>>> Source package of the current NVIDIA proprietary driver. Binary
+>>> packages are named x11-driver-video-nvidia-current.
+>>>
+>>> tmb <tmb> 304.37-2.mga3:
+>>> + Revision: 282319
+>>> - add provides kmod(nvidia-current) as upstream now has provides kmod(nvidis) (mga #7113)
+>>
+>> What?
+>>
+>> /usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+>> in dkms.conf.
+>>
+> 
+> Thats just it:
+> 
+> --- dkms.conf.295       2012-07-27 02:44:55.000000000 +0300
+> +++ dkms.conf.304       2012-08-19 03:32:59.000000000 +0300
+> @@ -1,8 +1,7 @@
+> -PACKAGE_NAME="nvidia-current"
+> -PACKAGE_VERSION="295.59-2.mga3.nonfree"
+> -BUILT_MODULE_NAME[0]="nvidia"
+> -DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
+> -DEST_MODULE_NAME[0]="nvidia-current"
+> -MAKE[0]="make SYSSRC=${kernel_source_dir} module"
+> -CLEAN="make -f Makefile.kbuild clean"
+> +PACKAGE_NAME="nvidia"
+> +PACKAGE_VERSION="304.37"
+> +BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
+> +DEST_MODULE_LOCATION[0]="/kernel/drivers/video"
+> +MAKE[0]="make module SYSSRC=${kernel_source_dir}"
+> +CLEAN="make clean"
+>   AUTOINSTALL="yes"
+
+???
+
+dkms.conf is supposed to be our own file, the above change renames the
+module which would break our driver handling....
+
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018224.html b/zarb-ml/mageia-dev/2012-August/018224.html new file mode 100644 index 000000000..4d3f0f1b7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018224.html @@ -0,0 +1,132 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Thomas Backlund + tmb at mageia.org +
+ Sun Aug 19 21:45:33 CEST 2012 +

+
+ +
Thomas Backlund skrev 19.8.2012 22:37:
+> Thomas Backlund skrev 19.8.2012 22:26:
+>> Anssi Hannula skrev 19.8.2012 22:07:
+>>> 19.08.2012 21:58, tmb kirjoitti:
+>>>> Name        : nvidia-current               Relocations: (not
+>>>> relocatable)
+>>>> Version     : 304.37                            Vendor: Mageia.Org
+>>>> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19
+>
+>
+>>>> tmb <tmb> 304.37-2.mga3:
+>>>> + Revision: 282319
+>>>> - add provides kmod(nvidia-current) as upstream now has provides
+>>>> kmod(nvidis) (mga #7113)
+>>>
+>>> What?
+>>>
+>>> /usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+>>> in dkms.conf.
+>>>
+>>
+>> Thats just it:
+>>
+>> --- dkms.conf.295       2012-07-27 02:44:55.000000000 +0300
+>> +++ dkms.conf.304       2012-08-19 03:32:59.000000000 +0300
+>> @@ -1,8 +1,7 @@
+>> -PACKAGE_NAME="nvidia-current"
+>> -PACKAGE_VERSION="295.59-2.mga3.nonfree"
+>> -BUILT_MODULE_NAME[0]="nvidia"
+>> -DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
+>> -DEST_MODULE_NAME[0]="nvidia-current"
+>> -MAKE[0]="make SYSSRC=${kernel_source_dir} module"
+>> -CLEAN="make -f Makefile.kbuild clean"
+>> +PACKAGE_NAME="nvidia"
+>> +PACKAGE_VERSION="304.37"
+>> +BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
+>> +DEST_MODULE_LOCATION[0]="/kernel/drivers/video"
+>> +MAKE[0]="make module SYSSRC=${kernel_source_dir}"
+>> +CLEAN="make clean"
+>>   AUTOINSTALL="yes"
+>>
+>
+> Ah,
+> I see nvidia is now providing their own kernel/dkms.conf in tarballs
+> wich gets used ...
+>
+> I guess we need to remove that one / install our own...
+>
+
+And NVIDIA changelog :
+2012-07-13 version 304.22
+
+  * Added support for DKMS in nvidia-installer. Installing the kernel
+       module through DKMS allows the module to be rebuilt automatically
+       when changing to a different Linux kernel. See the README and the
+       nvidia-installer help text for the "--dkms" option.
+
+--
+Thomas
+
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018225.html b/zarb-ml/mageia-dev/2012-August/018225.html new file mode 100644 index 000000000..4828178a9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018225.html @@ -0,0 +1,136 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Thomas Backlund + tmb at mageia.org +
+ Sun Aug 19 22:15:20 CEST 2012 +

+
+ +
19.08.2012 22:37, Anssi Hannula skrev:
+> 19.08.2012 22:26, Thomas Backlund kirjoitti:
+>> Anssi Hannula skrev 19.8.2012 22:07:
+>>> 19.08.2012 21:58, tmb kirjoitti:
+>>>> Name        : nvidia-current               Relocations: (not relocatable)
+>>>> Version     : 304.37                            Vendor: Mageia.Org
+>>>> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19 20:54:19 2012
+>>>> Install Date: (not installed)               Build Host: ecosse.mageia.org
+>>>> Group       : System/Kernel and hardware    Source RPM: (none)
+>>>> Size        : 105048604                        License: Freeware
+>>>> Signature   : (none)
+>>>> Packager    : tmb <tmb>
+>>>> URL         : http://www.nvidia.com/object/unix.html
+>>>> Summary     : NVIDIA proprietary X.org driver and libraries, current driver series
+>>>> Description :
+>>>> Source package of the current NVIDIA proprietary driver. Binary
+>>>> packages are named x11-driver-video-nvidia-current.
+>>>>
+>>>> tmb <tmb> 304.37-2.mga3:
+>>>> + Revision: 282319
+>>>> - add provides kmod(nvidia-current) as upstream now has provides kmod(nvidis) (mga #7113)
+>>>
+>>> What?
+>>>
+>>> /usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+>>> in dkms.conf.
+>>>
+>>
+>> Thats just it:
+>>
+>> --- dkms.conf.295       2012-07-27 02:44:55.000000000 +0300
+>> +++ dkms.conf.304       2012-08-19 03:32:59.000000000 +0300
+>> @@ -1,8 +1,7 @@
+>> -PACKAGE_NAME="nvidia-current"
+>> -PACKAGE_VERSION="295.59-2.mga3.nonfree"
+>> -BUILT_MODULE_NAME[0]="nvidia"
+>> -DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
+>> -DEST_MODULE_NAME[0]="nvidia-current"
+>> -MAKE[0]="make SYSSRC=${kernel_source_dir} module"
+>> -CLEAN="make -f Makefile.kbuild clean"
+>> +PACKAGE_NAME="nvidia"
+>> +PACKAGE_VERSION="304.37"
+>> +BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
+>> +DEST_MODULE_LOCATION[0]="/kernel/drivers/video"
+>> +MAKE[0]="make module SYSSRC=${kernel_source_dir}"
+>> +CLEAN="make clean"
+>>    AUTOINSTALL="yes"
+>
+> ???
+>
+> dkms.conf is supposed to be our own file, the above change renames the
+> module which would break our driver handling....
+>
+>
+
+Yep.
+
+this is now properly fixed in nvidia-current-304.37-3.mga3 currently 
+building...
+
+--
+Thomas
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018226.html b/zarb-ml/mageia-dev/2012-August/018226.html new file mode 100644 index 000000000..985104cb0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018226.html @@ -0,0 +1,139 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Anssi Hannula + anssi at mageia.org +
+ Sun Aug 19 22:20:57 CEST 2012 +

+
+ +
19.08.2012 23:15, Thomas Backlund kirjoitti:
+> 19.08.2012 22:37, Anssi Hannula skrev:
+>> 19.08.2012 22:26, Thomas Backlund kirjoitti:
+>>> Anssi Hannula skrev 19.8.2012 22:07:
+>>>> 19.08.2012 21:58, tmb kirjoitti:
+>>>>> Name        : nvidia-current               Relocations: (not relocatable)
+>>>>> Version     : 304.37                            Vendor: Mageia.Org
+>>>>> Release     : 2.mga3.nonfree                Build Date: Sun Aug 19 20:54:19 2012
+>>>>> Install Date: (not installed)               Build Host: ecosse.mageia.org
+>>>>> Group       : System/Kernel and hardware    Source RPM: (none)
+>>>>> Size        : 105048604                        License: Freeware
+>>>>> Signature   : (none)
+>>>>> Packager    : tmb <tmb>
+>>>>> URL         : http://www.nvidia.com/object/unix.html
+>>>>> Summary     : NVIDIA proprietary X.org driver and libraries, current driver series
+>>>>> Description :
+>>>>> Source package of the current NVIDIA proprietary driver. Binary
+>>>>> packages are named x11-driver-video-nvidia-current.
+>>>>>
+>>>>> tmb <tmb> 304.37-2.mga3:
+>>>>> + Revision: 282319
+>>>>> - add provides kmod(nvidia-current) as upstream now has provides kmod(nvidis) (mga #7113)
+>>>>
+>>>> What?
+>>>>
+>>>> /usr/lib/rpm/mageia/kmod.prov should extract this from DEST_MODULE_NAME
+>>>> in dkms.conf.
+>>>>
+>>>
+>>> Thats just it:
+>>>
+>>> --- dkms.conf.295       2012-07-27 02:44:55.000000000 +0300
+>>> +++ dkms.conf.304       2012-08-19 03:32:59.000000000 +0300
+>>> @@ -1,8 +1,7 @@
+>>> -PACKAGE_NAME="nvidia-current"
+>>> -PACKAGE_VERSION="295.59-2.mga3.nonfree"
+>>> -BUILT_MODULE_NAME[0]="nvidia"
+>>> -DEST_MODULE_LOCATION[0]="/kernel/drivers/char/drm"
+>>> -DEST_MODULE_NAME[0]="nvidia-current"
+>>> -MAKE[0]="make SYSSRC=${kernel_source_dir} module"
+>>> -CLEAN="make -f Makefile.kbuild clean"
+>>> +PACKAGE_NAME="nvidia"
+>>> +PACKAGE_VERSION="304.37"
+>>> +BUILT_MODULE_NAME[0]="$PACKAGE_NAME"
+>>> +DEST_MODULE_LOCATION[0]="/kernel/drivers/video"
+>>> +MAKE[0]="make module SYSSRC=${kernel_source_dir}"
+>>> +CLEAN="make clean"
+>>>    AUTOINSTALL="yes"
+>>
+>> ???
+>>
+>> dkms.conf is supposed to be our own file, the above change renames the
+>> module which would break our driver handling....
+>>
+>>
+> 
+> Yep.
+> 
+> this is now properly fixed in nvidia-current-304.37-3.mga3 currently 
+> building...
+
+OK, thanks.
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018227.html b/zarb-ml/mageia-dev/2012-August/018227.html new file mode 100644 index 000000000..0c233c335 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018227.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release poppler-0.20.3-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release poppler-0.20.3-1.mga3

+ Charles A Edwards + CAE at eslrahc.com +
+ Sun Aug 19 23:10:53 CEST 2012 +

+
+ +
On Sun, 19 Aug 2012 22:56:31 +0200 (CEST)
+luigiwalser wrote:
+
+> luigiwalser <luigiwalser> 0.20.3-1.mga3:
+> + Revision: 282379
+> - 0.20.3
+> - remove upstream patches
+
+
+Why is the change in major not noted?
+
+
+    Charles
+
+
+-- 
+A fool's brain digests philosophy into folly, science into
+superstition, and art into pedantry.  Hence University education.
+		-- G. B. Shaw
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.2-tmb-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120819/69cd8e1a/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018228.html b/zarb-ml/mageia-dev/2012-August/018228.html new file mode 100644 index 000000000..11daf3372 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018228.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release poppler-0.20.3-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release poppler-0.20.3-1.mga3

+ David Walser + luigiwalser at yahoo.com +
+ Sun Aug 19 23:33:18 CEST 2012 +

+
+ +
Charles A Edwards wrote:
+> On Sun, 19 Aug 2012 22:56:31 +0200 (CEST)
+> luigiwalser wrote:
+> 
+>> luigiwalser <luigiwalser> 0.20.3-1.mga3:
+>> + Revision: 282379
+>> - 0.20.3
+>> - remove upstream patches
+> 
+> 
+> Why is the change in major not noted?
+
+You just noted it, so now it is.
+
+All jokes aside, it's certainly not a bad idea to mention it, but there's no convention to do that, and I only see once in the SVN log for this 
+package in particular that it's been noted, even though it's changed multiple times.  If we want more consistency on that, I guess someone 
+could propose it as a policy.
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018229.html b/zarb-ml/mageia-dev/2012-August/018229.html new file mode 100644 index 000000000..2275be03e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018229.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Samuel Verschelde + stormi at laposte.net +
+ Mon Aug 20 09:41:19 CEST 2012 +

+
+ +
Le dimanche 19 août 2012 23:15:20 Thomas Backlund a écrit :
+> this is now properly fixed in nvidia-current-304.37-3.mga3 currently
+> building...
+> 
+
+Will there be an updated package for mga2 too?
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018230.html b/zarb-ml/mageia-dev/2012-August/018230.html new file mode 100644 index 000000000..c63c32610 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018230.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Upgrade of Kolab to 3.0 Alpha + + + + + + + + + +

[Mageia-dev] Upgrade of Kolab to 3.0 Alpha

+ Olav Vitters + olav at vitters.nl +
+ Mon Aug 20 11:36:45 CEST 2012 +

+
+ +
On Thu, Aug 16, 2012 at 09:01:27PM -0700, Thomas Spuhler wrote:
+> I am starting to upgrade Kolab to 3 Alpha. It will break a lot.
+
+Mageia is one of the few distributions shipping evolution-kolab (thanks
+to taking the package from Mandriva). I don't expect much development
+to support an alpha release in GNOME 3.5.x or 3.6.
+
+So be aware you might break this package and might take a while before
+it works.
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018231.html b/zarb-ml/mageia-dev/2012-August/018231.html new file mode 100644 index 000000000..ba660f275 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018231.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release flrig-1.3.07-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release flrig-1.3.07-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 20 18:55:37 CEST 2012 +

+
+ +
On 17 August 2012 10:03, shlomif <buildsystem-daemon at mageia.org> wrote:
+> Description :
+> Flrig is a transceiver control program designed to be used either stand
+> alone or as an adjunct to fldigi. The user interface changes to accommodate
+> the degree of CAT support available for the transceiver in use.
+> The back end control code for each transceiver is unique to flrig.
+> No additional libraries or definition files are required.
+>
+> Authors:
+> --------
+> W1HKJ - w1hkj at w1hkj.com
+
+%description != AUTHORS file
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018232.html b/zarb-ml/mageia-dev/2012-August/018232.html new file mode 100644 index 000000000..522b57dea --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018232.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 20 20:49:05 CEST 2012 +

+
+ +
Here are several packages candidate for removal:
+
+- apache-mod_python: doesn't build with apache 2.4, unmaintained 
+upstream, dropped from fedora, no response from current maintainer 
+(https://bugs.mageia.org/show_bug.cgi?id=7024)
+
+- apache-mod_ruby: doesn't build with apache 2.4, unmaintained upstream
+
+- ocsinventory-server and ocsinventory-agent: unmaintained, several 
+pending security updates, better alternatives available (glpi + 
+fusioninventory-agent)
+
+- madwifi-sources: no maintainer, no binaries available in the 
+distribution, considered as deprecated
+
+Unless someone step it to fix pending issues, those packages should 
+better get dropped.
+-- 
+BOFH excuse #180:
+
+ether leak
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018233.html b/zarb-ml/mageia-dev/2012-August/018233.html new file mode 100644 index 000000000..1adc45721 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018233.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 20 21:15:50 CEST 2012 +

+
+ +
Guillaume Rousse <guillomovitch at ...> writes:
+> Here are several packages candidate for removal:
+> - apache-mod_python
+> - apache-mod_ruby
+> - ocsinventory-server and ocsinventory-agent
+> - madwifi-sources
+
+Agreed, and there are surely other unmaintained packages that lack sufficient
+need or interest to stay and should be dropped as well.
+
+Furthermore, what is the procedure for dropping a package?  The wicd package is
+broken and has unpatched security vulnerabilities[1].  It was previously asked
+on this list if it should be dropped, nobody objected, a bug was filed asking
+to drop it an assigned to sysadmin-bugs at ml.mageia.org [2], but it hasn't been
+dropped as far as I know.
+
+[1] - https://bugs.mageia.org/show_bug.cgi?id=5608
+[2] - https://bugs.mageia.org/show_bug.cgi?id=5926
+
+Some other candidates for removal that come to mind:
+
+abrt/libreport/btparser - tool for sending bug reports to RedHat, does not seem
+  to belong in Mageia, our drakxtools have their own tool for sending crash
+  reports to our bugzilla, unpatched security issues.
+  https://bugs.mageia.org/show_bug.cgi?id=6523
+
+sos - another RedHat-specific thing, unpatched security issues.
+  https://bugs.mageia.org/show_bug.cgi?id=6525
+
+libgnomesu - really old and unmaintained upstream, unpatched security issues,
+  probably not needed.
+  https://bugs.mageia.org/show_bug.cgi?id=7068
+
+I'm sure there are plenty of other good candidates.
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018234.html b/zarb-ml/mageia-dev/2012-August/018234.html new file mode 100644 index 000000000..cca90accd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018234.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Antoine Pitrou + solipsis at pitrou.net +
+ Mon Aug 20 21:14:57 CEST 2012 +

+
+ +
On Mon, 20 Aug 2012 20:49:05 +0200
+Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Here are several packages candidate for removal:
+> 
+> - apache-mod_python: doesn't build with apache 2.4, unmaintained 
+> upstream, dropped from fedora, no response from current maintainer 
+> (https://bugs.mageia.org/show_bug.cgi?id=7024)
+
+Nobody uses mod_python anymore, mod_wsgi has been the official
+superseder for years.
+
+Regards
+
+Antoine.
+
+
+-- 
+Software development and contracting: http://pro.pitrou.net
+
+
+
+ + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018235.html b/zarb-ml/mageia-dev/2012-August/018235.html new file mode 100644 index 000000000..76381b424 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018235.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Damien Lallement + mageia at damsweb.net +
+ Mon Aug 20 21:20:09 CEST 2012 +

+
+ +
Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+> Here are several packages candidate for removal:
+>
+> [...]
+>
+> - ocsinventory-server and ocsinventory-agent: unmaintained, several
+> pending security updates, better alternatives available (glpi +
+> fusioninventory-agent)
+
+Noooooo, I'm using it for a customer of my company.
+I think that it's hard to remove this package as glpi/funsioninventory 
+are better alternatives, sure, but not compatible with ocsinventory-*.
+So, for me, it's not an alternative but an other solution.
+
+> [...]
+
+My 2cts
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018236.html b/zarb-ml/mageia-dev/2012-August/018236.html new file mode 100644 index 000000000..c278e8089 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018236.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Mon Aug 20 22:17:20 CEST 2012 +

+
+ +
Le 20/08/2012 21:20, Damien Lallement a écrit :
+> Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+>> Here are several packages candidate for removal:
+>>
+>> [...]
+>>
+>> - ocsinventory-server and ocsinventory-agent: unmaintained, several
+>> pending security updates, better alternatives available (glpi +
+>> fusioninventory-agent)
+>
+> Noooooo, I'm using it for a customer of my company.
+> I think that it's hard to remove this package as glpi/funsioninventory
+> are better alternatives, sure, but not compatible with ocsinventory-*.
+> So, for me, it's not an alternative but an other solution.
+Meaning you're volonteering for maintainership ?
+-- 
+BOFH excuse #233:
+
+TCP/IP UDP alarm threshold is set too low.
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018237.html b/zarb-ml/mageia-dev/2012-August/018237.html new file mode 100644 index 000000000..f977fe7ba --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018237.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Damien Lallement + mageia at damsweb.net +
+ Mon Aug 20 22:24:32 CEST 2012 +

+
+ +
Le 20/08/2012 22:17, Guillaume Rousse a écrit :
+> Le 20/08/2012 21:20, Damien Lallement a écrit :
+>> Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+>>> Here are several packages candidate for removal:
+>>>
+>>> [...]
+>>>
+>>> - ocsinventory-server and ocsinventory-agent: unmaintained, several
+>>> pending security updates, better alternatives available (glpi +
+>>> fusioninventory-agent)
+>>
+>> Noooooo, I'm using it for a customer of my company.
+>> I think that it's hard to remove this package as glpi/funsioninventory
+>> are better alternatives, sure, but not compatible with ocsinventory-*.
+>> So, for me, it's not an alternative but an other solution.
+> Meaning you're volonteering for maintainership ?
+
+If I don't have any choice, I am.
+/me hides :-)
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018238.html b/zarb-ml/mageia-dev/2012-August/018238.html new file mode 100644 index 000000000..be02f2a12 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018238.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ David Walser + luigiwalser at yahoo.com +
+ Mon Aug 20 22:56:15 CEST 2012 +

+
+ +
Damien Lallement <mageia at ...> writes:
+> Le 20/08/2012 22:17, Guillaume Rousse a écrit :
+> > Meaning you're volonteering for maintainership ?
+> 
+> If I don't have any choice, I am.
+> /me hides 
+
+Thanks Damien.  Here you go.
+https://bugs.mageia.org/show_bug.cgi?id=5252
+https://bugs.mageia.org/show_bug.cgi?id=2129
+
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018239.html b/zarb-ml/mageia-dev/2012-August/018239.html new file mode 100644 index 000000000..6ab827b59 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018239.html @@ -0,0 +1,120 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Manuel Hiebel + manuel.mageia at hiebel.eu +
+ Mon Aug 20 23:02:51 CEST 2012 +

+
+ +
Le 2012-08-20 21:15, David Walser a écrit :
+> Guillaume Rousse <guillomovitch at ...> writes:
+>> Here are several packages candidate for removal:
+>> - apache-mod_python
+>> - apache-mod_ruby
+>> - ocsinventory-server and ocsinventory-agent
+>> - madwifi-sources
+>
+> Agreed, and there are surely other unmaintained packages that lack 
+> sufficient
+> need or interest to stay and should be dropped as well.
+>
+> Furthermore, what is the procedure for dropping a package?  The wicd
+> package is
+> broken and has unpatched security vulnerabilities[1].  It was
+> previously asked
+> on this list if it should be dropped, nobody objected, a bug was 
+> filed asking
+> to drop it an assigned to sysadmin-bugs at ml.mageia.org [2], but it 
+> hasn't been
+> dropped as far as I know.
+>
+> [1] - https://bugs.mageia.org/show_bug.cgi?id=5608
+> [2] - https://bugs.mageia.org/show_bug.cgi?id=5926
+>
+> Some other candidates for removal that come to mind:
+>
+> abrt/libreport/btparser - tool for sending bug reports to RedHat,
+> does not seem
+>   to belong in Mageia, our drakxtools have their own tool for sending 
+> crash
+>   reports to our bugzilla, unpatched security issues.
+>   https://bugs.mageia.org/show_bug.cgi?id=6523
+>
+> sos - another RedHat-specific thing, unpatched security issues.
+>   https://bugs.mageia.org/show_bug.cgi?id=6525
+>
+> libgnomesu - really old and unmaintained upstream, unpatched security 
+> issues,
+>   probably not needed.
+>   https://bugs.mageia.org/show_bug.cgi?id=7068
+>
+> I'm sure there are plenty of other good candidates.
+
+Some months ago, we were speaking of removing all unmainted packages, I 
+guess this out of brain nowadays ?
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018240.html b/zarb-ml/mageia-dev/2012-August/018240.html new file mode 100644 index 000000000..ac3757020 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018240.html @@ -0,0 +1,93 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Damien Lallement + mageia at damsweb.net +
+ Mon Aug 20 23:10:50 CEST 2012 +

+
+ +
Le 20/08/2012 22:56, David Walser a écrit :
+> Damien Lallement <mageia at ...> writes:
+>> Le 20/08/2012 22:17, Guillaume Rousse a écrit :
+>>> Meaning you're volonteering for maintainership ?
+>>
+>> If I don't have any choice, I am.
+>> /me hides
+>
+> Thanks Damien.  Here you go.
+> https://bugs.mageia.org/show_bug.cgi?id=5252
+> https://bugs.mageia.org/show_bug.cgi?id=2129
+
+Amazing but on my side, I'm not happy enough to thank you. ;-)
+
+
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018241.html b/zarb-ml/mageia-dev/2012-August/018241.html new file mode 100644 index 000000000..054617f5c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018241.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ David Walser + luigiwalser at yahoo.com +
+ Tue Aug 21 02:20:39 CEST 2012 +

+
+ +
Manuel Hiebel wrote:
+> Some months ago, we were speaking of removing all unmainted packages, I 
+> guess this out of brain nowadays ?
+
+Well, we don't need to get too carried away :o)
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018242.html b/zarb-ml/mageia-dev/2012-August/018242.html new file mode 100644 index 000000000..e643b140e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018242.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Juan Luis Baptiste + juancho at mageia.org +
+ Tue Aug 21 02:44:54 CEST 2012 +

+
+ +
On Mon, Aug 20, 2012 at 3:17 PM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 20/08/2012 21:20, Damien Lallement a écrit :
+>>> - ocsinventory-server and ocsinventory-agent: unmaintained, several
+>>> pending security updates, better alternatives available (glpi +
+>>> fusioninventory-agent)
+>>
+>>
+>> Noooooo, I'm using it for a customer of my company.
+>> I think that it's hard to remove this package as glpi/funsioninventory
+>> are better alternatives, sure, but not compatible with ocsinventory-*.
+>> So, for me, it's not an alternative but an other solution.
+>
+> Meaning you're volonteering for maintainership ?
+
+We're working on these two packages with one of my apprentices, so
+there's no need to drop them.
+
+Cheers,
+
+-- 
+Juancho
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018243.html b/zarb-ml/mageia-dev/2012-August/018243.html new file mode 100644 index 000000000..2ffad898a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018243.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron nonfree/release nvidia-current-304.37-2.mga3.nonfree

+ Thomas Backlund + tmb at mageia.org +
+ Tue Aug 21 08:27:52 CEST 2012 +

+
+ +
Samuel Verschelde skrev 20.8.2012 10:41:
+> Le dimanche 19 août 2012 23:15:20 Thomas Backlund a écrit :
+>> this is now properly fixed in nvidia-current-304.37-3.mga3 currently
+>> building...
+>>
+>
+> Will there be an updated package for mga2 too?
+>
+
+Nope.
+
+Atleast not for now.
+
+The 295.71 currently in updates_testing does not have this problem,
+as the breakage happend only with 304.37.
+
+--
+Thomas
+
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018244.html b/zarb-ml/mageia-dev/2012-August/018244.html new file mode 100644 index 000000000..246f88502 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018244.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Tue Aug 21 09:20:25 CEST 2012 +

+
+ +
Le 21/08/2012 02:44, Juan Luis Baptiste a écrit :
+> On Mon, Aug 20, 2012 at 3:17 PM, Guillaume Rousse
+> <guillomovitch at gmail.com> wrote:
+>> Le 20/08/2012 21:20, Damien Lallement a écrit :
+>>>> - ocsinventory-server and ocsinventory-agent: unmaintained, several
+>>>> pending security updates, better alternatives available (glpi +
+>>>> fusioninventory-agent)
+>>>
+>>>
+>>> Noooooo, I'm using it for a customer of my company.
+>>> I think that it's hard to remove this package as glpi/funsioninventory
+>>> are better alternatives, sure, but not compatible with ocsinventory-*.
+>>> So, for me, it's not an alternative but an other solution.
+>>
+>> Meaning you're volonteering for maintainership ?
+>
+> We're working on these two packages with one of my apprentices, so
+> there's no need to drop them.
+So just take over maintainership. "we're working on it" is not a clear 
+status.
+
+-- 
+BOFH excuse #61:
+
+not approved by the FCC
+
+ + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018245.html b/zarb-ml/mageia-dev/2012-August/018245.html new file mode 100644 index 000000000..a47dd3c58 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018245.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] itstool vs gnome-doc-utils + + + + + + + + + +

[Mageia-dev] itstool vs gnome-doc-utils

+ Olav Vitters + olav at vitters.nl +
+ Tue Aug 21 12:33:33 CEST 2012 +

+
+ +
FYI,
+
+In case a GNOME package suddenly requires itstool, then normally:
+- gnome-doc-utils buildrequire can be dropped
+- %find_lang should have --with-help
+- remove the omf stuff
+
+This is not a golden rule. I normally submit the package multiple times.
+And usually forget to drop the gnome-doc-utils br...
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018246.html b/zarb-ml/mageia-dev/2012-August/018246.html new file mode 100644 index 000000000..f795adaf9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018246.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Bersuit Vera + bersuit.cooker at gmail.com +
+ Tue Aug 21 13:21:41 CEST 2012 +

+
+ +
Hi
+The agent is ready and the server will be asap.
+I'm a eager rookie and so I'll do my best, but bare in mind that I'm just a
+rookie that juancho decides
+
+Salut Bersuit.
+
+2012/8/21 Guillaume Rousse <guillomovitch at gmail.com>
+
+> Le 21/08/2012 02:44, Juan Luis Baptiste a écrit :
+>
+>  On Mon, Aug 20, 2012 at 3:17 PM, Guillaume Rousse
+>> <guillomovitch at gmail.com> wrote:
+>>
+>>> Le 20/08/2012 21:20, Damien Lallement a écrit :
+>>>
+>>>> - ocsinventory-server and ocsinventory-agent: unmaintained, several
+>>>>> pending security updates, better alternatives available (glpi +
+>>>>> fusioninventory-agent)
+>>>>>
+>>>>
+>>>>
+>>>> Noooooo, I'm using it for a customer of my company.
+>>>> I think that it's hard to remove this package as glpi/funsioninventory
+>>>> are better alternatives, sure, but not compatible with ocsinventory-*.
+>>>> So, for me, it's not an alternative but an other solution.
+>>>>
+>>>
+>>> Meaning you're volonteering for maintainership ?
+>>>
+>>
+>> We're working on these two packages with one of my apprentices, so
+>> there's no need to drop them.
+>>
+> So just take over maintainership. "we're working on it" is not a clear
+> status.
+>
+> --
+> BOFH excuse #61:
+>
+> not approved by the FCC
+>
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120821/60ff1aab/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018247.html b/zarb-ml/mageia-dev/2012-August/018247.html new file mode 100644 index 000000000..a924f9b0e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018247.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] itstool vs gnome-doc-utils + + + + + + + + + +

[Mageia-dev] itstool vs gnome-doc-utils

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 21 14:37:31 CEST 2012 +

+
+ +
On 21 August 2012 12:33, Olav Vitters <olav at vitters.nl> wrote:
+> FYI,
+>
+> In case a GNOME package suddenly requires itstool, then normally:
+> - gnome-doc-utils buildrequire can be dropped
+> - %find_lang should have --with-help
+> - remove the omf stuff
+>
+> This is not a golden rule. I normally submit the package multiple times.
+> And usually forget to drop the gnome-doc-utils br...
+
+Then evince needs that treatment.
+I only added the new BR.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018248.html b/zarb-ml/mageia-dev/2012-August/018248.html new file mode 100644 index 000000000..6a2770975 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018248.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] itstool vs gnome-doc-utils + + + + + + + + + +

[Mageia-dev] itstool vs gnome-doc-utils

+ Olav Vitters + olav at vitters.nl +
+ Tue Aug 21 14:50:53 CEST 2012 +

+
+ +
On Tue, Aug 21, 2012 at 02:37:31PM +0200, Thierry Vignaud wrote:
+> Then evince needs that treatment.
+> I only added the new BR.
+
+I (someone:) need to fix load of packages. I did fix the --with-help
+(otherwise there are unpackaged files)
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018249.html b/zarb-ml/mageia-dev/2012-August/018249.html new file mode 100644 index 000000000..97c6fd54a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018249.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] no mouse in cauldron boot.iso + + + + + + + + + +

[Mageia-dev] no mouse in cauldron boot.iso

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 21 14:54:55 CEST 2012 +

+
+ +
On 15 August 2012 19:28, eatdirt <dirteat at gmail.com> wrote:
+> I know it is very early to test the installer;
+
+It's not. Installer is kept workable at any time.
+It may be temporary broken on rebuild due to other packages changes
+but that got fixed pretty fast.
+
+> but after screwing up the
+> /usr migration I reinstalled cauldron from thye current boot.iso; which was
+> not finding any mouse on my machine.
+
+Can you check if mga2 installer was OK on your machine?
+
+> Let me know if you want me to open a bug report.
+
+Looks like latest rebuild broke sg
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018250.html b/zarb-ml/mageia-dev/2012-August/018250.html new file mode 100644 index 000000000..147b11084 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018250.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 21 14:56:13 CEST 2012 +

+
+ +
On 20 August 2012 21:15, David Walser <luigiwalser at yahoo.com> wrote:
+> abrt/libreport/btparser - tool for sending bug reports to RedHat, does not seem
+>   to belong in Mageia, our drakxtools have their own tool for sending crash
+>   reports to our bugzilla, unpatched security issues.
+>   https://bugs.mageia.org/show_bug.cgi?id=6523
+
+These actually help me to catch some segfault in some gnome packages
+from times to times.
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018251.html b/zarb-ml/mageia-dev/2012-August/018251.html new file mode 100644 index 000000000..26b717c74 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018251.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Juan Luis Baptiste + juancho at mageia.org +
+ Tue Aug 21 16:14:39 CEST 2012 +

+
+ +
On Tue, Aug 21, 2012 at 2:20 AM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+>>
+>> We're working on these two packages with one of my apprentices, so
+>> there's no need to drop them.
+>
+> So just take over maintainership. "we're working on it" is not a clear
+> status.
+>
+
+Done.
+
+
+-- 
+Juancho
+
+ + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018252.html b/zarb-ml/mageia-dev/2012-August/018252.html new file mode 100644 index 000000000..3b7fd5a06 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018252.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Wed Aug 22 08:13:59 CEST 2012 +

+
+ +
在 Thu, 16 Aug 2012 18:31:30 +0800, Kira <elegant.pegasus at gmail.com>寫道:
+
+> 在 Thu, 16 Aug 2012 18:21:47 +0800, andre999  
+> <andre999mga at laposte.net>寫道:
+>>>
+>> I use gnome (thus gdm), and dpms is off on my system as well. and I  
+>> have a similar problem from time to time (almost every day).
+>> I found a workaround by chance : if I click the mouse several times  
+>> when this happens, then the screen turns on after a few seconds, and  
+>> everything is still running.  Otherwise I have to reboot to get my  
+>> display back.
+>> I also use the ati driver and not fglrx, and leave my system on most of  
+>> the time.
+>> So maybe try this workaround ?
+>>
+> I had tried it before, but it just died.....
+I had tried 4 different kinds of flavor kernels(mga/tmb X desktop/Server)
+
+None of them work! Anyone please help me?
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018253.html b/zarb-ml/mageia-dev/2012-August/018253.html new file mode 100644 index 000000000..a4e45fac9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018253.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 22 11:35:32 CEST 2012 +

+
+ +
On 22 August 2012 08:13, Kira <elegant.pegasus at gmail.com> wrote:
+>>> I use gnome (thus gdm), and dpms is off on my system as well. and I have
+>>> a similar problem from time to time (almost every day).
+>>> I found a workaround by chance : if I click the mouse several times when
+>>> this happens, then the screen turns on after a few seconds, and everything
+>>> is still running.  Otherwise I have to reboot to get my display back.
+>>> I also use the ati driver and not fglrx, and leave my system on most of
+>>> the time.
+>>> So maybe try this workaround ?
+>>>
+>> I had tried it before, but it just died.....
+>
+> I had tried 4 different kinds of flavor kernels(mga/tmb X desktop/Server)
+>
+> None of them work! Anyone please help me?
+
+telling what is your graphic card, if you're using proprietary driver or not,
+providin /var/log/Xorg.0.log.old ... could help
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018254.html b/zarb-ml/mageia-dev/2012-August/018254.html new file mode 100644 index 000000000..06f886b36 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018254.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Wed Aug 22 11:48:54 CEST 2012 +

+
+ +
在 Wed, 22 Aug 2012 17:35:32 +0800, Thierry Vignaud  
+<thierry.vignaud at gmail.com>寫道:
+>
+> telling what is your graphic card, if you're using proprietary driver or  
+> not,
+> providin /var/log/Xorg.0.log.old ... could help
+I had tried with proprietary, but it even won't boot in(Should be another  
+bug)
+
+I am using the open source driver now, attachment is the log
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: Xorg.0.log
+Type: application/octet-stream
+Size: 37689 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120822/346f33df/attachment-0001.obj>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018255.html b/zarb-ml/mageia-dev/2012-August/018255.html new file mode 100644 index 000000000..4e5c6e4e8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018255.html @@ -0,0 +1,109 @@ + + + + [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text + + + + + + + + + +

[Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text

+ Marja van Waes + marja11 at xs4all.nl +
+ Wed Aug 22 12:57:43 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+Hi all,
+
+About a help text for drakx-installer-stage2:
+
+Can someone please help documentation team with a good help text for
+the help button for the "Add or Modify a Boot Menu Entry" screen, so
+for the pop up screen you see in the second screenshot here (the one
+that pops up on top of the Bootloader Configuration screen)
+http://docteam.mageia.nl/installer/content/setupBootloaderAddEntry.html
+
+Thanks :)
+marja
+
+
+
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iQEcBAEBAgAGBQJQNLshAAoJEKWubDMI5nEBRyAH/1bVBLnpI083ds611ay1T6af
+17KYMf46zzeROnwI+KhZQ/ikoVhSVeeaIiBV8YP5XZpcKnxOc0nf6/kId5E2h3zk
++W9JRHkGCQ0wTdZRq5DVH0VAlHMSCKZUcLu+qN5hgoKWzr0ebajyBV6P3kesZXUk
+166gPMz808nbvDC3eTF6/U8X1olvY1JCCdEctSJndgke2ufWTCd9X/ot51GSCo12
+EDTPmHgTvtU3UYi1EiTesDBbYduIyHyx2pSxr9w0aicfuyrigfAPtQmNVigVeY+2
+hCwBfeI/oZRVTSBg7yEE4hxyPl5w5imSXqy2RvTfe7e9WixnKI77Hd3HrAhI4kk=
+=d9KH
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018256.html b/zarb-ml/mageia-dev/2012-August/018256.html new file mode 100644 index 000000000..678ed8f3b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018256.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] no mouse in cauldron boot.iso + + + + + + + + + +

[Mageia-dev] no mouse in cauldron boot.iso

+ EatDirt + dirteat at gmail.com +
+ Wed Aug 22 15:19:29 CEST 2012 +

+
+ +
On 21/08/12 14:54, Thierry Vignaud wrote:
+> On 15 August 2012 19:28, eatdirt<dirteat at gmail.com>  wrote:
+>
+> Can you check if mga2 installer was OK on your machine?
+
+Yep it works fine actually ! The mouse is found.
+
+Cheers,
+Chris.
+
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018257.html b/zarb-ml/mageia-dev/2012-August/018257.html new file mode 100644 index 000000000..550984d72 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018257.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text + + + + + + + + + +

[Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Aug 22 16:29:19 CEST 2012 +

+
+ +
On Wed, Aug 22, 2012 at 11:57 AM, Marja van Waes <marja11 at xs4all.nl> wrote:
+> Hi all,
+>
+> About a help text for drakx-installer-stage2:
+>
+> Can someone please help documentation team with a good help text for
+> the help button for the "Add or Modify a Boot Menu Entry" screen, so
+> for the pop up screen you see in the second screenshot here (the one
+> that pops up on top of the Bootloader Configuration screen)
+> http://docteam.mageia.nl/installer/content/setupBootloaderAddEntry.html
+
+What is the expected kind of text? ( I have never read the help :) )
+An explanation of the different fields?
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018258.html b/zarb-ml/mageia-dev/2012-August/018258.html new file mode 100644 index 000000000..f08f4d353 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018258.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] Tonight's meeting + + + + + + + + + +

[Mageia-dev] Tonight's meeting

+ Anne Nicolas + ennael1 at gmail.com +
+ Wed Aug 22 16:52:23 CEST 2012 +

+
+ +
Hi there
+
+We will have a meeting tonight as usual at 19h UTC. Here are the 
+proposed topics:
+
+- Coming Mageia 3 alpha 1 release
+- kernel support for Mageia 2
+- mentoring review + siplew account
+
+As usual feel free to add another one
+
+Cheers
+
+-- 
+Anne
+http://mageia.org
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018259.html b/zarb-ml/mageia-dev/2012-August/018259.html new file mode 100644 index 000000000..59c36cc2e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018259.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] Tonight's meeting + + + + + + + + + +

[Mageia-dev] Tonight's meeting

+ Sander Lepik + sander.lepik at eesti.ee +
+ Wed Aug 22 17:21:47 CEST 2012 +

+
+ +
On Aug 22, 2012 5:52 PM, "Anne Nicolas" <ennael1 at gmail.com> wrote:
+>
+> Hi there
+>
+> We will have a meeting tonight as usual at 19h UTC. Here are the proposed
+topics:
+>
+> - Coming Mageia 3 alpha 1 release
+> - kernel support for Mageia 2
+> - mentoring review + siplew account
+>
+> As usual feel free to add another one
+
+I would add all the open questions that are holding back mass rebuild. :)
+
+--
+Sander
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120822/ea54be17/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018260.html b/zarb-ml/mageia-dev/2012-August/018260.html new file mode 100644 index 000000000..5a89e4e33 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018260.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] Tonight's meeting + + + + + + + + + +

[Mageia-dev] Tonight's meeting

+ Pierre-Malo Deniélou + pierre-malo.denielou at rhul.ac.uk +
+ Wed Aug 22 18:30:06 CEST 2012 +

+
+ +
On 22/08/12 15:52, Anne Nicolas wrote:
+> Hi there
+>
+> We will have a meeting tonight as usual at 19h UTC. Here are the
+> proposed topics:
+>
+> - Coming Mageia 3 alpha 1 release
+> - kernel support for Mageia 2
+> - mentoring review + siplew account
+>
+> As usual feel free to add another one
+>
+> Cheers
+
+Sorry, I can't attend tonight. I have very reduced internet access these 
+days. I'll be more involved from next week on.
+
+Cheers,
+-- 
+Malo
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018261.html b/zarb-ml/mageia-dev/2012-August/018261.html new file mode 100644 index 000000000..20001fe8b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018261.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] HELP! Evolution Seriously Broken since latest updates!!! + + + + + + + + + +

[Mageia-dev] HELP! Evolution Seriously Broken since latest updates!!!

+ List Lister + list at foxconsult.net +
+ Wed Aug 22 20:52:10 CEST 2012 +

+
+ +
[rfox at ThinkFox ~]$ evolution
+GLib (gthread-posix.c): Unexpected error from C library during
+'pthread_mutex_lock': Invalid argument.  Aborting.
+Aborted
+
+
+[rfox at ThinkFox ~]$ rpm -qa | grep evolution
+evolution-data-server-3.5.90-2.mga3
+evolution-3.5.5.1-1.mga3
+nautilus-sendto-evolution-3.5.3-1.mga3
+evolution-webcal-2.32.0-4.mga2
+
+Won't start at all- what can I do??
+
+Thx,
+R.Fox
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120822/95dc47a6/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018262.html b/zarb-ml/mageia-dev/2012-August/018262.html new file mode 100644 index 000000000..2d3401317 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018262.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] HELP! Evolution Seriously Broken since latest updates!!! + + + + + + + + + +

[Mageia-dev] HELP! Evolution Seriously Broken since latest updates!!!

+ Funda Wang + fundawang at gmail.com +
+ Thu Aug 23 06:24:11 CEST 2012 +

+
+ +
Does it work better with latest evolution?
+
+在 2012年8月23日星期四，List Lister <list at foxconsult.net> 写道：
+> [rfox at ThinkFox ~]$ evolution
+> GLib (gthread-posix.c): Unexpected error from C library during
+'pthread_mutex_lock': Invalid argument.  Aborting.
+> Aborted
+>
+> [rfox at ThinkFox ~]$ rpm -qa | grep evolution
+> evolution-data-server-3.5.90-2.mga3
+> evolution-3.5.5.1-1.mga3
+> nautilus-sendto-evolution-3.5.3-1.mga3
+> evolution-webcal-2.32.0-4.mga2
+>
+> Won't start at all- what can I do??
+>
+> Thx,
+> R.Fox
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120823/615c0bb3/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018263.html b/zarb-ml/mageia-dev/2012-August/018263.html new file mode 100644 index 000000000..d5b4a3c18 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018263.html @@ -0,0 +1,154 @@ + + + + [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text + + + + + + + + + +

[Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Aug 23 07:33:13 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 22/08/2012 16:29, Pascal Terjan wrote:
+> On Wed, Aug 22, 2012 at 11:57 AM, Marja van Waes
+> <marja11 at xs4all.nl> wrote:
+>> Hi all,
+>> 
+>> About a help text for drakx-installer-stage2:
+>> 
+>> Can someone please help documentation team with a good help text
+>> for the help button for the "Add or Modify a Boot Menu Entry"
+>> screen, so for the pop up screen you see in the second screenshot
+>> here (the one that pops up on top of the Bootloader Configuration
+>> screen) 
+>> http://docteam.mageia.nl/installer/content/setupBootloaderAddEntry.html
+>
+>> 
+> What is the expected kind of text? ( I have never read the help :)
+> ) An explanation of the different fields?
+
+Thanks for asking :-D
+
+Yes, and what can be done there and what shouldn't
+
+If you already have an idea about what to write, then don't read on
+(my questions might make you forget things you'd otherwise add ;) )
+
+
+
+
+
+For instance the append field:
+* Is it wrong to make a new entry for your bootloader and leave that
+field empty (I'm sure I never entered a UUID, because I don't really
+know what it is nor how to find the one for that partition..... what
+sets the UUID and how /do/ you find it, btw?)
+* What options are there, what do they do?
+
+And for the advanced screen:
+
+Can you change the initrd image independently from the vmlinuz image
+in the previous screen (and the other way around), in other words, are
+they allowed to have different versions and if so, when can that be
+needed or useful?
+
+(I know too little about initrd and vmlinuz to be able to tell in a
+few lines what they actually do and what I know might even be wrong.
+It would be nice to have a short explanation in this help text)
+
+For the video mode, when is changing that useful or OK? Can fiddling
+with it help if, for instance, while booting into Mageia and pressing
+"Esc", the text is too far to the left of the screen so you can't see
+the first part of each line?
+
+If you changed the video mode and made things worse, can you put
+something on the append line to try with a different mode? (that is a
+general question, too, for anything that you change here)
+
+
+
+
+
+
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iQEcBAEBAgAGBQJQNcCQAAoJEKWubDMI5nEBSREIAIGJK/b14wpN/019ObIa6DnY
+QTKD6D2B0yxYnwv9VUABqd1Vgo65qaE88I72e4kc15RTbk2NlUwTiIzQrH0ZyPWi
+dkIagwLU8nC2SV2A0nCk/e7WrE1ipBNr8BcXbU54dQvhO0hc+uFUvc3WAqY6VsvX
+7196TjlwmUlKxnJOB5E5wBmATVKW/VldjcrN9YntVR1GuLt2Q0CvW5YnU26fBOwj
+Bp+aORbIoRvBp8h7s5GKMcjtcnPF3NmWCVkPy1UtuVbVGjNn9A0DpAUWVnnVe8we
+Nu7p12cwyAUPDmwpdbFSG4bHso9pf7sfwgSvLVSBc14jk+uXF1dJXNmPbcSC3jc=
+=P4iI
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018264.html b/zarb-ml/mageia-dev/2012-August/018264.html new file mode 100644 index 000000000..5b30c7ebd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018264.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] perl 5.16.1 on its way + + + + + + + + + +

[Mageia-dev] perl 5.16.1 on its way

+ Jerome Quelin + jquelin at gmail.com +
+ Thu Aug 23 14:17:51 CEST 2012 +

+
+ +
hi,
+
+now that i did the usrmove switch (thanks coling for the help!), i can
+resume updating packages... so i just updated perl to 5.16.1.
+
+however, i cannot get iurt to work locally (and don't really understand
+why it fails where it was working fine before), so i submitted it
+blindly to bs. now i just need to leave for vacation, plf-style! :-)
+
+anyway, update should be smooth. (famous last words) otherwise, hey,
+it's cauldron, and way too stable those days.
+
+jérôme 
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018265.html b/zarb-ml/mageia-dev/2012-August/018265.html new file mode 100644 index 000000000..b6a9215a0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018265.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Mageia 3 alpha 1 on the way.. + + + + + + + + + +

[Mageia-dev] Mageia 3 alpha 1 on the way..

+ Anne Nicolas + ennael at mageia.org +
+ Thu Aug 23 15:26:50 CEST 2012 +

+
+ +
Hi there
+
+As stated yesterday during our meeting 
+(http://meetbot.mageia.org/mageia-dev/2012/mageia-dev.2012-08-22-19.08.html), 
+Mageia 3 alpha1 is planned for 4th of september.
+
+We will freeze local repository about 4 days before for final isos. If 
+you want to get more tests on your packages, please submit new one or 
+updates before this deadline.
+
+Cheers
+
+-- 
+Anne
+http://mageia.org
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018266.html b/zarb-ml/mageia-dev/2012-August/018266.html new file mode 100644 index 000000000..83e92a052 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018266.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] problem building grass - changes in ffmpeg + + + + + + + + + +

[Mageia-dev] problem building grass - changes in ffmpeg

+ Oliver Burger + obgr_seneca at mageia.org +
+ Thu Aug 23 15:32:43 CEST 2012 +

+
+ +
Am 15.08.2012 10:36, schrieb Oliver Burger:
+> Hi there,
+>
+> I have a problem with grass since we updated ffmpeg on Cauldron.
+> The problem is a change in ffmpeg which results in grass not building
+> anymore.
+> I tried to fix it myself, but I was not able to so I asked upstream
+> about it, who were not really responsive.
+> As I searched further for a solution I noticed that none of the other
+> big distros (openSUSE, Fedora, Debian, Ubuntu) do compile grass with
+> ffmpeg support.
+> So here is the question.
+> Should I just disable the ffmpeg support in grass as the others do or is
+> anyone willing into it?
+>
+No comments on that? If I don't get any replies in the next days, I will 
+disable ffmpeg support in grass for the time being until upstream gets 
+it sorted out.
+If this shouldn't happen before the Mga3 freeze, I will note it in the 
+errata.
+
+Oliver
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018267.html b/zarb-ml/mageia-dev/2012-August/018267.html new file mode 100644 index 000000000..55348526f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018267.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] Mageia 3 alpha 1 on the way.. + + + + + + + + + +

[Mageia-dev] Mageia 3 alpha 1 on the way..

+ isadora + isadora7777777 at gmail.com +
+ Thu Aug 23 15:51:28 CEST 2012 +

+
+ +
Posted in our forum:
+
+https://forums.mageia.org/en/viewtopic.php?f=3&t=3349
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018268.html b/zarb-ml/mageia-dev/2012-August/018268.html new file mode 100644 index 000000000..9602c281c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018268.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] updating torque? + + + + + + + + + +

[Mageia-dev] updating torque?

+ EatDirt + dirteat at gmail.com +
+ Thu Aug 23 18:14:24 CEST 2012 +

+
+ +
Hi,
+torque package is not maintained by anyone. The version we have on 
+mageia is 2.5.3 which is *very* old. Torque comes in various branches, 
+the version 2 is now at 2.5.12 wheras the last version is 4.1.0
+
+
+The spec file is an old monster from mandriva that would need cleaning. 
+Some scripts have been extracted from the very old source files, and 
+then edited by hand, moved to SOURCES/ and are still in use to overwrite 
+the new ones coming with the new version. If by chance this is still 
+working, it won't at some point :)
+
+I am actually using torque at work (but from centos...), so I can give 
+it a try; unless someone has a peculiar interest in doing it instead.
+
+My plan is:
+
+1) Upgrade 2.5.3 -> 2.5.12 + drop old scripts + clean specfile
+
+2) Import torque 4.1.0 and create torque2 branch
+
+3) Eventually drop torque2 branch at some point
+
+
+Please let me know if you disagree or have any comments! Any suggestions 
+welcome.
+
+Cheers,
+Chris.
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018269.html b/zarb-ml/mageia-dev/2012-August/018269.html new file mode 100644 index 000000000..81192b831 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018269.html @@ -0,0 +1,123 @@ + + + + [Mageia-dev] Dropping hal from Mageia 3 REMINDER + + + + + + + + + +

[Mageia-dev] Dropping hal from Mageia 3 REMINDER

+ Damien Lallement + mageia at damsweb.net +
+ Thu Aug 23 18:16:32 CEST 2012 +

+
+ +
Le 17/07/2012 16:10, Damien Lallement a écrit :
+> Hi boys and girls.
+>
+> What do you think about dropping hal for Mageia 3?
+> I was planning to ask it for Mageia 2 but it was too late.
+> I made some cleaning in May but it still remains:
+>
+> [dams at maximus ~]$ urpmq --whatrequires hal
+> draksnapshot
+> draksnapshot
+> hal
+> lib64hal-devel
+> lib64hal1
+> libhal-devel
+> libhal1
+> sugar
+> sugar
+> usb-imagewriter
+> usb-imagewriter
+> [dams at maximus ~]$ urpmq --whatrequires libhal1
+> hal
+> libhal-devel
+> libhal1
+> librapi2
+> libsynce0
+> nut-drivers-hal
+> wmbattery
+> [dams at maximus ~]$
+>
+> If packagers can check their packages to remove hal deps, I will add it
+> to task-obsoletes before first alpha.
+> Thanks.
+
+Reminder... :-)
+-- 
+Damien Lallement
+twitter: damsweb - IRC: damsweb/coincoin
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018270.html b/zarb-ml/mageia-dev/2012-August/018270.html new file mode 100644 index 000000000..df557c4d0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018270.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] updating torque? + + + + + + + + + +

[Mageia-dev] updating torque?

+ P. Christeas + xrg at linux.gr +
+ Thu Aug 23 19:04:40 CEST 2012 +

+
+ +
On Thursday 23 August 2012, EatDirt wrote:
+> Hi,
+> I am actually using torque at work (but from centos...), so I can give
+> it a try; unless someone has a peculiar interest in doing it instead.
+> 
+> My plan is:
+> 1) Upgrade 2.5.3 -> 2.5.12 + drop old scripts + clean specfile
+> 2) Import torque 4.1.0 and create torque2 branch
+> 3) Eventually drop torque2 branch at some point
+
+
+Nice. Although I'm using it on another distro, too, I could help test your 
+package.
+
+
+-- 
+Say NO to spam and viruses. Stop using Microsoft Windows!
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018271.html b/zarb-ml/mageia-dev/2012-August/018271.html new file mode 100644 index 000000000..a31f4faf2 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018271.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 23 20:14:21 CEST 2012 +

+
+ +
On 23 August 2012 19:03, shlomif <buildsystem-daemon at mageia.org> wrote:
+> shlomif <shlomif> 0.0.4-4.mga3:
+> + Revision: 283316
+> - Rebuild for new perl interpreter
+
+Why?
+That's hardly necessary.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018272.html b/zarb-ml/mageia-dev/2012-August/018272.html new file mode 100644 index 000000000..64a7c56c4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018272.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Thu Aug 23 21:01:18 CEST 2012 +

+
+ +
Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+> Unless someone step it to fix pending issues, those packages should
+> better get dropped.
+I just removed madwifi-sources, apache-mod_python and apache-mod_ruby 
+from the subversion repository. I need an admin to remove the 
+corresponding packages (including the debug ones) from the distribution 
+tree.
+
+-- 
+BOFH excuse #19:
+
+floating point processor overflow
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018273.html b/zarb-ml/mageia-dev/2012-August/018273.html new file mode 100644 index 000000000..7d9bbce37 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018273.html @@ -0,0 +1,125 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-5.16.1-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-5.16.1-2.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 23 22:27:22 CEST 2012 +

+
+ +
On Thu, Aug 23, 2012 at 9:13 PM, tv <buildsystem-daemon at mageia.org> wrote:
+> Name        : perl                         Relocations: (not relocatable)
+> Version     : 5.16.1                            Vendor: Mageia.Org
+> Release     : 2.mga3                        Build Date: Thu Aug 23 22:03:35 2012
+> Install Date: (not installed)               Build Host: ecosse.mageia.org
+> Group       : Development/Perl              Source RPM: (none)
+> Size        : 15778754                         License: GPL+ or Artistic
+> Signature   : (none)
+> Packager    : tv <tv>
+> URL         : http://www.perl.org/
+> Summary     : The Perl programming language
+> Description :
+> Perl is a high-level programming language with roots in C, sed, awk
+> and shell scripting.  Perl is good at handling processes and files,
+> and is especially good at handling text.  Perl's hallmarks are
+> practicality and efficiency.  While it is used to do a lot of
+> different things, Perl's most common applications (and what it excels
+> at) are probably system administration utilities and web programming.
+> A large proportion of the CGI scripts on the web are written in Perl.
+> You need the perl package installed on your system so that your
+> system can handle Perl scripts.
+>
+> You need perl-base to have a full perl.
+>
+> tv <tv> 2:5.16.1-2.mga3:
+> + Revision: 283354
+> - rebuild b/c find-provides insert perlapi provides depending on installed
+>   perl, not the one we currently build...
+
+And now cauldron is broken :(
+
+Some requested packages cannot be installed:
+coreutils-8.17-3.mga3.i586 (due to conflicts with
+perl-File-Sync-0.110.0-1.mga3.i586)
+openldap-2.4.32-1.mga3.i586 (due to unsatisfied setup[>= 2.2.0-6mdk])
+perl-File-Sync-0.110.0-1.mga3.i586 (due to unsatisfied perlapi-5.16.0)
+perl-List-MoreUtils-0.330.0-1.mga3.i586 (due to unsatisfied perlapi-5.16.0)
+setup-2.7.20-1.mga2.i586 (due to conflicts with
+perl-File-Sync-0.110.0-1.mga3.i586)
+sudo-1.8.5p1-1.mga3.i586 (due to unsatisfied openldap[*])
+util-linux-2.21.2-3.mga3.i586 (due to unsatisfied coreutils[*])
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018274.html b/zarb-ml/mageia-dev/2012-August/018274.html new file mode 100644 index 000000000..d0e7a2723 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018274.html @@ -0,0 +1,135 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-5.16.1-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-5.16.1-2.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 23 22:38:50 CEST 2012 +

+
+ +
On Thu, Aug 23, 2012 at 9:27 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Thu, Aug 23, 2012 at 9:13 PM, tv <buildsystem-daemon at mageia.org> wrote:
+>> Name        : perl                         Relocations: (not relocatable)
+>> Version     : 5.16.1                            Vendor: Mageia.Org
+>> Release     : 2.mga3                        Build Date: Thu Aug 23 22:03:35 2012
+>> Install Date: (not installed)               Build Host: ecosse.mageia.org
+>> Group       : Development/Perl              Source RPM: (none)
+>> Size        : 15778754                         License: GPL+ or Artistic
+>> Signature   : (none)
+>> Packager    : tv <tv>
+>> URL         : http://www.perl.org/
+>> Summary     : The Perl programming language
+>> Description :
+>> Perl is a high-level programming language with roots in C, sed, awk
+>> and shell scripting.  Perl is good at handling processes and files,
+>> and is especially good at handling text.  Perl's hallmarks are
+>> practicality and efficiency.  While it is used to do a lot of
+>> different things, Perl's most common applications (and what it excels
+>> at) are probably system administration utilities and web programming.
+>> A large proportion of the CGI scripts on the web are written in Perl.
+>> You need the perl package installed on your system so that your
+>> system can handle Perl scripts.
+>>
+>> You need perl-base to have a full perl.
+>>
+>> tv <tv> 2:5.16.1-2.mga3:
+>> + Revision: 283354
+>> - rebuild b/c find-provides insert perlapi provides depending on installed
+>>   perl, not the one we currently build...
+>
+> And now cauldron is broken :(
+>
+> Some requested packages cannot be installed:
+> coreutils-8.17-3.mga3.i586 (due to conflicts with
+> perl-File-Sync-0.110.0-1.mga3.i586)
+> openldap-2.4.32-1.mga3.i586 (due to unsatisfied setup[>= 2.2.0-6mdk])
+> perl-File-Sync-0.110.0-1.mga3.i586 (due to unsatisfied perlapi-5.16.0)
+> perl-List-MoreUtils-0.330.0-1.mga3.i586 (due to unsatisfied perlapi-5.16.0)
+> setup-2.7.20-1.mga2.i586 (due to conflicts with
+> perl-File-Sync-0.110.0-1.mga3.i586)
+> sudo-1.8.5p1-1.mga3.i586 (due to unsatisfied openldap[*])
+> util-linux-2.21.2-3.mga3.i586 (due to unsatisfied coreutils[*])
+
+in a base chroot:
+
+	perlapi-5.16.0 is needed by (installed) perl-File-Sync-0.110.0-1.mga3.i586
+	perlapi-5.16.0 is needed by (installed) perl-List-MoreUtils-0.330.0-1.mga3.i586
+	perlapi-5.16.0 is needed by (installed) perl-URPM-4.12-1.mga3.i586
+	perlapi-5.16.0 is needed by (installed) perl-Filesys-Df-0.920.0-7.mga3.i586
+	perlapi-5.16.0 is needed by (installed) perl-Locale-gettext-1.50.0-6.mga3.i586
+	perlapi-5.16.0 is needed by (installed) perl-XML-LibXML-2.0.200-1.mga3.i586
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018275.html b/zarb-ml/mageia-dev/2012-August/018275.html new file mode 100644 index 000000000..f04ea1691 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018275.html @@ -0,0 +1,139 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-5.16.1-2.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-5.16.1-2.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 23 22:41:05 CEST 2012 +

+
+ +
On Thu, Aug 23, 2012 at 9:38 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Thu, Aug 23, 2012 at 9:27 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+>> On Thu, Aug 23, 2012 at 9:13 PM, tv <buildsystem-daemon at mageia.org> wrote:
+>>> Name        : perl                         Relocations: (not relocatable)
+>>> Version     : 5.16.1                            Vendor: Mageia.Org
+>>> Release     : 2.mga3                        Build Date: Thu Aug 23 22:03:35 2012
+>>> Install Date: (not installed)               Build Host: ecosse.mageia.org
+>>> Group       : Development/Perl              Source RPM: (none)
+>>> Size        : 15778754                         License: GPL+ or Artistic
+>>> Signature   : (none)
+>>> Packager    : tv <tv>
+>>> URL         : http://www.perl.org/
+>>> Summary     : The Perl programming language
+>>> Description :
+>>> Perl is a high-level programming language with roots in C, sed, awk
+>>> and shell scripting.  Perl is good at handling processes and files,
+>>> and is especially good at handling text.  Perl's hallmarks are
+>>> practicality and efficiency.  While it is used to do a lot of
+>>> different things, Perl's most common applications (and what it excels
+>>> at) are probably system administration utilities and web programming.
+>>> A large proportion of the CGI scripts on the web are written in Perl.
+>>> You need the perl package installed on your system so that your
+>>> system can handle Perl scripts.
+>>>
+>>> You need perl-base to have a full perl.
+>>>
+>>> tv <tv> 2:5.16.1-2.mga3:
+>>> + Revision: 283354
+>>> - rebuild b/c find-provides insert perlapi provides depending on installed
+>>>   perl, not the one we currently build...
+>>
+>> And now cauldron is broken :(
+>>
+>> Some requested packages cannot be installed:
+>> coreutils-8.17-3.mga3.i586 (due to conflicts with
+>> perl-File-Sync-0.110.0-1.mga3.i586)
+>> openldap-2.4.32-1.mga3.i586 (due to unsatisfied setup[>= 2.2.0-6mdk])
+>> perl-File-Sync-0.110.0-1.mga3.i586 (due to unsatisfied perlapi-5.16.0)
+>> perl-List-MoreUtils-0.330.0-1.mga3.i586 (due to unsatisfied perlapi-5.16.0)
+>> setup-2.7.20-1.mga2.i586 (due to conflicts with
+>> perl-File-Sync-0.110.0-1.mga3.i586)
+>> sudo-1.8.5p1-1.mga3.i586 (due to unsatisfied openldap[*])
+>> util-linux-2.21.2-3.mga3.i586 (due to unsatisfied coreutils[*])
+>
+> in a base chroot:
+>
+>         perlapi-5.16.0 is needed by (installed) perl-File-Sync-0.110.0-1.mga3.i586
+>         perlapi-5.16.0 is needed by (installed) perl-List-MoreUtils-0.330.0-1.mga3.i586
+>         perlapi-5.16.0 is needed by (installed) perl-URPM-4.12-1.mga3.i586
+>         perlapi-5.16.0 is needed by (installed) perl-Filesys-Df-0.920.0-7.mga3.i586
+>         perlapi-5.16.0 is needed by (installed) perl-Locale-gettext-1.50.0-6.mga3.i586
+>         perlapi-5.16.0 is needed by (installed) perl-XML-LibXML-2.0.200-1.mga3.i586
+
+I will restore previous perl and rebuild them with it (I think blino
+had a script, I'll look for it)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018276.html b/zarb-ml/mageia-dev/2012-August/018276.html new file mode 100644 index 000000000..4cf238c31 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018276.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 23 22:48:12 CEST 2012 +

+
+ +
On 23 August 2012 20:55, Shlomi Fish <shlomif at iglu.org.il> wrote:
+>> wrote:
+>> > shlomif <shlomif> 0.0.4-4.mga3:
+>> > + Revision: 283316
+>> > - Rebuild for new perl interpreter
+>>
+>> Why?
+>> That's hardly necessary.
+>
+> The problem is that the /usr/bin/perlmf (and other programs written in perl) have
+> the interpreter path hard-coded as /usr/bin/perl5.16.0, which is no longer available.
+> I could add a symlink on my system, but it requires every Cauldron user to do the same.
+>
+> For example:
+>
+> shlomif[rpms]:$mageia$ /usr/bin/magpie co -s perl-Test-More
+> -bash: /usr/bin/magpie: /usr/bin/perl5.16.0: bad interpreter: No such
+> file or directory
+>
+> How do you propose to resolve all that?
+
+By calling /usr/bin/perl directly...
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018277.html b/zarb-ml/mageia-dev/2012-August/018277.html new file mode 100644 index 000000000..05b218587 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018277.html @@ -0,0 +1,130 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 23 22:54:51 CEST 2012 +

+
+ +
'Twas brillig, and Olivier Blin at 11/08/12 11:33 did gyre and gimble:
+> nicolas vigier <boklm at mars-attacks.org> writes:
+> 
+>> On Mon, 29 Aug 2011, Michael Scherer wrote:
+> 
+> [...]
+> 
+>>>> After looking at the problem, I suspect it could be linked to texmf.
+>>>> Each time iurt install it, the process stop.  
+>>>
+>>> Boklm found the problem, it was urpmi segfaulting.
+>>>
+>>> We remove the chroot, and thing seems to be ok now again.
+>>
+>> But we probably still have the problem, as segfaults seems to be
+>> happenning not all the time.
+>>
+>> After succesfully reproducing the error using the old chroot and running
+>> urpmi several times, the backtrace :
+>>
+>> #0  0xf7405b29 in _int_malloc () from /lib/i686/libc.so.6
+>> #1  0xf7408177 in malloc () from /lib/i686/libc.so.6
+>> #2  0xf6eadfa8 in __os_malloc (env=0xb442db8, size=4149199776, storep=0xffbbf5cc) at ../os/os_alloc.c:253
+>> #3  0xf6eac47c in __memp_sync_int (env=0xb442db8, dbmfp=0xb893130, trickle_max=0, flags=8, wrote_totalp=0x0, interruptedp=0x0)
+>>     at ../mp/mp_sync.c:294
+>> #4  0xf6eacfaf in __memp_fsync (dbmfp=0xb893130) at ../mp/mp_sync.c:202
+>> #5  0xf6e3cdf9 in __db_sync (dbp=0xb8963e8) at ../db/db_am.c:706
+>> #6  0xf6e3aa68 in __db_refresh (dbp=0xb8963e8, txn=0x0, flags=0, deferred_closep=0xffbbf6fc, reuse=0) at ../db/db.c:819
+>> #7  0xf6e3adc5 in __db_close (dbp=0xb8963e8, txn=0x0, flags=0) at ../db/db.c:695
+>> #8  0xf6e52a38 in __db_close_pp (dbp=0xb8963e8, flags=0) at ../db/db_iface.c:253
+>> #9  0xf72fec45 in db3close (dbi=0xb893030, flags=0) at backend/db3.c:494
+>> #10 0xf73071c6 in dbiClose (db=0xb2b6950) at ../lib/rpmdb_internal.h:453
+>> #11 rpmdbClose (db=0xb2b6950) at rpmdb.c:852
+>> #12 0xf73379d6 in rpmtsCloseDB (ts=0xb231b20) at rpmts.c:64
+>> #13 0xf7337a48 in rpmtsFree (ts=0xb231b20) at rpmts.c:567
+>> #14 0xf736c7a1 in XS_URPM__DB_DESTROY (my_perl=0x8d42008, cv=0x8e2d420) at URPM.xs:2794
+> 
+> [...]
+> 
+> Hello,
+> 
+> After hitting the issue yesterday with the "git" package, we had a look
+> at the issue together with pterjan.
+> I had to merge some patches in valgrind to support the new compressed
+> debug info first, but then valgrind spotted some interesting issues.
+> 
+> pterjan fixed some of them, fixes are now in perl-URPM 4.12.
+> It should help preventing "build loops" in the BS.
+> 
+> Attached is the valgrind log with remaining issues, maybe insightful for
+> Titi.
+
+
+jonund was seeing plenty urpmi segv's today...
+
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018278.html b/zarb-ml/mageia-dev/2012-August/018278.html new file mode 100644 index 000000000..9fd6afa6b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018278.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Olivier Blin + mageia at blino.org +
+ Fri Aug 24 00:58:45 CEST 2012 +

+
+ +
Colin Guthrie <mageia at colin.guthr.ie> writes:
+
+>>>> Boklm found the problem, it was urpmi segfaulting.
+>
+>> After hitting the issue yesterday with the "git" package, we had a look
+>> at the issue together with pterjan.
+>> I had to merge some patches in valgrind to support the new compressed
+>> debug info first, but then valgrind spotted some interesting issues.
+>> 
+>> pterjan fixed some of them, fixes are now in perl-URPM 4.12.
+>> It should help preventing "build loops" in the BS.
+>> 
+>> Attached is the valgrind log with remaining issues, maybe insightful for
+>> Titi.
+>
+> jonund was seeing plenty urpmi segv's today...
+
+Yep, there is still at least one remaining issue in perl-URPM, that can
+be reproduced by just installing texlive-texmf IIRC.
+
+pterjan and tv have (probably) been discussing this off-list.
+Any news about this?
+
+-- 
+Olivier Blin - blino
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018279.html b/zarb-ml/mageia-dev/2012-August/018279.html new file mode 100644 index 000000000..e9407c862 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018279.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 24 01:44:01 CEST 2012 +

+
+ +
On Thu, Aug 23, 2012 at 11:58 PM, Olivier Blin <mageia at blino.org> wrote:
+> Colin Guthrie <mageia at colin.guthr.ie> writes:
+>
+>>>>> Boklm found the problem, it was urpmi segfaulting.
+>>
+>>> After hitting the issue yesterday with the "git" package, we had a look
+>>> at the issue together with pterjan.
+>>> I had to merge some patches in valgrind to support the new compressed
+>>> debug info first, but then valgrind spotted some interesting issues.
+>>>
+>>> pterjan fixed some of them, fixes are now in perl-URPM 4.12.
+>>> It should help preventing "build loops" in the BS.
+>>>
+>>> Attached is the valgrind log with remaining issues, maybe insightful for
+>>> Titi.
+>>
+>> jonund was seeing plenty urpmi segv's today...
+>
+> Yep, there is still at least one remaining issue in perl-URPM, that can
+> be reproduced by just installing texlive-texmf IIRC.
+>
+> pterjan and tv have (probably) been discussing this off-list.
+> Any news about this?
+
+I have committed a change which should avoid it, but was interrupted
+by perl breakage in cauldron
+There is new perl-URPM in cauldron and 2/updates_testing, but I need
+to upload a new urpmi too
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018280.html b/zarb-ml/mageia-dev/2012-August/018280.html new file mode 100644 index 000000000..808755f3b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018280.html @@ -0,0 +1,129 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Shlomi Fish + shlomif at shlomifish.org +
+ Fri Aug 24 10:12:53 CEST 2012 +

+
+ +
Hi,
+
+On Thu, 23 Aug 2012 22:48:12 +0200
+Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+
+> On 23 August 2012 20:55, Shlomi Fish <shlomif at iglu.org.il> wrote:
+> >> wrote:
+> >> > shlomif <shlomif> 0.0.4-4.mga3:
+> >> > + Revision: 283316
+> >> > - Rebuild for new perl interpreter
+> >>
+> >> Why?
+> >> That's hardly necessary.
+> >
+> > The problem is that the /usr/bin/perlmf (and other programs written
+> > in perl) have the interpreter path hard-coded
+> > as /usr/bin/perl5.16.0, which is no longer available. I could add a
+> > symlink on my system, but it requires every Cauldron user to do the
+> > same.
+> >
+> > For example:
+> >
+> > shlomif[rpms]:$mageia$ /usr/bin/magpie co -s perl-Test-More
+> > -bash: /usr/bin/magpie: /usr/bin/perl5.16.0: bad interpreter: No
+> > such file or directory
+> >
+> > How do you propose to resolve all that?
+> 
+> By calling /usr/bin/perl directly...
+
+What? I don't understand. Do you mean that the Perl programs should have 
+"#!/usr/bin/perl" as their sha-bang? (Which will require either
+postprocessing them or tweaking their installer.) Or do you mean that
+I should do «perl /usr/bin/magpie» instead?
+
+Regards,
+
+	Shlomi Fish
+
+-- 
+-----------------------------------------------------------------
+Shlomi Fish       http://www.shlomifish.org/
+Best Introductory Programming Language - http://shlom.in/intro-lang
+
+I may be a geek, but I’m a true Klingon geek‐warrior! And a true Klingon geek
+warrior ALWAYS bottom‐posts.
+
+Please reply to list if it's a mailing list post - http://shlom.in/reply .
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018281.html b/zarb-ml/mageia-dev/2012-August/018281.html new file mode 100644 index 000000000..37e76c7f7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018281.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Aug 24 10:20:10 CEST 2012 +

+
+ +
Le 24/08/2012 10:12, Shlomi Fish a écrit :
+>>> How do you propose to resolve all that?
+>>
+>> By calling /usr/bin/perl directly...
+>
+> What? I don't understand. Do you mean that the Perl programs should have
+> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+> postprocessing them or tweaking their installer.)
+Yes, packaged perl programs should use an unversionned shebang, which is 
+the case for the large majority of them.
+-- 
+BOFH excuse #192:
+
+runaway cat on system.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018282.html b/zarb-ml/mageia-dev/2012-August/018282.html new file mode 100644 index 000000000..ba75052cc --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018282.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] problem building grass - changes in ffmpeg + + + + + + + + + +

[Mageia-dev] problem building grass - changes in ffmpeg

+ EatDirt + dirteat at gmail.com +
+ Fri Aug 24 10:50:56 CEST 2012 +

+
+ +
On 23/08/12 15:32, Oliver Burger wrote:
+
+>>
+> No comments on that? If I don't get any replies in the next days, I will
+> disable ffmpeg support in grass for the time being until upstream gets
+> it sorted out.
+> If this shouldn't happen before the Mga3 freeze, I will note it in the
+
+Hi Master,
+In my opinion, you should disable ffmpeg because the new ffmpeg 0.11 is 
+a completely new API. This kind of fixes should come from upstream.
+
+I got into the same problem with "motion" and I had to disable 
+temporarily ffmpeg till it was fixed in git upstream.
+
+Cheers,
+Chris.
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018283.html b/zarb-ml/mageia-dev/2012-August/018283.html new file mode 100644 index 000000000..3d7215eaf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018283.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 24 11:06:23 CEST 2012 +

+
+ +
On 24 August 2012 10:20, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>>>> How do you propose to resolve all that?
+>>>
+>>>
+>>> By calling /usr/bin/perl directly...
+>>
+>>
+>> What? I don't understand. Do you mean that the Perl programs should have
+>> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+>> postprocessing them or tweaking their installer.)
+>
+> Yes, packaged perl programs should use an unversionned shebang, which is the
+> case for the large majority of them.
+
+We could clean that in spec-helper.
+Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018284.html b/zarb-ml/mageia-dev/2012-August/018284.html new file mode 100644 index 000000000..d1fe263e1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018284.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Aug 24 11:11:21 CEST 2012 +

+
+ +
Le 24/08/2012 11:06, Thierry Vignaud a écrit :
+> On 24 August 2012 10:20, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>>>>> How do you propose to resolve all that?
+>>>>
+>>>>
+>>>> By calling /usr/bin/perl directly...
+>>>
+>>>
+>>> What? I don't understand. Do you mean that the Perl programs should have
+>>> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+>>> postprocessing them or tweaking their installer.)
+>>
+>> Yes, packaged perl programs should use an unversionned shebang, which is the
+>> case for the large majority of them.
+>
+> We could clean that in spec-helper.
+> Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
+>
+Yes, it seems a marvelous idea to automatically convert python and tcl 
+scripts to use perl interpreter instead, it will make our base 
+installation footprint lower :)
+
+More seriously, we can do it easily for perl and tcl, but with much 
+caution for python, as we have two different major versions available at 
+once in the distribution.
+
+-- 
+BOFH excuse #367:
+
+Webmasters kidnapped by evil cult.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018285.html b/zarb-ml/mageia-dev/2012-August/018285.html new file mode 100644 index 000000000..badc3ec9e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018285.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 24 11:21:44 CEST 2012 +

+
+ +
On 24 August 2012 11:11, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>>>>> By calling /usr/bin/perl directly...
+>>>>
+>>>> What? I don't understand. Do you mean that the Perl programs should have
+>>>> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+>>>> postprocessing them or tweaking their installer.)
+>>>
+>>> Yes, packaged perl programs should use an unversionned shebang, which is
+>>> the case for the large majority of them.
+>>
+>> We could clean that in spec-helper.
+>> Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
+>>
+> Yes, it seems a marvelous idea to automatically convert python and tcl
+> scripts to use perl interpreter instead, it will make our base installation
+> footprint lower :)
+>
+> More seriously, we can do it easily for perl and tcl, but with much caution
+> for python, as we have two different major versions available at once in the
+> distribution.
+
+Let's say we should do it for perl/php/tcl for now
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018286.html b/zarb-ml/mageia-dev/2012-August/018286.html new file mode 100644 index 000000000..9e7c0fd2c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018286.html @@ -0,0 +1,111 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Aug 24 11:28:10 CEST 2012 +

+
+ +
Le 24/08/2012 11:21, Thierry Vignaud a écrit :
+> On 24 August 2012 11:11, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>>>>>> By calling /usr/bin/perl directly...
+>>>>>
+>>>>> What? I don't understand. Do you mean that the Perl programs should have
+>>>>> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+>>>>> postprocessing them or tweaking their installer.)
+>>>>
+>>>> Yes, packaged perl programs should use an unversionned shebang, which is
+>>>> the case for the large majority of them.
+>>>
+>>> We could clean that in spec-helper.
+>>> Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
+>>>
+>> Yes, it seems a marvelous idea to automatically convert python and tcl
+>> scripts to use perl interpreter instead, it will make our base installation
+>> footprint lower :)
+>>
+>> More seriously, we can do it easily for perl and tcl, but with much caution
+>> for python, as we have two different major versions available at once in the
+>> distribution.
+>
+> Let's say we should do it for perl/php/tcl for now
+Actually, it seems a bit exagerated to add yet another script for 
+spec-helper that will scan all text files for all packages at each 
+build, in order to solve such low occurence issue... How many packages 
+are concerned ?
+-- 
+BOFH excuse #48:
+
+bad ether in the cables
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018287.html b/zarb-ml/mageia-dev/2012-August/018287.html new file mode 100644 index 000000000..5648e0674 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018287.html @@ -0,0 +1,122 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 24 11:30:08 CEST 2012 +

+
+ +
On Fri, Aug 24, 2012 at 10:28 AM, Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 24/08/2012 11:21, Thierry Vignaud a écrit :
+>
+>> On 24 August 2012 11:11, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>>>>>>>
+>>>>>>> By calling /usr/bin/perl directly...
+>>>>>>
+>>>>>>
+>>>>>> What? I don't understand. Do you mean that the Perl programs should
+>>>>>> have
+>>>>>> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+>>>>>> postprocessing them or tweaking their installer.)
+>>>>>
+>>>>>
+>>>>> Yes, packaged perl programs should use an unversionned shebang, which
+>>>>> is
+>>>>> the case for the large majority of them.
+>>>>
+>>>>
+>>>> We could clean that in spec-helper.
+>>>> Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
+>>>>
+>>> Yes, it seems a marvelous idea to automatically convert python and tcl
+>>> scripts to use perl interpreter instead, it will make our base
+>>> installation
+>>> footprint lower :)
+>>>
+>>> More seriously, we can do it easily for perl and tcl, but with much
+>>> caution
+>>> for python, as we have two different major versions available at once in
+>>> the
+>>> distribution.
+>>
+>>
+>> Let's say we should do it for perl/php/tcl for now
+>
+> Actually, it seems a bit exagerated to add yet another script for
+> spec-helper that will scan all text files for all packages at each build, in
+> order to solve such low occurence issue... How many packages are concerned ?
+
+Not all (only executables at most)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018288.html b/zarb-ml/mageia-dev/2012-August/018288.html new file mode 100644 index 000000000..230e0ec86 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018288.html @@ -0,0 +1,117 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release perl-Module-Format-0.0.4-4.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 24 11:42:21 CEST 2012 +

+
+ +
On 24 August 2012 11:28, Guillaume Rousse <guillomovitch at gmail.com> wrote:
+>>>>>>> By calling /usr/bin/perl directly...
+>>>>>>
+>>>>>>
+>>>>>> What? I don't understand. Do you mean that the Perl programs should
+>>>>>> have
+>>>>>> "#!/usr/bin/perl" as their sha-bang? (Which will require either
+>>>>>> postprocessing them or tweaking their installer.)
+>>>>>
+>>>>>
+>>>>> Yes, packaged perl programs should use an unversionned shebang, which
+>>>>> is
+>>>>> the case for the large majority of them.
+>>>>
+>>>>
+>>>> We could clean that in spec-helper.
+>>>> Along "#!/bin/env perl|python|tcl" => "#!/usr/bin/perl" too.
+>>>>
+>>> Yes, it seems a marvelous idea to automatically convert python and tcl
+>>> scripts to use perl interpreter instead, it will make our base
+>>> installation
+>>> footprint lower :)
+>>>
+>>> More seriously, we can do it easily for perl and tcl, but with much
+>>> caution
+>>> for python, as we have two different major versions available at once in
+>>> the
+>>> distribution.
+>>
+>>
+>> Let's say we should do it for perl/php/tcl for now
+>
+> Actually, it seems a bit exagerated to add yet another script for
+> spec-helper that will scan all text files for all packages at each build, in
+> order to solve such low occurence issue... How many packages are concerned ?
+
+for /bin/env, it was ~800 @mdv
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018289.html b/zarb-ml/mageia-dev/2012-August/018289.html new file mode 100644 index 000000000..45a4b6764 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018289.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Olivier Blin + mageia at blino.org +
+ Fri Aug 24 12:48:31 CEST 2012 +

+
+ +
Pascal Terjan <pterjan at gmail.com> writes:
+
+> On Thu, Aug 23, 2012 at 11:58 PM, Olivier Blin <mageia at blino.org> wrote:
+>> Colin Guthrie <mageia at colin.guthr.ie> writes:
+>>> jonund was seeing plenty urpmi segv's today...
+>>
+>> Yep, there is still at least one remaining issue in perl-URPM, that can
+>> be reproduced by just installing texlive-texmf IIRC.
+>>
+>> pterjan and tv have (probably) been discussing this off-list.
+>> Any news about this?
+>
+> I have committed a change which should avoid it, but was interrupted
+> by perl breakage in cauldron
+> There is new perl-URPM in cauldron and 2/updates_testing, but I need
+> to upload a new urpmi too
+
+The urpmi change seems to be just a workaround, don't we have a better
+fix to do in perl-URPM?
+
+-- 
+Olivier Blin - blino
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018290.html b/zarb-ml/mageia-dev/2012-August/018290.html new file mode 100644 index 000000000..839bff2db --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018290.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?) + + + + + + + + + +

[Mageia-dev] urpmi segfaults on the build system (was Re: Our BS is about to eat packages?)

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 24 13:53:53 CEST 2012 +

+
+ +
On Fri, Aug 24, 2012 at 11:48 AM, Olivier Blin <mageia at blino.org> wrote:
+> Pascal Terjan <pterjan at gmail.com> writes:
+>
+>> On Thu, Aug 23, 2012 at 11:58 PM, Olivier Blin <mageia at blino.org> wrote:
+>>> Colin Guthrie <mageia at colin.guthr.ie> writes:
+>>>> jonund was seeing plenty urpmi segv's today...
+>>>
+>>> Yep, there is still at least one remaining issue in perl-URPM, that can
+>>> be reproduced by just installing texlive-texmf IIRC.
+>>>
+>>> pterjan and tv have (probably) been discussing this off-list.
+>>> Any news about this?
+>>
+>> I have committed a change which should avoid it, but was interrupted
+>> by perl breakage in cauldron
+>> There is new perl-URPM in cauldron and 2/updates_testing, but I need
+>> to upload a new urpmi too
+>
+> The urpmi change seems to be just a workaround, don't we have a better
+> fix to do in perl-URPM?
+
+Yes (or maybe in perl) but valgrind is still segfaulting in cauldron
+so I preferred avoiding the segfault without waiting for a proper
+debugging of the issue
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018291.html b/zarb-ml/mageia-dev/2012-August/018291.html new file mode 100644 index 000000000..0dacea2e9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018291.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] Having problem with the monitor + + + + + + + + + +

[Mageia-dev] Having problem with the monitor

+ Kira + elegant.pegasus at gmail.com +
+ Fri Aug 24 15:04:44 CEST 2012 +

+
+ +
在 Wed, 22 Aug 2012 17:48:54 +0800, Kira <elegant.pegasus at gmail.com>寫道:
+
+> 在 Wed, 22 Aug 2012 17:35:32 +0800, Thierry Vignaud  
+> <thierry.vignaud at gmail.com>寫道:
+>>
+>> telling what is your graphic card, if you're using proprietary driver  
+>> or not,
+>> providin /var/log/Xorg.0.log.old ... could help
+> I had tried with proprietary, but it even won't boot in(Should be  
+> another bug)
+>
+> I am using the open source driver now, attachment is the log
+Alright, I gave up. I reinstalled it back to Mageia 2, everything
+
+works. I believe there's some bug in radeon(ati) driver, because
+
+even in Mageia 1/2, they both works.
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018292.html b/zarb-ml/mageia-dev/2012-August/018292.html new file mode 100644 index 000000000..a53bff7da --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018292.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Aug 24 16:43:11 CEST 2012 +

+
+ +
'Twas brillig, and Guillaume Rousse at 23/08/12 20:01 did gyre and gimble:
+> Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+>> Unless someone step it to fix pending issues, those packages should
+>> better get dropped.
+> I just removed madwifi-sources, apache-mod_python and apache-mod_ruby
+> from the subversion repository. I need an admin to remove the
+> corresponding packages (including the debug ones) from the distribution
+> tree.
+
+By "removed" do you mean "svn mv'ed" to the obsolete folder?
+
+I think that's generally better than removing (and we can potentially
+use it to prevent people importing packages that are listed there should
+they come in without knowing).
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018293.html b/zarb-ml/mageia-dev/2012-August/018293.html new file mode 100644 index 000000000..ade3678fb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018293.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Aug 24 16:57:22 CEST 2012 +

+
+ +
Le 24/08/2012 16:43, Colin Guthrie a écrit :
+> 'Twas brillig, and Guillaume Rousse at 23/08/12 20:01 did gyre and gimble:
+>> Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+>>> Unless someone step it to fix pending issues, those packages should
+>>> better get dropped.
+>> I just removed madwifi-sources, apache-mod_python and apache-mod_ruby
+>> from the subversion repository. I need an admin to remove the
+>> corresponding packages (including the debug ones) from the distribution
+>> tree.
+>
+> By "removed" do you mean "svn mv'ed" to the obsolete folder?
+No, svn rm'ed.
+
+
+> I think that's generally better than removing (and we can potentially
+> use it to prevent people importing packages that are listed there should
+> they come in without knowing).
+Agreed. Hence the point of writing the procedure somewhere.
+
+-- 
+If you improve or tinker with something long enough, eventually it will 
+break or malfunction
+		-- Murphy's In Laws n°8
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018294.html b/zarb-ml/mageia-dev/2012-August/018294.html new file mode 100644 index 000000000..7b7e1b38b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018294.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Luis Daniel Lucio Quiroz + dlucio at okay.com.mx +
+ Fri Aug 24 16:58:42 CEST 2012 +

+
+ +
I think removing mod python and ruby is an error
+
+Enviado desde mi DROID 4G LTE de Verizon Wireless
+
+Colin Guthrie <mageia at colin.guthr.ie> escribió:
+
+>'Twas brillig, and Guillaume Rousse at 23/08/12 20:01 did gyre and gimble:
+>> Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+>>> Unless someone step it to fix pending issues, those packages should
+>>> better get dropped.
+>> I just removed madwifi-sources, apache-mod_python and apache-mod_ruby
+>> from the subversion repository. I need an admin to remove the
+>> corresponding packages (including the debug ones) from the distribution
+>> tree.
+>
+>By "removed" do you mean "svn mv'ed" to the obsolete folder?
+>
+>I think that's generally better than removing (and we can potentially
+>use it to prevent people importing packages that are listed there should
+>they come in without knowing).
+>
+>Col
+>
+>
+>-- 
+>
+>Colin Guthrie
+>colin(at)mageia.org
+>http://colin.guthr.ie/
+>
+>Day Job:
+>  Tribalogic Limited http://www.tribalogic.net/
+>Open Source:
+>  Mageia Contributor http://www.mageia.org/
+>  PulseAudio Hacker http://www.pulseaudio.org/
+>  Trac Hacker http://trac.edgewall.org/
+>Email Shield provided by NOCWorldWide.com
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120824/efa62715/attachment.html>
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018295.html b/zarb-ml/mageia-dev/2012-August/018295.html new file mode 100644 index 000000000..0f5b83044 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018295.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Olivier Blin + mageia at blino.org +
+ Fri Aug 24 17:04:13 CEST 2012 +

+
+ +
Guillaume Rousse <guillomovitch at gmail.com> writes:
+
+> Le 24/08/2012 16:43, Colin Guthrie a écrit :
+>> 'Twas brillig, and Guillaume Rousse at 23/08/12 20:01 did gyre and gimble:
+>>> Le 20/08/2012 20:49, Guillaume Rousse a écrit :
+>>>> Unless someone step it to fix pending issues, those packages should
+>>>> better get dropped.
+>>> I just removed madwifi-sources, apache-mod_python and apache-mod_ruby
+>>> from the subversion repository. I need an admin to remove the
+>>> corresponding packages (including the debug ones) from the distribution
+>>> tree.
+>>
+>> By "removed" do you mean "svn mv'ed" to the obsolete folder?
+> No, svn rm'ed.
+>
+>> I think that's generally better than removing (and we can potentially
+>> use it to prevent people importing packages that are listed there should
+>> they come in without knowing).
+> Agreed. Hence the point of writing the procedure somewhere.
+
+You mean like already done here? :)
+https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package
+
+-- 
+Olivier Blin - blino
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018296.html b/zarb-ml/mageia-dev/2012-August/018296.html new file mode 100644 index 000000000..98410c789 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018296.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] updating torque? + + + + + + + + + +

[Mageia-dev] updating torque?

+ David Walser + luigiwalser at yahoo.com +
+ Fri Aug 24 19:03:50 CEST 2012 +

+
+ +
EatDirt <dirteat at ...> writes:
+> I am actually using torque at work (but from centos...), so I can give 
+> it a try; unless someone has a peculiar interest in doing it instead.
+> 
+
+Good to hear :o)  Please have a look at this when you do:
+https://bugs.mageia.org/show_bug.cgi?id=6082
+
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018297.html b/zarb-ml/mageia-dev/2012-August/018297.html new file mode 100644 index 000000000..16c6da4ef --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018297.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Aug 24 19:44:17 CEST 2012 +

+
+ +
Le 24/08/2012 16:58, Luis Daniel Lucio Quiroz a écrit :
+> I think removing mod python and ruby is an error
+Well, that's a bit late... However, feel free to resurect them from the 
+subversion repository, if you're ready to take maintainership of course.
+
+-- 
+BOFH excuse #341:
+
+HTTPD Error 666 : BOFH was here
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018298.html b/zarb-ml/mageia-dev/2012-August/018298.html new file mode 100644 index 000000000..61a098d0a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018298.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Guillaume Rousse + guillomovitch at gmail.com +
+ Fri Aug 24 19:50:16 CEST 2012 +

+
+ +
Le 24/08/2012 17:04, Olivier Blin a écrit :
+>> Agreed. Hence the point of writing the procedure somewhere.
+>
+> You mean like already done here? :)
+> https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package
+Ah, great. Excepted that I disagree with the 'thou shall force users to 
+remove the package also', by using obsolete tags.
+
+-- 
+BOFH excuse #436:
+
+Daemon escaped from pentagram
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018299.html b/zarb-ml/mageia-dev/2012-August/018299.html new file mode 100644 index 000000000..b5ab0ff0c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018299.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] updating torque? + + + + + + + + + +

[Mageia-dev] updating torque?

+ eatdirt + dirteat at gmail.com +
+ Fri Aug 24 21:57:42 CEST 2012 +

+
+ +
So torque-2.5.12-1mga3 landed; please open bug reports if it doesn't 
+work for you.
+
+Cheers,
+Chris.
+
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018300.html b/zarb-ml/mageia-dev/2012-August/018300.html new file mode 100644 index 000000000..ceac3470b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018300.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] updating torque? + + + + + + + + + +

[Mageia-dev] updating torque?

+ Thomas Backlund + tmb at mageia.org +
+ Fri Aug 24 22:00:31 CEST 2012 +

+
+ +
EatDirt skrev 23.8.2012 19:14:
+> Hi,
+> torque package is not maintained by anyone. The version we have on
+> mageia is 2.5.3 which is *very* old. Torque comes in various branches,
+> the version 2 is now at 2.5.12 wheras the last version is 4.1.0
+>
+>
+> The spec file is an old monster from mandriva that would need cleaning.
+> Some scripts have been extracted from the very old source files, and
+> then edited by hand, moved to SOURCES/ and are still in use to overwrite
+> the new ones coming with the new version. If by chance this is still
+> working, it won't at some point :)
+>
+> I am actually using torque at work (but from centos...), so I can give
+> it a try; unless someone has a peculiar interest in doing it instead.
+>
+> My plan is:
+>
+> 1) Upgrade 2.5.3 -> 2.5.12 + drop old scripts + clean specfile
+>
+> 2) Import torque 4.1.0 and create torque2 branch
+>
+> 3) Eventually drop torque2 branch at some point
+>
+>
+> Please let me know if you disagree or have any comments! Any suggestions
+> welcome.
+>
+
+the obvious question....
+
+Do we really need 2 branches of torque ?
+
+Why not simply say bye-bye to 2.* series ?
+
+--
+Thomas
+
+
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018301.html b/zarb-ml/mageia-dev/2012-August/018301.html new file mode 100644 index 000000000..1df2415d6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018301.html @@ -0,0 +1,101 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release rpmtools-6.3-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release rpmtools-6.3-1.mga3

+ Olivier Blin + mageia at blino.org +
+ Sat Aug 25 00:15:31 CEST 2012 +

+
+ +
tv <buildsystem-daemon at mageia.org> writes:
+
+> Name        : rpmtools                     Relocations: (not relocatable)
+> Version     : 6.3                               Vendor: Mageia.Org
+> Release     : 1.mga3                        Build Date: Fri Aug 24 23:39:12 2012
+
+[...]
+
+> tv <tv> 6.3-1.mga3:
+> + Revision: 281521
+> - actually compress xml files with '--text' flag passed to lzma (shrinks
+>   files.xml.lzma by 25% \o/)
+
+Couldn't we use xz for these xml files as well?
+
+> - compress synthesis with XZ too (40% saving)
+
+And use --text for the synthesis?
+It's just text too.
+
+Is there any doc about this --text option?
+I couldn't find any in man page or long help.
+
+BTW, it seems you have your changelog entries doubled (in this package
+and urpmi as well).
+
+Great savings anyway! :)
+Thanks
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018302.html b/zarb-ml/mageia-dev/2012-August/018302.html new file mode 100644 index 000000000..d2d587252 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018302.html @@ -0,0 +1,125 @@ + + + + [Mageia-dev] updating torque? + + + + + + + + + +

[Mageia-dev] updating torque?

+ eatdirt + dirteat at gmail.com +
+ Sat Aug 25 00:53:06 CEST 2012 +

+
+ +
+> the obvious question....
+>
+> Do we really need 2 branches of torque ?
+>
+> Why not simply say bye-bye to 2.* series ?
+>
+> --
+> Thomas
+>
+>
+>
+
+Agreed! I was just avoiding to do a big jump as 2.5.x is still 
+maintained upstream, but ultimately that could be the plan.
+
+As we have some bugs on the current 2.5.3 version on mga2, we could also 
+fix them by upgrading to 2.5.12, drop 2.5.12 in cauldron and move the 4.1.
+
+
+The folks at torque says:
+
+<<
+The 2.5.x branch is the current maintenance build and will continue to 
+have minor features and functionality added to it. The build has been 
+deployed successfully in many environments and is considered reliable. 
+Build torque-2.5.12.tar.gz is the latest release and the one we 
+recommend most sites use.
+ >>
+
+
+For the branch 3, the summary is not very encouraging :)
+
+<<
+The 3.0.x branch has all 2.5.x functionality plus support for NUMA 
+architectures, such as SGI. The 3.0.x branch is not backward compatible. 
+Even though the 3.0.x code branch will work on all platforms we 
+recommend 2.5.x for sites that do not need NUMA. Build 
+torque-3.0.6.tar.gz is the latest release for the 3.0.x branch and will 
+be the last release in the 3.0.x branch. Adaptive Computing support for 
+the 3.0.x branch will end on December 31, 2012.
+ >>
+
+4.1 is indeed the next step:
+
+<<
+The 4.1.x branch has added significant enhancements and a streamlined 
+architecture for managing workload faster, more reliably and with easier 
+administration on Cray systems. It also features fixes and updates from 
+the 4.0.x branch. It is the latest TORQUE release and the one we 
+recommend customers use
+ >>
+
+
+cheers,
+chris.
+
+
+ + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018303.html b/zarb-ml/mageia-dev/2012-August/018303.html new file mode 100644 index 000000000..45af4ce10 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018303.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Sat Aug 25 02:33:31 CEST 2012 +

+
+ +
* Guillaume Rousse (guillomovitch at gmail.com) wrote:
+> Le 24/08/2012 17:04, Olivier Blin a écrit :
+> >>Agreed. Hence the point of writing the procedure somewhere.
+> >
+> >You mean like already done here? :)
+> >https://wiki.mageia.org/en/Packaging_guidelines#Obsoleting_a_package
+> Ah, great. Excepted that I disagree with the 'thou shall force users
+> to remove the package also', by using obsolete tags.
+
+I disagree with this suggest: it is not because the packager want to
+drop the package from the distribution the package must be drop from all
+computer around the world.
+
+Moreover we take the risk to match a completelly unrelated package (git
+is one the notable example, before being a VCS it was a set tools).
+
+For me obsolete should be reserved for replacements or rename, nothing
+more.
+
+BTW: I don't understand the need of versionned obsolete (why the <=
+cauldron version).
+
+Regards.
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120825/10026803/attachment.asc>
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018304.html b/zarb-ml/mageia-dev/2012-August/018304.html new file mode 100644 index 000000000..45e4e1908 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018304.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Johnny A. Solbu + cooker at solbu.net +
+ Sat Aug 25 03:42:16 CEST 2012 +

+
+ +
On Saturday 25 August 2012 02:33, Olivier Thauvin wrote:
+> For me obsolete should be reserved for replacements or rename, nothing
+> more.
+
+I agree on this.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120825/470e1a33/attachment.asc>
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018305.html b/zarb-ml/mageia-dev/2012-August/018305.html new file mode 100644 index 000000000..b4fcbf895 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018305.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release rpmtools-6.3-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release rpmtools-6.3-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Sat Aug 25 09:20:12 CEST 2012 +

+
+ +
On 25 August 2012 00:15, Olivier Blin <mageia at blino.org> wrote:
+>> tv <tv> 6.3-1.mga3:
+>> + Revision: 281521
+>> - actually compress xml files with '--text' flag passed to lzma (shrinks
+>>   files.xml.lzma by 25% \o/)
+>
+> Couldn't we use xz for these xml files as well?
+>
+>> - compress synthesis with XZ too (40% saving)
+>
+> And use --text for the synthesis?
+> It's just text too.
+
+Indeed it saves 4.1 % on synthesis.
+In next release.
+
+> Is there any doc about this --text option?
+> I couldn't find any in man page or long help.
+
+probably lzma man page is now the xz one
+
+> BTW, it seems you have your changelog entries doubled (in this package
+> and urpmi as well).
+
+Already fixed
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018306.html b/zarb-ml/mageia-dev/2012-August/018306.html new file mode 100644 index 000000000..5ef89744b --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018306.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] Mageia 3 alpha 1 on the way.. + + + + + + + + + +

[Mageia-dev] Mageia 3 alpha 1 on the way..

+ Pierre-Malo Deniélou + pierre-malo.denielou at rhul.ac.uk +
+ Sun Aug 26 00:45:52 CEST 2012 +

+
+ +
Le 23/08/12 14:26,Anne Nicolas nous adresse ces quelques mots :
+> Hi there
+> 
+> As stated yesterday during our meeting
+> (http://meetbot.mageia.org/mageia-dev/2012/mageia-dev.2012-08-22-19.08.html),
+> Mageia 3 alpha1 is planned for 4th of september.
+> 
+> We will freeze local repository about 4 days before for final isos. If
+> you want to get more tests on your packages, please submit new one or
+> updates before this deadline.
+> 
+> Cheers
+
+Should we use this occasion to try to reduce the list of 374 packages
+that cannot be installed in the current cauldron? Many are just missing
+rebuilds.
+
+http://check.mageia.org/cauldron/dependencies.html
+
+-- 
+Malo
+
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018307.html b/zarb-ml/mageia-dev/2012-August/018307.html new file mode 100644 index 000000000..50759c1e3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018307.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] ocsinventory & php-gd + + + + + + + + + +

[Mageia-dev] ocsinventory & php-gd

+ Bersuit Vera + bersuit.cooker at gmail.com +
+ Sun Aug 26 12:52:24 CEST 2012 +

+
+ +
Hi all.
+In my  ocsinventory.spec file:
+
+Requires php-gd
+
+ocsinventory builds successfully
+When I install the package with urpmi:
+
+[root at cualdron64 noarch]# urpmi ocsinventory-*
+Para satisfacer la dependencia «php-gd», se necesita uno de los paquetes
+siguientes:
+ 1- php-gd-5.3.15-1.mga2.x86_64: GD extension module for PHP (para instalar)
+ 2- php-gd-bundled-5.3.15-1.mga2.x86_64: GD extension module for PHP (para
+instalar)
+¿Qué elige? (1-2)
+
+What is the difference between php-gd and php-gd-bundled?
+Why urpmi does not choose the first?
+
+Sorry, i'm novice packager :-)
+
+Best regards
+
+
+Bersuit.
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120826/eddf34a4/attachment.html>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018308.html b/zarb-ml/mageia-dev/2012-August/018308.html new file mode 100644 index 000000000..a385d1431 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018308.html @@ -0,0 +1,107 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Sun Aug 26 16:15:04 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 25/08/12 02:42 did gyre and gimble:
+> On Saturday 25 August 2012 02:33, Olivier Thauvin wrote:
+>> For me obsolete should be reserved for replacements or rename, nothing
+>> more.
+> 
+> I agree on this.
+
+So in two years time, we add a new package with the same filename as one
+of these old package, we may get some very strange edge cases on package
+upgrades/installer because keeping these old, no longer shipped packages
+installed is still "supported" (of course this could happen even if the
+old package were obsoleted properly, due to package install order on
+upgrades)
+
+What about when there are security issues in the old package? Do we just
+drop it and then wash our hands of the whole affair and don't give a
+crap when a user's system is completely compromised?
+
+In my opinion we should run a tight ship. If users want to use something
+we no longer ship, then they still have several choices:
+ 1. Don't install task-obsolete and add it to their skip.list.
+ 2. Do a local compile+install into /usr/local of the software in question
+ 3. Package it and become a contributor (assuming the reason for
+dropping the package was due to a lack of maintainer rather than a
+specific desire/reason (i.e. legal))
+
+For all of these options the user is both informed and can make a very
+clear, concious choice about how they want to proceed and know the
+consequences of doing so.
+
+
+Obsoletes in packages which genuinely replace the old one seem
+reasonable and uncontroversial.
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018309.html b/zarb-ml/mageia-dev/2012-August/018309.html new file mode 100644 index 000000000..b6d42c8e3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018309.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Sander Lepik + sander.lepik at eesti.ee +
+ Sun Aug 26 16:33:22 CEST 2012 +

+
+ +
+Sander
+
+26.08.2012 17:15, Colin Guthrie kirjutas:
+> 'Twas brillig, and Johnny A. Solbu at 25/08/12 02:42 did gyre and gimble:
+>> On Saturday 25 August 2012 02:33, Olivier Thauvin wrote:
+>>> For me obsolete should be reserved for replacements or rename, nothing
+>>> more.
+>> I agree on this.
+> So in two years time, we add a new package with the same filename as one
+> of these old package, we may get some very strange edge cases on package
+> upgrades/installer because keeping these old, no longer shipped packages
+> installed is still "supported" (of course this could happen even if the
+> old package were obsoleted properly, due to package install order on
+> upgrades)
+>
+> What about when there are security issues in the old package? Do we just
+> drop it and then wash our hands of the whole affair and don't give a
+> crap when a user's system is completely compromised?
+>
+> In my opinion we should run a tight ship. If users want to use something
+> we no longer ship, then they still have several choices:
+>  1. Don't install task-obsolete and add it to their skip.list.
+>  2. Do a local compile+install into /usr/local of the software in question
+>  3. Package it and become a contributor (assuming the reason for
+> dropping the package was due to a lack of maintainer rather than a
+> specific desire/reason (i.e. legal))
+>
+> For all of these options the user is both informed and can make a very
+> clear, concious choice about how they want to proceed and know the
+> consequences of doing so.
+>
+>
+> Obsoletes in packages which genuinely replace the old one seem
+> reasonable and uncontroversial.
+>
+> Col
+>
+What about new feature. Some txt file (containing obsoleted package per line and probably
+can be signed somehow) in the mirrors that can be updated by sysadmins. During update urpmi
+will check this file and will compare with local file where user has marked what (s)he wants
+to do with those packages (<obsoleted package> <status: keep/remove> per line). If urpmi
+finds package that hasn't been listed in local file it will ask the user what to do with it
++ will show warning that all possible security problems are not our problem anymore.
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018310.html b/zarb-ml/mageia-dev/2012-August/018310.html new file mode 100644 index 000000000..4ba669e23 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018310.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] ocsinventory & php-gd + + + + + + + + + +

[Mageia-dev] ocsinventory & php-gd

+ Thomas Spuhler + thomas at btspuhler.com +
+ Sun Aug 26 17:41:49 CEST 2012 +

+
+ +
On Sunday, August 26, 2012 03:52:24 AM Bersuit Vera wrote:
+> Hi all.
+> In my  ocsinventory.spec file:
+> 
+> Requires php-gd
+> 
+> ocsinventory builds successfully
+> When I install the package with urpmi:
+> 
+> [root at cualdron64 noarch]# urpmi ocsinventory-*
+> Para satisfacer la dependencia «php-gd», se necesita uno de los paquetes
+> siguientes:
+>  1- php-gd-5.3.15-1.mga2.x86_64: GD extension module for PHP (para
+> instalar) 2- php-gd-bundled-5.3.15-1.mga2.x86_64: GD extension module for
+> PHP (para instalar)
+> ¿Qué elige? (1-2)
+> 
+> What is the difference between php-gd and php-gd-bundled?
+> Why urpmi does not choose the first?
+> 
+> Sorry, i'm novice packager :-)
+> 
+> Best regards
+> 
+> 
+> Bersuit.
+This is the normal behavior. The it requires one of them.
+
+Maybe we should start discussing why do we still provide php-gd-bundled?
+What does it provide other packages dont?
+If we want to have them all-in-one should we make a meta package intsead?
+I think, we just imported it from Mandriva.
+
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018311.html b/zarb-ml/mageia-dev/2012-August/018311.html new file mode 100644 index 000000000..ed4195606 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018311.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] how to upgrade a package with %_preun_service ? + + + + + + + + + +

[Mageia-dev] how to upgrade a package with %_preun_service ?

+ eatdirt + dirteat at gmail.com +
+ Sun Aug 26 19:07:04 CEST 2012 +

+
+ +
Hi there,
+package A is on mga2 and run at uninstall
+%_preun_service myserv
+
+package B (different name) obsoletes package A and at install run
+%_post_service myserv
+
+same name for "myserv".
+
+When I run this, the old package %preun section remove the new service 
+installed by package B. Any idea how to fix this?
+
+Thanks,
+Chris.
+
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018312.html b/zarb-ml/mageia-dev/2012-August/018312.html new file mode 100644 index 000000000..33a5394bb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018312.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Olivier Thauvin + nanardon at nanardon.zarb.org +
+ Sun Aug 26 22:47:06 CEST 2012 +

+
+ +
* Colin Guthrie (mageia at colin.guthr.ie) wrote:
+> In my opinion we should run a tight ship. If users want to use something
+> we no longer ship, then they still have several choices:
+>  1. Don't install task-obsolete and add it to their skip.list.
+
+As obsoletes are automatically promote, there is no way to keep a package
+except adding it to skip.list.
+
+>  3. Package it and become a contributor (assuming the reason for
+> dropping the package was due to a lack of maintainer rather than a
+> specific desire/reason (i.e. legal))
+
+Sys admin work is not to make package.
+
+> 
+> For all of these options the user is both informed and can make a very
+> clear, concious choice about how they want to proceed and know the
+> consequences of doing so.
+
+This system silently remove packages. I am pretty sure a lot of people
+will wonder why some need libraries get removed from their system at
+each update...
+
+-- 
+
+Olivier Thauvin
+CNRS  -  LATMOS
+♖ ♘ ♗ ♕ ♔ ♗ ♘ ♖
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120826/0b140350/attachment.asc>
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018313.html b/zarb-ml/mageia-dev/2012-August/018313.html new file mode 100644 index 000000000..c7dbde099 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018313.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] how to upgrade a package with %_preun_service ? + + + + + + + + + +

[Mageia-dev] how to upgrade a package with %_preun_service ?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Sun Aug 26 22:53:57 CEST 2012 +

+
+ +
On 26 August 2012 19:07, eatdirt <dirteat at gmail.com> wrote:
+> Hi there,
+> package A is on mga2 and run at uninstall
+> %_preun_service myserv
+>
+> package B (different name) obsoletes package A and at install run
+> %_post_service myserv
+>
+> same name for "myserv".
+>
+> When I run this, the old package %preun section remove the new service
+> installed by package B. Any idea how to fix this?
+
+look for %triggerpostun or %posttrans
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018314.html b/zarb-ml/mageia-dev/2012-August/018314.html new file mode 100644 index 000000000..9583775c6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018314.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] Package removal proposal + + + + + + + + + +

[Mageia-dev] Package removal proposal

+ Charles A Edwards + CAE at eslrahc.com +
+ Sun Aug 26 23:35:32 CEST 2012 +

+
+ +
On Sun, 26 Aug 2012 15:15:04 +0100
+Colin Guthrie wrote:
+
+> Obsoletes in packages which genuinely replace the old one seem
+> reasonable and uncontroversial.
+
+It is both reasonable and uncontroversial because the User is given the
+choice.
+
+With obsoletes in packages Before any installation or package removal
+via urpmi/rpmdrake
+1)	user is informed that rpm A must be removed for other rpms to
+	be updated
+2)	user is given the option y/n before the installation/removal
+	proceeds.
+
+If using task-obsolete 
+1)	user does not know Which or When rpm/s will be removed
+2)	user does not know Why the rpm must be removed
+3)	user has no choice as this is all occurring in secret	
+
+
+    Charles
+	
+
+-- 
+// Minor lesson: don't fuck about with something you don't fully
+understand -- the dosdoom source code
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.2-tmb-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120826/bf71619a/attachment-0001.asc>
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018315.html b/zarb-ml/mageia-dev/2012-August/018315.html new file mode 100644 index 000000000..d210ca5cd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018315.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kernel-tmb-3.5.3-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kernel-tmb-3.5.3-1.mga3

+ Charles A Edwards + CAE at eslrahc.com +
+ Mon Aug 27 04:56:37 CEST 2012 +

+
+ +
On Mon, 27 Aug 2012 02:10:04 +0200 (CEST)
+tmb wrote:
+
+> Name        : kernel-tmb                   Relocations: (not
+> relocatable) Version     : 3.5.3                             Vendor:
+> Mageia.Org Release     : 1.mga3                        Build Date:
+> Mon Aug 27 00:41:55 2012 Install Date: (not installed)
+> Build Host: ecosse.mageia.org Group       : System/Kernel and
+> hardware    Source RPM: (none) Size        :
+> 69012881                         License: GPLv2 Signature   : (none)
+> Packager    : tmb <tmb>
+> URL         : http://www.kernel.org
+
+
+This is a curiosity question that has begun to nag at me.
+
+Why/how are the tmb-kernels able to boot soooo much faster than 
+the 'main' kernel?
+
+For those who are not aware I boot to init 3 not to a DM.
+
+This kernel, tmb-3.5.3-1 or any tmb-kernel, boots to the command prompt
+in less than 25 sec.
+On the other hand with the 'main' kernels it takes nearly 2 mins
+to reach the same prompt.
+
+
+    Charles
+
+-- 
+"Time is money and money can't buy you love and I love your outfit"
+- T.H.U.N.D.E.R. #1
+----------------------
+Mageia release 3 (Cauldron) for x86_64$
+On SuperSize....http://www.eslrahc.com
+Registered Linux user #182463
+3.5.3-tmb-server-1.mga3 x86_64
+----------------------
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: signature.asc
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120826/95b0f3de/attachment.asc>
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018316.html b/zarb-ml/mageia-dev/2012-August/018316.html new file mode 100644 index 000000000..e9e25d3a8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018316.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release iurt-0.6.6-1.r5364.1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release iurt-0.6.6-1.r5364.1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 27 05:29:37 CEST 2012 +

+
+ +
On 15 August 2012 16:05, pterjan <buildsystem-daemon at mageia.org> wrote:
+> pterjan <pterjan> 0.6.6-1.r5364.1.mga3:
+> + Revision: 281419
+> - Update to new svn snapshot
+>  * Fixes default media name (s/Main/Core/)
+>  * Improves chroot handling
+>  * Support using btrfs snaphots
+
+can we please do real releases?
+Thanks.
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018317.html b/zarb-ml/mageia-dev/2012-August/018317.html new file mode 100644 index 000000000..d8adce059 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018317.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] [soft-commits] [5307] Initial btrfs support + + + + + + + + + +

[Mageia-dev] [soft-commits] [5307] Initial btrfs support

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 27 06:12:44 CEST 2012 +

+
+ +
On 8 August 2012 10:56, Pascal Terjan <pterjan at gmail.com> wrote:
+>> Initial btrfs support
+>
+> In case someone is interested:
+> - It works fine here
+
+Errr, I've some serious doubts...
+You added a 'config' parameter to clean_all_chroot_tmp()
+... but you never pass it!!!!
+some sudo commands will just fail in some cases...
+
+You would have caught it would you have run perl_checker... :-(
+
+I've fixed it.
+Running iurt locally (not using btrfs) works OK.
+Please check on your end with btrfs.
+
+> - Building a package on my machine takes 12/13s vs 18/20s using a
+> tarball. Savings would be less visible if using tmpfs or a ssd (time
+> savings happen at two times: when creating the chroot we don't need to
+> untar it, and when deleting it we don't need to rm -rf)
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018318.html b/zarb-ml/mageia-dev/2012-August/018318.html new file mode 100644 index 000000000..f7efc02a8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018318.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] [soft-commits] [5307] Initial btrfs support + + + + + + + + + +

[Mageia-dev] [soft-commits] [5307] Initial btrfs support

+ Luis Daniel Lucio Quiroz + dlucio at okay.com.mx +
+ Mon Aug 27 06:18:23 CEST 2012 +

+
+ +
Is it a big change from mga2?
+
+I did test 3 months ago in a 2tb disk, eventually i lost info.
+
+Enviado desde mi DROID 4G LTE de Verizon Wireless
+
+Thierry Vignaud <thierry.vignaud at gmail.com> escribió:
+
+>On 8 August 2012 10:56, Pascal Terjan <pterjan at gmail.com> wrote:
+>>> Initial btrfs support
+>>
+>> In case someone is interested:
+>> - It works fine here
+>
+>Errr, I've some serious doubts...
+>You added a 'config' parameter to clean_all_chroot_tmp()
+>... but you never pass it!!!!
+>some sudo commands will just fail in some cases...
+>
+>You would have caught it would you have run perl_checker... :-(
+>
+>I've fixed it.
+>Running iurt locally (not using btrfs) works OK.
+>Please check on your end with btrfs.
+>
+>> - Building a package on my machine takes 12/13s vs 18/20s using a
+>> tarball. Savings would be less visible if using tmpfs or a ssd (time
+>> savings happen at two times: when creating the chroot we don't need to
+>> untar it, and when deleting it we don't need to rm -rf)
+>Email Shield provided by NOCWorldWide.com
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120826/80ced520/attachment.html>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018319.html b/zarb-ml/mageia-dev/2012-August/018319.html new file mode 100644 index 000000000..0f014c1e7 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018319.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] [soft-commits] [5307] Initial btrfs support + + + + + + + + + +

[Mageia-dev] [soft-commits] [5307] Initial btrfs support

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 27 06:20:17 CEST 2012 +

+
+ +
On 27 August 2012 06:18, Luis Daniel Lucio Quiroz <dlucio at okay.com.mx> wrote:
+> Is it a big change from mga2?
+
+That's a 3 weeks old change that happened in Cauldron.
+
+> I did test 3 months ago in a 2tb disk, eventually i lost info.
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018320.html b/zarb-ml/mageia-dev/2012-August/018320.html new file mode 100644 index 000000000..f0e2e5cda --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018320.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] [soft-commits] [5307] Initial btrfs support + + + + + + + + + +

[Mageia-dev] [soft-commits] [5307] Initial btrfs support

+ AL13N + alien at rmail.be +
+ Mon Aug 27 09:30:12 CEST 2012 +

+
+ +
Op woensdag 8 augustus 2012 09:56:11 schreef Pascal Terjan:
+> On Wed, Aug 8, 2012 at 1:17 AM,  <root at mageia.org> wrote:
+> > Revision 5307 Author pterjan Date 2012-08-08 02:17:24 +0200 (Wed, 08 Aug
+> > 2012)
+> > 
+> > Log Message
+> > 
+> > Initial btrfs support
+> 
+> In case someone is interested:
+> - It works fine here
+> - Building a package on my machine takes 12/13s vs 18/20s using a
+> tarball. Savings would be less visible if using tmpfs or a ssd (time
+> savings happen at two times: when creating the chroot we don't need to
+> untar it, and when deleting it we don't need to rm -rf)
+
+while not using iurt; i do use some kind of chrooted snapshotted testbuild 
+script in btrfs on my development machine on mga2; and it is also pretty fast. 
+mine opens a bash shell in a screen session with everything and when you end 
+the screen session the build is cleaned up
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018321.html b/zarb-ml/mageia-dev/2012-August/018321.html new file mode 100644 index 000000000..a8ae0948a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018321.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] how to upgrade a package with %_preun_service ? + + + + + + + + + +

[Mageia-dev] how to upgrade a package with %_preun_service ?

+ EatDirt + dirteat at gmail.com +
+ Mon Aug 27 09:57:39 CEST 2012 +

+
+ +
On 26/08/12 22:53, Thierry Vignaud wrote:
+
+> look for %triggerpostun or %posttrans
+>
+
+Fantastic! You saved me!!
+
+Cheers.
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018322.html b/zarb-ml/mageia-dev/2012-August/018322.html new file mode 100644 index 000000000..1763b089a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018322.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] How to Test the new uClibc? + + + + + + + + + +

[Mageia-dev] How to Test the new uClibc?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 27 11:03:42 CEST 2012 +

+
+ +
On 9 August 2012 12:40, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>>>>> If busybox tools still work, just go on...
+>>>>>
+>>>>> Ping! It's time to make cauldron hot!
+>>>>
+>>>> I don't know if you attended that IRC conversation, so let me quote it (I am rindolf):
+>
+> (...)
+>
+>>>> So I'm back at square 1, and don't know how to further proceed. If someone more capable than me can take
+>>>> it upon themselves, then it would be great.
+>
+> (...)
+>
+>> Dracut just uses what is on the system, so yeah it'll use glibc unless
+>> some module pulls it in. There is a busybox module in dracut to allow it
+>> to be installed but it's not enabled by default AFAICT.
+>>
+>>> So I don't think it's that much critical.
+>>> At worst, we can check that regenerating initrd on a LVM machine still
+>>> boots.
+>>
+>> My machine is an LVM one, so I can likely test this, but as my current
+>> initrd does not have ulibc in it, I doubt very much this test will show
+>> anything other than success :)
+>
+> So since it's largely unused and doesn't affect much, let's update uclibc
+> and just check that a rebuild busybox tools still work,
+
+ping?
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018323.html b/zarb-ml/mageia-dev/2012-August/018323.html new file mode 100644 index 000000000..cde46114e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018323.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] Servers offline today + + + + + + + + + +

[Mageia-dev] Servers offline today

+ nicolas vigier + boklm at mars-attacks.org +
+ Mon Aug 27 11:16:29 CEST 2012 +

+
+ +
Hello,
+
+As we are going to replace one of the server of the build system and run
+memory tests on the other, the build system will be stopped for a few
+hours today.
+
+We are also going to replace a switch, so the other servers (except
+website and blog) will be down for a few minutes.
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018324.html b/zarb-ml/mageia-dev/2012-August/018324.html new file mode 100644 index 000000000..6637723c5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018324.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Luiz Alberto Saba + las at transauto.com.br +
+ Mon Aug 27 16:23:09 CEST 2012 +

+
+ +
Hi guys
+
+I've done a fresh mageia 2 install (x86_64) to test a new ssd.
+Can I change the resitories to cauldron and do a urpmi --auto-select or 
+it will not work?
+
+Thanks
+
+Luiz Alberto Saba
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018325.html b/zarb-ml/mageia-dev/2012-August/018325.html new file mode 100644 index 000000000..5460f5d0f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018325.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Matteo + pasotti.matteo at gmail.com +
+ Mon Aug 27 16:37:53 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 27/08/2012 16:23, Luiz Alberto Saba wrote:
+> Hi guys
+> 
+> I've done a fresh mageia 2 install (x86_64) to test a new ssd. Can
+> I change the resitories to cauldron and do a urpmi --auto-select
+> or it will not work?
+> 
+> Thanks
+> 
+> Luiz Alberto Saba
+> 
+Yes, you can but you have to pay attention to [1]
+
+Regards,
+
+[1] https://wiki.mageia.org/en/Feature:UsrMove
+- -- 
+Matteo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iQEcBAEBAgAGBQJQO4ZBAAoJED3LowjDDWbN9JgH/1XDJy/tFFFPACHt2+sYnuYH
+g4EmeG54UTb6toeWIBotFkJClxnz1j3nDdCaIyItf0LXXwLTFRh6ti8KbXQzFcc3
+yCq1TAFoqrcE9O/o6FbqJlZtYMCXR8KoLOcF7qStXjPCORuGuNQ22mMdkEXJrrwk
+33bxWoFxMQowSSHoYgTd4VbKtNzYlh6uWVcpOEeKYigRw6ut4x6VqUBoh/ECasIj
+KyK1SuUn/BNR2hc1Zh2W/BQBGdSKD/rAmGVD06rC9nLvSD1PimoMhy40/HqsZKAL
+PP3KItpwbaNbw6Ploc6Ix34/gm8DiJ++ELcRDBbGdEd5b35BTABu8wYfZdHwxyA=
+=+OJZ
+-----END PGP SIGNATURE-----
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018326.html b/zarb-ml/mageia-dev/2012-August/018326.html new file mode 100644 index 000000000..da77795f0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018326.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Mon Aug 27 16:38:44 CEST 2012 +

+
+ +
'Twas brillig, and Luiz Alberto Saba at 27/08/12 15:23 did gyre and gimble:
+> Hi guys
+> 
+> I've done a fresh mageia 2 install (x86_64) to test a new ssd.
+> Can I change the resitories to cauldron and do a urpmi --auto-select or
+> it will not work?
+
+Install the update rpm package from mga2 updates_testing first, then
+switch your repos and "urpmi dracut" and follow the instructions from
+step 2 on https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes.
+
+After following these steps the rest of the auto-select/upgrade should
+go smoothly.
+
+Let me know if there are any issues.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018327.html b/zarb-ml/mageia-dev/2012-August/018327.html new file mode 100644 index 000000000..563d6dabf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018327.html @@ -0,0 +1,85 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Mon Aug 27 16:39:41 CEST 2012 +

+
+ +
2012/8/27 Matteo <pasotti.matteo at gmail.com>:
+> -----BEGIN PGP SIGNED MESSAGE-----
+> Hash: SHA1
+>
+> On 27/08/2012 16:23, Luiz Alberto Saba wrote:
+>> Hi guys
+>>
+>> I've done a fresh mageia 2 install (x86_64) to test a new ssd. Can
+>> I change the resitories to cauldron and do a urpmi --auto-select
+>> or it will not work?
+>>
+>> Thanks
+>>
+>> Luiz Alberto Saba
+>>
+> Yes, you can but you have to pay attention to [1]
+>
+> Regards,
+>
+> [1] https://wiki.mageia.org/en/Feature:UsrMove
+
+Because of this change I'd rather install MGA3 Alpha1 (due Sept 4)
+
+-- 
+wobo
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018328.html b/zarb-ml/mageia-dev/2012-August/018328.html new file mode 100644 index 000000000..c9098c00a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018328.html @@ -0,0 +1,70 @@ + + + + [Mageia-dev] BS is stopped + + + + + + + + + +

[Mageia-dev] BS is stopped

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Mon Aug 27 19:28:35 CEST 2012 +

+
+ +
Hi
+It looks like BS is stopped for 10 hours...
+Can someone kick it?
+
+Thx
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018329.html b/zarb-ml/mageia-dev/2012-August/018329.html new file mode 100644 index 000000000..b45828685 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018329.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] BS is stopped + + + + + + + + + +

[Mageia-dev] BS is stopped

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Mon Aug 27 19:32:28 CEST 2012 +

+
+ +
Le lundi 27 août 2012 19:28:35 Thierry Vignaud a écrit :
+> Hi
+> It looks like BS is stopped for 10 hours...
+> Can someone kick it?
+> 
+> Thx
+
+Some ppl are in Marseilles to change some machines so this is normal see 
+"[Mageia-dev] Servers offline today"
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018330.html b/zarb-ml/mageia-dev/2012-August/018330.html new file mode 100644 index 000000000..121627219 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018330.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ AL13N + alien at rmail.be +
+ Tue Aug 28 01:55:26 CEST 2012 +

+
+ +
Op maandag 27 augustus 2012 19:28:35 schreef Thierry Vignaud:
+> Hi
+> It looks like BS is stopped for 10 hours...
+> Can someone kick it?
+> 
+> Thx
+
+IINM the BS was stopped due to the work being done on-site.
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018331.html b/zarb-ml/mageia-dev/2012-August/018331.html new file mode 100644 index 000000000..5763aba22 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018331.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Thomas Spuhler + thomas at btspuhler.com +
+ Tue Aug 28 03:50:14 CEST 2012 +

+
+ +
On Monday, August 27, 2012 07:38:44 AM Colin Guthrie wrote:
+> 'Twas brillig, and Luiz Alberto Saba at 27/08/12 15:23 did gyre and gimble:
+> > Hi guys
+> > 
+> > I've done a fresh mageia 2 install (x86_64) to test a new ssd.
+> > Can I change the resitories to cauldron and do a urpmi --auto-select or
+> > it will not work?
+> 
+> Install the update rpm package from mga2 updates_testing first, then
+> switch your repos and "urpmi dracut" and follow the instructions from
+> step 2 on https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes.
+> 
+> After following these steps the rest of the auto-select/upgrade should
+> go smoothly.
+> 
+> Let me know if there are any issues.
+> 
+> Col
+
+And if you upgrade from 2, then be very, very patient. You will see a lot of 
+errors when booting and and you need to wait for timeouts to happen. The /usr 
+move kind of happens randomly. You may need to try a few times.  Calculate 
+about 1/2 hour to boot, but eventually you should get there.
+
+This is on a virtual box.
+-- 
+Best regards
+Thomas Spuhler
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018332.html b/zarb-ml/mageia-dev/2012-August/018332.html new file mode 100644 index 000000000..b8c318699 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018332.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ Sandro CAZZANIGA + cazzaniga.sandro at gmail.com +
+ Tue Aug 28 07:54:50 CEST 2012 +

+
+ +
2012/8/28 AL13N <alien at rmail.be>:
+> Op maandag 27 augustus 2012 19:28:35 schreef Thierry Vignaud:
+>> Hi
+>> It looks like BS is stopped for 10 hours...
+>> Can someone kick it?
+>>
+>> Thx
+>
+> IINM the BS was stopped due to the work being done on-site.
+
+Hi guys,
+
+Is the bs up today?
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018333.html b/zarb-ml/mageia-dev/2012-August/018333.html new file mode 100644 index 000000000..651418669 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018333.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] Servers offline today + + + + + + + + + +

[Mageia-dev] Servers offline today

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 28 09:22:05 CEST 2012 +

+
+ +
On 27 August 2012 11:16, nicolas vigier <boklm at mars-attacks.org> wrote:
+> Hello,
+>
+> As we are going to replace one of the server of the build system and run
+> memory tests on the other, the build system will be stopped for a few
+> hours today.
+>
+> We are also going to replace a switch, so the other servers (except
+> website and blog) will be down for a few minutes.
+
+Can we get an update status as BS is stopped for a day now?
+Thx
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018334.html b/zarb-ml/mageia-dev/2012-August/018334.html new file mode 100644 index 000000000..e9f936e3c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018334.html @@ -0,0 +1,130 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 28 10:11:06 CEST 2012 +

+
+ +
'Twas brillig, and Thomas Spuhler at 28/08/12 02:50 did gyre and gimble:
+> On Monday, August 27, 2012 07:38:44 AM Colin Guthrie wrote:
+>> 'Twas brillig, and Luiz Alberto Saba at 27/08/12 15:23 did gyre and gimble:
+>>> Hi guys
+>>>
+>>> I've done a fresh mageia 2 install (x86_64) to test a new ssd.
+>>> Can I change the resitories to cauldron and do a urpmi --auto-select or
+>>> it will not work?
+>>
+>> Install the update rpm package from mga2 updates_testing first, then
+>> switch your repos and "urpmi dracut" and follow the instructions from
+>> step 2 on https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes.
+>>
+>> After following these steps the rest of the auto-select/upgrade should
+>> go smoothly.
+>>
+>> Let me know if there are any issues.
+>>
+>> Col
+> 
+> And if you upgrade from 2, then be very, very patient. You will see a lot of 
+> errors when booting and and you need to wait for timeouts to happen. The /usr 
+> move kind of happens randomly.
+
+It certainly shouldn't behave that way! It certainly doesn't "happen
+randomly", it happens when you specifically tell it to happen via a
+kernel command line argument and if you're on the same filesystem for
+both / and /usr then the whole process will usually take < 1 minute
+(depending on disk speed and number of packages).
+
+There should be NO timeouts (or at least no *more* timeouts than usual!
+:p) The usrmove part of the initrd is just a script that is run at the
+right point and has absolutely zero bearing on any timeouts.
+
+I've not seen any bug report about this behaviour (other than what has
+been discussed and resolved on this list), so if you have such reports,
+please do share them.
+
+The new dracut was problematic due to various incompatibilities and
+issues introduced by half updated systems in cauldron, but upgrading
+from mga2 should, in theory at least, be much smoother.
+
+> You may need to try a few times.  Calculate 
+> about 1/2 hour to boot, but eventually you should get there.
+> 
+> This is on a virtual box.
+
+Can you give more details. If it's VB then any strange timeouts etc.
+should be easy to reproduce. I have of course ran this upgrade about 20
+times inside virtual box and even when they were on separate partitions
+it didn't take more than a few minutes to copy the files.
+
+I'd really like to get to the bottom of any issue, but I need specifics!
+
+Cheers
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018335.html b/zarb-ml/mageia-dev/2012-August/018335.html new file mode 100644 index 000000000..9c564985f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018335.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] Servers offline today + + + + + + + + + +

[Mageia-dev] Servers offline today

+ nicolas vigier + boklm at mars-attacks.org +
+ Tue Aug 28 10:17:46 CEST 2012 +

+
+ +
On Tue, 28 Aug 2012, Thierry Vignaud wrote:
+
+> On 27 August 2012 11:16, nicolas vigier <boklm at mars-attacks.org> wrote:
+> > Hello,
+> >
+> > As we are going to replace one of the server of the build system and run
+> > memory tests on the other, the build system will be stopped for a few
+> > hours today.
+> >
+> > We are also going to replace a switch, so the other servers (except
+> > website and blog) will be down for a few minutes.
+> 
+> Can we get an update status as BS is stopped for a day now?
+> Thx
+
+It should come back sometime today.
+
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018336.html b/zarb-ml/mageia-dev/2012-August/018336.html new file mode 100644 index 000000000..b3e0086fe --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018336.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Matteo + pasotti.matteo at gmail.com +
+ Tue Aug 28 10:42:38 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 28/08/2012 03:50, Thomas Spuhler wrote:
+> On Monday, August 27, 2012 07:38:44 AM Colin Guthrie wrote:
+>> 'Twas brillig, and Luiz Alberto Saba at 27/08/12 15:23 did gyre
+>> and gimble:
+>>> Hi guys
+>>> 
+>>> I've done a fresh mageia 2 install (x86_64) to test a new ssd. 
+>>> Can I change the resitories to cauldron and do a urpmi
+>>> --auto-select or it will not work?
+>> 
+>> Install the update rpm package from mga2 updates_testing first,
+>> then switch your repos and "urpmi dracut" and follow the
+>> instructions from step 2 on
+>> https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes.
+>> 
+>> After following these steps the rest of the auto-select/upgrade
+>> should go smoothly.
+>> 
+>> Let me know if there are any issues.
+>> 
+>> Col
+> 
+> And if you upgrade from 2, then be very, very patient. You will see
+> a lot of errors when booting and and you need to wait for timeouts
+> to happen. The /usr move kind of happens randomly. You may need to
+> try a few times.  Calculate about 1/2 hour to boot, but eventually
+> you should get there.
+> 
+> This is on a virtual box.
+FYI, I have not experienced such a thing on a virtual machine
+(virtualbox and vmware) neither on a real machine.
+Regards,
+- -- 
+Matteo
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iQEcBAEBAgAGBQJQPIR6AAoJED3LowjDDWbNrwsIALzhcmeg9WPvRAIhvnVigLK1
+/Cm1XJV4k2SkBJhpmWMcyvfWYkCPVDhDA6PCrJ8pM1chU769wCaZ1seo0Zrycl8+
+AEmuu7i81mnuNMB/a3JUAP7s8JAhcz1Ayjy0QmtMZzM3BYxu8VtRvY3mn/GptA21
+qXtTexNS+K0zwQaD5QXqdkPpMzPdXiq/sQ0Cv8CiySkDjVFapl8gpx0KfScRXsU7
+MsxqaQYuc71rfE9UHnyXBURErCit8izrxM5sIydRNcWGRrP2FHL4s3VHC0fFZFex
+HvplzdjZPRmO6keI8lHvSyceMxlbNH01l2SXGF0laY/Rlx53QvtV5trqnI0ImEw=
+=BVXM
+-----END PGP SIGNATURE-----
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018337.html b/zarb-ml/mageia-dev/2012-August/018337.html new file mode 100644 index 000000000..8f3b83242 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018337.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Mageia 2 can be turned to cauldron actually? + + + + + + + + + +

[Mageia-dev] Mageia 2 can be turned to cauldron actually?

+ Luiz Alberto Saba + las at transauto.com.br +
+ Tue Aug 28 13:44:37 CEST 2012 +

+
+ +
Em 27-08-2012 11:38, Colin Guthrie escreveu:
+> 'Twas brillig, and Luiz Alberto Saba at 27/08/12 15:23 did gyre and gimble:
+>> Hi guys
+>>
+>> I've done a fresh mageia 2 install (x86_64) to test a new ssd.
+>> Can I change the resitories to cauldron and do a urpmi --auto-select or
+>> it will not work?
+> Install the update rpm package from mga2 updates_testing first, then
+> switch your repos and "urpmi dracut" and follow the instructions from
+> step 2 on https://wiki.mageia.org/en/Feature:UsrMove#Release_Notes.
+>
+> After following these steps the rest of the auto-select/upgrade should
+> go smoothly.
+>
+> Let me know if there are any issues.
+>
+> Col
+>
+>
+Thank you, Colin!
+
+It worked very fine.
+Just some conflicts & dependencies that were solved running urpmi 
+--auto-select a second time.
+
+Thanks again
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018338.html b/zarb-ml/mageia-dev/2012-August/018338.html new file mode 100644 index 000000000..2c4c7d5ec --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018338.html @@ -0,0 +1,70 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Tue Aug 28 17:56:36 CEST 2012 +

+
+ +
On 28 August 2012 07:54, Sandro CAZZANIGA <cazzaniga.sandro at gmail.com> wrote:
+>> IINM the BS was stopped due to the work being done on-site.
+>
+> Hi guys,
+>
+> Is the bs up today?
+
+It looks like it has been restarted after the maintenance done in the
+datacenter.
+However, mails are no more sent when packages are uploaded.
+Is that a side effect of the switch of servers?
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018339.html b/zarb-ml/mageia-dev/2012-August/018339.html new file mode 100644 index 000000000..e013ffa52 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018339.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ Pascal Terjan + pterjan at gmail.com +
+ Tue Aug 28 18:06:57 CEST 2012 +

+
+ +
On Tue, Aug 28, 2012 at 4:56 PM, Thierry Vignaud
+<thierry.vignaud at gmail.com> wrote:
+> On 28 August 2012 07:54, Sandro CAZZANIGA <cazzaniga.sandro at gmail.com> wrote:
+>>> IINM the BS was stopped due to the work being done on-site.
+>>
+>> Hi guys,
+>>
+>> Is the bs up today?
+>
+> It looks like it has been restarted after the maintenance done in the
+> datacenter.
+> However, mails are no more sent when packages are uploaded.
+> Is that a side effect of the switch of servers?
+
+Mails are sent but ML seems broken
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018340.html b/zarb-ml/mageia-dev/2012-August/018340.html new file mode 100644 index 000000000..4fb81bcf6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018340.html @@ -0,0 +1,115 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ Pascal Terjan + pterjan at gmail.com +
+ Tue Aug 28 18:09:16 CEST 2012 +

+
+ +
On Tue, Aug 28, 2012 at 5:06 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+> On Tue, Aug 28, 2012 at 4:56 PM, Thierry Vignaud
+> <thierry.vignaud at gmail.com> wrote:
+>> On 28 August 2012 07:54, Sandro CAZZANIGA <cazzaniga.sandro at gmail.com> wrote:
+>>>> IINM the BS was stopped due to the work being done on-site.
+>>>
+>>> Hi guys,
+>>>
+>>> Is the bs up today?
+>>
+>> It looks like it has been restarted after the maintenance done in the
+>> datacenter.
+>> However, mails are no more sent when packages are uploaded.
+>> Is that a side effect of the switch of servers?
+>
+> Mails are sent but ML seems broken
+
+[root at alamut ~]# /etc/init.d/sympa status
+sympa.pl is stopped
+bulk.pl is stopped
+archived.pl (pid  3160) is running...
+bounced.pl (pid  3174) is running...
+task_manager.pl (pid  3186) is running...
+[root at alamut ~]# /etc/init.d/sympa start
+sympa is already running
+[root at alamut ~]# /etc/init.d/sympa restart
+Stopping bounced:
+
+                   [  OK  ]
+Stopping archived:
+
+                   [  OK  ]
+Stopping task_manager:
+
+                   [  OK  ]
+Starting sympa:
+
+                   [  OK  ]
+Starting bulk:
+
+                   [  OK  ]
+Starting archived:
+
+                   [  OK  ]
+Starting bounced:
+
+                   [  OK  ]
+Starting task_manager:
+
+                   [  OK  ]
+[root at alamut ~]# /etc/init.d/sympa status
+sympa.pl (pid  20720) is running...
+bulk.pl (pid  20733) is running...
+archived.pl (pid  20751) is running...
+bounced.pl (pid  20762) is running...
+task_manager.pl (pid  20773) is running...
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018341.html b/zarb-ml/mageia-dev/2012-August/018341.html new file mode 100644 index 000000000..36f041048 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018341.html @@ -0,0 +1,88 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ Thomas Backlund + tmb at mageia.org +
+ Tue Aug 28 19:21:08 CEST 2012 +

+
+ +
28.08.2012 19:09, Pascal Terjan skrev:
+> On Tue, Aug 28, 2012 at 5:06 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+>> On Tue, Aug 28, 2012 at 4:56 PM, Thierry Vignaud
+>> <thierry.vignaud at gmail.com> wrote:
+>>> On 28 August 2012 07:54, Sandro CAZZANIGA <cazzaniga.sandro at gmail.com> wrote:
+>>>>> IINM the BS was stopped due to the work being done on-site.
+>>>>
+>>>> Hi guys,
+>>>>
+>>>> Is the bs up today?
+>>>
+>>> It looks like it has been restarted after the maintenance done in the
+>>> datacenter.
+>>> However, mails are no more sent when packages are uploaded.
+>>> Is that a side effect of the switch of servers?
+>>
+>> Mails are sent but ML seems broken
+>
+> [root at alamut ~]# /etc/init.d/sympa status
+> sympa.pl is stopped
+> bulk.pl is stopped
+
+Yep. Sympa died when it lost contact with the ldap and its db
+
+--
+
+Thomas
+
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018342.html b/zarb-ml/mageia-dev/2012-August/018342.html new file mode 100644 index 000000000..ca81194ed --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018342.html @@ -0,0 +1,103 @@ + + + + [Mageia-dev] [Mageia-sysadm] BS is stopped + + + + + + + + + +

[Mageia-dev] [Mageia-sysadm] BS is stopped

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Tue Aug 28 19:48:07 CEST 2012 +

+
+ +
'Twas brillig, and Thomas Backlund at 28/08/12 18:21 did gyre and gimble:
+> 28.08.2012 19:09, Pascal Terjan skrev:
+>> On Tue, Aug 28, 2012 at 5:06 PM, Pascal Terjan <pterjan at gmail.com> wrote:
+>>> On Tue, Aug 28, 2012 at 4:56 PM, Thierry Vignaud
+>>> <thierry.vignaud at gmail.com> wrote:
+>>>> On 28 August 2012 07:54, Sandro CAZZANIGA
+>>>> <cazzaniga.sandro at gmail.com> wrote:
+>>>>>> IINM the BS was stopped due to the work being done on-site.
+>>>>>
+>>>>> Hi guys,
+>>>>>
+>>>>> Is the bs up today?
+>>>>
+>>>> It looks like it has been restarted after the maintenance done in the
+>>>> datacenter.
+>>>> However, mails are no more sent when packages are uploaded.
+>>>> Is that a side effect of the switch of servers?
+>>>
+>>> Mails are sent but ML seems broken
+>>
+>> [root at alamut ~]# /etc/init.d/sympa status
+>> sympa.pl is stopped
+>> bulk.pl is stopped
+> 
+> Yep. Sympa died when it lost contact with the ldap and its db
+
+Roll on a set of split up systemd units with automatic restart :)
+
+Col
+
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018343.html b/zarb-ml/mageia-dev/2012-August/018343.html new file mode 100644 index 000000000..2c68e459c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018343.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ eatdirt + dirteat at gmail.com +
+ Wed Aug 29 00:39:01 CEST 2012 +

+
+ +
Sorry to ask for help (again) but I have a locally unreproducible build 
+failure on the BS, I am so desperate that I am suspecting a date/time shift:
+
+Does this suffix shows the time on the BS?
+
+0.20120828222902
+
+Is it 28/08/2012? If yes, that's a few hours late and would explain my 
+build failures, never at the same file/location:
+
+<<
+Error: Corrupted compiled interface
+src/utils/net/anyEndian.cmi
+ >>
+
+for which the ocaml user manual says:
+
+<<
+The compiler produces this error when it tries to read a compiled 
+interface file (.cmi file) that has the wrong structure. This means 
+something went wrong when this .cmi file was written: the disk was full, 
+the compiler was interrupted in the middle of the file creation, and so 
+on. This error can also appear if a .cmi file is modified after its 
+creation by the compiler. Fix: remove the corrupted .cmi file, and 
+rebuild it.
+ >>
+
+Any ideas or hints welcome!
+
+Cheers,
+Chris.
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018344.html b/zarb-ml/mageia-dev/2012-August/018344.html new file mode 100644 index 000000000..0fa31cf9d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018344.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ Pierre-Malo Deniélou + pierre-malo.denielou at rhul.ac.uk +
+ Wed Aug 29 00:42:50 CEST 2012 +

+
+ +
Le 28/08/12 23:39,eatdirt nous adresse ces quelques mots :
+> Sorry to ask for help (again) but I have a locally unreproducible build
+> failure on the BS, I am so desperate that I am suspecting a date/time
+> shift:
+> 
+> Does this suffix shows the time on the BS?
+> 
+> 0.20120828222902
+> 
+> Is it 28/08/2012? If yes, that's a few hours late and would explain my
+> build failures, never at the same file/location:
+> 
+> <<
+> Error: Corrupted compiled interface
+> src/utils/net/anyEndian.cmi
+>>>
+> 
+> for which the ocaml user manual says:
+> 
+> <<
+> The compiler produces this error when it tries to read a compiled
+> interface file (.cmi file) that has the wrong structure. This means
+> something went wrong when this .cmi file was written: the disk was full,
+> the compiler was interrupted in the middle of the file creation, and so
+> on. This error can also appear if a .cmi file is modified after its
+> creation by the compiler. Fix: remove the corrupted .cmi file, and
+> rebuild it.
+>>>
+> 
+> Any ideas or hints welcome!
+
+Maybe it's because of the -j24 in %make: try 'make' instead.
+
+Cheers,
+-- 
+Malo
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018345.html b/zarb-ml/mageia-dev/2012-August/018345.html new file mode 100644 index 000000000..3ddba13fe --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018345.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ Remco Rijnders + remco at webconquest.com +
+ Wed Aug 29 05:07:06 CEST 2012 +

+
+ +
On Wed, Aug 29, 2012 at 12:39:01AM +0200, eatdirt wrote in 
+<k1jha6$ql2$1 at ger.gmane.org>:
+>Sorry to ask for help (again) but I have a locally unreproducible 
+>build failure on the BS, I am so desperate that I am suspecting a 
+>date/time shift:
+>
+>Does this suffix shows the time on the BS?
+>
+>0.20120828222902
+>
+>Is it 28/08/2012? If yes, that's a few hours late and would explain 
+>my build failures, never at the same file/location:
+
+Well, could it be that that timestamp is based on UTC? In other words, 
+currently a 2 hour offset from Paris CET?
+
+That said, I did notice yesterday that pkgsubmit.mageia.org at some point 
+did display things like "Submitted -1141 seconds ago", so it could well be 
+that the clock still is off too.
+
+Remmy
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 836 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120829/f7a9a352/attachment-0001.asc>
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018346.html b/zarb-ml/mageia-dev/2012-August/018346.html new file mode 100644 index 000000000..6bd508ceb --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018346.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 29 07:35:57 CEST 2012 +

+
+ +
On 29 August 2012 05:07, Remco Rijnders <remco at webconquest.com> wrote:
+>> Does this suffix shows the time on the BS?
+>>
+>> 0.20120828222902
+>>
+>> Is it 28/08/2012? If yes, that's a few hours late and would explain my
+>> build failures, never at the same file/location:
+>
+>
+> Well, could it be that that timestamp is based on UTC? In other words,
+> currently a 2 hour offset from Paris CET?
+>
+> That said, I did notice yesterday that pkgsubmit.mageia.org at some point
+> did display things like "Submitted -1141 seconds ago", so it could well be
+> that the clock still is off too.
+
+See https://bugs.mageia.org/show_bug.cgi?id=7228
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018347.html b/zarb-ml/mageia-dev/2012-August/018347.html new file mode 100644 index 000000000..3aa278d47 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018347.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ EatDirt + dirteat at gmail.com +
+ Wed Aug 29 10:04:41 CEST 2012 +

+
+ +
On 29/08/12 00:42, Pierre-Malo Deniélou wrote:
+
+> Maybe it's because of the -j24 in %make: try 'make' instead.
+
+Fantastic, that was it, you saved me too!! :)
+
+Thanks!!
+
+
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018348.html b/zarb-ml/mageia-dev/2012-August/018348.html new file mode 100644 index 000000000..7ce8c5266 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018348.html @@ -0,0 +1,68 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Aug 29 10:51:10 CEST 2012 +

+
+ +
On Wed, Aug 29, 2012 at 9:04 AM, EatDirt <dirteat at gmail.com> wrote:
+> On 29/08/12 00:42, Pierre-Malo Deniélou wrote:
+>
+>> Maybe it's because of the -j24 in %make: try 'make' instead.
+>
+>
+> Fantastic, that was it, you saved me too!! :)
+
+Then the proper fix is to fix the makefile and send it upstream
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018349.html b/zarb-ml/mageia-dev/2012-August/018349.html new file mode 100644 index 000000000..224e60baa --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018349.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release augeas-0.10.0-3.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release augeas-0.10.0-3.mga3

+ Olivier Blin + mageia at blino.org +
+ Wed Aug 29 11:57:12 CEST 2012 +

+
+ +
spuhler <buildsystem-daemon at mageia.org> writes:
+
+> Name        : augeas                       Relocations: (not relocatable)
+> Version     : 0.10.0                            Vendor: Mageia.Org
+> Release     : 3.mga3                        Build Date: Tue Aug 28 18:21:50 2012
+> Install Date: (not installed)               Build Host: jonund.mageia.org
+> Group       : Development/C                 Source RPM: (none)
+> Size        : 1685662                          License: LGPv2.1+
+> Signature   : (none)
+> Packager    : spuhler <spuhler>
+> URL         : http://augeas.net/
+> Summary     : A library for changing configuration files
+
+[...]
+
+> spuhler <spuhler> 0.10.0-3.mga3:
+> + Revision: 284648
+> - drop .la files
+> - rebuild against new gnulibs and with no-gets patch
+
+Hi,
+
+There's a file conflict to be fixed:
+
+Installation failed:    file /usr/lib64/libfa.so.1.3.5 from install of
+lib64fa1-0.10.0-3.mga3.x86_64 conflicts with file from package lib64augeas0-0.10.0-1.mga3.x86_64
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018350.html b/zarb-ml/mageia-dev/2012-August/018350.html new file mode 100644 index 000000000..f4bbea182 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018350.html @@ -0,0 +1,119 @@ + + + + [Mageia-dev] [packages-commits] [285454] Adding support for rxvt-unicode-256 (bug 6835) + + + + + + + + + +

[Mageia-dev] [packages-commits] [285454] Adding support for rxvt-unicode-256 (bug 6835)

+ Jani Välimaa + jani.valimaa at gmail.com +
+ Wed Aug 29 15:16:30 CEST 2012 +

+
+ +
On 29.08.2012 13:05, root at mageia.org wrote:
+> Revision
+>     285454
+> Author
+>     eatdirt
+> Date
+>     2012-08-29 12:05:59 +0200 (Wed, 29 Aug 2012)
+> 
+> 
+>       Log Message
+> 
+> Adding support for rxvt-unicode-256 (bug 6835)
+> 
+> 
+>       Modified Paths
+> 
+>   * updates/2/ncurses/current/SPECS/ncurses.spec
+>     <#updates2ncursescurrentSPECSncursesspec>
+> 
+> Modified: updates/2/ncurses/current/SPECS/ncurses.spec
+> ===================================================================
+> --- updates/2/ncurses/current/SPECS/ncurses.spec	2012-08-29 10:04:51 UTC (rev 285453)
+> +++ updates/2/ncurses/current/SPECS/ncurses.spec	2012-08-29 10:05:59 UTC (rev 285454)
+> @@ -2,6 +2,7 @@
+>  %define patchdate 20110108
+>  %define version 5.9
+>  %define release %mkrel 6
+> +%define subrel 1
+>  %define major 5
+>  %define majorminor 5.9
+>  %define utf8libname %mklibname %{name}w %{major}
+> @@ -25,7 +26,7 @@
+>  Patch1:		ncurses-5.6-xterm-debian.patch
+>  Patch2:		ncurses-5.9-20111224-patch.sh.bz2
+>  Patch3:		ncurses-5.9-20111231-20120204.patch.bz2
+> -Patch7:		ncurses-5.7-urxvt.patch
+> +Patch7:		ncurses-5.9-urxvt.patch
+>  # Patch >100 from here:
+>  # ftp://invisible-island.net/ncurses/5.7/
+>  BuildRequires:	gpm-devel
+> @@ -115,7 +116,7 @@
+>  
+>  %patch2 -p1 -b .update
+>  %patch3 -p1 -b .update2
+> -%patch7 -p0 -b .urxvt
+> +%patch7 -p1 -b .urxvt
+>  
+>  # regenerating configure needs patched autoconf, so modify configure
+>  # directly
+> 
+
+Hi,
+
+When rediffing patches, please use 'svn mv' so the patch history doesn't
+get lost. (Rediff patch, svn mv to new name, edit .spec and commit changes).
+
+Also, please don't use 'mgarepo sync -c', it's not needed and shouldn't
+be used anymore. Just edit .spec, DL new sources, do mgarepo sync and
+commit changes in .spec and sha1.lst.
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018351.html b/zarb-ml/mageia-dev/2012-August/018351.html new file mode 100644 index 000000000..feec27f04 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018351.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Olivier Blin + mageia at blino.org +
+ Wed Aug 29 15:36:05 CEST 2012 +

+
+ +
colin <buildsystem-daemon at mageia.org> writes:
+
+> Name        : systemd                      Relocations: (not relocatable)
+> Version     : 189                               Vendor: Mageia.Org
+> Release     : 2.mga3                        Build Date: Tue Aug 28 19:49:16 2012
+
+[...]
+
+> colin <colin> 189-2.mga3:
+> + Revision: 284851
+> - Drop /proc/bus/usb mount as it's no longer available with kernels >= 3.5
+
+Is there any migration to do in drakx and ldetect because of this?
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018352.html b/zarb-ml/mageia-dev/2012-August/018352.html new file mode 100644 index 000000000..fb1604fa8 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018352.html @@ -0,0 +1,104 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Wed Aug 29 15:46:46 CEST 2012 +

+
+ +
'Twas brillig, and Olivier Blin at 29/08/12 14:36 did gyre and gimble:
+> colin <buildsystem-daemon at mageia.org> writes:
+> 
+>> Name        : systemd                      Relocations: (not relocatable)
+>> Version     : 189                               Vendor: Mageia.Org
+>> Release     : 2.mga3                        Build Date: Tue Aug 28 19:49:16 2012
+> 
+> [...]
+> 
+>> colin <colin> 189-2.mga3:
+>> + Revision: 284851
+>> - Drop /proc/bus/usb mount as it's no longer available with kernels >= 3.5
+> 
+> Is there any migration to do in drakx and ldetect because of this?
+
+Oh yeah I meant to send a message to the list about this.
+
+Yeah because we're now on kernel 3.5 we can no longer do certain things
+relating to this mount point.
+
+IIRC some ldetect stuff used it and some of the 3G and/or
+printer/scanner stuff might also depend on it and need to be migrated
+too. I don't know that code very well, but I know some folks complained
+when we stopped mounting it by default, so I've no doubt that it's use
+is lurking somewhere!
+
+I would guess that in some cases /dev/bus/usb/ might be sufficient for
+what is needed.
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018353.html b/zarb-ml/mageia-dev/2012-August/018353.html new file mode 100644 index 000000000..819a01ee4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018353.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] date/time on the BS? + + + + + + + + + +

[Mageia-dev] date/time on the BS?

+ EatDirt + dirteat at gmail.com +
+ Wed Aug 29 16:00:53 CEST 2012 +

+
+ +
On 29/08/12 10:51, Pascal Terjan wrote:
+> On Wed, Aug 29, 2012 at 9:04 AM, EatDirt<dirteat at gmail.com>  wrote:
+
+> Then the proper fix is to fix the makefile and send it upstream
+>
+
+Ok! I have simply reported the bug upstream for the time being...
+
+Thanks.
+Chris.
+
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018354.html b/zarb-ml/mageia-dev/2012-August/018354.html new file mode 100644 index 000000000..ef14871cd --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018354.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 29 16:06:50 CEST 2012 +

+
+ +
On 29 August 2012 15:46, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>> Is there any migration to do in drakx and ldetect because of this?
+>
+> Oh yeah I meant to send a message to the list about this.
+>
+> Yeah because we're now on kernel 3.5 we can no longer do certain things
+> relating to this mount point.
+>
+> IIRC some ldetect stuff used it and some of the 3G and/or
+> printer/scanner stuff might also depend on it and need to be migrated
+> too. I don't know that code very well, but I know some folks complained
+> when we stopped mounting it by default, so I've no doubt that it's use
+> is lurking somewhere!
+>
+> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+> what is needed.
+
+Humm...
+I've still around a patch making ldetect using libusb.
+Sadly, we're missing some data...
+Basically we would miss the kernel driver name binded with each usb device.
+
+We cannot workaround it since libusb misses with the ability to either
+query the sysfs device path or to got the Port number
+("Port" in /proc/bus/usb/devices).
+(I miss the Port number in order to compute the
+/sys/bus/devices/usb/foobar path)
+
+W/o that I cannot retrieve the modalias which would help me to get the kernel
+driver name.
+
+I guess I'll have to resurect that work and try harder to find some
+workaround...
+
+See you
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018355.html b/zarb-ml/mageia-dev/2012-August/018355.html new file mode 100644 index 000000000..02ef834ca --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018355.html @@ -0,0 +1,97 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Pascal Terjan + pterjan at gmail.com +
+ Wed Aug 29 16:13:17 CEST 2012 +

+
+ +
On Wed, Aug 29, 2012 at 3:06 PM, Thierry Vignaud
+<thierry.vignaud at gmail.com> wrote:
+> On 29 August 2012 15:46, Colin Guthrie <mageia at colin.guthr.ie> wrote:
+>>> Is there any migration to do in drakx and ldetect because of this?
+>>
+>> Oh yeah I meant to send a message to the list about this.
+>>
+>> Yeah because we're now on kernel 3.5 we can no longer do certain things
+>> relating to this mount point.
+>>
+>> IIRC some ldetect stuff used it and some of the 3G and/or
+>> printer/scanner stuff might also depend on it and need to be migrated
+>> too. I don't know that code very well, but I know some folks complained
+>> when we stopped mounting it by default, so I've no doubt that it's use
+>> is lurking somewhere!
+>>
+>> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+>> what is needed.
+>
+> Humm...
+> I've still around a patch making ldetect using libusb.
+> Sadly, we're missing some data...
+> Basically we would miss the kernel driver name binded with each usb device.
+>
+> We cannot workaround it since libusb misses with the ability to either
+> query the sysfs device path or to got the Port number
+> ("Port" in /proc/bus/usb/devices).
+> (I miss the Port number in order to compute the
+> /sys/bus/devices/usb/foobar path)
+>
+> W/o that I cannot retrieve the modalias which would help me to get the kernel
+> driver name.
+>
+> I guess I'll have to resurect that work and try harder to find some
+> workaround...
+
+Why not using sysfs for everything directly?
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018356.html b/zarb-ml/mageia-dev/2012-August/018356.html new file mode 100644 index 000000000..a42a428b6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018356.html @@ -0,0 +1,98 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 29 16:14:28 CEST 2012 +

+
+ +
On 29 August 2012 16:06, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>> Is there any migration to do in drakx and ldetect because of this?
+>>
+>> Oh yeah I meant to send a message to the list about this.
+>>
+>> Yeah because we're now on kernel 3.5 we can no longer do certain things
+>> relating to this mount point.
+>>
+>> IIRC some ldetect stuff used it and some of the 3G and/or
+>> printer/scanner stuff might also depend on it and need to be migrated
+>> too. I don't know that code very well, but I know some folks complained
+>> when we stopped mounting it by default, so I've no doubt that it's use
+>> is lurking somewhere!
+>>
+>> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+>> what is needed.
+>
+> Humm...
+> I've still around a patch making ldetect using libusb.
+> Sadly, we're missing some data...
+> Basically we would miss the kernel driver name binded with each usb device.
+>
+> We cannot workaround it since libusb misses with the ability to either
+> query the sysfs device path or to got the Port number
+> ("Port" in /proc/bus/usb/devices).
+> (I miss the Port number in order to compute the
+> /sys/bus/devices/usb/foobar path)
+>
+> W/o that I cannot retrieve the modalias which would help me to get the kernel
+> driver name.
+>
+> I guess I'll have to resurect that work and try harder to find some
+> workaround...
+
+I'd also a minimal module reusing code from usbutils.
+If I remember, upstream author wasn't opposed to have some libusbutils library.
+
+ + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018357.html b/zarb-ml/mageia-dev/2012-August/018357.html new file mode 100644 index 000000000..026d1ce97 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018357.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 29 16:15:33 CEST 2012 +

+
+ +
On 29 August 2012 16:13, Pascal Terjan <pterjan at gmail.com> wrote:
+>>> Oh yeah I meant to send a message to the list about this.
+>>>
+>>> Yeah because we're now on kernel 3.5 we can no longer do certain things
+>>> relating to this mount point.
+>>>
+>>> IIRC some ldetect stuff used it and some of the 3G and/or
+>>> printer/scanner stuff might also depend on it and need to be migrated
+>>> too. I don't know that code very well, but I know some folks complained
+>>> when we stopped mounting it by default, so I've no doubt that it's use
+>>> is lurking somewhere!
+>>>
+>>> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+>>> what is needed.
+>>
+>> Humm...
+>> I've still around a patch making ldetect using libusb.
+>> Sadly, we're missing some data...
+>> Basically we would miss the kernel driver name binded with each usb device.
+>>
+>> We cannot workaround it since libusb misses with the ability to either
+>> query the sysfs device path or to got the Port number
+>> ("Port" in /proc/bus/usb/devices).
+>> (I miss the Port number in order to compute the
+>> /sys/bus/devices/usb/foobar path)
+>>
+>> W/o that I cannot retrieve the modalias which would help me to get the kernel
+>> driver name.
+>>
+>> I guess I'll have to resurect that work and try harder to find some
+>> workaround...
+>
+> Why not using sysfs for everything directly?
+
+Why not.
+It's just sad to have everyone parse it instead if having a common library
+exporting the needed data.
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018358.html b/zarb-ml/mageia-dev/2012-August/018358.html new file mode 100644 index 000000000..afa5e52db --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018358.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Aug 29 16:16:00 CEST 2012 +

+
+ +
On 29 August 2012 16:15, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>>> Yeah because we're now on kernel 3.5 we can no longer do certain things
+>>>> relating to this mount point.
+>>>>
+>>>> IIRC some ldetect stuff used it and some of the 3G and/or
+>>>> printer/scanner stuff might also depend on it and need to be migrated
+>>>> too. I don't know that code very well, but I know some folks complained
+>>>> when we stopped mounting it by default, so I've no doubt that it's use
+>>>> is lurking somewhere!
+>>>>
+>>>> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+>>>> what is needed.
+>>>
+>>> Humm...
+>>> I've still around a patch making ldetect using libusb.
+>>> Sadly, we're missing some data...
+>>> Basically we would miss the kernel driver name binded with each usb device.
+>>>
+>>> We cannot workaround it since libusb misses with the ability to either
+>>> query the sysfs device path or to got the Port number
+>>> ("Port" in /proc/bus/usb/devices).
+>>> (I miss the Port number in order to compute the
+>>> /sys/bus/devices/usb/foobar path)
+>>>
+>>> W/o that I cannot retrieve the modalias which would help me to get the kernel
+>>> driver name.
+>>>
+>>> I guess I'll have to resurect that work and try harder to find some
+>>> workaround...
+>>
+>> Why not using sysfs for everything directly?
+>
+> Why not.
+> It's just sad to have everyone parse it instead if having a common library
+> exporting the needed data.
+
+See also http://sourceforge.net/apps/trac/libusbx/ticket/24
+
+ + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018359.html b/zarb-ml/mageia-dev/2012-August/018359.html new file mode 100644 index 000000000..06d410f47 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018359.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 29 23:31:50 CEST 2012 +

+
+ +
I have installed mga2 on a system which is replacing an old system, and as soon as I boot after selecting Mageia on the GRUB menu (which is default), the screen goes black and it doesn't work ever untill I reboot. I have blacklisted the nouveau module and ran dracut again to generate a new image.
+It now goes black at aout the time where it is starting X, and again the screen is blank untill I get back to the "BIOS startup screen".
+
+The card is a GeForce 6800 GTO.
+I am Not using any proprieraty drivers, nor have I enabled tainted or non-free repos. I have simply done a standard boot.iso network install and rebooted.
+
+Any idea on how to proceed?
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120829/ecd82d7b/attachment.asc>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018360.html b/zarb-ml/mageia-dev/2012-August/018360.html new file mode 100644 index 000000000..6463a4c41 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018360.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ AL13N + alien at rmail.be +
+ Wed Aug 29 23:34:40 CEST 2012 +

+
+ +
Op woensdag 29 augustus 2012 22:31:50 schreef Johnny A. Solbu:
+> I have installed mga2 on a system which is replacing an old system, and as
+> soon as I boot after selecting Mageia on the GRUB menu (which is default),
+> the screen goes black and it doesn't work ever untill I reboot. I have
+> blacklisted the nouveau module and ran dracut again to generate a new
+> image. It now goes black at aout the time where it is starting X, and again
+> the screen is blank untill I get back to the "BIOS startup screen".
+> 
+> The card is a GeForce 6800 GTO.
+> I am Not using any proprieraty drivers, nor have I enabled tainted or
+> non-free repos. I have simply done a standard boot.iso network install and
+> rebooted.
+> 
+> Any idea on how to proceed?
+
+if you're not using propriatery drivers, nor the nouveau module... what ARE 
+you using then? vesa?
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018361.html b/zarb-ml/mageia-dev/2012-August/018361.html new file mode 100644 index 000000000..c2c8327b0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018361.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] Association between SRPMs and bug reports in Mageia App Db + + + + + + + + + +

[Mageia-dev] Association between SRPMs and bug reports in Mageia App Db

+ Samuel Verschelde + stormi at laposte.net +
+ Wed Aug 29 23:35:30 CEST 2012 +

+
+ +
Hi,
+
+In Mageia App Db [1], there was a page that listed all packages from 
+updates_testing media, named "Update candidates" in the menu.
+
+This page now gives for each package the link to its bug report in bugzilla, 
+if it can find one. 
+
+Example: update candidates for Mageia 2, source packages:
+http://mageia.madb.org/rpm/list/listtype/updates_testing/application/0/source/1
+
+When a bug report has been found to match the update candidate, an additional 
+piece of information is added right to it:
+- QA = exact SRPM name match (anywhere in the bug report), bug assigned to QA
+- QA in CC = exact SRPM name match, QA is in CC of the bug (probably waiting 
+for the packager to do something)
+- no QA = exact SRPM match, but QA was not involved (yet?)
+- partial match, QA = partial SRPM name match with the bug report's RPM field, 
+bug assigned to QA
+- partial match, QA in CC = partial SRPM name match with the bug report's RPM 
+field, bug assigned to QA.
+
+RPMs and bug reports are not matched in real time (too much time consuming), 
+but most new links should appear rather quickly though.
+
+It can happen that it takes up to 24 hours for an update candidate to appear 
+in the list, due to Sophie [2] (which Mageia App Db queries) having some 
+difficulties to detect that a new package was added in updates_testing and 
+updates media (it looks like their addition doesn't trigger the right event, 
+so we have to wait for sophie to perform its full scan to see them in the 
+list, which happens once a day IIRC). Olivier Thauvin can probably correct me 
+if I'm wrong.
+
+[1] http://mageia.madb.org
+[2] http://sophie.zarb.org
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018362.html b/zarb-ml/mageia-dev/2012-August/018362.html new file mode 100644 index 000000000..32909cf04 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018362.html @@ -0,0 +1,79 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Johnny A. Solbu + cooker at solbu.net +
+ Wed Aug 29 23:54:50 CEST 2012 +

+
+ +
On Wednesday 29 August 2012 23:34, AL13N wrote:
+> if you're not using propriatery drivers, nor the nouveau module... what ARE 
+> you using then? vesa?
+
+Good question. nouveau does Not work on this card. As soon as this driver is loaded, the screen goes blank and only a reboot will fix it.
+It seems like "nv" works.
+
+"nouveau" seems to be seriously broken on mga2.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120829/2e2bf08f/attachment.asc>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018363.html b/zarb-ml/mageia-dev/2012-August/018363.html new file mode 100644 index 000000000..4ecfeeb43 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018363.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 30 00:30:31 CEST 2012 +

+
+ +
'Twas brillig, and Johnny A. Solbu at 29/08/12 22:54 did gyre and gimble:
+> On Wednesday 29 August 2012 23:34, AL13N wrote:
+>> if you're not using propriatery drivers, nor the nouveau module... what ARE 
+>> you using then? vesa?
+> 
+> Good question. nouveau does Not work on this card. As soon as this driver is loaded, the screen goes blank and only a reboot will fix it.
+> It seems like "nv" works.
+> 
+> "nouveau" seems to be seriously broken on mga2.
+
+Might you be getting hit by:
+https://bugs.kde.org/show_bug.cgi?id=295814
+
+See the thread on this list from a week or two ago: "Desktop Monitor
+powering down"
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018364.html b/zarb-ml/mageia-dev/2012-August/018364.html new file mode 100644 index 000000000..e0bd15364 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018364.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Johnny A. Solbu + cooker at solbu.net +
+ Thu Aug 30 01:20:12 CEST 2012 +

+
+ +
On Thursday 30 August 2012 00:30, Colin Guthrie wrote:
+> See the thread on this list from a week or two ago: "Desktop Monitor
+> powering down"
+
+That is not my problem. My monitor does Not power down. it just doesn't display anything, using nouveau, whereas nv works, once I figured out how to enable it.
+
+If the power settings where the issiue, I would still be able to have a visible graphical login. but I don't. As soon as the graphical login screen (dm) starts, the sceen goes blank, but it does not power Off or Down. Stopping dm or changing runlevel does not help. I have to reboot in order to get my screen back, untill it blanks again once dm starts....
+
+... And round and round it goes, untill one manually selects nv as the driver.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120830/ebf9f2f1/attachment.asc>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018365.html b/zarb-ml/mageia-dev/2012-August/018365.html new file mode 100644 index 000000000..4c9087b72 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018365.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Balcaen John + mikala at mageia.org +
+ Thu Aug 30 02:11:42 CEST 2012 +

+
+ +
Le jeudi 30 août 2012 00:20:12 Johnny A. Solbu a écrit :
+> On Thursday 30 August 2012 00:30, Colin Guthrie wrote:
+> > See the thread on this list from a week or two ago: "Desktop Monitor
+> > powering down"
+> 
+> That is not my problem. My monitor does Not power down. it just doesn't
+> display anything, using nouveau, whereas nv works, once I figured out how
+> to enable it.
+> 
+> If the power settings where the issiue, I would still be able to have a
+> visible graphical login. but I don't. As soon as the graphical login screen
+> (dm) starts, the sceen goes blank, but it does not power Off or Down.
+> Stopping dm or changing runlevel does not help. I have to reboot in order
+> to get my screen back, untill it blanks again once dm starts....
+> 
+> ... And round and round it goes, untill one manually selects nv as the
+> driver.
+Do you have anything useful in logs ? (dmesg, xorg.log etc etc) ?
+Like some missing firmware  ?
+
+-- 
+Balcaen John
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018366.html b/zarb-ml/mageia-dev/2012-August/018366.html new file mode 100644 index 000000000..4ffc12b29 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018366.html @@ -0,0 +1,90 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Remco Rijnders + remco at webconquest.com +
+ Thu Aug 30 04:11:00 CEST 2012 +

+
+ +
On Wed, Aug 29, 2012 at 10:31:50PM +0100, Johnny wrote in 
+<201208292331.58583.cooker at solbu.net>:
+>I have installed mga2 on a system which is replacing an old system, and as soon as I boot after selecting Mageia on the GRUB menu (which is default), the screen goes black and it doesn't work ever untill I reboot. I have blacklisted the nouveau module and ran dracut again to generate a new image.
+>It now goes black at aout the time where it is starting X, and again the screen is blank untill I get back to the "BIOS startup screen".
+>
+>The card is a GeForce 6800 GTO.
+>I am Not using any proprieraty drivers, nor have I enabled tainted or non-free repos. I have simply done a standard boot.iso network install and rebooted.
+>
+>Any idea on how to proceed?
+
+Is only one graphic card detected on this system? This sounds similar to 
+what I had on a reasonably recent laptop which detected two graphical 
+"cards" and where the system got confused. (It didn't help that the two 
+chips needed different drivers).
+
+Remmy
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 836 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120830/4df8b860/attachment-0001.asc>
+
+ + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018367.html b/zarb-ml/mageia-dev/2012-August/018367.html new file mode 100644 index 000000000..af8b8b942 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018367.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Johnny A. Solbu + cooker at solbu.net +
+ Thu Aug 30 04:22:29 CEST 2012 +

+
+ +
On Thursday 30 August 2012 04:11, Remco Rijnders wrote:
+> Is only one graphic card detected on this system?
+
+Yes. 
+And it's a desktop., not a laptop.
+It does however have two DVI ports on the same card.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120830/988881d5/attachment.asc>
+
+ + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018368.html b/zarb-ml/mageia-dev/2012-August/018368.html new file mode 100644 index 000000000..e8c78a07a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018368.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Johnny A. Solbu + cooker at solbu.net +
+ Thu Aug 30 05:18:58 CEST 2012 +

+
+ +
On Thursday 30 August 2012 02:11, Balcaen John wrote:
+> Do you have anything useful in logs ? (dmesg, xorg.log etc etc) ?
+
+http://www.solbu.net/mageia-dm/
+
+> Like some missing firmware  ?
+
+As I were saying, I don't use proprietary drivers. That includes proprietary firmware.
+And I have Not enabled the nonfree repo.
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120830/6d19b97f/attachment.asc>
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018369.html b/zarb-ml/mageia-dev/2012-August/018369.html new file mode 100644 index 000000000..23740f015 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018369.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text + + + + + + + + + +

[Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Aug 30 11:22:53 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 22/08/2012 16:29, Pascal Terjan wrote:
+> On Wed, Aug 22, 2012 at 11:57 AM, Marja van Waes
+> <marja11 at xs4all.nl> wrote:
+>> Hi all,
+>> 
+>> About a help text for drakx-installer-stage2:
+>> 
+>> Can someone please help documentation team with a good help text
+>> for the help button for the "Add or Modify a Boot Menu Entry"
+>> screen, so for the pop up screen you see in the second screenshot
+>> here (the one that pops up on top of the Bootloader Configuration
+>> screen) 
+>> http://docteam.mageia.nl/installer/content/setupBootloaderAddEntry.html
+>
+>> 
+> What is the expected kind of text? ( I have never read the help :)
+> ) An explanation of the different fields?
+
+You didn't reply to my reply, so maybe I misunderstood. I thought you
+were longing to help us :þ
+
+Anyway, if no one comes up with something better, we'll remove
+
+"Add some text
+
+........
+
+........"
+
+and leave the help text as it is.
+
+Cheers,
+marja
+
+
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iQEcBAEBAgAGBQJQPzDoAAoJEKWubDMI5nEBljoH/3JwXfVuHbS6NNnI9AR7ZCh5
+aSrOMW1gbVXSfFEjIF988jEBbz4KoszDaPwFhXXQKfJ47sSJsJvEslonqztbhU7z
+/+f+RbuEqc1uJmT8EixmBx/OrZT0a1rZTDxw6PXwL44s8R+cFVZQZbQPAwEq5NNd
+wNv/X8rnpNvXY7qsRQxWdtaPlgOUWBJyPVbmX9kdg5QoMsXI3Qo/zmtxCHe+F24B
+zrm1nTrP+iBj+W8k+pz3Bp8u6bBAXKVUt/9x2mShk575lULoGvvYXIvXNDtCRrrJ
+K5oRkXawEj3ZjiBZHEA3bnpHD3+0MCaAwPkrZJHYrIV4By6UA7q13rJLduq5v+U=
+=JEob
+-----END PGP SIGNATURE-----
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018370.html b/zarb-ml/mageia-dev/2012-August/018370.html new file mode 100644 index 000000000..3b74594d1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018370.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3) + + + + + + + + + +

[Mageia-dev] dropping /proc/bus/sub (Re: [changelog] [RPM] cauldron core/release systemd-189-2.mga3)

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Thu Aug 30 11:39:16 CEST 2012 +

+
+ +
On 29 August 2012 16:16, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+>>>>> Yeah because we're now on kernel 3.5 we can no longer do certain things
+>>>>> relating to this mount point.
+>>>>>
+>>>>> IIRC some ldetect stuff used it and some of the 3G and/or
+>>>>> printer/scanner stuff might also depend on it and need to be migrated
+>>>>> too. I don't know that code very well, but I know some folks complained
+>>>>> when we stopped mounting it by default, so I've no doubt that it's use
+>>>>> is lurking somewhere!
+>>>>>
+>>>>> I would guess that in some cases /dev/bus/usb/ might be sufficient for
+>>>>> what is needed.
+>>>>
+>>>> Humm...
+>>>> I've still around a patch making ldetect using libusb.
+>>>> Sadly, we're missing some data...
+>>>> Basically we would miss the kernel driver name binded with each usb device.
+>>>>
+>>>> We cannot workaround it since libusb misses with the ability to either
+>>>> query the sysfs device path or to got the Port number
+>>>> ("Port" in /proc/bus/usb/devices).
+>>>> (I miss the Port number in order to compute the
+>>>> /sys/bus/devices/usb/foobar path)
+>>>>
+>>>> W/o that I cannot retrieve the modalias which would help me to get the kernel
+>>>> driver name.
+>>>>
+>>>> I guess I'll have to resurect that work and try harder to find some
+>>>> workaround...
+>>>
+>>> Why not using sysfs for everything directly?
+
+(...)
+
+> See also http://sourceforge.net/apps/trac/libusbx/ticket/24
+
+I've put a simple fix at https://bugs.mageia.org/show_bug.cgi?id=7248
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018371.html b/zarb-ml/mageia-dev/2012-August/018371.html new file mode 100644 index 000000000..9f488fc5f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018371.html @@ -0,0 +1,75 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Aug 30 13:18:46 CEST 2012 +

+
+ +
On 08/29/2012 11:18 PM, Johnny A. Solbu wrote:
+>> Like some missing firmware  ?
+> As I were saying, I don't use proprietary drivers. That includes proprietary firmware.
+> And I have Not enabled the nonfree repo.
+>
+That may be the problem.  For many ATI cards (yes, I know you're 
+nvidia), the install sets an ATI driver (free or proprietary) which will 
+not work without nonfree firmware, resulting in exactly what you see.  
+These days, for a cauldron install, I have to specifically select "vesa" 
+during install, and only switch it to the actual driver after firmware 
+has been installed.
+
+You need to figure out what driver is being set by the install, and what 
+its requirements are.  Worst case, redo the install and in Summary 
+choose Graphical and see what's selected by default.  Then select 
+"Xorg::vesa", and go with that until this has been cleared up.  Googling 
+a combination of your card model and the driver name will probably help.
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018372.html b/zarb-ml/mageia-dev/2012-August/018372.html new file mode 100644 index 000000000..c6e278d4f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018372.html @@ -0,0 +1,84 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Remco Rijnders + remco at webconquest.com +
+ Thu Aug 30 13:45:00 CEST 2012 +

+
+ +
On Thu, Aug 30, 2012 at 07:18:46AM -0400, Frank wrote in 
+<503F4C16.4030701 at roadrunner.com>:
+>
+>You need to figure out what driver is being set by the install, and 
+>what its requirements are.  Worst case, redo the install and in 
+>Summary choose Graphical and see what's selected by default.  Then 
+>select "Xorg::vesa", and go with that until this has been cleared up.  
+>Googling a combination of your card model and the driver name will 
+>probably help.
+
+Courtesy of wobo, this is what we used last weekend:
+
+- Add "init 3" to the boot parameters, this should take you to text only 
+login.
+
+- Run XFDrake to see what driver you are using and possibly adjust it if 
+needed.
+
+Remmy
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 836 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120830/ad77f6b2/attachment.asc>
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018373.html b/zarb-ml/mageia-dev/2012-August/018373.html new file mode 100644 index 000000000..75daf0733 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018373.html @@ -0,0 +1,71 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Aug 30 14:01:10 CEST 2012 +

+
+ +
On 08/30/2012 07:45 AM, Remco Rijnders wrote:
+>
+> Courtesy of wobo, this is what we used last weekend:
+>
+> - Add "init 3" to the boot parameters, this should take you to text 
+> only login.
+>
+> - Run XFDrake to see what driver you are using and possibly adjust it 
+> if needed.
+>
+That will work fine, if you're lucky enough to have a driver/card that 
+works in text mode without firmware.   Unfortunately, the older ATI ones 
+don't.
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018374.html b/zarb-ml/mageia-dev/2012-August/018374.html new file mode 100644 index 000000000..a61c025c9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018374.html @@ -0,0 +1,69 @@ + + + + [Mageia-dev] isolinux questions + + + + + + + + + +

[Mageia-dev] isolinux questions

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Aug 30 14:23:50 CEST 2012 +

+
+ +
1) What is isolinux/alt1 these days ?  Googling comes up with nothing 
+except pointers to various repos and mirrors where it exists, and 
+there's nothing in the isolinux help files about it.
+
+2) Is there an isolinux vmlinux/all.rdz variant to match 
+boot-nonfree.iso/all-nonfree.img ?  Would it be a lot of trouble to have 
+one (alt2 ?) ?  I'm guessing these files already exist, but are embedded 
+in the iso/img variant.
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018375.html b/zarb-ml/mageia-dev/2012-August/018375.html new file mode 100644 index 000000000..bd01d78f9 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018375.html @@ -0,0 +1,89 @@ + + + + [Mageia-dev] isolinux questions + + + + + + + + + +

[Mageia-dev] isolinux questions

+ Thomas Backlund + tmb at mageia.org +
+ Thu Aug 30 14:37:05 CEST 2012 +

+
+ +
Frank Griffin skrev 30.8.2012 15:23:
+> 1) What is isolinux/alt1 these days ?  Googling comes up with nothing
+> except pointers to various repos and mirrors where it exists, and
+> there's nothing in the isolinux help files about it.
+>
+
+You mean besides the advanced help info:
+http://mirrors.kernel.org/mageia/distrib/cauldron/i586/isolinux/advanced.msg
+
+Basically it's the server kernel instead of desktop586,
+as some hw does not boot on desktop586.
+
+also as its server kernel is supports xen installs.
+
+> 2) Is there an isolinux vmlinux/all.rdz variant to match
+> boot-nonfree.iso/all-nonfree.img ?
+
+Not separate at this point...
+
+>  Would it be a lot of trouble to have
+> one (alt2 ?) ?  I'm guessing these files already exist, but are embedded
+> in the iso/img variant.
+
+Not tested / decided yet...
+
+--
+Thomas
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018376.html b/zarb-ml/mageia-dev/2012-August/018376.html new file mode 100644 index 000000000..b2d15ca28 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018376.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] isolinux questions + + + + + + + + + +

[Mageia-dev] isolinux questions

+ Frank Griffin + ftg at roadrunner.com +
+ Thu Aug 30 14:56:24 CEST 2012 +

+
+ +
On 08/30/2012 08:37 AM, Thomas Backlund wrote:
+> Frank Griffin skrev 30.8.2012 15:23:
+>> 1) What is isolinux/alt1 these days ? Googling comes up with nothing
+>> except pointers to various repos and mirrors where it exists, and
+>> there's nothing in the isolinux help files about it.
+>>
+>
+> You mean besides the advanced help info:
+> http://mirrors.kernel.org/mageia/distrib/cauldron/i586/isolinux/advanced.msg 
+>
+
+Thanks for the link.  Just FYI, I was looking in the x86_64 directory, 
+and advanced.msg there mentions only alt0.
+
+
+
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018377.html b/zarb-ml/mageia-dev/2012-August/018377.html new file mode 100644 index 000000000..15f8fa072 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018377.html @@ -0,0 +1,94 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Digigold + digigold808 at gmail.com +
+ Thu Aug 30 14:57:27 CEST 2012 +

+
+ +
On 08/30/2012 08:01 AM, Frank Griffin wrote:
+> On 08/30/2012 07:45 AM, Remco Rijnders wrote:
+>>
+>> Courtesy of wobo, this is what we used last weekend:
+>>
+>> - Add "init 3" to the boot parameters, this should take you to text 
+>> only login.
+>>
+>> - Run XFDrake to see what driver you are using and possibly adjust it 
+>> if needed.
+>>
+> That will work fine, if you're lucky enough to have a driver/card that 
+> works in text mode without firmware.   Unfortunately, the older ATI 
+> ones don't.
+FWIW my laptop has an ATI Radeon Mobility 4250 and I do a fresh cauldron 
+install about every other week.  I do have initial issues with the 
+Radeon upon first boot; however, I always just login to run level 3, (I 
+add "ro 3" not "init 3", but get the same result.)  add the non-free 
+repo then install the needed drivers, firmware and fglrx kernel mod.  
+Reboot to RL3 again.  Run the display setup program. Adjust settings 
+accordingly, then reboot to RL5 and proceed normally.
+
+Regards
+
+-- 
+
+
+        /"A mind that is stretched by a new experience can never go back
+        to its old dimensions."/
+
+
+          *~Oliver Wendell Holmes, Jr.*
+
+-------------- next part --------------
+An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120830/97e573a8/attachment.html>
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018378.html b/zarb-ml/mageia-dev/2012-August/018378.html new file mode 100644 index 000000000..44df72315 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018378.html @@ -0,0 +1,86 @@ + + + + [Mageia-dev] isolinux questions + + + + + + + + + +

[Mageia-dev] isolinux questions

+ Thomas Backlund + tmb at mageia.org +
+ Thu Aug 30 14:58:44 CEST 2012 +

+
+ +
Frank Griffin skrev 30.8.2012 15:56:
+> On 08/30/2012 08:37 AM, Thomas Backlund wrote:
+>> Frank Griffin skrev 30.8.2012 15:23:
+>>> 1) What is isolinux/alt1 these days ? Googling comes up with nothing
+>>> except pointers to various repos and mirrors where it exists, and
+>>> there's nothing in the isolinux help files about it.
+>>>
+>>
+>> You mean besides the advanced help info:
+>> http://mirrors.kernel.org/mageia/distrib/cauldron/i586/isolinux/advanced.msg
+>>
+>
+> Thanks for the link.  Just FYI, I was looking in the x86_64 directory,
+> and advanced.msg there mentions only alt0.
+>
+
+Yep. thats because we dont need alt1 on x86_64 as desktop kernel on 
+x86_64 is xen-enabled too...
+
+The need for alternative kernel is only on i586
+
+--
+thomas
+
+
+
+
+ + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018379.html b/zarb-ml/mageia-dev/2012-August/018379.html new file mode 100644 index 000000000..aa1b1a406 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018379.html @@ -0,0 +1,83 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Thu Aug 30 15:02:38 CEST 2012 +

+
+ +
'Twas brillig, and Digigold at 30/08/12 13:57 did gyre and gimble:
+> (I add "ro 3" not "init 3", but get the same result.)
+
+Yeah the word "init" is not needed here, just a "3" will do. Although
+such runlevels are really just compatibility with a somewhat outdated
+concept, and appending "systemd.unit=multi-user.target" is arguably the
+more "correct" way of specifying things. That said, "3" is considerably
+shorter to type and has much less chance of typos so I struggle to
+recommend this alternative with a straight face :p
+
+
+Col
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018380.html b/zarb-ml/mageia-dev/2012-August/018380.html new file mode 100644 index 000000000..33cc9b947 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018380.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] Fresh mga2 install - NO screen ! + + + + + + + + + +

[Mageia-dev] Fresh mga2 install - NO screen !

+ Johnny A. Solbu + cooker at solbu.net +
+ Thu Aug 30 15:33:45 CEST 2012 +

+
+ +
On Thursday 30 August 2012 15:02, Colin Guthrie wrote:
+> "3" is considerably
+> shorter to type and has much less chance of typos so I struggle to
+> recommend this alternative with a straight face :p
+
+It is also easier to get a regular user to type over the phone when they call me for help, and I don't have to use the pronetic alphabet in order to make sure they get it right. :-)=
+
+-- 
+Johnny A. Solbu
+PGP key ID: 0xFA687324
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 189 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120830/9ababfd3/attachment.asc>
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018381.html b/zarb-ml/mageia-dev/2012-August/018381.html new file mode 100644 index 000000000..725a620a3 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018381.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text + + + + + + + + + +

[Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text

+ Pascal Terjan + pterjan at gmail.com +
+ Thu Aug 30 16:08:18 CEST 2012 +

+
+ +
On Thu, Aug 30, 2012 at 10:22 AM, Marja van Waes <marja11 at xs4all.nl> wrote:
+> -----BEGIN PGP SIGNED MESSAGE-----
+> Hash: SHA1
+>
+> On 22/08/2012 16:29, Pascal Terjan wrote:
+>> On Wed, Aug 22, 2012 at 11:57 AM, Marja van Waes
+>> <marja11 at xs4all.nl> wrote:
+>>> Hi all,
+>>>
+>>> About a help text for drakx-installer-stage2:
+>>>
+>>> Can someone please help documentation team with a good help text
+>>> for the help button for the "Add or Modify a Boot Menu Entry"
+>>> screen, so for the pop up screen you see in the second screenshot
+>>> here (the one that pops up on top of the Bootloader Configuration
+>>> screen)
+>>> http://docteam.mageia.nl/installer/content/setupBootloaderAddEntry.html
+>>
+>>>
+>> What is the expected kind of text? ( I have never read the help :)
+>> ) An explanation of the different fields?
+>
+> You didn't reply to my reply, so maybe I misunderstood. I thought you
+> were longing to help us :ţ
+
+Sorry, I was away for an extended week-end, I may have some time tomorrow
+
+> Anyway, if no one comes up with something better, we'll remove
+>
+> "Add some text
+>
+> ........
+>
+> ........"
+>
+> and leave the help text as it is.
+>
+> Cheers,
+> marja
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018382.html b/zarb-ml/mageia-dev/2012-August/018382.html new file mode 100644 index 000000000..d4f8f3530 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018382.html @@ -0,0 +1,78 @@ + + + + [Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text + + + + + + + + + +

[Mageia-dev] Add or Modify a Boot Menu Entry - please help write the help text

+ Marja van Waes + marja11 at xs4all.nl +
+ Thu Aug 30 16:17:59 CEST 2012 +

+
+ +
-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
+On 30/08/2012 16:08, Pascal Terjan wrote:
+
+> 
+> Sorry, I was away for an extended week-end, I may have some time
+> tomorrow
+> 
+
+Ah, that would be great :-D
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.4.12 (GNU/Linux)
+Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
+
+iQEcBAEBAgAGBQJQP3YSAAoJEKWubDMI5nEBfloH/A2TcRvSefJsvUalzzDy4hVC
+CRrn7D+cCKxvNN7iVMFWwkVp/wv9jrWtjamc8KD08e92Tn20D5O7Gtae4XjWKyiC
+oBqltpvzVQlZsQh9HQ67Mj8AOypGCjo06WXXx6d+GpYmZ0URc02V2BGcr4BFQ0k8
+Ffum4aq/hXMQ3TuC+652jgxct8iz4hWUywphxDdE1JUBhNnWMVpj9AUA5nSy8gRI
+gihxfq5BNRMy6wtCm1o6Qtww+a1ex6facvABChV3d0e9Mdq3Rk3At5dit3xnVq1e
+B/S3Ked/b/PQEVSBdRYZ7OvVccaCjoa4aqTI9MMGBOOk773UT2w2NAfxRpf24T0=
+=GGw+
+-----END PGP SIGNATURE-----
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018383.html b/zarb-ml/mageia-dev/2012-August/018383.html new file mode 100644 index 000000000..441c65261 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018383.html @@ -0,0 +1,92 @@ + + + + [Mageia-dev] Problems with suspend using 3.5.x kernels + + + + + + + + + +

[Mageia-dev] Problems with suspend using 3.5.x kernels

+ Scott Chevalley + avalon at osguru.org +
+ Thu Aug 30 17:49:32 CEST 2012 +

+
+ +
I'm running the latest cauldron on a Dell XPS 15 laptop using the Nouveau driver
+and have noticed that it will not wake properly from suspend when using any of
+the 3.5.x desktop or tmb-desktop kernels.  I get a pretty almost paisley pattern
+on the screen.
+
+The system is responsive to ssh, but there is no way to recover the screen short
+of rebooting.
+
+If I switch to a tty and run pm-suspend, then it will wake fine, but I have to
+completely kill X and restart it before it is usable.
+
+Looking in dmesg when it did it this morning I see this:
+
+[drm] nouveau 0000:02:00.0: PFIFO - playlist update failed
+[drm] nouveau 0000:02:00.0: 0x2634 != chid: 0x00100005
+[drm] nouveau 0000:02:00.0: PFIFO: unknown status 0x00000100
+[drm] nouveau 0000:02:00.0: PFIFO - playlist update failed
+[drm] nouveau 0000:02:00.0: 0x2634 != chid: 0x00100004
+[drm] nouveau 0000:02:00.0: PFIFO: unknown status 0x00000100
+[drm] nouveau 0000:02:00.0: PFIFO - playlist update failed
+[drm] nouveau 0000:02:00.0: 0x2634 != chid: 0x00100002
+[drm] nouveau 0000:02:00.0: PFIFO: unknown status 0x00000100
+[drm] nouveau 0000:02:00.0: PFIFO - playlist update failed
+[drm] nouveau 0000:02:00.0: PFIFO: unknown status 0x00000100
+[drm] nouveau 0000:02:00.0: 0x2634 != chid: 0x00100001
+[drm] nouveau 0000:02:00.0: PFIFO: unknown status 0x00000100
+[drm] nouveau 0000:02:00.0: PFIFO - playlist update failed
+[drm] nouveau 0000:02:00.0: PFIFO: unhandled status 0x00000001
+detected fb_set_par error, error code: -16
+
+at the end.
+
+Suspend and resume work fine on kernel 3.4.6.
+
+Thanks!
+Scott
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018384.html b/zarb-ml/mageia-dev/2012-August/018384.html new file mode 100644 index 000000000..94d131b00 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018384.html @@ -0,0 +1,58 @@ + + + + [Mageia-dev] 29522 broken dependencies... + + + + + + + + + +

[Mageia-dev] 29522 broken dependencies...

+ eatdirt + dirteat at gmail.com +
+ Fri Aug 31 00:39:05 CEST 2012 +

+
+ +
collector?
+
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018385.html b/zarb-ml/mageia-dev/2012-August/018385.html new file mode 100644 index 000000000..621719668 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018385.html @@ -0,0 +1,62 @@ + + + + [Mageia-dev] [soft-commits] [5460] Remove input methods that don't have packages in Mageia repo. + + + + + + + + + +

[Mageia-dev] [soft-commits] [5460] Remove input methods that don't have packages in Mageia repo.

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 31 08:07:17 CEST 2012 +

+
+ +
On 31 August 2012 05:30,  <root at mageia.org> wrote:
+> Log Message
+>
+> Remove input methods that don't have packages in Mageia repo.
+
+we could have packaged them instead...
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018386.html b/zarb-ml/mageia-dev/2012-August/018386.html new file mode 100644 index 000000000..e973a360d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018386.html @@ -0,0 +1,66 @@ + + + + [Mageia-dev] [soft-commits] [5460] Remove input methods that don't have packages in Mageia repo. + + + + + + + + + +

[Mageia-dev] [soft-commits] [5460] Remove input methods that don't have packages in Mageia repo.

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 31 11:25:48 CEST 2012 +

+
+ +
On Fri, Aug 31, 2012 at 7:07 AM, Thierry Vignaud
+<thierry.vignaud at gmail.com> wrote:
+> On 31 August 2012 05:30,  <root at mageia.org> wrote:
+>> Log Message
+>>
+>> Remove input methods that don't have packages in Mageia repo.
+>
+> we could have packaged them instead...
+
+I added scim-hangul
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018387.html b/zarb-ml/mageia-dev/2012-August/018387.html new file mode 100644 index 000000000..5429e9940 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018387.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release telepathy-kde-common-internals-0.5.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release telepathy-kde-common-internals-0.5.0-1.mga3

+ John Balcaen + mikala at mageia.org +
+ Fri Aug 31 11:38:41 CEST 2012 +

+
+ +
2012/8/30 neoclust <buildsystem-daemon at mageia.org>:
+> Name        : telepathy-kde-common-internals  Relocations: (not relocatable)
+[...]
+> mikala <mikala> 0.5.0-1.mga3:
+> + Revision: 285939
+> - use conflicts instead of obsoletes to allow update
+[...]
+Hello thierry (& others :p ),
+Do you have any ideas why i'm forced to used a conflicts to ensure
+upgrade of packages here ?
+Some files where added in %{name} package but since thoses files are
+noarch i moved them in a noarch package.
+However from my local test it seems that a noarch package can't
+obsolete an arch package
+aka if i'm adding in the %{name}-core an obsoletes: %{name} < 0.5.0,
+urpmi will prevent the upgrade due to files conflicts between
+%{name}-0.4.0 & %{name}-core-0.5.0
+
+Regards,
+
+
+-- 
+Balcaen John
+Jabber-id: mikala at jabber.littleboboy.net
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018388.html b/zarb-ml/mageia-dev/2012-August/018388.html new file mode 100644 index 000000000..5274b7652 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018388.html @@ -0,0 +1,77 @@ + + + + [Mageia-dev] make -l ? + + + + + + + + + +

[Mageia-dev] make -l ?

+ Pascal Terjan + pterjan at gmail.com +
+ Fri Aug 31 11:40:18 CEST 2012 +

+
+ +
Currently %make is expanded to make -j<nb cpu>
+
+I'd like it to be replaced with make -l<nb cpu>
+
+For those we don't know the difference:
+
+       -j [jobs], --jobs[=jobs]
+            Specifies the number of jobs (commands) to run
+simultaneously.  If there is more than one -j option, the last one is
+effective.  If the  -j  option
+            is given without an argument, make will not limit the
+number of jobs that can run simultaneously.
+
+       -l [load], --load-average[=load]
+            Specifies that no new jobs (commands) should be started if
+there are others jobs running and the load average is at least  load
+(a  floating-point
+            number).  With no argument, removes a previous load limit.
+
+In short, this means taking into account the current load of the machine.
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018389.html b/zarb-ml/mageia-dev/2012-August/018389.html new file mode 100644 index 000000000..7da544ab0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018389.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release telepathy-kde-common-internals-0.5.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release telepathy-kde-common-internals-0.5.0-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 31 11:50:13 CEST 2012 +

+
+ +
On 31 August 2012 11:38, John Balcaen <mikala at mageia.org> wrote:
+>> mikala <mikala> 0.5.0-1.mga3:
+>> + Revision: 285939
+>> - use conflicts instead of obsoletes to allow update
+> [...]
+> Hello thierry (& others :p ),
+> Do you have any ideas why i'm forced to used a conflicts to ensure
+> upgrade of packages here ?
+> Some files where added in %{name} package but since thoses files are
+> noarch i moved them in a noarch package.
+> However from my local test it seems that a noarch package can't
+> obsolete an arch package
+> aka if i'm adding in the %{name}-core an obsoletes: %{name} < 0.5.0,
+> urpmi will prevent the upgrade due to files conflicts between
+> %{name}-0.4.0 & %{name}-core-0.5.0
+
+Always use both Conflicts & Obsoletes.
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018390.html b/zarb-ml/mageia-dev/2012-August/018390.html new file mode 100644 index 000000000..d3c3c3ce6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018390.html @@ -0,0 +1,81 @@ + + + + [Mageia-dev] make -l ? + + + + + + + + + +

[Mageia-dev] make -l ?

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 31 11:51:36 CEST 2012 +

+
+ +
n 31 August 2012 11:40, Pascal Terjan <pterjan at gmail.com> wrote:
+> Currently %make is expanded to make -j<nb cpu>
+>
+> I'd like it to be replaced with make -l<nb cpu>
+>
+> For those we don't know the difference:
+>
+>        -j [jobs], --jobs[=jobs]
+>             Specifies the number of jobs (commands) to run
+> simultaneously.  If there is more than one -j option, the last one is
+> effective.  If the  -j  option
+>             is given without an argument, make will not limit the
+> number of jobs that can run simultaneously.
+>
+>        -l [load], --load-average[=load]
+>             Specifies that no new jobs (commands) should be started if
+> there are others jobs running and the load average is at least  load
+> (a  floating-point
+>             number).  With no argument, removes a previous load limit.
+>
+> In short, this means taking into account the current load of the machine.
+
+Why not.
+It would be better to test it on some big packages first.
+And timing their build with both "make -j" & "make -l"
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018391.html b/zarb-ml/mageia-dev/2012-August/018391.html new file mode 100644 index 000000000..d0cf4b746 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018391.html @@ -0,0 +1,65 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release chromium-browser-stable-21.0.1180.81-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release chromium-browser-stable-21.0.1180.81-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 31 12:46:07 CEST 2012 +

+
+ +
On 31 August 2012 12:41, dmorgan <buildsystem-daemon at mageia.org> wrote:
+>   + dams <dams>
+>     - clean specfile
+>     - remove useless part of the description: old issue (5.x)
+
+1) please use separate commits next time so that they're easier to review
+2) don't gratuitously change whitespace in packages maintained by other people
+    especially when it'll make their job of syncing with other distros
+harder :-(
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018392.html b/zarb-ml/mageia-dev/2012-August/018392.html new file mode 100644 index 000000000..869494987 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018392.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] Rakudo + + + + + + + + + +

[Mageia-dev] Rakudo

+ Sandro CAZZANIGA + cazzaniga.sandro at gmail.com +
+ Fri Aug 31 14:17:03 CEST 2012 +

+
+ +
Hi guys,
+
+Can someone package rakudo on cauldron? I don''t have any cauldron
+here, so I just join a spec file, in the hope that a nice and brillant
+packager can build it locally (for cauldron). Maybe it needs a
+dependance on NQP.
+
+ I can maintain it, just tell me the result of the build please.
+
+thanks in advance
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: rakudo.spec
+Type: application/octet-stream
+Size: 1303 bytes
+Desc: not available
+URL: </pipermail/mageia-dev/attachments/20120831/b2eec9f7/attachment.obj>
+
+ + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018393.html b/zarb-ml/mageia-dev/2012-August/018393.html new file mode 100644 index 000000000..8a08ca8e1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018393.html @@ -0,0 +1,58 @@ + + + + [Mageia-dev] Kristoffer Grundström vill lägga till dig på Zoosk! + + + + + + + + + +

[Mageia-dev] Kristoffer Grundström vill lägga till dig på Zoosk!

+ Kristoffer Grundström + kristoffer.grundstrom1983 at gmail.com +
+ Fri Aug 31 16:56:11 CEST 2012 +

+
+ +
An HTML attachment was scrubbed...
+URL: </pipermail/mageia-dev/attachments/20120831/16833863/attachment.html>
+
+ + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018394.html b/zarb-ml/mageia-dev/2012-August/018394.html new file mode 100644 index 000000000..1237bda3f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018394.html @@ -0,0 +1,73 @@ + + + + [Mageia-dev] Rakudo + + + + + + + + + +

[Mageia-dev] Rakudo

+ Malo + pierre-malo.denielou at rhul.ac.uk +
+ Fri Aug 31 17:13:44 CEST 2012 +

+
+ +
On 31/08/12 13:17, Sandro CAZZANIGA wrote:
+> Hi guys,
+>
+> Can someone package rakudo on cauldron? I don''t have any cauldron
+> here, so I just join a spec file, in the hope that a nice and brillant
+> packager can build it locally (for cauldron). Maybe it needs a
+> dependance on NQP.
+>
+>   I can maintain it, just tell me the result of the build please.
+>
+> thanks in advance
+
+You should open a bug report for that.
+
+Cheers,
+-- 
+Malo
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018395.html b/zarb-ml/mageia-dev/2012-August/018395.html new file mode 100644 index 000000000..1bc5529be --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018395.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] Rakudo + + + + + + + + + +

[Mageia-dev] Rakudo

+ Nicolas Lécureuil + nicolas.lecureuil at free.fr +
+ Fri Aug 31 17:24:18 CEST 2012 +

+
+ +
Le vendredi 31 août 2012 16:13:44 Malo a écrit :
+> On 31/08/12 13:17, Sandro CAZZANIGA wrote:
+> > Hi guys,
+> > 
+> > Can someone package rakudo on cauldron? I don''t have any cauldron
+> > here, so I just join a spec file, in the hope that a nice and brillant
+> > packager can build it locally (for cauldron). Maybe it needs a
+> > dependance on NQP.
+> > 
+> >   I can maintain it, just tell me the result of the build please.
+> > 
+> > thanks in advance
+> 
+> You should open a bug report for that.
+> 
+> Cheers,
+
+or better, use a chroot to test on a cauldron.
+
+ + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/018396.html b/zarb-ml/mageia-dev/2012-August/018396.html new file mode 100644 index 000000000..fba8faeff --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018396.html @@ -0,0 +1,70 @@ + + + + [Mageia-dev] Rakudo + + + + + + + + + +

[Mageia-dev] Rakudo

+ AL13N + alien at rmail.be +
+ Fri Aug 31 17:24:59 CEST 2012 +

+
+ +
Op vrijdag 31 augustus 2012 14:17:03 schreef Sandro CAZZANIGA:
+> Hi guys,
+> 
+> Can someone package rakudo on cauldron? I don''t have any cauldron
+> here, so I just join a spec file, in the hope that a nice and brillant
+> packager can build it locally (for cauldron). Maybe it needs a
+> dependance on NQP.
+> 
+>  I can maintain it, just tell me the result of the build please.
+> 
+> thanks in advance
+
+maybe you could have a virtual cauldron?
+
+or you can ask your mentor to submit build for cauldron
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ diff --git a/zarb-ml/mageia-dev/2012-August/author.html b/zarb-ml/mageia-dev/2012-August/author.html new file mode 100644 index 000000000..0e83a763a --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/author.html @@ -0,0 +1,2827 @@ + + + + The Mageia-dev August 2012 Archive by author + + + + + +

August 2012 Archives by author

+ +

Starting: Wed Aug 1 00:09:39 CEST 2012
+ Ending: Fri Aug 31 17:24:59 CEST 2012
+ Messages: 556

+

+

+ Last message date: + Fri Aug 31 17:24:59 CEST 2012
+ Archived on: Fri Aug 31 17:25:08 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-dev/2012-August/date.html b/zarb-ml/mageia-dev/2012-August/date.html new file mode 100644 index 000000000..afee52cd6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/date.html @@ -0,0 +1,2827 @@ + + + + The Mageia-dev August 2012 Archive by date + + + + + +

August 2012 Archives by date

+ +

Starting: Wed Aug 1 00:09:39 CEST 2012
+ Ending: Fri Aug 31 17:24:59 CEST 2012
+ Messages: 556

+

+

+ Last message date: + Fri Aug 31 17:24:59 CEST 2012
+ Archived on: Fri Aug 31 17:25:08 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-dev/2012-August/index.html b/zarb-ml/mageia-dev/2012-August/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/index.html @@ -0,0 +1 @@ +thread.html \ No newline at end of file diff --git a/zarb-ml/mageia-dev/2012-August/subject.html b/zarb-ml/mageia-dev/2012-August/subject.html new file mode 100644 index 000000000..7f0c24fbe --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/subject.html @@ -0,0 +1,2827 @@ + + + + The Mageia-dev August 2012 Archive by subject + + + + + +

August 2012 Archives by subject

+ +

Starting: Wed Aug 1 00:09:39 CEST 2012
+ Ending: Fri Aug 31 17:24:59 CEST 2012
+ Messages: 556

+

+

+ Last message date: + Fri Aug 31 17:24:59 CEST 2012
+ Archived on: Fri Aug 31 17:25:08 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + diff --git a/zarb-ml/mageia-dev/2012-August/thread.html b/zarb-ml/mageia-dev/2012-August/thread.html new file mode 100644 index 000000000..3315fcf95 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/thread.html @@ -0,0 +1,3779 @@ + + + + The Mageia-dev August 2012 Archive by thread + + + + + +

August 2012 Archives by thread

+ +

Starting: Wed Aug 1 00:09:39 CEST 2012
+ Ending: Fri Aug 31 17:24:59 CEST 2012
+ Messages: 556

+

+

+ Last message date: + Fri Aug 31 17:24:59 CEST 2012
+ Archived on: Fri Aug 31 17:25:08 CEST 2012 +

+

+

+

+ This archive was generated by + Pipermail 0.09 (Mailman edition). + + + -- cgit v1.2.1