hi again,
Here's an alternative minimal working example:
--
$ cat mwe2.f90
integer function f(x)
real, intent(in) :: x(:)
f = size(x)
end function
$ gfortran -c -Wuninitialized mwe2.f90 -o mwe2.o
during GIMPLE pass: early
Package: gfortran
Version: 4:14.2.0-1
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: arm64
Dear Maintainer,
* What led up to the situation?
I tried to compile some fortran source files on my Pinephone,
including the '-Wall' compiler opt
hi again,
There's a workaround. On the same system, compiling with
gfortran -g -O1 -c -o x.o x.f90
gives no error at all on many repeated tries.
For the file
https://codeberg.org/boud/cosmdist/src/branch/main/cosm_f90.f90
on which I discovered the error,
gfortran -g -O0 -c -o x.o x.f90
Package: gfortran
Version: 4:14.2.0-1
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org
User: debian-...@lists.debian.org
Usertags: arm64
Dear Maintainer,
* What led up to the situation?
I tried to compile cosmdist commit 3ea40c144d [1] from source with
'./configure && make' on my P
hi all,
On Fri, 16 May 2025, Arnaud Ferraris wrote:
Does megapixels-1.* work on Pinephone Pro or any of the devices
running Mobian or Droidian ?
Yes, it does work on (at least) sargo.
Glad we have a reason to avoid a 'grave' level Megapixels bug. :)
For people following this thread, here a
hi Pirate Praveen, all,
On Tue, 13 May 2025, Pirate Praveen wrote:
On Fri, 2 May 2025 21:11:45 +0200 (CEST) Boud Roukema
wrote:
Package: megapixels
Version: 1.8.3-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Does megapixels work on Pinephone Pro or other devices
Package: megapixels
Version: 1.8.3-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I have been using Megapixels on the PinePhone v1.2b for a bit under
four years on Mobian/Debian testing (bookworm prior to bookworm
bec
hi all,
The Debian Chromium team is aware of the ungoogled-chromium
project and has a list of the patches included in the Debian
source:
https://salsa.debian.org/chromium-team/chromium/-/blob/master/ungoogled-chromium.md
I agree that it would make more sense to work with the Debian Chromium
tea
Package: chromium
Severity: normal
Tags: patch
Dear Maintainer,
The current description [1] of 'chromium' in Debian is
"Web browser that aims to build a safer, faster, and more stable
internet browsing experience."
While that might be literally true in terms of the *aims* of some of
the or
Package: chromium
Severity: normal
Tags: patch
Dear Maintainer,
This bug aims to make it easier to track progress on the list of
ungoogled-chromium [1] patches [2] that are potentially under
consideration for improving Debian Chromium privacy.
There's an ITP for a parallel "ungoogled-chromium"
hi Jonas, Marco,
Just confirming that for me both
QT_QUICK_CONTROLS_STYLE=Universal nheko
and
QT_QUICK_CONTROLS_STYLE= nheko
solve this bug for me. (For obvious reasons, mistyping the
name of the environment variable does not solve the bug ;))
Machine/environment:
Mobian/trixie PinePhone v1
hi Jeremy, all,
gnome-snapshot does not accept any arguments nor does it have any
configuration files. Therefore, there is nothing to document with a
manpage.
On the contrary, apart from the usual minimal information required in Debian,
a description of the buttons' meanings and the expected b
Package: gnome-snapshot
Version: 47.0.1-2
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
I wanted more information about the 'snapshot' binary.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I typed 'man snapshot' in a t
hi Josh, maintainers,
Josh - thanks for posting this so that the wider community can track
what's happening in Debian in reaction to the opt-out
advertising-tracking telemetry inserted in firefox-128 by Mozilla.
but in the meantime, please set
dom.private-attribution.submission.enabled to "fals
hi all
Leaving aside the questions of dependencies of other Debian packages,
I agree that 5.2.5 looks like the most recent version that is
definitely free of any directly or indirectly authored contributions
by Jia Tan.
https://salsa.debian.org/debian/xz-utils/-/tree/v5.2.5?ref_type=tags
In the
Dear all,
This bug is still present in the current Debian bookworm.
CONTEXT:
Debian/bookworm
$ dpkg -l |grep -E "inkscape|imagemagick"
ii imagemagick8:6.9.11.60+dfsg-1.6+deb12u1
amd64image manipulation programs -- binaries
ii imagemagick-6-commo
hi Colin, all,
On Sat, 30 Dec 2023, Colin Watson wrote:
This is a proposal for redesigned memory controllers. It isn't an
actionable mitigation at the level of OpenSSH.
You're right: the end of the paragraph "Key Mechanism" on page 2 and
Section 4.1 "ABACuS's Hardware Design" make that clear
On Tue, 26 Dec 2023, Boud Roukema wrote:
PS: Conspiracy theory (numerology): this bug number is 105000 +
101*93, while the ArXiv ID after YYMM is 101*97. Common to
both is 101*p where p is a prime and p < 100 . ;)
Correction: 101*93 = 9393, but 11*907 = 9977. So much for the conspir
hi openssh maintainers,
There's a proposed mitigation for CVE-2023-51767 with ABACuS:
https://arxiv.org/abs/2310.09977
https://github.com/CMU-SAFARI/ABACuS
Something on this should probably be added to the "Notes" at
https://security-tracker.debian.org/tracker/CVE-2023-51767 .
Disclaimer: I j
hi Emilio,
On Fri, 24 Nov 2023, Emilio Pozuelo Monfort wrote:
I just checked this and tested it on TB 115 and it is completely disabled,
without a way to enable it (which I don't see as a problem). It's config key
toolkit.temetry.enabled in the config editor.
$ dpkg -l |grep thunderbird
ii
Package: mailman3
Version: 3.3.8-2~deb12u1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I upgraded from mailman2 to mailman3.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I read /usr/share/doc/mailman3/README.Debian, which said not
hi again
Sorry, I didn't include the line numbers in the patch. The patch should
be:
--- python/mach/mach/telemetry.py.orig 2023-10-21 00:34:41.135764889 +0200
+++ python/mach/mach/telemetry.py 2023-10-21 01:
Dear Maintainers,
The current bookworm version 1:102.15.1-1~deb12u1 of Thunderbird
still has opt-*out*, not opt-in, for telemetry. While we don't
seem to have a formal Debian policy on this, it would be within
the spirit of Debian to set this to opt-in, not opt-out.
We do have some warnings at h
hi Maintainers,
* https://security-tracker.debian.org/tracker/CVE-2021-40347 says that this
bug (993746 - python3-django-postorius: CVE-2021-40347 New upstream to fix
security bug)
is fixed in all versions.
A quick browse is consistent with that:
* buster patch
https://salsa.debian.org/mailm
Package: mailman3-web
Version: 0+20200530-2.1
Followup-For: Bug #1053502
Dear Maintainer,
SUMMARY:
--
For me, this bug is confirmed, but solved. There appear to be three separate
issues:
* the need to add DEFAULT_AUTO_FIELD in
hi maintainers,
1053502 and 1041496 appear to be the same mailman3-web update bug.
My guess is that they should be merged, but I'm still extremely new to mailman3,
so better that someone who understands the package sends the merge command.
Some hints that overlap hacks discussed at 1041496 are a
Package: iio-sensor-proxy
Version: 3.5-1
Severity: normal
Tags: upstream
Dear Maintainer,
* What led up to the situation?
I wanted more information about the 'monitor-sensor' binary and
the 'iio-sensor-proxy' systemd service.
* What exactly did you do (or not do) that was effective (or
hi Guido,
On Fri, 1 Sep 2023, Guido Günther wrote:
(put the bug in cc: so we have a all the bits together)
OK.
On Thu, Aug 31, 2023 at 11:09:02PM +0200, Boud Roukema wrote:
hi Guido,
I agree with closing #1050762. But upstream I still see two minor fixes
needed (unless I misunderstand
hi Dylan,
On Tue, 29 Aug 2023, Dylan Aïssi wrote:
Le mar. 29 août 2023 à 00:27, Boud Roukema a écrit :
PROPOSAL (1):
Should the user be informed when doing the system upgrade? More specifically,
would a one-line warning to the user be considered acceptable, as a post-install
script? E.g
hi Guido,
On Tue, 29 Aug 2023, Guido Günther wrote:
On Tue, Aug 29, 2023 at 02:12:36AM +0200, Boud Roukema wrote:
I discovered from browsing sources and git histories that the debian
'feedbackd' package automatically installs several user-level programs
that the user should be info
Package: feedbackd-device-themes
Version: 0.0.r3-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I tried following the upstream 'feedbackd' README file and spent a lot
of time making wrong guesses about syntax and about testing the effects
of modifying the theme .json fil
On Sat, 26 Aug 2023, Boud Roukema wrote:
I expected to find upstream files such as
README.md (possibly renamed to README.source)
NEWS.gz
NEWS.Debian.gz
installed in /usr/share/doc/feedbackd/ .
Obviously, NEWS.Debian.gz is not an upstream file. :)
hi Dylan,
On Mon, 28 Aug 2023, Dylan Aïssi wrote:
I think the bug you are describing is a kind of duplicate of #1027136 [1]
filled against xdg-desktop-portal. So, I will quote the smcv's answer here [2]:
I think (the) xdg-desktop-portal user service(s) should be stopped before
removing the pa
Package: feedbackd
Version: 0.2.0-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
I tried to find out how to customise my feedbackd settings and searched
in /usr/share/doc/feedbackd/
* What exactly did you do (or not do) that was effective (or
ineffective)?
I s
Package: mirrors
Severity: normal
Dear Maintainer,
* What led up to the situation?
I tried to access
https://ftp.pl.debian.org/debian
in firefox, which gave
'Warning: Potential Security Risk Ahead'
* What exactly did you do (or not do) that was effective (or
ineffective)?
I selected 'advanc
hi mozilla-related packages maintainers,
I remember having xpdf blocking access to audio devices several years ago.
I suggest that unless someone can still reproduce the bug in buster (I'm still
on stretch, but haven't seen that bug for at least a year or so), that this
bug be closed:
* this is
hi konsole maintainer(s), Alison,
SAME BUG:
I also have this bug with konsole on Stretch: sometimes copies to "the
X buffer" (this term assumes a single universal X buffer exists for a
single X session; I'm just guessing) using mouse selection are ignored
when pasting with the mouse.
After sele
On Wed, 23 Jan 2019, Samuel Thibault wrote:
Boud Roukema, le mer. 23 janv. 2019 15:53:42 +0100, a ecrit:
Though shouldn't it be 'include ' ?
For the case of GNU Mach, yes. But as the compatibility header suggests,
might be more portable.
OK, that makes sense. Looking at
Source: abyss
Version: 2.1.5-3
Severity: important
SUMMARY: abyss fails to build on hurd - googletest EXPECT_DEATH
DISCOVERY:
Found by Samuel Thibault as followup of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920240
DESCRIPTION:
Abyss-2.1.5-3 + the patch
https://bugs.debian.org/cgi-
hi Andreas, Samuel,
On Wed, 23 Jan 2019, Samuel Thibault wrote:
Andreas wrote:
Could you please adjust the severity? Regarding the description[1]
important means:
a bug which has a major effect on the usability of a package, without
rendering it completely unusable to everyone.
I d
Source: abyss
Version: 2.1.5-3
Severity: important
SUMMARY: abyss fails to build on hurd due to missing header file
DISCOVERY:
Build log of abyss-2.1.5-3 on mahler.debian.net (2019-01-09 22:47:19):
https://buildd.debian.org/status/fetch.php?pkg=abyss&arch=hurd-i386&ver=2.1.5-3&stamp=154707403
This bug occurs for reading from stdin in C too.
Again on an exodar schroot on sid:
CONTEXT:
$ dpkg -l |egrep "tree.*puzzle|openmpi|pmix|gfortran|gcc|mpifort|libc[-0]"
ii gcc4:8.2.0-2 hurd-i386
GNU C compiler
ii gcc-8
hi again
I forgot to state evidence that this is a GNU/Hurd bug:
On an amd64 machine running Debian/stretch GNU/Linux, mpifort runs this test
program as expected.
$ cat hurd_fortran_minimal.f90
program openmpi_hurd_bug
i_myid = 178
print*,'i_myid = ',i_myid,' Please type in an integer and h
Source: openmpi
Version: 3.1.3-9
Severity: important
SUMMARY: mpifort (openmpi 3.1.3-9) infinite loop on hurd while reading from
stdin
DESCRIPTION:
On GNU/Hurd, a few-line fortran program that reads an integer from
stdin and outputs it to stdout, and has no calls to mpi, runs
as expected when c
* typo:
Obviously I cut and paste some CONTEXT lines wrongly in bug report 918031.
$ schroot -e -c ${sessionid} # exit schroot
should be
$ schroot -r -c ${sessionid} # run schroot
Don't waste time by using the -e option until you're ready.
* also: mpifort is not a separate package; it's in
Source: openmpi
Version: 3.1.3-7
Severity: important
Control: affects -1 mpgrafic
Dear Maintainer,
SUMMARY: mpi_init pmix error on GNU/Hurd (gds_dstore.c line 1030)
DESCRIPTION: mpi_init gives a fatal pmix error on GNU/Hurd.
This occurred for a Debian automatic build for mpgrafic-0.3.16-1
on a
hi all
There was an FTBFS bug #911941 for mpgrafic on 17 and 27 October 2018, which
were clearly
only because of libpsm2 bug #910485 reporting a timeout to stdout:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910485
The reproducible builds of mpgrafic since then look OK:
https://tests.re
Source: piuparts
Version: 0.81~201709101403~0.80-7-g42acc540
Severity: normal
Tags: patch upstream
Dear Maintainer,
This inhomog build log:
https://piuparts.debian.org/sid/fail/libinhomog0_0.1.6.1-1.log includes
the piupart version:
0m0.0s INFO: piuparts version 0.81~201709101403~0.80-7-g42ac
Hi again Guillem (sorry I misspelt your surname :),
On Mon, 4 Sep 2017, Guillem Jover wrote:
On Mon, 2017-09-04 at 00:23:42 +0200, Boud Roukema wrote:
At https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871956
Guillem Rover proposes to revert this patch (for bug #874078) and make a better
At https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871956
Guillem Rover proposes to revert this patch (for bug #874078) and make a better
one.
Just to summarise again the point that to me still seems valid after
Guillem's clarification on p(write|read)(|64): to me it's confusing to
have text th
hi Guillem, all,
On Sun, 3 Sep 2017, Guillem Jover wrote:
When you define _FILE_OFFSET_BITS=64 the interfaces are transparently
mapped to the 64-bit variants and no other code change is required. So
you *must* not be switching from foo to foo64 in the call sites. This
is IMO the preferred way t
Package: lintian
Version: 2.5.52
Severity: normal
Tags: patch lfs
Dear Maintainers,
CONTEXT:
Mpgrafic-0.3.15-1 is flagged with the binary-file-built-without-LFS-support
lintian
flag despite my attempts to follow the lintian recommendations, after having
searched for LFS info in obvious place
hi Adam, all,
On Sat, 2 Sep 2017, Adam Borowski wrote:
AC_SYS_LARGEFILE on i386 (linux) for mpgrafic-0.3.15-1 apparently does *not*
always do the right thing:
You call it but don't actually use what it returns:
mpicc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdeb
On Fri, 1 Sep 2017, Adam Borowski wrote:
And what AC_SYS_LARGEFILE does, at least on Linux, is to return a hardcoded
setting so programs switch from off_t to off64_t whether they need to or
not. This does the right thing on old 32-bit archs and is harmless on
64-bit and new 32-bit.
AC_SYS_LAR
On Fri, 1 Sep 2017, Adam Borowski wrote:
Also, the vast majority of packages don't trigger this warning as they
request LFS unconditionally instead of trying to autodetect it.
The lintian warning here:
https://lintian.debian.org/tags/binary-file-built-without-LFS-support.html
says "This can be
This is not a pure fortran bug: the same error occurs for a C
even-less-than-hello-world program. These tests are on a different machine,
again on a physical partition. The fortran error is unchanged.
++ cat /etc/debian_version
buster/sid
++ uname -vorsmpi
GNU/kFreeBSD 10.3-0-amd64 #0 Fr
hi Alastair
On Wed, 30 Aug 2017, Alastair McKinstry wrote:
I suspect this is due to the libgfortran4 transition that is currently
in progress. 2.1.1-6 was built against libgfortran3;
2.1.1-6+b1 against libgfortran4 and should not have this issue.
Can you please retest ?
I aptitude updated/
Source: openmpi
Version: 2.1.1-6
Severity: important
Dear Maintainer,
DESCRIPTION:
Running a minimal mpi fortran program with openmpi-2.1.1-6 on
kfreebsd-amd64 gives a libgfortran.so.3 vs .so.4 warning and fails
with PMIX ERROR: UNREACHABLE and PMIX ERROR: NOT-SUPPORTED.
CONTEXT:
I found thi
There seems to be the same bug for i386: lintian is happy with the
amd64 build for mpgrafic-0.3.15-1, but not the i386 build:
https://lintian.debian.org/resources/19e49e9fd069a7399a0e50f1e564bf80aa5b7fb21eada72ead5470475a69460b.gz
N: Unpacking packages in group mpgrafic/0.3.15-1
N:
N: Proce
hi Jonas, Debian Astro team,
On Fri, 18 Aug 2017, Jonas Smedegaard wrote:
I have never seen a package description so stuffed with advanced
technical terms.
I am very impressed at how it still (I guess) succeeds at hinting at its
purpose for non-experts like myself.
Thanks for the pedagogical
Package: wnpp
Severity: wishlist
Owner: Boud Roukema
* Package name: inhomog
Version : 0.1.5
Upstream Author : Boud Roukema, Jan Ostrowski, Justyna Borkowska
* URL : https://bitbucket.org/broukema/inhomog
* License : GPL-2+
Programming Lang: C
Description
hi Svante,
I could not find the xpdf upstream developer pages. Your message here:
On Wed, 8 Mar 2017, Svante Signell wrote:
And FYI:
Quoting from upstream, sent to me yesterday:
Regarding security bugs, I try to respond to those as quickly as
possible.
gives the impression that there is jus
Package: blhc
Version: 0.07+20161116+gitbf41976
Severity: normal
Dear Maintainer,
SUMMARY: On https://qa.debian.org/bls/packages/m/mpgrafic.html,
blhc, which is presumably the version of blhc presently in sid, i.e.
blhc-0.07+20161116+gitbf41976, incorrectly labels builds of mpgrafic
as "I no-com
This may affect mpgrafic, which depends on mpi-default-dev and
mpi-default-bin, i.e. effectively on openmpi.
mipsel-manda-01 (mips64el) had a segmentation violation fault for the
code regression test on mpgrafic-0.3.10-1 and 0.3.7.8-1:
https://buildd.debian.org/status/logs.php?pkg=mpgrafic&arch=
DESCRIPTION:
The openmpi bug #851918 / mpgrafic bug #851923 on the s390x
architecture appears to be related to fortran/C interfacing
in terms of referencing/dereferencing pointers. The minimal
test program and example compilation and run below illustrate
the bug.
It looks like fftw-2.1.5/mpi/fft
The mips build (including the code regression test) of mpgrafic-0.3.9-1
succeeded:
https://buildd.debian.org/status/fetch.php?pkg=mpgrafic&arch=mips&ver=0.3.9-1&stamp=1485163898&raw=0
So this bug might not be purely an endianness bug.
Just for the record: in mpgrafic-0.3.9-1, the symptoms of this
bug remain - mpgrafic-0.3.9-1 fails to build on s390x, ppc64, ppc64, sparc64:
https://buildd.debian.org/status/fetch.php?pkg=mpgrafic&arch=s390x&ver=0.3.9-1&stamp=1485163445&raw=0
FAIL: regression-test-0.3.7.9.sh
Package: mpgrafic
Version: 0.3.7.8-1
Severity: serious
Tags: upstream
Justification: fails to build from source
Dear Maintainer,
Description:
After installing mpgrafics-0.3.7.8-1 on mips by the debian buildd system,
`make check' runs `regression-test-0.3.7.8.sh', which runs
`mpirun -n 1 --mca p
There's a discussion thread starting here:
https://lists.debian.org/debian-mentors/2017/01/msg00322.html
about mpirun (a front end provided by openmpi to run a user program)
refusing, by default, to run as root for mpgrafic, a program that uses
mpi.
This would affect any other debian package us
Package: mpgrafic
Version: 0.3.7.6-2
Severity: serious
Justification: fails to build from source
In this debian automated build of mpgrafic-0.3.7.6-2 (debian
downstream version) on an s390x architecture, `make check' calls
`regression-test-0.3.7.sh', which gives this fatal error:
* lines 878-884
Source: openmpi
Version: openmpi-2.0.2~git.20161225-8
Severity: normal
Dear Maintainer,
In this debian automated build of mpgrafic-0.3.7.6-2 (debian
downstream version) on an s390x architecture, `make check' calls
`regression-test-0.3.7.sh', which calls mpgrafic with a standard
input file, expec
Package: wnpp
Severity: wishlist
Owner: Boud Roukema
* Package name: mpgrafic
Version : 0.3.2
Upstream Author : Simon Prunet, Christophe Pichon, Boud Roukema
* URL : https://bitbucket.org/broukema/mpgrafic
* License : GPL-v2+
Programming Lang: fortran
salut Georges et bugtracker,
On Thu, 25 Oct 2007, Georges Khaznadar wrote:
Hello Boud, once again, I do not succeed in reproducing this bug.
I shall try again next week, after my travel.
Best regards, Georges.
Boud Roukema a écrit :
salut,
i'm not sure if this is re
On Mon, 22 Oct 2007, Georges Khaznadar wrote:
Boud Roukema a écrit :
ANALYSIS:
From the command line:
as user wims:
cd /var/lib/wims/public_html/ && ./wims
outputs a correct html page.
as user www-data, same command:
cd /var/lib/wims/public_html/ && ./wims
outputs:
al school teachers, the latter
may concentrate on course creation and not local installation. Anyway, this
is getting offtopic from the bug report, sorry.
amities
boud
On Wed, 24 Oct 2007, Boud Roukema wrote:
Package: wims
Version: 3.62-8
Severity: important
--
To UNSUBSCRIBE, email to [E
Package: wims
Version: 3.62-8
Severity: important
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=pl_PL.ISO-8859-2, LC_CTYPE=pl_PL.ISO-8859-2
(char
On Thu, 18 Oct 2007, Georges Khaznadar wrote:
Hello Boud,
the package wims_3.62-8 will be available shortly, which fixes this bug
and many others.
hi Georges,
i think that this bug is not yet closed... And i have another one which seems
to be independent so i'll file it independently.
amit
Package: wims
Version: 3.60-6
Severity: grave
Justification: renders package unusable
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=pl_PL.ISO-8859
78 matches
Mail list logo
