Bug#919156: 404: pristine-tar: recommends -> depends or better error message

Op zo 13 jan. 2019 om 13:17 schreef Guido Günther : > > pristine-tar is a recommends, not a depends, so it wasn't installed on > > my system and it took quite some time to figure out why the > > buildpackage was failing. > > pristine-tar is not required at all for gbp operation and people use it >

Bug#919259: systemd: (Security?) update breaks systemd (inside unprivileged container?)

Package: systemd Version: 232-25+deb9u7 Severity: important Hi folks, this morning, some lxc containers on my machine did an unattended upgrade from systemd 232-25+deb9u1 to version 232-25+deb9u7. As part of that upgrade, systemd was reexecuted, which resulted in systemd freezing: systemd[1]:

Bug#822920: marked as done (lighttpd: compress should not be in main lightttpd.conf but in conf-available with a LOWER priority than SSI)

Control: reopen -1 Hi Glenn, On Sun, Jan 13, 2019 at 09:51:03PM +, Debian Bug Tracking System wrote: > To: 822920-d...@bugs.debian.org > > Package: lighttpd > Version: lighttpd/1.4.35-4 > > fixed upstream in lighttpd 1.4.52-4 What seems like a good idea, is a bad one. Now the version

Bug#919257: RFS: antlr4-cpp-runtime/4.7.2-1 [ITP] -- ANTLR Parser Generator - C++ runtime support

Package: sponsorship-requests Severity: normal Control: block 918109 by -1 Dear mentors, I am looking for a sponsor for my package "antlr4-cpp-runtime". Package is required to update mysql-workbench (#902798). * Package name: antlr4-cpp-runtime Version : 4.7.2-1 Upstream

Bug#919234: [Pkg-freeradius-maintainers] Bug#919234: ttls fails with tls 1.3, enabled by default

I have no time to look into this. Can you send a patch please? On Sun, Jan 13, 2019 at 11:33 PM Sam Hartman wrote: > package: freeradius > severity: important > version: 3.0.17+dfsg-1 > justification: regression that totally breaks connectivity > tags: upstream > > > I've cc'd Kurt because he

Bug#919236: [Pkg-freeradius-maintainers] Bug#919236: Inappropriately broad default CA for EAP configuration

Can you send a patch please? It’s been like that since before I touched the package. On Sun, Jan 13, 2019 at 11:39 PM Sam Hartman wrote: > package: freeradius > tags: security > version: 3.0.17+dfsg-1 > severity: important > justification: Inappropriately broad default authorization > > The

Bug#872191: [Freedombox-pkg-team] Bug#872191: plinth: Merge the Disks and Snapshots configuration tabs?

[Joseph Nuthalapati] > It might not be a good idea to merge the snapshots feature into > storage for the following reasons: Interesting observations, but I miss how these arguments hold up when seen from the users point of view. My suggestion was based on my experience as a user, wondering where

Bug#892656: even more tests fail with version 2.0.2

Il 13/01/19 16:52, Paul Gevers ha scritto: > user debian-rele...@lists.debian.org > usertags 884543 bsp-2019-01-nl-venlo > thanks > > On Mon, 23 Apr 2018 14:36:00 +0200 Paolo Greppi > wrote: >> So I'd propose we go straight for option #3 (downgrade node-is-descriptor to >> 1.0). >> Can you do

Bug#919195: cups: gutenprint driver nmo longer workin after upgrade

Hi there Michal, Le dimanche, 13 janvier 2019, 17.04:59 h CET Michal Suchanek a écrit : > I upgraded cups from stable to testing and I am no longer able to print. > > The driver used with stable was something like 'HP LaserJet 6MP > CUPS+gutenprint v5.2' and after upgrade this driver is no

Bug#919258: gnome-mahjongg: Can't change layout

Package: gnome-mahjongg Version: 1:3.22.0-1 Severity: normal Dear Maintainer, Gmome-mahjongg is part of debian gnome destktop. I just start the game in actual debian 9.6 standard desktop installation on a notebook. When starting a mahjongg game, there is no way to select which layout to use. It

Bug#919256: dnssec-trigger: Failed to upgrade: installed dnssec-trigger package post-installation script subprocess returned error exit status 1

Package: dnssec-trigger Version: 0.17+repack-1 Severity: serious Setting up dnssec-trigger (0.17+repack-1) ... Job for dnssec-triggerd.service failed because the control process exited with error code. See "systemctl status dnssec-triggerd.service" and "journalctl -xe" for details. invoke-rc.d:

Bug#872191: plinth: Merge the Disks and Snapshots configuration tabs?

It might not be a good idea to merge the snapshots feature into storage for the following reasons: - Disk management and snapshots are different in functionality. Snapshots is in fact more similar to Backups than to Storage. - Snapshots already has a subsubmenu with 2 entries. Further nesting

Bug#919255: gnucap-python: please stop build-depending on python3.6

Source: gnucap-python Version: 0.0.2-1 Severity: serious Control: block 916817 by -1 Deaer maintainer, We would like to remove python3.6 from buster, so please drop the build-depends on gnucap-python. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18

Bug#905674: Citation notice FAQ

Hi Kurt Fitzner You question whether software should be cited and if so how? These links suggest: Yes, you should cite software, and if the author suggests a way of citing use that. * https://blog.apastyle.org/apastyle/2015/01/how-to-cite-software-in-apa-style.html *

Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)

Hello Santiago, thanks for the reporting it. Unfortunately I am not able to reproduce the described error. It builds just fine and the recent upload into Debian did not identified the problems with the package [1]. Please give some more information, how can it be reproduced. Thanks [1]

Bug#919115: linux-image-4.19.0-0.bpo.1-amd64-unsigned: Graphical glitches (lightdm and cinnamon) after upgrading linux (RadeonRX540)

Some details on the lightdm/lockscreen issue. I just noticed that if I switch to tty1 and go back to lightdm everything is displayed properly, or well, that's what I thought at first, because when I tried to click something or even type, it was unresponsive, it's like a frozen frame,

Bug#919254: chkrootkit: Fix for incorrectly initialized variable in chk_tcpd()

Package: chkrootkit Version: 0.52-2 Severity: normal Tags: patch Under certain circumstances, the CMD variable in chk_tcpd is incorrectly initialized and this leads to a false positive: erroneously reported an infected tcpd. The attached patch fixes this for me in Ubuntu 18.04 but it makes sense

Bug#919253: RM: postbooks [kfreebsd-amd64 kfreebsd-i386 hurd-i386] -- RoQA; Obsolete Qt4 cruft

Package: ftp.debian.org Severity: normal Built with Qt5 on other archs. Scott K

Bug#919252: RM: brewtarget [kfreebsd-amd64 kfreebsd-i386] -- RoQA; Obsolete Qt4 cruft

Package: ftp.debian.org Severity: normal Package is updated for Qt5 on other archs. Scott K

Bug#919251: RM: bibletime [kfreebsd-amd64 kfreebsd-i386] -- RoQA; Obsolete Qt4 cruft

Package: ftp.debian.org Severity: normal Package is updated for Qt5 on other archs. Scott K

Bug#919250: RM: qtscriptgenerator -- RoQA; Obsolete, unmaintained, RC buggy

Package: ftp.debian.org Severity: normal Last maintainer upload was in 2012. Package has been out of Testing for 15 months and will not return. This is an obsolete, unmaintained Qt4 package that should be removed. Scott K

Bug#917406: RFS: elinks/0.13~20180825-1 [UPDATE]

Hello, I am adopting elinks. I have worked on the fork that Moritz has mentioned: https://github.com/rkd77/felinks I have emailed previous upstream maintainers,asking them if they are still maintaining elinks. Two emails bounced back, and I still got no reply from the others. Anyways,

Bug#917406: RFS: elinks/0.13~20180825-1 [UPDATE]

Hello, I am adopting elinks. I have worked on the fork that Moritz has mentioned: https://github.com/rkd77/felinks I have emailed previous upstream maintainers,asking them if they are still maintaining elinks. Two emails bounced back, and I still got no reply from the others. Anyways,

Bug#919249: security issue: instability and crash due to crafted message flooding

Package: mumble Version: 1.2.19-3 Severity: important Tags: security fixed-upstream fixed-in-experimental It is currently possible to cause mumble-server to freeze and/or crash by sending specifically it crafted commands, leading to a denial of service. The server usually automatically recovers,

