Subject: elpa-lsp-haskell: recommends haskell-ide-engine and lsp-ui which are
not in unstable
Package: elpa-lsp-haskell
Version: 1.0.20211214-1
Severity: minor
User: car...@pina.cat
Usertags: package-relations
Dear maintainer,
I see that the package elpa-lsp-haskell (version 1.0.20211214-1
Subject: fwsnort: recommends snort-rules-default which is not in unstable
Package: fwsnort
Version: 1.6.8-2
Severity: minor
User: car...@pina.cat
Usertags: package-relations
Dear maintainer,
I see that the package fwsnort (version 1.6.8-2) recommends snort-rules-default
which is not in unstable
Subject: dvbackup: recommends rsbep which is not in unstable
Package: dvbackup
Version: 1:0.0.4-11
Severity: minor
User: car...@pina.cat
Usertags: package-relations
Dear maintainer,
I see that the package dvbackup (version 1:0.0.4-11) recommends rsbep
which is not in unstable.
This can be seen
Subject: display-dhammapada: recommends linotify-bin which is not in unstable
Package: display-dhammapada
Version: 1.0-1
Severity: minor
User: car...@pina.cat
Usertags: package-relations
Dear maintainer,
I see that the package display-dhammapada (version 1.0-1) recommends
linotify-bin
which is
Package: rsh-server
Version: 0.17-24
Severity: important
Dear Maintainer,
rsh-server depends on inet-superserver which is provided by inetutils-inetd or
xinetd
rsh-server, in its postinst, launches update-inetd, which is ONLY provided by
inetutils-inetd and NOT by xinetd.
Therefore, if
Package: rsh-server
Version: 0.17-24
Severity: important
Dear Maintainer,
rsh-server depends on inet-superserver which is provided by inetutils-inetd or
xinetd
rsh-server, in its postinst, launches update-inetd, which is ONLY provided by
inetutils-inetd and NOT by xinetd.
Therefore, if you
ssing archive
/var/cache/apt/archives/pacman.c_0+git20240818+ds-1+b1_amd64.deb (--unpack):
trying to overwrite '/usr/games/pacman', which is also in package pacman 10-20
Errors were encountered while processing:
/var/cache/apt/archives/pacman.c_0+git20240818+ds-1+b1_amd64.deb
Since both p
Your message dated Thu, 4 Jul 2024 14:48:46 +0200
with message-id <94c466cc-384a-43e3-8116-323659530...@debian.org>
and subject line Re: please show which commands are run
has caused the Debian Bug report #355121,
regarding please show which commands are run
to be marked as done.
This mean
Your message dated Mon, 2 Oct 2023 18:03:33 -0400
with message-id <56c01718-98dd-4513-9a1f-26aa29fbf...@kamens.us>
and subject line Deprecation of which has been reverted, this ticket is moot
has caused the Debian Bug report #998806,
regarding deprecated which
to be marked as done.
This
Your message dated Mon, 28 Aug 2023 07:18:53 +
with message-id
and subject line Bug#1037213: fixed in awstats 7.9-1
has caused the Debian Bug report #1037213,
regarding awstats: prompting due to modified conffiles which were not modified
by the user: /etc/logrotate.d/httpd-prerotate/awstats
Your message dated Mon, 03 Jul 2023 23:41:55 +
with message-id
and subject line Bug#1040237: Removed package(s) from unstable
has caused the Debian Bug report #678493,
regarding masqmail: prompting due to modified conffiles which were not modified
by the user
to be marked as done.
This
/debian-policy/ch-files.html#behavior,
which says "[These scripts handling conffiles] must not ask unnecessary
questions (particularly during upgrades), and must otherwise be good
citizens."
https://wiki.debian.org/DpkgConffileHandling should help with figuring
out how to do this properly.
Your message dated Tue, 09 May 2023 15:08:22 +
with message-id
and subject line Bug#1035818: Removed package(s) from unstable
has caused the Debian Bug report #964571,
regarding Languages are installed in a directory which is not expected by
"bygfoot"
to be marked as done.
This
Your message dated Fri, 14 Apr 2023 03:19:05 +
with message-id
and subject line Bug#1008579: fixed in a2ps 1:4.14-8
has caused the Debian Bug report #1008579,
regarding a2ps: 'fixps -f' calls gs device 'pswrite' which should be 'ps2write'
to be marked as done.
Hi Ondřej,
Please use the original bug. I have changed the BTS address.
Am 04.04.23 um 22:25 schrieb Ondřej Surý:
I went through the upstream changes between 20171227..20190702
and as far as I can tell, there's nothing important in there:
...
Out of these, there are only two commits that might
Am 23.03.23 um 09:58 schrieb Paul Gevers:
Bastian, if you really want that threaded bug fixed, please prepare a targeted fix based on the version currently in
bookworm and revert all other changes. We can then review the targeted fix. But I'll not unblock the version of argon2
as it's currently
Processing control commands:
> tags -1 d-i
Bug #1032235 {Done: Guilhem Moulin } [libargon2-1]
cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work
Added tag(s) d-i.
--
1032235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032235
Debian Bug Tracking System
Contact ow...@bug
I do not insist on it.
cryptsetup can only migrate when argon2 migrates, which leaves me two
options: letting argon2 in as it is now in unstable or going for
cryptsetup via t-p-u. Both sub-optimal, because argon2 has changes that
weren't even meeting the freeze policy rules at the time o
b.
Ack.
As I already mentioned on this or some related bug, I would find it nice
for #1014110 to be fixed in bookworm (threaded argon2 executable) but I
do not insist on it.
cryptsetup can only migrate when argon2 migrates, which leaves me two
options: letting argon2 in as it is now in unstab
argon2 migrates,
I see that in the excuse page now but don't understand the reason why,
there was no ABI change in the src:argon2 upload and libcryptsetup12 has
‘Depends: libargon2-1 (>= 0~20171227)’. I'm not really familiar with
britney's logic but don't understand w
On Thu, 16 Mar 2023 at 16:01:47 +0100, Paul Gevers wrote:
> On 16-03-2023 14:31, Guilhem Moulin wrote:
>>> cryptsetup can only migrate when argon2 migrates,
>>
>> I see that in the excuse page now but don't understand the reason why,
>
> It took me a while and the help of colleagues, but it's libcr
27;s binaries missing a dependency?
It was intentional, see the article
https://developers.redhat.com/articles/2021/12/17/why-glibc-234-removed-libpthread
.
Unfortunately that change broke initramfs-tools' fix for
https://bugs.debian.org/950254
which we (src:cryptsetup maintainers) relied on for
>
> > As I already mentioned on this or some related bug, I would find it nice
> > for #1014110 to be fixed in bookworm (threaded argon2 executable) but I
> > do not insist on it.
>
> cryptsetup can only migrate when argon2 migrates, which leaves me two
> options
Hi,
On Thu, 16 Mar 2023 at 09:13:44 +0100, Paul Gevers wrote:
> On 15-03-2023 23:28, Guilhem Moulin wrote:
>> Yes there is, namely the fact that libargon2-1 no longer links against
>> libpthread, which in turn caused a major regression in
>> cryptsetup-initramfs (mitigate
Am 16.03.23 um 09:13 schrieb Paul Gevers:
I'm not 100% sure I parse that sentence as you intended, so let me ask explicitly: if we binNMU (now or in the future)
src:argon2 version 0~20171227-0.3 in bookworm, would it also loose its linking to libpthread? That would be a time bomb
(not only in th
nger links against
libpthread, which in turn caused a major regression in
cryptsetup-initramfs (mitigated in src:cryptsetup 2:2.6.1-2). Unlike
what I initially claimed in #1014110's msg#20 that change can't be
reverted or fixed in src:argon2 since it's caused by building with a
n
ue for cryptsetup is worked around in cryptsetup
>>
>> libargon2-1 is linked by more packages. Are they all OK without this
>> unintentional change unfixed? Why is the unintentional change not
>> reverted or fixed?
>
> There is no unintentional change.
Yes there is, namely the
Am 15.03.23 um 22:39 schrieb Paul Gevers:
Hi,
[Release Team here]
On Thu, 2 Mar 2023 18:42:56 +0100 Bastian Germann wrote:
On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin wrote:
> Ah no my bad, the changelog entry is probably incorrect and the
> cryptsetup-initramfs breakage is caused by th
Hi,
[Release Team here]
On Thu, 2 Mar 2023 18:42:56 +0100 Bastian Germann wrote:
On Thu, 2 Mar 2023 05:10:41 +0100 Guilhem Moulin wrote:
> Ah no my bad, the changelog entry is probably incorrect and the
> cryptsetup-initramfs breakage is caused by the recent libargon2 upload
> indeed, but AFA
Your message dated Wed, 15 Mar 2023 20:39:46 +
with message-id
and subject line Bug#1008579: fixed in a2ps 1:4.15.1-1~exp1
has caused the Debian Bug report #1008579,
regarding a2ps: 'fixps -f' calls gs device 'pswrite' which should be 'ps2write'
to be marked
Your message dated Sun, 12 Feb 2023 19:33:27 +0200
with message-id
and subject line Re: Bug#1014643: Depends on mplayer which isn't in testing
has caused the Debian Bug report #1014646,
regarding Depends on mplayer which isn't in testing
to be marked as done.
This means that you clai
Your message dated Tue, 27 Dec 2022 21:44:31 +
with message-id
and subject line Bug#1026929: Removed package(s) from unstable
has caused the Debian Bug report #944522,
regarding libsparkline-php: use of Object which is now a reserved word
to be marked as done.
This means that you claim that
Your message dated Wed, 23 Nov 2022 21:34:15 +
with message-id
and subject line Bug#856829: fixed in checkpw 1.02-3
has caused the Debian Bug report #856829,
regarding checkpw: Please use "that" over "which" in package short description
to be marked as done.
This means
Your message dated Thu, 8 Sep 2022 15:25:39 +0200
with message-id
and subject line Closing already long fixed bugs
has caused the Debian Bug report #689595,
regarding xine-ui: 0.99.7-1 pulls in libvdpau1, which crashes upon startup on
non nvidia hardware
to be marked as done.
This means that
Processing control commands:
> clone -1 -2 -3 -4
Bug #1014643 [dradio] Depends on mplayer which isn't in testing
Bug 1014643 cloned as bugs 1014644-1014646
> reassign -2 qwinff 0.2.1+git20201215-1
Bug #1014644 [dradio] Depends on mplayer which isn't in testing
Bug reassigned from
Package: dradio
Version: 3.8-2
Tags: sid bookworm
Severity: serious
Control: clone -1 -2 -3 -4
Control: reassign -2 qwinff 0.2.1+git20201215-1
Control: reassign -3 vdr-plugin-mp3 0.10.4-2
Control: reassign -4 videotrans 1.6.1-8
Dear maintainer,
Your package Depends on mplayer, which currently
Package: fslint
Severity: wishlist
X-Debbugs-Cc: waxh...@dirtcellar.net
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
fslint is no longer avalable
* What exactly did you do (or not do) that was effective (or
Package: a2ps
Version: 1:4.14-7
Severity: important
Dear Maintainer,
The 'fixps' program fails when performing a full GS rewrite due to
$ grep pswrite /usr/bin/fixps
$gs -q -dSAFER -dNOPAUSE -dBATCH -sDEVICE=pswrite
-sOutputFile=- -c save pop -f $file ;;
whic
Your message dated Thu, 17 Mar 2022 03:59:32 +
with message-id
and subject line Bug#1007221: Removed package(s) from unstable
has caused the Debian Bug report #744768,
regarding libnfsidmap2 fails to obtain username which results in failed
translation
to be marked as done.
This means that
Package: tango-icon-theme
Version: 0.8.90-8
Severity: normal
X-Debbugs-Cc: jaap.keu...@xs4all.nl
Dear Maintainer,
When running XFCE4 launching KDE applications from a terminal (e.g. Konsole)
leads to the warning "Icon theme "crystalsvg" not found."
Looking at the Tango icon theme the index file (
://gitlab.gnome.org/Archive/amtk and
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/564 for
more details.
The versions of gedit and devhelp on GNOME infrastructure stopped using
amtk at the same time they stopped using tepl, which is in a similar
situation (see #993909). I don't
Processing control commands:
> block 993922 by -1
Bug #993922 [src:amtk] amtk: abandoned upstream
993922 was blocked by: 993909 993929 993928
993922 was not blocking any bugs.
Added blocking bug(s) of 993922: 993931
--
993922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993922
993931: http
Your message dated Thu, 08 Apr 2021 13:00:13 +
with message-id
and subject line Bug#845960: fixed in x-tile 3.3-1
has caused the Debian Bug report #845960,
regarding x-tile: depends on python-gnome2 which deprecated
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 17 Feb 2021 00:49:38 +
with message-id
and subject line Bug#958597: fixed in pmacct 1.7.6-2
has caused the Debian Bug report #958597,
regarding pmacct: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that the
Your message dated Thu, 04 Feb 2021 20:26:05 +
with message-id
and subject line Bug#958597: fixed in pmacct 1.7.5-2
has caused the Debian Bug report #958597,
regarding pmacct: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that the
Your message dated Mon, 01 Feb 2021 22:18:23 +
with message-id
and subject line Bug#980504: Removed package(s) from unstable
has caused the Debian Bug report #391101,
regarding Readline should have a mode which allows the use of both the emacs
and the vi keys
to be marked as done.
This
Your message dated Wed, 30 Dec 2020 04:18:21 +
with message-id
and subject line Bug#978609: fixed in a2ps 1:4.14-6
has caused the Debian Bug report #978609,
regarding a2ps: uses embedded copy of help2man which embeds timestamps
to be marked as done.
This means that you claim that the problem
, and thus embeds
timestamps in generated manpages.
The attached patch adds help2man to build-depends and patches various
Makefiles to use the system help2man binary, which supports
SOURCE_DATE_EPOCH.
Thanks for maintaining a2ps!
live well,
vagrant
From 3dd10ad40c8d8d4af9d8c0e3c749dde69d620a57 Mon
Control: forcemerge 967485 -1
On Wed, Nov 18, 2020 at 12:09:30AM +1100, Hugh McMaster wrote:
> Hi Adrian,
Hi Hugh,
> On Tue, 17 Nov 2020 at 03:53, Adrian Bunk wrote:
>
> > What is the point of moving libexif-gtk to GTK3 when the only package
> > using it does not support it?
> >
> > This sounds
on libexif-gtk, which is moving to
GTK3
Severity set to 'normal' from 'serious'
947713 was blocked by: 967278 967727 967341 967384 967332 885135 967723 967300
967255 967394 967310 967577 967673 967743 967747 967321 967677 967573 967374
967665 967752 967288 967565 967298 9675
On Mon, Oct 12, 2020 at 11:04:42PM +1100, Hugh McMaster wrote:
>...
> libexif-gtk is moving to GTK3 in response to #967573.
>
> gtkman also only supports GTK2, which means it blocks the introduction of
> libexif-gtk built on GTK3.
>...
What is the point of moving libexif-gt
Your message dated Fri, 06 Nov 2020 08:49:24 +
with message-id
and subject line Bug#958607: fixed in pppconfig 2.3.25
has caused the Debian Bug report #958607,
regarding pppconfig: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that
Your message dated Mon, 12 Oct 2020 10:00:31 +
with message-id
and subject line Bug#958620: fixed in sanlock 3.8.2-1
has caused the Debian Bug report #958620,
regarding sanlock: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that
Your message dated Sun, 06 Sep 2020 15:34:53 +
with message-id
and subject line Bug#958621: fixed in schroot 1.6.10-10
has caused the Debian Bug report #958621,
regarding schroot: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> tags 958621 patch
Bug #958621 [src:schroot] schroot: Build-Depends on deprecated dh-systemd which
is going away
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958621: https://bugs.debi
Hi,
I've prepared a merge request in gitlab to remove the dependency on dh-systemd
and update the required version of debhelper:
https://salsa.debian.org/debian/schroot/-/merge_requests/1
I've also attached to this mail the same proposed patch.
--
https://bugs.debian.org/cgi-bin/bugreport.cgi?
Your message dated Wed, 03 Jun 2020 21:59:14 +
with message-id
and subject line Bug#961749: Removed package(s) from unstable
has caused the Debian Bug report #925451,
regarding xenomai-kernel-source: depends on kernel-package, which will not be
in buster
to be marked as done.
This means
Your message dated Thu, 23 Apr 2020 23:18:48 +
with message-id
and subject line Bug#958595: fixed in nvi 1.81.6-16
has caused the Debian Bug report #958595,
regarding nvi: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.
This means that you claim that the
Source: schroot
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal
Hi,
your package schroot declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transiti
Source: sanlock
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal
Hi,
your package sanlock declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transiti
Source: pppconfig
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal
Hi,
your package pppconfig declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty tran
Source: nvi
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal
Hi,
your package nvi declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional pac
0.so.5.0.0', which is also in
package libdleyna-core-1.0-3:amd64 0.6.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If y
processing archive
/tmp/apt-dpkg-install-B5lolQ/064-libdleyna-core-1.0-5_0.6.0-3_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0',
which is also in package libdleyna-core-1.0-3:amd64 0.6.0-1
Looks like a missing Breaks/Replaces: 0.
Package: libsparkline-php
Version: 0.2-7
Severity: normal
I invoke sparkline via ikiwiki's sparkline plugin. Since updating to Buster
I now get:
remote: PHP Fatal error: Cannot use 'Object' as class name as it is reserved
in /usr/share/php/sparkline/Object.php on line 71
-- System Information
Processing commands for cont...@bugs.debian.org:
> severity 942977 serious
Bug #942977 [src:disk-manager] disk-manager: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> severity 937453 serious
Bug #937453 [src:pygtksourceview] pygtksourceview: Python2 removal in
sid/bulls
Your message dated Fri, 18 Oct 2019 04:23:38 +
with message-id
and subject line Bug#936210: Removed package(s) from unstable
has caused the Debian Bug report #543273,
regarding bittorrent: does not handle announce url which already contains
server variable
to be marked as done.
This means
Your message dated Fri, 18 Oct 2019 04:23:38 +
with message-id
and subject line Bug#936210: Removed package(s) from unstable
has caused the Debian Bug report #482478,
regarding bittorrent: btlaunchmany checks all files at once which hits the
system hard
to be marked as done.
This means that
Your message dated Mon, 30 Sep 2019 14:51:55 +
with message-id
and subject line Bug#933588: fixed in smlnj 110.79-5
has caused the Debian Bug report #933588,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in
bullseye
to be marked as done.
This means that
Your message dated Tue, 03 Sep 2019 01:05:31 +
with message-id
and subject line Bug#524981: fixed in xmldiff 2.3-1
has caused the Debian Bug report #524981,
regarding xmldiff: "IndexError" when comparing two files which have namespaces
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> clone 933280 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
Bug #933280 [src:breathe] BD on texlive-generic-extra which isn't build anymore
and isn't in bullseye
Bug 933280 cloned as bugs 933581-933591
> reassign -1 python-networkx 2
clone 933280 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
reassign -1 python-networkx 2.2-1
reassign -2 python-pymzml 0.7.6-dfsg-5
reassign -3 python-tidylib 0.3.2~dfsg-4
reassign -4 pyx 0.12.1-11
reassign -5 pyx3 0.15-1
reassign -6 sasview 4.2.1-1
reassign -7 sfepy 2018.1-4
reassign -8 smlnj 110.79-4
reassi
96
LOOSE CULRY ,BODY WAVE ,STRAIGHT ,CURLY ,LOOSE WAVE
WHICH YOUR END CLIENTS WANT MOSTLY
Available ON Stock
Color wig ,cusomized wig only need 3 wokirng days
Wana know which the end clients like or any further questions just feel free to
contact me .
m:
+8615018763458
w:
[1
package: xenomai-kernel-source
version: 2.6.4+dfsg-1
severity: serious
Hi,
It seems xenomai-kernel-source depends on kernel-package, which will not be in
buster, (see https://bugs.debian.org/925411).
Cheers,
Ivo
96
LOOSE CULRY ,BODY WAVE ,STRAIGHT ,CURLY ,LOOSE WAVE
WHICH YOUR END CLIENTS WANT MOSTLY
Available ON Stock
Color wig ,cusomized wig only need 3 wokirng days
Wana know which the end clients like or any further questions just feel free to
contact me .
m:
+8615018763458
w:
[1
96
LOOSE CULRY ,BODY WAVE ,STRAIGHT ,CURLY ,LOOSE WAVE
WHICH YOUR END CLIENTS WANT MOSTLY
Available ON Stock
Color wig ,cusomized wig only need 3 wokirng days
Wana know which the end clients like or any further questions just feel free to
contact me .
m:
+8615018763458
w:
[1
Your message dated Sun, 04 Nov 2018 06:05:08 +
with message-id
and subject line Bug#893870: Removed package(s) from unstable
has caused the Debian Bug report #790207,
regarding luakit: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.
This means that you claim that the
Package: bochs
Version: 2.6-5
Severity: important
Tags: sid buster
Control: block 895046 with -1
Hi,
bochs depends on vgabios which has been requested to be removed:
https://bugs.debian.org/895046
qemu, which also used vgabios in the past, has switched to seabios long
ago - perhaps that'
Processing control commands:
> block 895046 with -1
Bug #895046 [ftp.debian.org] RM: vgabios -- ROM; an old not-used-anymore package
895046 was not blocked by any bugs.
895046 was not blocking any bugs.
Added blocking bug(s) of 895046: 902221
--
895046: https://bugs.debian.org/cgi-bin/bugreport.
Your message dated Tue, 02 Jan 2018 22:24:13 +
with message-id
and subject line Bug#885966: Removed package(s) from unstable
has caused the Debian Bug report #822585,
regarding gvrng: depends on python-gtksourceview2 which is deprecated
to be marked as done.
This means that you claim that
Your message dated Tue, 02 Jan 2018 22:22:28 +
with message-id
and subject line Bug#885948: Removed package(s) from unstable
has caused the Debian Bug report #790586,
regarding gnome-btdownload: depends on python-gnome2 which is deprecated
to be marked as done.
This means that you claim that
Your message dated Tue, 02 Jan 2018 22:23:19 +
with message-id
and subject line Bug#885956: Removed package(s) from unstable
has caused the Debian Bug report #845960,
regarding x-tile: depends on python-gnome2 which deprecated
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 02 Jan 2018 22:21:39 +
with message-id
and subject line Bug#885913: Removed package(s) from unstable
has caused the Debian Bug report #309069,
regarding perlpanel: Perlpanel's gtk-config uses localized positioning
parameters which cannot be parsed
to be marked as
Your message dated Tue, 26 Dec 2017 15:56:16 +
with message-id
and subject line Bug#885033: Removed package(s) from unstable
has caused the Debian Bug report #790146,
regarding gdevilspie: depends on python-wnck which is deprecated
to be marked as done.
This means that you claim that the
Your message dated Fri, 22 Dec 2017 22:12:58 +
with message-id
and subject line Bug#884990: Removed package(s) from unstable
has caused the Debian Bug report #790590,
regarding hamster-applet: depends on python-gnome2 which is deprecated
to be marked as done.
This means that you claim that
Your message dated Fri, 22 Dec 2017 22:12:58 +
with message-id
and subject line Bug#884990: Removed package(s) from unstable
has caused the Debian Bug report #790147,
regarding hamster-applet: depends on python-wnck which is deprecated
to be marked as done.
This means that you claim that the
Your message dated Tue, 12 Dec 2017 13:43:00 +
with message-id
and subject line Bug#881583: Removed package(s) from unstable
has caused the Debian Bug report #790578,
regarding gdesklets: depends on python-gnome2 which is deprecated
to be marked as done.
This means that you claim that the
Your message dated Tue, 12 Dec 2017 13:43:00 +
with message-id
and subject line Bug#881583: Removed package(s) from unstable
has caused the Debian Bug report #786364,
regarding gdesklets: depends on pyorbit which is going to be removed
to be marked as done.
This means that you claim that the
Your message dated Mon, 11 Dec 2017 17:47:22 +
with message-id
and subject line Bug#879167: Removed package(s) from unstable
has caused the Debian Bug report #790220,
regarding webkit2pdf: depends on libwebkitgtk-1.0-0 which is deprecated
to be marked as done.
This means that you claim that
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
Processing control commands:
> severity 790573 serious
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2 which is deprecated
Ignoring request to change severity of Bug 790573 to the same value.
> tags 790573 = buster sid
Bug #790573 [src:aptoncd] aptoncd: depends on python-gnome2
1 - 100 of 239 matches
Mail list logo
