Bug#868503: exim4-config: update-exim4.conf brokenness
Package: exim4-config
Version: 4.89-3
Severity: normal
Dear maintainer,
Brokenness in the debconf part of the package has resulted in all local
email (sent from system daemons to users in the same host) to become
undeliverable and therefore frozen.
Background:
Exim4 was automatically installed on the affected system, probably due
to package recommendations. It had been working "without apparent
problems" (local email was being successfully delivered) since the
operating system installation (about a month ago).
As best as I recall, I was never presented with any debconf prompt of
any kind for this package, not during the system installation, nor at
any later time (including package upgrades, of which I think 2 took
place).
This week I noticed that no new email was being received. After
investigating I discovered that since at least 2 weeks ago all email
was being frozen.
The reason for this was that Exim was using "(none" (sic) as value for
"qualify_domain" (from macro ETC_MAILNAME), while variable
"local_domains" had been set to "@:localhost:(none)" (from macro
MAIN_LOCAL_DOMAINS). Therefore incoming messages using unqualified
local usernames as source and/or destination addresses were not
recognised as local:
2017-07-10 06:26:20 1dUrQy-00032m-1m <= root@(none U=root P=local S=702
2017-07-10 06:26:20 1dUrQy-00032m-1m ** root@(none R=nonlocal: Mailing to
remote domains not supported
2017-07-10 06:26:20 1dUrQy-00032o-5d Error while reading message with no
usable sender address (R=1dUrQy-00032m-1m): at least one malformed recipient
address: root@(none - domain missing or malformed
2017-07-10 06:26:20 1dUrQy-00032m-1m Process failed (1) when writing error
message to root@(none (frozen)
Notice that "(none)" is Linux's default hostname. IIUC, systemd will
call sethostname early during boot to change it to something else (taken
either from /etc/hostname or a build-time fallback), so I don't quite
understand how the debconf scripts in exim4-config got that value from
the "hostname" command (which seems to be the only method used to learn
the hostname). I believe my /etc/hostname was always properly set up
(and even if it wasn't, the fallback in systemd should have replaced
"(none)"; see function hostname_setup in systemd), so this has me
puzzled.
Possible leads
--
IIRC, the hostname of the system at installation time was simply
"localhost". Some time ago I made two changes that may or may not have
caused the problem to surface:
1. I changed the hostname using hostnamectl to a single word, say,
"foohost" (both "transient" and "static"). I also added "foohost" to
/etc/hosts as an alias.
2. I changed the name of the administrator user ("oldusername", which
appears below in some configuration dug up by reportbug).
Brokenness
--
The patch for bug #215319 (reported 2003, closed 2006) was supposed to
result in just the first word of /etc/mailname being used for macro
ETC_MAILNAME, but what it really did is to erase "non-word" characters
after the first span of (seemingly arbitrarily chosen) "word"
characters: the regex is not anchored; also, it probably wasn't meant to
allow backslashes, but it did. This explains why "(none)" was turned
into "(none".
In 2007, the badly named filter "check_ascii_pipe" was introduced: it
didn't just "check", it also transformed; it didn't just filter
non-ASCII, it filtered anything outside an apparently arbitrary set of
characters; again it allowed probably unintended characters; missing
shell quoting, it could result in an incorrect error message; that error
message is as wrongly worded as the function name. During 2007, the
maintainer kept increasing the set of allowed characters in the
mentioned filter, not because they were expected in /etc/mailname but
because the same filter was used in a bunch of places with different
requirements; this made the filter "loose". Eventually he needed to add
square brackets: continuing to repeat the backslash mistake the regex
was broken, resulting in only filtering characters followed by "]".
(Looking at the code and Git log, it appears that the maintainer
struggled to write simple shell scripts; or RTFM.)
Conclusion
--
About update-exim4.conf: I was going to send a patch (it's trivial) but
after reading the script, I believe the best course of action here is
not a patch but a flamethrower.
About the weird configuration state observed in the affected system: I
don't understand how it happened; manually running "dpkg-reconfigure
exim4-config" was enough to clean things up, "apt purge exim4" further
cleaned things.
About the frozen messages: In case it could be useful to someone, I'll
mention that Exim seems perfectly capable of delivering messages to
"@(none)" addresses, as weird a domain as that seems. So after manually
editing the configuration and thawing the frozen messages they will be
correctly delivered.
Thanks to the maintainer for h
Bug#868502: gringotts: Email address given in About dialogue does not exist
Package: gringotts Version: 1.2.10-1+b1 Severity: normal The email address man...@users.sourceforge.net given in the about dialogue does not exist. Best regards, Torquil Sørensen -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gringotts depends on: ii libc6 2.24-11+deb9u1 ii libgdk-pixbuf2.0-0 2.36.5-2 ii libglib2.0-02.50.3-2 ii libgringotts2 1:1.2.1-15 ii libgtk2.0-0 2.24.31-2 ii libpango-1.0-0 1.40.5-1 ii libpopt01.16-10+b2 gringotts recommends no packages. Versions of packages gringotts suggests: ii xdg-utils 1.1.1-1 -- no debconf information
Bug#868378: RFS: nlohmann-json/2.1.1-1
Hi there, (not a DD, can't sponsor, but a quick comment:) On 07/15/2017 12:05 PM, Muri Nicanor wrote: > * Switched build system to cmake, library is now installed in > /usr/include/nlohmann, which is upstream default (Closes: #868112) This will likely break builds of reverse dependencies because they might not find the header anymore. Did you test all of the reverse dependencies of nlohmann-json in the archive that they'll find the header in the new location? If some of them don't, you should file bugs against those packages (ideally with patches) that the maintainers know about this change. [1] Also, if the current packages can't auto-detect the new location (i.e. they start to FTBFS with your new package), then this is technically a library transition, so you should follow the guidelines for those: https://wiki.debian.org/Teams/ReleaseTeam/Transitions Regards, Christian [1] List of reverse depends (since this is a header-only library): grep-dctrl -s Package -F Build-Depends,Build-Depends-Indep \ nlohmann-json-dev /var/lib/apt/lists/*Sources (You need sid in your sources.list and a recent apt-get update to ensure this is up to date.)
Bug#865938: #865938 python-django-bootstrap-form FTBFS with Django 1.11
Hi. This issue is threatening to throw the FreedomBox packages out of testing. Is the proposed patch ok, or do you need another approach to fix it? -- Happy hacking Petter Reinholdtsen
Bug#868501: tinyca2: fails to parse subject DN when whitespace surrounds '=' token
Package: tinyca
Version: 0.7.5-6
Severity: important
File: /usr/bin/tinyca2
Tags: patch
Dear Maintainer,
I discovered that tinyca2 fails to properly parse the subject DN of
certificate requests when they are formatted with extra whitespace around
the '=' token, e.g. C = US, ST = California, ...
The attached patch corrects this problem.
-- System Information:
Debian Release: 9.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages tinyca depends on:
ii libgtk2-perl2:1.2499-1
ii liblocale-gettext-perl 1.07-3+b1
ii openssl 1.1.0f-3
Versions of packages tinyca recommends:
ii zip 3.0-11+b1
tinyca suggests no packages.
-- no debconf information
--- /usr/share/tinyca/HELPERS.pm2006-07-25 13:12:00.0 -0700
+++ HELPERS.pm 2017-07-15 23:00:09.981265372 -0700
@@ -110,7 +110,7 @@
foreach(@dn) {
s/^\s+//;
s/\s+$//;
- ($k, $v) = split(/=/);
+ ($k, $v) = split(/\s*=\s*/);
next if(not defined($k));
if($k =~ /ou/i) {
$tmp->{'OU'} or $tmp->{'OU'} = [];
Bug#858870: gnome-control-center: Can't turn on hotspot
Hello. Thanl you for your workaround really fixed. Now I can turn on hotspot. But I cant connect other devices to it. My phone and other devices are seeing this hotspot but when I enter password, it simply goes to "saved" state in phone and in other laptops it take time and goes to nothing. my `journalctl -u NetworkManager` is attached. Jul 16 10:48:41 debian NetworkManager[487]: [1500181421.3408] Config: added 'ssid' value 'debian' Jul 16 10:48:41 debian NetworkManager[487]: [1500181421.3408] Config: added 'mode' value '2' Jul 16 10:48:41 debian NetworkManager[487]: [1500181421.3408] Config: added 'frequency' value '2412' Jul 16 10:48:41 debian NetworkManager[487]: [1500181421.3408] Config: added 'key_mgmt' value 'WPA-PSK' Jul 16 10:48:41 debian NetworkManager[487]: [1500181421.3408] Config: added 'psk' value '' Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1692] device (wlx78542e2432cf): supplicant interface state: inactive -> completed Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1692] device (wlx78542e2432cf): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Started Wi-Fi Hotspot 'debian'. Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1693] device (wlx78542e2432cf): state change: config -> ip-config (reason 'none') [50 70 0] Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1900] Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlx78542e2432cf --protocol tcp --destination-port 53 --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1925] Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlx78542e2432cf --protocol udp --destination-port 53 --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1946] Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlx78542e2432cf --protocol tcp --destination-port 67 --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1968] Executing: /sbin/iptables --table filter --insert INPUT --in-interface wlx78542e2432cf --protocol udp --destination-port 67 --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.1989] Executing: /sbin/iptables --table filter --insert FORWARD --in-interface wlx78542e2432cf --jump REJECT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2008] Executing: /sbin/iptables --table filter --insert FORWARD --out-interface wlx78542e2432cf --jump REJECT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2026] Executing: /sbin/iptables --table filter --insert FORWARD --in-interface wlx78542e2432cf --out-interface wlx78542e2432cf --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2044] Executing: /sbin/iptables --table filter --insert FORWARD --source 10.42.0.0/255.255.255.0 --in-interface wlx78542e2432cf --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2061] Executing: /sbin/iptables --table filter --insert FORWARD --destination 10.42.0.0/255.255.255.0 --out-interface wlx78542e2432cf --match state --state ESTABLISHED,RELATED --jump ACCEPT Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2082] Executing: /sbin/iptables --table nat --insert POSTROUTING --source 10.42.0.0/255.255.255.0 ! --destination 10.42.0.0/255.255.255.0 --jump MASQUERADE Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2101] dnsmasq-manager: starting dnsmasq... Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2112] device (wlx78542e2432cf): state change: ip-config -> ip-check (reason 'none') [70 80 0] Jul 16 10:48:42 debian dnsmasq[2473]: started, version 2.76 cachesize 150 Jul 16 10:48:42 debian dnsmasq[2473]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify Jul 16 10:48:42 debian dnsmasq-dhcp[2473]: DHCP, IP range 10.42.0.10 -- 10.42.0.254, lease time 1h Jul 16 10:48:42 debian dnsmasq[2473]: cleared cache Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2257] device (wlx78542e2432cf): state change: ip-check -> secondaries (reason 'none') [80 90 0] Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2260] device (wlx78542e2432cf): state change: secondaries -> activated (reason 'none') [90 100 0] Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.2261] manager: NetworkManager state is now CONNECTED_LOCAL Jul 16 10:48:42 debian NetworkManager[487]: [1500181422.3252] device (wlx78542e2432cf): Activation: successful, device activated. Jul 16 10:48:43 debian NetworkManager[487]: [1500181423.5831] policy: ipv6-pd: no device to obtain a subnet to share on wlx78542e2432cf from
Bug#868500: atril: CVE-2017-1000083
Source: atril Version: 1.16.1-2 Severity: grave Tags: security Justification: user security hole Hi, the following vulnerability was published for atril. CVE-2017-183[0]: Evince command injection vulnerability in CBT handler If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2017-183 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-183 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#868499: osmose-emulator: No sound
Package: osmose-emulator Version: 1.0-4 Severity: important Dear Maintainer, Emulator correctly plays games, except with no sound. Relevant Log entry: cannot open audio device : plughw:0,0No such file or directory I don't use plugged in sound card, just a regular laptop hardware sound card. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages osmose-emulator depends on: ii libasound21.1.3-5 ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5gui55.7.1+dfsg-3+b1 ii libqt5opengl5 5.7.1+dfsg-3+b1 ii libqt5widgets55.7.1+dfsg-3+b1 ii libstdc++66.3.0-18 ii zlib1g1:1.2.8.dfsg-5 osmose-emulator recommends no packages. osmose-emulator suggests no packages. -- no debconf information
Bug#868498: git-related
I should also mention that I made the patch on top of commit 35c94313f5e0e7bb9 of the debian git repository for xpdf https://anonscm.debian.org/cgit/collab-maint/xpdf.git/
Bug#868498: additional details
In order to test that the patch works as intended, run /usr/bin/xpdf.real -remote SERV q1.pdf This will open up a pdf viewer with a document. Now make a serach using the remote interface using the "SERV" server name. /usr/bin/xpdf.real -remote SERV -exec 'search(needle)' This will cause the xpdf instance to search and go to the page of the first match, and highlight the word "needle" (just as it would if you were to use the Find dialog).
Bug#868431: wmaker: uses static upstream menu
On 2017-07-15 Doug Torrance wrote: > On 07/15/2017 08:03 AM, Andreas Metzler wrote: >> Debian's wmaker ships a menu-method for update-menus, but is not used, >> wmaker takes /usr/share/WindowMaker/menu. [...] >> The search does not succeed, the menu-method writes to >> /etc/GNUstep/Defaults/menu.hook. [...] >> xsession-errors says >> "/usr/lib/WindowMaker/wmaker(configureMenu(rootmenu.c:1512)): warning: >> using default menu file "/usr/share/WindowMaker/menu" as the menu >> referenced in WMRootMenu could not be found" > The Debian menu loads just fine for me provided that I have the menu package > (in wmaker's Suggests) installed. Hello, Strange, I also do have menu installed. I have doublechecked that it is not my user profile that is broken by testing with a freshly generated user with almost empty ~/. I need to symlink/copy /etc/GNUstep/Defaults/menu.hook to ~/GNUstep/Library/WindowMaker/ to get the Debian menu. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#868498: xpdf: adding search command usable through xpdf's remote feature
Package: xpdf
Version: 3.04-1ubuntu1
Severity: wishlist
Tags: patch
Hi,
I've added a new feature that can be used to execute a search in a document
through the remote interface that xpdf provides. This was useful to me and is
a feature I've always wanted to see in xpdf.
Best regards,
Stefan
-- System Information:
Debian Release: stretch/sid
APT prefers xenial-updates
APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500,
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.4.0-72-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages xpdf depends on:
ii libc6 2.23-0ubuntu7
ii libgcc1 1:6.0.1-0ubuntu1
ii libpoppler58 0.41.0-0ubuntu1.2
ii libstdc++65.4.0-6ubuntu1~16.04.4
ii libx11-6 2:1.6.3-1ubuntu2
ii libxm42.3.4-10
ii libxt61:1.1.5-0ubuntu1
Versions of packages xpdf recommends:
ii cups-bsd 2.1.3-4
ii gsfonts-x110.24
ii poppler-data 0.4.7-7
ii poppler-utils 0.41.0-0ubuntu1.1
xpdf suggests no packages.
-- no debconf information
Index: xpdf/xpdf/XPDFViewer.cc
===
--- xpdf.orig/xpdf/XPDFViewer.cc
+++ xpdf/xpdf/XPDFViewer.cc
@@ -239,6 +239,7 @@ XPDFViewerCmd XPDFViewer::cmdTab[] = {
{ "scrollToTopLeft", 0, gTrue, gFalse, &XPDFViewer::cmdScrollToTopLeft },
{ "scrollUp",1, gTrue, gFalse, &XPDFViewer::cmdScrollUp },
{ "scrollUpPrevPage",1, gTrue, gFalse, &XPDFViewer::cmdScrollUpPrevPage },
+ { "search", 1, gTrue, gFalse, &XPDFViewer::cmdSearch },
{ "setSelection",5, gTrue, gFalse, &XPDFViewer::cmdSetSelection },
{ "singlePageMode", 0, gFalse, gFalse, &XPDFViewer::cmdSinglePageMode },
{ "startPan",0, gTrue, gTrue, &XPDFViewer::cmdStartPan },
@@ -3844,3 +3845,13 @@ XmFontList XPDFViewer::createFontList(ch
return fontList;
}
+
+void XPDFViewer::cmdSearch(GString *args[], int nArgs, XEvent *event) {
+ char *searchText = args[0]->getCString();
+ core->find(searchText,
+gFalse,
+gFalse,
+gFalse,
+gFalse,
+gFalse);
+}
Index: xpdf/xpdf/XPDFViewer.h
===
--- xpdf.orig/xpdf/XPDFViewer.h
+++ xpdf/xpdf/XPDFViewer.h
@@ -158,6 +158,7 @@ private:
void cmdScrollToTopLeft(GString *args[], int nArgs, XEvent *event);
void cmdScrollUp(GString *args[], int nArgs, XEvent *event);
void cmdScrollUpPrevPage(GString *args[], int nArgs, XEvent *event);
+ void cmdSearch(GString *args[], int nArgs,XEvent *event);
void cmdSetSelection(GString *args[], int nArgs, XEvent *event);
void cmdSinglePageMode(GString *args[], int nArgs, XEvent *event);
void cmdStartPan(GString *args[], int nArgs, XEvent *event);
Bug#868497: debian-policy: Signed .dsc Files
Package: debian-policy Version: 4.0.0.4 Severity: wishlist -- Debian Policy Manual, Section 5.4, "Debian source control files - .dsc", states in the first sentence: "This file consists of a single paragraph, possibly surrounded by a PGP signature." This does not state whether someone who is creating a package to be uploaded by a sponsor can clearsign their own .dsc file, or if only the sponsor is able to do that without causing upload problems. What is permissible? Can you clarify that in a future update to this section? Thank you, Paul Hardy
Bug#868496: debian-policy: Please Clarify Need for update-fonts-dir in postinst and postrm Scripts
Package: debian-policy
Version: 4.0.0.4
Severity: minor
--
The Debian Policy Manual, Section 11.8.5, "Packages providing fonts",
states in item 12:
"Font packages must invoke update-fonts-dir on each directory into
which they install fonts. This invocation must occur in both the
postinst (for all arguments) and postrm (for all arguments except
upgrade) scripts."
Strictly speaking this is correct, but it could be taken to mean that
a font packager must have postinst and postrm scripts in their
package's debian directory. That is no longer necessary. I suggest
appending the following to the above paragraph:
"Note: if your build scripts invoke dh_installxfonts, this is handled
automatically and it is not necessary to create postinst or postrm
files in your debian directory for this purpose. See
dh_installxfonts(1)."
The man page for dh_installxfonts(1) states:
"Your package should depend on xfonts-utils so that the update-fonts-*
commands are available. (This program adds that dependency to
${misc:Depends}.)
"This program automatically generates the postinst and postrm commands
needed to register X fonts. These commands are inserted into the
maintainer scripts by dh_installdeb. See dh_installdeb(1) for an
explanation of how this works."
See also the Debian Fonts Packaging Policy page at
https://wiki.debian.org/Fonts/PackagingPolicy.
The new "dh $@" rules format invokes dh_installxfonts on a font
package at the appropriate time.
Thank you,
Paul Hardy
Bug#868495: passwordsafe: Program difficult to close
Package: passwordsafe Version: 1.00+dfsg-1 Severity: normal Dear Maintainer, (I'm using Cinnamon, for what it's worth.) Starting Password Safe, and pressing Escape or the Close Window keybind (e.g. Alt-F4) at the initial Safe Combination Entry dialog exits as expected. After entering the passphrase, pressing the Close Window key combination also exits as expected. However, if the database is locked after it was unlocked (e.g. after the timeout, or by minimizing with "Lock password database on minimize" enabled), it becomes difficult to close the application. Pressing Escape or Alt-F4 minimizes it. Ctrl-q and Ctrl-w do not work. The only way to quit is by minimizing the program by pressing Escape or Alt-F4, then right-clicking the program in the taskbar and selecting Close, which is cumbersome, obscure, and unexpected. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 4.11.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages passwordsafe depends on: ii libc62.24-12 ii libgcc1 1:7.1.0-9 ii libstdc++6 7.1.0-9 ii libuuid1 2.29.2-1 ii libwxbase3.0-0v5 3.0.2+dfsg-4 ii libwxgtk3.0-0v5 3.0.2+dfsg-4 ii libx11-6 2:1.6.4-3 ii libxerces-c3.1 3.1.4+debian-2 ii libxtst6 2:1.2.3-1 ii libykpers-1-11.17.3-1 ii passwordsafe-common 1.00+dfsg-1 Versions of packages passwordsafe recommends: ii xvkbd 3.3-1+b1 passwordsafe suggests no packages. -- debconf-show failed
Bug#855600: src:nlopt: Please provide binary package for cxx library
Hi, Sergey, على السبت 8 تـمـوز 2017 07:11، كتب Sergey B Kirpichev: > On Mon, 20 Feb 2017 22:03:19 -0800 Afif Elghraoui wrote: >> Anyway, I see the packaging is still in SVN. I'll switch it to Git and >> prepare a team upload. > Please ask first other co-maintainers! > > Personally, I'm +1 for packaging in Git. Unfortunally, Christophe > rejected this idea in the past. nlopt is maintained as part of the Debian Science time, and according to the Debian Science policy, the team has already agreed to use Git as its VCS [1]. In any case, I have zero time to continue working on this package in the forseeable future. regards Afif 1. http://debian-science.alioth.debian.org/debian-science-policy.html#idm45916847100528 -- Afif Elghraoui | عفيف الغراوي http://afif.ghraoui.name
Bug#868457: fwupd: Upload new 0.9.5 version
s/unstable/experimental/ Sent from VMware Boxer On Jul 15, 2017 14:46, "Limonciello, Mario" wrote: Matthias, Can you sponsor it to unstable in the meanwhile? I can't upload it because it has NEW binary package introduced (fwupd-tests). Sent from VMware Boxer On Jul 15, 2017 11:30, Matthias Klumpp wrote: 2017-07-15 18:15 GMT+02:00 Nelson A. de Oliveira : > Source: fwupd > Severity: wishlist > > Hi! > > While I see that version 0.9.5 was tagged almost 10 days ago > https://anonscm.debian.org/gitweb/?p=uefi/fwupd.git I can't see it > uploaded to Debian: > > $ rmadison fwupd > fwupd | 0.7.4-2 | stable | source, amd64, arm64, > armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x > fwupd | 0.8.2-2 | testing| source, amd64, arm64, > armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x > fwupd | 0.8.2-2 | unstable | source, amd64, arm64, > armel, armhf, i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x > fwupd | 0.8.2-2 | unstable-debug | source > fwupd | 0.9.2-6 | experimental | source, powerpc, s390x > fwupd | 0.9.2-6 | experimental-debug | source > fwupd | 0.9.4-1 | experimental | source, amd64, arm64, > armel, armhf, i386, mips, mips64el, mipsel, ppc64el > fwupd | 0.9.4-1 | experimental-debug | source > > > Nor it's available in NEW https://ftp-master.debian.org/new.html > > Maybe you forgot to upload it? :-) This is blocked on an appstream-glib upload, which is waiting for a gobject-introspection upload which is waiting for glib to be updated in unstable. So this might take a while. Cheers, Matthias
Bug#868494: ITP: dtksettings -- Deepin Tool Kit Settings library
Package: wnpp Severity: wishlist Owner: Boyuan Yang <073p...@gmail.com> * Package name: dtksettings Version : 0.1.7 Upstream Author : Deepin Technology Co., Ltd. * URL : https://github.com/linuxdeepin/dtksettings * License : GPL-3+ Programming Lang: C++ Description : Deepin Tool Kit Settings library DtkSettings is a powerful tool to generate config form json. This source package provides several libraries needed by various softwares developed by Deepin Linux. Deepin Linux is a derivative distribution of Debian, developed mainly by Deepin Technology Co., Ltd. I intend to co-maintain this package inside Debian Chinese Team and put packaging Git repository under collab-maint.
Bug#868493: ifupdown: no match using mac/XXX/=foo
Package: ifupdown Version: 0.8.20 Severity: normal Hi! I've tried the newest and greatest interface matching and renaming. State before: 1: lo: ... 2: eth0: ... master br0 3: wlan0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:e0:4c:11:7f:4e brd ff:ff:ff:ff:ff:ff inet 192.168.8.6/24 brd 192.168.8.255 scope global wlan0 valid_lft forever preferred_lft forever inet6 fe80::2e0:4cff:fe11:7f4e/64 scope link valid_lft forever preferred_lft forever 4: br0: ... I physically pulled out the USB WiFi card, wrote its stanza using the way mentioned in your d-d@l.d.o post: allow-hotplug mac/00:e0:4c:11:7f:4e/=wl0 iface wl0 inet static wpa-ssid mial wpa-psk address 192.168.8.6 netmask 255.255.255.0 upgraded ifupdown to 0.8.20, and plugged the WiFi card back in. It's sitting there under its old name and unconfigured as: 5: wlan0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:e0:4c:11:7f:4e brd ff:ff:ff:ff:ff:ff Am I holding it wrong? -- Package-specific info: --- /etc/network/interfaces: #source /etc/network/interfaces.d/* auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet manual auto br0 iface br0 inet6 static bridge_ports eth0 address 2001:470:64f4::6 netmask 64 gateway 2001:470:64f4::90 up ip addr add 10.0.1.6/24 dev br0 up ip route add default via 10.0.1.90 allow-hotplug usb0 iface usb0 inet static address 192.168.2.14 netmask 255.255.255.0 up iptables -A POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE # up echo 1 > /proc/sys/net/ipv4/ip_forward down iptables -D POSTROUTING -t nat -s 192.168.2.15/32 -j MASQUERADE # down echo 0 > /proc/sys/net/ipv4/ip_forward up ip addr add 2001:470:64f4:3::1/64 dev usb0 down ip addr del 2001:470:64f4:3::1/64 dev usb0 # up /etc/init.d/radvd start # down /etc/init.d/radvd stop allow-hotplug mac/00:e0:4c:11:7f:4e/=wl0 iface wl0 inet static wpa-ssid mial wpa-psk address 192.168.8.6 netmask 255.255.255.0 #allow-hotplug wlan0 #iface wlan0 inet manual # hostapd /etc/hostapd/hostapd.conf --- up and down scripts installed: /etc/network/if-down.d: total 8 -rwxr-xr-x 1 root root 332 Jan 6 2013 upstart lrwxrwxrwx 1 root root 32 Feb 20 11:55 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-post-down.d: total 12 lrwxrwxrwx 1 root root 29 Jun 26 17:48 bridge -> /lib/bridge-utils/ifupdown.sh lrwxrwxrwx 1 root root 25 Feb 20 11:55 hostapd -> ../../hostapd/ifupdown.sh lrwxrwxrwx 1 root root 32 Feb 20 11:55 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-pre-up.d: total 16 lrwxrwxrwx 1 root root 29 Jun 26 17:48 bridge -> /lib/bridge-utils/ifupdown.sh -rwxr-xr-x 1 root root 344 Sep 22 2014 ethtool lrwxrwxrwx 1 root root 25 Feb 20 11:55 hostapd -> ../../hostapd/ifupdown.sh lrwxrwxrwx 1 root root 32 Feb 20 11:55 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh /etc/network/if-up.d: total 28 -rwxr-xr-x 1 root root 1685 Sep 22 2014 ethtool -rwxr-xr-x 1 root root 4958 Oct 25 2014 mountnfs -rwxr-xr-x 1 root root 168 Nov 11 2016 openntpd -rwxr-xr-x 1 root root 972 Mar 30 12:18 openssh-server -rwxr-xr-x 1 root root 1483 Jan 6 2013 upstart lrwxrwxrwx 1 root root 32 Feb 20 11:55 wpasupplicant -> ../../wpa_supplicant/ifupdown.sh -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.12.2+ (SMP w/6 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ifupdown depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii iproute2 4.9.0-1 ii libc62.24-12 ii lsb-base 9.20161125 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.5-3 Versions of packages ifupdown suggests: pn ppp pn rdnssd -- no debconf information
Bug#868458: `systemctl status' output is ellipsised
Control: tags -1 pending On Sat, Jul 15, 2017 at 12:42 PM, Iain Lane wrote: > Package: init-system-helpers > Version: 1.47 > Severity: normal > Tags: patch > > Hi all, > > See: > > https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_ > 77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ > armhf/i/init-system-helpers/20170715_153215_783d6@/log.gz > > invoke-rc.d: initscript udev, action "restart" failed. > ● systemd-udevd.service - udev Kernel Device Manager > Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; > vendor preset: enabled) > Active: activating (start) since Sat 2017-07-15 15:32:01 UTC; 23ms ago >Docs: man:systemd-udevd.service(8) > man:udev(7) > Main PID: 1219 (systemd-udevd) > Tasks: 1 > CGroup: /system.slice/systemd-udevd.service > └─1219 /lib/systemd/systemd-udevd > > Jul 15 15:32:01 autopkgtest-lxd-hlpuup systemd[1]: > systemd-udevd.service: Fai…ed > Jul 15 15:32:01 autopkgtest-lxd-hlpuup systemd[1]: Starting udev Kernel > Devic….. > Hint: Some lines were ellipsized, use -l to show in full. > dpkg: error processing package udev (--configure): >subprocess installed post-installation script returned error exit > status 1 > Processing triggers for dbus (1.10.18-1ubuntu2) ... > Errors were encountered while processing: >udev > > It would be good to do what the hint in the output says, so we can see > what's going wrong from logs. Patch attached. > Thanks. I've applied your patch as 5836b30 . -- Saludos, Felipe Sateler
Bug#868121: libgssapi-krb5-2: obsolete conffile left behind
On Wed, 12 Jul 2017 04:53:35 -0400 Sam Hartman wrote: > I'm not actually sure I particularly want it removed from the system. Policy indicates that old conffiles should be removed on upgrade: https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3 > Obsolete configuration files without local changes should be removed > by the package during upgrade. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#868461: gnome-terminal: Gnome-terminal won't open.
On Sat, Jul 15, 2017 at 08:33:30PM +0300, Pavel wrote: > There is a issue in Stretch and GNOME in particular. If i don't open gnome- > terminal in a few minutes after start up it won't open at all unless i reboot. > This is persistent only in GNOME, i didn't encounter this bug in Xfce or MATE. > I installed mate-terminal in GNOME and it works fine. Only gnome-terminal is > affected by this bug. Can you try running gnome-terminal from within mate-terminal or some other terminal and see if there are any error messages? You might also see useful messages in syslog or by running journalctl. Also, there are some gnome-terminal debugging tips at https://wiki.gnome.org/Apps/Terminal/Debugging which may help you figure out what is causing this.
Bug#868492: firetools: missing xterm dependency?
Package: firetools Version: 0.9.44-1 Severity: normal Dear Maintainer, Firetools provides graphical interface access to the 'join' option of Firejail. In my hands, this feature depends on xterm, but xterm is currently not a dependency of Firetools. Could I maybe ask you to have a brief look at it? Thank you very much for taking care of the Firejail packages! All the best, Detlef -- System Information: Debian Release: 9.0 Versions of packages firetools depends on: ii firejail0.9.48-2 ii libc6 2.24-11+deb9u1 ii libgcc1 1:6.3.0-18 ii libqt5core5a5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libstdc++6 6.3.0-18 firetools recommends no packages. firetools suggests no packages. -- no debconf information
Bug#868447: O: sendxmpp -- commandline XMPP (jabber) utility
Guus Sliepen wrote... > If noone steps up, I will file a RM request in the current release > cycle. Ping me before you do that. Read: While I'm a somewhat active user of this program and also the underlying libnet-xmpp-perl, given my real-life constraints I should be carefull about increasing my commitment for Debian. But before we loose this package .. If anybody else wishes to take over, go ahead. Christoph signature.asc Description: Digital signature
Bug#863682: jessie-pu: package intel-microcode/3.20170511.1~deb8u1 [v2]: target jessie
On Sat, 15 Jul 2017, Adam D. Barratt wrote: > On Tue, 2017-06-20 at 14:58 -0300, Henrique de Moraes Holschuh wrote: > > Attached new debdiff and diffstat files (v2) with the following fixes: > > * target jessie > > Flagged for acceptance. Thank you! -- Henrique Holschuh
Bug#867989: stretch-pu: package intel-microcode/3.20170707.1~deb9u1
On Sat, 15 Jul 2017, Adam D. Barratt wrote: > On Thu, 2017-07-13 at 18:40 -0300, Henrique de Moraes Holschuh wrote: > > On Thu, 13 Jul 2017, Adam D. Barratt wrote: > > > Please go ahead. > > > > Uploaded, thank you very much! > > Flagged for acceptance. Thanks! -- Henrique Holschuh
Bug#819048: systemd service should be run while network is still online
fixed -1 0.93.1+nmu1 Hi Kilian, On Wed, 23 Mar 2016 10:05:54 +0100 Kilian Krause wrote: > Package: unattended-upgrades > Version: 0.83.3.2+deb8u1 > Severity: wishlist > Tags: patch > > Dear maintainer, > > since the shutdown part in systemd does not list network-online.target > in /lib/systemd/system/unattended-upgrades.service the shutdown is quite > likely to be run at a rather late stage in the shutdown process. > > Probably it's not strictly necessary to have online networking for > packages to be installed correctly, but that may as well be just a > minimal patch to ensure the service is run first, before killing stuff > like remote filesystems etc.. > > IMHO the /lib/systemd/system/unattended-upgrades.service should > therefore include something like: > [Unit] > Wants=network-online.target Thanks for the bug report. This has been fixed in last NMU. Cheers, Balint
Bug#825107: unattended-upgrades: Cannot enable/disable automatic upgrades using debconf with noninteractive frontend
Control: notfound -1 0.92
Hi Michael,
On Thu, 26 May 2016 12:56:29 +0200 Michael Weghorn
wrote:
> On 2016-05-24 04:20, James Valleroy wrote:
> > Is there a way to accommodate this, while also preserving local
> > changes during an upgrade?
>
> Thank you for your quick reply. Reading that post helped me better
> understand the problem and how everything is related with each other.
>
> On further research, I found that the man page of debconf-devel (7)
> (section "Config file handling") describes how config files should be
> handled by debconf.
> The way unattended-upgrades does it is totally according to that.
>
> This showed me that my understanding of debconf so far was not
> sufficient and my first approach of changing the value was not
> appropriate.
> I checked how FAI [1] does it and the appropriate way seems to be to
> use the "DEBCONF_DB_OVERRIDE" environment variable as described in the
> man page of debconf (7).
>
> Example:
>
> root@debian:~# cat /tmp/override.dat
> Name: unattended-upgrades/enable_auto_updates
> Template: unattended-upgrades/enable_auto_updates
> Value: false
> Owners: unattended-upgrades
>
> root@debian:~# DEBCONF_DB_OVERRIDE="File{/tmp/override.dat
> readonly:true}" DEBIAN_FRONTEND=noninteractive dpkg-reconfigure
> unattended-upgrades
> Replacing config file /etc/apt/apt.conf.d/20auto-upgrades with new
> version
> update-rc.d: warning: start and stop actions are no longer
> supported; falling back to defaults
> debconf: DbDriver "_ENV_stack": unable to save changes to:
> unattended-upgrades/enable_auto_updates
>
> Then, to also update the debconf cache:
>
> root@debian:~# debconf-copydb override_db config
> --config=Name:override_db --config=Driver:File
> --config=Filename:"/tmp/override.dat"
>
>
> Therefore, this bug should possibly closed as "invalid".
Doing so.
Cheers,
Balint
Bug#867783: gnupg mystery agent failure [and 1 more messages]
Ian Jackson writes ("gnupg mystery agent failure"):
> The following occurs during CI testing of dgit:
>
> + gpg --list-secret
> gpg: WARNING: unsafe permissions on homedir
> '/tmp/autopkgtest-virt-lxc.shared.ar7jp_mz/downtmp/autopkgtest_tmp/gnupg'
> gpg: starting migration from earlier GnuPG versions
> gpg: porting secret keys from
> '/tmp/autopkgtest-virt-lxc.shared.ar7jp_mz/downtmp/autopkgtest_tmp/gnupg/secring.gpg'
> to gpg-agent
> gpg: key A3DBCBC039B13D8A/A3DBCBC039B13D8A: error sending to agent: No such
> file or directory
> gpg: error building skey array: No such file or directory
> gpg: key 2AC1E075F5ED1B25/2AC1E075F5ED1B25: error sending to agent: No such
> file or directory
> gpg: error building skey array: No such file or directory
> gpg: key 14A868BFAC3BD039/14A868BFAC3BD039: error sending to agent: No such
> file or directory
> gpg: error building skey array: No such file or directory
> gpg: migration succeeded
> + test 2 = 0
>
> This does not seem to happen in my own tests using adt-run.
FYI in ci.debian.net this has mysteriously stopped happening.
Observe this list:
https://ci.debian.net/packages/d/dgit/unstable/amd64/
The debci log for the first recent pass, 2017-07-13 20:37:25 UTC, is
here
https://ci.debian.net/data/packages/unstable/amd64/d/dgit/20170713_201325.log
and contains useful information about "what changed".
Look for these sections:
Change in test packages for dgit since last test run
Change in the base system since last run
I searched for the error message and found these:
https://bugs.alpinelinux.org/issues/5463
https://bugzilla.redhat.com/show_bug.cgi?id=1236304
https://github.com/sobolevn/git-secret/issues/46
Nothing in the list of testbed changes looks particularly relevannt.
Note that the versions of dgit (including test suite) and gnupg (and
related packages) are unchanged.
If it's a race, it's one whose timing is altered by the dependencies,
because the dgit test suite has a lot of individual tests which either
all pass or almost all fail. That is, the data contradicts the
hypothesis that this is a random failure, independent for each gnupg
migration, whose probability was the same in the tests for 2017-07-12
09:22:51 UTC and 2017-07-13 20:37:25 UTC.
Ian.
Bug#702325: unattended-upgrades: false "apache2 upgradable but kept back"
Control: tags -1 wontfix Hi Teodor, On Tue, 05 Mar 2013 11:22:14 +0200 Teodor wrote: > Package: unattended-upgrades > Version: 0.79.3 > Severity: normal > > Hi, > > I've only seen this in the past (and today) for apache2 package: > > | Packages that are upgraded: > | apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common > | Packages with upgradable origin but kept back: > | apache2 > > U-A returns True and no problem for upgrades. But at least in the > message it says that this package was kept back: This is OK. Not all packages can be upgraded in unattended mode but the ones which could have been upgraded without error. Cheers, Balint
Bug#867856: stretch-pu: package src:muse-el/3.20+dfsg-1
Control: tags -1 - moreinfo Hi Adam, On Sat, Jul 15, 2017 at 11:05:54AM +0100, Adam D. Barratt wrote: > Control: tags -1 + moreinfo > > On Sun, 2017-07-09 at 18:37 -0400, Nicholas D Steeves wrote: > > I would like to add missing copyright information for debian/* in > > src:muse-el (builds elpa-muse and muse-el dummy package), along with > > several minor fixes; however, if you would prefer I can remove the > > minor fixes. These changes have been in experimental since 2017-06-17 > > and in testing since 2017-06-25. > > > > The changes do not affection functionality, but missing copyright for > > debian/* might affect our downstreams. About six months ago I sent an > > email to the Release Team, asking if this issue merited an unblock > > request, and I didn't know at that time that that I should have filed > > it as a bug. > > And here are the associated debdiffs: > [...] > > $ debdiff muse-el_3.20+dfsg-1_all.deb muse-el_3.20+dfsg-1+deb9u1_all.deb > > That appears to be missing a source debdiff, which is what's generally > expected. My apologies! It is my first time submitting an update request. I've attached the output of: debdiff muse-el_3.20+dfsg-1.dsc muse-el_3.20+dfsg-1+deb9u1.dsc Also, here is the commit history for this proposed update: git log --pretty=oneline --abbrev-commit debian/3.20+dfsg-1...debian/3.20+dfsg-1+deb9u1 396bcca Update changelog for 3.20+dfsg-1+deb9u1 514c1a6 Do not create redundant subdir during installation to /u/s/e-m/contrib bffe7f8 debian/copyright can now be simplified f71c9c6 Add privacy-respecting Message-Id headers to COPYING.emails 0f0239c Update changelog for new Debian version 39ea8b5 Add license for debian/* with confirmation emails from all previous contributors. ae2db52 Make dependencies closer to pkg-emacsen standards. Sincerely, Nicholas signature.asc Description: Digital signature
Bug#685355: KeyError: 'CODENAME'
Control: fixed -1 0.93.1+nmu1
On Fri, 24 Aug 2012 09:55:06 +0300 Teodor MICU wrote:
> Since I had this problem only on my workstation, I have found that the
> cause was the network being down at the time Cron jobs were executed
> -- including u-a.
>
> Yesterday, I've added a short python script to /etc/cron.hourly that
> sent a nice message every hour:
> | /etc/cron.hourly/unattended-upgrade:
> | {'DESCRIPTION': u'Debian GNU/Linux unstable (sid)', 'RELEASE':
> u'unstable', 'CODENAME': 'sid', 'OS': 'GNU/Linux', 'ID': 'Debian'}
>
> The python script is:
> | #! /usr/bin/python
> |
> | import lsb_release
> | print lsb_release.get_distro_information()
>
> Today U-A was executed with network UP and the log starts with:
> | Preconfiguring packages ...
> | {'DESCRIPTION': u'Debian GNU/Linux unstable (sid)', 'RELEASE':
> u'unstable', 'CODENAME': 'sid', 'OS': 'GNU/Linux', 'ID': 'Debian'}
>
> I don't know if there is anything to fix for this case.
This issue has been fixed by the NMU making u-u-s run before network
becomes available.
Since the default installation now starts u-u from systemd rather than
from cron the fix should solve the problem for almost all users.
Cheers,
Balint
Bug#868478: More backtrace
As promised, here comes the next backtrace. Hope this helps.
#0 MOZ_CrashOOL (aLine=3424, aReason=0x5556ca10 "(run->regs_mask[elm] &
(1U << bit)) == 0")
at /build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/mfbt/Assertions.cpp:33
No locals.
#1 0x55567c1d in arena_dalloc_small (mapelm=,
ptr=, chunk=, arena=)
at
/build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/memory/mozjemalloc/jemalloc.c:4660
run_pageind =
run_mapelm =
run =
bin =
size =
#2 arena_dalloc (ptr=, offset=)
at
/build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/memory/mozjemalloc/jemalloc.c:4728
chunk =
arena = 0x76c00040
pageind =
mapelm =
#3 0x7fffebb16423 in js_free (p=)
at
/build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/build-browser/dist/include/js/Utility.h:257
No locals.
#4 js::FreeOp::free_ (this=0x7fffde7f9ce0, p=) at
/build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/js/src/vm/Runtime.h:1371
No locals.
#5 JSObject::finalize (fop=0x7fffde7f9ce0, this=)
at /build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/js/src/jsobjinlines.h:93
nobj = 0x7fff2051e040
#6 js::gc::Arena::finalize (this=this@entry=0x7fff2051e000,
fop=fop@entry=0x7fffde7f9ce0,
thingKind=thingKind@entry=js::gc::AllocKind::OBJECT8_BACKGROUND,
thingSize=thingSize@entry=96)
at /build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/js/src/jsgc.cpp:457
i = { = {firstThingOffset = 64, thingSize =
64, arenaAddr = 0x7fff2051e000, span = {first = 39538,
last = 6}, thing = 64, traceKind = JS::TraceKind::Object,
needsBarrier = false,
initialized = {}}, }
firstThingOrSuccessorOfLastMarkedThing = 64
lastThing = 4000
newListHead = {first = 64, last = 1792}
newListTail = 0x7fffde7f8adc
nmarked = 0
lastMarkedThing =
#7 0x7fffebb16d53 in FinalizeTypedArenas (fop=0x7fffde7f9ce0,
src=0x7fffde7f8bf8, dest=...,
thingKind=thingKind@entry=js::gc::AllocKind::OBJECT8_BACKGROUND,
budget=..., keepArenas=js::gc::ArenaLists::KEEP_ARENAS)
at /build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/js/src/jsgc.cpp:515
arena =
nmarked =
nfree =
maybeLock = {mIsSome = false, mStorage = {u = {
mBytes = "\000VVUUU\000\000\b\017\220\241\377\177\000\000
\001\300\366\377\177\000", mDummy = 93824992302592}}}
#8 0x7fffebb187e4 in FinalizeArenas
(keepArenas=js::gc::ArenaLists::KEEP_ARENAS, budget=..., thingKind=, dest=...,
src=0x7fffde7f8bf8, fop=0x7fff526d4000) at
/build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/js/src/jsgc.cpp:549
No locals.
#9 js::gc::ArenaLists::backgroundFinalize (fop=fop@entry=0x7fffde7f9ce0,
listHead=, empty=empty@entry=0x7fffde7f9c98)
at /build/firefox-esr-KT8g23/firefox-esr-52.2.0esr/js/src/jsgc.cpp:2801
zone = 0x7fff526d4000
finalizedSorted = {static MinThingSize = 16, static MaxThingsPerArena =
253, thingsPerArena_ = 42, segments = {{
head = 0x7fff9eb9c000, tailp = 0x7fff14376010}, {head =
0x7fff538ec000, tailp = 0x7fff2c618010}, {head = 0x7fff6ceb6000,
tailp = 0x7fff14bec010}, {head = 0x7fff7c819000, tailp =
0x7fff5506a010}, {head = 0x7fff7ff6e000, tailp = 0x7fff14251010}, {
head = 0x7fff23372000, tailp = 0x7fff3f5b3010}, {head =
0x7fff5381, tailp = 0x7ffee3f8b010}, {head = 0x7fff2a874000,
tailp = 0x7fff143ae010}, {head = 0x7fff5376e000, tailp =
0x7fff77020010}, {head = 0x7fff1826c000, tailp = 0x7fff14c46010}, {
head = 0x7fff53813000, tailp = 0x7fff7c97d010}, {head =
0x7fff182ce000, tailp = 0x7ffee24bf010}, {head = 0x7fff34f3,
tailp = 0x7fff3f594010}, {head = 0x7fff1a3c8000, tailp =
0x7fff204cc010}, {head = 0x7fff1a351000, tailp = 0x7fff54730010}, {
head = 0x7fff18233000, tailp = 0x7fff3acd5010}, {head =
0x7fff182c9000, tailp = 0x7fff6d831010}, {head = 0x7fff14863000,
tailp = 0x7ffef0e2f010}, {head = 0x7fff182cd000, tailp =
0x7fff14b4a010}, {head = 0x7fff1a3e9000, tailp = 0x7ffee21e6010}, {
head = 0x7fff182c5000, tailp = 0x7fff1b091010}, {head =
0x7fff16de3000, tailp = 0x7fff2be40010}, {head = 0x7fff1f3eb000,
tailp = 0x7fff2396b010}, {head = 0x7fff182d4000, tailp =
0x7fff16b29010}, {head = 0x7fff18264000, tailp = 0x7fff1436a010}, {
head = 0x7fff2bfa2000, tailp = 0x7fff22e44010}, {head =
0x7fff1e768000, tailp = 0x7fffb2fa2010}, {head = 0x7fff182a3000,
tailp = 0x7fff22d45010}, {head = 0x7fff1a3f7000, tailp =
0x7fff14a9e010}, {head = 0x7fff14adb000, tailp = 0x7fff14aad010}, {
head = 0x7fff1a34a000, tailp = 0x7fffc21ad010}, {head =
0x7fff1429d000, tailp = 0x7fff23996010}, {head = 0x7fff1a34b000,
tailp = 0x7fff14a86010}, {head = 0x7fff495a1000, tailp =
0x7fff23950010}, {head = 0x7fff1a3ee000, tailp = 0x7fff1b14b010}, {
head = 0x7fff1a3ad000, tailp = 0
Bug#647883: lists ${distro_codename}-updates but needs stable-updates
On Mon, 26 Sep 2016 15:38:50 -0400 anarcat wrote:
> Control: fixed 647883 0.83.3.1
>
> On Tue, Nov 08, 2011 at 12:00:26PM +0100, Michael Vogt wrote:
> > On Mon, Nov 07, 2011 at 10:53:12AM +0100, Philipp Kern wrote:
> > > The commented-out example for squeeze-updates
(${distro_codename}-updates)
> > > provided by unattended-upgrades does not work. You actually need
to specify
> > > stable-updates to get automatic upgrades.
> >
> > Thanks for your bugreport.
> >
> > I pushed this fix to
> > http://anonscm.debian.org/bzr/apt/unattended-upgrades/debian-squeeze/
> > and it will need a proposed-updates upload.
>
> It looks like you forgot to close this bug report. I believe this was
> actually fixed in 0.83.3.1:
>
>
https://github.com/mvo5/unattended-upgrades/commit/9a2afa59502b34a5941ee6d1f72294f4494d129a
... and closing it now.
Cheers,
Balint
Bug#700178: unattended-upgrades: minor corruption caused by Content-Transfer-Encoding: quoted-printable
Hi Bernhard, On Wed, 25 Mar 2015 09:21:43 +0100 Bernhard Schmidt wrote: > Control: fixed -1 0.83.3 > > Hi, > > as far as I can tell this is fixed in (at least) the version in Jessie. > Not exactly sure when it was fixed first, the changelog is inconclusive. Thanks, then it can be closed now. Cheers, Balint
Bug#868491: eth0 missing from /run/network/ifstate
Package: chrony Version: 3.0-4 Severity: normal Dear Maintainer, After upgrading to stretch I noticed my network was not registering correctly. By this I mean that even though the network (eth0) came up and worked, it didn't have an entry in /run/network/ifstate (the ifstate file was empty). This is using ifupdown + ifplugd in a setup that worked fine on jessie and works fine now after removing chrony. It took me a while to nail down the problem, but I finally noticed this kept showing up in my log. run-parts: /etc/network/if-up.d/chrony exited with return code 1 When I put an 'exit 0' at the top of that script my networking came up fine and was added to /run/network/ifstate. So by exiting with an error that script was preventing ifup from completing the ifstate registration. I ultimately fixed this issue by removing chrony and switching to openntpd. -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages chrony depends on: ii adduser 3.115 ii init-system-helpers 1.48 ii iproute2 4.9.0-1 ii libc62.24-11+deb9u1 ii libcap2 1:2.25-1 ii libedit2 3.1-20160903-3 ii libseccomp2 2.3.1-2.1 pn libtomcrypt0 ii lsb-base 9.20161125 ii ucf 3.0036 ii util-linux 2.29.2-1 chrony recommends no packages. chrony suggests no packages.
Bug#812070: unattended-upgrades: system shuts down instead of rebooting since jessie
Control: tags -1 moreinfo Hi Michael, On Wed, 20 Jan 2016 08:35:27 +0100 "M. Braun" wrote: > Package: unattended-upgrades > Version: 0.83.3.2+deb8u1 > Severity: important > > Dear Maintainer, > > * What led up to the situation? > > I upgraded my systems from wheezy to jessie. > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I enabled the automatic reboot (Unattended-Upgrade::Automatic-Reboot "true";). > > * What was the outcome of this action? > > The system shuts down whenever a kernel update was installed. > > * What outcome did you expect instead? > > I expect the system to reboot. This worked with wheezy before. > > The sytem reboots fine when running "reboot" or "shutdown -r" on commandline. > > But it shuts down instead whenever unattended-upgrades writes into its log: > "WARNING Found /var/run/reboot-required, rebooting". This affects multiple machines > running x86_32 and x86_64, physical machines as well as virtual machines. > > The system also does not poweroff when unattended-upgrades tries to reboot. Does "shutdown -r now" reboot your system? This is what is run by u-u by default. Cheers, Balint
Bug#868360: cups-filters-core-drivers: driverless sets bizarre 600x2 resolution
On Sat 15 Jul 2017 at 19:40:04 +, brian m. carlson wrote: > On Sat, Jul 15, 2017 at 08:16:19PM +0100, Brian Potkin wrote: > > On Fri 14 Jul 2017 at 22:48:32 +, brian m. carlson wrote: > > > > > This does fix the problem. Since this printer supports PCL, I can also > > > use the hpijs-pcl5c driver in the mean time. > > > > Is this a bug in Brother's printer? It looks like it is. > > It does look like a firmware bug to report this resolution. However, > I think cups could improve upon its behavior in several ways: > > * Validate data. Nobody is going to print a two-pixel raster image, and > cups should not accept it as a valid (and in this case, the only > valid) option. cups and cupsfilters have both accepted and fixed past bugs in their implementation of driverless printing. In some cases cups has made allowances for deficiencies in a manufacturer's implementaion of IPP Everywhere. But where does it end? Assuming this is a firmware bug, doesn't the vendor (who after all is using a well defined standard) have the reponsibility, especially if the issue is drawn to their attention by an affected user? If AirPrint was involved you could well imagine they would jump to it. > * Prefer PCL, PostScript, and PDF over PWG. People specifically buy > printers that support the former languages. I've never heard of PWG > raster format as a selling point. The URF PDL is not a selling point; but Airprint is. PWG is (I think) a requirement for Google Cloud Print. People may not have heard of either raster format but it's all under the hood. Many less costly printers nowadays do not have PCL, PostScript or PDF as an accepted PDL, but they do have URF and/or PWG. It is a good avenue for avoiding proprietary drivers and plugins. > * Use the printer resolution instead of the PWG resolution when > generating raster images. At the very least, these should be > resolution options for configuration in addition to the PWG > resolution. Surely the printer resolution is what is returned by an IPP query? Either that, or it is in a supplied PPD. > * Stop suggesting driverless configurations as the recommended option if > they're obviously broken or not going to work. No bugs in PCL, PostScript or PDF interpreters? No bugs in PPDs? We would end up not "recommending" anything. :) -- Brian.
Bug#868489: e2fsprogs: division error in ext2fs_open2
Package: e2fsprogs Version: 1.43.4-2 e2fsck crashes when checking the attached filesystem: $ /sbin/e2fsck ext2fs_open2.ext4 E2fsck 1.43.4 (31-Jan-2017) Signal (8) SIGFPE si_code=FPE_INTDIV fault addr=0xf77066c5 /sbin/e2fsck(+0x2e192)[0x5664e192] Linux-gate.so.1(__kernel_rt_sigreturn+0x0)[0xf7755cb0] /lib/i386-linux-gnu/libext2fs.so.2(ext2fs_open2+0x515)[0xf77066c5] /sbin/e2fsck(+0xc62b)[0x5662c62b] /sbin/e2fsck(main+0x6d4)[0x566295a4] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf74cf276] /sbin/e2fsck(+0xc43d)[0x5662c43d] Found using american fuzzy lop: http://lcamtuf.coredump.cx/afl/ -- System Information: Architecture: i386 Versions of packages e2fsprogs depends on: ii e2fslibs1.43.4-2 ii libblkid1 2.29.2-2 ii libc6 2.24-12 ii libcomerr2 1.43.4-2 ii libss2 1.43.4-2 ii libuuid12.29.2-2 ii util-linux 2.29.2-2 -- Jakub Wilk ext2fs_open2.ext4.gz Description: application/gzip
Bug#868490: say use --max MAXCOUNT
Package: unicode Version: 2.4 Severity: minor Please make this change: -Too many characters to display, more than 10, use --max option to change it +Too many characters to display, more than 10, use --max MAXCOUNT to change it Otherwise the user will certainly do $ unicode bla $ unicode --max bla $ man unicode $ unicode --max 55 bla When he could just have done $ unicode bla $ unicode --max 55 bla
Bug#868488: RFS: sokochez/0.6.2-1 ITP
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "sokochez" * Package name: sokochez Version : 0.6.2-1 Upstream Author : Baptiste Pouget * URL : https://github.com/Sokochez/sokochez * License : GPLv3 Section : games It builds those binary packages: sokochez - two players puzzle game To access further information about this package, please visit the following URL: https://mentors.debian.net/package/sokochez Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/s/sokochez/sokochez_0.6.2-1.dsc This was the template from mentors.debian.net but I hope someone will like Sokochez so it can be made available for everyone running Debian :) ! Thank you ! Regards, Baptiste Pouget -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=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/dash Init: systemd (via /run/systemd/system)
Bug#765895: closed by Francois Marier (Bug#765895: fixed in rkhunter 1.4.2-6+deb9u1)
On Sat, 2017-07-15 at 22:21 +, Debian Bug Tracking System wrote: > * Disable remote updates to fix CVE-2017-7480 and prevent bugs like > it in the future (closes: #765895, #866677) It's good to see this finally done... but really sad to see, that it required an actually exploit to be found to get that done what I've already strongly suggested nearly THREE years agoo.O :-( smime.p7s Description: S/MIME cryptographic signature
Bug#868088: RFS: sysbench/1.0.8+ds-1 -- multi-threaded benchmark tool for database systems
control: owner -1 ! control: tag -1 +moreinfo Hello, On Tue, Jul 11, 2017 at 11:57:53PM +0200, JCF Ploemen wrote: > Changes since last upload: > * New upstream release. > * Patches: remove 02 and 05: merged upstream. > * Bump Standards-Version to 4.0.0 (from 3.9.8; no further changes). > * Control: limit build-depend on libaio-dev to linux-only. Could you explain the need for this change, please? Perhaps directly in the changelog. Also, you need to run `dch -r` -- the changelog timestamp is behind changes you've made. -- Sean Whitton signature.asc Description: PGP signature
Bug#867597: stretch-pu: package retext/6.0.2-2+deb9u1
Control: tags -1 + pending On Wed, 2017-07-12 at 17:28 +0100, Adam D. Barratt wrote: > On 2017-07-12 16:25, Dmitry Shachnev wrote: > > Hi Jonathan and the release team, > > > > On Sun, Jul 09, 2017 at 09:00:07PM +0100, Jonathan Wiltshire wrote: > >> On Fri, Jul 07, 2017 at 07:48:50PM +0300, Dmitry Shachnev wrote: > >> > I would like to request a Stretch update for ReText. > >> > > >> > The attached debdiff fixes two issues: > >> > > >> > * RC bug #863640 — segfault in XSettings code. > >> > * Syntax error in the appdata XML file. > >> > >> Please go ahead. > > > > I have a dumb question: > > > > On Jul 10th I have uploaded retext to stretch and even got an ACCEPTED > > mail: > > > > retext_6.0.2-2+deb9u1_source.changes ACCEPTED into > > proposed-updates->stable-new For reference, that mail says it was accepted into stable-new, /not/ that it was accepted in to proposed-updates. (stable-new is a policy queue that sits in front of proposed-updates.) > > However it does not appear on tracker or on buildd status page. Should > > I just > > wait, or I am doing something wrong? (Are source-only uploads to > > stretch for > > arch:all packages supported?) > > You need to wait for someone from the Release Team to process it and > accept it into proposed-updates. See > https://release.debian.org/proposed-updates/stable.html Flagged for acceptance. Regards, Adam
Bug#868361: stretch-pu: package socat/1.7.3.1-2+deb9u1
Control: tags -1 + pending On Sat, 2017-07-15 at 11:55 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Fri, 2017-07-14 at 23:08 +0200, László Böszörményi wrote: > > There's a chance that on some signals (including, but not limited to > > SIGSEGV) socat goes to an infinite loop and consume all CPU cycles. > > Upstream patched it[1] for 1.7.3.2 release, which is in Sid. Basically > > set 'diag_immediate_exit' in the signal handling function to let it > > exit. Full debdiff is attached. > > > > Thanks for considering, > > Laszlo/GCS > > [1] > > http://repo.or.cz/socat.git/commitdiff/6b596b8852d8fad2675894e3ceb18a04801eaf23?hp=d34493c18df0a4d0c4fdb5bda74a155ce13e4ccf > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#868105: stretch-pu: package rkhunter/1.4.2-6
Control: tags -1 + pending On Sat, 2017-07-15 at 11:43 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Tue, 2017-07-11 at 20:10 -0700, Francois Marier wrote: > > This is an update for a security issue that is not going to get a DSA: > > > > https://security-tracker.debian.org/tracker/CVE-2017-7480 > > For some reason this never made it to the debian-release list. > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#864973: stretch-pu: package win32-loader/0.8.3+deb9u1
Control: tags -1 + pending On Fri, 2017-07-14 at 15:15 +0200, Didier 'OdyX' Raboud wrote: > Le dimanche, 25 juin 2017, 22.53:27 h CEST Cyril Brulebois a écrit : > > Looks good to me, feel free to upload, thanks. > > > > By the way, we probably shouldn't be using “stable” in URLs, but the > > target distribution (stretch here)? > > Uploaded. Flagged for acceptance. Regards, Adam
Bug#867970: stretch-pu: package python3-plumbum/1.6.2-1
Control: tags -1 + pending On Thu, 2017-07-13 at 09:59 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On 2017-07-10 21:14, Philipp Huebner wrote: > > debdiff attached > > +python-plumbum (1.6.2-1+deb9u1) stable; urgency=medium > > "stretch", not "stable", please. > > With that change, please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#867490: stretch-pu: package perl/5.24.1-3+deb9u1
Control: tags -1 + pending On Tue, 2017-07-11 at 17:46 +0100, Dominic Hargreaves wrote: > On Mon, Jul 10, 2017 at 09:41:00PM +0100, Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Thu, 2017-07-06 at 20:52 +0100, Dominic Hargreaves wrote: > > > We would like to apply the following fixes to perl in stretch for the > > > next point release: > > > > > > * Backport various Getopt-Long fixes from upstream 2.49..2.51. > > > (Closes: #855532, #864544) > > > * Backport upstream patch fixing regexp "Malformed UTF-8 character" > > > crashes. (Closes: #864782) > > > * Apply upstream base.pm no-dot-in-inc fix (from 5.24.2-RC1) > > > (Closes: #867170) > > > > Please go ahead. > > Thanks, done. Flagged for acceptance. Regards, Adam
Bug#868486: diffoscope often fails to detect APKs
Package: diffoscope Version: 83 APKs are basically a ZIP file with a JAR signature, but not necessarily the CAFEBABE byte sequence that marks a JAR. This means that comparing APKs with diffoscope often results in a straight binary diff, which is useless. Here's one example: https://verification.f-droid.org/im.zom.messenger_1510005.binary.apk.diffoscope.html im.zom.messenger_1510005.binary.apk is available here: https://verification.f-droid.org/Zom-15.1.0-alpha-5-zomrelease-release-unsigned.apk im.zom.messenger_1510005.apk is available here: https://github.com/zom/Zom-Android/releases/download/15.1.0-alpha-5/Zom-15.1.0-alpha-5-zomrelease-release.apk You can get lots and lots of APKs from here: https://f-droid.org/packages I'd like a way to force the file type in diffoscope. We are calling it from a build process, so we already know all files are going to be APKs. Also, I tried to get this added to libfile, but upstream is not willing to accept detection routines that rely on more complicated things like presence of a file in a ZIP. They just want byte patterns, which is not enough to consistently detect APKs.
Bug#867965: stretch-pu: package pykde4/4.14.3-2+deb9u1
Control: tags -1 + pending On Sat, 2017-07-15 at 13:55 -0400, Scott Kitterman wrote: > On Saturday, July 15, 2017 11:07:46 AM Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Mon, 2017-07-10 at 14:37 -0400, Scott Kitterman wrote: > > > QtWebKit support was removed from PyQt4 as part of an attempt to > > > (originally) remove it for stretch and later reduce its use to a minimum > > > due to scads of unfixed security issues (QtWebKit for Qt4 has been > > > unmaintained upstream for quite some time). I neglected to remove > > > QtWebKit usages from PyKDE4 before release (see the bug this fixes). > > > > > > All this patch does is remove usage of the not available functionality so > > > that the bindings work at all. Regression risk is nil. The same change > > > is already in sid and buster with no issues reported. > > > > > > The package is ready to upload. I would appreciate an ack in time to get > > > this in for 9.1 (but understand that I might not get that). > > > > A changelog distribution of "stretch" would be preferred to > > "stable" (although either work, as you know). > > > > Please feel free to upload, bearing in mind that we are getting very > > close to the window close for 9.1. > > Thanks. Uploaded. Flagged for acceptance. Regards, Adam
Bug#867966: stretch-pu: package python3-colorlog/2.10.0-1
Control: tags -1 + pending On Thu, 2017-07-13 at 10:01 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On 2017-07-10 21:14, Philipp Huebner wrote: > > debdiff attached > > +python-colorlog (2.10.0-1+deb9u1) stable; urgency=medium > > Please target "stretch", rather than "stable". > > With that change, please go ahead. Flagged for acceptance. Regards, Adam
Bug#868222: stretch-pu: package partman-base/191+deb9u1
Control: tags -1 + pending On Thu, 2017-07-13 at 11:16 +0200, Cyril Brulebois wrote: > Adam D. Barratt (2017-07-13): > > Control: tags -1 + confirmed > > > > On 2017-07-13 8:56, Cyril Brulebois wrote: > > >| partman-base (191+deb9u1) stretch; urgency=medium > > >| > > >| [ Karsten Merker ] > > >| * For systems that are known to have their boot firmware on an mmcblk > > >| device, protect the firmware area on all mmcblk devices (and not > > >| only on mmcblk0) from being clobbered during guided partitioning > > >| and add missing whitespace to the corresponding log output. > > >| (Closes: #854822) > > > > Please go ahead. > > Thanks, uploaded. Flagged for acceptance. Regards, Adam
Bug#868128: stretch-pu: package python-imaplib2/2.55-1
Control: tags -1 + pending
On Sat, 2017-07-15 at 11:29 +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Thu, 2017-07-13 at 10:39 +0200, Cyril Brulebois wrote:
> > Hi,
> >
> > Ilias Tsitsimpis (2017-07-12):
> > > Due to cut'n'paste error, the python3-imaplib2 package in stretch
> > > declares no dependencies (#867437). Do you believe this is something
> > > worth fixing in stretch? Attached is the proposed diff.
> >
> > This would look good to me.
> >
> > > diff -Nru python-imaplib2-2.55/debian/changelog
> > > python-imaplib2-2.55/debian/changelog
> > > --- python-imaplib2-2.55/debian/changelog 2016-09-09 20:11:08.0
> > > +0300
> > > +++ python-imaplib2-2.55/debian/changelog 2017-07-12 11:37:15.0
> > > +0300
> > > @@ -1,3 +1,10 @@
> > > +python-imaplib2 (2.55-1+deb9u1) stable-proposed-updates; urgency=medium
> >
> > Please target “stretch” instead.
> >
> > > + * Fix typo that resulted in missing dependencies for python3-imaplib2.
> > > +Thanks to Adrian Bunk for reporting this (Closes: #867437)
> > > +
> > > + -- Ilias Tsitsimpis Wed, 12 Jul 2017 11:37:15
> > > +0300
> > > +
> > > python-imaplib2 (2.55-1) unstable; urgency=medium
> > >
> > >* New upstream release.
> > > diff -Nru python-imaplib2-2.55/debian/control
> > > python-imaplib2-2.55/debian/control
> > > --- python-imaplib2-2.55/debian/control 2016-09-09 20:11:08.0
> > > +0300
> > > +++ python-imaplib2-2.55/debian/control 2017-07-12 11:36:39.0
> > > +0300
> > > @@ -20,7 +20,7 @@
> > >
> > > Package: python3-imaplib2
> > > Architecture: all
> > > -Depends: ${python:Depends}, ${misc:Depends}
> > > +Depends: ${python3:Depends}, ${misc:Depends}
> > > Description: Threaded Python IMAP4 client (Python 3)
> > > Python IMAP4 rev1 mail protocol client class using threads for parallel
> > > operation, allowing full use of the IMAP4 concurrency features and to
> >
> > This might need to wait until 9.2 since 9.1 freeze is coming up shortly,
> > and the fixed version hasn't reached testing yet.
>
> If the upload could happen today, I'd be okay with getting it into 9.1
> on the basis that testing migration would happen before the point
> release itself.
Uploaded and flagged for acceptance.
Regards,
Adam
Bug#867231: stretch-pu: package openstack-debian-images/1.19
Control: tags -1 + pending On Fri, 2017-07-14 at 18:36 +0200, Thomas Goirand wrote: > On 07/14/2017 07:25 AM, Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Wed, 2017-07-05 at 10:41 +0200, Thomas Goirand wrote: > >> On 07/05/2017 07:42 AM, Cyril Brulebois wrote: > As usual, please provide a debdiff of the proposed source package, > built and tested on stable, so that it can be confirmed. > >>> > >>> Yeah, following the usual procedure, that has existed for years, *will* > >>> save everyone time. Please do that. > >> > >> Sorry for this, my bad. Debdiff attached for version 1.20~deb9u1 built > >> on a stretch sbuild chroot. The built package is available here: > >> > >> http://sid.gplhost.com/stretch-proposed-updates/openstack-debian-images/ > > > > Thanks. > > > > +openstack-debian-images (1.20~deb9u1) stretch-proposed-updates; > > urgency=medium > > > > Simply "stretch" is generally preferred there. > > > > Please go ahead, bearing in mind that the upload window for 9.1 closes > > over this weekend. > > > > Regards, > > > > Adam > > Thanks, uploaded. And Sledge is warned that he should build OpenStack > images with that version when he generates them for 9.1. Flagged for acceptance. Regards, Adam
Bug#867567: stretch-pu: package nagios-nrpe/3.0.1-3+deb9u1
Control: tags -1 + pending On Sat, 2017-07-08 at 19:36 +0200, Sebastiaan Couwenberg wrote: > On 07/08/2017 06:31 PM, Jonathan Wiltshire wrote: > > On Fri, Jul 07, 2017 at 03:04:12PM +0200, Bas Couwenberg wrote: > >> To fix the incompatibility between NRPE 2.x and 3.x releases when SSL > >> support is enabled, I'd like to propose the following update. > > > > Please go ahead. > > Thanks, uploaded. Flagged for acceptance. Regards, Adam
Bug#868485: spawn-fcgi: does not support IPv6
Package: spawn-fcgi Version: 1.6.4-1 Severity: normal Tags: upstream patch ipv6 Dear Maintainer, I wanted to run spawn-fcgi on an IPv6 address and port. However any IPv6 addresses were rejected. Looking at the output of: $ spawn-fcgi -v spawn-fcgi v1.6.4 - spawns FastCGI processes does not indicate any IPv6 support either, while it should according to upstream. I attached a patch for configure.ac that I believe fixes this bug. -- System Information: Debian Release: 8.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) 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) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages spawn-fcgi depends on: ii libc6 2.19-18+deb8u10 spawn-fcgi recommends no packages. spawn-fcgi suggests no packages. -- no debconf information >From dbed609d7255e2f21675c120ce28872f2c2709e2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tim=20D=C3=BCsterhus?= Date: Sun, 16 Jul 2017 00:19:51 +0200 Subject: [PATCH] Fix detection of IPv6 support in generated configure script --- configure.ac | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/configure.ac b/configure.ac index b1a7401..742843d 100644 --- a/configure.ac +++ b/configure.ac @@ -75,13 +75,13 @@ AC_ARG_ENABLE(ipv6, if test x$ipv6 = xtrue; then AC_CACHE_CHECK([for IPv6 support], ac_cv_ipv6_support, -[AC_TRY_LINK([[ +[AC_TRY_LINK([ #include #include #include -]], [[ +], [ struct sockaddr_in6 s; struct in6_addr t=in6addr_any; int i=AF_INET6; s; t.s6_addr[0] = 0; -]], [ac_cv_ipv6_support=yes], [ac_cv_ipv6_support=no])]) +], [ac_cv_ipv6_support=yes], [ac_cv_ipv6_support=no])]) if test "$ac_cv_ipv6_support" = yes; then AC_DEFINE(HAVE_IPV6,1,[Whether to enable IPv6 support]) -- 2.13.0
Bug#868228: stretch-pu: package os-prober/1.76~deb9u1
Control: tags -1 + pending On Thu, 2017-07-13 at 21:15 +0200, Cyril Brulebois wrote: > Adam D. Barratt (2017-07-13): > > Please go ahead. > > Thanks, uploaded. Flagged for acceptance. Regards, Adam
Bug#867248: stretch-pu: package libclamunrar/0.99-3+deb9u1
Control: tags -1 + pending On Sat, 2017-07-15 at 14:15 -0400, Scott Kitterman wrote: > On Sat, 15 Jul 2017 10:58:19 +0100 "Adam D. Barratt" barratt.org.uk> wrote: > > Control: tags -1 + confirmed > > > > On Wed, 2017-07-05 at 08:41 +0200, Sebastian Andrzej Siewior wrote: > > > This is an update to Stretch with a patch from git which fixes > > > CVE-2012-6706. The final clamav release is planned for the end of July, > > > this is the only commit in the libclamunrar part so far. > > > > Please use a changelog distribution of "stretch" and feel free to > > upload, bearing in mind that the window for 9.1 closes this weekend. > > Thanks. I've loaded it for Sebastian with that change as he's currently > offline for a bit. Flagged for acceptance. Regards, Adam
Bug#867989: stretch-pu: package intel-microcode/3.20170707.1~deb9u1
Control: tags -1 + pending On Thu, 2017-07-13 at 18:40 -0300, Henrique de Moraes Holschuh wrote: > On Thu, 13 Jul 2017, Adam D. Barratt wrote: > > Please go ahead. > > Uploaded, thank you very much! Flagged for acceptance. Regards, Adam
Bug#868214: stretch-pu: package grub-installer/1.140+deb9u1
Control: tags -1 + pending On Thu, 2017-07-13 at 09:48 +0200, Cyril Brulebois wrote: > Control: tag -1 confirmed > > Adam D. Barratt (2017-07-13): > > Control: tags -1 + confimred > > > > On 2017-07-13 8:03, Cyril Brulebois wrote: > > >| grub-installer (1.140+deb9u1) stretch; urgency=medium > > >| > > >| * Apply another patch by Hideki Yamane to fix support for systems with > > >a > > >| large number of disks, since the regression fix in the previous > > >upload > > >| was incomplete (Closes: #839894). > > > > Please go ahead. > > Thanks, on its way. Flagged for acceptance. Regards, Adam
Bug#868130: stretch-pu: package geolinks/0.2.0-1+deb9u1
Control: tags -1 + pending On Thu, 2017-07-13 at 10:07 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On 2017-07-12 10:35, Bas Couwenberg wrote: > > The incorrect dependencies for the python3-geolinks binary package > > reported in #867405 also affect the package in stretch. > > > > geolinks (0.2.0-2) has fixed the issue in testing & unstable, and the > > same fix is included in this proposed update for stretch. > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#868054: stretch-pu: package dwarfutils/20161124-1+deb9u1
Control: tags -1 + pending On Sat, 2017-07-15 at 14:58 +0200, Daniel Stender wrote: > On 15.07.2017 12:25, Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Tue, 2017-07-11 at 17:01 +0200, Fabian Wolff wrote: > >> * Add patch 02-fix-CVE-2017-9052.patch to fix CVE-2017-9052 and > >> CVE-2017-9055 (Closes: #864064). > >> * Add patch 03-fix-CVE-2017-9053.patch to fix CVE-2017-9053. > >> * Add patch 04-fix-CVE-2017-9054.patch to fix CVE-2017-9054. > >> * Add patch 05-fix-CVE-2017-9998.patch to fix CVE-2017-9998 > >> (Closes: #866968). > > > > A changelog distribution of "stretch" would be preferred over "stable". > > > > Please go ahead, bearing in mind that the window for 9.1 will close > > during the weekend. > > > > Regards, > > > > Adam > > In! Flagged for acceptance. Regards, Adam
Bug#868102: stretch-pu: package devscripts/2.17.6+deb9u1
Control: tags -1 + pending
On Thu, 2017-07-13 at 21:29 -0400, James McCoy wrote:
> On Thu, Jul 13, 2017 at 10:09:46AM +0100, Adam D. Barratt wrote:
> > On 2017-07-12 3:27, James McCoy wrote:
> > > * debchange:
> > > + Target stretch-backports with --bpo. Closes: #867662
> > > + Support $codename{,-{proposed-updates,security}} as well.
> >
> > I think there's a bug (or two?) that could be closed there?
>
> Indeed. Add the bug reference to the changelog.
>
> > > * bts:
> > > + Add support for the new 'a11y' tag. Closes: #867416
> >
> > Please go ahead.
>
> Done.
Flagged for acceptance.
Regards,
Adam
Bug#867659: stretch-pu: package gnutls28/3.5.8-5+deb9u2
Control: tags -1 + pending On Sat, 2017-07-15 at 13:07 +0200, Andreas Metzler wrote: > On 2017-07-15 "Adam D. Barratt" wrote: > > Control: tags -1 + confirmed > > > On Sat, 2017-07-08 at 10:52 +0200, Andreas Metzler wrote: > >> I would like to fix #867581 in stable by pulling the patch from 3.5.13. > >> The issue is about broken AES-GCM in-place encryption and decryption on > >> aarch64. > > > Please go ahead, bearing in mind that the window for 9.1 closes this > > weekend. > > Thank you, uploaded. Flagged for acceptance. Regards, Adam
Bug#868344: stretch-pu: package gnome-settings-daemon/3.22.2-2+deb9u2
Control: tags -1 + pending On Fri, 2017-07-14 at 18:36 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Fri, 2017-07-14 at 19:00 +0200, Laurent Bigonville wrote: > > When a new user is login-in for the first time, g-s-d will add by > > default the machine keyboard layout but also the US one. > > > > The problem is that on the 1st login, for some reason the layout will be > > set on US and not on the machine one. This is bug #859268. > > > > A patch that is only adding the US layout if the system configured one > > cannot be determined has been merged upstream. > > > > This should probably be fixed in stable as well. > > Yes, please. > > (Bearing in mind that the upload window for 9.1 closes this weekend.) Uploaded and flagged for acceptance. Regards, Adam
Bug#868017: stretch-pu: package dgit/3.11~deb9
Control: tags -1 + pending On Sat, 2017-07-15 at 10:46 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Tue, 2017-07-11 at 09:33 +0100, Ian Jackson wrote: > > dgit 3.10 has a number of bugs which need to be fixed urgently. I > > considered them RC for buster and uploaded 3.11 to fix them there. > > They need to be fixed in stable too. > > > > 3.11 has only stable-targeted bugfixes. I would like to rebuild it > > for stretch-p-u as 3.11~deb9, ASAP. > > +dgit (3.11~deb9) stable; urgency=high > > That wants to be 3.11~deb9u1 and a target distribution of "stretch", > please. > > Feel free to upload, bearing in mind that the window for getting fixes > in to 9.1 closes this weekend (it's intentionally a non-specific window, > an upload today would be safer). Uploaded and flagged for acceptance. Regards, Adam
Bug#867716: stretch-pu: package debsecan/0.4.19~deb9u1
Control: tags -1 + pending On Sat, 2017-07-15 at 22:30 +0200, Salvatore Bonaccorso wrote: > Hi > > On Sat, Jul 15, 2017 at 11:23:45AM +0100, Adam D. Barratt wrote: > > Control: tags -1 + confirmed > > > > On Mon, 2017-07-10 at 20:02 +0200, Cyril Brulebois wrote: > > > Hi, > > > > > > Salvatore Bonaccorso (2017-07-08): > > > > Hi SRM, X-Debbug-CC'ed Florian Weimer > > > > > > > > The upload of debsecan to unstable fixed two bugs with respect to > > > > 0.4.18 as in stretch. One is the use of https_proxy which is needed > > > > for proxy configuration with https:// URLs. This was #749424. > > > > > > > > Then there was as well #789196, which adds support for stretch (and > > > > buster), as well to be choosen from the debconf menu. > > > > > > > > Unfortunately the 0.4.18 source tarball, contained .git and some out > > > > files in testsuite. I'm attaching only the result from: > > > > > > > > debdiff debsecan_0.4.18.dsc debsecan_0.4.19~deb9u1.dsc | filterdiff -x > > > > '*/.git/*' > > > > > > > > Alternatively if that's prefered, we can cherry pick the two commits > > > > and do a 0.4.18.1 upload, but doing a rebuild from 0.4.19 from > > > > unstable for stretch would resolve as well the .git and > > > > testsuite/*.out files. > > > > > > > > Any preference on your end? > > > > > > My first impression would be that your proposed approach (0.4.19~deb9u1) > > > is cleaner, but I'd welcome a second look from someone else. > > > > Ack, please go ahead. > > Thank you, uploaded. Flagged for acceptance. Regards, Adam
Bug#868451: stretch-pu: package debian-edu-doc/1.921~20170603+deb9u1
Control: tags -1 + pending On Sat, 2017-07-15 at 16:06 +0200, Holger Levsen wrote: > Please accept debian-edu-doc/1.921~20170603+deb9u1 into stretch, > the changes are only documentation and translations and are in sid > already as well. Flagged for acceptance. Regards, Adam
Bug#867190: stretch-pu: package apt/1.4.7
Control: tags -1 + pending On Fri, 2017-07-14 at 00:34 +0200, Julian Andres Klode wrote: > On Thu, Jul 13, 2017 at 09:00:06PM +0100, Adam D. Barratt wrote: > > Control: tags -1 -moreinfo +confirmed > > > > On Sun, 2017-07-09 at 17:08 +0200, Julian Andres Klode wrote: > > > The first one by David, the second by me, so this would end up > > > something like the following (order may be different, it's auto-generated > > > from git commits): > > > > > > apt (1.4.7) stretch; urgency=medium > > > > > > [ Robert Luberda ] > > > * fix a "critical" typo in old changelog entry (Closes: 866358) > > > > > > [ David Kalnischkies ] > > > * use port from SRV record instead of initial port > > > * travis: ignore profiling warning in progress lines > > > > > > > > > [ Julian Andres Klode ] > > > * Reset failure reason when connection was successful > > > > maybe "... ensuring errors are correctly reported" or something similar? > > > > > * debian/gbp.conf: Set debian-branch to 1.4.y > > > * http: Do not try reading content if Content-Length is 0 > > > * travis: Migrate to Docker > > > * Release 1.4.7 (LP: #1702326) > > > > Having the release item at the end looks slightly odd, imho. :-) > > > > Please feel free to upload something like the above (bearing in mind > > that the window for 9.1 closes this weekend). > > Uploaded with: > > apt (1.4.7) stretch; urgency=medium Flagged for acceptance. Regards, Adam
Bug#868223: stretch-pu: package avogadro/1.2.0-2+deb9u1
Control: tags -1 + pending On Thu, 2017-07-13 at 10:06 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On 2017-07-13 9:18, Michael Banck wrote: > > Version 1.2.0-2 (now in testing) fixes an RC bug in stretch where atoms > > are not displayed at all, rendering avogadro useless. > > > > The debdiff is attached, it replaces the old eigen3.patch with the > > upstream versions here: > > > > https://github.com/cryos/avogadro/commit/2d4be7ede177a8df7340fe3b209698d591ee8a04 > > https://github.com/cryos/avogadro/commit/43af3c117b0b3220b15c2fe2895b94bbd83d3a60 > > > > Changelog entry: > > > > |avogadro (1.2.0-2+deb9u1) stretch; urgency=medium > > As mentioned on IRC, that wants to be 1.2.0-1+deb9u1, please, so as not > to have a higher version than unstable and testing. ;-) > > With that change, please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#867479: stretch-pu: package adwaita-icon-theme/3.22.0-1
Control: tags -1 + pending On Sat, 2017-07-15 at 10:48 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Thu, 2017-07-06 at 20:18 +0200, Laurent Bigonville wrote: > > It seems that the version 3.22.0-1 of adwaita-icon-theme is shipping a > > malformed .svg icon. > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#867335: stretch-pu: package systemd/232-25
Am 15.07.2017 um 23:28 schrieb Cyril Brulebois: > Adam D. Barratt (2017-07-13): >> On Wed, 2017-07-05 at 23:25 +0200, Michael Biebl wrote: > […] >> I'm okay with the diff, but as mentioned: >> >>> The changes shouldn't affect the installer. CCed debian-boot >>> nonetheless for a KiBi ack. > > Testing looks good, fine with me. Thank you both. Just uploaded 232-25+deb9u1 a few minutes ago. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#868484: transition: bullet
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition I would like to request a transition slot for Bullet 2.86 which is already available in experimental. The affected reverse-dependencies are: kido hkl gazebo cyphesis-cpp openmw ros-geometry ros-geometry-experimental Except for hkl (#868481), a test is failing now, all packages build fine with the new version. Regards, Markus Ben file: title = "bullet"; is_affected = .depends ~ /libbulletcollision2\.83\.7|libbulletdynamics2\.83\.7|libbulletfileloader2\.83\.7|libbulletsoftbody2\.83\.7|libbulletworldimporter2\.83\.7|libbulletxmlworldimporter2\.83\.7|libconvexdecomposition2\.83\.7|libgimpactutils2\.83\.7|libhacd2\.83\.7|liblinearmath2\.83\.7/ | .depends ~ /libbullet2\.86|libbullet-extras2\.86/; is_good = .depends ~ /libbullet2\.86|libbullet-extras2\.86/; is_bad = .depends ~ /libbulletcollision2\.83\.7|libbulletdynamics2\.83\.7|libbulletfileloader2\.83\.7|libbulletsoftbody2\.83\.7|libbulletworldimporter2\.83\.7|libbulletxmlworldimporter2\.83\.7|libconvexdecomposition2\.83\.7|libgimpactutils2\.83\.7|libhacd2\.83\.7|liblinearmath2\.83\.7/;
Bug#833585: lintian: Check presence of upstream signature if signing key available
Dear Niels, > You need the $group parameter (the 5th parameter to the run sub). Bingo, that works. Will tidy a bunch of things up and push it tomorrow. Thanks again! Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#868483: cross-config: cross-config files missing for multiple architectures
Source: dpkg-cross Version: 2.6.15-1 Severity: normal User: helm...@debian.org Usertags: rebootstrap Hi! While working on fixing some issues with cross-building native versions of gcc, I noticed that dpkg-cross is missing the cross-config files for multiple architectures: * mips64el * powerpcspe * ppc64 * ppc64el * s390x * sparc * sparc64 * x32 I'm not sure whether these configuration files are actually still being used since at least for gcc they are actually creating problems when cross-building from 64 to 32 bits, but that's most likely due to a flawky configure script in gcc. I'm also not sure about hurd-i386, kfreebsd-i386 and kfreebsd-amd64 as I never cross-built for these targets. Either way, the list should be consistent or removed altogether. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#808336: unattended-upgrades: obsolete config /etc/apt/apt.conf.d/50unattended-upgrades
Control: tags -1 moreinfo unreproducible Hi Martin-Éric, On Fri, 18 Dec 2015 20:08:17 +0200 =?utf-8?q?Martin-=C3=89ric_Racine?= wrote: > Package: unattended-upgrades > Version: 0.86.5 > Severity: important > > The file /etc/apt/apt.conf.d/50unattended-upgrades is reported as old config. It needs to be deleted upon upgrade by maintainer scripts. This config file seems to be still used and removed on purge. Could you please add some more detail about the problem? Cheers, Balint
Bug#868468: stretch-pu: package libopenmpt/0.2.7386~beta20.3-3+deb9u2
On 15/07/17 20:50, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Sat, 2017-07-15 at 20:37 +0100, James Cowgill wrote: >> Some more security issues were discovered in libopenmpt so it will need >> another stretch update. One of the issues looked potentially serious so >> I had CVE-2017-11311 allocated for it. That CVE has been marked as >> no-dsa by the security team. >> >> Also, sorry this is pretty late for 9.1. > > It is, but if it's uploaded in time then it still might make it. Thankyou! Uploaded. James signature.asc Description: OpenPGP digital signature
Bug#868211: jessie-pu: package python3-plumbum/1.4.2-1
Control: tags -1 + pending On Thu, 2017-07-13 at 09:57 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On 2017-07-13 6:26, Philipp Huebner wrote: > > I would like to fix #867449 in Jessie. > > +python-plumbum (1.4.2-1+deb8u1) oldstable; urgency=medium > > That wants to target "jessie", not "oldstable", please. > > With that change, please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#868482: ITP: sokochez -- two players puzzle game
Package: wnpp Severity: wishlist Owner: Baptiste Pouget * Package name: sokochez Version : 0.6.2 Upstream Author : Baptiste Pouget * URL : https://github.com/Sokochez/sokochez * License : GPLv3+ Programming Lang: C++ Description : two players puzzle game Sokochez is a two players puzzle game inspired by Sokoban, it contains a map editor, there are three gamemodes and many different maps. This package is useful for one to distract himself and does not require any dependency as it is made in pure C++. I played this game and created it with friends so I know it quite well. By the way it can also be played by a single person even though the gameplay is meant for two players. I am planning to maintain it alone since it is a small package.
Bug#868210: jessie-pu: package python3-colorlog/2.4.0-1
Control: tags -1 + pending On Thu, 2017-07-13 at 09:58 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On 2017-07-13 6:25, Philipp Huebner wrote: > > I would like to fix #867422 in Jessie. > > debdiff attached. > > +python-colorlog (2.4.0-1+deb8u1) oldstable; urgency=medium > > "jessie", not "oldstable", please. > > With that change, please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#864745: jessie-pu: package perl/5.20.2-3+deb8u6
Control: tags -1 + pending On Tue, 2017-07-11 at 17:46 +0100, Dominic Hargreaves wrote: > On Mon, Jul 10, 2017 at 09:24:11PM +0100, Adam D. Barratt wrote: > > Control; tags -1 + confirmed > > > > On Wed, 2017-06-14 at 00:14 +0100, Dominic Hargreaves wrote: > > > In July 2016 we released a security update for perl to fix an optional > > > module loading related vulnerability: > > > > > > https://www.debian.org/security/2016/dsa-3628 > > > > > > This update included a change that has been since improved by upstream > > > for better compatibility with existing code. The original update caused > > > a few packages to FTBFS: > > > > > > #864302 > > > #864299 > > > #832862 > > > #832866 > > > #832845 > > > > > > As such we believe that it makes sense to update perl in jessie to > > > include the improved fix, which is scheduled for inclusion in upstream > > > maintenance releases soon. > > > > Please go ahead. > > > > Regards, > > > > Adam > > Thanks, done. Flagged for acceptance. Regards, Adam
Bug#868481: hkl FTBFS with Bullet 2.86.1
Source: hkl Version: 5.0.0.2173-2 Severity: important Hi, hkl fails to build from source with Bullet 2.86.1 which is currently in experimental but will be uploaded to unstable soon. Apparently hkl itself builds fine but one test is failing hkl3d-test-t 1..3 ok 1 - no identical objects status: 0 hkl3d-test-t.c:94:check_collision # status: 0 hkl3d-test-t.c:94:check_collision not ok 2 - collision [] ok 3 - no-collision # Looks like you failed 1 test of 3 FAILED 2 Failed Set Fail/Total (%) Skip Stat Failing Tests -- -- hkl3d-test-t 1/3 33%00 2 Failed 1/949 tests, 99.89% okay. Files=22, Tests=949, 4.32 seconds (4.13 usr + 0.09 sys = 4.22 CPU) Makefile:1101: recipe for target 'check-local' failed make[4]: *** [check-local] Error 1 make[4]: Leaving directory '/build/hkl-5.0.0.2173/tests' Makefile:973: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 make[3]: Leaving directory '/build/hkl-5.0.0.2173/tests' Makefile:825: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory '/build/hkl-5.0.0.2173/tests' Makefile:560: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/build/hkl-5.0.0.2173' dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2 debian/rules:9: recipe for target 'build' failed make: *** [build] Error 2
Bug#862173: jessie-pu: package offlineimap/6.3.4-1
Control: tags -1 + pending On Sat, 2017-07-15 at 11:46 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Tue, 2017-05-09 at 15:29 +0300, Ilias Tsitsimpis wrote: > > I would like to update OfflineIMAP in jessie, to fix the #859478 RC bug. > > Backporting the fix from newer versions of the software is too invasive, > > so instead I have added a WARNING message, that will prevent users from > > using the broken functionality. For more information, please see the > > related bug report. > > +offlineimap (6.3.4-1+deb8u1) stable-proposed-updates; urgency=medium > > That wants a distribution of "jessie", please (not least because right > now the proposed version wouldn't reach jessie at all). > > Please go ahead. Uploaded and flagged for acceptance. Regards, Adam
Bug#868230: jessie-pu: package os-prober/1.65+deb8u1
Control: tags -1 + pending On Thu, 2017-07-13 at 21:15 +0200, Cyril Brulebois wrote: > Adam D. Barratt (2017-07-13): > > Not as much as I feared from that comment. :-) > > It made me unhappy anyway. :) > > > Please go ahead. > > Thanks, uploaded. Flagged for acceptance. Regards, Adam
Bug#868243: jessie-pu: package partman-ext3/84+deb8u1
Control: tags -1 + pending On Thu, 2017-07-13 at 21:16 +0200, Cyril Brulebois wrote: > Adam D. Barratt (2017-07-13): > > Please go ahead. > > Thanks, uploaded. Flagged for acceptance. Regards, Adam
Bug#867328: jessie-pu: package libclamunrar/0.99-0+deb8u3
Control: tags -1 + pending On Sat, 2017-07-15 at 14:15 -0400, Scott Kitterman wrote: > On Sat, 15 Jul 2017 11:36:07 +0100 "Adam D. Barratt" barratt.org.uk> wrote: > > Control: tags -1 + confirmed > > > > On Wed, 2017-07-05 at 21:24 +0200, Sebastian Andrzej Siewior wrote: > > > This is an update to Jessie with a patch from git which fixes > > > CVE-2012-6706. The final clamav release is planned for the end of July, > > > this is the only commit in the libclamunrar part so far. > > > > Please use a changelog distribution of "jessie", rather than > > "oldstable", and feel free to upload. > > Thanks. I've loaded it for Sebastian with that change as he's currently > offline for a bit. Flagged for acceptance. Regards, Adam
Bug#868480: Please build-depend on ocamlbuild
Package: src:hhvm Version: 3.12.11+dfsg-1 Severity: important Dear maintainer, hhvm uses ocamlbuild. To ease a future transition to ocaml 4.05.0, where ocamlbuild is a separate package, please add it to Build-Depends. The dependency is fullfilled by ocaml 4.02.3-10 at the moment. Cheers, -- Stéphane -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#863562: jessie-pu: package libonig/5.9.5-3.2
Control: tags -1 + pending On Wed, 2017-06-28 at 02:25 +0200, Cyril Brulebois wrote: > Control: tag -1 confirmed > > Hi Jörg, > > Jörg Frings-Fürst (2017-05-28): > > I have the release 5.9.5-3.2+deb8u1 with fixes for the CVE's: > > > > CVE-2017-9224 > > CVE-2017-9226 > > CVE-2017-9227 > > CVE-2017-9228 > > CVE-2017-9229 > > > > ready, The debdiff is attached. > > It seems there was some kind of coordination with the security team, > since I see “no-dsa” mentioned in the security tracker, but feel free > to mention this upfront in your next pu requests. > > A few remarks: > - patch -p1 was unhappy with the debian/patches/series update. :) > - funny things, using square brackets in filenames. > > I suspect it would have been nice to have separate patches for each > bug fix, in case someone needs to dig into one or another, but oh > well, having them all lumped together isn't that bad. > > A few comments: > > diff -Nru libonig-5.9.5/debian/changelog libonig-5.9.5/debian/changelog > > --- libonig-5.9.5/debian/changelog 2014-12-28 12:11:12.0 +0100 > > +++ libonig-5.9.5/debian/changelog 2017-05-28 16:59:55.0 +0200 > > @@ -1,3 +1,15 @@ > > +libonig (5.9.5-3.2+deb8u1) stable; urgency=medium > > Please always use codenames, and target jessie instead. > > > + * New debian/patches/0500-CVE-2017-922[4-9].patch: > > +- Cherrypicked from upstream to correct: > > + + CVE-2017-9224 (Closes: #863312) > > + + CVE-2017-9226 (Closes: #863314) > > + + CVE-2017-9227 (Closes: #863315) > > + + CVE-2017-9228 (Closes: #863316) > > + + CVE-2017-9229 (Closes: #863318) > > + > > + -- Jörg Frings-Fürst Sun, 28 May 2017 > > 16:59:55 +0200 > > […] > > > --- libonig-5.9.5/debian/patches/0500-CVE-2017-922[4-9].patch > > 1970-01-01 01:00:00.0 +0100 > > +++ libonig-5.9.5/debian/patches/0500-CVE-2017-922[4-9].patch > > 2017-05-26 07:07:41.0 +0200 > > @@ -0,0 +1,121 @@ > > +Correct CVE-2017-922[4-9] > > + Fix mutilple invalid pointer dereference, out-of-bounds write memory > > + corruption and stack buffer overflow, > > +Origin: Cheerypicked from upstream > > (multiple & cherrypicked) > > With the target distribution (and maybe typos) fixed, feel free to > upload; thanks. Uploaded and flagged for acceptance. Regards, Adam
Bug#863682: jessie-pu: package intel-microcode/3.20170511.1~deb8u1 [v2]: target jessie
Control: tags -1 + pending On Tue, 2017-06-20 at 14:58 -0300, Henrique de Moraes Holschuh wrote: > Attached new debdiff and diffstat files (v2) with the following fixes: > * target jessie Flagged for acceptance. Regards, Adam
Bug#862891: jessie-pu: package flightgear/3.0.0-5+deb8u2
Control: tags -1 + pending On Mon, 2017-07-03 at 07:31 +0200, Markus Wanner wrote: > Hi Cyril, > > On 07/02/2017 11:14 PM, Cyril Brulebois wrote: > >>> What's up with the security upload? > > sorry, I misunderstood this as you asking for an upload of deb8u2. > > >>> (Also, you should be targetting “jessie” directly instead of “stable”.) > > (Just out of curiosity: is there a difference between uploading to > "jessie" versus (now) "oldstable"?) > > > When a pu request is marked with +moreinfo, you're supposed to be giving > > feedback. Uploads should only happen after you're given a green light > > (through a +confirmed). Flagged for acceptance. Regards, Adam
Bug#866643: jessie-pu: package init-select/1.20140921+deb8u1
Control: tags -1 + pending On Fri, 2017-07-14 at 18:58 +0100, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Mon, 2017-07-10 at 01:59 +0200, Andreas Beckmann wrote: > > Control: tag -1 - moreinfo > > > > On 2017-07-01 02:32, Cyril Brulebois wrote: > > > Andreas Beckmann (2017-06-30): > > >> init-select contains a grub config snippet that unconditionally runs a > > >> command, which will cause failures (in update-grub and friends) if > > >> init-select was removed but not purged. > > >> This was noticed on jessie->stretch upgrades of coreboot where > > >> init-select was installed in jessie (but gets removed during the upgrade > > >> to stretch). > > > > > I accidentally noticed a thread on debian-ctte@ about this. It would be > > > helpful to have a summary of what was agreed on there, and to make sure > > > grub people are in the loop. > > > > Discussion over there has ceased. > > To summarize it in one sentence: > > grub is encouraged to claim ownership of that conffile and take the > > neccessary measures to fix this bug on upgrades to stretch. > > > > I havent heard of any progress on the grub side ... > > but since it is also reproducible in plain jessie (the neccessary > > sequence is just not covered by the default piuparts tests), let's fix > > init-select in jessie, too. > > That seems a reasonable idea from my reading of the TC discussion. Uploaded and flagged for acceptance. Regards, Adam
Bug#868241: jessie-pu: package netcfg/1.131+deb8u2
Control: tags -1 + pending On Thu, 2017-07-13 at 21:16 +0200, Cyril Brulebois wrote: > Adam D. Barratt (2017-07-13): > > s/prevents/prevent/, fwiw. > > Oopsie, missed it before building & uploading. > > > Please go ahead. > > Done, thanks. Flagged for acceptance. Regards, Adam
Bug#866967: jessie-pu: package galternatives/0.13.5+nmu3+deb8u1
Control: tags -1 + pending On Tue, 2017-07-04 at 08:04 +0200, Cyril Brulebois wrote: > Control: tag -1 confirmed > > Hi, > > Boyuan Yang <073p...@gmail.com> (2017-07-03): > > KiBi suggested in [1] to fix the bug #325172 in Jessie as well. As a > > result, I am preparing a stable update for galternatives in Debian > > Jessie here. > > > > Source debdiff is provided here as attachment. > > That looks good to me, feel free to upload; thanks. Uploaded and flagged for acceptance. Regards, Adam
Bug#863734: unblock: gnupg2/2.1.18-8
Adam D. Barratt (2017-07-13): > Finally, unless I missed one when checking back through the thread, we > also need a d-i ack. From a few quick tests, spotted no issues in d-i. KiBi. signature.asc Description: Digital signature
Bug#867335: stretch-pu: package systemd/232-25
Adam D. Barratt (2017-07-13): > On Wed, 2017-07-05 at 23:25 +0200, Michael Biebl wrote: […] > I'm okay with the diff, but as mentioned: > > > The changes shouldn't affect the installer. CCed debian-boot > > nonetheless for a KiBi ack. Testing looks good, fine with me. KiBi. signature.asc Description: Digital signature
Bug#868450: Make usage of fstab-decode optional
Am 15.07.2017 um 23:18 schrieb Christian Seiler: > On 07/15/2017 11:10 PM, Michael Biebl wrote: >> You raise some good points. Maybe this is something you could bring up >> on the upstream mailing list? > > I assume you mean the upstream systemd mailing list? Indeed, I meant the upstream systemd mailing list. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#868479: twittering-mode: correct incorrect time formatting due to "84600" typo
Hi, > twittering-mode: correct incorrect time formatting due to "84600" typo (Adding missing patch) Regards, -- ,''`. : :' : Chris Lamb, Debian Project Leader `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/twittering-mode.el b/twittering-mode.el index 5f885d3..1297ca0 100644 --- a/twittering-mode.el +++ b/twittering-mode.el @@ -9468,7 +9468,7 @@ rendered at POS, return nil." ((< secs 2400) (format "%d minutes ago" (/ (+ secs 30) 60))) ((< secs 5400) "about 1 hour ago") -((< secs 84600) (format "about %d hours ago" +((< secs 86400) (format "about %d hours ago" (/ (+ secs 1800) 3600))) (t (format-time-string time-format encoded-created-at (properties (append additional-properties @@ -9476,7 +9476,7 @@ rendered at POS, return nil." (time-string ;; Copy a string and restore properties. (apply 'propertize time-string properties))) - (if (< secs 84600) + (if (< secs 86400) (put-text-property 0 (length time-string) 'need-to-be-updated `(twittering-make-passed-time-string
Bug#868479: twittering-mode: correct incorrect time formatting due to "84600" typo
Source: twittering-mode Version: 3.1.0-1.1 Severity: normal Tags: minor Hi, The attached patch corrects the incorrect time formatting due to a "84600" typo (should be 24 * 60 * 60 = 86400). Best wishes, -- ,''`. : :' : Chris Lamb, Debian Project Leader `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#868450: Make usage of fstab-decode optional
Hi Michael, On 07/15/2017 11:10 PM, Michael Biebl wrote: > thanks a lot for your detailed reply! > > I've CCed the pkg-systemd-maintainers m-l and Wouter, as the maintainer > of nbd. > > You raise some good points. Maybe this is something you could bring up > on the upstream mailing list? I assume you mean the upstream systemd mailing list? Ok, I'll do that in the next couple of days once I find some time to write this up better from a more generic perspective. (Because I think this could also be useful in other cases.) Regards, Christian
