Source: virtualbox
Version: 6.0.10-dfsg-1
Severity: serious
Tags: patch ftbfs
We recently noticed that gsoap should not depend on libgsoap-dev
(#930961). For this reason gsoap dropped the dependency any any
downstream needs to explicitly depend on libgsoap-dev. virtualbox is
such a downstream and
Package: node-anymatch
Version: 3.0.3+~2.0.7-1
Severity: serious
Justification: makes package unusable
Found this while building node-watchpack 1.6
Error: Cannot find module 'normalize-path' Require stack:
- /usr/share/nodejs/anymatch/index.js -
Source: python-slugify
Version: 3.0.2-2
Severity: grave
Hi,
3.0.2-2 fixed the missing unidecode binary dependency. However
text-unidecode is still registered as a required dependency. This breaks
reverse dependencies if text-unidecode is not installed on the system.
I'm working on it.
regards,
On Fri, 26 Jul 2019 16:42:03 -0300, intrigeri wrote:
> > I'll file bugs against all reverse-dependencies to alert their
> > maintainer about this situation.
>
> Done. All such bug reports are usertagged "pkg-components-removal" so
> they'll appear there shortly:
>
>
Your message dated Sat, 27 Jul 2019 23:47:07 +
with message-id
and subject line Bug#932401: fixed in patch 2.7.6-3+deb10u1
has caused the Debian Bug report #932401,
regarding patch: CVE-2019-13636
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 27 Jul 2019 23:47:40 +
with message-id
and subject line Bug#932401: fixed in patch 2.7.5-1+deb9u2
has caused the Debian Bug report #932401,
regarding patch: CVE-2019-13636
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing control commands:
> severity -1 wishlist
Bug #933229 [yarnpkg] yarnpkg: Cannot find module
'babel-runtime/helper/asyncToGenerator'
Severity set to 'wishlist' from 'grave'
--
933229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933229
Debian Bug Tracking System
Contact
Your message dated Sat, 27 Jul 2019 23:17:36 +
with message-id
and subject line Bug#930024: fixed in neovim 0.1.7-4+deb9u1
has caused the Debian Bug report #930024,
regarding neovim: CVE-2019-12735: Modelines allow arbitrary code execution
to be marked as done.
This means that you claim that
Control: severity -1 wishlist
On 2019, ജൂലൈ 28 1:48:56 AM IST, Christoph Schulz
wrote:
>Package: yarnpkg
>Version: 1.13.0-1
>Severity: grave
>Justification: renders package unusable
>
>
>Dear Maintainer,
>
>it seems like the yarnpkg executable is broken somehow.
>
>Please see below for the full
Processing commands for cont...@bugs.debian.org:
> severity 926534 serious
Bug #926534 [aweather] libgps changed API of gps_read
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926534:
Processing commands for cont...@bugs.debian.org:
> severity 926521 serious
Bug #926521 [obdgpslogger] libgps changed API of gps_read
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926521:
Processing commands for cont...@bugs.debian.org:
> severity 926522 serious
Bug #926522 [navit] libgps changed API of gps_read
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926522:
Processing commands for cont...@bugs.debian.org:
> severity 926528 serious
Bug #926528 [collectd] libgps changed API of gps_read
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926528:
On 2019-07-26 23:39, Simon McVittie wrote:
> > On mips, the gvariant test timed out.
>
> This is failing a fuzz-test that randomly modifies binary data and
> tries to parse it. I thought it might be reaching some pathological
> case where the parser breaks, but no - it looks like the actual
Processing commands for cont...@bugs.debian.org:
> tags 930228 + bullseye sid
Bug #930228 [partman-crypto] partman-crypto: cryptsetup's initramfs integration
was moved to a separate package
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need
Hi again,
intrigeri:
> I'm very glad I was mislead. It looks like Dpkg::Changelog{,::*} are
> sufficient for many, if not most, use cases of Parse::DebianChangelog :)
Hoping it will help other affected folks go through this transition,
here are MRs that give examples about how some code can be
Package: yarnpkg
Version: 1.13.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
it seems like the yarnpkg executable is broken somehow.
Please see below for the full error. I will resort to the installation method
from the yarn site for now. [1]
I have installed
Your message dated Sat, 27 Jul 2019 19:10:57 +
with message-id
and subject line Bug#932678: fixed in glib2.0 2.60.6-1
has caused the Debian Bug report #932678,
regarding wine can not be installed after updating libglib2.0-0 to 2.60
to be marked as done.
This means that you claim that the
Your message dated Sat, 27 Jul 2019 19:10:57 +
with message-id
and subject line Bug#932678: fixed in glib2.0 2.60.6-1
has caused the Debian Bug report #932678,
regarding glib2.0: tests timeout on i386 and mips
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 27 Jul 2019 19:07:27 +
with message-id
and subject line Bug#933184: Removed package(s) from unstable
has caused the Debian Bug report #919059,
regarding ensymble: Time to retire
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 27 Jul 2019 19:08:19 +
with message-id
and subject line Bug#933195: Removed package(s) from unstable
has caused the Debian Bug report #915773,
regarding Useless in Debian
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 27 Jul 2019 19:01:52 +
with message-id
and subject line Bug#933039: Removed package(s) from unstable
has caused the Debian Bug report #846854,
regarding nagios2mantis: Don't depend on nagios3 which has been removed from
unstable
to be marked as done.
This means that
Your message dated Sat, 27 Jul 2019 18:59:57 +
with message-id
and subject line Bug#932936: Removed package(s) from unstable
has caused the Debian Bug report #840388,
regarding doers nothing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 27 Jul 2019 19:01:26 +
with message-id
and subject line Bug#933037: Removed package(s) from unstable
has caused the Debian Bug report #900375,
regarding hg-fast-export: Incompatible with mercurial 4.6
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 27 Jul 2019 19:00:57 +
with message-id
and subject line Bug#932994: Removed package(s) from unstable
has caused the Debian Bug report #856726,
regarding sapgui-package: depends on no longer available openjdk-6-jre
to be marked as done.
This means that you claim that
Your message dated Sat, 27 Jul 2019 19:02:17 +
with message-id
and subject line Bug#933047: Removed package(s) from unstable
has caused the Debian Bug report #915761,
regarding libosl FTBFS with boost 1.67
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 27 Jul 2019 18:56:26 +
with message-id
and subject line Bug#932826: Removed package(s) from unstable
has caused the Debian Bug report #930400,
regarding boa-constructor: Pychecker will be removed after buster
to be marked as done.
This means that you claim that the
Your message dated Sat, 27 Jul 2019 18:55:19 +
with message-id
and subject line Bug#932771: Removed package(s) from unstable
has caused the Debian Bug report #915128,
regarding Don't include in buster
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 27 Jul 2019 18:56:01 +
with message-id
and subject line Bug#932823: Removed package(s) from unstable
has caused the Debian Bug report #930676,
regarding goplay: Should this package be removed?
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 27 Jul 2019 18:51:45 +
with message-id
and subject line Bug#932740: Removed package(s) from unstable
has caused the Debian Bug report #904374,
regarding screenie-qt: Should this package be removed?
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 27 Jul 2019 18:49:47 +
with message-id
and subject line Bug#932690: Removed package(s) from unstable
has caused the Debian Bug report #929588,
regarding lsat missing source for configure
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 27 Jul 2019 18:49:47 +
with message-id
and subject line Bug#932690: Removed package(s) from unstable
has caused the Debian Bug report #931140,
regarding lsat: probably obsolete
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 27 Jul 2019 18:49:12 +
with message-id
and subject line Bug#932610: Removed package(s) from unstable
has caused the Debian Bug report #914635,
regarding woo FTBFS with boost 1.67
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Sat, 27 Jul 2019 18:36:47 +
with message-id
and subject line Bug#932326: Removed package(s) from unstable
has caused the Debian Bug report #887879,
regarding macchanger-gtk: Please don't recommend gksu
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 27 Jul 2019 18:36:47 +
with message-id
and subject line Bug#932326: Removed package(s) from unstable
has caused the Debian Bug report #912895,
regarding macchanger-gtk: Depends on libgtk2-perl, that won't be part of
Bullseye
to be marked as done.
This means that you
Your message dated Sat, 27 Jul 2019 18:36:47 +
with message-id
and subject line Bug#932326: Removed package(s) from unstable
has caused the Debian Bug report #904559,
regarding macchanger-gtk: Please remove dependency on libgtk2-gladexml-perl
to be marked as done.
This means that you claim
Your message dated Sat, 27 Jul 2019 18:33:14 +
with message-id
and subject line Bug#932234: Removed package(s) from unstable
has caused the Debian Bug report #904556,
regarding libgtk2-trayicon-perl: Don't ship libgtk2-trayicon-perl in Buster
to be marked as done.
This means that you claim
Your message dated Sat, 27 Jul 2019 18:32:38 +
with message-id
and subject line Bug#932238: Removed package(s) from unstable
has caused the Debian Bug report #912876,
regarding gtkorphan: Depends on libgtk2-perl, that won't be part of Bullseye
to be marked as done.
This means that you claim
Your message dated Sat, 27 Jul 2019 18:32:38 +
with message-id
and subject line Bug#932238: Removed package(s) from unstable
has caused the Debian Bug report #904562,
regarding gtkorphan: Please remove dependency on libgtk2-gladexml-perl
to be marked as done.
This means that you claim that
Your message dated Sat, 27 Jul 2019 18:31:47 +
with message-id
and subject line Bug#932232: Removed package(s) from unstable
has caused the Debian Bug report #904555,
regarding libgtk2-traymanager-perl: Don't ship libgtk2-traymanager-perl in
Buster
to be marked as done.
This means that you
Your message dated Sat, 27 Jul 2019 18:29:38 +
with message-id
and subject line Bug#932226: Removed package(s) from unstable
has caused the Debian Bug report #904549,
regarding libgtk2-ex-simple-list-perl: Don't ship libgtk2-ex-simple-list-perl
in Buster
to be marked as done.
This means
Your message dated Sat, 27 Jul 2019 18:31:20 +
with message-id
and subject line Bug#932230: Removed package(s) from unstable
has caused the Debian Bug report #904554,
regarding libgtk2-spell-perl: Don't ship libgtk2-spell-perl in Buster
to be marked as done.
This means that you claim that
Your message dated Sat, 27 Jul 2019 18:30:29 +
with message-id
and subject line Bug#932228: Removed package(s) from unstable
has caused the Debian Bug report #904551,
regarding libgtk2-gladexml-simple-perl: Don't ship libgtk2-gladexml-simple-perl
in Buster
to be marked as done.
This means
Your message dated Sat, 27 Jul 2019 18:30:54 +
with message-id
and subject line Bug#932229: Removed package(s) from unstable
has caused the Debian Bug report #904552,
regarding libgtk2-notify-perl: Don't ship libgtk2-notify-perl in Buster
to be marked as done.
This means that you claim that
Your message dated Sat, 27 Jul 2019 18:30:02 +
with message-id
and subject line Bug#932227: Removed package(s) from unstable
has caused the Debian Bug report #904550,
regarding libgtk2-ex-volumebutton-perl: Don't ship libgtk2-ex-volumebutton-perl
in Buster
to be marked as done.
This means
Your message dated Sat, 27 Jul 2019 18:28:44 +
with message-id
and subject line Bug#932225: Removed package(s) from unstable
has caused the Debian Bug report #904548,
regarding libgtk2-ex-printdialog-perl: Don't ship libgtk2-ex-printdialog-perl
with Buster
to be marked as done.
This means
Your message dated Sat, 27 Jul 2019 18:28:20 +
with message-id
and subject line Bug#932224: Removed package(s) from unstable
has caused the Debian Bug report #904547,
regarding libgtk2-ex-podviewer-perl: Don't ship libgtk2-ex-podviewer-perl with
Buster
to be marked as done.
This means that
Your message dated Sat, 27 Jul 2019 18:27:30 +
with message-id
and subject line Bug#93: Removed package(s) from unstable
has caused the Debian Bug report #885676,
regarding libgtk2-sourceview2-perl: Depends on unmaintained gtksourceview2
to be marked as done.
This means that you claim
Your message dated Sat, 27 Jul 2019 18:23:53 +
with message-id
and subject line Bug#932053: Removed package(s) from unstable
has caused the Debian Bug report #889906,
regarding xcrysden FTBFS with libtogl-dev 2.0-1
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 27 Jul 2019 18:25:41 +
with message-id
and subject line Bug#932144: Removed package(s) from unstable
has caused the Debian Bug report #917847,
regarding ipsec-tools is unsuitable for inclusion in Debian
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 27 Jul 2019 18:27:58 +
with message-id
and subject line Bug#932223: Removed package(s) from unstable
has caused the Debian Bug report #904546,
regarding libgtk2-ex-entry-pango-perl: Remove libgtk2-ex-entry-pango-perl
during the Buster cycle
to be marked as done.
This
Your message dated Sat, 27 Jul 2019 17:51:47 +
with message-id
and subject line Bug#899067: fixed in screenruler 0.960+bzr41+deb10-2
has caused the Debian Bug report #899067,
regarding screenruler: does not start: `loop': wrong number of arguments
to be marked as done.
This means that you
Your message dated Sat, 27 Jul 2019 17:51:14 +
with message-id
and subject line Bug#933205: fixed in haskell-patience 0.2.1.1-2
has caused the Debian Bug report #933205,
regarding haskell-patience_0.2.1.1-1_all.changes REJECTED
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 27 Jul 2019 17:51:20 +
with message-id
and subject line Bug#933010: fixed in haskell-quickcheck 2.12.6.1-2
has caused the Debian Bug report #933010,
regarding haskell-quickcheck_2.12.6.1-1_s390x.changes REJECTED
to be marked as done.
This means that you claim that the
Your message dated Sat, 27 Jul 2019 17:51:04 +
with message-id
and subject line Bug#933204: fixed in haskell-cgi 3001.3.0.3-2
has caused the Debian Bug report #933204,
regarding haskell-cgi_3001.3.0.3-1_s390x.changes REJECTED
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 27 Jul 2019 17:51:47 +
with message-id
and subject line Bug#868893: fixed in screenruler 0.960+bzr41+deb10-2
has caused the Debian Bug report #868893,
regarding screenruler: Missing dependency prevents screenruler from starting
to be marked as done.
This means that
Your message dated Sat, 27 Jul 2019 17:50:58 +
with message-id
and subject line Bug#933165: fixed in haskell-brick 0.46-2
has caused the Debian Bug report #933165,
regarding haskell-brick_0.46-1_s390x.changes REJECTED
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 27 Jul 2019 17:50:42 +
with message-id
and subject line Bug#933164: fixed in haskell-aeson 1.4.2.0-2
has caused the Debian Bug report #933164,
regarding haskell-aeson_1.4.2.0-1_mipsel.changes REJECTED
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 27 Jul 2019 17:50:52 +
with message-id
and subject line Bug#933166: fixed in haskell-base64-bytestring 1.0.0.2-2
has caused the Debian Bug report #933166,
regarding haskell-base64-bytestring_1.0.0.2-1_mipsel.changes REJECTED
to be marked as done.
This means that you
Source: siridb-server
Version: 2.0.34-1
Severity: serious
Justification: missing source
The Release/makefile starts with:
# Automatically-generated file. Do not edit!
Your message dated Sat, 27 Jul 2019 16:35:57 +
with message-id
and subject line Bug#932404: fixed in unzip 6.0-25
has caused the Debian Bug report #932404,
regarding firefox-esr, FTBFS "possible zip bomb".
to be marked as done.
This means that you claim that the problem has been dealt with.
Source: check-mk
Severity: serious
Justification: QA/MIA-Team
Dear maintainers of check-mk,
check-mk is currently RC-Buggy with 2 RC bugs:
#876686 [S| | ] [check-mk-config-icinga] check-mk-config-icinga: file
conflict with check-mk-common: /usr/share/check_mk/cmk/paths.py
#924727 [S|
On Fri, Jul 26, 2019 at 04:01:15AM +, Adler, Mark wrote:
> All,
>
> Thank you Santiago for the report and David for the diagnosis. Though this is
> not a valid zip file, there are in fact no overlapping structures and so
> there should not be a bomb alert.
>
> I have added a commit that
Your message dated Sat, 27 Jul 2019 11:42:32 -0400
with message-id
and subject line Re: Bug#932592: kopano-webapp: autopkgtest regression
has caused the Debian Bug report #932592,
regarding kopano-webapp: autopkgtest regression
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> reassign 932592 src:chromium
Bug #932592 [src:kopano-webapp] kopano-webapp: autopkgtest regression
Bug reassigned from package 'src:kopano-webapp' to 'src:chromium'.
No longer marked as found in versions kopano-webapp/3.5.6+dfsg1-1.
Ignoring
Your message dated Sat, 27 Jul 2019 15:20:38 +
with message-id
and subject line Bug#933069: fixed in libglib-perl 3:1.329-4
has caused the Debian Bug report #933069,
regarding libglib-perl: autopkgtest regression with GLib 2.60.x: GKeyFile
comments no longer contain trailing newline
to be
gregor herrmann:
> In dpt-new-upstream we're using Dpkg::Changelog::Debian from
> libdpkg-perl, which might help here as well.
Oh, this is very interesting, thanks! I had taken a look at that
module, but from the documentation I understood it only gives us "the
number of changelog entries that
Your message dated Sat, 27 Jul 2019 16:17:38 +0100
with message-id <20190727161738.77ecc466@sylvester.codehelp>
and subject line Not found - version 1.35 has left NEW
has caused the Debian Bug report #928311,
regarding geany-plugin-spellcheck : Depends: geany-abi-18176 but it is not
installable
Source: rdkit
Version: 201809.1+dfsg-7
Severity: serious
Tags: ftbfs sid bullseye
Since version 2019.20190311-1 the texlive-base package doesn't build
texlive-generic-extra anymore. This is an issue for your package as it
build-depends on it. Please update the building of your package to not
need
Control: tag -1 pending
Hello,
Bug #933069 in libglib-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #933069 [src:libglib-perl] libglib-perl: autopkgtest regression with GLib
2.60.x: GKeyFile comments no longer contain trailing newline
Added tag(s) pending.
--
933069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933069
Debian Bug Tracking
Source: haskell-patience
Version: 0.2.1.1-1
Severity: serious
On 2019-07-27 14:42, Debian FTP Masters wrote:
> libghc-patience-doc_0.2.1.1-1_all.deb: has 1 file(s) with a timestamp too far
> in the past:
> usr/share/doc/libghc-patience-doc/changelog.gz (Thu Jan 1 00:00:00 1970)
>
>
>
> ===
Processing commands for cont...@bugs.debian.org:
> found 933069 3:1.329-3
Bug #933069 [src:libglib-perl] libglib-perl: autopkgtest regression with GLib
2.60.x: GKeyFile comments no longer contain trailing newline
Marked as found in versions libglib-perl/3:1.329-3.
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> forwarded 933069 https://gitlab.gnome.org/GNOME/perl-glib/merge_requests/4
Bug #933069 [src:libglib-perl] libglib-perl: autopkgtest regression with GLib
2.60.x: GKeyFile comments no longer contain trailing newline
Changed Bug
Source: haskell-cgi
Version: 3001.3.0.3-1
Severity: serious
On 2019-07-27 14:40, Debian FTP Masters wrote:
>
>
> libghc-cgi-dev_3001.3.0.3-1_s390x.deb: has 1 file(s) with a timestamp too far
> in the past:
> usr/share/doc/libghc-cgi-dev/changelog.gz (Thu Jan 1 00:00:00 1970)
>
>
>
> ===
Control: reopen -1
autopkgtests still fail on testing with 1.329-3. I've dived deeper
into the problem and found the root cause: the (patched) t/g.t adjusts
its expectations depending on what version of GLib we were compiled
against (in this case: sid's 2.60.5), while it should depend on what
Processing control commands:
> reopen -1
Bug #933069 {Done: intrigeri } [src:libglib-perl]
libglib-perl: autopkgtest regression with GLib 2.60.x: GKeyFile comments no
longer contain trailing newline
Bug reopened
Ignoring request to alter fixed versions of bug #933069 to the same values
Processing commands for cont...@bugs.debian.org:
> notfixed 933069 3:1.329-3
Bug #933069 {Done: intrigeri } [src:libglib-perl]
libglib-perl: autopkgtest regression with GLib 2.60.x: GKeyFile comments no
longer contain trailing newline
No longer marked as fixed in versions
Your message dated Sat, 27 Jul 2019 14:39:11 +
with message-id
and subject line Bug#931034: fixed in debian-design 3.0.13
has caused the Debian Bug report #931034,
regarding debian-design: shouldn't depend on libreoffice-ogltrans (needs
rebuild with fixed boxer-data)
to be marked as done.
Your message dated Sat, 27 Jul 2019 13:35:28 +
with message-id
and subject line Bug#932186: fixed in mediawiki2latex 7.33-3
has caused the Debian Bug report #932186,
regarding auto-multiple-choice depends on cruft package.
to be marked as done.
This means that you claim that the problem has
Package: fai-server
Version: 5.8.4
Severity: grave
Tags: security, buster
Dear Maintainer,
fai-server installs /etc/fai/apt/sources.list with the following entry
by default:
deb [trusted=yes] http://fai-project.org/download buster koeln
This is problematic, as the [trusted=yes] part will tell
On Thu, Jul 25, 2019 at 11:39:43PM +0200, Moritz Mühlenhoff wrote:
> On Sat, Jan 12, 2019 at 12:12:46PM +, Dominic Hargreaves wrote:
> > Source: ensymble
> > Version: 0.29-1
> > Severity: serious
> > Justification: maintainer
> >
> > I'm going to hazard a guess and say that there is
On Thu, Jul 25, 2019 at 10:58:15PM -0600, MyMail5 wrote:
> Dear Maintainer,
> Please add the "perl-doc-html" package to Debian 10.
Hello,
Unfortunately the perl-doc-html maintainer orphaned the package last year
so it was removed so that it didn't reflect the wrong version of perl
shipped in
Hi,
On Fri, Jul 26, 2019 at 8:18 PM Stéphane Glondu wrote:
> > The upstream cduce-next branch can be built with Debian's OCaml 4.05.
> > I've asked upstream (Giuseppe Castagna) to make a new release and I
> > was told that they will do it soon.
>
> Any news on that?
>
I haven't heard anything
Processing commands for cont...@bugs.debian.org:
> tags 930228 + patch
Bug #930228 [partman-crypto] partman-crypto: cryptsetup's initramfs integration
was moved to a separate package
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
930228:
On Fri, 26 Jul 2019 23:47:02 +0200,
Samuel Thibault wrote:
>
> Distribution installation images such as Debian include different sets
> of modules which can be downloaded dynamically. Such images may notably
> include the hda sound modules but not the i915 DRM module, even if the
> latter was
Source: haskell-base64-bytestring
Version: 1.0.0.2-1
Severity: serious
On 2019-07-27 06:07, Debian FTP Masters wrote:
> libghc-base64-bytestring-prof_1.0.0.2-1_mipsel.deb: has 1 file(s) with a
> timestamp too far in the past:
> usr/share/doc/libghc-base64-bytestring-prof/changelog.gz (Thu Jan
Source: haskell-aeson
Version: 1.4.2.0-1
Severity: serious
On 2019-07-27 05:49, Debian FTP Masters wrote:
> libghc-aeson-prof_1.4.2.0-1_mipsel.deb: has 1 file(s) with a timestamp too
> far in the past:
> usr/share/doc/libghc-aeson-prof/changelog.gz (Thu Jan 1 00:00:00 1970)
>
>
>
> ===
>
Source: haskell-brick
Version: 0.46-1
Severity: serious
On 2019-07-27 05:07, Debian FTP Masters wrote:
>
>
> libghc-brick-dev_0.46-1_s390x.deb: has 1 file(s) with a timestamp too far in
> the past:
> usr/share/doc/libghc-brick-dev/changelog.gz (Thu Jan 1 00:00:00 1970)
>
>
>
> ===
>
>
89 matches
Mail list logo
