Your message dated Tue, 17 Aug 2021 18:02:21 +0200
with message-id <[email protected]>
and subject line Re: Bug#992348: mapserver: please re-enable build of
ruby-mapscript package
has caused the Debian Bug report #992348,
regarding mapserver: please re-enable build of ruby-mapscript package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
992348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992348
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mapserver
Version: 7.6.4-1
Severity: wishlist
Hi Debian GIS maintainers, hi Bas!
tldr: would it be possible to re-enable the ruby-mapscript package
build?
Extended explication: requiring a packaged version of ruby-mapscript
on Ubuntu 20.04 I today basically reverted commits [1] and [2] and
ruby-mapscript built just fine. A quick test showed ruby-mapscript
to work. Then I did the same thing on bullseye and again,
ruby-mapscript build fine.
Questions:
* would it be possible to start building the ruby-mapscript package again?
* I see commit [1] that says "Build Ruby MapScript only for default version",
but it doesn't say why builds for other ruby versions are being dropped.
What was the reason for dropping the build of ruby-mapscript for the
various existing Ruby versions?
* half an hour later there's a commit [2] that drops ruby-mapscript
alltogether. I couldn't find a log of the respective FTBS. But
maybe it doesn't matter any more since it does seem to build just
fine now.
So would it be possible to revert [1] and [2]? Or should I fork the
project on Salsa and file a PR?
Either way: *thanks a lot for maintaining mapserver*!!!
Greetings,
*t
[1]
https://salsa.debian.org/debian-gis-team/mapserver/-/commit/45f6f67e4272122d9d9fa0c49f247d68690c659a
[2]
https://salsa.debian.org/debian-gis-team/mapserver/-/commit/8d14c0fe55e33ef1922ac529e23cbb04776afd9a
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8),
LANGUAGE=de_CH:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
tags 992348 wontfix
thanks
On 8/17/21 5:35 PM, Tomas Pospisek wrote:
> tldr: would it be possible to re-enable the ruby-mapscript package
> build?
While possible, I'd rather not.
> Extended explication: requiring a packaged version of ruby-mapscript
> on Ubuntu 20.04 I today basically reverted commits [1] and [2] and
> ruby-mapscript built just fine. A quick test showed ruby-mapscript
> to work. Then I did the same thing on bullseye and again,
> ruby-mapscript build fine.
Then you are one of the very few actual users of ruby-mapscript.
> Questions:
>
> * would it be possible to start building the ruby-mapscript package again?
>
> * I see commit [1] that says "Build Ruby MapScript only for default version",
> but it doesn't say why builds for other ruby versions are being dropped.
> What was the reason for dropping the build of ruby-mapscript for the
> various existing Ruby versions?
Building for more than one ruby/php/python/etc version requires building
mapserver again, this makes the build time significantly longer for very
little gain during transitions to new interpreter versions.
> * half an hour later there's a commit [2] that drops ruby-mapscript
> alltogether. I couldn't find a log of the respective FTBS. But
> maybe it doesn't matter any more since it does seem to build just
> fine now.
Because popcon showed no actual users of ruby-mapscript keeping the
package around just causes unnecessary busy work. I don't use Ruby nor
ruby-mapscript, but I do have to spend time maintaining those bits in
mapserver.
> So would it be possible to revert [1] and [2]? Or should I fork the
> project on Salsa and file a PR?
Don't bother with a PR, just maintain the fork of the packaging for your
personal repo.
If I could count on your long term commitment on maintaining the Ruby
support in the mapserver package, I might consider merging your changes.
But my experience with onboarding new contributors has been
disappointing, they tend to disappear not long after their work got in
the archive and don't stick around for long term maintenance.
I'm not keen on increasing the amount of packaging I have to maintain
but don't actually use.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
