Bug#915886:
Well, the PUMPIN MUD just means enum-extract.pl didn't do the right thing. config.log.gz says: configure:26532: ./scripts/enum-extract.pl zone_stat_item /lib/modules/4.18.0-3-amd64/source/include/linux/mmzone.h | egrep -qx NR_SLAB_RECLAIMABLE Can't locate Getopt/Std.pm in @INC (you may need to install the Getopt::Std module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/ share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at ./scripts/enum-extract.pl line 13. BEGIN failed--compilation aborted at ./scripts/enum-extract.pl line 13. So that is claiming it doesn't think you have Getopt/Std.pm, which should be provided by perl-modules-$(PERL_MAJOR_MINOR_VERSION) (e.g. in your case, 5.28). What do dpkg -l | egrep '^ii perl-' and ls -l /usr/share/perl/5.28*/Getopt/Std.pm have to say? (Regardless of what they have to say, there should definitely be an explicit perl dep in zfs-dkms now, since that definitely won't work without it.) - Rich
Bug#915908: matplotlib breaks python-cogent autopkgtest
Control: tags -1 help Hi Sandro, On Fri, Dec 07, 2018 at 03:59:50PM -0500, Sandro Tosi wrote: > control: reassign -1 python-cogent > control: notfound -1 matplotlib/2.2.3-2 > > this is something to fix in cogent test suite (they even got > expected/observed reverted...) Could you please be a bit more verbose why this is expected. Any suggestion for a fix? Kind regards Andreas. -- http://fam-tille.de
Bug#915937: ntpdate.8: Some minor corrections to the manual
Thanks for the patch! I've prepared an upload with it. I added these changes too: --- a/debian/man/ntpdate.8 +++ b/debian/man/ntpdate.8 @@ -23,7 +23,7 @@ ntpdate \- set the date and time via NTP sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the .I server -arguments to determine the correct time. +argument(s) to determine the correct time. It must be run as root on the local host (unless the option \fB\-q\fR is used). A number @@ -68,10 +68,10 @@ authentication function. .TP .B \-B Force the time to always be slewed using the adjtime() system -call, even if the measured offset is greater than +-128 ms. The +call, even if the measured offset is greater than \(+-128 ms. The default is to step the time using settimeofday() if the offset -is greater than +-128 ms. Note that, if the offset is much -greater than +-128 ms in this case, that it can take a long +is greater than \(+-128 ms. Note that, if the offset is much +greater than \(+-128 ms in this case, that it can take a long time (hours) to slew the clock to the correct value. During this time, the host should not be used to synchronize clients. .TP @@ -148,7 +148,7 @@ tickadj. .SH AUTHOR David L. Mills (mi...@udel.edu) .br -This man page was converted from html to roff by +This man page was converted from HTML to roff by Fabrizio Polacco .SH "SEE ALSO" \fBntpdate\-debian\fR(8) -- Richard
Bug#915946: python-escript: FTBFS with openmpi >= 3.1.3-3 (multiarch)
Source: python-escript
Version: 5.2-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
python-escript currently fails to build from source against openmpi >=
3.1.3-3, since it made a change in that version to have the symlink be
/usr/include/$ma/openmpi instead of /usr/include/openmpi [1]. This is
causing the following failure [2]:
RuntimeError: mpi.h not found under /usr/include:
File "/<>/SConstruct", line 496:
env=checkOptionalLibraries(env)
File "/<>/site_scons/dependencies.py", line 497:
mpi_inc_path,mpi_lib_path=findLibWithHeader(env, env['mpi_libs'], 'mpi.h',
env['mpi_prefix'], lang='c++')
File "/<>/site_scons/site_init.py", line 44:
raise RuntimeError('%s not found under %s'%(header,paths))
make[1]: *** [debian/rules:78: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:30: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Can you please look into making python-escript aware of the multiarch
path for openmpi?
Thanks,
Logan
[1]
https://tracker.debian.org/news/1007552/accepted-openmpi-313-3-source-amd64-all-into-unstable/
[2]
https://launchpadlibrarian.net/400657334/buildlog_ubuntu-disco-amd64.python-escript_5.2-3_BUILDING.txt.gz
-- System Information:
Debian Release: buster/sid
APT prefers cosmic-updates
APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500,
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-11-generic (SMP w/8 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)
LSM: AppArmor: enabled
Bug#915945: Feature request: determine the filesystem using "file" instead of trying one by one.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: pmount Version: 0.9.99-alpha-1 Severity: wishlist You can determine the type of filesystems by probing the superblock using "file -s". For example: ===BEGIN OUTPUT=== pthfdr:/u/h/pthfdr>file -s /dev/sd* /dev/sda: DOS/MBR boot sector, LInux i386 boot LOader /dev/sdb: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid partition table" at offset 0x17b "Error loading operating system" at offset 0x19a "Missing operating system", disk signature 0x512bd3a9; partition 1 : ID=0x7, active, start-CHS (0x0,32,33), end-CHS (0x11,80,63), startsector 1, 234441647 sectors /dev/sdb1: DOS/MBR boot sector, code offset 0x52+2, OEM-ID "NTFS", sectors/cluster 8, Media descriptor 0xf8, sectors/track 63, heads 255, hidden sectors 1, dos < 4.0 BootSector (0x80), FAT (1Y bit by descriptor); NTFS, sectors/track 63, sectors 234441646, $MFT start cluster 786432, $MFTMirror start cluster 2, bytes/RecordSegment 2^(-1*246), clusters/index block 1, serial number 0a05667ac566781c0; containsMicrosoft Windows XP/VISTA bootloader BOOTMGR /dev/sdc: Linux rev 1.0 ext4 filesystem data, UUID=afb8ef7a-29bc-42fa-8d6b-970f5d91f45a, volume name "ARCHIVE" (needs journal recovery) (extents) (large files) (huge files) /dev/sdd: empty /dev/sde: empty /dev/sdf: empty /dev/sdg: DOS/MBR boot sector, code offset 0x58+2, OEM-ID "mkfs.fat", sectors/cluster 128, reserved sectors 2, FAT 1, sectors/track 32, heads 64, sectors 62333952 (volumes > 32 MB), FAT (32 bit), sectors/FAT 3805, serial number 0x779542a7, label: "SDUT " ===END OUTPUT=== This command works with normal users, so you do not need to try to guess which FS the disk in question is using. -- "And in the naked light, I saw ten thousand people, maybe m\ ore. People talking without speaking, people hearing withou\ t listening. People writing songs that voices never shared,\ no one dared disturb the sound of silence." -BEGIN PGP SIGNATURE- Version: ProtonMail Comment: https://protonmail.com wsBcBAEBCAAQBQJcC0qyCRDYtWA5RV10HwAAqvAIAKFJueQias6Qj1iKo4p5 zw50NTiFxcvNsFvsV2DMZadCF4PfoRWqgyXbTpPC+Z0nHppRkaE7y3As4opY JwLshvKZDZuzB1kU6ms/UApfT96CTuXLo4CcjXi5Rj+Ry6Npw3Bgs+oK0fZf Z9yWUIUW4Tqd9OGTCK89trfcUeX+6icpNn6fQYo0+UzRj1v444pp5YqjfpJb 1zBb1Mvc9sK+qbmR8l7h9VoVKoR2MsCSNYCqtduVVQYRWp2izJ4TsRxaBYLz 7tIs488jGKHNyXdgfI+7ez8JRYqyJ8O0I01oy4XlRSPHWjLBM+2dPf8Gz7Qc 7fBqZ+hSVpdHep4gvpG9zmE= =2UiG -END PGP SIGNATURE- publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc Description: application/pgp-keys publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig Description: PGP signature
Bug#915944: pcc: Including non-free BSD-4-Clause licensed files
Source: pcc Version: 1.2.0~DEVEL+20180604-2 Severity: serious Dear pcc maintainer, Upstream pcc source code contains file with BSD-4-Clause-licensed file: https://sources.debian.org/src/pcc/1.2.0%7EDEVEL+20180604-2/cc/cc/cc.c/#L44 It looks like the latest release still has this issue. Please contact with upstream to fix this problem. -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#915703: FTBFS: fails to correctly detect PETSc 3.10 version
On 2018-12-07 20:57, Graham Inggs wrote: On 2018/12/06 11:30, Drew Parsons wrote: A build of deal.ii against PETSc 3.10 (currently in experimental) fails: This should be fixed in deal.ii 9.0.1-1 in NEW. Thanks Graham! Drew
Bug#912823: hollywood: diff for NMU version 1.14-1.1
Control: tags 912823 + patch
Control: tags 912823 + pending
Dear maintainer,
I've prepared an NMU for hollywood (versioned as 1.14-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru hollywood-1.14/debian/changelog hollywood-1.14/debian/changelog
--- hollywood-1.14/debian/changelog 2018-10-21 09:17:10.0 -0400
+++ hollywood-1.14/debian/changelog 2018-12-07 23:02:30.0 -0500
@@ -1,3 +1,11 @@
+hollywood (1.14-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/control: Add missing package dependency tmux.
+(Closes: #912823)
+
+ -- Boyuan Yang Fri, 07 Dec 2018 23:02:30 -0500
+
hollywood (1.14-1) unstable; urgency=medium
* Initial release (Closes: #888265)
diff -Nru hollywood-1.14/debian/control hollywood-1.14/debian/control
--- hollywood-1.14/debian/control 2018-10-21 09:17:10.0 -0400
+++ hollywood-1.14/debian/control 2018-12-07 23:02:30.0 -0500
@@ -11,6 +11,7 @@
Depends:
${misc:Depends},
byobu,
+ tmux,
Recommends:
apg,
bmon,
@@ -37,6 +38,7 @@
Depends:
${misc:Depends},
byobu,
+ tmux,
Recommends:
caca-utils,
newsbeuter,
signature.asc
Description: This is a digitally signed message part
Bug#915816: RM: uptimed -- ROM; long time bugs non-fixed, better alternatives
On Sat, 8 Dec 2018 08:12:54 +0800 gustavo panizzo wrote: > On Fri, Dec 07, 2018 at 11:06:01AM +0100, Axel Beckert wrote: > >Hi, > > >> leap second [2], > > > >Never noticed that despite having uptimed installed on more or less > >all my Debian systems for more like 15 years or so. You're breaking my > >tradition!!1!eleventy! ;-) > > > > I understand how you feel, I've used uptimed on all my systems for the > past 10 years. > > In the usecase were uptimes shines(servers) there is almost no reason to > no use tuptime [1] > > On boards, were usually run from SD, you want to minimize disk > writes, uptimed won't let you remount the filesystem as RO. > With tuptime you'll need to hack a bit to remount RW every now and > then, or run it just before shutting down, but is more manageable. > > > On laptops uptimed is buggy, tuptime is not. > > If you wanna build something on top of the uptime data, tuptime gives > you a sqlite db which is better that parse /var/spool/uptime/records [2] > > If you wanna "extend" tuptime you just need yo hack the Python script. > > I really don't see a situation where uptimed is better than tuptime. > > > >> and general bugginess that hasn't been solved in years [3] > > > >That one I noticed. But as the severity states, it's minor (but > >admittedly annoying). > > > >> Ricardo (tuptime upstream and Debian maintainer) has agreed to add a > >> note to tuptime's long description about uptimed (for people doing > >> `apt-cache search uptimed`) and a migration script [4] > > > >Actually for some reason, I thought the import of the uptimed database > >is done by default if present. I probably misread that addition to the > >package description. > > > >> I'll submit a patch to Buster release notes regarding the removal. > > > >Maybe there should be a transitional package from uptimed to tuptime > >which actually calls that migration script. (For that it needs to be > >packaged uncompressed and not under /usr/share/doc/. Will file bug > >reports for these two things later today.) > > > > No, I don't think tuptime should replace uptimed, their CLI is > different, tuptime pulls Python. > > tuptime could run the import script on postinst (I'd provide a patch if > Ricardo agrees with the idea and implementation), but it should not > Breaks/Conflicts/Replaces uptimed in case > someone wants to keep using uptimed after upgrading to Buster. [3] It seems like it's not for sure this should be removed right now. Axel: are you willing to take over as maintainer? I see there is a new upstream release. Perhaps this bug should be put on hold for now? If you agree, please add a moreinfo tag. That takes it out of the regular processing que. Scott K
Bug#915940: tree: Please update Vcs-* fields
Source: tree Version: 1.7.0-5 Severity: important Dear tree maintainer, With the decommission of Alioth platform, current Vcs-* fields of package tree is defunct. Since you enrolled in lowNMU list, I will prepare an NMU and upload onto DELAYED/0 soon. -- Thanks, Boyuan Yang
Bug#915941: tree: Please packaging new upstream version 1.8.0
Package: tree Version: 1.7.0-5 Severity: normal Dear tree maintainer, Tree upstream has released new version 1.8.0. Please consider packaging the latest version and see if we could make it into Buster release. Thanks, Boyuan Yang
Bug#915942: libext2fs2: ships empty directory /usr/share/doc/libext2fs
Package: libext2fs2 Version: 1.44.4-2 Severity: minor User: debian...@lists.debian.org Usertags: piuparts Hi, due to a typo in debian/rules, line 388, the libext2fs2 package ships the empty directory /usr/share/doc/libext2fs (missing the SOVERSION in the name). Andreas PS: and now I still need to understand why this disappears on some stretch->buster upgrade paths ...
Bug#914435: haskell-finite-field: Missing build-dependency on singletons
Hello, On Fri 23 Nov 2018 at 02:41PM +0200, Ilias Tsitsimpis wrote: > Source: haskell-finite-field > Version: 0.8.0 > Severity: serious > Justification: fails to build from source > > This package is not part of LTS. Do we want to continue maintaining it? > If so, we will have to package singletons. I've packaged it in DHG_packages.git. I don't know if it will build yet but d/copyright is done, at least. -- Sean Whitton signature.asc Description: PGP signature
Bug#913277: "FATAL_ERROR: No valid sound driver! FATAL_ERROR: Server exited!"
Package: moc Version: 1:2.6.0~svn-r2984-1 Followup-For: Bug #913277 In fact, what are we doing exactly when linking '/usr/share/alsa/alsa.conf.d/pulse.conf' file and '/etc/alsa/conf.d' directory?
Bug#915939: Updating libasound2-data overwrites alsa.conf
Package: libasound2-data Version: 1.1.7-2 Many people use Alsa only with Debian and with Hifi speakers connected to analog out of the motherboard. However the audio device 0 is hdmi audio and you need to change it in /usr/share/alsa/alsa.conf: defaults.ctl.card 2 defaults.pcm.card 2 Many other Debian packages asks confirmation from the user when updating configuration files. The libasound2-data package should do the same.
Bug#906625: ruby-globalid: FTBFS in buster/sid (failing tests)
Package: ruby-globalid Followup-For: Bug #906625 Hi, Thanks for reporting this. If you check thed ftbfs message carefully. You'd find it fails on different tests with the one reported previously, and it mentioned it's rails 5 related. I am currently working on rails 5 transition: https://salsa.debian.org/ruby-team/rails/wikis/Transition-to-Rails-5.2-for-Debian-Buster This package builds fine with rails 5.2 in experimental. Due to rails 5 is awaiting for transition and currently available in `experimental`. Maybe we should open another bug or retitle this one to match it's currently status better. Thanks, -Andrew
Bug#913277: "FATAL_ERROR: No valid sound driver! FATAL_ERROR: Server exited!"
Package: moc
Version: 1:2.6.0~svn-r2984-1
Followup-For: Bug #913277
Ok, good! Linking the two files ("ln -s /usr/share/alsa/alsa.conf.d/pulse.conf
/etc/alsa/conf.d")
'mocp' works normally now, there are no errors ("mocp -D" and no errors in
'mocp_client_log' / 'mocp_server_log').
So, what happens exactly? What is the exact problem here? Which package is
"buggy"?
Cheers,
Awtul
Bug#833401: debian-policy: virtual packages: dbus-session-bus, default-dbus-session-bus
control: tag -1 +patch Hello, On Sat 24 Nov 2018 at 03:23PM GMT, Simon McVittie wrote: > The routes that I described as "other options" were not taken. > > The current situation is that we have the two virtual packages that I > proposed in the original bug report > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833401#5 > modulo the rename of dbus-default-session-bus to default-dbus-session-bus > as mentioned in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833401#10 (trying to > continue/establish a convention that the preferred implementation of a > virtual package foo is default-foo). So: > > * dbus-session-bus: anything providing the D-Bus well-known session bus > for most or all user login sessions. If dbus-session-bus is > installed, then programs in at least graphical login sessions can > rely on seeing the $DBUS_SESSION_BUS_ADDRESS environment variable, > the $XDG_RUNTIME_DIR/bus Unix socket, or some other way to discover a > session bus that is supported by all the major D-Bus client libraries. > > * default-dbus-session-bus: Debian's preferred implementation of > dbus-session-bus, possibly architecture-specific. Thanks. Seeking seconds: diff --git a/virtual-package-names-list.yaml b/virtual-package-names-list.yaml index ab2662e..f7626ef 100644 --- a/virtual-package-names-list.yaml +++ b/virtual-package-names-list.yaml @@ -106,6 +106,10 @@ virtualPackages: description: anything that is capable of controlling an UPS - name: cron-daemon description: Any cron daemon that correctly follows policy requirements + - name: dbus-session-bus + description: provides the D-Bus well-known session bus for most or all user login sessions + - name: default-dbus-session-bus + description: Debian's preferred implementation of dbus-session-bus, possibly architecture-specific # Documentation @@ -435,3 +439,7 @@ virtualPackages: # virtual-mysql-server-core # virtual-mysql-testsuite # 08 Jan 2017 Added adventure +# +# Sean Whitton: +# xx Dec 2018 Added dbus-session-bus +# Added default-dbus-session-bus -- Sean Whitton signature.asc Description: PGP signature
Bug#915938: migrate: Enable compatability with sqlite >= 3.26
Package: migrate
Version: 0.11.0-3
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/use-legacy-alter-sqlite.patch: Cherry-picked from upstream
gerrit review (https://review.openstack.org/#/c/623564/) to ensure
compatability with sqlite >= 3.26 (LP: #1807262).
Thanks for considering the patch.
-- System Information:
Debian Release: buster/sid
APT prefers disco
APT policy: (500, 'disco'), (500, 'cosmic-security'), (500, 'bionic-security')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-11-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru migrate-0.11.0/debian/patches/series
migrate-0.11.0/debian/patches/series
--- migrate-0.11.0/debian/patches/series2018-04-27 04:29:21.0
-0400
+++ migrate-0.11.0/debian/patches/series2018-12-07 14:16:55.0
-0500
@@ -2,3 +2,4 @@
keep_empty_modules.patch
disable_issuetracker.patch
remove-tempest-lib-build-depends-from-upstream.patch
+use-legacy-alter-sqlite.patch
diff -Nru migrate-0.11.0/debian/patches/use-legacy-alter-sqlite.patch
migrate-0.11.0/debian/patches/use-legacy-alter-sqlite.patch
--- migrate-0.11.0/debian/patches/use-legacy-alter-sqlite.patch 1969-12-31
19:00:00.0 -0500
+++ migrate-0.11.0/debian/patches/use-legacy-alter-sqlite.patch 2018-12-07
14:16:14.0 -0500
@@ -0,0 +1,53 @@
+From f73dac34f00f3c783c6a824c93f86a756aa5cf64 Mon Sep 17 00:00:00 2001
+From: Corey Bryant
+Date: Fri, 7 Dec 2018 13:49:20 -0500
+Subject: [PATCH] Use legacy_alter_table ON in sqlite recreate_table
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Use "PRAGMA legacy_alter_table = ON" with sqlite >= 3.26 when
+using "ALTER TABLE RENAME TO migration_tmp" to maintain legacy
+behavior.
+
+As of sqlite version 3.26, when a table is renamed using
+"ALTER TABLE RENAME TO", REFERENCES clauses that refer to the
+table will be updated. To maintain legacy (3.24 and earlier)
+behavior, "PRAGMA legacy_alter_table" can be set to true and
+"PRAGMA foreign_keys" can be set to false. [1]
+
+[1] https://www.sqlite.org/src/info/ae9638e9c0ad0c36
+
+Thanks to "László Böszörményi (GCS)" for
+providing the code for this patch, which has since been
+slightly modified.
+
+Change-Id: I539988ab2ad6df6c8f423ecec15364ad8fcc7267
+Closes-Bug: 1807262
+---
+ migrate/changeset/databases/sqlite.py | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/migrate/changeset/databases/sqlite.py
b/migrate/changeset/databases/sqlite.py
+index 92d42f2..568a329 100644
+--- a/migrate/changeset/databases/sqlite.py
b/migrate/changeset/databases/sqlite.py
+@@ -96,8 +96,15 @@ class SQLiteHelper(SQLiteCommon):
+ if omit_constraints is None or cons.name not in omit_constraints
+ ])
+
++tup = sqlite3.sqlite_version_info
++if tup[0] > 3 or (tup[0] == 3 and tup[1] >= 26):
++self.append('PRAGMA legacy_alter_table = ON')
++self.execute()
+ self.append('ALTER TABLE %s RENAME TO migration_tmp' % table_name)
+ self.execute()
++if tup[0] > 3 or (tup[0] == 3 and tup[1] >= 26):
++self.append('PRAGMA legacy_alter_table = OFF')
++self.execute()
+
+ insertion_string = self._modify_table(table, column, delta)
+
+--
+2.19.1
+
Bug#915607: prelink breaks kwallet5d, plasmashell on amd64
Dear Maintainer, tried to reproduce this issue and attached backtrace is created by - using a minimal buster amd64 qemu VM - installing a minimal plasma desktop - logging into graphical session - via ssh: running "prelink -mR /usr/bin/plasmashell" - via ssh: running "DISPLAY=:0 /usr/bin/plasmashell --replace" The crash seems to happen on an attempt to resolve the member QQuickWindow::event through the executables .plt section. For some reason with prelink this pointer looks damaged and points not into the .plt section: With prelink: 0x77e3f978 <_ZTVN12KQuickAddons21QuickViewSharedEngineE+56>: 0x551d8b171af0 (gdb) stepi 0x551d8b171af0 in ?? () Without prelink: 0x77e3f978 <_ZTVN12KQuickAddons21QuickViewSharedEngineE+56>: 0x55571af0 (gdb) stepi 0x55571af0 in QQuickWindow::event(QEvent*)@plt () Kind regards, Bernhard (gdb) bt #0 0x551d8b171af0 in ?? () #1 0x767ea491 in QApplicationPrivate::notify_helper (this=this@entry=0x55610610, receiver=receiver@entry=0x55a95530, e=e@entry=0x7fffd3b0) at kernel/qapplication.cpp:3727 #2 0x767f1ad0 in QApplication::notify (this=0x7fffe470, receiver=0x55a95530, e=0x7fffd3b0) at kernel/qapplication.cpp:3486 #3 0x75d95039 in QCoreApplication::notifyInternal2 (receiver=0x55a95530, event=event@entry=0x7fffd3b0) at ../../include/QtCore/5.11.2/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:307 #4 0x75dc47b8 in QCoreApplication::sendEvent (event=0x7fffd3b0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #5 QObjectPrivate::setParent_helper (this=0x5596ccb0, o=0x55a95530) at kernel/qobject.cpp:2040 #6 0x75dc5394 in QObject::QObject (this=0x55aad850, parent=0x55a95530) at kernel/qobject.cpp:812 #7 0x77adfb92 in KDeclarative::QmlObject::QmlObject (this=0x55aad850, engine=0x5568d3d0, rootContext=0x5596bf50, obj=0x55aad850, parent=) at ./src/kdeclarative/qmlobject.cpp:170 #8 0x77ae20ff in KDeclarative::QmlObjectSharedEngine::QmlObjectSharedEngine (this=0x55aad850, parent=0x55a95530) at ./src/kdeclarative/qmlobjectsharedengine.cpp:58 #9 0x77e39210 in KQuickAddons::QuickViewSharedEnginePrivate::QuickViewSharedEnginePrivate (module=0x55a95530, this=0x5596bf70) at ./src/quickaddons/quickviewsharedengine.cpp:50 #10 KQuickAddons::QuickViewSharedEngine::QuickViewSharedEngine (this=0x55a95530, parent=) at ./src/quickaddons/quickviewsharedengine.cpp:147 #11 0x77f8ea26 in PlasmaQuick::ContainmentView::ContainmentView (this=0x55a95530, corona=0x55661a00, parent=) at ./src/plasmaquick/containmentview.cpp:197 #12 0x5557f0a3 in DesktopView::DesktopView (this=0x55a95530, corona=0x55661a00, targetScreen=0x5562ee90) at ./shell/desktopview.cpp:40 #13 0x55595f4a in ShellCorona::addOutput (this=this@entry=0x55661a00, screen=, screen@entry=0x5562ee90) at ./shell/shellcorona.cpp:1199 #14 0x5559dae3 in ShellCorona::load (this=this@entry=0x55661a00) at ./shell/shellcorona.cpp:697 #15 0x5559dfd9 in ShellCorona::load (this=0x55661a00) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:937 #16 0x75dbe3e0 in QtPrivate::QSlotObjectBase::call (a=0x7fffd950, r=0x55661a00, this=0x5577c6b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376 #17 QMetaObject::activate (sender=0x55664f50, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3754 #18 0x77e6c1b1 in KActivities::Consumer::serviceStatusChanged (this=, _t1=) at ./obj-x86_64-linux-gnu/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_consumer.cpp:248 #19 0x77e6d62b in KActivities::Consumer::qt_static_metacall (_o=, _c=, _id=, _a=) at ./obj-x86_64-linux-gnu/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_consumer.cpp:114 #20 0x75dbe28b in QMetaObject::activate (sender=0x55678a60, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3771 #21 0x77e6c071 in KActivities::ActivitiesCache::serviceStatusChanged (this=this@entry=0x55678a60, _t1=, _t1@entry=KActivities::Consumer::Running) at ./obj-x86_64-linux-gnu/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:407 #22 0x77e651bd in KActivities::ActivitiesCache::setAllActivities (this=this@entry=0x55678a60, _activities=...) at ./src/lib/activitiescache_p.cpp:300 #23 0x77e653ee in KActivities::ActivitiesCache::passInfoFromReply, void (KActivities::ActivitiesCache::*)(QList const&)> (f=(void (KActivities::ActivitiesCache::*)(KActivities::ActivitiesCache * const, const QList &)) 0x77e65010 const&)>, watcher=0x556711e0, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:156 #24 KActivities::ActivitiesCache::setAllActivitiesFromReply (this=,
Bug#913237: xterm: exec-formatted yields a tilde character in zsh and emacs
On Wed, Dec 05, 2018 at 02:44:43PM +0100, Vincent Lefevre wrote: > On 2018-12-05 14:12:32 +0100, Vincent Lefevre wrote: > > I suspect a bug in doSelectionFormat() in button.c that makes xterm > > think that there was a bracketed paste, whose consequence is to > > generate the "ESC [ 2 0 1 ~ .". > > > > If I remove > > > > #if OPT_READLINE > > mydata->paste_brackets = screen->paste_brackets; > > SCREEN_FLAG_unset(screen, paste_brackets); > > #endif > > > > then I no longer get the "\33[201~". There's another issue, but > > that's a start. > > Replacing > > mydata->paste_brackets = screen->paste_brackets; no - it's more complicated than that. The problem is that when xterm's handling selectToClipboard, the X libraries delay the call to SelectionReceived, and in working on #758633, I didn't notice this particular scenario. (I'm debugging a solution, will probably put out #338 when this is resolved) -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: Digital signature
Bug#915816: RM: uptimed -- ROM; long time bugs non-fixed, better alternatives
On Fri, Dec 07, 2018 at 11:06:01AM +0100, Axel Beckert wrote: Hi, leap second [2], Never noticed that despite having uptimed installed on more or less all my Debian systems for more like 15 years or so. You're breaking my tradition!!1!eleventy! ;-) I understand how you feel, I've used uptimed on all my systems for the past 10 years. In the usecase were uptimes shines(servers) there is almost no reason to no use tuptime [1] On boards, were usually run from SD, you want to minimize disk writes, uptimed won't let you remount the filesystem as RO. With tuptime you'll need to hack a bit to remount RW every now and then, or run it just before shutting down, but is more manageable. On laptops uptimed is buggy, tuptime is not. If you wanna build something on top of the uptime data, tuptime gives you a sqlite db which is better that parse /var/spool/uptime/records [2] If you wanna "extend" tuptime you just need yo hack the Python script. I really don't see a situation where uptimed is better than tuptime. and general bugginess that hasn't been solved in years [3] That one I noticed. But as the severity states, it's minor (but admittedly annoying). Ricardo (tuptime upstream and Debian maintainer) has agreed to add a note to tuptime's long description about uptimed (for people doing `apt-cache search uptimed`) and a migration script [4] Actually for some reason, I thought the import of the uptimed database is done by default if present. I probably misread that addition to the package description. I'll submit a patch to Buster release notes regarding the removal. Maybe there should be a transitional package from uptimed to tuptime which actually calls that migration script. (For that it needs to be packaged uncompressed and not under /usr/share/doc/. Will file bug reports for these two things later today.) No, I don't think tuptime should replace uptimed, their CLI is different, tuptime pulls Python. tuptime could run the import script on postinst (I'd provide a patch if Ricardo agrees with the idea and implementation), but it should not Breaks/Conflicts/Replaces uptimed in case someone wants to keep using uptimed after upgrading to Buster. [3] [1] - tuptime pulls Python as a dep, I don't remeber any server without python installed in the last years (python apps, or fail2ban, or ansible, or saltstack or monitoring scripts, and the list goes on) some people may not want to have python installed [2] - which may have duplicate data anyway [3] - uptimed is composed by a binary, a daemon and a library, it only links against glibc so an old deb should keep working for a few releases -- IRC: gfa GPG: 0X44BB1BA79F6C6333
Bug#906609: gnucash 1:3.3-1 FTBFS mips
Control: severity -1 important > Hm, unfortunately this is outside of my wheelhouse... May I suggest > contacting the MIPS porters? Again, would really love to see gnucash > released in buster... We already removed gnucash/mips from unstable [1] so this issue is not blocking gnucash from migrating to Testing. Since we don't consider this to be release-critical at this time, I'm lowering the severity so that this bug itself won't be a blocker to gnucash re-entering Testing. [1] https://bugs.debian.org/915066 Thanks, Jeremy Bicha
Bug#915937: ntpdate.8: Some minor corrections to the manual
Package: ntpsec-ntpdate Version: 1.1.2+dfsg1-4 Severity: minor Tags: patch Dear Maintainer, the patch is in the attachment. Changes: Remove space characters at the end of lines. # Use the correct macro for the font change of a single argument. 19:.IR server # Change - to \- if it shall be printed as a minus sign. 69:call, even if the measured offset is greater than +-128 ms. The 71:is greater than +-128 ms. Note that, if the offset is much 72:greater than +-128 ms in this case, that it can take a long # Remove a repeated word ! 119 --> is # Split lines longer than 80 characters into two or more lines. Appropriate break points are the end of a sentence and a subordinate clause; after punctuation marks ntpdate.8: line 27 length 106 the correct time. It must be run as root on the local host (unless the option \fB\-q\fR is used). A number # Use \(en for a dash (en-dash) between space characters, not a minus (\-) or a hyphen (-), except in the NAME section. 110:Query only - don't set the clock. # Write "man page" or "manual page", see man-pages(7), not "manpage". -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.10-2 (SMP w/2 CPU cores) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ntpsec-ntpdate depends on: ii netbase 5.5 ii python3 3.6.7-1 ii python3-ntp 1.1.2+dfsg1-4 ntpsec-ntpdate recommends no packages. ntpsec-ntpdate suggests no packages. -- Configuration Files: /etc/default/ntpsec-ntpdate changed [not included] -- no debconf information -- Bjarni I. Gislason --- ntpdate.8 2018-11-18 10:11:00.0 + +++ ntpdate.8.new 2018-12-08 00:26:51.0 + @@ -2,13 +2,13 @@ .SH NAME ntpdate \- set the date and time via NTP .SH SYNOPSIS -.B ntpdate -.RB [\| \-bBdoqsuv \|] -.RB [\| \-a -.IR key \|] -.RB [\| \-e -.IR authdelay \|] -.RB [\| \-k +.B ntpdate +.RB [\| \-bBdoqsuv \|] +.RB [\| \-a +.IR key \|] +.RB [\| \-e +.IR authdelay \|] +.RB [\| \-k .IR keyfile \|] .RB [\| \-o .IR version \|] @@ -16,15 +16,17 @@ ntpdate \- set the date and time via NTP .IR samples \|] .RB [\| \-t .IR timeout \|] -.IR server +.I server .RB [\| ... \|] .SH DESCRIPTION -.B ntpdate +.B ntpdate sets the local date and time by polling the Network Time Protocol (NTP) server(s) given as the -.I server -arguments to determine -the correct time. It must be run as root on the local host (unless the option \fB\-q\fR is used). A number +.I server +arguments to determine the correct time. +It must be run as root on the local host (unless the option \fB\-q\fR +is used). +A number of samples are obtained from each of the servers specified and a subset of the NTP clock filter and selection algorithms are applied to select the best of these. Note that the accuracy and reliability of @@ -107,7 +109,7 @@ as the integer samples, with values from default is 4. .TP .B \-q -Query only - don't set the clock. +Query only \(en don't set the clock. .TP .B \-s Divert logging output from the standard output (default) to the @@ -116,7 +118,7 @@ convenience of cron scripts. .TP .BI \-t \ timeout Specify the maximum time waiting for a server response as the -value timeout, in seconds and fraction. The value is is rounded +value timeout, in seconds and fraction. The value is rounded to a multiple of 0.2 seconds. The default is 1 second, a value suitable for polling across a LAN. .TP @@ -135,7 +137,7 @@ identification string to be logged. and could update the clock, and nonzero otherwise. .SH FILES .TP -.I /etc/ntp.keys +.I /etc/ntp.keys \- encryption keys used by ntpdate. .SH BUGS The slew adjustment is actually 50% larger than the measured offset, @@ -146,7 +148,7 @@ tickadj. .SH AUTHOR David L. Mills (mi...@udel.edu) .br -This manpage converted from html to roff by +This man page was converted from html to roff by Fabrizio Polacco .SH "SEE ALSO" \fBntpdate\-debian\fR(8)
Bug#905254: libphp-phpmailer: Please update to version 6.x
WordPress probably uses its own version which, I assume, they will maintain afterwards. I'll see if I can find more about what they're doing with it for the longer term. The easiest way for me is to just drop the depends. - Craig On Sat, 8 Dec. 2018, 02:06 Salvatore Bonaccorso Control: severity -1 serious > > As mentioned in > https://github.com/PHPMailer/PHPMailer/releases/tag/v5.2.27 the 5.2 > branch is deprecated and will not recieve security updates anymore > after 31st December 2018. > > This is not an issue per se, as we usually need to backport fixes to > older versions in general for bugfixes but in particular for > security-fixes; but starting buster with a know deprecated and not > supported version given upstream actively develops on the 6.x branch > looks somehow problematic for the buster release cycle. > > For this concern, I'm raising the severity to RC. > > there are a couple of packages with Depends or Build-Depends on > libphp-phpmailer, and I'm X-Debbugs-CC'ing those here. > > # Broken Depends: > cacti: cacti > tt-rss: tt-rss > wordpress: wordpress > > # Broken Build-Depends: > wordpress: libphp-phpmailer (>= 5.2.14) > > Regards, > Salvatore >
Bug#914495: upstream Kernels
Specifically This seems to fix v4.18.20 for me: > commit e0790ccfd489d46c0eeed32a8c4443b9b2119766 (HEAD -> test) > Author: Philip J Freeman > Date: Fri Dec 7 16:02:46 2018 -0800 > > Revert "drm/i915/ringbuffer: Delay after EMIT_INVALIDATE for gen4/gen5" > > This reverts commit 06e562e7f515292ea7721475950f23554214adde. > -- ⛵ - ☠️
Bug#850776: zfs-auto-snapshot: cronjob exits with error after package removal
Followup-For: Bug #850776 Hi, I've just opened a stretch-pu request to fix this bug in stable, too: https://bugs.debian.org/915935 Andreas diff -Nru zfs-auto-snapshot-1.2.1/debian/changelog zfs-auto-snapshot-1.2.1/debian/changelog --- zfs-auto-snapshot-1.2.1/debian/changelog2016-11-06 11:38:36.0 +0100 +++ zfs-auto-snapshot-1.2.1/debian/changelog2018-12-08 00:45:54.0 +0100 @@ -1,3 +1,10 @@ +zfs-auto-snapshot (1.2.1-1+deb9u1) stretch; urgency=medium + + * Backported from 1.2.4: +- Make cronjobs exit silently after package removal. (Closes: #850776) + + -- Andreas Beckmann Sat, 08 Dec 2018 00:45:54 +0100 + zfs-auto-snapshot (1.2.1-1) unstable; urgency=medium * Initial release (Closes: #720657) diff -Nru zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch --- zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch 1970-01-01 01:00:00.0 +0100 +++ zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch 2018-12-08 00:33:01.0 +0100 @@ -0,0 +1,48 @@ +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.daily zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.daily +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.daily 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.daily 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=daily --keep=31 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.frequent zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.frequent +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.frequent 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.frequent 2017-09-18 09:25:02.0 +0200 +@@ -1,3 +1,3 @@ + PATH="/usr/bin:/bin:/usr/sbin:/sbin" + +-*/15 * * * * root zfs-auto-snapshot -q -g --label=frequent --keep=4 // ++*/15 * * * * root which zfs-auto-snapshot > /dev/null || exit 0 ; zfs-auto-snapshot --quiet --syslog --label=frequent --keep=4 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.hourly zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.hourly +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.hourly 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.hourly 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=hourly --keep=24 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.monthly zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.monthly +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.monthly 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.monthly 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=monthly --keep=12 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.weekly zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.weekly +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.weekly 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.weekly 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=weekly --keep=8 // diff -Nru zfs-auto-snapshot-1.2.1/debian/patches/series zfs-auto-snapshot-1.2.1/debian/patches/series --- zfs-auto-snapshot-1.2.1/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ zfs-auto-snapshot-1.2.1/debian/patches/series 2018-12-08 00:45:50.0 +0100 @@ -0,0 +1 @@ +crontabs.patch
Bug#915936: mupdf.1: Some typographical and formatting fixes to the manual
Package: mupdf Version: 1.14.0+ds1-2 Severity: minor Tags: patch Dear Maintainer, I found some formatting and textual defects: 1) Remove a superfluous escape character /home/bg/git/groff/build/../tmac/an-old.tmac:385: backtrace: macro 'B' troff: :131: warning: escape character ignored before '+' 2) Change '-' (\-) to '\(en' (en-dash) for a numeric range. mupdf.1:122:.B [0-9]m mupdf.1:125:.B [0-9]t mupdf.1:212:MuPDF is Copyright 2006-2017 Artifex Software, Inc. # 3) Add a comma (or \&) after "e.g." and "i.e.", or use English words (man-pages(7) [package "manpages"]). 199:file to be reloaded automatically, for use in e.g. build scripts. # 4) Wrong distance between sentences or protect the indicator. a) Separate the sentences and subordinate clauses; each begins on a new line. See man-pages(7) [package "manpages"] and "info groff". Or b) Adjust space between sentences (two spaces), c) or protect the indicator by adding "\&" after it. The "indicator" is an "end-of-sentence character" (.!?). 45:(off) and 8 (best). The default value is 8. 48:Sets the full-page tint using hexadecimal color syntax. The default value 67:A left click on a hyper link follows the link. In presentation mode 74:Pan the page. Panning beyond the bottom or top 78:Select text in an area. On X11, the selected text 87:Pan page up or down. Does not change page 117:Mark current page for snap back. Up to 256 pages can be marked. 199:file to be reloaded automatically, for use in e.g. build scripts. # The patch is in the attachment. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.10-2 (SMP w/2 CPU cores) Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE=is_IS.iso88591 (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages mupdf depends on: ii libc62.27-8 ii libfreetype6 2.9.1-3 ii libharfbuzz0b2.1.1-1+b1 ii libjbig2dec0 0.15-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libopenjp2-7 2.3.0-1 ii libssl1.11.1.1a-1 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii zlib1g 1:1.2.11.dfsg-1 mupdf recommends no packages. Versions of packages mupdf suggests: pn mupdf-tools -- no debconf information -- Bjarni I. Gislason --- mupdf.1 2018-11-04 00:13:26.0 + +++ mupdf.1.new 2018-12-06 00:34:22.0 + @@ -26,8 +26,6 @@ and various image formats such as .B GIF, and .B TIFF. -.PP - .SH OPTIONS A description of each of the supported options is included below. @@ -42,11 +40,12 @@ The default value is 72. .TP .B \-A bits Changes the anti-aliasing quality, specified as a number of bits between 0 -(off) and 8 (best). The default value is 8. +(off) and 8 (best). +The default value is 8. .TP .B \-C RRGGBB -Sets the full-page tint using hexadecimal color syntax. The default value -is FFFAF0. +Sets the full-page tint using hexadecimal color syntax. +The default value is FFFAF0. .TP .B \-W width Page width in points for EPUB layout. @@ -64,18 +63,20 @@ User style sheet for EPUB layout. .TP .B Left mouse button click -A left click on a hyper link follows the link. In presentation mode -advances to the next page. +A left click on a hyper link follows the link. +In presentation mode advances to the next page. .TP .B Right mouse button click In presentation mode goes back to the previous page. .TP .B Left mouse button drag -Pan the page. Panning beyond the bottom or top +Pan the page. +Panning beyond the bottom or top edge will go to the next or previous page. .TP .B Right mouse button drag -Select text in an area. On X11, the selected text +Select text in an area. +On X11, the selected text can be pasted in another application with a middle click. Press .B Ctrl+C @@ -84,8 +85,8 @@ On Windows, the selected text will autom to the clipboard. .TP .B Scroll wheel -Pan page up or down. Does not change page -when reaching the bottom or top edge. +Pan page up or down. +Does not change page when reaching the bottom or top edge. .TP .B Shift + Scroll wheel Pan page left or right. @@ -114,21 +115,22 @@ Go to page 123. Go to the first or last page. .TP .B m -Mark current page for snap back. Up to 256 pages can be marked. +Mark current page for snap back. +Up to 256 pages can be marked. .TP .B t Pop back to the latest mark. .TP -.B [0-9]m +.B [0\(en9]m Save the current page number in the numbered register. .TP -.B [0-9]t +.B [0\(en9]t Go to the page saved in the numbered register. .PP Zooming and rotating: .TP -.B \+, \- +.B +, \- Zoom in or out. .TP .B W, H @@ -196,7 +198,7 @@ Quit. .TP .B SIGHUP Sending a \fBSIGHUP\fR signal to the mupdf process will also cause the viewed -file to be reloaded automatically, for use in e.g.
Bug#915010: Hardware Error
This turned out to be a hardware issue. Tested fine on same arch, different hardware.
Bug#915935: stretch-pu: package zfs-auto-snapshot/1.2.1-1+deb9u1
Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu Can we backport the changes from unstable that silence the cronjobs after package removal? #850776 Andreas diff -Nru zfs-auto-snapshot-1.2.1/debian/changelog zfs-auto-snapshot-1.2.1/debian/changelog --- zfs-auto-snapshot-1.2.1/debian/changelog2016-11-06 11:38:36.0 +0100 +++ zfs-auto-snapshot-1.2.1/debian/changelog2018-12-08 00:45:54.0 +0100 @@ -1,3 +1,10 @@ +zfs-auto-snapshot (1.2.1-1+deb9u1) stretch; urgency=medium + + * Backported from 1.2.4: +- Make cronjobs exit silently after package removal. (Closes: #850776) + + -- Andreas Beckmann Sat, 08 Dec 2018 00:45:54 +0100 + zfs-auto-snapshot (1.2.1-1) unstable; urgency=medium * Initial release (Closes: #720657) diff -Nru zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch --- zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch 1970-01-01 01:00:00.0 +0100 +++ zfs-auto-snapshot-1.2.1/debian/patches/crontabs.patch 2018-12-08 00:33:01.0 +0100 @@ -0,0 +1,48 @@ +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.daily zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.daily +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.daily 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.daily 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=daily --keep=31 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.frequent zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.frequent +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.frequent 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.frequent 2017-09-18 09:25:02.0 +0200 +@@ -1,3 +1,3 @@ + PATH="/usr/bin:/bin:/usr/sbin:/sbin" + +-*/15 * * * * root zfs-auto-snapshot -q -g --label=frequent --keep=4 // ++*/15 * * * * root which zfs-auto-snapshot > /dev/null || exit 0 ; zfs-auto-snapshot --quiet --syslog --label=frequent --keep=4 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.hourly zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.hourly +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.hourly 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.hourly 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=hourly --keep=24 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.monthly zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.monthly +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.monthly 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.monthly 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=monthly --keep=12 // +diff -Nru zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.weekly zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.weekly +--- zfs-auto-snapshot-1.2.1/etc/zfs-auto-snapshot.cron.weekly 2014-10-14 06:19:48.0 +0200 zfs-auto-snapshot-1.2.4/etc/zfs-auto-snapshot.cron.weekly 2017-09-18 09:25:02.0 +0200 +@@ -1,2 +1,6 @@ + #!/bin/sh ++ ++# Only call zfs-auto-snapshot if it's available ++which zfs-auto-snapshot > /dev/null || exit 0 ++ + exec zfs-auto-snapshot --quiet --syslog --label=weekly --keep=8 // diff -Nru zfs-auto-snapshot-1.2.1/debian/patches/series zfs-auto-snapshot-1.2.1/debian/patches/series --- zfs-auto-snapshot-1.2.1/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ zfs-auto-snapshot-1.2.1/debian/patches/series 2018-12-08 00:45:50.0 +0100 @@ -0,0 +1 @@ +crontabs.patch
Bug#915904: [Pkg-phototools-devel] Bug#915904: feh: Does not store rotate images
Control: tags -1 +confirmed
On Fri, Dec 7, 2018 at 8:45 PM Andreas Tille wrote:
> Package: feh
> Version: 3.1-1
[...]
> since the update to version 3.1 feh does not store images that
> are rotated via '<' / '>' keys.
Indeed and that's an upstream decision since the 3.0 release[1]. Quoting:
"Flip and rotation (keys "<", ">", "|", and "_") no longer change the
underlying file. This leaves delete ("Ctrl+Delete") as the only
destructive action which is enabled by default.
Add option --edit, which makes flip and rotation change the underlying
file as well as the displayed image. This was the default behaviour in
feh 1.x and 2.x".
You have three options to circumvent this. Use the 's' key to save the
modified image with the 'feh_' filename prefix, use 'feh --edit' to
view and be able to change your pictures (please close the bug in
these cases if you agree with it) or as a package uploader you can
restore the previous behavior with patching src/options.c to set
opt.edit unconditionally (close this bug from the changelog then).
Kind regards,
Laszlo/GCS
[1] https://feh.finalrewind.org/archive/3.0/
Bug#915934: libeigen3-dev: cannot build with Eigen anymore after upgrade of gcc-8 to 8.2.0-11
Package: libeigen3-dev
Version: 3.3.5-2
Severity: grave
Justification: renders package unusable
Hi,
steps to reproduce:
--%<---
#include "eigen3/Eigen/Eigen"
int main(int argc, char* argv[]) { return 0; }
-->%---
$ gcc main.cc
In file included from /usr/include/eigen3/Eigen/SparseCore:50,
from /usr/include/eigen3/Eigen/Sparse:26,
from /usr/include/eigen3/Eigen/Eigen:2,
from main.cc:1:
/usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h: In member function
'Eigen::internal::sparse_matrix_block_impl::BlockType&
Eigen::internal::sparse_matrix_block_impl::operator=(const BlockType&)':
/usr/include/eigen3/Eigen/src/SparseCore/SparseBlock.h:216:33: error: expected
primary-expression before '>' token
return operator=(other);
^
This did not happen with snapshot 20181207T090635Z where src:gcc-8
packages were still in version 8.2.0-10. It started happening one
dinstall later in snapshot 20181207T153749Z where src:gcc-8 version
8.2.0-11 got uploaded.
Thanks!
cheers, josch
Bug#914495: upstream Kernels
I tested some upstream stable kernels and can report that the bug is not present in v4.18.19 and is present in v4.18.20. * a9da8725b7a7 (tag: v4.18.20) Linux 4.18.20 * 6559b2338d96 (tag: v4.18.19) Linux 4.18.19 -- ⛵ - ☠️
Bug#913883: usrmerge: can't merge with iptables and ebtables installed
On Nov 17, Marco d'Itri wrote: > > Uninstalling ebtables makes the conversion pass. Installing ebtables > > again works without error. > But I highly doubt that the ebtables nft emulation would still work at > that point. Confirmed: this way ebtables overwrites the iptables diversion. > > I have no idea who is at fault here > iptables should not have started managing /usr/sbin/ebtables-restore > without coordinaation with ebtables (or else conflicting with it). > I cannot see how this would not be broken even without a merged-/usr > since systems would have two functionally different ebtables-restore > programs in different directories. Confirmed: iptables should divert /sbin/ebtables*, and having two different commands with the same name in the $PATH is broken with or without merged-/usr. But while the bug is in iptables I will make usrmerge conflict with ebtables: since ebtables is deprecated this should cause less problems for users. I would really appreciate if the iptables maintainer could comment about this bug. -- ciao, Marco signature.asc Description: PGP signature
Bug#914716: molly-guard: breaks conversion to merged /usr with usrmerge
On Nov 26, Chris Lamb wrote: How to reproduce: install pm-utils and molly-guard, then install usrmerge. So I will make usrmerge conflict with molly-guard, again. > I'm not sure why this wasn't fixed in #660064 or #837928, but: preinst says: # Disable diversions of pm-utils binaries until #812545 is fixed #for cmd in pm-hibernate pm-suspend pm-suspend-hybrid ; do #dpkg-divert --package molly-guard --divert /lib/molly-guard/$cmd --rename /usr/sbin/$cmd #done But #812545 was fixed in May, so molly-guard should be fixed, again. -- ciao, Marco signature.asc Description: PGP signature
Bug#904976: what are the problems?
Andreas, you say "The GTK3 version contains too much problems". Do you have a list of these problems? Just now I found a problem in geeqie (fullscreen spanning multiple monitors is broken), which is very easy to fix for GTK3 and hard to fix for GTK2 (https://github.com/BestImageViewer/geeqie/pull/651) If we had a list of issues, I might have a look at some of them (just to get my fullscreen fix working in Debian). openSUSE has been compiling geeqie with GTK3 since April 2016, so it can't be all that bad. If you paper over the issues by sticking to GTK2, we might never get the chance to fix them. -- Jiri Bohac e-mail/jabber: j...@boha.cz
Bug#912583: simpleitk patch for Python 3.7
On Fri, Dec 07, 2018 at 11:05:18PM +0100, Andreas Tille wrote: > On Fri, Dec 07, 2018 at 10:37:55PM +0200, Adrian Bunk wrote: > > Can you send the complete build log? The error might be elsewhere. > > Attached. Kind regards, Andreas. The actual error in the log is: ... CMake Error at /usr/lib/cmake/ITK-4.12/ITKModuleAPI.cmake:56 (message): No such module: "ITKImageIO" Call Stack (most recent call first): /usr/lib/cmake/ITK-4.12/ITKModuleAPI.cmake:26 (itk_module_load) /usr/lib/cmake/ITK-4.12/ITKModuleAPI.cmake:84 (_itk_module_config_recurse) /usr/lib/cmake/ITK-4.12/ITKConfig.cmake:79 (itk_module_config) Code/IO/src/CMakeLists.txt:17 (find_package) ... My first guess for that would be that this might be something new in ITK 4.13? cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#895123: libsdl2-2.0-0: This is normally a bug in some application using the D-Bus library.
Hi, Em sáb, 24 de nov de 2018 às 08:10, develo...@oldunreal.com escreveu: > > Sorry, I assumed the bugtracking system gathered all needed information. > The problem appears on x86_64 when linking a -m32 compiled application > against system provided libsdl2. We have to go back to square one. The text of the original report is empty, and the title "This is normally a bug in some application using the D-Bus library" also doesn't explain what the problem is about. So could you please reformulate the problem? Cheers. -- Manuel A. Fernandez Montecelo
Bug#873341: SBT is uninstallable; depends on nonexistent packages
Package: sbt Version: 0.13.13-2 Followup-For: Bug #873341 Dear Maintainer, just a curiosity, are you trying to package the latest 0.13.x version or the newer 1.x version? https://www.scala-sbt.org/download.html JFYI I would use sbt to try to build the Kitai Struct compiler: https://github.com/kaitai-io/kaitai_struct_compiler Thank you, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sbt depends on: ii libsbt-java0.13.13-2 ii openjdk-8-jre [java8-runtime] 8u191-b12-2 sbt recommends no packages. sbt suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#912042: electrum.png file moved from py-electrum to electrum without proper Breaks/Replaces
Hi again, Cyril Brulebois (2018-12-07): > setup.py doesn't seem to have been updated regarding that data file, > stored in the data_files variable and used in the same way in 3.1.3-1 > and in 3.2.3-1, so I suspect the tooling might have changed (at least > python3-setuptools seems to have been updated several times, without > much details in its debian/changelog). > > I think I won't dig into it much more, and just ACK the image move from > one package to another through the proposed Breaks/Replaces > relationship. > > I'll set up a chroot-based test case, upgrading from older electrum & > python3-electrum packages, checking they fail to upgrade to sid's > packages; then redo this with fixed packages. I'll post the final patch > and upload (possibly to DELAYED) once I'm done with testing. I can't seem able to trigger a practical issue with the following steps, with repo1 having 3.1.3-1 in the buster distribution, which I install first, and 3.2.3-1 in the sid distribution, which I upgrade to later: sudo debootstrap buster buster-amd64 http://mirror.home/debian rsync -av repo1 buster-amd64/tmp sudo chroot buster-amd64 echo 'deb [trusted=yes] file:///tmp/repo1 buster main' > /etc/apt/sources.list.d/electrum.list apt-get update apt-get -y install python3-electrum electrum --no-install-recommends echo 'deb [trusted=yes] file:///tmp/repo1 sid main' > /etc/apt/sources.list.d/electrum.list apt-get update apt-get -y install electrum A dpkg feature seems triggered: Preparing to unpack .../electrum_3.2.3-1_all.deb ... Unpacking electrum (3.2.3-1) over (3.1.1-1) ... => Replaced by files in installed package python3-electrum (3.1.1-1) ... Preparing to unpack .../python3-electrum_3.2.3-1_all.deb ... Unpacking python3-electrum (3.2.3-1) over (3.1.1-1) ... Setting up python3-electrum (3.2.3-1) ... Processing triggers for mime-support (3.61) ... Setting up electrum (3.2.3-1) ... And that seems to happen because of a Replaces relationship the other way around: $ dpkg --info python3-electrum_3.2.3-1_all.deb | grep Replaces: Replaces: electrum, python-electrum which might be responsible for this (with some debug on the dpkg side): root@wodi:/tmp/repo1/pool/main/e/electrum# dpkg -D440 -i *3.2.3* (Reading database ... 11134 files and directories currently installed.) Preparing to unpack electrum_3.2.3-1_all.deb ... Unpacking electrum (3.2.3-1) over (3.1.3-1) ... D40: does_replace new=electrum:all old=python3-electrum:all (0:3.1.3-1) D40: does_replace ... no D40: does_replace new=python3-electrum:all old=electrum:all (0:3.2.3-1) D000400: does_replace ... found old, version D40: does_replace ... yes Replaced by files in installed package python3-electrum (3.1.3-1) ... Preparing to unpack python3-electrum_3.2.3-1_all.deb ... Unpacking python3-electrum (3.2.3-1) over (3.1.3-1) ... […] I'm told electrum is an undocumented Tails feature, so I'll probably disable it for the time being; at least until the maintainer comments on this bug report. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ signature.asc Description: PGP signature
Bug#915933: missing license in debian/copyright
Package: twms Version: 0.06y-2 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: twms-0.06y/twms/twms.conf twms-0.06y/index.py to your debian/copyright. Thanks! Thorsten
Bug#915932: RM: aolserver4-nsxml -- RoQA; Module for obsolete aolserver
Package: ftp.debian.org Severity: normal Please remove aolserver4-nsxml, it's a module for the obsolete aolserver, which is filed for removal (#891633).
Bug#915931: RM: aolserver4-nssha1 -- RoQA; Module for obsolete aolserver
Package: ftp.debian.org Severity: normal Please remove aolserver4-nssha1, it's a module for the obsolete aolserver, which is filed for removal (#891633).
Bug#915930: RM: aolserver4-nssqlite3 -- RoQA; Module for obsolete aolserver
Package: ftp.debian.org Severity: normal Please remove aolserver4-nssqlite3, it's a module for the obsolete aolserver, which is filed for removal (#891633).
Bug#915929: RM: aolserver4-nspostgres -- RoQA; Module for obsolete aolserver (scheduled for removal)
Package: ftp.debian.org Severity: normal Please remove aolserver4-nspostgres, it's a module for the obsolete aolserver, which is filed for removal (#891633).
Bug#915928: RM: aolserver4-nsmysql -- RoQA; Module for obsolete aolserver (scheduled for removal)
Package: ftp.debian.org Severity: normal Please remove aolserver4-nsmysql, it's a module for the obsolete aolserver, which is filed for removal (#891633). Cheers, Moritz
Bug#915927: RM: aolserver4-nsldap -- RoQA; aolserver4-nsldap
Package: ftp.debian.org Severity: normal Please remove aolserver4-nsldap, it's a module for the obsolete aolserver, which is filed for removal (#891633). Cheers, Moritz
Bug#915926: mate-power-manager: Uses vendor-specific patch series file (ubuntu.series)
Source: mate-power-manager Version: 1.20.2-2 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, mate-power-manager appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915917: numix-gtk-theme: Uses vendor-specific patch series file (ubuntu.series)
Source: numix-gtk-theme Version: 2.6.7-3 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, numix-gtk-theme appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915915: xchat: Uses vendor-specific patch series file (ubuntu.series)
Source: xchat Version: 2.8.8-15 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, xchat appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915924: deluge: Uses vendor-specific patch series file (ubuntu.series)
Source: deluge Version: 1.3.15-2 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, deluge appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915925: libxfce4util: Uses vendor-specific patch series file (ubuntu.series)
Source: libxfce4util Version: 4.13.2-1 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, libxfce4util appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915918: mate-terminal: Uses vendor-specific patch series file (ubuntu.series)
Source: mate-terminal Version: 1.20.1-1 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, mate-terminal appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915922: filezilla: Uses vendor-specific patch series file (ubuntu.series)
Source: filezilla Version: 3.33.0-1 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, filezilla appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915916: smuxi: Uses vendor-specific patch series file (ubuntu.series)
Source: smuxi Version: 1.0.7-4 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, smuxi appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915919: mixxx: Uses vendor-specific patch series file (ubuntu.series)
Source: mixxx Version: 2.1.5~dfsg-1 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, mixxx appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915923: fail2ban: Uses vendor-specific patch series file (neurodebian-backport.series)
Source: fail2ban Version: 0.10.2-2.1 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, fail2ban appears to use a vendor-specific patch series file: debian/patches/neurodebian-backport.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915921: libfreenect: Uses vendor-specific patch series file (neurodebian-backport.series)
Source: libfreenect Version: 1:0.5.3-1 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, libfreenect appears to use a vendor-specific patch series file: debian/patches/neurodebian-backport.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915920: liferea: Uses vendor-specific patch series file (ubuntu.series)
Source: liferea Version: 1.12.5-2 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, liferea appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915914: xfce4-smartbookmark-plugin: Uses vendor-specific patch series file (ubuntu.series)
Source: xfce4-smartbookmark-plugin Version: 0.4.6-2 Severity: important User: la...@debian.org Usertags: package-uses-vendor-specific-patch-series Dear Maintainer, xfce4-smartbookmark-plugin appears to use a vendor-specific patch series file: debian/patches/ubuntu.series This is feature of dpkg that can be used to apply a different series of quilt patches when the source package is unpacked on different systems. However, since Debian source packages are usually treated as a pure transport format this can cause confusion and frustration. Please migrate away from such series files and consider alternatives such differing source packages or modify the build process to behave conditionally or to conditionally patch files explicitly. After Buster is released, the presence of a vendor-specific patch series will be a violation of a MUST directive in Debian policy. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#915913: autopkgtest: please document what the syntax of the Features field is
Package: autopkgtest Version: 5.6 Severity: normal Hi, from here: https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst it says: > Features: feature-name [, another-feature-name ...] > Declares some additional capabilities or good properties of the > tests defined in this stanza. Any unknown features declared will be > completely ignored. See below for the defined features. > > Features are separated by commas and/or whitespace. then further below under "defined features" it says: > test-name > Set an explicit test name for the log heading and the ``summary`` file > for a ``Test-Command:`` inline test. When not given, these are > enumerated like ``command1``. But this does not explain the syntax of how a test name is actually specified. Does one just write it in the Features field? Or is it test-name:thename or does one have to quote something? Please document what the right syntax is. My use case: I have a test that uses Test-Command but the output becomes hard to understand if tests are just named command1, command2 and so forth. Thus I want to give them meaningful names. Unfortunately under "Test-Command" it also says "This is mutually exclusive with the ``Tests:`` field". Is there a practical reason why these fields are mutually exclusive? Naively, I would've expected, that when Test-Command is given, then it doesn't look for a script but instead executes the command but that it anyways takes the test name from the "Tests" field. It seems unnecessarily complicated to require the test-name feature thing. Thanks! cheers, josch
Bug#909163: Bug#913112: ufw all traffic blocked, icmp-type + logging error on enable
On Tue, 20 Nov 2018 15:40:04 -0600 Jamie Strandboge wrote: > This issue is caused be a regression in iptables 1.8.1: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912610 > > This is now addressed in iptables. Please upgrade to iptables 1.8.2-2 and ufw > should start work again. If not, please file a new bug. This does not work, even with iptables 1.8.2-2 on a Debian sid system. Nor would I expect it to; ufw has explicit code to reject this scenario. See also Launchpad #1368411, and specifically this comment from me with a patch (which I have also attached): https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1368411/comments/10 -- Richard Author: Richard Laager Description: Fix inserting IPv6 rules The list of ufw rules is a single list, with IPv4 rules before IPv6 rules. When inserting an IPv6 rule, the ufw code converts the position from the overall list containing both IPv4 and IPv6 rules into a position in the subset of IPv6 rules only. If the specified position falls inside the IPv4 rules, then by definition, the desired IPv6 position is 1, but the current code needlessly rejects that. This breaks fail2ban, which always uses: ufw insert 1 reject from ADDRESS to any Forwarded: no Last-Update: 2018-10-08 Bug-Ubuntu: https://launchpad.net/bugs/1368411 --- a/src/frontend.py +++ b/src/frontend.py @@ -454,8 +454,7 @@ if r.position > num_v4: r.set_position(r.position - num_v4) elif r.position != 0 and r.position <= num_v4: -pos_err_msg += str(r.position) + "'" -raise UFWError(pos_err_msg) +r.set_position(1) r.set_v6(True) tmp = self.backend.set_rule(r) elif ip_version == "both": --- a/tests/ipv6/rules64/runtest.sh +++ b/tests/ipv6/rules64/runtest.sh @@ -156,7 +156,7 @@ echo "ipv6 rule in ipv4 section" >> $TESTTMP/result do_cmd "0" null delete allow to ::1 port -do_cmd "1" null insert 2 allow to ::1 port +do_cmd "0" null insert 2 allow to ::1 port echo "ipv4 rule in ipv6 section" >> $TESTTMP/result do_cmd "0" null delete allow to ::1 port
Bug#914833: RFS: python-pyxs/0.4.1-1 [ITP] -- Pure Python XenStore client implementation
Hi nicoo, Thank you for looking at my package! I appreciate any feedback. On Freitag, 07 Dezember 2018, 13:08 +0100, Nicolas Braud-Santoni wrote: > I created salsa.d.o/Debian/pyxs and granted access to @benjamin-guest. > Can you confirm this is you? :) Thank you! It is I and I have pushed there. > Speaking of which, it was signed with an OpenPGP key that I was unable to > find on keyservers: 0x5B290760467674D74D787DF41B47C9BAC891A072 The key is now to be found at the deep end of the sks pool; it appears not to be fully propagated yet :) gpg --keyserver keyserver2.computer42.org \ --recv-keys 4A1A4FB9DFAF3A4015B19FE5667FBEDE1C69BE14 Kind regards, Benjamin signature.asc Description: PGP signature
Bug#915805: Should this package be removed?
On 2018-12-07 13:41, Kevin Smith wrote: > Apologies, I’d forgotten that we’d prepared an update from upstream and not > gotten it submitted. We’ll try to address this in the next week or so. Nice! If you intend to raise the package from the not yet dead, please consider joining the XMPP packaging team and have the Debian package code in salsa.debian.org/xmpp-team/
Bug#913112: Info received (Bug#913112: ufw all traffic blocked, icmp-type + logging error on enable)
Fyi, I reopened this since it was accidentally closed. I plan on looking at this bug, so hopefully we can close it for real soon. :) -- Jamie Strandboge | http://www.canonical.com signature.asc Description: PGP signature
Bug#915912: merge request for modules reproducability
Control: tags -1 + patch Control: forwarded -1 https://salsa.debian.org/mckinstry/modules/merge_requests/3 Hi again, I've submitted my proposed patch as a merge-request against the packaging vcs (see above). Regards, Andreas Henriksson
Bug#915912: modules: reproducible build (usrmerge): embeds path of tools found via PATH
Source: modules Version: 4.2.1-1 Severity: normal Tags: unreproducible User: m...@linux.it Dear Maintainer, The package currently fails to build reproducibly in a merged-usr vs non-merged environment. The path of ps is embedded in a shipped file and is found via /usr/bin (rather than /bin) on a merged-usr system (where /bin is a symlink to /usr/bin), since default PATH has /usr/bin before /bin. This is unfortunate for non-merged systems as there /usr/bin/ps does not exist. There are other tools which has the same problem, but they are not affected by merged-usr as they normally live in /usr/bin. However these paths might also end up incorrect, since the local dirty build environment could have the tool installed in /usr/local/bin or may have modified $PATH in some way that gives undesired results. Regards, Andreas Henriksson
Bug#915911: Additional information
Purging and reinstalling Blender didn't help. However listing installed packages shows minor version discrepancy. blender-data/testing,testing,now 2.79.b+dfsg0-4 all [installed,automatic] blender/testing,now 2.79.b+dfsg0-4+b2 amd64 [installed] Not sure if this can be the reason but I am reporting it anyway. -- Mladen Mijatov Key ID: 4096R/83EFD5A0 2013-08-18
Bug#915908: matplotlib breaks python-cogent autopkgtest
control: reassign -1 python-cogent control: notfound -1 matplotlib/2.2.3-2 this is something to fix in cogent test suite (they even got expected/observed reverted...) On Fri, Dec 7, 2018 at 3:39 PM Paul Gevers wrote: > > Source: matplotlib, python-cogent > Control: found -1 matplotlib/2.2.3-2 > Control: found -1 python-cogent/1.9-12 > X-Debbugs-CC: debian...@lists.debian.org > User: debian...@lists.debian.org > Usertags: breaks needs-update > > Dear maintainers, > > With a recent upload of matplotlib the autopkgtest of python-cogent > fails in testing when that autopkgtest is run with the binary packages > of matplotlib from unstable. It passes when run with only packages from > testing. In tabular form: >passfail > matplotlib from testing2.2.3-2 > python-cogent from testing1.9-12 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. Interestingly > enough, the test passed with 2.2.3-1, in contrast to the other packages > at that time. > > Currently this regression is contributing to the delay of the migration > of matplotlib to testing [1]. Due to the nature of this issue, I filed > this bug report against both packages. Can you please investigate the > situation and reassign the bug to the right package? If needed, please > change the bug's severity. > > More information about this bug and the reason for filing it can be found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://qa.debian.org/excuses.php?package=matplotlib > > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cogent/1451883/log.gz > > autopkgtest [11:48:18]: test run-unit-test: [--- > bwa can be tested on amd64 arch > lolo > Can't find formatdb executable: skipping test > Can't find blastall executable: skipping test > Can't find blat executable: skipping test > Can't find bwa executable: skipping test > Can't find carnac executable: skipping test > Can't find cdbfasta executable: skipping test > Can't find clearcut executable: skipping test > Can't find cmfinder.pl executable: skipping test > Can't find comrna executable: skipping test > Can't find contrafold executable: skipping test > Can't find covea executable: skipping test > Can't find dialign2-2 executable: skipping test > Can't find dynalign executable: skipping test > Can't find FastTree executable: skipping test > Can't find foldalign executable: skipping test > Can't find guppy executable: skipping test > Can't find ilm executable: skipping test > Can't find knetfold.pl executable: skipping test > Can't find mfold executable: skipping test > Can't find muscle executable: skipping test > Can't find msms executable: skipping test > Can't find pplacer executable: skipping test > Can't find rdp_classifier-2.2.jar executable: skipping test > Can't find rdp_classifier-2.0.jar executable: skipping test > Can't find Fold.out executable: skipping test > Can't find findphyl executable: skipping test > Can't find pknotsRG-1.2-i386-linux-static executable: skipping test > Can't find RNAalifold executable: skipping test > Can't find rnaview executable: skipping test > Can't find RNAfold executable: skipping test > Can't find sfold.X86_64.LINUX executable: skipping test > Can't find stride executable: skipping test > Can't find hybrid-ss-min executable: skipping test > Can't find cd-hit executable: skipping test > Can't find calculate_likelihood executable: skipping test > Can't find sfffile executable: skipping test > Can't find sffinfo executable: skipping test > Can't find uclust executable: skipping test > Can't find usearch executable: skipping test > Environment variable TEST_DB=1 not set: skipping db tests >
Bug#915910: dist: reproducible build (usrmerge): embeds path of tools found via PATH
Package: dist Version: 1:3.5-236-0.1 Severity: normal Tags: patch unreproducible User: m...@linux.it Usertags: usrmerge Dear Maintainer, The package currently fails to build reproducibly on merged-usr vs non-merged systems. The paths of grep, sed, cat and zcat are looked up during build from PATH and is embedded in shipped files. There's a "d_portable" setting which promises to build portable scripts (by expanding from PATH at runtime, rather than build-time), but enabling it seems to cause build failure so it could not be used. I thus opted for explicitly specifying the paths for the affected tools. You however might want to earn extra bonus points fixing builds in dirty local environment by looking at all tools specified in loclist and trylist (in Configure), find which ones gets their path embedded in shipped files, and explicitly specify them all. (Or why not just fix up d_portable?) You might however want to give priority to looking at the stuff that lintian warns about for this package, which seems alot more urgent than spending time on fixing up builds done in dirty local environments. Please see the attached patch. Regards, Andreas Henriksson diff -u dist-3.5-236/debian/changelog dist-3.5-236/debian/changelog --- dist-3.5-236/debian/changelog +++ dist-3.5-236/debian/changelog @@ -1,3 +1,13 @@ +dist (1:3.5-236-0.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Since d_portable seems broken, tell configure which paths to use +for grep, sed, cat and zcat explicitly. +- fixes reproducible build on merged-usr vs non-merged systems. + * Use -D prefix=/usr instead of non-existant $(PREFIX) + + -- Andreas Henriksson Fri, 07 Dec 2018 20:47:02 +0100 + dist (1:3.5-236-0.1) unstable; urgency=medium * Non-maintainer upload. diff -u dist-3.5-236/debian/rules dist-3.5-236/debian/rules --- dist-3.5-236/debian/rules +++ dist-3.5-236/debian/rules @@ -35,7 +35,7 @@ touch .config/nomail&& \ sh ./Configure \ -de\ --D prefix=$(PREFIX)\ +-D prefix=/usr \ -D orgname=/etc/news/organization \ -D myhostname=localhost\ -D mydomain=localdomain\ @@ -44,6 +44,10 @@ -D pager=/bin/more \ -D mansrc=/usr/share/man/ \ -D cf_email='$(email)' \ +-D grep=/bin/grep \ +-D sed=/bin/sed\ +-D cat=/bin/cat\ +-D zcat=/bin/zcat \ -D d_berknames='define'
Bug#913112: ufw all traffic blocked, icmp-type + logging error on enable
reopen 909163 = signature.asc Description: PGP signature
Bug#915909: cups: CVE-2018-4700: Linux session cookies used a predictable random number seed
Source: cups Version: 2.2.9-4 Severity: important Tags: patch security upstream Hi, The following vulnerability was published for cups. CVE-2018-4700[0]: Linux session cookies used a predictable random number seed If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-4700 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-4700 [1] https://github.com/apple/cups/commit/feb4c62b211bfbd78dc10d737d873439ccdfa58c [2] https://github.com/apple/cups/commit/b9ff93ce913ff633a3f667317e5a81fa7fe0d5d3 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#912583: simpleitk patch for Python 3.7
On Mon, Dec 03, 2018 at 09:37:45AM +0100, Andreas Tille wrote: > Control: tags -1 help > > Hi, > > thanks for the patch which was applied in Git. I also bumped simpleitk > to latest upstream version. Unfortunately there seems to be an issue > with gdcm (gdcm Uploaders in CC): > > ... > -- Performing Test CXX_HAS-Wno-invalid-offsetof - Success > -- The imported target "vtkgdcmsharpglue" references the file >"/usr/lib/x86_64-linux-gnu/libvtkgdcmsharpglue.so" > but this file does not exist. Possible reasons include: > * The file was deleted, renamed, or moved to another location. > * An install or uninstall procedure did not complete successfully. > * The installation package was faulty and contained >"/usr/lib/x86_64-linux-gnu/gdcm-2.8/GDCMTargets.cmake" > but not all the files it references. > > -- The imported target "vtkgdcmPython" references the file >"/usr/lib/python/dist-packages/vtkgdcmPython.so" > but this file does not exist. Possible reasons include: > * The file was deleted, renamed, or moved to another location. > * An install or uninstall procedure did not complete successfully. > * The installation package was faulty and contained >"/usr/lib/x86_64-linux-gnu/gdcm-2.8/GDCMTargets.cmake" > but not all the files it references. > > -- Performing Test SITK_HAS_CXX11_STATIC_ASSERT > ... > > > Any hint how to deal with this? This looks like #826048, with claims there that this is harmless. Can you send the complete build log? The error might be elsewhere. > Kind regards > > Andreas. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#915908: matplotlib breaks python-cogent autopkgtest
Source: matplotlib, python-cogent Control: found -1 matplotlib/2.2.3-2 Control: found -1 python-cogent/1.9-12 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainers, With a recent upload of matplotlib the autopkgtest of python-cogent fails in testing when that autopkgtest is run with the binary packages of matplotlib from unstable. It passes when run with only packages from testing. In tabular form: passfail matplotlib from testing2.2.3-2 python-cogent from testing1.9-12 all others from testingfrom testing I copied some of the output at the bottom of this report. Interestingly enough, the test passed with 2.2.3-1, in contrast to the other packages at that time. Currently this regression is contributing to the delay of the migration of matplotlib to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=matplotlib https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cogent/1451883/log.gz autopkgtest [11:48:18]: test run-unit-test: [--- bwa can be tested on amd64 arch lolo Can't find formatdb executable: skipping test Can't find blastall executable: skipping test Can't find blat executable: skipping test Can't find bwa executable: skipping test Can't find carnac executable: skipping test Can't find cdbfasta executable: skipping test Can't find clearcut executable: skipping test Can't find cmfinder.pl executable: skipping test Can't find comrna executable: skipping test Can't find contrafold executable: skipping test Can't find covea executable: skipping test Can't find dialign2-2 executable: skipping test Can't find dynalign executable: skipping test Can't find FastTree executable: skipping test Can't find foldalign executable: skipping test Can't find guppy executable: skipping test Can't find ilm executable: skipping test Can't find knetfold.pl executable: skipping test Can't find mfold executable: skipping test Can't find muscle executable: skipping test Can't find msms executable: skipping test Can't find pplacer executable: skipping test Can't find rdp_classifier-2.2.jar executable: skipping test Can't find rdp_classifier-2.0.jar executable: skipping test Can't find Fold.out executable: skipping test Can't find findphyl executable: skipping test Can't find pknotsRG-1.2-i386-linux-static executable: skipping test Can't find RNAalifold executable: skipping test Can't find rnaview executable: skipping test Can't find RNAfold executable: skipping test Can't find sfold.X86_64.LINUX executable: skipping test Can't find stride executable: skipping test Can't find hybrid-ss-min executable: skipping test Can't find cd-hit executable: skipping test Can't find calculate_likelihood executable: skipping test Can't find sfffile executable: skipping test Can't find sffinfo executable: skipping test Can't find uclust executable: skipping test Can't find usearch executable: skipping test Environment variable TEST_DB=1 not set: skipping db tests
Bug#915802: apt-lisbugs: [INTL:pt] Portuguese translation
On Thu, 6 Dec 2018 21:35:31 + Miguel Figueiredo wrote: [...] > Updated Portuguese translation for apt-listbugs messages. > Feel free to use it. Hello Miguel, thanks for sending the updated translation! I have a question: #: ../lib/aptlistbugs/logic.rb:513 msgid "Failed to invoke querybts." msgstr "Falhou invocar o querybts." I guess "o" is an article. Since "querybts" is the name of a program (just like "cp", "ls", "firefox", and so forth...), is the use of an article in front of it appropriate? Please note that I know basically nothing about the Portuguese language, hence I can well be completely off-track... Please let me know, thanks for your time. > > For translation updates please contact 'Last Translator' or the > Portuguese Translation Team . Of course. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpEzxGngK1gl.pgp Description: PGP signature
Bug#911705: [Pkg-fonts-devel] Bug#911705: #911705 [l10n|gu] debian-installer: fonts broken for Gujarati
Hi,
Jonas Smedegaard wrote:
> Quoting Holger Wansing (2018-12-07 14:15:32)
> > Hi,
> >
> > Jonas Smedegaard wrote:
> > > Quoting Holger Wansing (2018-12-07 08:46:37)
> > > > Jonas Smedegaard wrote:
> > > > > A quick search for samples led me to
> > > > > https://fontinfo.opensuse.org/fonts/NotoSansGujaratiRegular.html
> > > > > and
> > > > > https://fontinfo.opensuse.org/fonts/NotoSerifGujaratiRegular.html
> > > > > which (especially when zoomed in and comparing the largest
> > > > > samples) show slight difference e.g. in the "middle" glyf (to me
> > > > > looking like an elefant at a lake with a candle on its head...)
> [...]
> > > > There is something going wrong with my font selection patch in
> > > > rootskel-gtk, it has no effect at all. Don't know what I am doing
> > > > wrong.
> > > > No matter which variant of
> > > > FONT_NAME="Noto Sans Gujarati"
> > > > FONT_NAME="Noto Sans Gujarati UI"
> > > > FONT_NAME="Noto Serif Gujarati"
> > > > I use, the used font is always the same.
> > >
> > > Did you see my comments on that above? Are you sure the differences
> > > are not simply _extremely_ small?
> >
> > Yes, that's probably possible. I need to validate this.
>
> Yes, please do.
>
>
> > Interestingly, when I don't set at all which font to use for gu, I get
> > the same result, at least at a first glance: I see the glyphs which
> > can be seen on the screenshots you got. In contrary, when I build an
> > installer image without the noto-fonts-unhinted-udeb package included,
> > I get the TOFU placeholder signs inserted for all gu character.
> > That makes me think that font selection via the gtk-set-font script
> > does not work here for whatever reason and some default is selected.
>
> That does not explain the elefant-at-lake-with-candle-on-head glyph in
> OpenSUSE samples being slightly different shape between Sans and Serif!
>
> I recommend to prioritize close examination over wild speculation.
Yes, you are right.
And in fact, Kartik wrote me that the screenshots I sent with
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911705#55
are all fine, but Noto Serif Gujarati is the best.
Kartik is fine with my request for forwarding his mail, so here it is:
Date: Fri, 7 Dec 2018 19:30:56 +0530
From: Kartik Mistry
To: hwans...@mailbox.org
Subject: Re: [debian-installer] Gujarati not usable, font broken or missing
On Fri, Dec 7, 2018 at 7:12 PM Holger Wansing wrote:
> may I get your attention on bug #915825:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915825.
Hi,
Sorry for ignoring this long time and thanks a lot for your work on
this! I was suppose to reply this and then had to move home in hurry
:/
> As I wrote there, I cannot see any difference on the three fonts
> "Noto Sans Gujarati", "Noto Sans Gujarati UI" and "Noto Serif Gujarati" in
> those screenshots.
> Can you?
> If yes, which one is best?
You can go ahead with any of these. All seems working fine. However,
Noto Serif Gujarati seems the best.
Thanks again!
--
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com
--
Holger Wansing
PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#915907: rclone: autopkgtest regression
Source: rclone Version: 1.45-1 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of rclone the autopkgtest of rclone fails in testing when that autopkgtest is run with the binary packages of rclone from unstable. It passes when run with only packages from testing. In tabular form: passfail rclone from testing1.45-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is contributing to the delay of the migration to testing [1]. Can you please investigate the situation and fix it? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=rclone https://ci.debian.net/data/autopkgtest/testing/amd64/r/rclone/1448865/log.gz autopkgtest [05:43:10]: test command1: [--- [info] Testing github.com/ncw/rclone... [info] Source code installed by binary package, overriding dh_auto_configure... dh build --buildsystem=golang --with=golang,bash-completion dh_update_autotools_config -O--buildsystem=golang dh_autoreconf -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest-lxc.g4pz4qxs/downtmp/autopkgtest_tmp' mkdir -p "obj-x86_64-linux-gnu" cp -a /usr/share/gocode/src "obj-x86_64-linux-gnu" make[1]: Leaving directory '/tmp/autopkgtest-lxc.g4pz4qxs/downtmp/autopkgtest_tmp' dh_auto_build -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -gcflags=all=\"-trimpath=/tmp/autopkgtest-lxc.g4pz4qxs/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\" -asmflags=all=\"-trimpath=/tmp/autopkgtest-lxc.g4pz4qxs/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src\" -v -p 2 github.com/ncw/rclone github.com/ncw/rclone/backend/alias github.com/ncw/rclone/backend/all github.com/ncw/rclone/backend/amazonclouddrive github.com/ncw/rclone/backend/azureblob github.com/ncw/rclone/backend/b2 github.com/ncw/rclone/backend/b2/api github.com/ncw/rclone/backend/box github.com/ncw/rclone/backend/box/api github.com/ncw/rclone/backend/cache github.com/ncw/rclone/backend/crypt github.com/ncw/rclone/backend/crypt/pkcs7 github.com/ncw/rclone/backend/drive github.com/ncw/rclone/backend/dropbox github.com/ncw/rclone/backend/dropbox/dbhash github.com/ncw/rclone/backend/ftp github.com/ncw/rclone/backend/googlecloudstorage github.com/ncw/rclone/backend/http github.com/ncw/rclone/backend/hubic github.com/ncw/rclone/backend/jottacloud github.com/ncw/rclone/backend/jottacloud/api github.com/ncw/rclone/backend/local github.com/ncw/rclone/backend/onedrive github.com/ncw/rclone/backend/onedrive/api github.com/ncw/rclone/backend/onedrive/quickxorhash github.com/ncw/rclone/backend/opendrive github.com/ncw/rclone/backend/pcloud github.com/ncw/rclone/backend/pcloud/api github.com/ncw/rclone/backend/s3 github.com/ncw/rclone/backend/sftp github.com/ncw/rclone/backend/swift github.com/ncw/rclone/backend/union github.com/ncw/rclone/backend/webdav github.com/ncw/rclone/backend/webdav/api github.com/ncw/rclone/backend/webdav/odrvcookie github.com/ncw/rclone/backend/yandex github.com/ncw/rclone/backend/yandex/api github.com/ncw/rclone/cmd github.com/ncw/rclone/cmd/about github.com/ncw/rclone/cmd/all github.com/ncw/rclone/cmd/authorize github.com/ncw/rclone/cmd/cachestats github.com/ncw/rclone/cmd/cat github.com/ncw/rclone/cmd/check github.com/ncw/rclone/cmd/cleanup github.com/ncw/rclone/cmd/cmount github.com/ncw/rclone/cmd/config github.com/ncw/rclone/cmd/copy github.com/ncw/rclone/cmd/copyto github.com/ncw/rclone/cmd/copyurl github.com/ncw/rclone/cmd/cryptcheck github.com/ncw/rclone/cmd/cryptdecode github.com/ncw/rclone/cmd/dbhashsum github.com/ncw/rclone/cmd/dedupe github.com/ncw/rclone/cmd/delete github.com/ncw/rclone/cmd/deletefile github.com/ncw/rclone/cmd/genautocomplete github.com/ncw/rclone/cmd/gendocs github.com/ncw/rclone/cmd/hashsum github.com/ncw/rclone/cmd/info github.com/ncw/rclone/cmd/link github.com/ncw/rclone/cmd/listremotes github.com/ncw/rclone/cmd/ls github.com/ncw/rclone/cmd/ls/lshelp github.com/ncw/rclone/cmd/lsd github.com/ncw/rclone/cmd/lsf github.com/ncw/rclone/cmd/lsjson github.com/ncw/rclone/cmd/lsl github.com/ncw/rclone/cmd/md5sum github.com/ncw/rclone/cmd/memtest github.com/ncw/rclone/cmd/mkdir github.com/ncw/rclone/cmd/mount github.com/ncw/rclone/cmd/mountlib github.com/ncw/rclone/cmd/mountlib/mounttest github.com/ncw/rclone/cmd/move github.com/ncw/rclone/cmd/moveto github.com/ncw/rclone/cmd/ncdu github.com/ncw/rclone/cmd/ncdu/scan github.com/ncw/rclone/cmd/obscure github.com/ncw/rclone/cmd/purge github.com/ncw/rclone/cmd/rc github.com/ncw/rclone/cmd/rcat github.com/ncw/rclone/cmd/rcd github.com/ncw/rclone/cmd/reveal
Bug#915906: python-pip: autopkgtest regression: output to stderr
Source: python-pip Version: 18.1-2 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of python-pip the autopkgtest of python-pip fails in testing when that autopkgtest is run with the binary packages of python-pip from unstable. It passes when run with only packages from testing. In tabular form: passfail python-pip from testing18.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. (Same stuff applies to python2 output. Currently this regression is contributing to the delay of the migration to testing [1] (apart from to other, please have a look at those too). Can you please investigate the situation and fix it? If needed, please change the bug's severity. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python-pip https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pip/1451877/log.gz autopkgtest [11:47:16]: test pip3-user.sh: [--- Collecting world Downloading https://files.pythonhosted.org/packages/c3/f6/369da6782ac505a0dd4d506bcf56f65c5242c441f6e64616aeba2da1/world-4.0.tar.gz Requirement already satisfied: atpublic in /usr/local/lib/python3.6/dist-packages (from world) (1.0) Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (from world) (40.5.0) Building wheels for collected packages: world Running setup.py bdist_wheel for world: started Running setup.py bdist_wheel for world: finished with status 'done' Stored in directory: /tmp/autopkgtest-lxc.v533yvr0/downtmp/autopkgtest_tmp/.cache/pip/wheels/d2/3a/b5/dbd026ee64b640c89a82a91a929e2589c4200a895853be9f9b Successfully built world Installing collected packages: world The script world is installed in '/tmp/autopkgtest-lxc.v533yvr0/downtmp/autopkgtest_tmp/.local/bin' which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. Successfully installed world-4.0 Package Version - --- asn1crypto0.24.0 atpublic 1.0 cryptography 2.3 entrypoints 0.2.3.post3 idna 2.6 keyring 16.1.1 keyrings.alt 3.1 pip 18.1 pycrypto 2.6.1 PyGObject 3.30.2 pyxdg 0.25 SecretStorage 2.3.1 setuptools40.5.0 six 1.11.0 wheel 0.30.0 world 4.0 drwxr-xr-x 2 debci debci 4096 Dec 7 11:47 /tmp/autopkgtest-lxc.v533yvr0/downtmp/autopkgtest_tmp/.local/lib/python3.6/site-packages/world-4.0.dist-info Uninstalling world-4.0: Successfully uninstalled world-4.0 Package Version - --- asn1crypto0.24.0 atpublic 1.0 cryptography 2.3 entrypoints 0.2.3.post3 idna 2.6 keyring 16.1.1 keyrings.alt 3.1 pip 18.1 pycrypto 2.6.1 PyGObject 3.30.2 pyxdg 0.25 SecretStorage 2.3.1 setuptools40.5.0 six 1.11.0 wheel 0.30.0 autopkgtest [11:47:21]: test pip3-user.sh: ---] autopkgtest [11:47:22]: test pip3-user.sh: - - - - - - - - - - results - - - - - - - - - - pip3-user.sh FAIL stderr: The script world is installed in '/tmp/autopkgtest-lxc.v533yvr0/downtmp/autopkgtest_tmp/.local/bin' which is not on PATH. autopkgtest [11:47:22]: test pip3-user.sh: - - - - - - - - - - stderr - - - - - - - - - - The script world is installed in '/tmp/autopkgtest-lxc.v533yvr0/downtmp/autopkgtest_tmp/.local/bin' which is not on PATH. Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. signature.asc Description: OpenPGP digital signature
Bug#913942: espeakup 0.80-5+deb9u3 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: espeakup Version: 0.80-5+deb9u3 Explanation: debian/espeakup.service: Fix compatibility with older versions of systemd
Bug#909131: kmodpy 0.1.10-2.1~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: kmodpy Version: 0.1.10-2.1~deb9u1 Explanation: remove incorrect Multi-Arch: same from python-kmodpy
Bug#913529: openvpn 2.4.0-6+deb9u3 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: openvpn Version: 2.4.0-6+deb9u3 Explanation: fix NCP behaviour on TLS reconnect, causing "AEAD Decrypt error: cipher final failed" errors
Bug#909213: wvstreams 4.6.1-12~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: wvstreams Version: 4.6.1-12~deb9u1 Explanation: work around stack corruption
Bug#893541: isort 4.2.5+ds1-2+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: isort Version: 4.2.5+ds1-2+deb9u1 Explanation: fix Python dependencies
Bug#915905: Wish: support /usr/bin/go via Debian alternatives system?
Package: golang-1.11 Version: 1.11.2-2 Severity: wishlist Dear Maintainer, I had golang-1.10 installed as a dependency of golang-go, and /usr/bin/go was linked to version 1.10. When I installed goland-1.11, I expected that link perhaps to be updated, but more likely added to /etc/alternatives, so that I could select the appropriate version from there. As far as I could tell, the only option is/was to rewrite that link if I wanted 1.11 as default. Am I missing something? -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages golang-1.11 depends on: ii golang-1.11-doc 1.11.2-2 ii golang-1.11-go 1.11.2-2 ii golang-1.11-src 1.11.2-2 golang-1.11 recommends no packages. golang-1.11 suggests no packages. -- no debconf information
Bug#893543: pylint-django 0.7.2-1+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: pylint-django Version: 0.7.2-1+deb9u1 Explanation: fix Python 3 dependencies
Bug#908957: z3 4.4.1-0.4~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: z3 Version: 4.4.1-0.4~deb9u1 Explanation: remove incorrect Multi-Arch: same from python-z3
Bug#909127: ibus 1.5.14-3+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: ibus Version: 1.5.14-3+deb9u1 Explanation: fix multi-arch installation by removing the gir package's Python dependency
Bug#893550: astroml-addons 0.2.2-4~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: astroml-addons Version: 0.2.2-4~deb9u1 Explanation:
Bug#892853: wicd 1.7.4+tb2-5~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: wicd Version: 1.7.4+tb2-5~deb9u1 Explanation: always depend on net-tools, rather than alternatives
Bug#892845: openni2 2.2.0.33+dfsg-7+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: openni2 Version: 2.2.0.33+dfsg-7+deb9u1 Explanation: fix armhf baseline violation and armel FTBFS caused by NEON usage
Bug#891660: linux-igd 1.0+cvs20070630-5+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: linux-igd Version: 1.0+cvs20070630-5+deb9u1 Explanation: make the init script require $network
Bug#891569: gvrng 4.4-3~deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: gvrng Version: 4.4-3~deb9u1 Explanation: fix permissions problem that prevented starting gvrng; generate correct Python dependencies
Bug#891649: uglifyjs 2.7.5-2+deb9u1 flagged for acceptance
Control: tags -1 + pending Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: uglifyjs Version: 2.7.5-2+deb9u1 Explanation: fix manpage contents
Bug#905027: tgt-glusterfs: bs-type glfs doesn't work at all
Control: severity -1 important Control: tags -1 + moreinfo Hi, Thanks for the report and apologies for the late response. On 20:56 Mon 30 Jul , Moritz Molle wrote: > Package: tgt-glusterfs > Version: 1:1.0.69-1 > Severity: grave Downgrading severity to important. Although this bug makes the package unusable for this particular scenario, it does not do so in general. > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > with a relatively simple setup: > > local glusterfs, with a replica 2 volume, I tried to use tgtd with glfs. My > tgt config was like so: > > > vendor_id xx > bs-type glfs > bsopts "logfile=/var/log/bs-glfs.log;loglevel=3" > write-cache off > initiator-address 10.10.8.0/24 > backing-store "gv_b_0@127.0.0.1:/iSCSI_VOL1.img" > backing-store "gv_b_0@127.0.0.1:/iSCSI_VOL2.img" > controller_tid=10 > > > ... > > /var/log/daemon.log gives me this endlessly > Jul 30 20:28:55 storage-b-02 tgtd[30479]: tgtd: abort_task_set(1349) found > 38ec 0 > Jul 30 20:28:55 storage-b-02 tgtd[30479]: tgtd: abort_cmd(1325) found 38ec 6 > Jul 30 20:29:05 storage-b-02 tgtd[30479]: tgtd: abort_task_set(1349) found > 38ec 0 > Jul 30 20:29:05 storage-b-02 tgtd[30479]: tgtd: abort_cmd(1325) found 38ec 6 > > /var/log/messages contains this > Jul 30 20:34:17 storage-b-02 kernel: [436035.821673] tgtd[31394]: segfault at > 220 ip 7f6944b24dcb sp 7fffdf64f800 error 4 in > libgfapi.so.0.0.0[7f6944b1d000+25000] > Jul 30 20:37:39 storage-b-02 kernel: [436237.496969] tgtd[31627]: segfault at > 220 ip 7f370a520dcb sp 7ffd3c51e5c0 error 4 in > libgfapi.so.0.0.0[7f370a519000+25000] > > I don't know, if it's related to the Volume-Files being 10T big, but it > shouldn't, I think. > Unfortunately these messages don't help much. FWIW this could also be a bug in glusterfs code. Any chance you can give it a try with the version from unstable? Could you also try to obtain a core dump or a backtrace using gdb and the tgt-dbgsym and glusterfs-common-dbgsym packages? Thanks, Apollon
Bug#913363: RFS: desktopfolder/1.0.10-1 [ITP]
Hi Herbert, many thanks for your advice. I followed the instructions in uscan - imported the upstream maintainers public key and then exported the minimal signing key. I've rebuilt the package, confirmed that uscan downloads with the minimal signing key and then built on buster. Running linitian -i -I on the built changes file no longer reports the wishlist public-upstream-key-not-minimal David On Fri, 7 Dec 2018 at 10:10, foss.freedom wrote: > > It has been about a month since the initial package was uploaded to > mentors. Still hoping for some feedback please. > > Yesterday I've tweaked the package to remove an unnecessary > build-dependency after discussing with upstream. > > I note one new "Information" lintian issue now occurs since the > initial upload. Probably due to a slight tweak to the current debian > policy? > > public-upstream-key-not-minimal > upstream/signing-key.asc has 1 extra signature(s) for keyid 92DED901DA15CC0D > > Is this something I can deal with (if so how?) - or should I ask > upstream to create a signing-key.asc for me using "gpg --armor > --export --export-options export-minimal,export-clean keyid" > > thanks in advance > > David
Bug#915411: dovecot-core: doveadm crashes with segmentation fault ('batch -A : kick')
Control: tags -1 + upstream confirmed Control: forwarded -1 https://www.dovecot.org/pipermail/dovecot/2018-December/113819.html Hi, On 11:52 Fri 07 Dec , Bernhard Übelacker wrote: > I could reproduce this crash in a minimal stretch amd64 VM > with just dovecot-core installed and default configuration. > > That command crashes also in a similar VM with current > buster/testing version. Thanks to both of you for the information. I have forwarded this bug upstream, it looks like `batch` is set up to work primarily with "version 1" doveadm commands, converting "version 2" commands to 1 under the hood. Apparently `kick` is lacking an allocation function that would allow it to work as a "version 1" command, causing a null pointer dereference on the way there. Regards, Apollon
Bug#915904: feh: Does not store rotate images
Package: feh Version: 3.1-1 Severity: normal Hi, since the update to version 3.1 feh does not store images that are rotated via '<' / '>' keys. Kind regards Andreas. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages feh depends on: ii libc6 2.27-8 ii libcurl4 7.62.0-1 ii libexif12 0.6.21-5 ii libimlib2 1.5.1-1 ii libpng16-16 1.6.34-2 ii libx11-6 2:1.6.7-1 ii libxinerama1 2:1.1.4-1 ii yudit-common 2.9.6-8 Versions of packages feh recommends: ii libjpeg-turbo-progs [libjpeg-progs] 1:1.5.2-2+b1 feh suggests no packages. -- no debconf information
Bug#904418: transition: json-c
hi, i did a rebuild of all reverse dependencies using ratt and submitted bug reports to the packages i found to fail rebuild: bti_034-3: #915839 opensips_2.2.2-3 #904660 ptask_1.0.0-1 #915840 hhvm_3.24.7+dfsg-2: already removed from testing shogun_3.2.0-8: see #912565 captagent_6.1.0.20-3: fails because of #891532 and was already removed from testing newsbeuter_2.9-8: #915841 psensor_1.1.5-1: #915851 u1db_13.10-6.2: #915897 syslog-ng_3.13.2-5: #914246 (i've never followed a transition nor used ratt before, i hope that was the right way to move forward) cheers, Birger
Bug#915903: broctl: reproducible build (usrmerge): embeds path of shell found via PATH
Package: broctl Version: 1.4-1 Severity: normal User: m...@linux.it Usertags: usrmerge Tags: patch Dear Maintainer, The package currently fails to build reproducibly on merged-usr vs non-merged systems. This is because the build systems InstallShellScript macro rewrites shebangs by looking up things via PATH which can lead to picking up unwanted paths (eg. /usr/local/bin/bash). The upstream build system has already identified this problem and provides a configure flag to disable the rewriting: --binary-package Unfortunately it seems dh doesn't use the provided configure script but invokes CMake directly, thus I had to define the "internal" symbol that --binary-package sets: -DBINARY_PACKAGE_MODE=true Please see the attached patch that fixes this bug report. Regards, Andreas Henriksson diff -Nru broctl-1.4/debian/changelog broctl-1.4/debian/changelog --- broctl-1.4/debian/changelog 2015-10-30 23:33:09.0 +0100 +++ broctl-1.4/debian/changelog 2018-12-07 20:21:42.0 +0100 @@ -1,3 +1,11 @@ +broctl (1.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Use --binary-package configure flag to avoid rewriting files +- fixes reproducible build on merged-usr vs non-merged systems + + -- Andreas Henriksson Fri, 07 Dec 2018 20:21:42 +0100 + broctl (1.4-1) unstable; urgency=medium * New upstream version diff -Nru broctl-1.4/debian/rules broctl-1.4/debian/rules --- broctl-1.4/debian/rules 2015-10-30 23:13:44.0 +0100 +++ broctl-1.4/debian/rules 2018-12-07 20:21:42.0 +0100 @@ -11,7 +11,8 @@ override_dh_auto_configure: dh_auto_configure -- \ -DBRO_ETC_INSTALL_DIR=/etc/bro -DBRO_SCRIPT_INSTALL_PATH=/usr/share/bro \ - -DBRO_SPOOL_DIR=/var/spool/bro -DBRO_LOG_DIR=/var/log/bro + -DBRO_SPOOL_DIR=/var/spool/bro -DBRO_LOG_DIR=/var/log/bro \ + -DBINARY_PACKAGING_MODE=true override_dh_install: dh_install --fail-missing
Bug#915880: Acknowledgement (lvm2: Dependency on liblz4-1 causes /sbin binaries to depend on /usr/lib libraries)
FWIW, I tried doing a blank install with the Buster Alpha 3 installer, putting /usr on a separate LVM volume to see if Debian Buster would also be affected of this. It was not - /usr was mounted without any obvious problems during bootup. (This seems to be different from Ubuntu 18.04, but I haven't tried that install myself, only seen others failing with it when /usr was on a separate LVM volume.) So, the severity of this is rightfully "normal". Would you like me to re-route it to the liblz4-1 package instead of lvm2? (I guess the proper fix for this would be to fix the build script for liblz4-1 so that it's build output gets packaged into /lib instead of /usr/lib) On Fri, Dec 7, 2018 at 4:57 PM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 915880: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915880. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > As you requested using X-Debbugs-CC, your message was also forwarded to > per...@gmail.com > (after having been given a Bug report number, if it did not have one). > > Your message has been sent to the package maintainer(s): > Debian LVM Team > > If you wish to submit further information on this problem, please > send it to 915...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 915880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915880 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems
