[jira] [Commented] (ARROW-3654) [Python] Column with CategoricalIndex fails to be read back

[Armin Berres (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARROW-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832511#comment-16832511
 ] 

Armin Berres commented on ARROW-3654:
-

Confirmed, work for me as well now.

> [Python] Column with CategoricalIndex fails to be read back
> ---
>
> Key: ARROW-3654
> URL: https://issues.apache.org/jira/browse/ARROW-3654
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: Python
>Affects Versions: 0.11.1
>Reporter: Armin Berres
>Priority: Major
>  Labels: parquet
>
> When a column with a \{Categoricalndex} is written the data can never be read 
> back.
>  {code:python}
> df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
> df['c1'] = df['c1'].astype('category')
> df = df.set_index(['c1'])
> table = pa.Table.from_pandas(df)
> pq.write_table(table, 'test.parquet')
> pq.read_pandas('test.parquet').to_pandas()
> {code}
> Results in
> {code}
> KeyError  Traceback (most recent call last)
> ~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
> _pandas_type_to_numpy_type(pandas_type)
> 676 try:
> --> 677 return _pandas_logical_type_map[pandas_type]
> 678 except KeyError:
> KeyError: 'categorical'
> {code}
> The schema looks good:
> {code}
> column_indexes": [{"name": "c1", "field_name": "c1", "pandas_type": 
> "categorical", "numpy_type": "int8", "metadata": {"num_categories": 2, 
> "ordered": false}}]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ARROW-3654) [Python] Column with CategoricalIndex fails to be read back

[Armin Berres (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARROW-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Armin Berres resolved ARROW-3654.
-
Resolution: Fixed

> [Python] Column with CategoricalIndex fails to be read back
> ---
>
> Key: ARROW-3654
> URL: https://issues.apache.org/jira/browse/ARROW-3654
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: Python
>Affects Versions: 0.11.1
>Reporter: Armin Berres
>Priority: Major
>  Labels: parquet
>
> When a column with a \{Categoricalndex} is written the data can never be read 
> back.
>  {code:python}
> df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
> df['c1'] = df['c1'].astype('category')
> df = df.set_index(['c1'])
> table = pa.Table.from_pandas(df)
> pq.write_table(table, 'test.parquet')
> pq.read_pandas('test.parquet').to_pandas()
> {code}
> Results in
> {code}
> KeyError  Traceback (most recent call last)
> ~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
> _pandas_type_to_numpy_type(pandas_type)
> 676 try:
> --> 677 return _pandas_logical_type_map[pandas_type]
> 678 except KeyError:
> KeyError: 'categorical'
> {code}
> The schema looks good:
> {code}
> column_indexes": [{"name": "c1", "field_name": "c1", "pandas_type": 
> "categorical", "numpy_type": "int8", "metadata": {"num_categories": 2, 
> "ordered": false}}]
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ARROW-3652) [Python] CategoricalIndex is lost after reading back

[Armin Berres (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ARROW-3652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Armin Berres updated ARROW-3652:

Affects Version/s: 0.11.1

> [Python] CategoricalIndex is lost after reading back
> 
>
> Key: ARROW-3652
> URL: https://issues.apache.org/jira/browse/ARROW-3652
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: Python
>Affects Versions: 0.11.1
>Reporter: Armin Berres
>Priority: Major
>
> When a {{CategoricalIndex}} is written and read back the resulting index is 
> not more categorical.
> {code}
> df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
> df['c1'] = df['c1'].astype('category')
> df = df.set_index(['c1'])
> table = pa.Table.from_pandas(df)
> pq.write_table(table, 'test.parquet')
> ref_df = pq.read_pandas('test.parquet').to_pandas()
> print(df.index)
> # CategoricalIndex(['a', 'c'], categories=['a', 'c'], ordered=False, 
> name='c1', dtype='category')
> print(ref_df.index)
> # Index(['a', 'c'], dtype='object', name='c1')
> {code}
> In the metadata the information is correctly contained:
> {code:java}
> {"name": "c1", "field_name": "c1", "p'
> b'andas_type": "categorical", "numpy_type": "int8", "metadata": 
> {"'
> b'num_categories": 2, "ordered": false}
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3654) [Python] Column with CategoricalIndex fails to be read back

[Armin Berres (JIRA)]

Armin Berres created ARROW-3654:
---

 Summary: [Python] Column with CategoricalIndex fails to be read 
back
 Key: ARROW-3654
 URL: https://issues.apache.org/jira/browse/ARROW-3654
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Affects Versions: 0.11.1
Reporter: Armin Berres


When a column with a \{Categoricalndex} is written the data can never be read 
back.

 {code:python}
df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
df['c1'] = df['c1'].astype('category')
df = df.set_index(['c1'])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

pq.read_pandas('test.parquet').to_pandas()
{code}

Results in

{code}
KeyError  Traceback (most recent call last)
~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
_pandas_type_to_numpy_type(pandas_type)
676 try:
--> 677 return _pandas_logical_type_map[pandas_type]
678 except KeyError:

KeyError: 'categorical'
{code}

The schema looks good:
{code}
column_indexes": [{"name": "c1", "field_name": "c1", "pandas_type": 
"categorical", "numpy_type": "int8", "metadata": {"num_categories": 2, 
"ordered": false}}]
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3654) [Python] Column with CategoricalIndex fails to be read back

[Armin Berres (JIRA)]

Armin Berres created ARROW-3654:
---

 Summary: [Python] Column with CategoricalIndex fails to be read 
back
 Key: ARROW-3654
 URL: https://issues.apache.org/jira/browse/ARROW-3654
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Affects Versions: 0.11.1
Reporter: Armin Berres


When a column with a \{Categoricalndex} is written the data can never be read 
back.

 {code:python}
df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
df['c1'] = df['c1'].astype('category')
df = df.set_index(['c1'])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

pq.read_pandas('test.parquet').to_pandas()
{code}

Results in

{code}
KeyError  Traceback (most recent call last)
~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
_pandas_type_to_numpy_type(pandas_type)
676 try:
--> 677 return _pandas_logical_type_map[pandas_type]
678 except KeyError:

KeyError: 'categorical'
{code}

The schema looks good:
{code}
column_indexes": [{"name": "c1", "field_name": "c1", "pandas_type": 
"categorical", "numpy_type": "int8", "metadata": {"num_categories": 2, 
"ordered": false}}]
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3652) [Python] CategoricalIndex is lost after reading back

[Armin Berres (JIRA)]

Armin Berres created ARROW-3652:
---

 Summary: [Python] CategoricalIndex is lost after reading back
 Key: ARROW-3652
 URL: https://issues.apache.org/jira/browse/ARROW-3652
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Reporter: Armin Berres


When a {{CategoricalIndex}} is written and read back the resulting index is not 
more categorical.
{code}
df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
df['c1'] = df['c1'].astype('category')
df = df.set_index(['c1'])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

ref_df = pq.read_pandas('test.parquet').to_pandas()

print(df.index)
# CategoricalIndex(['a', 'c'], categories=['a', 'c'], ordered=False, name='c1', 
dtype='category')

print(ref_df.index)
# Index(['a', 'c'], dtype='object', name='c1')
{code}
In the metadata the information is correctly contained:
{code:java}
{"name": "c1", "field_name": "c1", "p'
b'andas_type": "categorical", "numpy_type": "int8", "metadata": {"'
b'num_categories": 2, "ordered": false}
{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3652) [Python] CategoricalIndex is lost after reading back

[Armin Berres (JIRA)]

Armin Berres created ARROW-3652:
---

 Summary: [Python] CategoricalIndex is lost after reading back
 Key: ARROW-3652
 URL: https://issues.apache.org/jira/browse/ARROW-3652
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Reporter: Armin Berres


When a {{CategoricalIndex}} is written and read back the resulting index is not 
more categorical.
{code}
df = pd.DataFrame([['a', 'b'], ['c', 'd']], columns=['c1', 'c2'])
df['c1'] = df['c1'].astype('category')
df = df.set_index(['c1'])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

ref_df = pq.read_pandas('test.parquet').to_pandas()

print(df.index)
# CategoricalIndex(['a', 'c'], categories=['a', 'c'], ordered=False, name='c1', 
dtype='category')