Bug#919248: RM: ruby-bcat -- ROM; dead upstream, dependency failure

package: ftp.debian.org X-debbugs-CC: pkg-ruby-extras-maintain...@lists.alioth.debian.org Hi, Please ruby-bcat package that I maintain. ruby-aruba, the only package that build-depends on ruby-bcat is updated and it drops its dependency, so we can remove ruby-bcat package safely now. --

Bug#919247: kthresher: cronjob exits with error after package removal

Package: kthresher Version: 1.3.1-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your packages cronjob exits with error after the package has been removed. >From the attached log (scroll to the bottom...): 0m28.1s INFO:

Bug#919246: oss4-dkms: module FTBFS for Linux 4.19

Package: oss4-dkms Version: 4.2-build2017-1 Severity: serious Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts Hi, the oss4-dkms kernel module fails to build for Linux 4.19: DKMS make.log for oss4-4.2-build2017 for kernel 4.19.0-1-amd64 (x86_64) Mon

Bug#918502: golang-github-opencontainers-runtime-tools: autopkgtest needs update for new version of golang-github-hashicorp-go-multierror

I pushed some changes to Salsa:   * New upstream version 0.8.0+dfsg   * Update patches   * Add patch to build against hashicorp-multierror 1.0 Can someone upload this package, as I'm just DM and I don't have permission for that? I CC Dmitry as he's the original author of the package, but

Bug#919060: same problem here...

On 2019, ജനുവരി 13 11:26:54 PM IST, Dragos Jarca wrote: >after apt-get update and apt-get dist-upgrade... > >now gitlab cannot be used... This is a different issue, please open a new bug. >cannot upgrade to experimental to... > >root@omv:/usr/share/gitlab# apt-get install

Bug#919245: xdvi.1: Use the correct style macro for a single argument

Package: texlive-binaries Version: 2018.20181218.49446-1 Severity: minor Tags: patch Dear Maintainer, the font-alternating macros are for two fonts and thus for two or more arguments. See man-pages(7) for a style guide and an appropriate man-page for the use of man-macros, for example

Bug#919244: RM: tomboy/experimental -- RoQA; unmaintained, depends on ancient GNOME libraries

Package: ftp.debian.org X-Debbugs-CC: tom...@packages.debian.org Please remove tomboy from experimental. It was removed from unstable 2 months ago. The experimental version has the same problems as the unstable version. https://bugs.debian.org/907316 Thanks, Jeremy Bicha

Bug#918502: golang-github-opencontainers-runtime-tools: autopkgtest needs update for new version of golang-github-hashicorp-go-multierror

Thanks for the report, I'm looking into that. The FTBFS is not fixed by updating opencontainers-runtime-tools to the latest version (0.8). Actually, the issue is that opencontainers-runtime-tools is using an outdated vendored copy of hashicorp-go-multierror. It doesn't build out of the box

Bug#919243: Acknowledgement (resolvconf: man page missing important /etc/resolv.conf.d/ information)

Sorry, made a mistake on the directory, I am referring to: /etc/resolvconf/resolv.conf.d/ On 14/01/2019 09:09, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 919243: >

Bug#919242: update

Seems to work when i run $ aa-disable quassel-core Seems the AppArmor profile is insufficient when quassel-core is ran by a regular user.

Bug#919243: resolvconf: man page missing important /etc/resolv.conf.d/ information

Package: resolvconf Version: 1.79 Severity: important The man page of resolvconf is missing important information regarding /etc/resolv.conf.d/ It appears the man page from other OS contains information about these directories: https://unix.stackexchange.com/a/128223

Bug#919242: quassel-core: fails to start, permission errors

Seems to work when i run $ aa-disable quassel-core Seems the AppArmor profile is insufficient when quassel-core is ran by a regular user.

Bug#918570: python3-sklearn-lib: dependency on libblas3 | libblas.so.3 instead of libatlas3-base?

> some libraries of this package are linked to libcblas.so.3. > Could this be replaced by linking to libblas.so? > Could this package depend on libblas3 | libblas.so.3 instead of > libatlas3-base? Additionally, in a no-change rebuild of the package currently in sid (0.20.1+dfsg-1), the config

Bug#874219: jxplorer: debian/watch is out of date

