Bug#872601: flash-kernel: Patch for Raspberry Pi 2 support

[Petter Reinholdtsen]

Package: flash-kernel
Severity: wishlist
Tags: patch
X-Debbugs-CC: Sjoerd Simons 

Dear Maintainer,

Please consider the attached patch which adds support for Raspberry Pi
2 Model B.

The patch was lifted from
https://repositories.collabora.co.uk/debian/pool/rpi2/f/flash-kernel/ >
found via the blog post on
http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/ >
linked to from https://wiki.debian.org/RaspberryPi2 >.

With the patched version of flash-kernel, apt is able to install a new
kernel as it should.

diff -ur flash-kernel-3.35/db/all.db flash-kernel-3.35.co1/db/all.db
--- flash-kernel-3.35/db/all.db 2015-04-06 22:19:51.0 +
+++ flash-kernel-3.35.co1/db/all.db 2015-04-26 18:47:54.0 +
@@ -594,6 +594,11 @@
 Mtd-Initrd: ramdisk
 Bootloader-Sets-Incorrect-Root: yes
 
+Machine: Raspberry pi 2 Model B
+Machine: BCM2709
+Kernel-Flavors: rpi2
+Boot-Kernel-Path: /boot/firmware/kernel7.img
+
 Machine: TI AM335x BeagleBone
 Machine: TI AM335x BeagleBone Black
 Kernel-Flavors: armmp
diff -ur flash-kernel-3.35/debian/changelog 
flash-kernel-3.35.co1/debian/changelog
--- flash-kernel-3.35/debian/changelog  2015-04-06 22:33:25.0 +
+++ flash-kernel-3.35.co1/debian/changelog  2015-04-26 18:46:42.0 
+
@@ -1,3 +1,9 @@
+flash-kernel (3.35.co1) rpi2; urgency=medium
+
+  * Add support for Raspberry pi 2 Model B
+
+ -- Sjoerd Simons   Sun, 26 Apr 2015 20:45:52 
+0200
+
 flash-kernel (3.35) unstable; urgency=medium
 
   * Team upload.

-- 
Happy hacking
Petter Reinholdtsen

Bug#869931: Fixed: Re: Bug#869931: (Retrying Login to lxde fails)

[David Lawyer]

The problem is fixed.  I found some very old .x.. configuration files in my
home directory and root directory.  They said to use icewm which is in
conflict with the lxde/lightdm setup I'm now using.  I removed them and
the problem is gone.

David Lawyer

Bug#872600: RFP: open-rpi-firmware -- Open source VPU side bootloader for Raspberry Pi

[Petter Reinholdtsen]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: pkg-raspi 

* Package name: open-rpi-firmware
  Version : n/a, no tags in git
  Upstream Author : Kristina Brooks
* URL : https://github.com/christinaa/rpi-open-firmware
* License : BSD and GPL
  Description : Open source VPU side bootloader for Raspberry Pi

This package contains firmware to boot the various Raspberry Pi boards.

The free firmware is fairly early in its development process, but it
would be useful to have it in Debian to ensure all the build tools
needed are working and to allow those of us that prefer to run into free
software on our units an option to boot our RPis. :)

Not quite sure what the package name should be.  Suggested the
-firmware name to match the
https://tracker.debian.org/pkg/raspi3-firmware > name structure.

-- 
Happy hacking
Petter Reinholdtsen

Bug#872599: lua-cjson: no lua5.3 package

[daurnimator]

Package: lua-cjson
Severity: important

Dear Maintainer,

The lua-cjson package is missing a lua 5.3 version (it only contains 5.1 and 
5.2)

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

Kernel: Linux 4.12.8-1-ARCH (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages lua-cjson depends on:
ii  libc6  2.24-11+deb9u1
ii  multiarch-support  2.24-11+deb9u1

lua-cjson recommends no packages.

lua-cjson suggests no packages.

Bug#870185: armel/marvell kernel size

[Roger Shimizu]

On Mon, Jul 31, 2017 at 11:43 PM, Roger Shimizu  wrote:
> On Mon, Jul 31, 2017 at 3:05 AM, Roger Shimizu  wrote:
>>
>> While I'm still working on this, but I find the latest kernel in
>> archive, 4.11.11-1+b1, fails to boot on my kirkwood based Linkstation.
>> I tried netconsole, but don't get any log. (netconsole outputs fine on
>> working kernels, such as 4.9 and 4.10 series.)
>> And I trace to latest working kernel is 4.10.7-1~exp1.
>>
>> 4.11-1_exp[12] FTBFS on armel, and 4.11.3-1_exp1 doesn't boot.
>>
>> I checked d-kernel and d-arm list, but didn't find similar issue.
>> Do you have any clue on this? Thanks!
>
> I think my problem is very likely the same as:
>  - https://bugs.debian.org/870185
>
> And I tried Ben's recommendation to make armel kernel smaller,
> which I pushed to branch rosh/strip_armel on alioth, confirmed it worked
> well for 4.10.7-1~exp1 (by cherry-pick) on my kirkwood based Linkstation.

I find some new clue about kernel size issue for armel.
vmlinuz installed under /boot is compressed. It can be decompressed by
"scripts/extract-vmlinux" script under linux git repo. But for armel,
it need at patch I posted:
 - https://patchwork.kernel.org/patch/8120831/

After I decompress the kernel images, I find the size for 4.11
increased significantly:


$ ~/linux/scripts/extract-vmlinux /boot/vmlinuz-4.9.0-3-marvell >
~/vmlinuz-4.9.0-3-marvell.extracted
$ ~/linux/scripts/extract-vmlinux /boot/vmlinuz-4.10.0-trunk-marvell >
~/vmlinuz-4.10.0-trunk-marvell.extracted
$ ~/linux/scripts/extract-vmlinux /boot/vmlinuz-4.11.0-0.bpo.1-marvell
> ~/vmlinuz-4.11.0-0.bpo.1-marvell.extracted

$ ls -l ~/vmlinuz-*
-rw-r--r-- 1 rosh rosh 5782024 Aug 19 12:35
vmlinuz-4.10.0-trunk-marvell.extracted
-rw-r--r-- 1 rosh rosh 8763712 Aug 19 12:36
vmlinuz-4.11.0-0.bpo.1-marvell.extracted
-rw-r--r-- 1 rosh rosh 5844072 Aug 19 12:35 vmlinuz-4.9.0-3-marvell.extracted


I know for bug #870185, Robert fixed his device by modify uboot
params, but I guess it's still possible to keep uboot params and only
change the boot addresses of kernel/initrd in flash-kernel db file.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#853639: Fix for the regina-normal FTBFS with gcc 7

[Benjamin Burton]

Hi Adrian,

> A fix for the regina-normal FTBFS with gcc 7 is attached.

Having just uploaded the fix that has been sitting on my hard drive while I was 
on holiday all week, I realised that you had also sent in a patch for this 
(which of course is the same one-liner as mine).

Apologies for the duplicated effort, and thanks for looking into this.

- Ben.

Bug#872375: lirc: irrecord segfaults when recording a button

[Alec Leamas]

On Fri, 18 Aug 2017 22:38:15 +0200 Gianfranco Costamagna 
 wrote:

> Hello,
>
> > Dear Maintainer,
> >
> > When trying to create a configuration file for my remote, irrecord
> > crashes when it gets to the 'Now hold down button Xxx' step:
> can you please try 0.10.0 from unstable?
>
> thanks


The usage here actually does not look  sane. We have

> # irrecord -H devinput -f -d /dev/input/event13 /tmp/tmp.conf

According to the sources, when presented with the devinput driver 
irrecord displays a message like this:


"Usually you should not create a new config file for devinput\n"
"devices. LIRC is installed with a devinput.lircd.conf file 
which \n"

"is built for the current system which works with all remotes \n"
"supported by the kernel. There might be a need to update \n"
"this file so it matches the current kernel. For this, use the \n"
"lirc-make-devinput(1) script.";

Perhaps you missed this message, irrecord does indeed spit out a lot of 
text. That said, this usecase is not really supported.


OTOH, a segfault is never acceptable. Filed upstream bug [1]


Cheers!

--alec

[1] https://sourceforge.net/p/lirc/tickets/299/

Bug#872597: cowbuilder: umask 027 leads to an unreadable /.ilist file and Unknown error executing apt-key

[Paul Wise]

Package: cowbuilder
Version: 0.85
Severity: normal
Usertags: umask

I semi-recently started getting this error from my D10-apt-update hook:

W: Failed to fetch http://deb.debian.org/debian/dists/sid/InRelease
Unknown error executing apt-key

The cause is that the /.ilist file is unreadable for some reason:

29142 open("/.ilist", O_RDONLY) = -1 EACCES (Permission denied)

The permissions on the file are like this with pdebuild:

-rw-r- 1 root root 217984 Aug  6 13:37 /.ilist

With --login they are like this:

-rw-r--r-- 1 root root 217888 Aug  6 13:40 /.ilist

There are two fixes for this:

Switch umask from 027 to 022 (I prefer not to do that).

Add a pbuilder D hook to run `chmod a+r /.ilist`

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages cowbuilder depends on:
ii  cowdancer0.85
ii  libc62.24-12
ii  libncurses5  6.0+20170715-2
ii  libtinfo56.0+20170715-2
ii  pbuilder 0.228.7

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#872586: drumgizmo: FTBFS on several arches because of test failures

[James Cowgill]

Hi,

On 18/08/17 21:32, Jeremy Bicha wrote:
> Source: drumgizmo
> Version: 0.9.14-2
> Severity: serious
> 
> drumgizmo fails to build from source on several release architectures
> that it used to build on because of test failures.
> 
> https://buildd.debian.org/status/package.php?p=drumgizmo

The attached patch does not fix all the test failures, but does fix the
3 affecting mips, and this should be enough to fix armel and mipsel as
well. Things are still broken on mips64el and s390x after this.

src/atomic.h:
This fixes enginetest by removing the assertion. My guess is that the
writer of the code meant to say "does this atomic use the std::atomic
implementation" (as opposed to the other implementation in src/atomic.h)
but instead said "is this atomic lock free" assuming that all
std::atomics are always lock free...

test/atomictest.cc:
Fixes atomictest by removing the test for lock free atomics. One some
architectures isLockFree may legitimately return false (eg it is
impossible to make atomic lock free on 32-bit mips). The test
was probably added with the same assumption as above.

plugingui/image.cc:
Fixes imagecachetest. The original code was not big-endian safe. Replace
the memcpy with shifts and ORs.

Thanks,
James
--- a/src/atomic.h
+++ b/src/atomic.h
@@ -151,8 +151,6 @@ public:
 	SettingRef(Atomic& value)
 		: value(value)
 	{
-		// string isn't lock free either
-		assert((std::is_same::value || value.is_lock_free()));
 	}
 
 	bool hasChanged()
--- a/test/atomictest.cc
+++ b/test/atomictest.cc
@@ -40,7 +40,6 @@ class AtomicTest
 	CPPUNIT_TEST(nonPodAtomicCanBeValueInitialized);
 	CPPUNIT_TEST(podAtomicCanBeValueAssigned);
 	CPPUNIT_TEST(nonPodAtomicCanBeValueAssigned);
-	CPPUNIT_TEST(podAtomicsAreLockFree);
 	CPPUNIT_TEST_SUITE_END();
 	
 	public:
@@ -99,23 +98,6 @@ class AtomicTest
 			CPPUNIT_ASSERT_EQUAL(s.load(), std::string{"hello world"});
 		}
 		
-		void podAtomicsAreLockFree() {
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			CPPUNIT_ASSERT(isLockFree());
-			
-			// compile error: undefined reference to `__atomic_is_lock_free'
-			//CPPUNIT_ASSERT(isLockFree());
-		}
-		
 		// todo: further testing
 		
 	private:
@@ -123,12 +105,6 @@ class AtomicTest
 		bool isUsingStandardImpl() {
 			return std::is_base_of::value;
 		}
-		
-		template 
-		bool isLockFree() {
-			Atomic a;
-			return a.is_lock_free();
-		}
 };
 
 // Registers the fixture into the 'registry'
--- a/plugingui/image.cc
+++ b/plugingui/image.cc
@@ -86,10 +86,16 @@ void Image::setError()
 
 	std::uint32_t iw, ih;
 
-	std::memcpy(, ptr, sizeof(uint32_t));
+	iw = (uint32_t) ptr[0] |
+	 (uint32_t) ptr[1] << 8 |
+	 (uint32_t) ptr[2] << 16 |
+	 (uint32_t) ptr[3] << 24;
 	ptr += sizeof(uint32_t);
 
-	std::memcpy(, ptr, sizeof(uint32_t));
+	ih = (uint32_t) ptr[0] |
+	 (uint32_t) ptr[1] << 8 |
+	 (uint32_t) ptr[2] << 16 |
+	 (uint32_t) ptr[3] << 24;
 	ptr += sizeof(uint32_t);
 
 	_width = iw;


signature.asc
Description: OpenPGP digital signature

Bug#872596: confclerk: infinite loop of error dialogs with DebConf17: UNCAUGHT OrmException: No object exception

[Paul Wise]

Package: confclerk
Version: 0.6.2-1
Severity: normal

When loading the DebConf17 schedule, switching to Saturday 2017-08-12,
expanding the 16:15 - 18:50 slot and scrolling down to the blank entry,
 confclerk pops up an Error dialog that gives the error message
"UNCAUGHT OrmException: No object exception". This is accompanied by
100% CPU usage. Clicking on the OK button just leads to further dialogs.
There are also some console messages listed below.

https://debconf17.debconf.org/schedule/pentabarf.xml

$ confclerk 
No room found for event id:  0 
OrmException: "No object exception" 
No room found for event id:  0 
No room found for event id:  0 
QPainter::end: Painter ended with 2 saved states
No room found for event id:  0 
QPainter::end: Painter ended with 2 saved states
No room found for event id:  0 
QPainter::end: Painter ended with 2 saved states
No room found for event id:  0 
QPainter::end: Painter ended with 2 saved states
No room found for event id:  0 
QPainter::end: Painter ended with 2 saved states
No room found for event id:  0 
QPainter::end: Painter ended with 2 saved states

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages confclerk depends on:
ii  libc6  2.24-12
ii  libgcc11:7.1.0-10
ii  libqt4-network 4:4.8.7+dfsg-11
ii  libqt4-sql 4:4.8.7+dfsg-11
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-11
ii  libqt4-xml 4:4.8.7+dfsg-11
ii  libqtcore4 4:4.8.7+dfsg-11
ii  libqtgui4  4:4.8.7+dfsg-11
ii  libstdc++6 7.1.0-10

confclerk recommends no packages.

confclerk suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#861174: importmagic

[Diane Trout]

Hi,

I packaged importmagic and it's in new right now.
https://ftp-master.debian.org/new/importmagic_0.1.7-1.html

Though following current policy I default to only building the Python 3
version.

Diane

Bug#872523: RE:Bug#872523: fatal: refusing to merge unrelated histories

[Sean Whitton]

On Fri, Aug 18 2017, PICCA Frederic-Emmanuel wrote:

> ] ++ if v >= [2,9]
> then [ "--allow-unrelated-histories" ]
> else []
> [...]
> Yes here

Okay.  I think that this is a bug, but I don't know how to reproduce it
yet.

Do you have an upstream remote pointing to Joey's repository?

Please run propellor with PROPELLOR_DEBUG=1 so we can see the commands
it runs to set up the upstream/master branch.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#872595: calibre: please use system libmspack instead of embedded copy

[duck]

Source: calibre
Version: 3.4.0+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-CC: t...@security.debian.org


Quack,

Sorry for the bad news, but Calibre embed a very old version of 
libmspack to build a plugin: /usr/lib/calibre/calibre/plugins/lzx.so


Unfortunately, this library had a few security issues over time, and 
recently:

  https://security-tracker.debian.org/tracker/source-package/libmspack

So this means Calibre is affected (all versions is Debian) by these two 
security bugs and probably other older ones. The proper solution would 
be to use the libmspack library which has been fixed with all the fixes 
backported to stable and oldstable.


It is defined in 'setup/extensions.json' but I have no idea how to make 
it use the system library so I have no patch to suggest.


Btw it seems 'src/calibre/utils/' contains a lot of borrowed code which 
might lead to security problems too, so I would suggest to have a look 
and work things out with upstream to at least have build flags to use 
system libraries when available.


Regards.

--
Marc Dequènes

Bug#813431: python-numpy: Debian adds include dir symlinks that break virtualenvs

[Pauli Virtanen]

Hi,

Ping --- any news on this front?

The symlinks added by Debian still break installing old numpy versions
and packages depending on them in virtualenvs. These symlinks are not
necessary, because Python packages obtain the appropriate include paths
via `numpy.get_include()`.

-- 
Pauli Virtanen

Bug#872512: patchutils

[dann frazier]

Note that this also allows patchutils to be dropped as a build dependency.

Bug#872594: clamav: please use system libmspack instead of embedded copy

[duck]

Source: clamav
Version: 0.99.3~beta1+dfsg-1
Severity: important


Quack,

I can see there was some work to use the library instead of the embedded 
code, and that upstream even added the changes, which is nice, 
unfortunately the resulting packages do not depend on it.


I think the missing piece would be to use the --with-system-libmspack 
configure flag.


\_o<

--
Marc Dequènes

Bug#872593: Build-Dep on libunwind-dev instead of libunwind8-dev

[dann frazier]

Source: google-perftools
Version: 2.5-2.2
Tags: patch

libunwind8-dev is now just a transitional package for libunwind-dev.

--- google-perftools-2.5.orig/debian/control2017-08-18 16:45:03.0 
-0600
+++ google-perftools-2.5/debian/control 2017-08-18 16:45:21.773022873 -0600
@@ -2,7 +2,7 @@ Source: google-perftools
 Section: libs
 Priority: optional
 Maintainer: Daigo Moriwaki 
