[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#752316: marked as done (migration/testing.pl: canm not handle maltiarch package name with :any)

Your message dated Mon, 25 Feb 2019 20:49:00 +0000
with message-id <a6be09b3-83db-b3fa-ffef-b73f60892b9a@thykier.net>
and subject line Re: testing.pl: needs rewriting
has caused the Debian Bug report #658937,
regarding migration/testing.pl: canm not handle maltiarch package name with :any
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
658937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658937
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: normal

https://release.debian.org/migration/testing.pl?package=ibus currently
have:

| Why is package X not in testing yet?
| 
| Checking ibus
| 
| trying to update ibus from 1.5.6-4 to 1.5.7-1 (candidate is 1 days old)
| ibus is only 1 days old. It must be 5 days old to go in.
| Dependency analysis (including build-depends; i386 only):
| 
| ibus depends on python3:any >= 3.3.2-2~, which is not available in
| testing
| python3:any is not available in Debian


We have 3.4.1-1 for python3-defaults providing python3.

So above analysis is wrong.

I think $pkg needs to be sanitized before using it in testing.pl.

Tailing :any should be removed.

--- End Message ---
--- Begin Message --- 
On Mon, 06 Feb 2012 20:58:01 +0000 "Adam D. Barratt"
<adam@adam-barratt.org.uk> wrote:
> Package: release.debian.org
> Severity: important
> User: release.debian.org@packages.debian.org
> Usertag: tools
> 
> migration/testing.pl needs to be updated to make it react better when
> called repeatedly, or to avoid the need to do so.  Right now it's
> sufficiently resource hungry to make a 16-core machine unhappy.
> 
> An initial idea might be to statically generate package pages, although
> this would need to be benchmarked for feasibility.  testing.pl could
> then simply become a redirect to /package/blah or similar.
> 
> 
> 
> 

I am closing this old bug against the testing.pl script as it has been
decommissioned for a few years now and will not return.

Thanks,
~Niels

--- End Message ---
Reply to: