Bug#943472: launchy: Rename icons cache folder to .weby-icon-cache or similar
Package: launchy Version: 2.5-4 Severity: wishlist Dear Maintainer, would it be possible to patch the package so that the application is storing its icons cache into a hidden directory, instead of ~/weby-icon-cache ? It is a bit distracting when such an obviously temp direcotry is always being recreated in my home dir. The patch should be trivial: just change launchy-2.5/plugins/weby/weby.cpp at line 95, e.g. to ~/.weby-icon-cache. Thank you, Pavel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (840, 'testing'), (740, 'unstable'), (738, 'experimental'), (540, 'proposed-updates'), (540, 'stable'), (500, 'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages launchy depends on: ii libc6 2.29-2 ii libgcc1 1:9.2.1-8 ii libqt4-network 4:4.8.7+dfsg-19 ii libqtcore4 4:4.8.7+dfsg-19 ii libqtgui4 4:4.8.7+dfsg-19 ii libstdc++6 9.2.1-8 ii libx11-62:1.6.8-1 launchy recommends no packages. Versions of packages launchy suggests: ii launchy-plugins 2.5-4 ii launchy-skins2.5-4 -- no debconf information
Bug#943517: boxbackup: FTBFS with test failures
Package: boxbackup Version: 0.13~~git20190527.g039c4a1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, boxbackup/experimental FTBFS in my sid/experimental pbuilder environment on amd64 and i386. This seems to be a recent regression, since earlier builds of that version have succeeded. Unfortunately I can't tell from the buildlog which error is the actual failure and which errors are expected for some tests. Andreas boxbackup_0.13~~git20190527.g039c4a1-2.log.gz Description: application/gzip
Bug#943520: mdadm: Introduce broken state parsing to mdadm
Package: mdadm
Version: 4.1-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Dear Maintainer,
* Currently, mounted raid0/md-linear arrays have no indication/warning when one
or more members are removed or suffer from some non-recoverable error
condition. The mdadm tool shows "clean" state regardless if a member was
removed.
* The patch proposed in this SRU addresses this issue by introducing a new
state "broken", which is analog to "clean" but indicates that array is not in a
good/correct state. The commit, available upstream as 43ebc910 ("mdadm:
Introduce new array state 'broken' for raid0/linear") [0], was extensively
discussed and received a good amount of reviews/analysis by both the current
mdadm maintainer as well as an old maintainer.
* One important note here is that this patch requires a counter-part in the
kernel to be fully functional, which was SRUed in LP: #1847773.
It works fine/transparently without this kernel counter-part though.
In Ubuntu, the attached patch was applied to achieve the following:
* Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)
Thanks for considering the patch.
diff -Nru mdadm-4.1/debian/control mdadm-4.1/debian/control
--- mdadm-4.1/debian/control2019-05-04 23:58:27.0 -0400
+++ mdadm-4.1/debian/control2019-10-13 17:04:34.0 -0400
@@ -1,8 +1,7 @@
Source: mdadm
Section: admin
Priority: optional
-Maintainer: Ubuntu Developers
-XSBC-Original-Maintainer: Debian QA Group
+Maintainer: Debian QA Group
Build-Depends: debhelper (>= 11), po-debconf, groff-base
Standards-Version: 4.3.0
Vcs-Git: https://git.dgit.debian.org/mdadm
diff -Nru
mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
--- mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
1969-12-31 19:00:00.0 -0500
+++ mdadm-4.1/debian/patches/lp-1847924-introduce-new-array-state-broken.patch
2019-10-13 17:04:34.0 -0400
@@ -0,0 +1,159 @@
+Subject: Introduce new array state 'broken' for raid0/linear
+
+Currently if a md raid0/linear array gets one or more members removed while
+being mounted, kernel keeps showing state 'clean' in the 'array_state'
+sysfs attribute. Despite udev signaling the member device is gone, 'mdadm'
+cannot issue the STOP_ARRAY ioctl successfully, given the array is mounted.
+
+Nothing else hints that something is wrong (except that the removed devices
+don't show properly in the output of mdadm 'detail' command). There is no
+other property to be checked, and if user is not performing reads/writes
+to the array, even kernel log is quiet and doesn't give a clue about the
+missing member.
+
+This patch is the mdadm counterpart of kernel new array state 'broken'.
+The 'broken' state mimics the state 'clean' in every aspect, being useful
+only to distinguish if an array has some member missing. All necessary
+paths in mdadm were changed to deal with 'broken' state, and in case the
+tool runs in a kernel that is not updated, it'll work normally, i.e., it
+doesn't require the 'broken' state in order to work.
+Also, this patch changes the way the array state is showed in the 'detail'
+command (for raid0/linear only) - now it takes the 'array_state' sysfs
+attribute into account instead of only rely in the MD_SB_CLEAN flag.
+
+Author: Guilherme G. Piccoli
+Origin: upstream,
+git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cb77f8c598ede2b7efec23f899b1cda44c315195
+Bug-Ubuntu: https://bugs.launchpad.net/bugs/1847924
+Last-Update: 2019-10-13
+---
+ Detail.c | 14 --
+ Monitor.c | 8 ++--
+ maps.c| 1 +
+ mdadm.h | 1 +
+ mdmon.h | 2 +-
+ monitor.c | 4 ++--
+ 6 files changed, 23 insertions(+), 7 deletions(-)
+
+diff --git a/Detail.c b/Detail.c
+index b3e857a..d24f334 100644
+--- a/Detail.c
b/Detail.c
+@@ -81,6 +81,7 @@ int Detail(char *dev, struct context *c)
+ int external;
+ int inactive;
+ int is_container = 0;
++ char *arrayst;
+
+ if (fd < 0) {
+ pr_err("cannot open %s: %s\n",
+@@ -485,9 +486,18 @@ int Detail(char *dev, struct context *c)
+ else
+ st = ", degraded";
+
++ if (array.state & (1 << MD_SB_CLEAN)) {
++ if ((array.level == 0) ||
++ (array.level == LEVEL_LINEAR))
++ arrayst = map_num(sysfs_array_states,
++sra->array_state);
++ else
++ arrayst = "clean";
++ } else
++ arrayst = "active";
++
+ printf(" State : %s%s%s%s%s%s \n",
+- (array.state & (1 << MD_
Bug#943472: launchy: Rename icons cache folder to .weby-icon-cache or similar
Hi Pavel, Just FYI, The package launchy has been removed from Debian Testing/Sid due to the lack of maintenance and the inactivity of upstream. As a result, this bug is unlikely to be solved unless someone steps in and reintroduce launchy into Debian. The current old version in Debian stable will be left untouched. Best, Boyuan Yang 在 2019-10-25五的 11:01 +0200，Pavel Reznicek写道： > Package: launchy > Version: 2.5-4 > Severity: wishlist > > Dear Maintainer, > > would it be possible to patch the package so that the application is > storing its icons cache into a hidden directory, instead of ~/weby-icon- > cache ? It is a bit distracting when such an obviously temp direcotry is > always being recreated in my home dir. The patch should be trivial: just > change launchy-2.5/plugins/weby/weby.cpp at line 95, e.g. to ~/.weby-icon- > cache. > > Thank you, > Pavel > > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (840, 'testing'), (740, 'unstable'), (738, 'experimental'), > (540, 'proposed-updates'), (540, 'stable'), (500, 'oldstable-proposed- > updates'), (500, 'oldoldstable'), (500, 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: > LC_ALL set to en_US.UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages launchy depends on: > ii libc6 2.29-2 > ii libgcc1 1:9.2.1-8 > ii libqt4-network 4:4.8.7+dfsg-19 > ii libqtcore4 4:4.8.7+dfsg-19 > ii libqtgui4 4:4.8.7+dfsg-19 > ii libstdc++6 9.2.1-8 > ii libx11-62:1.6.8-1 > > launchy recommends no packages. > > Versions of packages launchy suggests: > ii launchy-plugins 2.5-4 > ii launchy-skins2.5-4 > > -- no debconf information > signature.asc Description: This is a digitally signed message part
debian-qa-packages@lists.debian.org
Source: xpdf Version: 3.04-13exp2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) xpdf/experimental FTBFS on all architectures: https://buildd.debian.org/status/package.php?p=xpdf&suite=experimental debian/rules build-arch dh build-arch dh_update_autotools_config -a debian/rules override_dh_auto_configure make[1]: Entering directory '/<>' cp goo/gfile.h xpdf/xfile.h sed -e s/GFILE/XFILE/g -i xpdf/xfile.h cp goo/gfile.cc xpdf/xfile.cc sed -e s/GFILE/XFILE/g -i xpdf/xfile.cc cp xpdf/GlobalParams.h xpdf/XPDFParams.h sed -e s/globalParams/xpdfParams/g -e s/GlobalParams/XPDFParams/g \ -e s/GLOBALPARAMS/XPDFPARAMS/g -e s/popplerParams/globalParams/g \ -e s/PopplerParams/GlobalParams/g \ -i xpdf/XPDFParams.h cp xpdf/GlobalParams.cc xpdf/XPDFParams.cc sed -e s/globalParams/xpdfParams/g -e s/GlobalParams/XPDFParams/g \ -e s/GLOBALPARAMS/XPDFPARAMS/g -e s/popplerParams/globalParams/g \ -e s/PopplerParams/GlobalParams/g \ -i xpdf/XPDFParams.cc mkdir -p build cp goo/parseargs.c goo/parseargs.h xpdf/CoreOutputDev.cc xpdf/CoreOutputDev.h xpdf/PDFCore.cc xpdf/PDFCore.h xpdf/XPDFApp.cc xpdf/XPDFApp.h xpdf/XPDFCore.cc xpdf/XPDFCore.h xpdf/XPDFParams.cc xpdf/XPDFParams.h xpdf/XPDFTree.cc xpdf/XPDFTree.h xpdf/XPDFViewer.cc xpdf/XPDFViewer.h xpdf/xfile.cc xpdf/xfile.h xpdf/xpdf.cc xpdf/config.h xpdf/XPDFTreeP.h xpdf/about-text.h xpdf/*.xbm xpdf/xpdfIcon.xpm build sed -E -e s/GString/GooString/g -e s/GMutex/GooMutex/g -e s/GHash/GooHash/g \ -e s/GList/GooList/g -e s/\/\/g \ -e s/GBool/bool/g -e s/gTrue/true/g -e s/gFalse/false/g \ -e 's/deleteGooList\(([^,]+), ([^)]+)\);/deleteGooList<\2> \(\1\);/' \ -i build/* mv build/parseargs.c build/parseargs.cc make[1]: Leaving directory '/<>' debian/rules override_dh_auto_build make[1]: Entering directory '/<>' x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo -I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args -Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H -DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\" -c -o build/CoreOutputDev.o build/CoreOutputDev.cc x86_64-linux-gnu-g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo -I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args -Wfatal-errors -DHAVE_DIRENT_H -DHAVE_PAPER_H -DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\" -c -o build/PDFCore.o build/PDFCore.cc build/PDFCore.cc: In member function 'virtual void PDFCore::displayDest(LinkDest*, double, int, bool)': build/PDFCore.cc:311:37: error: no matching function for call to 'PDFDoc::findPage(Ref&)' topPageA = doc->findPage(pageRef); ^ compilation terminated due to -Wfatal-errors. make[1]: *** [: build/PDFCore.o] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:50: build-arch] Error 2 Andreas
Bug#862300: continuos segfaults debian due systemd paths
since debian 10 path are not in root accoutn and then citadel does not work... citadel server also other must run several other commands and does not found those Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#943531: citadel does not creates socket unix and segfault at startup
Package: citadel-server Version: 917-2+b1 Severity: important Dear Maintainer, * What led up to the situation? installed citadel-suite and does not work since buster, systemd (again) startud does nto really start the service.. * What exactly did you do (or not do) that was effective (or ineffective)? only install citadel * What was the outcome of this action? does not stat, it said segfault and does not create socket. but daemon are running in fisrt place.. the isntallation scripts does not work due the new behaviour of systemd su command and forces me to use sudo.. but agains now start but does not creates socket.. also package creates a user and does not use to start the daemon.. * What outcome did you expect instead? it that question necesary? -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages citadel-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcitadel4917-2 ii libcurl4 7.64.0-4 ii libdb5.3 5.3.28+dfsg1-0.5 ii libexpat1 2.2.6-2 ii libical3 3.0.4-3 ii libldap-2.4-2 2.4.47+dfsg-3 ii libpam0g 1.3.1-5 ii libsieve2-12.2.6-2 ii libssl1.1 1.1.1c-1 ii lsb-base 10.2019051400 ii openssl1.1.1c-1 ii patch 2.7.6-3+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages citadel-server recommends: pn db4.6-util ii shared-mime-info 1.10-1 citadel-server suggests no packages. -- Configuration Files: /etc/citadel/public_clients changed [not included] /etc/init.d/citadel changed [not included] -- debconf information: * citadel/Password: (password omitted) * citadel/Password_again: (password omitted) citadel/BadUser: citadel/LDAPBaseDN: dc=example,dc=com citadel/LDAPBindDN: * citadel/ServerIPAddress: 0.0.0.0 citadel/LDAPServer: 0.0.0.0 * citadel/LoginType: Internal citadel/LDAPBindDNPassword: OpenSesame * citadel/Administrator: citaroot citadel/LDAPServerPort: 389 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
