Bug#928822: raqm: clean after build deletes docs/html/* which is not regenerated
On Sun, May 12, 2019 at 02:25:41PM +0200, Andreas Beckmann wrote: > On 2019-05-12 04:38, أحمد المحمودي wrote: > > I checked the diff between upstream sources 0.5.0 (the one in testing) & > > 0.6.0, and I don't see any significant difference in Makefiles or docs/ > > to cause this. It might something in experimental's toolchain ? > > This is probably reproducible in sid as well, I just run this test on > experimental only. ---end quoted text--- I just tried to double-build version 0.5.0 on unstable, and it also failed, yet, if I understand correctly, it used to double-build before. Hence, this must be due to some change in the toolchain. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Bug#925134: grub-efi-amd64-signed: doesn't mount cryptodisk
Hi Mark and all, I'm in the same situation. So what do we do ? Thx On Thu, 4 Jul 2019 18:34:01 +0200 Mark Caglienzi wrote: > Hi all, > is this bug relevant yet? > > I have a buster laptop (so no VM, but real hardware, and no fresh > install) with encrypted disk, and I blocked the upgrade of grub since > March because of the fear to not be able to boot it after the upgrade of > grub. > > I am still with 2.02+dfsg1-12 because of this. > > The severity is critical (and if the bug is confirmed, I understand > that's *critical*), but I don't understand if I can upgrade or not. > > I don't see "movement" in the thread since some months, and the bug just > "lies here". > > Thanks in advance, > Mark > -- Félix Defrance PGP: 0x46A603D10F04DC57 signature.asc Description: OpenPGP digital signature
Bug#931507: kernel-wedge: HDA sound board detection takes 60s in d-i
Package: kernel-wedge Version: 2.99 Severity: serious Tags: a11y Justification: prevents blind people from using d-i We have had (late, unfortunately) reports that HDA-based audio hardware does not get detected. Actually it does, but only after 60s of delay, which is way too long for the espeakup script. What happens is in snd_hdac_i915_init, which tries to load the i915 module, which is not included in d-i, and waits for 60s to get it loaded and bound to it. The delay was "only" 10s in 4.19.12, but apparently increased to 60s in 4.19.37. So I guess we should just ship the i915 module in d-i, either manually in the existing sound-modules*-di package, or in a separate package and make sound-modules*-di depend on it. It's a big 3M module, but it would be shipped only in the gtk images anyway. It'd definitely be so much useful to have this change uploaded in time for 10.1. Samuel -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.1.0 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages kernel-wedge depends on: ii debhelper 12.1.1 ii make 4.2.1-1.2 kernel-wedge recommends no packages. kernel-wedge suggests no packages. -- Samuel * c is away : cuisine; bouffe oh, moi je fais plutôt cuisine & bouffe en fait :) oui c'est vrai, certains font cuisine && bouffe (juste au cas où... ;-)) ( cuisine && bouffe ) || restau voire ((cuisine && bouffe) || restau) & apéritif -+- #ens-mim -+-
Bug#931491: iputils: FTBFS in sid (missing dependency on setcap)
There's a bug in upstream's build system that causes the build to fail if setcap is unavailable, even if its usage is disabled via the NO_SETCAP_OR_SUID configuration. I'll work with upstream to get this fixed.
Bug#931491: iputils: FTBFS in sid (missing dependency on setcap)
On Sat, Jul 06, 2019 at 01:31:08PM +0200, Gianfranco Costamagna wrote: > > Hello, looks like the new version does search for *bin/setcap tool, and fails > to build if missing. > Hm. Seems libcap2-bin is present in my pbuilder environment as a result of being a dependency of packages like iproute2. I think the better thing to do would be to disable execution of the build-aux/setcap-setuid.sh script at build time, since we don't need the capabilities assigned during the build. Thanks for this report...
Bug#926193: still not working with the actual kernel in buster
Hi folks,
as I read on bits.debian.org that buster will be released
today I think it's time to tell you that this bug is still
NOT gone with the actual kernel in buster
(linux-image 4.19.37-5).
If buster is released with this kernel it will still not
work on my laptop (Acer Travelmate B117), which is sad
because I actually don't want to use the outdated
linux-image-4.19.0-2 forever.
The bug had got the tag 'fixed upstream' which might be
true, but it's still NOT fixed in the Debian-package in
buster. Why is it so hard to apply a revert-drm-i915 patch
to the kernel as other distributions did. As attachment you
find the patch that the fedora-folks applied to their
kernel in march 19.
Klaumi
---
Klaus-Michael Klingsporn
phone: +49-30-9445363
mail: klaumi...@gmx.de
web: www.klaumikli.de
From e90ac616e4b1d49ec9092086b0e10108df12157d Mon Sep 17 00:00:00 2001
From: Fedora Kernel Team
Date: Tue, 5 Mar 2019 12:56:35 -0600
Subject: [PATCH] Revert drm/i915/fbdev: Actually configure untiled displays
---
drivers/gpu/drm/i915/intel_fbdev.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_fbdev.c b/drivers/gpu/drm/i915/intel_fbdev.c
index e0c02a9..9e2e998 100644
--- a/drivers/gpu/drm/i915/intel_fbdev.c
+++ b/drivers/gpu/drm/i915/intel_fbdev.c
@@ -336,8 +336,8 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
bool *enabled, int width, int height)
{
struct drm_i915_private *dev_priv = to_i915(fb_helper->dev);
+ unsigned long conn_configured, conn_seq, mask;
unsigned int count = min(fb_helper->connector_count, BITS_PER_LONG);
- unsigned long conn_configured, conn_seq;
int i, j;
bool *save_enabled;
bool fallback = true, ret = true;
@@ -355,9 +355,10 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
drm_modeset_backoff();
memcpy(save_enabled, enabled, count);
- conn_seq = GENMASK(count - 1, 0);
+ mask = GENMASK(count - 1, 0);
conn_configured = 0;
retry:
+ conn_seq = conn_configured;
for (i = 0; i < count; i++) {
struct drm_fb_helper_connector *fb_conn;
struct drm_connector *connector;
@@ -370,8 +371,7 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
if (conn_configured & BIT(i))
continue;
- /* First pass, only consider tiled connectors */
- if (conn_seq == GENMASK(count - 1, 0) && !connector->has_tile)
+ if (conn_seq == 0 && !connector->has_tile)
continue;
if (connector->status == connector_status_connected)
@@ -475,10 +475,8 @@ static bool intel_fb_initial_config(struct drm_fb_helper *fb_helper,
conn_configured |= BIT(i);
}
- if (conn_configured != conn_seq) { /* repeat until no more are found */
- conn_seq = conn_configured;
+ if ((conn_configured & mask) != mask && conn_configured != conn_seq)
goto retry;
- }
/*
* If the BIOS didn't enable everything it could, fall back to have the
--
2.20.1
Processed: tagging 931490
Processing commands for cont...@bugs.debian.org: > tags 931490 - ipv6 Bug #931490 [revelation] should not be removed from Buster (important for visually impaired users)) Removed tag(s) ipv6. > thanks Stopping processing here. Please contact me if you need assistance. -- 931490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931490 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#931492: verilator: please honour CFLAGS and CXXFLAGS to build
Source: verilator
Version: 4.016-2
Severity: serious
Tags: patch experimental
Hello, looks like the new dwz from experimental makes verilator FTBFS, see:
https://bugs.launchpad.net/ubuntu/+source/dwz/+bug/1835398
reason is: debug flags are not injected to every package that is built, and the
new dwz in experimental
fails to compress them.
the attached patch fixes the build failure (that is showing only in
experimental, for now)
thanks for accepting, I sent it by email also upstream some minutes ago.
G.
Description: Honour system flags, this makes debug flags being injected correctly
Author: Gianfranco Costamagna
Last-Update: 2019-07-06
--- verilator-4.016.orig/configure.ac
+++ verilator-4.016/configure.ac
@@ -91,10 +91,10 @@ AC_SUBST(CFG_WITH_PREC11)
AC_MSG_RESULT($CFG_WITH_PREC11)
# Compiler flags
-CFLAGS=-I${includedir}
-CPPFLAGS=-I${includedir}
-CXXFLAGS=-I${includedir}
-LDFLAGS=-L${libdir}
+CFLAGS+=" -I${includedir}"
+CPPFLAGS+=" -I${includedir}"
+CXXFLAGS+=" -I${includedir}"
+LDFLAGS+=" -L${libdir}"
# Checks for programs.
AC_PROG_CC
--- verilator-4.016.orig/src/Makefile_obj.in
+++ verilator-4.016/src/Makefile_obj.in
@@ -60,6 +60,8 @@ pkgdatadir = @pkgdatadir@
CFG_WITH_CCWARN = @CFG_WITH_CCWARN@
CFG_WITH_DEFENV = @CFG_WITH_DEFENV@
CPPFLAGS += @CPPFLAGS@
+CFLAGS += @CFLAGS@
+CXXFLAGS += @CXXFLAGS@
LDFLAGS += @LDFLAGS@
EXEEXT = @EXEEXT@
CFG_CXXFLAGS_SRC = @CFG_CXXFLAGS_SRC@
@@ -135,7 +137,7 @@ VLCOVGEN = $(srcdir)/vlcovgen
all: make_info $(TGT)
make_info:
- @echo " Compile flags: " $(CXX) ${CPPFLAGS}
+ @echo " Compile flags: " $(CXX) ${CFLAGS} ${CXXFLAGS} ${CPPFLAGS}
clean mostlyclean distclean maintainer-clean::
-rm -f *.o *.d perlxsi.c *_gen_*
@@ -280,21 +282,21 @@ V3Number_test: V3Number_test.o
$(PERL) $(ASTGEN) -I$(srcdir) $*.cpp
%.o: %.cpp
- $(OBJCACHE) ${CXX} ${CPPFLAGSWALL} -c $<
+ $(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSWALL} -c $<
%.o: %.c
- $(OBJCACHE) ${CC} ${CPPFLAGSWALL} -c $<
+ $(OBJCACHE) ${CC} ${CFLAGS} ${CPPFLAGSWALL} -c $<
V3ParseLex.o: V3ParseLex.cpp V3Lexer.yy.cpp V3ParseBison.c
- $(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+ $(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
V3ParseGrammar.o: V3ParseGrammar.cpp V3ParseBison.c
- $(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+ $(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
V3ParseImp.o: V3ParseImp.cpp V3ParseBison.c
- $(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+ $(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
V3PreProc.o: V3PreProc.cpp V3PreLex.yy.cpp
- $(OBJCACHE) ${CXX} ${CPPFLAGSPARSER} -c $<
+ $(OBJCACHE) ${CXX} ${CXXFLAGS} ${CPPFLAGSPARSER} -c $<
Generated files
Bug#931491: iputils: FTBFS in sid (missing dependency on setcap)
Source: iputils Version: 3:20190515-1 Severity: serious Tags: patch Hello, looks like the new version does search for *bin/setcap tool, and fails to build if missing. Please add it to build dependencies if possible --- iputils-20190515/debian/control 2019-07-06 00:49:21.0 +0200 +++ iputils-20190515/debian/control 2019-07-06 13:27:11.0 +0200 @@ -4,7 +4,7 @@ Maintainer: Noah Meyerhans Standards-Version: 4.3.0 Build-Depends: debhelper (>= 10), xsltproc, docbook-xsl, - docbook-xsl-ns, libcap-dev, + docbook-xsl-ns, libcap-dev, libcap2-bin, libgcrypt-dev, libidn11-dev, bash (>= 3), meson Vcs-Git: https://salsa.debian.org/debian/iputils.git Vcs-Browser: https://salsa.debian.org/debian/iputils thanks G.
Processed: Re: Bug#930869: Asked to try and mediate this bug.
Processing control commands: > severity -1 wishlist Bug #930869 [pm-utils] Don't release with buster Severity set to 'wishlist' from 'serious' > tags -1 +moreinfo Bug #930869 [pm-utils] Don't release with buster Added tag(s) moreinfo. -- 930869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#930869: Asked to try and mediate this bug.
Control: severity -1 wishlist
Control: tags -1 +moreinfo
On Sun, Jun 30, 2019 at 11:26:01AM -0400, Sam Hartman wrote:
> Unfortunately, to do that, I'm going to need to ask at least one
> question that Adam is already asked.
[...]
Michael: if you have trouble naming either any particular problem, or a
viable replacement for this package, I assume there are none. If that's
incorrect, please provide more info before bumping the severity again.
The only remaining actionable part of this bug are the hacks ("quirks")
for buggy machines. Having researched the package a bit more, I see that
they talk to real-mode display BIOS -- such machines generally stopped
being manufactured roughly at the time pm-utils became unmaintained
upstream, thus I wonder whether that particular part of the code can be
said to "do more more harm then good". I'd wary before pulling the quirks
from under potentially working hardware.
But, I have no way to check that: none of 5 laptops I have even _has_ a
real-mode BIOS (three because of being non-x86, two because of level 3
UEFI without CSM). And for my non-laptops, which range from a 2004 box to
this year's stuff, pm-utils work perfectly without quirks.
So there are two questions:
* are pm-utils useful on non-quirk hardware?
• my answer is a strong "yes"
* should code for legacy hardware be kept if it can't be tested?
• this part I can't answer
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ According to recent spams, "all my email accounts are owned
⢿⡄⠘⠷⠚⠋ by a hacker". So what's the problem?
⠈⠳⣄
Bug#931490: should not be removed from Buster (important for visually impaired users))
Package: revelation Version: 0.4.14-3 Severity: grave Tags: ipv6 Hello I am sorry that I report this so close to Buster release but I just noticeed that in the Debian Buster release notes it is said that Revelation is removed from the Buster. Release notes suggests that passwords can be exported from Revelation and then imported to keepass2 password manager. Unfortunately that is not an option if you are blind or other visually impaired user like I am. Keepass2 password manager is not accessible with the Orca screen reader. So it is not accessible if you are visually impaired. I am still using Debian Stretch, but this problem most likeyly applies to Buster too. I have tried every graphical password manager I can find in Debian Stretch and Revelation isthe only graphical password managerwhich is accessible with the Orca screen reader. None of the other graphical password managers are accessible with the Orca screen reader. So Revelation is really the only accessible graphical password manager for the visually impaired users. So now if Revelation password manager is is not in Buster then suddenly visually impaired users have no way to store their passwords and no way to access passwords already stored in Revelation. This is not ok, it is not ok to remove Revelation from Debian when there is no other accessible password manger and no way to use keepass2 because it is not accessible with Orca screen reader. Please include Revelation in Buster. -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages revelation depends on: ii gconf2 3.2.6-4+b1 ii gnome-extra-icons 1.1-3 ii gnome-icon-theme 3.12.0-2 ii python 2.7.13-2 ii python-cracklib2.9.2-5 ii python-crypto 2.6.1-7 ii python-dbus1.2.4-1+b1 ii python-gnome2 2.28.1+dfsg-1.2 ii python-gobject 3.22.0-2 ii python-gtk22.24.0-5.1 ii shared-mime-info 1.8-1+deb9u1 revelation recommends no packages. revelation suggests no packages. -- no debconf information
