Bug#924602: Acknowledgement (systemd - regression: syslog msg from units not routed according to StandardOutput=)

complete journal entries of a different try: __CURSOR=s=8545edb250274321b56a06f3763e1935;i=2cb;b=72db9eebfc5d4d599d064d1dec0942a2;m=84edb947;t=58414a225dfde;x=358be __REALTIME_TIMESTAMP=1552599038156766 __MONOTONIC_TIMESTAMP=2230171975 _BOOT_ID=72db9eebfc5d4d599d064d1dec0942a2 PRIORITY=6

Bug#924602: systemd - regression: syslog msg from units not routed according to StandardOutput=

Package: systemd Version: 241-1 Severity: normal syslog messages from units are not longer routed according to the StandardOutput setting, but I don't see a new setting to change it. My test case is: /etc/systemd/service/test.service: | [Service] | ExecStart=/usr/local/bin/service-test |

Bug#924461: unblock: waagent/2.2.34-3

@@ -1,3 +1,10 @@ +waagent (2.2.34-3) unstable; urgency=medium + + * Set proper access rights on swap file. +CVE-2019-0804 + + -- Bastian Blank Tue, 12 Mar 2019 09:34:51 +0100 + waagent (2.2.34-2) unstable; urgency=medium * Disable all tests, they need a real system. (closes: #918943

Bug#923889: google-compute-image-packages - DoS via serial console write

On Thu, Mar 07, 2019 at 02:25:12PM -0800, Ross Vandegrift wrote: > On Wed, Mar 06, 2019 at 07:49:38PM +0100, Bastian Blank wrote: > > This package instructs journald to duplicate everything sent to the > > journal to the serial console. The serial console is a pretty rate > &g

Bug#923889: google-compute-image-packages - DoS via serial console write

Package: google-compute-image-packages Version: 20190124-2 Severity: grave This package instructs journald to duplicate everything sent to the journal to the serial console. The serial console is a pretty rate limited log output device and blocking there will make all software with any log

Bug#913965: dak: Please ignore build-profile packages from Package-List

Hi Guillem On Sat, Nov 17, 2018 at 05:52:01PM +0100, Guillem Jover wrote: > But as dak uses the entire Package-List from the .dsc for its "seen" > tracking this is problematic, because these require NEW processing, > or these uploads are not accepted as part of a source-only upload, > and even if

Bug#887988: conflicts are not appropriate

Control: reopen -1 Control: found -1 0.3.1-1 Conflicts are no appropriate tool to handle conflicts files. Please fix that properly. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.2

Bug#922973: Acknowledgement (iptables-save -- Table `raw' does not exist)

Control: affects -1 src:neutron This seems to affect all OpenStack Neutron variants, as it tries to save some builtin tables and fails due to the returned error. Bastian -- Wait! You have not been prepared! -- Mr. Atoz, "Tomorrow is Yesterday", stardate 3113.2

Bug#922973: iptables-save -- Table `raw' does not exist

Package: iptables Version: 1.8.2-3 Severity: important iptables-save fails with an error to stdout if a given built-in table does not exist. | % sudo iptables-save -t filter; echo $? | Table `filter' does not exist | 1 See https://bugzilla.redhat.com/show_bug.cgi?id=1673609 for more

Bug#922375: closed by Bastian Blank (Re: Bug#922375: cloud-init: build from src failes some unit tests)

Hi Dirk On Fri, Feb 15, 2019 at 08:41:59AM +, Mayer, Dirk wrote: > But I am wondering when the new version will be available in the current > testing/buster repository, as is seems that the version you mentioned 18.3-5 > is only available in the unstable/sid repository. Due to the freeze

Bug#921319: stretch-pu: package iptables-persistent/1.0.4+nmu2

On Mon, Feb 04, 2019 at 10:55:26PM +0800, gustavo panizzo wrote: > On Mon, Feb 04, 2019 at 09:59:06AM +, Adam D. Barratt wrote: > > Control: tags -1 + moreinfo > > > > On 2019-02-04 08:11, gustavo panizzo wrote: > > > I'd like to fix the bug #921186 in stable, only adding a dependency to > >

Bug#920820: shim-signed - Fails to boot if run via EFI shell

Package: shim-signed Version: 1.28+nmu1+0.9+1474479173.6c180c6-1 Severity: important shim fails to boot if it was started from the EFI shell in the EDK2 reference implementation. Boot is aborted from the ExitBootServices call: | EFI stub: UEFI Secure Boot is enabled. | Bootloader has not

Bug#920819: shim-signed - Fails to run if called from EFI shell without extension

Package: shim-signed Version: 1.28+nmu1+0.9+1474479173.6c180c6-1 Severity: normal shim fails to run if called on the EFI shell as "shimx64". | FS0:\efi\debian\> shimx64 | Failed to open \efi\debian\shimx64 - Not Found | Failed to load image \efi\debian\shimx64: Not Found | start_image() returned

Bug#920799: src:olive - Hijacked name of unrelated package

as much as possible. Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer Unser

Bug#919915: grub2-common: fails to upgrade from 'stretch-backports' - trying to overwrite /etc/kernel/postinst.d/zz-update-grub from grub-cloud-amd64 0.0.4~bpo9+1

Control: notfound -1 0.4.4~bpo9+1 Control: found -1 0.0.4~bpo9+1 Control: fixed -1 0.0.4 Control: severity -1 important Control: tags -1 wontfix On Sun, Jan 20, 2019 at 05:46:27PM +, Colin Watson wrote: > It isn't me who needs the policy lecture here - this is grub2-common's > configuration

Bug#919864: ftp.debian.org: Dak is broken with python-debian 0.1.34

On Sun, Jan 20, 2019 at 10:44:08AM +0100, Christian Marillat wrote: > With python-debian 0.1.34 dak crash with 'dak process-upload' : > In python-debian 0.1.34 a third parameter has been added to deb822 class You mean they made incompatible changes to the API without any real fallback? As dak

Bug#893557: thin-provisioning-tools: FTBFS with glibc 2.17

Hi Steve On Tue, Mar 20, 2018 at 02:10:52PM -0700, Steve Langasek wrote: > Considering debian/rules also hardcodes -O2 for the package itself, it > doesn't seem inappropriate to also build the test shim with the same > options? > Yes, this is working around a toolchain issue. Feel free to

Bug#918187: fai - hook error handling completely broken

On Fri, Jan 11, 2019 at 01:51:53PM +0100, Thomas Lange wrote: > since you did not justified why this bug is grave, I will downgrade > it to normal. Well, I consider it RC for the cloud stuff as it makes image build silently break. Do you really want to play this every time? > Did you tried to

Bug#918187: fai - hook error handling completely broken

Source: fai Version: 5.7.2 Severity: grave There seems to be no way to make hooks abort the run. I explicitely made a hook always fail and it always continued: | partition.GRUB_CLOUD_AMD64 FAILED with exit code 1. | Skipping task_partition | Calling hook: mountdisks.CLOUD | No fstab file

Bug#918185: fai - fcopy mode handling broken precedence

Source: fai Version: 5.7.2 Severity: important fcopy defines three sources for the modes of the final files: - specified on the command line with -m/-M - file-modes files in the files tree - modes of source file The modes specified in the command-line have the highest precedence and override per

Bug#916802: RM: kvpm -- RoQA; unmaintained, requires to-be-removed library

Package: ftp.debian.org Severity: normal Please remove kvpm from unstable. It is NMU maintained while maintainer is also upstream. Last upstream change was two years ago. It depends on liblvm2app, which is going away pretty soon, see #915690. Regards, Bastian

Bug#913116: Needs to depend on chromium-sandbox

On Mon, Dec 17, 2018 at 04:32:50AM -0500, Michael Gilbert wrote: > On Fri, Nov 16, 2018 at 4:30 AM Bastian Blank wrote: > > Debian does not support unprivileged user namespaces, so chromium needs > > to depend on -sandbox to get a working package. > The debian version of

Bug#915691: glusterfs-common - Depends on deprecated liblvm2app

Package: glusterfs-common Version: 5.1-2 Severity: serious liblvm2app is deprecated and will be not longer shipped with Buster. Please drop it's usage. Further references are found here: https://bugzilla.redhat.com/show_bug.cgi?id=1489590 Bastian -- System Information: Debian Release:

Bug#915692: collectd - Recommends deprecated liblvm2app

Package: colectd Version: 5.8.1-1 Severity: serious liblvm2app is deprecated and will be not longer shipped with Buster. Please drop it's usage. Further references are found here: https://bugzilla.redhat.com/show_bug.cgi?id=1489590 https://github.com/collectd/collectd/issues/2647 Bastian --

Bug#915690: kvpm - Depends on deprecated liblvm2app

Package: kvpm Version: 0.9.10-1.1 Severity: serious liblvm2app is deprecated and will be not longer shipped with Buster. Please drop it's usage. Further references are found here: https://bugzilla.redhat.com/show_bug.cgi?id=1489590 Bastian -- System Information: Debian Release: buster/sid

Bug#913146: ovmf debug

hould use a different file name, so /usr/share/ovmf/OVMF-debug.fd or /usr/share/ovmf/debug/OVMF.fd, whatever is easier to do. Also it should define "DEBUG_ON_SERIAL_PORT". For some reason the debug output is behind another feature gate for ovmf. Regards, Bastian -- Bastian Blank Berate

Bug#913116: Needs to depend on chromium-sandbox

Control: reopen -1 Debian does not support unprivileged user namespaces, so chromium needs to depend on -sandbox to get a working package. Re-opening, as recommends are not enough. Regards, Bastian for kernel team -- A woman should have compassion. -- Kirk, "Catspaw", stardate

Bug#912038: closed by Bastian Blank (Re: Bug#912038: grub-cloud-amd64: fails to install)

Dear release team On Sat, Oct 27, 2018 at 03:42:48PM +, Holger Levsen wrote: > 5. General > (a) Supportable > Packages in the archive must not be so buggy or out of date that > we refuse to support them. > This package is too buggy. We expect all packages to install fine under >

Bug#910952: binfmt-support - Fails to run if it can't load modules

Proposed fix in https://salsa.debian.org/debian/binfmt-support/merge_requests/1 Regards, Bastian

Bug#913146: edk2 - Build ovmf variant with DEBUG_ON_SERIAL_PORT

Source: edk2 Version: 0~20180812.cb5f4f45-1 Severity: wishlist Please build an ovmf variant with DEBUG_ON_SERIAL_PORT to allow for proper debugging of stuff like secure boot. Bastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500,

Bug#867668: packages on security.debian.org have different Priority than in the main archive

On Mon, Nov 05, 2018 at 08:44:16PM +, Steve McIntyre wrote: > Thanks! Do you have a feel for how much work that might be please? Running dak control-override with -C in addition to -a should be enough. Bastian -- Well, Jim, I'm not much of an actor either.

Bug#910959: grub-cloud-amd64: missing Conflicts: grub-coreboot, grub-efi-ia32, grub-ieee1275, grub-xen

Hi grub maintainers On Sun, Oct 14, 2018 at 06:40:44PM +0200, Bastian Blank wrote: > On Sat, Oct 13, 2018 at 09:33:26PM +0200, Andreas Beckmann wrote: > > Here is a list of files that are known to be shared by both packages > > (according to the Contents file for sid/a

Bug#911242: grub-legacy - Fails to install on disk

Package: grub-legacy Version: 0.97-73 Severity: grave grub-legacy fails to install a proper bootloader on disk. Given the not longer existing usefulness of this package, I intend to request removal in a short time. Regards, Bastian | # grub-install /dev/sda | Searching for GRUB installation

Bug#911241: grub-installer - Remove grub-legacy support

Package: grub-installer Version: 1.157 Please remove grub-legacy support. I intend to request removal pretty soon as it does not longer work. Bastian -- Behind every great man, there is a woman -- urging him on. -- Harry Mudd, "I, Mudd", stardate 4513.3

Bug#911239: RM: grub-choose-default -- RoQA; outdated, orphaned

Package: ftp.debian.org Control: affects -1 src:grub-choose-default Please remove package grub-choose-default from unstable. It was last uploaded ten years ago. It was orphaned three years ago. It is the last dependency of grub-legacy. Regards, Bastian -- The joys of love made her human and

Bug#776413: The priority of the ed package

Hi On Tue, Oct 16, 2018 at 11:49:58AM +0100, Ian Jackson wrote: > This makes it sound theoretical, or a question of breaking people's > `finger macros'. That is indeed annoying. But there is a much more > serious practical point, which Paul Hardy touches on. How many people are using "ed" and

Bug#910959: grub-cloud-amd64: missing Conflicts: grub-coreboot, grub-efi-ia32, grub-ieee1275, grub-xen

Hi grub maintainers On Sat, Oct 13, 2018 at 09:33:26PM +0200, Andreas Beckmann wrote: > Here is a list of files that are known to be shared by both packages > (according to the Contents file for sid/amd64, which may be > slightly out of sync): > > etc/kernel/postinst.d/zz-update-grub >

Bug#910959: grub-cloud-amd64: missing Conflicts: grub-coreboot, grub-efi-ia32, grub-ieee1275, grub-xen

Control: reassign -1 src:grub,grub-cloud-amd64 Hi Andreas On Sat, Oct 13, 2018 at 09:33:26PM +0200, Andreas Beckmann wrote: > This bug is assigned to both packages. If you, the maintainers of > the two packages in question, have agreed on which of the packages will > resolve the problem please

Bug#910952: binfmt-support - Fails to run if it can't load modules

Package: binfmt-support Version: 2.1.8-2 Severity: important Currently the update-binfmt tool fails to run if it can't use modprobe to load the binfmt_misc module. As the kernel does autoloading for this module, just mounting the filesystem is enough. This makes building the Debian cloud images

Bug#910654: cloud.debian.org: cloud-init apt module can't add GPG keys; dirmngr missing

On Tue, Oct 09, 2018 at 11:01:33AM +, Daniel Strong wrote: > On clean instantiations of the Debian Stretch AWS AMIs, the cloud-init Apt > Configure > module can't receive GPG keys. The following cloud-init Please define the complete key in the config. While not obvious in the documentation,

Bug#910429: grub-cloud-amd64: fails to install in a chroot

Control: reassign -1 release.debian.org Control: retitle -1 piuparts not able to test grub-cloud due to missing /dev On Sun, Oct 07, 2018 at 10:51:01AM +0200, Andreas Beckmann wrote: > piuparts regressions block migration for quite some time already. Well, then let's re-assign tht to

Bug#910429: grub-cloud-amd64: fails to install in a chroot

Hi On Sat, Oct 06, 2018 at 09:15:13AM +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package failed to install. This is more or less expected, as this package will break your bootloader if it finds anything useful. >

Bug#909984: ITP: vaapi-media-driver -- VA-API driver for Intel Gen8+ graphic cards

On Mon, Oct 01, 2018 at 12:16:49AM +0200, Sebastian Ramacher wrote: > Package: wnpp > Severity: wishlist > Owner: Sebastian Ramacher > Control: block -1 by 909983 > > * Package name: vaapi-media-driver > Version : 18.2.0 > Upstream Author : Intel Corporation > * URL :

Bug#909827: linux-source-4.18: not configurable to my liking

Hi On Sat, Sep 29, 2018 at 12:26:54PM +0200, andrew glaeser wrote: > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? >* What exactly did you do (or not do) that was effective (or > ineffective)? >* What was the

Bug#908678: security-tracker - Breaks salsa.d.o

Hi Salvatore On Thu, Sep 13, 2018 at 01:37:35PM +0200, Salvatore Bonaccorso wrote: > Do you have any hints at us on what we could look at to faciliate/help > more salsa maintainers? Please try to fork that repo. Git will take a long time to resolve deltas. This is due to Git not handling very

Bug#908678: security-tracker - Breaks salsa.d.o

Package: security-tracker Severity: critical The security tracker git repository is in a state which git does not really like. git clone takes ages, fsck takes ages, repack is reported to be impossible. The GitLab on salsa.d.o also chokes on it some times during git operations. Some may be

Bug#908632: linux-image-4.19.0-rc3-amd64-unsigned: kernel 4.19 fails to load amdgpu driver on R9 270X.

On Wed, Sep 12, 2018 at 12:45:12AM -0300, felipe wrote: >The system fails to load amdgpu driver with >linux-image-4.19-rc{2,3}-amd64-unsigned, making it impossible to >start X session. I see that you use _both_ radeon and amdgpu. Is this combination even supported? | Kernel modules:

Bug#908570: linux 4.18: dmesg readable as normal user

On Tue, Sep 11, 2018 at 12:01:32PM +0200, Philipp Kern wrote: > Unfortunately I have experienced this on a rebuilt package and cannot easily > test with the one actually in Debian unstable, but for me dmesg seems to > work as a normal user again. "cat /dev/kmsg" just works: Unreproducible: | %

Bug#907704: choose-mirror: default to deb.debian.org

Hi Philipp On Tue, Sep 04, 2018 at 09:02:42AM +0200, Philipp Kern wrote: > I pulled out my RT account to check for mirror-related problems (they > seem to be in a different queue I can't see) and found [0], so it looks > like there's now a third unannounced provider that is not in the > rotation

Bug#907800: fai - Hides stderr from executed scripts

Source: fai Version: 5.7 Severity: important fai-do-scripts writes the output of scripts only to the log. This includes stderr, so it hides errors and the output just states that it failed. Bastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990,

Bug#907799: fai - Does not execute scripts

Source: fai Version: 5.7 Severity: serious fai-do-scripts tries to detect the type of the file, bailing out if it does not know about it, instead of just executing it. It's okay to du that if execution fails with 127 (shell for ENOENT, aka interpreter not found). But it is not okay to do that

Bug#907798: fai - setup-storage unable to set GPT partition id

Package: fai-server Version: 5.7 Severity: normal For cloud images we need to explicitely set GPT partition ids. The root filesystem needs to be on partition one, while also being the last partition on the disk. A partition table will need look like similar to this: | Device Start

Bug#723966: installation-reports: /root directory deleted when re-installing

On Sat, Aug 18, 2018 at 06:52:26PM -0700, Paul Hardy wrote: > Would it be possible to copy /root someplace temporarily during > installation, for example to /home/root if /home is an available file > system or even a RAM-based temporary file system (which won't help > during a kernel panic)? Then

Bug#906085: gcc-8: 2 simultaneous threads of compilation cause machine shutdown

Hi Arthur On Tue, Aug 14, 2018 at 08:32:18AM +0930, Arthur Marsh wrote: > results in machine shutdown. Setting CONCURRENCY_LEGVEL=1 avoids the problem. While gcc may use the system in unusual ways, it does not have the permissions to shutdown a system. If a user space program breaks a system,

Bug#902631: devscripts: CI fails in unstable due to Python 3.7

Hi I miss any description of the real problem. You only describe solutions, but you forget to mention why the easiest solution, just upgrade both sources, does not work. Sure, some of the points can be found in the bug report. On Thu, Aug 02, 2018 at 12:39:18PM -0400, Sandro Tosi wrote: >

Bug#905165: debootstrap - fails in docker environment

Package: debootstrap Version: 1.0.106 Severity: grave debootstrap fails in docker environment completely by: - symlinking $TARGET/proc to /proc - running chroot $TARGET mount -t proc none /proc The later obviously failing with a recursive symlink: | mount: mount proc on /proc failed: Too many

Bug#904978: ITP: protobuf-2 -- This is the protobuf pacakge but version 2.6.1 same as that foudn in jessie but is being packaged to unstable since kotlin-1.1.1 needs it. p.s kotlin-1.1.1 is also being

On Mon, Jul 30, 2018 at 12:20:36PM +0530, Saif Abdul Cassim wrote: > Description : This is the protobuf pacakge but version 2.6.1 same as > that foudn in jessie but is being packaged to unstable since kotlin-1.1.1 > needs it. p.s kotlin-1.1.1 is also being packaged to unstable. This is

Bug#902248: linux-image-4.16.0-2-amd64: General protection fault (with nvidia driver) redulting in Xork proces hanging in "D" state

Control: reassign -1 src:nvidia-graphics-drivers Control: forcemerge 901990 -1 On Sat, Jun 23, 2018 at 11:15:07PM +0200, Lukasz Miller wrote: > After booting new kernel after the upgrade the system came up with blank > screen (initial console boot messages were visible, > but around the time

Bug#901990: linux-image-4.16.0-2-amd64: kernel BUG at startup in usercopy.c ; impossible to boot

Control: reassign -1 src:nvidia-graphics-drivers Control: severity -1 important Hi On Thu, Jun 21, 2018 at 07:34:02AM +0200, Ara Keary wrote: > after switching to version 4.16.16-1 of linux-image-4.16.0-2-amd64 my system > does not boot anymore. I obtain a kernel BUG message in syslog in

Bug#899045: ignore the piuparts failures for gcc-7-cross, gcc-8-cross

On Wed, Jun 13, 2018 at 12:27:23PM +, Holger Levsen wrote: > > The failures are in cruft packages. There is a manual decruft requested: > > #899045, but the cruft packages shouldn't block migration anyway. > > piuparts does not know about cruft, it just takes everything from the > > Packages

Bug#887707: Ignored for now

Control: severity -1 important Let's ignore that for now. I have to ask Microsoft again about it. Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189

Bug#896898: mirror submission for sjc.edge.kernel.org

Hi Konstantin Do you expect users to explicitely configure this mirror or is this just an internal name? Regards, Bastian On Wed, Apr 25, 2018 at 03:04:50PM +, Konstantin Ryabitsev wrote: > Submission-Type: new > Site: sjc.edge.kernel.org > Type: leaf > Archive-architecture: ALL amd64 arm64

Bug#895602: [Pkg-ganeti-devel] Bug#895602: ganeti-os-noop - export fails with non block device

Hi Mike On Tue, Apr 24, 2018 at 11:15:30AM +, Mike Gabriel wrote: > I fixed this in unstable now. Thanks, will take a look when it landed. Regards, Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl...@credativ.de credativ GmbH, HRB Mönchengladbach 12080,

Bug#892883: mirrors: Debian mirror opensource.nchc.org.tw: add as candidate of ftp.tw

Hi On Sat, Apr 14, 2018 at 08:51:32PM +0800, Steven Shiau wrote: > Any idea when will ftp.tw.debian.org use opensource.nchc.org.tw? There is a problem with that. I've seen several occurances of lookup failures for this name. | ssh: Could not resolve hostname opensource.nchc.org.tw: Temporary |

Bug#895602: ganeti-os-noop - export fails with non block device

Package: ganeti-os-noop Version: 0.2-1 Severity: grave The export script tries to use blockdev to check for the size. This works fine for block devices, but completely fails for everything else. As this script also ignores the error, the export fails with a completely non-discriptive output. |

Bug#895599: ganeti-2.15 - Fails to export vm: certificate is valid but its commonName does not match hostname

Package: ganeti Version: 2.15.2-7+deb9u1 Severity: grave All vm exports fail with: | 2018-04-13 09:23:25,650: socat: E certificate is valid but its commonName does not match hostname This is fixed in 2.16. Bastian -- Bastian Blank Berater Telefon: +49 2166 9901-194 E-Mail: bastian.bl

Bug#894561: add new variable

Hi On Wed, Apr 04, 2018 at 10:36:46AM +0200, Thomas Lange wrote: > FAI_PACKAGE_NAME_CHECK=0 > or > DISABLE_PACKAGE_NAME_CHECK=1 > > Which variable name is better? Do you have any better name? You don't have an existing naming schema for that? I would go for the later, or you decide that all

Bug#894561: fai - Make non-existing packages fatal

Source: fai Version: 5.6 Severity: important fai currently ignores all unavaible packages during the normal install step. This behaviour is not configurable. In the case of fai-diskimage, this behaviour is rarely useful, because it usualy produces broken images and finding problems faster is

Bug#882760: Debian debian.linux.edu.lv: ftpsync version, push+cron

Hi All pushs fail since 2018-03-04. Please investigate. We did not get any response from you for our last inquiry since several months. It is as follows: On Sun, Nov 26, 2017 at 02:19:38PM +0100, Bastian Blank wrote: > You receive this mail because you are listed as cont

Bug#892883: mirrors: Debian mirror opensource.nchc.org.tw: add as candidate of ftp.tw

On Sat, Mar 24, 2018 at 01:03:02PM +0800, Steven Shiau wrote: > Yes, we have updated ftpsync on our mirror server (opensource.nchc.org.tw or > a.k.a free.nchc.org.tw), and is ready to receive push mirror. > Now I'd like to ask the mirrors team where may we receive the push trigger? I selected

Bug#894030: linux-image-4.15.0-2-amd64: kernel memory leak while recording with audacity

Hi Dominique On Sun, Mar 25, 2018 at 04:53:30PM +0200, Dominique Dumont wrote: > ** Tainted: D (128) > * Kernel has oopsed before. According to this, your kernel is not in the best of states. Maybe you want to read the fulle kernel log and see where this started? > ** Kernel log: > [

Bug#893845: initramfs-tools: Add LZ4 support

On Fri, Mar 23, 2018 at 08:16:11AM +0100, Paul Menzel wrote: > As for some users boot speed is quite important, shaving 400 ms off the boot > time is quite nice. And then they use BIOS which is aweful slow in disk access, so the time is used instead to actually read the blocks from disk? Bastian

Bug#893557: thin-provisioning-tools: FTBFS with glibc 2.17

Hi Steve On Mon, Mar 19, 2018 at 03:37:17PM -0700, Steve Langasek wrote: > Ok, after some trial and error, I've determined that the reason my earlier > test succeeded was because I had built the test preload.so without the > benefit of dpkg-buildflags, which means -O3, which is used by default

Bug#892647: linux-image-4.14.0-0.bpo.3-amd64: Kernel panic, NULL pointer dereference in xhci_hcd

Control: severity -1 important Control: tag -1 moreinfo On Sun, Mar 11, 2018 at 07:57:11PM +0200, enyone wrote: [ no text] > ** Tainted: O (4096) > * Out-of-tree module has been loaded. Please drop this modules, they are not supported by us. After you do, please show new evidence. Bastian

Bug#885762: mirror submission for mirrors.nipa.cloud

Hi Thank you for mirroring Debian and sorry about the wait. On Fri, Dec 29, 2017 at 06:27:17PM +, TH-NIPA-CLOUD wrote: > Trace Url: http://mirrors.nipa.cloud/debian/project/trace/mirrors.nipa.cloud We don't longer list new mirrors that do not use ftpsync. Please fetch yourself a copy from

Bug#882668: mirror submission for mirror.uzcloud.uz

Hi I'm closing this request for mirror listing due to lack of reponse. Bastian -- The heart is not a logical organ. -- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4

Bug#891235: linux-headers-4.15.0-1-amd64: dkms modules, like zfs-dkms and spl-dkms do not compile against this kernel package

Hi On Fri, Feb 23, 2018 at 05:39:49PM +0100, Hans Freitag wrote: > I have problems updating to kernel 4.15 due to the fact that zfs-dkms and spl- > dkms won't compile automatically anymore. There is not much that the kernel can do if other stuff does not follow. Please write the bug against

Bug#882141: closed by Scott Kitterman <sc...@kitterman.com> (Bug#882141: fixed in postfix 3.2.4-1)

On Sun, Feb 11, 2018 at 11:11:16PM -0500, Scott Kitterman wrote: > Would you please check that your /lib/systemd/system/postfix@.service has: > > After=network-online.target nss-lookup.target > Wants=network-online.target > > At least as I understand it, that's supposed to make sure the network

Bug#891003: docker-compose - ImportError: No module named types

Package: docker-compose Version: 1.17.1-1 Severity: important docker-compose fails to run with fulfilled dependencies: | $ docker-compose -f docker-compose.yml -f docker-compose-dev.yml build | Traceback (most recent call last): | File "/usr/bin/docker-compose", line 11, in |

Bug#890239: Not fixed

Control: found -1 65.0.3325.73-1 Not sure what happened, but this version does not contain this recommends. | $ apt-cache show chromium=65.0.3325.73-1 | grep u2f | $ Bastian -- Power is danger. -- The Centurion, "Balance of Terror", stardate 1709.2

Bug#890579: mirror submission for mirrors.nav.ro

Hi Daniel Thank you for mirrorring Debian. On Fri, Feb 16, 2018 at 08:50:49AM +, Daniel S. wrote: > Maintainer: Daniel S. Do you have a role address to act as contact? People come and go and we have way to many mirrors without any working contact. Bastian -- The sight of

Bug#887366: mirror submission for debian.mirror.net.in

Hi Mirror Admin Thank you for mirroring Debian. Some remarks: - Please don't use "ftp.*.debian.org" as upstream. Only HTTP is guaranteed to be available. Regards, Bastian On Mon, Jan 15, 2018 at 02:42:53PM +, Mirror Admin - Debian wrote: > Submission-Type: new > Site:

Bug#890026: mirror submission for mirrors.pxd.me

Hi Fabien Thank you for mirroring Debian. However: - http://mirrors.pxd.me/ return 403 - http://mirrors.pxd.me/debian/ return 403 - You don't include source, which makes you violate the license of a lot of software and is a red flag. - Just "amd64" is a bit meagre. - You don't list any

Bug#882141: closed by Scott Kitterman <sc...@kitterman.com> (Bug#882141: fixed in postfix 3.2.4-1)

On Fri, Feb 09, 2018 at 01:50:29AM -0500, Scott Kitterman wrote: > Because I don't get that error when I try to replicate the condition. So postconf does not fail for you if inet_interfaces lists an ip the system does not currently have? > Feb 09 01:28:58 relay02 postmulti[3783]: fatal:

Bug#882141: closed by Scott Kitterman <sc...@kitterman.com> (Bug#882141: fixed in postfix 3.2.4-1)

Control: reopen -1 Control: found -1 3.2.5-1 On Fri, Dec 15, 2017 at 06:24:06AM +, Debian Bug Tracking System wrote: >* Rewrite debian/postfix-instance-generator to avoid use of postmulti > to fix failures when inet_interfaces != all Closes: #882141 It now uses postconf -h

Bug#887704: waagent - Auto-updated agent mangles packet filter rules

On Fri, Jan 19, 2018 at 10:04:50AM +0100, Bastian Blank wrote: > The auto-upgraded agent part mangles the packet filter rules, as global > resources. I think we got to an understanding that such changes undermine the normal security process of distributions and that they should not do it

Bug#887707: waagent - Azure platform installs binary-only extension without user consent

Moin On Fri, Jan 19, 2018 at 11:05:41AM +0100, Bastian Blank wrote: > One of this components is a diagnostics agent used to extract metrics > from the system. This extension is installed without user consent if > the user enables serial console output (boot diagnostics) via the Azure

Bug#888992: linux-image-4.14.0-3-amd64: kernel oops on dpkg/apt/aptitude

Control: forcemerge 888954 -1 On Wed, Jan 31, 2018 at 07:35:00PM -0500, Scott Bailey wrote: > This bizarre behavior first appeared during the week between Christmas and > New Years (approx 28 December 2017) and has plagued me relentlessly since > that > time, across multiple kernel versions. I

Bug#887255: lvm2 should depend on e2fsprogs explicitly

On Sun, Jan 21, 2018 at 10:09:14AM +0100, Andreas Henriksson wrote: > The fsadm(.sh) script does indeed invoke both tune2fs and resize2fs > under certain circumstances, so from a laymans view there should > definitely be a dependency added. It also needs resize_reiserfs and xfs_growfs, but there

Bug#887707: waagent - Azure platform installs binary-only extension without user consent

Package: waagent Version: 2.2.18-3 Severity: serious The waagent includes support for installing and updating arbitrary extensions. This mechanism is used for example to reset passwords and ssh keys, but also to install various other, also commercial, components on the system, controlled by the

Bug#887704: waagent - Auto-updated agent mangles packet filter rules

Package: waagent Version: 2.2.18-3 Severity: grave The auto-upgraded agent part mangles the packet filter rules, as global resources. | 2018/01/19 08:26:51.997473 INFO Event: name=WALinuxAgent, op=Install, message=Agent WALinuxAgent-2.2.19 downloaded successfully, duration=0 | 2018/01/19

Bug#886238: Build-Profiles purpose, mechanism vs policy (was Re: Bug#886238: Please introduce official nosystemd build profile)

On Tue, Jan 09, 2018 at 07:29:51PM -0500, Sam Hartman wrote: > A build profile seems like a great way to express the flag, and like > many things in Debian, the work would fall on those who would benefit > from it. > So, I do support the use of build profiles for use flags. > I also believe

Bug#887554: RM: ibm-3270 -- ROM

Package: ftp.debian.org Severity: normal Please remove package ibm-3270. Bastian

Bug#887540: RM: python-dvdvideo -- ROM

Package: ftp.debian.org Severity: normal Please remove package python-dvdvideo. Bastian

Bug#887541: RM: uucp-lmtp -- ROM

Package: ftp.debian.org Severity: normal Please remove package uucp-lmtp. Bastian

Bug#865497: support status of check-mk-agent

Hi Is the agent still supported outside that "OMD environment"? Bastian -- Another Armenia, Belgium ... the weak innocents who always seem to be located on a natural invasion route. -- Kirk, "Errand of Mercy", stardate 3198.4

Bug#882744: [IPHH #1071507] Re: Bug#882744: Debian mirror debian.mirror.iphh.net: upstreammirror, ftpsync version

Hi Carsten On Fri, Dec 29, 2017 at 05:48:56PM +0100, Carsten Rosenberg wrote: > the ftpsync has been updated with a new version downloaded from: > http://ftp.debian.org/debian/project/ftpsync/ftpsync-current.tar.gz Thanks. > I hope everything is fine now? Does monitor the status of our mirror

Bug#884381: mirror submission for linux.extremehosting.nl

On Sat, Dec 30, 2017 at 09:03:09PM +0100, Bastian Blank wrote: > On Sat, Dec 30, 2017 at 07:16:52PM +, eXtremeHosting wrote: > > The files are downloaded without any problems. > > http://linux.extremehosting.nl/debian/project/trace/linux.extremehosting.nl This file contains:

Bug#884381: mirror submission for linux.extremehosting.nl

Hi On Sat, Dec 30, 2017 at 07:16:52PM +, eXtremeHosting wrote: > We don`t allow browsing the directory. Well, our monitoring currently needs it, so this is a showstopper. > The files are downloaded without any problems. >

Bug#874473: Re: Bug#874473: Debian mirror ftp.cica.es: invalid-tracefile, syncscript

On Tue, Nov 28, 2017 at 10:33:35AM +0100, Soporte CICA wrote: > we've applied all the changes you proposed. We are using now ftpsync to > mirror Debian and we've configured the update every four hours. By the other > hand, the problem with the tracefile jumps should be already solved. We have >

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