On 29 January 2023 at 01:58, Adrian Bunk wrote:
| Package: r-cran-pbkrtest
| Version: 0.5.2-1
| Severity: serious
|
| The following packages have unmet dependencies:
| r-cran-pbkrtest : Depends: r-cran-lme4 (>= 1.1.31) but it is not going to be
installed
|
| You might want to reconsider
|
|
Processing control commands:
> severity -1 grave
Bug #1028081 [argus-server] argus-server: Produces corrupted argus.out file
Severity set to 'grave' from 'important'
--
1028081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028081
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing commands for cont...@bugs.debian.org:
> clone 1011445 -1
Bug #1011445 {Done: Daniel Leidert }
[ruby-gitlab-license-finder,ruby-license-finder]
ruby-gitlab-license-finder,ruby-license-finder: error when trying to install
together
Bug 1011445 cloned as bug 1029919
> reassign 1011445
Package: gstreamer1.0-plugins-good
Version: 1.22.0-3
Severity: serious
Justification: Policy 7.6.1
> Unpacking gstreamer1.0-plugins-good:amd64 (1.22.0-3) over (1.20.5-2) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-qofiMB/43-gstreamer1.0-plugins-good_1.22.0-3_amd64.deb
>
Processing commands for cont...@bugs.debian.org:
> reopen 1029919
Bug #1029919 {Done: Daniel Leidert }
[ruby-gitlab-license-finder] ruby-gitlab-license-finder,ruby-license-finder:
error when trying to install together
Bug reopened
Ignoring request to alter fixed versions of bug #1029919 to the
Control: retitle -1 gopacket: FTBFS with libpcap >= 1.10.2
Control: tags -1 + confirmed
Control: forwarded -1 https://github.com/google/gopacket/issues/1088
It appears that libpcap 1.10.2 introduced some change that is causing
the test failure. Manually downgrading to libpcap 1.10.1-4 from
Processing control commands:
> retitle -1 gopacket: FTBFS with libpcap >= 1.10.2
Bug #1028841 [src:gopacket] gopacket: FTBFS: pcap_test.go:26: Error
returned for nonexistent file: /path/to/nonexistent/file: No such file or
directory
Changed Bug title to 'gopacket: FTBFS with libpcap >=
Processing commands for cont...@bugs.debian.org:
> reopen 1016936
Bug #1016936 {Done: David Prévot } [dwz] dwz: Unknown
debugging section .debug_addr causes some builds to fail
Bug reopened
Ignoring request to alter fixed versions of bug #1016936 to the same values
previously set
> thanks
Processing commands for cont...@bugs.debian.org:
> close 1029328 0.11.0-1
Bug #1029328 [src:rust-imagesize] rust-imagesize: autopkgtest failure
Marked as fixed in versions rust-imagesize/0.11.0-1.
Bug #1029328 [src:rust-imagesize] rust-imagesize: autopkgtest failure
Marked Bug as done
> thanks
Source: nagios-plugins-contrib
Version: 38.20230124
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nagios-plugins-contrib/30770474/log.gz
...
autopkgtest [00:15:02]: test command7: /usr/lib/nagios/plugins/check_ssl_cert
-H www.debian.org
autopkgtest [00:15:02]: test
Your message dated Sun, 29 Jan 2023 03:32:28 +0100
with message-id <763d54b8be69240e04d817c07df9c81007507c4a.ca...@gmx.net>
and subject line Bug#1029915: fixed in mikutter 5.0.4+dfsg1-2
has caused the Debian Bug report #1029915,
regarding mikutter: Depends: ruby-gtk3 (>= 3.4.9) but it is not going
Your message dated Sun, 29 Jan 2023 00:34:59 +
with message-id
and subject line Bug#1029908: fixed in libjna-java 5.13.0-2
has caused the Debian Bug report #1029908,
regarding libjna-java: JNA HelloWorld fails on armhf
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 29 Jan 2023 01:08:28 +
with message-id
and subject line Bug#1029917: fixed in r-cran-pbkrtest 0.5.2-2
has caused the Debian Bug report #1029917,
regarding r-cran-pbkrtest: Depends: r-cran-lme4 (>= 1.1.31) but it is not going
to be installed
to be marked as done.
This
Your message dated Sun, 29 Jan 2023 04:18:28 +0200
with message-id
and subject line Fixed since 0.25.0-1
has caused the Debian Bug report #995359,
regarding ruby-gitlab-labkit: autopkgtest needs update for new version of
ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10)
to be marked
Your message dated Sun, 29 Jan 2023 03:26:12 +0100
with message-id
and subject line FTBFS was caused by ruby-qdbm not being built with Ruby 3.1
has caused the Debian Bug report #1019604,
regarding bsfilter: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that
Source: dials
Version: 3.12.1+dfsg3-4
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/arm64/d/dials/30737888/log.gz
https://ci.debian.net/data/autopkgtest/testing/ppc64el/d/dials/30737889/log.gz
...
== FAILURES ===
Package: msmtp-mta
Version: 1.8.22-1
Severity: serious
https://piuparts.debian.org/sid/fail/msmtp-mta_1.8.22-3.log
...
Purging configuration files for msmtp-mta (1.8.22-3) ...
/var/lib/dpkg/info/msmtp-mta.postrm: 8: deluser: not found
dpkg: error processing package msmtp-mta (--purge):
On Fri, Jan 27, 2023 at 9:42 PM Andreas Tille wrote:
>
> Am Fri, Jan 27, 2023 at 08:21:46PM +0800 schrieb Aron Xu:
> > On Fri, Jan 27, 2023 at 7:12 PM Andreas Tille wrote:
> > > make: *** [debian/rules:83: binary] Terminated
> > > ninja: build stopped: interrupted by user.
> > >
> > > could
Hi!
I managed now to reproduce this. The purge step is not relevant, but
simply the upgrade itself.
In clean Docker container with Debian unstable:
$ apt install -y mariadb-server-10.6
-> install successful
$ apt full-upgrade -y
-> does nothing
$ service mariadb restart
Stopping MariaDB
Processing commands for cont...@bugs.debian.org:
> reassign 1029911 librust-rustls-dev 0.20.8-1
Bug #1029911 [src:rust-ureq] rust-ureq FTBFS: error: unable to load build
system class 'cargo': Can't locate String/ShellQuote.pm
Bug reassigned from package 'src:rust-ureq' to 'librust-rustls-dev'.
Processing control commands:
> submitter -1 Thorsten Glaser
Bug #1029235 {Done: Santiago Ruano Rincón } [grep] grep:
sometimes mistakenly matches lines when last of multiple patterns includes
backref
Changed Bug submitter to 'Thorsten Glaser ' from 'g1
'.
--
1029235:
Control: submitter -1 Thorsten Glaser
On Fri, 02 Dec 2022 02:12:20 +0100 Thorsten Glaser wrote:
> Package: grep
> Version: 3.6-1
> Followup-For: Bug #930247
> X-Debbugs-Cc: t...@mirbsd.de
> Control: found 930247 3.8-3
> Control: severity 930247 serious
> Control: retitle 930247 grep: does not
Control: tags 1024287 + patch
Control: tags 1024287 + pending
Dear maintainer,
I've prepared an NMU for django-assets (versioned as 2.0-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru django-assets-2.0/debian/changelog
Processing control commands:
> tags 1024287 + patch
Bug #1024287 [src:django-assets] django-assets: FTBFS against python 3.11
Bug #1024564 [src:django-assets] django-assets FTBFS: re.error: global flags
not at the start of the expression at position 6
Bug #1026496 [src:django-assets]
Hello Steve McIntyre,
As you might have noticed I've taken the liberty to NMU strace into
*experimental*.
I've done so based on my past experience that strace can have many
architecture specific problems, to give me a picture of what the
situation is for the latest upstream 6.1 release.
(And
Your message dated Sat, 28 Jan 2023 15:29:54 +0100
with message-id
and subject line Re: libde265: CVE-2020-21594 CVE-2020-21595 CVE-2020-21596
CVE-2020-21597 CVE-2020-21599 CVE-2020-21601 CVE-2020-21603 CVE-2020-21604
CVE-2020-21605 CVE-2020-21606
has caused the Debian Bug report #1004963,
Processing commands for cont...@bugs.debian.org:
> limit source tar
Limiting to bugs with field 'source' containing at least one of 'tar'
Limit currently set to 'source':'tar'
> tags 1026204 + pending
Bug #1026204 [tar] tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64
Added tag(s)
reassign 1028848 python-zeroconf 0.47.1-1
fixed 0.47.1-2
close 1028848
stop
This was a problem with zeroconf instead, which has been fixed.
Re-assigned and closed.
--
Best,
Nilesh
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> fixed 1028848 0.47.1-2
Bug #1028848 {Done: Nilesh Patra } [python-zeroconf]
python-miio: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.11" returned exit code 13
There is no source info for the package
Processing commands for cont...@bugs.debian.org:
> forcemerge 1026496 1024564
Bug #1026496 [src:django-assets] django-assets: FTBFS: dh_auto_test: error:
pybuild --test --test-nose -i python{version} -p "3.11 3.10" returned exit code
13
Bug #1024287 [src:django-assets] django-assets: FTBFS
Processing commands for cont...@bugs.debian.org:
> severity 1029806 serious
Bug #1029806 [steam-installer] steam-installer: Launching Steam (Failed). You
are not authorised to execute this file
Severity set to 'serious' from 'important'
> tags 1029806 + pending
Bug #1029806 [steam-installer]
El 28/1/23 a las 10:11, Vincent Bernat escribió:
On 2023-01-28 00:20, Santiago Vila wrote:
Release Policy exists as a canonical list of what should be RC and > what not,
and it's intended to avoid stupid discussions like this one.
Extending build-essential is easier than asking many people
El 28/1/23 a las 13:59, Adrian Bunk escribió:
Policy 4.2 also says
Source packages should specify which binary packages they require to
be installed or not to be installed in order to build correctly.
We are not following the "not to be installed" part,
which is the can of worms you would
Source: ruby-rack
Version: 2.2.4-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerabilities were published for ruby-rack.
CVE-2022-44570[0]:
| rack: Fix ReDoS in Rack::Utils.get_byte_ranges
CVE-2022-44571[1]:
| rack: Fix
Processing control commands:
> tag -1 pending
Bug #1028826 [src:python-xlib] herbstluftwm: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
Ignoring request to alter tags of bug #1028826 to the same tags previously set
--
1028826:
Control: tag -1 pending
Hello,
Bug #1028826 in python-xlib 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:
Your message dated Sat, 28 Jan 2023 07:59:20 +
with message-id
and subject line Bug#1027245: fixed in symfit 0.5.5-2
has caused the Debian Bug report #1027245,
regarding symfit: autopkgtest fail with numpy/1.24.1
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> close 1027638
Bug #1027638 [src:pdm] pdm: FTBFS: ImportError: cannot import name
'LegacyVersion' from 'packaging.version'
(/usr/lib/python3/dist-packages/packaging/version.py)
Marked Bug as done
> thanks
Stopping processing here.
Please
On 2023-01-28 00:20, Santiago Vila wrote:
Release Policy exists as a canonical list of what should be RC and > what not,
and it's intended to avoid stupid discussions like this one.
Extending build-essential is easier than asking many people to do
pointless work to satisfy a set of
It seems the module does not yet support Python newer than 3.7 (3.9 in the
latest version on Github), see
https://github.com/ilius/pyglossary/tree/master/pyglossary/plugin_lib
Copying the folder pyglossary/plugin_lib/py37 to py310 and py311 fixes this
build-error for me.
Your message dated Sat, 28 Jan 2023 10:50:19 +
with message-id
and subject line Bug#1029044: fixed in gcc-12-cross-mipsen 3+c2
has caused the Debian Bug report #1029044,
regarding gcc-12-cross-mipsen: source and binary version go out of sync
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> reopen 997274
Bug #997274 {Done: Andreas Henriksson } [src:strace] strace:
FTBFS: ../../tests/perf_event_open.c:187:25: error: array subscript ‘struct
perf_event_attr[0]’ is partly outside array bounds of ‘unsigned char[120]’
Hi,
Le Wed, Jan 18, 2023 at 01:24:37AM +0100, Helge Deller a écrit :
> On Sat, 14 Jan 2023 20:38:38 +0100 Andreas Henriksson
> wrote:
> > Here's a slightly different patch to implement basically the same thing
>
> Yes, I like this patch better too.
Unfortunately, even if both patches allow me
Your message dated Sat, 28 Jan 2023 12:33:02 +
with message-id
and subject line Bug#1029799: fixed in msmtp 1.8.22-3
has caused the Debian Bug report #1029799,
regarding msmtp fails to purge when adduser is not installed
to be marked as done.
This means that you claim that the problem has
On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
>...
> * Those bugs are RC by definition and have been for a long time.
>...
Please provide a pointer where a release team member has said so
explicitly in recent years.
In my experience they are usually saying that FTBFS that do
On 2023-01-28 13:59, Adrian Bunk wrote:
I am not saying that trying to force maintainers to spend time on such
issues by making them release critical is better, but you are also
creating extra work and frustration for the people who are doing QA work
in Debian.
It also pushes some maintainers
Am Fri, Jan 27, 2023 at 11:12:10PM +0100 schrieb Étienne Mollier:
> favor of funtion tbb::parallel_pipeline). I'm a bit dry for the
> moment and will have the weekend busy, so if someone wants to
> take over from here, please go ahead.
I'll see what I can do, thanks in any case
Andreas.
--
Your message dated Sat, 28 Jan 2023 14:48:53 +0530
with message-id <20230128091853.cuzx362wehupa...@nileshpatra.info>
and subject line Re: ruby-fogbugz: FTBFS: ERROR: Test "ruby3.1" failed:
:85:in
`require': cannot load such file -- mocha/mini_test (LoadError)
has caused the Debian Bug report
Your message dated Sat, 28 Jan 2023 13:09:29 +
with message-id
and subject line Bug#1029806: fixed in steam-installer 1:1.0.0.75+ds-5
has caused the Debian Bug report #1029806,
regarding steam-installer: Launching Steam (Failed). You are not authorised to
execute this file
to be marked as
Processing commands for cont...@bugs.debian.org:
> reassign 1028848 python-zeroconf 0.47.1-1
Bug #1028848 [src:python-miio] python-miio: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Bug reassigned from package 'src:python-miio'
Your message dated Sat, 28 Jan 2023 12:26:47 +
with message-id
and subject line Bug#1027877: fixed in jool 4.1.9-1
has caused the Debian Bug report #1027877,
regarding jool: please switch to B-D: dh-sequence-dkms (or dh-dkms)
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 28 Jan 2023 12:26:47 +
with message-id
and subject line Bug#1029268: fixed in jool 4.1.9-1
has caused the Debian Bug report #1029268,
regarding jool: FTBFS: multiple definition of `_init'
to be marked as done.
This means that you claim that the problem has been dealt
On Sat, Jan 28, 2023 at 12:20:16AM +0100, Santiago Vila wrote:
> El 27/1/23 a las 22:37, Adrian Bunk escribió:
> > On Fri, Dec 16, 2022 at 02:15:13AM +0100, Santiago Vila wrote:
...
> > I am right now looking at #1027382, and the first question is how I can
> > make apt remove e2fsprogs so that I
Source: amanda
Version: 1:3.5.1-9
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerabilities were published for amanda.
CVE-2022-37704[0], CVE-2022-37705[1].
If you fix the vulnerabilities
Processing commands for cont...@bugs.debian.org:
> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'
> tags 1029046 + pending
Bug #1029046 [src:linux] S3 suspend broken on AMD Ryzen Pro 7 5850U
Added tag(s) pending.
Your message dated Sat, 28 Jan 2023 16:07:44 +0100
with message-id
and subject line not a bug in bullseye
has caused the Debian Bug report #1027360,
regarding calcurse: FTBFS in bullseye (missing build-depends on tzdata)
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 28 Jan 2023 16:07:44 +0100
with message-id
and subject line not a bug in bullseye
has caused the Debian Bug report #1027364,
regarding golang-github-go-co-op-gocron: FTBFS in bullseye (missing
build-depends on tzdata)
to be marked as done.
This means that you claim that
Your message dated Sat, 28 Jan 2023 16:07:44 +0100
with message-id
and subject line not a bug in bullseye
has caused the Debian Bug report #1027370,
regarding golang-github-powerman-check: FTBFS in bullseye (missing
build-depends on tzdata)
to be marked as done.
This means that you claim that
Your message dated Sat, 28 Jan 2023 16:07:44 +0100
with message-id
and subject line not a bug in bullseye
has caused the Debian Bug report #1027381,
regarding siridb-server: FTBFS in bullseye (missing build-depends on tzdata)
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tags -1 +unreproducible
Bug #1029423 [src:jc] jc: FTBFS in bookworm (undeclared build-dependency on
tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1029423 [src:jc] jc: FTBFS in bookworm (undeclared build-dependency on
tzdata)
Severity set to
Processing control commands:
> tags -1 +unreproducible
Bug #1029419 [src:golang-github-mattn-go-sqlite3]
golang-github-mattn-go-sqlite3: FTBFS in bookworm (undeclared build-dependency
on tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1029419
Processing control commands:
> tags -1 +unreproducible
Bug #1029424 [src:kopeninghours] kopeninghours: FTBFS in bookworm (undeclared
build-dependency on tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1029424 [src:kopeninghours] kopeninghours: FTBFS in bookworm (undeclared
Control: tags -1 +unreproducible
Control: severity -1 wishlist
Hi!
You've done a MBF despite _negative_ consensus in several discussions
(debian-devel, debootstrap, policy, ...); folks seem to be in agreement
that either the Policy doesn't require building in an environment that
is explicitly
Processing control commands:
> tags -1 +unreproducible
Bug #1027905 [src:golang-github-arran4-golang-ical]
golang-github-arran4-golang-ical: FTBFS in bookworm (undeclared
build-dependency on tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1027905
Processing control commands:
> tags -1 +unreproducible
Bug #1027907 [src:golang-github-go-git-go-git] golang-github-go-git-go-git:
FTBFS in bookworm (undeclared build-dependency on tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1027907 [src:golang-github-go-git-go-git]
Processing control commands:
> tags -1 +unreproducible
Bug #1029418 [src:gnote] gnote: FTBFS in bookworm (undeclared build-dependency
on tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1029418 [src:gnote] gnote: FTBFS in bookworm (undeclared build-dependency
on tzdata)
Severity
Processing control commands:
> tags -1 +unreproducible
Bug #1029462 [src:golang-github-nats-io-jwt] golang-github-nats-io-jwt: FTBFS
in bookworm (undeclared build-dependency on tzdata)
Added tag(s) unreproducible.
> severity -1 wishlist
Bug #1029462 [src:golang-github-nats-io-jwt]
Control: close 1027364
On Sat, Jan 28, 2023 at 04:31:25PM +0100, Santiago Vila wrote:
> retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends
> on tzdata)
> reopen 1027364
> found 0.5.0-2
> thanks
>
> Adam, please don't close bugs just because they say "bullseye" in the
Processing control commands:
> close 1027364
Bug #1027364 [src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron:
FTBFS (missing build-depends on tzdata)
Marked Bug as done
--
1027364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027364
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> limit source python-pytest-xprocess
Limiting to bugs with field 'source' containing at least one of
'python-pytest-xprocess'
Limit currently set to 'source':'python-pytest-xprocess'
> tags 1026549 + pending
Bug #1026549
Processing commands for cont...@bugs.debian.org:
> close 1024238 1.0.6-2
Bug #1024238 [src:libequihash] libequihash: binary-any FTBFS
Bug #1028268 [src:libequihash] libequihash: binary-any FTBFS
Marked as fixed in versions libequihash/1.0.6-2.
Marked as fixed in versions libequihash/1.0.6-2.
Bug
Processing commands for cont...@bugs.debian.org:
> close 1024239 1.0.6-2
Bug #1024239 [src:libequihash] libequihash: baseline violation on i386 and
FTBFS on !x86
Marked as fixed in versions libequihash/1.0.6-2.
Bug #1024239 [src:libequihash] libequihash: baseline violation on i386 and
FTBFS on
Processing control commands:
> tag -1 pending
Bug #1019681 [src:samizdat] samizdat: FTBFS with ruby3.1: ERROR: Test "ruby3.1"
failed.
Added tag(s) pending.
--
1019681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #1019681 in samizdat 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: tags -1 confirmed +patch
Hello there,
while at St-Cergue's BSP, I took a look at this issue, so here are my
findings.
* I can confirm it fails to build from source in a main+contrib+non-free
cowbuilder.
* This FTBFS is the consequence of a new requirement from setuptools; see this
Processing control commands:
> tags -1 confirmed +patch
Bug #1029775 [src:pyhst2] pyhst2: FTBFS with setuptools 66: Invalid version:
'2020ca'
Added tag(s) confirmed.
Bug #1029775 [src:pyhst2] pyhst2: FTBFS with setuptools 66: Invalid version:
'2020ca'
Added tag(s) patch.
--
1029775:
Processing commands for cont...@bugs.debian.org:
> reassign 1029403 xtables-addons
Bug #1029403 [shorewall] shorewall: fails to start with "Couldn't load match
`iface':No such file or directory"
Bug reassigned from package 'shorewall' to 'xtables-addons'.
No longer marked as found in versions
Control: tags -1 +pending
So. I have a much shorter (and better) patch, that I'll upload to DELAYED/5 in
few minutes.
See the attached patch, which consists of setting the setup.py version to a
PEP-440-compliant Debian-specific version (which I have confirmed to sort
bigger than "2020ca").
Processing control commands:
> tags -1 +pending
Bug #1029775 [src:pyhst2] pyhst2: FTBFS with setuptools 66: Invalid version:
'2020ca'
Added tag(s) pending.
--
1029775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
El 28/1/23 a las 16:50, Adam Borowski escribió:
Control: close 1027364
On Sat, Jan 28, 2023 at 04:31:25PM +0100, Santiago Vila wrote:
retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends on
tzdata)
reopen 1027364
found 0.5.0-2
thanks
Adam, please don't close bugs just
retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends on
tzdata)
reopen 1027364
found 0.5.0-2
thanks
Adam, please don't close bugs just because they say "bullseye" in the title.
In most cases, I really meant "bullseye and later".
I've now fixed the title to avoid
Processing commands for cont...@bugs.debian.org:
> retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends
> on tzdata)
Bug #1027364 {Done: Adam Borowski }
[src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron: FTBFS in
bullseye (missing build-depends on tzdata)
On 2023-01-27 13:35, Romain Francoise wrote:
Do you mind if I merge them?
Sure, please merge.
Processing commands for cont...@bugs.debian.org:
> tags 1027851 + pending
Bug #1027851 [src:pytorch] pytorch FTBFS with Python 3.11 as default version
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027851:
Your message dated Sat, 28 Jan 2023 16:53:21 +
with message-id
and subject line Bug#1008409: fixed in ruby-tioga 1.19.1-4
has caused the Debian Bug report #1008409,
regarding ctioga2: FTBFS:
:85:in
`require':
/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/Dobjects/Dvector.so: undefined
Processing commands for cont...@bugs.debian.org:
> forwarded 1026740 https://github.com/pyviz-dev/pyct/issues/94
Bug #1026740 [src:pyct] pyct: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> block 1025884 with 1028113
Bug #1025884 {Done: Paul Gevers } [src:ddnet] src:ddnet:
fails to migrate to testing for too long: FTBFS on s390x
1025884 was not blocked by any bugs.
1025884 was not blocking any bugs.
Added blocking bug(s) of
Hi David,
* David Prévot [2023-01-28 17:44]:
I prepared an upload (new upstream release) of this package in order to
fix this RC-bug as part of the BSP currently happening in St-Cergue,
Switzerland. A merge request has been submitted.
Processing commands for cont...@bugs.debian.org:
> limit source nekohtml
Limiting to bugs with field 'source' containing at least one of 'nekohtml'
Limit currently set to 'source':'nekohtml'
> tags 1021739 + pending
Bug #1021739 [src:nekohtml] nekohtml: CVE-2022-24839
Added tag(s) pending.
>
Processing commands for cont...@bugs.debian.org:
> found 1027364 0.5.0-2
Bug #1027364 [src:golang-github-go-co-op-gocron] golang-github-go-co-op-gocron:
FTBFS (missing build-depends on tzdata)
Ignoring request to alter found versions of bug #1027364 to the same values
previously set
> thanks
Processing commands for cont...@bugs.debian.org:
> forwarded 1028833 https://github.com/pimutils/khal/issues/1205
Bug #1028833 [src:khal] khal: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.10 3.11" returned exit code 13
Set Bug forwarded-to-address to
Source: bazel-bootstrap
Version: 4.2.3+ds-2
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bazel-bootstrap/30777521/log.gz
...
autopkgtest [09:12:31]: test java-1-hello: [---
Loading:
Loading: 0 packages loaded
Analyzing: target
Your message dated Sat, 28 Jan 2023 17:28:12 +
with message-id
and subject line Bug#1019681: fixed in samizdat 0.7.1-2
has caused the Debian Bug report #1019681,
regarding samizdat: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.
This means that you claim that the
Your message dated Sat, 28 Jan 2023 15:44:29 +0100
with message-id
and subject line Re: freedroidrpg: ftbfs with GCC-10
has caused the Debian Bug report #957229,
regarding freedroidrpg: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tag -1 -patch
Hi!
The alleged patch doesn't fix the FTBFS. Besides the non-bug (per numerous
discussions on debian-devel and elsewhere) of non-depending on a required
package "tzdata", the package fails from an actual build failure even in
a non-sabotaged build chroot.
I'm thus
Processing control commands:
> tag -1 -patch
Bug #1029430 [src:reposurgeon] reposurgeon: FTBFS in bookworm (undeclared
build-dependency on tzdata)
Removed tag(s) patch.
--
1029430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029430
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> severity 1024831 important
Bug #1024831 [src:linux] xorg: xserver fails to resume after suspend-to-disk
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1024831:
Hi,
Le Sat, Dec 31, 2022 at 11:42:12PM +0100, Timo R=F6hling a =E9crit :
> forwarded 1026549 https://github.com/pytest-dev/pytest-xprocess/issues/117
Thanks Timo,
I prepared an upload (new upstream release) of this package in order to
fix this RC-bug as part of the BSP currently happening in
Source: harfbuzz
Severity: serious
Version: 6.0.0-1
Justification: Policy 2.1
Harfbuzz includes a nondistributable font in its test suite. I thought
it was just in sid/bookworm, but it's apparently also in bullseye as
well.
In bullseye:
Processing commands for cont...@bugs.debian.org:
> tags 1026204 - patch pending
Bug #1026204 [tar] tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64
Removed tag(s) patch and pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026204:
1 - 100 of 242 matches
Mail list logo
