Control: fixed -1 3.8-1
On 2/26/25 10:20, Russell Coker wrote:
https://qa.debian.org/excuses.php?package=libsemanage
It says that libsemanage is not migrating due to bug #1091109.
That bug never affected version 3.8 as the issue was addressed upstream. I
accidentally dropped the changelog ent
Package: qa.debian.org
Severity: wishlist
Hi,
would it be possible to color-code the Excuses links based on the
migration status? I'd think about
* green -> "Will attempt migration"
* red -> "BLOCKED"
* (default) -> "check later"
Maybe the "red" flag could further be distinguished between "inher
Package: qa.debian.org
Severity: normal
This does not seem to be a transient error:
Error: remote: warning: unable to find all commit-graph files
https://qa.debian.org/cgi-bin/vcswatch?package=acpi-call
https://qa.debian.org/cgi-bin/vcswatch?package=nvidia-support
Andreas
Hi,
This does not seem to be related to piuparts at all. AFAIK we don't run
piuparts on !amd64.
On 03/12/2023 15.44, Markus Koschany wrote:
maybe someone on this list can point me in the right direction. The package
src:spring doesn't migrate to testing because "spring-javaai/arm64 has
unsati
Package: qa.debian.org
Severity: important
User: qa.debian@packages.debian.org
Usertags: udd
X-Debbugs-Cc: Cyril Brulebois
The list of RC bugs in sid
https://udd.debian.org/bugs.cgi?release=sid&merged=ign&fnewerval=7&flastmodval=7&rc=1&sortby=id&sorto=desc&format=html#results
does not contain
On 24/10/2023 23.52, Carles Pina i Estany wrote:
New user of debian/watch and I cannot see why it reports failure in a
qa.debian.org but I cannot reproduce it.
status: error
warnings: In debian/watch no matching files for watch line
https://github.com/kyan001/ping3/tags
https://github.co
On 07/02/2023 12.12, Andreas Beckmann wrote:
I recently moved bin:firmware-nvidia-gsp from
src:nvidia-graphics-drivers from the non-free archive area to the new
non-free-firmware archive area. As a result src:nvidia-graphics-drivers
is now considered to be in non-free-firmware, too. Second
On 17/07/2023 07.16, Helmut Grohne wrote:
Then I found trei...@debian.org using edos-file-overwrite. That latter
one seems like what I need here. Should we move it to the qa space and
drop the edos part? I suggest debian-qa@lists.debian.org usertags
file-overwrite. Otherwise, Ralf are you ok wit
On 06/06/2023 21.19, cardinale.salvo55 wrote:
Can this be helpfull in building a working package for bullseye?
bullseye-pu request: https://bugs.debian.org/1037187
Andreas
On 07/05/2023 08.44, Paul Wise wrote:
I noticed that someone added the piuparts usertag to a whole bunch of
bugs of many different ages and that many of those bugs are FTBFS bugs.
These are intentional. There are usually also Affects on some binary
packages built from that source. The FTBFS ma
Package: tracker.debian.org
Severity: normal
Hi,
while cleaning up bugs remaining orphaned after the archival of jessie,
I noticed that tracker.d.o sometimes displays incorrect release
information in the "versions" box, e.g.
https://tracker.debian.org/pkg/fedmsg-meta-debian
That package was las
On 18/04/2023 20.30, Patrice Duroux wrote:
Hi,
After considering https://piuparts.debian.org/sid/fail/mrtg_2.17.10-4+b1.log
and reporting #1034530, I would like to be sure that another case
like: https://piuparts.debian.org/sid/pass/pipewire_0.3.65-3.log is
more tricky due to that pipewire may
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: Cyril Brulebois
I recently moved bin:firmware-nvidia-gsp from
src:nvidia-graphics-drivers from the non-free archive area to the new
non-free-firmware archive area. As a result src:nvidia-graphics-drivers
is now considered to be in non-free-fir
On 07/02/2023 09.41, Raphael Hertzog wrote:
But with >3 source packages to monitor, we're not able to verify new
releases each hour. It's a process that is spread over a longer period...
I don't know if this is already done, but from historic release data it
might be possible to derive pac
On 05/06/2022 20.25, Paul Gevers wrote:
> However, this looks like the path where the issue lies.
> bin:nvidia-kernel-dkms (non-free, built from src:nvidia-graphics-drivers
> in non-free) Depends (on amd64 only) on nvidia-firmware-470.103.01 which
> is Provided by bin:nvidia-kernel-support (built
Package: qa.debian.org
Severity: normal
Hi,
some parts of the pages generated by the (old) PTS no longer get
updated:
E.g. https://packages.qa.debian.org/s/spirv-llvm-translator-12.html
(a relatively new package)
* 'versions' box: only lists the version in unstable, not the one in
testing
* 'b
Package: qa.debian.org
Severity: normal
Hi,
DDPO currently uses the "No Entry" sign with read background ⛔ (U+26D4)
for the "neutral" CI state. I find this more eye-catching than the "fail"
state (which uses the word "fail" in red).
The CI pages itself use the "No Entry" sign with a blue backgrou
I still find very odd that
$ dak rm -Rn python-setuptools-scm
doesn't find anything though. dak is obviously aware of the package...
You missed -b for binary packages:
$ dak rm -Rn -b python-setuptools-scm
Will remove the following packages from unstable:
python-setuptools-scm |4.1
Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Usertags: udd
Hi,
in the list of all RC bugs in oldstable:
https://udd.debian.org/bugs/?release=stretch&merged=ign&fnewerval=7&flastmodval=7&rc=1&chints=1&ctags=1&caffected=1&crttags=1&sortby=last_modified&sorto=desc&
On 27/04/2020 19.55, peter green wrote:
> 1. What should the policy be on handling virtual packages? it seems to
> me that virtual packages with only a single provider should be treated
> much the same as real packages but what about those with multiple
> providers? ignore them? pick one according
On 2019-01-14 19:53, Lucas Nussbaum wrote:
> On 12/01/19 at 08:32 +0100, Andreas Beckmann wrote:
>> Source packages that build binary-arch packages, but no amd64 binary
>> packages are usually not tested by archive wide rebuilds and may
>> silently FTBFS for a long time.
&
On 2019-01-12 15:26, Holger Levsen wrote:
> On Sat, Jan 12, 2019 at 08:32:42AM +0100, Andreas Beckmann wrote:
>> Source packages that build binary-arch packages, but no amd64 binary
>> packages are usually not tested by archive wide rebuilds and may
>> silently FTBFS for a lon
Hi,
I just looked at #917650, the qi FTBFS which goes back to jessie (at least).
Source packages that build binary-arch packages, but no amd64 binary
packages are usually not tested by archive wide rebuilds and may
silently FTBFS for a long time.
This should not affect packages building only arch
Hi,
here are my observations after analyzing a few pbuilder --twice failures
in experimental. I only did full (source+arch+indep) builds.
The command sequence being tested is roughly:
1. debian/rules clean
2. dpkg-source
3. debian/rules build binary
4. debian/rules clean
5. dpkg-source
6. debia
On 2017-07-19 23:29, Lucas Nussbaum wrote:
> Hi,
>
> It is becoming increasingly painful to do QA work due to the number of
> packages in unstable that have been completely broken for a long time.
>
> I've been pondering with ignoring packages not in testing when doing
> archive rebuilds, but tha
Hi,
does someone have a bug template ready for failing to build twice in a row?
After doing some experimental rebuilds locally to find old cruft that
does not build any more (and probably did not for years) - all should
have bugs filed by now - I tried to enable --twice in my pbuilder setup,
but
On 2017-07-20 12:07, Holger Levsen wrote:
> On Wed, Jul 19, 2017 at 11:29:50PM +0200, Lucas Nussbaum wrote:
>> It is becoming increasingly painful to do QA work due to the number of
>> packages in unstable that have been completely broken for a long time.
>
> indeed.
>
>> So, I propose that we r
Package: qa.debian.org
Severity: normal
User: qa.debian@packages.debian.org
Hi,
udd bug queries in the web interface should have markers for
oldstable/oldoldstable in the releases column, too, in addition to (STUEē).
What about (O) for oldstable and (∞) for oldoldstable (but otoh, the
infinit
Hi,
if anybody has some spare time, I would be interested in packages that
are real packages in jessie but virtual packages in stretch, and the
packages in stretch that depend (recommend) on the virtual package.
This can cause upgrade issues ... like #863890.
The package texlive-math-extra is on
Hi,
I just looked at #857897 ... haven't we done any i386 (or other 32-bit)
archive wide rebuild since gcc-6 has become the default?
Andreas
On Wed, 15 Mar 2017 19:52:36 +0100 Markus Koschany wrote:
> I think both are affected but probably tracker.debian.org as the
> successor of the PTS is the better place to address this issue.
Not to forget britney integration ...
We discussed this at some point, but these will probably be only
po
On 2015-07-23 22:07, Jonathan Wiltshire wrote:
> On Thu, Jul 23, 2015 at 07:44:53PM +0200, Andreas Beckmann wrote:
>> nmu caja-actions_1.8.0+dfsg1-1 . amd64 . -m "Rebuild in an up-to-date
>> environment."
>>
>> was quarantined in NEW since February ...
>&
[ switching to -qa@ and piuparts-devel@ ]
I think we can assign severities to piuparts problems. for now 2 should
suffice:
* serious, e.g. "modifies/deletes files from an unrelated package"
* important, e.g. "leaves cruft in /var/log/$PACKAGE/ after purge"
For stable releases we usually disable t
On 2014-01-26 01:43, Ivo De Decker wrote:
> The attached patches should add this information to the PTS.
Thanks a lot!
Looking at
http://packages.qa.debian.org/~pabs/x/xastir.html
It is affected by RC bug(s) and 733383
This does not look like a good sentence:
- there should be no 'and' if the
Hi,
the problem discovered in http://bugs.debian.org/736426 can probably
checked for automatically. But I don't know enough about the
full-archive rebuilds (nor do I have time to dig into them ... as least
as long as there are failures discovered with piuparts) to see how this
can be accomplished
Package: qa.debian.org
Severity: wishlist
Hi,
it would be nice if the PTS would list package versions in DEFERRED
(and the remaining time) in the "versions" box, like it is done for
packages in the NEW queue.
Andreas
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subje
With the upcoming rdepends removal it's getting even more important to
make this information available prominently.
Andreas
--
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.
Package: qa.debian.org
Severity: normal
Hi,
UDD seems be be a bit confused about some bugs, too:
query for closed bugs affecting sid (all bugs), and you will find
several kfreebsd-8 bugs there, e.g. #725575
but kfreebsd-8 has been removed from jessie and sid ...
Maybe the sid and jessie tags add
On 2013-11-24 12:24, Lucas Nussbaum wrote:
>> On 2013-10-04 08:43, Niels Thykier wrote:
>>> There are a number of cases where the Debian Bug Tracker can become
>>> "confused" or (to many) behave surprisingly. The most common example
>>> is when a bug in marked as "found" and "fixed" in the same ve
On 2013-11-24 12:02, Lucas Nussbaum wrote:
> On 06/11/13 at 04:47 +0100, Andreas Beckmann wrote:
>> it would be helpful to have a way to exclude bugs that are fixed in
>> experimental (derived from version information, not the ancient
> I've fixed this in a slightly differe
On 2013-11-24 12:24, Lucas Nussbaum wrote:
> On 04/10/13 at 15:23 +0200, Niels Thykier wrote:
>> On 2013-10-04 08:43, Niels Thykier wrote:
>>> There are a number of cases where the Debian Bug Tracker can become
>>> "confused" or (to many) behave surprisingly. The most common example
>>> is when a
Package: qa.debian.org
Severity: wishlist
Hi,
it would be helpful to have a way to exclude bugs that are fixed in
experimental (derived from version information, not the ancient
fixed-in-experimental tag) (or do other things with experiental fixage)
Packages that have no version in experimental s
Hi Lucas,
On 2013-05-09 11:32, Lucas Nussbaum wrote:
> I'm unlikely to be able to do much archive rebuild work in the coming year,
> so
> I would welcome help on that front.
I'm not volunteering for the job :-)
But your mail rises two questions:
* do we have a recent wheezy rebuild - ideally
Package: qa.debian.org
Severity: normal
Looking at my overview page
http://qa.debian.org/developer.php?login=anbe%40debian.org+pkg-nvidia-devel%40lists.alioth.debian.org+pkg-fglrx-devel%40lists.alioth.debian.org&comaint=yes&reset=yes
I don't see my NMUs to PU listed there.
The packages were liste
Package: qa.debian.org
Severity: normal
Hi,
the PTS incorrectly reports
This package is neither part of unstable nor experimental.
even if the package is in experimental:
http://packages.qa.debian.org/q/qpopper.html
oldstable 4.0.9.dfsg-1
stable 4.0.9.dfsg-1.2
exp 4.1~a4+dfsg-1
Andreas
Package: qa.debian.org
Severity: normal
Hi,
I just noticed that
http://qa.debian.org/developer.php?login=debian%40abeckmann.de+pkg-nvidia-devel%40lists.alioth.debian.org+pkg-fglrx-devel%40lists.alioth.debian.org&comaint=yes
only lists the packages for the first email address. Last year (up to
N
Package: qa.debian.org
Severity: normal
Hi,
the watch file report as of today in
http://qa.debian.org/developer.php?packages=nvidia-graphics-drivers
is incorrect:
Watch
UnstableExp
280.13.really.275.36280.13.really.275.36
Download link to 275.36 tarbal
On 2011-08-22 23:03, Giovanni Mascellani wrote:
> Which content search function are you referring to? I don't know
> anything like that for PTS.
I mean the content search on
http://www.debian.org/distrib/packages
Andreas
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a su
Package: qa.debian.org
Severity: normal
Hi,
The PTS package content search function does not seem to support
searching for directories or just any file below a certain directory.
Example query: "List all packages that ship a file in some foobar.d/
directory, e.g. /usr/share/X11/xorg.conf.d/" whi
Package: qa.debian.org
Severity: wishlist
Hi,
is it possible to provide not only a copy of Changelog.Debian online,
but also one of NEWS.Debian?
Andreas
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (800, 'testing'), (800, 'stable'), (600, 'unstable'),
Package: qa.debian.org
Severity: normal
Hi,
I just noted that qa.debian.org shows 0 bugs for a package with 3 open
bug reports (those bugs are already rather old, so if the bug counts are
only updated e.g. daily they should have been counted long ago):
http://packages.qa.debian.org/n/nvidia-graph
Package: qa.debian.org
Severity: wishlist
Hi,
if the focus would be set to input field, one could start typing the
package name immediately.
Google does this with some javascript:
function sf(){document.f.q.focus();}
...
Andreas
-- System Information:
Debian Release: testing/unstable
APT p
52 matches
Mail list logo
