Bug#932855: e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133

[jim_p]

Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855

I know it will sound like a support question, but please help me.
I have 2 pcs, one with debian unstable i386 and one with debian testing amd64.
Obviously, the first one was hit by that bug earlier today.

Because I have no optical drive on my systems so as to load a live cd, I
removed the drive with the i386 installation, installed it on the amd64 one and
chrooted from there. As suggested here, I installed logsave, exited the chroot
and put the drive back in place. However, the problem still persists. Any ideas
why?



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcom-err2  1.44.5-1
ii  libext2fs2   1.44.5-1
ii  libss2   1.44.5-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  parted 3.2-25+b1

-- no debconf information

Bug#932882: python3-pyroute2: /usr/bin/ss2 shipped in both packages

[Felix Geyer]

Package: python3-pyroute2
Version: 0.5.4-1
Severity: serious

/usr/bin/ss2 is shipped in python-pyroute2 and python3-pyroute2 without any
kind of Conflicts/Replaces resulting in an error when trying to install
both packages:

> Preparing to unpack .../10-python-pyroute2_0.5.4-1_all.deb ...
> Unpacking python-pyroute2 (0.5.4-1) over (0.5.2-1) ...
> Preparing to unpack .../11-python3-pyroute2_0.5.4-1_all.deb ...
> Unpacking python3-pyroute2 (0.5.4-1) over (0.5.2-1) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-0jYnUK/11-python3-pyroute2_0.5.4-1_all.deb (--unpack):
>  trying to overwrite '/usr/bin/ss2', which is also in package python-pyroute2 
> 0.5.4-1
> dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

Cheers,
Felix

Processed: Re: Bug#932881: add dependency on logsave

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 e2fsprogs 1.45.3-1
Bug #932881 [initramfs-tools] add dependency on logsave
Bug reassigned from package 'initramfs-tools' to 'e2fsprogs'.
No longer marked as found in versions initramfs-tools/0.133.
Ignoring request to alter fixed versions of bug #932881 to the same values 
previously set
Bug #932881 [e2fsprogs] add dependency on logsave
Marked as found in versions e2fsprogs/1.45.3-1.
> forcemerge 932861 -1
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932881 [e2fsprogs] add dependency on logsave
Severity set to 'critical' from 'grave'
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Merged 932855 932859 932861 932881

-- 
932855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932855
932859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932859
932861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932861
932881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932881: add dependency on logsave

[Sven Joachim]

Control: reassign -1 e2fsprogs 1.45.3-1
Control: forcemerge 932861 -1

On 2019-07-24 08:32 +0300, Aleksi Suhonen wrote:

> Package: initramfs-tools
> Severity: grave
> Version: 0.133
>
> After upgrading e2fsprogs to 1.45.3-1, computer fails to boot because
> rootfs fails to fsck. And fsck fails because binary for logsave is
> missing. Or in fact, fsck doesn't fail, but the init script reports it
> did, because it cannot tell the difference...
>
> This is because logsave has just been split into its own package
> "logsave." The initrd builder scripts should depend on it, except it
> seems that not all hardware platforms have the logsave package yet...

It is e2fsprogs which needs to depend on logsave for the time being in
order not to break its reverse dependencies.  As for initramfs-tools,
initramfs-tools-core should probably depend on
logsave | e2fsprogs (<< 1.45.3), that is tracked in #932854.

Cheers,
   Sven

Bug#932881: add dependency on logsave

[Aleksi Suhonen]

Package: initramfs-tools
Severity: grave
Version: 0.133

After upgrading e2fsprogs to 1.45.3-1, computer fails to boot because 
rootfs fails to fsck. And fsck fails because binary for logsave is 
missing. Or in fact, fsck doesn't fail, but the init script reports it 
did, because it cannot tell the difference...


This is because logsave has just been split into its own package 
"logsave." The initrd builder scripts should depend on it, except it 
seems that not all hardware platforms have the logsave package yet...


Excerpt from the other package's changelog:

e2fsprogs (1.45.3-1) unstable; urgency=medium

  * New upstream version
  * Automatic online file system scrubs is now disabled by default.
They can be enabled by editing /etc/e2scrub.conf.
...
  * Only require the udev, systemd, and cron build dependencies when
