Package: nginx-light
Version: 1.18.0-6
Followup-For: Bug #869799
X-Debbugs-Cc: and...@lists.savchenko.net
This is still a problem for in Bullseye. Any plan to remove ipv6
directive in the default config before Debian v11 is released?
To reproduce:
1. Boot with `ipv6.disable=1`
2. Attempt to
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package micro-evtd
[ Reason ]
One-line patch to fix FTBFS (#987631). Also taking the opportunity to
update the Maintainer field; I hope that's OK.
[ Impact ]
The
Package: shim-signed
Version: 1.34~1+deb10u1+15.4-2~deb10u1
Severity: serious
X-Debbugs-Cc: none, Tollef Fog Heen
Looks like postinst is poking into /sys/firmware/efi, which doesn't
exist on a non-UEFI system.
Preparing to unpack .../shim-signed_1.34~1+deb10u1+15.4-2~deb10u1_amd64.deb ...
lowmem=2 worked nicely. I completed an installation successfully with
that setting. Thanks!
Is there anything I can do to help improve the default experience on
this target, besides documenting for others the process to set the extra
bootarg in the u-boot environment?
thanks for your work
Package: 3.0.2-1.1
Version: SoapFault - faultcode: 'SOAP-ENV:Server' faultstring: 'Processing
Failure' faultactor: 'null' detail: org.kxml2.kdom.Node@87c474c
Severity:
Tags:
X-Debbugs-CC:
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the
A couple comments below.
On Mon, May 3, 2021 at 2:24 PM Francesco Poli wrote:
>
> On Sun, 2 May 2021 14:11:59 -0700 Ross Boylan wrote:
>
> [...]
> > On Sun, May 2, 2021 at 11:08 AM Francesco Poli
> > wrote:
> [...]
> > > I wonder why logcheck does not send hourly mail messages about
> > >
On Tue, 4 May 2021, Faustin Lammler wrote:
Hi Matthew!
Thanks for your detailed report.
Appreciate the followup :)
Indeed, the generated log rotate seems wrong (and I am able to reproduce
the problem with 10.5 on sid).
Could you maybe help on this directly upstream
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package mina2
(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)
[
Package: python3-fdb
Version: 2.0.1-2
Severity: normal
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
Traceback (most recent call last):
...
File "/usr/lib/python3/dist-packages/fdb/fbcore.py", line 271, in
DateFromTicks
return apply(Date,
Package: release-notes
Severity: normal
Hi,
please add a new paragraph 5.1.13 (and move existing 5.1.14 to .14) regarding
exim and the new 'tainted data' issue.
Text copied from NEWS.Debian file:
---
Please consider exim 4.93/4.94 a *major* exim upgrade. It introduces the
concept of
Hi Lev,
Lev Lamberov writes:
> That's interesting! Thanks for your input.
Thanks! And you're welcome :-)
> I've tried Antoine's minimal configuration and can confirm that
> commenting out (package-initialize) resolves the problem. So, it
> really means that lsp-mode has an autoload cookie
Package: discover-data
Version: 2.2013.01.11
Severity: normal
Tags: d-i
Dear Maintainer,
Two years ago I purchased a Qotom Q190N MiniPC and successfully installed
Debian 8.2, subsequently upgraded to 10.1. A second Qotom of the same model
purchased a few months ago fails to install, even with
Hi Antoine,
I had started on a draft of this email before receiving your latest
update; however, I the info below is still relevant.
Antoine Beaupré writes:
> I still need to get to the office to confirm the fix, but this totally
> makes sense. I have a very old Emacs configuration, which I've
On Tue, 4 May 2021, Kurt Fitzner wrote:
> I just tried to install rcconf on a Debian testing sytem. Since rcconf
How is rcconf even useful on a nōn-sysvinit+sysv-rc system?
Maybe rcconf should depend on that or conflict with all others?
bye,
//mirabilos
--
Infrastrukturexperte • tarent
I can confirm the bug: can no longer decrypt a file encrypted with a
256-bit ECDH sub-key.
Downgrading libcrypt20 to 1.8.7-3 solves the problem.
Cheers,
--
Francesc
Package: libtorrent
Severity: important
Version: 0.13.8-2
Tags: patch
User:hahwang
Usertags: hurd
I decide to fix a broken package found at the recommended page
https://people.debian.org/~sthibault/out_of_date2.txt named `libtorrent`.
After I download the package source and try to
On Tue, 4 May 2021 23:47:30 +0100
Steve McIntyre wrote:
>
> Wow, OK. That *is* surprising! Oh well, thanks for the information
> anyway. It seems that *something* has caused your system to install
> shim-signed, but I've no clue what! :-)
>
I have been trying to recapture my memory and I
Dixi quod…
>Jessica Clarke brought out docs saying f8‥f15 must be saved, the
>other FPU registers not:
This needs to be fixed in klibc.
>>• klibc does not really support the FPU anyway
>
>… GCC chooses to allocate an FPU register for a pointer value.
This is a curiosity.
>>• the half of v10
Package: mssh
Version: 2.2-5+b1
Severity: normal
Hi.
The package used to contain the conffile:
/etc/bash_completion.d/mssh
but apparently no longer does so.
Could you please clean that up in a future version
with an appropriate dpkg-maintscript-helper rm_conffile… ?
Thanks in advance,
Package: trocla
Version: 0.2.3-1
Severity: normal
Tags: patch pending
Dear maintainer,
I've prepared an NMU for trocla (versioned as 0.3.0-0.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
I also uploaded it to experimental, given that we're in a
Package: xoscope
Version: 2.2-1+b1
Severity: important
Dear Maintainer,
It looks like ALSA support has been omitted in the RaspiOS port
of xoscope. The program runs but can't find the audio input device.
The audacity package finds the capture device via ALSA, so the
hardware is ok, along with
Hi Steve,
On Tue, 4 May 2021 20:26:33 +0100
Steve McIntyre wrote:
> I'll ask you the same question I asked Jörgen earlier - did you
> deliberately install shim-signed on a non-EFI system, or was it pulled
> in automatically somehow? I'm struggling to see a way to get here
> automatically.
>
I
On Wed, May 05, 2021 at 12:53:53AM +0200, Michael Rasmussen wrote:
>On Tue, 4 May 2021 23:47:30 +0100
>Steve McIntyre wrote:
>
>>
>> Wow, OK. That *is* surprising! Oh well, thanks for the information
>> anyway. It seems that *something* has caused your system to install
>> shim-signed, but I've
On Tue, May 04, 2021 at 10:00:05PM +0200, Michael Rasmussen wrote:
>Hi Steve,
>
>On Tue, 4 May 2021 20:26:33 +0100
>Steve McIntyre wrote:
>
>> I'll ask you the same question I asked Jörgen earlier - did you
>> deliberately install shim-signed on a non-EFI system, or was it pulled
>> in
Package: docker.io
Version: 18.09.1+dfsg1-7.1+deb10u3
Severity: important
When installing docker via `apt-get install -y --no-install-recommends
docker.io`
inside a VM where the host is under heavy load, dockerd segfaults occasionally,
but reproducibly.
dockerd[2131]: panic: runtime error:
Hi,
I wonder what the state of this issue is.
I looked at the code and somehow it has a few hints on (at least
partial?) Python 3 compatibility.
Russell, can you give me a short update on how far this got? Can we
somehow get to the goal of making this fully work with Python 3? Maybe
even for
* Salvatore Bonaccorso:
> CVE-2021-3504[0]:
> | Buffer overflow when provided invalid node key length
>
> Making the severity RC as I think the fix needs to go into bullseye.
Right.
I contacted team@security.d.o a about the issue, including a proposed
hivex/1.3.18-1+deb10u1 for stable-security
On 2021-05-04 08:56 +0200, Aurelien Jarno wrote:
> Package: dpkg-cross
> Version: 2.6.17
> Severity: serious
>
> dpkg-cross source contains at the following .deb files:
> - gcc-10-i686-linux-gnu-amd64-cross_10.2.1-6cross1_all.deb
> - gcc-10-i686-linux-gnu_10.2.1-6cross1_amd64.deb
>
> Those files
Package: trocla
Followup-For: Bug #974697
I prepared a NMU for experimental here:
https://salsa.debian.org/anarcat/trocla
Will see if I can upload this soon, ran out of time today.
-- System Information:
Debian Release: 11.0
APT prefers testing-security
APT policy: (500,
Hi,
On Tue, May 04, 2021 at 09:19:20PM +0200, Salvatore Bonaccorso wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: car...@debian.org
>
> Dear release team
>
> This is a pre-approval request to please
This bug should be fixed in Wireshark 3.2 and later as described at
https://gitlab.com/wireshark/wireshark/-/issues/15865.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: ed-deb...@s5h.net
Please unblock package rust-pleaser
[ Reason ]
Unblock is needed to migrate rust-pleaser 0.4.1 to testing. The SUSE
Security Team (primarily Matthias
Control: forward -1 https://github.com/duritong/trocla/issues/63
On 2021-05-04 15:54:02, Antoine Beaupré wrote:
> FWIW, I tried to fix this by updating to latest upstream (0.3.0) and I
> get the exact same test failure in unstable right now.
>
> I contacted upstream about the problem privately.
Hi,
Any update on this? This is actually very dangerous.
$ xdg-open hello.exe
Hello World!
$ cp hello.exe hello.ΡDF # <- actually not a P but a uppercase rho
$ xdg-open hello.PDF
Hello World!
Gabriel
Control: tags -1 confirmed moreinfo
On 2021-05-02 14:13:56 +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org, debian-b...@lists.debian.org
>
> I'd like
After the latest upgrade which failed you are not able to uninstall the
package either.
In my opinion this should race the severity to grave.
sudo dpkg -r --force-all shim-signed:amd64
(Reading database ... 613031 files and directories currently installed.)
Removing shim-signed:amd64
Source: bouncycastle
Severity: wishlist
X-Debbugs-Cc: jvalle...@mailbox.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear Maintainer,
bctls-jdk15on 1.65 jar is needed for jitsi-videobridge (ITP #757769)
[1]. I believe this should be built from the tls/ folder in
src:bouncycastle [2].
FWIW, I tried to fix this by updating to latest upstream (0.3.0) and I
get the exact same test failure in unstable right now.
I contacted upstream about the problem privately.
A.
--
"Faith" means not wanting to know what is true.
- Friedrich Nietzshe
Hi Michael,
On Tue, May 04, 2021 at 06:06:13PM +0200, Michael Rasmussen wrote:
>After the latest upgrade which failed you are not able to uninstall the
>package either.
>
>In my opinion this should race the severity to grave.
>
>sudo dpkg -r --force-all shim-signed:amd64
>(Reading database ...
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: car...@debian.org
Dear release team
This is a pre-approval request to please unblock package libxml2 (not
yet uploaded to unstable, but to experimental so far as
Another thing I should mention is that I accidentally (I swear) ended up
in memtest86 during some kernel switching tests, and figured I would let
that run. It found about a dozen errors in 10-20 minutes testing, so
there's also that: it could be a problem with the RAM.
That said, those are new
I can confirm this.
Regards,
Stephan
Control: tags -1 + moreinfo
Hi Olivier,
On Tue, May 04, 2021 at 10:01:17AM +0200, Olivier Monaco wrote:
> Package: src:linux
> Version: 5.10.19-1~bpo10+1
> Severity: important
>
> On a virtual machine running a NFS server the following kernel panic occurs:
> 2021-05-04T02:28:21.051193+02:00
Package: shim-signed
Version: 1.34+15.4-2
Followup-For: Bug #988056
X-Debbugs-Cc: n...@iname.com
Dear Maintainer,
same problem here: Dell laptop
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux
Package: redshift
Version: 1.12-4.1
Severity: important
Dear Maintainer,
* What led up to the situation?
The configuration file may be in .config/redshift/ instead of
.config/ and the apparmor profile usr.bin.redshift only allows reading
.config/redshift.conf
* What exactly did you do (or
The reason for the too-many-open-files appears to be that
sockets are leaked when client connections fail due to SSL
errors.
The particular SSL error in my case seemed to be due to the
server certificate having expired. Barrier seems to automagically
create SSL certs that are valid for one
El mar, 2 mar 2021 a las 0:28, Agustin Martin () escribió:
>
> I am attaching proposed patches for three additional changes on top of
> the previous debhelper ones. I do not know current build status for
> ia64 build, problematic CFLAFS should be added to
> DEB_CFLAGS_MAINT_STRIP inside the ifeq
Control: found -1 0.9.64.4-1
Hi Phil,
On Fri, Apr 16, 2021 at 01:03:16PM +0200, Phil Nightowl wrote:
> Launching skypeforlinux version 8.71.0.36 using supplied profile fails with
> the following error:
>
> Error: tmpfs outside $HOME is only available for root
> Error: proc 13576 cannot sync
Control: forwarded -1 https://github.com/netblue30/firejail/pull/4240
Hi Ralf,
On Sun, Mar 28, 2021 at 06:53:50PM +0200, Ralf Jung wrote:
> some time earlier this year, Chromium started to show an error message on
> each start that the "browserpass" extension could not be properly loaded.
> I
Package: barrier
Version: 2.1.2+dfsg-1~bpo9+1
Severity: normal
Dear Maintainer,
I have Barrier server version 2.1.2+dfsg-1~bpo9+1 on a Debian box
and Barrier client version 2.3.3 on a Mac (from Homebrew).
After restarting the Mac, Barrier failed to start. Its log says
repeatedly:
ERROR: ssl
Control: retitle -1 unblock: open-iscsi/2.1.3-4
Hello Paul,
On Fri, 2021-04-30 at 22:00 +0200, Paul Gevers wrote:
> Hi,
>
> On 30-04-2021 17:03, Ritesh Raj Sarraf wrote:
> > I will go ahead with the upload now and will untag this bug report
> > of
> > `moreinfo`.
>
> That's not what I meant.
Package: pianobooster
Version: 1.0.0-2
When pianobooster is in "Follow You" mode, it is checked only whether the
correct notes are played and the wrong ones are completely ignored.
In my opinion pianobooster (piano teacher) should teach the student, i.e.
he must make sure that the student
I'd like to report that another reason to support systemd-nspawn, which
really is an upgraded version of chroot, is that it Just Does The Right
Thing. For example, using autopkgtest-virt-chroot without further
preparation besides calling debootstrap causes my test to fail due to
not having /dev/
On Tue, 2021-05-04 at 16:51 +0200, Guido Günther wrote:
> Since upstream is pretty inactive i wonder if we should just drop it,
> it
> won't be in bullseye either and popcon is fairly low:
Hmm I always found it to be pretty nice... an are there any specific
bugs/features that would be needed to
Package: workrave
Version: 1.10.44-7.1
Severity: important
X-Debbugs-Cc: dmitry.zvorikin+deb...@gmail.com
I have a rest break and I always had it shown in the tray applet.
After last upgrade the applet only shows the cup icon and no timer.
I can go to Preferences -> Timers -> Micro-break ->
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian...@lists.debian.org
* Package name: dasel
Version : 1.14.1
Upstream Author : Tom Wright
* URL : https://github.com/TomWright/dasel
* License : MIT
Programming Lang: Golang
Description : Query,
Package: passwordsafe
Version: 1.12.0+dfsg-1
Severity: normal
X-Debbugs-Cc: amribrahim1...@hotmail.com
Dear Maintainer,
The app icon is missing from the dash, the top panel and the window switcher in
gnome-shell under Wayland.
I added this line to a local passwordsafe.desktop and it fixes the
retitle 978656 ITA: zenburn-emacs -- low contrast color theme for Emacs
thanks
Hi Sean,
I intend to adopt this package. I maintain a similar package,
clues-emacs, so I'm familiar with maintaining Emacs themes.
Thanks
--
Raúl Benencia
signature.asc
Description: PGP signature
Hi,
On Sat, May 01, 2021 at 03:07:50AM +0200, Christoph Anton Mitterer wrote:
> Hey.
>
> AFAICS, all python script have been adapted to Python3 upstream (or
> dropped)... so I guess this could be solved by upgrading to the current
> version.
Since upstream is pretty inactive i wonder if we
It doesn’t yet.
--
Ondřej Surý (He/Him)
> On 4. 5. 2021, at 16:48, Kilian Krause wrote:
>
> Package: bind9
> Version: 1:9.16.15-1
> Severity: normal
>
> Hi,
>
> as per
> https://gitlab.isc.org/isc-projects/bind9/-/wikis/DoH/DOH-and-DoT-Design
> the 9.16 BIND9 release has support for
Package: bind9
Version: 1:9.16.15-1
Severity: normal
Hi,
as per
https://gitlab.isc.org/isc-projects/bind9/-/wikis/DoH/DOH-and-DoT-Design
the 9.16 BIND9 release has support for DoT/DoH if built with nghttp2
support. This is not enabled in Debian and it would be great, if it
could be added.
TIA!
Hi Simon,
And thanks a lot for debugging/digging/sharing!
Simon McVittie (2021-05-03):
> On Mon, 03 May 2021 at 17:17:21 +0100, Simon McVittie wrote:
> > I've also been able to attach a debugger to debconf. My preliminary finding
> > is: we enter gtk_container_idle_sizer() in GTK 2 and never
Salvatore,
On Sun, May 2, 2021 at 8:59 AM Salvatore Bonaccorso wrote:
>
> Control: tags -1 + moreinfo
>
> Hi Mathieu,
>
> This bug thread was by the time very long but stoppend in 2016. Are
> the issues still relevant for us or should we close this bug by now?
Thanks for your triaging.
It
Hi Jörgen,
On Tue, May 04, 2021 at 02:45:57PM +0200, Jörgen Hägg wrote:
>Package: shim-signed
>Version: 1.34+15.4-2
>Severity: important
>
>
>Setting up shim-signed:amd64 (1.34+15.4-2) ...
>cat: /sys/firmware/efi/fw_platform_size: No such file or directory
>dpkg: error processing package
Control: tags -1 -moreinfo
Control: retitle -1 unblock: spip/3.2.11-2
Hi Ivo,
Le 13/04/2021 à 10:52, Ivo De Decker a écrit :
I'm leaning towards accepting it. I suggest you upload it to unstable, and
we'll leave it there for a while.
Uploaded three weeks ago.
If issues show up (either in
On Tue, 2021-05-04 at 14:02 +0200, Bill Allombert wrote:
> Yes, as I understand, the ioctl was disabled in the kernel at some
> point,
sadly :-(
>
> You can check by trying 'shift-page up / shift-page down'.
> If it does not scroll, then scrolling is disabled.
Nah, that already stopped working
Valentin Vidic (2021-05-03):
> Thanks, here is another one for s390x, should be relatively simple if
> you wish to link it here:
>
> linux: Debian installation fails in qemu-system-s390x due to missing
> virtio_blk module
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988005
Thanks, but I
On Tue, May 04, 2021 at 10:57:57AM +0200, Andreas Beckmann wrote:
> I've just NMUed the fix to DELAYED/3. Please let me know if I should
> delay it longer.
Definitely not from my side (as a non-Uploader for this package).
Thanks a lot for all your effort
Andreas.
--
Package: shim-signed
Version: 1.34+15.4-2
Severity: important
Setting up shim-signed:amd64 (1.34+15.4-2) ...
cat: /sys/firmware/efi/fw_platform_size: No such file or directory
dpkg: error processing package shim-signed:amd64 (--configure):
installed shim-signed:amd64 package post-installation
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xsane":
Package name: xsane
Version : 0.999-11
Upstream Author : Oliver Rauch
URL :
License : GPL-2+, public-domain, Artistic-1.0
Vcs
Package: shim-signed-common
Version: 1.34+15.4-2
Severity: normal
# apt autoremove --purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
mokutil* shim-signed-common*
0 upgraded, 0 newly installed, 2 to
Followup-For: Bug #952533
Control: tag -1 patch
Broken symlinks reported by adequate before applying the patch:
llvm: broken-symlink /usr/share/man/man1/bugpoint.1.gz -> bugpoint-11.1.gz
llvm: broken-symlink /usr/share/man/man1/dsymutil.1.gz -> dsymutil-11.1.gz
llvm: broken-symlink
On 30.1.2021 21.45, Helmut Grohne wrote:
Source: libglvnd
Version: 1.3.2-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
libglvnd participates in dependency loops relevant to architecture
bootstrap such as #979976. Instead of looking into such a difficult
problem, I looked into
Package: shim-signed
Version: 1.34+15.4-2
Severity: serious
Hi!
Just upgraded shim packages today and then shim-signed was unable to
configure:
,---
Setting up shim-signed:amd64 (1.34+15.4-2) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
On Tue, May 04, 2021 at 04:11:58AM +0200, Christoph Anton Mitterer wrote:
> Package: consolation
> Version: 0.0.8-1
> Severity: normal
>
> Hey there.
>
> First, awesome tool, work so much nicer than gpm...
> this should be made more well known :-)
Thanks Christoph!
> But 2nd, is scorlling
Package: urlview
Version: 0.9-21
Severity: normal
If you add a ~/.urlview config file containing
WRAP Yes
(with no terminating linefeed)
then running urlview gets you this error:
Unknown value for WRAP: Ye. Valid values are: YES, NO
It is just failing to read the last character, presumably
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-xstatic-angular
[ A bit of background about xstatic packages ]
XStatic packages are a way to embedd artifacts in a Python module. In
Debian, they are patched
On Tue, May 04, 2021 at 11:48:09AM +0100, peter green wrote:
> > This was automatically closed by ftpmaster because the package was
> > removed from unstable, but this still does not fix the FTBFS problem
> > in stable.
>
> Unfortunately I don't think a proper fix will be forthcoming, upstream
>
This is still a problem in fail2ban 0.10.2 in Debain 10.9 (buster).
On my system there's no imap or imap3 in /etc/services only imap2. Hence I
think the linked issues, and their fix is not really relevant here.
Hi Scott,
* John Scott [2021-05-03 00:35]:
Has anyone been able to reproduce this? Attempting to build Sage in a
fresh unstable environment succeeds for me; perhaps the build failure
was spurious.
I triggered reproducible builds yesterday:
Package: python-django
Version: 1:1.10.7-2+deb9u12
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for python-django.
CVE-2021-31542[0][1]:
Potential directory-traversal via uploaded files
If you fix the vulnerability
Package: dpkg-cross
Version: 2.6.17
Severity: important
When dpkg-cross converts a native package into a cross package, it moves
around libraries updating symlinks. It most notably moves the dynamic
loader, but doesn't update the path in the content of linker scripts
like
On 5/3/21 10:58 PM, Josh Triplett wrote:
> On Mon, May 03, 2021 at 12:56:58PM +0200, Matthias Klose wrote:
Is that still the case, a few years later?
>>>
>>> I'm running into this issue as well. I'd like to be able to
>>> cross-compile for aarch64, and I'd also like gcc -m32 to continue
>>>
Package: ifupdown2
Version: 3.0.0-1
Severity: normal
Dear Maintainer,
We have a system where we need to use allow-hotplug in
/etc/network/interfaces to automatically bring up a network interface
after the firmware has completed initialising. Unfortunately the
ifupdown2 package is missing the
This was automatically closed by ftpmaster because the package was
removed from unstable, but this still does not fix the FTBFS problem
in stable.
Unfortunately I don't think a proper fix will be forthcoming, upstream
has abandoned the crate in question.
Afaict the only purpose this package
Package: ifupdown2
Version: 3.0.0-1
Severity: normal
Dear Maintainer,
We have a system where we need to use allow-hotplug in /etc/network/interfaces
to automatically bring up a network interface after the firmware has completed
intialising. Unfortunately the ifupdown2 package is missing the
Control: severity -1 normal
I just uploaded version 2.3+dfsg-3. This version restricts the
postgresql related dependencies to postgresql-13, which makes the
package installable on Bullseye.
As discussed by Markus, this however does not solve the problem
completely; therefore only the
Control: reopen -1
Hi Sebastien,
On Fr 30 Apr 2021 17:37:38 CEST, Sebastien Bacher wrote:
Hey Mike,
Great, thanks, that's helpful, I will check that next week on Ubuntu!
Cheers,
Sebastien
The Debian builds failed for two architectures [1,2], and also with
the upstream DEBs I see test
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: msdem...@ari.uni-heidelberg.de
Severity: normal
Please unblock package gavodachs
[ Reason ]
The version 2.3+dfsg-3 lowers the severity of #984555 so that it is not
longer release critical.
tags 988025 +patch
thanks
I was able to bisect to find the upstream commit that fixed this. A debdiff is
attached.
If someone wants to negotiate with the release team about getting it uploaded
feel free,
I probablly won't bother to do so myself.
diff -Nru rust-rustyline-3.0.0/debian/changelog
Hi Zoli,
On Tue, May 04, 2021 at 11:29:22AM +0200, Zoli wrote:
>Package: shim-signed
>Version: 1.34+15.4-2
>Severity: normal
>X-Debbugs-Cc: z...@dzsiudzs.icu
>
>Dear Maintainer,
>
>aptitude upgrade tried to uninstall shim-signed-common and upgrade shim-signed.
>
>This results in the postinst
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package broadcom-sta
[ the reason for the unblock ]
It fixes a serious bug #987159
that txpower cannot get/set correctly, with some other fixes.
The patches are in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This happened only recently, last updates were installed on Apr 27:
> root@bulls-eye:~# ls -alt /var/lib/dpkg/info | grep "Apr 27"
> drwxr-xr-x 1 root root 276 Apr 27 18:00 ..
> drwxr-xr-x 1 root root 497630 Apr 27 17:58 .
> -rw-r--r-- 1 root
Followup-For: Bug #986812
Control: tag -1 pending
Hi,
I've just uploaded my fix to DELAYED/3, please let me know if I should
delay it longer.
Andreas
Package: shim-signed
Version: 1.34+15.4-2
Severity: normal
X-Debbugs-Cc: z...@dzsiudzs.icu
Dear Maintainer,
aptitude upgrade tried to uninstall shim-signed-common and upgrade shim-signed.
This results in the postinst script failing:
Setting up shim-signed:amd64 (1.34+15.4-2) ...
Installing for
Hi Andreas,
On Mon, May 03, 2021 at 07:19:52PM +0200, Andreas Beckmann wrote:
> Followup-For: Bug #984555
> I think I have an idea what is happening: The upgrade from buster to
> bullseye does not install postgresql-13-pgsphere and postgresql-13-q3c
> but keeps postgresql-pgsphere and
Control: forwarded -1 https://github.com/MariaDB/server/pull/1556
Hi Matthew!
Thanks for your detailed report.
Indeed, the generated log rotate seems wrong (and I am able to reproduce
the problem with 10.5 on sid).
Could you maybe help on this directly upstream
On Wed, Jan 30, 2019 at 02:58:44PM +, Clint Adams wrote:
> On Wed, Jan 30, 2019 at 09:51:42AM -0500, Dan Martins wrote:
> > On systems where the nofile limit is large, fakeroot hangs
> > For example on an Arch Linux system, where DefaultLimitNOFILE=infinity
> > in /etc/systemd/system.conf:
>
Followup-For: Bug #986813
Control: tag -1 pending
Hi,
I've just NMUed my fix to DELAYED/3, please let me know if I should
delay it longer.
Andreas
Package: bind9
Severity: normal
Hi,
While doing a bind9 update for stretch LTS, Anton Gladky added a salsa
pipeline which had a blhc (build log hardening check) test that was
failing.
I have investigated it and found that bind9 is not using automake and while
it tries to honor most *FLAGS
1 - 100 of 111 matches
Mail list logo