print(ref_df.index)
# Index(['a', 'c'], dtype='object', name='c1')
{code}
In the metadata the information is correctly contained:
{code:java}
{"name": "c1", "field_name": "c1", "p'
b'andas_type": "categorical", "numpy_type": "int8", "metadata": {"'
b'num_categories": 2, "ordered": false}
{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARROW-3651) [Python] Datetimes from non-DateTimeIndex cannot be deserialized

[Armin Berres (JIRA)]

[ 
https://issues.apache.org/jira/browse/ARROW-3651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668434#comment-16668434
 ] 

Armin Berres commented on ARROW-3651:
-

Not sure but maybe Pandas should behave different in this case as well and 
create a {{DateTimeIndex}} index in this case as the complete index consists of 
{{Timestamp}} objects?

{{df.columns = pd.to_datetime(df.columns)}} in the code above mitigates the 
problem.

 

> [Python] Datetimes from non-DateTimeIndex cannot be deserialized
> 
>
> Key: ARROW-3651
> URL: https://issues.apache.org/jira/browse/ARROW-3651
> Project: Apache Arrow
>  Issue Type: Bug
>  Components: Python
>Affects Versions: 0.11.1
>Reporter: Armin Berres
>Priority: Major
>
> Given an index which contains datetimes but is no DateTimeIndex writing the 
> file works but reading back fails.
> {code:python}
> df = pd.DataFrame(1, index=pd.MultiIndex.from_arrays([[1,2],[3,4]]), 
> columns=[pd.to_datetime("2018/01/01")])
> # columns index is no DateTimeIndex anymore
> df = df.reset_index().set_index(['level_0', 'level_1'])
> table = pa.Table.from_pandas(df)
> pq.write_table(table, 'test.parquet')
> pq.read_pandas('test.parquet').to_pandas()
> {code}
> results in 
> {code}
> KeyError  Traceback (most recent call last)
> ~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
> _pandas_type_to_numpy_type(pandas_type)
> 676 try:
> --> 677 return _pandas_logical_type_map[pandas_type]
> 678 except KeyError:
> KeyError: 'datetime'
> {code}
> The created schema:
> {code}
> 2018-01-01 00:00:00: int64
> level_0: int64
> level_1: int64
> metadata
> 
> {b'pandas': b'{"index_columns": ["level_0", "level_1"], "column_indexes": 
> [{"n'
> b'ame": null, "field_name": null, "pandas_type": "datetime", 
> "nump'
> b'y_type": "object", "metadata": null}], "columns": [{"name": 
> "201'
> b'8-01-01 00:00:00", "field_name": "2018-01-01 00:00:00", 
> "pandas_'
> b'type": "int64", "numpy_type": "int64", "metadata": null}, 
> {"name'
> b'": "level_0", "field_name": "level_0", "pandas_type": "int64", 
> "'
> b'numpy_type": "int64", "metadata": null}, {"name": "level_1", 
> "fi'
> b'eld_name": "level_1", "pandas_type": "int64", "numpy_type": 
> "int'
> b'64", "metadata": null}], "pandas_version": "0.23.4"}'}
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3651) [Python] Datetimes from non-DateTimeIndex cannot be deserialized

[Armin Berres (JIRA)]

Armin Berres created ARROW-3651:
---

 Summary: [Python] Datetimes from non-DateTimeIndex cannot be 
deserialized
 Key: ARROW-3651
 URL: https://issues.apache.org/jira/browse/ARROW-3651
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Affects Versions: 0.11.1
Reporter: Armin Berres


Given an index which contains datetimes but is no DateTimeIndex writing the 
file works but reading back fails.
{code:python}
df = pd.DataFrame(1, index=pd.MultiIndex.from_arrays([[1,2],[3,4]]), 
columns=[pd.to_datetime("2018/01/01")])

# columns index is no DateTimeIndex anymore
df = df.reset_index().set_index(['level_0', 'level_1'])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

pq.read_pandas('test.parquet').to_pandas()
{code}

results in 
{code}
KeyError  Traceback (most recent call last)
~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
_pandas_type_to_numpy_type(pandas_type)
676 try:
--> 677 return _pandas_logical_type_map[pandas_type]
678 except KeyError:

KeyError: 'datetime'
{code}

The created schema:

{code}
2018-01-01 00:00:00: int64
level_0: int64
level_1: int64
metadata

{b'pandas': b'{"index_columns": ["level_0", "level_1"], "column_indexes": [{"n'
b'ame": null, "field_name": null, "pandas_type": "datetime", "nump'
b'y_type": "object", "metadata": null}], "columns": [{"name": "201'
b'8-01-01 00:00:00", "field_name": "2018-01-01 00:00:00", "pandas_'
b'type": "int64", "numpy_type": "int64", "metadata": null}, {"name'
b'": "level_0", "field_name": "level_0", "pandas_type": "int64", "'
b'numpy_type": "int64", "metadata": null}, {"name": "level_1", "fi'
b'eld_name": "level_1", "pandas_type": "int64", "numpy_type": "int'
b'64", "metadata": null}], "pandas_version": "0.23.4"}'}
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3651) [Python] Datetimes from non-DateTimeIndex cannot be deserialized

[Armin Berres (JIRA)]

Armin Berres created ARROW-3651:
---

 Summary: [Python] Datetimes from non-DateTimeIndex cannot be 
deserialized
 Key: ARROW-3651
 URL: https://issues.apache.org/jira/browse/ARROW-3651
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Affects Versions: 0.11.1
Reporter: Armin Berres


Given an index which contains datetimes but is no DateTimeIndex writing the 
file works but reading back fails.
{code:python}
df = pd.DataFrame(1, index=pd.MultiIndex.from_arrays([[1,2],[3,4]]), 
columns=[pd.to_datetime("2018/01/01")])

# columns index is no DateTimeIndex anymore
df = df.reset_index().set_index(['level_0', 'level_1'])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

pq.read_pandas('test.parquet').to_pandas()
{code}

results in 
{code}
KeyError  Traceback (most recent call last)
~/venv/mpptool/lib/python3.7/site-packages/pyarrow/pandas_compat.py in 
_pandas_type_to_numpy_type(pandas_type)
676 try:
--> 677 return _pandas_logical_type_map[pandas_type]
678 except KeyError:

KeyError: 'datetime'
{code}

The created schema:

{code}
2018-01-01 00:00:00: int64
level_0: int64
level_1: int64
metadata

{b'pandas': b'{"index_columns": ["level_0", "level_1"], "column_indexes": [{"n'
b'ame": null, "field_name": null, "pandas_type": "datetime", "nump'
b'y_type": "object", "metadata": null}], "columns": [{"name": "201'
b'8-01-01 00:00:00", "field_name": "2018-01-01 00:00:00", "pandas_'
b'type": "int64", "numpy_type": "int64", "metadata": null}, {"name'
b'": "level_0", "field_name": "level_0", "pandas_type": "int64", "'
b'numpy_type": "int64", "metadata": null}, {"name": "level_1", "fi'
b'eld_name": "level_1", "pandas_type": "int64", "numpy_type": "int'
b'64", "metadata": null}], "pandas_version": "0.23.4"}'}
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3650) [Python] Mixed column indexes are read back as strings

[Armin Berres (JIRA)]

Armin Berres created ARROW-3650:
---

 Summary: [Python] Mixed column indexes are read back as strings 
 Key: ARROW-3650
 URL: https://issues.apache.org/jira/browse/ARROW-3650
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Affects Versions: 0.11.1
Reporter: Armin Berres


Consider the following example: 

{code:java}
df = pd.DataFrame(1, index=[pd.to_datetime('2018/01/01')], columns=['a string', 
pd.to_datetime('2018/01/02')])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

ref_df = pq.read_pandas('test.parquet').to_pandas()

print(df.columns)
# Index(['a string', 2018-01-02 00:00:00], dtype='object')
print(ref_df.columns)
# Index(['a string', '2018-01-02 00:00:00'], dtype='object')
{code}

The serialized data frame has an index with a string and a datetime field 
(happened when resetting the index of a formerly datetime only column).
When reading the string back the datetime is converted into a string.

When looking at the schema I find {{"pandas_type": "mixed", "numpy_ty'
b'pe": "object"}} before serializing and {{"pandas_type": 
"unicode", "numpy_'
b'type": "object"}} after reading back. So the schema was aware of 
the mixed type but did not store the actual types.

The same happens with other types like numbers as well. One can produce 
interesting situations:

{{pd.DataFrame(1, index=[pd.to_datetime('2018/01/01')], columns=['1', 1])}} can 
be written but fails to be read back as the index is no more unique with '1' 
showing up two times.

IIf this is not a bug but expected maybe the user should be somehow warned that 
information is lost? Like a {{NotImplemented}} exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ARROW-3650) [Python] Mixed column indexes are read back as strings

[Armin Berres (JIRA)]

Armin Berres created ARROW-3650:
---

 Summary: [Python] Mixed column indexes are read back as strings 
 Key: ARROW-3650
 URL: https://issues.apache.org/jira/browse/ARROW-3650
 Project: Apache Arrow
  Issue Type: Bug
  Components: Python
Affects Versions: 0.11.1
Reporter: Armin Berres


Consider the following example: 

{code:java}
df = pd.DataFrame(1, index=[pd.to_datetime('2018/01/01')], columns=['a string', 
pd.to_datetime('2018/01/02')])

table = pa.Table.from_pandas(df)
pq.write_table(table, 'test.parquet')

ref_df = pq.read_pandas('test.parquet').to_pandas()

print(df.columns)
# Index(['a string', 2018-01-02 00:00:00], dtype='object')
print(ref_df.columns)
# Index(['a string', '2018-01-02 00:00:00'], dtype='object')
{code}

The serialized data frame has an index with a string and a datetime field 
(happened when resetting the index of a formerly datetime only column).
When reading the string back the datetime is converted into a string.

When looking at the schema I find {{"pandas_type": "mixed", "numpy_ty'
b'pe": "object"}} before serializing and {{"pandas_type": 
"unicode", "numpy_'
b'type": "object"}} after reading back. So the schema was aware of 
the mixed type but did not store the actual types.

The same happens with other types like numbers as well. One can produce 
interesting situations:

{{pd.DataFrame(1, index=[pd.to_datetime('2018/01/01')], columns=['1', 1])}} can 
be written but fails to be read back as the index is no more unique with '1' 
showing up two times.

IIf this is not a bug but expected maybe the user should be somehow warned that 
information is lost? Like a {{NotImplemented}} exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Bug#619193: Workaround is working

[Armin Berres]

Yay, great!
LD_PRELOAD=/usr/lib/libstdc++.so.6 pytrainer
fixes the issue.

Good enough as a workaround for the moment.

Thanks,
Armin



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

[Python-modules-team] Bug#619193: Workaround is working

[Armin Berres]

Yay, great!
LD_PRELOAD=/usr/lib/libstdc++.so.6 pytrainer
fixes the issue.

Good enough as a workaround for the moment.

Thanks,
Armin



___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team

Bug#619193: [python-matplotlib] python-matplotlib: crash in py_to_agg_transformation_matrix

[Armin Berres]

Package: python-matplotlib
Version: 1.0.1-1

pytrainer is not really usable as it crashes all the time when it tries 
to render something with matplotlib.
To reproduce: Install and start pytrainer. Select FileNew and create an 
entry with a random distance and a random duration.
Now try to switch to the week view and observe the crash. The backtrace 
looks like this:


#0  0x7fffef9f6ae4 in __cxa_allocate_exception () from 
/usr/lib/libstdc++.so.6
#1  0x7fffe3102ae4 in py_to_agg_transformation_matrix(_object*, 
bool) () from /usr/lib/pymodules/python2.6/matplotlib/_path.so
#2  0x7fffe310d6eb in _path_module::update_path_extents(Py::Tuple 
const) () from /usr/lib/pymodules/python2.6/matplotlib/_path.so
#3  0x7fffe31143e8 in 
Py::ExtensionModule_path_module::invoke_method_varargs(void*, 
Py::Tuple const) () from /usr/lib/pymodules/python2.6/matplotlib/_path.so
#4  0x7fffe30ff6fd in method_varargs_call_handler () from 
/usr/lib/pymodules/python2.6/matplotlib/_path.so

#5  0x004a7ba5 in PyEval_EvalFrameEx ()


--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.37-2-amd64

Debian Release: wheezy/sid
  500 unstableftp.de.debian.org
  500 testing ftp.de.debian.org
  500 stable  ftp.de.debian.org
1 experimentalftp.de.debian.org

--- Package information. ---
Depends(Version) | Installed
-+-==
python-cairo | 1.8.8-1+b1
python-dateutil  | 1.4.1-3
python-gobject   | 2.21.4+is.2.21.3-1
python-matplotlib-data  (= 1.0.1-1) | 1.0.1-1
python-numpy(= 1:1.3.0) | 1:1.4.1-5
python-pyparsing | 1.5.2-2
python-tz| 2010b-1
python  ( 2.7) | 2.6.6-3+squeeze5
python  (= 2.5) | 2.6.6-3+squeeze5
python-support   (= 0.90.0) | 1.0.11
libatk1.0-0  (= 1.29.3) | 1.30.0-1
libc6 (= 2.2.5) | 2.11.2-13
libcairo2 (= 1.2.4) | 1.10.2-4
libfontconfig1(= 2.8.0) | 2.8.0-2.1
libfreetype6  (= 2.2.1) | 2.4.4-1
libgcc1 (= 1:4.1.1) | 1:4.5.2-5
libglib2.0-0 (= 2.16.0) | 2.28.1-1+b1
libgtk2.0-0   (= 2.8.0) | 2.20.1-2
libpango1.0-0(= 1.14.0) | 1.28.3-2~sid1
libpng12-0 (= 1.2.13-4) | 1.2.44-1
libstdc++6(= 4.4.0) | 4.5.2-5
tcl8.5(= 8.5.0) | 8.5.9-2
tk8.5 (= 8.5.0) | 8.5.9-2
zlib1g  (= 1:1.1.4) | 1:1.2.3.4.dfsg-3


Recommends (Version) | Installed
-+-===
python-glade2| 2.17.0-4
python-tk (= 2.5.2-1.1) | 2.7.1-1


Suggests   (Version) | Installed
-+-===
dvipng   |
ipython   (= 0.6.3) |
librsvg2-common  | 2.26.3-1
python-configobj |
python-excelerator   |
python-gtk2  | 2.17.0-4
python-matplotlib-doc|
python-qt3   | 3.18.1-4+b1
python-qt4   | 4.8.3-1
python-scipy | 0.7.2+dfsg1-1
python-traits   (= 2.0) |
python-wxgtk2.8  |
texlive-extra-utils  | 2009-10
texlive-latex-extra  | 2009-10







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

[Python-modules-team] Bug#619193: [python-matplotlib] python-matplotlib: crash in py_to_agg_transformation_matrix

[Armin Berres]

Package: python-matplotlib
Version: 1.0.1-1

pytrainer is not really usable as it crashes all the time when it tries 
to render something with matplotlib.
To reproduce: Install and start pytrainer. Select FileNew and create an 
entry with a random distance and a random duration.
Now try to switch to the week view and observe the crash. The backtrace 
looks like this:


#0  0x7fffef9f6ae4 in __cxa_allocate_exception () from 
/usr/lib/libstdc++.so.6
#1  0x7fffe3102ae4 in py_to_agg_transformation_matrix(_object*, 
bool) () from /usr/lib/pymodules/python2.6/matplotlib/_path.so
#2  0x7fffe310d6eb in _path_module::update_path_extents(Py::Tuple 
const) () from /usr/lib/pymodules/python2.6/matplotlib/_path.so
#3  0x7fffe31143e8 in 
Py::ExtensionModule_path_module::invoke_method_varargs(void*, 
Py::Tuple const) () from /usr/lib/pymodules/python2.6/matplotlib/_path.so
#4  0x7fffe30ff6fd in method_varargs_call_handler () from 
/usr/lib/pymodules/python2.6/matplotlib/_path.so

#5  0x004a7ba5 in PyEval_EvalFrameEx ()


--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.37-2-amd64

Debian Release: wheezy/sid
  500 unstableftp.de.debian.org
  500 testing ftp.de.debian.org
  500 stable  ftp.de.debian.org
1 experimentalftp.de.debian.org

--- Package information. ---
Depends(Version) | Installed
-+-==
python-cairo | 1.8.8-1+b1
python-dateutil  | 1.4.1-3
python-gobject   | 2.21.4+is.2.21.3-1
python-matplotlib-data  (= 1.0.1-1) | 1.0.1-1
python-numpy(= 1:1.3.0) | 1:1.4.1-5
python-pyparsing | 1.5.2-2
python-tz| 2010b-1
python  ( 2.7) | 2.6.6-3+squeeze5
python  (= 2.5) | 2.6.6-3+squeeze5
python-support   (= 0.90.0) | 1.0.11
libatk1.0-0  (= 1.29.3) | 1.30.0-1
libc6 (= 2.2.5) | 2.11.2-13
libcairo2 (= 1.2.4) | 1.10.2-4
libfontconfig1(= 2.8.0) | 2.8.0-2.1
libfreetype6  (= 2.2.1) | 2.4.4-1
libgcc1 (= 1:4.1.1) | 1:4.5.2-5
libglib2.0-0 (= 2.16.0) | 2.28.1-1+b1
libgtk2.0-0   (= 2.8.0) | 2.20.1-2
libpango1.0-0(= 1.14.0) | 1.28.3-2~sid1
libpng12-0 (= 1.2.13-4) | 1.2.44-1
libstdc++6(= 4.4.0) | 4.5.2-5
tcl8.5(= 8.5.0) | 8.5.9-2
tk8.5 (= 8.5.0) | 8.5.9-2
zlib1g  (= 1:1.1.4) | 1:1.2.3.4.dfsg-3


Recommends (Version) | Installed
-+-===
python-glade2| 2.17.0-4
python-tk (= 2.5.2-1.1) | 2.7.1-1


Suggests   (Version) | Installed
-+-===
dvipng   |
ipython   (= 0.6.3) |
librsvg2-common  | 2.26.3-1
python-configobj |
python-excelerator   |
python-gtk2  | 2.17.0-4
python-matplotlib-doc|
python-qt3   | 3.18.1-4+b1
python-qt4   | 4.8.3-1
python-scipy | 0.7.2+dfsg1-1
python-traits   (= 2.0) |
python-wxgtk2.8  |
texlive-extra-utils  | 2009-10
texlive-latex-extra  | 2009-10







___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team

Accepted ksshaskpass 0.5.3-1 (source amd64)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 02 Jan 2010 00:01:55 +0100
Source: ksshaskpass
Binary: ksshaskpass
Architecture: source amd64
Version: 0.5.3-1
Distribution: unstable
Urgency: low
Maintainer: Armin Berres armin+deb...@space-based.de
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 ksshaskpass - interactively prompt users for a passphrase for ssh-add
Changes: 
 ksshaskpass (0.5.3-1) unstable; urgency=low
 .
   * New upstream release.
 - Upload to unstable.
   * Raise standards version to 3.8.3. No changes needed.
   * Use dh v7 and minimal rules file:
 - Build depend on debhelper 7.3 for cmake support.
   * Switch package to dpkg-source format 3.0 (quilt).
   * Add README.Debian.
   * Update my email address.
   * Depend on ${misc:Depends}.
   * Override lintian warning 'desktop-command-not-in-package'.
   * Remove unused postrm file.
Checksums-Sha1: 
 cb9ad954366b9e7f4463c1aa80739f0d736300f9 1135 ksshaskpass_0.5.3-1.dsc
 e3f83e1cc1105cc4476fdc5a9300d770aa10b78b 11010 ksshaskpass_0.5.3.orig.tar.gz
 3df227b2d6e93dfbb4429f637b687bb84e9bea1e 2744 ksshaskpass_0.5.3-1.debian.tar.gz
 5b42ba2a035c64f4055106960f5c6b7fe1de5eb7 9568 ksshaskpass_0.5.3-1_amd64.deb
Checksums-Sha256: 
 0e7c0ec27d122443946ba2a3a32684b26db5fee6291a69415053ad2d35e90e47 1135 
ksshaskpass_0.5.3-1.dsc
 a3a47eba74a52ec3d9d8740ed9a29a5aa852d4e268b5d81154f85b90258a2124 11010 
ksshaskpass_0.5.3.orig.tar.gz
 05053f4355a8ca7bef10f53c71d35f3601b20cec6b4fd26fe2a96657c8868801 2744 
ksshaskpass_0.5.3-1.debian.tar.gz
 512f32a6978da8d879ea79f1b0ca0bf7da2ad2e50e21e6b34774d33f47355916 9568 
ksshaskpass_0.5.3-1_amd64.deb
Files: 
 82172bedc5bd3577b25084c1d4a999c0 1135 utils optional ksshaskpass_0.5.3-1.dsc
 05dad7745e9d92b08bd86e7ab7a9540d 11010 utils optional 
ksshaskpass_0.5.3.orig.tar.gz
 a9e9590006af4fa5db3e66278c8fbf97 2744 utils optional 
ksshaskpass_0.5.3-1.debian.tar.gz
 d0d41cd436cb82e34839854a8d71d048 9568 utils optional 
ksshaskpass_0.5.3-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Signed by Ana Guerrero

iEYEARECAAYFAks+hu4ACgkQn3j4POjENGGcSACfeebVKeI4pDZGaoTlJcFDaSDu
NyEAn1v6E+yVOI5mSjkY9j+AyDJbMqRP
=cNhT
-END PGP SIGNATURE-


Accepted:
ksshaskpass_0.5.3-1.debian.tar.gz
  to main/k/ksshaskpass/ksshaskpass_0.5.3-1.debian.tar.gz
ksshaskpass_0.5.3-1.dsc
  to main/k/ksshaskpass/ksshaskpass_0.5.3-1.dsc
ksshaskpass_0.5.3-1_amd64.deb
  to main/k/ksshaskpass/ksshaskpass_0.5.3-1_amd64.deb
ksshaskpass_0.5.3.orig.tar.gz
  to main/k/ksshaskpass/ksshaskpass_0.5.3.orig.tar.gz


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#553180: [akonadi-server] Looses data

[Armin Berres]

tags 553180 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 553180 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#553180: [akonadi-server] Looses data

[Armin Berres]

tags 553180 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 553180 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#552041: kmail: KMail tortures my hdd for minutes after every startup

[Armin Berres]

tags 552041 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 552041 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#552041: kmail: KMail tortures my hdd for minutes after every startup

[Armin Berres]

tags 552041 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 552041 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551910: [dolphin] Dolphin and directory watching

[Armin Berres]

tags 551910 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 551910 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551894: ktimetracker 4.3.2 reports itself as 4.3.1, distorted gui

[Armin Berres]

tags 551894 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 551894 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551910: [dolphin] Dolphin and directory watching

[Armin Berres]

tags 551910 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 551910 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551894: ktimetracker 4.3.2 reports itself as 4.3.1, distorted gui

[Armin Berres]

tags 551894 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 551894 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551552: Kmail does not quote original message when replying or forwarding

[Armin Berres]

tags 551552 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 551552 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#551552: Kmail does not quote original message when replying or forwarding

[Armin Berres]

tags 551552 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 551552 KDE-BUG-URL
thanks
[ copy this ]

If you need any help or have questions do not hesitate to contact me.

Greetings,
Armin Berres



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#550992: Unable to start session with kdm

[Armin Berres]

On Wed, 14 Oct 09 20:20, denis wrote:
 Package: kdm
 Version: 4:4.3.1-1
 Severity: normal

Erm, would you mind to give us some more information?
What exactly are you doing, what do you expect, what happens...?
Do you see anything interesting in the logs? Candidates are e.g.
/var/log/kdm.log, /var/log/Xorg.0.log or ~/.xsession-errors.

