Processing commands for cont...@bugs.debian.org:
> affects 932678 src:wine src:wine-development
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
Added indication that 932678 affects src:wine
Processing control commands:
> owner -1 !
Bug #932257 [libdbd-oracle-perl] libdbd-oracle-perl: unsatisfiable dependencies
Owner recorded as Alex Muntada .
> severity -1 minor
Bug #932257 [libdbd-oracle-perl] libdbd-oracle-perl: unsatisfiable dependencies
Severity set to 'minor' from 'grave'
--
Control: owner -1 !
Control: severity -1 minor
Hector said:
> Thanks for the explanation, I was just checking repository
> consistency for buster and came up with this issue. I leave
> it up to you to downgrade severity accordingly or close the
> bug. Fixing the README installation one way or
Package: pspp
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious
pspp build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Package: gri
Version: 3.5.2-1
Tags: bullseye, sid, patch
Severity: serious
gri build-depends on texlive-generic-reccomended which is no longer built by
the texlive-base source package. Please build-depend on texlive-plain-generic
instead.
Processing commands for cont...@bugs.debian.org:
> tags 932874 + pending
Bug #932874 [logsave] logsave: Insufficient Breaks/Replaces on e2fsprogs
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
932874:
Your message dated Thu, 25 Jul 2019 01:34:48 +
with message-id
and subject line Bug#932912: fixed in hhsuite 3.2.0-2
has caused the Debian Bug report #932912,
regarding hhsuite: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 929581 important
Bug #929581 [zfs-dkms] zfs-dkms: fails to build module for 4.19.0-5-686-pae
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
929581:
Package: vistrails
Severity: serious
Version: 2.2.4-1
Tags: bullseye, sid
vistrails depends on python-usagestats which is no longer built by the
usagestats source package.
If you want your Package to remain in Debian you probablly need to migrate to
python3.
Source: ghc
Version: 8.6.5+dfsg1-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
User: debian-s...@lists.debian.org
Usertags: s390x
Hi!
GHC currently fails to build from source on all architectures which use
the unregisterised compiler.
It fails with:
Control: tags 931808 + pending
Dear maintainer,
I've prepared an NMU for comix (versioned as 4.0.4-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru comix-4.0.4/debian/changelog comix-4.0.4/debian/changelog
---
Processing control commands:
> tags 931808 + pending
Bug #931808 [comix] comix: broken after python-pil:amd64 5.4.1-2 -> 6.1.0-1
upgrade
Added tag(s) pending.
--
931808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> tags 825381 + pending
Bug #825381 [makejail] makejail fails on updating symbolic links
Added tag(s) pending.
--
825381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 825381 + pending
Dear maintainer,
I've prepared an NMU for makejail (versioned as 0.0.5-10.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
It was necessary to apply the patch directly to the upstream
makejail file that is attached to the
Package: librust-docopt-dev
Version: 1.0.2-1
Severity: serious
Tags: buster, sid
librust-docopt-dev depends on the virtual package
librust-strsim-0.7+default-dev which is no longer provider by
librust-strsim-dev. The virtual package seems to have been renamed to
Your message dated Wed, 24 Jul 2019 21:50:37 +
with message-id
and subject line Bug#892648: fixed in xcffib 0.8.1-0.1
has caused the Debian Bug report #892648,
regarding xcffib FTBFS: xcffibgen: Map.!: given key is not an element in the map
to be marked as done.
This means that you claim
Your message dated Wed, 24 Jul 2019 21:49:42 +
with message-id
and subject line Bug#903619: fixed in haskell-language-python 0.5.6-1
has caused the Debian Bug report #903619,
regarding haskell-language-python FTBFS build hangs.
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tags -1 patch pending
Bug #892648 [src:xcffib] xcffib FTBFS: xcffibgen: Map.!: given key is not an
element in the map
Added tag(s) pending and patch.
--
892648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892648
Debian Bug Tracking System
Contact
control: tags -1 patch pending
On Sun, 11 Mar 2018 20:47:29 +0200 Adrian Bunk wrote:
> Source: xcffib
> Version: 0.5.1-1
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/xcffib.html
>
> ...
> Linking dist/build/GeneratorTests.hs/GeneratorTests.hs ...
>
Your message dated Wed, 24 Jul 2019 21:49:42 +
with message-id
and subject line Bug#917171: fixed in haskell-language-python 0.5.6-1
has caused the Debian Bug report #917171,
regarding FTBFS on all architectures
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 24 Jul 2019 19:08:09 +
with message-id
and subject line Bug#830371: fixed in librevisa 0.0.20130812-2.2
has caused the Debian Bug report #830371,
regarding librevisa: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned
exit code 2
to be marked as done.
This means
在 2019-07-24三的 20:34 +0200，Simon Richter写道：
> Hi,
>
> > override_dh_auto_test:
> > ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> > -dh_auto_test
> > endif
>
> Yes, that's fine with me. I'm not even sure the conditional is needed,
> shouldn't dh_auto_test already
Hi,
> override_dh_auto_test:
> ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
> -dh_auto_test
> endif
Yes, that's fine with me. I'm not even sure the conditional is needed,
shouldn't dh_auto_test already look at DEB_BUILD_OPTIONS?
Simon
Hi Simon,
In this case I guess we could make tests optional so that the whole build will
not fail even if there's some test failures. In this way at lease we could
have some usable libraries in the archive.
The patch would be pretty simple by adding the following lines in
debian/rules:
Hi,
On Wed, Jul 24, 2019 at 01:30:26PM -0400, Boyuan Yang wrote:
> I tried to rebuild this package in my local sbuild chroot and the result
> appears to be successful. I plan to make a (no-change) NMU upload onto Sid to
> see if a sourceful rebuild would solve this issue.
This is an error
On Wed, Jul 24, 2019 at 05:46:50AM +0200, Sven Joachim wrote:
> 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:
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932881: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932881,
regarding [src:linux] Misses 'logsave' as a dependency, so the system stops
booting
to be marked as done.
This means that you
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932888: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932888,
regarding boot failure because e2fsprogs should depend on logsave
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932888: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932888,
regarding [src:linux] Misses 'logsave' as a dependency, so the system stops
booting
to be marked as done.
This means that you
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932888: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932888,
regarding e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932888: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932888,
regarding add dependency on logsave
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932888: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932888,
regarding logsave not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932881: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932881,
regarding logsave not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932881: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932881,
regarding boot failure because e2fsprogs should depend on logsave
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932881: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932881,
regarding e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932861: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932861,
regarding add dependency on logsave
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932861: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932861,
regarding boot failure because e2fsprogs should depend on logsave
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932859: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932859,
regarding [src:linux] Misses 'logsave' as a dependency, so the system stops
booting
to be marked as done.
This means that you
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932861: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932861,
regarding [src:linux] Misses 'logsave' as a dependency, so the system stops
booting
to be marked as done.
This means that you
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932859: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932859,
regarding add dependency on logsave
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932881: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932881,
regarding add dependency on logsave
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932861: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932861,
regarding logsave not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932855: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932855,
regarding boot failure because e2fsprogs should depend on logsave
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932859: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932859,
regarding logsave not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 24 Jul 2019 17:35:12 +
with message-id
and subject line Bug#932861: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932861,
regarding e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932855: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932855,
regarding [src:linux] Misses 'logsave' as a dependency, so the system stops
booting
to be marked as done.
This means that you
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932859: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932859,
regarding boot failure because e2fsprogs should depend on logsave
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932855: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932855,
regarding add dependency on logsave
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932855: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932855,
regarding logsave not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932859: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932859,
regarding e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 24 Jul 2019 17:35:11 +
with message-id
and subject line Bug#932855: fixed in e2fsprogs 1.45.3-2
has caused the Debian Bug report #932855,
regarding e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
to be marked as done.
This means that you claim that the problem
X-Debbugs-CC: s...@debian.org
Dear librevisa maintainer,
I tried to rebuild this package in my local sbuild chroot and the result
appears to be successful. I plan to make a (no-change) NMU upload onto Sid to
see if a sourceful rebuild would solve this issue.
Please let me know if there's any
Package: libleveldb1d
Version: 1.22-1
Severity: grave
Justification: renders package unusable
libleveldb1d version 1.22-1 does not contain any library, only a dead
symlink as it can be seen by looking at the content of the package:
| $ dpkg -c libleveldb1d_1.22-1_amd64.deb
| drwxr-xr-x root/root
Maybe something like this would fix it, but beware because it's
completely untested:
--- a/debian/rules
+++ b/debian/rules
@@ -37,8 +37,8 @@ override_dh_auto_clean:
override_dh_auto_build:
dh_auto_build -- NO_PNG=1
-override_dh_install:
- dh_install
+override_dh_fixperms-arch:
+
Processing control commands:
> tags 866419 + patch
Bug #866419 [src:cfv] cfv: depends on obsolete python-imaging (replace with
python3-pil or python-pil)
Added tag(s) patch.
> tags 866419 + pending
Bug #866419 [src:cfv] cfv: depends on obsolete python-imaging (replace with
python3-pil or
Control: tags 866419 + patch
Control: tags 866419 + pending
Dear maintainer,
I've prepared an NMU for cfv (versioned as 1.18.3-2.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru cfv-1.18.3/debian/changelog cfv-1.18.3/debian/changelog
Processing control commands:
> tags 932855 +pending
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932881 [e2fsprogs] add dependency on
Processing control commands:
> tags 932855 +pending
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932881 [e2fsprogs] add dependency on
Processing control commands:
> tags 932855 +pending
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932881 [e2fsprogs] add dependency on
Processing control commands:
> tags 932855 +pending
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932881 [e2fsprogs] add dependency on
Control: tags 932855 +pending
Control: tags 932859 +pending
Control: tags 932861 +pending
Control: tags 932881 +pending
Control: tags 932888 +pending
My apologies, I hadn't realized initramfs had a dependency on logsave.
I guess I should have known that, but it had slipped my mind. This
will be
Processing control commands:
> tags 932855 +pending
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932861 [e2fsprogs] boot failure because e2fsprogs should depend on logsave
Bug #932881 [e2fsprogs] add dependency on
Package: src:hhsuite
Version: 3.2.0-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in sid but it failed:
[...]
debian/rules build-indep
dh build-indep --builddirectory=mybuild
Your message dated Wed, 24 Jul 2019 16:23:39 +
with message-id
and subject line Bug#907020: fixed in vnstat 1.18-2.1
has caused the Debian Bug report #907020,
regarding vnstat: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Wed, Jul 24, 2019 at 6:31 AM Benjamin Kaduk wrote:
>
> It's hard to come up with many scenarios in which they could be related.
> The only remotely plausible one that comes to mind is if the idmapd is
> somehow using a different keytab (or libkrb5) than the core NFS server, but
> I don't
On Tue, Jul 23, 2019 at 12:09:29PM -0700, Felix Lechner wrote:
> 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
Dear Debian folks,
On 7/24/19 4:37 AM, Ben Caradoc-Davies wrote:
> 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.
If you
Kyle Robbertze wrote:
> > /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
Processing commands for cont...@bugs.debian.org:
> notfound 932881 1.44.5-1
Bug #932881 [e2fsprogs] add dependency on logsave
Bug #932855 [e2fsprogs] e2fsprogs 1.45.3-1 breaks initramfs-tools-core <=0.133
Bug #932859 [e2fsprogs] logsave not found
Bug #932861 [e2fsprogs] boot failure because
Processing control commands:
> reassign -1 e2fsprogs 1.45.3-1
Bug #932888 [src:linux] [src:linux] Misses 'logsave' as a dependency, so the
system stops booting
Bug reassigned from package 'src:linux' to 'e2fsprogs'.
No longer marked as found in versions linux/4.19.0-1.
Ignoring request to alter
Control: reassign -1 e2fsprogs 1.45.3-1
Control: forcemerge 932861 -1
Hi
On Wed, Jul 24, 2019 at 10:34:49AM +0200, rastersoft wrote:
> Package: src:linux
> Version: 4.19.0-1
> Severity: critical
>
> --- Please enter the report below this line. ---
>
> The "logsave" package isn't included in
On 2019-07-22 at 21:12:34 +0200, Sebastiaan Couwenberg wrote:
> Hi Elena,
>
> On Fri, 7 Jun 2019 09:21:22 +0200 Elena ``of Valhalla'' wrote:
> > Of course after the release the severity can be raised back, as then it
> > would apply to the majority of users indeed (but I'd just upload the
> > new
Package: src:linux
Version: 4.19.0-1
Severity: critical
--- Please enter the report below this line. ---
The "logsave" package isn't included in the dependencies, so, if it
isn't already installed when the kernel is being updates, the system
fails to start at boot, showing a message that
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855
Thank you so much! I can finally access my data :)
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
I just stumbled over this issue myself. I got my system to boot by adding
the "fastboot" option to the kernel command line from GRUB, which skips fsck
(among other things) and therefore ignores the missing logsave.
--
M.Sc. Carsten Andrich
Ilmenau University of Technology
Electronic Measurement
On Wed, Jul 24, 2019 at 10:06:08AM +0300, jim_p wrote:
> Package: e2fsprogs
> Version: 1.44.5-1
> Followup-For: Bug #932855
>
> Proof that I did install logsave 1 as I said above
>
> # cat var/log/apt/history.log | tail -5
> Start-Date: 2019-07-24 09:10:05
> Commandline: apt-get install logsave
Package: e2fsprogs
Version: 1.44.5-1
Followup-For: Bug #932855
Proof that I did install logsave 1 as I said above
# cat var/log/apt/history.log | tail -5
Start-Date: 2019-07-24 09:10:05
Commandline: apt-get install logsave
Requested-By: vaggos (1000)
Install: logsave:i386 (1.45.3-1)
End-Date:
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
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 ...
>
79 matches
Mail list logo
