Upstream source handling

2015-09-08 Thread Bastian Blank
Moin During the linux packaging BoF at DebConf, Ben asked for usefull upstream source handling. No compeling ones were mentioned. Some years ago (yes, years), I proposed some schema based on submodules, but never got around to actually implement it. I finally managed to do an initial implementa

Bug#798375: marked as done (Stale SCTP sockets / recovery only by reboot)

2015-09-08 Thread Debian Bug Tracking System
Your message dated Tue, 08 Sep 2015 19:06:38 +0100 with message-id <1441735598.2610.9.ca...@decadent.org.uk> and subject line Re: Bug#798375: Stale SCTP sockets / recovery only by reboot has caused the Debian Bug report #798375, regarding Stale SCTP sockets / recovery only by reboot to be marked as

Processed: Re: linux: update "Recommends" of linux on armel/sh4 due to package renamed

2015-09-08 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 linux: update "Recommends" of linux on armel/sh4 Bug #793608 {Done: Ben Hutchings } [linux] linux: update "Depends" of linux on armel/sh4 due to package renamed Changed Bug title to 'linux: update "Recommends" of linux on armel/sh4' from 'linux: update "

Bug#793608: linux: update "Recommends" of linux on armel/sh4 due to package renamed

2015-09-08 Thread Roger Shimizu
Control: retitle -1 linux: update "Recommends" of linux on armel/sh4 due to package renamed

Bug#784688: Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled

2015-09-08 Thread Chad Dougherty
I'm experiencing this bug too. The effect is that one particular guest cannot transmit on its vif. xl.conf has 'autoballoon="off"', /etc/default/grub has 'GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=2048M,max:2048M"' Trying the 'xl mem-set 0 4065' from earlier in the thread results in: root@xen4:/sy

Bug#798375: Stale SCTP sockets / recovery only by reboot

2015-09-08 Thread Harald Welte
Package: src:linux Version: 3.16.5-1 Severity: normal Tags: patch I appear to have run into a SCTP bug that has been around since 2009: http://sourceforge.net/p/lksctp/mailman/message/23492403/ and has been fixed in mainline as part of commit bdf6fa52f01b941d4a80372d56de465bdbbd1d23. However, the

Bug#798311: Processed: Re: Bug#798311: nvidia-kernel-dkms: fails to build against 4.2.0-trunk in experimental

2015-09-08 Thread Luca Boccassi
On Tue, 2015-09-08 at 12:46 +0100, Ben Hutchings wrote: > Control: tag 798311 - wontfix > Control: tag 798311 fixed-upstream patch > > As this has been fixed upstream (commit > 1dadafa86a779884f14a6e7a3ddde1a57b0a0a65) I'm prepared to cherry-pick > that fix. But this doesn't set a precedent that

Bug#798311: Processed: Re: Bug#798311: nvidia-kernel-dkms: fails to build against 4.2.0-trunk in experimental

2015-09-08 Thread Ben Hutchings
Control: tag 798311 - wontfix Control: tag 798311 fixed-upstream patch As this has been fixed upstream (commit 1dadafa86a779884f14a6e7a3ddde1a57b0a0a65) I'm prepared to cherry-pick that fix. But this doesn't set a precedent that I'm going to help with GPL-incompatible modules. Ben. -- Ben Hutc

Processed: Re: Processed: Re: Bug#798311: nvidia-kernel-dkms: fails to build against 4.2.0-trunk in experimental

2015-09-08 Thread Debian Bug Tracking System
Processing control commands: > tag 798311 - wontfix Bug #798311 [linux] nvidia-kernel-dkms: fails to build against 4.2.0-trunk in experimental Removed tag(s) wontfix. > tag 798311 fixed-upstream patch Bug #798311 [linux] nvidia-kernel-dkms: fails to build against 4.2.0-trunk in experimental Adde

Bug#798333: linux: remove loongson 2E/2F support and add octeon to mipsel

2015-09-08 Thread YunQiang Su
Package: src:linux Version: 4.2-1~exp1 We are planning to migrate mips/mipsel to MIPS32R2 from MIPS II. So loongson 2E/2F won't supported any more. So please remove these 2 flavors. On the other hand, please add octeon support to mipsel, as it has been in mips64el now. -- YunQiang Su 0001-rem