rtkit cannot be silenced by changing log levels, or even by redirecting output
to /dev/null. My
/etc/systemd/system/rtkit-daemon.service.d/log.conf looks like this:
[Service]
MaxLogLevel=3
StandardOutput=null
StandardError=null
...and still rtkit writes reams of junk to the system log. Since it i
bly fixed by this
commit upstream:
https://pagure.io/bind-dyndb-ldap/c/f0d75b778ee7bfd0feb368b51027943085a54705?branch=master
Note that there was a new bind upload since then, so there might be more
breakage...
Cheers,
Ivo
638 and ff.
> >
> Thanks for the pointer. Seems to me that misguided change should be
> reverted.
While that may be true, it might be good to change the test anyway, as it's
unclear if this behaviour can be relied on in the future (especially if
upstream doesn't revert).
Thanks,
Ivo
suitable for a stable release, it shouldn't
be in testing either. I added a block hint to prevent it from coming back
after the release.
Cheers,
Ivo
hat it seems there was a fix for #984579 in the upload to
unstable that isn't included in the upload to experimental. I assume this will
be fixed in the next upload as well.
Cheers,
Ivo
Thanks to Akshay, we
> figured out the new location of lodash-cli and fixed the build.
It seems the RC bug fix is unrelated to the new upstream. Please prepare an
upload based on the version currently in testing that only contains the fix
for the RC bug, not the new upsteam.
Thanks,
Ivo
4+dfsg-4
Please go ahead with the upload to unstable and remove the moreinfo tag from
this bug once the package is ready to migrate.
Thanks,
Ivo
can just
stay in unstable (unfortunately).
Cheers,
Ivo
]. The debdiff for 3.4.5~pre1-4 is at
> [6].
I suggest you upload 3.4.5~pre1-4 to unstable and 3.4.6-1 to experimental. I
haven't looked at 3.4.5~pre1-4 in detail yet, but I suspect it will be fine.
Once it migrates, we can look at 3.4.6-1 again, and by then, the upload to
experimental will at least show us obvious issues in the builds or the ci.
Please remove the moreinfo tag from this bug when 3.4.5~pre1-4 (or something
similar) is ready to migrate.
Thanks,
Ivo
note for the ftp-team:
As mentioned in the other bug report: dak rm show an rdep problem with
ruby-kramdown, but that's not actually the case, because libruby2.7 Provides
ruby-rexml:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986806#46
Thanks!
Ivo
do a libxcrypt upload in a couple
> of days.
OK, thanks!
> I think that I can leave the udeb library in /usr/lib/.
Yes. There is no upgrade issue there, and making sure the udeb doesn't change
avoids potential issues with the installer.
Ivo
Hi Mattia,
On 4/14/21 8:18 PM, Mattia Rizzolo wrote:
On Wed, Apr 14, 2021 at 02:22:54PM +0200, Ivo De Decker wrote:
So, if that's what you think, should I upload an inkscape with a manual
dependency on libpoppler-glib8 >= 20.09.0?
Yes, that would be useful.
I've just u
Control: tags -1 confirmed d-i
Hi,
On Mon, Apr 12, 2021 at 08:54:51PM +0200, Michael Biebl wrote:
> control: retitle -1 unblock: systemd/247.3-5
This look ok. Kibi was already in Cc for the unblock-udeb (the original mail
is quoted below).
Cheers,
Ivo
>
> Am 11.04.21 um 18:48 sch
Hi,
On Tue, Apr 13, 2021 at 06:53:55PM +0200, Mattia Rizzolo wrote:
> On Sun, Apr 11, 2021 at 08:02:20PM +0200, Ivo De Decker wrote:
> > There is a theoretical and a practical aspect to this issue. From a
> > theoretical point of view, the dependency relations should not be st
on't have a repo without a Size field, there should be no risk,
> as none of the code paths should be triggered.
>
> [ Checklist ]
> [x] all changes are documented in the d/changelog
> [x] I reviewed all changes and I approve them
> [x] attach debdiff against the package in testing
>
> [ Other info ]
>
> unblock apt/2.2.3
Please go ahead with the upload and remove the moreinfo tag from this bug once
the package is ready to migrate.
Thanks,
Ivo
Hi Guillem,
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:
> > 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 th
t; ERROR: test-archive.t output changed
> > !# Ret was: 0 (test-archive.t)
I'm pretty sure this is caused by changes in python 3.9.2 and fixed by this
patch from ubuntu:
https://patches.ubuntu.com/m/mercurial/mercurial_5.6.1-2ubuntu1.patch
Cheers,
Ivo
uspect this bug could be fixed by adding a versioned
dependency on python3-minimal to python3-joblib. Cc'ing Graham, who did the
last joblib uploads.
Cheers,
Ivo
st the package in testing
Please go ahead with the upload and remove the moreinfo tag from this bug once
the package is ready to migrate to testing.
Thanks,
Ivo
> See above. This doesn't sound great.
>
> I understand, the timing of this release sucks, and I’ll trust the judgment
> of the release team.
Yeah, neither option sounds very good.
I'm leaning towards accepting it. I suggest you upload it to unstable, and
we'll leave it there for a while. If issues show up (either in unstable or
upstream), we can reconsider it.
I'm tagging the bug moreinfo for now. Please remove that when the upload has
been in unstable for a while.
Thanks,
Ivo
.
Thanks for that! That made the review a lot easier.
> And the git branch is at:
>
> https://git.hadrons.org/cgit/debian/dpkg/dpkg.git/log/?h=next/1.20.8
>
> unblock dpkg/1.20.8
Cheers,
Ivo
st we can do, is to try to fix obvious cases
where we are aware of the issue. In other cases, we'll probably need to
advise our users to do a full upgrade instead of a partial one.
Cheers,
Ivo
he new libpoppler-glib8 fixes the issue.
A way to fix this, is to add a dependency to the newer libpoppler-glib8 as
well (as was done for elpa-pdf-tools-server). Obviously, it would be nice to
have an elegant way to handle this automatically at build time to make sure
the dependencies are correct, without having to add them manually.
Cheers,
Ivo
r than link-time dependencies. So, ugly games with c macros or
> wrappers trying to get some internally typed NIS APIs right.
> I definitely do not have time to develop the patch, although I could
> potentially make time to review and help test.
> I consider this risky for bullseye.
I agree here as well.
> I think my recommendation is go approve the breaks change, and hope that's
> good enough in practice.
OK.
Please remove the moreinfo tag from the unblock bug when the new version is in
unstable.
Thanks,
Ivo
Hi Julien,
Do you have any comment on the merge request Andreas submitted to
ca-certificates, to allow breaking to dependency cycle in
ca-certificates-java (see mail quoted below, from #922981)?
Thanks,
Ivo
On Fri, Mar 19, 2021 at 03:04:35AM +0100, Andreas Beckmann wrote:
> On Thu, 11 Mar 2
Hi,
On Fri, Mar 19, 2021 at 04:52:57PM +0100, Ivo De Decker wrote:
> > > I wonder if all this might be caused by the breaks from libcrypt1 (against
> > > libc6 (<< 2.29-4)). Is there a way to remove the breaks without causing
> > > issues? Maybe this is som
after that).
Cheers,
Ivo
d of the proper version (3.1.2) is being prepared.
Removing a package from unstable and then uploading the same package with a
lower version isn't possible. If you want to go back to version 3.x, you'll
need to do an upload with a version higher than the current one.
Cheers,
Ivo
libcrypt1 from bullseye (which takes over
libcrypt.so.1). Then remove that again. Now libcrypt.so.1 is missing. If the
breaks is present, libcrypt1 can only be installed together with the new
libc6, which prevents you from removing libcrypt1 afterwards.
Cheers,
Ivo
ded to unstable. Maybe an upload to experimental
might allow people to test this more easily?
I Cced the apt maintainers to see if they have other suggestions to get
apt/dpkg to unpack libcrypt1 before libc6.
I wonder if all this might be caused by the breaks from libcrypt1 (against
libc6 (<< 2.29-4)). Is there a way to remove the breaks without causing
issues? Maybe this is somewhat similar to the situation in
https://bugs.debian.org/972936#24: libgcc-s1 takes over binaries from libgcc1,
but only 'replaces' it, without breaks (note that extra steps had to be taken
to avoid further issues (adding Important: yes and Protected: yes)).
Cheers,
Ivo
le and remove the moreinfo tag from
this bug once the builds for the new version are done.
Thanks,
Ivo
le and remove the moreinfo tag from
this bug once the builds for the new version are done.
Cheers,
Ivo
ff between the version in
testing and unstable is very large and unreviewable. It certainly isn't going
to get unblocked like this. If you can provide a filtered diff, with only the
'real' changes, and not the noise generated by the new upstream release,
there's at least a chance we could look at them. Note that this doesn't
guarantee it will be unblocked. There's still a decent chance that the changes
will be too big.
Thanks,
Ivo
command you used to do the filtering.
> [ Other info ]
> If there is any open question regarding this unblock, I'm most happy
> to provide it.
>
> In the changelog unfortunately there is a typo, the new upstream
> versio is indeed 4.9.3, *not* 4.9.1.
As a new upload is needed anyway, you can fix this too.
Thanks,
Ivo
package: src:libgrokj2k
version: 7.6.6-2
severity: serious
tags: ftbfs
Hi,
The latest upload of libgrokj2k to unstable fails on i386:
https://buildd.debian.org/status/package.php?p=libgrokj2k
Cheers,
Ivo
l scenarios.
If a situation occurs where the debian-security-support hook runs on a broken
system, there's no point in trying to do something useful and failing. The
best that can be done is making sure dpkg/apt can continue, hoping that the
breakage will be fixed later on.
Thanks,
Ivo
eport.cgi?bug=964477#41
Finally, I think 964477 should be marked as serious (even though that's purely
cosmetic now, as the bug is fixed).
Cheers,
Ivo
ion
should have happened during the soft freeze is a different matter, but that's
unrelated to this bug).
Testing that the html is valid, and contains certain parts of the input might
be a more useful test.
Cheers,
Ivo
Hi Matthias,
On 2/23/21 1:36 AM, Matthias Klumpp wrote:
[...]
I'll have a look at fixing that.
Thanks for the quick fix!
Ivo
d of all packages in sid, your package failed to build
> on amd64.
Are you aware of this bug? Looking at
https://tests.reproducible-builds.org/debian/history/ldc.html
it seems the change that triggered it must have been uploaded fairly recently
(probaby in January).
Thanks,
Ivo
nd it seems the check wasn't done because the binary changed
from arch: any to arch: all at the same time. This case should probably be
checked in dak as well (obviously also for arch: all to arch: any).
Cloning the bug to track the issue in dak.
Cheers,
Ivo
OK. That's encouraging :)
> I expect to have things sorted soon.
Make sure to let is know if you encounter any issues.
Cheers,
Ivo
Control: tags 978521 pending
Hi Steve,
On Fri, Feb 12, 2021 at 01:35:52AM +, Steve McIntyre wrote:
> On Tue, Feb 09, 2021 at 04:26:02PM +0100, Ivo De Decker wrote:
> >Hi Steve,
> >
> >On Sun, Sep 27, 2020 at 08:39:53PM +0200, Lucas Nussbaum wrote:
> >> During a
> is that my chroot lives on a large tmpfs. Could that pose any problems?
>
> Any other details I could add to help better understand the issue?
There was an upload of nghttp2 yesterday, which built fine on the buildds, so
I'm downgrading this bug.
Cheers,
Ivo
on3-ufolib2, to break the
circular dependency. Once the build is done, the build-dep can be
reintroduced
- manually upload binaries for mipsel and mips64el. Once they are in unstable,
a binNMU can be scheduled to rebuild them on the buildds.
There are probably other ways.
Cheers,
Ivo
?
Cheers,
Ivo
/coffee-script.js").read
end
def tmp_path
It might be useful to replace the match with something else to detect
coffeescript.
Cheers,
Ivo
Hi,
On Fri, Feb 05, 2021 at 01:46:46PM +0100, Ivo De Decker wrote:
> error: 'Access denied for user 'root'@'localhost''
> 2021-01-21 13:20:47 5 [Warning] Access denied for user 'root'@'localhost'
> ERROR 1698 (28000): Access denied for us
anged to make it work under fakeroot. One
option is to start mysqld with --skip-grant-tables to disable permission
checks. This seems to work for many tests, but the tests that actually test
permissions and expect 'permission denied' fail in that case. Maybe it works
when doing a network connection and users with login/pw.
Cheers,
Ivo
etty sure that this is caused by the circular dependency beween
ca-certificates-java, default-jre-headless and openjdk-11-jre-headless, and
isn't actually a bug in yui-compressor
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929685
Cheers,
Ivo
reproduce this issue at all.
>
> Could you try with the new version?
Testing/unstable now has version 2021.01+dfsg-2. Benedikt, could you try this
version to see if the issue is still there?
Thanks,
Ivo
rchive. If not, I'll modify the autopkgtest.
>Ondrej
Testing now has 1:9.16.11-2. I retriggered the tests a number of times earlier
today, and one of them failed:
https://ci.debian.net/packages/b/bind9/testing/amd64/
https://ci.debian.net/data/autopkgtest/testing/amd64/b/bind9/10370897/log.gz
Cheers,
Ivo
ed needed first?
Cheers,
Ivo
change has to be reverted.
>
> What is clear at this point is that the kernel change should be reverted
> in buster since it causes a regression (including build failures on
> buildds). I am cloning this bug for a revert in the kernel of
> https://salsa.debian.org/kernel-team/linux/-/commit/947fbc66183d022fe3de7871dfb262d2b87af826
>
> I am marking the version in bullseye as found since we might run into
> the same problem again when buster DSAs will be built on machines
> running the bullseye kernel after the release of bullseye. It might be
> possible to mitigate this problem (e.g. in the kernel or by keeping some
> buildd running with the buster kernel), but without an open bug this
> issue might get forgotten and then resurface after the bullseye release.
Could the mips porters comment on this? Given that we're close to the release
of bullseye, I'm not convinced it's a good idea to change this now.
Cheers,
Ivo
@Base 0.6.0
> > mct_restrict_applications_dialog_build_app_filter@Base 0.6.0
> > mct_restrict_applications_dialog_get_app_filter@Base 0.6.0
> > mct_restrict_applications_dialog_get_type@Base 0.6.0
> > dh_makeshlibs: error: failing due to earlier errors
> > make: *** [debian/rules:7: binary] Error 25
Could you take a look at this, to fix the build?
Thanks!
Ivo
Control: tags -1 patch pending
Hi Colin,
On 2/8/21 11:56 PM, Colin Watson wrote:
On Mon, Feb 08, 2021 at 07:17:57PM +0100, Ivo De Decker wrote:
On Sat, Nov 21, 2020 at 07:06:02PM +0200, Tzafrir Cohen wrote:
On abel in a armel chroot the issue is reproduced by running:
man -Thtml
, what do
you think? Obviously, it would be nice to have a fix for bullseye.
Cheers,
Ivo
the build seems to
succeed (my tests where done with /bin/sh pointing to dash).
Cheers,
Ivo
Control: severity -1 important
Control: tags -1 - moreinfo unreproducible
Hi Bastian,
On Mon, Feb 08, 2021 at 02:22:31PM +0100, Bastian Blank wrote:
> On Mon, Feb 08, 2021 at 10:12:14AM +0100, Ivo De Decker wrote:
> > I tried a rebuild of git 1:2.28.0-1, 1:2.29.2-1 and 1:2.30.
you still reproduce this issue? And are you able to reproduce it on a
porterbox?
Cheers,
Ivo
Control: tags -1 patch
Hi,
On Wed, Oct 28, 2020 at 01:28:26AM -0400, Sandro Tosi wrote:
> forwarded 973168 https://github.com/PyCQA/pylint/issues/3895
> thanks
It seems upstream adjusted the tests to work with python 3.9.
Cheers,
Ivo
x/svntogit-packages/commits/packages/qt-gstreamer/trunk
Cheers,
Ivo
>From 6e4fb2f3fcfb453c5522c66457ac5ed8c3b1b05c Mon Sep 17 00:00:00 2001
From: George Kiagiadakis
Date: Sat, 7 Sep 2019 10:49:38 +0300
Subject: QGst/caps: compilation fix from
https://bugs.kde.org/show_bug.cgi?id=406676#c2
ks/pull/64/commits/9e08ea995a0353ae78470c344b68fcefa38b64b3
Ahmed, I noticed you are working on a new upstream version in git. However, it
FTBFS in the ci. Would you consider doing an upload based on the current
version, with only the pdf fix? Or do you prefer an NMU?
Thanks!
Ivo
error. However, the
> resultant object doesn't actually work (yet).
Oh. In that case, I'll remove the patch tag, because the (current) patch
doesn't actually work correctly.
> I'll upload it iff I can get something working before the freeze dates.
OK, thanks for you work on this. If this doesn't work out, please send an
update to the bug.
Cheers,
Ivo
cible-builds tests, while others do not. So the issue doesn't show up
in all cases. Maybe it's related to the type of filesystem used.
https://tests.reproducible-builds.org/debian/history/plexus-io.html
Cheers,
Ivo
48b0f5049990
Gordon, are you planning to upload this soon? The soft freeze is pretty close
now.
Thanks!
Ivo
-usrmerged systems).
Obvious patch to fix this attached.
Cheers,
Ivo
diff -Nur lvm2_2.03.11-2/scripts/blkdeactivate.sh.in lvm2_2.03.11-2i/scripts/blkdeactivate.sh.in
--- lvm2_2.03.11-2/scripts/blkdeactivate.sh.in 2021-01-08 09:10:11.0 +
+++ lvm2_2.03.11-2i/scripts/blkdeactivate.sh.i
can be removed by disabling the
em-synchrony tests (and updating the coverage settings). Maybe that should be
done, to allow em-synchrony to be removed from bullseye?
Cheers,
Ivo
ent error. The following address(es)
> > failed:
> >
> > deb...@jrms.com.ar
> > Unrouteable address
>
I noticed you fixed this in git. Are you planning to do an upload soon?
Thanks,
Ivo
aren't allowed anymore with gcc 10. Just removing them fixes this.
The attached patch does both and fixes the FTBFS.
Thanks,
Ivo
--- mdocml-1.14.4.orig/compat_err.c
+++ mdocml-1.14.4/compat_err.c
@@ -2,7 +2,7 @@
#if HAVE_ERR
-int dummy;
+//int dummy;
#else
--- mdocml-1.14.4.or
Hi,
On Mon, Feb 01, 2021 at 08:07:02PM +0100, Carsten Schoenert wrote:
> Am 01.02.21 um 19:33 schrieb Ivo De Decker:
> > There are 2 packages that depend on arduino-core:
> >
> > Output from dak rm:
> >
> > Checking reverse dependencies...
> > # Broken Dep
ed
to be updated to have the right dependency. Otherwise, they will have to be
removed (at least from testing), as they would become uninstallable if
arduino-core goes away.
However, given the timing of the freeze, it might be better to reintroduce
arduino-core as a transitional package, and deal with the removal after the
bullseye release.
Cheers,
Ivo
fixed by this upstream change:
https://www.mercurial-scm.org/repo/hg/rev/88dfe1c279bb
Cheers,
Ivo
new upstream version doesn't remove the code masking the systemd units.
It just changes it a little. So it doesn't fix this bug.
I don't know if there's already an upstream bug describing the issue, but that
might be needed to get the bug resolved upstream.
Cheers,
Ivo
package: webext-exteditor
version: 2.0.4-1
severity: serious
Hi,
Thunderbird 1:78.7.0-1 has 'Breaks: webext-exteditor (<= 2.0.4-1)', which
means webext-exteditor doesn't work with it.
Cheers,
Ivo
processing:
python3-extractor
E: Sub-process /usr/bin/dpkg returned an error code (1)
https://piuparts.debian.org/sid/fail/python3-extractor_1:0.6-8.log
Cheers,
Ivo
package: src:trapperkeeper-scheduler-clojure
version: 1.1.3-3
severity: serious
tags: ftbfs
Hi,
The latest upload of trapperkeeper-scheduler-clojure to unstable fails on all:
https://buildd.debian.org/status/package.php?p=trapperkeeper-scheduler-clojure
Cheers,
Ivo
;s inform the kylin-video team that we're about to remove
> crystalhd from bullseye.
>
> @kylin-video team, please drop your Build-Depends on libcrystalhd-dev
> and your Depends on libcrystalhd3. If this doesn't happen in a week or
> two, kylin-video will be removed from bullseye too.
Cloning the bug to track the RC issue in kylin-video.
Cheers,
Ivo
/mk-netbsd. It looks like this
failure might be fixed by moving those files to that directory.
Note that the failure was detected in version 2.2.2-1.1, currently in
unstable, but version 2.2.2-1 contains the same files, so I'm filing it
against that version.
Cheers,
Ivo
package: src:qdjango
version: 0.6.2-3
severity: serious
tags: ftbfs
Hi,
The latest upload of qdjango to unstable fails on the buildds:
https://buildd.debian.org/status/package.php?p=qdjango
Cheers,
Ivo
endency, I suggest to
> remove it from Debian
If you want the package removed, you should probably file an FTP removal bug.
Cheers,
Ivo
the frr test (or the frr package), I'm
reassigning the bugs there.
Cheers,
Ivo
IUI, the binaries for the newer version are broken.
I guess the only way to express that in the BTS is to clone the bug and
reassign one clone to the source in testing and unstable, and leave the other
one assigned to the binary in unstable.
Cheers,
Ivo
ang-google-cloud 976507
> jctools 976534
> jnr-ffi 976521
> libcereal 976585
> libmiglayout-java 976546
> multiboot 976502
> nova 976590
> python-fluids 976558
> python-ptrace 976468
> rapidjson 976536
> xenium 976480
> xfonts-100dpi 976571
> xfonts-75dpi 976471
> xfonts-cyrillic 976510
Cheers,
Ivo
package: src:debian-reference
version: 2.76
tags: bullseye sid ftbfs
severity: serious
Hi,
It seems debian-reference build-depends on libopencc2-data, which no longer
exists.
Cheers,
Ivo
package: src:xserver-xorg-video-ati
version: 1:19.1.0-2
severity: serious
tags: ftbfs
Hi,
The latest upload of xserver-xorg-video-ati to unstable fails on mips64el,
mipsel:
https://buildd.debian.org/status/package.php?p=xserver-xorg-video-ati
Cheers,
Ivo
package: src:xserver-xorg-video-amdgpu
version: 19.1.0-2
severity: serious
tags: ftbfs
Hi,
The latest upload of xserver-xorg-video-amdgpu to unstable fails on mips64el,
mipsel:
https://buildd.debian.org/status/package.php?p=xserver-xorg-video-amdgpu
Cheers,
Ivo
I added some hints to finish this, and now libindicator and libappindicator
are no longer in testing.
Thanks!
Ivo
t/bc7899393898a328d92392f80845d622620c8c14
Ivo
failed to build
> on amd64.
The patch from ubuntu seems to fix the build.
Cheers,
Ivo
diff -pruN 0.0.2-5/debian/changelog 0.0.2-5ubuntu2/debian/changelog
--- 0.0.2-5/debian/changelog 2014-09-02 10:37:53.0 +
+++ 0.0.2-5ubuntu2/debian/changelog 2020-09-01 01:29:48.0 +
@
sked for the
default setting to be different. Downgrading.
Cheers,
Ivo
> If one installs the example snap hello-world and launches hello-world.evil in
> apparmored system the application is NOT strictly confined by default.
>
> ~$ snap run hello-world.evil
> Hello Evil World!
package: nbdkit
severity: serious
version: 1.22.3-1
Hi,
The latest version of nbdkit build-depends on libtorrent-rasterbar-dev. As
libtorrent-rasterbar is no longer in testing, this prevents migration to
testing.
Cheers,
Ivo
changed the
mail script to avoid sending mail on the first day. When a new version
migrates, this should prevent a mail from being sent in the first 24 hours.
By the time those are passed, the bug status and the autoremoval info should
be up-to-date.
Please let me know if this doesn't solve the mail issue.
Thanks,
Ivo
Control: reopen -1
On Thu, Apr 02, 2020 at 01:33:36PM +, Debian FTP Masters wrote:
>* Update libstdc++6 symbols file for armel. Closes: #954954.
It seems the issue is still present in 10.2.0-6.
Thanks,
Ivo
On 7/10/20 8:57 PM, Mike Gabriel wrote:
Hi Ivo,
Hi Mike,
I have asked for white-listing some days back. I have pinged Philipp
Kern explicitly once more (he white-listed
php-horde-javascriptminify-jsmin just the other day...).
I will close this bug, once the white-listing is in place. I am
and
non-free are allowed to migrate to testing.
Thanks,
Ivo
ndencies that are not
satisfiable in testing, but are satisfiable by from unstable. Only the
last one was kept (uvloop in this case). I submitted a fix for this issue:
https://salsa.debian.org/release-team/britney2/-/merge_requests/47
Ivo
package: vrms
Hi,
Please consider changing the name of this package and removing the reference
to RMS. As the description says, the package isn't based on the opinions of
RMS, but on the DFSG.
Thanks,
Ivo
Control: severity -1 serious
Control: retitle -1 don't ship automake-1.15 in bullseye
Hi,
On Thu, May 28, 2020 at 09:34:18AM -0700, Vagrant Cascadian wrote:
> On 2020-02-04, Vagrant Cascadian wrote:
> > On 2019-01-12, Ivo De Decker wrote:
> >> On Wed, Sep 19, 2018 at 0
i-bin/bugreport.cgi?bug=959828
Cheers,
Ivo
1 - 100 of 1240 matches
Mail list logo
