On Wed, 08 Mar 2023 13:47:47 +0100 Ralf Jung wrote:
> Package: nginx
> Version: 1.22.1-7
> Severity: grave
> Justification: causes non-serious data loss
>
> Dear Maintainer,
>
> last weekend I did an "apt upgrade" of my system as usual, asking apt to
> prune configuration files for packages
Your message dated Mon, 24 Apr 2023 01:49:01 +
with message-id
and subject line Bug#1034367: fixed in golang-v2ray-core 4.34.0-9
has caused the Debian Bug report #1034367,
regarding v2ray geoip data has problematic license
to be marked as done.
This means that you claim that the problem has
Control: tag -1 pending
Hello,
Bug #1034367 in golang-v2ray-core 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 #1034367 [v2ray] v2ray geoip data has problematic license
Added tag(s) pending.
--
1034367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: singular
Version: 1:4.3.1-p3+ds-1
Severity: serious
Justification: rc-policy - "Packages must be buildable within the same release"
singular build-depends on python3-brial. python3-brial recently added a
dependency on python3-sage making it uninstallable on many architectures.
As a
AFAIK, both armel and armfh are low-powered/"slow" arches, but i386 is
surprising. Maybe due to memory limits?
I wonder if tests shouldn't simply be restricted to amd64, arm64, ppc64el and
s390x? This should give it enough of architecture heterogeneity to catch
any problems that simply do not
Processing commands for cont...@bugs.debian.org:
> severity 1034236 important
Bug #1034236 [mpd] mpd: dh_installsystemd doesn't handle files in
/usr/lib/systemd/system
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On 23/04/2023 21:07, Paul Gevers wrote:
Can you point to a discussion where we might draw the conclusion that
this is common practice or consensus? I *personally* [no hats on] find
that distinction a bit weird although I can see how we would come to
it and also why.
No, I can't point to a
Control: severity ! important
On Fri, Apr 21, 2023 at 03:24:25PM +0200, Geoffroy Youri Berret wrote:
> Le 11/04/2023 à 23:52, Florian Schlichting a écrit :
> > […]
> > I think we should take a step back and think about how a freshly
> > installed mpd package should look like. I think it may
Hi Peter,
On 23-04-2023 21:24, Peter Michael Green wrote:
That works in some cases, but it's a bad option here for two reasons.
1. It would create a build-dependency loop between brial and sagemath.
Which isn't practical problem as long as there is a proper build profile
involved, right?
On 23/04/2023 19:19, Paul Gevers wrote:
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual updating. Instead of
hard-coding the list, it's better to ensure the build doesn't happen
or fails on architectures where python3-sage is not
Processing commands for cont...@bugs.debian.org:
> fixed 150 3.0.4-2
Bug #150 {Done: Tobias Frost } [src:modsecurity]
modsecurity: depends on obsolete pcre3 library
Marked as fixed in versions modsecurity/3.0.4-2.
> found 150 3.0.8-1
Bug #150 {Done: Tobias Frost }
Processing commands for cont...@bugs.debian.org:
> fixed 1033496 6.1.1+dfsg2-6~exp1
Bug #1033496 [scilab] scilab: cannot start scilab at all
Bug #1033997 [scilab] scilab-6.1.1+dfsg2-5: scilab and xcos unable to launch.
Error dialog say onfiguration file is corrupted.
Marked as fixed in versions
Processing control commands:
> fixed -1 3.0.8-2
Bug #150 [src:modsecurity] modsecurity: depends on obsolete pcre3 library
Marked as fixed in versions modsecurity/3.0.8-2.
> severity -1 serious
Bug #150 [src:modsecurity] modsecurity: depends on obsolete pcre3 library
Severity set to
Hi Peter, all,
On Sat, 15 Apr 2023 15:33:04 +0100 Peter Green wrote:
* The architecture list of python3-brial needs to be limited to architectures
where python3-sage is available.
I claim this is wrong. Would python3-sage one day build on more
architectures, this list would need manual
Source: modsecurity
Version: 3.0.8-2
Severity: serious
Tags: ftbfs patch
Justification: FTBFS
Hi,
as you already know, modsecurity FTBFS on almost all archs, except amd64 and
i386:
It fails to find libpcre2 on those archs.
It seems that the shipped pcre2.m4 is broken: When using pkg-config to
Your message dated Sun, 23 Apr 2023 17:04:43 +
with message-id
and subject line Bug#1033617: fixed in openexr 3.1.5-5
has caused the Debian Bug report #1033617,
regarding libopenexr-dev: Cannot just upgrade libopenexr-dev to 3.1.5-4 because
of file conflict with older version of
Processing commands for cont...@bugs.debian.org:
> fixed 997084 3:4.7.6+~4.1.0-3
Bug #997084 [src:node-handlebars] node-handlebars: FTBFS: build hangs
Marked as fixed in versions node-handlebars/3:4.7.6+~4.1.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> tags -1 fixed-in-experimental
Bug #1033496 [scilab] scilab: cannot start scilab at all
Bug #1033997 [scilab] scilab-6.1.1+dfsg2-5: scilab and xcos unable to launch.
Error dialog say onfiguration file is corrupted.
Added tag(s) fixed-in-experimental.
Added tag(s)
Control: tags -1 fixed-in-experimental
Hello,
You submitted bugs about scilab not being able to start: I found the
cause, which is linked to the default JVM switching from openjdk-11 to
openjdk-17. I was able to fix this: the version of scilab in Debian
experimental, 6.1.1+dfsg2-6~exp1, is
Source: gluegen2
Version: 2.3.2-9
Severity: serious
Tags: fixed-in-experimental
Dear Maintainer,
Non-free header files are present in the source of gluegen2, see for instance
in make/stub_includes/jni/jni.h:
* Copyright 2006 Sun Microsystems, Inc. All rights reserved.
* SUN
Source: python-xmlschema
Version: 1.10.0-5
Severity: serious
Justification: Policy §4.9
Policy §4.9 states: For packages in the main archive, required targets
must not attempt network access, except, via the loopback interface, to
services on the build host that have been started by the build.
Your message dated Sun, 23 Apr 2023 09:49:39 +
with message-id
and subject line Bug#1034748: fixed in planetary-system-stacker
0.8.32~git20221019.66d7558-2
has caused the Debian Bug report #1034748,
regarding PlanetarySystemStacker does not work anylonger
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> tags 965794 + pending
Bug #965794 [python3-ooolib] python-ooolib: Removal of obsolete debhelper
compat 5 and 6 in bookworm
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
965794:
close 1034629
thanks
Package: planetary-system-stacker
Version: 0.8.32~git20221019.66d7558-1
Severity: grave
Due to a recent change in numpy, the planetary-system-stacker does not
work anylong and crashes during start:
Traceback (most recent call last):
File "/usr/bin/PlanetarySystemStacker", line 33, in
Processing commands for cont...@bugs.debian.org:
> close 1034629
Bug #1034629 {Done: Jochen Sprickerhof }
[pdf-presenter-console] pdf-presenter-console: pdfpc terminates with symbol
lookup error
Bug 1034629 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Wow, thanks everyone for tracking this down so quickly!
I'm going to close it, since it was due to non-debian packages.
Processing commands for cont...@bugs.debian.org:
> severity 918774 serious
Bug #918774 {Done: Nilesh Patra } [liblasi0] liblasi0:
response to missing system glyphs no longer works correctly
Severity set to 'serious' from 'important'
> stop
Stopping processing here.
Please contact me if you need
29 matches
Mail list logo
