Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

24.12.2018 6:00, Andreas Beckmann wrote: Followup-For: Bug #916279 Control: found -1 1:3.1+dfsg-2 Hi, you are missing a Breaks: qemu-system-data (<< 1:3.1+dfsg-1~) to match the Replaces, otherwise you are permitting partial upgrade/downgrade paths where files are disappearing whil dpkg consi

Bug#917210: revelation: Intent to remove from Debian

Source: revelation Version: 0.4.14-3 Severity: serious Tags: buster sid revelation was removed from Testing a year ago because it depends on gnome-python and libgnome. relevation is now one of the blockers for completing the removal of those unmaintained libraries from Debian. Therefore, I intend

Bug#790584: gjots2: depends on python-gnome2 which is deprecated

Control: tags -1 +pending I have uploaded gjots2 3.0.2-0.1 to the DELAYED/15 queue. Please let me know if I should speed up or slow down this upload. I submitted my packaging to https://github.com/leggewie-DM/gjots2/pulls Thanks, Jeremy Bicha

Processed: Re: gjots2: depends on python-gnome2 which is deprecated

Processing control commands: > tags -1 +pending Bug #790584 [src:gjots2] gjots2: depends on python-gnome2 which is deprecated Added tag(s) pending. -- 790584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917124: udev 240-1 break my system too

On 12/24/18 12:58 PM, John Wong wrote: > Yes, udev 240-1 break my lvm2 system. > Hi, replace /lib/systemd/systemd-udevd with udev version 239's (/lib/systemd/systemd-udevd), then update-initramfs -u. I can boot my system again. -- Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80A

Bug#917124: udev 240-1 break my system too

Yes, udev 240-1 break my lvm2 system. -- Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#915575: marked as done (libyaml-cpp-dev: ships /usr/include/{gmock,gtest}/*)

Your message dated Mon, 24 Dec 2018 04:51:16 + with message-id and subject line Bug#915575: fixed in yaml-cpp 0.6.2-2 has caused the Debian Bug report #915575, regarding libyaml-cpp-dev: ships /usr/include/{gmock,gtest}/* to be marked as done. This means that you claim that the problem has be

Processed: RM: xword -- RoQA; depends on unmaintained gnome-python-desktop

Processing control commands: > severity -1 normal Bug #913852 [src:xword] xword: Intent to remove from Debian Severity set to 'normal' from 'serious' > tags -1 -sid -buster Bug #913852 [src:xword] xword: Intent to remove from Debian Removed tag(s) sid. Bug #913852 [src:xword] xword: Intent to remo

Bug#913852: RM: xword -- RoQA; depends on unmaintained gnome-python-desktop

Control: severity -1 normal Control: tags -1 -sid -buster Control: retitle -1 RM: xword -- RoQA; depends on unmaintained gnome-python-desktop Control: reassign -1 ftp.debian.org Please remove xword from Debian. Thank you, Jeremy Bicha

Bug#881506: xul-ext-gnome-keyring doesn't work with firefox >=57

