On Wed, Jan 17, 2024 at 04:29:10PM +0100, Emanuele Rocca wrote:
> Source: kbtin
> Severity: serious
> Usertags: 32bit-stackclash
> kbtin currently fails to build from source on armhf. The failure is due
> to an incompatibility between valgrind and stack-clash-protection on
> 32bit arm reported
On Mon, Aug 21, 2023 at 10:38:52AM +0200, Emanuele Rocca wrote:
> Hi Adam,
Hi Em!
> On 2023-08-16 05:14, Adam Borowski wrote:
> > This is not a regression, thus why would it be a bug?
>
> Well FTBFS is a bug isn't it? :-)
A FTBFS on an architecture that has built before (an
On Fri, Aug 11, 2023 at 02:02:36PM +0300, Adrian Bunk wrote:
> I've prepared an NMU for pmdk (versioned as 1.13.1-1.1) and uploaded
> it to DELAYED/2. Please feel free to tell me if I should cancel it.
> +pmdk (1.13.1-1.1) unstable; urgency=low
> +
> + * Non-maintainer upload.
> + * Ignore
Package: debootstrap
Version: 1.0.128+nmu3
Severity: grave
bluca's NMU on 2023-07-15 makes debootstrap produce chroots using the
aliased-dirs scheme. While it's currently the default scheme for non-buildd
systems, it is both not supported by dpkg (with no solution in sight), but
is also likely
Source: python-clickhouse-driver
Version: 0.2.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
With any build type that includes the source, your package fails with:
dpkg-source: info: local changes detected, the modified files
Source: macs
Version: 2.2.7.1-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build, with:
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or
semicolon (after name and no
Source: binutils-mipsen
Version: 10+c3
Severity: grave
Justification: renders package unusable
mips* binutils tools crash on startup:
$ mips64el-linux-gnuabi64-as
mips64el-linux-gnuabi64-as: error while loading shared libraries:
libsframe.so.0: cannot open shared object file: No such file or
Package: wireplumber
Version: 0.4.14-3
Severity: grave
Hi!
In version 0.4.14-3, you added a hard dependency on a specific session
model of dbus, rather than the virtual package defined by the Policy
(dbus-session-bus). This makes it non-installable on any box where a
dependency of that package
Control: severity -1 normal
(I intended to avoid having to argue by implementing specific objective
tests that valgrind has to meet to be declared available, but I did not
manage to get that done. Thus, arguing...)
On Sat, Oct 22, 2022 at 12:12:40PM +0300, Adrian Bunk wrote:
> Package:
Source: arm-compute-library
Version: 20.08+dfsg-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build, with:
In file included from src/core/ITensorPack.cpp:24:
Source: fenix-plugins
Version: 0.0.20070803-8
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build; I see a lot of autoconf warnings,
then they get fatal:
Makefile.am: installing './depcomp'
Control: close 1027364
On Sat, Jan 28, 2023 at 04:31:25PM +0100, Santiago Vila wrote:
> retitle 1027364 golang-github-go-co-op-gocron: FTBFS (missing build-depends
> on tzdata)
> reopen 1027364
> found 0.5.0-2
> thanks
>
> Adam, please don't close bugs just because they say "bullseye" in the
Control: tags -1 +unreproducible
Control: severity -1 wishlist
Hi!
You've done a MBF despite _negative_ consensus in several discussions
(debian-devel, debootstrap, policy, ...); folks seem to be in agreement
that either the Policy doesn't require building in an environment that
is explicitly
Control: tag -1 -patch
Hi!
The alleged patch doesn't fix the FTBFS. Besides the non-bug (per numerous
discussions on debian-devel and elsewhere) of non-depending on a required
package "tzdata", the package fails from an actual build failure even in
a non-sabotaged build chroot.
I'm thus
Hi!
Would you be willing to reconsider for Bookworm?
While you do have reservations about xfce4-screensaver, the question is
not whether it's perfect, but how it fares against alternatives. And
lightm-locker is so buggy it's outright useless for a good deal of users
while reports for
On Mon, Jan 16, 2023 at 08:26:37AM +0200, Konstantinos Margaritis wrote:
> On 15/1/23 03:33, Adam Borowski wrote:
> > Hi!
> > As you're apparently too busy to either fix ppc or suggest a different plan,
> > I'd make a NMU dropping ppc64el for now so the package can be relea
Hi!
As you're apparently too busy to either fix ppc or suggest a different plan,
I'd make a NMU dropping ppc64el for now so the package can be released with
Bookworm.
Please say if I shouldn't.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Let's make a Debian conference in Yalta, Ukraine.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄
Hi!
As the window for new packages to [re-]enter bookworm will close soon,
and fixing vectorscan on ppc doesn't appear to be coming, what about
disabling that arch for now?
It is described as "in development", thus it's not surprising it's
not working yet. It'd be shame for the package to miss
Control: severity -1 wishlist
Control: tags -1 +wontfix
On Sun, Jan 01, 2023 at 11:49:26PM +0100, Santiago Vila wrote:
> [ Thanks for fixing the bug in unstable so fast ]
... too fast, in fact. Per the discussion on debian-policy, it's not a bug,
and this way I have a redundant dependency which
On Sun, Jan 01, 2023 at 01:53:31PM +0100, Santiago Vila wrote:
> Adam Borowski escribió:
> > nor any of people running archive rebuilds so far.
>
> FWIW: I am one of those people running archive rebuilds.
> I rebuilt the entire bullseye distribution, and I'm trying
> to m
Control: tags -1 +unreproducible moreinfo
On Fri, Dec 30, 2022 at 07:04:09PM +0100, Santiago Vila wrote:
> Package: src:safeclib
> Version: 3.5-3
> Severity: serious
> Tags: ftbfs patch
> During a rebuild of all packages in bullseye, your package failed to build:
> FAIL: t_gmtime_s
> FAIL:
Control: tags -1 +fixed-upstream
I see this is fixed upstream, thus you can unrevert to the current version.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Your snowflakes have nothing on my socks drawer.
⢿⡄⠘⠷⠚⠋⠀
⠈⠳⣄
Control: severity -1 normal
Control: tags -1 +moreinfo
On Tue, Oct 04, 2022 at 05:57:12PM +, Williams, Dan J wrote:
> On Mon, 26 Sep 2022 08:26:56 + Winnie Yue wrote:
> > Package: ndctl
> > Version: 71.1-1
> > Severity: serious
> > For Debian 11.5 32 bit, I got below info:
> > But I
Source: tideways
Version: 5.0.4-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build:
Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package
Source: php-facedetect
Version: 1.1.0-19-g135c72a-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build:
Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info:
Source: devscripts
Version: 2.22.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build:
python3 setup.py clean -a
/<>/scripts/setup.py:5: DeprecationWarning: The distutils package
is deprecated
Package: elpa-evil
Version: 1.14.0-1
Severity: grave
Justification: non-installable
Hi!
I'm afraid your package fails to install:
Setting up elpa-evil (1.14.0-1) ...
tsort: -: input contains a loop:
tsort: emacsen-common
tsort: elpa-goto-chg
tsort: -: input contains a loop:
tsort: elpa-undo-tree
On Mon, Sep 19, 2022 at 12:56:16AM +0200, Thorsten Glaser wrote:
> On Mon, 19 Sep 2022, Andreas Beckmann wrote:
>
> > usr/share/man/es/man8/runlevel.8.gz
>
> How can that be? They are diverted from preinst, positively this one.
I can't reproduce either; sample run:
On Tue, Sep 13, 2022 at 01:52:46PM +0200, Jean Baptiste Favre wrote:
> Hello Adam,
> Thanks for your report.
> I've unable to reproduce the build failure as of now, using both a docker
> image and sbuild on my laptop (amd64 only).
>
> The failing test simply tries to open /etc/hosts (which should
On Fri, Sep 02, 2022 at 01:50:28PM +0200, Daniel Baumann wrote:
> tag 1018043 pending
> thanks
♥
> On 8/24/22 17:40, Adam Borowski wrote:
> > This package has a massive size
>
> massive is relative.. it's 490KB.
4591 kB here...
> there was a reason (see #608484), but
Package: zutils
Version: 1.11-5, 1.12~pre2-1
Severity: serious
Justification: Policy 10.1
Hi!
This package has a massive size, as it's pointlessly statically built.
Not only this violates a "must" requirement of the Policy, it also does
so for no benefit at all: in the case libraries it's linked
Control: block -1 by 1018035
It'd be much better to fix the suppressions in src:valgrind rather than in
dependers.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋⠀ You're alive. But that's just a phase.
⠈⠳⣄
Control: reopen -1
On Tue, Aug 16, 2022 at 05:09:03PM +, Debian Bug Tracking System wrote:
> Your message dated Tue, 16 Aug 2022 19:06:12 +0200
> with message-id <429a5094-bef5-3b75-bfce-684319dfa...@debian.org>
> and subject line Re: Bug#1017441: debhelper: building src:shadow wrongly
>
On Tue, Aug 16, 2022 at 03:13:35PM +0100, Luca Boccassi wrote:
> On Tue, 16 Aug 2022 13:13:53 +0200 Johannes Schauer Marin Rodrigues
> > The package passwd=1:4.11.1+dfsg1-2 in the archive does not have the
> > dependency on "systemd | systemd-tmpfiles" and was compiled with
> > debhelper 13.6.
> >
Beside forcing a switch to systemd (or systemd-tmpfiles if the admin knows
about this option, which is not given in any messages), this wrong
dependency also makes Required packages non-installable on:
* hurd
* kfreebsd
* musl ports (prepared by helmut as a part of rebootstrap, and by others)
On Thu, Aug 11, 2022 at 02:00:59AM +0200, Cyril Brulebois wrote:
> The set of packages you uploaded contains uninstallable udebs, as they
> depend on sgml-base, which doesn't exist in the installer context
> (there's no udeb for it.
> This is not your fault, that's debhelper's #1015263:
Yeah but
Control: reassign -1 udev
Control: retitle -1 udev: Please drop systemd from Depends
> Control: reassign -1 sysvinit-core
> Control: retitle -1 sysvinit-core: please depend on
> systemd-standalone-sysusers, systemd-standalone-tmpfiles
>
> On Fri, 2022-07-22 at 21:19 +0200, Adam
On Mon, Jun 27, 2022 at 10:41:58AM +0200, Ansgar wrote:
> Source: mlucas
> Version: 20.1.1-1
> Severity: serious
> The maintainer address for src:mlucas is obviously invalid:
>
> Maintainer: Alex Vong
Well, besides the doofus sponsor who *somehow* managed to not notice this
change, let's
Source: tmpreaper
Version: 1.6.16
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build, with:
dh_testdir
./tmpreaper -h 2>&1 | grep 'tmpreaper -- Version: '1.6.16-DEB || (echo "You
forgot to fix
Source: mac-fdisk
Version: 0.1-18
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi!
I'm afraid that mac-fdisk fails to build with the toolchain in current
unstable. It doesn't include public headers, which results in a lot
of warnings like:
pdisk.c:156:5: warning:
Source: atitvout
Version: 0.4-13.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
dh_clean: error: Compatibility levels before 7 are no longer supported (level 6
requested)
That's pretty self-explaining...
Source: iotjs
Version: 1.0+715-1
Severity: serious
Justification: In the opinion of a QA person the package is unsuitable for
release.
Hi!
This package appears to be unmaintained, and:
* has a large set of CVEs reported. They are also untriaged and have seen
no maintainer response.
* blocks
Package: usrmerge
Version: 25
Severity: grave
Justification: causes non-serious data loss
Due to a lacking *rm script that would recover the system back to a
supported scheme, the system remains tainted by aliased-dirs even if the
usrmerge package is uninstalled.
Such a scheme is explicitly
Control: severity -1 critical
The current severity, "grave", is a serious understatement.
As all buildd chroots that are created with buggy debootstrap are tainted,
any packages built recently may assume merged usr, and thus needs to be
rebuilt.
Do we have a patch? If not, let's revert, today
Source: omega-rpg
Version: 1:0.90-pa9-16
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid that your package fails to build with:
scr.c: In function ‘print1’:
scr.c:351:5: error: format not a string literal and no format
Source: bsdgames
Version: 2.17-28
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid that your package fails to build:
canfield/canfield/canfield.c: In function ‘instruct’:
canfield/canfield/canfield.c:1650:3: error: format
Source: ytree
Version: 1.99pl1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid that your package fails to build with:
input.c: In function ‘InputChoise’:
input.c:352:3: error: format not a string literal and no format
Control: clone -1 -2
Control: retitle -2 RM: mozplugger -- RoQA; useless; dead upstream
Control: reassign -2 ftp.debian.org
In Sep 2018, Adrian Bunk wrote:
> As far as I can see, not a single one of the 15 (sic) browser packages
> in the dependencies does both still exist in unstable and still
Control: retitle -1 please backport to bullseye
Control: severity -1 wishlist
Hi!
A package not making it to the stable release is by no means a RC bug,
merely a statement of the package's quality at a time in the past.
I'm adjusting severity accordingly.
On the other hand, this case (and
Package: libpmem1
Version: 1.10-1
Severity: grave
Justification: causes data loss
[a fix is coming, filing this bug so the Release Team knows why]
Hi!
Support for arm64 in PMDK is deeply experimental. As far as I know, it has
never been tested on real hardware nor had been reviewed by someone
-1.12/debian/changelog 2021-06-23 14:55:39.0 +0200
@@ -1,3 +1,11 @@
+redshift (1.12-4.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop broken systemd-based startup, without a replacement for now.
+Closes: #892275
+
+ -- Adam Borowski Wed, 23 Jun 2021 14:55:39 +0200
Ping -- the package was scheduled to be autoremoved today.
> > > > IMVHO, you should remove the redshift systemd file and let redshift
> > > > start via de xdg autostart mechanism. The geoclue agent should then be
> > > > started before redshift as I think it start the process using the
> > >
> * Paul Gevers [210526 21:49]:
> > On Thu, 4 Feb 2021 14:29:55 +0100 Laurent Bigonville
> > wrote:
> > > IMVHO, you should remove the redshift systemd file and let redshift
> > > start via de xdg autostart mechanism. The geoclue agent should then be
> > > started before redshift as I think it
Package: sa-exim
Version: 4.2.1-19
Severity: grave
Justification: renders package uninstallable
Hi!
Current version of sa-exim depends on exim4-localscanapi-3.1, and indeed it
was compiled against that version. This makes it non-coinstallable with
fully-featured (-heavy) build with exim; it is
Hi!
Since your last report of a crash, there's been six new releases:
five in the 0.1.* version series, and now one 4.16.0-1. As the
new version claims a stable release, is there still a reason to
keep xfce4-screensaver out of Bullseye?
I've been using it happily all the time, with no borkage to
Control: tags -1 + moreinfo unreproducible
Hi Lucas!
> On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote:
> > Source: memkind
> > During a rebuild of all packages in sid, your package failed to build
> > on ppc64el. At the same time, it did not fail on amd64.
>
> > I'm marking
On Wed, Dec 09, 2020 at 01:27:11PM +0100, Adam Borowski wrote:
> On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote:
> > Source: memkind
> > Version: 1.10.1-1
>
> > During a rebuild of all packages in sid, your package failed to build
> > on ppc64el. At
On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote:
> Source: memkind
> Version: 1.10.1-1
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on amd64.
>
> I'm marking this bug as severity:serious since your package
Package: manpages
Version: 5.09-1
Severity: grave
Justification: renders package unupgradeable
Hi!
I'm afraid that the package fails to upgrade:
Unpacking manpages (5.09-1) over (5.08-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-Vi3YLk/00-manpages_5.09-1_all.deb (--unpack):
Package: unison-2.48
Version: 2.48.4-5+b1
Severity: serious
Justification: fails to upgrade
Hi!
I'm afraid there's no Replaces: stanza, resulting in:
Unpacking unison-2.48 (2.48.4-5+b1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-Q6eH0z/4-unison-2.48_2.48.4-5+b1_amd64
.deb
Control: block -1 by 964457
On Mon, Aug 03, 2020 at 01:19:42PM +0200, Lucas Nussbaum wrote:
> Source: vmem
> Version: 1.8-1
> Severity: serious
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> > vmem_aligned_alloc@@LIBVMEM_1.0
> > vmem_calloc@@LIBVMEM_1.0
Package: gimp-python
Version: 2.10.8-2+b1
Severity: grave
Justification: renders package unusable
Hi!
As the package "python" is no more, gimp-python can no longer be installed.
It needs to either depend on "python2" (in the short term) or, preferably,
be updated for py3.
Meow!
-- System
Control: severity -1 normal
On Thu, Jul 09, 2020 at 01:27:34PM +0200, Lucas Nussbaum wrote:
> Source: pmdk
> Version: 1.8-1
> Severity: serious
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> > pmem_check_version@@LIBPMEM_1.0
> >
Control: block -1 by 964457
On Thu, Jul 09, 2020 at 01:27:34PM +0200, Lucas Nussbaum wrote:
> Source: pmdk
> Version: 1.8-1
> Severity: serious
> Relevant part (hopefully):
> > pmem_check_version@@LIBPMEM_1.0
This is caused by #964457 which appends decoration to symbols once if there
should be
On Sat, Jul 18, 2020 at 03:36:48PM -0400, Boyuan Yang wrote:
> X-Debbugs-CC: debian-fo...@lists.debian.org m...@debian.org
>
> On Thu, 16 Jul 2020 23:19:31 +0200 Andreas Beckmann
> wrote:
> > Package: afdko-bin
> > Version: 3.4.0+dfsg1-2
> > Severity: serious
> >
> > Preparing to unpack
On Wed, Jul 08, 2020 at 03:44:21PM +0200, Ansgar wrote:
> On Wed, 2020-07-08 at 11:04 +0200, Johannes Schauer wrote:
> > What is happening here is, that aspcud chooses libelogind0 for installation
> > and
> > then apt decides that it refuses to install it because it doesn't want to
> > remove
The real culprit here, is that pkg:systemd provides many many distinct
interfaces, without letting any consumers say _which_ interfaces they want.
Thus, all of this would be solved if systemd declared Provides:systemctl
and relevant consumers depended on that.
Same with systemd-revolvd,
On Sun, Mar 22, 2020 at 09:24:01AM +0100, Lucas Nussbaum wrote:
> Source: safeclib
> Version: 3.5-2
> Severity: serious
> Justification: FTBFS on amd64
> > FAIL: t_towfc_s
> > ===
> >
> > test_towfc_s 211 Error: towfc(U+A7C7) => A7C7 "A7C8" status=C LATIN
> > CAPITAL LETTER D WITH
On Sat, Mar 21, 2020 at 05:47:25PM +0100, Ivo De Decker wrote:
> On Sat, Mar 21, 2020 at 02:43:19PM +0100, Adam Borowski wrote:
> > I've uploaded binaries for amd64 arm64 armhf i386 (ie, arch in testing), so
> > it should be done.
> >
> > Apparently the package can
Just so there's a public record: I've sponsored the version of runit that
was rotting on mentors as-is; it included a bunch of fixes and transfer of
maintainership to Lorenzo.
This means, we now have a proper maintainer.
Meow.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies
Control: severity -1 normal
I don't get why this would be severity:critical.
With Recommends enabled, there are hundreds of packages that cause a
large-scale changeover of the system -- be it DE switch, installing a gig or
more of random daemons, an init system switch, or the like.
So unless
Source: a2ps
Version: 1:4.14-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid this package build-depends on emacs25, which is long since gone.
-- System Information:
Debian Release: bullseye/sid
APT prefers
Package: qemu-system-ppc
Version: 1:4.2-2
Severity: grave
Justification: renders package uninstallable
Hi!
Upon upgrading or a fresh install:
Unpacking qemu-system-ppc (1:4.2-2) ...
dpkg: error processing archive «TMP»/3-qemu-system-ppc_1%3a4.2-2_amd64.deb
(--unpack):
trying to overwrite
Package: libipmctl4
Version: 02.00.00.3673+ds-2
Severity: serious
The conffile migration is broken, resulting in:
/etc/cron.daily/logrotate:
error: ipmctl.conf:1 duplicate log entry for /var/log/ipmctl/*log
error: found error in file ipmctl.conf, skipping
run-parts: /etc/cron.daily/logrotate
Control: clone -1 -2
Control: retitle -2 RM: doc-debian-fr -- RoQA; ancient docs
Control: severity -2 normal
Control: reassign -2 ftp.debian.org
On 2018-05-01, Moritz Muehlenhoff wrote:
> These docs have been updated the last time over 12 years ago, is this
> actually still useful or rather
On Thu, Nov 14, 2019 at 09:13:51AM +0100, Andras Korn wrote:
> I just stumbled on this bugreport.
>
> I'm a happy pm-utils user and would like the package to stick around. I use
> it on dozens of computers ranging from servers to desktops to laptops.
>
> From reading the bugreport, there doesn't
Source: fonts-beteckna
Version: 0.5-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi!
I'm afraid that fonts-beteckna fails to build:
** (process:53089): WARNING **: 22:56:10.699: GlyfData.vala:407: Point on point
in TTF. Index 50 Path: 1 in 9
E: Build killed with
Source: fonts-alegreya-sans
Version: 2.008-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi!
I'm afraid your package fails to build from source:
.
INFO:fontmake.font_project:Generating instance UFO for "Alegreya Sans Light"
Traceback (most recent call last):
Source: xfonts-efont-unicode
Version: 0.4.2-11
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi!
I'm afraid that the package fails to build, with a bunch of:
Assigning non-zero to $[ is no longer possible at tools/hex2bdf line 17, <>
line 7446.
Additionally, there's
On Mon, Oct 07, 2019 at 10:44:12PM +0200, Thorsten Glaser wrote:
> On Mon, 7 Oct 2019, Jean-Marc LACROIX wrote:
> > It seems that now all is ok, because sysvinit is correctly installed on
> > Debian
> > 10.1
>
> Yes, but the other packages are not yet ready for elogind
> in Debian 10.anything
On Sat, Sep 28, 2019 at 02:53:56AM +0200, Thorsten Glaser wrote:
> On Fri, 27 Sep 2019, Mark Hindley wrote:
>
> > Thanks. The aim of preventing accidental removal of systemd is very
> > reasonable. However, using this approach the hurdle you create even to a
> > user
> > who really wants to
On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
>
> The "init" package has the "Important: yes" control field which as I
> understand it tells apt to behave like
On Thu, Sep 26, 2019 at 12:52:27PM +0200, Thorsten Glaser wrote:
> On Thu, 26 Sep 2019, Mark Hindley wrote:
> > It is possible to get APT to attempt a solution by specifically requesting
> > 'apt
> > install libelogind0 sysvinit-core'. This removes systemd-sysv and then
> > fails
>
> Does it
On Mon, Sep 23, 2019 at 11:58:18AM -0400, Sam Hartman wrote:
> Mark> #935910 is now fixed in apt 1.8.4 in unstable and with that
> Mark> installed I can no longer reproduce #934491. The APT
> Mark> maintainers have said that adding a Breaks for the fixed
> Mark> version of apt is
On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
> When I looked I elogind a while back I was able to build a package without
> having a public libelogind0, I basically had that in my debian/rules file:
>
> # We only build the libelogind0 and libelogind-dev if we are building
On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote:
> I reached out to jcristau to talk about his block hint.
> Based on our IRC discussion, it sounds like he was having trouble
> bringing himself to remove the hint presumably because he doesn't think
> the broader issue was being dealt
Source: qemu
Version: 1:3.1+dfsg-8
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid that a recent incompatible change to gluster's API makes qemu
fail to build:
/<>/block/gluster.c: In function ‘qemu_gluster_do_truncate’:
p to be the new upstream, I guess we will have to have it
> removed eventually. Let's do it a while later (like by the end of this year).
> On Wed, 24 Jul 2019 03:05:20 +0200 Adam Borowski wrote:
> > Package: python-qrtools
> > Severity: grave
> > This package depends on pyth
Package: python-qrtools
Version: 1.4~bzr32-1
Severity: grave
Justification: renders package unusable
Hi!
This package depends on python-zbar, which has already been removed as part
of the python2-rm transition. This obviously makes it non-installable.
Meow!
-- System Information:
Debian
On Sat, Jul 13, 2019 at 04:40:31PM +0200, Yves-Alexis Perez wrote:
> On Thu, 2019-07-11 at 10:34 +0200, Adam Borowski wrote:
> > So... is there any reason to not let xfce4-screensaver go to Bullseye?
> > Any day that a human being suffers from light-locker is a bad day.
>
>
> So we're filing an RC bug to prevent it from migrating to testing,
> this can be closed once buster is frozen.
So... is there any reason to not let xfce4-screensaver go to Bullseye?
Any day that a human being suffers from light-locker is a bad day.
If you're afraid about yet-unknown bugs, more
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,
Control: severity -1 wishlist
On Thu, Jun 27, 2019 at 09:00:38PM +0200, Michael Biebl wrote:
> Am 24.06.19 um 00:46 schrieb Ivo De Decker:
> > acpi-support depends on it, so removal is not possible. And even if it was,
> > it
> > would probably be too late for that.
> >
> > Tagging this bug
On Sat, Jun 22, 2019 at 11:26:40AM +0200, Tobias Hansen wrote:
> On 6/21/19 10:54 PM, Adam Borowski wrote:
> > (patch is
> > https://salsa.debian.org/pulseaudio-team/pulseaudio/merge_requests/5)
> >
> > On Fri, Jun 21, 2019 at 11:37:48AM +0200, Tobias Hansen wrote:
&g
On Sat, Jun 22, 2019 at 08:06:08AM +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
> > severity 930869 serious
> Bug #930869 [pm-utils] needs purging of quirks
> Severity set to 'serious' from 'wishlist'
> > retitle 930869 Don't release with buster
>
Control: severity -1 wishlist
Control: retitle -1 needs purging of quirks
On Fri, Jun 21, 2019 at 10:22:16PM +0200, Michael Biebl wrote:
> >>> But, do we even have an alternative for suspending remotely?
> >> Not really, pm-utils is not needed.
> > Could you then please educate me what the
On Fri, Jun 21, 2019 at 08:53:32PM +0200, Michael Biebl wrote:
> Am 21.06.19 um 20:05 schrieb Adam Borowski:
> > But, do we even have an alternative for suspending remotely?
>
> What do you mean by that?
So here we have a computer. No GUI tools. No emulation of GUI tools.
And I
On Fri, Jun 21, 2019 at 07:42:00PM +0200, Michael Biebl wrote:
> Package: pm-utils
> Version: 1.4.1-18
> Severity: serious
>
> As former maintainer of pm-utils, I don't want to see pm-utils released
> with buster.
> pm-utils is a set of hacks/scripts which back in the days were necessary
> to
> "Crash confirmed. Buthis program is not expected to be able to deal
> with arbitrarily broken input. All I'm going to do about it is add a
> SIGSEGV handler."
> here we have an upstream maintainer explicitly saying that an
> image-processing program is not suitable for use on arbitrary input
Control: severity -1 important
> Severity: serious
> Justification: Debian Policy violation
> /bin/mkfs.btrfs and /bin/fsck.btrfs are Policy and FHS violations.
I don't believe this is in any way RC -- for Buster nor likely any future
release. There's no functional lossage, AFAIK.
fsck
1 - 100 of 383 matches
Mail list logo
