Hi Brian,
On Fri, Dec 16, 2022 at 08:21:17AM +1100, Brian May wrote:
> No idea now, sorry. I think this stuff was contributed by others.
> Probably legacy reasons now.
Maybe you could later try converting it to dh_auto_configure? Doing so
would significantly simplify the invocation:
* debhelper
Package: gscan2pdf
Version: 2.13.0-2
Severity: normal
Tags: upstream
Hey,
for every page processed by unpaper, I get two errors:
1. [image2 @ 0x558772ceee40] The specified filename
'/home/ssd/madduck/.tmp/gscan2pdf-SMFz/OHSkXwKy5v.pnm' does not
contain an image sequence pattern or a
Package: g++-13
Version: 13-20221214-1
Severity: serious
Hi Matthias,
thanks for pushing gcc-13 into experimental already. That leaves plenty
of time to work on it. I've located a quite fundamental problem with it
already:
$ cat test.c++
#include
$ g++-13 -c test.c++
In file included from
This bug has been discussed and fixed upstream:
https://sourceforge.net/p/logwatch/bugs/99/
This is fixed in logwatch 7.6+.
FWIW, I'm attaching the combination patch of the 2 commits that were
applied in logwatch Git repository.diff --git a/scripts/services/exim b/scripts/services/exim
index
Hi Martina,
> Control: affects -1 + src:golang-github-prometheus-exporter-toolkit
>
> [ Reason ]
> This package is currently FTBFS on stable due to flaky tests.
If we're doing a stable update anyway, could we also piggyback the
fix https://security-tracker.debian.org/tracker/CVE-2022-46146 ?
Hi,
thought it may be a little while until I could dig into this but
actually found the time today. So here's another quick update.
* Nick Hastings [221216 13:15]:
> Hi,
>
> quick update.
>
> * Nick Hastings [221215 14:40]:
>
> > * Bastian Germann [221215 08:57]:
> >
> > > Your package fails
Hi Paul,
Le jeudi 15 décembre 2022 à 21:16 +0100, Paul Gevers a écrit :
> On 13-12-2022 21:59, Sébastien Villemot wrote:
> > The problem is that atlas needs to be recompiled against lapack 3.11.0.
> > Which has been done in atlas 3.10.3-13. But atlas itself cannot migrate
> > to testing because
Version: 6.3.1-2
Followup-For: Bug #1024867
X-Debbugs-Cc: m...@debian.org
Control: tags -1 ftbfs patch
Hi,
I built it on the porterbox, which is the same as most buildds (HiFive
Unmatched) and slower than the others (except for builders with Qemu VMs, which
are disabled now and probably will
Brave always looked malware to me.
Maybe that's why it's always in RFP and there's no ITP. I personally prefer a
brave-less Debian.
On Tue, 6 Dec 2022 10:24:25 +0100
Michael Stapelberg wrote:
> sur5r, would you be interested in picking this tiny package up?
> Otherwise, I’ll file a bug to orphan it.
Yes, I will pick this up before the freeze.
Cheers,
sur5r
--
ceterum censeo microsoftem esse delendam.
pgpeFy99hVSle.pgp
Hi Paul,
Чт 15 дек 2022 @ 21:10 Paul Gevers :
> On 14-12-2022 10:15, Debian Bug Tracking System wrote:
>> * rebuild against new swi-prolog (Closes: #1026056)
>
> I can't but feel a bit uneasy by this "solution". Apparently it's not
> properly tracked by dependencies, so it doesn't show up
control: tags -1 patch pending
diff -Nru gsfonts-other-6.0/debian/changelog gsfonts-other-6.0/debian/changelog
--- gsfonts-other-6.0/debian/changelog 2022-12-10 14:09:14.0 +0100
+++ gsfonts-other-6.0/debian/changelog 2022-12-16 09:26:49.0 +0100
@@ -1,3 +1,12 @@
+gsfonts-other
On 15/12/2022 20:38, Mihai Moldovan wrote:
[Resent to the bug tracker as well]
* On 12/15/22 19:15, Emilio Pozuelo Monfort wrote:
I'm not sure I understand what the problem is. The patches are in
debian/patches/ and are applied during build using quilt.
Oh this is about the
Package: tar
Version: 1.34+dfsg-1.1
Tags: hppa, patch, ftbfs, lfs
I wondered why tar now suddenly fails to build on those platforms.
Testcase # 151 does create files whith access dates which are outside of the
reach for
32-bit plaforms with a default of 32-bit timestamps in glibc.
This does
101 - 114 of 114 matches
Mail list logo
