Proposing yada for removal
yada was recently orphaned: http://bugs.debian.org/636735 - I would like to propose it for removal. I believe it is unlikely to find a maintainer. There is a serious bug affecting all packages built using yada - yada modifies the build-dependencies of the package during each build. This will require some investment to fix, as it requires changing how/when control files are regenerated: http://bugs.debian.org/334164 14 packages Build-Depend on yada in unstable. Other packages can perform the same role as yada, notably debhelper and cdbs. Popcon is low - 121 installs, with a vote of just 21, and 98 old installs: http://qa.debian.org/popcon.php?package=yada Since it is a native package, the fact that it is orphaned means that there is currently no active development. Kind regards, -- Tim Retout -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADc0ge844TCr2sz+W9mw8ZCJmUWDBj2YVFATUvfx=effpaa...@mail.gmail.com
Re: Proposing yada for removal
On 6 August 2011 17:26, Luk Claes wrote: > On 08/06/2011 05:53 PM, Tim Retout wrote: >> There is a serious bug affecting all packages built using yada - yada >> modifies the build-dependencies of the package during each build. >> This will require some investment to fix, as it requires changing >> how/when control files are regenerated: >> http://bugs.debian.org/334164 >> >> 14 packages Build-Depend on yada in unstable. > > I guess these 14 RC bugs should be filed? Mmm, I've sent them off. Here they are: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=remove-yada;users=dioc...@debian.org -- Tim Retout -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADc0ge9OgBiH0_UNYJRoyZsh0r2=trcfw+mqzwv9u3hesqy...@mail.gmail.com
[PATCH] Add ruby-debian to list of required Ruby packages.
--- Hi! Here's a trivial fix to the UDD hacking.html doc. Kind regards, Tim web/hacking.html |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/web/hacking.html b/web/hacking.html index f72bbcf..b5d55f4 100755 --- a/web/hacking.html +++ b/web/hacking.html @@ -101,7 +101,7 @@ dropdb udd apt-get install apache2-mpm-worker # install some Ruby packages, needed for dmd.cgi -apt-get install ruby-dbi ruby-dbd-pg +apt-get install ruby-dbi ruby-dbd-pg ruby-debian # minimal configuration that works: - edit /etc/apache2/sites-enabled/000-default -- 1.7.10 -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1341857440-5866-1-git-send-email-dioc...@debian.org
[PATCH 1/2] dmd.cgi: Sort testing-only RC bugs after unstable RC bugs.
---
web/inc/dmd-data.rb |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/web/inc/dmd-data.rb b/web/inc/dmd-data.rb
index d777d23..3efd1c1 100755
--- a/web/inc/dmd-data.rb
+++ b/web/inc/dmd-data.rb
@@ -221,6 +221,7 @@ and source not in (select source from upload_history where
date > (current_date
def get_dmd_todos
@dmd_todos = []
rc_bugs = @all_bugs.select { |b| ['serious', 'grave',
'critical'].include?(b['severity']) }
+testing_rc_bugs = []
stable_rc_bugs = []
rc_bugs.each do |bug|
id = bug['id']
@@ -228,8 +229,8 @@ and source not in (select source from upload_history where
date > (current_date
@dmd_todos << { :type => 'RC bug', :source => bug['source'],
:description => "RC bug marked as done but still affects unstable:
http://bugs.debian.org/#{id}\";>##{id}: #{bug['title']}" }
elsif (not @bugs_tags[id].include?('rt_affects_unstable')) and
@bugs_tags[id].include?('rt_affects_testing')
-@dmd_todos << { :type => 'RC bug', :source => bug['source'],
-:description => "RC bug affecting testing only (ensure
the package migrates): http://bugs.debian.org/#{id}\";>##{id}:
#{bug['title']}" }
+testing_rc_bugs << { :type => 'RC bug', :source => bug['source'],
+ :description => "RC bug affecting testing only
(ensure the package migrates): http://bugs.debian.org/#{id}\";>##{id}: #{bug['title']}" }
elsif @bugs_tags[id].include?('rt_affects_unstable') or
@bugs_tags[id].include?('rt_affects_testing')
@dmd_todos << { :type => 'RC bug', :source => bug['source'],
:description => "RC bug needs fixing: http://bugs.debian.org/#{id}\";>##{id}: #{bug['title']}" }
@@ -238,6 +239,7 @@ and source not in (select source from upload_history where
date > (current_date
:description => "RC bug affecting stable: http://bugs.debian.org/#{id}\";>##{id}: #{bug['title']}" }
end
end
+@dmd_todos.concat(testing_rc_bugs)
@dmd_todos.concat(stable_rc_bugs)
@buildd.each_pair do |src, archs|
--
1.7.10
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1342206104-27390-1-git-send-email-dioc...@debian.org
[PATCH 2/2] dmd.cgi: Show only packages with this maintainer in sid or experimental.
When a package is adopted by another person or team, the original
maintainer will not want to see issues regarding that package. However,
the Maintainer field will not be updated in stable or testing. Avoid
showing those packages with the old address.
---
web/inc/dmd-data.rb |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/web/inc/dmd-data.rb b/web/inc/dmd-data.rb
index 3efd1c1..0ca714f 100755
--- a/web/inc/dmd-data.rb
+++ b/web/inc/dmd-data.rb
@@ -40,7 +40,7 @@ class UDDData
maint_emails = @emails.reject { |k, v| not v.include?(:maintainer) }.keys
if not maint_emails.empty?
q = <<-EOF
-select distinct source, maintainer_email from sources_uniq where release
in ('sid', 'experimental', 'wheezy', 'squeeze') and maintainer_email in
(#{maint_emails.map { |e| quote(e) }.join(',')})
+select distinct source, maintainer_email from sources_uniq where release
in ('sid', 'experimental') and maintainer_email in (#{maint_emails.map { |e|
quote(e) }.join(',')})
EOF
maint_rows = dbget(q)
else
@@ -50,7 +50,7 @@ class UDDData
upload_emails = @emails.reject { |k, v| not v.include?(:uploader) }.keys
if not upload_emails.empty?
q = <<-EOF
-select distinct source, email from uploaders where release in ('sid',
'experimental', 'wheezy', 'squeeze') and email in (#{upload_emails.map { |e|
quote(e) }.join(',')})
+select distinct source, email from uploaders where release in ('sid',
'experimental') and email in (#{upload_emails.map { |e| quote(e) }.join(',')})
EOF
upload_rows = dbget(q)
else
--
1.7.10
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1342206104-27390-2-git-send-email-dioc...@debian.org
Re: [PATCH 2/2] dmd.cgi: Show only packages with this maintainer in sid or experimental.
On 14 July 2012 00:50, Lucas Nussbaum wrote: > Note that it is not clear if it is really the responsibility of the new > maintainer to take care of stable bugs. Mmm; although I'm not sure what the consensus is on this, I think it is reasonable that the 'sid' version of Maintainer takes precedence. The BTS will send stable bugs to the new maintainer, rather than the one in stable. > Also, in the case of a removed package > that is still in stable, it is clearly the responsibility of the 'stable > maintainer' to take care of issues. > > I would rather have a checkbox (disabled by default) that would say "also > include all related source packages, not just those maintained in sid > and experimental". My preference would be to avoid as many checkboxes as possible. Yes, there are some edge cases, but I thought this patch might help flush them out. ;) (I wonder what should happen when a package changes maintainer, but then gets removed from unstable? Not very common.) Another interesting set of packages would be NMUs, where the uploader is responsible for any issues caused by the NMU. -- Tim Retout -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cadc0ge--73equjgdbwrytz9rfz-0u1fczfptkjvfehnjszb...@mail.gmail.com
Re: [PATCH 2/2] dmd.cgi: Show only packages with this maintainer in sid or experimental.
On 15 July 2012 14:48, Lucas Nussbaum wrote:
> OK, I agree with avoiding checkboxes if possible. To address (I think)
> all cases, I've changed the logic so that an email is associated with
> a package if, either:
> - it (co-)maintains the most recent version of the package is squeeze,
>wheezy or sid
> - or it (co-)maintains the package in experimental
> (there were some cases where a different maintainer was maintaining
> coreutils in experimental some time ago, in that case both maintainers
> should be associated with the package.)
Cool, this does sound right. Thanks. :)
>> Another interesting set of packages would be NMUs, where the uploader
>> is responsible for any issues caused by the NMU.
>
> Indeed, that would require selection of packages based on uploading key.
> It's already in the TODO list ;)
So far I was assuming this would use the changed_by field to work out
who prepared the nmudiff. The uploading key would tell you who
sponsored the NMU, and I suppose you could argue that the sponsor is
also responsible for any bugs...? This is my SQL from a
work-in-progress patch, for what it's worth:
select s.source, u.changed_by_email
from upload_history u
join sources s
on u.source = s.source
and u.version = s.version
where u.nmu = 't'
and s.release = 'sid'
and s.distribution = 'debian'
and u.changed_by_email in (#{nmu_emails.map { |e| quote(e) }.join(',')})
Of course, uploading key is necessary to list sponsored packages in a
similar manner to DDPO, but I can see that being tricky, since the
main GPG id might not match the maintainer email address...
--
Tim Retout
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CADc0ge8eF=UaTTm6RW0x222arWcfqG5yS8maRnz09mg==8x...@mail.gmail.com
[PATCH] dmd.cgi: Add general RC bug fixing to the maintainer TODO list.
If a maintainer doesn't have any RC bugs of their own to fix, then
they might want to contribute to the general release. Nudge them
in the direction of the bug list.
---
web/inc/dmd-data.rb | 24
1 file changed, 24 insertions(+)
diff --git a/web/inc/dmd-data.rb b/web/inc/dmd-data.rb
index f6c2c2d..d2fbde4 100755
--- a/web/inc/dmd-data.rb
+++ b/web/inc/dmd-data.rb
@@ -245,6 +245,22 @@ and source not in (select source from upload_history where
date > (current_date
get_buildd
end
+ def get_rc_bug_count
+q =<<-EOF
+select count(*) from bugs
+where severity >= 'serious'
+and id in (select id from bugs_rt_affects_testing)
+and id not in (select id from bugs_merged_with where id > merged_with)
+EOF
+rows = dbget(q)
+if rows
+ count = rows[0][0]
+else
+ count = 0
+end
+return count
+ end
+
def get_dmd_todos
@dmd_todos = []
rc_bugs = @all_bugs.select { |b| ['serious', 'grave',
'critical'].include?(b['severity']) }
@@ -269,6 +285,14 @@ and source not in (select source from upload_history where
date > (current_date
@dmd_todos.concat(testing_rc_bugs)
@dmd_todos.concat(stable_rc_bugs)
+if @dmd_todos.empty?
+ count = get_rc_bug_count
+ if count != 0
+@dmd_todos << { :type => 'RC bugs', :source => '',
+:description => "Fix one of http://udd.debian.org/bugs.cgi?release=wheezy&merged=ign&rc=1\";>the
#{count} RC bugs affecting the next release." }
+ end
+end
+
@buildd.each_pair do |src, archs|
archs.each do |arch|
@dmd_todos << { :type => 'missing build', :source => src,
--
1.7.10
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/1342730760-20549-1-git-send-email-dioc...@debian.org