Greetings,
Armin

PS: Please do not CC me in replies.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#550992: Replay

[Armin Berres]

reassign 550992 libgl1-mesa-dri
kthxbye

On Wed, 14 Oct 09 22:58, Denis Gottardello wrote:
 
 I cannot login in kde through kdm.
 Look at the end of this mail, /var/log/daemon.log.
 
 turbofinist:~# tail -f /var/log/kdm.log
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 
 
 X: main/renderbuffer.c:2159: _mesa_reference_renderbuffer: Assertion 
 `oldRb-Magic == 0xaabbccdd' failed.
^^
Here we have the real problem. It is not about the nasty kdm warning
that it cannot open default.face.
I guess this is a problem in Mesa. I am reassigning this bug. Can you tell us
which version of libgl1-mesa-dri you have installed?

Greetings,
Armin

 
 X.Org X Server 1.6.4
 Release Date: 2009-9-27
 X Protocol Version 11, Revision 0
 Build Operating System: Linux 2.6.31 i686 Debian
 Current Operating System: Linux turbofinist 2.6.30-1-686 #1 SMP Sat Aug 15 
 19:11:58 UTC 2009 i686
 Build Date: 30 September 2009  08:45:15PM
 xorg-server 2:1.6.4-2 (bgog...@debian.org)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
 Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 (==) Log file: /var/log/Xorg.0.log, Time: Wed Oct 14 22:46:40 2009
 (==) Using config file: /etc/X11/xorg.conf
 Fulfilled via DRI at 12587008
 Freed 12587008 (pool 2)
 SELinux: Disabled on system, not enabling in X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 
 turbofinist:~#
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 tail -f /var/log/Xorg.0.log
 (nothing)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 de...@turbofinist:~$ cat .xsession-errors
 Xsession: X session started for denis at mer ott 14 22:55:35 CEST 2009
 startkde: Starting up...
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
 kbuildsycoca4 running...
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
 kbuildsycoca4 running...
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kcminit_startup.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_ksmserver.so
 unknown program name(3908)/ KStartupInfo::createNewStartupId: 
 creating:  turbofinist;123737;234862;3908_TIME0 : unnamed app
 kephald starting up
 XRANDR error base:  162
 RRInput mask is set!!
 RandRScreen::loadSettings - adding mode:  117 1024 x 768
 RandRScreen::loadSettings - adding crtc:  115
 RandRScreen::loadSettings - adding output:  116
 Setting CRTC 115 on output default (previous 0 )
 CRTC outputs: (116)
 Output name: default
 Output refresh rate: 60
 Output rect: QRect(0,0 1024x768)
 Output rotation: 1
 XRandROutputs::init
   added output  116
 adding an output 0 with geom:  QRect(0,0 1024x768)
 output: SCREEN-0 QRect(0,0 1024x768) 0 true false
 load xml
 connected: 1
 looking for current SCREEN-0
 known * has score: 0.125
 screen: 0 QRect(0,0 1024x768)
 looking for a matching configuration...
 connected: 1
 looking for current SCREEN-0
 known * has score: 0.125
 found outputs, known: false
 activate external configuration!!
 registered the service: true
 screens registered on the bus: true
 outputs registered on the bus: true
 configurations registered on the bus: true
 

Bug#550992: Unable to start session with kdm

[Armin Berres]

On Wed, 14 Oct 09 20:20, denis wrote:
 Package: kdm
 Version: 4:4.3.1-1
 Severity: normal

Erm, would you mind to give us some more information?
What exactly are you doing, what do you expect, what happens...?
Do you see anything interesting in the logs? Candidates are e.g.
/var/log/kdm.log, /var/log/Xorg.0.log or ~/.xsession-errors.

Greetings,
Armin

PS: Please do not CC me in replies.



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#550992: Replay

[Armin Berres]

reassign 550992 libgl1-mesa-dri
kthxbye

On Wed, 14 Oct 09 22:58, Denis Gottardello wrote:
 
 I cannot login in kde through kdm.
 Look at the end of this mail, /var/log/daemon.log.
 
 turbofinist:~# tail -f /var/log/kdm.log
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 
 
 X: main/renderbuffer.c:2159: _mesa_reference_renderbuffer: Assertion 
 `oldRb-Magic == 0xaabbccdd' failed.
^^
Here we have the real problem. It is not about the nasty kdm warning
that it cannot open default.face.
I guess this is a problem in Mesa. I am reassigning this bug. Can you tell us
which version of libgl1-mesa-dri you have installed?

Greetings,
Armin

 
 X.Org X Server 1.6.4
 Release Date: 2009-9-27
 X Protocol Version 11, Revision 0
 Build Operating System: Linux 2.6.31 i686 Debian
 Current Operating System: Linux turbofinist 2.6.30-1-686 #1 SMP Sat Aug 15 
 19:11:58 UTC 2009 i686
 Build Date: 30 September 2009  08:45:15PM
 xorg-server 2:1.6.4-2 (bgog...@debian.org)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
 Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
 (==) Log file: /var/log/Xorg.0.log, Time: Wed Oct 14 22:46:40 2009
 (==) Using config file: /etc/X11/xorg.conf
 Fulfilled via DRI at 12587008
 Freed 12587008 (pool 2)
 SELinux: Disabled on system, not enabling in X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 The XKEYBOARD keymap compiler (xkbcomp) reports:
  Warning:  Type ONE_LEVEL has 1 levels, but RALT has 2 symbols
Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 
 turbofinist:~#
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 tail -f /var/log/Xorg.0.log
 (nothing)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 de...@turbofinist:~$ cat .xsession-errors
 Xsession: X session started for denis at mer ott 14 22:55:35 CEST 2009
 startkde: Starting up...
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
 kbuildsycoca4 running...
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
 kbuildsycoca4 running...
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_kcminit_startup.so
 kdeinit4: preparing to launch /usr/lib/libkdeinit4_ksmserver.so
 unknown program name(3908)/ KStartupInfo::createNewStartupId: 
 creating:  turbofinist;123737;234862;3908_TIME0 : unnamed app
 kephald starting up
 XRANDR error base:  162
 RRInput mask is set!!
 RandRScreen::loadSettings - adding mode:  117 1024 x 768
 RandRScreen::loadSettings - adding crtc:  115
 RandRScreen::loadSettings - adding output:  116
 Setting CRTC 115 on output default (previous 0 )
 CRTC outputs: (116)
 Output name: default
 Output refresh rate: 60
 Output rect: QRect(0,0 1024x768)
 Output rotation: 1
 XRandROutputs::init
   added output  116
 adding an output 0 with geom:  QRect(0,0 1024x768)
 output: SCREEN-0 QRect(0,0 1024x768) 0 true false
 load xml
 connected: 1
 looking for current SCREEN-0
 known * has score: 0.125
 screen: 0 QRect(0,0 1024x768)
 looking for a matching configuration...
 connected: 1
 looking for current SCREEN-0
 known * has score: 0.125
 found outputs, known: false
 activate external configuration!!
 registered the service: true
 screens registered on the bus: true
 outputs registered on the bus: true
 configurations registered on the bus: true
 

Bug#549165: grub-legacy: Same problem here with 0.97-59

[Armin Berres]

Package: grub-legacy
Version: 0.97-59

I have the same problem with 0.97-59. Even if I delete the menu.lst
update-grub fails and does not create a new one.
I do not have the time right now to look into the update-grub script,
but if you want any further information just tell me.

Greetings,
Armin

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages grub-legacy depends on:
ii  grub-common 1.97~beta4-1 GRand Unified Bootloader, version 

grub-legacy recommends no packages.

Versions of packages grub-legacy suggests:
pn  grub-legacy-doc   none (no description available)
pn  mdadm none (no description available)
pn  multiboot-doc none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#549165: grub-legacy: Same problem here with 0.97-59

[Armin Berres]

On Sun, 11 Oct 09 16:57, Felix Zielcke wrote:
 Probable some grub-probe call fails.
 If it's grub-probe please run it without the 2/dev/null part which
 supresses the error messages.
 And also check that your device.map has all needed devices listed.

Good guess. Here we go:

# grub-probe --device-map=/boot/grub/device.map -t device /
grub-probe: error: cannot find a device for /.

# cat /boot/grub/device.map
(hd0)   /dev/sda

Looks sane, doesn't it? I have /boot on a little ext3 partition and the
rest is on LVM.

# mount
/dev/dm-0 on / type ext3 (rw,errors=remount-ro)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/sda3 on /boot type ext3 (rw,noatime)
/dev/mapper/lvm-home on /home type ext4 (rw)
/dev/mapper/lvm-mail on /home/armin/mail type ext4 (rw,noatime)
/dev/sda1 on /windows type vfat (rw,utf8,gid=1000,uid=1000)
none on /proc/bus/usb type usbfs 
(rw,busgid=121,busmode=0775,devgid=121,devmode=0664)
fusectl on /sys/fs/fuse/connections type fusectl (rw)

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#549165: grub-legacy: Same problem here with 0.97-59

[Armin Berres]

