Re: Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)

Ian Jackson-2
Didier 'OdyX' Raboud writes ("Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)"):
> Package: dgit
> Version: 3.12
> Severity: important
>
> I finally wanted to try dgit today, but…

Sorry about this.

On stretch:
  perl -we 'use Dpkg::Source::Package; my $x = new Dpkg::Compression::Process'

On sid (libdpkg-perl 1.19.0.3):
  (build)ian@zealot:~$ perl -we 'use Dpkg::Source::Package; my $x = new Dpkg::Compression::Process'
  Can't locate object method "new" via package "Dpkg::Compression::Process" (perhaps you forgot to load "Dpkg::Compression::Process"?) at -e line 1.

Sadly I am not aware of a good way of detecting missing `use'
direcctives other than waiting for things to break when an implicitly
loaded module is no longer loaded.

There will be an update very shortly.

Ian.

Reply | Threaded
Open this post in threaded view
|

Re: Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)

Ian Jackson-2
Ian Jackson writes ("Re: Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)"):
> On stretch:
>   perl -we 'use Dpkg::Source::Package; my $x = new Dpkg::Compression::Process'
>
> On sid (libdpkg-perl 1.19.0.3):
>   (build)ian@zealot:~$ perl -we 'use Dpkg::Source::Package; my $x = new Dpkg::Compression::Process'
>   Can't locate object method "new" via package "Dpkg::Compression::Process" (perhaps you forgot to load "Dpkg::Compression::Process"?) at -e line 1.

Obviously this is hardly a bug in dpkg.  But can you perhaps add
   Breaks: dgit (<<3.13~)
?

Thanks,
Ian.

Reply | Threaded
Open this post in threaded view
|

Re: Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)

Cyril Brulebois-4
In reply to this post by Ian Jackson-2
Ian Jackson <[hidden email]> (2017-10-22):

> On stretch:
>   perl -we 'use Dpkg::Source::Package; my $x = new Dpkg::Compression::Process'
>
> On sid (libdpkg-perl 1.19.0.3):
>   (build)ian@zealot:~$ perl -we 'use Dpkg::Source::Package; my $x = new Dpkg::Compression::Process'
>   Can't locate object method "new" via package "Dpkg::Compression::Process" (perhaps you forgot to load "Dpkg::Compression::Process"?) at -e line 1.
>
> Sadly I am not aware of a good way of detecting missing `use'
> direcctives other than waiting for things to break when an implicitly
> loaded module is no longer loaded.
I'm not sure what the problem with use-ing Dpkg::Compression::Process
unconditionally would be?


Cheers,
--
Cyril Brulebois ([hidden email])            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)

Ian Jackson-2
Cyril Brulebois writes ("Bug#879526: dgit broken by recent dpkg (Can't locate object method "new" via package "Dpkg::Compression::Process" …)"):
> I'm not sure what the problem with use-ing Dpkg::Compression::Process
> unconditionally would be?

There isn't one, and that's how #879526 was fixed in dgit.

My comment ...

> Ian Jackson <[hidden email]> (2017-10-22):
> > Sadly I am not aware of a good way of detecting missing `use'
> > direcctives other than waiting for things to break when an implicitly
> > loaded module is no longer loaded.

... related to the fact that there may be other similar bugs lurking
in dgit (and in other programs).  It would be nice if there was a way
to spot them.

Ian.

--
Ian Jackson <[hidden email]>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.