Bug#1036424: sylpheed: replying to an email you sent doesn't set account accordingly

[Hideki Yamane]

control: tags -1 +unreproducible

Hi,

 As I wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036388,
 please describe your environment and reproducible way step by step.


-- 
Hideki Yamane 

Bug#1036388: sylpheed: account unadvertingly and unwantingly changed when email is received

[Hideki Yamane]

Hi,

 Please describe reproduce way step by step, and describe your environment
 at detail. I cannot see such issue until now.


On Sat, 20 May 2023 12:00:16 +0200 =?ISO-8859-1?Q?Jos=E9?= Luis 
=?ISO-8859-1?Q?Gonz=E1lez?=  wrote:
> If a new mail arrives to an account other than the current one it is
> changed without permission nor warning to the one receiving the email,
> which means all activity from then on is done unadvertingly on the
> switched-to account.
> 
> Considering the consequences of sending email from an account different
> from the one intended, like sending from a private one to a public
> forum (like a mailing list available on the web, or the DBTS), or using
> an account that is not permitted for what was unwantedly done, this
> makes the package mostly unusable since the consequences of can't be
> usually undone and can be very grave, which renders the program
> unusable for any serious user.
> 
> 



-- 
Hideki Yamane 

Bug#1033833: unknown-horizons: Fails to start Couldn't open

[Hideki Yamane]

 content/fonts/Unifont.ttf
Message-Id: <20230404093247.b65a8493b462bfa1d06d3...@iijmio-mail.jp>
In-Reply-To: 
X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit

Hi Tobias,

On Mon, 3 Apr 2023 19:29:24 +0200 Tobias Frost  wrote:
> thanks for your feedback and the hint to look into otf.
> It seems that the fife engine of unknown-horizons can read otf fonts as well,
> so redirecting the symlink to that version works \o/

 Good! :)


> PS: Long description of the fonts-unifont package is still mentioning 
> truetype fonts$B!D(B
> Maybe that needs s/truetype/opentype/ ?

 Ouch, now fixed it in git... will be updated as package with
 unifont 16.0 release.
 
 Thanks!


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#1033833: unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf

[Hideki Yamane]

On Sun, 2 Apr 2023 18:33:34 +0200
Tobias Frost  wrote:
> it seems so that the fonts package unifont dropped unifont.ttf in
> 1:15.0.01-1:

 Yes, and upstream plans to drop ttf. So I do not want to revert
 this change in Debian package.

> Unifont 15.0.01 installs OpenType fonts alongside the TrueType fonts
> that are installed in Unifont 14.0.x and previous releases.
> The current plan is for Unifont 16.0.01 to no longer install TrueType
> fonts that have OpenType equivalents. This will allow a period of
> approximately one year for Unifont users to switch from TrueType to
> OpenType files. 


-- 
Hideki Yamane 

Bug#1032884: Acknowledgement (amanda-client: Amanda is unusable)

[Hideki Yamane]

control: tags -1 +pending


On Wed, 15 Mar 2023 18:39:47 + Jose M Calhariz  wrote:
> Thank you, your problem is known and will be fixed on the next upload.

-- 
Hideki Yamane 

Bug#987008: grub2: diff for NMU version 2.06-8.1

[Hideki Yamane]

Control: tags -1 +pending

Hi from RC bugs digger,

 It's better to show this issue is going to be solved, add "pending"
 is good to avoid duplicate efforts :)


-- 
Hideki Yamane 

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

[Hideki Yamane]

On Thu, 2 Mar 2023 09:42:36 +
Simon McVittie  wrote:
> Is there consensus among Japanese-speaking users of Debian that mozc is
> a better default for all Japanese speakers, including new users who are
> not familiar with GNOME or Debian?

 anthy vs mozc : mozc is better to default now

 - As a user, I prefer mozc than anthy. When I used anthy on Debian long
   ago, its hiragana-kanji conversion quality did not satisfy me, lower
   than IM on Windows. However, mozc is good - almost same quality as Google
   Japanese Input Method on Windows since its code base is same one.

 - Upsteam: anthy development is not active, almost dead since years.
   Original author says "This is unmaintained ancient stuff and not for
   general use." in his repo [1] and now I found some other staff tries to
   restart it as anthy-unicode [2]
 
   While mozc is still alive [3]. mozc did not accept patches from outside
   of Google in early days, but it seems that they relax their policies [4].

 
 1) https://github.com/yt76/anthy/blob/master/README
 2) https://github.com/fujiwarat/anthy-unicode
 3) https://github.com/google/mozc/commits/master
 4) https://github.com/google/mozc/blob/master/PULL_REQUEST_TEMPLATE.md



> Looking at #984875 and #983653, I also see a mention of mozc only being
> available on certain architectures: it's available on x86, ARM and riscv64,
> but not on mips*el, ppc64el or s390x.

 Well, it's better to be on every archs, but we can ignore them since
 nearly 100% Japanese desktop users use it on i386, amd64 and arm[hf|64].


> I'm also concerned that mozc still depends on GTK 2 (a switch to GTK
> 3 was tried and then reverted, see #967641). This is OK for bookworm,
> but will probably not be supportable in Debian 13.

 It should be reported to mozc upstream, they don't aware of it now, I guess.


> > Upstream prefers ibus-anthy for Japanese input
> 
> Please talk to upstream about this: if mozc is a better default for Debian,
> then it's probably also a better default for upstream.

 Okay, I'll do.



-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#1027628: snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token

[Hideki Yamane]

control: tags -1 +confirmed
control: tags -1 +forwarded https://github.com/openSUSE/snapper/issues/762
control: tags -1 +upstream

 It was introduced with a change in libbtrfs-dev_6.1-1, 
 /usr/include/btrfs/kerncompat.h.
 
https://github.com/kdave/btrfs-progs/commit/788a71c16a917f8357784571106537a1d42012e8

> typedef struct wait_queue_head_s {
> } wait_queue_head_t;
> 
> #define __init
> #define __cold
> 
> #endif

 Just commented out "#define __init", it can be compiled.
 

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#984102: > libfm-qt: ftbfs with GCC-11

[Hideki Yamane]

 As 0.16.0-3.2 changelog, it seems to be okay to close this bug

