Bug#899766: ivtv-utils: Invalid maintainer address pkg-mythtv-maintain...@lists.alioth.debian.org

On Thu, 2018-05-24 at 09:44 +0200, Christoph Biedl wrote: > Package: src:ivtv-utils > Version: 1.4.1-2 > Severity: serious > User: ad...@alioth-lists.debian.net > Usertag: alioth-lists-maintainer > > Dear uploader of ivtv-utils, > > as you've probably heard, Debian's alioth services are shutting

Bug#898087: Debian kernel packaging no longer accepts typical downstream version numbering.

On Mon, 2018-05-07 at 13:36 +0100, peter green wrote: > Common practice for downstreams (whether complete derivatives or end > users) is to version modified packages with a version number like > > 4.16.5-1+something1 > > Where "something" is the name of a project, the name of the person >

Bug#712841: A bit late, but still an issue...

On Mon, 2018-04-16 at 20:12 +0200, Martin Michlmayr wrote: > Do you know if /etc/default is Debian-specific or generic? I'm just > wondering if the qcontrol configs should read from /etc/default/qcontrol > (Google suggests Red Hat and SUSE have it too, so I guess that should > be ok.) They have

Bug#712841: A bit late, but still an issue...

On Sun, 2018-04-15 at 15:33 +0100, Ian Campbell wrote: > That said, if there are modifications which can be made to the existing > config file installed on this variant which would minimise the > modifications i.e. by adding a simple "has_a_fan = true" which affected > p

Bug#712841: A bit late, but still an issue...

On Sun, 2018-04-15 at 16:03 +0200, Martin Michlmayr wrote: > * Axel Sommerfeldt [2018-04-14 22:07]: > > Just a reminder that this bug is still a thing. And yes, the model > can be found in uLinux.conf: > > Ian, do you think it's worth asking the release team if they'd

Bug#894515: qcontrol: daemon does not start at boot

Control: tag -1 +moreinfo On Sat, 2018-03-31 at 19:04 +0200, alberto wrote: > I see that in the list of supported models (/etc/qcontdol.conf) the 212P is > missing but if I start the daemon manually (service qcontrold start) > everything > works. I assume the problem is not the model but

Bug#894155: openjdk-9-jre: "Minecraft.jar" no longer running via binfmt misc

Package: openjdk-9-jre Version: 9.0.4+12-2 Severity: important Dear Maintainer, After a recent upgrade I am now seeing: $ ./Minecraft.jar can't locate java: No such file or directory At the weekend I updated my (slightly out of date) Buster system, picking up new versions of many Java

Bug#889991: lintian: Please warn if versions differ only in the epoch

Package: lintian Version: 2.5.65 Severity: wishlist Dear Maintainer, The recent "Debian part of a version number when epoch is bumped" has highlighted the fact that the epoch is not included in the names of the various package files (source and binary) and that this can potentially cause

Bug#774227: busybox-static: execs applets when chrooting

On Mon, 2018-02-05 at 12:17 +0100, Chris Boot wrote: > Control: tags -1 -confirmed -patch +wontfix > Control: retitle -1 busybox-static: always prefers applets when chrooting > > This is desired behaviour for the busybox-static package, and I can't > think of any documentation changes that could

Bug#886238: Please introduce official nosystemd build profile

On Tue, 2018-01-09 at 05:03 +, Wookey wrote: > And the reason why you'd use it for something like this is that it > lets you upstream patches (which change dependencies) in a reasonably > clean way. And is the reason this is preferable to `dpkg-vendor` based stuff because `dpkg-vendor` cannot

Bug#886238: closed by Bastian Blank <wa...@debian.org> (Re: Bug#886238: Please introduce official nosystemd build profile)

On Mon, 2018-01-08 at 08:46 -0800, Don Armstrong wrote: > All of that said, if you are interested in Debian supporting a nosystemd > build profile, continuing to escalate conflicts with other developers is > not helping your cause. It would be more helpful if people on _both_ sides would stop

Bug#885914: "RuntimeError: dictionary changed size during iteration" in s3cmd put

Package: s3cmd Version: 2.0.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, s3cmd put is failing with: ! An unexpected error has occurred. Please try reproducing the error using the latest s3cmd code

Bug#883580: debian-installer: arm64: please ship dtb files

On Wed, 2017-12-06 at 07:53 +0100, Andre Heider wrote: > > I don't know what devices you work on, but I have a couple of different > consumer armhf and arm64 devices, spread out over different > architectures. All their device trees are updated every single kernel > release. Often it's for new

Bug#883133: Bug#883134: general: Add new package header Upstream-Version:

On Sat, 2017-12-02 at 06:06 +0200, Victor Porton wrote: > For this I need the upstream versions of "python2.7" and "xsltproc". The upstream version of a Debian package can be deterministically extracted from the package version, see https://www.debian.org/doc/debi an-policy/#s-f-version for the

