Bug#1061764: unattended-upgrades ftbfs with Python 3.12 as default

[Michael Vogt]

Hey Doko,

thanks for your bugreport. This is should be fixed in the git repo at github, 
at least a test-build with the python3 from experimental on debian/unstable 
build fine. I will look into a new release.

Cheers,
 Michael

On Mon, Jan 29, 2024, at 13:54, Matthias Klose wrote:
> Package: src:unattended-upgrades
> Version: 2.9.1+nmu4
> Severity: serious
> Tags: sid trixie ftbfs
> User: debian-pyt...@lists.debian.org
> Usertags: python3.12
>
> With python3-defaults from experimental, the package fails to build:
>
> [...]
> Running ./test_pep484.py with python3
> s
> --
> Ran 0 tests in 0.000s
>
> NO TESTS RAN (skipped=1)
> make[2]: *** [Makefile:9: check] Error 5
> make[2]: Leaving directory '/<>/test'
> make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
>
> 5 is a new exit value when all tests are skipped.

Bug#1016184: unattended-upgrades: Unattended-upgrades has file lock after completion

[Michael Vogt]

Thanks for your bugreport.

On Thu, Jul 28, 2022, at 19:34, Tim McConnell wrote:
> Package: unattended-upgrades
> Version: 2.9.1
> Severity: normal
> X-Debbugs-Cc: tmcconnell...@gmail.com
[..]
> Unattended-Upgrades runs successfully, but if I try to run `apt-get dist-
> upgrades' when packages are held back I get a message stating unattended
> upgrades has the file locked (I also get this with Gnome Software center). If 
> I
> search `ps -ux' for that PID it isn't there. Sometimes I can run `sudo
> unattended-upgrade --debug --dry-run' and the lock is released other times I
> have to reboot the computer. It seems it's completed but hasn't let go of the
> lock.
[..]

The log in /var/log/unattended-upgrades/unattended-upgrades.log might be
interesting here. However what you describe sounds quite puzzling, the lock
should only be held if there is an active PID of unattended-upgrades, If you
see this again, could you please open a new terminal and type:
$ ps afx | grep /proc//
$ sudo lsof -p 
$ date
$ tail /var/log/unattended-upgrades/unattended-upgrades.log

Also "--dry-run" should not influence the lock file. It might be the issue goes
away after some time and running --dry-run also takes some time so when
it finishes the lock is gone. Or some hidden bug of course.

Thanks,
 Michael

Bug#1011678: python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not been declared

[Michael Vogt]

Hey,

thanks for reaching out. Julian was kind enough to merge the fix in
https://salsa.debian.org/apt-team/apt/-/merge_requests/249
so as soon as apt gets a new upload this issue should be fixed.

Cheers,
 Michael

On Sat, Jul 23, 2022, at 23:33, Boyuan Yang wrote:
> X-Debbugs-CC: m...@debian.org j...@debian.org
>
> Hi,
>
> On Thu, 26 May 2022 08:41:04 +0200 Lucas Nussbaum  wrote:
>> Source: python-apt
>> Version: 2.3.0
>> Severity: serious
>> Justification: FTBFS
>> Tags: bookworm sid ftbfs
>> User: lu...@debian.org
>> Usertags: ftbfs-20220525 ftbfs-bookworm
>> 
>> Hi,
>> 
>> During a rebuild of all packages in sid, your package failed to build
>> on amd64.
>
> This is getting serious since an archive-wide rebuild to drop python3.9
> support was just made. Your package fails to build from source in the
> rebuild [1], which would block the python3.10-only transition [2].
>
> Please consider looking into this bug. If you have time, please also fix the
> other RC bug https://bugs.debian.org/994348 , which is also long overdue.
>
> Thanks,
> Boyuan Yang
>
>
> [1] https://buildd.debian.org/status/package.php?p=python-apt
> [2] https://release.debian.org/transitions/html/python3.10-only.html
>
> Attachments:
> * signature.asc

Bug#1011688: Thank you for the synaptic NMU

[Michael Vogt]

Hey,

just wanted to send a quick THANK YOU note for the NMU diff. I uploaded a new 
version of synaptic with it and various other collected fixes/changes. But I 
realized I did not reply with a thank you :)

Cheers,
 Michael

Bug#1014164: synaptic: 'Supported' column icon is now giant - too large for space allowed

[Michael Vogt]

Hey,

thanks for your bugreport. I mostly did not change things except for a rebuild 
so I wonder what is going on. Could you please try to move the /root/.synaptic 
folder (temporary) away and start with a fresh profile to see if that also 
shows the problem?

Thanks,
  Michael

On Fri, Jul 1, 2022, at 14:23, Steven Zalek wrote:
> Package: synaptic
> Version: 0.91.1
> Severity: minor
> X-Debbugs-Cc: zalek.ste...@gmail.com
>
> Dear Maintainer,
>
> What led up to the situation >> Updated the application to version 0.91.1
>
> The 'Supported' column icons now appear to be about double the original size.
> It is not possible to resize the column with to show the full icon symbol. The
> new icon size also affects the row height, which now appears to be taller.
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (800, 'testing'), (500, 'unstable'), (200, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages synaptic depends on:
> ii  hicolor-icon-theme   0.17-2
> ii  libapt-pkg6.02.5.0
> ii  libc62.33-7
> ii  libept1.6.0  1.2.1
> ii  libgcc-s112.1.0-2
> ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-1
> ii  libglib2.0-0 2.72.2-2
> ii  libgtk-3-0   3.24.34-1
> ii  libpango-1.0-0   1.50.7+ds-1
> ii  libstdc++6   12.1.0-2
> ii  libvte-2.91-00.68.0-1+b1
> ii  libxapian30  1.4.18-4
> ii  policykit-1  0.105-33
>
> Versions of packages synaptic recommends:
> ii  libgtk3-perl  0.038-1
> ii  xdg-utils 1.1.3-4.1
>
> Versions of packages synaptic suggests:
> pn  apt-xapian-index 
> ii  deborphan    1.7.35
> pn  dwww 
> pn  software-properties-gtk  
> ii  tasksel  3.69+rebuild
>
> -- no debconf information

-- 
  Michael Vogt
  michaelv...@imap.cc

Bug#1011688: Thank you!

[Michael Vogt]

Hey Boyuan Yang,

thank you so much your NMU and the diff. I will merge it into the git tree and 
may do a new upload with some more pending github fixes merged. Hope that is 
okay with you.

Thanks again for your help!
 Michael

Bug#1001999: snapd: packaging not up to Debian standards

[Michael Vogt]

Thanks for reaching out and reporting this bug. Fwiw, I did reply to the 
original mail too bug for some reason it seems that the reply did not made it 
to you, not sure what happened here, sorry for that.

I am preparing an upload of the latest 2.54.1 release of snapd that partly 
addresses the points you raised. Unfortunately I won't be able to fix it all in 
this upload (time constraints) but it should improve the situation quite a bit.

Thanks,
 Michael

Bug#1000979: snapd: Please upgrade go golang-1.17

[Michael Vogt]

Hi,

sorry for my late reply. I plan to update snapd to the upcoming 2.54
release before EOY and as part of this will also rebuild with 1.17.

Thanks,
 Michael

Bug#993783: snapd: AppArmor profile breaks snaps

[Michael Vogt]

Hi,

thanks for your bugreport. I can reproduce the issue and it seems like
it is triggered by the recent move to apparmor 3 in unstable. The
profile loading for snaps used to be done directly by apparmor but
with apparmor3 we need a patch in snapd to do it ourselfs. I will push
a fix ASAP (testing right now).

Sorry for the trouble,
 Michael

Bug#923500: snapd: non-classic snap not confined

[Michael Vogt]

Just a quick update - we looked at this and we think the apparmor
support in Debian is sufficient to enable it in snaps by
default.

This is being worked on in https://github.com/snapcore/snapd/pull/9936
and once that lands I will upload to Debian. The goal is within this
week.

In addition to the spread tests we manually validated some key snaps
and did not see regressions.

With that upload we can close this bug because snaps are confined on
Debian. Snaps will see the read only version of the "base" snap
(e.g. core or core20) and only what access is granted via snap
"interfaces". 

Cheers,
 Michael

Bug#956783: Please support go buildtags

[Michael Vogt]

On Wed, Apr 15, 2020 at 06:21:16PM +0800, Shengjing Zhu wrote:
> On Wed, Apr 15, 2020 at 4:54 PM Michael Vogt  wrote:
> >
> > Package: dh-golang
> > Version: 1.48
> >
> > It would be nice if dh-golang would support setting go buildtags.
> >
> > My use-case is a relatively large go application (snapd). It has a
> > buildtag (nosecboot) to exclude parts that are only relevant for
> > embedded systems. Right now I workaround this by removing files but
> > that is a bit of a ugly workaround.
> 
> I think you cat override dh_auto_* target, like:
> 
> override_dh_auto_build:
>dh_auto_build -- -tags nosecboot
> 
> Real examples are:
> https://salsa.debian.org/go-team/packages/runc/-/blob/master/debian/rules#L12

Thank you for your quick and reply and your suggestion! Yes, this
works and it is what I was doing so far and it works in most cases.

However it seems like it's not enough for some cases (like the latest
changes in snapd).

There are bits inside dh_golang that use "go list -f ..." without
considering tags and AFAICT with no way to add awareness for build
tags.

So in my case go list will also include the files that have the
"!secboot" tag which have extra go dependencies that are not available
in debian. This then makes the build fail.

Let me give an example, suppose we have foo.go:
"""
// +build !nosecboot

package foo
import "unavailable.pkg/in/debian"
""""

then "go list -f" will pickup the unavailalbe import (I hope this
explanation makes sense, happy to expand or give more concrete
examples). If there is a workaround for this, I would love to learn it
:)

Thanks,
 Michael

Bug#956783: Please support go buildtags

[Michael Vogt]

Package: dh-golang
Version: 1.48

It would be nice if dh-golang would support setting go buildtags.

My use-case is a relatively large go application (snapd). It has a
buildtag (nosecboot) to exclude parts that are only relevant for
embedded systems. Right now I workaround this by removing files but
that is a bit of a ugly workaround. Better support for buildtags would
solve this nicely. On fedora their rpm macro honors "BUILDTAGS" so I
was wondering if we should maybe support for a DH_GOLANG_BUILDTAGS
environment?

Attached is a very lightly tested patch that seems to be doing what I
want. But I'm really not a perl guy so someone should have a careful
look :)

Cheers,
 Michael
diff -Nru dh-golang-1.48/debian/changelog dh-golang-1.48+mvo1/debian/changelog
--- dh-golang-1.48/debian/changelog	2020-02-26 21:28:21.0 +0100
+++ dh-golang-1.48+mvo1/debian/changelog	2020-04-15 09:27:05.0 +0200
@@ -1,3 +1,9 @@
+dh-golang (1.48+mvo1) UNRELEASED; urgency=medium
+
+  * add support for DH_GOLANG_BUILDTAGS
+
+ -- Michael Vogt   Wed, 15 Apr 2020 09:27:05 +0200
+
 dh-golang (1.48) unstable; urgency=medium
 
   * Prevent "no non-test Go files" error during build
diff -Nru dh-golang-1.48/lib/Debian/Debhelper/Buildsystem/golang.pm dh-golang-1.48+mvo1/lib/Debian/Debhelper/Buildsystem/golang.pm
--- dh-golang-1.48/lib/Debian/Debhelper/Buildsystem/golang.pm	2020-02-26 21:28:21.0 +0100
+++ dh-golang-1.48+mvo1/lib/Debian/Debhelper/Buildsystem/golang.pm	2020-04-15 09:27:05.0 +0200
@@ -213,6 +213,11 @@
 Depending on what the Go package in question uses C for, you may
 want to enable C:
 
+=item DH_GOLANG_BUILDTAGS
+
+C (string, default empty) controls what build tags
+to use during the build.
+
 =over
 
 =item *
@@ -593,20 +598,20 @@
 my @targets = $this->get_targets();
 
 if (exists($ENV{DH_GOLANG_GO_GENERATE}) && $ENV{DH_GOLANG_GO_GENERATE} == 1) {
-$this->doit_in_builddir("go", "generate", "-v", @_, @targets);
+$this->doit_in_builddir("go", "generate","-tags", $ENV{DH_GOLANG_BUILDTAGS}, "-v", @_, @targets);
 }
 unshift @_, ('-p', $this->get_parallel());
 
 if (_go1_has_minor(13)) {
 # Go 1.13 officially supports reproducible build, adding new -trimpath option
 # https://github.com/golang/go/issues/16860
-$this->doit_in_builddir("go", "install", "-trimpath", "-v", @_, @targets);
+$this->doit_in_builddir("go", "install", "-tags", $ENV{DH_GOLANG_BUILDTAGS}, "-trimpath", "-v", @_, @targets);
 } elsif (_go1_has_minor(10)) {
 # Go 1.10 changed flag behaviour, -{gc,asm}flags=all= only works for Go >= 1.10.
 my $trimpath = "all=\"-trimpath=" . $ENV{GOPATH} . "/src\"";
-$this->doit_in_builddir("go", "install", "-gcflags=$trimpath", "-asmflags=$trimpath", "-v", @_, @targets);
+$this->doit_in_builddir("go", "install", "-tags", $ENV{DH_GOLANG_BUILDTAGS}, "-gcflags=$trimpath", "-asmflags=$trimpath", "-v", @_, @targets);
 } else {
-$this->doit_in_builddir("go", "install", "-v", @_, @targets);
+$this->doit_in_builddir("go", "install", "-tags", $ENV{DH_GOLANG_BUILDTAGS}, "-v", @_, @targets);
 }
 }
 
@@ -621,11 +626,11 @@
 # of many not-yet-fixed upstream packages, so we disable it for the time
 # being.
 if (_go1_has_minor(10)) {
-$this->doit_in_builddir("go", "test", "-vet=off", "-v", @_, @targets);
+$this->doit_in_builddir("go", "test", "-tags", $ENV{DH_GOLANG_BUILDTAGS}, "-vet=off", "-v", @_, @targets);
 } else {
 # For backwards-compatibility with Go < 1.10, which incorrectly
 # interprets the -vet=off flag as a target:
-$this->doit_in_builddir("go", "test", "-v", @_, @targets);
+$this->doit_in_builddir("go", "test", "-tags", $ENV{DH_GOLANG_BUILDTAGS}, "-v", @_, @targets);
 }
 }
 
diff -Nru dh-golang-1.48/script/dh_golang dh-golang-1.48+mvo1/script/dh_golang
--- dh-golang-1.48/script/dh_golang	2020-02-24 07:29:05.0 +0100
+++ dh-golang-1.48+mvo1/script/dh_golang	2020-04-15 09:27:05.0 +0200
@@ -74,7 +74,7 @@
 
 my $tmpl = '{{ range .Deps }}{{.}}
 {{ end }}';
-my @godeps = exec_single(qq{go list -f '$tmpl'}, @targets);
+my @godeps = exec_single(qq{go list -tags "$ENV{DH_GOLANG_BUILDTAGS}" -f '$tmpl'}, @targets);
 
 my $gofiletmpl = '\
 {{ .Dir }}/{{ index (or .GoFiles .CgoFiles .TestGoFiles .XTestGoFiles .IgnoredGoFiles) 0 }}';
@@ -84,7 +84,7 @@
 $gofiletmpl = '{{if not .Standard}}' . $gofiletmpl . '{{end}}';
 }
 
-my @gofiles = exec_chunked(qq{go list -f '$gofiletmpl'}, uniq(@godeps));
+my @gofiles = exec_chunked(qq{go list -tags "$ENV{DH_GOLANG_BUILDTAGS}" -f '$gofiletmpl'}, uniq(@godeps));
 
 my @realpath;
 foreach my $pathname (@gofiles) {

Bug#894790: Anything I can help with?

[Michael Vogt]

Hi,

just wanted to check if there is anything I can do to improve the
chance that this patch could get accepted? I'm happy to rework or add
tests as needed. My use-case is that I maintain a package that uses a
symlink for the "debian" dir and after each gbp update I apply my
patch (which is not a big deal, just would be slightly easier to not
have to do it :)

Thanks!
 Michael

Bug#891877: Have either synaptic removed or have it rebuilt with libgtk3-perl in it recommends.

[Michael Vogt]

On Sun, Oct 13, 2019 at 05:58:30AM +0200, intrigeri wrote:
> Hi,
Hi,

> shirish शिरीष:
> > Dunno if this is the right place to discuss it or not. Integri asked
> > hence sharing.
[..]
> AFAICT:
> 
>  - The synaptic codebase does not use libgtk2-perl directly.
>  - This Recommends is historically in place so that the user
>can benefit from debconf's GNOME frontend.
>  - debconf's GNOME frontend has been ported to libgtk3-perl 1.5 years
>ago (first released in 1.5.66):
>https://salsa.debian.org/pkg-debconf/debconf/commit/0250616b
> 
> Hence, the current "Recommends: libgtk2-perl" has been useless
> for a year an a half. With libgtk2-perl being phased out,
> this Recommends is now a more serious problem. On top of that,
> a suitable dependency on libgtk3-perl is missing.
> 
> Jeremy Bicha filed #891877 a while ago, requesting that Synaptic's
> dependencies are updated accordingly. I believe the actions Jeremy
> suggested on #891877 will solve the problem shirish is raising here,
> improve the life of Synaptic's users, and make it clearer what is the
> status of libgtk2-perl in the archive.
> 
> Thoughts?
> 
> (Oh my, so many words for a bug that can be fixed by s/2/3/ in one
> single place :)

Thanks for looking into this and sorry that this slipped my radar. I
updated the dependency in git and depending on urgency can do an
upload very soon - I guess we want one quickly?

Cheers,
 Michael

Bug#927155: synaptic: Idiotic dependencies after the upgrade to 0.84.6

[Michael Vogt]

On Mon, Oct 14, 2019 at 07:50:49AM +0300, jim_p wrote:
> Package: synaptic
> Followup-For: Bug #927155
> 
> Now that synaptic was updated to 0.84.7 and it no longer pulls zenity as a
> dependency, its dependencies have dropped to the minimal ones, so this issue
> can be closed.
> 
> I will open a new one on zenity, because its dependencies remain stupid.

Thank you! Yeah, I think its worthwhile to open a bug about this
dependency. And it was a valid bug against synaptic, I was considering
to write a small wrapper myself to avoid it but time is short :(

Fortunately this is resolved now. Fwiw, I would maybe use a word
slightly less negative than "idiotic" in the bugreport against zenity.

Cheers,
 Michael
 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages synaptic depends on:
> ii  hicolor-icon-theme  0.17-2
> ii  libapt-inst2.0  1.8.4
> ii  libapt-pkg5.0   1.8.4
> ii  libc6   2.29-2
> ii  libept1.5.0 1.1+nmu3+b1
> ii  libgcc1 1:9.2.1-8
> ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-1
> ii  libglib2.0-02.62.1-1
> ii  libgtk-3-0  3.24.12-1
> ii  libpango-1.0-0  1.42.4-7
> ii  libstdc++6  9.2.1-8
> ii  libvte-2.91-0   0.58.0-1
> ii  libxapian30 1.4.12-1
> ii  policykit-1 0.105-26
> 
> Versions of packages synaptic recommends:
> pn  libgtk2-perl  
> ii  xdg-utils 1.1.3-1
> 
> Versions of packages synaptic suggests:
> pn  apt-xapian-index 
> ii  deborphan1.7.31
> pn  dwww 
> pn  menu 
> pn  software-properties-gtk  
> ii  tasksel  3.55
> 
> -- no debconf information

Bug#915298: Thank you and +1

[Michael Vogt]

Hi Axel,

thanks for the NMU diff - the proposed patch looks good.

Cheers,
 Michael

Bug#911501: synaptic: search button seems to be disappeared

[Michael Vogt]

Hi bitfreak,
1;5202;0c
thanks for your bugreport.

On Sun, Oct 21, 2018 at 01:19:19AM +0200, bitfreak25 wrote:
> Package: synaptic
> Version: 0.84.4
> Severity: minor
> 
> Dear Maintainer,
> 
> after an update from synaptic 0.84.3 to 0.84.4 I couldn't find the search
> button in the left corner. It just take some time to realize it moved into 
> the right corner (together with the options button).
> 
> This is very confusing for previous users like me. It is also inappropriate
> for users with big sized displays where you need to move the mouse cursor 
> to the right corner and back, which takes a lot of time.
>
> So please revert this change.

Added Simon who suggested and implemented this change - Simon, any
idea what we can do to help bitfreak to make this easier? @bitfreak -
could you link to a screenshot how it looks like on your screen?

thanks,
 Michael


> bitfreak
> 
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.18.0-2-amd64 (SMP w/16 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
> LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages synaptic depends on:
> ii  hicolor-icon-theme   0.17-2
> ii  libapt-inst2.0   1.7.0
> ii  libapt-pkg5.01.7.0
> ii  libatk1.0-0  2.30.0-1
> ii  libc62.27-6
> ii  libcairo-gobject21.15.12-1
> ii  libcairo21.15.12-1
> ii  libept1.5.0  1.1+nmu3+b1
> ii  libgcc1  1:8.2.0-7
> ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
> ii  libglib2.0-0 2.58.1-2
> ii  libgnutls30  3.5.19-1
> ii  libgtk-3-0   3.24.1-2
> ii  libpango-1.0-0   1.42.4-3
> ii  libpangocairo-1.0-0  1.42.4-3
> ii  libpcre2-8-0 10.31-3
> ii  libstdc++6   8.2.0-7
> ii  libvte-2.91-00.54.1-1
> ii  libx11-6 2:1.6.7-1
> ii  libxapian30  1.4.7-4
> ii  policykit-1  0.105-21
> ii  zlib1g   1:1.2.11.dfsg-1
> 
> Versions of packages synaptic recommends:
> ii  libgtk2-perl   2:1.24992-1+b1
> ii  rarian-compat  0.8.1-6+b1
> ii  xdg-utils  1.1.3-1
> 
> Versions of packages synaptic suggests:
> pn  apt-xapian-index 
> pn  deborphan
> pn  dwww 
> pn  menu 
> pn  software-properties-gtk  
> ii  tasksel  3.46
> 
> -- no debconf information

Bug#710442: Intent to NMU squid-deb-proxy to fix longstanding l10n bugs

[Michael Vogt]

On Wed, Aug 15, 2018 at 08:33:35PM +0200, Helge Kreutzmann wrote:
> Hello Michael,
HI Helge,

> I intend to NMU squid-deb-proxy early September to fix longstanding l10n
> bugs[1]. The changelog would be something like the following:
> 
>   * Non-maintainer upload.
>   * debian/po/pt.po:
> - add (updated) Portuguese translation of squid-deb-proxy debconf 
> messages,
>   thanks to Rui Branco (closes: #710442, #858747))
> 
> Please tell me if you are currently preparing a new release yourself
> and would like me to skip the NMU.

If you have the NMU ready please go ahead and upload it. Thanks for
your help with fixing those!

Thanks,
 Michael

Bug#894790: [patch] Please support repos that have a debian/ symlink

[Michael Vogt]

package: git-buildpackage
version: 0.9.8

We have a git repo that contains debian packaging under
packaging/- and we use a "debian" symlink to the
right packaging subdir that is part of the git tree. 

When trying to use `gbp buildpackage` to build such a git repo it will
fail because it uses "git show HEAD:debian/changelog" which does not
understand symlinks and errors. It would be great if building such a
tree would work :)

One possible fix is to use:

   git cat-file --follow-symlinks --batch

and pipe the wanted thing in (and cut the header). I attached a
(trivial) patch that does exactly this. It makes my repo build but I
did not test further than that. Please let me know if this looks
reasonable, if so I'm happy to adjust the patch further as needed.

Thanks for your consideration!

Cheers,
 Michael
diff -Nru git-buildpackage-0.9.8/gbp/git/repository.py git-buildpackage-0.9.8.1/gbp/git/repository.py
--- git-buildpackage-0.9.8/gbp/git/repository.py	2018-03-16 13:00:14.0 +0100
+++ git-buildpackage-0.9.8.1/gbp/git/repository.py	2018-04-04 11:45:10.0 +0200
@@ -1639,11 +1639,11 @@
 
 @rtype: C{bytestr}
 """
-obj, stderr, ret = self._git_inout('show', ["--pretty=medium", id],
-   capture_stderr=True)
+obj, stderr, ret = self._git_inout("cat-file", ["--follow-symlinks", "--batch="], input=id.encode("utf-8"), capture_stderr=True)
 if ret:
 raise GitRepositoryError("can't get %s: %s" % (id, stderr.decode().rstrip()))
-return obj
+# skip the first line, it contains aheader
+return obj[1:]
 
 def grep_log(self, regex, since=None):
 """

Bug#892028: unattended-upgrades: too slow to be unattended

[Michael Vogt]

On Sun, Mar 04, 2018 at 11:51:31AM +0100, Benoît wrote:
1;4804;0c> Package: unattended-upgrades
> Version: 1.0
> Severity: important

Thanks for your bugreport.
 
> Dear Maintainer,
> 
> on my modest laptop, I can definitely tell when unattended-upgrades is
> running every morning because it causes my CPU's fan to go full speed
> for at least an hour.
> 
> $ time unattended-upgrade --download-only
> 
> real  15m40,254s
> user  14m35,468s
> sys   0m50,685s
> 
> This seems unreasonable.
> I'm attaching a cProfile output of the same command.
> (Took 52min to run).

Hm, that is an unusually large runtime. What does your sources.list
look like? How many packages are upgradable. The output of
$ sudo unattended-upgrades --debug --dry-run
might give some clues.

Cheers,
 Michael

> apt.systemd.daily calls it twice:
> 
> root 14038 13985 99 10:34 pts/400:15:35 
> /usr/bin/python3 /usr/bin/unattended-upgrade --download-only
> root 14538 13985 99 10:50 pts/400:50:50 
> /usr/bin/python3 /usr/bin/unattended-upgrade
> 
> Yes, that's 65 minutes of full CPU time.
> 
> 
> For the record, aptitude full-upgrade gives me a plan in 11 seconds.
> 
> 
> 
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
> LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages unattended-upgrades depends on:
> ii  debconf  1.5.63
> ii  lsb-base 9.20170808
> ii  lsb-release  9.20170808
> ii  python3  3.6.4-1
> ii  python3-apt  1.4.0~beta3+b1
> ii  ucf  3.0036
> ii  xz-utils 5.2.2-1.3
> 
> Versions of packages unattended-upgrades recommends:
> ii  anacron 2.3-24
> ii  cron [cron-daemon]  3.0pl1-128.1
> 
> Versions of packages unattended-upgrades suggests:
> ii  bsd-mailx  8.1.2-0.20160123cvs-4
> ii  exim4-daemon-light [mail-transport-agent]  4.90.1-1
> pn  needrestart
> 
> -- Configuration Files:
> /etc/apt/apt.conf.d/50unattended-upgrades changed:
> // Unattended-Upgrade::Origins-Pattern controls which packages are
> // upgraded.
> //
> // Lines below have the format format is "keyword=value,...".  A
> // package will be upgraded only if the values in its metadata match
> // all the supplied keywords in a line.  (In other words, omitted
> // keywords are wild cards.) The keywords originate from the Release
> // file, but several aliases are accepted.  The accepted keywords are:
> //   a,archive,suite (eg, "stable")
> //   c,component (eg, "main", "contrib", "non-free")
> //   l,label (eg, "Debian", "Debian-Security")
> //   o,origin(eg, "Debian", "Unofficial Multimedia Packages")
> //   n,codename  (eg, "jessie", "jessie-updates")
> // site  (eg, "http.debian.net")
> // The available values on the system are printed by the command
> // "apt-cache policy", and can be debugged by running
> // "unattended-upgrades -d" and looking at the log file.
> //
> // Within lines unattended-upgrades allows 2 macros whose values are
> // derived from /etc/debian_version:
> //   ${distro_id}Installed origin.
> //   ${distro_codename}  Installed codename (eg, "buster")
> Unattended-Upgrade::Origins-Pattern {
> // Codename based matching:
> // This will follow the migration of a release through different
> // archives (e.g. from testing to stable and later oldstable).
> // Software will be the latest available for the named release,
> // but the Debian release itself will not be automatically upgraded.
> //  "origin=Debian,codename=${distro_codename}-updates";
> //  "origin=Debian,codename=${distro_codename}-proposed-updates";
> "origin=Debian,codename=${distro_codename},label=Debian";
> "origin=Debian,codename=${distro_codename},label=Debian-Security";
> // Archive or Suite based matching:
> // Note that this will silently match a different release after
> // migration to the specified archive (e.g. testing becomes the
> // new stable).
> //  "o=Debian,a=stable";
> //  "o=Debian,a=stable-updates";
> //  "o=Debian,a=proposed-updates";
> //  "o=Debian Backports,a=${distro_codename}-backports,l=Debian 
> Backports";
> };
> // List of packages to not update (regexp are supported)
> Unattended-Upgrade::Package-Blacklist {
> // "vim";
> // "libc6";
> // "libc6-dev";
> // "libc6-i686";
> };
> // This option allows you to control if on a unclean dpkg exit
> // unattended-upgrades will automatically run 
> //   dpkg 

Bug#888126: [patch] Please enable systemd-sysusers unit

[Michael Vogt]

Hi,

just a small update on this. systemd git master has the needed support
to reproduce the base-passwd passwd and group files now. The sysuers.d
conf file for this looks like this:

   
https://github.com/systemd/systemd/blob/master/test/TEST-21-SYSUSERS/test-5.input

and it generates output like this:

   
https://github.com/systemd/systemd/blob/master/test/TEST-21-SYSUSERS/test-5.expected-passwd
   
https://github.com/systemd/systemd/blob/master/test/TEST-21-SYSUSERS/test-5.expected-group

The only remaining problem is that it generates /sbin/nologin which we
do not have (we use /usr/sbin/nologin). But IMO that is not a blocker
we could make it a problem of the user (by recommending to the users
to create a symlink) - it may go away if UsrMerge takes off.

Cheers,
 Michael

Bug#888126: [patch] Please enable systemd-sysusers unit

[Michael Vogt]

On Mon, Jan 29, 2018 at 09:28:36AM +0100, Michael Vogt wrote:
> On Sat, Jan 27, 2018 at 10:20:46PM +0100, Martin Pitt wrote:
[..]
> Fixing this in the code is pretty trivial, we just need an OK from
> upstream how to do it (either by ensuing the uid:gid syntax never
> changes the uid/gid or via a new prefix/postfix like "!" to force
> creation).
[..]

Fwiw, I send https://github.com/systemd/systemd/pull/8037 which will
allow the reuse of IDs and added a test-case that replicates the
base-passwd master.{passwd,group} (modulo the /usr/sbin/nologin vs
/sbin/nologin issue and "sync" having a different login shell).

Cheers,
 Michael

Bug#888126: [patch] Please enable systemd-sysusers unit

[Michael Vogt]

On Sat, Jan 27, 2018 at 10:20:46PM +0100, Martin Pitt wrote:
[..]
> Michael Vogt [2018-01-23 16:15 +0100]:
> > sync:*:4:65534:sync:/bin:/bin/sync
> > 
> > which cannot be represented because you cannot specify a different
> > primary gid in the sysusers file (or a login shell). So extra work is
> > required for this but (personally) I would love to this is.
> 
> Since you freshly looked at this, was this the only problem? I figure the sync
> group is mostly unused anyway, and completely irrelevant for containers - but
> does this also affect static groups which are actually important? I. e. which
> static groups cannot be replicated with sysusers?

I think man is the important one, it has uid=6 gid=12. Also nobody and
nogroup share the same id but different names.

> IMHO if we enable this, we should also provide a reasonably correct static
> sysusers so that the program actually works as intended. It doesn't need to
> (and can't right now) be perfect, but at least not completely break your
> system.

Toally agree. To do that I pushed a PR to systemd
(https://github.com/systemd/systemd/pull/7973) to allow a new uid:gid
syntax. Fwiw, I'm impressed once more by the quality and speed of the
upstream code reviews.

With and the attached sysusers.d conf file we are closer but there is
the issue that some users/groups share the same ID, e.g. nouser and
nogroup. systemd-sysusers does not like that, it will pick a new
ID in this case.

Fixing this in the code is pretty trivial, we just need an OK from
upstream how to do it (either by ensuing the uid:gid syntax never
changes the uid/gid or via a new prefix/postfix like "!" to force
creation).

Then there is also a small issue incompatibility with the shell:
```
$ head -n2 passwd 
root:x:0:0::/root:/bin/sh
daemon:x:1:1::/usr/sbin:/sbin/nologin