On Mon, Nov 19, 2018 at 5:20 PM Moritz Mühlenhoff wrote: > On Mon, Nov 19, 2018 at 07:22:11AM -0500, Jeremy Bicha wrote: > > > Given that Xul is still supported in Thunderbird, let maybe drop the > > > support for > > > Firefox/Iceweasel (with a NOTE telling people how to migrate their > > > exi

Processed: RM: liblunar -- RoQA; unused library, depends on pygtksourceview

Processing control commands: > severity -1 normal Bug #914111 [src:liblunar] liblunar: Intent to remove from Debian Severity set to 'normal' from 'serious' > tags -1 -sid -buster Bug #914111 [src:liblunar] liblunar: Intent to remove from Debian Removed tag(s) sid. Bug #914111 [src:liblunar] liblun

Bug#914111: RM: liblunar -- RoQA; unused library, depends on pygtksourceview

Control: severity -1 normal Control: tags -1 -sid -buster Control: retitle -1 RM: liblunar -- RoQA; unused library, depends on pygtksourceview Control: reassign -1 ftp.debian.org Please remove liblunar from Debian. Thank you, Jeremy Bicha

Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted

After downgrading udev and libudev1 to 239-15, swap volume is mounted properly on boot. "lvm2-activation-generator: lvmconfig failed" is still produced on boot, but only once and seems not to break anything. Thanks.

Bug#897806: lmms: ftbfs with GCC-8

PS: My email sent to *@jasp.net keeps bouncing; I received 550 The message does not meet the trust level of one recipient at least See http://www.jasp.net/smtp/trust.xhtml Administrative prohibition I don't know if you could receive my email but at least you may view the archived version on https

Bug#897806: lmms: ftbfs with GCC-8

Hi Javier, > I asked for an upload two weeks ago. Are you referring to any request for upload in Debian? I couldn't find the place where you asked any upload in Debian, either on mentors.debian.net or https://bugs.debian.org/sponsorship-requests . Could you provide a reference to it, especially a

Bug#917058: marked as done (ocaml-migrate-parsetree FTBFS:)

Your message dated Mon, 24 Dec 2018 03:20:45 + with message-id and subject line Bug#917058: fixed in ocaml-migrate-parsetree 1.2.0-1 has caused the Debian Bug report #917058, regarding ocaml-migrate-parsetree FTBFS: to be marked as done. This means that you claim that the problem has been dea

Bug#913116: Needs to depend on chromium-sandbox

On Mon, Dec 17, 2018 at 4:40 AM Bastian Blank wrote: > > Since this can be used in place of chromium's setuid binary, my > > opinion is that the Depends relationship on chromium-sandbox is no > > longer required. > > Nope, at least if the package is supposed to work without admin > intervention. D

Bug#916279: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

Followup-For: Bug #916279 Control: found -1 1:3.1+dfsg-2 Hi, you are missing a Breaks: qemu-system-data (<< 1:3.1+dfsg-1~) to match the Replaces, otherwise you are permitting partial upgrade/downgrade paths where files are disappearing while dpkg considers everything correctly installed. And

Processed: Re: qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement

Processing control commands: > found -1 1:3.1+dfsg-2 Bug #916279 {Done: Michael Tokarev } [qemu-system-common] qemu-system-common: Overwrite /usr/share/doc-base/qemu-system-doc without declaring replacement Marked as found in versions qemu/1:3.1+dfsg-2; no longer marked as fixed in versions qem

Processed: retitle 915464 to debian-parl: Depends on broken Firefox addons, tagging 917068 ..., tagging 917082 ...

Processing commands for cont...@bugs.debian.org: > retitle 915464 debian-parl: Depends on broken Firefox addons Bug #915464 {Done: Jonas Smedegaard } [src:debian-parl] RM: mozvoikko -- RoQA; incompatible with newer firefox-esr versions Changed Bug title to 'debian-parl: Depends on broken Firefox

Processed: affects 917205

Processing commands for cont...@bugs.debian.org: > affects 917205 + src:openmpi Bug #917205 [dh-fortran-mod] dh-fortran-mod: must not act on arch:all packages Added indication that 917205 affects src:openmpi > thanks Stopping processing here. Please contact me if you need assistance. -- 917205:

Bug#917205: dh-fortran-mod: must not act on arch:all packages

Package: dh-fortran-mod Version: 0.7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects: src:openmpi Hi, during a test with piuparts I noticed the postrm snippets inserted by your package cause errors. >From the attached log (scroll to the bottom...): Purgi

Processed: Re: Bug#917202: lm-sensors: Ability to install both libsensors4 and libsensors5?

Processing control commands: > reassign -1 collectd Bug #917202 [lm-sensors] lm-sensors: Ability to install both libsensors4 and libsensors5? Bug reassigned from package 'lm-sensors' to 'collectd'. No longer marked as found in versions lm-sensors/1:3.5.0-3. Ignoring request to alter fixed version

Bug#917203: FTBFS on at least two architectures: test failure in the enigma algorithm

Package: src:libmcrypt Version: 2.5.8-3.3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I've been doing a full rebuild of the Debian archive, building all source packages targeting armel and armhf using arm64 hardware. We are plan

Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted

On Sun, 23 Dec 2018 15:58:50 +0100 Piotr Jurkiewicz wrote: On two machines running sid I observed errors during the upgrade to 2.03.01-2. One of these machines became practically unusable immediately after the update (disk IO operations became so slow that even closing aptitude took 2 minutes

Bug#916173: marked as done (granite-demo: crashes with missing io.elementary.desktop.wingpanel.datetime schema)

Your message dated Mon, 24 Dec 2018 00:07:51 + with message-id and subject line Bug#916173: fixed in granite 5.2.2-1 has caused the Debian Bug report #916173, regarding granite-demo: crashes with missing io.elementary.desktop.wingpanel.datetime schema to be marked as done. This means that yo

Bug#917200: pyside2: build-dependencies no longer satisfiable on mips64el.

Package: pyside2 Version: 5.11.2-1 Severity: serious It seems that patchelf has been removed on mips64el due to testsuite failures, but pyside2 still bulid-depends on it. So pyside cannot be built on mips64el anymore. Possible fixes (in roughly descending order of preferences) 1. Fix the tests

Bug#917199: pivy, unbuildable on mips* due to testsuite failures in patchelf.

Package: pivy Version: 0.6.4-1 Severity: serious pivy cannot be built on mips/mipsel because of a depedency on pyside2 which is not built on mips/mipsel pyside2 is not being built on those architectures due to a dependency on patchelf. patchelf is not currently building on mips* due to a tests

Bug#917197: nullmailer: tests/smtp-auth fails randomly on mips64el

Source: nullmailer Version: 1:2.2-2 Severity: serious Justification: ftbfs The mentioned tests seems to fail about 10-20% of the time. I'm not sure if it's really architecture specific, or just a race condition that didn't happen on the other buildd's. When it does fail the test 'Testing auth log

Bug#917195: FTBFS on mips(el): expected ‘dev_t *’ {aka ‘long long unsigned int *’} but argument is of type ‘long unsigned int *’

Source: systemd Version: 240-1 Severity: serious User: debian-m...@lists.debian.org Usertags: mipsel mips Forwarded: https://github.com/systemd/systemd/issues/11247 The latest upstream release of systemd fails to build on mips/mipsel with the following error message: [346/1708] cc -Isrc/core/2ac6

Bug#897806: lmms: ftbfs with GCC-8

I asked for an upload two weeks ago. smime.p7s Description: S/MIME cryptographic signature

Bug#916223: marked as done (moonshot-gss-eap: FTBFS against xmltooling 3)

Your message dated Sun, 23 Dec 2018 21:37:05 + with message-id and subject line Bug#916223: fixed in moonshot-gss-eap 1.0.1-4 has caused the Debian Bug report #916223, regarding moonshot-gss-eap: FTBFS against xmltooling 3 to be marked as done. This means that you claim that the problem has b

Processed: Re: [Pkg-fonts-devel] Bug#916948: fonts-hack FTBFS: Unable to execute ttfautohint on the Hack-Regular variant set

Processing control commands: > severity -1 normal Bug #916948 [src:fonts-hack] fonts-hack FTBFS: Unable to execute ttfautohint on the Hack-Regular variant set Severity set to 'normal' from 'serious' > tags -1 +unreproducible Bug #916948 [src:fonts-hack] fonts-hack FTBFS: Unable to execute ttfauto

Bug#916948: [Pkg-fonts-devel] Bug#916948: fonts-hack FTBFS: Unable to execute ttfautohint on the Hack-Regular variant set

Control: severity -1 normal Control: tags -1 +unreproducible Am Donnerstag, den 20.12.2018, 21:38 +0200 schrieb Adrian Bunk: > Warning: Option `-w G' is deprecated! Use option `-a qsq' instead > postbuild_processing/tt-hinting/Hack-Regular-TA.txt:3:1: invalid > glyph name (0x204) > uni0023 tou

Bug#867656: marked as done (ruby-mixlib-install: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: res = http.request(request))

Your message dated Sun, 23 Dec 2018 19:06:54 + with message-id and subject line Bug#867656: fixed in ruby-mixlib-install 3.11.7-1 has caused the Debian Bug report #867656, regarding ruby-mixlib-install: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: res = http.request(request) to be mark

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

On 23/12/2018 19:15, Michael Biebl wrote: Thanks for the info. Very interesting read . Learned a few things today. -- eric

Bug#917167: Fwd: Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Michael Biebl wrote: > For processes that are spawned by PID 1, the limits are set differently > though, so the unlimited rlimit for PID 1 should have no effect on other > processes. > > Problem is, pam_limits.so in Debian ships a custom patch, which reads > the limits from PID 1 and set those for

Processed: tagging 917167

Processing commands for cont...@bugs.debian.org: > tags 917167 - moreinfo Bug #917167 [systemd] systemd: 240 breaks kde (rakes ages to launch) Bug #917168 [systemd] systemd: fail to start kde after 240-1 upgrade Bug #917173 [systemd] systemd 240-1 breaks Plasma Removed tag(s) moreinfo. Removed tag

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Control: forcemerge -1 917168 917173 Control: severity -1 grave Am 23.12.18 um 18:27 schrieb Baptiste BEAUPLAT: > Dear maintainers, > > This issue seems related to #917168, feel free to merge it. > > For the 100% cpu, I think the problem is here in kinit: > > https://github.com/KDE/kinit/blob/m

Processed: Re: Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Processing control commands: > forcemerge -1 917168 917173 Bug #917167 [systemd] systemd: 240 breaks kde (rakes ages to launch) Bug #917168 [systemd] systemd: fail to start kde after 240-1 upgrade Severity set to 'critical' from 'important' Added tag(s) moreinfo. Bug #917173 [systemd] systemd 240-

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Dear maintainers, This issue seems related to #917168, feel free to merge it. For the 100% cpu, I think the problem is here in kinit: https://github.com/KDE/kinit/blob/master/src/kdeinit/kinit.cpp#L163 ```c /* * Clean up the file descriptor table by closing all file descriptors * that are sti

Bug#916764: marked as done (znc-backlog: overly strict dependency on znc?)

Your message dated Sun, 23 Dec 2018 17:50:46 + with message-id and subject line Bug#916764: fixed in znc-backlog 0.20180824-1 has caused the Debian Bug report #916764, regarding znc-backlog: overly strict dependency on znc? to be marked as done. This means that you claim that the problem has

Bug#917166: I can confirm that my machines and up in the same state

I upgraded two machines. Did not see any problem during the upgrade. But now both of the machines have problem booting. One I can get started by starting in recovery mode. The other boots anyway. But that machine I never boot into any GUI.

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

Hi, Simon McVittie (2018-12-23): > To be completely clear about the decision that Ian asked the technical > committee to overrule: > > In all debootstrap versions since 1.0.102, merged /usr is the default > (for all variants except --variant=buildd). This means that new > installations of Debian

Bug#917173: systemd 240-1 breaks Plasma

Sorry, the first message accidentally got sent while I was still writing it, intended full text below: Installing systemd 240-1 breaks plasma-workspace: xinit /usr/bin/startkde hangs with a black screen, with kdeinit5 stuck at 100% CPU usage. Attaching strace to kdeinit5 reveals that it's trying t

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Please provide a verbose debug log with precise error messages. No time to do that. I already wasted two hours today... It was just to warn people that this version of udev should have gone to experimental or receive more testing before deploying it... You have now tree bugs on the same sub

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

Package: davmail Version: 5.0.0.2801-2 Severity: serious Hello, unfortunately davmail fails to build from source with libjackrabbit-java 2.18.0. Long deprecated methods have been removed. Your package build-depends on a very old version of jackrabbit (2.4.3). See also the deprecated list that ex

Bug#917173: systemd 240-1 breaks Plasma

Package: systemd Version: 240-1 Severity: critical Installing systemd 240-1 breaks plasma-workspace: xinit /usr/bin/startkde hangs with a black screen, with kdeinit5 stuck at 100% CPU usage. Attaching strace to kdeinit5 reveals that it's trying to close bogus file descriptors: [..] close(39936688

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

On 23/12/2018 17:57, Michael Biebl wrote: Control: tags -1 + moreinfo Am 23.12.18 um 17:11 schrieb Eric Valette: Package: systemd Version: 240-1 Severity: critical Justification: breaks unrelated software After upgrading to 240 version, all my system started to take ages to boot. It seems rel

Processed: Re: Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Processing control commands: > tags -1 + moreinfo Bug #917167 [systemd] systemd: 240 breaks kde (rakes ages to launch) Added tag(s) moreinfo. -- 917167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Control: tags -1 + moreinfo Am 23.12.18 um 17:11 schrieb Eric Valette: > Package: systemd > Version: 240-1 > Severity: critical > Justification: breaks unrelated software > > After upgrading to 240 version, all my system started to take ages to boot. > It seems related to disk mapping first and

Bug#917171: FTBFS on all architectures

Package: src:haskell-language-python Version: 0.5.4-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=haskell-language-python shows current state - failed builds everywhere. Looking at logs, they're all showing 160 | parens (pretty (endRow span) <> comma <> pretty

Processed: notfound 915650 in 12~22-1

Processing commands for cont...@bugs.debian.org: > notfound 915650 12~22-1 Bug #915650 [src:openjdk-12] openjdk-12: don't release with Buster No longer marked as found in versions openjdk-12/12~22-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 915650: https://

Bug#867945: marked as done (moonshot-ui: Build-Depends on deprecated libgnome-keyring-dev)

Your message dated Sun, 23 Dec 2018 15:21:43 + with message-id and subject line Bug#867945: fixed in moonshot-ui 1.1.0+libsecret~1 has caused the Debian Bug report #867945, regarding moonshot-ui: Build-Depends on deprecated libgnome-keyring-dev to be marked as done. This means that you claim

Bug#917166: Errors on and after upgrade to 2.03.01-2, swap on lvm not mounted

Package: lvm2 Version: 2.03.01-2 Severity: grave On two machines running sid I observed errors during the upgrade to 2.03.01-2. One of these machines became practically unusable immediately after the update (disk IO operations became so slow that even closing aptitude took 2 minutes instead us

Bug#917071: marked as done (elpa-persp-projectile: byte compilation fails: make-variable-frame-local)

Your message dated Sun, 23 Dec 2018 14:44:44 + with message-id and subject line Bug#917071: fixed in perspective-el 2.2-1 has caused the Debian Bug report #917071, regarding elpa-persp-projectile: byte compilation fails: make-variable-frame-local to be marked as done. This means that you cla

Bug#916223: moonshot-gss-eap: FTBFS against xmltooling 3

> "Sebastian" == Sebastian Andrzej Siewior writes: Sebastian> On 2018-12-11 18:26:24 [-0500], Sam Hartman wrote: >> Fixing moonshot-gss-eap and getting a new moonshot-ui is next up >> for me for Debian weekend tasks. Sebastian> This means an upload from exp to unstable? I'm

Bug#917058: ocaml-migrate-parsetree FTBFS:

Hi Ralf, I've just pushed to salsa for a fix and update to the latest upstream version. I tested the update with autopkgtests against unstable-amd64 and unstable-mips, both passed. Would you review and upload? Best, Andy On Sat, Dec 22, 2018 at 9:00 AM Adrian Bunk wrote: > Source: ocaml-migrat

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 01:40 schrieb Michael Biebl: > Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies: >> Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed >> Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator >> failed. >> Dec 23 13:07:52 ripley systemd[376]: >> /lib

Processed: Patch for this bug

Processing control commands: > tag -1 +patch Bug #916875 [src:vm] vm: FTBFS with Emacs 26.1: Variable name missing after &optional Added tag(s) patch. -- 916875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#916875: Patch for this bug

control: tag -1 +patch Hello, Ubuntu has a fix: https://bugs.launchpad.net/vm/+bug/1763377 https://launchpadlibrarian.net/364804904/vm-emacs26.patch -- Sean Whitton signature.asc Description: PGP signature

Bug#914680: marked as done (libplplotada3: missing Breaks+Replaces: libplplotada2)

Your message dated Sun, 23 Dec 2018 14:11:19 + with message-id and subject line Bug#914680: fixed in plplot 5.14.0+dfsg-1~exp1 has caused the Debian Bug report #914680, regarding libplplotada3: missing Breaks+Replaces: libplplotada2 to be marked as done. This means that you claim that the pro

Bug#916714: marked as done (plplot FTBFS: Cannot find "usr/lib/*/plplot*/drivers/cairo.*")

Your message dated Sun, 23 Dec 2018 14:11:19 + with message-id and subject line Bug#916714: fixed in plplot 5.14.0+dfsg-1~exp1 has caused the Debian Bug report #916714, regarding plplot FTBFS: Cannot find "usr/lib/*/plplot*/drivers/cairo.*" to be marked as done. This means that you claim that

Bug#913504: marked as done (frog FTBFS with ICU 63.1)

Your message dated Sun, 23 Dec 2018 14:11:09 + with message-id and subject line Bug#913504: fixed in frog 0.15-1 has caused the Debian Bug report #913504, regarding frog FTBFS with ICU 63.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Processed: Re: [Pkg-emacsen-addons] Bug#917071: elpa-persp-projectile: byte compilation fails: make-variable-frame-local

Processing control commands: > reassign -1 elpa-perspective Bug #917071 [elpa-persp-projectile] elpa-persp-projectile: byte compilation fails: make-variable-frame-local Bug reassigned from package 'elpa-persp-projectile' to 'elpa-perspective'. No longer marked as found in versions persp-projectil

Bug#917071: [Pkg-emacsen-addons] Bug#917071: elpa-persp-projectile: byte compilation fails: make-variable-frame-local

control: reassign -1 elpa-perspective control: found -1 1.12+git20160216.add7942-2 control: tag -1 +pending Hello, On Sat 22 Dec 2018 at 03:41pm +0900, David Bremner wrote: > Package: elpa-persp-projectile > Version: 1:0.2.0-2 > Severity: serious > Justification: fails to install > > install/per

Processed: Re: Bug#885563: vte: Do not release with Buster

Processing control commands: > severity -1 important Bug #885563 [src:vte] vte: Do not release with Buster Severity set to 'important' from 'serious' > retitle -1 vte: Do not release with bullseye Bug #885563 [src:vte] vte: Do not release with Buster Changed Bug title to 'vte: Do not release with

Bug#864340: mariadb-10.1 FTBFS on mips64el on Loongson: Installing system database killed with signal TERM after 150 minutes of inactivity

Adrian Bunk 于2017年6月7日周三 下午4:33写道： > > Source: mariadb-10.1 > Version: 10.1.22-3 > Severity: serious > > https://buildd.debian.org/status/logs.php?pkg=mariadb-10.1&arch=mips64el > > ... > # Run testsuite > cd builddir/mysql-test && ./mtr --force --testcase-timeout=30 > --suite-timeout=540 --retry

Bug#885563: vte: Do not release with Buster

Control: severity -1 important Control: retitle -1 vte: Do not release with bullseye The only thing using the old vte in Debian is cdebconf-terminal. But since that's a critical package that hasn't been converted yet, let's defer vte's removal until Bullseye. Thanks, Jeremy Bicha

Processed: notfound 917124 in udev/240-1, found 917124 in 240-1

Processing commands for cont...@bugs.debian.org: > notfound 917124 udev/240-1 Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 The source udev and version 240-1 do not appear to match any binary pa

Processed: notfound 917124 in systemd/239-15

Processing commands for cont...@bugs.debian.org: > notfound 917124 systemd/239-15 Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 No longer marked as found in versions systemd/239-15. No longer ma

Processed: notfound 917124 in systemd/240-1

Processing commands for cont...@bugs.debian.org: > notfound 917124 systemd/240-1 Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 No longer marked as found in versions systemd/240-1. No longer mark

Processed: tagging 917124

Processing commands for cont...@bugs.debian.org: > tags 917124 - moreinfo Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 Removed tag(s) moreinfo. Removed tag(s) moreinfo. > thanks Stopping proces

Processed: found 917124 in udev/240-1

Processing commands for cont...@bugs.debian.org: > found 917124 udev/240-1 Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 The source udev and version 240-1 do not appear to match any binary packa

Processed: bug 917124 is forwarded to https://github.com/systemd/systemd/issues/11255

Processing commands for cont...@bugs.debian.org: > forwarded 917124 https://github.com/systemd/systemd/issues/11255 Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 Set Bug forwarded-to-address to

Bug#917155: pcl: FTBFS on mips/el: virtual memory exhausted: Cannot allocate memory

Hi Emilio, * Emilio Pozuelo Monfort [2018-12-23 12:31]: cd /<>/pcl-1.9.1+dfsg1/build/surface && /usr/bin/c++ -DPCLAPI_EXPORTS -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -Dqh_QHpointer -DvtkDomainsChemistry_AUTOINIT="1(vtkDomainsChemistryOpenGL

Processed: forcibly merging 917124 917136, severity of 917124 is grave

Processing commands for cont...@bugs.debian.org: > forcemerge 917124 917136 Bug #917124 [udev] lvm2 logical volumes are not properly initialized Bug #917136 [udev] udev: LVM volumes fail to initialize properly with udev 240-1 Severity set to 'critical' from 'important' Marked as found in versions

Bug#917070: marked as done (elpa-smex: byte-compilation fails)

Your message dated Sun, 23 Dec 2018 11:34:48 + with message-id and subject line Bug#917070: fixed in smex 3.0-4 has caused the Debian Bug report #917070, regarding elpa-smex: byte-compilation fails to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#917070: marked as done (elpa-smex: byte-compilation fails)

Your message dated Sun, 23 Dec 2018 11:34:42 + with message-id and subject line Bug#917070: fixed in smex 3.0-3 has caused the Debian Bug report #917070, regarding elpa-smex: byte-compilation fails to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#917155: pcl: FTBFS on mips/el: virtual memory exhausted: Cannot allocate memory

Source: pcl Version: 1.9.1+dfsg1-3 Severity: serious Tags: ftbfs Your package failed to build on mips and mipsel: cd /<>/pcl-1.9.1+dfsg1/build/surface && /usr/bin/c++ -DPCLAPI_EXPORTS -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -Dqh_QHpointer

Processed: affects 917075

Processing commands for cont...@bugs.debian.org: > affects 917075 src:grass Bug #917075 [src:mariadb-10.3] mariadb-10.3: libmariadb3 causes removal of default-libmysqlclient-dev Ignoring request to set affects of bug 917075 to the same value previously set > thanks Stopping processing here. Plea

Processed: reassign 917135 to libmariadb-dev

Processing commands for cont...@bugs.debian.org: > reassign 917135 libmariadb-dev 1:10.3.11-1 Bug #917135 [libmaridb-dev] libmariadb-dev: missing Depends: libssl-dev Warning: Unknown package 'libmaridb-dev' Bug reassigned from package 'libmaridb-dev' to 'libmariadb-dev'. No longer marked as found

Processed: reassign 917124 to udev, found 917124 in 240-1

Processing commands for cont...@bugs.debian.org: > reassign 917124 udev Bug #917124 [systemd] lvm2 logical volumes are not properly initialized Bug reassigned from package 'systemd' to 'udev'. No longer marked as found in versions systemd/240-1. Ignoring request to alter fixed versions of bug #917

Bug#917124: lvm2 logical volumes are not properly initialized

Dear Maintainer, I have same problem at startup. Thanks. syslog: ... dic 23 09:39:29 SERVER lvm2-activation-generator: lvmconfig failed dic 23 09:39:29 SERVER lvm2-activation-generator: Activation generator failed. dic 23 09:39:29 SERVER systemd[542]: /lib/systemd/system-generators/lvm2-activation

Bug#917124: systemd: local-fs.target fails with result 'dependency'

On 23/12/2018 15:43, Michael Biebl wrote: Ok, first of all thanks for the information you provided so far. You are welcome. Thank you for the quick turnaround and detailed instructions. I doubt it's a but in systemd itself, it's just the recipient of a device not showing up properly. The is

Bug#917133: openmpi: weird rm -f errors on upgrade

close 917133 thanks On 23/12/2018 05:17, Christoph Anton Mitterer wrote: Source: openmpi Version: 3.1.3-6 Severity: critical Justification: causes serious data loss Thanks for your work, but this bug report is wrong. Hi. On upgrading from 3.1.3-5 I get these: Unpacking libopenmpi3:amd64 (3