Bug#781927: collab-maint
Hello Antti, FWIW collab-maint a.k.a. Aloith can be used by non-DM and non-DD. Having Aloith account is enough. Cheers Geert Stappers P.S. Sorry for not replying on the e-mail of last week. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#789612: now titled
Control: retitle -1 gcc-5-mips-32-fpxx Control: tag -1 patch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788634: debian-installer: Accepting a preseed URL from DHCP allows attacker to hijack installation
+Template: preseed/accept_preseed_from_DHCP +Default: false +_Description: Accept a preseed URL from the DHCP server? :-( We have allready 'auto-install/enable' ( 'auto' for short ) See also https://www.debian.org/releases/jessie/mips/apbs02.html.en#preseed-auto Geert Stappers signature.asc Description: Digital signature
Bug#789475: udhcpc: valid rfc1123 hostname recognized as bad
Control: tag -1 moreinfo On Sun, Jun 21, 2015 at 02:14:17PM +0200, Bodo Eggert wrote: The valid hostname 52-54-0-12-34-56 is recognized as bad while it should be valid according to rfc1123 (Section 2.1). What programma and/or device did recognize 52-54-0-12-34-56 as bad? How was the error encountered? Any error messages? Please elaborate what the reason for this bugreport is. Capture of the DHCP reply: be1.lrz.bootps 192.168.7.107.bootpc: BOOTP/DHCP, Reply, length 300, xid 0x4cc35164, Flags [none] Vendor-rfc1048 Extensions DHCP-Message Option 53, length 1: ACK Hostname Option 12, length 16: 52-54-0-12-34-56 That is content from a network packet sent by a DHCP server, which might be configured for providing such hostname. Please provide more information. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788634: debian-installer: Accepting a preseed URL from DHCP allows attacker to hijack installation
control: tag -1 mordac I don't think handwaving and tagging wontfix is the right play here. Now tagging with 'mordac'. For those new to Mordac, get a first impression at http://dilbert.com/strip/2007-11-16 And http://dilbert.com/search_results?terms=Mordac for a complete overview of Mordac, the preventer of information services. In other words: How to cope with nonsense like security is more important than usability? Further discussion should go to d-boot@l.d.o., Reply-To is set for it. And ignoring this bugreport is also fine. KiBi is right, it is code that matters. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788634: debian-installer: Accepting a preseed URL from DHCP allows attacker to hijack installation
On Sat, Jun 13, 2015 at 04:32:04PM +0100, Aliz Hammond wrote: Due to this, an attacker on the local network can spoof a DHCP responce pointing to their own preseed file, which can do all sorts of mischief (such as adding users or executing commands). So the actual problem is that the local network is compromised. I'm not sure of the best way to mitigate this, without annoying people who use this feature. Perhaps a kernel commandline arg to specifically enable preseed via DHCP is a good idea? A good idea is getting the local network to a state where it can be trusted to use DHCP at all. Groeten Geert Stappers Who considered control: tag -1 wontfix -- Leven en laten leven signature.asc Description: Digital signature
Bug#788156: debian-installer: Debian-Installer does not detect disks HP G9
control: -1 moreinfo On Mon, Jun 08, 2015 at 03:23:00PM -0700, Sean Mottles wrote: } an HP DL360 Gen9 server, Smart Array P440ar Controller,Version 2.14 Please provide more information. Such as: * PCI ID * name of kernel module, a special the name of the kernel module with the working version Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788156: detect disks HP G9
Control: tag -1 moreinfo stop On Mon, Jun 08, 2015 at 11:03:03PM +, Debian Bug Tracking System wrote: Processing control commands: -1 moreinfo Unknown command or malformed arguments to command. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788156: debian-installer: Debian-Installer does not detect disks HP G9
On Mon, Jun 08, 2015 at 05:32:05PM -0700, Sean M wrote: Debian-Installer syslog from the broken version: Jun 8 21:34:25 kernel: [ 78.080247] scsi0 : hpsa Jun 8 21:34:25 kernel: [ 78.081628] hpsa :03:00.0: RAID device c0b3t0l0 added. Jun 8 21:34:25 kernel: [ 78.081793] scsi 0:3:0:0: RAID HP P440ar 2.14 PQ: 0 ANSI: 5 Jun 8 21:34:25 kernel: [ 78.083510] scsi 0:3:0:0: Attached scsi generic sg0 type 12 Jun 8 21:34:26 check-missing-firmware: looking at dmesg again, restarting from \[9.164044\] Jun 8 21:34:26 check-missing-firmware: timestamp found, truncating dmesg accordingly Jun 8 21:34:26 check-missing-firmware: saving timestamp for a later use: [ 78.083510] Jun 8 21:34:26 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jun 8 21:34:26 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping Jun 8 21:34:26 check-missing-firmware: no missing firmware in loaded kernel modules Check (missing) firmware Thanks, Sean Regards Geert Stappers while doing bug triage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768073: status request
Hello, What is the status of the ITP of lxd -- The Linux Container Daemon? At https://linuxcontainers.org/lxd/downloads/ I couldn't find the Ubuntu packaging stuff. Groeten Geert Stappers -- $ host people.progress-technologies.net Host people.progress-technologies.net not found: 3(NXDOMAIN) signature.asc Description: Digital signature
Bug#787739: ITP: plip -- fully automated protein-ligand interaction profiler
On Fri, Jun 05, 2015 at 02:08:37PM +0200, Simon Richter wrote: On 05.06.2015 11:25, Alex Mestiashvili wrote: This might be confusing to old people. PLIP is a protocol for transporting IP packets over the parallel port. I agree that the name is a bit ambiguous, but I see a couple of reasons why it is still might be ok: Yes, I also think it is probably okay -- I just wanted to mention that it might be confusing at first. In other words: 'plip' is a good name for the protein-ligand interaction profiler Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787117: debootstrap: missing wily
On Thu, May 28, 2015 at 07:59:24PM +, Tianon Gravi wrote: I'd attach a patch, but for a symlink it's going to be longer than just mentioning that the fix is ln -s gutsy scripts/wily. :) Mmm, I would expect something like ln -s gutsy wily So 'gutsy' and 'wily' in the same directory. Groeten Geert Stappers Mostly in a 'seen the bugreport' -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783089: Workaround, amendum
On Wed, May 06, 2015 at 10:01:29AM +0200, jean-y...@lenhof.eu.org wrote: Le 2015-05-05 18:56, Geert Stappers a écrit: FWIW: I think that at '*' has to be something like tar xf data.tar Hum...Hum... True that I forget something... my bad. This should be more something like this : xzcat data.tar.xz | tar xvf - Yes. Minor advice make it xzcat data.tar.xz | tar xf - So without the verbose option. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783089: Workaround, amendum
On Tue, May 05, 2015 at 04:11:14PM +0200, jean-y...@lenhof.eu.org wrote: Hi, As a workaround, you can : - Boot on the Debian CD - Select Rescue - Change to a terminal - cd /tmp - ar x /cdrom/pool/main/l/linux/linux-image-3.16.0-4-amd64_3.16.7-ckt7-1_amd64.deb - xzcat data.tar.xz * - cd /tmp/lib/modules/3.16.0-4-amd64/kernel/drivers/md/ - insmod raid10.ko - insmod dm-raid.ko - change back to first console and select your root lv FWIW: I think that at '*' has to be something like tar xf data.tar Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783982: D-i: preseed from floppy no longer works !
On Sun, May 03, 2015 at 07:50:54AM +0300, Alexey Eromenko wrote: I'd prefer not to introduce any new dependecies, for portability reasons. cpio is available on any *NIX system. Having the 'preseed.cfg' in the initrd means there is no need to mount a device (like a floppy or second CDROM) See https://wiki.debian.org/DebianInstaller/NetbootFirmware for an example about adding to the cpio initrd. Would like to have floppy support back. - Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#784148: base-installer: NTP daemon should be installed on any system missing an RTC
Debian installations on hardware with no (battery-backuped) RTC is likely an installation that hasn't network connection. So please do not push (too hard) for you MUST allway known what time it is Make it possible to do installs on hardware without RTC and no access to a NTP server. Installing fake-hwclock https://packages.debian.org/stretch/fake-hwclock on the absence of the a RTC Avoiding filesystem checks when no RTC present would also be good. Simular as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767040 Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#784148: base-installer: NTP daemon should be installed on any system missing an RTC
On Sun, May 03, 2015 at 05:23:30PM +0100, Ben Hutchings wrote: On Sun, 2015-05-03 at 17:40 +0200, Geert Stappers wrote: Debian installations on hardware with no (battery-backuped) RTC is likely an installation that hasn't network connection. What makes you think that? embedded systems, cheap embedded systems that have no real time clock, those are the ones that I expect to be without network connection. Example given: stand-alone mediaplayers. My actual point: Do not assume when RTC is absence, then NTP server will be present. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#783982: D-i: preseed from floppy no longer works !
On Sat, May 02, 2015 at 01:09:34AM +0300, Alexey Eromenko wrote: On Fri, May 01, 2015 at 11:28:32PM +0200, Geert Stappers wrote: I think you are looking for providing a preseed file, hence my advice https://www.google.nl/search?q=virtualbox+host+http+server+for+guests You're correct in that I'm looking to provide preseed file. But host-side HTTP server won't work for my needs, unless VirtualBox has it integrated. My technology is aimed at people, who require *zero* configuration, and should work across all hosts. Like click, click, click... In my words: In an attempt to make some technology available your are hidding other technology with old technology like floppies. Basically I need very minimal (and portable) host-side logic (and move as much complexity into the guest as possible). Do an attended install. Verify that reading from floppy is possible. That is important. It proofs that the Virtualbox host provides a floppy disk controller and that the Vbox guest has a kernel kernel for the f.d.c. Also it shows there is /dev/fd0 (IIRC) Well... you'r right ! /dev/fd0 is the problem ! Yes, I ensured, that VM has floppy controller configured, plus floppy.img inserted. Debian 8 (mini-)kernel (inside amd64-DVD) does NOT see /dev/fd0 ! (part of debian-installer); This works just fine with Debian 6 and 7 ! Post-install Debian 8 kernel _does_ see /dev/fd0, can loop-mount and can read files from it. (after installing from Debian 8 amd64-DVD), so no problem here. Okay, do `ls -l /dev/fd0` in the working system and write down the major and minor node numbers. Next is reading the manaul page of mknod(1). Create a fake /dev/fd1, or even a real /dev/fd1 if virtualbox can provide a second floppy drive. Reboot in the vbox guest into Debian Installer. Get to a shell for commandline access. Use your new skills to create /dev/fd0 Then these commands mkdir floppy mount /dev/fd0 floppy And please report back The natural question: Are those kernels different ? Yes. Think several generations technology, example given i386, i486 and i586. All generations can boot with the oldest. Or thihk All those drivers for audio, blue tooth, printers image scanners. Install without those drivers. (I always assumed it is the *same* kernel) :-) It seems the mini-kernel does not provide me with /proc/config.gz, so I have no clue what's included and what's excluded. How can I check ? Debian ships kernel with the config file. Thanks for finding the problem ! I want the name and location of kernel config of d-i.:-) Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#783995: [feature-request] Please allow to view kernel config via /proc/config.gz in all Debian kernels
On Fri, May 01, 2015 at 11:50:31PM +0100, Ben Hutchings wrote: On Sat, 2015-05-02 at 01:39 +0300, Alexey Eromenko wrote: As far as I'm aware it's stable feature, and there is no downside from enabling it. [...] There is a downside: it consumes more memory and disk space (though not that much). And there is no need for it. Debian provides allready the information of zcat /proc/config.gz in a file with a name like config-VERSION-VER-ARCH which gets installed in /boot Example given grep -i -e floppy -e fdc /boot/config* Groeten Geert Stappers Who thinks that this bugreport should be closed or marked as 'WONTFIX' -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783982: D-i: preseed from floppy no longer works !
control tag -1 moreinfo stop I need this feature to enable unattended install of Debian 8 VM in VirtualBox (vbox-unattended feature), where preseed script gets loaded from virtual floppy. https://forums.virtualbox.org/viewtopic.php?f=10t=46798 | Unattended Guest OS Install - vbox-unattended | (a.k.a. coffee break system installation) | Postby Technologov » 19. Dec 2011, 15:38 Working with debian-8.0.0-amd64-DVD-1.iso. Official Jessie 8.0 Debian installer. Please fix preseed/file=/floppy/preseed.cfg: First find out where it is broken. Do an attended install. Verify that reading from floppy is possible. That is important. It proofs that the Virtualbox host provides a floppy disk controller and that the Vbox guest has a kernel kernel for the f.d.c. Also it shows there is /dev/fd0 (IIRC) Report you findings. Sent them to 783...@bugs.debian.org Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783982: D-i: preseed from floppy no longer works !
On Fri, May 01, 2015 at 10:55:36PM +0300, Alexey Eromenko wrote: As a separate, but related question: is it possible to load preseed script from 2nd CDROM ? (IDE Secondary Slave, or SATA 2nd CD...) I tried preseed/file=/cdrom2/preseed.cfg, but it didn't work. I think you are looking for providing a preseed file, hence my advice https://www.google.nl/search?q=virtualbox+host+http+server+for+guests To get 2nd CDROM + preseed/file=/cdrom2/preseed.cfg working: * Detect what 2nd CDROMs is ( IDE Secondary Slave, or SATA 2nd CD... ) * mount -t iso9660 -o ro /dev/detectedCDrom /cdrom2 all done on a computer that is about be installed. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#783083: [pkg-bacula-devel] Bug#783083: bacula-director-common: Bacula director has problems with kernel linux-image-3.16.0-0.bpo.4-amd64 (v3.16.7-ckt7-1~bpo70+1)
On Tue, Apr 21, 2015 at 09:38:11PM +0200, Artur Linhart wrote: Package: bacula-director-common Version: 5.2.6+dfsg-9 Severity: normal The director is not able under some circumstances communicate with Bacula communication console, after (service) restart it is not able to listen on the specified configured port even if the service seems to be running. What to do to reproduce the not able to listen? Please elaborate. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764982: Backports when the danger is contrib and non-free
On Mon, Apr 20, 2015 at 11:00:09PM +0200, Paul van der Vlis wrote: Op 20-04-15 om 22:19 schreef Geert Stappers: Op 20-04-15 om 09:39 schreef Turbo Fredriksson: Besides, we had this exact argument for weeks (months) about contrib and non-free 'in the day'. Eventually, _that_ (amongst others) won the argument - it's not an official part of Debian GNU/Linux! I had a closer look at /etc/apt/sources.list of a recent installed machine. And sadly discovered that 'contrib' and 'non-free' were enabled ... I have installed with RC1 and with RC2, but I cannot remember that I have seen that! Maybe you have used a nightly build? I am interested who did this when you are correct. I don't know how it happened. Facts: * /var/log/installer/lsb-release says 'build 20150324' * the is from 2015-03-30 Enabling non-free and contrib in sources.list is a very stupid idea because Debian is about DFSG software and non-free is not DFSG, and contrib needs non-DFSG software. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764982: Backports when the danger is contrib and non-free
On Mon, Apr 20, 2015 at 09:39:41AM +0200, Turbo Fredriksson wrote: On Apr 20, 2015, at 7:01 AM, Christian PERRIER wrote: I really don't think this is a good idea and I'm this close to re-close the bug report. Well, I asked a fair question I think. I knew the answer (but I could be wrong - I haven't been paying attention to Debian GNU/Linux matters in years): Is anything but main part of the official Debian GNU/Linux distribution? If not, it should not be enabled _by default_. Right? So I still think it can, and should, be closed. Done. If not for all the other reasons, then that? There have, in any case, been numerous cases against enabling it, but NONE for enabling it. And no, I want it and I use it is NOT an opinion FOR it! :) Besides, we had this exact argument for weeks (months) about contrib and non-free 'in the day'. Eventually, _that_ (amongst others) won the argument - it's not an official part of Debian GNU/Linux! I had a closer look at /etc/apt/sources.list of a recent installed machine. And sadly discovered that 'contrib' and 'non-free' were enabled ... Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764982: Backports, where is the danger (why the FUD)
On Sun, Apr 19, 2015 at 07:35:21PM +0200, Turbo Fredriksson wrote: On Apr 19, 2015, at 7:15 PM, Cyril Brulebois wrote: Do you see that ?but?? That's exactly why it's not safe to have this turned on by default. Thank you KiBi! I defiantly don't want back ports enabled by default! _I_ don't trust them (even if the rest of the world do - I have the right to my opinion after all). And just because you, Paul, do trust them and enable them on everything, doesn't mean everyone else is comfortable with it. There is a potential risk with them (as KiBi pointed out) so having them in the file, but commented out (don't know if that was the solution, or removing them all together) seems like the most prudent option. What is the danger of having backports (default) enabled? I do see the FUD and I want to call it Fear Uncertainty and Doubt! And it is that I want to go beyond the FUD. So what is the danger that I do see yet? I also see this as a non-issue (and yet I had to voice my opinion - I must be more bored than I thought :). I wasn't bored and did read https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764982#15 So now I have a nice opportunity to quote Joey Hess apt won't install newer versions from backports unless the user explicitly specifies -t $suite-backports previous in this BR Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764982: Backports, 2B || !2B
reopen 764982 stop On Sun, Apr 19, 2015 at 07:13:36PM +0200, Geert Stappers wrote: control reopen -1 stop BR reopened for futher discussion. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764982: Backports removed from sources.list ;-(
control reopen -1 stop On Sun, Apr 19, 2015 at 05:44:12PM +0200, Paul van der Vlis wrote: Hello, I saw backports has been removed as default setting from sources.list in Jessie RC3. I am very disappointed by this last minute change, without much discussion so far I know. I did not know about this bug. BR reopened for futher discussion. from the changelog: | Changes: | apt-setup (1:0.97) unstable; urgency=medium | . |* Stop enabling backports by default (Closes: #764982). Rationale: | - Packages in the base suite are preferred to the ones in the | backports suite so one needs to specifically ask for the version | from backports. | - That isn't true for packages which are only available in the | backports suite. | This means one could possibly install such packages without even | noticing they're not fetched from the base suite; and that seems | a dangerous default. That danger is installing an old package. That danger only occures when there is NO new package. A bigger danger, a bigger disadvantage, is NOT getting the package installed. (not getting a package installed that _is available_ in backports ) The danger is no danger, the bigger danger is. In my opinion it's very good when backports is default in sources.list. Typical use cases for having backports enabled: * Package became available after the release ( this will happen more and more ) * Package was too late for the freeze ( that has happend allready ) About the | This means one could possibly install such packages without even | noticing they're not fetched from the base suite; and that seems | a dangerous default. There is much doubt in 'could possibly' and 'seems a dangerous default' Please go beyond the doubt and install available packages. And let us find out which packages are missing in the base suite. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781511: debian-installer-8-netboot-i386: fails to mount ext4 file system at / for root on /
On Mon, Mar 30, 2015 at 11:35:24AM +0200, Wolfgang Schweer wrote: Package: debian-installer-8-netboot-i386 Version: 20150107 'The attempt to mount a file system with type ext4 in LVM VG vg_system, LV root at / failed.' Same with d-i-8-netboot-amd64, I guess. Yes, (sadly) the same with amd64. So confirming this BR. Additional information from me: * Real hardware * SSD, Solid State Disk * `cat /proc/partitions` and `fdisk -l /dev/sda` show '/dev/sda1' * manual `mount /dev/sda1 /media` returns 'mount: mounting /dev/sda1 on /media failed: Invalid argument' * `mount -t ext4 /dev/sda1 /media` returns 'mount: mounting /dev/sda1 on /media failed: No such device' * that gives in `dmesg`: '[ seconds.started ] ext4: Unknown symbol pagecache_get_page_fixed (err 0)' Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781511: debian-installer-8-netboot-i386: fails to mount ext4 file system at / for root on /
control: -1 merge 779651 stop On Mon, Mar 30, 2015 at 04:56:43PM +0200, Geert Stappers wrote: `mount -t ext4 /dev/sda1 /media` returns 'mount: mounting /dev/sda1 on /media failed: No such device' that gives in `dmesg`: '[ seconds.started ] ext4: Unknown symbol pagecache_get_page_fixed (err 0)' That is also reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779651 And FWIW in https://lists.debian.org/debian-boot/2015/03/msg00525.html are new boot images announced. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#781511: debian-installer-8-netboot-i386: fails to mount ext4 file system at / for root on /
control: merge -1 779651 stop Package from http://incoming.debian.org/debian-buildd/pool/main/d/debian-installer-netboot-images/ ( debian-installer-8-netboot-amd64_20150324_all.deb ) gets beyond the error! Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#781511: debian-installer-8-netboot-i386: fails to mount ext4 file system at / for root on /
Control: -1 close stop On Mon, Mar 30, 2015 at 06:46:17PM +0200, Wolfgang Schweer wrote: On Mon, Mar 30, 2015 at 05:43:14PM +0200, Geert Stappers wrote: Package from http://incoming.debian.org/debian-buildd/pool/main/d/debian-installer-netboot-images/ ( debian-installer-8-netboot-amd64_20150324_all.deb ) gets beyond the error! Same here with debian-installer-8-netboot-i386_20150324_all.deb Thanks reporting. Groeten Geert Stappers Closing this bugreport -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779794: lspci ( on multiple lines )
On Wed, Mar 04, 2015 at 02:43:48PM -0600, Shane Roach wrote: $ lspci [all on a single line] $ lspci 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 02:00.0 VGA compatible controller: NVIDIA Corporation Device 13c0 (rev a1) 02:00.1 Audio device: NVIDIA Corporation Device 0fbb (rev a1) 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 13) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779010: local in version
Rumours says that version number in the changelog should contain the string 'local' to get a build without (ABI) checks Please confirm, preferable in the README.source Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776595: Raar probleem met Gnome in Jessie
Contro: tags -1 + patch On Mon, Feb 02, 2015 at 09:41:00PM +0100, Frans Spiesschaert wrote: Ik heb het probleem voorgelegd aan de debian ontwikkelaars van Gnome (https://lists.debian.org/debian-gtk-gnome/2015/02/msg0.html) en het antwoord is dat ze het probleem ernstig genoeg vinden en dus graag een patch krijgen. --- gnome-menus-3.13.3-original/po/nl.po +++ gnome-menus-3.13.3/po/nl.po @@ -92,7 +92,7 @@ #: ../desktop-directories/Utility.directory.in.h:1 msgid Accessories -msgstr Hulpmiddelen +msgstr Accessoires #: ../desktop-directories/Utility.directory.in.h:2 msgid Desktop accessories signature.asc Description: Digital signature
Bug#418519: Processed (with 1 errors): patches welcome
Control: tags -1 - wontfix Making way for propellor or/and other changes On Sat, Jan 03, 2015 at 08:03:06AM +, Debian Bug Tracking System wrote: Processing control commands: -1 - wontfix Unknown command or malformed arguments to command. Sorry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#418519: patches welcome
Control: -1 - wontfix But I can't implement it simply Patches welcome -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#418519: Reason for having raw disk as physical volume
When the only disk is completely LVM, then boot loaders should also have support for it. When the computer is Only LVM also. workaround: use an additional dedicated boot disk[1] Groeten Geert Stappers Note [1] something that bootROM ( BIOS ) supports signature.asc Description: Digital signature
Bug#760032: name of the program
+ With program asterisk-config-custom in the asterisk package,
+ you can create an asterisk-config replacement package.
I also still don't like the name of the program. Any better suggestions?
asterisk-config-custom-prepare
That is also based upon the Asterisk package dependency
asterisk-config (= ${source:Version}) | asterisk-config-custom
Regards Geert Stappers
Who can't tell if it is a better suggestion ...
--
Leven en laten leven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760032: minimal config packaged
On Sun, Aug 31, 2014 at 09:17:18AM +0300, Tzafrir Cohen wrote: For a specialized installation of mine I maintain a certain minimalistic package that provides asterisk-config-custom. Just for the kicks I had modules.conf disable automatic module loading. Building yet another package was very simple with dh. I see no reason to try to script it (though others may disagree). Having a skeleton of a minimalistic package may be useful and may save work as a better starting point: an empty configuration is not usable. Would a directory with minimal working configuration be of use? I think both, minimal configuration and get it in a package, are good. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760032: only placeholders
On Wed, Dec 31, 2014 at 11:42:41AM +0200, Tzafrir Cohen wrote: * The configuration generated by it is not usable. I don't think asterisk will even start that way. But I didn't check it yet. Unlikely that is will work. It are only placeholders. Use asterisk-config-custom sync to get a working config for being packaged. But fine tuning that could be done later. Yes. Next year. ( It is 2014-12-31 in my time zone ;-) Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#773402: ITP: libgaminggear -- Provides functionality for gaming input devices
On Wed, Dec 17, 2014 at 06:46:56PM -0500, Tristan Schmelcher wrote: Package: wnpp Severity: wishlist Owner: Tristan Schmelcher tristan_schmelc...@alumni.uwaterloo.ca * Package name: libgaminggear Version : 0.5.0 Upstream Author : Stefan Achatz erazor...@users.sourceforge.net * URL : https://sourceforge.net/projects/libgaminggear/ * License : GPL2 Programming Lang: C Description : Provides functionality for gaming input devices libgaminggear is a support library for userspace device input drivers to facilitate implementation of advanced features commonly found in gaming peripherals, such as macros. This library needs to be packaged in order to package roccat-tools. I am planning to package and maintain both of them (I will need a sponsor). I might be interrested in sponsoring both. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#773890: flash-kernel: No entry for BeagleBone Black when running 3.18 kernel
Support for alternative machine name for BeagleBone Black.
The old name was ambiguous with the original BeagleBone (often called
White),
detect if booting on a BeagleBone white and print an error since the DTB
will
be wrong. We don't currently support the White. (Closes: #773890, which
contains full background).
diff --git a/bootscript/bootscr.beaglebone b/bootscript/bootscr.beaglebone
index a0e5121..1d079f8 100644
--- a/bootscript/bootscr.beaglebone
+++ b/bootscript/bootscr.beaglebone
euh
git mv bootscript/bootscr.beaglebone{,black}
@@ -1,4 +1,14 @@
-# boot script for BeagleBone
+# boot script for BeagleBone Black
+
snip/
--- a/db/all.db
+++ b/db/all.db
@@ -581,6 +581,7 @@ Mtd-Initrd: ramdisk
Bootloader-Sets-Incorrect-Root: yes
Machine: TI AM335x BeagleBone
+Machine: TI AM335x BeagleBone Black
Kernel-Flavors: armmp
DTB-Id: am335x-boneblack.dtb
snip/
Groeten
Geert Stappers
--
Leven en laten leven
signature.asc
Description: Digital signature
Bug#760032: debian/patches/asterisk-config-custom.patch
Control: tags -1 + patch
Hello Asterisk maintainers,
Find attached two files, asterisk-config-custom.patch and debiancontrol.patch
asterisk-config-custom.patch
This file is for in the directory debian/patches
It creates the file contrib/script/asterisk-config-custom
and manual page contrib/scripts/asterisk-config-custom.8
Plus updates toplevel Makefile so they will be installed.
Activate it will be some something like
echo asterisk-config-custom.patch debian/patches/series
or
quilt import -P asterisk-config-custom.patch path/to/file
Updating debian/changelog would be something like
debchange Added asterisk-config-custom (Closes: #760032)
debiancontrol.patch
---
A unified patch that has to be applied.
It will tell asterisk(-config) users
about asterisk-config-custom
Looking forward to your feedback.
Regards
Geert Stappers
Descirption: asterisk config custom
Author: Geert Stappers stapp...@stappers.it
Forwarded-Upstream: no
Bug-Debian: #760032
Upgrading the asterik package,
is usualy upgrading the asterisk-config package.
But changing the asterisk-config package effects the custom configuration.
Unless the asterisk configuration is in the package asterisk-config-custom.
This patch provides the script asterisk-config-custom that helps
to create the asterisk-config-custom package
--- /dev/null
+++ b/contrib/scripts/asterisk-config-custom
@@ -0,0 +1,385 @@
+#!/bin/bash
+#
+# asterisk-config-custom
+# script to help creating a 'asterisk-config-custom' .deb package
+#
+#
+# Created by: Geert Stappers stapp...@stappers.it
+# And distributed under the terms of the GPL
+#
+#
+function acc_usage ()
+{
+cat HERE
+
+asterisk-config-custom {command}
+
+Where 'command' is 'init', 'next', 'sync', 'help' or 'force'.
+
+ init: Creates directory 'my-asterisk-config' with content
+
+ next: Provides instruction for next step
+
+ sync: Mostly \`rsync --archive /etc/asterisk etc_asterisk\`
+
+ help: Prints _another_ help text
+
+ force: How to force the first install when asterisk-config is installed
+
+HERE
+}
+
+function acc_help ()
+{
+cat HERE
+
+Program 'asterisk-config-custom' is for helping you making
+your 'asterisk-config-custom' .deb package.
+
+Typical work flow is running
+ asterisk-config-custom init
+only once.
+
+Now you have a directory named
+ my-asterisk-config
+feel free to rename it
+Important is that it has a debian/ directory
+and an etc_asterisk/ directory
+
+Change working directory with
+ cd my-asterisk-config # or to what you renamed it.
+Edit files in etc_asterisk. You may use
+ asterisk-config-custom sync
+to get you a starting point.
+Create the actual package with
+ dpkg-buildpackge -uc -us
+
+And install with
+ sudo dpkg -i ../asterisk-config-custom_*_all.deb
+
+See also \`asterisk-config-custom force\`
+
+HERE
+}
+
+function acc_force ()
+{
+cat HERE
+
+When package \`asterisk-config\` is installed, you have to
+use force to install your \`asterisk-config-custom\` package.
+ sudo dpkg --force-conflicts --force-overwrite -i ../asterisk-config-custom_*_all.deb
+Purge the conflicting package with
+ sudo dpkg --purge asterisk-config
+
+Now you can use the typical workflow which includes
+ sudo dpkg -i ../asterisk-config-custom_*_all.deb
+
+You can avoid '--force-conflicts' and '--force-overwrite' by
+installing \`asterisk-config-custom\` _before_ you install \`asterisk\`.
+Or by
+ sudo apt-get remove asterisk
+ sudo dpkg -i ../asterisk-config-custom_*_all.deb
+ sudo apt-get install asterisk
+That gives you downtime on Asterisk, but you get a reload/restart.
+Note: Installing asterisk-config-custom does no asterisk reload.
+
+HERE
+}
+
+function acc_init ()
+{
+# Creates a diretory and puts files in it,
+# including the Debian packaging files.
+
+mkdir --parents my-asterisk-config/debian/source
+
+cat HERE my-asterisk-config/README
+
+In this directory you can / should run
+
+ dpkg-buildbuildpackage -uc -us
+
+to get your 'asterisk-config-custom' package build.
+
+HERE
+
+cat LastLine my-asterisk-config/Makefile
+#
+# Makefile
+#
+all: etc_asterisk/asterisk.conf \
+ usr/share/doc/asterisk-config/examples/configs/modules.conf.sample
+ @echo FYI: (minimal set of) configuration files are available
+
+etc_asterisk/asterisk.conf:
+ @mkdir --parents etc_asterisk
+ echo ; only a place holder etc_asterisk/asterisk.conf
+
+usr/share/doc/asterisk-config/examples/configs/modules.conf.sample:
+ @mkdir --parents usr/share/doc/asterisk-config/examples/configs
+ echo ; place holder \\
+ usr/share/doc/asterisk-config/examples/configs/modules.conf.sample
+
+
+install:
+ install --directory \$(DESTDIR)/usr
+ install --directory \$(DESTDIR)/etc/asterisk
+ rsync --archive --delete usr/* \$(DESTDIR)/usr
+ rsync --archive --delete etc_asterisk/* \$(DESTDIR)/etc/asterisk
+
+# l l
+LastLine
+
+cat LastLine my-asterisk-config/acc.config
+# This file will be read during \`asterisk-config-custom sync\`
+#
+ACC_SYNC_CONFIG_EXAMPLES=Yes
Bug#769108: asterisk: rr_copy array too small for some record-route headers
On Sat, Dec 13, 2014 at 02:05:19PM +0100, Geert Stappers wrote: It is against the Wheezy branch In the Jessie branch there has upstream Asterisk ' char rr_copy[256]; ' removed. Right now I not sure what to do with this bug report for 1:1.8.13.1~dfsg1-3+deb7u3 Hopefully is (was?) my work on #769108 any use. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772469: wishlist: debian/README.source
Is git-buildpackage being used for Asterisk packaging in Debian? If so, what work-flow is used? Groeten Geert Stappers -- Leven en laten leven From 81640ea283d74b6366bfa03c4a5ebed654f02804 Mon Sep 17 00:00:00 2001 From: Stappers Geert stapp...@paddy.gpm.stappers.nl Date: Sun, 14 Dec 2014 14:46:33 +0100 Subject: [PATCH] new file: debian/README.source --- debian/README.source | 6 ++ 1 file changed, 6 insertions(+) create mode 100644 debian/README.source diff --git a/debian/README.source b/debian/README.source new file mode 100644 index 000..af4d066 --- /dev/null +++ b/debian/README.source @@ -0,0 +1,6 @@ + +Documentation of gbp, git build package, is +at http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html + +You find that doc also in /usr/share/doc/git-buildpackage/manual-html/gbp.html +after installing the package git-buildpackage -- 2.1.3
Bug#771463: CVE-2014-8418 CVE-2014-8412 CVE-2014-8414 CVE-2014-8417
On Mon, Dec 08, 2014 at 07:36:11AM +0200, Tzafrir Cohen wrote: On Sat, Nov 29, 2014 at 10:33:31PM +0100, Moritz Muehlenhoff wrote: Source: asterisk Severity: grave Tags: security Please see http://downloads.digium.com/pub/security/AST-2014-018.html http://downloads.digium.com/pub/security/AST-2014-017.html http://downloads.digium.com/pub/security/AST-2014-014.html http://downloads.digium.com/pub/security/AST-2014-012.html 012 was already fixed (in a version uploaded to Unstable, but didn't stay there long enough). Sadly Unstable has Asterisk 13, and thus those need to be pushed directly to Jessie. I created a Jessie branch in git with those fixes. Thanks Sadly I didn't have the time to properly document them. What kind of documentation should be added? In debian/patches/AST-2014-014.patch is From 90cdc0d1c75ac44837da9ff4a6cecf754d99e4f9 Mon Sep 17 00:00:00 2001 From: Joshua Colp jc...@digium.com Date: Thu, 20 Nov 2014 14:20:08 + Subject: [PATCH 1/3] AST-2014-014: Fix race condition where channels may get stuck in ConfBridge under load. Under load it was possible for the bridging API, and thus ConfBridge, to get channels that may have hung up stuck in it. This is because handling of state transitions for a bridged channel within a bridge was not protected and simply set the new state without regard to the existing state. If the existing state had been hung up this would get overwritten. This change adds locking to protect changing of the state and also takes into consideration the existing state. ASTERISK-24440 #close Reported by: Ben Klang Review: https://reviewboard.asterisk.org/r/4173/ git-svn-id: http://svn.asterisk.org/svn/asterisk/branches/11@428299 f38db490-d61c-443f-a65b-d21fe96a405b --- main/bridging.c | 26 +- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/main/bridging.c b/main/bridging.c index a36ccf9..0f8f4e8 100644 --- a/main/bridging.c +++ b/main/bridging.c Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769108: asterisk: rr_copy array too small for some record-route headers
Control: -1 + patch
On Tue, Nov 11, 2014 at 10:56:34AM +0100, Dirk Teurlings - SIGNET B.V. wrote:
Looking into this I found that in chan_sip.c in function build_route
there is a definition of 'char rr_copy[256]' (line 14252). This is
too small as you can see. My proposed fix would be to enlarge this
field to a bigger value.
Converted into a patch. Find it attached.
For now I have set mine to 8192. This completely resolves the issue.
To avoid the risc of memory exhausting enlarged from 256 to 512.
Groeten
Geert Stappers
--
Leven en laten leven
From 940660f2d8f4e4551044032350bf5008c95317a0 Mon Sep 17 00:00:00 2001
From: Stappers Geert stapp...@paddy.gpm.stappers.nl
Date: Sat, 13 Dec 2014 13:44:11 +0100
Subject: [PATCH] Transformed #769108 into a patch.
It is against the Wheezy branch
modified: debian/changelog
new file: debian/patches/rr_copy_array_too_small
modified: debian/patches/series
---
debian/changelog | 8 +--
debian/patches/rr_copy_array_too_small | 41 ++
debian/patches/series | 1 +
3 files changed, 48 insertions(+), 2 deletions(-)
create mode 100644 debian/patches/rr_copy_array_too_small
diff --git a/debian/changelog b/debian/changelog
index 782bafc..552b920 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
-asterisk (1:1.8.13.1~dfsg1-3+deb7u4) UNRELEASED; urgency=low
+asterisk (1:1.8.13.1~dfsg1-3+deb7u4.1) UNRELEASED; urgency=low
+ [ Tzafrir Cohen ]
* Patch AST-2014-001 (CVE-2014-2286) - Stack overflow in HTTP processing
of Cookie headers.
- -- Tzafrir Cohen tzaf...@debian.org Wed, 12 Mar 2014 22:50:01 +0200
+ [ Stappers Geert ]
+ * rr_copy array in chan_sip.c larger (Closes: #769108)
+
+ -- Stappers Geert stapp...@debian.org Sat, 13 Dec 2014 13:29:15 +0100
asterisk (1:1.8.13.1~dfsg1-3+deb7u3) stable-security; urgency=high
diff --git a/debian/patches/rr_copy_array_too_small b/debian/patches/rr_copy_array_too_small
new file mode 100644
index 000..9af380b
--- /dev/null
+++ b/debian/patches/rr_copy_array_too_small
@@ -0,0 +1,41 @@
+Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769108
+Author: Dirk Teurlings - SIGNET B.V. dteurli...@signet.nl
+Description: rr_copy array too small for some record-route headers
+
+Connecting with Microsoft Lync through one or more SIP proxies fails when
+the Record-Route value exceeds 256 characters in length. Asterisk's log
+shows the following warning message:
+
+[Nov 10 16:11:04] WARNING[22109]: sip/reqresp_parser.c:1070
+ get_in_brackets_full: No closing bracket found in
+ 'sip:192.168.10.2;r2=on;lr;ftag=as36b4c879;vsf=AAA'
+
+where the complete Record-Route was:
+sip:127.1.2.3;line=sr-EcmQ.7qAr7xCqCtAi7V9q7qy.13CnXJzETMC8bByn1ehE7xMPcthPLxh6-3R6zBREzEzianBn7eQ.16z67Bwusjwusjwusjwusjwusjwusjwusjwu2iY3smwsaAQdBjXOKjw3-RgsaElrdl2OXuM67qAr7YU67KhPajyogmmEQ**,sip:192.168.10.2;r2=on;lr;ftag=as736f5b00;vsf=AABCUEIARlpOQVhAAFxWRg--;did=f31.5bf1;nat=yes.
+
+As you can see it cuts the Record-Route string short at exactly 256 chars.
+
+Looking into this I found that in chan_sip.c in function build_route
+there is a definition of 'char rr_copy[256]' (line 14252). This is too
+small as you can see. My proposed fix would be to enlarge this field to
+a bigger value. For now I have set mine to 8192. This completely resolves
+the issue.
+
+
+Transforming that information into an unified diff was
+done by Geert Stappers stapp...@stappers.nl.
+
+Stappers choose for s/256/512/ to avoid the risc of memory exhausting.
+
+
+--- a/channels/chan_sip.c
b/channels/chan_sip.c
+@@ -14231,7 +14231,7 @@ static void build_route(struct sip_pvt *p, struct sip_request *req, int backward
+ /* 1st we pass through all the hops in any Record-Route headers */
+ for (;;) {
+ /* Each Record-Route header */
+- char rr_copy[256];
++ char rr_copy[512];
+ char *rr_copy_ptr;
+ char *rr_iter;
+ rr = __get_header(req, Record-Route, start);
diff --git a/debian/patches/series b/debian/patches/series
index 1922f76..96c133f 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -25,6 +25,7 @@ kfreebsd
menuselect_cflags
ilbc_disable
httpd_port
+rr_copy_array_too_small
AST-2012-012
AST-2012-013
--
2.1.3
signature.asc
Description: Digital signature
Bug#769108: tag +patch
Control: tag -1 + patch On Sat, Dec 13, 2014 at 01:09:18PM +, Debian Bug Tracking System wrote: Processing control commands: -1 + patch Unknown command or malformed arguments to command. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Thu, Dec 11, 2014 at 03:31:38PM +0200, EpsiloN EpsiloN wrote: Geert: do you have some plans investigate the problem more deeply? As said in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134#40 I have allready interresting problems :-) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Wed, Dec 10, 2014 at 10:40:40AM +0200, EpsiloN EpsiloN wrote: Any feedback is appreciated. Information that I couldn't find at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134 is where the iSCSI initiator gets it's IP configuration. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Wed, Dec 10, 2014 at 01:53:13PM +0200, EpsiloN EpsiloN wrote: Any idea why kernel hasn't read the /etc/network/interfaces during disk initilization? That is called boot sequence. Disk (driver) initalisation needs to be done before a disk can be read. Why does already working server hungs at random? That question has be seen. And this message shows that it is not ignored. I think #772134 could be an interresting problem and I know I have allready interresting problems :-) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
On Wed, Dec 10, 2014 at 03:14:16PM +0200, EpsiloN EpsiloN wrote: Is there any way to debug the problem? Advice: Analyze the core file(s) that where found -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772469: wishlist: debian/README.source
Package: asterisk
Version: 1:13.0.0~dfsg-2
Severity: wishlist
Hi,
After doing
debcheckout asterisk
fullfilling the dependencies, starting
fakeroot dpkg-buildpackage -uc -us
got me
dpkg-source: error: can't build with source format '3.0 (quilt)':
no upstream tarball found at
../asterisk_13.0.0~dfsg.orig.tar.{bz2,gz,lzma,xz}
dpkg-buildpackage: error: dpkg-source -b asterisk gave
error exit status 255
It would nice if the file debian/README.source has information
how to build Asterisk debian package from Source Code Management, SCM, tools.
At https://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource
is this text:
debian/README.source may also include any other information that would
be helpful to someone modifying the source package.
Thank you for considering
Groeten
Geert Stappers
--
Leven en laten leven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772416: initrd: support booting from chroot
On Sat, Dec 06, 2014 at 04:49:10PM +0100, lemonsqueeze wrote: Patch and details can be found here: https://github.com/lemonsqueeze/boot_chroot https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch $ wget https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch --2014-12-06 17:39:48-- https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch Resolving github.com (github.com)... 192.30.252.130 Connecting to github.com (github.com)|192.30.252.130|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'initrd.patch' [ = ] 36,652 167KB/s in 0.2s 2014-12-06 17:39:49 (167 KB/s) - 'initrd.patch' saved [36652] $ file initrd.patch initrd.patch: HTML document, UTF-8 Unicode text, with very long lines $ :-( Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772416: initrd: support booting from chroot
On Sat, Dec 06, 2014 at 05:44:02PM +0100, Geert Stappers wrote:
On Sat, Dec 06, 2014 at 04:49:10PM +0100, lemonsqueeze wrote:
Patch and details can be found here:
https://github.com/lemonsqueeze/boot_chroot
https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
$ wget https://github.com/lemonsqueeze/boot_chroot/blob/master/initrd.patch
Length: unspecified [text/html]
Real patch is
https://raw.githubusercontent.com/lemonsqueeze/boot_chroot/master/initrd.patch
Here inline (and also attached)
diff -Nru orig/init new/init
--- orig/init 2014-12-04 11:42:27.0 +0100
+++ new/init2014-12-04 17:24:18.0 +0100
@@ -149,6 +149,9 @@
ip=*)
IP=${x#ip=}
;;
+ chroot=*)
+ CHROOT=${x#chroot=}
+ ;;
boot=*)
BOOT=${x#boot=}
;;
diff -Nru orig/scripts/local new/scripts/local
--- orig/scripts/local 2014-12-04 11:42:27.0 +0100
+++ new/scripts/local 2014-12-04 11:45:23.0 +0100
@@ -150,6 +150,37 @@
fi
fi
+ if [ $CHROOT ]; then
+ if [ $mountroot_status != 0 ]; then
+ if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+ panic
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it. To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+
+ fi
+ fi
+
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+
+ if [ ! -d /host/${CHROOT} ]; then
+ panic ALERT! /host/${CHROOT} does not exist.
Dropping to a shell!
+ fi
+
+ # FIXME This has no error checking
+ mount --bind /host/${CHROOT} ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+ fi
+
[ $quiet != y ] log_begin_msg Running /scripts/local-bottom
run_scripts /scripts/local-bottom
[ $quiet != y ] log_end_msg
Thanks for the patch
Groeten
Geert Stappers
--
Leven en laten leven
diff -Nru orig/init new/init
--- orig/init 2014-12-04 11:42:27.0 +0100
+++ new/init 2014-12-04 17:24:18.0 +0100
@@ -149,6 +149,9 @@
ip=*)
IP=${x#ip=}
;;
+ chroot=*)
+ CHROOT=${x#chroot=}
+ ;;
boot=*)
BOOT=${x#boot=}
;;
diff -Nru orig/scripts/local new/scripts/local
--- orig/scripts/local 2014-12-04 11:42:27.0 +0100
+++ new/scripts/local 2014-12-04 11:45:23.0 +0100
@@ -150,6 +150,37 @@
fi
fi
+ if [ $CHROOT ]; then
+ if [ $mountroot_status != 0 ]; then
+ if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+panic
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it. To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+
+ fi
+ fi
+
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+
+ if [ ! -d /host/${CHROOT} ]; then
+ panic ALERT! /host/${CHROOT} does not exist. Dropping to a shell!
+ fi
+
+ # FIXME This has no error checking
+ mount --bind /host/${CHROOT} ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+ fi
+
[ $quiet != y ] log_begin_msg Running /scripts/local-bottom
run_scripts /scripts/local-bottom
[ $quiet != y ] log_end_msg
Bug#769407: Should set up Grub for serial and console
On Thu, Nov 13, 2014 at 02:19:50PM +0100, martin f krafft wrote: Package: debian-installer Version: 20141112-00:20 Severity: wishlist Following an install with auto console=tty0 console=ttyS0,115200n8 on the command line and using yesterday's amd64 daily jessie installer, the /etc/default/grub file had GRUB_TERMINAL=serial enabled. Please set that to GRUB_TERMINAL=console serial to allow Grub to display on both, which it has supported for a while. To which package should this bugreport be assigned? Groeten Geert Stappers Not sure if this BR should be merged with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769406 -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679479: [pkg-bacula-devel] Bug#679479: bacula-fd fails to start because network is not initialized
On Mon, Dec 01, 2014 at 01:04:34PM -0800, Tom Epperly wrote: On Mon, Dec 1, 2014 at 10:41 AM, Carsten Leonhardt l...@carotec.de wrote: Dear Tom, is (or was, as your bug report is over 2 years old now) there a specific reason why you had the FDAddress = faerun.epperly.home directive in your bacula-fd.conf? Just omitting the directive should (have) give(n) you a functioning backup. I think I based my configuration file on the documentation and examples that were available at the time. What could (should?) be done to avoid that other people encounter the bug that you reported? Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767504: separate package for libmp4v2
FWIW I have been told that libmp4v2 is not in upstream mpd So a clean solution for the license issue this bugreport is about, is to put libmp4v2 in a separate package. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770740: qemu-system: qemu-system-i386 -fda /dev/fd0 ... fails.
Control: merge 770740 770742 and also specify which version of qemu you're using - your bug report does not specify this. Bugreport 770742 is from the same reporter and states version: 1.1.2+dfsg-6 B.R. #770740 and #770742 are merged and for convience this URL http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770742 Regards Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769996: debian-installer: Possible help text for win32diskimager users
On Tue, Nov 18, 2014 at 06:04:20AM +0100, nodiscc wrote: Hello, here is a short text that can be used in the documentation: * download win32diskimager from http://sourceforge.net/projects/win32diskimager/, unpack the archive and run Win32DiskImager.exe * in the Image file area, select the .iso debian installer iage you downloaded from debian.org * in the Device area, select the drive letter for the USB drive you want to use as an installation media * you may have to format the USB drive first to affect a drive letter to it * Click Write. **All data present on the USB drive will be erased!** Thanks! Proposal: --- manual/en/install-methods/boot-usb-files.xml(revision 69458) +++ manual/en/install-methods/boot-usb-files.xml(working copy) @@ -178,4 +178,32 @@ /sect2 + sect2 id=usb-prepare-windows + titleCreating USB-stick Debian-installer under Windows/title +para + +Download win32diskimager from http://sourceforge.net/projects/win32diskimager/, +unpack the archive and run Win32DiskImager.exe + +/parapara + +In the Image file area, +select the .iso installer image you downloaded. + +/parapara + +In the Device area, +select the drive letter for the USB drive +you want to use as an installation media. + +/parapara + +You may have to format the USB drive first +to affect a drive letter to it. +Click Write. **All data present on the USB drive will be erased!** + +/para + + /sect2 + /sect1 Attached the same patch. Reason for not tagging with 'patch' is because I have build the manual. Groeten Geert Stappers -- Leven en laten leven Index: manual/en/install-methods/boot-usb-files.xml === --- manual/en/install-methods/boot-usb-files.xml(revision 69458) +++ manual/en/install-methods/boot-usb-files.xml(working copy) @@ -178,4 +178,32 @@ /sect2 + sect2 id=usb-prepare-windows + titleCreating USB-stick Debian-installer under Windows/title +para + +Download win32diskimager from http://sourceforge.net/projects/win32diskimager/, +unpack the archive and run Win32DiskImager.exe + +/parapara + +In the Image file area, +select the .iso installer image you downloaded. + +/parapara + +In the Device area, +select the drive letter for the USB drive +you want to use as an installation media. + +/parapara + +You may have to format the USB drive first +to affect a drive letter to it. +Click Write. **All data present on the USB drive will be erased!** + +/para + + /sect2 + /sect1
Bug#769936: now titled
retitle 769936 It's something with the nouveau drivers and xorg. thanks here- that's where I'll go to troubleshoot if I can get console access at some point. FWIW: install SSH server and access it over the network Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769996: document win32diskimager
Package: debian-installer Hi, I felt the need to park 05:38 -!- nohklm [~b...@0001f69f.user.oftc.net] has joined #debian-boot 05:39 nohklm hello, is anyone form the debian install system team around? 05:40 nohklm this is about a trivial but annoying bug 05:40 nohklm https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283136 05:40 nohklm debian-installer-manual: creating USB-stick Debian-installer under Windows 05:40 nohklm it's been sitting there since 2004 05:41 nohklm I was on #debian and we constantly have to direct users to win32diskimager 05:41 nohklm can it be added to the docs? 05:41 nohklm http://sourceforge.net/projects/win32diskimager/ GPLv2 here. I'll see I can convert it in a patch against the documention. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769749: it installed a system that wouldn't boot without wifi firmware
On Sat, Nov 15, 2014 at 10:10:58PM -0600, Tim Dowd wrote: Package: installation-reports Boot method: Netinstall CD, Jessie Beta 2 Image version: http://cdimage.debian.org/cdimage/jessie_di_beta_2/i386/iso-cd/debian-jessie-DI-b2-i386-netinst.iso Date: 2014-11-15 Machine: Compaq Presario V3000 Processor: Centrino Duo Memory: Partitions: Output of lspci -knn (or lspci -nn): 05:00.0 Network controller [0280]: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection [8086:4222] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:135b] Kernel driver in use: iwl3945 [ ] Comments/Problems: Installed i386 version of Jessie, selected MATE desktop. Upon booting, just got infinite loop of iwlwifi trying to find firmware. Upon reboot, this started, but calmed down enough to let MATE load. I installed the wrong firmware package, rebooted, and could never get back in Re-ran installation but chose XFCE instead. Started to have scrolling action but then XFCE loaded. I got the right firmware in and no more scrolling Bottom line is it installed a system that wouldn't boot without firmware (or a lot of luck.) Hello Tim, Good install report. Thanks for bringing this issue up. I, as in I personaly, think that will be hard to resolve without access to the hardware. So right now the only thing you know is that someone has seen your bugreport and took time to acknowledge it. I have some questions: Installed i386 version of Jessie, selected MATE desktop. Upon booting, just got infinite loop of iwlwifi trying to find firmware. Was that a warm reboot? ( Was it without a power cycle? ) How was iwlwifi trying to find firmware shown to you? ( How did you know what was inside the infinite loop? ) Upon reboot, this started, Was that a cold reboot? ( Was it with turning-off and on again? ) Now imagine people that did a websearch on linux 8086:4222 I got the right firmware in and no more scrolling What is the right firmware for the wifi device? Where did you get it? Would have https://www.debian.org/releases/jessie/i386/ch06s04.html.en helped? Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766664: qemu-system-common VMs with bridged-networking doesn't start.
On Fri, Oct 24, 2014 at 06:56:27PM +0200, Jonathan Dumke wrote: Dear Maintainer, And others who care about QEMU I want to start VMs with cmd like this: kvm -net bridge -m 1024 ... but qemu quit alltimes with following output: failed to parse default acl file `/etc/qemu/bridge.conf' failed to launch bridge helper And what is the content of your /etc/qemu/bridge.conf? Can it be read by the user who is starting kvm? ( file permissions ) I hope these questions do contribute to a better QEMU Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766039: which console (or why tty9)
Hi, Please also document how to change the console that gets the debug information. tty9 is not aviable on systems without video-output. Such as embedded systens that only have a serial port. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763897: [i...@hellion.org.uk: Re: Inclusion of sun7i-a20-bananapi.dts]
- Forwarded message from Ian Campbell i...@hellion.org.uk - Date: Fri, 03 Oct 2014 23:05:14 +0100 From: Ian Campbell i...@hellion.org.uk To: Karsten Merker mer...@debian.org Cc: Ben Hutchings b...@decadent.org.uk, debian-ker...@lists.debian.org Subject: Re: Inclusion of sun7i-a20-bananapi.dts X-Mailer: Evolution 3.12.6-1 On Fri, 2014-10-03 at 17:03 +0200, Karsten Merker wrote: Ian, if you should find the time, could you perhaps give it a try? It built for me so I've pushed it. Ian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1412373914.17796.53.ca...@hellion.org.uk - End forwarded message - Hope this helps -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760853: on mentors, work in progress
on Thu, 25 Sep 2014 18:48:56 +0300, Damian Minkov wrote: On Thu, Sep 25, 2014 at 5:18 PM, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: severity 760853 grave Bug #760853 [jitsi] jitsi is bound/dependant on libavfilter4 instead of libavfilter5 Severity set to 'grave' from 'important' retitle 760853 jitsi uninstallable in sid Bug #760853 [jitsi] jitsi is bound/dependant on libavfilter4 instead of libavfilter5 Changed Bug title to 'jitsi uninstallable in sid' from 'jitsi is bound/dependant on libavfilter4 instead of libavfilter5' stop Stopping processing here. Hi, we have updated the package to newer version and it is uploaded on mentors. The new version will fix this one. Regards damencho FWIW the upload to mentors announce is http://lists.jitsi.org/pipermail/dev/2014-September/022040.html It did trigger a new upload of package 'strophejs' ( migration status is at https://packages.qa.debian.org/s/strophejs.html ) That is all fine. But what is needed for an upload to 'unstable' or 'exprimental'? Cheers Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754586: debcheckout jitsi
Hi, It would be nice if debcheckout jitsi would work. Bugreport #754586, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754586 has allready a patch. It is https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=add_vcs_headers.patch;att=1;bug=754586 Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760032: asterisk-config-custom
Package: asterisk-config
Version: 1:11.10.2~dfsg-1
Severity: wishlist
Dear Maintainers,
Asterisk has as
dependency asterisk-config (= ${source:Version}) | asterisk-config-custom
Allowing both configuration packages is good.
That `asterisk-config` is made available is great.
This bug report is to make `asterisk-config-custom` available.
I mean that the Asterisk package should provide tools
to make `asterisk-config-custom` packages.
At least it would be nice if it has such support.
And if it is allready available it should be more visible / accessable.
I have something that covers my needs which I want to share with you.
It is a script that creates a directory with a Makefile in
plus a debian directory with packaging files. Running in
that directory `dpkg-buildpackage -uc -us` creates
a 'asterisk-config-custom' package.
The script will be sent to this bug report
upon recieving the bug report number.
Cheers
Geert Stappers
--
Leven en laten leven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760032: asterisk-config-custom
On Sun, Aug 31, 2014 at 07:50:04AM +0200, Geert Stappers wrote:
[ ... submit bug report ... ]
I have something that covers my needs which I want to share with you.
It is a script that creates a directory with a Makefile in
plus a debian directory with packaging files. Running in
that directory `dpkg-buildpackage -uc -us` creates
a 'asterisk-config-custom' package.
The script will be sent to this bug report
upon recieving the bug report number.
Find it attached.
Cheers
Geert Stappers
--
Leven en laten leven
#!/bin/bash
#
# asterisk-config-custom
# script to help creating a 'asterisk-config-custom' .deb package
#
function acc_usage ()
{
cat HERE
asterisk-config-custom {command}
Where 'command' is 'init', 'next', 'sync', 'help' or 'force'.
init: Creates directory 'my-asterisk-config' with content
next: Provides instruction for next step
sync: Mostly \`rsync --archive /etc/asterisk etc_asterisk\`
help: Prints _another_ help text
force: How to force the first install when asterisk-config is installed
HERE
}
function acc_help ()
{
cat HERE
Program 'asterisk-config-custom' is for helping you making
your 'asterisk-config-custom' .deb package.
Typical work flow is running
asterisk-config-custom init
only once.
Change working directory with
cd my-asterisk-config # or rename it first
Edit files in etc_asterisk. You may use
asterisk-config-custom sync
to get you a starting point.
Create the actual package with
dpkg-buildpackge -uc -us
And install with
sudo dpkg -i ../asterisk-config-custom_*_all.deb
See also \`asterisk-config-custom force\`
HERE
}
function acc_force ()
{
cat HERE
When package \`asterisk-config\` is installed, you have to
use force to install your \`asterisk-config-custom\` package.
sudo dpkg --force-conflicts --force-overwrite -i
../asterisk-config-custom_*_all.deb
Purge the conflicting package with
sudo dpkg --purge asterisk-config
Now you can use the typical workflow which includes
sudo dpkg -i ../asterisk-config-custom_*_all.deb
You can avoid '--force-conflicts' and '--force-overwrite' by
installing \`asterisk-config-custom\` _before_ you install \`asterisk\`.
Or by
sudo apt-get remove asterisk
sudo dpkg -i ../asterisk-config-custom_*_all.deb
sudo apt-get install asterisk
That gives you downtime on Asterisk, but you get a reload/restart.
Note: Installing asterisk-config-custom does no asterisk reload.
HERE
}
function acc_init ()
{
# Creates a diretory and puts files in it,
# including the Debian packaging files.
mkdir --parents my-asterisk-config/debian/source
cat HERE my-asterisk-config/README
In this directory you can / should run
dpkg-buildbuildpackage -uc -us
to get your 'asterisk-config-custom' package build.
HERE
cat LastLine my-asterisk-config/Makefile
#
# Makefile
#
all: etc_asterisk/asterisk.conf \
usr/share/doc/asterisk-config/examples/configs/modules.conf.sample
@echo FYI: (minimal set of) configuration files are available
etc_asterisk/asterisk.conf:
@mkdir --parents etc_asterisk
echo ; only a place holder etc_asterisk/asterisk.conf
usr/share/doc/asterisk-config/examples/configs/modules.conf.sample:
@mkdir --parents usr/share/doc/asterisk-config/examples/configs
echo ; place holder \\
usr/share/doc/asterisk-config/examples/configs/modules.conf.sample
install:
install --directory \$(DESTDIR)/usr
install --directory \$(DESTDIR)/etc/asterisk
rsync --archive --delete usr/* \$(DESTDIR)/usr
rsync --archive --delete etc_asterisk/* \$(DESTDIR)/etc/asterisk
# l l
LastLine
cat LastLine my-asterisk-config/acc.config
# This file will be read during \`asterisk-config-custom sync\`
#
ACC_SYNC_CONFIG_EXAMPLES=Yes
# another value as 'Yes' wouldn't sync the configuration examples
#
#
# l l
LastLine
##
# Those who are familiar with Debian packaging
# can consider the rest of this function as a dedicated `dh_make`.
cat LastLine my-asterisk-config/debian/control
Source: asterisk-config-custom
Section: comm
Priority: optional
Maintainer: Me Myself ${LOGNAME}@$( hostname --fqdn )
Build-Depends: debhelper (= 9)
Standards-Version: 3.9.5
Homepage: insert the upstream URL, if relevant
#Vcs-Git: git://anonscm.debian.org/collab-maint/asterisk-config-custom.git
#Vcs-Browser:
http://anonscm.debian.org/?p=collab-maint/asterisk-config-custom.git;a=summary
Package: asterisk-config-custom
Architecture: all
Depends: ${misc:Depends}
Recommends: asterisk
Conflicts: asterisk-config
Description: Custom configuration files for Asterisk
Package that contains custom configuration files for Asterisk.
.
It is to keep _your_ config files while upgrading Asterisk.
.
The trick is that Asterisk depends
on asterisk-config OR asterisk-config-custom
LastLine
cat LastLine my-asterisk-config/debian/changelog
asterisk-config-custom (0.6) unstable; urgency=medium
* Created with \`asterisk-config-custom
Bug#760032: asterisk-config-custom
On Sun, Aug 31, 2014 at 09:17:18AM +0300, Tzafrir Cohen wrote:
On Sun, Aug 31, 2014 at 07:50:04AM +0200, Geert Stappers wrote:
[ ... submit bug report ... ]
I mean that the Asterisk package should provide tools
to make `asterisk-config-custom` packages.
At least it would be nice if it has such support.
For a specialized installation of mine I maintain a certain
minimalistic package that provides asterisk-config-custom. Just for the
kicks I had modules.conf disable automatic module loading.
I think we all have a specialized installation which
is a modified version of package `asterisk-config`.
Getting such installations in `asterisk-config-custom`
is the goal for this bug report.
Building yet another package was very simple with dh.
I see no reason to try to script it (though others may disagree).
Done as
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=10;filename=asterisk-config-custom;att=1;bug=760032
Having a skeleton of a minimalistic package may be useful and may save
work as a better starting point: an empty configuration is not usable.
Would a directory with minimal working configuration be of use?
(Assuming that minimal working _Asterisk_ configuration is ment)
Yes, that would be usefull.
Making the minimal working Asterisk configuration easy to install
and to avoid the
| == Modified (by you or by a script) since installation.
| == Package distributor has shipped an updated version.
|What would you like to do about it ? Your options are:
| Y or I : install the package maintainer's version
| N or O : keep your currently-installed version
| D : show the differences between the versions
| Z : start a shell to examine the situation
| The default action is to keep your current version.
dialog upon upgrading Asterisk is the reason for requesting support
for asterisk-config-custom.
Groeten
Geert Stappers
--
Package: asterisk
Depends: ... , asterisk-config (= ${source:Version}) | asterisk-config-custom,
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760032: asterisk-config-custom visible
And if it is allready available it should be more visible / accessable. --- a/debian/control +++ b/debian/control @@ -278,3 +278,6 @@ Description: Configuration files for Asterisk Asterisk is an Open Source PBX and telephony toolkit. . This package contains the default configuration files of Asterisk. + . + Script 'asterisk-config-custom' helps to create + 'asterisk-config-custom' packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748574: 3.14.1 does not boot on Dell server
Op 2014-05-18 om 17:29 schreef Erwan David: When trying to boot 3.14.1 It stops at the first line booting the kernel, no other message, even when trying to start without quiet. Did the PowerEdge R210 boot with previous Linux kernels? If yes, what is the last known good version? Please tell more about the installation of the 3.14.1 kernel. (Was it a fresh install? Was it a update? Was there enough disk space during the update?) Regards Geert Stappers PS : since I access it through an iDrac kvm which does not transmit arrow keys nor Ctrl keys, FWIW: I think that iDRAC kvm can transmit arrow keys and ConTRoL. I can't tell how, but it is very likely that such keys are supported. That those keys have special meaning on the admin machine, is something to cope / workaround with. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735922: wishlist: document logging in /var/log/auth.log
Package: sslh Version: 1.13b-3.2 Severity: minor Dear Maintainer, When I have logged in through sslh, my connection is from localhost. I do understand this artifact of sslh. I did took me some time to find out from where the connection came from. It would be nice if the manual page says that logging is done in /var/log/auth.log Thank you for maintaining sslh in Debian. Cheers Geert Stappers -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages sslh depends on: ii adduser 3.113+nmu3 ii debconf 1.5.49 ii libc6 2.13-38 ii libconfig91.4.8-5 ii lsb-base 4.1+Debian8 ii update-inetd 4.43 Versions of packages sslh recommends: ii apache2 2.2.22-13 ii apache2-mpm-prefork [httpd] 2.2.22-13 ii openssh-server [ssh-server] 1:6.0p1-4 Versions of packages sslh suggests: pn openbsd-inetd | inet-superserver none -- Configuration Files: /etc/default/sslh changed: RUN=yes DAEMON=/usr/sbin/sslh DAEMON_OPTS=--user sslh --listen 0.0.0.0:443 --numeric --ssh 127.0.0.1:22 --ssl 127.0.0.1:443 --pidfile /var/run/sslh/sslh.pid -- debconf information: * sslh/inetd_or_standalone: standalone -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732193: spf-milter-python: socket not available
Package: spf-milter-python Version: 0.8.18-2 Severity: important Dear Maintainer, In /etc/spf-milter-python/spfmilter.cfg is the line socketname = /var/run/spf-milter-python/spfmiltersock But in directory /var/run/spf-milter-python/ is no socket visible. As I understand it, it should be. In Debian BTS #725974 ( http://bugs.debian.org/725974 ) also says that the socket is missing. This bugreport is spf-milter-python in combination with Postix. (The other ticket is with sendmail as MTA) Futher information from my research: * Only .pid file in /var/run/ directory * list open files, lsof, says the process has a socket. screenshot $ ls -lA /var/run/spf-milter-python/ total 4 -rw-r--r-- 1 spf-milter-python spf-milter-python 6 Dec 13 19:09 spfmilter.pid $ sudo lsof -p $( cat /var/run/spf-milter-python/spfmilter.pid ) | grep sock spfmilter 20709 spf-milter-python3u unix 0x880037097540 0t0 1644085 /var/run/spf-milter-python/spfmiltersock $ /screenshot What should I do to see the socket of spf-milter-python ? Groeten Geert Stappers -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.11-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages spf-milter-python depends on: ii adduser3.113+nmu3 ii lsb-base 4.1+Debian12 ii python 2.7.5-5 ii python-milter 0.9.8-2 ii python-spf 2.0.8-2 spf-milter-python recommends no packages. Versions of packages spf-milter-python suggests: ii postfix 2.10.2-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725974: cross reference hth
Submitter wrote: But /var/run/spf-milter-python/spfmiltersock doesn't exist I did open BTS #732193 http://bugs.debian.org/732193 for tracking the none existing socket. That is because I can't tell if both issues are duplicates or two different problems. And now with this update has the BTS a cross reference to it. Hope this helps. Groeten Geert Stappers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732193: other system has the socket
Hello, Subject says all: other system the socket. The working system is a 32-bit Wheezy system. (The bugreport is from a 64-bit Jessie system.) More information about the (old) Wheezy system: screenshot $ ls -l /var/run/spf-milter-python/ totaal 4 -rw-r--r-- 1 spf-milter-python spf-milter-python 5 dec 15 19:34 spfmilter.pid srwxr-xr-x 1 spf-milter-python spf-milter-python 0 dec 15 19:34 spfmiltersock $ uname -a Linux ganesha 3.2.0-4-686-pae #1 SMP Debian 3.2.51-1 i686 GNU/Linux $ python --version Python 2.7.3 $ cat /etc/os-release PRETTY_NAME=Debian GNU/Linux 7 (wheezy) NAME=Debian GNU/Linux VERSION_ID=7 VERSION=7 (wheezy) ID=debian ANSI_COLOR=1;31 HOME_URL=http://www.debian.org/; SUPPORT_URL=http://www.debian.org/support/; BUG_REPORT_URL=http://bugs.debian.org/; $ /screenshot Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#728776: FYI uploaded to NEW queue
For your information and for the BTS Package f-irc is uploaded to the NEW queue. See http://ftp-master.debian.org/new/f-irc_1.26-1.html for progress information. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: davmail src/java/com/ctc/wstx/sr/StreamScanner.java
Op 2013-11-29 om 13:00 schreef FTPmaster Luca Falavigna under Subject: davmail_4.3.0.2125-1_amd64.changes REJECTED Hi, src/java/com/ctc/wstx/sr/StreamScanner.java seems part of StAX2 API, licensed under LGPL-2.1+ or Apache-2.0. Does is say davmail should depend on the StAX2 API or does it say in debian/copyright should Files: src/java/com/ctc/wstx/sr/StreamScanner.java License: GPL-2 be changed? Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. Thanks for reviewing. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726656: [patch] more debconf support for apt-cacher-ng
Op 2013-11-23 om 16:48 schreef Eduard Bloch: [ ... new version needs to get released ... ] Please do Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728535: which size increment to expect
Op 2013-11-17 om 11:15 schreef Geert Stappers: Op 2013-11-17 om 10:55 schreef Geert Stappers: Edit on the kernel module source file, to add USB ID. Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger due the extra USB ID Is it correct to expect an increase in size of the .ko with a few bytes? Or is size increment in steps of 256 of 1024 bytes? Answer on my question: Yes, adding in .c source a line with VendorID and ProductID does increase the .ko module. In my case 120 bytes. So no increment in steps of 256 or 1024 bytes. $ filtered ls -l output -rw-r--r-- 1 root root 23144 Nov 15 20:55 /lib/modules/3.11-1-amd64/kernel/drivers/media/usb/gspca/gspca_sunplus.ko -rw-r--r-- 1 stappers stappers 23264 Nov 17 14:40 /home/stappers/src/linux/linux-3.11.5-goed/debian/linux-image-3.11-1-amd64/lib/modules/3.11-1-amd64/kernel/drivers/media/usb/gspca/gspca_sunplus.ko Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730065: document new_id interface
Package: debian-kernel-handbook Version: 1.0.15 Severity: wishlist Op 2013-11-17 om 12:28 schreef Bastian Blank: snip/ Also you want to use new_id interface[1] if possible. Bastian [1]: /sys/class/usb/drivers/*/new_id http://www.ha19.no/usb/ Adding that URL to the kernel-handbook would be an improvement. Now filed as a separate bugreport. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728535: so far
Summary: help is welcome After a apt-get source linux cd linux-VERSION fakeroot debian/rules binary there is linux-image-VERSION.deb that can be install. Succesfull rebooted with that new kernel. Edit on the kernel module source file, to add USB ID. Now is wanted the fastest way to get a .ko with the extra USB ID. Attempt 1: Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger due the extra USB ID Attempt 2: Executed `make -j 3` Failed with error about missing the .config file Attempt 3 4: screenshot HOSTCC arch/x86/tools/relocs_32.o HOSTCC arch/x86/tools/relocs_64.o HOSTCC arch/x86/tools/relocs_common.o HOSTLD arch/x86/tools/relocs Using /home/stappers/src/linux/linux-3.11.5 as source for kernel /home/stappers/src/linux/linux-3.11.5 is not clean, please run 'make mrproper' in the '/home/stappers/src/linux/linux-3.11.5' directory. make[5]: *** [prepare3] Error 1 make[4]: *** [sub-make] Error 2 make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/stappers/src/linux/linux-3.11.5/debian/build/build_amd64_none_amd64' make[2]: *** [debian/stamps/build_amd64_none_amd64_plain] Error 2 make[2]: Leaving directory `/home/stappers/src/linux/linux-3.11.5' make[1]: *** [binary-arch_amd64_none_amd64_real] Error 2 make[1]: Leaving directory `/home/stappers/src/linux/linux-3.11.5' make: *** [binary-arch] Error 2 $ make mrproper CLEAN scripts/basic CLEAN scripts/kconfig CLEAN /home/stappers/src/linux/linux-3.11.5/debian/ CLEAN include/config include/generated arch/x86/include/generated $ fakeroot debian/rules binary-arch /usr/bin/fakeroot: line 178: debian/rules: No such file or directory $ /screenshot In other words: I'm back at square 1 :-/ Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728535: which size increment to expect
Op 2013-11-17 om 10:55 schreef Geert Stappers: Edit on the kernel module source file, to add USB ID. Executed `fakeroot debian/rules binary-arh Produced a same size .ko, but it should be bigger due the extra USB ID Is it correct to expect an increase in size of the .ko with a few bytes? Or is size increment in steps of 256 of 1024 bytes? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: status: with r2174 no SMTP Body
Summary: Help Op 2013-11-11 om 21:49 schreef Geert Stappers: Hi, The version of Davmail in Alioth seems to been upstream revision r2174. With that version send E-mail has only SMTP headers, no SMTP body. With self-compiled upstream package version r2192 I do get SMTP bodies in sent mail. My attempt to add a newer version from upstream to packaging git repo failed horrible. I copied files from upstream SVN to the git packaging repo. Did `debuild -uc -us` and got: dpkg-source: warning: file dpkg/davmail-setup.nsi has no final newline (either original or modified version) dpkg-source: warning: file dpkg/archive/jsmooth-0.9.9-7-patch/skeletons/samplejar/sample.manifest has no final newline (either original or modified version) dpkg-source: error: cannot represent change to archive/jsmooth/skeletons/windowed-wrapper64/windowed-wrapper64.exe: binary file contents changed dpkg-source: error: add archive/jsmooth/skeletons/windowed-wrapper64/windowed-wrapper64.exe in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to archive/jsmooth/skeletons/console-wrapper/consolewrapper.exe: binary file contents changed dpkg-source: error: add archive/jsmooth/skeletons/console-wrapper/consolewrapper.exe in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to archive/jsmooth/skeletons/autodownload-wrapper/autodownload.exe: binary file contents changed dpkg-source: error: add archive/jsmooth/skeletons/autodownload-wrapper/autodownload.exe in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to archive/jsmooth/skeletons/winservice-wrapper/winservice.exe: binary file contents changed dpkg-source: error: cannot represent change to src/site/resources/images/thunderbirdSmtp.png: binary file contents changed dpkg-source: error: add src/site/resources/images/thunderbirdSmtp.png in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: warning: file dpkg/src/java/imapflags_it.properties has no final newline (either original or modified version) dpkg-source: warning: file dpkg/src/contribs/init/davmail-init has no final newline (either original or modified version) dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -b dpkg gave error exit status 2 How to add a new upstream version to the packaging repo? Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#569668: status: with r2174 no SMTP Body
Hi, The version of Davmail in Alioth seems to been upstream revision r2174. With that version send E-mail has only SMTP headers, no SMTP body. With self-compiled upstream package version r2192 I do get SMTP bodies in sent mail. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: having headers in IMAP
Op 2013-11-06 om 19:24 schreef Alexandre Rossi: Geert Stappers: Mmm, indeed headers are missing in messages from IMAP. Missing headers now fixed for me with http://anonscm.debian.org/gitweb/?p=pkg-java/davmail.git;a=blob;f=debian/patches/gnumail-fix;h=be0f7cebe084e7f3fb615eef5f039e82a3768a16;hb=HEAD. Yes, now also for me headers visible Alex Thank you for adding new upstream version to the Alioth git repository Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723028: RFS: libnu-htmlparser-java 1.4-1 (new package)
Op 2013-11-01 om 18:17 schreef Andrew Ross: On 31/10/13 22:57, Geert Stappers wrote: I am looking for a sponsor for my new package libnu-htmlparser-java. This is a dependency of the latest version of Netbeans. $ aptitude show libhtmlparser-java Package: libhtmlparser-java Section: java Description: java library to parse html snip/ Homepage: http://htmlparser.sourceforge.net/ Hi Geert, Hello Andy, Hello World, I'm aware of this package, but unfortunately it's not the same. The one I'm proposing is the Validator.nu HTML parser, as used by Netbeans. It's probably infeasible to patch Netbeans to use the sourceforge one, and it would certainly be a lot of work in comparison to packaging the correct dependency. Okay, thanks for telling that http://about.validator.nu/htmlparser/ is another Java HTML-parser as in package 'libhtmlparser-java'. The ITP at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723028 has now also this information. And about the request for sponsoring: When packaging is done, add information to the ITP where the Debian files are. Thanks, Andy Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#728535: debian-kernel-handbook: document rebuilding a single kernel module
Package: debian-kernel-handbook Version: 1.0.15 Severity: wishlist Hello, The Debian kernel handbook has a chapter Common kernel-related tasks. Which has paragraphs as Rebuilding official Debian kernel packages, Building a custom kernel from Debian kernel source and Building out-of-tree kernel modules. But I miss a paragraph how to (re)build a single kernel module. Typical use case is having a USB device with a supported chip set, but USB-IDs not enumerated in the driver. In other words: How to do simple driver development as adding USB-IDs? Please document which steps should be taken to have only a single module compiled that can be insmod to the Debian kernel. Groeten Geert Stappers -- Leven en laten leven signature.asc Description: Digital signature
Bug#728535: debian-kernel-handbook: document rebuilding a single kernel module
Op 2013-11-02 om 18:09 schreef Geert Stappers: But I miss a paragraph how to (re)build a single kernel module. Typical use case is having a USB device with a supported chip set, but USB-IDs not enumerated in the driver. In other words: How to do simple driver development as adding USB-IDs? Please document which steps should be taken to have only a single module compiled that can be insmod to the Debian kernel. Say I have a new webcam and want to build sunplus because I have added an extra USB-ID to drivers/media/usb/gspca/sunplus.c What options should I provide to `make`? Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723028: RFS: libnu-htmlparser-java 1.4-1 (new package)
Op 2013-10-31 om 22:15 schreef Andrew Ross: Dear Debian Java Team members, I am looking for a sponsor for my new package libnu-htmlparser-java. This is a dependency of the latest version of Netbeans. The changelog is as follows: libnu-htmlparser-java (1.4-1) unstable; urgency=low * Initial release (Closes: #723028) $ aptitude show libhtmlparser-java Package: libhtmlparser-java State: not installed Version: 1.6.20060610.dfsg0-3 Priority: optional Section: java Maintainer: Tiago Saboga tiagosab...@gmail.com Architecture: all Uncompressed Size: 340 k Depends: java-gcj-compat | java2-runtime Suggests: libhtmlparser-java-doc Description: java library to parse html HTML Parser is a Java library used to parse HTML in either a linear or nested fashion. Primarily used for transformation or extraction, it features filters, visitors, custom tags and easy to use JavaBeans. The two fundamental use-cases that are handled by the parser are extraction and transformation (the syntheses use-case, where HTML pages are created from scratch, is better handled by other tools closer to the source of data). In general, to use the HTMLParser you will need to be able to write code in the Java programming language. Although some example programs are provided that may be useful as they stand, it's more than likely you will need (or want) to create your own programs or modify the ones provided to match your intended application. Homepage: http://htmlparser.sourceforge.net/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: some progress and uploaded to experimental
Op 2013-10-21 om 08:22 schreef Alexandre Rossi: Hi, :-) * now investigating what is wrong the SMTP part in my second configuration. Fixed. Are you using the version which is on git://anonscm.debian.org/pkg-java/davmail.git ? Because I had an issue with IMAP, it did not include mail headers in messages. This was caused by depending on gnumail instead of javamail. Yes, I'm using the version from git://anonscm.debian.org/pkg-java/davmail.git Mmm, indeed headers are missing in messages from IMAP. Davmail 4.3.0 has been uploaded to 'experimental'. Let's see if a newer version is worth to get uploaded to 'unstable'. Alex Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: some progress
Sorry, for having you waiting. Previous months got other projects higher priority. Now back to this project, sponsoring Davmail. I have a working setup for Davmail for about two years. It is daily used. (Hence the reason for low priority for another setup.) Now I have second setup for Davmail, this time with a .deb that should be uploaded to the Debian archive. Status: * davmail runs a second computer * IMAP works fine * SMTP doesn't work yet * now investigating what is wrong the SMTP part in my second configuration. Feel free to ping me for another progress report. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720296: offering NMU
Hello Eduard, Does it help if I do a NMU to fix http://bugs.debian.org/720296 ? AIUI did #720296 cause the removal of apt-cacher-ng from testing. http://packages.qa.debian.org/a/apt-cacher-ng/news/20131015T163915Z.html is not really clear about the real reason for removal from testing. Something else, but related to this offer to help. Is there a public SCM repository with the authoritive version of apt-cacher-ng? The mecurial repo at Alioth was empty last time (about a month ago) I checked. Groeten Geert Stappers Happy User of apt-cacher-ng -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726656: more debconf for acng
Package: apt-cacher-ng Version: 0.7.18-1 Severity: normal Hello Eduard, Apt-cacher-ng works great, doing an upgrade isn't. It are the messages as in screenshot Setting up apt-cacher-ng (0.7.11-1) ... Configuration file `/etc/apt-cacher-ng/acng.conf' == Modified (by you or by a script) since installation. == Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** acng.conf (Y/I/N/O/D/Z) [default=N] ? /screenshot -- and the exta work that I would like to avoid. The Configuration file `/etc/apt-cacher-ng/acng.conf' == Modified is seen by me and others who modify 'CacheDir', 'Port' and 'BindAddress' on each upgrade. Also by all those who have to set 'Proxy'. It is something where debconf is part of the solution. The patch that I have been preparing, will follow soon. It was written with guidance of `man 7 debconf-devel`. Looking forward for feedback on to the proposed changes. Kind Regards Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726656: [patch] more debconf support for apt-cacher-ng
(s) (e.g. 0.0.0.0 will listen +# only to IPv4). +# +# Example: localhost 192.168.7.254 publicNameOnMainInterface +# +# When all wanted, comment out but keep the Parameter Keyword +# +# Default: not set, will listen on all interfaces and protocols +# +#BindAddress: to keep this Parameter Keyword + +# Where to store what we aiming to cache +CacheDir: /var/cache/apt-cacher-ng + +# l l +HERE +fi + if [ $1 = configure ]; then # user should exist. adduser sometimes fails (system range issue) but that's ok @@ -149,6 +194,32 @@ ;; esac + db_get $NAME/bindaddress + BINDADDRESS=$RET + if [ x$BINDADDRESS = xall ] ; then + BINDADDRESS='#BindAddress: to keep this Parameter Keyword' + else + BINDADDRESS=BindAddress: $BINDADDRESS + fi + db_get $NAME/port + PORT=$RET + db_get $NAME/proxy + PROXY=$RET + if [ x$PROXY = xnone ] ; then + PROXY='#Proxy: to keep this Parameter Keyword' + else + PROXY=Proxy: $PROXY + fi + + cp -a -f $CONFIGFILE $CONFIGFILE.tmp + + sed -e s~^ *CacheDir:.*~CacheDir: $CDIR~ \ + -e s/.*BindAddress.*/$BINDADDRESS/ \ + -e s/^ *Port:.*/Port:$PORT/ \ + -e s'.*Proxy.*'$PROXY' \ +$CONFIGFILE $CONFIGFILE.tmp + mv -f $CONFIGFILE.tmp $CONFIGFILE + db_stop || true rm -f $CFG/in.acng $CFG/mount.acng debian/apt-cacher-ng.postrm --- ../apt-cacher-ng-0.7.18.nen2//debian/apt-cacher-ng.postrm 2013-05-29 22:32:41.0 +0200 +++ ./debian/apt-cacher-ng.postrm 2013-10-10 07:26:34.688330786 +0200 @@ -1,7 +1,11 @@ #!/bin/sh -e +. /usr/share/debconf/confmodule + NAME=apt-cacher-ng -CDIR=/var/cache/$NAME +CONFIGFILE=/etc/$NAME/deb.conf +db_get $NAME/cachedir +CDIR=$RET LDIR=/var/log/$NAME if [ $1 = purge ]; then @@ -10,6 +14,7 @@ rm -f $LDIR/apt-cacher.err $LDIR/apt-cacher.log $LDIR/apt-cacher.log.* $LDIR/maint_*.log rmdir $LDIR 2/dev/null || true rm -rf /var/lib/apt-cacher-ng + rm -rf $CONFIGFILE dpkg-statoverride --remove /etc/apt-cacher-ng/security.conf 2/dev/null || true conf/acng.conf --- ../apt-cacher-ng-0.7.18.nen2//conf/acng.conf2013-07-28 20:09:43.0 +0200 +++ ./conf/acng.conf2013-10-10 07:26:34.688330786 +0200 @@ -2,7 +2,9 @@ # Letter case in directive names does not matter. Must be separated with colons. # Valid boolean values are a zero number for false, non-zero numbers for true. -CacheDir: /var/cache/apt-cacher-ng +# For your information: +# Keywords as 'Proxy', 'BindAddress, 'Port' and 'CacheDir' +# are now in another configuration file # set empty to disable logging LogDir: /var/log/apt-cacher-ng @@ -11,27 +13,6 @@ # found in the configuration directory # SupportDir: /usr/lib/apt-cacher-ng -# TCP (http) port -# Set to to emulate apt-proxy -Port:3142 - -# Addresses or hostnames to listen on. Multiple addresses must be separated by -# spaces. Each entry must be an exact local address which is associated with a -# local interface. DNS resolution is performed using getaddrinfo(3) for all -# available protocols (IPv4, IPv6, ...). Using a protocol specific format will -# create binding(s) only on protocol specific socket(s) (e.g. 0.0.0.0 will listen -# only to IPv4). -# -# Default: not set, will listen on all interfaces and protocols -# -# BindAddress: localhost 192.168.7.254 publicNameOnMainInterface - -# The specification of another proxy which shall be used for downloads. -# Username and password are, and see manual for limitations. -# -#Proxy: http://www-proxy.example.net:80 -#proxy: username:proxypassw...@proxy.example.net:3128 - # Repository remapping. See manual for details. # In this example, some backends files might be generated during package # installation using information collected on the system. source/acfg.cc --- ../apt-cacher-ng-0.7.18.nen2//source/acfg.cc2013-08-12 10:51:40.0 +0200 +++ ./source/acfg.cc2013-10-10 07:26:34.688330786 +0200 @@ -1058,6 +1058,7 @@ _ReadMainConfiguration(*it); #else _ReadMainConfiguration(confdir+SZPATHSEPacng.conf); + _ReadMainConfiguration(confdir+SZPATHSEPdeb.conf); #endif } debian/changelog --- ../apt-cacher-ng-0.7.18.nen2//debian/changelog 2013-08-20 00:47:19.0 +0200 +++ ./debian/changelog 2013-10-17 21:58:24.954370316 +0200 @@ -1,3 +1,9 @@ +apt-cacher-ng (0.7.18-1.1) UNRELEASED; urgency=low + + * debconf for Proxy, Bindaddress, Port and CacheDir (closes: #726656) + + -- Geert Stappers stapp...@stappers.nl Thu, 17 Oct 2013 21:57:34 +0200 + apt-cacher-ng (0.7.18-1) unstable; urgency=medium * New upstream release Done creating patch Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720296: offering NMU
Op 2013-10-17 om 22:37 schreef Eduard Bloch: Hallo Geert, nice to hear from you again. :-) * Geert Stappers [Thu, Oct 17 2013, 09:41:43PM]: Hello Eduard, snip/ However, I really wish that you hold this NMU back for a few days. I think you have thought it through and most of the changes will be used but there is at least one thing that looked suspicious (this patch of acfg.cc, the part you replaced was meant for systems without glob(), if I remember correctly, and shouldn't be effective on Debian/glibc based ones, but I am not sure though). So I really wish to proof read this without rush and having a clear mind. Okay, I'll hold my horses ;-) Unfortunately I am not in the condition to work on Debian packages in the next couple of days but I hope to find some spare time on Sunday. All fine, no worries, no need to rush. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656373: rebooting, without BIOS defaults
The 'BIOS reset to defaults' is not allways needed. A simple reboot seems also to help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708122: Asterisk 11 and Debian
Op 2013-08-07 om 12:09 schreef Tzafrir Cohen: On Wed, Aug 07, 2013 at 04:57:02AM -0400, Vlad Cerny wrote: Hello, I would like to ask about status of Asterisk 11 in Debian. I could find only version 1.8 packages. After extensive research I still do not understand if there are any (experimental) packages for version 11 (which should be LTS). Is there any FAQ regarding this? The only information I found is this: https://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/2013-June/023645.html If I want to run Asterisk 11 on Debian, am I supposed to compile it myself? If it is simple why there are no packages already? If the compilation and packaging is difficult for experienced maintainers then I have no chance to succeed. I have been using Asterisk for years, but always Debian packages, I had trouble with compilation. Could you please help? I can see no other way how to ask for an advice. Thank you very much, It depends on pjproject. Pjproject's packaging is almost complete. FWIW, pjproject was uploaded to the new at 2013-08-08 Bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708122 is marked as pending. http://anonscm.debian.org/gitweb/?p=pkg-voip/pjproject.git Asterisk has now been converted to git and should build. http://anonscm.debian.org/gitweb/?p=pkg-voip/asterisk.git Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569668: HB NP
Other week without an update on this bugreport, time for a short message: Heart Beat No Progress -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