$ head -n2 /usr/share/base-passwd/passwd.master 
root:*:0:0:root:/root:/bin/bash
daemon:*:1:1:daemon:/usr/sbin:/usr/sbin/nologin
```

For root it is "nologin" and the path of /sbin/nologin between Debian
and Fedora differs. Thats another open issue.

That seems to be the blockers for making this available
generally. What do you think?

Cheers,
 Michael

#Type  NameID GECOS Home directory
u  root 0 - /root
u  daemon   1 - /usr/sbin
u  bin  2 - /bin
u  sys  3 - /dev
g  adm  4 -
g  tty  5 -
g  disk 6 -
g  man 12-
u  sync 4:65534 - /bin
u  games5:60 - /usr/games
u  man  6:12 - /var/cache/man
u  lp   7 - /var/spool/lpd
u  mail 8 - /var/mail
u  news 9 - /var/spool/news
u  uucp10 - /var/spool/uucp
u  proxy   13 - /bin
g  kmem15 -
g  dialout 20 -
g  fax 21 -
g  voice   22 -
g  cdrom   24 -
g  floppy  25 -
g  tape26 -
g  sudo27 -
g  audio   29 -
g  dip 30 -
u  www-data33 - /var/www
u  backup  34 - /var/backups
g  operator37 -
u  list38 - /var/list
u  irc 39 - /var/run/ircd
g  src 40 -
u  gnats   41 - /var/lib/gnats
g  shadow  42 -
g  utmp43 -
g  video   44 -
g  sasl45 -
g  plugdev 46 -
g  staff   50 -
g  games   60 -
g  users  100 -
u  nobody   65534:65534 - /nonexistent
g  nogroup  65534 -

Bug#888126: [patch] Please enable systemd-sysusers unit

[Michael Vogt]

package: systemd
version: 236-3

Dear systemd team,


please enable the systemd-sysuser.service unit. The rational is that
users who want to use this inside their containers/deployments can do
so. Attached is a (trivial) patch to enable the unit. It is also
documented widely and the fact that it does not work on Debian (and
Ubuntu) is slightly surprising.

There is no downside (AFAICS), the unit is conditiional on
ConditionNeedsUpdate=/etc so it will never run on default Debian
systems. 

I also looked into providing debian specific basic.conf that would
re-generate the base-passwd passwd.master (and group) file. However it
looks like the systemd-sysusers file format is not expressive enough
for this (which is slightly unfortunate). I.e. we have entries like

sync:*:4:65534:sync:/bin:/bin/sync

which cannot be represented because you cannot specify a different
primary gid in the sysusers file (or a login shell). So extra work is
required for this but (personally) I would love to this is. 


Thanks for your consideration!
 Michael
 
>From 69af77164ce2eb9bdddfce1c397b9b0c1ae7da55 Mon Sep 17 00:00:00 2001
From: Michael Vogt <m...@ubuntu.com>
Date: Tue, 23 Jan 2018 15:55:38 +0100
Subject: [PATCH] Enable sysusers service units

This allows users who want to use /usr/lib/sysusers.d/* to use
it together with an empty /etc. Note that this PR does not ship
any sysuser.d files. It is up to the user to provide those.
---
 debian/rules | 1 -
 1 file changed, 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 0389867ec..0cc4b85ec 100755
--- a/debian/rules
+++ b/debian/rules
@@ -216,7 +216,6 @@ override_dh_install:
 	find debian/install/*/etc/systemd/system/ -type l -delete
 	# FIXME: generate proper sysusers.d/basic.conf for Debian, and add autopkgtest
 	rm -rf debian/install/*/usr/lib/sysusers.d/*
-	rm -f debian/install/*/lib/systemd/system/*sysusers*.service debian/install/*/lib/systemd/system/*/*sysusers*.service
 ifeq (, $(filter noudeb, $(DEB_BUILD_PROFILES)))
 	dh_install -pudev-udeb -plibudev1-udeb --sourcedir=debian/install/udeb
 endif
-- 
2.14.1

Bug#887984: [patch] boltdb for upcoming snapd 2.31

[Michael Vogt]

package: snapd
version: 2.31

The snapd package will use github.com/snapcore/bolt in the upcoming
2.31 release. This fork from github.com/boltdb/bolt just contains a
(trivial) built fix for powerpc. I attached a (quilt) patch that makes
the debian version switch back to the boltdb repo and will submit the
(trivial) patch to the debian package of golang-github-boltdb-bolt [1].

Fwiw, I also submited the fix boltdb upstream and to the coreos fork
of bolt. It was accepted by the later but the "official" boltdb repo
is currently not accepting patches.

Cheers,
 Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887983Indecription: Do not use a fork of github.com/boltdb/bolt
 Upstream uses a fork of this library to fix a built failure on powerpc.
 We can just fix the golang-github-boltdb-bolt-dev package with the
 relevant fix: https://github.com/snapcore/bolt/commit/9eca199504ee1299394669820724322b5bfc070a
Author: Michael Vogt <m...@debian.org>
Origin: vendor
Forwarded: not-needed
Last-Update: 2017-08-15: snapd/advisor/backend.go
===
--- snapd.orig/advisor/backend.go
+++ snapd/advisor/backend.go
@@ -23,7 +23,7 @@ import (
 	"strings"
 	"time"
 
-	"github.com/snapcore/bolt"
+	"github.com/boltdb/bolt"
 
 	"github.com/snapcore/snapd/dirs"
 )

Bug#887983: [patch] fix usage on powerpc

[Michael Vogt]

package: golang-github-boltdb-bolt
version: 1.3.1-1

Dear golang-github-boltdb-bolt maintainers,

attached is a debdiff with a fix to make packages that use boltdb work
on powerpc. The build currently fails because the "brokenUnaligned" is
not defined on powerpc.

I submited this fix upstream to
https://github.com/boltdb/bolt/pull/740 however upstream does not
accept PRs anymore (even for trivial fixes like this :(

I also send the fix to the coreos fork of bolt
(https://github.com/coreos/bbolt/pull/73) where it was accepted right
away.

Cheers,
 Michael


diff -Nru 
golang-github-boltdb-bolt-1.3.1/debian/patches/fix-powerpc-build.patch 
golang-github-boltdb-bolt-1.3.1/debian/patches/fix-powerpc-build.patch
--- golang-github-boltdb-bolt-1.3.1/debian/patches/fix-powerpc-build.patch  
1970-01-01 01:00:00.0 +0100
+++ golang-github-boltdb-bolt-1.3.1/debian/patches/fix-powerpc-build.patch  
2018-01-22 11:26:44.0 +0100
@@ -0,0 +1,22 @@
+Description: This fixes a built failure on powerpc (ppc in golang speak).
+ It was submited to bolt https://github.com/boltdb/bolt/pull/740 and
+ it was accepted in https://github.com/coreos/bbolt/pull/73
+Author: Michael Vogt <m...@ubuntu.com>
+Origin: vendor
+Bug: https://github.com/boltdb/bolt/pull/740
+Last-Update: 2018-01-22
+---
+ bolt_ppc.go | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/bolt_ppc.go b/bolt_ppc.go
+index 645ddc3..55cb8a7 100644
+--- a/bolt_ppc.go
 b/bolt_ppc.go
+@@ -7,3 +7,6 @@ const maxMapSize = 0x7FFF // 2GB
+ 
+ // maxAllocSize is the size used when creating array pointers.
+ const maxAllocSize = 0xFFF
++
++// Are unaligned load/stores broken on this arch?
++var brokenUnaligned = false
diff -Nru golang-github-boltdb-bolt-1.3.1/debian/patches/series 
golang-github-boltdb-bolt-1.3.1/debian/patches/series
--- golang-github-boltdb-bolt-1.3.1/debian/patches/series   2017-07-19 
21:11:48.0 +0200
+++ golang-github-boltdb-bolt-1.3.1/debian/patches/series   2018-01-22 
11:26:59.0 +0100
@@ -1 +1,2 @@
 Bug#849663_Fix_32bit_failures.patch
+fix-powerpc-build.patch


- End forwarded message -

Bug#883451: less: [patch] add lesspipe support for snaps

[Michael Vogt]

Package: less
Version: 481-2.1
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu  ubuntu-patch




In Ubuntu, the attached patch was applied to achieve the following:

  * debian/lesspipe:
- add snap support, thanks to Adam Collard


Thanks for considering the patch.

Cheers,
 Michael

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

Kernel: Linux 4.13.0-16-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)
diff -Nru less-481/debian/lesspipe less-481/debian/lesspipe
--- less-481/debian/lesspipe2016-07-22 15:55:47.0 +0200
+++ less-481/debian/lesspipe2017-11-28 10:22:35.0 +0100
@@ -192,6 +192,13 @@
rpm -q -l -p "$1"
else echo "rpm isn't available, no query on rpm 
package possible"; fi ;;
 
+*.snap)
+if [ -x "`which snap`" ]; then snap info "$1"; fi
+if [ -x "`which unsquashfs`" ]; then
+echo
+echo '*** Contents:'; unsquashfs -ll -d '' 
"$1" 
+else echo "No unsquashfs available"; fi ;;
+
*.tar.gz|*.tgz|*.tar.z|*.tar.dz)
tar tzvf "$1" --force-local
;;

Bug#858004: [patch] dpkg --root=/dir handles conffile transition incorrectly

[Michael Vogt]

Package: dpkg
Version: 1.18.23

As discussed on irc yesterday there is a bug in dpkg when a conffile
moves from pkg-a to pkg-b and the "dpkg --root=/dir" option is used.

The Ubuntu bugreport is
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1673247

Attached is a patch for the dpkg-tests.git repository that reproduces
the issue and a patch (from Guillem Jover) that fixes the issue. I
tested the patch both against the minimal test-case and also against
the "real" issue we were seeing on the Ubuntu live-cd with ubiquity.

Thanks,
 Michael
>From 4da6ee05156257972fc461b9e2b2634026354cc8 Mon Sep 17 00:00:00 2001
From: Michael Vogt <m...@ubuntu.com>
Date: Fri, 17 Mar 2017 08:36:44 +0100
Subject: [PATCH] add test for LP:1673247

---
 Makefile   |  1 +
 t-conffile-root-option/Makefile| 30 ++
 .../pkg-conff-a.v1/DEBIAN/conffiles|  1 +
 .../pkg-conff-a.v1/DEBIAN/control  |  8 ++
 .../pkg-conff-a.v1/test-conffile   |  1 +
 .../pkg-conff-a.v2/DEBIAN/control  |  8 ++
 .../pkg-conff-b.v1/DEBIAN/control  |  8 ++
 .../pkg-conff-b.v2/DEBIAN/conffiles|  1 +
 .../pkg-conff-b.v2/DEBIAN/control  |  8 ++
 .../pkg-conff-b.v2/test-conffile   |  1 +
 10 files changed, 67 insertions(+)
 create mode 100644 t-conffile-root-option/Makefile
 create mode 100644 t-conffile-root-option/pkg-conff-a.v1/DEBIAN/conffiles
 create mode 100644 t-conffile-root-option/pkg-conff-a.v1/DEBIAN/control
 create mode 100644 t-conffile-root-option/pkg-conff-a.v1/test-conffile
 create mode 100644 t-conffile-root-option/pkg-conff-a.v2/DEBIAN/control
 create mode 100644 t-conffile-root-option/pkg-conff-b.v1/DEBIAN/control
 create mode 100644 t-conffile-root-option/pkg-conff-b.v2/DEBIAN/conffiles
 create mode 100644 t-conffile-root-option/pkg-conff-b.v2/DEBIAN/control
 create mode 100644 t-conffile-root-option/pkg-conff-b.v2/test-conffile

diff --git a/Makefile b/Makefile
index 996fab1..75a34b9 100644
--- a/Makefile
+++ b/Makefile
@@ -137,6 +137,7 @@ TESTS_PASS += t-substvars
 TESTS_PASS += t-failinst-failrm
 TESTS_PASS += t-dir-extension-check
 TESTS_PASS += t-multiarch
+TESTS_PASS += t-conffile-root-option
 
 ifneq (,$(filter test-all,$(DPKG_TESTSUITE_OPTIONS)))
 TESTS := $(TESTS_PASS) $(TESTS_FAIL) $(TESTS_MANUAL)
diff --git a/t-conffile-root-option/Makefile b/t-conffile-root-option/Makefile
new file mode 100644
index 000..a0a
--- /dev/null
+++ b/t-conffile-root-option/Makefile
@@ -0,0 +1,30 @@
+TESTS_DEB := pkg-conff-a.v1 pkg-conff-a.v2 pkg-conff-b.v1 pkg-conff-b.v2
+
+include ../Test.mk
+
+TEST_CASES += test-conffile-travels-packages-no-rootdir test-conffile-travels-packages-rootdir
+
+test-case: $(TEST_CASES)
+
+test-conffile-travels-packages-no-rootdir:
+	# install base version
+	$(DPKG_INSTALL) pkg-conff-a.v1.deb pkg-conff-b.v1.deb
+	# instlal update, conffile traves from a to b
+	$(DPKG_INSTALL) pkg-conff-a.v2.deb pkg-conff-b.v2.deb
+	-$(DPKG_PURGE) pkg-conff-b
+	-$(DPKG_PURGE) pkg-conff-a
+
+test-conffile-travels-packages-rootdir:
+	# install base version
+	mkdir -p $(CURDIR)/target/var/lib/dpkg/info
+	mkdir -p $(CURDIR)/target/var/lib/dpkg/updates
+	touch $(CURDIR)/target/var/lib/dpkg/status
+	$(DPKG_INSTALL) --root=$(CURDIR)/target pkg-conff-a.v1.deb pkg-conff-b.v1.deb
+	# instlal update, conffile traves from a to b
+	$(DPKG_INSTALL) --root=$(CURDIR)/target pkg-conff-a.v2.deb pkg-conff-b.v2.deb
+	-$(DPKG_PURGE) --root=$(CURDIR)/target pkg-conff-b
+	-$(DPKG_PURGE) --root=$(CURDIR)/target pkg-conff-a
+
+test-clean:
+	-$(DPKG_PURGE) pkg-conff-a pkg-conff-b
+	-rm -rf $(CURDIR)/target
diff --git a/t-conffile-root-option/pkg-conff-a.v1/DEBIAN/conffiles b/t-conffile-root-option/pkg-conff-a.v1/DEBIAN/conffiles
new file mode 100644
index 000..4fad7e9
--- /dev/null
+++ b/t-conffile-root-option/pkg-conff-a.v1/DEBIAN/conffiles
@@ -0,0 +1 @@
+/test-conffile
diff --git a/t-conffile-root-option/pkg-conff-a.v1/DEBIAN/control b/t-conffile-root-option/pkg-conff-a.v1/DEBIAN/control
new file mode 100644
index 000..e97fe2e
--- /dev/null
+++ b/t-conffile-root-option/pkg-conff-a.v1/DEBIAN/control
@@ -0,0 +1,8 @@
+Package: pkg-conff-a
+Version: 1
+Section: test
+Priority: extra
+Maintainer: Dpkg Developers <debian-d...@lists.debian.org>
+Architecture: all
+Description: test package - conflicting conffile
+
diff --git a/t-conffile-root-option/pkg-conff-a.v1/test-conffile b/t-conffile-root-option/pkg-conff-a.v1/test-conffile
new file mode 100644
index 000..024da49
--- /dev/null
+++ b/t-conffile-root-option/pkg-conff-a.v1/test-conffile
@@ -0,0 +1 @@
+pkg-conff-a
diff --git a/t-conffile-root-option/pkg-conff-a.v2/DEBIAN/control b/t-conffile-root-option/pkg-conff-a.v2/DEBIAN/control
new file mode 100644
index 000..1174243
--- /dev/null
+++ b/t-conffile-root-option/pkg-conff-a.v2/DEBIAN/co

Bug#388255: Patch to fix this

[Michael Vogt]

On Sat, Jan 07, 2017 at 05:30:51PM +0100, Roderich Schupp wrote:
> Hi,
Hi,

> the attached patch ignores the bin-nmu suffix in the package version when
> computing getChangelogURI().
> It needs a compiler implementing C++11, though.
[..]

Thanks for the patch! It looks great. My only small concern is the
c++11 dependency. It needs gcc 4.9 AIUI which means that it won't work
on oldstable. Probably ok, I doubt people backport this far back.

Thanks,
 Michael

Bug#847538: Followup

[Michael Vogt]

Hi Josh,

On Wed, Jan 04, 2017 at 11:42:59PM -0800, Josh Triplett wrote:
> Following up on this.  Any chance of a version of synaptic with this
> patch included, before the freeze?

Yes, sorry. I really need a co-maintainer for synaptic :/

I uploaded this today (together with some more fixes from the BTS).

Cheers,
 Michael

Bug#849718: Can not reproduce from fresh git checkout

[Michael Vogt]

Hi,

I tried this from a fresh git build and can not reproduce it.  Could you
please double check that
"Settings/Preferences/Marking Changes/Ask to confirm changes that also
affect other packages"
is set?

Cheers,
 Michael

Bug#841763: unattended-upgrades: Breaks hard when apt is upgraded

[Michael Vogt]

On Sun, Oct 23, 2016 at 01:55:37PM +0200, Alexandre Detiste wrote:
> Le dimanche 23 octobre 2016, 13 h 43 min 59 s CEST Santiago Vila a écrit :
> > Aha! I can reproduce this too. On the machines where this happens,
> > I believe I answered "yes" to a debconf question about restarting
> > services automatically (one of the times I upgraded by hand and not
> > using unattended-upgrades).
> > 
> > Maybe something like this would work as a workaround?
> > 
> > echo "libc6 libraries/restart-without-asking boolean false" | 
> > debconf-set-selections
> > 
> > Thanks a lot.
> 
> Hi,
> 
> I think that adding this snippet to apt's debian/rules would fix this problem,
> not tested tough.
> 
> 
> 
> override_dh_systemd_start:
> dh_systemd_start apt-daily.timer
> 

Yes, I think you are right. This appears to be what is happening. I
have commited this fix to git and it will be part of the next upload.

Thanks,
 Michael

> 
> Without this override, we get this: apt got -daily.service got "try-restart"ed
> bit this statement in atp.postinst:
> -
> 
> 
> # Automatically added by dh_systemd_start
> if [ -d /run/systemd/system ]; then
> systemctl --system daemon-reload >/dev/null || true
> if [ -n "$2" ]; then
> _dh_action=try-restart
> else
> _dh_action=start
> fi
> deb-systemd-invoke $_dh_action apt-daily.service apt-daily.timer 
> >/dev/null || true
> fi
> # End automatically added section
> 
> 
> 
> 
> Greets,
> 
> Alexandre Detiste

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Michael Vogt]

On Mon, Jan 25, 2016 at 06:02:22PM +0330, Tsu Jan wrote:
> On Mon, 25 Jan 2016 12:17:45 +0100 Michael Vogt <m...@debian.org> wrote:
> > This is a bug indeed, the question is how it got triggered, that dir
> > should be owend by the _apt user.
> >
> > What is the output of:
> > $ ls -dl /var/cache/apt/archives/partial/
> >
> > Thanks,
> > Michael
> 
> That directory has been owned by root from time immemorial. I've never had
> an "_apt" user/group and no update created such a user/group. In other
> words, this is a *new* problem that started after a recent update (of apt?).
[..]

Thanks! If you do not have an _apt user, that appears to be the
problem. If I do:

  $ grep -B2 _apt /var/lib/dpkg/info/apt.postinst

I see that the postinst tries to create such a user. Is there anything
unusual about your system that might prevent creating this user? 

Thanks,
 Michael

Bug#810152: synaptic: Polish translation of News section is still clumsy (regression?)

[Michael Vogt]

On Thu, Jan 07, 2016 at 02:40:41AM +0100, Michal Szwaczko wrote:
> Package: synaptic
> Version: 0.82.5
> Severity: minor

Thanks!

> Dear Maintainer,
> 
> Polish translation of the "News" section is still clumsy.
> (I reported it some time ago: bug #613346). 
> 
> Source package's po/pl.po still contains this clumsy translation, 
> and so does the binary package.
> 
> Either it was never fixed, contrary to the original bug's closing note, 
> or it is a regression. This is annoying :)
> Polish term for News (understood as Newsgroups/Usenet) is 'Grupy dyskusyjne'
> not 'Grupy nowin'
> Hope it gets through finally :) 

I think that was a regression, thanks for letting me know. I fixed it
(again!) and I hope it stays fixed now :)

Cheers,
 Michael

> Regards
> Michal
> 
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages synaptic depends on:
> ii  hicolor-icon-theme   0.13-1
> ii  libapt-inst2.0   1.1.10
> ii  libapt-pkg5.01.1.10
> ii  libatk1.0-0  2.18.0-1
> ii  libc62.21-6
> ii  libcairo-gobject21.14.4-1
> ii  libcairo21.14.4-1
> ii  libept1.5.0  1.1+nmu3
> ii  libgcc1  1:5.3.1-4
> ii  libgdk-pixbuf2.0-0   2.32.3-1
> ii  libglib2.0-0 2.46.2-3
> ii  libgnutls-deb0-283.3.19-1
> ii  libgtk-3-0   3.18.6-1
> ii  libpango-1.0-0   1.38.1-1
> ii  libpangocairo-1.0-0  1.38.1-1
> ii  libstdc++6   5.3.1-4
> ii  libvte-2.91-00.42.1-2
> ii  libx11-6 2:1.6.3-1
> ii  libxapian22v51.2.21-1.2
> ii  zlib1g   1:1.2.8.dfsg-2+b1
> 
> Versions of packages synaptic recommends:
> ii  libgtk2-perl   2:1.2496-3+b1
> ii  policykit-10.105-14
> ii  rarian-compat  0.8.1-6
> ii  xdg-utils  1.1.1-1
> 
> Versions of packages synaptic suggests:
> pn  apt-xapian-index 
> ii  deborphan1.7.28.8-0.2
> pn  dwww 
> ii  menu 2.1.47
> pn  software-properties-gtk  
> pn  tasksel  
> 
> -- no debconf information

Bug#808802: #808802 synaptic: Can't drop privileges for downloading as file '/var/lib/apt/lists/partial/ftp.fr.debian.org_debian_dists_testing_InRelease'

[Michael Vogt]

On Tue, Jan 05, 2016 at 01:58:12PM +0330, Tsu Jan wrote:
> On Wed, 23 Dec 2015 11:01:29 +0100 Alexandre Detiste
>  wrote:
> > This is likely a duplicate of this (read from #15), IE, not a bug:
> 
> For me, in Debian Testing, the message is:
> 
> 
> W: Can't drop privileges for downloading as file
> '/var/cache/apt/archives/partial/PACKAGE' couldn't be accessed by user
> '_apt'. - pkgAcquire::Run (13: Permission denied)
> 
> This IS a bug for, at least, two reasons:
> 
> (1) The Synaptic user encounters such an unhelpful message after the
> download is complete;
> 
> (2) The message is not only unhelpful but also meaningless TO THE END USER
> because there's no '/var/cache/apt/archives/partial/PACKAGE' when the
> download in complete.

This is a bug indeed, the question is how it got triggered, that dir
should be owend by the _apt user.

What is the output of:
$ ls -dl /var/cache/apt/archives/partial/

Thanks,
 Michael

Bug#811857: synaptic: FTBFS with GCC 6: no matching function for call to

[Michael Vogt]

On Tue, Jan 19, 2016 at 06:47:08PM -0800, Martin Michlmayr wrote:
> Package: synaptic
> Version: 0.83
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-no-match

Thanks for your bugreport.

> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
> 
> Note that only the first error is reported; there might be more.  You
> can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
> you can set CC=gcc-6 CXX=g++-6 explicitly.
[..]

I fixed this in git and it will be part of the next upload.

Cheers,
 Michael

Bug#160743: Cleanup

[Michael Vogt]

Hi,

I agree with the idea that after a successful install/upgrade we want to
remove the downloaded
debs. There are setups (like pbuilder) that want to keep the cache files
but those seem to be
not the common case. Attached is a quick patch to implement the removal.
We can tweak
the name and the default for "Apt::Keep-Downloaded-Debs" of course :)
Test-case is missing
but will soon follow if there is agreement on this.

Cheers,
 Michael
diff --git a/apt-private/private-install.cc b/apt-private/private-install.cc
index 74a2424..f7dde47 100644
--- a/apt-private/private-install.cc
+++ b/apt-private/private-install.cc
@@ -346,6 +346,18 @@ bool InstallPackages(CacheFile ,bool ShwKept,bool Ask, bool Safety)
   c0out << _("Note: This is done automatically and on purpose by dpkg.") << std::endl;
}
 
+   // cleanup downloaded debs
+   if (_config->FindB("Apt::Keep-Downloaded-Debs", true) == false)
+   {
+  std::string const archivedir = _config->FindDir("Dir::Cache::archives");
+  for (auto I = Fetcher.ItemsBegin(); I != Fetcher.ItemsEnd(); ++I)
+  {
+	 if (flNotFile((*I)->DestFile) != archivedir)
+	continue;
+ RemoveFile("Keep-Downloaded-Debs=false", (*I)->DestFile);
+  }
+   }
+
return true;
 }
 	/*}}}*/
diff --git a/debian/apt.cron.daily b/debian/apt.cron.daily
index d3c9e04..7e976a0 100644
--- a/debian/apt.cron.daily
+++ b/debian/apt.cron.daily
@@ -62,6 +62,9 @@
 #  APT::Periodic::AutocleanInterval "0";
 #  - Do "apt-get autoclean" every n-days (0=disable)
 #
+#  APT::Periodic::CleanInterval "0";
+#  - Do "apt-get clean" every n-days (0=disable)
+#
 #  APT::Periodic::Verbose "0";
 #  - Send report mail to root
 #  0:  no report (or null string)
@@ -411,6 +414,9 @@ eval $(apt-config shell UnattendedUpgradeInterval APT::Periodic::Unattended-Upgr
 AutocleanInterval=0
 eval $(apt-config shell AutocleanInterval APT::Periodic::AutocleanInterval)
 
+CleanInterval=0
+eval $(apt-config shell CleanInterval APT::Periodic::CleanInterval)
+
 BackupArchiveInterval=0
 eval $(apt-config shell BackupArchiveInterval APT::Periodic::BackupArchiveInterval)
 
@@ -422,7 +428,8 @@ if [ $UpdateInterval -eq 0 ] &&
[ $DownloadUpgradeableInterval -eq 0 ] &&
[ $UnattendedUpgradeInterval -eq 0 ] &&
[ $BackupArchiveInterval -eq 0 ] &&
-   [ $AutocleanInterval -eq 0 ]; then
+   [ $AutocleanInterval -eq 0 ] &&
+   [ $CleanInterval -eq 0 ]; then
 
 # check cache size
 check_size_constraints
@@ -498,6 +505,19 @@ else
 debug_echo "unattended-upgrade (not run)"
 fi
 
+# clean package archive
+CLEAN_STAMP=/var/lib/apt/periodic/clean-stamp
+if check_stamp $CLEAN_STAMP $CleanInterval; then
+if  eval apt-get $XAPTOPT -y clean $XSTDERR; then
+	debug_echo "clean (success)."
+	update_stamp $CLEAN_STAMP
+else
+	debug_echo "clean (error)"
+fi
+else
+debug_echo "clean (not run)"
+fi
+
 # autoclean package archive
 AUTOCLEAN_STAMP=/var/lib/apt/periodic/autoclean-stamp
 if check_stamp $AUTOCLEAN_STAMP $AutocleanInterval; then

Bug#809428: unattended-upgrades: please add APT key to always do 'apt-get clean' after a succesfull upgrade

[Michael Vogt]

On Thu, Dec 31, 2015 at 12:26:29AM +0200, Martin-Éric Racine wrote:
> Package: unattended-upgrades
> Version: 0.86.4
> Severity: wishlist

Thanks for your bugreport.

I like this idea, I implemented it in:
https://github.com/mvo5/unattended-upgrades/commit/c0a9a1c429b2999bd23857149f01bae3995c840a

The default behavior is now to remove the downloaded .deb files after
successful installs. This the best default, the operation was
successful so why keep the files around. I added a option to override
this too just in case someone disagrees :) If so I would be curious to
know the use-cases to keep the downloaded debs around. I wonder if
this should not also be the default for apt itself.

Cheers,
 Michael

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Currently, the global key APT::Periodic::AutocleanInterval allows performing 
> 'apt-get autoclean' after N days. This is insufficient on systems that have 
> limitted storage space, since autoclean only clears downloaded packages that 
> no longer appear in the archive. What is needed is for 'apt-get clean' to be 
> performed, to remove all downloaded packages from the cache, but only after a 
> succesful unattended upgrade.
> 
> - -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (1001, 'testing'), (1001, 'stable'), (1001, 'oldstable')
> Architecture: i386 (i586)
> 
> Kernel: Linux 3.16.0-4-586
> Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages unattended-upgrades depends on:
> ii  apt1.1.5
> ii  apt-utils  1.1.5
> ii  debconf [debconf-2.0]  1.5.58
> ii  init-system-helpers1.24
> ii  lsb-base   9.20150917
> ii  lsb-release9.20150917
> ii  python33.4.3-7
> ii  python3-apt1.1.0~beta1
> ii  ucf3.0031
> ii  xz-utils   5.1.1alpha+20120614-2.1
> 
> Versions of packages unattended-upgrades recommends:
> ii  systemd-cron [cron-daemon]  1.5.3-1
> 
> Versions of packages unattended-upgrades suggests:
> ii  bsd-mailx  8.1.2-0.20150408cvs-1
> ii  nullmailer [mail-transport-agent]  1:1.13-1
> 
> - -- Configuration Files:
> /etc/logrotate.d/unattended-upgrades changed:
> /var/log/unattended-upgrades/unattended-upgrades.log 
> /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
> /var/log/unattended-upgrades/unattended-upgrades-shutdown.log
> {
>   rotate 6
>   daily
>   compress
>   missingok
>   notifempty
> }
> 
> 
> - -- debconf information:
> * unattended-upgrades/enable_auto_updates: true
>   unattended-upgrades/origins_pattern: 
> "origin=Debian,codename=${distro_codename},label=Debian-Security";
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQIcBAEBCAAGBQJWhFoPAAoJEK4fgnfEtNe2p7EP/34lPqW2bGSzeZvjk207ZRrT
> p/34fGA8avOTuY6Dr7gxL9cHdbFa2L/pA2nGgLe4jSyf0k9Qg6WIS5piIg7zGX4+
> QS27frJ9iqczwgfDZEIJ4A0ZXGPfedD1fCQRodFxKQ6BUYPqNe1GDldryuaLPtzh
> LSMClIeaxTTMKRg9a/hJA2wPB1wdIyssGzH53mQn7/HqKkKOIlWleFJHisYaxiSG
> +lpO5Uw1f8HfNnck0prp+9NuFsWe2BkoiOh9oji2CpqM34Wv3bgBQDYFdFUSkAIE
> EjviryDRdP2Ypq8IlS3+S2vwxplrFgVB7E6tXbF9LkQLMDJ4oCELx+KhAvtFvCse
> QDjAGU+oQWDe7VaTaY374Ctxs88YMgGJQ04GpOXnNQYINkmTtgztFspKiDCxdBxZ
> VOrhTP4+6E7eqxYw7TL+QiLFt/ry2A8/aQ3CQTPd41AKCez3iqOsevs9jvJ3Pid4
> yy+noF6CuvAXUHP2+CdhxPjJiUxbD8baDd4LocEH7s5Vcj4ashm404ZBApY99+En
> 4I28FQKzTF7eJUaPWVFKy6705s2/nDU5t9loO7jx85TKTJMqWb45ACppWt87hCYW
> NM2/Me9zn6Rx/IFxm71LO2kdvR9EsCQ3r+ibbrrYXlsd8AroB4KfsIu1DfpZF9OE
> QmlIdeOvWmGrDmLzUQJ8
> =b3y8
> -END PGP SIGNATURE-

Bug#788026: synaptic: Uses obsolete vte3 which is going away

[Michael Vogt]

On Sat, Aug 29, 2015 at 12:15:16PM +0200, Egmont Koblinger wrote:
> Hi,
Hi,

[..]
> - The big piece is spawning a process for the terminal, and here my
> patch is definitely incomplete as it'd require more thorough
> understanding of the code:
> 
> -- argv needs to be populated with the command to be launched
> -- the possible pty flags and spawn should be carefully revised
> -- I _think_ that whatever happened so far between the
> vte_whatever_fork() and the exec() [now I replaced vte_whatever_fork()
> by vte_whatever_spawn(), but I haven't traced down where the exec()
> happens], which I believe is probably what DoInstallPostFork() does,
> needs to be moved into the child_setup method of vte_whatever_spawn().
> It's going to be a bit of refactoring.
[..]

Thanks for your initial patch. I finally managed to look at this issue
and I updated the code. It was a bit tricky as synaptic really needs
forkpty() instad of spawn_{,a}sync support. But that should work
now. If you have time it would be awsome to test the latest git.

Cheers,
 Michael

Bug#798884: Synaptic, broken/empty History

[Michael Vogt]

On Thu, Dec 03, 2015 at 02:43:49PM +0800, xuzhen wrote:
> Oh, made a mistake in previous patch. Reupload a new one.

Thanks a bunch! I merged this and the previous patch and it works like
a charm again.

I will soon upload a new version with the fix. There are some more
deprecation warnings in the code, if you have a bit of time I would be
really thankful if you could have a look! I have unfortunately not
that much time these days :/

Thanks!
 Michael

Bug#806251: transition: apt

[Michael Vogt]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal

We would like to release a new apt that brings a ton of improvements
but also breaks the ABI (and has some small API change that affects
aptitude and packagekit, see below).

We prepared the package in experimental and double checked the rdepends
in an ubuntu PPA. There are some small and mostly internal API changes
as well. The affected packages were aptitude, synaptic and
packagekit. All of those have fixes ready for libapt-pkg5.0. Synaptic
just needs a rebuild, aptitude and packagekit are ready for upload and
will get uploaded by their maintainers once apt is in unstable. 

Thanks,
 Michael

Ben file:

title = "apt";
is_affected = .depends ~ /libapt-pkg4.16|libapt-inst1.7/ | .depends ~
"libept1.4
.16" | .depends ~ /libapt-pkg5.0|libapt-inst2.0|libept1.5.0/;
is_good = .depends ~ /libapt-pkg5.0|libapt-inst2.0|libept1.5.0/;
is_bad = .depends ~ /libapt-pkg4.16|libapt-inst1.7/ | .depends ~
"libept1.4.16";


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



signature.asc
Description: Digital signature

Bug#804870: synaptic - FR localisation patch

[Michael Vogt]

On Thu, Nov 12, 2015 at 04:09:07PM +0100, treb...@tuxfamily.org wrote:
> Package: synaptic
> Version: 0.82
> 
> Hi, please find attached a debdiff which adds French localisation to the
> fr.po file. I've been checking in the version 0.81-2 version (jessie stable
> version) and those 2 strings doesn't appear neither. So it could be
> backported as well.

Thanks! I commited the patch to git and it will be part of the
next upload.

Cheers,
 Michael

> Regards,
> Olivier

> Description: l10n FR
> Origin: LibraZiK
> Forwarded: not needed - already there upstream
> Author: Olivier Humbert 
> Reviewed-by:
> Last-Update: 2015 11 12
> 
> --- a/po/fr.po
> +++ b/po/fr.po
> @@ -1,15 +1,16 @@
>  # French translation for synaptic
> -# Copyright (c) 2011 Rosetta Contributors and Canonical Ltd 2011
> +# Copyright (c) 2011 Rosetta Contributors and Canonical Ltd 2011 and others.
>  # This file is distributed under the same license as the synaptic package.
>  # FIRST AUTHOR , 2011.
> +# Olivier Humbert , 2015.
>  #
>  msgid ""
>  msgstr ""
>  "Project-Id-Version: synaptic\n"
>  "Report-Msgid-Bugs-To: \n"
>  "POT-Creation-Date: 2011-02-10 09:41+0100\n"
> -"PO-Revision-Date: 2012-01-04 12:47+\n"
> -"Last-Translator: Bruno Patri \n"
> +"PO-Revision-Date: 2015-11-12 13:52+0100\n"
> +"Last-Translator: Olivier Humbert \n"
>  "Language-Team: French \n"
>  "Language: fr\n"
>  "MIME-Version: 1.0\n"
> @@ -2704,6 +2705,10 @@
>  msgid "Show for individual files"
>  msgstr "Afficher les d??tails par fichier"
>  
> +#: ../gtk/gtkbuilder/window_fetch.ui.h:1
> +msgid "Show individual files"
> +msgstr "Afficher les d??tails par fichier"
> +
>  #: ../gtk/gtkbuilder/window_changes.ui.h:1
>  msgid ""
>  "Mark additional required changes? @@ -3663,6 +3668,12 @@
>  msgid "Synaptic Package Manager"
>  msgstr "Gestionnaire de paquets Synaptic"
>  
> +#: ../data/com.ubuntu.pkexec.synaptic.policy.in.h:1
> +msgid "Authentication is required to run the Synaptic Package Manager"
> +msgstr ""
> +"Une authentification est requise pour ex??cuter le gestionnaire de paquets "
> +"Synaptic"
> +
>  #: ../gtk/rgfiltermanager.h:62
>  msgid "Includes"
>  msgstr "Inclut"

Bug#804309: unattended-upgrades: [INTL:de] Updated German debconf translation

[Michael Vogt]

On Sat, Nov 7, 2015, at 09:28, Chris Leick wrote:
> Package: unattended-upgrades
> Version: 0.86.6
> Severity: wishlist
> Tags: l10n patch

Thanks for this update! I commited it to git.

Thanks,
 Michael 
 
> Hi,
> 
> please find attached the newest German debconf translation of unattended-
> upgrades.
> 
> Kind regards,
> Chris.
> Email had 1 attachment:
> + de.po.gz
>   2k (application/gzip)

Bug#804136: [l10n:eu] unattended-upgrades 0.86.6: updated Basque translation

[Michael Vogt]

On Thu, Nov 05, 2015 at 11:23:43AM +0100, dooteo wrote:
> Package: unattended-upgrades
> Version: 0.86.6
> X-Debbugs-CC: debian-l10n-bas...@lists.debian.org
> Severity: wishlist
> Tags: l10n patch

Thanks a lot! I commited this to my git
feature/debconf-template-update branch.

Cheers,
 Michael
 

> Attached Basque translation. Please, could you add it for us?
> 
> Thanks and best regards,
> 
> Dooteo
> 

> # Basque translation for unattended-upgrades
> # Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
> # This file is distributed under the same license as the PACKAGE package.
> #
> # Piarres Beobide , 2008, 2009, 2015.
> # Iñaki Larrañaga Murgoitio , 2015.
> msgid ""
> msgstr ""
> "Project-Id-Version: unattended-upgrades 0.86.6\n"
> "Report-Msgid-Bugs-To: unattended-upgra...@packages.debian.org\n"
> "POT-Creation-Date: 2015-11-03 07:12+0100\n"
> "PO-Revision-Date: 2015-11-05 11:19+0100\n"
> "Last-Translator: Iñaki Larrañaga Murgoitio \n"
> "Language-Team: Basque \n"
> "Language: eu\n"
> "MIME-Version: 1.0\n"
> "Content-Type: text/plain; charset=UTF-8\n"
> "Content-Transfer-Encoding: 8bit\n"
> "X-Generator: Lokalize 1.5\n"
> "Plural-Forms: nplurals=2; plural=(n != 1);\n"
> 
> #. Type: boolean
> #. Description
> #: ../templates:2001
> msgid "Automatically download and install stable updates?"
> msgstr "Bertsio-berritze egonkorrak automatikoki deskargatu eta instalatu?"
> 
> #. Type: boolean
> #. Description
> #: ../templates:2001
> #| msgid ""
> #| "Applying updates on a frequent basis is an important part of keeping "
> #| "systems secure. By default, updates need to be applied manually using "
> #| "package  management tools. Alternatively, you can choose to have this "
> #| "system  automatically download and install security updates."
> msgid ""
> "Applying updates on a frequent basis is an important part of keeping systems 
> "
> "secure. By default, updates need to be applied manually using package  "
> "management tools. Alternatively, you can choose to have this system  "
> "automatically download and install important updates."
> msgstr ""
> "Maiztasunean oinarritutako bertsio-berritze ezarpenak sistema seguru "
> "mantentzearen zati garrantzitsu bat da. Lehenetsi gisa, eguneraketek "
> "paketeak kudeatzeko tresnak eskuz erabiltzea eskatzen dute. Bestela, "
> "sistema honek automatikoki eguneraketa garrantzitsuak deskargatzea eta "
> "instalatzea aukera dezakezu."
> 
> #. Type: string
> #. Description
> #: ../templates:3001
> msgid "Origins-Pattern that packages must match to be upgraded:"
> msgstr "Jatorriko eredua (bertsio-berrituko diren paketeekin bat etortzeko):"
> 
> #. Type: string
> #. Description
> #: ../templates:3001
> msgid "Please specify a value for the unattended-upgrades Origins-Pattern."
> msgstr ""
> "Galdetu gabe bertsio-berrituko diren 'Jatorriko eredua'ren balioa zehaztu."
> 
> #. Type: string
> #. Description
> #: ../templates:3001
> msgid ""
> "A package will be upgraded only if its metadata values match all the "
> "supplied keywords in the origin line."
> msgstr ""
> "Pakete bat bertsio-berrituko da baldin eta bere meta-datuen balioak "
> "emandako jatorriaren lerroko gako-hitz guztiekin bat etortzen bada."
> 

Bug#801166: [BTS#801166] templates://unattended-upgrades/{templates} : Final update for English review

[Michael Vogt]

On Fri, Oct 30, 2015 at 07:12:31AM +0100, Christian PERRIER wrote:
> Dear Debian maintainer,
> 
> On Monday, October 12, 2015, I notified you of the beginning of a review 
> process
> concerning debconf templates for unattended-upgrades.
> 
> The debian-l10n-english contributors have now reviewed these templates,
> and the final proposed changes are attached to this update to the
> original bug report.
> 
> Please review the suggested changes, and if you have any
> objections, let me know in the next 3 days.
[..]

Thanks a bunch! I created a git branch for the updated template and
the new translations and will commit all updates there until the
translation phase is over.

Thanks again!
 Michael

> However, please try to avoid uploading unattended-upgrades with these changes
> right now.
> 
> The second phase of this process will begin on Monday, November 02, 2015, 
> when I will
> coordinate updates to translations of debconf templates.
> 
> The existing translators will be notified of the changes: they will
> receive an updated PO file for their language.
> 
> Simultaneously, a general call for new translations will be sent to
> the debian-i18n mailing list.
> 
> Both these calls for translations will request updates to be sent as
> individual bug reports. That will probably trigger a lot of bug
> reports against your package, but these should be easier to deal with.
> 
> The call for translation updates and new translations will run until
> about Monday, November 23, 2015. Please avoid uploading a package with fixed 
> or changed
> debconf templates and/or translation updates in the meantime. Of
> course, other changes are safe.
> 
> Please note that this is an approximative delay, which depends on my
> own availability to process this work and is influenced by the fact
> that I simultaneously work on many packages.
> 
> Around Tuesday, November 24, 2015, I will contact you again and will send a 
> final patch
> summarizing all the updates (changes to debconf templates,
> updates to debconf translations and new debconf translations).
> 
> Again, thanks for your attention and cooperation.
> 
> 
> -- 
> 
> 

> # These templates have been reviewed by the debian-l10n-english
> # team
> #
> # If modifications/additions/rewording are needed, please ask
> # debian-l10n-engl...@lists.debian.org for advice.
> #
> # Even minor modifications require translation updates and such
> # changes should be coordinated with translators and reviewers.
> 
> Template: unattended-upgrades/enable_auto_updates
> Type: boolean
> Default: false
> _Description: Automatically download and install stable updates?
>  Applying updates on a frequent basis is an important part of keeping
>  systems secure. By default, updates need to be applied manually using 
> package 
>  management tools. Alternatively, you can choose to have this system 
>  automatically download and install important updates.
> 
> Template: unattended-upgrades/origins_pattern
> Type: string
> Default: "origin=Debian,codename=${distro_codename},label=Debian-Security";
> _Description: Origins-Pattern that packages must match to be upgraded:
>  Please specify a value for the unattended-upgrades Origins-Pattern.
>  .
>  A package will be upgraded only if its metadata values match all the supplied
>  keywords in the origin line.

> Source: unattended-upgrades
> Section: admin
> Priority: optional
> Maintainer: Michael Vogt <m...@debian.org>
> Build-Depends: debhelper (>= 7.0.50~), po-debconf
> Build-Depends-Indep: python (>= 2.6.6-3~), python3-distutils-extra,
>  python3-setuptools, python-dev, python3-dev, python-coverage, pep8,
>  pyflakes, python-apt, python3-apt, python-mock, python3-mock,
>  lsb-release, dh-systemd (>= 1.5)
> Standards-Version: 3.9.3
> Vcs-Git: https://github.com/mvo5/unattended-upgrades.git
> XS-Testsuite: autopkgtest
> 
> Package: unattended-upgrades
> Architecture: all
> Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, python3, 
>  python3-apt, apt-utils, apt, ucf, lsb-release, lsb-base (>= 3.2-14),
>  xz-utils
> Recommends: cron | cron-daemon | anacron
> Suggests: bsd-mailx, mail-transport-agent
> Description: automatic installation of security upgrades
>  This package can download and install security upgrades automatically
>  and unattended, taking care to only install packages from the
>  configured APT source, and checking for dpkg prompts about
>  configuration file changes.
>  .
>  This script is the backend for the APT::Periodic::Unattended-Upgrade
>  option.

> --- unattended-upgrades.old/debian/templates  2015-10-07 07:04:02.436316089 
> +0200
> +++ unattended-upgrades/debian/tem

Bug#804086: [INTL:da] Danish translation of the debconf templates unattended-upgrades

[Michael Vogt]

On Wed, Nov 04, 2015 at 07:43:42PM +, Joe Dalton wrote:
> Package: unattended-upgrades
> Severity: wishlist
> Tags: l10n patch

Thanks a lot! I commited this to my git
feature/debconf-template-update branch.

Cheers,
 Michael
 

> Please include the attached Danish unattended-upgrades translation
> 
> joe@pc:~/over/debian/unattended-upgrades$ msgfmt --statistics -c -v -o 
> /dev/null da.po
> da.po: 5 oversatte tekster.
> 
> bye
> Joe

Bug#803950: unattended-upgrades: [INTL:ru] Russian debconf templates translation update

[Michael Vogt]

On Tue, Nov 03, 2015 at 06:14:32PM +0300, Yuri Kozlov wrote:
> Package: unattended-upgrades
> Version: 0.86.6
> Severity: wishlist
> Tags: l10n patch

Thanks a lot! I commited this to my git
feature/debconf-template-update branch.

Cheers,
 Michael

> 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 ***
> 
> Russian debconf templates translation update is attached.
> 
> -- System Information:
> Debian Release: 8.1
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, armhf, armel
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)

Bug#793663: (no subject)

[Michael Vogt]

On Sat, Oct 10, 2015 at 02:13:11PM +0200, Manu Ka wrote:
> Hi Michael
Hi Manu,

> Indeed the problem relates to the locale setting ( with
> unattended-upgrade 0.86.3 )
> 
> export LC_ALL=C
> unattended-upgrade --help
> Usage: unattended-upgrade [options]
> ( works as expected)
> 
> 
> setting a different locale brings an error which seems python2->python3
> related:

Could you please re-test with 0.86.4 that just hit testing? I think
this issue is fixed there.

Thanks,
 Michael

> export LC_ALL=fr_FR.utf-8
> unattended-upgrade --help
> 
> Traceback (most recent call last):
>   File "/usr/bin/unattended-upgrade", line 1424, in 
> (options, args) = parser.parse_args()
>   File "/usr/lib/python3.4/optparse.py", line 1386, in parse_args
> stop = self._process_args(largs, rargs, values)
>   File "/usr/lib/python3.4/optparse.py", line 1426, in _process_args
> self._process_long_opt(rargs, values)
>   File "/usr/lib/python3.4/optparse.py", line 1500, in _process_long_opt
> option.process(opt, value, values, self)
>   File "/usr/lib/python3.4/optparse.py", line 784, in process
> self.action, self.dest, opt, value, values, parser)
>   File "/usr/lib/python3.4/optparse.py", line 806, in take_action
> parser.print_help()
>   File "/usr/lib/python3.4/optparse.py", line 1646, in print_help
> file.write(self.format_help())
>   File "/usr/lib/python3.4/optparse.py", line 1634, in format_help
> result.append(self.format_option_help(formatter))
>   File "/usr/lib/python3.4/optparse.py", line 1614, in format_option_help
> result.append(OptionContainer.format_option_help(self, formatter))
>   File "/usr/lib/python3.4/optparse.py", line 1060, in format_option_help
> result.append(formatter.format_option(option))
>   File "/usr/lib/python3.4/optparse.py", line 321, in format_option
> help_text = self.expand_default(option)
>   File "/usr/lib/python3.4/optparse.py", line 293, in expand_default
> return option.help.replace(self.default_tag, str(default_value))
> TypeError: 'str' does not support the buffer interface
> 
> 
> -- 
> /*
> http://parttimelog.wordpress.com/
> Part time pictures
> */

Bug#799857: apt: Low select timeout

[Michael Vogt]

On Wed, Sep 23, 2015 at 12:57:19PM +0200, Olaf van der Spek wrote:
> Subject: apt: Low select timeout
> Package: apt
> Version: 1.0.10.2
> Severity: wishlist

Thanks for your bugreport.

> Dear Maintainer,
> 
> > pselect6(19, [0 16 18], NULL, NULL, {0, 50}, {[], 8}) = 0 (Timeout)
> > waitpid(14977, 0xbfbc03d4, WNOHANG) = 0
> > pselect6(19, [0 16 18], NULL, NULL, {0, 50}, {[], 8}) = 0 (Timeout)
> > waitpid(14977, 0xbfbc03d4, WNOHANG) = 0
> 
> apt-get seems to use a timeout of 0.5ms for some select call.. Was
> this supposed to be 500ms?
> 0.5ms seems unrealistically low and results in unnecessary CPU usage.
> No big problem though. ;)
> This happened when hung on Installing new version of config file
> /etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf ...

This is fixed in git and will be part of the next upload.

Cheers,
 Michael

> Greetings,
> 
> Olaf
> 
> -- Package-specific info:
> 
> -- apt-config dump --
> 
> APT "";
> APT::Architecture "i386";
> APT::Build-Essential "";
> APT::Build-Essential:: "build-essential";
> APT::Install-Recommends "1";
> APT::Install-Suggests "0";
> APT::Authentication "";
> APT::Authentication::TrustCDROM "true";
> APT::NeverAutoRemove "";
> APT::NeverAutoRemove:: "^firmware-linux.*";
> APT::NeverAutoRemove:: "^linux-firmware$";
> APT::NeverAutoRemove:: "^linux-image-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^linux-image-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^linux-headers-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^linux-headers-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^linux-image-extra-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^linux-image-extra-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^linux-signed-image-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^linux-signed-image-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^kfreebsd-image-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^kfreebsd-image-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^kfreebsd-headers-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^kfreebsd-headers-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^gnumach-image-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^gnumach-image-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^.*-modules-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^.*-modules-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^.*-kernel-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^.*-kernel-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.1\.0-2-686-pae$";
> APT::NeverAutoRemove:: "^linux-tools-4\.1\.0-1-686-pae$";
> APT::NeverAutoRemove:: "^linux-tools-4\.1\.0-2-686-pae$";
> APT::VersionedKernelPackages "";
> APT::VersionedKernelPackages:: "linux-image";
> APT::VersionedKernelPackages:: "linux-headers";
> APT::VersionedKernelPackages:: "linux-image-extra";
> APT::VersionedKernelPackages:: "linux-signed-image";
> APT::VersionedKernelPackages:: "kfreebsd-image";
> APT::VersionedKernelPackages:: "kfreebsd-headers";
> APT::VersionedKernelPackages:: "gnumach-image";
> APT::VersionedKernelPackages:: ".*-modules";
> APT::VersionedKernelPackages:: ".*-kernel";
> APT::VersionedKernelPackages:: "linux-backports-modules-.*";
> APT::VersionedKernelPackages:: "linux-tools";
> APT::Never-MarkAuto-Sections "";
> APT::Never-MarkAuto-Sections:: "metapackages";
> APT::Never-MarkAuto-Sections:: "restricted/metapackages";
> APT::Never-MarkAuto-Sections:: "universe/metapackages";
> APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
> APT::Never-MarkAuto-Sections:: "oldlibs";
> APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
> APT::Never-MarkAuto-Sections:: "universe/oldlibs";
> 
>  [ Wrote 230 lines ]
> 
> Report will be sent to "Debian Bug Tracking System" 
> Submit this report on apt (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|s|?]?
> Bug report written as /var/tmp/apt.bug
> 
> If you want to provide additional information, please wait to receive
> the bug tracking number via email; you may then send any extra
> information to n...@bugs.debian.org (e.g.
> 999...@bugs.debian.org), where n is the bug number. Normally you will
> receive an acknowledgement via email including the bug report number
> within an hour; if you haven't received a confirmation,
> then the bug reporting process failed at some point (reportbug or MTA
> failure, BTS maintenance, etc.).
> olaf@unstable:~$ cat /var/tmp/apt.bug
> Content-Type: text/plain; charset="us-ascii"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> From: Olaf van der Spek 
> To: Debian Bug Tracking System 
> Subject: apt: Low select timeout
> Message-ID: <20150923105620.15397.70969.reportbug@unstable>
> X-Mailer: reportbug 6.6.5
> Date: Wed, 23 Sep 2015 12:56:20 +0200
> 
> Package: apt
> Version: 1.0.10.2
> Severity: wishlist
> 
> Dear Maintainer,
> 
> > pselect6(19, [0 16 18], NULL, NULL, {0, 50}, {[], 8}) = 0 (Timeout)
> > 

Bug#793663: Bug also on my system....

[Michael Vogt]

Hi,

On Sat, Sep 26, 2015 at 08:48:47AM +0200, Christian PERRIER wrote:
> Just a quick note to mention that this bug is also affecting me. 
[..]
> But, even with the C locale:
> Traceback (most recent call last):
>   File "/usr/bin/unattended-upgrade", line 1406, in 
> help=_("print debug messages"))
>   File "/usr/lib/python3.4/gettext.py", line 519, in lgettext
> return ldgettext(_current_domain, message)
>   File "/usr/lib/python3.4/gettext.py", line 491, in ldgettext
> return t.lgettext(message)
>   File "/usr/lib/python3.4/gettext.py", line 317, in lgettext
> return tmsg.encode(locale.getpreferredencoding())
> UnicodeEncodeError: 'ascii' codec can't encode character '\xe9' in position 
> 26: ordinal not in range(128)
[..]

Thanks, this appears to be a regression caused by moving from gettext
to lgettext. It seems like this needs to be reverted.

Cheers,
 Michael

Bug#793663: Re[3]: Bug#793663: [unattended-upgrades] Unsupported operand type(s) for %: 'bytes' and 'tuple'

[Michael Vogt]

On Tue, Sep 22, 2015 at 06:22:52AM +, mrpa...@gmail.com wrote:
> Hi Michael,
Hi Frank,

> Did you have a chance to look further into the issue? Let me know if there
> is anything I can do to help.

I'm still struggling with this one, does 0.86.3 still crash for you? I
assume so, could you send me the backtrace of the crash please?

Thanks,
 Michael

> Frank
> 
> 
> -- Originalnachricht --
> Von: mrpa...@gmail.com
> An: 793...@bugs.debian.org
> Gesendet: 8/31/2015 19:43:17
> Betreff: Re[2]: Bug#793663: [unattended-upgrades] Unsupported operand
> type(s) for %: 'bytes' and 'tuple'
> 
> >Glad if I can help :-)
> >
> >My unattended-upgrades is version 0.86.3. It updated today from version
> >0.86.2. I do have
> >
> >from gettext import lgettext as _
> >
> >(at line 44).
> >
> >The output of locale is:
> >
> ># locale
> >LANG=de_DE.UTF-8
> >LANGUAGE=
> >LC_CTYPE="de_DE.UTF-8"
> >LC_NUMERIC="de_DE.UTF-8"
> >LC_TIME="de_DE.UTF-8"
> >LC_COLLATE="de_DE.UTF-8"
> >LC_MONETARY="de_DE.UTF-8"
> >LC_MESSAGES="de_DE.UTF-8"
> >LC_PAPER="de_DE.UTF-8"
> >LC_NAME="de_DE.UTF-8"
> >LC_ADDRESS="de_DE.UTF-8"
> >LC_TELEPHONE="de_DE.UTF-8"
> >LC_MEASUREMENT="de_DE.UTF-8"
> >LC_IDENTIFICATION="de_DE.UTF-8"
> >LC_ALL=
> >Currently it doesn't crash because I just manually updated all my packages
> >(apt-get update, apt-get upgrade). Guess I will have to wait with
> >generating more debug info until some package updates are available in the
> >repos.
> >
> >Let me know what you want me to try out next.
> >
> >Frank
> >
> >-- Originalnachricht --
> >Von: "Michael Vogt" <m...@debian.org>
> >An: mrpa...@gmail.com; 793...@bugs.debian.org
> >Gesendet: 8/31/2015 19:28:23
> >Betreff: Re: Bug#793663: [unattended-upgrades] Unsupported operand type(s)
> >for %: 'bytes' and 'tuple'
> >
> >>On Mon, Aug 31, 2015 at 11:48:42AM +, mrpa...@gmail.com wrote:
> >>> Hi Michael,
> >>Hi Frank,
> >>
> >>> Thanks for looking into the issue. I'm getting almost the exact same
> >>>error
> >>> message. It started a few weeks ago. The issue is reproducible
> >>>whether I run
> >>> unattended-upgrades from the shell or from cron.
> >>
> >>Thanks a lot for helping me to track down this issue! Great to have
> >>someone who can reproduce the issue, I really want to track down this
> >>issue so its awsome to have you to help and answer all my questions :)
> >>
> >>>   File "/usr/bin/unattended-upgrade", line 815, in
> >>>send_summary_mail
> >>> host(), res)
> >>> TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple'
> >>> This statement is causing the error on my system:
> >>>
> >>> subject = _("unattended-upgrades result for '%s': '%s'") %
> >>>(host(), res)
> >>>
> >>> res argument is 'None'. host() is a string.
> >>>type(_("unattended-upgrades
> >>> result for '%s': '%s'")) is . Shouldn't this be
> >>> string?
> >>
> >>This smeels like a clue:
> >>  type(_("unattended-upgrades result for '%s': '%s'")
> >>should indeed be "str" instead of bytes.
> >>
> >>What version of unattended-upgrades do you have?
> >>$ apt list unattended-upgrades
> >>will tell you.
> >>
> >>Do you have in the unattended-upgrades binary the lines:
> >>"""
> >>from gettext import lgettext as _
> >>"""
> >>
> >>> My
> >>> locale is de_DE.UTF-8. gettext on the shell does return a
> >>>translation:
> >>>
> >>> # gettext unattended-upgrades "unattended-upgrades result for
> >>>'%s':
> >>> '%s'"
> >>> Unattended-Upgrades-Ergebnis für »%s«: %s
> >>>
> >>> If I change the message to be translated, unattended-upgrades
> >>>continues, but
> >>> complains about another _(...) message further down.
> >>>
> >>> Now I'm lost. Any help is greatly appreciated.
> >>
> >>What is the output of "locale"?
> >>
> >>
> >>
> >>Thanks,
> >> Michael

Bug#791661: patches

[Michael Vogt]

Hi,

looks like the actual patches are missing for some reason. Attached
are the two patches that add support for libnss-extrausers.

Cheers,
 Michael
Description: Add support to passwd for updating libnss-extrausers locations
Author: Michael Terry 

Index: shadow-4.1.5.1/lib/defines.h
===
--- shadow-4.1.5.1.orig/lib/defines.h
+++ shadow-4.1.5.1/lib/defines.h
@@ -316,6 +316,14 @@ char *strchr (), *strrchr (), *strtok ()
 #endif
 #endif
 
+#ifndef EXTRAUSERS_PASSWD_FILE
+#define EXTRAUSERS_PASSWD_FILE "/var/lib/extrausers/passwd"
+#endif
+
+#ifndef EXTRAUSERS_SHADOW_FILE
+#define EXTRAUSERS_SHADOW_FILE "/var/lib/extrausers/shadow"
+#endif
+
 #ifndef NULL
 #define NULL ((void *) 0)
 #endif
Index: shadow-4.1.5.1/src/passwd.c
===
--- shadow-4.1.5.1.orig/src/passwd.c
+++ shadow-4.1.5.1/src/passwd.c
@@ -544,8 +544,15 @@ static void update_noshadow (void)
 {
 	const struct passwd *pw;
 	struct passwd *npw;
+	bool try_extrausers = strcmp (pw_dbname (), EXTRAUSERS_PASSWD_FILE) != 0 &&
+	  access (EXTRAUSERS_PASSWD_FILE, F_OK) == 0;
 
 	if (pw_lock () == 0) {
+		if (try_extrausers) {
+			pw_setdbname (EXTRAUSERS_PASSWD_FILE);
+			update_noshadow ();
+			return;
+		}
 		(void) fprintf (stderr,
 		_("%s: cannot lock %s; try again later.\n"),
 		Prog, pw_dbname ());
@@ -553,6 +560,20 @@ static void update_noshadow (void)
 	}
 	pw_locked = true;
 	if (pw_open (O_RDWR) == 0) {
+		if (try_extrausers) {
+			if (pw_unlock () == 0) {
+(void) fprintf (stderr,
+_("%s: failed to unlock %s\n"),
+Prog, pw_dbname ());
+SYSLOG ((LOG_ERR, "failed to unlock %s", pw_dbname ()));
+/* continue */
+			}
+			pw_locked = false;
+
+			pw_setdbname (EXTRAUSERS_PASSWD_FILE);
+			update_noshadow ();
+			return;
+		}
 		(void) fprintf (stderr,
 		_("%s: cannot open %s\n"),
 		Prog, pw_dbname ());
@@ -561,6 +582,21 @@ static void update_noshadow (void)
 	}
 	pw = pw_locate (name);
 	if (NULL == pw) {
+		if (try_extrausers) {
+			(void) pw_close ();
+			if (pw_unlock () == 0) {
+(void) fprintf (stderr,
+_("%s: failed to unlock %s\n"),
+Prog, pw_dbname ());
+SYSLOG ((LOG_ERR, "failed to unlock %s", pw_dbname ()));
+/* continue */
+			}
+			pw_locked = false;
+
+			pw_setdbname (EXTRAUSERS_PASSWD_FILE);
+			update_noshadow ();
+			return;
+		}
 		(void) fprintf (stderr,
 		_("%s: user '%s' does not exist in %s\n"),
 		Prog, name, pw_dbname ());
@@ -598,8 +634,15 @@ static void update_shadow (void)
 {
 	const struct spwd *sp;
 	struct spwd *nsp;
+	bool try_extrausers = strcmp (spw_dbname (), EXTRAUSERS_SHADOW_FILE) != 0 &&
+	  access (EXTRAUSERS_SHADOW_FILE, F_OK) == 0;
 
 	if (spw_lock () == 0) {
+		if (try_extrausers) {
+			spw_setdbname (EXTRAUSERS_SHADOW_FILE);
+			update_shadow ();
+			return;
+		}
 		(void) fprintf (stderr,
 		_("%s: cannot lock %s; try again later.\n"),
 		Prog, spw_dbname ());
@@ -607,6 +650,20 @@ static void update_shadow (void)
 	}
 	spw_locked = true;
 	if (spw_open (O_RDWR) == 0) {
+		if (try_extrausers) {
+			if (spw_unlock () == 0) {
+(void) fprintf (stderr,
+		_("%s: failed to unlock %s\n"),
+		Prog, spw_dbname ());
+SYSLOG ((LOG_ERR, "failed to unlock %s", spw_dbname ()));
+/* continue */
+			}
+			spw_locked = false;
+
+			spw_setdbname (EXTRAUSERS_SHADOW_FILE);
+			update_shadow ();
+			return;
+		}
 		(void) fprintf (stderr,
 		_("%s: cannot open %s\n"),
 		Prog, spw_dbname ());
@@ -617,7 +674,9 @@ static void update_shadow (void)
 	if (NULL == sp) {
 		/* Try to update the password in /etc/passwd instead. */
 		(void) spw_close ();
-		update_noshadow ();
+		if (!try_extrausers) {
+			update_noshadow ();
+		}
 		if (spw_unlock () == 0) {
 			(void) fprintf (stderr,
 			_("%s: failed to unlock %s\n"),
@@ -626,6 +685,10 @@ static void update_shadow (void)
 			/* continue */
 		}
 		spw_locked = false;
+		if (try_extrausers) {
+			spw_setdbname (EXTRAUSERS_SHADOW_FILE);
+			update_shadow ();
+		}
 		return;
 	}
 	nsp = __spw_dup (sp);
Index: shadow-4.1.5.1/lib/commonio.c
===
--- shadow-4.1.5.1.orig/lib/commonio.c
+++ shadow-4.1.5.1/lib/commonio.c
@@ -401,6 +401,7 @@ int commonio_lock_nowait (struct commoni
 int commonio_lock (struct commonio_db *db)
 {
 #ifdef HAVE_LCKPWDF
+  if (strncmp(db->filename, "/etc/", 5) == 0) {
 	/*
 	 * only if the system libc has a real lckpwdf() - the one from
 	 * lockpw.c calls us and would cause infinite recursion!
@@ -428,7 +429,9 @@ int commonio_lock (struct commonio_db *d
 
 	ulckpwdf ();
 	return 0;		/* failure */

Bug#793663: [unattended-upgrades] Unsupported operand type(s) for %: 'bytes' and 'tuple'

[Michael Vogt]

On Mon, Aug 31, 2015 at 11:48:42AM +, mrpa...@gmail.com wrote:
> Hi Michael,
Hi Frank,

> Thanks for looking into the issue. I'm getting almost the exact same error
> message. It started a few weeks ago. The issue is reproducible whether I run
> unattended-upgrades from the shell or from cron.

Thanks a lot for helping me to track down this issue! Great to have
someone who can reproduce the issue, I really want to track down this
issue so its awsome to have you to help and answer all my questions :)

>   File "/usr/bin/unattended-upgrade", line 815, in send_summary_mail
> host(), res)
> TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple'
> This statement is causing the error on my system:
> 
> subject = _("unattended-upgrades result for '%s': '%s'") % (host(), res)
> 
> res argument is 'None'. host() is a string. type(_("unattended-upgrades
> result for '%s': '%s'")) is . Shouldn't this be
> string?

This smeels like a clue:
  type(_("unattended-upgrades result for '%s': '%s'")
should indeed be "str" instead of bytes.

What version of unattended-upgrades do you have?
$ apt list unattended-upgrades
will tell you.

Do you have in the unattended-upgrades binary the lines:
"""
from gettext import lgettext as _
"""

> My
> locale is de_DE.UTF-8. gettext on the shell does return a translation:
> 
> # gettext unattended-upgrades "unattended-upgrades result for '%s':
> '%s'"
> Unattended-Upgrades-Ergebnis für »%s«: %s
> 
> If I change the message to be translated, unattended-upgrades continues, but
> complains about another _(...) message further down.
> 
> Now I'm lost. Any help is greatly appreciated.

What is the output of "locale"?



Thanks,
 Michael

Bug#795499: patch

[Michael Vogt]

On Sun, Aug 16, 2015 at 02:21:47PM +0200, Sylvestre Ledru wrote:
 Hello,
Hi,

 Le 14/08/2015 20:35, Michael Vogt a écrit :
  Hi,
 
  here the debian/* debdiff. I'm not sure about the version number, it
  appears that upstream has changed the schema.
 The old versioning is still proposed here:
 https://github.com/include-what-you-use/include-what-you-use/releases
 
 Thanks for your patch. Next time, please write if from the current
 version (3.5) ;)

Hm, I guess the version numbering is confusing now :) I looked at
http://include-what-you-use.org/ and there it says that version 0.4
(for clang 3.6) is the most recent one.

If I messed it up, I'm sorry.

Cheers,
 Michael

Bug#793663: [unattended-upgrades] Unsupported operand type(s) for %: 'bytes' and 'tuple'

[Michael Vogt]

On Sun, Jul 26, 2015 at 09:23:23AM +0100, Antonio Marcos López Alonso wrote:
 Package: unattended-upgrades
 Version: 0.86.2
 Severity: normal

Thanks for your bugreport.

 --- Please enter the report below this line. ---
 
 Dear maintainers:
 
 APT complains on some operand error due to unattended-upgrades:
 
 /etc/cron.daily/apt:
 Exception: unsupported operand type(s) for %: 'bytes' and 'tuple'
 Traceback (most recent call last):
   File /usr/bin/unattended-upgrade, line 1435, in module
 main(options)
   File /usr/bin/unattended-upgrade, line 1382, in main
 pkgs, pkg_install_success, pkgs_kept_back, mem_log, log_content)
   File /usr/bin/unattended-upgrade, line 816, in send_summary_mail
 body = _(Unattended upgrade returned: %s\n\n) % res
 TypeError: unsupported operand type(s) for %: 'bytes' and 'bool'

I tried to reproduce this in various way, but failed so far.

Is this reproducable if you run unattended-upgrades manually? Or only
via cron? Anything special in your env or language environment or
python environment that might help me to find a way to reproduce? If
you can reproduct, could you add debug lines like:

print(type(res))
print(type(_(Unattended upgrade returned: %s\n\n)))

right before the line that crashes and send me the output?

Thanks,
 Michael
 
 Regards,
 Antonio
 
 --- System information. ---
 Architecture: amd64
 Kernel:   Linux 4.0.0-2-amd64
 
 Debian Release: stretch/sid
   900 testing security.debian.org 
   900 testing ftp.es.debian.org 
   800 stable  update.devolo.com 
   800 stable  kxstudio.linuxaudio.org 
   800 stable  dl.google.com 
   500 trusty  ppa.launchpad.net 
   500 sid linux.dropbox.com 
   500 lucid   ppa.launchpad.net 
 
 --- Package information. ---
 Package's Depends field is empty.
 
 Package's Recommends field is empty.
 
 Package's Suggests field is empty.

Bug#795499: patch

[Michael Vogt]

Hi,

here the debian/* debdiff. I'm not sure about the version number, it
appears that upstream has changed the schema.

Cheers,
 Michael
--- iwyu-3.4/debian/changelog   2014-05-06 17:36:43.0 +0200
+++ iwyu-0.4/debian/changelog   2015-08-14 20:00:53.0 +0200
@@ -1,3 +1,9 @@
+iwyu (1:0.4-1) unstable; urgency=low
+
+  * new upstream release
+
+ -- Michael Vogt m...@debian.org  Fri, 14 Aug 2015 20:00:47 +0200
+
 iwyu (3.4-1) unstable; urgency=medium
 
   * New upstream release
--- iwyu-3.4/debian/control 2014-05-06 17:32:10.0 +0200
+++ iwyu-0.4/debian/control 2015-08-14 20:05:31.0 +0200
@@ -3,16 +3,16 @@
 Priority: extra
 Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
 Uploaders: Sylvestre Ledru sylves...@debian.org
-Build-Depends: debhelper (= 8.0.0), cmake, libclang-3.4-dev, llvm-3.4-dev,
+Build-Depends: debhelper (= 8.0.0), cmake, libclang-3.6-dev, llvm-3.6-dev,
  help2man, libncurses5-dev
 Standards-Version: 3.9.5
-Homepage: http://code.google.com/p/include-what-you-use/
-Vcs-Svn: svn://svn.debian.org/svn/pkg-llvm/iwyu/trunk/
-Vcs-Browser: http://svn.debian.org/viewsvn/pkg-llvm/iwyu/trunk/
+Homepage: http://include-what-you-use.org/
+Vcs-Git: https://github.com/include-what-you-use/include-what-you-use.git
+Vcs-Browser: https://github.com/include-what-you-use/include-what-you-use
 
 Package: iwyu
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, clang-3.3 | clang-3.4 | 
clang-3.5, python
+Depends: ${shlibs:Depends}, ${misc:Depends}, clang-3.3 | clang-3.4 | clang-3.5 
| clang-3.6, python
 Description: Analyze #includes in C and C++ source files
  Include what you use means this: for every symbol (type, function variable,
  or macro) that you use in foo.cc, either foo.cc or foo.h should #include a .h
--- iwyu-3.4/debian/rules   2014-05-06 17:17:12.0 +0200
+++ iwyu-0.4/debian/rules   2015-08-14 20:07:13.0 +0200
@@ -11,7 +11,7 @@
dh $@ --buildsystem=cmake --builddirectory=$(TARGET_BUILD)
 
 override_dh_auto_configure:
-   dh_auto_configure -- -DLLVM_PATH=/usr/lib/llvm-3.4/
+   dh_auto_configure -- -DLLVM_PATH=/usr/lib/llvm-3.6/
 
 override_dh_auto_build:
dh_auto_build
--- iwyu-3.4/debian/watch   2014-05-06 17:35:49.0 +0200
+++ iwyu-0.4/debian/watch   2015-08-14 20:07:06.0 +0200
@@ -1,3 +1,2 @@
 version=3
-https://code.google.com/p/include-what-you-use/ \
-http://include-what-you-use.com/downloads/include-what-you-use-(.*).src.tar.gz
\ No newline at end of file
+http://include-what-you-use.com/downloads/include-what-you-use-(.*).src.tar.gz

Bug#795499: iwyu: [patch] new upstream release

[Michael Vogt]

Package: iwyu
Version: 1:0.4-1
Severity: wishlist
Tags: patch


Hi,

I stumbled upon 
https://code.google.com/p/include-what-you-use/issues/detail?id=150 
when running iwyu with apt and this is fixed with the new upstream
release 0.4 for clang 3.6. Attached is a debian/* debdiff for the
updated version. I can also upload if that is easier for you.

Cheers,
 Michael

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 
'vivid-proposed'), (500, 'vivid'), (100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages iwyu depends on:
ii  clang-3.4   1:3.4.2-13ubuntu2
ii  clang-3.5   1:3.5.2-0ubuntu1
ii  clang-3.6   1:3.6-2ubuntu1
ii  libc6   2.21-0ubuntu4
ii  libgcc1 1:5.1~rc1-0ubuntu1
ii  libstdc++6  4.9.2-10ubuntu13
ii  libtinfo5   5.9+20140712-2ubuntu2
ii  python  2.7.9-1
ii  zlib1g  1:1.2.8.dfsg-2ubuntu1

iwyu recommends no packages.

iwyu suggests no packages.

-- no debconf information
--- iwyu-3.4/debian/changelog	2014-05-06 17:36:43.0 +0200
+++ iwyu-0.4/debian/changelog	2015-08-14 20:00:53.0 +0200
@@ -1,3 +1,9 @@
+iwyu (1:0.4-1) unstable; urgency=low
+
+  * new upstream release
+
+ -- Michael Vogt m...@debian.org  Fri, 14 Aug 2015 20:00:47 +0200
+
 iwyu (3.4-1) unstable; urgency=medium
 
   * New upstream release
--- iwyu-3.4/debian/control	2014-05-06 17:32:10.0 +0200
+++ iwyu-0.4/debian/control	2015-08-14 20:05:31.0 +0200
@@ -3,16 +3,16 @@
 Priority: extra
 Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
 Uploaders: Sylvestre Ledru sylves...@debian.org
-Build-Depends: debhelper (= 8.0.0), cmake, libclang-3.4-dev, llvm-3.4-dev,
+Build-Depends: debhelper (= 8.0.0), cmake, libclang-3.6-dev, llvm-3.6-dev,
  help2man, libncurses5-dev
 Standards-Version: 3.9.5
-Homepage: http://code.google.com/p/include-what-you-use/
-Vcs-Svn: svn://svn.debian.org/svn/pkg-llvm/iwyu/trunk/
-Vcs-Browser: http://svn.debian.org/viewsvn/pkg-llvm/iwyu/trunk/
+Homepage: http://include-what-you-use.org/
+Vcs-Git: https://github.com/include-what-you-use/include-what-you-use.git
+Vcs-Browser: https://github.com/include-what-you-use/include-what-you-use
 
 Package: iwyu
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, clang-3.3 | clang-3.4 | clang-3.5, python
+Depends: ${shlibs:Depends}, ${misc:Depends}, clang-3.3 | clang-3.4 | clang-3.5 | clang-3.6, python
 Description: Analyze #includes in C and C++ source files
  Include what you use means this: for every symbol (type, function variable,
  or macro) that you use in foo.cc, either foo.cc or foo.h should #include a .h
--- iwyu-3.4/debian/rules	2014-05-06 17:17:12.0 +0200
+++ iwyu-0.4/debian/rules	2015-08-14 20:07:13.0 +0200
@@ -11,7 +11,7 @@
 	dh $@ --buildsystem=cmake --builddirectory=$(TARGET_BUILD)
 
 override_dh_auto_configure:
-	dh_auto_configure -- -DLLVM_PATH=/usr/lib/llvm-3.4/
+	dh_auto_configure -- -DLLVM_PATH=/usr/lib/llvm-3.6/
 
 override_dh_auto_build:
 	dh_auto_build
--- iwyu-3.4/debian/watch	2014-05-06 17:35:49.0 +0200
+++ iwyu-0.4/debian/watch	2015-08-14 20:07:06.0 +0200
@@ -1,3 +1,2 @@
 version=3
-https://code.google.com/p/include-what-you-use/ \
-http://include-what-you-use.com/downloads/include-what-you-use-(.*).src.tar.gz
\ No newline at end of file
+http://include-what-you-use.com/downloads/include-what-you-use-(.*).src.tar.gz
--- iwyu-3.4/debian/changelog	2014-05-06 17:36:43.0 +0200
+++ iwyu-0.4/debian/changelog	2015-08-14 20:00:53.0 +0200
@@ -1,3 +1,9 @@
+iwyu (1:0.4-1) unstable; urgency=low
+
+  * new upstream release
+
+ -- Michael Vogt m...@debian.org  Fri, 14 Aug 2015 20:00:47 +0200
+
 iwyu (3.4-1) unstable; urgency=medium
 
   * New upstream release
--- iwyu-3.4/debian/control	2014-05-06 17:32:10.0 +0200
+++ iwyu-0.4/debian/control	2015-08-14 20:05:31.0 +0200
@@ -3,16 +3,16 @@
 Priority: extra
 Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
 Uploaders: Sylvestre Ledru sylves...@debian.org
-Build-Depends: debhelper (= 8.0.0), cmake, libclang-3.4-dev, llvm-3.4-dev,
+Build-Depends: debhelper (= 8.0.0), cmake, libclang-3.6-dev, llvm-3.6-dev,
  help2man, libncurses5-dev
 Standards-Version: 3.9.5
-Homepage: http://code.google.com/p/include-what-you-use/
-Vcs-Svn: svn://svn.debian.org/svn/pkg-llvm/iwyu/trunk/
-Vcs-Browser: http://svn.debian.org/viewsvn/pkg-llvm/iwyu/trunk/
+Homepage: http://include-what-you-use.org/
+Vcs-Git: https://github.com/include-what-you-use/include-what-you-use.git
+Vcs-Browser: https://github.com/include-what-you-use/include-what-you-use
 
 Package: iwyu
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, clang-3.3 | clang-3.4

Bug#792216: unatteded-upgrades - error message: 'installArchives() failed'

[Michael Vogt]

On Sun, Jul 12, 2015 at 08:49:10PM +0200, Bastian Blank wrote:
 Package: unattended-upgrades
 Version: 0.83.3.2+deb8u1
 Severity: important

Thanks for your bugreport.

 unattended-upgrades in jessie fails to install anything.
 
 2015-07-12 06:50:24,929 INFO Initial blacklisted packages:
 2015-07-12 06:50:24,930 INFO Initial whitelisted packages:
 2015-07-12 06:50:24,930 INFO Starting unattended upgrades script
 2015-07-12 06:50:24,931 INFO Allowed origins are: 
 ['origin=Debian,codename=jessie,label=Debian-Security', 
 'origin=Debian,archive=stable,label=Debian', 
 'origin=Debian,archive=stable,label=Debian-Security', 
 'origin=Debian,archive=testing,label=Debian', 
 'origin=Debian,archive=testing,label=Debian-Security']
 2015-07-12 06:50:34,280 INFO Packages that will be upgraded: bind9-host host 
 libbind9-90 libdns100 libisc95 libisccc90 libisccfg90 liblwres90
 2015-07-12 06:50:34,281 INFO Writing dpkg log to 
 '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
 2015-07-12 06:50:34,464 ERROR Installing the upgrades failed!
 2015-07-12 06:50:34,465 ERROR error message: 'installArchives() failed'
 2015-07-12 06:50:34,465 ERROR dpkg returned a error! See 
 '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' for details
 
 Log started: 2015-07-12  06:50:34
 Error in function:
 Log ended: 2015-07-12  06:50:34

The erorr message looks like something in python-apt goes wrong (or in
the way u-u interacts with python-apt). Do you get a more meaningful
error message if you run:
  # unattended-upgrades --debug
on a terminal?

Is there anything unusual about the system? What apt/python-apt
version are in use?

Thanks,
 Michael

 Bastian
 
 -- System Information:
 Debian Release: stretch/sid
   APT prefers testing
   APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#791749: synaptic: Add to Quick filter text entry a button to clean it.

[Michael Vogt]

On Wed, Jul 08, 2015 at 04:12:07AM +0200, Gianni Lerro wrote:
 Package: synaptic
 Version: 0.81.3
 Severity: normal
 Tags: patch

Thanks for your bugreport and your patch!

 is possible to add to Quick filter text entry a button to clean it.

Absolutely, thanks a lot! This is merged and I uploaded it to sid
now. I also moved the code to git to make it easier to hack on it.

If you enjoy working on the code, I would love to get some help
hacking on synaptic. There is plenty of cool stuff that could be
done. Please let me know if you are interessted :)

Cheers and many thanks,
 Michael





 Thanks.
 
 
 
 -- System Information:
 Debian Release: stretch/sid
   APT prefers testing-updates
   APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), 
 (500, 'testing'), (1, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 4.1-1.dmz.2-liquorix-amd64 (SMP w/2 CPU cores; PREEMPT)
 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages synaptic depends on:
 ii  hicolor-icon-theme   0.13-1
 ii  libapt-inst1.5   1.0.9.10
 ii  libapt-pkg4.12   1.0.9.10
 ii  libatk1.0-0  2.16.0-2
 ii  libc62.19-18
 ii  libcairo-gobject21.14.2-2
 ii  libcairo21.14.2-2
 ii  libept1.4.12 1.0.12.1
 ii  libgcc1  1:5.1.1-12
 ii  libgdk-pixbuf2.0-0   2.31.4-2
 ii  libglib2.0-0 2.44.1-1.1
 ii  libgtk-3-0   3.16.4-2
 ii  libpango-1.0-0   1.36.8-3
 ii  libpangocairo-1.0-0  1.36.8-3
 ii  libstdc++6   5.1.1-12
 ii  libvte-2.90-91:0.36.3-1
 ii  libx11-6 2:1.6.3-1
 ii  libxapian22  1.2.21-1
 ii  libxext6 2:1.3.3-1
 ii  zlib1g   1:1.2.8.dfsg-2+b1
 
 Versions of packages synaptic recommends:
 ii  gksu   2.0.2-9
 ii  libgtk2-perl   2:1.2495-1
 ii  policykit-10.105-8
 ii  rarian-compat  0.8.1-6
 
 Versions of packages synaptic suggests:
 ii  apt-xapian-index 0.47
 ii  deborphan1.7.28.8-0.1
 pn  dwww none
 ii  menu 2.1.47
 ii  software-properties-gtk  0.92.25debian1
 ii  tasksel  3.32
 
 -- no debconf information

 === modificato file gtk/rgmainwindow.h
 --- gtk/rgmainwindow.h2014-03-18 19:58:18 +
 +++ gtk/rgmainwindow.h2015-07-08 00:20:58 +
 @@ -181,6 +181,8 @@
  
 // helpers for search-as-you-type 
 static void cbSearchEntryChanged(GtkWidget *editable, void *data);
 +   static void cbSearchEntryClean(GtkEntry *entry, GtkEntryIconPosition 
 icon_pos,
 +  GdkEvent *event, void *data);
 static void xapianIndexUpdateFinished(GPid pid, gint status, void* data);
 static gboolean xapianDoSearch(void *data);
 static gboolean xapianDoIndexUpdate(void *data);
 
 === modificato file gtk/gtkbuilder/window_main.ui
 --- gtk/gtkbuilder/window_main.ui 2013-10-26 19:20:45 +
 +++ gtk/gtkbuilder/window_main.ui 2015-07-08 00:20:02 +
 @@ -830,7 +830,9 @@
  property name=has_focusTrue/property
  property name=is_focusTrue/property
  property name=invisible_char●/property
 +property 
 name=secondary_icon_namegtk-clear/property
  signal name=changed 
 handler=on_entry_fast_search_changed swapped=no/
 +signal name=icon-press 
 handler=on_entry_fast_search_icon_press swapped=no/
/object
packing
  property name=expandTrue/property
 
 === modificato file gtk/rgmainwindow.cc
 --- gtk/rgmainwindow.cc   2014-05-16 06:16:17 +
 +++ gtk/rgmainwindow.cc   2015-07-08 00:28:10 +
 @@ -1010,6 +1010,9 @@
 g_signal_connect(gtk_builder_get_object(_builder, entry_fast_search),
  changed,
  G_CALLBACK(cbSearchEntryChanged), this);
 +   g_signal_connect(gtk_builder_get_object(_builder, entry_fast_search),
 +icon-press,
 +G_CALLBACK(cbSearchEntryClean), this);
  
 _propertiesB = GTK_WIDGET(gtk_builder_get_object(_builder, 
 button_details));
 assert(_propertiesB);
 @@ -2855,6 +2858,15 @@
 me-_fastSearchEventID = g_timeout_add(500, xapianDoSearch, me);
  }
  
 +void RGMainWindow::cbSearchEntryClean(GtkEntry *entry,
 +  GtkEntryIconPosition icon_pos,
 +  GdkEvent *event,
 +  void *data)
 +{
 +   if (icon_pos == GTK_ENTRY_ICON_SECONDARY)
 +  gtk_entry_set_text(GTK_ENTRY(entry), );
 +}
 +
  void RGMainWindow::cbUpdateClicked(GtkWidget *self, void *data)
  {
 RGMainWindow *me = (RGMainWindow *) data;
 
 === modificato file gtk/rgmainwindow.h
 --- gtk/rgmainwindow.h

Bug#791908: The --no-vowels turns on PW_UPPER even with --no-capitalize

[Michael Vogt]

Package: pwgen
Version: 2.07-1

A friend of mine stumbled over the issue that:
$ pwgen  --no-vowels  --no-capitalize
and
$ pwgen  --no-capitalize --no-vowels
give different results. The later does include captialized
results while the former does not. I was expecting no upper
cases in both cases.

The attached patch fixes this. Alternative the documentation for
--no-vowels could maybe improved to mention that it turns on
PW_UPPERS.

Thanks,
 Michael
--- pwgen-2.07.orig/pwgen.c
+++ pwgen-2.07/pwgen.c
@@ -154,7 +154,7 @@ int main(int argc, char **argv)
break;
case 'v':
pwgen = pw_rand;
-   pwgen_flags |= PW_NO_VOWELS | PW_DIGITS | PW_UPPERS;
+   pwgen_flags |= PW_NO_VOWELS | PW_DIGITS;
break;
case 'h':
case '?':

Bug#790084: Re : synaptic: Set Internal Options crash

[Michael Vogt]

On Mon, Jul 06, 2015 at 09:24:47PM +, E/LH/O13B - JULE Corentin wrote:
 seems to be duplicate of #774056

Thanks, I fixed this in bzr now.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#791375: Should honour system settings when opening web browser

[Michael Vogt]

On Fri, Jul 03, 2015 at 07:08:17PM -0500, Steve M. Robbins wrote:
 Package: synaptic
 Version: 0.81.3
 Severity: normal
 
 When I click the Visit Homepage button, synaptic opens iceweasel,
 even though I have set my (KDE) system to use chrome.

Thanks for your bugreport. How is kde setting this? synaptic will use
xdg-open if its available to open links. Is there a xdg-open like
command for kde that synaptic should use?

Thanks,
 Michael
 
 -- System Information:
 Debian Release: stretch/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages synaptic depends on:
 ii  hicolor-icon-theme   0.13-1
 ii  libapt-inst1.5   1.0.9.10
 ii  libapt-pkg4.12   1.0.9.10
 ii  libatk1.0-0  2.16.0-2
 ii  libc62.19-18
 ii  libcairo-gobject21.14.2-2
 ii  libcairo21.14.2-2
 ii  libept1.4.12 1.0.12.1
 ii  libgcc1  1:5.1.1-12
 ii  libgdk-pixbuf2.0-0   2.31.4-2
 ii  libglib2.0-0 2.44.1-1.1
 ii  libgtk-3-0   3.16.4-2
 ii  libpango-1.0-0   1.36.8-3
 ii  libpangocairo-1.0-0  1.36.8-3
 ii  libstdc++6   5.1.1-12
 ii  libvte-2.90-91:0.36.3-1
 ii  libx11-6 2:1.6.3-1
 ii  libxapian22  1.2.21-1
 ii  libxext6 2:1.3.3-1
 ii  zlib1g   1:1.2.8.dfsg-2+b1
 
 Versions of packages synaptic recommends:
 ii  gksu   2.0.2-9
 ii  libgtk2-perl   2:1.2495-1
 ii  policykit-10.105-8
 ii  rarian-compat  0.8.1-6
 
 Versions of packages synaptic suggests:
 pn  apt-xapian-index none
 ii  deborphan1.7.28.8-0.1
 ii  dwww 1.12.1
 ii  menu 2.1.47
 pn  software-properties-gtk  none
 ii  tasksel  3.32
 
 -- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#791661: support for alternative passwd location (i.e. libnss-extrausers)

[Michael Vogt]

Package: shadow
Version: 1:4.1.5.1-1.1
Severity: wishlist

Hi,

in Ubuntu we applied a patch that adds a new --extrausers flag that
will use the libnss-extrauser passwd/group/shadow databasees instead
of the normal ones.

I'm happy to cleanup this patch and forward it to Debian if there is a
chance that it might get applied. Please let me know if thats
something you would consider.

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#789491: [INTL:tr] Turkish translation update for apt

[Michael Vogt]

On Sun, Jun 21, 2015 at 04:55:27PM +0300, Mert Dirik wrote:
 Package: apt
 Severity: wishlist
 Tags: l10n patch
 
 Please find the attached Turkish translation update of apt program messages.

Thanks, this is merged and it will be part of the next upload.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#789469: Default configuration does not upgrade packages from debian-security

[Michael Vogt]

On Sun, Jun 21, 2015 at 11:42:24AM +0200, Simon Van der Linden wrote:
 Package: unattended-upgrades
 Version: 0.83.3.1

Thanks for your bugreport.

 The default configuration of unattended-upgrade in Jessie does not let 
 packages from debian-security be upgraded unattended.
 

This is a brown-paperbag bug in 0.83.3.1. I uploaded a fix to
stable-proposed and I'm talking to the security team to get  updated
version into -security too.

Sorry,
 Michael

 # unattended-upgrade --debug
 Initial blacklisted packages: 
 Initial whitelisted packages: 
 Starting unattended upgrades script
 Allowed origins are: ['o=Debian,a=jessie-security']
 Checking: libssl1.0.0 ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: openssl ([Origin component:'main' archive:'stable' origin:'Debian' 
 label:'Debian-Security' site:'security.debian.org' isTrusted:True])
 pkgs that look like they should be upgraded: 
 Fetched 0 B in 0s (0 B/s) 
 
 fetch.run() result: 0
 blacklist: []
 whitelist: []
 InstCount=0 DelCount=0 BrokenCount=0
 No packages found that can be upgraded unattended
 #
 
 
 /etc/apt/apt.conf.d/50unattended-upgrades:
  
 Unattended-Upgrade::Allowed-Origins {
 ${distro_id}:${distro_codename}-security;
 };
 
 
 Using the following instead solves the problem:
 
 Unattended-Upgrade::Origins-Pattern {
 
 origin=${distro_id},codename=${distro_codename},label=${distro_id}-Security;
 };


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#788066: unattended-upgrades: Security updates not installed since last upgrade of unattended-upgrades package

[Michael Vogt]

On Mon, Jun 08, 2015 at 11:51:30AM +0200, Hans Yntema wrote:
 Package: unattended-upgrades
 Version: 0.83.3.1
 Severity: important

Thanks for your bugreport.

This is a brown-paperbug bug of me, sorry for this. I uploaded a new
version with a updated conffile to stable-proposed-updates that should
fix the issue [1]. Sorry for that and please let me know if that fixes
the issue.

Cheers,
 Michael

[1] https://wiki.debian.org/StableProposedUpdates

 Dear Maintainer,
 
 Initially (6 weeks ago), unattended-upgrades did not install 
 security-updates. I was able to fix by applying fix suggested in 783690.
 I added origin=Debian,codename=${distro_codename},label=Debian-Security to 
 50unattended-upgrades.
 
 Last week, unattended-upgrades got updated via Debian apt-get. Because I 
 manually changed 50unattended-upgrades (due to 783690),
 I decided to replace it with stock 50unattended-upgrades during the update 
 (assuming that 783690 would be fixed in the proper way)
 
 Since this last upgrade, security updates don't get installed automatically.
 
 Somehow, applying the fix suggested in 783690 does't work anymore. I get 
 errors when I run
 unattended-upgrade --dry-run --debug
 
 The unchanged 50unattended-upgrades yields following results
 
 sudo unattended-upgrade --dry-run --debug
 Initial blacklisted packages:
 Initial whitelisted packages:
 Starting unattended upgrades script
 Allowed origins are: ['o=Debian,a=jessie-security']
 Checking: libapache2-mod-php5 ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php-pear ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5 ([Origin component:'main' archive:'stable' origin:'Debian' 
 label:'Debian-Security' site:'security.debian.org' isTrusted:True])
 Checking: php5-cli ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-common ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-gd ([Origin component:'main' archive:'stable' origin:'Debian' 
 label:'Debian-Security' site:'security.debian.org' isTrusted:True])
 Checking: php5-intl ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-ldap ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-mcrypt ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-mysql ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-readline ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: php5-xsl ([Origin component:'main' archive:'stable' 
 origin:'Debian' label:'Debian-Security' site:'security.debian.org' 
 isTrusted:True])
 Checking: x2goserver ([Origin component:'main' archive:'' origin:'X2Go' 
 label:'X2Go' site:'packages.x2go.org' isTrusted:True])
 Checking: x2goserver-extensions ([Origin component:'main' archive:'' 
 origin:'X2Go' label:'X2Go' site:'packages.x2go.org' isTrusted:True])
 Checking: x2goserver-xsession ([Origin component:'main' archive:'' 
 origin:'X2Go' label:'X2Go' site:'packages.x2go.org' isTrusted:True])
 pkgs that look like they should be upgraded:
 Fetched 0 B in 0s (0 B/s)
 fetch.run() result: 0
 blacklist: []
 whitelist: []
 InstCount=0 DelCount=0 BrokenCount=0
 No packages found that can be upgraded unattended
 
 
 
 -- System Information:
 Debian Release: 8.1
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages unattended-upgrades depends on:
 ii  apt1.0.9.8
 ii  apt-utils  1.0.9.8
 ii  debconf [debconf-2.0]  1.5.56
 ii  init-system-helpers1.22
 ii  lsb-base   4.1+Debian13+nmu1
 ii  lsb-release4.1+Debian13+nmu1
 ii  python33.4.2-2
 ii  python3-apt0.9.3.11
 ii  ucf3.0030
 ii  xz-utils   5.1.1alpha+20120614-2+b3
 
 unattended-upgrades recommends no packages.
 
 Versions of packages unattended-upgrades suggests:
 ii  bsd-mailx   8.1.2-0.20141216cvs-2
 ii  postfix [mail-transport-agent]  2.11.3-1
 
 -- Configuration Files:
 

Bug#788049: unattended-upgrades: seems to fail on detecting deleted conffile, leading to conf prompt and error

[Michael Vogt]

On Mon, Jun 08, 2015 at 07:59:56AM +0200, Bernhard Schmidt wrote:
 Package: unattended-upgrades
 Version: 0.83.3
 Severity: important

Thanks for your bugreport.

 I _think_ there is an error in unattended-upgrades regarding the proper
 handling of changed configuration files.
 
 We have basically two large group of systems where unattended-upgrades
 is installed. In one of them we change
 /etc/apt/apt.conf.d/50unattended-upgrades, in another (puppet-managed)
 cluster we ship /etc/apt/apt.conf.d/99unattended-upgrades-local and
 delete /etc/apt/apt.conf.d/50unattended-upgrades
 
 The systems in the first cluster (changed file) have behaved as expected
 with the unattended-upgrades update shipped in the last Jessie point
 release
[..]

Indeed it is, thanks a bunch!

This should be fixed with
https://github.com/mvo5/unattended-upgrades/commit/8b7e14f0f394b2be90d00ed25a7475f615bde213

Fwiw, the fact that the conffile changed on a stable upload is a bug
in itself :(

Cheers,
 Michael

 2015-06-08 02:25:46,879 WARNING Package 'unattended-upgrades' has
 conffile prompt and needs to be upgraded manually
 2015-06-08 02:25:48,847 INFO package 'unattended-upgrades' not upgraded
 
 In the second cluster unattended-upgrades attempted an upgrade of itself
 and failed reproducibly due to a conffile prompt
 
 2015-06-07 02:20:01,297 INFO Packages that will be upgraded: base-files dbus 
 libdbus-1-3 libgnutls-deb0-28 libgnutls-openssl27 libpam-systemd libsystemd0 
 libudev1 linux-compiler-gcc-4.8-x86 linux-headers-3.16.0-4-amd64 
 linux-headers-3.16.0-4-common linux-image-3.16.0-4-amd64 linux-libc-dev perl 
 perl-base perl-modules ruby systemd systemd-sysv tasksel tasksel-data udev 
 unattended-upgrades
 2015-06-07 02:20:01,298 INFO Writing dpkg log to 
 '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
 2015-06-07 02:20:16,887 ERROR Exception happened during upgrade.
 Traceback (most recent call last):
   File /usr/bin/unattended-upgrade, line 472, in upgrade_in_minimal_steps
 res = cache.commit(install_progress=iprogress)
   File /usr/lib/python3/dist-packages/apt/cache.py, line 505, in commit
 raise SystemError(installArchives() failed)
 SystemError: installArchives() failed
 2015-06-07 02:20:16,890 ERROR Installing the upgrades failed!
 2015-06-07 02:20:16,890 ERROR error message: 'installArchives() failed'
 2015-06-07 02:20:16,890 ERROR dpkg returned a error! See 
 '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
 
 Preparing to unpack .../unattended-upgrades_0.83.3.1_all.deb ...
 Unpacking unattended-upgrades (0.83.3.1) over (0.83.3) ...
 Processing triggers for systemd (215-17) ...
 Processing triggers for man-db (2.7.0.2-5) ...
 Setting up unattended-upgrades (0.83.3.1) ...
 
 Configuration file '/etc/apt/apt.conf.d/50unattended-upgrades'
  == Deleted (by you or by a script) since installation.
  == Package distributor has shipped an updated version.
What would you like to do about it ?  Your options are:
 Y or I  : install the package maintainer's version
 N or O  : keep your currently-installed version
   D : show the differences between the versions
   Z : start a shell to examine the situation
  The default action is to keep your current version.
 *** 50unattended-upgrades (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
 package unattended-upgrades (--configure):
  EOF on stdin at conffile prompt
 Errors were encountered while processing:
  unattended-upgrades
 Error in function: 
 Log ended: 2015-06-07  02:20:16
 
 This leads to unattended-upgrades being held in a half-configured state.
 
 So it seems that unattended-upgrades does detect changed configuration
 files, but not deleted ones. 
 
 Bernhard


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#788066: unattended-upgrades: Security updates not installed since last upgrade of unattended-upgrades package

[Michael Vogt]

On Wed, Jun 10, 2015 at 12:18:32PM +0200, Johannes Weißl wrote:
 On Mon, Jun 08, 2015 at 11:51AM +0200, Hans Yntema wrote:
  Since this last upgrade, security updates don't get installed automatically.
 
 I can confirm this, the fix of #783690 seems to be faulty. It uses
 Allowed-Origins instead of Origins-Pattern, which does not seem to
 support codenames (e.g. Jessie) nor matching only security updates.
 
 This works:
 
 Unattended-Upgrade::Origins-Pattern {
   origin=${distro_id},codename=${distro_codename},label=Debian-Security;
 }
 
 (drop the ,label=Debian-Security if you want normal updates as well,
 as suggested in #787945)
[..]

Sorry for this, this is a brown-paperbag bug in my upload, I uploaded
a new 0.83.3.2 to stable-proposed-updates [1]

Sorry,
 Michael

[1] https://wiki.debian.org/StableProposedUpdates


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#788358: unattended-upgrades: Automatic-Reboot function is now broken

[Michael Vogt]

On Fri, Jun 12, 2015 at 12:19:54PM +0100, John Smith wrote:
 Ok, thanks. Will this fix be applied to my existing Jessie installation
 somehow via the usual apt-get upgrade?

I uploaded a new version to stable-updates.

 On 12 June 2015 at 12:09, Michael Vogt m...@debian.org wrote:
 
 
  This got fixed in version 0.83.4:
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#786869: help needed?

[Michael Vogt]

Hi,

I ran accross this issue today and was wondering if I can help in any
way? i.e. sponsor the debian upload with the fix or update to a new
upstream version?

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#787945: Bad build of 0.83.3.1 for jessie

[Michael Vogt]

On Mon, Jun 15, 2015 at 01:59:32PM +0200, Till Maas wrote:
 Hi,
Hi,

 unattendend-upgrades-0.83.3.1 seems to have been built on a Ubuntu
 system instead of a Debian system, therefore it contains the Ubuntu
 config file:
 
 https://sources.debian.net/src/unattended-upgrades/0.83.3.1/data/50unattended-upgrades.Ubuntu/
 
 instead of the Debian one:
 https://sources.debian.net/src/unattended-upgrades/0.83.3.1/data/50unattended-upgrades.Debian/
 
 There are not logs at
 
 https://buildd.debian.org/status/package.php?p=unattended-upgradessuite=jessie
 
 which indicates that the build did not happen on a clean Debian build
 system.
 
 Therefore please re-build the package with the proper Debian config
 file.

Uh, thats a brown-paperbag bug indeed :/ Sorry for that. I always
build in clean schroots, looks like I picked the wrong one this time,
I'm sorry!

Fix is uploaded.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#788358: unattended-upgrades: Automatic-Reboot function is now broken

[Michael Vogt]

On Wed, Jun 10, 2015 at 04:12:39PM +0100, coder5 wrote:
 Package: unattended-upgrades
 Version: 0.83.3.1
 Severity: normal

Thanks for your bugreport.

 The update-notifier-common package has been removed from Jessie and as a 
 result, /var/run/reboot-required will never be created. Consequently, the 
 Automatic-Reboot option will never cause the system to reboot after an 
 upgrade which requires one.
 
 Therefore unattended-upgrades needs some other way of determining if the 
 system needs a post-upgrade reboot.

This got fixed in version 0.83.4:

unattended-upgrades (0.83.4) unstable; urgency=medium

  [ Alexandre Detiste ]
* fix sending dpkg log in mails (Closes: #776752)

  [ Michael Vogt ]
* Document how the reboot-required file is generated (Closes: #776769)
* Add recommends to cron|cron-daemon|anacron (Closes: #776550),
thanks to Alexandre Detiste and christophe
* Ship /etc/kernel/postinst.d hook to ensure the
  /var/run/reboot-required file is created (avoid the need to have
  update-notifier-common installed) (Closes: #776769)

 -- Michael Vogt m...@debian.org  Tue, 10 Feb 2015 13:58:26 +0100
 

 -- System Information:
 Debian Release: 8.1
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
 Architecture: amd64 (x86_64)
 
 Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages unattended-upgrades depends on:
 ii  apt1.0.9.8
 ii  apt-utils  1.0.9.8
 ii  debconf [debconf-2.0]  1.5.56
 ii  init-system-helpers1.22
 ii  lsb-base   4.1+Debian13+nmu1
 ii  lsb-release4.1+Debian13+nmu1
 ii  python33.4.2-2
 ii  python3-apt0.9.3.11
 ii  ucf3.0030
 ii  xz-utils   5.1.1alpha+20120614-2+b3
 
 unattended-upgrades recommends no packages.
 
 Versions of packages unattended-upgrades suggests:
 ii  bsd-mailx  8.1.2-0.20141216cvs-2
 ii  exim4-daemon-light [mail-transport-agent]  4.84-8
 
 -- Configuration Files:
 /etc/apt/apt.conf.d/50unattended-upgrades changed:
 // Automatically upgrade packages from these (origin:archive) pairs
 Unattended-Upgrade::Allowed-Origins {
   ${distro_id}:${distro_codename}-security;
   ${distro_id}:${distro_codename}-updates;
 //${distro_id}:${distro_codename}-proposed;
 //${distro_id}:${distro_codename}-backports;
 };
 // List of packages to not update (regexp are supported)
 Unattended-Upgrade::Package-Blacklist {
 //vim;
 //libc6;
 //libc6-dev;
 //libc6-i686;
 };
 // This option allows you to control if on a unclean dpkg exit
 // unattended-upgrades will automatically run 
 //   dpkg --force-confold --configure -a
 // The default is true, to ensure updates keep getting installed
 //Unattended-Upgrade::AutoFixInterruptedDpkg false;
 // Split the upgrade into the smallest possible chunks so that
 // they can be interrupted with SIGUSR1. This makes the upgrade
 // a bit slower but it has the benefit that shutdown while a upgrade
 // is running is possible (with a small delay)
 //Unattended-Upgrade::MinimalSteps true;
 // Install all unattended-upgrades when the machine is shuting down
 // instead of doing it in the background while the machine is running
 // This will (obviously) make shutdown slower
 //Unattended-Upgrade::InstallOnShutdown true;
 // Send email to this address for problems or packages upgrades
 // If empty or unset then no email is sent, make sure that you
 // have a working mail setup on your system. A package that provides
 // 'mailx' must be installed. E.g. u...@example.com
 //Unattended-Upgrade::Mail root;
 // Set this value to true to get emails only on errors. Default
 // is to always send a mail if Unattended-Upgrade::Mail is set
 //Unattended-Upgrade::MailOnlyOnError true;
 // Do automatic removal of new unused dependencies after the upgrade
 // (equivalent to apt-get autoremove)
 //Unattended-Upgrade::Remove-Unused-Dependencies false;
 Unattended-Upgrade::Remove-Unused-Dependencies true;
 // Automatically reboot *WITHOUT CONFIRMATION*
 //  if the file /var/run/reboot-required is found after the upgrade 
 //Unattended-Upgrade::Automatic-Reboot false;
 Unattended-Upgrade::Automatic-Reboot true;
 // If automatic reboot is enabled and needed, reboot at the specific
 // time instead of immediately
 //  Default: now
 //Unattended-Upgrade::Automatic-Reboot-Time 02:00;
 // Use apt bandwidth limit feature, this example limits the download
 // speed to 70kb/sec
 //Acquire::http::Dl-Limit 70;
 
 
 -- debconf information:
 * unattended-upgrades/enable_auto_updates: true


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#787067: jessie-pu: package apt/1.0.9.8

[Michael Vogt]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: pu
Tags: jessie
Severity: normal

Dear stable release managers,

I would like to ask for a p-u upload for apt. The following
bugs will be fixed with that upload:

  * parse specific-arch dependencies correctly on single-arch systems
(Closes: 60)
  * remove first package seen is native package assumption.
Thanks to Axel Beckert for testing (Closes: 782777)
  * Fix endless loop in apt-get update that can cause disk
fillup (LP: #1445239)

The code diff is attached. The fixes were also uploaded to sid some
days ago.

Thanks for your consideration,
 David  Michael

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

diff -Nru apt-1.0.9.8/apt-pkg/pkgcache.cc apt-1.0.9.8.1/apt-pkg/pkgcache.cc
--- apt-1.0.9.8/apt-pkg/pkgcache.cc 2015-04-13 07:25:06.0 +0200
+++ apt-1.0.9.8.1/apt-pkg/pkgcache.cc   2015-05-28 11:08:42.0 +0200
@@ -230,12 +230,7 @@
 pkgCache::PkgIterator pkgCache::FindPkg(const string Name) {
size_t const found = Name.find(':');
if (found == string::npos)
-   {
-   if (MultiArchCache() == false)
-   return SingleArchFindPkg(Name);
-   else
-   return FindPkg(Name, native);
-   }
+  return FindPkg(Name, native);
string const Arch = Name.substr(found+1);
/* Beware: This is specialcased to handle pkg:any in dependencies as
   these are linked to virtual pkg:any named packages with all archs.
@@ -249,13 +244,6 @@
 // -
 /* Returns 0 on error, pointer to the package otherwise */
 pkgCache::PkgIterator pkgCache::FindPkg(const string Name, string const 
Arch) {
-   if (MultiArchCache() == false  Arch != none) {
-   if (Arch == native || Arch == all || Arch == any ||
-   Arch == NativeArch())
-   return SingleArchFindPkg(Name);
-   else
-   return PkgIterator(*this,0);
-   }
/* We make a detour via the GrpIterator here as
   on a multi-arch environment a group is easier to
   find than a package (less entries in the buckets) */
diff -Nru apt-1.0.9.8/apt-pkg/pkgcache.h apt-1.0.9.8.1/apt-pkg/pkgcache.h
--- apt-1.0.9.8/apt-pkg/pkgcache.h  2015-04-13 07:25:06.0 +0200
+++ apt-1.0.9.8.1/apt-pkg/pkgcache.h2015-05-28 11:08:42.0 +0200
@@ -218,7 +218,7 @@
 
 private:
bool MultiArchEnabled;
-   PkgIterator SingleArchFindPkg(const std::string Name);
+   APT_DEPRECATED PkgIterator SingleArchFindPkg(const std::string Name);
 };
/*}}}*/
 // Header structure/*{{{*/
diff -Nru apt-1.0.9.8/configure apt-1.0.9.8.1/configure
--- apt-1.0.9.8/configure   2015-04-13 18:47:50.0 +0200
+++ apt-1.0.9.8.1/configure 2015-05-28 11:10:56.0 +0200
@@ -2436,7 +2436,7 @@
 
 
 PACKAGE=apt
-PACKAGE_VERSION=1.0.9.8
+PACKAGE_VERSION=1.0.9.8.1
 PACKAGE_MAIL=APT Development Team de...@lists.debian.org
 cat confdefs.h _ACEOF
 #define PACKAGE $PACKAGE
diff -Nru apt-1.0.9.8/configure.ac apt-1.0.9.8.1/configure.ac
--- apt-1.0.9.8/configure.ac2015-04-13 18:47:48.0 +0200
+++ apt-1.0.9.8.1/configure.ac  2015-05-28 11:10:55.0 +0200
@@ -18,7 +18,7 @@
 AC_CONFIG_HEADER(include/config.h:buildlib/config.h.in 
include/apti18n.h:buildlib/apti18n.h.in)
 
 PACKAGE=apt
-PACKAGE_VERSION=1.0.9.8
+PACKAGE_VERSION=1.0.9.8.1
 PACKAGE_MAIL=APT Development Team de...@lists.debian.org
 AC_DEFINE_UNQUOTED(PACKAGE,$PACKAGE)
 AC_DEFINE_UNQUOTED(PACKAGE_VERSION,$PACKAGE_VERSION)
diff -Nru apt-1.0.9.8/debian/changelog apt-1.0.9.8.1/debian/changelog
--- apt-1.0.9.8/debian/changelog2015-04-13 07:25:06.0 +0200
+++ apt-1.0.9.8.1/debian/changelog  2015-05-28 11:08:42.0 +0200
@@ -1,3 +1,16 @@
+apt (1.0.9.8.1) stable; urgency=medium
+
+  [ Michael Vogt ]
+  * Fix endless loop in apt-get update that can cause disk fillup (LP: 
#1445239)
+
+  [ David Kalnischkies ]
+  * parse specific-arch dependencies correctly on single-arch systems
+(Closes: 60)
+  * remove first package seen is native package assumption.
+Thanks to Axel Beckert for testing (Closes: 782777)
+
+ -- Michael Vogt m...@debian.org  Thu, 28 May 2015 11:07:45 +0200
+
 apt (1.0.9.8) unstable; urgency=medium
 
   [ David Kalnischkies ]
diff -Nru apt-1.0.9.8/debian/gbp.conf apt-1.0.9.8.1/debian/gbp.conf
--- apt-1.0.9.8/debian/gbp.conf 2015-04-13 07:25:06.0 +0200
+++ apt-1.0.9.8.1/debian/gbp.conf   2015-05-28 11:08:42.0 +0200
@@ -1,7 +1,7 @@
 [DEFAULT]
 prebuild = ./prepare-release pre-export
 postbuild = ./prepare-release post-build
-debian-branch = debian/sid
+debian-branch

Bug#779217: python-apt-doc: [PATCH] Rewrite example using the new API

[Michael Vogt]

On Wed, Mar 04, 2015 at 07:06:18PM +0100, von wrote:
 Package: python-apt-doc
 Version: 0.9.3.11
 Followup-For: Bug #779217
 
 Here is a patch rewriting the print_uris.py example with the new API.
 
 This patch, as well as all contributions from mat...@mailoo.org, is under the 
 GPL-2+ License.

Thanks a bunch! This is merged into git now and it will be part of the
next upload.

Cheers,
 Michael

 -- System Information:
 Debian Release: 8.0
   APT prefers testing
   APT policy: (500, 'testing'), (400, 'unstable'), (300, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages python-apt-doc depends on:
 ii  libjs-jquery  1.7.2+dfsg-3.2
 ii  libjs-sphinxdoc   1.2.3+dfsg-1
 ii  libjs-underscore  1.7.0~dfsg-1
 ii  python-apt0.9.3.11
 
 python-apt-doc recommends no packages.
 
 python-apt-doc suggests no packages.
 
 -- no debconf information

 From a9cbcf1e90e32971d370d97ae8d37d25fe0835f2 Mon Sep 17 00:00:00 2001
 From: von mat...@mailoo.org
 Date: Sat, 28 Feb 2015 17:00:04 +0100
 Subject: [PATCH] Update the print_uris.py example to use the new API
 
 ---
  doc/examples/print_uris.py | 18 +++---
  1 file changed, 3 insertions(+), 15 deletions(-)
 
 diff --git a/doc/examples/print_uris.py b/doc/examples/print_uris.py
 index 06043e4..27e49d1 100755
 --- a/doc/examples/print_uris.py
 +++ b/doc/examples/print_uris.py
 @@ -4,19 +4,7 @@
  #
  
  import apt
 -import apt_pkg
  
 -
 -cache = apt.Cache()
 -upgradable = filter(lambda p: p.is_upgradable, cache)
 -
 -
 -for pkg in upgradable:
 -pkg._lookupRecord(True)
 -path = apt_pkg.TagSection(pkg._records.record)[Filename]
 -cand = pkg._depcache.get_candidate_ver(pkg._pkg)
 -for (packagefile, i) in cand.file_list:
 -indexfile = cache._list.find_index(packagefile)
 -if indexfile:
 -uri = indexfile.archive_uri(path)
 -print uri
 +for pkg in apt.Cache():
 +  if pkg.is_upgradable:
 +print pkg.candidate.uri
 -- 
 2.1.4
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#783810: unattended-upgrades: Shows a message saying Started when machine is being rebooted (!)

[Michael Vogt]

On Thu, Apr 30, 2015 at 01:34:40PM +0200, Santiago Vila wrote:
 Package: unattended-upgrades
 Version: 0.83.3

Thanks for your bugreport.

 When I reboot a machine having this package installed and configured
 to actually work, I see this:
 
 Started Unattended Upgrades
 
 How is that possible?
 
 If this is not harmless (I really don't know, and that's why I'm not
 using any severity here), please consider an upload for the next point
 release of jessie.

The message is indeed confusing. What its actaully all about is that
unattended-upgrades needs to check if there is a upgrade in
progress. If this is the case it will halt the shutdown progress until
the packaging system is in a consistent state (either by finishing or
by stoping if it was in minimal upgrade steps mode).

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#779290: unblock: dvd+rw-tools/7.1-11

[Michael Vogt]

On Thu, Feb 26, 2015 at 09:40:44PM -0300, Rogério Brito wrote:
 Hi.
Hi Rogério,
 
 On Feb 26 2015, Ivo De Decker wrote:
  On Thu, Feb 26, 2015 at 05:19:53PM +0100, Michael Vogt wrote:
   Please unblock package dvd+rw-tools (not yet uploaded, I'm asking
   for approval before uploading).
  
  Please go ahead and remove the moreinfo tag from this bug once the upload
  is in unstable.
 
 I'm a bit overloaded right now. Michael, can you please NMU what you have?

Sure, I just did the upload for this. Its a minimal diff to improve
the chances that this makes it into the release.

 The changes that I have are on the master branch of
 
https://github.com/rbrito/pkg-dvd-rw-tools
 
 but they have some modernization and/or cosmetic changes (well, changing the
 packaging to compat 9 of debhelper enables hardening of the package, which
 isn't enabled in the version in unstable---if that is OK for testing, then I
 guess that the work of uploading stuff is almost complete and only a quick
 last review would suffice).

Thanks for this! I like that, especially that the hardening is
enabled now. For the next upload I guess :) (unless the release team
grants a exception for the benefit of having the hardening).

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#779290: unblock: dvd+rw-tools/7.1-11

[Michael Vogt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package dvd+rw-tools (not yet uploaded, I'm asking
for approval before uploading).

The current dvd+rw-tools will fail right at the end when burning
a bluray BD-R disc with the error message CLOSE SESSION failed.

This affects all frontends that use growisofs (like k3b and more,
there are recommendations on the net to install cdrecord from third
party sources to workaround the issue).

The relevant bug and fix is described in #713016. Its a one-line
diff that is used in fedora since June 2013 [1]. I think it would
be good if we could release with a fix for this bug as bluray seem
to be quite common and we should support it with free tools.

The full diff is attached.

Thanks for your consideration,
 Michael


unblock dvd+rw-tools/7.1-11

[1] 
http://pkgs.fedoraproject.org/cgit/dvd+rw-tools.git/commit/?id=545689bfb2a04cb642b48a8495024e23545363a4

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

Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
diff -Nru dvd+rw-tools-7.1/debian/changelog dvd+rw-tools-7.1/debian/changelog
--- dvd+rw-tools-7.1/debian/changelog   2011-03-07 10:48:42.0 -0500
+++ dvd+rw-tools-7.1/debian/changelog   2015-02-26 10:40:30.0 -0500
@@ -1,3 +1,12 @@
+dvd+rw-tools (7.1-11) unstable; urgency=medium
+
+  * debian/patches/10-blue-ray-bug713016.patch:
+- apply patch from Thomas Schmitt to fix in session closing
+  on blue ray (closes: #713016), LP: #1113679
+  * added myself to uploaders
+
+ -- Michael Vogt m...@debian.org  Thu, 19 Feb 2015 12:34:23 +0100
+
 dvd+rw-tools (7.1-10) unstable; urgency=low
 
   * Add patch to fix grammar in manpage. Closes: #607605.
diff -Nru dvd+rw-tools-7.1/debian/control dvd+rw-tools-7.1/debian/control
--- dvd+rw-tools-7.1/debian/control 2011-03-07 08:53:35.0 -0500
+++ dvd+rw-tools-7.1/debian/control 2015-02-26 10:41:23.0 -0500
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Optical Media Tools Team 
pkg-opt-media-t...@lists.alioth.debian.org
 Uploaders: TANIGUCHI Takaki tak...@debian.org,
-  Rogério Brito rbr...@ime.usp.br
+  Rogério Brito rbr...@ime.usp.br,
+   Michael Vogt m...@debian.org
 DM-Upload-Allowed: yes
 Build-Depends: debhelper (= 7),
   libcam-dev [kfreebsd-i386 kfreebsd-amd64],
diff -Nru dvd+rw-tools-7.1/debian/patches/10-blue-ray-bug713016.patch 
dvd+rw-tools-7.1/debian/patches/10-blue-ray-bug713016.patch
--- dvd+rw-tools-7.1/debian/patches/10-blue-ray-bug713016.patch 1969-12-31 
19:00:00.0 -0500
+++ dvd+rw-tools-7.1/debian/patches/10-blue-ray-bug713016.patch 2015-02-26 
10:39:24.0 -0500
@@ -0,0 +1,17 @@
+## Description: Fix spurious CLOSE SESSION failed on BD-R
+## Origin/Author: Thomas Schmitt scdbac...@gmx.net
+## Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713016
+Index: dvd+rw-tools-7.1/growisofs_mmc.cpp
+===
+--- dvd+rw-tools-7.1.orig/growisofs_mmc.cpp
 dvd+rw-tools-7.1/growisofs_mmc.cpp
+@@ -756,6 +757,9 @@ static void bd_r_format (Scsi_Command c
+ 
+ wait_for_unit (cmd);
+ 
++// debian bug #713016
++bdr_plus_pow = 1;
++
+ cmd[0] = 0x35;// FLUSH CACHE
+ cmd[9] = 0;
+ cmd.transport();
diff -Nru dvd+rw-tools-7.1/debian/patches/series 
dvd+rw-tools-7.1/debian/patches/series
--- dvd+rw-tools-7.1/debian/patches/series  2011-03-07 10:45:34.0 
-0500
+++ dvd+rw-tools-7.1/debian/patches/series  2015-02-26 10:39:24.0 
-0500
@@ -8,3 +8,4 @@
 08-includes.patch
 09-wctomb.patch
 ignore_pseudo_overwrite.patch
+10-blue-ray-bug713016.patch

Bug#713016: New upload of dvd+rw-tools (was: Re: New upload?)

[Michael Vogt]

On Fri, Feb 20, 2015 at 09:54:38PM -0200, Rogério Brito wrote:
 Hi, Michael.
HI Rogério,
 
 On Feb 19 2015, Michael Vogt wrote:
  I tested the patch and it works for me too,
 
 Not having a bluray disc/drive available, I wasn't able to test this
 myself. (To be honest, I have never even *seen* a BD).

No worries, I understand your concern. But it seems to be pretty safe,
http://pkgs.fedoraproject.org/cgit/dvd+rw-tools.git/commit/?id=545689bfb2a04cb642b48a8495024e23545363a4
has it since June 2013 and I burned a buncf of blurays with it as
well. 
 
  I would really like to see this fix in Debian and want to help making this
  happen.
 
 Would this have any chance of getting into the next stable?

I think we should try, targeted fixes for release criticial bugs of
severity critical are stull supported
(https://release.debian.org/jessie/freeze_policy.html)

I guess one could argue that this is a critical bug as it prevents
bluray burning. The diff is tiny, the regression risk too. Worth a
shoot in my opinion :)

  If there are no objections I would like to do a upload with the patch
  of the package and add myself to the uploaders.
 
 Do you have changes ready already? The packaging is in a desperate need of a
 facelift and adoption of best current practices (e.g., a pristine-tar
 branch, updating many other things etc.).

I think its a good goal to modernize the packaging. However if we want to
try to get this change into testing I think the smaller the diff, the
better the chances :)

For Ubuntu I did:
https://launchpadlibrarian.net/198147479/dvd%2Brw-tools_7.1-10build1_7.1-10ubuntu0.14.10.1.diff.gz
 

Its a tiny diff, I think we should try to get that into testing and do
further packaging later.

 I am taking a *brief* look at the packaging, but I would appreciate any kind
 of help.
 
 I think that I will put a copy of this under my github account, since I like
 the user interface better there.

Sure, thats fine.
 
 Also, as I have expressed in the past, I think that this team should be
 merged with the other team that is taking care of, say, cdrkit and others.

I have no opinion either way :)

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#778769: stop being nice does not work

[Michael Vogt]

On Thu, Feb 19, 2015 at 03:26:13PM +0100, Harald Staub wrote:
 Package: unattended-upgrades
 Version: 0.83.3, 0.83.4
 
 See:
 https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1422345
 
 Since version 0.81, unattended-upgrades does the upgrade calculation with
 os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the
 following call is used:
 os.nice(0)
 
 Since the argument is interpreted as incremental, this should be:
 os.nice(-19)
 
 Without this fix, this problem is back:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850
 unattended-upgrades: nice 19/ionice idle inherited by restarted processes
 
 Found in the trusty version (0.82.1ubuntu2), but probably in any version
 (including Debian) since 0.81.

Thanks, I uploaded the fix today as
unattended-upgrades_0.83.5_amd64.changes to unstable.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#713016: New upload?

[Michael Vogt]

Hi,

I tested the patch and it works for me too, I would really like to see
this fix in Debian and want to help making this happen.

If there are no objections I would like to do a upload with the patch
of the package and add myself to the uploaders.

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776550: unattended-upgrades: Depend on cron

[Michael Vogt]

On Wed, Feb 04, 2015 at 06:57:28PM +0100, Alexandre Detiste wrote:
 Hi,
Hi,
 
 On Debian, the 'Recommends:' should really be cron | cron-daemon | anacron.
 
 There will certainly a transition going this way after Jessie is released.
 https://lists.debian.org/debian-devel/2014/10/msg00474.html
 
 This virtual package 'cron-daemon' is not used by the ubuntu-* meta-packages; 
 https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1409266
 ...but it doesn't hurt to be there.
 And the cron.deb in Ubuntu does provide cron-daemon for example.

Thanks! I added it now in git.

Cheers,
 Michael
 
 Alexandre
 
 Le mercredi 4 février 2015, 18:09:16 Michael Vogt a écrit :
  On Thu, Jan 29, 2015 at 09:33:24AM +0100, christophe wrote:
   
   Package: unattended-upgrades
   Version: 0.79.5+wheezy1
   Severity: normal
  
  Thanks for your bugreport.
  
  I added a Recommends: cron|anacron in git and it will be part of the
  next upload.
  
  Cheers,
   Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776550: unattended-upgrades: Depend on cron

[Michael Vogt]

On Thu, Jan 29, 2015 at 09:33:24AM +0100, christophe wrote:
 
 Package: unattended-upgrades
 Version: 0.79.5+wheezy1
 Severity: normal

Thanks for your bugreport.

I added a Recommends: cron|anacron in git and it will be part of the
next upload.

Cheers,
 Michael
 
 Dear Maintainer,
 *** Please consider answering these questions, where appropriate ***
 
* What led up to the situation?  Fresh install of LXC container with
 homegrown template
* What exactly did you do (or not do) that was effective (or
  ineffective)? Installed unattended-upgrades, but it didn't upgrade
 packages because of missing cron package
* What was the outcome of this action? No upgrades
* What outcome did you expect instead? Upgrades
 
 *** End of the template - remove these lines ***
 
 
 -- System Information:
 Debian Release: 7.6
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.16-0.bpo.2-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages unattended-upgrades depends on:
 ii  apt0.9.7.9+deb7u6
 ii  apt-utils  0.9.7.9+deb7u6
 ii  debconf [debconf-2.0]  1.5.49
 ii  lsb-base   4.1+Debian8+deb7u1
 ii  lsb-release4.1+Debian8+deb7u1
 ii  python 2.7.3-4+deb7u1
 ii  python-apt 0.8.8.2
 ii  ucf3.0025+nmu3
 ii  xz-utils   5.1.1alpha+20120614-2
 
 unattended-upgrades recommends no packages.
 
 Versions of packages unattended-upgrades suggests:
 ii  bsd-mailx  8.1.2-0.2006cvs-1
 ii  exim4-daemon-light [mail-transport-agent]  4.80-7
 
 -- debconf information:
 * unattended-upgrades/enable_auto_updates: true


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776753: unattended-upgrades: dpkg log extraneously include progress indicator

[Michael Vogt]

On Wed, Feb 04, 2015 at 02:09:01PM +0100, Alexandre Detiste wrote:
  I can not reproduce this on my workstation, I don't have a raspi here
  right now to test it against that. Do you see this on a normal sid
  also or is this specific to the package set for the raspi?
 
 This is not Raspi specific at all.
 The only think modified by their patch is the default configuration file.
 
 I thought it was because of 'Dpkg::Progress-Fancy 1;'
 as advertised, but it doesn't seem to be the case.
 
 Maybe it's because I use systemd-cron instead of cron
 and the tty or environment is not set the same way
 and then dpkg or it's python wrapper doesn't know it
 shouldn't display a progress bar.

Thanks! That sounds plausible, if systemd-cron runs the jobs inside a
pty that explains what you see. Is this the case? If so I will have to
think a bit what can be done, probably involves some poking at the
dpkg source code to figure out if there is a config switch or a
environment variable to stop dpkg from showing this progress.

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776769: unattended-upgrades: Document hooks necessary for automatic reboots

[Michael Vogt]

On Sun, Feb 01, 2015 at 03:41:20PM +0100, Bernhard Schmidt wrote:
 Package: unattended-upgrades
 Version: 0.83.3
 Severity: wishlist

Thanks for your bugreport.
 
 Hi,
 
 the README states
 
 * `Unattended-Upgrade::Automatic-Reboot` - boolean (default:False)
  
  Automatically reboot *WITHOUT CONFIRMATION* if the file
  /var/run/reboot-required is found after the upgrade.
 
 however it does not say in any way how this file is created and that there
 is nothing triggering it in a default Debian installation.
 
 Please document this fact and refer to either the package 
 update-notifier-common or a manual hook in /etc/kernel/postinst.d
 
 See also
 http://serverfault.com/questions/551594/unattended-upgrades-does-not-reboot

I pushed a fix to
https://github.com/mvo5/unattended-upgrades/commit/1418bae710bb7304a39b483249e11fc015fbf1e0
and it will be part of the next upload.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776753: unattended-upgrades: dpkg log extraneously include progress indicator

[Michael Vogt]

On Sun, Feb 01, 2015 at 12:09:25PM +0100, Alexandre Detiste wrote:
 Package: unattended-upgrades
 Version: 0.81+rpi1
 Severity: minor

Thanks for your bugreport.
 
[..]
 I have found a way to get rid of those lines;
 but this is not a proper fix;
 and only work with my current locale:
 
  if stanza_start = install_start_time:
  found_start = True
 -if found_start:
 +if found_start and not line.startswith('(Lecture de la base de 
 données...'):
  content.append(line)
 
 problem also found on 0.83.3, but hidden by other bug #776752
[..]

I can not reproduce this on my workstation, I don't have a raspi here
right now to test it against that. Do you see this on a normal sid
also or is this specific to the package set for the raspi?

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776752: uu: install_start_time = datetime.datetime.now() should be computed early

[Michael Vogt]

On Sun, Feb 01, 2015 at 11:48:50AM +0100, Alexandre Detiste wrote:
 Package: unattended-upgrades
 Version: 0.83.3
 Severity: minor
 Tags: patch

Thanks for your bugreport and your patch!

[..] 
 Due to truncating of time values less than a second,
 the dpkg log is sometimes not found; and
 if stanza_start = install_start_time:
 doens't work as expected.

Thats really interessting, I assumed the = relation would have
helped here :/ Oh well. I merged your patch and it will be part of the
next upload.

Many thanks!
 Michael

 It is easy to fix, the line install_start_time = datetime.datetime.now()
 just needs to be moved up to the start of main()
 
 https://github.com/a-detiste/unattended-
 upgrades/commit/83f9d2b76428a4cad6f72d91b08a93a17d8d8c3b
 
 Alexandre Detiste
 
 
 
 -- System Information:
 Debian Release: 8.0
   APT prefers testing
   APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
 Architecture: amd64 (x86_64)
 Foreign Architectures: i386
 
 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/6 CPU cores)
 Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 Init: systemd (via /run/systemd/system)
 
 Versions of packages unattended-upgrades depends on:
 ii  apt1.0.9.6
 ii  apt-utils  1.0.9.6
 ii  debconf [debconf-2.0]  1.5.55
 ii  init-system-helpers1.22
 ii  lsb-base   4.1+Debian13+nmu1
 ii  lsb-release4.1+Debian13+nmu1
 ii  python33.4.2-2
 ii  python3-apt0.9.3.11
 ii  ucf3.0030
 ii  xz-utils   5.1.1alpha+20120614-2+b3
 
 unattended-upgrades recommends no packages.
 
 Versions of packages unattended-upgrades suggests:
 pn  bsd-mailx  none
 ii  nullmailer [mail-transport-agent]  1:1.13-1
 
 -- debconf information:
 * unattended-upgrades/enable_auto_updates: true
 
 -- debsums errors found:
 debsums: changed file /usr/bin/unattended-upgrade (from unattended-upgrades 
 package)

 From 83f9d2b76428a4cad6f72d91b08a93a17d8d8c3b Mon Sep 17 00:00:00 2001
 From: Alexandre Detiste alexandre.deti...@gmail.com
 Date: Sun, 1 Feb 2015 11:36:04 +0100
 Subject: [PATCH] fix sending dpkg log in mails
 
 due to some rounding of time values less than a second,
 the dpkg log is not found
 ---
  unattended-upgrade | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
 
 diff --git a/unattended-upgrade b/unattended-upgrade
 index 0205897..39ea8d0 100755
 --- a/unattended-upgrade
 +++ b/unattended-upgrade
 @@ -1028,6 +1028,7 @@ def get_dpkg_log_content(logfile_dpkg, 
 install_start_time):
  
  
  def main(options, rootdir=):
 +install_start_time = datetime.datetime.now()
  
  # useful for testing
  if rootdir:
 @@ -1252,7 +1253,6 @@ def main(options, rootdir=):
  # only perform install step if we actually have packages to install
  pkg_install_success = None
  shutdown_lock = -1
 -install_start_time = datetime.datetime.now()
  if len(pkgs_to_upgrade)  0:
  # lock for the shutdown check - its fine if the system
  # is shutdown while downloading but not so much while installing
 -- 
 2.1.4
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#776905: Please consider adding libudev-dev as build-dependency

[Michael Vogt]

Package: util-linux
Version: 2.25.2-4.2

Could you please consider adding libudev-dev to the build-dependencies
of util-linux. This will enable lsblk to show the LABEL and
PARTLABEL information when running as a non-root user.

I ran into this issue when checking the lsblk output as non-root and
noticed that it won't display the parition label (e.g.
  $ lsblk --ascii --output NAME,LABEL --pairs
will show a empty label.

But
  $ sudo lsblk --ascii --output NAME,LABEL --pairs
will show the label (if you have a label :)

Adding the build-dependency fixes this.

Thanks for considering,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773256: dbus + triggers + apt issue (was: Bug#773256: pre-approval: unblock: dpkg/1.17.23)

[Michael Vogt]

On Thu, Jan 08, 2015 at 02:47:05AM +0100, Guillem Jover wrote:
 [ @deity: please check out the dbus issue below. ]
[..]
 [ Re dbus issue ]
  Noted.  Do we (still?) have a (reliable) way of reproducing the dbus
  trigger issue?
 
 We didn't up to now (AFAIK), but there's now very valuable data from
 Karl Ljungkvist at #774124. I've been able to reproduce the issue with
 that status file and apt (over a clean debootstrap of jessie, and
 adding i386 as a foreign arch). 

Thanks for pointing us towards this bugreport, this contains some good
information. I followed up there with some more questions, it would be
really nice to be able to reproduce what error happend that caused
this broken state.

 And have been trying out several things:
 
   * It seems to affect both apt from jessie/sid and wheezy. :(
 apt gets into a state it cannot recover from by itself.

Indeed, apt sees the triggers-pending and triggers-awaited state
and tries to run dpkg --configure on all those packages. This
fails.

   * «dpkg --configure --pending» solves the issue.
   * Using dpkg --force-configure-any only fixes the issue partially, :(
 because apt does not notice that the package has been implicitly
 configured, and tries to configure the package again and dpkg exits
 with an error for that run, which apt does not like much either (as
 I feared). So I'd need to also change dpkg to not fail configuring
 an already configure package, or try to detect that specific case.

When you say implicitly configured what does that mean exactly? Is
the issue here that apt should ignore the triggers-awaited state
because those will be dealt with by dpkg entirely?

I also wonder if there are further implications for apt by the trigger
changes. The ordering code in apt builds on the premise that there is
no implict configuration, it builds the unpack/configure ordering
early and its static. Is this still a valid assumption?

[..] 
 Before considering either reverting, or trying to find a workaround
 for this in dpkg, I'd like to know if this is easily fixable in apt
 and the implications of this problem (i.e. can it affect similar
 situations regardless of the recent dpkg trigger changes?) and the
 implications of such a fix.

We have code in pkgApplyStatus that detects and fixes not-ok
packages. So far it considered packages with
triggers-{pending,awaited} as something to just dpkg --configure. We
could change the code to ignore those states and simply let dpkg
handle them (via Davids code that ensures 'dpkg --configure -a' gets
called). Does that sound sensible?

I'm still a bit nervous about the issue that lead to #774124. It would
be good to get more data here.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#538568: apt: apt-get incorrect remaining time

[Michael Vogt]

On Thu, Jan 08, 2015 at 08:57:43AM +0100, Torquil Macdonald Sørensen wrote:
 Package: apt
 Version: 1.0.9.5
 Followup-For: Bug #538568

Thanks for the additional information.
 
 This is very similar to the remaining time I just got, after the
 download was finished:
 
 Fetched 379 kB in 213503982334601d 6h 58min 14s (0 B/s)
 
 Actually, the speed (0 B/s) is also wrong, but might just be a
 consequency of the large incorrect duration.

Was there anything unusual about this transfer? What protocol? Was it
particularly slow of fast? Is this reproducable in any way?

Thanks,
 Michael  


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#775163: apt pigs out in /var, particularly with multi-arch

[Michael Vogt]

On Sun, Jan 11, 2015 at 09:40:20PM -0800, Elliott Mitchell wrote:
 Package: apt
 Version: 0.9.7.9+deb7u7

Thanks for your bugreport.
 
 I've ended up examining how much space programs are using in /var, and
 APT is the top pig, using close to half of /var as /var/lib/apt/lists,
 one factor does appear to be exasperating this, `dpkg` has 5 foreign
 architectures.
 
 Trying a few compression methods:
 
 426248  lists
 114580  lists.gz
 90868   lists.bz2
 85648   lists.lzma
 86532   lists.xz
 
 Nearly all of this space is being used for the Packages files.  Merely
 compressing them would be a rather major improvement.  The main Debian
 testing file is the biggest of these.

You can use the configuration option 

Acquire::GzipIndexes 1;

to keep the indexes compressed on disk. You trade the speed for
building the mmap cache with the size of the data on disk. 

Note that this option works best with later apt versions (1.0.9.2 or
later) where this option supports all compressions that apt supports
(the older versions only support gzip).

Cheers,
 Michael

 
 -- 
 (\___(\___(\__  --= 8-) EHM =--  __/)___/)___/)
  \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
   \_CS\   |  _  -O #include stddisclaimer.h O-   _  |   /  _/
 8A19\___\_|_/58D2 7E3D DDF4 7BA6 -PGP- 41D1 B375 37D0 8714\_|_/___/5445
 
 
 -- 
 To UNSUBSCRIBE, email to deity-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: https://lists.debian.org/20150112054020.ga74...@scollay.m5p.com
 


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#774124: dpkg.status backup from before 30dec

[Michael Vogt]

Hi,

thanks a lot for the logs and the status file. The status file is very
useful and we now can debug why apt can't recover from this dpkg
status file.

But it would also be really great if a backup of the dpkg.status file
from before 30dec would be availalble (one where dbus is still at
version 1.8.12-1). This might help us to reproduce the situation that
lead to the actual error.

From reading the logs it appears that the dist-upgrade at 
2014-12-30  10:41:26 fails with a dpkg error code. Unfortunately
there is nothing in the term.log output that indicates what the actual
problem is, the log stops at Log ended: 2014-12-30  10:42:16 without
a error message. I wonder what is going on there and the old status
file might help us to find out about it. So if you still have that,
could you please attach it?

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773285: unattended-upgrades unblock request

[Michael Vogt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi release team,

I would like to ask for allow unattended-upgrades 0.83.3 into
testing. Version 0.83 has a regression when it sends out the summary
mail of the completed upgrade. The full changelog:

unattended-upgrades (0.83.3) unstable; urgency=medium

  [ Alexandre Detiste ]
  * add Raspbian template

  [ Michael Vogt ]
  * Attach all dpkg log to the summary mail on minimal-upgrades-steps
  mode
(closes: #759693)

 -- Michael Vogt m...@debian.org  Wed, 10 Dec 2014 21:36:34 +0100

unattended-upgrades (0.83.2) unstable; urgency=medium

  [ Martin-Éric Racine ]
  * debian/changelog:
- updated to the DEP-5 format

  [ Alexandre Detiste ]
  * Fix spurious newlines

 -- Michael Vogt m...@debian.org  Wed, 26 Nov 2014 10:19:48 +0100

unattended-upgrades (0.83.1) unstable; urgency=medium

  * unattended-upgrade:
- fix regression and only send out the most recent dpkg log part
  when sending the summary mail (closes: #759693)
  * README.md:
- improve documentation
  * debian/control:
- update Vcs-Bzr location

 -- Michael Vogt m...@debian.org  Mon, 24 Nov 2014 11:09:41 +0100

Thanks for your consideration,
 Michael


signature.asc
Description: Digital signature

Bug#772729: RM: xdb -- ROM; Unmaintained upstream

[Michael Vogt]

Package: ftp.debian.org
Severity: normal

Please remove the xdb source package, its unmaintained and superseeded
by xbase64.

Thanks,
 Michael


signature.asc
Description: Digital signature

Bug#759693: unattended-upgrades: please document how to configure the logging options

[Michael Vogt]

On Fri, Nov 28, 2014 at 01:23:14PM +0200, Martin-Éric Racine wrote:
 2014-11-27 16:58 GMT+02:00 Martin-Éric Racine martin-eric.rac...@iki.fi:
  2014-11-27 13:50 GMT+02:00 Alexandre Detiste alexandre.deti...@gmail.com:
  Sorry, but this hardly qualifies as a log. It only shows the
  intallation of one single package and a summary. :/
[..]
 What I got with 0.83.2:
[..]
 Packages that will be upgraded: iucode-tool libksba8 liblzma5 xz-utils
 Writing dpkg log to 
 '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
 All upgrades installed
 8X
 
 This obviously doesn't constitute a complete log. Four packages slated
 for upgrade, but the log only shows the installation of the first one.

Indeed, thanks for reporitng this bug! I can reproduce this in
minimal-upgrade-steps mode and its fixed in git now. I will upload it
soon, if you want to test, you can just use the git version
https://raw.githubusercontent.com/mvo5/unattended-upgrades/debian/sid/unattended-upgrade

(its self-contained). It fixes the issue on my local box (and I added
a regression test).

 Btw, would printing the version of unattended-upgrade somewhere in the
 log be a good idea?

Yes, I think thats a good idea.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759693: unattended-upgrades: please document how to configure the logging options

[Michael Vogt]

On Mon, Nov 24, 2014 at 08:19:36PM +0200, Martin-Éric Racine wrote:
 2014-11-24 12:27 GMT+02:00 Michael Vogt m...@debian.org:
  On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote:
  2) Please note that the change to a single log file did not fix what
  the initial bug report asked, which was to document how logging
  options can be configured. ;)
 
  Yeah, this is still outstanding I think. I updated README.md to
  include a lot more options and its much better now (IMO) but
  /etc/logrotate.d/unattended-upgrades is not documented yet.
 
  The logging defaults should be better and more consistent now at
  least.
 
 They are not. Automated updates are run daily via CRON, while the
 logrotate file installed by unattended-upgrades is set for monthly
 rotates.  This is precisely why since the logging functions have been
 re-writen, we get daily e-mails that show upgrades logs starting the
 previous months, instead of since the last time unattended-upgrades
 was executed (which tends to be yesterday, since we use cron.daily).

Thanks for your reply. Am I reading this correctly that with version
0.83.1 you still get the full logs? This version (uploaded yesterday)
was supposed to fix the problem and only mail you the current output
not the entire file. Does that not work for you? 

Thanks,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#770589: unattended-upgrades: [patch] DEP-5 copyright

[Michael Vogt]

On Sat, Nov 22, 2014 at 02:02:43PM +0200, Martin-Éric Racine wrote:
 Package: unattended-upgrades
 Version: 0.83
 Severity: normal
 Tags: patch

Thanks for this bugreport and your patch.
 
 The enclosed file migrates debian/copyright to the DEP-5 format.

This is added to bzr and it will be part of the next upload
(unfortunately I overlooked it and its not part of my upload from some
minutes ago).

Thanks,
 Michael

 -- System Information:
 Debian Release: jessie/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
 Architecture: i386 (i686)
 
 Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages unattended-upgrades depends on:
 ii  apt1.0.9.3
 ii  apt-utils  1.0.9.3
 ii  debconf [debconf-2.0]  1.5.53
 ii  init-system-helpers1.22
 ii  lsb-base   4.1+Debian13+nmu1
 ii  lsb-release4.1+Debian13+nmu1
 ii  python33.4.2-1
 ii  python3-apt0.9.3.11
 ii  ucf3.0030
 ii  xz-utils   5.1.1alpha+20120614-2+b1
 
 unattended-upgrades recommends no packages.
 
 Versions of packages unattended-upgrades suggests:
 ii  bsd-mailx  8.1.2-0.20140825cvs-1
 ii  nullmailer [mail-transport-agent]  1:1.13-1
 
 -- debconf information excluded

 Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Source: http://code.launchpad.net/~ubuntu-core-dev/unattended-upgrades/ubuntu
 
 Files: *
 Copyright: © 2005-2014 Michael Vogt michael.v...@ubuntu.com,
© 2005-2009 Canonical Ltd
 License: GPL-2+
   On Debian systems, the complete text of the GNU General Public License
   can be found in /usr/share/common-licenses/GPL-2.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759693: unattended-upgrades: please document how to configure the logging options

[Michael Vogt]

On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote:
 2014-10-28 12:51 GMT+02:00 Michael Vogt m...@debian.org:
  On Wed, Oct 22, 2014 at 07:35:40AM +0200, Alexandre Detiste wrote:
  control: reopen -1
 
  Since this change, the mail I receive contains the changes from all 
  previous days.
 
  See multiple 'Log Started' in attached mail.
 
  Thanks for your bugreport.
 
  The attached patch should fix this problem. It will be part of the
  next upload to unstable.
 
 1) Could this patched version please be uploaded NOW while bugs with
 severity 'important' are still allowed?

Thanks for the reminder, I uploaded the fix now.
 
 2) Please note that the change to a single log file did not fix what
 the initial bug report asked, which was to document how logging
 options can be configured. ;)

Yeah, this is still outstanding I think. I updated README.md to
include a lot more options and its much better now (IMO) but
/etc/logrotate.d/unattended-upgrades is not documented yet.

The logging defaults should be better and more consistent now at
least.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#759693: unattended-upgrades: please document how to configure the logging options

[Michael Vogt]

On Sat, Nov 22, 2014 at 01:31:39PM +0200, Martin-Éric Racine wrote:
 2014-10-28 12:51 GMT+02:00 Michael Vogt m...@debian.org:
  On Wed, Oct 22, 2014 at 07:35:40AM +0200, Alexandre Detiste wrote:
  control: reopen -1
 
  Since this change, the mail I receive contains the changes from all 
  previous days.
 
  See multiple 'Log Started' in attached mail.
 
  Thanks for your bugreport.
 
  The attached patch should fix this problem. It will be part of the
  next upload to unstable.
 
 1) Could this patched version please be uploaded NOW while bugs with
 severity 'important' are still allowed?
 
 2) Please note that the change to a single log file did not fix what
 the initial bug report asked, which was to document how logging
 options can be configured. ;)

I did a little bit of documentation in
https://alioth.debian.org/scm/loggerhead/apt/unattended-upgrades/debian-sid/revision/307?start_revid=307
 now.

Feedback/improvements welcome.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767253: Please provide hashes for uncompressed Translation-*

[Michael Vogt]

On Wed, Oct 29, 2014 at 07:25:09PM +, Steve McIntyre wrote:
 On Wed, Oct 29, 2014 at 07:53:32PM +0100, Michael Vogt wrote:
 On Wed, Oct 29, 2014 at 04:28:42PM +, Steve McIntyre wrote:
  Hi Michael!
[..]
 Having the uncompressed files on the cdrom should not be needed, apt
 should simply fetch the compressed ones if the uncompressed ones are
 missing. It does need the hash of the uncompressed one in the Release
 so that it can verify that it matches after the uncompression.
 
 OK, cool. I'll admit to being curious - why does it want both
 compressed and uncompressed? Is there a worry about corruption, maybe?
[..]

Its a bit of a idiosyncrasy of apt. It used to only check the hash
after uncompression. Nowdays it checks it at all stages. But indeed, a
nice benefit of this is that it also protects against corruption
during the uncompression.

Cheers,
 Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#767339: dh-python: [patch] Please add Multi-Arch: foreign

[Michael Vogt]

Package: dh-python
Version: 1.20141026-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch



*** /tmp/tmpoAZ0Kv/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/control:
- add Multi-Arch: foreign to dh-python


Thanks for considering the patch.

Cheers,
 Michael

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

Kernel: Linux 3.16.0-24-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru dh-python-1.20141026/debian/changelog dh-python-1.20141026/debian/changelog
diff -Nru dh-python-1.20141026/debian/control dh-python-1.20141026/debian/control
--- dh-python-1.20141026/debian/control	2014-10-26 23:41:17.0 +0100
+++ dh-python-1.20141026/debian/control	2014-10-30 11:12:37.0 +0100
@@ -14,6 +14,7 @@
 
 Package: dh-python
 Architecture: all
+Multi-Arch: foreign
 Depends: ${misc:Depends}, ${python3:Depends}
 Breaks:
 # due to /usr/bin/dh_python3 and debhelper files