The original problem report showed the following situation was hit:
common/malloc_simple.c:29:
log_err("alloc space exhausted\n");
You cannot expect normal system behavior when reaching this situation.
The available space for simple malloc is defined by:
CONFIG_SPL_SYS_MALLOC_F_LEN=0x2000
CO
Hi,
Le lundi 17 mai 2021 à 15:20 +0200, Jochen Sprickerhof a écrit :
> Hi Julien,
>
> * Julien Puydt [2021-05-17 09:01]:
> > I tried to create a testing sbuild and compile sagemath 9.2-2 with
> > it,
> > and it worked so unless I made a mistake in my setup, something
> > made
> > that bug go awa
Processing control commands:
> tags -1 pending
Bug #988674 [python3-saga] python3-saga: broken symlink:
/usr/lib/python3/dist-packages/_saga_api.cpython-39-x86_64-linux-gnu.so ->
_saga_api-7.3.0.so
Added tag(s) pending.
--
988674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988674
Debian
Control: tags -1 pending
On 5/18/21 6:25 AM, Sebastiaan Couwenberg wrote:
> On 5/17/21 8:30 PM, Andreas Beckmann wrote:
>> during a test with piuparts I noticed your package ships (or creates)
>> a broken symlink.
>>
>> >From the attached log (scroll to the bottom...):
>>
>> 6m23.3s ERROR: FAIL: B
On 5/17/21 8:30 PM, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
>
>>From the attached log (scroll to the bottom...):
>
> 6m23.3s ERROR: FAIL: Broken symlinks:
> /usr/lib/python3/dist-packages/_saga_api.cpython-39-x86_64-lin
On 2021-05-16, Vagrant Cascadian wrote:
> Control: severity 988217 serious
>
> On 2021-05-07, Vagrant Cascadian wrote:
>> On 2021-04-16, Bastian Germann wrote:
>>> On a Lamobo R1, I can verify 2021.01 versions not to boot with a
>>> default environment. However, 2020.10+dfsg-2 boots. Even though th
Hi Simon!
Simon McVittie (2021-05-17):
> My instinct is that it's far, far too late to be moving to GTK 3 this
> cycle, and I'd prefer to get a suitable hack into GTK 2 if we can
> find one. We can make it #ifdef DEBIAN_INSTALLER to avoid disrupting
> the installed system.
If you're happy with f
On Mon, 17 May 2021 at 18:12:35 +0200, Cyril Brulebois wrote:
> And for those not following #debian-boot, I'm finding myself between a
> rock and a hard place, as both options (trying to work around the
> rendering-related hangs versus switching to GTK 3 at the last moment)
> are very far from idea
Discussing the path forward for bullseye with the release team in
#988686
Processing control commands:
> close -1 2.8.0-2
Bug #988685 [src:jssc] jssc FTBFS in buster due to a regression in jh_build
argument parsing
Marked as fixed in versions jssc/2.8.0-2.
Bug #988685 [src:jssc] jssc FTBFS in buster due to a regression in jh_build
argument parsing
Marked Bug as done
Source: jssc
Version: 2.8.0-1
Severity: serious
Tags: ftbfs
Control: close -1 2.8.0-2
https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/jssc.html
...
make[1]: Entering directory '/build/jssc-2.8.0'
jh_build -o"-source 1.6 -target 1.6 -encoding UTF-8" --javadoc-opts="-source
1.6 -en
Processing commands for cont...@bugs.debian.org:
> # Policy 3.5 + RC policy
> severity 964511 serious
Bug #964511 [formiko] Tests are failing, need to depends on the svg loader
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> tags 988673 + bookworm
Bug #988673 [src:centreon-connectors] centreon-connectors: FTBFS: Could not
find libgcrypt's headers
Added tag(s) bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
988673: https://b
Processing control commands:
> severity -1 serious
Bug #978954 [pepperflashplugin-nonfree] pepperflashplugin-nonfree: should not
be part of bookworm
Severity set to 'serious' from 'important'
--
978954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978954
Debian Bug Tracking System
Contact
On Mon, May 17, 2021 at 07:57:23PM +0200, Guillem Jover wrote:
> > -if [ $code -eq 104 ] && \
> > -! command -v systemctl > /dev/null ; then
> > -# We're not using systemd and thus may have some sysvinit cleanup
> > -# to do in order to comply with policy 9.3.3.1
> >
Control: reopen -1
Hi Mike,
On 17-05-2021 12:57, Mike Gabriel wrote:
> Can you do your autopkgtest magic with upcoming dbus-test-runner
> 16.10.0~bzr100+repack1-5~exp2 once more?
Sure thing. Sadly, if fails 6/20:
https://ci.debian.net/user/elb...@debian.org/jobs?package=dbus-test-runner
Paul
Processing control commands:
> reopen -1
Bug #986590 {Done: Mike Gabriel } [src:dbus-test-runner]
dbus-test-runner: flaky ppc64el autopkgtest: FAIL test-libdbustest-mock-test
(exit status: 1)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be clea
Package: python3-saga
Version: 7.3.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
6m23.3s ERROR: FAIL: Broken symlinks:
Source: centreon-connectors
Version: 19.10.0-1
Severity: serious
Tags: ftbfs sid
This package fails to build from source on current sid/amd64.
See for instance
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/centreon-connectors.html
-- The CXX compiler identification is G
On Mon, 2021-05-17 at 10:41:28 -0700, Noah Meyerhans wrote:
> -if [ $code -eq 104 ] && \
> -! command -v systemctl > /dev/null ; then
> -# We're not using systemd and thus may have some sysvinit cleanup
> -# to do in order to comply with policy 9.3.3.1
> -
> -
Hi Julien,
* Julien Puydt [2021-05-17 09:01]:
I tried to create a testing sbuild and compile sagemath 9.2-2 with it,
and it worked so unless I made a mistake in my setup, something made
that bug go away...
Can someone independently give it a try?
I triggered reproducible-builds again:
https
-if [ $code -eq 104 ] && \
-! command -v systemctl > /dev/null ; then
-# We're not using systemd and thus may have some sysvinit cleanup
-# to do in order to comply with policy 9.3.3.1
-
-if [ -z "$ENABLED" -o "$ENABLED" = 0 ]; then
-# The rc?d sy
close 988668 0.11.9-1
found 988668 0.11.2-1
# upcoming prosody DSA
fixed 988668 0.11.2-1+deb10u1
thanks
Processing commands for cont...@bugs.debian.org:
> close 988668 0.11.9-1
Bug #988668 [src:prosody] prosody: CVE-2021-32917 CVE-2021-32918 CVE-2021-32919
CVE-2021-32920 CVE-2021-32921
Marked as fixed in versions prosody/0.11.9-1.
Bug #988668 [src:prosody] prosody: CVE-2021-32917 CVE-2021-32918 CVE
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:vala
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Settin
Processing commands for cont...@bugs.debian.org:
> severity 986384 important
Bug #986384 [src:courier] [Courier-imap] courier and maildrop it seems does not
work as xpected
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
9
Source: prosody
Version: 0.11.8-1
Severity: serious
Tags: security upstream
Justification: security issues, need to be fixed in testing for avoid security
regression from buster
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Control: found -1 0.11.2-1
Control: fixed -1 0.11.2-1+deb10u1
Co
On Mon, 2021-05-17 at 18:58 +0900, Roger Shimizu wrote:
> Dear Ben,
>
> Thanks for the report and NMU!
>
> On Mon, May 17, 2021 at 8:21 AM Ben Hutchings wrote:
> >
> > Control: tags 988562 + patch
> > Control: tags 988562 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for bro
Your message dated Mon, 17 May 2021 16:48:40 +
with message-id
and subject line Bug#988284: fixed in golang-github-prometheus-procfs 0.3.0-2
has caused the Debian Bug report #988284,
regarding golang-github-prometheus-procfs-dev: missing Breaks:
golang-procfs-dev (<< 0.2.0)
to be marked as do
Processing control commands:
> tag -1 pending
Bug #988284 [golang-github-prometheus-procfs-dev]
golang-github-prometheus-procfs-dev: missing Breaks: golang-procfs-dev (<<
0.2.0)
Added tag(s) pending.
--
988284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988284
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #988284 in golang-procfs 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/go-team/packages/golang-github-prometheus-procfs/-/c
Cyril Brulebois, le lun. 17 mai 2021 18:12:35 +0200, a ecrit:
> Additionally, even with all 3 cdebconf-gtk-* packages converted, we
> still get libgtk2.0-0-udeb pulled into a netboot-gtk build, because this
> package pulls it:
>
> build/pkg-lists/gtk-common:libgail18-udeb
>
> Adding debian-ac
Cyril Brulebois (2021-05-17):
> > The steps to use GTK 3 in d-i would be:
> >
> > - convert cdebconf-gtk-udeb from GTK 2 to GTK 3
> > - convert cdebconf-gtk-entropy from GTK 2 to GTK 3
> > - convert cdebconf-gtk-terminal from GTK 2 to GTK 3 and, simultaneously,
> > from libvte9-udeb to libvte-2
Good day!
Please check the documents in one doc available through the link lower:
sewabiliktraining.com/l28S/979609-69.zip
-Original Message-
On Thursday, 29 April 2021, 17:24, <979...@bugs.debian.org> wrote:
Good day!
Please check the documents in one doc available through the li
Hi Simon,
Simon McVittie (2021-05-13):
> Adding a udeb-specific hack in one of those packages seems reasonable,
> *if* we can find a suitable hack.
>
> pango1.0 just has one build shared between the udeb and the full .deb,
> so if the hack goes there, a prerequisite would be to build it twice
>
Hi Paul,
On Do 15 Apr 2021 13:50:31 CEST, Paul Gevers wrote:
Hi Mike,
On 15-04-2021 12:24, Mike Gabriel wrote:
Hi Paul,
Am Donnerstag, 15. April 2021 schrieb Paul Gevers:
Hi Mike,
On 14-04-2021 21:41, Mike Gabriel wrote:
Can you re-run those autopkgtests multiple times on ppc64el and che
It appears than xalan2 (requires)-> xerces2 (requires)->
libxml-commons-external-java explicitly removes versioned jar in its build
(debian/libxml-commons-external-java.poms)
debian/xml-apis.xml --java-lib --usj-name=xml-apis --artifact=xml-apis.jar
--no-usj-versionless
Don't know why but it brea
Hi,
I'd like to forward this to Debian Java list for comments.
Kind regards
Andreas.
On Mon, May 17, 2021 at 01:50:01PM +0200, olivier sallou wrote:
> Issue seems to be related to xml-apis.jar not being symlinked itself
>
> /usr/share/java# ls *xml-api*
> xml-apis-1.4.01.jar xml-apis-ex
Issue seems to be related to xml-apis.jar not being symlinked itself
/usr/share/java# ls *xml-api*
xml-apis-1.4.01.jar xml-apis-ext-1.4.01.jar xml-apis-ext.jar
Usually, java libs have a versioned file and an unversionned file which is
a symlink to versioned one (see above).
xml-apis here is not
Package: node-es6-shim
Version: 0.35.6+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m37.9s ERROR: FAIL: Broken symlinks:
need to check, but I suppose referenced lib changed its path or name in
dependencies...
Le lun. 17 mai 2021 à 13:33, Andreas Beckmann a écrit :
> Package: logol
> Version: 1.7.9-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts
Package: logol
Version: 1.7.9-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
1m53.8s ERROR: FAIL: Broken symlinks:
/usr/share/
Your message dated Mon, 17 May 2021 11:03:39 +
with message-id
and subject line Bug#988562: fixed in broadcom-sta 6.30.223.271-17
has caused the Debian Bug report #988562,
regarding Fails to build due to unspecified debhelper compatibility level
to be marked as done.
This means that you claim
Your message dated Mon, 17 May 2021 11:03:49 +
with message-id
and subject line Bug#987936: fixed in libstorj 1.0.3-1.1
has caused the Debian Bug report #987936,
regarding libstorj: fails to build from the source
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 17 May 2021 11:03:44 +
with message-id
and subject line Bug#986590: fixed in dbus-test-runner
16.10.0~bzr100+repack1-5~exp2
has caused the Debian Bug report #986590,
regarding dbus-test-runner: flaky ppc64el autopkgtest: FAIL
test-libdbustest-mock-test (exit status: 1
Your message dated Mon, 17 May 2021 10:50:10 +
with message-id
and subject line Bug#988604: fixed in plocate 1.1.7-3
has caused the Debian Bug report #988604,
regarding plocate: autopkgtest regression: plocate and mlocate can't be
co-installed anymore
to be marked as done.
This means that yo
Hi Phil and Josue,
On 15/05/2021 06:05, Philip Wyett wrote:
> Attached is a (NMU) debdiff that fixes the issue. Cherry picked patch from
> Fedora[1].
>
> This RC bug can be handled however wished by the maintainer. Just one less to
> fix. :-)
>
> [1] Original patch by: Gwyn Ciesla
It would a
Your message dated Mon, 17 May 2021 10:18:35 +
with message-id
and subject line Bug#986100: fixed in mate-session-manager 1.24.1-2
has caused the Debian Bug report #986100,
regarding mate-session-manager: Should not upload XDG_SESSION_ID to systemd
--user
to be marked as done.
This means tha
Package: python3-vtk-dicom
Version: 0.8.12-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
7m25.8s ERROR: FAIL: Broken symlinks:
Package: ruby-font-awesome-rails
Version: 4.7.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m44.3s ERROR: FAIL: Broken sym
Dear Ben,
Thanks for the report and NMU!
On Mon, May 17, 2021 at 8:21 AM Ben Hutchings wrote:
>
> Control: tags 988562 + patch
> Control: tags 988562 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for broadcom-sta (versioned as 6.30.223.271-16.1)
> and uploaded it.
>
> The changes are a
Hi,
I tried to create a testing sbuild and compile sagemath 9.2-2 with it,
and it worked so unless I made a mistake in my setup, something made
that bug go away...
Can someone independently give it a try?
JP
52 matches
Mail list logo
