Bug#605267: Do set The Homepage control field to http://alioth.debian.org/projects/pkg-sysvinit
Source: sysvinit Version: 2.88dsf-13 Severity: minor http://alioth.debian.org/projects/pkg-sysvinit is the URL in copyright. The URL in the Homepage control field is dead. I suggest replacing it with the one in the copyright. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728289: Is 728289 still open, while claimed to be closed for ~3 months?
Quoting suod's changelog.Debian: sudo (1.8.8-3) unstable; urgency=low * document in README.Debian that the sssd support is enabled in the sudo package, not in the sudo-ldap package, closes: #728289 -- Bdale Garbee Wed, 30 Oct 2013 10:33:44 -0600 As of this writing, I see 728289 is still open. Without any messages that it was reopened, or otherwise manipulated. Version in testing is 1.8.9p4-1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727736: Latest linux-image-686-pae fail to boot a xen domU
Package: linux-image-686-pae Version: 3.10+52 Severity: normal This version depends on linux-image-3.10-3-686-pae. I am the client of a xen provider. Unfortuntely, because of that I don't have many details. I think there is a similar problem with both Amazon Web Service, and another provider. As far as I can tell, both sell xen domU. 3.2.0-4-686-pae works for both. With Amazon and 3.9 or 3.10, not sure which, I got The following last lines of the the System Log: ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: unknown compression format xc_dom_bzimageloader.c:394: panic: xc_dom_probe_bzimage_kernel: unknown compression format ERROR Invalid kernel: xc_dom_find_loader: no loader found xc_dom_core.c:523: panic: xc_dom_find_loader: no loader found xc_dom_parse_image returned -1 Error 9: Unknown boot failure Press any key to continue... I tried to run a self compiled kernel out of Debian source that would be bzip, not xz. Or that is what I think the compression methods were. I hardly remember. I think I have changed 4 settins of the config file, from xz to bzip. And then made a self compiled kernel. It was a crude guess. And did not work. As far as I remember, I did manage to run several self compiled kernels before that of 3.9. I don't have access to the to the Amazon machine any more. The issue is on https://forums.aws.amazon.com/thread.jspa?threadID=127984&tstart=0https://forums.aws.amazon.com/thread.jspa?threadID=127984&tstart=0. As can be seen, someone responded, asking if it is solved. With the 2nd xen domU provider, I currently have no means to get the boot messages. However the domU doesn't get to a point where I can connect to it. I suspect, but not sure, that it is the same issue. To me, it looks similar to Amazon 1/2 checks passed. The control panel claims the machine is offline, while the boot process supposedly succeeded. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727736: Latest linux-image-686-pae fail to boot a xen domU
On Sat, Oct 26, 2013 at 05:40:36AM +0100, Ben Hutchings wrote: > On Sat, 2013-10-26 at 06:27 +0200, Bastian Blank wrote: > > On Sat, Oct 26, 2013 at 05:18:56AM +0100, Ben Hutchings wrote: > > > I think this is just like missing hardware support, which we consider an > > > important bug. And it's also a regression in support. > > > > There is no hardware involved. > > If some relatively unchangeable VM environment can only boot > gzip-compressed kernels then using xz compression means we don't support > that 'hardware'. > > > > I don't know whether it is important enough to justify using less > > > efficient compression, but AWS is a very popular platform. Stock debian's 3.2.0-4-686-pae works. Does that means that a self compiled kernel that: 1. Using debian's config from the current-686-pae kernel, where cuurent is 3.10.11 at this time. and 2. Modifying the config to have: CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_XZ is not set is supposed to work? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727736: Latest linux-image-686-pae fail to boot a xen domU
On Sat, Oct 26, 2013 at 05:40:36AM +0100, Ben Hutchings wrote: > On Sat, 2013-10-26 at 06:27 +0200, Bastian Blank wrote: > > On Sat, Oct 26, 2013 at 05:18:56AM +0100, Ben Hutchings wrote: > > > I think this is just like missing hardware support, which we consider an > > > important bug. And it's also a regression in support. > > > > There is no hardware involved. > > If some relatively unchangeable VM environment can only boot > gzip-compressed kernels then using xz compression means we don't support > that 'hardware'. > > > > I don't know whether it is important enough to justify using less > > > efficient compression, but AWS is a very popular platform. > > > > AWS even provides pre-built PV-GRUB with support for XZ[1], so apart > > from a menu.lst nothing else is needed. > > OK, so maybe we should provide a NEWS entry or other documentation that > this is now required. > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedKernels.html was mentioned above by Bastian Blank. At http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727736#20. That document states, in the section `Limitations of PV-GRUB', that * PV-GRUB can boot kernels compressed using the gzip, bzip2, lzo, and xz compression formats. It also states that one of the reasonss of their choice of PV-GRUB is that it understands standard grub.conf or menu.lst commands, which allows it to work with all currently supported Linux distributions. I still think there is a problem with newer Debian's kernels and xen's PV domU. I'll try to obtain access to an aws vps to boot such a kernel and get the boot log. Like I wrote, such a kernel failed with another xen commercial provider. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727736: With full log: Wheezy -> testing kernel upgrade won't reboot.
I terminated the prevoius instance, and started from scratch.
1. Searching for an AMI: looking at public, 32-bit images and the Debian
platform. There are 93 images available. Looks like there are 2 or
3 for Wheezy. Choosing
AMI ID ami-f494e99d
AMI Name debian-wheezy-i386-20130705
Owner 379101102735
Source 379101102735/debian-wheezy-i386-20130705
Status available
State Reason -
Platform Debian
Architecture i386
Image Type machine
DescriptionDebian 7.1a (Wheezy) Base
Root Device Name /dev/sda1
Root Device Type ebs
RAM disk ID-
Kernel ID aki-b6aa75df
Product Codes -
Block Devices /dev/sda1=snap-df83078f:8:true:standard
and launch it.
2. Using a size of 30GB and without implicit deletion on termination.
It is running.
As an aside: there is
https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy
3. vps is running and can be connected by ssh.
4. root@ip-vps:~# shutdown -r now
successfuly reboots the machine. And so does Amazon API.
5. root@ip-vps:~# aptitude -R safe-upgrade linux-image-686-pae
Resolving dependencies...
The following NEW packages will be installed:
linux-image-3.10-3-686-pae{a}
The following packages will be upgraded:
initramfs-tools linux-image-686-pae
The following packages are RECOMMENDED but will NOT be installed:
busybox busybox-static firmware-linux-free libc6-i686
2 packages upgraded, 1 newly installed, 0 to remove and 134 not upgraded.
Need to get 24.3 MB of archives. After unpacking 87.5 MB will be used.
linux-image-3.10-3-686-pae is now installed. Grub is set to boot
it by default. Rebooting from inside the vps.
6. It takes a few minutes to see that Amazon API reports a running
Instant State and 1/2 checks for Status checks. The machine does not
respond to the network. The boot log follows. I hope the deletion
of many empty lines, and ncurses codes interfering with copy-paste
didn't remove important information.
ll now restart.
[1670414.627648] xenbus_dev_shutdown: device/console/0: Initialising !=
Connected, skipping
[1670414.992956] Disabling non-boot CPUs ...
[1670414.992974] Restarting system.
Xen Minimal OS!
start_info: 0xa01000(VA)
nr_pages: 0x26700
shared_inf: 0x7de2a000(MA)
pt_base: 0xa04000(VA)
nr_pt_frames: 0x9
mfn_list: 0x967000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: root=/dev/sda1 ro 4
stack: 0x946780-0x966780
MM: Init
_text: 0x0(VA)
_etext: 0x61e05(VA)
_erodata: 0x76000(VA)
_edata: 0x7b6b4(VA)
stack start: 0x946780(VA)
_end: 0x966d34(VA)
start_pfn: a10
max_pfn: 26700
Mapping memory range 0xc0 - 0x2670
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for b3e000(b3e000)-0(2670)
MM: done
Demand map pfns at 26701000-36701000.
Heap resides at 36702000-76702000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x26701000.
Initialising scheduler
Thread "Idle": pointer: 0x36702008, stack: 0xbf
Initialising xenbus
Thread "xenstore": pointer: 0x36702478, stack: 0x2660
Dummy main: start_info=0x966880
Thread "main": pointer: 0x367028e8, stack: 0x2661
"main" "root=/dev/sda1" "ro" "4"
vbd 2049 is hd0
*** BLKFRONT for device/vbd/2049 **
backend at /local/domain/0/backend/vbd/1400/2049
Failed to read /local/domain/0/backend/vbd/1400/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/1400/2049/feature-flush-cache.
62914560 sectors of 0 bytes
**
oting '3.10-3-686-pae'
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-3.10-3-686-pae root=/dev/xvda1 ro
initrd /boot/initrd.img-3.10-3-686-pae
ERROR Invalid kernel: xc_dom_probe_bzimage_kernel: unknown compression format
xc_dom_bzimageloader.c:394: panic: xc_dom_probe_bzimage_kernel: unknown
compression format
ERROR Invalid kernel: xc_dom_find_loader: no loader found
xc_dom_core.c:536: panic: xc_dom_find_loader: no loader found
xc_dom_parse_image returned -1
Error 9: Unknown boot failure
Press any key to continue...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727736: With full log: Wheezy -> testing kernel upgrade won't reboot.
On Sun, Oct 27, 2013 at 12:29:55PM +0100, Bastian Blank wrote: > On Sun, Oct 27, 2013 at 05:52:46AM +0200, Regid Ichira wrote: > >Kernel ID aki-b6aa75df > > This does not match _any_ of the PV-GRUB versions listed on [1]. > > Bastian > > [1]: > http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/UserProvidedKernels.html Indeed, aki-b6aa75df is not mentioned. I tried aki-919dcaf8, which is one of the PV-GRUB versions listed on [1]. It created a debian-wheezy-installer-amd64-20130613_deb7u1 (ami-29fea140). As documented at https://wiki.debian.org/Cloud/AmazonEC2DebianInstaller. I couldn't ssh to it, which might be reasonable if it gave an installer at the first steps. The AmazonEC2DebianInstaller states I need the euca2ools.deb. There are 4 images in each region. Half of that are i386 images. I couldn't find any i386 images in any region. Half of what is left are Ubuntu related images. There are many of these. I think that any debian related, in the whole list, is for the installer. I think the PV-GRUB able aki is irrelevant for our discussion: 1. Qouting http://wiki.xen.org/wiki/PvGrub: (pv-grub) runs an adapted version of the grub boot loader inside the created domain itself, and uses the regular domU facilities to read the disk mounted as root directory, fetch files from network, etc.; it also eventually loads the PV kernel and chain-boots it. In addition, http://wiki.xen.org/wiki/PvGrub has a link to Xen PVGRUB Howto: http://backdrift.org/xen-pvgrub-howto. Qouting this Howto: From the xen wiki: PV-GRUB replaces PyGrub to boot domU images safely: it runs the regular grub inside the created domain itself and uses regular domU facilities to read the disk / fetch files from network etc.; it eventually loads the PV kernel and chain-boots it. This means that your domU guests can install and manage their own kernels as if they were running on regular hardware. Yum, apt-get and other package management software will let you patch your virtual machine's kernel without the need to alter any Xen configuration. Doesn't all hat means the PV vps can mostly ignore pv-grub as long as it has a menu.lst file in the right place? I think that conclusion is also consistent with [1]. 2. Both ami-f494e99d and aki-919dcaf8 are created by the Debian AMI Account (account number 379101102735). ami-f494e99d, which is mentioned at https://wiki.debian.org/Cloud/AmazonEC2Image/Wheezy, uses aki-b6aa75df. I think Debian AMI Account people are official Debian representative. Thus, know what they are doing. 3. I wonder what is the difference between the xen minimal os that is mentioned in the boot logs, and PV-GRUB is a paravirtual "mini-OS" that runs a patched version of GNU GRUB 0.97 which is mentioned in [1]. Xen Minimal OS! is mentioned at the boot log I posted in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727736#40, which also shows the content of menu.lst. I think it won't be great surprise if Xen Minimal OS! and PV-GRUB is the same thing. So PV-GRUB booted ami-f494e99d, even though aki-b6aa75df is not in [1]. Most of all, which is also in accordabce with the quote of the http://backdrift.org/xen-pvgrub-howto from above, ami-f494e99d, which uses aki-b6aa75df, gave me a virtual wheezy machine. I can, and actually did, apt-get all its packages to the latest testing machine. I was able to reboot it when it had wheezy's kernel. Actually, before debian source 3.9 came out, I was able to use the latest debian source for that time, run a configold, make a self compiled kernel, install it and reboot the machine to the new self compiled kernel. That ability was broke by the debian source for 3.9. My conclusion is that there is an ability to run a wheezy machine, that can not be upgraded to testing machine. Isn't that a bug in Debian? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#727736: With full log: Wheezy -> testing kernel upgrade won't reboot.
On Mon, Oct 28, 2013 at 03:47:09AM +0100, Bastian Blank wrote: > On Mon, Oct 28, 2013 at 03:33:18AM +0200, Regid Ichira wrote: > > I think the PV-GRUB able aki is irrelevant for our discussion: > > The original error was from PV-GRUB. I'm not going to respond to the > rest of the mail as you did not do as I said. Please only replace the > aki with one listed on the page and show the new result. > I am not sure what you expected. I did not prepare the ami that included the problematic aki by myself. I don't have time, and aws resources, to prepare an ami myself. I don't know how to take an ami and replace its embedded aki with another aki. I insert here the boot log when booting the ami that included the aki from the list. Do tell me if you think I should post more data, or do other things. As before, the boot log is copied-pasted. With some empty lines removed. And probably ncurses codes interfere with vim. Xen Minimal OS! start_info: 0xae2000(VA) nr_pages: 0x26700 shared_inf: 0x7dcd2000(MA) pt_base: 0xae5000(VA) nr_pt_frames: 0x9 mfn_list: 0x9ae000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: root=/dev/sda ro 4 stack: 0x96d840-0x98d840 MM: Init _text: 0x0(VA) _etext: 0x7dc7d(VA) _erodata: 0x9a000(VA) _edata: 0x9fce0(VA) stack start: 0x96d840(VA) _end: 0x9ade40(VA) start_pfn: af1 max_pfn: 26700 Mapping memory range 0xc0 - 0x2670 setting 0x0-0x9a000 readonly skipped 0x1000 MM: Initialise page allocator for c1f000(c1f000)-2670(2670) MM: done Demand map pfns at 26701000-2026701000. Heap resides at 2026702000-4026702000. Initialising timer interface Initialising console ... done. gnttab_table mapped at 0x26701000. Initialising scheduler Thread "Idle": pointer: 0x2026702050, stack: 0x2666 Thread "xenstore": pointer: 0x2026702800, stack: 0x2667 xenbus initialised on irq 1 mfn 0xc8e977 Thread "shutdown": pointer: 0x2026702fb0, stack: 0x2668 Dummy main: start_info=0x98d940 Thread "main": pointer: 0x2026703760, stack: 0x2669 "main" "root=/dev/sda" "ro" "4" vbd 2048 is hd0 *** BLKFRONT for device/vbd/2048 ** backend at /local/domain/0/backend/vbd/1039/2048 Failed to read /local/domain/0/backend/vbd/1039/2048/feature-barrier. Failed to read /local/domain/0/backend/vbd/1039/2048/feature-flush-cache. 62914560 sectors of 512 bytes ** [H[J GNU GRUB version 0.97 (629760K lower / 0K upper memory) +-+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line. Debian Installer root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /vmlinuz root=LABEL=debian-installer ro console=hvc0 auto=true priority= critical url=http://169.254.169.254/latest/user-data DEBIAN_FRONTEND=text initrd /initrd.gz = Init TPM Front Tpmfront:Error Unable to read device/vtpm/0/backend-id during tpmfront initialization! error = ENOENT Tpmfront:Info Shutting down tpmfront close blk: backend=/local/domain/0/backend/vbd/1039/2048 node=device/vbd/2048 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.51-1 [0.00] Command line: root=LABEL=debian-installer ro console=hvc0 auto=true priority=critical url=http://169.254.169.254/latest/user-data DEBIAN_FRONTEND=text [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 pages of unused memory [0.00] Set 0 page(s) to 1-1 mapping [0.00] BIOS-provided physical RAM map: [0.00] Xen: - 000a (usable) [0.00] Xen: 000a - 0010 (reserved) [0.00] Xen: 0010 - 26f0 (usable) [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] No AGP bridge found [0.00] last_pfn = 0x26f00 max_arch_pfn = 0x4 [0.00] x2apic enabled by BIOS, switching to x2apic ops [0.00] init_memory_mapping: -26f0 [0.00] RAMDISK: 0193d000 - 064c4000 [0.00] NUMA turned off [0.00] Faking a node at -26f0 [0.00] Initmem setup node 0 -26f0 [0.00] NODE_DATA [266fb000 - 266f] [0.00] Zone PFN ranges: [0.00] DMA 0x0010 -> 0x1000 [0.00] DMA320x1000 -> 0x0010 [0.00] Normal empty [
Bug#729526: ssh.deb: somewhat misleading description
Package: ssh
Version: 1:6.4p1-1
Severity: minor
Tags: patch
$ dpkg -p ssh | grep -B2 remove
This metapackage is a convenient way to install both the OpenSSH client
and the OpenSSH server. It provides nothing in and of itself, so you
may remove it if nothing depends on it.
$
I think noting depends on it, so I tried to remove it.
$ aptitude -sy remove ssh | grep -A2 REMOVED
The following packages will be REMOVED:
openssh-server{u} ssh
0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
I do want openssh-server. Which doesn't strictly depend on ssh:
$ dpkg -p openssh-server | grep Depends | grep ' ssh'
$
As the reason is openssh-server is marked automatically by its pull
by ssh, should ssh's description made more accurate:
$ dpkg -p ssh | grep -A3 Description | diff ~/description -
2,4c2,4
< This metapackage is a convenient way to install, and possibly keep
< installed, both the OpenSSH client and the OpenSSH server. It
< provides nothing in and of itself.
---
> This metapackage is a convenient way to install both the OpenSSH client
> and the OpenSSH server. It provides nothing in and of itself, so you
> may remove it if nothing depends on it.
?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729526: ssh.deb: somewhat misleading description
On Wed, Nov 13, 2013 at 01:00:10PM -0800, Russ Allbery wrote:
> Regid Ichira writes:
>
> > I think noting depends on it, so I tried to remove it.
>
> > $ aptitude -sy remove ssh | grep -A2 REMOVED
> > The following packages will be REMOVED:
> > openssh-server{u} ssh
> > 0 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
> >
> > I do want openssh-server. Which doesn't strictly depend on ssh:
>
> > $ dpkg -p openssh-server | grep Depends | grep ' ssh'
> > $
>
> This is a standard aptitude thing with anything that was installed via a
> transitional package. You need to also run:
>
> aptitude unmarkauto openssh-server
Indeed I had to unmarkauto first.
My point is that my understanding of the description is that I could
remove the ssh package without unmarkauto. Which is why I think the
description should be modified. Am I the only one who might
understand the description this way?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#729770: sysctl.8: attempt to improve the phrasing in the DEPRECATED PARAMETERS section
Package: procps Version: 1:3.3.4-2 Severity: minor Tags: patch File: /usr/share/man/man8/sysctl.8.gz I am not a native English speaker. Am I right that the current phrasing is unfortunate? --- sysctl.82013-11-17 04:31:28.538097363 +0200 +++ sysctl.82013-11-17 04:28:09.0 +0200 @@ -142,9 +142,9 @@ The .B base_reachable_time and .B retrans_time -are deprecated. The sysctl command does not allow changing values of there -parameters. Users who insist to use deprecated kernel interfaces should values -to /proc file system by other means. For example: +are deprecated. The sysctl command does not allow setting values of these +parameters. Users who insist on using deprecated kernel interfaces should access +the /proc file system by other means. For example: .PP echo 256 > /proc/sys/net/ipv6/neigh/eth0/base_reachable_time .SH FILES -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741144: typo in changelog.gz: propagating, not propigating
Package: debhelper Version: 9.20140228 Severity: minor File: /usr/share/doc/debhelper/changelog.gz Tags: patch --- /usr/share/doc/debhelper/changelog.gz 2014-03-08 18:09:23.680845425 -0800 +++ changelog 2014-03-08 18:08:55.0 -0800 @@ -10,7 +10,7 @@ debhelper (9.20140227) unstable; urgency usemaps. Closes: #704443 * dh_installdocs: When doc dirs are symlinked make the dependency versioned per policy. Closes: #676777 - * dh_makeshlibs: Defer propigating dpkg-gensymbols error until + * dh_makeshlibs: Defer propagating dpkg-gensymbols error until all packages have been processed. Closes: #736640 * dh: Reject unknown parameters that are not dashed command-line parameters intended to be passed on to debhelper commands. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741386: calendar.judaic is out of date
Package: bsdmainutils Version: 9.0.5 Severity: normal File: /usr/share/calendar/calendar.judaic $ grep 2013 /usr/share/calendar/calendar.judaic * Jewish calendar for the CE year 2013 $ The problem stems from the low updating rate of bsdmainutils, coupled with the fact that the python script for generating calendar.judaic produces a calendar for one year. A short term solution might be to make an updated package, just for the sake of running the script for the CE year 2014. A long term solution might be to have a calendar.judaic directory, not just file. Since the script accepts a year argument, this directory might contain files for the current, and 2 successive, CE years. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698393: iptables.8: Should have been 10.0.0.0/8, not 10.0.0.8
Package: iptables Version: 1.4.14-3 Severity: normal Tags: patch File: /usr/share/man/man8/iptables.8.gz --- iptables.8 2013-01-17 23:46:42.811571599 +0200 +++ iptables.8.new 2013-01-17 23:28:29.0 +0200 @@ -809,7 +809,7 @@ matching on source port matching on subnet "1 packets per minute for every /28 subnet (groups of 8 addresses) in 10.0.0.0/8" => -\-s 10.0.0.8 \-\-hashlimit\-mask 28 \-\-hashlimit\-upto 1/min +\-s 10.0.0.0/8 \-\-hashlimit\-mask 28 \-\-hashlimit\-upto 1/min .SS helper This module matches packets related to a specific conntrack-helper. .TP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698400: icmpush.8: \fI' causes the ' character to be emphasized
Package: icmpush
Version: 2.2-6
Severity: minor
Tags: patch
File: /usr/share/man/man8/icmpush.8.gz
Without this patch, my non graphic terminal shows the data with
the underline extended to the single quote (') characters. I think
that on a graphic window, the single quote (') characters will be
in Italic.
--- icmpush.8 2013-01-18 00:05:30.869234933 +
+++ icmpush.8.new 2013-01-18 00:01:22.0 +
@@ -373,7 +373,7 @@ timeout to read the data will be 2 secon
'D E A T H' (blanks included). We will mask the source address as
192.168.0.255,
and we do not want to read the answers:
-\fBicmpush -echo -sp\fP \fI192.168.0.255\fP \fB-data\fP \fI'D E A T H'\fP
+\fBicmpush -echo -sp\fP \fI192.168.0.255\fP \fB-data\fP '\fID E A T H\fP'
\fB-to\fP \fI0 192.168.0.255\fP
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649045: cp -fv: File is removed before it is copied upon
Package: coreutils Version: 8.13-3 Severity: normal $ touch testFile1 testFile2 $ chmod -v -w testFile2 mode of `testFile2' changed from 0644 (rw-r--r--) to 0444 (r--r--r--) $ cp -vf testFile1 testFile2 `testFile1' -> `testFile2' removed `testFile2' I would expect the order of the messages to be reversed. Logically, testFile2 was removed before it was copied upon. I have noticed that copying the file works. I merely think that the printed messages should reflect the logical order of actions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697422: iptables.8::state match extension: make the states list more apparent
Package: iptables Version: 1.4.14-3 Severity: minor Tags: patch File: /usr/share/man/man8/iptables.8.gz 1. Make the states list more apparent 2. A few slight modifications, like replacing commas with periods, while visiting that text. --- iptables.8 2013-01-05 02:37:47.262723326 +0200 +++ iptables.8.mod 2013-01-05 02:32:35.0 +0200 @@ -1459,25 +1459,40 @@ the connection tracking state for this p .TP [\fB!\fP] \fB\-\-state\fP \fIstate\fP Where state is a comma separated list of the connection states to -match. Possible states are +match. Possible states are: +.RS +.TP .B INVALID meaning that the packet could not be identified for some reason which includes running out of memory and ICMP errors which don't correspond to any -known connection, +known connection. +.RE +.RS +.TP .B ESTABLISHED meaning that the packet is associated with a connection which has seen -packets in both directions, +packets in both directions. +.RE +.RS +.TP .B NEW meaning that the packet has started a new connection, or otherwise associated with a connection which has not seen packets in both -directions, and +directions. +.RE +.RS +.TP .B RELATED meaning that the packet is starting a new connection, but is associated with an existing connection, such as an FTP data transfer, or an ICMP error. +.RE +.RS +.TP .B UNTRACKED meaning that the packet is not tracked at all, which happens if you use the NOTRACK target in raw table. +.RE .SS statistic This module matches packets based on some statistic condition. It supports two distinct modes settable with the -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692072: README.Debian is misleading about no script to update options when ppp comes up
Package: bind9 Version: 1:9.8.1.dfsg.P1-4.3 Severity: normal Tags: patch File: /usr/share/doc/bind9/README.Debian.gz --- a/README.Debian 2012-11-02 00:22:45.963048224 +0200 +++ b/README.Debian 2012-11-02 00:19:35.0 +0200 @@ -134,7 +134,7 @@ run named non-root. PPP Control Script: - -Unfortunately, 'ndc reload' will not honor any command line options that were +Unfortunately, 'rndc reload' will not honor any command line options that were fed to named on the initial invocation. If you can live with that, and want to wiggle your DNS configuration when your PPP link goes up or down, the following script fragment from Francesco Potorti` may be helpful @@ -161,12 +161,7 @@ to you: rewriting the configuration file after ppp goes up. Then the script above makes bind reload the configuration. - Now, someone should write that clever script :-) - - By the way, this is a badly wanted feature, that should help setting up - a ppp connection automatically. Currently, setting up a ppp connection - is much easier on a windows system than on linux, and there is really no - reason why it should be so, given that all the tools are there. + One might want to investigate the offer of the resolvconf package in this area. Apparmor Profile -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692154: Shouldn't description mention also 3.2 kernels?
Package: libc6-i686 Version: 2.13-35 Severity: normal Package description mentions 2.6 kernels. These days, Debian also have 3.2 kernels. Shouldn't the description mention those kernels too? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692173: aptitude.8: doesn't that line referrs to the show command?
Package: aptitude Version: 0.6.8.1-2 Severity: normal Tags: patch File: /usr/share/man/man8/aptitude.8 - Without the patch: $ man aptitude | grep -B2 'listed following the search command' show Displays detailed information about one or more packages, listed following the search command. If a package name - With the patch: show Displays detailed information about one or more packages, listed following the show command. If a package name --- a/aptitude.82012-11-03 02:55:27.623656976 +0200 +++ b/aptitude.82012-11-03 02:47:20.0 +0200 @@ -449,7 +449,7 @@ and .PP \fBshow\fR .RS 4 -Displays detailed information about one or more packages, listed following the search command\&. If a package name contains a tilde character (\(lq\fB~\fR\(rq) or a question mark (\(lq\fB?\fR\(rq), it will be treated as a search pattern and all matching packages will be displayed (see the section +Displays detailed information about one or more packages, listed following the show command\&. If a package name contains a tilde character (\(lq\fB~\fR\(rq) or a question mark (\(lq\fB?\fR\(rq), it will be treated as a search pattern and all matching packages will be displayed (see the section \(lqSearch Patterns\(rq in the \fBaptitude\fR -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692154: Shouldn't description mention also 3.2 kernels?
On Fri, Nov 02, 2012 at 07:08:35PM -0700, Jonathan Nieder wrote: > severity 692154 minor > tags 692154 + patch > quit > > Regid Ichira wrote: > > > Package description mentions 2.6 kernels. These days, Debian also > > have 3.2 kernels. Shouldn't the description mention those kernels > > too? > > How about this patch? > > Thanks, > Jonathan > > Index: changelog > === > --- changelog (r??vision 5364) > +++ changelog (copie de travail) > @@ -1,6 +1,9 @@ > eglibc (2.13-37) UNRELEASED; urgency=low > > - * > + [ Jonathan Nieder ] > + * control.in/opt: remove outdated reference to 2.6 kernel from > +description of i686 variant. Thanks to Regid Ichira. Closes: > +#692154. > > -- Aurelien Jarno Fri, 26 Oct 2012 19:26:34 +0200 > > Index: control.in/opt > === > --- control.in/opt(r??vision 5364) > +++ control.in/opt(copie de travail) > @@ -11,10 +11,10 @@ > library and the standard math library, as well as many others. > . > This set of libraries is optimized for i686 machines, and will only be > - used if you are running a 2.6 kernel on an i686 class CPU (check the > - output of `uname -m'). This includes Pentium Pro, Pentium II/III/IV, > - Celeron CPU's and similar class CPU's (including clones such as AMD > - Athlon/Opteron, VIA C3 Nehemiah, but not VIA C3 Ezra). > + used on an i686 class CPU (check the output of `uname -m'). This includes > + Pentium Pro, Pentium II/III/IV, Celeron CPU's and similar class CPU's > + (including clones such as AMD Athlon/Opteron, VIA C3 Nehemiah, but not VIA > + C3 Ezla). > > Package: libc6-xen > Architecture: i386 This looks fine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692173: aptitude.8: doesn't that line referrs to the show command?
On Sat, Nov 03, 2012 at 10:55:07AM +0800, Daniel Hartwig wrote: > Control: tags -1 + confirmed > > On 3 November 2012 08:56, Regid Ichira wrote: > > $ man aptitude | grep -B2 'listed following the search command' > >show > >Displays detailed information about one or more packages, > >listed following the search command. If a package name > > > > - With the patch: > >show > >Displays detailed information about one or more packages, > >listed following the show command. If a package name > > The second part doesn't really make sense either way and should be > removed, though I don't want to disturb the translations at this point > so might leave this until after Wheezy. > > Regards I agree it is better left after Wheezy. I didn't understand what doesn't make sense? Doesn't $ aptitude show '?name(libc6-*)' make sense? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#695719: uuid-runtime relation to libuuid1
Pcakage: uuid-runtime Version: 2.20.1-5.2 Severity: normal uuid-runtime description states it is used by libuuid: $ dpkg -p uuid-runtime | tail -6 The uuidd daemon is used to generate UUIDs, especially time-based UUID???s, in a secure and guaranteed-unique fashion, even in the face of large numbers of threads trying to grab UUID???s running on different CPU???s. It is used by libuuid as well as the uuidgen program. Homepage: http://userweb.kernel.org/~kzak/util-linux/ Yet libuuid1 only recommends uuid-runtime: $ dpkg -p libuuid1 | grep Recommends Recommends: uuid-runtime Quoting http://bugs.debian.org/695719 : the vast majority of installations of libuuid1 don't actually *need* uuid-runtime Shouldn't the relation of uuid-runtime and libuuid1 be clearer? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696587: uuid-runtime relation to libuuid1
Package: uuid-runtime Version: 2.20.1-5.2 Severity: normal uuid-runtime description states it is used by libuuid: $ dpkg -p uuid-runtime | tail -6 The uuidd daemon is used to generate UUIDs, especially time-based UUID???s, in a secure and guaranteed-unique fashion, even in the face of large numbers of threads trying to grab UUID???s running on different CPU???s. It is used by libuuid as well as the uuidgen program. Homepage: http://userweb.kernel.org/~kzak/util-linux/ Yet libuuid1 only recommends uuid-runtime: $ dpkg -p libuuid1 | grep Recommends Recommends: uuid-runtime Quoting http://bugs.debian.org/695719 : the vast majority of installations of libuuid1 don't actually *need* uuid-runtime Shouldn't the relation of uuid-runtime and libuuid1 be clearer? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#695719: uuid-runtime relation to libuuid1
On Sun, Dec 23, 2012 at 09:12:01AM -0400, David Pr??vot wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Control: tags -1 moreinfo > > Hi, > > Le 23/12/2012 08:56, Regid Ichira a ??crit : > > > uuid-runtime description states it is used by libuuid: > [???] > > It is used by libuuid as well as the uuidgen program. > [???] > > Yet libuuid1 only recommends uuid-runtime: > [???] > > the vast majority of installations of libuuid1 don't actually > > *need* uuid-runtime > > > > Shouldn't the relation of uuid-runtime and libuuid1 be clearer? > > What kind of better relation do you expect, for a package that (can) use > another one, than recommending the said package? > Either the description of uuid-runtime should make it clear when it must be installed. Or libuuid should depends on uuid-runtime. Currently, I think that uuid-runtime description states a dependency of libuuid1, and the actual relations states another thing. An important note is that I find recommends vs suggests very confusing. > Regards > > David > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iQIcBAEBCAAGBQJQ1wMfAAoJELgqIXr9/gnyw9UQAIAtblj0vkgkf99qB3F85WgG > rR9FZ6sU2hzO4NHNuqBMpLOlduJDYkEy8ggbovLu4QB+nB6UP755B6avia636azH > DILH3gbyjS02+uqnevwHAiHM7Lg3j4SyhorK/5y4QhjdLtG+1ERLTJKPoKq7R11A > Gk4HDHl7tiKi39BpaX0E/FN2CMK/3RWR3O45akzTFrv34T3SjU7Lz957JQMBnkVb > StCMPl2brdA/R/vM+GC+lKuNAocMY+N58+dC5+OVGzSExcyxF2T/HHyOOjDbWIP0 > HiYFnreiw9twNnZmNIy7EPmf7JkcDstWBZNNlmbHVa/PwmtFJMoMEvloH488uN0Y > XSRC9xGw8sZUnIvXWxiMsVajYW9W1B0+o9QI6Wk76x4qtMlpFpZGYNHSZ53qasI9 > rinZUJ0vW9Ix4L9YKCbA+0+4/8teyZvIbaP2KDJvWOSAcNamKauxyvdSOh16C1Hs > Ja+d/hrCP+WLTnaMV/sx1INZn7ZoXMGIGeKBjXd4oOQGShDDU6/t1gBTj0hAVzsF > PTLioNGWVhRizMVsiSo6XXypZYvMn//QKJvAmX6WccrepS+dz6h+ZQwQgl4kssMT > /TP6jC+wuHEPcJLhMdYxgCX6+1TAUEuC9JC7d0T1XZA/OvtgBkNzhGkY1anQJB1h > dU3KaNnxLfXx6YMnmW7z > =cbSD > -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636029: What is the diffrence, compared to make listnewconfig ?
A note for those looking at this report: I think the issue of this bug should be persued. I wonder whether while doing that, one should not clarify the difference, if at all, between the quote from Documentation/kbuild/kconfig.txt that is shown at the beginning of Message #5 and the output of make listnewconfig. $ make CC=ccache\ gcc help | grep listnewconfig listnewconfig - List new options $ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575660: With last kernels, terminal/console processing getting worth.
On Sun, Sep 30, 2012 at 12:16:07PM -0700, Jonathan Nieder wrote: > Hi Regid, > > In 2010, Regid Ichira wrote: > > > 1) With 32-9, when tty1 shows the login prompt after boot, I can't see > >the characters that I type. I believe they are not processed as > >expected. This doesn't happen with 32-5. > [...] > > An old AT (DIN5 connector) white colored keyboard. > > 01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) > [...] > > By connecting over the network one can see that the i8042 interrupt > > counter does not go up. > > Do you still have access to this machine? If so, what kernel version > are you using these days, and how does it behave? > For some time now, the machine has problems with the display. Could be a bios setting issue, or some sort of a software problem. More likely there is one, or more, hardware failures. I am reluctened to make any tests or changes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#610297: Can't a Should-Start LSB header fix the problem?
Have you considered 1. a Should-Start LSB header - http://wiki.debian.org/LSBInitScripts 2. a virtual facility name - http://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#689953: svnpath's description in README: suversion repository or subversion repository?
Package: devscripts Version: 2.12.4 Severity: minor Tags: patch File: /usr/share/doc/README.gz --- a/README2012-10-08 11:40:46.491123496 +0200 +++ b/README2012-10-08 11:39:35.0 +0200 @@ -205,7 +205,7 @@ And now, in mostly alphabetical order, t - suspicious-source: outputs a list of files which are not common source files [python-magic] -- svnpath: Prints the path to the suversion repository of a subversion +- svnpath: Prints the path to the subversion repository of a subversion checkout. Also supports calculating the paths for branches and tags in a repository independent fashion. Used by debcommit to generate svn tags. [subversion] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690024: devscripts:rc-alert: A patch for on the fly selection of curl or wget
package: devscripts
Version: 2.12.4
Tags:patch
Files: /usr/bin/rc-alert
/usr/share/doc/devscripts/README.gz
Many devscripts choose on the fly whether to use curl or wget,
depending on what is installed. So far rc-alert was using solely
wget. The following patches tries to rectify this.
1. rc-alert is a Perl script. Can you verify that the patch is
correct, and reasonbly written, As far as Perl is concerned?
2. Are the following pairs equivalent?
2.1curl -qsR -C - $url
wget -qN --no-continue $url
2.2curl -qs $url
wget -q -O - $url
--- a/usr/bin/rc-alert 2012-09-25 01:45:59.0 +0200
+++ n/usr/bin/rc-alert 2012-10-09 01:26:26.0 +0200
@@ -158,8 +158,13 @@ $excludedists = remove_duplicate_values(
## First download the RC bugs page
-unless (system("command -v wget >/dev/null 2>&1") == 0) {
-die "$progname: this program requires the wget package to be installed\n";
+my $curl_or_wget;
+if (system("command -v curl >/dev/null 2>&1") == 0) {
+$curl_or_wget = "curl";
+} elsif (system("command -v wget >/dev/null 2>&1") == 0) {
+$curl_or_wget = "wget";
+} else {
+die "$progname: this program requires either the curl or the wget package
to be installed\n";
}
@@ -171,16 +176,33 @@ if (! -d $cachedir and $forcecache) {
if (-d $cachedir) {
chdir $cachedir or die "$progname: can't cd $cachedir: $!\n";
-# Either use the cached version because the remote hasn't been updated
-# (-N) or download a complete new copy (--no-continue)
-if (system('wget', '-qN', '--no-continue', $url) != 0) {
+# Is
+# curl -qsR -C - $url
+# equivalent to
+# wget -qN --no-continue $url
+# ?
+if ("$curl_or_wget" eq "curl") {
+if (system('curl', '-qsR', '-C', '-', $url) != 0) {
+ die "$progname: curl failed!\n";
+}
+} elsif (system('wget', '-qN', '--no-continue', $url) != 0) {
+# $curl_or_wget" eq "wget"
+# Either use the cached version because the remote hasn't
+# been updated (-N) or download a complete new copy
+# (--no-continue)
die "$progname: wget failed!\n";
}
open BUGS, $cachefile or die "$progname: could not read $cachefile: $!\n";
}
else {
-open BUGS, "wget -q -O - $url |" or
- die "$progname: could not run wget: $!\n";
+if ("$curl_or_wget" eq "curl") {
+open BUGS, "curl -qs $url |" or
+ die "$progname: could not run curl: $!\n";
+} else {
+# $curl_or_wget" eq "wget"
+open BUGS, "wget -q -O - $url |" or
+ die "$progname: could not run wget: $!\n";
+}
}
## Get list of installed packages (not source packages)
@@ -204,8 +226,13 @@ if ($popcon) {
or die "$progname: Unable to access popcon data: $!";
$pc_regex = '(\d+)\s\d+\s(\S+)';
} else {
- open POPCON, "wget -q -O - http://popcon.debian.org/by_$pc_by.gz |
gunzip -c |"
- or die "$progname: Not able to receive remote popcon data!";
+if ("$curl_or_wget" eq "curl") {
+ open POPCON, "curl -qs http://popcon.debian.org/by_$pc_by.gz |
gunzip -c |"
+} else {
+# $curl_or_wget" eq "wget"
+ open POPCON, "wget -q -O - http://popcon.debian.org/by_$pc_by.gz |
gunzip -c |"
+}
+or die "$progname: Not able to receive remote popcon data!";
$pc_regex = '(\d+)\s+(\S+)\s+(\d+\s+){5}\(.*\)';
}
--- a/README2012-10-09 00:35:19.512134230 +0200
+++ b/README2012-10-09 00:34:37.0 +0200
@@ -197,7 +197,8 @@ And now, in mostly alphabetical order, t
- pts-subscribe: subscribe to the PTS (Package Tracking System) for a
limited period of time. [bsd-mailx | mailx, at]
-- rc-alert: list installed packages which have release-critical bugs [wget]
+- rc-alert: list installed packages which have release-critical bugs
+ [curl | wget]
- rmadison: Remotely query the Debian archive database about packages.
[liburi-perl, wget | curl]
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121008234003.gb2...@nt1.in
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690024: A similar patch while one line shorter
A one line shorter then before, provided the Perl construct
if (condition) {
something piped_to |
}
else {
something_else piped_to |
}
or die "message"
does what seems to me the obviuos intention.
--- a/usr/bin/rc-alert 2012-09-25 01:45:59.0 +0200
+++ n/usr/bin/rc-alert 2012-10-09 01:26:26.0 +0200
@@ -158,8 +158,13 @@ $excludedists = remove_duplicate_values(
## First download the RC bugs page
-unless (system("command -v wget >/dev/null 2>&1") == 0) {
-die "$progname: this program requires the wget package to be installed\n";
+my $curl_or_wget;
+if (system("command -v curl >/dev/null 2>&1") == 0) {
+$curl_or_wget = "curl";
+} elsif (system("command -v wget >/dev/null 2>&1") == 0) {
+$curl_or_wget = "wget";
+} else {
+die "$progname: this program requires either the curl or the wget package
to be installed\n";
}
@@ -171,16 +176,32 @@ if (! -d $cachedir and $forcecache) {
if (-d $cachedir) {
chdir $cachedir or die "$progname: can't cd $cachedir: $!\n";
-# Either use the cached version because the remote hasn't been updated
-# (-N) or download a complete new copy (--no-continue)
-if (system('wget', '-qN', '--no-continue', $url) != 0) {
+# Is
+# curl -qsR -C - $url
+# equivalent to
+# wget -qN --no-continue $url
+# ?
+if ("$curl_or_wget" eq "curl") {
+if (system('curl', '-qsR', '-C', '-', $url) != 0) {
+ die "$progname: curl failed!\n";
+}
+} elsif (system('wget', '-qN', '--no-continue', $url) != 0) {
+# $curl_or_wget" eq "wget"
+# Either use the cached version because the remote hasn't
+# been updated (-N) or download a complete new copy
+# (--no-continue)
die "$progname: wget failed!\n";
}
open BUGS, $cachefile or die "$progname: could not read $cachefile: $!\n";
}
else {
-open BUGS, "wget -q -O - $url |" or
- die "$progname: could not run wget: $!\n";
+if ("$curl_or_wget" eq "curl") {
+open BUGS, "curl -qs $url |"
+} else {
+# $curl_or_wget" eq "wget"
+open BUGS, "wget -q -O - $url |"
+}
+or die "$progname: could not run $curl_or_wget: $!\n";
}
## Get list of installed packages (not source packages)
@@ -204,8 +225,13 @@ if ($popcon) {
or die "$progname: Unable to access popcon data: $!";
$pc_regex = '(\d+)\s\d+\s(\S+)';
} else {
- open POPCON, "wget -q -O - http://popcon.debian.org/by_$pc_by.gz |
gunzip -c |"
- or die "$progname: Not able to receive remote popcon data!";
+if ("$curl_or_wget" eq "curl") {
+ open POPCON, "curl -qs http://popcon.debian.org/by_$pc_by.gz |
gunzip -c |"
+} else {
+# $curl_or_wget" eq "wget"
+ open POPCON, "wget -q -O - http://popcon.debian.org/by_$pc_by.gz |
gunzip -c |"
+}
+or die "$progname: Not able to receive remote popcon data!";
$pc_regex = '(\d+)\s+(\S+)\s+(\d+\s+){5}\(.*\)';
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690056: wnpp-alert; Use curl or wget, whichever is installed
package: devscripts
Version: 2.12.4
Severity: normal
Tags: patch
Files:/usr/bin/wnpp-alert
/usr/share/doc/devscripts/README.gz
Many devscripts choose on the fly whether to use curl or wget,
depending on what is installed. So far wnpp-alert was using solely
wget. The following patches tries to rectify this.
--- a/usr/bin/wnpp-alert2012-09-25 01:45:59.0 +0200
+++ b/usr/bin/wnpp-alert2012-10-09 16:51:11.0 +0200
@@ -16,6 +16,8 @@
PROGNAME=`basename $0`
CACHEDIR=~/.devscripts_cache
CACHEDDIFF="${CACHEDIR}/wnpp-diff"
+CURLORWGET=""
+GETCOMMAND=""
usage () { echo \
"Usage: $PROGNAME [--help|-h|--version|-v|--diff|-d] [package ...]
@@ -52,8 +54,14 @@ wnppdiff () {
if [ "x$1" = "x--help" -o "x$1" = "x-h" ]; then usage; exit 0; fi
if [ "x$1" = "x--version" -o "x$1" = "x-v" ]; then version; exit 0; fi
-if ! command -v wget >/dev/null 2>&1; then
-echo "$PROGNAME: need the wget package installed to run this" >&2
+if command -v curl >/dev/null 2>&1; then
+CURLORWGET="curl"
+GETCOMMAND="curl -qs -o"
+elif command -v wget >/dev/null 2>&1; then
+CURLORWGET="wget"
+GETCOMMAND="wget -q -O"
+else
+echo "$PROGNAME: need either the curl or wget package installed to run
this" >&2
exit 1
fi
@@ -84,16 +92,16 @@ fi
# matching lines and then processing them, this attempts to sed
# every line; those which succeed execute the 'p' command, those
# which don't skip over it to the label 'd'
-wget -q -O $WNPPTMP http://www.debian.org/devel/wnpp/orphaned || \
-{ echo "wnpp-alert: wget http://www.debian.org/devel/wnpp/orphaned failed"
>&2; exit 1; }
+$GETCOMMAND $WNPPTMP http://www.debian.org/devel/wnpp/orphaned || \
+{ echo "wnpp-alert: $CURLORWGET http://www.debian.org/devel/wnpp/orphaned
failed" >&2; exit 1; }
sed -ne 's/.*\([^:<]*\)[:
]*\([^<]*\)<\/a>.*/O \1 \2 -- \3/; T d; p; : d' $WNPPTMP > $WNPP
-wget -q -O $WNPPTMP http://www.debian.org/devel/wnpp/rfa_bypackage || \
-{ echo "wnpp-alert: wget http://www.debian.org/devel/wnpp/rfa_bypackage";
>&2; exit 1; }
+$GETCOMMAND $WNPPTMP http://www.debian.org/devel/wnpp/rfa_bypackage || \
+{ echo "wnpp-alert: $CURLORWGET
http://www.debian.org/devel/wnpp/rfa_bypackage"; >&2; exit 1; }
sed -ne 's/.*\([^:<]*\)[:
]*\([^<]*\)<\/a>.*/RFA \1 \2 -- \3/; T d; p; : d' $WNPPTMP >> $WNPP
-wget -q -O $WNPPTMP http://www.debian.org/devel/wnpp/help_requested || \
-{ echo "wnpp-alert: wget http://www.debian.org/devel/wnpp/help_requested";
>&2; exit 1; }
+$GETCOMMAND $WNPPTMP http://www.debian.org/devel/wnpp/help_requested || \
+{ echo "wnpp-alert: $CURLORWGET
http://www.debian.org/devel/wnpp/help_requested"; >&2; exit 1; }
sed -ne 's/.*\([^:<]*\)[:
]*\([^<]*\)<\/a>.*/RFH \1 \2 -- \3/; T d; p; : d' $WNPPTMP >> $WNPP
cut -f3 -d' ' $WNPP | sort > $WNPP_PACKAGES
--- /usr/share/doc/devscripts/README.gz 2012-10-09 17:03:17.235201485 +0200
+++ README 2012-10-09 16:53:42.0 +0200
@@ -237,7 +237,7 @@ And now, in mostly alphabetical order, t
Debian archive [gnupg, debian-keyring, debian-maintainers, wget]
- wnpp-alert: list installed packages which are orphaned or up for adoption
- [wget]
+ [curl | wget]
- wnpp-check: check whether there is an open request for packaging or
intention to package bug for a package [wget]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690059: wnpp-check; On the fly choose curl or wget, whichever is installed
package: devscripts
Version: 2.12.4
Severity: normal
Tags: patch
Files:/usr/bin/wnpp-check
/usr/share/doc/devscripts/README.gz
Many devscripts choose on the fly whether to use curl or wget,
depending on what is installed. So far wnpp-check was using solely
wget. The following patches tries to rectify this.
--- /usr/bin/wnpp-check 2012-09-25 01:45:59.0 +0200
+++ wnpp-check 2012-10-09 17:12:50.0 +0200
@@ -10,6 +10,8 @@
PROGNAME=`basename $0`
PACKAGES="$@"
+CURLORWGET=""
+GETCOMMAND=""
usage () { echo \
"Usage: $PROGNAME [...]
@@ -33,8 +35,14 @@ if [ "x$1" = "x--help" -o "x$1" = "x-h"
if [ "x$1" = "x--version" -o "x$1" = "x-v" ]; then version; exit 0; fi
if [ "x$1" = "x" ]; then usage; exit 1; fi
-if ! command -v wget >/dev/null 2>&1; then
-echo "$PROGNAME: need the wget package installed to run this" >&2
+if command -v curl >/dev/null 2>&1; then
+CURLORWGET="curl"
+GETCOMMAND="curl -qs -o"
+elif command -v wget >/dev/null 2>&1; then
+CURLORWGET="wget"
+GETCOMMAND="wget -q -O"
+else
+echo "$PROGNAME: need either the curl or wget package installed to run
this" >&2
exit 1
fi
@@ -50,12 +58,12 @@ trap "rm -f '$WNPP' '$WNPPTMP' '$WNPP_PA
# every line; those which succeed execute the 'p' command, those
# which don't skip over it to the label 'd'
-wget -q -O $WNPPTMP http://www.debian.org/devel/wnpp/being_packaged || \
-{ echo "wnpp-check: wget http://www.debian.org/devel/wnpp/being_packaged
failed" >&2; exit 1; }
+$GETCOMMAND $WNPPTMP http://www.debian.org/devel/wnpp/help_requested || \
+{ echo "wnpp-alert: $CURLORWGET
http://www.debian.org/devel/wnpp/help_requested"; >&2; exit 1; }
sed -ne 's/.*\([^:<]*\)[:
]*\([^<]*\)<\/a>.*/ITP \1 \2 -- \3/; T d; p; : d' $WNPPTMP > $WNPP
-wget -q -O $WNPPTMP http://www.debian.org/devel/wnpp/requested || \
-{ echo "wnpp-check: wget http://www.debian.org/devel/wnpp/requested"; >&2;
exit 1; }
+$GETCOMMAND $WNPPTMP http://www.debian.org/devel/wnpp/help_requested || \
+{ echo "wnpp-alert: $CURLORWGET
http://www.debian.org/devel/wnpp/help_requested"; >&2; exit 1; }
sed -ne 's/.*\([^:<]*\)[:
]*\([^<]*\)<\/a>.*/RFP \1 \2 -- \3/; T d; p; : d' $WNPPTMP >> $WNPP
awk -F' ' '{print $3" ("$1" - #"$2")"}' $WNPP | sort > $WNPP_PACKAGES
--- /usr/share/doc/devscripts/README.gz 2012-10-09 17:19:43.957978654 +0200
+++ README 2012-10-09 17:14:01.0 +0200
@@ -240,7 +240,7 @@ And now, in mostly alphabetical order, t
[wget]
- wnpp-check: check whether there is an open request for packaging or
- intention to package bug for a package [wget]
+ intention to package bug for a package [curl | wget]
- wrap-and-sort: wrap long lines and sort items in packaging files
[python-debian]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690485: accopt.html: Isn't there a full stop ('.') at the middle of a sentence?
Package: ntp-doc
Version: 1:4.2.6.p5+dfsg-2
Severity: minor
Tags: patch
File: /usr/share/doc/ntp-doc/html/accopt.html
Isn't there a full stop ('.'), after the word flags, which is at
the middle of a sentence?
--- /usr/share/doc/ntp-doc/html/accopt.html 2009-12-09 09:36:36.0
+0200
+++ accopt.html 2012-10-14 21:29:15.0 +0200
@@ -103,7 +103,7 @@ time) in log2 s with default
to indicate the default entry.
Some flags have the effect to deny service, some have the effect to
- enable service and some are conditioned by other flags. The flags. are
+ enable service and some are conditioned by other flags. The flags are
not orthogonal, in that more restrictive flags will often make less
restrictive
ones redundant. The flags that deny service are classed in two
categories,
those that restrict time service and those that restrict informational
queries
@@ -199,4 +199,4 @@ time) in log2 s with default
-
\ No newline at end of file
+
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690485: accopt.html: `present, though if it is otherwise unconfigured;'
The following patch includes the prevoius one. It also fixes what looks to me a problem with the last sentence on the page. --- /usr/share/doc/ntp-doc/html/accopt.html 2009-12-09 09:36:36.0 +0200 +++ accopt.html 2012-10-14 22:45:11.0 +0200 @@ -103,7 +103,7 @@ time) in log2 s with default to indicate the default entry. Some flags have the effect to deny service, some have the effect to - enable service and some are conditioned by other flags. The flags. are + enable service and some are conditioned by other flags. The flags are not orthogonal, in that more restrictive flags will often make less restrictive ones redundant. The flags that deny service are classed in two categories, those that restrict time service and those that restrict informational queries @@ -189,7 +189,7 @@ time) in log2 s with default Default restriction list entries with the flags ignore, ntpport, for each of the local host's interface addresses are inserted into the table at startup to prevent the server from attempting to synchronize to its own time. - A default entry is also always present, though if it is otherwise unconfigured; + A default entry is also always present, though it is, by default, otherwise unconfigured; no flags are associated with the default entry (i.e., everything besides your own NTP server is unrestricted). @@ -199,4 +199,4 @@ time) in log2 s with default - \ No newline at end of file + -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#690485: ntpd.html: compters are, probably, computers
--- /usr/share/doc/ntp-doc/html/ntpd.html 2011-07-11 05:18:26.0 +0300 +++ ntpd.html 2012-10-15 22:49:39.0 +0200 @@ -39,7 +39,7 @@ Once the NTP software distribution has been compiled and installed and the configuration file constructed, the next step is to verify correct operation and fix any bugs that may result. Usually, the command line that starts the daemon is included in the system startup file, so it is executed only at system boot time; however, the daemon can be stopped and restarted from root at any time. Once started, the daemon will begin sending and receiving messages, as specified in the configuration file. Setting the Time and Frequency The ntpd program operates by exchanging messages with one or more servers at designated intervals ranging from about one minute to about 17 minutes. When started, the program requires several exchanges while the algorithms accumulate and groom the data before setting the clock. The initial delay to set the clock can be reduced using options on the Server Options page. - Most compters today incorporate a time-of-year (TOY) chip to maintain the time during periods when the power is off. When the machine is booted, the chip is used to initialize the operating system time. In case there is no TOY chip or the TOY time is more than 1000 s from the server time, ntpd assumes something must be terribly wrong and exits with a panic message to the system operator. With the -g option the clock will be initially set to the server time regardless of the chip time. However, once the clock has been set, an error greater than 1000 s will cause ntpd to exit anyway. + Most computers today incorporate a time-of-year (TOY) chip to maintain the time during periods when the power is off. When the machine is booted, the chip is used to initialize the operating system time. In case there is no TOY chip or the TOY time is more than 1000 s from the server time, ntpd assumes something must be terribly wrong and exits with a panic message to the system operator. With the -g option the clock will be initially set to the server time regardless of the chip time. However, once the clock has been set, an error greater than 1000 s will cause ntpd to exit anyway. Under ordinary conditions, ntpd slews the clock so that the time is effectively continuous and never runs backwards. If due to extreme network congestion an error spike exceeds the step threshold, by default 128 ms, the spike is discarded. However, if the error persists for more than the stepout threshold, by default 900 s, the system clock is stepped to the correct value. In practice the need for a step has is extremely rare and almost always the result of a hardware failure. With the -x option the step threshold is increased to 600 s. Other options are available using the tinker command on the Miscellaneous Options page. The issues should be carefully considered before using these options. The maximum slew rate possible is limited to 500 parts-per-million (PPM) by the Unix kernel. As a result, the clock can take 2000 s for each second the clock is outside the acceptable range. During this interval the clock will not be consistent with any other network clock and the system cannot be used for distributed applications that require correctly synchronized network time. The frequency file, usually called ntp.drift, contains the latest estimate of clock frequency. If this file does not exist when ntpd is started, it enters a special mode designed to measure the particular frequency directly. The measurement takes 15 minutes, after which the frequency is set and ntpd resumes normal mode where the time and frequency are continuously adjusted. The frequency file is updated at intervals of an hour or more depending on the measured clock stability. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691680: mount.8: `An unbindable' instead of `A unbindable'
Package: mount Version: 2.20.1-5.2 Severity: minor Tags: patch File: /usr/share/man/man8/mount.8.gz --- a/mount.8 2012-10-28 17:25:03.891071581 +0200 +++ b/mount.8 2012-10-28 17:22:46.0 +0200 @@ -437,7 +437,7 @@ Since Linux 2.6.15 it is possible to mar private, slave or unbindable. A shared mount provides ability to create mirrors of that mount such that mounts and umounts within any of the mirrors propagate to the other mirror. A slave mount receives propagation from its master, but -any not vice-versa. A private mount carries no propagation abilities. A +any not vice-versa. A private mount carries no propagation abilities. An unbindable mount is a private mount which cannot be cloned through a bind operation. Detailed semantics is documented in Documentation/filesystems/sharedsubtree.txt file in the kernel source tree. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#478567: Why vsftpd.logrotate commenting on ftpd ability to handle SIGHUP?
Package: vsftpd
Version: 3.0.2-1
Severity: minor
Tags: patch
File: /etc/logrotate.d/vsftpd
--- a/etc/logrotate.d/vsftpd2009-02-05 17:48:08.0 +0200
+++ b/etc/logrotate.d/vsftpd2012-09-29 22:39:16.0 +0200
@@ -2,7 +2,7 @@
{
create 640 root adm
- # ftpd doesn't handle SIGHUP properly
+ # no signal will make vsftpd reopen its log files
missingok
notifempty
rotate 4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693255: (no subject)
Package: manpages-dev
Version: 3.42-1
Severity: minor
Tags: patch
File: /usr/share/man/man3/fputs.3.gz
Adding a space character, after the comma, in putc(c,stdout):
--- a/fputs.3 2012-11-14 18:27:50.763875583 +0200
+++ b/fputs.3 2012-11-14 18:22:26.0 +0200
@@ -63,7 +63,7 @@ more than once.
.PP
.BI "putchar(" c );
is equivalent to
-.BI "putc(" c , stdout ).
+.BI "putc(" c ", " stdout ).
.PP
.BR puts ()
writes the string
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693993: manual.txt: option is ignored if $text_flowed is set, too because some reason
Package: mutt Version: 1.5.21-6.2 Severity: minor Tags: patch File: /usr/share/doc/mutt/manual.txt.gz Does the word `too' in place? --- a/manual.txt2012-11-22 19:28:30.418118366 +0200 +++ b/manual.txt2012-11-22 19:25:20.0 +0200 @@ -7608,7 +7608,7 @@ Specifies the string to prepend to each which you are replying. You are strongly encouraged not to change this value, as it tends to agitate the more fanatical netizens. -The value of this option is ignored if $text_flowed is set, too because the +The value of this option is ignored if $text_flowed is set, because the quoting mechanism is strictly defined for format=flowed. This option is a format string, please see the description of $index_format for -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693993: 3.112. index_format: Add a reference to where the %? construct is described
--- a/manual.txt2012-11-22 21:11:57.590632242 +0200 +++ b/manual.txt2012-11-22 21:11:51.0 +0200 @@ -7623,7 +7623,8 @@ This variable allows you to customize th personal taste. ???Format strings??? are similar to the strings used in the C function printf(3) to -format output (see the man page for more details). The following sequences are +format output (see the man page for more details). For an explanation of the +%? construct, see the $status_format description. The following sequences are defined in Mutt: ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: Need to prefix a host list definition with the hostlist keyword
host_reject_connection is a deprecated configuration item. I think that without the following patch it would not work as described. I also think this is not the only place in which spec.txt attempts to define a typed list without specifying the type. --- spec.txt2012-01-11 00:02:27.0 +0200 +++ spec.txt.mod2012-01-11 00:03:30.0 +0200 @@ -7529,7 +7529,7 @@ level - they are not recognized in an in * If any item that follows "+include_unknown" requires information that cannot found, Exim behaves as if the host does match the list. For example, -host_reject_connection = +include_unknown:*.enemy.ex +hostlist host_reject_connection = +include_unknown:*.enemy.ex rejects connections from any host whose name matches "*.enemy.ex", and also any hosts whose name it cannot find. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655920: Rebooting by kexec leaves the old BOOT_IMAGE in /proc/cmdline
Package: kexec-tools Version: 1:2.0.2-3 Severity: normal I invoke freshly installed kernel images by rebooting with kexec. $ cat /proc/cmdline root=/dev/sda1 ro BOOT_IMAGE=/boot/vmlinuz-3.1.1-1.1 $ uname -r 3.1.8-2.1 $ ls -l /vmlinuz lrwxrwxrwx 1 root root 25 Jan 14 18:08 /vmlinuz -> boot/vmlinuz-3.1.8-2.1 I think 3.1.1-1.1 got there a few weeks ago, when I actually powered down the machine, and afterwards cold boot it. It had that kernel version back then. Is not updating /proc/cmdline expected? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: Need to prefix a host list definition with the hostlist keyword
--- On Tue, 1/10/12, Adam D. Barratt wrote: > On Tue, 2012-01-10 at 14:18 -0800, Regid Ichira wrote: > > host_reject_connection is a deprecated configuration item > > I think that without the following patch it would not work as > > described. I also think this is not the only place in which > > spec.txt attempts to define a typed list without specifying > > the type. > > It's not a typed list. As you said yourself, it's a > configuration item - one whose /value/ is a list. Thank you. You are right. > I'm not actually sure if exim will let you do what your patch > suggests (define a list with the same name as a configuration > item) but it certainly seems like it would be confusing. > I think it does let me define my own hostlist host_reject_connection. And it does not use its value for the configuration item with the same name. Indeed, this is confusing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#648633: o properly document non preserved variables
Did I understand correctly that not preserving changes across reboots to the UTC variable, and possibly others, will not be changed in the future? If so, please properly document that. I think the first place such a thing should be documented is in the related file, which is currently /etc/default/rcS. As far as I can tell, the current situation is not documented at all. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#659836: hostname.1: Ssee -->> See
Package: hostname Version: 3.10 Severity: minor File: /usr/share/man/man1/hostname.1.gz Tags: patch --- /usr/share/man/man1/hostname.1.gz 2012-02-14 04:14:36.563040001 +0200 +++ hostname.1 2012-02-14 04:08:19.0 +0200 @@ -186,7 +186,7 @@ Display the name of the DNS domain. Don to get the DNS domain name because it will show the NIS domain name and not the DNS domain name. Use .B dnsdomainname -instead. Ssee the warnings in section +instead. See the warnings in section .B "THE FQDN" above, and avoid using this option. .TP -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: When reading, it a applies a timeout
Package: exim4-base Version: 4.80-3 --- a/spec.txt 2012-06-30 16:55:30.633325335 +0300 +++ b/spec.txt2012-06-30 16:50:00.0 +0300 @@ -18455,7 +18455,7 @@ message, which happens if the return_mes |transport_filter_timeout|Use: transports|Type: time|Default: 5m| ++---+--+---+ -When Exim is reading the output of a transport filter, it a applies a timeout +When Exim is reading the output of a transport filter, it applies a timeout that can be set by this option. Exceeding the timeout is normally treated as a temporary delivery failure. However, if a transport filter is used with a pipe transport, a timeout in the transport filter is treated in the same way as a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#680149: lvremove: Do add a --ignoremonitoring command line switch
Package: lvm2 Version: 2.02.95-4 Severity: wishlist File: /sbin/lvremove Consider: # lvcreate --permission r --size 1000m --snapshot \ > --name homeSnap /dev/vg00/home Logical volume "homeSnap" created # lvremove -f /dev/vg00/homeSnap /sbin/dmeventd: stat failed: No such file or directory Logical volume "homeSnap" successfully removed Do add lvremove a --ignoremonitoring command line switch. lvcreate has it: $ $ man lvcreate | grep -C1 'Make no attempt to interact' --ignoremonitoring Make no attempt to interact with dmeventd unless --mon- itor is specified. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: Does exim -d-all include, or exclude, "memory"?
$ zgrep -A47 -B1 'When -d is used' /usr/share/doc/exim4/spec.txt.gz | sed '/^ pid/,/^uid/d' | sed '/^verify/s/.*/... Many items deleted for the purpose of this message/' | sed '/^auth/,/^lookup/d' | sed '/^ acl/s/.*/... Many items deleted for the purpose of this message/' | cat -n 1 2 When -d is used, -v is assumed. If -d is given on its own, a lot of 3 standard debugging data is output. This can be reduced, or increased to 4 include some more rarely needed information, by directly following -d with 5 a string made up of names preceded by plus or minus characters. These add 6 or remove sets of debugging data, respectively. For example, -d+filter adds 7 filter debugging, whereas -d-all+filter selects only filter debugging. Note 8 that no spaces are allowed in the debug setting. The available debugging 9 categories are: 10 11 ... Many items deleted for the purpose of this message 12 memory memory handling 13 ... Many items deleted for the purpose of this message 14 all almost all of the above (see below), and also -v 15 16 The "all" option excludes "memory" when used as "+all", but includes it for 17 "-all". The reason for this is that "+all" is something that people tend to 18 use when generating debug output for Exim maintainers. If "+memory" is 19 included, an awful lot of output that is very rarely of interest is 20 generated, so it now has to be explicitly requested. However, "-all" does 21 turn everything off. 22 $ When referring to the exclusion, or inclusion, of "memory" by "-all", I think there is a mismatch between lines 16-17 to lines 7-8 or 20-21. Is the following patch justified? --- /usr/share/doc/exim4/spec.txt 2012-01-30 02:36:24.0 +0200 +++ /usr/share/doc/exim4/spec.txt.mod 2012-01-30 02:38:56.0 +0200 @@ -3370,2 +3370,2 @@ brief message about itself and exits. -The "all" option excludes "memory" when used as "+all", but includes it for -"-all". The reason for this is that "+all" is something that people tend to +The "all" option excludes "memory" when used as "+all". +The reason for this is that "+all" is something that people tend to -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: return code: "or 1 any other" -> "or 1 for any other"
--- /usr/share/doc/exim-base/spec.txt 2012-02-03 16:14:32.703623796 +0200 +++ /usr/share/doc/exim-base/spec.txt.mod 2012-02-03 15:44:41.0 +0200 @@ -3783,8 +3783,8 @@ brief message about itself and exits. Provided this error message is successfully sent, the Exim receiving process exits with a return code of zero. If not, the return code is 2 if -the problem is that the original message has no recipients, or 1 any other -error. This is the default -oex option if Exim is called as rmail. +the problem is that the original message has no recipients, or 1 for any +other error. This is the default -oex option if Exim is called as rmail. -oem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: -Tqt: "This an option" -> "This is an option"
--- /usr/share/doc/exim-base/spec.txt 2012-02-06 16:26:00.505182473 +0200 +++ /usr/share/doc/exim-base/spec.txt.mod 2012-02-06 16:25:14.0 +0200 @@ -4151,10 +4151,10 @@ brief message about itself and exits. -Tqt -This an option that is exclusively for use by the Exim testing suite. It is -not recognized when Exim is run normally. It allows for the setting up of -explicit "queue times" so that various warning/retry features can be -tested. +This is an option that is exclusively for use by the Exim testing suite. +It is not recognized when Exim is run normally. It allows for the setting +up of explicit "queue times" so that various warning/retry features can +be tested. -t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: section 10.7 and caching a typed list which includes a file name
--- On Sat, 7/14/12, Andreas Metzler wrote:
> On 2012-01-08 Regid Ichira
> wrote:
> > Based on
>
> > $ zgrep -A22 '^10.3 File names
> in lists' \
> > >
> /usr/share/doc/exim4-base/spec.txt.gz | tail -4
> > Putting a file name in a list
> has the same effect as inserting
> > each line of the file as an
> item in the list (blank lines and
> > comments excepted). However,
> there is one important difference:
> > the file is read each time the
> list is processed, so if its
> > contents vary over time, Exim's
> behaviour changes.
>
> > I think the following patch should be applied to
> section '10.7 Named
> > list caching':
>
> > --- spec.txt 2012-01-09 00:09:38.0
> +0200
> > +++ spec.txt.mod 2012-01-09
> 00:11:49.0 +0200
> [...]
> > -the cache operates only if the list contains no $
> characters, which guarantees
> [...]
> > +the cache operates only if the list contains no $
> characters, and no file
> > +names, which guarantees that it will not change when
> it is expanded.
> [...]
>
> I am pretty sure this change is not correct, the contents of
> files are
> cached.
>
> For illustration, compare the results of these two settings
> (with
> /etc/exim4/dc_other_hostnames containing a single line,
> listing a
> single domain):
> [1] domainlist local_domains =
> ${readfile{/etc/exim4/dc_other_hostnames}}
> [2] domainlist local_domains =
> /etc/exim4/dc_other_hostnames
>
> "exim -d+expand" shows this for [2]
> check domains = !+local_domains
> cached no match for +local_domains
> cached lookup data = NULL
>
I have tried to reproduce that, and couldn't. I have no experience
with debugging exim. What I did is to set local_domains as you
suggested and
# exim -d+expand+lookup -bP +local_domain
. I couldn't see the output you mentioned. Did I miss it? I guess
it will be better to do that while exim actually delievrs a message.
Can I take upstream's default run time configuration, set
local_domains as required, optionally change the listening port, and
see that output? What exactly should I do?
I do have some comments on the output you gave. I am not sure
they are worth something, but here it is. Just in case:
1. What is the related output for [1]?
2. Doesn't the output you gave actually shows that the cache doesn't
work for file names? I mean, it does say it wasn't in the cache,
doesn't it?
3. Perhaps the data is expected not to be cached for the first
evaluation of the list. Which means that a correct test must
make sure that the delivery process will evaluate the list more
then once? Did your test made sure the list is evaluated more
then once?
> I think "if its contents vary over time" refers to the fact
> that a
> newly forked forked exim binary (as happens for every
> incoming
> connection or outgoing delivery) will read the new file.
>
All I have is what I qouted from spec.txt.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#653750: retitle - nightmare bug
--- On Wed, 7/18/12, Marc Haber wrote: > retitle #653750 nightmare multi-bug > about spec.txt - please do not report more issues here - > file new bugs > thanks Do you think it would help if I will: 1. Copy the whole, multiple issues report, as a message to pkg-exim4-users. Just to have it archived. 2. close the bug. ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#686701: /usr/share/man/man5/rcS.5: add fsck.5 to the the list in SEE ALSO
Package: initscripts Version: 2.88dsf-31 Severity: minor Tags: patch File: /usr/share/man/man5/rcS.5 Rational: for more details about FSCK. --- a/rcS.5 2012-09-04 23:26:41.077717991 +0300 +++ b/rcS.5 2012-09-04 23:18:06.0 +0300 @@ -103,6 +103,7 @@ Miquel van Smoorenburg .SH SEE ALSO +.BR fsck (8), .BR hwclock (5), .BR hwclock (8), .BR inetd (8), -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687123: zgrep OPTIONs are NOT the same as for 'grep'.
Package: gzip Version: 1.5-1.1 Severity: normal Tags: patch Files:/bin/zgrep /usr/share/man/man1/zgrep.1.gz Rational: $ grep OPTIONs /bin/zgrep OPTIONs are the same as for 'grep'. $ grep -C2 exc /bin/zgrep case $option in (-[drRzZ] | --di* | --exc* | --inc* | --rec* | --nu*) printf >&2 '%s: %s: option not supported\n' "$0" "$option" exit 2;; As an aside, the patch for zgrep.1 has comma (`,') at the beginning of two of the lines. I think those commas should be written at the end of the prevoius line, without being emphazised, --- a/bin/zgrep 2012-06-20 18:30:33.0 +0300 +++ b/bin/zgrep 2012-09-10 02:37:13.0 +0300 @@ -42,6 +42,9 @@ usage="Usage: $0 [OPTION]... [-e] PATTER Look for instances of PATTERN in the input FILEs, using their uncompressed contents if they are compressed. +Other then +(-[drRzZ] | --di* | --exc* | --inc* | --rec* | --nu*) +, which are NOT supported by $0, OPTIONs are the same as for 'grep'. Report bugs to ." --- a/zgrep.1 2012-09-10 02:51:53.213591617 +0300 +++ b/zgrep.1 2012-09-10 02:51:19.0 +0300 @@ -11,7 +11,11 @@ zgrep \- search possibly compressed file invokes .I grep on compressed or gzipped files. -All options specified are passed directly to +Other then +.BI (-[drRzZ] | --di* | --exc* | --inc* | --rec* | --nu*) +, which are NOT supported by +.I zgrep +, all options specified are passed directly to .IR grep . If no file is specified, then the standard input is decompressed if necessary and fed to grep. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#687123: A somewhat better patch for zgrep.1
--- a/zgrep.1 2012-09-10 03:20:56.541637782 +0300 +++ b/zgrep.1 2012-09-10 03:18:21.0 +0300 @@ -11,7 +11,13 @@ zgrep \- search possibly compressed file invokes .I grep on compressed or gzipped files. -All options specified are passed directly to +These +.I grep +options will cause +.I zgrep +to terminate with an error code: +.BI (-[drRzZ] | --di* | --exc* | --inc* | --rec* | --nu*) . +All other options specified are passed directly to .IR grep . If no file is specified, then the standard input is decompressed if necessary and fed to grep. @@ -23,6 +29,8 @@ If the GREP environment variable is set, uses it as the .I grep program to be invoked. +.SH EXIT CODE +2 - An option that is not supported was specified. .SH AUTHOR Charles Levert (char...@comm.polymtl.ca) .SH "SEE ALSO" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704499: Please include preseed examples, and a list of configurations variables
Source: debian-installer Version: 20130211 Severity: wishlist Am I right that there are no preseed examples in the package? If so, please consider adding one, or more. Perhaps in the doc directory. While at it, perhaps a comprehensive list of all the d-i configuration variables can be added? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704499: Please include preseed examples, and a list of configurations variables
On Tue, Apr 02, 2013 at 02:58:32AM +0200, Samuel Thibault wrote: > Regid Ichira, le Tue 02 Apr 2013 03:37:07 +0300, a ?crit : > > Source: debian-installer > > Version: 20130211 > > Severity: wishlist > > > > Am I right that there are no preseed examples in the package? > > If so, please consider adding one, or more. Perhaps in the doc > > directory. > > While at it, perhaps a comprehensive list of all the d-i > > configuration variables can be added? > > Isn't all this available in the installation manual? > I am trying to install wheezy, using an installation manual for squeeze. Is wheezy installation manual available on the web? Can I build from source only the documentation, including the installation manual? Well, I just tried to look for more information on preseeding in the source package. I didn't build anything myself. Only tried images from the web. Is the list in http://www.debian.org/releases/squeeze/example-preseed.txt exhustive? Most of those variables are not listed explicitly in the installation manual. In addition, example-preseed.txt targets an old release. And it is an external URL. Isn't the code suppose to be the definitive source of information? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#576423: Taking settings from squid-deb-proxy.conf into squid.conf
I have briefly looked into it. I wonder if it is possible to merge squid-deb-proxy.conf with the out of the box squid.conf. Perhaps only by putting the relevant lines into comments in squid.conf. Are the refresh_pattern from below the most importnat? I don't know if other solutions to cache debs might be better in general. https://mvogt.wordpress.com/2013/04/11/squid-deb-proxy-for-debian/ writes that squid-deb-proxy is lately uploaded to debian as well. I think the main thing of squid-deb-proxy is its squid-deb-proxy.conf file. For reference, the file from the Ubuntu's deb is: # WELCOME TO SQUID DEB PROXY # -- # # This config file is a version of a squid proxy file optimized # as a configuration for a caching proxy for Ubuntu systems. # # More information about squid and its configuration can be found here # http://www.squid-cache.org/ and in the FAQ # settings that you may want to customize # --- # this file contains private networks (10.0.0.0/8, 172.16.0.0/12, # 192.168.0.0/16) by default, you can add/remove additional allowed # source networks in it to customize it for your setup acl allowed_networks src "/etc/squid-deb-proxy/autogenerated/allowed-networks-src.acl" # this file contains the *archive.ubuntu.com mirrors by default, # if you use a different mirror, add it there acl to_ubuntu_mirrors dstdomain "/etc/squid-deb-proxy/autogenerated/mirror-dstdomain.acl" # this contains the package blacklist acl blockedpkgs urlpath_regex "/etc/squid-deb-proxy/autogenerated/pkg-blacklist-regexp.acl" # default to a different port than stock squid http_port 8000 # - # settings below probably do not need customization # user visible name visible_hostname squid-deb-proxy # we need a big cache, some debs are huge maximum_object_size 512 MB # use a different dir than stock squid and default to 40G cache_dir aufs /var/cache/squid-deb-proxy 4 16 256 # use different logs cache_access_log /var/log/squid-deb-proxy/access.log cache_log /var/log/squid-deb-proxy/cache.log cache_store_log /var/log/squid-deb-proxy/store.log # tweaks to speed things up cache_mem 200 MB maximum_object_size_in_memory 10240 KB # pid pid_filename /var/run/squid-deb-proxy.pid # refresh pattern for debs and udebs refresh_pattern deb$ 129600 100% 129600 refresh_pattern udeb$ 129600 100% 129600 refresh_pattern tar.gz$ 129600 100% 129600 # always refresh Packages and Release files refresh_pattern \/(Packages|Sources)(|\.bz2|\.gz)$ 0 0% 0 refresh_pattern \/Release(|\.gpg)$ 0 0% 0 # handle meta-release and changelogs.ubuntu.com special refresh_pattern changelogs.ubuntu.com/* 0 1% 1 # only allow connects to ports for http, https acl Safe_ports port 80 acl Safe_ports port 443 563 # only allow ports we trust http_access deny !Safe_ports # do not allow to download from the pkg blacklist http_access deny blockedpkgs # allow access only to official ubuntu mirrors # uncomment the third and fouth line to permit any unlisted domain http_access deny !to_ubuntu_mirrors #http_access allow !to_ubuntu_mirrors # don't cache domains not listed in the mirrors file # uncomment the third and fourth line to cache any unlisted domains cache deny !to_ubuntu_mirrors #cache allow !to_ubuntu_mirrors # allow access from our network and localhost http_access allow allowed_networks # And finally deny all other access to this proxy http_access deny all -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#576423: Doesn't squid caches .debs out of the box?
Package: squid Version: 2.7.STABLE9-4.1 I was looking more carefully in /var/log/squid/store.log. # grep 'debian.*deb' /var/log/squid/store.log shows also SWAPOUT lines for .debs. Doesn't that state the a .deb was cached? The squid.conf is mostly as shipped by the squid .deb. Should this bug be closed? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694954: ps.1: Is t for stopped because it is being traced?
Package: procps Version: 1:3.3.3-2 Severity: normal Tags: patch File: /usr/share/man/man1/ps.1.gz Based on http://www.mail-archive.com/linux-il@cs.huji.ac.il/msg63550.html and http://www.mail-archive.com/linux-il@cs.huji.ac.il/msg63551.html --- ps.1.orig 2012-12-02 18:34:57.598046061 +0200 +++ ps.1.new2012-12-02 18:31:10.0 +0200 @@ -838,8 +838,11 @@ running or runnable (on run queue) S interruptible sleep (waiting for an event to complete) .TP +t +stopped because it is being traced +.TP T -stopped, either by a job control signal or because it is being traced +stopped by a job control signal .TP W paging (not valid since the 2.6.xx kernel) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#711468: modules.5: Have an example
Package: kmod Version: 9-3 Severity: wishlist Tags: patch File: /usr/share/man/man5/modules.5.gz The following patch add an example file: --- modules.5 2013-06-07 05:21:17.849492132 +0300 +++ modules.5.new 2013-06-07 05:20:30.0 +0300 @@ -8,6 +8,17 @@ The file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Lines beginning with a '#' are ignored. +.SH "EXAMPLE" +# /etc/modules: kernel modules to load at boot time. +# +# This file contains the names of kernel modules that +# should be loaded at boot time, one per line. Lines +# beginning with "#" are ignored. + +w83781d + +3c509 irq=15 +nf_nat_ftp .SH "SEE ALSO" .BR depmod (8) .BR modprobe (8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701149: Which initrd.gz version had a size of 28524879 bytes around 11-Feb-2013?
1. http://d-i.pascal.at/ suggest to use append initrd=initrd.gz ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw DEBCONF_PRIORITY=medium (line broken here for readability) Since I have a seperate initrd directive in my syslinux.cfg, I added to the append directive: vga=791 ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw With this addition, I can boot into the installer. 2. I then tried the linux and initrd.gz of 23-Feb-2013 from the netboot section. Both what I believe is the text (newt) version, and the GTK one. The machine reboots itself with nothing seen on the display. This happens with an append line of vga=791 as well as with an append line of vga=791 ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw 3. With the current, 23-Feb-2013, hd-media/gtk vmlinuz and initrd.gz, and an append line of vga=791 ramdisk_size=10240 root=/dev/rd/0 devfs=mount,dall rw I got a kernel panic that looks to me similar to the one in the post that open #701149. Now I wonder where are the kernel and initrd.gz that do work came from? The kernel size is 2503264 bytes. The initrd.gz is 28524879 bytes. I think they boot into a GTK version of the installer. I also think they were put on the archive on 11-Feb-2013. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701149: difficult to find a kernel + initrd to boot the installer
ftp.zcu.cz: /mirrors/linux/debian/dists/wheezy/main/ \ installer-i386/current/images/netboot/gtk/ \ debian-installer/i386/ (line broken by me for readability) has, at this time, a linux kernel of size 2503264 bytes. With an initrd.gz of size 28526283 bytes. That was mirrored there on 12-Feb-2013. Although the kernel from there is the same one as the one that boots into the installer on my machine, the initrd.gz is not. Indeed, the pair from ftp.zcu.cz resulted in a kernel panic when I used it. I would expect it would be much easier for me to boot into the installer. Maybe I am doing something wrong. I am still unsure where did I get in kernel + initrd.gz from that does work. Maybe I took them from some iso image. As far as I can tell so far, there has been a regression in the installer ability to run on my machine. From my point of view, the current version of the kernel + initrd.gz, those that were made close to 23-Feb-2013, are worse then those that were made close to 11-Feb-2013. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699537: Was it supposed to look for the "icmp" extension in the first place?
Package: iptables Version: 1.4.14-3 Severity: normal # iptables -t filter -N icmp /lib/xtables/libipt_icmp.so: no "icmp" extension found for this protocol # iptables -S icmp -N icmp I was trying to create a user defined icmp chain. To filter icmp packets. Is this an innocent warning? Can I go on with my user defined icmp chain with that name? I think there is some sort of name space collision here. Is it documented that an icmp name for a user defined chain is not acceptable? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636029: [PATCH] kbuild: Fix missing '\n' for NEW symbols in yes "" | make oldconfig >conf.new
From: Ben Hutchings
According to Documentation/kbuild/kconfig.txt, the commands:
yes "" | make oldconfig >conf.new
grep "(NEW)" conf.new
should list the new config symbols with their default values.
However, currently there is no line break after each new symbol. When
kconfig is interactive the user will type a new-line at this point,
but when non-interactive kconfig must print it.
Signed-off-by: Ben Hutchings
---
Reference: http://bugs.debian.org/636029
Reported-by: 636029-submit...@bugs.debian.org
[regi...@nt1.in: Adjusted Ben's work to apply cleanly to this tree]
Tested-by: Regid Ichira
Applied and tested to 3.8.0-rc4, on top of commit
5da1f88 - Linus Torvalds, 2013-01-18 : Merge tag 'usb-3.8-rc4' of git:/
---
scripts/kconfig/conf.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/scripts/kconfig/conf.c b/scripts/kconfig/conf.c
index 4da3b4a..e39fcd8 100644
--- a/scripts/kconfig/conf.c
+++ b/scripts/kconfig/conf.c
@@ -36,6 +36,7 @@ enum input_mode {
} input_mode = oldaskconfig;
static int indent = 1;
+static int tty_stdio;
static int valid_stdin = 1;
static int sync_kconfig;
static int conf_cnt;
@@ -108,6 +109,8 @@ static int conf_askvalue(struct symbol *sym, const char
*def)
case oldaskconfig:
fflush(stdout);
xfgets(line, 128, stdin);
+ if (!tty_stdio)
+ printf("\n");
return 1;
default:
break;
@@ -495,6 +498,8 @@ int main(int ac, char **av)
bindtextdomain(PACKAGE, LOCALEDIR);
textdomain(PACKAGE);
+ tty_stdio = isatty(0) && isatty(1) && isatty(2);
+
while ((opt = getopt_long(ac, av, "", long_opts, NULL)) != -1) {
input_mode = (enum input_mode)opt;
switch (opt) {
@@ -621,7 +626,7 @@ int main(int ac, char **av)
return 1;
}
}
- valid_stdin = isatty(0) && isatty(1) && isatty(2);
+ valid_stdin = tty_stdio;
}
switch (input_mode) {
--
1.7.10.4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701053: homepage field, copyright file: states domains which are NXDOMAIN
Package: util-linux Version: 2.20.1-5.3 Severity: normal 1. debian/control has http://userweb.kernel.org/~kzak/util-linux/ in the Homepage field. userweb.kernel.org is NXDOMAIN. According to https://en.wikipedia.org/wiki/util-linux , it should be http://www.kernel.org/pub/linux/utils/util-linux/ . I find https://en.wikipedia.org/wiki/util-linux to be a better URL. 2. $ grep -A1 downloaded /usr/share/doc/util-linux/copyright It was downloaded from: ftp://ftp.us.kernel.org/pub/linux/utils/util-linux-ng/ $ ftp.us.kernel.org is NXDOMAIN. Shouldn't that be ftp://ftp.kernel.org/pub/linux/utils/util-linux/ ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701149: Instalation failed: Probably the HD was not recognised
Package: installation-reports Version: 13-Feb-2013 Severity: installation failed. I have syslinux booting xp and memtest86+ on a laptop. syslinux was installed on xp natively. By that I mean that I downloaded syslinux.exe from syslinux site, and used it to install syslinux on xp's ntfs file system. I then downloaded memtest86+, and added an entry in syslinux.cfg for it. So I can boot MS xp, or memtest86+. I want to install debian on the laptop too. I added a debian-installer entry to the existing syslinux.cfg file. That part of the installation worked. I was successful to boot the installer in this way. But I couldn't get the installer initrd to work. I think it has to do with the Ali M5229 PCI Bus Master IDE controller. At least that is what xp is reporting about the hardware. According to xp, the controller has no IRQ settings. The primary and secondary channels are set in xp to IRQ 14 and 15. According to a Google search, that is a normal arrangment with this controller. I tried 4 sets of kernel and initrd: 1. hd-media 2. cdrom: a gtk, and plain versions. 3. netboot. I think all of them were downloaded from http.us.debian.org/debian/dists/wheezy/main/installer-i386/current/images/ , and the version is of 13-Feb-2013, but I am not sure of that. It could be a later version by a few days at most. 1. hd-media With this pair of kernel and initrd, the machine got rebooted by itself almost as soon as syslinux got the initrd, or is it the kernel, running. By experience with xp I know that the machine reboots itself if it senses that there is a problem to boot the HD. 2. netboot With this pair of kernel and initrd, I got a kernel panic. Before the panic details, I could see that List of all partitions: No file system could be mount root, tried: That is why I think there was a problem to recognise the Ali M5229 controller. The boot messages up to the kernel panic were running too fast to be able to see if the controller was recognised. Perhaps you should allow a CONFIG_BOOT_DELAY, or something similar? Due to the kernel panic, I had to reboot with the appropriate sysrq combination. 3. cdrom The results with a plain cdrom kernel + initrd were similar to that of the netboot kernel + initrd. With the gtk version, I got what seem to be an infinite loop. I couldn't see the details. It does seem that each iteration in the loop ended with an error message about something related to x.org configuration file. Does that make sense? Since there was no kernel panic, I could reboot using the alt+ctrl+delete combination. Two final comments: 1. I think it is a good thing that sysrq is working. I think it is not documented in the installation manual. It should be. It could help non developers too. And also introduce them to a useful feature of the system. For me, I would otherwise need to reboot my laptop the hard way. 2. Pehaps the ability to boot with syslinux should be mentioned in the installation manual? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702091: cron.8: Two words out of context. Are they left over?
Package: cron Version: 3.0pl1-124 Severity: minor Tags: patch File: /usr/share/man/man8/man.8.gz The page has two words out of context. Are they left over? --- cron.8 2013-03-02 18:15:34.559768510 +0200 +++ cron.8.new 2013-03-02 18:13:12.0 +0200 @@ -79,7 +79,6 @@ to run programs under /etc/cron.hourly, Debian, see the note under .B DEBIAN SPECIFIC below. -in order Additionally, in Debian, .I cron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702759: viewdiff: command not found, but mentioned in help
Package: vim Version: 2:7.3.547-7 Severity: normal The viewdiff command is not found, but mentioned in help: $ viewdiff bash: viewdiff: command not found $ $ grep viewdiff /usr/share/vim/vim73/doc/diff.txt You may also use "viewdiff" or "gviewdiff". Vim starts in readonly mode then. $ vimdiff is installed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575660: With last kernels, terminal/console processing getting worth.
Package: linux-source-2.6.32 Version: 2.6.32-9 Severity: normal I am making my own kernels out of Debian's linux-source. I upgraded the source from 32-5 to 32-9. I have added a few more kernel modules with 32-9. I believe the config diff is not relevant for this report. 1) With 32-9, when tty1 shows the login prompt after boot, I can't see the characters that I type. I believe they are not processed as expected. This doesn't happen with 32-5. 2) I am using /etc/console-tools/config to get the terminal into BLANK_DPMS=powerdown. With both 32-5 and 32-9, pressing anything on the keyboard doesn't seem to get the terminal out of BLANK_DPMS=powerdown mode. In the past it did work as expected. I can not tell from which kernel version the problem is apparent. 3) Also with both 32-5 and 32-9, the shutdown command doesn't take the screen out of BLANK_DPMS=powerdown mode. So nothing is displayed on the screen when the system goes down. It was not like that in the past. I can't tell from which kernel version the problem emerged. _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575660: (1) type of keyboard and video card (2) log of kernel messages during boot
> From: b...@decadent.org.uk > > Please send a log of kernel messages during boot. > > Also please specify what type of keyboard and video card you are using. > An old AT (DIN5 connector) white colored keyboard. 01:00.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) kernel: klogd 1.5.0#5, log source = /proc/kmsg started. kernel: Linux version 2.6.32-9.p3.2 (2.6.32) (re...@ichira) (gcc version 4.4.3 20100108 (prerelease) (Debian 4.4.2-9) ) #1 Thu Mar 25 22:43:24 EET 2010 kernel: KERNEL supported cpus: kernel: Intel GenuineIntel kernel: AMD AuthenticAMD kernel: NSC Geode by NSC kernel: Cyrix CyrixInstead kernel: Centaur CentaurHauls kernel: Transmeta GenuineTMx86 kernel: Transmeta TransmetaCPU kernel: UMC UMC UMC UMC kernel: BIOS-provided physical RAM map: kernel: BIOS-e820: - 000a (usable) kernel: BIOS-e820: 000f - 0010 (reserved) kernel: BIOS-e820: 0010 - 17ff (usable) kernel: BIOS-e820: 17ff - 17ff3000 (ACPI NVS) kernel: BIOS-e820: 17ff3000 - 1800 (ACPI data) kernel: BIOS-e820: - 0001 (reserved) kernel: DMI 2.1 present. kernel: last_pfn = 0x17ff0 max_arch_pfn = 0x10 kernel: MTRR default type: uncachable kernel: MTRR fixed ranges enabled: kernel: 0-9 write-back kernel: A-B uncachable kernel: C-C7FFF write-protect kernel: C8000-F7FFF uncachable kernel: F8000-FBFFF write-through kernel: FC000-F uncachable kernel: MTRR variable ranges enabled: kernel: 0 base 0 mask FF000 write-back kernel: 1 base 01000 mask FF800 write-back kernel: 2 disabled kernel: 3 disabled kernel: 4 disabled kernel: 5 disabled kernel: 6 disabled kernel: 7 disabled kernel: PAT not supported by CPU. kernel: initial memory mapped : 0 - 0180 kernel: init_memory_mapping: -17ff kernel: 00 - 40 page 4k kernel: 40 - 0017c0 page 2M kernel: 0017c0 - 0017ff page 4k kernel: kernel direct mapping tables up to 17ff @ 7000-c000 kernel: ACPI: RSDP 000f70b0 00014 (v00 GBT ) kernel: ACPI: RSDT 17ff3000 00028 (v01 GBT AWRDACPI 42302E31 AWRD ) kernel: ACPI: FACP 17ff3040 00074 (v01 GBT AWRDACPI 42302E31 AWRD ) kernel: ACPI: DSDT 17ff30c0 020B5 (v01 GBT AWRDACPI 1000 MSFT 010C) kernel: ACPI: FACS 17ff 00040 kernel: 383MB LOWMEM available. kernel: mapped low ram: 0 - 17ff kernel: low ram: 0 - 17ff kernel: node 0 low ram: - 17ff kernel: node 0 bootmap 1000 - 4000 kernel: (6 early reservations) ==> bootmem [00 - 0017ff] kernel: #0 [00 - 001000] BIOS data page ==> [00 - 001000] kernel: #1 [000100 - 000128acb4] TEXT DATA BSS ==> [000100 - 000128acb4] kernel: #2 [09f000 - 10] BIOS reserved ==> [09f000 - 10] kernel: #3 [000128b000 - 0001291091] BRK ==> [000128b000 - 0001291091] kernel: #4 [007000 - 008000] PGTABLE ==> [007000 - 008000] kernel: #5 [001000 - 004000] BOOTMAP ==> [001000 - 004000] kernel: Zone PFN ranges: kernel: DMA 0x -> 0x1000 kernel: Normal 0x1000 -> 0x00017ff0 kernel: Movable zone start PFN for each node kernel: early_node_map[2] active PFN ranges kernel: 0: 0x -> 0x00a0 kernel: 0: 0x0100 -> 0x00017ff0 kernel: On node 0 totalpages: 98192 kernel: free_area_init_node: node 0, pgdat c12197bc, node_mem_map c1292000 kernel: DMA zone: 32 pages used for memmap kernel: DMA zone: 0 pages reserved kernel: DMA zone: 3968 pages, LIFO batch:0 kernel: Normal zone: 736 pages used for memmap kernel: Normal zone: 93456 pages, LIFO batch:31 kernel: ACPI: PM-Timer IO Port: 0x4008 kernel: Allocating PCI resources starting at 1800 (gap: 1800:e7ff) kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 97424 kernel: Kernel command line: root=/dev/sdb3 ro BOOT_IMAGE=/vmlinuz-2.6.32-9.p3.2 kernel: PID hash table entries: 2048 (order: 1, 8192 bytes) kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) kernel: Enabling fast FPU save and restore... done. kernel: Enabling unmasked SIMD FPU exception support... done. kernel: Initializing CPU#0 kernel: Memory: 386548k/393152k available (1495k kernel code, 6112k reserved, 661k data, 228k init, 0k highmem) kernel: virtual kernel memory layout: kernel: fixmap : 0xfffe5000 - 0xf000 ( 104 kB) kernel: vmalloc : 0xd87f - 0xfffe3000 ( 631 MB) kernel: lowmem : 0xc000 - 0xd7ff ( 383 MB) kernel: .init : 0xc121c000 - 0xc1255000 ( 228 kB) kernel: .data : 0xc1175f04 - 0xc121b308 ( 661 kB) kernel: .text : 0xc100 - 0xc1175f04 (
Bug#575871: /usr/share/doc/bind9/FAQ.gz: s/from a title/from a terminal/
Package: bind9 Version: 1:9.6.1.dfsg.P3-1 Severity: minor Tags: patch --- FAQ 2010-03-30 02:56:43.0 +0300 +++ FAQ.mod 2010-03-30 02:57:16.0 +0300 @@ -287,7 +287,7 @@ First ensure that named is running and no errors are being reported at startup (/var/log/messages or equivalent). Running "named -g " from a title can help at this point. + arguments>" from a terminal can help at this point. Secondly ensure that named is configured to use rndc either by "rndc-confgen -a", rndc-confgen or manually. The Administrators _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575660: #15652 in kernel bug tracker
> From: b...@decadent.org.uk > Let us know the bug number so we can track it. > It is 15652. _ Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. https://signup.live.com/signup.aspx?id=60969 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575918: Do states, in an example section of man{5,8}/rndc.*, the default values for the tokens in rndc.conf.
Package: bind9
Version: 1:9.6.1.dfsg.P3-1
Severity: normal
Does the the source code has default values for the tokens in
rndc.conf? If so, I think those values should be explicitly mentioned,
in an example section, of the rndc.{8,conf.5}. The tokens that don't
have default values should be mentioned, as such, in the example too.
_
Hotmail: Trusted email with powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575660: With last kernels, terminal/console processing getting worse.
I noticed that the i8042 interrupt counter is 1, not 0. As if it got incremented once. I suspect the processing of key presses are some how messed up. Can you point some reasonable points (file name, perhaps a function and line number) in the source to insert a printk, just to see weather each key press produces a message at those points? Must I compile the entire kernel to get those printk into the binary? _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#629864: debian/rules: Please switch back to traditional rules, reverting the switch to cdbs
Source: nut Version: 2.6.0-2 Severity: normal A switch to cdbs was made on 2.6.0-2. cdbs doesn't work as advertised in its documentation. This makes it harder to use the Debian source code, somewhat defeating the spirit of Debian. See my bts report #627968. If I got it right, that is due to a limitation, or implementation, of make. As discussed in the context of an earlier, still open, bug report against cdbs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#627968: Commenting the Package stanza in the control file
I hope cdbs documentation is accurate, or there is an apparent workaround, in other situations too. - Original Message From: Laurent Bigonville To: Regid Ichira Cc: 629864-cl...@bugs.debian.org Sent: Thu, June 9, 2011 11:59:08 AM Subject: Re: Bug#629864: debian/rules: Please switch back to traditional rules, reverting the switch to cdbs If you want to prevent the building of some package, you can comment the Package stanza in the control file. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#627968: Fw: [Build-common-hackers] Bug#627968: Commenting the Package stanza in the control file
Even if there is a proper way to avoid building a package, my understanding of cdbs documentation is that setting DEB_*PACKAGES variables should have a similar effect. It could be that I don't understand cdbs's documentation. If I do understand the documentation correctly, why it didn't work for me? Doesn't the fact that it didn't work for me implies there is a bug? Either a bug in the code, or in the documentation. - Original Message From: Jonas Smedegaard To: Regid Ichira ; 627968-d...@bugs.debian.org Sent: Thu, June 9, 2011 3:51:05 PM Subject: Re: [Build-common-hackers] Bug#627968: Commenting the Package stanza in the control file Hi Regid, On 11-06-09 at 05:29am, Regid Ichira wrote: > I hope cdbs documentation is accurate, or there is an apparent > workaround, in other situations too. As far as understand this bugreport, Laurent Bigonville is correct: the proper way to avoid building a package is to remove it from the control file. That is general to Debian packaging, not specific to CDBS. I hereby close this bugreport as a non-bug. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#627968: [Build-common-hackers] Bug#627968: Commenting the Package stanza in the control file
I actually used the documentation in a pdf format. I can't find the specific file I used before. Now I found http://build-common.alioth.debian.org/cdbs-doc.html#basic-settings. Can't one set DEB_PACKAGES,and all the other variables,the way I tried to? I did notice that, in general, the variables should be set after the rule fragments are included. Even though the patch in 627968 set them before the fragments inclusion, I did try the other order too. - Original Message From: Jonas Smedegaard Perhaps try elaborate more on the documentation you've interpreted this way, so we can figure out what might need improving. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630242: libwrap0 and tcpd have the same, long and short, description.
Package: libwrap0 Version: 7.6.q-19 Severity: normal libwrap0 and tcpd are 2 packages. Both with the same, long and short, description. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630244: /etc/hosts.{allow,deny} created by libwrap0. man pages distributed by tcpd
Package: tcpd
Version: 7.6.q-19
Severity: normal
$ zgrep -A2 7.6.q-17 /usr/share/doc/libwrap0/changelog.Debian.gz
tcp-wrappers (7.6.q-17) unstable; urgency=medium
* Moved the creation of /etc/hosts.{allow,deny} from tcpd to libwrap0.
In view of this, I think that the man pages should also be distributed
with libwrap0.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638021: /etc/init.d/nut-server: The DEFAULT=/etc/default/nut should be deleted
Package: nut-server Version: 2.6.1-2 Severity: minor Tags: patch File: /etc/init.d/nut-server /etc/default/nut is not used anymore. --- a/etc/init.d/nut-server 2011-08-16 17:42:24.0 +0300 +++ b/etc/init.d/nut-server 2011-08-16 18:15:25.0 +0300 @@ -17,7 +17,6 @@ NAME=nut DESC="Network UPS Tools" -DEFAULT=/etc/default/nut CONFIG=/etc/nut/nut.conf . /lib/lsb/init-functions -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#638221: Does drivers/rhino.c has a memory leaks?
Source: nut Version: 2.6.1-2 Severity: normal Tags: patch File: drivers/rhino.c I don't use this driver. I can't see where the allocated memory at line 648 is freed. I also think that the whole time update block is unused. I think there is a similar issue in the drivers/rhino.c:getbaseinfo(). Are the static variables on lines 88-90 useful? --- a/drivers/rhino.c 2011-08-17 22:19:07.0 +0300 +++ b/drivers/rhino.c 2011-08-17 22:30:24.0 +0300 @@ -645,17 +645,6 @@ unsigned char temp[256]; int tam; -int hours, mins; - -/* time update */ -time_t *tmt; -struct tm *now; -tmt = ( time_t * ) malloc( sizeof( time_t ) ); -time( tmt ); -now = localtime( tmt ); -hours = now->tm_hour; -mins = now->tm_min; - temp[0] = 0; /* flush temp buffer */ tam = ser_get_buf_len(upsfd, temp, pacsize, 3, 0); -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636756: A patch for the other instances.
I am not using any of these drivers.
Index: b/drivers/belkinunv.c
===
--- a/drivers/belkinunv.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/belkinunv.c 2011-08-17 00:26:30.0 +0300
@@ -1239,12 +1239,13 @@ int instcmd(const char *cmdname, const c
/* set a variable */
static int setvar(const char *varname, const char *val)
{
- int i, r;
+ int i;
if (!strcasecmp(varname, "input.sensitivity")) {
for (i=0; i= 0)
{
- sdata.shut_pkt.bType = Start[0];
if(Start[0]==SHUT_SYNC)
{
upsdebugx (4, "received SYNC token");
@@ -819,7 +817,6 @@ int shut_packet_recv (u_char *Buf, int d
{
upsdebug_hex(3, "Receive", Start, 2);
Size=Start[1]&0x0F;
- sdata.shut_pkt.bLength = Size;
for(recv=0;recvUPS", Tmp, Len+3) ;
/* flush serial port */
- ret = ser_flush_in(upsfd, "", 0) ; /* empty input buffer */
-
- ret = ser_send_buf(upsfd, Tmp, Len+3) ; /* send data to the UPS */
+ ser_flush_in(upsfd, "", 0) ; /* empty input buffer */
+ ser_send_buf(upsfd, Tmp, Len+3) ; /* send data to the UPS */
}
Index: b/drivers/solis.c
===
--- a/drivers/solis.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/solis.c 2011-08-17 00:23:22.0 +0300
@@ -320,7 +320,6 @@ static void confups( void )
{
int i, chks = 0;
- unsigned char tst;
ConfigPack[0] = 0xCF;
ConfigPack[1] = ihour;
@@ -339,7 +338,10 @@ static void confups( void )
/* MSB zero */
ConfigPack[10] = ConfigPack[10] & (~(0x80));
- tst = ConfigPack[10];
+ /*
+ unsigned char tst;
+ tst = ConfigPack[10];
+*/
for(i=0; i < 11; i++)
chks = chks + ConfigPack[i];
@@ -355,9 +357,9 @@ static void confups( void )
static void prnInfo( void )
{
- int iw, sunday=0, monday=0, tuesday=0, wednesday=0, thursday=0,
friday=0, saturday=0;
+ int sunday=0, monday=0, tuesday=0, wednesday=0, thursday=0, friday=0,
saturday=0;
unsigned char dweek;
- iw = weekn;
+ /* int iw; iw = weekn; */
printf( UPS_DATE, Year, Month, Day );
printf( SYS_DATE, anon, mesn, dian, seman );
Index: b/drivers/libshut.c
===
--- a/drivers/libshut.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/libshut.c 2011-08-17 00:23:22.0 +0300
@@ -678,7 +678,6 @@ int shut_packet_recv(int upsfd, u_char *
u_short Pos=0;
u_char Retry=0;
int recv;
- shut_data_t sdata;
upsdebugx (4, "entering shut_packet_recv (%i)", datalen);
@@ -687,7 +686,6 @@ int shut_packet_recv(int upsfd, u_char *
/* if(serial_read (SHUT_TIMEOUT, &Start[0]) > 0) */
if(ser_get_char(upsfd, &Start[0], SHUT_TIMEOUT/1000, 0) > 0)
{
- sdata.shut_pkt.bType = Start[0];
if(Start[0]==SHUT_SYNC)
{
upsdebugx (4, "received SYNC token");
@@ -702,7 +700,6 @@ int shut_packet_recv(int upsfd, u_char *
{
upsdebug_hex(4, "Receive", Start, 2);
Size=Start[1]&0x0F;
- sdata.shut_pkt.bLength = Size;
for(recv=0;recvtm_hour;
-mins = now->tm_min;
+/* int hours, mins; hours = now->tm_hour; mins = now->tm_min; */
temp[0] = 0; /* flush temp buffer */
tam = ser_get_buf_len(upsfd, temp, pacsize, 3, 0);
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#633971: Patch for most instances
untested code!
Mostly deal with usleep, but there are a few places where sleep is
replaced with nanosleep.
Index: b/clients/upssched.c
===
--- a/clients/upssched.c2011-05-31 13:36:47.0 +0300
+++ b/clients/upssched.c2011-08-17 00:40:17.0 +0300
@@ -652,7 +652,7 @@ static int check_parent(const char *cmd,
unlink(lockfn);
/* give the other one a chance to start it, then try again */
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
upslog_with_errno(LOG_ERR, "Failed to connect to parent and failed to
create parent");
@@ -705,7 +705,7 @@ static void sendcmd(const char *cmd, con
if (pipefd == PARENT_STARTED) {
/* loop back and try to connect now */
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay,
NULL);
continue;
}
Index: b/clients/upsmon.c
===
--- a/clients/upsmon.c 2011-05-31 13:36:47.0 +0300
+++ b/clients/upsmon.c 2011-08-17 00:40:17.0 +0300
@@ -610,7 +610,7 @@ static void slavesync(void)
return;
}
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
}
Index: b/docs/new-drivers.txt
===
--- a/docs/new-drivers.txt 2011-05-31 13:36:47.0 +0300
+++ b/docs/new-drivers.txt 2011-08-17 00:40:17.0 +0300
@@ -632,9 +632,9 @@ depends on how fast your system is.
You should check your driver with `strace` or its equivalent on your
system. If the driver is calling read() multiple times, consider adding
-a call to usleep before going into the ser_read_* call. That will give
-it a chance to accumulate so you get the whole thing with one call to
-read without looping back for more.
+a call to nanosleep before going into the ser_read_* call. That will
+give it a chance to accumulate so you get the whole thing with one call
+to read without looping back for more.
This is not a request to save CPU time, even though it may do that. The
important part here is making the strace/ktrace output easier to read.
Index: b/drivers/safenet.c
===
--- a/drivers/safenet.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/safenet.c 2011-08-17 00:40:17.0 +0300
@@ -299,7 +299,7 @@ void upsdrv_initinfo(void)
dstate_setinfo("driver.version.internal", "%s", DRIVER_VERSION);
- usleep(10);
+ struct timespec delay = {0, 100e6}; nanosleep(&delay, NULL);
/*
* Very crude hardware detection. If an UPS is attached, it will set DSR
Index: b/drivers/powerpanel.c
===
--- a/drivers/powerpanel.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/powerpanel.c 2011-08-17 00:40:17.0 +0300
@@ -165,7 +165,7 @@ void upsdrv_initups(void)
}
ser_set_dtr(upsfd, 1);
- usleep(1);
+ struct timespec delay = {0, 10e6}; nanosleep(&delay, NULL);
if (subdriver[mode]->initups() > 0) {
upslogx(LOG_INFO, "CyberPower UPS with %s protocol on
%s detected", subdriver[mode]->version, device_path);
@@ -173,7 +173,7 @@ void upsdrv_initups(void)
}
ser_set_dtr(upsfd, 0);
- usleep(1);
+ nanosleep(&delay, NULL);
}
fatalx(EXIT_FAILURE, "CyberPower UPS not found on %s", device_path);
Index: b/drivers/bestups.c
===
--- a/drivers/bestups.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/bestups.c 2011-08-17 00:40:17.0 +0300
@@ -252,7 +252,7 @@ static void ups_sync(void)
if ((ret > 0) && (buf[0] == '('))
return;
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
fatalx(EXIT_FAILURE, "Unable to detect a Best/SOLA or Phoenix protocol
UPS");
@@ -333,7 +333,7 @@ void upsdrv_updateinfo(void)
}
/* these things need a long time to respond completely */
- usleep(20);
+ struct timespec delay = {0, 200e6}; nanosleep(&delay, NULL);
ret = ser_get_line(upsfd, buf, sizeof(buf), ENDCHAR, "",
SER_WAIT_SEC, SER_WAIT_USEC);
Index: b/drivers/microdowell.c
===
--- a/drivers/microdowell.c 2011-08-17 00:40:17.0 +0300
+++ b/drivers/microdowell.c 2011-08
Bug#633971: Patch for most instances were sent to the wrong bug #
You are right. I am sorry for the nuisance. Thank you for pointing that out. --- On Wed, 8/17/11, Guillem Jover wrote: > From: Guillem Jover > Subject: Re: Bug#633971: Patch for most instances > To: "Regid Ichira" , 633...@bugs.debian.org > Date: Wednesday, August 17, 2011, 8:12 PM > Hi! > > On Wed, 2011-08-17 at 12:47:56 -0700, Regid Ichira wrote: > > untested code! > > Mostly deal with usleep, but there are a few places > where sleep is > > replaced with nanosleep. > > This already closed bug report, was about bochs, I think > you mixed up > the report number? > > regards, > guillem > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#633791: Patch for most instances
untested code!
Mostly deal with usleep, but there are a few places where sleep is
replaced with nanosleep.
Index: b/clients/upssched.c
===
--- a/clients/upssched.c2011-05-31 13:36:47.0 +0300
+++ b/clients/upssched.c2011-08-17 00:40:17.0 +0300
@@ -652,7 +652,7 @@ static int check_parent(const char *cmd,
unlink(lockfn);
/* give the other one a chance to start it, then try again */
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
upslog_with_errno(LOG_ERR, "Failed to connect to parent and failed to
create parent");
@@ -705,7 +705,7 @@ static void sendcmd(const char *cmd, con
if (pipefd == PARENT_STARTED) {
/* loop back and try to connect now */
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay,
NULL);
continue;
}
Index: b/clients/upsmon.c
===
--- a/clients/upsmon.c 2011-05-31 13:36:47.0 +0300
+++ b/clients/upsmon.c 2011-08-17 00:40:17.0 +0300
@@ -610,7 +610,7 @@ static void slavesync(void)
return;
}
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
}
Index: b/docs/new-drivers.txt
===
--- a/docs/new-drivers.txt 2011-05-31 13:36:47.0 +0300
+++ b/docs/new-drivers.txt 2011-08-17 00:40:17.0 +0300
@@ -632,9 +632,9 @@ depends on how fast your system is.
You should check your driver with `strace` or its equivalent on your
system. If the driver is calling read() multiple times, consider adding
-a call to usleep before going into the ser_read_* call. That will give
-it a chance to accumulate so you get the whole thing with one call to
-read without looping back for more.
+a call to nanosleep before going into the ser_read_* call. That will
+give it a chance to accumulate so you get the whole thing with one call
+to read without looping back for more.
This is not a request to save CPU time, even though it may do that. The
important part here is making the strace/ktrace output easier to read.
Index: b/drivers/safenet.c
===
--- a/drivers/safenet.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/safenet.c 2011-08-17 00:40:17.0 +0300
@@ -299,7 +299,7 @@ void upsdrv_initinfo(void)
dstate_setinfo("driver.version.internal", "%s", DRIVER_VERSION);
- usleep(10);
+ struct timespec delay = {0, 100e6}; nanosleep(&delay, NULL);
/*
* Very crude hardware detection. If an UPS is attached, it will set DSR
Index: b/drivers/powerpanel.c
===
--- a/drivers/powerpanel.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/powerpanel.c 2011-08-17 00:40:17.0 +0300
@@ -165,7 +165,7 @@ void upsdrv_initups(void)
}
ser_set_dtr(upsfd, 1);
- usleep(1);
+ struct timespec delay = {0, 10e6}; nanosleep(&delay, NULL);
if (subdriver[mode]->initups() > 0) {
upslogx(LOG_INFO, "CyberPower UPS with %s protocol on
%s detected", subdriver[mode]->version, device_path);
@@ -173,7 +173,7 @@ void upsdrv_initups(void)
}
ser_set_dtr(upsfd, 0);
- usleep(1);
+ nanosleep(&delay, NULL);
}
fatalx(EXIT_FAILURE, "CyberPower UPS not found on %s", device_path);
Index: b/drivers/bestups.c
===
--- a/drivers/bestups.c 2011-05-31 13:36:49.0 +0300
+++ b/drivers/bestups.c 2011-08-17 00:40:17.0 +0300
@@ -252,7 +252,7 @@ static void ups_sync(void)
if ((ret > 0) && (buf[0] == '('))
return;
- usleep(25);
+ struct timespec delay = {0, 250e6}; nanosleep(&delay, NULL);
}
fatalx(EXIT_FAILURE, "Unable to detect a Best/SOLA or Phoenix protocol
UPS");
@@ -333,7 +333,7 @@ void upsdrv_updateinfo(void)
}
/* these things need a long time to respond completely */
- usleep(20);
+ struct timespec delay = {0, 200e6}; nanosleep(&delay, NULL);
ret = ser_get_line(upsfd, buf, sizeof(buf), ENDCHAR, "",
SER_WAIT_SEC, SER_WAIT_USEC);
Index: b/drivers/microdowell.c
===
--- a/drivers/microdowell.c 2011-08-17 00:40:17.0 +0300
+++ b/drivers/microdowell.c 2011-08
Bug#638557: State that diff --show-c-function does the right thing for other then C.
Source: diffutils
Version: 1:3.0-1
Severity: normal
Tags: patch
Files: src/diff.c man/diff.1
It seems to me that
diff -show-c-function
is showing correct results for many programming languages.
Therefor, I think the following patches should be considered:
--- a/src/diff.c 2010-04-15 22:53:08.0 +0300
+++ b/src/diff.c 2011-08-19 20:42:57.0 +0300
@@ -195,7 +195,7 @@ static struct option const longopts[] =
{"recursive", 0, 0, 'r'},
{"report-identical-files", 0, 0, 's'},
{"sdiff-merge-assist", 0, 0, SDIFF_MERGE_ASSIST_OPTION},
- {"show-c-function", 0, 0, 'p'},
+ {"show-enclosing-function", 0, 0, 'p'},
{"show-function-line", 1, 0, 'F'},
{"side-by-side", 0, 0, 'y'},
{"speed-large-files", 0, 0, 'H'},
@@ -265,7 +265,7 @@ main (int argc, char **argv)
lin ocontext = -1;
bool explicit_context = false;
size_t width = 0;
- bool show_c_function = false;
+ bool show_enclosing_function = false;
char const *from_file = NULL;
char const *to_file = NULL;
uintmax_t numval;
@@ -440,7 +440,7 @@ main (int argc, char **argv)
break;
case 'p':
- show_c_function = true;
+ show_enclosing_function = true;
add_regexp (&function_regexp_list, "^[[:alpha:]$_]");
break;
@@ -623,7 +623,7 @@ main (int argc, char **argv)
if (output_style == OUTPUT_UNSPECIFIED)
{
- if (show_c_function)
+ if (show_enclosing_function)
{
specify_style (OUTPUT_CONTEXT);
if (ocontext < 0)
@@ -860,7 +860,7 @@ static char const * const option_help_ms
N_("-c -C NUM --context[=NUM] Output NUM (default 3) lines of copied co
ntext.\n\
-u -U NUM --unified[=NUM] Output NUM (default 3) lines of unified context
.\n\
--label LABEL Use LABEL instead of file name.\n\
- -p --show-c-function Show which C function each change is in.\n\
+ -p --show-enclosing-function Show which source code function each change
is in.\n\
-F RE --show-function-line=RE Show the most recent line matching RE."),
N_("-q --brief Output only whether files differ."),
N_("-e --ed Output an ed script."),
--- a/man/diff.1 2010-04-15 22:53:19.0 +0300
+++ b/man/diff.1 2011-08-19 20:34:30.0 +0300
@@ -47,8 +47,8 @@ Output NUM (default 3) lines of unified
\fB\-\-label\fR LABEL
Use LABEL instead of file name.
.TP
-\fB\-p\fR \fB\-\-show\-c\-function\fR
-Show which C function each change is in.
+\fB\-p\fR \fB\-\-show\-enclosing\-function\fR
+Show which source code function each change is in.
.TP
\fB\-F\fR RE \fB\-\-show\-function\-line\fR=\fIRE\fR
Show the most recent line matching RE.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#644819: iptables.8: default is icmp-port-unreachable, not port-unreachable
Package: iptables Version: 1.4.12-1 Sevirity: normal Tags: patch File: /usr/share/man/man8/iptables.8.gz It took me a while to figure that the command line should read icmp-port-unreachable, not port-unreachable. I think the current manual page is confusing for someone who does this rarely. Am I the only one who thinks so? For consistency, I suggest: --- iptables.8 2011-10-09 13:24:17.0 +0200 +++ iptables.8.mod 2011-10-09 13:27:29.0 +0200 @@ -2232,7 +2232,7 @@ \fBicmp\-net\-prohibited\fP, \fBicmp\-host\-prohibited\fP or \fBicmp\-admin\-prohibited\fP (*) -which return the appropriate ICMP error message (\fBport\-unreachable\fP is +which return the appropriate ICMP error message (\fBicmp\-port\-unreachable\fP is the default). The option \fBtcp\-reset\fP can be used on rules which only match the TCP protocol: this causes a -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#529664: I think current wording is confusing
I find the current statement confusing for someone who is not verse in Debian. I mean, where are the implied /etc/udev/rules.d/91-permissions.rules and /etc/udev/rules.d/52-nut-usbups.rules ? While I am at it, I am not sure /etc/udev/rules.d/local.rules is not a better choice. --- a/debian/nut-server.README.Debian 2011-10-10 22:15:20.0 +0300 +++ b/debian/nut-server.README.Debian 2011-10-11 20:53:39.0 +0300 @@ -70,15 +70,18 @@ This is not done by default for security reason on Debian, but is applied on Ubuntu. -b) Another solution, for system supporting udev, is to create a file - (for example /etc/udev/rules.d/92-nut-serialups.rules), placed - after 91-permissions.rules and to add something like: +b) Another solution, for system supporting udev, is to create a file, + For example /etc/udev/rules.d/92-nut-serialups.rules. It will + be used after /lib/udev/rules.d/91-permissions.rules, and + contains something like: + KERNEL=="ttyS1", GROUP="nut" - where 'ttyS1' has to be replaced by the exact name of your serial port. + where 'ttyS1' has to be replaced by the exact name of your serial + port. For USB devices, permissions are automatically set by the -52-nut-usbups.rules udev rules file. +/lib/udev/rules.d/52-nut-usbups.rules udev rules file. (4) /etc/nut/upsd.conf (see 'man 5 upsd.conf' for more information) the default /etc/nut/upsd.conf is fine for a "standalone" configuration. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645283: exim4-config_files.5: typo. an, not and
Package: exim4-config Version: 4.76-3 Severity: minor Tags: patch File: /usr/share/man/man5/exim4-config_files.5.gz --- a/exim4-config_files.52011-10-14 02:06:48.0 +0300 +++ b/exim4-config_files.5.mod2011-10-14 02:07:09.0 +0300 @@ -236,7 +236,7 @@ Please note that target.mail.server.example is currently the value that exim can read from reverse DNS: It first follows the host name of -the target system until it finds and IP address, and then looks up the +the target system until it finds an IP address, and then looks up the reverse DNS for that IP address to use the outcome of this query (or the IP address itself should the query fail) as index into /etc/exim4/passwd.client. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636029: Patch works after adjustment of line numbers
Patch is working, after adjusting the lines numbers (for a linux source that
is provided by a Debian source package):
$ patch --dry-run --verbose scripts/kconfig/conf.c ../636029.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|--- a/scripts/kconfig/conf.c
|+++ b/scripts/kconfig/conf.c
--
Patching file scripts/kconfig/conf.c using Plan A...
Hunk #1 succeeded at 38.
Hunk #2 FAILED at 110.
Hunk #3 FAILED at 467.
Hunk #4 FAILED at 573.
3 out of 4 hunks FAILED -- saving rejects to file scripts/kconfig/conf.c.rej
Hmm... Ignoring the trailing garbage.
done
$ patch --dry-run --verbose scripts/kconfig/conf.c ../conf.c.patch
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|--- scripts/kconfig/conf.c 2011-07-31 14:09:19.0 +0300
|+++ ../conf.c 2011-07-31 14:15:39.0 +0300
--
Patching file scripts/kconfig/conf.c using Plan A...
Hunk #1 succeeded at 38.
Hunk #2 succeeded at 110.
Hunk #3 succeeded at 492.
Hunk #4 succeeded at 600.
done
$ cat ../conf.c.patch
--- scripts/kconfig/conf.c 2011-07-31 14:09:19.0 +0300
+++ ../conf.c 2011-07-31 14:15:39.0 +0300
@@ -38,6 +38,7 @@ enum input_mode {
char *defconfig_file;
static int indent = 1;
+static int tty_stdio;
static int valid_stdin = 1;
static int sync_kconfig;
static int conf_cnt;
@@ -109,6 +110,8 @@ static int conf_askvalue(struct symbol *
case oldaskconfig:
fflush(stdout);
xfgets(line, 128, stdin);
+ if (!tty_stdio)
+ printf("\n");
return 1;
default:
break;
@@ -489,6 +492,8 @@ int main(int ac, char **av)
bindtextdomain(PACKAGE, LOCALEDIR);
textdomain(PACKAGE);
+ tty_stdio = isatty(0) && isatty(1) && isatty(2);
+
while ((opt = getopt_long(ac, av, "", long_opts, NULL)) != -1) {
input_mode = (enum input_mode)opt;
switch (opt) {
@@ -595,7 +600,7 @@ int main(int ac, char **av)
return 1;
}
}
- valid_stdin = isatty(0) && isatty(1) && isatty(2);
+ valid_stdin = tty_stdio;
}
switch (input_mode) {
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#636319: A typo in /usr/share/man/man3/calloc.3.gz
package: manpages-dev Version: 3.28-1 Sevirity: normal Tags: patch File: /usr/share/man/man3/calloc.3.gz --- calloc.32011-08-02 11:01:49.0 +0300 +++ calloc.3.mod2011-08-02 11:03:59.0 +0300 @@ -96,7 +96,7 @@ to .I size bytes. -The contents will be unchanged n the range from the start of the region +The contents will be unchanged in the range from the start of the region up to the minimum of the old and new sizes; newly allocated memory will be uninitialized. If -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637030: Does ntptrace look for non existant value in ntpq output?
Source: ntp Version: 4.2.6.p3+dfsg-1 Severity: normal Tags: patch Explanation: I think it is try to catch the rootsisp output from ntpq -n -c rv --- ntp-4.2.6.p3+dfsg/scripts/ntptrace.in 2009-12-09 09:36:35.0 +0200 +++ ntptrace.in 2011-08-08 01:06:06.0 +0300 @@ -34,7 +34,7 @@ # Very old servers report phase and not offset. $offset = $1 if (/(?:offset|phase)=([^\s,]+)/); $rootdelay = $1 if (/rootdelay=([^\s,]+)/); - $rootdispersion = $1 if (/rootdispersion=([^\s,]+)/); + $rootdispersion = $1 if (/rootdisp=([^\s,]+)/); $refid = $1 if (/refid=([^\s,]+)/); } close(PH) || die "$cmd failed"; -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637390: update-rc.d -n fail when run by a regular user, with partialy false message
Package: sysv-rc
Version: 2.88dsf-13.11
Severity: normal
Tags: patch
File: /usr/sbin/update-rc.d
While trying
/usr/sbin/update-rc.d -n
as non root:
$ /usr/sbin/update-rc.d -n lvm2 start 26 S .
update-rc.d: using dependency based boot sequencing
Can't exec "insserv": No such file or directory at /usr/sbin
/update-rc.d line 417.
update-rc.d: error: insserv rejected the script header
I suggest:
--- /usr/sbin/update-rc.d 2011-07-13 22:41:44.0 +0300
+++ update-rc.d 2011-08-10 22:52:34.0 +0300
@@ -414,7 +414,7 @@
cmp_args_with_defaults($scriptname, $action, @args);
if ( -f "/etc/init.d/$scriptname" ) {
-my $rc = system("insserv", @opts, $scriptname) >> 8;
+my $rc = system("/sbin/insserv", @opts, $scriptname) >> 8;
if (0 == $rc && !$notreally) {
save_last_action($scriptname, @orig_argv);
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639906: Does ls --ignore list get confused by explicit file list?
Package: coreutils Version: 8.5-1 Severity: normal Consider a directory with a.txt and b.txt. Why a.txt get shown here $ ls --ignore=a.txt *.txt a.txt b.txt and not $ ls --ignore=a.txt . b.txt here? Can it be that an explicit file list confuses ls? --hide has the same problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641965: postinst: getent > /dev/null
Package: vsftpd
Version: 2.3.4-1
Severity: normal
Tags: patch
File: /var/lib/dpkg/info/vsftpd.postinst
I think getent is too loud.
--- /var/lib/dpkg/info/vsftpd.postinst 2011-09-05 17:08:16.0 +0300
+++ vsftpd.postinst 2011-09-18 11:48:41.0 +0300
@@ -16,10 +16,10 @@
db_stop
- if ! getent passwd "${_USERNAME}"
+ if ! getent passwd "${_USERNAME}" > /dev/null
then
adduser --system --home ${_DIRECTORY} --no-create-home
--quiet --gecos 'ftp daemon' --group ${_USERNAME}
- elif ! getent group "${_USERNAME}"
+ elif ! getent group "${_USERNAME}" > /dev/null
then
addgroup --system --quiet ${_USERNAME}
gpasswd -a ${_USERNAME} ${_USERNAME}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642173: iptables -S --line-numbers does not work
Package: iptables Version: 1.4.12 Severity: normal # iptables -S --line-numbers iptables v1.4.12: Illegal option `-0' with this command Try `iptables -h' or 'iptables --help' for more information. # iptables -L --line-numbers does work. Is: $ zgrep -B4 line-numbers /usr/share/doc/iptables/changelog.gz iptables v1.4.1.1 Changelog = Henrik Nordstrom (1): iptables: fix printing of line numbers with --line-numbers arg related? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642173: An untested patch. Not sure it is in the right direction
Does the following in the right direction?
--- iptables.c 2011-07-22 15:37:34.0 +0300
+++ iptables.c.new 2011-09-21 01:47:25.0 +0300
@@ -163,7 +163,7 @@
/*DEL_CHAIN*/ {'x','x','x','x','x',' ','x','x','x','x','x','x'},
/*SET_POLICY*/{'x','x','x','x','x',' ','x','x','x','x',' ','x'},
/*RENAME*/{'x','x','x','x','x',' ','x','x','x','x','x','x'},
-/*LIST_RULES*/{'x','x','x','x','x',' ','x','x','x','x','x','x'},
+/*LIST_RULES*/{'x','x','x','x','x',' ','x','x','x',' ','x','x'},
/*CHECK*/ {'x',' ',' ',' ',' ',' ','x',' ',' ','x','x',' '},
};
Just a thought. Untested.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
