Your message dated Sun, 05 Jan 2025 03:21:00 +
with message-id
and subject line Bug#1083037: Removed package(s) from unstable
has caused the Debian Bug report #500564,
regarding directfb: DirectFB fails to start ("Unsupported pixelformat: rgba
5/0, 5/5, 5/10, 0/0 (16bit)") (BGR
32785096&raw=0
./auto-str auto_home `head -1 conf-home` > auto_home.c
./chkshsgr || ( cat warn-shsgr; exit 1 )
Oops. Your getgroups() returned 0, and setgroups() failed; this means
that I can't reliably do my shsgr test. Please either ``make'' as root
or ``make'
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 07 Nov 2024 08:37:25 +0100
Source: aspell-hu
Architecture: source
Version: 0.99.4.2-0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By
aspell-hu_0.99.4.2-0-5_source.changes uploaded successfully to localhost
along with the files:
aspell-hu_0.99.4.2-0-5.dsc
aspell-hu_0.99.4.2-0-5.debian.tar.xz
aspell-hu_0.99.4.2-0-5_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Fri, 21 Jun 2024 12:44:00 +
with message-id
and subject line Bug#1073968: Removed package(s) from unstable
has caused the Debian Bug report #726608,
regarding sleepd suspends on AC even when running with --ac-unused=0
to be marked as done.
This means that you claim that
Your message dated Sun, 16 Jun 2024 00:59:30 +
with message-id
and subject line Bug#1073081: Removed package(s) from unstable
has caused the Debian Bug report #677825,
regarding Default configuration of auto_post=0 is confusing on upgrade
to be marked as done.
This means that you claim that
fldiff_1.1+0-7_source.changes uploaded successfully to localhost
along with the files:
fldiff_1.1+0-7.dsc
fldiff_1.1+0-7.debian.tar.xz
fldiff_1.1+0-7_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 05 May 2024 08:14:21 +0200
Source: fldiff
Architecture: source
Version: 1.1+0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Petter
Your message dated Tue, 02 Apr 2024 15:34:22 +
with message-id
and subject line Bug#1067391: fixed in bitlbee-facebook 1.2.2-3
has caused the Debian Bug report #1067391,
regarding bitlbee-facebook: redundant dependency on libglib2.0-0
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> severity 1067391 serious
Bug #1067391 [bitlbee-facebook] bitlbee-facebook: redundant dependency on
libglib2.0-0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you ne
severity 1067391 serious
thanks
After rebuilding for the time64 transition, bitlbee-facebook depends on
both libglib2.0-0 and libglib2.0-0t64. As a result it is uninstallable on
architectures affected by the time64 transition (armel, armhf and
several unofficial ports).
-size-param: (size=-5)
#0 0x5f90a3e1cf33 in __interceptor_memcpy
(/raptor/raptor-asan/utils/.libs/rapper+0x3cf33) (BuildId:
31b11a035fdbbfb23ddb7c1a5db60302956622be)
#1 0x7c902fa96e5a in raptor_uri_resolve_uri_reference
(/raptor/raptor/src/.libs/libraptor2.so.0+0x19e5a) (Bu
Package: libraptor2-0
X-Debbugs-Cc: ped...@gmail.com, Debian Security Team
Version: 2.0.15-4
Severity: grave
Justification: user security hole
Tags: patch upstream security
Hi,
Following on Hanno Bock's footsteps [1], I decided to fuzz libraptor2
[2][3] and after a few days found a c
libglib2.0-0.
Thanks for considering the patch.
-- System Information:
Debian Release: trixie/sid
APT prefers mantic-updates
APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500,
'mantic'), (100, 'mantic-backports')
Architecture: am
Your message dated Wed, 20 Mar 2024 20:37:34 +
with message-id
and subject line Bug#1067171: fixed in bleachbit 4.6.0-3
has caused the Debian Bug report #1067171,
regarding bleachbit: hard-coded dependency on libgtk-3-0 will become
uninstallable on armel/armhf
to be marked as done.
This
Processing control commands:
> block 1036884 by -1
Bug #1036884 [release.debian.org] transition: time64_t
1036884 was blocked by: 1067170 1065787 1065973 1067069 1055352 1065816 1066049
1066794 1055530 1062847
1036884 was not blocking any bugs.
Added blocking bug(s) of 1036884: 1067171
--
10368
Package: bleachbit
Version: 4.6.0-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1
bleachbit is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect
Your message dated Wed, 29 Nov 2023 17:19:04 +
with message-id
and subject line Bug#940987: fixed in apt-xapian-index 0.54
has caused the Debian Bug report #940987,
regarding rdetails fails: TypeError: sequence item 0: expected str instance,
bytes found
to be marked as done.
This means that
Your message dated Tue, 15 Aug 2023 14:35:03 +
with message-id
and subject line Bug#1043245: fixed in dbus-c++ 0.9.0-14
has caused the Debian Bug report #1043245,
regarding libdbus-c++-ecore-1-0/experimental: undeclared file conflict with
libdbus-c++-1-0v5/unsable
to be marked as done.
This
Your message dated Tue, 15 Aug 2023 14:35:03 +
with message-id
and subject line Bug#1043246: fixed in dbus-c++ 0.9.0-14
has caused the Debian Bug report #1043246,
regarding libdbus-c++-glib-1-0/experimental: undeclared file conflict with
libdbus-c++-1-0v5/unsable
to be marked as done.
This
Hello Helmut,
you are right. This has happened because with my upload to Debian Mentors
I was assuming the next release would be 0.9.0-12~exp1, but Bastian had
already uploaded the new release 0.9.0-12 and so had to pick a newer
release number for my changes. That means that the version numb
Package: libdbus-c++-glib-1-0
Version: 0.9.0-13
Severity: serious
Control: affects -1 + libdbus-c++-1-0v5
User: debian...@lists.debian.org
Usertags: fileconflict
Both libdbus-c++-glib-1-0/experimental and libdbus-c++-1-0v5/unstable
contain the files /usr/lib/x86_64-linux-gnu/libdbus-c++-glib-1.so
Processing control commands:
> affects -1 + libdbus-c++-1-0v5
Bug #1043246 [libdbus-c++-glib-1-0] libdbus-c++-glib-1-0/experimental:
undeclared file conflict with libdbus-c++-1-0v5/unsable
Added indication that 1043246 affects libdbus-c++-1-0v5
--
1043246: https://bugs.debian.org/cgi-
Processing control commands:
> affects -1 + libdbus-c++-1-0v5
Bug #1043245 [libdbus-c++-ecore-1-0] libdbus-c++-ecore-1-0/experimental:
undeclared file conflict with libdbus-c++-1-0v5/unsable
Added indication that 1043245 affects libdbus-c++-1-0v5
--
1043245: https://bugs.debian.org/cgi-
Package: libdbus-c++-ecore-1-0
Version: 0.9.0-13
Severity: serious
Control: affects -1 + libdbus-c++-1-0v5
User: debian...@lists.debian.org
Usertags: fileconflict
Both libdbus-c++-ecore-1-0/experimental and libdbus-c++-1-0v5/unstable
contain the files /usr/lib/x86_64-linux-gnu/libdbus-c++-ecore-1
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 15 Jul 2023 23:18:39 +0200
Source: aspell-it
Architecture: source
Version: 2.4-20070901-0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed
aspell-it_2.4-20070901-0-4_source.changes uploaded successfully to localhost
along with the files:
aspell-it_2.4-20070901-0-4.dsc
aspell-it_2.4-20070901-0-4.debian.tar.xz
aspell-it_2.4-20070901-0-4_source.buildinfo
Greetings,
Your Debian queue daemon (running on host
Your message dated Sat, 01 Jul 2023 18:05:05 +
with message-id
and subject line Bug#1039949: Removed package(s) from unstable
has caused the Debian Bug report #719412,
regarding pads: Setting daemon to 0 still runs PADS on boot
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> reassign 1034696 libargon2-1-udeb 0~20190702+dfsg-2
Bug #1034696 [src:argon2] libargon2-1-udeb: should build with threading support
Bug reassigned from package 'src:argon2' to 'libargon2-1-udeb'.
No longer marked as fou
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
Control: tags -1 d-i
Hi Bastian, Guilhem,
On 16-03-2023 13:44, Paul Gevers wrote:
cryptsetup will need to migrate to mitigate the time bomb.
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
Hi,
[@aurel32, glibc question at the bottom]
On 16-03-2023 11:57, Bastian Germann wrote:
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
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
nd the help of colleagues, but it's libcryptsetup12-udeb
> that has:
> Depends: libargon2-1-udeb (>= 0~20190702)
Oh I see, thanks for the info and sorry for not doing the homework!
That might also explain why src:cryptsetup 2:2.6.1-2 was blocked from
entering testing in time. That'
on2-1-udeb (>= 0~20190702)
While writing this up and discussing with others, I realized that the error
is coming from one of glibc's binaries. It has been stated that the issue
started with with a change there, but is that change done on purpose, or a
bug? I.e. is one of glibc&#x
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 the archive,
> > > but also for downstreams and other use
;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 the archive, but also for downst
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 on
ewer libc; a binNMU would therefore have caused the same regression,
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 b
aused by building with a
newer libc; a binNMU would therefore have caused the same regression, it
was just unfortunate timing to dust up the package and upload just
before the hard freeze.
> If packages are waiting for argon2 then I would prefer an unblock of
> both argon2 and cryptsetup at the
sed by the recent libargon2 upload
> indeed, but AFAICT not by anything particular in the upload.
I am sorry for having caused that issue, Daniel. Thanks for investigating,
Guilhem.
The changelog entry is correct because it fixes a formerly made change.
0~20171227-0.1 intended to compile
deed, but AFAICT not by anything particular in the upload.
I am sorry for having caused that issue, Daniel. Thanks for investigating,
Guilhem.
The changelog entry is correct because it fixes a formerly made change.
0~20171227-0.1 intended to compile only udeb without threads:
"Build udeb withou
Your message dated Sun, 12 Mar 2023 16:20:24 +
with message-id
and subject line Bug#1028355: fixed in libvisual 0.4.1-1
has caused the Debian Bug report #1028355,
regarding libvisual-0.4-0: Please update to libvisual 0.4.1
to be marked as done.
This means that you claim that the problem has
Package: libvisual-0.4-0
Version: 0.4.0-19
Severity: normal
X-Debbugs-Cc: sebast...@pipping.org
Hi!
All existing Debian patches against libvisual 0.4.0 have been reviewed and
integrated upstream [1] into new releases 0.4.1, either unmodified or taken
further. I believe there is a good chance
Your message dated Tue, 20 Dec 2022 16:05:26 +
with message-id
and subject line Bug#1026459: Removed package(s) from unstable
has caused the Debian Bug report #966893,
regarding kvmtool: FTBFS: string_fortified.h:34:10: error: writing 1 byte into
a region of size 0 [-Werror=stringop-overflow
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 13 Oct 2022 14:25:49 +0100
Source: aspell-is
Architecture: source
Version: 0.51.1-0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Jelmer Vernooij
Changes:
aspell-is (0.51.1-0
aspell-is_0.51.1-0-2_source.changes uploaded successfully to localhost
along with the files:
aspell-is_0.51.1-0-2.dsc
aspell-is_0.51.1-0-2.debian.tar.xz
aspell-is_0.51.1-0-2_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 09 Jun 2022 10:41:55 +0200
Source: monero
Architecture: source
Version: 0.17.3.0+~0+20200826-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Jonas Smedegaard
Changes:
monero
monero_0.17.3.0+~0+20200826-2_source.changes uploaded successfully to localhost
along with the files:
monero_0.17.3.0+~0+20200826-2.dsc
monero_0.17.3.0+~0+20200826-2.debian.tar.xz
monero_0.17.3.0+~0+20200826-2_source.buildinfo
Greetings,
Your Debian queue daemon (running on host
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 20 May 2022 19:25:25 +0200
Source: aspell-hu
Architecture: source
Version: 0.99.4.2-0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Holger Levsen
Changes:
aspell-hu
aspell-hu_0.99.4.2-0-4.1_source.changes uploaded successfully to localhost
along with the files:
aspell-hu_0.99.4.2-0-4.1.dsc
aspell-hu_0.99.4.2-0-4.1.debian.tar.xz
aspell-hu_0.99.4.2-0-4.1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing control commands:
> severity -1 serious
Bug #993203 [gnome-shell-mailnag] gnome-shell-mailnag: does not declare
compatibility with GNOME Shell 40
Severity set to 'serious' from 'important'
--
993203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993203
Debian Bug Tracking System
Control: severity -1 serious
On Sat, 28 Aug 2021 at 13:52:40 +0100, Simon McVittie wrote:
> as usual various third-party extensions will need either updating, or
> temporarily removing from testing
I've now uploaded gnome-shell 40 to unstable, so gnome-shell extensions
incompatible with that vers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 01 Mar 2021 12:43:58 +0100
Source: aspell-is
Architecture: source
Version: 0.51.1-0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Andreas Beckmann
Closes: 966163
Changes
aspell-is_0.51.1-0-1_source.changes uploaded successfully to localhost
along with the files:
aspell-is_0.51.1-0-1.dsc
aspell-is_0.51.1-0.orig.tar.bz2
aspell-is_0.51.1-0-1.debian.tar.xz
aspell-is_0.51.1-0-1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host
Your message dated Wed, 27 Jan 2021 15:38:10 +0100
with message-id <20210127143810.gw287...@zedat.fu-berlin.de>
and subject line Re: Bug#383377: ignore Xresources and window at +0+0
has caused the Debian Bug report #383377,
regarding xpdf: [missing feature] ignore Xresources and window at +
Your message dated Wed, 27 Jan 2021 15:38:10 +0100
with message-id <20210127143810.gw287...@zedat.fu-berlin.de>
and subject line Re: Bug#383377: ignore Xresources and window at +0+0
has caused the Debian Bug report #383377,
regarding xpdf: [missing feature] ignore Xresources and window at +
> In fact, I'd say that xpdf-reader always opens with top-left corner at
> +0+0 and thus completely ignores any window hints from the window
> manager.
This bug seems to have been fixed -- I've tested it with Debian xpdf
3.04-4, upstream xpdf 3.04 and xpopple, and -geometry n
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 01 Jan 2021 15:02:25 +0100
Source: aspell-it
Architecture: source
Version: 2.4-20070901-0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Holger Levsen
Changes:
aspell-it
aspell-it_2.4-20070901-0-3.1_source.changes uploaded successfully to localhost
along with the files:
aspell-it_2.4-20070901-0-3.1.dsc
aspell-it_2.4-20070901-0-3.1.debian.tar.xz
aspell-it_2.4-20070901-0-3.1_source.buildinfo
Greetings,
Your Debian queue daemon (running on host
Package: dblatex
Version: 0.3.11py3-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: jeromearbezgin...@gmail.com
Dear Maintainer,
3 attached files minimal configuration to reproduce the issue
The xsl file includes the following line:
When I invoke the command:
dblatex -
Your message dated Fri, 13 Mar 2020 22:37:55 +
with message-id
and subject line Bug#953738: Removed package(s) from unstable
has caused the Debian Bug report #59828,
regarding plan: exit(0);doc vs. plan.dir; error on 29. March
to be marked as done.
This means that you claim that the problem
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 22 Jan 2020 16:21:48 -0500
Source: zeitgeist
Architecture: source
Version: 1.0.2+py3-0~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Boyuan Yang
Changes:
zeitgeist
zeitgeist_1.0.2+py3-0~exp1_source.changes uploaded successfully to localhost
along with the files:
zeitgeist_1.0.2+py3-0~exp1.dsc
zeitgeist_1.0.2+py3.orig.tar.xz
zeitgeist_1.0.2+py3-0~exp1.debian.tar.xz
zeitgeist_1.0.2+py3-0~exp1_amd64.buildinfo
Greetings,
Your Debian queue
Your message dated Sun, 17 Nov 2019 04:35:59 +
with message-id
and subject line Bug#555952: fixed in sysfsutils 2.1.0+repack-6
has caused the Debian Bug report #555952,
regarding sysfsutils: does not remove stop symlinks in runlevels 0, 1, 6 on
upgrades
to be marked as done.
This means that
gtk2 bindings (libgtk-vnc-1.0-0).
xenwatch is the only package in Debian to depend on the gtk2 library.
I've never used xenwatch, but I believe there are alternative
maintained apps in Debian like virt-manager, virt-viewer, and
gnome-boxes.
Orphan bug: https://bugs.debian.org/54
Your message dated Mon, 23 Sep 2019 21:15:28 +
with message-id
and subject line Bug#926486: Removed package(s) from unstable
has caused the Debian Bug report #296441,
regarding zapping: set line sound level to 0 when changing channel
to be marked as done.
This means that you claim that the
", line 852, in perform
return f(self.args)
File "/usr/bin/axi-cache", line 718, in do_rdetails
print(name, tag, " ".join(deps))
TypeError: sequence item 0: expected str instance, bytes found
It seems the query is returning bytes instead of strings. Converting
with ut
Your message dated Thu, 22 Aug 2019 01:46:16 +
with message-id
and subject line Bug#935228: Removed package(s) from unstable
has caused the Debian Bug report #286466,
regarding kmldonkey: kmldonkey sets max_hard_upload_rate from time to time to
value: 0
to be marked as done.
This means that
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 21 Jul 2019 20:22:49 -0300
Source: fldiff
Architecture: source
Version: 1.1+0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Diego Sarzi
Changes:
fldiff (1.1+0-6) unstable
fldiff_1.1+0-6_source.changes uploaded successfully to localhost
along with the files:
fldiff_1.1+0-6.dsc
fldiff_1.1+0-6.debian.tar.xz
fldiff_1.1+0-6_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
ng symbols
> found)...done.
> [New LWP 9037]
> [New LWP 9011]
> [New LWP 9012]
> [New LWP 9013]
> [New LWP 9016]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Core was generated by `/usr/
Processing control commands:
> reassign -1 libkrb5-3 1.16.2-1
Bug #918088 [autofs-ldap] autofs-ldap: automount dies with SIGABRT after
libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)"
Bug reassigned from package 'autofs-ldap' to 'libkrb5-3'.
d_db.so.1".
Core was generated by `/usr/sbin/automount -d -f'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f
nd,dc=de".
parse_server_string: lookup(ldap): server "(default)", base dn
"automountmapname=auto.home,cn=badphish,cn=automount,dc=badphish,dc=ypbind,dc=de"
parse_ldap_config: lookup(ldap): ldap authentication configured with the
following options:
parse_ldap_config: lookup(ldap): use_tls: 1,
Your message dated Sun, 9 Dec 2018 20:08:02 +0100
with message-id <295a3971-6655-315d-b593-410c64d74...@debian.org>
and subject line Re: libsoundio1: Missing hard dependency on libjack-jackd2-0
has caused the Debian Bug report #835590,
regarding libsoundio1: Missing hard dependency on l
, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=16
ioc1: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=16
mpt-status does not work. See:
agenzia-480:~# mpt-status -u0 -p
Checking for SCSI ID:0
Checking for SCSI ID:1
Checking for SCSI ID:2
Checking for SCSI ID:3
Checking for SCSI ID:4
Checking
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
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 04 May 2018 19:17:31 +0200
Source: aspell-it
Binary: aspell-it
Architecture: source all
Version: 2.4-20070901-0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Agustin Martin
aspell-it_2.4-20070901-0-3_amd64.changes uploaded successfully to localhost
along with the files:
aspell-it_2.4-20070901-0-3.dsc
aspell-it_2.4-20070901-0-3.debian.tar.xz
aspell-it_2.4-20070901-0-3_all.deb
aspell-it_2.4-20070901-0-3_amd64.buildinfo
Greetings,
Your Debian queue
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
Your message dated Sun, 06 Aug 2017 04:49:35 +
with message-id
and subject line Bug#869743: Removed package(s) from unstable
has caused the Debian Bug report #486466,
regarding mrxvt: Clones settings for profiles > 9 from profile 0.
to be marked as done.
This means that you claim that
Your message dated Thu, 03 Aug 2017 17:37:05 +
with message-id
and subject line Bug#868984: Removed package(s) from unstable
has caused the Debian Bug report #866658,
regarding xombrero: depends on libwebkitgtk-3.0-0 which is deprecated
to be marked as done.
This means that you claim that
Fermented
Sent from my iPhone
Your message dated Tue, 1 Aug 2017 06:55:39 +0200
with message-id <20170801045538.5utyvigpkt4ke...@alf.mars>
and subject line please use liborbit2-dbgsym
has caused the Debian Bug report #495159,
regarding /usr/lib/libORBit-2.so.0: Requesting orbit-dbg package
to be marked as done.
This
Your message dated Sun, 16 Jul 2017 17:48:50 +
with message-id
and subject line Bug#866628: fixed in apvlv 0.1.5+dfsg-2
has caused the Debian Bug report #866628,
regarding apvlv: depends on libwebkitgtk-3.0-0 which is deprecated
to be marked as done.
This means that you claim that the
Your message dated Fri, 07 Jul 2017 15:50:00 +
with message-id
and subject line Bug#866640: fixed in gtkpod 2.1.5-6
has caused the Debian Bug report #866640,
regarding gtkpod: depends on libwebkitgtk-3.0-0 which is deprecated
to be marked as done.
This means that you claim that the problem
Source: xombrero
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1
Hi,
xombrero depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
xombrero
Processing commands for cont...@bugs.debian.org:
> reassign 866630 balsa
Bug #866630 [apvlv] balsa: depends on libwebkitgtk-1.0-0 which is deprecated
Bug reassigned from package 'apvlv' to 'balsa'.
Ignoring request to alter found versions of bug #866630 to the same values
Package: apvlv
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-1.0-0 webkit1
Hi,
balsa depends on libwebkitgtk-1.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). balsa should
be
Package: apvlv
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1
Hi,
apvlv depends on libwebkitgtk-3.0-0, which is deprecated in favor of
libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk). apvlv should
be
Igor Starkov:
> mount: mounting aufs on /root/ failed: No such device
> mount aufs on /root/ failed with option -o
> noatime,noxino,dirs=/live/overlay/=rw://filesystem.squashfs/=rr+wh
Maybe your kernel lacks aufs support. Look into using the aufs-dkms package.
> Igor Starkov:
>>[2.974235] FAT-fs (sda1): IO charset ascii not found
>>mount: mounting /dev/sda1 on /live/medium failed: Invalid argument
>> skipped similar lines
>>[ 63.554664] FAT-fs (sda1): IO charset ascii not found
>>mount: mounting /dev/sda1 on /live/m
Igor Starkov:
>[2.974235] FAT-fs (sda1): IO charset ascii not found
>mount: mounting /dev/sda1 on /live/medium failed: Invalid argument
> skipped similar lines
>[ 63.554664] FAT-fs (sda1): IO charset ascii not found
>mount: mounting /dev/sda1 on /live/medium f
Package: live-build
Version: 4.0.3-1
Severity: important
Dear Maintainer,
* I'm trying to build live Jessie image with backported kernel.
Kernel version: linux-image-4.7.0-0.bpo.1-amd64
* Steps to reproduce:
lb config noauto \
--apt-indices false \
--apt-s
Your message dated Wed, 21 Sep 2016 02:39:29 +
with message-id
and subject line Bug#628848: Removed package(s) from unstable
has caused the Debian Bug report #359896,
regarding libpam-unix2: Authentication always fail if uidNumber=0 and the user
is in LDAP
to be marked as done.
This means
aspell-hu_0.99.4.2-0-4_source.changes uploaded successfully to localhost
along with the files:
aspell-hu_0.99.4.2-0-4.dsc
aspell-hu_0.99.4.2-0-4.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
1 - 100 of 209 matches
Mail list logo
