Bug#1051577: iproute2: obsolete conffiles

On Tue, 2023-09-12 at 23:13 +0200, Luca Boccassi wrote: > On Mon, 11 Sept 2023 at 15:57, Daniel Gröber > wrote: > > > > Hi Luca, > > > > On Mon, Sep 11, 2023 at 01:06:06PM +0100, Luca Boccassi wrote: > > > > I want to question whether removing these conffiles is a good idea at > > > > all. I'm

Bug#1029513: xss-lock: crashes with core dump on activation

Control: severity -1 important Control: tags -1 +help On Mon, 2023-01-23 at 11:04 -0500, Stuart Freeman wrote: > Calling `xdg-screensaver activate` causes xss-lock to dump core. Thank you for your report. >From the logs it looks like xss-lock is actually hitting an assertion which manifests in

Bug#1016963: Please test u-boot for dreamplug

On Sat, 2023-01-21 at 12:09 -0800, Vagrant Cascadian wrote: > On 2022-12-29, Ian Campbell wrote: > > On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: > > > dreamplug > > > > booting u-boot and Debian both from external mmc > > > >   testing:

Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: > jetson-tk1 testing: 2022.04+dfsg-2+b1  ok unstable: 2022.10+dfsg-2 ok exp: 2023.01~rc4+dfsg-1 ok > Bananapi I don't seem to have a working setup for this any more, sorry. > Cubieboard2  testing: 2022.04+dfsg-2+b1 ok

Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck

On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: > On 2022-12-28, Vagrant Cascadian wrote: > > On 2022-12-22, Vagrant Cascadian wrote: > > > On 2022-08-20, Vagrant Cascadian wrote: > > > > On 2022-08-10, Vagrant Cascadian wrote: > > > > > This bug is just to delay migration to testing

Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup

On Fri, 2021-02-26 at 15:41 +0100, Bernhard Übelacker wrote: > The attached patch is an attempt to grow the buffer size > if the header changes on a new page. > This is just tested for the given crash, nothing more, therefore > there might be side effects on replacing this buffer? It doesn't look

Bug#974828: Fwd: Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup

Control: found -1 3.20.11+dfsg0-2 Control: found -1 3.21.2+dfsg1-1 On Thu, 2021-02-25 at 18:32 +, Ian Campbell wrote: > I'll see if I can upgrade and repeat. Confirmed I see this with both the current bullseye and sid versions of printer-driver-hpcups. Ian.

Bug#974828: printer-driver-hpcups: SIGABRT with "free(): invalid next size (normal)" in HPCupsFilter::cleanup

Package: printer-driver-hpcups Version: 3.20.9+dfsg0-4 Severity: serious Tags: upstream Justification: #972339 Dear Maintainer, I have just filed this crash at https://bugs.launchpad.net/hplip/+bug/1904318 dagon:/tmp# /usr/lib/cups/filter/hpcups 1 debian '' 1 '' print_step_3.hpcups

Bug#963294: cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

On Sat, 2020-06-27 at 12:54 +0200, Gianfranco Costamagna wrote: > Hello Ian, > > > It seems like pybuild has some heuristics for picking the build > plugin > > to use, for me (and buildd) it selects plugin_distutils.py but for > you > > it is selecting plugin_cmake.py. I can't see why. If you

Bug#963294: cmake-format: FTBFS: ./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/./.pybuild/cpython3_3.8/build/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create'

On Sun, 2020-06-21 at 21:52 +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for the report Lucas. I tried reproducing locally with: sbuild -n -A -s --force-orig-source --apt-update -d unstable -v --no-run-lintian

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

On Tue, 2019-09-24 at 10:05 +0100, Mark Hindley wrote: > Ian, > > Thanks for this. > > On Tue, Sep 24, 2019 at 07:28:29AM +0800, Ian Campbell wrote: > > On Fri, 2019-09-20 at 10:16 +0100, Mark Hindley wrote: > > Would it be any help at all of the "dbus client-i

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

On Fri, 2019-09-20 at 10:16 +0100, Mark Hindley wrote: > On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote: > > Hello, > > > > When I looked I elogind a while back I was able to build a package without > > having a public libelogind0, I basically had that in my debian/rules file:

Bug#918465: sunxi-tools installation fils without udev installed

