Bug#844449: bluefish: Bluefish immediately crashed

[Daniel Leidert]

severity 89 important
tags 89 + moreinfo
thanks

Am Dienstag, den 15.11.2016, 21:37 +0100 schrieb Peter Schütt:
> 
> Bluefish crash very often immediately.

Can you please install the debugging symbols and run bluefish from
within a gdb session and attach any backtrace you get to this report?
You'll find a more detailed explanation at [1]. The information you
provided is not sufficient enough. Further I'm downgrading severity as
I have no information, that many or most bluefish users are affected.

[1] https://wiki.debian.org/HowToGetABacktrace

Regards, Daniel

signature.asc
Description: This is a digitally signed message part

Bug#1030846: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Hi Steve,

I believe that your fix to grub2 in Sid is not enough to handle
#1030939/#1030846.

This problem breaks e.g. vmdb2. I can no longer create a Bullseye
system image with vmdb2 on Sid, because the grub-install step in the
Bullseye chroot now fails, because the created filesystem (created with
e2fsprogs on Sid) cannot be recognized by grub. I have to downgrade
e2fsprogs to the version in Testing to get the build going again. It
also means that a Bookworm system can never be used to format and
debootstrap a Bullseye or Buster system that requires a grub
installation.

I guess that the fix applied to grub2 in Sid would have to be applied
to grub2 in Bullseye as well (and basically to any grub2 package in any
Debian or Ubuntu or Raspbian release supported by debootstrap).

This situation is really messy. It breaks basically all my image builds
with vmdb2.

Regards, Daniel


signature.asc
Description: This is a digitally signed message part

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote:
> > Hi Steve,
> > 
> > I believe that your fix to grub2 in Sid is not enough to handle
> > #1030939/#1030846.
> > 
> > This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> > system image with vmdb2 on Sid, because the grub-install step in the
> > Bullseye chroot now fails, because the created filesystem (created with
> > e2fsprogs on Sid) cannot be recognized by grub.
> 
> I'm confused, why does using vmdb2 on *sid* involve running
> grub-install on a *bulleye* chroot?

My workstation is running Sid. I want to create an image for Bullseye
(in this case using vmdb2, but I could do it manually as well). First,
one creates the paritioning and the filesystems for the target system
with the tools provided by the host system. This involves running the
unfortunate version of e2fsprogs with the breaking change. Then, one
installs the base system with deboostrap (also from the host system)
into the created partitions/filesystem. Then one (bind-)mounts the
virtual filesystems into the target systems, does a chroot into it, and
then one finishes the installation inside the chroot, including running
grub-install.

This is standard and common behavior. I have never ever seen in my
whole life someone to use grub2 from Sid to make a grub-install for a
Bullseye target. I have not even seen anybody suggest that.

Consider another example: Server providers use GRML or Bookworm with
e2fsprogs 1.47.0 as their rescue system. Now people are no longer able
to create a Bullseye system using the deboostrap method [1]. If the
host system uses e2fsprogs 1.47.0 or above and the target system for
[1] uses a grub without a fix, then this no longer works.

[1] https://www.debian.org/releases/stable/amd64/apds03

> That seems to be extremely ill-advised.

I'm sorry? I think you are completely missing the point.

> If you are trying to install a bullseye system, why
> can't you using vmdb2 on bullseye?

Because I am using Sid and because I use features of vmdb2 which are
not available in the version in Bullseye. And this feature breaks vmdb2
and similar tools. It also breaks a standard way of installing Debian
systems.

> And if you are trying to install a sid or bookworm system using vmdb2,
> why can't you (or vmdb2) use a sid or bookworm chroot for doing the
> grub-install?

What are you talking about? You basically break the toolchains and then
you suggest to do non-standard stuff to handle this or even avoid doing
installations of affected systems?!

> > I guess that the fix applied to grub2 in Sid would have to be applied
> > to grub2 in Bullseye as well (and basically to any grub2 package in any
> > Debian or Ubuntu or Raspbian release supported by debootstrap).
> 
> I can understand why we need to keep things synchronized so that a
> debian installer for Bookworm be able to generate a bootable system
> using the version of grub and e2fsprogs in Bookworm.
> 
> But a generalized requirement that we be able to use debootstrap and
> vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
> seem to be reasonable.

You are completyl wrong. This breaks a standard way of installing any
system supported by deboostrap with a grub without a fix to deal with
this version of e2fsprogs. This isn't just about vmdb2.

What you are saying is ignorant.

If this isn't cared about, then this version of e2fsprogs shouldn't
make it into Bookworm. We are in the middle of a freeze and this breaks
toolchains and a standard way (see [1]) of installing Debian.

Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
> > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> 
> ...
> 
> > > But a generalized requirement that we be able to use debootstrap and
> > > vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
> > > seem to be reasonable.
> > 
> > You are completyl wrong. This breaks a standard way of installing any
> > system supported by deboostrap with a grub without a fix to deal with
> > this version of e2fsprogs. This isn't just about vmdb2.
> > 
> > What you are saying is ignorant.
> > 
> > If this isn't cared about, then this version of e2fsprogs shouldn't
> > make it into Bookworm. We are in the middle of a freeze and this breaks
> > toolchains and a standard way (see [1]) of installing Debian.
> 
> Sorry Daniel, but I have to (mostly!) agree with Ted here. If you're
> creating an image of an older release using newer tools then you'll
> need to be aware that sometimes the newer tools will create things
> that don't work there. If there's a bug here, I would strongly argue
> that it's in vmdb2. deboostrap (for example) includes some
> release-specific knowledge to cope with issues like this.

debootstrap does nothing related to grub. So it is a bad example. Again
I refer to [1]: If the host system contains the problematic e2fsprogs
and the target system doesn't contain a grub with the fix [2], then
this breaks installations. This breaks older systems *and* current
systems. For example, I neither see the necessary grub patch in both
Ubuntu 20.04 and 22.04 either. So they also cannot be installed using
the deboostrap method and the toolchain in Sid (and Bookworm if
e2fsprogs makes it there). 

[1] https://www.debian.org/releases/stable/amd64/apds03
[2] Even "our" grub only contains a patch and not an upstream version
with support. So how can you even expect the target system to contain a
fix and be able to handle the created filesystem?!

Whe whole handling is completely wrong here. First, grub should have
been fixed upstream. And the change in e2fsprogs should have been done
only after "fixed" grub versions had settled. If we do it the other way
around, we have to patch grub in affected distributions as well. And
for Debian that means at least to patch Bullseye and any other release
we want to be able to install from Bookworm. I even a lot of companies
using Buster still.

> If we don't allow for this kind of change, that wouldn't allow us to
> *ever* make breaking changes in some packages, and that's just not
> sustainable.

I'm critizicing the way of handling that breaking change and the
ignorance shown reagarding the impact, not that fact that there is a
breaking change. And it breaks a lot! This doesn't affect just a few
minor use cases. It affects the basic way of installing a clean Ubuntu
or Debian (or derivative) on a remote server using the debootstrap
method.


And again: We are in the middle of a freeze here. And e2fsprogs pushes
a breaking change that is not even handled by any existing grub
upstream release, and is also not properly handled within Debian?!

Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 14:58 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote:
> 
> 
[..]
> Breakages happen like this,

This breakage is *unnecessary* and it breaks at the momnent *all*
debootstrap installations except for doing a bookworm/sid installation
themselves. That is just stupid.

Get down from your high horse and ackknowledge the problems your
behavior causes.

> and this has happened before in similar
> circumstances.

No it has not. You are doing a breakage on purpose during a freeze
period while the transition period is over. Do it with a proper
transition during the next release cycle.


> > 
[..]
> > Whe whole handling is completely wrong here. First, grub should have
> > been fixed upstream. And the change in e2fsprogs should have been done
> > only after "fixed" grub versions had settled. If we do it the other way
> > around, we have to patch grub in affected distributions as well. And
> > for Debian that means at least to patch Bullseye and any other release
> > we want to be able to install from Bookworm. I even a lot of companies
> > using Buster still.
> 
> And I know of folks still working on Stretch and Jessie. How far back
> do you want to tie things??

How about staying on topic and explaining, why this transition is
necessary and has to be done the wrong way around, instead of picking
the fact that older systems still exist? You break almost *all*
installation right now. You also broke an Ubuntu 20.04 or 22.04 LTS
installation. Are they new enough?

[..]
> > 
> > I'm critizicing the way of handling that breaking change and the
> > ignorance shown reagarding the impact, not that fact that there is a
> > breaking change. And it breaks a lot! This doesn't affect just a few
> > minor use cases. It affects the basic way of installing a clean Ubuntu
> > or Debian (or derivative) on a remote server using the debootstrap
> > method.
> 
> People using these tools need to be aware of the potential issue. What
> would happen if you ran debootstrap with a filesystem that the target
> distro doesn't know how to mount at all, for example?

That is different from introducing a breaking change for which no grub
upstream release has a fix yet. So basically the only system able to
handle a filesystem created with e2fsprogs 1.47.0 is Sid right now. Can
you please ignore your ego and see the problems you are causing?

You push a breaking change for no reason at all. What is the gain here
compared to the issues you are causing?

> > And again: We are in the middle of a freeze here. And e2fsprogs
> > pushes
> > a breaking change that is not even handled by any existing grub
> > upstream release, and is also not properly handled within Debian?!
> 
> Grub upstream is already known to be problematic in terms of release
> cycles.

That is not enough and it is not a solution for the problem. There is
*no* grub version out there supporting this, except for the patched
version is Sid. Is this the sign for a working transition?

> We now know about this particular issue (thanks Ted!) and
> we've fixed it in unstable (and soon testing).

Which helps exactly nobody, as it still breaks all other Debian or
Ubuntu installation.

I cannot belive that you intentionally break one of the standard
methods to install Debian or Ubuntu for no reason at all and without a
proper transition. Version 1.47.0 of e2fsprogs contains nothing
necessary for Bookworm. I'll bring this to the attention of the release
team. I'm sick of your ignorance. Do a proper transition and don't
start it during a freeze.


Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 12:34 -0500 schrieb Theodore Ts'o:
> 
[..]
> In any case, a version of grub that will support the csum_seed feature
> will be landing in Bookworm in just a few days.  So at that point,
> you'll be able to create VM images for Bookworm and Sid that will work
> with the e2fsprogs in sid.  The current plan of record is that it will
> only be at that point that e2fsprogs will be allowed to migrate into
> Bookworm.

As soon as this version hits testing, you have successfully disabled
the last working environment to use vmdb2 to create images of Ubuntu
and Debian. As soon as this version hits Testing, one then can no
longer build images for either any Ubuntu release nor Debian Bullseye
or older. I can then only build images for Bookworm and Sid. Please
think about that.

You *seriously* break the debootstrap method of installing Debian or
Ubuntu. vmdb2 ist just another tool that is broken by now, a tool that
I use very often. I explained the impacts of what you are doing often
enough now. By now the impact should be clear. And you are still not
dealing with the aftermath of your intended action?! You haven't done a
proper transition. You haven't given any affected toolchain the
necessary time to adopt. You haven't documented how to disable that
breaking change when creating filesystems for distributions where grub
does not support this (there is not even a NEWS entry). You haven't
even announced that breaking change. And yet you are going to break one
of our two standard methods of installing Debian or Ubuntu. How is any
of what you have been saying so far addressing any of these issues? 

> [..]
> By the way, in the case of the csum_seed feature, it's pretty
> straightforward to just run "tune2fs -O ^metadata_csum_seed
> /tmp/boot.img".  If the UUID has been changed since the file system
> was created, you'll have to do this while the file system is
> unmounted
> and it will take a few seconds, but that's almost certainly not the
> case with vmdb2.

Well, how do you intend to distribute that information, so people who
have to use the deboostrap method to install a Debian or Ubuntu release
with a grub not supporting csum_seed (basically all existing releases,
except for the upcoming Bookworm) know that?

I do not understand why you are pushing 1.47.0 over 1.46.6, which you
had uploaded just five days before the former. You haven't even
presented a reason yet.

Regards, Daniel

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Package: release.debian.org
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

