kst 2.0.8-5 is marked for autoremoval from testing on 2023-03-16
It (build-)depends on packages with these RC bugs:
1030175: libgetdata: FTBFS: dh_install: error: missing files, aborting
https://bugs.debian.org/1030175
This mail is generated by:
https://salsa.debian.org/release-team/release-to
adv-17v35x 5.0.6.0-4 is marked for autoremoval from testing on 2023-03-02
It is affected by these RC bugs:
1030187: adv-17v35x-dkms: module fails to build for Linux 6.1
https://bugs.debian.org/1030187
This mail is generated by:
https://salsa.debian.org/release-team/release-tools/-/blob/master/
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 Feb 2023 20:23:31 -0500
Source: gnulib
Architecture: source
Version: 20230127+stable-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By:
gnulib_20230127+stable-1_source.changes uploaded successfully to localhost
along with the files:
gnulib_20230127+stable-1.dsc
gnulib_20230127+stable.orig.tar.gz
gnulib_20230127+stable-1.debian.tar.xz
gnulib_20230127+stable-1_amd64.buildinfo
Greetings,
Your Debian queue daemon (run
Version: 0.1.1-2.1+rm
Dear submitter,
as the package gcap has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1030878
The v
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
gcap | 0.1.1-2.1 | source, all
--- Reason ---
RoQA; outdated, broken, no upload since 2018, no upstream updates
-
Your message dated Wed, 08 Feb 2023 21:09:21 +
with message-id
and subject line Bug#1030878: Removed package(s) from unstable
has caused the Debian Bug report #1030877,
regarding gcap: perl error, package unusable
to be marked as done.
This means that you claim that the problem has been dealt
Opppss I thought I had, here it is.
bt full
#0 0x5641638af954 in print_arp_asset_screen (rec=0x2a)
at ./src/output/output-screen.c:115
No locals.
#1 0x5641638af6f0 in print_arp_asset (ip_addr=...,
mac_addr=0x7fa6db692384 "") at ./src/output/output.c:210
head = 0x564165
Am 08.02.23 um 18:42 schrieb Tim McConnell:
Hi Bernhard,
Okay I did that. Let me know if that was of any use.
Hello Tim,
could you send the actual output below the `bt full`?
Kind regards,
Bernhard
Package: gcap
Version: 0.1.1-2
Severity: grave
This package does not work (with an existing or non existing YT video),
using manpage examples:
On my workstation:
$ gcap 0QRO3gKj3qw
Checking ...Couldn't parsefile
[http://video.google.com/timedtext?hl=en&type=list&v=0QRO3gKj3qw] with
LWP:
no e
Hi Bernhard,
Okay I did that. Let me know if that was of any use.
--
Tim McConnell
On Wed, 2023-02-08 at 16:16 +0100, Bernhard Übelacker wrote:
> bt full
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 08 Feb 2023 17:11:13 +0100
Source: adv-17v35x
Architecture: source
Version: 5.0.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andr
adv-17v35x_5.0.7.0-1_source.changes uploaded successfully to localhost
along with the files:
adv-17v35x_5.0.7.0-1.dsc
adv-17v35x_5.0.7.0.orig.tar.gz
adv-17v35x_5.0.7.0-1.debian.tar.xz
adv-17v35x_5.0.7.0-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.
Your message dated Wed, 08 Feb 2023 16:34:03 +
with message-id
and subject line Bug#1030187: fixed in adv-17v35x 5.0.7.0-1
has caused the Debian Bug report #1030187,
regarding adv-17v35x-dkms: module fails to build for Linux 6.1
to be marked as done.
This means that you claim that the problem
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 08 Feb 2023 09:25:23 -0500
Source: purity
Architecture: source
Version: 1-20
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Boyuan Yang
Hello Tim,
thanks, that is good helpful information, but as long the core file
might be in the system, could you execute following commands:
export DEBUGINFOD_URLS="https://debuginfod.debian.net";
coredumpctl gdb 1546
(gdb) bt full
This will enable gdb to download needed debug symbol files
purity_1-20_source.changes uploaded successfully to localhost
along with the files:
purity_1-20.dsc
purity_1.orig.tar.gz
purity_1-20.debian.tar.xz
purity_1-20_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
17 matches
Mail list logo