> libfm-qt (0.16.0-3.2) unstable; urgency=high
> .
>   * Non-maintainer upload.
>   * debian/*.symbols*: Dropped, unmaintainable for c++ library.

 Could you check it, please?

-- 
Hideki Yamane 

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

Hi,

 I've restructured openscap pacakge to fix Bug#990183 and make it
 better, upload to https://salsa.debian.org/henrich/openscap

 I'll upload it to experimental with delay-10, if you want to cancel
 it, don't hestitate.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#990412: pam: Regression - it won't search /lib/security

[Hideki Yamane]

Hi Sam,

On Tue, 06 Jul 2021 08:46:30 -0600 Sam Hartman  wrote:
> This many years after multiarch, I think it is entirely reasonable for
> PAM to drop support for non-multiarch paths at the transition between
> buster and bullseye.

 It was NOT raised as a goal of bullseye for libpam-* packages those
 are not multiarch-ed, IMO. And at this time, last minutes for release,
 we should ensure "it works" as previously to deliver values for users.
 Breaking several libpam-* packages is not.

 Is there any *strong* reason to not deffer make libpam-* packages multiarch-ed
 to bookworm release?


> I think Steve is quite familiar with multiarch and while he hasn't
> commented yet I'm assuming he dropped those patch lines as part of
> removing unnecessary upstream deltas.

 I want his comment, too. git log in his repo just says "refresh
 patches" for this change, and 
debian/patches-applied/lib_security_multiarch_compat
 is the patch for non-multiarch pam modules and still remains. If it
 was intended, it should be removed, I suppose.


> I think you failed to read my comments in the 990412 bug log before
> Merging and reassigning.
 
 Okay, will read again. Thanks!


-- 
Hideki Yamane 

Bug#990412: pam: Regression - it won't search /lib/security

[Hideki Yamane]

control: tags -1 +patch +pending

Hi,

 I've found the root cause of this bug, and fixed it.
 On my local sid machine, I've tested it with edit /etc/pam.d/su
 as search pam_yubico.so, exec su and it searchs /lib/security/pam_yubico.so :)

 See below debdiff. If it seems to be okay, I'll put it into sid
 and request unblock.

diff -Nru pam-1.4.0/debian/changelog pam-1.4.0/debian/changelog
--- pam-1.4.0/debian/changelog  2021-03-16 04:01:55.0 +0900
+++ pam-1.4.0/debian/changelog  2021-07-06 22:09:15.0 +0900
@@ -1,3 +1,13 @@
+pam (1.4.0-7.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * debian/patches-applied/lib_security_multiarch_compat
+- Fix regression that was introduced in 1.4.0-1, some lines were not
+  applied during refresh patch and it doesn't work.
+  (Closes: #979973, #990412)
+
+ -- Hideki Yamane   Tue, 06 Jul 2021 22:09:15 +0900
+
 pam (1.4.0-7) unstable; urgency=medium
 
   * Updated portuguese debconf translation, thanks Pedro Ribeiro, Closes:
diff -Nru pam-1.4.0/debian/patches-applied/lib_security_multiarch_compat 
pam-1.4.0/debian/patches-applied/lib_security_multiarch_compat
--- pam-1.4.0/debian/patches-applied/lib_security_multiarch_compat  
2021-01-31 07:09:52.0 +0900
+++ pam-1.4.0/debian/patches-applied/lib_security_multiarch_compat  
2021-07-06 22:09:15.0 +0900
@@ -11,11 +11,11 @@
 order to get everything installed where we want it and get absolute paths
 the way we want them.
 
-Index: pam/libpam/pam_handlers.c
+Index: pam-1.4.0/libpam/pam_handlers.c
 ===
 pam.orig/libpam/pam_handlers.c
-+++ pam/libpam/pam_handlers.c
-@@ -735,7 +735,18 @@
+--- pam-1.4.0.orig/libpam/pam_handlers.c
 pam-1.4.0/libpam/pam_handlers.c
+@@ -735,7 +735,27 @@ _pam_load_module(pam_handle_t *pamh, con
success = PAM_ABORT;
  
D(("_pam_load_module: _pam_dlopen(%s)", mod_path));
@@ -31,11 +31,20 @@
 +  } else {
 +  pam_syslog(pamh, LOG_CRIT, "cannot malloc full mod path");
 +  }
++   if (!mod->dl_handle) {
++   if (asprintf(_full_path, "%s/%s",
++_PAM_ISA, mod_path) >= 0) {
++   mod->dl_handle = _pam_dlopen(mod_full_path);
++   _pam_drop(mod_full_path);
++   } else {
++   pam_syslog(pamh, LOG_CRIT, "cannot malloc full mod path");
++   }
++  }
 +  }
D(("_pam_load_module: _pam_dlopen'ed"));
D(("_pam_load_module: dlopen'ed"));
if (mod->dl_handle == NULL) {
-@@ -812,7 +823,6 @@
+@@ -812,7 +832,6 @@ int _pam_add_handler(pam_handle_t *pamh
  struct handler **handler_p2;
  struct handlers *the_handlers;
  const char *sym, *sym2;
@@ -43,7 +52,7 @@
  servicefn func, func2;
  int mod_type = PAM_MT_FAULTY_MOD;
  
-@@ -824,16 +834,7 @@
+@@ -824,16 +843,7 @@ int _pam_add_handler(pam_handle_t *pamh
  
  if ((handler_type == PAM_HT_MODULE || handler_type == 
PAM_HT_SILENT_MODULE) &&
mod_path != NULL) {

Bug#990263: podman sets oom_score_adj to -1000 for processes inside the

[Hideki Yamane]

control: severity -1 normal
control: reassign -1 conmon
control: tags -1 +patch +upstream

On Thu, 01 Jul 2021 08:29:07 +0200 Max Bruckner  wrote:
> I just found the bug and the fix! It's not in podman but in conmon!
> 
> See https://github.com/containers/conmon/releases/tag/v2.0.29 and
> https://github.com/containers/conmon/commit/b033cb5dfde6de05e63408fc839f1bb641cddd85

 Great :)


> Yes, when running as normal user it just doesn't have the permissions to set 
> negative OOM score adjustments, that's why
> it's 0.

 Aha, I got it.


> Probably because it's the conmon version that matters. I can reproduce it on 
> Archlinux as well by downgrading conmon to
> 2.0.28

 Let's reassign this bug to conmon, then (as above control header).


> I'm new to debian bug reports and only saw the "breaks the whole system" 
> criterium in the list that "reportbug" printed.
> So feel free to downgrade. Not sure if I have the permission to do so as the 
> bug reporter, but if so I don't even know
> how to.

 Thanks, I did. If you would have a chance to do so, please check above
 of this mail :)


-- 
Hideki Yamane 

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

On Sat, 3 Jul 2021 21:36:53 +0900
Hideki Yamane  wrote:
>  Mostly done, still have an error with autopkgtest for python3-openscap

 Updated. Passed all salsa-ci test as below, and eliminate most of
 lintian warning/info.
 https://salsa.debian.org/henrich/openscap/-/pipelines/265972


diff -Nru openscap-1.3.4/debian/changelog openscap-1.3.4/debian/changelog
--- openscap-1.3.4/debian/changelog 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/changelog 2021-06-30 16:33:53.0 +0900
@@ -1,3 +1,37 @@
+openscap (1.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+  * Package structure changes
+- Apply soname change (libopenscap8 -> 25)
+- Split libopenscap25 to openscap-scanner, openscap-utils and
+  openscap-common
+- Drop -dbg package and unnecessary lintian-overrides
+  * debian/control
+- Specify https for upstream URL
+- Use debhelper-compat (= 13) to not forget to install necessary files
+  with dh_missing
+- Add missing dependencies: libacl1-dev, libblkid-dev, libglib2.0-dev,
+  libyaml-dev, librpm-dev, libpopt-dev, libprocps-dev, libopendbx1-dev,
+  libxmlsec1-dev, doxygen, graphviz, asciidoc,
+  * Drop unnecessary debian/compat
+  * debian/rules
+- Enable documentation build
+- Enable hardening
+  * Add openscap-common.docs to install HTML docs
+  * debian/openscap-scanner.install
+- Install bash-completion
+  * openscap-utils.install
+- Install autotailor and scap-as-rpm
+  * Add debian/openscap-{scanner,utils}.manpages
+
+  * Trim trailing whitespace.
+  * Update watch file format version to 4.
+  * Set upstream metadata fields: Bug-Database, Bug-Submit.
+  * Drop unnecessary dependency on dh-autoreconf.
+
+ -- Hideki Yamane   Wed, 30 Jun 2021 16:33:53 +0900
+
 openscap (1.3.4-1) unstable; urgency=medium
 
   * New upstream version 1.3.4
diff -Nru openscap-1.3.4/debian/compat openscap-1.3.4/debian/compat
--- openscap-1.3.4/debian/compat2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/compat1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -Nru openscap-1.3.4/debian/control openscap-1.3.4/debian/control
--- openscap-1.3.4/debian/control   2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/control   2021-06-30 16:33:53.0 +0900
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Pierre Chifflier 
 Uploaders: Philippe Thierry 
-Build-Depends: debhelper (>= 13),
+Build-Depends: debhelper-compat (= 13),
 cmake,
 libpcre3-dev,
 libxml2-dev,
@@ -18,19 +18,30 @@
 libattr1-dev,
 libldap2-dev,
 libbz2-dev,
+libacl1-dev,
+libblkid-dev,
+libglib2.0-dev,
+libyaml-dev,
+librpm-dev,
+libpopt-dev,
+libprocps-dev,
+libopendbx1-dev,
+libxmlsec1-dev,
+doxygen, graphviz,
+asciidoc,
 pkg-config,
 dh-python,
 chrpath,
 libdbus-1-dev
+Section: admin
 X-Python3-Version: >= 3.9
 Standards-Version: 4.5.1
-Section: libs
-Homepage: http://www.open-scap.org/
+Homepage: https://www.open-scap.org/
 
 Package: libopenscap-dev
 Section: libdevel
 Architecture: linux-any
-Depends: libopenscap8 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
+Depends: libopenscap25 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -48,13 +59,13 @@
  .
  This package contains the development files for OpenSCAP.
 
-Package: libopenscap8
+Package: libopenscap25
 Section: libs
 Architecture: linux-any
-Conflicts: libopenscap0, libopenscap1, libopenscap3
-Replaces: libopenscap0, libopenscap1, libopenscap3
+Conflicts: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
+Replaces: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends},
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -69,11 +80,13 @@
   * Common Vulnerability Scoring System (CVSS)
   * Extensible Configuration Checklist Description Format (XCCDF)
   * Open Vulnerability and Assessment Language (OVAL)
+ .
+ This package contains libraries for OpenSCAP.
 
 Package: python3-openscap
 Section: python
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap8 
(= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap25 
(= ${binary:Version})
 X-Python3-Version: ${python3:Versions}
 Provides: ${python3:Provides}
 Description: Set of libraries enabling integration of t

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

On Fri, 2 Jul 2021 00:43:02 +0200
Sebastian Ramacher  wrote:
> Yes, but note that this needs to happen soon as it has to pass NEW.

 Mostly done, still have an error with autopkgtest for python3-openscap
 https://salsa.debian.org/henrich/openscap/-/pipelines/265919
 (It doesn't have git repo, so I pushed it under my user at salsa).

 It includes fixes a *lot* (sorry at this freeze time, but...), if it should
 be shrunk, we can rebase it.

diff -Nru openscap-1.3.4/debian/changelog openscap-1.3.4/debian/changelog
--- openscap-1.3.4/debian/changelog 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/changelog 2021-06-30 16:33:53.0 +0900
@@ -1,3 +1,37 @@
+openscap (1.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+  * Package structure changes
+- Apply soname change (libopenscap8 -> 25)
+- Split libopenscap25 to openscap-scanner, openscap-utils and
+  openscap-common
+- Drop -dbg package and unnecessary lintian-overrides
+  * debian/control
+- Specify https for upstream URL
+- Use debhelper-compat (= 13) to not forget to install necessary files
+  with dh_missing
+- Add missing dependencies: libacl1-dev, libblkid-dev, libglib2.0-dev,
+  libyaml-dev, librpm-dev, libpopt-dev, libprocps-dev, libopendbx1-dev,
+  libxmlsec1-dev, doxygen, graphviz, asciidoc,
+  * Drop unnecessary debian/compat
+  * debian/rules
+- Enable documantation build
+- Enable hardening
+  * Add openscap-common.docs to install HTML docs
+  * debian/openscap-scanner.install
+- Install bash-completion
+  * openscap-utils.install
+- Install autotailor and scap-as-rpm
+  * Add debian/openscap-{scanner,utils}.manpages
+
+  * Trim trailing whitespace.
+  * Update watch file format version to 4.
+  * Set upstream metadata fields: Bug-Database, Bug-Submit.
+  * Drop unnecessary dependency on dh-autoreconf.
+
+ -- Hideki Yamane   Wed, 30 Jun 2021 16:33:53 +0900
+
 openscap (1.3.4-1) unstable; urgency=medium
 
   * New upstream version 1.3.4
diff -Nru openscap-1.3.4/debian/compat openscap-1.3.4/debian/compat
--- openscap-1.3.4/debian/compat2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/compat1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -Nru openscap-1.3.4/debian/control openscap-1.3.4/debian/control
--- openscap-1.3.4/debian/control   2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/control   2021-06-30 16:33:53.0 +0900
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Pierre Chifflier 
 Uploaders: Philippe Thierry 
-Build-Depends: debhelper (>= 13),
+Build-Depends: debhelper-compat (= 13),
 cmake,
 libpcre3-dev,
 libxml2-dev,
@@ -18,19 +18,30 @@
 libattr1-dev,
 libldap2-dev,
 libbz2-dev,
+libacl1-dev,
+libblkid-dev,
+libglib2.0-dev,
+libyaml-dev,
+librpm-dev,
+libpopt-dev,
+libprocps-dev,
+libopendbx1-dev,
+libxmlsec1-dev,
+doxygen, graphviz,
+asciidoc,
 pkg-config,
 dh-python,
 chrpath,
 libdbus-1-dev
+Section: admin
 X-Python3-Version: >= 3.9
 Standards-Version: 4.5.1
-Section: libs
-Homepage: http://www.open-scap.org/
+Homepage: https://www.open-scap.org/
 
 Package: libopenscap-dev
 Section: libdevel
 Architecture: linux-any
-Depends: libopenscap8 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
+Depends: libopenscap25 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -48,13 +59,13 @@
  .
  This package contains the development files for OpenSCAP.
 
-Package: libopenscap8
+Package: libopenscap25
 Section: libs
 Architecture: linux-any
-Conflicts: libopenscap0, libopenscap1, libopenscap3
-Replaces: libopenscap0, libopenscap1, libopenscap3
+Conflicts: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
+Replaces: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends},
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -69,11 +80,13 @@
   * Common Vulnerability Scoring System (CVSS)
   * Extensible Configuration Checklist Description Format (XCCDF)
   * Open Vulnerability and Assessment Language (OVAL)
+ .
+ This package contains libraries for OpenSCAP.
 
 Package: python3-openscap
 Section: python
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap8 
(= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, l

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

On Fri, 2 Jul 2021 00:43:02 +0200
Sebastian Ramacher  wrote:
> Yes, but note that this needs to happen soon as it has to pass NEW.

 Thanks, I'll try it.

-- 
Hideki Yamane 

Bug#989799: psmisc: Undeclared file conflict with manpages-de

[Hideki Yamane]

Hi Helge,

On Fri, 2 Jul 2021 10:29:53 +0900
Hideki Yamane  wrote:
>  We can close it via mail, but should investigate its reason, IMO.

 Note it as https://bugs.debian.org/990557
 Let's close Bug#989799 via hand.


-- 
Hideki Yamane 

Bug#989799: psmisc: Undeclared file conflict with manpages-de

[Hideki Yamane]

On Thu, 1 Jul 2021 21:07:03 +0200
Helge Kreutzmann  wrote:
> It now has. So this bug is closed, if users upgrade to the latestes
> backport version.

 Hmm, however, this bug is not closed automatically. Weird.
 
https://tracker.debian.org/news/1243791/accepted-manpages-l10n-4100-1bpo101-source-into-buster-backports-backports-policy-buster-backports/

 We can close it via mail, but should investigate its reason, IMO.
 

-- 
Hideki Yamane 

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

Hi,

On Tue, 22 Jun 2021 11:23:51 +0200 Sebastian Ramacher  
wrote:
> 1.3.4-1 would have needed to rename the package to libopenscap25 and
> start a library transition. The library package also contains a bunch of
> binaries and other files that do not look like the should be part of a
> library package. In any case, raising the severity to serious is the
> current packaging of the library is broken.

 Can we have a chance to put splitted packages (openscap-scanner as tools
 binary as other distros do and openscap-common for /usr/share files) for
 bullseye release? If so, I'll try to do so.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#989799: psmisc: Undeclared file conflict with manpages-de

[Hideki Yamane]

 from buster-backports
Message-Id: <20210630134637.d8e6f92027ef11aeb9a09...@iijmio-mail.jp>
In-Reply-To: <20210627060424.GA7522@Debian-50-lenny-64-minimal>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sun, 27 Jun 2021 08:04:24 +0200 Helge Kreutzmann  
wrote:
> manpages-l10n (4.10.0-1~bpo10+1) buster-backports; urgency=medium
> 
>   * Rebuild for buster-backports.
>   * Properly conflict with future versions of psmisc and procps so that
> upgrades to bullseye will work without file conflicts. Closes: #989799
> 
>  -- Helge Kreutzmann   Sun, 20 Jun 2021 10:27:10 +0200
> 
> Also tracker.debian.org does not show (yet), that it has been accepted.

 Have it reached to buster-backports repo?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#990263: podman sets oom_score_adj to -1000 for processes inside the

[Hideki Yamane]

 container so the system breaks in OOM situations
Message-Id: <20210629000848.a3125fe89a9984a780074...@iijmio-mail.jp>
In-Reply-To: <502056d5848360369973f2c96882ff37ad42bb4f.ca...@doo.shop>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi,

On Thu, 24 Jun 2021 11:37:35 +0200 Max Bruckner  wrote:
> How to reproduce:
> 
> ```
> # podman run -it --rm debian sh
> # cat /proc/$$/oom_score_adj
> -1000
> ```

 Well, I've tested it too with bullseye on KVM and reproduced it, however,
 it's only under root privilege. Just run "$ podman run -it --rm debian sh"
 via normal user and it returns 0.

 And also tested with my daily driver unstable system I cannot reproduce it.
 (But sid on KVM can reproduce it, hmm...)


 It may be better to downgrade as important if it's only root privilege, IMO.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#982794: firefox-esr: illegal instruction in libxul.so on armhf

[Hideki Yamane]

Hi,

On Sun, 14 Feb 2021 14:12:17 + Vincent Arkesteijn  
wrote:
> Firefox is killed with SIGILL shortly after startup:
> $ firefox-esr -safe-mode
> Illegal instruction

 Can you reproduce it on freshly installed bullseye sytem?

> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: armhf (armv7l)

 However,

> Kernel: Linux 3.5.7-14-ARCH (PREEMPT)

 It seems that is not the kernel bullseye provides.


 And it maybe help to provide its hardware information, too.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#934713: os-prober: missing dependency on mount

[Hideki Yamane]

control: tags -1 +patch

On Thu, 15 Aug 2019 16:49:46 +0200 Johannes Schauer  wrote:
> > > https://lists.debian.org/20170726081846.ga22...@fatal.se
> > 
> > Well, debian-devel@ isn't where one files bug reports against packages that
> > suddenly need a dependency?
> 
> I was not trying to justify or excuse the omission of the src:util-linux
> maintainers. I can only imagine that os-prober somehow slipped through the
> cracks when the src:util-linux maintainers filed bugs against all packages 
> that
> need the mount utilities during the buster release cycle.
> 
> I agree that the situation now is unfortunate but I only reported this problem
> once I stumbled across it. I was not involved in the decision two years ago.

 Anyway, here's a tiny MR
 https://salsa.debian.org/installer-team/os-prober/-/merge_requests/9


 If it would be a wrong way to deal with this bug, then close above MR
 and remove Tags: patch, please. If not - just merge it and push the package :D


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#981054: openipmi: Missing dependency on kmod

[Hideki Yamane]

control: severity -1 wishlist

Hi,

On Mon, 25 Jan 2021 19:14:08 + =?utf-8?q?Ville_Skytt=C3=A4?= 
 wrote:
> /etc/init.d/openipmi invokes /sbin/lsmod, but nothing in the package's
> dependency chain pulls it in. I suppose adding dependency on kmod is
> in order.

 As debian/openipmi.init
 https://sources.debian.org/src/openipmi/2.0.29-0.1/debian/openipmi.init/

> unload_all_ipmi_modules()
> {
(snip)
> # delete interface node ONLY if ipmi_devintf is unloaded
> [ `lsmod | grep -c "ipmi_devintf"` -eq 0 ] &&
>   rm -f "/dev/ipmi${INTF_NUM}"
> }
> 
> unload_ipmi_modules_leave_features()
> {
>   for m in ${MODULES_INTERFACES}; do
>   modprobe -q -r ${m} > /dev/null 2>&1
>   done
> # delete interface node ONLY if ipmi_devintf is unloaded
> [ `lsmod | grep -c "ipmi_devintf"` -eq 0 ] &&
>   rm -f "/dev/ipmi${INTF_NUM}"
>   lsmod | egrep -q "ipmi_(poweroff|watchdog)" > /dev/null 2>&1
>   if [ "$?" -ne "0" ]; then
>   stop_watchdog_quiet
>   stop_powercontrol_quiet
>   for m in ${MODULES}; do
>   modprobe -q -r ${m} > /dev/null 2>&1
>   done
>   fi
> }

 It seems that the lack of lsmod does not prevent openipmi to work,
 so just add "Recommends: kmod" is enough, IMHO.

 And it is NOT "serious" problem since it works without kmod except
 two functions and the average environment have kmod package, so
 severity: wishlist is better.

 Here's a MR.
 https://salsa.debian.org/debian/openipmi/-/merge_requests/2

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#989255: qbittorrent-nox web UI fails after qt5 upgrade

[Hideki Yamane]

control: tags -1 +unreproducible
control: severity -1 important

On Sun, 30 May 2021 09:09:27 -0500 allan grossman  wrote:
>  Ran aptitude safe-upgrade this morning which updated qt5 libraries.  
> After reboot, qbittorrent-nox web UI is inaccessible.
>  Tried opening web UI in Chrome and Firefox and both browsers download 
> the page instead of opening it.  Backend works just
>  fine as radarr and sonarr are both communicating with it just fine but 
> web UI is broken.

 I've tested that with those environment but couldn't reproduce it,
 Web UI works fine.

   - sid
   - bullseye on docker
   - fresh install bullseye on KVM

 So, once tags it as unreproducible and downgrade severity.
 

 Could you install qbittorrent-dbg and run it with strace as
 "strace qbittorrent-nox --skipdialog=true" and send debug log,
 please?




-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#988358: bucardo: please use versioned Depends: libpod-parser-perl (>= 1.63)

[Hideki Yamane]

control: tags -1 +patch

Hi,

 Here's a tiny MR for it.
 https://salsa.debian.org/postgresql/bucardo/-/merge_requests/2


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#987461: libuima-adapter-soap-java is empty

[Hideki Yamane]

On Mon, 21 Jun 2021 16:47:49 -0700
tony mancill  wrote:
> My apologies if using Breaks in this way is a common pattern.  I am
> simply not familiar with it.  If you have used the pattern before, I
> will upgrade the package as-is, since your way is cleaner.  Otherwise, I
> will remove the Breaks.

 Not so much common, "Breaks: + Replaces: + Provides:" pattern is the
 common case for package replacement. I cannot remember whether I used
 it before... Please remove Breaks: since ftpmasters would be happy with
 more simple debdiff :)


-- 
Hideki Yamane 

Bug#987461: libuima-adapter-soap-java is empty

[Hideki Yamane]

Hi,

On Mon, 21 Jun 2021 11:52:14 -0700
tony mancill  wrote:
> I saw the note in the changelog that Breaks is in fact there to remove
> the empty package, but it's not happening for me when I try to upgrade
> locally.  My test case is to install uima-utils (which will install
> libuima-adapter-soap-java via Recommends) and then try to upgrade the
> binaries to 2.10.2-4 using dpkg.  

 Well, it would remove libuima-adapter-soap-java if I've tested it
 on chroot env as below.

# apt install /tmp/libuima-core-java_2.10.2-4_all.deb 
(snip)
The following packages will be REMOVED:
  libuima-adapter-soap-java
The following packages will be upgraded:
  libuima-core-java
1 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B/1513 kB of archives.
After this operation, 12.3 kB disk space will be freed.


> The only way I can make this work is remove libuima-adapter-soap-java
> manually.  Are you sure that Breaks is necessary?  apt-get autoremove
> will clean up libuima-adapter-soap-java at some point.

 Okay, libuima-adapter-soap-java is empty now, just manual autoremove
 is fine. 

> I took a look at policy to see if Breaks + Replaces should be used in
> this situation, but I'm not sure it really applies (although I think it
> would work better than just Breaks).  Still, I'm unsure about the need
> for Breaks for this empty package clean-up use case.

 I don't think "Replaces" to be used in this situation since it
 does not provide any fuctions as same as previous one.
 

> Any concerns if I drop the Breaks before the upload?

 None, please go ahead for bullseye :)



-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#989103: pulseaudio crashes on startup

[Hideki Yamane]

control: tags -1 -moreinfo
control: tags -1 -unreproducible
control: tags -1 +patch

Hi,

On Mon, 7 Jun 2021 22:37:11 +0300 Igor Kovalenko  
wrote:
> I confirm this is a regression in pulseaudio-14.0, fixed in pulseaudio
> master now.
> 
> https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/576

 Thank you, let's patch for debian package, then.
 I've attached patches not MR, since some commits were already done
 in master branch.



-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp
>From 7b3a5ada2664e16a44edec2f0abe65f5a12f4fc1 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Mon, 21 Jun 2021 02:32:42 +0900
Subject: [PATCH 2/2] note to changelog

---
 debian/changelog | 9 +
 1 file changed, 9 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index dffa6bc8..5ede7839 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+pulseaudio (14.2-2.1) unstable; urgency=medium
+
+  * NMU.
+  * debian/patches
+- Add: 0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch
+  (Closes: #989103)
+
+ -- Hideki Yamane   Mon, 21 Jun 2021 02:31:10 +0900
+
 pulseaudio (14.2-2) unstable; urgency=medium
 
   * Stop installing the console kit module.
-- 
2.32.0

>From fef59ed6742bdec063267122fdb360826adaed18 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Mon, 21 Jun 2021 02:27:34 +0900
Subject: [PATCH 1/2] Add
 0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch

---
 ...mixer-check-if-mapping-is-NULL-befor.patch | 39 +++
 debian/patches/series |  1 +
 2 files changed, 40 insertions(+)
 create mode 100644 debian/patches/0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch

diff --git a/debian/patches/0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch b/debian/patches/0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch
new file mode 100644
index ..c9f84b66
--- /dev/null
+++ b/debian/patches/0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch
@@ -0,0 +1,39 @@
+From: Hideki Yamane 
+Date: Mon, 21 Jun 2021 02:25:34 +0900
+Subject: Bug#989103 alsa-mixer: check if mapping is NULL before using it
+
+Taken from upstream git, see
+https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/79cb1369fc4d22966cb65253e9da2ccda2f25b45?merge_request_iid=576
+---
+ src/modules/alsa/alsa-sink.c   | 3 ++-
+ src/modules/alsa/alsa-source.c | 3 ++-
+ 2 files changed, 4 insertions(+), 2 deletions(-)
+
+diff --git a/src/modules/alsa/alsa-sink.c b/src/modules/alsa/alsa-sink.c
+index f7fef8a..84cdb15 100644
+--- a/src/modules/alsa/alsa-sink.c
 b/src/modules/alsa/alsa-sink.c
+@@ -2107,7 +2107,8 @@ static void find_mixer(struct userdata *u, pa_alsa_mapping *mapping, const char
+ u->mixers = pa_hashmap_new_full(pa_idxset_string_hash_func, pa_idxset_string_compare_func,
+ NULL, (pa_free_cb_t) pa_alsa_mixer_free);
+ 
+-mdev = pa_proplist_gets(mapping->proplist, "alsa.mixer_device");
++if (mapping)
++mdev = pa_proplist_gets(mapping->proplist, "alsa.mixer_device");
+ if (mdev) {
+ u->mixer_handle = pa_alsa_open_mixer_by_name(u->mixers, mdev, true);
+ } else {
+diff --git a/src/modules/alsa/alsa-source.c b/src/modules/alsa/alsa-source.c
+index 76370f8..083f928 100644
+--- a/src/modules/alsa/alsa-source.c
 b/src/modules/alsa/alsa-source.c
+@@ -1813,7 +1813,8 @@ static void find_mixer(struct userdata *u, pa_alsa_mapping *mapping, const char
+ u->mixers = pa_hashmap_new_full(pa_idxset_string_hash_func, pa_idxset_string_compare_func,
+ NULL, (pa_free_cb_t) pa_alsa_mixer_free);
+ 
+-mdev = pa_proplist_gets(mapping->proplist, "alsa.mixer_device");
++if (mapping)
++mdev = pa_proplist_gets(mapping->proplist, "alsa.mixer_device");
+ if (mdev) {
+ u->mixer_handle = pa_alsa_open_mixer_by_name(u->mixers, mdev, false);
+ } else {
diff --git a/debian/patches/series b/debian/patches/series
index 54c06fdd..fe50543a 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 disable-autospawn.patch
 tests-fix-use-of-uninitialized-variable-cpu_info.patch
+0003-Bug-989103-alsa-mixer-check-if-mapping-is-NULL-befor.patch
-- 
2.32.0

Bug#987461: libuima-adapter-soap-java is empty

[Hideki Yamane]

control: tags -1 +patch

On Sat, 24 Apr 2021 18:40:31 +0200 Chris Hofstaedtler  wrote:
> It appears the change itself was intentional:
> 
> > uimaj (2.10.2-2) unstable; urgency=medium
> > 
> >   * No longer build the uimaj-adapter-soap module
> > 
> >  -- Emmanuel Bourg   Fri, 30 Nov 2018 09:07:17 +0100
> 
> However, the binary package should probably also have been removed.
> 
> Maintainers, please come to a conclusion regarding the now empty binary 
> package.

 Okay, libuima-adapter-soap-java has no reverse dependency.

$ apt-rdepends -r libuima-adapter-soap-java
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libuima-adapter-soap-java


 So let's remove its binary package and add Breaks: to it.
 MR is here, could someone review it, please?
 https://salsa.debian.org/java-team/uimaj/-/merge_requests/1


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#989491: libxstream-java: CVE-2021-29505

[Hideki Yamane]

On Sat, 05 Jun 2021 09:29:20 +0200 Salvatore Bonaccorso  
wrote:
> Source: libxstream-java
> Version: 1.4.15-2

 Let's check it with buster version, then.
 Here's a patch for it, it lacks some blacklist items from current
 unstable version but it should be so if sticks to a minimum.

 Anyway, could you review it, please




libstream-java.debdiff
Description: Binary data

Bug#989080: cifs-utils: Fix for CVE-2021-20208 breaks cifs.upcall

[Hideki Yamane]

control: tags -1 +patch


 Here's MR
 https://salsa.debian.org/samba-team/cifs-utils/-/merge_requests/8

Bug#989080: cifs-utils: Fix for CVE-2021-20208 breaks cifs.upcall

[Hideki Yamane]

Hi,

On Tue, 25 May 2021 16:02:14 +0200 Finn Martin Krein 
 wrote:
> when using cifs-utils to mount a samba share using a krb5 ticket cifs.upcall 
> fails:
> $ mount -t cifs --verbose -o 
> seal,idsfromsid,cifsacl,rw,sec=krb5i,user=finnkrein,cruid=finnkrein 
> //storage.physik.fu-berlin.de/finnkrein /net/test
> mount error(126): Required key not available
> 
> From journalctl -e:
> cifs.upcall[34940]: switch_to_process_ns: setns() failed for cgroup
> cifs.upcall[34940]: unable to switch to process namespace: Operation not>
> cifs.upcall[34940]: Exit status 1
> 
> This bug was likely introduced by the fix for CVE-2021-20208 (#987308), is 
> known upstream and discussed at 
> https://www.spinics.net/lists/linux-cifs/msg21550.html.
> The respective patch is currently included as "0010-CVE-2021-20208.patch". 

 As https://www.spinics.net/lists/linux-cifs/msg21976.html, SUSE engineer
 has already prepared and applied fix for it but not merged into upstream
 yet. So, let's try to build and test it. I'll prepare the packages for it.




-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#989438: CVE-2021-31855

[Hideki Yamane]

control: tags -1 +patch

Merge Request was prepared as
https://salsa.debian.org/qt-kde-team/kde/messagelib/-/commit/30133062524fefeafd0784837d868b603f0797f1



-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#980466: cervisia: missing dependency on kinit package

[Hideki Yamane]

control: tags -1 +confirmed +patch

Hi,

 I'd prepare tiny patch for this issue as below.



diff --git a/debian/changelog b/debian/changelog
index cbd284c..7fde2e5 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cervisia (4:20.12.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix dependency to exec without whole KDE environment (Closes: #980466)
+
+ -- Hideki Yamane   Tue, 15 Jun 2021 01:08:14 +0900
+
 cervisia (4:20.12.0-1) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/control b/debian/control
index 44c6731..9da63c4 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,8 @@ Rules-Requires-Root: no
 Package: cervisia
 Architecture: any
 Section: devel
-Depends: cvsservice (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: cvsservice (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends},
+ kinit,
 Suggests: khelpcenter
 Description: graphical CVS client
  Cervisia is a front-end for the CVS version control system client.

Bug#932501: problem still present in 0.8.15

[Hideki Yamane]

On Tue, 13 Apr 2021 20:13:59 +0200 =?UTF-8?B?SsOpcsOpbXkgVmnDqHM=?= 
 wrote:
> Just to confirm the issue is still present in bullseye current release.
> I had to add the following lines to apparmor configuration to make it work.
> 
>   /etc/squid-deb-proxy/** r,
>   /var/log/squid-deb-proxy/* rw,
>   /run/squid-deb-proxy.pid rwk,
>   /var/cache/squid-deb-proxy/** rw,

 Thank you, put it to debdiff now.


diff -Nru squid-deb-proxy-0.8.15/debian/apparmor-profiles/squid-deb-proxy 
squid-deb-proxy-0.8.15+nmu1/debian/apparmor-profiles/squid-deb-proxy
--- squid-deb-proxy-0.8.15/debian/apparmor-profiles/squid-deb-proxy 
1970-01-01 09:00:00.0 +0900
+++ squid-deb-proxy-0.8.15+nmu1/debian/apparmor-profiles/squid-deb-proxy
2021-06-14 23:38:09.0 +0900
@@ -0,0 +1,6 @@
+# vim:syntax=apparmor
+
+/etc/squid-deb-proxy/** r,
+/var/log/squid-deb-proxy/* rw,
+/run/squid-deb-proxy.pid rwk,
+/var/cache/squid-deb-proxy/** rw,
diff -Nru squid-deb-proxy-0.8.15/debian/changelog 
squid-deb-proxy-0.8.15+nmu1/debian/changelog
--- squid-deb-proxy-0.8.15/debian/changelog 2020-01-19 03:00:55.0 
+0900
+++ squid-deb-proxy-0.8.15+nmu1/debian/changelog2021-06-14 
23:41:11.0 +0900
@@ -1,3 +1,10 @@
+squid-deb-proxy (0.8.15+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add apparmor profiles to work (Closes: #932501)
+
+ -- Hideki Yamane   Mon, 14 Jun 2021 23:41:11 +0900
+
 squid-deb-proxy (0.8.15) unstable; urgency=medium
 
   [ Graham Cantin ]
diff -Nru squid-deb-proxy-0.8.15/debian/squid-deb-proxy.dirs 
squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.dirs
--- squid-deb-proxy-0.8.15/debian/squid-deb-proxy.dirs  2020-01-10 
19:02:40.0 +0900
+++ squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.dirs 2021-06-14 
23:40:40.0 +0900
@@ -1,2 +1,3 @@
 etc/resolvconf/update-libc.d
+etc/apparmor.d/abstractions/squid-deb-proxy
 var/log/squid-deb-proxy
diff -Nru squid-deb-proxy-0.8.15/debian/squid-deb-proxy.install 
squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.install
--- squid-deb-proxy-0.8.15/debian/squid-deb-proxy.install   2020-01-10 
19:02:40.0 +0900
+++ squid-deb-proxy-0.8.15+nmu1/debian/squid-deb-proxy.install  2021-06-14 
23:40:21.0 +0900
@@ -1,3 +1,4 @@
 ../update-libc.d etc/resolvconf/
 etc/squid-deb-proxy
 init-common.sh usr/share/squid-deb-proxy/
+../apparmor-profiles/* etc/apparmor.d/abstractions/squid-deb-proxy/

Bug#968897: src:pylint should provide a pylint3 transitional package

[Hideki Yamane]

control: tags -1 +patch


On Tue, 1 Jun 2021 22:49:18 +0300 Adrian Bunk  wrote:
> Provides is good for fulfilling dependencies, but won't for an upgrade 
> to the renamed package.

 Okay, then add transitional dummy package for it as below.
 If anything goes wrong, I'll upload it to delay-5 queue later.


>From 2e52e9170265d4eb8160f813b07e34aa41b97521 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Mon, 14 Jun 2021 21:51:09 +0900
Subject: [PATCH 1/2] Add Transitional dummy package pylint3 (Closes: #968897)

---
 debian/control | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index a60b507..cca8351 100644
--- a/debian/control
+++ b/debian/control
@@ -58,7 +58,7 @@ Depends: python3-astroid (>= 2.4.0),
 Recommends: python3-tk,
 Suggests: pylint-doc,
   python3-mccabe,
-Breaks: pylint3,
+Breaks: pylint3 (<< 2.7.2-2),
 python3-pylint-django (<< 2.0),
 python3-pylint-plugin-utils (<< 0.4),
 python3-pytest-pylint (<< 0.10),
@@ -83,3 +83,9 @@ Description: Python 3 code static checker and UML diagram 
generator
* pyreverse3: an UML diagram generator
* symilar3: an independent similarities checker
* epylint3: Emacs and Flymake compatible Pylint
+
+Package: pylint3
+Architecture: all
+Depends: pylint
+Description: Transitional dummy package
+ This is transitional dummy package for pylint, you can safely remove it.
-- 
2.32.0


>From 4d18a26c96b9a0b449a01efe198f8aa46ddc046d Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Mon, 14 Jun 2021 22:04:59 +0900
Subject: [PATCH 2/2] note to changelog

---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index bae2d32..37bdddb 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pylint (2.7.2-2) unstable; urgency=medium
+
+  * Team upload
+  * debian/control
+- Introduce pylint3 trantional package for smooth upgrade (Closes: #968897)
+
+ -- Hideki Yamane   Mon, 14 Jun 2021 23:03:38 +0900
+
 pylint (2.7.2-1) unstable; urgency=medium
 
   * New upstream release
-- 
2.32.0

Bug#989554: Add argyll dependency

[Hideki Yamane]

Hi,

On Mon, 07 Jun 2021 13:36:17 + Age Bosma  wrote:
> The colour calibration functionality gnome-control-center will happily start 
> the lengthy process of colour testing, only the fail at the end with the 
> error:
> 
> "Tools required for calibration are not installed"
> 
> This without specifying which tools exactly.
> 
> Installing the argyll package solves the issue.

 It seems that we can pull it via Recommends is enough as below.
 But its git repo is a bit confusing, should I patch it to 3.38.4-1
 in unstable or more updated version 3.38.6-1 in repo?


>From 9eaa7e05e3279637667b5aad6cc2555906c6ae6a Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Mon, 14 Jun 2021 21:38:24 +0900
Subject: [PATCH] Add Recommends: argyll to provide color management feature 
(Closes: #989554)

---
 debian/control.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/control.in b/debian/control.in
index 7c106ecb3..4e02f278a 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -92,6 +92,7 @@ Recommends: cups-pk-helper,
 libnss-myhostname,
 cracklib-runtime,
 pulseaudio-module-bluetooth,
+argyll,
 realmd
 Suggests: gnome-software | gnome-packagekit,
   gstreamer1.0-pulseaudio,
-- 
2.32.0

Bug#982723: ruby-rails-html-sanitizer: FTBFS: ERROR: Test "ruby2.7" failed.

[Hideki Yamane]

Hi,

 It seems that is caused with latest ruby-loofah and it was fixed
 in upstream git repo.

 https://github.com/rails/rails-html-sanitizer.git


 I'll check it later, and push it if it works.



-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#982723: marked as pending in ruby-rails-html-sanitizer

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #982723 in ruby-rails-html-sanitizer reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ruby-team/ruby-rails-html-sanitizer/-/commit/b4a7443224307692b056339415a2afcf954b338e


Fix test failure (Closes: #982723)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982723

Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

[Hideki Yamane]

Hi Andreas,

 Thanks for your suggestion.

On Sun, 7 Mar 2021 08:47:05 +0100
Andreas Metzler  wrote:
> I think that might be a dh_installdeb error, it seems to check whether
> the first character is a '/', and does not account for possible quoting
> characters.
> 
> This might work around this
> rm_conffile /etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg,\ \*

 Well, * is considered as [prior-version], then.


> BTW you should really specify [prior-version and [package].

 Yes, but above problem prevent me to solve issue...


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#929165: How to use rm_conffile to remove files that contain empty " ", comma "," and wildcard "*"?

[Hideki Yamane]

X-debbugs-CC: debian-de...@lists.debian.org

Hi,

 I've tried to remove files that was accidentally containts empty " ",
 comma "," and wildcard "*" via rm_conffile from dpkg-maintscript-helper.

 However, it returns an error like below.

> dh_installdeb: error: The current conffile path for rm_conffile must be 
> present and absolute, got 
> '/etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg,

 I've specified it like below.

> # cat debian/ubuntu-dbgsym-keyring.maintscript
> rm_conffile '/etc/apt/trusted.gpg.d/ubuntu-keyring-2016-dbgsym.gpg, *'
> rm_conffile '/etc/apt/trusted.gpg.d/ubuntu-dbgsym-removed-keys.gpg, *'



 How to use rm_conffile to remove such files that contains empty, comma
 and * in its filenames?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#948876: fontforge: Segmentation fault, making kodi FTBFS

[Hideki Yamane]

control: severity -1 important
control: retitle -1 fontforge: memory leak issue

Hi,

> fontforge: Segmentation fault, making kodi FTBFS

 fontforge has still memory leak issues that are able to detect with
 sanitize DEB_BUILD_OPTION in debian/rules, however, kodi build can
 be without fontforge's segmentation fault now. So, downgrade severity
 and retitle it.



-- 
Hideki Yamane 

Bug#981365: linux-image-5.10.0-2-amd64: HP EliteBook x360 1040 G6 crashing since 5.10.0-1

[Hideki Yamane]

Control: severity -1 important

On Fri, 29 Jan 2021 23:07:50 +0100 Cervinko  wrote:
> Justification: breaks the whole system

 No, it's not.


> i am using a thunderbolt docking station

 If it works without it, it's because docking station.
 Similarly I'm using EliteBook830 G5 with HP Thunderbolt Dock G2, and
 it works (its USB function is instability if it's unplugged and plugged again).

 Anyway, please try to update your EliteBook BIOS and also Thunderbolt docking
 station firmware.


-- 
Hideki Yamane 

Bug#982697: marked as pending in afdko

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #982697 in afdko reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/fonts-team/afdko/-/commit/3df5df3cabd2c78530b94b355db5e96397db61d6


Adjust Build-Depends with cu2qu removal (Closes: #982697)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982697

Bug#975810: fonts-pecita: FTBFS: Error: Validation error

[Hideki Yamane]

Source: fonts-pecita, fontforge
Control: found -1 fontforge/1:20201107~dfsg-1


 It fails with newest fontforge package but succeeded with previous
 version. Can someone investigate it?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#962615: sylfilter: glib error prevent filter working

[Hideki Yamane]

control: tags -1 - a11y
control: notfound -1 0.8-6
control: severity -1 important

 Not sure what reason, sylfilter's db was corrupt and it was not
 introduced in this version, and it doesn't always happen so
 downgrade severity.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#971611: marked as pending in fonts-sil-gentiumplus-compact

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #971611 in fonts-sil-gentiumplus-compact reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/fonts-team/fonts-sil-gentiumplus-compact/-/commit/f74d81dec807cb0d8d024a4f6687d7e485c1730e


Avoid conflict with fonts-sil-gentiumplus (Closes: #971611)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971611

Bug#943015: marked as pending in fonts-ebgaramond

[Hideki Yamane]

On Thu, 18 Jun 2020 23:11:39 +0200
Moritz Mühlenhoff  wrote:
> What's the status, this is pendingg for over half a year? :-)

 It's vintage ;)
 Let's upload and close it now...
 

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#944496: marked as pending in xfonts-efont-unicode

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #944496 in xfonts-efont-unicode reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/fonts-team/xfonts-efont-unicode/-/commit/4c98de1415c5d8d2009f2f4ef30f50e3c229ffae


add 0002-deal-with-deprecated-feature-in-Perl5.30.patch (Closes: #944496)

use "use Array::Base +1;" and add libarray-base-perl for dependency


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944496

Bug#962615: sylfilter: glib error prevent filter working

[Hideki Yamane]

Hi,

On Wed, 10 Jun 2020 20:02:27 +0200
Xavier Brochard  wrote:
> Sylfilter doesn't work anymore in Sylpheed. 
> Sylpheed log contains these lines each time sylfilter is launched:
> GLib-DEBUG: posix_spawn avoided (fd close requested) 
> ** Sylpheed-WARNING: summary_junk_func: junk filter command returned 127

 Which logfile, could you provide a filename, please?


>* What led up to the situation?
>  System update, but user notify me long time after problem start.

 From which version to version?


 Could you try to invoke sylpfiter with terminal and get output
 like below?

$ sylfilter -c lspci.txt -d
xfilter_bayes_db_init: init database
xfilter_bayes_db_init: path: /home/henrich/.sylfilter
xfilter_bayes_db_init: making directory: /home/henrich/.sylfilter
xfilter_bayes_db_init: opening db: /home/henrich/.sylfilter/junk.db
xfilter_bayes_db_init: opening db: /home/henrich/.sylfilter/clean.db
xfilter_bayes_db_init: opening data file: /home/henrich/.sylfilter/status.dat
filter-manager.c: xfilter_manager_run: run filter chain
exec filter: text-content [content filter] in data type: message/rfc822
exec filter: text-content: status 3: out data type: text/plain
exec filter: wordsep [content filter] in data type: text/plain
exec filter: wordsep: status 3: out data type: text/plain
exec filter: bayes-learn-clean [content filter] in data type: text/plain
learning clean message
xfilter_update_status: writing status to file
xfilter_update_status: done
exec filter: bayes-learn-clean: status 4: out data type: text/plain

xfilter_bayes_db_init: close database


 And how about trying to rename ~/.sylfilter directory and create new
 db temporary? Does it work?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#961253: libmecab-perl: Can't load Perl module

[Hideki Yamane]

control: found -1 0.996-7
control: tags -1 +confirmed

On Fri, 22 May 2020 14:10:43 +0900
OHURA Makoto  wrote:
> After downgrading libmecab-perl to 0.99.6-2+b4 (got from 
> snapshot.debian.org), it's working fine.

 Well, it seems that libmecab-perl from mecab package was introduced
 in 0.996-7, and its libmecab-perl 0.99.6-2 was generated with another
 source package, libmecab-perl as https://tracker.debian.org/pkg/libmecab-perl
 

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#955680: birdfont: diff for NMU version 2.28.0-1.1

[Hideki Yamane]

Hi Adrian,

On Sat, 2 May 2020 20:56:57 +0300
Adrian Bunk  wrote:
> I've prepared an NMU for birdfont (versioned as 2.28.0-1.1) and uploaded 
> it to DELAYED/14. Please feel free to tell me if I should cancel it.

 Thanks for the patch! I'll include it as 2.28.0-2 upload.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#955680: marked as pending in birdfont

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #955680 in birdfont reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/fonts-team/birdfont/-/commit/56e3e9aebc7ca26b667d1f87e2af2f431d569ed3


Import Debian changes 2.28.0-1.1

birdfont (2.28.0-1.1) unstable; urgency=low

  * Non-maintainer upload.
  * Link with libcairo-gobject. (Closes: #955680)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/955680

Bug#953404: marked as pending in debootstrap

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #953404 in debootstrap reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/installer-team/debootstrap/-/commit/5874bb9894b72ccf8912f2583447c48e82ec7ea9


fix to work with specify stable/testing as its suite (Closes: #953404)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/953404

Bug#951806: ruby-serverengine: FTBFS aginst Ruby2.5 and Ruby2.7

[Hideki Yamane]

Hi,

 I've investigated it and it seems that failure happens with ruby-rspec
 3.9.0c1e0m1s2-1, not 3.8.0c0e1m0s0-1 in buster.


> Just FTR, this package has no reverse-dependencies or
> reverse-build-dependencies. Is it a good sign for it to be filed for
> removal?

 No, fluentd needs it (ITPed as https://bugs.debian.org/926692 )


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#951349: mecab: Fails to build against ruby2.7

[Hideki Yamane]

control: block -1 by 951623

Hi,

On Wed, 19 Feb 2020 17:41:37 -0300
Lucas Kanashiro  wrote:
> FYI ruby2.7 is already enabled in unstable (the ruby2.7 transition
> already started), so no need to use experimental. Here you can find the
> build logs with failures:
> https://buildd.debian.org/status/package.php?p=mecab

 It seems that 951623 is the issue.


-- 
Hideki Yamane 

Bug#941917: nginx: FTBFS on several architectures: luajit.h: No such file or directory

[Hideki Yamane]

Hi,

 In debian/control, Build-Depends: libluajit-5.1-dev [i386 amd64 kfreebsd-i386 
armel armhf powerpc powerpcspe mips mipsel]
 is wrong, as https://buildd.debian.org/status/package.php?p=luajit=sid 
says below archs are built.

amd64
arm64
armel
armhf
i386
mips64el
mipsel
ppc64el
hurd-i386
kfreebsd-amd64
kfreebsd-i386
powerpc
ppc64

 So, it should be libluajit-5.1-dev [amd64 arm64 armel armhf i386 mips64el 
mipsel ppc64el hurd-i386 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64] and so on.
 And it seems that it should check whether its arch has libluajit-5.1-dev or 
not.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#929714: python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

[Hideki Yamane]

On Tue, 4 Jun 2019 00:09:06 +0900 Hideki Yamane  wrote:
>  Just removing some lines from debian/rules improves it, debdiff
>  attached.

 I've submitted it to DELEYED/5 queue, feel free to cancel it.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#929714: python-acora: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

[Hideki Yamane]

control: tags -1 +patch

On Wed, 29 May 2019 16:29:31 +0200 Lucas Nussbaum  wrote:
> >  dpkg-source -b .
> > dpkg-source: info: using source format '3.0 (quilt)'
> > dpkg-source: info: building python-acora using existing 
> > ./python-acora_2.2.orig.tar.gz
> > dpkg-source: info: local changes detected, the modified files are:
> >  python-acora-2.2/acora/_acora.c
> >  python-acora-2.2/acora/_acora.html
> >  python-acora-2.2/acora/_cacora.c
> >  python-acora-2.2/acora/_cacora.html
> > dpkg-source: error: aborting due to unexpected upstream changes, see 
> > /tmp/python-acora_2.2-1.diff.VWSw_l
> > dpkg-source: info: you can integrate the local changes with dpkg-source 
> > --commit
> > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

 Just removing some lines from debian/rules improves it, debdiff
 attached.

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp


python-acora.debdiff
Description: Binary data

Bug#922346: Fix for this issue still not available in testing

[Hideki Yamane]

On Sun, 26 May 2019 12:41:39 +0200 Michel Le Bihan  wrote:
> I saw that Mesa 18.3.6-2 was accepted into unstable on 2019-05-11. That
> version still hasn't migrated to testing because of the freeze. Could
> you please contact the release team to get this release in testing ASAP
> as I (and probably other users) am still experiencing this issue and it
> is very critical because opening a media file can cause my DE to crash
> causing the loss of any unsaved work.

 However, it contains thousands of diffs that is unsuitable during
 full freeze period. It'd be better to provide patch that only dealing
 with this issue for testing-proposed-update suite.


-- 
Hideki Yamane 

Bug#929720: RE:Bug#929720: hkl: FTBFS:

[Hideki Yamane]

 ../../hkl/ccan/generator/generator.h:23:2: error: #error Generators require
  coroutines
Message-Id: <20190601215909.5c48c58048e0920e76d56...@iijmio-mail.jp>
In-Reply-To: 

X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

control: tags -1 +unreproducible

On Fri, 31 May 2019 17:22:31 + PICCA Frederic-Emmanuel 
 wrote:
> I cannot reproduce this issue into my sbuild (buster).

 It's same here, I've tried it with my local cowbuilder buster/sid
 and AWS Lightsail VM buster chroot.


-- 
Hideki Yamane 

Bug#929715: strace: FTBFS: open: /dev/kvm: No such file or directory

[Hideki Yamane]

Hi (send again due to typo...),

On Wed, 29 May 2019 16:30:05 +0200 Lucas Nussbaum  wrote:
> Source: strace
> Version: 4.26-0.2
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20190529 qa-ftbfs
> Justification: FTBFS in buster on amd64

 I think it is because you would run this job on AWS, its host runs
 on Xen, so there's no /dev/kvm file. This FTBFS depends on such
 specific environment, so we can close it, IMHO.


-- 
Hideki Yamane 

Bug#922669: fixed in sqlalchemy 1.2.18+ds1-2

[Hideki Yamane]

Hi,

 Do you file unblock for sqlalchemy? 
 Or also add debian/NEWS file to indicate potential incompatibility for
 applications?

-- 
Hideki Yamane 

Bug#929575: simpleid: Not compatible with PHP 7

[Hideki Yamane]

control: tags -1 +fixed-upstream

On Mon, 27 May 2019 00:07:55 +1000 Stuart Prescott  wrote:
> Justification: Does not work with PHP 7 in buster

> According to the upstrem bug tracker, simpleid is not compatible with PHP7,

 And he indicated upstream 1.0.2 works with PHP7, so add "fixed-upstream"
 tag.

 I propose that we'll remove simpleid package from stretch and buster
 at least, since it was too old, not cared for a long time since 2016.


-- 
Hideki Yamane 

Bug#866758: Please close this bug

[Hideki Yamane]

Hi Roger,

On Wed, 29 May 2019 13:47:07 -0500 "Roger T. Imai"  
wrote:
> I can't find a method or instructions for closing bug 866758, possibly
> because I was a contributor, not the original submitter. A subsequent
> kernel or Intel microcode update resolved the issue in my case.

 It's easy, just send mail to -d...@bugs.debian.org.
 However, I want to wait original reporter's reply for it.


-- 
Hideki Yamane 

Bug#866758: Additional information kernel 4.9.0-4-amd64

[Hideki Yamane]

Hi,

 https://bugs.debian.org/866758 is still open, is there any additional
 information for it? If not, I'll suggest you to close it.


On Mon, 11 Dec 2017 02:20:56 -0600
"Roger T. Imai"  wrote:
> In further testing, I found that I am able to boot into X11/Gnome3 if I
> revert to booting Linux kernel 4.9.0-*3*-amd64. I will continue with
> 4.9.0-3-amd64 until the next amd64-related update.
> 
> I am an intermediate user with no programming knowledge, but somewhat
> familiar with the command line and file paths. Please feel free to send
> instructions for extracting additional diagnostic information as needed.
> I'm also willing to install additional debug tools as required. Thanks for
> your attention.
> 
> Attachment: If helpful, full hardware list for my notebook, an obscure HP
> model sold to college engineering schools, probably with older components
> than the commercial models.
> 
> Roger T. Imai
> Franklin (Nashville) TN


-- 
Hideki Yamane 

Bug#928052: CVE-2019-11502 CVE-2019-11503

[Hideki Yamane]

control: tags -1 +fixed-upstream

On Fri, 26 Apr 2019 23:04:05 +0200 Moritz Muehlenhoff  wrote:
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11502

 It was fixed in upstream 2.38 
 
https://github.com/snapcore/snapd/commit/bdbfeebef03245176ae0dc323392bb0522a339b1

> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11503
 
 It was fixed in upstream 2.39
 
https://github.com/snapcore/snapd/commit/187893dee84e34ed40680217d2c3ce810985f97e

-- 
Hideki Yamane 

Bug#927942: marked as pending in gucharmap

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #927942 in gucharmap reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gucharmap/commit/fe401950cdf5cb5601a6df79be13345e86f6880d


update changelog (Closes: #927942)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/927942

Bug#927153: plymouth: upgrade fails:

[Hideki Yamane]

 /usr/share/initramfs-tools/hooks/plymouth failed with return 134
Message-Id: <20190528073815.2ba8e2fb13cf10d0fb4bc...@iijmio-mail.jp>
In-Reply-To: <20190520133004.gb2...@zira.vinc17.org>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 20 May 2019 15:30:04 +0200 Vincent Lefevre  wrote:
> On 2019-05-14 15:33:45 +0200, Tobias Eliasson wrote:
> > Are you able to reproduce this error with the latest fontconfig 2.13.1 in
> > buster?
> 
> I've just tried, and I no longer get a failure.

 Let's close this bug, then :)


-- 
Hideki Yamane 

Bug#925555: linux-image-4.19.0-4-amd64: [regression] No graphics on some

[Hideki Yamane]

 IvyBridge / Haswell systems
Message-Id: <20190528065209.ab9aed4d6eabe80a6b398...@iijmio-mail.jp>
In-Reply-To: <20190528064028.dec9969527111b97d555d...@iijmio-mail.jp>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 28 May 2019 06:40:28 +0900 Hideki Yamane  wrote:
>  It seems that fixed in 4.9.38 as below.

 4."19".38.


-- 
Hideki Yamane 

Bug#925555: linux-image-4.19.0-4-amd64: [regression] No graphics on some IvyBridge / Haswell systems

[Hideki Yamane]

control: tags -1 +fixed-upstream

Hi,

 It seems that fixed in 4.9.38 as below.

> commit 2bc7ce32eb21b094b3ae3e489017fabfe72b4dda
> Author: Dave Airlie 
> Date:   Wed Apr 24 10:47:56 2019 +1000
> 
> Revert "drm/i915/fbdev: Actually configure untiled displays"
> 
> commit 9fa246256e09dc30820524401cdbeeaadee94025 upstream.
> 
> This reverts commit d179b88deb3bf6fed4991a31fd6f0f2cad21fab5.
> 
> This commit is documented to break userspace X.org modesetting driver in 
> certain configurations.
> 
> The X.org modesetting userspace driver is broken. No fixes are available 
> yet. In order for this patch to be applied it either needs a config option or 
> a workaround developed.
> 
> This has been reported a few times, saying it's a userspace problem is 
> clearly against the regression rules.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109806
> Signed-off-by: Dave Airlie 
> Cc:  # v3.19+
> Signed-off-by: Greg Kroah-Hartman 

-- 
Hideki Yamane 

Bug#928304: groonga-httpd: Privilege escalation due to insecure use of logrotate

[Hideki Yamane]

Hi Salvatore,

 Can you follow his question? I guess debian revision should be
 6.1.5-1+deb9u1, but others are okay.


On Tue, 7 May 2019 23:15:58 +0900
Kentaro Hayashi  wrote:
> I maintain Groonga package as a DM, so I want to fix #928304.
> But I've never uploaded package to stable before, so I need help
>  to do it in a good manner.
> 
> I've attached debdiff against current version.
> Is it ok to upload stretch-security?



diff -Nru groonga-6.1.5/debian/changelog groonga-6.1.5/debian/changelog
--- groonga-6.1.5/debian/changelog  2017-01-23 19:14:09.0 +0900
+++ groonga-6.1.5/debian/changelog  2019-05-07 22:33:11.0 +0900
@@ -1,3 +1,13 @@
+groonga (6.1.5-2) stretch-security; urgency=medium
+
+  * debian/groonga-httpd.logrotate
+debian/groonga-server-gqtp.logrotate
+- Mitigate privilege escalation by changing the owner and group of logs
+  with "su" option. Reported by Wolfgang Hotwagner.
+  (Closes: #928304) (CVE-2019-11675)
+
+ -- Kentaro Hayashi   Tue, 07 May 2019 22:33:11 +0900
+
 groonga (6.1.5-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru groonga-6.1.5/debian/groonga-httpd.logrotate 
groonga-6.1.5/debian/groonga-httpd.logrotate
--- groonga-6.1.5/debian/groonga-httpd.logrotate2016-12-10 
15:18:50.0 +0900
+++ groonga-6.1.5/debian/groonga-httpd.logrotate2019-05-07 
22:33:11.0 +0900
@@ -1,11 +1,11 @@
 /var/log/groonga/httpd/*.log {
+su groonga groonga
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
-create 640 groonga groonga
 sharedscripts
 postrotate
 . /etc/default/groonga-httpd
diff -Nru groonga-6.1.5/debian/groonga-server-gqtp.logrotate 
groonga-6.1.5/debian/groonga-server-gqtp.logrotate
--- groonga-6.1.5/debian/groonga-server-gqtp.logrotate  2016-12-10 
15:18:50.0 +0900
+++ groonga-6.1.5/debian/groonga-server-gqtp.logrotate  2019-05-07 
22:33:11.0 +0900
@@ -1,11 +1,11 @@
 /var/log/groonga/*-gqtp.log {
+su groonga groonga
 daily
 missingok
 rotate 30
 compress
 delaycompress
 notifempty
-create 640 groonga groonga
 sharedscripts
 postrotate
 . /etc/default/groonga-server-gqtp

Bug#928509: Firefox insecure because of missing extensions

[Hideki Yamane]

Hi,

On Mon, 6 May 2019 15:04:09 +0200 Karsten  wrote:
> Package: firefox-esr
> Version: 60.6.1esr-1~deb8u1

 It was already done in unstable and stable-proposed-updates, and
 reporter asks about oldstable, so CC:ed to lts mailing list.
 
 LTS maintainers, could you build it for oldstable, please?


> When there is no fix for the used Firefox-Version, then a new browser 
> solution is needed for Debian.

 No, you can migrate to Debian9 at least...


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#925555: linux-image-4.19.0-4-amd64: Display manager fails to start or display anything on IvyBridge with linux-image-4.19.0-4-amd64

[Hideki Yamane]

Hi,

 Maybe https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926193 is same?

-- 
Hideki Yamane 

Bug#927263: riece: error on (wrong-number-of-arguments (1 . 1) 2)

[Hideki Yamane]

control: tags -1 +patch +pending

Hi,

 Thanks for your patch, I'll test and upload in this weekend holiday.

-- 
Hideki Yamane 

Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and

[Hideki Yamane]

Hi,

 I've created a patch for squid-deb-proxy-client bug as below.
 But I'm not sure it's okay to override conffile under /etc with
 symlink. Any comments? If not, I'll upload it.


On Sat, 16 Mar 2019 15:58:30 +0900 Hideki Yamane  wrote:
>  How about moving 30autoproxy to /usr/share and create symlink under
>  /etc/apt/apt.conf.d to it? Here's a patch, works well after package
>  removal and piuparts clean one.

> diff -Nru squid-deb-proxy-0.8.14+nmu1/Makefile 
> squid-deb-proxy-0.8.14+nmu2/Makefile
> --- squid-deb-proxy-0.8.14+nmu1/Makefile  2018-08-16 03:25:06.0 
> +0900
> +++ squid-deb-proxy-0.8.14+nmu2/Makefile  2019-03-16 15:30:32.0 
> +0900
> @@ -19,4 +19,4 @@
>   install -m 644 mirror-dstdomain.acl $(DESTDIR)/etc/squid-deb-proxy/
>   # client
>   install -m 755 apt-avahi-discover 
> $(DESTDIR)/usr/share/squid-deb-proxy-client/
> - install -m 644 30autoproxy $(DESTDIR)/etc/apt/apt.conf.d
> + install -m 644 30autoproxy $(DESTDIR)/usr/share/squid-deb-proxy-client/
> diff -Nru squid-deb-proxy-0.8.14+nmu1/debian/changelog 
> squid-deb-proxy-0.8.14+nmu2/debian/changelog
> --- squid-deb-proxy-0.8.14+nmu1/debian/changelog  2018-08-16 
> 03:25:06.0 +0900
> +++ squid-deb-proxy-0.8.14+nmu2/debian/changelog  2019-03-16 
> 15:30:32.0 +0900
> @@ -1,3 +1,12 @@
> +squid-deb-proxy (0.8.14+nmu2) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * move /etc/apt/conf.d/30autoproxy to under 
> /usr/share/squid-deb-proxy-client
> +and make symlink to it, to avoid package fetch failure after removed its
> +package (Closes: #867682)



-- 
Hideki Yamane 

Bug#867681: fixed in software-properties 0.96.24.32.7-1

[Hideki Yamane]

Hi,

On Sun, 27 Jan 2019 15:35:35 + Julian Andres Klode  wrote:
> Source: software-properties
> Binary: python3-software-properties software-properties-common 
> software-properties-gtk software-properties-kde
> Architecture: source
> Version: 0.96.24.32.7-1
> Distribution: experimental

 Do you upload it to unstable, too?
 For buster release, this is one of the RC bugs.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and

[Hideki Yamane]

Hi,

On Sat, 16 Mar 2019 09:37:04 +0100
Andreas Beckmann  wrote:
> Does this conffile-to-symlink transition work cleanly on upgrades? i.e.
> does dpkg "forget" about the conffile?
> I'd expect that you may need dpkg-maintscript_helper rm_conffile and
> create the symlink manually in the postinst ...

 Yes, it is. I've tested it with

 sudo piuparts --scriptsdir /etc/piuparts/scripts --no-eatmydata 
--allow-database \
   --warn-on-leftovers-after-purge --mirror 
'http://debian-mirror.sakura.ne.jp/debian/ main' \
   --arch amd64 -b /home/henrich/tmp/buster.tgz -d testing -d sid \
   squid-deb-proxy-client_0.8.14+nmu2_all.deb

 and local machine.


-- 
Hideki Yamane 

Bug#867682: squid-deb-proxy-client: breaks apt operation if removed and

[Hideki Yamane]

 system upgraded to stretch
Message-Id: <20190316155830.288514652de850440de12...@iijmio-mail.jp>
In-Reply-To: <1540574...@msgid.manchmal.in-ulm.de>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt"

This is a multi-part message in MIME format.

--Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

control: tags -1 +patch

Hi,

On Fri, 26 Oct 2018 19:27:05 +0200 Christoph Biedl 
 wrote:
> So the only solution I can think of was to either move
> apt-avahi-discover to /etc/ (not quite good style), or to create a small
> wrapper script in /etc/ that just does the check as above - not the best
> thing as well, but should do the trick.
> 
> Did I miss something?

 How about moving 30autoproxy to /usr/share and create symlink under
 /etc/apt/apt.conf.d to it? Here's a patch, works well after package
 removal and piuparts clean one.


-- 
Hideki Yamane 

--Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt
Content-Type: text/x-diff;
 name="bug867682.patch"
Content-Disposition: attachment;
 filename="bug867682.patch"
Content-Transfer-Encoding: 7bit

diff -Nru squid-deb-proxy-0.8.14+nmu1/Makefile 
squid-deb-proxy-0.8.14+nmu2/Makefile
--- squid-deb-proxy-0.8.14+nmu1/Makefile2018-08-16 03:25:06.0 
+0900
+++ squid-deb-proxy-0.8.14+nmu2/Makefile2019-03-16 15:30:32.0 
+0900
@@ -19,4 +19,4 @@
install -m 644 mirror-dstdomain.acl $(DESTDIR)/etc/squid-deb-proxy/
# client
install -m 755 apt-avahi-discover 
$(DESTDIR)/usr/share/squid-deb-proxy-client/
-   install -m 644 30autoproxy $(DESTDIR)/etc/apt/apt.conf.d
+   install -m 644 30autoproxy $(DESTDIR)/usr/share/squid-deb-proxy-client/
diff -Nru squid-deb-proxy-0.8.14+nmu1/debian/changelog 
squid-deb-proxy-0.8.14+nmu2/debian/changelog
--- squid-deb-proxy-0.8.14+nmu1/debian/changelog2018-08-16 
03:25:06.0 +0900
+++ squid-deb-proxy-0.8.14+nmu2/debian/changelog2019-03-16 
15:30:32.0 +0900
@@ -1,3 +1,12 @@
+squid-deb-proxy (0.8.14+nmu2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * move /etc/apt/conf.d/30autoproxy to under /usr/share/squid-deb-proxy-client
+and make symlink to it, to avoid package fetch failure after removed its
+package (Closes: #867682)
+
+ -- Hideki Yamane   Sat, 16 Mar 2019 15:30:32 +0900
+
 squid-deb-proxy (0.8.14+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload with maintainer consent
diff -Nru squid-deb-proxy-0.8.14+nmu1/debian/squid-deb-proxy-client.links 
squid-deb-proxy-0.8.14+nmu2/debian/squid-deb-proxy-client.links
--- squid-deb-proxy-0.8.14+nmu1/debian/squid-deb-proxy-client.links 
1970-01-01 09:00:00.0 +0900
+++ squid-deb-proxy-0.8.14+nmu2/debian/squid-deb-proxy-client.links 
2019-03-16 15:30:32.0 +0900
@@ -0,0 +1 @@
+usr/share/squid-deb-proxy-client/30autoproxy etc/apt/apt.conf.d/30autoproxy

--Multipart=_Sat__16_Mar_2019_15_58_30_+0900_/j+zRXFvRO9OiPHt--

Bug#918722: debootstrap: says InRelease file expired

[Hideki Yamane]

On Wed, 9 Jan 2019 14:13:14 +0100
Julien Cristau  wrote:
> I reverted the 1.0.113 changes to unbreak this and uploaded 1.0.114.

 Thanks to take caring for this.

> I'm happy to review an updated version when you get that working.  Hope
> that's ok.

 Now I've pushed MR with (hopefully) fixed version, please check it.


-- 
Hideki Yamane 

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

[Hideki Yamane]

On Fri, 4 Jan 2019 10:22:08 -0300
Antonio Terceiro  wrote:
> Are you working on updating sinatra? I started working on a new sinatra
> upstream release to unbreak debci after a new rack was uploaded, and
> could build binaries for ruby-sinatra-contrib (and ruby-rack-protection,
> which was also moved into sinatra) from the ruby-sinatra source in one
> go.

 Thanks Antonio for updating sinatra package!
 
 And now I've found that ruby-sinatra-contrib was removed from repository,
 is that intended?

 See https://ftp-master.debian.org/removals.txt


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#918584: os-autoinst FTBFS on i386: FAIL: 01-test_needle.t

[Hideki Yamane]

control: forwarded -1 https://progress.opensuse.org/issues/45782

On Mon, 07 Jan 2019 17:48:40 +0200
Adrian Bunk  wrote:
> not ok 14 - found area is the original one too
> #   Failed test 'found area is the original one too'
> #   at ./01-test_needle.t line 73.
> #  got: '944'
> # expected: '108'

 Thanks, I got same result with upstream master, forwarded to
 them.


-- 
Hideki Yamane 

Bug#910463: os-autoinst FTBFS on !x86/ppc64{,el}: test failure

[Hideki Yamane]

control: severity -1 important

Hi,

 Just a workaround, specify it is released as i386 and amd64 only
 for now.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#899595: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org

[Hideki Yamane]

Hi,

 With Bugs search "Cleaner view", I've found those bugs are not closed
 in unstable but are done in experimental. Do you have a plan to put them
 into unstable, or just apply only those fixes to current unstable packages?

 I know xfce4.13 series are development release, but some projects like Fedora
 and Xubuntu have released 4.13 series as discussed at
 https://mail.xfce.org/pipermail/xfce4-dev/2018-July/032143.html
 

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#816640: Bug #816640 in ruby-eventmachine marked as pending

[Hideki Yamane]

Hi,

On Fri, 16 Feb 2018 13:48:16 + z...@debian.org wrote:
> Bug #816640 in ruby-eventmachine reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below, and you can check the diff of the fix at:
> 
> https://salsa.debian.org/ruby-team/ruby-eventmachine/commit/a752744e504c657cc43044df98881b6713d6bd65
> 
> 
> Blacklist another "network"-needing test. Closes: #816640

 Is there any reason not upload to the repository?
 It would be nice to fix this FTBFS :)


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#916123: Bug #916123 in grcompiler marked as pending

[Hideki Yamane]

Control: tag -1 pending

Hello,

Bug #916123 in grcompiler reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/fonts-team/grcompiler/commit/3b501679d8e032ee8bc26197e748787c4afa31ce


add icu_pkg-config.patch (Closes: #916123)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916123

Bug#864709: xfce CD1 image should contain fonts for languages supported by debian installer

[Hideki Yamane]

Hi,

On Sun, 30 Dec 2018 18:46:45 +0530
Pirate Praveen  wrote:
> We have not stopped providing CD images. DVD is an additional option. I think 
> this matters still.

 Well, we've already stopped it 3 years ago.
 https://lists.debian.org/debian-devel-announce/2015/09/msg4.html

 But, https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/ shows
 debian-9.6.0-amd64-xfce-CD-1.iso as default desktop image... why?

-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#864709: xfce CD1 image should contain fonts for languages supported by debian installer

[Hideki Yamane]

Hi,

On Tue, 13 Jun 2017 14:35:03 +0530 Pirate Praveen  wrote:
> I selected Malayalam during installation of last testing snapshot of
> stretch, but the system did not have a Malayalam font installed. I'd
> think the case would be similar for other languages. Can't we reuse the
> fonts used by the installer? It may require changes in the installer to
> use normal debs instead of udebs.

 Just a question: Now we provide DVD image, not CD image. Is it still matter?

-- 
Hideki Yamane 

Bug#906688: ruby-netrc: FTBFS in buster/sid (test_missing_environment fails)

[Hideki Yamane]

Hi,

 It builds well with cowbuilder, at least (I don't know why...)


-- 
Hideki Yamane 

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

[Hideki Yamane]

Hi,

On Sun, 23 Dec 2018 00:36:52 +
Simon McVittie  wrote:
> To be completely clear about the decision that Ian asked the technical
> committee to overrule:
> 
> In all debootstrap versions since 1.0.102, merged /usr is the default (for
> all variants except --variant=buildd). This means that new installations
> of Debian buster using debian-installer will have merged /usr.
> 
> Do the debian-installer and debootstrap maintainers think this should
> continue to be true for the buster release?

 At this time, yes. +1

 However, if it'll be a blocker for release during freeze, it should
 be reverted.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#887601: libcamlimages-ocaml: Detect freetype using pkg-config

[Hideki Yamane]

Hi,

On Thu, 18 Jan 2018 11:19:18 + Hugh McMaster  
wrote:
> Package: libcamlimages-ocaml
> Version: 1:4.2.0-1.1+b3
> Severity: important
> 
> Dear Maintainer,
> 
> The next version of libfreetype6-dev will *not* ship the 'freetype-config'
> script.
> 
> Please use pkg-config to detect the freetype headers and libraries instead.

 I've prepared patches (and more update) at
 https://salsa.debian.org/ocaml-team/camlimages/merge_requests/2

 I'm not sure why but I cannot detect freetype header files with
 Check_header_library, so just specified pkg-config checks returns
 "true".

 Anyway, please check it.
 

-- 
Hideki Yamane 

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default? /usr by default

[Hideki Yamane]

Hi,

On Wed, 5 Dec 2018 08:39:27 +
Simon McVittie  wrote:
> It might also be considered appropriate to revert the change in
> debootstrap 1.0.111 if data from reproducible-builds demonstrates that
> bugs similar to #913226 have all been fixed or are very rare, but this
> should be done cautiously, and certainly not before buster is released.

 Okay, my opinion is "Push usr-merge effort forward, fix those issues
 with it as bug that is tracked at reproducible builds(*), and turn it
 on again as default (probably after buster cycle)".

 *) 
https://tests.reproducible-builds.org/debian/issues/unstable/paths_vary_due_to_usrmerge_issue.html


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default

[Hideki Yamane]

Hi,

 Thanks Simon, it's perhaps clear for me now.

On Sun, 2 Dec 2018 15:15:21 +
Simon McVittie  wrote:
> >   - What is the problem? (broken build for which packages? Just R?)
> 
> The problem we're aware of is:
> 
> Some packages auto-detect the absolute path to an executable (for example
> bash or perl) and hard-code it into their output (for example the #! line
> of the bash scripts in quilt).

 Can we check and track this behavior in our packages?

 Once disable merged-usr is good to prevent confusion but we detect such
 as a bug for manage non-merged-usr and merged-usr Debian system in the end,
 right? (or do you want to stay change in debootstrap 1.0.111 forever?)


-- 
Hideki Yamane 

Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default

[Hideki Yamane]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

On Fri, 30 Nov 2018 19:40:45 +0100
"Didier 'OdyX' Raboud"  wrote:
> tl;dr: debootstrap maintainers; can you agree to disable "merged /usr" by 
> default now, or are you OK letting the TC decide on this subject?

 Hmm, I'm still considering what's the good way...

> Hideki, if I read the debootstrap history correctly, you enabled "merged 
> /usr" 
> by default in debootstrap 1.0.102. 

 Yes, that's right. #839046 was filed in Sep 2016, and uploaded in Jun 2018.

> Given the recent discussion in debian-
> devel@ (starting at [0]) and on #914897, could you (or anyone speaking as 
> with 
> a "debootstrap maintainer" hat on) state if, either of:
> 
> * you would be willing to toggle the "merged /usr" default in debootstrap in a
>   subsequent upload;
> * you maintain that the "merged /usr" default (to yes) is here to stay.

 Well, with a quick look to the thread (I cannot follow all of the email in it,
 tons of emails...), I cannot find the discussion about

  - What is the problem? (broken build for which packages? Just R?)
  - How many packages are affected?
  - Why it was caused? (just symlink to /bin or /sbin isn't enough
to deal with it?)
  - Does it cause any failure on users' machine?

 So, I want to listen above things (not thought or idea), then reply to
 your question. Please quote if someone can do it.


- -- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp
 http://wiki.debian.org/HidekiYamane
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQZYJUbYxgXxV33EdBBJ4KqpAHFMFAlwDzlUACgkQBBJ4KqpA
HFOnfxAAv8s9EQwntX9SBHALIY+5X1Ma98aMhrzZ2SWDt1txznXRt18z/85oOWqs
FGLrm2QY159qWEG2lpsWhAIr7wQJBPcFH5MRQcn6pDM6pXB1ioaTsW9uhd/AMl+s
mCyvWW0xtJ1ww2EXV2hN5X0K4AAre2rajb0P4p6efeY5V9sbMQ/gZa+L2sJuL1P/
/6fK4Kxe893lVuZ3oxtOhKRkdgi1V1X63kUURofuTSZiVzeGYWAuPdnHBxADs9vK
kk6mpUFkYSeOfg45h2KQzUqeTsX5GTogWIFqEOAJ0KJGDusOiFEPWL/pus+De1E7
cyEX2i6yq3wOOQBov5/eNH2gMs9pDaOqM8hR0tjvya4aAJOa7VyFY2GzMdsEHdQe
Ay7EtzG3RLwuiQ0XrSmIyaDdlJpofCGernNgVu+dnBJb/1U4RHgneVbIELULGUYm
DGFov6FpeUQB6wc/fsaoDWQBiwwNCS2qkJnZJg5nu4ne12NqnERqoq2lIR3ivSe2
1Oi9v/ClKqNSKGLAIoRVvllZhs9W1ppwkZIqtC0mZlN05nw7Wyrj4YoRbJ4r70Rd
rdQzTntchOXbYOmdt2H6yUdpnJJoA46+OxlwykvjrUnDnzgheNMJ0wRh36LcOz50
pjQBQGGVVl/9+Tjw/vSCu+alwLwPY34YFOM8I4fh/V0OHbO4fNE=
=yD0D
-END PGP SIGNATURE-

Bug#905165: debootstrap - fails in docker environment

[Hideki Yamane]

Hi,

On Wed, 1 Aug 2018 07:55:07 +0200 Bastian Blank  wrote:
> Package: debootstrap
> Version: 1.0.106
> Severity: grave
> 
> debootstrap fails in docker environment completely by:

 Does it still occur with 1.0.107 or 1.0.108?


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#905165: debootstrap - fails in docker environment

[Hideki Yamane]

On Wed, 1 Aug 2018 07:55:07 +0200
Bastian Blank  wrote:
> Package: debootstrap
> Version: 1.0.106
> Severity: grave
> 
> debootstrap fails in docker environment completely by:

 Could you try 1.0.107 in git repo, please?
 I was in trouble with uploading it, but it would be better one.

 And if it still happens, please describe reproduce step for it.

-- 
Hideki Yamane 

Bug#896071: debootstrap fails to retrive Release file over https

[Hideki Yamane]

On Sun, 20 May 2018 10:14:13 +0200
Philipp Kern <pk...@debian.org> wrote:
> So the way it works with your patch is that local variables are
> inherited by called functions (but not the caller). So from and dest
> from just_get() are visible in wgetprogress() and hence the construction
> of $@ works. I'd rather have $dest and $from be explicit parameters to
> wgetprogress. Given that you reset $@ anyway I don't see how that'd hurt.

 Hmm, but if I don't put $dest and $from to $@ and other parameters are
 empty, then it would be extracted as '' and wget will fail.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#896071: debootstrap fails to retrive Release file over https

[Hideki Yamane]

On Sat, 19 May 2018 20:18:17 +0200
Philipp Kern <pk...@debian.org> wrote:
> You local'ed from and dest and now don't pass it anymore to
> wgetprogress. How does this work?

 It is passed to wget via $@


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#896071: debootstrap fails to retrive Release file over https

[Hideki Yamane]

On Mon, 14 May 2018 00:48:53 +0200
Philipp Kern  wrote:
> any new about incorporating Raphael's suggestion? There's still a grave
> bug opened against debootstrap right now (on a version that is in testing).

 Sorry for late reply, revert previous fix and modified functions as
 Raphael suggested, and it works on my box. Please check it.


diff --git a/functions b/functions
index dc55faf..350f463 100644
--- a/functions
+++ b/functions
@@ -79,6 +79,18 @@ progress_next () {
 wgetprogress () {
[ ! "$VERBOSE" ] && NVSWITCH="-nv"
local ret=0
+
+   set -- -O "$dest" "$from" "$@"
+   if [ -n "$PRIVATEKEY" ]; then
+   set -- "$PRIVATEKEY" "$@"
+   fi
+   if [ -n "$CERTIFICATE" ]; then
+   set -- "$CERTIFICATE" "$@"
+   fi
+   if [ -n "$CHECKCERTIF" ]; then
+   set -- "$CHECKCERTIF" "$@"
+   fi
+
if [ "$USE_DEBIANINSTALLER_INTERACTION" ] && [ "$PROGRESS_NEXT" ]; then
wget "$@" 2>&1 >/dev/null | "$PKGDETAILS" "WGET%" 
"$PROGRESS_NOW" "$PROGRESS_NEXT" "$PROGRESS_END" >&3
ret=$?
@@ -401,20 +413,14 @@ just_get () {
# args: from dest
local from="$1"
local dest="$2"
+
mkdir -p "${dest%/*}"
+
if [ "${from#null:}" != "$from" ]; then
error 1 NOTPREDL "%s was not pre-downloaded" "${from#null:}"
-   elif [ "${from#http://}; != "$from" ] || [ "${from#ftp://}; != "$from" 
]; then
-   # http/ftp mirror
-   if wgetprogress -O "$dest" "$from"; then
-   return 0
-   else
-   rm -f "$dest"
-   return 1
-   fi
-   elif [ "${from#https://}; != "$from" ] ; then
-   # http/ftp mirror
-   if wgetprogress "$CHECKCERTIF" "$CERTIFICATE" "$PRIVATEKEY" -O 
"$dest" "$from"; then
+   elif [ "${from#http://}; != "$from" ] || [ "${from#ftp://}; != "$from" 
] || [ "${from#https://}; != "$from" ]; then
+   # HTTP(S) mirror (FTP mirror is deprecated but not removed)
+   if wgetprogress ; then
return 0
else
rm -f "$dest"