Package: qa.debian.org
Severity: normal
http://packages.qa.debian.org/m/mksh.html tells me to…
│ Todo
│ * The package should be updated to follow the last version of [29]Debian
Policy
Apparently, it has not been fixed with later runs:
$ lynx -dump http://packages.qa.debian.org/m/mksh.html
[…]
Overview of [4]mksh source package
General information
Latest version 37.3-2
Maintainer [5]Thorsten Glaser [6][email]
Maintenance[7]DMUA
Hi again,
looks like it works now. I assume you can close the bug?
bye,
//mirabilos
--
Sometimes they [people] care too much: pretty printers [and syntax highligh-
ting, d.A.] mechanically produce pretty output that accentuates irrelevant
detail in the program, which is as sensible as putting al
Package: qa.debian.org
Severity: wishlist
Lines of the form
│Vcs-CVS: :ext:_anon...@anoncvs.mirbsd.org:/cvs contrib/hosted/tg/deb/makefs
are converted to bogus hyperlinks of the form
│http://packages.qa.debian.org/libb/:ext:_anoncvs%40anoncvs.mirbsd.org:/cvs%20contrib/hosted/tg/deb/libbsd-arc4rand
Package: qa.debian.org
I’ve sponsored an upload of mediawiki for the second time now,
and it still doesn’t show up at:
http://qa.debian.org/developer.php?login...@mirbsd.de
Note mediawiki-extensions is not sponsored but indeed uploaded
by me, but mediawiki isn’t.
http://packages.qa.debian.org/m/
Francesca Ciceri dixit:
>Hey mira :)
;)
>> where are we supposed to track bugs against packages in
>> debian-ports.org’s unreleased suite?
>
>Aehm. No idea. I mean, do you usually use the BTS?
Good question. Strictly speaking, debian-ports.org is not
Debian (no matter whether it’s a package in
Package: qa.debian.org
Hi,
http://qa.debian.org/developer.php?login=t...@mirbsd.de
has the package CVS up to date, as can be seen in
http://qa.debian.org/cgi-bin/watch?pkg=cvs
but it’s still blue, not green, probably due to the epoch.
I have already mangled away the epoch in the last upload,
so
Package: qa.debian.org
Severity: normal
Package declares a build time dependency on debhelper-compat (= 12) which
cannot be satisfied on amd64.
Please hack debcheck that it works with these virtual packages. Thanks!
-- System Information:
Debian Release: bullseye/sid
APT prefers buildd-unsta
On Tue, 19 Nov 2019, Thorsten Glaser wrote:
> Please hack debcheck that it works with these virtual packages. Thanks!
Perhaps same with 'default-logind | logind'.
Thanks in advance,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel:
On Sun, 15 Dec 2019, Colin Watson wrote:
> Both this and debhelper-compat are cases of versioned Provides (although
> one is typically found in Build-Depends and one in Depends, but it works
> out much the same way). I've made a merge request that should fix this:
Thanks!
I get that or’d depend
Package: qa.debian.org
I’ve barely managed to get the DDPO to fit on my 1024x768 laptop screen
by zooming out, and now there are suddenly icons which make it wider again.
Please allow me to get rid of them.
Similarily, dropping the icon from the Bugs column would be a welcome feature.
-- System
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
https://qa.debian.org/cgi-bin/vcswatch?package=campania and others have:
Error: fatal: dumb http transport does not support shallow capabilities
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
There used to be a box (or something, I mostly use this with lynx)
for testing migration status, but it’s apparently now missing.
I know tracker.d.o has it, but that site’s appalling in UI/UX and
looks awful and it’s much harder
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Look at https://packages.qa.debian.org/b/bash.html
bugs
all [93]bug history graph
[94]406 ([95]433)
RC
[96]0
I&N
[97]275 ([98]295)
M&W
[99]131 ([100]138)
F&P
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’ve been seeing an FTBFS in the “Rep” column for a few days now
for a package that is merely unreproducible but does build twice
(dygraphs).
The same bad info shows up on tracker.d.o if that helps.
Package: tracker.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Unsure if this is the right pseudopackage; if not, please reassign.
The “new” Debian tracker shows:
debian/patches: 1 patch to forward upstream
The package however uses the single-debian-patch mechanism
to let a diff be
reassign 1038121 dpkg-dev
thanks
Raphael Hertzog dixit:
>So maybe it's dpkg-source that needs to be tweaked so that such patches
>have a field "Forwarded: not-needed" and an explanation that the patch
>is an auto-generated mess that can't be forwarded as is.
I guess so. I was thinking along thes
Bart Martens dixit:
>> Can you update the PTS so that it puts TODO items on the pages for
>> packages with broken or overridden watch files?
>
>Good idea. I have done a few updates, and if all is well then the info should
>appear on the pts in a few hours from now.
How do I get “updated watch fi
Bart Martens dixit:
>Which ones are bogus/broken/wrong ?
At least mksh (we talked about it already) and cvs.
I want a generic way to remove these “updated” files.
bye,
//mirabilos
--
[DJBDNS Zone] TTL 86400 – kann man da auch 1d schreiben?
nö, außerdem kann ein Deutscher oder ein Japaner mit
Bart Martens dixit:
>What would be bogus/broken/wrong about them ?
cvs misses one mangle that's needed due to a DEHS bug, and
both have absolutely insane file extension matches that,
in the case of mksh, definitely will never happen.
Also, this is *not* about a particular instance of something
b
Bart Martens dixit:
>It does happen. Upstream did change the file extension between versions 40 and
>41. Checking for only one file extension is a common mistake, see:
I *am* upstream!
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bon
Holger Levsen dixit:
>on jenkins.debian.net we're using pbuilder from wheezy in a wheezy environment
Do you mean pbuilder from jessie?
>as tests involving network fail
That’s deliberate. There may be no network access during package build;
this is a bug in the packages involved. (The earlier ve
Package: qa.debian.org
Severity: normal
tglase@tglase:~ $ rmadison libxml2
libxml2| 2.8.0+dfsg1-7+wheezy5 | oldstable | source, amd64,
armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc,
s390, s390x, sparc
[…]
However, https://packages.debian.org/wh
Hi,
https://qa.debian.org/cgi-bin/vcswatch?package=xrdp
shows this as behind, although the master branch and
related tags are up-to-date wrt. the package in sid,
and the experimental branch and tags are up-to-date
wrt. the package in experimental.
Is this a bug?
Although I have to admit the VCS-
Andreas Beckmann dixit:
>How could we check for these bugs?
Why are these bugs anyway? I mean, not why they are defined as bugs
(I do know the rule), but why does this rule exist (or, at least,
still exist)?
Even quite some time ago, I’d assume a build to always start from
a clean state (.dsc or
Holger Levsen dixit:
>On Thu, Dec 21, 2017 at 05:14:02AM +0100, Andreas Beckmann wrote:
>> Does the reproducible build effort currently test for reproducibility of
>> source packages?
>
>no. the creation of Debian source packages is not reproducible at the
>moment. I don't recall whether we found
https://qa.debian.org/cgi-bin/vcswatch?package=musescore-general-soundfont
Error: Cloning into bare repository
'/srv/scratch/qa.debian.org/vcswatch/m/musescore-general-soundfont'...
fatal: dumb http transport does not support shallow capabilities
Just unshallow then ☺
Hi Paul,
> > fatal: dumb http transport does not support shallow capabilities
> >
> > Just unshallow then ☺
>
> Please file a bug about this so it isn't forgotten.
a bug report against what? Surely not against myon… the page says:
“To report a problem with the QA web site, e-mail
debian-qa@list
Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: vcswatch
https://qa.debian.org/cgi-bin/vcswatch?package=musescore-general-soundfont
lists this error:
Error: Cloning into bare repository
'/srv/scratch/qa.debian.org/vcswatch/m/musescore-general-soundfont'...
fatal: dumb htt
Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: vcswatch
Individual vcswatch pages as linked from DDPO do not have any indication
of where to report bugs to, e.g.
https://qa.debian.org/cgi-bin/vcswatch?package=musescore-general-soundfont
only shows “To report a problem wit
30 matches
Mail list logo