Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Wed, 25 Sep 2019, Mark Hindley wrote: > Thanks. Triggers may be an answer to the libsystemd soversion issue. Mind that anything that runs between unpacking the new libsystemd0 and running the trigger will use libsystemd0 instead of libelogind0. > > I don’t like this approach. > > In this

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Wed, 25 Sep 2019, Sam Hartman wrote: > Thorsten> dpkg-divert also has a small period in which neither is > Thorsten> available. I don’t like this approach. > > Is that only when adding a diversion or when upgrading a diverted file > each time? When adding a diversion. dpkg-divert is

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Wed, 25 Sep 2019, Mark Hindley wrote: > libelogind0 can be coninstalled with libsystemd0. However, it is fragile > because > the file that needs to be diverted out of the way is libsystemd.so.0.26.0 (the > actual library file, not a symlink) otherwise ldconfig will still find it and > create

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Mon, 23 Sep 2019, Sam Hartman wrote: > Mark> #935910 is now fixed in apt 1.8.4 in unstable and with that > Mark> installed I can no longer reproduce #934491. The APT > Mark> maintainers have said that adding a Breaks for the fixed > Mark> version of apt is not useful. > >

Bug#939983: error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers'

Hi, I’ve had to downgrade in the meantime, since #935734 at least has a workaround. FWIW, the GNU Guix people have the same problem, and with a different path, others: https://www.redhat.com/archives/libvir-list/2019-July/msg01310.html https://bugzilla.redhat.com/show_bug.cgi?id=1751120 I have

Bug#934491: libelogind0: failing to switch from systemd to sysvinit-core/elogind results in libsystemd.so.0 disappearing

On Thu, 19 Sep 2019, Mark Hindley wrote: > On irc he also said there was little point in adding the Breaks: as apt > doesn't > rexec itself. Yes, even a Pre-Depends would not achieve anything TTBOMK. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn •

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Hello Julien, > conflicting with systemd is doomed. The replacement of sysvinit with > systemd was careful to keep both init systems co-installable, and I note that: ① elogind is not part of the init system, only an add-on to enable systemd-like Provides to get some GUI software to run

Bug#939983: error: Unable to read from '/sys/fs/cgroup/unified/machine/cgroup.controllers'

Package: libvirt-daemon Version: 5.6.0-2 Severity: serious Justification: unusable, no working workaround tglase@tglase:~ $ alias wirrsh wirrsh='virsh -c qemu:///system' tglase@tglase:~ $ wirrsh start MirBSD error: Failed to start domain MirBSD error: Unable to read from

Bug#935109: hwinfo: FTBFS on x32: mdt.c:20:10: fatal error: x86emu.h: No such file or directory