Package: jxplorer Followup-For: Bug #874219 Hi, I'm seeing as much activity on the SourceForge page for jxplorer [1] as I am for the Github page [2], so I'm not sure whether we need to change the watch file unless maybe the upstream authors express a preference. I agree that the release of

Bug#919242: quassel-core: fails to start, permission errors

Package: quassel-core Version: 1:0.13.0-4 Severity: grave Justification: renders package unusable Dear Maintainer, When attempting to start quassel-core as a regular user, it is unable to start, errors below (note occurs without any config files present. Permissions on the .config directory are

Bug#919241: RFP: vroom -- Functional testing tool for VIM

Package: wnpp Severity: wishlist "Vroom is for testing vim. Let's say you're a vimscript author. You want to test your new plugin. You could find a nice vimscript test suite, but that only lets you test your vimscript functions. What you really want is a way to specify vim commands — actual

Bug#918418: django-prometheus FTBFS: test failures

Hi, On 05/01/2019 22:06, Adrian Bunk wrote: > Source: django-prometheus > Some recent change in unstable makes django-prometheus FTBFS: This is due to the changes in the Prometheus Python client library. This is discussed in https://github.com/korfuri/django-prometheus/issues/83 and there is a

Bug#910373: gnucash: various UI issues with arrows keys and text selection

Control: found -1 1:3.2-1 This version is now affected too! I don't know why. Perhaps it is less common or this is due to the upgrade of other parts of the system. Now, it's time to upgrade to 3.4, for which the bug should be fixed... -- Vincent Lefèvre - Web: 100%

Bug#914755: /etc/default/dnsmasq ENABLED=0 does not work

On Mon, 26 Nov 2018 17:29:48 -0600 Brent S Elmer wrote: > Package: dnsmasq > Version: 2.79-1 > Severity: normal > > Setting ENABLED=0 in /etc/default/dnsmasq does not prevent dnsmasq from > starting at boot. It appears that dnsmasq will start at boot regardless of > what ENABLED is set to. >

Bug#919240: reproducible: Add back jtk1b armhf node.

Package: jenkins.debian.org Severity: normal I've gotten jtk1b up and running again, and made a branch to re-add it: https://salsa.debian.org/vagrant/jenkins.debian.net/tree/jtk1b-returns live well, vagrant signature.asc Description: PGP signature

Bug#919239: ball: FTBFS when built with dpkg-buildpackage -A

Package: src:ball Version: 1.5.0+git20180813.37fc53c-2 Severity: serious Tags: ftbfs Hello Andreas. Just in case this went unnoticed: This package fails to build with "dpkg-buildpackage -A". From my build log:

Bug#919127: RFS: kio-gdrive/1.2.5+fixedtarball-1

On Sun, Jan 13, 2019 at 12:02:30PM +0200, Adrian Bunk wrote: > On Sat, Jan 12, 2019 at 03:05:55PM -0700, Nicholas D Steeves wrote: > >... > > Changes since the last upload: > > > > kio-gdrive (1.2.5+fixedtarball-1) unstable; urgency=medium > > > > * Restore missing translations. (Closes:

Bug#919238: cloudsql-proxy: Non-working uploader address

Package: cloudsql-proxy Version: 1.13-1 Severity: important This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

Bug#918901: binfmt-support: using fix-binary with existing magic installs detector

On Thu, Jan 10, 2019 at 01:19:27PM +0100, Stefan Agner wrote: > Using update-binfmts with the same magic and fix-binary twice, will > install the detector on the second call. However, this breaks fix-binary > since the whole point of fixed binary is to allow to use the interpreter > inside a

Bug#918588: libtool: generated libtool script is broken, affecting build on AIX

Hi, On 2019-01-12 14:33:06 +, Alastair McKinstry wrote: > I've disabled patch > 0010-libtool-mitigate-the-sed_quote_subst-slowdown.patch, which includes the > 'func_quote' code in the diff, which should revert back to previous working > behavior, but I've no AIX system to debug or test. > Can

Bug#919197: Acknowledgement (qtwayland-opensource-src: FTBFS on hppa - Segmentation faults in testsuite)

On 2019-01-13 2:52 p.m., John David Anglin wrote: > Looks to me to be a NULL pointer check issue in mesa: > > static inline struct wl_drm_buffer * > wayland_drm_buffer_get(struct wl_drm *drm, struct wl_resource *resource) > { >     if (resource == NULL) >     return NULL; > >   

Bug#918987: transition: ode

El 13/1/19 a les 15:52, Emilio Pozuelo Monfort ha escrit: > On 11/01/2019 18:09, Emilio Pozuelo Monfort wrote: >> Control: tags -1 confirmed >> >> On 11/01/2019 15:17, Leopold Palomo-Avellaneda wrote: >>> Subject: transition: ode >>> Package: release.debian.org >>> User:

Bug#919187: base-passwd: Reallocate 64044 (grsec-proc)

On Sun, Jan 13, 2019 at 03:31:58PM +0100, Yves-Alexis Perez wrote: > the range 64040-64044 is assigned to various grsec-related groups. The > groups are created by the linux-grsec-base package postinst, which was > used when src:linux-grsec was a thing. Unfortunately, there is no more > package

Bug#898969: Possible solution released

Hi, I wasn't able to figure out how to test the trigger solution suggested by Paul Wise. I did end up taking so long to fix this that OpenSSL 1.1.1 was released, and I tried to set an installation dependency so the updated version of openssl would be installed first. It does check to see if the

Bug#919237: node-jsonld: FTBFS in sid (Error: Can't resolve 'rdf-canonize')

Package: src:node-jsonld Version: 1.4.0-2 Severity: serious Tags: ftbfs Hello Jonas. I tried to build this package in sid but it failed: [...] debian/rules build-indep dh build-indep dh_update_autotools_config

Bug#919236: Inappropriately broad default CA for EAP configuration

package: freeradius tags: security version: 3.0.17+dfsg-1 severity: important justification: Inappropriately broad default authorization The debian freeradius package changes the default eap configuration to use the default list of Debian certification authorities as the default CAs for verifying

Bug#919235: abcm2ps: FTBFS because debhelper uses ninja build system instead of autoconf

Package: abcm2ps Version: 8.14.2-0.1 Severity: serious Tags: patch Justification: failure to build from scratch Hello. My NMU fails to build because debhelper uses ./build.ninja instead of ./configure and ./Makefile.in. This is quite surprising, and I cannot reproduce the issue in my chroot.

Bug#919234: ttls fails with tls 1.3, enabled by default

package: freeradius severity: important version: 3.0.17+dfsg-1 justification: regression that totally breaks connectivity tags: upstream I've cc'd Kurt because he requested openssl 1.3 test results a while back. While writing automated tests for moonshot-gss-eap, I discovered that by default

Bug#919233: [installation-guide] document Secure-Boot related bits in the d-i manual

Package: installation-guide Severity: wishlist Steve McIntyre wrote: > I've just pushed changes to a few bits of d-i this weekend to make SB > work for amd64: > > * build/util/efi-image: > >We can use pre-existing (and already signed) EFI binaries instead >of building a new

Bug#908796:

I can confirm that today's systemd update fixed it I did apt full-upgrade and update-initramfs -c -k all Tried a reboot and now it boots fine

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

I was able to solve the problem by temporarily compiling it from https://git.zx2c4.com/WireGuard and installing it On Mon, 14 Jan 2019, 03:37 Aryan Duggal DKMS make.log for wireguard-0.0.20181218 for kernel 5.0.0-rc1+ (x86_64) > Sun Jan 13 21:52:56 GMT 2019 > make: Entering directory

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

DKMS make.log for wireguard-0.0.20181218 for kernel 5.0.0-rc1+ (x86_64) Sun Jan 13 21:52:56 GMT 2019 make: Entering directory '/usr/src/linux-headers-5.0.0-rc1+' CC [M] /var/lib/dkms/wireguard/0.0.20181218/build/main.o CC [M] /var/lib/dkms/wireguard/0.0.20181218/build/noise.o CC [M]

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

Package: wireguard-dkms Version: 0.0.20181218-1 Severity: grave Justification: renders package unusable -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign

Bug#919213: irqbalance: endless loop during configure, system reaches maximum of open files

Not seen when upgrading irqbalance (1.5.0-0.1 => 1.5.0-2) on sid amd64: # apt-get dist-upgrade -V Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: irqbalance (1.5.0-0.1 => 1.5.0-2) 1

Bug#919231: salt-master: Upgrade Stretch -> Buster: permission denied on certain files/directories

Package: salt-master Version: 2018.3.3+dfsg1-2 Severity: important Dear Maintainer, Upgrading salt-master from its Stretch version to Buster (whole system was upgraded) breaks the Salt master. Symptoms: E: Sub-process /usr/bin/dpkg returned an error code (1) [...] Job for salt-master.service

Bug#636317: libagar (ITP) libtool troubles

On Sun, Jan 13, 2019 at 5:57 PM Tormod Volden wrote: > Unfortunately, it doesn't build in the PPA yet, because of a libtool > issue. If anyone can take a look at the failed build log and give me a I believe I have fixed this issue (bug in BSDBuild makefile), and the new package is at:

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

It's emacspeak-47.0+dfsg-6 On Sun, Jan 13, 2019 at 8:10 PM Paul Gevers wrote: > On Sun, 13 Jan 2019 13:25:24 -0600 Rob Browning > wrote: > > > Tried to uninstall emacspeak package only and the problems appears > again, > > > so you're right. I'm not able to uninstall it anyway. Should I report

Bug#919229: RM: karma-tools libkarma-cil libkarma-cil-dev libkarma-dev libkarma0 [mips mips64el alpha hppa ia64 m68k powerpcspe riscv64 sh4 sparc64 x32] -- RoQA; ANAIS

Package: ftp.debian.org Severity: normal Control: affects -1 src:libkarma According to https://buildd.debian.org/status/package.php?p=mono=sid , libkarma's build dependency, mono, is no longer being built on several architectures (especially mips and mips64el). This left cruft of libkarma in the

Bug#636317: libagar (ITP) libtool troubles

While looking for a Debian package of agar, I found Stephen's work here: https://launchpad.net/~bregma/+archive/ubuntu/debian/+sourcefiles/agar/1.4.1-1/agar_1.4.1-1.dsc I updated it for upstream 1.5.0 and a few other fixes here:

Bug#919206: udevadm segfaults when using --subsystem-match containing '/'

Control: forwarded -1 https://github.com/systemd/systemd/issues/11416 Thanks, forwarded this issue upstream. I replaced the backtrace with one where libudev1-dbgsym and udev1-dbgsym is installed [1] Regards, Michael [1] https://wiki.debian.org/HowToGetABacktrace -- Why is it that all of the

Bug#918450: RFS: elpy/1.28.0-1

Hi Chris, On Sun, Jan 13, 2019 at 06:26:31PM +, Chris Lamb wrote: > Nicholas D Steeves wrote: > > > elpy (1.28.0-1) unstable; urgency=medium > > … uploaded. Thank you :-) > Regarding: > > ifneq ($(filter nodoc,$(DEB_BUILD_PROFILES)),) > echo -e "\nnodoc profile enabled,

Bug#919227: more acpi info

It seems to be the case that the lid is the most visible breakage but not the only one: when charging, the battery information is not updated. Attaching the output of "acpi -V" with the kernel from stable and the current one in unstable. Battery 0: Charging, 86%, 00:21:57 until charged Battery

Bug#917607: marked as done (udev 240 Makes System Unbootable; rootfs Not Found)

On Sat, 12 Jan 2019 23:18:05 +, Debian Bug Tracking System wrote: >* sd-device-monitor: Fix ordering of setting buffer size. > Fixes an issue with uevents not being processed properly during coldplug > stage and some kernel modules not being loaded via "udevadm trigger". >

Bug#919228: wrong Recommends:

Package: toil Version: 3.18.0-1 Severity: serious thanks Package toil Recommends: python3-futures which is not available. So this package might not be installable on some systems. Did you mean python3-future? Thorsten

Bug#919227: linux-image-4.19.0-1-amd64: acpi lid regression from stable to testing

Package: src:linux Version: 4.19.13-1 Severity: normal Dear Maintainer, after the upgrade to Testing, the system is no longer able to detect a closed lid to initiate suspend-to-ram; reinstalling the kernel from Stable (4.9.0-7), while keeping the rest of the system as is, brings the

Bug#916075: policykit-1: Regression from CVE-2018-19788 fix

Control: retitle -1 policykit-1: Regression from CVE-2018-19788 fix Control: forwarded -1 https://gitlab.freedesktop.org/polkit/polkit/issues/77 Control: found -1 0.105-18+deb9u1 Control: affects -1 security.debian.org,release.debian.org On Sun, Dec 09, 2018 at 09:00:59PM +0100, Paul Gevers

Bug#919226: ITP: hardening-runtime -- Runtime hardening configuration files

Package: wnpp Severity: wishlist Owner: Yves-Alexis Perez * Package name: hardening-runtime Version : 1 Upstream Author : Yves-Alexis Perez https://salsa.debian.org/corsac/hardening-runtime * License : GPL-2+ Programming Lang: configuration file Description :

Bug#918308: transition: botan

Hi Emilio, On Mon, Jan 7, 2019 at 6:08 PM Emilio Pozuelo Monfort wrote: > On 04/01/2019 23:08, Laszlo Boszormenyi (GCS) wrote: > > It's a small transition with only three packages: biboumi, > > libqtshadowsocks and qtcreator. All three build fine with > > this botan release as well. > > Go

Bug#704180: Use p11-kit to replace nssckbi

Le 11/01/19 à 18:28, Daniel Kahn Gillmor a écrit : On Fri 2019-01-11 18:17:26 +0100, Laurent Bigonville wrote: The problem is what/who will decide if this package is installed? If that package is being pulled by on other package for some reason, that means that the local administrator will not

Bug#919225: libballview1.5-dev: missing Breaks+Replaces: libballview1.4-dev

Package: libballview1.5-dev Version: 1.5.0+git20180813.37fc53c-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it

Bug#915667: Reopen Bug 915667

Control: reopen -1 Sorry for closing this bug by mistake. Reopening it now. -- Regards, Boyuan Yang

Bug#919108: wbar: segfaults sometimes, undetermined conditions

It seems to happen when opening or closing windows. I have taskbar activated (this could be relevant) so the number of icons changes along running programs, base icons are 9. It was running happily with compton until last libgdk (I think) upgrade. With default config it doesn't trigger, so it

Bug#919027: wireshark: missing executables

Control: tags -1 confirmed Hi Stefan, On Sat, Jan 12, 2019 at 6:33 AM Stefan Pietsch wrote: > > Package: wireshark-common > Version: 2.6.6-1 > Severity: normal > > The wireshark-common package is missing these executable files: > > - captype Adding it. > - idl2wrs This is already present in

Bug#901461: ITP: mu -- simple editor for beginner Python programmers

A quick update to let everyone know that mu-editor is in the NEW queue. This "small packaging project" has resulted in 14 new Debian source packages, of which 11 have already been accepted into unstable. The last piece of the puzzle, the firmware-microbit-micropython [1] source package is

Bug#919067: Please add a Recommends: on shim-signed

So, looking through this diff: (holy crap, the grub-installer script is getting big! :-() On that front, I'm *tempted* to say it's time to stop caring about and supporting grub-legacy here, maybe? On Sat, Jan 12, 2019 at 01:51:41PM +, Colin Watson wrote: >diff --git a/grub-installer

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

Tried to uninstall emacspeak package only and the problems appears again, so you're right. I'm not able to uninstall it anyway. Should I report the bug to them? On Sat, Jan 12, 2019 at 6:43 PM Rob Browning wrote: > Pavel Kreuzt writes: > > > Package: emacs-gtk > > Version: 1:25.2+1-11 > >

Bug#907997: emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25 25.2+1-6+b2

Control: fixed -1 emacs/1:26.1+1-1 I think this bug may now be "fixed" by the switch of the emacs package to upstream 26.1, which should avoid including any of the conflicting paths. While we may also consider simplifying the control dependencies now, I think this problem is likely resolved.

Bug#919067: Please add a Recommends: on shim-signed

On Sun, Jan 13, 2019 at 05:34:41PM +, Steve McIntyre wrote: > >I'm about to test this lot locally and double-check it DTRT for both >amd64/efi with -signed and i386/efi (without), anyway. And all looks good in both cases. Committing now. -- Steve McIntyre, Cambridge, UK.

Bug#918979: Emacs now just shows dark red dots for images

Sven Joachim writes: > Unfortunately, the binNMUs failed because of #918646. :-/ I should be uploading a -4 in the next day or so with the fix for that. Thanks -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as

Bug#902888: [lcl-utils-1.8] lazbuild crash when lazarus-src is not installed

On Sun, 2019-01-13 at 12:31 +0100, Abou Al Montacir wrote:... > The error messages current location is decided by FPC make file and not by our > scripts. And even it we are going to overwrite this we may want to move the > error files to either/usr/share/fpc/3.0.4/compiler/msg/errore.msgor >

Bug#919224: RM: maliit-framework/experimental -- ROM; dead upstream, unused

Package: ftp.debian.org Severity: normal Control: clone -1 -2 Control: retitle -2 maliit-plugins/experimental -- ROM; dead upstream, unused Hi, These were going to be used as a general OSK type thing, but then the project(s) died upstream, and I forgot about them until bunk reminded me on IRC.

Bug#919223: ruby-haml-contrib FTBFS with ruby-haml 5.0.4-1

Source: ruby-haml-contrib Version: 1.0.0.1-2 Severity: serious Tags: ftbfs buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-haml-contrib.html ... ┌──┐ │ Run tests for ruby2.5 from

Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

On Sun, 13 Jan 2019 13:25:24 -0600 Rob Browning wrote: > > Tried to uninstall emacspeak package only and the problems appears again, > > so you're right. I'm not able to uninstall it anyway. Should I report the > > bug to them? > > Hmm, suppose it may make sense to reassign this bug there for

Bug#919218: non-transition: libqt5gui5-gles

Package: release.debian.org Dear Release team, In Qt/KDE team, we have recently been working on Qt packages built with OpenGL ES support. This is what most participants of the Qt OpenGL thread [1] expressed their wish for. The main idea is that there is now a libqt5gui5-gles package (and, in

Bug#909699:

Control: reassign -1 libotf0 Control: retitile -1 libotf0: crash on rendering Kannada script (affects Emacs) "J. Smith" writes: > This is a libotf bug. See https://debbugs.gnu.org/30193 > According to ldd, gedit does not use libotf. Thanks -- and if I read that right, it looks like a fix may

Bug#919220: ITP: rumur -- model checker for the Murphi language

Package: wnpp Severity: wishlist Owner: Matthew Fernandez * Package name: rumur Version : 2019.01.12 Upstream Author : Matthew Fernandez * URL : https://github.com/Smattr/rumur * License : The Unlicense Programming Lang: C, C++, Python Description :

Bug#919060: same problem here...

after apt-get update and apt-get dist-upgrade... now gitlab cannot be used... cannot upgrade to experimental to... root@omv:/usr/share/gitlab# apt-get install ruby-gitaly=1.5.0+dfsg-1 ruby-responders ruby-default-value-for=3.1.1-1 ruby-devise ruby-doorkeeper ruby-doorkeeper-openid-connect

Bug#919222: ubuntu-keyring: [INTL:pt] Updated Portuguese translation - debconf messages

Package: ubuntu-keyring Version: 2018.09.18.1-1 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for ubuntu-keyring's debconf messages Translator: Américo Monteiro Feel free to use it. For translation updates please contact 'Last Translator' -- Melhores cumprimentos/Best

Bug#919221: lxc: [INTL:pt] Updated Portuguese translation - debconf messages

Package: lxc Version: 1_3.1.0+really3.0.3-2 Tags: l10n, patch Severity: wishlist Updated Portuguese translation for lxc's debconf messages Translator: Américo Monteiro Feel free to use it. For translation updates please contact 'Last Translator' -- Melhores cumprimentos/Best regards,

Bug#919219: abcm2ps: fails to build from scratch because debhelper detects the ninja build system

Package: abcm2ps Version: 8.14.2-0.1 Severity: important Tags: patch My NMU fails to build because debhelper uses ./build.ninja instead of ./configure and ./Makefile.in. This is quite surprising, and I cannot reproduce the issue in my chroot. However, the attached patch selects an explicit

Bug#918450: RFS: elpy/1.28.0-1

Nicholas D Steeves wrote: > elpy (1.28.0-1) unstable; urgency=medium … uploaded. Regarding: ifneq ($(filter nodoc,$(DEB_BUILD_PROFILES)),) echo -e "\nnodoc profile enabled, building without sphinxdoc..\n" dh $@ --with elpa,python3 --buildsystem=pybuild else

  1   2   3   >