Package: dpkg
Version: 1.19.4
Followup-For: Bug #921031
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
In Ubuntu, the attached patch was applied to achieve the following:
* scripts/Dpkg/Source/Package.pm: use Dpkg::Source:Format (closes: #921031)
Simple
On Wed, Feb 20, 2019 at 12:28:48AM +0100, Sebastian Andrzej Siewior wrote:
> On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
> > this is a remainder about the openssl transition [0]. We really want to
> > remove libssl1.0-dev from unstable for Buster. I will raise the severity
> >
Processing commands for cont...@bugs.debian.org:
> tags 922692 = ftbfs
Bug #922692 [galax] galax: FTBFS on ppc64el - ERROR: unable to find
camomileLibrary.cmi in /usr/lib/ocaml/camomile
Added tag(s) ftbfs; removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> severity 922692 serious
Bug #922692 [galax] galax: FTBFS on ppc64el - ERROR: unable to find
camomileLibrary.cmi in /usr/lib/ocaml/camomile
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> tags 922692 + pending
Bug #922692 [galax] galax: FTBFS on ppc64el - ERROR: unable to find
camomileLibrary.cmi in /usr/lib/ocaml/camomile
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Source: r-cran-vegan
Version: 2.5-4+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 2.5-4+dfsg-1, r-cran-vegan has been failing its
own autopkgtests [1] with the following error:
On Tue, 12 Feb 2019 09:32:48 +0700 Arnaud Rebillout
wrote:
> I looked into this a bit yesterday.
>
> As mentioned in the issue upstream at
> https://github.com/etcd-io/etcd/issues/9353, the fix has been merged in
> the master branch of etcd in March 2018, almost a year ago. The
> conversation
Hi. Why did the package start depending on QtWebEngine at all? I had to
hold it because of that. If I got the upstream README correctly,
QtWebEngine is needed only for IDE, which is in another package.
Just updated my test machines to the newly released qemu/1:3.1+dfsg-4
and can confirm it's fixed. Thanks!
Your message dated Tue, 19 Feb 2019 23:51:09 +
with message-id
and subject line Bug#851085: fixed in conserver 8.2.1-1.1
has caused the Debian Bug report #851085,
regarding conserver: Please migrate to openssl1.1 in buster
to be marked as done.
This means that you claim that the problem has
Hi!
On Tue, 2019-02-12 at 17:33:03 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> > # Breaks autopkgtests and is therefore a migration blocker
> > severity 921031 grave
> Bug #921031 [libdpkg-perl] Dpkg::Source::Package missing use of ::Format
>
On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.
There has
Control: tags 851085 + patch
Control: tags 851085 + pending
Dear maintainer,
I've prepared an NMU for conserver (versioned as 8.2.1-1.1) and I am
about to upload (RC bug with no feedback, RM bug filled).
Regards.
Sebastian
diff -u conserver-8.2.1/configure conserver-8.2.1/configure
---
Processing control commands:
> tags 851085 + patch
Bug #851085 [src:conserver] conserver: Please migrate to openssl1.1 in buster
Added tag(s) patch.
> tags 851085 + pending
Bug #851085 [src:conserver] conserver: Please migrate to openssl1.1 in buster
Added tag(s) pending.
--
851085:
Package: epiphany-browser
Version: 3.31.91-2
Severity: grave
$ mkdir /tmp/p
$ HOME=/tmp/p epiphany /etc/motd
** (epiphany:11842): WARNING **: 06:53:40.412: Web process crashed
(WebKitWebProcess:12106): GLib-GObject-WARNING **: 06:53:41.133:
../../../gobject/gtype.c:4265: type id '0' is invalid
#894962 was probably partially due to #909151.
Thanks to Mauricio Oliveira to have fixed #909151.
https://bugs.debian.org/894962
FTBFS and Debci failure with node-process-nextick-args 2.0.0-1
https://bugs.debian.org/909151
'Uncaught TypeError: nextTick is not a function' with
#894962 was probably partially due to #909151.
Thanks to Mauricio Oliveira to have fixed #909151.
https://bugs.debian.org/894962
FTBFS and Debci failure with node-process-nextick-args 2.0.0-1
https://bugs.debian.org/909151
'Uncaught TypeError: nextTick is not a function' with
On 2019-01-27 06:06:08 [+0100], Moritz Muehlenhoff wrote:
> Should zorp be removed? It's incompatible with OpenSSL 1.1 and the bug has
> been unacknowledged since 15 months (859840). It's one of the few remaining
> packages blocking the removal at this point, so this doesn't get ported
> to
Your message dated Tue, 19 Feb 2019 22:34:17 +
with message-id
and subject line Bug#922719: fixed in libpdfbox-java 1:1.8.16-2
has caused the Debian Bug report #922719,
regarding src:libpdfbox-java: FTBFS in buster and sid after recent update to
lcdf-typetools
to be marked as done.
This
Control: tag -1 pending
Hello,
Bug #922719 in libpdfbox-java 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 #922719 [src:libpdfbox-java] src:libpdfbox-java: FTBFS in buster and sid
after recent update to lcdf-typetools
Added tag(s) pending.
--
922719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922719
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 893287 confirmed
Bug #893287 [src:libjogl2-java] libjogl2-java FTBFS with openjdk-9
Added tag(s) confirmed.
> tags 887140 confirmed
Bug #887140 [src:libjogl2-java] libjogl2-java FTBFS on architectures that use
zero (timeout)
Added tag(s)
Processing commands for cont...@bugs.debian.org:
> tags 875358 confirmed
Bug #875358 [src:powermock] Fails with Java 9, >2.0.0 required to work
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
875358:
Source: zoneminder
Severity: grave
Tags: security
Please see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8429
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8428
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8427
On Wed, Feb 20, 2019 at 02:12:55AM +0500, Andrey Rahmatullin wrote:
> On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote:
> > If a transition (even though it's marginal in size) isn't an option at this
> > point
> That's not for me to decide. Should we ask the RT?
Sounds like a
On Thu, Jan 10, 2019 at 08:39:36PM +0100, Joost van Baal-Ilić wrote:
> Hi Moritz,
>
> On Thu, Jan 10, 2019 at 08:33:05PM +0100, Moritz Mühlenhoff wrote:
> > On Mon, Nov 05, 2018 at 03:13:08PM +0100, Joost van Baal-Ilić wrote:
> > >
> > > FWIW, this work:
> > >
> > > > validns
On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote:
> If a transition (even though it's marginal in size) isn't an option at this
> point
That's not for me to decide. Should we ask the RT?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Dec 13, 2018 at 08:55:05PM +0100, Moritz Mühlenhoff wrote:
> On Tue, Jun 05, 2018 at 11:12:34PM +0200, Moritz Muehlenhoff wrote:
> > On Sun, Jun 26, 2016 at 12:21:20PM +0200, Kurt Roeckx wrote:
> > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages
> > > using
> > >
On Sat, Feb 16, 2019 at 10:35:05PM +0500, Andrey Rahmatullin wrote:
> On Sat, Feb 16, 2019 at 12:33:08PM +, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > severity 776246 grave
> > Bug #776246 [librsync1] MD4 collision/preimage attacks
On Sun, 10 Sep 2017 21:41:52 +0100 Chris West wrote:
> Source: powermock
> Version: 1.6.6
> Severity: normal
> User: debian-j...@lists.debian.org
> Usertags: default-java9
>
> Powermock fails to work properly on Java 9.
Powermock still fails to build but has not been removed from testing yet
Package: src:libpdfbox-java
Version: 1:1.8.16-1
Severity: serious
Justification: Policy 4.15
The package FTBFS with the following error after a recent update to
lcdf-typetools:
[...]
make[1]: Leaving directory '/build/libpdfbox-java-1.8.16'
jh_linkjars -O--buildsystem=maven
debian/rules
On 2019-01-10 23:59:09 [+0100], Christoph Biedl wrote:
> Sebastian Andrzej Siewior wrote...
>
> > On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote:
> >
> > > Or should we rather remove netkit-ftp-ssl? There are TLS-capable ftp
> > > client
> > > alternatives in the archive still, e.g.
Control: severity -1 important
On Fri, 06 Jul 2018 13:25:28 + Santiago Vila wrote:
> Package: src:exec-maven-plugin
> Version: 1.1.1+dfsg-3
> Severity: serious
> Tags: ftbfs
Buster/Sid is not affected. Since there is also a simple workaround for
stable and oldstable (disabling the tests), I
Processing control commands:
> severity -1 important
Bug #903125 [src:exec-maven-plugin] exec-maven-plugin: FTBFS: tests fail with
(expected:<[mvn] --version> but was:<['mvn'] --version>)
Severity set to 'important' from 'serious'
--
903125:
Your message dated Tue, 19 Feb 2019 21:40:02 +0100
with message-id
and subject line Re: tiles-autotag: FTBFS in buster/sid (failing tests)
has caused the Debian Bug report #906416,
regarding tiles-autotag: FTBFS in buster/sid (failing tests)
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> Found 914517 linux-image-4.19.0-2-amd64-unsigned
Bug #914517 [src:linux] linux-image-4.9.0-7-amd64: Boot fails unless nomodeset
is set
The source 'linux' and version 'linux-image-4.19.0-2-amd64-unsigned' do not
appear to match any binary
Your message dated Tue, 19 Feb 2019 18:49:20 +
with message-id
and subject line Bug#891796: fixed in libjgraphx-java 2.1.0.7-2
has caused the Debian Bug report #891796,
regarding CVE-2017-18197
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 19 Feb 2019 18:34:04 +
with message-id
and subject line Bug#922313: fixed in kopanocore 8.7.0-2
has caused the Debian Bug report #922313,
regarding kopano-search: missing an end of line character in
/etc/apparmor.d/usr.sbin.kopano-search
to be marked as done.
This
Your message dated Tue, 19 Feb 2019 19:09:34 +0100
with message-id <10a32260-082c-024f-8b1a-414b5c886...@debian.org>
and subject line Re: libxml-security-java FTBFS: error: package javax.xml.bind
does not exist
has caused the Debian Bug report #920793,
regarding libxml-security-java FTBFS: error:
This problem is resolved with redmine (4.0.1-1), but another problem
appeared:
Setting up redmine (4.0.1-1) ...
Could not find gem 'pg (~> 1.1)' in any of the gem sources listed in
your Gemfile.
dpkg: error processing package redmine (--configure):
installed redmine package post-installation
On Mon, Feb 18, 2019 at 11:15:56PM +, Luca Boccassi wrote:
> On Mon, 2019-02-18 at 22:57 +0100, Moritz Mühlenhoff wrote:
> > On Mon, Nov 12, 2018 at 02:36:23PM +, Luca Boccassi wrote:
> > > On Mon, 2018-11-12 at 13:47 +0100, Andreas Beckmann wrote:
> > > > On 2018-11-11 13:54, Luca
Processing commands for cont...@bugs.debian.org:
> reassign 922701 src:node-mocha
Bug #922701 [mocha] mocha: ./build.sh[254]: mocha: not found
Bug reassigned from package 'mocha' to 'src:node-mocha'.
No longer marked as found in versions node-mocha/4.1.0+ds3-4.
No longer marked as fixed in
On Mon, 7 Jan 2019 16:49:41 + Steve McIntyre wrote:
> Hi Matthew,
>
> On Sun, Dec 30, 2018 at 05:38:57PM -0500, Matthew Fluet wrote:
> >If it is just the `world` regression tests that are failing, then it
> >is almost certainly due to save/restore world being incompatible with
> >ASLR; see
Processing commands for cont...@bugs.debian.org:
> fixed 922701 4.1.0+ds3-5
Bug #922701 [mocha] mocha: ./build.sh[254]: mocha: not found
Marked as fixed in versions node-mocha/4.1.0+ds3-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
922701:
Package: mocha
Version: 4.1.0+ds3-4
Severity: grave
Justification: renders package unusable
The /usr/bin/mocha command, present in mocha_4.1.0+ds3-3_all.deb, no
longer exists, making the package totally unusable.
-- System Information:
Debian Release: buster/sid
APT prefers buildd-unstable
Processing commands for cont...@bugs.debian.org:
> fixed 922695 4.1.0+ds3-5
Bug #922695 {Done: Xavier } [src:node-mocha] node-mocha:
breaks all rdepends autopkgtests
The source 'node-mocha' and version '4.1.0+ds3-5' do not appear to match any
binary packages
Marked as fixed in versions
Your message dated Tue, 19 Feb 2019 16:13:21 +0100
with message-id
and subject line Fixed a few minutes ago
has caused the Debian Bug report #922695,
regarding node-mocha: breaks all rdepends autopkgtests
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: kcov
Version: 25+dfsg-1
Severity: serious
Tags: sid buster
Compilation usually fails with messages
cd /<>/kcov-25+dfsg/obj-i686-linux-gnu/src && /usr/bin/c++
-I/<>/kcov-25+dfsg/src/include -I/usr/include/i386-linux-gnu
-std=c++0x -g -Wall -D_GLIBCXX_USE_NANOSLEEP
Processing commands for cont...@bugs.debian.org:
> reassign 922693 libdpkg-perl
Bug #922693 [dpkg] dgit: autopkgtests regressed since the upload of dpkg 1.19.3
Bug reassigned from package 'dpkg' to 'libdpkg-perl'.
Ignoring request to alter found versions of bug #922693 to the same values
Source: node-mocha
Version: 4.1.0+ds3-4
Severity: serious
Every autopkgtest triggered by node-mocha in Ubuntu is failing:
https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#node-mocha
Thanks,
Jeremy Bicha
Processing control commands:
> reassign -1 dpkg
Bug #922693 [dgit] dgit: autopkgtests regressed since the upload of dpkg 1.19.3
Bug reassigned from package 'dgit' to 'dpkg'.
No longer marked as found in versions dgit/8.3.
Ignoring request to alter fixed versions of bug #922693 to the same values
Your message dated Tue, 19 Feb 2019 14:45:12 +
with message-id
and subject line Bug#922478: fixed in linux 4.9.144-3.1
has caused the Debian Bug report #922478,
regarding upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to
4.9.144-3 renders many systems unbootable
to be marked as
Your message dated Tue, 19 Feb 2019 14:45:12 +
with message-id
and subject line Bug#922478: fixed in linux 4.9.144-3.1
has caused the Debian Bug report #922478,
regarding linux-image-4.9.0-8-armmp: Failed to boot after upgrading to
linux-image-4.9.0-8-armmp version 4.9.144-3
to be marked as
Your message dated Tue, 19 Feb 2019 14:45:12 +
with message-id
and subject line Bug#922478: fixed in linux 4.9.144-3.1
has caused the Debian Bug report #922478,
regarding upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to
4.9.144-3 renders many systems unbootable
to be marked as
On Tue, Feb 19, 2019 at 10:26:09AM +0100, Christoph Martin wrote:
> What can we do to not loose these packages (burp in my case)?
>
> librsync 2.0.2-1~exp1 was uploaded to experimental three days ago.
I guess librsync2 would need to go into unstable and testing. Than
we can try to update our
Processing commands for cont...@bugs.debian.org:
> severity 908493 serious
Bug #908493 [src:pegtl] Duplicate of tao-pegtl
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
908493:
Processing commands for cont...@bugs.debian.org:
> reopen 914004
Bug #914004 {Done: Adrian Bunk } [src:acorn] acorn build
depends on cruft package node-unicode-10.0.0
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to
Your message dated Tue, 19 Feb 2019 11:57:41 +
with message-id
and subject line Bug#922656: Removed package(s) from unstable
has caused the Debian Bug report #795007,
regarding [mopidy-youtube] needs python-pafy from stable (not in sid...)
to be marked as done.
This means that you claim that
Your message dated Tue, 19 Feb 2019 11:56:54 +
with message-id
and subject line Bug#922637: Removed package(s) from unstable
has caused the Debian Bug report #875612,
regarding ruby-compass-rails: ruby-compass obsolete and now broken
to be marked as done.
This means that you claim that the
Your message dated Tue, 19 Feb 2019 11:52:27 +
with message-id
and subject line Bug#922562: Removed package(s) from unstable
has caused the Debian Bug report #844967,
regarding picviz: FTBFS: CMake Error: install TARGETS given no ARCHIVE
DESTINATION for static library target "picviz"
to be
Processing control commands:
> tags 922478 + pending
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.144-3 renders many systems unbootable
Bug #922532 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.144-3 renders many
On Mon, Feb 18, 2019 at 11:21:57PM +0100, Wolfgang Schweer wrote:
> On Sun, Feb 17, 2019 at 04:41:57PM +0100, Wolfgang Schweer wrote:
> > On Mon, Jan 14, 2019 at 03:43:26PM +, Holger Levsen wrote:
> > > On Mon, Jan 14, 2019 at 05:15:59PM +0200, Eliza Ralph wrote:
> > > > So are you saying it's
> Hi Thomas,
>> Dear Andreas,
>>
>> Thanks for taking care of toulbar2. I did spend some time to try to go
>> around this #920459 bug but even a postprocessing of the LaTeX output of
>> doxygen (removing inclusion of the xcolor package that generates the
>> LaTeX compilation issue) did not work
Sorry, missed the Reply-All as Andreas pointed out. See attached mail.
Thomas
--- Begin Message ---
Hi Thomas,
On Tue, Feb 19, 2019 at 11:15:13AM +0100, Thomas Schiex wrote:
> Dear Andreas,
>
> Thanks for taking care of toulbar2. I did spend some time to try to go
> around this #920459 bug
Processing control commands:
> tag -1 - upstream
Bug #922667 [beep] beep: Error: could not open any device
Removed tag(s) upstream.
> severity -1 normal
Bug #922667 [beep] beep: Error: could not open any device
Severity set to 'normal' from 'grave'
--
922667:
Control: tag -1 - upstream
Control: severity -1 normal
Hi.
On 2/19/19 6:46 AM, jim_p wrote:
> After today's upgrade to version 1.4.x, beep no longer works and pops the
> above
> error. After checking its man page, I found out that it tries to access these
> devices, in that specific order
>
Your message dated Tue, 19 Feb 2019 11:05:51 +
with message-id
and subject line Bug#909752: fixed in php-apcu-bc 1.0.4-4
has caused the Debian Bug report #909752,
regarding php-apcu-bc: undefined symbol: zif_apcu_store
to be marked as done.
This means that you claim that the problem has been
Package: src:openjdk-11-dcevm
Version: 11.0.1+7-1
Severity: serious
Tags: sid buster patch
openjdk-11-dcevm ftbfs on i386.
Also the build logs is very terse. Debian policy now says that the default for
build logs should be verbose.
dh binary-arch
dh_testroot -a
dh_prep -a
debian/rules
Your message dated Tue, 19 Feb 2019 10:51:05 +
with message-id
and subject line Bug#918611: fixed in ruby-jquery-atwho-rails 1.3.2-3
has caused the Debian Bug report #918611,
regarding ruby-jquery-atwho-rails FTBFS with rails 5.2
to be marked as done.
This means that you claim that the
On Tue, Feb 19, 2019 at 11:13:29AM +0100, Andreas Tille wrote:
> On Tue, Feb 19, 2019 at 09:07:24AM +0100, Ondřej Surý wrote:
> > I believe that it was the case before that if the autoremoval was due a
> > specific RC bug, any activity on that specific bug would reset the timer
> > for
Dear Sir or Madam,
the University of Potsdam is currently conducting research regarding
coring of extension functionality on digital platforms in the browser
context.
Specifically, we are interested in which _effects result to you as a
developer_ from platform coring. Furthermore, which
On Tue, Feb 19, 2019 at 09:07:24AM +0100, Ondřej Surý wrote:
> I believe that it was the case before that if the autoremoval was due a
> specific RC bug, any activity on that specific bug would reset the timer for
> autoremoval.
I've thought the same but despite the activity it is not reset (at
What can we do to not loose these packages (burp in my case)?
librsync 2.0.2-1~exp1 was uploaded to experimental three days ago.
Am 18.02.19 um 18:34 schrieb Valentin Vidic:
> Hi,
>
> Not sure why grave so late in the release process that we lose
> some packages (csync2 in my case)? grave
Hi,
On Thu, Feb 14, 2019 at 02:13:14PM +0100, Dr. Tobias Quathamer wrote:
>
> the package "debian-faq" has been uploaded three months ago and contains
> various important fixes. It's currently stuck in BYHAND.
>
> Is there any chance that we can get this package into buster?
and feb 15 it got
Hi,
I believe that it was the case before that if the autoremoval was due a
specific RC bug, any activity on that specific bug would reset the timer for
autoremoval.
But it might have changed since… or my memory is failing me.
Cheers,
Ondrej
> On 19 Feb 2019, at 08:46, Andreas Tille wrote:
75 matches
Mail list logo
