Processed: Re: Bug#882175: busybox: out-of-bounds read in get_header_ar()

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 882175 
> http://lists.busybox.net/pipermail/busybox/2017-November/085974.html
Bug #882175 [busybox] busybox: out-of-bounds read in get_header_ar()
Set Bug forwarded-to-address to 
'http://lists.busybox.net/pipermail/busybox/2017-November/085974.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
882175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#882177: busybox: unzip creates world-writable directories

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 882177 
> http://lists.busybox.net/pipermail/busybox/2017-November/085975.html
Bug #882177 [busybox] busybox: unzip creates world-writable directories
Set Bug forwarded-to-address to 
'http://lists.busybox.net/pipermail/busybox/2017-November/085975.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
882177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

base-installer_1.179_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Feb 2018 19:11:19 +0100
Source: base-installer
Binary: base-installer bootstrap-base
Architecture: source
Version: 1.179
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 base-installer - base system installation framework (udeb)
 bootstrap-base - Install the base system (udeb)
Changes:
 base-installer (1.179) unstable; urgency=medium
 .
   [ Updated translations ]
   * Tajik (tg.po) by Victor Ibragimov
Checksums-Sha1:
 ebacd5f079cbab8309d7a70f71528d12d8f19d16 1913 base-installer_1.179.dsc
 7a08ce6d816a152c4925ff2f7444b3e62b1156ac 254672 base-installer_1.179.tar.xz
Checksums-Sha256:
 f60e3eff064807bb22dc5adad9f8ad8ba9112e6f3fad757e9b1fcd121b68b34d 1913 
base-installer_1.179.dsc
 e3b75371bbd060fb7af3950da6b5cef127022dfa78c729339d4eb7a43a09db95 254672 
base-installer_1.179.tar.xz
Files:
 0bea1aff618072a82169ca6771ad749c 1913 debian-installer required 
base-installer_1.179.dsc
 07e1da0df2f0da6cd2a0097ce8f4edfd 254672 debian-installer required 
base-installer_1.179.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE1cL5v8oSi7oip3IYhy9wLE1uJagFAlp5QX0ACgkQhy9wLE1u
JagbNg/9G7OXqruQJ7/Ybvca4JHIQXxP7Qn0TeouL6xDcH8XGBmKWvpgqOKWOZV4
NXCy3JSbrCAx6SoKcVDCbE7/xf99Y2NSEkjVIUKFnXX8dUoy36znL6UWup2/pfyc
kuBtIG0L3oZLcUjfZHzyPQ4fO9Zl6N32ivgHupeV0sFSIr43arlorfdM+TdNF6xf
Bb1YfqpAELZ8k8+sTMLoLTkw8XaIEtSi4EeJFn6YC38GrzKn99D/8mgFnDb+Eyk0
aVvmXWKXk230Qs6/WWlbGdh+rEbw0cx/DWoLO268ErtpRbQFQBFnDrwv4rVgllrR
XOviresLi9Bss8MmloAkpwlP8mbS1mZbg1VakxFLexA3kZgtust5PMuhA2Z17wRn
ta30faN5YKFIpg0FkOU4rAOzd2L3CVW7LVa5DiFxrwA/3W3MAmzpQG9BB2QsuPvj
V21uN9jSUBVAnD19/B+FMnDOYpBm1rvFwerA+Qm3IdWggwSvd5hm4GNbwrsmSSyj
ORBf4OwOhDLTzr/lH5i7c+rETdYQoMnDyrvq+lZWoMYa2x/S3DJ5P3e5vASUZyIe
woP0ojPdtlNenly2FaTxxCVITynmFW5qqS7y43rFUrptJ55V1SxKqZe6SgJ4nHbP
k4eA0DMR81Kgl0BXu9keRToPvuBoZj3G2vBnq6RHni7NKkUi/L0=
=KSEe
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of base-installer_1.179_source.changes

[Debian FTP Masters]

base-installer_1.179_source.changes uploaded successfully to localhost
along with the files:
  base-installer_1.179.dsc
  base-installer_1.179.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

Accepted base-installer 1.179 (source) into unstable

[Christian Perrier]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Feb 2018 19:11:19 +0100
Source: base-installer
Binary: base-installer bootstrap-base
Architecture: source
Version: 1.179
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 base-installer - base system installation framework (udeb)
 bootstrap-base - Install the base system (udeb)
Changes:
 base-installer (1.179) unstable; urgency=medium
 .
   [ Updated translations ]
   * Tajik (tg.po) by Victor Ibragimov
Checksums-Sha1:
 ebacd5f079cbab8309d7a70f71528d12d8f19d16 1913 base-installer_1.179.dsc
 7a08ce6d816a152c4925ff2f7444b3e62b1156ac 254672 base-installer_1.179.tar.xz
Checksums-Sha256:
 f60e3eff064807bb22dc5adad9f8ad8ba9112e6f3fad757e9b1fcd121b68b34d 1913 
base-installer_1.179.dsc
 e3b75371bbd060fb7af3950da6b5cef127022dfa78c729339d4eb7a43a09db95 254672 
base-installer_1.179.tar.xz
Files:
 0bea1aff618072a82169ca6771ad749c 1913 debian-installer required 
base-installer_1.179.dsc
 07e1da0df2f0da6cd2a0097ce8f4edfd 254672 debian-installer required 
base-installer_1.179.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE1cL5v8oSi7oip3IYhy9wLE1uJagFAlp5QX0ACgkQhy9wLE1u
JagbNg/9G7OXqruQJ7/Ybvca4JHIQXxP7Qn0TeouL6xDcH8XGBmKWvpgqOKWOZV4
NXCy3JSbrCAx6SoKcVDCbE7/xf99Y2NSEkjVIUKFnXX8dUoy36znL6UWup2/pfyc
kuBtIG0L3oZLcUjfZHzyPQ4fO9Zl6N32ivgHupeV0sFSIr43arlorfdM+TdNF6xf
Bb1YfqpAELZ8k8+sTMLoLTkw8XaIEtSi4EeJFn6YC38GrzKn99D/8mgFnDb+Eyk0
aVvmXWKXk230Qs6/WWlbGdh+rEbw0cx/DWoLO268ErtpRbQFQBFnDrwv4rVgllrR
XOviresLi9Bss8MmloAkpwlP8mbS1mZbg1VakxFLexA3kZgtust5PMuhA2Z17wRn
ta30faN5YKFIpg0FkOU4rAOzd2L3CVW7LVa5DiFxrwA/3W3MAmzpQG9BB2QsuPvj
V21uN9jSUBVAnD19/B+FMnDOYpBm1rvFwerA+Qm3IdWggwSvd5hm4GNbwrsmSSyj
ORBf4OwOhDLTzr/lH5i7c+rETdYQoMnDyrvq+lZWoMYa2x/S3DJ5P3e5vASUZyIe
woP0ojPdtlNenly2FaTxxCVITynmFW5qqS7y43rFUrptJ55V1SxKqZe6SgJ4nHbP
k4eA0DMR81Kgl0BXu9keRToPvuBoZj3G2vBnq6RHni7NKkUi/L0=
=KSEe
-END PGP SIGNATURE-

