Hi,
I just wanted to give a heads up, that earlier today I uploaded an NMU
to DELAYED+5 containing upstream version 1.7.4 which should fix this bug.
I pushed the changes to the packaging repository on salsa, so I assume a
debdiff of the NMU is not required here.
Regards
Sven
Hi,
I just noticed that the current upstream release 1.7.2 still has a bug
very similar to this bug present.
(https://projects.torsion.org/borgmatic-collective/borgmatic/issues/590)
It's basically the same bug, only with `patterns_from` instead of
`patterns`.
Regards
Sven
Package: borgmatic
Version: 1.5.12-2
Severity: grave
Tags: upstream fixed-upstream
Forwarded:
https://projects.torsion.org/borgmatic-collective/borgmatic/issues/574
Control: found -1 1.6.3-1
Hi,
Recently I reported the bug mentioned above upstream, which causes
most data to be silently excluded
Control: tag -1 +patch
On Wed, 4 May 2022 12:57:46 -0400
=?UTF-8?Q?Louis-Philippe_V=c3=a9ronneau?= wrote:
Thanks for reporting this bug. I confirm I can reproduce it on my system
running unstable. Never caught it since I was running the poppler plugin.
Understandable. I discovered this
Source: dwarf-fortress
Version: 0.44.12-1
Severity: serious
The source tarballs for both amd64 and i386 contain the following
shared libraries:
$ ls {amd64,i386}/libs/lib{gcc_s.so.1,stdc++.so.6}
amd64/libs/libgcc_s.so.1
amd64/libs/libstdc++.so.6
i386/libs/libgcc_s.so.1
i386/libs/libstdc++.so.6
Source: vde2
Version: 2.3.2+r586-2.2+b1
Severity: serious
Justification: Policy ยง12.5
Greetings,
during the review of this package in the NEW queue I discovered
various issues that are already present in the current unstable
version of the package as outlined below.
These files are marked in
Hi,
On Fri, 31 Jan 2020 16:01:19 +0100 Andreas Beckmann wrote:
> the kubernetes package has been requested to be removed (#950247), but
> kubectx still build-depends on it.
>
> Please find a solution.
Just adding my two cents, as I'm the one who originally reported the RM
bug against
On Wed, 5 Oct 2016 17:12:45 +
Clint Adams wrote:
> Source: ghc
> Version: 7.10.3-9
> Severity: serious
>
> clint@abel ~/haskell-http-api-data-0.2.4
> % ghci -isrc -XCPP -D"MIN_VERSION_base(X,Y,Z)=1"
> GHCi, version 7.10.3: http://www.haskell.org/ghc/ :? for help
>
Am Mon, 4 Jul 2016 18:17:37 +0200
schrieb Matthias Klose <d...@debian.org>:
> On 04.07.2016 15:01, Sven Bartscher wrote:
> > On Sun, 24 Apr 2016 22:13:47 +0200 Matthias Klose <d...@debian.org>
> > wrote:
> >> [snip]
> >>
> >> [I was doi
On Sun, 24 Apr 2016 22:13:47 +0200 Matthias Klose
wrote:
> Package: haskell-devscripts
> Version: 0.10.2.3
> Severity: serious
> Tags: sid stretch
>
> [I was doing a transition (icu 55 to 57), and investigating some
> build failures with link failures, some missing icu55
Package: simpleid
Version: 0.8.1-14
Severity: grave
Tags: security
The identity files (in /var/lib/simpleid/identities) expect user
passwords to be given as MD5 hashes of the actual passwords, but MD5
is generally considered broken and should probably not be used to
store user passwords.
--
On Sun, 10 Jan 2016 20:37:13 +0100 Tomas Janousek <t...@nomi.cz> wrote:
> Hi,
>
> On Fri, Jan 08, 2016 at 03:19:49PM +0100, Sven Bartscher wrote:
> > > It would be good if you open another report for ghc-mod, so it won't
> > > migrate before its libexecdir is set
Control: reassign -1 haskell-cabal-helper
On Mon, 4 Jan 2016 16:29:22 +0100 Sven Bartscher
<sven.bartsc...@weltraumschlangen.de> wrote:
> On Sun, 3 Jan 2016 20:52:52 +0100
> Tomas Janousek <t...@nomi.cz> wrote:
> > Also, ghc-mod seems to expect cabal-helper in /usr/libex
Control: tag -1 + pending
On Sun, 3 Jan 2016 20:52:52 +0100
Tomas Janousek wrote:
> Package: cabal-helper
> Version: 0.6.2.0-1
> Severity: grave
> Justification: renders package unusable
>
> There's no cabal-helper binary in the package:
>
> > $ dpkg -L cabal-helper
> > /.
> >
On Sun, 27 Dec 2015 15:37:43 +0100
Joachim Breitner wrote:
> Hi,
>
> on ghc-mod:
>
> Am Sonntag, den 27.12.2015, 14:50 +0530 schrieb Vasudev Kamath:
> > Checking at the tracker It looks like this package is having this
> > problem for about ~6 months.
>
> Does this
Package: openmw-launcher
Version: 0.36.1-1+b2
Severity: grave
Justification: renders package unusable
omwlauncher doesn't start, but gives the following error message
instead:
omwlauncher: error while loading shared libraries:
libboost_system.so.1.55.0: cannot open shared object file: No such
On Mon, 23 Feb 2015 17:04:11 +
Alessio Treglia ales...@debian.org wrote:
severity 778866 grave
On Mon, Feb 23, 2015 at 4:49 PM, Sven Bartscher
sven.bartsc...@weltraumschlangen.de wrote:
Control: severity -1 important
This should set the severity, since you didn't prefix
better.
On Fri, Feb 20, 2015 at 9:06 PM, Sven Bartscher
sven.bartsc...@weltraumschlangen.de wrote:
I converted to mp4 files with movie-to-dvd movie1.mp4 movie2.mp4.
I made a background with movie-make-title-simple -o title -m pal
Then I tried to create the .vob with movie-title -o title.vob -t
Greetings,
I've tried to figure out why the read terminates the whole script.
Disabling the set -e makes the script run almost fine. So it seems,
that read has a non-zero exit status. Ignoring the error with
'read xx yy ${TEMP}' made the script run fine (without disabling
set -e).
run fine isn't
Package: videotrans
Version: 1.6.1-2
Severity: grave
Justification: renders package unusable
I converted to mp4 files with movie-to-dvd movie1.mp4 movie2.mp4.
I made a background with movie-make-title-simple -o title -m pal
Then I tried to create the .vob with movie-title -o title.vob -t title
Source: haskell-hgettext
Version: 0.1.30-2
Severity: grave
When trying to build a package, that uses function from hgettext in
its Setup.hs, with cabal-install and libghc-cabal-dev is installed,
the build fails with a bunch of messages about not matching command
line options.
This happens,
Greetings,
Can you reproduce this with 4.2.33-1? At least I can't. Maybe this was
fixed in the new version.
I think if you can't reproduce this, we can just close this bug.
Regards
Sven
signature.asc
Description: PGP signature
Control: severity -1 minor
Control: tag -1 + unreproducible
I noticed that I can now install both packages again. Reinstalling
libopenal1 fixed the problem.
But it's a fact that llibopenal1 and libopenal-dev contain the same
symlink? Is this intended? Should the symlink be removed from
23 matches
Mail list logo