Bug#852127: Bug#871476: qcontrold not starting

sooner, my qnap systems are sticking with sysvinit for the forseeable future (only because they are working fine for me as is, not because I want to avoid systemd in general). Ian. commit 910a6d6f37c8829ddb935f82cd15093ca6790159 Author: Ian Campbell <i...@debian.org> Date: Sun Jan 29 14:44:33

Bug#878363: cron: Please mark cron as Multi-Arch: foreign

Package: cron Version: 3.0pl1-128.1 Severity: wishlist Tags: patch Hello, I have an i386 system which I would like to update a subset of to amd64 (a partial cross-grade). Two of the packages which I need to install are mythtv-{database,backend}:amd64 (from dmo) which each have a dependency on

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

On Tue, 2017-10-10 at 15:37 -0700, Francois Marier wrote: > On 2017-10-10 at 21:37:30, Ian Campbell wrote: > > Sorry, looks like I accidentally missed out a hunk in the orignal > > patch > > I sent, see below. Like last time note the mode as well as the > > content >

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

On Tue, 2017-10-10 at 13:13 -0700, Francois Marier wrote: > On 2017-10-10 at 19:38:18, Ian Campbell wrote: > > On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote: > > > E: libhdhomerun4: ldconfig-symlink-missing-for-shlib > > > usr/lib/x86_64-linux-gnu/libhd

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

On Tue, 2017-10-10 at 13:13 -0700, Francois Marier wrote: > On 2017-10-10 at 19:38:18, Ian Campbell wrote: > > On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote: > > > E: libhdhomerun4: ldconfig-symlink-missing-for-shlib > > > usr/lib/x86_64-linux-gnu/libhd

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

On Tue, 2017-10-10 at 11:20 -0700, Francois Marier wrote: > Thanks for the patch Ian. > > I merged it [1] but then noticed that it introduces two lintian problems: > > E: libhdhomerun4: ldconfig-symlink-missing-for-shlib > usr/lib/x86_64-linux-gnu/libhdhomerun.so.4 >

Bug#878100: iputils-ping: Please mark iputils-ping as Multi-Arch: foreign

Package: iputils-ping Version: 3:20161105-1 Severity: wishlist Tags: patch I have an i386 system which I would like to update a subset of to amd64 (a partial cross-grade). One of the packages which I need to install is libmyth-29:amd64 (from dmo) which has a dependency on iputils-ping which

Bug#878099: libhdhomerun: Please make libhdhomerun4 Multi-Arch: same

Source: libhdhomerun Version: 20170930-1 Severity: wishlist Tags: patch Dear Maintainer, Please move the libraries to /usr/lib/${DEB_HOST_MULTIARCH} and mark the package as Multi-Arch: same to allow coinstallation of libhdhomerun4:i386 and libhdhomerun4:amd64 (for example). I've tested the

Bug#876662: s3cmd: Errors with --cache-file= and use of Python3

Package: s3cmd Version: 2.0.0-1 Severity: important Dear Maintainer, My backup scripts invocation of s3cmd is resulting in two warnings/errors. I report them together here since I am unsure if the second is a consequence of the first. First warning is: WARNING: !!! Support for python3

Bug#870185: armel/marvell kernel size

On Sat, 2017-08-19 at 12:57 +0900, Roger Shimizu wrote: > I know for bug #870185, Robert fixed his device by modify uboot > params, but I guess it's still possible to keep uboot params and only > change the boot addresses of kernel/initrd in flash-kernel db file. In

Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II

On Sun, 2017-08-13 at 11:56 +0200, Robert Schlabbach wrote: > Von: "Ian Campbell" <i...@debian.org> > > There is one other option, which is to ask people to adjust their > u- > > boot boot scripts as Robert has done, however the QNAP systems are > &g

Bug#870185: FATAL: kernel 4.11.0-0.bpo.1-marvell does not boot on QNAP TS-219P II

On Sat, 2017-08-12 at 21:49 +0100, Ben Hutchings wrote: > On Mon, 2017-07-31 at 18:10 +0200, Robert Schlabbach wrote: > > Ok, I figured it out. I noticed that the 4.11 kernel has a more > > "generous" memory layout than the 4.9 one: > >  > > kernel 4.9: > >  > > [0.00] Memory:

Bug#870430: linux-image-4.9.0-3-marvell: Couldn't find DTB in /usr/lib/linux-image-4.9.0-3-marvell or /etc/flash-kernel/dtbs

On Wed, 2017-08-02 at 21:29 +0200, noone never wrote: > Please find my answers inline. Thanks! In particular for... > [...] > > The message: > >     Couldn't find DTB  in /usr/lib/linux-image-4.9.0-3-marvell or > > /etc/flash-kernel/dtbs > > is interesting since the double space in "DTB  in" is

