Felix Lechner, le dim. 09 janv. 2022 08:15:27 -0800, a ecrit:
> On Sun, Jan 9, 2022 at 7:36 AM Samuel Thibault wrote:
> >
> > we cannot
> > write lintian overrides files that avoid red flags on both platforms.
>
> Lintian's latest version will always be aut
Mattia Rizzolo, le dim. 09 janv. 2022 15:58:31 +0100, a ecrit:
> On Sat, Jan 08, 2022 at 05:39:04PM +0100, Samuel Thibault wrote:
> > With lintian's current tendency of changing its output, we have to adapt
> > the suppression rules. But it appears that qa.debian.org and sals
Package: qa.debian.org
Severity: important
Hello,
With lintian's current tendency of changing its output, we have to adapt
the suppression rules. But it appears that qa.debian.org and salsa's CI
rules are not using the same version of lintian, so we are stuck with
either having lintian errors sho
Control: -1 + unreproducible
Control: close -1
Samuel Thibault, le jeu. 07 janv. 2021 20:10:25 +0100, a ecrit:
> Samuel Thibault, le dim. 03 janv. 2021 02:18:56 +0100, a ecrit:
> > The VCS CI tick is super useful, but it seems it's not always correctly up
> > to date. As of
Hello,
Samuel Thibault, le dim. 03 janv. 2021 02:18:56 +0100, a ecrit:
> The VCS CI tick is super useful, but it seems it's not always correctly up
> to date. As of now, on line ccsm of
>
> https://qa.debian.org/developer.php?email=sthibault%40debian.org
>
> there is a &
Hello,
M. Zhou, le jeu. 17 janv. 2019 08:28:24 +, a ecrit:
> For example, ci.d.o keeps running autopkgtest for zfs-linux and
> intel-mkl on Debian testing, but the result is not displayed on my DDPO
> page[1].
>
> https://ci.debian.net/packages/z/zfs-linux/testing/amd64/
> https://ci.debian.n
Package: qa.debian.org
Severity: normal
Hello,
The VCS CI tick is super useful, but it seems it's not always correctly up
to date. As of now, on line ccsm of
https://qa.debian.org/developer.php?email=sthibault%40debian.org
there is a "failed" word in the VCS column, while
https://salsa.debian
Hello,
Ryan Kavanagh, le jeu. 21 mai 2020 11:05:28 -0400, a ecrit:
> The "Lintian" reports link on packages overview pages are broken. For
> example, clicking on "Lintian" on my packages overview page [0] brings
> you to the following non-existing page [1]. It looks like the page may
> have moved
Helmut Grohne, le lun. 03 juin 2019 17:12:22 +0200, a ecrit:
> What we need here is more people working on the difficult issues, not
> random maintainers staring at undecipherable cross build failures.
Ok :)
> What we also need is maintainers replying to bug reports and
> converting their package
Package: qa.debian.org
Severity: normal
Hello,
https://tracker.debian.org/ has a link to the cross-buildability status
of a package. It'd be useful to have a tick or cross on the
https://qa.debian.org/developer.php page, e.g. in the CI/Rep column, as
a link to the cross-buildability status, to be
Hello,
Raphael Hertzog, on Mon 11 Jul 2016 13:08:30 +0200, wrote:
> Putting Samuel Thibault in copy as he might be able to provide some
> useful input.
Unfortunately I'm really not an expert of *web* accessibility :)
Samuel
Shérab, le Sat 03 Jan 2015 20:38:12 +0100, a écrit :
> Samuel Thibault (2015/01/03 19:47 +0100):
> > I guess a cron could be set up on an amd64 porter box, using a dedicated
> > chroot for the build.
>
> What's a porter box?
It's a system administrated by DS
Shérab, le Sat 03 Jan 2015 19:41:40 +0100, a écrit :
> > I'd be happy to, if you still consider it sensible, given what I said
> > above.
>
> Well, I don't know, actually. Out of jenkins, are there other ways to
> build packages bsed on upstream HEAD n an easy way?
I guess a cron could be set up
Package: tracker.debian.org
Severity: normal
Hello,
I was wondering why the nvidia-cuda-toolkit transition wasn't
happening. The QA page for nvidia-cuda-toolkit or one of its rev-dep,
starpu-contrib, would only show "Valid candidate". It happens that it
doesn't migrate because the starpu-contri
On Tue, Jan 18, 2011 at 09:11, Silvio Cesare wrote:
> I performed an audit of Debian stable for memset(x,y,0) bugs. These should
> typically be corrected with memset(x,0,y).
>
> The results can be found
> https://github.com/silviocesare/Automated-Audits/blob/master/Debian5.05/Memset0Count/06-01-20
Hello,
Julien Cristau, le Sun 29 Nov 2009 12:43:48 +0100, a écrit :
> So one thing I think might help would be to organise some sort of
> focused BSPs where you pick a weekend, a set of packages (say X, or
> gnome, or mozilla, …), and 20 or so people, and you try to triage /
> answer / close as ma
16 matches
Mail list logo