-Build-Depends: cdbs, autoconf, automake, libtool, patchutils, debhelper (>= 
10.2.1), binutils, libunwind8-dev [amd64]
+Build-Depends: cdbs, autoconf, automake, libtool, patchutils, debhelper (>= 
10.2.1), binutils, libunwind-dev [amd64]
 Build-Conflicts: autoconf2.13, automake1.4
 Standards-Version: 3.9.8
 Homepage: https://github.com/gperftools/gperftools

Bug#872194: espeakup: Espeakup fails to start due to libespeak-ng.so.1.1.49 segfault

[Samuel Thibault]

Steven Shiau, on ven. 18 août 2017 12:33:19 +0900, wrote:
> Nothing was changed in /etc/default/espeakup:
> ==
> $ cat /etc/default/espeakup
> # To choose the default voice of the espeakup daemon, define VOICE here.
> # See /usr/lib/*/espeak-data/voices/ for a list of possible voices.
> 
> VOICE=

Ok, try to put "en" here, that should avoid the issue.

Samuel

Bug#872587: debian-policy: please document "Important: yes"

[Adam Borowski]

Control: block 872587 by 872589

On Fri, Aug 18, 2017 at 02:28:22PM -0700, Sean Whitton wrote:
> On Fri, Aug 18 2017, Adam Borowski wrote:
> > Thus, some Policy guidance would be nice.  Is it legal to use "Important:
> > yes" at this moment?
> 
> It wouldn't be up to policy whether it's legal.  We document fields in
> policy once they are already in use in the archive.

src:util-linux just added it on two of its binaries (mount and fdisk), thus
the field can be said to be in use.

> Do you have any idea how long we can expect to wait until dpkg supports
> the field?  I would suggest that we wait until dpkg has defined
> behaviour for the field, as it will make documenting it much easier.  It
> will also allow us to be more confident that there is no serious
> disagreement about the purpose of the field.

Right, let's have dpkg maintainers tell us what they think.

> I couldn't find a bug against dpkg, but if there is one, it should
> probably be set to block this bug.

872587 < 872589, I filed the Policy one first.  Block added.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀-- Genghis Ht'rok'din
⠈⠳⣄ 

Bug#872592: ITP: node-syntax-error -- detect and report syntax errors in source code strings

[Bastien ROUCARIES]

