package: riseup-vpn
severity: grave
version: 0.21.11+ds1-5+b4
It misses a dependency on openvpn-systemd-resolved and on boomworm it
was working after installing it. But on mobian trixie, which has
systemd-resolved installed by default (through mobian-base), dns
resolution fails when riseup
Processing commands for cont...@bugs.debian.org:
> retitle 1056281 snort: CVE-2023-20246
Bug #1056281 [src:snort] snort: CVE-2023-20246 CVE-2023-20031
Changed Bug title to 'snort: CVE-2023-20246' from 'snort: CVE-2023-20246
CVE-2023-20031'.
> thanks
Stopping processing here.
Please contact me
Processing commands for cont...@bugs.debian.org:
> affects 1056183 + tex-common
Bug #1056183 [texlive-binaries] texlive-luatex: lualatex exits immediately due
to new zlib
Bug #1056186 [texlive-binaries] texlive-binaries: zlib library mismatch
Bug #1056189 [texlive-binaries] luahbtex: PANIC:
Processing control commands:
> tags -1 + confirmed
Bug #1056279 [molly-guard] Symlinks in /usr/lib/molly-guard/ are gone after
upgrade
Added tag(s) confirmed.
> clone -1 -2
Bug #1056279 [molly-guard] Symlinks in /usr/lib/molly-guard/ are gone after
upgrade
Bug 1056279 cloned as bug 1056292
>
Control: tags -1 + confirmed
Control: clone -1 -2
Control: reassign -2 systemd-sysv
Control: found -2 255-rc2-1
Control: retitle -2 duplicated diversions are still broken by moved files
On Sun, Nov 19, 2023 at 02:08:35PM -0800, Francois Marier wrote:
> I'm also a little confused by the diverts.
Your message dated Sun, 19 Nov 2023 22:48:58 +
with message-id
and subject line Bug#1042640: fixed in lazr.config 3.0-1
has caused the Debian Bug report #1042640,
regarding lazr.config: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid
command 'build_sphinx'
to be marked as done.
This
Source: django-assets
Version: 2.0-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=django-assets=all=2.0-3=1700432008=0
...
dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:310: cd
/<>/.pybuild/cpython3_3.11_django-assets/build; python3.11 -m nose
-v
Processing control commands:
> tags -1 patch
Bug #1053700 [src:python-xarray] python-xarray: autopkgtest regression on s390x
Added tag(s) patch.
--
1053700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
These all come from xarray/tests/test_coding_times.py, and are probably
fixable by replacing both instances of ("M8[ns]" if
sys.byteorder=='big' else "haven't actually tried that.
CCing Helmut who wrote the initial patch for systemd 255+ support (see
Bug#1055510).
I also see the same thing:
$ ls -lh /usr/lib/molly-guard/
Permissions Size User Group Date Modified Name
.rwxr-xr-x 3,4k root root 11 nov 14:02 molly-guard*
lrwxrwxrwx31 root root 14 nov 2019
This bug is now a crash (not the original error message):
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/39962554/log.gz
I don't know whether the same patch still works.
The Salsa repository now appears to be up to date.
You probably also want to include the fixes for the
Source: adios2
Version: 2.8.2+dfsg1-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Drew Parsons
https://buildd.debian.org/status/fetch.php?pkg=adios2=all=2.8.2%2Bdfsg1-2=1700402832=0
...
debian/rules override_dh_missing
make[1]: Entering directory '/<>'
dh_missing --sourcedir=install-serial
Package: node-get-stream
Version: 8.0.1-8
Severity: serious
Tags: patch
Hello,
looks like the package is using internet during tests, and so FTBFS without
internet access.
The log is:
✔ string › handles truncated UTF-8 sequences over maxBuffer
✔ string › get stream with invalid UTF-8
Processing commands for cont...@bugs.debian.org:
> tags 1056284 + upstream
Bug #1056284 [src:nss] nss: CVE-2023-5388
Added tag(s) upstream.
> tags 1056283 + upstream fixed-upstream
Bug #1056283 [src:postgresql-15] postgresql-15: CVE-2023-5868 CVE-2023-5869
CVE-2023-5870
Added tag(s) upstream and
Processing commands for cont...@bugs.debian.org:
> retitle 1056282 gpac: CVE-2023-47384 CVE-2023-48011 CVE-2023-48013
> CVE-2023-48014 CVE-2023-5998 CVE-2023-46001
Bug #1056282 [src:gpac] gpac: CVE-2023-47384 CVE-2023-4785 CVE-2023-48011
CVE-2023-48013 CVE-2023-48014 CVE-2023-5998
Source: gpac
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for gpac.
CVE-2023-47384[0]:
| MP4Box GPAC v2.3-DEV-rev617-g671976fcc-master was discovered to
| contain a memory leak in the function gf_isom_add_chapter at
|
Source: snort
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerabilities were published for snort.
CVE-2023-20246[0]:
| Multiple Cisco products are affected by a vulnerability in Snort
| access control policies that could allow an unauthenticated,
Christoph Biedl wrote...
> after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/
> are gone.
It was suggested in IRC this might be the effect of another package's
upgrade. I find that unlikely since no other package should touch
/usr/lib/molly-guard/ - still, here's the
On 19 November 2023 at 09:59, Dirk Eddelbuettel wrote:
| On 19 November 2023 at 13:49, Graham Inggs wrote:
| | We don't believe only touching debian/changelog, or a binNMU, is
| | sufficient. We were surprised that your r-cran-lme4 upload did not at
| | least include:
| | Depends: r-cran-matrix
Package: molly-guard
Version: 0.8.1
Severity: grave
X-Debbugs-Cc: debian.a...@manchmal.in-ulm.de
Greetings,
after upgrading from 0.7.2 to 0.8.1, the symlinks in /usr/lib/molly-guard/
are gone. As this happened on a second machine today, I reckon it's not
a coincidence.
Current state:
# ls -l
Your message dated Sun, 19 Nov 2023 18:06:21 +
with message-id
and subject line Bug#1042693: fixed in python-django-celery-results 2.5.1-2
has caused the Debian Bug report #1042693,
regarding python-django-celery-results: FTBFS with Sphinx 7.1, docutils 0.20:
make[1]: *** [debian/rules:14:
Your message dated Sun, 19 Nov 2023 18:04:06 +
with message-id
and subject line Bug#1056240: fixed in debputy 0.1.8
has caused the Debian Bug report #1056240,
regarding debputy-py.test calls py3versions -s without depending on python3-all
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> #
> https://buildd.debian.org/status/fetch.php?pkg=gcc-13=mips64el=13.1.0-7=1688411201=0
> found 1056238 13.1.0-7
Bug #1056238 [src:gcc-13] gcc-13: FTBFS on mips64el: E: Build killed with
signal TERM after 150 minutes of inactivity
Marked as
Processing control commands:
> tag -1 pending
Bug #1042693 [src:python-django-celery-results] python-django-celery-results:
FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:14:
override_dh_auto_build] Error 2
Added tag(s) pending.
--
1042693:
Control: tag -1 pending
Hello,
Bug #1042693 in python-django-celery-results 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:
On Mon, 23 Oct 2023 17:28:50 +0200 Orión González wrote:
> A contributor suggested that 1.0 release should be on hold until some new
> features get stabilized
> https://github.com/chmln/sd/issues/203#issuecomment-1775390770
>
> This might mean that the 1.0 release might take many more months.
Processing control commands:
> severity -1 normal
Bug #1054730 [src:trac] trac: FTBFS: ValueError: ("Missing 'Version:' header
and/or PKG-INFO file at path: /<>/Trac.egg-info/PKG-INFO", Trac
[unknown version] (/<>))
Severity set to 'normal' from 'serious'
> tag -1 + moreinfo
Bug #1054730
Control: severity -1 normal
Control: tag -1 + moreinfo
Hi, I can't reproduce this FTBFS.
Could you try again, please?
I'll upload a new version, but it shouldn't make a difference.
Hi Graham,
On 19 November 2023 at 13:49, Graham Inggs wrote:
| On Tue, 14 Nov 2023 at 12:42, Dirk Eddelbuettel wrote:
| > Doesn't 'normal' do that?
|
| No, only serious and above are considered RC [1] and also for migration.
|
| This week, Paul Gevers and I spent some time discussing ways to
Your message dated Sun, 19 Nov 2023 15:19:33 +
with message-id
and subject line Bug#1038111: fixed in haproxy-log-analysis 5.1.0-1
has caused the Debian Bug report #1038111,
regarding haproxy-log-analysis: current version not usable, new upstream
release available
to be marked as done.
This
Hi Andreas
On Sat, 18 Nov 2023 at 19:18, Andreas Tille wrote:
> We need some means to follow ABI changes. In Debian we could use
> something like r-matrix-abi-VERSION.
Indeed, this is one solution. As you saw in [1], upstream now provide
an ABI version and a way to extract it:
> Matrix will
Hi Dirk
On Tue, 14 Nov 2023 at 12:42, Dirk Eddelbuettel wrote:
> Doesn't 'normal' do that?
No, only serious and above are considered RC [1] and also for migration.
This week, Paul Gevers and I spent some time discussing ways to move
this transition forward.
Referring back to some of your
Processing commands for cont...@bugs.debian.org:
> clone 1053674 -1
Bug #1053674 [ftp.debian.org] RM: g3dviewer -- ROM; abandoned upstream; depends
on gtk2
Bug 1053674 cloned as bug 1056272
967358 was blocked by: 1053674
967358 was blocking: 947713 967491
Added blocking bug(s) of 967358: 1056272
Processing commands for cont...@bugs.debian.org:
> affects 1050359 src:gpr
Bug #1050359 [ftp.debian.org] RM: gpr -- RoQA; dead upstream; depends on gtk2
Added indication that 1050359 affects src:gpr
> clone 1050359 -1
Bug #1050359 [ftp.debian.org] RM: gpr -- RoQA; dead upstream; depends on gtk2
Processing commands for cont...@bugs.debian.org:
> clone 1051070 -1
Bug #1051070 [ftp.debian.org] RM: gtimer -- RoQA; low popcon; depends on gtk2
Bug 1051070 cloned as bug 1056270
> reassign -1 src:gtimer
Bug #1056270 [ftp.debian.org] RM: gtimer -- RoQA; low popcon; depends on gtk2
Bug reassigned
Hello,
to make the package build in a buildd chroot some more adaptions are
needed:
- Depend on python3-docutils (which was pulled in before by
python3-sphinx)
- Drop debian/dh-virtualenv.doc-base as the documentation is missing
now
- Don't call dh with --with sphinxdoc
The complete
On 19/11/2023 12:14, Peter Michael Green wrote:
Package: rust-ripasso-cursive
Version: 0.6.1-1
Severity: serious
Tags: trixie, sid
It appears, that despite the version number indicating a compatible
release, that the new
version of ripasso broke the build of ripasso-cursive.
Processing commands for cont...@bugs.debian.org:
> affects 1051243 src:postgis
Bug #1051243 [tex-common] tex-common: fmtutil failed on tex-common upgrade
Added indication that 1051243 affects src:postgis
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1051243:
Package: rust-ripasso-cursive
Version: 0.6.1-1
Severity: serious
Tags: trixie, sid
It appears, that despite the version number indicating a compatible
release, that the new
version of ripasso broke the build of ripasso-cursive.
Package: src:debputy
Version: 0.1.7.8
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12
debputy-py.test calls py3versions -s without depending on python3-all.
[...]
234s autopkgtest [18:22:37]: test debputy-py.test: [---
234s +
Your message dated Sun, 19 Nov 2023 10:19:49 +
with message-id
and subject line Bug#1055952: fixed in ffmpeg 7:6.1-3
has caused the Debian Bug report #1055952,
regarding vlc: upgrade to libva 7:6.1-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Source: gcc-13
Version: 13.2.0-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=gcc-13=mips64el=13.2.0-6=1700351970=0
=== libstdc++
Processing control commands:
> tag -1 patch
Bug #1056147 [src:midge] midge possibly contains non-DFSG-free examples
Added tag(s) patch.
--
1056147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 patch
I have now uploaded a possible repackaged .orig.tar.bz2:
http://users.am-1.org/~ivan/src/sfn.2xNKGoveuNoRGASEQosuADUES3vYQfQmWVeMuitdtLI.tar.bz2
It was produced with the following shell command (where 39
blocks starting with 180 cover the entirety
Your message dated Sun, 19 Nov 2023 09:34:07 +
with message-id
and subject line Bug#1042591: fixed in pg8000 1.30.3-1
has caused the Debian Bug report #1042591,
regarding pg8000: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command
'build_sphinx'
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> forcemerge 1038111 1040286
Bug #1038111 [haproxy-log-analysis] haproxy-log-analysis: current version not
usable, new upstream release available
Unable to merge bugs because:
package of #1040286 is 'python3-haproxy-log-analysis' not
Hi,
I'm not a member of the DPT, but I've created a merge request in the package
repository for updating this package to upstream 5.1.0:
https://salsa.debian.org/python-team/packages/haproxy-log-analysis/-/merge_requests/2
I hope this is of some use in getting this resolved.
Best regards,
Processing control commands:
> close -1 0.3.5
Bug #1056218 [src:deb-gview] src:deb-gview: fails to migrate to testing for too
long: autopkgtest failure
Marked as fixed in versions deb-gview/0.3.5.
Bug #1056218 [src:deb-gview] src:deb-gview: fails to migrate to testing for too
long: autopkgtest
Source: deb-gview
Version: 0.3.3
Severity: serious
Control: close -1 0.3.5
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as
Processing control commands:
> block -1 by 1056204
Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3
1056210 was not blocked by any bugs.
1056210 was not blocking any bugs.
Added blocking bug(s) of 1056210: 1056204
> merge -1 1056183
Bug #1056210 [texlive-binaries] luatex panics with
Control: block -1 by 1056204
Control: merge -1 1056183
signature.asc
Description: PGP signature
Source: rust-async-task
Version: 4.4.1-1
Severity: serious
Control: close -1 4.5.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1055099
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Processing control commands:
> close -1 4.5.0-1
Bug #1056217 [src:rust-async-task] src:rust-async-task: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions rust-async-task/4.5.0-1.
Bug #1056217 [src:rust-async-task] src:rust-async-task: fails to migrate
Processing control commands:
> severity -1 grave
Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3
Severity set to 'grave' from 'normal'
> merge -1 1056183
Bug #1056210 [texlive-binaries] luatex panics with zlib 1.3
Unable to merge bugs because:
blockedby of #1056183 is '1056204' not ''
54 matches
Mail list logo
