Search Results: "tolimar"

28 May 2013

Christian Perrier: Bug #710000

Alexander Reichle-Schmehl created Debian bug #710000 on Monday May 27th 2013, against the ftp.debian.org pseudo-package, by cloning a bug report by Rene Engelhard. So, technically speaking, Rene reported this bug....but Tolimar is responsible for that. Bug #700000 was reported as of February 7th: 3 months and 20 days for 10,000 bugs. This is again a VERY significant drop in the bug reporting rate in Debian. Is that related to the release of jessie? We'll see that in the upcoming 4 months.

12 March 2013

Alexander Reichle-Schmehl: A pledge about a certain Debian mailing list

I hereby pledge, that for every mail I send into a thread on the private Debian list with more than 10 mails, I will fix a release critical bug in a foreign package.

30 June 2012

Luca Falavigna: FTP Team stats during Wheezy development

Already chilled by Wheezy freeze? It s been a long ride since the release of Squeeze, and your beloved FTP Team tried to assist our tireless developers and contributors at its best. Here are some hot stats to give you a figure about what happened behind the scenes. Since the release of Squeeze, 7462 .changes files with NEW components were processed by dak, with an average of 14.660 NEW packages per day. On the FTP Team side, we had 6877 accepts (13.511 per day), 641 rejects (1.259 per day) and 280 comments to maintainers (0.550 per day). This table represents the activity by single team member:
Login Accepts Rejects Comments
ansgar 407 accepts (0.800 per day) 71 rejects (0.139 per day) 53 comments (0.104 per day)
dak 12 accepts (0.024 per day) 1 rejects (0.002 per day) 0 comments (0.000 per day)
dktrkranz 4319 accepts (8.485 per day) 381 rejects (0.749 per day) 104 comments (0.204 per day)
joerg 100 accepts (0.196 per day) 12 rejects (0.024 per day) 1 comments (0.002 per day)
mhy 214 accepts (0.420 per day) 14 rejects (0.028 per day) 5 comments (0.010 per day)
stew 67 accepts (0.132 per day) 16 rejects (0.031 per day) 7 comments (0.014 per day)
tolimar 1480 accepts (2.908 per day) 93 rejects (0.183 per day) 84 comments (0.165 per day)
twerner 278 accepts (0.546 per day) 53 rejects (0.104 per day) 26 comments (0.051 per day)


Who were the most prolific maintainers who got a NEW processing? Here is our special top ten:
  1. Debian Perl Group (559 accepts)
  2. Debian Haskell Group (491 accepts)
  3. Debian Ruby Extras Maintainers (285 accepts)
  4. Debian Java Maintainers (257 accepts)
  5. Debian Med Packaging Team (164 accepts)
  6. Debian Multimedia Maintainers (160 accepts)
  7. Debian Fonts Task Force (156 accepts)
  8. Debian Javascript Maintainers (137 accepts)
  9. Debian Python Modules Team (129 accepts)
  10. Debian Qt/KDE Maintainers (98 accepts)
That doesn t reflect the real developers, though. Here s our Changed-By top ten:
  1. Clint Adams (216 accepts)
  2. Jonas Smedegaard (208 accepts)
  3. Ben Hutchings (203 accepts)
  4. Joachim Breitner (153 accepts)
  5. TANIGUCHI Takaki (112 accepts)
  6. Alessio Treglia (101 accepts)
  7. David Paleino (95 accepts)
  8. Nicholas Bamber (76 accepts)
  9. Mathieu Parent (68 accepts)
  10. Jeff Breidenbach (63 accepts)
Clint rocks with tons of Haskell packages, followed by Jonas (mostly Perl packages), and Ben (kernel uploads). Italian cabal stands still, with Alessio and David respectively at 6th and 7th place ;)


How long does a package stay in NEW? Some more, some less, but the average is 3 days, 15 minutes and 21 seconds. Now go and check your dak mails to see whether you had a fast processing or not :) liblog4ada 1.2-1 surely had, as it was accepted after 30 seconds! gsoap 2.7.17-1 was not so lucky, it took 103 days, 8 hours, 20 minutes and 43 seconds to clear NEW, but then made its way to the archive. Better late than never ;)


FTP Team is not just accepting NEW packages, but also removing obsolete ones. Here are some details about this task:

FTP Team also took care of override changes:

29 June 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 26

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1088
Affecting Wheezy:697
Wheezy only:128
Remaining to be fixed in Wheezy:569
Of these 569 bugs, the following tags are set:
Pending in Wheezy:21
Patched in Wheezy:77
Duplicates in Wheezy:57
Can be fixed in a security Update:22
Contrib or non-free in Wheezy:8
Claimed in Wheezy:1
Delayed in Wheezy:2
Otherwise fixed in Wheezy:44
Ignoring all the above (multiple tags possible) 375 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 603 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

22 June 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 25

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1167
Affecting Wheezy:771
Wheezy only:189
Remaining to be fixed in Wheezy:582
Of these 582 bugs, the following tags are set:
Pending in Wheezy:31
Patched in Wheezy:82
Duplicates in Wheezy:57
Can be fixed in a security Update:21
Contrib or non-free in Wheezy:11
Claimed in Wheezy:2
Delayed in Wheezy:5
Otherwise fixed in Wheezy:47
Ignoring all the above (multiple tags possible) 376 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 671 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

15 June 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 24

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1289
Affecting Wheezy:862
Wheezy only:180
Remaining to be fixed in Wheezy:682
Of these 682 bugs, the following tags are set:
Pending in Wheezy:37
Patched in Wheezy:86
Duplicates in Wheezy:57
Can be fixed in a security Update:22
Contrib or non-free in Wheezy:10
Claimed in Wheezy:2
Delayed in Wheezy:2
Otherwise fixed in Wheezy:41
Ignoring all the above (multiple tags possible) 466 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 757 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

8 June 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 23

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1422
Affecting Wheezy:978
Wheezy only:244
Remaining to be fixed in Wheezy:734
Of these 734 bugs, the following tags are set:
Pending in Wheezy:39
Patched in Wheezy:93
Duplicates in Wheezy:63
Can be fixed in a security Update:18
Contrib or non-free in Wheezy:11
Claimed in Wheezy:2
Delayed in Wheezy:7
Otherwise fixed in Wheezy:69
Ignoring all the above (multiple tags possible) 496 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 874 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

1 June 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 22

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1412
Affecting Wheezy:977
Wheezy only:272
Remaining to be fixed in Wheezy:705
Of these 705 bugs, the following tags are set:
Pending in Wheezy:51
Patched in Wheezy:118
Duplicates in Wheezy:57
Can be fixed in a security Update:24
Contrib or non-free in Wheezy:9
Claimed in Wheezy:2
Delayed in Wheezy:4
Otherwise fixed in Wheezy:99
Ignoring all the above (multiple tags possible) 427 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 867 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

25 May 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 21

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1534
Affecting Wheezy:1095
Wheezy only:238
Remaining to be fixed in Wheezy:857
Of these 857 bugs, the following tags are set:
Pending in Wheezy:82
Patched in Wheezy:175
Duplicates in Wheezy:62
Can be fixed in a security Update:27
Contrib or non-free in Wheezy:11
Claimed in Wheezy:2
Delayed in Wheezy:18
Otherwise fixed in Wheezy:86
Ignoring all the above (multiple tags possible) 500 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 975 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

18 May 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 20

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1515
Affecting Wheezy:1078
Wheezy only:235
Remaining to be fixed in Wheezy:843
Of these 843 bugs, the following tags are set:
Pending in Wheezy:70
Patched in Wheezy:169
Duplicates in Wheezy:62
Can be fixed in a security Update:23
Contrib or non-free in Wheezy:12
Claimed in Wheezy:2
Delayed in Wheezy:12
Otherwise fixed in Wheezy:71
Ignoring all the above (multiple tags possible) 504 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 968 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

11 May 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 19

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1609
Affecting Wheezy:1136
Wheezy only:206
Remaining to be fixed in Wheezy:930
Of these 930 bugs, the following tags are set:
Pending in Wheezy:83
Patched in Wheezy:208
Duplicates in Wheezy:46
Can be fixed in a security Update:27
Contrib or non-free in Wheezy:12
Claimed in Wheezy:2
Delayed in Wheezy:31
Otherwise fixed in Wheezy:61
Ignoring all the above (multiple tags possible) 556 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 1025 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

10 February 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 06

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1340
Affecting Wheezy:777
Wheezy only:122
Remaining to be fixed in Wheezy:655
Of these 655 bugs, the following tags are set:
Pending in Wheezy:41
Patched in Wheezy:86
Duplicates in Wheezy:45
Can be fixed in a security Update:21
Contrib or non-free in Wheezy:16
Claimed in Wheezy:0
Delayed in Wheezy:6
Otherwise fixed in Wheezy:49
Ignoring all the above (multiple tags possible) 447 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 687 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

