(Posting this mostly as a status update to the bug report. Maybe jbicha
already has a plan for these.)
Regards,
Andreas Henriksson
Control: tag -1 pending
Hello,
Bug #907934 in gnome-usage 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-usage/commit/0e34e1d139bc83fade69536
Control: tag -1 pending
Hello,
Bug #908298 in gdk-pixbuf 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/gdk-pixbuf/commit/8edcee3d520416976f9748210
ee NM 1.14 in unstable/testing. (Ofcourse iwd can be used separately
but using it with NM is still probably quite likely thus having those
work together is probably a good idea for testing version.)
This bug report should be closed once we have network-manager 1.14 in
testing/buster.
Regards,
An
Regards,
Andreas Henriksson
z196 and above, Debian still supports z10. If we
>and/or upstream get a patch to support z10, we can add this back. :)
> - see also https://github.com/golang/go/issues/16637
(Adding and removing this on a whim rather than actually considering if
you can really support it
On Sun, Nov 20, 2016 at 07:11:31PM +0100, Andreas Henriksson wrote:
[...]
> Please discuss this with ftp team.
[...]
Seconds after sending this mail I was pointed to #845003
Thanks for filing that and lets see how it goes.
Regards,
Andreas Henriksson
rity reasons under wayland. Remoting functionality needs to be
implemented at a different level in the stack on Wayland (and vino
is not part of the solution at all).
Regards,
Andreas Henriksson
w
if this file was ever modified by you or not?
Regards,
Andreas Henriksson
, explicitly disabling openssl somehow might be even better
to prevent accidentally building against it (again) in the future.
I doubt the severity for that is serious until the problem actually
occurs again though.)
Would you agree?
Regards,
Andreas Henriksson
; Previous version works.
[...]
The attached debdiff incorporates a patch from fedora fixing the problem.
(Someone should take responsibility for getting this uploaded and
unblocked by the release team if they want to see gmrun stay in stretch.
If you need sponsorship feel free to ask me.)
Regards,
t should also be
available via some variable.
Advice on which alternative is preferred (by the maintainer) welcome!
Regards,
Andreas Henriksson
> Once the package has been uploaded I will file an unblock request for
> the release team.
Great.
--
Regards,
Andreas Henriksson
Hello Lukas,
On Fri, Mar 10, 2017 at 01:36:06PM +0100, Lukas Schwaighofer wrote:
> Hi Andreas,
>
> On Fri, 10 Mar 2017 13:14:57 +0100
> Andreas Henriksson wrote:
> > Please post the full .dsc url (so I can simply dget it, and I don't
> > care much about you us
27;s unclear about the "masked"
message they get when trying to start munin.service.
(Likely this bug report should be closed as "not a bug". People here
just seem to be very confused. Nothing to see please move along?!)
Regards,
Andreas Henriksson
ting nfs-blkmap.service on your system
and replace:
PIDFile=/var/run/blkmapd.pid
with:
PIDFile=/run/blkmapd.pid
.. and report back if that solves the issue or not?
(It looks to me like debian/patches/21-no-more-var-run.patch needs
to be updated to also cover systemd/nfs-blkmap.service )
Regards,
Andreas Henriksson
g to touch the package...
At the same time I have to mention that bumping standards-version
and debhelper compat during freeze is something the release-team
really dislikes seeing in the debdiff for the unblock request.
Only essential changes.
Regards,
Andreas Henriksson
Control: tags -1 + pending
Hello.
On Mon, Mar 13, 2017 at 02:33:27PM -0700, Nye Liu wrote:
> On Sat, Mar 11, 2017 at 08:15:02PM +0100, Andreas Henriksson wrote:
> > Could you please test editing nfs-blkmap.service on your system
> > and replace:
> > PIDFile=/var/run
rotNames->disposeName);
free(rotNames->disposeName);
rotNames->disposeName = NULL;
}
.. and the stretch version:
/* if the last rotation doesn't exist, that's okay */
if (rotNames->disposeName && access(rotNames->disposeName, F_OK)) {
message(MESS_DEBUG,
"log %s doesn't exist -- won't try to dispose of it\n",
rotNames->disposeName);
free(rotNames->disposeName);
rotNames->disposeName = NULL;
}
Please note that the !debug condition has been dropped, which seems
correct to me.
I thus very much suspect this is an already fixed bug.
Regards,
Andreas Henriksson
y, so downgrading
severity atleast. Feel free to close if you can confirm my suspicion
above is the cause or find something else.)
Regards,
Andreas Henriksson
c7e7fe86b9c652b731be2c1715db4c7b838bca9d
Author: Andreas Henriksson
Date: Wed Mar 22 09:50:17 2017 +0100
Add evolution-data-server dependency
Closes: #858206
diff --git a/debian/changelog b/debian/changelog
index e81904c..2b88979 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+gnome-todo
in strikes
when you try to remove/purge your way out of the failed install removing
the user and all its data. Just one example out of many. Nowhere does it
seem to account for conffiles having been removed by the admin as another
example. These maintainer scripts are just waay to buggy/unreliabl
orrectness, you should include a 'Justification:' field
in your bug report citing which section of debian policy you're
arguing isn't followed.
In practice is doesn't really matter though. Any severity >= serious
is considered "RC" (release critical), which has some implications
on testing migration.
Regards,
Andreas Henriksson
if you can come up with a nice
user-understandable description.
You might also want to file a minor bug report against firefox
(upstream?) to give a less misleading error message.
Regards,
Andreas Henriksson
I'll add a note to util-linux.NEWS about DISPLAY and XAUTHORITY.
Regards,
Andreas Henriksson
Control: tag -1 pending
Hello,
Bug #905409 in util-linux 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/debian/util-linux/commit/e975bc5479c926360336585070c4b
Hello Helge Kreutzmann,
Sorry if my comments sounded too negative, some more reasoning below.
On Sun, Aug 12, 2018 at 04:35:47PM +0200, Helge Kreutzmann wrote:
> Hello Andreas Henriksson,
> I'm a bit puzzled by your e-mail. Simon asked me to provide some text,
> Chris prodded me
uess I have little option but to ask the relevant
debian entity group (tech-ctte, policy, release-team) about their
view on this. Either way, I'd like to hear how you think I should
continue.
Regards,
Andreas Henriksson
d....
Regards,
Andreas Henriksson
PS. debian/pydist-overrides should likely either be renamed
to debian/py3dist-overrides and updated, or the leftover
file removed. Keeping it makes no relevant difference so
I'd suggest removing it.
build] Error 2
>
This seems to be fixed upstream by:
https://github.com/aead/poly1305/commit/3fee0db0b63511234f7230da50b72414f6258f10
See also:
https://github.com/aead/chacha20/commit/52db354a4a380462fc762185d72dffb206e50a42
... and prior commits.
Regards,
Andreas Henriksson
Control: tags -1 + patch
Please see attached patch that makes sure config.h gets included
before HAVE_SYS_SYSMACROS_H is checked, so that major and minor
macros gets properly defined.
Regards,
Andreas Henriksson
diff -Nru fdutils-5.5-20060227/debian/changelog
fdutils-5.5-20060227/debian
Control: tag -1 pending
Hello,
Bug #918514 in golang-github-aead-poly1305 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-aead-po
block -1 by 918514 918515
thanks
Hopefully this ftbfs should vanish with the dependencies being fixed,
see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=918514
https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=918515
Regards,
Andreas Henriksson
has
there been any work on actual migration of current rng-tools users
configuration to what rng-tools5 uses?)
I'd be really interested to hear what people have on their minds for
this task and how I can help out.
Regards,
Andreas Henriksson
pristine-tar
If you don't have time to review, merge, upload I'm happy to help out
with a NMU. Just tell me about it
Regards,
Andreas Henriksson
ce 2019-01-12 15:12:29.219286997
+0100
@@ -12,7 +12,7 @@
ReadOnlyPaths=/
ReadWritePaths=/proc/irq
RestrictAddressFamilies=AF_UNIX
-TemporaryFileSystem=/run:ro
+TemporaryFileSystem=/run
# If IRQBALANCE_ONESHOT environment is set, the service will exit so:
Restart=no
Regards,
Andreas Henriksson
Control: forwarded -1 https://github.com/Irqbalance/irqbalance/issues/85
See also upsteam bug report about the abstract socket name,
which bigon just pointed out to me.
Regards,
Andreas Henriksson
n a less network restricted environment, maybe that
confirms the suspision without having to dive deep in every problem
instantly.
HTH
The long-term solution should probably be that the test-suite
automatically checks pre-conditions it has and skips the tests
that can not be run under the current build environment automatically.
Regards,
Andreas Henriksson
Control: forwarded -1
https://salsa.debian.org/multimedia-team/linuxptp/merge_requests/1
Control: tags -1 + patch
Sent a merge-request on salsa with a patch that fixes the problem
by making sure (which defines clockid_t) is included
before
Regards,
Andreas Henriksson
he build-dependencies.
(Atleast the package builds, I haven't done any other tests.)
For your convenience I've submitted a merge request with the fix,
and as a bonus also the translation update.... see above.
Regards,
Andreas Henriksson
sort according to C locale, see
http://sources.debian.net/src/libsoup2.4/2.50.0-2/libsoup/Makefile.am/#L315
Please feel free to investigate why this does not work as intended
if building under different locales is important to you.
(And ofcourse preferrably get any changes needed merged via upstream.)
Regards,
Andreas Henriksson
testing once
that's possible and hopefully also alert some reverse dep
maintainers about this via http://packages.qa.debian.org
so that the removal can happen before Stretch.
Regards,
Andreas Henriksson
last time around so I think
it should be good enough this time as well.
See https://bugs.debian.org/797074 which I set as a blocker for
this bug-report.
Regards,
Andreas Henriksson
[2654]: segfault at 8 ip 7f6ae6c13132 sp
> 7fff82ba7850 error 4 in libdleyna-server-1.0.so.1.0.3[7f6ae6c03000+21000]
[...]
bt full
(See also https://wiki.debian.org/HowToGetABacktrace )
Regards,
Andreas Henriksson
ted I wonder if you can still reproduce this
issue or if it might have been solved in imobiledevice since?
Regards,
Andreas Henriksson
Control: tags -1 + patch
Hello!
Please see attached patch to generate the Built-Using field.
(This needs to be generate as the Built-Using is supposed to declare a
strict relation to the exact version of dietlibc that was used to build
the package.)
Regards,
Andreas Henriksson
diff -u integrit
upload or we can RM
storaged.
(Personally I think storaged is the better name but I'd really like
to avoid renaming the DBus interfaces and having to port everything
over but lets see what Martin and others finally decide.)
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
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
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
.. 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
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
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
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
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
ould appreciate
you blocking their package from testing migration until you've uploaded
a relinted version of your package.)
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
27;ll also need a build-dep on package containing systemd.pc)
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
"$(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
/sources.debian.org/src/gammu/1.42.0-7/debian/gammu-smsd.install/#L5
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
es.debian.org/src/pam/1.5.2-6/debian/rules/#L33
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
=get_option.*systemdsystemunitdir&literal=0&perpkg=1
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
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
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
g --variable=systemdsystemunitdir systemd
(Note: You'll also need to build-dep on pkg-config and systemd, for
systemd.pc)
Regards,
Andreas Henriksson
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
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.
erity of this bug report should be downgraded
(maybe even closed)?
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
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
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
get to add pkg-config and systemd (for systemd.pc) to
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
, thus you'll need to
build-depend on the systemd package (as you already list
pkg-config in build-deps).
Regards,
Andreas Henriksson
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
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...
unitdir+path%3ACMake&literal=0
https://codesearch.debian.net/search?q=systemdsystemunitdir+path%3AFindSystemd&literal=0
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
ng in here that is controversial or wrong, but
hopefully there isn't.
Regards,
Andreas Henriksson
uld give it ASAP!
What do you think?
Regards,
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
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
&
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
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
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
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
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, 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:
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
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: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
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
/commit/abb1979d20d9a3290442d5d0ed304ce24c0a710e
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
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
esn't seem release-critical to me
so consider if maybe the severity should be downgraded.
Regards,
Andreas Henriksson
1 - 100 of 761 matches
Mail list logo
