Bug#500622: ITP: libflickr-upload-perl -- Flickr::Upload from CPAN

2008-09-29 Thread Alex Muntada
Package: wnpp
Severity: wishlist

* Package name: libflickr-upload-perl
  Version : 1.32
  Upstream Author : Christophe Beauregard [EMAIL PROTECTED]
* URL : http://search.cpan.org/dist/Flickr-Upload/
* License : Perl5
  Programming Lang: Perl
  Description : Module for uploading images to flickr.com

  Upload an image to flickr.com.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#500622: Acknowledgement (ITP: libflickr-upload-perl -- Flickr::Upload from CPAN)

2008-10-08 Thread Alex Muntada
libflickr-upload-perl was recently injected into pkg-perl svn repo:
http://svn.debian.org/wsvn/pkg-perl/trunk/libflickr-upload-perl?op=logrev=0sc=0isdir=1

I'd appreciate any comments about this; it's my first package
prepared for Debian pkg-perl team.

Thanks a lot!

-- 
Alex Muntada [EMAIL PROTECTED]
http://alexm.org/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#500622: Acknowledgement (ITP: libflickr-upload-perl -- Flickr::Upload from CPAN)

2008-10-08 Thread Alex Muntada
* Damyan Ivanov [EMAIL PROTECTED]:

  * to flag that the package is ready for review/upload you should sed
   the distribution to something else, not 'UNRELEASED'. 'dch -r' can
   help here.

It makes perfect sense, so the uploader doesn't have to change a
thing. Fixed.

  * no need to detail the changes for the -1 release. Initial release
   (Closes ITP) entry is enough. In debian/changelog you describe the
   changes since the previous debian release. Since this is the first
   debian release, there is no much to describe.

True, I forgot about this. Fixed too.

Therefore, I guess the package is ready for upload unless someone
has any further comments about it.

Thanks!

-- 
Alex Muntada [EMAIL PROTECTED]
http://alexm.org/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#443570: New Option MacModel mini available upstream

2007-09-22 Thread Alex Muntada
Upstream just committed a patch to add this new option to get MacMini
displays working properly.  See for details:

https://bugs.freedesktop.org/show_bug.cgi?id=12525#c12

I guess that the experimental xserver-xorg-video-ati version should be
updated accordingly.

-- 
Alex Muntada [EMAIL PROTECTED]
http://alexm.org/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#454792: using utf8 module instead of enconding should work

2008-03-16 Thread Alex Muntada
As commented on this Perl Monks node:
http://perlmonks.org/?node_id=674382

The utf8 module works fine with Unicode in Perl regexes,
so in the sample above just remove the use encoding ...
line to get rid of the double free bug.

HTH

-- 
Alex Muntada [EMAIL PROTECTED]
http://alexm.org/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#505763: ITP: libfile-sharedir-par-perl -- File::ShareDir with PAR support

2008-11-14 Thread Alex Muntada
Package: wnpp
Severity: wishlist

* Package name: libfile-sharedir-par-perl
  Version : 0.02
  Upstream Author : Steffen Müller [EMAIL PROTECTED]
* URL : http://search.cpan.org/dist/File-ShareDir-PAR
* License : Perl (Artistic and GPL)
  Programming Lang: Perl
  Description : File::ShareDir with PAR support

File::ShareDir::PAR provides the same functionality as File::ShareDir
but tries hard to be compatible with PAR packaged applications.

The problem is, that the concept of having a distribution or module
specific share directory becomes a little hazy when you're loading
everything from a single file. PAR uses an @INC hook to intercept any
attempt to load a module. File::ShareDir uses the directory structure
that is typically found in the directories that are listed in @INC for
storing the shared data. In a PAR enviroment, this is not necessarily
possible.

When you call one of the functions that this module provides, it will
take care to search in any of the currently loaded .par files before
scanning @INC. This is the same order of preference you get for loading
modules when PAR is in effect. If the path or file you are asking for is
found in one of the loaded .par files, that containing .par file is
extracted and the path returned will point to the extracted copy on
disk.

Depending on how you're using PAR, the files that are extracted this way
are either cleaned up after program termination or cached for further
executions. Either way, you're safe if you use the shared data as
read-only data. If you write to it, your changes may be lost after the
program ends.




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#505763: File::ShareDir::PAR requires File::ShareDir version 1.00

2008-11-14 Thread Alex Muntada
sub File::ShareDir::class_file is required by File::ShareDir::PAR,
but it's not available since version 1.0, so I added a block for
this ITP bug by #496478.

-- 
Alex Muntada [EMAIL PROTECTED]
http://alexm.org/



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#318058: works fine under libdbd-mysql-perl 4.008-1 in unstable

2009-04-15 Thread Alex Muntada
* WK w...@hot.ee wrote:

 I think you are right, but i'm just confused now.
 I used the first one, but i tried like this:

 my $dbh = DBI-connect($data_source, $user, $password)
 || die no connection\n;
 $dbh-{mysql_enable_utf8} = 1;

Please, read what the docs for DBD::mysql say about this:

This will only take effect if used as part of the call to connect().
If you turn the flag on after connecting, you will need to issue
the command SET NAMES utf8 to get the same effect.

 One thing i can suggest: maybe this option (mysql_enable_utf8)
 could be enabled automatically when database is in UTF8.

Having the Debian module work in a different way that the one
upstream would be a Bad Thing, in my opinion. So I guess that
the best place to suggest such a change would be upstream:

http://rt.cpan.org/Public/Dist/Display.html?Name=DBD-mysql

Happy hacking!

-- 
Alex Muntada al...@alexm.org
http://alexm.org/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#318058: works fine under libdbd-mysql-perl 4.008-1 in unstable

2009-04-04 Thread Alex Muntada
I was asked by gregor herrmann to take a look at this bug,
and I just tried the test case with successful results under
libdbd-mysql-perl 4.008-1 in unstable:

1 šš ðð

Can you please confirm that it works for you too?

-- 
Alex Muntada al...@alexm.org
http://alexm.org/



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#521984: fix is on the way

2009-04-06 Thread Alex Muntada
tags 521984 + pending upstream
thanks

I uploaded a fix for this bug into pkg-perl svn
and sent a message to upstream author too.

-- 
Alex Muntada al...@alexm.org
http://alexm.org/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#318058: works fine under libdbd-mysql-perl 4.008-1 in unstable

2009-04-07 Thread Alex Muntada
* WK w...@hot.ee:

 Thank you, but sorry, I still can't. Did you change anything
 in testcase?

Only $username and $password.

 Could you please let me see your mysql-server status report
 (i mean \s from client)?

mysql  Ver 14.12 Distrib 5.0.77, for debian-linux-gnu (i486) using readline 5.2

Connection id:  46
Current database:   
Current user:   r...@localhost
SSL:Not in use
Current pager:  stdout
Using outfile:  ''
Using delimiter:;
Server version: 5.0.77-1 (Debian)
Protocol version:   10
Connection: Localhost via UNIX socket
Server characterset:latin1
Db characterset:latin1
Client characterset:latin1
Conn.  characterset:latin1
UNIX socket:/var/run/mysqld/mysqld.sock
Uptime: 2 days 19 hours 48 min 27 sec

Threads: 1  Questions: 245  Slow queries: 0  Opens: 149  Flush tables:
2  Open tables: 18  Queries per second avg: 0.001

 I set up fresh Debian Squeeze on Virtualbox and i still got wrong characters.

I'm using LANG=en_US.UTF-8, just in case. Do you think
that testing it with your locales should fail too? I'm willing
to perform any tests you'd like, just ask ;-)

-- 
Alex Muntada al...@alexm.org
http://alexm.org/



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#518071: python-apt: replace obsolete ftp.caliu.info with ftp.caliu.cat

2009-03-03 Thread Alex Muntada
Package: python-apt
Version: 0.7.8
Severity: important

Domain caliu.info was replaced long time ago with caliu.cat,
which is now listed in http://www.debian.org/mirrors/sponsors
(caliu.info is no longer managed by us). So the following
files should be updated accordingly:

