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 a
On Mar 14, Aurelien Jarno wrote:
> The binaries should probably be moved to a different package like
> kmod-udeb, as they conflict with busybox-udeb. Right now the kmod ones
> are used, but it depends on the unpack order.
Good to know after 8 years! Should I bother at all building a kmod-udeb
if
On Mar 15, John Paul Adrian Glaubitz wrote:
> Do you have a patch handy, then I'll fix the package manually for the time
> being for ia64 only?
Just edit debian/patch_libtool.
Let me know if it works and I will apply the change.
--
ciao,
Marco
signature.asc
Description: PGP signature
On 3/14/20 5:19 PM, James Clarke wrote:
> This is just the opposite of #947606; ia64 is meant to have libcrypt.so.1, not
> libcrypt.so.1.1 like alpha, and so that change needs to be reverted. See [1]
> for an old glibc build log to demonstrate the correct name (and note that,
> unlike alpha, sysdep
> please don't remove it yet.
> I started porting it to Python 3 some time ago and plan to finish
> that in the next weeks.
please keep in mind there's nothing wrong in removing the package
as-is now and re-introduce it later on when it's been ported to
python3.
but anyways, ok we'll wait, but i'
> I tried a test build with llvm-8 and -9 and it failed. There have been
> no releases since March 2019,
>
> but there is very active development as flang is being merged into the
> official llvm project.
>
> There have been no tags since, but I will see if I can build/test head
> of tree against l
Processing commands for cont...@bugs.debian.org:
> clone 953562 -1
Bug #953562 [libcrypt1] libcrypt1 should ship file in /usr, Replaces is useless
Bug 953562 cloned as bug 953958
> retitle -1 libcrypt1: Wrong soname on ia64
Bug #953958 [libcrypt1] libcrypt1 should ship file in /usr, Replaces is us
Processing commands for cont...@bugs.debian.org:
> found 953952 9-3
Bug #953952 [kmod] kmod: libkmod2-udeb contains binary instead of libraries
Marked as found in versions kmod/9-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953952: https://bugs.debian.org/cg
Processing commands for cont...@bugs.debian.org:
> clone 953562
Unknown command or malformed arguments to command.
> retitle 953562 libcrypt1 should ship file in /usr, Replaces is useless
Bug #953562 [libcrypt1] libcrypt1: Wrong soname on ia64
Changed Bug title to 'libcrypt1 should ship file in /u
Your message dated Sat, 14 Mar 2020 19:34:56 -0400
with message-id <2113783.URg3d3lheC@l5580>
and subject line Closing - probably local configuration error
has caused the Debian Bug report #949733,
regarding python-pip: 'pip install' don't work for python2 in Debian10
to be marked as done.
This me
Control: tag -1 pending
Hello,
Bug #938027 in python-pip 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/python-team/modules/python-pip/-/commit/2bdf00b2a8327ee
Processing commands for cont...@bugs.debian.org:
> tags 938027 + pending
Bug #938027 [src:python-pip] python-pip: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938027: https://bugs.debian.org/cgi-bin/bugrepor
Processing control commands:
> tag -1 pending
Bug #938027 [src:python-pip] python-pip: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #938027 to the same tags previously set
--
938027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938027
Debian Bug Tracking System
Cont
Your message dated Sat, 14 Mar 2020 22:23:39 +
with message-id
and subject line Bug#953158: fixed in sdpa 7.3.14+dfsg-1
has caused the Debian Bug report #953158,
regarding sdpa: hardcoded old mumps-seq dependency
to be marked as done.
This means that you claim that the problem has been dealt
Package: kmod
Version: 26+20191223-1
Severity: serious
Tags: d-i
Justification: Policy 8.6.4
The libkmod2 shlibs file contains the following entry:
| libkmod 2 libkmod2 (>= 26+20191223)
| udeb: libkmod 2 libkmod2-udeb (>= 26+20191223)
It means that libkmod.so.2 is supposed to be provided by libk
Your message dated Sat, 14 Mar 2020 22:23:31 +
with message-id
and subject line Bug#938410: fixed in rpm 4.14.2.1+dfsg1-1.1
has caused the Debian Bug report #938410,
regarding rpm: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Hi Valentin,
On 14-03-2020 23:02, Valentin Vidić wrote:
> On Sat, Mar 14, 2020 at 10:55:29PM +0100, Paul Gevers wrote:
>> Can you rephrase your question, I don't understand what you're asking.
>> Everything I can provide you is already available from ci.debian.net.
>
> Right, so when the test tim
On Sat, Mar 14, 2020 at 10:55:29PM +0100, Paul Gevers wrote:
> Can you rephrase your question, I don't understand what you're asking.
> Everything I can provide you is already available from ci.debian.net.
Right, so when the test timeouts it hangs on something but this is not
visible in the logs o
Control: found -1 3.1.1+cvs20050801-31
Control: tag -1 sid bullseye
Hi Sandro,
On Sat, 14 Mar 2020 15:33:34 -0400 Sandro Tosi wrote:
> I believe this package should be removed:
please file the "should this package be removed?" bugs tagged
sid+bullseye (unless you want them removed from (old)sta
Hi Valentin,
On 14-03-2020 21:59, Valentin Vidić wrote:
> On Sat, Mar 14, 2020 at 09:25:33PM +0100, Paul Gevers wrote:
>> I copied the output at the bottom of this report. All the failing tests
>> that I inspected look like it.
>>
>> I'll put your package on the ci.d.n ignore list until this bug i
Processing control commands:
> found -1 3.1.1+cvs20050801-31
Bug #953942 [jack] jack: should this package be removed?
Marked as found in versions jack/3.1.1+cvs20050801-31.
> tag -1 sid bullseye
Bug #953942 [jack] jack: should this package be removed?
Added tag(s) sid and bullseye.
--
953942: ht
I have the same problem too.
Anyway I found the following report:
https://gitlab.gnome.org/GNOME/gimp/issues/4490
I tried to delete the file:
/usr/lib/gimp/2.0/plug-ins/pagecurl/pagecurl
and Gimp seems to work correctly.
Regards,
Stefano
On Saturday, March 14 2020, Andreas Tille wrote:
> On Fri, Mar 13, 2020 at 11:09:31PM +0100, Paul Gevers wrote:
>>
>> raise RuntimeError(('Could not find drmaa library. Please specify
>> its ' +
>> RuntimeError: Could not find drmaa library. Please specify its full
>> path using the environ
On Sat, Mar 14, 2020 at 09:25:33PM +0100, Paul Gevers wrote:
> I copied the output at the bottom of this report. All the failing tests
> that I inspected look like it.
>
> I'll put your package on the ci.d.n ignore list until this bug is fixed.
Ok, but would it be possible to get a process list w
Control: severity -1 important
Hi,
Hmm, it seems it was slightly too quick. There are runs where the
package installs correctly, so it seems this is related to the environment.
Paul
signature.asc
Description: OpenPGP digital signature
Processing control commands:
> severity -1 important
Bug #953946 [rabbitmq-server] rabbitmq-server fails to install on arm64 (in lxc)
Severity set to 'important' from 'serious'
--
953946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953946
Debian Bug Tracking System
Contact ow...@bugs.debia
Package: rabbitmq-server
Version: 3.7.18-1
Severity: serious
X-Debbugs-CC: de...@packages.debian.org
Control: affects -1 debci
Justification: fails to install
Dear maintainer,
As part of the autopkgtest of debci, rabbitmq-server is installed.
However, the test fails on arm64 because the installat
Processing control commands:
> affects -1 debci
Bug #953946 [rabbitmq-server] rabbitmq-server fails to install on arm64 (in lxc)
Added indication that 953946 affects debci
--
953946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953946
Debian Bug Tracking System
Contact ow...@bugs.debian.org
As far as I know, an XIO error means the X server dropped the connection to the
xscreensaver client. So either the X server itself crashed, or it decided to
disconnect xscreensaver for some unknown reason.
If the client had done something wrong, X11-protocol-wise, this would have been
a more v
Your message dated Sat, 14 Mar 2020 20:45:39 +
with message-id
and subject line Bug#953866: fixed in openclipart 1:0.18+dfsg-16
has caused the Debian Bug report #953866,
regarding openclipart: please add a explicit build-dependency on
libreoffice-core (FTBFS: /usr/lib/libreoffice/program/geng
Processing commands for cont...@bugs.debian.org:
> # unconfuse the bts (found+fixed in the same version)
> notfound 930893 1.12.0-1
Bug #930893 [augeas-lenses] augeas-lenses: dovecot lens cannot parse default
/etc/dovecot/conf.d/10-mail.conf
No longer marked as found in versions augeas/1.12.0-1.
Source: crmsh
Version: 4.1.0-4
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky timeout
Dear maintainer(s),
I am currently going through the list [1] of packages that time out on
our ci.debian.net infrastructure. crmsh
Your message dated Sat, 14 Mar 2020 20:10:56 +
with message-id
and subject line Bug#951933: fixed in igraph 0.8.0-1
has caused the Debian Bug report #951933,
regarding igraph: FTBFS: ld: cannot find -llzma
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Daniel Shahaf wrote on Sat, 14 Mar 2020 19:57 +00:00:
> ...
Sorry for the noise! I typo'd the bug number in the To: header ☹
Source: chake
Version: 0.20-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression timeout
Dear maintainers,
The autopkgtest of your package recently started to time out after 2:47
hours. I copied some of the output at the bottom of this
Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00:
> - ::
> -
> - /closes:\s*(?:bug)?\#?\s?\d+(?:,\s*(?:bug)?\#?\s?\d+)*/i
> -
> + All of the bug numbers listed must be given on the same physical line
> + as the word ``closes:``.
Is this newly-added sentence correct?
Whether it cor
Your message dated Sat, 14 Mar 2020 19:49:45 +
with message-id
and subject line Bug#953703: fixed in klog 0.9.9.1-1
has caused the Debian Bug report #953703,
regarding src:klog: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 14 Mar 2020 19:49:45 +
with message-id
and subject line Bug#948911: fixed in klog 0.9.9.1-1
has caused the Debian Bug report #948911,
regarding klog: FTBFS on mipsel: {standard input}:107582: Error: branch out of
range
to be marked as done.
This means that you claim t
Processing commands for cont...@bugs.debian.org:
> retitle 952045 ruby-net-scp: FTBFS: ERROR: Test "ruby2.7" failed
Bug #952045 {Done: Antonio Terceiro } [src:ruby-net-scp]
ruby-net-scp: FTBFS: ERROR: Test "ruby2.7" failed: Error:
test_upload_file_with_metacharacters_in_name_should_escape_remote
Processing commands for cont...@bugs.debian.org:
> block 949187 by 951944 948416 953940 952217 950858
Bug #949187 [release.debian.org] transition: python3.8
949187 was blocked by: 953316 953550 951899
949187 was not blocking any bugs.
Added blocking bug(s) of 949187: 951944, 948416, 950858, 952217
Package: jack
Severity: serious
Hello,
I believe this package should be removed:
* python2-only
* no upstream release since 2004 (!) or svn update since 2005 (!)
* it's keeping several python2 modules in debian that could be dropped if jack
is removed too
* several alternatives exist that are
Your message dated Sat, 14 Mar 2020 19:27:40 +
with message-id
and subject line Bug#953874: Removed package(s) from unstable
has caused the Debian Bug report #945740,
regarding syslog-nagios-bridge: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the probl
Source: igraph
Version: 0.8.0-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: ftpmas...@debian.org
debian/copyright on igraph is incomplete. Examples:
- src/drl_layout_3d.cpp (BSD-3)
- src/CHOLMOD/Modify/cholmod_rowdel.c (Timothy A. Davis)
Please verify the whole copyright status.
B
Source: breezy
Version: 3.0.2-4
Severity: serious
Tags: ftbfs bullseye sid
Hi Maintainer
Your package FTBFS when built with Python 3.8 [1].
Please find what I hope is the relevant part of the log below.
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/history/amd64/breezy.html
Your message dated Sat, 14 Mar 2020 19:17:09 +
with message-id
and subject line Bug#951329: fixed in user-mode-linux 4.19-1um-1+deb10u1
has caused the Debian Bug report #951329,
regarding FTBFS in buster with linux-source-4.19 4.19.98-1
to be marked as done.
This means that you claim that the
Your message dated Sat, 14 Mar 2020 19:17:10 +
with message-id
and subject line Bug#830726: fixed in xtrlock 2.8+deb10u1
has caused the Debian Bug report #830726,
regarding xtrlock: CVE-2016-10894: xtrlock does not block multitouch events
to be marked as done.
This means that you claim that t
Your message dated Sat, 14 Mar 2020 18:48:48 +
with message-id
and subject line Bug#949189: fixed in golang-github-prometheus-common
0+git20181119.b36ad28-1+deb10u1
has caused the Debian Bug report #949189,
regarding golang-github-prometheus-common FTBFS after 2019-07-13
to be marked as done.
Your message dated Sat, 14 Mar 2020 18:19:43 +
with message-id
and subject line Bug#949887: fixed in munin 2.0.57-1
has caused the Debian Bug report #949887,
regarding munin autopkgtest failure for sysvinit based tests
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 14 Mar 2020 18:19:11 +
with message-id
and subject line Bug#953359: fixed in debian-edu 2.11.13
has caused the Debian Bug report #953359,
regarding education-menus: missing Breaks+Replaces: education-tasks (<< 2.11.12)
to be marked as done.
This means that you claim th
Your message dated Sat, 14 Mar 2020 18:04:11 +
with message-id
and subject line Bug#950374: fixed in apertium-en-es 0.8.0~r57502-5
has caused the Debian Bug report #950374,
regarding apertium-en-es FTBFS with apertium 3.6.1
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 953880 grave
Bug #953880 [gimp] gimp: segmentation fault on startup
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953880: https://bugs.debian.org/cgi-bin/bugrepo
Source: sinntp
Version: 1.6-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Your package was removed from testing some time ago. To migrate back,
the autopkgtest needs to pass, but unfortunately, it doesn't.
I
Source: ragout
Version: 2.2+ds-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package ragout, great.
However, it fails. Currently this failure is blocking the migrat
On Sat, 14 Mar 2020 21:53:11 +0530 Pirate Praveen <
prav...@onenetbeyond.org> wrote:
> I think this was introduced by libsass/ruby-sassc updates.
Just confirmed, downgrading libsass to 3.6.1 fixed the issue
Get it from
http://snapshot.debian.org/package/libsass/3.6.1-1/
Source: uc-echo
Version: 1.12-14
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package uc-echo, great.
However, it fails on arm64. Currently this failure is blocking
Your message dated Sat, 14 Mar 2020 16:35:05 +
with message-id
and subject line Bug#951903: fixed in duktape 2.5.0-2
has caused the Debian Bug report #951903,
regarding duktape: d/copyright issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> found -1 ncbi-vdb/2.10.3+dfsg-1
Bug #953897 [src:ncbi-vdb, src:sra-sdk] ncbi-vdb breaks sra-sdk autopkgtest:
undefined symbol: vdb_mbedtls_md_setup
Marked as found in versions ncbi-vdb/2.10.3+dfsg-1.
> found -1 sra-sdk/2.9.3+dfsg-1
Bug #953897 [src:ncbi-vdb, src:sra
Source: ncbi-vdb, sra-sdk
Control: found -1 ncbi-vdb/2.10.3+dfsg-1
Control: found -1 sra-sdk/2.9.3+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of ncbi-v
Control: forwarded -1
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27267
On Mon, 9 Mar 2020 11:37:07 +0200 Dragos Jarca <
dragos.ja...@dynamicpuzzle.ro> wrote:
> Package: gitlab
> Version: 12.6.8-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Whe
Thanks Sven,
It's fixed, you can close the bug report.
Thanks :-)
Le sam. 14 mars 2020 à 11:49, Sven Joachim a écrit :
> Control: reassign -1 cpp-9
> Control: forcemerge 953806 -1
>
> On 2020-03-14 10:11 +0100, Berillions wrote:
>
> > Package: libc6-dev
> > Version: 2.30-2
> >
> > Hello,
> >
>
Processing control commands:
> retitle -1 libcrypt1: Wrong soname on ia64
Bug #953562 [libcrypt1] libcrypt1 should ship file in /lib, Replaces is useless
Changed Bug title to 'libcrypt1: Wrong soname on ia64' from 'libcrypt1 should
ship file in /lib, Replaces is useless'.
--
953562: https://bug
Control: retitle -1 libcrypt1: Wrong soname on ia64
On 14 Mar 2020, at 14:20, John Paul Adrian Glaubitz
wrote:
>
> Package: libcrypt1
> Version: 1:4.4.15-1
> Followup-For: Bug #953562
> User: debian-i...@lists.debian.org
> Usertags: ia64
>
> Hello!
>
> This actually causes issues on ia64 now:
Source: golang-github-hashicorp-terraform-svchost
Version: 0.0~git20191119.d2e4933-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package
golang-github-hashicorp-ter
Package: libvirt-daemon
Version: 6.0.0-2
Severity: grave
Justification: renders package unusable
Updating to 6.0.0-2 hangs indefinitely:
...
Setting up libvirt-daemon-system (6.0.0-2) ...
Installing new version of config file
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper ...
Installing new versi
Source: prometheus-node-exporter-collectors
Version: 0+git20200110.fc91c86-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package
prometheus-node-exporter-collectors
Hi Sandro,
please don't remove it yet.
I started porting it to Python 3 some time ago and plan to finish
that in the next weeks.
Kind regards,
Reiner
signature.asc
Description: PGP signature
Hi Andreas,
On 14-03-2020 14:30, Andreas Tille wrote:
> Hi Paul,
[...]
> Any help would be welcome
I can't help you with this.
Paul
signature.asc
Description: OpenPGP digital signature
Processing commands for cont...@bugs.debian.org:
> tags 952253 + pending patch
Bug #952253 [src:oneliner-el] oneliner-el: FTBFS: Malformed UTF-8 character
(fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3387.
Added tag(s) patch and pending.
> thanks
Stopping processing here.
Please con
tags 952253 + pending patch
thanks
Hi.
We need to use UTF-8 encoding instead of EUC-JP for Japanese texi
file. I'll fix this bug and upload a new package soon.
Thanks.
On Sun, 23 Feb 2020 22:22:00 +0900,
Lucas Nussbaum wrote:
>
> Source: oneliner-el
> Version: 0.3.6-8
> Severity: serious
On Mar 14, John Paul Adrian Glaubitz wrote:
> This actually causes issues on ia64 now:
Why do you believe that this is the cause?
> /usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot
> open shared object file: No such file or directory
Is this cured by manually running l
Package: libcrypt1
Version: 1:4.4.15-1
Followup-For: Bug #953562
User: debian-i...@lists.debian.org
Usertags: ia64
Hello!
This actually causes issues on ia64 now:
Setting up libc6.1:ia64 (2.30-2) ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open
shared object f
Your message dated Sat, 14 Mar 2020 15:03:28 +0100
with message-id <158419460883.1376083.5924019944724337...@auryn.jones.dk>
and subject line Re: Bug#952128: janus: FTBFS: build-dependency not
installable: rollup
has caused the Debian Bug report #952128,
regarding janus: FTBFS: build-dependency no
Control: blocked -1 by 949204
Control: tags -1 help
Control: retitle -1 cannot allocate memory in static TLS block
Hi Paul,
On Fri, Mar 13, 2020 at 11:09:31PM +0100, Paul Gevers wrote:
>
> raise RuntimeError(('Could not find drmaa library. Please specify
> its ' +
> RuntimeError: Could not find drmaa library. Please sp
Processing control commands:
> tags -1 help
Bug #953832 [src:drmaa] drmaa: autopkgtest failure: RuntimeError: Could not
find drmaa library
Added tag(s) help.
> retitle -1 cannot allocate memory in static TLS block
Bug #953832 [src:drmaa] drmaa: autopkgtest failure: RuntimeError: Could not
find d
Dear Gabriele,
On 14-03-2020 12:02, Gabriele wrote:
> Many thanks for your email. As I have only recently started managing
> packages on Debian, I am not sure if there is anything that I have to do
> about this at all. If I understand correctly, the issue here is caused
> by the fact that the late
Your message dated Sat, 14 Mar 2020 12:34:41 +
with message-id
and subject line Bug#953270: fixed in libusrsctp 0.9.3.0+20200312-1
has caused the Debian Bug report #953270,
regarding libusrsctp: CVE-2019-20503
to be marked as done.
This means that you claim that the problem has been dealt wit
Your message dated Sat, 14 Mar 2020 12:35:49 +
with message-id
and subject line Bug#947006: fixed in libvirt 6.0.0-2
has caused the Debian Bug report #947006,
regarding libvirt: autopkgtest always fails and now started to time out
regularly
to be marked as done.
This means that you claim tha
David Bremner writes:
> Paulo Matos writes:
>
>> Upstream issue reference for:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948789
>> Mailing list information:
>> https://groups.google.com/d/msg/racket-dev/o631-azv-5g/r9Ct1H_KDAAJ
>
> I'm not sure if this is a surprise or not, but it l
Processing commands for cont...@bugs.debian.org:
> severity 953875 critical
Bug #953875 [src:runit] runit - default installation wants to remove systemd
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953875: https://bugs.d
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 the
Processing control commands:
> severity -1 normal
Bug #953875 [src:runit] runit - default installation wants to remove systemd
Severity set to 'normal' from 'critical'
--
953875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953875
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Source: runit
Version: 2.1.2-35
Severity: critical
An installation attempt on a default system (with recommends enabled) of
runit wants to replace the installed init:
| $ sudo apt install runit
| Reading package lists... Done
| Building dependency tree
| Reading state information... Done
| The fo
Dear Paul
Many thanks for your email. As I have only recently started managing
packages on Debian, I am not sure if there is anything that I have to do
about this at all. If I understand correctly, the issue here is caused by
the fact that the latest sources (which are of version 1.0.0) are no lon
Processing commands for cont...@bugs.debian.org:
> severity 944619 serious
Bug #944619 [bitwise] bitwise: bogus hardcoded dependencies on libncurses5 and
libreadline5
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
944619:
Processing control commands:
> reassign -1 cpp-9
Bug #953867 [libc6-dev] error when compiling wine
Bug reassigned from package 'libc6-dev' to 'cpp-9'.
No longer marked as found in versions glibc/2.30-2.
Ignoring request to alter fixed versions of bug #953867 to the same values
previously set
> f
Your message dated Sat, 14 Mar 2020 09:36:17 +
with message-id
and subject line Bug#952045: fixed in ruby-net-scp 2.0.0-2
has caused the Debian Bug report #952045,
regarding ruby-net-scp: FTBFS: ERROR: Test "ruby2.7" failed: Error:
test_upload_file_with_metacharacters_in_name_should_escape_re
Your message dated Sat, 14 Mar 2020 09:05:35 +
with message-id
and subject line Bug#953846: fixed in psychopy 2020.1.3+dfsg-2
has caused the Debian Bug report #953846,
regarding psychopy: ships /usr/lib/python3/dist-packages/packaging/__init__.py
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> retitle 952347 /usr/lib/libreoffice/program/gengal.bin: symbol lookup error:
> /usr/lib/libreoffice/program/gengal.bin: undefined symbol: _Z10getGlxPipev
> with libreoffice-core-nogui installed
Bug #952347 [libreoffice-dev] openclipart: FTBFS:
Your message dated Sat, 14 Mar 2020 08:57:08 +
with message-id
and subject line Bug#953316: fixed in volume-key 0.3.12-3.1
has caused the Debian Bug report #953316,
regarding volume-key: FTBFS with python3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 14 Mar 2020 08:56:55 +
with message-id
and subject line Bug#953826: fixed in r-cran-rprotobuf 0.4.15-2
has caused the Debian Bug report #953826,
regarding r-cran-rprotobuf: autopkgtest regression: cannot open file
'/usr/share/doc/r-cran-rprotobuf/tests/runUnitTests.R'
Processing commands for cont...@bugs.debian.org:
> severity 952347 important
Bug #952347 [libreoffice-dev] openclipart: FTBFS:
/usr/lib/libreoffice/program/gengal.bin: symbol lookup error:
/usr/lib/libreoffice/program/gengal.bin: undefined symbol: _Z10getGlxPipev
Severity set to 'important' from
Your message dated Sat, 14 Mar 2020 08:46:46 +
with message-id
and subject line Bug#949835: fixed in lirc 0.10.1-6.1
has caused the Debian Bug report #949835,
regarding lirc ftbfs with python 3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> forwarded 953863 https://trac.torproject.org/projects/tor/ticket/30882
Bug #953863 [python3-stem] python3-stem: "RuntimeError: dictionary keys changed
during iteration" with python 3.8
Set Bug forwarded-to-address to
'https://trac.torproject.org
Package: python3-stem
Version: 1.7.1-1.1
Severity: serious
Hi,
onioncircuits fails to start on current sid:
Traceback (most recent call last):
File "/bin/onioncircuits", line 657, in
app = OnionCircuitsApplication()
File "/bin/onioncircuits", line 633, in __init__
self.connect_contr
Processing commands for cont...@bugs.debian.org:
> close 949941 5.132-1
Bug #949941 [src:byobu] byobu build depends on the removed pep8 transitional
package
The source 'byobu' and version '5.132-1' do not appear to match any binary
packages
Marked as fixed in versions byobu/5.132-1.
Bug #949941
Hi,
please transfer natsort from debian to python-team/modules,
see #950221 for background.
Thanks in advance
Adrian
Control: tags 953770 + patch
Control: tags 953770 + pending
Dear maintainer,
I've prepared an NMU for bluez (versioned as 5.50-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
I decided to not explicitly change the default set for the new
configuration
Processing control commands:
> tags 953770 + patch
Bug #953770 [src:bluez] bluez: CVE-2020-0556
Added tag(s) patch.
> tags 953770 + pending
Bug #953770 [src:bluez] bluez: CVE-2020-0556
Added tag(s) pending.
--
953770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953770
Debian Bug Tracking S
Your message dated Sat, 14 Mar 2020 07:49:09 +
with message-id
and subject line Bug#925753: fixed in libneo4j-client 2.2.0-1.1
has caused the Debian Bug report #925753,
regarding libneo4j-client: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt
1 - 100 of 103 matches
Mail list logo