A week ago, Theodore Ts'o uploaded e2fsprogs 1.47.0 into Debian unstable. This
version contains a unannounced change that basically breaks grub2 (and
grub-install). This issue has been reported as #1030939 [1] and #1030846 [2].
To "fix" the issue, instead of turning the feature off, a patch to grub2 in Sid
has been committed recently. Unfortunately, that only fixes grub in Sid. Grub
in Bullseye or any current Ubuntu release *cannot* deal with a filesystem
created by this version of e2fsprogs. This basically breaks the debootstrap
method of installing a Debian or Ubuntu. If e2fsprogs 1.47.0 is allowed into
Testing, we can no longer use the debootstrap method to install a Debian
Bullseye (or older) or any Ubuntu release. It requires to manually change the
filesystem features before it can be used again. It also makes e.g. vmdb2 in
Sid unusable to create images of Bullseye or older Debian releases, or Ubuntu
releases.

The gain of enabling the metadata_csum_seed feature by default is not
noteworthy. It is a feature that hardly anybody needs. I have not seen one
use-case nor even relevant search hits. But the loss is heavy. User's can no
longer simply follow [3] to install any Debian or Ubuntu system if the
filesystem has been created with e2fsprogs 1.47.0. It also breaks software in
the midst of the freeze.

I hereby ask the release team to step in and either make sure that the
metadata_csum_seed feature is not turned on by default in e2fsprogs in Bookworm
or that version 1.47.0 is not shipped as part of Bookworm.

Reasons:

- - this breaks existing tools for no apparant reason

- - introducing this breaking change is too late in the release cycle to deal
  with it properly

- - the metadata_csum_seed feature is hardly useful or requested; it can be
  turned on if necessary; no need to make it the default in Bookworm

- - there is no grub upstream release with support for it; only patched grub
  versions can cope with it

- - the change makes it impossible to create filesystems with this version of
  e2fsprogs and then run a grub-install from a target system that does not cope
  with that feature; basically breaking the debootstrap method of installing
  Debian or Ubuntu onto a server (violating #4 of the Debian social contract)

- - to cope with the former issues, users will have to know about that
  incompatibility and ways to deal with it; none of that is prepared; the
  package maintainer even refuses a NEWS entry

- - it breaks vmdb2, only allowing to make images of Debian Bookworm and Sid (if
  grub is involved)

- - pushing this metadata_csum_seed feature violates #4 of the Debian social
  contract

Instead, turning on this feature should be postponed for the next release cycle
where a proper transition can be done.

[1] https://bugs.debian.org/1030939
[2] https://bugs.debian.org/1030846
[3] https://www.debian.org/releases/stable/amd64/apds03

Daniel Leidert

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPsE8UACgkQS80FZ8KW
0F0Aug/+Kb6xrQcILq+VYpKk/161UXgQA47ccydz78uT3r1eRBVJIPReULZPdjvk
W4PDDOYypScsx4+EahdOVViAMiOyzI0eroivZmDItxY1HR6LpKdeQFPLET6FdbfM
pDHezFKXqsulYQWLu5M6yPCtMWGCmAtiH9NeppzUY7+dnBr2yzZGitH4pPSh7MmS
9jxRIKG0xGa3wF+a1yEgHE0nPvqD5a97GlwL5+MTg580k/e1VRpaQaYrTRr3CHyK
EJbVOu70K+qXgP837x6B5eyYmihJWiNBMxm9JqF1TrwTKXwk26zpZ2+T1uKVgVKj
Y5AlZX8Gypdxq0Q3uFPSlzBhetd2wvrUt9hKEb52fdzw3L4AsY2Ken98sAhqy7Xi
PGVdihiUSAT5gslthm3qB3fGQQMIEXI3UdHqSx7ARgZJ6Gkf/zIjk5sKl/xiGe+t
jJExPdCR7H8+tPNZhJEhx6BLtLs8tLm+zhOAr3rZVekEn3PJJAHOKPs1KPBWinYr
FsVBsWBWzOgKNARu31u/o4s5BFV99M45gZqHLs3Mp5TvJqIxkbwS0FDoCa/TausP
vojuW4kDPM7Jjw568W4O8csXBiI/qEcEPXZGPrgGVs3Yo1hV/KkJUOkQ9y/VvRps
POx+RwF400ov8zOxGPqETkqDjl/2JQ47OOvogJMi6FDRQk+YE2w=
=bKh7
-END PGP SIGNATURE-

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 16:53 -0500 schrieb Theodore Ts'o:

[snip]

Your arrogant and ignorant attitude is frustrating, to say the least.
You don't care about the mess you create, for a feature, that probably
only a handful of people will ever need (I did a quick search and
didn't find anything regarding this feature - so why turn it on by
default then?). But yet you have to make it the default and break
running toolchains and methods. Talking to you is pointless. You cost
me hours of useless work yesterday and today because you ignore the
rules we have set out as a project to not frustrate each other.

I have reported this to the release team now.

Daniel

Bug#1031395: tzdata 2022g-3 removes /etc/timezone while other packages depend on it, breaking these packages

[Daniel Leidert]

Package: tzdata
Version: 2022g-3
Severity: critical

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

in version 2022g-3, the /etc/timezone file has been removed and gets purged
from user's computers. This makes unrelated software break that relies on this
file. Examples are samizdat and ruby-et-orbi. But codesearch.d.o shows more
code-snippets that rely on the existence of that file. There hasn't been any
announcement, any transition, nor any mass-bug filing, leaving multiple
packages broken at this stage. I reported that issue to the release team as
#1031376 and have been asked to open a bug report against tzdata.

Regards, Daniel

- -- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.82

tzdata recommends no packages.

tzdata suggests no packages.

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPuJ/gACgkQS80FZ8KW
0F2CPQ/+M+A8ok4famSAdTA6Tpjw+ydaYGO2E4+NoQy/diq8KKhFMiOOdduiQji4
6J8no1J7K00eEPgqBko3lQXDJByDuRKHWXD3NFmQJme/pL9Wf4yc7+Zx4QhaBI96
UuUV4M8khv89bA9Bb6TWGUD0OkEOgpze7HAZAQqc8gnaGA2yRkh3JC9DmHe9boQJ
ywODuoFmlPIgyv+Jx8KlXgGdZWWoJpQtm8ol21WeYRtAWxPL+b/FbC1rTrSSEgka
wmw+pa4VbKC8sQIyGQPbJJk0q3PTIqKu1ia59KGKSrCox4cfAvV3EccgyH1xYliI
BRrlSEG1mau1O8jz4fq7oqMVs6W/KMRuj+pSI4n5DEFU9tEJ2G3trysusnS531tj
L++pD/aWISx76rpVzizVQjw1J63pr9sK8sh9/s/jz4s3Ddwiij/HVMaA6t7X+2DU
I3O8jgUq4N6taWw7NcBLDSyFRESqc0BcZYwfsvD7DD0UHSUeZmE5PnetHVWLwqeg
O/ljWDNuIiB61DfVWJr5nfhKXOZYFWXJEOOwDQ5zxWviHlahEGsu3wOQLGW7OA9E
bKUO2IpAOMHX0Oxx752t9eParFqs2yfAX338PGC73w7dCIB5bVowD9SHRCJi6FRX
8HhD5hgq8SsuJEej0eBS63QqN3uqxZKbZsoQgA5aS3eMffxEPRM=
=i0wy
-END PGP SIGNATURE-

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Am Donnerstag, dem 16.02.2023 um 18:37 +0200 schrieb Adrian Bunk:
> On Wed, Feb 15, 2023 at 12:05:41AM +0100, Daniel Leidert wrote:
> > ...
> > Reasons:
> > ...
> > - - the change makes it impossible to create filesystems with this version 
> > of
> >   e2fsprogs and then run a grub-install from a target system that does not 
> > cope
> >   with that feature; basically breaking the debootstrap method of installing
> >   Debian or Ubuntu onto a server (violating #4 of the Debian social 
> > contract)
> > ...
> > Instead, turning on this feature should be postponed for the next release 
> > cycle
> > where a proper transition can be done.
> > ...
> 
> Daniel, you are contradicting yourself when claiming that a change that 
> would allegedly violate the Debian social contract could be done in the 
> next release cycle.

Actually, I'm not. I have never said that I reject the introduction of
that change. But I reject it in the current situation, and I reject the
way it is handled. And if you read the whole report and the discussion
I was involved in, then maybe you can understand that I perceive it
that both, Steve and Theodore, were very well with the idea of breaking
with Bullseye and Ubuntu and other systems, where grub doesn't support
that feature, right now and "just like that". And I think this is a
violation of #4. I have also written in [1] how I think the transition
should be handled (IMO), especially given the fact that grub has no
upstream release with a fix yet.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030939#108

Regards, Daniel

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Am Donnerstag, dem 16.02.2023 um 20:10 +0200 schrieb Adrian Bunk:

[..]
> I am currently spending time trying to summarize the situation and open
> questions, and I am a bit underwhelmed by the inaccuracies and lack of
> technical detail in your emails.

Well, I didn't have weeks to prepare. I had <24 hours and gave you
already enough information so you did not have to start from scratch.

I will summarize my points at the bottom.

> The instructions you cite in [1] are for installing bullseye from
> non-Debian systems.

That is simply not true. Those are general instructions, they are not
limited to non-Debian systems. Most server providers have exctly *one*
rescue system from where I can do a clean installation with deboostrap
(and that even usually is a Debian). I cannot choose to use one that
hasn't an e2fsprogs that has this breaking change enabled. Say for
example, grml, used by multiple providers I know as rescue system and
based on Debian, picks up Bookworm with e2fsprogs with that change. Now
users trying to install anything other than a Debian Bookworm using the
deboostrap method will run into the situation that "grub-install" will
fail, and it won't even indicate that they will have to tune the just
created ext4 filesystem or even change /etc/mke2fs.conf. I spent a few
hours until I tracked it down. And the situation right now is, that I
can simply install any system with the deboostrap method. I'm not aware
that there are any breakages or incompatibilities.

> What bookworm ships does not matter much there,
> these instructions will be wrong as soon as some *other* distribution
> like Fedora changes the default.

Fedora isn't used much as a rescue system, don't you think? Have you
ever encountered that? I do custom server setups with deboostrap for
almost two decades now. I haven't seen any distribution so far that
changed the created filesystem to be incomatible with grub-install from
the systems that might be installed. Most of the rescue systems were
Debian based, JFTR.

> I am wondering how exactly your often repeated "there is no grub 
> upstream release with support for it" would be relevant in practice.
> Whether it's 2.06-8 or 2.07-1 in bookworm shouldn't make a difference.

You completely miss the point here. It would lead to exactly the same
situation if 2.07 would be the *first* to support it and could be
shipped with Bookworm as long as e2fsprogs makes this breaking change
now. But it makes a huge difference if 2.07 with a fix is released in
around the same time as Bookworm and can spread until Trixie is
prepared and the breaking change is postponed to Trixie. Ubuntu 24
would have picked up that fix by then. 22 and maybe even 20 would
probably have picked it up either. Even bullseye could get a patch to
deal with that. The breakage would have less impact than it has now,
while nothing is prepared.

And it is completely illusional to say that people should first create
a Bullseye chroot to then do a deboostrap setup of a target system from
that chroot, as Theodore suggested. Well, I'm more than underwhlemed by
suggestions like this.

> Sebastian has now created #1031364 for your original vmdb2 problem, 
> everyone discussing in #1030939 seems to have missed that tools in 
> bookworm creating images for < bookworm must handle such changes.
> That's not different from debootstrap having code to handle 
> apt-transport-https being required in some older releases.

I agree. So don't you think introducing this now is a really bad
timing?

I checked a search engine to find out what this feature even does.
Turns out, there were less than 500 hits. It is a feature available
since kernel 4.4 and not widely used nor default. So what is the gain
here? I also tried to understand why our users would need to be able to
change the UUID of the filesystem. In 20 years with Debian, I haven't
encountered a situation where this has been necessary (I didn't even
know that one could). My gut feeling is, that this feature is only
useful to a handful of people. I haven't heard any explanation so far
why this needs to be turned on by default just now. The whole
discussion so far has been Theodore argueing why he doesn't care about
his actions and why he doesn't have to.

If this feature should be turned on, then I still think that doing this
for Trixie is the better choice. The tools affected can be fixed to
work around the issue. The other distributions can pick up the grub-
install fix.

And JFTR: The attitude I preceived since I got into the discussion with
the simple sentence that fixing grub in Bookworm might not be enough,
can be summarized as "I/we don't care". So, sorry, I care, even if my
less excellent mails might be underwhelming for you.

Daniel

Bug#1031441: Relax oauth2 dependency

[Daniel Leidert]

I just rebuilt ruby-github-api by relaxing the dependency on oauth2. I
pulled the test cases from github to check if anything happens. It
built just fine. 6 tests failed, but none related to OAuth2 (seems some
keywords/options mismatch).

I think we could fix this by relaxing the dep on oauth2 for now.

There is an upstream report asking for supporting oauth2 2.x at
https://github.com/piotrmurach/github/issues/386.

Regards, Daniel

Bug#1030966: marked as pending in ruby-jekyll-remote-theme

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1030966 in ruby-jekyll-remote-theme 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:

https://salsa.debian.org/ruby-team/ruby-jekyll-remote-theme/-/commit/bf744b6d951229f6ba0c1455454345cf59a6a01d


Enable tests accessing the internet only if internet is available

  * d/ruby-tests.rake: Revert a debugging commit that enabled tests by default
that access the internet (closes: #1030966).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030966

Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

[Daniel Leidert]

Source: ruby-jekyll-remote-theme
Version: 0.4.3-3
Severity: serious
Forwarded: 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package fails to build right now with jekyll-github-metadata 2.15.0. The
culprit seems to be

https://github.com/jekyll/github-metadata/commit/a771d0d7457a7bff42b129ce0bed70c74514a506

The issue has been forwarded to

https://github.com/benbalter/jekyll-remote-theme/issues/98

Regards, Daniel

- -- System Information:
Debian Release: bookworm/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPwtkgACgkQS80FZ8KW
0F2IUg//R+DwQrb/S78zLPMtd3eL/6Xl7rF0lrubOnakzRhWj0zykVxzQq1iFgX0
6BrTARWOK2XDTZOTWB4+4FhPuhZd1SPiyC6XDg/PSBCZb+blyyhG/zY7X7p9faPm
GbWSq6QIo470HEVwC4E5crDdIWEG4ApLocEX2A7+GbJeb0tbXGxI0A6HrkxnILJr
5aqds/+5D842QU0Tro+otAeMvM+jPffk6vY8tgRDzxGf8X8HU4oBYQeoPeoczrc9
fr4M6yrGKZ3gPleLHijktUsza8yUFaQKZwTalbesQfxfAdwKdLKS05Uv+wQPz3w8
79Z09ZLK4b1XqU4njQYPRWrr8WOFGqzkWaF0g2qGlwdZXQv3bcWhug6PGoP+A2/M
ehYGjry1kldPzXBhRZKFAJsk90zcQbmmqlZ6uiwMa8gtoQhX5JEMebPJ+iFk+PSt
U3aKQSXdsp2ey6jAwjkuOf+OWfTB+YVVvzwKs6hecdM7DkSye3Qh9Dw4GyYg7lh+
KxyKJf4NSdmkaOIBYdOBwtYdIId4krg+um5nJSfE9D8xOafvGbkvsialfz2WBOuv
+3CQQbuVcYYOrY3NM9gRT5cvem+kals67n9gITsr87QXH10s3tbijTvpl2vf5fZk
bid9XIIpQMIOfo1QryLqbRCj4r/Y083p9YSULQvjyN40OIxTaGc=
=woiX
-END PGP SIGNATURE-

Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

[Daniel Leidert]

Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk:

[..]
> FYI:
> 
> The package in bookworm builds with jekyll-github-metadata 2.15.0:
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ruby-jekyll-remote-theme.html
> (the buildinfo link has the complete package list)

That is due to this environments not running the failing test. The
test-file checks if there is an internet connection and adds or removes
tests depending on the outcome). The test in question is one that
requires an internet connection.

The package currently doesn't build in a Bookworm nor a Sid chroot if
the test in question is running. I can also reproduce the issue in a
chrooot with a Ruby-only environment. It has already been forwarded to
upstream, and I might simply revert the commit in jekyll-github-
metadata 2.15.0 that is causing this regression, or disable this one
test for now.


Regards, Daniel


signature.asc
Description: This is a digitally signed message part

Bug#1031548: FTBFS with ruby-jekyll-github-metadata 2.15.0

[Daniel Leidert]

Am Sonntag, dem 26.02.2023 um 16:57 +0200 schrieb Adrian Bunk:
> On Sun, Feb 26, 2023 at 03:47:49PM +0100, Daniel Leidert wrote:
> > Am Samstag, dem 25.02.2023 um 16:15 +0200 schrieb Adrian Bunk:
> > 
> > [..]
> > > FYI:
> > > 
> > > The package in bookworm builds with jekyll-github-metadata
> > > 2.15.0:
> > > https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/ruby-jekyll-remote-theme.html
> > > (the buildinfo link has the complete package list)
> > 
> > That is due to this environments not running the failing test. The
> > test-file checks if there is an internet connection and adds or
> > removes
> > tests depending on the outcome). The test in question is one that
> > requires an internet connection.
> > ...
> 
> Accessing the internet during the build is an RC bug.