$ grep caliu /usr/share/python-apt/templates/*.mirrors
/usr/share/python-apt/templates/Debian.mirrors:ftp://ftp.caliu.info/debian/
/usr/share/python-apt/templates/Debian.mirrors:http://ftp.caliu.info/debian/
/usr/share/python-apt/templates/Ubuntu.mirrors:http://ftp.caliu.info/pub/distribucions/ubuntu/ubuntu/

I've checked out python-apt from experimental (0.7.9~exp2)
and it has the same old references to caliu.info.

Thanks a lot,
/alexm


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-apt depends on:
ii  apt [libapt-pkg-libc6.7-6-4.6 0.7.20.2   Advanced front-end for dpkg
ii  apt-utils [libapt-inst-libc6. 0.7.20.2   APT utility programs
ii  libc6 2.9-4  GNU C Library: Shared libraries
ii  libgcc1   1:4.3.3-5  GCC support library
ii  libstdc++64.3.3-5The GNU Standard C++ Library v3
ii  lsb-release   3.2-20 Linux Standard Base version report
ii  python2.5.4-2An interactive high-level object-o
ii  python-central0.6.11 register and build utility for Pyt

python-apt recommends no packages.

Versions of packages python-apt suggests:
pn  python-apt-dbgnone (no description available)

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742195: ITP: libmojolicious-plugin-cgi-perl -- Run CGI script from Mojolicious

2014-04-16 Thread Alex Muntada
It's been a while since my last package (it was before git) and
i'm trying to update my knowlege about the packaging process.

The problem i'm facing is that there's a test in this Perl
distribution that is behaving differently inside pdebuild with
cowbuilder. As far as i can see from the tests i performed
outside pdebuild, the problem seems to be that there's an extra
pipe for fd/0 which makes an odd number of pipes, thus failing
the test.

I made some changes to the test with quilt and pushed them into
the pkg-perl repo, but they're only to help me debug the issue
for now. Those changes make the test show some diags, e.g.

$ pdebuild --pbuilder cowbuilder
...
make[1]: Entering directory `/tmp/buildd/libmojolicious-plugin-cgi-perl-0.07'
PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 
'blib/lib', 'blib/arch') t/*.t
t/00-basic.t ... ok
t/basic.t .. ok
t/before.t . ok
t/errlog.t . ok
t/multipart.t .. ok
# 11686
# waiting for 11686
Use of uninitialized value in pattern match (m//) at t/post.t line 35.
# pipes: $VAR1 = [
#   [
# '/proc/11685/fd/0',
# 'pipe:[90940]'
#   ],
#   [
# '/proc/11685/fd/1',
# 'pipe:[91868]'
#   ],
#   [
# '/proc/11685/fd/2',
# 'pipe:[91869]'
#   ],
#   [
# '/proc/11685/fd/6',
# 'pipe:[91868]'
#   ],
#   [
# '/proc/11685/fd/7',
# 'pipe:[91869]'
#   ]
# ];

#   Failed test 'no leaky pipes'
#   at t/post.t line 41.
# Looks like you failed 1 test of 5.
t/post.t ... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/5 subtests 
t/redirect.t ... ok

Does anybody have a clue about where does the fd/0 come from and
how could i improve the test? I'll ask the author if it's safe
to ignore fd/0 in this case. Any other thoughts?

Thanks a lot,
Alex


signature.asc
Description: Digital signature


Bug#742195: ITP: libmojolicious-plugin-cgi-perl -- Run CGI script from Mojolicious

2014-04-16 Thread Alex Muntada
Dominique Dumont:

 The problem is: '/proc' is not mounted in the pbuilder chroot.

Yes it is in this case, because the test finds those pipes it's
looking for. The problem is that it fins one too many, ie. fd/0.

I already asked the upstream author about ignoring fd/0:
https://github.com/jhthorsen/mojolicious-plugin-cgi/issues/6

 Unfortunately, I don't think this is possible in Debian build environments 
 (and it won't work in system where /proc is not available: hurd ? bsd ? )
 so you may have to disable these tests.

The test checks for /proc/$$/fd first, so it will be ignored if
/proc is not available, whatever the system.

Thanks,
Alex


signature.asc
Description: Digital signature


Bug#742195: ITP: libmojolicious-plugin-cgi-perl -- Run CGI script from Mojolicious

2014-05-11 Thread Alex Muntada
Alex Muntada:

 I already asked the upstream author about ignoring fd/0:
 https://github.com/jhthorsen/mojolicious-plugin-cgi/issues/6

No response, so far.

 The test checks for /proc/$$/fd first, so it will be ignored if
 /proc is not available, whatever the system.

I was unable to isolate the issue so I removed the non-portable
test as suggested by Dominique.

Thanks,
Alex


signature.asc
Description: Digital signature


Bug#751747: /etc/init.d/samhain: invalid arguments

2014-06-16 Thread Alex Muntada
Package: samhain
Version: 3.1.0-5

When /etc/logrotate.d/samhain runs /etc/init.d/samhain reload
it raises the following error:

/etc/cron.daily/logrotate:
/etc/init.d/samhain: invalid arguments
error: error running shared postrotate script for '/var/log/samhain/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

The problem is that /etc/init.d/samhain is missing an argument
in the call to pidofproc. Just adding $DAEMON fixes that:

--- /etc/init.d/samhain 2014-03-29 08:39:04.0 +0100
+++ samhain 2014-06-16 11:43:31.979809768 +0200
@@ -35,7 +35,7 @@
pid=`cat $PIDFILE`
 # No pid, probably no daemon present
if [ -n $pid ] ; then
-   pidofproc -p $PIDFILE
+   pidofproc -p $PIDFILE $DAEMON
return $?
fi

Cheers,
Alex


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#742195: ITP: libmojolicious-plugin-cgi-perl -- Run CGI script from Mojolicious

2014-03-20 Thread Alex Muntada
Package: wnpp
Severity: wishlist
Owner: Alex Muntada al...@alexm.org

* Package name: libmojolicious-plugin-cgi-perl
  Version : 0.07
  Upstream Author : Jan Henning Thorsen jhthor...@cpan.org
* URL : https://metacpan.org/release/Mojolicious-Plugin-CGI
* License : GPL, Artistic
  Programming Lang: Perl
  Description : Mojolicious::Plugin::CGI runs CGI scripts from Mojolicious

Mojolicious::Plugin::CGI enables Mojolicious to run Perl CGI scripts.
It does so by forking a new process with a modified environment and
reads the STDOUT in a non-blocking matter.


signature.asc
Description: Digital signature


Bug#762734: gbp-pull support for git fetch --prune

2014-09-24 Thread Alex Muntada
Package: git-buildpackage
Version: 0.6.19

After renaming the default debian branch from debian to master
and the upstream branch from master to upstream on a pkg-perl
team repository, we realized that the old debian remote branch
would still be there in the working copies after gbp-pull.
It would be nice to be able to ask for a git fetch --prune
somehow.

Maybe it's safer to not enable this by default but having that
option would help cleanup the working copies of several pkg-perl
fellows.

Thanks!
Alex


signature.asc
Description: Digital signature


Bug#790704: Please add Alex Muntada as a Debian Maintainer

2015-06-30 Thread Alex Muntada
Package: debian-maintainers
Tags: patch

Please, add me as a Debian Maintainer. See the jetring changeset
attached below.

Thanks!
Alex

Comment: Add Alex Muntada al...@alexm.org as a Debian Maintainer
Date: Wed, 01 Jul 2015 00:59:59 +0200
Recommended-By: 
  Axel Beckert a...@debian.org, gregor herrmann gre...@debian.org
Agreement: 
  https://lists.debian.org/debian-newmaint/2015/06/msg00024.html
Advocates: 
  https://lists.debian.org/debian-newmaint/2015/06/msg00025.html
  https://lists.debian.org/debian-newmaint/2015/06/msg00026.html
Action: import
Data: 
  -BEGIN PGP PUBLIC KEY BLOCK-
  Version: GnuPG v1
  
  mQINBEyjZWQBEADeb5Zu4Y6Jsu9e1hB8STTqeZoqlUx9ARamqgmEmJhzEJz6SQE6
  wF/3f3GBWaMrtgg/AHApM2+MlDADdYnOGB4pUe52PkJCxwWpyK7FldI0v3YtnnPB
  d2YEmoS6qCM0w2dj1V/IKGXFVPFopygOayBMmBk7pm4lYtpNZLMoAMeTzR5qiDh1
  rmfptxGnyqWpPa/ZOm2WIy7GG0PEuYv8lPJ/yXeNJwf4aCFHYMSe5tcDfCAXS8AI
  RAOnEqnyGzJ7ekX1/VCf5AHYyjjAtDs0Y+cTt7VrfnLU9YCXdaeFkue+gf5+jYRI
  RNNxlaZ/N4u0KkVbZfU7zKTX7lHy+aj3qp/lhgHwZJXnjK1bnKbXNP75f50IPhLG
  6Obd9QsdHRhnD0mVrtdQQ+p210v+/3zXFP4bhN0qoTwtsiAcam9nZi7/8S33wfz7
  /paRqA26ntpqao+fdlEVk0YhuG0VSR/1ok9KiISAmrJdIuP8xmVtY7Ewniwx58/X
  HBCFENucmF+oYl3ueT+xGtqIPupcfVqsfcKyaylAuwM+UpX9lBSzyNxuNcoerwPi
  JlAuUVWz8KUC1VwcSbOLuTqXw1w4g/EjHwxjhBYhZ92LVayDHYCd73S+MD1astTo
  1GazNhjb686IhdN9hNywFpihJ/2+V2bCxKovef8YD1JmvEMZec1I5ePvpQARAQAB
  tB5BbGV4IE11bnRhZGEgPGFsZXhtQGFsZXhtLm9yZz6JAjoEEwEIACQCGwMFCwkI
  BwMFFQoJCAsFFgIDAQACHgECF4AFAkyjb+QCGQEACgkQ466XjoNOXn5n9Q/+Jkeu
  TRh1Ehle8qZHZb/Iwp7qZUWgh1qnhdfcR+WNC5NBt46Z+C7BgD7TC/PyrIN7vdmK
  BGYY9OnA4wQC1myIrDpjyBfRKwDAyb45zXnENmEZy0xXLpJ6ap3mhjeuA4XF72zR
  Lhrx+eU6p1+Qfdze23z5iT3ErsK4TVVPMpLYQOORVkMTVn+bxqkpEqV3Tc7nLCYf
  /yhsTCPeTquCCgScax8pZ33vTd9+bUcRPhVu/8ZPhisPuhqzdHNAsbLJeVDqwqy5
  vE2O0Eb+f6FWX5qVxh5oR/x/+uLipJHVkcxj+MtC8onUI0EXMj3LwATKbjhtfVRc
  XFuFR7NgADqzwv/MpXBe+o4my/wBPPLVBx3X4gLF/I5idMBS5TsXsjOWKWShgh9B
  XXXq9b7EsJQeK/LrUXR4fZgBFLYQJPXkt9mit/DqDFU2gk0yRXMJW/mRkKHnVV9a
  fbqjBteuqv9myaltP2OeuYMPdyQWoBpIr4tU0qX50UcQJT5+fYLOLIPWwL/uMS1g
  okYl1i4yKZnXLDsXMj7oggfohu2dYyJFtUpVfavsUdJ5CPPW7ZyiWB031LL6eP8y
  6DA+j+bsRjL6j2oYosqC6RwEHWsJ9Wrq1S40wDOYaKa5xlZqIx+zg6jg4cvtEZLc
  tKy0Snsz3dHJAGGgoli5A2XI1KNSYV0ZYdsYnKuIRgQQEQgABgUCTKNw3AAKCRAt
  3EIZLfNoEVv7AJ4hfJ17J2y5q4dvCKbQIbBHEPfRfQCdFdpiVTAjRrzEX3zajbpp
  0GSBxuaJAhwEEAEIAAYFAky8ZeQACgkQBY4p8QRJo7BDhBAAsXoEPMRqoAlrG7M7
  fUXaLE5BRX21Vecdi/l6KiMDHBrXNCZorIce1bIJW3cIi0WXtstIBgYDh+HDaE9z
  rtXBI1IHGvhMOcEMPGgRXTdC4Z2rGcqjUacFUFwbUUHwgpQ//824iyT/AsBWYUOM
  EJcIbcBULOgokKHWCUuTlX8y7Iwc2BpoB7AJcHLv6tHYl9tq4TlbRMFd4tyFsq1o
  T/HpOVrGcDF3SyTCIudBfLycfK1Cm2KFhVDf4LX2uwvtdGcHMsNIYTvMqrlf4aZF
  +/q7l78j8UyaB8aQrKBf5Gt75OVhiNtWe9Q0L1/utYYZV77Gnu2P13v2C/6vO2yl
  d9ys1Dx0alubJLQ4ahcWymtn/fwB0C0PlCoBTHX4YyxLABh4po8VTPRCS+X4aEgG
  J59/aRH/ZQXXlNS7X/XYQQGTy/Cywn9xIED2ADSVbSX3rL0ieh/gc8Ae55nHSA1y
  +2BRAKXzjN+ZnCUs/ewCLettzg/5NMxb4jf+uqX4GSBjnXrcupSQGBhYp+LxTFX+
  Z0chf+oWeYdwKA3xwwBh/g+GMoxiOp/OHXFJ3QaAfUrxRPPwOyaM+7pLo7Df5J8p
  yMcpQFwoSfWBzYkQfgdSDGzQ0yIOPyW7Fg1wI9pAxFzikHgjj7VXIkDjdCC9TFES
  EY41bAPP4dGsLqbmSRTprwb2whSJAhwEEAEIAAYFAkze0LUACgkQe+u6XaP6gGll
  axAAmSjDV5h06j0RGZRIJRmkOLaOvqT2nbDkUkB5RBe/kZM7A5DYSeB9LcGRLOrO
  jkqXotFmcKTtysszl2J8kxcJuttbbERPOkdPpS73RtLKmZ2CVt2djjnyYTfxF7aq
  jkTT+P/X8NTABCiAFhlkgoulE8UL/tI7HAQDHA6vtxdPHmhi2NmR63wpFydvfHnJ
  MIgv/Uvy6i1KSAJwQwLivQJoiLvxVy431Od3KXla26WF98zuzcdO0epWac+WL0HT
  NR/tWBmXaG6kwhfpN8sqlPbBZvKkeE2OyCgep0mg0/prZZh+9X2iJxSL1ftBHtdB
  AEcgT2MjaR/El9JKz3YQAFBmI/mt1q6p4gfNDPlYM+W8B70A5qojUveG3R/ZD+V1
  QV+IkylKj6HYSlnBuj2EI6web3IhmXygvQPgDwN0IEouRhkvgZB0ww5FNRQg7uJC
  FcRuUJgePPg8ma5HKhMxOKksjOtEZdxTE/TErW8vreIJFvrqZzj3FxgyB7AZ7HIT
  /uxOTlRTDQ1/oft53jhhTe36FJcrvAnQ7iEweYyOIvwXCQHd+vJNMIAvI5IIbXQc
  LPEzUFTx/k2UcQR0++FRQ9gL15NQN8kUaujz8cDG9cc6guVs1StoSctJE44qmm3D
  Twb9xRA6fetzXqfcRnBPssIspDoMnpgtaemp5XAtt/URvU2IRgQQEQIABgUCTarv
  lAAKCRBAlomgxt440pNIAKCAZTdeZGqiNWSw08O7K72ZA4vwWgCfRajOQlb6oYxP
  lyuVmepiN4lslW6IRgQQEQIABgUCTsIvIQAKCRDArvFVl0UeanKsAKCBisrHaaBI
  AWsiwQ254nGaNhjw2gCfX/HOdE+DZptF/g1YGIUcQzNKfQyIRgQQEQIABgUCUyTN
  qAAKCRD8SWwDTpG/oR45AKCKI7XFLxGnFNR05toyURjHUGS2YwCguo9tvLqionI5
  aJIwnWFEsx2PVj+IXgQQEQgABgUCTZhKPwAKCRCPqfbDkJn0OVSFAP9S1bPodv3q
  4hd8pN6D0eDebQulqa5QXJ7pCrYl5I6cOAD+NctttuBxzpviulnkO8m0RCztjPlI
  C64hyU1UIma3gfmJAhwEEAEIAAYFAlMl6TwACgkQ7v8jcKPzONGO3BAAqTKOpTLY
  oq7RuyZJXk6bSZa+m3ayqXQTrng3jwLI7iEb+JiKoSlC3UUOkZlrOfE0wRZLsdrN
  ebgygfEhvUc+jXaqhGvc63aWUbhWzps49NKcSZSwtxRR9xMVoMdmSNtqUXV0XnzL
  9lIiO0ea2O9rlmLYDX4+MkSJoZaRgE86kczAkPqbmbLUhs+RJQFAa16Q1SEm9lt6
  wQLLjjlW9aX80d+720gTjKeADUdnN5emY5saRexlPZAwOVAyWVQbGNGAsZLEdcoC
  0oSB27VYjRS4YZgVz2FI4yT++db0m2CgmYS7Wt+y3hE3nVxbC9fq0s9/oPbAbSy8
  s9MBEUkGo1ZEVGAKbNw04g7BDDNX0HvksPgGNBWzADFW/iOyZ1ZA2gPvqknkcMel
  M0k0C/KtVlYYrJTxN+VTSMOz7xp0gEC7S32YvntQXQasUAU83KeAEedAKI1nUgiw
  pmTIu4tcDttIHs2sMPNdKLMYKCcSZdNWfrU1ieKNgJEIYDeHG5+swzftpC0Cr51k
  hyYrUkKKpdJ/q/MYZPfgDtUa8J6/eksLMJPwsaH9Z6CzGdDF4bILcRfpqndQfd5Y
  x5VviBs2fho0qg5gIV4u2aoKh4iPO9MOnlKJIuzZbWFUaFQHkiwf7qR4Z4lPxGm2
  KG7pY

Bug#759324: successfully build latest versions

2015-10-30 Thread Alex Muntada
Today I managed to successfully build and test DBD::Oracle 1.74
on sid using Perl 5.20.2 and Oracle 12.1 for amd64 (well, the
Unicode tests were skipped due to lack of Unicode support, but
I will look into that eventually).

The next step will be to build it using experimental Perl 5.22
and prepare a package upgrade for sid.

Cheers,
Alex



signature.asc
Description: Digital signature


Bug#781290: still happens in d-i 20150606

2015-07-11 Thread Alex Muntada
Control: found -1 20150606

This week I reinstalled my laptop with Debian GNU/Linux 8.1.0
Jessie - Official amd64 CD Binary-1 20150606-14:19 and I was
surprised that the encrypted LVM volume I created manually from
partman has a Linux (83) type instead of Linux LVM (8e).

Cheers,
Alex



signature.asc
Description: Digital signature


Bug#788842: merge with bug 767682

2015-07-11 Thread Alex Muntada
Control: severity -1 important
Control: merge -1 767682

It seems to me that both #788842 and #789427 are the same bug
than #767682 that I stumbled upon on Mon Jul 6th, so let's
merge them altogether.

Cheers,
Alex



signature.asc
Description: Digital signature


Bug#767682: still happens in d-i 20150606

2015-07-11 Thread Alex Muntada
Control: found -1 20150606

Stumbled upon this bug last Monday while installing Jessie from
Debian GNU/Linux 8.1.0 Jessie - Official amd64 CD Binary-1
20150606-14:19 on top of a previous Ubuntu installation that
had an existing /boot partition on sda3 formatted with ext4.

I formatted the partition from the TUI and then I found that
a confirmation was required before proceeding by mkfs.ext4.
After that the installation was performed successfully.

Cheers,
Alex



signature.asc
Description: Digital signature


Bug#759324: successfully build latest versions

2016-01-17 Thread Alex Muntada
Dominic Hargreaves:

> perl 5.22 finally hit unstable last week, which should make this
> part easier, at least :)

Version 1.74 successfully built on perl 5.22 with no issues.

Good job and thanks a lot!
Alex


signature.asc
Description: Digital signature


Bug#813736: ITP: castnow -- command-line chromecast player

2016-02-07 Thread Alex Muntada
Dominik George:

> * Package name: castnow
>   Version : 0.4.14
>   Upstream Author : Simon Kusterer 
> * URL : https://github.com/xat/castnow

Did you notice that the upstream author says this in the README?

I currently don't have that much time to maintain this
project and have also lost some interest (to be honest).

BTW, I tried castnow on the Chromecast 2 that I got a few weeks
ago and it didn't work. I managed to connect to the Chromecast
device using the IP address and it showed a progress bar of the
file that was being uploaded but it always ends with an error
(some kind of timeout I guess). No matter if its an MP4 or JPG.

There may be something wrong in my end, but I just wanted to
share my worries that it may not be ready yet for adding it to
Debian.

Cheers,
Alex



signature.asc
Description: Digital signature


Bug#759324: dbd-oracle

2016-02-02 Thread Alex Muntada
Christoph Martin:

> If you need any help with building or uploading dbd-oracle, I can help.
> I have Oracle Installations and I am a Debian developper and can do uploads.

I just need to make a few small changes and will be ready to
upload the amd64 build.

Thanks for your offer, I will keep it in mind :)

Cheers!
Alex



signature.asc
Description: Digital signature


Bug#833119: libdbd-oracle-perl: Oracle Instant Client installation instructions outdated

2016-08-01 Thread Alex Muntada
Christoph Biedl:

> Perhaps rephrase the last sentence to
> 
> | To install the Instant Client, download the RPM package 
> | * "Instant Client for Linux x86-64" for amd64, or 
> | * "Instant Client for Linux x86" for i386
> | from 
> 
> | and install it using the "alien" program.
> 
> This however assumes the labels are somewhat stable.

I made some improvements in the documentation based on your
comments. Please find the changes in http://deb.li/30t7A

> Personally, I'd also add the alien package to Suggests: or even
> Recommends:,

alien and fakeroot are both build dependencies for the instant
client packages, but not for libdbd-oracle-perl itself. As long
as you build the instant client somewhere else, you don't need
those extra packages to install libdbd-oracle-perl and they
don't provide extra features either.

> add two sentences:
>
> | An "Oracle Account" is required to download these packages.
> 
> | Other architectures are not supported.

Both sentences were added too. See the changes above.

Thanks!
Alex



signature.asc
Description: Digital signature


Bug#833119: libdbd-oracle-perl: Oracle Instant Client installation instructions outdated

2016-08-03 Thread Alex Muntada
Christoph Biedl:

> Nice. You plan to leave the description in debian/control unchanged?
> Then I suspect people will still follow just the link there and might
> get stuck the way I did. It's so clickable in
> https://packages.debian.org/sid/libdbd-oracle-perl
> 
> Also README.Debian is not accessible before the package is installed,
> but it's not installable before the procedures described there to
> install the instant client have been followed %-)

Hmm, you're absolutely right. I didn't remember that detail and
I think it's really the key to improve the whole documentation.

> So I'd rather re-phrase the last sentence, use an URL to your README,
> and also mention the arch restriction.
> 
> | To install the Instant Client, available for the i386 and amd64 archs
> | only, download the RPM package from the Oracle web page and install it
> | using Alien. Detailled instructions for this are available at
> | 
> 

What about using the whole README contents in the Description
field in debian/control and get rid of README? Would it be too
much?

Thanks!
Alex



signature.asc
Description: Digital signature


Bug#832845: [Help] Re: Bug#832845: libbio-das-lite-perl: FTBFS: Tests failures

2016-08-07 Thread Alex Muntada
Andreas Tille:

> I can reproduce the problem but I have no idea how to solve it.

The issue is "use base" of a module without using it first:

Base class package "t::FileStub" is empty.
(Perhaps you need to 'use' the module which defines that package first,
or make that module available in @INC (@INC contains: 
/«PKGBUILDDIR»/blib/lib /«PKGBUILDDIR»/blib/arch lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.22.2 /usr/local/share/perl/5.22.2 
/usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .).
 at t/FileStubChunked.pm line 11.

And the fix is easy:

$ diff -u t/FileStubChunked.pm{.orig,}
--- t/FileStubChunked.pm.orig   2011-05-06 12:24:03.0 +0200
+++ t/FileStubChunked.pm2016-08-07 13:17:36.272822915 +0200
@@ -8,6 +8,7 @@
 package t::FileStubChunked;
 use strict;
 use warnings;
+use t::FileStub;
 use base qw(t::FileStub);
 
 our $VERSION = do { my @r = (q$Revision: 19 $ =~ /\d+/mxg); sprintf 
'%d.'.'%03d' x $#r, @r };

Cheers!
Alex



Bug#847628: ITP: libpod-pom-view-restructured-perl -- View for Pod::POM that outputs reStructuredText

2016-12-09 Thread Alex Muntada
Package: wnpp
Severity: wishlist
Owner: Alex Muntada <al...@alexm.org>

* Package name: libpod-pom-view-restructured-perl
  Version : 0.02
  Upstream Author : Don Owens <d...@regexguy.com>
* URL : https://metacpan.org/pod/Pod::POM::View::Restructured
* License : Artistic
  Programming Lang: Perl
  Description : View for Pod::POM that outputs reStructuredText

This module outputs reStructuredText that is expected to be used with
Sphinx. Verbatim sections (indented paragraphs) in the POD will be output
with syntax hilighting for Perl code by default.

This module will be used to build the Debian Perl Group manual on
<http://pkg-perl.alioth.debian.org>.

The package will be maintained under the umbrella of the Debian Perl Group.



signature.asc
Description: Digital signature


Bug#847516: RFP: libnet-dns-lite-perl -- libnet-dns-lite-perl

2016-12-10 Thread Alex Muntada
Control: retitle -1 ITP: libnet-dns-lite-perl -- a pure-perl DNS resolver with 
support for timeout
Owner: Alex Muntada <al...@alexm.org>
X-Debbugs-CC: debian-p...@lists.debian.org

I'm going to take care of packaging this module.

Cheers,
Alex



signature.asc
Description: Digital signature


Bug#847514: Amazon::S3 vs. Net::Amazon::S3

2016-12-14 Thread Alex Muntada
Christopher Hoskin:

> I'd already done most of this at the weekend, so thought
> I might as well upload it. Hope you don't mind!

Not at all :)

Just remember that retitling a RFP bug into an ITP and
taking ownership makes it easier to see that somebody
is already working on the package.

Thanks!
Alex



signature.asc
Description: Digital signature


Bug#847514: Amazon::S3 vs. Net::Amazon::S3

2016-12-12 Thread Alex Muntada
Reading the CPAN Ratings I found out that Net::Amazon::S3
has many more dependencies (some huge ones, like Moose and
XML::LibXML) than Amazon::S3.

In my opinion, that difference should justify that we also
package Amazon::S3 for Debian since RT depends on it.

On the other side, https://github.com/tima/perl-amazon-s3
hasn't received any changes since 2009 and the CPAN RT queue
for Amazon::S3 has been unattended for several years too.
So it seems that Amazon::S3 is actually unmaintained.

FWIW, https://github.com/rustyconover/net-amazon-s3 hasn't
got any changes in more than a year either (9 issues and
3 pull requests open). I may be wrong, but I think that,
in terms of maintainership, there's no difference between
the two at this moment.

Thus, unless there's any strong opinion against it, I'll
start packaging Amazon::S3 in a few days so we can have
all RT 4.4 deps ready.

Cheers!
Alex



signature.asc
Description: Digital signature


Bug#860023: libdebian-source-perl: Rejects valid field names based on letter case

2017-04-12 Thread Alex Muntada
gregor herrmann:


Maybe someone has an idea how we can simulate something
like case-insensitive method names?


AUTOLOAD comes to mind, but that's something we'd probably like to avoid.
Normalizing the method names is the alternative: replace dashes with
underscores, make the whole method name smallcase, then call it.

I can take a look at the actual code tomorrow and see how difficult it'd be.

Cheers!
Alex


Bug#860023: libdebian-source-perl: Rejects valid field names based on letter case

2017-04-13 Thread Alex Muntada
Ben Finney:

> So, with the above example, if each those field names were accepted,
> and they all map to the Perl object accessor ‘Vcs_Git’, and other Perl
> code still needed to spell the *accessor* name that way, that would
> IMO be compliant with Policy and would resolve this bug report.

The patch provided below accepts any valid field ignoring case
by using the canonical name instead, so VCS-Git, vCS-gIT, etc.
will end up being Vcs-Git. Would that be compliant with Policy?

Cheers!
Alex

diff --git a/lib/Debian/Control/Stanza.pm b/lib/Debian/Control/Stanza.pm
index f6642e6..3036e14 100644
--- a/lib/Debian/Control/Stanza.pm
+++ b/lib/Debian/Control/Stanza.pm
@@ -48,9 +48,17 @@ L class.
 
 use constant fields => ();
 
+my %canonical;
+
 sub import {
 my( $class ) = @_;
 
+# map the accessor name for the lower case equivalent
+%canonical = map (
+( lc($_) => $_ ),
+$class->fields,
+);
+
 $class->mk_accessors( $class->fields );
 }
 
@@ -87,6 +95,8 @@ sub new {
 
 while( my($k,$v) = each %$init ) {
 $k =~ s/-/_/g;
+# translate field name into the accessor canonical name
+$k = $canonical{ lc $k } || $k;
 $self->can($k)
 or croak "Invalid field given ($k)";
 $self->$k($v);


signature.asc
Description: Digital signature


Bug#871769: forgot to attatch patch

2017-08-11 Thread Alex Muntada
Patch attached now, sorry.

Cheers,
Alex

diff --git a/man/reportbug.1 b/man/reportbug.1
index f5f0ede..201e3e1 100644
--- a/man/reportbug.1
+++ b/man/reportbug.1
@@ -190,7 +190,7 @@ could use
 Include the specified \fIFILE\fP as part of the body of the message to
 be edited.  Can be used multiple times to add multiple files;
 text-only please!  From a suggestion by Michael Alan Dorman in the
-\fBbug\fP mailing list.  (See also the \fB\-a/\-\-attach\fP option.)
+\fBbug\fP mailing list.  (See also the \fB\-A/\-\-attach\fP option.)
 .TP
 .B \-I, \-\-no\-check\-installed
 Do not check whether the package is installed before filing a report.


signature.asc
Description: PGP signature


Bug#871767: lintian: [checks/cruft] use substr instead of substring in example

2017-08-11 Thread Alex Muntada
Package: lintian
Version: 2.5.52
Severity: minor

Dear Maintainers,
the mentions-deprecated-usr-lib-perl5-directory check show an
example to add in debian/rules that uses a misspelled Perl
function that gives an error:

$ perl -MConfig -wE'say substring($Config{vendorarch},1)'
Undefined subroutine ::substring called at -e line 1.

The right spelling would be substr (patch attached at the end).

Cheers!
Alex


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages lintian depends on:
ii  binutils  2.29-4
ii  bzip2 1.0.6-8.1
ii  diffstat  1.61-1+b1
ii  dpkg  1.18.24
ii  file  1:5.31-1
ii  gettext   0.19.8.1-2+b1
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.32+b2
ii  libarchive-zip-perl   1.59-1
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-2+b2
ii  libdpkg-perl  1.18.24
ii  libemail-valid-perl   1.202-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.96-1
ii  liblist-moreutils-perl0.416-1+b3
ii  libparse-debianchangelog-perl 1.2.0-12
ii  libperl5.26 [libdigest-sha-perl]  5.26.0-5
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.72-1
ii  libxml-simple-perl2.24-1
ii  libyaml-libyaml-perl  0.63-2+b2
ii  man-db2.7.6.1-2
ii  patchutils0.3.4-2
ii  perl  5.26.0-5
ii  t1utils   1.40-2
ii  xz-utils  5.2.2-1.3

Versions of packages lintian recommends:
pn  libperlio-gzip-perl  

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  dpkg-dev   1.18.24
ii  libhtml-parser-perl3.72-3+b2
ii  libtext-template-perl  1.46-1


diff --git a/checks/cruft.desc b/checks/cruft.desc
index 57ed5cc95..e3948565b 100644
--- a/checks/cruft.desc
+++ b/checks/cruft.desc
@@ -857,7 +857,7 @@ Info: As of Perl 5.20, the vendorarch directory is /usr/lib/triplet/perl
  but this package still uses usr/lib/perl5 in some of the files under debian/.
  Please replace that with the value of $Config{vendorarch} configuration
  parameter, e.g.
-  $(shell perl -MConfig -wE'say substring($$Config{vendorarch},1)')
+  $(shell perl -MConfig -wE'say substr($$Config{vendorarch},1)')
 
 Tag: readme-source-is-dh_make-template
 Severity: important


signature.asc
Description: PGP signature


Bug#871769: reportbug: man page mentions -a instead of -A

2017-08-11 Thread Alex Muntada
Package: reportbug
Version: 7.1.7
Severity: minor

Dear Maintainer,
while reading how to attach a file in reportbug I found a small
typo in the man page where it mentions the -a instead of -A for
attachments. The details are in the patch attached below.

Cheers,
Alex


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages reportbug depends on:
ii  apt1.5~beta1
ii  python33.5.3-3
ii  python3-reportbug  7.1.7

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail   
pn  debconf-utils
pn  debsums  
pn  dlocate  
pn  emacs24-bin-common | emacs25-bin-common  
ii  file 1:5.31-1
pn  gir1.2-gtk-3.0   
pn  gir1.2-vte-2.91  
ii  gnupg2.1.18-8
pn  postfix | exim4 | mail-transport-agent   
pn  python3-gi   
pn  python3-gi-cairo 
pn  python3-gtkspellcheck
pn  python3-urwid
ii  xdg-utils1.1.1-1

Versions of packages python3-reportbug depends on:
ii  apt1.5~beta1
ii  file   1:5.31-1
ii  python33.5.3-3
ii  python3-debian 0.1.30
ii  python3-debianbts  2.6.1
ii  python3-requests   2.18.1-1

python3-reportbug suggests no packages.



signature.asc
Description: PGP signature


Bug#867068: nm.debian.org: Cannot claim account after former SSO alioth cert expired

2017-07-03 Thread Alex Muntada
Package: nm.debian.org
Severity: minor

Hi!

On April I claimed my GPG fingerprint for the NM account as part
of my path to becoming a DD. With the claim I managed to set up
a few fields and start the process.

My SSO alioth certificate expired on May 27, so I requested a new
one on May 31.

Recently, I tried to see the status of my application for DD in
nm.debian.org and I found that the site says:

alexm-gu...@users.alioth.debian.org (not known to this site yet)

Then, I tried to claim that account again and this time I got a
different message:

The GPG fingerprint corresponds to a person that has a valid
Single Sign-On username

Now, I'm not sure if this issue is due to the final steps of my
application being in progress or that NM website doesn't support
reclaiming an account that had been already claimed with a older
certificate.

I haven't looked in the website code yet, but I thought it would
be helpful to file this bug in case someone else had the same
issue.

Thanks a lot,
Alex


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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



signature.asc
Description: PGP signature


Bug#870334: pkg-perl-autopkgtest: revisiting smoke prove --recurse

2017-08-04 Thread Alex Muntada
Niko Tyni:

> Any urgency this issue had is gone now that you did all the work of
> fixing the --recurse regressions. Many thanks for that :)
> 
> I think I'm leaving this for now. We can see if it becomes a problem
> later, and if not, just close this.

Agreed.

Thanks both for your work!
Alex



signature.asc
Description: PGP signature


Bug#870252: pkg-perl-autopkgtest: skip t/00-compile/*.t

2017-08-04 Thread Alex Muntada
gregor herrmann:

> A quick glance at the commit says: looks good!

Looks good to me, too.

Cheers!
Alex



signature.asc
Description: PGP signature


Bug#870876: tracker.debian.org: make subscription easier to upstreams with many packages

2017-08-05 Thread Alex Muntada
Package: tracker.debian.org
Severity: wishlist

Dear Maintainers,
some time ago one particular upstream for several Perl modules
asked me if there's a way to easily subscribe to all packages
related to them automatically, i.e. an opt-in subscription for
upstreams that they could just check on or off and if a new
package appears and they're the upstream, then tracker would
automatically subscribe them to that package.

Most pkg-perl packages have a debian/upstream/metadata that
could be used to obtain the upstream author, but I guess it
could be fetched from metacpan also. That could work for other
upstream distribution systems like pypi, rubygems, npm, etc.

Cheers!
Alex


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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



signature.asc
Description: PGP signature


Bug#870872: tracker.debian.org: Server Error (500) when using a new SSO cert

2017-08-05 Thread Alex Muntada
Package: tracker.debian.org
Severity: normal

Dear Maintainers,
I was using my SSO guest-account certificate from alioth just fine
in https://tracker.debian.org/pkg/libpod-pom-view-restructured-perl
and then decided it was time to switch to a new SSO debian account
certificate. So created a new certificate for me in sso.debian.org,
then went to the previous URL but I got a 500 error status from the
tracker.

However, the new certificate did actually work fine after restarting
firefox. I'm not sure if this was a transient error or some other
issue with firefox instead, but I just wanted to let you know.

Cheers!
Alex


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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



signature.asc
Description: PGP signature


Bug#870334: pkg-perl-autopkgtest: revisiting smoke prove --recurse

2017-08-01 Thread Alex Muntada
gregor herrmann:

> alexm has more idea, we'll add something hopefully more
> coherent later :)

My idea is that we should smoke test the same list of tests that
are actually run by "make test" or "./Build test" without having
to parse those *.PL files to figure out that list. Therefore,
the list should be obtained by running those same commands with
some "--dry-run" and "--verbose" options, so we can get a list of
the files being run as tests and put that list in the smoke setup
files.

The issue here is how this "--dry-run" and "--verbose" mode can
be run (e.g. "make -n test TEST_VERBOSE=1" comes to mind) and at
which point of package building that should happen, without
requiring human intervention if possible.

Cheers!
Alex



signature.asc
Description: PGP signature


Bug#790727: Mail::Sender is deprecated upstream

2017-08-22 Thread Alex Muntada
I found this bug report in my open tabs in firefox and I forgot
why I opened it in the first place. Anyway, I took a quick look
and found that it's been deprecated upstream:

https://metacpan.org/pod/Mail::Sender

  "Mail::Sender is deprecated. Email::Sender is the go-to choice
  when you need to send Email from Perl. Go there, be happy!"

Since it has no reverse dependencies and last upload was in 2010,
(it never made it into stretch) I guess it should be pretty safe
to remove it.

Cheers,
Alex



signature.asc
Description: PGP signature


Bug#853045: pkg-perl-tools: Broken link for repack.sh in examples/repack.stub

2017-05-21 Thread Alex Muntada
Hi Christopher,
I see that you updated that URL in Jan 2017, but the change hasn't
made it to sid yet. On the other side, I just checked that the old
URL is now returning a redirect (302) that eventually downloads
the file.

Cheers!
Alex



signature.asc
Description: Digital signature


Bug#832059: dh-make-perl now uses https for copyright-format

2017-05-21 Thread Alex Muntada
Hi Axel,
dh-make-perl switched to using the https URL for copyright format
on 20 May 2016 (commit id 591e0b20), and I just checked that it's
already present in sid (not in jessie, though).

Therefore, do you think that we can close this bug report?

Cheers!
Alex



signature.asc
Description: Digital signature


Bug#877986: libconfig-model-dpkg-perl: skip commit or provide commit message to remove-uploader script

2017-10-08 Thread Alex Muntada
Package: libconfig-model-dpkg-perl
Version: 2.100
Severity: wishlist

Dear Maintainer,

As discussed in debian-perl list, I think it would be a great
idea to add these options to remove-uploader script:

* --no-commit
  Do not perform the final commit step from the script, so the
  person using it can decide whether it's the right time for
  the change to be committed or not.

* --commit-message
  Use the provided commit message instead of default in case
  the resulting default would be inadequate, too long or not
  very helpful in describing the change.

Thanks a lot for considing them,
Alex


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libconfig-model-dpkg-perl depends on:
ii  libapt-pkg-perl  0.1.33
ii  libarray-intspan-perl2.003-1
ii  libconfig-model-perl 2.112-1
ii  libexporter-lite-perl0.08-1
ii  liblog-log4perl-perl 1.49-1
ii  libmouse-perl2.4.10-1
ii  libparse-recdescent-perl 1.967015+dfsg-1
ii  libsoftware-license-perl 0.103012-1
ii  libtext-autoformat-perl  1.74-2
ii  libtext-levenshtein-damerau-perl 0.41-1
ii  liburi-perl  1.72-1
ii  libwww-perl  6.15-2
ii  libyaml-perl 1.21-1
ii  licensecheck 3.0.31-2
ii  lintian  2.5.54
ii  perl 5.26.0-8
ii  perl-modules-5.26 [libmodule-corelist-perl]  5.26.0-8

Versions of packages libconfig-model-dpkg-perl recommends:
ii  libconfig-model-tkui-perl  1.364-1

libconfig-model-dpkg-perl suggests no packages.

-- debconf-show failed


signature.asc
Description: PGP signature


Bug#877984: libconfig-model-dpkg-perl: misinterpreting comments in debian/control

2017-10-08 Thread Alex Muntada
Package: libconfig-model-dpkg-perl
Version: 2.100
Severity: normal

Dear Maintainer,

while preparing a mass-commit removal of inactive pkg-perl
members from Uploaders, I found an issue reformatting
debian/control in libmoosex-types-iso8601-perl:

$ cme modify dpkg-control -save
cme: using Dpkg::Control model
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Warning in 'source Standards-Version' value '3.9.6': Current standards 
version is '4.1.1'. Please read 
file:///usr/share/doc/debian-policy/upgrading-checklist.txt.gz to check what 
changes need to applied to your package to upgrade it from standard version 
'3.9.6' to '4.1.1'.

Configuration item 'binary:"libmoosex-types-iso8601-perl" Synopsis' has a 
wrong value:
Undefined mandatory value.
$ echo $?
2

If I remove the comments in debian/control, then it ends without
failing.

On the other side, if I run cme remove-uploader script then one
of the comments is moved to the end of the stanza while the other
stays where it was, resulting in comments that make no sense
because they should stick together.

I guess that dealing with comments in deb822 format is difficult
if you reorder the fields, thus I'm wondering if there's a way
to reformat debian/control without altering the ordering, just
reformatting the values.

Thanks for your work!
Alex


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

Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libconfig-model-dpkg-perl depends on:
ii  libapt-pkg-perl  0.1.33
ii  libarray-intspan-perl2.003-1
ii  libconfig-model-perl 2.112-1
ii  libexporter-lite-perl0.08-1
ii  liblog-log4perl-perl 1.49-1
ii  libmouse-perl2.4.10-1
ii  libparse-recdescent-perl 1.967015+dfsg-1
ii  libsoftware-license-perl 0.103012-1
ii  libtext-autoformat-perl  1.74-2
ii  libtext-levenshtein-damerau-perl 0.41-1
ii  liburi-perl  1.72-1
ii  libwww-perl  6.15-2
ii  libyaml-perl 1.21-1
ii  licensecheck 3.0.31-2
ii  lintian  2.5.54
ii  perl 5.26.0-8
ii  perl-modules-5.26 [libmodule-corelist-perl]  5.26.0-8

Versions of packages libconfig-model-dpkg-perl recommends:
ii  libconfig-model-tkui-perl  1.364-1

libconfig-model-dpkg-perl suggests no packages.

-- debconf-show failed


signature.asc
Description: PGP signature


Bug#902797: lintian: check latest changelog entry for duplicate contributor information

2018-07-02 Thread Alex Muntada
Hi Jonas,

> I find it irrelevant¹ to list changes reverted or shadowed later
> within same release: Please cleanup auto-generated changelog,
> stripping parts not ending in the final package release.

At least in this particular case (iterating over URL changes in
the deb822 headers) I think this makes a lot of sense. IMHO,
the only meaningful change in the URLs is the current one since
the last released package version.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer - log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#887107: regarding dl10n-check memory footprint

2018-04-29 Thread Alex Muntada
Hi,
an easy way of finding how much memory any command uses, you can
use this trick:

/usr/bin/time --verbose dl10n-check ...

OTOH, if you'd like to get more details about why or where is
this Perl script failing, you can try with Devel::SimpleTrace
module. Just add «use Devel::SimpleTrace;» and you're done
(you'll need libdevel-simpletrace-perl installed, of course).

I tried to debug this issue locally but I need a full mirror,
so I need to figure out where to put all that data first.

My guess is that loading all those details in memory is too
much for tye. We could try mapping the $data hash to disk
before rewriting the whole Debian::L10n::Db module.

Cheers,
Alex



signature.asc
Description: PGP signature


Bug#845297: Migration to Salsa

2018-04-29 Thread Alex Muntada
Hi Paul,

> Please note that smart_change.pl needs to work with the new workflow.
> This means that we can't use git commit IDs in translations headers,
> unless we want smart_change.pl to make two commits instead of one.

Thanks for pointing that out. I've been studying smart_change.pl
and I couldn't find where that commit you mention is happening.

> The alternative is to use git file+metadata hashes, which can be
> calculated before a commit happens, placed into translations headers
> and used to diff between two versions of a file. I'm not sure how well
> this will fit with the existing webwml VCS modules though.

Could you elaborate a bit more on the git file+metafile details?
I'm not following you, sorry.

Thanks!
Alex



signature.asc
Description: PGP signature


Bug#845297: Migration to Salsa

2018-04-29 Thread Alex Muntada
Hi Steve,

> I'm thinking of taking some vacation (a week or so) from my day
> job during May to get stuck in here. When are other people
> available?

I'm attending a conference from May 8 to 10, so I guess I'll be
more available than usual in working hours the whole week.

> What can I help with? I'm OK-ish in perl, so I'm thinking of
> looking at the translation workflow stuff, unless that's
> already in hand.

Laura explained the translation workflow to me, and I thought
that we wouldn't need to keep track of current CVS revisions
because using the last commit id from a file and checking if a
commit id is ancestor to another should be enough:

  $ git log -1 --oneline english/license.wml
  8e8136309fa use https for the link to www.spi-inc.org
  $ git log -1 --oneline catalan/license.wml
  8e8136309fa use https for the link to www.spi-inc.org
  $ git merge-base --is-ancestor 8e8136309fa 8e8136309fa
  $ echo $?
  0

However, I didn't take into account that sometimes there are
changes applied to several files at the same time that have
nothing to do with translations (as showed in the example above).

Therefore, it seems that we'll need to translate CVS revisions to
commit IDs at least once after the repository has been migrated
finally to git and before any translation is performed.

Since we can't be sure that people translating will stop during
the migration, maybe we can add a kill-switch in the scripts so
we can enable it before migrating and removing it to enable the
translation work after everything is setup correctly in git.

Something like this makes sense?

  1. People translate on CVS.
  2. Add a kill-switch to translations scripts.
  3. Let people translate on CVS until migration date.
  4. Enable kill-switch so people cannot translate.
  5. Migrate repo to git.
  6. Setup new workflow.
  7. Make changes to translations docs.
  8. Remove kill-switch.
  9. Let people translate on git.

Steps 5-7 should take the shortest time possible to avoid impact,
of course.

The kill-switch should be very easy to implement, e.g.:

  my $kill_switch = 0;
  die "Sorry! webwml migration in progress. Check the wiki.\n"
  if $kill_switch;

Since I'm not very familiar with the translation workflow yet,
I'd like to work on the Perl scripts that will deal with the
files in git, etc. But I'm fine doing something else if someone
prefers to do that.

Cheers!
Alex



signature.asc
Description: PGP signature


Bug#890815: libtext-dhcpleases-perl: vendor class identifier attribute should be handler

2018-02-20 Thread Alex Muntada
Hi grin,
thanks for providing an improvement for this Perl module.

> Patch to handle vendor class attribute attached.

In general we'd like that new features are being added on the
upstream new releases, otherwise maintainance of the code gets
more complicated for packagers. In this particular case, it seems
that the upstream author isn't active anymore since there are a
few bugs open that didn't get much attention.

Therefore, I'd suggest that you file a new bug report upstream
with this improvement, so there's a record that this has been
reported also there. Then, you may try to contact the upstream
author and see if he's still interested in maintaining that
module. We'll see how to proceed in case he isn't.

Cheers,
Alex



signature.asc
Description: PGP signature


Bug#903220: libconfig-model-dpkg-perl: Please change policy to current version of debian policy in sid

2018-07-10 Thread Alex Muntada
Hi Andreas,

> I'd use the following ranking:
> 
>1. Stay in sync with lintian
>2. use AptPkg API

Agreed. Being in sync with lintian is a Good Thing, even if that
means depending [even more] on lintian.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer - log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#895210: ITP: libdist-zilla-role-modulemetadata-perl -- role for plugins that use Module::Metadata

2018-04-08 Thread Alex Muntada
Package: wnpp
Owner: Alex Muntada <al...@debian.org>
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libdist-zilla-role-modulemetadata-perl
  Version : 0.005
  Upstream Author : Karen Etheridge <et...@cpan.org>
* URL : https://metacpan.org/release/Dist-Zilla-Role-ModuleMetadata
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : role for plugins that use Module::Metadata

This role provides some common utilities for Dist::Zilla plugins which
use Module::Metadata and the information that it provides.

Module Dist::Zilla::Role::ModuleMetadata is a prerequisite for
Dist::Zilla::Plugin::MetaProvides::Package.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



signature.asc
Description: PGP signature


Bug#895211: ITP: libdist-zilla-plugin-metaprovides-package-perl -- Extract namespaces/version from traditional packages for provides

2018-04-08 Thread Alex Muntada
Package: wnpp
Owner: Alex Muntada <al...@debian.org>
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libdist-zilla-plugin-metaprovides-package-perl
  Version : 2.004003
  Upstream Author : Kent Fredric <ken...@cpan.org>
* URL : 
https://metacpan.org/release/Dist-Zilla-Plugin-MetaProvides-Package
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Extract namespaces/version from traditional packages for 
provides

This is a Dist::Zilla|Dist::Zilla Plugin that populates the provides property
of META.json and META.yml by absorbing it from your shipped modules, in a
manner similar to how PAUSE itself does it.

This allows you to easily create an authoritative index of what module
provides what version in advance of PAUSE indexing it, which PAUSE in turn
will take verbatim.

This module requires Dist::Zilla::Role::ModuleMetadata which isn't
currently packaged.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



signature.asc
Description: PGP signature


Bug#895206: ITP: libdist-zilla-plugin-minimumperl-perl -- Detects the minimum version of Perl required for your dist

2018-04-08 Thread Alex Muntada
Package: wnpp
Owner: Alex Muntada <al...@debian.org>
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libdist-zilla-plugin-minimumperl-perl
  Version : 1.006
  Upstream Author : Apocalypse <apo...@cpan.org>
* URL : https://metacpan.org/release/Dist-Zilla-Plugin-MinimumPerl
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Detects the minimum version of Perl required for your dist

Dist::Zilla::Plugin::MinimumPerl uses Perl::MinimumVersion to automatically
find the minimum version of Perl required for your dist and adds it to the
prereqs.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.



signature.asc
Description: PGP signature


Bug#845297: Bug #845297: Website transition from CVS to Git

2018-03-27 Thread Alex Muntada
Hi Laura,

> 3.- Which are the next steps? (I guess attack the Perl scripts,

I'd love to help with those scripts but I'm afraid I lack the
experience of the translation team to understand what is that
needs to be done. I found the issues listed on the wiki page
WebsiteGitTransition, but I can't figure out the changes that
need to be made in the Perl scripts from those.

Thus, if someone could elaborate on the details I may provide
some code. In particular, I think it'd be best to split the
scripts from the translations in webwml repo, so they could
evolve separatedly and the scripts could be migrated to salsa
sooner.

> or find a way of facilitating translators the work to keep
> translations in sync with the "english" folder). About this,
> I have some new ideas (not sure if they are good or silly. Just
> throwing them here for the case it rings a bell for anybody):
> 
> * Maybe Gitlab CI can help to "generate a translator dashboard"
> in a simpler way than the scripts that currently create the
> pages of the type:
> https://www.debian.org/devel/website/stats/es

Gitlab Pages can be built in the CI and then published as
https://{team-name}.pages.debian.net/{whatever}.html

We build the former pkg-perl website using this feature:
https://perl-team.pages.debian.net/

You can see the build script is pretty straight forward:
https://salsa.debian.org/perl-team/perl-team.pages.debian.net/blob/master/.gitlab-ci.yml

> * I'll try to explore the integration with a Weblate instance.

I like the idea of using PO files for translating very much,
since I was member of the translations team for GNU website long
time ago. I would've loved to have something like Weblate...
Some time after I left, Yavor Doganov created GNUnited Nations,
also based on PO files, though it isn't packaged for Debian
either.

Therefore, I think moving to PO files would be worth the effort
the sooner the better. Even if that means breaking the current
workflow for a while, it sure will help getting more people into
translating Debian texts.

Hope this helps,
Alex



signature.asc
Description: PGP signature


Bug#930118: libconfig-model-dpkg-perl: adds debian/compat despite debhelper-compat

2019-07-12 Thread Alex Muntada
Hi Dominique,

> Come to think of it, I've detailed the fix mechanism (sorry
> for the headache), but, in the end, the 'cme fix' command will
> cascade the fixes to end up with 'debhelper-compat (= 12)'
> (or whatever latest release). This is similar to the current
> mechanism where a cme fix for an old compat sets compat (and
> delhelper) to latest compat value.

It makes perfect sense :) Good job!

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#933804: Improve dpt-forward documentation

2019-09-01 Thread Alex Muntada
Control: owner -1 !
Control: tags -1 + fixed pending

Hi Aniol,
thanks for trying dpt-forward and taking the time to report this
bug. Feedback is very welcome :)

> In the dpt-forward man page the need to belong in an
> organization when forwarding a patch to GitHub is not
> stated, so the user won't know that the default organization
> is pkg-perl-tools and it may have to be changed with the
> variable DPT_GITHUB_ORGNAME. I think that both the need to
> be in a organization and how to change it should be added to
> the man page.

The documentation for DPT_GITHUB_* variables and defaults is
available in man Debian::PkgPerl::GitHub. Unfortunately there
was no mention of that in man dpt-forward, so I just added it:
https://salsa.debian.org/perl-team/modules/packages/pkg-perl-tools/commit/ddb5d96a068a2af7ef91c161c007a14841e68a5e

> On the other hand, it is also not explained that the clone
> process is done through SSH, and it may cause problems if you
> expect it to be HTTPS. In this case I think that adding a
> variable DPT_GITHUB_PROTOCOL={https,ssh} would be very useful.

For the record, we've alreary addressed that in merge request !7:
https://salsa.debian.org/perl-team/modules/packages/pkg-perl-tools/merge_requests/7

Thank you!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#934062: Upstream metadata to help our users contribute back to projects we redistribute.

2019-08-06 Thread Alex Muntada
Hi Chris,

> With the current state of the upstream metadata docs, I was
> about to abandon the effort of adding metadata. It's not clear
> at all which fields are useful, how a "normal" file looks like,
> what it contains, ...
> Skimming the wiki gives me the impression its only useful for
> academic citations.

We use debian/upstream/metadata in the Perl team to easily
obtain the CPAN distribution name and the bug tracker URL,
so we can forward patches to CPAN RT or GitHub or mail them
to the upstream authors:

https://manpages.debian.org/unstable/pkg-perl-tools/dpt-forward.1.en.html

When the upstream metadata doesn't exist we try to get that
information from other places (i.e. META.*, debian/control,
debian/copyright, etc.).

For us, having upstream metadata is useful to record that
a particular contact method is preferred by upstream. Even
though there are only a handful of cases where they prefer
to be contacted by mail, those are very important to keep a
healthy relationship.

Hope this helps,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies

2019-07-17 Thread Alex Muntada
Hi gregor,

> I just wanted to propose "Check the README" but it seems like
> the friendly README at
> https://salsa.debian.org/perl-team/modules/packages/libdbd-oracle-perl/blob/master/debian/README
> doesn't get installed in the package anymore … Oops.

Ouch! I missed that. Thanks for pointing that out.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies

2019-07-17 Thread Alex Muntada
Hi Hector,

> Where can I find those packages to close the dependency loop,

Since those dependencies should be installed before this package,
the full package description has a link to the README where you
can find where to download them and how to get them into shape
for Debian:

https://packages.debian.org/buster/libdbd-oracle-perl
https://deb.li/dbdoracle

I just found out that APT is not showing the full package
description anymore, and that makes it more difficult for this
package to explain how to proceed with dependencies.

Any ideas on improving this are truly appreciated.

> checking at non-free those do not seem to be available.

Sorry, we can't put them in non-free either because the source is
not available.

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies

2019-07-17 Thread Alex Muntada
Hi gregor,

> I just wanted to propose "Check the README" but it seems like
> the friendly README [...] doesn't get installed in the package
> anymore … Oops.

I examined the contents of the older versions I have in my
computer and none of them installed the README. Maybe it's
because package installation will fail unless its depends
are met first and hence the link to the README in the full
description.

I guess we could rename README to README.Debian and install
it anyway. What do you think?

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies

2019-07-17 Thread Alex Muntada
Hi Héctor,

> libdbd-oracle-perl depends on oracle-instantclient12.1-basic |
> oracle-instantclient12.1-basiclite, which are not found in
> buster|bullseye|unstable, causes the package to be unusable.

There's a comment in d/copyright explaining why this package is
in contrib:

«The upstream Perl distribution is freely licensed by the
copyright holders but depends on Oracle Instant Client software,
that is not free. Therefore, it belongs to Debian contrib section
according to DFSG.»

Is there something that has recently changed that maybe I'm
missing?

Thanks!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#932257: libdbd-oracle-perl: unsatisfiable dependencies

2019-07-24 Thread Alex Muntada
Control: owner -1 !
Control: severity -1 minor

Hector said:

> Thanks for the explanation, I was just checking repository
> consistency for buster and came up with this issue. I leave
> it up to you to downgrade severity accordingly or close the
> bug. Fixing the README installation one way or the other
> might be nice.

Will fix the README installation. For now, I'm lowering the
bug severity to avoid autoremoval from testing.

Thanks,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#945298: ITA: fet -- timetable generator

2019-12-01 Thread Alex Muntada
Control: retitle -1 ITA: fet -- timetable generator
Control: owner -1 !

As part of my job at UPC BarcelonaTech I need to find a
replacement for our current timetabling software and FET
looks promising.

I'm also open to collaborate with anyone else that has an
interest in maintaining this package. Just let me know,
so we can work together.

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#880368: YAML::XS::Load expects utf8 octets, not perl's encoding; use slurp_raw

2019-12-19 Thread Alex Muntada
Hi Dominique,

> Dear debian-perl team colleagues, do you foresee any problem
> with this change?

None that I'm aware of... +1 to YAML::XS

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#958542: dacco: non utf-8 filename in source

2020-04-25 Thread Alex Muntada
Hi Ivo,

> If you prefer, I can do an NMU (or sponsor an upload).

Please, go ahead with the NMU. The former maintainer passed away
last year and the package has a new prospective maintainer, that
I intend to sponsor eventually, but packaging work hasn't started
yet.

Thanks!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#966896: fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here

2020-08-29 Thread Alex Muntada
Upstream already fixed this issue in a newer version.

After asking Jordi his permission in private, I've prepared a NMU.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970756: gap-openmath: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: gap-openmath
Version: 11.5.0+ds-1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970755: gap-guava: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: gap-guava
Version: 3.15+ds-2
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970759: normaliz: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: normaliz
Version: 3.8.5+ds-1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970753: apertium-ind-zlm: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: apertium-ind-zlm
Version: 0.1.2-2
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: kar...@debian.org, t...@didriksen.cc

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970754: e-antic: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: e-antic
Version: 0.1.5+ds-2.1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: plugw...@raspbian.org, calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970757: gap-scscp: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: gap-scscp
Version: 2.3.1+ds-1
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#970758: mpfi: Wrong e-mail address in Maintainer field

2020-09-22 Thread Alex Muntada
Package: mpfi
Version: 1.5.3+ds-4
Severity: serious
Usertags: alioth-lists.debian.org
X-Debbugs-Cc: calcu...@rezozer.net, lfou...@debian.org

The Maintainer of this package uses the alioth-lists.debian.org
domain, which does not exist. This breaks policy §3.3[1] that
requires a working e-mail address. You should be using the
alioth-lists.debian.net domain instead.

After reporting[2] the issue to debian-science-maintainers list,
I'm filing this bug as suggested[3] there.

Cheers,
Alex

  [1] https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer
  [2] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085266.html
  [3] 
https://alioth-lists.debian.net/pipermail/debian-science-maintainers/2020-September/085350.html

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#966896: fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here

2020-08-03 Thread Alex Muntada
Tags: +patch

Hi Lucas,
thanks for reporting this bug. Fortunately, the fix is pretty
straight-forward :)

> Relevant part (hopefully):
> > gcc fatsort.o FAT_fs.o deviceio.o endianness.o sig.o entrylist.o errors.o 
> > options.o clusterchain.o sort.o misc.o natstrcmp.o stringlist.o regexlist.o 
> >  -o fatsort -Wl,-z,relro -Wl,-z,now -s
> > /usr/bin/ld: entrylist.o:./src/options.h:38: multiple definition of 
> > `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here
> > /usr/bin/ld: options.o:./src/options.h:38: multiple definition of 
> > `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here
> > /usr/bin/ld: sort.o:./src/options.h:38: multiple definition of 
> > `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here
> > /usr/bin/ld: misc.o:./src/options.h:38: multiple definition of 
> > `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here
> > collect2: error: ld returned 1 exit status

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄

--- fatsort-1.6.2.605.orig/src/options.h
+++ fatsort-1.6.2.605/src/options.h
@@ -35,7 +35,7 @@ extern uint32_t OPT_VERSION, OPT_HELP, O
 extern struct sStringList *OPT_INCL_DIRS, *OPT_EXCL_DIRS, *OPT_INCL_DIRS_REC, *OPT_EXCL_DIRS_REC, *OPT_IGNORE_PREFIXES_LIST;
 extern struct sRegExList *OPT_REGEX_INCL, *OPT_REGEX_EXCL;
 
-char *OPT_LOCALE;
+extern char *OPT_LOCALE;
 
 // parses command line options
 int32_t parse_options(int argc, char *argv[]);


signature.asc
Description: PGP signature


Bug#977199: lists.debian.org: Please create a new list: debian-localgroups

2021-01-10 Thread Alex Muntada
Dear list admins,
I'm a member of the Debian Catalan local group and I'm interested
in having a list for support and help organizing local groups in
general, thus I'm supporting Elena's request.

This topic was discussed in #debian-localgroups meetings and the
conclusion was that having such a list seems the most appropiate
way for us to coordinate. The #debian-localgroups usually has
more than 40 users, which are prospective members of the list.

Hope this helps!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#990521: I wonder whether bug #990521 "apt-secure points to apt-key which is deprecated" should get a higher severity

2021-07-02 Thread Alex Muntada
Hi Andreas

> BTW, I did some
> 
>apt-key del 578A0494D1C646D1
> 
> added my key to /etc/apt/trusted.gpg.d/fam-tille.gpg and added an
> according
> 
>[signed-by=/etc/apt/trusted.gpg.d/fam-tille.gpg]
> 
> option to the sources.list line ... and it does not yet work.  So I
> think it is critical to point to a solution that *really* works.

Move it out of /etc/apt/trusted.gpg.d which is the equivalent of
using «apt-key add». This works for me:

deb [arch=amd64 signed-by=/usr/local/share/keyrings/docker-archive-keyring.gpg] 
https://download.docker.com/linux/debian buster stable

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#984568: pam: update translation of debian/po/ca.po

2021-03-05 Thread Alex Muntada
Source: pam
Severity: wishlist
Tags: patch

Dear Maintainer,
please find the updated translation of debian/po/ca.po below.

Thanks,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄

diff --git a/debian/po/ca.po b/debian/po/ca.po
index 94e76c02..b79d3001 100644
--- a/debian/po/ca.po
+++ b/debian/po/ca.po
@@ -8,15 +8,14 @@ msgstr ""
 "Project-Id-Version: pam 1.1.3-6.1\n"
 "Report-Msgid-Bugs-To: p...@packages.debian.org\n"
 "POT-Creation-Date: 2021-02-26 10:32-0500\n"
-"PO-Revision-Date: 2012-01-21 08:33+0100\n"
-"Last-Translator: Innocent De Marchi \n"
+"PO-Revision-Date: 2021-03-05 11:06+0100\n"
+"Last-Translator: Alex Muntada \n"
 "Language-Team: Catalan \n"
 "Language: ca\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"X-Poedit-Language: Catalan\n"
-"X-Poedit-Country: SPAIN\n"
+"X-Generator: Poedit 2.2.1\n"
 
 #. Type: string
 #. Description
@@ -28,12 +27,6 @@ msgstr ""
 #. Type: string
 #. Description
 #: ../libpam0g.templates:1001
-#, fuzzy
-#| msgid ""
-#| "Most services that use PAM need to be restarted to use modules built for "
-#| "this new version of libpam.  Please review the following space-separated "
-#| "list of init.d scripts for services to be restarted now, and correct it "
-#| "if needed."
 msgid ""
 "Most services that use PAM need to be restarted to use modules built for "
 "this new version of libpam.  Please review the following space-separated "
@@ -41,8 +34,8 @@ msgid ""
 msgstr ""
 "És necessari reiniciar la majoria dels serveis que fan servir PAM per a que "
 "facin servir els mòduls d'aquesta versió de «libpam». Reviseu la següent "
-"llista separada per espais dels scripts «init.d» que indica els serveis que "
-"es reiniciaran ara i modificau-la si és necessari."
+"llista separada per espais dels serveis que es reiniciaran ara i modificau-"
+"la si és necessari."
 
 #. Type: error
 #. Description
@@ -113,8 +106,8 @@ msgid ""
 "asked questions on each library upgrade."
 msgstr ""
 "Hi ha serveis instal·lats en el seu sistema que necessiten ser reiniciats en "
-"actualitzar certes biblioteques, com libpam, libc i libssl. Ja que el procés "
-"de reinicii pot causar interrupcions en el sistema, normalment se vos "
+"actualitzar certes biblioteques, com libpam, libc i libssl. Com que el "
+"procés de reinici pot causar interrupcions en el sistema, normalment se vos "
 "demanarà, a cada actualització, per a la llista de serveis que voleu "
 "reiniciar. Podeu triar aquesta opció per evitar que se vos demani; en canvi, "
 "es faran automàticament tots els reinicis necessaris sense demanar-vos "
@@ -141,7 +134,7 @@ msgid ""
 "allowing configuration of additional actions to take when starting user "
 "sessions."
 msgstr ""
-"Els «Pluggable Authentication Modules» (PAM, o Mòduls d'autenticació "
+"Els «Pluggable Authentication Modules» (PAM, o mòduls d'autenticació "
 "inseribles) determinen com es gestionen en el sistema l'autenticació, "
 "autorització i modificació de contrasenyes. També permet la definició "
 "d'accions addicionals a realitzar quan s'inicia la sessió d'un usuari."
@@ -186,7 +179,7 @@ msgstr "Seleccioneu un conjunt distint de mòduls a activar."
 #: ../libpam-runtime.templates:4001
 msgid "Override local changes to /etc/pam.d/common-*?"
 msgstr ""
-"Desitjau descartar els canvis locals realitzats a «/etc/pam.d/common-*»?"
+"Desitjau sobreescriure els canvis locals realitzats a «/etc/pam.d/common-*»?"
 
 #. Type: boolean
 #. Description
@@ -249,7 +242,7 @@ msgstr ""
 #. Description
 #: ../libpam-modules.templates:2001
 msgid "PAM Profiles with Deprecated Modules Disabled"
-msgstr ""
+msgstr "Perfils de PAM amb mòduls descartats desactivats"
 
 #. Type: error
 #. Description
@@ -260,12 +253,16 @@ msgid ""
 "prevent users from accessing your system. As a result, these profiles have "
 "been disabled."
 msgstr ""
+"El vostre sistema tenia perfils de PAM activats amb els mòduls PAM "
+"${modules}. Aquests mòduls s'han eliminat de PAM. Deixant aquests perfils "
+"activats els usuaris no podrien accedir al vostre sistema. Com a resultat, "
+"aquests perfils s'han desactivat."
 
 #. Type: error
 #. Description
 #: ../libpam-modules.templates:3001
 msgid "you are us

Bug#1010241: libdebian-source-perl: Incorrect case sensitivity in Debian::Control::Stanza::new for field names

2022-04-27 Thread Alex Muntada
Hi gregor!

> And then I found the following d/changelog entry for 0.95:
> 
>   [ Alex Muntada ]
>   * Debian::Control::Stanza: accept case-insensitive field names in new()
> as required by Debian Policy while retaining the canonical accessors.
> Thanks to Ben Finney for the bug report. (Closes: #860023)

Wow, I totally forgot that :)

> But yeah, it's not only a déjà-vu, apparently we need to take a look
> at this part of the code again …

Here's a proof of concept:

```
#!perl
use strict;
use warnings;
use v5.30;

use Debian::Control::Stanza::Source;
#use Debian::Control::Stanza::Binary;
my %stanza = (
'Source' => 'package-name',
'VCS-GIT' => 'test-vcs-git',
);
my $s = Debian::Control::Stanza::Source->new(\%stanza);
say $s->Vcs_Git;
```

It works as expected unless you uncomment the use of the
Stanza::Binary package. Then it fails:

```
Invalid field given (VCS_GIT) at case-insensitive.pl line 12.
```

That's because the import in D::C::Stanza is called twice and
the $class->fields is different for ::Source than ::Binary.
I think we need to move the canonicalization to the constructor
instead (see the patch attached, that seems to work and passes
t/Control.t too).

HTH

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄

diff --git a/lib/Debian/Control/Stanza.pm b/lib/Debian/Control/Stanza.pm
index f534c19..3be0d2a 100644
--- a/lib/Debian/Control/Stanza.pm
+++ b/lib/Debian/Control/Stanza.pm
@@ -63,12 +63,6 @@ my %canonical;
 sub import {
 my( $class ) = @_;
 
-# map the accessor name for the lower case equivalent
-%canonical = map (
-( lc($_) => $_ ),
-$class->fields,
-);
-
 $class->mk_accessors( $class->fields );
 }
 
@@ -99,6 +93,12 @@ sub new {
 my $class = shift;
 my $init = shift || {};
 
+# map the accessor name for the lower case equivalent
+my %canonical = map (
+( lc($_) => $_ ),
+$class->fields,
+);
+
 my $self = Tie::IxHash->new;
 
 bless $self, $class;


signature.asc
Description: PGP signature


Bug#1022124: libdbd-oracle-perl needs binaries uploaded for the perl 5.36 transitions

2022-10-21 Thread Alex Muntada
Hi Adrian,

> libdbd-oracle-perl cannot be built on the buildds,
> and it needs binaries uploaded for the perl 5.36 transition.

Please, don't hesitate to remove libdbd-oracle-perl from testing
for the perl 5.36 transition to proceed. I'll try to have those
binaries by next week, but I don't want to stall the transition.

Cheers!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#1021197: fwupd: Blocked executable in the ESP, ensure grub and shim are up to date

2022-10-03 Thread Alex Muntada
Package: fwupd
Version: 1.5.7-4
Severity: normal
Tags: fixed-upstream

Dear Maintainer,
there's an issue in bullseye fwupd that seems to need an upgrade
or a backport from unstable for the following update to succeed
(see https://github.com/fwupd/fwupd/issues/5035 for details):

$ sudo fwupdmgr update
Devices with no available firmware updates:
 • ...
Upgrade available for UEFI dbx from 77 to 217
UEFI dbx and all connected devices may not be usable while updating. Continue 
with update? [Y|n]:
Downloading… [***]
Decompressing…   [***]
Authenticating…  [***]
Authenticating…  [***]
Updating UEFI dbx…   [***]
Verifying…   [***]
Blocked executable in the ESP, ensure grub and shim are up to date: 
/boot/efi/EFI/Boot/shimx64.efi Authenticode checksum 
[47b31a1c7867644b2ee8093b2d5fbe21e21f77c1617a2c08812f57ace0850e9f] is present 
in dbx



-- System Information:
Debian Release: 11.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages fwupd depends on:
ii  libc6  2.31-13+deb11u3
ii  libcurl3-gnutls7.74.0-1.3+deb11u2
ii  libefiboot137-6
ii  libelf10.183-1
ii  libflashrom1   1.2-5
ii  libfwupd2  1.5.7-4
ii  libfwupdplugin11.5.7-4
ii  libglib2.0-0   2.66.8-1
ii  libgnutls303.7.1-5+deb11u2
ii  libgudev-1.0-0 234-1
ii  libgusb2   0.3.5-1
ii  libjcat1   0.1.3-2
ii  libjson-glib-1.0-0 1.6.2-1
ii  libpolkit-gobject-1-0  0.105-31+deb11u1
ii  libsmbios-c2   2.4.3-1
ii  libsqlite3-0   3.34.1-3
ii  libsystemd0247.3-7
ii  libtss2-esys-3.0.2-0   3.0.3-2
ii  libxmlb1   0.1.15-2
ii  shared-mime-info   2.0-1

Versions of packages fwupd recommends:
ii  bolt   0.9.1-1
ii  dbus   1.12.20-2
ii  fwupd-amd64-signed [fwupd-signed]  1.5.7+4
ii  python33.9.2-3
pn  secureboot-db  
ii  udisks22.9.2-2+deb11u1

Versions of packages fwupd suggests:
pn  gir1.2-fwupd-2.0  

-- no debconf information

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#1022124: libdbd-oracle-perl Upload

2022-11-18 Thread Alex Muntada
Hi Christoph,

> when do you plan to upload the fixed version?
> If you need any help, please let us know.

The VM where I was building and testing the amd64 package is
currently broken. I should be able to build the package anyway
on a chroot, but I have no means to test it ATM.

I can build and upload the package untested if you're in a hurry.
Otherwise, I guess I should be able to reinstall the VM this
weekend and proceed as usual.

Cheers and sorry for the inconvenience,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#1016992: libdbd-oracle-perl: Built against unsupported Oracle Instant Client 12.1

2022-11-20 Thread Alex Muntada
Hi Daniel,

> libdbd-oracle-perl has been built against OIC 12.1
> since version 1.66-1 (Aug 30, 2013).
> 
> Oracle's "Release Schedule of Current Database Releases":
>   
> https://support.oracle.com/knowledge/Oracle%20Database%20Products/742060_1.html
> says "Patching End Dates" are:
>   * 12.1 - Jul 31, 2022
>   * 19c  - Apr 30, 2024
>   * 21c  - Apr 30, 2024

Thanks for sharing that URL above. After reading it, let me
expand on the support details for the record of this bug:

* 12.1.0.2 (Terminal Release) "Patching End Dates":
  - Jul 31, 2022 with paid ES, ULA, or EBS waiver
  - Dec 31, 2023 (with a Custom Market Driven Support Contract)
* 19c (Long Term Release)
  - April 30, 2025 with no ES/ULA
(see that you wrote **2024** here!)
  - April 30, 2027 with ES/ULA
* 21c (Innovation Release)
  - April 30, 2024

> Upstream DBD::Oracle 1.81 introduced support for OIC 21.
> 
> Could the following two changes be made?
>   1) Import upstream version 1.83
>   2) Build against OIC 19c (Version 19.16) or 21c (Version 21.7)
>
> However, two problems remain:
>   1) Bookworm will be supported well beyond Apr 30, 2024
>   2) Oracle may release higher 19.xx and 21.x versions

Seeing the above end dates, my bet is on 19c right now for two
reasons: 1) is the longest supported version right now, and 2)
is a Long Term Release, which means that they may extend its
support longer as they did with 12.1.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#1023196: fet: new version 6.7.0 available

2022-11-28 Thread Alex Muntada
Hi Gianfranco,

> Hello, please consider updating to version 6.7.0, capable of
> building with qt6 too, including new feature and bug fixes.

I just uploaded 6.7.3, that closed this bug. FYI, I tried to
build fet with Qt6 and failed. Then I decided to upgrade the
package with Qt5 first, polish a few packaging details and try
to build it with Qt6 next time.

It turns out that the build is missing qmake (FWIW, I've been
comparing debian/control from other Qt6 enabled packages because
I couldn't find any best practices on the KDE/Qt Team website).
Let me know if you can figure it out.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#1032432: ITA: fatsort - taking over maintenance

2023-03-06 Thread Alex Muntada
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: Jordi Sayol 

After talking to current maintainer of fatsort, we both agreed
that I should take over maintenance.

This bug report will serve as a log of our agreement.

Thanks,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#1016992: libdbd-oracle-perl: Built against unsupported Oracle Instant Client 12.1

2023-02-27 Thread Alex Muntada
Hi Daniel, last time I said:

> Seeing the above end dates, my bet is on 19c right now for two
> reasons: 1) is the longest supported version right now, and 2)
> is a Long Term Release, which means that they may extend its
> support longer as they did with 12.1.

It turns out that 19.18 was released this month for x86_64
(amd64), but not for x86 (i386), which remains at 19.17.

Since having the deps for amd64 and i386 differ was a bad idea,
and after noticing that from release 21 onwards the package name
has no release number included, I decided to upgrade OCI deps to
release 21.

Cheers,
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature


Bug#928460: fatsort FTCBFS: builds for the wrong architecture

2024-04-09 Thread Alex Muntada
Control: owner -1 !
Control: tags -1 moreinfo

Hi Helmut,

it's been a while since you reported this bug, and now fatsort
uses dh instead of cdbs. In fact, I recently uploaded the latest
upstream version that also made some fixes on the Makefile.

Can you check if this bug is still valid?

Thanks!
Alex

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁   Alex Muntada 
  ⢿⡄⠘⠷⠚⠋   Debian Developer  log.alexm.org
  ⠈⠳⣄



signature.asc
Description: PGP signature