Bug#904302: Whether vendor-specific patch series should be permitted in the archive

[Tollef Fog Heen]

]] Stuart Prescott 

> Essentially, this is a request that the TC overrule both Debian
> maintainers *and* derivative maintainers in what they have agreed as a
> workflow that obviously works for them. Today, Debian decides to not
> allow debian/patches/vendor.series, then tomorrow, a derivative
> patches dpkg-source and Debian is asked to decide whether
> debian/patches/vendor-dammit-i-want-these-patches-applied.series is
> allowed in the source package.

I can see where you are coming from, but I disagree with your
conclusions.

Hypothetically, if a downstream distribution implemented support
vendor.series without there being any support in Debian for it, I don't
think we would disallow vendor.series in Debian.  (I think it would be a
bad idea for a downstream to patch such functionality into dpkg, but
there are many bad ideas that should not be forbidden.)

> (Footnote: Sean has referred this under §6.1.3, requesting a decision but 
> since this is overriding a (set of) maintainer(s) that includes those using 
> vendor.series and the dpkg maintainers, I assume §6.1.4 applies.)

I believe his request might also be considered under §6.1.1, since we're
being asked about a policy change.  (After talking to Sean in person, he
said he intended it under §6.1.3, not §6.1.1, though.)

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#904250: RFS - golang-github-ulule-limiter - don't skip all tests

[Alexandre Viau]

On 2018-07-28 05:49 AM, Paride Legovini wrote:
> Alexandre Viau wrote on 28/07/2018:
>> Hello,
>>
>> I have noticed that you skip all tests in golang-github-ulule-limiter.
>>
>> However, there is only two tests that require redis.
>>
>> I think that it would be best to skip only these two tests.
>>
>> You can simply write a patch that adds t.Skip() to these tests.
> Hello Alexandre,
>
> I think I've found a better way to skip that test, without patching.
> Please check my last commits when you have time.

This is clever, good work.

Uploaded :)

-- 
Alexandre Viau
av...@debian.org




signature.asc
Description: OpenPGP digital signature

Bug#615646: [installation-guide] How do I know which CD has the package I need?

[Holger Wansing]

Hi,

Rick Thomas  wrote:
> 
> On Jul 28, 2018, at 10:44 AM, Holger Wansing  wrote:
> 
> > 
> > Robert Cymbala  wrote:
> >> QUESTION:  
> >>   I burned the first fifteen (15) CD's and GNU/Emacs, which I want to 
> >> install, 
> >>   is not on them.  How do I find out which CDs I need to burn? (There are 
> >> 37 
> >>   more in cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/ and I used to 
> >> burn 
> >>   all the CDs for a release but am too lazy to burn all 52 discs this 
> >> time, 
> >>   I only burnt the first 15.)
> > 
> > Time has changed, we don't provide that big sets of CD images anymore. 
> > So the above question is no longer that important.
> > 
> > However, I would like to add something like the following to chapter 4.1
> > (https://d-i.debian.org/manual/en.amd64/ch04s01.html):
> > 
> > 
> > 
> > diff --git a/en/install-methods/official-cdrom.xml 
> > b/en/install-methods/official-cdrom.xml
> > index 512011690..f1f12554d 100644
> > --- a/en/install-methods/official-cdrom.xml
> > +++ b/en/install-methods/official-cdrom.xml
> > @@ -30,6 +30,12 @@ the installation to download the remaining files or 
> > additional CDs.
> > 
> > 
> > 
> > +Also, keep in mind: if the CD(s) you are using doesn't contain some 
> > packages
> > +you need, you can always install that packages afterwards from your running
> > +new Debian system (after the installation has finished).
> > +
> > +
> > +
> > If your machine doesn't support CD booting (only relevant
> > on very old PC systems), but you do have a CD set,
> > you can use an alternative strategy such as
> 
> For some people, getting packages via the Internet after installation is not 
> an 
> option.  For example, air-gapped high-security environments, or folks with 
> very
> slow Internet connections (does anyone remember 9600 baud modems?).
> 
> Can we acknowledge such situations in the proposed changes?  For them, at 
> least,
> the question in the subject line is still relevant (perhaps with “CD” changed
> to “DVD”, giving a nod to changing times).

Ok, I missed that fact. ACK'ed.
So I have added a phrase for the  search
(proposed by Ben in 2015 and this morning by Steve) to the patch:




diff --git a/en/install-methods/official-cdrom.xml 
b/en/install-methods/official-cdrom.xml
index 512011690..858b018fa 100644
--- a/en/install-methods/official-cdrom.xml
+++ b/en/install-methods/official-cdrom.xml
@@ -30,6 +30,14 @@ the installation to download the remaining files or 
additional CDs.
 
 
 
+Also, keep in mind: if the CDs/DVDs you are using don't contain some packages
+you need, you can always install that packages afterwards from your running
+new Debian system (after the installation has finished). If you need to know,
+on which CD/DVD to find a specific package, visit
+https://cdimage-search.debian.org/;>https://cdimage-search.debian.org/.
+
+
+
 If your machine doesn't support CD booting (only relevant
 on very old PC systems), but you do have a CD set,
 you can use an alternative strategy such as


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#904253: RFS: golang-github-lucasb-eyer-go-colorful - please use expat in d/copyright

[Alexandre Viau]

On 2018-07-28 05:38 AM, Paride Legovini wrote:
> Alexandre Viau wrote on 28/07/2018:
>> Hello,
>>
>> d/copyright for golang-github-lucasb-eyer-go-colorful says:
>>
>>> License: MIT
>> However, the short name for this license is "Expat".
> Done. That's what I usually do, not sure why I forgot about it.
> Thanks for pointing it out.

Uploaded!

Thank you for your work.

-- 
Alexandre Viau
av...@debian.org




signature.asc
Description: OpenPGP digital signature

Bug#904877: ITP: trololio -- Trollius and asyncio compatibility library

[Sergio Durigan Junior]

Package: wnpp
Severity: wishlist
Owner: Sergio Durigan Junior 

* Package name: trololio
  Version : 1.0
  Upstream Author : ThinkChaos
* URL : https://github.com/ThinkChaos/Trololio
* License : Expat
  Programming Lang: Python
  Description : trololio -- Trollius and asyncio compatibility library

 Trololio provides a compatibility layer for Trollius and asyncio (aka
 Tulip). It addresses the differences listed in Trollius and Tulip:
 .
  * Allows the use of Trollius' syntax with asyncio.
  * Provides missing objects and aliases for the others.
  * Synchronizes debug environnement variables.

I will maintain this package with the DPMT.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#904876: pycodestyle fails one test case when running with Python 3.7

[Matthias Klose]

Package: src:pycodestyle
Version: 2.3.1-2
Severity: serious
Tags: sid buster
Forwarded: https://github.com/PyCQA/pycodestyle/issues/786

one test case fails when running with Python 3.7:

[...]
test_check_non_existent (testsuite.test_shell.ShellTestCase) ... ok
test_check_simple (testsuite.test_shell.ShellTestCase) ... ok
test_check_stdin (testsuite.test_shell.ShellTestCase) ... ok
test_print_usage (testsuite.test_shell.ShellTestCase) ... ok
test_normalize_paths (testsuite.test_util.UtilTestCase) ... ok

==
FAIL: test_checkers_testsuite (testsuite.test_all.PycodestyleTestCase)
--
Traceback (most recent call last):
  File "/home/packages/tmp/pycodestyle-2.3.1/testsuite/test_all.py", line 39, in
test_checkers_testsuite
msg='%s failure(s)' % report.total_errors)
AssertionError: 15 is not false : 15 failure(s)

--
Ran 30 tests in 0.542s

FAILED (failures=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1:
python3.7 setup.py test
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13

also seen in the new upstream 2.4.0.

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

[Scott Kitterman]

On Sat, 28 Jul 2018 14:16:11 +0100 Chris Lamb  wrote:
> Hi Stuart,
> 
> > In the upload of translate-toolkit 2.3.0-3, I ended up with the following:
> > 
> > Depends: python3, python3-pkg-resources, python3-six, python3-translate, 
> > python3:any, python:any
> > 
> > such that the package depended on both the Python 2 and Python 3 
interpreters.
> 
> Thinking about it, we have:
> 
>   
> https://lintian.debian.org/tags/python-package-depends-on-package-from-other-python-variant.html
> 
> This won't trigger for packages unless they are called /
> ^python([23]?)-/ however. Indeed, this seems to be required so we
> "know" that a package is a "2" or a "3".

You don't need to know.  All you need to know is a package depends on both.  I 
don't think that there is any need to limit it to pyhon{3}-* pacakges.  It's 
likely wrong for any situation.

Scott K

Bug#904875: Attaching the correct screenshot

[Kamaraju Kusumanchi]

The screenshot attached in my original email is not correct. Please find
the correct one attached.

Bug#898085: gnupg: gpg --search-keys and parcimonie don't work: Tor misconfigured/keyserver EPERM

[Cyril Brulebois]

Hi,

And sorry for the lag…

intrigeri  (2018-07-08):
> So indeed, the default GnuPG configuration in Stretch cannot work out
> of the box once "use-tor" is enabled. One needs to:
> 
>  - either specify a keyserver whose hostname won't resolve to IPv6, like:
> 
>  echo 'keyserver hkp://jirk5u4osbsr34t5.onion' \
>   >> ~/.gnupg/dirmngr.conf

That plus killing dirmngr (so that it gets restarted) leads to a
successful key search indeed.

>  - or edit /etc/tor/torrc to enable the "IPv6Traffic" flag for the
>"SocksPort" that's used by dirmngr, i.e. something along the lines
>of:
> 
>  echo 'SocksPort 9050 IPv6Traffic' | sudo tee -a /etc/tor/torrc && \
>  sudo systemctl restart tor@default

Reverting the change above (and restarting dirmngr) and implementing
this instead also leads to a successful search.

> Can you please confirm that one of those fixes the problem you're
> facing?

Both do, thanks!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#904875: vim: incorrect syntax highlighting in bash script

[Kamaraju Kusumanchi]

Package: vim
Version: 2:8.0.0197-4+deb9u1
Severity: normal

Dear Maintainer,

The following shell script is not highlighted correctly.

. % cat foo.sh
#!/usr/bin/bash

UPSTREAM=${1:-'@{u}'}

Steps to reproduce:
* Create the shell script
* close vim (if it was used to create the shell script)
* Open the script using vim
vim foo.sh

As you can see in the attached screenshot, the first and second
left curly braces are blue and yellow while the first and second
right curly braces are blue and magenta.

Expected behavior: first and second right curly braces should be
yellow and blue respectively.

Using vim 8.0, on Debian 9.5 (Stretch).

thanks
raju



-- Package-specific info:

--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.gtk
/usr/bin/vim is /usr/bin/vim.gtk
/usr/bin/gvim is /usr/bin/vim.gtk

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

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

Versions of packages vim depends on:
ii  libacl1  2.2.52-3+b1
ii  libc62.24-11+deb9u3
ii  libgpm2  1.20.4-6.2+b1
ii  libselinux1  2.6-3+b3
ii  libtinfo56.0+20161126-1+deb9u2
ii  vim-common   2:8.0.0197-4+deb9u1
ii  vim-runtime  2:8.0.0197-4+deb9u1

vim recommends no packages.

Versions of packages vim suggests:
ii  exuberant-ctags [ctags]  1:5.9~svn20110310-11
pn  vim-doc  
pn  vim-scripts  


  

Pasteboard  Uploaded Image




http://pasteboard.co/HwyXxZU.png;>


https://cdn.pbrd.co/images/HwyXxZU.png;>




  
  
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-34180422-1']);
_gaq.push(['_trackPageview']);

(function() {
  var ga = document.createElement('script'); ga.type = 
'text/javascript'; ga.async = true;
  ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 
'http://www') + '.google-analytics.com/ga.js';
  var s = document.getElementsByTagName('script')[0]; 
s.parentNode.insertBefore(ga, s);
})();
  


  (adsbygoogle = window.adsbygoogle || []).push({
google_ad_client: "ca-pub-7940233671791385",
enable_page_level_ads: true
  });

  
  

  
  

  

  
  Image not found


  

  
  
   
   (adsbygoogle = window.adsbygoogle || []).push({});
   


  
https://cdn.pbrd.co/images/HwyXxZU.png; 
data-load-src="https://pasteboard.co/images/HwyXxZU.png/load; alt="uploaded 
image" class="image js">
  
   https://cdn.pbrd.co/images/HwyXxZU.png; 
alt="uploaded image" class="image"> 

  
  

  
Views
  
  
Embed URL:
https://cdn.pbrd.co/images/HwyXxZU.png; 
readonly>
  


  Embed URL:
  https://cdn.pbrd.co/images/HwyXxZU.png; 
readonly>

Download image

Report image

Upload 
an image

  Views


 
  

  
  (adsbygoogle = window.adsbygoogle || []).push({});
  

  
  
  
  
  
PasteboardEasy Image Uploads
  
  
  Terms  Policy
  


  window.PB_IMAGE = "HwyXxZU.png";


  

Bug#904874: libopenmpt: Crash with some malformed custom tunings in MPTM files

[James Cowgill]

Source: libopenmpt
Version: 0.2.7025~beta20.1-1
Severity: important
Tags: upstream

A new version of libopempt 0.3.11 was released with a security fix:
https://lib.openmpt.org/libopenmpt/2018/07/28/security-updates-0.3.11-0.2.10635-beta34-0.2.7561-beta20.5-p10-0.2.7386-beta20.3-p13/

From SVN log:
[Fix] Tuning: Fix integer overflow and division by zero in
GetRatio()/GetRatioFine() with out-of-range m_FineStepCount caused by
malformed files (caught with afl-fuzz).

AFAIKT this is denial of service only, so keeping the severity at important.

James



signature.asc
Description: OpenPGP digital signature

Bug#903525: python3-dropbox fails to install with Python 3.7 as supported version

[Matthias Klose]

Control: tags -1 + patch

the byte-compilation succeeds, even if the module name is async.

packaging for 9.0.0 can be found at
https://launchpad.net/ubuntu/+source/python-dropbox/9.0.0-0ubuntu1

Bug#904871: rust-humantime: Incomplete debian/copyright?

[Chris Lamb]

Source: rust-humantime
Version: 1.1.1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Wolfgang Silbermayr , 
ftpmas...@debian.org

Hi,

I just ACCEPTed rust-humantime from NEW but noticed it was missing 
attribution in debian/copyright for at least the portions of the
musl libc that it embeds.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#904873: openjpeg2: CVE-2018-14423

[Salvatore Bonaccorso]

Source: openjpeg2
Version: 2.3.0-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/uclouvain/openjpeg/issues/1123

Hi,

The following vulnerability was published for openjpeg2.

CVE-2018-14423[0]:
| Division-by-zero vulnerabilities in the functions pi_next_pcrl,
| pi_next_cprl, and pi_next_rpcl in lib/openjp3d/pi.c in OpenJPEG through
| 2.3.0 allow remote attackers to cause a denial of service (application
| crash).

Filling the bug to track upstream issue.

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-2018-14423
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14423
[1] https://github.com/uclouvain/openjpeg/issues/1123

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#904872: rust-try-lock: Incomplete debian/copyright?

[Chris Lamb]

Source: rust-try-lock
Version: 0.2.2-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Wolfgang Silbermayr , 
ftpmas...@debian.org

Hi,

I just ACCEPTed rust-try-lock from NEW but noticed it was missing 
attribution in debian/copyright for at least Alex Crichton.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#904870: autopkgtest: calls su with an empty username, thus fails

[Chris Hofstaedtler]

Package: autopkgtest
Version: 5.4.1
Severity: grave
Justification: renders package unusable

Dear autopkgtest Maintainers,

In various situations autopkgtest calls /bin/su with an empty string for
the username. The old su (from login) ignored this, but newer su
versions (from util-linux 2.32-0.2) do not accept this, and abort.
Personally I think autopkgtest got lucky that this worked before, but
this probably was not a valid thing to do.

One of the affected lines:
   https://sources.debian.org/src/autopkgtest/5.4.1/lib/adt_testbed.py/#L1096

Example output from autopkgtest:

   autopkgtest [15:52:36]: test supported-algos: [---
   su: user  does not exist
   autopkgtest [15:52:36]: test supported-algos: ---]
   Unexpected error:
   Traceback (most recent call last):
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 717, in mainloop
   command()
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 646, in command
   r = f(c, ce)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 584, in cmd_copyup
   copyupdown(c, ce, True)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 469, in copyupdown
   copyupdown_internal(ce[0], c[1:], upp)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 494, in 
copyupdown_internal
   copyup_shareddir(sd[0], sd[1], dirsp, downtmp_host)
 File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 408, in 
copyup_shareddir
   shutil.copy(tb, host)
 File "/usr/lib/python3.6/shutil.py", line 241, in copy
   copyfile(src, dst, follow_symlinks=follow_symlinks)
 File "/usr/lib/python3.6/shutil.py", line 120, in copyfile
   with open(src, 'rb') as fsrc:
   FileNotFoundError: [Errno 2] No such file or directory: 
'/tmp/autopkgtest.zwqy11/supported-algos-stdout'
   autopkgtest [15:52:36]: ERROR: testbed failure: cannot send to testbed: 
[Errno 32] Broken pipe
   autopkgtest [15:52:36]: Binaries: resetting testbed apt configuration

Note that tests that say "Restrictions: needs-root" do not appear to hit
those code paths.

I might try to come up with a patch if no one beats me to it.

Chris

Bug#564935: RM: gmod -- RoM; ancient; abandoned upstream;

[Boyuan Yang]

Control: retitle -1 RM: gmod -- RoM; ancient; abandoned upstream;
Control: severity -1 normal

Just reviewed the whole package and I believe this package "gmod" should 
indeed be removed. It's a leftover that has been around for 8 years.

Dear FTP Masters, please remove this package from the archive. Thanks!

--
Regards,
Boyuan Yang