Bug#870430: linux-image-4.9.0-3-marvell: Couldn't find DTB in /usr/lib/linux-image-4.9.0-3-marvell or /etc/flash-kernel/dtbs

Control: reassign -1 src:flash-kernel 3.79 On Tue, 2017-08-01 at 23:39 +0200, noone never wrote: > Package: src:linux > Version: 4.9.30-2+deb9u2 > Severity: important > Dear Maintainer, > > When I dist-upgrade my Sheevaplug from jessie to stretch, I get this error: > Couldn't find DTB  in

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

On Wed, 2017-07-26 at 19:23 +0200, Helio Loureiro wrote: > Hi, > > I already sent. Please provide a full serial log when booting with the bad kernel. Also please let us know what version of Xen you are running and whether this was running as a guest or as dom0. > And in the first post in this

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

On Wed, 2017-07-26 at 18:51 +0200, Helio Loureiro wrote: > Hi, > > It can't be.  It is the same bug as describe in this one. > > If you read the first post, it can't boot and shows the same content > as in the bug I detected now on my system. Nowhere there does it say anything about failing to

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

outage > because of this parameter. > > I held on kernel 3.19 from Jessie meanwhile. > > Best Regards, > Helio Loureiro > http://helio.loureiro.eng.br > https://se.linkedin.com/in/helioloureiro > http://twitter.com/helioloureiro > > > 2017-07-26 17:56 GMT+02:00 Ian Campbel

Bug#852324: Disable CONFIG_DEBUG_WX in order to avoid this issue.

On Wed, 2017-07-26 at 17:13 +0200, Helio Loureiro wrote: > Hi, > > As much it sounds correct to protect systems in this way, you broke > compatibility.  I'm back to kernel 3.19 until this is fixed. > > So in order to have such parameter enabled, you should at the least > provide a bootparam

Bug#868217: qemu-user-static: Missing binfmt.d files causing systemd-binfmt.service to die with `condition failed`

