Hi!
On Fri, 2021-11-12 at 18:50:36 +0100, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> Control: forwarded -1
> https://release.debian.org/transitions/html/auto-liburing.html
>
> On 2021-11-12 04:18:57 +0100, Guillem Jover wrote:
> > Package: release.debian.org
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hi!
The liburing source bumped its SONAME from liburing1 to liburing2, but
it should be API compatible. The new upstream has been uploaded to
experimental, and I did a rebuild of all
Control: tag -1 wontfix
On Tue, 2018-03-13 at 13:47:10 -0400, Konstantin Ryabitsev wrote:
> On 03/13/18 05:33, Uwe Kleine-König wrote:
> >>> But it also has an impact on security: As long as the signature isn't
> >>> verified I have to consider the .tar.xz "untrusted" and the less tools I
> >>>
Hi!
On Tue, 2020-08-04 at 20:56:48 +0200, Guillem Jover wrote:
> Control: tags -1 patch
> On Tue, 2020-08-04 at 20:09:05 +0200, Sven Joachim wrote:
> > Package: aptitude
> > Version: 0.8.13-1+b1
> > Severity: normal
> > X-Debbugs-Cc: Sven Joachim , Guillem J
Hi!
On Thu, 2021-10-28 at 15:02:19 -0700, Leo Puvilland wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Leo Puvilland
>
> * Package name: makedeb
> Version : 7.1.2+bugfix1
> Upstream Author : Hunter Wittenborn
> * URL : https://makedeb.hunterwittenborn.com
> *
Hi!
On Thu, 2021-10-21 at 13:42:58 +0100, Ian Jackson wrote:
> Package: dpkg
> Version: 1.16.1
> Control: found -1 1.20.9
> I looked at Policy to double-check my recollection:
>
>
Hi!
On Tue, 2021-10-05 at 20:49:53 +0200, Svante Signell wrote:
> Index: p11-kit-0.24.0-2.3/common/unix-peer.c
> ===
> --- p11-kit-0.24.0-2.3.orig/common/unix-peer.c
> +++ p11-kit-0.24.0-2.3/common/unix-peer.c
> @@ -36,7 +36,6 @@
>
ht solution, but attached patch with the
> above.
See above.
I think the attached patch is the correct fix. I think I can push to
the repo, so if no one has any concerns I might do that during the
weekend.
Thanks,
Guillem
From 1dcd625cd3282e66782cbe13e3fada43dd59e139 Mon Sep 17 00:00:00 2001
From: Guillem
Hi!
On Thu, 2021-09-30 at 16:21:21 +0200, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.20.6
> Severity: grave
> Justification: breaks unrelated packages by removing their conffiles
>
> attached is a small package demonstrating the misbehavior of
> remove-on-upgrade which may delete
Package: lintian
Version: 2.77.0
Severity: serious
Sigh,
So the problematic --fail-on default change never got actually reverted
as the patch applied in commit 3758bfafd5dd742c327f2312dac8e3a71b1f036e
omitted the relevant part that would make it work. :(
None of the previous arguments against
Hi!
On Wed, 2021-09-29 at 21:57:29 +0200, MichaIng wrote:
> Package: dpkg
> Version: 1.20.9
> I recognised just recently that dpkg is not able to gracefully replace files
> on FAT partitions, e.g. when reinstalling or upgrading a package. It seems
> to try creating a file link as backup, while
Control: severity -1 wishlist
Hi!
On Wed, 2020-07-01 at 11:35:14 +0200, Christian Ehrhardt wrote:
> Package: liburing
> Version: 0.6-3
> But in regard to build time and autopkgtests I found that these always
> failed.
> I've taken a look at that as I'd love to get some actual test coverage onto
Control: reassign -1 glx-diversions 1.2.0
On Tue, 2021-09-14 at 11:19:43 +0200, Sébastien Villemot wrote:
> Control: reassign -1 dpkg 1.20.9
> Le dimanche 12 septembre 2021 à 15:24 +, Witold Baryluk a écrit :
> > Package: octave
> > Version: 6.2.0-1
> > Followup-For: Bug #993338
> >
Hi!
On Sat, 2021-09-11 at 00:17:07 +0200, Matteo F. Vescovi wrote:
> On 2021-09-10 at 14:46 (-07), Dima Kogan wrote:
> > Also, do we want to ship the binaries? Any particular reason to put them
> > in /usr/lib/libraw? That's an odd place for executables.
>
> Good question. When I inherited the
Control: tag -1 moreinfo
Hi!
On Mon, 2021-08-23 at 17:59:48 +0300, Raul Tambre wrote:
> Package: dpkg-dev
> Version: 1.20.9
> Severity: normal
> GNU ld generates a nullptr absolute symbol for each version script tag.
> test.sym:
>
> LIBTEST_1
> {
> };
>
> clang -shared /dev/null
Control: severity -1 minor
Control: retitle -1 dpkg-gensymbols: Add error for invalid symver entries
On Thu, 2021-09-09 at 14:34:21 +0200, Matthias Klose wrote:
> Package: src:dpkg
> Version: 1.20.9
> Severity: important
> seen with the gcc-11 builds on alpha:
>
>
Package: pacemaker
Version: 2.0.5-2
Severity: important
Tags: patch upstream fixed-upstream
Forwarded:
https://github.com/ClusterLabs/pacemaker/commit/825557ebe55038c2fdb87ed26b91a04173a496bd
Hi!
This release up to 2.1 spams the log file with:
,---
Set r/w permissions for uid=105, gid=110
On Mon, 2020-08-24 at 09:42:23 +0300, Adrian Bunk wrote:
> On Sun, Jan 26, 2020 at 02:51:05AM +, Debian Bug Tracking System wrote:
> >...
> > inetutils (2:1.9.4-11) unstable; urgency=medium
> > .
> >* Add patches from upstream:
> > - telnet: Validate supplied environment variables.
Hi!
On Tue, 2020-04-14 at 21:56:41 +0530, Pirate Praveen wrote:
> Package: src:inetutils
> Severity: wishlist
> Version: 2:1.9.4-11
> libnet-dev is not avilable on hurd-i386 and kfreebsd-* architectures
> https://buildd.debian.org/status/package.php?p=dnprogs=sid
>
> So it'd be nice if commands
Hi!
On Wed, 2020-12-02 at 07:16:52 +0300, Anatoli Babenia wrote:
> Package: dpkg-dev
> Version: 1.19.7
> Severity: normal
> File: /usr/bin/dpkg-source
> It would help greatly if `dpkg-source` reported native or non-native
> package type.
>
> -dpkg-source: info: using source format '1.0'
>
Hi!
On Mon, 2021-03-08 at 22:35:49 -0800, Ross Vandegrift wrote:
> Package: dpkg
> Version: 1.20.7.1
> Severity: wishlist
> X-Debbugs-Cc: rvandegr...@debian.org
>
> dpkg-divert is too sensitive to the order of the command line parameters.
> Since I only use it rarely, I almost always run into:
>
Control: severity -1 minor
Control: retitle -1 dpkg: Man page not clear on re-inclusion behavior
Hi!
On Mon, 2017-08-07 at 15:26:36 -0500, Adam Heath wrote:
> package: dpkg
> version: 1.17.27
>
> In the manpage for dpkg, there is an example for path-exclude/path-include:
>
> ==
>
Hi!
[ Sorry I thought I had replied to this, but it seems I only did on my
head… :/ ]
On Tue, 2017-08-08 at 09:20:32 -0400, Vagrant Cascadian wrote:
> Package: dpkg-dev
> Severity: wishlist
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: toolchain
> X-Debbugs-Cc:
Hi!
On Sat, 2021-08-28 at 12:19:55 +0800, beks...@westnet.com.au wrote:
> Package: dpkg
> Install to Raspberry Pi 4 (4G RAM)
>
> Methodhttps://www.raspberrypi.org/forums/viewtopic.php?f=50=282839=3c56d720738b6f6768874193298c3c38
> install ran 26 August 2021 using images downloaded that day.
>
Control: user debian-d...@lists.debian.org
Control: usertags -1 dpkg-mismatch-source-vs-version-format
Hi!
On Wed, 2012-10-24 at 21:06:49 +0200, Matthias Klose wrote:
> tags 684431 + wontfix
> severity 684431 minor
> thanks
> these packages, and others like the gcc-4.x packages are split into
Source: python-defaults
Source-Version: 2.7.18-3
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing (to unexperienced and experience packagers
Source: user-mode-linux-doc
Source-Version: 20060501-3.1
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both
Source: gdb-avr
Source-Version: 7.7-4.1
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source and
Source: netselect
Source-Version: 0.3.ds1-29
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source
Source: php-ps
Source-Version: 1.4.1+pecl+nophp8+1.3.7-2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both
On Mon, 2021-08-23 at 19:22:54 -0700, Vagrant Cascadian wrote:
> Ok, a slightly more complicated workflow pseudocode:
>
> if DEB_BUILD_PATH && fixfilepath
> then
> -spec=/usr/share/dpkg/fixfilepath.spec ...
> else if fixfilepath
> -ffile-prefix-map= build_path ...
> fi
While in theory
On Mon, 2021-08-23 at 17:07:13 -0700, Vagrant Cascadian wrote:
> On 2021-08-23, Guillem Jover wrote:
> > On Fri, 2021-03-19 at 11:32:52 -0700, Vagrant Cascadian wrote:
> >> Note that it is only a partial patch; it doesn't export DEB_BUILD_PATH
> >> in dpkg-buildpackage a
Control: tag -1 moreinfo unreproducible
Hi!
On Wed, 2021-07-07 at 19:00:34 +0200, Christoph Anton Mitterer wrote:
> Package: dpkg
> Severity: normal
> I've seen the following several times now when upgrading from stretch to
> buster
> via aptitude:
>
> Setting up libgail-common:amd64
Hi!
On Fri, 2021-03-19 at 11:32:52 -0700, Vagrant Cascadian wrote:
> Package: dpkg
> Severity: normal
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: buildpath
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
> While the reproducible=+fixfilepath and
Hi!
On Mon, 2020-12-21 at 23:02:29 -0500, John Scott wrote:
> Source: dpkg
> Severity: wishlist
> Tags: upstream
> Just to see what trickery I could get away with, I tried cross building dpkg
> with MinGW. It fails due to lchown being missing, but it seems like this is
> one of the only
Package: libtinyxml2-9
Version: 9.0.0+dfsg-2
Severity: serious
Hi!
This package contains bogus Provides/Conflicts against libtinyxml2-8
from when the package was named libtinyxml2-8a. These need to be
removed as they are leftovers, incorrect (as they might make package
depending on libtinyxml2-8
Hi!
On Thu, 2021-08-19 at 16:50:48 -0400, Boyuan Yang wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Boyuan Yang
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: which-gnu
> Version : 2.21
> Upstream Author : Carlo Wood
> * URL :
On Tue, 2021-08-10 at 00:37:51 -0500, Samuel Johnston wrote:
> The Linux kernel is now supplying modules compressed with zstd. Version
> updates for 5.12 and 5.13 are unable to be installed anymore on Debian due
> to this issue being unresolved.
I'm not sure how that is related to this report?
to the "deprecation" entry, but repetition is not ideal
and I can see push back on that too, so I'd rather have it listed
just once than not at all.
Thanks,
Guillem
From 134021b9dff9ad4e52a7446ce57dbfc0339b4754 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Wed, 11 Aug 2021 21:24:59 +02
Hi!
On Mon, 2011-05-23 at 09:44:04 +0200, Martin Pitt wrote:
> Package: edac-utils
> Version: 0.16-1
> User: mp...@debian.org
> Usertags: libsysfs-deprecation
> Some years ago libsysfs (source package: sysfsutils) was written as an
> abstraction layer for accessing /sys/. However, this turned
Hi!
On Mon, 2011-05-23 at 09:44:21 +0200, Martin Pitt wrote:
> Package: cpufreqd
> Version: 2.4.2-1
> User: mp...@debian.org
> Usertags: libsysfs-deprecation
> Some years ago libsysfs (source package: sysfsutils) was written as an
> abstraction layer for accessing /sys/. However, this turned out
Hi!
On Mon, 2011-05-23 at 09:43:23 +0200, Martin Pitt wrote:
> Package: openhpi
> Version: 2.14.1-1
> User: mp...@debian.org
> Usertags: libsysfs-deprecation
> Some years ago libsysfs (source package: sysfsutils) was written as an
> abstraction layer for accessing /sys/. However, this turned out
Hi!
On Sun, 2017-04-09 at 10:17:41 +0200, Philipp Kern wrote:
> On 02/24/2017 11:05 PM, Michael Biebl wrote:
> > Some years ago libsysfs (source package: sysfsutils) was written as an
> > abstraction layer for accessing /sys/. However, this turned out to be
> > a historical error and evolutionary
Source: mariadb-10.5
Source-Version: 1:10.5.10-2
Severity: serious
Forwarded: https://jira.mariadb.org/browse/MDEV-20821
Control: fixed -1 1:10.5.11-1~exp1
Hi!
When replication is enabled with the slave running in parallel mode,
the daemon completely hangs and will not terminate, which means
dc50d6cca9a69922f75f98fe73d95bb2f1067cfa Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Tue, 20 Jul 2021 20:40:54 +0200
Subject: [PATCH] Use an epsilon when doing the reboot boot timestamp
comparisons
At least on Linux, the current method to retrieve the boot timestamp is
racy, as we first
Hi!
On Fri, 2021-07-16 at 15:23:01 -0400, Zack Weinberg wrote:
> Package: dpkg
> Version: 1.20.9
> Severity: normal
> File: /usr/sbin/dpkg-fsys-usrunmess
> X-Debbugs-Cc: za...@panix.com
> I tried to run dpkg-fsys-usrunmess from systemd’s emergency mode,
> thinking that this would be safer, since
Source: libdata-messagepack-perl
Source-Version: 1.01-1
Severity: normal
Hi!
This package started setting Rules-Requires-Root explicitly to
binary-targets, but it seems unnecessary, as the source does not seem
to require root to build. The actual problem is that for some reason
the XS modules
Hi!
On Tue, 2021-06-29 at 08:01:49 +0200, Helmut Grohne wrote:
> Package: debianutils
> Version: 4.11.2
> Severity: wishlist
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> We've had a discussion on the expectations on /etc/shells on
> d-devel@l.d.o recently. You can find the
Control: reassign -1 debhelper
Hi!
This is not a dpkg issue, but it is debhelper related, reassigning and
leaving context.
On Fri, 2021-07-09 at 08:52:18 +, Dennis Bijwaard wrote:
> Package: dpkg-dev
> Version: 1.19.7
> Severity: normal
>
> Dear all,
>
> When I use dpkg-buildpackage -us
On Wed, 2021-06-23 at 01:04:58 +0200, Christoph Anton Mitterer wrote:
> Package: fuse3
> Version: 3.10.3-2
> Severity: normal
> X-Debbugs-Cc: debian-d...@lists.debian.org
> I've noted that /etc/fuse.conf was missing from all my servers (and
> I'm pretty sure I haven't deleted it).
>
>
On Wed, 2021-06-23 at 09:11:55 +0200, Thomas Lange wrote:
> >>>>> On Wed, 23 Jun 2021 01:59:43 +0200, Guillem Jover
> >>>>> said:
> > * bin/install_packages
> >The function mkpackagelist() checks for the presence of the available
Source: piuparts
Source-Version: 1.1.3
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-db-access-blocker dpkg-db-access-ctrl
Hi!
The piuparts package contains various scripts directly accessing the
internal dpkg database, instead of using publicly supported
interfaces. I
Source: fai
Source-Version: 5.10.3
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-db-access-meta dpkg-db-access-inert
Hi!
This package contains multiple scripts that access the internal dpkg
database directly, instead of using publicly supported interfaces:
*
Source: crowdsec
Source-Version: 1.0.9-2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-db-access-ctrl
Hi!
This package contains the «cscli» program, which directly accesses
the dpkg internal database, which seems gratuitous.
The postinst is overloaded to act as some kind
On Thu, 2021-06-17 at 10:31:52 +0200, Bill Allombert wrote:
> Sorry about not following here but then the freeze was coming and I
> stopped working on this. Thanks for bringing this up now that the
> release is close.
Sure, no problem!
> So the main point is: is it a stable interface for which
Hi!
[ Sorry, it seems I missed replying to this. ]
On Sat, 2019-02-02 at 10:59:05 +0100, A Mennucc1 wrote:
> I see your point;
>
> but (as the name " dpkg_L_faster" suggests), using the dpkg commands to
> obtain meta-information is quite slow; so I will have to think about it
Ok, the dpkg_L
On Sat, 2020-12-12 at 15:33:47 +0100, Bill Allombert wrote:
> On Thu, Nov 28, 2019 at 08:55:00PM +, Niels Thykier wrote:
> > While it would take a bit of restructuring / refactoring, I think it
> > would be possible to use a single dpkg-query for everything and still be
> > able to process the
On Mon, 2021-06-14 at 08:24:38 +0200, Marc Haber wrote:
> Package: dpkg-dev
> Version: 1.20.9
> Severity: minor
> File: /usr/bin/dpkg-buildpackage
> this occurred to me while building a source-only upload:
>
> | dpkg-source: warning: upstream signing key but no upstream tarball signature
> |
clearly from the ARCv2 arch, following the existing pattern in
MIPS r6. Otherwise placing the bitness after the ISA version makes
for an even more confusing name.
- This can be proposed for addition once the upstream toolchain has
support for it, but given that the overall a
Control: tags -1 unreproducible
On Wed, 2021-05-05 at 17:27:58 +0200, Juergen Richtsfeld wrote:
> Package: prometheus-node-exporter
> Version: 1.1.2+ds-1+b1
> Severity: normal
> X-Debbugs-Cc: juergen.richtsf...@gmx.at
> I tried to get disk (filesystem) i/o metrics like
>
Hi!
On Mon, 2021-05-24 at 20:08:57 -0400, James Valleroy wrote:
> Package: wnpp
> Severity: wishlist
> Owner: James Valleroy
> X-Debbugs-Cc: debian-de...@lists.debian.org, jvalle...@mailbox.org
>
> * Package name: object-cloner
> Version : 0.2
> Upstream Author : Kamran Zafar
>
Hi!
On Tue, 2021-05-18 at 09:07:17 +0900, YOKOTA Hiroshi wrote:
> Package: wnpp
> Severity: wishlist
> Owner: YOKOTA Hiroshi
> X-Debbugs-Cc: debian-de...@lists.debian.org, yokota.h...@gmail.com
>
> * Package name: 7zip
> Version : 21.02
> Upstream Author : Igor Pavlov
> * URL
On Mon, 2021-05-17 at 10:41:28 -0700, Noah Meyerhans wrote:
> -if [ $code -eq 104 ] && \
> -! command -v systemctl > /dev/null ; then
> -# We're not using systemd and thus may have some sysvinit cleanup
> -# to do in order to comply with policy 9.3.3.1
> -
> -
ot
preserve user configuration. :)
The problem seems to stem from commit
955194996671416bd9712bfefe82c4847a7f2a5b which dropped the ENABLED
variable support from /etc/default/spamassassin but forgot to also
remove the handling of that variable from the postinst, which means
that even if the daemon is runn
On Fri, 2021-05-14 at 12:17:44 +0200, Guillem Jover wrote:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/19610
>
> On Fri, 2021-05-14 at 11:34:37 +0200, Michael Biebl wrote:
> > Am 14.05.21 um 11:17 schrieb Guillem Jover:
> > > The version in exper
Control: forwarded -1 https://github.com/systemd/systemd/issues/19610
On Fri, 2021-05-14 at 11:34:37 +0200, Michael Biebl wrote:
> Am 14.05.21 um 11:17 schrieb Guillem Jover:
> > The version in experimental introduced a new system group called sgx
> > which has an over
Package: systemd
Version: 248-1
Severity: normal
Hi!
The version in experimental introduced a new system group called sgx
which has an overly generic name with the potential to collide with
user and group names, say their initials. Could it be rename to use
the system name convention of
Package: shim-signed
Version: 1.34+15.4-2
Severity: serious
Hi!
Just upgraded shim packages today and then shim-signed was unable to
configure:
,---
Setting up shim-signed:amd64 (1.34+15.4-2) ...
Installing for x86_64-efi platform.
Installation finished. No error reported.
Package: sensible-utils
Version: 0.0.14
Severity: normal
Hi!
The select-editor program misbehaves when the environment does not
contain the HOME variable set. For normal users this means the code
will be unable to write to «/.selected_editor», for root that means
the code will pollute the «/»
Source: radicale
Source-Version: 3.0.6-2
Severity: important
[ Not setting as serious, even though it might be, because I don't
think this is a setup directly supported by Debian? Even though
upstream seems to. ]
Hi!
Just upgraded my server to bullseye, and one of the errors was with
[ Just upgraded my server to bullseye, and aide started to fail, now
noticed this report, after also hitting the error via lsattr. ]
On Mon, 2021-04-05 at 17:35:54 -0400, Theodore Ts'o wrote:
> On Mon, Apr 05, 2021 at 12:46:48AM +0200, Chris Hofstaedtler wrote:
> > AFAICT, for /dev/dri/card0
Hi!
[ I'm assuming this is from Andreas Beckman? :) CCed explicitly. ]
On Wed, 2021-03-17 at 12:04:32 +0100, piupar...@zam127.zam.kfa-juelich.de wrote:
> Package: dpkg
> Version: 1.20.7.1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block 985297 with -1
Hi!
On Thu, 2021-04-15 at 21:18:03 +0200, Simon Josefsson wrote:
> Chris Hofstaedtler writes:
> > * Simon Josefsson [210415 19:06]:
> >> Hi! Upstream is not maintained either -- at least the download URL in
> >> netkit-telnet's debian/copyright file does not work. How about dropping
> >>
021 19.22, Guillem Jover wrote:
> > > Otherwise, I don't see a bug in dpkg for this here. And I'd be
> > > inclined to close this.
>
> I've managed to solve most of the upgrade paths by propagating some
> Conflicts from libreoffice-common to libreoffice-core, s.t. t
Control: retitle -1 [pre-approval] unblock: dpkg/1.20.9
Control: tag -1 - moreinfo
Hi!
On Tue, 2021-04-13 at 20:22:46 +0200, Ivo De Decker wrote:
> On Tue, Apr 13, 2021 at 08:13:10PM +0200, Guillem Jover wrote:
> > On Tue, 2021-04-13 at 17:58:08 +0200, Guillem Jover wrote:
> > &g
On Tue, 2021-04-13 at 17:58:08 +0200, Guillem Jover wrote:
> On Tue, 2021-04-13 at 15:36:08 +0200, Ivo De Decker wrote:
> > Please go ahead with the upload and remove the moreinfo tag from this bug
> > when
> > the new version is in unstable.
>
> Thanks! I'm targetin
Hi!
On Tue, 2021-04-13 at 15:36:08 +0200, Ivo De Decker wrote:
> On Mon, Apr 12, 2021 at 06:20:10PM +0200, Guillem Jover wrote:
> > This is a pre-approval unblock request for dpkg.
> >
> > [ Reason ]
> >
> > This includes an RC bug fix, and an old regre
.debdiff.xz
Description: application/xz
From 09b0b3ab99ba197a4fc5abf9363de32b472d9b61 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sat, 16 Jan 2021 13:34:34 +0100
Subject: [PATCH 01/15] Test::Dpkg: Fix test data path fetching on CPAN
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
On Thu, 2021-04-08 at 19:49:42 +0200, Helge Kreutzmann wrote:
> Done (locally); any specific commit message requested?
Great, thanks. Hmm typo or other similar translation fixes do not have
a standardized format, so use whatever you feel like with a "po: "
prefix for now as I'll have to massage
Hi!
On Thu, 2021-04-08 at 21:26:07 +0200, Helge Kreutzmann wrote:
> for some reason, I cannot push at the moment:
> ssh: connect to host git.dpkg.org port 22: Connection timed out
> fatal: Konnte nicht vom Remote-Repository lesen.
>
> Bitte stellen Sie sicher, dass die korrekten
Hi!
On Tue, 2021-03-02 at 13:09:40 +0100, Christoph Berg wrote:
> Package: dpkg-dev
> Version: 1.20.7.1
> Severity: normal
> in dpkg-gencontrol, the translation of
>
> dpkg-gencontrol: warning: Depends field of package elephant-shed:
> substitution variable ${keyring:Depends} used, but is not
021 at 23:47:30 +0100, Guillem Jover wrote:
> > > I've recently retried switching to Wayland and I think I'm sticking
> > > with it. But while checking for toolkits support, noticed that SDL 1.2
> > > does not have native Wayland support, but SDL 2.0 does.
> >
Hi!
On Thu, 2021-03-18 at 18:25:17 +0100, Rene Engelhard wrote:
> Am 18.03.21 um 06:53 schrieb Rene Engelhard:
> > It would be helpful if you actually did your homework. There already was
> > 985297 so you now caused a bogus addditional RC bug.
> >
> > That bug even was marked as blocked by the
On Mon, 2020-03-15 at 19:26:14 +, Nicholas Brown wrote:
> I could imagine the patch below, which I started looking at some time ago
> but never
> got around to coming back to, could form a start at implementing this.
This is pretty close to what I initially did, and mentioned on my first
On Wed, 2021-03-17 at 12:21:24 -0700, Jonathan Nieder wrote:
> Guillem Jover wrote:
> > The latest version in sid, breaks user code sourcing the git-sh-prompt
> > shell library as it moved from /usr/lib/ to /usr/libexec, even though
> > I see the comment there says to co
On Wed, 2021-03-17 at 09:48:35 +0100, Sven Joachim wrote:
> On 2021-03-16 13:47 +0100, Guillem Jover wrote:
> > Could you perhaps add a backwards compatibility symlink for the time
> > being? Or when using bash, perhaps even a warning based on the
> > “caller” builtin if u
Control: reassign -1 libreoffice-common 1:7.0.4-3
[ Leaving all context for the reassign. ]
Hi!
On Wed, 2021-03-17 at 12:13:52 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.20.7.1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: block 985297
Package: git
Version: 1:2.31.0-1
Severity: normal
Hi!
The latest version in sid, breaks user code sourcing the git-sh-prompt
shell library as it moved from /usr/lib/ to /usr/libexec, even though
I see the comment there says to copy it, but that means no automatic
upgrades. :/
Could you perhaps
Source: glob2
Source-Version: 0.9.4.4-5
Severity: wishlist
Hi!
Upstream git (which seems rather active) includes SDL2 support, which
among others supports Wayland natively. SDL1 is considered deprecated
by upstream and should be switched away from. It would be nice to
package a snapshot of that.
Source: edgar
Source-Version: 1.23-1
Severity: wishlist
Hi!
Upstream is at 1.34, which happens to have SDL2 support, which among
others supports Wayland natively. SDL1 is considered deprecated by
upstream and should be switched away from.
Thanks,
Guillem
Source: reminiscence
Source-Version: 0.2.1-2
Severity: wishlist
Hi!
Upstream is at 0.4.6, which happens to have SDL2 support, which among
others supports Wayland natively. SDL1 is considered deprecated by
upstream and should be switched away from.
Thanks,
Guillem
Source: aranym
Source-Version: 1.1.0-2
Severity: wishlist
Hi!
This package is currently built against SDL 1.2, which is considered
deprecated by upstream who recommend using instead SDL 2.0. The latter
also supports Wayland natively.
It seems like this package can be built with both, so it
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: pkg-sdl-maintain...@lists.alioth.debian.org,
debian-devel-ga...@lists.debian.org
* Package name: libsdl1.2-compat
Version : 0.0~git
Upstream Author : Ryan C. Gordon
* URL : https://github.com/libsdl-org/sdl12-compat
*
Control: reassign -1 mono-gac 6.8.0.105+dfsg-3
Control: retitle -1 mono-gac: messes with the unpacking of another package
[ Leaving context for the reassign. ]
Hi!
On Fri, 2021-03-12 at 12:54:31 +0100, Andreas Beckmann wrote:
> Package: mono-runtime-common,dpkg
> Severity: serious
> User:
Control: reassign -1 fltk1.3
Control: retitle -1 fltk: Please add a Wayland driver
Hi!
On Sat, 2021-03-06 at 23:21:33 -0500, Aaron M. Ucko wrote:
> Guillem Jover writes:
> > Given that the X.Org server is apparently pretty much dead, that other
> > distributions are also switc
Hi!
On Sat, 2021-03-06 at 15:50:44 +0100, Guillem Jover wrote:
> On Thu, 2021-01-21 at 16:31:29 +0100, Michel Le Bihan wrote:
> > I built Chromium with ozone, but I'm not sure if it's ready for Debian
> > yet. It will need testing. You can test it, if you want:
> > https:
Control: reassign -1 apt
Control: retitle -1 apt: Broken python-empy:amd64 Depends on python:any:any
Hi!
On Fri, 2021-03-05 at 11:34:26 +0100, Andreas Beckmann wrote:
> Package: dpkg
> Version: 1.19.7
> Severity: normal
> I just saw something curious in dpkg's debug output:
>
> Investigating
Hi!
On Thu, 2021-01-21 at 16:31:29 +0100, Michel Le Bihan wrote:
> I built Chromium with ozone, but I'm not sure if it's ready for Debian
> yet. It will need testing. You can test it, if you want:
> https://lebihan.pl/chromium/chromium_88.0.4324.96-ozone.tar
> Currently, I only built for amd64.
Source: fltk1.1
Source-Version: 1.1.10-29
Severity: wishlist
Tags: upstream
Forwarded: https://www.fltk.org/str.php?L3371
Hi!
I've just switched to use Wayland (after several previous attempts),
and I noticed one of the remaining items on my system that require
using the Xwayland compatibility
ttached patches, which I'll commit into master once I open it up for
1.21.x.
Also just to make sure, the GNU triplets are:
arc-linux-gnu
arceb-linux-gnu
No ABI modifiers (stuff like “eabi”) for the libc part (“gnu“) right?
Thanks,
Guillem
From f5cae4f8fc4ef67ec5e26dffeb3b3c540949f554 Mon S
501 - 600 of 4830 matches
Mail list logo
