Hi,
Quoting Chris Hofstaedtler (2024-04-28 18:30:56)
> the autopkgtests for mmdebstrap as part of migration tests for testing/amd64
> fail with apt reporting 'Not found' errors.
>
> As an example, for this scenario:
> mmdebstrap 1.4.3-6
> util-linux/2.40-8 gdm3/46.0-2 sssd/2
> src:util-linux
Package: reform-setup-wizard
Version: 0.1.0-1
Severity: serious
As it says in subject.
Control: tag -1 pending
Hello,
Bug #1064266 in python-lsp-black reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: python-lsp-black
Version: 2.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sylves...@debian.org
Hi,
python-lsp-black currently FTBFS in unstable. To track down the reason,
I ran debbisect:
DEBIAN_BISECT_SRCPKG=python-lsp-black debbisect
Source: krb5
Version: 1.20.1-5+b1
Severity: serious
Tags: ftbfs
Hi,
there as a binNMU "Rebuild to sync binNMU versions" for krb5 and that
failed for arm64, armel and ppc64el:
https://buildd.debian.org/status/package.php?p=krb5
The error logs look very similar:
making check in lib/rpc...
Control: retitle -1 building less from source fails the island test
On Fri, 09 Feb 2024 00:24:00 +0100 Johannes Schauer Marin Rodrigues
wrote:
> the current curl packaging
The first sentence in my mail should've been
> the current less packaging
Apologies for the confusion!
cheers,
Source: less
Version: 590-2
Severity: serious
Tags: patch
Hi,
the current curl packaging uses pre-built artifacts from the upstream
tarball without regenerating them. Attempting to regenerate them by
running "make -f Makefile.aut" proceeds to call curl to download stuff
from
Hi,
On Tue, 16 Jan 2024 20:43:11 +0100 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
thank you for your bug!
> Couldn't find include 'GObject-2.0.gir' (search path: '['/usr/share/gir-1.0',
> '/usr/lib/x86_64-linux-gnu/gir-1.0',
>
On 2024-01-11 23:40, Bastian Germann wrote:
Ping. It is now 1 week until this will auto-remove several packages.
Please consider releasing and packaging the new release.
Whoops, sorry!! And thank you for the ping.
This has now been taken care of. The version I just uploaded has the
Package: zlib1g
Version: 1:1.3.dfsg-2
Severity: serious
Hi,
I didn't investigate this further yet but filing this as RC as it is easy to
reproduce and it's easy to find out that only zlib1g changed using debbisect.
Downgrading to zlib1g 1:1.2.13.dfsg-3 makes the problem go away. Steps to
Package: gedit
Version: 44.2-1
Severity: serious
Hi,
currently, gedit cannot be installed in unstable with this error message
from apt:
Reading package lists...
Building dependency tree...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if
Quoting Alexandru Mihail (2023-09-21 12:30:52)
> I have no problem with that, can you minimally review the tag and determine
> if it's fit for release or if anything is missing (ignore the added patch,
> that fixes a separate bug) ?
>
> This is still one of my first releases, I'm still getting
Hi,
Quoting Alexandru Mihail (2023-09-21 01:31:23)
> Hello again,> okay, I'll wait. Thank you for your quick reply!
> Thank you for the wait !
> I've committed the necessary systemd service fix into a new mini-httpd
> release (1.30-5). Currently waiting for sponsored upload from my mentor.
if
Quoting Alexandru Mihail (2023-09-19 23:41:05)
> > do you have an estimate when you think you can upload this? This bug has
> > now blocked part of my work in Debian for two weeks and I'm unable to do
> > another release for my package until this bug gets fixed.
> I'm planning to release no later
Hi,
Quoting Alexandru Mihail (2023-09-17 15:13:29)
> This is great, I successfully tested your proposed service file changes and
> everything appears to work great ! We're currently on
> mini-httpd/unstable,now 1.30-4; The next release (1.30-5) will incorporate
> your fix, closing this bug.
do
Source: morty
Severity: serious
Hi,
last upstream commit was in April 2021. This package was mainly useful
together with searx (from the same developer) but that project got
abandoned in favour of searxng by different people which does not need
morty anymore. Additionally, morty has a very low
Hi,
Quoting Alexandru Mihail (2023-09-16 16:40:38)
> > I asked in #debian-systemd and the fix could be as simple as setting the
> > following in the .service file:
> >
> > EnvironmentFile=-/etc/default/mini-httpd
> >
> > Can you confirm?
> I will test this and get back to you as soon as I can
Hi Nicholas,
Quoting Nicholas D Steeves (2023-09-16 14:06:00)
> Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
> fluidsynth -dev package. 'not sure how that happened, but my mistake! Isn't
> only waiting 48h a bit rushed for an NMU though?
the number of delayed days
Hi,
Quoting Johannes Schauer Marin Rodrigues (2023-09-16 09:23:43)
> On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues
> wrote:
> > after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems
> > that
> > this new version changed the init s
Hi Alexandru & Nicholas,
On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues
wrote:
> after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems that
> this new version changed the init script for a systemd unit where the latter
> ignores the con
Control: affects -1 + src:ardour src:blockattack src:calf src:chocolate-doom
src:crispy-doom src:denemo src:fluidsynth-dssi src:freedink src:frotz
src:gambas3 src:gargoyle-free src:gst-plugins-bad1.0 src:jag src:pianobooster
src:planetblupi src:qsynth src:qtads src:scummvm src:toppler src:ufoai
Package: mini-httpd
Version: 1.30-4
Severity: serious
Hi,
after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems
that this new version changed the init script for a systemd unit where
the latter ignores the contents of /etc/default/mini-httpd.
If that is intentional and not an
Package: usrmerge
Version: 36
Severity: serious
Tags: patch
Hi,
the recent changes to usr-is-merged.postinst broke DPKG_ROOT support:
Setting up usr-is-merged (36) ...
removed '/lib64'
/tmp/mmdebstrap.P6Rv45i7Hi/var/lib/dpkg/info/usr-is-merged.postinst: 16: rmdir:
not found
dpkg: error
Package: debianutils
Version: 5.9
Severity: serious
Tags: patch
Hi,
this commit broke $DPKG_ROOT support:
https://salsa.debian.org/debian/debianutils/-/commit/89daf5e2
this in turn breaks the mmdebstrap autopkgtest, thus filing this with severity
serious to prevent transition to testing until
Hi Adrian,
thank you for weighing in!
Quoting Adrian Bunk (2023-07-20 01:27:10)
>
> Package: box64
> Architecture: amd64 arm64 ppc64el riscv64
> Depends:
> libgcc-s1:amd64,
> libstdc++6:amd64,
>
> A package must not assume that the user has other architectures enabled.
why not? Is this
Quoting Jeremy Bícha (2023-07-18 22:29:58)
> On Tue, Jul 18, 2023 at 4:23 PM Johannes Schauer Marin Rodrigues
> wrote:
> > Quoting Jeremy Bícha (2023-07-18 21:20:21)
> > > https://tracker.debian.org/pkg/box64 says that box64 is unable to migrate
> > > into Testin
Hi,
Quoting Jeremy Bícha (2023-07-18 21:20:21)
> https://tracker.debian.org/pkg/box64 says that box64 is unable to migrate
> into Testing because it has unsatisfiable dependencies on amd64, arm64,
> ppc64el (and I guess riscv64)
I saw that but it doesn't say which one is unsatisfiable. Do you
Hi,
Quoting Helmut Grohne (2023-07-06 13:27:19)
> librust-syn-1-dev has (among other things) the following metadata:
>
> Provides: librust-syn-1.0.109-dev
> Breaks: librust-syn-1.0.109-dev
> Multi-Arch: same
this looks very bad.
> If apt and dose were refusing this situation this were a normal
Hi,
Quoting Nicolas Dandrimont (2023-05-18 20:51:04)
> On Thu, May 18, 2023, at 10:03, Marc Haber wrote:
> > adduser probably needs an additional hint because the new upload makes
> > piuparts fail now, as discussed yesterday.
> To work around this issue on the piuparts side, it sounds like we
Hi,
here is a status update on the adduser situation.
Quoting Johannes Schauer Marin Rodrigues (2023-05-10 08:10:26)
> The remaining 14 failures belong to the following 9 source packages:
>
> amavisd-new #1035841
> debian-edu-fai #1035292
> desktop-autoloader #1
Hi,
Quoting Johannes Schauer Marin Rodrigues (2023-05-16 23:35:38)
> On Wed, 03 May 2023 14:45:01 +0200 Andreas Beckmann wrote:
> > There is ongoing discussion how to handle system users on package
> > removal, see https://bugs.debian.org/621833
> > Consensus seems to be
Hi,
Quoting Johannes Schauer Marin Rodrigues (2023-05-16 23:34:06)
> Quoting jo...@debian.org (2023-05-10 07:56:44)
> > To work around this problem, at least 125 source packages [codesearch]
> > simply
> > ignore failures of calling the passwd or adduser tools during pur
Quoting Johannes Schauer Marin Rodrigues (2023-05-16 23:27:26)
> since time is running out, would you mind if I NMU kismet with this change
> and file the unblock request?
never mind, no urgency here, because kismet is not in testing (nor in the
current stable) and suffers from multiple R
Hi Hubert,
Quoting Hubert Chathi (2023-05-17 00:43:00)
> On Tue, 16 May 2023 23:31:16 +0200, Johannes Schauer Marin Rodrigues
> said:
> > since time is running short, I am going to NMU matrix-sydent on Thursday
> > with a delay of 2 days unless you disagree and/or want t
Hi,
On Sun, 14 May 2023 18:29:56 +0200 Patrice Duroux
wrote:
> Here is a patch for the .postrm script useing deluser/delgroup on purge.
that patch looks good. Thanks!
Since time is running short, I am going to NMU x2gothinclient on Thursday with
a delay of 2 days unless you disagree and/or
On Wed, 03 May 2023 14:45:01 +0200 Andreas Beckmann wrote:
> There is ongoing discussion how to handle system users on package
> removal, see https://bugs.debian.org/621833
> Consensus seems to be not to remove system users (to avoid reusing UIDs
> which could grant access to the wrong files) but
Hi,
Quoting jo...@debian.org (2023-05-10 07:56:44)
> To work around this problem, at least 125 source packages [codesearch] simply
> ignore failures of calling the passwd or adduser tools during purge. The
> following patch should fix this package by doing the same:
>
>
Hi,
Quoting jo...@debian.org (2023-05-10 07:49:26)
> To work around this problem, at least 125 source packages [codesearch] simply
> ignore failures of calling the passwd or adduser tools during purge. The
> following patch should fix this package by doing the same:
>
>
Hi,
On Sun, 30 Apr 2023 05:08:50 +0200 Andreas Beckmann wrote:
> during a test with piuparts I noticed your package failed to purge due
> to a command not found. According to policy 7.2 you cannot rely on the
> depends being available during purge, only the essential packages are
> available for
Hi,
On Thu, 11 May 2023 23:52:00 + Debian FTP Masters
wrote:
> Changes:
> amavisd-new (1:2.13.0-3) unstable; urgency=medium
> .
>* Fix failure to purge without adduser. Closes: #1035841.
thank you! Would you like me to take care of filing the unblock request with
release.debian.org
Hi,
Quoting Helmut Grohne (2023-05-07 13:52:50)
>
> I contend that:
>
> 1. This change is in unstable since 2022-10-31, i.e. more than half a
> year.
> 2. While having adduser drop from the essential+apt set is caused by
> apt dropping it, this was an implementation detail and any
Hi Shengjing,
Quoting Shengjing Zhu (2023-03-01 06:40:38)
> I've debugged it as well and here is my write up. Though I don't have
> solution yet.
you don't have a *good* solution yet but I think you are extremely close! Thank
you so much for spending all the time debugging this *and* for this
Hi,
Quoting Johannes Schauer Marin Rodrigues (2023-02-06 00:47:35)
> since glibc 2.34 and coreutils 9.1, fakeroot fails to preserve ownership
> information when running "cp -a" on a file owned by a user other than
> root. On armel, armhf and i386 (our 32 bit arches)
Package: fakeroot
Version: 1.30.1-1.1
Severity: grave
Control: affects -1 + mmdebstrap
Hi,
since glibc 2.34 and coreutils 9.1, fakeroot fails to preserve ownership
information when running "cp -a" on a file owned by a user other than
root. On armel, armhf and i386 (our 32 bit arches), you can
Hi,
Quoting Vagrant Cascadian (2023-02-03 00:18:58)
> On 2023-02-01, Jérôme Charaoui wrote:
> > I don't know how common that is in build environments, but it's not
> > something that I have or think I should have in my build (sbuild) or
> > test (autopkgtest) environments.
>
> I was able to
Package: greetd
Version: 0.8.0-1+b1
Severity: critical
Hi,
installing the greetd package will log out the current user. When
attempting to log in again, the message "This account is currently not
available." is shown and the user is put back into the login prompt.
This happens independent of
Package: ltrace
Version: 0.7.3-6.3
Severity: grave
Hi,
running ltrace on mipsel, I get:
$ ltrace echo
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ef8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ee8
unexpected breakpoint at 0x77e74ef8
unexpected
Control: tag -1 pending
Hello,
Bug #1016070 in sbuild reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 + patch
Control: forwarded -1
https://gitlab.mister-muffin.de/josch/mmdebstrap/commit/d4cb0656396b12718f67f045e548d6ebe9ffef85
Quoting Bastian Blank (2022-10-09 10:28:25)
> mmdebstrap writed "uninitialized" to /etc/machine-id. This triggers
> first boot semantic[1], so makes the
Package: mmdebstrap
Version: 1.2.1-2
Severity: serious
X-Debbugs-Cc: jo...@debian.org
The functionality of lsb-base is in the Essential:yes set since
Bullseye. The package itself is now an empty transitional package
(because debootstrap doesn't understand the Provides relationship) which
depends
Hi Paul,
thanks for caring about my "contrib" package! :)
Quoting Paul Gevers (2022-09-18 11:44:07)
> vcmi build depends on libluajit-5.1-dev but that got removed on
> ppc64el because it doesn't work correcty on that architecture and
> noone volunteers to fix *and maintain* it on that
ontconfig-config from arch:all to
+arch:any prevents this from happening. (closes: #960679)
+
+ -- Johannes Schauer Marin Rodrigues Sun, 04 Sep 2022 18:37:48 +0200
+
fontconfig (2.13.1-4.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru fontconfig-2.13.1/debian/control fo
Source: mmdebstrap
Version: 1.1.0-1
Severity: serious
X-Debbugs-Cc: jo...@debian.org
Control: block -1 by 1017590
Hi,
since the upload of src:glibc 2.34, getpwnam are not wrapped anymore by
fakechroot. This breaks the autopkgtest of mmdebstrap.
See https://bugs.debian.org/1017590 for details.
Package: debhelper
Version: 13.9
Severity: serious
X-Debbugs-Cc: jo...@debian.org
Steps to reproduce:
$ sbuild -d unstable shadow
[...]
[...]
[...]
passwd_4.11.1+dfsg1-2_amd64.deb
---
new Debian package, version 2.0.
size 944912 bytes: control archive=7432 bytes.
Package: freecad
Version: 0.20+dfsg1-2
Severity: serious
X-Debbugs-Cc: jo...@debian.org
Hi,
when installing freecad together with kicad, one gets the following
error:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the
Hi Lucas,
Quoting Lucas Nussbaum (2022-07-29 20:18:41)
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
thanks a lot for your bug report!
> > command: MALLOC_PERTURB_=84 /usr/bin/appstream-util validate-relax
> >
Quoting Paul Gevers (2022-07-26 22:24:55)
> That worker (ci-worker13) has 7 TB of disk available, so space shouldn't be
> the problem. I'm also not seeing [1] the disk usage anytime higher than 7%
> (and it's actually that /mnt/lxc-containers that's being used and that
> doesn't peak above 1.2%
Hi,
Quoting Luca Boccassi (2022-07-26 15:27:35)
> If it's not appropriate, please do update it accordingly, but IIRC it's what
> gets used in these cases.
a bunch of sbuild issues piled up during the last weeks so I'll be doing an
upload soon and will include a fix for this as well.
> > I put
Hi,
thank you for your bug report!
Quoting Luca Boccassi (2022-07-26 13:28:50)
> Severity: serious
why is an autopkgtest failure "serious"?
> The autopkgtest run for sbuild keeps failing in debci, blocking other
> packages migrations. The failure manifests in two different error
> types, but
Source: neatvnc
Version: 0.5.1+dfsg-1
Severity: serious
Justification: Policy 2.3
X-Debbugs-Cc: jo...@debian.org
Hi,
your recent upload of neatvnc introduced murmurhash which is copyright
"2014 Joseph Werle" but you did not add that to d/copyright:
Hi Boyuan,
recently you uploaded neatvnc 0.5.1+dfsg-1 without making sure that its reverse
dependencies don't break. This resulted in the following FTBFS for wayvnc. I'm
fixing that now, but in the future, please do a rebuild of your reverse
dependencies before uploading or upload to experimental
Hi Andreas,
Quoting Andreas Tille (2022-05-04 17:15:49)
> > Well, yes, it would be more convenient for me, but you are doing the work,
> > so I'm not going to make any demands. :D I think the stronger reason to go
> > roll back to dcmtk-3.6.7+really3.6.6 is, that Sebastian Ramacher as a
> >
Quoting Andreas Tille (2022-05-04 16:07:27)
> I'm an3as in IRC but I do not lurk in IRC usually.
Ah, nice word play in the nick. :)
> > So it seems that the right way forward would be an upload of
> > dcmtk-3.6.7+really3.6.6.
> >
> > And then not forgetting the Breaks+Replaces from libdcmtk17
Hi Andreas,
Quoting Andreas Tille (2022-05-04 14:57:25)
> > Will you take care of making sure that reverse dependencies are binNMU-ed?
>
> I admit I would use the chance to to real team uploads and check the
> other dependencies manually. Your finding with ant makes me suspicious
> about some
Hi Andreas,
Quoting Andreas Tille (2022-05-04 11:25:20)
> Aaargh, sorry for my sloppyness. I did not expect a SONAME bump connected
> with micro-Version bump. An updated package is in new.
thanks a lot for this very quick fix!
I think the problem is that package-name-doesnt-match-sonames is
Hi,
On Tue, 03 May 2022 22:17:24 +0200 Johannes Schauer Marin Rodrigues
wrote:
> thanks for your upload of the new upstream version of dcmtk. Unfortunately,
> I think this is missing a proper transition because the ABI and thus the
> SONAME changed. This can also be seen in the aut
.10.1+dfsg/debian/changelog2022-05-04 10:13:08.0
+0200
@@ -1,3 +1,10 @@
+orthanc (1.10.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * add patch to build with dcmtk >= 3.6.7 (closes: #XXX)
+
+ -- Johannes Schauer Marin Rodrigues Wed, 04 May 2022
10:13
Source: itksnap
Version: 3.6.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: jo...@debian.org
Hi,
currently itksnap FTBFS because it B-D on libvtk6-dev which depends on
libjsoncpp24:
@@ -1,3 +1,10 @@
+biosig (2.3.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * add patch to build with dcmtk >= 3.6.7 (closes: #XXX)
+
+ -- Johannes Schauer Marin Rodrigues Tue, 03 May 2022
23:06:01 +0200
+
biosig (2.3.3-1) unstable; urgency=medium
[ Alois Schlögl ]
d
Source: dcmtk
Version: 3.6.6-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ti...@debian.org
Hi Andreas,
thanks for your upload of the new upstream version of dcmtk.
Unfortunately, I think this is missing a proper transition because the
ABI and thus the SONAME changed.
Control: tag -1 + patch
Dear sfepy maintainers,
On Fri, 10 Dec 2021 21:49:08 +0100 Paul Gevers wrote:
> Currently this regression is blocking the migration of python3-defaults
> to testing [1]. https://docs.python.org/3/whatsnew/3.10.html lists
> what's new in Python3.10, it may help to
Hi Sebastian,
On Fri, 21 Jan 2022 13:52:15 +0100 Johannes Schauer Marin Rodrigues
wrote:
> Sebastian, do you think that this is a solution that would allow debianutils
> to
> be unblocked from migration to testing?
the recent debianutils NMU by waldi implements the tech ctte decision
Control: tag -1 + patch
On Sat, 22 Jan 2022 04:08:18 +0100 Vincent Lefevre wrote:
> I get the following error when I want to upgrade:
>
> Unpacking debianutils (5.6-0.1) over (5.5-1) ...
> dpkg: error processing archive
> /var/cache/apt/archives/debianutils_5.6-0.1_amd64.deb (--unpack):
>
Control: tag -1 + patch
On Tue, 30 Nov 2021 12:08:44 + Robie Basak wrote:
> If I patch the debianutils source package, then I find that I cannot
> easily rebuild it without the following files from Salsa VCS that are
> not included in the Debian source package:
>
>
Hi Sebastian,
On Mon, 18 Oct 2021 06:39:01 +0200 Helmut Grohne wrote:
> As recently announced [1], the Release Team now considers packages that are
> out-of-sync between testing and unstable for more than 60 days as having a
> Release Critical bug in testing. Your package src:debianutils has
Control: retitle -1 Pillow claims GIF frame to be mode RGB instead of P
Control: reassign -1 pillow 9.0.0
Hi,
Quoting Matthias Klose (2022-01-13 12:23:39)
> img2pdf's autopkg tests fail with pillow 9.0.0, as seen at
> https://tracker.debian.org/pkg/img2pdf
>
> === short
Control: block 1003191 by -1
Control: affects -1 + mmdebstrap
On Wed, 05 Jan 2022 13:25:57 -0800 "Joseph Carter"
wrote:
> On Sun, 02 Jan 2022 23:28:32 +0100 Hilko Bengen wrote:
> > * Laurent Bigonville:
> >
> > > It looks like libguestfs-tools version 1:1.46.2-1 in depending on
> > >
Package: mmdebstrap
Severity: serious
Version: 0.8.2-1
Hi,
Quoting Benjamin Drung (2022-01-05 20:59:37)
> I saw that the autopkgtests for bdebstrap fails for mmdebstrap 0.8.2-1
> on Ubuntu jammy:
> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
>
> amd64
Control: severity -1 normal
On Wed, 03 Nov 2021 15:47:39 +0100 Johannes Schauer Marin Rodrigues
wrote:
> Quoting Sam Hartman (2021-11-03 15:36:30)
> > I did initial investigation of the source, and there's nothing odd going
> > on there with the configure script.
> >
.126+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Undo the changes of the last upload. (Closes: #998867)
+
+ -- Johannes Schauer Marin Rodrigues Sun, 28 Nov 2021 12:38:15 +0100
+
debootstrap (1.0.126) unstable; urgency=low
* Ensure bookworm+ suites are set up with m
Control: affects -1 mmdebstrap
Hi,
Quoting Dimitri John Ledkov (2021-11-15 14:54:36)
> > Please point out what you plan to do about this change in debootstrap so
> > that I can adapt the mmdebstrap autopkgtest accordingly.
>
> I did notice the mmdebstrap autopkgtest regression. [...]
this bug
Quoting Julien Cristau (2021-11-09 09:33:14)
> On Tue, Nov 09, 2021 at 07:49:03AM +0100, Johannes Schauer Marin Rodrigues
> wrote:
> > since 1.0.126 the --no-merged-usr option became a no-op if for any code
> > name but
> > etch*|lenny|squeeze|wheezy|jessie*|stretch|ascii
Hi Sam,
Quoting Sam Hartman (2021-11-03 15:36:30)
> I did initial investigation of the source, and there's nothing odd going
> on there with the configure script.
> So, this one is going to be strange and probably isn't pam's fault.
>
> I think the bug is appropriate, but it wouldn't surprise me
Source: mlv
Version: 3.1.0-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
since the upload of dash 0.5.11+git20210903+057cd650a4ed-2 yesterday,
mlv FTBFS with:
./configure: 8146: test: xFrench: unexpected operator
./configure:
Control: retitle -1 imagemagick dropped FFTW support
Control: reassign -1 imagemagick 8:6.9.12.20+dfsg1-1.1
Control: tags -1 - moreinfo
Quoting Håvard Flaget Aasen (2021-10-04 19:15:00)
> It looks like Imagemagick has changed some configure options. In
> commit [1] they changed support for FFTW
Hi Felix,
Quoting Felix Geyer (2021-09-30 20:56:14)
> On 30.09.21 08:40, Johannes Schauer Marin Rodrigues wrote:
> > On Fri, 17 Sep 2021 07:15:16 +0200 Johannes Schauer Marin Rodrigues
> > wrote:
> >> you set the upstream bug to
> >> https://github.com/seccomp
Hi Felix,
On Fri, 17 Sep 2021 07:15:16 +0200 Johannes Schauer Marin Rodrigues
wrote:
> you set the upstream bug to https://github.com/seccomp/libseccomp/issues/336
> but I don't think that is correct. The failures is not the same for the
> different architectures. mipsel fails diffe
Hi Felix,
you set the upstream bug to https://github.com/seccomp/libseccomp/issues/336
but I don't think that is correct. The failures is not the same for the
different architectures. mipsel fails different than arm64. I bisected upstream
git on both architectures and found out that the arm64
Source: libseccomp
Version: 2.5.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
libseccomp fails to build on arm64, armhf, mips64el and mipsel. This in
turn makes the tests of my package mmdebstrap fail because of the
resulting
946)
+
+ -- Johannes Schauer Marin Rodrigues Thu, 09 Sep 2021 19:50:34 +0200
+
fakechroot (2.19-3.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru fakechroot-2.19/debian/patches/0001-Wrap-__nss_files_fopen-for-getpwnam-in-glibc-2.32.patch fakechroot-2.19/debian/patches/0001-W
Control: tag -1 + patch
Control: forwarded -1 https://github.com/dex4er/fakechroot/issues/97
With the help of the glibc developer Adhemerval Zanella I managed to find a
solution for this problem. The attached patch wraps __nss_files_fopen from
glibc.--- a/configure.ac
+++ b/configure.ac
@@ -165,6
I got a gdb backtrace for the openat syscall of /etc/passwd.
This is with glibc 2.31:
#0 __GI___open64_nocancel (file=0x77df715e "/etc/passwd", oflag=524288)
at ../sysdeps/unix/sysv/linux/open64_nocancel.c:45
#1 0x77e82185 in __GI__IO_file_open (fp=fp@entry=0x96b0,
Quoting Johannes Schauer Marin Rodrigues (2021-09-08 13:59:02)
> since the upload of glibc 2.32 to unstable, adduser under fakechroot
> fails because it is not wrapping some library call and thus read the
> system's /etc/passwd instead of the chroot's.
>
> Some bits from strace out
Package: fakechroot
Version: 2.19-3.4
Severity: grave
Justification: renders package unusable
Hi,
since the upload of glibc 2.32 to unstable, adduser under fakechroot
fails because it is not wrapping some library call and thus read the
system's /etc/passwd instead of the chroot's.
Some bits
y options.
>
> Johannes Schauer Marin Rodrigues, Do you agree with this solution?
It is not up to me but it's Debian policy that decides whether the solution is
correct or not. Quickly skimming through the diff it seems that the offending
file has been removed. Whether this is the c
Package: glances
Version: 3.1.5-1
Severity: serious
Justification: Policy 2.2.1
Hi,
the source package contains:
glances/outputs/static/public/glances.js
glances/outputs/static/public/glances.map.js
these files are copied into the binary package as:
Package: rviz
Version: 1.14.4+dfsg-3
Severity: grave
Justification: renders package unusable
Hi,
when trying to run rviz I get:
rviz: error while loading shared libraries: libOgreOverlay.so.1.12.5: cannot
open shared object file: No such file or directory
But all my system has is
Quoting Johannes Schauer Marin Rodrigues (2021-02-04 08:50:51)
> oh wow! Thanks a ton for all your work! This is phantastic. :)
while this still stands
> Do you want to do the upload yourself? Just add yourself to Uploaders as well
> while you are at it, you seem to know what you
Hi Sunil,
Quoting Sunil Mohan Adapa (2021-02-04 03:17:55)
> tag 970633 + patch
> tag 932924 + patch
> thanks
>
> Hello,
>
> Eagerly looking forward to tt-rss being in good shape for FreedomBox in
> Bullseye, I have done the packaging work needed for uploading 21.1
> version of tt-rss. Please
Hi Bruno,
Quoting Bruno Kleinert (2021-01-24 06:46:39)
> I looked into /usr/share/sbuild/create-chroot to create a patch, but began to
> wonder where and if that script is actually used. I use sbuild to locally
> build packages on my desktop computer, so it's installed, and
>
> grep -r
1 - 100 of 257 matches
Mail list logo