Bug#839046: debootstrap: enable --merged-usr by default

[Holger Levsen]

On Mon, Feb 05, 2018 at 08:19:33PM +0100, Julien Cristau wrote:
> On Sat, Feb  3, 2018 at 09:16:40 +0100, Marco d'Itri wrote:
> > On Dec 23, md wrote:
> > > On Dec 20, Julien Cristau  wrote:
> > > > > This change was reverted in 1.0.87 as dpkg-shlibdeps didn't cope
> > > > > properly with a merged-usr system. Thus reopening this bug report for
> > > > > that version.
> > > > > 
> > > > > The dpkg-shlibdeps bugs has been fixed [1] in the mean time. So it 
> > > > > would
> > > > > be great if this bug report could be re-considered.
> > > > That'll be after stretch now.
> > > Stretch was been released long ago: please re-enable --merged-usr in 
> > > debootstrap.
> > There has not been any negative feedback, can we move on please?
> Is there buy-in from the dpkg maintainer?

cc:ing them.


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#839046: debootstrap: enable --merged-usr by default

[Julien Cristau]

On Sat, Feb  3, 2018 at 09:16:40 +0100, Marco d'Itri wrote:

> On Dec 23, md wrote:
> 
> > On Dec 20, Julien Cristau  wrote:
> > 
> > > > This change was reverted in 1.0.87 as dpkg-shlibdeps didn't cope
> > > > properly with a merged-usr system. Thus reopening this bug report for
> > > > that version.
> > > > 
> > > > The dpkg-shlibdeps bugs has been fixed [1] in the mean time. So it would
> > > > be great if this bug report could be re-considered.
> > > That'll be after stretch now.
> > Stretch was been released long ago: please re-enable --merged-usr in 
> > debootstrap.
> There has not been any negative feedback, can we move on please?

Is there buy-in from the dpkg maintainer?

Cheers,
Julien

Bug#889673: Successfull: Jessie on Olimex A20-Olinuxino Micro Rev. J

[greg]

Package: installation-reports
Severity: normal



-- Package-specific info:

Boot method: USB Stick
Image version: 
http://ftp.debian.org/debian/dists/stable/main/installer-armhf/current/images/hd-media/hd-media.tar.gz
 
https://cdimage.debian.org/debian-cd/current/armhf/iso-cd/debian-9.3.0-armhf-xfce-CD-1.iso
Date: 2018-01-20

Machine: Olimex A20-Olinuxino Micro Rev. J
Partitions: 2018-01-24

$ df -Tl
Dateisystem   Typ  1K-Blöcke Benutzt Verfügbar Verw% 
Eingehängt auf
udev  devtmpfs492424  492424 0  100% /dev
tmpfs tmpfs   102156   10516 91640   11% /run
/dev/mapper/schubert--vg-root ext4 170783032 3001084 1590369882% /
tmpfs tmpfs   510768   05107680% 
/dev/shm
tmpfs tmpfs 5120   0  51200% 
/run/lock
tmpfs tmpfs   510768   05107680% 
/sys/fs/cgroup
/dev/sda1 ext2240972  147771 80760   65% /boot
tmpfs tmpfs   102152   01021520% 
/run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [E]
Detect CD:  [ ]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[O]

Comments/Problems:

Network did not work because of a kernel issue with hardware Revision J.
see https://www.olimex.com/forum/index.php?topic=5839.msg24167#msg24167


-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="9 (stretch) - installer build 20170615+deb9u2+b1"
X_INSTALLATION_MEDIUM=hd-media