Package: wnpp
Severity: wishlist
Owner: ro...@debian.org
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-syntax-error
  Version : 1.3.0
  Upstream Author : James Halliday  (http://substack.net)
* URL : https://github.com/substack/node-syntax-error
* License : Expat
  Programming Lang: JavaScript
  Description : detect and report syntax errors in source code strings

 This module allow ones to emulate in pure javascript the behavior of
Node.js for detecting   syntax error.
.
This module allow ones to get a friendly error report about exactly
where the syntax error is
in a javascript file.
 .
 Node.js is an event-based server-side JavaScript engine.

Bug#872523: RE:Bug#872523: fatal: refusing to merge unrelated histories

[PICCA Frederic-Emmanuel]

setupUpstreamMaster :: String -> IO ()
setupUpstreamMaster newref = do
changeWorkingDirectory =<< dotPropellor
go =<< catchMaybeIO getoldrev
  where
go Nothing = warnoutofdate False
go (Just oldref) = do
let tmprepo = ".git/propellordisttmp"
let cleantmprepo = void $ catchMaybeIO $ 
removeDirectoryRecursive tmprepo
cleantmprepo
git ["clone", "--quiet", ".", tmprepo]

changeWorkingDirectory tmprepo
git ["fetch", distrepo, "--quiet"]
git ["reset", "--hard", oldref, "--quiet"]
v <- gitVersion
let mergeparams =
[ "merge", newref
, "-s", "recursive"
, "-Xtheirs"
, "--quiet"
, "-m", "merging upstream version"
] ++ if v >= [2,9]
then [ "--allow-unrelated-histories" ]
else []
git mergeparams

void $ fetchUpstreamBranch tmprepo
cleantmprepo
warnoutofdate True

getoldrev = takeWhile (/= '\n')
<$> readProcess "git" ["show-ref", upstreambranch, "--hash"]

git = run "git"
run cmd ps = unlessM (boolSystem cmd (map Param ps)) $
error $ "Failed to run " ++ cmd ++ " " ++ show ps

Yes here

Bug#872591: ipython: quit in ipdb does not immediately exit the debugger

[Brian Murray]

Package: ipython
Version: 5.1.0-3
Severity: normal
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful

Dear Maintainer,

There is an upstream ipdb fix which would be useful to include in the
packaged version of ipdb.

https://github.com/ipython/ipython/pull/10009

A detailed bug report with test case was also filed in Ubuntu and can be
found at http://launchpad.net/bugs/1711741.
The description, from Brian Murray, follows:

Using the following test case I'd expect that entering the quit command the 
code containing the ipdb import would exit immediately. This is not the case 
and the code continues to run. Here's a test case:

#!/usr/bin/python3

word = 'the word'
from ipdb import set_trace; set_trace()
print('bird is %s' % word)

This is the failure:

 $ ./ipdb-test.py
> /tmp/ipdb-test.py(5)()
  1 #!/usr/bin/python3
  2 
  3 word = 'the word'
  4 from ipdb import set_trace; set_trace()
> 5 print('bird is %s' % word)

ipdb> quit
bird is the word

With the fix:

 $ ./ipdb-test.py
> /tmp/ipdb-test.py(5)()
  2 
  3 word = 'the word'
  4 from ipdb import set_trace; set_trace()
> 5 print('bird is %s' % word)

ipdb> quit
Exiting Debugger.

This affects both python3 and python2.7 ipdb in Artful. Package version 5.1.0-3.

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

Kernel: Linux 4.11.0-13-generic (SMP w/4 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)

Bug#872589: dpkg-gencontrol: please allow field "Important: yes"

[Guillem Jover]

Hi!

On Fri, 2017-08-18 at 23:09:08 +0200, Adam Borowski wrote:
> Package: dpkg-dev
> Version: 1.18.24
> Severity: wishlist

> Stretch's versions of all apt frontends other than cupt already support
> "Important: yes" packages, thus it'd be reasonable to allow them in Buster.

We are actually not very happy with the name and were already thinking
about using something else. We've also written down our thoughts on
the matter, as there are still some undecided/undesirable semantics:

  

but as we were on the freeze didn't bring it into a wider audience.
We'll be probably doing that in the coming days.

> However, dpkg-gencontrol currently fails to copy the field into a generated
> package.  If I post-process it with a hack like:
> .
> override_dh_gencontrol:
> dh_gencontrol
> sed -e '2i Important: yes' -i debian/${PACKAGE}/DEBIAN/control
> `
> all is ok.

Just for reference, the proper way to tell dpkg-gencontrol how to
export unknown fields into various outputs is to use the export markers
such as SBC as in «XB-Important: yes», as described in deb-src-control(5).

> It is not documented in the Policy, I've filed #872587 asking for their
> opinion.

I don't think it makes sense to file this kind of bug on policy as
long as there's no support in dpkg, nor a clear plan yet on how to
proceed. :)

Thanks,
Guillem

Bug#872587: debian-policy: please document "Important: yes"

[Sean Whitton]

Hello Adam,

Thank you for filing this bug.

On Fri, Aug 18 2017, Adam Borowski wrote:

> On the other hand, dpkg does not know the field.  It won't say a word upon
> removal, and dpkg-gencontrol silently removes it.
> [...]
> Thus, some Policy guidance would be nice.  Is it legal to use "Important:
> yes" at this moment?

It wouldn't be up to policy whether it's legal.  We document fields in
policy once they are already in use in the archive.

Do you have any idea how long we can expect to wait until dpkg supports
the field?  I would suggest that we wait until dpkg has defined
behaviour for the field, as it will make documenting it much easier.  It
will also allow us to be more confident that there is no serious
disagreement about the purpose of the field.

I couldn't find a bug against dpkg, but if there is one, it should
probably be set to block this bug.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#872590: libisofs6: integer overflow in susp_iter_next()

[Jakub Wilk]

Package: libisofs6
Version: 1.4.6-1

The susp_iter_next() function does the following:

  nblocks = DIV_UP(iter->ce_off + iter->ce_len, BLOCK_SIZE);
  iter->buffer = realloc(iter->buffer, nblocks * BLOCK_SIZE);
  for (block = 0; block < nblocks; ++block) {
  /* ... */
  }
  iter->base = iter->buffer + iter->ce_off;

(I omitted the boring parts.)

An overflow can happen in the computation of nblocks.
For example, in the attached ISO file:
- iter->ce_off is 4294901808;
- iter->ce_len is 65328;
- nblocks is computed as 0;
- iter->base is set to a bogus pointer.

Found using American Fuzzy Lop:
http://lcamtuf.coredump.cx/afl/

--
Jakub Wilk


intoverflow.iso.gz
Description: application/gzip

Bug#872514: devscripts: Please add script to report on reproducibility status of installed packages

[Chris Lamb]

Hi,

> devscripts: Please add script to report on reproducibility status
> of installed packages

Updated patch attached:

  commit ae5eb4b49f6388e4e813a1fb5aef58a291b82ffc
  Author: Chris Lamb 
  Date:   Thu Aug 17 17:07:16 2017 -0700
  
  reproducible-check: New script to report on reproducibility status of 
installed packages.
  
  Signed-off-by: Chris Lamb 
  
   .gitignore |   1 +
   debian/control |   7 ++
   debian/copyright   |   6 ++
   scripts/Makefile   |   7 +-
   scripts/reproducible-check | 185 
+
   scripts/setup.py   |   2 +-
   6 files changed, 205 insertions(+), 3 deletions(-)

Compared to the previous patch, it

  * Lets the cache expire after 1 day
  * Sets a User-Agent
  * Tidies up some variable names, etc.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
>From ae5eb4b49f6388e4e813a1fb5aef58a291b82ffc Mon Sep 17 00:00:00 2001
From: Chris Lamb 
Date: Thu, 17 Aug 2017 17:07:16 -0700
Subject: [PATCH] reproducible-check: New script to report on reproducibility
 status of installed packages.

Signed-off-by: Chris Lamb 
---
 .gitignore |   1 +
 debian/control |   7 ++
 debian/copyright   |   6 ++
 scripts/Makefile   |   7 +-
 scripts/reproducible-check | 185 +
 scripts/setup.py   |   2 +-
 6 files changed, 205 insertions(+), 3 deletions(-)
 create mode 100755 scripts/reproducible-check

diff --git a/.gitignore b/.gitignore
index e96730cd..248fd399 100644
--- a/.gitignore
+++ b/.gitignore
@@ -98,6 +98,7 @@ scripts/origtargz.1
 scripts/plotchangelog
 scripts/pts-subscribe
 scripts/rc-alert
+scripts/reproducible-check.1
 scripts/rmadison
 scripts/rmadison.1
 scripts/sadt.1
diff --git a/debian/control b/debian/control
index 82165b80..6eac2ce5 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Build-Depends: bash-completion,
dpkg-dev (>= 1.17.6),
file,
gnupg | gnupg2,
+   help2man,
libdistro-info-perl,
libdpkg-perl,
libfile-desktopentry-perl,
@@ -29,11 +30,14 @@ Build-Depends: bash-completion,
po4a (>= 0.40),
pylint,
python3-all,
+   python3-apt,
python3-debian (>= 0.1.15),
python3-flake8,
python3-magic,
+   python3-requests,
python3-setuptools,
python3-unidiff ,
+   python3-xdg,
shunit2 (>= 2.1.6),
unzip,
wdiff,
@@ -72,9 +76,12 @@ Recommends: apt,
 man-db,
 patch,
 patchutils,
+python3-apt,
 python3-debian (>= 0.1.15),
 python3-magic,
+python3-requests,
 python3-unidiff,
+python3-xdg,
 sensible-utils,
 strace,
 unzip,
diff --git a/debian/copyright b/debian/copyright
index c22addad..95550dc7 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -68,6 +68,12 @@ Copyright: 2009,  Jonathan Patrick Davies 
2006-2008, Kees Cook 
2007-2008, Siegfried-Angel Gevatter Pujals 
2013,  Rafael Laboissiere 
+License: GPL-3+
+
+Files: scripts/reproducible-check
+Copyright: © 2017 Chris Lamb 
+License: GPL-3+
+
 License: GPL-3+
  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
diff --git a/scripts/Makefile b/scripts/Makefile
index ece5455a..21ed11a6 100644
--- a/scripts/Makefile
+++ b/scripts/Makefile
@@ -24,9 +24,9 @@ COMPLETION = $(patsubst %.bash_completion,$(BC_BUILD_DIR)/%,$(COMPL_FILES))
 COMPL_DIR := $(shell pkg-config --variable=completionsdir bash-completion)
 PKGNAMES:=wnpp-alert wnpp-check mk-build-deps rmadison mass-bug debsnap dd-list build-rdeps who-uploads transition-check getbuildlog dcontrol grep-excuses rc-alert whodepends dget pts-subscribe pts-unsubscribe debcheckout
 # also update the list in setup.py
-PYTHON3_SCRIPTS:=debdiff-apply sadt suspicious-source wrap-and-sort
+PYTHON3_SCRIPTS:=debdiff-apply sadt suspicious-source wrap-and-sort reproducible-check
 
-GEN_MAN1S += debrepro.1 devscripts.1 mk-origtargz.1 uscan.1
+GEN_MAN1S += debrepro.1 devscripts.1 mk-origtargz.1 uscan.1 reproducible-check.1
 
 all: $(SCRIPTS) $(GEN_MAN1S) $(CWRAPPERS) $(COMPLETION)
 
@@ -74,6 +74,9 @@ devscripts.1: devscripts.1.in
 	perl ../debian/genmanpage.pl >> $@.$(PID)
 	mv $@.$(PID) $@
 
+reproducible-check.1: reproducible-check
+	help2man --no-info --no-discard-stderr 

Bug#853715: yrmcds: ftbfs with GCC-7

[Nobuhiro Iwamatsu]

Hi,

> Package: src:yrmcds
> Version: 1.1.8-1
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-7
>
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
> severity of this report may be raised before the buster release.
> There is no need to fix this issue in time for the stretch release.
>
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc7-20170126/yrmcds_1.1.8-1_unstable_gcc7.log
> The last lines of the build log are at the end of this report.
>
> To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.

This problem fixed in upstream repository.
  
https://github.com/cybozu/yrmcds/commit/a7026e02da4fcc6d0260dfa49649446158147015

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

Bug#872523: fatal: refusing to merge unrelated histories

[Sean Whitton]

Hello,

On Fri, Aug 18 2017, PICCA Frederic-Emmanuel wrote:

>>--allow-unrelated-histories
>
> I tryed with this options but Igot this error message.

Yes, I didn't expect this to work.

Sorry that my question wasn't clear.  I need you to look in the
DotDir.hs file in your tree, to see if it contains that string.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#826428: ITA: gcompris-qt -- Educational games for small children - Qt rewrite

[Simon Quigley]

Control: retitle -1 ITA: gcompris-qt -- Educational games for small children - 
Qt rewrite
Control: owner -1 tsimo...@ubuntu.com

I would like to adopt this package.

Bug#872589: dpkg-gencontrol: please allow field "Important: yes"

[Adam Borowski]

Package: dpkg-dev
Version: 1.18.24
Severity: wishlist

Hi!
Stretch's versions of all apt frontends other than cupt already support
"Important: yes" packages, thus it'd be reasonable to allow them in Buster.

However, dpkg-gencontrol currently fails to copy the field into a generated
package.  If I post-process it with a hack like:
.
override_dh_gencontrol:
dh_gencontrol
sed -e '2i Important: yes' -i debian/${PACKAGE}/DEBIAN/control
`
all is ok.

It is not documented in the Policy, I've filed #872587 asking for their
opinion.


If you'd want to test the behaviour of current frontends yourself, you can
use my test packages:

deb http://angband.pl/debian essimp main
(-src, https), key:
wget -qO- https://angband.pl/deb/archive.html|apt-key add -
"test-essential", "test-important"



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

Kernel: Linux 4.13.0-rc5-debug-00121-gc6b5a5fd577f (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages dpkg-dev depends on:
ii  binutils  2.29-4
ii  bzip2 1.0.6-8.1
ii  libdpkg-perl  1.18.24
ii  make  4.1-9.1
ii  patch 2.7.5-1+b2
ii  perl  5.26.0-5
ii  tar   1.29b-2
ii  xz-utils  5.2.2-1.3

Versions of packages dpkg-dev recommends:
ii  build-essential  12.3
ii  clang-4.0 [c-compiler]   1:4.0.1-1
ii  fakeroot 1.22-1
ii  gcc [c-compiler] 4:7.1.0-2
ii  gcc-7 [c-compiler]   7.1.0-13
ii  gnupg2.1.23-2
ii  gpgv 2.1.23-2
ii  libalgorithm-merge-perl  0.08-3
ii  tcc [c-compiler] 0.9.27~git20161217.cd9514ab-3

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2017.05.28

-- no debconf information

Bug#872523: fatal: refusing to merge unrelated histories

[PICCA Frederic-Emmanuel]

Hello Sean

> git changed its behaviour, but there was a fix added to DotDir.hs some
> time ago.  What version are you upgrading from?  Please look in
> DotDir.hs in your repo for the string

my local.propellor repository contained the 3.2.3 version.
Then I upgrade my unstable machine with the latest 4.6.x version you uploaded 
recently.

I did nothing special...

>--allow-unrelated-histories

I tryed with this options but Igot this error message.

picca@mordor:~/.propellor$ LANG=C git merge --allow-unrelated-histories 
upstream/master
Auto-merging stack.yaml
CONFLICT (add/add): Merge conflict in stack.yaml
Auto-merging src/wrapper.hs
CONFLICT (add/add): Merge conflict in src/wrapper.hs
Auto-merging src/Utility/UserInfo.hs
CONFLICT (add/add): Merge conflict in src/Utility/UserInfo.hs
Auto-merging src/Utility/SystemDirectory.hs
CONFLICT (add/add): Merge conflict in src/Utility/SystemDirectory.hs
Auto-merging src/Utility/Scheduled.hs
CONFLICT (add/add): Merge conflict in src/Utility/Scheduled.hs
Auto-merging src/Utility/SafeCommand.hs
CONFLICT (add/add): Merge conflict in src/Utility/SafeCommand.hs
Auto-merging src/Utility/Process.hs
CONFLICT (add/add): Merge conflict in src/Utility/Process.hs
Auto-merging src/Utility/Path.hs
CONFLICT (add/add): Merge conflict in src/Utility/Path.hs
Auto-merging src/Utility/PartialPrelude.hs
CONFLICT (add/add): Merge conflict in src/Utility/PartialPrelude.hs
Auto-merging src/Utility/Misc.hs
CONFLICT (add/add): Merge conflict in src/Utility/Misc.hs
Auto-merging src/Utility/LinuxMkLibs.hs
CONFLICT (add/add): Merge conflict in src/Utility/LinuxMkLibs.hs
Auto-merging src/Utility/FileSystemEncoding.hs
CONFLICT (add/add): Merge conflict in src/Utility/FileSystemEncoding.hs
Auto-merging src/Utility/FileMode.hs
CONFLICT (add/add): Merge conflict in src/Utility/FileMode.hs
Auto-merging src/Utility/Exception.hs
CONFLICT (add/add): Merge conflict in src/Utility/Exception.hs
Auto-merging src/Utility/DataUnits.hs
CONFLICT (add/add): Merge conflict in src/Utility/DataUnits.hs
Auto-merging src/Propellor/Types/ZFS.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/ZFS.hs
Auto-merging src/Propellor/Types/Result.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/Result.hs
Auto-merging src/Propellor/Types/OS.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/OS.hs
Auto-merging src/Propellor/Types/MetaTypes.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/MetaTypes.hs
Auto-merging src/Propellor/Types/Info.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/Info.hs
Auto-merging src/Propellor/Types/Docker.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/Docker.hs
Auto-merging src/Propellor/Types/Dns.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/Dns.hs
Auto-merging src/Propellor/Types/Core.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/Core.hs
Auto-merging src/Propellor/Types/CmdLine.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/CmdLine.hs
Auto-merging src/Propellor/Types/Chroot.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types/Chroot.hs
Auto-merging src/Propellor/Types.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Types.hs
Auto-merging src/Propellor/Ssh.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Ssh.hs
Auto-merging src/Propellor/Spin.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Spin.hs
Auto-merging src/Propellor/Shim.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Shim.hs
Auto-merging src/Propellor/Property/ZFS/Process.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/ZFS/Process.hs
Auto-merging src/Propellor/Property/User.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/User.hs
Auto-merging src/Propellor/Property/Unbound.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Unbound.hs
Auto-merging src/Propellor/Property/Tor.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Tor.hs
Auto-merging src/Propellor/Property/Systemd.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Systemd.hs
Auto-merging src/Propellor/Property/Sudo.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Sudo.hs
Auto-merging src/Propellor/Property/Ssh.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Ssh.hs
Auto-merging src/Propellor/Property/SiteSpecific/JoeySites.hs
CONFLICT (add/add): Merge conflict in 
src/Propellor/Property/SiteSpecific/JoeySites.hs
Auto-merging src/Propellor/Property/SiteSpecific/GitAnnexBuilder.hs
CONFLICT (add/add): Merge conflict in 
src/Propellor/Property/SiteSpecific/GitAnnexBuilder.hs
Auto-merging src/Propellor/Property/Sbuild.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Sbuild.hs
Auto-merging src/Propellor/Property/Rsync.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Rsync.hs
Auto-merging src/Propellor/Property/Reboot.hs
CONFLICT (add/add): Merge conflict in src/Propellor/Property/Reboot.hs
Auto-merging 

Bug#801381: debian-archive-keyring: Depend/Recommend gnupg2 and gpgv2?

[Manuel A. Fernandez Montecelo]

Hi Adam,

2017-08-18 21:59 GMT+02:00 Adam D. Barratt :
>
> I've therefore pushed the removal of the dependencies from the .deb
> package for the next upload. (The udeb has a Recommends on gpgv-udeb,
> but I don't know the installer environment well enough to be happy
> touching that right now.)

Looks like a good solution, thanks!


-- 
Manuel A. Fernandez Montecelo 

Bug#854265: owner

[Bastien ROUCARIES]

control: owner -1 ro...@debian.org

Bug#860141: some progress

[Thomas Lange]

I've managed to create an image (using the FAI 5.4~beta2 version) with 
following change:

--- Volumes.pm  2017-01-04 21:18:01.351924832 +0100
+++ /usr/share/fai/setup-storage/Volumes.pm 2017-08-18 22:51:39.620984379 
+0200
@@ -401,6 +401,7 @@
   use Linux::LVM;
   use Cwd qw(abs_path);
 
+  return;
   # get the existing volume groups
   foreach my $vg (get_volume_group_list()) {
 # initialise the hash entry


So disabling the detection of the current LVM devices helps. Then I
used the name vg8 (instead of vg1) in the disk_config/LVM file.
On the host, where I'm calling fai-diskimage I'm using vg1, so this
should not be used in the disk config. Currently the vg8 is not
cleaned up at the end.

I have to manage to tell setup-storage not to detect the lvm things
when setup-storage is used by fai-diskimage. This is not that easy.

But this test shows, that it's possible, although some cleanup has to
be added.

-- 
regards Thomas

Bug#872588: [libgtk-3-bin] GtkFileChooser: Selected vs non-selected files/folders behave inconsistently on single/double-click, causing accidental selection/navigation

[OmegaPhil]

Package: libgtk-3-bin
Version: 3.22.16-1
Severity: normal

Opening a bug here so that I can track this in Debian.

Since 3.18, the 'click to activate' behaviour of a GtkFileChooser has
been purposefully broken to allow selecting and acting on a
file/directory with one click[0]. This is not normal behaviour, and
frequently gets in my way when I have to use GTK3 programs.

There is a bug upstream, unresolved after a few years[0], which
highlights that Ubuntu has a patch[1] (rather, a hack) to get back to
the correct behaviour. Please can this be considered to be included into
Debian proper (it doesn't look like the maintainers are interested in
fixing it from reading the ticket).

Thanks

0:
https://git.gnome.org/browse/gtk%2B/commit/?id=fb0a13b7f070a14312dafa1e4df6ba03cf33be01
1: https://bugzilla.gnome.org/show_bug.cgi?id=758065
2: https://bugzilla.gnome.org/show_bug.cgi?id=758065#c32


--- System information. ---
Architecture: Kernel:   Linux 4.9.0-3-amd64

Debian Release: stretch/sid
  990 testing 10.1.0.3   500 unstable10.1.0.3   500
quodlibet-unstable lazka.github.io   100 ascii-proposed  10.1.0.3
--- Package information. ---
Depends(Version) | Installed
-+-===
libatk-bridge2.0-0(>= 2.5.3) | 2.22.0-2
libatk1.0-0  (>= 2.15.1) | libc6
  (>= 2.4) | libcairo-gobject2(>= 1.10.0) | libcairo2
(>= 1.14.0) | libepoxy0   (>= 1.0) |
libfontconfig1 (>= 2.11) | libfreetype6
(>= 2.2.1) | libgdk-pixbuf2.0-0   (>= 2.22.0) | libglib2.0-0
(>= 2.49.4) | libgtk-3-0(>= 3.22.16-1) |
libpango-1.0-0   (>= 1.37.3) | libpangocairo-1.0-0
(>= 1.37.3) | libpangoft2-1.0-0(>= 1.37.3) |
libwayland-client0   (>= 1.9.91) | libwayland-cursor0
(>= 1.9.91) | libwayland-egl1-mesa(>= 10.0.2)  |  OR
libwayland-egl1  | libx11-6
   | libxcomposite1  (>= 1:0.3-1) | libxcursor1
 (>> 1.1.2) | libxdamage1   (>= 1:1.1) |
libxext6 | libxfixes3
   | libxi6   | libxinerama1
| libxkbcommon0 (>= 0.5.0) |
libxrandr2   | libgtk-3-common   (>=
3.22.16-1) | gtk-update-icon-cache|

Package's Recommends field is empty.

Package's Suggests field is empty.






signature.asc
Description: OpenPGP digital signature

Bug#865858: neofetch: Starts /usr/games/pacman if package pacman is installed

[Axel Beckert]

Control: reopen -1

Hi Nobuhiro,

Nobuhiro Iwamatsu wrote:
> Package: neofetch
> Version: 2.0.1-1
[...]
> This problem is not reproduced in 3.2.0-1.

I'm sorry to continue to bother you with this, but I can still very
easily reproduce this with 3.2.0-1 in an uptodate Sid installation.

Actually I just ran into it again yesterday, when I compared neofetch,
screenfetch and inxi.

> The fix for this problem is done in 2.0.1-1.

I don't understand that sentence. 2.0.1-1 is a pre-stretch version and
has been replaced long time ago, even long before I ran into that bug.

See also the version graph in the bug tracking system:
https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;info=1;found=neofetch%2F3.2.0-1;collapse=1;fixed=neofetch%2F2.0.1-1;package=neofetch

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#872587: debian-policy: please document "Important: yes"

[Adam Borowski]

Package: debian-policy
Version: 4.0.1.0
Severity: wishlist

Hi!
A couple of packages with "Important: yes" has just hit unstable (mount,
fdisk) -- or rather, _would_ hit unstable had dpkg-gencontrol not silently
ignored this field.

The problem is, this field is currently undocumented and unofficial.

Support in frontends in Stretch looks good enough, thus I believe there's no
reason to avoid using this field in Buster.  I've tested apt, dselect, aptitude,
synaptic, gnome-packagekit, apper -- only nit is messages talking about
"essential", but that's okayish.  There is a frontend that doesn't know this
field, cupt, but with popcon vote 23, the cross-section of people who 1. try
to remove an Important:yes package, 2. use cupt, 3. use Stretch's version
of tools to remove a Buster's package, is expected to be nil.

On the other hand, dpkg does not know the field.  It won't say a word upon
removal, and dpkg-gencontrol silently removes it.  Currently to build such a
package you need a hack like:

override_dh_gencontrol:
dh_gencontrol
sed -e '2i Important: yes' -i debian/${PACKAGE}/DEBIAN/control


Thus, some Policy guidance would be nice.  Is it legal to use "Important:
yes" at this moment?


As far as I know, the intended behaviour is to make a package:
* easy to not install
* hard to remove
Ie, it's meant to protect stuff like "init" or "mount" from being removed,
while not wasting space on a buildd chroot or a container.
Current state of the these packages is:
* mount: Important:yes, Depends: path from both systemd and
  sysvinit-core→initscripts
* init: no protection at all
Thus obviously "init" wants this to be set.


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

Kernel: Linux 4.13.0-rc5-debug-00121-gc6b5a5fd577f (SMP w/6 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

debian-policy depends on no packages.

debian-policy recommends no packages.

Versions of packages debian-policy suggests:
pn  doc-base  

-- no debconf information

Bug#870813: [bug #51666] Please hash the hostname in ~/.wget-hsts files

[Tim Rühsen]

On Freitag, 18. August 2017 14:51:12 CEST Ander Juaristi wrote:
> Follow-up Comment #2, bug #51666 (project wget):
> 
> I'm not generally against these kind of small tweaks that don't harm and
> slightly improve user's privacy.
> 
> If Firefox doesn't do it, we don't care: it's their business and they will
> end up doing it if users request that feature (maybe because they saw it in
> wget).
> 
> Private SSH keys can be protected with a password if you want to.

As long as it is optional...

It would be nice being file compatible with Firefox (at least reading Firefox 
HSTS db).
Maybe the sqlite backend that has been mentioned earlier should then work with 
the same settings (hashed/not hashed).

> We can do both, hash and still keep the readable to the user only. If the
> overhead is not much I would go for it. That is the basis of every security
> framework out there: if the benefits of having 2 security mechanisms instead
> of only 1 outweigh the drawbacks, then implement 2 instead of 1.

Absolutely, but in this special case you open up a can of worms. From a 
security standpoint, the average home directory is a nightmare. Once someone 
gets access to it (read or write)...

Regards, Tim

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

Bug#854501: owner

[Bastien ROUCARIES]

control: owner -1 ro...@debian.org

Bug#870780: Bug#872525: [pkg-gnupg-maint] Bug#872525: debian-archive-keyring FTBFS with gnupg 2.1.23

[Adam D. Barratt]

[CC += 870780]

On Fri, 2017-08-18 at 03:46 -0400, Daniel Kahn Gillmor wrote:
> On Fri 2017-08-18 10:02:49 +0300, Adrian Bunk wrote:
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-archive-keyring.html
> >
> > ...
> > gpg --no-options --no-default-keyring --no-auto-check-trustdb 
> > --trustdb-name ./trustdb.gpg \
> > --keyring keyrings/team-members.gpg --verify \
> > keyrings/debian-archive-keyring.gpg.asc \
> > keyrings/debian-archive-keyring.gpg
> > gpg: Signature made Thu May 25 06:30:03 2017 -12
> > gpg:using RSA key C5CE5DC2C542CD59
> > gpg: BAD signature from "Adam D. Barratt " 
> > [unknown]
[...]
> The difference between the keyrings is the trust packets:
[...]
> This is happening because of a combination of several factors:
> 
> One of them is https://bugs.debian.org/870780 -- the
> debian-archive-keyring really shouldn't have OpenPGP trust packets in it
> in the first place.  Those are deliberately underspecified and
> vendor-specific:
[...]
> The larger problem here is that jetring (and debian-archive-keyring, and
> anything else which uses jetring) seems to assume some things about what
> GnuPG does with the contents of ~/.gnupg.
[...]
> If #870780 was resolved (perhaps by fixing jetring to use GnuPG's
> external interfaces?) and a new debian-archive-keyring.gpg.asc was
> created by Adam (or some other member of the team) then i think this
> problem would go away.

As discussed on IRC, I think the fundamental fix here needs to be in
jetring. In the short term, however, we could resolve the issue in d-a-k
in one of two ways.

1. Have the rules that generate the keyrings clean them afterwards. For
example, changing:

keyrings/debian-archive-keyring.gpg: active-keys/index
jetring-build -I $@ active-keys

to

keyrings/debian-archive-keyring.gpg: active-keys/index
jetring-build -I $@ active-keys
gpg --import-options import-export --import < $@ > $@.tmp
mv -f $@.tmp $@

and similarly for the removed keyring. (and maybe for the trusted.gpg.d
files as well?)

2. Add the manual equivalent of the above to the "pre-build" section of
README.maintainer, leaving the package creating crufty files and the
responsibility of cleaning them up resting with the person generating
the package.

Particularly if we want/need to clean up the trusted.gpg.d files as
well, I'm inclined towards option 1, even if it does mean a small bit of
repetition in the makefile.

Regards,

Adam

Bug#872375: lirc: irrecord segfaults when recording a button

[Gianfranco Costamagna]

Hello,

> Dear Maintainer,
> 
> When trying to create a configuration file for my remote, irrecord
> crashes when it gets to the 'Now hold down button Xxx' step:
can you please try 0.10.0 from unstable?

thanks



signature.asc
Description: OpenPGP digital signature

Bug#872586: drumgizmo: FTBFS on several arches because of test failures

[Jeremy Bicha]

Source: drumgizmo
Version: 0.9.14-2
Severity: serious

drumgizmo fails to build from source on several release architectures
that it used to build on because of test failures.

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

You can do something like the below snippet to ignore test failures on
some architectures but still have them be mandatory for the remaining
architectures.

override_dh_auto_test:
ifneq (,$(findstring
$(DEB_HOST_ARCH),"alpha","armel","hppa","mips","mips64el","powerpc","sparc64","s390x",))
-dh_auto_test
else
dh_auto_test
endif

Thanks,
Jeremy Bicha

Bug#865929: Advice on dealing with GRUB upgrade failure caused by init-select

[Niko Tyni]

On Wed, Aug 16, 2017 at 06:58:32PM +0200, Philip Hands wrote:
> Colin Watson  writes:
> 
> ...
> > If you want to consider this bug closed at this point without a formal
> > resolution, then I'm OK with saving you folks some time, ...
> 
> I think that's fine, so I'm going to just close the bug now.

Fine by me at least, thanks Phil.

Following OdyX's suggestion I'm appending my initial draft for a
resolution that turned out to be unnecessary. Maybe this is helpful
in some way.

Please note that this has not been reviewed by other tech-ctte members
except partly Phil. Any errors (factual or otherwise) are therefore all
mine.

=== Draft resolution ===

The Technical Committee has been asked for advice regarding a GRUB upgrade
failure caused by a configuration file in the init-select package.

The default contents of this configuration file in the current oldstable
distribution (jessie) have a bug that triggers when the init-select
package is removed but not purged. The package has since been removed from
Debian and does not exist in the current stable distribution (stretch)
or in unstable/testing. Normal system upgrades from jessie to stretch
result in the package getting removed due to other dependencies, leading
to an upgrade failure.

While fixing the configuration file in oldstable in a point release would
mitigate the issue, it would leave upgrades straight to current stable
affected. Therefore a fix in a stable point release would be preferrable
(but does not rule out fixing this in oldstable too.)

The fix can go either in the (now obsolete) configuration file, or
GRUB's handling of it. As there is no package left responsible for
cleaning away the configuration file, changes in the GRUB handling
would be needed potentially forever and would therefore cause a long
term maintenance burden.  By contrast, fixing the configuration file is
a one-time operation.

The Committee therefore resolves that:

1. We advise the GRUB maintainer to take over management of the
   offending configuration file.

Actual changes in the configuration file (modifying or removing it)
are not in scope of this resolution and are governed by normal Debian
policies and procedures.

2. Developers who consider this takeover to violate the Debian Policy
   are invited to voice their concerns via the normal policy process so
   that the policy can be amended if necessary.

=== End Draft Resolution ===

The change proposed by Guillem in

 <20170702011536.kux7dnmybmbsv...@gaara.hadrons.org>

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863801#22

to introduce a comment in the configuration file (instead of removing it
straight away) seems sound to me and might have been part of the advice
but we never got as far as discussing that.

-- 
Niko Tyni   nt...@debian.org

Bug#872471: perl FTCBFS: ./generate_uudmap: 1: ./generate_uudmap: Syntax error: "(" unexpected

[Niko Tyni]

Control: tag -1 confirmed

On Thu, Aug 17, 2017 at 07:48:15PM +0200, Helmut Grohne wrote:
> Source: perl
> Version: 5.26.0-5
> Severity: wishlist
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> Hi perl maintainers,
> 
> perl fails to cross build from source:
> 
> | powerpc-linux-gnu-gcc -c -DPERL_CORE -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/build/perl-qTvMce/perl-5.26.0=. -fstack-protector-strong 
> -Wformat -Werror=format-security -fwrapv -fno-strict-aliasing -pipe 
> -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -std=c89 -O2 
> -g -Wall -Werror=declaration-after-statement -Wextra -Wc++-compat 
> -Wwrite-strings generate_uudmap.c
> | powerpc-linux-gnu-gcc -o generate_uudmap -Wl,-z,relro 
> -fstack-protector-strong -L/usr/local/lib generate_uudmap.o -ldl -lm 
> -lpthread -lc -lcrypt 
> | ./generate_uudmap uudmap.h bitcount.h mg_data.h
> | ./generate_uudmap: 1: ./generate_uudmap: Syntax error: "(" unexpected
> | Makefile:320: recipe for target 'bitcount.h' failed
> | make[1]: *** [bitcount.h] Error 2
> | make[1]: Leaving directory '/<>'
> | debian/rules:124: recipe for target 'perl.static' failed
> | make: *** [perl.static] Error 2
> | dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Thanks. I can reproduce this. The intention is to run the build
architecture 'generate_uudmap' binary, which is compiled earlier and
copied aside as build-generate_uudmap. Something goes wrong and the
build system ends up trying to run the host architecture binary instead,
which fails for obvious reasons.

I suspect upstream behaviour changes in the Configure -O (override)
argument handling but will need to dig into it some more.

In sake somebody wants to play with it, my steps in reproducing it in
a chroot (for armhf in this case) were roughly

# dpkg --add-architecture armhf
# apt update
# apt install crossbuild-essential-armhf
# apt -a armhf build-dep perl
$ dpkg-buildpackage -b -aarmhf

-- 
Niko Tyni   nt...@debian.org

Bug#872577: debootstrap: Handle existing /dev

[Dan Nicholson]

On Fri, Aug 18, 2017 at 2:48 PM, Henrique de Moraes Holschuh
 wrote:
> On Fri, 18 Aug 2017, Dan Nicholson wrote:
>> When devices.tar.gz was being used, the devices would be written into
>> place with tar. This has the effect that the devices would be merged
>> into an existing /dev in the target. setup_devices_simple() does not
>> handle this case and fails when /dev already exists.
>>
>> Normally, the target would be empty and this wouldn't be an issue.
>> However, some tools that use debootstrap to initialize a target depended
>> on the old behavior. In particular, the obs-build package used for OBS
>> sets up a minimal /dev in the generic prep code before using debootstrap
>> to install packages needed for building debian packages.
>>
>> The attached patch fixes this by using tar to emulate the old
>> behavior. It would be really helpful if this could be applied.
>
> Wouldn't it be more straigthforward to "test -e || mknod" ?

I definitely considered that, but it seemed more noisy to the code to
add a conditional for every call. But I'd be fine reworking to that
approach if that's more acceptable, though.

Bug#872182: RFS: budgie-desktop/10.4-1

[foss.freedom]

with regards to the latest upload to the mentors queue - I have now
merged in the proposed fix for Bug #869953





On 15 August 2017 at 23:17, foss.freedom  wrote:
> thanks.
>
> I have doubled checked the bug number in the 10.2.9-3 release - this
> was released to unstable whilst 10.3 was in experimental.  I've
> updated the changelog to reflect this.
>
> I've pulled the budgie 10.4 release notes from the upstream
> announcement and added it to the changelog-announcement.txt
>
> Ack 4.0.1 and Standards-Version.
>
> I've double checked 4.0.1 and 4.0.0 to double check.  bookmarked this
> checklist as well for the future.
>
> I've done a further rebuild to confirm that the changelog changes are
> ok.  Also uploaded to mentors.
>
> On 15 August 2017 at 21:48, Andrey Rahmatullin  wrote:
>> On Tue, Aug 15, 2017 at 09:33:48PM +0100, foss.freedom wrote:
>>> - Merge changelog for 10.2.9-3 Stretch bug-fix release;
>>>   v10.2.9-3 is a hotfix for Stretch released after the v10.3.x
>>>   series was uploaded to testing
>> 10.2.9-3 is not in stretch.
>> We don't upload to testing.
>> We don't prepend "v" to package versions.
>>
>>> - debian/rules: add override_dh_installchangelogs with
>>>   debian/changelog-announcement.txt to describe
>>>   where to find the upstream announcement and description of changes
>> This is is wrong, it should contain the upstream changelog directly if
>> present.
>>
>>> >> - debian/control: standards version 4.0.0
>>> >Current one is 4.0.1.
>>>
>>> My unstable build is up-to-date as of today.  Building does not
>>> recognise 4.0.1
>> Please read what does this field mean:
>> https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version
>>
>>> I've updated the standards-version as requested though
>> You shouldn't blindly update it, you should go through
>> https://www.debian.org/doc/debian-policy/upgrading-checklist.html and make
>> sure the package actually conforms to the new policy version.
>>
>> --
>> WBR, wRAR

Bug#872585: [nodejs] Document why not supported on powerpc/armel

[Bastien ROUCARIÈS]

Package: nodejs
Version: 6.11.2~dfsg-2
Severity: important

Could you please document in README.Debian why it is not supported on powerpc 
and armel ? With maybe link to bug in bts, bug forwarded upstream

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

Bug#872584: bmagic: new upstream version

[Yury Stankevich]

Package: bmagic
Version: 3.7.0-3
Severity: normal

Hello,

please consider to package new upstream,
it have a better support for new GCC and allow to drop -fpermissive
hack.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (990, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

bmagic depends on no packages.

Versions of packages bmagic recommends:
ii  g++ [c++-compiler]4:6.3.0-4
ii  g++-6 [c++-compiler]  6.3.0-18

bmagic suggests no packages.

-- no debconf information

Bug#872583: fusiondirectory: Package depends on apache | lighthttpd | httpd | nginx, yet install config breaks if apache is not up and running.

[Harald Thingelstad]

Package: fusiondirectory
Version: 1.0.19-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I checked and found Fusiondirectory could be installed on nginx, my
preferred webserver, probably with a bit of manual configuration but 
nothing out of the way.
Still, when I tried to install the packages, the autoconfiuration system
relies on apache. Even when you try to install apache (but not run it
because nginx aleady runs), configuration breaks. (And I rely on nginx
for web proxying so it's not just to remove either.)

What more, when I tried to remove Fusiondirectory because it didn't work
for me, even the uninstall process breaks due to lack of a running
apache server. Not even 
dpkg --force-all -P fusiondirectory
succeeds in removing this package.
The solution was to uninstall apache2, then the other packages could be
uninstalled too.

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

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

Versions of packages fusiondirectory depends on:
ii  apache2 [httpd] 2.4.25-3+deb9u2
pn  fusiondirectory-smarty3-acl-render  
ii  gettext 0.19.8.1-2
ii  javascript-common   11
pn  libarchive-extract-perl 
pn  libcrypt-cbc-perl   
ii  libfile-copy-recursive-perl 0.38-1
pn  libjs-prototype 
pn  libjs-scriptaculous 
ii  libnet-ldap-perl1:0.6500+dfsg-1
pn  libpath-class-perl  
ii  libperl5.24 [libdigest-sha-perl]5.24.1-3+deb9u1
pn  libterm-readkey-perl
ii  libxml-twig-perl1:3.50-1
ii  nginx-extras [nginx]1.10.3-1+deb9u1
ii  openssl 1.1.0f-3
pn  php 
pn  php-cas 
pn  php-curl
pn  php-fpdf
pn  php-gd  
pn  php-imagick 
pn  php-imap
pn  php-ldap
pn  php-recode  
ii  php7.0-cli [php-cli]7.0.19-1
pn  schema2ldif 
pn  smarty-gettext  
pn  smarty3 

fusiondirectory recommends no packages.

Versions of packages fusiondirectory suggests:
ic  argonaut-server 1.0-1
ic  fusiondirectory-schema  1.0.19-1
ii  slapd   2.4.44+dfsg-5

-- no debconf information

Bug#801381: debian-archive-keyring: Depend/Recommend gnupg2 and gpgv2?

[Adam D. Barratt]

Control: tags -1 + pending

On Tue, 2017-08-15 at 17:07 +0100, Adam D. Barratt wrote:
> On 2017-08-15 15:37, Daniel Kahn Gillmor wrote:
> > I'm not even sure i understand why debian-archive-keyring Depends: gpgv
> > -- the package's goal is to provide the archive keyring to enable
> > OpenPGP validation, but the package itself doesn't appear to require
> > gpgv in any way.  Presumably the packages that need to *do* OpenPGP
> > validation will Depend: gpgv (or whatever other OpenPGP validator tool
> > they prefer to use).
> > 
> > I recommend moving gpgv to Suggests: and and removing gnupg from the 
> > set
> 
> The dependency was added as part of the changes in d-a-k 2012.1:
> 
> [ David Kalnischkies ]

For the record, I talked with David on IRC about this.

When the dependency was originally added, apt did not depend on gpgv or
gpg itself, as archive signing was very much optional, so d-a-k had to
ensure that they were available directly. These days, apt has the
required dependencies, so there's no need for them in d-a-k.

I've therefore pushed the removal of the dependencies from the .deb
package for the next upload. (The udeb has a Recommends on gpgv-udeb,
but I don't know the installer environment well enough to be happy
touching that right now.)

Regards,

Adam

Bug#872582: lua-cliargs: Add nocheck to lua-busted build dependency

[Jochen Sprickerhof]

Source: lua-cliargs
Severity: normal

Dear Maintainer,

In ef6b60ce695c34a7ff7135e5c3b4b96e11fa87f7 you added lua-busted as a
build dependency (for tests), which in turn has a dependency on
lua-cliargs which results in a loop and making it unable to bootstrap
lua-cliargs. I would propose to add  behind the lua-busted
dependency in debian/control to break this.

For more information see:

https://wiki.debian.org/BuildProfileSpec

Cheers Jochen

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

Kernel: Linux 4.9.0-3-amd64 (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: sysvinit (via /sbin/init)

Bug#872577: debootstrap: Handle existing /dev

[Henrique de Moraes Holschuh]

On Fri, 18 Aug 2017, Dan Nicholson wrote:
> When devices.tar.gz was being used, the devices would be written into
> place with tar. This has the effect that the devices would be merged
> into an existing /dev in the target. setup_devices_simple() does not
> handle this case and fails when /dev already exists.
> 
> Normally, the target would be empty and this wouldn't be an issue.
> However, some tools that use debootstrap to initialize a target depended
> on the old behavior. In particular, the obs-build package used for OBS
> sets up a minimal /dev in the generic prep code before using debootstrap
> to install packages needed for building debian packages.
> 
> The attached patch fixes this by using tar to emulate the old
> behavior. It would be really helpful if this could be applied.

Wouldn't it be more straigthforward to "test -e || mknod" ?

-- 
  Henrique Holschuh

Bug#872581: change policy format from debiandoc SGML to DocBook/XML

[W. Martin Borgert]

Package: python3
Version: 3.5.3-3
Severity: normal
Tags: patch

As discussed at DebConf, debiandoc SGML is obsolete and will be
removed from Debian.

Patches attached, one for the format change itself, the other
for rules, dependencies etc.

Python 2 bug is #872421
From 0dca8587cbb052c67053878dd2819a553594e57f Mon Sep 17 00:00:00 2001
From: "W. Martin Borgert" 
Date: Fri, 18 Aug 2017 09:44:19 +0200
Subject: [PATCH 1/2] change format from debiandoc SGML to DocBook/XML

---
 debian/python-policy.dbk  | 695 +
 debian/python-policy.sgml | 702 --
 2 files changed, 695 insertions(+), 702 deletions(-)
 create mode 100644 debian/python-policy.dbk
 delete mode 100644 debian/python-policy.sgml

diff --git a/debian/python-policy.dbk b/debian/python-policy.dbk
new file mode 100644
index 000..866119e
--- /dev/null
+++ b/debian/python-policy.dbk
@@ -0,0 +1,695 @@
+
+http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd;>
+
+
+  Debian Python Policy
+  
+	Neil Schemenauer
+	n...@debian.org
+  
+  
+	Matthias Klose
+	d...@debian.org
+  
+  
+	Gregor Hoffleit
+	fli...@debian.org
+  
+  
+Josselin Mouette
+	j...@debian.org
+  
+  
+Joe Wreschnig
+	pi...@debian.org
+  
+  version 0.4.1.0
+
+  
+	This document describes the packaging of Python within the
+	Debian GNU/Linux distribution and the policy requirements for
+	packaged Python programs and modules.
+  
+
+  1999 2001 2003 2006 Software in the
+	  Public Interest
+	
+	
+	  This manual is free software; you can redistribute it and/or
+	  modify it under the terms of the GNU General Public License
+	  as published by the Free Software Foundation; either version
+	  2 of the License, or (at your option) any later version.
+	
+	
+	  This is distributed in the hope that it will be useful, but
+	  WITHOUT ANY WARRANTY; without even the implied warranty of
+	  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See
+	  the GNU General Public License for more details.
+	
+	
+	  A copy of the GNU General Public License is available as
+	  /usr/share/common-licences/GPL in the Debian GNU/Linux
+	  distribution or on the World Wide Web at
+	  http://www.gnu.org/copyleft/gpl.html;
+	  >The GNU Public Licence.
+	
+	
+	  You can also obtain it by writing to the
+	  Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+	  Boston, MA 02111-1307, USA.
+	
+  
+
+  Python Packaging
+  
+	Versions
+	
+	  At any given time, the package python will
+	  represent the current default Debian Python version.
+	
+	
+	  The default Debian Python version should alway be the latest stable
+	  upstream release that can be integrated in the distribution.
+	
+	
+	  Apart from the default version, legacy versions of Python
+	  or beta versions of future releases
+	  may be included as well in the distribution, as long as they
+	  are needed by other packages, or as long as it seems
+	  reasonable to provide them.  (Note: For the scope of this
+	  document, Python versions are synonymous to feature
+	  releases, i.e. Python 2.0 and 2.0.1 are subminor versions of
+	  the same Python version 2.0, but Python 2.1 and 2.2 are
+	  indeed different versions.)
+	
+	
+	  For any version, the main package must be called
+	  pythonX.Y.
+	
+
+	
+	  The set of currently supported python versions can be found
+	  in /usr/share/python/debian_defaults.
+	
+
+  
+
+  
+	Main package
+	
+	  For every Python version provided in the distribution, the
+	  package pythonX.Y
+	  shall comprise a complete distribution for
+	  deployment of Python scripts and applications. The
+	  package includes the binary
+	  /usr/bin/pythonX.Y and
+	  all modules of the upstream Python distribution.
+	
+	
+	  Excluded are any modules that depend on
+	  non-required packages, they will be provided in
+	  separate packages.  Some tools and files for the
+	  development of Python modules are split off in a
+	  separate package
+	  pythonX.Y-dev.
+	  Documentation will be provided separately as well.
+	
+	
+	  At any time, the python package must contain
+	  a symlink /usr/bin/python to the the appropriate binary
+	  /usr/bin/pythonX.Y. The
+	  python package must also depend on the
+	  appropriate pythonX.Y
+	  to ensure this binary is installed. The version of the
+	  python package must be greater than or equal to
+	  X.Y and smaller than X.Y+1.
+	
+  
+
+  
+Python Interpreter
+
+  Interpreter Name
+  
+	Python scripts depending on the default Python version (see ) or not depending on a specific Python version should
+	use python (unversioned) as the interpreter name.
+	
+  
+	Python scripts that only work with a specific Python version must
+	explicitly use the versioned interpreter name
+	(pythonX.Y).
+  
+
+
+  

Bug#872565: encfs: FTBFS on mips, mipsel: undefined reference to `__atomic_store_8'

[Eduard Bloch]

Hallo,
* James Cowgill [Fri, Aug 18 2017, 05:02:52PM]:
> Source: encfs
> Version: 1.9.2-1
> Severity: serious
> Tags: sid buster
> 
> Hi,
> 
> ensfc FTBFS on mips, mipsel and various ports architectures with the error:
> > libencfs.so.1.9.2: undefined reference to `__atomic_store_8'
> > libencfs.so.1.9.2: undefined reference to `__atomic_fetch_add_8'
> > collect2: error: ld returned 1 exit status
> 
> This happens because those architectures do not have native 64-bit
> atomic instructions and instead call out to libatomic to provide
> emulations of them. To allow linking on these architecture you must link
> against libatomic.
> 
> One option is to add the -latomic to LDFLAGS in the Debian package, or I
> could probably come up with a patch to be applied upstream which will
> link only on the architectures it's needed.
> 
> Note there is an upstream GCC bug about doing all this in the toolchain,
> but for the moment it has to be done per package:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358

Thank you. I will try to handcraft a patch for the build system itself
and push it upstream ASAP.

Reminds me on a similar problem with
https://buildd.debian.org/status/fetch.php?pkg=apt-cacher-ng=powerpc=3-5=1493319231=0
which is confusing, the current solution (detection of libatomic) was
successfull on mips and most other 32-bit arches. Needs a tougher
investigation, apparently.

Best regards,
Eduard.

Bug#872580: [node-evp-bytestokey] FTBFS with node v6

[Bastien ROUCARIÈS]

Package: node-evp-bytestokey
Version: 1.0.0-3
Severity: serious
forwarded: https://github.com/crypto-browserify/EVP_BytesToKey/issues/8

nodejs test.js 
TAP version 13
# password: password
ok 1 should be equal
# password: ふっかつ　あきる　すぶり　はやい　つける　まゆげ　たんさん　みんぞく　ねほりはほり　せまい　たいまつばな　ひはん
not ok 2 should be equal
  ---
operator: equal
expected: '96d23d45a6b1fe'
actual:   'e985b4ba0c84e2'
at: Test. (/home/bastien/Documents/Personnel/soft/debian/js/
node-evp-bytestokey/node-evp-bytestokey/test.js:13:7)
  ...
# password: Z͑ͫAͫ͗LͨͧG̑͗O͂̌!̿̋
not ok 3 should be equal
  ---
operator: equal
expected: 'fc960d2ad3186e'
actual:   '84190e0d926c7c'
at: Test. (/home/bastien/Documents/Personnel/soft/debian/js/
node-evp-bytestokey/node-evp-bytestokey/test.js:13:7)
  ...
# password: 
not ok 4 should be equal
  ---
operator: equal
expected: '01382ecc78e6ae'
actual:   '82282e0665da04'
at: Test. (/home/bastien/Documents/Personnel/soft/debian/js/
node-evp-bytestokey/node-evp-bytestokey/test.js:13:7)
  ...

1..4
# tests 4
# pass  1
# fail  3


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

Bug#872579: xjed does not receive keyboard input unless you kill ibus-daemon

[Avery Pennarun]

Package: xjed
Version: 1:0.99.19-7+b1
Severity: important

I recently dist-upgraded to a new version of various packages and found that
xjed (both 0.99.18+dfsg.1-11_amd64 and 0.99.19-7+b1_amd64) had stopped
working at all.  The symptoms are:
- No response to keyboard input
- No response to SIGINT
- (Sometimes) window renders, but is just a blank black window with a text
  cursor
- Using 'jed' (non-X11 version) has no problem.

I found this thread where someone had a similar problem:
http://jed-users.jedsoft.narkive.com/WGfkeAGx/xjed-ignores-keypresses

Sure enough, the advice in that thread, to kill ibus-daemon, makes the
problem go away as long as ibus-daemon remains dead.

I haven't run into any other programs conflicting with ibus-daemon, so I
guess this is a problem in xjed somewhere.

-- System Information:
Debian Release: jessie/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-83-generic (SMP w/48 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: upstart (via init_is_upstart())

Versions of packages xjed depends on:
ii  jed-common  1:0.99.19-7
ii  libc6   2.19-0ubuntu6.13
ii  libslang2   2.3.1a-1
ii  libx11-62:1.6.2-1ubuntu2
ii  libxft2 2.3.1-2

xjed recommends no packages.

xjed suggests no packages.

-- no debconf information

Bug#872438: [Pkg-javascript-devel] Bug#872438: Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Jérémy Lal]

2017-08-18 20:38 GMT+02:00 Bastien ROUCARIES :

> On Fri, Aug 18, 2017 at 7:42 PM, Jérémy Lal  wrote:
> > James Cowgill replied this to my give back request on mip64el:
> >
> >> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el
> >> at the moment:
> >> https://bugs.debian.org/871514
> >
> >> Thanks,
> >> James
> >
> > Cheers,
> >
> > Jérémy
>
> Thanks BTW why node has no debug symbols ?
>

Because
https://packages.debian.org/fr/sid/nodejs-dbgsym

Bug#872569: RFS: kadu/4.3-0.1 [RC]

[Andrey Rahmatullin]

On Fri, Aug 18, 2017 at 08:34:23PM +0200, Mateusz Łukasik wrote:
>   Changes since the last upload:
> 
>   * Non-maintainer upload.
>   * New upstream release.
>   * Add patch to fix FTBFS with gcc-7. Thanks Fanael Linithien (Closes:
> #853470)
>   * Drop debian/patches/04-fix_compilation_error_c++14_vs_gnu++11.patch
NMUs shouldn't include new upstream releases unless really needed.
Please read 
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#871594: mediawiki-extensions-universallanguageselector - package description not really understandable

[Tomas Pospisek]

Hello Kartik Mistry,

the description you chose for your package is: "Tool to select a language 
and configure for MediaWiki".


What does "select a configure" mean? Do you mean "select a configuration"?

Or do you mean "Tool to select and configure a language for MediaWiki"?

Please make the wording of the description clearer.

Thanks a lot for packaging!
*t

Bug#872529: /usr/bin/caff: caff: puts TTY into weird state when prompting to send mail

[G. Branden Robinson]

Hi Guilhem!  Thanks for the prompt follow-up.

I've edited a thinko in my original report below, marked with [] brackets.

At 2017-08-18T15:39:31+0200, Guilhem Moulin wrote:
> On Fri, 18 Aug 2017 at 03:27:14 -0400, G. Branden Robinson wrote:
> > The only way to get past the prompt [is to] type Ctrl+J (yes, hold down
> > Control and press J).
> 
> I'm afraid I can't reproduce this.
> 
>   - How did you run caff(1)?  (Could you share the command line?)

$ caff e9800953

>   - Is the bug also present when you add ‘$CONFIG{colors} = {};’ to your
> ~/.caffrc?

Yes.

>   - Could you share the output of `stty -a` before and after running
> caff(1)?

$ vi ~/.caffrc; stty -a; caff e9800953; stty -a
[removed ‘$CONFIG{colors} = {};’]
"~/.caffrc" 52L, 1711C written
speed 38400 baud; rows 73; columns 191; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = 
; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase 
= ^W; lnext = ; discard = ^O;
min = 1; time = 0;
-parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon 
-ixoff -iuclc -ixany -imaxbel iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0
isig -icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt 
echoctl echoke -flusho -extproc
[NOTICE] Importing GnuPG options from ~/.gnupg/gpg.conf:
[NOTICE] personal-digest-preferences SHA256
[NOTICE] cert-digest-algo SHA256
[INFO] Key D19E9C7D71266DCE not changed
[NOTICE] Fetching keys from a keyserver (this may take a while)...
[INFO] Key E9800953 not changed
[INFO] Key E9800953 imported
[WARN] Ignoring revoked key 9B7E3E4611A61708AD807AF0733E9FDBE9800953
[WARN] More than one key matched E9800953 (assuming 
00E7CB9E10210383D2FD2459AA68ECC8E9800953).  Try to specify the long keyid or 
full fingerprint to avoid collisions.
[NOTICE] Sign the following keys according to your policy, then exit gpg with 
'save' after signing each key
gpg --homedir=/home/branden/.caff/gnupghome --no-options 
--personal-digest-preferences=SHA256 --cert-digest-algo=SHA256 
--no-auto-check-trustdb --trust-model=always --local-user D19E9C7D71266DCE 
--edit-key 00E7CB9E10210383D2FD2459AA68ECC8E9800953 sign
gpg (GnuPG) 2.1.18; Copyright (C) 2017 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

uid  Matt Taggart 
sig!3AA68ECC8E9800953 2009-06-02 never   [self-signature]*
 [primary]
uid  Matt Taggart 
sig!3AA68ECC8E9800953 2009-06-02 never   [self-signature]*
uid  Matt Taggart 
sig!3AA68ECC8E9800953 2009-06-02 never   [self-signature]*
sub  09FBB7BFCF693E8D
sig! AA68ECC8E9800953 2009-06-02 never   [self-signature]*
key AA68ECC8E9800953:
2 duplicate signatures removed

pub  rsa4096/AA68ECC8E9800953
 created: 2009-06-02  expires: never   usage: SC
sub  rsa4096/09FBB7BFCF693E8D
 created: 2009-06-02  expires: never   usage: E
[ unknown] (1). Matt Taggart 
[ unknown] (2)  Matt Taggart 
[ unknown] (3)  Matt Taggart 

Really sign all text user IDs? (y/N) y
"Matt Taggart " was already signed by key D19E9C7D71266DCE
"Matt Taggart " was already signed by key D19E9C7D71266DCE
"Matt Taggart " was already signed by key D19E9C7D71266DCE
Nothing to sign with key D19E9C7D71266DCE

##gpg> save
[INFO] Key 0xAA68ECC8E9800953 UID 1 Matt Taggart  done
[INFO] Key 0xAA68ECC8E9800953 UID 2 Matt Taggart  done
[INFO] Key 0xAA68ECC8E9800953 UID 3 Matt Taggart  done
Mail signature for 'Matt Taggart ' to 'm...@lackof.org'? [Y/n] 
^M^JWhat about [Y/n] is so hard to understand?
Answer with either 'n' or 'y' or just press enter for the default.
Mail signature for 'Matt Taggart ' to 'm...@lackof.org'? [Y/n] 
n^M^JWhat about [Y/n] is so hard to understand?
Answer with either 'n' or 'y' or just press enter for the default.
Mail signature for 'Matt Taggart ' to 'm...@lackof.org'? [Y/n] 
n^JMail signature for 'Matt Taggart ' to 
'tagg...@debian.org'? [Y/n] n^JMail signature for 'Matt Taggart 
' to 'tagg...@riseup.net'? [Y/n] n^J[INFO] Key 
0xAA68ECC8E9800953 done
speed 38400 baud; rows 73; columns 191; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ; eol2 = 
; swtch = ; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase 
= ^W; lnext = ; discard = ^O;
min = 1; time = 0;
-parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr -icrnl -ixon 
-ixoff -iuclc -ixany -imaxbel iutf8
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill 

Bug#872578: qBittorent: updating to 3.3.15 from 3.3.7 fixes crashes

[Михаил]

Package: qbittorrent
Version: 3.3.7

I am using Ubuntu 17.04 and qbittorent 3.3.7 from its repositories, and 
it crashes from time to time. Updated qbittorrent to 3.3.15 and 
libtorrent-rasterbar9 1.1.4+git20170719.f0d2551073 from 1.1.1 using the 
PPA 
https://launchpad.net/~qbittorrent-team/+archive/ubuntu/qbittorrent-stable 
, and it seems to not crash anymore. Reporting the bug to Debian because 
Ubuntu imports Debian packages and I see lots of other bug reports with 
crashes here.


Catching signal: SIGSEGV
Please file a bug report at http://bug.qbittorrent.org and provide the 
following information:

qBittorrent version: v3.3.7
stack trace:
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x158eab  
[0x7fb175b9aeab]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x15ae5a  
[0x7fb175b9ce5a]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x9b423  
[0x7fb175add423]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x9e57a  
[0x7fb175ae057a]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xa2faf  
[0x7fb175ae4faf]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xa465d  
[0x7fb175ae665d]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x162d4c  
[0x7fb175ba4d4c]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x1631a7  
[0x7fb175ba51a7]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x2fcf54  
[0x7fb175d3ef54]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0x1be988  
[0x7fb175c00988]
  /usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xbf6bf  
[0x7fb175b016bf]

  /lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x76da [0x7fb17379a6da]
  /lib/x86_64-linux-gnu/libc.so.6 : clone()+0x5f  [0x7fb172c2cd7f]
Ошибка сегментирования (стек памяти сброшен на диск)

--
--
С уважением,
Михаил Новоселов, технический специалист школы "Думалогия"
думалогия.рф | mikhail...@dumalogiya.ru

Bug#872577: debootstrap: Handle existing /dev

[Dan Nicholson]

Package: debootstrap
Version: 1.0.89
Severity: normal
Tags: patch

When devices.tar.gz was being used, the devices would be written into
place with tar. This has the effect that the devices would be merged
into an existing /dev in the target. setup_devices_simple() does not
handle this case and fails when /dev already exists.

Normally, the target would be empty and this wouldn't be an issue.
However, some tools that use debootstrap to initialize a target depended
on the old behavior. In particular, the obs-build package used for OBS
sets up a minimal /dev in the generic prep code before using debootstrap
to install packages needed for building debian packages.

The attached patch fixes this by using tar to emulate the old
behavior. It would be really helpful if this could be applied.

Thanks!

--
Dan Nicholson  |  +1.206.437.0833  |  Endless
From d5b723f800c027e0d377627946bc1d697a5be322 Mon Sep 17 00:00:00 2001
From: Dan Nicholson 
Date: Fri, 18 Aug 2017 13:36:27 -0500
Subject: [PATCH] Merge devices to /dev with tar

When devices.tar.gz was being used, the devices would be written into
place with tar. This has the effect that the devices would be merged
into an existing /dev in the target. setup_devices_simple() does not
handle this case and fails when /dev already exists.

Normally, the target would be empty and this wouldn't be an issue.
However, some tools that use debootstrap to initialize a target depended
on the old behavior. In particular, the obs-build package used for OBS
sets up a minimal /dev in the generic prep code before using debootstrap
to install packages needed for building debian packages.

Emulate the old behavior by creating the devices in a temporary
debootstrap/dev and then use tar to write them into place.
---
 functions | 34 --
 1 file changed, 20 insertions(+), 14 deletions(-)

diff --git a/functions b/functions
index 3cfa0d4..0d99a95 100644
--- a/functions
+++ b/functions
@@ -1163,24 +1163,30 @@ setup_dynamic_devices () {
 
 setup_devices_simple () {
 	# The list of devices that can be created in a container comes from
-	# src/core/cgroup.c in the systemd source tree.
-	mknod -m 666 $TARGET/dev/null	c 1 3
-	mknod -m 666 $TARGET/dev/zero	c 1 5
-	mknod -m 666 $TARGET/dev/full	c 1 7
-	mknod -m 666 $TARGET/dev/random	c 1 8
-	mknod -m 666 $TARGET/dev/urandom	c 1 9
-	mknod -m 666 $TARGET/dev/tty	c 5 0
-	mkdir $TARGET/dev/pts/ $TARGET/dev/shm/
+	# src/core/cgroup.c in the systemd source tree. The devices are first
+	# created in a temporary /dev and written into place using tar like
+	# the old devices tarball.
+	mkdir $TARGET/debootstrap/dev
+	mknod -m 666 $TARGET/debootstrap/dev/null	c 1 3
+	mknod -m 666 $TARGET/debootstrap/dev/zero	c 1 5
+	mknod -m 666 $TARGET/debootstrap/dev/full	c 1 7
+	mknod -m 666 $TARGET/debootstrap/dev/random	c 1 8
+	mknod -m 666 $TARGET/debootstrap/dev/urandom	c 1 9
+	mknod -m 666 $TARGET/debootstrap/dev/tty	c 5 0
+	mkdir $TARGET/debootstrap/dev/pts/ $TARGET/debootstrap/dev/shm/
 	# Inside a container, we might not be allowed to create /dev/ptmx.
 	# If not, do the next best thing.
-	if ! mknod -m 666 $TARGET/dev/ptmx c 5 2; then
+	if ! mknod -m 666 $TARGET/debootstrap/dev/ptmx c 5 2; then
 		warning MKNOD "Could not create /dev/ptmx, falling back to symlink. This chroot will require /dev/pts mounted with ptmxmode=666"
-		ln -s pts/ptmx $TARGET/dev/ptmx
+		ln -s pts/ptmx $TARGET/debootstrap/dev/ptmx
 	fi
-	ln -s /proc/self/fd   $TARGET/dev/fd
-	ln -s /proc/self/fd/0 $TARGET/dev/stdin
-	ln -s /proc/self/fd/1 $TARGET/dev/stdout
-	ln -s /proc/self/fd/2 $TARGET/dev/stderr
+	ln -s /proc/self/fd   $TARGET/debootstrap/dev/fd
+	ln -s /proc/self/fd/0 $TARGET/debootstrap/dev/stdin
+	ln -s /proc/self/fd/1 $TARGET/debootstrap/dev/stdout
+	ln -s /proc/self/fd/2 $TARGET/debootstrap/dev/stderr
+
+	# Tar the temporary /dev into place to merge with an existing /dev
+	(cd $TARGET/debootstrap; tar -cf - dev) | (cd $TARGET; tar -xf -)
 }
 
 setup_devices_fakechroot () {
-- 
2.11.0

Bug#872575: graphicsmagick: CVE-2017-12936: use-after-free in ReadWMFImage (wmf.c)

[Salvatore Bonaccorso]

Source: graphicsmagick
Version: 1.3.26-5
Severity: important
Tags: upstream patch security

Hi,

the following vulnerability was published for graphicsmagick.

CVE-2017-12936[0]:
| The ReadWMFImage function in coders/wmf.c in GraphicsMagick 1.3.26 has
| a use-after-free issue for data associated with exception reporting.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12936
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12936
[1] http://www.openwall.com/lists/oss-security/2017/08/18/3
[2] http://hg.code.sf.net/p/graphicsmagick/code/rev/be898b7c97bd

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#872576: graphicsmagick: CVE-2017-12935: nvalid memory read in SetImageColorCallBack (image.c)

[Salvatore Bonaccorso]

Source: graphicsmagick
Version: 1.3.26-5
Severity: important
Tags: patch security upstream

Hi,

the following vulnerability was published for graphicsmagick.

CVE-2017-12935[0]:
| The ReadMNGImage function in coders/png.c in GraphicsMagick 1.3.26
| mishandles large MNG images, leading to an invalid memory read in the
| SetImageColorCallBack function in magick/image.c.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12935
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12935
[1] http://www.openwall.com/lists/oss-security/2017/08/18/4
[2] http://hg.code.sf.net/p/graphicsmagick/code/rev/cd699a44f188

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#872573: Stopping libvirtd.service does not properly stop all (dnsmasq) processes

[Michael Biebl]

Package: libvirt-daemon-system
Version: 3.6.0-1
Severity: normal
File: /lib/systemd/system/libvirtd.service

libvirtd.service uses KillMode=process, this means, it's up to the main
process to kill all child processes properly. This doesn't seem to be
the case for libvirtd

# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2017-08-18 20:08:30 CEST; 37min ago
 Docs: man:libvirtd(8)
   http://libvirt.org
 Main PID: 689 (libvirtd)
Tasks: 18 (limit: 32768)
   CGroup: /system.slice/libvirtd.service
   ├─ 689 /usr/sbin/libvirtd
   ├─1529 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─1530 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper

# systemctl stop libvirtd
# systemctl status libvirtd
● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: inactive (dead) since Fri 2017-08-18 20:46:35 CEST; 1s ago
 Docs: man:libvirtd(8)
   http://libvirt.org
  Process: 689 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, 
status=0/SUCCESS)
 Main PID: 689 (code=exited, status=0/SUCCESS)
Tasks: 2 (limit: 32768)
   CGroup: /system.slice/libvirtd.service
   ├─1529 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─1530 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper

See, how the dnsmasq processes are still running after stopping the
service.


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

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

Versions of packages libvirt-daemon-system depends on:
ii  adduser  3.116
ii  debconf  1.5.63
ii  gettext-base 0.19.8.1-2+b1
ii  init-system-helpers  1.49
ii  iptables 1.6.1-2
ii  libapparmor1 2.11.0-10
ii  libaudit11:2.7.7-1+b2
ii  libblkid12.29.2-4
ii  libc62.24-14
ii  libcap-ng0   0.7.7-3+b1
ii  libdbus-1-3  1.11.16+really1.10.22-1
ii  libdevmapper1.02.1   2:1.02.142-1
ii  libnl-3-200  3.2.27-2
ii  libnl-route-3-2003.2.27-2
ii  libnuma1 2.0.11-2.1
ii  libselinux1  2.6-3+b2
ii  libvirt-clients  3.6.0-1
ii  libvirt-daemon   3.6.0-1
ii  libvirt0 3.6.0-1
ii  libxml2  2.9.4+dfsg1-3
ii  libyajl2 2.1.0-2+b3
ii  logrotate3.11.0-0.1
ii  lsb-base 9.20161125
ii  policykit-1  0.105-18

Versions of packages libvirt-daemon-system recommends:
ii  bridge-utils  1.5-14
ii  dmidecode 3.1-1
ii  dnsmasq-base  2.77-2
ii  ebtables  2.0.10.4-3.5+b1
ii  iproute2  4.9.0-1
ii  parted3.2-17

Versions of packages libvirt-daemon-system suggests:
ii  apparmor2.11.0-10
pn  auditd  
ii  nfs-common  1:1.3.4-2.1+b1
pn  pm-utils
pn  radvd   
ii  systemd 234-2
pn  systemtap   
pn  zfsutils

-- Configuration Files:
/etc/libvirt/nwfilter/allow-arp.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-arp.xml'
/etc/libvirt/nwfilter/allow-dhcp-server.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-dhcp-server.xml'
/etc/libvirt/nwfilter/allow-dhcp.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-dhcp.xml'
/etc/libvirt/nwfilter/allow-incoming-ipv4.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-incoming-ipv4.xml'
/etc/libvirt/nwfilter/allow-ipv4.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/allow-ipv4.xml'
/etc/libvirt/nwfilter/clean-traffic.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/clean-traffic.xml'
/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-arp-ip-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-arp-mac-spoofing.xml'
/etc/libvirt/nwfilter/no-arp-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-arp-spoofing.xml'
/etc/libvirt/nwfilter/no-ip-multicast.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-ip-multicast.xml'
/etc/libvirt/nwfilter/no-ip-spoofing.xml [Errno 13] Keine Berechtigung: 
'/etc/libvirt/nwfilter/no-ip-spoofing.xml'

Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

[David Mohammed]

patch sid



On 18 August 2017 at 19:37, David Mohammed  wrote:
> control: patch
>
> Gianfranco and Jeremy
>
> Please find a debdiff that resolves this issue.
>
> The bug is rather unfortunately been exposed due to the unexpected
> GTK+3.24 version only being migrated to buster - budgie-desktop is
> expecting a coordinated GTK+3.24 gnome-settings-daemon and libmutter
> being migrated at the same time.
>
> I have applied this to the budgie-desktop version in unstable (same
> version in buster), and run a pbuilder to check that it compiles.
>
> Separately I have built and installed the built .debs and can confirm
> I can now login successfully into a buster budgie-desktop session.
>
> Given the rather unfortunate showstopper nature of this bug I have
> marked the patch urgency=high
>
> Gianfranco - I will separately merge this patch with budgie-desktop
> 10.4 that is in the mentors queue.
>
> many thanks in advance
>
>
>
> On 17 August 2017 at 22:37, Bruno Miguel  
> wrote:
>> Changing the RequiredComponents content fixed things. I now have
>> "RequiredComponents=org.gnome.SettingsDaemon.A11yKeyboard;org.gnome.SettingsDaemon.A11ySettings;org.gnome.SettingsDaemon.Clipboard;org.gnome.SettingsDaemon.Color;org.gnome.SettingsDaemon.Datetime;org.gnome.SettingsDaemon.Housekeeping;org.gnome.SettingsDaemon.Keyboard;org.gnome.SettingsDaemon.MediaKeys;org.gnome.SettingsDaemon.Mouse;org.gnome.SettingsDaemon.Orientation;org.gnome.SettingsDaemon.Power;org.gnome.SettingsDaemon.PrintNotifications;org.gnome.SettingsDaemon.Rfkill;org.gnome.SettingsDaemon.ScreensaverProxy;org.gnome.SettingsDaemon.Sharing;org.gnome.SettingsDaemon.Smartcard;org.gnome.SettingsDaemon.Sound;org.gnome.SettingsDaemon.Wacom;org.gnome.SettingsDaemon.XRANDR;org.gnome.SettingsDaemon.XSettings;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"
>>
>> Thanks for the help!
>>
>> On Thu, Aug 17, 2017 at 10:09 PM, Bruno Miguel
>>  wrote:
>>> On Thu, Aug 17, 2017 at 9:21 PM, Jeremy Bicha  wrote:
 Control: reopen -1

 On Thu, Aug 17, 2017 at 3:47 PM, Bruno Miguel
  wrote:
> I've installed Budgie in Testing and it won't login due to missing gnome-
> settings-daemon binary.

 I downloaded budgie-core 10.3.1-4+b1 from
 https://packages.debian.org/sid/amd64/budgie-core/download

 and verified that
 /usr/share/gnome-session/sessions/budgie-desktop.session contains this
 line:

 RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;

 which won't work with gnome-settings-daemon 3.24. It should have the
 individual gnome-settings-daemon binaries instead of
 'gnome-settings-daemon' listed.
>>>
>>> It does have 
>>> "RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"
>>>
>>> I'll change it and test.
>>>
 Thanks,
 Jeremy Bicha
>>>
>>> Cheers.

Bug#872574: graphicsmagick: CVE-2017-12937: heap-based buffer overflow in ReadSUNImage (sun.c)

[Salvatore Bonaccorso]

Source: graphicsmagick
Version: 1.3.26-5
Severity: important
Tags: upstream security patch

Hi,

the following vulnerability was published for graphicsmagick.

CVE-2017-12937[0]:
| The ReadSUNImage function in coders/sun.c in GraphicsMagick 1.3.26 has
| a colormap heap-based buffer over-read.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12937
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12937
[1] http://www.openwall.com/lists/oss-security/2017/08/18/5
[2] http://hg.code.sf.net/p/graphicsmagick/code/rev/95d00d55e978

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#872572: ring: Account status "Not Registered"

[paine]

Package: ring
Version: 20170803.2.5fcfe3f~dfsg1-1~bpo9+1
Severity: important

Dear Maintainer,

For reasons unknown to me, the status of my account is described as "Not
Registered" under "Settings -> Accounts". When it is listed as such, it fails
to generate a PIN code that enables it to be used on more than one device. I
know that because, briefly, my account was reported as being listed. And I then
seized the opportunity to generate the PIN code and connect it with my mobile
device. That is no longer the case, hence, I would like to recover that
functionality.

I'll be at your disposal, if you ever need specific logs and more information.
Thanks for your time.



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 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 ring depends on:
ii  dconf-gsettings-backend [gsettings-backe  0.26.0-2+b1
ii  libappindicator3-10.4.92-4
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-11+deb9u1
ii  libcairo-gobject2 1.14.8-1
ii  libcairo2 1.14.8-1
ii  libclutter-1.0-0  1.26.0+dfsg-3
ii  libclutter-gtk-1.0-0  1.8.2-2
ii  libcogl-pango20   1.22.2-2
ii  libcogl-path201.22.2-2
ii  libcogl20 1.22.2-2
ii  libdbus-1-3   1.10.18-1
ii  libdbus-glib-1-2  0.108-2
ii  libdbusmenu-glib4 12.10.2-2
ii  libdrm2   2.4.74-1
ii  libebackend-1.2-103.22.7-1
ii  libebook-1.2-16   3.22.7-1
ii  libebook-contacts-1.2-2   3.22.7-1
ii  libedata-book-1.2-25  3.22.7-1
ii  libedataserver-1.2-22 3.22.7-1
ii  libegl1-mesa [libegl1-x11]13.0.6-1+b2
ii  libgbm1   13.0.6-1+b2
ii  libgcc1   1:6.3.0-18
ii  libgdk-pixbuf2.0-02.36.5-2
ii  libglib2.0-0  2.50.3-2
ii  libgtk-3-03.22.11-1
ii  libjavascriptcoregtk-4.0-18   2.16.3-2
ii  libjson-glib-1.0-01.2.6-1
ii  libnm-glib4   1.6.2-3
ii  libnm-util2   1.6.2-3
ii  libnotify40.7.7-2
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libqrencode3  3.4.4-1+b2
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libsecret-1-0 0.18.5-3.1
ii  libsoup2.4-1  2.56.0-2+deb9u1
ii  libstdc++66.3.0-18
ii  libwayland-client01.12.0-1
ii  libwayland-cursor01.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]13.0.6-1+b2
ii  libwayland-server01.12.0-1
ii  libwebkit2gtk-4.0-37  2.16.3-2
ii  libx11-6  2:1.6.4-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxkbcommon0 0.7.1-1
ii  libxml2   2.9.4+dfsg1-2.2
ii  libxrandr22:1.5.1-1
ii  ring-daemon   20170803.2.5fcfe3f~dfsg1-1~bpo9+1

ring recommends no packages.

ring suggests no packages.

-- no debconf information

Bug#872571: RFS: injeqt/1.1.0-1.1 [RC]

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: important

  Dear mentors,

  I am looking for a sponsor for my package "injeqt"

 * Package name: injeqt
   Version : 1.1.0-1.1
   Upstream Author : Rafał Malinowski 


 * URL : https://github.com/vogel/injeqt
 * License : LGPL-2.1
   Section : libs

  It builds those binary packages:

libinjeqt-dev - Dependency injection framework for Qt
 libinjeqt1 - Dependency injection framework for Qt

  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/injeqt


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/i/injeqt/injeqt_1.1.0-1.1.dsc



  Changes since the last upload:

  * Non-maintainer upload.
  * Add patch to fix ftbfs with GCC-7. (Closes: #853452)

  Regards,
   Mateusz Łukasik

Bug#869953: budgie-core: Adapt to gnome-settings-daemon 3.24

[David Mohammed]

control: patch

Gianfranco and Jeremy

Please find a debdiff that resolves this issue.

The bug is rather unfortunately been exposed due to the unexpected
GTK+3.24 version only being migrated to buster - budgie-desktop is
expecting a coordinated GTK+3.24 gnome-settings-daemon and libmutter
being migrated at the same time.

I have applied this to the budgie-desktop version in unstable (same
version in buster), and run a pbuilder to check that it compiles.

Separately I have built and installed the built .debs and can confirm
I can now login successfully into a buster budgie-desktop session.

Given the rather unfortunate showstopper nature of this bug I have
marked the patch urgency=high

Gianfranco - I will separately merge this patch with budgie-desktop
10.4 that is in the mentors queue.

many thanks in advance



On 17 August 2017 at 22:37, Bruno Miguel  wrote:
> Changing the RequiredComponents content fixed things. I now have
> "RequiredComponents=org.gnome.SettingsDaemon.A11yKeyboard;org.gnome.SettingsDaemon.A11ySettings;org.gnome.SettingsDaemon.Clipboard;org.gnome.SettingsDaemon.Color;org.gnome.SettingsDaemon.Datetime;org.gnome.SettingsDaemon.Housekeeping;org.gnome.SettingsDaemon.Keyboard;org.gnome.SettingsDaemon.MediaKeys;org.gnome.SettingsDaemon.Mouse;org.gnome.SettingsDaemon.Orientation;org.gnome.SettingsDaemon.Power;org.gnome.SettingsDaemon.PrintNotifications;org.gnome.SettingsDaemon.Rfkill;org.gnome.SettingsDaemon.ScreensaverProxy;org.gnome.SettingsDaemon.Sharing;org.gnome.SettingsDaemon.Smartcard;org.gnome.SettingsDaemon.Sound;org.gnome.SettingsDaemon.Wacom;org.gnome.SettingsDaemon.XRANDR;org.gnome.SettingsDaemon.XSettings;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"
>
> Thanks for the help!
>
> On Thu, Aug 17, 2017 at 10:09 PM, Bruno Miguel
>  wrote:
>> On Thu, Aug 17, 2017 at 9:21 PM, Jeremy Bicha  wrote:
>>> Control: reopen -1
>>>
>>> On Thu, Aug 17, 2017 at 3:47 PM, Bruno Miguel
>>>  wrote:
 I've installed Budgie in Testing and it won't login due to missing gnome-
 settings-daemon binary.
>>>
>>> I downloaded budgie-core 10.3.1-4+b1 from
>>> https://packages.debian.org/sid/amd64/budgie-core/download
>>>
>>> and verified that
>>> /usr/share/gnome-session/sessions/budgie-desktop.session contains this
>>> line:
>>>
>>> RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;
>>>
>>> which won't work with gnome-settings-daemon 3.24. It should have the
>>> individual gnome-settings-daemon binaries instead of
>>> 'gnome-settings-daemon' listed.
>>
>> It does have 
>> "RequiredComponents=gnome-settings-daemon;budgie-wm;budgie-daemon;budgie-panel;budgie-polkit;"
>>
>> I'll change it and test.
>>
>>> Thanks,
>>> Jeremy Bicha
>>
>> Cheers.


budgie-desktop_10.3.1-5.debdiff
Description: Binary data

Bug#872438: [Pkg-javascript-devel] Bug#872438: Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Bastien ROUCARIES]

On Fri, Aug 18, 2017 at 7:42 PM, Jérémy Lal  wrote:
> James Cowgill replied this to my give back request on mip64el:
>
>> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el
>> at the moment:
>> https://bugs.debian.org/871514
>
>> Thanks,
>> James
>
> Cheers,
>
> Jérémy

Thanks BTW why node has no debug symbols ?

Bastien

>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#872570: RFS: openbox-menu/0.8.0+hg20161009-1

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "openbox-menu"

 * Package name: openbox-menu
   Version : 0.8.0+hg20161009-1
   Upstream Author : mimas 
 * URL : https://bitbucket.org/fabriceT/openbox-menu
 * License : GPL-3+
   Section : x11

  It builds those binary packages:

openbox-menu - openbox pipe-menu to display entries in *.desktop files

  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/openbox-menu


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/o/openbox-menu/openbox-menu_0.8.0+hg20161009-1.dsc


  Changes since the last upload:
  [ Helmut Grohne ]
  * Fix FTCBFS: (Closes: #871404)
+ Make pkg-config substitutable.
+ Do not strip during install.

  [ Mateusz Łukasik ]
  * Merge latest hg version.
  * debian/control:
+ Bump Standards-Version to 4.0.1. (no changes needed)
+ Bump dh version to 10.
  * Update debian/rules.
  * Update debian/copyright.
  * Add testsuite.

  Regards,
   Mateusz Łukasik

Bug#872368: gpgme: please adjust libgpgme11 dependency on gnupg package

[Daniel Kahn Gillmor]

Hi RjY--

On Fri 2017-08-18 13:51:29 +0100, RjY wrote:
> As a test I created an empty package to subvert the dependency and see
> if anything breaks. The control file was thus:
>
> Package: no-full-gnupg-install
> Maintainer: RjY 
> Architecture: all
> Version: 1
> Depends: gpg (>= 2.1.23-2)
> Recommends: gpg-agent (>= 2.1.23-2)
> Provides: gnupg (= 2.1.23-2)
> Description: No full GNUPG install
>  This package "provides" gnupg, to avoid libgpgme11
>  pulling in the full gnupg suite, until 872368 is fixed.
>
> This allowed installing only gpg and gpg-agent. So far, things still
> seem to be working as expected: mutt appears fine, I can still use gpg
> to encrypt/decrypt backups, and so on. It would still be good to get
> this fixed in src:gpgme, though!

This is a neat suggestion, but i'm not convinced it's a good idea.

In particular, if you don't have gpg-agent, you won't be able to do any
secret key operations.  if you don't have dirmngr, network access will
fail.

gpgme aims to support all of those things.  I *really* don't like the
idea of introducing those kinds of hard-to-debug failures.  Furthermore,
GnuPG upstream prefers that we *don't* ship a bunch of separate
packages, they see the whole thing as a suite.

So let me ask you more about your motivation with this bug report here
-- are you interested in having fewer packages installed?  less software
total?  smaller disk images?  something else?

The other package re-arrangement i've been flirting with on the gnupg2
source package is to go ahead and collapse *all* of the files shipped in
the binary packages together (with the exception of gpgv, which needs to
be separate and small for validation-only systems).  That would make a
single package, so there would only be one dependency from gpgsm.  It
would look less scary when you "apt install mutt", and it would be less
disk space (because of fewer copies of
/usr/share/doc/*/{copyright,changelog.gz,changelog.Debian.gz,etc…}).

Would that satisfy your goals?  If not, why not?

 --dkg


signature.asc
Description: PGP signature

Bug#872569: RFS: kadu/4.3-0.1 [RC]

[Mateusz Łukasik]

Package: sponsorship-requests
Severity: important

  Dear mentors,

  I am looking for a sponsor for my package "kadu"

 * Package name: kadu
   Version : 4.3-0.1
   Upstream Author : Kadu Team
 * URL : http://kadu.net
 * License : GPL-3+
   Section : net

  It builds those binary packages:

kadu  - Gadu-Gadu/XMPP client for X11
 kadu-common - Gadu-Gadu/XMPP client for X11
 kadu-dev   - Development files needed to compile plugins for kadu
 kadu-themes - Additional icons and emoticons for Kadu
 libkadu- Gadu-Gadu/XMPP client for X11

  To access further information about this package, please visit the 
following URL:


  https://mentors.debian.net/package/kadu

  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/k/kadu/kadu_4.3-0.1.dsc


  Changes since the last upload:

  * Non-maintainer upload.
  * New upstream release.
  * Add patch to fix FTBFS with gcc-7. Thanks Fanael Linithien (Closes: 
#853470)

  * Drop debian/patches/04-fix_compilation_error_c++14_vs_gnu++11.patch


  Regards,
   Mateusz Łukasik

Bug#872568: rsyslog: FTBFS on mips, mipsel - error: 'pThis' undeclared

[James Cowgill]

Source: rsyslog
Version: 8.29.0-1
Severity: serious
Tags: sid buster patch

Hi,

rsyslog FTBFS on mips, mipsel and various ports architectures with the
error:
> In file included from ../../runtime/prop.h:25:0,
>  from ../../runtime/glbl.h:38,
>  from ../../runtime/stream.h:73,
>  from ../../runtime/obj.h:48,
>  from ../../runtime/rsyslog.h:634,
>  from imptcp.c:61:
> imptcp.c: In function 'AcceptConnReq':
> imptcp.c:831:39: error: 'pThis' undeclared (first use in this function)
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>^
> ../../runtime/atomic.h:206:22: note: in definition of macro 
> 'ATOMIC_INC_uint64'
>pthread_mutex_lock(phlpmut); \
>   ^~~
> imptcp.c:831:2: note: in expansion of macro 'STATSCOUNTER_INC'
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>   ^~~~
> imptcp.c:831:39: note: each undeclared identifier is reported only once for 
> each function it appears in
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>^
> ../../runtime/atomic.h:206:22: note: in definition of macro 
> 'ATOMIC_INC_uint64'
>pthread_mutex_lock(phlpmut); \
>   ^~~
> imptcp.c:831:2: note: in expansion of macro 'STATSCOUNTER_INC'
>   STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
>   ^~~~

As the error suggests, pThis is not declared in that function. The code
is only used on architectures which do not have 64-bit atomics which is
why it only fails on some architectures.

There is an upstream pull request to fix this:
https://github.com/rsyslog/rsyslog/pull/1725

I've also attached the patch from that PR which should fix this.

Thanks,
James
From 2ea84c47b208214370034500f0aab19fe93cce7f Mon Sep 17 00:00:00 2001
From: Pete Nelson 
Date: Wed, 16 Aug 2017 17:19:33 -0400
Subject: [PATCH] correct paste oversight on mutex arg

Remove the 'pThis->' from the second argument to STATSCOUNTER_INC macro.
This only affects architectures without atomic uint64 actions, like aarm64.
Others do not use the mut argument, and it gets compiled out.
---
 plugins/imptcp/imptcp.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/plugins/imptcp/imptcp.c b/plugins/imptcp/imptcp.c
index c373c17e6..ab2a17e5b 100644
--- a/plugins/imptcp/imptcp.c
+++ b/plugins/imptcp/imptcp.c
@@ -828,7 +828,7 @@ AcceptConnReq(ptcplstn_t *pLstn, int *newSock, prop_t **peerName, prop_t **peerI
 		LogMsg(0, RS_RET_NO_ERRCODE, LOG_INFO, "imptcp: connection established with host: %s", propGetSzStr(*peerName));
 	}
 
-	STATSCOUNTER_INC(pLstn->ctrSessOpen, pThis->pLstn->mutCtrSessOpen);
+	STATSCOUNTER_INC(pLstn->ctrSessOpen, pLstn->mutCtrSessOpen);
 	*newSock = iNewSock;
 
 finalize_it:
@@ -837,7 +837,7 @@ AcceptConnReq(ptcplstn_t *pLstn, int *newSock, prop_t **peerName, prop_t **peerI
 		if(iRet != RS_RET_NO_MORE_DATA && pLstn->pSrv->bEmitMsgOnOpen) {
 			LogError(0, NO_ERRCODE, "imptcp: connection could not be established with host: %s", propGetSzStr(*peerName));
 		}
-		STATSCOUNTER_INC(pLstn->ctrSessOpenErr, pThis->pLstn->mutCtrSessOpenErr);
+		STATSCOUNTER_INC(pLstn->ctrSessOpenErr, pLstn->mutCtrSessOpenErr);
 		/* the close may be redundant, but that doesn't hurt... */
 		if(iNewSock != -1)
 			close(iNewSock);


signature.asc
Description: OpenPGP digital signature

Bug#870181: stretch-pu: package bareos/16.2.4-3+deb9u1

[Felix Geyer]

On 08.08.2017 22:00, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Tue, 2017-08-08 at 07:52 +0200, Felix Geyer wrote:
>> Control: tags -1 - moreinfo
>>
>> On Mon, 31 Jul 2017 00:24:41 +0200 Felix Geyer  wrote:
>>> Uh, you are right of course. Not sure how I missed that. Thanks for 
>>> checking!
>>> I've just upload 16.2.6-3 with those changes to unstable.
>>>
>>> While looking further into it I noticed that the version check in
>>> bareos-director.postinst is wrong.
>>> Instead of 15.2.2-1~ it should be 16.2.4-3+deb9u1~
>>
>> The fixed version is now in testing.
> 
> Thanks. Please feel free to upload.

Uploaded, thanks!
The only change compared to the debdiff is the version check in postinst.

Felix

Bug#870178: jessie-pu: package bareos/14.2.1+20141017gitc6c5b56-3+deb8u3

[Felix Geyer]

On 08.08.2017 21:47, Adam D. Barratt wrote:
>> So far as I can tell, the logrotate issues also affects the package in
>> unstable - is that correct?
> 
> It looks like that was resolved in a subsequent upload.
> 
> Please go ahead.

Uploaded, thanks!

Felix

Bug#869971: nose: Provide a package for PyPy

[Dmitry Shachnev]

Hi Ghislain!

On Fri, Jul 28, 2017 at 10:28:09AM +0100, Ghislain Antony Vaillant wrote:
> Dear Maintainer,
>
> The lack of a nose package for PyPy may block testing of future packaged
> PyPy modules. Since nose should be compatible with PyPy according to the
> upstream wiki [1], you might want to consider providing a corresponding
> pypy-nose package.

I want to note that nose is deprecated [1] and completely unmaintained [2]
upstream, and all users are encouraged to switch to nose2 [3] or other
alternatives (plain unittest/unittest2 or pytest).

So if you want to package a new Python or PyPy module, please consider
not using nose there.

[1]: https://github.com/nose-devs/nose/blob/master/NEWS
[2]: https://groups.google.com/d/msg/nose-dev/rkofU1WdNNc/um9FRb19BQAJ
[3]: https://tracker.debian.org/pkg/nose2

--
Dmitry Shachnev

Bug#872523: fatal: refusing to merge unrelated histories

[Sean Whitton]

control: tag -1 +moreinfo

Hello Fred,

On Fri, Aug 18 2017, picca wrote:

> I just tryed to integrate the new propellor files into my
> repository, but this time I got this error message
>
> :~/LANG=C git merge upstream/master
> fatal: refusing to merge unrelated histories
>
> I do not think that this is normal ;).
> it used to work previously, so maybe something went wrong during the 
> packaging...
> or git changed its behaviour...

git changed its behaviour, but there was a fix added to DotDir.hs some
time ago.  What version are you upgrading from?  Please look in
DotDir.hs in your repo for the string

--allow-unrelated-histories

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#541306: g15daemon: Fail to install when required hardware is not present

[manu]

On Thu, 13 Aug 2009 10:43:30 +0200 "Giacomo A. Catenazzi"
 wrote:
> Petter Reinholdtsen wrote:
> > I just tried to install the g15daemon package on a Dell Latitude D505,
> > and there the package failed to install because the init.d script
> > return an error exit code (1).  The messages sent to syslog indicate
> > that the daemon failed to start because the supported hardware was not
> > found.  I belive it should be possible to install the package even if
> > the supported hardware is missing.
> 
> Yes, it is a know problem, and it was one of the reason of my
> recent post in debian-devel. Few hours ago I uploaded a new version,
> which finally use udev, and I hope I corrected all the possible
> error, when hardware is not present (but I still need to test it
> extensively).
> 
> > Also, the LSB header in the init.d script lack a dependency on
> > $syslog, making the daemon start before syslog is available.  As the
> > daemon log to syslog, its init.d script should depend on $syslog.
> 
> Ok. I forgot this.
> 
> ciao
>   cate
> 
> PS: next week I'll do more testing about the init.d script of this package
> (case without hardware, and with less common architectures) and about
> sysvinit -> insserv timing, but I wait for my null-modem cable
> 
> 
> 
Hello,

For information it seems the problem still occurs : upgrade from jessie
to stretch failed because the G15 is not connected at this time :

Setting up g15daemon (1.9.5.3-8.3+b1) ...
Job for g15daemon.service failed. See 'systemctl status
g15daemon.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript g15daemon, action "start" failed.
dpkg: error processing package g15daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 g15daemon
E: Sub-process /usr/bin/dpkg returned an error code (1)


# systemctl status g15daemon.service
● g15daemon.service - LSB: load deamon for Logitech G15 keyboard lcd display
   Loaded: loaded (/etc/init.d/g15daemon)
   Active: failed (Result: exit-code) since ven. 2017-08-18 19:35:09
CEST; 1min 5s ago
  Process: 29497 ExecStart=/etc/init.d/g15daemon start (code=exited,
status=1/FAILURE)

août 18 19:35:09 lambda g15daemon[29529]: Unable to attach to the G15
Keyboard... exiting
août 18 19:35:09 lambda g15daemon[29497]: Starting g15daemon:
.../dev/input/uinput not found ...
août 18 19:35:09 lambda systemd[1]: g15daemon.service: control process
exited, code=exited status=1
août 18 19:35:09 lambda systemd[1]: Failed to start LSB: load deamon for
Logitech G15 keyboard lcd display.
août 18 19:35:09 lambda systemd[1]: Unit g15daemon.service entered
failed state.


Regards,

Manu

Bug#872438: [Pkg-javascript-devel] Bug#872438: Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Jérémy Lal]

James Cowgill replied this to my give back request on mip64el:

> My guess is this GCC-7 bug which is breaking lots of stuff on mips64el
> at the moment:
> https://bugs.debian.org/871514

> Thanks,
> James

Cheers,

Jérémy

Bug#870204: RFS: openfst/1.6.3-1 -- weighted finite-state transducers library

[Giulio Paci]

Il 18/ago/2017 16:20, "Adam Borowski"  ha scritto:
> Let's upload openfst now, then opengrm-ngram once openfst passes binNEW
and
> hits the buildds.  phonetisaurus can be ignored for now -- it will be
> uninstallable but people who already have it installed have libfst4 which
> satisfies its needs.
>
>
> Does this sound good to you?

It sounds good to me.

Cheers,
Giulio

Bug#868550: [pkg-gnupg-maint] Bug#868550: reprepro seems to provide a repro

[Ian Jackson]

NIIBE Yutaka writes ("Re: [pkg-gnupg-maint] Bug#868550: reprepro seems to 
provide a repro"):
> Ian Jackson  wrote:
> >gpg --ignore-time-conflict
> >  --no-options
> >  --no-default-keyring
> >  --homedir
> >  /tmp/apt-key-gpghome.yLlu1bwwPI
> >  --no-auto-check-trustdb
> >  --trust-model
> >  always
> >  --batch
> >  --import
> 
> Thank you for minimizing.  I'd like to clarify the case.  Is this
> importing private key?

I think so, but I'm not sure.

> The invocation of gpg-agent by gpg frontend has an inherent race in the
> current implementation; When gpg frontend invokes gpg-agent, after
> spawning gpg-agent, gpg frontend tries to connect five times with one
> second intervals.  When a machine is busy enough and scheduling of
> processes goes not that fair, the connection to gpg-agent from gpg
> frontend may fail.

This might be relevant.  My test suite failures occur on a loaded
machine, because the test case runner parallelises separate tests.

Does this produce a particular message, when it occurs ?

There are other possible approaches to this situation than to hope to
win the race.  But I hesitate to suggest adding additional code to
this area, having seen what's there already...

If you would like to suggest a debug printf, or name lines of source
code, I can probably arrange to see if this is happening.

Ian.

Bug#872438: [Pkg-javascript-devel] Bug#872438: src:nodejs: FTBFS on mips64el: Can't determine the arch of ./node

[Bastien ROUCARIES]

Starting program: /home/rouca/nodejs-6.11.2~dfsg/node
warning: GDB can't find the start of the function at 0xfff7fcd0c4.
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".
warning: GDB can't find the start of the function at 0xfff7fcddc8.
[New Thread 0xfff59db1e0 (LWP 516)]
[New Thread 0xfff59bb1e0 (LWP 517)]
[New Thread 0xfff51bb1e0 (LWP 518)]
[New Thread 0xfff49bb1e0 (LWP 521)]
[New Thread 0xfff41bb1e0 (LWP 522)]

Thread 1 "node" received signal SIGBUS, Bus error.
0x0001 in ?? ()
(gdb) info register
  zero   at   v0   v1
 R0    00ffda68 4500d051 53731e19
a0   a1   a2   a3
 R4   0001 00ffda98 000120f81220 2ee04241
a4   a5   a6   a7
 R8   2ee63501 2ee41019 0003 0003
t0   t1   t2   t3
 R12  35436b00 84080018 811372e0 0009
s0   s1   s2   s3
 R16  0001 00ffda98 0001 
s4   s5   s6   s7
 R20  2ee635c8 beeddead 000120f81258 2ee3ed41
t8   t9   k0   k1
 R24  000120f82cc8 0001 0015 
gp   sp   s8   ra
 R28  000120f424b0 00ffda60 00ffda88 3540610c
status   lo   hi badvaddr
  04109cf3 604189374cdec514 00ebe2a5 0001
 cause   pc
  00800010 0001
  fcsr  fir  restart
  dc64 00739600 
(gdb) bt
warning: GDB can't find the start of the function at 0x3540610b.
#0  0x0001 in ?? ()
#1  0x3540610c in ?? ()
(gdb) frame
#0  0x0001 in ?? ()
(gdb)

Bug#847003: ITP: connid -- framework for provisioning identities to repositories

[Christopher Hoskin]

Package: wnpp
Followup-For: Bug #847003
Owner: Christopher Hoskin 

Work in progress here:

https://anonscm.debian.org/cgit/pkg-java/connid.git/

Christopher

Bug#789567: [pkg-wicd-maint] Bug#789567: wicd: needs systemd integration

[Axel Beckert]

Hi Laurent,

Laurent Bigonville wrote:
> You should give this a try, this might fix the issues where the
> network is stopped before the mount points are unmounted.

Thanks for the patch!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#789567: wicd: needs systemd integration

[Laurent Bigonville]

And of course, I forgot to attach the patch...


Le 18/08/17 à 18:34, Laurent Bigonville a écrit :

tags 789567 + patch
User pkg-systemd-maintain...@lists.alioth.debian.org
Usertags 789567 + integration systemd-units
thanks

Hi,

I'm not personally using wicd but you can find here a patch to 
installing the .service file for the systemd support.


You should give this a try, this might fix the issues where the 
network is stopped before the mount points are unmounted.


If it's not working as expected, don't hesitate to ask the Debian 
systemd developers to assist you to integrate wicd.


Cheers,

Laurent Bigonville


diff -Nru wicd-1.7.4+tb2/debian/changelog wicd-1.7.4+tb2/debian/changelog
--- wicd-1.7.4+tb2/debian/changelog	2017-05-28 22:20:00.0 +0200
+++ wicd-1.7.4+tb2/debian/changelog	2017-08-18 18:24:02.0 +0200
@@ -1,3 +1,9 @@
+wicd (1.7.4+tb2-4.1) UNRELEASED; urgency=medium
+
+  * Install systemd dbus .service files (Closes: #789567)
+
+ -- Laurent Bigonville   Fri, 18 Aug 2017 18:24:02 +0200
+
 wicd (1.7.4+tb2-4) unstable; urgency=medium
 
   [ Axel Beckert ]
diff -Nru wicd-1.7.4+tb2/debian/control wicd-1.7.4+tb2/debian/control
--- wicd-1.7.4+tb2/debian/control	2017-05-08 00:41:25.0 +0200
+++ wicd-1.7.4+tb2/debian/control	2017-08-18 18:23:02.0 +0200
@@ -4,7 +4,7 @@
 Maintainer: Debian WICD Packaging Team 
 Uploaders: Axel Beckert ,
Giap Tran 
-Build-Depends: debhelper (>= 9~),
+Build-Depends: debhelper (>= 9.20160709~),
dh-python,
python (>= 2.6.6-3~)
 Build-Depends-Indep: gettext,
diff -Nru wicd-1.7.4+tb2/debian/rules wicd-1.7.4+tb2/debian/rules
--- wicd-1.7.4+tb2/debian/rules	2016-05-23 23:24:47.0 +0200
+++ wicd-1.7.4+tb2/debian/rules	2017-08-18 18:23:56.0 +0200
@@ -8,7 +8,7 @@
 export LANG=C
 
 %:
-	dh $@ --with python2
+	dh $@ --with python2,systemd
 
 override_dh_auto_configure:
 	if [ -e wicd/wpath.py ]; then cp -pf wicd/wpath.py debian/; fi
diff -Nru wicd-1.7.4+tb2/debian/wicd-daemon.install wicd-1.7.4+tb2/debian/wicd-daemon.install
--- wicd-1.7.4+tb2/debian/wicd-daemon.install	2016-05-23 23:24:47.0 +0200
+++ wicd-1.7.4+tb2/debian/wicd-daemon.install	2017-08-18 18:19:48.0 +0200
@@ -1,7 +1,9 @@
 etc/dbus-1/
 etc/wicd/
+lib/systemd/system/
 usr/lib/pm-utils/
 usr/sbin/
+usr/share/dbus-1/system-services/
 usr/share/locale/
 usr/share/man/nl/man5/
 usr/share/man/nl/man8/wicd.8

Bug#872562: Please provide a stable backport of biboumi

[Jonas Smedegaard]

Hi Martin,

Quoting W. Martin Borgert (2017-08-18 17:49:44)
> It would be nice, if users of stable could use biboumi, too.
> 
> Also, the Debian XMPP server could maybe provide an IRC gateway, if 
> there were a backport to stretch.

Thanks for the suggestion.

I do not currently have any plans to get involved with the bpo 
side-project of Debian.  Others are quite welcome to step up to do that.

I take pride in ensuring that packages are easy backportable: Please 
file bugreports - just make sure (as always) to mention at which version 
of Debian the bug was found.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#789567: wicd: needs systemd integration

[Laurent Bigonville]

tags 789567 + patch
User pkg-systemd-maintain...@lists.alioth.debian.org
Usertags 789567 + integration systemd-units
thanks

Hi,

I'm not personally using wicd but you can find here a patch to 
installing the .service file for the systemd support.


You should give this a try, this might fix the issues where the network 
is stopped before the mount points are unmounted.


If it's not working as expected, don't hesitate to ask the Debian 
systemd developers to assist you to integrate wicd.


Cheers,

Laurent Bigonville

Bug#853658: Forwarded upstream

[Sebastiaan Couwenberg]

On Mon, 7 Aug 2017 08:49:19 +0100 Ghislain Vaillant wrote:
> control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194

Instead of packaging a snapshot as suggested by upstream, I suggest to
explicitly build the package with GCC 6 (as per the attached patch)(
until the new upstream release is available which builds successfully
with GCC 7.

Kind Regards,

Bas
diff --git a/debian/control b/debian/control
index dabad673..2afa097f 100644
--- a/debian/control
+++ b/debian/control
@@ -5,6 +5,8 @@ Section: science
 Priority: optional
 Build-Depends: cmake,
debhelper (>= 10),
+   gcc-6,
+   g++-6,
libblas-dev | libblas.so,
libboost-date-time-dev,
libboost-filesystem-dev,
diff --git a/debian/rules b/debian/rules
index 9e6a203e..0f4ad606 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,9 @@ export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic
 export DEB_CXXFLAGS_MAINT_APPEND = -Wall -pedantic
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
+export CC=gcc-6
+export CXX=g++-6
+
 # Common cmake options.
 CMAKE_BUILD_OPTIONS = \
 	-DBUILD_SHARED_LIBS=ON \

Bug#853658: Forwarded upstream

[Ghislain Vaillant]

On 18/08/17 17:26, Sebastiaan Couwenberg wrote:

On Mon, 7 Aug 2017 08:49:19 +0100 Ghislain Vaillant wrote:

control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194


Instead of packaging a snapshot as suggested by upstream, I suggest to
explicitly build the package with GCC 6 (as per the attached patch)(
until the new upstream release is available which builds successfully
with GCC 7.


That's a good point, though I am worried of the lack of response from 
upstream and lack of commit activity overall (compared to when I 
packaged the software initially).


Thanks for the patch, I'll incorporate it soon.

Ghis

Bug#872479: alsa-utils: alsa-restore.service uses /run which is tmpfs

[Grand T]

To ensure a full restore of all level ( PCM for example) i modify the service 
as below


[Unit]
Description=Save/Restore Sound Card State
Documentation=man:alsactl(1)
ConditionPathExists=!/etc/alsa/state-daemon.conf
ConditionPathExistsGlob=/dev/snd/control*
After=alsa-state.service

[Service]
Type=oneshot
RemainAfterExit=true
ExecStartPre=/bin/sleep 60
ExecStart=-/usr/sbin/alsactl -E HOME=/var/lib/alsa restore
ExecStop=-/usr/sbin/alsactl -E HOME=/var/lib/alsa store

So it is much better and done after all snd management

journalctl -b|grep -i -e alsa -e sound -e snd août 18 17:47:13 debian kernel: 
snd_hda_intel :02:00.1: Refused to change power state, currently in D3 août 
18 17:47:13 debian kernel: snd_hda_intel :02:00.1: Handle vga_switcheroo 
audio client août 18 17:47:13 debian kernel: snd_hda_intel :02:00.1: VGA 
controller is disabled août 18 17:47:13 debian kernel: snd_hda_intel 
:02:00.1: Delaying initialization août 18 17:47:13 debian kernel: 
snd_hda_codec_idt hdaudioC0D0: autoconfig for 92HD81B1X5: line_outs=1 
(0xd/0x0/0x0/0x0/0x0) type:speaker août 18 17:47:13 debian kernel: 
snd_hda_codec_idt hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) août 18 
17:47:13 debian kernel: snd_hda_codec_idt hdaudioC0D0: hp_outs=1 
(0xb/0x0/0x0/0x0/0x0) août 18 17:47:13 debian kernel: snd_hda_codec_idt 
hdaudioC0D0: mono: mono_out=0x0 août 18 17:47:13 debian kernel: 
snd_hda_codec_idt hdaudioC0D0: inputs: août 18 17:47:13 debian kernel: 
snd_hda_codec_idt hdaudioC0D0: Internal Mic=0x11 août 18 17:47:13 debian 
kernel: snd_hda_codec_idt hdaudioC0D0: Mic=0xa août 18 17:47:13 debian kernel: 
input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/sound/card0/input12 août 18 17:47:13 debian 
kernel: input: HDA ATI SB Mic as 
/devices/pci:00/:00:14.2/sound/card0/input13 août 18 17:47:13 debian 
kernel: input: HDA ATI SB Front Headphone as 
/devices/pci:00/:00:14.2/sound/card0/input14 août 18 17:47:15 debian 
systemd[1]: Reached target Sound Card. août 18 17:47:23 debian systemd[1]: 
Starting Save/Restore Sound Card State... août 18 17:47:46 debian kernel: 
snd_hda_intel :02:00.1: Start delayed initialization août 18 17:47:46 
debian kernel: snd_hda_intel :02:00.1: CORB reset timeout#2, CORBRP = 65535 
août 18 17:47:46 debian kernel: snd_hda_intel :02:00.1: no codecs 
initialized août 18 17:47:46 debian kernel: snd_hda_intel :02:00.1: 
initialization error août 18 17:48:23 debian systemd[1]: Started Save/Restore 
Sound Card State.

Bug#680386: closed by Bart Martens <ba...@quantz.debian.org> (closing RFP: ineptepub -- decrypt Adobe ADEPT-encrypted EPUB books)

[Christoph Anton Mitterer]

Control: reopen -1

Just because no one has stepped forward yet to package this, doesn't
mean that the interest in it is gone... and after all, this is what
RFPs are... *requests* for packaging.

smime.p7s
Description: S/MIME cryptographic signature

Bug#796212: bittornado: please make the build reproducible

[Chris Lamb]

tags 796212 + pending patch
thanks

I've uploaded dtaus 0.9-1.1 to DELAYED/15:
  
  dtaus (0.9-1.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Please make the build reproducible. (Closes: #777321)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for dtaus_0.9-1 dtaus_0.9-1.1

 changelog |7 +++
 rules |4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff -u dtaus-0.9/debian/changelog dtaus-0.9/debian/changelog
--- dtaus-0.9/debian/changelog
+++ dtaus-0.9/debian/changelog
@@ -1,3 +1,10 @@
+dtaus (0.9-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Please make the build reproducible. (Closes: #777321)
+
+ -- Chris Lamb   Fri, 18 Aug 2017 09:17:37 -0700
+
 dtaus (0.9-1) unstable; urgency=low
 
   * New upstream version
diff -u dtaus-0.9/debian/rules dtaus-0.9/debian/rules
--- dtaus-0.9/debian/rules
+++ dtaus-0.9/debian/rules
@@ -64,7 +64,7 @@
$(installdoc) README TODO debian/tmp/usr/share/doc/$(package)
$(installdoc) ChangeLog debian/tmp/usr/share/doc/$(package)/changelog
$(installdoc) dtaus.txt debian/tmp/usr/share/doc/$(package)
-   gzip -9f 
debian/tmp/usr/share/doc/$(package)/{changelog{,.Debian},README,dtaus.txt}
+   gzip -9fn 
debian/tmp/usr/share/doc/$(package)/{changelog{,.Debian},README,dtaus.txt}
#
$(installbin) -d debian/tmp/usr/share/doc/$(package)/examples
$(installdoc) dtaus.cls debian/tmp/usr/share/doc/$(package)/examples
@@ -76,7 +76,7 @@
$(installdoc) dtaus.1 debian/tmp/usr/share/man/man1
$(installbin) -d debian/tmp/usr/share/man/man5
$(installdoc) dtaus.5 debian/tmp/usr/share/man/man5
-   gzip -9 debian/tmp/usr/share/man/man?/*
+   gzip -9n debian/tmp/usr/share/man/man?/*
#
dpkg-shlibdeps debian/tmp/usr/bin/dtaus
dpkg-gencontrol -isp

Bug#777321: dtaus: please make the build reproducible

[Chris Lamb]

tags 777321 + pending patch
thanks

I've uploaded cgilib 0.6-1.1 to DELAYED/15:
  
  cgilib (0.6-1.1) unstable; urgency=medium
  
* Non-maintainer upload.
* Make the build reproducible. (Closes: #776935)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for cgilib_0.6-1 cgilib_0.6-1.1

 changelog |7 +++
 rules |4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff -u cgilib-0.6/debian/changelog cgilib-0.6/debian/changelog
--- cgilib-0.6/debian/changelog
+++ cgilib-0.6/debian/changelog
@@ -1,3 +1,10 @@
+cgilib (0.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Make the build reproducible. (Closes: #776935)
+
+ -- Chris Lamb   Fri, 18 Aug 2017 09:17:07 -0700
+
 cgilib (0.6-1) unstable; urgency=low
 
   * New upstream version
diff -u cgilib-0.6/debian/rules cgilib-0.6/debian/rules
--- cgilib-0.6/debian/rules
+++ cgilib-0.6/debian/rules
@@ -70,14 +70,14 @@
$(installdoc) CREDITS debian/tmp/usr/share/doc/$(package)/credits
$(installdoc) cgitest.c debian/tmp/usr/share/doc/$(package)/examples
$(installdoc) jumpto.c debian/tmp/usr/share/doc/$(package)/examples
-   gzip -9f debian/tmp/usr/share/doc/$(package)/changelog{,.Debian}
+   gzip -9fn debian/tmp/usr/share/doc/$(package)/changelog{,.Debian}
#
$(installbin) -d debian/tmp/usr/share/man/man{3,5}
for page in *.3; do \
  $(installdoc) $${page} debian/tmp/usr/share/man/man3/$${page}; \
done
$(installdoc) cgi.5 debian/tmp/usr/share/man/man5/cgi.5
-   gzip -9f debian/tmp/usr/share/man/man?/*
+   gzip -9fn debian/tmp/usr/share/man/man?/*
#
$(installbin) -d debian/tmp/usr/include
$(installdoc) cgi.h debian/tmp/usr/include

Bug#776935: cgilib: please make the build reproducible

[Chris Lamb]

tags 776935 + pending patch
thanks

I've uploaded bittornado 0.3.18-10.3 to DELAYED/15:
  
  bittornado (0.3.18-10.3) unstable; urgency=medium
  
* Non-maintainer upload.
* Make the build reproducible. (Closes: #796212)
* Add missing Build-Depends on dh-python.

The full debdiff is attached.


Regards,

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

 changelog |8 
 control   |2 +-
 rules |1 +
 3 files changed, 10 insertions(+), 1 deletion(-)

diff -Nru bittornado-0.3.18/debian/changelog bittornado-0.3.18/debian/changelog
--- bittornado-0.3.18/debian/changelog  2015-08-18 07:54:10.0 -0700
+++ bittornado-0.3.18/debian/changelog  2017-08-18 09:16:55.0 -0700
@@ -1,3 +1,11 @@
+bittornado (0.3.18-10.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Make the build reproducible. (Closes: #796212)
+  * Add missing Build-Depends on dh-python.
+
+ -- Chris Lamb   Fri, 18 Aug 2017 09:16:55 -0700
+
 bittornado (0.3.18-10.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru bittornado-0.3.18/debian/control bittornado-0.3.18/debian/control
--- bittornado-0.3.18/debian/control2015-08-18 07:54:10.0 -0700
+++ bittornado-0.3.18/debian/control2017-08-18 09:16:55.0 -0700
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Cameron Dale  
 Build-Depends: debhelper (>= 7)
-Build-Depends-Indep: python-all (>= 2.6.6-3~), docbook-to-man
+Build-Depends-Indep: python-all (>= 2.6.6-3~), docbook-to-man, dh-python
 Standards-Version: 3.8.4
 Vcs-Svn: svn://svn.debian.org/pkg-bittornado/bittornado/trunk
 Vcs-Browser: http://svn.debian.org/wsvn/pkg-bittornado/bittornado/trunk/
diff -Nru bittornado-0.3.18/debian/rules bittornado-0.3.18/debian/rules
--- bittornado-0.3.18/debian/rules  2015-08-18 07:52:23.0 -0700
+++ bittornado-0.3.18/debian/rules  2017-08-18 09:16:55.0 -0700
@@ -66,6 +66,7 @@
( cd debian/tmp/usr/bin && \
  for i in btcopyannounce btsethttpseeds btmaketorrentgui; \
  do mv $$i.py $$i || exit 1; done )
+   chmod 644 debian/tmp/usr/bin/btmakemetafile.py 
debian/tmp/usr/bin/btcompletedir.py
 
dh_installchangelogs 
dh_install --sourcedir=debian/tmp

Bug#857122: python-gdata: please make the build reproducible

[Chris Lamb]

Hi,

> Sent upstream here:
>
>  https://github.com/google/gdata-python-client/pull/56

Have pinged upstream.



Regards,

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

Bug#776376: dict-gazetteer2k: please make the build reproducible

[Chris Lamb]

tags 776376 + pending patch
thanks

I've uploaded dict-gazetteer2k 1.0.0-5.4 to DELAYED/15:
  
  dict-gazetteer2k (1.0.0-5.4) unstable; urgency=medium
  
* Non-maintainer upload.
* Make the build reproducible. (Closes: #776376)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diffstat for dict-gazetteer2k_1.0.0-5.3 dict-gazetteer2k_1.0.0-5.4

 changelog |7 +++
 rules |2 ++
 2 files changed, 9 insertions(+)

diff -u dict-gazetteer2k-1.0.0/debian/changelog 
dict-gazetteer2k-1.0.0/debian/changelog
--- dict-gazetteer2k-1.0.0/debian/changelog
+++ dict-gazetteer2k-1.0.0/debian/changelog
@@ -1,3 +1,10 @@
+dict-gazetteer2k (1.0.0-5.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Make the build reproducible. (Closes: #776376)
+
+ -- Chris Lamb   Fri, 18 Aug 2017 09:04:37 -0700
+
 dict-gazetteer2k (1.0.0-5.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u dict-gazetteer2k-1.0.0/debian/rules dict-gazetteer2k-1.0.0/debian/rules
--- dict-gazetteer2k-1.0.0/debian/rules
+++ dict-gazetteer2k-1.0.0/debian/rules
@@ -35,6 +35,8 @@
$(PYTHON) zipswriter.py
$(PYTHON) placeswriter.py
$(PYTHON) countieswriter.py
+   # Ensure deterministic mtime for dictzip to inherit
+   touch --date='@$(SOURCE_DATE_EPOCH)' *.dict
dictzip *.dict
 
touch build-stamp

Bug#872567: libidn2-0-dev can no longer satisfy cross Build-Depends

[Helmut Grohne]

Package: libidn2-0-dev
Version: 2.0.2-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:curl src:gnutls28 src:html-xml-utils src:libpsl 
src:wget src:wget2

The packages listed under affects cannot satisfy their cross
Build-Depends, because their dependency on libidn2-0-dev is
unsatisfiable. In general, Architecture: all packages can never satisfy
cross Build-Depends unless marked Multi-Arch: foreign. In this case,
such a marking would be fatal, because it would cause its dependency
libidn2-dev to be installed for the build architecture rather than the
host architecture. Thus libidn2-0-dev needs to be switched to
Architecture: any. Please apply the attached patch.

Helmut
diff --minimal -Nru libidn2-0-2.0.2/debian/changelog 
libidn2-0-2.0.2/debian/changelog
--- libidn2-0-2.0.2/debian/changelog2017-08-02 20:27:38.0 +0200
+++ libidn2-0-2.0.2/debian/changelog2017-08-18 16:48:33.0 +0200
@@ -1,3 +1,10 @@
+libidn2-0 (2.0.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch libidn2-0-dev back to arch:any again. Closes: #-1.
+
+ -- Helmut Grohne   Fri, 18 Aug 2017 16:48:33 +0200
+
 libidn2-0 (2.0.2-3) unstable; urgency=low
 
   * Rename libidn2-0-dev to libidn2-dev.
diff --minimal -Nru libidn2-0-2.0.2/debian/control 
libidn2-0-2.0.2/debian/control
--- libidn2-0-2.0.2/debian/control  2017-08-02 20:27:38.0 +0200
+++ libidn2-0-2.0.2/debian/control  2017-08-18 16:48:15.0 +0200
@@ -35,7 +35,7 @@
 
 Package: libidn2-0-dev
 Depends: libidn2-dev, ${misc:Depends}
-Architecture: all
+Architecture: any
 Priority: extra
 Section: oldlibs
 Description: Internationalized domain names (IDNA2008/TR46) transitional 
package

Bug#859715: Info received (resiprocate: Please migrate to openssl1.1 in Buster)

[Gregor Jasny]

There's also an upstream PR open:
https://github.com/resiprocate/resiprocate/pull/83