Bug#933548: transition: gnome-desktop3

On Wed, 02 Oct 2019 at 21:00:29 +0200, Paul Gevers wrote: > If my view of things is > up-to-date and correct, it's the last piece of the puzzle together with > the samba situation (assuming LO will just build on mips64el). If I'm reading the log correctly, we have the remaining issues still

Bug#941854: Does not follow timezone

Package: rsyslog Version: 8.1908.0-1 Severity: normal If a system's timezone is updated, rsyslog doesn't find out about it. Arguably, this only applies to travelling laptops, but rsyslog is the default Debian logger on this, which is why I think this is worthwhile to think about. Many other

Bug#941839: tcp-wrappers: DECLS replacement (musl, rebootstrap) (PATCH)

On Oct 06, Davor Ocelic wrote: > Patch for building tcp-wrappers with musl. Can you explain why this is relevant for the Debian package? -- ciao, Marco signature.asc Description: PGP signature

Bug#824883: bug#824883

On Sat, 6 Jan 2018 19:06:42 +0100 Andreas Bombe wrote: ... I have been working on an update for some time. As you found out, 3.9 is obsolete already and the development has moved to GitHub. The current upstream maintainers are not interested in making releases so I will have to package git

Bug#941853: crypt(3) should be provided by libxcrypt

Package: glibc Version: 2.29-2 Severity: normal The libc implementation of crypt(3) has been deprecated since 2.28. libxcrypt is needed to support modern hashing algorithms. How do you want to coordinate switching to libxcrypt? The libxcrypt implementation is source and binary backward

Bug#941852: pyqt5webengine: please restore python-pyqt5.qtwebengine (which disappeared without a trace)

Source: pyqt5webengine Version: 5.12.1-2 Severity: normal Dear pyqt5webengine maintainer[s], Unfortunately when this package was broken out of pyqt5 the Python 2 bindings for QtWebEngine disappeared without a trace (no changelog entry, no NEWS). This has now caused Bug #941802, and Bug #941806.

Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is available.

The reason it's still there is in the cruft report: - broken Build-Depends: user-mode-linux: linux-source-4.19 Is user-mode-linux maintained? This seems to come up somewhat regularly. Scott K On October 6, 2019 2:37:09 PM UTC, Ben Hutchings wrote: >Control: reassign -1 ftp.debian.org

Bug#941851: gnome-session very chatty, outputs a lot of DEBUG messages to the journal