@@ +hwinfo (21.67-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add x32 to list of architectures needing libx86emu-dev (Closes: #935109) + + -- Thorsten Glaser Mon, 09 Sep 2019 17:39:10 +0200 + hwinfo (21.67-1) unstable; urgency=medium * New upstream version 21.67 diff

Bug#939712: performous-composer: missing Depends on libqt5multimedia5-plugins

Package: performous-composer Version: 2.0+20181009-gitbeeea23-1 Severity: serious Justification: dependencies incorrect https://github.com/performous/composer/issues/36 ↓ https://stackoverflow.com/a/22046880/2171120 -- System Information: Debian Release: bullseye/sid APT

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Dixi quod… >branch and testing it; can we please merge it into master and upload >to unstable once it has been tested (should be no problem, I already FWIW, it builds and installs (as upgrade) and starts. bye, //mirabilos -- 15:41⎜ Somebody write a testsuite for helloworld :-)

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Version: 9.0.24-1 Emmanuel, > What is the issue with the dependency on systemd? I was under the there is new data related to that: In bullseye/sid, there’s elogind as desktop/logind alternative that implements the logind API but does not otherwise try to take over the system, allowing other

Bug#935968: texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not found

Norbert Preining dixit: >> I just uploaded a corrected version on CTAN. I think it will be soon > >Thanks a lot for the quick fix, great! Thanks from me (affected end user) as well! Goodnight, //mirabilos -- „Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu

Bug#935968: texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not found

On Wed, 28 Aug 2019, Thorsten Glaser wrote: > (/usr/share/texlive/texmf-dist/fonts/source/public/esint/esint10.mf) This file is clearly broken (besides having a soft hyphen in the licence name now); diffing shows: --- home/tglase/texlive-latex-extra_2019.20190710-1_all-extracted/d/usr/sh

Bug#935968: texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not found

On Wed, 28 Aug 2019, Thorsten Glaser wrote: > I’ll try to make an MWE. This is enough to reproduce the error: tglase@tglase:...cuments/target/latex/betriebshandbuch $ less missfont.log mktextfm esint10 tglase@tglase:...cuments/target/latex/betriebshandbuch $ mktextfm esint10 mktextfm: Runn

Bug#935968: texlive-latex-extra: Font U/esint/m/n/10.95=esint10 at 10.95pt not loadable: Metric (TFM) file not found

Package: texlive-latex-extra Version: 2019.20190824-1 Severity: grave Justification: renders package unusable After updating: Unpacking texlive-latex-extra (2019.20190824-1) over (2019.20190710-1) ... Trying to build documentation: […]

Bug#935734: [workaround] Re: Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

Dixi quod… > tglase@tglase:~ $ virsh -c qemu:///system start MirBSD > error: Failed to start domain MirBSD > error: Operation not supported: operation 'setCpusetMemoryMigrate' not > supported Looking around I found the (not very helpful to me) https://bugzilla.redhat.com/show_bug.cgi?id=1688736

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

On Sun, 25 Aug 2019, Thorsten Glaser wrote: > Package: libvirt-daemon > Version: 5.0.0-4.1 > After a recent upgrade in sid: Hm, but it’s not libvirt, I think, whose upgrade broke things (even if libvirt is unusable): looking at the logfiles under /var/log/libvirt/qemu/ I see the last s

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

> The diff is: HOME, USER, LOGNAME, fd argument for netdev, and kernel > 4.19.0-5-amd64 (worked) vs 5.2.0-2-amd64 (fails). Another difference might be that, in the meantime, I switched from consolekit plus old policykit to elogind, which might have affected some of the “modern desktop” things

Bug#935734: error: Operation not supported: operation 'setCpusetMemoryMigrate' not supported

Package: libvirt-daemon Version: 5.0.0-4.1 Severity: grave Justification: renders package unusable After a recent upgrade in sid: tglase@tglase:~ $ virsh -c qemu:///system start MirBSD error: Failed to start domain MirBSD error: Operation not supported: operation 'setCpusetMemoryMigrate' not

Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX

Hi Chet, >There is a problem with bash-5.0 when the variable is declared local in >the interposed function, and I need to fix that, but that's not a posix ah, okay, I didn’t test what removing the “local” would do. Debian is a special beast: it requires of a /bin/sh to behave like a POSIX shell

Bug#923481: alpine: replies lose In-Reply-To and References headers

On Tue, 13 Aug 2019, Unit 193 wrote: > Ah right. Though while looking through several of my recent sent items, it > seems it preserved those fields as expected. I am using alpine 2.21. Please try this, from the original submission: If I take a message, reply to it, then go to the Subject

Bug#935115: passing variable assignments to functions (was Re: Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX)

Dixi quod… >┌──┬┬──┬┬──┐ >│ shell \ what │ inside visible │ exported │ afterwards visible │ exported │ >├──┼┼──┼┼──┤ >│ ksh93│ ✔ as required │ ✗ (ok) │ ✗ no,

Bug#935115: bash: [regression] passing variable assignments to functions broken in POSIX mode, violating POSIX

Package: bash Version: 5.0-4 Severity: critical Justification: breaks unrelated software Found this gem in #934027: tglase@tglase:~ $ cat testscript dbc_mysql_createdb(){ local ret l_dbname _dbc_nodb echo "dbc_mysql_createdb: _dbc_nodb(1)=$_dbc_nodb" _dbc_nodb="yes"

Bug#935109: hwinfo: FTBFS on x32: mdt.c:20:10: fatal error: x86emu.h: No such file or directory

tags 935109 + patch thanks On Mon, 19 Aug 2019, Thorsten Glaser wrote: > I’m working on a patch. The following debdiff allows the build to succeed: diff -Nru hwinfo-21.67/debian/changelog hwinfo-21.67/debian/changelog --- hwinfo-21.67/debian/changelog 2019-07-28 10:13:51.0 +0

Bug#935109: hwinfo: FTBFS on x32: mdt.c:20:10: fatal error: x86emu.h: No such file or directory

Source: hwinfo Version: 21.67-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) […] cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -Wall -Wno-pointer-sign -pipe -g -I/<>/src/hd

Bug#933979: gnutls28: FTBFS on i386: Build killed with signal TERM after 150 minutes of inactivity after dtls/dtls test

Source: gnutls28 Version: 3.6.9-3 Severity: serious Justification: FTBFS on release arch From: https://buildd.debian.org/status/fetch.php?pkg=gnutls28=i386=3.6.9-3=1564822578=0 […] SKIP: p11-kit-trust.sh

Bug#931021: musescore: phones home, including to Google Analytics, on first start

notfound 931021 musescore-snapshot/3.1+dfsg1-1 thanks > Bugreport for myself and for release tracking. MuseScore 3, which is currently sitting in experimental, intending to hit sid after the release, is NOT affected; disabling the web centre thingy seems to suffice. bye, //mirabilos -- «MyISAM

Bug#931021: musescore: phones home, including to Google Analytics, on first start

Package: musescore Version: 2.3.2+dfsg2-6 Severity: serious Tags: security Justification: phones home Bugreport for myself and for release tracking. Dear release team, please indicate whether this is buster release-critical, I will try to fix it later tonight. On first startup, MuseScore

Bug#929983: ipxe-qemu: virtio booting no longer works after upgrade to buster

On Tue, 4 Jun 2019, Vagrant Cascadian wrote: > Works for me using a virt-manager configured with virtio or the > hypervisor default for netoworking with the same seabios and ipxe Hmm. > versions. My system was recently upgraded from stretch to buster. This one was a fair bit older, I think it

Bug#929983: ipxe-qemu: virtio booting no longer works after upgrade to buster

Package: ipxe-qemu Version: 1.0.0+git-20190125.36a4c85-1 Severity: serious Justification: makes package unusable On this virtualisation system I’ve upgraded to buster (using libvirt and Linux-kvm), netbooting VMs no longer works: -BEGIN cutting here may damage your screen surface-

Bug#929841: crda: Failed to set regulatory domain: -7

Package: crda Version: 3.18-1 Severity: serious Justification: fails tglase@tglase-nb:~ $ fgrep -i -e crda -e regdom /var/log/syslog Jun 1 17:06:26 tglase-nb vmunix: [ 32.679951] systemd-udevd[2262]: Process '/sbin/crda' failed with exit code 255. tglase@tglase-nb:~ $ sudo cleanenv /

Bug#794466: Virtualbox backport for Stretch?

On Fri, 17 May 2019, Harald Dunkel wrote: > AFAIU #794466 seems to be a political issue. Debian wants to provide Nah, it’s an Oracle issue. They did the same with MySQL IIRC, which has nowadays been replaced by MariaDB as this is untenable with the reliability promises Debian gives. > and

Bug#927862: youtube-dl: please update to 2019.04.24

Package: youtube-dl Version: 2019.01.17-1 Followup-For: Bug #927862 Control: severity -1 grave Control: retitle -1 youtube-dl: needs upstream version update to continue working It now doesn’t work at all any more, however, the upstream version does: $ youtube-dl -f 18 U2n5aGqou9E [youtube]

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

tomatically anyway (Closes: #925928) + * Correct the ownership and permissions on the log directory: +group adm and setgid (Closes: #925929) + + -- Thorsten Glaser Tue, 02 Apr 2019 22:54:17 +0200 + tomcat9 (9.0.16-3) unstable; urgency=medium * Removed read/write access to /var/lib/sol

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

On Wed, 3 Apr 2019, Emmanuel Bourg wrote: > > I really insist on being able to install tomcat9 without having to > > install a whole other init system, even if it is not used. > > See this as a compromise? I don’t know… the missing initscript is an RC bug, so the compromise would start _after_

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

On Wed, 3 Apr 2019, Emmanuel Bourg wrote: > Assuming #926316 gets fixed, I think we should focus only on providing a > usable sysvinit script as required by the policy. Supporting people I really insist on being able to install tomcat9 without having to install a whole other init system, even if

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Hi Emmanuel, >What is the issue with the dependency on systemd? Most people using Debian without systemd have APT pinning or other measures in place that prevent the systemd package, which ships the systemd-sysusers binary (and service?), from being installed, in order to not sneakily being

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Hi Emmanuel, > This restores the ability to create the tomcat user without systemd. due to your objection against perceived complexity, I changed the way I’ve implemented this. Doing this at all is required because the hard “Depends: systemd” will not work on many non-systemd systems, and, as

Bug#925473: tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)

Gianfranco Costamagna 2013-2018, Emmanuel Bourg 2001-2017, Markus Koschany + 2015–2019, mirabilos License: Apache-2.0 License: Apache-2.0 diff --git a/debian/changelog b/debian/changelog index 9e1dab71..163eb8d9 100644 --- a/debian/changelog +++ b/debian/change

Bug#925473: Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

On Mon, 25 Mar 2019, Emmanuel Bourg wrote: > When it's ready please let me review the update before uploading. OK. > Not changing the maintainer scripts nor the configuration files in the > process would be nice. I agree; at the current point in time, this should be least-intrusive. bye,

Bug#925473: Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

On Mon, 25 Mar 2019, Emmanuel Bourg wrote: > We've got two serious security issues in the Tomcat init script in the You told me this. I replied by: • I’m active and willing to maintain it • if I don’t realise there’s a bug you can ping me • if even that fails, you can *still* remove it You

Bug#913119: Bug#913138: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Hi Cesare, > But, in the meantime, doesn't the workaround of disabling blk_mq work > for you? I don’t know, because I have no means to trigger the bug. The three other virtualisators I’ve upgraded at the same time did not trigger it. My desktop machine also hits it only occasionally. I’ve

Bug#923481: alpine: replies lose In-Reply-To and References headers

Package: alpine Version: 2.21+dfsg1-1.1 Severity: serious If I take a message, reply to it, then go to the Subject line, press ^K to remove the existing (possibly damaged) text and type new text (possibly to change the subthread subject), the eMail gets sent out AND Fcc’d without both In-Reply-To

Bug#913119: Bug#913138: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1

Hi Debian Linux kernel maintainers, On Wed, 27 Feb 2019, Dragan Milenkovic wrote: > > Hello Dragan, do you know if the patch was eventually included upstream and > > possibly in which version? > > Hello, Cesare. It was included in 4.20.11 and 4.19.24. please do consider uploading 4.19.24 to

Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used

Hi Norbert, >Go ahead immediately, you have every approval. >BTW, changes can be sent to the new development place > https://github.com/debian-tex/texlive-nonbin OK, will do so. I’ll give people a bit to review, although someone on TeX.SE said tabu is broken enough there’s no way I can

Bug#920459: tabu: breaks with color and/or xcolor when spread or negative X coefficients are used

) + + -- Thorsten Glaser Sun, 24 Feb 2019 17:47:26 +0100 + texlive-extra (2018.20190131-1) unstable; urgency=medium * new upstream checkout diff -Nru texlive-extra-2018.20190131/debian/patches/fix-tabu-920459 texlive-extra-2018.20190131/debian/patches/fix-tabu-920459 --- texlive-extra

Bug#914632: uw-imap: CVE-2018-19518

Hi Magnus, >Perhaps wanting to run imapd via remote shell is so rare that there's >no need to write a NEWS.Debian entry? in case of doubt just write one, it does not hurt. Are you going to upload within the next five days or so, or do you need help? (We’re at a BSP and currently fixing stuff…)

Bug#914632: uw-imap: CVE-2018-19518

Hi Magnus, >I reckon. I just haven't been able to make gbp use my long PGP key id... any progress with that? Otherwise I’d be willing to NMU your patch. Greetings from the BSP, //mirabilos -- 21:12⎜ sogar bei opensolaris haben die von der community so ziemlich jeden mist eingebaut │ man sollte

Bug#922701: mocha: ./build.sh[254]: mocha: not found

Package: mocha Version: 4.1.0+ds3-4 Severity: grave Justification: renders package unusable The /usr/bin/mocha command, present in mocha_4.1.0+ds3-3_all.deb, no longer exists, making the package totally unusable. -- System Information: Debian Release: buster/sid APT prefers buildd-unstable

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

Andreas Metzler dixit: >commu.teckids.org offers TLS 1.3, so I a suspect the TLS code is not up >to date for TLS 1.3. No, I can normally connect. mcabber is my primary client because it works inside GNU screen. It just didn’t work at FOSDEM in the IPv6-only network there (the FOSDEM-legacy had

Bug#921195: mcabber: does not connect to Jabber via IPv6 (fails Etch release goal)

Package: mcabber Version: 1.1.0-1.1 Severity: serious Tags: ipv6 Justification: fails release goal I’m currently in the FOSDEM WLAN (IPv6-only, not FOSDEM-legacy), and I can neither connect to the Jabber server with SRV RRs nor when hardcoding commu.teckids.org in mcabberrc. A netcat on

Bug#915689: Bug#919893: Bug#915689: Bug#919893: package shouldn't exist

Michael Stone dixit: > So that's basically just the --rng-entropy argument? If we switch rng-tools5 > to /usr/lib/stunnel/arngc-slrd | runtunnel | \ rngd -f -r /proc/self/fd/0 -H 0.99 -B 2 \ -s 32 -W "$threshold" -t 300 -T 60 I just had the idea of “castling”¹,

Bug#915689: Bug#919893: Bug#915689: Bug#919893: package shouldn't exist

Michael Stone dixit: > Yes, exactly: it's definitely better for a certain class of hardware, but I'm > honestly just not sure whether any of those are still relevant. (Like, do they > work with current kernels, are they in hardware that's otherwise supported, > etc.?) I'd love to see reports from

Bug#920020: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

On Mon, 21 Jan 2019, Matthias Klose wrote: > no, why are you exaggerating? Both the jre and the jdk are usable. The javadoc tool isn’t, and this breaks all builds. I’ve enacted the workaround in the meantime, even if this goes against the documented javadoc options… bye, //mirabilos -- tarent

Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

Package: openjdk-11-jdk Version: 11.0.2+7-1 Severity: grave Tags: patch Justification: renders package unusable [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on project octopus-rpctunnel: MavenReportException: Error while generating

Bug#915689: prevent from migrating to testing

Michael Stone dixit: > So use the epoch. They're invented for fixing collosal errors like > this. Except this time, have the appropriate discussion on -devel > instead of just uploading something without coordination. Sounds like an approach, but please see in #919893 my message first for an

Bug#915689: prevent from migrating to testing

Michael Stone dixit: > Please upload a fixed version of rng-tools instead, reverting the erroneous > change. That is impossible because the version changed. In the tool I’m using, I have a hard version requirement on rng-tools (<< 3) | rng-tools-debian (<< 3). At best we could do with an

Bug#915689: prevent from migrating to testing

Michael Stone dixit: > No, that's something else that shouldn't have happened It’s important to me because the upload of rng-tools (>> 2) broke things on unstable. Perhaps letting it migrate to testing wasn’t ideal, but it will work for people there, and it won’t affect existing users or those

Bug#919855: 2.0.5-1 crashes

Ben Hutchings dixit: >the new Debian version crashes on s390x. It looks like this is due to >an address collision between the build ID in the shared library and >the code in the executables. Helge Deller dixit: >[ 58.612345] 117 (fstype): Uhuuh, elf segment at 0001 requested

Bug#918079: pandas: FTBFS: B-D on python-nbsphinx which is no longer installable nor built any more

Source: pandas Version: 0.23.3-1 Severity: serious See #917418 for “python-nbsphinx (0.4.1+ds-1) is not installable”. src:nbsphinx (0.4.1+ds-3) now only builds the py3k package. python-nbsphinx (= 0.3.5+ds-1) is installable and usable, but no longer in Debian, so please move to python3-nbsphinx

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

On Wed, 19 Dec 2018, Dmitry Smirnov wrote: > trust - a something we can only have in backports-like "volatile" repo. Did you mean: in an unstable-like “volatile” repo? Backports have a defined mission, which has nothing to do with the “volatile” proposal. What you were referring to,

Bug#916377: cups-browsed: segfault during upgrade

retitle 916377 cups-browsed: segfault during upgrade and at system shutdown forcemerge 916377 916149 thanks On Thu, 13 Dec 2018, Till Kamppeter wrote: > This I have already fixed upstream. It was already reported as Ah, okay. In this case, sorry about the noise. > upstream issue #79 and Debian

Bug#916377: cups-browsed: segfault during upgrade

Package: cups-browsed Version: 1.21.5-1 Severity: serious Justification: segfaults Setting up cups-browsed (1.21.5-1) ... Installing new version of config file /etc/cups/cups-browsed.conf ... Restarting CUPS Bonjour daemon: cups-browsed. [ 1143.414255] cups-browsed[8312]: segfault at b8 ip

Bug#916147: Bug #916147: rng-tools: replaced with inferior version

Putting the Launchpad bug into Cc. -- Forwarded message -- Message-ID: Date: Mon, 10 Dec 2018 18:23:56 +0100 (CET) Subject: rng-tools: replaced with inferior version Source: rng-tools Version: 5-1 Severity: serious Justification: breaks existing uses of this package This is the

Bug#916147: rng-tools: replaced with inferior version

Source: rng-tools Version: 5-1 Severity: serious Justification: breaks existing uses of this package This is the same as Launchpad bug #1333293 now arrived in Debian itself. The options (at least) -B, -H, -T, -t are gone, which breaks my application using rngd. I had to create this…

Bug#916017: pax FTBFS with glibc 2.28

Hi Adrian, >Tags: ftbfs > >https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pax.html > >... >cpio.c: In function 'vcpio_wr': >pax.h:261:18: warning: implicit declaration of function 'major' >[-Wimplicit-function-declaration] > #define MAJOR(x) major(x) > ^

Bug#915954: inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)

Package: src:linux Version: 4.18.20-2 Severity: serious When booting with 4.18.0-3, as soon as the display switches from the 80x25 GRUB left the screen in to the framebugger text console the screen instead goes completely blank. Booting the previous kernel, it works. I could try booting with

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

On Fri, 30 Nov 2018, Pirate Praveen wrote: > That is indeed the current definition. The question is about the > possibility of changing that definition or finding other ways to No. It’s there for good reasons, including stability. > accommodate fast changing software like gitlab. Broadening the

Bug#915050: (gitlab) Re: Bug#915050: Keep out of testing

On Fri, 30 Nov 2018, Pirate Praveen wrote: > How about allowing gitlab to be backported directly from unstable? No. Backports are *always* from testing because a backport is supposed to be replaced by the regular stable version of the subsequent release. Hence, only from testing, in the hope

Bug#914291: jaxrs-api: copyright file wrong

Source: jaxrs-api Version: 2.1.2-2 Severity: serious Justification: Policy 2.3, 12.5, possibly 2.1 In an internal Java™ project of $dayjob I was checking licences of updated components and found that javax.ws.rs:javax.ws.rs-api 2.1.1 has a new, different, licence I am unfamiliar with. I de‐ cided

Bug#914074: ln: failed to create symbolic link '/sbin/iptables': File exists

On Mon, 19 Nov 2018, Thorsten Glaser wrote: > Setting up iptables (1.8.2-1) ... > ln: failed to create symbolic link '/sbin/iptables': File exists > dpkg: error processing package iptables (--configure): > installed iptables package post-installation script subprocess returned

Bug#914074: ln: failed to create symbolic link '/sbin/iptables': File exists

Package: iptables Version: 1.8.2-1 Severity: serious Justification: not installable Setting up iptables (1.8.2-1) ... ln: failed to create symbolic link '/sbin/iptables': File exists dpkg: error processing package iptables (--configure): installed iptables package post-installation script

Bug#913335: qemu-system-i386: Display 'sdl' is not available.

reopen 913336 thanks Michael Tokarev dixit: >> pn qemu-system-gui > >Ditto as for #913336. Nope. 1. I still get “Display 'sdl' is not available.” if I select it. 2. qemu *still* runs a VNC server by default if the above package is not installed. Additionally, GTK+3 is… problematic and

Bug#911389: [Pkg-openssl-devel] Bug#911389: libssl1.1: loss of WLAN connectivity after upgrading; it's not the library's job to disable TLSv1.0

Kurt Roeckx dixit: >I will enable SSLv2, SSLv3, 3DES, RC4, export ciphers, and so on again. Stop trolling. //mirabilos -- (gnutls can also be used, but if you are compiling lynx for your own use, there is no reason to consider using that package) -- Thomas E. Dickey on the Lynx mailing

Bug#911389: libssl1.1: loss of WLAN connectivity after upgrading; it's not the library's job to disable TLSv1.0

Package: libssl1.1 Version: 1.1.1-1 Severity: grave Justification: renders package unusable I have the following stanza in my /etc/network/interfaces: iface tarent-lan inet dhcp wireless-mode Managed wireless-essid tarent-lan wpa-ssid tarent-lan wpa-key-mgmt

Bug#812574: grub-pc: wants to overwrite admin configuration on each upgrade

On Wed, 10 Oct 2018, Jeroen Dekkers wrote: > Here we generate /etc/default/grub based on the values stored by > debconf. I think that that is the problem. You should not generate a completely new file if the file is user-extensible or contains values that aren’t also passed through debconf. You

Bug#908087: Bug#908131: forcibly merging 908087 908131

On Fri, 7 Sep 2018, Vincent Lefevre wrote: > I disagree. Both behaviors are caused by the same issue in > python3-pysimplesoap. These behaviors are different just because the > users chose different interfaces in their reportbug configuration. Ah, okay then. > 100% accessible validated (X)HTML

Bug#908131: forcibly merging 908087 908131

Hi Salvatore, > forcemerge 908087 908131 I don’t think these are the same bug. In #908131 I could report the bug, just the BTS contact for existing bugs etc. failed. In #908087 someone could not even report a bug. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn •

Bug#894970: closed by Markus Koschany (Bug#867247: fixed in tomcat8 8.5.14-1+deb9u3)

On Sat, 1 Sep 2018, Debian Bug Tracking System wrote: > #894970: tomcat8: missing Depends on libservlet3.1-java > > It has been closed by Markus Koschany . Confirm fixed, thanks! bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228

Bug#906744: /usr/lib/php/20151012/yaml.so: cannot open shared object file

reopen 906744 thanks Ondřej Surý dixit: >https://tracker.debian.org/media/packages/p/php-defaults/changelog-61 Meh, but why’s it still in mods-available then? bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228

Bug#906744: /usr/lib/php/20151012/yaml.so: cannot open shared object file

Package: php-yaml Version: 2.0.2+1.3.1-2 Severity: grave Justification: renders package unusable php-yaml (2.0.2+1.3.1-2) has a regression over (2.0.0+1.3.0-2+b1): root@tglase:~ # /usr/lib/php/sessionclean PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20160303/yaml.so'

Bug#882943: php-guzzlehttp-psr7 FTBFS with phpunit 6.4.4-2

Hi David, are you planning to do anything with it? We’d NMU if needed, perhaps if this is not fixed in a week or so? Thanks, //mirabilos -- Thorsten Glaser (Gründungsmitglied) Teckids e.V. — Digitale Freiheit mit Jugend und Bildung https://www.teckids.org/

Bug#902934: [pkg-php-pear] Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

David Prévot dixit: >pkg-php-pear != pkg-php-maint But all those Alioth lists no longer exist. bye, //mirabilos -- 18:47⎜ well channels… you see, I see everything in the same window anyway 18:48⎜ i know, you have some kind of telnet with automatic pong 18:48⎜ haha, yes :D 18:49⎜

Bug#902934: phpunit: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org

Package: phpunit Version: 7.2.4-1 Severity: serious Justification: Policy 3.3 See #899636 et al. for all the gory details. -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), (100,

Bug#902933: phpunit : Depends: php-phar-io-version (< 2~~) but 2.0.0-1 is to be installed

Package: phpunit Version: 7.2.4-1 Severity: serious Justification: package no longer installable in sid The recent upload of php-phar-io-version broke even the most recent upload of phpunit. -- System Information: Debian Release: buster/sid APT prefers unreleased APT policy: (500,

Bug#900032: mocha: missing-copyright-file /usr/share/doc/mocha/copyright

Package: mocha Version: 4.1.0+ds1-1 Severity: serious Justification: Policy 12.5 Adequate reports: mocha: missing-copyright-file /usr/share/doc/mocha/copyright And adequate is right, as /usr/share/doc/mocha/ is empty. -- System Information: Debian Release: buster/sid APT prefers unreleased

Bug#898757: musescore: crash on startup

severity 898757 normal tags 898757 + moreinfo thanks Hi Rob, >After displaying the splash screen, Musescore stops while I understand your frustration this works for others, so I’m downgrading the severity. I’m even using it on an i386 system the same as you are. Please do the following:

Bug#893268: libjbzip2-java now in Java team, libnanoxml2-java remains buggy (Was: Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team)

On Thu, 10 May 2018, Emmanuel Bourg wrote: > need some help from a make/shell expert. You summoned? Try this (untested): diff --git a/debian/rules b/debian/rules index 19037e6..6458af2 100755 --- a/debian/rules +++ b/debian/rules @@ -37,10 +37,11 @@ override_dh_auto_build: nanoxml

Bug#895856: portmidi: maintainer address bounces mail from Debian system

Source: portmidi Version: 1:217-6 Severity: serious -- Forwarded message -- From: Mail Delivery System Message-ID: X-Spam-Status: Yes, hits=0.99 required=0.90, tests=bmf To: t...@debian.org Date: Mon,

Bug#894961: ldap-account-manager: missing dependencies on php-xml and php-zip

Roland Gruber dixit: >thanks for your report. This was already addressed in 871471. Perhaps, but would you please also fix it in stable? Thanks, //mirabilos -- “ah that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole

Bug#894961: closed by Roland Gruber <p...@rolandgruber.de> (Re: Bug#894961: ldap-account-manager: missing dependencies on php-xml and php-zip)

found 894961 5.5-1+deb9u1 thanks This is still a grave RC bug in stable, though.

Bug#894970: tomcat8: missing Depends on libservlet3.1-java

Package: tomcat8 Version: 8.5.14-1+deb9u2 Severity: grave Justification: renders package unusable Without libservlet3.1-java installed, deploying a simple WAR fails: 05-Apr-2018 16:25:18.310 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web

Bug#894961: ldap-account-manager: missing dependencies on php-xml and php-zip

Package: ldap-account-manager Version: 5.5-1+deb9u1 Severity: grave Justification: renders package unusable After installing ldap-account-manager, I get this message: -cutting here may damage your screen surface- Your PHP has no XML support! Please install the XML extension for PHP.

Bug#864719: [Pkg-openldap-devel] Bug#864719: slapd: also when upgrading from wheezy to jessie, fails to configure when olcSuffix contains a backslash-escaped umlaut

Hi, > Multiple issues, I'm afraid. […] > Reopened for fixing properly... this sounds like a lot of fixing, thanks for caring, and thanks for the feedback. Good luck, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49

Bug#893992: xfreerdp: command line syntax not documented, matches neither manpage nor usage

Package: freerdp-x11 Version: 1.1.0~git20140921.1.440916e+dfsg1-15 Severity: grave Justification: renders package unusable SYNOPSIS xfreerdp [file] [options] [/v:server[:port]] […] OPTIONS /v [:port] Server hostname […] /rfx RemoteFX […] Hmm. Okay,

Bug#893789: vtk6: FTBFS: Source option 1.5 is no longer supported. Use 1.6 or later.

Source: vtk6 Version: 6.3.0+dfsg2-1 Severity: serious Justification: fails to build from source but built successfully before [100%] Compiling Java Classes cd /<>/vtk6-6.3.0+dfsg2/debian/build/Wrapping/Java && /usr/lib/jvm/default-java/bin/javac -J-Xmx1024m -source 1.5 -target 1.5 -classpath

Bug#893390: ed: no longer M-A:foreign, wrecks havoc on whole system on upgrade

Package: ed Version: 1.14.2-1 Severity: serious Despite the changelog saying “Restore Multi-Arch: foreign” the .deb file actually does not carry any M-A annotation. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49

Bug#891661: maven: missing Depends on libcommons-cli-java

Hi Stephen, >> Installing that library fixes it, so it’s just a missing Depends. > >Thanks for reporting this Thorsten, the dependency is present in >version 3.5.2-2 (via libmaven3-core-java). indeed it is, thanks. I guess that version had not hit my mirror yet when I reported that, and the

Bug#891861: fonts-freefont: debian/copyright does not contain upstream licence

Package: fonts-freefont-ttf Version: 20120503-7 Severity: serious Justification: Policy 12.5 The “Licensing” paragraph of the upstream README file contains the licence grant; in particular, it contains a GPL Font Exception, but also differs in wording from what’s contained in d/copyright (which

<    1   2   3   4   5   6   7   8   9   10   >