❦ 18 June 2021 11:48 +02, Stefan Schlesinger:
> Thanks for the fix! Is the updated version going to transition to
> buster-backports at some point?
Hello Stefan,
I have just uploaded it.
--
Follow each decision as closely as possible with its associated action.
- The Elements of
Control: tags -1 - moreinfo
❦ 11 June 2021 21:05 +02, Sebastian Ramacher:
>> > Could you also provide us with a binary debdiff to be sure that these
>> > changes in d/rules have the desired effect?
>>
>> Hello Sebastian,
>>
>> Here it is:
>>
>> [The following lists of changes regard files as
Control: tags -1 - moreinfo
>> [ Reason ]
>> It ships SOF audio firmware signed by Intel and is needed on modern
>> platforms using SOF. The 1.7 release will be needed to make hardware
>> that would be released in September work. I have tested the resulting
>> package on my laptop and it works
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Mark Pearson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is a pre-approval for package firmware-sof.
[ Reason ]
It ships SOF audio firmware signed by Intel and is
-
diff --git a/debian/changelog b/debian/changelog
index 8d8be4a94d23..05580f6f4a6c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+exabgp (4.2.8-2) unstable; urgency=medium
+
+ * Patch exabgp.service to fix socket creation on start.
+Closes: #886568.
+
+ -- Vincent Bernat
❦ 28 mai 2021 16:03 +01, Tim Small:
> After installing the version 2.2.9-1 Debian package, the default
> /etc/haproxy/haproxy.cfg contains an SSL configuration excerpt in the
> global section which has been generated with:
>
> https://ssl-config.mozilla.org/#server=haproxy=2.0.3=intermediate
>
>
❦ 19 mai 2021 15:27 +02, Stefan Schlesinger:
> All released versions of haproxy 2.2 contain a nasty bug which will
> continue to override the backend server status as UP, when the
> agent-check returns UP, although the http-check reports the backend as
> down.
>
> The issue was fixed upstream[1]
❦ 6 juin 2010 21:13 +02, Fabrice Lorrain:
> Using lldp with HP procurve switches, I've been using the posibility
> of configuring LLDP in <> ways on each port :
> - TX = transmit only mode
> - RX = receive only mode
> - TX_RX = mixte mode, TX & RX
>
> lldpd doesn't seem to provide such
severity 984767 normal
tag 984767 + moreinfo
thanks
❦ 8 mars 2021 08:55 +01, Johann Queuniet:
> I have issues with building packages with dh-virtualenv using a compat
> of 12 or higher, ending up with the following error:
>
> ```
> debian/rules binary
> dh binary --with python-virtualenv
❦ 24 avril 2021 16:15 +02, Salvatore Bonaccorso:
> Is this still something we should consider, or can the bug be closed?
I suppose that's since almost nobody chimes in in all these years, there
is no need.
--
Watch out for off-by-one errors.
- The Elements of Programming Style
❦ 11 avril 2021 18:44 -07, Josh Triplett:
>> > Whether you have an initramfs or not is orthogonal to DHCP
>> > configuration. The kernel's built-in DHCP configuration works even if
>> > you're not using a network filesystem as the root filesystem.
>>
>> The initramfs is supposed to take
Hey!
Feel free to upload yourself!
On March 28, 2021 12:24:52 AM GMT+01:00, Thomas Goirand wrote:
>Package: python3-netaddr
>Version: 0.7.19-1
>Severity: important
>
>Hi,
>
>OpenStack Manila, for the next version of OpenStack, needs version 0.8.0.
>Please package this when possible. Otherwise,
❦ 19 mars 2021 17:01 +01, Thomas Goirand:
> DKG for example, did a presentation, if I remember well, in Germany,
> where he explained that he belives 7 days is the best practice. I have
> to admit there's no established norm in Debian, but I do agree with what
> DKG says about this.
This
❦ 18 mars 2021 11:46 +01, Thomas Goirand:
> By default, haproxy /etc/logrotate.d/haproxy is set with:
>
> rotate 52
>
> This is keeping a WAY too much log history. This isn't reasonable, especially
> with (very) busy servers. This also is a privacy concern: the best practices
> in Debian is to
❦ 9 mars 2021 21:03 GMT, Debian Bug Tracking System:
> This is not the same issue at all, and this is not new in FF80 either.
> It has been this way for, essentially, ever. If you want to file a
> separate bug for this, fine, but piling on this unrelated bug, with all
> its history being
❦ 25 février 2021 08:38 +01, Patrick J.:
>> By any chance, maybe you did install the firmwares manually in the past,
>> so you already had a intel/sof-tplg directory which then was not
>> replaced by the symlink?
>
> Yes, indeed. I tried some manual approaches in the past before the
>
❦ 24 février 2021 23:26 +01, Vincent Bernat:
>> I installed the firmware-sof-signed package on a Dell Inspiron 7590 and
>> still no sound was detected.
>>
>> The "dmesg" hinted that the file "intel/sof-tplg/sof-hda-generic-2ch.tplg"
>>
❦ 24 février 2021 14:24 +01, Patrick Jaap:
> I installed the firmware-sof-signed package on a Dell Inspiron 7590 and still
> no sound was detected.
>
> The "dmesg" hinted that the file "intel/sof-tplg/sof-hda-generic-2ch.tplg"
> was not found.
>
> Currently, the package copies the files to
❦ 2 février 2021 21:08 +01, Helmut Grohne:
>> Is that something that needs to go for Bullseye (honest question)?
>
> No.
>
> I say so when I think something is urgent. This is a drop-in-the-bucket
> kind of bug.
OK, I have queued your change to the 0.8.0 release which will happen
after
debian/control
> libcbor-0.5.0+dfsg/debian/control
> --- libcbor-0.5.0+dfsg/debian/control 2018-05-17 17:08:03.0 +0200
> +++ libcbor-0.5.0+dfsg/debian/control 2021-02-02 07:03:06.0 +0100
> @@ -2,11 +2,13 @@
> Priority: optional
> Maintainer: Vincent Bernat
❦ 27 janvier 2021 09:35 -04, David Bremner:
> I just NMUed js2-mode (delayed/2). Since the old VCS was gone, I also set up
>
> https://salsa.debian.org/emacsen-team/js2-mode
>
> I propose we move the package to the debian emacsen team
> umbrella. I've invited you to the team on salsa, so you
Control: forcemerge 964537 949570
❦ 22 janvier 2020 16:58 +11, Dmitry Smirnov:
>> dropwatch should not use the private binutils shared libraries. If it
>> cannot be dropped, then please link those statically and document it with
>> the Built-Using tag in the binary package.
>
> I don't
❦ 19 janvier 2021 10:57 +01, Vincent Bernat:
>> bpftrace should not depend on the non-public binutils ABI. This always
>> generated
>> an upper dependency on libbinutils. If you think it's worth having this
>> dependency, please statically link with libbinutils and re
❦ 19 janvier 2021 08:33 +01, Matthias Klose:
> bpftrace should not depend on the non-public binutils ABI. This always
> generated
> an upper dependency on libbinutils. If you think it's worth having this
> dependency, please statically link with libbinutils and record the the version
> used in
❦ 17 janvier 2021 10:53 -05, Nicolas Mora:
>> How outdated is the package for you?
>>
> Right now it isn't.
>
> My package glewlwyd doesn't use the new features and I've tested it
> with libcbor 0.8 with no noticeable bug so here's no rush AFAICT. But
> the versions since 0.5 fix lots of bugs
❦ 17 janvier 2021 09:25 -05, Nicolas Mora:
> libcbor 0.8.0 has been released, is it possible to upgrade the debian package
> before bullseye soft freeze? The current version is outdated.
It is a bit late. Upstream also has introduced proper SO versioning, so
we need a new binary package. It
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Upstream request the package to be removed from Debian as it is
replaced by cryptsetup-reencrypt and running a conversion with recent
cryptsetup variants will lead to data loss.
For example:
❦ 7 janvier 2021 09:46 GMT, Luca Boccassi:
> CC'ing Vincent, as maintainer of bpftrace - looks like this will be
> part of bullseye. There should be no changes from the point of view of
> bpftrace, as it's an internal detail of bpfcc's library, but just in
> case.
Let's try. If there is a
❦ 4 janvier 2021 11:52 +01, Katharina Drexel:
> Meanwhile, the logging problem is solved upstream (tested with
> 2.4-dev4-4d71176).
> With the default config and the rsyslog snippet (49-haproxy.conf) the logs go
> into haproxy.log again and look like:
>
> Jan 4 11:40:53 haproxy-test
❦ 28 décembre 2020 10:32 -05, Sam Hartman:
> But for example, we have a rule that is fairly basic to our community
> that we don't break upgrades, or at least we try hard not to.
This is becoming harder and harder because we pile more and more choices
(init choice, initramfs choice, merged-usr
Package: chromium
Version: 87.0.4280.88-0.2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
Thanks for updating Chromium!
Since 87.0.4280.88, hardware acceleration seems to be totally disabled:
Graphics Feature Status
Canvas: Software only. Hardware acceleration disabled
❦ 18 décembre 2020 22:38 +0530, Ritesh Raj Sarraf:
> Thank you Vincent for the fix. It is committed to the repository and
> will be uploaded soon.
Thanks, it fixes the issue with bpftrace!
--
Whenever you find that you are on the side of the majority, it is time
to reform.
--
clone 977549 -1
reassign -1 libbpfcc
retitle -1 libbpfcc: please compile with -DENABLE_LLVM_SHARED=on
severity -1 normal
found -1 0.17.0-8
block 977549 by -1
thanks
❦ 16 décembre 2020 16:48 +01, Emanuele Rocca:
> Package: bpftrace
> Version: 0.11.3-3
> Severity: grave
> Justification: renders
❦ 15 décembre 2020 11:14 GMT, Mark Hindley:
>> Okay, great, I now see a clearer argument in favour of dropping the init
>> script: enabling the maintainer to preemptively avoid dealing with bugs
>> which are likely to generate hostility, rather than just the idea that
>> there could be bugs
❦ 11 décembre 2020 20:36 -05, Mark Pearson:
>> They seem to say future releases will be tagged. So, I think you should
>> use in gbp.conf:
>>
>> upstream-tag = v%(version%~%-)s
>> pristine-tar = False
>>
>> No need for upstream-branch since you won't use "gbp import-orig" as the
>> origin
owner 960788 markpear...@lenovo.com
quit
❦ 11 décembre 2020 12:15 -05, Mark Pearson:
>>> I did have to comment out "overlay = True" in the gbp.conf - it gave me
>>> an error that I'll have to dig into.
>>
>> That's because you went for the first "classic" solution. I was pushing
>> for the
❦ 6 décembre 2020 11:59 +01, Matthias Klose:
> import ctypes.util
> ctypes.util.find_library("libc")
>> Traceback (most recent call last):
>> File "", line 1, in
>> File "/usr/lib/python3.9/ctypes/util.py", line 341, in find_library
>> _get_soname(_findLib_gcc(name)) or
Package: libpython3.9-stdlib
Version: 3.9.1~rc1-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
>>> import ctypes.util
>>> ctypes.util.find_library("libc")
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.9/ctypes/util.py", line 341, in
❦ 1 décembre 2020 22:28 +01, Moritz Mühlenhoff:
> Michael has been heroically keeping up with this beast of a codebase for
> years,
> but we clearly need a broader base to sustain it going forward.
In the past, it was team-maintained. I don't remember exactly, but I
think there was a
❦ 19 novembre 2020 09:04 GMT, Matthew Vernon:
> 3) many upstreams (esp. those who support BSD) ship a sysvinit file,
> again making the daemon (source at least) package the natural place to
> keep it.
I don't think this is very common. Init scripts are very specific to a
distribution. A Debian
❦ 17 novembre 2020 14:52 +01, Katharina Drexel:
> When updating from haproxy 2.2.5 to 2.3.0, the logs only go into syslog, not
> to haproxy.log any more.
> For fixing that, you need an additional line in the 49-haproxy.conf of
> rsyslog:
>
> local0.*/var/log/haproxy.log
>
> The diff
❦ 6 octobre 2020 12:32 +03, Jyrki Pulliainen:
> Now, python3.8-venv contains the ensurepip module. But to me it is very
> unclear if python3.8-venv is going to disappear? It also makes depending on
> these packages generally a lot more brittle: I'd rather depend on
> python3-venv than
Package: flatpak
Version: 1.8.2-2
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
After upgrading to 1.8.2-2, I cannot run any Flatpak. I have tried
com.spotify.Client and us.zoom.Zoom and both of them are returning the
following error:
error: The name
Package: webext-browserpass
Version: 3.4.1-4+b1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
When Firefox starts, Browserpass icons appear then shortly disappear.
Disabling/enabling the extension is enough to fix this as long as
Firefox keeps running.
Upstream has
❦ 31 juillet 2020 10:14 +02, Salvatore Bonaccorso:
>> > > > This needs to be rebased to the 1.8.19-1+deb10u1 which was released
>> > > > as
>> > > > DSA 4577-1 AFAICT.
>> > >
>> > > Oh, sorry. Here is the updated patch.
>> >
>> > Please go ahead.
>>
>> Too late for buster 10.4 but actually
❦ 23 juillet 2020 12:59 +03, Peter Pentchev:
>> > If you add "-fcommon" to gcc-10 it should work.
>>
>> this would be a work-around, not a fix.
>
> Hi,
>
> Fix proposed:
>
> https://savannah.gnu.org/bugs/index.php?58810
>
> https://salsa.debian.org/debian/xnee/-/merge_requests/1
Thanks! I'll
❦ 20 juillet 2020 15:00 +00, Chris Lamb:
>> Lintian is a very useful tool, but too many stuff is a warning while
>> this is a matter of opinion. I have given up on the "info" level
>> since a long time for similar reasons. I would like not to give up on
>> the "warning" level.
>
> (It is a shame
Hello Felix,
Thanks for your quick reply.
❦ 19 juillet 2020 09:33 -07, Felix Lechner:
>> the shebang is harmless and I won't
>> patch or other upstream about a harmless shebang.
>
> As explained in this MR [2], we consider the hashbang an error. The
> snippets are not meant to be executed. The
Package: lintian
Version: 2.84.0
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
I have just noticed that bash-completion-with-hashbang got bump from
minor to certain, after commit 70eaca50411. I don't understand the
rationale behind this commit, but in case of
❦ 13 juillet 2020 21:24 +02, Christian Göttsche:
> * Package name: ncdu
>Version : 1.15.1-0.1
>Upstream Author : Yoran Heling
> * URL : https://dev.yorhel.nl/ncdu/
> * License : expat
> * Vcs : None
>Section : admin
You should
❦ 12 juillet 2020 16:14 -04, Wesley Schwengle:
> In December 2019 version 1.7.0 was released and in April 2020 1.7.1 and
> 1.7.2 were released. It adds a very useful feature:
>
> https://cookiecutter.readthedocs.io/en/1.7.2/advanced/directories.html
>
> I would like to make use of this. Could
e enough to send a patch?
Yes. Here it is!
From bf4e9caa65eabc4ef77fe5cb46dfaa42f7bd4d4c Mon Sep 17 00:00:00 2001
From: Vincent Bernat
Date: Sat, 13 Jun 2020 14:31:28 +0200
Subject: [PATCH] d/control: add build-dependencies to enable X11 backend
---
debian/changelog | 7 +++
debian/control |
Source: wlroots
Version: 0.10.1-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
Would it be possible to compile wlroots with X11 backend? This enables
running Sway over X11 for testing purposes by running it with
WLR_BACKENDS=x11. Currently, X11 support is not compiled
Package: libfacter3.11.0
Version: 3.11.0-4.1
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
set = {__val = {0, 1431634051, 94476679444720, 139623352393688, 0,
94476679915560, 94476680133744,
Package: pulseaudio
Version: 13.99.1-1
Severity: normal
Tags: patch upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When using PulseAudio from experimental with the version of
alsa-ucm-conf from unstable, the sound is not working properly on
sound cards relying on UCM, like the
❦ 4 juin 2020 16:56 +08, Paul Wise:
>> My understanding is the SOF team didn't want to use intel-firmware but
>> I'm trying to find the discussion on the SOF mailing list as to why.
>
> I'm not sure what you mean by intel-firmware. Based on the Repology
> website I guess you mean the Intel CPU
On Wed, 22 Apr 2020 11:55:00 +0300 jim_p wrote:
> As the title suggests, please update chromium to 81.0.4044.113 (or later),
> because it includes a patch for CVE-2020-6457, which is a critical security
> issue. More info here
>
❦ 2 juin 2020 09:11 +03, Alexandru Ardelean:
> Thanks for the message.
> I'm still interested in getting this into Debian.
> I'd probably need to organize a bit, and ping some co-maintainers.
> Maybe also some polish to the debian rules [for packaging].
> But, let's see.
>
> I'll try to make
Hello Alexandru!
If you are still interested into getting mstpd in Debian, I can help you
with that.
Thanks.
--
Make sure every module hides something.
- The Elements of Programming Style (Kernighan & Plauger)
❦ 26 avril 2020 19:21 +02, Marco d'Itri:
>> It is a fork of bgpq3.
> I appreciate the ITP, but is there any point now in keeping bgpq3
> around?
I don't think it is up to us to decide what people should use. bgpq4 is
still pretty recent and bgpq3 is still maintained. Just the change of
the
Package: wnpp
Severity: wishlist
Owner: Vincent Bernat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: bgpq4
Version : 0.0.6
Upstream Author : Job Snijders
* URL : https://github.com/bgp/bgpq4
* License : BSD 2-clause
Programming Lang: C
Control: forwarded -1 https://github.com/criticalstack/libevhtp/pull/143
Control: block -1 by 958467
<#secure method=pgpmime mode=sign>
❦ 26 avril 2020 13:45 +02, Alexandre Rossi:
> It appears that $libdir is empty:
>
> $ cat /usr/lib/x86_64-linux-gnu/pkgconfig/evhtp.pc
> prefix=/usr
>
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The package is dead upstream and is superseded by pyeapi which is
present in Debian. It is not compatible with Python 3. Please, remove.
-BEGIN PGP SIGNATURE-
❦ 24 avril 2020 20:54 +02, Moritz Mühlenhoff:
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2removal
>>
>> Python2 becomes end-of-live upstream, and Debian aims to remove
>> Python2 from the distribution, as discussed in
>>
❦ 1 avril 2020 10:01 +02, Wouter Verhelst:
> xnee comes with two GUI components: gnee, a GUI version of cnee, and
> pnee, a Gnome applet.
>
> At least gnee seems to compile just fine on my buster system. However,
> neither of these two are shipped as part of the Debian package.
See:
-
❦ 30 mars 2020 01:36 +01, Ben Hutchings:
>> Please consider adding kernel module '9p' to the cloud image. It is
>> impossible to passthrough filesystem from hypervisor with the current cloud
>> image and there are no additional packages to install it. The only way that
>> I know to passthrough
Source: golang-goprotobuf
Version: 1.3.4-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
After the upgrade to 1.3.4, the generated code is not usable with
golang-google-grpc-dev currently in unstable. Both packages share a
tight relationship.
. CVE-2019-18277.
+
+ -- Vincent Bernat Sun, 26 Jan 2020 12:54:30 +0100
+
haproxy (1.8.19-1+deb10u1) buster-security; urgency=high
* Apply two patches around HTTP/2 header validation allowing an attacker
diff --git a/debian/logrotate.conf b/debian/logrotate.conf
index 442dc4e01e79..ad2031f198e6 100
❦ 4 février 2020 17:17 +00, Chris Hide :
> I believe there is an inconsistency in the location of the PID file.
> In /lib/systemd/system/haproxy.service the PID file is /run/haproxy.pid.
> In /etc/init.d/haproxy the PID file is /var/run/${BASENAME}.pid.
That's the same file. /var/run should be
Package: libgcc1
Version: 1:10-20200202-1
Followup-For: Bug #950551
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
On both my systems running unstable, libgcc-s1 is installed, but I
don't have /usr/lib/x86_64-linux-gnu/libgcc_s.so.1. So, it seems
something removes it. I have no clue on
Package: initramfs-tools
Version: 0.136
Followup-For: Bug #950254
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I was also hit by this bug. The issue is that the upload of gcc-10
moved libgcc_s.so to /lib instead of /lib/x86_64-linux-gnu. The hack
in cryptroot hook doesn't find it
Package: xss-lock
Version: 0.3.0-8
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
On my system, /usr/share/zsh/site-functions is not part of $fpath. I
don't know how easy it is to override the completion target with cmake
or if we need to patch it.
See bottom of
Package: x11-xserver-utils
Version: 7.7+8
Followup-For: Bug #784324
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
I am also hit by xrandr segfaulting from time to time. I don't know if
I am in the same case as Steve (its coredump is too old to match
current binary), but I have traced my
❦ 29 janvier 2020 12:43 +00, Simon McVittie :
>> More specifically, it breaks certificate trust in libraries and
>> applications inside the runtime if they are linked to p11-kit older
>> than 0.23.19. In particular this affects anything that uses GNUTLS,
>> notably the GNOME stack.
>
> I've sent
Package: p11-kit
Version: 0.23.19-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
Upgarding p11-kit to 0.23.19 breaks many Flatpaks, including Steam and
Spotify. It seems Flatpak is using p11-kit-remote and the on-wire
format was updated, but the details are a bit fuzzy.
❦ 26 janvier 2020 13:00 +01, Vincent Bernat :
>>> The logrotate configuration file for HAProxy doesn't signal rsyslog
>>> correctly. Therefore, logs are not really rotated and on a moderately
>>> busy site, this can fill up a log partition. When running with
>>
a49cf 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+haproxy (1.8.19-1+deb10u1) buster; urgency=medium
+
+ * d/logrotate.conf: use rsyslog helper instead of SysV init script.
+Closes: #946973.
+ * d/patches: reject messages where "chunked" is missing from
+
rom bcf26bb2d684d793792742e30fd66c5b4018b53f Mon Sep 17 00:00:00 2001
From: Vincent Bernat
Date: Fri, 20 Dec 2019 08:20:40 +0100
Subject: [PATCH] d/logrotate.conf: use rsyslog helper instead of SysV init
script
---
debian/changelog | 7 +++
debian/logrotate.conf | 2 +-
2 files changed, 8 insertions(+), 1 delet
❦ 21 janvier 2020 23:51 +00, Tim Bray :
>> This setting is for the size of the route cache. You can have far more
>> routes. In the past, there were bugs where each lookup will be put in
>> cache, but since 4.2, only the PMTU exceptions are stored in cache. See
>>
❦ 21 janvier 2020 18:58 +00, Tim Bray :
> I also agree.
>
> I've just spent a month tracking down an issue where IPv6 networking
> connections hang. Using Debian buster, 4.19.0-6-amd64.
>
> Machine carries a full IPv6 table, received via BGP. About 80k routes.
>
> Symptoms were BFD dropping
❦ 17 janvier 2020 20:23 +01, Davide Prina :
> Jan 15 11:37:33 prinad03 kernel: [ 9354.966794] i915 :00:02.0: GPU
> HANG: ecode 9:1:0x, hang on rcs0
You may want to follow this thread. 5.3 and 5.4 seem to be difficult
kernels for Intel graphic cards. It's unknown if 5.5 will fix it
Package: firmware-iwlwifi
Version: 20190717-2
Followup-For: Bug #940813
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
I was running in this problem (as well as some unreliability with the
Bluetooth). Instead of downgrading to -41, I have updated the -46 to
the version in
Package: grub2-common
Version: 2.04-5
Followup-For: Bug #945404
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
On a system where it works, I get:
# grub-probe -t abstraction
/usr/share/desktop-base/futureprototype-theme/grub/grub-16x9.png
cryptodisk
luks
gcry_rijndael
gcry_rijndael
Hello Michael,
I was able to hit the bug again. It seems I have to go to another wifi
network, then back to my home network to hit the bug. On the
client-side, I get:
janv. 06 18:57:13 zoro NetworkManager[75721]: [1578333433.9474] dhcp4
(wlp3s0): activation: beginning transaction (timeout in
❦ 29 décembre 2019 13:40 +01, Michael Biebl :
> Can you provide a full, verbose debug log:
>
> https://wiki.gnome.org/Projects/NetworkManager/Debugging
>
> Which dhcp client do you use: internal, isc-dhcp-client, ...?
I am using the internal client. Unfortunately, I am not able to
reproduce the
Package: network-manager
Followup-For: Bug #947613
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
I've got the same problem. Comparing the output of "journalctl -u
NetworkManager" on both versions, the only difference I am able to
spot is that with 1.22.2-1, I have these lines:
déc. 29
Hello Alexandre,
Bugs #931617 and #940036 are quite annoying. Both of them have very
simple fixes. Can I make an upload for the next point release to fix
them?
Thanks.
--
When you are about to die, a wombat is better than no company at all.
-- Roger Zelazny, "Doorways in the
Source: golang-github-xenolf-lego
Version: 0.3.1-5
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
The package is quite outdated in Debian (0.3.1 while upstream is
3.2.0). Contributors from upstream are wondering[2] if this could be
fixed. I know there are many
Hello,
I have pushed the change for the next uploads in unstable and
experimental. I understand you would also like this to be fixed in
stable, but I currently didn't do anything about that.
--
Follow each decision as closely as possible with its associated action.
- The Elements of
Package: lintian
Version: 2.41.0
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
service-key-has-whitespace says service files should not have spaces
surrounding the = key. This is not true and this has been clarified in
systemd 242 that this is authorized. See
❦ 4 novembre 2019 18:55 +0530, Vasudeva Sathish Kamath :
> I'm trying simple oneliner with bpftrace given in the man pages. For example
> following
>
> bpftrace -e 'tracepoint:syscalls:sys_enter_execve { join(args->argv); }'
>
> It fails with following error message
>
> Error creating map:
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
Please, remove pyvnc2swf, it is dead upstream, not really relevant
today and Python 2-only.
Thanks.
-BEGIN PGP SIGNATURE-
iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl17OfQSHGJlcm5hdEBk
Package: wnpp
Severity: wishlist
Owner: Vincent Bernat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: xtl
Version : 0.6.5
Upstream Author : QuantStack
* URL : https://github.com/QuantStack/xtl
* License : BSD
Programming Lang: C
❦ 5 septembre 2019 12:42 +02, Marcin Juszkiewicz
:
> I am using Kolla to build container images with OpenStack components.
> One of images contains haproxy. And it fails to build.
>
> Part of build is creation of users with fixed UID/GID values. Which
> works fine for most situations as
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When first packages, napalm was distributed as several tarball: a base
one and one for each supported platform. This is not the case anymore
as a single tarball now provides support for a set of
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When first packages, napalm was distributed as several tarball: a base
one and one for each supported platform. This is not the case anymore
as a single tarball now provides support for a set of
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When first packages, napalm was distributed as several tarball: a base
one and one for each supported platform. This is not the case anymore
as a single tarball now provides support for a set of
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When first packages, napalm was distributed as several tarball: a base
one and one for each supported platform. This is not the case anymore
as a single tarball now provides support for a set of
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When first packages, napalm was distributed as several tarball: a base
one and one for each supported platform. This is not the case anymore
as a single tarball now provides support for a set of
Package: ftp.debian.org
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
When first packages, napalm was distributed as several tarball: a base
one and one for each supported platform. This is not the case anymore
as a single tarball now provides support for a set of
101 - 200 of 2341 matches
Mail list logo
