Package: libtidy5.6
Version: 1:5.6.0-0.1~exp1
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
when symbols in the library change, you need to actually bump the
SOVERSION/SONAME of the package. It's not enough and it's wrong
to just change the package name for several
Samuel Thibault, le ven. 12 oct. 2018 04:12:08 +0200, a ecrit:
> I'm thinking... My chroots have a lib -> usr/lib symlink. Could it be
> that python somehow gets lost between /lib/python* and /usr/lib/python*,
> and dependending on e.g. inode number or directory order, we could have
> one way or
Dear all,
While upgrading my system, I came across this bug (shared by apt-listbugs) .
I wonder if there are any gdbm databases which are built and have that
database.
The one example that was shared by6 Niko was of libmarc-charset-perl
an optional component. Maybe some core packges might be
Please always keep the bug in Cc, so that I am not the only
recipient of the mail. Writing to me only means risking falling in
the middle of my vacations and thus not getting an answer for weeks,
or that I just don't have the time to answer and thus you would at
best get a terse answer, or worse,
On 15/10/18 22:02, Samuel Thibault wrote:
Hello,
Keith Barrett, le dim. 14 oct. 2018 16:50:08 +0100, a ecrit:
I removed the package with a view to reinstalling but
invoke-rc.d: initscript espeakup, action "start" failed.
Mmm, perhaps you just need to have the speakup_soft module loaded?
Ian Jackson writes ("Re: xenstore-utils: removal of xenstore-utils makes files
disappear from xen-utils-common"):
> > The installation sequence to reproduce this problem is
> >
> > apt-get install xen-utils-common/stretch
> > # (1)
> > apt-get install xenstore-utils/sid
> > apt-get
> The installation sequence to reproduce this problem is
>
> apt-get install xen-utils-common/stretch
> # (1)
> apt-get install xenstore-utils/sid
> apt-get remove xenstore-utils
> # (2)
But this is not possible because xen-utils-common Depends on
xenstore-utils (even in stretch). You
Processing commands for cont...@bugs.debian.org:
> reassign 911056 chromium
Bug #911056 [chromium,webext-browserpass] chromium,webext-browserpass:
impossible to install chromium and webext-browserpass together
Bug reassigned from package 'chromium,webext-browserpass' to 'chromium'.
Ignoring
Unless chromium changed the places it looks for some files, I guess this is an
oversight in chromium and thus be fixed there.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes
Processing commands for cont...@bugs.debian.org:
> merge 911056 911067
Bug #911056 [chromium] chromium,webext-browserpass: impossible to install
chromium and webext-browserpass together
Bug #911056 [chromium] chromium,webext-browserpass: impossible to install
chromium and webext-browserpass
Processing commands for cont...@bugs.debian.org:
> forcemerge 899240 909658
Bug #899240 [debian-installer] debian-installer: blank screen on boot (6th Gen.
ThinkPad X1)
Bug #909658 [debian-installer] debian-installer: blank screen on install (HP
Elitebook 830 G5)
Severity set to 'normal' from
Processing control commands:
> merge 899240 -1
Bug #899240 [debian-installer] debian-installer: blank screen on boot (6th Gen.
ThinkPad X1)
Unable to merge bugs because:
severity of #909658 is 'important' not 'normal'
Failed to merge 899240: Did not alter merged bugs.
> severity -1 serious
Bug
Your message dated Mon, 15 Oct 2018 22:08:57 +
with message-id
and subject line Bug#885051: fixed in pdfmod 0.9.1-8.1
has caused the Debian Bug report #885051,
regarding pdfmod: Depends on old GNOME libraries
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> close 911120 1:0.80-11
Bug #911120 [espeakup] espeakup: Does not fully install
There is no source info for the package 'espeakup' at version '1:0.80-11' with
architecture ''
Unable to make a source version for version '1:0.80-11'
Marked as fixed
close 911120 1:0.80-11
thanks
Package: espeakup
Version: 1:0.80-10
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Frequent loss of speech in the console, particularly when
Your message dated Mon, 15 Oct 2018 21:27:33 +
with message-id
and subject line Bug#910915: fixed in fenrir 1.9.3-2
has caused the Debian Bug report #910915,
regarding fenrir: fails to install: SyntaxError
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 15 Oct 2018 21:26:28 +
with message-id
and subject line Bug#885672: fixed in cellwriter 1.3.6-1
has caused the Debian Bug report #885672,
regarding cellwriter: Unnecessary Build-Depend on libgnome
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> tags 910915 + pending
Bug #910915 [fenrir] fenrir: fails to install: SyntaxError
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
910915:
On Mon, Oct 15, 2018 at 3:59 PM Yavor Doganov wrote:
> It would be great if you can create a repository (possibly using gbp's
> --debsnap option), import it at Salsa and grant me commit access.
> That way, I can make gradual commits which will be easier to review by
> a potential sponsor (rather
Hello,
On Wed, 10 Oct 2018 19:19:53 +0200 Narcis Garcia
wrote:
> Stable packages aren't ready for Thunderbird 60 presence.
> It's better to wait for better repository consistence before adding this
> update.
With keeping Thunderbird at version 52 in stretch you mean to keep the
packages with
Ying-Chun Liu, please review the patch attached to
https://bugs.debian.org/868382 to fix the RC bug keeping gbatnav out
of Testing. If we don't hear from you soon, we will NMU this package.
Thanks,
Jeremy Bicha
Jeremy Bicha wrote:
> Yavor, I'm planning to orphan gniall now. Are you interested in being
> its maintainer in Debian? It's ok if you don't want to.
No, but if it gets orphaned, I can prepare a QA upload fixing other
packaging issues and take care of it in the future (I'm already
subscribed to
Hi,
Am 15.10.18 um 19:45 schrieb Erich Schubert:
> Hi,
>
> It seems the classpath is not set up correctly.
>
> With Java 11 as my main java, the following works:
>
> java -cp
>
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:xiphos
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package meson
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
Yavor, I'm planning to orphan gniall now. Are you interested in being
its maintainer in Debian? It's ok if you don't want to.
Thanks,
Jeremy
On Mon, Oct 15, 2018 at 4:30 AM Christoph Berg wrote:
> Can I help with the transition?
If you want, you can investigate why the build tests seem to hang with
postgresql 11.
You can check whether glom works with postgresql 11.
And you can report any issues to
Re: To Jeremy Bicha 2018-10-15 <20181015083032.gb6...@msg.df7cb.de>
> Re: Jeremy Bicha 2018-10-15
>
> > How soon do you need this issue fixed? I'm ok with glom being removed
> > from Testing if that helps.
>
> At the moment the biggest blocker is that llvm-toolchain-7 is not in
> testing (OOM
Your message dated Mon, 15 Oct 2018 23:54:39 +0530
with message-id
and subject line closing
has caused the Debian Bug report #903780,
regarding gitlab: fails to install: Could not find gem 'fog-google (~> 0.5)'
to be marked as done.
This means that you claim that the problem has been dealt with.
I'm having the same issue with libpsm2-2 version 11.2.68-1. Downgrading
to 10.3.58-2 fixes it for me.
--
Jonas Lippuner, PhD
Scientist
Computational Physics and Methods, CCS-2
Center for Theoretical Astrophysics
Los Alamos National Laboratory
jlippu...@lanl.gov
505-667-1646
Source: android-platform-dalvik
Version: 7.0.0+r33-1
Severity: serious
X-Debbugs-CC: saif...@cse.mrt.ac.lk
android-platform-dalvik depends and build-dpeends on
libandroid-dex-java but that package is no longer built by
android-platform-libcore.
This has led to android-sdk-meta being removed from
[2018-10-15 20:18] Niko Tyni
> > I am sorry to say it, but probably binNMU or sourceful upload would
> > be required for all packages, that bundle gdbm databases, generated
> > by (gdbm << 1.9)
>
> This sounds really sad. So even the gdbm we have in our current stable
> release is too old to
Hi,
It seems the classpath is not set up correctly.
With Java 11 as my main java, the following works:
java -cp
Control: reassign -1 cantor-backend-sage
Please provide more information. How can the bug be triggered? I'm not familiar
with cantor. If someone can demonstrate that the segfault is really in sage,
the bug can be reassigned to sagemath.
Best,
Tobias
On 10/15/2018 03:34 PM, Kinky Nekoboi
Processing control commands:
> reassign -1 cantor-backend-sage
Bug #911084 [sagemath] sagemath crashes as cantor backend
Bug reassigned from package 'sagemath' to 'cantor-backend-sage'.
No longer marked as found in versions sagemath/8.3-3.
Ignoring request to alter fixed versions of bug #911084
Your message dated Mon, 15 Oct 2018 17:34:12 +
with message-id
and subject line Bug#873156: fixed in fofix-dfsg 3.121-5
has caused the Debian Bug report #873156,
regarding fofix: FoFiX.py rises a NotImplementedError on startup
to be marked as done.
This means that you claim that the problem
On Mon, Oct 15, 2018 at 12:21:16AM +, Dmitry Bogatov wrote:
>
> [2018-10-13 13:20] Niko Tyni
> > The libgdbm6 transition broke autopkgtest checks of src:perl and
> > libmarc-charset-perl.
> >
> > It looks like some GDBM databases which were working with the older
> > gdbm are not readable
Hello,
FreedomBox is set to be autoremoved from testing on 2018/10/21 (in about
5 days) due to mod-gnutls which won't transition into testing which in
turn due won't migrate to testing due to its dependency on moneysphere.
This effects all FreedomBox users.
Please consider uploading the
On Mon, Oct 15, 2018 at 12:27 PM Yavor Doganov wrote:
>
> Jeremy Bicha wrote:
> > On Mon, Oct 15, 2018 at 9:13 AM Yavor Doganov wrote:
> > > Please do what you think is best.
> >
> > No. I'm delegating this decision to you. There is no upstream. There
> > is no Debian maintainer. You're the
Hello,
2018 m. spalio 15 d., pirmadienis 16:11:38 EEST Patrick Franz rašė:
> >
> > dpkg: erreur de traitement de l'archive /var/cache/apt/archives/
>
> chromium_70.0.3538.54-2_amd64.deb (--unpack) :
> > tentative de remplacement du répertoire « /etc/chromium » dans le
>
> paquet
Jeremy Bicha wrote:
> On Mon, Oct 15, 2018 at 9:13 AM Yavor Doganov wrote:
> > Please do what you think is best.
>
> No. I'm delegating this decision to you. There is no upstream. There
> is no Debian maintainer. You're the closest we have to either one of
> those for this package.
If your
Your message dated Mon, 15 Oct 2018 16:21:49 +
with message-id
and subject line Bug#899594: fixed in lirc-compat-remotes 0.9.0-1.1
has caused the Debian Bug report #899594,
regarding lirc-compat-remotes: Invalid maintainer address
pkg-lirc-ma...@lists.alioth.debian.org
to be marked as done.
Your message dated Mon, 15 Oct 2018 16:21:36 +
with message-id
and subject line Bug#899578: fixed in libirman 0.5.2-1.1
has caused the Debian Bug report #899578,
regarding libirman: Invalid maintainer address
pkg-lirc-ma...@lists.alioth.debian.org
to be marked as done.
This means that you
Your message dated Mon, 15 Oct 2018 16:22:22 +
with message-id
and subject line Bug#899663: fixed in pylirc 0.0.5-3.1
has caused the Debian Bug report #899663,
regarding pylirc: Invalid maintainer address
pkg-lirc-ma...@lists.alioth.debian.org
to be marked as done.
This means that you claim
Your message dated Mon, 15 Oct 2018 16:21:43 +
with message-id
and subject line Bug#899981: fixed in lirc 0.10.1-2
has caused the Debian Bug report #899981,
regarding lirc: Invalid maintainer address
pkg-lirc-ma...@lists.alioth.debian.org
to be marked as done.
This means that you claim that
On Mon, Oct 15, 2018 at 05:12:10PM +0200, Andreas Beckmann wrote:
> Package: libapt-pkg5.0
> Version: 1.7.0
> Severity: serious
>
> Hi,
>
> I just did a partial upgrade on a stretch+buster+sid development
> system resulting in apt-get erroring out with
>
> apt-get: relocation error:
Processing control commands:
> tags -1 patch pending
Bug #899663 [src:pylirc] pylirc: Invalid maintainer address
pkg-lirc-ma...@lists.alioth.debian.org
Added tag(s) pending and patch.
--
899663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899663
Debian Bug Tracking System
Contact
control: tags -1 patch pending
uploaded in unstable the following debdiff
--- pylirc-0.0.5/debian/changelog 2011-06-14 22:24:16.0 +0200
+++ pylirc-0.0.5/debian/changelog 2018-10-15 18:10:22.0 +0200
@@ -1,3 +1,10 @@
+pylirc (0.0.5-3.1) unstable; urgency=medium
+
+ *
Control: tags 899578 + patch
Control: tags 899578 + pending
diff -Nru libirman-0.5.2/debian/changelog libirman-0.5.2/debian/changelog
--- libirman-0.5.2/debian/changelog 2016-10-29 05:19:40.0 +0200
+++ libirman-0.5.2/debian/changelog 2018-10-15 18:06:39.0 +0200
@@ -1,3
Processing control commands:
> tags 899578 + patch
Bug #899578 [src:libirman] libirman: Invalid maintainer address
pkg-lirc-ma...@lists.alioth.debian.org
Added tag(s) patch.
> tags 899578 + pending
Bug #899578 [src:libirman] libirman: Invalid maintainer address
Hi Jörg,
it seems there is an accepted solution for this bug since almost two weeks:
- rename libsane1 back to libsane
- add a "Provides: libsane1" to libsane
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908681#51
Why isn't that route followed?
Thanks,
Philip
signature.asc
On 14.10.18 at 14:35 Jeremy Bicha wrote:
> Control: severity -1 serious
>
> On Sat, 13 Oct 2018 at 19:59:38 Philip Rinn wrote:
>> Control: -1 severity normal
>>
>> Hi,
>>
>> I lower the severity of this bug as I couldn't find a severe violation of the
>> Debian policy - please point me to it if
Package: libjetbrains-annotations-java
Version: 16.0.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused
Control: block -1 by 908681
Hi,
I'm really sorry that gImageReader in testing is still not fixed. Unfortunately
it's still blocked by the back and forth due to the libsane -> libsane1
transition
- although it's technically totally unrelated, it just happened during the same
time.
Best,
Philip
Processing control commands:
> block -1 by 908681
Bug #909099 {Done: Philip Rinn } [gimagereader]
gimagereader: crashes at startup
909099 was not blocked by any bugs.
909099 was not blocking any bugs.
Added blocking bug(s) of 909099: 908681
--
909099:
Your message dated Mon, 15 Oct 2018 15:35:18 +
with message-id
and subject line Bug#906602: fixed in haskell-hashable 1.2.7.0-5
has caused the Debian Bug report #906602,
regarding haskell-hashable: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim
Dear maintainer,
after updating from 4.18.0-1-amd64 to 4.18.0-2-amd64 the behaviour of my system
seems to be back to normal. As far as I can see this bug is fixed for me.
Best regards and thank you for your time
G. Heine
Package: python3.5-minimal
Version: 3.5.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + python3-pymca5-dbg
Control: found -1 python3-pymca5-dbg/5.4.0+dfsg-1
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It
Processing control commands:
> affects -1 + python3-pymca5-dbg
Bug #911091 [python3.5-minimal] python3.5-minimal: incompatible with
python3-minimal 3.5.3-1 from stretch
Added indication that 911091 affects python3-pymca5-dbg
> found -1 python3-pymca5-dbg/5.4.0+dfsg-1
Bug #911091
Dear maintainer
I wrote that I use Debian Jessie with the MATE desktop environment.
However, I should have written that I use Stretch with the MATE desktop
environment. I upgraded from Jessie to Stretch only two months ago.
Furthermore, the Bug Tracking System has indicated that
Package: libapt-pkg5.0
Version: 1.7.0
Severity: serious
Hi,
I just did a partial upgrade on a stretch+buster+sid development
system resulting in apt-get erroring out with
apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-private.so.0.0:
symbol
Processing control commands:
> severity -1 grave
Bug #886394 [pdfsam] java.lang.ClassNotFoundException: javafx.scene.layout.HBox
Severity set to 'grave' from 'important'
> block -1 by 910764
Bug #886394 [pdfsam] java.lang.ClassNotFoundException: javafx.scene.layout.HBox
886394 was not blocked by
On Mon, Oct 15, 2018 at 12:55:54PM +0200, Michael Schubert wrote:
> ./gtimelog currently fails with the following traceback:
>
> Traceback (most recent call last):
> File "/usr/bin/gtimelog", line 11, in
...
> File "/usr/lib/python3/dist-packages/gtimelog/main.py", line 55, in
>
On Mon, Oct 15, 2018 at 9:13 AM Yavor Doganov wrote:
> Jeremy Bicha wrote:
> > On Sun, Oct 14, 2018 at 5:00 PM Yavor Doganov wrote:
> > > I am not in a position to decide the faith of a package that I do not
> > > maintain.
> >
> > With its very low popcon and the fact that it has no maintainer
Package: sagemath
Version: 8.3-3
Severity: serious
Justification: unkown
as above
cantor-sage-backend crashes with Segmentation fault.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux
forwarded 909837 https://github.com/libreswan/libreswan/issues/206
close 909837 3.27-1
thanks
Processing commands for cont...@bugs.debian.org:
> forwarded 909837 https://github.com/libreswan/libreswan/issues/206
Bug #909837 [src:libreswan] libreswan: FTBFS on armel, armhf, i386, mips, mipsel
Bug #909839 [src:libreswan] libreswan FTBFS on 32bit
Set Bug forwarded-to-address to
On Mon, Oct 15, 2018 at 06:33:50PM +0530, Pirate Praveen wrote:
> On Sat, 13 Oct 2018 23:42:59 +0300 Adrian Bunk wrote:
> > Package: libprotobuf17
> > Version: 3.6.1-2
> > Severity: serious
> > Control: affects -1 src:cura-engine
>
> I think this was caused by another dependency still built
Control: tag -1 pending
Hello,
Bug #910974 in utidylib 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 #910974 [src:utidylib] utidylib: FTBFS with new tidy-html5 5.7.16:
Build-dep list needs updating, test fails (upstream behaviour change)
Added tag(s) pending.
--
910974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910974
Debian Bug
Hi
On Mon, 15 Oct 2018 12:28:05 +0200 wrote:
> Package: chromium
> Version: 70.0.3538.54-1
> Severity: serious
> Justification: Policy 10.7.4
>
> dpkg: erreur de traitement de l'archive /var/cache/apt/archives/
chromium_70.0.3538.54-2_amd64.deb (--unpack) :
> tentative de remplacement du
Jeremy Bicha wrote:
> On Sun, Oct 14, 2018 at 5:00 PM Yavor Doganov wrote:
> > I am not in a position to decide the faith of a package that I do not
> > maintain.
>
> With its very low popcon and the fact that it has no maintainer in
> Debian (or anywhere), I think your opinion is the most
Your message dated Mon, 15 Oct 2018 13:06:29 +
with message-id
and subject line Bug#840377: fixed in pyepl 1.1.0+git12-g365f8e3-3
has caused the Debian Bug report #840377,
regarding pyepl: Please remove build dependency on jade
to be marked as done.
This means that you claim that the problem
Your message dated Mon, 15 Oct 2018 13:07:21 +
with message-id
and subject line Bug#911068: fixed in ranger 1.9.2-2
has caused the Debian Bug report #911068,
regarding ranger: broken symlinks: /etc/ranger/*/*.* ->
/usr/lib/python3.6/dist-packages/ranger/*/*.*
to be marked as done.
This
Your message dated Mon, 15 Oct 2018 13:06:29 +
with message-id
and subject line Bug#866459: fixed in pyepl 1.1.0+git12-g365f8e3-3
has caused the Debian Bug report #866459,
regarding pyepl: depends on obsolete python-imaging (replace with python3-pil
or python-pil)
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> notfound 910806 4.9.0.2652-3
Bug #910806 {Done: Alexandre Rossi } [davmail]
Latest testing update (4.9.0.2652-2) fails to execute in daemon mode
Ignoring request to alter found versions of bug #910806 to the same values
previously set
> thanks
Processing control commands:
> tags -1 unreproducible
Bug #911079 [pdfsam] [pdfsam] Window blank
Added tag(s) unreproducible.
> severity -1 important
Bug #911079 [pdfsam] [pdfsam] Window blank
Severity set to 'important' from 'grave'
--
911079:
Control: tags -1 unreproducible
Control: severity -1 important
Am 15.10.18 um 14:11 schrieb Marco Righi:
> Package: pdfsam
> Version: 1.1.4-4
> Severity: grave
>
> --- Please enter the report below this line. ---
> Hi,
> After pdfsam execution appears only a little box (see image_1).
> After
Your message dated Mon, 15 Oct 2018 13:59:24 +0200
with message-id <027cd8ae-21bd-fb02-db36-7e7730a9e...@fishpost.de>
and subject line gambas3: FTBFS w/SDL2 2.0.7+: MIX_INIT_FLUIDSYNTH undeclared
has caused the Debian Bug report #900998,
regarding gambas3: FTBFS w/SDL2 2.0.7+: MIX_INIT_FLUIDSYNTH
Package: triplea
Version: 1.9.0.0.7062-2
Severity: grave
Justification: renders package unusable
After the switch to OpenJFX 11, triplea fails to start with a
NullPointerException.
triplea.engine.version.bin:1.9
java.lang.NullPointerException
at
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 910836 piuparts
There were no usertags set.
Usertags are now: piuparts.
> severity 911049 serious
Bug #911049
Package: gtimelog
Version: 0.11.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
./gtimelog currently fails with the following traceback:
Traceback (most recent call last):
File "/usr/bin/gtimelog", line 11, in
load_entry_point('gtimelog==0.11.1',
On Sun, Oct 14, 2018 at 04:02:06PM -0300, Rogério Brito wrote:
> Second, I would like to more formally update youtube-dl for stable releases
> in conjunction with Holger.
yay!
> So, what is the way to proceed with updates to stable releases? I've never
> done that before.
you file a bug
Package: ranger
Version: 1.9.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
/etc/ranger/data/scope.sh ->
On Sun, Oct 14, 2018 at 03:08:34AM +0200, Javier Serrano Polo wrote:
> El ds 13 de 10 de 2018 a les 11:14 +, Holger Levsen va escriure:
> > why don't you attach your fix to this bug?
> Because I am the lazy maintainer.
shrugs then.
--
cheers,
Holger
Package: chromium
Version: 70.0.3538.54-1
Severity: serious
Justification: Policy 10.7.4
dpkg: erreur de traitement de l'archive
/var/cache/apt/archives/chromium_70.0.3538.54-2_amd64.deb (--unpack) :
tentative de remplacement du répertoire « /etc/chromium » dans le paquet
chrome-gnome-shell
Hi Andreas,
On 10/15/2018 12:54 PM, Andreas Tille wrote:
> when I tried last time we had antlr 4.5. I now tried with 4.6 but it
> seems 4.7 is really needed. Any chance to get this soon?
I am interested in packaging antlr 4.7 (with Cpp support, needed for #902798),
I am working on it right
Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in
git-format-patch form)"):
> It's not that much trouble for me but rather sad that people spent time
> on (in this case) just tedious work while they could fix other stuff
> in the same time since the maintainer is already on
Hi,
when I tried last time we had antlr 4.5. I now tried with 4.6 but it
seems 4.7 is really needed. Any chance to get this soon?
Kind regards
Andreas.
On Sat, Aug 04, 2018 at 11:23:42AM +0200, Andreas Tille wrote:
> On Thu, Jul 19, 2018 at 09:44:30AM +0200, Emmanuel Bourg wrote:
> >
Your message dated Mon, 15 Oct 2018 08:38:05 +
with message-id
and subject line Bug#907952: fixed in openvswitch
2.10.0+2018.08.28+git.8ca7c82b7d+ds1-6
has caused the Debian Bug report #907952,
regarding openvswitch-common: Fails to install due to file conflict
to be marked as done.
This
Package: ukui-control-center
Version: 1.1.6-1
Severity: serious
The following packages have unmet dependencies:
ukui-control-center : Depends: gnome-control-center-faces but it is not
installable
On 2018-10-15 10:12 +0200, Jonas Smedegaard wrote:
> Package: chromium,webext-browserpass
> Severity: serious
> Justification: 7
>
> With chromium 70.0.3538.54-1 and webext-browserpass 2.0.11+dfsg-2 installed,
> attempting to upgrade to chromium 70.0.3538.54-2 fails:
>
> Gør klar til at udpakke
Your message dated Mon, 15 Oct 2018 10:28:55 +0200
with message-id <20181015082855.qr3ufszgbqhmx...@sk2.org>
and subject line Re: Bug#909035: dependency missing to libx11-protocol-perl
has caused the Debian Bug report #909035,
regarding dependency missing to libx11-protocol-perl
to be marked as
Re: Jeremy Bicha 2018-10-15
> How soon do you need this issue fixed? I'm ok with glom being removed
> from Testing if that helps.
At the moment the biggest blocker is that llvm-toolchain-7 is not in
testing (OOM when stripping on mips(el)), so it's not urgent anyway.
But that could change
Package: chromium,webext-browserpass
Severity: serious
Justification: 7
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
With chromium 70.0.3538.54-1 and webext-browserpass 2.0.11+dfsg-2 installed,
attempting to upgrade to chromium 70.0.3538.54-2 fails:
Gør klar til at udpakke
Hi,
On Sun, Oct 14, 2018 at 10:55:10PM +0100, Ian Jackson wrote:
> Guido Günther writes ("Re: Bug#910446: NMU diff (substantive patches in
> git-format-patch form)"):
> > On Sun, Oct 14, 2018 at 03:36:49PM +0100, Ian Jackson wrote:
> > > Hi. I fixed this bug, and some other FTBFS, and am about
Quoting Paul Wise (2018-10-15 05:49:46)
> On Tue, 02 Oct 2018 00:57:59 +0200 Jonas Smedegaard wrote:
>
> > planet-venus only reference BeautifulSoup in a vendor dir which is fully
> > patched out and therefore irrelevant.
>
> In that case the Recommends should be removed, reopening.
Oh,
Processing control commands:
> notfixed -1 7.3.0~rc2-2
Bug #909110 {Done: OndÅej Surý } [php7.3-dev] Extraneous 'L'
in /usr/bin/phpize7.3
No longer marked as fixed in versions 7.3.0~rc2-2.
> fixed -1 7.3.0~rc3-1
Bug #909110 {Done: OndÅej Surý } [php7.3-dev] Extraneous 'L'
in
Control: notfixed -1 7.3.0~rc2-2
Control: fixed -1 7.3.0~rc3-1
No, I am sorry, you are right, it was correctly fixed in 7.3.0~rc2-3, and it’s
also included in 7.3.0~rc3-1 that I just uploaded.
Ondrej
--
Ondřej Surý
ond...@sury.org
> On 15 Oct 2018, at 08:55, Kunal Mehta wrote:
>
> Hi,
>
>
1 - 100 of 104 matches
Mail list logo