On Sun, 2019-01-06 at 13:32 +0200, Adrian Bunk wrote: > Package: sunxi-tools > Version: 1.4.2+git20181114.6d598a-2 > Severity: serious > > https://piuparts.debian.org/sid/fail/sunxi-tools_1.4.2+git20181114.6d598a-2.log Thanks, I was just working on a fix having spotted the report on

Bug#907298: CVE-2018-15869

On Thu, 2018-10-18 at 11:48 +0800, Shengjing Zhu wrote: > Package: awscli > Followup-For: Bug #907298 > > The corresponding bug on Redhat is closed as > > > Closing this bug as NOTABUG and asked MITRE for rejection, since the issue > > does not seem to be in AWS CLI but in Packer. > > Can we

Bug#907171: prometheus FTBFS:

On Thu, 2018-08-30 at 13:23 +0100, Martín Ferrari wrote: > > Unless the tests are run in their own network namespace (which provides > > some guarantees over what else might be bound to a port, I can't seem > > to find logs which would confirm or deny if a netns was in use here > > though)

Bug#907171: prometheus FTBFS:

On Mon, 2018-08-27 at 19:18 +0100, Martín Ferrari wrote: > On 27/08/18 17:08, Adrian Bunk wrote: > > > How often did you try? > > > > I would say the probability to hit is somewhere around 50%: > > https://tests.reproducible-builds.org/debian/history/prometheus.html > > I just tried 20 builds,

Bug#905574: linux-image-4.17.0-0.bpo.1-amd64: cryptsetup missing in intitramfs for kernel 4.17

On Mon, 2018-08-06 at 23:47 +0800, Ben Hutchings wrote: > On Mon, 2018-08-06 at 14:40 +0100, Ian Campbell wrote: > > On Mon, 2018-08-06 at 21:15 +0800, Ben Hutchings wrote: > > > > Inspecting the initramfs shows that the cryptsetup related > > > > parts are &g

Bug#905574: linux-image-4.17.0-0.bpo.1-amd64: cryptsetup missing in intitramfs for kernel 4.17

On Mon, 2018-08-06 at 21:15 +0800, Ben Hutchings wrote: > > Inspecting the initramfs shows that the cryptsetup related parts are > > missing for 4.17, but still in the 4.16 kernel. > > > > I was able to mitigate the issue by use the cryptsetup packages from > > buster. > > This is strange.

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

Sorry for the unexplained reopen, I expected `bts reopen` to give me the opportunity to write something. AFAICT the upstream bug remains open and [0] indicates that the workaround is only temporary. Neither [1] nor any of the issues it links to as closed seem related and [2] does show any changes

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

On Thu, 2018-05-24 at 09:27 +0100, Ian Campbell wrote: > So I think removing ivtv-utils from Debian is probably the best > answer. > Unless someone from the X-Debbugs-Cc line suggests oherwise I will do > so, lets say on or after 1 June 2018 (a bit over a week from today).

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#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#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#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#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#810070: [Pkg-xen-devel] Bug#810070: Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

Control: close -1 4.6.0-1 On Thu, 2016-02-11 at 16:56 +0100, a...@trash-mail.com wrote: > > If possible it might be interesting to first try the 4.6 hypervisor in > > Stretch, I suspect the xen-hypervisor-4.6-amd64 package will just > install > > on Jessie with no issues since it has no

Bug#814338: armhf-20150422: Format partitions error for ext4/fat/jfs : Unknown symbol __getblk_gfp

On Wed, 2016-02-10 at 15:31 +0100, Gaël Jobin wrote: > Package: installation-reports > Severity: grave > Tags: d-i > Justification: renders package unusable > > I'm trying to run Debian Jessie on ARMv7 using Qemu. I used the initrd.gz > and > vmlinuz available at

Bug#813995: flash-kernel: writes to nand without being aware of bad blocks

Control: reassign -1 mtd-utils So far I see no evidence for the claim that flashcp should not be used for writing to NAND devices in either its --help or its source (it has no man page AFAICS). Having a tool in Debian called "flashcp" which can (according to this report, I haven't checked this

Bug#812327: [Pkg-xen-devel] Bug#812327: xen: initrd booting with xen don't find any harddisks

On Fri, 2016-01-22 at 12:40 +0100, Markus Schraeder wrote: > Package: xen-system-amd64 > Version: 4.6.0-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I installed fresh from ALPHA5, no UEFI, with two disks. Each disk > got a partition for /boot and one for

Bug#812327: [Pkg-xen-devel] Bug#812327: xen: initrd booting with xen don't find any harddisks

(adding the bug back, please keep it ccd) On Fri, 2016-01-22 at 13:05 +0100, Markus Schräder wrote: > What is for you a full log? A dmesg? At least the linux dmesg in both cases, yes. In the Xen case if you can get the Xen dmesg one too (which you may not from a initrd) that would be useful as

Bug#810070: [Pkg-xen-devel] Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

Control: tag -1 +upstream On Wed, 2016-01-06 at 08:36 +, Wolf Karsten Dietz wrote: > Package: xen-hypervisor-4.4-amd64 > Version: 4.4.1-9+deb8u3 > Severity: grave > > Hello, > I am trying to install the XEN Hypervisor on a Debian Jessie Server.   > When I am booting without the Hypervisor,

Bug#787229: [Pkg-xen-devel] Bug#787229: xen-hypervisor-4.4-amd64: xl command hangs on Dell R720

10:31 GMT+02:00 Ian Campbell i...@debian.org: On Sat, 2015-05-30 at 05:23 +0200, Benoît Tonnerre wrote: mai 29 23:20:50 jango xen[1150]: Starting Xen daemons: xenfs xenstored mai 29 22:20:50 jango xen[1150]: Warning: Fake start-stop-daemon called, doing

Bug#786936: [Pkg-xen-devel] Bug#786936: xen-hypervisor-4.4-amd64: Upgrade dom0 from wheezy to jessie on Dell R610 results in dom0 unaccessible with xen_netback issue

Control: reassign -1 linux-image-3.16.0-4-amd64 3.16.7-ckt9-3~deb8u1 On Wed, 2015-05-27 at 08:44 +1000, Andrew Perry wrote: Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from

Bug#787229: [Pkg-xen-devel] Bug#787229: xen-hypervisor-4.4-amd64: xl command hangs on Dell R720

On Sat, 2015-05-30 at 05:23 +0200, Benoît Tonnerre wrote: mai 29 23:20:50 jango xen[1150]: Starting Xen daemons: xenfs xenstored mai 29 22:20:50 jango xen[1150]: Warning: Fake start-stop-daemon called, doing nothing. mai 29 23:20:50 jango xen[1150]: Warning: Fake start-stop-daemon called,

Bug#786936: [PATCHv2 1/3] xen-netback: return correct ethtool stats

Control: fixed -1 4.0-1~exp1 On Wed, 2015-03-04 at 11:14 +, David Vrabel wrote: Use correct pointer arithmetic to get the pointer to each stat. I think this incorrect arithmetic was also responsible for the crash reported in http://bugs.debian.org/786936 which was using the resulting stray

Bug#786882: debian-installer: FTBFS on arm64: can't find dtbs

On Tue, 2015-05-26 at 14:16 +0200, Cyril Brulebois wrote: [...] There seems to be some dtb dance here, and I think the src:linux's having relocated the dtbs under subdirectories is responsible for the FTBFS. Comparing some recent kernels: | kibi@wodi:/tmp/linux-kernel$ debdiff

Bug#783019: kirkwood network console images ask to choose ethernet device

Package: oldsys-preseed Version: 3.15 Severity: grave Tags: patch Doing a test install of jessie on my TS-419 I get asked (via the serial) for a serial port and a ssh password. I happen to have a serial port but these devices mostly do not and are supposed to be headless. I'm using the images

Bug#783019: kirkwood network console images ask to choose ethernet device

On Mon, 2015-04-20 at 19:11 +0100, Ian Campbell wrote: By commenting out that one line things seem to progress in a way which looks promising (i.e. much more spew than above). I think the most plausible solution would be: diff --git a/oldsys-preseed b/oldsys-preseed index f60196f..4cd7138

Bug#777191: grub-efi-amd64 on Debian Jessie cannot boot zfs native root filesystem running the latest git code soon to be 0.6.4 tagged - official release

On Thu, 2015-02-05 at 20:04 -0800, Azeem Esmail wrote: Works with 0.6.3 (v0.6.3-766_gfde0d6d) Does not work with 0.6.3 latest code (dailies version). What are these the versions of? At first reboot, the screen freezes with the following message: mount: mounting /sys on /root/sys failed:

Bug#778810: grub-efi-amd64-bin: boot/bootx86.efi problems

Control: severity -1 important Control: tags -1 +unreproducible +moreinfo On Wed, 2015-02-25 at 12:19 +, Ian Campbell wrote: On Sat, 2015-02-21 at 23:27 +0900, Mark Brown wrote: On Sat, Feb 21, 2015 at 10:31:19AM +, Ian Campbell wrote: On Sat, 2015-02-21 at 11:39 +0900, Mark Brown

Bug#779799: linux: Older patches causing FTBFS on armhf

On Wed, 2015-03-04 at 22:44 +, B.R. Oake wrote: On 04/03/15 22:20, maximilian attems wrote: they are already removed in the repository for experimental, waiting for 3.19.X for the next upload. in any case thanks for the details. Hi, maks; thanks, that's good to know. For the

Bug#778810: grub-efi-amd64-bin: boot/bootx86.efi problems

On Sat, 2015-02-21 at 23:27 +0900, Mark Brown wrote: On Sat, Feb 21, 2015 at 10:31:19AM +, Ian Campbell wrote: On Sat, 2015-02-21 at 11:39 +0900, Mark Brown wrote: Neither of these appears to have disrupted the boot partition though so I'm not sure what's been doing

Bug#778810: grub-efi-amd64-bin: boot/bootx86.efi problems

On Sat, 2015-02-21 at 11:39 +0900, Mark Brown wrote: On Fri, Feb 20, 2015 at 02:32:34PM +, Steve McIntyre wrote: In fact, for EFI just grub-install -v should tell you a lot more. ...and here's the Acer. Thanks. Neither of these appears to have disrupted the boot partition though so

Bug#778810: grub-efi-amd64-bin: boot/bootx86.efi problems

(Steve is probably best placed to say something sensible about this, but he's away at the moment so I'll see if I can avoid sounding too dumb...) On Fri, 2015-02-20 at 14:21 +0900, Mark Brown wrote: Package: grub-efi-amd64-bin Version: 2.02~beta2-20 Severity: critical On a couple of

Bug#778810: grub-efi-amd64-bin: boot/bootx86.efi problems

On Fri, 2015-02-20 at 18:39 +0900, Mark Brown wrote: This is a 1st gen Lenovo Yoga, the other machine that's broken with a fresh install is an Acer Aspire E11 (with BIOS 1.13 IIRC). I can supply more specific data on both if you tell me what you're looking for (I see some talk of a blacklist

Bug#776488: regression: arm map_hardware[] not NULL terminated

On Wed, 2015-01-28 at 18:38 +0100, Cyril Brulebois wrote: dann frazier da...@dannf.org (2015-01-28): On Wed, Jan 28, 2015 at 06:10:49PM +0100, Cyril Brulebois wrote: I was about to push it but you apparently already did; adjusting tags accordingly. Cool, thanks :) Do you +1 me

Bug#764162: Regression with kernel 3.16.7-ckt2-1

On Sat, 2015-01-03 at 09:54 -0200, Rogério Brito wrote: [...] Thanks for the info. Since I can't reproduce it would be useful if you could take this issue to the upstream developers who were involved in the original bug report and work with them directly to find a cure. I may try, but I

Bug#764162: Regression with kernel 3.16.7-ckt2-1

On Wed, 2014-12-31 at 06:08 -0200, Rogério Brito wrote: unarchive 764162 found 764162 3.16.7-ckt2-1 notfound 764162 3.16.7-2 thanks Hi. I have a Kurobox Pro that I use as a NAS and I was affected by the network corruption when the TSO was enabled in versions 3.16 before the version with

Bug#767037: Grub EFI fallback - patches for review

On Sat, 2014-12-20 at 09:45 +0100, David Härdeman wrote: one option that doesn't seem to have been considered would be to create a separate package (let's call it UEFIx) that installs an UEFI binary to EFI/boot/bootx64.efi. That binary could then do what the UEFI BIOS should've done (i.e. look

Bug#773233: linux: Packaging is not correctly enforcing ABI

Source: linux Version: 3.16.7-2 Severity: serious Justification: Not enforcing the ABI will potentially lead to mismatched modules, breakage of stable updates in Jessie etc It appears that we are not currently correctly checking the ABI of kernels against debian/abi/* at build time.

Bug#772983: kirkwood kernel image is too big

On Fri, 2014-12-12 at 18:12 +, Ben Hutchings wrote: Package: src:linux Version: 3.16.7-2 Severity: serious The kirkwood and orion5x kernel images generally have to be installed in flash partitions with a fixed size. Currently we check at build time that vmlinuz is small enough to fit.

Bug#767037: Grub EFI fallback - patches for review

On Mon, 2014-12-08 at 01:36 +, Steve McIntyre wrote: The current package in sid (-17) is unblocked and I think ought to transition tomorrow (or perhaps Tuesday depending on TZ). I propose to upload -18 with this change shortly after that happens. Will you take care of the unblock request

Bug#767037: Grub EFI fallback - patches for review

Control: tag -1 +pending On Wed, 2014-12-03 at 15:27 +, Steve McIntyre wrote: On Wed, Dec 03, 2014 at 09:42:20AM +, Ian Campbell wrote: On Wed, 2014-12-03 at 01:55 +, Steve McIntyre wrote: On Tue, Dec 02, 2014 at 08:36:31AM +, Ian Campbell wrote: On Mon, 2014-12-01 at 13:57

Bug#767037: Grub EFI fallback - patches for review

On Wed, 2014-12-03 at 02:10 +, Steve McIntyre wrote: On Tue, Dec 02, 2014 at 08:51:24AM +, Ian Campbell wrote: On Mon, 2014-12-01 at 13:57 +, Steve McIntyre wrote: I didn't review the text since that seems to have been done already. diff --git a/rescue.d/81grub-efi-force

Bug#767037: Grub EFI fallback - patches for review

On Wed, 2014-12-03 at 01:55 +, Steve McIntyre wrote: On Tue, Dec 02, 2014 at 08:36:31AM +, Ian Campbell wrote: On Mon, 2014-12-01 at 13:57 +, Steve McIntyre wrote: Starting with grub-install-fallback.patch: From e384e597914b6e1b1dcbf96ef6782cf9bcc2313b Mon Sep 17 00:00:00 2001

Bug#767037: Grub EFI fallback - patches for review

On Mon, 2014-12-01 at 13:57 +, Steve McIntyre wrote: Starting with grub-install-fallback.patch: From e384e597914b6e1b1dcbf96ef6782cf9bcc2313b Mon Sep 17 00:00:00 2001 debian/patches/grub-install-extra-removable.patch | 115 ++ Could you send this to

Bug#767037: Grub EFI fallback - patches for review

On Mon, 2014-12-01 at 13:57 +, Steve McIntyre wrote: grub-installer-rescue-UEFI-removable.patch: diff --git a/debian/grub-installer.templates b/debian/grub-installer.templates index e439ad0..a6af2ec 100644 --- a/debian/grub-installer.templates +++ b/debian/grub-installer.templates @@

Bug#737613: Debian Bug 737613: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen

Control: forcemerge 503287 737613 (making $subjet a bit more helpful this time too) On Mon, Nov 24, 2014 at 05:28:59PM +, Ian Campbell wrote: Before investigating any further can either of you confirm whether this still happens with the version of Xen currently in Jessie, which is 4.4.1-3

Bug#770412: grub-xen: fails to install in a chroot

On Fri, 2014-11-21 at 20:34 +, Ian Campbell wrote: Anyway, I'll investigate ischroot or running-in-container which the grub postinst seem to use already (not sure what it does, might be suitable). Neither of those seemed quite right, so here is what I came up with. Passes a local piuparts

Bug#770412: grub-xen: fails to install in a chroot

Control: tag -1 +patch On Sat, 2014-11-22 at 00:39 +, Colin Watson wrote: I only saw this after I sent my previous mail with patch. (also forgot to add the patch tag, doing that here instead) On Fri, Nov 21, 2014 at 12:42:43PM +, Ian Campbell wrote: Looking at https

Bug#770412: grub-xen: fails to install in a chroot

On Fri, 2014-11-21 at 04:02 +0100, Andreas Beckmann wrote: during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. Thanks. It seems like

Bug#770412: grub-xen: fails to install in a chroot

On Fri, 2014-11-21 at 14:31 +0100, Andreas Beckmann wrote: [...snip, useful info, thanks...] There is an ischroot command in debianutils. I take it there is no piuparts overrides in place for the other grub-* packages? No, they work out-of-the-box now. It seems their postinsts are

Bug#764162: [PATCH 0/1] mv643xx_eth: Disable TSO by default

tests using the mvneta driver (Armada 370/38x/XP SoC) pass with no issues. Frankly, I'm a bit puzzled about this, and so any ideas or debugging hints are well received. Hi, Can you try this : It fixes things for me, thanks! Tested-by: Ian Campbell i...@hellion.org.uk

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network

On Fri, 2014-10-31 at 14:29 +0100, Julien D'Ascenzio wrote: Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit : On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network

On Tue, 2014-11-04 at 08:51 +, Ian Campbell wrote: On Fri, 2014-10-31 at 14:29 +0100, Julien D'Ascenzio wrote: Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit : On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network

On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact with the developer of this feature. Tell me if this command resolve your problem Excellent, please let us know how you get on (feel free

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network

On Sun, 2014-10-19 at 14:44 +0200, Julien D'Ascenzio wrote: Since v3.16 kernel a tso feature was introduced in the driver of marvell ethernet. This feature seems to work badly. 3.16-1~exp1 was reported as not exhibiting the issue, but maybe that was just a quick test which got lucky. So this

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network

On Sun, 2014-10-12 at 23:46 +0200, Svenska wrote: If you were able to try 3.16-1~exp1[0] from snapshot.debian.org that might help rule that out. I downloaded linux-image-3.16-trunk-kirkwood_3.16-1~exp1_armel.deb from your link and flashed it into the NAS. I have not done a deeper

Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network

On Mon, 2014-10-06 at 01:21 +0200, Svenska wrote: Package: src:linux Version: 3.16.3-2 Severity: serious Justification: may cause silent data corruption Hello, after upgrading the kernel of my NAS to 3.16-2-kirkwood, I noticed corrupt data on my files. The NAS works as a DHCP client on

Bug#760215: linux-image-3.14-2-kirkwood: Not enough space in MTD RootFS1 (need 9768399 but is actually 9437184)

On Mon, 2014-09-01 at 23:51 +0200, Diego Fernandez Duran wrote: Not enough space in MTD RootFS1 (need 9768399 but is actually 9437184). What do you have in /etc/initramfs-tools/initramfs.conf for MODULES=? I have MODULES=most and the largest initrd I have is 3177784, about 1/3 of yours.

Bug#758581: debian-installer: FTBFS on armhf/network-console: No library provides non-weak __aeabi_unwind_cpp_pr0

On Fri, 2014-08-22 at 05:26 +0200, Cyril Brulebois wrote: Ian Campbell i...@hellion.org.uk (2014-08-22): The Internet(tm) seems to think that __aeabi_unwind_cpp_pr0 comes from libunwind, but the wifi in this hotel is making it a rather slow job to figure out what might be depending

Bug#758581: debian-installer: FTBFS on armhf/network-console: No library provides non-weak __aeabi_unwind_cpp_pr0

On Sun, 2014-08-24 at 21:24 +0100, Ian Campbell wrote: I've timed out for now, but I'll continue prodding as I have the chance... I caught up with Adam Conrad a debconf and he pointed out that __aeabi_* are some weird internal ABI thing which doesn't actually indicate an unresolved symbol. IOW

Bug#758886: closing 758886, closing 758901

close 758886 close 758901 thanks Further information on #756449 shows that u-boot-tools has been reinstated so I think nothing needs to be done for sunxi-tools any more, hence closing both bugs. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of

Bug#758886: sunxi-tools: Requires u-boot-tools to build which is no longer available for powerpc

On Fri, 2014-08-22 at 08:25 -0400, Scott Kitterman wrote: Package: sunxi-tools Version: 1.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) u-boot has dropped powerpc from its supported architectures, so this package will no longer build

Bug#758886: sunxi-tools: Requires u-boot-tools to build which is no longer available for powerpc

at 17:36 +0100, Ian Campbell wrote: On Fri, 2014-08-22 at 08:25 -0400, Scott Kitterman wrote: Package: sunxi-tools Version: 1.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) u-boot has dropped powerpc from its supported architectures

Bug#758581: debian-installer: FTBFS on armhf/network-console: No library provides non-weak __aeabi_unwind_cpp_pr0

On Tue, 2014-08-19 at 00:34 +0200, Cyril Brulebois wrote: | -Object: ./tmp/network-console/tree/lib/libgcc_s.so.1-so-stripped […] | +1170 symbols, 38 unresolved | +Traceback (most recent call last): | + File /usr/bin/mklibs, line 560, in module | +raise Exception(No library provides

Bug#753121: FTBFS, needs to build-depend on libgnutls28-dev / libgcrypt20-dev

On Sun, 2014-07-13 at 14:27 +0100, peter green wrote: libvirt's build-dependencies are uninstallable on current sid: - The following packages have unmet dependencies: libssh2-1-dev : Depends: libgcrypt20-dev but it is not going to be installed E: Build-dependencies

Bug#751816: flash-kernel and dtb

On Fri, 2014-07-11 at 16:33 -0700, Vagrant Cascadian wrote: Control: tags 751816 patch On Tue, Jul 08, 2014 at 08:03:30PM +0100, Ian Campbell wrote: I think the patch below resolves the worst issue and it works for me on cubietruck. The more minor stuff mentioned in that report I'm

Bug#753121: Reported gcc bug as #754548

Control: block -1 by 754548 It didn't look like it had been reported yet so I've reported the gcc bug as #754548. Cheers, Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#753121: gnulib test failure caused by compiler bug

On Sat, 2014-07-12 at 10:00 +0100, Colin Watson wrote: [I need libvirt to be buildable for an upcoming parted transition, so:] On Sat, Jul 05, 2014 at 10:22:05PM +0200, Julian Taylor wrote: the test failure is due to a compiler bug in gcc-4.9:

Bug#751816: Unresolved issues with bootargs handling

Package: flash-kernel Version: 3.20 Severity: serious X-Debbugs-CC: debian-...@lists.debian.org The new boot.scr bootargs handling needs some work before it is suitable for Jessie, so filing this as an rc bug. See the thread starting at https://lists.debian.org/debian-arm/2014/06/msg00064.html

Bug#746058: sqlite: FTBFS: /bin/sh: 1: tclsh: not found

Package: src:sqlite Followup-For: Bug #746058 As well as the tclsh issue the log also shows: sort: cannot read: +4: No such file or directory Which seems to be down to the use of an obsolete command line syntax. Seemingly the supported syntax is sort -k 4. Ian. -- System Information: Debian

Bug#737613: [Pkg-xen-devel] Bug#737613: xen-hypervisor-4.3-amd: Xen not loading dom0 on Jessie - FATAL error on running /etc/init.d/xen

On Tue, 2014-02-04 at 09:57 +, Steve Hnizdur wrote: FATAL: Failed to initialize dom0 state: iappropriate ioctl for device. IME this is usually down to a mismatch between the dom0 userspace tools and the hypervisor, but if this is a fresh system then I see no reason for that to be the case.

Bug#740219: FTBFS on armel: modules in more than one package

On Thu, 2014-02-27 at 03:07 +, Wookey wrote: End of the build log at: https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armelver=3.13.4-1stamp=1393291598 some modules are in more than one package debian/jffs2-modules-3.13-1-orion5x-di

Bug#740219: FTBFS on armel: modules in more than one package

On Fri, 2014-02-28 at 11:26 +0100, Arnaud Patard wrote: Ian Campbell i...@hellion.org.uk writes: On Thu, 2014-02-27 at 03:07 +, Wookey wrote: End of the build log at: https://buildd.debian.org/status/fetch.php?pkg=linuxarch=armelver=3.13.4-1stamp=1393291598 some modules

Bug#736872: busybox: zcat does not decompress file which do not have a .gz suffix

On Tue, 2014-01-28 at 13:07 +0400, Michael Tokarev wrote: Uncortunately, this whole mess around compression introduces another issue. After the 2 fixes for this bug, busybox zcat happily accepts uncompressed input and behaves like regular cat, while original zcat refuses to accept uncpmpressed

Bug#736872: busybox: zcat does not decompress file which do not have a .gz suffix

Package: busybox Version: 1:1.22.0-2 Severity: critical Justification: breaks the whole system The zcat applet seems to behave like cat unless the input file has a .gz suffix: Given two identical files (compressed string Hello World), one with a .gz suffix and one without: $ file test test.gz

Bug#736872: busybox: zcat does not decompress file which do not have a .gz suffix

On Mon, 2014-01-27 at 20:58 +, Ian Campbell wrote: http://git.busybox.net/busybox/commit/?id=b664f740d90880560ce46b11f766625341342e80 looks interesting... but not as interesting as http://git.busybox.net/busybox/commit/?id=7c47b560a8fc97956dd8132bd7f1863d83c19866 Ian. -- To UNSUBSCRIBE

Bug#736872: busybox: zcat does not decompress file which do not have a .gz suffix

http://git.busybox.net/busybox/commit/?id=b664f740d90880560ce46b11f766625341342e80 looks interesting... -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#736872: busybox: zcat does not decompress file which do not have a .gz suffix

On Mon, 2014-01-27 at 21:01 +, Ian Campbell wrote: On Mon, 2014-01-27 at 20:58 +, Ian Campbell wrote: http://git.busybox.net/busybox/commit/?id=b664f740d90880560ce46b11f766625341342e80 looks interesting... but not as interesting as http://git.busybox.net/busybox/commit/?id

Bug#735254: flash-kernel: QNAP TS-212 doesn't boot with 3.12-1-kirkwood and flash-kernel 3.12

Control: reassign -1 src:linux Control: forcemerge 735172 -1 On Tue, 2014-01-14 at 05:50 +, Ruben Silveira wrote: Description and steps to reproduce: - QNAP TS-212 (cpuinfo = 'QNAP TS-119/TS-219') with 3.11-2-kirkwood and flash-kernel 3.12; - Installed 3.12-1-kirkwood (update-initramfs

Bug#721485: flash-kernel: flash_kernel_set_root waits for stdin in a particular case, which makes the installer hang

clone 721485 -1 reassign -1 partman-base retitle -1 partman-base: /dev/disk links are not refreshed on dreamplug after repartitioning found -1 165 thanks On Sun, 2013-09-01 at 10:51 +0200, Paul Kocialkowski wrote: I reached this case when using and formating an ext2 root partition: it seems

Bug#701744: Xen netback regression

On Thu, 2013-07-04 at 04:42 +0100, Ben Hutchings wrote: I must apologise for the poor response to this bug report. It should have been fixed long ago, and it was fixed upstream in April. While there are an overwhelming number of bugs against the kernel, this regression should have been

Bug#701744: Xen netback regression

On Sat, 2013-07-06 at 08:10 +0100, Ian Campbell wrote: wheezy sha1: Replaced with a version built on the correct baseline: abbf6e229470de2848b643c846491ce4b8ec001d linux_3.2.46.orig.tar.xz e2168426623b7f518a124f9768d83d4a782ecfa6 linux_3.2.46-1+deb7u1~ijc0.debian.tar.xz

Bug#701744: Stable backport requested

reassign 701744 src:linux found 701744 2.6.32-48 found 701744 3.2.41-2+deb7u2 thanks FYI I have requested[0] an upstream stable backport of the fixes for this issue, which is in the kernel not the hypervisor. Ian. [0] http://marc.info/?l=linux-netdevm=136973447431251w=2 -- To UNSUBSCRIBE,

Bug#705124: Info received (base: Filesystem corruption issue)

On Tue, 2013-04-16 at 09:39 -0400, Anthony Sheetz wrote: What does dom0 dmesg say about barriers on that device/filesystem? Nothing in dmesg about barriers on any file system. 'dmesg|grep barrier' returns nothing. I've just realised that the message in domU is from the

Bug#705124: Info received (base: Filesystem corruption issue)

On Mon, 2013-04-15 at 15:02 -0400, Anthony Sheetz wrote: Current status. New laptop hard drive purchased and installed. Thanks! Experiment 1 [] Result: 4.9Gb file transferred fine! Experiment 2 [...] Result: successful transfer. Great news. Experiment 3 Change from above (2): LVM

Bug#705124: base: Filesystem corruption issue

On Wed, 2013-04-10 at 08:17 -0400, Anthony Sheetz wrote: Steps to reproduce: Install Debian Testing from Netinstall CD, amd64. Choose LVM and Full Disk Encryption, with a separate /home Resize /home to be 80GB Install openswan, connect to remote network Install xen Set up a virtual machine

Bug#705124: [Pkg-xen-devel] Bug#705124: downgrading, we would like to upgrade our developers to Testing. However, this bug prevents us from doing so, and would prevent us from migrating to 7.0 when it

On Sat, 2013-04-13 at 19:48 +0800, Thomas Goirand wrote: On 04/10/2013 10:49 PM, Anthony Sheetz wrote: ___ Pkg-xen-devel mailing list pkg-xen-de...@lists.alioth.debian.org

  1   2   >