1 |
--------------------------------------------------------------------------- |
2 |
Gentoo Weekly Newsletter |
3 |
http://www.gentoo.org/news/en/gwn/current.xml |
4 |
This is the Gentoo Weekly Newsletter for the week of 19 June 2006. |
5 |
--------------------------------------------------------------------------- |
6 |
|
7 |
============== |
8 |
1. Gentoo news |
9 |
============== |
10 |
|
11 |
Userrel wants YOU! - User Representatives Nominations |
12 |
----------------------------------------------------- |
13 |
|
14 |
As one of the major distributions at the moment, Gentoo's organisation can |
15 |
be a fiendishly complicated thing to understand, and it can be difficult |
16 |
to know how you can help out. To this end, we have created the position of |
17 |
‘user representative’, and would like to take this opportunity to explain |
18 |
something about the role. |
19 |
|
20 |
“Know thy users” is popular advice, and often we attempt to achieve this |
21 |
by consultation with one or more users. People will tend to err towards |
22 |
the idea of the statistical ‘average user’ – one speaks for all. Although |
23 |
this approach is a simple and oftentimes effective way to find a |
24 |
representative user, the results are only valuable if the user base, their |
25 |
day-to-day tasks and work settings are homogeneous. If there are |
26 |
significant variations, this approach will fail to support some users, and |
27 |
can result in a product that does not meet their needs. It relies heavily |
28 |
upon having selected the most important user attributes for sampling and |
29 |
consultation, and can easily tempt us to think that knowing the |
30 |
characteristics of the average user, we need not consult with them. In |
31 |
this way it discourages us from challenging our own assumptions, and may |
32 |
deny us a source of valuable information that could prevent mistakes. |
33 |
|
34 |
The User Relations project focuses on bridging the gap between the |
35 |
developer and user communities, actively seeking out ways to improve |
36 |
communications between the two and encourage user involvement. It aims to |
37 |
ensure that high standards are met, and to work closely with other user |
38 |
focused projects to produce the best distribution possible for the user |
39 |
base. To this end, it is looking for user representatives to help in this |
40 |
quest. |
41 |
|
42 |
The project has decided that 5 user representatives should be enough to |
43 |
provide a sufficiently diverse range of opinions and interests while |
44 |
avoiding the issues associated with having too many. Nominations are now |
45 |
open; see this forum thread[1] for more information and to nominate any |
46 |
users you would like to see considered for the position. |
47 |
|
48 |
1. http://forums.gentoo.org/viewtopic-t-470136.html |
49 |
|
50 |
What does a User Representative do? |
51 |
|
52 |
Becoming a user representative may take some time, energy and commitment, |
53 |
but it can also be very rewarding. The role of user representative |
54 |
involves: |
55 |
|
56 |
* Present the views, and represent the interests, of all elements of our |
57 |
diverse user base. |
58 |
* Be a ‘critical friend’ to the User Relations project, offering |
59 |
alternative opinions and perspectives, and challenging the assumptions of |
60 |
all involved wherever appropriate. |
61 |
* Engage positively with developers and Gentoo projects |
62 |
* Interact with a wide range of groups and individuals to find out what |
63 |
our users think, and what they would like to see happening. |
64 |
* Suggest ways in which other users could be engaged and involved in the |
65 |
project, in planning and delivering information and elsewhere. |
66 |
* Channel information back to the users regarding proceedings of and |
67 |
decisions made in meetings. |
68 |
|
69 |
If you were thinking of becoming a user representative, you will not be |
70 |
left alone. The user relations project will be there to support you, and |
71 |
you will be assigned a current developer as a point of contact with whom |
72 |
you can discuss any questions or concerns about your role or the group as |
73 |
a whole. |
74 |
|
75 |
Why become a user representative? |
76 |
|
77 |
* You will have the opportunity to influence how information, news, and |
78 |
support are delivered to users, and to ensure that they are organised in |
79 |
the best way possible for all our users. |
80 |
* You will gain experience as an advocate for the user community, and |
81 |
useful knowledge and skills that can be applied in many areas of life. |
82 |
* It is a great way to give something back to the community, and to get |
83 |
involved as a user. |
84 |
* You will have the chance to meet and get to know other users and |
85 |
developers. |
86 |
|
87 |
What makes a good user representative? |
88 |
|
89 |
The ideal user representative would: |
90 |
|
91 |
* Be willing to network with a wide range of other users. |
92 |
* Be seen as approachable by others, so that people will be open about |
93 |
their views. Be non-judgemental and show sensitivity towards what may be |
94 |
difficult issues. |
95 |
* Work constructively with developers and staff. Not be scared or |
96 |
intimidated by developers, but to view them as people doing the best they |
97 |
can within constraints. Should it be necessary to challenge them, do so in |
98 |
a supportive manner wherever possible. |
99 |
* Be able to negotiate, to make the case for a particular course of |
100 |
action, and willing to compromise where appropriate. |
101 |
* Be able to step outside of his/her own experience, and be able to argue |
102 |
a viewpoint with which you may not fully agree. |
103 |
* Present users' views with confidence, and not be afraid to raise issues |
104 |
about the role or the workings of the project. |
105 |
|
106 |
Where can I learn more? |
107 |
|
108 |
We hope that most questions will have been answered above, but for any |
109 |
more information please do get in touch with the user relations team by |
110 |
one of the following methods: |
111 |
|
112 |
* gentoo-userrel mailing list -- to subscribe, send a blank email to |
113 |
gentoo-userrel+subscribe@g.o; the address to post is then |
114 |
gentoo-userrel@g.o. |
115 |
* By email to userrel@g.o. |
116 |
* In IRC: #gentoo-userrel[2] on irc.freenode.net. |
117 |
2. irc://irc.freenode.net/gentoo-userrel |
118 |
|
119 |
|
120 |
Other ways to get involved |
121 |
|
122 |
There are a number of areas in which interested users can contribute to |
123 |
Gentoo: |
124 |
|
125 |
* Gentoo Linux Development team: Prospective developers are encouraged to |
126 |
become active on bugzilla[3]. The bug reports are monitored by development |
127 |
recruiters, so start squashing bugs and you will become noticed. |
128 |
* Gentoo Bugdays: On the first Saturday of each month both developers and |
129 |
users gather in #gentoo-bugs[4] on irc.freenode.net[5] where bugs are |
130 |
tested, discussed and resolved. Bugdays offer a great way for developers |
131 |
and users to work together and get to know each other. It also provides an |
132 |
opportunity for potential developers to be scouted. For further |
133 |
information the Bugday team[6] can be contacted. |
134 |
* Gentoo Linux Documentation team: The team provides users with clear and |
135 |
concise documentation. It consists of Writers/Editors and Translators for |
136 |
various languages. For more information on joining take a look at the |
137 |
Gentoo Linux Documentation Policy.[7] |
138 |
* Gentoo Weekly Newsletter: If you would like to offer your help to the |
139 |
GWN team as a contributor or translator then contact information can be |
140 |
found in the Gentoo Weekly Newsletter Overview. |
141 |
* #gentoo IRC Channel: Knowledgeable users are encouraged to come and |
142 |
help out in #gentoo[8] on irc.freenode.net. |
143 |
* #gentoo-dev-help IRC Channel: Anyone wanting to know more about ebuild |
144 |
writing and/or Gentoo development is welcome to come and ask in |
145 |
#gentoo-dev-help[9] on Freenode, where developers and other users are |
146 |
waiting to help. |
147 |
3. bugs.gentoo.org |
148 |
4. irc://irc.freenode.net/gentoo-bugs |
149 |
5. http://irc.freenode.net |
150 |
6. http://bugday.gentoo.org/ |
151 |
7. http://www.gentoo.org/proj/en/gdp/doc/doc-policy.xml |
152 |
8. irc://irc.freenode.net/gentoo |
153 |
9. irc://irc.freenode.net/gentoo-dev-help |
154 |
|
155 |
|
156 |
Project Sunrise - Gentoo User Overlay |
157 |
------------------------------------- |
158 |
|
159 |
Last week there was the announcement of an overlay for user-submitted |
160 |
ebuilds. This was intended to help users to find and use ebuilds that for |
161 |
now only exist in Gentoo Bugzilla and to ensure that these ebuilds adhere |
162 |
to quality standards. Also it might offer a good environment for |
163 |
recruiting new ebuild developers from the user community. |
164 |
|
165 |
Giving commit access to this repository to trusted users has caused some |
166 |
very intense debates, centering mostly around policies and potential |
167 |
problems from malicious users. During the council meeting on June 16th it |
168 |
was decided that while the idea is quite good the execution was lacking. |
169 |
|
170 |
As a consequence the Sunrise overlay has been suspended from official |
171 |
Gentoo hardware, but it does continue on gentoo-sunrise.org[10] as an |
172 |
unofficial project. |
173 |
|
174 |
10. http://gentoo-sunrise.org |
175 |
|
176 |
Sunrise is looking for more users to add ebuilds from bugzilla to the |
177 |
overlay. You can find more information about Sunrise and its goals on the |
178 |
project page[11] and have a look at the FAQ[12] as well as the actual |
179 |
overlay.[13] Feel free to visit the IRC channel - #gentoo-sunrise[14] on |
180 |
irc.freenode.net awaits you! |
181 |
|
182 |
11. http://www.gentoo.org/proj/en/sunrise |
183 |
12. http://gentoo-sunrise.org/cgi-bin/trac.cgi/wiki/SunriseFaq |
184 |
13. http://gentoo-sunrise.org/cgi-bin/trac.cgi/browser |
185 |
14. irc://irc.freenode.net/gentoo-sunrise |
186 |
|
187 |
Java 1.5 progress and changes in Java handling |
188 |
---------------------------------------------- |
189 |
|
190 |
As some might have noticed, Java 1.5 has been package.masked for some time |
191 |
now. There are a number of issues introduced with 1.5 that have kept it in |
192 |
package.mask. Please see the Java 1.5 FAQ[15] for more details. |
193 |
|
194 |
15. http://www.gentoo.org/proj/en/java/tiger-faq.xml |
195 |
|
196 |
About a year ago, work was begun on improving our part of the build system |
197 |
(read: Java related eclasses and our java-config tool) in a way to make it |
198 |
much more flexible in general, but specifically improve it to get around |
199 |
the known issues. It took about six months to fully develop. |
200 |
Unfortunately, the new system was not quite a drop-in replacement. So, it |
201 |
took from then until now to determine how to migrate from the current |
202 |
system to the new one in a sane way. |
203 |
|
204 |
But now we are ready to move to the new system. |
205 |
|
206 |
Highlights of the new system: |
207 |
|
208 |
* Ability to switch the current VM on the fly |
209 |
* Changes to the user and system VM take effect immediately, and no |
210 |
longer are tied to the shell environment (ie no more running env-update && |
211 |
source /etc/profile after switching the sytem VM) |
212 |
* Now has the concept of a ‘build VM’, which is used to emerge packages, |
213 |
and is configured independently of the system VM. |
214 |
* For each version of Java, ie 1.3, 1.4, 1.5, etc, the build vm can |
215 |
configured as to which vendor and version of a VM to use |
216 |
* The VM at emerge time will be switched on the fly according to its |
217 |
configuration, as well as the dependency of the package. For example, some |
218 |
packages won't compile with 1.5. In these cases, a 1.4 VM will be used at |
219 |
build time. |
220 |
* Java packages which build with ant will have their build.xml rewritten |
221 |
at build time, in order to ensure that the correct version of Java |
222 |
bytecode is compiled. |
223 |
* We'll be able to unmask Java 1.5 soon, and be able to handle Java 1.6 |
224 |
when it comes out this fall. |
225 |
|
226 |
The new system is currently being discussed on the gentoo-dev |
227 |
mailinglist[16], and assuming no major issues come up, will likely make |
228 |
their way into the tree in the next few weeks. |
229 |
|
230 |
16. http://article.gmane.org/gmane.linux.gentoo.devel/39547 |
231 |
|
232 |
nss_ldap breakage and how to prevent it |
233 |
--------------------------------------- |
234 |
|
235 |
With the upgrade to nss_ldap-249 and later many users found their system |
236 |
in an almost unusable state: Upon boot it could take an extremely long |
237 |
time (up to an hour) to get to a login prompt. This is caused by a small |
238 |
change in behaviour: What used to be a fixed timeout is now a configurable |
239 |
amount of attempts with increasing time between them. Information how to |
240 |
fix this problem can be found here: |
241 |
|
242 |
* Upgrading/using nss_ldap/nss_mysql/nss_nis/nss... and not breaking your |
243 |
system[17] |
244 |
17. http://robbat2.livejournal.com/199841.html |
245 |
|
246 |
|
247 |
Hungarian GWN translators |
248 |
------------------------- |
249 |
|
250 |
Recently a Hungarian GWN translation has been considered. Right now we are |
251 |
looking for some translators to help with the task - if you are interested |
252 |
please send a notice to gwn-feedback@g.o. Many thanks in advance! |
253 |
|
254 |
========================= |
255 |
2. Heard in the community |
256 |
========================= |
257 |
|
258 |
planet.gentoo.org |
259 |
----------------- |
260 |
|
261 |
Gentoo multimedia FAQ |
262 |
|
263 |
After seeing lots of similar questions on the Gentoo Forums and the |
264 |
#gentoo IRC channel Steve Dibb started collecting questions for a |
265 |
multimedia FAQ. If you like to see common questions being answered in his |
266 |
FAQ let him know[18]. |
267 |
|
268 |
18. beandog@g.o |
269 |
|
270 |
* Gentoo multimedia FAQ[19] |
271 |
19. http://wonkabar.org/blog/?p=96 |
272 |
|
273 |
|
274 |
gentoo-dev |
275 |
---------- |
276 |
|
277 |
Project Sunrise |
278 |
|
279 |
The User Overlay project by Stefan Schweizer[20] and Markus Ullmann[21] |
280 |
has caused much discussion and has been suspended for now. The following |
281 |
threads spawned from this announcement: |
282 |
|
283 |
20. genstef@g.o |
284 |
21. jokey@g.o |
285 |
|
286 |
* [ANNOUNCE] Project Sunrise - Gentoo User Overlay [22] |
287 |
* Project Sunrice: arch team perspective [23] |
288 |
* What is "official"? [24] |
289 |
* Sunrise Project -- Open questions post requirement [25] |
290 |
* Project Sunrise -- Proposal [26] |
291 |
* Project Sunrise overlay suspended pending Council resolution[27] |
292 |
* A heretical thought? Blessing project sunrise as an almost-fork. [28] |
293 |
* Sunrise: way forward, semi-official, review[29] |
294 |
22. http://thread.gmane.org/gmane.linux.gentoo.devel/38898 |
295 |
23. http://thread.gmane.org/gmane.linux.gentoo.devel/39002 |
296 |
24. http://thread.gmane.org/gmane.linux.gentoo.devel/39013 |
297 |
25. http://thread.gmane.org/gmane.linux.gentoo.devel/39043 |
298 |
26. http://thread.gmane.org/gmane.linux.gentoo.devel/39166 |
299 |
27. http://thread.gmane.org/gmane.linux.gentoo.devel/39250 |
300 |
28. http://thread.gmane.org/gmane.linux.gentoo.devel/39301 |
301 |
29. http://thread.gmane.org/gmane.linux.gentoo.devel/39512 |
302 |
|
303 |
|
304 |
Defining the Tree: a proto-GLEP. |
305 |
|
306 |
Stephen Bennett[30] starts a discussion that has its roots in the |
307 |
“alternative package manager” threads of the last weeks. One issue that |
308 |
was often mentioned is the lack of a formal specification of the ebuild |
309 |
format, environment and many other small details. So Stephen intends to |
310 |
write, together with the portage team and other interested developers, a |
311 |
full specification if there is enough interest and support within the |
312 |
developer community – and, almost obviously, this idea is almost |
313 |
universally accepted as a good thing. |
314 |
|
315 |
30. spb@g.o |
316 |
|
317 |
* Defining the Tree: a proto-GLEP [31] |
318 |
31. http://thread.gmane.org/gmane.linux.gentoo.devel/39259 |
319 |
|
320 |
|
321 |
Profiles Part 2 |
322 |
|
323 |
Following on from the lengthy and at times heated discussion in the |
324 |
Paludis and Profiles[32] thread mentioned here two weeks ago, Stephen |
325 |
Bennett[33] sent a new proposal to the list to make life easier for |
326 |
alternative package managers in the tree. This version is |
327 |
package-manager-agnostic and met with a much more positive response and no |
328 |
visible opposition. As things stand, it is set to be implemented at some |
329 |
point after the 2006.1 release. |
330 |
|
331 |
32. http://thread.gmane.org/gmane.linux.gentoo.devel/38016 |
332 |
33. spb@g.o |
333 |
|
334 |
* Profiles Part 2[34] |
335 |
34. http://thread.gmane.org/gmane.linux.gentoo.devel/39249 |
336 |
|
337 |
|
338 |
GLEP 42 Revisited |
339 |
|
340 |
GLEP 42, “Critical News Reporting”, has been waiting in a sort of limbo |
341 |
since its author left the Gentoo project. However, Stephen Bennett has now |
342 |
taken over sponsorship of it, and sent it to the mailing list again. The |
343 |
GLEP seems to have fairly widespread support, and should be sent to the |
344 |
Gentoo Council for approval in the near future. |
345 |
|
346 |
* GLEP 42 (News) revisited[35] |
347 |
35. http://thread.gmane.org/gmane.linux.gentoo.devel/39258 |
348 |
|
349 |
|
350 |
GWN issues |
351 |
|
352 |
Under the slightly unintuitive title "July Council Meeting: Requested |
353 |
Agenda Item" Christel Dahlskjaer[36] starts a discussion about the state |
354 |
of the GWN. There were some issues with past GWNs, especially with the |
355 |
limited availability of Ulrich Plate[37]. As a positive side effect |
356 |
Christel and some other devs have joined the GWN and will try to help |
357 |
where they can. |
358 |
|
359 |
36. christel@g.o |
360 |
37. plate@g.o |
361 |
|
362 |
* July Council Meeting: Requested Agenda Item [38] |
363 |
38. http://thread.gmane.org/gmane.linux.gentoo.devel/39141 |
364 |
|
365 |
|
366 |
[RFC] i18n project |
367 |
|
368 |
Diego 'Flameeyes' Pettenò[39] asks for some input on one of his excellent |
369 |
ideas: An internationalization (i18n) project to make the life of our |
370 |
non-English users easier. Initial goals include translating error messages |
371 |
of Gentoo-developed applications and the respective manpages but the real |
372 |
span is yet to be defined. |
373 |
|
374 |
39. flameeyes@g.o |
375 |
|
376 |
* [RFC] i18n project [40] |
377 |
40. http://thread.gmane.org/gmane.linux.gentoo.devel/39131 |
378 |
|
379 |
|
380 |
======================= |
381 |
3. Gentoo International |
382 |
======================= |
383 |
|
384 |
Germany: FrOSCon, Bonn/Rhein-Sieg |
385 |
--------------------------------- |
386 |
|
387 |
Gentoo Developer Tobias Scherbaum[41] will give two talks at the first |
388 |
Free and Open Source Software Conference[42] taking place at the |
389 |
University of Applied Sciences Bonn-Rhein-Sieg next weekend. His first |
390 |
talk is an introduction to Gentoo where he talks about Gentoo's history, |
391 |
Gentoo's current state and further development. The second talk covers |
392 |
Gentoo's usage in business environments and demonstrates Gentoo's |
393 |
strengths, but also areas where Gentoo needs to evolve. For more details |
394 |
check the FrOSCon lectures website[43]. |
395 |
|
396 |
41. dertobi123@g.o |
397 |
42. http://www.froscon.org |
398 |
43. http://programm.froscon.org |
399 |
|
400 |
Gentoo Summer Camp 2006 |
401 |
----------------------- |
402 |
|
403 |
The second Gentoo Summer Camp will take place on 26 and 27 august on a |
404 |
campground next to the fourth largest lake in Lower Saxony called “Grosses |
405 |
Meer”. While this claims to be a Gentoo camp, the organization team around |
406 |
Forums moderator Uwe Hölzel[44] focusses mainly on social aspects. |
407 |
Playing mini-golf, having barbeque or just discovering the nature is |
408 |
preferred over hacking. For everyone who is interested in attending, the |
409 |
GSC team already set up a web page[45] which provides further information |
410 |
and a forum. |
411 |
|
412 |
44. http://forums.gentoo.org/profile.php?mode=viewprofile&u=18822 |
413 |
45. http://gsc2006.nachtnebelnelken.de/ |
414 |
|
415 |
====================== |
416 |
4. Gentoo in the press |
417 |
====================== |
418 |
|
419 |
gentoo.de: Guide to Portage 2.1 (13 June 2006) |
420 |
---------------------------------------------- |
421 |
|
422 |
The German community website gentoo.de published an article on new |
423 |
features and changed behaviour in Portage 2.1[46]. Author Tobias |
424 |
Scherbaum[47] includes an overview, but also gives practical examples on |
425 |
how these new features can be used to improve your Gentoo experience. The |
426 |
article is currently only available in German, an English translation can |
427 |
be done on short notice if some people indicate interest. |
428 |
|
429 |
46. http://www.gentoo.de/main/de/portage-2.1.xml |
430 |
47. tobias.scherbaum@×××××××××.org |
431 |
|
432 |
Rapid GUI Development with QtRuby |
433 |
--------------------------------- |
434 |
|
435 |
Gentoo Developer Caleb Tennis[48] has recently published a book called |
436 |
“Rapid GUI Development with QtRuby”. It is available as PDF on the |
437 |
Pragmatic Programmer Website[49]. While it does assume some basic working |
438 |
knowledge of Ruby it is intended to be easy to read and informative even |
439 |
for people not yet familiar with Qt. |
440 |
|
441 |
48. caleb@g.o |
442 |
49. http://pragmaticprogrammer.com/titles/ctrubyqt/index.html |
443 |
|
444 |
Although it is not Gentoo-specific all testing of programs for this book |
445 |
happened on Gentoo. The QtRuby bindings can be emerged with emerge qtruby, |
446 |
the KDE extension Korundum can also be emerged with emerge korundum, so |
447 |
Gentoo users will have it especially easy if they wish to play around with |
448 |
these programs. |
449 |
|
450 |
Caleb Tennis has been a Gentoo developer for three years now and is part |
451 |
of the Ruby, Qt and KDE herds. |
452 |
|
453 |
================== |
454 |
5. Tips and tricks |
455 |
================== |
456 |
|
457 |
Exploring portage features |
458 |
-------------------------- |
459 |
|
460 |
The new release of Portage 2.1 brings many features and improvements. |
461 |
While most of them are documented in the example make.conf and the portage |
462 |
man page they may not be obvious to most users, so we will show how to use |
463 |
some of these features. |
464 |
|
465 |
All the features have to be set in /etc/make.conf. |
466 |
|
467 |
Portage is now able to download some package's source code while compiling |
468 |
another. This can considerably reduce installation time when emerging many |
469 |
packages. There's no need to run emerge --fetchonly while doing a normal |
470 |
emerge anymore. You just have to add the following option: |
471 |
|
472 |
+-------------------------------------------------------------------------+ |
473 |
| Code Listing 5.1: | |
474 |
| Setting parallel-fetch in /etc/make.conf | |
475 |
+-------------------------------------------------------------------------+ |
476 |
| | |
477 |
|FEATURES="parallel-fetch" | |
478 |
| | |
479 |
+-------------------------------------------------------------------------+ |
480 |
|
481 |
This feature appears to be non-functional in some of the Portage 2.1 |
482 |
releases, but is expected to be fixed soon. |
483 |
|
484 |
Another new option to reduce installation time yet a bit more is |
485 |
confcache. With this new feature portage caches many of the tests |
486 |
configuration scripts do, thus making execution faster. This comes with |
487 |
the small risk of caching wrong values, so be warned that this feature is |
488 |
known to have a few bugs. Since this package is currently keyworded on |
489 |
most architectures, the required steps to enable it are: |
490 |
|
491 |
+-------------------------------------------------------------------------+ |
492 |
| Code Listing 5.2: | |
493 |
| Enabling confcache | |
494 |
+-------------------------------------------------------------------------+ |
495 |
| | |
496 |
|Add this in /etc/make.conf | |
497 |
|FEATURES="confcache" | |
498 |
|We need to unmask the package before emerging it | |
499 |
|echo "=dev-utils/confcache-0.4.2-r1 ~arch" \ | |
500 |
| >>/etc/portage/package.keywords | |
501 |
|Installing confcache | |
502 |
|emerge -av confcache | |
503 |
|On further installations. you'll see stuff like: | |
504 |
|checking for i686-pc-linux-gnu-gcc... (cached) i686-pc-linux-gnu-gcc | |
505 |
|checking whether we are using the GNU C compiler...(cached) yes | |
506 |
|checking whether i686-pc-linux-gnu-gcc accepts -g... (cached) yes | |
507 |
| | |
508 |
+-------------------------------------------------------------------------+ |
509 |
|
510 |
Another important new feature is the ability to log all the messages |
511 |
ebuilds print. Which messages to log and how to do it is configurable. For |
512 |
example, to save just the warnings and errors in a separate file for each |
513 |
package we emerge, you have to add: |
514 |
|
515 |
+-------------------------------------------------------------------------+ |
516 |
| Code Listing 5.3: | |
517 |
| Configuring logging features in /etc/make.conf | |
518 |
+-------------------------------------------------------------------------+ |
519 |
| | |
520 |
|This sets what to log | |
521 |
|PORTAGE_ELOG_CLASSES="warn error log" | |
522 |
|And this is how to do it | |
523 |
|PORTAGE_ELOG_SYSTEM="save" | |
524 |
| | |
525 |
+-------------------------------------------------------------------------+ |
526 |
|
527 |
There are many more options like sending log messages via email. Please |
528 |
check out make.conf.example for further information. |
529 |
|
530 |
========================= |
531 |
6. Gentoo developer moves |
532 |
========================= |
533 |
|
534 |
Moves |
535 |
----- |
536 |
|
537 |
The following developers recently left the Gentoo project: |
538 |
|
539 |
* Chris White* |
540 |
|
541 |
Adds |
542 |
---- |
543 |
|
544 |
The following developers recently joined the Gentoo project: |
545 |
|
546 |
* Chris White (chriswhite) (random stuff)* |
547 |
|
548 |
Changes |
549 |
------- |
550 |
|
551 |
The following developers recently changed roles within the Gentoo project: |
552 |
|
553 |
* none this week |
554 |
|
555 |
Note: Chris White resigned and then retracted his resignation. To show |
556 |
this change in status he is mentioned both as leaving and newly joining. |
557 |
|
558 |
================== |
559 |
7. Gentoo security |
560 |
================== |
561 |
|
562 |
GDM: Privilege escalation |
563 |
------------------------- |
564 |
|
565 |
An authentication error in GDM could allow users to gain elevated |
566 |
privileges. |
567 |
|
568 |
For more information, please see the GLSA Announcement[50] |
569 |
|
570 |
50. http://www.gentoo.org/security/en/glsa/glsa-200606-14.xml |
571 |
|
572 |
Asterisk: IAX2 video frame buffer overflow |
573 |
------------------------------------------ |
574 |
|
575 |
Asterisk contains a bug in the IAX2 channel driver making it vulnerable to |
576 |
the remote execution of arbitrary code. |
577 |
|
578 |
For more information, please see the GLSA Announcement[51] |
579 |
|
580 |
51. http://www.gentoo.org/security/en/glsa/glsa-200606-15.xml |
581 |
|
582 |
DokuWiki: PHP code injection |
583 |
---------------------------- |
584 |
|
585 |
A flaw in DokuWiki's spell checker allows for the execution of arbitrary |
586 |
PHP commands, even without proper authentication. |
587 |
|
588 |
For more information, please see the GLSA Announcement[52] |
589 |
|
590 |
52. http://www.gentoo.org/security/en/glsa/glsa-200606-16.xml |
591 |
|
592 |
OpenLDAP: Buffer overflow |
593 |
------------------------- |
594 |
|
595 |
The OpenLDAP replication server slurpd contains a buffer overflow that |
596 |
could result in arbitrary code execution. |
597 |
|
598 |
For more information, please see the GLSA Announcement[53] |
599 |
|
600 |
53. http://www.gentoo.org/security/en/glsa/glsa-200606-17.xml |
601 |
|
602 |
PAM-MySQL: Multiple vulnerabilities |
603 |
----------------------------------- |
604 |
|
605 |
Vulnerabilities in PAM-MySQL can lead to a Denial of Service, making it |
606 |
impossible to log into a machine. |
607 |
|
608 |
For more information, please see the GLSA Announcement[54] |
609 |
|
610 |
54. http://www.gentoo.org/security/en/glsa/glsa-200606-18.xml |
611 |
|
612 |
Sendmail: Denial of Service |
613 |
--------------------------- |
614 |
|
615 |
Faulty multipart MIME messages can cause forked Sendmail processes to |
616 |
crash. |
617 |
|
618 |
For more information, please see the GLSA Announcement[55] |
619 |
|
620 |
55. http://www.gentoo.org/security/en/glsa/glsa-200606-19.xml |
621 |
|
622 |
Typespeed: Remote execution of arbitrary code |
623 |
--------------------------------------------- |
624 |
|
625 |
A buffer overflow in the network code of Typespeed can lead to the |
626 |
execution of arbitrary code. |
627 |
|
628 |
For more information, please see the GLSA Announcement[56] |
629 |
|
630 |
56. http://www.gentoo.org/security/en/glsa/glsa-200606-20.xml |
631 |
|
632 |
Mozilla Thunderbird: Multiple vulnerabilities |
633 |
--------------------------------------------- |
634 |
|
635 |
Several vulnerabilities in Mozilla Thunderbird allow cross site scripting, |
636 |
JavaScript privilege escalation and possibly execution of arbitrary code. |
637 |
|
638 |
For more information, please see the GLSA Announcement[57] |
639 |
|
640 |
57. http://www.gentoo.org/security/en/glsa/glsa-200606-21.xml |
641 |
|
642 |
=========== |
643 |
8. Bugzilla |
644 |
=========== |
645 |
|
646 |
Summary |
647 |
------- |
648 |
|
649 |
* Statistics |
650 |
* Closed bug ranking |
651 |
* New bug rankings |
652 |
|
653 |
Statistics |
654 |
---------- |
655 |
|
656 |
The Gentoo community uses Bugzilla (bugs.gentoo.org[58]) to record and |
657 |
track bugs, notifications, suggestions and other interactions with the |
658 |
development team. Between 12 June 2006 and 19 June 2006, activity on the |
659 |
site has resulted in: |
660 |
|
661 |
58. http://bugs.gentoo.org |
662 |
|
663 |
* 710 new bugs during this period |
664 |
* 366 bugs closed or resolved during this period |
665 |
* 21 previously closed bugs were reopened this period |
666 |
|
667 |
Of the 10298 currently open bugs: 54 are labeled 'blocker', 138 are |
668 |
labeled 'critical', and 554 are labeled 'major'. |
669 |
|
670 |
Closed bug rankings |
671 |
------------------- |
672 |
|
673 |
The developers and teams who have closed the most bugs during this period |
674 |
are: |
675 |
|
676 |
* Portage team[59], with 22 closed bugs[60] |
677 |
* Gentoo KDE team[61], with 19 closed bugs[62] |
678 |
* AMD64 Project[63], with 18 closed bugs[64] |
679 |
* Gentoo Security[65], with 16 closed bugs[66] |
680 |
* Gentoo Games[67], with 14 closed bugs[68] |
681 |
* Xavier Neys[69], with 13 closed bugs[70] |
682 |
* Gentoo Linux Gnome Desktop Team[71], with 13 closed bugs[72] |
683 |
* Gentoo's Team for Core System packages[73], with 10 closed bugs[74] |
684 |
59. dev-portage@g.o |
685 |
60. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=dev-portage@g.o |
686 |
61. kde@g.o |
687 |
62. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=kde@g.o |
688 |
63. amd64@g.o |
689 |
64. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=amd64@g.o |
690 |
65. security@g.o |
691 |
66. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=security@g.o |
692 |
67. games@g.o |
693 |
68. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=games@g.o |
694 |
69. neysx@g.o |
695 |
70. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=neysx@g.o |
696 |
71. gnome@g.o |
697 |
72. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=gnome@g.o |
698 |
73. base-system@g.o |
699 |
74. http://bugs.gentoo.org/buglist.cgi?bug_status=RESOLVED&bug_status=CLOSED&chfield=bug_status&chfieldfrom=2006-06-12&chfieldto=2006-06-19&resolution=FIXED&assigned_to=base-system@g.o |
700 |
|
701 |
|
702 |
New bug rankings |
703 |
---------------- |
704 |
|
705 |
The developers and teams who have been assigned the most new bugs during |
706 |
this period are: |
707 |
|
708 |
* Default Assignee for New Packages[75], with 35 new bugs[76] |
709 |
* Default Assignee for Orphaned Packages[77], with 22 new bugs[78] |
710 |
* Gentoo's Team for Core System packages[79], with 9 new bugs[80] |
711 |
* Jon Hood[81], with 8 new bugs[82] |
712 |
* Gentoo Sound Team[83], with 8 new bugs[84] |
713 |
* Gentoo Games[85], with 7 new bugs[86] |
714 |
* Gentoo Science Related Packages[87], with 6 new bugs[88] |
715 |
* Netmon Herd[89], with 6 new bugs[90] |
716 |
75. maintainer-wanted@g.o |
717 |
76. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=maintainer-wanted@g.o |
718 |
77. maintainer-needed@g.o |
719 |
78. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=maintainer-needed@g.o |
720 |
79. base-system@g.o |
721 |
80. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=base-system@g.o |
722 |
81. squinky86@g.o |
723 |
82. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=squinky86@g.o |
724 |
83. sound@g.o |
725 |
84. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=sound@g.o |
726 |
85. games@g.o |
727 |
86. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=games@g.o |
728 |
87. sci@g.o |
729 |
88. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=sci@g.o |
730 |
89. netmon@g.o |
731 |
90. http://bugs.gentoo.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&chfield=assigned_to&chfieldfrom=2006-06-12&chfieldto=2006-06-19&assigned_to=netmon@g.o |
732 |
|
733 |
|
734 |
=============== |
735 |
9. GWN feedback |
736 |
=============== |
737 |
|
738 |
Please send us your feedback[91] and help make the GWN better. |
739 |
|
740 |
91. gwn-feedback@g.o |
741 |
|
742 |
================================ |
743 |
10. GWN subscription information |
744 |
================================ |
745 |
|
746 |
To subscribe to the Gentoo Weekly Newsletter, send a blank e-mail to |
747 |
gentoo-gwn+subscribe@g.o. |
748 |
|
749 |
To unsubscribe to the Gentoo Weekly Newsletter, send a blank e-mail to |
750 |
gentoo-gwn+unsubscribe@g.o from the e-mail address you are |
751 |
subscribed under. |
752 |
|
753 |
=================== |
754 |
11. Other languages |
755 |
=================== |
756 |
|
757 |
The Gentoo Weekly Newsletter is also available in the following languages: |
758 |
|
759 |
* Danish[92] |
760 |
* Dutch[93] |
761 |
* English[94] |
762 |
* German[95] |
763 |
* French[96] |
764 |
* Korean[97] |
765 |
* Japanese[98] |
766 |
* Italian[99] |
767 |
* Polish[100] |
768 |
* Portuguese (Brazil)[101] |
769 |
* Portuguese (Portugal)[102] |
770 |
* Russian[103] |
771 |
* Spanish[104] |
772 |
* Turkish[105] |
773 |
92. http://www.gentoo.org/news/da/gwn/gwn.xml |
774 |
93. http://www.gentoo.org/news/nl/gwn/gwn.xml |
775 |
94. http://www.gentoo.org/news/en/gwn/gwn.xml |
776 |
95. http://www.gentoo.org/news/de/gwn/gwn.xml |
777 |
96. http://www.gentoo.org/news/fr/gwn/gwn.xml |
778 |
97. http://www.gentoo.org/news/ko/gwn/gwn.xml |
779 |
98. http://www.gentoo.org/news/ja/gwn/gwn.xml |
780 |
99. http://www.gentoo.org/news/it/gwn/gwn.xml |
781 |
100. http://www.gentoo.org/news/pl/gwn/gwn.xml |
782 |
101. http://www.gentoo.org/news/pt_br/gwn/gwn.xml |
783 |
102. http://www.gentoo.org/news/pt/gwn/gwn.xml |
784 |
103. http://www.gentoo.org/news/ru/gwn/gwn.xml |
785 |
104. http://www.gentoo.org/news/es/gwn/gwn.xml |
786 |
105. http://www.gentoo.org/news/tr/gwn/gwn.xml |
787 |
|
788 |
|
789 |
Ulrich Plate <plate@g.o> - Editor |
790 |
Patrick Lauer <patrick@g.o> - Author |
791 |
Christel Dahlskjaer <christel@g.o> - Author |
792 |
Tobias Scherbaum <dertobi123@g.o> - Author |
793 |
Mark Kowarsky <mark_alec@g.o> - Author |
794 |
Markus Ullmann <jokey@g.o> - Author |
795 |
Steve Dibb <beandog@g.o> - Author |
796 |
Lucas Chiesa <lucas.chiesa@×××××.com> - Author |
797 |
Lars Weiler <pylon@g.o> - Author |
798 |
|
799 |
-- |
800 |
gentoo-gwn@g.o mailing list |