Control: severity -1 important
As FTBFS on an architecture not in testing is not RC, lowering severity to
let it migrate. This is a toolchain bug.
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ The moon landing was staged, but the director insisted they
⢿⡄⠘⠷⠚⠋⠀ shoot on location -- so they did.
⠈⠳⣄
Unsubscribe
On Wed, Mar 19, 2025 at 12:06 PM László Böszörményi (GCS)
wrote:
> Control: forwarded -1 https://github.com/libexpat/libexpat/issues/980
>
> Hi Jeremy,
>
> Strange, didn't get your bug report via email. Emailing directly.
> This is known, I've already reported it upstream [1], git
Hi Jeremy,
On Tue, Mar 04, 2025 at 05:44:52PM -0500, Jeremy Bícha wrote:
> xpdf fails to build with poppler 25.03.
This is already fixed upstream, so it just needs an update of the
xpdf package to the latest Git version.
Thanks,
--
Adam Sampson <http://offog.org/>
ds an upstream fix on top of the above change.)
3. I then installed
linux-image-6.1.0-0.a.test-amd64-unsigned_6.1.128-1a~test2_amd64.deb
(uname -a includes " 6.1.128-1a~test2"). That also boots fine.
Regards,
Adam
Some further observations:
I tried booting the 6.1.0-29-amd64 kernel and continue to see the same
behaviour (i.e. system is unbootable).
These are servers running xen. If I boot the affected kernels directly
rather than via the xen hypervisor, I can boot succesfully.
Under xen, I have tried
I see the same symptoms on linux-image-6.1.0-28-amd64 kernel 6.1.119-1:
boot hangs at the same point, and I see the same "swiotlb buffer is
full" message from i40e on the console.
syslog from a failed boot.2024-11-18T19:57:33.624467+00:00 xenhost4-a systemd[1]: Started xen.service -
LSB: Xen daemons.
2024-11-18T19:57:33.692566+00:00 xenhost4-a kernel: [ 13.184037]
vlanbr1100_2nd: port 1(ens785f0.1100) entered blocking state
2024-11-18T19:57:33.692590+00:00 xenhost4-a ke
Package: src:linux
Version: 6.1.115-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
Trying to boot 6.1.0-27-amd64 / 6.1.115-1 (under the current Xen
hypervisor xen-hypervisor-4.17-amd64) led to a hang at boot whilst
trying to bring up network interfaces. I was able to
are
not RC.
Regards,
Adam
Package: matrix-synapse
Version: 1.116.0-3+b1
Severity: grave
Justification: renders package unusable
Hi,
with the update of python3-twisted in unstable to 24.10.0-1,
matrix-synapse refuses to start:
$ /usr/bin/python3 -m synapse.app.homeserver
--config-path=/etc/matrix-synapse/homeserver.yaml
; (for /boot/ partition).
>
> Maybe that document should be updated for this CENTURY?
"That document" comes from src:installation-guide, which is maintained
by the d-i team, not the Release Team.
Regards,
Adam
build of the same kernel version.
Please let us know if you need any further information.
Regards,
Adam
On Thu, 2024-05-16 at 17:01 +0100, Sean Whitton wrote:
> control: reopen 1031888
>
> Hello Adam,
>
> On Fri 21 Apr 2023 at 10:19am +01, Adam D. Barratt wrote:
>
[...]
> > With my DSA hat on, I'm not aware of it having been confirmed to
> > fix
> > th
package release.debian.org
tags 1067016 = bullseye pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian bullseye.
Thanks for your contribution!
Upload details
==
Package: nvidia-settings
Version: 470
On 2024-04-07 05:23, Ying-Chun Liu (PaulLiu) wrote:
I've fixed the bug. And I'll do NMU if no one object in 10 days.
I'll upload it to the delay/10 queue.
Attachment is the debdiff. Please review it.
Thanks, looks good
- Adam
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 ups
On Sun, 2023-11-05 at 21:46 +0100, Markus Koschany wrote:
> Am Sonntag, dem 05.11.2023 um 20:35 + schrieb Adam D. Barratt:
> > [...]
> > After a bit of searching, I happened across a discussion of a
> > similar
> > change in a different product that mentioned the
&
On Sun, 2023-11-05 at 19:18 +0100, Markus Koschany wrote:
> Am Sonntag, dem 05.11.2023 um 16:33 + schrieb Adam D. Barratt:
> > [...]
> > Do you have an idea how simple rebuilding the bullseye package on
> > buster would be? I'm happy to try that in general, but I&#x
general, but I've not really
looked at the Java ecosystem in Debian much.
Regards,
Adam
sure which keystore is being referred to, but none of the files
listed in /etc/puppetdb/conf.d/jetty.ini appear to contain more than a
single certificate.
Regards,
Adam
-- Logs begin at Sat 2023-11-04 14:52:45 UTC, end at Sat 2023-11-04 16:16:11
UTC. --
Nov 04 14:52:50 handel systemd[1]: St
an Testing.
No. Architecture-specific removals happen in unstable, so the request
needs to be made to the FTP Team.
Regards,
Adam
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 befor
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 check
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 to
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 a
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 dire
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 is
at the list of bugs you have filed so far tonight,
any transition that introduces over 100 build failures in other
packages is in no sense ready to happen "soon".
Regards,
Adam
le $prefix/grub.cfg
So I have 2 work arounds though for some reason when pasting from a pikvm
after grub has loaded results in characters not always pasting correctly
which make it more difficult to enter the password.
- Adam Hough
On Sun, May 14, 2023 at 12:06 AM Adam Hough wrote:
> Package: g
Package: grub-efi-amd64-bin
Version: 2.06-12
Followup-For: Bug #924151
Dear Maintainer,
* What led up to the situation?
Upgraded to the latest grub2 packages on 2023-05-02 and then had a power
outage today resulting in a reboot.
grep grub dpkg.log | grep upgrade
2023-05-02 16:44:00 upgra
load today (or early tomorrow)?
>
With my DSA hat on, I'm not aware of it having been confirmed to fix
the issue on bullseye. I'm happy to test an updated package in the
meantime. (FWIW the update isn't in p-u currently because of this
issue.)
Regards,
Adam
in front of my computer.
Regards, Adam.
On March 25, 2023 2:55:39 PM GMT+01:00, Andreas Tille wrote:
>Hi,
>
>as you can read in the bug log, there was an upload of a new version of
>tiledb a couple of hours before it has migrated to testing. Thus the
>package remains affected
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: valgrind-
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:
./arm_compute/core/ITensorPack.h:89:5
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'
configu
1u1 on the same system works fine. Removing the
emacs packages and installing +deb11u2 directly fails in the same way.
This is reproducible on four debian.org buildds.
Regards,
Adam
Source: linuxcnc
Severity: serious
Source files for libnml lack standard Debian or SPDX copyright headers. Also
obsolete version of LGPL used.
Source files for both the core linuxcnc & libmnl are forked and munged from a
NIST project known as the Enhanced Machine Control (EMC). The source code
due to issues with Video4Linux. Relevant-looking log
output is included below.
Regards,
Adam
FAILED: obj/media/gpu/v4l2/v4l2/v4l2_video_decoder_delegate_vp8.o
clang++-13 -MMD -MF obj/media/gpu/v4l2/v4l2/v4l2_video_decoder_delegate_vp8.o.d
-DMEDIA_GPU_IMPLEMENTATION -DUSE_UDEV -DUSE_AURA=1
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
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 "tot
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 untaggin
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 xfce4-screen
Source: debian-archive-keyring
Version: 2021.1.1
Severity: serious
X-Debbugs-Cc: debian-rele...@lists.debian.org
Hi,
We need an SRM key for bookworm, so that we can include it in the
release.
Regards,
Adam
Source: debian-archive-keyring
Version: 2021.1.1
Severity: serious
X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org
Hi,
We need new archive signing keys for bookworm, so that we can include
them in the release.
Regards,
Adam
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 ca
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 bo
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 Wed, 2023-01-04 at 18:31 +, Adam D. Barratt wrote:
> One difference at least is that "IPv6-only" buildds *do* have IPv4
> networking, but only on lo. As a result, your have_inet4 test will
> return true:
>
> adsb@x86-conova-01:~$ ip --brief -4 a
> lo
NKNOWN127.0.0.1/8
adsb@x86-conova-01:~$ perl -MIO::Socket::INET -e '$sock =
IO::Socket::INET->new(LocalAddr => "127.0.0.1", Proto => "udp");' -e
'print $sock ? "true\n" : "false\n";'
true
https://lists.debian.org/debian-devel/2020/07/msg00070.html is a
discussion of the general issue from a couple of years ago, which
actually includes spamassassin in its list of affected packages.
Regards,
Adam
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
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: t_loc
g-any" build dep doesn't allow the package to be built.
(I wound up moving 'testing' above 'stable' and upgrading the whole system,
but when I tried this I had 'stable' at priority 900 and 'testing' at 400.)
Adam Buchbinder
-- System Information:
D
which generate
lists of RC bugs in unstable and testing for britney, meaning that
those lists have not been updated since Monday morning.
Regards,
Adam
s is not supposed to happen, and I haven't seen this before.
So far as I can tell, the timeline is:
- 2022-10-26 package is uploaded
- 2022-10-31 package is removed as obsolete
- 2022-11-03 the same package is re-uploaded, with a different GPG
signature
The file in the archive matches the "expected" hashes, whereas deb.d.o
is returning the original file.
Regards,
Adam
the former was fixed in 1.1.1n-0+deb11u2).
> * (CVE-2022-2097)[https://nvd.nist.gov/vuln/detail/CVE-2022-2097]
> (medium)
>
and https://security-tracker.debian.org/tracker/CVE-2022-2097 has this
tagged as waiting for additional updates to fix it alongside.
Regards,
Adam
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 foun
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 tidewa
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: sou
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 an
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:
https://angband.pl/tmp/piu_sys
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 /
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)
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 w
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.
⠈⠳⣄
suitable directory for output in ‘comp-native-load-path’.
I had the same issue. Turned out my personal .emacs.d/eln-cache
directory and its folders belonged to root:
$ ls -la $HOME/.emacs.d/eln-cache
total 16
drwxr-xr-x 4 root root 4096 Aug 21 19:32 .
drwx-- 4 adam users 4096 Aug 19 19:43 .
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
> make
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
tand openrc is no longer maintained, this may be the
best option.
In case it's helpful, one of the Devuan maintainers found this issue
on OpenRC's github, reporting the same issue:
https://github.com/OpenRC/openrc/issues/383. I assume this was never
reported.
Best,
Adam
own-linux-gnu/release/deps/libuluru-42c98827bce5cca4.rmeta
--extern
unicode_bidi=/<>/build-browser/mipsel-unknown-linux-gnu/release/deps/libunicode_bidi-d16d7c80c58bfd63.rmeta
--extern
unicode_segmentation=/<>/build-browser/mipsel-unknown-linux-gnu/release/deps/libunicode_segmentation-cec5165efb9b4c7f.rmeta
--extern
void=/<>/build-browser/mipsel-unknown-linux-gnu/release/deps/libvoid-183776478cdbbb7c.rmeta
--cap-lints warn --remap-path-prefix=/<>=. -Cembed-bitcode=yes
-Cembed-bitcode=yes -C codegen-units=1` (signal: 6, SIGABRT: process abort
signal)
Regards,
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 CC
patch
>
> Hello, in the last version .26 the place for the test file changed from
>
> test/test.py
>
> to:
>
> test/python_magic_test.py
>
> please update debian/tests/run-testsuite accordingly
>
> G.
>
>
>
--
Adam Hupp | http://hupp.org/adam/
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 th
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: impli
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 Py
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 unsup
he
format parser.
Thanks!
- Adam
On 12/16/21 9:37 AM, Damyan Ivanov wrote:
Dear maintainer,
I've prepared an NMU for lpr (versioned as 1:2008.05.17.3+nmu1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
Thank you! The upload is appreciated.
- Adam
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 o
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 ar
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 a
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 wor
from Buster? (Its
original installation was Jessie and has been upgraded throughout releases.)
* Adam Reece
* Sven Co-op team
* Email: a...@svencoop.com <mailto:a...@svencoop.com>
* Web: www.svencoop.com <http://www.svencoop.com>
On 31/08/2021 17:47, Timo Aaltonen wrote:
On 22.
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 associa
o directory "/etc/dirsrv/slapd-amun" to be sure
that wasn't needed. Still starts fine.
The package installation triggers probably just need updating to make that "lib"
directory and symlink "libjemalloc.so.2" in place.
--
* Adam Reece
* Sven Co-op team
OpenPGP_signature
Description: OpenPGP digital signature
hen restart the server.
> Aug 22 14:13:38 amun systemd[1]: dirsrv@amun.service.service: Main process
> exited, code=exited, status=1/FAILURE
> Aug 22 14:13:38 amun systemd[1]: dirsrv@amun.service.service: Failed with
> result 'exit-code'.
> Aug 22 14:13:38 amun systemd[1]: Failed to start 389 Directory Server
> amun.service..
I've also done `apt install libjemalloc2` to bring this library in, but that
didn't resolve this.
Please let me know if any further information is required.
Thanks,
Adam
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 wi
Hello,
Upstream bug has been fixed:
https://github.com/ilevkivskyi/typing_inspect/commit/6bc521b9ba9fd22d2d3f219fcc99dedc3fb4c2f7
You can find attached a slightly modified version of the patch that
applies to current package and fix test failure.
Regards, Adam.
--- python-typing-inspect
00
+++ redshift-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
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
> > > >
crashes with the same error message, it cannot start.
I updated the package on SALSA to latest upstream version:
https://salsa.debian.org/python-team/packages/python-drf-spectacular
And this one is building fine, unittests run successfully and my Django app is
working again.
I'm not sure if
> * 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
1 - 100 of 2737 matches
Mail list logo