On Sun, 11 Oct 09 17:17, Felix Zielcke wrote:
 Thanks, now I only need to know which line in update-grub causes this.

 As I said one line above the part you quoted from me:
 `sh -x update-grub'

# sh -x /usr/bin/update-grub
sh: Can't open /usr/bin/update-grub
bluefire:/home/armin# sh -x /usr/sbin/update-grub
+ set -e
+ uname -s
+ tr [A-Z] [a-z]
+ host_os=linux
+ find_grub_dir
+ echo -n Searching for GRUB installation directory ...
Searching for GRUB installation directory ... + [ -d /boot/grub ]
+ grub_dir=/boot/grub
+ break
+ [ -z /boot/grub ]
+ echo found: /boot/grub
found: /boot/grub
+ echo /boot/grub
+ grub_dir=/boot/grub
+ device_map=/boot/grub/device.map
+ menu_file_basename=menu.lst
+ menu_file=/boot/grub/menu.lst
+ default_file_basename=default
+ default_file=/boot/grub/default
+ find_device /
+ test -e /boot/grub/device.map
+ grub-probe --device-map=/boot/grub/device.map -t device /
+ root_device=

 *sigh*
 I'm now too lazy to search the bug reports we got for grub2 because of
 this, but the problem is a change in dmsetup which was reverted in the
 next upload. And so only affects sid users.
 Solution is to run `update-initramfs -c -t -k all' and if you don't want
 to reboot then also run `echo change  /sys/block/dm-0/uevent'

Wee, awesome. This fixed it. Thanks for your help.
FWIW I will switch to grub2 as soon as my thesis is finished :)

Greetings,
Armin





 
 
 -- 
 Felix Zielcke
 Proud Debian Maintainer and GNU GRUB developer
 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#550145:

[Armin Berres]

On Thu, 08 Oct 09 01:07, Erik wrote:
 Should I still report bugs concerning KDE to the Debian BTS and then connect 
 them to the KDE bug
 (so people know about this bug) or should I report those bugs to KDEs BTS 
 only?

In the end this is your decision. We do not mind, if you just open
upstream bugs upstream and not CC the Debian bts.

Thanks and greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#550145:

[Armin Berres]

On Thu, 08 Oct 09 01:07, Erik wrote:
 Should I still report bugs concerning KDE to the Debian BTS and then connect 
 them to the KDE bug
 (so people know about this bug) or should I report those bugs to KDEs BTS 
 only?

In the end this is your decision. We do not mind, if you just open
upstream bugs upstream and not CC the Debian bts.

Thanks and greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#548103: /etc/init.d/kdm: please add kbd to Should-Start

[Armin Berres]

On Wed, 23 Sep 09 21:36, Michael Schutte wrote:
 Please consider applying the attached patch.  It adds the “kbd” word to
 the requirements of your init script, so the list of reverse
 dependencies in /etc/init.d/kbd can be eventually removed again.

Just did this, because it does not hurt. But I wonder one thing: You
write it is a temporary solution. What is your long term plan? Do you
want to switch from kbd back to console-screen? This would be a bit,
uhm, weird.

Greetings,
Armin



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#548229: ksnapshot has no man page

[Armin Berres]

tags 548229 help
kthxbye

Hi Daniel!

On Thu, 24 Sep 09 14:04, Daniel Bolton wrote:
 Package: ksnapshot

 This is a binary without a manpage.

Thanks for your bugreport. Sadly KDE upstream does not ship manpages for
nearly all executables and the Debian KDE team has no time to write the
missing manpages.
If you would provide us a manpage we can add it to the package.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#548229: ksnapshot has no man page

[Armin Berres]

tags 548229 help
kthxbye

Hi Daniel!

On Thu, 24 Sep 09 14:04, Daniel Bolton wrote:
 Package: ksnapshot

 This is a binary without a manpage.

Thanks for your bugreport. Sadly KDE upstream does not ship manpages for
nearly all executables and the Debian KDE team has no time to write the
missing manpages.
If you would provide us a manpage we can add it to the package.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#547527: plasma desktop crashes and coredumps

[Armin Berres]

On Sun, 20 Sep 09 17:02, Justin Piszcz wrote:
 Hi,
 
 This occurred with Debian/Testing (Squeeze/x86) -- but ok.

Yeah, no doubt. It is just, that we (and we is the Debian KDE team here)
cannot do anything to solve the problem. A KDE programmer has to look at
the issue, and as they do not read bugs.debian.org it is better to
report it to bugs.kde.org directly. If we would have enough manpower we
would do this for you, but sadly we do not have it.

Thanks,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#547527: plasma desktop crashes and coredumps

[Armin Berres]

On Sun, 20 Sep 09 17:02, Justin Piszcz wrote:
 Hi,
 
 This occurred with Debian/Testing (Squeeze/x86) -- but ok.

Yeah, no doubt. It is just, that we (and we is the Debian KDE team here)
cannot do anything to solve the problem. A KDE programmer has to look at
the issue, and as they do not read bugs.debian.org it is better to
report it to bugs.kde.org directly. If we would have enough manpower we
would do this for you, but sadly we do not have it.

Thanks,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#547188: krandrtray does not come back automagically when we merge output

[Armin Berres]

tags 547188 upstream
kthxbye

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following the
instructions to report a new bug.

We appreciate that you reported the bug, but sadly the 
Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs. Therefore it is unlikely that your
bug will be solved if you do not directly report it to the KDE
developers (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one in the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 547188 KDE-BUG-URL
thanks
[ copy this ]

Greetings,
Armin Berres
Reply-To: Bastien ROUCARIES roucaries.bast...@gmail.com, 
547...@bugs.debian.org
Resent-From: Bastien ROUCARIES roucaries.bast...@gmail.com
Resent-To: debian-bugs-d...@lists.debian.org
Resent-CC: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
X-Loop: ow...@bugs.debian.org
Resent-Date: Thu, 17 Sep 2009 15:09:27 +
Resent-Message-ID: handler.547188.b.125319896717...@bugs.debian.org
X-Debian-PR-Message: report 547188
X-Debian-PR-Package: kdebase-workspace-bin
X-Debian-PR-Keywords: 
X-Debian-PR-Source: kdebase-workspace
Received: via spool by sub...@bugs.debian.org id=B.125319896717939
  (code B ref -1); Thu, 17 Sep 2009 15:09:27 +
Received: (at submit) by bugs.debian.org; 17 Sep 2009 14:49:27 +
Received: from fg-out-1718.google.com ([72.14.220.154])
by rietz.debian.org with esmtp (Exim 4.63)
(envelope-from roucaries.bast...@gmail.com)
id 1MoIIY-0004eB-V4
for sub...@bugs.debian.org; Thu, 17 Sep 2009 14:49:27 +
Received: by fg-out-1718.google.com with SMTP id d23so1429981fga.5
for sub...@bugs.debian.org; Thu, 17 Sep 2009 07:49:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:received:received:from:to:subject:date
 :user-agent:mime-version:content-type:content-transfer-encoding
 :message-id;
bh=mIXov/roiSUIqLG9Crvd+raUQU9EHMsTlNaxqiAxEiw=;
b=A14umq+gxNa3e+ctLYFgegWIrzh7ZZPxEGy+5dcVQ6IValcXzHTOEJTvbMWMUp/lAa
 p3XuTbp/7zbeRQcgzkHZ2K5z+381pM+KcOfKdJPNDfzS6JamhPaeaKlFBKlTcEP7/L55
 j0fTQiTraptpVZbCSASYZlqjNafLjyuhZHPS0=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=from:to:subject:date:user-agent:mime-version:content-type
 :content-transfer-encoding:message-id;
b=tUJJAuwLaPvHAWY6fz81FibcuNvu08g4QPEl22Prnry0OlnydkGhrsjyL66+wxgA8y
 YfS+Qaal5fldddb0i8aYZ3PqnzZtZD5YfrXJ7zKO+P5kk4TwIB54bxQoAv5h5JdJWPV+
 /LbKyQmMBW3K4UAXmqnLnwgbTJnjVREK3ck7o=
Received: by 10.86.17.27 with SMTP id 27mr660917fgq.31.1253198965266;
Thu, 17 Sep 2009 07:49:25 -0700 (PDT)
Received: from portablebastien.localnet ([147.127.17.49])
by mx.google.com with ESMTPS id 4sm168856fge.29.2009.09.17.07.49.24
(version=SSLv3 cipher=RC4-MD5);
Thu, 17 Sep 2009 07:49:24 -0700 (PDT)
From: Bastien ROUCARIES roucaries.bast...@gmail.com
To: sub...@bugs.debian.org
Date: Thu, 17 Sep 2009 16:49:14 +0200
User-Agent: KMail/1.12.1 (Linux/2.6.30-1-amd64; KDE/4.3.1; x86_64; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: 200909171649.15178.roucaries.bastien+...@gmail.com
Delivered-To: sub...@bugs.debian.org
Resent-Date: Thu, 17 Sep 2009 15:09:30 +
X-Rc-Spam: 2008-11-04_01
X-Rc-Virus: 2007-09-13_01
X-Rc-Spam: 2008-11-04_01
X-Mailing-List: debian-qt-...@lists.debian.org archive/latest/35137
X-Loop: debian-qt-...@lists.debian.org
List-Id: debian-qt-kde.lists.debian.org
List-Post: mailto:debian-qt-...@lists.debian.org
List-Help: mailto:debian-qt-kde-requ...@lists.debian.org?subject=help
List-Subscribe: 
mailto:debian-qt-kde-requ...@lists.debian.org?subject=subscribe
List-Unsubscribe: 
mailto:debian-qt-kde-requ...@lists.debian.org?subject=unsubscribe
Precedence: list
Resent-Sender: debian-qt-kde-requ...@lists.debian.org

Package: kdebase-workspace-bin
Version: 4:4.3.1-1
Severity: grave

Krandrtray offer to go to previous setting after 15s if we do not click on ok. 
Unfortunatly it apply immediatly the setting when merging the output leading 
on my video output on a black screen, crashing my Xsession (therefore grave)

Regards

Bastien


--- System information. ---
Architecture: amd64
Kernel:   Linux 2.6.30-1-amd64

Debian Release: squeeze/sid
  550 testing http.us.debian.org 
  500 unstablehttp.us.debian.org 

--- Package information. ---
Depends  (Version) | Installed

Bug#534229: kopete: Yahoo protocol still broken in Squeeze

[Armin Berres]

On Fri, 28 Aug 09 00:29, Sharuzzaman Ahmat Raslan wrote:
 I don't think I can just install kopete 4.3.x as it requires kdelibs5 to be
 updated to version 4.3 as well. I believe that will cause my whole KDE will
 to stop working, or not working correctly.

Updating kdelibs/pimlibs _should_ not kill any KDE 4.2 applications. It
is supposed to be backwards compatible. But if you do not want to risk
anything wait until the beast arrives in testing.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#534229: kopete: Yahoo protocol still broken in Squeeze

[Armin Berres]

On Fri, 28 Aug 09 00:29, Sharuzzaman Ahmat Raslan wrote:
 I don't think I can just install kopete 4.3.x as it requires kdelibs5 to be
 updated to version 4.3 as well. I believe that will cause my whole KDE will
 to stop working, or not working correctly.

Updating kdelibs/pimlibs _should_ not kill any KDE 4.2 applications. It
is supposed to be backwards compatible. But if you do not want to risk
anything wait until the beast arrives in testing.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#543485: eigen2: FTBFS due to missing hierarchy.html

[Armin Berres]

On Tue, 25 Aug 09 12:06, Cyril Brulebois wrote:
 Package: eigen2
 Version: 2.0.5-1
 Severity: serious
 Justification: FTBFS
 
 Hi,
 
 your package FTBFS due to missing hierarchy.html, e.g. on hppa[1]:
 | cd /build/buildd/eigen2-2.0.5/obj-hppa-linux-gnu/doc  
 /build/buildd/eigen2-2.0.5/doc/cleanhierarchy.sh 
 /build/buildd/eigen2-2.0.5/obj-hppa-linux-gnu/doc/html/hierarchy.html
 | sed: can't read 
 /build/buildd/eigen2-2.0.5/obj-hppa-linux-gnu/doc/html/hierarchy.html: No 
 such file or directory
 | sed: can't read 
 /build/buildd/eigen2-2.0.5/obj-hppa-linux-gnu/doc/html/hierarchy.html: No 
 such file or directory
 | sed: can't read 
 /build/buildd/eigen2-2.0.5/obj-hppa-linux-gnu/doc/html/hierarchy.html: No 
 such file or directory
 | make[4]: *** [doc/CMakeFiles/doc] Error 2
 
  1. https://buildd.debian.org/status/package.php?suite=unstablep=eigen2
 
 I've reproduced it on kfreebsd-i386 and once that point reached, there
 was no hierarchy.html to be seen.

Caused by doxygen 1.6: http://bugzilla.gnome.org/show_bug.cgi?id=592975

Thanks for reporting
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Accepted eigen2 2.0.5-1 (source amd64)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 23 Aug 2009 12:53:08 +0200
Source: eigen2
Binary: libeigen2-dev libeigen2-doc
Architecture: source amd64
Version: 2.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 libeigen2-dev - lightweight C++ template library for linear algebra
 libeigen2-doc - eigen2 API docmentation
Changes: 
 eigen2 (2.0.5-1) unstable; urgency=low
 .
   * New upstream release.
   * Add libeigen2-doc.
   * Upgrade standards version to 3.8.3. No changes needed.
   * Update copyrights file.
Checksums-Sha1: 
 e1c1e574909e12ac2718ae7f92f0308bd4b209ec 1229 eigen2_2.0.5-1.dsc
 3eb3848e08ae14d788cbcac40f25d23637efea9f 429413 eigen2_2.0.5.orig.tar.gz
 07ad8fe520b37db8b5b0982d0d930e6c62a93172 2862 eigen2_2.0.5-1.diff.gz
 f4c8fb014bd5cf6b474ffbf76586e0956507ad97 3320 libeigen2-dev_2.0.5-1_amd64.deb
 5f5addcfa617af07e8fc1ee199a69a26175f1de2 498104 libeigen2-doc_2.0.5-1_amd64.deb
Checksums-Sha256: 
 3802c9b527bd95c83c9bc89ac092e52be7de500c22361a73e4fa4621c2862661 1229 
eigen2_2.0.5-1.dsc
 fdead636ea16fb5deb0a84e45462951182a3c5921a08abca313e2cde97db399d 429413 
eigen2_2.0.5.orig.tar.gz
 01e3943d923472f412dd6b0d202eb5d9b119262e6797e9987918619a94e6fe0f 2862 
eigen2_2.0.5-1.diff.gz
 572829be711f578e6cd8246f30b4e00be35d394e618a5ab5f4ea5bdd12dd8dc2 3320 
libeigen2-dev_2.0.5-1_amd64.deb
 a02bebe6eb6ead80f1d491cbaf3c9ee024d231271d7645f46a9c1ce40b182c47 498104 
libeigen2-doc_2.0.5-1_amd64.deb
Files: 
 0a89e10c6af82f2078d7cd2952488096 1229 libdevel extra eigen2_2.0.5-1.dsc
 511f131183001b7a05caf837e19a33b2 429413 libdevel extra eigen2_2.0.5.orig.tar.gz
 63f2c694bbe8fdb950566db9bcc0e5ed 2862 libdevel extra eigen2_2.0.5-1.diff.gz
 ea7960d8163f36995bae4e4094ecfa80 3320 libdevel extra 
libeigen2-dev_2.0.5-1_amd64.deb
 08617b8ba0af615bcae6ccb2b15c271b 498104 doc extra 
libeigen2-doc_2.0.5-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Signed by Ana Guerrero

iEYEARECAAYFAkqRWwkACgkQn3j4POjENGGx+QCffu+9ZfrKr7KCTnbJL4Sw/3Mu
85wAnAhJjipLON27belgjzuQonQLTjW7
=MAk5
-END PGP SIGNATURE-


Accepted:
eigen2_2.0.5-1.diff.gz
  to pool/main/e/eigen2/eigen2_2.0.5-1.diff.gz
eigen2_2.0.5-1.dsc
  to pool/main/e/eigen2/eigen2_2.0.5-1.dsc
eigen2_2.0.5.orig.tar.gz
  to pool/main/e/eigen2/eigen2_2.0.5.orig.tar.gz
libeigen2-dev_2.0.5-1_amd64.deb
  to pool/main/e/eigen2/libeigen2-dev_2.0.5-1_amd64.deb
libeigen2-doc_2.0.5-1_amd64.deb
  to pool/main/e/eigen2/libeigen2-doc_2.0.5-1_amd64.deb


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: OpenOffice.org plans for the squeeze cycle

[Armin Berres]

On Thu, 20 Aug 09 19:26, Matthias Klose wrote:
 On 16.08.2009 15:15, Rene Engelhard wrote:
 .0s should be avoided for Debian stable, the are almost always full of
 bad bugs/regressions, as we see e.g. in 3.1.0, too.
 
 So this would mean, that squeeze will release with 3.1.x (3.1.0
 release in Apr 2009), which will be several months old when squeeze
 releases. Would it be possible to package 3.2.0 for unstable, and

I thought the squeeze freeze/release date is not fixed yet and these
mails should be the base for the final date...

/Armin


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#542266: facing pages view mode is wrong

[Armin Berres]

On Tue, 18 Aug 09 20:28, martin f krafft wrote:
 The Facing pages view mode is nice but wrongly implemented: page
 1 is not on the left of page 2, but rather page 1 is on the right
 all alone, and page 2 is on the left of page 3; odd pages are always
 on the right hand side.

Try SettingsConfigure Okular... and select Center first page in the
View Options section. This is what you are looking for, right?

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#542266: facing pages view mode is wrong

[Armin Berres]

On Tue, 18 Aug 09 20:28, martin f krafft wrote:
 The Facing pages view mode is nice but wrongly implemented: page
 1 is not on the left of page 2, but rather page 1 is on the right
 all alone, and page 2 is on the left of page 3; odd pages are always
 on the right hand side.

Try SettingsConfigure Okular... and select Center first page in the
View Options section. This is what you are looking for, right?

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Accepted meta-kde 5:51 (source all)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 04 Aug 2009 16:20:03 +0200
Source: meta-kde
Binary: kde-full kde-minimal kde-standard
Architecture: source all
Version: 5:51
Distribution: unstable
Urgency: low
Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 kde-full   - the K Desktop Environment official modules
 kde-minimal - the K Desktop Environment, minimal applications
 kde-standard - the K Desktop Environment, standard desktop applications
Changes: 
 meta-kde (5:51) unstable; urgency=low
 .
   * Update depencies to reflect the 4.3.0 upload.
Checksums-Sha1: 
 5511f65a5b3ecda7ae235b3a3636d8a8a2b96006 1074 meta-kde_51.dsc
 54a9634e32ccd3158ffec1ad8fb4436b75af118e 7447 meta-kde_51.tar.gz
 ff294f99ba91d469191e593ccf1314aad02f8f50 7744 kde-full_51_all.deb
 00221998fdc706b38757b4b8cf5b17fbc2fdf840 7628 kde-minimal_51_all.deb
 059a6e0a945fb3cde86566cd93fe7de4d20170a8 7558 kde-standard_51_all.deb
Checksums-Sha256: 
 2055624ececc7b5635acc224a99579e019b7f3e1b0a53ebd41547a68f95fa944 1074 
meta-kde_51.dsc
 b1ea8d646ea5a1a135b06e8b802a61a9ff674d9ed6cc530513c2b3bf4d02f3ac 7447 
meta-kde_51.tar.gz
 c5973ea05d70eac357471894c00ece62828227c92645ff30b9a807440f2900a4 7744 
kde-full_51_all.deb
 759e65962f8d1ffe2528196f4494dbe1464d43182bb610a385caf1af8aa37968 7628 
kde-minimal_51_all.deb
 99136d1d0eb570207b36b811fdbf85b2699bad12f4a4f5a832ac30df748358b5 7558 
kde-standard_51_all.deb
Files: 
 9c8464c45282ccea9b589276a812dbea 1074 kde optional meta-kde_51.dsc
 a73c2eb3d6e461a52c15590f41a714e0 7447 kde optional meta-kde_51.tar.gz
 3d3e795b96bdb0661dd4a7cb4c829ab4 7744 kde optional kde-full_51_all.deb
 8ad120df2d24074dd93b660951501d9d 7628 kde optional kde-minimal_51_all.deb
 bc91451d30841f66b43ce18c4ed99d27 7558 kde optional kde-standard_51_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Signed by Ana Guerrero

iEYEARECAAYFAkp+6RQACgkQn3j4POjENGFJsQCeMrlXCWfe+wK+3RbPKGN6s7H2
XC4An0SSb/jJ1T1FPQZd0jf1ufyVewas
=2c8C
-END PGP SIGNATURE-


Accepted:
kde-full_51_all.deb
  to pool/main/m/meta-kde/kde-full_51_all.deb
kde-minimal_51_all.deb
  to pool/main/m/meta-kde/kde-minimal_51_all.deb
kde-standard_51_all.deb
  to pool/main/m/meta-kde/kde-standard_51_all.deb
meta-kde_51.dsc
  to pool/main/m/meta-kde/meta-kde_51.dsc
meta-kde_51.tar.gz
  to pool/main/m/meta-kde/meta-kde_51.tar.gz


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Accepted eigen2 2.0.4-1 (source amd64)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Aug 2009 01:41:58 +0200
Source: eigen2
Binary: libeigen2-dev
Architecture: source amd64
Version: 2.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 libeigen2-dev - lightweight C++ template library for linear algebra
Closes: 537408
Changes: 
 eigen2 (2.0.4-1) unstable; urgency=low
 .
   * New upstream release.
   * Skip building the testcase if DEB_BUILD_OPTIONS=nocheck is set
 (Closes: #537408).
Checksums-Sha1: 
 a35698f2ebd86a4a10fd71c4bbc3ebd278564e17 970 eigen2_2.0.4-1.dsc
 664611aa75be064af9ef9344e5daa9eecc33d9c7 439929 eigen2_2.0.4-1.tar.gz
 85d46dd537ff0498e411f21abf8b511a1db38358 204398 libeigen2-dev_2.0.4-1_amd64.deb
Checksums-Sha256: 
 3ced8ba7cf3b92f537fe436df0a8e41d159ac7f7feb2df038d332b23afac0c48 970 
eigen2_2.0.4-1.dsc
 cba8cd4dca34354d233adbe00e69132b47feaf7978069157002826c3331ff0ec 439929 
eigen2_2.0.4-1.tar.gz
 90c7b5ebdaa78454c83e02ad9581c2a40134c98fb1e7505e08af8a42bdfef10d 204398 
libeigen2-dev_2.0.4-1_amd64.deb
Files: 
 69b3bd816c5535957843631653eb5c98 970 libdevel extra eigen2_2.0.4-1.dsc
 033f0f03fcd59ffc4944fd65d684e834 439929 libdevel extra eigen2_2.0.4-1.tar.gz
 db7ea1f5d0612d3864b864a215a15419 204398 libdevel extra 
libeigen2-dev_2.0.4-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Signed by Ana Guerrero

iEYEARECAAYFAkp5goYACgkQn3j4POjENGFaTgCeMRRPeUFgr5J4hI/npu0IWZqb
u1EAn1V7mll+RiREL+n2qWznzez0v04A
=2Yos
-END PGP SIGNATURE-


Accepted:
eigen2_2.0.4-1.dsc
  to pool/main/e/eigen2/eigen2_2.0.4-1.dsc
eigen2_2.0.4-1.tar.gz
  to pool/main/e/eigen2/eigen2_2.0.4-1.tar.gz
libeigen2-dev_2.0.4-1_amd64.deb
  to pool/main/e/eigen2/libeigen2-dev_2.0.4-1_amd64.deb


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Accepted kdesdk 4:4.3.0-2 (source all i386)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 05 Aug 2009 13:48:22 +0200
Source: kdesdk
Binary: kdesdk cervisia kapptemplate kate kbugbuster kcachegrind 
kcachegrind-converters kdesdk-dev kdesdk-kio-plugins kdesdk-misc kdesdk-scripts 
kdesdk-strigi-plugins kmtrace kompare kuiviewer cvsservice poxml umbrello 
lokalize kpartloader kdesdk-dbg
Architecture: source all i386
Version: 4:4.3.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 cervisia   - CVS client for KDE 4
 cvsservice - D-Bus service for accessing CVS repositories
 kapptemplate - KDE 4 application template generator
 kate   - KDE 4 Advanced Text Editor
 kbugbuster - Bugzilla client for KDE 4
 kcachegrind - visualisation tool for the Valgrind profiler
 kcachegrind-converters - format converters for KCachegrind profiler 
visualisation tool
 kdesdk - Software Development Kit from the official KDE 4 release
 kdesdk-dbg - debugging symbols for the KDE 4 Software Development Kit module
 kdesdk-dev - development files for the KDE 4 Software Development Kit module
 kdesdk-kio-plugins - transparent Subversion access for KDE 4 applications
 kdesdk-misc - miscellaneous tools from the KDE 4 Software Development Kit
 kdesdk-scripts - scripts and data files for KDE 4 development
 kdesdk-strigi-plugins - software development file format plugins for Strigi 
Desktop Searc
 kmtrace- memory leak tracer for KDE 4
 kompare- file difference viewer for KDE 4
 kpartloader - test tool for KParts
 kuiviewer  - viewer for Qt Designer user interface files
 lokalize   - computer-aided translation system for KDE 4
 poxml  - tools for translating DocBook XML files with gettext
 umbrello   - UML modelling tool and code generator
Changes: 
 kdesdk (4:4.3.0-2) unstable; urgency=low
 .
   * Add conflicts and replaces with libcvsservice0 to cvsservice.
Checksums-Sha1: 
 429f04edd4257d7d55db3c1395c7bca6f1704e39 1776 kdesdk_4.3.0-2.dsc
 488f908d3bf3581d99f3883cfa6b94fa1be93ad1 19554 kdesdk_4.3.0-2.diff.gz
 93e130970300ff060bb0bb17420bf9e4572e6eb6 11624 kdesdk_4.3.0-2_all.deb
 414d5fad24b083666a743accdf3868091f26b13f 21140 
kcachegrind-converters_4.3.0-2_all.deb
 11345a00fd49fc5db27049b44ea5d49a716ca625 215386 kdesdk-scripts_4.3.0-2_all.deb
 5f7aaa62a993a9a71be5ea57edaaba58fa764133 671664 cervisia_4.3.0-2_i386.deb
 d07ab98cee49619f73020d0672d406efb958498c 799898 kapptemplate_4.3.0-2_i386.deb
 032eef66e019c7b40b1dc7627ac3ca6a439a2af3 1115714 kate_4.3.0-2_i386.deb
 b4bc2e5c8d1333004bd81f9771c94497d39a30b4 384092 kbugbuster_4.3.0-2_i386.deb
 13fed423bb31764055ea862b75ecbefbf5816c72 368094 kcachegrind_4.3.0-2_i386.deb
 d4545579a6322c4409c95e55b96604e16489d9ca 22350 kdesdk-dev_4.3.0-2_i386.deb
 8c1fa5530f939bc7ec4f239d3eda378d117357bd 429232 
kdesdk-kio-plugins_4.3.0-2_i386.deb
 e847ac9e15488d83b3343ee49205911a598c4fc8 17730 kdesdk-misc_4.3.0-2_i386.deb
 8d3ca7e93db78c7ad50da319d7f8ac1d344d6d9a 24850 
kdesdk-strigi-plugins_4.3.0-2_i386.deb
 af50cab3557722d6becba6a9abb865f97f441c2e 95674 kmtrace_4.3.0-2_i386.deb
 870d3a75689927960e09ec9d2eaecbcbbea72cca 393882 kompare_4.3.0-2_i386.deb
 12da386f6b0d843ac18a7f3c3035e13bcf35745e 47010 kuiviewer_4.3.0-2_i386.deb
 6cf554137b8ec2f58b5c52f7448e41edd7a6734c 55766 cvsservice_4.3.0-2_i386.deb
 bee6b52d77c7d707e199d44f8e42e37a0380ca41 264180 poxml_4.3.0-2_i386.deb
 49a2d0ae74f94282e12eee73f9a50d0d0d7615a0 2767634 umbrello_4.3.0-2_i386.deb
 1f29d45363fd8267de24a22b4f00af1ab4af842d 678662 lokalize_4.3.0-2_i386.deb
 deb43f9977402157459719d284a89567386ad68e 22332 kpartloader_4.3.0-2_i386.deb
 0b24d0944793264fe691c5efd7a7e2e55f6e2c57 44360400 kdesdk-dbg_4.3.0-2_i386.deb
Checksums-Sha256: 
 7acf9960e764e8c22c007bfc94ef3b312a41c337e7be8cdfcb2ef6544b50a232 1776 
kdesdk_4.3.0-2.dsc
 5427852fb8605a7db4100287c4bcde9bfef7e7bb626b2f97dd802df39cf80331 19554 
kdesdk_4.3.0-2.diff.gz
 f61981ee393232a31284afb410ebd87ce51a38656493d2a6b08389953dc52ffc 11624 
kdesdk_4.3.0-2_all.deb
 b338772f877d46fe35316367c2ab39aa0c65ea10cae4f7f8ab5a3d77ec8b5533 21140 
kcachegrind-converters_4.3.0-2_all.deb
 8ca64413dbc3b8e822a65932f2a36186dfb27e83fd121c3dda93b40846d8dcad 215386 
kdesdk-scripts_4.3.0-2_all.deb
 d9650a02b23fe857c40a94a9a2cb875df194f6e7e11cb6ee315d8bd87dee3300 671664 
cervisia_4.3.0-2_i386.deb
 6f84bb6ccff7981a86126e7e7bd4ae804084c16911019f74b8a87c9835f110b0 799898 
kapptemplate_4.3.0-2_i386.deb
 eeb66b1a5e601d213c433b1e13d1db77203bc6c1f3d3802ce8d7639b463efca5 1115714 
kate_4.3.0-2_i386.deb
 610e2c8f310a922e15196038b4081e2c367cc6c144120945fbddd8f2ff549fe3 384092 
kbugbuster_4.3.0-2_i386.deb
 d0625a044704cf5329ea7df483070a410cac44966e3539f49298b5dabfe68f77 368094 
kcachegrind_4.3.0-2_i386.deb
 2885d3776fc3dd530a89703aa0fbe877a09d0213daa945b86e35efcc57047360 22350 
kdesdk-dev_4.3.0-2_i386.deb
 973e9c68b6a728ef9e5225ce2bcf8b6976a17ffd8c24b989409ec4131a096e28 429232 
kdesdk-kio-plugins_4.3.0-2_i386.deb

Bug#539992: initscripts: /etc/init.d/rc.local has wrong dependency information

[Armin Berres]

Package: initscripts
Version: 2.87dsf-2
Severity: normal

If we look at the dependency information of /etc/init.d/rc.local we see
# Required-Start:$remote_fs $syslog
but in /etc/rc.local we read 
# This script is executed at the end of each multiuser runlevel.

Without dependecy based booting /etc/rc.local also has been started at
S99.

The dependency information should be updated to start
/etc/init.d/rc.local at the very end of the boot process.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii  debianutils 3.2  Miscellaneous utilities specific t
ii  libc6   2.9-12   GNU C Library: Shared libraries
ii  lsb-base3.2-23   Linux Standard Base 3.2 init scrip
ii  mount   2.15.1~rc1-1 Tools for mounting and manipulatin
ii  sysvinit-utils  2.87dsf-2System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs 1.41.8-2   ext2/ext3/ext4 file system utiliti
ii  psmisc22.8-1 utilities that use the proc file s

initscripts suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

[Pkg-sysvinit-devel] Bug#539992: initscripts: /etc/init.d/rc.local has wrong dependency information

[Armin Berres]

Package: initscripts
Version: 2.87dsf-2
Severity: normal

If we look at the dependency information of /etc/init.d/rc.local we see
# Required-Start:$remote_fs $syslog
but in /etc/rc.local we read 
# This script is executed at the end of each multiuser runlevel.

Without dependecy based booting /etc/rc.local also has been started at
S99.

The dependency information should be updated to start
/etc/init.d/rc.local at the very end of the boot process.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages initscripts depends on:
ii  debianutils 3.2  Miscellaneous utilities specific t
ii  libc6   2.9-12   GNU C Library: Shared libraries
ii  lsb-base3.2-23   Linux Standard Base 3.2 init scrip
ii  mount   2.15.1~rc1-1 Tools for mounting and manipulatin
ii  sysvinit-utils  2.87dsf-2System-V-like utilities

Versions of packages initscripts recommends:
ii  e2fsprogs 1.41.8-2   ext2/ext3/ext4 file system utiliti
ii  psmisc22.8-1 utilities that use the proc file s

initscripts suggests no packages.

-- no debconf information



___
Pkg-sysvinit-devel mailing list
Pkg-sysvinit-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel

Bug#539488: [dolphin] Moreinformation

[Armin Berres]

Hi Bastien,

thanks for all your bugreports and especially for forwarding them
upstream. I just wanted to let you know, that there is no need to also
file the bugreports in the Debian BTS if you have found it/will open it
upstream anyway.
Alaso additional information is better mentioned in the upstream report.

Not really much KDE developers read the Debian BTS and we as Debian
developers do not have the time to bring the new information to the
attention of upstream.

Packaging bugs are for sure very very welcome here :)

Greetings and thanks,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#539488: [dolphin] Moreinformation

[Armin Berres]

Hi Bastien,

thanks for all your bugreports and especially for forwarding them
upstream. I just wanted to let you know, that there is no need to also
file the bugreports in the Debian BTS if you have found it/will open it
upstream anyway.
Alaso additional information is better mentioned in the upstream report.

Not really much KDE developers read the Debian BTS and we as Debian
developers do not have the time to bring the new information to the
attention of upstream.

Packaging bugs are for sure very very welcome here :)

Greetings and thanks,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#539129: offlineimap: imap idle does not handle connection problems gracefully

[Armin Berres]

Package: offlineimap
Version: 6.1.2
Severity: normal

First: Thanks for the imap idle support :-)

I am using offlineimap on my notebook and after suspends to ram,
offlineimap prints backtraces like this:

Sleeping for 60:00
Exception in thread Thread-47:
Traceback (most recent call last):
  File /usr/lib/python2.5/threading.py, line 486, in __bootstrap_inner
self.run()
  File /usr/lib/python2.5/threading.py, line 446, in run
self.__target(*self.__args, **self.__kwargs)
  File /usr/lib/pymodules/python2.5/offlineimap/imapserver.py, line 443, in 
idle
imapobj.noop()
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 790, in noop
return self._simple_command('NOOP', **kw)
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 1352, in 
_simple_command
return self._command_complete(self._command(name, *args), kw)
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 1076, in 
_command
raise self.abort('connection closed')
abort: connection closed

Exception in thread Thread-46:
Traceback (most recent call last):
  File /usr/lib/python2.5/threading.py, line 486, in __bootstrap_inner
self.run()
  File /usr/lib/python2.5/threading.py, line 446, in run
self.__target(*self.__args, **self.__kwargs)
  File /usr/lib/pymodules/python2.5/offlineimap/imapserver.py, line 443, in 
idle
imapobj.noop()
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 790, in noop
return self._simple_command('NOOP', **kw)
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 1352, in 
_simple_command
return self._command_complete(self._command(name, *args), kw)
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 1144, in 
_command_complete
typ, dat = rqb.get_response('command: %s = %%s' % rqb.name)
  File /usr/lib/pymodules/python2.5/offlineimap/imaplib2.py, line 151, in 
get_response
raise typ(exc_fmt % str(val))
abort: command: NOOP = socket error: class 'socket.error' - (104, 
'Connection reset by peer')

Afterwards it dies nothing anymore. If I send SIGUSR1 to offlineimap it prints
Copying folder structure from IMAP to Maildir, but does nothing else.

I think offlineimap is quite often used on Notebooks and should be able to deal 
with non-constant
connections.

Greetings,
Armin

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'testing'), (500, 'stable'), (101, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages offlineimap depends on:
ii  python2.5.4-2An interactive high-level object-o
ii  python-support1.0.3  automated rebuilding support for P

offlineimap recommends no packages.

Versions of packages offlineimap suggests:
pn  python-kerberos   none (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Debian decides to adopt time-based release freezes

[Armin Berres]

On Wed, 29 Jul 09 11:40, Luk Claes wrote:
 Sune Vuorela wrote:
 I guess you are talking about freezing this December and not in general?
 
 Lets discuss the issues regarding KDE and see if we can come to a solution.

Good. So let me propose something.

 Are you confident that KDE will be better at releasing in time and
 with a higher quality than they are used to? Otherwise it looks to
 me like we would need many more months before we can freeze KDE.

Yes, we are quite sure, that KDE will release in time. KDE 4.3 released
slipped a week, but all the RCs have already been very stable.

You want to try something with the next release? So let me propose the
following: We ship the exactly same Upstream KDE as Ubuntu -- talking
about version numbers here. This really allows us to use the momentum 
between Debian and Ubuntu on the Desktop front. Everything else is just
useless.
In the end this means: In January we put 4.4 (or maybe even the RCs, as
they are normally stable) into unstable, and later we also put the 4.4.1
and 4.4.2 (maybe also 4.4.3) into unstable. I am very sure we will not
not introduce RC bugs which will not be fixed within very less days, but
we will fix a lot of minor bugs with the uploads. Your job is just to
unblock the fun then :)
In the freeze times, the changes happening to the KDE packages are very
marginal. We do win nothing by freezing that long (and yes, I do not
believe the freeze is over after 3 months).

So, do you think we can manage to ship Squeeze with the best KDE ever,
to make Squeeze the best Debian ever, and at the same time align with
Ubuntu which will release before us?

Greetings,
Armin
member of the Debian Qt KDE team


-- 
To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#535324: kaddressbook: I want an addressbook client, not a mysql server

[Armin Berres]

On Mon, 13 Jul 09 13:30, Kevin Krammer wrote:
 On Monday, 2009-07-13, Simone Piccardi wrote:
  So I cannot understand why the dependency on the akonadi plugin is
  forced on all of us. It should be possible to put this in a separate
  package, avoiding it if the  user dos'nt need that.
 
 Not sure what the rational was given that it is a plugin not enabled by 
 default, but you could try asking for a change from depends to recommends.

Are we talking on the dependency of kaddressbook on akonadi-server right
now? Or is there a plugin I do not see right now?

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#535324: kaddressbook: I want an addressbook client, not a mysql server

[Armin Berres]

On Mon, 13 Jul 09 13:30, Kevin Krammer wrote:
 On Monday, 2009-07-13, Simone Piccardi wrote:
  So I cannot understand why the dependency on the akonadi plugin is
  forced on all of us. It should be possible to put this in a separate
  package, avoiding it if the  user dos'nt need that.
 
 Not sure what the rational was given that it is a plugin not enabled by 
 default, but you could try asking for a change from depends to recommends.

Are we talking on the dependency of kaddressbook on akonadi-server right
now? Or is there a plugin I do not see right now?

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Accepted oxygen-icons 4:4.2.95-1 (source all)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 17 May 2009 21:03:20 -0400
Source: oxygen-icons
Binary: oxygen-icon-theme kde-icons-oxygen
Architecture: source all
Version: 4:4.2.95-1
Distribution: experimental
Urgency: low
Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 kde-icons-oxygen - transitional package for oxygen icon theme
 oxygen-icon-theme - Oxygen icon theme
Changes: 
 oxygen-icons (4:4.2.95-1) experimental; urgency=low
 .
   * Initial release as standalone package. The icons have formerly been a part
 of kdebase-runtime.
   * Provide transitional package
Checksums-Sha1: 
 b6fe8b5a224f8f56ed9b6e17037db3cc4d363a1e 1435 oxygen-icons_4.2.95-1.dsc
 ef541600e0de732dbcddae14051e71f735033bd7 97234307 
oxygen-icons_4.2.95.orig.tar.gz
 3c34eb964582d55956ac1b3bffae7162983e193d 2170 oxygen-icons_4.2.95-1.diff.gz
 7c86a5c76bf2631d445db50c5ca2728d6084c170 20216326 
oxygen-icon-theme_4.2.95-1_all.deb
 224ec4ec6d9f6b1af5db0c26a59e52722460a69f 2870 kde-icons-oxygen_4.2.95-1_all.deb
Checksums-Sha256: 
 644879dfca89e44cdda736d06136275ba2933a5a278f7902f70b5c4b2cc9a338 1435 
oxygen-icons_4.2.95-1.dsc
 731bfe2897ede5f351a991200739c0f848d95824cdc0fc9a1ffb76d74167224e 97234307 
oxygen-icons_4.2.95.orig.tar.gz
 e6c4b3807f8452cfdfed4a5093ed69252d0338ff0890872f3ede90b03594ea8a 2170 
oxygen-icons_4.2.95-1.diff.gz
 6ad19dbb6596bd7ce6abf36daf6d623865d2f5336c8dc63778f2fa6cc16d7369 20216326 
oxygen-icon-theme_4.2.95-1_all.deb
 cd45f54fb5d651de7943bd8095b7db828597b96ca67969f2e494e3acd4876ce1 2870 
kde-icons-oxygen_4.2.95-1_all.deb
Files: 
 afbf769d17e036dac88b8df67fc648db 1435 x11 optional oxygen-icons_4.2.95-1.dsc
 05e159507e27786afa00c545b17f1bbd 97234307 x11 optional 
oxygen-icons_4.2.95.orig.tar.gz
 b8046cdf59b34c7e662caac733bd6834 2170 x11 optional 
oxygen-icons_4.2.95-1.diff.gz
 36a3ebc1883db75215b5075370517414 20216326 x11 optional 
oxygen-icon-theme_4.2.95-1_all.deb
 a8c62b766087b592770d1694dab0f708 2870 kde optional 
kde-icons-oxygen_4.2.95-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkpMks8ACgkQnMvaFgH6i0qmGQCeJxd5HfzuTR/MCSwz4oYWKEwk
g8gAn31F5X6yI2kfzShcQ7Bq5mA55Lmr
=YusC
-END PGP SIGNATURE-


Accepted:
kde-icons-oxygen_4.2.95-1_all.deb
  to pool/main/o/oxygen-icons/kde-icons-oxygen_4.2.95-1_all.deb
oxygen-icon-theme_4.2.95-1_all.deb
  to pool/main/o/oxygen-icons/oxygen-icon-theme_4.2.95-1_all.deb
oxygen-icons_4.2.95-1.diff.gz
  to pool/main/o/oxygen-icons/oxygen-icons_4.2.95-1.diff.gz
oxygen-icons_4.2.95-1.dsc
  to pool/main/o/oxygen-icons/oxygen-icons_4.2.95-1.dsc
oxygen-icons_4.2.95.orig.tar.gz
  to pool/main/o/oxygen-icons/oxygen-icons_4.2.95.orig.tar.gz


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Accepted eigen2 2.0.3-1 (source amd64)

[Armin Berres]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 21 Jun 2009 16:37:49 -0400
Source: eigen2
Binary: libeigen2-dev
Architecture: source amd64
Version: 2.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org
Changed-By: Armin Berres armin+deb...@space-based.de
Description: 
 libeigen2-dev - lightweight C++ template library for linear algebra
Changes: 
 eigen2 (2.0.3-1) unstable; urgency=low
 .
   * New upstream release
Checksums-Sha1: 
 ad9500a31b0ef04cbf89705e469fe95cc5933fa2 1175 eigen2_2.0.3-1.dsc
 95a60fc9ca87bf82112bc48ba8b678c774dd451c 427999 eigen2_2.0.3.orig.tar.gz
 75ed424a88a639f8997e823ca16f9d344aae4650 2372 eigen2_2.0.3-1.diff.gz
 bd828bda2ae1fb618db2700c675a0bf384f207b7 203426 libeigen2-dev_2.0.3-1_amd64.deb
Checksums-Sha256: 
 63d707fa7f02929ee412751af31e2add32ed1d5e1993278ef5a854a000deb22c 1175 
eigen2_2.0.3-1.dsc
 565fbf621fc1caa69e1a248928eb89a6418a82d163cab05fbb6115f22056bcc8 427999 
eigen2_2.0.3.orig.tar.gz
 6f1ee4d71afd4215a77eddaed78e8edf23d5e8e17a633695fb35299dd274957b 2372 
eigen2_2.0.3-1.diff.gz
 fe8573afc3e32a98190356eb5a6f0b125d15821ff9ff7aabc9f96828d53c6a10 203426 
libeigen2-dev_2.0.3-1_amd64.deb
Files: 
 de32315d01720dd707a5b7b04ce43115 1175 libdevel extra eigen2_2.0.3-1.dsc
 b6b4519256427b98d3c5223ec479e6a4 427999 libdevel extra eigen2_2.0.3.orig.tar.gz
 4806e9c7192c9e9aa2f570573b8845d4 2372 libdevel extra eigen2_2.0.3-1.diff.gz
 20e280125e348fdbde51615c183cb30a 203426 libdevel extra 
libeigen2-dev_2.0.3-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkpBI1wACgkQnMvaFgH6i0qStACdFoAmLmnLg6gmIt/cDY6fD6Ex
Np4AnA4yxJFYOKJa5LABk6mIzpe08fPR
=oy5C
-END PGP SIGNATURE-


Accepted:
eigen2_2.0.3-1.diff.gz
  to pool/main/e/eigen2/eigen2_2.0.3-1.diff.gz
eigen2_2.0.3-1.dsc
  to pool/main/e/eigen2/eigen2_2.0.3-1.dsc
eigen2_2.0.3.orig.tar.gz
  to pool/main/e/eigen2/eigen2_2.0.3.orig.tar.gz
libeigen2-dev_2.0.3-1_amd64.deb
  to pool/main/e/eigen2/libeigen2-dev_2.0.3-1_amd64.deb


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#533712: powerdevil: Powerdevil doesn't lock screen before/after suspend.

[Armin Berres]

On Sat, 20 Jun 09 02:04, Hakan BAYINDIR wrote:
 Package: kdebase-workspace-bin
 Version: 4:4.2.2-2
 Severity: important
 File: powerdevil
 
 Powerdevil, has an option called lock screen on resume but, after suspend to 
 disk or suspend to RAM, screen is not locked upon resume causing security 
 issues on computers that are not powered off but suspended.

Does not solve your problem, but it works for me. So something about
your system must be special.
Dies locking the screen via the menu work?

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#533712: powerdevil: Powerdevil doesn't lock screen before/after suspend.

[Armin Berres]

On Sat, 20 Jun 09 02:04, Hakan BAYINDIR wrote:
 Package: kdebase-workspace-bin
 Version: 4:4.2.2-2
 Severity: important
 File: powerdevil
 
 Powerdevil, has an option called lock screen on resume but, after suspend to 
 disk or suspend to RAM, screen is not locked upon resume causing security 
 issues on computers that are not powered off but suspended.

Does not solve your problem, but it works for me. So something about
your system must be special.
Dies locking the screen via the menu work?

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Adding presubj files for all KDE packages

[Armin Berres]

On Tue, 26 May 09 10:00, Modestas Vainius wrote:
 Hello,
 
 On 2009 m. May 26 d., Tuesday 05:44:25 Armin Berres wrote:
  with the template provided by Modestas. Is this our new policy? Do we
  officially not forward bugreports anymore (at least as long as we have
  no Bugsqad) and tell people immediately to take this upstream?
  I am just asking, because my impression after various discussions e.g.
  on d...@l.d.o has been that this is considered quite rude. But in fact it
  is way less rude than just letting the bugs rot forever.
 Who thinks it is rude, (s)he can join our team and do a better job (but they 
 won't). The main difference is that KDE is not a small package and most vocal 
 developers on d...@l.d.o have no idea what it is like to maintain a huge pile 
 of software which you hardly use 1/3rd yourself (I base my opinion on 
 discussion about copyright files). It is either:
 
 1) let user know what is typically going to happen with his/her bug (i.e. 
 nothing). If we continue with tagging 'upstream', we do a pretty good job 
 separating wasted bugs from useful ones and it is already an improvement.
 2) forget/ignore bugs like we did before. BTS continues to become useless.
 
 IMHO, 1st is a better option. As for presubj, we only have a handful of 
 people 
 reporting upstream bugs to Debian BTS. Once they all get a template reply at 
 least once, it is high probability they won't report such bugs again (or 
 think 
 good about it before reporting). So eventually such presubj's won't be needed.

In case anything wonders what the status is:
We started to tag (mostly) all incoming upstream bugs as those and were begging
the submitter to resubmit upstream.
Some of the bugs have been resubmitted upstream, so this can be
considered to be a success. No one really complained and when there were
complaints people understood our position after a further explanation.

Greetings,
Armin

--
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk

Re: Usertagging incoming bugreports

[Armin Berres]

On Tue, 19 May 09 19:59, trig...@space-based.de wrote:
 1) packaging-bug: These bugs are our fault and should be addressed by us.

Maybe packaging-bug is not the best description, but tagging of bugs we
should have a closer look at, because there is a good chance that we
should try to fix them started.
The currently tagged bugs can be found here:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-...@lists.debian.org;dist=unstable;tag=packaging-bug
So, happy tagging and happy bugfixing.

I have a script to directly tag bugs from mutt (and also send the
requests to forward bugs upstream), if anyone is interested feel free to
ask me for it.

Greetings,
Armin

--
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk

Bug#533441: binutils-gold: does not support -z origin

[Armin Berres]

Package: binutils-gold
Version: 2.19.1-1
Severity: normal

Building qtcreator with gold fails, because qtcreator explicitly sets an
rpath using $ORIGIN:
| QMAKE_LFLAGS += -Wl,-z,origin \'-Wl,-rpath,$${IDE_PLUGIN_RPATH}\'

With gold linking fails, because -z origin is unknown. When removing
the option the rpath is still fine though, so it seems gold supports
$ORIGIN without -z origin.

Greetings,
Armin

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-rc5 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages binutils-gold depends on:
ii  binutils   2.19.1-1  The GNU assembler, linker and bina
ii  libc6  2.9-12GNU C Library: Shared libraries
ii  libgcc11:4.4.0-4 GCC support library
ii  libstdc++6 4.4.0-4   The GNU Standard C++ Library v3
ii  zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime

binutils-gold recommends no packages.

binutils-gold suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#532574: python-kde4: Upgrading to python-qt4 4.5.1 breaks python-kde4

[Armin Berres]

On Wed, 10 Jun 09 11:46, Christoph Burgmer wrote:
 Package: python-kde4
 Version: 4:4.2.4-1
 Severity: grave
 Justification: renders package unusable
 
 After upgrading to python-qt4 4.5.1 any import of a PyKDE4 module makes
 Python exit giving a memory access error (translated from German):
 
 $ python
 Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45)
 [GCC 4.3.3] on linux2
 Type help, copyright, credits or license for more information.
  from PyKDE4 import kdeui
 Speicherzugriffsfehler
 $

Interesting. I observed something like this with python-qt3. See
#528144.
FWIW I think that this is a bug in python-qt4 and not in python-kde4
BTW.
So, anyone out there familiar with python? I would bet that the
python-qt3 and the python-qt4 issues are the same.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#532574: python-kde4: Upgrading to python-qt4 4.5.1 breaks python-kde4

[Armin Berres]

On Wed, 10 Jun 09 11:46, Christoph Burgmer wrote:
 Package: python-kde4
 Version: 4:4.2.4-1
 Severity: grave
 Justification: renders package unusable
 
 After upgrading to python-qt4 4.5.1 any import of a PyKDE4 module makes
 Python exit giving a memory access error (translated from German):
 
 $ python
 Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45)
 [GCC 4.3.3] on linux2
 Type help, copyright, credits or license for more information.
  from PyKDE4 import kdeui
 Speicherzugriffsfehler
 $

Interesting. I observed something like this with python-qt3. See
#528144.
FWIW I think that this is a bug in python-qt4 and not in python-kde4
BTW.
So, anyone out there familiar with python? I would bet that the
python-qt3 and the python-qt4 issues are the same.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#532574: python-kde4: Upgrading to python-qt4 4.5.1 breaks python-kde4

[Armin Berres]

On Wed, 10 Jun 09 11:46, Christoph Burgmer wrote:
 Package: python-kde4
 Version: 4:4.2.4-1
 Severity: grave
 Justification: renders package unusable
 
 After upgrading to python-qt4 4.5.1 any import of a PyKDE4 module makes
 Python exit giving a memory access error (translated from German):
 
 $ python
 Python 2.5.4 (r254:67916, Feb 17 2009, 20:16:45)
 [GCC 4.3.3] on linux2
 Type help, copyright, credits or license for more information.
  from PyKDE4 import kdeui
 Speicherzugriffsfehler
 $

Interesting. I observed something like this with python-qt3. See
#528144.
FWIW I think that this is a bug in python-qt4 and not in python-kde4
BTW.
So, anyone out there familiar with python? I would bet that the
python-qt3 and the python-qt4 issues are the same.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#525756: closed by Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org (Bug#525756: fixed in kdenetwork 4:4.2.4-1)

[Armin Berres]

found 525756 4:4.2.4-1
kthxbye

On Wed, 03 Jun 09 18:34, Facundo wrote:
  We believe that the bug you reported is fixed in the latest version of
  kdenetwork, which is due to be installed in the Debian FTP archive:
 
 I'm using KDE 4.2.4 and kopete still having the same problem. Should I
 report a new bug or it can be open again?

The Debian bug should been open again.
Please also reopen it upstream.
https://bugs.kde.org/show_bug.cgi?id=190786

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#525756: closed by Debian Qt/KDE Maintainers debian-qt-kde@lists.debian.org (Bug#525756: fixed in kdenetwork 4:4.2.4-1)

[Armin Berres]

found 525756 4:4.2.4-1
kthxbye

On Wed, 03 Jun 09 18:34, Facundo wrote:
  We believe that the bug you reported is fixed in the latest version of
  kdenetwork, which is due to be installed in the Debian FTP archive:
 
 I'm using KDE 4.2.4 and kopete still having the same problem. Should I
 report a new bug or it can be open again?

The Debian bug should been open again.
Please also reopen it upstream.
https://bugs.kde.org/show_bug.cgi?id=190786

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531521: hal reports same battery two times

[Armin Berres]

Package: hal
Version: 0.5.12~git20090406.46dc48-2
Severity: normal

Hal reports my internal battery two times, which confuses e.g. the
battery applet of KDE (and this one then confuses me).

From lshal:

udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4_0'
  battery.charge_level.current = 5457  (0x1551)  (int)
  battery.charge_level.design = 11217  (0x2bd1)  (int)
  battery.charge_level.last_full = 11217  (0x2bd1)  (int)
  battery.charge_level.percentage = 48  (0x30)  (int)
  battery.charge_level.rate = 5241  (0x1479)  (int)
  battery.is_rechargeable = true  (bool)
  battery.model = 'Primary'  (string)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = true  (bool)
  battery.rechargeable.is_discharging = false  (bool)
  battery.remaining_time = 3956  (0xf74)  (int)
  battery.reporting.current = 379  (0x17b)  (int)
  battery.reporting.design = 779  (0x30b)  (int)
  battery.reporting.last_full = 779  (0x30b)  (int)
  battery.reporting.rate = 364  (0x16c)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.serial = '02225 2008/05/23'  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.vendor = 'Hewlett-Packard'  (string)
  battery.voltage.current = 16801  (0x41a1)  (int)
  battery.voltage.design = 14400  (0x3840)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Primary'  (string)
  info.subsystem = 'power_supply'  (string)
  info.udi = 
'/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4_0'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'power_supply'  (string)
  linux.sysfs_path = '/sys/class/power_supply/C1F4'  (string)

udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4'
  battery.charge_level.current = 5760  (0x1680)  (int)
  battery.charge_level.design = 11217  (0x2bd1)  (int)
  battery.charge_level.last_full = 11217  (0x2bd1)  (int)
  battery.charge_level.percentage = 51  (0x33)  (int)
  battery.charge_level.rate = 4420  (0x1144)  (int)
  battery.is_rechargeable = true  (bool)
  battery.model = 'Primary'  (string)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = true  (bool)
  battery.rechargeable.is_discharging = false  (bool)
  battery.remaining_time =   (0x115c)  (int)
  battery.reporting.current = 400  (0x190)  (int)
  battery.reporting.design = 779  (0x30b)  (int)
  battery.reporting.last_full = 779  (0x30b)  (int)
  battery.reporting.rate = 307  (0x133)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.serial = '02225 2008/05/23'  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.vendor = 'Hewlett-Packard'  (string)
  battery.voltage.current = 16803  (0x41a3)  (int)
  battery.voltage.design = 14400  (0x3840)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Primary'  (string)
  info.subsystem = 'power_supply'  (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4'  
(string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'power_supply'  (string)
  linux.sysfs_path = '/sys/class/power_supply/C1F4'  (string)

acpi reports just one battery:

| $ acpi
| Battery 0: Charging, 52%, 01:27:43 until charged

Greetings,
Armin

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-rc5 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hal depends on:
ii  acl  2.2.47-2Access control list utilities
ii  adduser  3.110   add and remove users and groups
ii  consolekit   0.3.0-2 framework for defining and trackin
ii  dbus 1.2.14-2simple interprocess messaging syst
ii  hal-info 20090309-1  Hardware Abstraction Layer - fdi f
ii  libc62.9-12  GNU C Library: Shared libraries
ii  libdbus-1-3  1.2.14-2simple interprocess messaging syst
ii  libdbus-glib 0.80-4  simple interprocess messaging syst
ii  libexpat12.0.1-4 XML parsing C library - runtime li
ii  libgcc1  1:4.4.0-4   GCC support library
ii  libglib2.0-0 2.20.1-2The GLib library of C routines
ii  libhal-stora 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share
ii  

Bug#528937: [kdm]

[Armin Berres]

On Mon, 01 Jun 09 14:00, Eike Sauer wrote:
 Hello!
 
 Am Montag, 1. Juni 2009 schrieb Armin Berres:
  I somehow expected the locale to be already set when the init scripts
  are running.
 
 This sound reasonable - so should the bug be forwarded to the init system? 
 Or to the locales package?

It seems as if it is always and since forever the case, that the locale is
set as soon as the user logs in and not before.
Normally this is no problem since most init scripts do not rely on the
locale in any way.

Todays/tomorrows kdebase-workspace upload should fix the bug as soon as
the packages are out of NEW.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531521: Acknowledgement (hal reports same battery two times)

[Armin Berres]

Oh, and I guess it is interesting that this is a new issue. I do not
long since when I have the problem, because until now I thought this was
a rendering problem of plasma, but it is definitely not older then the
last large hal update.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#528937: [kdm]

[Armin Berres]

On Mon, 01 Jun 09 14:00, Eike Sauer wrote:
 Hello!
 
 Am Montag, 1. Juni 2009 schrieb Armin Berres:
  I somehow expected the locale to be already set when the init scripts
  are running.
 
 This sound reasonable - so should the bug be forwarded to the init system? 
 Or to the locales package?

It seems as if it is always and since forever the case, that the locale is
set as soon as the user logs in and not before.
Normally this is no problem since most init scripts do not rely on the
locale in any way.

Todays/tomorrows kdebase-workspace upload should fix the bug as soon as
the packages are out of NEW.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

[Pkg-utopia-maintainers] Bug#531521: hal reports same battery two times

[Armin Berres]

Package: hal
Version: 0.5.12~git20090406.46dc48-2
Severity: normal

Hal reports my internal battery two times, which confuses e.g. the
battery applet of KDE (and this one then confuses me).

From lshal:

udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4_0'
  battery.charge_level.current = 5457  (0x1551)  (int)
  battery.charge_level.design = 11217  (0x2bd1)  (int)
  battery.charge_level.last_full = 11217  (0x2bd1)  (int)
  battery.charge_level.percentage = 48  (0x30)  (int)
  battery.charge_level.rate = 5241  (0x1479)  (int)
  battery.is_rechargeable = true  (bool)
  battery.model = 'Primary'  (string)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = true  (bool)
  battery.rechargeable.is_discharging = false  (bool)
  battery.remaining_time = 3956  (0xf74)  (int)
  battery.reporting.current = 379  (0x17b)  (int)
  battery.reporting.design = 779  (0x30b)  (int)
  battery.reporting.last_full = 779  (0x30b)  (int)
  battery.reporting.rate = 364  (0x16c)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.serial = '02225 2008/05/23'  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.vendor = 'Hewlett-Packard'  (string)
  battery.voltage.current = 16801  (0x41a1)  (int)
  battery.voltage.design = 14400  (0x3840)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Primary'  (string)
  info.subsystem = 'power_supply'  (string)
  info.udi = 
'/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4_0'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'power_supply'  (string)
  linux.sysfs_path = '/sys/class/power_supply/C1F4'  (string)

udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4'
  battery.charge_level.current = 5760  (0x1680)  (int)
  battery.charge_level.design = 11217  (0x2bd1)  (int)
  battery.charge_level.last_full = 11217  (0x2bd1)  (int)
  battery.charge_level.percentage = 51  (0x33)  (int)
  battery.charge_level.rate = 4420  (0x1144)  (int)
  battery.is_rechargeable = true  (bool)
  battery.model = 'Primary'  (string)
  battery.present = true  (bool)
  battery.rechargeable.is_charging = true  (bool)
  battery.rechargeable.is_discharging = false  (bool)
  battery.remaining_time =   (0x115c)  (int)
  battery.reporting.current = 400  (0x190)  (int)
  battery.reporting.design = 779  (0x30b)  (int)
  battery.reporting.last_full = 779  (0x30b)  (int)
  battery.reporting.rate = 307  (0x133)  (int)
  battery.reporting.technology = 'Li-ion'  (string)
  battery.reporting.unit = 'mAh'  (string)
  battery.serial = '02225 2008/05/23'  (string)
  battery.technology = 'lithium-ion'  (string)
  battery.type = 'primary'  (string)
  battery.vendor = 'Hewlett-Packard'  (string)
  battery.voltage.current = 16803  (0x41a3)  (int)
  battery.voltage.design = 14400  (0x3840)  (int)
  battery.voltage.unit = 'mV'  (string)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery'  (string)
  info.parent = '/org/freedesktop/Hal/devices/computer'  (string)
  info.product = 'Primary'  (string)
  info.subsystem = 'power_supply'  (string)
  info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_C1F4'  
(string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'power_supply'  (string)
  linux.sysfs_path = '/sys/class/power_supply/C1F4'  (string)

acpi reports just one battery:

| $ acpi
| Battery 0: Charging, 52%, 01:27:43 until charged

Greetings,
Armin

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-rc5 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hal depends on:
ii  acl  2.2.47-2Access control list utilities
ii  adduser  3.110   add and remove users and groups
ii  consolekit   0.3.0-2 framework for defining and trackin
ii  dbus 1.2.14-2simple interprocess messaging syst
ii  hal-info 20090309-1  Hardware Abstraction Layer - fdi f
ii  libc62.9-12  GNU C Library: Shared libraries
ii  libdbus-1-3  1.2.14-2simple interprocess messaging syst
ii  libdbus-glib 0.80-4  simple interprocess messaging syst
ii  libexpat12.0.1-4 XML parsing C library - runtime li
ii  libgcc1  1:4.4.0-4   GCC support library
ii  libglib2.0-0 2.20.1-2The GLib library of C routines
ii  libhal-stora 0.5.12~git20090406.46dc48-2 Hardware Abstraction Layer - share
ii  

Bug#528937: [kdm]

[Armin Berres]

First: Thanks for forwarding :-)

On Sun, 31 May 09 16:24, Eike Sauer wrote:
 Debian points me to upstream KDE,
 and KDE points me to downstream Debian... :o)
 
 Ok, I tried the hint from KDE: 
 Setting LC_ALL in /etc/init.d/kdm works.

Hah, LC_ALL overwrites all other LC_* variables and should therefore
normally not be used. [0]
KDM should definitely not rely on LC_ALL which is normally not set.

So, I hereby send you back upstream. Let us see what Ossi has to say.

Greetings,
Armin

[0] http://opengroup.org/onlinepubs/007908799/xbd/envvar.html



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#528937: [kdm]

[Armin Berres]

On Sun, 31 May 09 16:24, Eike Sauer wrote:
 But isn't this a Debian bug nevertheless?
 I called dpkg-reconfigure locales, and de_DE.UTF-8 is 
 (and already was) my default locale, so I feel kdm should 
 use it out of the box...

Oh, and could you send the output of locale? Just to make sure
everything looks sane...

/Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#528937: [kdm]

[Armin Berres]

On Sun, 31 May 09 16:24, Eike Sauer wrote:
 Package: kdm
 Version: 4:4.2.2-2
 
 --- Please enter the report below this line. ---
 Debian points me to upstream KDE,
 and KDE points me to downstream Debian... :o)

Sory for the confusion, but yes, this is a Debian bug.
I somehow expected the locale to be already set when the init scripts
are running.

Could you please try to add the following to /etc/init.d/kdm:

| if [ -r /etc/default/locale ]; then
|  . /etc/default/locale
|  export LANG LANGUAGE
| fi

This should fix the issue.
Will apply this to SVN in a second.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530696: kdebase-runtime really does need Oxygen icons

[Armin Berres]

On Mon, 01 Jun 09 01:48, Sune Vuorela wrote:
 On Monday 01 June 2009 00:58:25 Ben Klein wrote:
  2009/6/1 Josh Metzler josh...@metzlers.org:
   severity 530696 wishlist
   tags 530696 + wontfix
   thanks
  
   The main reason the Oxygen icon set is so much bigger than many others is
   that it is the only one containing a complete set of icons.  It is used
   as a backup in case the selected icon set is missing an icon.  If you
   were to install one of the smaller icon sets and remove kde-icons-oxygen,
   you would likely have many missing icons.
 
  I still think it's unnecessarily large and a packaging error.
  kdebase-runtime should depend on a virtual package that can be
  provided by other, complete icon themes when they become available.
 
 We can easy revisit it the day there is a complete alternate icon  set.
 
 I really think though, that the fallback icon theme should be present always, 
 else you might get weird questionmarks in all sorts of applications.

And for what it'ss worth, the icons will not be small, but a lot smaller
one 4.3 is out. The reason is, that the .svgz-files will not be
installed anymore.

ar...@bluefire:~/tmp/oxygen-icons-4.2.85/debian$ du -hs kde-icons-oxygen
33M kde-icons-oxygen

$ aptitude show kde-icons-oxygen | grep Size
Uncompressed Size: 85.7M

/Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531359: closed by Sune Vuorela s...@vuorela.dk (Re: Bug#531359: kicker: Unmet dependancies)

[Armin Berres]

On Sun, 31 May 09 20:17, Norbert Veber wrote:
 On Sun, May 31, 2009 at 11:30:08PM +, Debian Bug Tracking System wrote:
  There is no more kicker in kde.
 
 If thats true, then kdebase shouldnt depend on it.

Are you trying something like aptitude safe-upgrade? If yes
aptitude dist-upgrade is what you want. The kdebase from
testing definitely does not depend anymore on kicker.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531359: closed by Sune Vuorela s...@vuorela.dk (Re: Bug#531359: kicker: Unmet dependancies)

[Armin Berres]

On Sun, 31 May 09 22:58, Norbert Veber wrote:
 On Sun, May 31, 2009 at 10:53:47PM -0400, Norbert Veber wrote:
  Version: 4:3.5.9.dfsg.1-6
 
 Oops, I was looking at the wrong package, thats what I get for having both
 stable and unstable in sources.list.
 
 Anyhow, something IS depending on kicker in unstable because 
 aptitude install kde fails, its jsut not kdebase :P

This will install kde from stable. The meta-package called kde is
gone. These days you have e.g. kde-minimal and kde-full.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#528937: [kdm]

[Armin Berres]

First: Thanks for forwarding :-)

On Sun, 31 May 09 16:24, Eike Sauer wrote:
 Debian points me to upstream KDE,
 and KDE points me to downstream Debian... :o)
 
 Ok, I tried the hint from KDE: 
 Setting LC_ALL in /etc/init.d/kdm works.

Hah, LC_ALL overwrites all other LC_* variables and should therefore
normally not be used. [0]
KDM should definitely not rely on LC_ALL which is normally not set.

So, I hereby send you back upstream. Let us see what Ossi has to say.

Greetings,
Armin

[0] http://opengroup.org/onlinepubs/007908799/xbd/envvar.html



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#528937: [kdm]

[Armin Berres]

On Sun, 31 May 09 16:24, Eike Sauer wrote:
 But isn't this a Debian bug nevertheless?
 I called dpkg-reconfigure locales, and de_DE.UTF-8 is 
 (and already was) my default locale, so I feel kdm should 
 use it out of the box...

Oh, and could you send the output of locale? Just to make sure
everything looks sane...

/Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#528937: [kdm]

[Armin Berres]

On Sun, 31 May 09 16:24, Eike Sauer wrote:
 Package: kdm
 Version: 4:4.2.2-2
 
 --- Please enter the report below this line. ---
 Debian points me to upstream KDE,
 and KDE points me to downstream Debian... :o)

Sory for the confusion, but yes, this is a Debian bug.
I somehow expected the locale to be already set when the init scripts
are running.

Could you please try to add the following to /etc/init.d/kdm:

| if [ -r /etc/default/locale ]; then
|  . /etc/default/locale
|  export LANG LANGUAGE
| fi

This should fix the issue.
Will apply this to SVN in a second.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530696: kdebase-runtime really does need Oxygen icons

[Armin Berres]

On Mon, 01 Jun 09 01:48, Sune Vuorela wrote:
 On Monday 01 June 2009 00:58:25 Ben Klein wrote:
  2009/6/1 Josh Metzler josh...@metzlers.org:
   severity 530696 wishlist
   tags 530696 + wontfix
   thanks
  
   The main reason the Oxygen icon set is so much bigger than many others is
   that it is the only one containing a complete set of icons.  It is used
   as a backup in case the selected icon set is missing an icon.  If you
   were to install one of the smaller icon sets and remove kde-icons-oxygen,
   you would likely have many missing icons.
 
  I still think it's unnecessarily large and a packaging error.
  kdebase-runtime should depend on a virtual package that can be
  provided by other, complete icon themes when they become available.
 
 We can easy revisit it the day there is a complete alternate icon  set.
 
 I really think though, that the fallback icon theme should be present always, 
 else you might get weird questionmarks in all sorts of applications.

And for what it'ss worth, the icons will not be small, but a lot smaller
one 4.3 is out. The reason is, that the .svgz-files will not be
installed anymore.

ar...@bluefire:~/tmp/oxygen-icons-4.2.85/debian$ du -hs kde-icons-oxygen
33M kde-icons-oxygen

$ aptitude show kde-icons-oxygen | grep Size
Uncompressed Size: 85.7M

/Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531359: closed by Sune Vuorela s...@vuorela.dk (Re: Bug#531359: kicker: Unmet dependancies)

[Armin Berres]

On Sun, 31 May 09 20:17, Norbert Veber wrote:
 On Sun, May 31, 2009 at 11:30:08PM +, Debian Bug Tracking System wrote:
  There is no more kicker in kde.
 
 If thats true, then kdebase shouldnt depend on it.

Are you trying something like aptitude safe-upgrade? If yes
aptitude dist-upgrade is what you want. The kdebase from
testing definitely does not depend anymore on kicker.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531359: closed by Sune Vuorela s...@vuorela.dk (Re: Bug#531359: kicker: Unmet dependancies)

[Armin Berres]

On Sun, 31 May 09 22:58, Norbert Veber wrote:
 On Sun, May 31, 2009 at 10:53:47PM -0400, Norbert Veber wrote:
  Version: 4:3.5.9.dfsg.1-6
 
 Oops, I was looking at the wrong package, thats what I get for having both
 stable and unstable in sources.list.
 
 Anyhow, something IS depending on kicker in unstable because 
 aptitude install kde fails, its jsut not kdebase :P

This will install kde from stable. The meta-package called kde is
gone. These days you have e.g. kde-minimal and kde-full.

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531110: lskat: Game terminates with Game was aborted, no points

[Armin Berres]

Sorry, but what do you want to tell us with this bugreport which is
empty apart from the subject?

Greetings,
Armin

On Sat, 30 May 09 09:01, Raj Mathur wrote:
 Package: lskat
 Version: 4:4.2.2-1
 Severity: normal
 
 
 
 -- System Information:
 Debian Release: squeeze/sid
   APT prefers testing
   APT policy: (990, 'testing')
 Architecture: i386 (i686)
 
 Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
 Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash
 
 Versions of packages lskat depends on:
 ii  kdebase-runtime   4:4.2.2-1  runtime components from the 
 offici
 ii  kdegames-card-data4:4.2.2-1  card decks for KDE 4 games
 ii  kdelibs5  4:4.2.2-2  core libraries for all KDE 4 
 appli
 ii  libc6 2.9-12 GNU C Library: Shared libraries
 ii  libgcc1   1:4.4.0-5  GCC support library
 ii  libkdegames5  4:4.2.2-1  libraries and common files for 
 KDE
 ii  libqt4-dbus   4.5.1-2Qt 4 D-Bus module
 ii  libqt4-network4.5.1-2Qt 4 network module
 ii  libqt4-svg4.5.1-2Qt 4 SVG module
 ii  libqt4-xml4.5.1-2Qt 4 XML module
 ii  libqtcore44.5.1-2Qt 4 core module
 ii  libqtgui4 4.5.1-2Qt 4 GUI module
 ii  libstdc++64.4.0-5The GNU Standard C++ Library v3
 
 lskat recommends no packages.
 
 lskat suggests no packages.
 
 -- no debconf information
 
 
 
 -- 
 To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#531110: lskat: Game terminates with Game was aborted, no points

[Armin Berres]

Sorry, but what do you want to tell us with this bugreport which is
empty apart from the subject?

Greetings,
Armin

On Sat, 30 May 09 09:01, Raj Mathur wrote:
 Package: lskat
 Version: 4:4.2.2-1
 Severity: normal
 
 
 
 -- System Information:
 Debian Release: squeeze/sid
   APT prefers testing
   APT policy: (990, 'testing')
 Architecture: i386 (i686)
 
 Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
 Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/bash
 
 Versions of packages lskat depends on:
 ii  kdebase-runtime   4:4.2.2-1  runtime components from the 
 offici
 ii  kdegames-card-data4:4.2.2-1  card decks for KDE 4 games
 ii  kdelibs5  4:4.2.2-2  core libraries for all KDE 4 
 appli
 ii  libc6 2.9-12 GNU C Library: Shared libraries
 ii  libgcc1   1:4.4.0-5  GCC support library
 ii  libkdegames5  4:4.2.2-1  libraries and common files for 
 KDE
 ii  libqt4-dbus   4.5.1-2Qt 4 D-Bus module
 ii  libqt4-network4.5.1-2Qt 4 network module
 ii  libqt4-svg4.5.1-2Qt 4 SVG module
 ii  libqt4-xml4.5.1-2Qt 4 XML module
 ii  libqtcore44.5.1-2Qt 4 core module
 ii  libqtgui4 4.5.1-2Qt 4 GUI module
 ii  libstdc++64.4.0-5The GNU Standard C++ Library v3
 
 lskat recommends no packages.
 
 lskat suggests no packages.
 
 -- no debconf information
 
 
 
 -- 
 To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526779: Forwarding bugs upstream (Was: Bug#526779: battery-applet: Misleads about still charging)

[Armin Berres]

Sheridan Hutchinson wrote:
 In my view, what you have wrote is completely contrary to the spirit
 and the wording of section 3.5 of the Debian Developer's Reference:
 http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination

 I refer specifically to this sentence:
 A big part of your job as Debian maintainer will be to stay in
 contact with the upstream developers. Debian users will sometimes
 report bugs that are not specific to Debian to our bug tracking
 system. You have to forward these bug reports to the upstream
 developers so that they can be fixed in a future upstream release.

 With this wording it would appear that the onus does fall on KDE
 developers to forward this to upstream.

 I invite your comments.

So you have found the Developer's Reference. Nice. The problem is, that
we have no way to realize what is written there. We simply have not the
manpower to forward the tons of upstream bugs we receive. KDE is a very
very huge beast and we are very less developers. Sou our choices are to
a) Package new releases and fix packaging bugs, or b) Forward bugs
upstreams.
So, what do you prefer? It is not that we are to lazy to forward the
bugs, we would love to do it. But sadly it is not possible.

I find it way less rude to tell you that it is not likely that we
forward the bug upstream instead of letting the bug rot the next 3 years
and then as you to report if the bug still applies.

I hope you get the point.

Everyone is welcome to join the team and forward bugs btw...

Greetings,
Armin




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526779: Forwarding Bugs upstream (was: Bug#526779: battery-applet: Misleads about still charging)

[Armin Berres]

On Fri, 29 May 09 07:36, Sheridan Hutchinson wrote:
 In my view, what you have wrote is completely contrary to the spirit
 and the wording of section 3.5 of the Debian Developer's Reference:
 http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination
 
 I refer specifically to this sentence:
 A big part of your job as Debian maintainer will be to stay in
 contact with the upstream developers. Debian users will sometimes
 report bugs that are not specific to Debian to our bug tracking
 system. You have to forward these bug reports to the upstream
 developers so that they can be fixed in a future upstream release.
 
 With this wording it would appear that the onus does fall on KDE
 developers to forward this to upstream.
 
 I invite your comments.

So you have found the Developer's Reference. Nice. The problem is, that
we have no way to realize what is written there. We simply have not the
manpower to forward the tons of upstream bugs we receive. KDE is a very
very huge beast and we are very less developers. Sou our choices are to
a) Package new releases and fix packaging bugs, or b) Forward bugs
upstreams.
So, what do you prefer? It is not that we are to lazy to forward the
bugs, we would love to do it. But sadly it is not possible.

I find it way less rude to tell you that it is not likely that we
forward the bug upstream instead of letting the bug rot the next 3 years
and then as you to report if the bug still applies.

I hope you get the point.

Everyone is welcome to join the team and forward bugs btw...

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526779: Forwarding bugs upstream (Was: Bug#526779: battery-applet: Misleads about still charging)

[Armin Berres]

Sheridan Hutchinson wrote:
 In my view, what you have wrote is completely contrary to the spirit
 and the wording of section 3.5 of the Debian Developer's Reference:
 http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination

 I refer specifically to this sentence:
 A big part of your job as Debian maintainer will be to stay in
 contact with the upstream developers. Debian users will sometimes
 report bugs that are not specific to Debian to our bug tracking
 system. You have to forward these bug reports to the upstream
 developers so that they can be fixed in a future upstream release.

 With this wording it would appear that the onus does fall on KDE
 developers to forward this to upstream.

 I invite your comments.

So you have found the Developer's Reference. Nice. The problem is, that
we have no way to realize what is written there. We simply have not the
manpower to forward the tons of upstream bugs we receive. KDE is a very
very huge beast and we are very less developers. Sou our choices are to
a) Package new releases and fix packaging bugs, or b) Forward bugs
upstreams.
So, what do you prefer? It is not that we are to lazy to forward the
bugs, we would love to do it. But sadly it is not possible.

I find it way less rude to tell you that it is not likely that we
forward the bug upstream instead of letting the bug rot the next 3 years
and then as you to report if the bug still applies.

I hope you get the point.

Everyone is welcome to join the team and forward bugs btw...

Greetings,
Armin




--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#526779: Forwarding Bugs upstream (was: Bug#526779: battery-applet: Misleads about still charging)

[Armin Berres]

On Fri, 29 May 09 07:36, Sheridan Hutchinson wrote:
 In my view, what you have wrote is completely contrary to the spirit
 and the wording of section 3.5 of the Debian Developer's Reference:
 http://www.debian.org/doc/manuals/developers-reference/developer-duties.html#upstream-coordination
 
 I refer specifically to this sentence:
 A big part of your job as Debian maintainer will be to stay in
 contact with the upstream developers. Debian users will sometimes
 report bugs that are not specific to Debian to our bug tracking
 system. You have to forward these bug reports to the upstream
 developers so that they can be fixed in a future upstream release.
 
 With this wording it would appear that the onus does fall on KDE
 developers to forward this to upstream.
 
 I invite your comments.

So you have found the Developer's Reference. Nice. The problem is, that
we have no way to realize what is written there. We simply have not the
manpower to forward the tons of upstream bugs we receive. KDE is a very
very huge beast and we are very less developers. Sou our choices are to
a) Package new releases and fix packaging bugs, or b) Forward bugs
upstreams.
So, what do you prefer? It is not that we are to lazy to forward the
bugs, we would love to do it. But sadly it is not possible.

I find it way less rude to tell you that it is not likely that we
forward the bug upstream instead of letting the bug rot the next 3 years
and then as you to report if the bug still applies.

I hope you get the point.

Everyone is welcome to join the team and forward bugs btw...

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530886: kde-window-manager: trying to enable desktop effects freezes computer

[Armin Berres]

tags 530886 upstream
thanks

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one on the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 530419 KDE-BUG-URL
thanks
[ copy this ]

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530886: kde-window-manager: trying to enable desktop effects freezes computer

[Armin Berres]

tags 530886 upstream
thanks

Hello,

the bug you reported is a KDE bug. Please report it via
Help - Report bug... menu item of the respective application
or by visiting https://bugs.kde.org/ and following instructions
to report a new bug.

Debian Qt/KDE maintainers do not have resources to deal with
non Debian-specific bugs and therefore it is unlikely that
your bug will be solved if you do not report it to KDE developers
directly (unless it is/has been reported by somebody else).

Whenever you open a bug report or find an existing one on the KDE
bug tracking system, you can couple both this Debian bug and the
KDE bug together by sending a mail with the text below to
cont...@bugs.debian.org (replace KDE-BUG-URL with the address of
the bug report on https://bugs.kde.org/)

[ copy this ]
forwarded 530419 KDE-BUG-URL
thanks
[ copy this ]

Greetings,
Armin



-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Adding presubj files for all KDE packages

[Armin Berres]

On Tue, 19 May 09 20:41, trig...@space-based.de wrote:
 What do you think?

So, no feedback here so far, we are really more IRC than mailinglist
users.
What I understand so far is, that installing presubj files for all
packages is not an option, because e.g. people get used to simply ignore
the presubj messages.
The question is, if presubj files should be installed for packages which
create a lot of reports like Konqueror, Kmail, Akreator, Plasma...

These days people started to tag all upstream bugs as those and reply
with the template provided by Modestas. Is this our new policy? Do we
officially not forward bugreports anymore (at least as long as we have
no Bugsqad) and tell people immediately to take this upstream? 
I am just asking, because my impression after various discussions e.g.
on d...@l.d.o has been that this is considered quite rude. But in fact it
is way less rude than just letting the bugs rot forever.

So, can we agree on something official?
The default template-solution has my vote FWIW...

Greetings,
Armin

--
http://lists.alioth.debian.org/mailman/listinfo/pkg-kde-talk

Bug#528754: closed by Sune Vuorela deb...@pusling.com (Re: Bug#528754: kdelibs do not build without avahi)

[Armin Berres]

On Mon, 18 May 09 15:18, bugrepor...@udmvt.ru wrote:
 I didn't understand, why you closed the bug. Seriously.
 Do you have enough expertise to read the mentioned patch file? 
 (./debian/patches/98_buildprep.diff)
 If so, do it. If not, I will try to explain what I am seeing.
 
 So, first, there are the original source package. It builds OK.
 There are debianised sources - the added ./debian directory.
 That directory contains subdirectory ./patches.
 When you build .deb binary packages, you usually run debian/rules
 makefile. And it unconditionally applies .diff files from debian/patches
 directory (it really doesn't ask you). That's not my modification, that's 
 Debian's.
 This report was about Debian package kdelibs, not upstream's, not my own 
 version.
 
 What is wrong with Debian's modifications to the package.
 It removes (otherwise provided by upstream) the option to build without
 some questionable and purely optional feature like dnssd,
 that opens additional remote attack vectors, limited to local network.
 The files, that come from Debian maintainers (do you represent any of them?),
 break configure process if there is no libahavi development files present
 on the system.

Do you expect random people to close random bugreports?

 I have wrote already to the debian desktop mailing list and
 was told, that I have a freedom to recompile binary .debs from
 sources and without that exactly option.
 
 This report was to inform everyone, that it is no more true for Debian version
 of the kdelibs. 

We do officially not support any kind of changes to the Debian packages
in the archive. I'm sorry, but if you change a Debian source package and it
does not work afterwards, you are on your own. You could use the sources
provided by upstream e.g.
Debian is not Gentoo. We do not support enabling/disabling random
features by recompiling.
Debian is all about the binary packages and unchanged source packages.

And anyway: KDE 3 is dead. There will be no uploads which do not fix
RC-Bugs. If we consider this to be a bug (and we don't), it changes nothing,
because it is definitely not RC and will therefore not be fixed.

Friendly,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#529356: akregator: SIGSEV after marking a lot of unread feeds as read

[Armin Berres]

On Mon, 18 May 09 23:17, Jordan Manolov wrote:
 Package: akregator
 Version: 4:4.2.2-1
 Severity: normal
 
 After fetching feeds - about 75-100 - and marking them as read, 
 akregator always crashes. Here is the backtrace:
 
 Application: Akregator (akregator), signal SIGSEGV
 
 Thread 1 (Thread 0xb4fae710 (LWP 12671)):
 #0  0xb7f61424 in __kernel_vsyscall ()
 #1  0xb69a2386 in nanosleep () from /lib/i686/cmov/libc.so.6
 #2  0xb69a219e in sleep () from /lib/i686/cmov/libc.so.6
 #3  0xb7c90738 in ?? () from /usr/lib/libkdeui.so.5
 #4  0x in ?? ()

Could you please install kdepim-dbg (attention, it is large) and
recreate the backtrace? The one above is quite meaningless without
debugging symbols.

Thanks in advance,
Armin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org