e_info).unwrap();
| ^ not found in this scope
Some errors have detailed explanations: E0425, E0433.
For more information about an error, try `rustc --explain E0425`.
error: could not compile `apple-nvram` (lib test) due to 4 previous errors
```
Regards,
Andreas Henriksson
ould resolve itself once it's accepted.
Regards,
Andreas Henriksson
ink manually written maintscript code should be frowned
upon (since it's a very common source of bugs), I guess this means
this bug is not RC severity?!
Regards,
Andreas Henriksson
unitdir+path%3ACMake&literal=0
https://codesearch.debian.net/search?q=systemdsystemunitdir+path%3AFindSystemd&literal=0
Regards,
Andreas Henriksson
Hello again,
On Wed, Apr 12, 2023 at 01:19:52PM +0200, Andreas Henriksson wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> > Package: drkonqi
> > Version: 5.27.2-1
> > Severity: serious
> > Tags: sid bookworm
> > User: debhel...
ess you can always add a hack that appends to dh_install to move
the file into the correct directory as returned by
`pkg-config --variable=systemdsystemunitdir systemd`.
(Note: make sure to have systemd.pc available by build-dep on systemd)
Regards,
Andreas Henriksson
, thus you'll need to
build-depend on the systemd package (as you already list
pkg-config in build-deps).
Regards,
Andreas Henriksson
t )
There's however this in unixconf.pri (which is wrong):
```
# Systemd Service file
nogui:systemd {
systemdService.files = $$DIST_PATH/systemd/qbittorrent-nox@.service
systemdService.path = $$PREFIX/lib/systemd/system
INSTALLS += systemdService
}
```
Regards,
Andreas Henriksson
get to add pkg-config and systemd (for systemd.pc) to
build-deps.
Regards,
Andreas Henriksson
at moves the file (if it's not already located in the same path as
returned by `pkg-config --variable=systemdsystemunitdir systemd`) after
dh_install has run probably.
Regards,
Andreas Henriksson
owsocks-libev.install
you would have to make the file executable and integrate dh-exec.
I'll leave it up to you to decide if you think integrating dh-exec
is worth it or not
(Another option is to make the upstream build system install the file
in the correct path.)
Regards,
Andreas Henriksson
Hello Max Kellermann,
On Tue, Apr 11, 2023 at 04:13:28PM +0200, Max Kellermann wrote:
> On 2023/04/11 15:11, Andreas Henriksson wrote:
> > The culprit seems to be that mpd falls back on hard-coded path (instead
> > of failing) when systemd.pc is not found!
>
> What does
erity of this bug report should be downgraded
(maybe even closed)?
Regards,
Andreas Henriksson
the hardcoded sysuser directory at:
https://sources.debian.org/src/cloudflare-ddns/2.0.0-3/exe/meson.build/#L90
See attached file which you might want to improve (for example you could
make systemd a build-option even on linux if you care).
Regards,
Andreas Henriksson
diff -Nru cloudflare-ddns-2.0.
mpdscribble/0.24-2/systemd/system/meson.build/#L1-L4
As pkg-config is already part of build-deps, simply adding systemd (for
systemd.pc) should be enough to fix the problem.
Regards,
Andreas Henriksson
g --variable=systemdsystemunitdir systemd
(Note: You'll also need to build-dep on pkg-config and systemd, for
systemd.pc)
Regards,
Andreas Henriksson
ed to reverse that change again in the future.
Preferably the correct path is derived from the value given by
pkg-config --variable=systemdsystemunitdir systemd
You could use this via making your debian/caddy.install executable
and integrating dh-exec. You'll have to decide if you th
t the path from the proper source via:
pkg-config --variable=systemdsystemunitdir systemd
(Note: you'll need to build-dep on pkg-config and systemd, for
systemd.pc)
Regards,
Andreas Henriksson
please consider finding the path via:
pkg-config --variable=systemdsystemunitdir systemd
(Note: you'll need to build-dep on pkg-config and systemd, for
systemd.pc)
Regards,
Andreas Henriksson
=get_option.*systemdsystemunitdir&literal=0&perpkg=1
Regards,
Andreas Henriksson
sr/lib/systemd/system` to:
export TLP_SYSD=$(shell pkg-config --variable=systemdsystemunitdir systemd)
* Update https://sources.debian.org/src/tlp/1.5.0-1/debian/tlp.install/#L5
Regards,
Andreas Henriksson
es.debian.org/src/pam/1.5.2-6/debian/rules/#L33
Regards,
Andreas Henriksson
Fixing the problem should be as easy as adding a build-dep on the
package that contains systemd.pc (systemd).
Regards,
Andreas Henriksson
/sources.debian.org/src/gammu/1.42.0-7/debian/gammu-smsd.install/#L5
Regards,
Andreas Henriksson
"$(DESTDIR)$(LIBDIR)/systemd/system/pass-close@.service"
```
To get the correct path you could use:
```
pkg-config --variable=systemdsystemunitdir systemd
```
(Note: do not forget to also build-dep on the package containing systemd.pc as
well as pkg-config itself.)
Regards,
Andreas Henriksson
On Tue, Apr 11, 2023 at 02:23:32PM +0200, Andreas Henriksson wrote:
> On Tue, Apr 11, 2023 at 09:37:27AM +0200, bi...@debian.org wrote:
> > Package: fapolicyd
> > Version: 1.1.7-3
> > Severity: serious
> > Tags: sid bookworm
> > User: debhel...@packages
27;ll also need a build-dep on package containing systemd.pc)
Regards,
Andreas Henriksson
ut contains
very little useful information (probably all already available in the
package itself).
If this is even a bug then it would be at most Severity: wishlist as I
see it.
What am I missing here that makes Homepage so important for this
package to warrant a release-critical severity?
Regards,
Andreas Henriksson
ould appreciate
you blocking their package from testing migration until you've uploaded
a relinted version of your package.)
Regards,
Andreas Henriksson
ential additional
problems as an excercise for the maintainer(s) to figure out while
testing their new package.
Please consider adding a simple compile test as an autopkgtest,
which would help you catch missing dependencies in the -dev packages.
For example see:
https://sources.debian.org/src/util-linux/2.38.1-5/debian/tests/libmount-dev/
Regards,
Andreas Henriksson
onfigure.in/#L117
The sane-backends.pc from unstable (1.2.1-1) has:
# grep -e ldflags= -e libs=
/usr/lib/x86_64-linux-gnu/pkgconfig/sane-backends.pc
libs= -ldl -lm -ltiff -ljpeg -lgphoto2 -lgphoto2_port -lm -lavahi-common
-lavahi-client -lusb-1.0
While the sane-backends.pc currently in testing (1.1.1-6) has:
# grep -e ldflags= -e libs= usr/lib/x86_64-linux-gnu/pkgconfig/sane-backends.pc
ldflags=-Wl,-z,relro -Wl,-z,now
libs=
Regards,
Andreas Henriksson
endencies listed in the pkg-config
file.
For example see:
https://sources.debian.org/src/util-linux/2.38.1-5/debian/tests/libmount-dev/
Regards,
Andreas Henriksson
Hello again,
On Sat, Feb 11, 2023 at 06:55:13PM +0100, Andreas Henriksson wrote:
> On Sun, Jan 29, 2023 at 02:29:23PM +0100, László Böszörményi (GCS) wrote:
> > Control: tags -1 +confirmed
> >
> > On Sun, Jan 29, 2023 at 12:33 PM Adrian Bunk wrote:
> > > ht
.. now that I've written all this I see there's already:
https://salsa.debian.org/science-team/libgetdata/-/commit/f698db0b309351d8dc66fad194f9462fb5c531ea
Might still be worth considering not hardcoding any versions as discussed above
though (to avoid repeating this problem once python 3.11 goes out of
fashion)...
Regards,
Andreas Henriksson
d in by node-chalk).
-- Jonas Smedegaard Sat, 12 Oct 2019 15:19:55 +0200
I'm not able to determine if either enigmail should dep on node-chalk
itself because it uses supposedly optional components of eslint
or if there's a mistake in eslint which should have node-chalk
as a depends rather than recommends
Hope someone else can figure this out.
Regards,
Andreas Henriksson
nt (maybe)...
I tried quickly looking at upstream git history if it could confirm
my suspicion, but the closest I could find was:
https://github.com/notroj/neon/commit/eff6521be537c74511593743bf8665d898e26567
Seems like localhost -> 127.0.0.1 switch was intentional (and done
during SVN days?). Maybe someone digging deeper can find "r1910".
Regards,
Andreas Henriksson
hat's kind of the only solution inside iptables that I can see have
it explicitly (un)set IFS. I however don't think that's the correct
solution, just a solution.
>
> #1007829 was a similar problem in arptables,
> I haven't checked how these are related.
I don't see how these two are related at all.
#1007829 seems to be a simple logic error.
Regards,
Andreas Henriksson
On Wed, Feb 01, 2023 at 04:46:14PM +0100, Guido Günther wrote:
> Hi,
> On Wed, Feb 01, 2023 at 04:37:37PM +0100, Andreas Henriksson wrote:
[...]
> > FWIW here are some examples of autopkgtest for checking if pkg-config
> > works for your own -dev packages:
> > https://sou
On Wed, Feb 01, 2023 at 04:23:00PM +0100, Andreas Henriksson wrote:
> On Wed, Feb 01, 2023 at 04:03:47PM +0100, Guido Günther wrote:
> > Hi,
> > [..snip..]
> > > This seems to be caused by wlroots/experimental missing a
> > > build-dependency on libvulkan-dev and i
build-dependency on libvulkan-dev. I think what you mean is
> the lack of a dependency in the libwlroots-dev package?
Exactly... I've already retitled the bug report (again) to remove
my incorrect use of build-dep, when what I mean was -dev package
depending on another -dev package.
Regards,
Andreas Henriksson
working as expected (because it's easy to forget to check
every .pc file changes and cross-check which package provides that and
if it's listed in build-depends on every update).
Regards,
Andreas Henriksson
ssibly 'Always' option could have come from here:
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.config/#L56
But then again, the initial/re-configure should not have been run at all
because of
https://sources.debian.org/src/fontconfig/2.14.1-3/debian/fontconfig-config.postinst/#L32
as mentioned earlier.
Regards,
Andreas Henriksson
Hello,
On Tue, Jan 31, 2023 at 02:26:50AM +0100, Helge Deller wrote:
> Hi David & Andreas,
>
> On 1/28/23 12:10, David Prévot wrote:
> > 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
&
Hello taffit,
On Sat, Jan 28, 2023 at 12:10:53PM +0100, David Prévot wrote:
> 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 pa
uld give it ASAP!
What do you think?
Regards,
Andreas Henriksson
ng in here that is controversial or wrong, but
hopefully there isn't.
Regards,
Andreas Henriksson
s already mentioned, I think wishlist is the proper severity.
(And as said, I don't mind this being considered a bug or fixing it
which is simple... however with a relevant severity.)
Regards,
Andreas Henriksson
n i386 chroot which previously failed).
(Note: The initial two lines in debian/rules could also be replaced by
`include /usr/share/dpkg/architecture.mk` for further slight modernization.)
Regards,
Andreas Henriksson
--- a/debian/rules 2023-01-14 19:20:32.572449385 +
+++ b/debian/rules
esn't seem release-critical to me
so consider if maybe the severity should be downgraded.
Regards,
Andreas Henriksson
Hello,
So the mipsel FTBFS is because of a failing test-case that was added in
the 1.30-1 version of fakeroot.
For more information on this issue see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023286#48
Regards,
Andreas Henriksson
p8.fix_code(), but at the same time changes like these might cause
alot of breakage (atleast if used in tests like in this case).
Regards,
Andreas Henriksson
/commit/abb1979d20d9a3290442d5d0ed304ce24c0a710e
Regards,
Andreas Henriksson
the debian collectd packaging git repo has been
opened, albeit with a different patch than upstreams:
https://salsa.debian.org/debian/pkg-collectd/-/merge_requests/11
Regards,
Andreas Henriksson
On Tue, Jan 03, 2023 at 11:56:51PM +0100, Andreas Henriksson wrote:
> On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote:
> > On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> > > rpi_4
> > > rpi_4_32b
[...]
Hello again,
While I on
general feedback if it's suitable to upload the experimental
package to unstable this close to the freeze (which I feel will need
to happen ASAP or wait until after the release).
If I don't get any feedback, I will likely not upload to unstable.
Regards,
Andreas Henriksson
On Tue, Jan 03, 2023 at 11:46:31PM +0100, Andreas Henriksson wrote:
> On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> > rpi_4
> > rpi_4_32b
>
> I dug up my old dusty rpi4 which I probably haven't touched
> since last time we spoke about u-boot on
On Wed, Dec 28, 2022 at 04:11:04PM -0800, Vagrant Cascadian wrote:
> rpi_4
> rpi_4_32b
I dug up my old dusty rpi4 which I probably haven't touched
since last time we spoke about u-boot on it.
I've tested only the 64bit (arm64) version so far.
The version that was on the sd-card since last time:
quot;# /var/lib/popa3d should be created by package" well it's /var
so don't trust it to be unchanged. Should probably wrap the
chmod/chown commands in an `if test -d /var/lib/popa3d ; then`.
Regards,
Andreas Henriksson
diff --git a/debian/postinst b/debian/postinst
index 75e
ings seems to work as expected to me, although DLNA/UPnP-AV itself and
proprietary vendors implementations of it are indeed quite confusing.
>
> VLC and Kodi do detect them.
Regards,
Andreas Henriksson
Control: tag -1 pending
Hello,
Bug #1008395 in golang-github-bmatsuo-lmdb-go 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-bma
Control: tag -1 pending
Hello,
Bug #998586 in libgxps 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/gnome-team/libgxps/-/commit/d59208d95950ea4726f4e8fea6d827
Control: tag -1 pending
Hello,
Bug #1004615 in gnome-sound-recorder 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/gnome-team/gnome-sound-recorder/-/commit/259
Control: tag -1 pending
Hello,
Bug #998528 in file-roller 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/gnome-team/file-roller/-/commit/30206544c02e1e62318696
nges like that are likely better done
during the next development cycle... and by someone who knows
what the future direction of gnome-todo might be, but feel free
to send a merge-request!)
Regards,
Andreas Henriksson
Hello again,
On Wed, Apr 07, 2021 at 11:36:30AM +0200, Andreas Henriksson wrote:
[...]
> I've submitted a merge-request that fixes the imminent problems for
> review at:
> https://salsa.debian.org/debian/libubootenv/-/merge_requests/3
[...]
I've studied things a bit more an
ould/should
be forwarded upstream as well A library should not print to stdout
like this!
Regards,
Andreas Henriksson
(and deps) from bullseye. The p2p feature is thus not a new
kernel feature or similar, simply new info exposed by NM.
As mentioned, this is fixed in upstream release 2.2.
I've also filed a pre-approval request to update to 2.2 during freeze,
see Bug#984925
Regards,
Andreas Henriksson
Control: tag -1 pending
Hello,
Bug #983917 in libgweather 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/gnome-team/libgweather/-/commit/bacbf97c838abb33c18ace
ng fixup commit in gnome-weather is:
https://gitlab.gnome.org/GNOME/gnome-weather/-/commit/6763f7dc9cb25eac4aa13e94e07ea932a42c8e4d
Regards,
Andreas Henriksson
e!
Please also feel free to follow up you severity bump with a
justification pointing out which specific policy paragraph you're
refering to.
Hope this helps. Please also remember that my views are mine and might
not neccessarily reflect the official pkg-gnome standpoint.
Regards,
Andreas Henriksson
rong doesn't feel like debian style either. Wouldn't it be better
to just ask the release team which solution they prefer and possibly
get an exception for introducing a new binary package if needed?
Regards,
Andreas Henriksson
time to try to convince people to try other
solutions and if that fails still have time to re-introduce things
before freeze happens
For now I'm lowering the severity below RC (maybe we should just close
this bug report. Feel free to do so as far as I'm concerned atleast).
And as s
rove the packaging logic so files are /moved/
from debian/build/install/ into the respective binary package directory
and then fail the build if debian/build/install/ still contains anything
(ie. similar to --fail-missing in generic dh packages).
Regards,
Andreas Henriksson
On Tue, Feb 16, 2021 at 10:35:53PM +0100, Andreas Henriksson wrote:
> Control: notfound -1 20201218-3
> Control: found -1 20210208-1
>
> On Tue, Feb 16, 2021 at 08:20:47AM +0100, maximilian attems wrote:
> [...]
> > right it was replaced by newer cypress version and there sh
ot* install it into debian/firmware-brcm80211 .
The reason seems to be that the filename is not listed in
debian/firmware-brcm80211.metainfo.xml
(The cypress filename the symlink points to is however listed
and that gets installed as expected.)
HTH
Regards,
Andreas Henriksson
cgi-bin/cvsweb/src/usr.bin/ssh/sk-usbhid.c
(and seems also being active in
https://github.com/openssh/openssh-portable ). YOLO and I'm moving on.
Regards,
Andreas Henriksson
fflags_udeb := $(confflags)
>
>
> Thanks,
>
> --
> Colin Watson (he/him) [cjwat...@debian.org]
Regards,
Andreas Henriksson
aintaining it still.
Unless there's a conclusion about this bug report I don't really see
much point in proceeding though.
Regards,
Andreas Henriksson
Control: tags -1 + patch
Hi again,
Attached is a possibly upstreamable patch that solves our problem
(but the base problem still exists in the code for anyone wishing to
build with openssl disabled).
See description in patch itself.
Regards,
Andreas Henriksson
Description: sk-usbhid.c: Only
Hi,
On Sun, Feb 14, 2021 at 09:18:25AM +0100, Andreas Henriksson wrote:
> On Sun, Feb 14, 2021 at 08:32:58AM +0100, Andreas Henriksson wrote:
> > Hello,
> >
> > On Sat, Feb 13, 2021 at 06:04:32PM +0100, Lucas Nussbaum wrote:
> > > Source: openssh
> > > Ver
On Sun, Feb 14, 2021 at 08:32:58AM +0100, Andreas Henriksson wrote:
> Hello,
>
> On Sat, Feb 13, 2021 at 06:04:32PM +0100, Lucas Nussbaum wrote:
> > Source: openssh
> > Version: 1:8.4p1-3
> > Severity: serious
> > Justification: FTBFS on amd64
[...]
> (Which
oesn't have any way to pass in -lmd as far as I can tell
(Which in turn makes me wonder if something changed on the libmd side?)
Regards,
Andreas Henriksson
e a good thing
to do, so for the record I'm not against that. My skepticism is more
at why this is not a wishlist bug report (that would be much better to
adress early in a development cycle, rather than when we're already in
the bullseye freeze).
Regards,
Andreas Henriksson
PS. The reason f
Control: tag -1 pending
Hello,
Bug #976518 in gsound 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/gnome-team/gsound/-/commit/8bc79f25bd01f5a3ac035d40bef40ac7
space) and
a/ not properly handling its expansion b/ mocking it as an executable
including the space.
The attached patch fixes the problem, but I have no idea why this
problem appeared now
Regards,
Andreas Henriksson
diff -uriNp xdg-utils-1.1.3.orig/autotests/t-xdg-open.sh xdg-utils-1.1.3/a
he archive,
however it might be useful to understand what purpose having it in
the emacs/site-lisp path serves and if that's actually preferred over
just maintaining the status quo.
Regards,
Andreas Henriksson
n boost ?
I think it would be better if the libphonenumber-dev pulled in
everything needed in every supported configuration (or alternatively
provided 2 separate -dev packages, eg. libphonenumber-boost-dev which
deps on libphonennumber-dev plus required boost parts but that seems
too complex for little gain - not to mention needing to go through NEW).
Regards,
Andreas Henriksson
u please provide a full build log?
Can you think of anything that might be relevant why the build
would fail for you but not me?
Regards,
Andreas Henriksson
This was not the case in libheif 1.9 (currently in testing).
The pkg-config file is thus broken when installing libheif-dev in
a clean system where the pkg-config files of aom, etc are not installed.
As far as I can tell the fix is:
a/ Add libaom-dev, libde265-dev and libx265-dev to Depends of libheif-dev
b/ preferably also write a simple autopkgtest that checks if libheif.pc
works as expected
eg. `pkg-config --exists --print-errors "libheif > 1.5.1"` should
not error out when libheif-dev is installed.
Regards,
Andreas Henriksson
Control: tag -1 pending
Hello,
Bug #957912 in vinagre 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/gnome-team/vinagre/-/commit/62a378f51dc54aa25d8484214bf85e
Control: tag -1 pending
Hello,
Bug #978357 in gnome-todo 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/gnome-team/gnome-todo/-/commit/e56c1f7ad205341e8b6f23db
tty clear that these are test-suite only
issues and not issues in the actual product.
I would thus personally just disable the test-suite on !amd64 if no
porter is interested in fixing the testsuite (unless we agree this
issue simply can be downgraded to non-RC).
Regards,
Andreas Henriksson
=976926
for the bug report against bbolt.
Regards,
Andreas Henriksson
Hello again,
On Sat, Dec 12, 2020 at 05:59:37PM +0100, Andreas Henriksson wrote:
> Hello all,
>
> 1 down, 1 to go info below.
>
> On Wed, Dec 09, 2020 at 10:03:31AM +0100, Lucas Nussbaum wrote:
> [...]
> > > === RUN TestBucket_Stats
> > > bucket_tes
ction
db.MustClose() runs and calls into things that tries
to take a read-write lock of db.mmaplock which times out.
The added tx.Rollback() on a read-only tx basically only
removes the transaction and releases the db.mmaplock.
I have no idea why this would not also trigger on any other arch.
Regards,
Andreas Henriksson
works? The ones which
someone is actually promising to support?)
The practical problem is that if the arch field is changed
what happens to the entire reverse dependency tree that has
accumulated? Getting one thing removed from the archive is hard
and painful enough
Regards,
Andreas Henriksson
obj-aarch64-linux-gnu && go test -vet=off -v -p 4
> > github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu
> > github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker
> > github.com/shirou/gopsutil/host github.com/shirou/gopsutil/internal/common
> > g
Hello Holger,
On Tue, Oct 06, 2020 at 11:25:06PM +, Holger Wansing wrote:
> Hi,
>
> Am Dienstag, 6. Oktober 2020 schrieb Andreas Henriksson:
> > Could you please test rebuilding kbd with --enable-libkeymap to
> > --disable-libkeymap in debian/rules?
>
> sbuild fa
be to refactor debian/rules to do two
separate flavoured builds with complete configure/build/install passes
for each flavour, to replace the current brittle hack that duplicates
the upstream build system as manual steps in debian/rules udeb build.
Help welcome here as well ofcourse.)
Regards,
Andreas Henriksson
Control: tag -1 pending
Hello,
Bug #967139 in gimp-help 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/gnome-team/gimp-help/-/commit/2cbd892e4913e5cbaaf079326a
1 - 100 of 749 matches
Mail list logo