Source: r-cran-unitizer
Version: 1.4.18-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
47s --- t-get.Rout.save_ 2023-06-28 00:18:14.856968786 +
47s +++ t-get.Rout_2023-06-28 00:18:14.860968876 +
Processing control commands:
> affects -1 + apparmor-profiles
Bug #1039668 [apparmor] apparmor: prompting due to modified conffiles which
were not modified by the user:
/etc/apparmor.d/abstractions/ubuntu-browsers.d/chromium-browser
Added indication that 1039668 affects apparmor-profiles
--
10
Package: apparmor
Version: 3.0.8-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + apparmor-profiles
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prom
Hi Mike,
Ad 1:
- banking.bank99.at uses crypto.getRandomValues() even before login
"The server at banking.bank99.at is taking too long to respond."
Yeah, http is blocked - you'll need to use https:// for that.
- RedHat support webpage uses getRandomUUID after login
Both fail with "Operati
Source: r-cran-xopen
Version: 1.0.0-2
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
30s == Failed
==
30s -- 1. Error ('test.R:4'): (code run
Source: r-cran-treespace
Version: 1.1.4.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
82s [ FAIL 2 | WARN 0 | SKIP 0 | PASS 45 ]
82s
82s == Failed tests
Source: r-cran-tikzdevice
Version: 0.12.4-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
160s [ FAIL 6 | WARN 0 | SKIP 32 | PASS 49 ]
160s
160s ══ Skipped tests
Source: r-cran-stars
Version: 0.6-0-4
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
104s STFDF> x = stfdf[stfdf[1:2,],]
104s Error in .local(from, to, ...) : DLL requires the use of native symbols
104s Calls
Source: r-cran-sjmisc
Version: 2.8.9-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
93s [ FAIL 10 | WARN 2 | SKIP 9 | PASS 148 ]
93s
93s ══ Skipped tests
═══
93s • empty test (6)
93s • On CRAN (3)
93s
9
Control: reopen -1
Control: found -1 racket-mode/20230425git0-1
> The release team has announced [1] that failing autopkgtest on amd64 and
> arm64 are considered RC in testing. [Release Team member hat on] Because
> we're currently in the hard freeze for bookworm, I have marked this bug
> as
Source: r-cran-ragg
Version: 1.2.5-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
40s [ FAIL 15 | WARN 0 | SKIP 3 | PASS 0 ]
40s
40s ══ Skipped tests
═══
Processing control commands:
> reopen -1
Bug #1033852 {Done: David Bremner } [src:racket-mode]
racket-mode: autopkgtest regression: Process *Racket REPL* connection broken by
remote peer
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared,
Source: r-cran-proc
Version: 1.18.0-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
72s [ FAIL 14 | WARN 51 | SKIP 32 | PASS 8973 ]
72s
72s ══ Skipped tests
═
Source: r-cran-pkgdown
Version: 2.0.7-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
95s [ FAIL 24 | WARN 0 | SKIP 78 | PASS 516 ]
95s
95s ══ Skipped tests
═
Source: r-cran-patchwork
Version: 1.1.2-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
47s [ FAIL 7 | WARN 0 | SKIP 0 | PASS 0 ]
47s
47s ══ Failed tests
Source: r-cran-pammtools
Version: 0.5.8-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
59s [ FAIL 2 | WARN 8 | SKIP 0 | PASS 341 ]
59s
59s ══ Failed tests
══
Source: r-cran-ncdfgeom
Version: 1.1.4+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
60s [ FAIL 1 | WARN 1 | SKIP 3 | PASS 637 ]
60s
60s ══ Skipped tests
═
Source: r-cran-knitr
Version: 1.42+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
80s autopkgtest [23:10:44]: test run-unit-test: [---
81s
81s R version 4.3.1 (2023-06-16) -- "Beagle Scouts"
81s Copyright (C) 2023 The R Foundation for Statist
Source: r-cran-irkernel
Version: 1.3.2-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
42s ==
42s FAIL: test_completion (__main__.IRkernelTes
Source: r-cran-gridtext
Version: 0.1.5-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
62s [ FAIL 3 | WARN 0 | SKIP 1 | PASS 231 ]
62s
62s ══ Skipped tests
══
Source: r-cran-glmmtmb
Version: 1.1.5+dfsg-4
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
50s autopkgtest [01:19:09]: test run-unit-test: [---
50s dpkg-architecture: warning: cannot determ
Source: r-cran-gnm
Version: 1.1-2-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
34s [ FAIL 2 | WARN 0 | SKIP 0 | PASS 39 ]
34s
34s == Failed tests
=
Source: r-cran-ggridges
Version: 0.5.4-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
45s [ FAIL 5 | WARN 2 | SKIP 0 | PASS 58 ]
45s
45s == Failed tests
Source: r-cran-ggrepel
Version: 0.9.3-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
100s [ FAIL 5 | WARN 0 | SKIP 0 | PASS 72 ]
100s
101s == Failed tests
==
Source: r-cran-ggplot2
Version: 3.4.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
84s [ FAIL 54 | WARN 4 | SKIP 95 | PASS 1450 ]
84s
84s ══ Skipped tests
═══
Source: r-cran-ggally
Version: 2.1.2-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
88s [ FAIL 1 | WARN 6 | SKIP 7 | PASS 530 ]
88s
88s == Skipped tests
Source: r-cran-epi
Version: 2.47-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
173s Attaching package: ‘survival’
173s
173s The following object is masked from ‘package:popEpi’:
173s
173s Surv
173s
Source: r-cran-cowplot
Version: 1.1.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
43s [ FAIL 7 | WARN 2 | SKIP 0 | PASS 55 ]
43s
43s ══ Failed tests
Source: r-cran-av
Version: 0.8.3+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
58s [ FAIL 4 | WARN 0 | SKIP 0 | PASS 0 ]
58s
58s ══ Failed tests
══
Source: r-cran-arsenal
Version: 3.6.3-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
48s [ FAIL 6 | WARN 0 | SKIP 12 | PASS 471 ]
48s
48s ══ Skipped tests
══
Source: r-bioc-sparsematrixstats
Version: 1.10.0+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
74s [ FAIL 1 | WARN 1 | SKIP 21 | PASS 1753 ]
74s
74s ══ Skipped tests
═
Source: r-bioc-scater
Version: 1.26.1+ds-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
168s [ FAIL 6 | WARN 4 | SKIP 0 | PASS 505 ]
168s
168s ══ Failed tests
══
Source: r-bioc-s4vectors
Version: 0.36.1-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
110s RUNIT TEST PROTOCOL -- Wed Jun 28 00:17:58 2023
110s ***
110s Number
Source: r-bioc-mutationalpatterns
Version: 3.8.1+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
147s [ FAIL 4 | WARN 4 | SKIP 0 | PASS 271 ]
147s
147s ══ Failed tests
═
Source: r-bioc-complexheatmap
Version: 2.14.0+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
120s Set `ht_opt$message = FALSE` to turn off this message.
120s > draw(ht, test = TRUE)
120s Error in Cairo(
Source: r-bioc-biomart
Version: 2.54.0+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
154s [ FAIL 1 | WARN 0 | SKIP 1 | PASS 146 ]
154s
154s ══ Skipped tests
══
Source: r-bioc-biocneighbors
Version: 1.16.0+ds-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fail with r-base (4.3.1-1):
344s [ FAIL 6 | WARN 488 | SKIP 0 | PASS 3372 ]
344s
344s ══ Failed tests
═
Processing control commands:
> fixed -1 1:15.0.7-2
Bug #1036614 [python3-lldb-15] python3-lldb-15: broken symlinks:
/usr/lib/llvm-15/lib/python3.11/dist-packages/lldb/_lldb.cpython-311-x86_64-linux-gnu.so,
/usr/lib/llvm-15/lib/python3/dist-packages/lldb/libLLVM-15.so.1, ...
Marked as fixed in ve
control: fixed -1 1:15.0.7-2
control: close -1
This is fixed for llvm-15+
G.
On Tue, 23 May 2023 11:13:34 +0200 Andreas Beckmann wrote:
Package: python3-lldb-15
Version: 1:15.0.6-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed
Source: r-bioc-bioccheck
Version: 1.34.2+dfsg-1
Severity: serious
Justification: autopkgtest failure
Dear Maintainer,
The autopkgtest of your package fails with r-base (4.3.1-1):
209s RUNIT TEST PROTOCOL -- Tue Jun 27 15:46:32 2023
209s ***
209s N
Processing commands for cont...@bugs.debian.org:
> severity 1038733 serious
Bug #1038733 {Done: Andreas Tille } [src:r-cran-rgeos]
r-cran-rgeos: autopkgtest failure with GEOS 3.12
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistan
Your message dated Wed, 28 Jun 2023 02:54:54 +
with message-id
and subject line Bug#1039621: fixed in sra-sdk 3.0.3+dfsg-6
has caused the Debian Bug report #1039621,
regarding libngs-jni: Installs shared object in wrong directory
to be marked as done.
This means that you claim that the proble
On 2023-06-27 17:35, Bastian Germann wrote:
Am 28.06.23 um 00:13 schrieb Richard Laager:
The last bugfix release took them more than 3 years and when #767 is
released is unknown.
When a release happens is irrelevant, as you can carry #767 as a patch
in the Debian package until then.
Even
The original submitter replied off the tracker (probably by accident).
I'll summarize here.
The ntp.conf he included is the stock ntp.conf.
He indicated he will try to get a backtrace.
--
Richard
Guillem Jover writes:
> /usr/lib/$(DEB_HOST_MULTIARCH)/jni/libncbi-ngs.so
>
> Where the variable has not been expanded and appears as is. So the
> shared object will not be found.
Oops, so it does; automatic testing evidently missed that due to running
with libncbi-ngs-dev installed. I went w
Doesn't fix the problem.
Your message dated Wed, 28 Jun 2023 00:52:20 +
with message-id
and subject line Bug#1039625: fixed in sl-modem 2.9.11~20110321-18
has caused the Debian Bug report #1039625,
regarding sl-modem-dkms: module fails to build for Linux 6.3, 6.4
to be marked as done.
This means that you claim that t
Your message dated Wed, 28 Jun 2023 00:52:19 +
with message-id
and subject line Bug#1039572: fixed in sl-modem 2.9.11~20110321-18
has caused the Debian Bug report #1039572,
regarding sl-modem-dkms: module fails to build for -cloud kernel, retitle -1
sl-modem-dkms: module fails to build for Li
Processing commands for cont...@bugs.debian.org:
> clone 1039572 -1
Bug #1039572 [sl-modem-dkms] sl-modem-dkms: module fails to build for -cloud
kernel, retitle -1 sl-modem-dkms: module fails to build for Linux 6.4
Bug 1039572 cloned as bug 1039626
> retitle -1 sl-modem-dkms: module fails to buil
Processing commands for cont...@bugs.debian.org:
> clone 1039572 -1
Bug #1039572 [sl-modem-dkms] sl-modem-dkms: module fails to build for Linux
6.3, 6.4
Bug 1039572 cloned as bug 1039625
> retitle 1039572 sl-modem-dkms: module fails to build for -cloud kernel,
> retitle -1 sl-modem-dkms: module
On Tue, Jun 27, 2023 at 11:39:12AM +0200, Philipp Marek wrote:
> Package: firefox
> Version: 114.0-1
> Severity: grave
> X-Debbugs-Cc: phil...@marek.priv.at
>
> Websites that need randomness ([1]) are broken,
> on both Debian FF 113.0.2 and 114.0 (114.0.2 not yet available for amd64).
>
> Reprodu
Am 28.06.23 um 00:13 schrieb Richard Laager:
Wait a minute... You are a maintainer for cyrus-sasl.
Just the package maintainer in Debian.
You have already addressed the BSD-4-clause-KTH in the latest upload.
That is true, which I have noted on the other bug.
You also fixed debian/copyright
Wait a minute... You are a maintainer for cyrus-sasl.
You have already addressed the BSD-4-clause-KTH in the latest upload.
You also fixed debian/copyright to reference BSD-3-Clause-Attribution in
the latest upload. That license is fine for the reasons I mentioned.
That just leaves the MD5 st
Package: libngs-jni
Version: 3.0.3+dfsg-5
Severity: serious
Hi
This package installs the shared object in the following _literal_
pathname:
/usr/lib/$(DEB_HOST_MULTIARCH)/jni/libncbi-ngs.so
Where the variable has not been expanded and appears as is. So the
shared object will not be found.
Th
Am 27.06.23 um 23:34 schrieb Richard Laager:
Cyrus SASL has reverse (binary) dependencies in the ballpark of 7,500. Quickly taking that list through UDD gives me
just over 4,500 source packages. Surely, a large number of those are going to be GPL licensed. Is your plan to file
Severity: serious
Bastian,
I see you have raised the severity on this bug again.
What is your goal here?
Cyrus SASL has reverse (binary) dependencies in the ballpark of 7,500.
Quickly taking that list through UDD gives me just over 4,500 source
packages. Surely, a large number of those are going to be GPL lice
Your message dated Tue, 27 Jun 2023 21:20:27 +
with message-id
and subject line Bug#1018018: fixed in wmforkplop 0.9.3-3
has caused the Debian Bug report #1018018,
regarding wmforkplop: FTBFS with imlib2 1.9.1
to be marked as done.
This means that you claim that the problem has been dealt wit
Control: tag -1 patch
On 27/06/2023 19.21, Richard Lewis wrote:
header.txt has not been modified since 2015.
I've found three versions (with sightly different spelling):
* lenny
* squeeze, wheezy, jessie
* stretch .. today
it is a simple yext file that is installed with debian/logcheck.insta
Processing control commands:
> tag -1 patch
Bug #1039591 [logcheck] logcheck: prompting due to modified conffiles which
were not modified by the user: /etc/logcheck/header.txt
Added tag(s) patch.
--
1039591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039591
Debian Bug Tracking System
Co
Processing commands for cont...@bugs.debian.org:
> tags 1028124 + sid
Bug #1028124 {Done: Andreas Tille } [r-cran-hunspell]
r-cran-hunspell: old copy of internal hunspell headers breaks (autopkg)test
with hunspell 1.7.2
Added tag(s) sid.
> thanks
Stopping processing here.
Please contact me if y
Processing commands for cont...@bugs.debian.org:
> # hunspell 1.7.2 is now in unstable
> severity 1028124 serious
Bug #1028124 {Done: Andreas Tille } [r-cran-hunspell]
r-cran-hunspell: old copy of internal hunspell headers breaks (autopkg)test
with hunspell 1.7.2
Severity set to 'serious' from '
Your message dated Tue, 27 Jun 2023 20:07:47 +
with message-id
and subject line Bug#1035347: fixed in boxer-data 10.8.28+deb11u1
has caused the Debian Bug report #1035347,
regarding boxer-data: generates dependencies on no longer installable lightning
to be marked as done.
This means that you
Your message dated Tue, 27 Jun 2023 19:59:10 +
with message-id
and subject line Bug#1037926: fixed in wike 2.0.1-3
has caused the Debian Bug report #1037926,
regarding wike: version 2.0.1-2 failed to start
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Source: python-can
Version: 4.2.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-can the autopkgtest of python-can fails
in testing when that autopkgtest is run with the binary packages of
python-can from unstable on
Processing control commands:
> found -1 nmap/7.94+dfsg1-1
Bug #1039613 [src:nmap, src:udptunnel] nmap breaks udptunnel autopkgtest:
UDPTunnel communication failed
Marked as found in versions nmap/7.94+dfsg1-1.
> found -1 udptunnel/1.1-9
Bug #1039613 [src:nmap, src:udptunnel] nmap breaks udptunnel
Source: nmap, udptunnel
Control: found -1 nmap/7.94+dfsg1-1
Control: found -1 udptunnel/1.1-9
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of nmap the autopkgtest of udptunnel fails in
testing when t
Package: libtool
Version: 2.4.6-15
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: erjoa...@gmail.com
Dear Maintainer,
While building isc-dhcpd-server, I tried using autoreconf as per instructions
to generate the ./configure file.
But running `autoreconf -i` on t
Processing control commands:
> found -1 celery/5.3.1-1
Bug #1039611 [src:celery, src:python-django-celery-beat] celery breaks
python-django-celery-beat autopkgtest: 'zoneinfo.ZoneInfo' object has no
attribute 'zone'
Marked as found in versions celery/5.3.1-1.
> found -1 python-django-celery-beat
Source: celery, python-django-celery-beat
Control: found -1 celery/5.3.1-1
Control: found -1 python-django-celery-beat/2.4.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of celery the autopkgtest of
Hi Paul,
On 27 June 2023 at 20:08, Paul Gevers wrote:
| Hi Dirk,
|
| On 26-06-2023 22:21, Dirk Eddelbuettel wrote:
| > I really appreciate the diligence and detail you put into this.
| >
| > But I would like to offer a simple shortcut. I am also CCing debian-r again
| > as this has come up ti
Hi Dirk,
On 26-06-2023 22:21, Dirk Eddelbuettel wrote:
I really appreciate the diligence and detail you put into this.
But I would like to offer a simple shortcut. I am also CCing debian-r again
as this has come up time and time again, is guaranteed to come up again for
as long as combine auto
Control: retitle -1 freespace2: FTBFS with libsdl1.2-compat-dev:
'malloc_usable_size' was not declared in this scope
(cc'ing adetiste because he was looking at this package recently; the
SDL2-based new upstream version will close both #1038352 and this bug,
assuming the SDL2 version compiles succ
Processing control commands:
> retitle -1 freespace2: FTBFS with libsdl1.2-compat-dev: 'malloc_usable_size'
> was not declared in this scope
Bug #1012232 [src:freespace2] freespace2: missing B-D: pkg-config,
libglu1-mesa-dev
Changed Bug title to 'freespace2: FTBFS with libsdl1.2-compat-dev:
'ma
header.txt has not been modified since 2015.
it is a simple yext file that is installed with debian/logcheck.install
the only change is that it used to be installed into /usr/share but got
moved to /etc to be a conffile in 2021. This didnt trigger any piuparts
issues and there was no change to th
Processing control commands:
> retitle -1 sl-modem-dkms: module fails to build for Linux 6.3, 6.4
Bug #1039572 [sl-modem-dkms] sl-modem-dkms: module fails to build for Linux 6.4
Changed Bug title to 'sl-modem-dkms: module fails to build for Linux 6.3, 6.4'
from 'sl-modem-dkms: module fails to bui
Followup-For: Bug #1039572
Control: retitle -1 sl-modem-dkms: module fails to build for Linux 6.3, 6.4
it also fails on i386 for Linux 6.3:
https://ci.debian.net/data/autopkgtest/testing/i386/s/sl-modem/34615841/log.gz
DKMS make.log for sl-modem-2.9.11~20110321 for kernel 6.1.0-9-686-pae (i686)
Your message dated Tue, 27 Jun 2023 16:23:07 +
with message-id
and subject line Bug#1039528: fixed in insighttoolkit5 5.3.0-4
has caused the Debian Bug report #1039528,
regarding plastimatch: FTBFS: Could not find a package configuration file
provided by "VTK"
to be marked as done.
This mean
On Monday, June 26, 2023 6:15:06 P.M. CDT Adrian Bunk wrote:
> Control: reassign -1 libinsighttoolkit5-dev 5.3.0-3
> Control: affects -1 src:plastimatch
>
> There are actually tow separate issues, both in libinsighttoolkit5-dev:
Thanks for bringing this to my attention.
> 1. The VTK build depend
Processing commands for cont...@bugs.debian.org:
> severity 1038242 serious
Bug #1038242 [rust-ashpd] Does not build against gtk 0.5
Severity set to 'serious' from 'normal'
> retitle 1038242 'Needs wayland 0.30'
Bug #1038242 [rust-ashpd] Does not build against gtk 0.5
Changed Bug title to ''Needs
Your message dated Tue, 27 Jun 2023 14:53:50 +
with message-id
and subject line Bug#1029434: fixed in pydrive2 1.15.0-3
has caused the Debian Bug report #1029434,
regarding python3-pydrive2: ships md5sums without files:
/usr/lib/python3/dist-packages/pydrive2/test/*
to be marked as done.
Thi
Package: logcheck
Version: 1.4.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being modified and then
prompted the user for an action. As there is n
Control: tag -1 pending
Hello,
Bug #1029434 in pydrive2 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:
https://salsa.debian.org/python-team/packages/pydrive2/-/commit/315d85f9b2a5c8dff
Processing control commands:
> tag -1 pending
Bug #1029434 [python3-pydrive2] python3-pydrive2: ships md5sums without files:
/usr/lib/python3/dist-packages/pydrive2/test/*
Added tag(s) pending.
--
1029434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029434
Debian Bug Tracking System
Cont
Processing commands for cont...@bugs.debian.org:
> tags 1039531 + sid trixie
Bug #1039531 [src:autoconf2.64] autoconf2.64: Keep out of testing
Added tag(s) trixie and sid.
> tags 1038746 + sid trixie
Bug #1038746 [src:python-cryptography] build dependency missing in testing
Added tag(s) trixie and
Processing commands for cont...@bugs.debian.org:
> retitle 1038197 "enigma: Depends on SDL 1.2; unmaintained (1.30 is SDL2)"
Bug #1038197 [src:enigma] enigma: Depends on SDL 1.2 and is unmaintained
(upstream
Changed Bug title to '"enigma: Depends on SDL 1.2; unmaintained (1.30 is
SDL2)"' from 'e
Processing commands for cont...@bugs.debian.org:
> retitle 1038197 enigma: Depends on SDL 1.2 and is unmaintained (upstream
Bug #1038197 [src:enigma] enigma: Depends on SDL 1.2
Changed Bug title to 'enigma: Depends on SDL 1.2 and is unmaintained (upstream'
from 'enigma: Depends on SDL 1.2'.
> 1.3
Package: sl-modem-dkms
Version: 2.9.11~20110321-17
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
1.) There is an autopkgtest regression with the -cloud kernel,
preventing migration to testing (therefore severity serious):
https://ci.debian.net/data/autopkgtest/testing/amd
Package: firefox
Version: 114.0-1
Severity: grave
X-Debbugs-Cc: phil...@marek.priv.at
Websites that need randomness ([1]) are broken,
on both Debian FF 113.0.2 and 114.0 (114.0.2 not yet available for amd64).
Reproduced with a new profile without any plugins.
strace shows FF being able to use ge
Processing commands for cont...@bugs.debian.org:
> block 1038197 with 902855
Bug #1038197 [src:enigma] enigma: Depends on SDL 1.2
1038197 was not blocked by any bugs.
1038197 was blocking: 1038036 1038037 1038070
Added blocking bug(s) of 1038197: 902855
> block 1039438 with 902855
Bug #1039438 [sr
Hi,
On 23-06-26 10:27:37, Antoine Beaupré wrote:
> Just to make sure, someone still is working on this to make sure it's
> fixed in bookworm?
I'll take care of it.
> I guess the first step is to wait for the package to transition to
> trixie and then do the -pu? I suspect it will be hard to test
Package: src:seqan3
Version: 3.2.0+ds-6
Severity: serious
Tags: sid trixie
seqan3's autopkg tests fail to build, letting the tests to not succeed:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/seqan3/34898359/log.gz
Your message dated Tue, 27 Jun 2023 07:34:21 +
with message-id
and subject line Bug#1039460: fixed in jpeg-xl 0.9.0~git20230623.689da0f-3
has caused the Debian Bug report #1039460,
regarding libjxl-gdk-pixbuf: fails to purge: gdk-pixbuf-query-loaders: not found
to be marked as done.
This mean
92 matches
Mail list logo
