Bug#588076: marked as done (mercurial-buildpackage: unnecessarily Recommends pbuilder)
Your message dated Fri, 28 Jul 2023 16:36:32 + with message-id and subject line Bug#1026433: Removed package(s) from unstable has caused the Debian Bug report #588076, regarding mercurial-buildpackage: unnecessarily Recommends pbuilder 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 you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 588076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588076 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mercurial-buildpackage Version: 0.8.2 Hi Jens, Trying to install mercurial-buildpackage today, I noticed it pulled in cdebootstrap (via pbuilder). The package description says: mercurial-buildpackage: Build a Debian package from the Mercurial repository, either in-place or using pbuilder. which suggests that mercurial-buildpackage is perfectly useful without pbuilder (and that this is not an unusual case like using an X app without a local X installation). Do I understand correctly? I would suggest changing the Recommends to Suggests or changing the package description to explain it. Regards, Jonathan --- End Message --- --- Begin Message --- Version: 0.10.2+rm Dear submitter, as the package mercurial-buildpackage has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026433 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#688281: marked as done (mercurial-buildpackage: mercurial-importorig leaves files that have been removed in new upstream version)
Your message dated Fri, 28 Jul 2023 16:36:32 + with message-id and subject line Bug#1026433: Removed package(s) from unstable has caused the Debian Bug report #688281, regarding mercurial-buildpackage: mercurial-importorig leaves files that have been removed in new upstream version 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 you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 688281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mercurial-buildpackage Version: 0.10 Severity: important When using mercurial-importorig to import a new upstream package, mercurial-importorig retains (in the default branch) files that were in the previous upstream package but removed in the new upstream package. These extra files now represent extra changes to the new upstream package that are not accounted for by quilt patches (for packages that uses the quilt 3.0 format). The bug is due to how mercurial-importorig uses merge to combine default branch and the (updated) upstream branch. While the merge would properly update all files that do exist in the new upstream package, it does not remove files that are missing from the new upstream package. mercurial-importorig needs to use a more complicated algorithm to incorporate new upstream packages. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mercurial-buildpackage depends on: ii devscripts2.12.2 ii libc6 2.13-35 ii libneko0 1.8.1-6+b1 ii mercurial 2.2.2-1 ii neko 1.8.1-6+b1 ii pristine-tar 1.25 Versions of packages mercurial-buildpackage recommends: ii pbuilder 0.211 ii sudo 1.8.5p2-1 Versions of packages mercurial-buildpackage suggests: ii quilt 0.60-2 -- no debconf information --- End Message --- --- Begin Message --- Version: 0.10.2+rm Dear submitter, as the package mercurial-buildpackage has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026433 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#743730: marked as done (mercurial-buildpackage: s/exiting/existing/ in NAME section of mercurial-importdsc(1))
Your message dated Fri, 28 Jul 2023 16:36:32 + with message-id and subject line Bug#1026433: Removed package(s) from unstable has caused the Debian Bug report #743730, regarding mercurial-buildpackage: s/exiting/existing/ in NAME section of mercurial-importdsc(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 you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 743730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mercurial-buildpackage Version: 0.9 Severity: minor -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 There is a spelling error in the NAME section of the mercurial-importdsc(1) man page. s/exiting/existing/ Regards, - -Roberto - -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mercurial-buildpackage depends on: ii devscripts2.12.6+deb7u2 ii libc6 2.13-38+deb7u1 ii libneko0 1.8.1-6+b1 ii mercurial 2.2.2-3 ii neko 1.8.1-6+b1 ii pristine-tar 1.25+deb7u1 Versions of packages mercurial-buildpackage recommends: ii pbuilder 0.213 ii sudo-ldap [sudo] 1.8.5p2-1+nmu1 Versions of packages mercurial-buildpackage suggests: ii quilt 0.60-2 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTQDZUAAoJECzXeF7dp7IPVE0P/jZwduOq/6XgLRPyLtp/8J1K zsTMbEJGJpx7uod2Hf7PwhsWWSA5beJtS7I92XeXnhP++dpovnq7nZBmvKeRURSt h3HZxmDXxvr1p6aCTuaOkK2Hpjm2PX7Bc5fmo1pArVx3JKGjERc33ZMd1D7p7Xmj Nt86xppvul6Kui07nxM135h+AJe6RnqYo4cmyTeyIQNlTx5Jia6Ojj0wVt+PlrD1 vZp4yMETS4ktv/WX8QUWudexNIaMJg9go8xob0mj8Wz9H/2syecTIWVZUR4gOny4 lVkuv13WqvlzQ5rt3iuwznBLOPPyINu1axg7xwlpSKNWNUsz9m+Z+Ix+Iqm6I4uC Zc9RDnU5Zx/TYUTxLtNU3wVLTYFAKKP6JMyBECML/qnjSLqOrBxDgRWe4UtqbVII gzRFF+xoS/CJgQWV539XSv+otlMxxCat0+9j3HJPz6/RzRgmv6Vp9BIHiVVojYU8 Ct9+XRbbA5SLaap85slg2cQWGnsd7WhgECOWmaCk24hs67UwDYApJJZeheuVc8kp 6XbUQ7MCMKPmi2eLQHwBn031dEitNldGbALnM7C2JkIKomfz7kE8Ju0AF3kgVC2E TB/ZNbWJbxqrlEX+7dQ6fYtzO3t4HGDpRpbUDTKsY26pOfgM2U30KiJhh8IIE8De fR31+rfuzLvB/X+qQpye =6VI0 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Version: 0.10.2+rm Dear submitter, as the package mercurial-buildpackage has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026433 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1026433: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: mercurial-buildpackage | 0.10.2 | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x --- Reason --- RoQA; no users left -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1026...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1026433 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1026433: Removed package(s) from unstable
Version: 0.10.2+rm Dear submitter, as the package mercurial-buildpackage has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1026433 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1042107: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: grpc-proto | 0.0~git20230110.6956c0e-1 | source, all --- Reason --- RoQA; Orphaned; Useless -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1042107 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1042107: Removed package(s) from unstable
Version: 0.0~git20230110.6956c0e-1+rm Dear submitter, as the package grpc-proto has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1042107 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Bug#1042467: sysv-rc-conf: from bullseye want to uninstall many packages without dependency when trying upgrading it
Package: sysv-rc-conf Version: 0.99-7.1 Severity: normal Dear Maintainer, * What led up to the situation? After an upgrade from bullseye to bookworm, sysv-rc-conf was tagged as upgrading possible. * What exactly did you do (or not do) that was effective (or ineffective)? Using synaptic I tried to upgrade it but it ranted throwing a long list of packages it wanted to uninstall, such as colord, gparted, haruna, gufw, etc, however when I check those 4 they have been upgraded correctly and moreover do not show any dependency with sysv-rc-conf ! * What was the outcome of this action? I backed off. * What outcome did you expect instead? sysv-rc-conf to upgrade smoothly, not trying to remove at least 30 packages that don't know it. Ziziz vely stlange, limit weild. Cheers, Jean-Yves -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sysv-rc-conf depends on: ii libcurses-ui-perl 0.9609-1.1 ii sysv-rc3.06-4 sysv-rc-conf recommends no packages. sysv-rc-conf suggests no packages. -- no debconf information
Bug#1042476: gimp: Crash when applying color filters/effects and choosing "Convert pixels to built-in sRGB (slow)" - happens only sometimes.
Package: gimp (maybe gimp-dds as well, imo)
Version: 2.10.34-1
Severity: normal
X-Debbugs-Cc: aidsistgra...@gmail.com
Dear Maintainer, I have made some mediocre experiences actually often with GIMP
and certain functions of it...
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian
12.2.0-14' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs --enable-
languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-
major-version-only --program-suffix=-12 --program-prefix=x86_64-linux-gnu-
--enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-
included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-
verify --enable-plugin --enable-default-pie --with-system-zlib --enable-
libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto
--enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-
abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-
none=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-
amdhsa=/build/gcc-12-bTRWOB/gcc-12-12.2.0/debian/tmp-gcn/usr --enable-offload-
defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-
gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-14)
# Libraries #
using babl version 0.1.98 (compiled against version 0.1.98)
using GEGL version 0.4.42 (compiled against version 0.4.42)
using GLib version 2.74.6 (compiled against version 2.74.5)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.50.12 (compiled against version 1.50.12)
using Fontconfig version 2.14.1 (compiled against version 2.14.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Aborted
Stack trace:
```
# Stack traces obtained from PID 499583 - Thread 499583 #
[New LWP 499584]
[New LWP 499587]
[New LWP 499588]
[New LWP 499590]
[New LWP 499628]
[New LWP 499642]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__GI___libc_read (nbytes=256, buf=0x7fffd44d43f0, fd=20) at
../sysdeps/unix/sysv/linux/read.c:26
Id Target IdFrame
* 1Thread 0x7f9277a31300 (LWP 499583) "gimp-2.10" __GI___libc_read
(nbytes=256, buf=0x7fffd44d43f0, fd=20) at ../sysdeps/unix/sysv/linux/read.c:26
2Thread 0x7f9276f896c0 (LWP 499584) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7f9274fff6c0 (LWP 499587) "gmain" 0x7f927846203f in
__GI___poll (fds=0x55c4948a21c0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
4Thread 0x7f9275df46c0 (LWP 499588) "gdbus" 0x7f927846203f in
__GI___poll (fds=0x55c4948b61e0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
5Thread 0x7f92515166c0 (LWP 499590) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
6Thread 0x7f924b1ff6c0 (LWP 499628) "dashboard" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
7Thread 0x7f924a1fd6c0 (LWP 499642) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 7 (Thread 0x7f924a1fd6c0 (LWP 499642) "swap writer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f92786d13cf in g_cond_wait () at /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#2 0x7f9278c59a29 in () at /lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3 0x7f92786a6cfd in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7f92783ef044 in start_thread (arg=) at
./nptl/pthread_create.c:442
ret =
pd =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140266285553344,
987589741701938502, -1152, 11, 140736755220416, 140266277163008,
-968261152184812218, -968150916761600698}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#5 0x7f927846f5fc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
Thread 6 (Thread 0x7f924b1ff6c0 (LWP 499628) "dashboard"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7f92786d150c in g_cond_wait_until () at /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#2 0x55c
gtkam is marked for autoremoval from testing
gtkam 1.0-3 is marked for autoremoval from testing on 2023-08-31 It (build-)depends on packages with these RC bugs: 1041382: gegl: FTBFS with ffmpeg 6.0 https://bugs.debian.org/1041382 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
gimp-dds is marked for autoremoval from testing
gimp-dds 3.0.1-3 is marked for autoremoval from testing on 2023-08-31 It (build-)depends on packages with these RC bugs: 1041382: gegl: FTBFS with ffmpeg 6.0 https://bugs.debian.org/1041382 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
gluas is marked for autoremoval from testing
gluas 0.1.20-2 is marked for autoremoval from testing on 2023-08-31 It (build-)depends on packages with these RC bugs: 1041382: gegl: FTBFS with ffmpeg 6.0 https://bugs.debian.org/1041382 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
gimp-gap is marked for autoremoval from testing
gimp-gap 2.6.0+dfsg-7 is marked for autoremoval from testing on 2023-08-31 It (build-)depends on packages with these RC bugs: 1041382: gegl: FTBFS with ffmpeg 6.0 https://bugs.debian.org/1041382 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl
Processed: fixed 1032620 in doctest/2.4.11-1, closing 1032620
Processing commands for cont...@bugs.debian.org: > fixed 1032620 doctest/2.4.11-1 Bug #1032620 [src:doctest] doctest: new 2.4.10 out, fixes pernicious bugs Marked as fixed in versions doctest/2.4.11-1. > close 1032620 Bug #1032620 [src:doctest] doctest: new 2.4.10 out, fixes pernicious bugs Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1032620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