==
Installer hardware-summary:
==
uname -a: Linux schubert 4.9.0-4-armmp #1 SMP Debian 4.9.65-3 (2017-12-03) 
armv7l GNU/Linux
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.9.0-4-armmp ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: MUSB HDRC host driver [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 01
usb-list:Manufacturer: Linux 4.9.0-4-armmp musb-hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 03 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.9.0-4-armmp ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 03 Device 02: USB Receiver [046d:c512]
usb-list:Level 01 Parent 01 Port 00  Class 00(>ifc ) Subclass 00 Protocol 00
usb-list:Manufacturer: Logitech
usb-list:Interface 00: Class 03(HID  ) Subclass 01 Protocol 01 Driver usbhid
usb-list:Interface 01: Class 03(HID  ) Subclass 01 Protocol 02 Driver usbhid
usb-list: 
usb-list: Bus 04 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.9.0-4-armmp ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 05 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 4.9.0-4-armmp ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
lsmod: Module  Size  Used by
lsmod: xts 3443  2
lsmod: gf128mul8527  1 xts
lsmod: dm_crypt   18980  1
lsmod: dm_mod103409  9 dm_crypt
lsmod: md_mod121064  0
lsmod: jfs   174500  0
lsmod: btrfs1146390  0
lsmod: xor 4718  1 btrfs
lsmod: zlib_deflate   20290  1 btrfs
lsmod: raid6_pq   87373  1 btrfs
lsmod: fuse   89119  0
lsmod: smsc3309  1
lsmod: dwmac_sunxi 2431  0
lsmod: stmmac_platform 5044  1 dwmac_sunxi
lsmod: 

Bug#853994: initramfs parameters invalid for IPv6 portal

[Kevin Otte]

I've identified the problem and submitted a patch. Is there something
more I need to do to move this along?

Bug#776554: sulogin says "System Maintenance Mode", doesn't asks for a password if the /etc/passwd (or shadow) entry for the user is empty

[Chris Boot]

Control: tags -1 moreinfo

On 29/01/15 09:06, Peng, Nancy (NSN - CN/Beijing) wrote:
> If the /etc/passwd (or shadow) entry for the user is empty, I invoke
> `sulogin' without arguments from an ordinary shell
> prompt, it prints `System Maintenance Mode', rather than to ask user for
> a password “Give root password for system maintenance
> (or type Control-D for normal startup)”
>  
> Here is a transcript:
>  
>   $ sulogin
>   System Maintenance Mode
>   $ /sbin/hello
>   System Maintenance Mode
>   $
>  
>  
> I suggest that sulogin always ask user for a password even if
> /etc/passwd (or shadow) entry for the user is empty.

Hi Nancy,

Do you mean that when the 'root' user has no password (in the password
or shadow databases) that busybox's sulogin simply goes straight into
maintenance mode rather than giving the user the choice of whether to do or?

sulogin is only enabled in busybox-static. In busybox 1.27.2, the
behaviour is as described above but the message is clearer than in your
initial report:

root@localhost:/# busybox sulogin
sulogin: starting shell for system maintenance
root@localhost:/#

Note that busybox's sulogin doesn't work when run as non-root;
util-linux's sulogin simply refuses to run ("only superuser can run this
program") while busybox's goes through the motions of asking for a
password but this never succeeds.

I suspect that two changes are needed in busybox sulogin:

1. Refuse to run as non-root as util-linux's implementation does. It
only makes sense to run sulogin as root, during boot, to allow the user
to perform maintenance if required.

2. When root has no password, give the user the choice of whether to
perform maintenance or not. Whether this is done by asking for a
password anyway or by some other means is up for debate.

Is this what you meant?

If so I will bring it up for discussion on the busybox-users mailing list.

Best regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#776554: sulogin says "System Maintenance Mode", doesn't asks for a password if the /etc/passwd (or shadow) entry for the user is empty

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #776554 [busybox] sulogin says "System Maintenance Mode", doesn't asks for 
a password if the /etc/passwd (or shadow) entry for the user is empty
Added tag(s) moreinfo.

-- 
776554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#744725: marked as done (busybox: wget is appending instead of replacing with "--header")

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 14:39:34 +
with message-id 
and subject line Re: Bug#744725: busybox: wget is appending instead of 
replacing with "--header"
has caused the Debian Bug report #744725,
regarding busybox: wget is appending instead of replacing with "--header"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
744725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.22.0-5
Severity: normal

The following command fails for me:

---
$ busybox wget --header 'Host: 1.updates.services.ffhl' 
"http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin;
Connecting to luebeck.freifunk.net (141.83.153.180:80)
wget: server returned error: HTTP/1.1 404 Not Found
---

While with GNU Wget 1.15 it works just fine:

---
wget --header 'Host: 1.updates.services.ffhl' 
"http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin;

--2014-04-13 23:58:26--  
http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin
Resolving luebeck.freifunk.net (luebeck.freifunk.net)... 141.83.153.180, 
2001:638:70a:b153:6e62:6dff:fe82:ec06
Connecting to luebeck.freifunk.net (luebeck.freifunk.net)|141.83.153.180|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 3407876 (3.2M) [application/octet-stream]
Saving to: ‘gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin.3’

 0% [  ] 
28,936  10.1KB/s ^C
---

Looking at the HTTP Get message with wireshark it seems that
busybox-wget is keeping the original "Host: luebeck.freifunk.net" and
only appends "Host: 1.updates.services.ffhl". While GNU-wget is
replacing the original http host field which seems to make more sense
from a user's perspective.

Cheers, Linus


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages busybox depends on:
ii  libc6  2.18-4

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

On 13/04/14 23:04, Linus Lüssing wrote:
> The following command fails for me:
> 
> ---
> $ busybox wget --header 'Host: 1.updates.services.ffhl' 
> "http://luebeck.freifunk.net/stable/sysupgrade/gluon-ffhl-0.4-tp-link-tl-mr3420-v1-sysupgrade.bin;
> Connecting to luebeck.freifunk.net (141.83.153.180:80)
> wget: server returned error: HTTP/1.1 404 Not Found
> ---
[snip]
> Looking at the HTTP Get message with wireshark it seems that
> busybox-wget is keeping the original "Host: luebeck.freifunk.net" and
> only appends "Host: 1.updates.services.ffhl". While GNU-wget is
> replacing the original http host field which seems to make more sense
> from a user's perspective.

Hi Linus,

I believe this bug is fixed with upstream commit
d7bfee1edb551d3503c7b616702a73192ba069a9, which is included in the
upstream 1.24.0 release. I cannot reproduce your test case in
1:1.27.2-2, currently in testing and unstable, so I believe that the bug
is indeed resolved in Debian.

Best regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Re: Mass bug filing for the removal of freetype-config and freetype.m4

[Hugh McMaster]

Hi Simon,

On Friday, 2 February 2018 11:14 PM, Simon McVittie wrote:
> On Thu, 01 Feb 2018 at 11:07:42 +, Hugh McMaster wrote:
>> Freetype-config has been considered deprecated for several years [1].
>
> By us, or by upstream?

Both. We considered freetype-config a deprecated legacy interface back in 2011 
[1].
Upstream also recommend using pkg-config over freetype-config in 
freetype-config(1).
In fact, freetype-config has used pkg-config as a wrapper since February 2017 
[2].

> Is there a reason to prefer removing AC_CHECK_FT2, rather than patching
> it to provide enough of its historical functionality for (I'd guess) 90%
> of packages? Something like this should work (untested):
>
> AC_DEFUN([AC_CHECK_FT2],
>  [
>PKG_CHECK_MODULES([FT2], [freetype2 >= $1], [$2], m4_if([$3], [], [:], 
> [$3]))
>  ])
>
> (This doesn't do the sanity-checks that current AC_CHECK_FT2 does,
> and it respects PKG_CONFIG_PATH instead of --with-ft-prefix,
> --with-ft-exec-prefix and FT_CONFIG, but this shouldn't matter most of
> the time; and it seems better if simple packages still compile than if
> they don't.)

codesearch.debian.net shows 26 packages referencing AC_CHECK_FT2.

> Does Freetype's upstream developer consider AC_CHECK_FT2 to be deprecated
> too?
Not as far as I can tell. That said, I'm not against patching the m4 macro to
use PKG_CHECK_MODULES if you believe it will be useful.

> If we ask the upstream developers of various packages to make a change
> because otherwise their package won't compile on Debian, some of them
> will say "well, that's Debian's fault for removing APIs provided by
> Freetype's upstream developer" and do nothing. If we ask them to make a
> change because Freetype upstream has officially deprecated the macro/tool
> they're using, or because otherwise their package (eventually) won't
> compile against newer upstream Freetype releases, it seems more likely
> to happen.
>
> Not carrying long-term patches to the build systems of a large number of
> packages seems a good goal.

Good point. I'll file a bug upstream to ask them to drop freetype-config.
In the meantime, I'll do the mass bug filing for Debian.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642354#10
[2] 
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/builds/unix/freetype-config.in?id=1c513fbb8872bfac5631964963b6a751169a1ce6

Bug#690889: marked as done (udhcpc always returns a domain of "bad" when receiving a valid dhcp ack packet)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 14:40:19 +0100
with message-id <7fcb4974-b15e-e9de-74b6-6b8b83c74...@debian.org>
and subject line Re: Bug#690889: udhcpc always returns a domain of "bad" when 
receiving a valid dhcp ack packet
has caused the Debian Bug report #690889,
regarding udhcpc always returns a domain of "bad" when receiving a valid dhcp 
ack packet
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
690889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udhcpc
Version: :1.20.0-7
Severity: normal
Tags: d-i

udhcpc always returns a domain of "bad" when receiving a valid dhcp ack
from an upstream dhcp server. To reproduce first create a shellscript to
dump all of the variables set by udhcpc uppon successful receipt of a lease:

echo '#!/bin/sh' > /tmp/export.sh
echo 'export' >> /tmp/export.sh
chmod +x /tmp/export.sh

Then call udhcpc with flags set to call the script:

/sbin/udhcpc -s /tmp/export.sh

In my environment with a known good/working isc-dhcpd config, the output is:

 /tmp/udhcpc -s /tmp/sh.sh
udhcpc (v1.20.2) started
export BOOT_IMAGE='debian-installer/amd64/linux.wheezy'
export HOME='/'
export LANG='C'
export LANGUAGE='en'
export MENU='/usr/bin/main-menu'
export PATH='/sbin:/usr/sbin:/bin:/usr/bin'
export PWD='/'
export SHELL='/bin/sh'
export SHLVL='1'
export TERM='vt102'
export TERM_TYPE='serial'
export USER='root'
export _='/tmp/udhcpc'
export initrd='debian-installer/amd64/initrd-wheezy-isc.gz'
export interface='eth0'
Sending discover...
Sending select for 10.30.109.62...
Lease of 10.30.109.62 obtained, lease time 600
export BOOT_IMAGE='debian-installer/amd64/linux.wheezy'
export HOME='/'
export LANG='C'
export LANGUAGE='en'
export MENU='/usr/bin/main-menu'
export PATH='/sbin:/usr/sbin:/bin:/usr/bin'
export PWD='/'
export SHELL='/bin/sh'
export SHLVL='1'
export TERM='vt102'
export TERM_TYPE='serial'
export USER='root'
export _='/tmp/udhcpc'
export boot_file='pxelinux.0'
export broadcast='10.30.109.255'
export dns='10.10.80.10 10.10.80.11'
export domain='bad'
export hostname='systest-2'
export initrd='debian-installer/amd64/initrd-wheezy-isc.gz'
export interface='eth0'
export ip='10.30.109.62'
export lease='600'
export mask='24'
export opt53='05'
export router='10.30.109.254'
export serverid='10.30.10.20'
export siaddr='10.30.10.20'
export subnet='255.255.255.0'

I've tcpdumped both the client and server side of the dhcp exchange and
wireshark decodes the full ack packet as a valid dhcp/bootp ack AND includes
the correct domainname as configured to be sent on the server.

Testing with isc-dhcp-client also yields a successful lease with the correct
domain name set.

The major problem with this bug is that when using debian installer the
network config generated is always invalid. The domain-name cannot be set
in preseed either since the d-i logic in netcfg always give precedence to
values received from dhcp.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

Hi,

The fix for this bug (commit 8efcc9589bd61171ec1fe4f71c33e9df62b6005b,
"networking: allow dot at the end of the domain name in dhcp response")
was included in the Busybox 1.25.0 upstream release, and therefore
included in the Debian upload for 1:1.27.2-1 back in September.

Best regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#538685: marked as done (busybox: dc require whitespace between language elements)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 13:55:07 +0100
with message-id <3bd1a1fb-2970-9bc5-f936-fe494861e...@debian.org>
and subject line Re: Bug#538685: busybox: dc require whitespace between 
language elements (fixed?)
has caused the Debian Bug report #538685,
regarding busybox: dc require whitespace between language elements
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
538685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.13.3-1
Severity: normal


master@capsaicin:~ 0 $ echo '10 2+f'|busybox dc
master@capsaicin:~ 0 $ echo '10 2+f'|dc
12

On the other hand:

master@capsaicin:~ 0 $ echo -e '10\n2\n+\nf'| busybox dc
12

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages busybox depends on:
ii  libc6 2.9-16 GNU C Library: Shared libraries

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

On 04/10/17 21:47, Edward Betts wrote:
> I think this bug is fixed. The example works correctly for me.
> 
> $ echo '10 2+f'|busybox dc
> 12
> $ dpkg -s busybox | grep Version
> Version: 1:1.27.2-1

Hi Lionel, Edward,

The fix for this bug (commit 70e30e8eec7f202cb584449e4c7a9176d57d980d)
was included in the Busybox 1.24.0 upstream release, and therefore
included in the Debian upload for 1:1.27.2-1 back in September.

Best regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#521483: marked as done (busybox: no way to handle a syslogd pidfile)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 13:50:25 +0100
with message-id <87e6a130-7907-08ef-3d40-22d90fc0f...@debian.org>
and subject line Re: Bug#521483: busybox: no way to handle a syslogd pidfile
has caused the Debian Bug report #521483,
regarding busybox: no way to handle a syslogd pidfile
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
521483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.10.2-2
Severity: normal

syslogd has no pidfile option.
also, busybox syslogd doubleforks, so we can't get the correct pid in an 
initscript.
i'd suggest adding a pidfile option (probably useful for other daemon 
functions, too).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: armel (armv4tl)

Kernel: Linux 2.6.28-rc4 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages busybox depends on:
ii  libc6 2.9-6  GNU C Library: Shared libraries

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
On 27/03/09 21:54, x wrote:
> syslogd has no pidfile option.

Hi,

As pointed out earlier in this bug: while busybox syslogd doesn't have
an explicit pidfile option, it does still write a pid file to
/var/run/syslogd.pid. Consequently, I am closing this bug.

Regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#884779: [armv7l] HOWTO get Banana M2 Ultra running

[Hermann Lauer]

Updated list of patches:
r40-sata.patchl
r40-usb.patchl
v2-4-5-ARM-sun8i-r40-enable-USB-host-for-Banana-Pi-M2-Ultra.patch
1-2-clk-sunxi-ng-r40-rewrite-init-code-to-a-platform-driver.patch
2-2-clk-sunxi-ng-r40-export-a-regmap-to-access-the-GMAC-register.patch
r40-gmac.patchl
r40-gmac-dt.patchl

Now the internal gmac runs on linux-4.15 on a gigabit ethernet port.
Thanks to Wens for the working devicetree.

RE: iso-codes -- Re: RE: Tajik translation for debian-installer

[victor.ibragimov]

Dear Tobias,

There is no a .po file yet to send.
Could you please, send me the needed file(s) with country names to translate 
into Tajik.

Thank you so much,
Victor


-Original Message-
From: Dr. Tobias Quathamer [mailto:to...@debian.org] 
Sent: Monday, February 5, 2018 4:27 PM
To: Holger Wansing ; victor.ibragi...@gmail.com
Cc: debian-i...@lists.debian.org; debian-boot@lists.debian.org
Subject: Re: iso-codes -- Re: RE: Tajik translation for debian-installer

Am 05.02.2018 um 08:55 schrieb Holger Wansing:
> Hi Victor,
> 
> Am Montag, 5. Februar 2018 schrieb victor.ibragi...@gmail.com:
>> Also I found that country names are not translated into Tajik. It 
>> looks like translation files for debian-installer do not contain country 
>> names as well.
> 
> Country names are imported from iso-codes package.
> That is to have one central place for this, instead of having every 
> project to maintain its own.
> That is also documented here:
> https://d-i.alioth.debian.org/doc/i18n/ch01s05.html
>  
>> So, please, prompt on how to translate country names into Tajik.
> 
> iso-codes repo is here:
> https://salsa.debian.org/iso-codes-team/iso-codes
> 
> You can translate country names (ISO 3166-1) here:
> https://hosted.weblate.org/engage/iso-codes/?utm_source=widget
> 
> However Tajik is not activated there.
> CC'ing Tobias as it's maintainer:
> 
> Tobias, could you please enable Tajik for ISO3166-1 ?

Sure, I'll be happy to do this! Victor, do you have a .po file which you could 
send to me? Then I'll integrate this into iso-codes so that the country names 
are available in Tajik as well.

If you do not have a .po file yet or if you need further help from me, please 
do not hesitate to contact me.

Regards,
Tobias

Bug#827718: marked as done (init: open /dev/console on GNU/kFreeBSD)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 13:22:52 +0100
with message-id <949032db-80c3-05e1-dca0-8e4dca75d...@debian.org>
and subject line Re: Bug#827718: [bugzi...@busybox.net: [Bug 9031] [PATCH] 
init: open /dev/console on FreeBSD]
has caused the Debian Bug report #827718,
regarding init: open /dev/console on GNU/kFreeBSD
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
827718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1.22.0-19
Tags: patch

FreeBSD kernel doesn't tell PID 1 the pathname of /dev/console through CONSOLE 
environment variable like Linux does. Instead it expects PID 1 to always open 
/dev/console.

This patch is tested on ubuntuBSD but I think it should work on Debian too (I 
haven't tested the whole init yet, but I verified that with my patch it can 
print to stdout).

I've also sent it to BusyBox bugzilla: 
https://bugs.busybox.net/show_bug.cgi?id=9031

-- 
Jon Boden

ubuntuBSD -- The power of FreeBSD kernel with familiarity of Ubuntu OS!

http://www.ubuntubsd.org/ -- https://twitter.com/ubuntuBSD
Index: busybox-1.22.0/init/init.c
===
--- busybox-1.22.0.orig/init/init.c
+++ busybox-1.22.0/init/init.c
@@ -277,11 +277,19 @@ static void console_init(void)
 #ifdef VT_OPENQRY
 	int vtno;
 #endif
-	char *s;
 
+#if defined(__linux__)
+	char *s;
 	s = getenv("CONSOLE");
 	if (!s)
 		s = getenv("console");
+#elif defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
+	const char *s;
+	s = "/dev/console";
+#else
+#error "we don't know how to open the console on this system"
+#endif
+
 	if (s) {
 		int fd = open(s, O_RDWR | O_NONBLOCK | O_NOCTTY);
 		if (fd >= 0) {
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

On 23/08/16 18:43, Jon Boden wrote:
> --- Comment #2 from Denys Vlasenko  ---
> Fixed in git.

Hi Joe,

That commit (d035528261eb9304e9e448c7d8847095b8e8c7c5) was included in
the Busybox 1.26.0 upstream release, and therefore included in the
Debian upload for 1:1.27.2-1 back in September.

I realise that busybox doesn't currently build for kfreebsd-*, but
that's a separate issue (and any help is gratefully received).

Regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#794049: marked as done (udhcpc: option domain with dns labels starting by numbers)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 13:08:27 +0100
with message-id 
and subject line Re: Bug#794049: udhcpc: option domain with dns labels starting 
by numbers
has caused the Debian Bug report #794049,
regarding udhcpc: option domain with dns labels starting by numbers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
794049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.22.0-15
Severity: normal
Tags: d-i patch

Dear Maintainer,

When running udhcpc with "option domain-name" like "0x1.net", the udhcpc
fails to parse it and replace it with "bad". The fix has been applied
upstream:
http://git.busybox.net/busybox/commit/?id=c29021e2a594fb29471c8c7e61ab8f45296622ba

Would it be possible to apply this patch in debian/patches?

Thanks!

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages busybox depends on:
ii  libc6  2.19-18

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

On 30/07/15 06:54, Arthur Gautier wrote:
> Dear Maintainer,
> 
> When running udhcpc with "option domain-name" like "0x1.net", the udhcpc
> fails to parse it and replace it with "bad". The fix has been applied
> upstream:
> http://git.busybox.net/busybox/commit/?id=c29021e2a594fb29471c8c7e61ab8f45296622ba

That commit was included in the Busybox 1.24.0 upstream release, and
therefore included in the Debian upload for 1:1.27.2-1 back in September.

Regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

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

[Ian Campbell]

On Mon, 2018-02-05 at 12:17 +0100, Chris Boot wrote:
> Control: tags -1 -confirmed -patch +wontfix
> Control: retitle -1 busybox-static: always prefers applets when chrooting
> 
> This is desired behaviour for the busybox-static package, and I can't
> think of any documentation changes that could make this clearer.
> 
> For the benefit of others who may stumble across this bug:
> 
> The standard and preferred package for use on a standard Debian system
> is 'busybox'. 'busybox-static' will also work just as well inside the
> initramfs, but is designed to be used as a rescue tool if fundamental
> components of your system, such as your C library, as broken.
> 
> To facilitate this busybox-static always prefers to run its own applets,
> including dpkg, rather than the system-supplied binaries; if your system
> is sufficiently broken that you are running busybox ash, it's a safe
> assumption that your system tools are also hosed.

(I'm not affected by this so just a drive-by comment).

For most applets this seems like sound logic, but for the `chroot`
applet specifically the likely purpose would seem to be to switch into
a new, non-broken, root and execute commands there. Switching into the
chroot and then reexecuting the busybox from the host instead of the
command from within that chroot seems rather counter-intuitive to me.

The patch given only seem to affect the command executed post-chroot
and not any other internal execing (including not the execution of
`chroot` itself).

Ian.

Bug#882258: busybox: CVE-2017-16544: lineedit: do not tab-complete any strings which have control characters

[Salvatore Bonaccorso]

Hi

On Mon, Feb 05, 2018 at 11:52:28AM +0100, Chris Boot wrote:
> Version: 1:1.27.2-2
> 
> Hi Salvatore,
> 
> This was fixed in the last upload of busybox but the bug wasn't closed,
> sorry. I see that the security tracker has been updated already, though.

Thanks for the notice! Yes we did already update the tracker (which
presumalby was after we checked the 1:1.27.2-2 upload).

Regards,
Salvatore

Bug#789475: marked as done (udhcpc: valid rfc1123 hostname recognized as "bad")

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 12:31:22 +0100
with message-id <8f408e70-abeb-ce71-94e2-9e17a1cb2...@debian.org>
and subject line Re: Bug#789475: udhcpc: valid rfc1123 hostname recognized as 
"bad"
has caused the Debian Bug report #789475,
regarding udhcpc: valid rfc1123 hostname recognized as "bad"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
789475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.22.0-9+deb8u1
Severity: normal
Tags: d-i

Dear Maintainer,

The valid hostname "52-54-0-12-34-56" is recognized as bad while it should be 
valid according to rfc1123 (Section 2.1).

-
Capture of the DHCP reply:
be1.lrz.bootps > 192.168.7.107.bootpc: BOOTP/DHCP, Reply, length 300, xid 
0x4cc35164, Flags [none]
  Client-IP 192.168.7.107
  Your-IP 192.168.7.107
  Client-Ethernet-Address 52:54:00:12:34:56 (oui Unknown)
  file "be1"
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: ACK
Server-ID Option 54, length 4: be1.lrz
Lease-Time Option 51, length 4: 600
Subnet-Mask Option 1, length 4: 255.255.255.0
Default-Gateway Option 3, length 4: be2.lrz
Domain-Name-Server Option 6, length 4: be1.lrz
Hostname Option 12, length 16: "52-54-0-12-34-56"
Domain-Name Option 15, length 3: "lrz"


-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages busybox depends on:
ii  libc6  2.19-18

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

On 30/01/17 17:33, Thorsten Glaser wrote:
> Hi,
> 
> I’ve stumbled upon this bug by means of d-i using “bad” as hostname
> right now as well and tracked it down to the offending piece of code
> myself.
> 
> When reading the bugreport messages, I found out that the patch linked –
> https://git.busybox.net/busybox/patch/?id=c29021e2a594fb29471c8c7e61ab8f45296622ba
> – is indeed correct and will fix this issue.

That commit was included in the Busybox 1.24.0 upstream release, and
therefore included in the Debian upload for 1:1.27.2-1 back in September.

Regards,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -confirmed -patch +wontfix
Bug #774227 [busybox-static] busybox-static: execs applets when chrooting
Removed tag(s) confirmed.
Bug #774227 [busybox-static] busybox-static: execs applets when chrooting
Removed tag(s) patch.
Bug #774227 [busybox-static] busybox-static: execs applets when chrooting
Added tag(s) wontfix.
> retitle -1 busybox-static: always prefers applets when chrooting
Bug #774227 [busybox-static] busybox-static: execs applets when chrooting
Changed Bug title to 'busybox-static: always prefers applets when chrooting' 
from 'busybox-static: execs applets when chrooting'.

-- 
774227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Chris Boot]

Control: tags -1 -confirmed -patch +wontfix
Control: retitle -1 busybox-static: always prefers applets when chrooting

This is desired behaviour for the busybox-static package, and I can't
think of any documentation changes that could make this clearer.

For the benefit of others who may stumble across this bug:

The standard and preferred package for use on a standard Debian system
is 'busybox'. 'busybox-static' will also work just as well inside the
initramfs, but is designed to be used as a rescue tool if fundamental
components of your system, such as your C library, as broken.

To facilitate this busybox-static always prefers to run its own applets,
including dpkg, rather than the system-supplied binaries; if your system
is sufficiently broken that you are running busybox ash, it's a safe
assumption that your system tools are also hosed.

Thanks,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature

Re: iso-codes -- Re: RE: Tajik translation for debian-installer

[Dr. Tobias Quathamer]

Am 05.02.2018 um 08:55 schrieb Holger Wansing:
> Hi Victor,
> 
> Am Montag, 5. Februar 2018 schrieb victor.ibragi...@gmail.com:
>> Also I found that country names are not translated into Tajik. It looks like
>> translation files for debian-installer do not contain country names as well.
> 
> Country names are imported from iso-codes package.
> That is to have one central place for this, instead of having
> every project to maintain its own.
> That is also documented here:
> https://d-i.alioth.debian.org/doc/i18n/ch01s05.html
>  
>> So, please, prompt on how to translate country names into Tajik.
> 
> iso-codes repo is here:
> https://salsa.debian.org/iso-codes-team/iso-codes
> 
> You can translate country names (ISO 3166-1) here:
> https://hosted.weblate.org/engage/iso-codes/?utm_source=widget 
> 
> However Tajik is not activated there.
> CC'ing Tobias as it's maintainer:
> 
> Tobias, could you please enable Tajik for ISO3166-1 ?

Sure, I'll be happy to do this! Victor, do you have a .po file which you
could send to me? Then I'll integrate this into iso-codes so that the
country names are available in Tajik as well.

If you do not have a .po file yet or if you need further help from me,
please do not hesitate to contact me.

Regards,
Tobias



signature.asc
Description: OpenPGP digital signature

Bug#756593: marked as done (busybox's switch_root makes read-only NFS root read/write)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 12:00:06 +0100
with message-id <691043a4-52f6-ed27-b53e-2c7d1117b...@debian.org>
and subject line Re: Bug#756593: busybox's switch_root makes read-only NFS root 
read/write
has caused the Debian Bug report #756593,
regarding busybox's switch_root makes read-only NFS root read/write
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
756593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.22.0-6
Severity: important

Dear Maintainer,

we have a PXE environments in our lab, where we boot both physical boxes
and XEN machines via NFS from one centralized Debian SID image. While
the kernel/initramfs mounts the image correctly read only (I set a
breakpoint just before switch_root get invoked) (see [1]), makes
switch_root the NFS root read/write (see [2]).

Alex


[1] 192.168.0.1:/usr/local/muclab/image/debian-sid on /root type nfs
(ro,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,
proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=192.168.0.1)

[2] 192.168.0.1:/usr/local/muclab/image/debian-sid on / type nfs
(rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,nolock,
proto=tcp,port=2049,timeo=7,retrans=3,sec=sys,local_lock=all,addr=192.168.0.1)


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14.0-netem.fas3270-aufs+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages busybox depends on:
ii  libc6  2.19-7

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information



signature.asc
Description: Message signed with OpenPGP using GPGMail
--- End Message ---
--- Begin Message ---
Control: tags -1 +unreproducible -moreinfo

Hi,

Almost four years have gone by since this bug was last discussed and,
given that the root cause was never found, I think it's time this bug
was closed. The bug will of course remain in the BTS, so the useful
debugging information will not be lost.

Thanks,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#882258: marked as done (busybox: CVE-2017-16544: lineedit: do not tab-complete any strings which have control characters)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 11:52:28 +0100
with message-id <2b90d242-8ede-d5dd-fa98-7a9e9aa6d...@debian.org>
and subject line Re: Bug#882258: busybox: CVE-2017-16544: lineedit: do not 
tab-complete any strings which have control characters
has caused the Debian Bug report #882258,
regarding busybox: CVE-2017-16544: lineedit: do not tab-complete any strings 
which have control characters
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
882258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: busybox
Version: 1:1.27.2-1
Severity: grave
Tags: security

Hi,

the following vulnerability was published for busybox. I realize you
know of the issue already but just filling to have a tracking bug as
well in the BTS.

CVE-2017-16544[0]:
| In the add_match function in libbb/lineedit.c in BusyBox through
| 1.27.2, the tab autocomplete feature of the shell, used to get a list
| of filenames in a directory, does not sanitize filenames and results in
| executing any escape sequence in the terminal. This could potentially
| result in code execution, arbitrary file writes, or other attacks.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-16544
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16544
[1] 
https://git.busybox.net/busybox/commit/?id=c3797d40a1c57352192c6106cc0f435e7d9c11e8

Please adjust the affected versions in the BTS as needed, only
unstable checked so far.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-2

Hi Salvatore,

This was fixed in the last upload of busybox but the bug wasn't closed,
sorry. I see that the security tracker has been updated already, though.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

[John Paul Adrian Glaubitz]

On 02/05/2018 11:45 AM, Chris Boot wrote:
> Is this still a problem with current gcc on m68k? I see that gcc points
> at gcc-7 (>= 7.2.0-1~) in sid and, as far as I can tell, it also applies
> to m68k.

I haven't checked. I will verify this tonight. I am currently on the
train back home from FOSDEM and have limited mobile internet only.

> To me this is really a gcc bug, and the fix belongs there. busybox has a
> real interest in remaining small on several architectures, and I really
> don't believe a workaround like this belongs in the busybox package.

I don't disagree. It is a gcc bug, of course, when a package misbehaves
when it's miscompiled. However, fixing such bugs in gcc takes a bit more
time, but they will eventually get fixed.

This is why I asked for the workaround. There is nothing wrong with
carrying a small workaround in the debian/rules file if it helps relieving
issues porters have on some architectures.

There are many packages in Debian that have such workarounds, even for
architectures like armhf, armel, mips and so on, so it's not limited
to m68k.

Packages with such workarounds include: mesa, qtwebkit-opensource-src,
mpfr4 for example. So, yes, I absolutely agree with you that the underlying
issue is a bug in gcc which needs to be fixed. But until that has happened,
it would be very helpful for the m68k porters if the workaround can be
carried in the meantime in the debian/rules file.

My suggestion would be to add a comment with a reference to the gcc
upstream bug report to the workaround so that the busybox maintainers
can easily check whether the workaround is still necessary when they
upload a new version.

I will verify the issue with the latest gcc version tonight. If it still
exists, I will finally open the upstream bug report and add the URL
with the "forwarded" keyword to this bug report. It would then be highly
appreciated if you could add the workaround with the gcc bug report
referenced to the debian/rules file for the time being until the gcc
bug has been fixed.

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Processed: Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #877735 [src:busybox] busybox: m68k build broken due to "-Os" in CFLAGS
Added tag(s) moreinfo.

-- 
877735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS

[Chris Boot]

Control: tags -1 moreinfo

On 06/10/17 01:09, John Paul Adrian Glaubitz wrote:
> On 10/05/2017 11:49 PM, Christoph Biedl wrote:
>> So please take this to gcc first unless you've
>> already done so. And let us know if you get the impression this won't
>> get fixed soon-ish - breaking an architecture still beats packaging
>> principles.
> 
> gcc bugs aren't usually something that get fixed promptly, in particular
> when talking about non-mainstream architectures like m68k.

Hi Adrian,

Is this still a problem with current gcc on m68k? I see that gcc points
at gcc-7 (>= 7.2.0-1~) in sid and, as far as I can tell, it also applies
to m68k.

To me this is really a gcc bug, and the fix belongs there. busybox has a
real interest in remaining small on several architectures, and I really
don't believe a workaround like this belongs in the busybox package.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#854923: marked as done (busybox: "sed -i nonexistent" creates bogus files)

[Debian Bug Tracking System]

Your message dated Mon, 5 Feb 2018 11:35:45 +0100
with message-id 
and subject line Re: Bug#854923: busybox: "sed -i" bug corrected in version 
1.23.0
has caused the Debian Bug report #854923,
regarding busybox: "sed -i nonexistent" creates bogus files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: busybox
Version: 1:1.22.0-19+b1
Severity: important

busybox sed -i -e 's/foo/bar/' foo
--  1 root 2689302520   0 Feb 12 01:13 foo

Impact includes for example breaking upgrading from systemd to sysvinit
after installing via stretch's d-i.



-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.10.0-rc7-debug-ssd-abort+ (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages busybox depends on:
ii  libc6  2.24-9

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:1.27.2-1

1.27.2 was uploaded back in September last year, but it looks like we
missed this bug while preparing the changelog.

I can confirm that I can't reproduce this with 1:1.27.2-2 which is
currently in testing and unstable.

Cheers,
Chris

-- 
Chris Boot
bo...@debian.org



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Re: Bug#888515: debian-installer: UEFI boot menu (grub) misses the help screen

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #888515 [debian-installer] debian-installer: UEFI boot menu (grub) misses 
the help screen
Bug 888515 cloned as bug 889643
> block -1 by -2
Bug #888515 [debian-installer] debian-installer: UEFI boot menu (grub) misses 
the help screen
888515 was not blocked by any bugs.
888515 was not blocking any bugs.
Added blocking bug(s) of 888515: 889643
> retitle -2 Add support for help screen
Bug #889643 [debian-installer] debian-installer: UEFI boot menu (grub) misses 
the help screen
Changed Bug title to 'Add support for help screen' from 'debian-installer: UEFI 
boot menu (grub) misses the help screen'.
> reassign -2 grub
Bug #889643 [debian-installer] Add support for help screen
Bug reassigned from package 'debian-installer' to 'grub'.
No longer marked as found in versions debian-installer/20171204.
Ignoring request to alter fixed versions of bug #889643 to the same values 
previously set
> forwarded -2 http://savannah.gnu.org/bugs/?53065
Bug #889643 [grub] Add support for help screen
Set Bug forwarded-to-address to 'http://savannah.gnu.org/bugs/?53065'.

-- 
888515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888515
889643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#888515: debian-installer: UEFI boot menu (grub) misses the help screen

[Samuel Thibault]

Control: clone -1 -2
Control: block -1 by -2
Control: retitle -2 Add support for help screen
Control: reassign -2 grub
Control: forwarded -2 http://savannah.gnu.org/bugs/?53065

Hello,

I have reported the feature request to http://savannah.gnu.org/bugs/?53065

Samuel

apt-setup_0.139_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 05 Feb 2018 06:48:13 +0100
Source: apt-setup
Binary: apt-setup-udeb apt-mirror-setup apt-cdrom-setup
Architecture: source
Version: 1:0.139
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Christian Perrier 
Description:
 apt-cdrom-setup - set up a CD in sources.list (udeb)
 apt-mirror-setup - set up a mirror in sources.list (udeb)
 apt-setup-udeb - Configure apt (udeb)
Changes:
 apt-setup (1:0.139) unstable; urgency=medium
 .
   [ Updated translations ]
   * Tajik (tg.po) by Victor Ibragimov
Checksums-Sha1:
 c3485824c3344c4b1b869072974deaa647ef2e6c 1823 apt-setup_0.139.dsc
 fca8b795fea5b98c93c218418ecf5cd851703685 251176 apt-setup_0.139.tar.xz
Checksums-Sha256:
 747b5dd41d3fa3c29b0b17277f044959cff1c915c8e47c41c0e77058d3eefa49 1823 
apt-setup_0.139.dsc
 3d94489345459b55eab2c96bd27196ddb67eda5b151aa01e7726f6eab1a122d4 251176 
apt-setup_0.139.tar.xz
Files:
 d812869524ae79dbf596a2c9eb3ad590 1823 debian-installer extra 
apt-setup_0.139.dsc
 44a2a67950fb533199066ce6646fd1e6 251176 debian-installer extra 
apt-setup_0.139.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE1cL5v8oSi7oip3IYhy9wLE1uJagFAlp4CQMACgkQhy9wLE1u
JagVXBAArN/+YnnTo8MjSCQH1ua2aub09j+5Ce6O/CGlTXDLTd7S/V+AYQ0V3x2d
awdaSXDVpDG6VxUYyu0/cz+BWambcp4l8ygm94od9dQDKfG8vqKTconjUDwxDyTU
YXe45QcEpuZ7LubdZCSG+c6ZZShTk+glTnyttN++rZXJCBOtYwIKV2ouxFutUVgM
pUnNfarkUQY3v7Xm4cBiqaloPTWONgvY2hqk04fWtxFhA9DOEp1/iY+GEH2SqYb1
VV6iUiJCGuCeDdO9NR9IzMX156p1R9y65VHGzXjFy0Fy8Y21DXagysEMcD36PGTd
eeEgRlf7tiUxIIGLevLvQSSYuJPZzdrHJZeG7Ellj2v4moDBJ+K/T73r+BMKG9X6
nnmKIR0Ju69ZmQamugG8X1mY3kiIS8qw+5MEix1tpDU1T1D0qmyiEFQ+nNd1Fm8n
koAd2i8M47Aoe8RYy9zRcl1IjSZ5tLrOmAfoIllZmqEmRlexJrw1N0ufglskG5fe
xjxQLBqQ52ZP6btYNUvaTrRGxqmhLSe0fX0Gv1UGa1pesQreRCDUg2NenTcOOUUF
lL2vJ0j0MUz/0DvJ40X5Gq76LlJRRfNW3rRkub0SUKHc+NbyBr/2jNXotkGMCXNC
wdRAzHdU9+kmu7LtJ+/8XaFhksfEFQ6JjLptjnVgm4Xmm5rovr4=
=b3/s
-END PGP SIGNATURE-


Thank you for your contribution to Debian.