> ```On Thu, 13 Jul 2017 00:17:54 -0700 Ben Young qemu-aarch64-static.conf [...] >    I can't seem to find the source for these files in either Debian's > or > Fedora's package source, nor in the upstream qemu source. These files are generated by the postinst script

Bug#868030: qemu-user-static: Please enable "F - fix binary" flag for binfmt entries

Package: qemu-user-static Version: 1:2.8+dfsg-6 Severity: wishlist Dear Maintainer, Please consider enabling the "F" flag in the binfmt entries which this package adds. From https://www.kernel.org/doc/html/v4.12/admin-guide/binfmt-misc.html: F - fix binary The usual behaviour of

Bug#866971: debian-installer: live-installer should show Debian live in upper right or left corner so it's known from a glance to people nearby

On Mon, 2017-07-03 at 17:33 +0100, Steve McIntyre wrote: > On Mon, Jul 03, 2017 at 02:03:27PM +0100, Chris Lamb wrote: > > Hi, > > > > > Currently there doesn't seem to be any difference in the UI while > > > either using the regular D-I or Debian Live > > > > Outside of the context of reporting

Bug#853258: docker.io: uses sleep to query user in maintainer script

Control: severity -1 serious On Tue, 2017-06-27 at 07:21 -0400, Antoine Beaupré wrote: > On 2017-06-27 08:11:03, Ian Campbell wrote: > > If you want to be pointlessly pedantic about it then your bug is that > > your maintainer script in debian/ calls a program which

Bug#853258: docker.io: uses sleep to query user in maintainer script

On Mon, 2017-06-26 at 19:07 -0400, Antoine Beaupré wrote: > > If something used in the maintainer script breaks policy, the maintainer > > breaks policy. With your argumentation, I could move a bunch of bad > > commands to this_is_not_a_maintainer_script.sh, source that, and policy > > does not

Bug#839108: [pkg-go] Bug#839108: dh-golang: Please document behavior and variables used

On Wed, 2017-06-21 at 01:39 -0700, Michael Stapelberg wrote: > > > > On Wed, Jun 21, 2017 at 1:21 AM, Ian Campbell <i...@debian.org> wrote: > > On Wed, 2017-06-21 at 06:28 +0200, Guillem Jover wrote: > > > Hi! > > > > > > On Tue, 201

Bug#839108: [pkg-go] Bug#839108: dh-golang: Please document behavior and variables used

On Wed, 2017-06-21 at 06:28 +0200, Guillem Jover wrote: > Hi! > > On Tue, 2017-06-20 at 09:49:26 +0200, Michael Stapelberg wrote: > > > > Guillem Jover writes: > > > Please document at least the variables from the environment that > > > directly affect the behavior such as

Bug#864525: flash-kernel: fails on fat32

On Sat, 2017-06-10 at 02:41 +0200, Heinrich Schuchardt wrote: > On 06/10/2017 02:11 AM, Ben Hutchings wrote: > > On Sat, 2017-06-10 at 00:59 +0200, Heinrich Schuchardt wrote: > >> On 06/10/2017 12:31 AM, Martin Michlmayr wrote: > > * Heinrich Schuchardt [2017-06-09 23:18]:

Bug#860808: ocfs2 blocks jbd2

On Sat, 2017-05-13 at 08:41 -0500, Russell Mosemann wrote: > package: src:linux > Version: 4.9.18-1~bpo8+1 > Severity: important >   > Is anyone from ocfs2 addressing these bugs? They won't see this message because you haven't sent it to them. Please take this directly to the ocfs2-devel mailing

Bug#861263: debian-installer: zfs support

On Fri, 2017-05-05 at 22:52 +0100, Sam Kuper wrote: > If so, is there > any reason in principle why that installer could not in future be > distributed with the capability to (download and) compile and run ZFS, > and to provide the user with the option to install Debian onto a ZFS > root

Bug#854854: Cherry pick and backport patches for rtc-s35390a (Was: Bug#854854: qcontrol: reboot/poweroff)

Control: retitle -1 Cherry pick and backport patches for rtc-s35390a to Jessie Control: found -1 3.16.39-1+deb8u2 Control: fixed -1 4.6.4-1 stable@ please see the list of requested backports at the end. debian-*: I tried (and succeeded!) to reassign to src:linux and tried (and failed!) to merge

Bug#852127: Info and patches from Arch linux package maintainer

friedrico (the author of [0]) pointed me to some patches which he used to get around some issues with qcontrol and systemd as seen in #781886, these look similar to stuff I was playing with but didn't manage to finish. I'm about to go AFK for a few days, but I shall try (again :-/) to make some

Bug#749991: Wrong kernel in debian-installer package

On Mon, 2017-03-27 at 13:32 +0200, Philip Hands wrote: > > Alexander Sosedkin writes: > > > On Mon, 27 Mar 2017 12:43:40 +0200 > > > > Philipp Kern wrote: > > > > > Even if we'd leave the old kernel udebs in testing for a while, you'd  > > > still hit a

Bug#858308: flash-kernel: documentation for upgrading Odroid-U2/U3 to flash-kernel

On Tue, 2017-03-21 at 00:31 +0100, Adam Borowski wrote: > Package: flash-kernel Not sure that this (or u-boot) is really the best place for it, it certainly wouldn't occur to look under either of those packages for such documentation. Perhaps a wiki page under wiki.debian.org/DebianOn might be

Bug#841144: kernel BUG at /build/linux-Wgpe2M/linux-4.8.11/fs/ocfs2/alloc.c:1514!

OCFS2 folks, any thoughts on this crash? On Tue, 2017-01-17 at 02:12 +, Ben Hutchings wrote: > On Mon, 2017-01-16 at 13:12 -0600, Russell Mosemann wrote: > [...] > > Jan 15 17:31:03 vhost032 kernel: [ cut here ] > > Jan 15 17:31:03 vhost032 kernel: kernel BUG at > >

Bug#489452: Solved (or solvable) in 1.4?

Hello, The upstream bug tracker where this bug is forwarded has gone away, migrated to another AIUI (trac at tickets.musicbrainz.org), but I can't find the forwarded bug there. I found a copy of the original upstream bug in:

Bug#853855: (no subject)

On Fri, 2017-02-03 at 15:51 +0100, Emmanuel Kasper wrote: > Actually on further research, net.ifnames and most dot-containing > parameters are not here for the kernel, but to configure on boot > various systemd components, d-i doesn't use systemd, does it? Ian.

Bug#853855: di-utils: Kernel boot options containing a dot are not propagated to the installed system

On Fri, 2017-02-03 at 12:22 +0100, Emmanuel Kasper wrote: > > > A kernel boot param like net.ifnames=0 will be skipped when the > > > installer parses the boot option for setting the bootloader. > > > > > > Found in di-utils:  > > > > > > # Skip module-specific variables > > >    

Bug#853855: di-utils: Kernel boot options containing a dot are not propagated to the installed system

On Wed, 2017-02-01 at 15:30 +0100, Emmanuel Kasper wrote: > Package: di-utils > Version: 1.117 > Severity: minor > Tags: d-i > > A kernel boot param like net.ifnames=0 will be skipped when the > installer parses the boot option for setting the bootloader. > > Found in di-utils:  > >

Bug#852437: qcontrold fails starting

On Sun, 2017-01-29 at 13:03 +, Ian Campbell wrote: > In response to this I got:   ch...@free.fr SMTP error from remote mail server after end of data: host mx1.free.fr [212.27.48.6]: 550 spam detected I'm sending you this from a different address, if this doesn't get through the

Bug#852437: qcontrold fails starting

tag -1 +moreinfo On Tue, 2017-01-24 at 13:39 +0100, Michaël Marchegay wrote: > Package: qcontrol > Version: 0.5.5-2 > > After a fresh install of stretch, qcontrold won't start on TS-410. > > I had to apply the following patch in order to make it working : > > root@qnap:/etc/qcontrol# diff -u

Bug#852596: iio-sensor-proxy: spams syslog with an error message every second

On Sun, 2017-01-29 at 14:30 +0530, Ritesh Raj Sarraf wrote: > On Fri, 2017-01-27 at 22:04 +0100, iqwue Wabv wrote: > > upstream of i-s-p suggests that this bug should be reassigned to kernel  > > package. > > ps. > > said 27.01.2017 on https://github.com/hadess/iio-sensor-proxy/issues/134 > >

Bug#852127: qcontrold is not started on default

On Wed, 2017-01-25 at 22:08 +, Thomas Pircher wrote: > On 2017-01-23 20:00, Ian Campbell wrote: > > [0] https://git.hellion.org.uk/?p=qcontrol.git;a=tree;f=systemd;h=f9b3c > > 358a84915b10bb780e0a8becdfa47604924;hb=HEAD > > Ok, I haven't managed to get the service fi

Bug#852324: x86/mm: Found insecure W+X mapping

On Mon, 2017-01-23 at 18:32 +, Ben Hutchings wrote: > Any ideas, Ian? I'm afraid I'm not so up to speed on Xen things since I changed jobs last year, looks like people from xen-devel are already involved though. Ian.

Bug#852127: qcontrold is not started on default

On Mon, 2017-01-23 at 18:29 +, Thomas Pircher wrote: > Thomas Pircher wrote: > > after an update from jessie to stretch the qcontrold daemon is no  > > longer > > started. > > This should have read "is no longer enabled by default". > I can start the qcontrold manually and the daemon works

Bug#851469: flash-kernel: ARM new boot.scr does not allow the device to boot

On Mon, 2017-01-16 at 20:11 +0100, permondes - sagen wrote: > no luck: > > > $ fw_printenv > > Cannot parse config file '/etc/fw_env.config': No such file or > > directory > > and indeed, the file does not exist. Yes, you would need to obtain or produce one suitable for your device, it's not

Bug#851469: flash-kernel: ARM new boot.scr does not allow the device to boot

On Mon, 2017-01-16 at 00:14 +0100, Karsten Merker wrote: > On Sun, Jan 15, 2017 at 08:24:37PM +0100, permondes - sagen wrote: > > Copying back the previous boot.scr made it boot again. The environment > > variables were the same as before. So I am back where I have been > > before. > > To make

Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel

On Sun, 2017-01-01 at 12:40 -0800, Martin Michlmayr wrote: > I investigated a bit more and > found > out that it relates to the use of "local".  See e.g. > http://superuser.com/questions/363444/how-do-i-get-the-output-and-exi > t-value-of-a-subshell-when-using-bash-e/1103711#1103711 > for an

Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel

On Sat, 2016-12-17 at 14:09 -0800, Martin Michlmayr wrote: > It seems the exit called from find_dtb_file() doesn't exit the whole > program.  I know this is normal because it's called in a subshell, > but > flash-kernel itself does a "set -e" so I thought any exit should > trigger the whole

Bug#789886: linux-image-3.2.0-4-kirkwood: Couldn't find /usr/lib/linux-image-3.2.0-4-kirkwood/kirkwood-sheevaplug.dtb

On Sat, 2016-12-17 at 12:59 -0800, Martin Michlmayr wrote: > It seems I never applied this patch because I was waiting for Ian to > review it. > > Ian, do you have some time to look at the proposed patch? I'm a bit jet-lagged, but your explanation does seem to make sense. I reckon go with the

Bug#847154: linux-image-amd64: Disabling vsyscall interface may break docker run

On Tue, 2016-12-06 at 14:17 +, Ben Hutchings wrote: > > But perhas we should more explicit in this message, e.g.: > > "This breaks (e)glibc 2.13 and earlier, which may still be installed in > a chroot or container environment based on Debian 7, RHEL/CentOS 6 or > earlier versions." That's a

Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)

On Fri, 2016-11-25 at 08:56 -0800, Ryan Tandy wrote: > On Fri, Nov 25, 2016 at 04:24:31PM +0000, Ian Campbell wrote: > > > > Is it possible that there are multiple variants of this one with > > differing numbers of disks? > > > > It's a little tricky to google

Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)

On Fri, 2016-11-25 at 08:10 -0800, Ryan Tandy wrote: > On Fri, Nov 25, 2016 at 07:42:37AM +0000, Ian Campbell wrote: > > > > Assuming orion5x-linkstation.dtsi is correctly relating to your > > platform you would appear to want one of: > >    $ git grep orion5x-linksta

Bug#845611: linux-image-4.8.0-1-marvell: hard drive not detected on LinkStation Pro (LS-GL)

On Thu, 2016-11-24 at 23:24 -0800, Ryan Tandy wrote: > whereas the new orion5x-linkstation.dtsi contains this code: > > { > status = "okay"; > nr-ports = <1>; > }; A .dtsi is an include file, not the final thing for any given device, for that you need a .dts (which is compiled

Bug#845085: docker.io: Some commands do not work on some images with kernel version 4.8

On Tue, 2016-11-22 at 12:17 +, Ian Campbell wrote: > On Sun, 2016-11-20 at 09:57 +, Luís Picciochi Oliveira wrote: > > > > While using Docker, some commands on some images stopped working. > > For > > example: > > > >   $ docker run -it --rm cent

Bug#845085: docker.io: Some commands do not work on some images with kernel version 4.8

On Sun, 2016-11-20 at 09:57 +, Luís Picciochi Oliveira wrote: > While using Docker, some commands on some images stopped working. For > example: > >   $ docker run -it --rm centos:centos6  bash > This does not work. It always returns with code 139: > >   $ echo $? > 139 FYI something

Bug#818731: approx: weekly cronjob breaks with removal of Files field from Sources

On Tue, 2016-11-15 at 20:48 -0500, Eric Cooper wrote: > On Sun, Mar 20, 2016 at 08:04:56AM +0000, Ian Campbell wrote: > > I've just received the following in a cron mail: > > > > /etc/cron.weekly/approx: > > File > /var/cache/approx/debian/dists/experimental/ma

Bug#843139: nmu: lua5.1_5.1.5-8.1+b1

> Please would you schedule a binNMU on at least armhf FYI I did a manual rebuild of lua5.1 locally and can confirm that qcontrol builds with the updated version. Thanks, Ian.

Bug#843139: nmu: lua5.1_5.1.5-8.1+b1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, My package (qcontrol) fails to build because lua5.1 has not yet been rebuilt with -fPIC on armhf. Please would you schedule a binNMU on at least armhf (although it might be worth doing

Bug#842159: libprotobuf-dev: Package is not specific to C++ but description says it is

Package: libprotobuf-dev Version: 3.0.0-7 Severity: normal Dear Maintainer, I was recently working with a golang project which used protobuf and wanted to import google/protobuf/descriptor.proto, I struggled to find the correct package because libprotobuf-dev describes itself as containing

Bug#842158: protobuf-compiler: Considerer Recommend: libprotobuf-dev

Package: protobuf-compiler Version: 3.0.0-7 Severity: normal Dear Maintainer, libprotobuf-dev contains several standard .proto files included in the upstream protobuf source. I was recently working with a (golang) project which imported google/protobuf/descriptor.proto and was surprised to find

Bug#836679: flash-kernel: cannot configure kernel 4.7 with new flash-kernel

On Fri, 2016-09-30 at 11:21 -0700, Martin Michlmayr wrote: > Looking at the code, all uses of find_dtb_file() check for the result > and produce an error if the file doesn't exist, so maybe we should > just move the error messages into find_dtb_file().  Then we could > tell > the user where we

Bug#837757: cloud-init: Please provide a utility/mode to wait for cloud-init to complete

Package: cloud-init Version: 0.7.7~bzr1156-2 Severity: wishlist Tags: upstream Dear Maintainer, I am provisioning an image using debian-jessie-amd64-hvm-2016-02-17-ebs-39d3917e-ff4e-4597-848e-4d0fdf8529e6-ami-f0e7d19a.3 (ami-3a13ac4) and after ssh becomes available I need to wait for cloud-init

Bug#834505: arm64 boot failure with large physical memory range

On Mon, 2016-08-22 at 11:03 +0100, Leif Lindholm wrote: > > > I thought there was a control bit on ARMv8 too which made it cause a > > fault if the code loaded through, stored via, branched to etc an > > address with bits set between the maximum physical address bit and the > > bits

Bug#834505: arm64 boot failure with large physical memory range

On Sun, 2016-08-21 at 11:42 +0100, Leif Lindholm wrote: >  > You're not wrong, but unfortunately the ability to write semi-portable > code left the planet over a decade ago. For clarification - the > problem is not with regards to code written specifically for arm64 and > not verified with

Bug#830949: Please add better xsession integration and documentation

I think this would be going to far for the sort of tool xss- lock is so I don't intend to do this. Ian. commit 323b8eeb04a7e6a7b87ae7670c1eda6a3ca891ce Author: Ian Campbell <i...@debian.org> Date:   Sun Aug 21 12:47:10 2016 +0100 Try to clarify usage via xsession or similar in xss-lock(1)

Bug#833561: arm64: dtbs no longer installed in vendor subdir

On Sat, 2016-08-06 at 11:14 +0100, Ian Campbell wrote: > On Fri, 2016-08-05 at 18:37 -0700, Martin Michlmayr wrote: > > > > I ran dtbs_install manually to verify: > > > > ARCH=arm64 make  -n -C debian/build/build_arm64_none_arm64 > > dtbs_install INSTALL_DTBS_PA

Bug#833561: arm64: dtbs no longer installed in vendor subdir

On Fri, 2016-08-05 at 18:37 -0700, Martin Michlmayr wrote: > I ran dtbs_install manually to verify: > > ARCH=arm64 make  -n -C debian/build/build_arm64_none_arm64 > dtbs_install INSTALL_DTBS_PATH=/home/tbm/debian/linux-4.7~rc7/x > echo '  INSTALL arch/arm64/boot/dts/amd/amd-overdrive.dtb'; mkdir

Bug#833097: flash-kernel: should exist when DTB doesn't exist

On Sun, 2016-07-31 at 13:16 -0700, Martin Michlmayr wrote: > Package: flash-kernel > Version: 3.68 > > At the moment, flash-kernel doesn't exit when the DTB doesn't exist. > It will print the DTB to be used but then not copy it.  That will > result in devices not being able to boot. > > Ian, is

Bug#830268: linux: please make the build reproducible

On Thu, 2016-07-07 at 20:52 +0200, Reiner Herrmann wrote: > While working on the "reproducible builds" effort [1], we have noticed > that linux could not be built reproducibly. > Since we started varying the shell used for /bin/sh (bash vs. dash), > linux no longer builds reproducibly. OOI what

Bug#825688: grub-efi-arm: refuses to install to an ext* device

On Sat, 2016-05-28 at 22:18 +0200, Steinar H. Gunderson wrote: > Package: grub-efi-arm > Version: 2.02~beta2-36 > Severity: normal > > Hi, > > grub-install completely refuses to install an EFI GRUB to a /boot/EFI > that is not on vfat or hfs+ (the C source code has explicit checks). > However,

Bug#792075: ITP: git-lfs -- Git Large File Support. An open source Git extension for versioning large files

On Thu, 2016-05-19 at 07:52 -0700, Stephen Gelman wrote: > Do I need to file an ITP for each one? AIUI, yes, I was hoping pkg-go-maintainers might be able to advice but it seems I (and I pressume, you) cannot post there (subscribers ony I guess). Good news is that it looks like about half the

Bug#792075: ITP: git-lfs -- Git Large File Support. An open source Git extension for versioning large files

Hi Stephen, On Fri, 2015-07-10 at 19:35 -0500, Stephen Gelman wrote: We are just about to start using git-lfs at work so I was wondering what the status of this ITP is? Looks like the RFS in #793171 was stalled due to the vendoring. I've taken the liberty of also CCing the go packaging team.

Bug#820771: xss-lock breaks suspend with xscreesaver on testing

On Mon, 2016-04-11 at 22:15 -0400, Jay Kamat wrote: > Package: xss-lock > Version: 0.3.0-2 > Severity: important > > Dear Maintainer, > > With the latest update of xscreensaver, xss-lock, a package which > locks > the screen using xscreensaver on suspend seems to prevent a suspend, > and >

Bug#818731: approx: weekly cronjob breaks with removal of Files field from Sources

Package: approx Version: 5.5-1 Severity: important Control: block 818463 by -1 Dear Maintainer, I've just received the following in a cron mail: /etc/cron.weekly/approx: File /var/cache/approx/debian/dists/experimental/main/source/Sources.xz, line 1: missing "Files" field run-parts:

Bug#818481: installation-reports: Xen PV drivers not present in 32-bit installer kernel (but present in installed kernel)

On Fri, 2016-03-18 at 06:50 +, John Dilley wrote: > Correct, I'm running the installer as a PVHVM domain (this is how > XenServer supports Jessie onwards). > > I tried running the xen netboot image, but although it booted it then > complained about a display issue, and didn't seem to bring up

Bug#813881: linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1

On Mon, 2016-03-14 at 10:48 -0700, Vagrant Cascadian wrote: > On 2016-03-14, Ian Campbell wrote: > > On Sun, 2016-02-07 at 19:50 -0800, Vagrant Cascadian wrote: > >> On 2016-02-06, Heinrich Schuchardt wrote: > >> > Booting with u-boot-imx requires imx6q-wandboard

Bug#813881: linux-image-4.3.0-1-armmp install wrong dtb on Wandboard Quad Rev B1

On Sun, 2016-02-07 at 19:50 -0800, Vagrant Cascadian wrote: > On 2016-02-06, Heinrich Schuchardt wrote: > > Booting with u-boot-imx requires imx6q-wandboard-revb1.dtb. > > linux-image-4.3.0-1-armmp installs imx6q-wandboard.dtb > > leaving me with a system that will not boot. > > > > With

Bug#812540: Add ARCH_HISI for Lemaker HiKey support

On Sat, 2016-03-12 at 09:00 -0800, Vagrant Cascadian wrote: > On 2016-03-12, Ian Campbell wrote: > > On Fri, 2016-03-11 at 20:03 -0800, Vagrant Cascadian wrote: > >> On 2016-03-10, Martin Michlmayr wrote: > >> > * Ian Campbell <i...@debian.org> [2016-01-25 0

Bug#818059: linux-image-4.4.0-1-armmp-lpae: Missing usb-power-supply in DTB for OlinuXino-A20-LIME2

Control: tag -1 +upstream On Sun, 2016-03-13 at 09:17 +0100, Michael Haas wrote: >  > I presume this would need to be fixed upstream in > arch/arm/boot/dts/un7i-a20-olinuxino-lime2.dts > but I don't know where to direct that specific bug report. Please report it (or, better, send a patch) to

Bug#812540: Add ARCH_HISI for Lemaker HiKey support

On Fri, 2016-03-11 at 20:03 -0800, Vagrant Cascadian wrote: > On 2016-03-10, Martin Michlmayr wrote: > > * Ian Campbell <i...@debian.org> [2016-01-25 09:57]: > >> I suppose it will need more than just ARCH_HISI. Are you able to > identify > >> the full set of o

Bug#817897: jessie-pu: package flash-kernel/3.35+deb8u2

On Fri, 2016-03-11 at 11:19 +0100, Uwe Kleine-König wrote: > Package: release.debian.org > Severity: normal > Tags: jessie > User: release.debian@packages.debian.org > Usertags: pu > > Hello, > > I'd like to update flash-kernel in jessie with the below debdiff. The > intention is to fix the

Bug#817016: linux-image-4.3.0-1-amd64: ThinkPad X1 Carbon: Boot stalls at "intel_pstate: HWP enabled"

Control: forwarded -1 https://bugzilla.kernel.org/show_bug.cgi?id=110941 On Mon, 2016-03-07 at 07:46 +, Andy Smith wrote: > Package: src:linux > Version: 4.3.5-1 > Severity: normal > > Dear Maintainer, > > Booting this kernel (or the debian-installer latest daily) results in a blank >

Bug#816164: nmudiff for 1.2.1-6.3

/changelog +++ flexbackup-1.2.1/debian/changelog @@ -1,3 +1,10 @@ +flexbackup (1.2.1-6.3) unstable; urgency=medium + + * Non-maintainer upload. + * Stop using defined on hashes (closes: #816164). + + -- Ian Campbell <i...@debian.org> Sun, 28 Feb 2016 10:14:56 + + flexbackup (1.2.1-6.2) un

Bug#816164: flexbackup: Uses removed defined(%hash) and defined(@array) construct

iption of the patch. ## DP: Bug #XX patch by Ian Campbell <i...@debian.org> ## DP: ## DP: defined(%hash) and defined(@array) have been deprecated for a while and ## DP: are now fatal errors: ## DP: ## DP: Can't use 'defined(%hash)' (Maybe you should just omit the defined()?) at /usr/bi

Bug#813023: flash-kernel: quoting error with bootargs in generic U-Boot boot script

On Sat, 2016-02-20 at 16:58 +0100, Jérémy Bobbio wrote: > > Did you ever see an actual problem related to the lack of quoting this > > bug is about or did you just spot what looked like an error by > > inspection? > > I stumbled on it because I had put in /etc/default/flash-kernel: > >

Bug#813023: flash-kernel: quoting error with bootargs in generic U-Boot boot script

On Sat, 2016-02-20 at 14:41 +0100, Jérémy Bobbio wrote: > Ian Campbell: > > On Sat, 2016-02-20 at 13:29 +0100, Jérémy Bobbio wrote: > > > Ian Campbell: > > > > Lunar -- which platform did you see an issue on and what do the > > > > abo

Bug#813023: flash-kernel: quoting error with bootargs in generic U-Boot boot script

On Sat, 2016-02-20 at 13:29 +0100, Jérémy Bobbio wrote: > Ian Campbell: > > Lunar -- which platform did you see an issue on and what do the > > above > > test commands give in that case? > > The version in Debian: https://packages.debian.org/sid/u-boot-rpi and how

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