Package: qmapshack
Version: 1.17.1-1+b6
Severity: normal
qmapshack's brouter setup wizard fails to parse the version of the jre
shipped with debian, resulting in being unable to complete the setup.
this is upstream https://github.com/Maproom/qmapshack/issues/664 .
they don't seem particularly in
On Mon, Mar 31, 2025 at 12:04:37PM +0100, Chris Lamb wrote:
we (RB) have found that using reference filestamps like
this to seed dates tends to be both unpredictable and opaque.
yes, when you don't really understand the build system and basically
hope for the best, then that's what you get.
H
On Mon, Mar 31, 2025 at 11:17:15AM +0100, Chris Lamb wrote:
+-RELEASE_DATE=`date -r $0 +%F`
++RELEASE_DATE=m4_esyscmd([date --utc --date="@${SOURCE_DATE_EPOCH:-$(date
+%s)}" +%Y-%m-%d])
did you even try to understand what the upstream code does, and why it
fails here?
the problem is that debi
i think this should be most probably closed. alejandro?
On Sun, Feb 02, 2025 at 02:47:55PM +0100, Alejandro Colomar wrote:
With the former, I might confuse it for an internal error notice.
seems a bit far-fetched, but fair enough. done in commit 281a9ba4.
note that no line number is printed, as that would be potentially
confusing, given that repetit
i recommend closing this bug, as nothing will be done about it beyond
what i already wrote.
this has been discussed upstream, see
https://sourceforge.net/p/isync/mailman/isync-devel/thread/20a4197379dc195856bcd53cb0ecb325%40doctors.org.uk/
my conclusion was that there is a bug in debian, but obviously not in
the isync package, but something openssl-related.
Source: xserver-xorg-video-nouveau
Version: 1:1.0.17-3
Severity: wishlist
a new upstream version 1.0.18 has been available for a few months
already.
afaict, it contains only one bugfix and a few cleanups, but still.
Package: slick-greeter
Version: 2.0.9-1
Severity: normal
the loop that processes the config file should skip lines that start
with # after being stripped.
actually, given that this is a python script, it could use much cleaner
and more exact matching of variable assignments.
On Tue, Jan 28, 2025 at 10:31:00AM +0100, Timo Röhling wrote:
mbsync -ls shows all folders I expect to be there on both sides, in
particular all the folders below INBOX which refuse to synchronize.
yeah, then it's very likely the aforementioned bug.
you should be fine with a git build from mast
isync has become a bit more strict about semantically questionable
configurations; maybe you ran into that.
or maybe you ran into the bug fixed by 8c781d4f. i need to finally
release 1.5.1 ...
please post the Store's config, and the actual file system layout (find
-type d; excerpt sufficient).
I didn't know what to do, or if it was even my fault.
that seems rather weird to me, having thought that the message is
entirely self-explanatory.
I would keep a HISTORY section in the manual page,
that might make sense for options that changed semantically rather than
just being renamed.
o
upstream commit a1be7e9a3 already addresses this adequately, imo.
Package: python3-numba
Version: 0.59.1+dfsg-3
Severity: important
the current version in sid is incompatible with python 3.13, and as that
has now become the default, numba gets forcibly uninstalled.
luckily, the current upstream version of numba is 0.61, which is
perfectly fine with py 3.13.
up
Package: python3-alsaaudio
Version: 0.10.0-0.1
Severity: wishlist
pyalsaaudio 0.11.0 has been available for a while.
Package: git-absorb
Version: 0.6.11-2
Severity: wishlist
the current version is 0.6.16. the one in the debian package is more
than a year old.
Package: libgtk-4-1
Followup-For: Bug #1086037
X-Debbugs-Cc: v8fl8y...@mozmail.com
You are absolutely right! I have a locally built version of the vulkan library
and somehow managed to pollute the linker search path without noticing on the
last build.
I apologize for taking up your time, and I ap
the most plausible explanation is that you have a concurrent background
sync job. maybe triggered by a directory watcher on the mailboxes, which
would cause the race somewhat reliably.
isync uses process-associated locking, so an internal origin is
impossible even you are trying to sync the same
i don't have a backup of the system i just upgraded (which is a rarely
used laptop), but on my desktop i have a full mirror on a secondary
disk, which i didn't update after the last upgrade yet, and here i see
that /lib64 _was_ a symlink ... but it pointed to /lib!?
i won't exclude the possibility
On Wed, Jul 17, 2024 at 04:28:16PM +0200, Chris Hofstaedtler wrote:
in the meantime, please provide more details:
- full upgrade log
attached
- dpkg and apt versions used to upgrade
if i'm reading the log correctly, apt 2.7.6 and dpkg 1.22.1.
- sources.list and priorities
- selected/inst
Package: base-files
Version: 13.3
Severity: important
while upgrading the system after a rather long time, this happened:
# apt dist-upgrade
...
Unpacking base-files (13.3) over (13) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-fU8xAF/12-base-files_13.3_amd64.deb (--unpack):
trying
Package: sensible-utils
Version: 0.0.23
Severity: important
the recursion checks in sensible-utils return zero instead of 126 or
127, so the command simply fails instead of trying the next option.
also, arguably, $PAGER, etc. should be simply ignored if they match the
script under execution, to s
Package: qt6-5compat-dev
Version: 6.6.2-1+b1
Severity: normal
i installed qt6-l10n-tools 6.6 from experimental, which also upgraded
qtbase and some other packages. however, it left qt6-5compat-dev at the
unstable 6.4, thus breaking subsequent builds due to binary
incompatibility; i got a bunch of
Package: kmscon
Version: 9.0.0-5+b1
Followup-For: Bug #1061686
"I suspect systemd is spooking somewhere" is quite correct: the package
leaves /etc/systemd/system/autovt@.service dangling instead of restoring
it to getty@.service.
i find the whole integration kinda questionable. why isn't there a
Package: valgrind
Version: 1:3.20.0-2.1
Severity: wishlist
the currently packaged version is more than 1.5 years old.
upstream released 3.23 a few days ago.
Package: lirc
Version: 0.10.2-0.7
Severity: important
# systemctl status lircd
● lircd.service - Flexible IR remote input/output application support
Loaded: loaded (/usr/lib/systemd/system/lircd.service; enabled; preset:
enabled)
Active: active (running) since Wed 2024-03-13 23:05:48 CE
it would be more logical to invert the provides, having gdb provide
gdb-minimal, and have packages depend on gdb-minimal where it's
sufficient. currently, such packages express it by depending on
"gdb-minimal | gdb".
Package: lirc
Version: 0.10.2-0.5
Severity: important
from the journal:
Feb 07 00:04:05 ugly lircd-0.10.2[35370]: Notice: lircd(default) ready, using
/var/run/lirc/lircd
Feb 07 00:05:35 ugly systemd[1]: lircd.service: start operation timed out.
Terminating.
so lircd gets terminated despite eve
Package: gimp-gmic
Version: 2.9.4-4+b4
Severity: wishlist
the current stable version is 3.3.0 as of now. the debian package lags
it quite a bit.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architec
turns out my suspicion was correct.
the issue is tracked upstream at
https://bugreports.qt.io/browse/QTBUG-87776 .
please re-open the bug and retitle it appropriately.
fwiw, because i failed to find a minimal replacement MTA that i actually
liked, i just sort of revived masqmail:
https://github.com/ossilator/masqmail
i did some build system polishing; otherwise it's taken straight from
meillo's repo, and i don't think i'll do much more with it.
i also upda
huh?
if the declaration of the private dependency is just missing in that qtc
plugin, then fair enough. but that doesn't explain the total garbage
error message which suggests some kind of internal error (it sort of
suggests that an incomplete package is installed like in the other bug i
repo
cmake files are necessary for static builds, because the "plugins"
aren't actually plugins then. at least i'm assuming that this
functionality wasn't lost during the cmake port ...
plugins may also be listed as runtime dependencies for deployment.
theoretically - whether that was actually imp
Package: qt6-declarative-dev
Version: 6.4.2+dfsg-1
Severity: normal
while building qt creator, cmake spits out this message during the
generation phase (that is, after configuration is done):
==
CMake Error in src/plugins/qmldesigner/CMakeLists.txt:
Imported target "Qt::QmlPrivate" include
Package: qt6-declarative-dev
Version: 6.4.2+dfsg-1
Severity: normal
trying to build qt creator, i got this error message:
===
CMake Error at
/usr/lib/x86_64-linux-gnu/cmake/Qt6QmlCompilerPrivate/Qt6QmlLintQuickPluginTargets.cmake:96
(message):
The imported target "Qt6::QmlLintQuickPlugin"
Package: btrfs-progs
Version: 6.1.2-1
Severity: normal
for the purpose of helping people to move away from reiserfs, it would
make sense to actually build btrfs-convert with support for it.
the catch is that libreiserfscore is not packaged separately; rather,
it's built into reiserfsprogs. i gu
On Fri, Nov 18, 2022 at 08:51:51PM +0100, Pierre-Elliott Bécue wrote:
Would you agree to release isync 1.4.5 or do I need to import your
license exception?
the thing is that it isn't even in master - i pushed a preliminary
commit to a branch. the reason for that is that its legal foundation is
Package: libkf5service5
Version: 5.97.0-1
Severity: grave
Justification: renders package unusable
/usr/bin/startplasma-x11: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libKF5Service.so.5: undefined symbol:
_ZN8KSandbox9isFlatpakEv
-- System Information:
Debian Release: bookworm/sid
APT pr
which would be confusing even
if this wasn't a perfectly finalized report, as it actually means
"sending unmodified generated report" or some such.
-- Package-specific info:
** Environment settings:
EDITOR="sensible-editor"
PAGER="sensible-pager"
EMAIL="
t, or at least allowing the envelopefrom option
being empty (note: i didn't check whether that's already the case - but
the reportbug.conf manual does not mention it).
-- Package-specific info:
** Environment settings:
EDITOR="sensible-editor"
PAGER="sensible-pa
Package: python3-pyaudio
Version: 0.2.11-1.4
Severity: normal
pyaudio started throwing this message:
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
https://stackoverflow.com/questions/70344884/pyaudio-write-systemerror-py-ssize-t-clean-macro-must-be-defined-for-format
ex
On Fri, Jun 10, 2022 at 10:45:53PM +0200, Bastian Germann wrote:
isync (mbsync binary) is GPL-2+ licensed and depends on libsasl2-2,
which is licensed under CMU's BSD-4-clause license and covered by the
RSA-MD and OpenSSL licenses.
whoops.
3) Ask upstream to add a license exception for libsa
isync had the --one2one option since v0.9, and the Patterns option since
v1.0. i think these satisfy the request.
fixed upstream in v1.4.3.
since v1.0, one can use
mbsync --push-delete
to achieve the desired effect.
maybe the openssl/libssl package changed its default config, or maybe
the affected server simply had its configuration fixed. in either case
it wasn't an isync bug to start with.
for reference, isync has the CipherString option since v1.4, which could
be used to work around this issue.
there have been some subtle changes in the namespace interpretation over
the years, which caused some configuration breakage in (more or less)
corner cases. also, some genuine bugs, which have been fixed long
since.
i don't think it makes sense to keep this report open, given its age.
fixed upstream in v1.4 for good (dynamic buffer).
for v1.3, see #1004979.
i recommend closing this report, as it's useless in its current form,
and the issue has almost certainly been fixed upstream meanwhile.
feel like doing that? it's a low-risk, high-impact change, and thus a
reasonable request. i'd include it upstream if 1.3 was still active.
some more context probably helps:
...
Setting up linux-image-5.15.0-3-amd64 (5.15.15-2) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.15.0-3-amd64:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-3-amd64
...
/et
two+ more years later, current version is 13.8.1, build system is still
maven-based.
Package: nvidia-legacy-340xx-driver
Version: 340.108-11
Severity: important
udev fails to associate the nvidia graphics card with a seat (query with
`loginctl seat-status seat0`), which results in modern display managers
like sddm not even attempting to start a graphical login screen.
special rul
On Sat, Dec 11, 2021 at 09:16:04AM +0100, Marc Haber wrote:
is this still reproducible in current unstable?
no (logs edited for brevity):
=== su
(to root) ossi on pts/13
pam_xauth(su:session): requesting user 1000/100, target user 0/0
pam_xauth(su:session): reading keys from `/home/ossi/.
a corner case. an arbitrary nesting depth limitation of 10 would be
easy to do, though.
>From 9b8fc616f3986c3bcdc8195f5ec221c38043e8d6 Mon Sep 17 00:00:00 2001
From: Oswald Buddenhagen
Date: Mon, 21 Jun 2021 11:35:24 +0200
Subject: [PATCH] limit maildir nesting depth
this is a cheap way to ca
Package: masqmail
Version: 0.3.4-1
Severity: wishlist
version 0.3.5 has been available at
http://marmaro.de/prog/masqmail/files/ since 2015; i'd say it's about
time to package it.
Package: imagemagick-6.q16
Version: 8:6.9.11.60+dfsg-1
Severity: minor
the command name in the first line of
/usr/lib/mime/packages/imagemagick-6.q16 contains an extra trailing
period, which presumably causes the display of image/avs to fail.
guys, are you serious? it's fine that you document a dependency on a
missing systemd feature for a clean solution (if you actually file a
request upstream), but the bug is nonetheless in the current
implementation of the apt-listbugs package, and can be worked around
there (e.g., by polling the
Package: python3-alsaaudio
Version: 0.8.4-1.1+b3
Severity: normal
the new release has been available for a while already. please upgrade.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1
Package: hugin
Version: 2020.0.0+dfsg-1
Severity: important
ASSERT INFO:
../src/gtk/bitmap.cpp(1262): assert "bmpData->m_pixbufNoMask" failed in
SetSourceSurface(): no bitmap data
BACKTRACE:
[1] wxBitmap::SetSourceSurface(_cairo*, int, int, wxColour const*, wxColour
const*) const
[2] wxBitmap::
can something be done about this, please? this affects every 3rd party
repository, and it seems a bit off that aptitude can't do something that
the "regular" apt tools have done for years.
well, the consequences should be somewhat predictable to anyone who's
been using sid for a while. also, they are clearly visible when you use
an interactive update tool like aptitude (which you really should when
you use sid).
more of a mystery to me is why this is done this way at all. there
this bug is duplicated by #970430, from which i learned that the
unversioned packages are indeed supposed to be deleted (see also
#937695).
this resolution appears satisfactory:
--\ Remove the following packages:
libpython-dev
libpython-stdlib
python-dev
python-minimal
py
On Tue, Jul 14, 2020 at 10:51:06PM +0200, Francesco Poli wrote:
Do you mean that your "no network when apt-listbugs timer runs" only
happens immediately after a wake-up from a suspended state and only
when the system has had no chance to run the timer between 7:00 a.m.
and the wake-up itself?
y
On Mon, Jul 13, 2020 at 11:25:21PM +0200, Francesco Poli wrote:
I haven't found a satisfying strategy to get what I wanted.
ok, fair enough. please make sure the maintainers know about this
requirement if you haven't done so yet.
Could it be that the timer was just about to be triggered, whe
On Tue, Jul 07, 2020 at 10:53:59PM +0200, Francesco Poli wrote:
On Tue, 7 Jul 2020 20:17:15 +0200 Oswald Buddenhagen wrote:
there is a report every hour despite it claiming to be a daily job.
that's weird at least.
It works this way by design. [...]
The rationale is: the job mu
On Tue, Jul 07, 2020 at 07:46:50PM +0200, Francesco Poli wrote:
• when did it begin?
i don't remember - i tend to ignore non-critical errors at first.
the journal doesn't say when it began, either, as it says that the
sevice "succeeded" despite the error mail ...
but there are actually clues
Package: apt-listbugs
Version: 0.1.32
Severity: normal
for some days/weeks now, i get this mail every day:
--
From: apt-listbugs timer
To: root
Subject: prefclean output on ugly
/usr/libexec/apt-listbugs/prefclean:
E: getaddrinfo: Temporary failure in name resolution (bu
Package: qtcreator
Version: 4.11.0-2
Followup-For: Bug #952718
i just wasted about half an hour on researching this, so i'll summarize
my current understanding:
libclang-N needs to depend on libclang-common-N-dev, as otherwise it's
dysfunctional.
failing that, qtcreator needs to recommend libc
Package: python3-q-text-as-data
Version: 1.7.4+2018.12.21+git+28f776ed46-2
Severity: normal
the current upstream version on github is 2.0.10. please package it.
repeated attempts to contact mswatch's author have failed. :-(
anyway, i suggest to close this bug, as mbsync itself works just fine
for all i can tell.
Package: aptitude
Version: 0.8.12-1
Severity: normal
while upgrading apt from within aptitude, i got this error:
[...]
Setting up libapt-pkg5.0:amd64 (1.8.4) ...
(Reading database ... 316101 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.8.4_amd64.deb ...
Unp
Steve McIntyre :
> Hi Leah,
>
> On Wed, Jul 31, 2019 at 10:19:19AM +0200, Leah Oswald wrote:
> >Package: debian-installer
> >Version: 20190702
> >Severity: important
> >Tags: d-i
> >
> >Hey, we tried to install debian buster with our preseed file (see:
Package: debian-installer
Version: 20190702
Severity: important
Tags: d-i
Hey, we tried to install debian buster with our preseed file (see:
https://paste.debian.net/hidden/ecde0369/) that was working with debian stretch.
Now the installation fails at installing the grub dummy ("Unable to install
On Wed, Apr 03, 2019 at 03:19:57PM -0400, Nik A. Melchior wrote:
> + mbsync hostname:lists.ip
> Maildir error: store 'local', folder 'lists.ip': SubFolders style Maildir++
> does not support dots in mailbox names
>
you need to use the canonical mailbox name, so hostname:lists/ip
Package: xoscope
Version: 2.2-1+b1
Followup-For: Bug #888704
indeed, libasound2-dev needs to be added to Build-depends. things work
fine after this is done.
note that esd support is also not built in due to being utterly
obsolete. that's just fine, but i'd suggest to patch the man page
accordingl
Package: kopete
Version: 4:17.08.3-2
Severity: important
when an xmpp account is configured and "Enable libjingle support" is
enabled, kopete will spawn libjingle-call (being online is apparently
sufficient). this will immediately crash, leaving such an entry in
the journal:
Nov 14 00:23:30 host
Package: ngspice
Version: 27-1
Severity: wishlist
Dear Maintainer,
upstream released version 28 with some interesting new features
a few months ago.
ok, that seems convincing. i bumped it to 4KiB (just to be safe) on the
1.3 branch.
please increase the buffer to whatever size works and then send me the
output of an -l session with the -D option, so i can see where i made
the wrong assumption.
Package: iotop
Version: 0.6-24-g733f3f8-1
Followup-For: Bug #737043
the current incarnation of this (?) problem:
Traceback (most recent call last):
File "/usr/sbin/iotop", line 17, in
main()
File "/usr/lib/python3/dist-packages/iotop/ui.py", line 737, in main
main_loop()
File "/usr
Package: prosody
Version: 0.9.12-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I've installed prosody on a nearly new installed debian strech system.
After installation I noticed s2s connections issues with some of my
jabber/xmpp contacts as the server was't able to c
Source: gcc-7
Version: 7.2.0-1
Severity: normal
the cpp/gcc/g++-6 packages are around 25mb.
the gcc-7 equivalents are 150+mb.
while this isn't necessarily a bug, it looks *relly* fishy, so i'm
bringing it up for attention.
-- System Information:
Debian Release: buster/sid
APT prefers unstab
i upstreamed this patch with an adjusted commit message.
if the timing is accurate, then the event that triggered both problems
is that yahoo implemented SASL.
the error message you're getting is just an elaborate way of saying
"login failed". judging by the mozilla bug, the problem might be that
you're using different capitalization of your login name.
this should be considered a duplicate of Bug#871765.
the patch is rather incomplete in the compat wrapper part. but my own
patch does not touch it at all, and i think i'll leave it at that
(introducing new features to the compat wrapper seems anti-thetical).
also, don't mix in the ssl2/3 removal
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-legacy-340xx-driver
I may have done:
aptitude -r install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')
nvidia-driver
instead of the mentioned first.
Did it again, now it worked.
This bug can be closed - thank you
> cannot reproduce in a fresh Stretch chroot. All the correct packages
> are installed.
>
> Are you sure you don't have previously installed leftovers?
No, I'm not. I did "apt-get purge nvidia*", but that seems not to have
been enough. What shall I do?
I came with an upgrade from 8.9, but was p
On Mon, Jan 16, 2017 at 06:54:33PM +0100, chrysn wrote:
> Oswald, do you think you could apply that patch to the 1.2 branch?
>
that's entirely out of the question.
i need to finally make an 1.3 release. i just have a bunch of things
cooking which i want to get done first ...
Package: qtcreator
Version: 4.1.0-3+b1
Severity: normal
switching to the welcome screen yields this message:
qrc:/timeline/TimelineContent.qml:29:1: module "QtQml.Models" is not installed
installing qml-module-qtqml-models2 manually makes it go away.
(the welcome screen is still empty even wit
i just pushed a fix to master.
-no-pie is not a useful option here, because it's passed to the _linker_
only.
i got it to build with this minimal patch:
--- a/Makefile
+++ b/Makefile
@@ -400,5 +400,5 @@ KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes
-Wno-trigraphs \
-Werror-implicit-function-declarati
ok, i did misread the spec in a subtle way. the thing is that while all
other folders are physically nested under INBOX, the imap view puts them
at the same (root) level. to get them shown as subfolders of INBOX, they
need to have _two_ leading dots, as we've seen in the example with
evolution (tho
please also save a message to INBOX and find out where it ends up. i'm
interested how the physical location of INBOX relates to ~/Mail.
On Tue, Oct 04, 2016 at 05:57:35PM -0400, Nik Melchior wrote:
> I don't know whose interpretation of Maildir++ is correct, but Courier
> does in fact prepend a '.' for top-level mailboxes.
>
please post your on-disk layout and the imap view (output from mbsync -l
-Dn -a is sufficient, provided you
fixed in git on isync_1_2_branch.
On Tue, Jul 28, 2015 at 09:21:57AM +0100, Ian Campbell wrote:
> It would be super useful if mbsync -l could produce the actual literal path
> of the Maildir to which a given folder was being sync'd. With sufficient
> debug/verbosity I can infer from the "reading sync state" message, but
> having a
On Sun, May 10, 2015 at 04:04:59AM +0200, Guillem Jover wrote:
> And while I'm not trying to be obtuse here, the way I read the specs I
> don't see anything wrong with my reasoning.
>
well, maybe you should re-read the mbsync manual then, to get a factual
basis for your reasoning. you are *still*
On Mon, May 04, 2015 at 10:40:19PM +0200, Guillem Jover wrote:
> Either that or I'm very confused…
>
i'd bet on the latter. ;)
Path is not the top-level folder - it is a "namespace" that contains
top-level folders.
this is also what you'd find on an actual imap server.
--
To UNSUBSCRIBE, email
On Mon, May 04, 2015 at 08:12:08PM +0200, Guillem Jover wrote:
> It seems to me that either «SubFolders Maildir++» does not work as
> documented or the documentation is not clear enough, (or I don't
> understand it).
>
your config attempts to have dots prefixed to the top-level folders'
names. the
1 - 100 of 317 matches
Mail list logo