Package: gnome-session-bin Version: 3.34.0-3 Severity: normal Since the update to a systemd manages gnome-session, I noticed that the journal has a lot of gnome-session debug messages: Okt 06 17:09:05 pluto gnome-session-binary[25218]: DEBUG(+): GsmXSMPClient: xsmp_finalize (0x7f228c003570

Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

I'm still getting the fail-whale for the GNOME Classic session. Tried with a fresh user account, just to be sure. Should this bug report be reopened or should I file a new one? signature.asc Description: OpenPGP digital signature

Bug#941844: Acknowledgement (gnome-shell: gdm fails to start: gnome-shell JS error)

On Sun, 6 Oct 2019 12:38:36 +0100 Simon McVittie wrote: > This is the same bug as #941782. Please upgrade gnome-shell > (and related packages) to the versions in unstable, or downgrade > gir1.2-gnomedesktop-3.0 to the version from buster. Thank you, I can also confirm downgrading fixes the

Bug#931964: Add sid to Vagrant Cloud boxes

Note that the testing VM image is configured with apt pinning, so you can install packages from unstable using e.g: apt install gcc-snapshot/unstable L. On 06/10/19 at 09:47 -0500, Andrew Pennebaker wrote: > My use case is getting some of the very latest applications in like qemu > updates,

Bug#885810: bumping severity of gmpc's use of libunique to Serious

Control: severity -1 serious The Debian GNOME team would like to remove libunique from Debian. Therefore, I'm bumping the severity of this bug to serious. Please see the master bug https://bugs.debian.org/895520 for documentation on moving away from libunique. It looks like it requires porting

Bug#931964: Add sid to Vagrant Cloud boxes

My use case is getting some of the very latest applications in like qemu updates, that aren't necessarily available in the testing repositories. Hmm, maybe we could do a daily VM push and ignore broken states? This would be a "best effort" artifact. > On Oct 6, 2019, at 6:27 AM, Lucas Nussbaum

Bug#941367: RFS: z3 4.8.6-1 -- theorem prover from Microsoft Research

On 10/4/19 11:44 PM, Gianfranco Costamagna wrote: >>My changes are on Salsa (I'll push to the actual repository once somebody has >>given >>me sufficient ("Maintainer") permissions to do so), and also on Mentors: >> >>  https://salsa.debian.org/wolff-guest/z3 >> 

Bug#941720: linux-headers-4.19.0-0.bpo.6-amd64 depends on linux-headers-4.19.0-0.bpo.6-common=4.19.67-2+deb10u1~bpo9+1 but only linux-headers-4.19.0-0.bpo.6-amd64=4.19.67-2~bpo9+1 is available.

Control: reassign -1 ftp.debian.org Control: retitle -1 RM: linux-source-4.19 -- NBS; replaced by linux-source-5.2 I can't fix this because it's a problem with the archive, not the package. The dependency, which is arch-independent, has been auto- built, but the upload of arch-indepdenent

Bug#941850: clamav: inconsistent results with "better zip bomb" reproducers

Package: clamav Version: clamav/0.101.4+dfsg-1 Severity: normal Hi, clamdscan returns surprising results for "better zip bomb" reproducers[0]: * Inconsistent results with zbsm.zip: clamdscan returns different results when run different times. The first time the file is considered sane, the

Bug#941688: marked as done (openssl 1.1.1d security update breaks openssh login on old kernels)

Hi Colin, On Sat, Oct 05, 2019 at 11:14:22PM +0100, Colin Watson wrote: > On Sat, Oct 05, 2019 at 10:58:18PM +0200, Sebastian Andrzej Siewior wrote: > > On 2019-10-05 21:34:22 [+0200], Salvatore Bonaccorso wrote: > > > Or maybe it would be worth as an option to reassign to src:openssh an > > >

Bug#941810: buster-pu: package openssh/1:7.9p1-10

Hi Colin, On Sat, Oct 05, 2019 at 10:39:29PM +0100, Colin Watson wrote: > Package: release.debian.org > Severity: normal > Tags: buster > User: release.debian@packages.debian.org > Usertags: pu > > https://bugs.debian.org/941663 reports an OpenSSH regression on old > kernels prompted by the

Bug#941849: librrds-perl: Cannot install / deleted by apt after perl upgrade to perl 5.30.0-5

Package: librrds-perl Version: 1.7.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? librrds-perl was removed by apt after upgrading to perl 5.30.0-5, after that became uninstallable because it requieres perlapi-5.28.1 * What

Bug#941848: RFS: ukui-control-center/2.0.0-1 -- utilities to configure the UKUI desktop

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ukui-control-center" * Package name: ukui-control-center Version : 2.0.0-1 Upstream Author : hebing * URL : https://github.com/ukui/ukui-control-center *

Bug#941794: pulseaudio: please drop obsolete gconf build-dependency

On Sun, Oct 6, 2019 at 9:42 AM Simon McVittie wrote: > On Sat, 05 Oct 2019 at 15:52:10 +0200, Andreas Henriksson wrote: > > Please remove the obsolete build-dependency on libgconf2-dev. > > > > The package currently already builds with --disable-gconf configure > > flag. I've also test-built the

Bug#941847: libenchant1c2a: Wrong dependency

Package: libenchant1c2a Version: 1.6.0-11.2 Severity: normal Dear Maintainer, Unavailable dependency "hunspell-directory" should be "hunspell-dictionary". Cheers, Itaï. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (600, 'unstable') Architecture:

Bug#939076: firmware-bnx2x: missing firmware: bnx2x/bnx2x-e2-7.13.11.0.fw

Control: tags -1 + patch Hi, On 01/09/19 at 00:51 +0200, Lucas Nussbaum wrote: > Version bnx2x/bnx2x-e2-7.13.11.0.fw is available upstream according to > https://github.com/wkennington/linux-firmware/commit/8fcf0ec44c11f1865f8451c0265e84bf16365312 > but not included in firmware-bnx2x. Attached

Bug#941817: llvm-toolchain-8: FTBFS on x32

On Sun, 6 Oct 2019, Sylvestre Ledru wrote: > guide. About the lto issue, it is fixed in the branch 9 (I am focussing my > time on this branch): I don’t mind working on 9 either, it’s just that some other programs cannot be built at the moment, and if we fix 9 only then these problems pile on

Bug#941817: llvm-toolchain-8: FTBFS on x32

On Sun, 6 Oct 2019, Sylvestre Ledru wrote: >> In the meantime, would you mind changing llvm-defaults to go >> back to version 7 on x32 which while outdated can at least >> build things (like src:v4l-utils) that are now BD-Uninstallable. > >I am afraid we don't have this capability. > >Sorry. OK,

Bug#941794: pulseaudio: please drop obsolete gconf build-dependency

On Sat, 05 Oct 2019 at 15:52:10 +0200, Andreas Henriksson wrote: > Please remove the obsolete build-dependency on libgconf2-dev. > > The package currently already builds with --disable-gconf configure > flag. I've also test-built the package without the libgconf2-dev > build-dependency. I've

Bug#941846: python-h5py: fix upstream MPI tests

Package: python-h5py Version: 2.10.0-1 Severity: normal Control: forwarded -1 https://github.com/h5py/h5py/issues/1364 Upstream tests currently break when run with mpirun. debian/tests/test_file_mpi.py has been created as a workaround to run mpio tests manually. Problem is logged upstream in

Bug#938173: python-sigmavirus24-urltemplate: diff for NMU version 3.0.0+git20181031.68064e2-1.1

Hi Sandro, Sandro Tosi 於 2019年10月6日 週日 上午9:42寫道： > > Control: tags 938173 + patch > Control: tags 938173 + pending > > > Dear maintainer, > > I've prepared an NMU for python-sigmavirus24-urltemplate (versioned as > 3.0.0+git20181031.68064e2-1.1) and > uploaded it to DELAYED/7. Please feel free

Bug#939035: xplanet: Uses GifQuantizeBuffer - stops working with newer giflib

Control: tags -1 patch On 2019-08-31 Andreas Metzler wrote: > Source: xplanet > Version: 1.3.0-5.1 > Severity: important > Hello, > this package uses GifQuantizeBuffer() from giflib. The symbol has been > dropped in giflib 5.2 (libgif-dev/libgif7 5.2.1 is available in > experimental) and

Bug#941845: postgresql-11_11.5-2+b2_s390x.changes REJECTED

Source: postgresql-11 Version: 11.5-2 Severity: serious On 2019-10-06 11:52, Debian FTP Masters wrote: > > > Version check failed: > Your upload included the binary package libpgtypes3, version 11.5-2+b2, for > s390x, > however unstable already has version 12.0-1. > Uploads to unstable must

Bug#931964: Add sid to Vagrant Cloud boxes

Hi, On 12/07/19 at 20:15 -0500, Andrew Pennebaker wrote: > Hey, neat that we have convenient VM's now for Debian! Could we get a VM > for sid as well? That's difficult, because unstable is frequently in a broken state... What is your use case? (and why isn't it met by the testing64 and

Bug#941844: gnome-shell: gdm fails to start: gnome-shell JS error

Control: reassign -1 gir1.2-gnomedesktop-3.0 3.34.0-2 Control: forcemerge 941782 -1 Control: affects 941782 + gnome-shell On Sun, 06 Oct 2019 at 11:38:27 +0100, Jamie Forth wrote: > After a recent full-upgrade, which included the installation of > libgnome-desktop-3-18:amd64 (3.34.0-2,

Bug#941831: gir1.2-gnomedesktop-3.0: 3.34.0-2 causes gdm3 black screen

Control: forcemerge 941782 -1 On Sat, 05 Oct 2019 at 20:37:25 -0700, Ross Vandegrift wrote: > Package: gir1.2-gnomedesktop-3.0 > Version: 3.34.0-2 > Severity: normal > > Dear Maintainer, > > After installing gir1.2-gnomedesktop-3.0 3.34.0-2, gdm3 only displays a black > screen. Downgrading to

Bug#941837: got the same issue, is there some sort of temporary workaround ?

Dear all, Got hit by the same bug while upgrading - Preparing to unpack .../32-texlive-fonts-extra_2019.20190930-2_all.deb ... Unpacking texlive-fonts-extra (2019.20190930-2) over (2019.20190830-1) ... dpkg: error processing archive

Bug#885813: bumping severity of xfce4-notes-plugin's use of libunique to Serious

Control: severity -1 serious The Debian GNOME team would like to remove libunique from Debian. Therefore, I'm bumping the severity of this bug to serious. Please see the master bug https://bugs.debian.org/895520 for documentation on moving away from libunique. It looks like it requires finishing

Bug#895520: bumping severity of gmpc's use of libunique to Serious

Control: severity -1 serious The Debian GNOME team would like to remove libunique from Debian. Therefore, I'm bumping the severity of this bug to serious. Please see the master bug https://bugs.debian.org/895520 for documentation on moving away from libunique. It looks like it requires porting

Bug#885814: bumping severity of lxsession's use of libunique to Serious

Control: severity -1 serious Hi, After about 2 years, I am bumping the severity of this bug to RC. Because lxsession is a "key package", it won't be automatically removed from Testing. From what I can tell, lxsession is the only major package still using libunique. Personally, I was surprised

Bug#936071: /usr/share/pam-configs/unix: nullok_secure tries to read /etc/securetty and generates a warning

Hi, This warning also appear on my system when login is attempted through various programs (login, su, gdm-password, ..). Oct 06 12:37:30 XXX login[9367]: pam_unix(login:auth): Couldn't open /etc/securetty: No such file or directory Oct 06 12:37:40 XXX su[9383]: pam_unix(su:auth): Couldn't open

Bug#941836: blhc: false positive for libtool relink mode?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2019-10-06 at 11:47 +0200, Simon Ruderich wrote: > Now I'm somewhat confused. I think the issue in this case is not > "libtool: relink:" because I get no errors for those lines when > running blhc on the buildd log. > > Instead, I think the

Bug#941844: gnome-shell: gdm fails to start: gnome-shell JS error

Package: gnome-shell Version: 3.30.2-11 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, After a recent full-upgrade, which included the installation of libgnome-desktop-3-18:amd64 (3.34.0-2, automatic), gdm fails to start, with the following gnome-shell

Bug#941843: fitsh FTCBFS: uses the build architecture linker

Source: fitsh Version: 0.9.2-1 Tags: patch upstream User: debian-cr...@lists.debian.org Usertags: ftcbfs fitsh fails to cross build from source, because its configure script detects the build architecture linker using AC_CHECK_PROG. It should be using AC_CHECK_TOOL for ld instead. Please consider

Bug#941838: plymouth: wrecked initramfs after changing theme

On Sunday, 6 October 2019 7:52:00 PM AEDT Laurent Bigonville wrote: > Do you see any specific error? No... The computer is on another continent with unskilled operator... I've got as much information as I could obtain under the circumstances. > Does is boot if you remove the "splash" from the

Bug#941842: RFP: vimoutliner -- script for building an outline editor on top of Vim

Package: wnpp Severity: wishlist * Package name: vimoutliner Version : 0.4.0 (or some more recent git commit...) Upstream Author : Steve Litt , Noel Henson * URL : https://github.com/vimoutliner/vimoutliner * License : mostly GPL-2 with

Bug#941841: Update node-rollup-plugin-babel to 4.x (required for updating babel to 7.x)

Package: node-rollup-plugin-babel Version: 3.0.3-2 Severity: important Control: block 941700 by -1 Please update this package to 4.x version to update node-babel to 7.x

Bug#941836: blhc: false positive for libtool relink mode?

On Sun, Oct 06, 2019 at 11:22:57AM +0200, Yves-Alexis Perez wrote: > Or a “real” build log from the buildd network: > https://buildd.debian.org/status/fetch.php?pkg=strongswan=amd64=5.8.0-1=1566867301=0 Thanks, that's the link I was looking for. > Here's an example: > > libtool: warning:

Bug#941700: [Pkg-javascript-devel] Bug#941700: Update babel to version 7

On Fri, 04 Oct 2019 11:27:58 +0530 Pirate Praveen wrote: > We already started the update work, but since it needs gulp 4, we are stuck > (we are not able to fix gulp 4 errors). Alternatively we could try to skip > gulp. With gulp 4.0.2-3, gulp build [14:53:55] Local gulp not found in

Bug#929811: Port build to gulp 4 (transition coming)

Control: block -1 by 941700 On Fri, 31 May 2019 20:31:55 +0500 Pirate Praveen wrote: > package: node-postcss > version: 6.0.23-1 > severity: important > > gulp 4.0 is now available in experimental. We'd like to upload it to > unstable (after freeze) when all reverse build dependencies are

Bug#941836: blhc: false positive for libtool relink mode?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sun, 2019-10-06 at 10:59 +0200, Simon Ruderich wrote: > sounds sensible. Can I get the relevant parts of the original > build log? Your updated regex won't match the line you pasted > ('libtool: ' vs. '/libtool" --tag CC --mode=relink') and I

Bug#941840: usb.ids: New upstream version available

Package: usb.ids Version: 2019.07.27-1 Severity: wishlist Dear Maintainer, upstream released a new usb.ids file on 2019.10.05 with some ids I contributed. It would be great if we could have it in Debian at some point. Thank you and keep up the good work, Antonio P.S. Would you accept a

Bug#941836: blhc: false positive for libtool relink mode?

On Sun, Oct 06, 2019 at 09:47:11AM +0200, Yves-Alexis Perez wrote: > Package: blhc > Version: 0.09-2 > Severity: normal > > Hi, > > blhc running on salsaci for strongSwan reports failure > (https://salsa.debian.org/debian/strongswan/-/jobs/350397/raw) at the > blhc step because of lines like

Bug#941838: plymouth: wrecked initramfs after changing theme

Le 6/10/19 à 10:35, Dmitry Smirnov a écrit : I've lost remote computer entirely after changing plymouth theme: sudo plymouth-set-default-theme futureprototype sudo update-initramfs -u -k all ("futureprototype" was one of the available themes according to "--list"). That was on

Bug#929829: gulp 4 cannot build node-babel 7 - Cannot convert undefined or null to object

On 2019, ഒക്‌ടോബർ 6 3:38:47 AM IST, Evgeny Kapun wrote: >> [15:37:17] Cannot convert undefined or null to object > >After checking the code, I found the root cause of this error. Awesome! We have been trying to find the root cause for some time. >The error is caused by NPM package

Bug#941839: tcp-wrappers: DECLS replacement (musl, rebootstrap) (PATCH)

Source: tcp-wrappers Severity: normal Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap Patch for building tcp-wrappers with musl. It is the same patch that has been applied by other projects:

Bug#941838: plymouth: wrecked initramfs after changing theme

Package: plymouth Version: 0.9.4-1.1 Severity: important I've lost remote computer entirely after changing plymouth theme: sudo plymouth-set-default-theme futureprototype sudo update-initramfs -u -k all ("futureprototype" was one of the available themes according to "--list"). That was on

Bug#861229: fixed

fixed 861229 0.9.8-2 thanks

Bug#941837: texlive-fonts-extra: file conflice with (older) texlive-fonts-extra-links

Package: texlive-fonts-extra Version: 2019.20190930-2 Severity: serious Hi, when upgrading in Debian testing I saw the following error message: +--- | Unpacking texlive-fonts-extra (2019.20190930-2) over (2019.20190830-1) ... | dpkg: error processing archive

Bug#941793: nmu: libimobiledevice_1.2.1~git20181030.92c5462-1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sat, 2019-10-05 at 15:45 +0200, Yves-Alexis Perez wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu libimobiledevice_1.2.1~git20181030.92c5462-1 . ANY . unstable .

Bug#941833: [Pkg-gtkpod-devel] Bug#941833: ifuse: "Stack smashing detected" error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 control: reassign -1 libimobiledevice control: affects -1 ifuse control: forcemerge 941703 -1 control: forwarded -1 https://github.com/libimobiledevice/libusbmuxd/issues/81 On Sun, 2019-10-06 at 19:26 +1300, Bart Joy wrote: > When running ifuse

Bug#941749: plasma-workspace: System tray not shown and no panel context menu

Good morning everyone, I did an upgrade this morning and it pulled in a bunch of plasma framework packages: libkf5kcmutils-data:all 5.62.0-1 libfontembed1:amd64 1.25.6-1 libkf5calendarevents5:amd64 5.62.0-1 libkf5plasma5:amd64 5.62.0-1 libkf5declarative-data:all 5.62.0-1 libkf5runner5:amd64

Bug#938281: python-xtermcolor: diff for NMU version 1.2.1-2.1

Thanks! I was planning to get around and do it before the next debian release :D Ciao Il giorno dom 6 ott 2019 alle ore 04:55 Sandro Tosi ha scritto: > > Control: tags 938281 + patch > Control: tags 938281 + pending > > > Dear maintainer, > > I've prepared an NMU for python-xtermcolor

Bug#941835: debian-policy: drop mentioning of legacy manual in package description

Package: debian-policy Version: 4.4.1.1 Severity: normal Dear Maintainer, the current package description contains this paragraph: It also replaces the old Packaging Manual; most of the still-relevant content is now included as appendices to the Policy Manual. I'm around a long time and I

Bug#941817: llvm-toolchain-8: FTBFS on x32

Le 06/10/2019 à 02:59, Thorsten Glaser a écrit : On Sun, 6 Oct 2019, Thorsten Glaser wrote: … which is caused by: cc1: error: unrecognized argument to '-flto=' option: 'thin' Somehow, the build system applies -flto=thin to the host compiler, and GCC doesn’t support this flag. This is but

Bug#941836: blhc: false positive for libtool relink mode?

Package: blhc Version: 0.09-2 Severity: normal Hi, blhc running on salsaci for strongSwan reports failure (https://salsa.debian.org/debian/strongswan/-/jobs/350397/raw) at the blhc step because of lines like these: 8890:CPPFLAGS missing (-D_FORTIFY_SOURCE=2): /bin/bash

Bug#938034: python-plumbum: diff for NMU version 1.6.7-1.1

Hi, Am 06.10.19 um 03:26 schrieb Sandro Tosi: > Dear maintainer, > > I've prepared an NMU for python-plumbum (versioned as 1.6.7-1.1) and > uploaded it to DELAYED/7. Please feel free to tell me if I > should delay it longer. thx, looks fine, so if possible feel free to reduce/remove the delay.

Bug#941834: gdm3: Gdm3 display manager break bluetooth audio.

Package: gdm3 Version: 3.22.3-3+deb9u2 Severity: normal How to reproduce this bug. Run from terminal as root $dpkg-reconfigure gdm3 and from window select lightdm restart system. My audio device working good and start wo need to stop/start bluetooth.sevice. Enabling again gdm3 fail to connect on

Bug#941782: Rescue plan

1) I confirm that Jean-Marc's instructions : > 1/ add the stable to your source.list > 2/ sudo apt update > 3/ sudo apt install gir1.2-gnomedesktop-3.0=3.30.2.1-2 > 4/ sudo apt-mark hold gir1.2-gnomedesktop-3.0 were sufficient to recover a functional system. 2) I suggest to mark this bug as

Bug#941833: ifuse: "Stack smashing detected" error

Package: ifuse Version: 1.1.4~git20181007.3b00243-1 Severity: important Dear Maintainer, When running ifuse to mount my iPhone, which is connected via USB, I immediately encounter the following error: *** stack smashing detected ***: terminated Instead of this error, I would have expected my

Bug#835086: Bug#941708: ITP: nextcloud-server -- Nextcloud folder synchronization tool (server)

You should fix the project license on GitLab, right now it's showing all rights reserved. That should be in the project settings somewhere... Also, have you seen ? That appears like it'll eventually allow a non-downloader package.

Bug#941832: RM: delaboratory -- RoM; upstream discontinued, obsolete

Package: ftp.debian.org Severity: normal Hi FTP Masters, As delaboratory is not maintained by upstream for years and popcon is low, there's no reason to keep it in the archives. Especially that this blocks wxwidgets3.0-gtk3 transition. Thanks, Laszlo/GCS

<    1   2