Package: src:h2o
Version: 2.2.5+dfsg1-6
Severity: serious
Dear Maintainer,
when trying to build h2o from source on amd64, inside sbuild, it fails:
h2o server (pid:14780) is ready to serve requests
fetch-ocsp-response (using OpenSSL 1.1.1-pre9 (beta) 21 Aug 2018)
failed to extract ocs
* Gianfranco Costamagna [180911 06:48]:
> control: tags -1 patch pending
> the following diff is now in deferred/4, please let me know if you want me to
> cancel or reschedule it.
Please commit your changes on salsa; feel free to do a team upload
(with no delay) then.
Cheers,
Chris
Upstream commit is:
https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=commit;h=fef089a6610f94a847541069f3008a5708044015
Control: tag -1 pending
Hello,
Bug #903285 in bundler reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/bundler/commit/8a341807711a62dd9bd44f185ad62545
Package: netgen
Version: 4.9.13.dfsg-11
Severity: serious
In #896085 it has been suggested that tk8.5 should go away before
stretch. This bug informs you of this ;-)
C.
Package: autopkgtest
Version: 5.4.1
Severity: grave
Justification: renders package unusable
Dear autopkgtest Maintainers,
In various situations autopkgtest calls /bin/su with an empty string for
the username. The old su (from login) ignored this, but newer su
versions (from util-linux 2.32-0.2) d
* Helge Kreutzmann [180808 18:57]:
> On Tue, Aug 07, 2018 at 08:20:23PM +0100, Simon McVittie wrote:
> > Andreas already asked for a merge request, so it seems that proposing a
> > patch would indeed be welcome.
>
> I'll do, incorporating your excellent explaination. I'll do so until
> the end of
Control: clone 896085 -2
Control: reassign -2 ftp.debian.org
Control: retitle -2 RM: tk8.5 -- ROQA; obsolete
Control: affects -2 src:tk8.5
* Sergei Golovan [180809 20:47]:
> Source: tk8.5
>
> Tcl/Tk 8.5 has reached its end-of-life, so it's time to remove it from Debian.
> Applications which use
Hi Markus,
* Markus Wanner [180809 20:52]:
> On 03/09/2018 10:32 AM, Jack Lloyd wrote:
> > 2.4.0 was just (in last week or so) packaged for buster -
> > https://packages.debian.org/buster/libbotan-2-4
>
> oh, very nice. Looks like I searched only "stable". Thank you for the hint.
Is there any
Dear ovito Maintainers,
is there any update on progress of porting to botan2, or at least
moving off botan1.10?
Cheers,
Chris
* Hideki Yamane [190103 03:40]:
> On Fri, 16 Feb 2018 13:48:16 + z...@debian.org wrote:
> > Bug #816640 in ruby-eventmachine reported by you has been fixed in the
> > Git repository and is awaiting an upload. You can see the commit
> > message below, and you can check the diff of the fix at:
>
Control: severity -1 important
* Bastian Germann [230226 14:12]:
> Control: retitle -1 RM: mercurial-buildpackage -- RoQA; no users left
> Control: severity -1 serious
>
> On Tue, 20 Dec 2022 03:24:46 +0100 Chris Hofstaedtler wrote:
> > It would appear mercurial-buildpac
+
+++ h2o-2.2.5+dfsg2/debian/changelog2023-03-21 12:40:38.0 +
@@ -1,3 +1,11 @@
+h2o (2.2.5+dfsg2-7) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove VCS tags from picohttpparser source files
+ * Disable failing mruby test (Closes: #1032554)
+
+ -- Chris
Hi Anton,
* roehl...@debian.org :
> Source: wslay
[..]
>
> your package wslay will soon experience autopkgtest failures because
> the new CMake release 3.27 will issue a deprecation warning on stderr
> if cmake_minimum_required() asks for compatibility with CMake 3.4 or
> older.
I've opened an M
* Niels Thykier :
> The fakeroot/1.30.1-1 FTBFS on mipsel (release arch) which blocks the fix
> for #1023286 from affecting mipsel binaries.
I'll note that the FTBFS is caused by a test failure in test
"t.chown". stat(1) is used to check the expected owner of a file,
and the test reveals (I think)
Package: x-loader
Version: 1.5.1+git20110715+fca7cd2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Dear QA Group,
the package x-loader was recently gifted to you, but it FTBFS:
gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -msoft-float -Werror
-D__KERNE
Source: golang-github-siddontang-go-snappy
Version: 0.0~git20140704.0.d8f7bb8-6.1
Severity: serious
This package was introduced for gitea, and has been orphaned once gitea
was removed. It has seen no updates since. Lets keep these libraries out
of testing.
Chris
Source: golang-github-unknwon-i18n
Version: 0.0~git20170218.0.8372b90-1
Severity: serious
This package was introduced as a library used by gitea, but has not seen
updates in 5 years and gitea itself is also long gone. Upstream also has
given up on it many years ago.
Lets keep these bits out of te
Control: retitle -1 VMs created on buster do not boot on bullseye
Control: severity -1 normal
Control: tags -1 + moreinfo
Control: reassign -1 virt-daemon
Hi everyone,
I just spent some time trying to reproduce this, until I re-read the
bug report more carefully. I think it says, in my words:
--
* YunQiang Su :
> 在 2022/1/14 23:30, Sandro Tosi 写道:
> > On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su
> > wrote:
> > >
> > > On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel
> > > wrote:
> > > > Built with gcc-11 and -fno-lto it doesn not work.
> > > >
> > > >
> > > (sid_mip
* Dmitry Bogatov :
>
> [2019-03-16 00:41] Lorenzo Puliti
> > >Bogatov wrote:
> > >Dear git maintainer, you could plug this bug by adding
> > >`/var/lib/supervise/git-daemon' into `debian/git-daemon-run.dirs'.
> >
> > Dmitry, are you sure? runsv can create the 'git-daemon' directory if
> > it's n
* Adrian Bunk :
> Source: libcommoncpp2
[..]
> src:ucommon is the successor of libcommoncpp2, and the only
> remaining build dependency on libcommoncpp2-dev in
> vdr-plugin-fritzbox is stale.
It appears all r-(build-)deps are gone. Should src:libcommoncpp2
also go away from unstable?
Chris
Source: scalc
Version: 0.2.4-6
Severity: serious
It appears src:scalc only builds a library package, and nothing in
Debian uses it. If people see value in keeping it in bookworm,
please speak up.
I'll note that there is a new, completely unrelated project using
the "scalc" name, so it might be a
Source: libbase58
Version: 0.1.4-5
Severity: serious
libbase58 appears to be a leaf library package - nothing else in Debian
debends on it. Apparently it was introduced for some other
bitcoin-related libraries, which are gone again.
I would suggest we waste no resources on this for bookworm. Inte
Hey Noah,
* Noah Meyerhans [190711 14:17]:
> If you disagree that ipsec-tools should be removed from future Debian
> releases, please say so now.
As we haven't really heard from anyone, should I go ahead and ask
for final removal via ftpmaster?
Cheers,
Chris
* Julien Cristau [210413 17:32]:
> I'm not sure that's quite correct as it doesn't restore the backwards
> compatibility that python broke. On the other hand I don't know if
> python even provides a way for consumers to remain backwards-compatible.
> Thanks, python...
No: https://bugs.python.org
Hello again,
just in case you are not aware - if snort should stay in testing,
someone will need to file an unblock bug against release.debian.org.
The updated version will not transition into testing automatically.
Cheers,
Chris
* Pelle [210423 15:45]:
> [..], but then freeze for about half a minute
> and then just disappear and thereby allow access to Sway without the password
> being entered.
Sounds like it crashes?
Please install swaylock-dbgsym and see if you can get a coredump.
Chris
* Thorsten Glaser [210423 16:00]:
> Chris Hofstaedtler dixit:
>
> >installation path. I imagine going back is now hopeless, so either
> >git searches both paths, or all other packages are just rc-buggy.
>
> I wasn’t considering just packages; unpackaged (or third-party
Hi everyone,
* Lisandro Damián Nicanor Pérez Meyer [210423 21:06]:
> Hi! Indeed it's not working again, so reopening the bug.
>
> On Wed, 21 Apr 2021 10:12:03 + Damyan Ivanov wrote:
> > Sigh. Now git reverted to using /usr/lib again, and git-flow is broken.
It appears some more coordinatio
* didi.deb...@cknow.org [210423 21:23]:
> TLSv1.2 was defined in 2008, so I don't think it's to 'wild' to use that
> as a default for security in the default configuration of nginx for Bullseye.
You seem to neglect to mention that SSL/TLS is disabled in the
default configuration. I agree that sug
Source: mosquitto
Version: 2.0.10-4
Severity: serious
Dear Maintainer,
your autopkgtest appears to fail:
autopkgtest [21:45:54]: test library: [---
pkill: killing pid 1764 failed: Operation not permitted
make: Entering directory
'/tmp/autopkgtest-lxc.zrj4yodu/downtmp/build.e
Hello Roland,
* Roland Mas [210424 11:17]:
> The problem mentioned in #986525 has a fix upstream in
> https://github.com/aio-libs/yarl/pull/575. I prepared a merge request at
> https://salsa.debian.org/python-team/packages/yarl/-/merge_requests/3 with
> the patch, formatted according to DEP-3 gui
* Brian Thompson [210424 14:04]:
> > autopkgtest [21:45:54]: test library: [---
> > pkill: killing pid 1764 failed: Operation not permitted
[..]
> I'm not a maintainer, but I see that in the code the command does what
> it intends to do, checks out with the man pages although
Control: tags -1 + moreinfo
Hi,
* Simon McVittie [210424 16:00]:
> This might have been triggered by not having librsvg2-common installed?
> GTK has a Recommends on librsvg2-common, but it is not a hard dependency,
> because not all GTK applications strictly need the ability to draw SVG
> icons.
It appears the change itself was intentional:
> uimaj (2.10.2-2) unstable; urgency=medium
>
> * No longer build the uimaj-adapter-soap module
>
> -- Emmanuel Bourg Fri, 30 Nov 2018 09:07:17 +0100
However, the binary package should probably also have been removed.
Maintainers, please come
Control: found -1 1.4.0-1
It appears this change was intentional, however the binary package
should then also go away:
> ocaml-migrate-parsetree (1.4.0-1) unstable; urgency=medium
>- do no longer provide automatic doc with dh_ocamldoc
Maintainers, please remove the now empty binary or make s
Control: found -1 0.9.14-1
Hello,
it appears this was an intentional change, but then the binary
package should also have been removed:
> lmfit-py (0.9.14-1) unstable; urgency=medium
>
> * unactivated the doc build until jupyter_sphinx is available.
Maintainers, please remove the binary packa
Control: found -1 2.0.7~dfsg-3
Probably introduced in this change?
> emscripten (2.0.7~dfsg-3) unstable; urgency=medium
> * fix avoid compiling code in architecture-independent build
Chris
Control: found -1 6.3.0+dfsg2-7
It appears this was intentional, but the binary package should also
have been removed:
> vtk6 (6.3.0+dfsg2-7) unstable; urgency=medium
> * d/*: remove support for QT, no reverse deps, Closes: #975135
Apparently vtk6 also Depends on libvtk6.3-qt for unknown reasons
It appears some StackOverflow users also see this:
https://superuser.com/questions/1483696/cifs-mounted-on-linux-from-windows-shows-corrupt-distorted-images
I could not find anything on bugzilla.kernel.org though :-(
Maybe someone who can reproduce the problem should talk to upstream
about it...
Control: fixed -1 prometheus-mongodb-exporter/1.0.0+git20180522.e755a44-3
> I tried to install prometheus-mongodb-exporter to export statistics
> about my MongoDB instance. After multiple attempt to
> make it connect to the database, I stopped the systemd service and ran
> it by hand
Hello,
* Holger Wansing [210424 21:42]:
> While trying to debug another problem yesterday, I found that the RC1
> graphical
> installer fails to go forward, when selecting one of these languages:
> - Kannada
> - Marathi
> - Persian
> - Sinhala
I spent a few hours today o
* Peter Pentchev [210424 23:34]:
> [Explanation]
> So... I think that this is the way the "build" tool is supposed to
> operate. If somebody needs to use it with assuredly nothing downloaded
> from external sites, e.g. during a Debian package build, then I think
> a non-isolated build is the way
* Adrian Bunk [210425 11:09]:
> g++ --version: "g++ (Debian 10.2.1-6) 10.2.1 20210110"
> ERROR: (test000) testrunner failed, see log
Looking at the tests, they all produce this error and then crash:
| unsupported compiler version 10.2(*), contact author for support
Indeed there's a gcc version
* Chris Hofstaedtler [210425 11:36]:
> Indeed there's a gcc version check in src/cov_file.C, which does not
> know about gcc 10.2 yet. The 10.1 code path got added by
>debian/patches/compilers.patch.
Trivially adding 10.2 in there does fix the FTBFS.
I imagine Alastair will
Hi,
* Holger Wansing [210425 11:34]:
> Chris Hofstaedtler wrote (Sat, 24 Apr 2021 23:45:13 +0200):
> > * Holger Wansing [210424 21:42]:
> > > While trying to debug another problem yesterday, I found that the RC1
> > > graphical
> > > installer fails to go
* Adrian Bunk [210425 12:34]:
> https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/kannel.html
[..]
> https://bugs.launchpad.net/ubuntu/+source/kannel/+bug/1838425
Kannel turned off building of PS docs in 1.4.5-7 (and stopped using
imagemagick); but obv. not in buster.
Source: muttprint
Version: 0.73-8.1
Severity: serious
Caused by #987504, see that bug for further details.
Log fragment:
dh_testdir
# convert images (and make pics/ build work)
cd pics && \
for i in BabyTuX_color.eps BabyTuX.eps Debian_color.eps Debian.eps; do \
convert $i `basename $i .eps`
* Holger Wansing [210425 16:53]:
> Chris Hofstaedtler wrote (Sun, 25 Apr 2021 14:13:05 +0200):
> > While the -exact- same bug does not appear on the
> > 20210424-7/amd64/iso-cd/debian-testing-amd64-netinst.iso image, I
> > think the bug is still there, just better hidden.
* Rene Engelhard [210425 15:25]:
> Am 25.04.21 um 15:05 schrieb Chris Hofstaedtler:
> > Caused by #987504, see that bug for further details.
>
> Then imagemagick should be fixed. I mean, come on, it's simple image
> convert...
While I agree with these simple words
* Georges Khaznadar [210426 06:43]:
> Dear Chris, thank you for the bug report.
>
> I believe that the bug is fixed with the newly uploaded release
> 3.35.2-3.
>
> What should I do next to allow clonezilla to be included in bullseye ?
> Is the upload enough or must I make some other acknowledgem
* Cyril Brulebois [210429 18:03]:
> Cyril Brulebois (2021-04-29):
> > This time around, testing 1.43.0 with debian/ carried over from
> > debian/1.42.4-8, adjusted for docs (some files are missing) and symbols
> > (one new symbol), the problem cannot be triggered in an obvious manner.
> >
> > Mo
* Cyril Brulebois [210430 09:47]:
> Anyway, looking at the diffstat between 1.43.0 (last known good) and
> 1.44.4 (first known bad), we have this:
> 179 files changed, 19157 insertions(+), 7045 deletions(-)
>
> Between 1.43.0 and 1.44 (if it were an earlier known bad):
> 165 files changed, 1100
Package: ifenslave
Version: 2.11
Severity: serious
Only trivial configurations with no per-slave configurations seem to
work. I.e. the example in /usr/share/doc/ifenslave/examples/two_ethernet
works.
However, the example in /usr/share/doc/ifenslave/examples/two_hotplug_ethernet
does not - the sla
Hi,
* Fabio Augusto De Muzio Tobich [210502 17:17]:
> Sorry, forgot to say that I intend to do this NMU in 5 days in DELAYED/10.
Might make sense to just go ahead.
Chris
(Replying to the bug only, as its not relevant for d-boot...)
* Ritesh Raj Sarraf [210515 17:32]:
> Time is pressing and I'm wondering what best to do here. I certainly do
> not care much for the iSCSI support in the installer. I didn't write or
> test that feature either.
[..]
> Maybe best to r
* Pino Toscano [210525 10:44]:
[..]
> Hence, it looks to me it would be a better idea to simply remove aewm
> from Debian.
I've cloned this as #989074 against src:aewm. Parties interested in
keeping aewm can reply there to indicate their commitments and also
keep aewm in bullseye...
Chris
ping to delay autoremoval until unblock bug is processed
* 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 start the pr
Package: vip-manager
Version: 1.0.1-3+b2
Severity: serious
Dear Maintainer,
thanks for maintaining the vip-manager package.
I've noticed that the service file
/lib/systemd/system/vip-manager.service uses options with one dash
(ex: `-ip=a.b.c.d`), but the vip-manager binary expects two dashes
(`-
Hi,
it appears not only have the numbers of dashes changed, but also the
actual parameter names.
In the current service file, I see:
ExecStart=/usr/bin/vip-manager -ip="${VIP_IP}" -iface="${VIP_IFACE}"
-key="${VIP_KEY}" -host="${VIP_HOST}" -type="${VIP_TYPE}"
-endpoint="${VIP_ENDPOINT}" -mask="
Hi Boyuan Yang,
* Boyuan Yang [200504 09:03]:
> Unfortunately yaml-cpp currently FTBFS on mipsel architecture. Build logs
> indicate that it might be caused by the exhaustion of memory:
[..]
> as: out of memory allocating 7161456 bytes after a total of 573444096 bytes
[..]
> I'm not sure what's t
Control: severity -1 important
Control: tags -1 + upstream
Hi Mark Hindley,
thanks for your report. See below.
* Mark Hindley [200505 13:27]:
> Unfortunately the testsuite fails when building in a pbuilder/cowbuilder
> chroot. In particular misc/fallocate and misc/mountpoint.
>
> The issues ap
* Ivo De Decker :
> On Thu, May 28, 2020 at 09:34:18AM -0700, Vagrant Cascadian wrote:
> > I *think* they are now no remaining depends or build-depends on
> > automake-1.15, seems like it could be removed now?
>
> dak rm seems to agree, so I added a testing removal hint (and upgraded this
> bug so
Hi,
* Paul Gevers [210124 21:51]:
> Please do get in touch if we need to dive into this together. Or if you
> want to discuss this issue.
[..]
> + service pdns restart
> Job for pdns.service failed because the control process exited with
> error code.
> See "systemctl status pdns.service" and "j
I've uploaded a new revision showing journal output on restart.
Maybe that will help debugging this.
Also: it would be great if I could get email for test failures.
Chris
* Chris Hofstaedtler [210124 22:24]:
> I don't see why this would "just fail randomly". I don't think its a
> timing thing. Maybe this worker is weird in a different way.
Having now looked at the (not very granular) timestamps, it looks
like the 30sec "service d
* Chris Hofstaedtler [210125 09:30]:
> Lets see what the pdns-recursor 4.4.2-4 test run brings.
^^^
That should have been 4.4.2-3.
> Paul, can you expedite that test run? Possibly in a way it runs on
> the problematic worker?
Actually it already
I've uploaded a possible patch to experimental, to avoid introducing
new build failures on other archs.
Diff below.
diff -Nru
acpica-unix-20200925/debian/patches/0001-Add-in-basic-infrastructure-for-big-endian-support.patch
acpica-unix-20200925/debian/patches/0001-Add-in-basic-infrastructure-
Control: severity -1 normal
* Dmitry Bogatov [2019-09-11 16:15]:
> control: severity -1 +normal
That appears to have failed. Trying again, as a service :-)
Source: cpqarrayd
Version: 2.3.6
Severity: serious
Linux upstream has removed the "cciss" driver in 4.14-rc1. cpqarrayd
needs the cciss driver to function.
I imagine we shouldn't ship software that did not work with buster's
kernel in bullseye.
Chris
* Jonas Smedegaard :
> severity -1 normal
Not sure if the missing "Control:" was intentional, but just to be
sure I'm pointing out this did not work.
> > Marking as serious as Python 2.7 is EOL and
> > https://wiki.debian.org/Python/2Removal clearly says that packages are
> > not allowed to rel
Hello Timo,
* Paul Gevers :
> On Thu, 18 Feb 2021 10:26:44 + Simon McVittie wrote:
> > On Mon, 18 Jan 2021 at 11:27:35 +, Simon McVittie wrote:
> > https://salsa.debian.org/xorg-team/vulkan/glslang/-/merge_requests/4
> >
> > (Updated patches attached, if you prefer the BTS.)
>
> Can we
Control: severity -1 important
* Lyndon Brown [210308 22:09]:
> # set severity to grave since it appears that the package is completely
> # broken currently.
> severity 983203 grave
"completely broken" appears to be a gross overstatement. The
firewalld integration might be broken - and I agree i
Control: severity -1 important
* Rob Browning [210403 00:45]:
> Andreas Henriksson writes:
>
> > Thanks for this info, it made it much easier to know where to look for
> > the problem which is caused by having emacs installed in the build
> > environment (which it isn't in a clean buildd chroot
Hello Christian,
* Christian Marillat [210405 15:26]:
> This package fail to install/build with :
>
> $ sudo apt-get dist-upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
Pinging this bug to avoid autoremoval, before migration of a fixed
package could happen.
One would hope the autoremovals logic would take care of such
things, but apparently not.
Chris
Control: found -1 2.9.15.1-2
Hi,
it appears this conffile handling problem is caused by a not good
enough attempt to move the old conffile /etc/cron.daily/5snort to
/etc/cron.daily/snort-common.
This was introduced in version 2.9.15.1-2 commit 8780db8c, to
snort-common.preinst:
+# renam
Hello Julian,
* Debian Bug Tracking System [201109 22:41]:
> This is an automatic notification regarding your Bug report
> which was filed against the greylistd package:
>
> #948706: greylistd: python3 version fails to start - conversion from python2
> very broken
...
> Changed-By: Julian Gilbe
* Paul Gevers [210125 22:18]:
> I don't have easy control over on which worker a job gets run. Unless I
> start it manually on the worker, but then there are no logs.
>
> I went ahead and did that anyways, find the data attached.
Thanks for doing that.
The log repeats these messages over and ov
Hi Paul,
* Paul Gevers [210128 09:05]:
> On 27-01-2021 23:00, Chris Hofstaedtler wrote:
> > Maybe it's best to start diffing the system configuration of the
> > ppc64el workers, given the other one works?
>
> Point being is that we manage our workers with chef. On th
* Helmut Grohne :
> On Fri, Aug 07, 2020 at 12:28:17PM +0200, Stefan Bühler wrote:
> > I think fixing libgamin0.shlibs and dropping fam from the archives is
> > the smoothest path to fixing this mess.
>
> Well, yeah. Removing fam removes the whole mess of compatibility.
#966273 has become RM: fa
Source: varmon
Version: 1.2.1-1
Severity: serious
Julien Danjou is no longer a Debian Developer, and
his mail address has started bouncing.
Someone will need to take care of this package.
Chris
You wrote:
> On 2/7/21 2:00 PM, Sebastian Ramacher wrote:
[..]
> I previously thought that libburnia is already being used by all relevant
> packages
> and that cdrkit is required only for mkisofs, in particular for creating ISO
> images with a HFS (not HFS+) filesystem.
That was also my vague un
Control: severity -1 normal
Given lack of feedback, no useful backtrace and that we have many
newer versions by now, I'm downgrading severity of this bug for now.
Chris
Control: severity -1 normal
* Diane Trout [210207 17:10]:
> I was looking through Debian release-critical bugs and saw this report
> that no one had followed up on. Evolution 3.38.2 is working for me and
> I was wondering if you were still having trouble.
Given there was no feedback and its gene
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/89
Control: severity -1 normal
This isn't a code bug, but a limitation of a proprietary service,
which we have no influence over. Given Evolution can be used with
other services and not just Gmail, it's certainly
Hi Felix,
friendly ping here, are you planning to fix this for bullseye?
* Felix Lechner [210207 17:20]:
> I would like to make sure any new module requirements are also
> compatible with systems booting in legacy BIOS mode.
While that's great, adding the module to the initramfs would at
least
> /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no
> acceptor (port is in use or requires root privileges) (RuntimeError)
Please explain what "IPv6-only buildd" actually means. How can one
reproduce this?
Chris
Package: telnetd
Version: 0.17-41.2
Severity: serious
Hi,
telnetd from netkit appears to have multiple problems, which make me
think we shouldn't ship it:
1) open bug #974428, causes telnetd to crash, remotely triggerable
2) possibly unpatched exploit here: https://www.exploit-db.com/exploits/48
Control: tags -1 + unreproducible moreinfo
Hi,
* Adrian Bunk [210207 18:14]:
> On Sun, Feb 07, 2021 at 06:30:20PM +0100, Chris Hofstaedtler wrote:
> > > /usr/lib/ruby/vendor_ruby/eventmachine.rb:532:in `start_tcp_server': no
> > > acceptor (port is in use o
Control: found -1 2.1.4-1
Control: tags -1 - unreproducible
* Chris Hofstaedtler [210207 18:19]:
> Thanks. However that info appears outdated, as on a current Debian
> unstable, I always get a `lo` interface with 127.0.0.1 and ::1
> bound. The tests want 127.0.0.1, so that works.
>
* Robert Nelson [210207 18:23]:
> I fixed this locally in our BeagleBoard.org Debian Repo with this quick patch:
> -java -Xmx64m -jar $JAR -storepass "$storepass"
> +java -Xmx64m -XX:-AssumeMP -jar $JAR -storepass "$storepass"
If this helps, someone please explain why this is not
Hi Logan,
* Logan Rosen [210207 18:53]:
> In Ubuntu, the attached patch was applied to achieve the following:
>
> * d/p/gcc-10.patch: Fix FTBFS with GCC 10.
Thanks for the patch. It appears _our_ GCC 10 also needs -fcommon in
CFLAGS. Not sure why it works for you without that.
Chris
Hello Heinrich,
I'm going to upload upstream's fix. Maybe you can give it a try.
Best,
Chris
Hi Helmut,
* Helmut Grohne [210207 19:50]:
> An arch-only build (but not a full build) of nghttp2 seems to reliably
> fail at test util_localtime_date:
[..]
> Since reproducible only performs full builds, it doesn't see this issue.
> Likewise crossqa skips tests and does not see it either. I don'
Hello Paul,
Hello knot-resolver Maintainers,
* Paul Gevers [210207 19:52]:
> With a not so recent change (beginning 2020) somewhere outside your
> package the autopkgtest of your package started to fail. I copied some
> of the output at the bottom of this report. Can you please investigate
> the
* Eduard Bloch [210208 00:43]:
> > Could you make an upload to DELAYED instead of further waiting?
>
> I am no longer waiting, today is timeout day. Will use 7-DAY DELAYED
> queue, should be appropriate.
That upload somehow did not make it into the archive?
Chris
Hi,
* Debian Bug Tracking System [210213 14:48]:
> #980580: ruby-ruby2ruby: FTBFS: ERROR: Test "ruby2.7" failed: RuntimeError:
> unknown arg type nil
have you noticed the autopkgtest failures on all archs?
https://tracker.debian.org/pkg/ruby-ruby2ruby
https://ci.debian.net/data/autopkgtest/te
1 - 100 of 697 matches
Mail list logo