Alexander Reichle-Schmehl: Release Critical Bug report for Week 06

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1340
Affecting Wheezy:777
Wheezy only:122
Remaining to be fixed in Wheezy:655
Of these 655 bugs, the following tags are set:
Pending in Wheezy:41
Patched in Wheezy:86
Duplicates in Wheezy:45
Can be fixed in a security Update:21
Contrib or non-free in Wheezy:16
Claimed in Wheezy:0
Delayed in Wheezy:6
Otherwise fixed in Wheezy:49
Ignoring all the above (multiple tags possible) 447 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 687 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

3 February 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 05

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1447
Affecting Wheezy:865
Wheezy only:170
Remaining to be fixed in Wheezy:695
Of these 695 bugs, the following tags are set:
Pending in Wheezy:46
Patched in Wheezy:91
Duplicates in Wheezy:42
Can be fixed in a security Update:18
Contrib or non-free in Wheezy:15
Claimed in Wheezy:0
Delayed in Wheezy:8
Otherwise fixed in Wheezy:44
Ignoring all the above (multiple tags possible) 482 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 767 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

1 February 2012

Alexander Reichle-Schmehl: Making myself a birthday present

For my yesterdays birthday I made me a really special birthday present. Nothing technical: I handed in my application for parental leave :) I'm quite happy :)

27 January 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 04

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1491
Affecting Wheezy:893
Wheezy only:179
Remaining to be fixed in Wheezy:714
Of these 714 bugs, the following tags are set:
Pending in Wheezy:48
Patched in Wheezy:102
Duplicates in Wheezy:45
Can be fixed in a security Update:19
Contrib or non-free in Wheezy:14
Claimed in Wheezy:0
Delayed in Wheezy:5
Otherwise fixed in Wheezy:48
Ignoring all the above (multiple tags possible) 491 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 788 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

20 January 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 03

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1563
Affecting Wheezy:928
Wheezy only:192
Remaining to be fixed in Wheezy:736
Of these 736 bugs, the following tags are set:
Pending in Wheezy:51
Patched in Wheezy:116
Duplicates in Wheezy:46
Can be fixed in a security Update:22
Contrib or non-free in Wheezy:12
Claimed in Wheezy:0
Delayed in Wheezy:3
Otherwise fixed in Wheezy:41
Ignoring all the above (multiple tags possible) 495 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 827 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

13 January 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 02

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1537
Affecting Wheezy:900
Wheezy only:188
Remaining to be fixed in Wheezy:712
Of these 712 bugs, the following tags are set:
Pending in Wheezy:48
Patched in Wheezy:111
Duplicates in Wheezy:45
Can be fixed in a security Update:24
Contrib or non-free in Wheezy:11
Claimed in Wheezy:0
Delayed in Wheezy:2
Otherwise fixed in Wheezy:46
Ignoring all the above (multiple tags possible) 477 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 799 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

6 January 2012

Alexander Reichle-Schmehl: Release Critical Bug report for Week 01

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1614
Affecting Wheezy:945
Wheezy only:148
Remaining to be fixed in Wheezy:797
Of these 797 bugs, the following tags are set:
Pending in Wheezy:47
Patched in Wheezy:135
Duplicates in Wheezy:45
Can be fixed in a security Update:28
Contrib or non-free in Wheezy:10
Claimed in Wheezy:0
Delayed in Wheezy:6
Otherwise fixed in Wheezy:50
Ignoring all the above (multiple tags possible) 532 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 845 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

30 December 2011

Alexander Reichle-Schmehl: Release Critical Bug report for Week 52

The bug webinterface of the Ultimate Debian Database currently knows about the following release critical bugs:
In Total:1586
Affecting Wheezy:960
Wheezy only:163
Remaining to be fixed in Wheezy:797
Of these 797 bugs, the following tags are set:
Pending in Wheezy:49
Patched in Wheezy:117
Duplicates in Wheezy:50
Can be fixed in a security Update:26
Contrib or non-free in Wheezy:9
Claimed in Wheezy:0
Delayed in Wheezy:8
Otherwise fixed in Wheezy:49
Ignoring all the above (multiple tags possible) 552 bugs need to be fixed by Debian Contributors to get Debian 7.0 Wheezy released. However, with the view of the Release Managers, 862 need to be dealt with for the release to happen. Please see Interpreting the release critical bug statistics for an explanation of the different numbers.

Next.