在 2018年4月17日星期二 CST 上午3:09:14，Riku Voipio 写道：
> reassign 564935 ftp.debian.org
> retitle 564935 gmod -- RoM; ancient; abandoned upstream;
> thanks
> 
> On Mon, Apr 16, 2018 at 07:19:36PM +0200, Moritz Muehlenhoff wrote:
> > On Tue, Jan 12, 2010 at 09:08:39PM +, Simon McVittie wrote:
> > > Source: gmod
> > > Severity: wishlist
> > > User: debian...@lists.debian.org
> > > Usertags: proposed-removal
> > > 
> > > gmod seems like a candidate for removal from Debian:
> > > 
> > > * RFA for a long time
> > > * very low popcon (2 votes)
> > > * alternatives that don't require specialized hardware exist (mikmod)
> > > * nothing in Debian depends on it
> > > 
> > > If you want to keep this package around in Debian, please just close
> > > this bug.> 
> > Eight years without anyone voicing a concern seems like an acceptable
> > grace period to finally remove this? :-)
> 
> At this point the package is just dead weight. Please remove from Debian!
> 
> Riku



signature.asc
Description: This is a digitally signed message part.

Bug#904869: dkms: modules fail to build during package installation on armv7l devices

[James Swineson]

Package: dkms
Version: 2.3-3
Severity: important

When I install package wireguard-dkms, it fails to compile the dkms.

I used the following install command:

$ echo "deb http://deb.debian.org/debian/ unstable main" > 
/etc/apt/sources.list.d/unstable.list
$ printf 'Package: *\nPin: release a=unstable\nPin-Priority: 150\n' > 
/etc/apt/preferences.d/limit-unstable
$ apt update
$ apt install linux-headers-next-sunxi wireguard

The relevent dpkg output is:

Loading new wireguard-0.0.20180718-1 DKMS files...  
 
dpkg: warning: version '3.4.113-sun8i 
4.14.18' has bad syntax: invalid character in revision number   
 
Building for 4.14.18-sunxi
Building initial module for 4.14.18-sunxi 
Error! Bad return status for module build on kernel: 4.14.18-sunxi (armv7l) 
 
Consult /var/lib/dkms/wireguard/0.0.20180718-1/build/make.log for more 
information.

The content of the make.log file is:

DKMS make.log for wireguard-0.0.20180718-1 for kernel 4.14.18-sunxi (armv7l)
Sun Jul 29 02:31:42 UTC 2018
make: Entering directory '/usr/src/linux-headers-4.14.18-sunxi'
Makefile:631: arch//Makefile: No such file or directory
make: *** No rule to make target 'arch//Makefile'.  Stop.
make: Leaving directory '/usr/src/linux-headers-4.14.18-sunxi'

However, I can compile and install that dkms module successfully by running 
`dkms build -m wireguard -v 0.0.20180718-1 -k 4.14.18-sunxi`.

Further investigation into the dkms package, I found the following script:

# dkms_common.postinst, line 227
if [ -n "$ARCH" ]; then
if which lsb_release >/dev/null && [ $(lsb_release -s -i) = "Ubuntu" ]; then
case $ARCH in
amd64)
ARCH="x86_64"
;;
lpia|i?86)
ARCH="i686"
;;
esac
fi
echo "Building for architecture $ARCH"
ARCH="-a $ARCH"
fi

which means if $ARCH is empty, it is going to be empty through the whole 
building process, passed into the Makefile, resulting in a build failure. This 
might be the problem I'm experiencing on an armv7l machine. 

I suggest that the $ARCH variable be unset if it exists and is empty in the 
postinst script, so dkms can figure out the arch itself. Also, why dpkg passed 
an empty string to the 4th argument of dkms_common.postinst (the $ARCH variable 
at dkms_common.postinst line 140) might need further investigation as it is 
likely to cause other issues if the installation is an upgrade rather than a 
new installation.

I am using Debian GNU/Linux 9.5 
(Armbian_5.38_Orangepipc_Debian_stretch_next_4.14.14), kernel 4.14.18-sunxi.

Bug#904868: Installation Report (Fail) : Debian 9.5 Install Fail

[Patrick Dunford]

Package: installation-reports

Boot method:  - netinst 
image on a pen drive non-UEFI
Image version:  
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-9.5.0-amd64-netinst.iso
Date:  2018-07-29 15:00 NZST

Machine:  Homebuilt desktop with 
Intel DB75EN mainboard
Processor: Intel Pentium G
Memory: 4 GB
Partitions: 

Filesystem Type 1K-blocksUsed Available Use% Mounted on
udev   devtmpfs   1989056   0   1989056   0% /dev
tmpfs  tmpfs   4001326236393896   2% /run
/dev/sdb1  ext4  23491408 2965860  19309192  14% /
tmpfs  tmpfs  2000652   0   2000652   0% /dev/shm
tmpfs  tmpfs 5120   4  5116   1% /run/lock
tmpfs  tmpfs  2000652   0   2000652   0% /sys/fs/cgroup
/dev/sdb3  ext4  83355912   57396  79021168   1% /tmp
tmpfs  tmpfs   400128   4400124   1% /run/user/110
tmpfs  tmpfs   400128   0400128   0% /run/user/0


 Output of lspci -knn (or lspci -nn):

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor DRAM Controller [8086:0150] (rev 09)
Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor 
DRAM Controller [8086:2041]
Kernel driver in use: ivb_uncore
Kernel modules: ie31200_edac
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset 
Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family USB 
xHCI Host Controller [8086:2041]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C216 
Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Intel Corporation 7 Series/C216 Chipset Family MEI 
Controller [8086:2041]
Kernel driver in use: mei_me
Kernel modules: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network 
Connection [8086:1503] (rev 04)
Subsystem: Intel Corporation 82579V Gigabit Network Connection 
[8086:2041]
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced 
Host Controller [8086:2041]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C216 Chipset Family 
High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Intel Corporation 7 Series/C216 Chipset Family High 
Definition Audio Controller [8086:2041]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C216 Chipset Family 
USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced 
Host Controller [8086:2041]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 
a4)
00:1f.0 ISA bridge [0601]: Intel Corporation B75 Express Chipset LPC Controller 
[8086:1e49] (rev 04)
Subsystem: Intel Corporation B75 Express Chipset LPC Controller 
[8086:2041]
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset 
Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04)
Subsystem: Intel Corporation 7 Series/C210 Series Chipset Family 6-port 
SATA Controller [AHCI mode] [8086:2041]
Kernel driver in use: ahci
Kernel modules: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C216 Chipset Family SMBus 
Controller [8086:1e22] (rev 04)
Subsystem: Intel Corporation 7 Series/C216 Chipset Family SMBus 
Controller [8086:2041]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 
210] [10de:0a65] (rev a2)
Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3530]
Kernel driver in use: nouveau
Kernel modules: nouveau
01:00.1 Audio device [0403]: NVIDIA Corporation High Definition Audio 
Controller [10de:0be3] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd High Definition Audio 
Controller [1458:3530]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

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

Initial boot:   [O]
Detect network card:[O]

Bug#846006: debian-cd: please provide flavor/spin netinst image for Debian Edu

[Steve McIntyre]

Hi Wolfgang,

On Sat, Jul 28, 2018 at 11:17:16PM +0200, Wolfgang Schweer wrote:
>On Sat, Jul 28, 2018 at 03:17:02AM +0100, Steve McIntyre wrote:
>> 
>> ACK. Just added them back now. In discussion with Holger yesterday, we
>> thought it was best to start with a small set and build up to what's
>> needed.
>
>exim4-daemon-heavy is needed as well; reason is: Debian Edu needs this 
>package early to avoid a clash with exim4-daemon-light (iirc installed 
>by default) later on in the installation process. The exim4-daemon-heavy 
>package is expected to be available on the ISO image to make debootstrap 
>happy.
>
>So please consider to adjust 
>https://salsa.debian.org/images-team/debian-cd/blob/master/tasks/buster/debian-edu
>  
>accordingly.
>
>Same might apply to the sudo-ldap package...

Holger has added these now. I'm curious why you thing these packages
in particular need to be on the netinst itself, though - can't you
just grab from the network? The set of debian-edu packages are making
the netinst quite a lot larger than the normal Debian netinst already,
which is surprising!

>Thanks a lot for working on Debian Edu installation media!

No problem, glad to help. :-)

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Welcome my son, welcome to the machine.

Bug#904867: emacs-goodies-el: drop perldoc.el

[David Bremner]

Package: emacs-goodies-el
Version: 39.0
Severity: normal

As far as I can tell, similar functionality is provided by
cperl-perldoc, which is part of (GNU) Emacs.

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs-goodies-el depends on:
ii  bash 4.4.18-3.1
ii  dpkg 1.19.0.5+b1
ii  emacs1:25.2+1-7
ii  emacs-gtk [emacsen]  1:25.2+1-7
ii  emacsen-common   3.0.0
ii  install-info 6.5.0.dfsg.1-4

Versions of packages emacs-goodies-el recommends:
ii  elpa-browse-kill-ring   2.0.0-1
ii  elpa-debian-el  37.0
ii  elpa-diminish   0.45-2
ii  elpa-dpkg-dev-el37.0
ii  elpa-graphviz-dot-mode  0.4+41+gc456a2b-1
ii  elpa-htmlize1.53-1
ii  elpa-markdown-mode  2.3+154-1
ii  perl-doc5.26.2-6
ii  wget1.19.5-1

emacs-goodies-el suggests no packages.

-- no debconf information

Bug#877337: Bug #877367: www.debian.org: Please consider adding redirects for old Policy chapters/appendices

[Sean Whitton]

Hello,

On Thu 05 Jul 2018 at 09:54AM +0100, Sean Whitton wrote:

> Could you switch the web mirrors to use the multipage version, please?

This is now done, thanks to Paul Wise.

> Then I can drop the file from our releases.

This will happen on the next upload.

> If Sphinx upstream improves the singlehtml output sufficiently that we
> decide to include it in our package again, I don't think we'd want to
> change the web mirrors again.  So you can take this change as the final
> change for as long as we use Sphinx, and put in place permanent 301
> redirects.

I am not sure which of these two bugs should remain open and with what
metadata; leaving that to the www-team.  But indeed, permanent redirects
can now be added.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#846006: debian-cd: please provide flavor/spin netinst image for Debian Edu

[Holger Levsen]

On Sat, Jul 28, 2018 at 11:17:16PM +0200, Wolfgang Schweer wrote:
> exim4-daemon-heavy is needed as well; reason is: Debian Edu needs this 
> package early to avoid a clash with exim4-daemon-light (iirc installed 
> by default) later on in the installation process. The exim4-daemon-heavy 
> package is expected to be available on the ISO image to make debootstrap 
> happy.
> 
> So please consider to adjust 
> https://salsa.debian.org/images-team/debian-cd/blob/master/tasks/buster/debian-edu
>   
> accordingly.
> 
> Same might apply to the sudo-ldap package...
 
I don't really get why these are downloaded via the net but i've added
them now to tasks/buster/debian-edu...

> Thanks a lot for working on Debian Edu installation media!

thank you too for testing and debugging! :)


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#904866: emacs-goodies-el: drop browse-huge-tar, clipper, coffee, ctypes, df, edit-env, egocentric, floatbg, joc-toggle-buffer-el, joc-toggle-case, keywiz, lcomp, map-lines, marker-

[David Bremner]

Package: emacs-goodies-el
Version: 39.0
Severity: normal

If someone wants to be upstream for one of these packages, feel free
to do so and file an RFP when ready, cc'ing
debian-emac...@lists.debian.org.

The following no longer seem maintained outside of
emacs-goodies-el. 

- [ ] browse-huge-tar.el
- [ ] clipper.el
- [ ] coffee.el
- [ ] edit-env
- [ ] egocentric
- [ ] floatbg
- [ ] joc-toggle-buffer
- [ ] joc-toggle-case
- [ ] keywiz (dead link on emacswiki)
- [ ] map-lines
- [ ] marker-visit
- [ ] pack-windows
- [ ] setnu
- [ ] slang-mode
- [ ] tlc
- [ ] todoo

the following are only present in emacswiki:

- [ ] ctypes.el (present on emacswiki)
- [ ] df (present on emacswiki)
- [ ] lcomp (present on emacswiki)

The following is now builtin to emacs

- [ ] underline

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs-goodies-el depends on:
ii  bash 4.4.18-3.1
ii  dpkg 1.19.0.5+b1
ii  emacs1:25.2+1-7
ii  emacs-gtk [emacsen]  1:25.2+1-7
ii  emacsen-common   3.0.0
ii  install-info 6.5.0.dfsg.1-4

Versions of packages emacs-goodies-el recommends:
ii  elpa-browse-kill-ring   2.0.0-1
ii  elpa-debian-el  37.0
ii  elpa-diminish   0.45-2
ii  elpa-dpkg-dev-el37.0
ii  elpa-graphviz-dot-mode  0.4+41+gc456a2b-1
ii  elpa-htmlize1.53-1
ii  elpa-markdown-mode  2.3+154-1
ii  perl-doc5.26.2-6
ii  wget1.19.5-1

emacs-goodies-el suggests no packages.

-- no debconf information

Bug#904859: dgit: should warn when $buildproductsdir is set but using a command that ignores it

[Sean Whitton]

Hello,

On Sun 29 Jul 2018 at 03:30AM +0100, Ian Jackson wrote:

> Sean Whitton writes ("Bug#904859: dgit: should warn when $buildproductsdir is 
> set but using a command that ignores it"):
>> Package: dgit
>> Version: 6.1
>>
>> In particular, `dgit build`.
>>
>> We discussed this but I don't think we ever implemented it.
>
> Right.  Is it just `build' ?

gbp-build too.  I think dgit build-source will respect it.  I think
that's it, but ICBW!

> I guess we should add the bpd thing to
> at least some of the dsc import test cases.

Hmm, I didn't think they put anything in ..

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904865: RM: promoe -- RoQA; Orphaned; Upstream development stalled; Affected by Qt4 Removal

[Boyuan Yang]

Package: ftp.debian.org
Severity: normal
X-Debbugs-CC: 761...@bugs.debian.org

Dear FTP Masters,

Please remove package promoe from Debian Archive.

This packge is currently:

* Orphaned, last packaging activity in 2011
* Upstream development stalled (only one commit since 2013)
* Affected by Qt4 Removal (https://wiki.debian.org/Qt4Removal), no
sign of porting away from Qt4
* Popcon declining
* No reverse dependencies

As a result, I suggest we remove package promoe from the archive.

--
Regards,
Boyuan Yang

Bug#871835: speed up for debootstrap

[Thomas Lange]

I repeated my tests with debootstrap 1.0.106 on buster and everything
went OK. The directory that is generated using the original functions
file and the patched one are the same. Here are the debootstrap calls
I've tested so far:

debootstrap stretch
debootstrap --variant=minbase stretch
debootstrap --variant=buildd stretch
debootstrap --foreign stretch
debootstrap --arch i386 --variant=buildd stretch
debootstrap --arch i386 stretch
debootstrap --include=top,git,tig stretch
debootstrap --exclude=dmidecode,tasksel,ncurses-bin stretch

debootstrap buster
debootstrap --variant=minbase buster
debootstrap --variant=buildd buster
debootstrap --foreign buster
debootstrap --arch i386 --variant=buildd buster
debootstrap --arch i386 buster
debootstrap --include=top,git,tig buster
debootstrap --exclude=dmidecode,tasksel,ncurses-bin buster


If you have more things to test, just let me know.

-- 
regards Thomas

Bug#799355: emacs-goodies-el: apache-mode has incorrect highlighting

[Nicholas D Steeves]

Control: reassign -1 src:apache-mode-el
Control: tags -1 moreinfo

Dear Teddy,

On Fri, Sep 18, 2015 at 10:51:10AM +0200, Teddy Hogeborn wrote:
> Package: emacs-goodies-el
> Version: 35.12
> Severity: minor
> Tags: upstream
> 
> The apache-mode.el has incorrect highlighting; it highlights the word
> "temporary" when in fact the correct syntax for Apache is "temp".
> (See line 563 in apache-mode.el.)

Apache Mode is no longer part of emacs-goodies-el.  Would you please
test if elpa-apache-mode (2.1+4.g97bf66c-2) continues to exhibit this
bug?  elpa-apache-mode (2.1+4.g97bf66c-2)

Thanks,
Nicholas


signature.asc
Description: PGP signature

Bug#904859: dgit: should warn when $buildproductsdir is set but using a command that ignores it

[Ian Jackson]

Sean Whitton writes ("Bug#904859: dgit: should warn when $buildproductsdir is 
set but using a command that ignores it"):
> Package: dgit
> Version: 6.1
> 
> In particular, `dgit build`.
> 
> We discussed this but I don't think we ever implemented it.

Right.  Is it just `build' ?  I guess we should add the bpd thing to
at least some of the dsc import test cases.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#904864: pdftk-java: not (or no longer) licensed under MPL-1.1

[Ansgar Burchardt]

Package: pdftk-java
Version: 0.0.0+20180620.1-1

+---
| Files: java/pdftk/com/*
|...
| License: LGPL-2+ or MPL-1.1
+---[ debian/copyright ]

But there is no mention of MPL-1.1 in the source files.  There is
however a script to remove the MPL-1.1 dual-license (as allowed):
java/pdftk/com/itext_replace_mpl_text_with_lgpl.sh

The reason for this seems to be a misunderstanding (that GPL/MPL might
be incompatible is irrelevant if the file is dual-licensed), but it
happened.

Ansgar

Bug#904862: dgit: should pass --no-source-only-changes to pbuilder

[Sean Whitton]

Rationale: if we don't pass this, pbuilder might overwrite the
_source.changes produced by dgit.  The new _source.changes will probably
work for an upload, but won't respect the -v option passed to
dgit or calculated by dgit.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#615646: [installation-guide] How do I know which CD has the package I need?

[Steve McIntyre]

On Sat, Jul 28, 2018 at 07:44:26PM +0200, Holger Wansing wrote:
>
>Robert Cymbala  wrote:
>> QUESTION:  
>>I burned the first fifteen (15) CD's and GNU/Emacs, which I want to 
>> install, 
>>is not on them.  How do I find out which CDs I need to burn? (There are 
>> 37 
>>more in cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/ and I used to 
>> burn 
>>all the CDs for a release but am too lazy to burn all 52 discs this time, 
>>I only burnt the first 15.)
>
>Time has changed, we don't provide that big sets of CD images anymore. 
>So the above question is no longer that important.

Oh, wow. I've managed to miss that bug. There has been a service to
help with this for ages:

https://cdimage-search.debian.org/

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I've only once written 'SQL is my bitch' in a comment. But that code 
 is in use on a military site..." -- Simon Booth

Bug#904863: emacs-goodies-el: drop tc.el

[David Bremner]

Package: emacs-goodies-el
Version: 39.0
Severity: normal

trivial-cite is no longer available even from emacswiki. If someone
wants to take over as upstream we can re-introduce it.

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages emacs-goodies-el depends on:
ii  bash 4.4.18-3.1
ii  dpkg 1.19.0.5+b1
ii  emacs1:25.2+1-7
ii  emacs-gtk [emacsen]  1:25.2+1-7
ii  emacsen-common   3.0.0
ii  install-info 6.5.0.dfsg.1-4

Versions of packages emacs-goodies-el recommends:
ii  elpa-browse-kill-ring   2.0.0-1
ii  elpa-debian-el  37.0
ii  elpa-diminish   0.45-2
ii  elpa-dpkg-dev-el37.0
ii  elpa-graphviz-dot-mode  0.4+41+gc456a2b-1
ii  elpa-htmlize1.53-1
ii  elpa-markdown-mode  2.3+154-1
ii  perl-doc5.26.2-6
ii  wget1.19.5-1

emacs-goodies-el suggests no packages.

-- no debconf information

Bug#904861: Acknowledgement (RFP: elpa-tc -- Japanese input method with T-code on Emacs)

[David Bremner]

Nick Steeves pointed out to me that tc.el in emacs-goodies-el is
trivial-cite. So no urgency to package this. Feel free to just close it
if you think there are better options already for Emacs.

Bug#904862: dgit: should pass --no-source-only-changes to pbuilder

[Sean Whitton]

Package: dgit
Version: 6.1
Control: block -1 by 904716

Hello,

I think this is likely to be implemented in pbuilder so here is a bug so
we remember to patch dgit to use the new option.

We'd also want to remove the warning about SOURCE_ONLY_CHANGES=yes from
dgit(1).

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904861: RFP: elpa-tc -- Japanese input method with T-code on Emacs

[David Bremner]

Package: wnpp
Severity: wishlist

User: debian-emac...@lists.debian.org
Usertags: elpafy

* Package name: elpa-tc
  Version : 2.3.1
  Upstream Author : Lars R. Clausen 
* URL : https://github.com/kanchoku/tc
* License : GPL2+
  Programming Lang: emacs-lisp
  Description : Japanese input method with T-code on Emacs

This package is actively maintained, and seems to have users on
melpa. It will be removed from emacs-goodies-el soon as part of our
unbundling effort. I don't feel qualified to maintain it because of
lack of Japanese language skill.  I'd be happy to help with using
dh-elpa to package, if needed.

Bug#904834: thunderbird: Thunderbird doesn't opens links on emails, but raises the cpu load and doesn't stops running directly after closing

[Carsten Schoenert]

Hi,

On Sat, Jul 28, 2018 at 06:58:28PM +0200, xiscu wrote:
> Dear Maintainer,
> try to reproduce by clicking on a know link on an email message,
> for me it doesn't opens the browser not it opens a new tab if
> the browser is active. Then the cpu load raises up and if one
> closes thunderbird then it keeps running on the background for
> a while (kill -9 needed).

do you have installed any extension which could have some side effect?

Do you have tried to start thundrbird in safe mode?

Have you had a look at #898926 [1], maybe the issue is partially the same.

And lastly, what is happen if you create a new user profile?

[1] https://bugs.debian.org/898926

Regards
Carsten

Bug#904860: speech-dispatcher: Fails to install on non-linux systems due to missing /lib/systemd/system/speech-dispatcherd.service: /usr/bin/deb-systemd-helper: error: unable to read speech-dispatcher

[Axel Beckert]

Source: speech-dispatcher
Severity: important
Version: 0.8.8-5
User: debian-...@lists.debian.org
Usertags: kfreebsd

If I try to install (or upgrade) speech-dispatcher on kfreebsd-i386, it
fails to configure as follows:

Setting up speech-dispatcher (0.8.8-5) ...
insserv: warning: current start runlevel(s) (3 4 5) of script 
`speech-dispatcher' overrides LSB defaults (2 3 4 5).
/usr/bin/deb-systemd-helper: error: unable to read speech-dispatcherd.service
dpkg: error processing package speech-dispatcher (--configure):
 installed speech-dispatcher package post-installation script subprocess 
returned error exit status 1

This is very likely caused by the "[linux-any]" restriction for
lib/systemd/system/speech-dispatcherd.service in
debian/speech-dispatcher.install.

Either remote the "[linux-any]" or guard the deb-systemd-helper calls in
debian/speech-dispatcher.postinst to be only executed on Linux.

[Bug report written on a different system than where I ran into the
issue.]

Bug#904859: dgit: should warn when $buildproductsdir is set but using a command that ignores it

[Sean Whitton]

Package: dgit
Version: 6.1

In particular, `dgit build`.

We discussed this but I don't think we ever implemented it.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904858: libtickit-widget-tabbed-perl: Incomplete debian/copyright?

[Chris Lamb]

Source: libtickit-widget-tabbed-perl
Version: 0.021-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andrej Shadura , ftpmas...@debian.org

Hi,

I just ACCEPTed libtickit-widget-tabbed-perl from NEW but noticed it 
was missing attribution in debian/copyright for at least Paul Evans.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#904810: emacs-goodies-el: drop muttrc-mode.el

[Nicholas D Steeves]

Dear Mutt maintainers, Antonio, and Faidon,

On Sat, Jul 28, 2018 at 04:24:32PM +0800, David Bremner wrote:
> Package: emacs-goodies-el
> Version: 39.0
> Severity: normal
> 
> This is only (?) available from emacswiki. Melpa doesn't provide these
> packages anymore and neither should we.
> 
> I guess it has also not been updated since 2009

I agree with David's rationale; however, it would be nice to be able
to retain an Emacs mode for editing muttrc.  Would you please contact
upstream Neomutt to see if they would be willing to adopt it?

I am willing to submit either a patch or PR, including extracting the
muttrc-mode information from the emacs-goodies-el info page—if
necessary, it is extra work after all.  Also, I would be happy to help
add the bits that would generate bin:elpa-muttrc to our src:neomutt
package.

There's also mutt-alias.el, which "allows you to lookup and insert the
expansion of mutt mail aliases".  Maybe upstream Neomutt could also
include it in a contrib subdir?

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#904852: lintian: package-contains-documentation-outside-usr-share-doc far too overzealous

[Chris Lamb]

Hi Axel,

> the phrase "Please move this files to /usr/share/doc/ or remove it."
> sounds very final, but completely ignores that there are quite a lot of
> files (often named README or so) documenting the purpose or contents of
> the directory they're in.

I agree. Bastian, you added this in #901274 — can you chime in here? I
am not the greatest fan of this tag, and have already skipped it in some
of my own packages which is not the best sign from a Lintian maintainer...


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#877871: RFP: pyside2 -- Python bindings for Qt5

[Kurt Kremitzki]

I'm very glad to see an update on this!

On 07/26/2018 09:16 AM, Raphael Hertzog wrote:
...
> 
> I hope the package will continue to build once the Qt 5.11 transition is
> over, right now it doesn't because unstable is in flux with the transition
> that just started. It might build against experimental, I haven't tried.
> 

It seems like the instability has ended because I'm able to build it
now. However, it also seems multi-core build support isn't working.

Bug#877871: RFP: pyside2 -- Python bindings for Qt5

[Kurt Kremitzki]

I'm very glad to see an update on this!

On 07/26/2018 09:16 AM, Raphael Hertzog wrote:
...
> 
> I hope the package will continue to build once the Qt 5.11 transition is
> over, right now it doesn't because unstable is in flux with the transition
> that just started. It might build against experimental, I haven't tried.
> 

It seems like the instability has ended because I'm able to build it
now. However, it also seems multi-core build support isn't working.

Bug#883950: Next steps on "[GPL-3+]" proposal

[Sean Whitton]

Hello,

On Sat 28 Jul 2018 at 04:15PM +0100, Simon McVittie wrote:

> On Sun, 29 Jul 2018 at 00:50:34 +1000, Stuart Prescott wrote:
>> Let us consider this proposed syntax in terms of what someone unfamiliar
>> with the format is going to see
>
> Along these lines, it might be helpful for people with an interest in
> pushing this forward to convert some d/copyright files to their proposed
> syntax, as concrete examples of what they're proposing. The ftp team
> might also find it easier to approve or reject proposals when looking at
> a concrete example?

I don't think this would be a good use of anyone's time until we make
progress on #904729.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#904793: RFS: libskk/1.0.4-2

[Boyuan Yang]

Hi Adam,

I made a reupload. Please try again.

---
Thanks,
Boyuan Yang

Adam Borowski  于2018年7月29日周日 上午8:11写道：
>
> On Sat, Jul 28, 2018 at 01:43:58PM +0800, 073p...@gmail.com wrote:
> >  * Package name: libskk
> >Version : 1.0.4-2
>
> [~/tmp/pkg]$ dget 
> https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4-2.dsc
> dget: retrieving 
> https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4-2.dsc
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  2237  100  22370 0   5049  0 --:--:-- --:--:-- --:--:--  5038
> dget: retrieving 
> https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4.orig.tar.gz
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  184k  100  184k0 0   564k  0 --:--:-- --:--:-- --:--:--  564k
> dget: retrieving 
> https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4-2.debian.tar.xz
>   % Total% Received % Xferd  Average Speed   TimeTime Time  
> Current
>  Dload  Upload   Total   SpentLeft  Speed
> 100  4568  100  45680 0  23070  0 --:--:-- --:--:-- --:--:-- 23070
> libskk_1.0.4-2.dsc:
>   Good signature found
>validating libskk_1.0.4.orig.tar.gz
> dscverify: invalid file length for libskk_1.0.4.orig.tar.gz (wanted 188524 
> got 188529)
>validating libskk_1.0.4-2.debian.tar.xz
> Validation FAILED!!
>
>
> As it's not the typical problem of a tarball on mentors.d.n differing from
> what's in the archive but the .dsc not matching the rest, I can't reliably
> recover: the new state might be not what you want.
>
> Thus, could you please re-upload?
>
>
> Meow!
> --
> // If you believe in so-called "intellectual property", please immediately
> // cease using counterfeit alphabets.  Instead, contact the nearest temple
> // of Amon, whose priests will provide you with scribal services for all
> // your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#904311: bugs.debian.org: connection to sometimes 2607:f8f0:614:1::1274:39 times out

[Vincent Lefevre]

The problem still occurs.

The machine answers to ping, but https doesn't work.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#895645: unable to load a web page fully related

[Michael Gilbert]

On Fri, Apr 13, 2018 at 5:29 PM, Jeffrin Thalakkottoor wrote:
> $sudo cat /var/log/syslog | grep query
> Apr 14 00:31:33 debian chromium.desktop[4485]:
> [869:905:0414/003133.619322:ERROR:adm_helpers.cc(73)] Failed to query stereo
> recording.

Can you try disabling extensions?  This upstream bug [0] mentions that
this error goes away if extensions are disabled.

Best wishes,
Mike

[0] http://crbug.com/694445

Bug#904793: RFS: libskk/1.0.4-2

[Adam Borowski]

On Sat, Jul 28, 2018 at 01:43:58PM +0800, 073p...@gmail.com wrote:
>  * Package name: libskk
>Version : 1.0.4-2

[~/tmp/pkg]$ dget 
https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4-2.dsc
dget: retrieving 
https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4-2.dsc
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  2237  100  22370 0   5049  0 --:--:-- --:--:-- --:--:--  5038
dget: retrieving 
https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4.orig.tar.gz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  184k  100  184k0 0   564k  0 --:--:-- --:--:-- --:--:--  564k
dget: retrieving 
https://mentors.debian.net/debian/pool/main/libs/libskk/libskk_1.0.4-2.debian.tar.xz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  4568  100  45680 0  23070  0 --:--:-- --:--:-- --:--:-- 23070
libskk_1.0.4-2.dsc:
  Good signature found
   validating libskk_1.0.4.orig.tar.gz
dscverify: invalid file length for libskk_1.0.4.orig.tar.gz (wanted 188524 got 
188529)
   validating libskk_1.0.4-2.debian.tar.xz
Validation FAILED!!


As it's not the typical problem of a tarball on mentors.d.n differing from
what's in the archive but the .dsc not matching the rest, I can't reliably
recover: the new state might be not what you want.

Thus, could you please re-upload?


Meow!
-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.

Bug#904857: libconfig-dev: missing CMake package files

[nick black]

Package: libconfig-dev
Version: 1.5-0.4
Severity: important

Dear Maintainer,

Please include the various CMake files with libconfig-dev and
libconfig++-dev, including:

cmake/libconfig++/libconfig++Config.cmake
cmake/libconfig/libconfigConfig.cmake

Thanks! They're already installed in e.g Arch's libconfig 1.7.2-1:

 https://www.archlinux.org/packages/community/x86_64/libconfig/files/

and necessary for pleasant use of libconfig in CMake apps.

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

Kernel: Linux 4.17.10 (SMP w/20 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libconfig-dev depends on:
ii  libconfig9  1.5-0.4
ii  pkg-config  0.29-4+b1

Versions of packages libconfig-dev recommends:
ii  libconfig-doc  1.5-0.4

libconfig-dev suggests no packages.

-- no debconf information

Bug#904856: scilab ftbfs in unstable

[Matthias Klose]

Package: src:scilab
Version: 6.0.1-2
Severity: serious
Tags: sid buster

libtool: compile:  gfortran -DNDEBUG -I../../modules/core/includes/ -g -O2 -c
src/fortran/dqags.f  -fPIC -o src/fortran/.libs/dqags.o
/bin/bash ../../libtool  --tag=F77   --mode=compile gfortran -DNDEBUG
-I../../modules/core/includes/ -g -O2 -c -o src/fortran/xerrwv.lo
src/fortran/xerrwv.f
libtool: compile:  gfortran -DNDEBUG -I../../modules/core/includes/ -g -O2 -c
src/fortran/xerrwv.f  -fPIC -o src/fortran/.libs/xerrwv.o
/bin/bash ../../libtool  --tag=F77   --mode=compile gfortran -DNDEBUG
-I../../modules/core/includes/ -g -O2 -c -o src/fortran/twodq.lo 
src/fortran/twodq.f
libtool: compile:  gfortran -DNDEBUG -I../../modules/core/includes/ -g -O2 -c
src/fortran/twodq.f  -fPIC -o src/fortran/.libs/twodq.o
src/fortran/twodq.f:373:17:

   call tridv(node,node1,node2,0.5d0,1)
 1
Error: Actual argument contains too few elements for dummy argument 'node'
(9/10) at (1)
make[3]: *** [Makefile:1444: src/fortran/twodq.lo] Error 1
make[3]: Leaving directory '/<>/modules/differential_equations'
make[2]: *** [Makefile:842: all-recursive] Error 1
make[2]: Leaving directory '/<>/modules'
make[1]: *** [Makefile:1590: all-recursive] Error 1
make[1]: Leaving directory '/<>'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build]
Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Bug#904855: octave ftbfs in unstable

[Matthias Klose]

Package: src:octave
Version: 4.4.0-3
Severity: serious
Tags: sid buster

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/uuid -I/usr/include/freetype2
-I/usr/include/libpng16 -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL
-I/usr/include/x86_64-linux-gnu/qt5
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtHelp
-I/usr/include/x86_64-linux-gnu/qt5
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtGui
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtSql
-I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtCore
-I/usr/include/x86_64-linux-gnu/qt5 -I./libgui/qterminal/libqterminal
-Ilibgui/src -I./libgui/src -I./libgui/src/m-editor -I./libgui/src/qtinfo
-I./libgui/graphics -I./liboctave/array -Iliboctave/numeric
-I./liboctave/numeric -Iliboctave/operators -I./liboctave/operators
-I./liboctave/system -I./liboctave/util -Ilibinterp -I./libinterp
-Ilibinterp/parse-tree -I./libinterp/parse-tree -Ilibinterp/corefcn
-I./libinterp/corefcn -I./libinterp/octave-value -I./liboctave/wrappers
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -fopenmp -Wall -W -Wshadow
-Wold-style-cast -Wformat -Wpointer-arith -Wwrite-strings -Wcast-align
-Wcast-qual -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -c
libgui/src/settings-dialog.cc  -fPIC -DPIC -o
libgui/src/.libs/libgui_src_libgui_src_la-settings-dialog.o
libgui/src/settings-dialog.cc: In constructor
'settings_dialog::settings_dialog(QWidget*, const QString&)':
libgui/src/settings-dialog.cc:302:57: error: invalid use of incomplete type
'class QButtonGroup'
   QButtonGroup *icon_size_group = new QButtonGroup (this);
 ^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtoolbutton.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QToolButton:1,
 from libgui/src/octave-dock-widget.h:30,
 from libgui/src/variable-editor.h:33,
 from libgui/src/settings-dialog.cc:33:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note:
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
libgui/src/settings-dialog.cc:303:18: error: invalid use of incomplete type
'class QButtonGroup'
   icon_size_group->addButton (ui->icon_size_small);
  ^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtoolbutton.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QToolButton:1,
 from libgui/src/octave-dock-widget.h:30,
 from libgui/src/variable-editor.h:33,
 from libgui/src/settings-dialog.cc:33:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note:
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
libgui/src/settings-dialog.cc:304:18: error: invalid use of incomplete type
'class QButtonGroup'
   icon_size_group->addButton (ui->icon_size_normal);
  ^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtoolbutton.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QToolButton:1,
 from libgui/src/octave-dock-widget.h:30,
 from libgui/src/variable-editor.h:33,
 from libgui/src/settings-dialog.cc:33:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note:
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
libgui/src/settings-dialog.cc:305:18: error: invalid use of incomplete type
'class QButtonGroup'
   icon_size_group->addButton (ui->icon_size_large);
  ^~
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtoolbutton.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QToolButton:1,
 from libgui/src/octave-dock-widget.h:30,
 from libgui/src/variable-editor.h:33,
 from libgui/src/settings-dialog.cc:33:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qabstractbutton.h:53:7: note:
forward declaration of 'class QButtonGroup'
 class QButtonGroup;
   ^~~~
libgui/src/settings-dialog.cc:312:52: error: invalid use of incomplete type
'class QButtonGroup'
   QButtonGroup *icon_group = new QButtonGroup (this);
^
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtoolbutton.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QToolButton:1,
 from libgui/src/octave-dock-widget.h:30,
 from libgui/src/variable-editor.h:33,
 from 

Bug#860158: python-pbcore: prints warnings with recent h5py on ppc64el

[Andreas Tille]

Hi,

with recent pandas in unstable I get:


...
=== FAILURES ===
__ TestCobraFluxAnalysis.test_fva_data_frame ___

self = 
model = 

def test_fva_data_frame(self, model):
df = flux_variability_analysis(model)
>   assert numpy.all([df.columns.values == ['maximum', 'minimum']])
E   assert False
E+  where False = ([array([False, 
False])])
E+where  = numpy.all

cobra/test/test_flux_analysis.py:450: AssertionError

   
...

I have no time for investigation the next 48 hours

  Andreas.


-- 
http://fam-tille.de

Bug#904854: gemma ftbfs in unstable (test failures and libquadmath not available on all architectures)

[Matthias Klose]

Package: src:gemma
Version: 0.97+dfsg-3
Severity: serious
Tags: sid buster

gemma ftbfs in unstable (test failures and libquadmath not available on all
architectures).  Please check the availability of libquadmath before explicitly
linking with libquadmath.

on amd64:

Ran 12 tests.

FAILED (failures=11)
tail -n 1 test.log | grep -q OK
make[1]: *** [Makefile:175: slow-check] Error 1
make[1]: Leaving directory '/<>/gemma-0.97+dfsg'
dh_auto_test: make -j4 check returned exit code 2
make: *** [debian/rules:18: build-arch] Error 2

Bug#904853: casacore ftbfs in unstable

[Matthias Klose]

Package: src:casacore
Version: 2.4.1-1
Severity: serious
Tags: sid buster

casacore ftbfs in unstable:

Start 460: tConvert
460/460 Test #460: tConvert .***Failed0.21 sec
187c187
< [45. 46.]
---
> [ 45.  46.]
191c191
< [45.]
---
> [ 45.]
193c193
< [45. 46.]
---
> [ 45.  46.]
309c309
< [1.3 4.  5.  6. ]
---
> [ 1.3  4.   5.   6. ]
311c311
< [10.-11.j  1. +2.j]
---
> [ 10.-11.j   1. +2.j]
323c323
< [10.-11.j  1. +2.j]
---
> [ 10.-11.j   1. +2.j]
332c332
< [3. 5. 7. 9.]
---
> [ 3.  5.  7.  9.]
334c334
< [3. 5. 7. 9.]
---
> [ 3.  5.  7.  9.]
336c336
< [3. 5. 7. 9.]
---
> [ 3.  5.  7.  9.]
338c338
< [20.+10.j]
---
> [ 20.+10.j]
340c340
< [21.]
---
> [ 21.]
346c346
< [2, 1.3, array([ True, False])]
---
> [2, 1.3, array([ True, False], dtype=bool)]
FAIL (output not verified): ./tConvert


99% tests passed, 1 tests failed out of 460

Total Test time (real) = 105.75 sec

The following tests FAILED:
460 - tConvert (Failed)
Errors while running CTest
make[2]: *** [Makefile:144: test] Error 8

Bug#904852: lintian: package-contains-documentation-outside-usr-share-doc far too overzealous

[Axel Beckert]

Package: lintian
Version: 2.5.94
Severity: normal

Hi,

the phrase "Please move this files to /usr/share/doc/ or remove it."
sounds very final, but completely ignores that there are quite a lot of
files (often named README or so) documenting the purpose or contents of
the directory they're in.

Examples:

---
$ cat /usr/lib/xymon/client/local/README
This directory - the client/local/ directory - can be used to
install Xymon client add-on scripts. The Xymon client will run
all files in this directory that are executable, and include the
output from each script in a separate section in the Xymon client
message which is sent to the Xymon server.

This output will have to be processed on the Xymon server; there
is no default processing done by Xymon on the output from these
scripts. They are merely added to the client data.

If you want to install an add-on script that direcly generates a 
status column in Xymon, this should go in the client/ext/ directory
instead.
---
$ cat /etc/sudoers.d/README
#
# As of Debian version 1.7.2p1-1, the default /etc/sudoers file created on
# installation of the package now includes the directive:
# 
#   #includedir /etc/sudoers.d
# 
# This will cause sudo to read and parse any files in the /etc/sudoers.d 
# directory that do not end in '~' or contain a '.' character.
# 
# Note that there must be at least one file in the sudoers.d directory (this
# one will do), and all files in this directory should be mode 0440.
# 
# Note also, that because sudoers contents can vary widely, no attempt is 
# made to add this directive to existing sudoers files on upgrade.  Feel free
# to add the above directive to the end of your /etc/sudoers file to enable 
# this functionality for existing installations if you wish!
#
# Finally, please note that using the visudo command is the recommended way
# to update sudoers content, since it protects against many failure modes.
# See the man page for visudo for more information.
---
$ cat /usr/share/rlwrap/filters/README
The filters in this directory have been written to test rlwrap,
not to be practical.
---

If you do a "find /etc /var /usr -name README -not -path
'/usr/share/doc/*'" you'll find tons more of such cases, but also cases
like these, where it definitely doesn't make sense to rename (!) all
these files and put them elsewhere (didn't check if lintian complains
about them, but according to the tag description it probably will):

/usr/share/themes/Agualemon/xfwm4/README
/usr/share/themes/BlackMATE/README
/usr/share/themes/Moheli/xfwm4/README
/usr/share/themes/Daloa/xfwm4/README
/usr/share/themes/Default-4.2/xfwm4/README
/usr/share/themes/Xfce/xfwm4/README
/usr/share/themes/Perl/xfwm4/README
/usr/share/themes/Tgc-large/xfwm4/README
/usr/share/themes/Curve/xfwm4/README
/usr/share/themes/Eazel-blue/xfwm4/README
/usr/share/themes/ukui-theme-jun/gtk-2.0/widgets/README
/usr/share/themes/Wallis/xfwm4/README
/usr/share/themes/TraditionalOk/xfwm4/README
/usr/share/themes/Defcon-IV/xfwm4/README
/usr/share/themes/TUX/xfwm4/README
/usr/share/themes/Tabs/xfwm4/README
/usr/share/themes/Redmond/xfwm4/README
/usr/share/themes/Kokodi/xfwm4/README
/usr/share/themes/Retro/xfwm4/README
/usr/share/themes/Alternate/xfwm4/README
/usr/share/themes/Default/xfwm4/README
/usr/share/themes/Gnububble/xfwm4/README
/usr/share/themes/MurrinaBlue/xfwm4/README
/usr/share/themes/Exocet/xfwm4/README
/usr/share/themes/Platinum/xfwm4/README
/usr/share/themes/Tubular/xfwm4/README
/usr/share/themes/R9X/xfwm4/README
/usr/share/themes/CortlandChicken/README
/usr/share/themes/Microcurve/xfwm4/README
/usr/share/themes/Symphony/xfwm4/README
/usr/share/themes/Prune/xfwm4/README
/usr/share/themes/RedmondXP/xfwm4/README
/usr/share/themes/Wildbush/xfwm4/README
/usr/share/themes/MurrinaAzul/xfwm4/README
/usr/share/themes/Biz/xfwm4/README
/usr/share/themes/Meenee/xfwm4/README
/usr/share/themes/Slimline/xfwm4/README
/usr/share/themes/BBS/xfwm4/README
/usr/share/themes/Kde/xfwm4/README
/usr/share/themes/Keramik/xfwm4/README
/usr/share/themes/MurrinaBleu/xfwm4/README
/usr/share/themes/Gtk/xfwm4/README
/usr/share/themes/Coolclean/xfwm4/README
/usr/share/themes/Default-4.0/xfwm4/README
/usr/share/themes/Ops/xfwm4/README
/usr/share/themes/Crux/xfwm4/README
/usr/share/themes/Tgc/xfwm4/README
/usr/share/themes/Elberg/xfwm4/README
/usr/share/themes/Default-4.6/xfwm4/README
/usr/share/themes/ukui-theme-black/gtk-2.0/widgets/README
/usr/share/themes/Synthetic/xfwm4/README
/usr/share/themes/MurrinaDark/xfwm4/README
/usr/share/themes/Linea/xfwm4/README
/usr/share/themes/Cruxish/xfwm4/README
/usr/share/themes/Quiet-purple/xfwm4/README
/usr/share/themes/Beastie/xfwm4/README
/usr/share/themes/Kiwi/xfwm4/README

Bug#904441: linux-image-4.17.0-1-amd64: system disk stopped during boot

[Felix C. Stegerman]

Package: src:linux
Version: 4.17.8-1
Followup-For: Bug #904441

Dear Maintainer,

Same issue here; 4.16.0-2-amd64 works fine; ahci.mobile_lpm_policy=1
does not help.

$ cat /sys/bus/scsi/devices/0\:0\:0\:0/model
ST9500325ASG
$ cat /sys/bus/scsi/devices/0\:0\:0\:0/rev
APM1

Happy to help debug this.  Not sure where to start though.

Thanks.

- Felix

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Apple Inc.
product_name: MacBookPro8,1
product_version: 1.0

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

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

Versions of packages linux-image-4.17.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.132
ii  kmod25-1
ii  linux-base  4.5

Versions of packages linux-image-4.17.0-1-amd64 recommends:
ii  apparmor 2.13-4
ii  firmware-linux-free  3.4
ii  irqbalance   1.3.0-0.1+b1

Versions of packages linux-image-4.17.0-1-amd64 suggests:
pn  debian-kernel-handbook  
ii  extlinux3:6.03+dfsg1-2
ii  grub-efi-amd64  2.02+dfsg1-4
pn  linux-doc-4.17  

Versions of packages linux-image-4.17.0-1-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#615646: [installation-guide] How do I know which CD has the package I need?

[Rick Thomas]

On Jul 28, 2018, at 10:44 AM, Holger Wansing  wrote:

> 
> Robert Cymbala  wrote:
>> QUESTION:  
>>   I burned the first fifteen (15) CD's and GNU/Emacs, which I want to 
>> install, 
>>   is not on them.  How do I find out which CDs I need to burn? (There are 37 
>>   more in cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/ and I used to burn 
>>   all the CDs for a release but am too lazy to burn all 52 discs this time, 
>>   I only burnt the first 15.)
> 
> Time has changed, we don't provide that big sets of CD images anymore. 
> So the above question is no longer that important.
> 
> However, I would like to add something like the following to chapter 4.1
> (https://d-i.debian.org/manual/en.amd64/ch04s01.html):
> 
> 
> 
> diff --git a/en/install-methods/official-cdrom.xml 
> b/en/install-methods/official-cdrom.xml
> index 512011690..f1f12554d 100644
> --- a/en/install-methods/official-cdrom.xml
> +++ b/en/install-methods/official-cdrom.xml
> @@ -30,6 +30,12 @@ the installation to download the remaining files or 
> additional CDs.
> 
> 
> 
> +Also, keep in mind: if the CD(s) you are using doesn't contain some packages
> +you need, you can always install that packages afterwards from your running
> +new Debian system (after the installation has finished).
> +
> +
> +
> If your machine doesn't support CD booting (only relevant
> on very old PC systems), but you do have a CD set,
> you can use an alternative strategy such as

For some people, getting packages via the Internet after installation is not an 
option.  For example, air-gapped high-security environments, or folks with very 
slow Internet connections (does anyone remember 9600 baud modems?).

Can we acknowledge such situations in the proposed changes?  For them, at 
least, the question in the subject line is still relevant (perhaps with “CD” 
changed to “DVD”, giving a nod to changing times).

Enjoy!
Rick

Bug#904851: override: ploop:admin/optional

[Reiner Herrmann]

Package: ftp.debian.org
Severity: normal

Hi,

please change the section of the binary package ploop
to 'admin'. It contains only a few small tools and is
therefore incorrectly in section 'libs'.

Thanks!

Kind regards,
   Reiner

Bug#904850: owserver on stretch no longer works with LinkUSB devices, used to work under jessie

[Larry Fahnoe]

Package: owserver
Version: 3.1p5-1
Severity: important
Tags: upstream

Dear Maintainer,

There is a regression from jessie to stretch when using owserver with
LinkUSB 1-Wire bus masters.  The issue is resolved in the current
upstream source.

--Larry

   * What led up to the situation?

owserver from Raspbian/jessie communicates properly with
LinkUSB 1-Wire bus masters.  After a fresh install of
Raspbian/stretch on the same hardware, owserver no longer
communicates properly with the LinkUSB 1-Wire bus master.
owserver has been upgraded since jessie and the version
included in stretch is broken with respect to LinkUSB devices.
The current release of owfs from the upstream source addresses
this issue and I have confirmed that it builds and works on my
system.

From the owfs 3.2p2 changelog:
* fixed LINK-USB when not using libftdi

Summary: Raspbian GNU/Linux 8 (jessie), owfs 2.9p8-6: works properly
 Raspbian GNU/Linux 9 (stretch), owfs 3.1p5-1: fails
 Raspbian GNU/Linux 9 (stretch), owfs 3.2p2: works properly

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

With a LinkUSB connected, owserver 3.1p5-1 exits immediately:

root@pi-b:~# apt list --installed ow\* libow\*
Listing... Done
libow-3.1-5/stable,now 3.1p5-1 armhf [installed,automatic]
ow-shell/stable,now 3.1p5-1 armhf [installed]
owfs-common/stable,now 3.1p5-1 all [installed,automatic]
owserver/stable,now 3.1p5-1 armhf [installed]

root@pi-b:~# owserver --version
owserver version:
3.1p5
libow version:
3.1p5

root@pi-b:~# owserver --link=/dev/ttyUSB0 -p 4304 --foreground 
--error_print=2 --error_level=1
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd 
library isn't found
CONNECT: owlib.c:(216) Cannot open LINK bus master at /dev/ttyUSB0
DEFAULT: owlib.c:(52) No valid 1-wire buses found

After building from upstream source (3.2p2), owserver connects and
works properly:

root@pi-b:~# /opt/owfs/bin/owserver --version
/opt/owfs/bin/owserver version:
3.2p2
libow version:
3.2p2
root@pi-b:~# /opt/owfs/bin/owserver --link=/dev/ttyUSB0 -p 4304 
--foreground --error_print=2 --error_level=1
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd 
library isn't found
^Croot@pi-b:~# echo $?
0

   * An additional suggestion (since package work is required) is to
 build with FTDI support which provides higher performance access
 to FTDI devices.  I used libftdi1-dev from stretch:

root@pi-b:~# apt list --installed libftdi\*
Listing... Done
libftdi1-2/stable,now 1.3-2 armhf [installed,automatic]
libftdi1-dev/stable,now 1.3-2 armhf [installed]
libftdi1-doc/stable,now 1.3-2 all [installed,automatic]

root@pi-b:~# lsusb | grep FT232
Bus 001 Device 004: ID 0403:6001 Future Technology Devices 
International, Ltd FT232 USB-Serial (UART) IC

root@pi-b:~# /opt/owfs/bin/owserver -d ftdi:d:001/004 -p 4304 
--foreground --error_print=2 --error_level=1
CONNECT: ow_dnssd.c:(81) Zeroconf/Bonjour is disabled since dnssd 
library isn't found
^Croot@pi-b:~# echo $?
0

-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 9.4 (stretch)
Release:9.4
Codename:   stretch
Architecture: armv7l

Kernel: Linux 4.14.52-v7+ (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages owserver depends on:
ii  libc62.24-11+deb9u3
ii  libgcc1  1:6.3.0-18+rpi1+deb9u1
ii  libow-3.1-5  3.1p5-1
ii  lsb-base 9.20161125+rpi1
ii  owfs-common  3.1p5-1

owserver recommends no packages.

Versions of packages owserver suggests:
ii  avahi-daemon  0.6.32-2

-- no debconf information

-- 
Larry Fahnoe, Fahnoe Technology Consulting, fah...@fahnoetech.com
   Minneapolis, Minnesota   www.FahnoeTech.com

Bug#904849: maxima: stderr is sent to stdout

[Anders Andersson]

Package: maxima
Version: 5.41.0-3
Severity: normal

While writing a script for Maxima, I wanted to print output to stdout while
simultaneously printing debug output to stderr. I am reporting this as a debian
bug first because console I/O likely ties in to the underlying libraries and
build configuration.



In the documentation for the Maxima "printf" function it states:

> If dest is a stream or true, then printf returns false. Otherwise, printf
> returns a string containing the output. By default the streams stdin, stdout
> and stderr are defined.

However, the output I expected to go to stderr actually went to stdout instead.



Here is a one-liner to show the behaviour:

> maxima --very-quiet -r >maxima-stdout 2>maxima-stderr \
>'printf(stdout,"stdout~%")$ printf(stderr,"stderr~%")$'

I expect two files: maxima-stdout should contain "stdout" and maxima-stderr
should contan "stderr". Instead, maxima-stdout contains both lines and
maxima-stderr is empty.



Starting up a Maxima session, stdout and stderr does not seem to mean anything
until using them with printf(). After doing that, I can print what stdout and
stderr are connected to:

> Maxima 5.41.0 http://maxima.sourceforge.net
> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1) stdout;
> (%o1)   stdout
> (%i2) stderr;
> (%o2)   stderr
> (%i3) printf(stdout,"Hello")$
> Hello
> (%i4) printf(stderr,"World")$
> World
> (%i5) stdout;
> (%o5) #
> (%i6) stderr;
> (%o6) #



My Maxima bug_report() says this:

-
Maxima version: "5.41.0"
Maxima build date: "2018-03-29 16:06:55"
Host type: "x86_64-pc-linux-gnu"
Lisp implementation type: "GNU Common Lisp (GCL)"
Lisp implementation version: "GCL 2.6.12"
-



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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages maxima depends on:
ii  libc6 2.27-5
ii  libgmp10  2:6.1.2+dfsg-3
ii  libreadline7  7.0-5
ii  libx11-6  2:1.6.5-1

Versions of packages maxima recommends:
ii  gnuplot-x11   5.2.2+dfsg1-2
ii  maxima-share  5.41.0-3

Versions of packages maxima suggests:
ii  maxima-doc5.41.0-3
pn  maxima-emacs  
pn  texmacs   
ii  tk [wish] 8.6.0+9
pn  xmaxima   

-- no debconf information

Bug#904848: apulse: please add Multi-Arch support

[Yuriy M. Kaminskiy]

Package: apulse
Version: 0.1.12-1
Severity: normal
Tags: patch

Dear Maintainer,

Please add support for co-installation of apulse package for multi-arch
systems. Patch attached; I've briefly tested without any apparent 
problems (in self-compiled backport on stretch system).


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'proposed-updates-debug'), (500, 'proposed-updates'), (500, 'stable')

Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R), 
LANGUAGE=ru_RU.KOI8-R (charmap=KOI8-R)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

diff -Nru apulse-0.1.12/debian/control apulse-0.1.12/debian/control
--- apulse-0.1.12/debian/control2018-05-19 20:39:22.0 +0300
+++ apulse-0.1.12/debian/control2018-07-28 23:43:20.0 +0300
@@ -10,6 +10,7 @@
 
 Package: apulse
 Architecture: linux-any
+Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: PulseAudio emulation for ALSA
  The program provides an alternative partial implementation of the PulseAudio
diff -Nru apulse-0.1.12/debian/patches/multi-arch.patch 
apulse-0.1.12/debian/patches/multi-arch.patch
--- apulse-0.1.12/debian/patches/multi-arch.patch   1970-01-01 
03:00:00.0 +0300
+++ apulse-0.1.12/debian/patches/multi-arch.patch   2018-07-28 
23:43:20.0 +0300
@@ -0,0 +1,33 @@
+Index: apulse-0.1.12/CMakeLists.txt
+===
+--- apulse-0.1.12.orig/CMakeLists.txt
 apulse-0.1.12/CMakeLists.txt
+@@ -1,6 +1,8 @@
+ project(apulse)
+ cmake_minimum_required (VERSION 2.8)
+ 
++include(GNUInstallDirs)
++
+ set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -std=gnu99 -Wall -fPIC 
-fvisibility=hidden")
+ set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Werror=implicit-function-declaration")
+ set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -pthread")
+@@ -72,7 +74,7 @@ target_link_libraries(pulse-simple ${SYM
+ 
+ add_subdirectory(tests)
+ 
+-set(APULSEPATH "${CMAKE_INSTALL_PREFIX}/lib/apulse" CACHE PATH "library 
installation directory")
++set(APULSEPATH "${CMAKE_INSTALL_LIBDIR}/apulse" CACHE PATH "library 
installation directory")
+ set(APULSE_SEARCH_PATHS "${APULSEPATH}" CACHE PATH "directory list for 
LD_LIBRARY_PATH")
+ configure_file("${CMAKE_CURRENT_SOURCE_DIR}/src/apulse.template"
+"${CMAKE_CURRENT_BINARY_DIR}/apulse" @ONLY)
+Index: apulse-0.1.12/src/apulse.template
+===
+--- apulse-0.1.12.orig/src/apulse.template
 apulse-0.1.12/src/apulse.template
+@@ -1,5 +1,5 @@
+ #!/bin/sh
+ 
+-APULSEPATH="@APULSE_SEARCH_PATHS@"
++APULSEPATH='/usr/$LIB/apulse'
+ 
+ LD_LIBRARY_PATH=$APULSEPATH${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH} exec "$@"
diff -Nru apulse-0.1.12/debian/patches/series 
apulse-0.1.12/debian/patches/series
--- apulse-0.1.12/debian/patches/series 1970-01-01 03:00:00.0 +0300
+++ apulse-0.1.12/debian/patches/series 2018-07-28 23:43:20.0 +0300
@@ -0,0 +1 @@
+multi-arch.patch

Bug#855918: connection refused after reboot

[Alan Lay]

Hi. I was able to solve this by renaming /etc/init.d/smbd to 
/etc/init.d/smbd.orig. I still don't understand the root cause, but I believe 
that something other than the unit file smbd.service was starting smbd early 
and not waiting for the interface to be configured. Maybe 
systemd-sysv-generator is creating a service unit inappropriately, even though 
a service unit of the same name already exits in /lib/systemd/system.

Alan

Bug#904798: chromium: Chromium failed to upgrade

[Michael Gilbert]

control: tag -1 moreinfo

On Sat, Jul 28, 2018 at 3:13 AM, Remi Vanicat wrote:
> Package: chromium
> Version: 68.0.3440.75-1~deb9u1
[...]
> Upgrading chromium on a sid box failed :

What was the precise command executed that caused this?

> -- System Information:
> Debian Release: buster/sid
>   APT prefers oldstable-updates
>   APT policy: (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), 
> (500, 'oldstable'), (150, 'unstable'), (120, 'experimental')

Your configuration is one that favors stable over unstable, even so
68.0.3440.75-1 (unstable) should have been chosen over
68.0.3440.75-1~deb9u1 (stable) based on dpkg's sorting algorithm.

How specifically would someone else reproduce what you did?

Best wishes,
Mike

Bug#859791: wvstreams: Please migrate to openssl1.1 in Buster

[Reiner Herrmann]

Control: forwarded -1 https://github.com/apenwarr/wvstreams/pull/2
Control: tags -1 + patch

I submitted the attached patch for OpenSSL 1.1 compatibility upstream.
Author: Reiner Herrmann 
Description: Port to OpenSSL 1.1
Bug-Debian: https://bugs.debian.org/859791
Forwarded: https://github.com/apenwarr/wvstreams/pull/2

diff --git a/crypto/wvcrl.cc b/crypto/wvcrl.cc
index fa00c76..880ad85 100644
--- a/crypto/wvcrl.cc
+++ b/crypto/wvcrl.cc
@@ -357,31 +357,19 @@ bool WvCRL::isrevoked(WvStringParm serial_number) const
 	ASN1_INTEGER *serial = serial_to_int(serial_number);
 	if (serial)
 	{
-	X509_REVOKED mayberevoked;
-	mayberevoked.serialNumber = serial;
-	if (crl->crl->revoked)
-	{
-		int idx = sk_X509_REVOKED_find(crl->crl->revoked, 
-	   );
-		ASN1_INTEGER_free(serial);
-		if (idx >= 0)
-{
-debug("Certificate is revoked.\n");
-		return true;
-}
-else
-{
-debug("Certificate is not revoked.\n");
-		return false;
-}
-	}
-	else
-	{
-		ASN1_INTEGER_free(serial);
-		debug("CRL does not have revoked list.\n");
-return false;
-	}
-	
+	X509_REVOKED *revoked_entry = NULL;
+	int idx = X509_CRL_get0_by_serial(crl, _entry, serial);
+	ASN1_INTEGER_free(serial);
+	if (idx >= 1 || revoked_entry)
+{
+debug("Certificate is revoked.\n");
+	return true;
+}
+else
+{
+debug("Certificate is not revoked.\n");
+	return false;
+}
 	}
 	else
 	debug(WvLog::Warning, "Can't convert serial number to ASN1 format. "
diff --git a/crypto/wvdiffiehellman.cc b/crypto/wvdiffiehellman.cc
index 7c0bf32..15cd104 100644
--- a/crypto/wvdiffiehellman.cc
+++ b/crypto/wvdiffiehellman.cc
@@ -39,24 +39,25 @@ WvDiffieHellman::WvDiffieHellman(const unsigned char *_key, int _keylen,
 {
 int problems;
 int check;
-{
+
 	info = DH_new();
-	info->p = BN_bin2bn(_key, _keylen, NULL);
+	BIGNUM *p = BN_bin2bn(_key, _keylen, NULL);
 // 	info->p->top = 0;
 // 	info->p->dmax = _keylen * 8 / BN_BITS2;
 // 	info->p->neg = 0;
 // 	info->p->flags = 0;
 
-	info->g = BN_new();
-	BN_set_word(info->g, generator);
+	BIGNUM *g = BN_new();
+	BN_set_word(g, generator);
 // 	info->g->d = 
 //  	info->g->top = 0;
 //  	info->g->dmax = 1;
 //  	info->g->neg = 0;
 //  	info->g->flags = 0;
-}
 
-check = BN_mod_word(info->p, 24);
+	DH_set0_pqg(info, p, NULL, g);
+
+check = BN_mod_word(p, 24);
 DH_check(info, );
 if (problems & DH_CHECK_P_NOT_PRIME)
  	log(WvLog::Error, "Using a composite number for authentication.\n");
@@ -64,7 +65,7 @@ WvDiffieHellman::WvDiffieHellman(const unsigned char *_key, int _keylen,
 	log(WvLog::Error,"Using an unsafe prime number for authentication.\n");
 if (problems & DH_NOT_SUITABLE_GENERATOR)
 	log(WvLog::Error, "Can you just use 2 instead of %s (%s)!!\n",
-	BN_bn2hex(info->g), check);
+	BN_bn2hex(g), check);
 if (problems & DH_UNABLE_TO_CHECK_GENERATOR)
 	log(WvLog::Notice, "Using a strange argument for diffie-hellman.\n");
 DH_generate_key(info);
@@ -72,18 +73,23 @@ WvDiffieHellman::WvDiffieHellman(const unsigned char *_key, int _keylen,
 
 int WvDiffieHellman::pub_key_len()
 {
-return BN_num_bytes(info->pub_key);
+const BIGNUM *pub_key = NULL;
+	DH_get0_key(info, _key, NULL);
+return BN_num_bytes(pub_key);
 }
 
 int WvDiffieHellman::get_public_value(WvBuf , int len)
 {
-int key_len = BN_num_bytes(info->pub_key);
+	const BIGNUM *pub_key = NULL;
+	DH_get0_key(info, _key, NULL);
+
+int key_len = BN_num_bytes(pub_key);
 if (key_len < len)
 	len = key_len;
 
 // alloca is stack allocated, don't free it.
 unsigned char *foo = (unsigned char*)alloca(key_len);
-BN_bn2bin(info->pub_key, foo);
+BN_bn2bin(pub_key, foo);
 outbuf.put(foo, len);
 
 return len;
@@ -91,8 +97,10 @@ int WvDiffieHellman::get_public_value(WvBuf , int len)
 
 bool WvDiffieHellman::create_secret(WvBuf , size_t in_len, WvBuf& outbuf)
 {
+   const BIGNUM *pub_key = NULL;
+   DH_get0_key(info, _key, NULL);
 unsigned char *foo = (unsigned char *)alloca(DH_size(info));
-   log("My public value\n%s\nYour public value\n%s\n",BN_bn2hex(info->pub_key),
+   log("My public value\n%s\nYour public value\n%s\n",BN_bn2hex(pub_key),
hexdump_buffer(inbuf.peek(0, in_len), in_len, false));
 int len = DH_compute_key (foo, BN_bin2bn(inbuf.get(in_len), in_len, NULL), 
 			  info);
diff --git a/crypto/wvdigest.cc b/crypto/wvdigest.cc
index 150edee..73ebb5d 100644
--- a/crypto/wvdigest.cc
+++ b/crypto/wvdigest.cc
@@ -13,10 +13,10 @@
 
 /* WvEVPMDDigest */
 
-WvEVPMDDigest::WvEVPMDDigest(const env_md_st *_evpmd) :
+WvEVPMDDigest::WvEVPMDDigest(const EVP_MD*_evpmd) :
 evpmd(_evpmd), active(false)
 {
-evpctx = new EVP_MD_CTX;
+evpctx = EVP_MD_CTX_new();
 

Bug#904847: squid-deb-proxy: stale caching when origin returns a redirect

[Corey Hickey]

Package: squid-deb-proxy
Version: 0.8.14
Severity: normal

Dear Maintainer,

I have encountered a problem with caching using squid-deb-proxy. This
may be a bug in squid itself, but I am not familiar enough with squid
to determine that.

The symptom of the problem is:

$ sudo apt-get update
Get:1 http://mirrors.kernel.org/debian sid InRelease [242 kB]
Get:2 http://mirrors.kernel.org/debian experimental InRelease [107 kB]  
  
Hit:3 https://packagecloud.io/slacktechnologies/slack/debian jessie InRelease   

Reading package lists... Done
E: Release file for http://mirrors.kernel.org/debian/dists/sid/InRelease is 
expired (invalid since 49d 18h 44min 20s). Updates for this repository will not 
be applied.
E: Release file for 
http://mirrors.kernel.org/debian/dists/experimental/InRelease is expired 
(invalid since 49d 18h 44min 20s). Updates for this repository will not be 
applied.


I have been using mirrors.kernel.org for a long time; relatively
recently, they started redirecting to mirrors.edge.kernel.org, and I
think that is what triggered this problem.

Here are some debugging commands to show what is happening:

Requesting from the proxy:

$ echo -e 'GET http://mirrors.kernel.org/debian/dists/sid/InRelease 
HTTP/1.1\r\nHost: mirrors.kernel.org\r\nConnection: Close\r\n\r\n' | nc fire 
8000 | head -n 20
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 02 Jun 2018 05:57:45 GMT
Content-Type: text/plain
Content-Length: 241761
Last-Modified: Sat, 02 Jun 2018 02:28:45 GMT
Accept-Ranges: bytes
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-Cache: MISS from squid-deb-proxy
X-Cache-Lookup: HIT from squid-deb-proxy:8000
Via: 1.1 squid-deb-proxy (squid/3.5.27)
Connection: close

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Origin: Debian
Label: Debian
Suite: unstable




Requesting from origin:

$ echo -e 'GET http://mirrors.kernel.org/debian/dists/sid/InRelease 
HTTP/1.1\r\nHost: mirrors.kernel.org\r\nConnection: Close\r\n\r\n' | nc 
mirrors.kernel.org 80 | head -n 20
HTTP/1.1 301 Moved Permanently
Content-length: 0
Location: http://mirrors.edge.kernel.org/debian/dists/sid/InRelease
Connection: close




...and following the redirect:

$ echo -e 'GET http://mirrors.kernel.org/debian/dists/sid/InRelease 
HTTP/1.1\r\nHost: mirrors.kernel.org\r\nConnection: Close\r\n\r\n' | nc 
mirrors.edge.kernel.org 80 | head -n 20
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 28 Jul 2018 21:19:35 GMT
Content-Type: text/plain
Content-Length: 232649
Last-Modified: Sat, 28 Jul 2018 20:28:39 GMT
Connection: close
Content-Security-Policy: default-src https:
Strict-Transport-Security: max-age=15768001
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-XSS-Protection:: 1; mode=block
Accept-Ranges: bytes

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Origin: Debian
Label: Debian
Suite: unstable




Requesting from the proxy results in entries in the access log like:

1532811922.767113 2001:470:805b:1:2efd:a1ff:feba:f3af 
TCP_REFRESH_IGNORED/200 242154 GET 
http://mirrors.kernel.org/debian/dists/sid/InRelease - 
HIER_DIRECT/2001:19d0:306:6:0:1994:3:14 text/plain



>From what I read, TCP_REFRESH_IGNORED means that squid is trying to get
a new object from the origin, but it thinks the response it gets is even
older than the cached object.

Doing a tcpdump on the proxy indicates that it only makes one request:

13:57:03.170260 IP6 tunnel8198-pt.tunnel.tserv3.fmt2.ipv6.he.net.59452 > 
mirrors.pdx.kernel.org.http: Flags [P.], seq 1:343, ack 1, win 222, options 
[nop,nop,TS val 1510245291 ecr 8], length 342: HTTP: GET 
/debian/dists/sid/InRelease HTTP/1.1
13:57:03.204071 IP6 mirrors.pdx.kernel.org.http > 
tunnel8198-pt.tunnel.tserv3.fmt2.ipv6.he.net.59452: Flags [F.], seq 1:142, ack 
343, win 232, options [nop,nop,TS val 88924 ecr 1510245291], length 141: 
HTTP: HTTP/1.1 301 Moved Permanently



I think squid should be returning the 301 to the client, but instead it
is returning a stale cached object.

Thanks,
Corey

-- System Information:
Debian Release: buster/sid
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'testing'), (500, 

Bug#904846: libjs-jstimezonedetect.js doesn't provide a *.min.js

[Sergio Durigan Junior]

Package: libjs-jstimezonedetect
Version: 1.0.6-1

A project I'm packaging depends on libjs-jstimezonedetect, and makes use
of the jstz.min.js file.  However, I can't find this file on the
package:

  $ apt-file list node-jstimezonedetect 
  node-jstimezonedetect: /usr/lib/nodejs/jstimezonedetect/jstz.js
  node-jstimezonedetect: 
/usr/share/doc/node-jstimezonedetect/changelog.Debian.gz
  node-jstimezonedetect: /usr/share/doc/node-jstimezonedetect/copyright

It would be great if you could ship it.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#904845: drop protbuf.el because built-in emacs-lock-mode provides this functionality?

[Nicholas D Steeves]

On Sat, Jul 28, 2018 at 05:06:39PM -0400, Nicholas D Steeves wrote:
> Source: emacs-goodies-el
> Version: 39.0
> Severity: normal
> 
> It seems like protbuf.el can be dropped, because "Emacs Lock is
> included in Emacs 24."
>   https://www.emacswiki.org/emacs/ProtectingBuffers

Oh, and it seems to be unmaintained upstream, and only available on
emacswiki...

Bug#904796: chromium for arm64 lacks security updates

[Michael Gilbert]

control: tag -1 confirmed
control: severity -1 serious
control: found -1 67.0.3396.87-1~deb9u1
control: notfound -1 66.0.3359.117-1~deb9u1

On Sat, Jul 28, 2018 at 2:06 AM, Mikulas Patocka wrote:
> Chromium on arm64 in Debian Stretch stopped receiving security updates.
> Chromium for i386, amd64 and armhf received updates for versions 67 and
> 68, however chromium for arm64 is stuck on version 66.

There was a build error in crashpad on arm64 introduced by upstream
chromium 67.  A patch fixing that has been included with the last two
security uploads, so I'm not sure why those builds would have failed.

Riki, do you have any ideas?

Best wishes,
Mike

Bug#904779: openmpi-bin: any program hangs on first MPI call (e.g. MPI_Init())

[Giacomo Mulas]

(1) How did you execute it ? mpiexec command line , etc?


any way of a number, does not seem to make any difference. Always on
the command line. I tried mpiexec, mpirun, just running the executable
without wrappers (used to work before, if one wanted to run one single
process). I also tried using a different number of processes, from 1 to 8,
no difference. In any case, if I run the code under gdb (or a graphical
wrapper to gdb, like ddd), I can see that the code hangs when trying to
execute the MPI_Init() call. Or, if I try some of the scalapack example
codes, the first call that implicitly tries to initialise MPI.



(2) Can you give the output of :

$ dpkg -l | grep pmix


gmulas@capitanata:~/transfer/debsrc$ dpkg -l | grep pmix
ii  libpmix2:amd64   3.0.0-1
 amd64Process Management 
Interface (Exascale) library



$ dpkg -l | grep psm


gmulas@capitanata:~/transfer/debsrc$ dpkg -l | grep psm
ii  gir1.2-osmgpsmap-1.0 1.1.0-3
 amd64GTK+ library to embed 
OpenStreetMap maps - Python bindings
ii  libcupsmime1:amd64   2.2.8-5
 amd64Common UNIX Printing 
System(tm) - MIME library
ii  libosmgpsmap-1.0-1:amd64 1.1.0-3
 amd64GTK+ library to embed 
OpenStreetMap maps
ii  libpsm-infinipath1   
3.3+20.604758e7-5   amd64PSM 
Messaging library for Intel Truescale adapters
ii  libpsm2-210.3.58-1  
 amd64Intel PSM2 library
ii  psmisc   23.1-1+b1  
 amd64utilities that use 
the proc file system


Any changes to /etc/openmpi/* files or environmental variables


No changes to /etc/openmpi/*. Here is my complete environment:

gmulas@capitanata:~/transfer/debsrc$ env
LC_ALL=it_IT.utf8
LC_MEASUREMENT=it_IT.UTF-8
LC_PAPER=it_IT.UTF-8
LC_MONETARY=it_IT.UTF-8
XDG_MENU_PREFIX=gnome-
LANG=it_IT.utf8
GDM_LANG=it_IT.utf8
LESS=-eiM
DISPLAY=:0
OLDPWD=/home/gmulas/transfer/debsrc/scalapack-2.0.2
DUSTEM_FILTER_DIR=/home/gmulas/PAHmodels/DUSTEM/Data/FILTERS/
EDITOR=joe
COLORTERM=truecolor
USERNAME=gmulas
NO_AT_BRIDGE=1
XDG_VTNR=2
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
PARA_ARCH=MPI
CLASSPATH=/usr/local/JMF-2.1.1e/lib/jmf.jar:.:/usr/local/JMF-2.1.1e/lib/jmf.jar:.
XDG_SESSION_ID=20
USER=gmulas
DUSTEM_DAT=/tmp/
DUSTEM_SOFT_DIR=/home/gmulas/PAHmodels/DUSTEM
PAGER=/usr/bin/less -eiMs
DESKTOP_SESSION=gnome-xorg
JMFHOME=/usr/local/JMF-2.1.1e
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/7aa5ce9c_afbf_4166_9720_8b3d3187d254
PWD=/home/gmulas/transfer/debsrc
HOME=/home/gmulas
TMP=/tmp/user/1000
DUSTEM_DRAINE_DATA_DIR=/home/gmulas/PAHmodels/DUSTEM/Data/DRAINE/
SSH_AGENT_PID=13026
UPARM=/home/gmulas/uparm
QT_ACCESSIBILITY=1
MONKEYSPHERE_VALIDATION_AGENT_SOCKET=http://127.0.0.1:35619
XDG_SESSION_TYPE=x11
MIDASHOME=/usr/local/midas
XDG_DATA_DIRS=/usr/share/gnome:/home/gmulas/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/:
DUSTEM_RES=/tmp/
XDG_SESSION_DESKTOP=gnome-xorg
GJS_DEBUG_OUTPUT=stderr
LC_NUMERIC=it_IT.UTF-8
DUSTEM_WHICH=DESERT
GTK_MODULES=gtk-vector-screenshot:gail:atk-bridge
WINDOWPATH=2
TURBOMOLE_SYSNAME=em64t-unknown-linux-gnu
TERM=xterm-256color
SHELL=/bin/bash
VTE_VERSION=5202
TEMPDIR=/tmp/user/1000
TURBODIR=/usr/local/tmoleX/TURBOMOLE
XDG_CURRENT_DESKTOP=GNOME
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
GNOME_TERMINAL_SERVICE=:1.319
SHLVL=1
XDG_SEAT=seat0
DUSTEM_PAHUV=DESERT
TEMP=/tmp/user/1000
GDMSESSION=gnome-xorg
LESSCHARSET=utf-8
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
LOGNAME=gmulas
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
XDG_RUNTIME_DIR=/run/user/1000
XAUTHORITY=/run/user/1000/gdm/Xauthority
UDEdir=
JACK_START_SERVER=1
PATH=/usr/local/tmoleX/TURBOMOLE/bin/em64t-unknown-linux-gnu_mpi:/usr/local/tmoleX/TURBOMOLE/scripts:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/gOpenMol-3.00/bin
MIDVERS=13SEP
GJS_DEBUG_TOPICS=JS ERROR;JS LOG
SESSION_MANAGER=local/capitanata:@/tmp/.ICE-unix/13067,unix/capitanata:/tmp/.ICE-unix/13067
PIPE_HOME=/usr/local/midas/13SEP/pipeline
LC_TIME=it_IT.UTF-8
_=/usr/bin/env

And, in case it may help, here goes the output of ldd on the simple "hello
world" MPI code I sent you, that hangs here:

gmulas@capitanata:~/PAHmodels/anharmonica-scalapack$ ldd sample_printf
linux-vdso.so.1 (0x7ffd034e3000)
libmpi.so.40 => /usr/lib/x86_64-linux-gnu/libmpi.so.40 
(0x7f94cc309000)
libpthread.so.0 => 

Bug#846006: debian-cd: please provide flavor/spin netinst image for Debian Edu

[Wolfgang Schweer]

On Sat, Jul 28, 2018 at 03:17:02AM +0100, Steve McIntyre wrote:
> >IMO at least these udebs should be added
> >debian-edu-profile-udeb
> >ltsp-client-builder
> 
> ACK. Just added them back now. In discussion with Holger yesterday, we
> thought it was best to start with a small set and build up to what's
> needed.

exim4-daemon-heavy is needed as well; reason is: Debian Edu needs this 
package early to avoid a clash with exim4-daemon-light (iirc installed 
by default) later on in the installation process. The exim4-daemon-heavy 
package is expected to be available on the ISO image to make debootstrap 
happy.

So please consider to adjust 
https://salsa.debian.org/images-team/debian-cd/blob/master/tasks/buster/debian-edu
  
accordingly.

Same might apply to the sudo-ldap package...

Thanks a lot for working on Debian Edu installation media!

Wolfgang


signature.asc
Description: PGP signature

Bug#904845: drop protbuf.el because built-in emacs-lock-mode provides this functionality?

[Nicholas D Steeves]

Source: emacs-goodies-el
Version: 39.0
Severity: normal

It seems like protbuf.el can be dropped, because "Emacs Lock is
included in Emacs 24."
  https://www.emacswiki.org/emacs/ProtectingBuffers

Bug#756859: installation-guide: USB boot

[Holger Wansing]

Osamu Aoki  wrote:
> Installation guide on USB boot is a bit outdated and may need some touch
> up.  (I could not find package to file bug report.)
> 
> === USB-HDD and USB Legacy ===
> 
> http://d-i.debian.org/manual/en.i386/apas02.html#howto-getting-images-usb
> A.2.2. USB memory stick
> 
> | Some BIOSes can boot USB storage directly, and some cannot. You may need
> | to configure your BIOS to boot from a “removable drive” or even a
> | “USB-ZIP” to get it to boot from the USB device. For helpful hints and
> | details, see Section 5.1.5, “Booting from USB Memory Stick”.
> 
> I think this can be:
> 
> | Some BIOSes can boot USB storage directly, and some cannot. You may need
> | to configure your BIOS to set "USB legacy support".  The boot device
> | selection menu should show “removable drive”, "USB-HDD", or even
> | “USB-ZIP” to get it to boot from the USB device.  For helpful hints and
> | details, see Section 5.1.5, “Booting from USB Memory Stick”.
> 
> The rationale is:
> Since current document focus is on iso image copied onto USB, this is
> confusing to have USB-ZIP and not USB-HDD.  Many new BIOSs have USB-HDD
> boot support if USB legacy support is enabled.  USB-HDD installation is
> quite easy, it is usable and intuitive from the HDD image and documented
> in:
>  4.3.2. Manually copying files to the USB stick
>  4.3.3. Manually copying files to the USB stick — the flexible way
> These seems to be complete. 
> 
> === USB-ZIP ===
> 
> USB-ZIP is said to require special partition and use /de/sd?4 for the
> data as documented in the syslinux documentation:
> /usr/share/doc/syslinux-common/txt/usbkey.txt
> 
> So adding pointer to this is needed somewhere on the document is
> desirable (Probably at the bottom of 4.3.)
> 
> === USB Legacy and interfarence ===
> 
> http://d-i.debian.org/manual/en.amd64/ch03s06.html#boot-dev-select
> 3.6.2. Boot Device Selection
> 
> Here,  mention that you may need to enable "USB legacy support" to get
> USB memory stick to become bootable.
> 
> (I have been bitten several times.  So I am sure on this.)
> 
> 3.6.4. Disabling the Windows 8 “fast boot” feature
> 
> Here, mention that enabling "USB legacy support" may interfare with
> booting of Windows 8.
> 
> (This is what I saw on the net.)

I have prepared a patch, to get this into the manual:




diff --git a/en/howto/installation-howto.xml b/en/howto/installation-howto.xml
index ff8a74184..1304b4c0d 100644
--- a/en/howto/installation-howto.xml
+++ b/en/howto/installation-howto.xml
@@ -162,8 +162,10 @@ sticks. For details, see .
 
 
 Some BIOSes can boot USB storage directly, and some cannot. You may need to
-configure your BIOS to boot from a removable drive or even a
-USB-ZIP to get it to boot from the USB device. For helpful
+configure your BIOS to enable USB legacy support. The boot 
device
+selection menu should show removable drive, 
USB-HDD,
+or even USB-ZIP to get it to boot from the USB device.
+For helpful
 hints and details, see .
 
 
diff --git a/en/install-methods/boot-usb-files.xml 
b/en/install-methods/boot-usb-files.xml
index 7f59939d9..d85cf994b 100644
--- a/en/install-methods/boot-usb-files.xml
+++ b/en/install-methods/boot-usb-files.xml
@@ -2,7 +2,7 @@
 
 
  
- Preparing Files for USB Memory Stick Booting
+ Preparing files for USB device booting
 
 
 
@@ -185,4 +183,17 @@ ISO image, even a DVD image, to it.
 
   
 
+  
+  Using an USB-ZIP drive for installation
+
+
+The use of an USB-ZIP drive as installation medium requires some special
+partitioning, and the partition /dev/sdX4 has to be used for the data. Details
+can be found on https://www.syslinux.org/doc/usbkey.txt;>https://www.syslinux.org/doc/usbkey.txt
+
+
+
+  
+
  
diff --git a/en/preparing/bios-setup/i386.xml b/en/preparing/bios-setup/i386.xml
index 4c50c1e2c..73f29271d 100644
--- a/en/preparing/bios-setup/i386.xml
+++ b/en/preparing/bios-setup/i386.xml
@@ -67,6 +67,7 @@ In particular if you use an isohybrid CD/DVD image on a USB 
stick
 (see ), changing the device type to
 USB CDROM helps on some BIOSes which will not boot from a USB 
stick in 
 USB harddisk mode.
+You may need to configure your BIOS to enable USB legacy 
support.
 
 
 



-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#883950: Next steps on "[GPL-3+]" proposal

[Russ Allbery]

Stuart Prescott  writes:

> From my perspective, the brackets are only making work for people who
> will have to rewrite parsers because the license short names are not the
> opaque tokens originally given in copyright-format/1.0.*

To be clear, I don't believe there's a way forward here that doesn't
require at least some rewriting of parsers.  Currently, copyright-format
1.0 requires either that every License stanza in a Files paragraph contain
some "license text" in the copyright-format text (which may just be the
common-licenses pointer) or that there be a later stand-alone License
paragraph with the same short license identifier that has that text.  This
proposal breaks that property by introducing the possibility of a short
license identifier with no accompanying text.  This will require parser
changes.

The silver lining is that this allows us to fix a long-standing wart in
copyright-format in which the License field could take two different forms
with complex semantics: either a first line with short license identifiers
followed by full license text, or only the first line.  The latter
indicated an implicit reference to a later license pargraph.

We can now define two separate fields: License-Identifier, which contains
only the short license identifiers, and License, which contains the short
license identifiers plus the license text.  Every Files paragraph must
then contain *either* a License-Identifier field *or* a License field.
A standalone license paragraph can be provided for identifiers given in a
License-Identifier field, or may be omitted based on the rules of the
distribution.  For Debian, we would say that it may be omitted if the
lienses in question are in common-licenses.

This is not a backward-compatible change, but it's semantically cleaner
and cleans up the semantics of the dual-purpose License field.

One remaining question in my mind is whether we should take the
opportunity of a format change to achieve a few other goals.  The most
obvious one would be to reconcile our short license identifiers with SPDX
(probably by making our identifiers a superset of the SPDX ones).

Note that this would introduce the GPL-2-or-later and GPL-3-or-later (and
friends) identifiers, which are a bit of a wart in the SPDX list since
they're defined to be equivalent to GPL-2+ and GPL-3+, but were requested
by the FSF, and could be used to make the meaning of "+" a lot clearer.

(It would also mean picking up MIT as a synonym for what we call Expat.
We had arguments against that, but I think the argument of convergence
with SPDX is stronger.)

I haven't checked to see if we have any conflicts with SPDX (license
identifiers we define to mean something different than they do).
Hopefully not.

Anyway, that's just an aside -- SPDX convergence will be a separate bug
and discussion if we decided to go down that path.

-- 
Russ Allbery (r...@debian.org)   

Bug#904844: w-scan doesn't detect dutch DVB-T fta channels; fork w-scan2 does

[Bas Zoetekouw]

Package: w-scan
Version: 20170107-1
Severity: normal

The current version of w-scan doesn't detect the dutch DVB-T fta
channels, but only outputs the encrypted channels.  Not sure what's
going on, because of I manaully tune my receiver, I can receive the
channels perfectly.

Anwyay, there is a fork of w-scan on
https://github.com/stefantalpalaru/w_scan2 which seems to be more
actively maintained, and which does detect the fta channels fine.
Please consider switching to the fork instead of the old w_scan
package.




-- System Information:
Debian Release: 9.5
  APT prefers stable
  APT policy: (620, 'stable'), (500, 'stable-updates'), (20, 'unstable'), (10, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages w-scan depends on:
ii  libc6  2.24-11+deb9u3

w-scan recommends no packages.

w-scan suggests no packages.

Bug#615646: [installation-guide] How do I know which CD has the package I need?

[Brian Potkin]

On Sat 28 Jul 2018 at 19:44:26 +0200, Holger Wansing wrote:

> 
> Robert Cymbala  wrote:
> > QUESTION:  
> >I burned the first fifteen (15) CD's and GNU/Emacs, which I want to 
> > install, 
> >is not on them.  How do I find out which CDs I need to burn? (There are 
> > 37 
> >more in cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/ and I used to 
> > burn 
> >all the CDs for a release but am too lazy to burn all 52 discs this 
> > time, 
> >I only burnt the first 15.)
> 
> Time has changed, we don't provide that big sets of CD images anymore. 
> So the above question is no longer that important.
> 
> However, I would like to add something like the following to chapter 4.1
> (https://d-i.debian.org/manual/en.amd64/ch04s01.html):
> 
> diff --git a/en/install-methods/official-cdrom.xml 
> b/en/install-methods/official-cdrom.xml
> index 512011690..f1f12554d 100644
> --- a/en/install-methods/official-cdrom.xml
> +++ b/en/install-methods/official-cdrom.xml
> @@ -30,6 +30,12 @@ the installation to download the remaining files or 
> additional CDs.
>  
>  
>  
> +Also, keep in mind: if the CD(s) you are using doesn't contain some packages
> +you need, you can always install that packages afterwards from your running
> +new Debian system (after the installation has finished).
> +
> +
> +
>  If your machine doesn't support CD booting (only relevant
>  on very old PC systems), but you do have a CD set,
>  you can use an alternative strategy such as

English (partly), I'm afraid:

CD(s) ---> DVD/CDs (brackets not needed)

doesn't ---> don't

that packages ---> a package

(after the installation has finished) is probably superfluous.

Keep up the good work.

Brian.

Bug#904843: boinc-manager: boincmgr does not properly start, exit code 0377

[Christian Lins]

Package: boinc-manager
Version: 7.12.0+dfsg-1exp2
Severity: important

Dear Maintainer,

on my workstation (Debian Testing) I sometimes use boincmgr, but after an
upgrade a few weeks(?) ago, boincmgr does no longer start. I cannot recall the
exact upgrade number as I do not use boincmgr regularily, but for now it does
not properly start:

(gdb) run
Starting program: /usr/bin/boincmgr
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe33fb700 (LWP 9844)]
[New Thread 0x7fffe25ed700 (LWP 9845)]
[New Thread 0x7fffe1dec700 (LWP 9846)]
[Thread 0x7fffe1dec700 (LWP 9846) exited]
[Thread 0x7fffe33fb700 (LWP 9844) exited]
[Thread 0x7fffe3401ac0 (LWP 9840) exited]
[Inferior 1 (process 9840) exited with code 0377]

No GUI is shown.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (500, 'stable'), (2, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.10 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages boinc-manager depends on:
ii  boinc-client  7.12.0+dfsg-1
ii  libboinc7 7.12.0+dfsg-1
ii  libc6 2.27-5
ii  libgcc1   1:8.1.0-12
ii  libglib2.0-0  2.56.1-2
ii  libgtk-3-03.22.30-2
ii  libnotify40.7.7-3
ii  libsqlite3-0  3.24.0-1
ii  libstdc++68.1.0-12
ii  libwxbase3.0-0v5  3.0.4+dfsg-4
ii  libwxgtk-webview3.0-gtk3-0v5  3.0.4+dfsg-4
ii  libwxgtk3.0-gtk3-0v5  3.0.4+dfsg-4

boinc-manager recommends no packages.

Versions of packages boinc-manager suggests:
ii  libgl1-mesa-glx  18.1.4-1
ii  libxt6   1:1.1.5-1

-- no debconf information

Bug#833256: login.defs: debian shipped vs util-linux builtin defaults

[Josh Triplett]

On Sun, 30 Jul 2017 21:32:53 +0200 Andreas Henriksson  wrote:
> My general feeling is that we can likely get away with not shipping
> any /etc/login.defs file at all if we want (or ship one with just
> commented out examples).

The former, please; examples can go in /usr/share/doc. When trying to
build minimal systems, and in particular stateless or near-stateless
systems with configurations as close as possible to the default, it
helps to not have packages shipping configuration files consisting
entirely of comments.

Bug#903851: DBUS? Continuing Problems after migration to "testing"

[Thomas Hardman]

Upon advice I have migrated the machine to "testing", resetting
/etc/apt/sources.list and running `apt-get update ; apt-get dist-upgrade`.
That process did not go without errors but `apt --fix-broken install` run
in a root terminal did complete.

My problem remains. At any time that I allow an unattended reboot, it gets
to a certain point and there is repetitive screen blanking, a brief flash
back to text mode, more screen blanking, etc. Attempts to switch to a text
console (via  for example) provide no relief nor a usable
screen. Flashing continues.

Rebooting and using GRUB to go rescue mode, I can watch the progress, I get
to the "reached rescue target" and login prompts. I give root password and
from there 'service dbus start ; systemctl default' takes me right to the X
login and from there all goes well and as expected. This is all very
repeatable.

Previous attempts to debug this seemed to indicate that 'dbus' was never
started by systemd but that doesn't seem possible. Yet that's how I hit on
the simple workaround of starting D-Bus from the rescue commandline. My
clue was messages in logs to the effect that /var/run/dbus did not exist.

I have /var on a "spinner" drive along with /home and /tmp, and /  and /usr
are on two different partitions of an NVME/PCIe solid-state drive.

/etc/fstab mounts these partitions from the "spinner" drive using UUID
rather than calling (for example) /dev/sda1 to mount on /var. Possibly
irrelevant.

Is it possible that somewhere in the process of mounting the spinner
partition for /var, the dbus directory with dbus.service and dbus.socket
becomes inaccessible and need to be recreated with `service dbus restart`?

If this seems likely, please advise on how to  add a workaround to the
systemd startup process. I admit to being less than proficient in systemd,
having come from sysv init.

Regards,

Bug#401889: [installation-guide] memory requirements for powerpc

[John Paul Adrian Glaubitz]

> On Jul 28, 2018, at 8:45 PM, Holger Wansing  wrote:
> 
> 
> Holger Levsen :
>> the following memory requirements for powerpc should be documented in the 
>> manual, because booting with too little memory results in strange effects / 
>> error messages, which especially people new to powerpc will not understand, 
>> and therefor think the installer is broken for there machine.
>> 
>> d-i: recommended is 48mb, might work with less, but on newworld it sureley 
>> doesnt boot with 32mb. (tested with daily cd from 2006-12-04). 64mb is still 
>> low-mem.
>> 
>> d-i: recommended is 128mb. works with 96mb, but partioning is buggy then. 
>> (it 
>> crashes and comes back, so it's usable, but really not recommended. With 
>> 96mb 
>> the main partition would "reliably" have no mount point set, with 160 mb 
>> this 
>> is no problem.)
> 
> Since powerpc is no longer a release-arch, and the things are most likely to 
> behave different with ppc64el, I would close this bug.

It’s not a release arch, but still maintained in Debian Ports.

Adrian

Bug#904842: Fails to compile with linux 4.15+ due to new timer interface

[Jakob Haufe]

Seems like I overlooked it when looking for a solution: There's a
corresponding upstream bug report at [1] containing a similar patch.

It might be better to include the patch available there as it will most
probably be applied upstream. If wanted, I can test the upstream patch
as well.

Cheers,
sur5r

[1] https://issues.asterisk.org/jira/browse/DAHLIN-359

-- 
ceterum censeo microsoftem esse delendam.


pgpz3avr_dRCd.pgp
Description: OpenPGP digital signature

Bug#904841: tracker.debian.org: Bugs total double-counts bugs with patches

[Rebecca N. Palmer]

Package: tracker.debian.org
Severity: minor
Control: tags -1 patch

The 'all' bugs count double-counts 'patch' bugs (but not 'help' or 
'newcomer' bugs, which also appear both there and in a severity 
category), e.g. https://tracker.debian.org/pkg/debhelper


Can probably be fixed (though I haven't tried this) by adding 'patch' to 
the exclude_from_count list at:


https://salsa.debian.org/qa/distro-tracker/blob/master/distro_tracker/vendor/debian/models.py#L333

Bug#904842: Fails to compile with linux 4.15+ due to new timer interface

[Jakob Haufe]

Package: dahdi-source
Version: 1:2.11.1.0.20170917~dfsg-3
Severity: important
Tags: upstream patch

Linux 4.15 introduced a new timer interface. This breaks compilation of
the
dahdi modules.

The attached patch fixes this. The original code is guarded by #ifdef
to keep it working for pre-4.15 kernels. It was compiled and tested
successfully against:

* 4.9.0-7-amd64
* 4.15.0-3-amd64
* 4.16.0-2-amd64
* 4.17.0-1-amd64

Please be aware that I was only able to test the zaphfc part in both NT
and TE mode as I currently have no access to other dahdi hardware.

Cheers,
sur5r

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

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C
(charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dahdi-source depends on:
ii  bzip2 1.0.6-8.1
ii  debhelper 11.3.5
ii  module-assistant  0.11.10

Versions of packages dahdi-source recommends:
ii  dahdi-linux  1:2.11.1.0.20170917~dfsg-3

dahdi-source suggests no packages.

-- no debconf information
diff --git a/dahdi/drivers/dahdi/dahdi-base.c b/dahdi/drivers/dahdi/dahdi-base.c
index 36766e6..7cd0a3d 100644
--- a/dahdi/drivers/dahdi/dahdi-base.c
+++ b/dahdi/drivers/dahdi/dahdi-base.c
@@ -10069,7 +10069,11 @@ static inline unsigned long msecs_processed(const struct core_timer *const ct)
 	return atomic_read(>count) * DAHDI_MSECS_PER_CHUNK;
 }
 
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+static void coretimer_func(struct timer_list *param)
+#else
 static void coretimer_func(unsigned long param)
+#endif
 {
 	unsigned long flags;
 	unsigned long ms_since_start;
@@ -10150,8 +10154,12 @@ static void coretimer_func(unsigned long param)
 
 static void coretimer_init(void)
 {
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+	timer_setup(_timer.timer, coretimer_func, 0);
+#else
 	init_timer(_timer.timer);
 	core_timer.timer.function = coretimer_func;
+#endif
 	ktime_get_ts(_timer.start_interval);
 	atomic_set(_timer.count, 0);
 	atomic_set(_timer.shutdown, 0);
diff --git a/dahdi/drivers/dahdi/dahdi_dynamic.c b/dahdi/drivers/dahdi/dahdi_dynamic.c
index 0a37e2a..699c9c9 100644
--- a/dahdi/drivers/dahdi/dahdi_dynamic.c
+++ b/dahdi/drivers/dahdi/dahdi_dynamic.c
@@ -831,7 +831,11 @@ EXPORT_SYMBOL(dahdi_dynamic_unregister_driver);
 
 static struct timer_list alarmcheck;
 
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+static void check_for_red_alarm(struct timer_list *ignored)
+#else
 static void check_for_red_alarm(unsigned long ignored)
+#endif
 {
 	int newalarm;
 	int alarmchanged = 0;
@@ -867,10 +871,14 @@ static const struct dahdi_dynamic_ops dahdi_dynamic_ops = {
 static int dahdi_dynamic_init(void)
 {
 	/* Start process to check for RED ALARM */
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+	timer_setup(, check_for_red_alarm, 0);
+#else
 	init_timer();
 	alarmcheck.expires = 0;
 	alarmcheck.data = 0;
 	alarmcheck.function = check_for_red_alarm;
+#endif
 	/* Check once per second */
 	mod_timer(, jiffies + 1 * HZ);
 #ifdef ENABLE_TASKLETS
diff --git a/dahdi/drivers/dahdi/dahdi_dynamic_ethmf.c b/dahdi/drivers/dahdi/dahdi_dynamic_ethmf.c
index dec368b..ac59951 100644
--- a/dahdi/drivers/dahdi/dahdi_dynamic_ethmf.c
+++ b/dahdi/drivers/dahdi/dahdi_dynamic_ethmf.c
@@ -681,7 +681,11 @@ static int ethmf_delay_dec(void)
  * Timer callback function to allow all spans to be added, prior to any of
  * them being used.
  */
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+static void timer_callback(struct timer_list *param)
+#else
 static void timer_callback(unsigned long param)
+#endif
 {
 	if (ethmf_delay_dec()) {
 		if (!atomic_read(_deleted)) {
@@ -764,9 +768,13 @@ static const struct file_operations ztdethmf_proc_fops = {
 
 static int __init ztdethmf_init(void)
 {
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+	timer_setup(, _callback, 0);
+#else
 	init_timer();
-	timer.expires = jiffies + HZ;
 	timer.function = _callback;
+#endif
+	timer.expires = jiffies + HZ;
 	if (!timer_pending())
 		add_timer();
 
diff --git a/dahdi/drivers/dahdi/wctc4xxp/base.c b/dahdi/drivers/dahdi/wctc4xxp/base.c
index 0d76d6a..6f0ea19 100644
--- a/dahdi/drivers/dahdi/wctc4xxp/base.c
+++ b/dahdi/drivers/dahdi/wctc4xxp/base.c
@@ -3701,9 +3701,15 @@ wctc4xxp_send_commands(struct wcdte *wc, struct list_head *to_send)
 }
 
 static void
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 15, 0)
+wctc4xxp_watchdog(struct timer_list *data)
+{
+	struct wcdte *wc = from_timer(wc, data, watchdog);
+#else
 wctc4xxp_watchdog(unsigned long data)
 {
 	struct wcdte *wc = (struct wcdte *)data;
+#endif
 	struct tcb *cmd, *temp;
 	LIST_HEAD(cmds_to_retry);
 	const int MAX_RETRIES = 5;
@@ -4094,8 +4100,10 @@ wctc4xxp_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
 	

Bug#904840: suggests libicu57 which is not available anymore

[Dmitry Eremin-Solenikov]

Package: libqtcore4
Version: 4:4.8.7+dfsg-17
Severity: normal

libqtcore4 suggests libicu57, which was removed from testing. Please
consider switching to libicu60.

-- 
With best wishes
Dmitry

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

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqtcore4 depends on:
ii  libc6 2.27-5
ii  libgcc1   1:8.1.0-12
ii  libglib2.0-0  2.56.1-2
ii  libstdc++68.1.0-12
ii  qtcore4-l10n  4:4.8.7+dfsg-17
ii  zlib1g1:1.2.11.dfsg-1

libqtcore4 recommends no packages.

Versions of packages libqtcore4 suggests:
ii  libicu57  57.1-9
ii  libthai0  0.1.27-2

-- no debconf information

Bug#401889: [installation-guide] memory requirements for powerpc

[Holger Wansing]

Holger Levsen :
> the following memory requirements for powerpc should be documented in the 
> manual, because booting with too little memory results in strange effects / 
> error messages, which especially people new to powerpc will not understand, 
> and therefor think the installer is broken for there machine.
> 
> d-i: recommended is 48mb, might work with less, but on newworld it sureley 
> doesnt boot with 32mb. (tested with daily cd from 2006-12-04). 64mb is still 
> low-mem.
> 
> d-i: recommended is 128mb. works with 96mb, but partioning is buggy then. (it 
> crashes and comes back, so it's usable, but really not recommended. With 96mb 
> the main partition would "reliably" have no mount point set, with 160 mb this 
> is no problem.)

Since powerpc is no longer a release-arch, and the things are most likely to 
behave different with ppc64el, I would close this bug.


Objections?



-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#286180: [installation-guide] manual could reflect debconf serverity level

[Holger Wansing]

Matt Taggart  wrote:
> Since it is possible to run debian installer at different debconf severity 
> levels (and make versions of d-i that run in those levels by defaults) it 
> would be cool if the debian-installation-manual was structured in such a way 
> that you could build different guides for the different levels. This way a 
> user at less than priority low could follow the install and not be confused 
> by 
> explainations of questions they aren't being asked.
> 
> Ideally there would be a way to tag things in the XML to do this, but if 
> something like that isn't possible then the document _could_ be restructured 
> to separate sections and then have a Makefile sort it all out.
> 
> This would be cool but would probably take some work both initially and 
> on-going as the manual was maintained. Filing at severity wishlist.

Introducing different variants of the manual could also add some irritation
or complexity to users, when they use the wrong variant, and cannot find a
said chapter, or the like.

Given the age of this bug (2004) and the manpower in the team, I would close 
this as wont-fix.

Objections?



-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#858159: [installation-guide] Memory requirements for installing Stretch have increased since Jessie

[John Paul Adrian Glaubitz]

On 07/28/2018 08:02 PM, Holger Wansing wrote:
> Currently we have in the guide for buster:
> 
> Install Type  | RAM (minimum) | RAM (recommended) | Hard Drive
> No desktop| 128 megabytes | 512 megabytes | 2 gigabytes
> With desktop  | 256 megabytes | 1 gigabyte| 10 gigabytes

128 MiB still work fine for me without a desktop, even on slow machines:

root@elgar:~> cat /proc/cpuinfo
CPU:68060
MMU:68060
FPU:68060
Clocking:   49.1MHz
BogoMips:   98.20
Calibration:491008 loops
root@elgar:~> free -h
  totalusedfree  shared  buff/cache   available
Mem:  114Mi21Mi   7.0Mi   1.0Mi85Mi86Mi
Swap: 953Mi   2.0Mi   951Mi
root@elgar:~> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux buster/sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;
root@elgar:~>

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

Bug#904839: bsdmainutils: cal still highlights though -h option is gone

[Aaron Hall]

Package: bsdmainutils
Version: 9.0.12+nmu1
Severity: normal

Dear Maintainer,

The -h option to cal(1) was removed with the rationale (given in
response to bug #867995:

> Yes, but this is by design as the docs say cal is supposed to be
> drop-in compatible to the original cal command.

That's well and good, but then cal should not highlight at all, because
a plain display without other control characters is the traditional
behavior of Unix cal. Because cal still adds highlighting, that
interferes with post-processing its output (which is the why the manpage
says it should be "bit for bit compatible").

Thanks,
Aaron


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.105-aja.1 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.29.2-1+deb9u1
ii  debianutils  4.8.1.1
ii  libbsd0  0.8.3-1
ii  libc62.24-11+deb9u3
ii  libncurses5  6.0+20161126-1+deb9u2
ii  libtinfo56.0+20161126-1+deb9u2

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:6.3.0-4
pn  vacation  
ii  wamerican [wordlist]  7.1-1
ii  whois 5.2.17~deb9u1

-- no debconf information


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.105-aja.1 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bsdmainutils depends on:
ii  bsdutils 1:2.29.2-1+deb9u1
ii  debianutils  4.8.1.1
ii  libbsd0  0.8.3-1
ii  libc62.24-11+deb9u3
ii  libncurses5  6.0+20161126-1+deb9u2
ii  libtinfo56.0+20161126-1+deb9u2

bsdmainutils recommends no packages.

Versions of packages bsdmainutils suggests:
ii  cpp   4:6.3.0-4
pn  vacation  
ii  wamerican [wordlist]  7.1-1
ii  whois 5.2.17~deb9u1

-- no debconf information

Bug#413647: [installation-guide] In Appendix D.3, common problem with Grub

[Holger Wansing]

Vincent Bernat  wrote:

> Each time I install a Debian using Appendix D.3, I run into a problem
> when using grub-install :
> 
> Could not find device for /boot: Not found or not a block device.
> 
> The solution is to use the following command before :
> 
> cat /proc/mounts > /etc/mtab
> 
> Here is the wording :
> 
> You may get this error when executing grub-install:
> 
> Could not find device for /boot: Not found or not a block device.
> 
> In this case, use the following command to solve this issue:
> 
> cat /proc/mounts > /etc/mtab

Since this report is quite old (2007) and procederes have changed heavily
in the meantime (like the use of UUIDs), we can close this report IMO.

Any objections?



-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#858159: [installation-guide] Memory requirements for installing Stretch have increased since Jessie

[Holger Wansing]

David Griffith  wrote:
> Chapter 3.4 of the Installation Guide for Stretch is out of date with 
> regard to RAM requirements.  Through trial and error, I determined the 
> following:
> 
> Install Type  | RAM (minimum) | RAM (recommended) | Hard Drive
> No desktop| 256 megabytes | 1 gigabyte| 2 gigabytes
> With desktop  | 768 megabytes | 1 gigabyte| 10 gigabytes


Currently we have in the guide for buster:

Install Type| RAM (minimum) | RAM (recommended) | Hard Drive
No desktop  | 128 megabytes | 512 megabytes | 2 gigabytes
With desktop| 256 megabytes | 1 gigabyte| 10 gigabytes



Should we increase the values for Buster?
(This is of course a difficult approach, since it does not value, which
architecture, desktop environment etc is used.)



I would propose to go with:

Install Type| RAM (minimum) | RAM (recommended) | Hard Drive
No desktop  | 256 megabytes | 1 gigabyte| 2 gigabytes
With desktop| 768 megabytes | 2 gigabyte| 10 gigabytes



Holger


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#904838: corsix-th: music does not play

[Sebastian Ramacher]

Package: corsix-th
Version: 0.61-1
Severity: normal

corsix-th does not play any music. Anouncements and sound effects work though.
It reports:
| ---
|
| Welcome to CorsixTH v0.61!
|
| ---
|
| This window will display useful information if an error occurs.
|
| ---
|
| An error has occurred!
| Almost anything can be the cause, but the detailed information below can help 
the developers find the source of the error.
| Running: The callback handler.
| A stack trace is included below, and the handler has been disconnected.
| ./Lua/audio.lua:580: Could not load music file 'Sound/Midi/ATLANTIS.XMI' 
(Unrecognized audio format)
| stack traceback:
| [C]: in function 'yield'
| ./Lua/app.lua:909: in function <./Lua/app.lua:904>

The version in stable play music correctly.

Cheers

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (650, 'unstable-debug'), (650, 'buildd-unstable'), (650, 
'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages corsix-th depends on:
ii  corsix-th-data   0.61-1
ii  libavcodec58 7:4.0.2-1
ii  libavformat587:4.0.2-1
ii  libavutil56  7:4.0.2-1
ii  libc62.27-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.2.0-1
ii  liblua5.2-0  5.2.4-1.1+b2
ii  libsdl2-2.0-02.0.8+dfsg1-1
ii  libsdl2-mixer-2.0-0  2.0.2+dfsg1-2
ii  libstdc++6   8.2.0-1
ii  libswresample3   7:4.0.2-1
ii  libswscale5  7:4.0.2-1
ii  lua-filesystem   1.6.3-1
ii  lua-lpeg 1.0.0-2

Versions of packages corsix-th recommends:
ii  game-data-packager  59

corsix-th suggests no packages.

-- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#685706: libc-bin: order of /etc/ld.so.conf.d/*.conf

[Alexander Huynh]

We've hit this issue recently when building software packages for multiple
architectures.

I believe the general consensus is we should order things, but another
point to discuss is the specific ordering Debian should use.

IOhannes' example lists libc.conf earlier in the ordering, putting
/usr/local/lib before /usr/lib/$(uname -m)-linux-gnu.

My colleagues and I agree that this is preferred for us, since this enables
the local administrator to effectively overwrite system-defined libraries,
if they so choose.

Thoughts?

Thanks,

– Alex

Bug#515917: hplip-data: [INTL:sv] Swedish translation for HPLIP

[Brian Potkin]

Thank you for your report, Daniel.


On Wed 18 Feb 2009 at 12:56:18 +0100, Daniel Nylander wrote:

> Package: hplip-data
> Severity: wishlist
> Tags: l10n patch
> 
> Here is the Swedish translation for HPLIP 2.8,7.
> Please include in package.
> 
> The patch has also been sent to upstream, without any ACK though.
> 
> https://bugs.launchpad.net/hplip/+bug/270684

After no resonse in nearly ten years, my guess would be that the
Printing Team does not wish to take responsibility for carrying a
patch to hplip-data indefinitely. Upstream have their own reasons
for not adopting it, which you could pursue further in LP #270684.

Closing. Sorry it didn't work out for you.

Regards,

Brian.

Bug#904837: util-linux: su manpage is missing

[Sven Joachim]

Package: util-linux
Version: 2.32-0.2

The latest version of util-linux has taken over the su command from the
login package, but not its manpage:

,
| $ LANG=C man su
| No manual entry for su
| See 'man 7 undocumented' for help when manual pages are not available.
`


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

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

Versions of packages util-linux depends on:
ii  fdisk  2.32-0.2
ii  libaudit1  1:2.8.3-1+b1
ii  libblkid1  2.32-0.2
ii  libc6  2.27-5
ii  libmount1  2.32-0.2
ii  libpam0g   1.1.8-3.7
ii  libselinux12.8-1+b1
ii  libsmartcols1  2.32-0.2
ii  libsystemd0239-7
ii  libtinfo6  6.1+20180714-1
ii  libudev1   239-7
ii  libuuid1   2.32-0.2
ii  login  1:4.5-1.1
ii  zlib1g 1:1.2.11.dfsg-1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.1-2
ii  kbd 2.0.4-3
ii  util-linux-locales  2.32-0.2

-- no debconf information

Bug#863246: hplip-data: removing hplip-data does not clean up some of its directories

[Brian Potkin]

Thank you for your report, Vincent.


On Wed 24 May 2017 at 12:55:51 +0200, Vincent Lefevre wrote:

> Package: hplip-data
> Version: 3.16.11+repack0-3
> Severity: minor
> 
> When I removed hplip-data, I got:
> 
> Removing hplip-data (3.16.11+repack0-3) ...
> dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/ui5' 
> not empty so not removed
> dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/scan' 
> not empty so not removed
> dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/prnt' 
> not empty so not removed
> dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/pcard' 
> not empty so not removed
> dpkg: warning: while removing hplip-data, directory 
> '/usr/share/hplip/installer' not empty so not removed
> dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/fax' 
> not empty so not removed
> dpkg: warning: while removing hplip-data, directory '/usr/share/hplip/copier' 
> not empty so not removed
> dpkg: warning: while removing hplip-data, directory 
> '/usr/share/hplip/base/pexpect' not empty so not removed
> 
> But for instance, /usr/share/hplip/ui5 contains only an empty
> directory __pycache__ that doesn't belong to any package and
> should have been removed in the process.

This unstable machine has nothing related to any hplip package on it. I
have just installed hplip-data 3.17.10+repack0-5.

 root@test:~# ls -l /usr/share/hplip/ui5/ | wc -l
 71

This includes __pycache__, which is generated at install time.

After purging hplip-data:

 root@test:~# ls -l /usr/share/hplip/
 ls: cannot access '/usr/share/hplip/': No such file or directory

Am I missing some nuance in your report?

Regards,

Brian.

Bug#615646: [installation-guide] How do I know which CD has the package I need?

[Holger Wansing]

Robert Cymbala  wrote:
> QUESTION:  
>I burned the first fifteen (15) CD's and GNU/Emacs, which I want to 
> install, 
>is not on them.  How do I find out which CDs I need to burn? (There are 37 
>more in cdimage.debian.org/debian-cd/6.0.0/i386/iso-cd/ and I used to burn 
>all the CDs for a release but am too lazy to burn all 52 discs this time, 
>I only burnt the first 15.)

Time has changed, we don't provide that big sets of CD images anymore. 
So the above question is no longer that important.

However, I would like to add something like the following to chapter 4.1
(https://d-i.debian.org/manual/en.amd64/ch04s01.html):



diff --git a/en/install-methods/official-cdrom.xml 
b/en/install-methods/official-cdrom.xml
index 512011690..f1f12554d 100644
--- a/en/install-methods/official-cdrom.xml
+++ b/en/install-methods/official-cdrom.xml
@@ -30,6 +30,12 @@ the installation to download the remaining files or 
additional CDs.
 
 
 
+Also, keep in mind: if the CD(s) you are using doesn't contain some packages
+you need, you can always install that packages afterwards from your running
+new Debian system (after the installation has finished).
+
+
+
 If your machine doesn't support CD booting (only relevant
 on very old PC systems), but you do have a CD set,
 you can use an alternative strategy such as




-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#904836: cyvcf2: FTBFS in sid

[Santiago Vila]

Package: src:cyvcf2
Version: 0.10.0+git20180727-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build

[... snipped ...]

cyvcf2/cyvcf2.c: In function '__pyx_pf_6cyvcf2_6cyvcf2_6Writer_4write_record':
cyvcf2/cyvcf2.c:40497:60: warning: passing argument 1 of 'bcf_hdr_add_hrec' 
discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
 __pyx_t_1 = ((bcf_hdr_add_hrec(__pyx_v_self->__pyx_base.hdr, __pyx_v_h) < 
0) != 0);
^~~~
In file included from cyvcf2/helpers.h:1,
 from cyvcf2/cyvcf2.c:571:
htslib/htslib/vcf.h:482:37: note: expected 'bcf_hdr_t *' {aka 'struct 
 *'} but argument is of type 'const bcf_hdr_t *' {aka 'const struct 
 *'}
 int bcf_hdr_add_hrec(bcf_hdr_t *hdr, bcf_hrec_t *hrec);
  ~~~^~~
cyvcf2/cyvcf2.c:40535:49: warning: passing argument 1 of 'bcf_hdr_sync' 
discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
 (void)(bcf_hdr_sync(__pyx_v_self->__pyx_base.hdr));
 ^~~~
In file included from cyvcf2/helpers.h:1,
 from cyvcf2/cyvcf2.c:571:
htslib/htslib/vcf.h:479:33: note: expected 'bcf_hdr_t *' {aka 'struct 
 *'} but argument is of type 'const bcf_hdr_t *' {aka 'const struct 
 *'}
 int bcf_hdr_sync(bcf_hdr_t *h);
  ~~~^
cyvcf2/cyvcf2.c:40594:100: warning: passing argument 2 of 'bcf_write' discards 
'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
   __pyx_t_2 = __Pyx_PyInt_From_int(bcf_write(__pyx_v_self->__pyx_base.hts, 
__pyx_v_self->__pyx_base.hdr, __pyx_v_var->b)); if (unlikely(!__pyx_t_2)) 
__PYX_ERR(0, 2073, __pyx_L1_error)

^~~~
In file included from cyvcf2/helpers.h:1,
 from cyvcf2/cyvcf2.c:571:
htslib/htslib/vcf.h:370:43: note: expected 'bcf_hdr_t *' {aka 'struct 
 *'} but argument is of type 'const bcf_hdr_t *' {aka 'const struct 
 *'}
 int bcf_write(htsFile *fp, bcf_hdr_t *h, bcf1_t *v);
~~~^
At top level:
cyvcf2/cyvcf2.c:6771:18: warning: '__pyx_f_6cyvcf2_6cyvcf2_xstr' defined but 
not used [-Wunused-function]
 static PyObject *__pyx_f_6cyvcf2_6cyvcf2_xstr(PyObject *__pyx_v_s) {
  ^~~~
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 
-fdebug-prefix-map=/<>/cyvcf2-0.10.0+git20180727=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -Ihtslib -Icyvcf2 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c htslib/hfile_s3.c -o build/temp.linux-amd64-2.7/htslib/hfile_s3.o
In file included from htslib/hfile_internal.h:32,
 from htslib/hfile_s3.c:33:
htslib/textutils_internal.h:68:1: warning: function declaration isn't a 
prototype [-Wstrict-prototypes]
 hts_json_token * hts_json_alloc_token();
 ^~
In file included from htslib/htslib/hts.h:35,
 from htslib/hfile_s3.c:37:
htslib/htslib/hts_log.h:52:6: warning: function declaration isn't a prototype 
[-Wstrict-prototypes]
 enum htsLogLevel hts_get_log_level();
  ^~~
htslib/hfile_s3.c:69:10: fatal error: openssl/hmac.h: No such file or directory
 #include 
  ^~~~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:9: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Seems like a missing build-depends somewhere.

There are also build failures here:

https://buildd.debian.org/status/package.php?p=cyvcf2

Thanks.

Bug#904217: debmake: typos in man page

[Osamu Aoki]

Hi,

Let me explain how manpage is created.

asciidoc/manpage.txt in debmake-doc is the base text.  and is written in
asciidoc.

It is converted to XML and used within debmake-doc.

manpage is generated by a2x --doctype manpage .. (See asciidoc/Makefile.

So the nroff/troff formatting is really not under my control.

On Sat, Jul 21, 2018 at 12:54:21PM -0700, Paul Hardy wrote:
> Package: debmake
> Version: 4.3.0
> Severity: minor
> Tags: patch
> 
> Here are patches for the debmake man page.  These could also be
> applied to the debmake man page that appears at the end of the "Guide
> for Debian Maintainers" document and to the description of the
> "-x[0-4]" flags in the main body of that guide.
> 
> The first change is "program to make the Debian source package" -->
> "program to make a Debian source package"; it can also be changed in
> the Description field in debian/control.
> 
> It looks like this man page might have been created from Docbook.  If
> so, I do not know how to apply the typographic changes to Docbook
> source, but I will describe them below.
> 
> Ellipses (three periods in a row) look better in troff/groff typeset
> output if there is more space between each period than ordinarily
> surrounds a period.  In nroff/troff, the traditional way of
> accomplishing this has been to put a "thick space" between the periods
> by typing "\|.\|.\|." instead of "...".  I made those changes.

For this, I think use of a UTF-8 ellipses character … may be good idea.
Let me think ...

> There were also instances of "\&.\&.\&.".  If what was intended was a
> thin space, that would be "\^" and not "\&".  "\&" can do weird things
> with alignment if you don't know how to use it, and it appeared
> throughout the file.  The file seems to have been generated by a
> Docbook style sheet, so there might be a bug in whatever style sheet
> was used.
> 
> In nroff, if in the middle of a line you temporarily switch to a
> different font style and then switch back to what you were using, it
> is preferable to use the "\fP" markup to return to the previous font
> style ("P" is for "previous", as in the previous font style).  For
> example, you can change "\fB-x0\fR" to "\fB-x0\fP".  See where I did
> that as I mention in the next paragraph...

Yah but I don't want to manually adjust it.

> The "-x[0-4]" options had ",," (two commas) to represent a quote mark,
> to mean that everything in the preceding line applied.  The symbol for
> a quote is locale-dependent though.  For example, in the U.S. we would
> use '' instead of ,,.  I added "same as \fB-x[0-3]\fP"... to avoid the
> whole quote/locale issue (you can look at the result to see what I
> did.

I am a bit confused here.  You mean to read English under the German locale.
For build, let's force C.UTF-8 as locale.

Anyway, I follow rule written in asciidoc/debmake-doc.txt.

> For the "-y" option, where you say doubled option = "force no", does
> that mean "-y -y" will force a "no" response?  That was the one part I
> wasn't sure about.

Yes.  It's in toggle mode.

> In the CAVEAT section, it says: "You must remove or edit such comment
> lines...".  I changed that to "You should remove or edit such comment
> lines..." because I think "must" would imply a policy violation.
> "Should" implies a recommendation.  If it truly is a policy violation,
> then I need to remove or edit the comments in my debian/watch files.
> :-)
> 
> You might want to change the copyright from "2014-2015" to
> "2014-2018", but I didn't change that in case "2014-2018" is what you
> intended.
> 
> I am also attaching the PDFs, so you can see the before and after
> results.  I created them with, for example:
> 
>  groff debmake.1 > debmake.1.ps
>  ps2pdf debmake.1.ps
> 
> Please let me know if you have any questions or comments.

Anyway, let me check your patch in detail.

Thanks

Osamu
> -debmake \- program to make the Debian source package
> +debmake \- program to make a Debian source package

Yes.

 
>  .SH "SYNOPSIS"
>  .SH "DESCRIPTION"
>  .sp
> -\fBdebmake\fR helps to build the Debian package from the upstream source\&. 
> Normally, this is done as follows:
> +\fBdebmake\fR helps to build a Debian package from the upstream source\&. 
> Normally, this is done as follows:

YES.

> -It is untared to create many files under the
> +It is untarred to create many files under the

Yes.

>  \fIpackage\-version/\fR
>  directory\&.
>  .RE
> @@ -72,7 +72,7 @@
>  .\}
>  debmake is invoked in the
>  \fIpackage\-version/\fR
> -directory possibly without any arguments\&.
> +directory, possibly without any arguments\&.

Yes.

>  make a native Debian source package without
> -\fB\&.orig\&.tar\&.gz\fR\&. This makes the \(lq\fB3\&.0 (native)\fR\(rq 
> format package\&.
> +\fB\&.orig\&.tar\&.gz\fR\&. This makes a \(lq\fB3\&.0 (native)\fR\(rq format 
> package\&.

Yes.

>  .sp
> -If you are thinking to package a Debian specific source tree with
> -\fBdebian/\fR* in it into a native Debian package, please 

Bug#759428: [installation-guide] non-US is no longer existing, so there is also no "export-restricted" software

[Holger Wansing]

Holger Wansing  wrote:
> in http://d-i.debian.org/manual/en.i386/ch08s03.html
> the manual mentions "export-restricted packages" (in reference to
> contrib and non-free). This is a left-over from non-US I think.
> Should be changed just into "restricted".
> 
[...]
> 
> Index: en/post-install/orientation.xml
> ===
> --- en/post-install/orientation.xml   (Revision 69270)
> +++ en/post-install/orientation.xml   (Arbeitskopie)
> @@ -61,7 +61,7 @@
>  One of the best installation methods is apt. You can use the command
>  line version apt-get or full-screen text version
>  aptitude.  Note apt will also let you merge
> -main, contrib, and non-free so you can have export-restricted packages
> +main, contrib, and non-free so you can have restricted packages
>  as well as standard versions.

I would like to commit this, if noone proofs me wrong here.


Holger

-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#904835: ITP: r-cran-ranger -- Fast Implementation of Random Forests

[Dylan Aïssi]

Package: wnpp
Severity: wishlist
Owner: Debian R Packages Maintainers 

Package name: r-cran-ranger
URL: https://cran.r-project.org/package=ranger
License: GPL-3+
Description: Fast Implementation of Random Forests
 A fast implementation of Random Forests, particularly suited for high
 dimensional data. Ensembles of classification, regression, survival and
 probability prediction trees are supported. Data from genome-wide association
 studies can be analyzed efficiently. In addition to data frames, datasets of
 class 'gwaa.data' (R package 'GenABEL') and 'dgCMatrix' (R package 'Matrix')
 can be directly analyzed.

The package will be maintained by the Debian R Packages Team at:
https://salsa.debian.org/r-pkg-team/r-cran-ranger.git