Nevermind, it was only coincidence, I guess I installed tor and updated
systemd at the same time, and ran into #840376. So my issue is not about
USETOR afterall.
Hello,
I also have this issue. It prevents me from syncing symlinks. :/
It seems that d/rules is trying to inject a clever version string, and
it fails for some reason.
Cheers,
Ben
Control: severity -1 minor
Thanks
Hello Wolfgang,
thanks for your quick response!
With your calls, you should not use the '-f' parameter. Without '-f',
the timestamp is passed on to date/gdate for parsing, which yields the
following for me on Debian Buster x86_64:
That changes the behavior:
Control: found -1 18.1-4
Thanks
Hello,
still happens.
This is strictly necessary for the recommended "upgrade-all" method [1].
Pip currently has no other way to do this [2], and this feature is
blocked by other issues [3], so "list --outdated" will continue to be of
interest for a long time.
Control: found -1 1.8.10-2
Heyaloha,
it seems like this is going to take a while to update.
Meanwhile, I sent in a patch [1], and it got "applied, with a small
change" [2]. You may want to do the following:
apt-get source network-manager-applet
sudo apt-get build-dep network-
Heyaloha,
is it possible that this is a duplicate of #865013?
- Both crash Consistently when clicking "modify"
- Both crash in src/libnma/nma-cert-chooser-button.c due to this line:
g_critical (…, error->message);
(it used to be line 95, currently it's line 98)
Note that I sent in a p
Control: found -1 1:3.22.4-3
Thanks
Hello,
still happens.
It looks like it's not necessary to complete the game.
I don't know why I didn't paste it the first time, but here's a Scheme
backtrace.
-- 8< --
Variation: westhaven
Scheme error:
(#f Wrong number of arguments to
Hello,
my best guess is that in Looper.C:63, the access of the field `Ppreset`
reads uninitialized memory.
Manual workaround: Add `Ppreset = 0;` at the top and hope that this
value makes any sense.
Works for me.
Cheers,
Ben Wiederhake
control: close -1
thanks
Hello,
I'm sorry, apparently this is already fixed in the actual current
version. It appears that the git repo is older than whatever apt-get
source serves.
Cheers,
Ben Wiederhake
Control: reopen
Thanks
Hello,
as far as I can see, this has been fixed to the following:
###
# Magic system request Key
# 0=disable, 1=enable all, >1 bitmask of sysrq functions
# Debian kernels have this set to 438 which is the OR
Here's the behavior of `xinput --watch-props` with the right device ID.
Actually I think it might make sense to look at that *when you change the
settings*.
I did, see previous mails: xinput only sees the "Synaptics Off" property
changing. xinput does *not* see anything related to "disable fo
Hello,
thanks for your quick response and pointers!
For the current settings and the rounding, can you check what ends up in the
input layer? You can use the xinput command to look into that. I don't use a
touchpad so I can't really give more details.
Here's the behavior of `xinput --watch-pr
I forgot to mention:
- This is not related to #728844 for two reasons: (1) the slider *does*
work, it's just inappropriately rounded. (2) Different slider ("Disable
Touchpad" duration, not "Pointer Acceleration")
- This is not related to #851802 either.
There is no other bug related to touchp
Reported upstream as https://bugzilla.gnome.org/show_bug.cgi?id=779149
Hello,
sorry for the long wait, real life happened. Also, note the version bump
in the subject from 1.2.3 to 1.2.5.
Seems like it, true, but sadly is necessary. The package is in version
control, and unless we provide pre-bundled origtars somewhere (which
won't happen), this has to build the
Hello,
They generate the orig tarball.
The watchfile is to check for the newest version.
These are unrelated things.
no. they are completely related things.
uscan downloads the tarball from the watch file, and if the uscan downloaded
tarball doesn't fit your needs
you have to call the repack
Control: tags -1 - moreinfo
Hello,
thanks for taking a look at this package :D
I'm not sure if anybody picked up the work for this bug, but lets do
another review:
- -please drop commented default stuff from rules file
- -please merge changelog in one single entry
(also "mentors" is not a t
Control: tag -1 + patch
Hello,
I'd like to suggest a patch for this, please find them enclosed.
The patches base on the currently unreleased ed9350e, or
"v2.15.10-2-ged9350e" as git describe puts it.
In fact, these are two patches, one of which "cleans up" a specific
aspect so that the secon
* d/README.source
- In upstream README.md you tell Debian Maintainers to use the
genorigtar.sh. Looking at Policy §4.14, I think README.source should
also instruct to do that.
* Paul Wise already wondered if libtgl should be separately packaged.
The related Debian Policy bit is §4.13 [3]
[F
Telegram-purple is a generic purple-plugin,
[...] including "pidgin" into the name would be highly misleading.
Other libpurple backends are named pidgin-* (like pidgin-openfetion,
pidgin-skype and pidgin-librvp) and I don't see any libpurple backends
with other names. Perhaps these packages shoul
Hello,
>> * Package name: telegram-purple
This should probably be named pidgin-telegram in line with the other
pidgin/libpurple plugins we have in the archive already.
Oh, I forgot to include the rationale for sticking with the name.
Telegram-purple is a generic purple-plugin, and also
Since there's somewhere a guideline saying that we should sometimes
post updates:
- Debianisation is technically complete, see
https://mentors.debian.net/package/telegram-purple
Still the same: technically complete. This is not the obstacle.
- Translation is coming along nicely, but we stil
Control: owner -1 !
Since there's somewhere a guideline saying that we should sometimes post
updates:
- Debianisation is technically complete, see
https://mentors.debian.net/package/telegram-purple (However, we will
change roles, so that I can soon start the sponsoring process.)
- Translatio
Control: close -1
Hello,
thanks for the swift response!
I suggest you contacting debian-mentors@ to ask for help if you're not sure
this is an actual lintian bug.
Thanks, I'll do that the next time. Sorry for bothering you.
Furthermore, ITPs are meant to be sent out *before* starting to w
24 matches
Mail list logo