building on Linux. (Closes: #931266)
  * Move logsave to its own package.  (Closes: #923372)
  * Update the Czech and Dutch translations

 -- Theodore Y. Ts'o   Sun, 14 Jul 2019 21:01:11 -0400



Best Regards,

--
Aleksi Suhonen

Bug#931932: fixed in ruby-mini-magick 4.9.2-1+deb10u1

[Utkarsh Gupta]

Hey,

On 24/07/19 10:53 am, Salvatore Bonaccorso wrote:
> Hey!
>
> On Wed, Jul 24, 2019 at 10:43:40AM +0530, Utkarsh Gupta wrote:
>> Hey Salvatore,
>>
>> On Tue, 16 Jul 2019 21:07:05 + Salvatore Bonaccorso
>>  wrote:
>>> Source: ruby-mini-magick
>>> Source-Version: 4.9.2-1+deb10u1
>>>
>>> We believe that the bug you reported is fixed in the latest version of
>>> ruby-mini-magick, which is due to be installed in the Debian FTP archive.
>> Where is the source of this upload?
>> I can't seem to find any changelog entries :(
>> Neither any separate branch :(
> Not on salsa. I'm not part of the the ruby team, and apparently the
> master branch did already track the experimental upload, so I just did
> a traditional NMU. The debdiff to import in the packaging repo is
> found at:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931932#23
>
> I would suggest to update to an upstream version which has the fix
> then upload later on to unstable. Would be nice to incoorporate the
> NMU (as well in changelog) so that BTS correctly tracks the fixed
> versions.
>
> Does this help?

Perfecto, thanks! :D


Best,
Utkarsh




signature.asc
Description: OpenPGP digital signature

Bug#931932: fixed in ruby-mini-magick 4.9.2-1+deb10u1

[Salvatore Bonaccorso]

Hey!

On Wed, Jul 24, 2019 at 10:43:40AM +0530, Utkarsh Gupta wrote:
> Hey Salvatore,
> 
> On Tue, 16 Jul 2019 21:07:05 + Salvatore Bonaccorso
>  wrote:
> > Source: ruby-mini-magick
> > Source-Version: 4.9.2-1+deb10u1
> >
> > We believe that the bug you reported is fixed in the latest version of
> > ruby-mini-magick, which is due to be installed in the Debian FTP archive.
> 
> Where is the source of this upload?
> I can't seem to find any changelog entries :(
> Neither any separate branch :(

Not on salsa. I'm not part of the the ruby team, and apparently the
master branch did already track the experimental upload, so I just did
a traditional NMU. The debdiff to import in the packaging repo is
found at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931932#23

I would suggest to update to an upstream version which has the fix
then upload later on to unstable. Would be nice to incoorporate the
NMU (as well in changelog) so that BTS correctly tracks the fixed
versions.

Does this help?

Regards,
Salvatore

Bug#931932: fixed in ruby-mini-magick 4.9.2-1+deb10u1

[Utkarsh Gupta]

Hey Salvatore,

On Tue, 16 Jul 2019 21:07:05 + Salvatore Bonaccorso
 wrote:
> Source: ruby-mini-magick
> Source-Version: 4.9.2-1+deb10u1
>
> We believe that the bug you reported is fixed in the latest version of
> ruby-mini-magick, which is due to be installed in the Debian FTP archive.

Where is the source of this upload?
I can't seem to find any changelog entries :(
Neither any separate branch :(

I am sorry if I am missing anything obvious, but maybe you could help?

> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed. If you
> have further comments please address them to 931...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Salvatore Bonaccorso  (supplier of updated
ruby-mini-magick package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)




signature.asc
Description: OpenPGP digital signature

Bug#932860: wine can not be installed after updating libglib2.0-0 to 2.61.1-2

[fin4478 fin4478]

There are same errors when trying to install wine32 4.0-2 from the
Debian repository. 

On Tue, 23 Jul 2019 17:27:37 -0700 James Lu
 wrote:
> Hi,
> 
> It looks like you're trying to install the Wine packages from WineHQ,
> which are not the same ones provided by Debian. It doesn't look like
> the WineHQ repository has been updated for Bullseye yet, so it's
> likely you'll have to wait for them to add those missing builds.
> 
> Best,
> James
> 
> On 2019-07-23 5:02 p.m., fin4478 fin4478 wrote:
> > Package: wine32
> > Version: 4.0-2
> > 
> > To prevent warnings in the file .xsession-errors with the Xfce
> > 4.13.3 desktop libglib2.0-0 must be updated to the version 2.60.
> > This removes wine and many of its libraries. Reinstalling wine
> > shows the following problems:
> > xfce@optipc:~$ sudo aptitude install winehq-staging
> > The following NEW packages will be installed:
> >   acl{a} glib-networking:i386{a} gstreamer1.0-plugins-base:i386{a} 
> >   libasound2-plugins:i386{a} libatk-bridge2.0-0:i386{a}
> > libatk1.0-0:i386{a} libatspi2.0-0:i386{a} libavcodec58:i386{a}
> > libbz2-1.0:i386{a} libcairo-gobject2:i386{a} libcolord2:i386{a}
> > libcroco3:i386{a} libgdbm-compat4:i386{a} libgdbm6:i386{a}
> > libgdk-pixbuf2.0-0:i386{a} libgstreamer-plugins-base1.0-0:i386{a}
> > libgstreamer1.0-0:i386{a} libgtk-3-0:i386{a} libharfbuzz0b:i386{a}
> > libieee1284-3{a} libieee1284-3:i386{a} libjson-glib-1.0-0:i386{a}
> > libmariadb3:i386{a} libpango-1.0-0:i386{a}
> > libpangocairo-1.0-0:i386{a} libpangoft2-1.0-0:i386{a}
> > libpci3:i386{a} libperl5.28:i386{a} librest-0.7-0:i386{a}
> > librsvg2-2:i386{a} librsvg2-common:i386{a} libsane{a}
> > libsane:i386{a} libsane-common{a} libsensors-config{ab}
> > libsensors5{a} libsensors5:i386{a} libsnmp-base{a} libsnmp30{a}
> > libsnmp30:i386{a} libsoup-gnome2.4-1:i386{a} libsoup2.4-1:i386{a}
> > sane-utils{a} update-inetd{a} wine-staging{a} wine-staging-amd64{a}
> > wine-staging-i386:i386{a} winehq-staging The following packages
> > will be REMOVED: bind9-host{u} cgroupfs-mount{u} dkms{u}
> > fonts-wine{u} geoip-database{u} gtk2-engines-xfce{u}
> > i965-va-driver:i386{u} intel-media-va-driver:i386{u}
> > libasyncns0:i386{u} libavahi-common-data:i386{u} libavahi-core7{u}
> > libavcodec57:i386{u} libavutil55:i386{u} libbind9-161{u}
> > libcom-err2:i386{u} libdaemon0{u} libdatrie1:i386{u} libdns1104{u}
> > libexif12:i386{u} libexo-1-0{u} libfaudio0{u} libflac8:i386{u}
> > libfstrm0{u} libgcrypt20:i386{u} libgd3:i386{u} libgeoip1{u}
> > libgeos-3.7.1{u} libgmp10:i386{u} libgomp1:i386{u} libgpm2:i386{u}
> > libgsoap-2.8.75{u} libgtksourceview-3.0-1{u}
> > libgtksourceview-3.0-common{u} libhogweed4:i386{u} libice6:i386{u}
> > libicu63:i386{u} libigdgmm9:i386{u} libintl-perl{u}
> > libintl-xs-perl{u} libisc1100{u} libisccc161{u} libisccfg163{u}
> > libjbig0:i386{u} libjim0.77{u} libk5crypto3:i386{u}
> > libkeybinder-3.0-0{u} libkeyutils1:i386{u} libkrb5support0:i386{u}
> > libllvm7{u} libltdl7:i386{u} liblwres161{u} liblz4-1:i386{u}
> > libmbim-glib4{u} libmbim-proxy{u} libmodule-find-perl{u}
> > libmodule-scandeps-perl{u} libnettle6:i386{u} libnotify-bin{u}
> > libnuma1:i386{u} libp11-kit0:i386{u} libpixman-1-0:i386{u}
> > libproc-processtable-perl{u} libprotobuf-c1{u} libqmi-glib5{u}
> > libqmi-proxy{u} libreadline7{u} libsasl2-2:i386{u}
> > libsasl2-modules:i386{u} libsasl2-modules-db:i386{u} libsm6:i386{u}
> > libsndfile1:i386{u} libsndio7.0:i386{u} libsort-naturally-perl{u}
> > libsoxr0:i386{u} libstb0{u} libstb0:i386{u} libswresample2:i386{u}
> > libsystemd0:i386{u} libtasn1-6:i386{u} libterm-readkey-perl{u} 

Bug#932860: wine can not be installed after updating libglib2.0-0 to 2.61.1-2

[fin4478 fin4478]

I  am using the version 2.61.1-2 from the experimental repository and it
does have the i386 version. I did notice that the i386 version is
missing with the version 2.60. I was unsure when I wrote this bug
report and used the 2.60 number.

Processed: Re: Bug#932860: wine can not be installed after updating libglib2.0-0 to 2.60

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:glib2.0
Bug #932860 [wine32] wine can not be installed after updating libglib2.0-0 to 
2.60
Bug reassigned from package 'wine32' to 'src:glib2.0'.
No longer marked as found in versions wine/4.0-2.
Ignoring request to alter fixed versions of bug #932860 to the same values 
previously set
> forcemerge 932678 -1
Bug #932678 [src:glib2.0] glib2.0: tests timeout on i386 and mips
Bug #932860 [src:glib2.0] wine can not be installed after updating libglib2.0-0 
to 2.60
Severity set to 'serious' from 'normal'
Marked as found in versions glib2.0/2.60.5-1.
Merged 932678 932860

-- 
932678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932678
932860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 932861 932855 932859

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 932861 932855 932859
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Severity set to 'critical' from 'normal'
Bug #932859 [e2fsprogs] logsave not found
Severity set to 'critical' from 'normal'
Merged 932855 932859 932861
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932855: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932855
932859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932859
932861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932874: logsave: Insufficient Breaks/Replaces on e2fsprogs

[Sven Joachim]

Package: logsave
Version: 1.45.3-1
Severity: serious

Installing logsave without upgrading e2fsprogs fails:

,
| Preparing to unpack .../logsave_1.45.3-1_amd64.deb ...
| Unpacking logsave (1.45.3-1) ...
| dpkg: error processing archive 
/var/cache/apt/archives/logsave_1.45.3-1_amd64.deb (--install):
|  trying to overwrite '/sbin/logsave', which is also in package e2fsprogs 
1.45.2-1
`

There are a Replaces/Breaks relationships on e2fsprogs (<< 1.45.2-1)
which need to be bumped to (<< 1.45.3-1).


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.60-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages logsave depends on:
ii  libc6  2.28-10

logsave recommends no packages.

logsave suggests no packages.

-- no debconf information

Bug#932861: boot failure because e2fsprogs should depend on logsave

[Ben Caradoc-Davies]

Thanks, Kyle. I took the liberty of bumping this to critical severity 
and updating the title because it breaks the whole system (failure to boot).


After booting my system with the previous kernel/initramfs, I was able 
to install logsave, but also needed to run "update-initramfs -u" to 
update the latest initramfs to include logsave before it was able to boot.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Processed: retitle 932861 to boot failure because e2fsprogs should depend on logsave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 932861 boot failure because e2fsprogs should depend on logsave
Bug #932861 [e2fsprogs] e2fsprogs should depend on logsave
Changed Bug title to 'boot failure because e2fsprogs should depend on logsave' 
from 'e2fsprogs should depend on logsave'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932872: [libkscreenlocker5] Doesn't lock automatically by timeout

[Alex Volkov]

Package: libkscreenlocker5
Version: 5.14.5-1
Severity: grave

--- Please enter the report below this line. ---

Doesn't lock automatically by timeout, which presents a security issue. Seems 
to work in a newly created test user setup, and randomly works sometimes in my 
user, but I have no idea what makes in work. Probably some app "inhibits" the 
automatic timeout, but I have no idea how to check it with all that 
"brilliant" dbus crap.  Ubuntu has https://wiki.ubuntu.com/
DebuggingScreenLocking, but it's for Gnome, not KDE.


--- System information. ---
Architecture: 
Kernel:   Linux 4.19.37-bootes0-iommu-p-1000

Debian Release: 10.0
  991 stable  security.debian.org 
  991 stable  ftp.fi.debian.org 
  990 buster-backports ftp.debian.org 
   99 stable  www.deb-multimedia.org 
  500 stable  dl.google.com 
  500 stable  deb.torproject.org 

--- Package information. ---
Depends (Version) | Installed
=-+-
kpackagetool5 | 5.54.0-1
libc6   (>= 2.28) | 
libkf5configcore5 (>= 5.24.0) | 
libkf5configgui5  (>= 4.97.0) | 
libkf5coreaddons5 (>= 4.97.0) | 
libkf5crash5  (>= 4.96.0) | 
libkf5declarative5   (>= 5.50.0~) | 
libkf5globalaccel-bin | 
libkf5globalaccel5 (>= 5.0.0) | 
libkf5i18n5   (>= 4.97.0) | 
libkf5idletime5   (>= 4.96.0) | 
libkf5notifications5  (>= 4.96.0) | 
libkf5package5(>= 5.42.0) | 
libkf5quickaddons5   (>= 5.50.0~) | 
libkf5waylandclient5 (>= 4:5.5.0) | 
libkf5waylandserver5 (>= 4:5.6.2) | 
libkf5windowsystem5   (>= 5.25.0) | 
libpam0g(>= 0.99.7.1) | 
libqt5core5a  (>= 5.11.0~rc1) | 
libqt5dbus5  (>= 5.11.0~) | 
libqt5gui5   (>= 5.11.0~) | 
libqt5network5   (>= 5.11.0~) | 
libqt5qml5 (>= 5.0.2) | 
libqt5quick5   (>= 5.2.0) | 
libqt5widgets5   (>= 5.11.0~) | 
libqt5x11extras5   (>= 5.6.0) | 
libseccomp2   (>= 0.0.0~20120605) | 
libstdc++6 (>= 4.4.0) | 
libwayland-client0(>= 1.9.91) | 
libwayland-server0  (>= 1.3~) | 
libx11-6  | 
libxcb-keysyms1(>= 0.4.0) | 
libxcb1   | 
libxi6(>= 2:1.2.99.4) | 


Recommends   (Version) | Installed
==-+-===
kde-config-screenlocker| 5.14.5-1


Package's Suggests field is empty.

Processed: severity of 932861 is critical

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 932861 critical
Bug #932861 [e2fsprogs] e2fsprogs should depend on logsave
Severity set to 'critical' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932635: [Pkg-electronics-devel] Bug#932635: iverilog ftbfs in unstable

[أحمد المحمودي]

On Sun, Jul 21, 2019 at 04:06:17PM +0200, Matthias Klose wrote:
>dh_auto_test -a
>   make -j1 check VERBOSE=1
> make[1]: Entering directory '/<>'
> mv parse.cc.h parse.h 2>/dev/null || mv parse.hh parse.h
> mv: cannot stat 'parse.hh': No such file or directory
> make[1]: *** [Makefile:259: parse.h] Error 1
---end quoted text---

 suspect a problem in toolchain, because previously the build didn't 
 attempt to do this during 'make check':
 mv parse.cc.h parse.h 2>/dev/null || mv parse.hh parse.h


-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#932865: python-qrtools: not installable: depends on python2 version of zbar

[Adam Borowski]

Package: python-qrtools
Version: 1.4~bzr32-1
Severity: grave
Justification: renders package unusable

Hi!
This package depends on python-zbar, which has already been removed as part
of the python2-rm transition.  This obviously makes it non-installable.


Meow!
-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.1-00036-gf2c1d208af28 (SMP w/64 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages python-qrtools depends on:
ii  python   2.7.16-1
pn  python-pil   
pn  python-zbar  
pn  qrencode 

python-qrtools recommends no packages.

python-qrtools suggests no packages.

Bug#932861: e2fsprogs should depend on logsave

[Kyle Robbertze]

Package: e2fsprogs
Version: 1.45.3-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

After upgrading e2fsprogs to 1.45.3-1, my system refused to boot with
the error:

> /init: line 398: logsave: not found
>
> The root filesystem on /dev/sda3 requires a manual fsck

I was then dropped back in to the initramfs shell. After ensuring that
the file system was clean using fsck and rebooting, the same issue
occured. The solution was to use a live image to chroot into the system
and install logsave. The system then booted normally.

Thus, the suggests on logsave should be replaced with a depends, as the
package is unusable without it.

Thanks
Kyle

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcom-err2  1.45.3-1
ii  libext2fs2   1.45.3-1
ii  libss2   1.45.3-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
ii  e2fsprogs-l10n  1.45.3-1

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
pn  gpart  
ii  logsave1.45.3-1
ii  parted 3.2-25+b1

-- no debconf information

Processed: severity of 922434 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # emacsXX transitional packages have been removed, package is uninstallable 
> in unstable
> severity 922434 serious
Bug #922434 [sass-elisp] sass-elisp: Should depend on generic emacs
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
922434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932856: mariadb-client-10.3: mysqldump uses 10.3 options with pre-10.3 servers and breaks

[Daniel Fussell]

Package: mariadb-client-10.3
Version: 1:10.3.15-1
Severity: critical
Tags: upstream
Justification: causes serious data loss

Dear Maintainer,

mysqldump is unable to backup triggers and routines from any pre-10.3
version server

From the upstream bug-report ( https://jira.mariadb.org/browse/MDEV-17429):

When issuing a 10.3 mysqldump command to dump triggers and routines
from a 10.2 server, the tool breaks because it tries to issue a SHOW
PACKAGES command which is not supported in 10.2 and earlier releases.

mysqldump --quick --routines --triggers --no-create-info
--skip-lock-tables --no-data --compress -h 10.10.16.138 -u
mariadb_mock_import -p myschema



mysqldump: Couldn't execute 'SHOW PACKAGE STATUS WHERE Db =
'myschema'': You have an error in your SQL syntax; check the manual
that corresponds to your MariaDB server version for the right syntax
to use near 'PACKAGE STATUS WHERE Db = 'myschema'' at line 1 (1064)

Running mysqldump without the --triggers and --routines flags will
backup the database structure and data, but will lose the associated
triggers and routines.  For admins and developers, loading the dump back
into a server would require manually creating the triggers from some
previous backup or repository (assuming a viable backup exists).

Running mysqldump with --triggers and --routines flags enabled will fail
entirely, potentially breaking backup scripts and cron jobs that depend
on it.  While this will not lose data directly, it does preclude the
option of restoring databases when a server upgrade fails, or tables are
corrupted, or when a mistaken drop/update/replace/insert statement is
issued.

A successful database dump (including triggers and routines) is expected.

The mysqldump 10.3 server version incompatibility is reported to be
fixed in 10.3.17.

-- 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, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-client-10.3 depends on:
ii  debianutils   4.8.6.1
ii  libc6 2.28-10
ii  libconfig-inifiles-perl   3.01-1
ii  libgnutls30   3.6.7-4
ii  libstdc++6    8.3.0-6
ii  mariadb-client-core-10.3  1:10.3.15-1
ii  perl  5.28.1-6
ii  zlib1g    1:1.2.11.dfsg-1

Versions of packages mariadb-client-10.3 recommends:
ii  libdbd-mysql-perl 4.050-2
ii  libdbi-perl   1.642-1+b1
ii  libterm-readkey-perl  2.38-1

mariadb-client-10.3 suggests no packages.

-- no debconf information

Bug#931932: marked as done (CVE-2019-13574)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jul 2019 20:48:02 +
with message-id 
and subject line Bug#931932: fixed in ruby-mini-magick 4.9.2-1.1
has caused the Debian Bug report #931932,
regarding CVE-2019-13574
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
931932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-mini-magick
Severity: grave
Tags: security

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13574

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: ruby-mini-magick
Source-Version: 4.9.2-1.1

We believe that the bug you reported is fixed in the latest version of
ruby-mini-magick, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 931...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated ruby-mini-magick 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 13 Jul 2019 21:51:59 +0200
Source: ruby-mini-magick
Architecture: source
Version: 4.9.2-1.1
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Salvatore Bonaccorso 
Closes: 931932
Changes:
 ruby-mini-magick (4.9.2-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Don't allow remote shell execution (CVE-2019-13574) (Closes: #931932)
Checksums-Sha1:
 60e7666502bdf1bbfb2cc52ac856d50838a7711b 2395 ruby-mini-magick_4.9.2-1.1.dsc
 dcce641d62e7554933595efc2691ca4a98d3210e 5972 
ruby-mini-magick_4.9.2-1.1.debian.tar.xz
 b07b5e74ee75bfba7cf2aadc83793f1ba80a9cd1 7270 
ruby-mini-magick_4.9.2-1.1_source.buildinfo
Checksums-Sha256:
 d6673f687e334c022f29571e2019908243927fa12d144e387b951af50b8171a5 2395 
ruby-mini-magick_4.9.2-1.1.dsc
 0dd8d2ae0b91bb1ca04d567ace60b2e352f8ed15246812c82147f0803e920384 5972 
ruby-mini-magick_4.9.2-1.1.debian.tar.xz
 9c4e4642b2b30dfe07da7321e47582f8bd3023cb9919b2bd2af43d92f210d14c 7270 
ruby-mini-magick_4.9.2-1.1_source.buildinfo
Files:
 655bf85b0935a1412078f8fcaf8a8d9d 2395 ruby optional 
ruby-mini-magick_4.9.2-1.1.dsc
 b1b41629a27110622795bf049e871cee 5972 ruby optional 
ruby-mini-magick_4.9.2-1.1.debian.tar.xz
 256390e9cdc1e7bc7c1b48693d8395ab 7270 ruby optional 
ruby-mini-magick_4.9.2-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl0qNptfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89ECsgP/1uXBn8yYqWtuUYvKh85nynpT0ntop9G
15emq0ROnklOBU5ka9kpco3WWMTQZdHRnRYBicvfvdbci1+gb5JfXR3G2jFScuSJ
ggCnYRyr6C522ujnF2IFlswrP9+mY0lU6dc9ni/Y+URFSLEEkK85YM98PgIcprN2
FxxPhhnv6Ljaz35SWbI89fTBRGmZY3T8IguYNye5BZJLFOiQBaSrr+eTf7f8Tt/Y
W5xl5Ve6eqfNB+PvKurcYBXs6OytJl8hFjLtaR8Wf5mbco9m6eKX5kLexvbtDpMh
yiZgx1lDwQ/mGAq9F2zZAAd8yO65TK4KF7YpMY3LD/V5+RUIYKOtVO2ZBydRl026
y2i1IuRqwdAmub6Z2I9/MixCiRY+gExkxhGe8/CztJcGoVh1Qzzp1b8Y68P8iC/q
85FHFbgtopRCGJgpizrZNpvfAySr6Ev8C/ERG9XoL0QxO7fOVo+opKUfQRyTP5OM
Xfu4Ks2BrLyn57fbUxHN0ltUFcgQuyztIt6deB7kMe//c9sUHa5tV/O/U7cJQMb8
VA1OKc2w5IUbUi/WwObidtTaMc5yVB7heu5T15Dy6vSebgtdQzDnvZQ39yHtbZuh
LS6zS4/nXF3N54mfl14n/prUVJqJfyDIJBEhmsFl+6GUeVjxj/UhAWGU9+LQFVLc
JSZyDnelsz8G
=7paR
-END PGP SIGNATURE End Message ---

Bug#932833: marked as done (postgresql-11-postgis-2.5-scripts: Version 2.5.2+dfsg-1 has no content outside /usr/share/doc/)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jul 2019 20:45:17 +
with message-id 
and subject line Bug#932833: fixed in postgis 3.0.0~alpha3+dfsg-1~exp2
has caused the Debian Bug report #932833,
regarding postgresql-11-postgis-2.5-scripts: Version 2.5.2+dfsg-1 has no 
content outside /usr/share/doc/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
932833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-11-postgis-2.5-scripts
Version: 2.5.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The first symptom I noticed was in psql, complaining that 
 > create extension postgis;
ERROR:  could not open extension control file 
"/usr/share/postgresql/11/extension/postgis.control": No such file or directory


I believe the cause is that upgrading postgresql-11-postgis-2.5-scripts to 
version 2.5.2
deleted all the useful contents of this package, as shown below.

After downgrading both postgresql-11-postgis-2.5 and 
postgresql-11-postgis-2.5-scripts
to 2.5.1+dfsg-1, the extension seems to be working again.


Thank you for your help.





root@behenian:/var/cache# dpkg -c 
./apt/archives/postgresql-11-postgis-2.5-scripts_2.5.2+dfsg-1_all.deb
drwxr-xr-x root/root 0 2019-07-07 06:12 ./
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/share/
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-07-07 06:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/
-rw-r--r-- root/root  1088 2019-02-01 02:47 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/NEWS.Debian.gz
-rw-r--r-- root/root 16286 2019-07-07 06:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.Debian.gz
-rw-r--r-- root/root488667 2019-03-11 12:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.gz
-rw-r--r-- root/root 47516 2019-07-07 06:10 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/copyright
root@behenian:/var/cache#



Vs

root@behenian:/var/cache# dpkg -c 
./apt/archives/postgresql-11-postgis-2.5-scripts_2.5.1+dfsg-1_all.deb
drwxr-xr-x root/root 0 2018-11-21 23:52 ./
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/doc/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/
-rw-r--r-- root/root  1088 2018-04-06 02:26 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/NEWS.Debian.gz
-rw-r--r-- root/root 16223 2018-11-21 23:52 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.Debian.gz
-rw-r--r-- root/root486501 2018-11-18 15:34 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.gz
-rw-r--r-- root/root 47516 2018-09-24 00:21 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/copyright
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/postgresql/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/postgresql/11/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/
-rw-r--r-- root/root 54217 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy.sql
-rw-r--r-- root/root  1227 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy_gist.sql
-rw-r--r-- root/root  2477 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy_minimal.sql
-rw-r--r-- root/root262917 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis.sql
-rw-r--r-- root/root 75034 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_comments.sql
-rw-r--r-- root/root269721 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_for_extension.sql
-rw-r--r-- root/root 23435 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_proc_set_search_path.sql
-rwxr-xr-x root/root150318 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_restore.pl
-rw-r--r-- root/root248504 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_upgrade.sql
-rw-r--r-- root/root255293 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgi

Bug#932833: marked as done (postgresql-11-postgis-2.5-scripts: Version 2.5.2+dfsg-1 has no content outside /usr/share/doc/)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jul 2019 20:45:00 +
with message-id 
and subject line Bug#932833: fixed in postgis 2.5.2+dfsg-2
has caused the Debian Bug report #932833,
regarding postgresql-11-postgis-2.5-scripts: Version 2.5.2+dfsg-1 has no 
content outside /usr/share/doc/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
932833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-11-postgis-2.5-scripts
Version: 2.5.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The first symptom I noticed was in psql, complaining that 
 > create extension postgis;
ERROR:  could not open extension control file 
"/usr/share/postgresql/11/extension/postgis.control": No such file or directory


I believe the cause is that upgrading postgresql-11-postgis-2.5-scripts to 
version 2.5.2
deleted all the useful contents of this package, as shown below.

After downgrading both postgresql-11-postgis-2.5 and 
postgresql-11-postgis-2.5-scripts
to 2.5.1+dfsg-1, the extension seems to be working again.


Thank you for your help.





root@behenian:/var/cache# dpkg -c 
./apt/archives/postgresql-11-postgis-2.5-scripts_2.5.2+dfsg-1_all.deb
drwxr-xr-x root/root 0 2019-07-07 06:12 ./
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/share/
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-07-07 06:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/
-rw-r--r-- root/root  1088 2019-02-01 02:47 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/NEWS.Debian.gz
-rw-r--r-- root/root 16286 2019-07-07 06:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.Debian.gz
-rw-r--r-- root/root488667 2019-03-11 12:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.gz
-rw-r--r-- root/root 47516 2019-07-07 06:10 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/copyright
root@behenian:/var/cache#



Vs

root@behenian:/var/cache# dpkg -c 
./apt/archives/postgresql-11-postgis-2.5-scripts_2.5.1+dfsg-1_all.deb
drwxr-xr-x root/root 0 2018-11-21 23:52 ./
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/doc/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/
-rw-r--r-- root/root  1088 2018-04-06 02:26 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/NEWS.Debian.gz
-rw-r--r-- root/root 16223 2018-11-21 23:52 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.Debian.gz
-rw-r--r-- root/root486501 2018-11-18 15:34 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.gz
-rw-r--r-- root/root 47516 2018-09-24 00:21 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/copyright
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/postgresql/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/postgresql/11/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/
-rw-r--r-- root/root 54217 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy.sql
-rw-r--r-- root/root  1227 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy_gist.sql
-rw-r--r-- root/root  2477 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy_minimal.sql
-rw-r--r-- root/root262917 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis.sql
-rw-r--r-- root/root 75034 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_comments.sql
-rw-r--r-- root/root269721 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_for_extension.sql
-rw-r--r-- root/root 23435 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_proc_set_search_path.sql
-rwxr-xr-x root/root150318 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_restore.pl
-rw-r--r-- root/root248504 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_upgrade.sql
-rw-r--r-- root/root255293 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_upgrade_fo

Bug#907020: vnstat: autopkgtest regression

[Teemu Toivola]

On Tue, 23 Jul 2019 19:51:23 +0200
Paul Gevers  wrote:

> > Yes, I've read the dev ref. I also had a chat in #debian-mentors yesterday
> > regarding if doing a NMU would be the correct way of proceeding in this
> > case as I haven't done one before nor have I been active with Debian
> > related packaging any time recently. I got pointed towards PackageSalvaging
> > [1], the MIA team and pinging the maintainer once more. That's why in
> > concluded it wouldn't hurt to ask here before taking any futher actions.
> 
> Concluding from this bug alone that the maintainer is MIA is IMHO a bit
> hasty. This bug received a response last year on the same day that I
> filed the bug. As the bug was, at that time, only severity normal, I'm
> not surprised that it hasn't been fixed, even though it was pending all
> the time. I only raised the severity one week ago. I am *assuming* you
> inspected the lack of response from him on the bugs in the logrotate
> package. I suggest you mention something like that explicitly next time
> (and please confirm if I was rightly assuming).

I haven't contacted MIA and I don't have any intent on trying to hijack
this (or any other) package. That's why I try to ask first before taking
any action so that there's no misunderstandings. I had some suspicions that
the maintainer may have become inactive when the discussion in bug #881811
[3] didn't result in any kind of reaction. After several months had past
and this bug was still open, I tried to contact him a little over a week
ago (before the severity change) offering help but haven't so far received
a reply or a bounce. Due to the severity change, I spent some time learning
how the packaging had been handled to see if there was some reason why the
changes already in Salsa hadn't been uploaded, but couldn't find anything
obvious. I couldn't either find any activity after September 2018 from those
locations that do appear to provide such information ([4] [5] [6]). So yes,
I'm aware that's he is also the maintainer of the logrotate package.

> > As for the NMU, the only thing that isn't fully clear after reading the
> > documentation is the handling of the DELAYED queue when using
> > mentors.debian.net and the behaviour of nmudiff in that situation. Invoking
> > nmudiff with --non-dd (which is mention in the --help output but not on the
> > man page) results in a mail template that doesn't mention the delay
> > anywhere. On the other hand, the template suggested by mentors.debian.net
> > [2] looks more complete/verbose but isn't as clear that the diff file
> > created by nmudiff/debdiff should also be attached for NMUs. Either way, is
> > the lack of 'delay' something I'd need to worry about in this phase?
> 
> It's the sponsor that has to upload to the DELAYED queue, so it's not
> something that you control as the sponsee, I suggest you explicitly
> mention it to your sponsor if you want the NMU to go through DELAYED
> (although your sponsor should be aware of that anyways). That said, an
> RC bug without response from the maintainer for a week is "entitled"
> (quotes very much on purpose, as personally I put more time on all my
> NMU uploads than the dev-ref suggests) to go straight into unstable.

Thanks, that clarifies it. The RFS is in bug #932843 [7].

> > [1] https://wiki.debian.org/PackageSalvaging
> > [2] https://mentors.debian.net/sponsors/rfs-howto/vnstat
> 
> Paul
> 
> PS: if --help has more info than the man page, I suggest you file a bug
> about that if it doesn't exist already.

Ok, I'll check that one too.


[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881811
[4] https://salsa.debian.org/cgzones-guest
[5] https://qa.debian.org/developer.php?email=cgzones%40googlemail.com
[6] https://contributors.debian.org/contributor/cgzones-guest@alioth/
[7] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932843

-Teemu

Bug#932703: marked as done (ifeffit (contrib) b-d's on pgplot5 (non-free) and ftbfs)

[Debian Bug Tracking System]

Your message dated Tue, 23 Jul 2019 21:37:29 +0200
with message-id <20190723193727.ga2...@mapreri.org>
and subject line Re: Bug#932703: ifeffit (contrib) b-d's on pgplot5 (non-free) 
and ftbfs
has caused the Debian Bug report #932703,
regarding ifeffit (contrib) b-d's on pgplot5 (non-free) and ftbfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
932703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ifeffit
Version: 2:1.2.11d-10.2
Severity: serious
Tags: sid buster bullseye

ifeffit (contrib) b-d's on pgplot5 (non-free) and ftbfs.

This is also seen in the buster release.
--- End Message ---
--- Begin Message ---
On Mon, Jul 22, 2019 at 02:27:50AM +0200, Matthias Klose wrote:
> Package: src:ifeffit
> Version: 2:1.2.11d-10.2
> Severity: serious
> Tags: sid buster bullseye
> 
> ifeffit (contrib) b-d's on pgplot5 (non-free) and ftbfs.
> 
> This is also seen in the buster release.

That's perfectly fine for a contrib package: they don't actually need
for their build-deps to be installable.

I've done binary uploads for the readline transition.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---

Bug#932000: In testing

[Felix Lechner]

On Tue, Jul 16, 2019 at 8:07 AM Greg Hudson  wrote:
>
> Candidate patch here:

Thank you. The update works great, although I now have problems with
idmap not working on a kerberized NFSv4 mount.

I write with hesitation. A week has passed and many other packages
were likewise updated. My idmap issue could not be related to cipher
suites in krb5, could it?

Bug#932833: postgresql-11-postgis-2.5-scripts: Version 2.5.2+dfsg-1 has no content outside /usr/share/doc/

[Sebastiaan Couwenberg]

On 7/23/19 8:45 PM, Mark Jeffcoat wrote:
> The first symptom I noticed was in psql, complaining that 
>  > create extension postgis;
> ERROR:  could not open extension control file 
> "/usr/share/postgresql/11/extension/postgis.control": No such file or 
> directory
> 
> 
> I believe the cause is that upgrading postgresql-11-postgis-2.5-scripts to 
> version 2.5.2
> deleted all the useful contents of this package, as shown below.

Yeah, it looks like the arch:all buildd didn't build the -scripts
package properly.

It always worked correctly on my system when building both arch:any &
arch:all together.

We probably need to fix some -indep targets, or just merge them together
to ensure that everything is always built.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#932834: FTBFS: relocation R_X86_64_32 against symbol `PyVersion_Type' can not be used when making a shared object; recompile with -fPIC

[Raphaël Hertzog]

Source: python-apt
Version: 1.8.4
Severity: serious
Justification: FTBFS
User: de...@kali.org
Usertags: origin-kali

Trying to rebuild python-apt in unstable currently fails with:

x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now 
-g -O2 -fdebug-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-write-strings -DDATE="Mar 11 2019" 
-DTIME="11:49:18" -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-3.7/python/acquire.o 
build/temp.linux-x86_64-3.7/python/acquire-item.o 
build/temp.linux-x86_64-3.7/python/apt_pkgmodule.o 
build/temp.linux-x86_64-3.7/python/cache.o 
build/temp.linux-x86_64-3.7/python/cachegroup.o 
build/temp.linux-x86_64-3.7/python/cdrom.o 
build/temp.linux-x86_64-3.7/python/configuration.o 
build/temp.linux-x86_64-3.7/python/depcache.o 
build/temp.linux-x86_64-3.7/python/generic.o 
build/temp.linux-x86_64-3.7/python/hashes.o 
build/temp.linux-x86_64-3.7/python/hashstring.o 
build/temp.linux-x86_64-3.7/python/hashstringlist.o 
build/temp.linux-x86_64-3.7/python/indexfile.o 
build/temp.linux-x86_64-3.7/python/lock.o 
build/temp.linux-x86_64-3.7/python/metaindex.o 
build/temp.linux-x86_64-3.7/python/orderlist.o 
build/temp.linux-x86_64-3.7/python/pkgmanager.o 
build/temp.linux-x86_64-3.7/python/pkgrecords.o 
build/temp.linux-x86_64-3.7/python/pkgsrcrecords.o 
build/temp.linux-x86_64-3.7/python/policy.o 
build/temp.linux-x86_64-3.7/python/progress.o 
build/temp.linux-x86_64-3.7/python/python-apt-helpers.o 
build/temp.linux-x86_64-3.7/python/sourcelist.o 
build/temp.linux-x86_64-3.7/python/string.o 
build/temp.linux-x86_64-3.7/python/tag.o -lapt-pkg -o 
build/lib.linux-x86_64-3.7/apt_pkg.cpython-37m-x86_64-linux-gnu.so
/usr/bin/ld: /tmp/ccZYGg3M.ltrans0.ltrans.o: relocation R_X86_64_32 against 
symbol `PyVersion_Type' can not be used when making a shared object; recompile 
with -fPIC
/usr/bin/ld: /tmp/ccZYGg3M.ltrans1.ltrans.o: relocation R_X86_64_32 against 
symbol `PyPolicy_Type' can not be used when making a shared object; recompile 
with -fPIC
/usr/bin/ld: /tmp/ccZYGg3M.ltrans2.ltrans.o: relocation R_X86_64_32 against 
symbol `PyAcquire_Type' can not be used when making a shared object; recompile 
with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1
dh_auto_build: python3.7 setup.py build --force returned exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Build finished at 2019-07-23T16:52:03Z


-- System Information:
Debian Release: bullseye/sid
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#932833: postgresql-11-postgis-2.5-scripts: Version 2.5.2+dfsg-1 has no content outside /usr/share/doc/

[Mark Jeffcoat]

Package: postgresql-11-postgis-2.5-scripts
Version: 2.5.2+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The first symptom I noticed was in psql, complaining that 
 > create extension postgis;
ERROR:  could not open extension control file 
"/usr/share/postgresql/11/extension/postgis.control": No such file or directory


I believe the cause is that upgrading postgresql-11-postgis-2.5-scripts to 
version 2.5.2
deleted all the useful contents of this package, as shown below.

After downgrading both postgresql-11-postgis-2.5 and 
postgresql-11-postgis-2.5-scripts
to 2.5.1+dfsg-1, the extension seems to be working again.


Thank you for your help.





root@behenian:/var/cache# dpkg -c 
./apt/archives/postgresql-11-postgis-2.5-scripts_2.5.2+dfsg-1_all.deb
drwxr-xr-x root/root 0 2019-07-07 06:12 ./
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/share/
drwxr-xr-x root/root 0 2019-07-07 06:12 ./usr/share/doc/
drwxr-xr-x root/root 0 2019-07-07 06:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/
-rw-r--r-- root/root  1088 2019-02-01 02:47 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/NEWS.Debian.gz
-rw-r--r-- root/root 16286 2019-07-07 06:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.Debian.gz
-rw-r--r-- root/root488667 2019-03-11 12:12 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.gz
-rw-r--r-- root/root 47516 2019-07-07 06:10 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/copyright
root@behenian:/var/cache#



Vs

root@behenian:/var/cache# dpkg -c 
./apt/archives/postgresql-11-postgis-2.5-scripts_2.5.1+dfsg-1_all.deb
drwxr-xr-x root/root 0 2018-11-21 23:52 ./
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/doc/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/
-rw-r--r-- root/root  1088 2018-04-06 02:26 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/NEWS.Debian.gz
-rw-r--r-- root/root 16223 2018-11-21 23:52 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.Debian.gz
-rw-r--r-- root/root486501 2018-11-18 15:34 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/changelog.gz
-rw-r--r-- root/root 47516 2018-09-24 00:21 
./usr/share/doc/postgresql-11-postgis-2.5-scripts/copyright
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/postgresql/
drwxr-xr-x root/root 0 2018-11-21 23:52 ./usr/share/postgresql/11/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/
drwxr-xr-x root/root 0 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/
-rw-r--r-- root/root 54217 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy.sql
-rw-r--r-- root/root  1227 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy_gist.sql
-rw-r--r-- root/root  2477 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/legacy_minimal.sql
-rw-r--r-- root/root262917 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis.sql
-rw-r--r-- root/root 75034 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_comments.sql
-rw-r--r-- root/root269721 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_for_extension.sql
-rw-r--r-- root/root 23435 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_proc_set_search_path.sql
-rwxr-xr-x root/root150318 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_restore.pl
-rw-r--r-- root/root248504 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_upgrade.sql
-rw-r--r-- root/root255293 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/postgis_upgrade_for_extension.sql
-rw-r--r-- root/root 73280 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/raster_comments.sql
-rw-r--r-- root/root297434 2018-11-21 23:52 
./usr/share/postgresql/11/contrib/postgis-2.5/rtpostgis.sql

[ ... and so on for another 200 lines ...]




-- System Information:
Debian Release: bullseye/sid
  APT prefers oldoldstable
  APT policy: (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

postgre

Processed: Re: Bug#842892: java.lang.UnsatisfiedLinkError: libz3java.so: undefined symbol: Z3_solver_get_model

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #842892 [libz3-jni] java.lang.UnsatisfiedLinkError: libz3java.so: undefined 
symbol: Z3_solver_get_model
Severity set to 'grave' from 'important'

-- 
842892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907020: vnstat: autopkgtest regression

[Paul Gevers]

Hi Teemu,

On 23-07-2019 18:06, Teemu Toivola wrote:
>>> as the maintainer appears to be inactive, is a NMU [1] containing the
>>> changes linked in the maintainer's previous message an acceptable solution
>>> for solving this?
>>>
>>> [1] https://mentors.debian.net/package/vnstat (no RFS has yet been sent)
>>
>> I assume you've read the NMU procedure [1]. Which part is unclear to you
>> in resolving the right approach for this issue?
>>
>> [1] https://www.debian.org/doc/manuals/developers-reference/ch05.html#nmu
> 
> Yes, I've read the dev ref. I also had a chat in #debian-mentors yesterday
> regarding if doing a NMU would be the correct way of proceeding in this
> case as I haven't done one before nor have I been active with Debian
> related packaging any time recently. I got pointed towards PackageSalvaging
> [1], the MIA team and pinging the maintainer once more. That's why in
> concluded it wouldn't hurt to ask here before taking any futher actions.

Concluding from this bug alone that the maintainer is MIA is IMHO a bit
hasty. This bug received a response last year on the same day that I
filed the bug. As the bug was, at that time, only severity normal, I'm
not surprised that it hasn't been fixed, even though it was pending all
the time. I only raised the severity one week ago. I am *assuming* you
inspected the lack of response from him on the bugs in the logrotate
package. I suggest you mention something like that explicitly next time
(and please confirm if I was rightly assuming).

> As for the NMU, the only thing that isn't fully clear after reading the
> documentation is the handling of the DELAYED queue when using
> mentors.debian.net and the behaviour of nmudiff in that situation. Invoking
> nmudiff with --non-dd (which is mention in the --help output but not on the
> man page) results in a mail template that doesn't mention the delay
> anywhere. On the other hand, the template suggested by mentors.debian.net
> [2] looks more complete/verbose but isn't as clear that the diff file
> created by nmudiff/debdiff should also be attached for NMUs. Either way, is
> the lack of 'delay' something I'd need to worry about in this phase?

It's the sponsor that has to upload to the DELAYED queue, so it's not
something that you control as the sponsee, I suggest you explicitly
mention it to your sponsor if you want the NMU to go through DELAYED
(although your sponsor should be aware of that anyways). That said, an
RC bug without response from the maintainer for a week is "entitled"
(quotes very much on purpose, as personally I put more time on all my
NMU uploads than the dev-ref suggests) to go straight into unstable.

> [1] https://wiki.debian.org/PackageSalvaging
> [2] https://mentors.debian.net/sponsors/rfs-howto/vnstat

Paul

PS: if --help has more info than the man page, I suggest you file a bug
about that if it doesn't exist already.



signature.asc
Description: OpenPGP digital signature

Bug#932827: django-compat: broken with Django 2.2, FTBFS, not ready

[Thomas Goirand]

Source: django-compat
Version: 1.0.15-2
Severity: serious

Hi,

Django-compat is broken in may ways currently.

1/ It's using the loginview function instead of the LoginView class, as per
the deprecation in Django 1.11.
2/ The tests/settings.py is missing lots of declarations.
3/ Python 2 support has to be removed from this package.

I tried to work on this, but it doesn't look trivial.

Cheers,

Thomas Goirand (zigo)

Bug#931970: gphoto2: autopkgtest failure block readline migration

[Sebastiaan Couwenberg]

On 7/23/19 7:17 PM, Herbert Fortes wrote:
> Can you detail more what is wrong?

See: https://ci.debian.net/packages/g/gphoto2/testing/amd64/

And the log files linked from there.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#931970: gphoto2: autopkgtest failure block readline migration

[Herbert Fortes]

Hi,

On Sat, 13 Jul 2019 07:49:23 +0200 Bas Couwenberg  wrote:
> Source: gphoto2
> Version: 2.5.20-3
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> 
> Dear Maintainer,
> 
> The autopkgtest failures for gphoto2 are blocking the testing migration
> of readline and its reverse dependencies.
> 
> Please fix the tests in your package or remove them.

I ran 'autopkgtest' and see no errors.


All tests have PASSED
autopkgtest [14:14:29]: test upstream-test-suite.sh: ---]
autopkgtest [14:14:29]: test upstream-test-suite.sh:  - - - - - - - - - - 
results - - - - - - - - - -
upstream-test-suite.sh PASS
autopkgtest [14:14:29]:  summary
upstream-test-suite.sh PASS


Can you detail more what is wrong?



Regards,
Herbert

Bug#930676: goplay: Should this package be removed?

[Boyuan Yang]

On Thu, 27 Jun 2019 14:06:06 +0200 Julian Andres Klode  wrote:
> On Sun, Jun 23, 2019 at 03:17:41AM +0200, Markus Koschany wrote:
> > Hello,
> > 
> > On Tue, 18 Jun 2019 12:46:30 +0200 Julian Andres Klode 
> > wrote:
> > > Package: goplay
> > > Severity: serious
> > > 
> > > Hi folks,
> > > 
> > > goplay has not received any updates since 2015, it uses libept,
> > > which we'd like to get rid of eventually I think, as it's also
> > > unmaintained, so I think it would be best to remove it.
> > 
> > I agree with you in general. However, IMHO, can we defer this decision
> > to buster +1 or is this really imminent. AFAIK the package works for
Buster?
> 
> Sure, we can defer this until after the release. 

With the release of Buster, looks like it's time to file removal request. I'm
sending RM bug to FTP Masters soon.

Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#907020: vnstat: autopkgtest regression

[Teemu Toivola]

On Tue, 23 Jul 2019 15:01:54 +0200
Paul Gevers  wrote:

> On 23-07-2019 12:38, Teemu Toivola wrote:
> > On Thu, 23 Aug 2018 11:18:27 +0200
> > Paul Gevers  wrote:
> > 
> >> On 23-08-18 10:50, Christian Göttsche wrote:
> >>> How soon should a new version be uploaded?
> >>
> >> That is fully up to you. If you upload now and the issue is fixed, the
> >> package migrates A LOT faster to testing, than if you wait.
> > 
> > as the maintainer appears to be inactive, is a NMU [1] containing the
> > changes linked in the maintainer's previous message an acceptable solution
> > for solving this?
> > 
> > [1] https://mentors.debian.net/package/vnstat (no RFS has yet been sent)
> 
> I assume you've read the NMU procedure [1]. Which part is unclear to you
> in resolving the right approach for this issue?
>
> [1] https://www.debian.org/doc/manuals/developers-reference/ch05.html#nmu

Yes, I've read the dev ref. I also had a chat in #debian-mentors yesterday
regarding if doing a NMU would be the correct way of proceeding in this
case as I haven't done one before nor have I been active with Debian
related packaging any time recently. I got pointed towards PackageSalvaging
[1], the MIA team and pinging the maintainer once more. That's why in
concluded it wouldn't hurt to ask here before taking any futher actions.

As for the NMU, the only thing that isn't fully clear after reading the
documentation is the handling of the DELAYED queue when using
mentors.debian.net and the behaviour of nmudiff in that situation. Invoking
nmudiff with --non-dd (which is mention in the --help output but not on the
man page) results in a mail template that doesn't mention the delay
anywhere. On the other hand, the template suggested by mentors.debian.net
[2] looks more complete/verbose but isn't as clear that the diff file
created by nmudiff/debdiff should also be attached for NMUs. Either way, is
the lack of 'delay' something I'd need to worry about in this phase?

-Teemu

[1] https://wiki.debian.org/PackageSalvaging
[2] https://mentors.debian.net/sponsors/rfs-howto/vnstat

Bug#932804: terminology-data: contains invalid arch specific file also contained in terminology package

[Sebastian Reichel]

Package: terminology-data
Version: 1.4.1-1
Severity: grave
Justification: renders package unusable

Hi,

terminology-data contains /usr/lib/x86_64-linux-gnu/terminology/tytest
in 1.4.1-1 and 1.5.0-1, which is also contained in terminology (so
package is not installable). Obviously an arch specific file does not
belong into an arch all package and should be removed from terminology-data.

-- Sebastian

Processed: Re: Bug#932307: multipath-tools does not update wwids file

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #932307 [multipath-tools] multipath-tools does not update wwids file
Severity set to 'important' from 'critical'

-- 
932307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932307: multipath-tools does not update wwids file

[Ritesh Raj Sarraf]

Control: severity -1 important

That severity was exaggerated. Works fine over here locally, with an
LIO target setup.

On Wed, 2019-07-17 at 15:20 +0200, root wrote:
> Dear Maintainer,
> 
> * What led up to the situation?
> 
> New Debian 10 Buster fresh installation with HBA cards and disks
> arrays
> multi-attached ((2 HBA cards, 2 arrays of 12 disks, 4 links)
> Disks are all listed correctly in /dev/ or /dev/disk/by-*/
> 
> * What exactly did you do (or not do) that was effective (or
>   ineffective)?
> 
> install multipath-tools (and depencies)
> write wanted aliases in /etc/multipath.conf (see attached file)
> 
> * What was the outcome of this action?
> 
> tryied 'usual' commands, to apply/refresh configuration:
> multipath -F
> multipath -r
> multipath or systemctl restart multipathd.service
> 
> It doesn't work as expected: 'multipath -v2 -ll' should have shown a
> populated devices state map: it's empty.
> 
> /dev/mapper/ is empty. /dev/dm-* are not present.
> 
> /etc/multipath/wwids is not updated/replaced.
> 

Do you not have /etc/multipath/bindings file generated in your case ?
A lot has changed lately in how multipath-tools works and you may have
to fiddle around with settings.

But I have it running fine here on my 2 local setups: sanboot and usual
one.

> * What outcome did you expect instead?
> 
> Aliases in /dev/mapper/ to use with zfs-dkms.
> 
> Note:
> The exact same machine works just fine on Debian 9 Stretch (with zfs-
> dkms).
> A upgrade to Buster, with untouched /etc/multipath.conf works just
> fine also.

You mean the same old configuration file from Stretch works fine on
Buster ?

-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


signature.asc
Description: This is a digitally signed message part

Processed: r-cran-etm: autopkgtest regression: saved results mismatch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #908662 {Done: Graham Inggs } [src:r-cran-etm] 
r-cran-etm: autopkgtest regression: saved results mismatch
Severity set to 'important' from 'serious'

-- 
908662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#908662: r-cran-etm: autopkgtest regression: saved results mismatch

[Graham Inggs]

Control: severity -1 important

Downgrading severity, since the autopkgtests now pass in unstable [1],
to avoid autoremoval warnings in several other packages.

[1] https://ci.debian.net/packages/r/r-cran-etm/unstable/amd64/

Bug#914731: r-bioc-biocparallel: autopkgtest regression

[Graham Inggs]

Control: severity -1 important

Downgrading severity, since the autopkgtests now pass in unstable [1],
to avoid autoremoval warnings in several other packages.

[1] https://ci.debian.net/packages/r/r-bioc-biocparallel/unstable/amd64/

Processed: r-bioc-biocparallel: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #914731 {Done: Dylan Aïssi } [src:r-bioc-biocparallel] 
r-bioc-biocparallel: autopkgtest regression
Severity set to 'important' from 'serious'

-- 
914731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#907020: vnstat: autopkgtest regression

[Paul Gevers]

Hi Teemu

Thanks for your interest in fixing this bug.

On 23-07-2019 12:38, Teemu Toivola wrote:
> On Thu, 23 Aug 2018 11:18:27 +0200
> Paul Gevers  wrote:
> 
>> On 23-08-18 10:50, Christian Göttsche wrote:
>>> How soon should a new version be uploaded?
>>
>> That is fully up to you. If you upload now and the issue is fixed, the
>> package migrates A LOT faster to testing, than if you wait.
> 
> as the maintainer appears to be inactive, is a NMU [1] containing the
> changes linked in the maintainer's previous message an acceptable solution
> for solving this?
> 
> [1] https://mentors.debian.net/package/vnstat (no RFS has yet been sent)

I assume you've read the NMU procedure [1]. Which part is unclear to you
in resolving the right approach for this issue?

Paul

[1] https://www.debian.org/doc/manuals/developers-reference/ch05.html#nmu



signature.asc
Description: OpenPGP digital signature

Bug#932796: Non-DFSG license in dyndns.pl file

[Joao Eriberto Mota Filho]

Package: dyndns
Version: 2016.1021-3
Severity: serious
Tags: upstream

When searching for a license inside dyndns.pl, I found the information shown
below:

  #!/usr/bin/perl
  #
  #   Copyright
  #
  #   Copyright (C) 1999-2016 Jari Aalto
  #
  #   License
  #
  #   This program is free software; you can redistribute it and/or modify
  #   it under the terms of the GNU General Public License as published by
  #   the Free Software Foundation; either version 2 of the License, or
  #   (at your option) any later version.

  [...]

  

  [...]

The last block says about a PROPRIETARY source code. This notice was shown two
times in dyndns main file.

Regards,

Eriberto

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

Processed: Re: Bug#932762: fakeroot file somefile: Bad system call

[Debian Bug Tracking System]

Processing control commands:

> reopen 932762
Bug #932762 {Done: Christoph Biedl } [file] 
fakeroot file somefile: Bad system call
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions file/1:5.37-4.
> severity 932762 important
Bug #932762 [file] fakeroot file somefile: Bad system call
Severity set to 'important' from 'serious'
> retitle 932762 Needs a sane solution for running under LD_PRELOAD like 
> fakeroot
Bug #932762 [file] fakeroot file somefile: Bad system call
Changed Bug title to 'Needs a sane solution for running under LD_PRELOAD like 
fakeroot' from 'fakeroot file somefile: Bad system call'.

-- 
932762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932762: fakeroot file somefile: Bad system call

[Christoph Biedl]

Control: reopen 932762
Control: severity 932762 important
Control: retitle 932762 Needs a sane solution for running under LD_PRELOAD like 
fakeroot

[ Taking Niels into the loop. I'm sorry the first approach didn't work out. ]

With the problem preliminary fixed, the whole story needs some
consideration. Aside, I noticed too late fakeroot-tcp is still broken,
so another upload will follow soon-ish.


Situation unchanged: When running under fakeroot, the file binary does
(via libfakeroot) additional syscalls that are not whitelisted in the
seccomp filter, hence breaking operation. This might happen in other
LD_PRELOAD mechanisms as well.

Helmut Grohne wrote...

> The blocked syscall is 68 aka msgget. It is an IPC call used by
> fakeroot to communicate the faked permissions. I think allowing more
> syscalls in the sandbox is a bad idea.
> 
>  * You're whitelisting amd64 syscalls now. Other architectures use
>different numbers and hunting them down for each and every
>architecture is painful.

JFTTR, whitelisting is done by a symbolic name - so this should work on
all archs.

>  * fakeroot uses msgget when used with faked-sysv. For use with
>faked-tcp, you will need socket and connect and stuff.
>  * Blocking IPC or network was exactly the job of seccomp. If you allow
>these calls, you are significantly weakening the sandbox.

Yes, figured that in the meantime, consider the whitelisting approach
dead for that reason.

>  * Have you tried faketime, fakechroot, eatmydata, ...?

faketime and eatmydata yes - but I assume there exist several more
packages using LD_PRELOAD during build.

> Let me propose a much simpler option: Check for the presence of
> LD_PRELOAD and imply -S when it is non-empty.

This however is very broad and and has a risk risc of silently
disabling this security feature in a production system, so, no.

What I am looking for now is to disable seccomp in a build environment
only. For the moment I can think of two ways to handle this:


* Have a second file package without seccomp support

A second file package without seccomp, "Package: file-buildd",
"Provides: file", and the toolchain/debhelper has an explicit
dependency on that one. This would require all buildsystems have
an explicit dependency on that packages, debhelper to start with.

My only concern is users will start using this, "because the other one
just creates trouble". Hence the somewhat obscure name. Feel free to
propose another one.


* Have a build system detection in file(1)

The programs using LD_PRELOAD often leave specific data in the
environment, file(1) could use that one, in theory. However, pseudo(1)
does not, and as that detection should be generic, I fail to see this
road leads anywhere.

So the final solution I can think of is a distinct environment variable
set by debhelper I could depend on.


In either way, this requires some coordination with debhelper, and
theoretically other build systems as well. And since the first one seems
way saner to me, I am willing to take the additional efforts required
(packaging, NEW) upon me as they are one-time only.

Christoph



signature.asc
Description: PGP signature

Bug#932659: Reproduced on a clean chroot

[Pirate Praveen]

I was able to reproduce in a clean sid chroot.

Created chroot with debootstrap, chroot to directory, install nodejs, node-y18n

node -e "require('y18n');"  internal/modules/cjs/loader.js:583  
throw err;  ^   
Error: Cannot find 
module 'y18n'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15) 
at Function.Module._load 
(internal/modules/cjs/loader.js:507:25)at 
Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18)  
at [eval]:1:1   at 
Script.runInThisContext (vm.js:96:20)at Object.runInThisContext 
(vm.js:303:38)   at Object. ([eval]-wrapper:6:22) at 
Module._compile (internal/modules/cjs/loader.js:689:30) 
 at evalScript (internal/bootstrap/node.js:587:27)

ls /usr/share/nodejs 
y18n
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#907020: vnstat: autopkgtest regression

[Teemu Toivola]

On Thu, 23 Aug 2018 11:18:27 +0200
Paul Gevers  wrote:

> On 23-08-18 10:50, Christian Göttsche wrote:
> > How soon should a new version be uploaded?
> 
> That is fully up to you. If you upload now and the issue is fixed, the
> package migrates A LOT faster to testing, than if you wait.

as the maintainer appears to be inactive, is a NMU [1] containing the
changes linked in the maintainer's previous message an acceptable solution
for solving this?

[1] https://mentors.debian.net/package/vnstat (no RFS has yet been sent)

-Teemu

Processed: issue with iptables -L

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #932498 [iptables] iptables -L goes into uninteruptable sleep
Severity set to 'normal' from 'critical'
> tags -1 = moreinfo unreproducible
Bug #932498 [iptables] iptables -L goes into uninteruptable sleep
Added tag(s) unreproducible and moreinfo; removed tag(s) a11y.

-- 
932498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#932498: issue with iptables -L

[Arturo Borrero Gonzalez]

Control: severity -1 normal
Control: tags -1 = moreinfo unreproducible

I can't reproduce this bug:

% sudo iptables -L
[sudo] password for arturo:

Chain INPUT (policy ACCEPT)
target prot opt source   destination

Chain FORWARD (policy ACCEPT)
target prot opt source   destination

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination


Please include more context information or I will close the bug as bogus.