It would be pretty stupid to generally disable tests for a *remote
theme* plugin (or any other package) that by defition relies on the
internet. This would disable the majority of tests here. We (as in "the
Ruby team") instead handle the tests if there is no internet, and
whenever possible, run them via autopkgtest (needs-internet
restriction) at least.

IMHO this is a valid approach and in this case spotted a regression. To
my understanding, builds must not fail due to access attempts and the
build itself must not rely on downloaded resources. However, this is
the test stage, not the build stage. But if you feel that strongly
about that, please show me the exact ruling. It won't change the fact
though, that this package will fail autopkgtest anyway due to a
regression.


Daniel

Bug#1032221: cryptsetup: libgcc_s.so.1 must be installed for pthread_exit to work

[Daniel Leidert]

Booting an older kernel/initrd and then downgrading libargon2-1 to the
version in Testing and updating the initrd resolves the situation for
now. Thanks to Kai and Guilhem.

Regards, Daniel


signature.asc
Description: This is a digitally signed message part

Bug#1031441: Potential RM candidate ?

[Daniel Leidert]

Am Mittwoch, dem 15.03.2023 um 21:19 +0530 schrieb Pirate Praveen:
> On Mon, 13 Mar 2023 23:17:02 +0530 Mohd Bilal  
> wrote:
>  > Hello,
>  >
>  > The upstream[1] for ruby-github-api has been inactive for over 2 years
>  > now and this is affecting other packages like ruby-oauth2[2] and
>  > ruby-faraday[3] from migrating.
>  >
>  > $ reverse-depends -b ruby-github-api
>  > Reverse-Build-Depends
>  > * ruby-jeweler
>  >
>  > $ reverse-depends -b ruby-jeweler
>  > No reverse dependencies found
>  >
>  > So should we remove these 2 packages ? or as a workaround we could relax
>  > the versions in Gemfile to actually fix this bug since the Debian source
>  > doesn't ship the upstream test suite.
> 
> I think we can remove these two packages.

I agree. Without migrating github-api to oauth2, IMHO/AFAIR it is also
dysfunctional right now.

JFTR: The upstream author is still very much active on github, just not
working on that gem, it seems.

Regards, Daniel

Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed

[Daniel Leidert]

Hi,

Am Mittwoch, dem 29.03.2023 um 18:42 +0200 schrieb Dominique Dumont:
> 
> Turns out that Perl module Net::SMTP supports SSL since 2014 [1], but
> bts still use Net::SMTPS which is an old wrapper around Net::SMTP.
> 
> I've patched bts to use Net::SMTP instead of Net::STMPS and I can
> connect to Daniel's server:

I'm really sorry for not getting back earlier. I was just too busy.


I'll test the updated package asap.

Thank you so much for working on this.

Regards, Daniel

Bug#1011445: marked as pending in ruby-license-finder

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1011445 in ruby-license-finder 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:

https://salsa.debian.org/ruby-team/ruby-license-finder/-/commit/c8a2a2c0bed2b9f683068eb4c635ddad8891ec96


Conflict with ruby-gitlab-license-finder

  * d/control: Declare a conflict with ruby-gitlab-license-finder
(closes: #1011445).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1011445

Bug#1005631: marked as pending in ruby-handlebars-assets

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1005631 in ruby-handlebars-assets 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:

https://salsa.debian.org/ruby-team/ruby-handlebars-assets/-/commit/4a863d6cb4532d68be3d1548bbfbd58dec6e598c


Fix tests with Ruby HAML 6

  * debian/patches/0005-Fix-syntax-for-ruby-haml-6.patch: Add patch.
- Fix syntax for Ruby HAML 6 (closes: #1005631).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005631

Bug#1026479: marked as pending in ruby-faraday-middleware

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1026479 in ruby-faraday-middleware 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:

https://salsa.debian.org/ruby-team/ruby-faraday-middleware/-/commit/c67c1a2471b6796fd410a95d224abae7dea3114c


Fix build

  * d/control (Build-Depends): Add ruby-safe-yaml (closes: #1026479).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1026479

Bug#1005625: marked as pending in ruby-gettext-i18n-rails-js

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1005625 in ruby-gettext-i18n-rails-js 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:

https://salsa.debian.org/ruby-team/ruby-gettext-i18n-rails-js/-/commit/965b8125b594ce2b5af01e712051ccbb5c2787f2


Fix FTBFS

  * d/clean: Add file and drop override_dh_clean.
  * d/control (Build-Depends): Bum debhelper to version 13.
  * d/rules: Work around new rubygems limitation and copy assets for build
stage and symlink them afterward (closes: #1005625).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005625

Bug#1019681: marked as pending in samizdat

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1019681 in samizdat 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:

https://salsa.debian.org/ruby-team/samizdat/-/commit/fbf5ddcf6f78951a53353880e02463b13e08b519


Fix FTBFS

  * d/control (Build-Depends, Depend): Depend on ruby-whitewash with Psych fix.
  * debian/patches/0003-Fix-compatibility-with-Psych-4.patch. Add patch.
- Use YAML.unsafe_load() because YAML.load() changed to YAML.safe_load()
  in Psych 4, leading to a FTBFS with errors like: Psych::DisallowedClass:
  Tried to load unspecified class XXX (closes: #1019681).
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1019681

Bug#959393: [DRE-maint] Bug#959393: ruby2.7 breaks diaspora-installer autopkgtest: sh: 1: bundle: not found

[Daniel Leidert]

Am Freitag, den 01.05.2020, 21:20 -0300 schrieb Antonio Terceiro:
> Control: reassign -1 libruby2.7
> Control: found -1 2.7.0-6
> 
> On Fri, May 01, 2020 at 09:12:57PM -0300, Antonio Terceiro wrote:
> > Control: reassign -1 ruby2.7
> > Control: found -1 2.7.0-6
> > 
> > On Fri, May 01, 2020 at 10:23:56PM +0200, Paul Gevers wrote:
> > > Using system bundler...
> > > Installing gems with rubygems ...
> > > sh: 1: bundle: not found
> > 
> > libruby2.7 now has some Provides: for libraries builtin to the standard
> > library, including ruby-bundler. But since ruby-bundler also provides a
> > `bundle` binary, which libruby2.7 does not, then this Provides: is not
> > really correct.
> > 
> > Instead, libruby2.7 should depend on ruby-bundler, like it already does on
> > rake, ruby-test-unit and others, and not provide it.
> 
> It's on libruby2.7, not ruby2.7

The binary is in ruby2.7. IMHO our approach should be:

- ship a symlink /usr/bin/bundle -> /usr/bin/bundle2.7 with ruby(-defaults),
- handle the symlink via dpkg-divert if ruby-bundler gets installed, and
- keep the provides in libruby2.7.

Regards, Daniel

___
> Pkg-ruby-extras-maintainers mailing list
> pkg-ruby-extras-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#985033: debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license

[Daniel Leidert]

Source: coderay
Version: 1.1.3-3
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It seem the coderay sources are now licensed under the MIT license and not
under the LGPL license. debian/copyright seems to be outdated and wrong here.

Regards, Daniel


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmBKthsACgkQS80FZ8KW
0F387w//ezc1er6Hv8c7swmmwgK8XfokzAcxFbktXyIsUOwN+s2fKlFwjinFkArU
PP8lOe7qzB2vB5eol19vofYdDzJoOqo/RCzsS+Q8Rm3gUzcyTF2pIeubzlNqZMf2
KMYaERHnfrGlLklcOzt+x8JfRvmxS2MAFHNLBuws0k9yISdWfW36DeCFiz0Miqik
VrPAaWMRFUzaqnH3lXEoi342OomkDq2wmx7YnqRd4ESHTWdpAY5b9dC8r6tCnynj
zcspt/0uPnXBKKPuBKXsucBoLr80te+x/7DZ/iLILAbIdEZ+o1jzCu3pCRXQUFdK
vNOnwaBVhDl9aciXTrj1ocbNS1shximlu6vJMaMTB5MXVNt5ph691jazr6bYXjn2
MZU8EK5fkPnYIkX3DOGGZMjuQ5wMN55Z3Udgf+pUE9oXDprc+0vxuLmq6UtLrHKy
uQm/WOd3Fj+r71s5zaRqlf7gShQU2oV23/4PLWC84nswoGkZTnk9yj5X4tw+HdfS
82+iOGayRny2a+EkglGT4IvOvXSdPnXnucjronzpf6s5kw/JP9BRyyF85AWM87q2
6zjycLQo+j3xh3CV4jgNC9pRC6yUTj5YsxnYPIM7v0YWgQBwEzAz6JLBMU/2zEvO
JRHm+XskHA+U6PsV4ccyA4m7zEKPsV10xRrqrZhQekf96BvaQ8Y=
=GfoC
-END PGP SIGNATURE-

Bug#947529: marked as pending in gnome-chemistry-utils

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #947529 in gnome-chemistry-utils 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:

https://salsa.debian.org/debichem-team/gnome-chemistry-utils/-/commit/4bbcaec102cbf34c6ea0e3951234e978178ad155


Replace gnome-doc-utils by yelp-tools

  * d/control (Build-Depends): Replace gnome-doc-utils by yelp-tools.
  * d/*.install: Fix the help path and remove the scrollkeeper path.
  * d/patches/use-yelp.patch: Add patch (closes: #947529).
- Rewrite source to use yelp-tools instead of gnome-doc-utils.
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947529

Bug#973133: marked as pending in ruby-jquery-ui-rails

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #973133 in ruby-jquery-ui-rails 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:

https://salsa.debian.org/ruby-team/ruby-jquery-ui-rails/-/commit/885eddaa8c0a41d980a4bb06665a3555b4996f2b


Fix the link creation to jquery-ui and fix the FTBFS

  * d/rules (override_dh_auto_build): Fix the link creation after
node-jquery-ui changed from /Usr/lib to /usr/share (closes: #973133).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973133

Bug#974014: Fails to install due to depending on ruby-rails < 6.0

[Daniel Leidert]

Package: diaspora
Version: 0.7.9.0+dfsg-4
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

While investigating the other RC issue I discovered that diaspora is
uninstallable in Sid:

The following packages have unmet dependencies:
 diaspora : Depends: ruby-rails (< 2:6.0) but 2:6.0.3.4+dfsg-1 is to be 
installed

Regards, Daniel


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages diaspora depends on:
ii  bc1.07.1-2+b2
hi  bundler   2.1.4-2
pn  diaspora-common   
pn  fonts-roboto-hinted   
ii  imagemagick   8:6.9.11.24+dfsg-1+b1
ii  imagemagick-6.q16 [imagemagick]   8:6.9.11.24+dfsg-1+b1
ii  libruby2.7 [ruby-json]2.7.2-3
ii  nodejs12.19.0~dfsg-1
ii  rake  13.0.1-4
ii  ruby  1:2.7+2
pn  ruby-active-model-serializers 
pn  ruby-activerecord-import  
pn  ruby-acts-as-api  
pn  ruby-acts-as-taggable-on  
ii  ruby-addressable  2.7.0-1
pn  ruby-asset-sync   
pn  ruby-autoprefixer-rails   
pn  ruby-backbone-on-rails
pn  ruby-bootstrap-sass   
pn  ruby-bootstrap-switch-rails   
pn  ruby-carrierwave  
pn  ruby-chunky-png   
pn  ruby-configurate  
pn  ruby-devise   
pn  ruby-devise-lastseenable  
pn  ruby-devise-two-factor
pn  ruby-diaspora-federation-json-schema  
pn  ruby-diaspora-federation-rails
pn  ruby-diaspora-prosody-config  
pn  ruby-entypo-rails 
pn  ruby-eye  
ii  ruby-faraday  0.17.3-1
pn  ruby-faraday-cookie-jar   
pn  ruby-faraday-middleware   
pn  ruby-fog-aws  
pn  ruby-gon  
pn  ruby-hamlit   
pn  ruby-handlebars-assets
pn  ruby-http-accept-language 
pn  ruby-i18n-inflector-rails 
pn  ruby-jquery-rails 
pn  ruby-jquery-ui-rails  
pn  ruby-js-image-paths   
pn  ruby-js-routes
ii  ruby-json 2.3.0+dfsg-1+b3
ii  ruby-json-schema  2.8.1-2
pn  ruby-leaflet-rails
pn  ruby-logging-rails
pn  ruby-markdown-it-html5-embed  
pn  ruby-markerb  
ii  ruby-mini-magick  4.10.1-1
pn  ruby-mobile-fu
ii  ruby-nokogiri 1.10.9+dfsg-1+b1
pn  ruby-oauth2   
pn  ruby-oembed   
pn  ruby-omniauth 
pn  ruby-omniauth-oauth2  
pn  ruby-omniauth-tumblr  
pn  ruby-omniauth-twitter 
pn  ruby-omniauth-wordpress   
pn  ruby-open-graph-reader
pn  ruby-openid-connect   
ii  ruby-pg   1.2.3-1+b1
pn  ruby-rack-cors
pn  ruby-rack-google-analytics
pn  ruby-rack-piwik   
pn  ruby-rack-rewrite 
pn  ruby-rack-ssl   

Bug#974144: Fails under wayland and fails trying to select a window

[Daniel Leidert]

Package: kazam
Version: 1.4.5-4
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I tried kazam. First the errors shown on the command line clearly indicate that
it is not supposed to work with wayland:

(kazam:89108): Wnck-WARNING **: 16:47:15.482: libwnck is designed to work in 
X11 only, no valid display found
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 
111, in cb_button_press_event
screen.force_update()
AttributeError: 'NoneType' object has no attribute 'force_update'

This can be fixed by calling the program with the X11 backend set:

$ GDK_BACKEND=x11 kazam

(JFTR: If either libwnck or kazam is designed to work with x11 only it should
call gdk_set_allowed_backends() at some point).

But even after setting the backend it is impossible to choose a window:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 
116, in cb_button_press_event
if win.is_visible_on_workspace(workspace) and win.is_in_viewport(workspace):
TypeError: Argument 1 does not allow None as a value

The program actually looks pretty dysfunctional for me at this point. I don't
think this should be shipped with the next stable.

Regards, Daniel


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.18.1-1
ii  gir1.2-gstreamer-1.0 1.18.1-1
ii  gir1.2-keybinder-3.0 0.3.2-1+b1
ii  gir1.2-wnck-3.0  3.36.0-1
ii  gnome-session-canberra   0.30-7
ii  gstreamer1.0-plugins-base1.18.1-1
ii  gstreamer1.0-plugins-good1.18.1-1
ii  gstreamer1.0-plugins-ugly1.18.1-1
ii  gstreamer1.0-pulseaudio  1.18.1-1
ii  python3  3.8.6-1
ii  python3-cairo1.16.2-4+b1
ii  python3-dbus 1.2.16-4
ii  python3-gi   3.38.0-1+b1
ii  python3-gi-cairo 3.38.0-1+b1
ii  python3-xdg  0.26-3

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1.18.1-1

kazam suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qt0QACgkQS80FZ8KW
0F1lvQ//ZjHU323yYl2h77L0u5vD/9tpkDxF0nutm892nRHPEEkiJ3coiXDWCTHg
h2jY+lI7a6MwdcQRwYjF9kub2HAVAy4nJAjjOIjhsr8+R1OCSgsrwFhD3g7LBWrT
ermP3XuEUuzteY3L5Y3MYgZsyL+a8o+zsMteDeNX0WiFT5UPNvEwnk7Dbwji8FtU
UyVVdy+H0MdO8+DGC/WgAqbQOX9YMDakDSp45obgwDbjHzp0vIPHzi+wWNoJP/VF
0xxFWpt3Mru8yXLZVpqVK541Bm+HYaWW9qOC78ndV/5tK+OC7S/B3ElSaaL2zmaU
kwS9x+vGxpqCS38jr2ymGepurkJ3JoFyhSQn7yjnpqeDjbYcWjX/dDQtJes2LVHy
gPHabH5G12FPOcp/vIr8HGKdTbYrZCjGjnFxbqNQR0gHkty1gf0tmY60bx//F33I
AkXqMmFAJST3u9c4SMKDVTDxLsGT/PrIeCGoJF61BXbiwF6ic/AaVKRJtZV+wvLw
/HVIkNXRV4Q5+R6ALcESLxO4v98WlQFhXMlzPz6gBQMYmWWDe+7LhiETEjKAW7/X
VhgQFK7RJ34bMP2zgILD1QOCbyILryYImtt9URjdVz1KQJfi71IN9WkZsex+fxBW
0U7IeyL1dJOgkTnZ6sCkugg/ZWK5SxFcPm/YDpgE8Id/EwNYvD4=
=X7HN
-END PGP SIGNATURE-

Bug#982059: And another file conflict: /usr/share/man/de/man1/killall.1.gz

[Daniel Leidert]

And yet another file conflict with manpages-de:

[..]
dpkg: error processing archive /var/cache/apt/archives/psmisc_23.4-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/man/de/man1/killall.1.gz', which is also in 
package manpages-de 4.2.0-1
[..]

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#966575: grub-pc: Bailing out if the boot device from the debconf database does not longer exist might produce a more complicated issue

[Daniel Leidert]

Hi Colin,

I recently stumbled into this issue myself. Reading your explanation was very
helpful. However the way you fixed it produces another issue as described here:

https://forum.openmediavault.org/index.php?thread/37903-grub-related-error-on-5-5-23-update/

The command suggested by the error message (dpkg-reconfigure) actually doesn't
work if grub-pc is not fully installed. I don't have a technical solution
myself, but bailing out creates an even worse situation here. Maybe instead of
bailing out print a warning instead?

I was also thinking: If this cannot be handled in a technical way this should
definitely be mentioned in the release notes.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#966575: grub-pc: Bailing out if the boot device from the debconf database does not longer exist might produce a more complicated issue

[Daniel Leidert]

Am Donnerstag, dem 11.02.2021 um 21:09 + schrieb Colin Watson:
> On Thu, Feb 11, 2021 at 09:34:31PM +0100, Daniel Leidert wrote:
> > I recently stumbled into this issue myself. Reading your explanation was
> > very
> > helpful. However the way you fixed it produces another issue as described
> > here:
> > 
> > https://forum.openmediavault.org/index.php?thread/37903-grub-related-error-on-5-5-23-update/
> > 
> > The command suggested by the error message (dpkg-reconfigure) actually
> > doesn't work if grub-pc is not fully installed.
> 
> Hm, it's true that's not entirely ideal, sorry.  I think I'd probably
> meant to recommend an interactive run of "dpkg --configure grub-pc", but
> I'll need to think about how to present that best.  Your reply on that
> thread seems slightly overkill - there should be no reason to drop to
> low priority, since the relevant questions are asked at critical.

I didn't check the priority. But I only see two possible actions to take after
the installation bailed out: either run "apt-get install -f" and enforce a
debconf frontend, or preset the value using debconf tools.

> > I don't have a technical solution myself, but bailing out creates an
> > even worse situation here.
> 
> For context: every single time the GRUB core <-> modules ABI has changed
> in the last ten years or so, we've had multiple critical bugs filed due
> to unbootable systems as a result of incorrect configuration causing the
> boot loader to be only half-upgraded.  I entirely disagree that a failed
> upgrade, even on many systems, is a worse situation than that.

"Worse" in the sense of that the upgrade bails out and the presented command
doesn't work. I wasn't just talking about the bailing-out part.

The user just needs a way to fix things when this issue is detected.

[..]
> > I was also thinking: If this cannot be handled in a technical way this
> > should definitely be mentioned in the release notes.
> 
> I'm not opposed to some kind of mention in the release notes, I suppose,
> but it feels like more of a general operations manual sort of thing (for
> example, it might happen on the next upgrade after a subtly-botched disk
> swap), and I'm not sure where would be best.  This isn't particularly
> specific to any one Debian release.

Large parts of the document are not specific to any one Debian release. Almost
all advice given in section 4 applies to upgrades in general. Maybe add a
section similar to 4.6 and call it "Upgrading grub (and related packages)"?


Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#981847: ArgumentError: invalid byte sequence in US-ASCII

[Daniel Leidert]

Am Donnerstag, dem 04.02.2021 um 20:56 +0530 schrieb Ritesh Raj Sarraf:
> 
> During a rebuild of the package on Bullseye, the package fails in one of
> the tests. Below is the failure snippet. The same is also seen in the
> Reproducible Builds reports.
> 
> ```
> [  194s] 
> ---
> [  194s] 107 tests, 152 assertions, 0 failures, 1 errors, 0 pendings, 0 
> omissions, 0 notifications
> [  194s] 99.0654% passed
> [  194s] 
> ---
> [  194s] 23.20 tests/s, 32.95 assertions/s
> [  194s] rake aborted!
> [  194s] Command failed with status (1): [ruby -w -I"test"  
> "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb"
>  "test/block_test.rb" "test/dyna_symbol_key_test.rb" "test/parser_test.rb" 
> "test/safe_op_test.rb" "test/trace_test.rb" "test/test_core_ext_helper.rb" 
> "test/test_helper.rb" -v]
> [  194s] /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in 
> `'
> [  194s] Tasks: TOP => default
> [  194s] (See full trace by running task with --trace)
> [  194s] ERROR: Test "ruby2.7" failed. Exiting.
> [  194s] dh_auto_install: error: dh_ruby --install 
> /usr/src/packages/BUILD/debian/ruby-power-assert returned exit code 1
> [  194s] make: *** [debian/rules:6: binary] Error 25
> [  194s] dpkg-buildpackage: error: debian/rules binary subprocess returned 
> exit status 2
> ```

Can you please provide the log file? The error mentioned in the subject
actually doesn't appear in the log snippet.

Reading the subject it might be a LANG-related issue and maybe we need to set
the environment to C.UTF-8 for the tests. Can you check if setting

ENV['LANG'] = 'C.UTF-8'

in debian/ruby-tests.rake fixes the issue?

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#974147: Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead

[Daniel Leidert]

Package: gtk-recordmydesktop
Version: 0.3.8-4.1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The application fails to start in Sid due to /usr/bin/python not existing
(anymore). I've asked on the #deian-python channel and got told that using
/usr/bin/python is a bug and when using python2 you have to use
/usr/bin/python2 instead.

Regards, Daniel


- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gtk-recordmydesktop depends on:
ii  python   2.7.17-2.0tails1
ii  python-gtk2  2.24.0-5.1+b1
ii  python2.72.7.18-1
ii  recordmydesktop  0.3.8.1+svn602-1.1

gtk-recordmydesktop recommends no packages.

gtk-recordmydesktop suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qu+UACgkQS80FZ8KW
0F1s+BAAg+mpqVdtDmpr/tKXVc0INTotSQuoKGi+5jbUHYDS1hbD8yIYHe6u0buy
cRpJ4xQ1+A5humvFv1H2XtktVA6MG14tSxdC9oc3xuJm1AfDcRSp4JhjwWj9o9iw
7sjGBsE1GopdrQlQFiITnYoUwZ4kOciIEwOwGPb0bQq1iEKLkfanjLArdBrMSCE+
9DuYeAN38BJXj+SsfNKv2xUTo4pxum+vDLqAebtI3HTS+VGgPP8SRQjtICx6EDV/
YgStQHVu8i1kZepFCiL3bcd4ACZIvJDNEpTCVgKiAoSfxSwNmsU8ztmxZPBT/vhD
f6xKTmzzYd9a6jQzmISs59fug0pUq8Vj/ET7HfwzlR559+nVa82jmJnoYQbLZRZF
d+ALQ+OzsU69NVhlsM871B7zxvfn1eQGwRCZpnlOCC24KTRWqKI7qFi7sDDSBwr8
QywZjcz+Omh9EWMTIWJ9MYiAUE2hyEWIi8vi4nT0lM3pFXKAJ/lKIFhIn7ZQGDsP
LbXzUjwhV8jS48bmtxFHhPIF7AOMbL37NMOY1ZtowMcW9OrIU3CfESFOkGyneHnJ
Sonzu8xxvhng+D+Sqd6q8uQRMAX06JfPjBqnSmUkHmu5CITCEAaWER9OfPeK0ns/
IPvpUJgcv/GrkT2AiglJOUjLHLOYUvcsygri+DmP88XifaL2IVg=
=NnaI
-END PGP SIGNATURE-

Bug#840680: dirmngr: Dirmngr not always responding

[Daniel Leidert]

Package: gnupg
Version: 2.1.15-4
Followup-For: Bug #840680

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

I'm also affected. For the time being: `killall dirmngr' seems to help.
Unfortunately I didn't get any useful output setting the log level yet;
will try to provide some.

Regards, Daniel



- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnupg depends on:
ii  gnupg-agent2.1.15-4
ii  libassuan0 2.4.3-1
ii  libbz2-1.0 1.0.6-8
ii  libc6  2.24-3
ii  libgcrypt201.7.3-2
ii  libgpg-error0  1.24-1
ii  libksba8   1.3.5-2
ii  libreadline7   7.0-1
ii  libsqlite3-0   3.14.2-1+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages gnupg recommends:
ii  dirmngr 2.1.15-4
ii  gnupg-l10n  2.1.15-4

Versions of packages gnupg suggests:
pn  parcimonie  
pn  xloadimage  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYA0YKAAoJEEvNBWfCltBdij0QAIw+dvvElEhb/4lv4jBJxeQ7
gTnDIlg927lP58fl/XyMnu0qgCQl8lnWZWYa0g147MKw/kG7XAIzVbnDzwp199ZD
LNRQSuL9VjufS+4h9t8UdLEQrxFiMBxBkDZs5bPmsQLxI3D/1Bms2of7B/ZnIivF
dw34gh8/jdBWbn9yMuhUKJ5hyqIBnX6YHEolW0aaUC5A14jdqVKhseMPTECpMezy
Ubr+4B8mGdMmKPHtGTcgLZofmSLKlf9EJhq/cPUJOLFRcnd8DiGTwMx9x9USRZsb
fAn/PvGQjpEzTHrLiNASu6SHtCYQBGWIRrieazX9WHWT4OZ3g9gkwKMTgRNHY5w/
S5q7rD45+Bf6viUh7kWn9sCEJ2QO6giVbmqrBEnI9eR/0hnNO3CWf6y5kZJRtKJC
b6I8TtN79TPKzbXBZXDSPgLCZrFY1LpeIaPn3SuhzZpmnSVR67c9XnupDKQO77mb
eo4oZ5RFqENy3BIcd3uolRTiMdBuT0yLyTXfzYmGMJT4Tdzmi9RyRyQAghCYIcAP
rKqG+keXYZTy5d88iZRImynt9lvHPzprjQmcny5l7rKtkxZoz5CncvWL0wKJdQfL
5/X9+mRuA723xg1MfP0q2UJY5NVQrbbDBlue6j09+nJtzZrzyHxkXXPOLKuNtjh8
yKxFwPXq2Yzk7ponsKYo
=j32Q
-END PGP SIGNATURE-

Bug#991225: Needs a versioned dependency on python3-translate

[Daniel Leidert]

Package: translate-toolkit
Version: 3.3.6-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The translate-toolkit has an unversioned dependency on python3-toolkit.
But so one can install the package from experimenal while still having
python3-toolkit installed. This leads to an error:

pkg_resources.VersionConflict: (translate-toolkit 3.3.2 
(/usr/lib/python3/dist-packages), Requirement.parse('translate-toolkit==3.3.6'))

and the scripts die. It clearly needs a versioned dependency on python3-toolkit.

Regards, Daniel



- -- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages translate-toolkit depends on:
ii  python33.9.2-3
ii  python3-pkg-resources  52.0.0-4
ii  python3-translate  3.3.2-1

Versions of packages translate-toolkit recommends:
ii  translate-toolkit-doc  3.3.2-1

translate-toolkit suggests no packages.

- -- no debconf information

- -- debsums errors found:
debsums: changed file /usr/bin/json2po (from translate-toolkit package)

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmDzcDAACgkQS80FZ8KW
0F2drA//Vi8EUKDn1gdDfkSnLKvUwnpWcZp5c4oNZeD8uNpBqcEEm2YH5sroMyPk
kpELs76VBNqc+oJRwE7Q+5vMI3UNUriRL+kWJlqA5Ef6fOZjKDfF7oEFXsyFO2oq
gDdmaxs+qvAR0CrhmO7dKxDjT0XTn04xEsaNaKsjRhqi8QCNVS1lj7Ybguj5jquC
jag1NBffmEMjjNfcyw0zjNtGPBVNlFq5WAt4Hfy0MP6NXp5qYUZ2m2kQwn9qLCyz
EGq2UGRx+JdOQh4P/tAPg3Em4MoQXetgsQEt8tq2wmkguHfTWPQc5GmKGYTqbaiF
nZF2xpwNeA/bOB9W1eqjG3djIde88CGGe44X2ZID+ivQUr4M1DK8waBU0YSZR54w
AlPOAce+YDZ6qX3UGCUufRH4NbkuPFsHVwS1FqOdh6izvaYeX1VI+6HazsNIFwgD
S3hTjidDo7lG427/nNBLHA90u0Plumm3vTX/FfcN4KfLxYsbiddCnIxTN14cfKMd
5xsIx5i1KVD5aydnfUkQXgoxU74bxZ1TsZZF7sCR9CBGTyqcpzO+rZVS8xQCPI1a
9NFzK39dDWg0APybbdlAPvtOihBL9p36VK915kOToMHtyFotkLhhL38ITkniJ1qb
iADC6OkQNiJR5eutVj68xcHIPv0xTMMLrM1XVpsEtBlcXOgt4OY=
=XnyG
-END PGP SIGNATURE-

Bug#991225: Re #991225

[Daniel Leidert]

Please replace "python3-toolkit" with "python3-translate" in my previous mail.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#1007248: nodejs trying to overwrite /usr/share/systemtap/tapset/node.stp

[Daniel Leidert]

reopen 1007248
thanks

I just got hit by this bug as well:

Entpacken von nodejs (16.13.2+really14.19.1~dfsg-5) über (12.22.9~dfsg-1) ...
dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-DvPfq0/442-
nodejs_16.13.2+really14.19.1~dfsg-5_amd64.deb (--unpack):
 Versuch, »/usr/share/systemtap/tapset/node.stp« zu überschreiben, welches auch
in Paket libnode72:amd64 12.22.9~dfsg-1 ist

It seems this issue is not yet fixed or this is a regression.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#1003405: misses dependency on python3-pmw

[Daniel Leidert]

Source: bkchem
Version: 0.14.0~pre4+git20211228-1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

bkchem requires the pmw module. But it ships neither a dependency on
python3-pmw, nor has python3-pmw been uploaded to the archive yet.

There is a working module though:
https://pypi.org/project/Pmw-py3/

Regards, Daniel

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmHbFIQACgkQS80FZ8KW
0F2tNA/9Fzmqc73T5VYN11Nt6Le+DG/+XH6JiH6q5oKNiw6NglO3ZI2h47NcfKVn
c7R6LwINax/Dzb721IQJAeK6yQpnsMA+twAu0WCKbTsM7R1AgqP5qjE+8CBBwpby
zCRo/RhA0nJZO+nbzdCVF/we2+X318oR3j9BA9zjavWCFBwyz6WTySPvRCjm4KPX
vzhWJigbak32CF3D2eKFUUlLph/UcuIFLKMJtKrC3jWC/PpJX6hV/rUqRZzLjV3q
Zz5jPqidtHovGoq/UGq3bKoxVkuj+dfnsbjT0pLUb2zDn7ct8sGWnBJqyPnU53Cb
GD8mN1UWS2cLiiFzuySWns4O/z+bt44RJpakTd7vr1JZMKbzNP9WOE9AwsYMk3Aa
8YEzMwQ7736hINQnXBRdTHAUxR00SxOvzBLrXPeOVo7h99IZdZ7bmPD9A3bcXVoN
Ub9hu47LiUIODjyeu5zbmhR1asVA3BMGbE3KYcasFwTlVapRjGscyau1XEUuDGN9
D5wGT+EdHvoB8eGZJ8mDA6TaHz+VlRjFBuyG772oboCiYIYsFmucwPIe6CdR8rfn
2cR/gtvhDvxTdMrC+7AuOMRgSvHwg5yxct6Eh2OS3fVPIoUdgTL3hPHkXp+PCTnG
7m1hq/ciZPMm/7uPFe7puqgImVz5zPB0kNHgNoM3rx57s0gtmIE=
=qWAi
-END PGP SIGNATURE-

Bug#886617: Please package version 2.1

[Daniel Leidert]

unblock 886617 by 936212
block  936212 by 886617
block 1003405 by 886617
retitle 886617 python-pmw: Please package version 2.1 and include Python 3 
support
thanks

Hi,

there is finally a bkchem version ported to python 3 and it has already been
packaged. However, it requires the update pf pmw to version 2.1
(https://pypi.org/project/Pmw-py3/).

This would close a lot of open bug reports, and maybe even allow the final
removal of python2.

Should we prepare an NMU?

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#1001129: Ruby 3.0: puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError)

[Daniel Leidert]

Package: puppet
Version: 5.5.22-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The version is not ruby 3.0 compatible:

ruby3.0 -e "require 'puppet'"
/usr/lib/ruby/vendor_ruby/puppet/util.rb:469:in `uri_encode': undefined method 
`escape' for URI:Module (NoMethodError)
from /usr/lib/ruby/vendor_ruby/puppet/util.rb:337:in `path_to_uri'
from /usr/lib/ruby/vendor_ruby/puppet/pops/model/ast.rb:4863:in 
`register_pcore_types'
from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:119:in `'
from /usr/lib/ruby/vendor_ruby/puppet/pops.rb:1:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/puppet/parser.rb:6:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from /usr/lib/ruby/vendor_ruby/puppet.rb:302:in `'
from 
:85:in 
`require'
from 
:85:in 
`require'
from -e:1:in `'

I'm intending to do a quick NMU to fix this.

Regards, Daniel



- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages puppet depends on:
ii  adduser  3.118
ii  facter   3.14.12-1.1
ii  hiera3.2.0-2.1
ii  init-system-helpers  1.60
ii  lsb-base 11.1.0
ii  ruby 1:2.7.6
ii  ruby-augeas  1:0.5.0-3+b9
ii  ruby-deep-merge  1.1.1-1
ii  ruby-shadow  2.5.0+gh-1+b1

Versions of packages puppet recommends:
ii  debconf-utils  1.5.79
ii  lsb-release11.1.0
pn  ruby-selinux   

Versions of packages puppet suggests:
pn  ruby-hocon  
pn  ruby-rrd

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGsALEACgkQS80FZ8KW
0F1nHQ/6AyVaWCMDdPHi0AyhhQZiEISZP0GYNqdrnD/LYF9SdZ2PRlXxQrQfJ7RI
F226bh4sRgzY/pcgfeUmiizaDfCyKxtGrvyjPqOvnoFACDRHDJm/rhjybdsTDCF7
MnHCNjIEic6qoPBqQmG20W15pshRzxbnSojTrZ+4QpHicn7shGYe2EmEJW2ZD6J3
Wsf/YB0Ny7AXKjZzWBqz3TFbBWObo47LC7XiutuirmjM7xe5f+QB5VtGiBk4448f
XgWIPU9LwyAS9uUYWbXd+jxSVZ/92YoR83KyfGTd861Gj042EFXvu/zHRYru+FGj
zM/H2PoQRudDUVlsVX4LXjKdaPJWxYjqhFOYeESRh86paZJFTzCp2VFdCMnCjAyo
y42hH4SFjYsZhysNyDjEMwwSBKjQguKKqkRCjdJ1PeFYWc8CEQwlgAZLtLGSFdPA
d22BplnTtZHT3AEweXUNWDvjfmDjAgObe85u/p5YQgAYldrj5f0C9BoWHpJ02P5I
6pi2KzWDgApuVk8OEbMrgoxsKnGxaXKEGRqoYxYZe8MWvDRJ8vlwTgXqZk3Us0LB
taAXdHCdzvQ3NxYT6JgWkOeBwcfKY14sVzPfeKE7vzB/Ib/HxqdR4qyAdkWqt2V0
ujonrXF3NDPL5ZAi2QIkb/7v42p3B1nc2PeJJ2z/SoIbq1nfqh8=
=CMGz
-END PGP SIGNATURE-

Bug#998509: marked as pending in ruby-rspec-puppet

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #998509 in ruby-rspec-puppet 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:

https://salsa.debian.org/ruby-team/ruby-rspec-puppet/-/commit/81b88ac3fe3a6232dfdfcd6c7ac59703dd045580


Add patch to fix Ruby 3.0 compatbility

  * d/patches/Add-Ruby-3.0-support.patch: Add patch.
- Fix keyword argument issue (closes: #998509).
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/998509

Bug#997657: Problem is in ruby-prawn-icon

[Daniel Leidert]

Hi,

the problem is actually in ruby-prawn-icon in the files
/usr/lib/ruby/vendor_ruby/prawn/icon/font_data.rb and
/usr/lib/ruby/vendor_ruby/prawn/icon/configuration.rb.

In the first the path to the fonts relies on 

Icon.configuration.font_directory

which is defined in the second and leads to the non-existent directory
/usr/lib/ruby/data/fonts, whereas the fonts are actually in
/usr/share/ruby-prawn-icon/data/fonts/.

The quick fix might be to change to the gem installation layout. Otherwise the
font_directory default must be adjusted.

Reassigning to ruby-prawn-icon.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#997657: NMU

[Daniel Leidert]

Hi,

I've just uploaded an NMU to fix this issue. Please find attached the debdiff.
Please note that your Git repository is not in sync with the Debian archive. It
is missing version 3.0.0, this NMU applies to.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
diff -Nru ruby-prawn-icon-3.0.0/debian/changelog ruby-prawn-icon-3.0.0/debian/changelog
--- ruby-prawn-icon-3.0.0/debian/changelog	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/changelog	2021-12-07 11:14:30.0 +0100
@@ -1,3 +1,12 @@
+ruby-prawn-icon (3.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use gem installation layout, so the font files can be found in the
+expected path (closes: #997657).
+  * Enable tests and add ruby-pdf-inspector to build dependencies.
+
+ -- Daniel Leidert   Tue, 07 Dec 2021 11:14:30 +0100
+
 ruby-prawn-icon (3.0.0-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru ruby-prawn-icon-3.0.0/debian/control ruby-prawn-icon-3.0.0/debian/control
--- ruby-prawn-icon-3.0.0/debian/control	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/control	2021-12-07 11:14:30.0 +0100
@@ -6,6 +6,7 @@
 Build-Depends: debhelper-compat (= 13),
gem2deb,
rake,
+   ruby-pdf-inspector,
ruby-prawn (<< 3.0.0),
ruby-prawn (>= 1.1.0),
ruby-rspec
@@ -20,8 +21,8 @@
 Package: ruby-prawn-icon
 Architecture: all
 XB-Ruby-Versions: ${ruby:Versions}
-Depends: ${ruby:Depends},
- ${misc:Depends}
+Depends: ${misc:Depends},
+ ${ruby:Depends}
 Description: Provides icon fonts for PrawnPDF
  Prawn::Icon provides various icon fonts including
  FontAwesome, PaymentFont and Foundation Icons
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch
--- ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch	1970-01-01 01:00:00.0 +0100
+++ ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch	2021-12-07 11:14:30.0 +0100
@@ -0,0 +1,31 @@
+Author: Daniel Leidert
+Date: 2021-12-07
+Subject: Remove bundler and simplecov usage
+
+Forwarded: not-needed
+
+--- a/spec/spec_helper.rb
 b/spec/spec_helper.rb
+@@ -5,11 +5,11 @@
+ # This is free software. Please see the LICENSE and COPYING files for details.
+ #
+ #
+-require 'simplecov'
+-SimpleCov.start
++#require 'simplecov'
++#SimpleCov.start
+ 
+-require "bundler"
+-Bundler.setup
++#require "bundler"
++#Bundler.setup
+ 
+ require "prawn/icon"
+ require 'pdf/inspector'
+@@ -22,4 +22,4 @@
+ RSpec.configure do |config|
+   config.include PDFHelper
+   config.include ParserHelper
+-end
+\ No newline at end of file
++end
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/series ruby-prawn-icon-3.0.0/debian/patches/series
--- ruby-prawn-icon-3.0.0/debian/patches/series	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/patches/series	2021-12-07 11:14:30.0 +0100
@@ -1,2 +1,3 @@
 0001-Clear-executable-bit-on-data-fonts-pf.patch
-0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+#0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+0003-Remove-bundler-and-simplecov.patch
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install
--- ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-data/fonts/[a-z]* /usr/share/ruby-prawn-icon/data/fonts/
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-tests.rake ruby-prawn-icon-3.0.0/debian/ruby-tests.rake
--- ruby-prawn-icon-3.0.0/debian/ruby-tests.rake	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-tests.rake	2021-12-07 11:14:30.0 +0100
@@ -1,4 +1,5 @@
-task default: %w[test]
+require 'gem2deb/rake/spectask'
 
-task :test do
+Gem2Deb::Rake::RSpecTask.new do |spec|
+  spec.pattern = './spec/**/*_spec.rb'
 end
diff -Nru ruby-prawn-icon-3.0.0/debian/rules ruby-prawn-icon-3.0.0/debian/rules
--- ruby-prawn-icon-3.0.0/debian/rules	2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/rules	2021-12-07 11:09:32.0 +0100
@@ -5,5 +5,7 @@
 # Uncomment this to turn on verbose mode.
 export DH_VERBOSE=1
 
+export DH_RUBY = --gem-install
+
 %:
 	dh $@ --buildsystem=ruby --with ruby


signature.asc
Description: This is a digitally signed message part

Bug#959571: marked as pending in ruby-psych

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #959571 in ruby-psych 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:

https://salsa.debian.org/ruby-team/ruby-psych/-/commit/e71781cff79f3af8d1a673fc5cb015b5e26675ac


Re-enable Java extension

  * d/control (Build-Depends): Re-add jruby and java dependencies.
Add libbytelist-java and libjcodings-java.
  * d/javabuild: Add to build psych.jar with javahelper.
  * d/rules: Build Java extension without
running jruby directly (closes: #976493, #959571).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/959571

Bug#976493: marked as pending in ruby-psych

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #976493 in ruby-psych 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:

https://salsa.debian.org/ruby-team/ruby-psych/-/commit/e71781cff79f3af8d1a673fc5cb015b5e26675ac


Re-enable Java extension

  * d/control (Build-Depends): Re-add jruby and java dependencies.
Add libbytelist-java and libjcodings-java.
  * d/javabuild: Add to build psych.jar with javahelper.
  * d/rules: Build Java extension without
running jruby directly (closes: #976493, #959571).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976493

Bug#996520: marked as pending in ruby-varia-model

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996520 in ruby-varia-model 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:

https://salsa.debian.org/ruby-team/ruby-varia-model/-/commit/f78938f6e176d18d7b5bdf9d4dbbcf349ebe13ed


Add patch to deal with FTBFS with Ruby 3.0

  * d/patches/0003-Ignore-test-on-Ruby-3.0.patch: Add patch (closes: #996520).
- Ignore test relying on JSON.create_id=nil hack on Ruby 3.0.
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996520

Bug#998511: marked as pending in ruby-jekyll-data

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #998511 in ruby-jekyll-data 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:

https://salsa.debian.org/ruby-team/ruby-jekyll-data/-/commit/4f31d8d1474ba73b0cef73a21f9a7980eb748224


Fix FTBFS

  * d/ruby-tests.rake: Delete d/Gemfile.lock prior to tests (closes: #998511).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/998511

Bug#998480: marked as pending in ruby-fog-aws

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #998480 in ruby-fog-aws 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:

https://salsa.debian.org/ruby-team/ruby-fog-aws/-/commit/9aab25c7deb95e71661dfefe1909a7d13950e52d


Fix FTBFS

  * d/ruby-tests.rake: Execute shindont with the correct Ruby binary
(closes: #998480).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/998480

Bug#996322: marked as pending in ruby-mmap2

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996322 in ruby-mmap2 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:

https://salsa.debian.org/ruby-team/ruby-mmap2/-/commit/ded5a06ae7e6a1b63dac2434f111e9592ad35550


Add patch to fix FTBFS with Ruby 3.0

  * d/patches/996322-fix-ruby3-compat.patch: Add patch.
- Drop rb_secure() and rb_safe_level() in Ruby 3 (Closes: #996322).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996322

Bug#996224: marked as pending in ruby-faker

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996224 in ruby-faker 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:

https://salsa.debian.org/ruby-team/ruby-faker/-/commit/3bb9ad257b9802626cd5020a1ffea7e77399bb1d


Add patch to fix test error with Ruby 3.0

  * d/patches/0005-Fix-Ruby-3.0-compatibility.patch: Add patch.
- Fix ArgumentError thrown by Ruby 3.0  (closes: #996224).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996224

Bug#996514: marked as pending in ruby-terrapin

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996514 in ruby-terrapin 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:

https://salsa.debian.org/ruby-team/ruby-terrapin/-/commit/f6db29dfa9614a4cfc4c3245a903c885907d2e0b


Fix FTBFS in tests

  * d/patches/dont-try-to-modify-frozen-Process-Status.patch: Add patch.
- Don't modify frozen Process::Status (closes: #996514).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996514

Bug#996206: marked as pending in ruby-cocaine

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996206 in ruby-cocaine 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:

https://salsa.debian.org/ruby-team/ruby-cocaine/-/commit/79eb7ef7bbf8b3d912338c33bbf30340a93a4222


Add patches

  * d/patches/drop-git-in-gemspec.patch: Add patch.
- Drop git usage in gemspec.
  * d/patches/dont-try-to-modify-frozen-Process-Status.patch: Add patch.
- Don't modify frozen Process::Status (closes: #996206).
  * d/patches/series: Enable new patches.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996206

Bug#996210: marked as pending in ruby-css-parser

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996210 in ruby-css-parser 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:

https://salsa.debian.org/ruby-team/ruby-css-parser/-/commit/ade387b157c6884e9315613b1c0747f89f2fe296


Update packaging files and fix FTBFS

  * d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Add ruby-webrick (closes: #996210).
  * d/copyright: Add Upstream-Contact field.
  * d/rules: Use gem installation layout and install upstream changelog.
  * d/watch: Update watch file.
  * d/upstream/metadata: Add Archive and Changelog fields.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996210

Bug#996215: marked as pending in ruby-dbf

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996215 in ruby-dbf 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:

https://salsa.debian.org/ruby-team/ruby-dbf/-/commit/68debea50349b3f7d8914a21b6327355d73f38aa


Fix FTBFS

  * d/patches/0002-Fix-Ruby-3-compatibility.patch: Add patch.
- Fix compatibility with Ruby 3 (closes: #996215).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996215

Bug#996208: marked as pending in ruby-commander

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996208 in ruby-commander 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:

https://salsa.debian.org/ruby-team/ruby-commander/-/commit/c00887d3bebbd0cc947ee0623dc0259665b3f050


Fix FTBFS

  * d/control (Depends, Build-Depends): Use ruby-sorted-set required by the
const_get() method (closes: #996208).

https://dev.to/aaronc81/removing-functionality-the-ruby-way-a-look-into-sortedset-on-ruby-3-clf


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996208

Bug#996369: Info

[Daniel Leidert]

This issue seems to be caused by rails. The issue is gone when using rails
6.1.4 from experimental.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#996369: marked as pending in ruby-responders

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996369 in ruby-responders 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:

https://salsa.debian.org/ruby-team/ruby-responders/-/commit/d57053b119b916a2a70bea683c3eda079eeeb706


Rails 6.1 will fix the FTBFS

  * d/control (Build-Depends): Require rails 6.1 to fix FTBFS (closes: #996369).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996369

Bug#996147: marked as pending in ruby-capybara

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996147 in ruby-capybara 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:

https://salsa.debian.org/ruby-team/ruby-capybara/-/commit/d8c2ed1980c13f17e9d2a2e4cfc2da4f284f84d4


ruby-capybara (3.36.0+ds-1) UNRELEASED

  * New upstream version 3.36.0.
- Fixes keyword argument handling (closes: #996147).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996147

Bug#996366: marked as pending in ruby-regexp-parser

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996366 in ruby-regexp-parser 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:

https://salsa.debian.org/ruby-team/ruby-regexp-parser/-/commit/82a4d330a36ec918ed68ce49c677fcb36f324169


Fix FTBFS and Riby 3 compatibility

  * d/patches/996366-fix-frozenerror.patch: Add patch.
- Don't modify range for Ruby 2.7+ (closes: #996366).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996366

Bug#995358: marked as pending in ruby-graphql

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #995358 in ruby-graphql 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:

https://salsa.debian.org/ruby-team/ruby-graphql/-/commit/68709ce9c8c544d7c9df4ff0206d7ca42cae54a4


Add patch to fix FTBFS in ruby-batch-loader

  * d/patches/Add-missing-require.patch: Add patch.
- Fix NameError by adding missing require statement (closes: #995358).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/995358

Bug#996159: marked as pending in ruby-batch-loader

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996159 in ruby-batch-loader 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:

https://salsa.debian.org/ruby-team/ruby-batch-loader/-/commit/df92d61337b44f2366b3c90e042fddcf47d6a86e


Update packaging files

  * d/control (Build-Depends): Adjust ruby-graphql version (closes: #996159).
(Depends): Remove ruby-graphql and rely on ${ruby:Depends}.
  * d/copyright (Copyright): Add team.
  * d/rules: Use gem installation layout.
  * d/watch: Update file.
  * d/upstream/metadata: Update some URLs.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996159

Bug#996228: marked as pending in ruby-ffaker

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996228 in ruby-ffaker 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:

https://salsa.debian.org/ruby-team/ruby-ffaker/-/commit/a341b7e36f4f9bcbe855064914a9adf3b7490408


Add patch to fix FTBFS

  * d/patches/0003-Test-with-github-action-ruby-3-468.patch: Add patch.
- Fix Ruby 3 compatibility (closes: #996228).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996228

Bug#996117: Update after uploading Rails 6.1

[Daniel Leidert]

With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of
errors like this:

Failure:
ActionController::Serialization::ImplicitSerializerTest#test_render_array_using_custom_root
 [/<>/test/action_controller/serialization_test.rb:186]:
--- expected
+++ actual
@@ -1 +1 @@
-"application/json"
+"application/json; charset=utf-8"


rails test /<>/test/action_controller/serialization_test.rb:181


-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#996117: Update after uploading Rails 6.1

[Daniel Leidert]

Am Samstag, dem 20.11.2021 um 00:18 +0100 schrieb Daniel Leidert:
> With Rails 6.1 the package now fails to build with Ruby 2.7 and a bunch of
> errors like this:
> 
> Failure:
> ActionController::Serialization::ImplicitSerializerTest#test_render_array_using
> _custom_root
> [/<>/test/action_controller/serialization_test.rb:186]:
> --- expected
> +++ actual
> @@ -1 +1 @@
> -"application/json"
> +"application/json; charset=utf-8"
> 
> 
> rails test /<>/test/action_controller/serialization_test.rb:181
> 

I think that this commit was supposed to fix this test issue:
https://github.com/rails-api/active_model_serializers/commit/55a6b23cd84395029aa92605f8aae73f37f57c4a

However, it doesn't work and this issue says that it has a different meaning:
https://github.com/rails/rails/issues/40376

It is possible that this problem is unsolved at the moment.

-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#996303: marked as pending in ruby-json-jwt

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996303 in ruby-json-jwt 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:

https://salsa.debian.org/ruby-team/ruby-json-jwt/-/commit/6ecae09c727dbb05924661c016b725a2c0567afb


Update packaging files

  * d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Require ruby-activesupport >= 6.1 (closes: #996303).
(Depends): Use ${ruby:Depends}.
  * d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
  * d/rules: Use gem installation layout.
  * d/watch: Update file.
  * d/upstream/metadata: Add Archive field.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996303

Bug#996119: marked as pending in ruby-activerecord-nulldb-adapter

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996119 in ruby-activerecord-nulldb-adapter 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:

https://salsa.debian.org/ruby-team/ruby-activerecord-nulldb-adapter/-/commit/e15ee7c2458c63f5d4d7bcba737f94868ea7e1c0


Update packaging files

  * d/control (Standards-Version): Bump to 4.6.0.
(Build-Depends): Bump to ruby-activerecord >= 2:6.1 (closes: #996119).
(Depends): Add ${ruby:Depends}.
  * d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
  * d/rules: Use gem installation layout and install changelog.
  * d/upstream/metadata: Add Archive and Changelog fields.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996119

Bug#996128: marked as pending in ruby-awesome-print

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996128 in ruby-awesome-print 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:

https://salsa.debian.org/ruby-team/ruby-awesome-print/-/commit/4b5ff87b83ad5c1fc0deb31f0c72edbc09f2a529


ruby-awesome-print (1.9.2-1) UNRELEASED

  * New upstream release.
- Provides compatbility with Ruby 3.0 (closes: #996128).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996128

Bug#996126: marked as pending in ruby-attr-encrypted

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996126 in ruby-attr-encrypted 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:

https://salsa.debian.org/ruby-team/ruby-attr-encrypted/-/commit/98da5fe243d0774be3f007c9217fc9e793e206ed


Fix FTBFS by fixing Ruby 2.7/3.0 compatibility

  * d/patches/fix-ruby-3.0.patch: Add patch.
- Fix support for Ruby 2.7 and its kwargs (closes: #996126).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996126

Bug#996382: marked as pending in ruby-seamless-database-pool

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996382 in ruby-seamless-database-pool 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:

https://salsa.debian.org/ruby-team/ruby-seamless-database-pool/-/commit/f820bc6a8d91a276b935de5b350dff6d9c061b15


Add patch to fix FTBFS

  * d/patches/0002-Fix-Ruby-3.0-kwargs-handling.patch: Add patch.
- Fix handling of keyword arguments for Ruby 3.0 (closes: #996382).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996382

Bug#996140: marked as pending in ruby-bogus

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996140 in ruby-bogus 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:

https://salsa.debian.org/ruby-team/ruby-bogus/-/commit/e984d931b5f765002d56ed50fa7b69fe9595416f


Update packaging files

  * d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
  * d/copyright: Add Upstream-Contact field.
(Copyright): Add team.
  * d/ruby-tests.rake: Exclude 2.0/2.1 tests with Ruby 3.0 (closes: #996140).
  * d/rules: Use gem installation layout.
  * d/watch: Update file to use secure gemwatch URL.
  * d/upstream/metadata: Add missing fields.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996140

Bug#996297: Ruby 3 freezes Ranges by default

[Daniel Leidert]

The problem is caused by Ruby 3 freezing Ranges by default [1,2]. Thus the
tests try to handle already frozen objects and some code is not working as
well. I've forwarded the problem to upstream, but they have been inactive for
some time.

[1] https://bugs.ruby-lang.org/issues/15504
[2] https://github.com/ruby/ruby/pull/3583/files
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#996229: marked as pending in ruby-flexmock

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996229 in ruby-flexmock 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:

https://salsa.debian.org/ruby-team/ruby-flexmock/-/commit/16b99bbb52294d3fc2e222984d439fd1215f9b6f


Add patch by Fedora to fix build with Ruby 3.0

  * d/patches/0003-Fix-compatibility-with-Ruby-3.0.patch: Add patch.
- Fix build with Ruby 3.0 (closes: #996229).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996229

Bug#996304: marked as pending in ruby-json-schema

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996304 in ruby-json-schema 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:

https://salsa.debian.org/ruby-team/ruby-json-schema/-/commit/7093323f30f36c2f376f33a3c417d27eaab13e1d


Add patch to fix FTBFS with Ruby 3.0

  * d/patches/ruby_30_support_uri_open.patch: Add patch.
- Call URI.open instead of open (closes: #996304).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996304

Bug#996301: marked as pending in ruby-jbuilder

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996301 in ruby-jbuilder 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:

https://salsa.debian.org/ruby-team/ruby-jbuilder/-/commit/0d696ce1230a2fe2788f8bb5444cb52e20693fca


Add patch to fix tests

  * d/patches/fix-the-test-that-depends-on-the-time-helper.patch: Add patch.
- Fix test case with rails 6.1 and timezone-aware helper (closes: #996301).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996301

Bug#996212: Fix require dalli 3.x

[Daniel Leidert]

After having a look at the issue, the 2.x series is not compatible with Rails
6.1. We need to upload dalli 3.x instead.

https://github.com/petergoldstein/dalli/issues/771

I checked and the 3.x series builds fine (except for one test which requires
network access and must be disabled).

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#996380: Explanation

[Daniel Leidert]

It seems here is an explanation of the problem:
https://github.com/paolobrasolin/jekyll-antex/issues/16

I cannot find any patches so far.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#997364: marked as pending in ruby-sprite-factory

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #997364 in ruby-sprite-factory 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:

https://salsa.debian.org/ruby-team/ruby-sprite-factory/-/commit/392beac8f4ca4b947fb8102b61017da27f0f4d6a


Add patch to replace deprecated method

  * d/patches/replace-deprecated-method-opacity.patch: Add patch.
- Replace deprecated method (closes: #997364).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997364

Bug#996526: marked as pending in rubygems

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996526 in rubygems 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:

https://salsa.debian.org/ruby-team/rubygems/-/commit/e848598f1d036f952d53ddb50d0610619f06de95


Update packaging files and fix FTBFS

  * d/bundler.docs: Add bundler/UPGRADING.md.
  * d/control (Standards-Version): Don't use the minor patch level.
(Build-Depends): Add ruby-webrick (closes: #996526).
  * d/copyright: Add bundler copyright and license information.
(Copyright): Update and add team.
  * d/watch: Update file.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996526

Bug#996524: marked as pending in ruby-whitequark-parser

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996524 in ruby-whitequark-parser 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:

https://salsa.debian.org/ruby-team/ruby-whitequark-parser/-/commit/50a09bacea441200b52d5554c816f644eb4775ca


ruby-whitequark-parser (3.0.2.0-1) unstable

This version adds Ruby 3.0 support (closes: #996524).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996524

Bug#1000488: marked as pending in ruby-nokogumbo

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #1000488 in ruby-nokogumbo 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:

https://salsa.debian.org/ruby-team/ruby-nokogumbo/-/commit/614048c6710572a43789c2f048026c451cefa089


Add patch to make nokogumbo Ruby 3.0 compatible

  * d/patches/Fix-Ruby3-keywords-issue.patch: Add patch.
- Fixes deprecated keyword parameters handling (closes: #1000488).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1000488

Bug#996381: marked as pending in ruby-sanitize

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996381 in ruby-sanitize 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:

https://salsa.debian.org/ruby-team/ruby-sanitize/-/commit/56462205a3c0b8529533a88bc20e86c6c2450c78


ruby-sanitize (5.2.3-1) UNRELEASED

  * New upstream release.
- Fixes issue when using keyword arguments (closes: #996381).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996381

Bug#996370: marked as pending in ruby-rgen

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996370 in ruby-rgen 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:

https://salsa.debian.org/ruby-team/ruby-rgen/-/commit/bacd0489d2c81cea85b7595a90026108258d4dc5


Fix tests

  * d/patches/Handle-Ruby-3-test-failures-fue-to-new-name-method.patch: Add.
- In Ruby 3 some classes got name methods. This leads to an unexpected
  error message in some tests, so we ignore them (closes: #996370).
  * d/patches/series: Adjust file.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996370

Bug#996239: marked as pending in ruby-hashie

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996239 in ruby-hashie 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:

https://salsa.debian.org/ruby-team/ruby-hashie/-/commit/ecc355f37ea1712b938f578d4093fd9be39a60a5


Add patch to fix FTBFS

  * d/patches/0002-Suppress-keyword-arguments-warning-for-Ruby-2.7.0.patch: Add
- Fix ArgumentError with Ruby 3 (closes: #996239).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996239

Bug#996365: marked as pending in ruby-redis-activesupport

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996365 in ruby-redis-activesupport 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:

https://salsa.debian.org/ruby-team/ruby-redis-activesupport/-/commit/0186c6c1933b2689172b2f48d2c7f3aa1d580662


Add patch to fix tests with Rails 6

  * d/patches/Disable-tests-which-will-fail-with-Rails-6.patch: Add patch.
- Fix remaining test failures caused by this gem not being targetted at
  Rails 6 (closes: #996365).
  * d/patches/series: Enable new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996365

Bug#996364: marked as pending in ruby-recursive-open-struct

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996364 in ruby-recursive-open-struct 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:

https://salsa.debian.org/ruby-team/ruby-recursive-open-struct/-/commit/75483f8c9a820734b0bb9a5174f991c78f8e0a9e


ruby-recursive-open-struct (1.1.3-1) UNRELEASED

  * New upstream release.
- Adds Ruby 3.0 support (closes: #996364).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996364

Bug#996309: marked as pending in ruby-kubeclient

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996309 in ruby-kubeclient 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:

https://salsa.debian.org/ruby-team/ruby-kubeclient/-/commit/d8da5d49ee86d4ad2a2b93fdffc2701d7ae8116f


Update packaging files

  * d/control (Build-Depends): Bump ruby-recursive-open-struct to 1.1.3, which
is Ruby 3.0 compatible (closes: #996309).
  * d/copyright (Copyright): Add team.
  * d/rules: Use gem installation layout and install upstream changelog.
  * d/watch: Update file.
  * d/upstream/metadata: Update Changelog URL.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996309

Bug#996351: marked as pending in ruby-rack-oauth2

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996351 in ruby-rack-oauth2 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:

https://salsa.debian.org/ruby-team/ruby-rack-oauth2/-/commit/ee3d412c2e843b9cf0882153a71ab1cff57389ac


ruby-rack-oauth2 (1.19.0-1) UNRELEASED

  * New upstream release.
- Removes usage of obsolete URI.encode method (closes: #996351).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996351

Bug#996300: marked as pending in ruby-jaeger-client

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996300 in ruby-jaeger-client 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:

https://salsa.debian.org/ruby-team/ruby-jaeger-client/-/commit/da76fc757eec6a74f0f51e44733ee2f0bf18700e


ruby-jaeger-client (1.2.0-1) UNRELEASED

  * New upstream release.
- Provides compatibility with Ruby 3.0 (closes: #996300).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996300

Bug#996345: marked as pending in ruby-packable

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996345 in ruby-packable 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:

https://salsa.debian.org/ruby-team/ruby-packable/-/commit/da340b430a052d3313303df76de70ee207505b4a


Add patch to fix ArgumentError

  * d/patches/fix-ruby-3.0-argumenterror.patch: Add patch.
- Fix for trying to create a Proc object without a block (closes: #996345).
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996345

Bug#996323: marked as pending in ruby-mono-logger

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996323 in ruby-mono-logger 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:

https://salsa.debian.org/ruby-team/ruby-mono-logger/-/commit/4bfe8ac410a0e8532e14e252c388d06a9260a152


ruby-mono-logger (1.1.1-1) UNRELEASED

  * Team upload.
  * New upstream release.
- Fixes compatibility with Ruby 3.0 (closes: #996323).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996323

Bug#964607: Massive update necessary

[Daniel Leidert]

This gem is out-of-date. Upstream is at 3.2.2, which requires packaging for
google-cloud-translate-v2 and google-cloud-translate-v3 and updating google-
cloud-core to >= 1.6. The tests require packageing google-style.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#969157: marked as pending in ruby-diaspora-federation-rails

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #969157 in ruby-diaspora-federation-rails 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:

https://salsa.debian.org/ruby-team/ruby-diaspora-federation-rails/-/commit/1f6da353e718c690b24133e094fea601193e1fbc


ruby-diaspora-federation-rails (0.2.7-1) UNRELEASED

  * New upstream release.
- Adds support for Ruby 3.0 and Rails < 7 (closes: #969157).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969157

Bug#969157: marked as pending in ruby-diaspora-federation-rails

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #969157 in ruby-diaspora-federation-rails 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:

https://salsa.debian.org/ruby-team/ruby-diaspora-federation-rails/-/commit/e71e325c7082d5a144a31282386c04da4445ec49


Add patch to backport Rails 6 support

  * d/patches/relax-rails-dep.patch: Add patch.
- Relax Rails dependency accordingly to upstream's master
  branch (closes: #969157).
  * d/patches/series: Add new patch.

The change has not been shipped with version 0.2.7. Therefor we have to
"backport" the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/969157

Bug#996352: marked as pending in ruby-rack-timeout

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996352 in ruby-rack-timeout 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:

https://salsa.debian.org/ruby-team/ruby-rack-timeout/-/commit/df14f02502c32de385e237a09cdbf1a1107bc93b


Add patch to fix Ruby 3.0 compatbility

  * d/patches/Explicitly-convert-hash-to-kwargs-in-test_helper.patch: Add.
- Fix for Ruby 3.0 keyword argument handling (closes: #996352).
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996352

Bug#990443: Issue seems to be ruby-gtk2

[Daniel Leidert]

I did some debugging with this issue and it actually seems to be caused by
ruby-gtk2. It is easy to reproduce. In irb:

require 'gtk2'
include Gtk
require 'openssl'

=> crash (happens when openssl loads openssl.so):

Traceback (most recent call last):
28: from /usr/bin/pdfwalker:25:in `'
27: from /usr/bin/pdfwalker:25:in `load'
26: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/bin/pdfwalker:4:in `'
25: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
24: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
23: from /usr/share/origami/gui/walker.rb:31:in `'
22: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
21: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
20: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami.rb:41:in 
`'
19: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
18: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
17: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/pdf.rb:49:in 
`'
16: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
15: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
14: from 
/usr/share/rubygems-integration/all/gems/origami-2.0.4/lib/origami/encryption.rb:21:in
 `'
13: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
12: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `'
10: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 9: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `'
 7: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 6: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `'
 4: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 3: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `'
 1: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': 
superclass mismatch for class Socket (TypeError)

That's not a bug in origami.

I'll have a look at ruby-gtk2. However, I guess as soon as Gtk2 vanishes from
Debian, pdfwalker will become dysfunctional.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#990443: [DRE-maint] Bug#990443: Issue seems to be ruby-gtk2

[Daniel Leidert]

Am Donnerstag, dem 25.11.2021 um 22:15 +0100 schrieb Daniel Leidert:
> I did some debugging with this issue and it actually seems to be caused by
> ruby-gtk2. It is easy to reproduce. In irb:
> 
> require 'gtk2'
> include Gtk
> require 'openssl'
> 
> => crash (happens when openssl loads openssl.so):

Correkt traceback:

14: from test.rb:3:in `'
13: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
12: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
11: from /usr/lib/ruby/2.7.0/openssl.rb:20:in `'
10: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 9: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 8: from /usr/lib/ruby/2.7.0/openssl/ssl.rb:15:in `'
 7: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 6: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 5: from /usr/lib/ruby/2.7.0/ipaddr.rb:19:in `'
 4: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 3: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
 2: from /usr/lib/ruby/2.7.0/socket.rb:4:in `'
 1: from 
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': 
superclass mismatch for class Socket (TypeError)


-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


signature.asc
Description: This is a digitally signed message part

Bug#951248: marked as pending in origami-pdf

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #951248 in origami-pdf 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:

https://salsa.debian.org/ruby-team/origami-pdf/-/commit/73c56e34ed807c4537c0d1580731fecab1d7703a


origami-pdf (2.0.4+dfsg-1) UNRELEASED

  * New upstream release.
- Removes Bignum/Fixnum usage (closes: #951248).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/951248

Bug#996155: marked as pending in origami-pdf

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996155 in origami-pdf 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:

https://salsa.debian.org/ruby-team/origami-pdf/-/commit/ee3bbfed5480084305724d42939638475c313f6f


Fix Ruby 3.0 keyword arguments error

  * d/patches/0002-Fix-Ruby-2.7-keyword-arguments-warnings.patch: Add patch.
- Fixes Ruby 3.0 keyword argument handling error (closes: #996155).
  * d/patches/series: Add new patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996155