On Tue, 2020-08-25 at 17:30 -0400, Peter S Galbraith wrote:
> I am on vacation so *should* have time to look into this soonish.
Did you get a chance to look at the libforms FTBFS with GCC-10?
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed
Your message dated Tue, 22 Sep 2020 01:18:28 +
with message-id
and subject line Bug#817441: fixed in dvidvi 1.0-10.1
has caused the Debian Bug report #817441,
regarding dvidvi: Removal of debhelper compat 4
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 22 Sep 2020 01:03:29 +
with message-id
and subject line Bug#957167: fixed in efax 1:0.9a-20
has caused the Debian Bug report #957167,
regarding efax: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Tue, 22 Sep 2020 00:48:25 +
with message-id
and subject line Bug#961381: fixed in gsutil 3.1-4
has caused the Debian Bug report #961381,
regarding gsutil: autopkgtest failure: Can't locate LWP/UserAgent.pm in @INC
to be marked as done.
This means that you claim that the
Your message dated Mon, 21 Sep 2020 23:48:48 +
with message-id
and subject line Bug#961456: fixed in pwget 2016.1019+git75c6e3e-4
has caused the Debian Bug report #961456,
regarding pwget: autopkgtest regression: Can't locate LWP/UserAgent.pm in @INC
to be marked as done.
This means that you
On Mon, Sep 21, 2020 at 12:48:25PM +0200, jhcha54008 wrote:
> should this bug be merged with #940056 and #968868 ?
If statx is the only reason for the failures.
Processing commands for cont...@bugs.debian.org:
> tags 968893 ftbfs
Bug #968893 [src:mariadb-10.3] mariadb-10.3: FTBFS on alpha: relocation
truncated to fit
Added tag(s) ftbfs.
> tags 970662 ftbfs
Bug #970662 [src:mariadb-10.5] mariadb-10.5: FTBFS on x32: operand size
mismatch for `crc32'
Your message dated Mon, 21 Sep 2020 21:34:10 +
with message-id
and subject line Bug#957615: fixed in ntp 1:4.2.8p15-1
has caused the Debian Bug report #957615,
regarding ntp: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> retitle 970662 mariadb-10.5: FTBFS on x32: operand size mismatch for `crc32'
Bug #970662 [src:mariadb-10.5] mariadb-105: FTBFS on x32: operand size mismatch
for `crc32'
Changed Bug title to 'mariadb-10.5: FTBFS on x32: operand size mismatch for
Source: numba
Version: 0.50.1-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)
numba has unsatisfiable build dependencies:
| report:
| -
| package: sbuild-build-depends-main-dummy
| version: 0.invalid.0
|
Version: 5.12-1
Version 5.12-1 compiled correctly on my testing system just now.
Diane
On Sun, 2020-09-13 at 20:47 -0700, Sean Whitton wrote:
> Hello,
>
> On Sat 05 Sep 2020 at 09:22PM -07, Diane Trout wrote:
>
> > I tried to just build 5.11, but export CABAL=./Setup breaks the
> > build, the
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:node-regexpu-core
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Your message dated Mon, 21 Sep 2020 17:03:32 +
with message-id
and subject line Bug#966127: fixed in embassy-phylip 3.69.660-4
has caused the Debian Bug report #966127,
regarding embassy-phylip: FTBFS with GCC 10: multiple definition of ... due to
-fno-common
to be marked as done.
This
Am Montag, den 21.09.2020, 17:57 +0200 schrieb Andreas Tille:
> On Mon, Sep 21, 2020 at 05:30:20PM +0200, Andreas Tille wrote:
> >
> > May be I misunderstood you - but if you do not run the test at all
> > (as done in some architectures) how will you know whether the test
> > might fail? May be
Your message dated Mon, 21 Sep 2020 16:48:31 +
with message-id
and subject line Bug#967167: fixed in librelp 1.7.0-1
has caused the Debian Bug report #967167,
regarding librelp: Unversioned Python removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tag -1 pending
Bug #967167 [src:librelp] librelp: Unversioned Python removal in sid/bullseye
Added tag(s) pending.
--
967167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #967167 in librelp reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> reassign -1 cowdancer
Bug #970688 [libtinfo6] rm: /lib/i386-linux-gnu/libtinfo.so.6: version
`NCURSES6_TINFO_6.2.current' not found (required by
/lib/i386-linux-gnu/libncurses.so.6)
Bug reassigned from package 'libtinfo6' to 'cowdancer'.
No longer marked as found
Control: reassign -1 cowdancer
Control: forcemerge 970555 -1
On 2020-09-21 17:53 +0200, Rene Engelhard wrote:
> Package: libtinfo6
> Version: 6.2+20200918-1
> Severity: serious
>
> Hi,
>
> in a (dist-|cowbuilder ) upgrade of my i386 chroot:
>
> Preparing to unpack
Package: libtinfo6
Version: 6.2+20200918-1
Severity: serious
Hi,
in a (dist-|cowbuilder ) upgrade of my i386 chroot:
$ sudo cowbuilder --update --basepath /var/cache/pbuilder/base.cow.i386/
--bindmounts /home
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.26407
I:
On Mon, Sep 21, 2020 at 05:30:20PM +0200, Andreas Tille wrote:
>
> May be I misunderstood you - but if you do not run the test at all
> (as done in some architectures) how will you know whether the test
> might fail? May be I miss your point here and thus I implemented
> my suggestion and we'll
Hi Matthias,
On 21-09-2020 11:43, Matthias Klose wrote:
> I don't think that referring to the Ubuntu autopkg testers is helping here. I
> couldn't find any documentation on the timeout settings for the Debian
> infrastructure, for both amd64 and arm64.
$(man autopkgtest) has a section about
Your message dated Mon, 21 Sep 2020 15:33:33 +
with message-id
and subject line Bug#957057: fixed in brightd 0.4.1-4
has caused the Debian Bug report #957057,
regarding brightd: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hey Scott,
since nitrokey-app has been kickout of testing today, I want to ask
about the update? Do you need some help I could offer?
Best,
Jan
Am 21.08.20 um 00:01 schrieb Scott Kitterman:
> I will take care of it. The removal isn't scheduled for almost a month, so
> there is plenty of time.
Hi Martin,
On Mon, Sep 21, 2020 at 09:26:41AM +, Uecker, Martin wrote:
> > To the best of my knowledge the fact that a test runs on amd64 but fails
> > on some other architecture is not only caused by issues in the tool
> > chain. For instance recently I learned that for instance if char is
Quoting Sylvestre Ledru (2020-09-21 16:52:18)
>
> Le 21/09/2020 à 16:48, Jonas Smedegaard a écrit :
> > Hi Sylvestre and others,
> >
> > I have a strong interest in getting emscripten into shape.
> >
> > I am not ready to get involved in the LLVM Packaging Team, nor do I
> > find the current
Hi Tony,
Le 21/09/2020 15:53, tony mancill a écrit :
On Mon, Sep 21, 2020 at 08:39:07AM +, Debian Bug Tracking System
wrote:
This is an automatic notification regarding your Bug report
which was filed against the src:openjfx package:
#969260: openfjx: FTBFS (gstreamer)
It has been closed
Processing commands for cont...@bugs.debian.org:
> notfound 970651 0.50.0-6
Bug #970651 {Done: Xavier Guimard } [rollup] rollup: Unable to
build with current tsc
Ignoring request to alter found versions of bug #970651 to the same values
previously set
> thanks
Stopping processing here.
Please
Le 21/09/2020 à 16:48, Jonas Smedegaard a écrit :
Hi Sylvestre and others,
I have a strong interest in getting emscripten into shape.
I am not ready to get involved in the LLVM Packaging Team, nor do I find
the current state of the package useful to work from, but I would be
willing to take
Hi,
When I take a screenshot of the whole screen the background of the
terminal is transparent, that is, if there is another window behind
then the content of that window is captured, the text of the terminal
is kept.
If I take a screenshot of the terminal window then the background is
Your message dated Mon, 21 Sep 2020 14:47:43 +
with message-id
and subject line Bug#958614: fixed in nyancat 1.5.2-0.1
has caused the Debian Bug report #958614,
regarding nyancat: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that
Hi Sylvestre and others,
I have a strong interest in getting emscripten into shape.
I am not ready to get involved in the LLVM Packaging Team, nor do I find
the current state of the package useful to work from, but I would be
willing to take over maintenance if that is ok with the current
Processing commands for cont...@bugs.debian.org:
> notfixed 968965 xen/4.14.0-1~exp1
Bug #968965 {Done: Hans van Kranenburg } [src:xen] xen: FTBFS
in sid
No longer marked as fixed in versions xen/4.14.0-1~exp1.
> found 968965 xen/4.14.0-1~exp1
Bug #968965 {Done: Hans van Kranenburg } [src:xen]
notfixed -1 xen/4.14.0-1~exp1
reopen
found -1 xen/4.14.0-1~exp1
thanks
Hi,
On 9/4/20 1:55 PM, Hans van Kranenburg wrote:
>
> On 8/24/20 7:03 PM, Gianfranco Costamagna wrote:
>> Source: xen
>> Version: 4.11.4+24-gddaaccbbab-1
>> Severity: serious
>>
>> Hello, looks like xen is FTBFS because of
Hi Stephen,
On Mon, Sep 21, 2020 at 08:39:07AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:openjfx package:
>
> #969260: openfjx: FTBFS (gstreamer)
>
> It has been closed by Debian FTP Masters
>
Your message dated Mon, 21 Sep 2020 13:50:26 +
with message-id
and subject line Bug#969260: fixed in openjfx 11.0.7+0-5
has caused the Debian Bug report #969260,
regarding openfjx: FTBFS (gstreamer)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Mon, 21 Sep 2020 11:50:03 +
with message-id
and subject line Bug#970651: fixed in node-rollup 1.12.0-3
has caused the Debian Bug report #970651,
regarding rollup: Unable to build with current tsc
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #970651 [rollup] rollup: Unable to build with current tsc
Ignoring request to alter tags of bug #970651 to the same tags previously set
--
970651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970651
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #970651 in node-rollup reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #970651 in node-rollup reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #970651 [rollup] rollup: Unable to build with current tsc
Ignoring request to alter tags of bug #970651 to the same tags previously set
--
970651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970651
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 970651 + pending
Bug #970651 [rollup] rollup: Unable to build with current tsc
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
970651:
X-Debbugs-CC: 964621-submit...@bugs.debian.org,
940056-submit...@bugs.debian.org, 968868-submit...@bugs.debian.org, Aurelien
Jarno
Hi,
should this bug be merged with #940056 and #968868 ?
Regards,
JH Chatenet
Your message dated Mon, 21 Sep 2020 10:00:11 +
with message-id
and subject line Bug#970408: fixed in facter 3.14.12-1
has caused the Debian Bug report #970408,
regarding facter: FTBFS: cc1plus: all warnings being treated as errors
to be marked as done.
This means that you claim that the
Your message dated Mon, 21 Sep 2020 10:00:33 +
with message-id
and subject line Bug#968965: fixed in xen 4.14.0-1~exp1
has caused the Debian Bug report #968965,
regarding xen: FTBFS in sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Mon, 21 Sep 2020 10:00:10 +
with message-id
and subject line Bug#970379: fixed in cpp-hocon 0.3.0-1
has caused the Debian Bug report #970379,
regarding FTBFS: cpp-hocon fails to build against boost1.71
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 21 Sep 2020 10:00:29 +
with message-id
and subject line Bug#953875: fixed in runit 2.1.2-37
has caused the Debian Bug report #953875,
regarding runit - default installation can force init switch
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 21 Sep 2020 10:00:11 +
with message-id
and subject line Bug#962692: fixed in facter 3.14.12-1
has caused the Debian Bug report #962692,
regarding facter aborts with free(): invalid pointer
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 21 Sep 2020 10:00:11 +
with message-id
and subject line Bug#962692: fixed in facter 3.14.12-1
has caused the Debian Bug report #962692,
regarding puppet: Crashes due to "missing" facts.d directories
to be marked as done.
This means that you claim that the problem has
Quoting Pirate Praveen (2020-09-21 09:15:46)
>
>
> On 2020, സെപ്റ്റംബർ 21 3:37:01 AM IST, Jonas Smedegaard
> wrote:
> >> I think we should create a release team within js team to handle it
> >> like how release team works for transitions.
> >
> >What do you mean more concretely?
> >
> >That
Processing control commands:
> clone -1 -2
Bug #970606 [src:openjdk-15] src:openjdk-*: autopkgtest times out on
Debian/Ubuntu infrastructure
Bug 970606 cloned as bug 970675
> reassign -2 release.debian.org
Bug #970675 [src:openjdk-15] src:openjdk-*: autopkgtest times out on
Debian/Ubuntu
Control: clone -1 -2
Control: reassign -2 release.debian.org
On 9/19/20 9:16 PM, Paul Gevers wrote:
> Source: openjdk-15
> Version: 15+36-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: timeout
>
> Dear
Hi Andreas,
Am Montag, den 21.09.2020, 09:45 +0200 schrieb Andreas Tille:
> Hi Martin,
>
> On Sat, Sep 19, 2020 at 05:50:34PM +, Uecker, Martin wrote:
> > > I'm not sure whether this is a good idea in general. If
> > > we can be sure that for s390x there is an issue with the
> > > tool
Your message dated Mon, 21 Sep 2020 09:06:59 +
with message-id
and subject line Bug#970656: fixed in r-cran-isospecr 2.1.2-3
has caused the Debian Bug report #970656,
regarding r-cran-isospecr: missing (unversioned) Breaks+Replaces: r-cran-isospec
to be marked as done.
This means that you
Control: tags -1 + moreinfo
On Sun, 20 Sep 2020 at 19:29:19 -0300, Fabian Inostroza wrote:
> After an upgrade of libvte gnome-terminal and other software using
> the library (gedit terminal plugin) doesn't work.
> Where the console should be there is some transparency and a effect
> similar to
Processing control commands:
> tags -1 + moreinfo
Bug #970664 [libvte-2.91-0] libvte-2.91-0: Terminal not displaying correctly
Added tag(s) moreinfo.
--
970664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 21 Sep 2020 08:36:13 +
with message-id
and subject line Bug#969260: fixed in openjfx 11.0.7+0-5~exp1
has caused the Debian Bug report #969260,
regarding openfjx: FTBFS (gstreamer)
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 21 Sep 2020 18:13:26 +1000
with message-id <3753945.cFZ7fMXtxX@deblab>
and subject line Done: litecoin: FTBFS on mips64el in binNMU against qrencode -
test failure
has caused the Debian Bug report #908987,
regarding litecoin: FTBFS on mips64el in binNMU against qrencode -
Hi Martin,
On Sat, Sep 19, 2020 at 05:50:34PM +, Uecker, Martin wrote:
> > I'm not sure whether this is a good idea in general. If
> > we can be sure that for s390x there is an issue with the
> > tool chain I could imagine something like:
> >
> > if build on s390x
> > run_test ||
On 2020, സെപ്റ്റംബർ 21 3:37:01 AM IST, Jonas Smedegaard wrote:
>> I think we should create a release team within js team to handle it
>> like how release team works for transitions.
>
>What do you mean more concretely?
>
>That only a smaller elite group should (approve) upload to unstable,
60 matches
Mail list logo
